From owner-freebsd-bugs Mon Jan 31 6:17:33 2000 Delivered-To: freebsd-bugs@freebsd.org Received: from implode.root.com (root.com [209.102.106.178]) by hub.freebsd.org (Postfix) with ESMTP id CCE3D14C1C for ; Mon, 31 Jan 2000 06:17:18 -0800 (PST) (envelope-from dg@implode.root.com) Received: from implode.root.com (localhost [127.0.0.1]) by implode.root.com (8.8.8/8.8.5) with ESMTP id GAA04699; Mon, 31 Jan 2000 06:17:02 -0800 (PST) Message-Id: <200001311417.GAA04699@implode.root.com> To: Terry Kennedy Cc: freebsd-bugs@FreeBSD.ORG Subject: Re: kern/10872: Panic in soreceive() due to NULL mbuf pointer In-reply-to: Your message of "Mon, 31 Jan 2000 09:08:33 EST." <01JLCKTQLVU08WW4MU@tmk.com> From: David Greenman Reply-To: dg@root.com Date: Mon, 31 Jan 2000 06:17:02 -0800 Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >> What motherboard are you using? An Intel N440BX perhaps? > > Intel SE440BX, Intel SE440BX-2, and a Tyan S1662D. I've had the problem >on all three platforms. I'm not familiar with the SE440BX, but we do know about a problem with the fxp [Pro/100+] on N440BX causing identical symptoms. People have reported trying de [DEC] boards and still having a similar problem. It seems to occur in conjunction with the NCR/Symbios controller, but noone has yet been able to put their finger on it. I've been told that the problem goes away when switching to an Adaptec. The problem definately seems to be related somehow to concurrent PCI DMA. I don't recall seeing any reports of this problem occuring with 440GX based motherboards (or anything else), so it leads me to think that it might be a bug in the 440BX chipset. -DG David Greenman Co-founder/Principal Architect, The FreeBSD Project - http://www.freebsd.org Creator of high-performance Internet servers - http://www.terasolutions.com Pave the road of life with opportunities. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message