Date: Sat, 13 May 2000 12:55:22 -0700 (PDT) From: B.Candler@pobox.com To: freebsd-gnats-submit@FreeBSD.org Subject: kern/18536: ex0 driver seems not to initialise 82595FX card reliably Message-ID: <20000513195522.ED25D37B801@hub.freebsd.org>
next in thread | raw e-mail | index | archive | help
>Number: 18536
>Category: kern
>Synopsis: ex0 driver seems not to initialise 82595FX card reliably
>Confidential: no
>Severity: serious
>Priority: low
>Responsible: freebsd-bugs
>State: open
>Quarter:
>Keywords:
>Date-Required:
>Class: sw-bug
>Submitter-Id: current-users
>Arrival-Date: Sat May 13 13:00:00 PDT 2000
>Closed-Date:
>Last-Modified:
>Originator: Brian Candler
>Release: 4.0-RELEASE
>Organization:
>Environment:
FreeBSD karma.linnet.org 4.0-RELEASE FreeBSD 4.0-RELEASE #1: Wed Sep 8 07:40:54 BST 1999 root@karma.linnet.org:/usr/src/sys/compile/KARMA i386
(oops, I forgot to set the BIOS clock before building the kernel...)
>Description:
This is an old ISA/VLB machine, which used to run Linux, but has now
had FB4.0 installed. The problem is with the ex0 network card.
When I boot this machine, occasionally the network card works, but
I'd say around 3 times in 4 it doesn't. When I try to ping another
machine, and run tcpdump on the remote machine, I see that the ARP
packets being sent by ex0 are corrupted - they appear like this:
16:54:57.774393 B 0:a0:c9:12:51:b8 sap 12 > Broadcast sap c9 I (s=40,r=92,P) len=42
0806 0001 0800 0604 0001 00a0 c912 51b8
d4f0 c2a2 0000 0000 0000 d4f0 c2ae 7e7e
7e7e 7e7e 7e7e 7e7e 7e7e
16:54:58.784104 B 0:a0:c9:12:51:b8 sap 12 > Broadcast sap c9 I (s=40,r=92,P) len=42
0806 0001 0800 0604 0001 00a0 c912 51b8
d4f0 c2a2 0000 0000 0000 d4f0 c2ae 7e7e
7e7e 7e7e 7e7e 7e7e 7e7e
16:54:59.793788 B 0:a0:c9:12:51:b8 sap 12 > Broadcast sap c9 I (s=40,r=92,P) len=42
0806 0001 0800 0604 0001 00a0 c912 51b8
d4f0 c2a2 0000 0000 0000 d4f0 c2ae 7e7e
7e7e 7e7e 7e7e 7e7e 7e7e
and therefore no IP communication is possible. On the occasions where
this does not happen, IP communication is fine. It therefore seems
likely to me that the card, or some data structure, is not being
initialised properly.
This PC used to run Linux, with three of these network cards in it,
and had no problem with them (driver was 'eepro')
In order to eliminate hardware problems:
(1) I have removed all other cards from the system, leaving just a
Promise EIDE VLB controller, an ET4000 VLB video card, and one network
card.
(2) I have tried each of the three network cards in turn (they are
configured as 0x210/IRQ9, 0x240/IRQ5, and 0x300/IRQ10).
(3) I have put one of these cards into a Linux box, where it runs fine.
(4) I have compiled a custom kernel, removing all ISA network cards
and SCSI cards, except ex (of course) and bt (since I have a BusLogic
SCSI card that I also wish to use)
In each case the problem is the same: rebooting the machine, more often
than not it is in a state where it sends these broken ARP packets.
>How-To-Repeat:
Install one of these cards in an ISA machine. Reboot several times.
After each boot, try pinging a machine on the same subnet. In most
cases you see the corrupted ARP packets and no IP communication is
possible.
The card I have is probably not a genuine Intel card. Its main
chip is labelled "S82595FX", but there's no Intel logo on the PCB.
It has an RJ45 connector and two yellow LEDs (ACT and LINK); it is
configured using a DOS utility called SOFTSET2.EXE
Motherboard is a BioStar AT, processor 586/133.
>Fix:
Not known. For now I think I'll have to find another ISA network card.
>Release-Note:
>Audit-Trail:
>Unformatted:
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20000513195522.ED25D37B801>