Bug 429562 – sys-kernel/gentoo-sources-3.4.7: slowpath oops when booting in qemu

• Product: Gentoo Linux
• Status: RESOLVED TEST-REQUEST

[Description Anthony Basile 2012-08-02 19:06:29 UTC]

[e-mail] hit this while testing a different issue on a hardened-kernel, bug #428576. He found, however, that this is not hardened related, but there in gentoo-sources-3.4.7.  See comments 23 and 24 in that bug.

The problem is that every once in about five, he hits the following oops when booting in qemu.  Its related to apic, and given that this is an emulated environment, its not surprising.  The configuration leading to this is in comment 1 of the above bug.

Freeing SMP alternatives: 8k freed
Enabling APIC mode:  Flat.  Using 1 I/O APICs
------------[ cut here ]------------
WARNING: at arch/x86/kernel/apic/apic.c:1334 setup_local_APIC+0x2d2/0x3c7()
Pid: 1, comm: swapper/0 Not tainted 3.4.7-hardened #3
Call Trace:
 [<c041db95>] ? warn_slowpath_common+0x65/0x90
 [<c053ae40>] ? setup_local_APIC+0x2d2/0x3c7
 [<c053ae40>] ? setup_local_APIC+0x2d2/0x3c7
 [<c041dc79>] ? warn_slowpath_null+0x19/0x20
 [<c053ae40>] ? setup_local_APIC+0x2d2/0x3c7
 [<c052b762>] ? native_smp_prepare_cpus+0x2c2/0x373
 [<c04d4b26>] ? ret_from_fork+0x6/0x20
 [<c0525714>] ? do_one_initcall+0x125/0x125
 [<c052575c>] ? kernel_init+0x48/0x180
 [<c0525714>] ? do_one_initcall+0x125/0x125
 [<c04d5156>] ? kernel_thread_helper+0x6/0xd
---[ end trace 4eaa2a86a8e2da22 ]---
..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
CPU0: Intel QEMU Virtual CPU version 1.0,1 stepping 03

[Comment 1 PaX Team 2012-08-02 19:26:59 UTC]

it's not an oops but this:

WARN_ON(max_loops <= 0);

[Comment 2 Maxim Kammerer 2012-08-02 19:41:16 UTC]

Another one (this time a kernel panic). Got it by running:

qemu-system-x86_64 -cpu kvm64 -nodefaults -sdl -monitor vc -m 64M -vga cirrus -kernel .../usr/src/linux-3.4.7-gentoo/arch/x86/boot/bzImage -serial stdio -append "earlyprintk=serial,keep debug"

Freeing SMP alternatives: 8k freed
Enabling APIC mode:  Flat.  Using 1 I/O APICs
..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
..MP-BIOS bug: 8254 timer not connected to IO-APIC
...trying to set up timer (IRQ0) through the 8259A ...
..... (found apic 0 pin 2) ...
....... failed.
...trying to set up timer as Virtual Wire IRQ...
..... failed.
...trying to set up timer as ExtINT IRQ...
..... failed :(.
Kernel panic - not syncing: IO-APIC + timer doesn't work!  Boot with apic=debug and send a report.  Then try booting with the 'noapic' option.

Pid: 1, comm: swapper/0 Not tainted 3.4.7-gentoo #3
Call Trace:
 [<c04c8bac>] ? panic+0x81/0x165
 [<c050dd59>] ? setup_IO_APIC+0x64a/0x680
 [<c050a64f>] ? native_smp_prepare_cpus+0x304/0x374
 [<c04cb286>] ? ret_from_fork+0x6/0x1c
 [<c050471f>] ? do_one_initcall+0x12f/0x12f
 [<c0504767>] ? kernel_init+0x48/0x17b
 [<c050471f>] ? do_one_initcall+0x12f/0x12f
 [<c04cb836>] ? kernel_thread_helper+0x6/0xd

By the way, it's not immediately clear from this bug: the kernel is x86.

[Comment 3 Maxim Kammerer 2012-08-02 19:57:17 UTC]

Seems relevant: https://bugzilla.redhat.com/show_bug.cgi?id=502058

[Comment 4 Mike Pagano 2012-09-09 18:57:43 UTC]

Are CONFIG_KVM_GUEST and CONFIG_KVM_CLOCK enabled?

[Comment 5 Maxim Kammerer 2012-09-10 09:35:43 UTC]

(In reply to comment #4)
> Are CONFIG_KVM_GUEST and CONFIG_KVM_CLOCK enabled?

No, see https://428576.bugs.gentoo.org/attachment.cgi?id=319658.

[Comment 6 Mike Pagano 2012-09-10 13:17:03 UTC]

Please enable and retest

[Comment 7 Maxim Kammerer 2012-10-12 18:32:38 UTC]

I am unable to reproduce the original problem with gentoo-sources-3.4.8 and 3.4.11. Perhaps it was fixed in mainline kernel or Gentoo patchset, or perhaps the last gcc update masked the problem. Feel free to close.