Red Hat Bugzilla – Bug 247922
kernel 2.6.21-1.3228.fc7 oopses in radix_tree_preload
Last modified: 2008-08-02 19:40:35 EDT
Description of problem:
That oops just happened while retrieving packages in 'yum update'.
The machine in question did not die although an ssh connection
in use become catatonic. Luckily it was possible to get
processor : 0
vendor_id : AuthenticAMD
cpu family : 6
model : 7
model name : AMD Duron(tm) Processor
stepping : 0
cpu MHz : 995.820
cache size : 64 KB
fdiv_bug : no
hlt_bug : no
f00f_bug : no
coma_bug : no
fpu : yes
fpu_exception : yes
cpuid level : 1
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 mtrr pge mca cmov pat pse36
mmx fxsr sse syscall mmxext 3dnowext 3dnow up ts
bogomips : 1992.10
clflush size : 32
and devices on board:
-[0000:00]-+-00.0 Silicon Integrated Systems [SiS] 735 Host
+-01.0-[0000:01]----00.0 ATI Technologies Inc 3D Rage Pro AGP 1X/2X
+-02.0 Silicon Integrated Systems [SiS] SiS85C503/5513 (LPC Bridge)
+-02.1 Silicon Integrated Systems [SiS] SiS961/2 SMBus Controller
+-02.2 Silicon Integrated Systems [SiS] USB 1.0 Controller
+-02.3 Silicon Integrated Systems [SiS] USB 1.0 Controller
+-02.5 Silicon Integrated Systems [SiS] 5513 [IDE]
+-02.7 Silicon Integrated Systems [SiS] AC'97 Sound Controller
\-03.0 Silicon Integrated Systems [SiS] SiS900 PCI Fast Ethernet
Oops trace is attached
Version-Release number of selected component (if applicable):
Never have seen that before
Created attachment 159022 [details]
oops trace from logs
well that's umm, special.
Did this ever happen again ? On more recent kernels perhaps?
To avoid chasing ghosts, if this is still reproducable, it'd be interesting to
know if this box survives a memtest run too.
> Did this ever happen again ? On more recent kernels perhaps?
Not that I am aware of. This is not a box which sits on my desk;
I am rather watching it from a distance. Hence a sigh of relief
that a blocked ssh connection did not mean a total cutoff. :-)
It looks like that the oops quoted was a "special event".
> .... if this box survives a memtest run too.
This is not something I can easily arrange but the machine
in question is in everyday quite extensive use and it looks rather