Package power limit notification

本文介绍了一种解决DELL12代服务器(R620)上频繁出现CPU报警的方法。通过调整BIOS设置禁用Turboboost功能来避免CPU因温度过高而触发报警。

   最近装了一批DELL 12代的服务器(R620),运行几天后,发现在系统日志中出现很多CPU报警,如下:

CPU13: Package power limit notification (total events = 1) 
CPU1: Package power limit notification (total events = 1) 
CPU17: Package power limit notification (total events = 1) 
CPU3: Package power limit notification (total events = 1) 
CPU19: Package power limit notification (total events = 1) 
CPU5: Package power limit notification (total events = 1) 
CPU21: Package power limit notification (total events = 1) 
CPU7: Package power limit notification (total events = 1) 
CPU23: Package power limit notification (total events = 1) 
CPU9: Package power limit notification (total events = 1) 
CPU25: Package power limit notification (total events = 1) 
CPU11: Package power limit notification (total events = 1) 
CPU27: Package power limit notification (total events = 1) 
CPU31: Package power limit notification (total events = 1) 
CPU15: Package power limit notification (total events = 1) 
CPU29: Package power limit notification (total events = 1) 
CPU17: Core power limit normal 
CPU1: Core power limit normal 
CPU3: Core power limit normal 
CPU19: Core power limit normal 
CPU21: Core power limit normal 
CPU5: Core power limit normal 
CPU23: Core power limit normal 
CPU7: Core power limit normal
查了一下google资料,解释说是应该是CPU的保护温度阈值在BIOS中设置的过于低了,于是在BIOS中搜索一番后,没有发现设置的CPU温度报警阈值的地方。在dell官网找到一份12代服务器的资料后,得到如下解释:


再次进入BIOS中,进入system profile settings,第一个选项默认是performance per watt(DAPC),选择该选项后,默认是开启Turbo boost的


在system profile中选择最后一个手动模式,剩下的其他选项就可以设置了,只要修改Turbo boost为disable,其余选项均不变即可,保存后重启机器。


转载于:https://my.oschina.net/guol/blog/125801

