mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Mikulas Patocka <mikulas@artax.karlin.mff.cuni.cz>
Cc: linux-kernel@vger.kernel.org
Subject: Re: APM crashes when IO is going on
Date: Fri, 21 Mar 2008 22:15:54 +0100	[thread overview]
Message-ID: <200803212215.54854.rjw@sisk.pl> (raw)
In-Reply-To: <Pine.LNX.4.64.0803212055550.6726@artax.karlin.mff.cuni.cz>

On Friday, 21 of March 2008, Mikulas Patocka wrote:
> Hi
> 
> > > > > I have an old notebook with APM and I am experiencing occasional APMD 
> > > > > lockups after resume, with kernels 2.6.25rc1 snd 2.6.25rc3. They didn't 
> > > > > happen with 2.6.24 or before.
> > > > > 
> > > > > The bug happens about once a week or so.
> > > > > 
> > > > > If you have any idea how to debug it, you can send me a test code.
> > > > 
> > > > It is possible that the bug was fixed in -rc4.  Can you please test -rc6 and
> > > > see if it's still present?
> > > > 
> > > > Thanks,
> > > > Rafael
> > > 
> > > I'm now running on -rc6, so I'll see (it takes some days for the bug to 
> > > appear). Where is that patch that went to -rc4 and that may fix it?
> > 
> > http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=7a8d37a37380e2b1500592d40b7ec384dbebe7a0
> > 
> > Thanks,
> > Rafael
> 
> I found another problem --- present in 2.6.23.1, 2.6.25rc3, 2.6.25rc6
> 
> --- when I run three threads concurrently reading raw disk partition and 
> suspend, I get 100% reproducible failure. (with one thread running it 
> usually succeeds, sometimes fail)

Are they userland threads or kernel threads?

> Either the on-going I/O will jam BIOS and I need to remove power to 
> continue.
> 
> Or the machine suspends, wakes up and reports "hda: lost interrupt" 
> (2.6.23.1 was able to recover from this condition, 2.6.25rc3,6 does not 
> recover and it is not able to send any more disk IOs).
> 
> How is suspending disk IO supposed to work?

That depends on the driver, if I understand your question correctly.

> And why it doesn't?

Hard to tell.  You didn't provide much information ...

Thanks,
Rafael

  reply	other threads:[~2008-03-21 21:16 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-19 15:15 APM lockups since 2.6.25 Mikulas Patocka
2008-03-20 10:31 ` Rafael J. Wysocki
2008-03-21  0:00   ` Mikulas Patocka
2008-03-21  0:27     ` Rafael J. Wysocki
2008-03-21 20:01       ` APM crashes when IO is going on Mikulas Patocka
2008-03-21 21:15         ` Rafael J. Wysocki [this message]
2008-03-21 21:17           ` Mikulas Patocka
2008-03-21 21:45             ` Rafael J. Wysocki
2008-03-21 22:49               ` Mikulas Patocka
2008-03-21 22:51                 ` Rafael J. Wysocki
2008-03-22  0:29                   ` Mikulas Patocka
2008-03-25  8:49             ` Pavel Machek
2008-03-25  8:46         ` Pavel Machek
2008-04-16 20:42       ` APM lockups since 2.6.25 Mikulas Patocka
2008-04-16 20:45         ` Mikulas Patocka
2008-04-17  0:14           ` Rafael J. Wysocki
2008-04-22 13:00             ` Pavel Machek

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=200803212215.54854.rjw@sisk.pl \
    --to=rjw@sisk.pl \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mikulas@artax.karlin.mff.cuni.cz \
    /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

Powered by JetHome