HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - Linux
- >
- Uhhuh. NMI received. Dazed and confused
Operating System - Linux
1827293
Members
2793
Online
109717
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-31-2009 04:47 PM
07-31-2009 04:47 PM
Uhhuh. NMI received. Dazed and confused
This message was occuring on a Proliant DL580 server. After running Smartstart Diagnostics, the ram and cpu checked out ok. I also booted with HP Proliant Firmware CD (version 7.91), and updated the BIOS for the RAID controllers, hard drives, and system ROM (with the correct supplemental file download to a floppy) after finding the following on HP's knowledge base (take out spaces)
h t t p s : / / w w w 13 . itrc . hp . c o m /service/cki/docDisplay.do?docId=emr_na-c01583480&docLocale=en&admit=109447627+1248981631870+28353475
although my server was not a "G5". This didnt hurt anything, but the server still had the warning message and annoying ever-increasing lockups. It turned out to be a failing network card. After removing the existing network card, and installing a different one the
"Uhhuh. NMI received. Dazed and confused, but trying to continue
You probably have a hardware problem with your RAM chips"
messages have stopped, as well as the server lockups. It was an intermittent hardware failure, which eventually started taking the server down with 10 minutes of booting. Im glad its finally resolved now. I suggest removing any any unecessary hardware from any computer with this error, and if that doesnt elminate the problem - try swapping any hardware you can til you isolate the problem. Although it "suggests" RAM to be the cause - its not always the system RAM....
Good luck
h t t p s : / / w w w 13 . itrc . hp . c o m /service/cki/docDisplay.do?docId=emr_na-c01583480&docLocale=en&admit=109447627+1248981631870+28353475
although my server was not a "G5". This didnt hurt anything, but the server still had the warning message and annoying ever-increasing lockups. It turned out to be a failing network card. After removing the existing network card, and installing a different one the
"Uhhuh. NMI received. Dazed and confused, but trying to continue
You probably have a hardware problem with your RAM chips"
messages have stopped, as well as the server lockups. It was an intermittent hardware failure, which eventually started taking the server down with 10 minutes of booting. Im glad its finally resolved now. I suggest removing any any unecessary hardware from any computer with this error, and if that doesnt elminate the problem - try swapping any hardware you can til you isolate the problem. Although it "suggests" RAM to be the cause - its not always the system RAM....
Good luck
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-17-2009 03:13 PM
08-17-2009 03:13 PM
Re: Uhhuh. NMI received. Dazed and confused
I've seen this behaviour by using the deprecated st.o instead of sg.o with backups.
After switchting to sg.o the problem was solved.
After switchting to sg.o the problem was solved.
Linux system administrator
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-18-2010 05:57 AM
02-18-2010 05:57 AM
Re: Uhhuh. NMI received. Dazed and confused
http://forums11.itrc.hp.com/service/forums/questionanswer.do?threadId=1408342
****
Unix operates with beer.
Unix operates with beer.
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
Support
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP