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: <20100916144917.54d5f2b0@jbarnes-x201>
Date:	Thu, 16 Sep 2010 14:49:17 +0200
From:	Jesse Barnes <jbarnes@...tuousgeek.org>
To:	tim.gardner@...onical.com
Cc:	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: MCP limit log messages, 2.6.36-rc4

On Wed, 15 Sep 2010 13:20:00 -0600
Tim Gardner <tim.gardner@...onical.com> wrote:

> On 09/15/2010 11:47 AM, Tim Gardner wrote:
> > I've been getting regular MCP limit log messages on a Dell Studio
> > 1458 (i5 CPU) with an A02 BIOS. With the attached debug hack it
> > prints the following values:
> >
> > [ 33.605098] intel ips 0000:00:1f.6: MCP limit exceeded: Avg power
> > 30123, limit 1023
> > [ 38.597998] intel ips 0000:00:1f.6: MCP limit exceeded: Avg power
> > 21697, limit 1023
> > [ 43.590917] intel ips 0000:00:1f.6: MCP limit exceeded: Avg power
> > 15390, limit 1023
> > [ 48.583821] intel ips 0000:00:1f.6: MCP limit exceeded: Avg power
> > 43370, limit 1023
> > [ 53.576740] intel ips 0000:00:1f.6: MCP limit exceeded: Avg power
> > 64728, limit 1023
> >
> > This is an idle machine which starts printing these messages about
> > 30 seconds after boot. Any thoughts?
> >
> > rtg
> 
> More clues:
> 
> [   13.426064] intel ips 0000:00:1f.6: Warning: CPU TDP doesn't match 
> expected value (found 25, expected 35)
> [   13.426086] intel ips 0000:00:1f.6: PCI INT C -> GSI 18 (level,
> low) -> IRQ 18
> [   13.426933] intel ips 0000:00:1f.6: IPS driver initialized, MCP
> temp limit 95
> 

Oh interesting, this looks like a slightly different problem than some
others have been seeing.  The power limit is listed at 1023 but the
reported value is looking at least 100x over that, so we may have a
reporting vs limit unit mismatch here.

I'm looking into finding a way to enable the thermal device which would
fix another problem we have with bogus thermal limits and reporting,
but yours is a separate problem.  I'll take a look at the sources and
double check my unit calculations...

Thanks,
-- 
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