HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - Linux
- >
- HP Proliant DL 385 / Enterprise Linux 4 / system h...
Operating System - Linux
1832511
Members
4856
Online
110043
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-25-2006 07:52 PM
07-25-2006 07:52 PM
HP Proliant DL 385 / Enterprise Linux 4 / system hangs
Linux Gurus,
I am running Enterprise Linux 4 on HP Proliant DL385 (AMD Opteron Processors). Since last few days, system started hanging. I checked up /var/log/messages file and found following messages getting repeated. Could anybody guide me thru as to why I am getting this message ?
-velu
==============================================
Jul 26 12:37:18 tsus006 kernel: powernow-k8: error - out of sync, fid 0xa 0xe, vid 0xc 0x8
Jul 26 12:37:18 tsus006 kernel: Warning: CPU frequency is 2200000, cpufreq assumed 1800000 kHz.
Jul 26 12:37:20 tsus006 kernel: powernow-k8: error - out of sync, fid 0xe 0xc, vid 0x8 0xa
Jul 26 12:37:23 tsus006 kernel: powernow-k8: error - out of sync, fid 0xc 0xa, vid 0xa 0xc
Jul 26 12:37:31 tsus006 gconfd (gur12378-22465): Exiting
.
.
.
Jul 26 12:45:44 tsus006 kernel: a.out[23472]: segfault at 000000000000005e rip 0
00000358546b146 rsp 0000007fbffff800 error 4
Jul 26 12:45:56 tsus006 kernel: gam_server[23313]: segfault at 0000000000000072
rip 0000003587723dc3 rsp 0000007fbfffe050 error 4
Jul 26 12:48:56 tsus006 kernel: a.out[23671]: segfault at 0000000000000060 rip 0
00000358546b146 rsp 0000007fbffff800 error 4
Jul 26 12:49:25 tsus006 kernel: a.out[23707]: segfault at 0000007fc0000000 rip 0
00000000040056f rsp 0000007fbffff900 error 4
Jul 26 13:00:08 tsus006 kernel: Warning: CPU frequency is 1800000, cpufreq assumed 2200000 kHz.
=============================================
I am running Enterprise Linux 4 on HP Proliant DL385 (AMD Opteron Processors). Since last few days, system started hanging. I checked up /var/log/messages file and found following messages getting repeated. Could anybody guide me thru as to why I am getting this message ?
-velu
==============================================
Jul 26 12:37:18 tsus006 kernel: powernow-k8: error - out of sync, fid 0xa 0xe, vid 0xc 0x8
Jul 26 12:37:18 tsus006 kernel: Warning: CPU frequency is 2200000, cpufreq assumed 1800000 kHz.
Jul 26 12:37:20 tsus006 kernel: powernow-k8: error - out of sync, fid 0xe 0xc, vid 0x8 0xa
Jul 26 12:37:23 tsus006 kernel: powernow-k8: error - out of sync, fid 0xc 0xa, vid 0xa 0xc
Jul 26 12:37:31 tsus006 gconfd (gur12378-22465): Exiting
.
.
.
Jul 26 12:45:44 tsus006 kernel: a.out[23472]: segfault at 000000000000005e rip 0
00000358546b146 rsp 0000007fbffff800 error 4
Jul 26 12:45:56 tsus006 kernel: gam_server[23313]: segfault at 0000000000000072
rip 0000003587723dc3 rsp 0000007fbfffe050 error 4
Jul 26 12:48:56 tsus006 kernel: a.out[23671]: segfault at 0000000000000060 rip 0
00000358546b146 rsp 0000007fbffff800 error 4
Jul 26 12:49:25 tsus006 kernel: a.out[23707]: segfault at 0000007fc0000000 rip 0
00000000040056f rsp 0000007fbffff900 error 4
Jul 26 13:00:08 tsus006 kernel: Warning: CPU frequency is 1800000, cpufreq assumed 2200000 kHz.
=============================================
1 REPLY 1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-25-2006 10:08 PM
07-25-2006 10:08 PM
Re: HP Proliant DL 385 / Enterprise Linux 4 / system hangs
Somewhere, deep in the bowels of RedHat Enterprise Linux 4 Release Notes, there is a sentence like this:
"Dual-core Opteron CPUs are supported only in RedHat ES4 _Update 2_ and above." (emphasis mine)
The reason for this: the kernel on RHES4 "base" installation CDs did not yet have a kernel patch required to properly handle dual-core Opterons.
Recommendation: Register your system to RedHat Network (if not already done) and use up2date to download and install all available updates. If you're using up2date GUI, you must explicitly select updated kernel packages for installation (by default, they are skipped). If you use up2date from the command line, the command is "up2date --force --update".
When the updates are installed, reboot. The system should automatically boot using a new kernel (you can still select an older kernel from the boot menu if necessary). The version string in /etc/redhat-release should now also show that you're now at the latest update level of RedHat ES 4.
"Dual-core Opteron CPUs are supported only in RedHat ES4 _Update 2_ and above." (emphasis mine)
The reason for this: the kernel on RHES4 "base" installation CDs did not yet have a kernel patch required to properly handle dual-core Opterons.
Recommendation: Register your system to RedHat Network (if not already done) and use up2date to download and install all available updates. If you're using up2date GUI, you must explicitly select updated kernel packages for installation (by default, they are skipped). If you use up2date from the command line, the command is "up2date --force --update".
When the updates are installed, reboot. The system should automatically boot using a new kernel (you can still select an older kernel from the boot menu if necessary). The version string in /etc/redhat-release should now also show that you're now at the latest update level of RedHat ES 4.
MK
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
Company
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP