hi guys
I have got a Pentium Celeron, 64Mb RAM, IDE Disk, 2 D-LINK FX-530 PCI
Network?s installed with Linux RedHat 7.1 working as a firewall.
I made a new kernel, and now I usually get some messages from the kernel
which repeats a lot of times while the system is working.
The messages are:
Jul 23 09:14:13 datdnn kernel: eth0: Oversized Ethernet frame spanned
multiple buffers, entry 0xe length 0 status 00000600!
Jul 23 09:14:13 datdnn kernel: eth0: Oversized Ethernet frame c37740e0 vs
c37740e0.
Jul 23 09:14:13 datdnn kernel: eth1: Oversized Ethernet frame spanned
multiple buffers, entry 0x2 length 0 status 00000600!
Jul 23 09:14:13 datdnn kernel: eth1: Oversized Ethernet frame c382c020 vs
c382c020.
Jul 23 11:10:24 datdnn kernel: NET: 9 messages suppressed.
Jul 23 11:10:24 datdnn kernel: NET: 13 messages suppressed.
Jul 19 11:17:09 datdnn kernel: NETDEV WATCHDOG: eth1: transmit timed out
Jul 19 11:17:09 datdnn kernel: eth1: Transmit timed out, status 0000, PHY
status 782d, resetting...
Jul 19 11:17:30 datdnn kernel: NETDEV WATCHDOG: eth0: transmit timed out
Jul 19 11:17:30 datdnn kernel: eth0: Transmit timed out, status 0000, PHY
status 782d, resetting...
Jul 19 11:17:34 datdnn kernel: NETDEV WATCHDOG: eth0: transmit timed out
Jul 19 11:17:34 datdnn kernel: eth0: Transmit timed out, status 0000, PHY
status 782d, resetting...
Jul 19 11:17:37 datdnn kernel: NETDEV WATCHDOG: eth1: transmit timed out
Jul 19 11:17:37 datdnn kernel: eth1: Transmit timed out, status 0000, PHY
status 782d, resetting...
Jul 19 11:17:40 datdnn kernel: NETDEV WATCHDOG: eth0: transmit timed out
Jul 19 11:17:40 datdnn kernel: eth0: Transmit timed out, status 0000, PHY
status 782d, resetting...
Jul 19 11:17:49 datdnn kernel: NETDEV WATCHDOG: eth1: transmit timed out
Jul 19 11:17:49 datdnn kernel: eth1: Transmit timed out, status 0000, PHY
status 782d, resetting...
Jul 19 11:20:32 datdnn kernel: NETDEV WATCHDOG: eth0: transmit timed out
Jul 19 11:20:32 datdnn kernel: eth0: Transmit timed out, status 0000, PHY
status 782d, resetting...
Please, I would like to know if this messages means everything bad in terms
of fine function of the system and if so, what I should do to resolve the
problem.
I have the idea that specially when the last messages appear the system lose
communication.
Sometimes I have to power off the system to get it fine again.
Thanks for you possible help.
My best Regards
Jaime Alexandre
Datinfor - Inform?tica Servi?os e Estudos, Lda
Tel. 351-226051700 Fax . 351-226051710
Address Mail. [email protected]
On Mon, 23 Jul 2001, Jaime Alexandre Bastos wrote:
> hi guys
> I have got a Pentium Celeron, 64Mb RAM, IDE Disk, 2 D-LINK FX-530 PCI
> Network?s installed with Linux RedHat 7.1 working as a firewall.
> I made a new kernel, and now I usually get some messages from the kernel
^^^^^^^^^^
So which version are you using now?
And which version of the DFE530-TX (not FX, I believe?) do you have?
The kernel output when it detects the cards (dmesg) or lspci output would
answer that.
> which repeats a lot of times while the system is working.
> The messages are:
>
> Jul 23 09:14:13 datdnn kernel: eth0: Oversized Ethernet frame spanned
> multiple buffers, entry 0xe length 0 status 00000600!
> Jul 23 09:14:13 datdnn kernel: eth0: Oversized Ethernet frame c37740e0 vs
> c37740e0.
> Jul 23 09:14:13 datdnn kernel: eth1: Oversized Ethernet frame spanned
> multiple buffers, entry 0x2 length 0 status 00000600!
> Jul 23 09:14:13 datdnn kernel: eth1: Oversized Ethernet frame c382c020 vs
> c382c020.
If you can figure out what is causing the messages I'd be interested to
know. Perhaps you can play with how your network looks, or examine network
traffic and see if there is some pattern (eg it only happens when machine
foo sends stuff to machine bar).
It's quite possible that the above warnings generate the errors below. But
I don't know what is going on.
> Jul 19 11:20:32 datdnn kernel: NETDEV WATCHDOG: eth0: transmit timed out
> Jul 19 11:20:32 datdnn kernel: eth0: Transmit timed out, status 0000, PHY
> status 782d, resetting...
>
> Please, I would like to know if this messages means everything bad in terms
> of fine function of the system and if so, what I should do to resolve the
> problem.
> I have the idea that specially when the last messages appear the system lose
> communication.
> Sometimes I have to power off the system to get it fine again.
2.4.3 should be better than earlier versions, as that driver actually
resets the card when it gets "transmit timed out". There are some other
minor changes too from 2.4.3 to 2.4.7, so it could be worth testing the
latest.
/Urban