Date: Sun, 31 Mar 1996 10:27:09 -0800 From: "Justin T. Gibbs" <gibbs@freefall.freebsd.org> To: asami@cs.berkeley.edu (Satoshi Asami) Cc: current@freefall.freebsd.org Subject: Re: aic7xxx driver and parity error problems Message-ID: <199603311827.KAA10284@freefall.freebsd.org> In-Reply-To: Your message of "Sun, 31 Mar 1996 04:42:52 PST." <199603311242.EAA01469@silvia.HIP.Berkeley.EDU>
next in thread | previous in thread | raw e-mail | index | archive | help
> * Also, the "disable parity checking" workaround failed here, as I got > * "timed out in message out phase, SCSISIGI=0xe6" and stuff (I'm not > * sure, I had to reset the machine while it was still scrolling). > * > * This threw the SCSI system into a serious funk as the next three > * reboots, from cold start, failed with a solid hang during the probe > * from ahc0 (I've told you about this before). > * > * It has come up now (with parity checking disabled), so I guess it (the > * workaround) does work sometimes. > >More update. The machine crashed shortly afterwards (running an old >kernel), and it seemed to have caused something to go seriously wrong. >I haven't been able to boot -current in about 15 tries, using new >kernels, old kernels (unfortunately I have only one version, which is >about 3 days old, which WAS running flawlessly until tonight), parity >turned on/off, etc. It always dies with the "sd1: timed out in >message in phase, SCSISIGI=0xe6" (note it's now sd1). > >However, I managed to boot the -stable system I haven't touched for >months. The funny thing is, this system is on sd1. I'm quite >puzzled. > >Satoshi Could it be a power supply problem? Or perhaps your Atlas is causing SCSI bus noise? Are other 7880 owners seeing this as well with the -current driver? -- Justin T. Gibbs =========================================== FreeBSD: Turning PCs into workstations ===========================================
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199603311827.KAA10284>