lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Mon, 27 Nov 2006 12:35:01 +0100
From:	Pavel Machek <pavel@....cz>
To:	Eric Sandall <eric@...dall.us>
Cc:	LKML <linux-kernel@...r.kernel.org>
Subject: Re: suspend broken in 2.6.18.1

On Mon 2006-10-16 15:25:52, Eric Sandall wrote:
> 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.
Try with 2.6.19-rcX.
								Pavel


-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists