From owner-freebsd-bugs Mon Apr 24 19:22: 3 2000 Delivered-To: freebsd-bugs@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id 13E1837BC55 for ; Mon, 24 Apr 2000 19:22:01 -0700 (PDT) (envelope-from gnats@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.9.3/8.9.2) id TAA25970; Mon, 24 Apr 2000 19:10:07 -0700 (PDT) (envelope-from gnats@FreeBSD.org) Date: Mon, 24 Apr 2000 19:10:07 -0700 (PDT) Message-Id: <200004250210.TAA25970@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org Cc: From: "Matthew N. Dodd" Subject: Re: kern/18200: 3com 3c509b recognized twice during boot Reply-To: "Matthew N. Dodd" Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org The following reply was made to PR kern/18200; it has been noted by GNATS. From: "Matthew N. Dodd" To: beirne@limerick.chicago.il.us Cc: freebsd-gnats-submit@FreeBSD.ORG Subject: Re: kern/18200: 3com 3c509b recognized twice during boot Date: Mon, 24 Apr 2000 21:59:18 -0400 (EDT) On Mon, 24 Apr 2000 beirne@limerick.chicago.il.us wrote: > During boot process, it recognizes two 3c509b cards one as ep0 and the > other as ep1. Ep0 gives the error "eeprom not responding". Doing an > "ifconfig ep0" will hang the machine. "ifconfig ep1" will work > though. I went back to the 3.4 release which works fine with the same > system. > >How-To-Repeat: > Install a 3Com 3c509b on an i386 architecture box and watch during > the boot process. Thats funny, all of mine work fine. Please boot verbose and send me the output. I have patches that may need to be brought back to -STABLE to address this problem. (If its what I think it is.) -- | Matthew N. Dodd | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD | | winter@jurai.net | 2 x '84 Volvo 245DL | ix86,sparc,pmax | | http://www.jurai.net/~winter | This Space For Rent | ISO8802.5 4ever | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message