From mi@aldan.algebra.com  Mon Nov 16 21:59:09 1998
Received: from aldan.algebra.com (kot.ne.mediaone.net [24.128.29.55])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA20321
          for <FreeBSD-gnats-submit@freebsd.org>; Mon, 16 Nov 1998 21:59:08 -0800 (PST)
          (envelope-from mi@aldan.algebra.com)
Received: (from mi@localhost)
	by aldan.algebra.com (8.8.8/8.8.7) id FAA21824;
	Tue, 17 Nov 1998 05:57:52 GMT
	(envelope-from mi)
Message-Id: <199811170557.FAA21824@aldan.algebra.com>
Date: Tue, 17 Nov 1998 05:57:52 GMT
From: Mikhail Teterin <mi@aldan.algebra.com>
Reply-To: mi@aldan.algebra.com
To: FreeBSD-gnats-submit@freebsd.org
Subject: sd0 vs. da0 in SCSI device wiring
X-Send-Pr-Version: 3.2

>Number:         8720
>Category:       kern
>Synopsis:       using sd-names in SCSI "wiring" prevents booting
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    jkh
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Mon Nov 16 22:00:01 PST 1998
>Closed-Date:    Mon Feb 1 11:10:23 PST 1999
>Last-Modified:  Mon Feb  1 11:11:33 PST 1999
>Originator:     Mikhail Teterin
>Release:        FreeBSD 3.0-CURRENT i386
>Organization:
Virtual Estates, Inc.
>Environment:

	Kernel config file, that worked for ages, with some SCSI
	disks "wired down".
	
>Description:

	I had several of my disks "wired down" in the config file
	as
		controller scbus0 at ahc0 bus 0
		disk sd0 at scbus0 target 1
		disk sd1 at scbus0 target 2

	After the introduction of CAM, this silently produces
	unbootable kernel -- "can not mount root (2)" panic.

>How-To-Repeat:

	See above.

>Fix:
	
	s/sd/da/ , but one would expect sd to continue working, or,
	at least, config to complain!
>Release-Note:
>Audit-Trail:
Responsible-Changed-From-To: freebsd-bugs->jkh 
Responsible-Changed-By: gibbs 
Responsible-Changed-When: Tue Nov 17 08:14:03 PST 1998 
Responsible-Changed-Why:  
Jordan added 'sd compatibility' to the i386 config files at the time 
CAM was introduced, and although I warned him of the problem with 
hard wired configuration, he didn't extend his solution to cover that 
scenario.  My suggestion would be to nuke the 'sd' compatibility all 
together so that config returns an error. 
State-Changed-From-To: open->closed 
State-Changed-By: jkh 
State-Changed-When: Mon Feb 1 11:10:23 PST 1999 
State-Changed-Why:  
This was always a compromise solution targetted at the "general" case. 
Those with enough smarts to wire devices were also expected to have 
kept up with CAM developments. :) 
>Unformatted:
