Bug 5589 - mageia2b3, timer 82...4 not connected to IO-APIC
Summary: mageia2b3, timer 82...4 not connected to IO-APIC
Status: RESOLVED INVALID
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: x86_64 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-04-24 15:41 CEST by episteme promeneur
Modified: 2012-04-25 12:11 CEST (History)
1 user (show)

See Also:
Source RPM: kernel
CVE:
Status comment:


Attachments

Description episteme promeneur 2012-04-24 15:41:08 CEST
Description of problem:


when starting pc briefly a text message is displayed :

MP bios bug : timer 82..4 timer not connected to IO-APIC

i am not sure about terms

this message happens since kernel 3.3.0 or 3.3.1
Comment 1 Dave Hodgins 2012-04-24 21:23:34 CEST
According to http://ubuntuforums.org/showthread.php?t=909367
that can be solved by adding  "noapic" and possibly "noacpi" to
the kernel options.

CC: (none) => davidwhodgins

Manuel Hiebel 2012-04-25 01:04:51 CEST

Source RPM: (none) => kernel

Comment 2 episteme promeneur 2012-04-25 12:11:45 CEST
i found this in /var/log/dmesg file

...
ftrace: allocating 17335 entries in 68 pages
[    0.092615] ..TIMER: vector=0x30 apic1=0 pin1=0 apic2=-1 pin2=-1
[    0.093991] ..MP-BIOS bug: 8254 timer not connected to IO-APIC
[    0.093991] ...trying to set up timer (IRQ0) through the 8259A ...
[    0.093991] ..... (found apic 0 pin 0) ...
[    0.104676] ....... works.
[    0.104678] CPU0: AMD Athlon(tm) 64 X2 Dual Core Processor 5000+ stepping 02
...

it seems it's not a pb

then
i close the big report

Status: NEW => RESOLVED
Resolution: (none) => INVALID


Note You need to log in before you can comment on or make changes to this bug.