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: Fri, 28 Sep 2012 10:09:58 +0200 [thread overview]
Message-ID: <50655B56.5080008@ahsoftware.de> (raw)
In-Reply-To: <20120927200538.GC12553@quack.suse.cz>
Am 27.09.2012 22:05, schrieb Jan Kara:
> On Thu 27-09-12 20:01:00, Alexander Holler wrote:
>> [ 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
> This last message usually means hardware really has an issue. You can
> use mcelog tool to find out what problems did the hardware report.
They are already in the messages(.txt) I've attached earlier and are all
like those two below:
----------
MCE 30
Sun Sep 25 15:10:56 2011
HARDWARE ERROR. This is *NOT* a software problem!
Please contact your hardware vendor
CPU 6 THERMAL EVENT TSC 28e5906c38e0
Processor 6 heated above trip temperature. Throttling enabled.
Please check your system cooling. Performance will be impacted
STATUS 880003c3 MCGSTATUS 0
CPUID Vendor Intel Family 6 Model 30
MCE 31
Sun Sep 25 15:10:56 2011
HARDWARE ERROR. This is *NOT* a software problem!
Please contact your hardware vendor
CPU 6 THERMAL EVENT TSC 28e5906c8b66
Processor 6 below trip temperature. Throttling disabled
STATUS 88050282 MCGSTATUS 0
CPUID Vendor Intel Family 6 Model 30
----------
Regards,
Alexander
next prev parent reply other threads:[~2012-09-28 8:13 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-14 11:34 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
2012-09-27 20:05 ` Jan Kara
2012-09-28 8:09 ` Alexander Holler [this message]
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=50655B56.5080008@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome