[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20061011095639.ad8169f7.akpm@osdl.org>
Date: Wed, 11 Oct 2006 09:56:39 -0700
From: Andrew Morton <akpm@...l.org>
To: Badari Pulavarty <pbadari@...ibm.com>
Cc: Theodore Tso <tytso@....edu>, lkml <linux-kernel@...r.kernel.org>,
shaggy@...ibm.com, ext4 <linux-ext4@...r.kernel.org>
Subject: Re: 2.6.19-rc1-mm1 (ext4 problem ?)
On Wed, 11 Oct 2006 08:02:14 -0700
Badari Pulavarty <pbadari@...ibm.com> wrote:
> On Tue, 2006-10-10 at 21:01 -0700, Andrew Morton wrote:
> >
> > > Andrew Morton wrote:
> > > > ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.19-rc1/2.6.19-rc1-mm1/
> > > >
> > > >
> > > > - Added the ext4 filesystem. Quick usage instructions:
> > > >
> > > > - Grab updated e2fsprogs from
> > > > ftp://ftp.kernel.org/pub/linux/kernel/people/tytso/e2fsprogs-interim/
> > > >
>
> ext4 did not survive my simple stress tests.
>
> I ran 4 copies of fsx on ext4dev filesystem (without extents) +
> 4 copies of fsx on ext4dev (with extents).
>
> Machine hung after running for few hours. There are 4 fsx sigsegv
> messages on the console and the last message on the console is
>
> do_IRQ: 0.62 No irq handler for vector
>
Quite a few people are hitting that - it's related to Eric's recent
IRQ/APIC-routing changes.
I don't know why that would cause fsx to get a sigsegv though.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists