Your message dated Fri, 24 Apr 2020 14:30:52 +0200
with message-id <20200424123052.GA28843@Red>
and subject line close bug
has caused the Debian Bug report #955426,
regarding qemu-system-x86_64 randomly kernel panic
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
955426: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=955426
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: qemu-system-x86
Version: 1:3.1+dfsg-8+deb10u4
On our kernelci lab, each qemu worker pass an healtcheck job each day and after
each job failure, so it is heavily used.
The healtcheck job is a Linux boot with a stable release.
Since we upgraded our worker to buster, the qemu x86_64 healthcheck randomly
panic with:
<6>[ 0.001000] APIC: Switch to symmetric I/O mode setup
<6>[ 0.001000] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
<3>[ 0.005000] ..MP-BIOS bug: 8254 timer not connected to IO-APIC
<6>[ 0.005000] ...trying to set up timer (IRQ0) through the 8259A ...
<6>[ 0.005000] ..... (found apic 0 pin 2) ...
<6>[ 0.009000] ....... failed.
<6>[ 0.009000] ...trying to set up timer as Virtual Wire IRQ...
<6>[ 0.009000] ..... failed.
<6>[ 0.009000] ...trying to set up timer as ExtINT IRQ...
<6>[ 0.009000] ..... failed :(.
<0>[ 0.009000] 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.
<4>[ 0.009000] CPU: 0 PID: 0 Comm: swapper/0 Not tainted 5.4.23 #1
<4>[ 0.009000] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS
1.12.0-1 04/01/2014
<4>[ 0.009000] Call Trace:
<4>[ 0.009000] dump_stack+0x50/0x70
<4>[ 0.009000] panic+0xf6/0x2b7
<4>[ 0.009000] setup_IO_APIC+0x7c3/0x81c
<4>[ 0.009000] ? clear_IO_APIC_pin+0xb3/0x100
<4>[ 0.009000] x86_late_time_init+0x1b/0x20
<4>[ 0.009000] start_kernel+0x429/0x4e2
<4>[ 0.009000] secondary_startup_64+0xa4/0xb0
The qemu is called with:
/usr/bin/qemu-system-x86_64 -cpu host -enable-kvm -nographic -net
nic,model=virtio,macaddr=52:54:00:12:34:58 -net user -m 512 -monitor none
-kernel
/var/lib/lava/dispatcher/tmp/741722/deployimages-xl6ogak_/kernel/bzImage
-append "console=ttyS0,115200 root=/dev/ram0 debug verbose
console_msg_format=syslog" -initrd
/var/lib/lava/dispatcher/tmp/741722/deployimages-xl6ogak_/ramdisk/rootfs.cpio.gz
-drive
format=qcow2,file=/var/lib/lava/dispatcher/tmp/741722/apply-overlay-guest-sfn3zqna/lava-guest.qcow2,media=disk,if=ide,id=lavatest
We have tried to upgrade the Linux version from 5.0.21 to 5.4.23 without any
change.
Only our buster worker fail like this.
No problem with stretch, and no problem on my gentoo worker (qemu 4.2.0).
Since more recent qemu work perfectly, I suspect a bug in the buster release.
--- End Message ---
--- Begin Message ---
This is know problem, when the host is too slow to emulate, the selftest fail.
Our solution was to add the "no_timer_check" kernel command line for our
healtcheck jobs.
This solution came from https://lkml.org/lkml/2020/4/2/269
--- End Message ---
