From: "Norton.Zhu" <norton.zhu@huawei.com>
To: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Cc: xen-devel@lists.xen.org
Subject: Re: 82599 passthrough problem
Date: Thu, 4 Feb 2016 14:42:32 +0800 [thread overview]
Message-ID: <56B2F2D8.40301@huawei.com> (raw)
In-Reply-To: <20160203175405.GC1069@char.us.oracle.com>
XEN HVM, after it hung, no serial log printed.
it hang in __pirq_guest_unbind. its call stack as follows:
(XEN) [<ffff82c4801682d6>] __pirq_guest_unbind+0x36/0x350
(XEN) [<ffff82c4801682d6>] __pirq_guest_unbind+0x36/0x350
(XEN) [<ffff82c480186e7b>] do_invalid_op+0x30b/0x3f0
(XEN) [<ffff82c48017e22c>] flush_area_mask+0x7c/0x130
(XEN) [<ffff82c480217808>] handle_exception_saved+0x30/0x6e
(XEN) [<ffff82c4801682cc>] __pirq_guest_unbind+0x2c/0x350
(XEN) [<ffff82c4801667a4>] domain_spin_lock_irq_desc+0x64/0xa0
(XEN) [<ffff82c4801689ed>] pirq_guest_unbind+0x5d/0x170
(XEN) [<ffff82c480141d9e>] pci_release_devices+0x13e/0x230
(XEN) [<ffff82c48015df28>] domain_relinquish_resources+0xa8/0x2a0
On 2016/2/4 1:54, Konrad Rzeszutek Wilk wrote:
> On Tue, Feb 02, 2016 at 12:04:36PM +0800, Norton.Zhu wrote:
>> Hi,all:
>>
>> I met a problem when passthrough 82599 to domU(for some reasons, I use pci passthrough not SRIOV).
>
> Is this PV or HVM?
>
>> It works well after passthrough, but the host hung after destroy domU.
>> Btw, no log prints even from serial port, but I found it hung afer unbind irq.
>> anyone knows what's wrong with it? thanks.
>
> Serial logs?
>>
>>
>> _______________________________________________
>> Xen-devel mailing list
>> Xen-devel@lists.xen.org
>> http://lists.xen.org/xen-devel
>
>
next prev parent reply other threads:[~2016-02-04 6:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-02 4:04 82599 passthrough problem Norton.Zhu
2016-02-03 17:54 ` Konrad Rzeszutek Wilk
2016-02-04 6:42 ` Norton.Zhu [this message]
2016-02-17 18:41 ` Konrad Rzeszutek Wilk
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=56B2F2D8.40301@huawei.com \
--to=norton.zhu@huawei.com \
--cc=konrad.wilk@oracle.com \
--cc=xen-devel@lists.xen.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.