Date: Thu, 10 Feb 2000 16:19:49 -0700 (MST) From: "Aaron Gifford" <agifford@infowest.com> To: <groudier@club-internet.fr> Cc: <freebsd-current@freebsd.org> Subject: Re: 4.0 fails to boot - sym troubles Message-ID: <20000210231949.7F84220F66@infowest.com> In-Reply-To: <Pine.LNX.3.95.1000210211357.371B-100000@localhost>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, 10 Feb 2000, Gerard Roudier <groudier@club-internet.fr> wrote: >Hello, > >Just quoting the offending messages: > >On Wed, 9 Feb 2000, Aaron Gifford wrote: > >> sym0: SCSI parity error detected: SCR=3D1 DBC=3D72580000 SBCL=3Daf >> (noperiph:sym0:0:-1:-1): SCSI BUS reset detected. > >The driver gets an SCSI parity error while attempting to snoop the BUS by >reading directly the SCSI BUS data line bit 0...7. I have recently >discovered experimentally that a spurious SCSI parity error due to the >chip checking against parity for bit 8..15 can be triggerred in some >special situations, for example when the WSR bit is set. The WSR bit is >set when a residual byte didn't fit a previous CHMOV for a scatter entry >and the target changes phase at the beginning of the next CHMOV (count) >with count > 1. (For count=3D1, the WSR bit isn't set and the residual byte >is transferred to memory). Since this issue cannot be cleanly >worked-around, I have decided to handle things differently so that it is >no longer needed to snoop the BUS by reading directly the SCSI BUS data >lines. Result is sym-1.3.2-20000206 that haven't (yet?) been committed due >to 4.0 release time.=20 > >If you could give a try with this driver version, this would help. >ftp://ftp.tux.org/roudier/drivers/freebsd/experimental/sym-1.3.2-freebsd.20= >000206.readme >ftp://ftp.tux.org/roudier/drivers/freebsd/experimental/sym-1.3.2-freebsd.20= >000206.tar.gz >(The tar contains full driver files to move to src/sys/dev/sym) > >You may want to let me know if it fixes or not. Thanks. > >Regards, > G=E9rard. > >PS: >On the other hand, I seem to remember that my last commit for the `sym' >driver has been done on January the 12th. So the kernel that fails should >just use same `sym' driver as 4.0-CURRENT-25-January that succeeds. >Btw, if the `ncr' that just ignores the WSR bit succeeds, then I may well >be right. > THANK YOU THANK YOU THANK YOU THANK YOU THANK YOU THANK YOU!!!! That fixed the problem! Too bad it didn't make it into the latest 4.0-RC. Other folks with Tekram cards experiencing the problem should give your fix a try too. I rebuilt my 4.0 (as of 10 Feb. 2000 CVSup) kernel using your latest sym files and rebooted. The errors I mentioned in my posts went away completely. I did not make any other changes. Since then, the driver appears to be working find. I'm doing a buildworld right now and have seen nothing unusual at all. Again, let me repeat, many thanks for your work and for the fix! Sincerely, Aaron Gifford 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?20000210231949.7F84220F66>