1833758 Members
2753 Online
110063 Solutions
New Discussion

HP Crashes

 
KapilRaj
Honored Contributor

HP Crashes

Hi friends,
I hv an HP D370/2 with HPUX 10.20 with Oracle 7.3 . Recently the machine started crashing. No H/W or S/W changes hv been made.

M/C crashes while working with following error

kernel couldnot detect this crash
spinlock timeout failure.
the spinlock code has not failed
instead some spinlock using code has failed to release a spinlock
soon enough
spinlock deadlock
panic : (display = 0xb8009 flag=0x0)

Any feedback,

Kapil Raj

Nothing is impossible
6 REPLIES 6
Cheryl Griffin
Honored Contributor

Re: HP Crashes

Use the Q4 instructions in the Knowledge Base on pre-processing the crash. You will need to open a support case with the HP Response Center and forward the crash info to be analyzed.

"Downtime is a Crime."
Anthony Goonetilleke
Esteemed Contributor

Re: HP Crashes

this could mean basically many things, if I were you I would apply all the 10.20 patches to do with spinlock there are know crashes to do with this.

Ofcourse use 'match target selection' before applying these...

s800 10.20 select(2) system call cumulative patch(PHKL_14283)
s800 10.20 SIG_IGN/SIGCLD,LVM,JFS,PCI/SCSI cumulative patch(PHKL_16751)
s800 10.20 Flock Manager fix(PHKL_16898)
s800 10.20 ki/nfs, vasusage, ACE 2 bundle cumulative patch(PHKL_17574)
s800 10.20 fix vfork(2)-induced panic under memory pressure(PHKL_19890)
s800 10.20 tlb cumulative patch(PHKL_19906)
s800 10.20 Fix for kthread b_sema wait queue corruption(PHKL_20850)
s800 10.20 WSIO SCSI cumulative patch(PHKL_21085)
s800 10.20 Visualize graphics; ITE; HIL; PS/2(PHKL_22088)
s800 10.20 HyperFabric B.10.20.0[0-3] cumulative patch(PHNE_16198)
s800 10.20 HP-PB Token Ring (J2166A) Cumulative patch(PHNE_17536)
s700_800 10.20 R5.1 SNAplus2 Link cumulative patch(PHNE_18487)
s800 10.20 HP-PB FDDI B.10.20.0[0-9] Cumulative patch(PHNE_19517)
s700_800 10.20 1000Base-SX B.10.20.0[123579] cumul. patch(PHNE_19564)
s700_800 10.20 EISA FDDI B.10.20.[01-11] cumulative patch(PHNE_20009)
s700_800 10.20 HSC FDDI B.10.20.[01-11] cumulative patch(PHNE_20010)
s800 10.20 cumulative ARPA Transport patch(PHNE_20834)
s700_800 10.20 PCI FDDI B.10.20.[01,03-05,09-11] cum. patch(PHNE_20875)
s700_800 10.20 HSC 100BT lan cumulative patch(PHNE_20893)
s700_800 10.20 NFS Kernel General Rel & Perf Patch(PHNE_20957)
s800 10.20 HP-PB 100BT cumulative patch(PHNE_20970)
s800 10.20 NIO Datakit 4.20.0[123] cumulative patch(PHNE_21200)
s800 10.20 2.23 ACC X.25/9000 Support (HP-PB) Patch(PHNE_21365)
s700_800 10.20 2.23 ACC X.25/9000 Support (EISA) Patch(PHNE_21366)
s800 10.20 2.40-2.40.02 X.25/ACC Accessory Product (NIO)(PHNE_21367)
s700_800 10.20 EISA 100BT cumulative patch(PHNE_21373)
s800 10.20 HSC Fibre Channel B.10.20.2[023] cumul. patch(PHNE_21923)
s800 10.20 Fibre Channel Mass Storage Driver Patch(PHSS_20418)
Minimum effort maximum output!
CHRIS_ANORUO
Honored Contributor

Re: HP Crashes

Have you installed the latest 10.20 patches for kernel? Please do so once the system comes up.
When We Seek To Discover The Best In Others, We Somehow Bring Out The Best In Ourselves.
Stefan Farrelly
Honored Contributor

Re: HP Crashes


You need to keep your ptaches up-to-date. Check this link, PHNE_20875 fixes your exact error;

http://europe-support.external.hp.com/wpsl/bin/doc.pl/screen=wpslDisplayPatch/sid=1e706ea31d6148114e?PATCH_PATH=/hp-ux_patches/s700_800/10.X/PHNE_20875&HW=s800&OS=10.20
Im from Palmerston North, New Zealand, but somehow ended up in London...
Andy Monks
Honored Contributor

Re: HP Crashes

Stefan

To say from just the message 'spinlock deadlock' that one specific patch fixes the problem is impossible. There are mean causes for this error and depending on what patches he already has on the machine which one might fix it.

At best a full stack trace is required, but with spinlock panic's this is rarely enough so he should really send the dump into hp for them to analyze

Andy 'who analyzes dumps for a living at hp'
Stefan Farrelly
Honored Contributor

Re: HP Crashes


I did a complete search on the HP intranet for the error message listed and thats the ONLY patch that came back with that error. Sounds reasonable to me to install just that patch to see if it fixes it.

However, thats no reason not to keep systems uptodate with the latest GR bundle which will incorporate a whole suite of important patches which should definitely fix the problem, so I advise installing the latest GR bundle if the patch above doesnt fix it, but installing a GR bundle takes a lot more time and effort than a single patch.

I used to analyze dumps for a living at HP but moved on to more challenging things.
Im from Palmerston North, New Zealand, but somehow ended up in London...