[nouveau] System unresponsive to keyboard and mouse clicks when changing screen background

[Lester Potter]

Right click on screen background and choose settings.
Then click a different background.
System becomes unresponsive to keyboard input and mouse clicks.
System returns to responsiveness after about 10 minutes.

Description: Ubuntu 20.04 LTS
Release: 20.04

CPU: 8-Core AMD Ryzen 7 1700 (-MT MCP-) speed: 2562 MHz
Kernel: 5.4.0-37-generic x86_64 Up: 48m Mem: 2370.8/32114.5 MiB (7.4%)
Storage: 1.82 TiB (5.5% used) Procs: 337 Shell: bash 5.0.16 inxi: 3.0.38

Expected behavior:
Changing the background happens immediately and system remains responsive to input.

What happened:
System did not change the background immediately and became unresponsive to keyboard and mouse input for 10 minutes at which point the background changed to the selected one and responsiveness returned.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gnome-control-center 1:3.36.2-0ubuntu1
ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41
Uname: Linux 5.4.0-37-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.3
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Fri Jun 26 15:50:44 2020
ExecutablePath: /usr/bin/gnome-control-center
InstallationDate: Installed on 2020-06-13 (13 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: gnome-control-center
UpgradeStatus: No upgrade log present (probably fresh install)

[Daniel van Vugt (vanvugt)]

Please:

1. Run this command:

   gsettings list-recursively org.gnome.shell > settings.txt

   and attach the resulting text file here.

2. Open a Terminal window and run 'top'. Now reproduce the problem again. While the problem is happening does 'top' report any process using very high CPU?

3. Follow these instructions to check for crashes: https://wiki.ubuntu.com/Bugs/Responses#Missing_a_crash_report_or_having_a_.crash_attachment

[Lester Potter (lesterpotter)]

In response to the last comment...
1. Run this command:

   gsettings list-recursively org.gnome.shell > settings.txt

   and attach the resulting text file here.

See attached

2. Open a Terminal window and run 'top'. Now reproduce the problem
again. While the problem is happening does 'top' report any process
using very high CPU?

All windows freeze. Only the cursor moves. "top" frozen.

3. Follow these instructions to check for crashes:
https://wiki.ubuntu.com/Bugs/Responses#Missing_a_crash_report_or_having_a_.crash_attachment

/var/crash is empty
/var/lib/whoopsie/whoopsie-id ... https://errors.ubuntu.com/user/ID reports that "No errors have been reported from this system"
Applied work around for bug 994921 and got same results (no crash)

### Additional Information ###
1. In addition to becoming un-responsive, window also freeze ("top" stops reporting while hung, Graphic applications like performance monitor also hang/freeze).
2. The "Settings" app shows a preview, when launched, it shows the current desktop. When selecting a different background, sometimes the preview will update (but freezes before updating the desktop), and sometimes the preview will not update.
3. After reboot, timing the hang, it takes about 16 minutes to become responsive again. However, a second settings change took as little as 90 seconds. Not enough evaluation has been done to determine if other factors are contributing to the timings (during the 90 second timing, I had tcpdump running and I pinged the machine from another machine during the hang).
4. After reboot, running tcpdump during the hang, viewing with wireshark after responsiveness returns, I find that there is some normal looking network traffice, including connectivity checks outbound and normal responses received.
###

[Daniel van Vugt (vanvugt)]

If the mouse cursor still moves then that means Xorg is still running and it was gnome-shell frozen. But we need to find out if it was just frozen or the result of a crash. Please use this command:

  pidof gnome-shell

to check the process ID before and after the freeze and tell us if it changes.

Also immediately after the next freeze please run:

  journalctl -b0 > post-freeze.txt

and attach the resulting text file here.

[Lester Potter (lesterpotter)]

"pidof gnome-shell" reports the same PID before and after.

On Mon, Jun 29, 2020 at 10:35 PM Daniel van Vugt <email address hidden>
wrote:

> If the mouse cursor still moves then that means Xorg is still running
> and it was gnome-shell frozen. But we need to find out if it was just
> frozen or the result of a crash. Please use this command:
>
> pidof gnome-shell
>
> to check the process ID before and after the freeze and tell us if it
> changes.
>
> Also immediately after the next freeze please run:
>
> journalctl -b0 > post-freeze.txt
>
> and attach the resulting text file here.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1885330
>
> Title:
> System unresponsive to keyboard and mouse clicks when changing screen
> background
>
> Status in gnome-shell package in Ubuntu:
> Incomplete
>
> Bug description:
> Right click on screen background and choose settings.
> Then click a different background.
> System becomes unresponsive to keyboard input and mouse clicks.
> System returns to responsiveness after about 10 minutes.
>
> Description: Ubuntu 20.04 LTS
> Release: 20.04
>
> CPU: 8-Core AMD Ryzen 7 1700 (-MT MCP-) speed: 2562 MHz
> Kernel: 5.4.0-37-generic x86_64 Up: 48m Mem: 2370.8/32114.5 MiB (7.4%)
> Storage: 1.82 TiB (5.5% used) Procs: 337 Shell: bash 5.0.16 inxi: 3.0.38
>
> Expected behavior:
> Changing the background happens immediately and system remains
> responsive to input.
>
> What happened:
> System did not change the background immediately and became unresponsive
> to keyboard and mouse input for 10 minutes at which point the background
> changed to the selected one and responsiveness returned.
>
> ProblemType: Bug
> DistroRelease: Ubuntu 20.04
> Package: gnome-control-center 1:3.36.2-0ubuntu1
> ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41
> Uname: Linux 5.4.0-37-generic x86_64
> ApportVersion: 2.20.11-0ubuntu27.3
> Architecture: amd64
> CasperMD5CheckResult: skip
> CurrentDesktop: ubuntu:GNOME
> Date: Fri Jun 26 15:50:44 2020
> ExecutablePath: /usr/bin/gnome-control-center
> InstallationDate: Installed on 2020-06-13 (13 days ago)
> InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64
> (20200423)
> ProcEnviron:
> PATH=(custom, no user)
> XDG_RUNTIME_DIR=<set>
> LANG=en_US.UTF-8
> SHELL=/bin/bash
> SourcePackage: gnome-control-center
> UpgradeStatus: No upgrade log present (probably fresh install)
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1885330/+subscriptions
>

[Lester Potter (lesterpotter)]

Here is the journalctl report.
Line 3144 is immediately prior to hanging GNOME.

[Lester Potter (lesterpotter)]

Additional info...

Upon invoking the freeze, Ctl-Alt-F3 sometimes brings up a terminal session on tty3.
If it does, Ctl-Alt-F2 will switch back to GNOME which will remain frozen for a while, but will allow switching back and forth with the Ctl-Alt-F# keys.

Running "top" on tty3 shows no processes taking much %CPU.
Observed a message "[TTM] Buffer eviction failed" 3 times (on tty3) while waiting for unfreeze.

Sometimes, Ctl-Alt-F3 is also unresponsive upon freeze, but did eventually switch to tty3 (after a about 20 seconds). This hasn't been tested much yet.

[Daniel van Vugt (vanvugt)]

Thanks. It looks most likely the freeze is a kernel bug in the 'nouveau' driver:

Jun 30 09:41:31 My-System kernel: [TTM] Buffer eviction failed
Jun 30 09:44:35 My-System kernel: ------------[ cut here ]------------
Jun 30 09:44:35 My-System kernel: Trying to vfree() bad address (00000000ba0a4082)
Jun 30 09:44:35 My-System kernel: WARNING: CPU: 0 PID: 1933 at mm/vmalloc.c:2237 __vunmap+0x1ec/0x210
Jun 30 09:44:35 My-System kernel: Modules linked in: vmw_vsock_vmci_transport vsock vmw_vmci binfmt_misc edac_mce_amd kvm_amd kvm snd_hda_codec_realtek snd_hda_codec_generic ledtrig_audio nls_iso8859_1 snd_hda_intel snd_intel_dspcfg snd_hda_codec snd_hda_core snd_hwdep snd_pcm crct10dif_pclmul ghash_clmulni_intel snd_seq_midi snd_seq_midi_event snd_rawmidi nouveau snd_seq snd_seq_device snd_timer eeepc_wmi aesni_intel asus_wmi mxm_wmi sparse_keymap ttm crypto_simd joydev input_leds cryptd glue_helper video wmi_bmof snd drm_kms_helper fb_sys_fops syscopyarea sysfillrect sysimgblt soundcore k10temp ccp mac_hid sch_fq_codel parport_pc ppdev lp parport drm dm_crypt ip_tables x_tables autofs4 hid_microsoft ff_memless hid_generic usbhid hid crc32_pclmul igb i2c_piix4 i2c_algo_bit ahci dca libahci wmi gpio_amdpt gpio_generic
Jun 30 09:44:35 My-System kernel: CPU: 0 PID: 1933 Comm: gnome-shell Not tainted 5.4.0-39-generic #43-Ubuntu
Jun 30 09:44:35 My-System kernel: Hardware name: System manufacturer System Product Name/ROG STRIX B350-F GAMING, BIOS 3401 12/04/2017
Jun 30 09:44:35 My-System kernel: RIP: 0010:__vunmap+0x1ec/0x210
Jun 30 09:44:35 My-System kernel: Code: 20 e8 28 cc fc ff eb d2 c3 31 d2 31 f6 48 c7 c7 ff ff ff ff e8 d5 fc ff ff eb bf 48 89 fe 48 c7 c7 d8 f6 37 9d e8 ef 97 e2 ff <0f> 0b eb b4 4c 89 ee 48 c7 c7 00 f7 37 9d e8 dc 97 e2 ff 0f 0b eb
Jun 30 09:44:35 My-System kernel: RSP: 0018:ffffc41903d639b8 EFLAGS: 00010286
Jun 30 09:44:35 My-System kernel: RAX: 0000000000000000 RBX: ffffa0d8fb2b0f00 RCX: 0000000000000006
Jun 30 09:44:35 My-System kernel: RDX: 0000000000000007 RSI: 0000000000000082 RDI: ffffa0d93ec178c0
Jun 30 09:44:35 My-System kernel: RBP: ffffc41903d639e0 R08: 000000000000047a R09: 0000000000000004
Jun 30 09:44:35 My-System kernel: R10: 0000000000000000 R11: 0000000000000001 R12: 0000000000000f60
Jun 30 09:44:35 My-System kernel: R13: ffffa0d9055d4f60 R14: 00000126c1557d86 R15: ffffc41903d63b08
Jun 30 09:44:35 My-System kernel: FS: 00007f89abd83cc0(0000) GS:ffffa0d93ec00000(0000) knlGS:0000000000000000
Jun 30 09:44:35 My-System kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Jun 30 09:44:35 My-System kernel: CR2: 000055a5ddc1aff8 CR3: 00000007a9666000 CR4: 00000000003406f0
Jun 30 09:44:35 My-System kernel: Call Trace:
Jun 30 09:44:35 My-System kernel: vunmap+0x30/0x40
Jun 30 09:44:35 My-System kernel: nvkm_umem_unmap+0x4e/0x70 [nouveau]
Jun 30 09:44:35 My-System kernel: nvkm_object_dtor+0xa1/0x110 [nouveau]
Jun 30 09:44:35 My-System kernel: nvkm_object_del+0x25/0x90 [nouveau]
Jun 30 09:44:35 My-System kernel: nvkm_ioctl_del+0x3c/0x60 [nouveau]
Jun 30 09:44:35 My-System kernel: nvkm_ioctl+0xf0/0x190 [nouveau]
Jun 30 09:44:35 My-System kernel: nvkm_client_ioctl+0x12/0x20 [nouveau]
Jun 30 09:44:35 My-System kern...

[Daniel van Vugt (vanvugt)]

Please open the 'Additional Drivers' app and try installing a graphics driver from Nvidia instead.

[Lester Potter (lesterpotter)]

Switched to the NVIDIA proprietary driver and the problem is solved.
This can be closed.

On Tue, Jun 30, 2020 at 10:10 PM Daniel van Vugt <email address hidden>
wrote:

> Please open the 'Additional Drivers' app and try installing a graphics
> driver from Nvidia instead.
>
> ** Summary changed:
>
> - System unresponsive to keyboard and mouse clicks when changing screen
> background
> + [nouveau] System unresponsive to keyboard and mouse clicks when changing
> screen background
>
> ** Package changed: gnome-shell (Ubuntu) => linux (Ubuntu)
>
> ** Tags added: nouveau
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1885330
>
> Title:
> [nouveau] System unresponsive to keyboard and mouse clicks when
> changing screen background
>
> Status in linux package in Ubuntu:
> Incomplete
>
> Bug description:
> Right click on screen background and choose settings.
> Then click a different background.
> System becomes unresponsive to keyboard input and mouse clicks.
> System returns to responsiveness after about 10 minutes.
>
> Description: Ubuntu 20.04 LTS
> Release: 20.04
>
> CPU: 8-Core AMD Ryzen 7 1700 (-MT MCP-) speed: 2562 MHz
> Kernel: 5.4.0-37-generic x86_64 Up: 48m Mem: 2370.8/32114.5 MiB (7.4%)
> Storage: 1.82 TiB (5.5% used) Procs: 337 Shell: bash 5.0.16 inxi: 3.0.38
>
> Expected behavior:
> Changing the background happens immediately and system remains
> responsive to input.
>
> What happened:
> System did not change the background immediately and became unresponsive
> to keyboard and mouse input for 10 minutes at which point the background
> changed to the selected one and responsiveness returned.
>
> ProblemType: Bug
> DistroRelease: Ubuntu 20.04
> Package: gnome-control-center 1:3.36.2-0ubuntu1
> ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41
> Uname: Linux 5.4.0-37-generic x86_64
> ApportVersion: 2.20.11-0ubuntu27.3
> Architecture: amd64
> CasperMD5CheckResult: skip
> CurrentDesktop: ubuntu:GNOME
> Date: Fri Jun 26 15:50:44 2020
> ExecutablePath: /usr/bin/gnome-control-center
> InstallationDate: Installed on 2020-06-13 (13 days ago)
> InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64
> (20200423)
> ProcEnviron:
> PATH=(custom, no user)
> XDG_RUNTIME_DIR=<set>
> LANG=en_US.UTF-8
> SHELL=/bin/bash
> SourcePackage: gnome-control-center
> UpgradeStatus: No upgrade log present (probably fresh install)
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1885330/+subscriptions
>

[Daniel van Vugt (vanvugt)]

Great!

If you don't want/need to discuss the original issue then we can close this as 'Won't Fix'.

[Lester Potter (lesterpotter)]

My only concern is whether there will be issues with updates and upgrades
to my box in the future.
Other than that, I am fine with "won't fix".

On Tue, Jun 30, 2020 at 11:10 PM Daniel van Vugt <email address hidden>
wrote:

> Great!
>
> If you don't want/need to discuss the original issue then we can close
> this as 'Won't Fix'.
>
>
> ** Changed in: linux (Ubuntu)
> Status: Incomplete => New
>
> ** Changed in: linux (Ubuntu)
> Status: New => Won't Fix
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1885330
>
> Title:
> [nouveau] System unresponsive to keyboard and mouse clicks when
> changing screen background
>
> Status in linux package in Ubuntu:
> Won't Fix
>
> Bug description:
> Right click on screen background and choose settings.
> Then click a different background.
> System becomes unresponsive to keyboard input and mouse clicks.
> System returns to responsiveness after about 10 minutes.
>
> Description: Ubuntu 20.04 LTS
> Release: 20.04
>
> CPU: 8-Core AMD Ryzen 7 1700 (-MT MCP-) speed: 2562 MHz
> Kernel: 5.4.0-37-generic x86_64 Up: 48m Mem: 2370.8/32114.5 MiB (7.4%)
> Storage: 1.82 TiB (5.5% used) Procs: 337 Shell: bash 5.0.16 inxi: 3.0.38
>
> Expected behavior:
> Changing the background happens immediately and system remains
> responsive to input.
>
> What happened:
> System did not change the background immediately and became unresponsive
> to keyboard and mouse input for 10 minutes at which point the background
> changed to the selected one and responsiveness returned.
>
> ProblemType: Bug
> DistroRelease: Ubuntu 20.04
> Package: gnome-control-center 1:3.36.2-0ubuntu1
> ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41
> Uname: Linux 5.4.0-37-generic x86_64
> ApportVersion: 2.20.11-0ubuntu27.3
> Architecture: amd64
> CasperMD5CheckResult: skip
> CurrentDesktop: ubuntu:GNOME
> Date: Fri Jun 26 15:50:44 2020
> ExecutablePath: /usr/bin/gnome-control-center
> InstallationDate: Installed on 2020-06-13 (13 days ago)
> InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64
> (20200423)
> ProcEnviron:
> PATH=(custom, no user)
> XDG_RUNTIME_DIR=<set>
> LANG=en_US.UTF-8
> SHELL=/bin/bash
> SourcePackage: gnome-control-center
> UpgradeStatus: No upgrade log present (probably fresh install)
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1885330/+subscriptions
>

[Daniel van Vugt (vanvugt)]

We can also reopen this and leave it open. But in an open state you might be asked by kernel engineers to test various things. If you're no longer using the offending driver then that could be annoying. It's up to you.