[nvidia] Screen freeze (GPU MMU faults reported by the kernel driver) on Quadro K620
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
| nvidia-graphics-drivers-440 (Ubuntu) |
Undecided
|
Unassigned | ||
| nvidia-graphics-drivers-450 (Ubuntu) |
Undecided
|
Unassigned |
Bug Description
Ubuntu 20.04 freezes randomly
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSign
Uname: Linux 5.4.0-45-generic x86_64
NonfreeKernelMo
.proc.driver.
.proc.driver.
.proc.driver.
.proc.driver.
.proc.driver.
.proc.driver.
.proc.driver.
NVRM version: NVIDIA UNIX x86_64 Kernel Module 450.66 Wed Aug 12 19:42:48 UTC 2020
GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2)
ApportVersion: 2.20.11-0ubuntu27.8
Architecture: amd64
BootLog: Error: [Errno 13] Erişim engellendi: '/var/log/boot.log'
CasperMD5CheckR
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Mon Sep 7 01:22:46 2020
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
DkmsStatus:
nvidia, 450.66, 5.4.0-45-generic, x86_64: installed
virtualbox, 6.1.10, 5.4.0-42-generic, x86_64: installed
virtualbox, 6.1.10, 5.4.0-45-generic, x86_64: installed
ExtraDebuggingI
GpuHangFrequency: Several times a day
GpuHangReproduc
GpuHangStarted: Since a couple weeks or more
GraphicsCard:
NVIDIA Corporation GM107GL [Quadro K620] [10de:13bb] (rev a2) (prog-if 00 [VGA controller])
Subsystem: NVIDIA Corporation GM107GL [Quadro K620] [10de:1098]
InstallationDate: Installed on 2020-04-26 (133 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
MachineType: Dell Inc. Precision Tower 3620
ProcEnviron:
TERM=xterm-
PATH=(custom, no user)
XDG_RUNTIME_
LANG=tr_TR.UTF-8
SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/25/2020
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 2.15.0
dmi.board.name: 0MWYPT
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 3
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.
dmi.product.family: Precision
dmi.product.name: Precision Tower 3620
dmi.product.sku: 06B7
dmi.sys.vendor: Dell Inc.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.101-2
version.
version.
version.
version.
version.
version.
version.
version.
Murat Gokmen (gokmen-murat) wrote : | #1 |
Daniel van Vugt (vanvugt) wrote : | #2 |
tags: | added: nvidia |
summary: |
- Xorg freeze + [nvidia] Screen freeze |
affects: | xorg (Ubuntu) → ubuntu |
Changed in ubuntu: | |
status: | New → Incomplete |
Also, next time the freeze happens, please reboot and then run:
journalctl -b-1 > prevboot.txt
and attach the resulting text file here.
Murat Gokmen (gokmen-murat) wrote : | #4 |
Thank you for your quick action. I think, I was not able to obtain an ID by step 1. However in the second step I came to the following conclusion:
And prevboot.txt file is attached as requested. Thanks.
Daniel van Vugt (vanvugt) wrote : | #5 |
Thanks. It appears your previous session crashed due to an Nvidia hardware/driver problem:
Eyl 08 14:05:52 gokmen-
Eyl 08 14:05:52 gokmen-
Eyl 08 14:05:52 gokmen-
Eyl 08 14:05:52 gokmen-
Eyl 08 14:05:52 gokmen-
Eyl 08 14:05:52 gokmen-
Eyl 08 14:05:52 gokmen-
Eyl 08 14:05:57 gokmen-
Eyl 08 14:05:58 gokmen-
Eyl 08 14:05:59 gokmen-
Eyl 08 14:05:59 gokmen-
affects: | ubuntu → nvidia-graphics-drivers-450 (Ubuntu) |
Changed in nvidia-graphics-drivers-450 (Ubuntu): | |
status: | Incomplete → New |
Daniel van Vugt (vanvugt) wrote : | #6 |
I suggest opening the 'Additional Drivers' app and trying to downgrade to driver version 440 instead of 450.
Murat Gokmen (gokmen-murat) wrote : | #7 |
Thank you for your suggestion. I was using driver version 440 when desktop freezing first started. I disabled all power savings, adjusted the nvidia gpu performance to maximum and upgraded the driver to latest stable version based on user experiences and recommendations in various forums.
I didn't paid attention to exactly after which action this problem started, it was a mistake of mine. I'm constantly updating my system. i suspect it started after a new kernel update.
I've downgraded the driver upon your suggestion. I still have all power savings disabled and gpu performance adjusted to maximum. I'll observe and update this issue in case desktop freezing continues.
Meanwhile I attached a video showing the freezing instant. Desktop freezes like this, keyboard and mouse become unresponsive, sound of playing media file continues to be heard for a while.
Launchpad Janitor (janitor) wrote : | #8 |
Status changed to 'Confirmed' because the bug affects multiple users.
Changed in nvidia-graphics-drivers-450 (Ubuntu): | |
status: | New → Confirmed |
Diego Rodriguez (chili-man) wrote : | #9 |
I just updated to the Nvidia 450 drivers today as part of the regular updates released today.
My computer froze when the Chrome and Brave browsers both segfaulted:
```
Sep 21 18:55:50 nopal /usr/lib/
Sep 21 18:55:53 nopal kernel: GpuWatchdog[12519]: segfault at 0 ip 000055f768df0182 sp 00007f910e3d3390 error 6 in brave[55f763d38
Sep 21 18:55:53 nopal kernel: Code: 89 de e8 81 a4 75 ff 80 7d c7 00 79 09 48 8b 7d b0 e8 52 2e 62 fe 41 8b 84 24 e0 00 00 00 89 45 b0 48 8d 7d b0 e8 4e 36 4e fb <c7> 04 25 00 00 00 00 37 13 00 00 48 83 c4 48 5b 41 5c 41 5d 41 5e
Sep 21 18:55:53 nopal systemd[1]: Starting Process error reports when automatic reporting is enabled...
Sep 21 18:55:57 nopal /usr/lib/
Sep 21 18:55:58 nopal whoopsie-
Sep 21 18:55:58 nopal whoopsie-
Sep 21 18:55:58 nopal whoopsie-
Sep 21 18:55:58 nopal systemd[1]: apport-
Sep 21 18:55:58 nopal systemd[1]: Finished Process error reports when automatic reporting is enabled.
Sep 21 18:55:59 nopal whoopsie[2931]: [18:55:59] Parsing /var/crash/
Sep 21 18:55:59 nopal whoopsie[2931]: [18:55:59] Uploading /var/crash/
Sep 21 18:56:00 nopal whoopsie[2931]: [18:56:00] Sent; server replied with: No error
Sep 21 18:56:00 nopal whoopsie[2931]: [18:56:00] Response code: 200
Sep 21 18:56:00 nopal whoopsie[2931]: [18:56:00] Reported OOPS ID 6197b784-
Sep 21 18:56:00 nopal systemd[1]: Starting Process error reports when automatic reporting is enabled...
Sep 21 18:56:00 nopal whoopsie-
Sep 21 18:56:00 nopal whoopsie-
Sep 21 18:56:00 nopal systemd[1]: apport-
Sep 21 18:56:00 nopal systemd[1]: Finished Process error reports when automatic reporting is enabled.
Sep 21 18:56:00 nopal /usr/lib/
Sep 21 18:56:02 nopal kernel: GpuWatchdog[10901]: segfault at 0 ip 000055bcb0e42a02 sp 00007fac3fb8a490 error 6 in chrome[
Sep 21 18:56:02 nopal kernel: Code: 89 de e8 c1 8e 6f ff 80 7d c7 00 79 09 48 8b 7d b0 e8 42 e9 6b fe 41 8b 84 24 e0 00 00 00 89 45 b0 48 8d 7d b0 e8 ce df 9c fb <c7> 04 25 00 00 00 00 37 13 00 00 48 83 c4 48 5b 41 5c 41 5d 41 5e
Sep 21 18:56:02 nopal systemd[1]: Starting Process error reports when automatic reporting is enabled...
Sep 21 18:56:06 nopal whoopsie-
Sep 21 18:56:06 nopal whoopsie-
Sep 21 18...
Daniel van Vugt (vanvugt) wrote : | #10 |
Diego,
Please open your own new bug about that.
Daniel (m4hakala) wrote : | #11 |
Bump, any solution? I'm experiencing the same issue.
Daniel van Vugt (vanvugt) wrote : | #12 |
Daniel,
Please open your own bug by running:
ubuntu-bug gnome-shell
so we can investigate your issue.
Changed in nvidia-graphics-drivers-440 (Ubuntu): | |
status: | New → Confirmed |
summary: |
- [nvidia] Screen freeze + [nvidia] Screen freeze (GPU MMU faults reported by the kernel driver) |
summary: |
- [nvidia] Screen freeze (GPU MMU faults reported by the kernel driver) + [nvidia] Screen freeze (GPU MMU faults reported by the kernel driver) on + Quadro K620 |
Thank you for taking the time to report this bug and helping to make Ubuntu better. It sounds like some part of the system has crashed. To help us find the cause of the crash please follow these steps:
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.