Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 548512 - >=sys-kernel/gentoo-sources-4.0.0 break radeon HDMI output and fullscreen operation
Summary: >=sys-kernel/gentoo-sources-4.0.0 break radeon HDMI output and fullscreen ope...
Status: RESOLVED NEEDINFO
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] Core system (show other bugs)
Hardware: AMD64 Linux
: Normal major (vote)
Assignee: Gentoo Kernel Bug Wranglers and Kernel Maintainers
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-05-03 17:48 UTC by faminebadger
Modified: 2017-02-04 07:27 UTC (History)
1 user (show)

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description faminebadger 2015-05-03 17:48:35 UTC
I have two monitors plugged into DisplayPort connectors on my Radeon HD7970, and a further HDMI connection to my amp and TV.

As of upgrading to kernel 4.0.0, the third display briefly (for ~1s or so) shows a desktop backdrop when the system is first booted, then reverts to just showing white snow.

All full-screen hardware decoding (via vdpau / vaa) operations are broken, resulting in "radeon: The kernel rejected CS" type messages on the terminal.

Inspection of dmesg shows messages like:
  May  3 19:26:40 gentoo kernel: [drm:radeon_uvd_cs_parse [radeon]] *ERROR* Failed mapping the UVD message (-22)!
  May  3 19:26:40 gentoo kernel: [drm:radeon_cs_ioctl [radeon]] *ERROR* Invalid command stream !

These effects are 100% reproducible on my system.

Rolling back to an older kernel fixes the problem (3.18.9 works fine, I haven't binary chopped all versions in between yet).


Reproducible: Always

Steps to Reproduce:
1. Boot to X with TV (3rd display) powered on & connected to HDMI
2. 
3.
Actual Results:  
White noise / snow only shown on 3rd display.

Expected Results:  
Extended desktop on 3rd display.
Comment 1 Alice Ferrazzi Gentoo Infrastructure gentoo-dev 2017-02-04 07:27:21 UTC
is this still a problem with more recent kernel ? 

Please open a new bug if the problem persist with a more recent kernel