From: Andrew Price <andy@andrewprice.me.uk>
To: Theodore Tso <tytso@mit.edu>
Cc: linux-kernel@vger.kernel.org
Subject: Re: BUG: using rootfstype=ext4 causes oops
Date: Thu, 16 Apr 2009 11:47:58 +0100 [thread overview]
Message-ID: <20090416104758.GA433@sucs.org> (raw)
In-Reply-To: <20090416041945.GK21586@mit.edu>
On Thu, Apr 16, 2009 at 12:19:45AM -0400, Theodore Tso wrote:
> On Wed, Apr 15, 2009 at 09:59:26PM +0100, Andrew Price wrote:
> > Using rootfstype=ext4 with today's linux-2.6.git causes a panic on my
> > two amd64 machines (haven't tested it on any others).
>
> Hmm, git commit id, please?
commit 3ee8da87ba6151ec91b2b8bbd27633bb248ea0d5
Merge: a2c252e 9dd175f
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date: Wed Apr 15 09:11:11 2009 -0700
> The stack traces are in the IDE interrupt
> handler, so it seems surprising that ext4 would trigger it but ext3
> would not. Have you tried ext4 on any earlier kernel?
It happened with linux-2.6.git kernels earlier in the week when I
started trying rootfstype=ext4 but I haven't tried properly bisecting it
yet.
> The main difference I can think of is that ext4 enables barriers by
> default; maybe that's the case of the IDE breakage? Can you try
> booting with the boot command option "rootfsflags=barrier=0" as well
> as "rootfstype=ext4", and see if that helps?
I added rootflags=barrier=0 ...
(aside: the ext4 docs say the param is "barriers" with an s; it isn't).
... and it doesn't panic.
> If so, it's a bug in the IDE code in that it's not handling barriers
> correctly.
Bingo.
--
Andrew Price
next prev parent reply other threads:[~2009-04-16 10:48 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-15 20:59 BUG: using rootfstype=ext4 causes oops Andrew Price
2009-04-16 4:19 ` Theodore Tso
2009-04-16 10:47 ` Andrew Price [this message]
2009-04-16 14:53 ` Theodore Tso
2009-04-16 16:02 ` Bartlomiej Zolnierkiewicz
2009-04-16 17:05 ` Andrew Price
2009-04-16 19:22 ` Bartlomiej Zolnierkiewicz
2009-04-16 16:38 ` Andrew Price
2009-04-16 16:55 ` Theodore Tso
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=20090416104758.GA433@sucs.org \
--to=andy@andrewprice.me.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=tytso@mit.edu \
/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.