From: "Sujal Shah" <sshah@progress.com>
To: Mikael Pettersson <mikpe@csd.uu.se>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Broken APIC detection 2.4.10?
Date: 01 Oct 2001 09:48:33 -0400 [thread overview]
Message-ID: <1001944127.32358.3.camel@pcsshah> (raw)
In-Reply-To: <200109301126.NAA24615@harpo.it.uu.se>
In-Reply-To: <200109301126.NAA24615@harpo.it.uu.se>
On Sun, 2001-09-30 at 07:26, Mikael Pettersson wrote:
> On 27 Sep 2001 18:21:54 -0400, Sujal Shah wrote:
[SNIP]
> Please elaborate: What does "This" in "This was not the case before."
> refer to? The "Could not enable APIC!" boot message or the XT-PIC in
> /proc/interrupts?
>
I'm just dumb. The message was new, but the behavior (non-APIC
interrupts) was not. I'm truly sorry for any confusion.
I was trying to track down another problem (the PNPBios issue that looks
to have been patched and an ALSA driver issue) when I just saw the
message, which I had never seen before.
Sorry.
Sujal
> 2.4.10 merged code from 2.4-ac which (in some .configs) will attempt
> to enable the CPU's local APIC. The boot message above is printed if
> your CPU doesn't have one.
>
> >Anyone have any ideas why this is? The APIC stuff was getting detected
> >fine in 2.4.7.
>
> Can you send me your .configs and boot logs for both 2.4.7 and 2.4.10?
> I don't think there is an actual problem, but I'd like to make sure.
>
> /Mikael
--
---- Sujal Shah --- sujal@sujal.net ---
http://www.sujal.net
Now Playing: none
next prev parent reply other threads:[~2001-10-01 13:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-30 11:26 Broken APIC detection 2.4.10? Mikael Pettersson
2001-09-30 12:41 ` Dave Jones
2001-10-01 13:48 ` Sujal Shah [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-09-27 22:21 Sujal Shah
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=1001944127.32358.3.camel@pcsshah \
--to=sshah@progress.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mikpe@csd.uu.se \
--cc=sujal@sujal.net \
/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.