Date: Tue, 3 Sep 1996 11:50:09 -0500 (CDT) From: Paul DuBois <dubois@primate.wisc.edu> To: imp@village.org (Warner Losh) Cc: current@freebsd.org Subject: Re: Food for thought Message-ID: <199609031650.LAA27866@night.primate.wisc.edu> In-Reply-To: <199609031549.JAA26803@rover.village.org> from "Warner Losh" at Sep 3, 96 09:49:53 am
next in thread | previous in thread | raw e-mail | index | archive | help
>That said, I recently bought more disk (a Jaz drive), and have been >very happy with CTM of CVS. I've not had any make worlds fail since >I've moved over to that which weren't the result of disk full >failures. Had you had problems with FreeBSD locking up if the Jaz has to be brought out of sleep mode? (I'm running 2.1 but) I've seen this in two contexts: 1) During a FreeBSD install. I got to the point where the install process began loading my selected subsets. This was going to take a while, so I went away. Then I can back and was ready to finish up. At some point during the finish-up, the Jaz got woken up, at which point the install hung. (I wasn't installing to the Jaz, by the way.) 2) During bootup. The SCSI probe part of the bootup process woke a sleeping Jaz, a command timeout and abort occurred, and the boot process was hung. Does -current handle these situations better? This was on a Dell OptiPlex with Adaptec 2940UW. In both cases a power cycle was necessary to restart the machine.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199609031650.LAA27866>