linux-kernel - kernel BUG at fs/jbd2/journal.c:311

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <4C7EC930.2070701@schaumburger.info>
Date:	Wed, 01 Sep 2010 23:44:16 +0200
From:	Steffen Schaumburg <steffen@...aumburger.info>
To:	linux-kernel@...r.kernel.org
Subject: kernel BUG at fs/jbd2/journal.c:311

 Hello,
First of all thanks for this great software :)
Now unfortunately I'm having problems with kernels 2.6.35-gentoo-r1 and
2.6.35-gentoo-r5. If I should try a vanilla kernel please tell me :)
I searched the LKML archive but couldn't find anything relevant.

The problem is twofold (the 2nd one is what I'm writing about, but the
first one may be relevant to the second one):
1. At 50004-50005 seconds after boot I got an error indicating that my
"ata3.00"/sdc is having physical problems:
[50004.996331] ata3.00: exception Emask 0x0 SAct 0xfd SErr 0x0 action 0x0
[50004.996335] ata3.00: irq_stat 0x40000008
[50004.996338] ata3.00: failed command: READ FPDMA QUEUED
[50004.996344] ata3.00: cmd 60/08:18:25:2c:63/00:00:54:00:00/40 tag 3
ncq 4096 in
[50004.996345]          res 41/40:04:29:2c:63/00:00:54:00:00/40 Emask
0x409 (media error) <F>
[50004.996348] ata3.00: status: { DRDY ERR }
[50004.996350] ata3.00: error: { UNC }
[50005.009325] ata3.00: configured for UDMA/133
[50005.009343] ata3: EH complete

2. At 163096 seconds after boot I get this message in the log: "kernel
BUG at fs/jbd2/journal.c:311!" (see attached full dmesg - most of it is
relevant anyways, and I didn't want to miss vital information, so I
attached the whole thing - I hope that was the right thing to do)

Is this really a kernel bug, or is it just that I have a dying drive?
Normally I would assume the latter, but since there's been so many hours
between the two error messages I'm not so sure.

I have gotten the error message in both the -r1 and -r5 kernel, but I
cannot reproduce the problem with any particular steps. When the error
happens then various processes (usually firefox and thunderbird first)
go into D state and are unkillable. Both times I proceeded to quit as
many applications as I could, umounted whatever partitions I could, and
remounted the remainder as read-only.
I have 4 SATA drives (1*1TB, 3*1.5TB) on my AMD/ATI 780series chipset
controller, running MDRAID (on /boot and /) and LVM-on-MDRAID for
everything else.

I would be most grateful for any advice! I am subscribed to LKML so you
don't need to CC me.

Thanks, Steffen

View attachment "dmesg2.txt" of type "text/plain" (31419 bytes)