I have also suffered for a number of years on different Intel-based x86_64 machines, whereby intermittent -110 (timeout) messages are encountered for adapters running in the dvbsky.c module (for me, the MyGica T230 DVB-T2 adapters and DVBSky S960 DVB-S2 adapters). Sometimes the machine can go for several weeks (or months) and be OK, then it will randomly encounter the error and require a reboot to fix it.
Personally, I worked around the issue by buying a usb hub and programmatically cycling the usb port power using uhubctl when the error is encountered (thus not requiring a full reboot), but this is obviously far from ideal.
I have recently made some headway in debugging the underlying cause in the driver. From what I've found it seems to occur more frequently when the TVheadend status period is set lower. e.g. with the status read period set to 8000ms (maximum) the issue occurs far less frequently for me.
I think it might be caused by a race condition when a thread attempts to update the last_lock status of the device, whilst another reads the state buffers (which are defined in the same struct as last_lock) to send i2c messages. I have attached a patch that I am trialling on my own machine, but since it can take several weeks for this to surface on my hardware I thought I would share this patch incase anyone else is able/willing to test on hardware where the error is more frequent. Note: this is only intended to fix those random -110 timeout problems with adapters running inside the dvbsky module (e.g. MyGica) - no ideas what the (similar) issue is with the Astrometa adapter as reported earlier in this thread - I don't own one of those adapters.
