From: Andrew Price <andy@andrewprice.me.uk>
To: Theodore Tso <tytso@mit.edu>
Cc: "Rafael J. Wysocki" <rjw@sisk.pl>,
Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>,
linux-kernel@vger.kernel.org
Subject: Re: BUG: using rootfstype=ext4 causes oops
Date: Thu, 16 Apr 2009 17:38:36 +0100 [thread overview]
Message-ID: <20090416163835.GB433@sucs.org> (raw)
In-Reply-To: <20090416145357.GM21586@mit.edu>
On Thu, Apr 16, 2009 at 10:53:57AM -0400, Theodore Tso wrote:
> OK, can you confirm that you tried using ext4 with either 2.6.29 or
> 2.6.28, and it was working previously? That would make it a
> regression which Rafael would track.
I've tested this with a local GFS2 mount (which uses barriers too) and
the same bug occurs. Apologies for making it seem like an ext4 bug. I'm
currently waiting for a kernel to build with Bartlomiej's patch so we'll
see how that goes.
> Also, I'd suggest sending Bartolmiej details about what IDE controller
> you have (the dmesg during a boot under ext3 or ext4 w/ barrier=0
> would also be useful), so he can track it down. It might be specific
> to a particular IDE controller/device, and not be a generalized IDE
> problem, after all.
00:0f.1 IDE interface [0101]: VIA Technologies, Inc. VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE [1106:0571] (rev 06) (prog-if 8a [Master SecP PriP])
Subsystem: ASUSTeK Computer Inc. A7V600/K8V-X/A8V Deluxe motherboard [1043:80ed]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 32
Interrupt: pin A routed to IRQ 20
Region 0: [virtual] Memory at 000001f0 (32-bit, non-prefetchable) [size=8]
Region 1: [virtual] Memory at 000003f0 (type 3, non-prefetchable) [size=1]
Region 2: [virtual] Memory at 00000170 (32-bit, non-prefetchable) [size=8]
Region 3: [virtual] Memory at 00000370 (type 3, non-prefetchable) [size=1]
Region 4: I/O ports at fc00 [size=16]
Capabilities: [c0] Power Management version 2
Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
Kernel driver in use: VIA_IDE
> Anyway, I'll hand this bug off to Raefael's and/or Bartlomiej's very
> capable hands, since I suspect you could also reproduce this using
> rootfstype=ext3 rootfsflags=barrier=1, and that this is purely an IDE
> driver problem.
Thanks Ted.
> P.S. Where in the documentation file do we have the mount option as
> "barriers=0". I went looking for it, and I couldn't find it. What I
> see is:
> <snip>
Further up in that file in the last paragraph of the 'Quick usage
instructions' it says:
[...]
'-o barriers=[0|1]' mount option for both ext3 and ext4 filesystems
[...]
(I searched the file for barrier and it was the first chunk of text
which matched.)
--
Andrew Price
next prev parent reply other threads:[~2009-04-16 16:38 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-15 20:59 Andrew Price
2009-04-16 4:19 ` Theodore Tso
2009-04-16 10:47 ` Andrew Price
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 [this message]
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=20090416163835.GB433@sucs.org \
--to=andy@andrewprice.me.uk \
--cc=bzolnier@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rjw@sisk.pl \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome