>Number:         4619
>Category:       kern
>Synopsis:       aha and uha probes conflict
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    kern-bug-people (Kernel Bug People)
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Mon Dec  1 11:20:00 1997
>Last-Modified:
>Originator:     Dave Burgess
>Organization:
Dave Burgess                   Network Engineer - Nebraska On-Ramp, Inc.
*bsd FAQ Maintainer / SysAdmin for the NetBSD system in my spare bedroom
"Just because something is stupid doesn't mean there isn't someone that 
doesn't want to do it...."
>Release:        NetBSD 1.3-BETA <NetBSD-current source date>
>Environment:
	
System: NetBSD cynjut.neonramp.com 1.3_BETA NetBSD 1.3_BETA (CYNJUT) #1: Mon Dec 1 12:32:08 CST 1997 burgess@cynjut.neonramp.com:/usr/src/sys/arch/i386/compile/CYNJUT i386


>Description:
	
A kernel with both 'aha0' and 'uha0' on the current defaults (port 330h) and
a uha controller will cause the uha controller to not be found by the
subsequent probe.

>How-To-Repeat:
	
Build a kernel with only the uha controller and boot from it.  The
system should be fine.  Add the aha controller, build a new kernel, and
boot from that  and the uha controller will not be probed.
>Fix:
	
Like the doctor said "If it hurts when you do that, then don't do that."
Right now, I'm building a kernel for each in case I need to swap out the
controller and use one of my 1542s.
>Audit-Trail:
>Unformatted: