Jan Kiszka wrote: > Charles Duffy wrote: >> Jan Kiszka wrote: >>> Charles Duffy wrote: >>>> irq 25, desc: ffffffff803afc80, depth: 1, count: 0, unhandled: 0 >>>> ->handle_irq(): ffffffff800b54e3, handle_bad_irq+0x0/0x1f6 >>>> ->chip(): ffffffff802ea700, 0xffffffff802ea700 >>>> ->action(): 0000000000000000 >>>> IRQ_DISABLED set >>>> unexpected IRQ trap at vector 19 >>>> ..MP-BIOS bug: 8254 timer not connected to IO-APIC >>>> timer doesn't work through the IO-APIC - disabling NMI Watchdog! >>>> Kernel panic - not syncing: IO-APIC + timer doesn't work! Try using the >>>> 'noapic' kernel parameter >>> Still too early for me, so I didn't get yet if you can trigger this >>> guest panic reliably or only sporadically (like I can). In the former >>> case I would be very interested in the how! >> Reproduced 100% of the time when using system_reset at the qemu monitor >> console coming from a non-panic'd state. (Thus, it happens only every >> other time doing a series of boots and system_reset monitor commands). > > Mmmh, /that/ sounds like some (re-)initialization issue of the > virtualized hardware. OK, once that kernel boots again on latest kvm.git > (currently broken due to a different issue), I will try to reproduce it.
OK, I can reproduce now. It's an in-kernel irqchip, -no-kvm-irqchip doesn't suffer. Will see if I can find the reason. Jan
signature.asc
Description: OpenPGP digital signature