From: Alexander Beregalov <a.beregalov@gmail.com>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-ext4@vger.kernel.org, Jens Axboe <jens.axboe@oracle.com>,
"Theodore Ts'o" <tytso@mit.edu>
Subject: 2.6.33-rc1: kernel BUG at fs/ext4/inode.c:1063 (sparc)
Date: Fri, 25 Dec 2009 01:28:34 +0300 [thread overview]
Message-ID: <a4423d670912241428n6917d2adsad887548612cf8ce@mail.gmail.com> (raw)
Hi
Kernel is 2.6.33-rc1-00366-g2f99f5c
Ext4 mounts ext3 filesystem
kernel BUG at fs/ext4/inode.c:1063!
\|/ ____ \|/
"@'/ .. \`@"
/_| \__/ |_\
\__U_/
flush-8:0(1137): Kernel bad sw trap 5 [#1]
TSTATE: 0000000080001603 TPC: 0000000000544fb4 TNPC: 0000000000544fb8
Y: 00000000 Not tainted
TPC: <ext4_get_blocks+0x3f4/0x400>
g0: fffff800dc862fe0 g1: 0000000000000001 g2: 0000000000000001 g3:
fffff800dc85f9c1
g4: fffff800df305880 g5: 2e68006800002e68 g6: fffff800dc860000 g7:
0000000000833e08
o0: 00000000007b0cb8 o1: 0000000000000427 o2: 0000000000000040 o3:
0000000000000040
o4: fffff800dc8630a0 o5: 000000000000000d sp: fffff800dc8628d1 ret_pc:
0000000000544fac
RPC: <ext4_get_blocks+0x3ec/0x400>
l0: 0000000000000002 l1: fffff800c2674000 l2: fffff800c26740d0 l3:
0000000000000001
l4: fffff800df39d2d0 l5: 00000000000003f9 l6: 0006000000000000 l7:
0000000000001ffe
i0: 0000000000000040 i1: fffff800c2674130 i2: 000000000000064c i3:
fffff800c26745a8
i4: fffff800dc863308 i5: 0000000000000003 i6: fffff800dc8629a1 i7:
0000000000545380
I7: <mpage_da_map_blocks+0x80/0x800>
Disabling lock debugging due to kernel taint
Caller[0000000000545380]: mpage_da_map_blocks+0x80/0x800
Caller[00000000005461c0]: mpage_add_bh_to_extent+0x40/0x100
Caller[000000000054642c]: __mpage_da_writepage+0x1ac/0x220
Caller[00000000004a951c]: write_cache_pages+0x19c/0x380
Caller[0000000000545d7c]: ext4_da_writepages+0x27c/0x680
Caller[00000000004a978c]: do_writepages+0x2c/0x60
Caller[00000000004f94cc]: writeback_single_inode+0xcc/0x3c0
Caller[00000000004fa3d8]: writeback_inodes_wb+0x338/0x500
Caller[00000000004fa6e8]: wb_writeback+0x148/0x220
Caller[00000000004fab00]: wb_do_writeback+0x240/0x260
Caller[00000000004fab8c]: bdi_writeback_task+0x6c/0xc0
Caller[00000000004b6f50]: bdi_start_fn+0x70/0xe0
Caller[000000000047030c]: kthread+0x6c/0x80
Caller[000000000042bc9c]: kernel_thread+0x3c/0x60
Caller[0000000000470408]: kthreadd+0xe8/0x160
Instruction DUMP: 92102427 7ffb95a5 901220b8 <91d02005> 01000000
01000000 9de3bf40 11002096 a4100018
note: flush-8:0[1137] exited with preempt_count 1
next reply other threads:[~2009-12-24 22:28 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-24 22:28 Alexander Beregalov [this message]
2009-12-24 22:49 ` 2.6.33-rc1: kernel BUG at fs/ext4/inode.c:1063 (sparc) Alexander Beregalov
2009-12-25 12:31 ` Dmitry Monakhov
2009-12-25 19:33 ` Alexander Beregalov
2009-12-25 23:47 ` Dmitry Monakhov
2009-12-27 20:32 ` Alexander Beregalov
2009-12-27 21:38 ` Dmitry Torokhov
2009-12-27 22:52 ` tytso
2009-12-27 23:02 ` Alexander Beregalov
2009-12-28 3:51 ` tytso
2009-12-30 5:37 ` tytso
2009-12-30 13:18 ` Dmitry Monakhov
2009-12-30 17:45 ` tytso
2009-12-30 17:48 ` tytso
2009-12-24 23:05 ` tytso
2009-12-24 23:15 ` tytso
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=a4423d670912241428n6917d2adsad887548612cf8ce@mail.gmail.com \
--to=a.beregalov@gmail.com \
--cc=jens.axboe@oracle.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@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).