Date: Sat, 10 Sep 2016 09:04:14 -0700 From: Yuri <yuri@rawbw.com> To: Ben Woods <woodsb02@gmail.com> Cc: "freebsd-net@freebsd.org" <freebsd-net@freebsd.org> Subject: Re: Search for SANE scanners freezes the system Message-ID: <11f0efa3-cb9f-9a99-48bf-ae1a13d31aaa@rawbw.com> In-Reply-To: <CAOc73CAoTq5R%2B6UP4dr8hvKMBPFGD7JcwqEe8v_mHv1aKD06aw@mail.gmail.com> References: <6b3e68d6-9add-bb25-9bbe-58d1721ab9d1@rawbw.com> <CAOc73CAoTq5R%2B6UP4dr8hvKMBPFGD7JcwqEe8v_mHv1aKD06aw@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?11f0efa3-cb9f-9a99-48bf-ae1a13d31aaa>