Re: [Xen-devel] Crash on efi_reset_machine on Lenovo ThinkCentre m93 (Haswell)

[Andrew Cooper <andrew.cooper3@xxxxxxxxxx>]

On 05/01/15 15:04, Konrad Rzeszutek Wilk wrote:
> The BIOS on the machine is:
>
> DMI: LENOVO 10A6S09R01/SHARKBAY, BIOS FBKTA4AUS 12/11/2014
>
> (just flashed it today - earlier versions had the same issue)
>
> And with both Xen 4.4 and Xen 4.5 when rebooting from EFI
> I get:
>
>
> [   35.278564] reboot: Restarting system
> (XEN) Domain 0 shutdown: rebooting machine.
> (XEN) ----[ Xen-4.4.1  x86_64  debug=n  Not tainted ]----
> (XEN) CPU:    0
> (XEN) RIP:    e008:[<00000000d5fd8412>] 00000000d5fd8412
> (XEN) RFLAGS: 0000000000010202   CONTEXT: hypervisor
> (XEN) rax: 0000000000000046   rbx: 0000000000000000   rcx: 0000000000000000
> (XEN) rdx: 00000000d5fd89b0   rsi: 0000000000000000   rdi: 0000000000000000
> (XEN) rbp: 0000000000000000   rsp: ffff82d0802dfac8   r8:  ffff82d0802dfb08
> (XEN) r9:  ffff82d0802dfaf8   r10: 0000000000000000   r11: 00000022ebb099f2
> (XEN) r12: 0000000000000000   r13: 0000000000000061   r14: 0000000000000000
> (XEN) r15: ffff82d0802dfd7c   cr0: 0000000080050033   cr4: 00000000001526f0
> (XEN) cr3: 00000004134cf000   cr2: ffff8800092472b0
> (XEN) ds: 0000   es: 0000   fs: 0000   gs: 0000   ss: 0000   cs: e008
> (XEN) Xen stack trace from rsp=ffff82d0802dfac8:
> (XEN)    0000000000010000 0000001000000000 ffff82d080178660 0000000000000000
> (XEN)    ffff82d0802dfb00 000000000004f0f8 ffff82d0802dfd7c 0000000000000000
> (XEN)    0000000000000046 0000000000000000 0000000000000000 00000000d5fe32f6
> (XEN)    0000000000000000 0000000000000000 00000000c1e87000 00000000fffffffe
> (XEN)    ffff82d0802d8000 ffff82d080233a1d 0000000000000000 00000000c1e87000
> (XEN)    00000000001526f0 ffff82d0802339fd 0000000000000061 0000000000000000
> (XEN)    00000000fffffffe ffff82d0801958dd ffff82d0802d8000 00000000ffffffff
> (XEN)    ffff82d0802f7800 0000000000000000 ffff82d0802dfdc8 ffff82d0802f7800
> (XEN)    0000000000000000 ffff82d080195a1b 0000000000000067 ffff82d080128f94
> (XEN)    0000000000000008 ffff82d0802dfc78 ffff82d080289780 ffff82d08017f329
> (XEN)    000000fc083c3a60 ffff82d0802dfdc8 0000000000000000 000000fb80000000
> (XEN)    0000000000000008 0000000000000046 0000000000000008 ffff82d080301040
> (XEN)    ffff82d080289780 ffff82d0802dfdc8 ffff82d0802f7800 0000000000000000
> (XEN)    ffff82d0802dfd7c ffff82d0801772f7 ffff82d0802dfd7c 0000000000000000
> (XEN)    ffff82d0802f7800 ffff82d0802dfdc8 ffff82d080289780 ffff82d080301040
> (XEN)    00000022ebb099f2 ffff82d080322ab0 0000000000000002 000000082b337202
> (XEN)    00000000000000c1 0000000000000002 00000000000003fa 0000000000000002
> (XEN)    ffff82d080301040 000000fb00000000 ffff82d08013fa0f 000000000000e008
> (XEN)    0000000000000206 ffff82d0802dfd20 0000000000000000 ffff82d08013fba1
> (XEN)    0000000000000004 ffff82d08012b96e ffff82d0802dfdc8 ffff82d080301080
> (XEN) Xen call trace:
> (XEN)    [<00000000d5fd8412>] 00000000d5fd8412
> (XEN)    [<ffff82d080178660>] io_apic_write+0/0x70
> (XEN)    [<ffff82d080233a1d>] efi_reset_system+0x2d/0x60
> (XEN)    [<ffff82d0802339fd>] efi_reset_system+0xd/0x60
> (XEN)    [<ffff82d0801958dd>] machine_restart+0xbd/0x1f0
> (XEN)    [<ffff82d080195a1b>] __machine_restart+0xb/0x10
> (XEN)    [<ffff82d080128f94>] smp_call_function_interrupt+0x64/0xa0
> (XEN)    [<ffff82d08017f329>] do_IRQ+0x279/0x6b0
> (XEN)    [<ffff82d0801772f7>] common_interrupt+0x57/0x60
> (XEN)    [<ffff82d08013fa0f>] ns_read_reg+0x4f/0x50
> (XEN)    [<ffff82d08013fba1>] ns16550_interrupt+0x31/0x80
> (XEN)    [<ffff82d08012b96e>] add_entry+0x4e/0xb0
> (XEN)    [<ffff82d08017f3e7>] do_IRQ+0x337/0x6b0
> (XEN)    [<ffff82d0801772f7>] common_interrupt+0x57/0x60
> (XEN)    [<ffff82d0801ba7f2>] mwait_idle+0x222/0x370
> (XEN)    [<ffff82d08016fe76>] idle_loop+0x26/0x60
> (XEN) 
> (XEN) 
> (XEN) ****************************************
> (XEN) Panic on CPU 0:
> (XEN) GENERAL PROTECTION FAULT
> (XEN) [error_code=0000]
> (XEN) ****************************************
> (XEN) 
> (XEN) ...
>
> or (Xen 4.5):
>
> (XEN) Domain 0 shutdown: rebooting machine.
> (XEN) ----[ Xen-4.5.0-rc-lK  x86_64  debug=y  Tainted:    C ]----
> (XEN) CPU:    0
> (XEN) RIP:    e008:[<00000000d5fd83d0>] 00000000d5fd83d0
> (XEN) RFLAGS: 0000000000010246   CONTEXT: hypervisor
> (XEN) rax: 00000000c2e1a990   rbx: 0000000000000000   rcx: 0000000000000002
> (XEN) rdx: 00000000d5fd89b0   rsi: 0000000000000000   rdi: 0000000000000000
> (XEN) rbp: 0000000000000000   rsp: ffff82d080457aa8   r8:  0000000000000000
> (XEN) r9:  ffff82d080457ad8   r10: ffff82d0802a1270   r11: 0000002580dbb411
> (XEN) r12: 0000000000000000   r13: 00000000000000fb   r14: 0000000000000061
> (XEN) r15: 0000000000000000   cr0: 0000000080050033   cr4: 00000000001526f0
> (XEN) cr3: 0000000413479000   cr2: ffff8803e800e4f0
> (XEN) ds: 002b   es: 002b   fs: 0000   gs: 0000   ss: e010   cs: e008
> (XEN) Xen stack trace from rsp=ffff82d080457aa8:
> (XEN)    ffff82d080457ab8 ffff82d08017c007 ffff82d080457ae8 ffff82d08017d1ef
> (XEN)    ffff82d080457ae0 0000000000000092 0000000000000000 0000000000000286
> (XEN)    ffff82d080457b18 0000000000000206 0000000000000000 00000000d5fe32f6
> (XEN)    0000000000000000 0000000000000000 ffff82d080457b48 ffff82d08024582c
> (XEN)    0000000000000000 ffff82d080245ad4 00000000c1eb4000 ffff82d080457b68
> (XEN)    0000000000152670 ffff82d080245aa4 0000000000000000 ffff82d080457c78
> (XEN)    ffff82d080457bb8 ffff82d080198dc5 ffff82d080457bc0 0000000080457b90
> (XEN)    000082d080198f38 0000000000000000 0000000000000000 ffff82d080457c78
> (XEN)    00000000000000fb ffff82d080457dd8 ffff82d080457bc8 ffff82d080198f06
> (XEN)    ffff82d080457be8 ffff82d08012ce38 0000000000000000 ffff82d080457dd8
> (XEN)    ffff82d080457bf8 ffff82d080199577 ffff82d080457c68 ffff82d080182902
> (XEN)    ffff8304134e5d80 ffff82d080457cc0 ffff82d080457dd8 8000000000000000
> (XEN)    ffff82d080457c88 ffff83040fd84510 ffff8304134e62b0 ffff82d080479cc0
> (XEN)    ffff82d080457dd8 ffff82d0802b6800 ffff82d080457dd8 0000000000000000
> (XEN)    00007d2f7fba8367 ffff82d080242202 0000000000000000 ffff82d080457dd8
> (XEN)    ffff82d0802b6800 ffff82d080457dd8 ffff82d080457d28 ffff82d080479cc0
> (XEN)    0000002580dbb411 000000135e46f104 ffff82d080497c60 0000000000000002
> (XEN)    00000000000000c1 0000000000000002 00000000000003fa 0000000000000002
> (XEN)    ffff82d080479cc0 000000fb00000000 ffff82d080144a92 000000000000e008
> (XEN)    0000000000000206 ffff82d080457d28 000000000000e010 ffff82d080457d38
> (XEN) Xen call trace:
> (XEN)    [<00000000d5fd83d0>] 00000000d5fd83d0
> (XEN) 
> (XEN) 
> (XEN) ****************************************
> (XEN) Panic on CPU 0:
> (XEN) GENERAL PROTECTION FAULT
> (XEN) [error_code=0000]
> (XEN) ****************************************
> (XEN) 
> (XEN) Reboot in five seconds...
>
> I tried the same Xen binary not using EFI (so legacy boot using Xen 4.4) -and 
> it
> rebooted fine.
>
> I hadn't dug deep enough in this to figure out how it works on Linux but
> was wondering if anybody else had seen this?

Hmm - backtraces in debug mode need to be capable of dealing with a lack
of frame pointers in the system firmware.  Another item to put on my
backtracing todo list.

However, you probably need to disassemble your firmware to work out
exactly what is blowing up, or see whether Linux has any quirks for this
system.

It might be sensible to fall back to non-efi reset methods if the efi
firmware is uncooperative.

~Andrew


_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel