drm_calc_timestamping_constants error
Dell Precision M4800 laptop
nVidia GK107GLM [Quadro K1100M]
openSUSE Tumbleweed
libdrm_nouveau2 2.4.101-2.1
Once it starts happening, the following line is printed to the journald log:
[drm:drm_calc_timestamping_constants [drm]] ERROR crtc 50: Can't calculate constants, dotclock = 0!
It's a continuous stream as long as the mouse is moving. After just a few hours there are thousands of these lines in the log.
There is a repeatable scenario:
- fresh boot, all is quiet, do some stuff and then wait for the power save timer to trigger sleep.
- wait a while, resume from sleep, errors begin quickly.
Sometimes, once the errors begin, a logout/login sequence will stop them. Usually I have many applications/files open at the time of suspend. The error behavior is identical whether all those applications/files are open or if none are (just the plasma desktop).
One other anomaly I have observed: at resume after suspend the timestamp on entries in the kernel log are wrong. Timestamps on the same entries in the journald log are correct. In the kernel log, the timestamp for resume is the same as for suspend even when many hours have elapsed. That pattern continues until reboot. The kernel log seem to correlate to uptime not elapsed time.
Log file attached shows fresh boot, sleep, resume, errors.