https://bugzilla.kernel.org/show_bug.cgi?id=198669 --- Comment #8 from Christian König (christian.koenig@xxxxxxx) --- (In reply to roger@xxxxxxxxxxxxxxxxxxxxx from comment #7) > The original point I made in the bug report was that this bug is not about > the mechanical hardware glitch. It as about the driver being in what is > obviously a failure mode and attempting a recovery that fails and leaves the > system in unusable state. You are missing the point. The driver fails to recover because the hardware is buggy and not because there is any problem with the recovery routine. In other words we read back an impossible value from the hardware and that is why the system is failing. I mean I can handle this impossible value at this code location, but as you actually figured out by yourself it then fails at the next best location. There are simply hundreds or even thousands of locations where the assumption is that the hardware works correctly and we don't handle the case to get nonsense values. -- You are receiving this mail because: You are watching the assignee of the bug. _______________________________________________ dri-devel mailing list dri-devel@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/dri-devel
