[realtek] Ping doesn't respond anymore after 5 good tests (Driver 1.12)

[Donald Becker]

On Mon, 8 Jan 2001, Alain SMEDTS wrote:

> hereby attached my /var/log/debug file after a reboot (with debug=7). I did
> a ping which failed after some good responses.

Jan  8 20:55:46 Volcanus kernel: eth1: interrupt  status=0x0004 new intstat=0x0000.
Jan  8 20:55:46 Volcanus kernel: eth1: interrupt  status=0x0001 new intstat=0x0000.
Jan  8 20:55:46 Volcanus kernel: eth1: In rtl8129_rx(), current 06f4 BufAddr 0760, free to 06e4, Cmd 0c.
Jan  8 20:55:46 Volcanus kernel: eth1:  rtl8129_rx() status 664001, size 0066, cur 06f4.
Jan  8 20:55:46 Volcanus kernel: eth1: Frame contents  01 40 66 00 00 10 b5 03 63 1d 00 30 4f 02 d7 38 08 00 45 00 00 54 2c 4d 00 00 80 01 ad 0d ac 11 04 64 ac 11 04 c8 00 00 00 5b 95 00 08 00 42 1b 5a 3a cf 4b 0c 00 08 09 0a 0b 0c 0d 0e 0f 10 11 12 13 14 15 16 17.
Jan  8 20:55:46 Volcanus kernel: eth1:  rtl8129_rx() status ffffffff, size ffff, cur 0760.
Jan  8 20:55:46 Volcanus kernel: eth1: Frame contents  ff ff ff ff 00 00 00 00 00 00 00 00 00 00 00 00 30 00 00 00 31 00 00 00 00 00 00 00 50 1f 0d 08 80 47 00 00 00 00 00 00 01 00 00 00 00 00 00 00 ff ff ff ff 01 46 00 00 00 00 00 00 00 00 00 00 08 00 00 00 31 00.
Jan  8 20:55:46 Volcanus kernel: eth1: Ethernet frame had errors, status ffffffff.

You just had a hardware problem!
The chip stopped responding (status 0xffffffff) and apparently reset itself
later.  The reset chip was not set up to enable receives.

I'll look for a way for the driver to detect that this has happened, but
keep in mind that this is a hardware problem, not a driver flaw.


Donald Becker				becker@scyld.com
Scyld Computing Corporation		http://www.scyld.com
410 Severn Ave. Suite 210		Second Generation Beowulf Clusters
Annapolis MD 21403			410-990-9993