Bug 1400039

Summary: [drm:uvd_v1_0_ib_test [radeon]] *ERROR* radeon: fence wait timed out.
Product: [Fedora] Fedora Reporter: luminoso <luminoso>
Component: xorg-x11-drv-atiAssignee: X/OpenGL Maintenance List <xgl-maint>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: urgent Docs Contact:
Priority: unspecified    
Version: 25CC: a.thiaville, cz172638, gansalmon, ichavero, itamar, jonathan, kernel-maint, labbott, madhu.chinakonda, mchehab, xgl-maint
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-12-12 10:08:09 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
dmesg for kernel 4.8.11
none
dmesg for kernel 4.8.11 rmmod
none
dmesg for kernel 4.8.8
none
dmesg for kernel 4.8.10
none
dmesg drm:uvd_v1_0_ib_test [radeon]] *ERROR* radeon: fence wait timed out none

Description luminoso 2016-11-30 10:40:25 UTC
Created attachment 1226245 [details]
dmesg for kernel 4.8.11

I have an bug that radeon module fails to initialize correctly with the following output:

"
[drm:uvd_v1_0_ib_test [radeon]] *ERROR* radeon: fence wait timed out.
[drm:radeon_ib_ring_tests [radeon]] *ERROR* radeon: failed testing IB on ring 5 (-110).
radeon 0000:01:00.0: scheduling IB failed (-12).
[drm:radeon_vce_get_create_msg [radeon]] *ERROR* radeon: failed to schedule ib (-12).
[drm:radeon_vce_ib_test [radeon]] *ERROR* radeon: failed to get create msg (-12).
[drm:radeon_ib_ring_tests [radeon]] *ERROR* radeon: failed testing IB on ring 6 (-12).
radeon 0000:01:00.0: scheduling IB failed (-12).
[drm:radeon_vce_get_create_msg [radeon]] *ERROR* radeon: failed to schedule ib (-12).
[drm:radeon_vce_ib_test [radeon]] *ERROR* radeon: failed to get create msg (-12).
[drm:radeon_ib_ring_tests [radeon]] *ERROR* radeon: failed testing IB on ring 7 (-12).
"

Latest kernel I remember no having this is kernel-4.7.9 from Fedora 24.

I was hoping that Fedora 25 latest kernel (4.8.11-300.fc25.x86_64) fixes the problem but did not.

Attached is an dmesg with important bits:
dmesg4.8.8.txt for kernel-4.8.8-300.fc25.x86_64 with radeon load on boot
dmesg4.8.10.txt for kernel-4.8.10-300.fc25.x86_64 with radeon load on boot
dmesg4.8.11.txt for kernel 4.8.11 but modprobe after X start and system boot.
dmesg4.8.11.txt for kernel 4.8.11 trying to rmmod radeon after modprobe radeon

Things I did to avoid this problem:

1) Block radeon from loading:
$ cat /etc/modprobe.d/noradeon.conf 
blacklist radeon

# dracut --omit-drivers radeon -f -v

2) Try to boot with radeon.vce=0 radeon.dpm=0

One major consequence is that my laptop cannot enter in deeper deep sleep stages. (This is why I marked the bug as Urgent). 
Reported by powertop for my laptop the deepest system level is C2 (pc2) and never enters deeper levels. This causes extreme battery drain. (The only solution I found for this was running kernel 4.9.7 that doesn't have this radeon problem).

This tested in order try to fix battery drainage:

# echo OFF > /sys/kernel/debug/vgaswitcheroo/switch
# echo battery > /sys/class/drm/card1/device/power_dpm_state

None of them seems to fix the battery drainage in a faulty kernel.

Is there any instructions how to do kernel bisect in fedora?
Should I submit this to kernel bugzilla?

Possible related bugs are #1397894 and #1398971

Comment 1 luminoso 2016-11-30 10:41:14 UTC
Created attachment 1226246 [details]
dmesg for kernel 4.8.11 rmmod

Comment 2 luminoso 2016-11-30 10:41:39 UTC
Created attachment 1226247 [details]
dmesg for kernel 4.8.8

Comment 3 luminoso 2016-11-30 10:42:00 UTC
Created attachment 1226248 [details]
dmesg for kernel 4.8.10

Comment 4 Fedora End Of Life 2017-11-16 19:43:00 UTC
This message is a reminder that Fedora 25 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 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 '25'.

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 25 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 Fedora End Of Life 2017-12-12 10:08:09 UTC
Fedora 25 changed to end-of-life (EOL) status on 2017-12-12. Fedora 25 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 6 a.thiaville 2018-01-03 08:12:59 UTC
Created attachment 1376216 [details]
dmesg drm:uvd_v1_0_ib_test [radeon]] *ERROR* radeon: fence wait timed out