BUG: soft lockup - CPU#1 stuck for 11s! [kacpid:48]; RIP: 0010:[acpi_ps_alloc_op+0x1/0x8c] [acpi_ps_alloc_op+0x1/0x8c] acpi_ps_alloc_op+0x1/0x8c
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Linux |
Invalid
|
High
|
|||
linux (Ubuntu) |
Incomplete
|
Medium
|
Unassigned |
Bug Description
Binary package hint: ubuntu-base
Applies both to Ubuntu 8.04.1, Kernel 2.6.24-19 server and Ubuntu 8.04.1 Kernel 2.6.24-19 generic (desktop).
Both in the server and generic desktop versions of the OS installed on the same machine, an Intel D945GCLF MB w/ Atom CPU. Makes no difference if hyperthreading is enabled or disabled except that when it is disabled, I can't do anything more after the CPU is locked up. In both versions of the OS, I thought that the problem might be CPU temp related, but now I am sure that it is not. Rather, it seems like it is CPU activity related -- even if the CPU is cool, the problem is correlated with a lot of CPU activity. It is not related to a particular application that I'm running. When using the system monitor in the desktop version, I can see CPU #1 going into the lock-up mode, but apparently CPU #0 does the update of the system monitor. No process is shown with high CPU activity. For both versions of the OS, it is impossible to shut down the computer using the OS. The busy CPU prevents all of the processes from terminating. Under the desktop version, once CPU #1 gets locked up, it is possible to undertake one more step in Gnome, at which point it locks up. The locked/busy CPU never becomes unlocked/unbusy.
No problems running Win2k on this computer.
From my Google searches, I have noted that quite a number of different CPU's, motherboards, and versions of Linux (not only Debian derivatives) are suffering from this problem, and it manifests itself under a wide range of circumstances. Smells to me like a kernel problem.
Changed in linux: | |
assignee: | nobody → ubuntu-kernel-team |
status: | Incomplete → Confirmed |
Changed in linux: | |
status: | Unknown → Invalid |
Changed in linux: | |
importance: | Unknown → High |
Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately we can't fix it, because your description does not yet have enough information. The message you describe is a very generic message as the result of many possible different problems.
Please include the following additional information, if you have not already done so (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" after a fresh boot and attach the resulting file "dmesg.log" to this bug report.
3. Please run the command "sudo lspci -vvnn > lspci-vvnn.log" and attach the resulting file "lspci-vvnn.log" to this bug report.
4. Please attach your /var/log/kern.log and /var/log/kern.log.0 files to this bug report.
For your reference, the full description of procedures for kernel-related bug reports is available at https:/ /wiki.ubuntu. com/KernelTeamB ugPolicies Thanks in advance!