Red Hat Bugzilla – Bug 353851
kernel panic after kernel update
Last modified: 2007-11-30 17:12:20 EST
Description of problem:
kernel panic after update kernel from kernel-2.6.21-1.3194 to 2.6.22
Version-Release number of selected component (if applicable):
yum update kernel
Steps to Reproduce:
1.yum update kernel -y
processor : 0
vendor_id : AuthenticAMD
cpu family : 15
model : 47
model name : AMD Athlon(tm) 64 Processor 3000+
stepping : 2
cpu MHz : 1800.000
cache size : 512 KB
fpu : yes
fpu_exception : yes
cpuid level : 1
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov
pat pse36 clflush mmx fxsr sse sse2 syscall nx mmxext fxsr_opt lm 3dnowext 3dnow
up pni lahf_lm
bogomips : 3607.41
TLB size : 1024 4K pages
clflush size : 64
cache_alignment : 64
address sizes : 40 bits physical, 48 bits virtual
power management: ts fid vid ttp tm stc
Created attachment 238801 [details]
screenshot after kernel panic
Created attachment 238841 [details]
Created attachment 238851 [details]
*** Bug 255861 has been marked as a duplicate of this bug. ***
There may be settings in the system BIOS screens that enable/disable USB legacy
keyboard emulation, please try changing the settings if they are there.
No. in my BIOS this setting not present.
(In reply to comment #5)
> There may be settings in the system BIOS screens that enable/disable USB legacy
> keyboard emulation, please try changing the settings if they are there.
No. In my BIOS this setting not present.
Only "Legacy USB support" set in auto.
If you can change "legacy usb support", try that.
I tried. No effect. kernel panic again
If a function faults at +0, it very obviously is some kind of an annotation
error or module loading error. Maybe an extraneous __init somewhere.
Something has gone very wrong. The code at that address is all zeros. This may
be caused by the sparsemem memory allocation bug that was recently fixed. Have
you tried 126.96.36.199-21?