I installed a self compiled image (24013, still current, with @kedder OV Shell) on 2 OVs in our club. On both OVs XCSoar crashes with libinput warning messages "lagging behind by XXms, your system is too slow".
On the first OV, this happens sometimes. On the second OV it happens frequently, and also vario sound stops after a few seconds (both variod and XCSoar generated). The vario itself (sensor data and vario gauge) keep working.
I took the µSD card from the second club OV, installed it in my OV sitting on my desk and tried to replicate these issues. but everything works fine here. I noticed CPU load shown in the XCSoar infobox is lower on my OV. All 3 OVs are the same build and same age, the only differences are no touchscreen installed on mine (removed) and no serial devices connected on my desk.
Could the (ageing) touchscreen generate "ghost" inputs overlading the processor? Any hints what to check or filter? I would prefer not having to physically disconnect the touch for testing due to a broken arm.
I installed a self compiled image (24013, still current, with @kedder OV Shell) on 2 OVs in our club. On both OVs XCSoar crashes with libinput warning messages "lagging behind by XXms, your system is too slow".
On the first OV, this happens sometimes. On the second OV it happens frequently, and also vario sound stops after a few seconds (both variod and XCSoar generated). The vario itself (sensor data and vario gauge) keep working.
I took the µSD card from the second club OV, installed it in my OV sitting on my desk and tried to replicate these issues. but everything works fine here. I noticed CPU load shown in the XCSoar infobox is lower on my OV. All 3 OVs are the same build and same age, the only differences are no touchscreen installed on mine (removed) and no serial devices connected on my desk.
Could the (ageing) touchscreen generate "ghost" inputs overlading the processor? Any hints what to check or filter? I would prefer not having to physically disconnect the touch for testing due to a broken arm.