[Wylug-help] eth1 "too much work at interrupt 0x0040"

[Jim Jackson]

On Mon, 3 Jan 2005, Peter Duffy wrote:

> On Sun, 2005-01-02 at 14:19 +0000, Jim Jackson wrote:
> > AFAIK it is not a good thing that there is an IRQ clash.
> > Findf an unused IRQ and force it.
>
> Agreed that it used to be a horrendous problem with the old ISA
> architecture. However, it's not normally an issue these days: PCI
> architecture allows sharing of IRQs as a standard feature.

AFAIK there are 2 aspects here: are shared IRQs supported by the hardware
and are they suported by the ISRs of the operating system that you are
running. Common IRQs imply a common ISR entry point, so the software must
be able to determine which device interrupted.

So some drivers may correctly support shared IRQs. others might have
problems. My advice would be keep them seperate.

> (One imagines
> that it must be better to assign a separate IRQ manually to each service
> if possible, but I've never seen any recommendation to do this.)
>
>
>
> _______________________________________________
> Wylug-help mailing list
> Wylug-help at wylug.org.uk
> http://list.wylug.org.uk/mailman/listinfo/wylug-help
>