soft lock detected on CPU#0 (system crashed) after acpi sleep event problem
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Incomplete
|
Undecided
|
Unassigned | ||
linux-source-2.6.17 (Ubuntu) |
Won't Fix
|
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.
> 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?