Hi,
here is my problem, specific to one of the variants of gprimeltexx. It runs postmarketos, alpine’s shrinked version of linux, for mobile/embedded devices.
However, even if the mainline works “almost” well (as torch is [1]), the zinitix component, as i guess the touchscreen, have a real bug on it.
often, after few hours of uptime, the zinitix touchscreen get unavailable. So the touchscreen doesnt works. I have added a modprobe -r zinitix & modprobe zinitix in the crontab. Wonderful : it almost fix the problem.
Almost.
Since this, except that i dont have to do a salvage reboot/shutdown (when the touchscreen was “frozen”, only a 15secs hold of powerbutton to salvage reboot it was possible), the zinitix process still kills the GUI. Phosh get crashed around every 15mins. It just takes 2mins to get interface working back, but it’s still annoying.
so as i asked how to debug it, here is the reply :
I’m trying to say that fixing your kernel first looks like a good move as it would fix your device freeze and (likely) avoid the GTK3 crash.
I’d start as usual:enable ssh access (so you can recover the device)
enable maximum debugging in the driver
disable the cronjob
see if you can catch anything when the screen stops functioning
report that to the team maintaining your device kernelThis can also be a problem in device tree (e.g. regulators) but I’d just start somewhere.
You want the dev_dbg in the driver to trigger. See e.g. Dynamic debug — The Linux Kernel documentation but that is out of scope for this channel and belongs to where your devices kernel is being discussed.
i admit im totally lost on that issue…