System Administration
cancel
Showing results for 
Search instead for 
Did you mean: 

Re: HP / PROLIANT / DL180-G6 crash and unfamiliar errors

 
Highlighted
Advisor

HP / PROLIANT / DL180-G6 crash and unfamiliar errors

Hi,

we had a server crash at
reboot system boot 2.6.18-164.el5 Thu Apr 7 06:24 (01:44)

and below are the messages that seemed most relevant to the error reproduced around the reboot/crash time

Apr 7 06:24:28 pinger-edge1-dtc-1 kernel: usbcore: registered new driver hiddev
Apr 7 06:24:28 pinger-edge1-dtc-1 kernel: usbcore: registered new driver usbhid
Apr 7 06:24:28 pinger-edge1-dtc-1 kernel: drivers/usb/input/hid-core.c: v2.6:USB HID core driver
Apr 7 06:24:28 pinger-edge1-dtc-1 kernel: PNP: No PS/2 controller found. Probing ports directly.
Apr 7 06:24:28 pinger-edge1-dtc-1 kernel: Failed to disable AUX port, but continuing anyway... Is this a SiS?
Apr 7 06:24:28 pinger-edge1-dtc-1 kernel: If AUX port is really absent please use the 'i8042.noaux' option.
Apr 7 06:24:28 pinger-edge1-dtc-1 kernel: serio: i8042 KBD port at 0x60,0x64 irq 1
Apr 7 06:24:28 pinger-edge1-dtc-1 kernel: mice: PS/2 mouse device common for all mice
Apr 7 06:24:28 pinger-edge1-dtc-1 kernel: md: md driver 0.90.3 MAX_MD_DEVS=256, MD_SB_DISKS=27
Apr 7 06:24:28 pinger-edge1-dtc-1 kernel: md: bitmap version 4.39

if i understand correctly kernel/hid-core.c is looking for PS/2 mouse/controller and when it doesn't find one kernel tries to disable AUX port detection routine.

as a preventive measure I have updated the BIOS to latest release and disabled 'Legacy USB support" from BIOS.

wonder what exactly is the problem and right solution because we have about dozen other this model of severs .

PS: should i attach entire /varlog/messages ? is that a normal practice ?


thanks
Tariq
2 REPLIES 2
Highlighted
Frequent Advisor

Re: HP / PROLIANT / DL180-G6 crash and unfamiliar errors

The quoted log messages do not reveal the cause for your crash. You should provide at least the kernel oops message with a call trace of the commands that were executed prior the crash. You will find that in /var/log/messages.

The best method to debug a kernel panic on RHEL based systems is to analyze a kernel dump. You will need to setup kdump for this:

http://www.mindtwist.de/main/linux/11-red-hat/27-how-to-configure-kernel-dumps-on-rhel-5.html
Highlighted
Advisor

Re: HP / PROLIANT / DL180-G6 crash and unfamiliar errors

Hey , thx for the support .

It was a hard panic/crash and don't see any oops messages/warnings . didn't have kdump support for the installed kernel either :( but now going to consider it . anything else I can do ? will cli crash be any help or it also needs a kernel dump file ?