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

_______________________________________________
freebsd-net@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"

Reply via email to