Date: Sat, 19 Feb 2011 14:44:01 -0800 From: Pyun YongHyeon <pyunyh@gmail.com> To: Steven Hartland <killing@multiplay.co.uk> Cc: freebsd-net@freebsd.org, freebsd-stable@freebsd.org Subject: Re: bge0 watchdog timeout -- resetting on 8.2-PREREL never recovers Message-ID: <20110219224401.GA28005@michelle.cdnetworks.com> In-Reply-To: <2FA20352DEB643BEA7EAB90A14346894@multiplay.co.uk> References: <E5786A8612384145B7AAAF645E7B148E@multiplay.co.uk> <2FA20352DEB643BEA7EAB90A14346894@multiplay.co.uk>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, Feb 19, 2011 at 03:59:57PM -0000, Steven Hartland wrote: > This may be totally unrelated to bge, investigating a potential failing > stick > of ram in the machine in question so until we've ruled this out as the cause > don't want to waste anyone's time. > > I did however notice the logic between the two fixes for DMA on 5704's on > PCIX > in svn differ so wondering which ones correct:- > http://svn.freebsd.org/viewvc/base/head/sys/dev/bge/if_bge.c?r1=216085&r2=216970 > http://svn.freebsd.org/viewvc/base/head/sys/dev/bge/if_bge.c?r1=217225&r2=217226 > > r216970 results in: > 1, 0, BUS_SPACE_MAXADDR_32BIT, BUS_SPACE_MAXADDR, NULL, > where as r217226 results in: > 1, BGE_DMA_BNDRY, BUS_SPACE_MAXADDR_32BIT, BUS_SPACE_MAXADDR, NULL, > I think it would be same for your case(BCM5704 PCI-X). However r217226 would be better one to address the issue. Actually I didn't like the workaround but there was no much time left to fix it for upcoming 8.2/7.4.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20110219224401.GA28005>