geiri@jk1.Cc.UiT.No (Geir Inge Jensen) writes:
> May 19 23:11:27 jk1 /netbsd: com2 at isa0 port 0x3e8-0x3ef irq 5: ns16550a, work
> ing fifo

I just noticed that in the last 9 days my first PCI ethernet card de0,
started getting irq 5 assigned to it (which conflicts with comm2). It
used to be at irq 14.

    NetBSD 1.2E (WSRCC) #2: Fri May  9 20:28:18 PDT 1997
    de0 at pci0 dev 15 function 0 at irq 14
    com2 at isa0 port 0x3e8-0x3ef irq 5: ns16550a, working fifo

    NetBSD 1.2E (WSRCC) #3: Sun May 18 21:13:46 PDT 1997
    de0 at pci0 dev 15 function 0 at irq 5
    com2 at isa0 port 0x3e8-0x3ef irq 5: ns16550a, working fifo

Could it be that your comm port is being polled because something
*else* got an interrupt?

Does anyone that understands how the IRQ's get handed out know why 1)
the de0 is now getting the same IRQ that will later be handed out to
comm2 ?

-wolfgang
-- 
Wolfgang Rupprecht    <wolfgang@wsrcc.com>     http://www.wsrcc.com/
Sick of spam?  Check out all the crap we've gotten. http://www.wsrcc.com/spam/