Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S264373AbTKMS4z (ORCPT ); Thu, 13 Nov 2003 13:56:55 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S264379AbTKMS4z (ORCPT ); Thu, 13 Nov 2003 13:56:55 -0500 Received: from fmr05.intel.com ([134.134.136.6]:61123 "EHLO hermes.jf.intel.com") by vger.kernel.org with ESMTP id S264373AbTKMS4x convert rfc822-to-8bit (ORCPT ); Thu, 13 Nov 2003 13:56:53 -0500 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 8BIT X-MimeOLE: Produced By Microsoft Exchange V6.0.6487.1 Subject: RE: invalid SMP mptable on Toshiba Satellite 2430-301 Date: Thu, 13 Nov 2003 10:56:34 -0800 Message-ID: <7F740D512C7C1046AB53446D37200173618736@scsmsx402.sc.intel.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: invalid SMP mptable on Toshiba Satellite 2430-301 Thread-Index: AcOqFxulbqA9O/H3T4mBD0zBrSKWZgAABc2w From: "Nakajima, Jun" To: "Jochen Voss" , "Linus Torvalds" Cc: X-OriginalArrivalTime: 13 Nov 2003 18:56:41.0118 (UTC) FILETIME=[DFBCFBE0:01C3AA17] Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2339 Lines: 71 Which kernel is this? In 2.6 we don't look at the MPS table if ACPI is available. Or ACPI detection is failing? Jun > -----Original Message----- > From: linux-kernel-owner@vger.kernel.org [mailto:linux-kernel- > owner@vger.kernel.org] On Behalf Of Jochen Voss > Sent: Thursday, November 13, 2003 10:45 AM > To: Linus Torvalds > Cc: linux-kernel@vger.kernel.org > Subject: Re: invalid SMP mptable on Toshiba Satellite 2430-301 > > Hello, > > On Thu, Nov 13, 2003 at 10:13:08AM -0800, Linus Torvalds wrote: > > Hmm.. Do you have ACPI enabled? We really shouldn't need the MP table if > > the information is elsewhere, but the mptable assumptions might be a bit > > entrenched. > > With SMP and ACPI enabled I get the following kernel > boot messages > > Intel MultiProcessor Specification v1.4 > Virtual Wire compatibility mode. > SMP mptable: bad signature [0x0]! > BIOS bug, MP table errors detected!... > ... disabling SMP support. (tell your hw vendor) > > The last message is generated by the following code > in arch/i386/kernel/mpparse.c: > > if (!smp_read_mpc((void *)mpf->mpf_physptr)) { > smp_found_config = 0; > printk(KERN_ERR "BIOS bug, MP table errors detected!...\n"); > printk(KERN_ERR "... disabling SMP support. (tell your hw > vendor)\n"); > return; > } > > I don't know what effects are caused by the 'smp_found_config = 0', > but later-on the following messages appear: > > No local APIC present or hardware disabled > ... > CPU: After generic identify, caps: bfebf9ff 00000000 00000000 > 00000000 > CPU: After vendor identify, caps: bfebf9ff 00000000 00000000 > 00000000 > CPU: Trace cache: 12K uops, L1 D cache: 8K > CPU: L2 cache: 512K > CPU: Hyper-Threading is disabled > CPU: After all inits, caps: bfebf9ff 00000000 00000000 00000080 > ... > SMP motherboard not detected. > Local APIC not detected. Using dummy APIC emulation. > Starting migration thread for cpu 0 > CPUS done 4 > > I hope this helps, > Jochen > -- > http://seehuhn.de/ - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/