Date: Tue, 1 May 2007 11:46:04 -0400 From: Jung-uk Kim <jkim@FreeBSD.org> To: freebsd-stable@FreeBSD.org Cc: Jason Chang <jason@FreeBSD.csie.nctu.edu.tw> Subject: Re: bge watchdog timeout -- resetting problem on recent update Message-ID: <200705011146.07715.jkim@FreeBSD.org> In-Reply-To: <20070501094643.6BC827F0A5@FreeBSD.csie.nctu.edu.tw> References: <20070501094643.6BC827F0A5@FreeBSD.csie.nctu.edu.tw>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tuesday 01 May 2007 05:46 am, Jason Chang wrote: > Dear All, > > After further testing, we concluded that > > 1. sysctl > hw.pci.enable_msi > hw.pci.enable_msix > does not change the result. bge still timeout. Okay. > 2. using latest(2007/04) 7-current source does not have this > problem. That's weird. The only difference between -CURRENT and -STABLE is this: http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/dev/bge/if_bge.c.diff?r1=1.91.2.21;r2=1.186 Are you sure it is okay with -CURRENT? Ah, I see that you have IPMI module. Can you add the following line in /boot/loader.conf: hw.bge.allow_asf="1" and reboot? > 3. we are very sure the problem results from > if_bge.c 1.91.2.21 > if_bgereg.h 1.36.2.10 > brgphy.c 1.34.2.13 > which are all commited at 2007/03/21 22:53 > > Please help to check the source code and find out why it affects > bge (BCM 5704 and 5714) network nics. Let me know how it goes. Jung-uk Kim
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200705011146.07715.jkim>