linux-kernel - Re: MCE/Hardware errors/Temperature on MacBookAir 4,2

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>] [<thread-prev] [day] [month] [year] [list]

Date:	Wed, 07 Dec 2011 10:55:47 +0800
From:	Chen Gong <gong.chen@...ux.intel.com>
To:	Nico Schottelius <nico-linux-20111201@...ottelius.org>,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: MCE/Hardware errors/Temperature on MacBookAir 4,2

于 2011/12/6 16:29, Nico Schottelius 写道:
> 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
>

pls check this thread:
https://lkml.org/lkml/2011/11/14/239
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/