On Thu, Jul 05, 2012 at 11:00:05PM +0100, M A Young wrote: > On Tue, 3 Jul 2012, Konrad Rzeszutek Wilk wrote: > > >Besides that..there is: > > > >9846ff1 xen: support pirq_eoi_map > >(and its fix) 521394e xen: use the pirq number to check the pirq_eoi_map > > In my case it is definitely IRQ related. From xl dmesg I get If you revert those two, are those issues still present? > (XEN) physdev.c:164: dom0: wrong map_pirq type 3 This is one is due to another one - a fix that went in 3.3 (allowing PCI domains to work). > (XEN) do_IRQ: 1.240 No irq handler for vector (irq -1) So vector 240...or 0xf0. That I am not sure about. > (XEN) traps.c:2488:d0 Domain attempted WRMSR 0000000000000079 from > 0x00000000000 > 00000 to 0xffffc90005193030. > (XEN) traps.c:2488:d0 Domain attempted WRMSR 0000000000000079 from > 0x00000000000 > 00000 to 0xffffc9000519b030. > (XEN) do_IRQ: 1.240 No irq handler for vector (irq -1) > (XEN) traps.c:2488:d1 Domain attempted WRMSR 0000000000000079 from > 0x00000000000 > 00000 to 0xffffc900001a9030. > (XEN) do_IRQ: 1.40 No irq handler for vector (irq -1) > (XEN) do_IRQ: 1.240 No irq handler for vector (irq -1) > (XEN) do_IRQ: 1.240 No irq handler for vector (irq -1) > > Michael Young -- xen mailing list xen@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/xen
