From owner-freebsd-stable@FreeBSD.ORG Tue Oct 4 23:48:46 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DB76216A41F for ; Tue, 4 Oct 2005 23:48:46 +0000 (GMT) (envelope-from djh@nebcorp.com) Received: from ratchet.nebcorp.com (ratchet.nebcorp.com [205.217.153.72]) by mx1.FreeBSD.org (Postfix) with ESMTP id A4D1043D46 for ; Tue, 4 Oct 2005 23:48:46 +0000 (GMT) (envelope-from djh@nebcorp.com) Received: by ratchet.nebcorp.com (Postfix, from userid 1014) id 88DC9D9879; Tue, 4 Oct 2005 16:48:46 -0700 (PDT) Date: Tue, 4 Oct 2005 16:48:46 -0700 From: Danny Howard To: Tim Howe Message-ID: <20051004234846.GG564@ratchet.nebcorp.com> References: <87y85nuqhy.fsf@beaker.data-secure.net> <4335D1D2.9060501@leadhill.net> <87r7bdt6o3.fsf@beaker.data-secure.net> <20051004233019.GF564@ratchet.nebcorp.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20051004233019.GF564@ratchet.nebcorp.com> User-Agent: Mutt/1.4.2.1i X-Loop: djhoward@uiuc.edu Cc: freebsd-stable@freebsd.org Subject: Re: 5.3 -> 5.4 breaks ATA (Intel ICH2) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 04 Oct 2005 23:48:47 -0000 On Tue, Oct 04, 2005 at 04:30:19PM -0700, Danny Howard wrote: > On Sun, Sep 25, 2005 at 01:10:20PM -0400, Tim Howe wrote: > > Billy Newsom writes: > > > Anyway, I count three systems that are normally boting with 5.3 or > > > 5.4, and then the upgrade to the latest 5-Stable breaks the boot. > > > > If I may make a small correction, I would like to point out that it's > > not 5-STABLE that breaks mine but 5.4-RELEASE. Even booting from the > > 5.4 mini-CD can't find the drive, but booting from the 5.3 installer > > can. > > I don't know if this helps, but I had some nasty tries installing > 5.(3?4?)-release from scratch on some SuperMicro SATA-based systems, and > while it seemed to be choking on SATA, what I did was install in "safe > mode" from the CD-ROM, compile an SMP kernel, and reboot. With the SMP > kernel, the systems ran fine, without, choking on SATA errors ... AErrr, pardon my stupidity ... this was actually on some motherboards with SCSI disks attached that were barfing on 5.3 ... my SATA machines have been just fine in this respect. :) Thanks, -danny