Date: Tue, 9 Jan 2007 11:51:16 -0500 From: John Baldwin <jhb@freebsd.org> To: Bruce Evans <bde@zeta.org.au> Cc: rwatson@freebsd.org, freebsd-amd64@freebsd.org Subject: Re: Panic in 6.2-PRERELEASE with bge on amd64 Message-ID: <200701091151.17166.jhb@freebsd.org> In-Reply-To: <20070108154433.C75042@delplex.bde.org> References: <1168211205.22629.6.camel@lanshark.dmv.com> <20070108154433.C75042@delplex.bde.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Monday 08 January 2007 00:06, Bruce Evans wrote: > On Sun, 7 Jan 2007, Sven Willenberger wrote: > > > I am starting a new thread on this as what I had assumed was a panic in > > nfsd turns out to be an issue with the bge driver. This is an amd64 box, > > dual processor (SMP kernel) that happens to be running nfsd. About every > > 3-5 days the kernel panics and I have finally managed to get a core > > dump. > > The system: FreeBSD 6.2-PRERELEASE #8: Tue Jan 2 10:57:39 EST 2007 > > Like most NIC drivers, bge unlocks and re-locks around its call to > ether_input() in its interrupt handler. This isn't very safe, and it > certainly causes panics for bge. I often see it panic when bringing > the interface down and up while input is arriving, on a non-SMP non-amd64 > (actually i386) non-6.x (actually -current) system. Bringing the > interface down is probably the worst case. It creates a null pointer > for bge_intr() to follow. Why do you feel that it is unsafe to drop the lock around if_input()? -- John Baldwin
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200701091151.17166.jhb>