[nvidia] nvidia-435 crashes the kernel in gpu_i2c_master_xfer

Bug #1855938 reported by leogps
24
This bug affects 3 people
Affects Status Importance Assigned to Milestone
nvidia-graphics-drivers-435 (Ubuntu)
New
Undecided
Unassigned

Bug Description

The screen freezes but the mouse can be moved. SSH access works.

This is on Legion Y545, Ubuntu 19.10
Nvidia Geforce 1660Ti
Intel 9750h

Symptoms:
This only happens when: Nvidia-Prime is selected as "on-demand"
And maybe most likely after the laptop comes out of sleep.
xserver-xorg-video-intel is the latest :: 2:2.99.917+git20190815-1

If I choose prime-select "nvidia", this never happens. Makes me believe this has to do with intel video drivers.

Error trace:
 GpuWatchdog[22171]: segfault at 0 ip 000056163556379d sp 00007fdeb6dd8480 error 6 in chrome[561631628000+7170000]
Dec 10 14:43:57 Legion-Y545 kernel: [27680.533760] Code: 48 c1 c9 03 48 81 f9 af 00 00 00 0f 87 c9 00 00 00 48 8d 15 29 61 9c fb f6 04 11 20 0f 84 b8 00 00 00 be 01 00 00 00 ff 50 30 <c7> 04 25 00 00 00 00 37 13 00 00 c6 05 11 6a a4 03 01 80 7d 8f 00

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: xorg 1:7.7+19ubuntu12
ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
Uname: Linux 5.3.0-24-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.gpus.0000.01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/0000:01:00.0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.suspend: suspend hibernate resume
.proc.driver.nvidia.suspend_depth: default modeset uvm
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module 435.21 Sun Aug 25 08:17:57 CDT 2019
 GCC version: gcc version 9.2.1 20191008 (Ubuntu 9.2.1-9ubuntu2)
ApportVersion: 2.20.11-0ubuntu8.2
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins'
Date: Tue Dec 10 15:01:38 2019
DistUpgraded: Fresh install
DistroCodename: eoan
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (prog-if 00 [VGA controller])
   Subsystem: Lenovo UHD Graphics 630 (Mobile) [17aa:3ffc]
 NVIDIA Corporation TU116M [GeForce GTX 1660 Ti Mobile] [10de:2191] (rev a1) (prog-if 00 [VGA controller])
   Subsystem: Lenovo TU116M [GeForce GTX 1660 Mobile] [17aa:3ffc]
InstallationDate: Installed on 2019-10-23 (48 days ago)
InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 048d:c100 Integrated Technology Express, Inc. ITE Device(8910)
 Bus 001 Device 002: ID 13d3:56a6 IMC Networks Integrated Camera
 Bus 001 Device 004: ID 8087:0aaa Intel Corp.
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: LENOVO 81Q6
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic root=UUID=8155cfb7-305e-41c0-9d80-fdf15d29e196 ro acpi=force
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/10/2019
dmi.bios.vendor: LENOVO
dmi.bios.version: BHCN33WW
dmi.board.asset.tag: NO Asset Tag
dmi.board.name: LNVNB161216
dmi.board.vendor: LENOVO
dmi.board.version: SDK0R32862 WIN
dmi.chassis.asset.tag: NO Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Legion Y545
dmi.modalias: dmi:bvnLENOVO:bvrBHCN33WW:bd10/10/2019:svnLENOVO:pn81Q6:pvrLegionY545:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrLegionY545:
dmi.product.family: Legion Y545
dmi.product.name: 81Q6
dmi.product.sku: LENOVO_MT_81Q6_BU_idea_FM_Legion Y545
dmi.product.version: Legion Y545
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.99-1ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.1-1ubuntu1
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

Revision history for this message
leogps (leogps) wrote :
Revision history for this message
leogps (leogps) wrote :

The error messages in the nvidia-installer.log, I got fed up with this bug and upgraded my kernel to the latest, 5.4.x but nvidia--driver-435 does not recognize that kernel, so I purged kernel 5.4.x and went back to the older version.

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Your kernel log is showing a crash in the Nvidia kernel driver which may or may not be related:
[27603.845573] gpu_i2c_master_xfer+0xf5/0x23b [i2c_nvidia_gpu]

