[Bug 20979] suspend fails on Acer TM290 if power adapter is pulled out during suspend or lid closed- acpi or kernel bug

[bugzilla-daemon at bugzilla.ubuntu.com]

Please do not reply to this email.  You can add comments at
http://bugzilla.ubuntu.com/show_bug.cgi?id=20979
Ubuntu | linux





------- Additional Comments From lists at wikidev.net  2005-12-14 19:15 UTC -------
Last time this happened was this morning with the dapper 2.6.15-8-686 kernel.
The supend was to disk, and i removed the power adapter about halfway between
pressing the suspend button and poweroff. The power led did blink the same way
as usual in supended state. When i pressed a keyboard button to switch the
machine back on it spun up the disk, but then stopped with the screen powered
off and not responding to sysrq. Pressing the lid switch in this situation did
not help, neither did adjusting the screen brightness or attempting to switch to
a console.

I experienced the same bug more often with the lid switch, getting 100% failure
when i closed the lid before the suspend had finished. The symptoms were just
the same with failure on resume ending in a hard hang. I'll see if i can get
some message out of a crash later tonight. There's nothing showing up in the
syslog- no special messages on shutdown, and nothing at all from the resume,
suggesting that / might not have been mounted yet. The failures with
supend-to-disk were also on resume, but i'm not sure if it picked up the mem and
hung then or just ignored the image. I'll check later tonight.

My speculations:
Both power and lid trigger acpi actions which usually involve disk access. No
idea if those actions are completely suppressed kernel-side or if it's just
keyboard and other inputs that are disabled plus freezing running processes at
the start of the suspend. At least for suspend-to-disk interrups can't be
completely disabled, so maybe acpi can sneak in somehow?

-- 
Configure bugmail: http://bugzilla.ubuntu.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.