From: j0rg3@arribatel.com
To: "Kagay-Anon Linux Users' Group (KLUG) Mailing List"
<klug@lists.linux.org.ph>
Cc: linux-kernel@vger.kernel.org
Subject: MP-BIOS bug: 8254 timer not connected to IO-APIC
Date: Tue, 17 Oct 2006 10:09:17 +0800 [thread overview]
Message-ID: <20061017100917.3od7d35ug4wgg0s4@mail.arribatel.com> (raw)
Is there any patch or workarounds about this bug on 2.6.x kernel? I
already googled this, there are patches on 2.4.x kernel but i dont like
downgrading the kernel. Or if someone already did a kernel
tweaking/hacking about these issues it would help.
NOTE: I don't think that there are bugs/problems on the BIOS because
this box has been already tested and runs smoothly without any problems
and issues on FreeBSD 6.1
## DMESG SHOWS THE MP-BIOS BUG ##
[root@localhost ~]# dmesg |grep -i APIC
ACPI: Local APIC address 0xfee00000
ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
Processor #0 15:15 APIC version 16
ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] disabled)
ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1])
ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1])
ACPI: IOAPIC (id[0x02] address[0xfec00000] gsi_base[0])
IOAPIC[0]: apic_id 2, version 33, address 0xfec00000, GSI 0-23
Setting APIC routing to flat
..MP-BIOS bug: 8254 timer not connected to IO-APIC <---*HERE'S THE SAID BUG*
Using local APIC timer interrupts.
Detected 12.436 MHz APIC timer.
ACPI: Using IOAPIC for interrupt routing
APIC error on CPU0: 04(40)
APIC error on CPU0: 40(40)
APIC error on CPU0: 40(40)
## THIS MACHINE HAS 1 SINGLE CORE AMD64 PROCESSOR #
[root@localhost ~]# dmesg |grep -i CPU
Initializing CPU#0
CPU 0: aperture @ 278000000 size 32 MB
CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line)
CPU: L2 Cache: 512K (64 bytes/line)
CPU: AMD Athlon(tm) 64 Processor 3200+ stepping 02
ACPI: Processor [CPU0] (supports 8 throttling states)
ACPI: Getting cpuindex for acpiid 0x1
APIC error on CPU0: 04(40)
APIC error on CPU0: 40(40)
APIC error on CPU0: 40(40)
##KERNEL VERSION AFTER I RECOMPILE IT BY HAND (without smp support and
also tried w/o ACPI) but IT DID'NT HELP
[root@localhost ~]# uname -a
Linux localhost.org 2.6.18.1 #1 Sun Oct 15 23:19:17 EDT 2006 x86_64
x86_64 x86_64 GNU/Linux
Best Regards,
Jorge T. Monzor III
Telecom Analyst
Arriba Telecontact Inc.
Rosario Arcade, Limketkai Center
Cagayan de Oro City,Philippines 9000
USDID# 1-305-508-5328 ext. 4
Toll-Free# 1-866-394-0909
URL: http://www.arribatel.com
next reply other threads:[~2006-10-17 2:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-17 2:09 j0rg3 [this message]
2006-10-17 2:17 ` Matthew Garrett
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=20061017100917.3od7d35ug4wgg0s4@mail.arribatel.com \
--to=j0rg3@arribatel.com \
--cc=klug@lists.linux.org.ph \
--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
all inboxes | Powered by JetHome®