From: Ducrot Bruno <ducrot-kk6yZipjEM5g9hUCZPvPmw@public.gmane.org>
To: Jan Rychter <jan-JAsPCFd0eodBDgjK7y7TUQ@public.gmane.org>
Cc: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: 8259A initialization oops after resume
Date: Tue, 17 Jun 2003 11:58:29 +0200 [thread overview]
Message-ID: <20030617095829.GX19556@poupinou.org> (raw)
In-Reply-To: <m2ptlf3vlb.fsf-dTJq59+VGzkkCw8IV3R6h0EOCMrvLtNR@public.gmane.org>
On Sun, Jun 15, 2003 at 02:00:00PM -0700, Jan Rychter wrote:
> People are getting a particular kind of oops after resuming from S4
> (implemented by swsusp). I'm posting this here, because the problem
> seems not to be specific to swsusp.
>
> Hopefully some people on this list will know how and why the 8259A needs
> to be initialized upon resuming from S4 and why it fails.
>
> The oops is reproducible -- one may do a number of suspend/resume cycles
> without it, but once it appears, it will reappear on every subsequent
> resume.
This was done but with S4Bios in mind, not with S4 via swsusp, and is
actually a (bad) hack, since that can not handle all cases.
A better way is done under 2.5.
Actually, there are many others troubles with
'echo 4 > /proc/acpi/sleep' and swsusp (fe, the devices are powered
down twice, via ACPI _and_ swsusp), which is bad. Better is
to use the swsusp own way to suspend, not via 'echo 4 > /proc/acpi/sleep'
which is IMO broken.
Under 2.5, the situation is different.
--
Ducrot Bruno
-- Which is worse: ignorance or apathy?
-- Don't know. Don't care.
-------------------------------------------------------
This SF.Net email is sponsored by: INetU
Attention Web Developers & Consultants: Become An INetU Hosting Partner.
Refer Dedicated Servers. We Manage Them. You Get 10% Monthly Commission!
INetU Dedicated Managed Hosting http://www.inetu.net/partner/index.php
next prev parent reply other threads:[~2003-06-17 9:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-15 21:00 8259A initialization oops after resume Jan Rychter
[not found] ` <m2ptlf3vlb.fsf-dTJq59+VGzkkCw8IV3R6h0EOCMrvLtNR@public.gmane.org>
2003-06-17 9:58 ` Ducrot Bruno [this message]
[not found] ` <20030617095829.GX19556-kk6yZipjEM5g9hUCZPvPmw@public.gmane.org>
2003-06-17 10:03 ` Nigel Cunningham
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=20030617095829.GX19556@poupinou.org \
--to=ducrot-kk6yzipjem5g9huczpvpmw@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=jan-JAsPCFd0eodBDgjK7y7TUQ@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