Bug 1232562 - starting with 3.20.0-0.rc0.git7.1 radeon fails to initialize one DisplayPort monitor
Summary: starting with 3.20.0-0.rc0.git7.1 radeon fails to initialize one DisplayPort ...
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: xorg-x11-drv-ati
Version: 36
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: X/OpenGL Maintenance List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-06-17 03:32 UTC by Charles R. Anderson
Modified: 2023-05-25 19:14 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-05-25 19:14:19 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
lspci-nn.txt (2.75 KB, text/plain)
2015-06-17 03:41 UTC, Charles R. Anderson
no flags Details
Xorg journal messages from bad kernel (92.74 KB, text/plain)
2015-06-17 03:42 UTC, Charles R. Anderson
no flags Details
Xorg journal messages from good 3.19.8-200.fc21 kernel (95.66 KB, text/x-vhdl)
2015-06-17 03:43 UTC, Charles R. Anderson
no flags Details
kernel journal messages from bad kernel (97.11 KB, text/plain)
2015-06-17 03:43 UTC, Charles R. Anderson
no flags Details
kernel journal messages from good 3.19.8-200.fc21 kernel (93.52 KB, text/plain)
2015-06-17 03:44 UTC, Charles R. Anderson
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Linux Kernel 100871 0 None None None Never

Description Charles R. Anderson 2015-06-17 03:32:10 UTC
Description of problem:

Ever since Fedora 21 was updated to kernel-4.x, the radeon drm driver fails to initialize one DisplayPort monitor of a multi-monitor setup.  Setup is four mini-DP ports on [AMD/ATI] Cedar GL [FirePro 2460], two Dell U2410 monitors connected via DP, and two Dell 2001FP monitors connected via DVI using DP-to-DVI adapters.

Version-Release number of selected component (if applicable):
kernel-3.20.0-0.rc0.git7.1.fc22.x86_64

How reproducible:
always

Steps to Reproduce:
1. boot kernel
2. after drm module loads, one DP monitor goes dark (text VC and X11)

Additional info:

01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Cedar GL [FirePro 2460] (prog-if 00 [VGA controller])
	Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Device 2002
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0, Cache Line Size: 64 bytes
	Interrupt: pin A routed to IRQ 29
	Region 0: Memory at e0000000 (64-bit, prefetchable) [size=256M]
	Region 2: Memory at f7e20000 (64-bit, non-prefetchable) [size=128K]
	Region 4: I/O ports at e000 [size=256]
	Expansion ROM at f7e00000 [disabled] [size=128K]
	Capabilities: <access denied>
	Kernel driver in use: radeon
	Kernel modules: radeon

I used koji-bisect to narrow down which kernel introduced the problem:

Last good kernel: kernel-3.20.0-0.rc0.git6.1.fc22.x86_64
First bad kernel: kernel-3.20.0-0.rc0.git7.1.fc22.x86_64

Looking at the changelog:

* Tue Feb 17 2015 Josh Boyer <jwboyer> - 3.20.0-0.rc0.git7.1
- Linux v3.19-7478-g796e1c55717e
- DRM merge

* Mon Feb 16 2015 Josh Boyer <jwboyer>
- CVE-XXXX-XXXX potential memory corruption in vhost/scsi driver (rhbz 1189864 1192079)
- CVE-2015-1593 stack ASLR integer overflow (rhbz 1192519 1192520)

* Mon Feb 16 2015 Peter Robinson <pbrobinson>
- Minor updates for ARMv7/ARM64

* Mon Feb 16 2015 Josh Boyer <jwboyer> - 3.20.0-0.rc0.git6.1
- Linux v3.19-6676-g1fa185ebcbce

I did a git bisect between Linux v3.19-6676-g1fa185ebcbce and v3.19-7478-g796e1c55717e and found:

# bad: [e55bca26188e45f209597abf986c87cc5a49894a] radeon/audio: enable DP audio
git bisect bad e55bca26188e45f209597abf986c87cc5a49894a
# first bad commit: [e55bca26188e45f209597abf986c87cc5a49894a] radeon/audio: enable DP audio

Comment 1 Charles R. Anderson 2015-06-17 03:41:39 UTC
Created attachment 1039725 [details]
lspci-nn.txt

Comment 2 Charles R. Anderson 2015-06-17 03:42:34 UTC
Created attachment 1039726 [details]
Xorg journal messages from bad kernel

