Date: Thu, 7 Dec 2000 11:22:29 +1300 From: "Dan Langille" <dan@langille.org> To: Gérard Roudier <groudier@club-internet.fr> Cc: David Kelly <dkelly@hiwaay.net>, freebsd-scsi@FreeBSD.ORG Subject: Re: sym SCSI card problems during settle wait Message-ID: <200012062222.LAA20969@ducky.nz.freebsd.org> In-Reply-To: <Pine.LNX.4.10.10012062157320.390-100000@linux.local> References: <200012062132.KAA20067@ducky.nz.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 6 Dec 2000, at 22:17, G=E9rard Roudier wrote: > In 3.5, it was probably the `ncr' driver and not the `sym' that attached > your SCSI card. The `ncr' uses a clock and timely polls the interrupt > status register of the PCI-SCSI chip. This was probably intended to reap > lost interrupts in early time of broken PCI bridging implementations. Bu= t > this has also the effect of silently band-aiding chips that have interru= pt > wiring misconfigured or just broken. > > The `sym' driver hasn't such an interrupt reaping clock. I donnot want > unaware user to run such band-aiding for years instead of having caught > and fixed such INT problem on day one. Instead, dummy PCI reads are > theorically in proper place in both SCSI scripts and C codes for not > losing interrupts in presence of posted transactions (not too broken > PCI-HOST bridges assumed). This works so since 5 years under Linux, btw. Hmm. OK. What do you suggest for this box? I was going to use 3.5.1 to get started, then upgrade to 4-stable. Given that the default 4.= 2 boot floppies won't work for me, will I have the same problem once I upgrade to 4-stable? thanks. -- Dan Langille The FreeBSD Diary - http://www.freebsddiary.org/ NZ ADSL - http://www.unixathome.org/adsl/ NZ Broadband - http://www.unixathome.org/broadband/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200012062222.LAA20969>