Fri Oct 29 11:15:05 1999
On Fri, 29 Oct 1999, Bernd Stahlbock wrote:
> I've now compiled the 1.08a driver into my 2.0.36 RTL 1.1 Kernel.
> General machine operation seems to be quite stable, but when I do a
> is also ok. But when I do
> ping 172.16.16.1 -s 5000 -f
> I get this (cat /proc/kmsg):
> <4>rt_ipc V0.3 -- IPC primitives for use with Real-Time Linux
> <4>Copyright (C) 1997 Jerry Epplin. All rights reserved.
> <4>Exposer Module V0.9 Init
> <4>Timer gestartet
> <4>invalid operand: 0000
> <4>CPU: 0
> <4>EIP: 0010:[<00123c46>]
> <4>EFLAGS: 00010293
... remainder of crash
> <4>Call Trace: [<0012211f>] [<0013cc60>] [<0013d0c7>] [<0018d499>]
> [<0014485b>] [<001448c4>] [<0018ce95>]
This crash is the problem. What routine did the kernel crash in?
If it's the driver, it might be a driver problem. If it's somewhere else,
it's probably not a driver bug.
Anything that happens after this point is likely a result of the crash, not
a cause of it.
> <4>Aiee, killing interrupt handler
> <4>kfree of non-kmalloced memory: 001a3eac, next= 00000000, order=0
> <4>kfree of non-kmalloced memory: 001a3e9c, next= 00000000, order=0
> <4>kfree of non-kmalloced memory: 001a43b0, next= 00000000, order=0
> <4>idle task may not sleep
OK, your kernel is now seriously confused
> <3>eth0: RTL8139 Interrupt line blocked, status 5.
> The network will work on with simple pings like the two first, but
> giving messages like 'interrupt line blocked' or 'transmit timeout'
> all few moments and loosing packets. The error counter in
Scyld Computing Corporation, and
| To unsubscribe, send mail to Majordomo@cesdis.gsfc.nasa.gov, and within the
| body of the mail, include only the text:
| unsubscribe this-list-name firstname.lastname@example.org
| You will be unsubscribed as speedily as possible.