Bug 27642
| Summary: | 2.6.37 says WARNING: at arch/x86/kernel/apic/apic.c:1287 setup_local_APIC+0x18f/0x263() | ||
|---|---|---|---|
| Product: | Platform Specific/Hardware | Reporter: | Maciej Rutecki (maciej.rutecki) |
| Component: | i386 | Assignee: | platform_i386 |
| Status: | RESOLVED OBSOLETE | ||
| Severity: | normal | CC: | alan, cyberrider, florian, maciej.rutecki, rjw, rob |
| Priority: | P1 | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Kernel Version: | 2.6.37 | Subsystem: | |
| Regression: | Yes | Bisected commit-id: | |
| Bug Depends on: | |||
| Bug Blocks: | 21782 | ||
| Attachments: |
VirtualBox vminfo output for Fedora 14 Virtual Machine
XML format Virtual Machine description/configuration The native VirtualBox "vbox" configuration file |
||
|
Description
Maciej Rutecki
2011-01-26 20:20:34 UTC
Is this still happening on 2.6.38.y? Is there any misbehaviour accompanying the warning? I haven't seen it in 2.6.38, I think it's been fixed. Alright, thanks for the update. I'm closing this as unreproducible. Guys, sorry to burst your bubble, but I have the same (or very similar) ABRT oops report for kernel release 2.6.38 when compiled on/under Fedora 14. https://bugzilla.redhat.com/show_bug.cgi?id=701115 kernel: WARNING: at arch/x86/kernel/apic/apic.c:1284 setup_local_APIC+0x15b/0x20b() The source line in apic.c and the function offset are different, but only by 3 lines in the source code. The specific kernel source was downloaded from the Fedora 15 SRPM directory, and compiled on/under a working Fedora 14 x86_64 system. I only seem to get these APIC errors when running in virtual machines, such as those provided by Oracle VirtualBox. The VirtualBox under which this occurred for me is v4.0.6 running in a Windows 7 x86_64 host, fully patched. I hope this helps narrow down the root cause of the abend. Backtrace from abrt: WARNING: at arch/x86/kernel/apic/apic.c:1284 setup_local_APIC+0x15b/0x20b() Hardware name: VirtualBox Modules linked in: Pid: 1, comm: swapper Not tainted 2.6.38.3-18.fc14.x86_64 #1 Call Trace: [<ffffffff81058f5f>] ? warn_slowpath_common+0x85/0x9d [<ffffffff81058f91>] ? warn_slowpath_null+0x1a/0x1c [<ffffffff81482318>] ? setup_local_APIC+0x15b/0x20b [<ffffffff812443d9>] ? __bitmap_weight+0x3e/0x8a [<ffffffff81b6591e>] ? native_smp_prepare_cpus+0x29b/0x34b [<ffffffff81b58ce1>] ? kernel_init+0x92/0x2b6 [<ffffffff8100ba64>] ? kernel_thread_helper+0x4/0x10 [<ffffffff81b58c4f>] ? kernel_init+0x0/0x2b6 [<ffffffff8100ba60>] ? kernel_thread_helper+0x0/0x10 Created attachment 56142 [details]
VirtualBox vminfo output for Fedora 14 Virtual Machine
Output file generated by:
vboxmanage showvminfo "Fedora 14 x64" --machinereadable
This may assist in reproducing or narrowing down cause of the APIC errors.
Created attachment 56152 [details]
XML format Virtual Machine description/configuration
Output from the:
vboxmanage export "Fedora 14 x64" --output Fed14x64.ovf
Once again, the analysis of the XML configuration may assist in determining what VirtualBox is doing when creating the virtual machine environment, and how it affects the kernel APIC code.
(And no, I'm not going to upload the companion vmdk file - it's too bl**dy big - the raw file is ~36GiB in size)
Created attachment 56162 [details]
The native VirtualBox "vbox" configuration file
Once again, the configuration of the Oracle VirtualBox virtual machine environment where the kernel is experiencing APIC errors.
This is the NATIVE Oracle virtualBox configuration format.
Closing as obsolete, if this is still seen on modern kernels please update |