BUG: soft lockup detected on CPU#0!

Bug #71029 reported by Andrew Fenn on 2006-11-09
2
Affects Status Importance Assigned to Milestone
Ubuntu
Undecided
Unassigned
linux (Ubuntu)
Undecided
Unassigned
linux-source-2.6.17 (Ubuntu)
Undecided
Unassigned

Bug Description

I am using a samsung r55 laptop. My laptop specs are at:
http://wiki.ubuntu.com/LaptopTestingTeam/SamsungR55

I upgraded from Dapper to Edgy with no problems.

After rebooting the boot sequence freezes on "Starting kernel event manager..."

My boot line is..

root (hd0, 1)
kernel /boot/vmlinuz-2.6.17-10-386 root=UUID=ce25e299-7cb4-4f9a-8115-e72bcd000674 ro vga=789 quiet splash
initrd /boot/initrd.img-2.6.17-10-386
savedefault
boot

Andrew Fenn (andrewfenn) wrote :

This is what I get in "non-splash" mode. I manually typed this so some parts may possibly have typing errors in.

[17179590.520000] NET: Registered protocol family 17!
[17179600.244000] BUG: soft lockup detected on CPU#0!
[17179600.244000] <c0121752> update_process_times+0x22.0x60 <c0106a26> timer_interrupt+0x46/0x90
[17179600.244000] <c0139ae3> handle_IRQ_event+0x33/0x60 <c0139b80> __do_IRQ+0x70/0xc0
[17179600.244000] <c0112238> hpet_readl+0x8/0x10 <c010c684> delay_hpet+0x24/0x30
[17179600.244000] <c01ccc09> __delay+0x9/0x10 <f8b79eae> ipw_bg_alive_start+0x5e/0xa0 [ipw3945]
[17179600.244000] <c0127591> run_workqueue+0x61/0xd0 <f8b79e50> ipw_bg_alive_start+0x0/0xa0 [ipw3945]
[17179600.244000] <c0127ac7> worker_thread+0x117/0x140 <c0115da0> default_wake_function+0x0/0x10
[17179600.244000] <c012a2d7> kthread+0xa7/0xe0 <c01279b0> worker_thread+0x0/0x140
[17179600.244000] <c012a230> kthread+0x0/0xe0 <c0101005> kernel_thread_helper+0x5/0x10

Andrew Fenn (andrewfenn) wrote :

I managed to boot in a few times last night. I have a bug report that was generated while I was upgrading (attached to this comment).

This bug seems to be because the something is going into deadlock while booting up.

If it doesn't deadlock while booting then I can use my computer as normal. It deadlocks at the same stage and shows the same information as I posted in my last comment.

towsonu2003 (towsonu2003) wrote :

Thanks for your bug report. how was the system upgraded apt-get/synaptic/adept/update-manager -c)? Could you please include the logs from /var/log/dist-upgrade/

Andrew Fenn (andrewfenn) wrote :

I used the official method...

gksu "update-manager -c"

Which I found from this post: http://www.ubuntuforums.org/showthread.php?t=286599

It takes about 4 or 5 times to actually boot in. Other times I receive the error posted above.

I included my logs in zip format.

towsonu2003 (towsonu2003) wrote :

thanks a lot for the fast reply :)

Changed in update-manager:
status: Needs Info → Unconfirmed
Andrew Fenn (andrewfenn) on 2006-11-22
Changed in linux-source-2.6.17:
assignee: nobody → ubuntu-laptop
Changed in linux-source-2.6.17:
assignee: ubuntu-laptop → nobody

Here are some pictures to illustrate what is going on. Sorry in advance for the bad lighting in the picture.

Here is a run down of what the pictures show.

before_broken.jpg - shows what the text says before it either stops booting or successfully boots to login.

broken.jpg - What is displayed when the laptop stops booting.

different_broken.jpg - This shows some more text which is above the text in broken.jpg

success.jpg - The text that is displayed before it successfully boots in.

Andrew Fenn (andrewfenn) wrote :

This bug has been confirmed by multiple people in the forum post located here:
http://www.ubuntuforums.org/showthread.php?p=1821189

Changed in nvidia-kernel-common:
status: Unconfirmed → Confirmed
Andrew Fenn (andrewfenn) on 2006-12-01
Changed in linux-source-2.6.17:
status: Unconfirmed → Confirmed

The 18 month support period for Edgy Eft 6.10 has reached its end of life. As a result, we are closing the linux-source-2.6.17 Edgy Eft kernel task. However, development has already began for the upcoming Intrepid Ibex 8.10 release. It would be helpful if you could test the upcoming release and verify if this is still an issue - http://www.ubuntu.com/testing . If the issue still exists, please update this report by changing the Status of the "linux" task from "Incomplete" to "New". We appreciate your patience and understanding as we make this transition. Thanks!

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers