linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ryan Underwood <nemesis-lists@icequake.net>
To: linux-kernel@vger.kernel.org
Subject: APIC support on Slot-A Athlon, K6
Date: Mon, 8 Dec 2003 02:48:42 -0600	[thread overview]
Message-ID: <20031208084842.GA12615@dbz.icequake.net> (raw)

[-- Attachment #1: Type: text/plain, Size: 2377 bytes --]


Hello,

2.4.23 kernel on all machines, freshly compiled.

In i386/kernel/apic.c:detect_init_APIC(), we have the following lines:
switch (boot_cpu_data.x86_vendor) {
case X86_VENDOR_AMD:
	if (boot_cpu_data.x86 == 6 && boot_cpu_data.x86_model > 1)
		break;
	goto no_apic;
...

Unfortunately, this disables the APIC support (if it existed) on a
Slot-A Athlon 600 MS-6167 (family 6, model 1, AMD-751/756), and a K6/3 400
Tyan S1598 (family 5, model 9, MVP3/686A).

What is the purpose of this check?  Why is the APIC availability dependent
on the CPU, rather than just the southbridge?  Also, there are only
checks for Intel and AMD CPUs.  Is it not possible to use an APIC in
conjunction with a Cyrix, et.al. ?



On to another topic, I would also like to know if anyone has used a
Shuttle HOT-591P successfully in ACPI mode.  It passes the date check as
the BIOS is (dmidecode):
Vendor: Award Software International, Inc.
Version: 4.51 PG
Release Date: 03/27/01

board:
Manufacturer: Shuttle Inc.
Product Name: VIA APOLLO MVP3 (HOT-597)
Version: 2A5LEH2B
(It is actually a 591P, regardless of the DMI string)

However, the kernel does the following on bootup:

ACPI: Subsystem revision 20031002
PCI: PCI BIOS revision 2.10 entry at 0xfb410, last bus=1
PCI: Using configuration type 1
 tbxface-0117 [03] acpi_load_tables      : ACPI Tables successfully acquired
Parsing all Control Methods:.......................................................
Table [DSDT](id F004) - 227 Objects with 26 Devices 55 Methods 17 Regions
ACPI Namespace successfully loaded at root c02dba3c
ACPI: IRQ9 SCI: Level Trigger.
evxfevnt-0089: *** Error: Could not transition to ACPI mode.
 utxface-0170 [03] acpi_enable_subsystem : acpi_enable failed.
ACPI: Unable to start the ACPI Interpreter
evxfevnt-0127 [06] acpi_disable          : System is already in legacy (non-ACPI) mode
 utalloc-0986 [05] ut_dump_allocations   : No outstanding allocations.
PCI: Probing PCI hardware
PCI: ACPI tables contain no PCI IRQ routing entries
...

At the "ACPI: IRQ9 SCI:" part, it pauses for a few seconds before continuing.
The APIC is also not enabled on this machine, but it is a 586B southbridge, which
I am not sure contains an APIC.

Any enlightenment on these topics would be appreciated.

thanks,

-- 
Ryan Underwood, <nemesis@icequake.net>

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

             reply	other threads:[~2003-12-08  8:48 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-08  8:48 Ryan Underwood [this message]
2003-12-08 10:44 APIC support on Slot-A Athlon, K6 Mikael Pettersson
     [not found] <20031208102800.5409.87787.Mailman@lists.us.dell.com>
2003-12-08 11:58 ` Ryan Underwood
2003-12-08 12:06   ` William Lee Irwin III
2003-12-08 17:07 Mikael Pettersson

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=20031208084842.GA12615@dbz.icequake.net \
    --to=nemesis-lists@icequake.net \
    --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).