From: Eugene Istomin <E.Istomin@edss.ee>
To: xen-devel@lists.xen.org
Subject: Re: soft lockups of tapdisk2 process - xen 4.4, kernel 3.12.17
Date: Thu, 01 May 2014 15:26:06 +0300 [thread overview]
Message-ID: <2631163.Q3hPdMvMB3@evis> (raw)
In-Reply-To: <3712937.BtoHIzAgQ3@evis>
[-- 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
prev parent reply other threads:[~2014-05-01 12:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
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 message]
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=2631163.Q3hPdMvMB3@evis \
--to=e.istomin@edss.ee \
--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.