From: "Hanno Böck" <ml@hboeck.de>
To: linux-kernel@vger.kernel.org
Subject: Assertion failure in journal_next_log_block() at fs/jbd/journal.c:568: "journal->j_free > 1"
Date: Fri, 11 Jan 2008 18:25:45 +0100 [thread overview]
Message-ID: <200801111825.48083.ml@hboeck.de> (raw)
[-- Attachment #1: Type: text/plain, Size: 2353 bytes --]
I got a message about a kernel bug in dmesg. I found only one reference to a
similar issue, a mail to lkml from 2006, but without any reply.
If this is a bug and not caused by hw failure, it seems to be triggered very
rare.
Gentoo Linux, Kernel is 2.6.23.12 with grsecurity, amd64. It's not
reproducible, only appeared once. After that, the system did strange things
and wasn't able to reboot, I had to reset manually. If there's anything more
I can provide as information, just ask me.
Please CC me on replies, as I'm not reading this list.
Assertion failure in journal_next_log_block() at
fs/jbd/journal.c:568: "journal->j_free > 1"
------------[ cut here ]------------
kernel BUG at fs/jbd/journal.c:568!
invalid opcode: 0000 [1]
CPU 0
Pid: 989, comm: kjournald Not tainted 2.6.23.12-grsec #1
RIP: 0010:[<ffffffff802b6ad6>] [<ffffffff802b6ad6>]
RSP: 0018:ffff81007ed37e20 EFLAGS: 00010286
RAX: 0000000000000060 RBX: ffff810031a65130 RCX: 0000000000000082
RDX: ffffffff80524a47 RSI: 0000000100000000 RDI: ffffffff804679cd
RBP: ffff8100474c4c70 R08: 0000000000000000 R09: ffffffff8044a9a0
R10: 0000000000000000 R11: ffff81007ed37cbc R12: ffff810066c93bc0
R13: ffff81007e891c00 R14: 00000000000001fb R15: ffff810049ee9c74
FS: 00002d76dffd7f80(0000) GS:ffffffff804cf000(0000) knlGS:0000000000000000
CS: 0010 DS: 0018 ES: 0018 CR0: 000000008005003b
CR2: 00002e036f0fa000 CR3: 000000007b15d000 CR4: 00000000000006e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
Process kjournald (pid: 989, threadinfo ffff81007ed36000, task
ffff810037d517e0)
Stack: ffff810049ee9c6c ffffffff802b381c ffff81007ed3e000 0000018c00001000
0000038c00000000 0000016300000000 ffff81007ed37ec0 0000000000000046
ffffffff8022b843 ffff810037d517e0 ffff8100485060c0 ffff8100483e70c0
Call Trace:
[<ffffffff802b381c>]
[<ffffffff8022b843>]
[<ffffffff802b6e42>]
[<ffffffff8022b843>]
[<ffffffff802b6d97>]
[<ffffffff8022b682>]
[<ffffffff8020bc38>]
[<ffffffff8035c774>]
[<ffffffff8022b63b>]
[<ffffffff8020bc2e>]
Code: 0f 0b eb fe 48 8b b7 d0 00 00 00 48 ff 8f e0 00 00 00 48 8d
RIP [<ffffffff802b6ad6>]
RSP <ffff81007ed37e20>
--
Hanno Böck Blog: http://www.hboeck.de/
GPG: 3DBD3B20 Jabber/Mail: hanno@hboeck.de
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
reply other threads:[~2008-01-11 17:30 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=200801111825.48083.ml@hboeck.de \
--to=ml@hboeck.de \
--cc=linux-kernel@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
Powered by JetHome