Thinkpad T61 locks up / freezes randomly; no flashing caps lock light, mouse cursor can be moved

Bug #377194 reported by Martin Rehn
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

I was experiencing Bug #300693 ("Thinkpad T61p hardlock flashing caps lock") on a Thinkpad T61. This is on a standard Jaunty 386 generic install, up to date as of 2009-05-16. After installing linux-backports-modules-jaunty, as suggested in the comments to that bug report, the machine still freezes, but slightly differently: the mouse cursor can still be moved and the CapsLock LED is not flashing. Otherwise the machine does not respond, but the SysRq key works.

I am reporting these "slightly softer" freezes separately in this report, as suggested by Jamin W. Collins. I'd be happy to hear suggestions on how to hunt down this bug.

ProblemType: Bug
Architecture: i386
DistroRelease: Ubuntu 9.04
HibernationDevice: RESUME=UUID=c18aa08f-d816-4f1d-afb6-6f7e5e641d80
MachineType: LENOVO 6465CTO
Package: linux-image-2.6.28-11-generic 2.6.28-11.42
ProcCmdLine: root=UUID=1d6089df-8dd4-4704-a0f7-8b5a541890ba ro quiet splash
ProcEnviron:
 LANGUAGE=
 LANG=sv_SE.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.28-11.42-generic
SourcePackage: linux

Revision history for this message
Martin Rehn (minpost) wrote :
Revision history for this message
Martin Rehn (minpost) wrote :

Since the WLAN was suspected in Bug #300693, I activated the radio kill switch in the BIOS. Now the wireless LED is always off. This makes no difference though. I am still getting very frequent lockups on this machine, always with the symptoms above.

Revision history for this message
Martin Rehn (minpost) wrote :

I did two more things. I ran Memtest86+ (v. 2.11) repeatedly on the machine, with no errors. Then I tried installing the 2.6.30-rc7 kernel (image-386, headers-all and headers-386) from http://kernel.ubuntu.com/~kernel-ppa/mainline/v2.6.30-rc7/) and the freezes and symptoms remain the same as with the Jaunty 2.6.28 kernel. I verified that I am booting the 2.6.30 kernel after installing it.

Is there anything else that is kernel-related to try? Could it be the Intel graphics drivers after all? What should I try here? This machine was fine with Intrepid, but now it is useless.

Revision history for this message
Jeremy Foshee (jeremyfoshee) wrote :

Hi Martin,

This bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? Can you try with the latest development release of Ubuntu? ISO CD images are available from http://cdimage.ubuntu.com/releases/lucid.

If it remains an issue, could you run the following command from a Terminal (Applications->Accessories->Terminal). It will automatically gather and attach updated debug information to this report.

apport-collect -p linux 377194

Also, if you could test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text. Please let us know your results.

Thanks in advance.

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

tags: added: needs-kernel-logs
tags: added: needs-upstream-testing
tags: added: kj-triage
Changed in linux (Ubuntu):
status: New → Incomplete
Revision history for this message
Jeremy Foshee (jeremyfoshee) wrote :

This bug report was marked as Incomplete and has not had any updated comments for quite some time. As a result this bug is being closed. Please reopen if this is still an issue in the current Ubuntu release http://www.ubuntu.com/getubuntu/download . Also, please be sure to provide any requested information that may have been missing. To reopen the bug, click on the current status under the Status column and change the status back to "New". Thanks.

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

tags: added: kj-expired
Changed in linux (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.