[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [Xen-devel] test report for Xen 4.3 RC1
> > 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." _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxx http://lists.xen.org/xen-devel
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |