Thanks. This appears to be an Nvidia hardware or driver fault.
Since this is the first time I've ever seen this (other Nvidia users
don't seem to encounter the same issue) I would suggest the simplest
solution would be to change the graphics card. Otherwise you will need
to seek support from Nvidia themselves.
The recurring problems are:
Aug 28 09:42:35 greystone /usr/lib/gdm3/gdm-x-session[2279]: (WW) NVIDIA(0):
WAIT (2-S, 17, 0x00e4, 0x00003fb8, 0x00004a1c)
Aug 28 09:42:42 greystone /usr/lib/gdm3/gdm-x-session[2279]: (WW) NVIDIA(0):
WAIT (1-S, 17, 0x00e4, 0x00003fb8, 0x00004a1c)
Aug 28 09:42:45 greystone /usr/lib/gdm3/gdm-x-session[2279]: (WW) NVIDIA(0):
WAIT (2-S, 17, 0x00e4, 0x00003fb8, 0x00004a1c)
and
Aug 28 09:08:05 greystone /usr/lib/gdm3/gdm-x-session[1681]: (EE)
NVIDIA(GPU-0): WAIT (2, 8, 0x8000, 0x000009a8, 0x00001f44)
Aug 28 09:08:12 greystone /usr/lib/gdm3/gdm-x-session[1681]: (EE)
NVIDIA(GPU-0): WAIT (1, 8, 0x8000, 0x000009a8, 0x00001f44)
Aug 28 09:08:19 greystone kernel: nvidia-modeset: WARNING: GPU:0: Lost display
notification (0:0x00000000); continuing.
Aug 28 09:08:33 greystone kernel: nvidia-modeset: ERROR: GPU:0: Idling display
engine timed out: 0x0000917d:0:0:954
Aug 28 09:08:44 greystone /usr/lib/gdm3/gdm-x-session[1681]: (EE)
NVIDIA(GPU-0): WAIT (2, 8, 0x8000, 0x000009a8, 0x00001f4c)
Aug 28 09:08:51 greystone /usr/lib/gdm3/gdm-x-session[1681]: (EE)
NVIDIA(GPU-0): WAIT (1, 8, 0x8000, 0x000009a8, 0x00001f4c)
Aug 28 09:10:03 greystone kernel: nvidia-modeset: ERROR: GPU:0: Idling display
engine timed out: 0x0000917d:0:0:954
Aug 28 09:12:54 greystone rsyslogd[1394]: -- MARK --
Aug 28 09:13:04 greystone kernel: nvidia-modeset: ERROR: GPU:0: Idling display
engine timed out: 0x0000917d:0:0:954
Aug 28 09:16:05 greystone kernel: nvidia-modeset: ERROR: GPU:0: Idling display
engine timed out: 0x0000917d:0:0:954
** Changed in: gnome-shell (Ubuntu)
Status: Incomplete => Invalid
** Also affects: nvidia-graphics-drivers-450 (Ubuntu)
Importance: Undecided
Status: New
** Also affects: nvidia-graphics-drivers-440 (Ubuntu)
Importance: Undecided
Status: New
** Summary changed:
- gnome-session fails, and fails, and fails yet again
+ [nvidia] Repeated screen freezes with GeForce GT 640 (GK107)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-440 in Ubuntu.
https://bugs.launchpad.net/bugs/1892973
Title:
[nvidia] Repeated screen freezes with GeForce GT 640 (GK107)
Status in gnome-shell package in Ubuntu:
Invalid
Status in nvidia-graphics-drivers-440 package in Ubuntu:
New
Status in nvidia-graphics-drivers-450 package in Ubuntu:
New
Bug description:
Ubuntu 20.04.01, gnome-shell 3.36.4, nvidia-driver-450, nvidia-
driver-440. Both drivers expressly support the hardware. All
varieties of desktop environment (Xorg, Gnome Classic, Ubuntu)
Bug summary
Screen hangs randomly and iretrievably with the only possibility of recovery
being a a hard system reset. Sometimes this is triggered by activity
(launching or using gnome-settings; resizing a window; using Nautilus),
sometimes, not. No session lasts more than five minutes.
No combination of keystrokes will yield a terminal of any kind.
The hang also interrupts System Monitor output, so no information regarding
use of system resources is available.
Steps to reproduce
1. Install gnome-session.
2. Reboot.
3. Use graphical applications.
What happened]
The screen froze irretrievably.
Screen hangs randomly and iretrievably with the only possibility of
recovery being a a hard system reset. Sometimes this is triggered by
activity (launching or using gnome-settings; resizing a window; using
Nautilus), sometimes, not. No session lasts more than five minutes.
No combination of keystrokes will yield a terminal of any kind.
The hang also interrupts System Monitor output, so no information
regarding use of system resources is available.
A hard system reset and consequent reboot yields a variety of
outcomes. Sometimes, a normal gdm login. Sometimes, a black screen
with an inverted-black mouse cursor/pointer/arrow that moves.
Sometimes an entirely black screen. Sometimes, not even a hard system
reset is sufficient and the system has to be booted into recovery
mode, the existing driver removed, and another installed, before
rebooting again.
With nvidia-driver-440, fewer hangs but the monitor resolution can't be set
to its capacity.
I don't get it. GNOME hangs have been extensively documented for ten years.
The drivers expressly support the hardware. This package is part of an Ubuntu
LTS release. Is gnome-session intended to be serious, functional, production
software subjected to rigorous and competent quality control? This is a
serious question because I have a business to run and can't be sucked down some
random technical rabbit hole just to do daily work.
Is GNOME just a cute code project intended as a resume line for people
looking for real work?
What kind of quality control processes are in place that allow ancient
failures, extensively reported, to persist?
Is anyone at GNOME able and willing to put on their big-boy pants to
get a reliable package suitable for production deployments, released?
The command
cat /var/log/syslog | grep gnome-session
reveals fundamental errors in implementing systemd syntax and
references/calls to nonexistent binaries. See the gnome-sesion units
in /usr/lib/systemd/user. Maybe getting this right would be a first
step to helping the developers understand the environment better.
Please see man systemd.
Source is, astonishingly, a hybrid of C and Javascript, which
doubtless presents a QC nightmare. Has anyone given this any thought?
What does it take to get this package to work today?
- What is the procedure? What commands must be run?
- Why doesn't GNOME simply include these commands in a script, just to make
it easier? Does anyone there know how?
- Why doesn't GNOME simply compile these commands into the package so it
works in the first place?
- Will a different graphics card matter?
- Which one?
- Why, if the drivers support the existing hardware, according to the
documentation if not the function?
Can this package be made to work today?
If not, will this package be ready for production use in the next
Ubuntu release (i.e., 20.04.02)?
If not, what alternatives exist for production use?
These are all serious questions. It is astonishing that this package has
been released to the public. It getting out the door poses an existential
reputational threat to the GNOME project.
Any help in getting this package to work would be most gratefully appreciated.
What did you expect to happen
I expected the screen not to freeze.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1892973/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
