Date: Wed, 08 Dec 1999 05:14:44 +0800 From: Peter Wemm <peter@netplex.com.au> To: Gerard Roudier <groudier@club-internet.fr> Cc: Ed Hall <edhall@screech.weirdnoise.com>, Matthew Dillon <dillon@apollo.backplane.com>, "Jonathan M. Bresler" <jmb@hub.freebsd.org>, kris@hub.freebsd.org, freebsd-hackers@FreeBSD.ORG Subject: Re: PCI DMA lockups in 3.2 (3.3 maybe?) Message-ID: <19991207211444.3C6571CC6@overcee.netplex.com.au> In-Reply-To: Message from Gerard Roudier <groudier@club-internet.fr> of "Tue, 07 Dec 1999 23:10:39 %2B0100." <Pine.LNX.3.95.991207224951.943A-100000@localhost>
next in thread | previous in thread | raw e-mail | index | archive | help
Gerard Roudier wrote:
>
>
> On Tue, 7 Dec 1999, Peter Wemm wrote:
>
> > I might add that others have found that using sym + fxp on the N440BX
> > motherboards didn't solve their problems, or moved the problem elsewhere,
> > eg: to the sbdrop() etc routines. One other interesting variable.. an ahc
> > + pn driver combination on a 440BX motherboard under -current in late may
> > 99 had the exact same problems we saw a number of times with ncr + fxp (ie:
> > sbdrop, sbflush, m_copym etc panics). The same motherboard with ahc + de o
r
> > fxp did not have the problems.
>
> (ncr || sym || ahc) && fxp = TRUE makes the fxp a better culprit. :-)
No no, ahc && fxp == FALSE. ahc && if_pn == TRUE. (or was true in june,
on non-N440BX machines, with an *exact* match of a crash class the fxp &&
ncr machines were having in october).
Cheers,
-Peter
--
Peter Wemm - peter@FreeBSD.org; peter@yahoo-inc.com; peter@netplex.com.au
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19991207211444.3C6571CC6>