System lockup with Thinkpad r32

Bug #51072 reported by William Lachance
10
Affects Status Importance Assigned to Milestone
linux-source-2.6.15 (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

Occassionally, it seems like the release version of Dapper causes
my thinkpad r32 to lockup hard. Neither breezy nor an earlier version of Dapper (from February, seems to manifest the problem).

Attaching /var/log/syslog (the last crash is from around 21:22:48, the messages after are boot messages after restarting), Xorg.0.log, and the output of 'lspci -vv'. Let me know if there's anything else I can provide which will help.

Revision history for this message
Caroline Ford (secretlondon) wrote :

NB Files are attached to duplicate bug #51073.

Looks like wireless drivers?

Revision history for this message
Caroline Ford (secretlondon) wrote :

->Wireless-tools (this may be the wrong package)

Revision history for this message
Simon Law (sfllaw) wrote :

Does this issue still persist in Edgy (6.10)?

Changed in wireless-tools:
assignee: nobody → sfllaw
status: Unconfirmed → Needs Info
Revision history for this message
William Lachance (wrlach) wrote :

A fresh install of Edgy on this laptop is so completely and utterly broken that I haven't been able to tell. Perhaps I'll try again with feisty...

Revision history for this message
William Lachance (wrlach) wrote :

Hmm, it seems like somehow most of my issues went away after reinstalling libgnomeui (bizarre...), so it looks like I may be able to verify this after all. Things are looking good after several hours of use.

Revision history for this message
Simon Law (sfllaw) wrote :

The user has reported that the bug is fixed.

Changed in linux-source-2.6.15:
assignee: sfllaw → nobody
status: Needs Info → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

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