From: Brannon Barrett Klopfer <bklopfer@stanford.edu>
To: linux-acpi@vger.kernel.org
Cc: acpi@linux.intel.com
Subject: hp dv8000t dead on resume from RAM
Date: Tue, 8 Aug 2006 10:15:11 -0700 [thread overview]
Message-ID: <1155057311.44d8c69f3f2fc@webmail.stanford.edu> (raw)
Howdy,
My hp dv8000t (core duo) is completely dead on resume from RAM (no caps
lock, sysrq, netconsole,
nothing). I've tried a recent (2.6.18-rc4) kernel running almost entirely
naked, so to speak (~990K) -- no support for:
SMP
preempt
modules
networking (+ enet drivers, unless running netconsole)
USB and SATA (not at same time; rootfs is either usb drive or SATA [ext2/3])
FireWire
cpufreq
framebuffer (vga=0)
audio
PCMCIA
IDE (for cdrom)
I've tried both native SATA (ahci) and legacy (ata_piix), but same result
w/both -- completely dead on resume from RAM. Blindly entering commands
does nothing, and running "$suspend ; $shutdown" does nothing either. I've
also tried with and without noapic, and a number of other kernel
paramaters, but nothing seems to work.
Be more than happy to try out patches, etc. to get this thing working.
Additionally, if someone could point me to that "beep on resume" patch,
that'd be great.
Some machine/debugging info (cpuinfo, messages, lspci, etc.) at:
http://www.stanford.edu/~bklopfer/wontsuspend/
Thanks,
Brannon Klopfer
next reply other threads:[~2006-08-08 17:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-08 17:15 Brannon Barrett Klopfer [this message]
2006-08-08 20:30 ` hp dv8000t dead on resume from RAM Rafael J. Wysocki
2006-08-09 18:01 ` Brannon Klopfer
2006-08-09 19:59 ` Rafael J. Wysocki
-- strict thread matches above, loose matches on Subject: below --
2006-08-10 18:29 Brannon Barrett Klopfer
2006-08-10 19:19 ` Rafael J. Wysocki
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=1155057311.44d8c69f3f2fc@webmail.stanford.edu \
--to=bklopfer@stanford.edu \
--cc=acpi@linux.intel.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox