I have made bge(4) patch for -STABLE (sorry, not suitable for RELENG_6_2): http://people.freebsd.org/~jkim/bge_releng6.diff I received few success reports but I need wider testing because changes are too big and there are two many BCM57xx variants out there. If it breaks anything, please let me know. Especially, I want to hear more about IPMI/ASF mode support, i.e., if it doesn't work but setting hw.bge.allow_asf=0 in /boot/loader.conf fixes the problem, definitely I want to know. Thanks, Jung-uk Kim
At 02:30 PM 3/16/2007, Jung-uk Kim wrote:>I have made bge(4) patch for -STABLE (sorry, not suitable for >RELENG_6_2): > >http://people.freebsd.org/~jkim/bge_releng6.diff > >I received few success reports but I need wider testing because >changes are too big and there are two many BCM57xx variants out >there. If it breaks anything, please let me know. Especially, I >want to hear more about IPMI/ASF mode support, i.e., if it doesn't >work but setting hw.bge.allow_asf=0 in /boot/loader.conf fixes the >problem, definitely I want to know.Hi, What sort of problems does the patch fix ? I have a name server that sees the odd watchdog reset. Do you think this would address that problem ? Its not that frequent, but it does happen. eg Feb 17 17:59:28 auth2 kernel: bge0: watchdog timeout -- resetting Feb 21 16:17:50 auth2 kernel: bge0: watchdog timeout -- resetting Feb 28 11:13:11 auth2 kernel: bge0: watchdog timeout -- resetting Mar 7 09:01:43 auth2 kernel: bge0: watchdog timeout -- resetting Mar 10 10:21:12 auth2 kernel: bge0: watchdog timeout -- resetting Mar 14 03:50:46 auth2 kernel: bge0: watchdog timeout -- resetting bge0: <Broadcom BCM5750 B1, ASIC rev. 0x4101> mem 0xfe5f0000-0xfe5fffff irq 19 at device 0.0 on pci4 miibus1: <MII bus> on bge0 brgphy0: <BCM5750 10/100/1000baseTX PHY> on miibus1 brgphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX, 1000baseTX-FDX, auto bge0: Ethernet address: 00:e0:81:59:2b:06 ---Mike
> I have made bge(4) patch for -STABLE (sorry, not suitable for > RELENG_6_2):What dates stable is this relative to ? I am trying to apply your patch to a cvsup of stable pulled on the day/time you sent your email, but parts of it are failing for me unfortunately. I would like to test this as I have a nmuber of bge interfaces running on some systems. -pete.
At 12:28 PM 3/19/2007, Pete French wrote:> > I have made bge(4) patch for -STABLE (sorry, not suitable for > > RELENG_6_2): > >What dates stable is this relative to ? I am trying to apply your >patch to a cvsup of stable pulled on the day/time you sent your email, >but parts of it are failing for me unfortunately. I would like to test this >as I have a nmuber of bge interfaces running on some systems.Mine applied cleanly to sources from last Friday. So far so good for me in that I have not yet seen the watchdog timeout (previously once every 4 days or so) but its too early to tell. Still, I have not seen any regressions with it yet since installing it last Saturday. This is a fairly busy recursive DNS server ---Mike
> Mine applied cleanly to sources from last Friday.O.K., that works (now I have the correct date in my supfile). Will give it a shot... -pete.
On Friday 16 March 2007 02:30 pm, Jung-uk Kim wrote:> I have made bge(4) patch for -STABLE (sorry, not suitable for > RELENG_6_2): > > http://people.freebsd.org/~jkim/bge_releng6.diff > > I received few success reports but I need wider testing because > changes are too big and there are two many BCM57xx variants out > there. If it breaks anything, please let me know. Especially, I > want to hear more about IPMI/ASF mode support, i.e., if it doesn't > work but setting hw.bge.allow_asf=0 in /boot/loader.conf fixes the > problem, definitely I want to know.It is committed now but ASF mode is disabled by default because at least two people reported breakage. http://docs.freebsd.org/cgi/mid.cgi?200703212253.l2LMrM9M041854 Thanks for your help! Jung-uk Kim
At 09:33 AM 3/17/2007, Mike Tancsa wrote:>At 03:37 PM 3/16/2007, Jung-uk Kim wrote: > >>It might fix your problem (i.e., we have some fixes for BCM5750 >>chipset family) but I am not so sure. Why don't you try it and tell >>me? ;-)Hi, Just to followup 11 days later and still no watchdog timeouts. I would have had at least 2 with the old driver by now! I havent tried whats in RELENG_6, just the patch you posted... But I am guessing they are essentially the same. Thanks for fixing it! bge0: <Broadcom BCM5750 B1, ASIC rev. 0x4101> mem 0xfe5f0000-0xfe5fffff irq 19 at device 0.0 on pci4 miibus1: <MII bus> on bge0 brgphy0: <BCM5750 10/100/1000baseTX PHY> on miibus1 brgphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX, 1000baseTX-FDX, auto bge0: Ethernet address: 00:e0:81:59:2b:06 bge0@pci4:0:0: class=0x020000 card=0x165914e4 chip=0x165914e4 rev=0x11 hdr=0x00 vendor = 'Broadcom Corporation' device = 'BCM5750A1 NetXtreme Gigabit Ethernet PCI Express' class = network subclass = ethernet cap 01[48] = powerspec 2 supports D0 D3 current D0 cap 03[50] = VPD cap 05[58] = MSI supports 8 messages, 64 bit cap 10[d0] = PCI-Express 1 endpoint ---Mike