[email protected] wrote:
>>> How about giving your sound device a proper seperate IRQ number?
>>> At least libata should like eth0 have its own kernel resources.
>> That's an issue with the way the motherboard IRQ lines are wired.
>> There's nothing the kernel can do about it.
>
> That sounds rather strange to me, as IRQ line 16 is a virtual
> IRQ as part of IO-APIC.
It's still generally wired that way on the motherboard, both devices are
connected to the same IRQ line. Or at least, the kernel has no control
over what devices are routed to what IRQs. It gets the IRQ mapping from
the BIOS and uses it.
>
>> Normally I wouldn't expect that to make a big difference though..
>
> fact is that when copying a iso from one SATA disk to the
> other results in flaky sound when playing online internet radio.
> Even starting firefox for the 1st time after booting results
> in flaky sound for a short time.
>
>> You'd really have to try a newer kernel first in order to get much help,
>> though. That's a pretty ancient kernel. Quite likely the situation is
>> improved in newer versions.
>
> I sure would like todo that. But why doesn't the linux-kernel community
> know howto pull virtual IRQ lines apart, as part of configuring
> a linux kernel? In the days of 386/486 cpu's, IRQ's of several
> add-on cards could be adjusted manually by jumpers. Why is there not
> such a thing for virtual IRQ's inside the IO-APIC system?
>
> The libata driver should like eth0 on IRQ 19 have its own IRQ.
You'd have to take that up with your motherboard manufacturer,
unfortunately :-)