Date: Tue, 8 Apr 1997 12:42:28 -0700 (PDT) From: Robert_Batten@Candle.com To: freebsd-gnats-submit@freebsd.org Subject: bin/3230: Unable to resolve dev conflict between ed0 and seagate scsi device Message-ID: <199704081942.MAA26314@freefall.freebsd.org> Resent-Message-ID: <199704081950.MAA26764@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
>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: open >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Tue Apr 8 12:50:01 PDT 1997 >Last-Modified: >Originator: Rob Batten >Organization: Candle Corporation >Release: 2.1.7 >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. >Audit-Trail: >Unformatted:
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199704081942.MAA26314>