Bug 1893931 - xorg-x11-drv-nouveau crashing Fedora 33
Summary: xorg-x11-drv-nouveau crashing Fedora 33
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: xorg-x11-drv-nouveau
Version: 33
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Adam Jackson
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-11-03 02:34 UTC by Ian Laurie
Modified: 2021-11-30 18:48 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: ---
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-11-30 18:48:18 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
dmesg log (95.44 KB, text/plain)
2020-11-03 02:34 UTC, Ian Laurie
no flags Details

Description Ian Laurie 2020-11-03 02:34:11 UTC
Created attachment 1726103 [details]
dmesg log

Description of problem:
xorg-x11-drv-nouveau is infrequently but randomly crashing Fedora on two systems of mine. This is new for Fedora 33, 32 didn't do this.

Version-Release number of selected component (if applicable):
xorg-x11-drv-nouveau-1.0.15-10.fc33.x86_64

How reproducible:
It's random, happens every few days.

Steps to Reproduce:
1. Simply use (in my case) Xfce and it randomly happens.
2.
3.

Additional info:

WARNING: CPU: 3 PID: 6074 at drivers/gpu/drm/nouveau/nvkm/engine/fifo/gk104.c:171 gk104_fifo_runlist_commit+0x11d/0x140 [nouveau]
Modules linked in: vboxnetflt(OE) vboxdrv(OE) nft_objref nf_conntrack_netbios_ns nf_conntrack_broadcast nft_fib_inet nft_fib_ipv4 nft_fib_ipv6 nft_fib nft_reject_inet nf_reject_ipv4 nf_reject_ipv6 nft_reject nft_ct nft_chain_nat nf_tables ebtable_nat ebtable_broute ip6table_nat ip6table_mangle ip6table_raw ip6table_security iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 iptable_mangle iptable_raw iptable_security rfkill ip_set nfnetlink ebtable_filter ebtables ip6table_filter ip6_tables iptable_filter sunrpc vfat fat intel_rapl_msr intel_rapl_common sb_edac x86_pkg_temp_thermal intel_powerclamp coretemp mei_hdcp kvm_intel mei_wdt iTCO_wdt intel_pmc_bxt iTCO_vendor_support kvm snd_hda_codec_realtek snd_hda_codec_generic snd_hda_codec_hdmi ledtrig_audio dcdbas dell_smm_hwmon snd_hda_intel snd_intel_dspcfg snd_hda_codec irqbypass rapl snd_hda_core intel_cstate snd_hwdep snd_seq intel_uncore snd_seq_device snd_pcm pcspkr i2c_i801 snd_timer i2c_smbus mei_me snd
 lpc_ich soundcore mei ip_tables nouveau crct10dif_pclmul video crc32_pclmul mxm_wmi crc32c_intel i2c_algo_bit drm_kms_helper ghash_clmulni_intel cec ttm drm e1000e ata_generic pata_acpi wmi uas usb_storage fuse [last unloaded: vboxnetadp]
CPU: 3 PID: 6074 Comm: Chrome_ChildIOT Tainted: G           OE     5.8.17-300.fc33.x86_64 #1
Hardware name: Dell Inc. Precision T5610/0WN7Y6, BIOS A10 06/26/2015
RIP: 0010:gk104_fifo_runlist_commit+0x11d/0x140 [nouveau]
Code: 24 08 48 8b 40 10 48 8b 78 10 4c 8b 77 50 4d 85 f6 74 34 e8 25 fa 39 d3 4c 89 f2 48 c7 c7 ca a0 57 c0 48 89 c6 e8 19 6a cb d2 <0f> 0b 41 8b 45 50 85 c0 0f 85 bf b4 07 00 48 83 c4 30 5b 5d 41 5c
RSP: 0018:ffffb18e441679f8 EFLAGS: 00010292
RAX: 000000000000001d RBX: ffff8947214b1800 RCX: ffff894527d98d18
RDX: 00000000ffffffd8 RSI: 0000000000000027 RDI: ffff894527d98d10
RBP: 0000000000002284 R08: 00000000000054e3 R09: 0000000000000003
R10: 0000000000000000 R11: 0000000000000001 R12: 0000000000000000
R13: ffff89452186e000 R14: ffff894726484860 R15: 0000000000000000
FS:  00007f2cc19a8640(0000) GS:ffff894527d80000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 000055b96d264c78 CR3: 00000002eaa0a005 CR4: 00000000001606e0
Call Trace:

Comment 1 Ian Laurie 2020-11-03 03:00:39 UTC
When this happens, I can initially ping the machine and ssh in, but when I try and reboot via ssh to unfreeze the console the system crashes and needs to be power cycled.

Comment 2 Fedora Admin user for bugzilla script actions 2021-05-07 03:01:09 UTC
This package has changed maintainer in Fedora. Reassigning to the new maintainer of this component.

Comment 3 Fedora Admin user for bugzilla script actions 2021-05-19 00:06:52 UTC
This package has changed maintainer in Fedora. Reassigning to the new maintainer of this component.

Comment 4 Ben Cotton 2021-11-04 14:00:00 UTC
This message is a reminder that Fedora 33 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 33 on 2021-11-30.
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 '33'.

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 33 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 5 Ben Cotton 2021-11-04 14:29:14 UTC
This message is a reminder that Fedora 33 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 33 on 2021-11-30.
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 '33'.

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 33 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 6 Ben Cotton 2021-11-04 15:26:58 UTC
This message is a reminder that Fedora 33 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 33 on 2021-11-30.
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 '33'.

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 33 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 7 Ben Cotton 2021-11-30 18:48:18 UTC
Fedora 33 changed to end-of-life (EOL) status on 2021-11-30. Fedora 33 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.