I just swapped my old gtx750 for a new gtx1060
Before all was good, but now there are issues; to reproduce:
Start the system normally
Let unigine valley free demo run for a couple of minutes
Put the system into hibernation
Wake up the system
Let unigine valley run a couple of minutes
After a while, the system starts to lag; even the mouse is jerky.
In the kernel logs, an unstoppable flood/LOOP (SEE A PATTERN) of the following will happen:
Process of elimination. A number of display function issues involve *bad Display Port cables which can now be ruled out in your case. BTW. DVD-D SL or DVD-D DL? Have you tried a different cable or electrical contact cleaner on the one you have?
Does your Belinea monitor have any sort of deep sleep feature? If so, have you tried turning it off?
@sandipt, I’m getting the xid 56 error on resume from hibernate too after upgrading from 730GT to gtx 1050Ti. It mostly happens when the hibernate was over an hour.
The system itself is very stable even when running something like Unigine Heaven-4.0 for hours.
The only issue is with hibernate. I am booting in legacy mode because I didn’t want to use uefi.
…so do you still experience slowness when resume, with jerky mouse too?
I’ve still to try newer drivers, i’m stuck with 375.26 which have the problem, but i tought it was fixed, because in the following changelogs:
i read:
“Fixed a bug that could cause a system hang when resuming from suspend with some GPUs.”
But if it is still not fixed, then i ask some light about the issue, what’s the state of this bug sandipt? it is almost an year and i just noticed that (on 375.26) it happens even when waking up from suspend to ram.
I don’t know, nor i can see any evidence in this thread, that the problem may depend on the use of UEFI.
Also, i asked if you experienced the very same:
Anyway, i just found that switching VT to a console and back to X, solves the problem for the session, but it has to be done after the problem arises, so here is an hacky workaround that works for me.
Needs to run has root.
It checks for Xid errors in the last line in the kernel buffer and if it founds that it matches the error expected, it switches vt and then back.
The screen will blank for a while, but after that, the graphic will become smooth again; it seems to be needed just one time per resume.
Just start it at boot and forget it, it has almost 0 cpu use.
#!/bin/bash
while true ; do
#EDIT NVRM string as it appears in your log.
if dmesg|tail -n 1|grep "NVRM: Xid (PCI:0000:01:00): 56, CMDre" ; then
chvt 1 #EDIT as your need
chvt 7 #EDIT as your need
sleep 1
echo koko_switch_vt_done > /dev/kmsg
#if the slowness persists, give user some time to shut down.
sleep 60
fi
sleep 1
#echo recheck
done