Reproduce Steps 1.$ xrandr --verbose 2.$ xrandr --output DP1 --crtc 1 3.$ xrandr --verbose Expected Result After step 3, check DP pipe and the pipe should display 1. Actual Result After step 3, can't change the DP pipe. Test Environment: Hardware: CRB:Braswell RVP Platform: Braswell CPU: Braswell A3 Audio card: ALC282 Software: BIOS: BRASWEL1.X64.0021.D00.1405260229 Kernel: 3.17.0 - rc2 Branch: git://anongit.freedesktop.org/drm-intel drm-intel-nightly tag:2014_09_02 Commit:45cb75c77746cc3023acdfb4033e745d1d6024d9
Is this a regression? Can you find a working kernel?
I don't confirm it is a regression and I don't find the good kernel. Because the August 15 kernel also bad and the BSW platform can't work on the July kernel.During find the good kernel, the kernel can't work normally always,so I can't find the good kernel.
Did you perhaps have something else using pipe B already? If not, please test again with a more recent kernel.
(In reply to Ville Syrjala from comment #3) > Did you perhaps have something else using pipe B already? > > If not, please test again with a more recent kernel. This bug is blocked by Bug 87671 now.
(In reply to Yi Sun from comment #4) > (In reply to Ville Syrjala from comment #3) > > Did you perhaps have something else using pipe B already? > > > > If not, please test again with a more recent kernel. > > This bug is blocked by Bug 87671 now. Blocker fixed, what's the status?
I verify the issue on the latest nightly kernel, can't reproduce it. Environment CRB:Braswell RVP Fab2 Platform: Braswell CPU: Braswell B1 Audio card: ALC282 BIOS: BRASWEL1.X64.0053.R00.1501031907 Kernel:3.19.0-rc6 Tree: git://anongit.freedesktop.org/drm-intel Branch:drm-intel-nightly Commit:2c2cd3
(In reply to zhaodan from comment #6) > I verify the issue on the latest nightly kernel, can't reproduce it. If I understand that correctly, this works now. Closing.
I verify the issue and the issue can't reproduce.The issue should be fixed.
Closing old verified.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.