Date: Mon, 14 Feb 2005 19:34:32 -0800 From: Peter Losher <Peter_Losher@isc.org> To: freebsd-stable@freebsd.org Subject: Weird bge related lock order reversal... Message-ID: <200502141934.41373.Peter_Losher@isc.org>
next in thread | raw e-mail | index | archive | help
--nextPart123173339.WT4U97SpFn Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline (apologies if you get this sent twice, I sent the first one to=20 stable@freebsd.org by mistake)=20 I have a quad-Opteron box running FreeBSD 5.3-p5/i386, and it has two onboa= rd Broadcom copper GigE NIC's (bge0 is used as a private wire, bge1 is the public interface) =2D=3D- bge0: <Broadcom BCM5704C Dual Gigabit Ethernet, ASIC rev. 0x2003> mem 0xf1140000-0xf114ffff,0xf1150000-0xf115ffff irq 31 at device 3.0 on pci14 miibus0: <MII bus> on bge0 bge0: Ethernet address: <some mac address> bge0: [GIANT-LOCKED] bge1: <Broadcom BCM5704C Dual Gigabit Ethernet, ASIC rev. 0x2003> mem 0xf1160000-0xf116ffff,0xf1170000-0xf117ffff irq 28 at device 3.1 on pci14 miibus1: <MII bus> on bge1 bge1: Ethernet address: <some mac address> bge1: [GIANT-LOCKED] =2D=3D- When booting, and just after initializing the network (configuring the NIC's for autoneg to a DLink GigE switch), console spits out this lock order reversal: =2D=3D- Starting local daemons:bge1: gigabit link up lock order reversal 1st 0xc5a65dec inp (rawinp) @ netinet/raw_ip.c:199 2nd 0xc5a65ea0 inp (raw6inp) @ netinet/raw_ip.c:199 KDB: stack backtrace: kdb_backtrace(ffffffff,c08fdb48,c08fdb70,c088f47c,c09223e8) at kdb_backtrace+0x29 witness_checkorder(c5a65ea0,9,c08391f0,c7) at witness_checkorder+0x49d _mtx_lock_flags(c5a65ea0,0,c08391e7,c7) at _mtx_lock_flags+0x1e rip_input(c5461200,14,50000e0,0,0) at rip_input+0x64 ip_input(c5461200) at ip_input+0x596 netisr_processqueue(c0923418) at netisr_processqueue+0x6e swi_net(0) at swi_net+0x88 ithread_loop(c4fe7a80,e7307d48,c08f6780,0,c082cc46) at ithread_loop+0x10c fork_exit(c05fa5dc,c4fe7a80,e7307d48) at fork_exit+0x66 fork_trampoline() at fork_trampoline+0x8 =2D-- trap 0x1, eip =3D 0, esp =3D 0xe7307d7c, ebp =3D 0 --- =2D=3D- Is this ominous? Are there any known issues w/ Broadcom NIC's running at Gi= gE speeds? The only other oddity on this system is that we have assigned v6 addresses to vlan interfaces. (we haven't done that in the past until now) Thanks in advance for any light you can shed on this... Best Wishes - Peter =2D-=20 Peter_Losher@isc.org | ISC | OpenPGP 0xE8048D08 | "The bits must flow" --nextPart123173339.WT4U97SpFn Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (FreeBSD) iD8DBQBCEW3RPtVx9OgEjQgRArMqAKCj60d7qy8CYvTQ85yl6lnPEx5kVwCdG0q3 f1ejnPHYs8BaSdQMbifHhCA= =cHzQ -----END PGP SIGNATURE----- --nextPart123173339.WT4U97SpFn--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200502141934.41373.Peter_Losher>