LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Len Brown <lenb@kernel.org>
To: markh@compro.net
Cc: linux-kernel@vger.kernel.org, linux-acpi@vger.kernel.org
Subject: Re: 2.6.17 - weird, boot CPU (#0) not listed by the BIOS.
Date: Sat, 13 Jan 2007 01:12:39 -0500	[thread overview]
Message-ID: <200701130112.39140.lenb@kernel.org> (raw)
In-Reply-To: <45A7AE57.8020400@compro.net>

On Friday 12 January 2007 10:50, Mark Hounschell wrote:
> Mark Hounschell wrote:
> > I have a Tyan S4881 Thunder K8QW 4 processor (8 cores). Kernel 2.6.16.37 boots
> > and runs fine.
> > However kernel 2.6.17 and up doesn't. Here is my boot error msg.
> > 
> > 
> > kernel /vmlinuz-2.6.17-smp  root=/dev/sda5inux version 2.6.17-smp (root@badboy1)
> > (gcc version 4.1.0 (SUSE Linux)) #1 SMP PREEMPT Fri Jan 12 07:53:35 EST 2007
> > BIOS-provided physical RAM map:
> >  BIOS-e820: 0000000000000000 - 0000000000093800 (usable)
> >  BIOS-e820: 0000000000093800 - 00000000000a0000 (reserved)
> >  BIOS-e820: 00000000000c2000 - 0000000000100000 (reserved)
> >  BIOS-e820: 0000000000100000 - 00000000cfea0000 (usable)
> >  BIOS-e820: 00000000cfea0000 - 00000000cfea4000 (ACPI data)
> >  BIOS-e820: 00000000cfea4000 - 00000000cff00000 (ACPI NVS)
> >  BIOS-e820: 00000000cff00000 - 00000000d0000000 (reserved)
> >  BIOS-e820: 00000000e0000000 - 00000000f0000000 (reserved)
> >  BIOS-e820: 00000000fec00000 - 00000000fec00400 (reserved)
> >  BIOS-e820: 00000000fee00000 - 00000000fee01000 (reserved)
> >  BIOS-e820: 00000000fff80000 - 0000000100000000 (reserved)
> >  BIOS-e820: 0000000100000000 - 0000000230000000 (usable)
> > Warning only 4GB will be used.
> > Use a PAE enabled kernel.
> > 3200MB HIGHMEM available.
> > 896MB LOWMEM available.
> > found SMP MP-table at 000f71f0
> > DMI present.
> > ACPI: PM-Timer IO Port: 0x8008
> > ACPI: LAPIC (acpi_id[0x00] lapic_id[0x10] enabled)
> > Processor #16 15:1 APIC version 16

The APIC id for the 1st processor here is 16.
Usually it is 0.

Apparently this has confused some of the smpboot code
with all their new nifty bitmaps for processors online and offline...

Does the latest kernel work any better, say 2.6.19?
What if you throw CONFIG_NR_CPUS=32 at it?

-Len

> > ACPI: LAPIC (acpi_id[0x01] lapic_id[0x11] enabled)
> > Processor #17 15:1 APIC version 16
> > ACPI: LAPIC (acpi_id[0x02] lapic_id[0x12] enabled)
> > Processor #18 15:1 APIC version 16
> > ACPI: LAPIC (acpi_id[0x03] lapic_id[0x13] enabled)
> > Processor #19 15:1 APIC version 16
> > ACPI: LAPIC (acpi_id[0x04] lapic_id[0x14] enabled)
> > Processor #20 15:1 APIC version 16
> > ACPI: LAPIC (acpi_id[0x05] lapic_id[0x15] enabled)
> > Processor #21 15:1 APIC version 16
> > ACPI: LAPIC (acpi_id[0x06] lapic_id[0x16] enabled)
> > Processor #22 15:1 APIC version 16
> > ACPI: LAPIC (acpi_id[0x07] lapic_id[0x17] enabled)
> > Processor #23 15:1 APIC version 16
> > ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1])
> > ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1])
> > ACPI: LAPIC_NMI (acpi_id[0x02] high edge lint[0x1])
> > ACPI: LAPIC_NMI (acpi_id[0x03] high edge lint[0x1])
> > ACPI: LAPIC_NMI (acpi_id[0x04] high edge lint[0x1])
> > ACPI: LAPIC_NMI (acpi_id[0x05] high edge lint[0x1])
> > ACPI: LAPIC_NMI (acpi_id[0x06] high edge lint[0x1])
> > ACPI: LAPIC_NMI (acpi_id[0x07] high edge lint[0x1])
> > ACPI: IOAPIC (id[0x00] address[0xfec00000] gsi_base[0])
> > IOAPIC[0]: apic_id 0, version 17, address 0xfec00000, GSI 0-23
> > ACPI: IOAPIC (id[0x01] address[0xda200000] gsi_base[24])
> > IOAPIC[1]: apic_id 1, version 17, address 0xda200000, GSI 24-27
> > ACPI: IOAPIC (id[0x02] address[0xda201000] gsi_base[28])
> > IOAPIC[2]: apic_id 2, version 17, address 0xda201000, GSI 28-31
> > ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 low level)
> > Enabling APIC mode:  Flat.  Using 3 I/O APICs
> > Using ACPI (MADT) for SMP configuration information
> > Allocating PCI resources starting at d1000000 (gap: d0000000:10000000)
> > Built 1 zonelists
> > Kernel command line: root=/dev/sda5 vga=normal resume=/dev/sda2  splash=silent
> > "console=ttyS0,19200"
> > Enabling fast FPU save and restore... done.
> > Enabling unmasked SIMD FPU exception support... done.
> > Initializing CPU#0
> > PID hash table entries: 4096 (order: 12, 16384 bytes)
> > Detected 2411.454 MHz processor.
> > Using pmtmr for high-res timesource
> > Console: colour VGA+ 80x25
> > Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
> > Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
> > Memory: 3366304k/4194304k available (1529k kernel code, 38968k reserved, 633k
> > data, 184k init, 2488960k highmem)
> > Checking if this processor honours the WP bit even in supervisor mode... Ok.
> > Calibrating delay using timer specific routine.. 4827.61 BogoMIPS (lpj=9655232)
> > Security Framework v1.0.0 initialized
> > Capability LSM initialized
> > Mount-cache hash table entries: 512
> > CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line)
> > CPU: L2 Cache: 1024K (64 bytes/line)
> > CPU 0(2) -> Core 0
> > Intel machine check architecture supported.
> > Intel machine check reporting enabled on CPU#0.
> > Checking 'hlt' instruction... OK.
> > Freeing SMP alternatives: 12k freed
> > ACPI Warning (nsload-0106): Zero-length AML block in table [SSDT] [20060127]
> > CPU0: AMD Athlon(tm) or Opteron(tm) CPU-model unknown stepping 02
> > weird, boot CPU (#0) not listed by the BIOS.
> > 
> > It then just reboots. Any ideas what I need to do for 2.6.17 and up kernels. I
> > have tried all the
> > way up to 2.6.20-rc4.
> > 
> > Thanks
> > Mark
> > 
> 
> Oh, I'm running in 32 bit mode on SuSE-10.2
> 
> Mark
> -
> 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/
> 

  reply	other threads:[~2007-01-13  6:14 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-12 15:39 Mark Hounschell
2007-01-12 15:50 ` Mark Hounschell
2007-01-13  6:12   ` Len Brown [this message]
2007-01-13 12:42     ` Mark Hounschell
2007-01-15 12:51       ` Mark Hounschell

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=200701130112.39140.lenb@kernel.org \
    --to=lenb@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=markh@compro.net \
    --subject='Re: 2.6.17 - weird, boot CPU (#0) not listed by the BIOS.' \
    /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

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).