From: Ben B <kernel@bb.cactii.net>
To: Todd Pytel <tppytel@sophrosune.org>
Cc: linux-acpi@vger.kernel.org
Subject: Re: Hang on S3 resume with Acer TravelMate 222X
Date: Tue, 5 Sep 2006 08:16:08 +0200 [thread overview]
Message-ID: <20060905061608.GA16903@cactii.net> (raw)
In-Reply-To: <1157424745.19942.2.camel@timaeus.sophrosune.org>
Todd Pytel <tppytel@sophrosune.org> uttered the following thing:
> Please? Anybody? Just some Google fodder or pointers on how to generate
> better debugging information for the list would be greatly appreciated.
Try unloading various modules before suspend. On many machines, at least
the usb host drivers need to be unloaded.
Video's another possibility. Look at vbetool, it might be able to
restore video and get things on track again.
Also, do your suspend from a shell script, and have this script log
debugging info after resume (remembering to sync in case you have to
hard boot).
Ben
next prev parent reply other threads:[~2006-09-05 6:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-31 23:29 Hang on S3 resume with Acer TravelMate 222X Todd Pytel
2006-09-05 2:52 ` Todd Pytel
2006-09-05 6:16 ` Ben B [this message]
2006-09-05 6:41 ` Todd Pytel
2006-09-05 6:28 ` Yu Luming
2006-09-05 6:48 ` Todd Pytel
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=20060905061608.GA16903@cactii.net \
--to=kernel@bb.cactii.net \
--cc=linux-acpi@vger.kernel.org \
--cc=tppytel@sophrosune.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