From nobody@FreeBSD.ORG Mon Aug 16 06:08:21 1999
Return-Path: <nobody@FreeBSD.ORG>
Received: by hub.freebsd.org (Postfix, from userid 32767)
	id 26D3414F03; Mon, 16 Aug 1999 06:08:21 -0700 (PDT)
Message-Id: <19990816130821.26D3414F03@hub.freebsd.org>
Date: Mon, 16 Aug 1999 06:08:21 -0700 (PDT)
From: andrew.lofthouse@robins.af.mil
Sender: nobody@FreeBSD.ORG
To: freebsd-gnats-submit@freebsd.org
Subject: 3.- branch hardware probe does not detect primary IDE controller
X-Send-Pr-Version: www-1.0

>Number:         13174
>Category:       kern
>Synopsis:       3.- branch hardware probe does not detect primary IDE controller
>Confidential:   no
>Severity:       critical
>Priority:       high
>Responsible:    freebsd-bugs
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Mon Aug 16 06:10:01 PDT 1999
>Closed-Date:    Mon Oct 4 06:40:53 PDT 1999
>Last-Modified:  Mon Oct  4 06:44:54 PDT 1999
>Originator:     Andrew Lofthouse
>Release:        3.2-STABLE
>Organization:
>Environment:
I cant' say (I'm not on my machine); something like: "FreeBSD lofthouse.my.domain 3.2-STABLE Sun 15 Aug 21:12:15 EDT root@lofthouse.my.domain:/usr/src/sys/compile/LOFTHOUSE i386"
P200 MMX with Intel 430TX chipset (includes PIIX4 Bus-Master IDE controller), Award BIOS 4.51 PGM, PnP BIOS 1.0A, AOpen AP5TC RC1.10 motherboard. 
>Description:
3.2-RELEASE (and 3.0-STABLE, for that matter), do not detect the primary IDE controller (wdc0). When the BIOS settings are changed to "hard drive auto-detect" and then saved, the controller is detected that time. This work-around only works one time. If the machine is rebooted, I need to enter BIOS setup and save settings, then the controller is detected again. 

NOTE: problem report KERN/11513 MAY be a related problem. In that problem report, the dmesg output showed that the primary IDE controller was not detected ("wdc0 not found at 0x1f0"). The submitter also uses the Intel 430TX chipset (or at least one that uses the same PIIX4 controller):
"chip0: <Intel 82443BX host to PCI bridge> rev 0x03 on pci0.0.0
chip1: <Intel 82443BX host to AGP bridge> rev 0x03 on pci0.1.0
chip2: <PCI to PCI bridge (vendor=1011 device=0024)> rev 0x03 on pci0.2.0
chip3: <Intel 82371AB PCI to ISA bridge> rev 0x02 on pci0.7.0
ide_pci0: <Intel PIIX4 Bus-master IDE controller> rev 0x01 on pci0.7.1
chip4: <Intel 82371AB Power management controller> rev 0x02 on pci0.7.3"


>How-To-Repeat:
Install 3.2-RELEASE (or -STABLE) on the machine. Attempt to boot without re-setting BIOS settings each time.
>Fix:


>Release-Note:
>Audit-Trail:

From: Lofthouse Andrew 2Lt WRALC/TIECT <Andrew.Lofthouse@robins.af.mil>
To: freebsd-gnats-submit@freebsd.org,
	Lofthouse Andrew 2Lt WRALC/TIECT <Andrew.Lofthouse@robins.af.mil>
Cc:  
Subject: re: kern/13174: 3.- branch hardware probe does not detect primary
	 ide controller
Date: Tue, 17 Aug 1999 08:28:50 -0400

 >>Additional Information: I have two hard drives connected to the primary
 IDE controller (wdc0),
 a 1.27 GB Samsung as master and a 6.54 GB Seagate as slave. I have an ATAPI
 CD-ROM
 drive as master on the secondary controller (wdc1). wdc1 is detected
 correctly every time I boot
 the machine. wdc0 is not detected unless I enter BIOS setup and save
 settings as I mentioned
 above. This is only a problem with 3.- branch (I've had 2.2.8-RELEASE on the
 same machine
 with no problems). The critical nature of this bug refers to the fact that
 the root filesystem cannot
 be mounted without the primary controller being detected (I have no SCSI
 drives on the system).
 
 
State-Changed-From-To: open->feedback 
State-Changed-By: sheldonh 
State-Changed-When: Fri Oct 1 05:04:21 PDT 1999 
State-Changed-Why:  
Any news on this one? 
State-Changed-From-To: feedback->closed 
State-Changed-By: sheldonh 
State-Changed-When: Mon Oct 4 06:40:53 PDT 1999 
State-Changed-Why:  
Originator moved two disks, which he now suspects didn't like each 
other, onto separate channels and has had things working 
with  that configuration since then. 
>Unformatted:
