Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 04 Jun 2003 17:16:42 +0100
From:      Robin Breathe <robin@isometry.net>
To:        stable@freebsd.org
Subject:   Re: bge drivers does not work for 3COM 3C996-SX / 3C996B-T
Message-ID:  <3EDE1B6A.6050804@isometry.net>
In-Reply-To: <ac078a$ehm$2@main.gmane.org>
References:  <ac078a$ehm$2@main.gmane.org>

next in thread | previous in thread | raw e-mail | index | archive | help
I'm experiencing similar problems with a 3C996-T under 4.8-REL.

In particular, connecting a 4.8-REL machine to a 5.1-REL machine leads 
to some interesting situations: I can do simple pings across the link, 
but ssh fails, and heavy pings crash the 4.8 machine.  Similarly 
changing the interface configuration with ifconfig tends to crash the 
4.8 machine (mtu, link0, up/down, etc).  The behaviour is somewhat hard 
to diagnose, since there's no panic - just a hard lock.

The 4.8-R machine:
$ uname -a
FreeBSD quadric.dsl.isometry.net 4.8-RELEASE FreeBSD 4.8-RELEASE #0: Sun 
Apr  6 19:46:37 UTC 2003 
root@quadric.dsl.isometry.net:/usr/obj/usr/src/sys/QUADRIC  i386
$ ifconfig bge0
bge0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
         options=3<rxcsum,txcsum>
         inet 192.168.108.1 netmask 0xffffff00 broadcast 192.168.108.255
         inet6 fe80::204:76ff:fe3b:6baf%bge0 prefixlen 64 scopeid 0x3
         ether 00:04:76:3b:6b:af
         media: Ethernet autoselect (1000baseTX <full-duplex>)
         status: active

The 5.1-R machine:
$ uname -a
FreeBSD twiddle.dsl.isometry.net 5.1-RELEASE FreeBSD 5.1-RELEASE #0: Wed 
Jun  4 08:23:22 UTC 2003 
root@twiddle.dsl.isometry.net:/var/obj/var/cvs/RELENG_5/src/sys/TWIDDLE 
  i386
$ ifconfig bge0
bge0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
         options=1b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING>
         inet 192.168.108.2 netmask 0xffffff00 broadcast 192.168.108.255
         inet6 fe80::204:76ff:fe3b:62e3%bge0 prefixlen 64 scopeid 0x1
         ether 00:04:76:3b:62:e3
         media: Ethernet autoselect (1000baseTX <full-duplex>)
         status: active

On both machines, the line "bge0: gigabit link up" comes up very 
regularly on the console.

I've had the 4.8-R machine talking happily to the (now) 5.1-R machine 
running Windows 2000, though also with the "bge0: gigabit link up" messages.

Anything else I can provide to help debug?

- Robin


Fabien THOMAS wrote the following on 16/05/2002 13:03:
> I've some problems with bge driver with 3COM 3C996-SX fiber card and
> 3C996B-T copper card under -stable:
> 
> The fiber card is detected correctly but the link does not go up (i've
> tested the same card between two Win2K and it works well).
> 
> The copper card is detected but the link goes up/down and sometimes lock the
> machine (reboot is needed to restart) when i start a 'ping -i0 -q'.
> 
> Does someone experienced the same problems ?
> 
> for the missing splx: i think i've found a new one in bge_init:
> 
> static void
> bge_init(xsc)
>         void *xsc;
> {
>         struct bge_softc *sc = xsc;
>         struct ifnet *ifp;
>         u_int16_t *m;
>         int s;
> 
>         s = splimp();
> 
>         ifp = &sc->arpcom.ac_if;
> 
>         if (ifp->if_flags & IFF_RUNNING)
> --> missing splx ?
>                 return;
> 
> 
> Fabien



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3EDE1B6A.6050804>