Date: Sun, 14 Nov 2004 23:31:24 -0600 From: "Val P" <garbage@injvstice.com> To: <freebsd-net@freebsd.org> Subject: OACTIVE on bge Message-ID: <20041115053131.7207B43D41@mx1.FreeBSD.org>
next in thread | raw e-mail | index | archive | help
We have a bridge running fbsd 4.8, and both ends of the interface are running broadcomm gigabit fiber NICs (bge2 and bge3). Periodically we see the bridge lock up with bge2 in state OACTIVE. We have resorted to having a script that periodically checks ifconfig and downs/reups the offending iface when this happens. Of course, sometimes this starts happening quite often and it creates havoc with established connections. This is not a good solution, but it's best we could have come up with. We are using this bridge in conjunction with IPF as a transparent firewall. Is this a known issue? Is there something we can fix? We are happy with 4.x but we'd consider upgrading to 5.3 if it fixed this problem. The bridge connects an Extreme Networks Black Diamond and a Foundry Big Iron... Here's the state when this happens: bge2: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> mtu 1500 options=3<rxcsum,txcsum> media: Ethernet autoselect (1000baseSX <full-duplex>) status: active bge3: flags=9d43<UP,BROADCAST,RUNNING,PROMISC,OACTIVE,SIMPLEX,LINK0,MULTICAST> \ mtu 1500 options=3<rxcsum,txcsum> media: Ethernet autoselect (1000baseSX <full-duplex>) status: active ... 2139/2256/26624 mbufs in use (current/peak/max): 2139 mbufs allocated to data 1584/1692/6656 mbuf clusters in use (current/peak/max) 3948 Kbytes allocated to network (19% of mb_map in use) 0 requests for memory denied 0 requests for memory delayed 0 calls to protocol drain routines
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20041115053131.7207B43D41>