From: Mikael Pettersson <mikpe@csd.uu.se>
To: linux-kernel@vger.kernel.org, munnikes@cistron.nl
Subject: Re: PROBLEM: spurious 8259A interrupt: IRQ7. AND VM: killing process ..
Date: Wed, 26 Sep 2001 22:27:45 +0200 (MET DST) [thread overview]
Message-ID: <200109262027.WAA05553@harpo.it.uu.se> (raw)
On Wed, 26 Sep 2001 18:22:26 +0200, Alfred Munnikes wrote:
>With a new compiled kernel 2.4.10 I have the next problem's
>
>first is gives the message "spurious 8259A interrupt: IRQ7."
>...
>I have a Abit KT7-raid with KT133 chipset, may the problem a hardware
>...
>Local APIC disabled by BIOS -- reenabling.
>Found and enabled local APIC!
>...
>enabled ExtINT on CPU#0
>ESR value before enabling vector: 00000000
>ESR value after enabling vector: 00000000
>Using local APIC timer interrupts.
>calibrating APIC timer ...
>..... CPU clock speed is 900.0498 MHz.
>..... host bus clock speed is 200.0110 MHz.
You didn't include your .config, but it seems you have
CONFIG_X86_UP_IOAPIC=y.
Please try either 2.4.10 with CONFIG_X86_UP_IOAPIC=n (don't worry,
you don't need it and won't lose any performance) or 2.4.9-ac with
CONFIG_X86_UP_IOAPIC=n and CONFIG_X86_UP_APIC=y.
There seems to be something amiss with the merge of the UP local APIC
code from -ac (where it's brilliant, but I'm biased) in 2.4.10, but I
haven't had time to investigate. I'm almost certain that it was a mistake
to lump UP *local APIC* and UP *IO-APIC* together under the same config
option in 2.4.10 -- they're separate in 2.4-ac.
/Mikael
next reply other threads:[~2001-09-26 20:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-26 20:27 Mikael Pettersson [this message]
2001-09-26 23:08 ` Wayne Whitney
-- strict thread matches above, loose matches on Subject: below --
2001-09-26 16:22 Alfred Munnikes
2001-09-26 17:00 ` Ingo Molnar
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=200109262027.WAA05553@harpo.it.uu.se \
--to=mikpe@csd.uu.se \
--cc=linux-kernel@vger.kernel.org \
--cc=munnikes@cistron.nl \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®