abrt version: 1.1.14 architecture: x86_64 cmdline: not_applicable comment: VirtualBox version is v3.2.12 r68302 component: kernel executable: kernel kernel: 2.6.35.9-64.fc14.x86_64 package: kernel reason: WARNING: at arch/x86/kernel/apic/apic.c:1238 setup_local_APIC+0x148/0x218() release: Fedora release 14 (Laughlin) tainted: 5/var/spool/abrt/kerneloops-1291880511-1724-1 time: 1293705393 uid: 0 backtrace ----- WARNING: at arch/x86/kernel/apic/apic.c:1238 setup_local_APIC+0x148/0x218() Hardware name: VirtualBox Modules linked in: Pid: 1, comm: swapper Not tainted 2.6.35.9-64.fc14.x86_64 #1 Call Trace: [<ffffffff8104d855>] warn_slowpath_common+0x85/0x9d [<ffffffff8104d887>] warn_slowpath_null+0x1a/0x1c [<ffffffff81462fc0>] setup_local_APIC+0x148/0x218 [<ffffffff81021fde>] ? apic_read+0x16/0x18 [<ffffffff81badb36>] native_smp_prepare_cpus+0x2a3/0x353 [<ffffffff81ba1cfe>] kernel_init+0xaa/0x2c0 [<ffffffff8100aae4>] kernel_thread_helper+0x4/0x10 [<ffffffff81ba1c54>] ? kernel_init+0x0/0x2c0 [<ffffffff8100aae0>] ? kernel_thread_helper+0x0/0x10 How to reproduce ----- 1. Powered up VM under VirtualBox (Win7-x64) 2. Logged in 3. That's it - ABRT reported an "oops"
Created attachment 471168 [details] File: backtrace
Package: kernel Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. Started F14x64 virtual machine after upgrading to VirtualBox v4.0.0 r69151 (Windows x64 host) 2. Logged in via GUI 3. Instant "oops" notification
The new comment (https://bugzilla.redhat.com/show_bug.cgi?id=666358#c2) above was generated by ABRT after the kernel had been upgraded to v2.6.35.10-74.fc14.x86_64.
New back-trace from the upgraded kernel: architecture: x86_64 cmdline: not_applicable component: kernel executable: kernel kernel: 2.6.35.10-74.fc14.x86_64 package: kernel reason: WARNING: at arch/x86/kernel/apic/apic.c:1238 setup_local_APIC+0x148/0x218() release: Fedora release 14 (Laughlin) tainted: 5/var/spool/abrt/kerneloops-1293738929-1754-1 time: 1293743692 uid: 0 backtrace ----- WARNING: at arch/x86/kernel/apic/apic.c:1238 setup_local_APIC+0x148/0x218() Hardware name: VirtualBox Modules linked in: Pid: 1, comm: swapper Not tainted 2.6.35.10-74.fc14.x86_64 #1 Call Trace: [<ffffffff8104d999>] warn_slowpath_common+0x85/0x9d [<ffffffff8104d9cb>] warn_slowpath_null+0x1a/0x1c [<ffffffff814632e0>] setup_local_APIC+0x148/0x218 [<ffffffff81021fde>] ? apic_read+0x16/0x18 [<ffffffff81badb36>] native_smp_prepare_cpus+0x2a3/0x353 [<ffffffff81ba1cfe>] kernel_init+0xaa/0x2c0 [<ffffffff8100aae4>] kernel_thread_helper+0x4/0x10 [<ffffffff81ba1c54>] ? kernel_init+0x0/0x2c0 [<ffffffff8100aae0>] ? kernel_thread_helper+0x0/0x10
Package: kernel Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. Started F14x64 virtual machine running under VirtualBox v4.0.0 r69151 (Windows 7 x64 host) 2. Logged in via GUI 3. Instant "oops" notification
Package: kernel Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. Booted Fedora 14 with kernel 2.6.35.11-83.fc14.x86_64 under Oracle Virtualbox 2. 3. Comment ----- Oracle Virtualbox version 4.0.0 r69151 is running under Windoze 7 x64
New data from abrt, including copy of new back-trace. architecture: x86_64 cmdline: not_applicable comment: Oracle Virtualbox version 4.0.0 r69151 is running under Windoze 7 x64 component: kernel executable: kernel kernel: 2.6.35.11-83.fc14.x86_64 package: kernel reason: WARNING: at arch/x86/kernel/apic/apic.c:1238 setup_local_APIC+0x148/0x218() release: Fedora release 14 (Laughlin) tainted: 5/var/spool/abrt/kerneloops-1297937234-1724-1 time: 1297939385 uid: 0 backtrace ----- WARNING: at arch/x86/kernel/apic/apic.c:1238 setup_local_APIC+0x148/0x218() Hardware name: VirtualBox Modules linked in: Pid: 1, comm: swapper Not tainted 2.6.35.11-83.fc14.x86_64 #1 Call Trace: [<ffffffff8104d9ad>] warn_slowpath_common+0x85/0x9d [<ffffffff8104d9df>] warn_slowpath_null+0x1a/0x1c [<ffffffff81463632>] setup_local_APIC+0x148/0x218 [<ffffffff81022092>] ? apic_read+0x16/0x18 [<ffffffff81badb36>] native_smp_prepare_cpus+0x2a3/0x353 [<ffffffff81ba1cfe>] kernel_init+0xaa/0x2c0 [<ffffffff8100aae4>] kernel_thread_helper+0x4/0x10 [<ffffffff81ba1c54>] ? kernel_init+0x0/0x2c0 [<ffffffff8100aae0>] ? kernel_thread_helper+0x0/0x10
Package: kernel Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. Booted Fedora 14 with kernel 2.6.35.11-83.fc14.x86_64 under Oracle Virtualbox (Win7 x86_64 host) 2. 3. Comment ----- Oracle Virtualbox version 4.0.4 r70112 is running under Windoze 7 x64
Package: kernel Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. First boot after upgrade of VirtualBox LinuxAdditions to v4.0.6 2. 3. Comment ----- The v4.0.6 VirtualBox Linux Additions install process removes the old kernel modules (both DKMS and non-DKMS) before building the new version of the additions against the active kernel. A reboot after the upgrade took some time whilst DKMS performed its own check and build.
architecture: x86_64 cmdline: not_applicable component: kernel executable: kernel kernel: 2.6.35.12-90.fc14.x86_64 package: kernel reason: WARNING: at arch/x86/kernel/apic/apic.c:1238 setup_local_APIC+0x148/0x218() release: Fedora release 14 (Laughlin) time: 1304162691 uid: 0 backtrace ----- WARNING: at arch/x86/kernel/apic/apic.c:1238 setup_local_APIC+0x148/0x218() Hardware name: VirtualBox Modules linked in: Pid: 1, comm: swapper Not tainted 2.6.35.12-90.fc14.x86_64 #1 Call Trace: [<ffffffff8104dce1>] warn_slowpath_common+0x85/0x9d [<ffffffff8104dd13>] warn_slowpath_null+0x1a/0x1c [<ffffffff8146420b>] setup_local_APIC+0x148/0x218 [<ffffffff810220b2>] ? apic_read+0x16/0x18 [<ffffffff81badba0>] native_smp_prepare_cpus+0x2a3/0x353 [<ffffffff81ba1cfe>] kernel_init+0xaa/0x2c0 [<ffffffff8100aae4>] kernel_thread_helper+0x4/0x10 [<ffffffff81ba1c54>] ? kernel_init+0x0/0x2c0 [<ffffffff8100aae0>] ? kernel_thread_helper+0x0/0x10
Since all the comments in this report are for the 64-bit version, I'll just say that I see the same behavior with 32-bit Fedora 14. The line number in apic.c is the same. Fedora continues to run after the message; there is no obvious breakage. Virtual Box is version 4.0.8 r71778 running on Windows 2003 server. In the VM, uname -a reports 2.6.35.13-91.fc14.i686 #1 SMP.
If you can duplicate this on Fedora 14 without the vbox modules loaded, please reopen. Otherwise you'll need to work with the vbox developers.
I don't seem to be getting this error anymore. VirtualBox is now version 4.0.10 r72479 (and it's been nagging me that a newer version is available). Fedora is now version 2.6.35.14-95.fc13.i686. I'm not sure when the error stopped.