Also, if the mouse moves then that means Xorg is still working. It's only Gnome Shell that has stopped responding.

Please start by following these instructions:

1. Look in /var/crash for crash files and if found run:
    ubuntu-bug YOURFILE.crash
Then tell us the ID of the newly-created bug.

2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine. Do you find any links to recent problems on that page? If so then please send the links to us.

3. If step 2 also failed then apply the workaround from bug 994921, reboot, reproduce the crash, and retry step 1.

Please take care to avoid attaching .crash files to bugs as we are unable to process them as file attachments. It would also be a security risk for yourself.

affects: xorg (Ubuntu) → gnome-shell (Ubuntu)
Changed in gnome-shell (Ubuntu):
status: New → Incomplete
Revision history for this message
leogps (leogps) wrote :

Hi Daniel,

The crash file I see is named "_opt_google_chrome_chrome.1000.crash". This makes sense because I remember the crash happened when I was browsing on chrome.
However, when I do `ubuntu-bug /var/crash/_opt_google_chrome_chrome.1000.crash`, a google-chrome dialog opens asking me to report it to google-chrome developers. I am not sure how to force it so as to report the crash here.
I will attach the crash file here. I might manually create a bug if needed in here with the crash file.

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

When you say the screen freezes, are you referring to the whole shell or just the web browser?

P.S. We are unable to handle Chrome crashes here because Chrome is not part of Ubuntu. See also comment #3.

Revision history for this message
leogps (leogps) wrote :

The whole shell and this happened before when I am working with other software.
The mouse moves but nothing in the screen responds to mouse or keyboard input.
I logged into the system from another laptop via shell and was able to generate the bug report.

I followed comment #3 and it said the chrome crashes cannot be sent out to ubuntu. I will enable on-demand or intel(performance mode) and see if I can reproduce the issue.

Thanks.

Revision history for this message
leogps (leogps) wrote :

Ok. This happened again today. Again, it's google chrome. I am attaching the crash dump just for reference.
I will uninstall chrome and see if this happens with other programs.
I will send a bug report to chrome.

Revision history for this message
leogps (leogps) wrote :

This happened again without google-chrome in the picture.
Opened another bug via cli: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1856092

Revision history for this message
Donjan Rodic (bryonak) wrote :
Download full text (3.1 KiB)

Experiencing the same maybe once every two weeks for about two years now.
When tabbing in or out of Chromium, the GUI freezes. The mouse cursor moves, but clicking does apparently nothing.
The keyboard works: space bar to pause/resume music if a player was focused, as well as switching to a virtual terminal. I can log in there and kill X / restart gdm3, but the GUI session is lost.

$ cat /etc/issue
Ubuntu 18.04.3 LTS

$ prime-select query
intel

Here's a heavily snipped journal (removed media key/spacenavd/network mount warnings and excess repeats) from around the crash:

