From mi@guest.zipnet.net  Sun May 19 09:08:20 1996
Received: from guest.zipnet.net (guest.zipnet.net [199.232.255.43])
          by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id JAA03431
          for <FreeBSD-gnats-submit@freebsd.org>; Sun, 19 May 1996 09:08:18 -0700 (PDT)
Received: (from mi@localhost) by guest.zipnet.net (8.7.5/8.7.3) id MAA00384; Sun, 19 May 1996 12:10:08 GMT
Message-Id: <199605191210.MAA00384@guest.zipnet.net>
Date: Sun, 19 May 1996 12:10:08 GMT
From: Mikhail Teterin <mi@guest.zipnet.net>
Reply-To: mi@aldan.zipnet.net
To: FreeBSD-gnats-submit@freebsd.org
Subject: second IDE-harddrive on the second IDE channel 
X-Send-Pr-Version: 3.2

>Number:         1217
>Category:       kern
>Synopsis:       separating to hardrives to two IDE channels hangs the OS
>Confidential:   no
>Severity:       critical
>Priority:       high
>Responsible:    freebsd-bugs
>State:          closed
>Quarter:
>Keywords:
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Sun May 19 09:10:01 PDT 1996
>Closed-Date:    Sun Feb 16 10:29:30 PST 1997
>Last-Modified:  Sun Feb 16 10:31:06 PST 1997
>Originator:     Mikhail Teterin
>Release:        FreeBSD 2.2-960501-SNAP i386
>Organization:
>Environment:

	Embedded PCI dual-channel IDE controller (seen as wdc0 and
	wdc1) Neptune chip-set. EISA and PCI buses. Pentium-100.
	NEC Image-P100E machine.  Two Conner CFS1257A disks. Custom
	built kernel.

>Description:

	If I put every disk on it's own IDE channel (motherboard has
	two IDE plugs), mounting the partition on the second drive goes
	fine, but attempt to read a file from there hangs the entire machine,
	although I can do `ls' before reading, and see the correct output.
	Tried async and read-only mounting also. Same effect.

>How-To-Repeat:

	See description.
>Fix:
	
	Put the drives on the same IDE channel (as master and slave).
	But, I thought, I can gain a few percents of performance by
	splitting them.
>Release-Note:
>Audit-Trail:
State-Changed-From-To: open->analyzed 
State-Changed-By: phk 
State-Changed-When: Mon Oct 21 12:54:23 PDT 1996 
State-Changed-Why:  
I will presume this is a hardware problem or possibly bios problem. 
I have run the same setup without problems, although not on PCI, 
considering the amount of PCI knowledge our driver has (none) 
I deem that to be a non-issue. 

Suggest you check your bios settings and/or upgrade the BIOS if  
possible. 

This PR closes Nov 1st unless new data should dictate otherwise. 

State-Changed-From-To: analyzed->closed 
State-Changed-By: mpp 
State-Changed-When: Sun Feb 16 10:29:30 PST 1997 
State-Changed-Why:  
In the audit trail, phk stated that this PR should be 
closed on 11/1/96 if no new data proved otherwise. 
>Unformatted:
