All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alexander Holler <holler@ahsoftware.de>
To: Jan Kara <jack@suse.cz>
Cc: Dan Carpenter <dan.carpenter@oracle.com>, linux-kernel@vger.kernel.org
Subject: Re: kernel BUG at fs/buffer.c:3205 (stable 3.5.3)
Date: Thu, 27 Sep 2012 20:12:37 +0200	[thread overview]
Message-ID: <50649715.1090507@ahsoftware.de> (raw)
In-Reply-To: <5064945C.4020403@ahsoftware.de>

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


  reply	other threads:[~2012-09-27 18:13 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-14 11:34 kernel BUG at fs/buffer.c:3205 (stable 3.5.3) Alexander Holler
2012-09-25 11:02 ` Dan Carpenter
2012-09-27 11:45   ` Alexander Holler
2012-09-27 15:12     ` Jan Kara
2012-09-27 15:46       ` Alexander Holler
2012-09-27 16:20         ` Alexander Holler
2012-09-27 18:01           ` Alexander Holler
2012-09-27 18:12             ` Alexander Holler [this message]
2012-09-27 20:05             ` Jan Kara
2012-09-28  8:09               ` Alexander Holler
2012-09-27 20:03         ` Jan Kara
2012-09-29 19:07           ` Alexander Holler
2012-10-01  9:10             ` Jan Kara
2012-10-01  9:21               ` Alexander Holler
2012-10-02  9:30                 ` Alexander Holler
2012-10-14  9:10                   ` Alexander Holler
2012-10-14 12:27                     ` Alan Cox
2012-10-15  8:46                       ` Alexander Holler

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=50649715.1090507@ahsoftware.de \
    --to=holler@ahsoftware.de \
    --cc=dan.carpenter@oracle.com \
    --cc=jack@suse.cz \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.