kernel lockup on feisty because of rt61 driver
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Won't Fix
|
Undecided
|
Unassigned | ||
linux-source-2.6.20 (Ubuntu) |
Won't Fix
|
Medium
|
Unassigned |
Bug Description
Computer freezes when running Feisty. This happens when using LiveCD, but also with HDD-based-version with all updates installed. System stops responding, mouse cursor freezes, no response to any keyboard input, including Num Lock. Freezes occur on average every 2-3 minutes. Only reboot helps after a freeze. When using console, the following message is displayed:
[64.036621] BUG soft lockup detected on CPU#0!8
The above mentioned error was displayed when I booted the system, waited for graphical login screen to appear, then immediately switched to console by pressing Ctrl+F2, and started to type sudo apt-get, when the system froze. I did not even manage to press enter key to execute the command.
Edgy runs pretty stable on the same hardware.
The output of uname -a is "Linux john-desktop 2.6.20-9-generic #2 SMP Mon Feb 26 03:01:44 UTC 2007 i686 GNU/Linux".
description: | updated |
description: | updated |
Changed in linux-source-2.6.20: | |
assignee: | nobody → ubuntu-kernel-team |
Changed in linux-source-2.6.20: | |
assignee: | nobody → ubuntu-kernel-team |
Thanks for taking the time to report this bug and helping to make Ubuntu better. Unfortunately we can't fix it, because your description doesn't yet have enough information. wiki.ubuntu. com/DebuggingKe rnelProblems . Thanks in advance!
Please include the following additional information, if you have not already done so (please pay attention to lspci's additional options), as required by the Ubuntu Kernel Team:
1. Please include the output of the command 'uname -a' in your next response. It should be one, long line of text which includes the exact kernel version you're running, as well as the CPU architecture.
2. Please run the command 'dmesg > dmesg.log' and attach the resulting file 'dmesg.log' to this bug report.
3. Please run the command 'lspci -vvnn > lspci-vvnn.log' and attach the resulting file 'lspci-vvnn.log' to this bug report.
For your reference, the full description of procedures for kernel-related bug reports is available at http://