[SNIP]
Jan 23 16:13:08 talas kernel: traps: compiz[17816] trap divide error ip:7fd0af9c4046 sp:7ffe928d2d20 error:0 in libstaticswitcher.so[7fd0af9b6000+1f000]
[SNIP]
Jan 23 16:13:35 talas /usr/lib/gdm3/gdm-x-session[2684]: (II) systemd-logind: got pause for 13:86
[SNIP]
Jan 23 16:13:36 talas /usr/lib/gdm3/gdm-x-session[1662]: (II) systemd-logind: got resume for 13:74
Jan 23 16:13:36 talas /usr/lib/gdm3/gdm-x-session[1662]: (II) systemd-logind: got resume for 226:0
Jan 23 16:13:36 talas /usr/lib/gdm3/gdm-x-session[1662]: (II) AIGLX: Resuming AIGLX clients after VT switch
Jan 23 16:13:36 talas /usr/lib/gdm3/gdm-x-session[1662]: (II) intel(0): switch to mode 2560x1440@60.0 on eDP1 using pipe 0, position (0, 0), rotation normal, reflection none
Jan 23 16:13:36 talas kernel: drm: not enough stolen space for compressed buffer (need 36864000 more bytes), disabling. Hint: you may be able to increase stolen memory size in the BIOS to avoid this.
[SNIP]
Jan 23 16:13:36 talas gnome-shell[1737]: g_array_unref: assertion 'array' failed
Jan 23 16:13:36 talas gnome-shell[1737]: g_array_unref: assertion 'array' failed
Jan 23 16:13:36 talas gnome-shell[1737]: g_array_unref: assertion 'array' failed
Jan 23 16:13:37 talas gnome-shell[1737]: Screen lock is locked down, not locking
[SNIP]
Jan 23 16:13:52 talas /usr/lib/gdm3/gdm-x-session[1662]: (II) AIGLX: Suspending AIGLX clients for VT switch
Jan 23 16:13:52 talas /usr/lib/gdm3/gdm-x-session[1662]: (II) systemd-logind: got pause for 13:68
[SNIP]
Jan 23 16:13:53 talas /usr/lib/gdm3/gdm-x-session[2684]: (II) systemd-logind: got resume for 13:65
Jan 23 16:13:53 talas /usr/lib/gdm3/gdm-x-session[2684]: (II) systemd-logind: got resume for 226:0
Jan 23 16:13:53 talas /usr/lib/gdm3/gdm-x-session[2684]: (II) AIGLX: Resuming AIGLX clients after VT switch
Jan 23 16:13:53 talas /usr/lib/gdm3/gdm-x-session[2684]: (II) intel(0): switch to mode 1920x1200@60.0 on DP3-1 using pipe 0, position (1200, 0), rotation left, reflection none
Jan 23 16:13:54 talas kernel: [drm] Reducing the compressed framebuffer size. This may lead to less power savings than a non-reduced-size. Try to increase stolen memory size if available in BIOS.
Jan 23 16:13:54 talas kernel: [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A FIFO underrun
Jan 23 16:13:54 talas /usr/lib/gdm3/gdm-x-session[2684]: (II) intel(0): switch to mode 1920x1200@60.0 on DP3-2 using pipe 1, position (0, 0), rotation left, reflection none
Jan 23 16:13:54 talas kernel: GpuWatchdog[22352]: segfault at 0 ip 00005586b96ff28d sp 00007f16fce386f0 error 6 in chromium-browser[5586b47ca000+8e97000]
...

Read more...

Revision history for this message
Daniel van Vugt (vanvugt) wrote : Re: [nvidia] Screen freezes and only mouse moves

Thanks but crashes in Chromium should ideally be dealt with as separate bugs. This is a Gnome Shell bug.

Please reproduce the freeze again, then reboot and immediately run:

  journalctl -b-1 > prevboot.txt

and attach the file 'prevboot.txt' here.

tags: added: nvidia
summary: - Screen freezes and only mouse moves
+ [nvidia] Screen freezes and only mouse moves
Revision history for this message
berglh (berglh) wrote :

I'm experiencing the same issue as the OP. Here is the requested 'pevboot.txt'. It's happening for me multiple times during the week - I'd say two to three times a week on Ubuntu 19.10.

gnome-shell 3.34.3-1ubuntu1~19.10.1
nvidia-driver-440 440.59-0ubuntu0~0.19.10.1
Linux 5.3.0-40-generic #32-Ubuntu SMP Fri Jan 31 20:24:34 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

Revision history for this message
Bjorn Hassler (bjohas) wrote :

I'm experiencing the same issue. Similarly, around 3 times a week on Ubuntu 19.10.

Revision history for this message
Donjan Rodic (bryonak) wrote :

@vanvugt: I haven't described a crash in Chromium. But I have switched away from Chromium, the frequency of Gnome Shell freezes it induces being one of the reasons. Attached is a journal from a freeze that happened today, with Firefox and VirtualBox open (and some filebrowser/terminal windows).

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Everyone other than the original reporter, please open your own separate bugs.

summary: - [nvidia] Screen freezes and only mouse moves
+ [nvidia] nvidia-435 crashes in gpu_i2c_master_xfer
affects: gnome-shell (Ubuntu) → nvidia-graphics-drivers-435 (Ubuntu)
summary: - [nvidia] nvidia-435 crashes in gpu_i2c_master_xfer
+ [nvidia] nvidia-435 crashes the kernel in gpu_i2c_master_xfer
Changed in nvidia-graphics-drivers-435 (Ubuntu):
status: Incomplete → New
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

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