Messages in this thread | | | From | Brian Geisel <> | Subject | Ethernet Oops / Ethernet Freak | Date | Fri, 7 May 1999 11:29:03 -0400 |
| |
Greetings, I believe I have two bugs submitted for your approval. I'm afraid I haven't a clue as to what is actually going on. Here are the two separate problems. We have a RedHat 6.0 system running 2.2.5 compiled on egcs which decides occasionally to ipx flood our entire network. We are using IPX for nothing, just in case you're wondering. The system is using an eepro100.o module for the ethernet driver. The process we're assuming that did it was rpciod, which was about the only network daemon still running while it was happening. We couldn't kill -9 it, so I'm guessing it made a kernel call that just freaked out.
Totally separate problem, part II... I'm also running a RedHat 4.2 system with kernel 2.2.0-pre5 which kernel Oopses. I'm not sure if this has been fixed since this kernel, but here's the Oops anyway:
ly disabling functions (7f7e). Unable to handle kernel NULL pointer dereference at virtual address 00000070 current->tss.cr3 = 00101000, %cr3 = 00101000 *pde = 00000000 Oops: 0002 CPU: 0 EIP: 0010:[<c01b35e2>] EFLAGS: 00010206 eax: c0210ddc ebx: c008610e ecx: 00000000 edx: 00000070 esi: 0000ed11 edi: c033e800 ebp: 00000003 esp: c0217e68 ds: 0018 es: 0018 ss: 0018 Process swapper (pid: 0, process nr: 0, stackpage=c0217000) Stack: 00000009 c0217ef4 00000009 c01eee1d 00000001 c010a99f 00000009 00000070 00006124 c0fa610e 00000014 00006100 c0210ddc c010a885 00000009 c0210ddc c0217ef4 c02035a8 00000009 c0217ef4 00000001 c010a99f 00000009 c0217ef4 Call trace: [<c01eee1d>] [<c010aa9d>] [<c0109924>] [<c0108058>] [<c01080af>] [<c0106000>] [c01080f0>] [<c015ac27>] [<c0117929>] [<c010aa9d>] [<c0109924>] [<c0108058>] [<c01080af>] [<c0106000>] [<c01080f0>] [<c0109888>] [<c0106000>] [<c010607b>] [<c0106000>] [<c0100177>] Code: ff 49 70 0f 94 44 24 24 80 7c 24 24 00 74 09 51 e8 51 5e fa Aiee, killing interrupt handler Kernel panic: Attempted to kill the idle task! In swapper task - not syncing
This happens everytime the aforementioned machine begins to flood the network. If I reboot it, it Ooopses as soon as it's booting (I'm assuming as it's initializing the network -- never looked).
If there's anything I can do to help track this down, please let me know and I will do what I can. Thank you.
geisel
- 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/
| |