lkml.org 
[lkml]   [2009]   [Apr]   [16]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: BUG: using rootfstype=ext4 causes oops
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


\
 
 \ /
  Last update: 2009-04-16 12:51    [W:0.059 / U:0.404 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site