Created attachment 112644 [details] log ==System Environment== -------------------------- Regression: Yes. I tried _drm-intel-testing 2014_12_06 commit and testdisplay shows normal. Non-working platforms: BYT ==kernel== -------------------------- -testing: 2015_01_18 commit 6dd5bb25ce0ed3a0012b69d553d74e1a0d39c313(test fails) ==Bug detailed description== ----------------------------- Connect to HDMI display, Boot BYT, login and run "testdisplay -o 30,3", HDMI screen flashes. The same issue happens on VGA, DP screen too. ==Reproduce steps== ---------------------------- 1. Connect to HDMI display, Boot BYT, login and run "testdisplay -o 30,3" Bisect is on going.
Created attachment 112645 [details] image
(In reply to Jiang Wang from comment #0) > Created attachment 112644 [details] > log > > ==System Environment== > -------------------------- > Regression: Yes. I tried _drm-intel-testing 2014_12_06 commit and > testdisplay shows normal. > > Non-working platforms: BYT > > ==kernel== > -------------------------- > -testing: 2015_01_18 commit 6dd5bb25ce0ed3a0012b69d553d74e1a0d39c313(test > fails) > > > ==Bug detailed description== > ----------------------------- > Connect to HDMI display, Boot BYT, login and run "testdisplay -o 30,3", HDMI > screen flashes. > > The same issue happens on VGA, DP screen too. > > ==Reproduce steps== > ---------------------------- > 1. Connect to HDMI display, Boot BYT, login and run "testdisplay -o 30,3" > > Bisect is on going. Jiang, you can provide the display timing/resolution which you were using And notice that any time you want to attach dmesg, be sure you have option drm.debug=0xe !
We find something different after furthur testing so I reported a new bug 88698. I prefer to close this issue to avoid confusion.
*** This bug has been marked as a duplicate of bug 88698 ***
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.