Lines Matching refs:issue

14 section equips users to determine if a specific issue was caused by the display
44 issue. If you do not see that line, something else might have failed before
46 display issue.
90 the issue; if you suspect that the display is not part of the problem and your
117 If you can boot your system with the DC disabled and still see the issue, it
120 issue. In some scenarios, disabling DC is impossible since it might be
121 necessary to use the display component to reproduce the issue (e.g., play a
136 disables DPM switches. If forcing DPM levels high does not fix the issue, it
137 is less likely that the issue is related to power management. If the issue
140 display side, if the power increase fixes the issue, it is worth debugging the
150 this type of issue, there is a considerable chance that you have a userspace
153 of the display parameters, but the userspace might also cause this issue. One
157 that the issue is likely on the the driver side. If you can still see the
158 problem in the data collected, it is an issue that probably happened during
175 initialized version of `dc_debug_options` to see if the issue gets fixed. Along
271 an issue arises is some generic timeout error. So, to get more relevant
296 Lastly, after you are able to reproduce the issue you are trying to debug,
303 enabling the relevant bits in the mask before reproducing the issue and