Bug 1592328 - [abrt] gf100_gr_init_ctxctl: WARNING: CPU: 0 PID: 5574 at drivers/gpu/drm/nouveau/nvkm/engine/gr/ctxgf100.c:1352 gf100_grctx_generate+0x617/0x6a0 [nouveau] [nouveau]
Summary: [abrt] gf100_gr_init_ctxctl: WARNING: CPU: 0 PID: 5574 at drivers/gpu/drm/nou...
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: xorg-x11-drv-nouveau
Version: 28
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Ben Skeggs
QA Contact: Fedora Extras Quality Assurance
URL: https://retrace.fedoraproject.org/faf...
Whiteboard: abrt_hash:423a0a7a2f7d0ecd7956ad717d8...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-06-18 12:43 UTC by Kévin Clément
Modified: 2019-05-28 20:41 UTC (History)
5 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2019-05-28 20:41:47 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: dmesg (245.84 KB, text/plain)
2018-06-18 12:43 UTC, Kévin Clément
no flags Details

Description Kévin Clément 2018-06-18 12:43:47 UTC
Description of problem:
I have a fresh install of fedora without any extension. This happens randomly at booting or later during the use of my laptop.
My computer is equiped with an nvidia graphic card.

Additional info:
reporter:       libreport-2.9.5
WARNING: CPU: 0 PID: 5574 at drivers/gpu/drm/nouveau/nvkm/engine/gr/ctxgf100.c:1352 gf100_grctx_generate+0x617/0x6a0 [nouveau]
Modules linked in: fuse rfcomm ccm nf_conntrack_netbios_ns nf_conntrack_broadcast xt_CT ip6t_rpfilter ip6t_REJECT nf_reject_ipv6 xt_conntrack ip_set nfnetlink ebtable_nat ebtable_broute bridge stp llc ip6table_nat nf_conntrack_ipv6 nf_defrag_ipv6 nf_nat_ipv6 ip6table_mangle ip6table_raw devlink ip6table_security iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack libcrc32c iptable_mangle iptable_raw iptable_security ebtable_filter ebtables ip6table_filter ip6_tables cmac bnep sunrpc vfat fat arc4 intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel iwlmvm snd_soc_skl kvm mac80211 joydev snd_soc_skl_ipc snd_hda_ext_core spi_pxa2xx_platform hid_multitouch snd_soc_sst_dsp iTCO_wdt snd_soc_sst_ipc iTCO_vendor_support snd_soc_acpi irqbypass snd_soc_core
 crct10dif_pclmul snd_hda_codec_hdmi crc32_pclmul iwlwifi snd_hda_codec_generic snd_compress ghash_clmulni_intel intel_cstate intel_uncore snd_pcm_dmaengine cfg80211 intel_rapl_perf ac97_bus snd_hda_intel uvcvideo btusb snd_hda_codec videobuf2_vmalloc videobuf2_memops btrtl videobuf2_v4l2 snd_hda_core snd_hwdep btbcm snd_seq btintel videobuf2_common asus_nb_wmi asus_wmi snd_seq_device sparse_keymap bluetooth wmi_bmof snd_pcm videodev snd_timer snd ecdh_generic i2c_i801 media rfkill soundcore mei_me shpchp mei processor_thermal_device idma64 int340x_thermal_zone intel_lpss_pci intel_soc_dts_iosf intel_lpss intel_pch_thermal tpm_crb tpm_tis tpm_tis_core tpm int3400_thermal asus_wireless acpi_thermal_rel acpi_pad uas usb_storage nouveau i915 mxm_wmi ttm i2c_algo_bit drm_kms_helper crc32c_intel
 drm serio_raw i2c_hid video wmi
CPU: 0 PID: 5574 Comm: kworker/0:1 Not tainted 4.16.3-301.fc28.x86_64 #1
Hardware name: ASUSTeK COMPUTER INC. X510UQ/X510UQ, BIOS X510UQ.308 03/13/2018
Workqueue: events gk104_fifo_recover_work [nouveau]
RIP: 0010:gf100_grctx_generate+0x617/0x6a0 [nouveau]
RSP: 0000:ffffb52e069a7c18 EFLAGS: 00010286
RAX: 0000000000000000 RBX: 0000000000000000 RCX: 0000000000000006
RDX: 0000000000000007 RSI: 0000000000000096 RDI: ffff9c62eec168f0
RBP: ffff9c62df5f4000 R08: 0000000000000030 R09: 00000000000004a6
R10: 0000000000000000 R11: 0000000000000001 R12: ffff9c62df872c00
R13: ffffb52e069a7c48 R14: ffffb52e069a7c40 R15: ffffb52e069a7c50
FS:  0000000000000000(0000) GS:ffff9c62eec00000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f60c9e6a000 CR3: 000000014320a003 CR4: 00000000003606f0
Call Trace:
 gf100_gr_init_ctxctl+0x4f6/0x9f0 [nouveau]
 gm107_gr_init+0x70d/0x740 [nouveau]
 nvkm_engine_init+0xaa/0x1e0 [nouveau]
 nvkm_subdev_init+0xb2/0x200 [nouveau]
 gk104_fifo_recover_work+0xb3/0x170 [nouveau]
 process_one_work+0x187/0x340
 worker_thread+0x2e/0x380
 ? pwq_unbound_release_workfn+0xd0/0xd0
 kthread+0x112/0x130
 ? kthread_create_worker_on_cpu+0x70/0x70
 ? do_syscall_64+0x16c/0x180
 ret_from_fork+0x35/0x40
Code: 48 8b 57 50 48 85 d2 75 04 48 8b 57 10 48 89 54 24 08 e8 bd e2 d2 dd 48 8b 54 24 08 48 c7 c7 72 47 95 c0 48 89 c6 e8 d3 4f 84 dd <0f> 0b e9 c7 fd ff ff 49 8b 7c 24 10 48 8b 57 50 48 85 d2 75 04

Comment 1 Kévin Clément 2018-06-18 12:43:59 UTC
Created attachment 1452614 [details]
File: dmesg

Comment 2 Ben Cotton 2019-05-02 19:19:20 UTC
This message is a reminder that Fedora 28 is nearing its end of life.
On 2019-May-28 Fedora will stop maintaining and issuing updates for
Fedora 28. 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 '28'.

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 28 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 3 Ben Cotton 2019-05-02 21:33:43 UTC
This message is a reminder that Fedora 28 is nearing its end of life.
On 2019-May-28 Fedora will stop maintaining and issuing updates for
Fedora 28. 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 '28'.

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 28 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-05-28 20:41:47 UTC
Fedora 28 changed to end-of-life (EOL) status on 2019-05-28. Fedora 28 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.