From: Andreas Steinmetz <ast@domdv.de>
To: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
Cc: Linux Kernel Mailinglist <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.15rc6: ide oops+panic
Date: Fri, 23 Dec 2005 21:07:04 +0100 [thread overview]
Message-ID: <43AC58E8.5000501@domdv.de> (raw)
In-Reply-To: <58cb370e0512230527l55810d0fif13d75f35723c1c3@mail.gmail.com>
Bartlomiej Zolnierkiewicz wrote:
> Driver OOPS-es on handling write barrier request (on finishing pre-flush)
> because REQ_STARTED flag is not set in __ide_end_request()
> but I don't see how this can happen, maybe something has changed
> in the block layer... Does 2.6.14 work for you?
>
> Does mounting ext3 with "barrier=0" option workaround the problem?
>
Testing the workaround now. I'll know for sure if the system survives
for the next few days.
--
Andreas Steinmetz SPAMmers use robotrap@domdv.de
next prev parent reply other threads:[~2005-12-23 20:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-22 21:55 2.6.15rc6: ide oops+panic Andreas Steinmetz
2005-12-23 13:27 ` Bartlomiej Zolnierkiewicz
2005-12-23 20:07 ` Andreas Steinmetz [this message]
2005-12-23 13:36 ` Andrew Morton
2005-12-23 20:07 ` Andreas Steinmetz
2005-12-26 23:17 ` Andreas Steinmetz
2005-12-26 23:27 ` Lee Revell
2005-12-26 23:31 ` Andreas Steinmetz
2005-12-31 23:13 ` Andreas Steinmetz
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=43AC58E8.5000501@domdv.de \
--to=ast@domdv.de \
--cc=bzolnier@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox