soft lock detected on CPU#0 (system crashed) after acpi sleep event problem

Bug #69086 reported by manuel fernandez on 2006-10-29
4
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Undecided
Unassigned
linux-source-2.6.17 (Ubuntu)
Undecided
Unassigned

Bug Description

edgy
boot sequence is stopped even in rescue mode.
when loading manual drivers it reports

BUG: soft lock detected on CPU#0

The system is then stuck and no longer responds. This bug is terrible because the machine cannot be accessed even in single mode.

How the problem began: The computer was updated from dapper to edgy. It worked reasonably well although the power manager did not perform the expected operations, in particular for lid closed (dell inspiron 6400, duo core). System went to sleep but did not wake up again. A hard reset allowed to restart the system.
Then loaded kpowersave battery monitor. Closed lid and system did not wake. But upon hard switch reboot could no longer boot as mentioned at the beginning.

towsonu2003 (towsonu2003) wrote :

> boot sequence is stopped even in rescue mode.
> when loading manual drivers it reports
> BUG: soft lock detected on CPU#0

does it do this after every boot since you had the closed lid problem?

Yes it does. Tried four or five times either in normal boot or rescue mode
and it got stuck at the same point.

The way I managed to stop it was to boot with older kernel 2.6.15.27. Then
removed the package kpowersave. Restarted the computer with the new kernel
2.6.17.10 and could then boot.

m. fernández guasti
<email address hidden>
Universidad Autónoma Metropolitana - Unidad Iztapalapa

---------- Original Message -----------
From: towsonu2003 <email address hidden>
To: <email address hidden>
Sent: Mon, 30 Oct 2006 05:44:06 -0000
Subject: [Bug 69086] Re: system locked up on boot!

> > boot sequence is stopped even in rescue mode.
> > when loading manual drivers it reports
> > BUG: soft lock detected on CPU#0
>
> does it do this after every boot since you had the closed lid problem?
>
> ** Changed in: Ubuntu
> Sourcepackagename: None => linux-source-2.6.17
>
> ** Summary changed:
>
> - system locked up on boot!
> + soft lock detected on CPU#0 (system crashed) after acpi sleep
> event problem
>
> --
> soft lock detected on CPU#0 (system crashed) after acpi sleep event
problem
> https://launchpad.net/bugs/69086
------- End of Original Message -------

Mikael Nilsson (mini) wrote :

Do you have a intel wireless 3945 card?

In that case, this is probably a duplicate of bug 63418.

Workaround: *enable* wireless during booting.

Yes, an ipw3945 intel wireless card.
I tried to boot with wireless off and indeed the system is locked. Turned it
on and rebooted and it worked all right.

The bug is then duplicate of 63418.

However, as mentioned in that thread, the problem not only arises due to the
3945 driver.

m. fernández guasti
<email address hidden>
Universidad Autónoma Metropolitana - Unidad Iztapalapa

---------- Original Message -----------
From: Mikael Nilsson <email address hidden>
To: <email address hidden>
Sent: Wed, 08 Nov 2006 00:49:06 -0000
Subject: [Bug 69086] Re: soft lock detected on CPU#0 (system crashed) after
acpi sleep event problem

> Do you have a intel wireless 3945 card?
>
> In that case, this is probably a duplicate of bug 63418.
>
> Workaround: *enable* wireless during booting.
>
> --
> soft lock detected on CPU#0 (system crashed) after acpi sleep event problem
> https://launchpad.net/bugs/69086
------- End of Original Message -------

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