- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - Linux
- >
- HP / PROLIANT / DL180-G6 crash and unfamiliar err...
Operating System - Linux
1753620
Members
5621
Online
108797
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
Discussions
Discussions
Forums
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
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
тАО04-07-2011 06:35 AM
тАО04-07-2011 06:35 AM
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
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
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-08-2011 02:27 AM
тАО04-08-2011 02:27 AM
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
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
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-08-2011 02:50 AM
тАО04-08-2011 02:50 AM
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 ?
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 ?
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.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP