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

[Mario Lang]

Alex ARNAUD <aarnaud at hypra.fr> writes:

> 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.

lsusb -v refusing to provide details usually means even the kernel had
trouble reading the device descriptors.

> 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

These logs are from the kernel, not BRLTTY.

>  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. 

Which tests?  On the same computer with Linux, or with some other OS?
Also, is the user actually using the device?

> Moving the log level to emergency doesn't seem to have produce any effects.

Which log level?  There are more log levels involved here.  What the
kernel reports, and what BRLTTY will log.

> 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.

Again, was the user actually using the device?  If it was properly
functioning, I wonder why BRLTTY was apparently retrying to initialize
the device again and again.  Could it be that more then just one BRLTTY
were trying to fight over the same device?  IOW, did you check that only
one instance of BRLTTY was running?

-- 
CYa,
  ⡍⠁⠗⠊⠕