From: Lee Revell <rlrevell@joe-job.com>
To: Folkert van Heusden <folkert@vanheusden.com>
Cc: Charles-Edouard Ruault <ce@ruault.com>, linux-kernel@vger.kernel.org
Subject: Re: [BUG] kernel 2.6.15.4: soft lockup detected on CPU#0!
Date: Wed, 15 Feb 2006 13:19:52 -0500 [thread overview]
Message-ID: <1140027592.2733.38.camel@mindpipe> (raw)
In-Reply-To: <20060215150710.GN30182@vanheusden.com>
On Wed, 2006-02-15 at 16:07 +0100, Folkert van Heusden wrote:
>
> So it seems it switches back to pio somewhere in time.
>
> But on the other hand: shouldn't pio run ok as well without softlockup
> errors?
AFAICT in PIO mode if a huge IO request is submitted and/or the device
is slow to respond there's nothing to prevent us spending a long time in
the IDE driver.
IIRC this can't be made preemptible due to data corruption issues on
some hardware. Maybe we should touch the watchdog in there.
Lee
next prev parent reply other threads:[~2006-02-15 18:19 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-12 18:50 [BUG] kernel 2.6.15.4: soft lockup detected on CPU#0! Charles-Edouard Ruault
2006-02-14 11:41 ` Folkert van Heusden
2006-02-14 16:32 ` Lee Revell
2006-02-15 15:07 ` Folkert van Heusden
2006-02-15 18:19 ` Lee Revell [this message]
2006-02-16 1:38 ` Alan Cox
2006-02-17 22:56 ` Lee Revell
2006-02-16 2:51 ` Andrew Morton
2006-02-16 9:44 ` Charles-Edouard Ruault
2006-02-16 10:36 ` Folkert van Heusden
2006-02-16 10:46 ` Andrew Morton
2006-02-16 11:18 ` Charles-Edouard Ruault
2006-02-16 12:57 ` Alan Cox
2006-02-16 13:33 ` Bartlomiej Zolnierkiewicz
2006-02-16 20:20 ` Andrew Morton
2006-02-17 11:47 ` Bartlomiej Zolnierkiewicz
2006-02-17 13:08 ` [patch] timer-irq-driven soft-watchdog, cleanups Ingo Molnar
2006-02-17 14:46 ` Bartlomiej Zolnierkiewicz
2006-02-17 19:52 ` Ingo Molnar
2006-02-17 20:11 ` Ingo Molnar
2006-02-17 22:15 ` Bartlomiej Zolnierkiewicz
2006-03-13 14:48 ` Charles-Edouard Ruault
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=1140027592.2733.38.camel@mindpipe \
--to=rlrevell@joe-job.com \
--cc=ce@ruault.com \
--cc=folkert@vanheusden.com \
--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 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.