From: Gabriel C <nix.or.die@googlemail.com>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Cc: Ingo Molnar <mingo@elte.hu>, Ingo Molnar <mingo@redhat.com>,
Andrew Morton <akpm@linux-foundation.org>,
Thomas Gleixner <tglx@linutronix.de>,
"H. Peter Anvin" <hpa@zytor.com>
Subject: Re: BIOS bug, APIC version is 0 for CPU#0!
Date: Sat, 03 May 2008 21:10:42 +0200 [thread overview]
Message-ID: <481CB8B2.7030404@googlemail.com> (raw)
In-Reply-To: <4810D12E.4030700@googlemail.com>
Gabriel C wrote:
> Gabriel C wrote:
>> Hi,
>>
>> I've just compiled latest linus git tree and getting now on an Q9300 Core2Quad , ASUS P5E-VM DO motherboard with BIOS Ver. 0606 , BIOS Rev. 8.12
>> the BIOS bug for CPU#0 message for each processor ?!? That seems somewhat buggy ?:)
>>
>> That BIOS version is beta and may be really buggy but I never got such a message on 2.6.24* nor on 2.6.25.
>>
>>
>> --($:~)-- uname -a
>> Linux thor 2.6.25-03530-g94bc891 #773 SMP PREEMPT Wed Apr 23 13:55:10 CEST 2008 i686 GNU/Linux
>>
>>
>> ..
>>
>> [ 0.000000] ACPI: PM-Timer IO Port: 0x808
>> [ 0.000000] ACPI: Local APIC address 0xfee00000
>> [ 0.000000] ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled)
>> [ 0.000000] BIOS bug, APIC version is 0 for CPU#0! fixing up to 0x10. (tell your hw vendor)
>> [ 0.000000] ACPI: LAPIC (acpi_id[0x02] lapic_id[0x01] enabled)
>> [ 0.000000] BIOS bug, APIC version is 0 for CPU#0! fixing up to 0x10. (tell your hw vendor)
>> [ 0.000000] ACPI: LAPIC (acpi_id[0x03] lapic_id[0x02] enabled)
>> [ 0.000000] BIOS bug, APIC version is 0 for CPU#0! fixing up to 0x10. (tell your hw vendor)
>> [ 0.000000] ACPI: LAPIC (acpi_id[0x04] lapic_id[0x03] enabled)
>> [ 0.000000] BIOS bug, APIC version is 0 for CPU#0! fixing up to 0x10. (tell your hw vendor)
>> [ 0.000000] ACPI: IOAPIC (id[0x04] address[0xfec00000] gsi_base[0])
>> [ 0.000000] IOAPIC[0]: apic_id 4, version 32, address 0xfec00000, GSI 0-23
>> [ 0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
>> [ 0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
>> [ 0.000000] ACPI: IRQ0 used by override.
>> [ 0.000000] ACPI: IRQ2 used by override.
>> [ 0.000000] ACPI: IRQ9 used by override.
>> [ 0.000000] Enabling APIC mode: Flat. Using 1 I/O APICs
>> [ 0.000000] ACPI: HPET id: 0xffffffff base: 0xfed00000
>> [ 0.000000] Using ACPI (MADT) for SMP configuration information
>>
>> ...
>>
>> Please let me know if you need more infos , dmesg , config etc .
>>
>
> I don't see that message on the same kernel but built for 64bit.
>
> ...
>
> [ 0.000000] ACPI: PM-Timer IO Port: 0x808
> [ 0.000000] ACPI: Local APIC address 0xfee00000
> [ 0.000000] ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled)
> [ 0.000000] ACPI: LAPIC (acpi_id[0x02] lapic_id[0x01] enabled)
> [ 0.000000] ACPI: LAPIC (acpi_id[0x03] lapic_id[0x02] enabled)
> [ 0.000000] ACPI: LAPIC (acpi_id[0x04] lapic_id[0x03] enabled)
> [ 0.000000] ACPI: IOAPIC (id[0x04] address[0xfec00000] gsi_base[0])
> [ 0.000000] IOAPIC[0]: apic_id 4, version 0, address 0xfec00000, GSI 0-23
> [ 0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
> [ 0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
> [ 0.000000] ACPI: IRQ0 used by override.
> [ 0.000000] ACPI: IRQ2 used by override.
> [ 0.000000] ACPI: IRQ9 used by override.
> [ 0.000000] Setting APIC routing to flat
> [ 0.000000] ACPI: HPET id: 0xffffffff base: 0xfed00000
> [ 0.000000] Using ACPI (MADT) for SMP configuration information
>
> ...
>
>
> So it is 32bit only ? And if yes how it is a HW bug ?
>
Hi all ,
I'm testing current git on 3 boxes and all got these annoying messages so far on 32bit kernels on all 3 ..
( After a quick scan on LKML posted dmesg's from current git I see a lot such messages too )
Could someone please explain why my HW is broken and why this 'BIOS bug' message is only
relevant on 32bit ?
generic_processor_info() in apic_64.c does not have such an check. If is a HW bug then why not ?
Assuming my HW is really broken , why is this message displayed 4 times when it should be there just once for CPU#0 ?
Thx,
Gabriel C
prev parent reply other threads:[~2008-05-03 19:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-23 12:14 BIOS bug, APIC version is 0 for CPU#0! Gabriel C
2008-04-23 18:06 ` Justin Mattock
2008-04-23 20:54 ` Gabriel C
2008-04-23 22:34 ` Justin Mattock
2008-04-24 18:27 ` Gabriel C
2008-05-03 19:10 ` Gabriel C [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=481CB8B2.7030404@googlemail.com \
--to=nix.or.die@googlemail.com \
--cc=akpm@linux-foundation.org \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.