Date: Tue, 18 Apr 2006 00:00:44 +0400 From: Oleg Bulyzhin <oleg@freebsd.org> To: "SungGON Yi." <skon@kr.FreeBSD.org> Cc: amd64@freebsd.org, stable@freebsd.org, questions@freebsd.org Subject: Re: bge0 problem on 6.1-PR Message-ID: <20060417200044.GB98808@lath.rinet.ru> In-Reply-To: <001801c65f02$d01ad2f0$6b182e93@skon2> References: <001801c65f02$d01ad2f0$6b182e93@skon2>
next in thread | previous in thread | raw e-mail | index | archive | help
--+xNpyl7Qekk2NvDX Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Apr 13, 2006 at 11:01:51PM +0900, SungGON Yi. wrote: > I am using 6.x on Tyan S2885ANRF board and add one more NIC. > Device names are bge0 (board lan) and bge1 (additional NIC).=20 >=20 > These worked well on FreeBSD 6.0-amd64 stable. > But when I updated to 6.1-PRERELEASE version, I had below messages and bg= e0 did not work. > bge1 worked well as before.=20 >=20 > -------------------------------- > bge0: watchdog timeout -- resetting > -------------------------------- >=20 > I am using 6.0-RELEASE now.=20 >=20 > -------------------------------- > bge0: <Broadcom BCM5701 Gigabit Ethernet, ASIC rev. 0x105> mem 0xfc6f0000= -0xfc6fffff irq 27 at device 8.0 on pci2 > miibus0: <MII bus> on bge0 > brgphy0: <BCM5701 10/100/1000baseTX PHY> on miibus0 > brgphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX, 100= 0baseTX-FDX, auto > bge0: Ethernet address: 00:04:76:f3:e8:c9 > bge1: <Broadcom BCM5703 Gigabit Ethernet, ASIC rev. 0x1002> mem 0xfc6e000= 0-0xfc6effff irq 24 at device 9.0 on pci2 > miibus1: <MII bus> on bge1 > brgphy1: <BCM5703 10/100/1000baseTX PHY> on miibus1 > brgphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX, 100= 0baseTX-FDX, auto > bge1: Ethernet address: 00:e0:81:27:a0:f6 > ----------------------------------- >=20 > -------------------------------------------------------------------------= ------------------------------------------------------- > $ ifconfig > bge0: flags=3D8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500 > options=3D1b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING> > inet6 fe80::204:76ff:fef3:e8c9%bge0 prefixlen 64 scopeid 0x1=20 > inet xxx.xxx.xxx.xxx netmask 0xffffff00 broadcast xxx.xxx.xxx.xxx > ether 00:04:76:f3:e8:c9 > media: Ethernet autoselect (100baseTX <full-duplex>) > status: active > bge1: flags=3D8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500 > options=3D1b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING> > inet6 fe80::2e0:81ff:fe27:a0f6%bge1 prefixlen 64 scopeid 0x2=20 > inet 192.168.24.106 netmask 0xffffff00 broadcast 192.168.24.255 > ether 00:e0:81:27:a0:f6 > media: Ethernet autoselect (1000baseTX <full-duplex>) > status: active > lo0: flags=3D8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 16384 > inet6 ::1 prefixlen 128=20 > inet6 fe80::1%lo0 prefixlen 64 scopeid 0x3=20 > inet 127.0.0.1 netmask 0xff000000=20 > pfsync0: flags=3D0<> mtu 2020 > pflog0: flags=3D0<> mtu 33160 > ------------------------------------ >=20 > SungGON Yi. > skon@kr.FreeBSD.org >=20 > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" I've seen one report about broken onboard bcm5701 asic rev 0x105. Unfortuna= tly i dont have such motherboard to play with. I have PCI nic with same chip/revision which works fine. Do you mind of doing binary search on if_bge.c (rev. 1.95 - 1.118) ? --=20 Oleg. --+xNpyl7Qekk2NvDX Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQFEQ/PsryLc73jOEF8RAnFwAJ0Ziezk4OdAECQ7MfhRzFkdfot/CACfS9d1 gF6hw820bAEvXIiixK9v8Gg= =uTwf -----END PGP SIGNATURE----- --+xNpyl7Qekk2NvDX--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060417200044.GB98808>