[Xen-devel] Xen crash after S3 suspend - Xen 4.13

[Marek Marczykowski-Górecki <marmarek@xxxxxxxxxxxxxxxxxxxxxx>]

Hi,

In my test setup (inside KVM with nested virt enabled), I rather
frequently get Xen crash on resume from S3. Full message below.

This is Xen 4.13.0, with some patches, including "sched: fix resuming
from S3 with smt=0".

Contrary to the previous issue, this one does not happen always - I
would say in about 40% cases on this setup, but very rarely on physical
setup.

This is _without_ core scheduling enabled, and also with smt=off.

Do you think it would be any different on xen-unstable? I cat try, but
it isn't trivial in this setup, so I'd ask first.


(XEN) Xen BUG at sched_credit2.c:3474
(XEN) ----[ Xen-4.13.0  x86_64  debug=n   Not tainted ]----
(XEN) CPU:    1
(XEN) RIP:    e008:[<ffff82d08022a60a>] 
sched_credit2.c#csched2_schedule+0xafa/0x1350
(XEN) RFLAGS: 0000000000010097   CONTEXT: hypervisor (d5v0)
(XEN) rax: ffff8300a9845000   rbx: 0000000000000001   rcx: ffff8301ba8fb0e0
(XEN) rdx: 000000000000001b   rsi: ffff8300821dcdd0   rdi: ffff82d0803fa720
(XEN) rbp: ffff82d08053aee0   rsp: ffff8301ba907d68   r8:  0000000000000000
(XEN) r9:  ffff8300a98452b8   r10: 0000000000000000   r11: 0000000000000000
(XEN) r12: ffff8301ba8fb238   r13: ffff8300821dcec0   r14: ffff8301ba8fbf70
(XEN) r15: 0000000000000001   cr0: 0000000080050033   cr4: 00000000000026e0
(XEN) cr3: 000000008e85e000   cr2: 00007a169cd25a10
(XEN) fsb: 0000000000000000   gsb: 0000000000000000   gss: 0000000000000000
(XEN) ds: 0000   es: 0000   fs: 0000   gs: 0000   ss: 0000   cs: e008
(XEN) Xen code around <ffff82d08022a60a> 
(sched_credit2.c#csched2_schedule+0xafa/0x1350):
(XEN)  65 10 0f 84 b6 f5 ff ff <0f> 0b 0f 1f 40 00 4c 89 ef e8 b8 bb ff ff e9 ee
(XEN) Xen stack trace from rsp=ffff8301ba907d68:
(XEN)    ffff82d0803fa720 00000051e8e6c8a5 0000000000000001 ffff8300821dcdd0
(XEN)    ffff82d000000000 0000000000000282 0000000000000001 ba90000100000010
(XEN)    00000051e8e7146c ffff83008ec38090 ffff8301ba907fff ffff8300a9845000
(XEN)    0000000000000000 0000000000000000 ffff8300821dcdd0 ffff8301ba919010
(XEN)    0000000000000000 ffff82d0803fa720 ffff8301ba8fbf70 00000051e8e6c8a5
(XEN)    ffff82d08022f469 ffff82d080229b10 ffff8300821dcdd0 0000000000000001
(XEN)    ffff8300821dcdd0 ffff82d08053aee0 0000000000000001 ffff8301ba919010
(XEN)    ffff83008ec38000 ffff82d080233815 ffff8301ba8fb238 ffff82d08051ff88
(XEN)    00000001ba907ef8 ffff8301ba8fb238 ffff83008ec38000 0000000000000000
(XEN)    ffff82d0802eed2f ffff82d08030e494 ffffffffffffffff ffff82d080524880
(XEN)    ffff82d08052c880 0000000000000001 0000000000000000 0000000000000000
(XEN)    ffff82d080234b51 ffff83008ec38000 0000000000000000 0000000000000000
(XEN)    0000000000000000 ffff82d08031233b ffffffff82614780 0000000000000000
(XEN)    0000000000000000 ffffffff82614780 0000000000000000 0000000000000000
(XEN)    000000000002e2b8 0000000000000000 00000000001b2ff4 0000000000000001
(XEN)    ffffffff81a18a10 0000000000000000 0000000000000000 ffffffff82603e58
(XEN)    0000003d0d5893ff 000000fa00000000 ffffffff81a18dee 0000000000000000
(XEN)    0000000000000246 ffffffff82603e90 0000000000000000 0000000000000000
(XEN)    0000000000000000 0000000000000000 0000000000000000 0000e01000000001
(XEN)    ffff83008ec38000 000000313a3ea000 00000000000026e0 0000000000000000
(XEN) Xen call trace:
(XEN)    [<ffff82d08022a60a>] R sched_credit2.c#csched2_schedule+0xafa/0x1350
(XEN)    [<ffff82d08022f469>] S schedule.c#do_schedule+0xb9/0x520
(XEN)    [<ffff82d080229b10>] S sched_credit2.c#csched2_schedule+0/0x1350
(XEN)    [<ffff82d080233815>] S schedule.c#schedule+0x1b5/0x230
(XEN)    [<ffff82d0802eed2f>] S hvm_vcpu_has_pending_irq+0x6f/0x90
(XEN)    [<ffff82d08030e494>] S nvmx_switch_guest+0x94/0x1a40
(XEN)    [<ffff82d080234b51>] S softirq.c#__do_softirq+0x51/0x80
(XEN)    [<ffff82d08031233b>] S vmx_asm_do_vmentry+0x2b/0x30
(XEN) 
(XEN) 
(XEN) ****************************************
(XEN) Panic on CPU 1:
(XEN) Xen BUG at sched_credit2.c:3474
(XEN) ****************************************
(XEN) 
(XEN) Reboot in five seconds...

Full serial log:
https://openqa.qubes-os.org/tests/6994/file/serial0.txt

-- 
Best Regards,
Marek Marczykowski-Górecki
Invisible Things Lab
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?

Attachment: signature.asc
Description: PGP signature

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxxx
https://lists.xenproject.org/mailman/listinfo/xen-devel