APIC Bug?

[DasFox]

I'm running Slackware 13.37 as a Guest in VB 4.1.4 and I noticed in /var/log/dmesg this:

weird, boot CPU (#0) not listed by the BIOS.
SMP motherboard not detected.
Enabling APIC mode:  Flat.  Using 0 I/O APICs
------------[ cut here ]------------
WARNING: at arch/x86/kernel/apic/apic.c:1299 setup_local_APIC+0x22c/0x2e2()
Hardware name: VirtualBox
Modules linked in:
Pid: 1, comm: swapper Not tainted 3.1.5 #1
Call Trace:
 [<c102fb37>] warn_slowpath_common+0x6a/0x7f
 [<c13119c9>] ? setup_local_APIC+0x22c/0x2e2
 [<c102fb60>] warn_slowpath_null+0x14/0x18
 [<c13119c9>] setup_local_APIC+0x22c/0x2e2
 [<c148fb2c>] APIC_init_uniprocessor+0x94/0xe9
 [<c148db9f>] native_smp_prepare_cpus+0x1d1/0x3b8
 [<c148569b>] ? start_kernel+0x2e3/0x2e3
 [<c14856d7>] kernel_init+0x3c/0xfd
 [<c13163fe>] kernel_thread_helper+0x6/0x10
---[ end trace a7919e7f17c0a725 ]---
APIC calibration not consistent with PM-Timer: 145ms instead of 100ms
APIC delta adjusted to PM-Timer: 6289924 (9125077)

So between also this 'weird, boot CPU' and the APIC warning I wanted to know if this is a bug?

I also don't like using the standard kernel in Linux, to make things that are not supported that you have to weed through all the messages to figure out what is going on, so I compile my own kernel.

These are some of the options I compiled in below. Also are there any other options I need to make sure I have support for in the kernel for VirtualBox, specific to it?

<*> Intel PIIX4 and compatible (ATI/AMD/Serverworks/Broadcom/SMSC)
<*>   EHCI HCD (USB 2.0) support
<*>   USB Mass Storage support 
[*] ISA support 

Processor type and features  --->
    [*] Tickless System (Dynamic Ticks)
    [ ] High Resolution Timer Support
    [X] Symmetric multi-processing support (keep this enabled for multiple cores, too!)
        Subarchitecture Type (PC-compatible)  --->
    [ ] Machine Check / overheating reporting
    [X] SMT (Hyperthreading) scheduler support (This too, for i7's)
Power management and ACPI options  --->
    [*] Power Management support
    [ ] Suspend to RAM and standby
    [ ] Hibernation (aka 'suspend to disk')
    [*] ACPI (Advanced Configuration and Power Interface) Support  --->
Device Drivers  --->
    < > ATA/ATAPI/MFM/RLL support
    <*> Serial ATA and Parallel ATA drivers
        <*> AHCI SATA Support
        [*] ATA SFF support
        <*> Intel ESB, ICH, PIIX3, PIIX4 PATA/SATA support
    [*] Network device support  --->
        [*] Ethernet (10 or 100Mbit)  --->
            [*] EISA, VLB, PCI and on board controllers
                <M>   AMD PCnet32 PCI support
        [*] Ethernet (1000 Mbit)  --->
            <M> Intel(R) PRO/1000 Gigabit Ethernet support
        [ ] Ethernet (10000 Mbit)  --->
    Input device support --->
        [*] Mice --->
           <*> PS/2 mouse
    Graphics support --->
        <*> Direct Rendering Manager (XFree86 4.1.0 and higher DRI support)  --->
            < > all options can be empty
    <M> Sound card support --->
        <M> Advanced Linux Sound Architecture --->
            [*] PCI sound Devices --->
                <M> Intel/SiS/nVidia/AMD/ALi AC97 Controller

THANKS

[DasFox]

Sorry for pasting some of the dmesg output, I've attached a log...

THANKS

[DasFox]

SORRY guys, false alarm, I removed these;

Symmetric multi-processing support SMT (Hyperthreading) scheduler support

Now I'm no longer getting the warning.

I do see other possible issues, so please see attached file; dmesg_2.log

THANKS

[DasFox]

Hi,

Sorry, don't mean to rush anyone, I just need to get a clean image with everything worked out for my business, so for the dmesg_2.log, the errors in it, I'd appreciate if it someone can tell me as soon as possible how I can correct those?

THANKS, I really appreciate it! :)

[DasFox]

Hi,

I was able to recompile the kernel and figure out a few things, these are all that are left that I don't know;

• Fast TSC calibration failed
• TSC: Unable to calibrate against PIT
• TSC: using PMTIMER reference calibration
• Performance Events: Broken PMU hardware detected, using software events only.
• Enabling APIC mode: Flat. Using 0 I/O APICs
• APIC calibration not consistent with PM-Timer: 101ms instead of 100ms
• APIC delta adjusted to PM-Timer: 6296145 (6368174)
• platform rtc_cmos: registered platform RTC device (no PNP device found)
• audit: initializing netlink socket (disabled)
• type=2000 audit(1325101768.517:1): initialized
• input: Unspecified device as /devices/virtual/input/input4

Again, I'd really appreciate some help here, I don't know if these are bugs, or something I can fix...

THANKS

[Jan Vansteenkiste]

console log apic and init_tsc_clocksource errors

[Jan Vansteenkiste]

I'm also getting this error on CentOS 6.2 with virtualbox 4.1.10 (target should probably be updated in the bug) Going to attach a console log with apic=debug enabled asap.

[Jan Vansteenkiste]

console log apic with apic=debug

[Frank Mehnert]

First analysis: According to the debug log, that's a 'division by zero' error. 'div %esi => esi is 0'.

[Jan Vansteenkiste]

VBox log

[Jan Vansteenkiste]

VBox.log (vanilla/binary Virtualbox 4.1.10) (also produced errors)

[Jan Vansteenkiste]

VirtualBox 4.1.14 - console log

[Jan Vansteenkiste]

VirtualBox 4.1.14 - vbox log

[Jan Vansteenkiste]

Still having the same problem on 4.1.14. This is not letting me boot vm's 1/5 times or so.

[Jan Vansteenkiste]

This is still valid for 4.1.16. I'm no longer going to add log files until somebody specifly asks for them. There doesnt seem to be any progress here anyhow...

[Frank Mehnert]

We just observed in #10837 that Gentoo uses its own compiler flags when compiling VirtualBox. In particular it adds -fomit-frame-pointer which makes the code invalid. So please check if the official VirtualBox package from this website (use one of the .run packages) shows the same behavior.

[Frank Mehnert]

No response, closing.