* soft lockups of tapdisk2 process - xen 4.4, kernel 3.12.17
@ 2014-04-17 5:11 Eugene Istomin
2014-04-17 6:39 ` Eugene Istomin
2014-05-01 12:26 ` Eugene Istomin
0 siblings, 2 replies; 3+ messages in thread
From: Eugene Istomin @ 2014-04-17 5:11 UTC (permalink / raw)
To: xen-devel
[-- Attachment #1.1: Type: text/plain, Size: 702 bytes --]
Hello,
after updating from xen 4.3 to xen 4.4 we have strange soft lockups, here
is log - https://gist.github.com/evis/10953677.[1]
We already disabled c-states in BIOS, kernel (processor.max_cstate=1
intel_idle.max_cstate=0), dom0 (xenpm set-max-cstate 1). An easy step to
reproduce in our environment - run 2 VMs with DRBD-backed disk.
What "blktap_run_deferred" in this trace mean and why dom0 needs to call
"blktap_device_restart"?
force_evtchn_callback+0xe/0x10
blktap_device_restart+0xdf/0xf0 [blktap2]
blktap_run_deferred+0xd1/0xe0 [blktap2]
blktap_ring_ioctl+0x3a5/0x4d0 [blktap2]
Thanks.
/---/
*/Best regards,/*
/Eugene Istomin/
--------
[1] https://gist.github.com/evis/10953677
[-- Attachment #1.2: Type: text/html, Size: 4247 bytes --]
[-- Attachment #2: Type: text/plain, Size: 126 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: soft lockups of tapdisk2 process - xen 4.4, kernel 3.12.17
2014-04-17 5:11 soft lockups of tapdisk2 process - xen 4.4, kernel 3.12.17 Eugene Istomin
@ 2014-04-17 6:39 ` Eugene Istomin
2014-05-01 12:26 ` Eugene Istomin
1 sibling, 0 replies; 3+ messages in thread
From: Eugene Istomin @ 2014-04-17 6:39 UTC (permalink / raw)
To: xen-devel; +Cc: Xen Devel
We compare 3.12/3.13/3.14 kernels (keyword - PREEMPT_NEED_RESCHED), 3.12
haven't any patches for related to PREEMPT_NEED_RESCHED:
3.12 - https://git.kernel.org/cgit/linux/kernel/git/stable/linux-stable.git/log/?id=refs%2Ftags%2Fv3.12.17&qt=grep&q=PREEMPT_NEED_RESCHED
3.13 - https://git.kernel.org/cgit/linux/kernel/git/stable/linux-stable.git/log/?id=refs%2Ftags%2Fv3.13.10&qt=grep&q=PREEMPT_NEED_RESCHED
3.14 - https://git.kernel.org/cgit/linux/kernel/git/stable/linux-stable.git/log/?id=refs%2Ftags%2Fv3.14.1&qt=grep&q=kmemleak.c
What do you think about commit ba1f14fbe70965ae0fb1655a5275a62723f65b77
(https://git.kernel.org/cgit/linux/kernel/git/stable/linux-stable.git/commit/?id=ba1f14fbe70965ae0fb1655a5275a62723f65b77
)? May this problem related to interrupt handling?
[ 6624.928058] Call Trace:
[ 6624.928058] [<ffffffff8036d192>] notify_remote_via_ipi+0x82/0xb0
..
---
Best regards,
Eugene Istomin
On Thursday, April 17, 2014 08:11:25 AM Eugene Istomin wrote:
Hello,
after updating from xen 4.3 to xen 4.4 we have strange soft lockups, here is
log - https://gist.github.com/evis/10953677.
We already disabled c-states in BIOS, kernel (processor.max_cstate=1
intel_idle.max_cstate=0), dom0 (xenpm set-max-cstate 1). An easy step to
reproduce in our environment - run 2 VMs with DRBD-backed disk.
What "blktap_run_deferred" in this trace mean and why dom0 needs to call
"blktap_device_restart"?
force_evtchn_callback+0xe/0x10
blktap_device_restart+0xdf/0xf0 [blktap2]
blktap_run_deferred+0xd1/0xe0 [blktap2]
blktap_ring_ioctl+0x3a5/0x4d0 [blktap2]
Thanks.
---
Best regards,
Eugene Istomin
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: soft lockups of tapdisk2 process - xen 4.4, kernel 3.12.17
2014-04-17 5:11 soft lockups of tapdisk2 process - xen 4.4, kernel 3.12.17 Eugene Istomin
2014-04-17 6:39 ` Eugene Istomin
@ 2014-05-01 12:26 ` Eugene Istomin
1 sibling, 0 replies; 3+ messages in thread
From: Eugene Istomin @ 2014-05-01 12:26 UTC (permalink / raw)
To: xen-devel
[-- Attachment #1.1: Type: text/plain, Size: 891 bytes --]
Closed,
lockups comes from misversioned xen packages after update:
xen-tools 4.3.2_01-12.1
xen-libs 4.3.2_01-12.1
xen 4.4.0_14-313.2
Thanks.
/---/
*/Best regards,/*
/Eugene Istomin/
Hello,
after updating from xen 4.3 to xen 4.4 we have strange soft lockups, here
is log - https://gist.github.com/evis/10953677.[1]
We already disabled c-states in BIOS, kernel (processor.max_cstate=1
intel_idle.max_cstate=0), dom0 (xenpm set-max-cstate 1). An easy step to
reproduce in our environment - run 2 VMs with DRBD-backed disk.
What "blktap_run_deferred" in this trace mean and why dom0 needs to call
"blktap_device_restart"?
force_evtchn_callback+0xe/0x10
blktap_device_restart+0xdf/0xf0 [blktap2]
blktap_run_deferred+0xd1/0xe0 [blktap2]
blktap_ring_ioctl+0x3a5/0x4d0 [blktap2]
Thanks.
/---/
*/Best regards,/*
/Eugene Istomin/
--------
[1] https://gist.github.com/evis/10953677
[-- Attachment #1.2: Type: text/html, Size: 6823 bytes --]
[-- Attachment #2: Type: text/plain, Size: 126 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2014-05-01 12:26 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2014-04-17 5:11 soft lockups of tapdisk2 process - xen 4.4, kernel 3.12.17 Eugene Istomin
2014-04-17 6:39 ` Eugene Istomin
2014-05-01 12:26 ` Eugene Istomin
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).