Re: [PATCH] 2.5.68 Fix IO_APIC IRQ assignment bug

Linus Torvalds (torvalds@transmeta.com)
Sun, 20 Apr 2003 22:58:49 +0000 (UTC)


In article <200304201811_MC3-1-3537-1648@compuserve.com>,
Chuck Ebbert <76306.1226@compuserve.com> wrote:
>
> Looks like the fix for the "ran out of interrupt sources" panic
>has a problem. It will eventually assign a device the same IRQ
>number as the first system vector, i.e. the local APIC timer.

Good call.

Although I suspect you need about a million interrupt sources to hit
this, since FIRST_SYSTEM_VECTOR is somethign like 0xef, and thus you can
hit it only when "offset" has already been incremented seven times
(which implies that we've walked the whole vector space quite a few
times by then).

Did you actually see this on hardware?

Anyway, applied as obvious.

Linus
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/