From: Anish Mistry <mistry.7@osu.edu>
To: linux-acpi@vger.kernel.org
Subject: ASRock K7Upgrade-880 with S3
Date: Wed, 7 Jun 2006 00:20:32 -0400 [thread overview]
Message-ID: <200606070020.54592.mistry.7@osu.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 3070 bytes --]
I'm prefacing my question with email to the FreeBSD ACPI list as this
problem is to ultimately debug an ACPI problem in FreeBSD.
-- START FreeBSD Email --
I'm trying to get my desktop to STR (S3) and can't even get S3 to
semi-powered down state. 6.1-RELEASE-p1
I've updated the BIOS to the latest version. When I do an acpiconf -s
3 the suspend get all the way into the AcpiEnterSleepState function
and begins to write registers. The last line I see (with full ACPI
debugging enabled):
heregs-0708 HwRegisterWrite : ----Entry
Then the power light on the case starts to blink seeming to indicate
that it is in suspend, except I can still see output on the monitor
and the fans and harddrives are still running. Then when I press
the power button to try to bring the system back up it then displays:
heregs-0708 HwRegisterWrite : ----Exit
and then continues with a few more HwRegisterWrite and then exits the
AcpiEnterSleepState function and then does nothing. The system shows
no life of coming back. I then need to perform a cold boot, because
if I just hit the reset button the system doesn't restart to the
point where it gets to the BIOS screen.
My acpidump output is at:
http://am-productions.biz/docs/bigguy.asl
I've fixed the errors in the asl and tried using that, but it showed
the same problem.
http://am-productions.biz/docs/bigguy-fix.asl
dmesg:
http://am-productions.biz/docs/bigguy.dmesg
When I do an "acpidump -dt" I see the following message displayed:
acpidump: RSDT entry 2 (sig OEMB) is corrupt
Windows isn't installed on this system so I can't compare it with
that. I tried suspending with Knoppix (2006-06-01) and that worked a
bit better. It successfully shuts off the disks on suspend, but the
case fans and video card/monitor were still on. When you press the
power button again in knoppix it successfully brought the system back
to life. Getting it to the point of Knoppix would be a good start.
S1 in FreeBSD does work, but it doesn't shut anything down, so it's
not really useful.
hw.acpi.supported_sleep_state: S1 S3 S4 S5
hw.acpi.power_button_state: S5
hw.acpi.sleep_button_state: S1
hw.acpi.lid_switch_state: S3
hw.acpi.standby_state: S1
hw.acpi.suspend_state: S3
hw.acpi.sleep_delay: 5
hw.acpi.s4bios: 0
hw.acpi.verbose: 1
hw.acpi.reset_video: 0
hw.acpi.cpu.cx_supported: C1/0
hw.acpi.cpu.cx_lowest: C1
hw.acpi.cpu.cx_usage: 100.00%
debug.acpi.acpi_ca_version: 0x20041119
I've also tried CURRENT with ACPI-CA 20051021 with the same results.
-- END FreeBSD Email --
Now for the Linux part. Since Linux (Knoppix with kernel 2.6.17)
seems to get at least some of the suspend/resume right I'm trying to
figure out how to get it to display the full debug information to
compare with FreeBSD. I'm looking for how to do the following in
Linux:
http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/acpi-debug.html
Specifically the ACPI layer and level debugging mention at the end of
the page.
Thanks,
--
Anish Mistry
[-- Attachment #2: Type: application/pgp-signature, Size: 187 bytes --]
reply other threads:[~2006-06-07 4:20 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=200606070020.54592.mistry.7@osu.edu \
--to=mistry.7@osu.edu \
--cc=linux-acpi@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.