There's 2 ways to really look at this:

1. wssattach() looks at already assigned irq's and doesn't try to attach if
   it's irq is taken. (Ok, yuck..violates some abstraction and gets very bad
   very quick).

2. Have isa_intr_establish return NULL on conflict cases and all drivers that
   use it start checking return values. (Not horrible, but would require some
   fairly wide code changes).

James

>
>	How difficult would it be to just make the isa wss attach fail in
>	this case?
>
>		David/absolute		-- www.netbsd.org: No hype required --
>
>
>On Wed, 20 Dec 2000 jchacon@genuity.net wrote:
>
>> I have multiple machines with wss in them that aren't on irq 10, but the PCI
>> puts an ethernet card on that irq.
>>
>> The problem is that any irq conflicts in a machine caused by auto-probed irq's
>> conflicting with hard coded ones like the wss isa one result in a panic() since
>> the interrupt handler registration routine has no error handling to speak of.
>>
>> James
>>
>> >
>> >Just commenting out wss seems to be the wrong "solution".  Surely
>> >the same problem can occur with other devices that happen to
>> >share an IRQ with a PCI device.  Are you going to comment out all
>> >ISA devices?
>> >
>> >What is the exact panic you are getting?  If this is a resource conflict
>> >problem I think we should try and solve it, not just dodge it.
>> >
>> >    -- Lennart
>> >
>> >
>> >jchacon@genuity.net wrote:
>> >
>> >> In this specific case it was conflicting with any PCI device that happens
>> >> to get auto-assigned to irq 10 on a machine.
>> >>
>> >> GENERIC is what we install for any new build. The last thing you want that
>> >> doing on the first reboot is panic'ing because the sound card has issues...
>> >> Most hardware you live with the risk, but in the case it's a sound card which
>> >> is to me, a secondary concern to making work.
>> >>
>> >> People treat GENERIC as the kitchen sink for all devices and all options
>> >> which is fine. However until it's not the default install kernel though it
>> >> really should boot on 99% of the systems out there.
>> >>
>> >> James
>> >>
>> >> >| Module Name: syssrc
>> >> >| Committed By:        jmc
>> >> >| Date:                Sun Dec 17 22:53:52 UTC 2000
>> >> >|
>> >> >| Modified Files:
>> >> >|        syssrc/sys/arch/i386/conf: GENERIC
>> >> >|
>> >> >| Log Message:
>> >> >| Comment out the isa wss driver.
>> >> >|
>> >> >| GENERIC is the kernel used on new installs and too many things overlap the
>> >> >| resources (irq mostly) the default isa version may be using which causes
>> >> >| panics on reboot.
>> >> >
>> >> >This makes me very queasy.
>> >> >
>> >> >I am unconvinced it is justified -- can you please justify it for me?
>> >> >
>> >> >Such a change should come along with an explanation in wss(4) about it,
>> >> >possibly in a BUGS section, as well as a CHANGES entry indicating
>> >> >that this took place.
>> >> >
>> >> >It would be nice to have an enumeration of what the items are that
>> >> >conflict with the wss at isa are what the right solution is for folks.
>> >> >
>> >> >--jhawk
>> >> >
>> >> >
>> >> >
>> >> >
>> >
>> >
>> >
>> >
>> >
>>
>>
>
>
>
>
>