Scheduled Maintenance: We are aware of an issue with Google, AOL, and Yahoo services as email providers which are blocking new registrations. We are trying to fix the issue and we have several internal and external support tickets in process to resolve the issue. Please see: viewtopic.php?t=158230

 

 

 

Package power limit notification issueDELL Poweredge R320

User discussion about Debian Development, Debian Project News and Announcements. Not for support questions.
Post Reply
Message
Author
rbmramesh
Posts: 3
Joined: 2014-07-30 09:30

Package power limit notification issueDELL Poweredge R320

#1 Post by rbmramesh »

Hi,
I am running Debian Wheezy 7 linux on DELL Power Edge R320 machine.
I am receiving the below error in my /var/log/syslog file and it degrades the server performance and the same error occurs on all my Linux servers. Could you please help me to resolve this issue .

Mar 26 08:37:26 weblive kernel: [1787796.394549] CPU0: Package power limit notification (total events = 15296088)
Mar 26 08:37:26 weblive kernel: [1787796.394542] CPU2: Package power limit normal
Mar 26 08:37:26 weblive kernel: [1787796.394535] CPU5: Core power limit normal
Mar 26 08:37:26 weblive kernel: [1787796.394496] CPU1: Core power limit normal
Mar 26 08:37:26 weblive kernel: [1787796.394468] CPU4: Core power limit normal
Mar 26 08:37:26 weblive kernel: [1787796.394429] CPU0: Core power limit normal
Mar 26 08:37:26 weblive kernel: [1787796.394385] CPU3: Core power limit normal
Mar 26 08:37:26 weblive kernel: [1787796.394345] CPU7: Core power limit normal
Mar 26 08:37:26 weblive kernel: [1787796.394305] CPU2: Core power limit normal
Mar 26 08:37:26 weblive kernel: [1787796.394301] CPU6: Core power limit normal
Mar 26 08:37:26 weblive kernel: [1787796.393697] CPU1: Package power limit notification (total events = 15364126)
Mar 26 08:37:26 weblive kernel: [1787796.389955] CPU4: Package power limit notification (total events = 15295975)
Mar 26 08:37:26 weblive kernel: [1787796.389908] CPU3: Package power limit notification (total events = 15381717)
Mar 26 08:37:26 weblive kernel: [1787796.389868] CPU7: Package power limit notification (total events = 15381639)
Mar 26 08:37:26 weblive kernel: [1787796.389790] CPU6: Package power limit notification (total events = 15365716)
Mar 26 08:37:26 weblive kernel: [1787796.389749] CPU2: Package power limit notification (total events = 15365737)
Mar 26 08:37:26 weblive kernel: [1787796.389703] CPU5: Package power limit notification (total events = 15364103)
Mar 26 08:37:26 weblive kernel: [1787796.389636] CPU4: Core power limit notification (total events = 15268515)
Mar 26 08:37:26 weblive kernel: [1787796.389594] CPU0: Core power limit notification (total events = 15268570)
Mar 26 08:37:26 weblive kernel: [1787796.389510] CPU3: Core power limit notification (total events = 15376749)
Mar 26 08:37:26 weblive kernel: [1787796.389431] CPU7: Core power limit notification (total events = 15376630)
Mar 26 08:37:26 weblive kernel: [1787796.389351] CPU6: Core power limit notification (total events = 15357603)
Mar 26 08:37:26 weblive kernel: [1787796.389307] CPU2: Core power limit notification (total events = 15357767)
Mar 26 08:37:26 weblive kernel: [1787796.389223] CPU5: Core power limit notification (total events = 15330864)
Mar 26 08:37:26 weblive kernel: [1787796.389145] CPU1: Core power limit notification (total events = 15331225)
Mar 26 08:32:26 weblive kernel: [1787496.978265] CPU0: Package power limit notification (total events = 15231817)
Mar 26 08:32:26 weblive kernel: [1787496.975870] CPU7: Package power limit notification (total events = 15317230)
Mar 26 08:32:26 weblive kernel: [1787496.975829] CPU3: Package power limit notification (total events = 15317310)
Mar 26 08:32:26 weblive kernel: [1787496.975751] CPU2: Package power limit notification (total events = 15301318)
Mar 26 08:32:26 weblive kernel: [1787496.975710] CPU6: Package power limit notification (total events = 15301297)
Mar 26 08:32:26 weblive kernel: [1787496.975667] CPU5: Package power limit notification (total events = 15299701)
Mar 26 08:32:26 weblive kernel: [1787496.975589] CPU1: Package power limit notification (total events = 15299724)
Mar 26 08:32:26 weblive kernel: [1787496.975548] CPU4: Package power limit notification (total events = 15231706)
Mar 26 08:32:26 weblive kernel: [1787496.975509] CPU7: Core power limit normal
Mar 26 08:32:26 weblive kernel: [1787496.975431] CPU3: Core power limit normal
Mar 26 08:32:26 weblive kernel: [1787496.975352] CPU2: Core power limit normal
Mar 26 08:32:26 weblive kernel: [1787496.975310] CPU6: Core power limit normal
Mar 26 08:32:26 weblive kernel: [1787496.975231] CPU5: Core power limit normal
Mar 26 08:32:26 weblive kernel: [1787496.975189] CPU1: Core power limit normal
Mar 26 08:32:26 weblive kernel: [1787496.975146] CPU4: Core power limit normal
Mar 26 08:32:26 weblive kernel: [1787496.975068] CPU0: Core power limit normal
Mar 26 08:27:24 weblive kernel: [1787195.219789] CPU1: Core power limit normal
Mar 26 08:27:24 weblive kernel: [1787195.219765] CPU4: Core power limit normal
Mar 26 08:27:24 weblive kernel: [1787195.219704] CPU3: Core power limit normal
Mar 26 08:27:24 weblive kernel: [1787195.219701] CPU7: Core power limit normal
Mar 26 08:27:24 weblive kernel: [1787195.219661] CPU2: Core power limit normal
Mar 26 08:27:24 weblive kernel: [1787195.219621] CPU6: Core power limit normal
Mar 26 08:27:24 weblive kernel: [1787195.219605] CPU0: Core power limit normal


Server details
root@weblive:~# uname -a
Linux weblive 3.2.0-4-amd64 #1 SMP Debian 3.2.60-1+deb7u3 x86_64 GNU/Linux
OS: Debian Wheezy 7

If you need any other detail please let me know.

User avatar
stevepusser
Posts: 12930
Joined: 2009-10-06 05:53
Has thanked: 41 times
Been thanked: 71 times

Re: Package power limit notification issueDELL Poweredge R32

#2 Post by stevepusser »

Ummmm....simply searching the web for " Package power limit notification" results in this Dell article
as the top result:

http://www.dell.com/support/article/us/ ... N266056/EN

A third workaround would be to use a newer kernel that does not spam the log with the harmless messages, but simply adding the kernel parameter to the boot command would be simplest.
MX Linux packager and developer

Post Reply