linux-kernel - Re: [RESEND 2] [PATCH 0/2] Rewrite power limit notification interrupt handling

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

Date:	Wed, 29 May 2013 14:14:09 -0400
From:	Prarit Bhargava <prarit@...hat.com>
To:	linux-kernel@...r.kernel.org
CC:	len.brown@...nel.org
Subject: Re: [RESEND 2] [PATCH 0/2] Rewrite power limit notification interrupt
 handling

Len,

>The "Power Limit Notification" (X86_FEATURE_PLN) was added in Sandy Bridge
>to give the OS the option of knowing when the package has reached
>a configured power threshold.

>printk(KERN_CRIT "CPU%d: %s power limit notification (total events = %lu)
>printk(KERN_INFO "CPU%d: %s power limit normal\n"

I'm seeing this on a widening number of systems, mostly newer Intel systems.

>However, these events are quite routine on some systems under some conditions,
>alarming customers and provoking un-necessary customer support calls.

The idea that these are "routine" just doesn't make sense to me.  Either this
warning is firing for a valid reason or it isn't.  If it isn't then the question
remains -- why is it firing?  Is it because of buggy FW or is something
actually wrong with the hardware?

P.
--
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/