Re: [Xen-devel] KDB in Xen 4.4

[Xin Xu <jungle.xuxin@xxxxxxxxx>]

On Mon, Jun 2, 2014 at 6:39 PM, Aravindh Puthiyaparambil (aravindp) <aravindp@xxxxxxxxx> wrote:

>I applied your patches to xen 4.4.0 source, It can be applied without
>errors, and built OK. I install it in ubuntu 12.04. After I reboot the
>system, it has a fatal error, and system cannot boot. I put the serial
>console log below. Do you have any ideas about what causes this problem?
>any
>suggestions will be appreciated. Thank you.
>
>
>
>[ Â Â0.000000] Booting paravirtualized kernel on Xen
>[ Â Â0.000000] Xen version: 4.4.0 (preserve-AD)
>[ Â Â0.000000] setup_percpu: NR_CPUS:256 nr_cpumask_bits:256 nr_cpu_ids:4
>nr_node_ids:1
>[ Â Â0.000000] PERCPU: Embedded 28 pages/cpu @ffff8800bfe9b000 s83072
>r8192
>d23424 u114688
>[ Â Â0.000000] pcpu-alloc: s83072 r8192 d23424 u114688 alloc=28*4096
>[ Â Â0.000000] pcpu-alloc: [0] 0 [0] 1 [0] 2 [0] 3
>[ Â Â0.000000] Built 1 zonelists in Node order, mobility grouping on. ÂTotal
>pages: 1026323
>[ Â Â0.000000] Policy zone: Normal
>[ Â Â0.000000] Kernel command line: root=UUID=b2902faa-4872-4d3b-ae3a-
>6284cbc63f12 ro earlyprintk=xen loglevel=8 console=hvc0
>[ Â Â0.000000] PID hash table entries: 4096 (order: 3, 32768 bytes)
>[ Â Â0.000000] invalid opcode: 0000 [#1] SMP
>[ Â Â0.000000] CPU 0
>[ Â Â0.000000] Modules linked in:
>[ Â Â0.000000]
>[ Â Â0.000000] Pid: 0, comm: swapper Not tainted 3.2.0-23-generic #36-Ubuntu
>Dell Inc. Vostro 220 Series /0JJW8N
>[ Â Â0.000000] RIP: e030:[<ffffffff8101d81c>] Â[<ffffffff8101d81c>]
>xstate_enable+0x3c/0x50
>[ Â Â0.000000] RSP: e02b:ffffffff81c01e58 ÂEFLAGS: 00010046
>[ Â Â0.000000] RAX: 0000000000000003 RBX: ffffffff81c01e94 RCX:
>0000000000000000
>[ Â Â0.000000] RDX: 0000000000000000 RSI: 0000000000000003 RDI:
>0000000000002660
>[ Â Â0.000000] RBP: ffffffff81c01e58 R08: ffffffff81c01e90 R09:
>ffffffff81c01e94
>[ Â Â0.000000] R10: 00000000ffffffff R11: 00000000ffffffff R12:
>ffffffff81c01e90
>[ Â Â0.000000] R13: ffffffff81c01e8c R14: ffffffff81c01e88 R15:
>ffff8800bfea7480
>[ Â Â0.000000] FS: Â0000000000000000(0000) GS:ffff8800bfe9b000(0000)
>knlGS:0000000000000000
>[ Â Â0.000000] CS: Âe033 DS: 0000 ES: 0000 CR0: 000000008005003b
>[ Â Â0.000000] CR2: 0000000000000000 CR3: 0000000001c05000 CR4:
>0000000000002660
>[ Â Â0.000000] DR0: 0000000000000000 DR1: 0000000000000000 DR2:
>0000000000000000
>[ Â Â0.000000] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7:
>0000000000000400
>[ Â Â0.000000] Process swapper (pid: 0, threadinfo ffffffff81c00000, task
>ffffffff81c0d020)
>[ Â Â0.000000] Stack:
>[ Â Â0.000000] Âffffffff81c01ec8 ffffffff81d0474c ffff8800bfea6150
>ffff8800bfea6950
>[ Â Â0.000000] Âffff8800bfea6150 ffff8800bfea6950 0000024000000003
>0000000000000240
>[ Â Â0.000000] Â0000000000000004 0000000000000008 0000000000000004
>0000000000000000
>[ Â Â0.000000] Call Trace:
>[ Â Â0.000000] Â[<ffffffff81d0474c>] xstate_enable_boot_cpu+0xa9/0x174
>[ Â Â0.000000] Â[<ffffffff81635a17>] xsave_init+0x26/0x28
>[ Â Â0.000000] Â[<ffffffff81637cdd>] cpu_init+0x2bb/0x2d8
>[ Â Â0.000000] Â[<ffffffff81d00f49>] trap_init+0x169/0x171
>[ Â Â0.000000] Â[<ffffffff81cfba28>] start_kernel+0x1d5/0x3c7
>[ Â Â0.000000] Â[<ffffffff81cfb388>] x86_64_start_reservations+0x132/0x136
>[ Â Â0.000000] Â[<ffffffff81cfef06>] xen_start_kernel+0x5bc/0x5c3
>[ Â Â0.000000] Code: 00 04 00 ff 14 25 90 76 c1 81 48 89 c7 48 81 cf 00 00
>04 00 ff 14 25 98 76 c1 81 48 8b 05 dd 0d dc 00 31 c9 48 89 c2 48 c1 ea 20
><0f> 01 d1 5d c3 66 66 66 66 66 66 2e 0f 1f 84 00 00 00 00 00 55
>[ Â Â0.000000] RIP Â[<ffffffff8101d81c>] xstate_enable+0x3c/0x50
>[ Â Â0.000000] ÂRSP <ffffffff81c01e58>
>[ Â Â0.000000] ---[ end trace a7919e7f17c0a725 ]---
>[ Â Â0.000000] Kernel panic - not syncing: Attempted to kill the idle task!
>[ Â Â0.000000] Pid: 0, comm: swapper Tainted: G Â Â ÂD Â Â Â3.2.0-23-generic
>#36-Ubuntu
>[ Â Â0.000000] Call Trace:
>[ Â Â0.000000] Â[<ffffffff81644023>] panic+0x91/0x1a4
>[ Â Â0.000000] Â[<ffffffff8106bcae>] do_exit+0x41e/0x420
>[ Â Â0.000000] Â[<ffffffff8165d620>] oops_end+0xb0/0xf0
>[ Â Â0.000000] Â[<ffffffff810168d8>] die+0x58/0x90
>[ Â Â0.000000] Â[<ffffffff8165cf94>] do_trap+0xc4/0x170
>[ Â Â0.000000] Â[<ffffffff81013f65>] do_invalid_op+0x95/0xb0
>[ Â Â0.000000] Â[<ffffffff8101d81c>] ? xstate_enable+0x3c/0x50
>[ Â Â0.000000] Â[<ffffffff8100aa82>] ? check_events+0x12/0x20
>[ Â Â0.000000] Â[<ffffffff8100b169>] ? get_phys_to_machine+0x9/0x70
>[ Â Â0.000000] Â[<ffffffff81006759>] ? pte_mfn_to_pfn+0x89/0xf0
>[ Â Â0.000000] Â[<ffffffff8100a29d>] ? xen_force_evtchn_callback+0xd/0x10
>[ Â Â0.000000] Â[<ffffffff81666a6b>] invalid_op+0x1b/0x20
>[ Â Â0.000000] Â[<ffffffff8101d81c>] ? xstate_enable+0x3c/0x50
>[ Â Â0.000000] Â[<ffffffff8101d80c>] ? xstate_enable+0x2c/0x50
>[ Â Â0.000000] Â[<ffffffff81d0474c>] xstate_enable_boot_cpu+0xa9/0x174
>[ Â Â0.000000] Â[<ffffffff81635a17>] xsave_init+0x26/0x28
>[ Â Â0.000000] Â[<ffffffff81637cdd>] cpu_init+0x2bb/0x2d8
>[ Â Â0.000000] Â[<ffffffff81d00f49>] trap_init+0x169/0x171
>[ Â Â0.000000] Â[<ffffffff81cfba28>] start_kernel+0x1d5/0x3c7
>[ Â Â0.000000] Â[<ffffffff81cfb388>] x86_64_start_reservations+0x132/0x136
>[ Â Â0.000000] Â[<ffffffff81cfef06>] xen_start_kernel+0x5bc/0x5c3
>*** kdb (Fatal Error on cpu:0 vec:1 Â????? ):
>ffff82d080223a0f: kdb_trap_immed+3f       Âlea 0x6058e(%rip), %rdi
>[0]xkdb>

I don't think this has anything to do with the KDB patch. You might be running in to this issue:
http://lists.xenproject.org/archives/html/xen-devel/2012-05/msg00080.html

Please try running with the xsave=0 kernel command line option or upgrade your kernel.

Thanks,
Aravindh

Hi Aravindh and Mukesh,

Thank you for your replies! You are right! KDB is working fine if I use xsave=0 in kernel command line. It seems to be the Dom0 issue. Thank you very much Â

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