Comment # 14
on bug 79980
from Andy Furniss
(In reply to comment #10) > (In reply to comment #9) > > (In reply to comment #8) > > > > optimize SI VM handling + use lower_32_bits where appropriate reverted - the > > > latter just so I could revert the former. > > > > > > I'll see if I am stable over the next couple of days like this. > > > > I am stable so far with the above reverted. > > Spoke too soon, I just locked. Wasn't quite the same as before in that > screen stayed on displaying normal rather that off/on + junk. > > Wasn't doing anything GPU related (accepting I always am with glamor), was > doing a big compile, so memory pressure I guess. > > Also just add to the mix, after thinking I was stable yesterday I upgraded > gcc and updated llvm and mesa so they were different in several ways, though > I haven't rebuilt kernel. I got another lock last thing, this one was "typical" happened when closing seamonkey, this is the third time closing it has locked. Of course it doesn't do it if I try. I must be using gl someway/sometimes, as the last thing I see is the xterm from where it was started and there is a mesa message about default setting for s3tc being overridden by env (and that's not by me - I don't have drirc anywhere). I think this is going to be a pain to find - I just tried reset --hard onto add large PTE support for NI, SI and CIK v5 that failed to resume from mem 1st try, though it wasn't locked. just corrupt (mouse cursor large block of junk, fluxbox desktop black, but toolbar still visible) so maybe a different issue fixed by a later commit. I could SysRq - the log was normal.
You are receiving this mail because:
- You are the assignee for the bug.
_______________________________________________ dri-devel mailing list dri-devel@xxxxxxxxxxxxxxxxxxxxx http://lists.freedesktop.org/mailman/listinfo/dri-devel
