Created attachment 313870 [details] kernelpanic screenshot Description of problem: Kernel Panic after Update from 09.08.2008 Version-Release number of selected component (if applicable): How reproducible: yes Steps to Reproduce: 1.up2date -u install the Kernel kernel-smp-2.6.9-78.0.1.EL+ernel-smp-2.6.9-78.EL 2.reboot the server see screenshot 3.the server booting with kernel panic on all server (6 mashines HP ProLiant ProLiant DL360 G4) the follow versions not working kernel-2.6.9-78.EL kernel-2.6.9-78.0.1.EL kernel-smp-2.6.9-78.EL kernel-smp-2.6.9-78.0.1.EL kernel panic (screenshot) the kernel 2.6.9-67.0.20.ELsmp work Actual results: Expected results: Additional info:
Addendum, so we hang it looks at the server reboot, Not at start Regards Netzi
Netzi, can you send us a sysreport from your system? Thanks, P.
Also, if you cannot hook up a serial port to the system to capture the panic, could you boot with the option "vga=791" and send us a screenshot of that? Thanks, P.
Created attachment 314116 [details] Sysreport
Created attachment 314118 [details] MD5
(In reply to comment #3) > Also, if you cannot hook up a serial port to the system to capture the panic, > could you boot with the option "vga=791" and send us a screenshot of that? > > Thanks, > > P. Hello Prarit, the servers are located at the customer's remote is maintained. All system updates were recorded. The Sysreport is appended Many greetings Günther
Günther, Please use the Virtual Serial Console and send us a log file of the boot/crash output.
(In reply to comment #7) > Günther, > > Please use the Virtual Serial Console and send us a log file of the boot/crash > output. Hi Tony, access to the serial console is not possible because the server in the RZ are remote and only by us. There are production systems. What can I do to give you information? Many greetings Guenther
Günther, The Virtual Serial Port can be accessed remotely. Follow this link. http://h20000.www2.hp.com/bc/docs/support/SupportManual/c00263709/c00263709.pdf
Guenther, Any progress? Any more information?
The last kernel update up2date generated over this error no longer Regards Guenther
This reason for this BZ appears to have been resolved when customer applied hp up2date to platform. Can we close this BZ?
Apparently the fw update fixed the problem. I'm closing this bug.