From owner-freebsd-hackers@freebsd.org Tue Feb 20 19:20:20 2018 Return-Path: Delivered-To: freebsd-hackers@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 AA9EBF2305E for ; Tue, 20 Feb 2018 19:20:20 +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 46EAB87F62; Tue, 20 Feb 2018 19:20:19 +0000 (UTC) (envelope-from hps@selasky.org) Received: from hps2016.home.selasky.org (unknown [62.141.128.70]) (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 06BB02603D1; Tue, 20 Feb 2018 20:20:12 +0100 (CET) Subject: Re: 'scanimage -L' from 'graphics/sane-backends' causes system crashes after a while To: Yuri , Freebsd hackers list Cc: Alan Somers References: <5fe20134-4b4f-4789-fa54-8ce746453130@rawbw.com> <766fc276-afd0-a214-509f-3ccf98bef733@rawbw.com> From: Hans Petter Selasky Message-ID: <0de11b5e-b154-9f20-e59c-0a5b7d932375@selasky.org> Date: Tue, 20 Feb 2018 20:20:02 +0100 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0 MIME-Version: 1.0 In-Reply-To: <766fc276-afd0-a214-509f-3ccf98bef733@rawbw.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 20 Feb 2018 19:20:20 -0000 On 02/20/18 19:35, Yuri wrote: > On 02/20/18 10:19, Alan Somers wrote: >> Please open an issue on bugzilla, and include the full stacktrace of the >> crash. > > > It actually freezes, doesn't crash. So I won't be able to get a stack > trace. > Hi, "procstat -ak " might give some clues. --HPS