From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Nigel Cunningham <ncunningham@clear.net.nz>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: How to avoid 'lost interrupt' messages post-resume?
Date: Thu, 01 Jan 2004 19:09:33 +1100 [thread overview]
Message-ID: <1072939036.768.39.camel@gaston> (raw)
In-Reply-To: <1072932095.6722.22.camel@laptop-linux>
On Thu, 2004-01-01 at 15:41, Nigel Cunningham wrote:
> Hi all.
>
> I have Software Suspend successfully running under 2.4.23 on a dual
> Celeron at OSDL, with only one outstanding issue: sometimes, after
> copying back the original kernel, I see 'hda: lost interrupt' and after
> another pause 'hdb:lost interrupt' messages. Apart from that, everything
> works fine (the machine has just suspended for the 46th time on the
> trot). I'm wanting to know if there's something I can do to fix this
> issue.
>
> Currently, prior to suspending, I set all irq affinities to CPU 0 (which
> does the suspend), save the state of the APICs and disable them and
> disable interrupts. At resume time, I again set the affinities to CPU 0
> and disable the APICs and interrupts prior to copying the original
> kernel back. After copying the original kernel back, I restore the
> original (pre-suspend) affinities and APIC settings & reenable
> interrupts (incomplete list). I'm no hardware expert, so feel free to
> tell me I'm doing something lame! Apart from these lost interrupts, all
> seems to work just fine.
You probably had a pending IDE request or something like that... IDE
in 2.4.x doesn't quite have the infrastructure to deal properly with
suspend & resume...
Ben.
next prev parent reply other threads:[~2004-01-01 8:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-01 4:41 How to avoid 'lost interrupt' messages post-resume? Nigel Cunningham
2004-01-01 8:09 ` Benjamin Herrenschmidt [this message]
2004-01-01 19:07 ` Nigel Cunningham
2004-01-01 22:59 ` Benjamin Herrenschmidt
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=1072939036.768.39.camel@gaston \
--to=benh@kernel.crashing.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ncunningham@clear.net.nz \
/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.