Bug 426414

Summary: "yum update" from rhel5 to rhel5.1 caused panic
Product: Red Hat Enterprise Linux 5 Reporter: GV Govindasamy <gvg>
Component: kernelAssignee: Red Hat Kernel Manager <kernel-mgr>
Status: CLOSED INSUFFICIENT_DATA QA Contact: Red Hat Kernel QE team <kernel-qe>
Severity: high Docs Contact:
Priority: low    
Version: 5.1CC: prarit, ricardo.labiaga
Target Milestone: rc   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2009-11-11 14:42:40 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
console screen of the panic none

Description GV Govindasamy 2007-12-20 21:24:45 UTC 
When upgraded from 

Red Hat Enterprise Linux Server release 5 (Tikanga)
Linux kc2b2-e0 2.6.18-8.1.3.el5 #1 SMP Mon Apr 16 15:54:14 EDT 2007 x86_64
x86_64 x86_64 GNU/Linux

to

Linux kc25b1-e0 2.6.18-53.el5 #1 SMP Wed Oct 10 16:34:19 EDT 2007 x86_64 x86_64
x86_64 GNU/Linux
Red Hat Enterprise Linux Server release 5.1 (Tikanga)

I did "yum update" and rebooted. hit the panic - that is attached.

Recycling the system again brought the system back up.
Comment 1 GV Govindasamy 2007-12-20 21:24:45 UTC 
Created attachment 290190 [details]
console screen of the panic
Comment 2 Linda Wang 2008-05-12 18:37:24 UTC 
the screen shot has only half of the kernel panic message, can you please
send up the upper half of the kernel panic message?
Comment 3 GV Govindasamy 2008-05-13 11:20:07 UTC 
Sorry that's how much I could capture at that time.
Comment 4 Prarit Bhargava 2008-09-19 11:32:11 UTC 
GV,

Could you try booting with vga=791 as a boot argument.  If your console supports it this will change your console resolution and potentially give you more of the kernel panic output.

P.