From: Mike Galbraith <efault@gmx.de>
To: Andrew Morton <akpm@digeo.com>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: 2.5.59mm2 BUG at fs/jbd/transaction.c:1148
Date: Sun, 19 Jan 2003 08:46:35 +0100 [thread overview]
Message-ID: <5.1.1.6.2.20030119084031.00c81180@pop.gmx.net> (raw)
In-Reply-To: <20030118002027.2be733c7.akpm@digeo.com>
[-- Attachment #1: Type: text/plain, Size: 167 bytes --]
Greetings,
I got the attached oops upon doing my standard reboot sequence SysRq[sub].
fwiw, I was fiddling with an ext2 ramdisk just prior to poking buttons.
-Mike
[-- Attachment #2: oops --]
[-- Type: application/octet-stream, Size: 1675 bytes --]
SysRq : Emergency Sync
Syncing device ide0(3,6) ... OK
Syncing device ide0(3,7) ...
<0>Assertion failure in journal_dirty_metadata() at fs/jbd/transaction.c:1148: "jh->b_jlist != 1"
------------[ cut here ]------------
kernel BUG at fs/jbd/transaction.c:1148!
invalid operand: 0000
CPU: 0
EIP: 0060:[<c01755e4>] Not tainted
EFLAGS: 00010286
EIP is at journal_dirty_metadata+0x10c/0x174
eax: 00000062 ebx: c33aeb80 ecx: c31df8e0 edx: c027fbb0
esi: c32b9260 edi: c7a89e00 ebp: c7a839c0 esp: c31e1ccc
ds: 007b es: 007b ss: 0068
Process syslogd (pid: 102, threadinfo=c31e0000 task=c31df8e0)
Stack: c0249ca0 c024a1c1 c0249c80 0000047c c024a1d8 c317cd3c c7a839c0 00000000
c31e1d64 c0169bd1 c7a839c0 c317cd3c c317cd3c 00001000 c317cd3c 00001000
00000050 00000040 c0169994 c7a839c0 c317cd3c 00010000 00000000 c31c5660
Call Trace:
[<c0169bd1>] commit_write_fn+0x19/0x60
[<c0169994>] walk_page_buffers+0x50/0x74
[<c0169cda>] ext3_commit_write+0xc2/0x1d8
[<c0169bb8>] commit_write_fn+0x0/0x60
[<c0129e13>] generic_file_aio_write_nolock+0x797/0x984
[<c01f2bab>] kfree_skbmem+0xb/0x54
[<c01f2cb6>] __kfree_skb+0xc2/0xc8
[<c0230fba>] unix_stream_recvmsg+0x2ea/0x370
[<c012a06f>] generic_file_write_nolock+0x6f/0x8c
[<c01efe46>] sock_aio_read+0x8a/0x9c
[<c013cab1>] do_sync_read+0x81/0xb0
[<c01163bd>] do_schedule+0x235/0x25c
[<c012a225>] generic_file_writev+0x31/0x44
[<c013d08b>] do_readv_writev+0x1a7/0x27c
[<c013cbe0>] do_sync_write+0x0/0xb0
[<c017205d>] ext3_force_commit+0x1d/0x24
[<c01675bb>] ext3_sync_file+0x5b/0x70
[<c013d1f7>] vfs_writev+0x4b/0x50
[<c013d262>] sys_writev+0x2a/0x3c
[<c010a367>] syscall_call+0x7/0xb
next prev parent reply other threads:[~2003-01-19 7:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-18 8:20 2.5.59-mm2 Andrew Morton
2003-01-18 20:12 ` 2.5.59-mm2 Arjan van de Ven
2003-01-19 7:46 ` Mike Galbraith [this message]
2003-01-19 8:05 ` 2.5.59mm2 BUG at fs/jbd/transaction.c:1148 Andrew Morton
2003-01-19 8:04 ` Mike Galbraith
2003-01-19 8:57 ` Andrew Morton
2003-01-19 8:06 ` Mike Galbraith
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=5.1.1.6.2.20030119084031.00c81180@pop.gmx.net \
--to=efault@gmx.de \
--cc=akpm@digeo.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.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