So the change of cache mode for the VESA frambuffer driver is at least not the only offender. It might even have no impact at all but I would not be 100% sure, yet. Normally this sounds like something that needs a bisect (building various kernels at stages between 3.16.0-37 and 38 which you would have to try and report whether they work or not). Though that is quite tedious.
Some things that you might try before: - try the latest 3.16 (*-87*) with the mtrr option - try to switch to a text console (ctrl-alt-f1) and try to cause some load (scp or wget files, ssh,...) - if you got another Linux machine, try to install openssh-server on the laptop and attempt to ssh into the laptop when it appears frozen (sometimes it is just the graphical frontend and keyboard/mouse events that lock up). The other question would be whether it happens also if you just log in an let it sit idle (provided the screen saver does not kick in) or does it only happen if you do something (and if that is true, would this be things that cause network activity or rather local activity)? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1561902 Title: Total system freeze after 3.16.0-38.52 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-lts-utopic/+bug/1561902/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
