From owner-freebsd-current@freebsd.org Mon Jun 4 20:31:52 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id DB73AFEEDAB for ; Mon, 4 Jun 2018 20:31:51 +0000 (UTC) (envelope-from Alexander@leidinger.net) Received: from mailgate.Leidinger.net (mailgate.leidinger.net [IPv6:2a00:1828:2000:375::1:5]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 770AF848AE for ; Mon, 4 Jun 2018 20:31:51 +0000 (UTC) (envelope-from Alexander@leidinger.net) Date: Mon, 04 Jun 2018 22:31:08 +0200 DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=leidinger.net; s=outgoing-alex; t=1528144302; bh=abOEiFmE6AeFwI7EaFM+bYXUWE26CWLDH61Za6SSmsU=; h=Date:From:To:Cc:Subject:References:In-Reply-To; b=UhF3f7bzVZnpHQRSgjnT70sqH979UVHTESQFaOwkqxE/sbDVTZQsQhhRJRRYChHNF FtX+v3juzfiVAZ8gMjgulGkIa1FmXWJGAs3AWG/3uxOCynaDsB0J/nQRSsj2ceAxfs z/AC58j2bynyKKWSiPBQcB/wnXmqx2BCA6nZCWTZGjUjRVT8gPvmfEdgZbkOJXAc5R 167iwC3K1rUVRsR1pzzi+gE9FfxUgFgm0Alk4NxBKbK2xiEzvRzRtezzGowRCbe5bW dxr0HgiyTkUW9UK9Ji6QiXqgIYphfZ1QOFloxoH6Su5xYNUhz8U0BpsoDENs7dHzCI k1/y2LqVzik1Q== Message-ID: <20180604223108.Horde.RcVquaVKWdNzNidD_5aJz7E@webmail.leidinger.net> From: Alexander Leidinger To: Slawa Olhovchenkov Cc: Kirill Ponomarev , freebsd-current@freebsd.org Subject: Re: Deadlocks / hangs in ZFS References: <20180522101749.Horde.Wxz9gSxx1xArxkYMQqTL0iZ@webmail.leidinger.net> <20180522122924.GC1954@zxy.spb.ru> <20180522161632.Horde.ROSnBoZixBoE9ZBGp5VBQgZ@webmail.leidinger.net> <20180522144055.GD1954@zxy.spb.ru> <20180527194159.v54ox3vlthpuvx4q@jo> <20180527220612.GK1926@zxy.spb.ru> <20180528090201.Horde._E4JZcuEaZHfj_BNzWjci2O@webmail.leidinger.net> <20180603211450.Horde.pI-Fom6S1tUcaHvTF4MUjin@webmail.leidinger.net> <20180603192814.GP1926@zxy.spb.ru> In-Reply-To: <20180603192814.GP1926@zxy.spb.ru> User-Agent: Horde Application Framework 5 Content-Type: multipart/signed; boundary="=_qe-DcLRCIIZd1WsRly-W4dK"; protocol="application/pgp-signature"; micalg=pgp-sha1 MIME-Version: 1.0 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 04 Jun 2018 20:31:52 -0000 This message is in MIME format and has been PGP signed. --=_qe-DcLRCIIZd1WsRly-W4dK Content-Type: text/plain; charset=utf-8; format=flowed; DelSp=Yes Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Quoting Slawa Olhovchenkov (from Sun, 3 Jun 2018=20=20 22:28:14=20+0300): > On Sun, Jun 03, 2018 at 09:14:50PM +0200, Alexander Leidinger wrote: > >> Quoting Alexander Leidinger (from Mon, 28 >> May 2018 09:02:01 +0200): >> >> > Quoting Slawa Olhovchenkov (from Mon, 28 May 2018 >> > 01:06:12 +0300): >> > >> >> On Sun, May 27, 2018 at 09:41:59PM +0200, Kirill Ponomarev wrote: >> >> >> >>> On 05/22, Slawa Olhovchenkov wrote: >> >>>> > It has been a while since I tried Karl's patch the last time, and= I >> >>>> > stopped because it didn't apply to -current anymore at some point= . >> >>>> > Will what is provided right now in the patch work on -current? >> >>>> >> >>>> I am mean yes, after s/vm_cnt.v_free_count/vm_free_count()/g >> >>>> I am don't know how to have two distinct patch (for stable and >> >>>> current) in one review. >> >>> >> >>> I'm experiencing these issues sporadically as well, would you mind >> >>> to publish this patch for fresh current? >> >> >> >> Week ago I am adopt and publish patch to fresh current and stable, is >> >> adopt need again? >> > >> > I applied the patch in the review yesterday to rev 333966, it >> > applied OK (with some fuzz). I will try to reproduce my issue with >> > the patch. >> >> The behavior changed (or the system was long enough in this state >> without me noticing it). I have a panic now: >> panic: deadlkres: possible deadlock detected for 0xfffff803766db580, >> blocked for 1803003 ticks > > Hmm, may be first determinate locked function > > addr2line -ie /boot/kernel/kernel 0xfffff803766db580 > > or > > kgdb > x/10i 0xfffff803766db580 Both don'T produce any sensible output: (kgdb) x/10i 0xfffff803766db580 0xfffff803766db580: subb $0x80,-0x78(%rsi) 0xfffff803766db584: (bad) 0xfffff803766db585: (bad) 0xfffff803766db586: (bad) 0xfffff803766db587: incl -0x7f7792(%rax) 0xfffff803766db58d: (bad) 0xfffff803766db58e: (bad) 0xfffff803766db58f: incl -0x7f7792(%rax) 0xfffff803766db595: (bad) 0xfffff803766db596: (bad) Seems I need to provoke a real kernel dump instead of a textdump for this. Bye, Alexander. --=20 http://www.Leidinger.net=20Alexander@Leidinger.net: PGP 0x8F31830F9F2772BF http://www.FreeBSD.org netchild@FreeBSD.org : PGP 0x8F31830F9F2772BF --=_qe-DcLRCIIZd1WsRly-W4dK Content-Type: application/pgp-signature Content-Description: Digitale PGP-Signatur Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQIcBAABAgAGBQJbFaGMAAoJEKrxQhqFIICEf8MP/3MJ5+SyvKue3kRXrHQDc1WG AOhJc8YMrJUYkh8udbEbkDTCVT/4XrrZVUL9tzhe59WnWKYxei9Bs9Zjku+83+wm BlqUBQ99AhMOOgL+KiDHw98IaFrd0wvVKQFLc5MJN2bggpDxib/Vkytw+fxdnfNJ CbHqIJZ0KeLPbFzmwXsrumU66zcQwQ+dHISJ9DLM+8a3jzL7x/X4xSkJeNxKjJNi CEO1rtI+mE5ATd13UqqcUBdGfDiWLKt/3crXwGWdlvvnZng4oSDAsfWuyzSg8QeU jHNnP2/CWshOU7H0N7K0nisAw9b86UKJGA34rKAGACyONQ61/Vquc4wIpHJyLT+B 9wtywOhJipV2ZNFp48f5UZnaEHBh82ySGsZh4ZCGqKwmbbtNDAvbLDbrCEEV1Hu2 rd/vge3RmF1ZBtZQ8RnncTU8gDSJ1zdyiNOMZi4t4Tq7seZFmWQ3SiAt6ljCn87d d9Dl/EpIFCbS8Pr9/IonzMIKJVHakWOm0qRC7gsnTTkGO4PX9/N36lgp2FPV+Qe1 EqmMtdrLZC4SClCXV1EbC7sBrRS2ORa18aRD74v3xsYWjO/PaCaZbo5+h1uLdd6I Hc9aLB+KZCwhWaIQ4edNilxe3Z7DkuOZarLMmLI2lVtGIkEDdBEufdcsScU2rrf8 pJpx8t+WznZBxn92cbR5 =X5zV -----END PGP SIGNATURE----- --=_qe-DcLRCIIZd1WsRly-W4dK--