Bug 1667550 - NVIDIA driver: System freezes frequently, UNUSABLE
Summary: NVIDIA driver: System freezes frequently, UNUSABLE
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: gnome-shell
Version: 29
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Florian Müllner
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-01-18 19:13 UTC by cacheflood
Modified: 2020-10-17 02:23 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-11-27 23:11:39 UTC
Type: Bug
Embargoed:
cacheflood: needinfo-
cacheflood: needinfo-


Attachments (Terms of Use)

Description cacheflood 2019-01-18 19:13:09 UTC
Description of problem:

System freezes, sometimes black screen and sometimes black borders/areas on screen. Last time I was able to switch to terminal and save the dmesg file, usually system is so freeze that you can only switch the power off/on
SYSTEM IS VERY UNUSABLE NOW.

Version-Release number of selected component (if applicable):

kernel 4.19.15-300.fc29.x86_64

I Reinstalled (clean install) fedora, still same problems. Graphics card 1060TI and nvidia drivers.

How reproducible:


Steps to Reproduce:
1. Work using fedora 29, wayland, only common point what I can point is that I had web browser open (firefox, switched to chromium due crashes but still crashing)

Actual results:

[ 6466.985994] Total swap = 8309756kB
[ 6466.985994] 2083955 pages RAM
[ 6466.985995] 0 pages HighMem/MovableOnly
[ 6466.985995] 39720 pages reserved
[ 6466.985995] 0 pages cma reserved
[ 6466.985995] 0 pages hwpoisoned
[ 6473.921698] NVRM: Xid (PCI:0000:10:00): 31, Ch 00000020, intr 10000000. MMU Fault: ENGINE GRAPHICS GPCCLIENT_T1_7 faulted @ 0x1_02523000. Fault is of type FAULT_PRIV_VIOLATION ACCESS_TYPE_READ
[ 6474.293058] NVRM: Xid (PCI:0000:10:00): 31, Ch 00000030, intr 10000000. MMU Fault: ENGINE GRAPHICS GPCCLIENT_PROP_0 faulted @ 0x1_03d4e000. Fault is of type FAULT_PDE ACCESS_TYPE_WRITE
[ 6475.758629] show_signal_msg: 24 callbacks suppressed
[ 6475.758632] gnome-shell[1636]: segfault at 48 ip 00007f71ce437364 sp 00007ffc597bc798 error 4 in libmutter-cogl-3.so[7f71ce411000+69000]
[ 6475.758640] Code: ff ff ff 0f 1f 00 e8 0b e9 fd ff 48 89 ef 31 db e8 61 e3 fd ff eb 96 e8 0a e0 fd ff 66 2e 0f 1f 84 00 00 00 00 00 f3 0f 1e fa <48> 8b 47 48 c3 0f 1f 80 00 00 00 00 f3 0f 1e fa 53 48 89 fb e8 f3
[ 6477.870143] NVRM: Xid (PCI:0000:10:00): 31, Ch 00000028, intr 10000000. MMU Fault: ENGINE GRAPHICS GPCCLIENT_PROP_0 faulted @ 0x1_086a2000. Fault is of type FAULT_PDE ACCESS_TYPE_WRITE
[ 6478.022125] gnome-shell[10067]: segfault at 48 ip 00007fccaaa23364 sp 00007ffe633c3ff8 error 4 in libmutter-cogl-3.so[7fccaa9fd000+69000]
[ 6478.022133] Code: ff ff ff 0f 1f 00 e8 0b e9 fd ff 48 89 ef 31 db e8 61 e3 fd ff eb 96 e8 0a e0 fd ff 66 2e 0f 1f 84 00 00 00 00 00 f3 0f 1e fa <48> 8b 47 48 c3 0f 1f 80 00 00 00 00 f3 0f 1e fa 53 48 89 fb e8 f3
[ 6535.508881] fbcon: Taking over console
[ 6535.511816] Console: switching to colour frame buffer device 128x48
[ 6570.796379] gnome-shell[1148]: segfault at 0 ip 00007f5e83355a4b sp 00007fffaf376460 error 6 in libnvidia-glcore.so.415.25[7f5e823d4000+11de000]
[ 6570.796388] Code: 74 1f 44 8b b3 98 55 0e 00 45 39 f4 74 13 45 85 f6 74 11 44 89 e6 48 89 df e8 01 12 f6 ff 90 eb 03 45 31 f6 49 8b 55 00 89 e8 <c7> 02 04 c0 04 20 49 03 07 48 c1 e8 20 89 42 04 41 03 2f 89 6a 08
[ 6573.188445] gnome-shell[10368]: segfault at 0 ip 00007f7c123aba4b sp 00007fff614bdd40 error 6 in libnvidia-glcore.so.415.25[7f7c1142a000+11de000]
[ 6573.188452] Code: 74 1f 44 8b b3 98 55 0e 00 45 39 f4 74 13 45 85 f6 74 11 44 89 e6 48 89 df e8 01 12 f6 ff 90 eb 03 45 31 f6 49 8b 55 00 89 e8 <c7> 02 04 c0 04 20 49 03 07 48 c1 e8 20 89 42 04 41 03 2f 89 6a 08

Expected results:


Additional info:

Comment 1 cacheflood 2019-01-19 09:22:41 UTC
Saved journal containing stack traces of latest crash, please email if more information needed.

Comment 2 Owen Taylor 2019-08-08 16:07:09 UTC
I understand that this was a while ago, and you might not still be using Fedora if the system was unusable for you :-(

But some follow up questions:
 - IIRC that we don't default to Wayland for NVIDIA proprietary drivers - did you do anything to force enable that?
 - Does the X session work properly?
 - does this still happen with Fedora 30?
 - does this still happen with the latest NVIDIA drivers? If so, what driver version?

Comment 3 Ben Cotton 2019-10-31 18:58:30 UTC
This message is a reminder that Fedora 29 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 29 on 2019-11-26.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
Fedora 'version' of '29'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 29 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 4 Ben Cotton 2019-11-27 23:11:39 UTC
Fedora 29 changed to end-of-life (EOL) status on 2019-11-26. Fedora 29 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.