[1.] One line summary of the problem:
Kernel panics after a few hours of heavy ATM traffic.
[2.] Full description of the problem/report:
This machine is planned to be a mirror, so it's transferring a large
amount of data while I'm populating it. After a variable period of time
(a few hours, normally), the machine OOPSes and locks up to the point
that even the magic sysrq keys don't work. If I leave the machine idle
(no network traffic), it seems to stay up indefinately.
[3.] Keywords (i.e., modules, networking, kernel):
networking, kernel.
[4.] Kernel version (from /proc/version):
Linux version 2.3.99-pre6 (root@carroll.cac.psu.edu) (gcc version
egcs-2.91.66 19990314/Linux (egcs-1.1.2 release)) #3 SMP Mon May 1
08:31:10 EDT 2000
[5.] Output of Oops.. message (if applicable) with symbolic information
resolved (see Documentation/oops-tracing.txt)
ksymoops 2.3.4 on i686 2.3.99-pre6. Options used
-V (specified)
-k /proc/ksyms (default)
-l /proc/modules (default)
-o /lib/modules/2.3.99-pre6/ (default)
-m /usr/src/linux/System.map (default)
No modules in ksyms, skipping objects
Warning (read_lsmod): no symbols in lsmod, is /proc/modules a valid
lsmod file?
Unable to handle kernel NULL pointer dereference at virtual address
00000000
c019fed8
*pde = 00000000
Oops: 0002
CPU: 1
EIP: 0010:[<c019fed8>]
Using defaults from ksymoops -t elf32-i386 -a i386
EFLAGS: 00010246
eax: 00000000 ebx: f7b3f180 ecx: 00000286 edx: 00000020
esi: f7e08c40 edi: f7e08c30 ebp: f7e08000 esp: c20bbf08
ds: 0018 es: 0018 ss: 0018
Process swapper (pid: 0, stackpage=c20bb000)
Stack: f7e08000 00000020 00000000 c02d4e40 00000067 c01a054d f7e08000
f7e0a684
c0125085 f7e08000 00000001 c02c1558 00000020 00000007 00124f2a
c02c1558
c02b8ac0 c02b8ad0 00000016 c2abbf74 c2aba000 c010dfde c0108da0
c20ba000
Call Trace: [<c01a054d>] [<c0125085>] [<c0124f20>] [<c010dfde>]
[<c0108da0>] [<c0108da0>] [<c010bfc4>]
[<c0108da0>] [<c0108da0>] [<c0100018>] [<c0108dcd>]
[<c0108e12>] [<c01cc807>] [<c018a04e>]
Code: f0 ff 00 8b 07 c7 00 04 00 00 00 ff 8d 1c 1d 00 00 83 c6 1c
>>EIP; c019fed8 <fore200e_irq_tx+c8/f8> <=====
Trace; c01a054d <fore200e_tasklet+1d/24>
Trace; c0125085 <tasklet_action+55/80>
Trace; c0124f20 <do_softirq+50/88>
Trace; c010dfde <do_IRQ+1ca/1dc>
Trace; c0108da0 <default_idle+0/34>
Trace; c0108da0 <default_idle+0/34>
Trace; c010bfc4 <ret_from_intr+0/20>
Trace; c0108da0 <default_idle+0/34>
Trace; c0108da0 <default_idle+0/34>
Trace; c0100018 <startup_32+18/c7>
Trace; c0108dcd <default_idle+2d/34>
Trace; c0108e12 <cpu_idle+3e/54>
Trace; c01cc807 <vgacon_cursor+1db/1e4>
Trace; c018a04e <set_cursor+6e/80>
Code; c019fed8 <fore200e_irq_tx+c8/f8>
00000000 <_EIP>:
Code; c019fed8 <fore200e_irq_tx+c8/f8> <=====
0: f0 ff 00 lock incl (%eax) <=====
Code; c019fedb <fore200e_irq_tx+cb/f8>
3: 8b 07 mov (%edi),%eax
Code; c019fedd <fore200e_irq_tx+cd/f8>
5: c7 00 04 00 00 00 movl $0x4,(%eax)
Code; c019fee3 <fore200e_irq_tx+d3/f8>
b: ff 8d 1c 1d 00 00 decl 0x1d1c(%ebp)
Code; c019fee9 <fore200e_irq_tx+d9/f8>
11: 83 c6 1c add $0x1c,%esi
Aiee, killing interrupt handler
Kernel panic: Attempted to kill the idle task:
[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)
Linux carroll.cac.psu.edu 2.3.99-pre6 #3 SMP Mon May 1 08:31:10 EDT 2000
i686 unknown
Kernel modules 2.3.11
Gnu C egcs-2.91.66
Binutils 2.9.5.0.22
Linux C Library 2.1.3
Dynamic linker ldd (GNU libc) 2.1.3
Procps 2.0.6
Mount 2.10f
Net-tools 1.54
Console-tools 0.3.3
Sh-utils 2.0
Modules Loaded
[7.2.] Processor information (from /proc/cpuinfo):
processor : 0
vendor_id : GenuineIntel
cpu family : 6
model : 7
model name : Pentium III (Katmai)
stepping : 3
cpu MHz : 598.506870
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 fxsr xmm
bogomips : 1192.76
processor : 1
vendor_id : GenuineIntel
cpu family : 6
model : 7
model name : Pentium III (Katmai)
stepping : 3
cpu MHz : 598.506870
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 fxsr xmm
bogomips : 1196.03
[7.3.] Module information (from /proc/modules):
(no modules loaded)
[7.4.] SCSI information (from /proc/scsi/scsi)
Attached devices:
Host: scsi0 Channel: 00 Id: 00 Lun: 00
Vendor: IBM Model: DMVS09M Rev: 0220
Type: Direct-Access ANSI SCSI revision: 03
Host: scsi0 Channel: 00 Id: 06 Lun: 00
Vendor: DELL Model: 1x3 U2W SCSI BP Rev: 5.35
Type: Processor ANSI SCSI revision: 02
Host: scsi1 Channel: 00 Id: 05 Lun: 00
Vendor: NEC Model: CD-ROM DRIVE:466 Rev: 1.06
Type: CD-ROM ANSI SCSI revision: 02
Host: scsi2 Channel: 00 Id: 15 Lun: 00
Vendor: Dell Model: 8 BAY U2W CU Rev: 0205
Type: Processor ANSI SCSI revision: 03
Host: scsi2 Channel: 02 Id: 00 Lun: 00
Vendor: MegaRAID Model: LD0 RAID5 08068R Rev: 1.01
Type: Direct-Access 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:
- I also tried this with 2.3.99pre3 with ATM-0.75 with the same results.
- I'm getting a lot of these messages in /var/log/messages:
May 4 08:39:55 carroll kernel: fore200e: damaged PDU on 0.0.409
May 4 09:00:06 carroll kernel: fore200e: damaged PDU on 0.0.412
May 4 09:20:15 carroll kernel: fore200e: damaged PDU on 0.0.413
May 4 15:36:36 carroll kernel: fore200e: damaged PDU on 0.0.428
-- Jason Holmes- 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/
This archive was generated by hypermail 2b29 : Sun May 07 2000 - 21:00:18 EST