From owner-freebsd-net@freebsd.org Sat Sep 10 16:04:16 2016 Return-Path: Delivered-To: freebsd-net@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 CD3B3BD404E for ; Sat, 10 Sep 2016 16:04:16 +0000 (UTC) (envelope-from yuri@rawbw.com) Received: from shell1.rawbw.com (shell1.rawbw.com [198.144.192.42]) by mx1.freebsd.org (Postfix) with ESMTP id BD995F6A for ; Sat, 10 Sep 2016 16:04:16 +0000 (UTC) (envelope-from yuri@rawbw.com) Received: from yuri.doctorlan.com (c-24-5-143-190.hsd1.ca.comcast.net [24.5.143.190]) (authenticated bits=0) by shell1.rawbw.com (8.15.1/8.15.1) with ESMTPSA id u8AG4FSo029928 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Sat, 10 Sep 2016 09:04:15 -0700 (PDT) (envelope-from yuri@rawbw.com) X-Authentication-Warning: shell1.rawbw.com: Host c-24-5-143-190.hsd1.ca.comcast.net [24.5.143.190] claimed to be yuri.doctorlan.com Subject: Re: Search for SANE scanners freezes the system To: Ben Woods References: <6b3e68d6-9add-bb25-9bbe-58d1721ab9d1@rawbw.com> Cc: "freebsd-net@freebsd.org" From: Yuri Message-ID: <11f0efa3-cb9f-9a99-48bf-ae1a13d31aaa@rawbw.com> Date: Sat, 10 Sep 2016 09:04:14 -0700 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:45.0) Gecko/20100101 Thunderbird/45.1.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 10 Sep 2016 16:04:16 -0000 On 09/09/2016 17:33, Ben Woods wrote: > Can you please define more what you mean by "freezes the system"? > > Does it panic the kernel (which either reboots itself or drops you to a > debugging console)? > > Does the command line just not output anything and not return to the > prompt? In this case, maybe a Ctrl+c will exit the scanimage program and > return you to the prompt? > > Or does it freeze your scanner (I.e. The impact is on your scanner, leaving > your FreeBSD machine running fine)? System doesn't panic, it just stops, the same image stays on the graphics screen, keyboard/mouse become dead, and it doesn't respond to the network queries. I am thinking that this command sends some unusual broadcasts that possibly expose some bug. I think I can reproduce it reliably on my system. But I am not sure where to go from here. Yuri