From: Sachin Sant <sachinp@in.ibm.com>
To: Theodore Tso <tytso@mit.edu>
Cc: linux-ext4@vger.kernel.org,
"Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>
Subject: Re: EXT4: kernel BUG at fs/jbd2/commit.c:533!
Date: Tue, 08 Sep 2009 19:51:06 +0530 [thread overview]
Message-ID: <4AA66852.8040009@in.ibm.com> (raw)
In-Reply-To: <20090902120958.GA16415@mit.edu>
Theodore Tso wrote:
> On Wed, Sep 02, 2009 at 04:48:46PM +0530, Sachin Sant wrote:
>
>> While executing fsstress against ext4 with 2.6.31-rc8 on a
>> powerpc box, ran into the following Bug.
>>
>> ------------[ cut here ]------------
>> cpu 0x0: Vector: 700 (Program Check) at [c0000000f3ae3970]
>> pc: c000000000280f28: .jbd2_journal_commit_transaction+0x8ac/0x1bfc
>> lr: c000000000280e58: .jbd2_journal_commit_transaction+0x7dc/0x1bfc
>> sp: c0000000f3ae3bf0
>> msr: 8000000000029032
>> current = 0xc0000000f315c7d0
>> paca = 0xc000000000b62600
>> pid = 23139, comm = kjournald2
>> kernel BUG at fs/jbd2/commit.c:533!
>>
Let me know if there is any thing i could try to help
find a solution for this problem. After increasing the
nproc value, i am able to consistently recreate this issue.
Thanks
-Sachin
--
---------------------------------
Sachin Sant
IBM Linux Technology Center
India Systems and Technology Labs
Bangalore, India
---------------------------------
next prev parent reply other threads:[~2009-09-08 14:21 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-02 11:18 EXT4: kernel BUG at fs/jbd2/commit.c:533! Sachin Sant
2009-09-02 12:09 ` Theodore Tso
2009-09-02 21:07 ` Andreas Dilger
2009-09-02 22:30 ` Theodore Tso
2009-09-03 4:01 ` Sachin Sant
2009-09-03 7:36 ` Sachin Sant
2009-09-04 5:00 ` Sachin Sant
2009-09-04 8:02 ` Aneesh Kumar K.V
2009-09-04 8:23 ` Sachin Sant
2009-09-08 14:21 ` Sachin Sant [this message]
2009-09-10 8:03 ` Aneesh Kumar K.V
2009-09-10 8:20 ` Sachin Sant
2009-09-18 9:07 ` Sachin Sant
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=4AA66852.8040009@in.ibm.com \
--to=sachinp@in.ibm.com \
--cc=aneesh.kumar@linux.vnet.ibm.com \
--cc=linux-ext4@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).