* Re: 2.6.19-rc1-mm1 (ext4 problem ?)
[not found] ` <1160578934.1447.1.camel@dyn9047017100.beaverton.ibm.com>
@ 2006-10-11 16:56 ` Andrew Morton
2006-10-11 17:08 ` Badari Pulavarty
0 siblings, 1 reply; 2+ messages in thread
From: Andrew Morton @ 2006-10-11 16:56 UTC (permalink / raw)
To: Badari Pulavarty; +Cc: Theodore Tso, lkml, shaggy, ext4
On Wed, 11 Oct 2006 08:02:14 -0700
Badari Pulavarty <pbadari@us.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.
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: 2.6.19-rc1-mm1 (ext4 problem ?)
2006-10-11 16:56 ` 2.6.19-rc1-mm1 (ext4 problem ?) Andrew Morton
@ 2006-10-11 17:08 ` Badari Pulavarty
0 siblings, 0 replies; 2+ messages in thread
From: Badari Pulavarty @ 2006-10-11 17:08 UTC (permalink / raw)
To: Andrew Morton; +Cc: Theodore Tso, lkml, shaggy, ext4
On Wed, 2006-10-11 at 09:56 -0700, Andrew Morton wrote:
> On Wed, 11 Oct 2006 08:02:14 -0700
> Badari Pulavarty <pbadari@us.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.
I don't think they are related. Hopefully once we figure out IRQ
problem, we can try to track down fsx problems.
Thanks,
Badari
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2006-10-11 17:08 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
[not found] <20061010000928.9d2d519a.akpm@osdl.org>
[not found] ` <452C616D.7040701@us.ibm.com>
[not found] ` <20061010210133.dda19d4c.akpm@osdl.org>
[not found] ` <1160578934.1447.1.camel@dyn9047017100.beaverton.ibm.com>
2006-10-11 16:56 ` 2.6.19-rc1-mm1 (ext4 problem ?) Andrew Morton
2006-10-11 17:08 ` Badari Pulavarty
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox