From owner-freebsd-hackers Mon Oct 11 17:18:48 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 3070015729; Mon, 11 Oct 1999 17:18:41 -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 RAA15224; Mon, 11 Oct 1999 17:17:54 -0700 (PDT) Message-Id: <199910120017.RAA15224@implode.root.com> To: Mike Smith Cc: sa-list@avantgo.com, FreeBSD-hackers@FreeBSD.ORG, FreeBSD-stable@FreeBSD.ORG Subject: Re: SMP + fxp0 wierdness In-reply-to: Your message of "Mon, 11 Oct 1999 17:04:12 PDT." <199910120004.RAA02842@dingo.cdrom.com> From: David Greenman Reply-To: dg@root.com Date: Mon, 11 Oct 1999 17:17:54 -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> >> So if this problem is NOT related to specific hardware, how can we get >> >> the driver fixed? >> > >> >Talk to the maintainer (David). We've offered him cores and kernels >> >before. Alternatively, you'll need to experiment with your setup to >> >determine what characterises the failures and help David out with more >> >data. >> >> Hotmail has troubleshooted the problem down to the NCR controller. It >> appears that the problem only occurs when using one of those. If they plug >> in an Adaptec 2940 and use it instead of the onboard NCR then the problems >> disappear. > >We did this (you remember that we went through all this a while back, >right?), but we've also been seing reports from people that aren't >using NCR controllers. I haven't seen a report yet from someone not using an NCR/Symbios controller. -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