From mboxrd@z Thu Jan 1 00:00:00 1970 From: George Dunlap Subject: Re: test report for Xen 4.3 RC1 Date: Tue, 28 May 2013 16:24:48 +0100 Message-ID: <51A4CC40.1090802@eu.citrix.com> References: <1B4B44D9196EFF41AE41FDA404FC0A1001AE1B1D@SHSMSX102.ccr.corp.intel.com> <20130528151537.GS724@phenom.dumpdata.com> <20130528152156.GB3027@phenom.dumpdata.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; Format="flowed" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20130528152156.GB3027@phenom.dumpdata.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Konrad Rzeszutek Wilk Cc: "Ren, Yongjie" , "Tian, Yongxue" , "xen-devel@lists.xen.org" , "Xu, YongweiX" , xen@bugs.xenproject.org, "Liu, SongtaoX" List-Id: xen-devel@lists.xenproject.org On 28/05/13 16:21, Konrad Rzeszutek Wilk wrote: >>> 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] [] schedule+0x24/0x70 > [ 483.723604] [] read_reply+0xad/0x160 > [ 483.741162] [] ? wake_up_bit+0x40/0x40 > [ 483.758572] [] xs_talkv+0xe4/0x1f0 > [ 483.775741] [] xs_single+0x46/0x60 > [ 483.792791] [] xenbus_transaction_start+0x24/0x60 > [ 483.809929] [] __xenbus_switch_ste+0x32/0x120 > ^G[ 483.826947] [] ? __dev_printk+0x39/0x90 > [ 483.843792] [] ? _dev_info+0x4e/0x50 > [ 483.860412] [] xenbus_switch_state+0xb/0x10 > [ 483.877312] [] xenbus_dev_shutdown+0x37/0xa0 > [ 483.894036] [] device_shutdown+0x15/0x180 > [ 483.910605] [] kernel_restart_prepare+0x31/0x40 > [ 483.927100] [] kernel_restart+0x11^G[ 483.943262] [] SYSC_reboot+0x1b5/0x260 > [ 483.959480] [] ? trace_hardirqs_on_caller+0^G[ 483.975786] [] ? trace_hardirqs_on+0xd/0x10 > [ 483.991819] [] ? kmem_cache_free+0x123/0x360 > [ 484.007675] [] ? __free_pages+0x25/0x^G[ 484.023336] [] ? free_pages+0x4c/0x50 > [ 484.039176] [] ? __mmdrop+0x67/0xd0 > [ 484.055174] [] ? sysret_check+0x22/0x5d > [ 484.070747] [] ? trace_hardirqs_on_caller+0x10d/0x1d0 > [ 484.086121] [] SyS_reboot+0x9/0x10 > [ 484.101318] [] system_call_fastpath+0x16/0x1b > [ 484.116585] 3 locks held by init/4163: > [ 484.131650]+.+.+.}, at: [] SYSC_reboot+0xe0/0x260 > ^G^G^G^G^G^G[ 484.147704] #1: (&__lockdep_no_validate__){......}, at: [] device_shutdown+0xc3/0x180 > [ 484.164359] #2: (&xs_state.request_mutex){+.+...}, at: [] xs_talkv+0x6b/0x1f0 > > create ! > title -1 "linux, xenbus mutex hangs when rebooting dom0 and guests hung." 1. I think that these commands have to come at the top 2. You don't need quotes in the title 3. You need to be polite and say "thanks" at the end so it knows it can stop paying attention. :-) -George