6 Feb
2018
6 Feb
'18
2:12 p.m.
https://bugzilla.kernel.org/show_bug.cgi?id=198669
--- Comment #6 from Christian König (christian.koenig@amd.com) --- Well the issue is triggered by the driver reading nonsense values from the hardware.
E.g. we ask the hardware what the last good position on a 16k ring buffer is and get 0xffffffff as result (or something like this) which obviously can't be correct.
My patch mitigated that by clamping the value to a valid range, but if you read nonsense values from the hardware because the hardware has a loose connection and acts strange on vibrations then I basically can't guarantee for anything.
--
You are receiving this mail because:
You are watching the assignee of the bug.