Date: Tue, 30 Mar 1999 12:40:03 -0800 (PST) From: "Justin T. Gibbs" <gibbs@plutotech.com> To: freebsd-bugs@FreeBSD.org Subject: Re: kern/10876: aic7895 code failed Message-ID: <199903302040.MAA40053@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
The following reply was made to PR kern/10876; it has been noted by GNATS. From: "Justin T. Gibbs" <gibbs@plutotech.com> To: doka@doka.kiev.sovam.com Cc: FreeBSD-gnats-submit@FreeBSD.ORG Subject: Re: kern/10876: aic7895 code failed Date: Tue, 30 Mar 1999 13:23:29 -0700 >>Description: > > While booting kernel detects SCSI controller successfully, but > later panics with such messages on console: > > (probe0:ahc0:0:1:7): parity error during Data-In phase > SEQADDR == 0x111 (may be 0x110 and 0x112) > SCSIRATE == 0x88 There is something wrong with your cabling or termination that is causing parity errors to be reported. This is not a driver bug. > Fatal trap 12 > fault virtual address = 0x8 > fault code = supervisor read, page not present > instruction pointer = 0x8:0xf015fae1 Taking the kernel from the 19990328-STABLE snapshot off of kern.flp: nm kernel | sort ... f015f654 t gcc2_compiled. f015f794 T dscheck f015fa80 T dsclose f015fad4 T dsgone f015fb3c T dsioctl f01600cc t dsiodone This is in the middle of dsgone(). Perhaps Bruce (bde@FreeBSD.org) can help you out here. My guess is that if you fix your parity problem, the diskslice code will be less confused. -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199903302040.MAA40053>