From: Mads Paulin <paulin-/w0Os/Ss2Sh/SzgSGea1oA@public.gmane.org>
To: Nirmal Govind <nirmalg-8DAjSxpRXgY@public.gmane.org>
Cc: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: acpi and 2.6.0 kernel - S3 doesn't resume, S4 = infinite loop
Date: Mon, 22 Dec 2003 10:59:25 +0100 [thread overview]
Message-ID: <1072087165.2411.1.camel@M2400N> (raw)
In-Reply-To: <3FE6A4EF.6070002-8DAjSxpRXgY@public.gmane.org>
Hi,
I have just done exactly the same - just on a Mandrake 9.1 box
I tried this on an ASUS M2400N laptop also with the i855 chipset
The results were the same - only a hard reebot boot was working.
Regards,
Mads
On Mon, 2003-12-22 at 09:01, Nirmal Govind wrote:
> Hi.. I just compiled the 2.6.0 kernel that was released on Dec.
> 18th... I have ACPI support with all the options enabled. I tried
> suspending with S3 and it suspends fine (my power indicator starts
> flashing which means that it has suspended). But when I hit the
> power button, it does not resume properly, it tries to resume, the
> power indicator stops flashing which means that it thinks it's woken
> up, but all I see is a blank screen and hitting any of the keys
> doesn't seem to do anything. Only thing that works is a hard reboot.
> I'm running Mandrake 9.2 on a Fujitsu Lifebook S series (6120D) with
> an Intel 855 chipset graphics adapter. Please let me know if there's
> a way to get S3 to work well.
>
> Also, I tried suspend with S4 and that suspended fine but when I
> tried to resume, it booted up, showed me the resume messages saying
> it was resuming, then reboots! And this keeps happening at each
> reboot -- an infinite loop basically. I finally had to boot without
> the resume= option to get it to boot properly. Is this a bug?
>
> Thanks,
> nirmal
>
>
>
> -------------------------------------------------------
> This SF.net email is sponsored by: IBM Linux Tutorials.
> Become an expert in LINUX or just sharpen your skills. Sign up for IBM's
> Free Linux Tutorials. Learn everything from the bash shell to sys admin.
> Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click
> _______________________________________________
> Acpi-devel mailing list
> Acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
> https://lists.sourceforge.net/lists/listinfo/acpi-devel
-------------------------------------------------------
This SF.net email is sponsored by: IBM Linux Tutorials.
Become an expert in LINUX or just sharpen your skills. Sign up for IBM's
Free Linux Tutorials. Learn everything from the bash shell to sys admin.
Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click
next prev parent reply other threads:[~2003-12-22 9:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-22 8:01 acpi and 2.6.0 kernel - S3 doesn't resume, S4 = infinite loop Nirmal Govind
[not found] ` <3FE6A4EF.6070002-8DAjSxpRXgY@public.gmane.org>
2003-12-22 9:59 ` Mads Paulin [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-12-23 6:19 acpi and 2.6.0 kernel - S3 doesn't resume, S4 =infinite loop Yu, Luming
[not found] ` <3ACA40606221794F80A5670F0AF15F8401720C4F-SRlDPOYGfgogGBtAFL8yw7fspsVTdybXVpNB7YpNyf8@public.gmane.org>
2003-12-23 14:12 ` Nirmal Govind
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=1072087165.2411.1.camel@M2400N \
--to=paulin-/w0os/ss2sh/szgsgea1oa@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=nirmalg-8DAjSxpRXgY@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