Comment 3 Charles R. Anderson 2015-06-17 03:43:14 UTC
Created attachment 1039727 [details]
Xorg journal messages from good 3.19.8-200.fc21 kernel

Comment 4 Charles R. Anderson 2015-06-17 03:43:45 UTC
Created attachment 1039728 [details]
kernel journal messages from bad kernel

Comment 5 Charles R. Anderson 2015-06-17 03:44:19 UTC
Created attachment 1039729 [details]
kernel journal messages from good 3.19.8-200.fc21 kernel

Comment 6 Charles R. Anderson 2015-06-17 04:00:15 UTC
commit e55bca26188e45f209597abf986c87cc5a49894a
Author: Slava Grigorev <slava.grigorev>
Date:   Fri Dec 12 17:01:42 2014 -0500

    radeon/audio: enable DP audio
    
    Reviewed-by: Christian König <christian.koenig>
    Signed-off-by: Slava Grigorev <slava.grigorev>
    Signed-off-by: Alex Deucher <alexander.deucher>

Comment 7 Charles R. Anderson 2015-07-18 03:11:47 UTC
Booting with radeon.audio=0 works around the problem and allows all monitors to initialize properly.

Comment 8 Charles R. Anderson 2015-10-20 22:52:12 UTC
(In reply to Charles R. Anderson from comment #7)
> Booting with radeon.audio=0 works around the problem and allows all monitors
> to initialize properly.


Still fails on 4.2.3-200.fc22.  This problem exists on at least 3 multi-headed systems here, some on F21 4.1.10-100.fc21 and some on F22 4.2.3-200.fc22.  The workaround is still needed to get all 4 monitors to initialize.

Comment 9 Fedora End Of Life 2016-07-19 14:52:29 UTC
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 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 10 Fedora End Of Life 2017-07-25 18:57:45 UTC
This message is a reminder that Fedora 24 is nearing its end of life.
Approximately 2 (two) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 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 '24'.

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 24 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 11 Fedora End Of Life 2017-08-08 11:59:10 UTC
Fedora 24 changed to end-of-life (EOL) status on 2017-08-08. Fedora 24 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 12 Charles R. Anderson 2017-08-08 19:35:55 UTC
Still a problem on Fedora 26.

Comment 13 Charles R. Anderson 2017-08-08 19:38:09 UTC
This is actually a bug in the kernel-side.

Comment 14 Laura Abbott 2017-08-08 20:07:16 UTC
the xorg-x11-drv-ati component is used for tracking kernel side problems in graphics drivers as well.

Comment 15 Fedora End Of Life 2018-05-03 08:49:55 UTC
This message is a reminder that Fedora 26 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 26. 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 '26'.

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 26 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 16 Fedora End Of Life 2018-05-29 12:00:38 UTC
Fedora 26 changed to end-of-life (EOL) status on 2018-05-29. Fedora 26
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 17 Charles R. Anderson 2022-08-08 21:33:51 UTC
Still a problem on Fedora 36.  Now using two newer monitors (DELL U3219Q) connected via DP instead of the previous four monitors (2 DP, 2 DVI) and neither monitor turns on unless radeon.audio=0 is passed.

Upstream bug report:

https://bugzilla.kernel.org/show_bug.cgi?id=100871

Maybe there needs to be a quirk added to the driver to keep audio turned off for this card?

Comment 18 Charles R. Anderson 2022-08-08 21:48:38 UTC
I believe the PCI ID is 1002:68f1:

01:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Cedar GL [FirePro 2460] [1002:68f1] (prog-if 00 [VGA controller])

Comment 19 Ben Cotton 2023-04-25 16:37:54 UTC
This message is a reminder that Fedora Linux 36 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora Linux 36 on 2023-05-16.
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 '36'.

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. Note that the version field may be hidden.
Click the "Show advanced fields" button if you do not see it.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora Linux 36 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 20 Ludek Smid 2023-05-25 19:14:19 UTC
Fedora Linux 36 entered end-of-life (EOL) status on 2023-05-16.

Fedora Linux 36 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 Linux
please feel free to reopen this bug against that version. Note that the version
field may be hidden. Click the "Show advanced fields" button if you do not see
the version field.

If you are unable to reopen this bug, please file a new report against an
active 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.