ProLiant Servers (ML,DL,SL)
cancel
Showing results for 
Search instead for 
Did you mean: 

Non-Maskable Interrupt error.

Non-Maskable Interrupt error.

Hi, I am running a ML310 G1, with MS 2000 Server.

I get the following error every few weeks:

Event Type: Error
Event Source: cpqasm
Event Category: None
Event ID: 4196
Date: 19/08/2005
Time: 22:40:13
User: N/A
Computer: X
Description:
The system encountered a Non-Maskable Interrupt (NMI) prior to this boot. The NMI source was: PCI bus error, slot 0.
Data:
0000: 00 00 00 00 09 00 4e 00 ......N.
0008: 00 00 00 00 64 10 35 c4 ....d.5Ä
0010: 00 00 00 00 00 00 00 00 ........
0018: 00 00 00 00 00 00 00 00 ........
0020: 00 00 00 00 00 00 00 00 ........

At the same time I get the following in Insight, Integrated Management Log:
POST Error: A Critical Error occurred prior to this power-up 8/19/2005 10:37PM 8/19/2005 10:37PM 1
ASR Detected by System ROM 8/19/2005 10:37PM 8/19/2005 10:37PM 1
PCI Bus Error (Slot 0, Bus 0, Device 15, Function 0)

Slot 0, Bus 0, Device 15 is listed as IDE Controller

This error happens when I am doing backups using a tape drive that is SCSI connected.

Help please???

Regards,

Pieter
8 REPLIES
Terry Hutchings
Honored Contributor

Re: Non-Maskable Interrupt error.

Are the hards drives ide based or are they scsi?
The truth is out there, but I forgot the URL..

Re: Non-Maskable Interrupt error.

Hi,

No, the only thing connected to IDE is a dvd/cd rom drive.

thanks

Re: Non-Maskable Interrupt error.

Does anyone know how to deal with this kind of problem?
Dave_180
Valued Contributor

Re: Non-Maskable Interrupt error.

In your backup configuration - do you have all media selected? Is it trying to back up an IDE device - can't read it so it fails?

About the only other thing I could come up with is an odd driver loaded by the backup software.

Re: Non-Maskable Interrupt error.

Hi

Thanks for reply. No IDE media selected for backup. This error only happens once every few weeks.

I have now raised a call with HP and gave them all the details. I am awaiting there reply on this.

Cheers
Eric Thostenson
Occasional Visitor

Re: Non-Maskable Interrupt error.

I'm having this exact problem with a DL360 G2. It won't boot at all, and I can't boot it to a floppy or CD-ROM. Please let us know what is is. Thanks.

Re: Non-Maskable Interrupt error.

Hi Eric,

I raised a call with HP support for this issue and they replied by telling me to update the system ROM. I have not done it yet since my problem is only happens once every few weeks. So even if I do it, it will be difficult to tell if it made a difference.

Anyway I included the reply with the links, for downloading and installing latest system ROM, that I got from HP. However, I don't know how you are going to update system rom if you can't even boot your system.

Best of luck and post a reply if you get it to work.

Regards,

Pieter

HP Support response:

Thank you for the log reports sent to us. I went through the log report ( survey.txt file) and Found that the relevant error message is suggesting the system ROM update for the server I am sending you the link for the customer advisory (which suggest System ROM update) and also link to download System ROM for the server ML310



#1 Customer advisory ID: EL031230_CW01 available at

http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?objectID=PSD_EL031230_CW01



#2 Link to download the System ROM



http://h18023.www1.hp.com/support/files/server/us/download/21964.html



Please Update the System ROM from the above mentioned link.
Sean Marshall_1
Frequent Advisor

Re: Non-Maskable Interrupt error.

Hello Peter:

For the most part NMI = PCI. I would suggest taking a look at the PCI bus. The error that you listed is stating that slot 0 bus 0 device 15 .... That is showing as being an integrated device. What SCSI controller is it that you are using? Is it the integrated one? or PCI? If it is integrated and you have applied the latest BIOS ( http://h18000.www1.hp.com/support/files/server/us/download/21964.html ) you may want to try a PCI SCSI adapter and see if it resolves the issue. If it is a PCI card then try to swap it out.



Hope that helps