[Expired for linux (Ubuntu) because there has been no activity for 60
days.]
** Changed in: linux (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1526657
Below is the information from Xorg.O.log.old (about the described lock,
on Nov. 21st):
[141735.156] nouveau_exa_download_from_screen:295 - falling back to memcpy
ignores tiling
[141735.188] (EE)
[141735.188] (EE) Backtrace:
[141735.198] (EE) 0: /usr/bin/Xorg (xorg_backtrace+0x56)
Well, I am not a strong graphical software user. Most of the time I am
using gvim to edit program files. One of the times I had the problem I
captured dmesg. Below you will see what I got (through ssh, I guess).
[Sat Nov 21 12:24:38 2015] nouveau E[ PFIFO][:01:00.0] read fault at
It would be nice to get a /var/log/Xorg.log capture, just to show that
it is really the same thing.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1526657
Title:
desktop freeze, htop shows kernel
>>So, my conclusion is that the problem happens exactly when the screen
saver takes control and the monitor turns off.
For me it was any sporadically associated with any graphics-related
operation, eg zooming in google earth, or opening a 3D molecule viewer.
I have swapped out the NVS 310
I should also mention that I have frequently updated both Debian and
Ubuntu and that I have seen the same problem with all the updates.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1526657
Title:
I have exactly the same problem in both an Ubuntu 14.04 that I use at
work and a Debian Jessie that I use at home, and the software is up to
date. Both systems have a "VGA compatible controller: NVIDIA Corporation
GF119 [NVS 310] (rev a1)" and two monitors. After the problem shows up,
I can login
Did this issue start happening after an update/upgrade? Was there a
prior kernel version where you were not having this particular problem?
>>Its a new machine.
>>I located another machine with exact same hardware, ubuntu build and
drivers which is manifesting no problems: therefore this is a
Did this issue start happening after an update/upgrade? Was there a
prior kernel version where you were not having this particular problem?
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.4
