From owner-freebsd-current@freebsd.org Tue Mar 21 16:29:54 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id DD8EED16561 for ; Tue, 21 Mar 2017 16:29:54 +0000 (UTC) (envelope-from hps@selasky.org) Received: from mail.turbocat.net (turbocat.net [88.99.82.50]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id A86C26E8 for ; Tue, 21 Mar 2017 16:29:54 +0000 (UTC) (envelope-from hps@selasky.org) Received: from hps2016.home.selasky.org (unknown [62.141.129.119]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.turbocat.net (Postfix) with ESMTPSA id 4695A1FE021; Tue, 21 Mar 2017 17:28:55 +0100 (CET) Subject: Re: sysctl -a hangs ? To: hiren panchasara , Kurt Jaeger References: <20170321160407.GJ64587@home.opsec.eu> <20170321161438.GH80268@strugglingcoder.info> Cc: freebsd-current@freebsd.org From: Hans Petter Selasky Message-ID: Date: Tue, 21 Mar 2017 17:29:00 +0100 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:45.0) Gecko/20100101 Thunderbird/45.7.1 MIME-Version: 1.0 In-Reply-To: <20170321161438.GH80268@strugglingcoder.info> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 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: Tue, 21 Mar 2017 16:29:55 -0000 On 03/21/17 17:14, hiren panchasara wrote: > On 03/21/17 at 05:04P, Kurt Jaeger wrote: >> Hello, >> >> I have a freshly installed/updated FreeBSD 11.0p8 on a supermicro >> X11SSZ-TLN4F board, and >> >> pkg install intel-ixl-kmod >> >> and now: >> >> sysctl -a >> >> hangs. Any quick ideas how to debug this ? > > If it's just not responding to anything, you can try to panic the box, > got to db> and see if you can find sleepchain/lockchain? > You can also take a dump and try to look at same with kgdb scripts. > You'd need kernel with WITNESS. Hi, procstat -ak Will tell you where it is stuck. --HPS