From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: "Ren, Yongjie" <yongjie.ren@intel.com>,
george.dunlap@eu.citrix.com, xen@bugs.xenproject.org
Cc: "Xu, YongweiX" <yongweix.xu@intel.com>,
"Liu, SongtaoX" <songtaox.liu@intel.com>,
"Tian, Yongxue" <yongxue.tian@intel.com>,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: test report for Xen 4.3 RC1
Date: Tue, 28 May 2013 11:21:56 -0400 [thread overview]
Message-ID: <20130528152156.GB3027@phenom.dumpdata.com> (raw)
In-Reply-To: <20130528151537.GS724@phenom.dumpdata.com>
> > 5. Dom0 cannot be shutdown before PCI device detachment from guest
> > http://bugzilla.xen.org/bugzilla/show_bug.cgi?id=1826
>
> Ok, I can reproduce that too.
This is what dom0 tells me:
[ 483.586675] INFO: task init:4163 blocked for more than 120 seconds.
[ 483.603675] "echo 0 > /proc/sys/kernel/hung_task_timG^G[ 483.620747] init D ffff880062b59c78 5904 4163 1 0x00000000
[ 483.637699] ffff880062b59bc8 0000000000000^G[ 483.655189] ffff880062b58000 ffff880062b58000 ffff880062b58010 ffff880062b58000
[ 483.672505] ffff880062b59fd8 ffff880062b58000 ffff880062f20180 ffff880078bca500
[ 483.689527] Call Trace:
[ 483.706298] [<ffffffff816a0814>] schedule+0x24/0x70
[ 483.723604] [<ffffffff813bb0dd>] read_reply+0xad/0x160
[ 483.741162] [<ffffffff810b6b10>] ? wake_up_bit+0x40/0x40
[ 483.758572] [<ffffffff813bb274>] xs_talkv+0xe4/0x1f0
[ 483.775741] [<ffffffff813bb3c6>] xs_single+0x46/0x60
[ 483.792791] [<ffffffff813bbab4>] xenbus_transaction_start+0x24/0x60
[ 483.809929] [<ffffffff813ba202>] __xenbus_switch_ste+0x32/0x120
^G[ 483.826947] [<ffffffff8142df39>] ? __dev_printk+0x39/0x90
[ 483.843792] [<ffffffff8142dfde>] ? _dev_info+0x4e/0x50
[ 483.860412] [<ffffffff813ba2fb>] xenbus_switch_state+0xb/0x10
[ 483.877312] [<ffffffff813bd487>] xenbus_dev_shutdown+0x37/0xa0
[ 483.894036] [<ffffffff8142e275>] device_shutdown+0x15/0x180
[ 483.910605] [<ffffffff810a8841>] kernel_restart_prepare+0x31/0x40
[ 483.927100] [<ffffffff810a88a1>] kernel_restart+0x11^G[ 483.943262] [<ffffffff810a8ab5>] SYSC_reboot+0x1b5/0x260
[ 483.959480] [<ffffffff810ed52d>] ? trace_hardirqs_on_caller+0^G[ 483.975786] [<ffffffff810ed5fd>] ? trace_hardirqs_on+0xd/0x10
[ 483.991819] [<ffffffff8119db03>] ? kmem_cache_free+0x123/0x360
[ 484.007675] [<ffffffff8115c725>] ? __free_pages+0x25/0x^G[ 484.023336] [<ffffffff8115c9ac>] ? free_pages+0x4c/0x50
[ 484.039176] [<ffffffff8108b527>] ? __mmdrop+0x67/0xd0
[ 484.055174] [<ffffffff816aae95>] ? sysret_check+0x22/0x5d
[ 484.070747] [<ffffffff810ed52d>] ? trace_hardirqs_on_caller+0x10d/0x1d0
[ 484.086121] [<ffffffff810a8b69>] SyS_reboot+0x9/0x10
[ 484.101318] [<ffffffff816aae69>] system_call_fastpath+0x16/0x1b
[ 484.116585] 3 locks held by init/4163:
[ 484.131650]+.+.+.}, at: [<ffffffff810a89e0>] SYSC_reboot+0xe0/0x260
^G^G^G^G^G^G[ 484.147704] #1: (&__lockdep_no_validate__){......}, at: [<ffffffff8142e323>] device_shutdown+0xc3/0x180
[ 484.164359] #2: (&xs_state.request_mutex){+.+...}, at: [<ffffffff813bb1fb>] xs_talkv+0x6b/0x1f0
create !
title -1 "linux, xenbus mutex hangs when rebooting dom0 and guests hung."
next prev parent reply other threads:[~2013-05-28 15:21 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-27 3:49 test report for Xen 4.3 RC1 Ren, Yongjie
2013-05-28 15:15 ` Konrad Rzeszutek Wilk
2013-05-28 15:21 ` Konrad Rzeszutek Wilk [this message]
2013-05-28 15:24 ` George Dunlap
2013-11-11 10:22 ` Ian Campbell
2013-11-08 16:21 ` Is: linux, xenbus mutex hangs when rebooting dom0 and guests hung." Was:Re: " Konrad Rzeszutek Wilk
2013-11-08 16:30 ` Processed: " xen
2013-11-10 20:20 ` Matt Wilson
2013-11-10 20:30 ` Processed: " xen
2013-11-11 2:40 ` Liu, SongtaoX
2013-11-11 2:45 ` Processed: " xen
-- strict thread matches above, loose matches on Subject: below --
2013-06-04 15:59 Ren, Yongjie
2013-06-04 16:35 ` Konrad Rzeszutek Wilk
2013-06-05 10:14 Ren, Yongjie
2013-06-05 14:50 ` Konrad Rzeszutek Wilk
2013-06-16 4:10 Ren, Yongjie
2013-06-17 14:23 ` Konrad Rzeszutek Wilk
2013-06-17 20:35 ` Konrad Rzeszutek Wilk
2013-06-17 20:36 ` Konrad Rzeszutek Wilk
2013-06-20 2:53 ` Ren, Yongjie
2013-06-21 18:17 ` Konrad Rzeszutek Wilk
2013-07-02 8:09 ` Ren, Yongjie
2013-07-02 13:36 ` 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=20130528152156.GB3027@phenom.dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=george.dunlap@eu.citrix.com \
--cc=songtaox.liu@intel.com \
--cc=xen-devel@lists.xen.org \
--cc=xen@bugs.xenproject.org \
--cc=yongjie.ren@intel.com \
--cc=yongweix.xu@intel.com \
--cc=yongxue.tian@intel.com \
/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.