Date: Mon, 24 Apr 2000 19:29:27 -0700 (PDT) From: Jean-Marc Zucconi <jmz@FreeBSD.org> To: winter@jurai.net Cc: freebsd-bugs@FreeBSD.org Subject: Re: kern/18200: 3com 3c509b recognized twice during boot Message-ID: <200004250229.TAA27422@freefall.freebsd.org> In-Reply-To: <200004250210.TAA25970@freefall.freebsd.org> (winter@jurai.net) References: <200004250210.TAA25970@freefall.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
>>>>> Matthew N Dodd writes:
> The following reply was made to PR kern/18200; it has been noted by GNATS.
> From: "Matthew N. Dodd" <winter@jurai.net>
> 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.)
I am willing to test them because I also suffer from this problem.
My current solution is to do
cd /sys/dev/ep; rm *; cvs update -D"6 dec 1999"
before building my kernel :-)
Jean-Marc
--
Jean-Marc Zucconi PGP Key: finger jmz@FreeBSD.org
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200004250229.TAA27422>