Date: Wed, 4 Nov 1998 12:00:01 -0800 (PST) From: "Kenneth D. Merry" <ken@plutotech.com> To: freebsd-bugs@FreeBSD.ORG Subject: Re: kern/8555: boot panic with SONY SCSI CD-ROM CDU625-S 1.0r hooked Message-ID: <199811042000.MAA25112@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
The following reply was made to PR kern/8555; it has been noted by GNATS. From: "Kenneth D. Merry" <ken@plutotech.com> To: Liviu.Ionescu@Romania.EU.net Cc: freebsd-bugs@FreeBSD.ORG, freebsd-gnats-submit@FreeBSD.ORG Subject: Re: kern/8555: boot panic with SONY SCSI CD-ROM CDU625-S 1.0r hooked Date: Wed, 4 Nov 1998 12:59:27 -0700 (MST) Liviu Ionescu wrote... > I applied the patch and (bingo!) the kernel now boots without panic. > > the picture also changed a bit, the CD-ROM is listed now at 20.0MB/s. > > but when I try to mount a disc I get an error: > > boca# mount /dev/cd0c /mnt > mount: Input/output error > > and the syslog shows: > > Nov 4 19:50:03 boca /kernel: (cd0:ahc1:0:3:0): parity error during Command > phase. > Nov 4 19:50:03 boca /kernel: (cd0:ahc1:0:3:0): parity error during Command > phase. > Nov 4 19:50:03 boca /kernel: SEQADDR == 0x153 > Nov 4 19:50:03 boca /kernel: SEQADDR == 0x153 > Nov 4 19:50:03 boca /kernel: SCSIRATE == 0xf > Nov 4 19:50:03 boca /kernel: SCSIRATE == 0xf > Nov 4 19:50:12 boca /kernel: (cd0:ahc1:0:3:0): parity error during Command > phase. > Nov 4 19:50:12 boca /kernel: (cd0:ahc1:0:3:0): parity error during Command > phase. > Nov 4 19:50:12 boca /kernel: SEQADDR == 0x153 > Nov 4 19:50:12 boca /kernel: SEQADDR == 0x153 > Nov 4 19:50:12 boca /kernel: SCSIRATE == 0xf > Nov 4 19:50:12 boca /kernel: SCSIRATE == 0xf > > I also tried to remove the parity/termination jumpers from the Sony drive, > without success. anyway, I remember that exactly the same hardware > configuration worked fine with 2.2.7 with cam patches applied, so it > shouldn't be a parity/terminator misconfiguration. This really looks like a cabling or termination problem. The Adaptec driver in -current isn't significantly different than the CAM driver you used with 2.2.7. So it's most likely some change in your hardware that has caused the problem. Ken -- Kenneth Merry ken@plutotech.com 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?199811042000.MAA25112>