public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Shaohua Li <shaohua.li-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
To: acpi-dev <acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>
Subject: S3 test
Date: Tue, 12 Jul 2005 17:22:29 +0800	[thread overview]
Message-ID: <1121160149.20699.6.camel@linux-hp.sh.intel.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 548 bytes --]

Hi,
Somebody in the list suggested we could test S3 with a kernel which
doesn't touch any device. Considering there are many broken drivers
(especially hard disk driver in some systems), this sounds like a good
method to narrow down S3 bugs. For those who want to try it, you can
make a kernel without any driver support, and make attached file as your
initrd, and see if S3 works. The attached initramfs doesn't touch any
device and just does something like below:

echo 'mem' >/sys/power/state
echo xxxxxxxx
while true; do done


Thanks,
Shaohua

[-- Attachment #2: initramfs.cpio.gz --]
[-- Type: application/x-cpio-compressed, Size: 32055 bytes --]

             reply	other threads:[~2005-07-12  9:22 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-12  9:22 Shaohua Li [this message]
     [not found] ` <1121160149.20699.6.camel-ECwVeV2eNyQD0+JXs3kMbRL4W9x8LtSr@public.gmane.org>
2005-07-12 13:08   ` S3 test Pavel Machek
2005-07-15 13:36   ` Frank
     [not found]     ` <200507151536.21857.hugelmopf-S0/GAf8tV78@public.gmane.org>
2005-07-15 14:29       ` Bernd Schubert
  -- strict thread matches above, loose matches on Subject: below --
2005-07-18  2:36 Li, Shaohua
     [not found] ` <16A54BF5D6E14E4D916CE26C9AD3057502B653B0-4yWAQGcml66iAffOGbnezLfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2005-07-20 18:59   ` Frank
     [not found]     ` <200507202059.28860.hugelmopf-S0/GAf8tV78@public.gmane.org>
2005-07-21 10:55       ` Sebastian Kärgel
2005-07-25  1:55       ` Shaohua Li

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=1121160149.20699.6.camel@linux-hp.sh.intel.com \
    --to=shaohua.li-ral2jqcrhueavxtiumwx3w@public.gmane.org \
    --cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.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