From nobody  Tue Apr  8 12:42:28 1997
Received: (from nobody@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id MAA26314;
          Tue, 8 Apr 1997 12:42:28 -0700 (PDT)
Message-Id: <199704081942.MAA26314@freefall.freebsd.org>
Date: Tue, 8 Apr 1997 12:42:28 -0700 (PDT)
From: Robert_Batten@Candle.com
To: freebsd-gnats-submit@freebsd.org
Subject: Unable to resolve dev conflict between ed0 and seagate scsi  device
X-Send-Pr-Version: www-1.0

>Number:         3230
>Category:       bin
>Synopsis:       Unable to resolve dev conflict between ed0 and seagate scsi  device
>Confidential:   no
>Severity:       serious
>Priority:       high
>Responsible:    freebsd-bugs
>State:          closed
>Quarter:
>Keywords:
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Tue Apr  8 12:50:01 PDT 1997
>Closed-Date:    Sat Aug 23 16:22:27 MEST 1997
>Last-Modified:  Sat Aug 23 16:22:53 MEST 1997
>Originator:     Rob Batten
>Release:        2.1.7
>Organization:
Candle Corporation
>Environment:
FreeBSD fairview-bsd.candle.com 2.1.7-RELEASE FreeBSD 2.1.7-RELEASE #0 Wed Feb 19 23:08:10 1997 jkh@thingy.cdrom.com:/usr/src/sys/compiler GENERIC i386
>Description:
Using the -c option on boot I attempted to resolve a device conflict between ed0 and the seagate sea0 device. Even though there appears to be no conflict ( i.e io base 280 irq 3 mmaddr 0d8000) for ed0 is not conflicting with sea0), the conf flag persists. Worse still, the problem disables my nic with edo:device timeout!!!
>How-To-Repeat:
boot with -c option, attempt to resolve
>Fix:
The hardware represented in this problem used to run with Freebsd 2.0.1. Unfortunately that is not an option for this fix.
>Release-Note:
>Audit-Trail:

From: j@uriah.heep.sax.de (J Wunsch)
To: Robert_Batten@Candle.com
Cc: freebsd-gnats-submit@FreeBSD.ORG
Subject: Re: bin/3230: Unable to resolve dev conflict between ed0 and seagate scsi  device
Date: Sun, 13 Apr 1997 02:01:50 +0200

 As Robert_Batten@Candle.com wrote:
 
 (Please break long lines.)
 
 > >Description:
 
 > Using the -c option on boot I attempted to resolve a device conflict
 > between ed0 and the seagate sea0 device. Even though there appears
 > to be no conflict ( i.e io base 280 irq 3 mmaddr 0d8000) for ed0 is
 > not conflicting with sea0), the conf flag persists. Worse still, the
 > problem disables my nic with edo:device timeout!!!
 
 Are you sure the conflict is against the sea0 driver?  Judging from
 the use of irq3, i would rather suspect a conflict with the sio1
 device.
 
 If this is not the case, please post the exact configuration as you
 tried it (i.e., the settings of all the drivers you haven't disabled).
 
 -- 
 cheers, J"org
 
 joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE
 Never trust an operating system you don't have sources for. ;-)
State-Changed-From-To: open->closed 
State-Changed-By: joerg 
State-Changed-When: Sat Aug 23 16:22:27 MEST 1997 
State-Changed-Why:  

PR stale, the originator never got back to the feedback request. 
>Unformatted:
