> There were various commits which went in up to v4.16.9 upstream which > should adress the issues. There is a 4.16.12-1 upload pending for sid, > can you check if this will fix your issue?
Hi, just reporting back that after 4.16.12-1 arrived to testing few days ago i booted the new version this morning, and the error still hasn't shown up, with the same workload that was triggering it before. At least for now... maybe fixed? Thank you. -- free as in freedom, not free beer
