From nobody@FreeBSD.ORG  Wed Jun 14 08:19:46 2000
Return-Path: <nobody@FreeBSD.ORG>
Received: by hub.freebsd.org (Postfix, from userid 32767)
	id D6E4A37C234; Wed, 14 Jun 2000 08:19:46 -0700 (PDT)
Message-Id: <20000614151946.D6E4A37C234@hub.freebsd.org>
Date: Wed, 14 Jun 2000 08:19:46 -0700 (PDT)
From: larse@isi.edu
Sender: nobody@FreeBSD.ORG
To: freebsd-gnats-submit@FreeBSD.org
Subject: 4.0-RELEASE: Promise Ultra66 install problem
X-Send-Pr-Version: www-1.0

>Number:         19266
>Category:       kern
>Synopsis:       4.0-RELEASE: Promise Ultra66 install problem
>Confidential:   no
>Severity:       critical
>Priority:       high
>Responsible:    freebsd-bugs
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Wed Jun 14 08:20:01 PDT 2000
>Closed-Date:    Mon Jun 26 12:23:30 PDT 2000
>Last-Modified:  Mon Jun 26 12:24:00 PDT 2000
>Originator:     Lars Eggert
>Release:        4.0-RELEASE
>Organization:
USC/ISI
>Environment:
don't get that far
>Description:
I'm having a strange problem booting after installing 4.0-RELEASE onto a
Maxtor 7200rpm ATA66 drive attached to a Promise Ultra66 controller.

Installation (booted from CD-ROM) went by without problems, but booting off the drive fails at
varying points during boot0 or the BTX boot loader. Sometimes I see a
message about "elf_loadexec: archsw.readin failed", sometimes not even that.

If I move the drive on the onboard (standard) IDE controller, I can boot
fine (until the time comes to mount things, because the fstab is wrong, but
that is to be expected.)

The system also has an onboard SCSI controller with drives attached and
3.4-RELEASE installed, could that be part of the problem? (Disabling it
didn't make a difference.)

I checked the archive, and the recommended fix for the "archsw.readin"
problem seems to be to reinstall boot blocks. I can't do this, however,
since I can't boot from the drive. I've redone the installation, would that
have the same effect? But wouldn't the boot blocks be okay anyway, since I
can boot if the drive is connected to a standard IDE controller?
>How-To-Repeat:

>Fix:
Workaround: Move drive onto onboard standard IDE controller. (Uses slower BIOSPIO though.)

>Release-Note:
>Audit-Trail:

From: Lars Eggert <larse@ISI.EDU>
To: freebsd-gnats-submit@FreeBSD.org, larse@ISI.EDU
Cc:  
Subject: Re: kern/19266: 4.0-RELEASE: Promise Ultra66 install problem
Date: Mon, 26 Jun 2000 11:57:00 -0700

 Please close. Problem caused by faulty hardware.
 -- 
 Lars Eggert <larse@isi.edu>                 Information Sciences Institute
 http://www.isi.edu/~larse/               University of Southern California
 
State-Changed-From-To: open->closed 
State-Changed-By: nrahlstr 
State-Changed-When: Mon Jun 26 12:23:30 PDT 2000 
State-Changed-Why:  
Submitter reports faulty hardware. 


http://www.freebsd.org/cgi/query-pr.cgi?pr=19266 
>Unformatted:
