FIRMWARE BUG – THE BIOS HAS CORRUPTED HW-PMU RESOURCES
2017-08-22 00:50
831 查看
If you’re trying to install CentOS 7 on HP server and you receive the error from the caption, don’t worry – you’re not alone. According to Google, there are about 48400 results related to this topic
The fix is still not available and according to HP, the problem is related to “Processor Power and Utilization Monitoring” function which should be disabled to fix this mess.
Affected servers:
– All ProLiant Gen8 Servers
– ProLiant DL580 G7
– ProLiant BL620 G7
– ProLiant BL680 G7
How to disable “Processor Power and Utilization Monitoring”:
– enter BIOS (press F9 during boot)
– press CTRL+A (Service Option is hidden by default)
– select “Service Options” -> Processor Power and Utilization Monitoring -> Disable
Press F10 to save and exit and reboot the server.
More information can be found on the next links:
https://bugs.centos.org/view.php?id=5493
http://h20565.www2.hp.com/hpsc/doc/public/display?sp4ts.oid=5227546&docId=emr_na-c03265132&lang=en&cc=us
转自：http://www.serveradminblog.com/2015/04/firmware-bug-the-bios-has-corrupted-hw-pmu-resources/
The fix is still not available and according to HP, the problem is related to “Processor Power and Utilization Monitoring” function which should be disabled to fix this mess.
Affected servers:
– All ProLiant Gen8 Servers
– ProLiant DL580 G7
– ProLiant BL620 G7
– ProLiant BL680 G7
How to disable “Processor Power and Utilization Monitoring”:
– enter BIOS (press F9 during boot)
– press CTRL+A (Service Option is hidden by default)
– select “Service Options” -> Processor Power and Utilization Monitoring -> Disable
Press F10 to save and exit and reboot the server.
More information can be found on the next links:
https://bugs.centos.org/view.php?id=5493
http://h20565.www2.hp.com/hpsc/doc/public/display?sp4ts.oid=5227546&docId=emr_na-c03265132&lang=en&cc=us
转自：http://www.serveradminblog.com/2015/04/firmware-bug-the-bios-has-corrupted-hw-pmu-resources/
内容来自用户分享和网络整理，不保证内容的准确性，如有侵权内容，可联系管理员处理 
相关文章推荐
- jvm bug A fatal error has been detected by the Java Runtime Environment:
- [Bug]The maximum array length quota (16384) has been exceeded while reading XML data.
- BUG: Cannot load from mysql.proc. The table is probably corrupted
- The data couldn’t be read because it has been corrupted
- JAVA VM bug ：A fatal error has been detected by the Java Runtime Environment
- bug_ _fragment_“The specified child already has a parent. You must call removeView＂的解决以及产生的原因
- This may be due to a corruption of the heap, which indicates a bug in *.exe or any of the DLLs it has loaded.
- this may be due to a corruption of the heap, which indicates a bug in ... or any of the DLLs it has
- Supported orientations has no common orientation with the application crash bug on iPad
- The data couldn’t be read because it has been corrupted
- [webpack]我所遇见的bug:[babel] note:the code generator has deoptimised the styling...
- BUG: Cannot load from mysql.proc. The table is probably corrupted
- [bug]The file ‘/xxx/xxx.aspx’ has not been pre-compiled, and cannot be requested
- SAPUI5教程——The project is corrupted because its '.user.project.json' file has an invalid JSON
- A fatal error has been detected by the Java Runtime Environment(jdk 1.6的一个BUG)
- 修复mysql 5.1升级至5.5出现的BUG: Cannot load from mysql.proc. The table is probably corrupted
- android学习之BUG——The connection to adb is down, and a severe error has occured.
- 【邂逅BUG】Namespace declaration statement has to be the very first statement in the script
- 解决bug：The content of the adapter has changed but ListView did not receive a notification
- springboot 中遇到BUG {Cannot forward to error page for request [/xxx] as the response has already ...}