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] [thread-next>] [day] [month] [year] [list]
Message-ID: <20100824183706.27645aa1@virtuousgeek.org>
Date:	Tue, 24 Aug 2010 18:37:06 -0700
From:	Jesse Barnes <jbarnes@...tuousgeek.org>
To:	Cesar Eduardo Barros <cesarb@...arb.net>
Cc:	linux-kernel@...r.kernel.org, platform-driver-x86@...r.kernel.org,
	Matthew Garrett <mjg@...hat.com>
Subject: Re: intel ips: CPU TDP doesn't match expected value

On Tue, 24 Aug 2010 21:48:45 -0300
Cesar Eduardo Barros <cesarb@...arb.net> wrote:

> I get the following messages on v2.6.36-rc2-203-g502adf5:
> 
> intel ips 0000:00:1f.6: Warning: CPU TDP doesn't match expected value 
> (found 25, expected 35)
> intel ips 0000:00:1f.6: PCI INT C -> GSI 18 (level, low) -> IRQ 18
> intel ips 0000:00:1f.6: IPS driver initialized, MCP temp limit 65535
> intel ips 0000:00:1f.6: MCP power or thermal limit exceeded
> intel ips 0000:00:1f.6: CPU power or thermal limit exceeded
> 
> (The last two messages repeat very often, one of them every five 
> seconds; if I understand it correctly, that is normal and expected.)
> 
> The code implies the "CPU TDP doesn't match expected value" is a sanity 
> check failing. Should that happen, or is there something wrong?

Yeah, it's normal, and should probably be downgraded to an
informational message.  It just means your BIOS doesn't want you to
push the CPU all the way up to its maximum TDP, probably because the
platform or chassis wasn't designed for that much heat or power
consumption.

-- 
Jesse Barnes, Intel Open Source Technology Center
--
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