Random desktop freeze

Bug #1731768 reported by hamalm
56
This bug affects 11 people
Affects Status Importance Assigned to Milestone
nvidia-graphics-drivers-384 (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

Since the last update (384.90-0ubuntu0.16.04.1 to 384.90-0ubuntu0.16.04.2) I experience random desktop freezes. To recover I have to switch to tty1 and do a restart of the lightdm service. This has the consequence of closing all running applications.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: nvidia-384 384.90-0ubuntu0.16.04.2
ProcVersionSignature: Ubuntu 4.10.0-38.42~16.04.1-generic 4.10.17
Uname: Linux 4.10.0-38-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: amd64
CurrentDesktop: Unity
Date: Sun Nov 12 16:13:56 2017
InstallationDate: Installed on 2016-11-19 (358 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
SourcePackage: nvidia-graphics-drivers-384
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
hamalm (hamalmaarten) wrote :
summary: - Random screen freeze
+ Random desktop freeze
Revision history for this message
hamalm (hamalmaarten) wrote :

Below are the extracts of the kern.log and xorg.log (keep in mind this probably also includes the lightdm restart.

Kern.log
Nov 12 16:10:09 maarten-ubuntu2 kernel: [ 8871.488182] NVRM: GPU at PCI:0000:01:00: GPU-a3fbf979-a610-7e84-b9a6-eca6a0ce3abb
Nov 12 16:10:09 maarten-ubuntu2 kernel: [ 8871.488186] NVRM: Xid (PCI:0000:01:00): 8, Channel 00000010
Nov 12 16:12:37 maarten-ubuntu2 kernel: [ 9019.351195] nvidia-modeset: Freed GPU:0 (GPU-a3fbf979-a610-7e84-b9a6-eca6a0ce3abb) @ PCI:0000:01:00.0
Nov 12 16:12:46 maarten-ubuntu2 kernel: [ 9028.341747] nvidia-modeset: Allocated GPU:0 (GPU-a3fbf979-a610-7e84-b9a6-eca6a0ce3abb) @ PCI:0000:01:00.0
Nov 12 16:13:00 maarten-ubuntu2 kernel: [ 9042.076029] snd_hda_codec_hdmi hdaudioC2D0: HDMI: invalid ELD data byte 2

=================================================================================================
Xorg.log
[ 8917.679] (--) NVIDIA(GPU-0): Acer X223W Q (CRT-0): connected
[ 8917.689] (--) NVIDIA(GPU-0): Acer X223W Q (CRT-0): 400.0 MHz maximum pixel clock
[ 8917.689] (--) NVIDIA(GPU-0):
[ 8917.710] (--) NVIDIA(GPU-0): DFP-0: disconnected
[ 8917.710] (--) NVIDIA(GPU-0): DFP-0: Internal TMDS
[ 8917.710] (--) NVIDIA(GPU-0): DFP-0: 330.0 MHz maximum pixel clock
[ 8917.710] (--) NVIDIA(GPU-0):
[ 8917.729] (--) NVIDIA(GPU-0): AOC 2275W (DFP-1): connected
[ 8917.729] (--) NVIDIA(GPU-0): AOC 2275W (DFP-1): Internal TMDS
[ 8917.729] (--) NVIDIA(GPU-0): AOC 2275W (DFP-1): 340.0 MHz maximum pixel clock
[ 8917.729] (--) NVIDIA(GPU-0):
[ 8917.729] (--) NVIDIA(GPU-0): DFP-2: disconnected
[ 8917.729] (--) NVIDIA(GPU-0): DFP-2: Internal TMDS
[ 8917.729] (--) NVIDIA(GPU-0): DFP-2: 165.0 MHz maximum pixel clock
[ 8917.729] (--) NVIDIA(GPU-0):
[ 8917.729] (--) NVIDIA(GPU-0): DFP-3: disconnected
[ 8917.729] (--) NVIDIA(GPU-0): DFP-3: Internal TMDS
[ 8917.729] (--) NVIDIA(GPU-0): DFP-3: 330.0 MHz maximum pixel clock
[ 8917.729] (--) NVIDIA(GPU-0):
[ 8917.729] (--) NVIDIA(GPU-0): DFP-4: disconnected
[ 8917.729] (--) NVIDIA(GPU-0): DFP-4: Internal DisplayPort
[ 8917.729] (--) NVIDIA(GPU-0): DFP-4: 960.0 MHz maximum pixel clock
[ 8917.729] (--) NVIDIA(GPU-0):
[ 8918.133] (II) NVIDIA(0): Setting mode "DVI-I-0: nvidia-auto-select @1680x1050 +1920+0 {ViewPortIn=1680x1050, ViewPortOut=1680x1050+0+0}, HDMI-0: nvidia-auto-select @1920x1080 +0+0 {ViewPortIn=1920x1080, ViewPortOut=1920x1080+0+0}"

Revision history for this message
Benny Prijono (bennylp) wrote :

I'm having similar problem with 1080 and Ubuntu 16.04. Sometimes the desktop would freeze, but the mouse cursor still moves. Usually I'm able to Ctrl-Alt-F1 to a console then Ctrl-Alt-F7 to get back to the desktop. When I get back to the desktop, the desktop registered the mouse clicks that I did when it freezed. But then usually it would freeze again, so I had to switch to tty1 again and so on, until a point where I'm not able to switch to tty1 anymore. Sometimes the whole system freezes when I'm in tty1, in this case sometimes Ctrl-Alt-Del would do the job but often (esp. when in desktop) hard power down is required.

But sometimes the system would run for days without this problem.

Ubuntu 16.04
Zotac Mini GTX 1080
Linux 4.10.0-42-generic #46~16.04.1-Ubuntu SMP
nvidia-387

Revision history for this message
Richard Ayres (rayres) wrote :

I've also experienced a similar issue, mouse stops working and requires switch to another console, multiple times running 16.04LTS and later (I'm currently on 17.10). It is a major issue for those afflicted.

I've rolled back to NVidia 304.135 and haven't had any mouse/screen issues since.

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in nvidia-graphics-drivers-384 (Ubuntu):
status: New → Confirmed
Revision history for this message
Van Stokes, Jr. (vstokes) wrote :

Problem still persists with 18.04 running nvidia-396 drivers.
More details here https://askubuntu.com/questions/1030466/ubuntu-18-04-keeps-freezing-nvidia

Revision history for this message
Daniel Boyd (danboyd) wrote :

I'm experiencing freezes on 18.04 with the nvidia-390 drivers. Computer has frozen three times before lunch today.

Revision history for this message
Leon (lnsilcott) wrote :

I am experiencing freezes on 18.04 with NVIDIA Driver Version 390.48. I've been forced to hard power cycle my machine at least 4 times this morning alone :(.

Revision history for this message
Dante Marshal (dante-marshal) wrote :

Using NVidia driver v390.116, I'm also experiencing freezes. Mouse only moves but Mouse buttons and Keyboard don't work while freezed. Though after the freeze all actions are performed at once. For example if I hit Alt+Tab 3 times on freeze, nothing happens then suddenly windows switch 3 times.

I'm on KDE, and kwin keeps crashing / sometimes "Restarting because of a Graphics reset" as stated in the notification.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.