Re: Lanfinity keeps breaking under load.

Am Dienstag, 22. April 2003 00:28 schrieb Donald Becker:
> There should be a message.
> A timer checks that the chip is still transitting.  If the packets
> back up, the driver prints a message with the chip status.
>
> You can use
>    mii-diag --msg-level 0xffff
> when the interface stops to enable all messages.

The --msg-level option gives me a German "Speicherzugriffsfehler", 
I would translate it to "memory access error".
Without this option, mii-diag doesn't say anything when the interface stops.

This is what syslog says when the memory access error occurs:
Apr 22 09:04:30 earnie kernel: Unable to handle kernel paging request at virtual address fffe000c
Apr 22 09:04:30 earnie kernel:  printing eip:
Apr 22 09:04:30 earnie kernel: c0137235
Apr 22 09:04:30 earnie kernel: *pde = 00001063
Apr 22 09:04:30 earnie kernel: *pte = 00000000
Apr 22 09:04:30 earnie kernel: Oops: 0000
Apr 22 09:04:30 earnie kernel: CPU:    0
Apr 22 09:04:30 earnie kernel: EIP:    0010:[fput+21/288]    Not tainted
Apr 22 09:04:30 earnie kernel: EFLAGS: 00010286
Apr 22 09:04:30 earnie kernel: eax: fffe0000   ebx: fffe0000   ecx: 00000000   edx: 00000000
Apr 22 09:04:30 earnie kernel: esi: 000089f3   edi: 00000000   ebp: c024e350   esp: c4063f84
Apr 22 09:04:30 earnie kernel: ds: 0018   es: 0018   ss: 0018
Apr 22 09:04:30 earnie kernel: Process mii-diag (pid: 2819, stackpage=c4063000)
Apr 22 09:04:30 earnie kernel: Stack: ffffffe7 c024e350 fffe0000 000089f3 00000000 c024e350 c014460e c4043900 
Apr 22 09:04:30 earnie kernel:        c24980c0 000089f3 0804e7c0 c4062000 0804e7d0 00000000 bffff9d8 c0107237 
Apr 22 09:04:30 earnie kernel:        00000003 000089f3 0804e7c0 0804e7d0 00000000 bffff9d8 00000036 0000002b 
Apr 22 09:04:30 earnie kernel: Call Trace: [sock_ioctl+0/48] [sock_ioctl+0/48] [sys_ioctl+126/432] [system_call+51/56] 
Apr 22 09:04:30 earnie kernel: 
Apr 22 09:04:30 earnie kernel: Code: 8b 70 0c 8b 68 08 8b 7d 08 ff 48 14 0f 94 c0 84 c0 75 14 8b 


Btw:  It's just a thought, but I think there is a correlation between the error and the memory usage. 
I tried to force the error under a small windowmanager and it did not occur.
Running Gnome2 fully featured with some other applications, it did.

Bernhard
_______________________________________________
tulip mailing list, [email protected]
To change to digest mode or unsubscribe visit
http://www.scyld.com/mailman/listinfo/tulip