Bug 1594403 - [abrt] nvkm_fifo_chan_child_fini: WARNING: CPU: 2 PID: 3439 at drivers/gpu/drm/nouveau/nvkm/engine/fifo/gpfifogf100.c:85 gf100_fifo_gpfifo_engine_fini+0x14e/0x1c0 [nouveau] [nouveau]
Summary: [abrt] nvkm_fifo_chan_child_fini: WARNING: CPU: 2 PID: 3439 at drivers/gpu/dr...
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: xorg-x11-drv-nouveau
Version: 34
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:5d0d27d82c59fd01f242744acad...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-06-22 20:57 UTC by David Kaufmann
Modified: 2022-06-07 20:14 UTC (History)
8 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2022-06-07 20:14:16 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: dmesg (86.05 KB, text/plain)
2018-06-22 20:58 UTC, David Kaufmann
no flags Details


Links
System ID Private Priority Status Summary Last Updated
freedesktop.org Gitlab xorg/driver/xf86-video-nouveau/issues/410 0 None None None 2020-03-11 22:23:56 UTC
freedesktop.org Gitlab xorg/driver/xf86-video-nouveau/issues/487 0 None None None 2020-03-11 22:23:35 UTC

Description David Kaufmann 2018-06-22 20:57:56 UTC
Additional info:
reporter:       libreport-2.9.5
WARNING: CPU: 2 PID: 3439 at drivers/gpu/drm/nouveau/nvkm/engine/fifo/gpfifogf100.c:85 gf100_fifo_gpfifo_engine_fini+0x14e/0x1c0 [nouveau]
Modules linked in: nls_utf8 isofs fuse nf_conntrack_netbios_ns nf_conntrack_broadcast xt_CT ip6t_rpfilter ip6t_REJECT nf_reject_ipv6 xt_conntrack devlink 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 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 sunrpc snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_codec_generic snd_hda_intel snd_hda_codec edac_mce_amd kvm_amd snd_hda_core ccp kvm snd_hwdep irqbypass snd_seq snd_seq_device snd_pcm snd_timer snd soundcore wmi_bmof k10temp shpchp sp5100_tco i2c_piix4 acpi_cpufreq nouveau video mxm_wmi
 i2c_algo_bit drm_kms_helper ttm firewire_ohci firewire_core serio_raw drm crc_itu_t via_rhine r8169 mii wmi uas usb_storage
CPU: 2 PID: 3439 Comm: disk_cache:0 Not tainted 4.16.3-301.fc28.x86_64 #1
Hardware name: Gigabyte Technology Co., Ltd. GA-890GPA-UD3H/GA-890GPA-UD3H, BIOS FD 07/23/2010
RIP: 0010:gf100_fifo_gpfifo_engine_fini+0x14e/0x1c0 [nouveau]
RSP: 0018:ffffadf9470579d0 EFLAGS: 00010286
RAX: 0000000000000000 RBX: ffff9b3f25e331b0 RCX: 0000000000000006
RDX: 0000000000000007 RSI: 0000000000000086 RDI: ffff9b3f2fc968f0
RBP: ffff9b3e9e3d2800 R08: 0000000000000030 R09: 0000000000000437
R10: 0000000000000000 R11: 0000000000000001 R12: ffff9b3f1fc6dc00
R13: ffff9b3f1fdd2540 R14: 000453b56aea8700 R15: ffff9b3e0576cea0
FS:  00007f3c7ba7f700(0000) GS:ffff9b3f2fc80000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 000055afea67def8 CR3: 00000002211c8000 CR4: 00000000000006e0
Call Trace:
 nvkm_fifo_chan_child_fini+0x62/0xe0 [nouveau]
 ? nvkm_oproxy_fini+0x2b/0x90 [nouveau]
 ? nvkm_object_fini+0xbc/0x150 [nouveau]
 ? nvkm_object_fini+0x73/0x150 [nouveau]
 ? nvkm_ioctl_del+0x3a/0x50 [nouveau]
 ? nvkm_ioctl+0xd8/0x170 [nouveau]
 ? nvif_object_fini+0x59/0x80 [nouveau]
 ? nouveau_channel_del+0x97/0x150 [nouveau]
 ? nouveau_channel_idle+0x94/0xe0 [nouveau]
 ? nouveau_abi16_chan_fini.isra.1+0xa0/0x110 [nouveau]
 ? nouveau_abi16_fini+0x2d/0x70 [nouveau]
 ? nouveau_drm_postclose+0x4d/0xf0 [nouveau]
 ? drm_release+0x292/0x3b0 [drm]
 ? __fput+0xa6/0x1f0
 ? task_work_run+0x84/0xa0
 ? do_exit+0x2d3/0xae0
 ? __wake_up_common_lock+0x89/0xc0
 ? do_group_exit+0x3a/0xa0
 ? get_signal+0x276/0x590
 ? do_signal+0x36/0x610
 ? fsnotify_destroy_marks+0x12/0xe0
 ? _cond_resched+0x15/0x30
 ? exit_to_usermode_loop+0x69/0xa0
 ? do_syscall_64+0x16c/0x180
 ? entry_SYSCALL_64_after_hwframe+0x3d/0xa2
Code: 5d 41 5e 41 5f c3 49 8b 7c 24 10 48 8b 5f 50 48 85 db 74 3f e8 a4 17 18 c8 48 89 da 48 c7 c7 9b 15 52 c0 48 89 c6 e8 bc 84 c9 c7 <0f> 0b 48 8b 44 24 08 8b 40 48 85 c0 75 20 48 8b 3c 24 bb 92 ff

