From: Nico Schottelius <nico-linux-20111201@schottelius.org>
To: LKML <linux-kernel@vger.kernel.org>
Cc: Nico Schottelius <nico-linux-20111201@schottelius.org>
Subject: MCE/Hardware errors/Temperature on MacBookAir 4,2
Date: Tue, 6 Dec 2011 09:29:53 +0100 [thread overview]
Message-ID: <20111206082953.GA1945@schottelius.org> (raw)
Hello,
with the previous kernel compiling a new kernel, I get these
messages in dmesg:
[170745.226310] ieee80211 phy0: brcms_ops_bss_info_changed: arp filtering: enabled true, count 1 (implement)
[170942.965765] CPU3: Core temperature above threshold, cpu clock throttled (total events = 1)
[170942.965770] CPU1: Core temperature above threshold, cpu clock throttled (total events = 1)
[170942.965776] CPU2: Package temperature above threshold, cpu clock throttled (total events = 1)
[170942.965781] CPU0: Package temperature above threshold, cpu clock throttled (total events = 1)
[170942.965785] CPU1: Package temperature above threshold, cpu clock throttled (total events = 1)
[170942.965791] CPU3: Package temperature above threshold, cpu clock throttled (total events = 1)
[170942.966766] CPU3: Core temperature/speed normal
[170942.966770] CPU1: Core temperature/speed normal
[170942.966775] CPU2: Package temperature/speed normal
[170942.966779] CPU0: Package temperature/speed normal
[170942.966782] CPU1: Package temperature/speed normal
[170942.966787] CPU3: Package temperature/speed normal
[171033.962774] [Hardware Error]: Machine check events logged
Shall I consider these informative/warning/dangerous?
In any case, I'm wondering whath the hardware error may be
and whether it's really a hardware error or OS problem?
Cheers,
Nico
--
PGP key: 7ED9 F7D3 6B10 81D7 0EC5 5C09 D7DC C8E4 3187 7DF0
next reply other threads:[~2011-12-06 13:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-06 8:29 Nico Schottelius [this message]
2011-12-07 2:55 ` MCE/Hardware errors/Temperature on MacBookAir 4,2 Chen Gong
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=20111206082953.GA1945@schottelius.org \
--to=nico-linux-20111201@schottelius.org \
--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