From owner-freebsd-bugs Mon Apr 1 09:06:22 1996 Return-Path: owner-bugs Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id JAA07081 for bugs-outgoing; Mon, 1 Apr 1996 09:06:22 -0800 (PST) Received: from lserver.infoworld.com (lserver.infoworld.com [192.216.48.4]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id JAA06976 Mon, 1 Apr 1996 09:06:00 -0800 (PST) Received: from ccgate.infoworld.com by lserver.infoworld.com with smtp (Smail3.1.29.1 #12) id m0u3nP4-000wunC; Mon, 1 Apr 96 09:28 PST Received: from cc:Mail by ccgate.infoworld.com id AA828378291; Mon, 01 Apr 96 09:57:24 PST Date: Mon, 01 Apr 96 09:57:24 PST From: "Brett Glass" Message-Id: <9603018283.AA828378291@ccgate.infoworld.com> To: Andreas Klemm Cc: freebsd-hardware@freebsd.org, bugs@freebsd.org Subject: Re: Cannot boot after install Sender: owner-bugs@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > Well this sounds silly. A lame excuse of your hardware vendor. Unfortunately, the maker of the drive happens to be Seagate. They're rather large, and just got larger. One has to accommodate them. > Figure out, only because one hardware vendor decides, that this > has to be done by the OS, not by BIOS or jumper setting, all OS > vendors or SCSI controller vendors have to rewrite their drivers > or firmware to turn off the green feature in case of trouble ?! This is an ATA drive. I was really surprised to find no jumper, but there isn't one. Seagate supplies a software solution for DOS, where (ironically) it is least needed. Anyway, the real problem is that FreeBSD's ATA disk driver is single-threaded and busy-waits in the kernel for commands to be accepted by the drive. The spindown/spinup would not really be a problem if the driver was coded using more robust techniques. (OS/2, for example, has no problems on the same machine.) --Brett