Comment 1 David Kaufmann 2018-06-22 20:58:09 UTC
Created attachment 1453850 [details]
File: dmesg

Comment 2 Ben Cotton 2019-05-02 21:32:41 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-28 20:44:10 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.

Comment 4 Dominik 'Rathann' Mierzejewski 2020-03-11 21:26:30 UTC
I'm getting this on F31 with kernel 5.5.7-200.fc31.x86_64. 100% reproducible with:
DRI_PRIME=1 mpv --hwdec=vdpau anymovie.mp4

DRI_PRIME=1 is needed for mpv to use the discrete GPU:
01:00.0 VGA compatible controller [0300]: NVIDIA Corporation GF108M [GeForce GT 525M] [10de:0df5] (rev a1) (prog-if 00 [VGA controller])
on this Dell XPS 15 L502X laptop.

Comment 5 Ben Cotton 2020-11-03 15:01:12 UTC
This message is a reminder that Fedora 31 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 31 on 2020-11-24.
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 '31'.

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 31 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 Dominik 'Rathann' Mierzejewski 2020-11-06 11:33:40 UTC
Still reproducible with: 5.8.16-200.fc32.x86_64. I'll check again after upgrading to F33.

Comment 7 Fedora Program Management 2021-04-29 15:54:23 UTC
This message is a reminder that Fedora 32 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 32 on 2021-05-25.
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 '32'.

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 32 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 8 Yonatan 2021-05-02 05:57:40 UTC
Kind regards, I am writing to report a very old bug with the nouveau driver for graphics "[GeForce 7025 / nForce 630a]" which affects practically all Linux distributions, for many years it has been causing a completely scratched screen error in Xorg, while In Wayland the screen only freezes and does not allow doing anything else, the following link describes this problem in more detail:
https://nouveau.freedesktop.narkive.com/NoeonDJf/system-freeze-debian-testing-with-c61-geforce-7025-nforce-630a

Preview: [img]https://www.mediafire.com/convkey/191d/t85974wub4smv7b6g.jpg[/img]

Please help me and do not forget this problem, I am low-income and I can't access more modern PCs, I'm afraid.

Reply to: yonatan.el.amigo

Comment 9 Dominik 'Rathann' Mierzejewski 2021-05-04 10:23:15 UTC
It's still mostly reproducible on F34 (5.11.17-300.fc34.x86_64). There's no video corruption or kernel WARNING any more, just system becoming slow to respond and Xorg consuming 100% of one CPU core with these messages in dmesg:

[ 7432.563548] Asynchronous wait on fence nouveau:Xorg[757]:ff8b744b timed out (hint:submit_notify [i915])
[ 7436.536516] nouveau 0000:01:00.0: mpv/vo[10304]: failed to idle channel 4 [mpv/vo[10304]]
[ 7443.316458] Asynchronous wait on fence nouveau:Xorg[757]:ff8b744c timed out (hint:submit_notify [i915])
[ 7451.536392] nouveau 0000:01:00.0: mpv/vo[10304]: failed to idle channel 4 [mpv/vo[10304]]
[ 7453.555484] nouveau 0000:01:00.0: fifo: runlist update timeout
[ 7453.555530] nouveau 0000:01:00.0: fifo: INTR 00000001: 0000000b
[ 7454.579422] Asynchronous wait on fence nouveau:Xorg[757]:ff8b744d timed out (hint:submit_notify [i915])
[ 7465.331280] Asynchronous wait on fence nouveau:Xorg[757]:ff8b744e timed out (hint:submit_notify [i915])
[ 7465.331371] Asynchronous wait on fence nouveau:mpv/vo[10304]:ff020b21 timed out (hint:submit_notify [i915])
[ 7476.595187] Asynchronous wait on fence nouveau:Xorg[757]:ff8b744f timed out (hint:submit_notify [i915])
[ 7487.347098] Asynchronous wait on fence nouveau:Xorg[757]:ff8b7450 timed out (hint:submit_notify [i915])
[ 7498.099011] Asynchronous wait on fence nouveau:Xorg[757]:ff8b7451 timed out (hint:submit_notify [i915])
[ 7509.362929] Asynchronous wait on fence nouveau:Xorg[757]:ff8b7452 timed out (hint:submit_notify [i915])

Again, it's enough to run:

DRI_PRIME=1 mpv -vo=vdpau --hwdec=vdpau any_h264_video.mp4

and press `q'.

Comment 10 Dominik 'Rathann' Mierzejewski 2021-05-04 10:28:00 UTC
(In reply to Yonatan from comment #8)
> Kind regards, I am writing to report a very old bug with the nouveau driver
> for graphics "[GeForce 7025 / nForce 630a]" which affects practically all
> Linux distributions, for many years it has been causing a completely
> scratched screen error in Xorg, while In Wayland the screen only freezes and
> does not allow doing anything else, the following link describes this
> problem in more detail:
> https://nouveau.freedesktop.narkive.com/NoeonDJf/system-freeze-debian-
> testing-with-c61-geforce-7025-nforce-630a

This seems to be a different issue. You are getting a kernel panic, while this report is about a different kernel WARNING.

Comment 11 Ben Cotton 2022-05-12 15:00:32 UTC
This message is a reminder that Fedora Linux 34 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora Linux 34 on 2022-06-07.
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
'version' of '34'.

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

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora Linux 34 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 Linux, you are encouraged to change the 'version' to a later version
prior to this bug being closed.

Comment 12 Ben Cotton 2022-06-07 20:14:16 UTC
Fedora Linux 34 entered end-of-life (EOL) status on 2022-06-07.

Fedora Linux 34 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.

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.