From mboxrd@z Thu Jan 1 00:00:00 1970 From: Eugene Istomin Subject: Re: soft lockups of tapdisk2 process - xen 4.4, kernel 3.12.17 Date: Thu, 01 May 2014 15:26:06 +0300 Message-ID: <2631163.Q3hPdMvMB3@evis> References: <3712937.BtoHIzAgQ3@evis> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1858203261432037098==" Return-path: In-Reply-To: <3712937.BtoHIzAgQ3@evis> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: xen-devel@lists.xen.org List-Id: xen-devel@lists.xenproject.org This is a multi-part message in MIME format. --===============1858203261432037098== Content-Type: multipart/alternative; boundary="nextPart1492214.sxCaz2hlO3" Content-Transfer-Encoding: 7Bit This is a multi-part message in MIME format. --nextPart1492214.sxCaz2hlO3 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="utf-8" 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 --nextPart1492214.sxCaz2hlO3 Content-Transfer-Encoding: 7Bit Content-Type: text/html; charset="utf-8"

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


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

 



--nextPart1492214.sxCaz2hlO3-- --===============1858203261432037098== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel --===============1858203261432037098==--