2.2.10 OOPS in kmem_free, and does 'stepping' need to match?

Stephen Rust (steve@tp.org)
Sat, 19 Jun 1999 15:07:04 -0400 (EDT)


Hi,

I have a dual processor setup which has been commonly OOPSing in
kmem_free. My first question is, does stepping between the two CPU's
need to match up? My CPU0 is stepping 2, while my CPU1 is stepping 0.
Would this cause any problem possibly? I appreciate any advice on this
matter.

I've included my cpu info, the OOPS run through ksymoops below. Thanks
for any help that anyone can offer.

Steve

-------------
cat /proc/cpuinfo

processor : 0
vendor_id : GenuineIntel
cpu family : 6
model : 5
model name : Pentium II (Deschutes)
stepping : 2
cpu MHz : 331.929042
cache size : 512 KB
fdiv_bug : no
hlt_bug : no
sep_bug : no
f00f_bug : no
coma_bug : no
fpu : yes
fpu_exception : yes
cpuid level : 2
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca
cmov pat pse36 mmx osfxsr
bogomips : 330.96

processor : 1
vendor_id : GenuineIntel
cpu family : 6
model : 5
model name : Pentium II (Deschutes)
stepping : 0
cpu MHz : 331.929042
cache size : 512 KB
fdiv_bug : no
hlt_bug : no
sep_bug : no
f00f_bug : no
coma_bug : no
fpu : yes
fpu_exception : yes
cpuid level : 2
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca
cmov pat pse36 mmx osfxsr
bogomips : 331.78

OOPS
=========

Unable to handle kernel NULL pointer dereference at virtual address
00000000
current->tss.cr3 = 03c63000, %cr3 = 03c63000
*pde = 00000000
Oops: 0002
CPU: 1
EIP: 0010:[<c01230c7>]
EFLAGS: 00010286
eax: 00000040 ebx: c2111460 ecx: 0000004a edx: 00000037
esi: c032f680 edi: 00000286 ebp: 40104000 esp: c34afc3c
ds: 0018 es: 0018 ss: 0018
Process sh (pid: 16724, process nr: 52, stackpage=c34af000)
Stack: c2fdf9c0 00012000 c211149c c011e5d6 c011e5f5 c032f680 c2111460
c34ae000
c34ae000 c01f6397 c1606800 c2111960 c012d318 c2fdf9c0 c34ae000
c34afdb0
c01f6397 c1606800 00000000 c012d46d fffffff9 c34afdb0 c01f6397
c29ef0c0
Call Trace: [<c011e5d6>] [<c011e5f5>] [<c01f6397>] [<c012d318>]
[<c01f6397>] [<c012d46d>] [<c01f6397>]
[<c01357fc>] [<c011f5d8>] [<c01f6394>] [<c012d262>] [<c012d9d3>]
[<c012dc13>] [<c012dc38>] [<c0108043>]
[<c010915c>]
Code: c7 05 00 00 00 00 00 00 00 00 eb 10 90 56 53 68 1e 48 1f c0

>>EIP: c01230c7 <kmem_cache_free+173/198>
Trace: c011e5d6 <exit_mmap+ae/108>
Trace: c011e5f5 <exit_mmap+cd/108>
Trace: c01f6397 <tvecs+3477/b905>
Trace: c012d318 <exec_mmap+3c/120>
Trace: c01f6397 <tvecs+3477/b905>
Trace: c012d46d <flush_old_exec+71/1e0>
Trace: c01f6397 <tvecs+3477/b905>
Trace: c01357fc <load_elf_binary+5d8/d4c>
Trace: c010915c <system_call+34/38>
Code: c01230c7 <kmem_cache_free+173/198> 00000000 <_EIP>: <===
Code: c01230c7 <kmem_cache_free+173/198> 0: c7 05 00 00 00 00
00 movl $0x0,0x0 <===
Code: c01230ce <kmem_cache_free+17a/198> 7: 00 00 00
Code: c01230d1 <kmem_cache_free+17d/198> a: eb 10
jmp c01230e3 <kmem_cache_free+18f/198>
Code: c01230d3 <kmem_cache_free+17f/198> c: 90
nop
Code: c01230d4 <kmem_cache_free+180/198> d: 56
pushl %esi
Code: c01230d5 <kmem_cache_free+181/198> e: 53
pushl %ebx
Code: c01230d6 <kmem_cache_free+182/198> f: 68 1e 48 1f c0
pushl $0xc01f481e

ver_linux
---------

Linux gate.tyorl.org 2.2.10 #41 SMP Mon Jun 14 19:38:15 CDT 1999 i686
unknown
Kernel modules 2.1.121
Gnu C egcs-2.91.66
Binutils 2.9.1.0.23
Linux C Library 2.1.1
Dynamic linker ldd (GNU libc) 2.1.1
Procps 2.0.2
Mount 2.9o
Net-tools 1.51
Kbd [option...]
Sh-utils 1.16
Modules Loaded

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/