From: Mathias Kretschmer <posting@blx4.net>
To: linux-kernel@vger.kernel.org
Subject: Asus A7N8X-E ACPI S3 resume hangs with 2.6.10 and 2.6.11-rc1
Date: Thu, 20 Jan 2005 08:42:35 -0800 [thread overview]
Message-ID: <41EFDF7B.40408@blx4.net> (raw)
[-- Attachment #1: Type: text/plain, Size: 448 bytes --]
Hi,
I haven't tried any earlier kernel. Problem exists with 2.6.10 and
2.6.11-rc1. System seems to suspend ok. When I press the power button
the fans turn on again, the IDE LED seems to flash a little and then
stays on permanently. System hangs. Display is still off, so I don't
know if there are any kernel messages. All I can do is hit the Reset
button. S1 works fine.
Under WinXP S3 works.
Does anyone see the same problem ?
Mathias
[-- Attachment #2: lspci_out.DEFANGED-13721 --]
[-- Type: application/DEFANGED-13721, Size: 2191 bytes --]
[-- Attachment #3: sanitizer.log --]
[-- Type: text/sanitizer-log, Size: 745 bytes --]
This message has been 'sanitized'. This means that potentially
dangerous content has been rewritten or removed. The following
log describes which actions were taken.
Sanitizer (start="1106239356"):
Part (pos="1132"):
SanitizeFile (filename="unnamed.txt", mimetype="text/plain"):
Match (names="unnamed.txt", rule="9"):
Enforced policy: accept
Part (pos="1737"):
SanitizeFile (filename="lspci.out", mimetype="text/plain"):
Match (rule="default"):
Enforced policy: defang
Replaced mime type with: application/DEFANGED-13721
Replaced file name with: lspci_out.DEFANGED-13721
Total modifications so far: 1
Anomy 0.0.0 : Sanitizer.pm
$Id: Sanitizer.pm,v 1.83 2004/03/23 12:33:48 bre Exp $
next reply other threads:[~2005-01-20 16:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-20 16:42 Mathias Kretschmer [this message]
2005-01-21 12:15 ` Asus A7N8X-E ACPI S3 resume hangs with 2.6.10 and 2.6.11-rc1 Pavel Machek
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=41EFDF7B.40408@blx4.net \
--to=posting@blx4.net \
--cc=linux-kernel@vger.kernel.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