[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <453406F0.5020803@sandall.us>
Date: Mon, 16 Oct 2006 15:25:52 -0700
From: Eric Sandall <eric@...dall.us>
To: Pavel Machek <pavel@....cz>
CC: LKML <linux-kernel@...r.kernel.org>
Subject: Re: suspend broken in 2.6.18.1
Pavel Machek wrote:
> Hi!
>
>> After updating from 2.6.17.13 to 2.6.18 (using `make oldconfig`),
>> suspend no longer suspends my laptop (Dell Inspiron 5100).
>>
>> # s2ram -f
>> Switching from vt7 to vt1
>> s2ram_do: Invalid argument
>> switching back to vt7
>>
>> The screen blanks, but then comes back up after a few seconds. This
>> happens both with and without X running.
>>
>> I've attached the output of `lspci -vvv` and my
>> /usr/src/linux-2.6.18/.config for more information. Please let me know
>> if there are any patches to try or if more information is required.
>
> Relevant part of dmesg after failed attempt is neccessary... and you
> can probably read it yourself and figure what is wrong. I'd guess some
> device just failed to suspend... rmmod it.
(This is now with 2.6.18.1)
Stopping tasks: =====================================================|
ACPI: PCI interrupt for device 0000:02:04.0 disabled
ACPI: PCI interrupt for device 0000:00:1f.5 disabled
ACPI: PCI interrupt for device 0000:00:1d.7 disabled
ACPI: PCI interrupt for device 0000:00:1d.2 disabled
ACPI: PCI interrupt for device 0000:00:1d.1 disabled
ACPI: PCI interrupt for device 0000:00:1d.0 disabled
Class driver suspend failed for cpu0
Could not power down device firmware: error -22
Some devices failed to power down
I've attached my entire dmesg as well.
-sandalle
--
Eric Sandall | Source Mage GNU/Linux Developer
eric@...dall.us | http://www.sourcemage.org/
http://eric.sandall.us/ | SysAdmin @ Shock Physics @ WSU
http://counter.li.org/ #196285 | http://www.shock.wsu.edu/
View attachment "dmesg.log" of type "text/plain" (15496 bytes)
Powered by blists - more mailing lists