From owner-freebsd-hackers Tue Oct 26 13:22:46 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from implode.root.com (root.com [209.102.106.178]) by hub.freebsd.org (Postfix) with ESMTP id 0BFA614CC4 for ; Tue, 26 Oct 1999 13:22:38 -0700 (PDT) (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 NAA23488; Tue, 26 Oct 1999 13:19:45 -0700 (PDT) Message-Id: <199910262019.NAA23488@implode.root.com> To: Lew Payne Cc: hackers@freebsd.org, Joe McGuckin Subject: Re: fxp related kernel panic In-reply-to: Your message of "Tue, 26 Oct 1999 12:21:15 PDT." <199910261921.MAA07922@relay.lppi.com> From: David Greenman Reply-To: dg@root.com Date: Tue, 26 Oct 1999 13:19:45 -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >Hi David -- What if I install a *real* EtherExpress Pro-100B (or >whatever it's known as today) in the PCI slot, and use it instead >of the on-board (N440BX motherboard) fxp0 interface? > >Judging that you probably know the nature of the problem, do you >think this might circumvent it? I think it is caused by the NCR/Symbios controller. It might be a side effect of the NCR just using up a lot of PCI bandwidth, with the real bug being in the fxp driver (although I've looked and haven't found one). So I don't think putting in a real Pro/100 will have any effect on the problem. Of course I don't really know what is causing it, so just about anything is possible. -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-hackers" in the body of the message