lkml.org 
[lkml]   [1999]   [Jul]   [18]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
SubjectOops when bringing up eth0
Date
From
[1.] One line summary of the problem:
Oops generated when loading tulip module at bootup.

[2.] Full description of the problem/report:
At bootup, an oops was generated when eth0 was being brought up. The oops
came up when the tulip module was being loaded.

[3.] Keywords (i.e., modules, networking, kernel):

[4.] Kernel version (from /proc/version):
2.2.10-ac8

[5.] Output of Oops.. message (if applicable) with symbolic information
resolved (see Documentation/oops-tracing.txt)

Options used: -V (default)
-o /lib/modules/2.2.10-ac8/ (default)
-k /proc/ksyms (default)
-l /proc/modules (default)
-m /usr/src/linux/System.map (default)
-c 1 (default)

You did not tell me where to find symbol information. I will assume
that the log matches the kernel and modules that are running right now
and I'll use the default options above for symbol resolution.
If the current kernel and/or modules do not match the log, you can get
more accurate output by telling me the kernel version and where to find
map, modules, ksyms etc. ksymoops -h explains the options.

Unable to handle kernel NULL pointer dereference at virtual address 00000000
current->tss.cr3 = 07e58000, %cr3 = 07e58000
*pde = 00000000
Oops: 0002
CPU: 0
EIP: 0010:[<c800d71e>]
EFLAGS: 00010246
eax: 00000000 ebx: 00000006 ecx: 00000174 edx: c033f2c8
esi: c801308c edi: 00000000 ebp: 00000000 esp: c7dffe2c
ds: 0018 es: 0018 ss: 0018
Process insmod (pid: 265, process nr: 10, stackpage=c7dff000)
Stack: 00140007 c8012f38 c7dfe000 c011a0d3 c7e4f148 c0096460 c3e89e40 c0096460
00000001 c8011612 00000008 00000246 c3e89e40 00000014 d4300001 0000000b
0000d400 c7dfe000 c011a0d3 c7e4f16c 03c82067 00000000 00000000 00000000
Call Trace: [<c8012f38>] [<c011a0d3>] [<c8011612>] [<c011a0d3>] [<c800d26e>] [<c800d000>] [<c800d04e>]
[<c800d000>] [<c8011405>] [<c0114f63>] [<c800d000>] [<c8013294>] [<c800d048>] [<c0108ee8>] [<c800d000>]
Code: f3 ab 8b 94 24 e8 00 00 00 89 6a 5c a1 80 30 01 c8 89 45 0c

>>EIP: c800d71e <_end+7e11cda/7ec4608>
Trace: c8012f38 <_end+7e174f4/7ec4608>
Trace: c011a0d3 <do_anonymous_page+6f/80>
Trace: c8011612 <_end+7e15bce/7ec4608>
Trace: c011a0d3 <do_anonymous_page+6f/80>
Trace: c800d26e <_end+7e1182a/7ec4608>
Trace: c800d000 <_end+7e115bc/7ec4608>
Trace: c800d04e <_end+7e1160a/7ec4608>
Trace: c800d000 <_end+7e115bc/7ec4608>
Code: c800d71e <_end+7e11cda/7ec4608> 00000000 <_EIP>: <===
Code: c800d71e <_end+7e11cda/7ec4608> 0: f3 ab repz stosl %eax,%es:(%edi) <===
Code: c800d720 <_end+7e11cdc/7ec4608> 2: 8b 94 24 e8 00 00 00 movl 0xe8(%esp,1),%edx
Code: c800d727 <_end+7e11ce3/7ec4608> 9: 89 6a 5c movl %ebp,0x5c(%edx)
Code: c800d72a <_end+7e11ce6/7ec4608> c: a1 80 30 01 c8 movl 0xc8013080,%eax
Code: c800d72f <_end+7e11ceb/7ec4608> 11: 89 45 0c movl %eax,0xc(%ebp)

11 warnings issued. Results may not be reliable.

[6.] A small shell script or example program which triggers the
problem (if possible)

[7.] Environment
[7.1.] Software (add the output of the ver_linux script here)
-- Versions installed: (if some fields are empty or looks
-- unusual then possibly you have very old versions)
Linux dilbert 2.2.10-ac8 #1 Sun Jul 4 14:08:03 EDT 1999 i586 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 ppp slhc pnp emu8k opl3 sb uart401 midi soundbase sndshield tulip

[7.2.] Processor information (from /proc/cpuinfo):
processor : 0
vendor_id : AuthenticAMD
cpu family : 5
model : 8
model name : AMD-K6(tm) 3D processor
stepping : 0
cpu MHz : 350.802158
fdiv_bug : no
hlt_bug : no
sep_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 mce cx8 sep mmx 3dnow
bogomips : 699.60

[7.3.] Module information (from /proc/modules):
ppp 20012 2 (autoclean)
slhc 4328 1 (autoclean) [ppp]
pnp 45748 0
emu8k 38600 0
opl3 13228 0
sb 31980 0
uart401 6740 0 [sb]
midi 27528 0 [pnp emu8k opl3 sb uart401]
soundbase 480152 0 [pnp emu8k opl3 sb uart401 midi]
sndshield 4300 0 [pnp emu8k opl3 sb uart401 midi soundbase]
tulip 25252 (uninitialized)

[7.4.] SCSI information (from /proc/scsi/scsi)
Attached devices:
Host: scsi0 Channel: 00 Id: 00 Lun: 00
Vendor: QUANTUM Model: VIKING 2.3 NSE Rev: 8808
Type: Direct-Access ANSI SCSI revision: 02
Host: scsi0 Channel: 00 Id: 01 Lun: 00
Vendor: QUANTUM Model: VIKING 4.5 NSE Rev: 880R
Type: Direct-Access ANSI SCSI revision: 02
Host: scsi0 Channel: 00 Id: 06 Lun: 00
Vendor: TOSHIBA Model: CD-ROM XM-6201TA Rev: 1037
Type: CD-ROM ANSI SCSI revision: 02

[7.5.] Other information that might be relevant to the problem
(please look in /proc and include all information that you
think to be relevant):
[X.] Other notes, patches, fixes, workarounds:
Hasn't had a problem before. The only noticable difference is that the disks
hit the maximum mount count and were checked during boot.

-
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/

\
 
 \ /
  Last update: 2005-03-22 13:53    [W:0.037 / U:0.472 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site