linux-acpi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dave Jones <davej@redhat.com>
To: Len Brown <lenb@kernel.org>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>, linux-acpi@vger.kernel.org
Subject: Re: SMP broken on pre-ACPI machine.
Date: Thu, 19 Oct 2006 15:16:44 -0400	[thread overview]
Message-ID: <20061019191644.GE26530@redhat.com> (raw)
In-Reply-To: <200610190133.40581.len.brown@intel.com>

On Thu, Oct 19, 2006 at 01:33:40AM -0400, Len Brown wrote:
 > On Wednesday 18 October 2006 18:24, Dave Jones wrote:
 > > I've been chasing a bug that got filed against the Fedora kernel
 > > a while back:  https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=199052
 > > This is a dual pentium pro from an era before we had ACPI, and
 > > it seems to be falling foul of this test in smpboot.c  ..
 > > 
 > >     if (!smp_found_config && !acpi_lapic) {
 > >         printk(KERN_NOTICE "SMP motherboard not detected.\n");
 > > 
 > > My initial reaction is that the !acpi_lapic test should be conditional
 > > on some variable that gets set if the ACPI parsing actually succeeded.
 > 
 > acpi_lapic isn't related to the problem at hand -- that  smp_found_config is not set.

Right, it just seemed odd to me when I was eyeballing this code.

 > That said, allowing acpi_lapic=1 to bail out of this check has the sole
 > function of allowing SMP/PIC configurations.  (smp_found_config
 > in ACPI mode is set if acpi_lapic and acpi_ioapic are set)
 > SMP/PIC configurations are not very interesting, except for debugging.
 > Indeed, MPS prohibits them by mandating an IOAPIC be present for SMP --
 > but ACPI has no such rule.

Why smp_found_config isn't set in that guys configuration is a mystery to me,
as his MPS tables look sane..

MP Table:
#	APIC ID	Version	State		Family	Model	Step	Flags
#	 0	 0x10	 BSP, usable	 6	 2	 1	 0x0381
#	 0	 0x10	 AP, usable	 6	 1	 7	 0xfbff

Hmm, wait, he has unpaired CPUs. I wonder if that's the reason.
I know *some* combinations of PPro's are valid to be paired, but I'll
need to dig out the old docs to be sure.

	Dave

-- 
http://www.codemonkey.org.uk

  reply	other threads:[~2006-10-19 19:17 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20061018222433.GA4770@redhat.com>
2006-10-18 23:48 ` SMP broken on pre-ACPI machine Sergio Monteiro Basto
2006-10-19  3:04   ` Dave Jones
2006-10-19  5:33 ` Len Brown
2006-10-19 19:16   ` Dave Jones [this message]
2006-10-19 20:11     ` Dave Jones
2006-10-19 22:17       ` Alan Cox
2006-10-19 23:20         ` Dave Jones

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=20061019191644.GE26530@redhat.com \
    --to=davej@redhat.com \
    --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;
as well as URLs for NNTP newsgroup(s).