Bug 1615250 - [abrt] gk104_gr_init: WARNING: CPU: 3 PID: 954 at drivers/gpu/drm/nouveau/nvkm/engine/gr/gf100.c:1624 gf100_gr_init_ctxctl+0x7b4/0x990 [nouveau] [nouveau]
Summary: [abrt] gk104_gr_init: WARNING: CPU: 3 PID: 954 at drivers/gpu/drm/nouveau/nvk...
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: xorg-x11-drv-nouveau
Version: 28
Hardware: x86_64
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: Ben Skeggs
QA Contact: Fedora Extras Quality Assurance
URL: https://retrace.fedoraproject.org/faf...
Whiteboard: abrt_hash:609294575bfbac62c86514693e9...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-08-13 07:33 UTC by Dilan Rona
Modified: 2019-05-28 22:07 UTC (History)
5 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2019-05-28 22:07:05 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: dmesg (69.17 KB, text/plain)
2018-08-13 07:33 UTC, Dilan Rona
no flags Details

Description Dilan Rona 2018-08-13 07:33:03 UTC
Description of problem:
upgraded from fedora server 27. had well over 1000 crashes, over a 3 day period for this driver alone, system is completely unstable, and keeps freezing. Downgraded the kernel, and so far it is more stable. But the error is still appearing.

Additional info:
reporter:       libreport-2.9.5
WARNING: CPU: 3 PID: 954 at drivers/gpu/drm/nouveau/nvkm/engine/gr/gf100.c:1624 gf100_gr_init_ctxctl+0x7b4/0x990 [nouveau]
Modules linked in: uas usb_storage rfcomm fuse ccm ip6t_rpfilter ip6t_REJECT nf_reject_ipv6 xt_conntrack ip_set nfnetlink ebtable_nat ebtable_broute bridge ip6table_nat nf_conntrack_ipv6 nf_defrag_ipv6 nf_nat_ipv6 ip6table_mangle ip6table_raw 8021q garp mrp stp llc ip6table_security iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack iptable_mangle iptable_raw iptable_security ebtable_filter ebtables ip6table_filter ip6_tables cmac bnep sunrpc vfat fat intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm irqbypass crct10dif_pclmul crc32_pclmul arc4 ghash_clmulni_intel rtl8723ae btcoexist intel_cstate rtl8723_common snd_hda_codec_hdmi rtl_pci intel_uncore wmi_bmof btusb btrtl rtlwifi iTCO_wdt btbcm iTCO_vendor_support btintel snd_hda_codec_via
 snd_hda_codec_generic intel_rapl_perf joydev bluetooth gpio_ich ecdh_generic mac80211 uvcvideo videobuf2_vmalloc videobuf2_memops i2c_i801 videobuf2_v4l2 videobuf2_common videodev cfg80211 snd_hda_intel snd_hda_codec rfkill media rtsx_pci_ms memstick snd_hda_core snd_hwdep snd_seq snd_seq_device shpchp pcc_cpufreq snd_pcm lpc_ich mei_me mei snd_timer snd soundcore xfs libcrc32c i915 nouveau hid_logitech_hidpp rtsx_pci_sdmmc mmc_core mxm_wmi ttm i2c_algo_bit crc32c_intel drm_kms_helper serio_raw drm r8169 rtsx_pci mii hid_logitech_dj wmi video
CPU: 3 PID: 954 Comm: Xorg Not tainted 4.17.11-100.fc27.x86_64 #1
Hardware name: GIGABYTE Q1542/Q1542, BIOS 4.6.5 11/28/2012
RIP: 0010:gf100_gr_init_ctxctl+0x7b4/0x990 [nouveau]
RSP: 0018:ffffa44e015c7a88 EFLAGS: 00010286
RAX: 0000000000000000 RBX: ffff950f298475c0 RCX: 0000000000000006
RDX: 0000000000000007 RSI: 0000000000000096 RDI: ffff950f2f396930
RBP: ffff950f22164000 R08: 00000000000003e4 R09: 0000000000000004
R10: 0000000000000004 R11: 0000000000000001 R12: 0000000077359b80
R13: ffff950f241e3ea0 R14: 0000183116b99d00 R15: 0000000000508420
FS:  00007f6662900a80(0000) GS:ffff950f2f380000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f800a923218 CR3: 0000000126276002 CR4: 00000000001606e0
Call Trace:
 gk104_gr_init+0x6b0/0x6f0 [nouveau]
 nvkm_engine_init+0x64/0x1e0 [nouveau]
 nvkm_subdev_init+0xb2/0x1f0 [nouveau]
 nvkm_device_init+0x132/0x270 [nouveau]
 nvkm_udevice_init+0x41/0x60 [nouveau]
 nvkm_object_init+0x3d/0x180 [nouveau]
 nvkm_object_init+0xa0/0x180 [nouveau]
 nvkm_object_init+0xa0/0x180 [nouveau]
 nouveau_do_resume+0x28/0x140 [nouveau]
 nouveau_pmops_runtime_resume+0x88/0x150 [nouveau]
 pci_pm_runtime_resume+0x78/0xb0
 ? pci_restore_standard_config+0x40/0x40
 __rpm_callback+0xcd/0x210
 rpm_callback+0x1f/0x70
 ? pci_restore_standard_config+0x40/0x40
 rpm_resume+0x4a5/0x780
 ? __handle_mm_fault+0xada/0x1310
 __pm_runtime_resume+0x47/0x70
 nouveau_drm_ioctl+0x35/0xc0 [nouveau]
 do_vfs_ioctl+0xa4/0x620
 ksys_ioctl+0x70/0x80
 __x64_sys_ioctl+0x16/0x20
 do_syscall_64+0x5b/0x160
 entry_SYSCALL_64_after_hwframe+0x44/0xa9
RIP: 0033:0x7f665fbdd0f7
RSP: 002b:00007fffb3082fa8 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
RAX: ffffffffffffffda RBX: 0000000002790070 RCX: 00007f665fbdd0f7
RDX: 0000000000000000 RSI: 000000000000641f RDI: 0000000000000012
RBP: 0000000000000000 R08: 00000000025f42b0 R09: 00000000033e4ac0
R10: 0000000000000095 R11: 0000000000000246 R12: 000000000000641f
R13: 0000000000000012 R14: 000000000084f558 R15: ffffffffffffffff
Code: fa ff ff 48 8b 7b 10 48 8b 5f 50 48 85 db 0f 84 05 01 00 00 e8 1e c8 f7 d8 48 89 da 48 89 c6 48 c7 c7 a5 6e 75 c0 e8 7c aa a5 d8 <0f> 0b 48 89 ef e8 82 f1 ff ff b8 f0 ff ff ff e9 12 fa ff ff b8

Comment 1 Dilan Rona 2018-08-13 07:33:15 UTC
Created attachment 1475488 [details]
File: dmesg

Comment 2 Ben Cotton 2019-05-02 19:21:48 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:09:50 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 22:07:05 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.