public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jan Kasprzak <kas@fi.muni.cz>
To: Len Brown <lenb@kernel.org>
Cc: linux-kernel@vger.kernel.org, linux-acpi@vger.kernel.org
Subject: Re: No mptable found (Tyan h1000E)
Date: Wed, 31 Jan 2007 12:41:36 +0100	[thread overview]
Message-ID: <20070131114136.GC6403@fi.muni.cz> (raw)
In-Reply-To: <200701310252.16653.lenb@kernel.org>

Len Brown wrote:
: This board appears to have no APIC (MADT) table -- which is what Linux uses to enumerate processors
: in ACPI mode.  (doesn't have MPS either, but in ACPI mode you wouldn't use it anyway).
: 
: Are there any BIOS SETUP settings for enabling SMP or ACPI features?
: 
	In the ACPI submenu there are following options:

ACPI version features (1.0, 2.0, 3.0 - I have set it to 3.0, but I think
	I have tried 2.0 as well)
ACPI APIC support (I have Enabled)
ACPI SRAT table (Enabled)
ACPI OEMB table (Enabled)
Headless mode (Disabled)

Then there is a MPS option in a different submenu (I have 1.4, but I have
	tried 1.1 as well).

Another APIC related function is in the southbridge setup:
Hide XIOAPIC PCI function (I think I have it disabled[*])

[*] I had to put this box to production use (even with one CPU visible),
	but I will have an identical box available in two weeks or so,
	so I can do more testing then.

: I guess that /proc/interrupts shows this system running in PIC mode?

	Yes, of course.

: Please open a bugzilla here and attach the output from acpidump.
: http://bugzilla.kernel.org/enter_bug.cgi?product=ACPI
: Component: Config-Processors
: 
	Done, http://bugzilla.kernel.org/show_bug.cgi?id=7908
BTW, when trying to attach the dmesg output to the bugzilla entry, I've
got the following message:

> Attachment #10239 to Bug #7908 Created
> /home/www/dead.letter... Saved message in /home/www/dead.letter
> Email sent to: acpi_config-processors@kernel-bugs.osdl.org,
> acpi-bugzilla@lists.sourceforge.net
> Excluding: kas@fi.muni.cz

	I think the dead.letter message should not be there :-)
Apparently, this bugzilla does not have a "bugzilla" category.
Where can I report this?

: Any chance you can see if Windows finds multiple processors on this board with this version of the BIOS?
: 
	I can try this in two weeks or so.

: ps. after you get the acpidump for the failing system, check for a BIOS update.

	In the pervious mail I wrote:
[...]
: > the latest Fedora kernel (2.6.19-1.2895.fc6). I have the latest BIOS
: > available for this board, and the BIOS can see all four cores.

	So AFAIK there is no BIOS update available.

-Yenya

-- 
| Jan "Yenya" Kasprzak  <kas at {fi.muni.cz - work | yenya.net - private}> |
| GPG: ID 1024/D3498839      Fingerprint 0D99A7FB206605D7 8B35FCDE05B18A5E |
| http://www.fi.muni.cz/~kas/    Journal: http://www.fi.muni.cz/~kas/blog/ |
> I will never go to meetings again because I think  face to face meetings <
> are the biggest waste of time you can ever have.        --Linus Torvalds <

      reply	other threads:[~2007-01-31 11:45 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-30 23:16 No mptable found (Tyan h1000E) Jan Kasprzak
2007-01-31  7:52 ` Len Brown
2007-01-31 11:41   ` Jan Kasprzak [this message]

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=20070131114136.GC6403@fi.muni.cz \
    --to=kas@fi.muni.cz \
    --cc=lenb@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --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