08-03 16:06:20.769640 19957 19996 I Finsky:background: [1511] abos.i(257): DL: Data loader session turned off due to Incremental install not requested: com.vkontakte.android 08-03 16:06:20.771626 17853 17939 W [0]DCS : Common Record event failed. DCS reject event: [appId=20089,logTag=20089,eventId=high_power_notification] . Pls check server config. 08-03 16:06:20.771625 19957 20053 I Finsky:background: [1539] abos.i(257): DL: Data loader session turned off due to Incremental install not requested: com.vkontakte.android 08-03 16:06:20.772463 19957 20033 I Finsky:background: [1528] ahqg.accept(444): IV2: Setting install scenario: 1 08-03 16:06:20.775159 19957 20033 E Finsky:background: [1528] ahqk.e(13): SM: Session creation failed with errorCode=5404 08-03 16:06:20.775159 19957 20033 E Finsky:background: java.lang.IllegalStateException: Too many active sessions for UID 10105 08-03 16:06:20.775159 19957 20033 E Finsky:background: at android.os.Parcel.createExceptionOrNull(Parcel.java:3280) 08-03 16:06:20.775159 19957 20033 E Finsky:background: at android.os.Parcel.createException(Parcel.java:3256) 08-03 16:06:20.775159 19957 20033 E Finsky:background: at android.os.Parcel.readException(Parcel.java:3239) 08-03 16:06:20.775159 19957 20033 E Finsky:background: at android.os.Parcel.readException(Parcel.java:3181) 08-03 16:06:20.775159 19957 20033 E Finsky:background: at android.content.pm.IPackageInstaller$Stub$Proxy.createSession(IPackageInstaller.java:626) 08-03 16:06:20.775159 19957 20033 E Finsky:background: at android.content.pm.PackageInstaller.createSession(PackageInstaller.java:820) 08-03 16:06:20.775159 19957 20033 E Finsky:background: at aick.a(PG:1121) 08-03 16:06:20.775159 19957 20033 E Finsky:background: at azfu.d(PG:3) 08-03 16:06:20.775159 19957 20033 E Finsky:background: at azfw.run(PG:38) 08-03 16:06:20.775159 19957 20033 E Finsky:background: at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1156) 08-03 16:06:20.775159 19957 20033 E Finsky:background: at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:651) 08-03 16:06:20.775159 19957 20033 E Finsky:background: at qhu.run(PG:29) 08-03 16:06:20.775159 19957 20033 E Finsky:background: at java.lang.Thread.run(Thread.java:1119) 08-03 16:06:20.775659 19957 19996 E Finsky:background: [1511] vlg.a(744): IV2: failed to create session for [Package:com.vkontakte.android, isid:Zrt6iUigSkC5hZ276rtG0w] statusCode=5404. 08-03 16:06:20.776402 19957 19996 E Finsky:background: [1511] nob.a(1005): IV2: request install failure for [Package:com.vkontakte.android, isid:Zrt6iUigSkC5hZ276rtG0w] 08-03 16:06:20.776402 19957 19996 E Finsky:background: com.google.android.finsky.installercommon.InstallerException: Status: 5404 08-03 16:06:20.776402 19957 19996 E Finsky:background: at vlg.a(PG:751) 08-03 16:06:20.776402 19957 19996 E Finsky:background: at azfu.d(PG:3) 08-03 16:06:20.776402 19957 19996 E Finsky:background: at azfw.run(PG:38) 08-03 16:06:20.776402 19957 19996 E Finsky:background: at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1156) 08-03 16:06:20.776402 19957 19996 E Finsky:background: at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:651) 08-03 16:06:20.776402 19957 19996 E Finsky:background: at qhu.run(PG:29) 08-03 16:06:20.776402 19957 19996 E Finsky:background: at java.lang.Thread.run(Thread.java:1119) 08-03 16:06:20.776619 1489 15125 D PipelineWatcher: onInputBufferReleased: frameIndex not found (620); ignored 08-03 16:06:20.779817 19957 19996 I Finsky:background: [1511] afco.a(317): SCU: Failed to abandon the session for com.vkontakte.android[iid:571] [isid:Zrt6iUigSkC5hZ276rtG0w] due to 5426, msg: Optional[No open Session with Context {name=com.vkontakte.android versionCode=40084} was found.] 08-03 16:06:20.780957 1134 1134 E HWC2 : Invalid CT ID. displayId: 0 08-03 16:06:20.781598 19957 19996 I Finsky:background: [1511] vmc.k(23): IV2: stopping install timeout for 571 08-03 16:06:20.789833 19957 19996 E Finsky:background: [1511] mrz.apply(202): IV2: Rejecting request for [Package:com.vkontakte.android, isid:Zrt6iUigSkC5hZ276rtG0w] statusCode: 5404 08-03 16:06:20.789833 19957 19996 E Finsky:background: com.google.android.finsky.installercommon.InstallerException: Status: 5404 08-03 16:06:20.789833 19957 19996 E Finsky:background: at vlg.a(PG:751) 08-03 16:06:20.789833 19957 19996 E Finsky:background: at azfu.d(PG:3) 08-03 16:06:20.789833 19957 19996 E Finsky:background: at azfw.run(PG:38) 08-03 16:06:20.789833 19957 19996 E Finsky:background: at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1156) 08-03 16:06:20.789833 19957 19996 E Finsky:background: at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:651) 08-03 16:06:20.789833 19957 19996 E Finsky:background: at qhu.run(PG:29) 08-03 16:06:20.789833 19957 19996 E Finsky:background: at java.lang.Thread.run(Thread.java:1119) 08-03 16:06:20.792809 1489 15125 D PipelineWatcher: onInputBufferReleased: frameIndex not found (621); ignored 08-03 16:06:20.796250 19957 19992 I Finsky:background: [1507] vqq.Y(19): IQ: start evaluating install requests. 08-03 16:06:20.797786 1134 1134 E HWC2 : Invalid CT ID. displayId: 0 08-03 16:06:20.800636 19957 20004 I Finsky:background: [1518] vqq.Q(41): IQ: Notifying installation update. [Package:com.vkontakte.android, isid:Zrt6iUigSkC5hZ276rtG0w], status=INSTALL_ERROR, status_code=5404, reason=single_install, tsc=PT1.332S, attempt=0
08-31
### 实现 Unity 中 Mixed Reality Power Thermal Notification 功能 在 Unity 中实现混合现实 (Mixed Reality, MR) 的电源热通知 (Power Thermal Notification),主要依赖于设备特定 API 和 Unity 插件的支持。对于 HoloLens 或其他支持 Windows Mixed Reality 平台的头戴显示装置,可以利用 UWP (Universal Windows Platform) 提供的功能来监测温度状态并触发相应的事件处理逻辑。 #### 使用 C# 脚本监听热管理变化 为了响应来自硬件层面上有关过热警告的信息,在应用程序启动时注册回调函数是一个常见做法: ```csharp using System; using UnityEngine.XR.WSA; public class ThermalNotificationHandler : MonoBehaviour { void Start() { // 注册用于接收热状态改变的通知 Thermometer.ThermalStatusChanged += OnThermalStatusChanged; } private void OnThermalStatusChanged(object sender, EventArgs e) { Debug.Log("Thermal status has changed."); var currentLevel = Thermometer.CurrentThermalLevel; switch(currentLevel){ case PerformanceLevel.Critical: HandleCriticalTemperature(); break; case PerformanceLevel.High: HandleHighTemperature(); break; default: ResumeNormalOperation(); break; } } private void HandleCriticalTemperature(){ // 执行紧急措施以防止损坏硬件 Application.Quit(); // 作为极端情况下的最后手段 } private void HandleHighTemperature(){ // 减少图形质量设置或其他消耗资源的操作 QualitySettings.SetQualityLevel(0); } private void ResumeNormalOperation(){ // 当温度恢复正常后重新调整应用性能参数 QualitySettings.SetQualityLevel(3); } } ``` 此脚本通过 `Thermometer` 类订阅了系统的热阈值跨越事件,并定义了几种不同级别的应对策略[^1]。 请注意上述代码片段中的类名和成员可能因 SDK 版本差异而有所变动;实际开发过程中应当参照最新官方文档确认具体接口名称与用法。
评论
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值