From: torvalds@transmeta.com (Linus Torvalds)
To: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] 2.5.68 Fix IO_APIC IRQ assignment bug
Date: Sun, 20 Apr 2003 22:58:49 +0000 (UTC) [thread overview]
Message-ID: <b7v8n9$p8o$1@penguin.transmeta.com> (raw)
In-Reply-To: 200304201811_MC3-1-3537-1648@compuserve.com
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
next prev parent reply other threads:[~2003-04-20 22:47 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-20 22:06 [PATCH] 2.5.68 Fix IO_APIC IRQ assignment bug Chuck Ebbert
2003-04-20 22:58 ` Linus Torvalds [this message]
2003-04-20 23:05 ` Zwane Mwaikambo
2003-04-20 23:06 ` Linus Torvalds
-- strict thread matches above, loose matches on Subject: below --
2003-04-21 7:48 Chuck Ebbert
2003-04-21 15:16 ` Zwane Mwaikambo
2003-04-21 16:04 ` Mika Penttilä
2003-04-21 17:22 ` Zwane Mwaikambo
2003-04-21 17:55 ` Mika Penttilä
2003-04-22 14:59 ` Maciej W. Rozycki
2003-04-21 16:34 Nakajima, Jun
2003-04-21 17:12 ` Zwane Mwaikambo
2003-04-21 18:24 Nakajima, Jun
2003-04-21 21:48 Chuck Ebbert
2003-04-22 15:02 ` Maciej W. Rozycki
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='b7v8n9$p8o$1@penguin.transmeta.com' \
--to=torvalds@transmeta.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.