From: Nigel Cunningham <ncunningham@clear.net.nz>
To: benh@kernel.crashing.org
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: How to avoid 'lost interrupt' messages post-resume?
Date: Fri, 02 Jan 2004 08:07:03 +1300 [thread overview]
Message-ID: <1072984022.22058.3.camel@laptop-linux> (raw)
In-Reply-To: <1072939036.768.39.camel@gaston>
Thanks for the reply.
I'll look into that area some more.
Regards,
Nigel
On Thu, 2004-01-01 at 21:09, Benjamin Herrenschmidt wrote:
> 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...
--
My work on Software Suspend is graciously brought to you by
LinuxFund.org.
next prev parent reply other threads:[~2004-01-01 19:08 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
2004-01-01 19:07 ` Nigel Cunningham [this message]
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=1072984022.22058.3.camel@laptop-linux \
--to=ncunningham@clear.net.nz \
--cc=benh@kernel.crashing.org \
--cc=linux-kernel@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