From: 宾西蒙 <binximeng@gmail.com>
To: linux-kernel@vger.kernel.org
Cc: BinXimeng@gmail.com
Subject: [pm] resume from s3 oops? (last checked on rc6)
Date: Wed, 12 May 2010 15:59:32 +0200 [thread overview]
Message-ID: <1273672772.7284.32.camel@eee51> (raw)
Hi lkml,
I'm trying to get suspend to ram working on a opensuse 11.2. (The box is
unfortunately not connected to the Internet). So far I've tried with
distribution's kernel 2.6.31.12 & now with 2.6.34-rc6 (already
downloaded a copy of rc7 and will try it today)
It suspends fine with "echo mem > /sys/power/state", resumes not though.
The caps lock and scroll lock leds are flashing, I think this relates to
a kernel oops? However, screen remains black.
I did this from a "bare" system with vga=0 init=/bin/zsh command line.
When using acpi_sleep=s3_beep, I get 3 high + 1 low beep right after
wake-up. With acpi_sleep=s3_mode, I don't get the blinking keyboard
leds, but the resume doesn't work either, especially do I believe it is
not only a "black screen", otherwise I should be able to toggle the
keyboard leds after resume.
The board has a debug led connected to an AMI bios, which shows "24" --
manual claims this to mean "Uncompress and initialize any platform
specific BIOS modules. GPNV is initialized at this checkpoint." Don't
know if this has any meaning and not just bogus though.
probably unrelated, s1&s4 work.
The hardware in question: ASRock Intel-X58 Extreme3 motherboard, AMD
HD3450 graphics.
any debug help/suggestions, things to try/look at to track this down
that you guys could give me?
cheers, ximeng
next reply other threads:[~2010-05-12 13:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-12 13:59 宾西蒙 [this message]
2010-05-12 22:32 ` [pm] resume from s3 oops? (last checked on rc6) 宾西蒙
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=1273672772.7284.32.camel@eee51 \
--to=binximeng@gmail.com \
--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;
as well as URLs for NNTP newsgroup(s).