From: "Michael Frank" <mhf-jjFNsPSvq+iXDw4h08c5KA@public.gmane.org>
To: Pierre Ossman
<drzeus-list-p3sGCRWkH8CeZLLa646FqQ@public.gmane.org>,
acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: suspend-to-ram hangs on HP NX7010
Date: Sat, 19 Jun 2004 11:29:25 +0800 [thread overview]
Message-ID: <opr9tnzbol4evsfm@smtp.pacific.net.th> (raw)
In-Reply-To: <40D348EC.8030903-p3sGCRWkH8CeZLLa646FqQ@public.gmane.org>
On Fri, 18 Jun 2004 21:56:28 +0200, Pierre Ossman <drzeus-list-p3sGCRWkH8CeZLLa646FqQ@public.gmane.org> wrote:
> I've updated to linux 2.6.7 and applied the acpi patch for it. The
> behaviour is now a bit different.
> When trying to suspend (echo 3 > /proc/acpi/sleep) I now get the following:
>
> PM: Preparing system for suspend
> Stopping tasks:
> ===================================================================================================|
> PCI: Setting latency timer of device 0000:00:1d.7 to 64
> Could not suspend device 0000:00:1d.7: error -5
> ACPI: PCI interrupt 0000:00:1f.1[A] -> GSI 5 (level, low) -> IRQ 5
> ACPI: PCI interrupt 0000:00:1f.5[B] -> GSI 10 (level, low) -> IRQ 10
> PCI: Setting latency timer of device 0000:00:1f.5 to 64
> Restarting tasks... done
>
> Device 0000:00:1d.7 is the USB 2 controller. If I remove the ECHI module
> the behaviour is as previously (i.e. locks up).
> I don't know if this is a new bug in the EHCI module or if this is the
> source of all the problems on this machine. I do not know enough of how
> things work at that level to determine if the USB controller could
> prevent the standby.
> The BIOS doesn't have an option to turn of USB so I can't try it with
> the hardware disabled.
> Any ideas?
>
Oh, how nice, it looks like progress with the drivers when it dies wo one ;)
Seriously, please try again with init=/bin/bash and then add drivers
in multiuser mode until you find the culprit.
Also ACPI modules may have to be removed.
Regards
Michael
-------------------------------------------------------
This SF.Net email is sponsored by The 2004 JavaOne(SM) Conference
Learn from the experts at JavaOne(SM), Sun's Worldwide Java Developer
Conference, June 28 - July 1 at the Moscone Center in San Francisco, CA
REGISTER AND SAVE! http://java.sun.com/javaone/sf Priority Code NWMGYKND
next prev parent reply other threads:[~2004-06-19 3:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-09 12:06 suspend-to-ram hangs on HP NX7010 Pierre Ossman
[not found] ` <40C6FD44.7090606-p3sGCRWkH8CeZLLa646FqQ@public.gmane.org>
2004-06-14 22:58 ` Pierre Ossman
[not found] ` <40CE2DB0.9050208-p3sGCRWkH8CeZLLa646FqQ@public.gmane.org>
2004-06-16 12:36 ` Pierre Ossman
2004-06-18 19:56 ` Pierre Ossman
[not found] ` <40D348EC.8030903-p3sGCRWkH8CeZLLa646FqQ@public.gmane.org>
2004-06-19 3:29 ` Michael Frank [this message]
[not found] ` <opr9tnzbol4evsfm-TBR8pM7LtsqkE96DxU8f+dAkNl5+tjhE@public.gmane.org>
2004-06-19 7:23 ` Pierre Ossman
-- strict thread matches above, loose matches on Subject: below --
2004-06-09 12:33 Yu, Luming
[not found] ` <3ACA40606221794F80A5670F0AF15F8404991407-4yWAQGcml66Amxt+E6XRvg@public.gmane.org>
2004-06-09 15:09 ` Pierre Ossman
[not found] ` <40C72816.70908-p3sGCRWkH8CeZLLa646FqQ@public.gmane.org>
2004-06-09 15:25 ` Matthew Wilcox
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=opr9tnzbol4evsfm@smtp.pacific.net.th \
--to=mhf-jjfnspsvq+ixdw4h08c5ka@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=drzeus-list-p3sGCRWkH8CeZLLa646FqQ@public.gmane.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox