From owner-freebsd-current@freebsd.org Sat Apr 7 04:01:40 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 BC2BDF80F02 for ; Sat, 7 Apr 2018 04:01:40 +0000 (UTC) (envelope-from julian@freebsd.org) Received: from vps1.elischer.org (vps1.elischer.org [204.109.63.16]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "vps1.elischer.org", Issuer "CA Cert Signing Authority" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 6057776431 for ; Sat, 7 Apr 2018 04:01:40 +0000 (UTC) (envelope-from julian@freebsd.org) Received: from Julian-MBP3.local (115-166-20-68.dyn.iinet.net.au [115.166.20.68]) (authenticated bits=0) by vps1.elischer.org (8.15.2/8.15.2) with ESMTPSA id w3741SHT071904 (version=TLSv1.2 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO) for ; Fri, 6 Apr 2018 21:01:31 -0700 (PDT) (envelope-from julian@freebsd.org) To: freebsd-current From: Julian Elischer Subject: deadlock detected in -current (new).. NFS? Anyone with 'amd' knowledge? Message-ID: Date: Sat, 7 Apr 2018 12:01:23 +0800 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:52.0) Gecko/20100101 Thunderbird/52.7.0 MIME-Version: 1.0 Content-Language: en-US Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 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: Sat, 07 Apr 2018 04:01:41 -0000 Anyone seen these recently? I just got the following: panic: deadlkres: possible deadlock detected for (address)  blocked for (big number) ticks anyone seen similar on very new (yesterday) -current GENERIC. ? there was a prior message that may or may not be related: newnfs: server pid741@gamma  error: fileid changed. fsid 0:0: expected fileid 0x1, got 0x2 (BROKEN NFS SERVER OR MIDDLEWARE) (amd screwed up). I suspect that amd is broken on -current using known good config files results in a hung nfs mount and even after killing amd, any attempt to touch the mountpoint results in a hung (but interruptable) proccess. For example as /net  was an amd mountpoint,   ls -l /    results in a hung copy of ls. (but you can get it back with ^C) I suspect the two are related. Julian