Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 31 May 1995 21:58:16 +1700 (PDT)
From:      "Rodney W. Grimes" <rgrimes@gndrsh.aac.dev.com>
To:        bde@zeta.org.au (Bruce Evans)
Cc:        bugs@ns1.win.net, current@FreeBSD.ORG
Subject:   Re: -cur boot hangs since may 1
Message-ID:  <199506010458.VAA03735@gndrsh.aac.dev.com>
In-Reply-To: <199505172031.GAA28969@godzilla.zeta.org.au> from "Bruce Evans" at May 18, 95 06:31:33 am

next in thread | previous in thread | raw e-mail | index | archive | help
> 
> >If you disable ie0 during a '-c' boot dialog (or build a kernel without ie0) 
> >then things work great.
> 
> >All my boxes have ep0 cards so I have been an unhappy boy for many days.
> 
> >I am looking at the probe technique in the ie0 driver to see what has
> >been changed.  It may be confusing the 3c509 card.
> 
> This is a known bug and was worked around in revision 1.20 (1994/11/18)
> of GENERIC.
> 
> 	Log:
> 	Put ie0 above ep0.  Otherwise, the ie0 probe clobbers it.
> 
> The work around was broken by sorting the devices in revision 1.38
> (1995/04/08).

Thanks for the leg work Bruce, I have commited what I think should fix
this and document it well enough that it does not happen until some
one fixes these probes up to not smash each other.

> The conflict is probably because      if_ie.c uses port ELINK_ID_PORT which
> is defined in elink.h    as 0x100 and if_ep.c uses port    EP_ID_PORT which
> is defined in if_epreg.h as 0x100.  The conflict is not detected because
> use of these ports is not recorded in the config file (there is no room
> for it) and the base ports don't conflict.  The conflict is not obvious
> in isa.h because few or no network ports are recorded there.
> 
> Bruce
> 


-- 
Rod Grimes                                      rgrimes@gndrsh.aac.dev.com
Accurate Automation Company                   Custom computers for FreeBSD



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199506010458.VAA03735>