[BRLTTY] BRLTTY floods the log with the Freedom Scientific Focus Blue

[Alex ARNAUD]

Hello all,

I'm helping a blind user with a Freedom Scientific focus blue with the 
id "0f4e:0114". I don't know the exact model sorry. It seems lsusb 
dosn't provide us detailed informations about the device.

He uses:

  * Debian 10 "Buster"
  * BRLTTY 6.1
  * The Linux kernel 5.8.10


BRLTTY floods the syslog and daemon files with the following logs:
> kernel: [ 1988.905326] usb 1-3: usbfs: USBDEVFS_CONTROL failed cmd 
> brltty rqt 128 rq 6 len 255 ret -71
> kernel: [ 1988.905587] usb 1-3: usbfs: USBDEVFS_CONTROL failed cmd 
> brltty rqt 128 rq 6 len 255 ret -71
> kernel: [ 1988.905755] usb 1-3: usbfs: USBDEVFS_CONTROL failed cmd 
> brltty rqt 128 rq 6 len 255 ret -71
> kernel: [ 1988.905824] xhci_hcd 0000:00:14.0: Trying to add endpoint 
> 0x1 without dropping it.
> kernel: [ 1988.905967] usb 1-3: usbfs: USBDEVFS_CONTROL failed cmd 
> brltty rqt 128 rq 6 len 255 ret -71
> brltty[3434]: USB language code string read error
> brltty[3434]: USB control transfer error 71: Erreur de protocole
> brltty[3434]: USB language code string read error
> brltty[3434]: USB configuration set error 22: Argument invalide
> brltty[3434]: USB control transfer error 71: Erreur de protocole
> brltty[3434]: USB configuration descriptor not readable: 0
> brltty[3434]: USB configuration descriptor not found: 1

It has produced 5 GB of logs and prevented X.Org to start.

Based on our tests, the Braille device works.

Moving the log level to emergency doesn't seem to have produce any 
effects. Defining the log file to /tmp/brltty.log continues to pollute 
the syslog and daemon.log.

What can we do to improve the situation? Currently we've unplugged the 
Focus Blue and stop BRLTTY.

Thanks in advance for any help you could provide,
Alex.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://brltty.app/pipermail/brltty/attachments/20201124/d215f269/attachment.html>