Ubuntu
linux-source-2.6.17 package

BUG: soft lockup detected on CPU#0! after Ibern

Bug #75508 reported by Riccardo Lucchese
4
Affects Status Importance Assigned to Milestone
linux-source-2.6.17 (Ubuntu)
Invalid
Undecided
Brian Murray

Bug Description

I'have installed edgy on a Fujitsu-Siemens 7425. Sorry but i don't know if "Ibern" is the exact translation in english, but by the way I mean the button between "suspend" and "restart" in the logout/shutdown dialog.

It seemed interesting to me to save my workspace and shutdown the system so I tried it :)... as i was very "confident" on edgy, after I clicked I just got out of the room... So I don't know what has happened exactly; but when I got back one hour later i found a simple black screen with this message:

[17202835.880000] BUG: soft lockup detected on CPU#0!

I couldn't do anything like typing or something, the system was completely hangt up.

The only thing I can say about CPU#0 :) is that the low-frequency/power-save button was on.

In the next days I won't be able to connect to the internet, so it won't be possible for me to give you more debug infos.

Hope the code string in the message may help!

Thanks,
Riccardo

Revision history for this message
towsonu2003 (towsonu2003) wrote :

can you have a look at bug # 63418 to check out if this is a duplicate of that one? sorry that it's quite a long bug report...

Changed in linux-source-2.6.17:
status: Unconfirmed → Needs Info
Revision history for this message
Mikael Nilsson (mini) wrote :

It's hardly bug 63418, as that only occurs on boot.

Revision history for this message
Brian Murray (brian-murray) wrote :

Please include as attachments 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 'sudo 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 https://wiki.ubuntu.com/KernelTeamBugPolicies . Thanks in advance!

Changed in linux-source-2.6.17:
assignee: nobody → brian-murray
Revision history for this message
Brian Murray (brian-murray) wrote :

We are closing this bug report as it lacks the information, described in the previous comments, we need to investigate the problem further. However, please reopen it if you can give us the missing information and feel free to submit bug reports in the future.

Changed in linux-source-2.6.17:
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

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