Re: kernel BUG at fs/buffer.c:3205 (stable 3.5.3)

From: Alexander Holler
Date: Thu Sep 27 2012 - 14:12:56 EST


Am 27.09.2012 20:01, schrieb Alexander Holler:

After 2 successful tries in sequence, the third failed (sorry, LANG=de):

---------------------------------------------------------------
[root@krabat bind]# tar cp . | mbuffer | bzip2smp
>/mnt/usb3/Krabat.Fedora17.sdb2.27.09.12.tar.bz2
in @ 33.1 MiB/s, out @ 38.3 MiB/s, 888 MiB total, buffer 95% fulltar:
./tmp/.X11-unix/X0: Socket ignoriert
in @ 0.0 KiB/s, out @ 20.8 MiB/s, 24.9 GiB total, buffer 22% full
summary: 24.9 GiByte in 19 min 53.0 sec - average of 21.4 MiB/s
[root@krabat bind]# tar djf /mnt/usb3/Krabat.Fedora17.sdb2.27.09.12.tar.bz2
./var/log/messages: Änderungszeit ist unterschiedlich
./var/log/messages: Größe ist unterschiedlich
./var/tmp/kdecache-aholler/icon-cache.kcache: Änderungszeit ist
unterschiedlich
./var/tmp/kdecache-aholler/icon-cache.kcache: Unterschiedliche Inhalte
./var/tmp/kdecache-aholler/plasma_theme_oxygen.kcache: Änderungszeit ist
unterschiedlich
./var/tmp/kdecache-aholler/plasma_theme_oxygen.kcache: Unterschiedliche
Inhalte
./var/lib/chrony/drift: Änderungszeit ist unterschiedlich
./var/lib/chrony/drift: Unterschiedliche Inhalte
./home/aholler/.kde/share/apps/konqueror/autosave/_1.77: Änderungszeit
ist unterschiedlich
./home/aholler/.kde/share/apps/konqueror/autosave/_1.77: Größe ist
unterschiedlich
./home/aholler/.kde/share/apps/konqueror/konq_history: Änderungszeit ist
unterschiedlich
./home/aholler/.kde/share/apps/konqueror/konq_history: Größe ist
unterschiedlich
./home/aholler/.kde/share/apps/kcookiejar/cookies: Änderungszeit ist
unterschiedlich
./home/aholler/thinstation_src-2.0beta2.tar.bz2: Unterschiedliche Inhalte

bzip2: Data integrity error when decompressing.
Input file = (stdin), output file = (stdout)

It is possible that the compressed file(s) have become corrupted.
You can use the -tvv option to test integrity of such files.

You can use the `bzip2recover' program to attempt to recover
data from undamaged sections of corrupted files.

tar: Unerwartetes Dateiende im Archiv.
tar: Child returned status 2
tar: Error is not recoverable: exiting now
[root@krabat bind]#
---------------------------------------------------------------

This time without any oops, dmesg just shows some

---------------------------------------------------------------
[ 111.087356] EXT4-fs (sdc1): mounted filesystem with ordered data
mode. Opts: (null)
[ 672.868948] CPU4: Core temperature above threshold, cpu clock
throttled (total events = 1)
[ 672.868949] CPU0: Core temperature above threshold, cpu clock
throttled (total events = 1)
[ 672.869970] CPU0: Core temperature/speed normal
[ 672.869971] CPU4: Core temperature/speed normal
[ 688.285419] CPU6: Core temperature above threshold, cpu clock
throttled (total events = 1)
[ 688.285421] CPU2: Core temperature above threshold, cpu clock
throttled (total events = 1)
[ 688.286442] CPU2: Core temperature/speed normal
[ 688.286443] CPU6: Core temperature/speed normal
[ 698.822614] CPU3: Core temperature above threshold, cpu clock
throttled (total events = 1)
[ 698.822615] CPU7: Core temperature above threshold, cpu clock
throttled (total events = 1)
[ 698.824674] CPU3: Core temperature/speed normal
[ 698.824675] CPU7: Core temperature/speed normal
[ 706.979633] CPU1: Core temperature above threshold, cpu clock
throttled (total events = 1)
[ 706.979635] CPU5: Core temperature above threshold, cpu clock
throttled (total events = 1)
[ 706.980648] CPU1: Core temperature/speed normal
[ 706.980649] CPU5: Core temperature/speed normal
[ 899.540485] [Hardware Error]: Machine check events logged
---------------------------------------------------------------

Nothing else. Kernel is 3.5.4 userland now F17.

Maybe it's really a heating problem and the stock fan (or throttling by the kernel) isn't enough if the processor (or the chipset) is used like that for about 60 minutes. I will checkout if one or more additional fans will help.

Regards,

Alexander

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/