From: Sachin Sant <sachinp@in.ibm.com>
To: linux-ext4@vger.kernel.org
Subject: EXT4: kernel BUG at fs/jbd2/commit.c:533!
Date: Wed, 02 Sep 2009 16:48:46 +0530 [thread overview]
Message-ID: <4A9E5496.8050909@in.ibm.com> (raw)
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!
enter ? for help
[c0000000f3ae3dd0] c000000000289c60 .kjournald2+0x198/0x46c
[c0000000f3ae3ed0] c0000000000a86a0 .kthread+0xac/0xb8
[c0000000f3ae3f90] c00000000002ab3c .kernel_thread+0x54/0x70
0:mon>
Ext4 FS was created and mounted using :
/usr/local/e2fsprogs/sbin/mkfs.ext4 -b 4096 /dev/sda4
mount -t ext4 -o errors=panic,data=journal /dev/sda4 /mnt/tmp/
Register information from xmon debugger :
0:mon> r
R00 = 0000000000000001 R16 = c0000000334e0160
R01 = c0000000f3ae3bf0 R17 = 0000000000000000
R02 = c000000000a6f1e8 R18 = 0000000000000000
R03 = c0000000e87c9024 R19 = 0000000000000001
R04 = c0000000334e0100 R20 = 0000000000000001
R05 = 0000000000000409 R21 = 0000000000000409
R06 = 0000000000000000 R22 = c0000000f3ae3c78
R07 = c0000000f315c7d0 R23 = 0000000000000000
R08 = c000000000b62600 R24 = c0000000e87c9000
R09 = 00000000000000a0 R25 = c0000000334e0170
R10 = c0000000f3ae0080 R26 = c0000000334e0100
R11 = 0000000100051657 R27 = c0000000334e0150
R12 = 0000000024000088 R28 = c0000000f3ae3c78
R13 = c000000000b62600 R29 = c0000000f315c7d0
R14 = c0000000008325c8 R30 = c0000000009ec158
R15 = c0000000e87c939c R31 = 0000000000000000
pc = c000000000280f28 .jbd2_journal_commit_transaction+0x8ac/0x1bfc
lr = c000000000280e58 .jbd2_journal_commit_transaction+0x7dc/0x1bfc
msr = 8000000000029032 cr = 24000084
ctr = 0000000000000000 xer = 0000000020000001 trap = 700
0:mon>
e2fsprog utility version is :
# /usr/local/e2fsprogs/sbin/mkfs.ext4 -V
mke2fs 1.41.6 (30-May-2009)
Using EXT2FS Library version 1.41.6
Let me know if i can provide any other information.
Thanks
-Sachin
--
---------------------------------
Sachin Sant
IBM Linux Technology Center
India Systems and Technology Labs
Bangalore, India
---------------------------------
next reply other threads:[~2009-09-02 11:18 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-02 11:18 Sachin Sant [this message]
2009-09-02 12:09 ` EXT4: kernel BUG at fs/jbd2/commit.c:533! 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
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=4A9E5496.8050909@in.ibm.com \
--to=sachinp@in.ibm.com \
--cc=linux-ext4@vger.kernel.org \
/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).