From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Sander Eikelenboom <linux@eikelenboom.it>
Cc: xen-devel@lists.xenproject.org, Jan Beulich <jbeulich@suse.com>
Subject: Re: Xen-unstable: Xen panic when shutting down HVM guest with PCI passthrough: RIP: e008:[<ffff82d0801099b1>] evtchn_move_pirqs+0x90/0xbf
Date: Thu, 5 Jun 2014 16:03:24 +0100 [thread overview]
Message-ID: <539086BC.7070200@citrix.com> (raw)
In-Reply-To: <495141585.20140605165458@eikelenboom.it>
[-- Attachment #1.1: Type: text/plain, Size: 5664 bytes --]
On 05/06/14 15:54, Sander Eikelenboom wrote:
> Hi,
>
> When shutting down a HVM guest with PCI passthrough Xen panics with the panic
> below (complete xl-dmesg attached).
>
> # addr2line -e xen-syms ffff82d0801099b1
> /usr/src/new/xen-unstable/xen/common/event_channel.c:1326
>
> which is:
> pirq_set_affinity(d, chn->u.pirq.irq, mask);
This is presumably an ordering issue on destroy.
Does reverting bac6334b5 fix the problem?
~Andrew
>
> (XEN) [2014-06-05 14:10:54.290] AMD-Vi: Disable: device id = 0x700, domain = 1, paging mode = 4
> (XEN) [2014-06-05 14:10:54.290] AMD-Vi: Setup I/O page table: device id = 0x700, type = 0x1, root table = 0x54ef41000, domain = 0, paging mode = 3
> (XEN) [2014-06-05 14:10:54.290] AMD-Vi: Re-assign 0000:07:00.0 from dom1 to dom0
> (XEN) [2014-06-05 14:10:54.650] ----[ Xen-4.5-unstable x86_64 debug=y Not tainted ]----
> (XEN) [2014-06-05 14:10:54.650] CPU: 5
> (XEN) [2014-06-05 14:10:54.650] RIP: e008:[<ffff82d0801099b1>] evtchn_move_pirqs+0x90/0xbf
> (XEN) [2014-06-05 14:10:54.650] RFLAGS: 0000000000010202 CONTEXT: hypervisor
> (XEN) [2014-06-05 14:10:54.650] rax: 0000000000000019 rbx: 0000000000000320 rcx: 0000000000000001
> (XEN) [2014-06-05 14:10:54.650] rdx: ffff83054ef86020 rsi: 0000000000000200 rdi: ffff8305416eb0bc
> (XEN) [2014-06-05 14:10:54.650] rbp: ffff83054ef7fce8 rsp: ffff83054ef7fcc8 r8: 0000000000000001
> (XEN) [2014-06-05 14:10:54.650] r9: 000000000000003a r10: ffff82e008e31940 r11: 0000000000000001
> (XEN) [2014-06-05 14:10:54.650] r12: ffff8305416eb000 r13: ffff82d08023d740 r14: ffff8305416eb0b8
> (XEN) [2014-06-05 14:10:54.650] r15: ffffffffffffffff cr0: 000000008005003b cr4: 00000000000006f0
> (XEN) [2014-06-05 14:10:54.650] cr3: 0000000537296000 cr2: 0000000000000328
> (XEN) [2014-06-05 14:10:54.650] ds: 0000 es: 0000 fs: 0000 gs: 0000 ss: e010 cs: e008
> (XEN) [2014-06-05 14:10:54.650] Xen stack trace from rsp=ffff83054ef7fcc8:
> (XEN) [2014-06-05 14:10:54.650] ffff83009faf7000 0000000000000000 ffff830546cb6ee0 ffff83054eff8d00
> (XEN) [2014-06-05 14:10:54.650] ffff83054ef7fd68 ffff82d080126e2f ffff83054ef7fd48 ffff830546df8ef0
> (XEN) [2014-06-05 14:10:54.650] 00000000416eb1c0 ffff830546333870 ffff8305416eb000 ffff82d080320d60
> (XEN) [2014-06-05 14:10:54.650] ffff82d080277d20 ffff83054eff1068 0000000000000000 ffff8305416eb000
> (XEN) [2014-06-05 14:10:54.650] ffff8305416eb000 0000000000000000 0000000000000000 0000000000000011
> (XEN) [2014-06-05 14:10:54.650] ffff83054ef7fd98 ffff82d080105dcc ffff82d080129dcf ffff8305416eb000
> (XEN) [2014-06-05 14:10:54.650] ffffffffffffffff 00007f9b40a0b004 ffff83054ef7fef8 ffff82d080103926
> (XEN) [2014-06-05 14:10:54.650] ffff83054ef913a0 0000000000000282 ffff8305480e1010 ffff83009fd27000
> (XEN) [2014-06-05 14:10:54.650] 0000000000000000 ffff83009fd2718c 0000000000000246 0000000000000011
> (XEN) [2014-06-05 14:10:54.650] ffff83054ef7fdf8 0000000000000206 ffff83054ef7fe18 ffff82d08012c757
> (XEN) [2014-06-05 14:10:54.650] ffff83009fd27060 0000000000000005 ffff83054ef7fe68 0000000000000206
> (XEN) [2014-06-05 14:10:54.650] ffff83009fd27088 0000000000000286 0000000a00000002 0000000000000001
> (XEN) [2014-06-05 14:10:54.650] 0000000001eb2168 0000000001eb16a0 00007f9b4037c000 00007f9b407fc9f2
> (XEN) [2014-06-05 14:10:54.650] 35622d6200000005 0000000000000000 00007fff2b72c740 00007f9b40158620
> (XEN) [2014-06-05 14:10:54.650] 0000000000000010 0000000001ea8330 00007fff2b72c7b0 0000000001eb1e40
> (XEN) [2014-06-05 14:10:54.650] 0000000000000001 00007f9b40802a55 0000000000000000 00007f9b3fa753c7
> (XEN) [2014-06-05 14:10:54.650] ffff83054ef7fed8 ffff83009fd27000 0000000000000011 ffff88004d45ab98
> (XEN) [2014-06-05 14:10:54.650] 00007fff2b72c650 0000000000000011 00007cfab10800c7 ffff82d08022ca8b
> (XEN) [2014-06-05 14:10:54.651] ffffffff8100148a 0000000000000024 0000000000000011 00007fff2b72c650
> (XEN) [2014-06-05 14:10:54.651] ffff88004d45ab98 0000000000000011 ffff88004a14be98 00007fff2b72c650
> (XEN) [2014-06-05 14:10:54.651] Xen call trace:
> (XEN) [2014-06-05 14:10:54.651] [<ffff82d0801099b1>] evtchn_move_pirqs+0x90/0xbf
> (XEN) [2014-06-05 14:10:54.651] [<ffff82d080126e2f>] sched_move_domain+0x2c1/0x3ea
> (XEN) [2014-06-05 14:10:54.651] [<ffff82d080105dcc>] domain_kill+0xd0/0x159
> (XEN) [2014-06-05 14:10:54.651] [<ffff82d080103926>] do_domctl+0xab8/0x1542
> (XEN) [2014-06-05 14:10:54.651] [<ffff82d08022ca8b>] syscall_enter+0xeb/0x145
> (XEN) [2014-06-05 14:10:54.651]
> (XEN) [2014-06-05 14:10:54.651] Pagetable walk from 0000000000000328:
> (XEN) [2014-06-05 14:10:54.651] L4[0x000] = 0000000544e38067 0000000000057fc5
> (XEN) [2014-06-05 14:10:54.651] L3[0x000] = 000000053cc28067 000000000004fdd5
> (XEN) [2014-06-05 14:10:54.651] L2[0x000] = 0000000000000000 ffffffffffffffff
> (XEN) [2014-06-05 14:10:55.709]
> (XEN) [2014-06-05 14:10:55.718] ****************************************
> (XEN) [2014-06-05 14:10:55.737] Panic on CPU 5:
> (XEN) [2014-06-05 14:10:55.750] FATAL PAGE FAULT
> (XEN) [2014-06-05 14:10:55.763] [error_code=0000]
> (XEN) [2014-06-05 14:10:55.776] Faulting linear address: 0000000000000328
> (XEN) [2014-06-05 14:10:55.796] ****************************************
> (XEN) [2014-06-05 14:10:55.815]
> (XEN) [2014-06-05 14:10:55.824] Reboot in five seconds...
> (XEN) [2014-06-05 14:10:55.839] APIC error on CPU0: 00(08)
> (XEN) [2014-06-05 14:10:55.855] APIC error on CPU0: 08(08)
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel
[-- Attachment #1.2: Type: text/html, Size: 6361 bytes --]
[-- Attachment #2: Type: text/plain, Size: 126 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2014-06-05 15:04 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-05 14:54 Xen-unstable: Xen panic when shutting down HVM guest with PCI passthrough: RIP: e008:[<ffff82d0801099b1>] evtchn_move_pirqs+0x90/0xbf Sander Eikelenboom
2014-06-05 15:03 ` Andrew Cooper [this message]
2014-06-05 16:03 ` Sander Eikelenboom
2014-06-05 16:22 ` Andrew Cooper
2014-06-06 4:43 ` Jürgen Groß
2014-06-06 8:15 ` Sander Eikelenboom
2014-06-06 8:35 ` Jan Beulich
2014-06-06 9:44 ` Sander Eikelenboom
2014-06-06 10:03 ` Jan Beulich
2014-06-06 10:14 ` Sander Eikelenboom
2014-06-06 10:31 ` Jan Beulich
2014-06-06 10:32 ` Jan Beulich
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=539086BC.7070200@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=jbeulich@suse.com \
--cc=linux@eikelenboom.it \
--cc=xen-devel@lists.xenproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).