Oops on 2.2.0

Tim Hockin (tphocki@www.orl.ilstu.edu)
Wed, 27 Jan 1999 16:23:36 -0600 (EST)


I have run across an Oops on 2.2.0. It seems to occur under random
conditions, after various lengths of uptime (ranging from 5 minutes to 3
hours so far). A colleague wrote the message down, so there may be mistakes
in the translation, but i don't think so.

The system is a Dual Pentium-2 400, 256 MB, EATA-DMA RAID controller on a
Tyan 1892D board (I am pretty sure that is all correct). It has been
running great under 2.0.3x.

I am not sure how to proceed, or what I can do to help further. They system
is once again under 2.0.35

here is my oops text, followed by my ksymoops output:
--------
unable to handle kernel NULL pointer dereference at virtual address 00000080
current->tss.cr3 = 03047000, %cr3 = 03047000
*pde = 00000000
Oops: 0000
CPU: 0
EIP: 0010:[<c018d04d>]
EFLAGS: 00010296

eax: 00000000 ebx: c0095260 ecx: 00000082 edx: c2930a08
esi: c0095260 edi: 00000000 ebp: c01d02e0 esp: c2937f40
ds: 0018 es: 0018 ss: 0018
Process procmail (pid 1242, process nr: 36, stackpage = c2937000)
Stack: 00000000 c01202c0 c3a2f168 4004100d c018cbe2 c01d02c0 c000077a0 00000001
00000000 0000000a c2057940 40041008 c010a455 0000000a c01d02c0 c2937fc4
c01bfb1c 000000a0 c00077a0 0000000a c010edd4 0000000a c2937fc4 c00077a0
Call Trace: [<c0180be2>] [<c010a455>] [<c010edd4>] [<c010a590>] [<c0108c9c>]

Code: 8b b8 80 00 00 00 8b 43 60 83 00 02 0d 00 00 00 c0 8a 00 3c
Aiee, killing interupt handler
wait_on_irq, CPU1:
irq: 1 [10]
bh: 0 [00]
<[c010a2d9]><c01146a9]><c01477b1]><[c0126722]><[c0108c00]>

---

Options used: -v /usr/src/linux-2.2.0/vmlinux (specified) -o /lib/modules/2.2.0/ (specified) -K (specified) -l /proc/modules (default) -m /usr/src/linux-2.2.0/System.map (specified) -c 1 (default)

No modules in ksyms, skipping objects No ksyms, skipping lsmod unable to handle kernel NULL pointer dereference at virtual address 00000080 current->tss.cr3 = 03047000, %cr3 = 03047000 *pde = 00000000 Oops: 0000 EIP: 0010:[<c018d04d>] EFLAGS: 00010296 eax: 00000000 ebx: c0095260 ecx: 00000082 edx: c2930a08 esi: c0095260 edi: 00000000 ebp: c01d02e0 esp: c2937f40 ds: 0018 es: 0018 ss: 0018 Stack: 00000000 c01202c0 c3a2f168 4004100d c018cbe2 c01d02c0 c000077a0 00000001 00000000 0000000a c2057940 40041008 c010a455 0000000a c01d02c0 c2937fc4 c01bfb1c 000000a0 c00077a0 0000000a c010edd4 0000000a c2937fc4 c00077a0 Call Trace: [<c0180be2>] [<c010a455>] [<c010edd4>] [<c010a590>] [<c0108c9c>] Code: 8b b8 80 00 00 00 8b 43 60 83 00 02 0d 00 00 00 c0 8a 00 3c

>>EIP: c018d04d <tr_tx+11/234> Trace: c0180be2 <SHATransform+1e/108> Trace: c010a455 <handle_IRQ_event+55/8c> Trace: c010edd4 <do_edge_ioapic_IRQ+60/9c> Trace: c010a590 <do_IRQ+30/4c> Trace: c0108c9c <ret_from_intr+0/20> Code: c018d04d <tr_tx+11/234> 00000000 <_EIP>: Code: c018d04d <tr_tx+11/234> 0: 8b b8 80 00 00 movl 0x80(%eax),%edi Code: c018d052 <tr_tx+16/234> 5: 00 Code: c018d053 <tr_tx+17/234> 6: 8b 43 60 movl 0x60(%ebx),%eax Code: c018d056 <tr_tx+1a/234> 9: 83 00 02 addl $0x2,(%eax) Code: c018d059 <tr_tx+1d/234> c: 0d 00 00 00 c0 orl $0xc0000000,%eax Code: c018d05e <tr_tx+22/234> 11: 8a 00 movb (%eax),%al Code: c018d060 <tr_tx+24/234> 13: 3c 00 cmpb $0x0,%al

Aiee, killing interupt handler

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