From owner-freebsd-scsi Wed Dec 6 14:23: 4 2000 From owner-freebsd-scsi@FreeBSD.ORG Wed Dec 6 14:23:02 2000 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from ducky.nz.freebsd.org (ns1.unixathome.org [203.79.82.27]) by hub.freebsd.org (Postfix) with ESMTP id 0C9AA37B400 for ; Wed, 6 Dec 2000 14:23:01 -0800 (PST) Received: from wocker (wocker.int.nz.freebsd.org [192.168.0.99]) by ducky.nz.freebsd.org (8.9.3/8.9.3) with ESMTP id LAA20969; Thu, 7 Dec 2000 11:22:48 +1300 (NZDT) Message-Id: <200012062222.LAA20969@ducky.nz.freebsd.org> From: "Dan Langille" Organization: langille.org To: Gérard Roudier Date: Thu, 7 Dec 2000 11:22:29 +1300 MIME-Version: 1.0 Content-type: text/plain; charset=ISO-8859-1 Content-transfer-encoding: Quoted-printable Subject: Re: sym SCSI card problems during settle wait Reply-To: dan@langille.org Cc: David Kelly , freebsd-scsi@FreeBSD.ORG Priority: normal References: <200012062132.KAA20067@ducky.nz.freebsd.org> In-reply-to: X-mailer: Pegasus Mail for Win32 (v3.12c) Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org 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