From: Torsten Duwe <duwe@caldera.de>
To: aj@dungeon.inka.de (Andreas Jellinghaus)
Cc: linux-kernel@vger.kernel.org
Subject: [Oops] apic, smp and k6
Date: Mon, 27 Nov 2000 15:11:00 +0100 (CET) [thread overview]
Message-ID: <14882.27508.534457.187156@ns.caldera.de> (raw)
In-Reply-To: <20001124181723.BAAC7B7813@dungeon.inka.de>
In-Reply-To: <20001124181723.BAAC7B7813@dungeon.inka.de>
>>>>> "Andreas" == Andreas Jellinghaus <aj@dungeon.inka.de> writes:
Andreas> a dual board (meant for pentium) with one k6 200 and a
Andreas> 2.4.0-test11 kernel with APIC support enabled does oops
Andreas> here. removed the APIC support, and now everything is fine. i
Andreas> read here it´s a known problem ? at least someone else reported
Andreas> this, and it´s the same problem here.
Yes, a colleague of mine has a similar beast, hence Caldera ships for quite a
while now with an appropriate patch. Now Christoph Hellwig has identified a
simpler solution (updated for -test11 by me):
--- linux/arch/i386/kernel/setup.c~ Fri Jul 7 04:42:06 2000
+++ linux/arch/i386/kernel/setup.c Tue Jul 18 19:22:48 2000
@@ -785,7 +785,8 @@
/*
* get boot-time SMP configuration:
*/
- if (smp_found_config)
+ if (smp_found_config && /* try only if the cpu has a local apic */
+ test_bit(X86_FEATURE_APIC, boot_cpu_data.x86_capability))
get_smp_config();
#endif
#ifdef CONFIG_X86_LOCAL_APIC
I think Alan has a similar thing in his test11-ac* series.
Hope that helps,
Torsten
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2000-11-27 14:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-24 18:17 [Oops] apic, smp and k6 Andreas Jellinghaus
2000-11-27 14:11 ` Torsten Duwe [this message]
2000-11-27 14:52 ` Alan Cox
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=14882.27508.534457.187156@ns.caldera.de \
--to=duwe@caldera.de \
--cc=Torsten.Duwe@caldera.de \
--cc=aj@dungeon.inka.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).