From: Andrew Morton <akpm@osdl.org>
To: Badari Pulavarty <pbadari@us.ibm.com>
Cc: Theodore Tso <tytso@mit.edu>, lkml <linux-kernel@vger.kernel.org>,
shaggy@us.ibm.com, ext4 <linux-ext4@vger.kernel.org>
Subject: Re: 2.6.19-rc1-mm1 (ext4 problem ?)
Date: Wed, 11 Oct 2006 09:56:39 -0700 [thread overview]
Message-ID: <20061011095639.ad8169f7.akpm@osdl.org> (raw)
In-Reply-To: <1160578934.1447.1.camel@dyn9047017100.beaverton.ibm.com>
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.
next parent reply other threads:[~2006-10-11 16:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[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 ` Andrew Morton [this message]
2006-10-11 17:08 ` 2.6.19-rc1-mm1 (ext4 problem ?) Badari Pulavarty
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=20061011095639.ad8169f7.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pbadari@us.ibm.com \
--cc=shaggy@us.ibm.com \
--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