Created attachment 130481 [details] dmesg was not showing full info with drm.debug=0x1e so kern.log instead Hi, There is a regression with my HW combination that maybe is somewhat exotic but I dont have a good remedy other than running the 4.2.8 kernel from 2015, so here's the bug report. I have a Gigabyte C1037U-EU board with Celeron 1037U/. When it is connected via HDMI to my Onkyo AVR HT-R380 and then to my Samsung UE55F6100 there is constant refresh rate flickering at 60/50hz. With 24hz it's more stable. When connecting the HDMI directly to the TV there is no issue at any refresh rates (all at 1080p). Replaced all cables to rule out issues there. Problem started with kernel 4.3.0-rc1, there are no problems with 4.2.8. Reporting this now with the following log that shows 3 boot/reboot cycles with kernels 4.11.0-994-generic (drm-tip), 4.3.0-040300rc1-generic and 4.2.8-040208-generic all from the ubuntu mainline ppa. Booted with video=HDMI-A-1:1920x1080@60D drm_kms_helper.edid_firmware=HDMI-A-1:edid/edid.bin drm.debug=0x1e. The EDID is from the Onkyo AVR as a possible workaround but hasnt helped with this issue. The first 2 kernels exhibit continuous screen refresh rate changes starting already at the Ubuntu bootup splash and only the last 4.2.8 boot does not have this symptom.
Would you be able to bisect the issue? Might give the best clues.
Sure, whatever it takes. Just need clear directions.
Any thoughts on how to bisect this?
(In reply to oliver from comment #3) > Any thoughts on how to bisect this? https://wiki.ubuntu.com/Kernel/KernelBisection git bisect good 4.2.8 git bisect bad 4.3.0-rc1
Created attachment 130748 [details] attachment-1498-0.html Thanks for the tip, Working with the ubuntu mainline-crack source it seems a rather humongous task though, any way to narrow down the commits? (also verified 4.2.0-unstable was ok and thought its closer to v4.3-rc1 on the timeline). odt@cube:mainline-crack$ git log --oneline v4.2 v4.3-rc1 | grep i915 | wc -l 8863 On Wed, Apr 5, 2017 at 9:53 AM, <bugzilla-daemon@freedesktop.org> wrote: > *Comment # 4 <https://bugs.freedesktop.org/show_bug.cgi?id=100414#c4> on > bug 100414 <https://bugs.freedesktop.org/show_bug.cgi?id=100414> from Jani > Nikula <jani.nikula@intel.com> * > > (In reply to oliver from comment #3 <https://bugs.freedesktop.org/show_bug.cgi?id=100414#c3>)> Any thoughts on how to bisect this? > https://wiki.ubuntu.com/Kernel/KernelBisection > > git bisect good 4.2.8 > git bisect bad 4.3.0-rc1 > > ------------------------------ > You are receiving this mail because: > > - You are on the CC list for the bug. > - You reported the bug. > >
Reporter, any updates on this?
Unfortunately I'm not able to bisect the issue due to lack of skills, willing to try anything prebuilt though.
(In reply to oliver from comment #7) > Unfortunately I'm not able to bisect the issue due to lack of skills, > willing to try anything prebuilt though. Changing the status to REOPEN.
(In reply to Elizabeth from comment #8) > (In reply to oliver from comment #7) > > Unfortunately I'm not able to bisect the issue due to lack of skills, > > willing to try anything prebuilt though. > > Changing the status to REOPEN. Hello Oliver, Could you try to reproduce with 4.13 or drm-tip? Thanks.
Created attachment 133121 [details] attachment-6321-0.html Hi, Issue still exists with drm-tip 4.13.0-994-generic. Actually it has gotten worse as now my TV is also distorting the image (blurring and going back to sharp eventually) and the desktop was overscaled. Would new logs on 4.13 be helpful? On Mon, Jul 24, 2017 at 10:33 PM, <bugzilla-daemon@freedesktop.org> wrote: > *Comment # 9 <https://bugs.freedesktop.org/show_bug.cgi?id=100414#c9> on > bug 100414 <https://bugs.freedesktop.org/show_bug.cgi?id=100414> from > Elizabeth <elizabethx.de.la.torre.mena@intel.com> * > > (In reply to Elizabeth from comment #8 <https://bugs.freedesktop.org/show_bug.cgi?id=100414#c8>)> (In reply to oliver from comment #7 <https://bugs.freedesktop.org/show_bug.cgi?id=100414#c7>) > > > Unfortunately I'm not able to bisect the issue due to lack of skills, > > > willing to try anything prebuilt though. > > > > Changing the status to REOPEN. > > Hello Oliver, > Could you try to reproduce with 4.13 or drm-tip? > Thanks. > > ------------------------------ > You are receiving this mail because: > > - You are on the CC list for the bug. > - You reported the bug. > >
(In reply to oliver from comment #10) > Hello Oliver, could you attach new dmesg with latest kernel? Also do the Onkyo has the latest firmware? Thank you.
Created attachment 134679 [details] New syslog for 4.14.0-994-generic
(In reply to Elizabeth from comment #11) > (In reply to oliver from comment #10) > > > Hello Oliver, could you attach new dmesg with latest kernel? Also do the > Onkyo has the latest firmware? > Thank you. Hi, The Onkyo model is non-upgradeable unfortunately and quite old by now (from 2010). I have made a couple of videos demonstrating problems with the screen refresh rate. I have reproduced with the latest drm-tip (4.14.0-994) and taken logs and recorded the behaviour aswell. new dmesg attached to the bug. boot cycle https://drive.google.com/open?id=0B-88HHr_LlAFSVVHakdmV3J5RVk interlacing issue at 24p https://drive.google.com/open?id=0B-88HHr_LlAFU2xXYkl6b1gwS0k (In reply to Elizabeth from comment #11) > (In reply to oliver from comment #10) > > > Hello Oliver, could you attach new dmesg with latest kernel? Also do the > Onkyo has the latest firmware? > Thank you.
First of all. Sorry about spam. This is mass update for our bugs. Sorry if you feel this annoying but with this trying to understand if bug still valid or not. If bug investigation still in progress, please ignore this and I apologize! If you think this is not anymore valid, please comment to the bug that can be closed. If you haven't tested with our latest pre-upstream tree(drm-tip), can you do that also to see if issue is valid there still and if you cannot see issue there, please comment to the bug.
Closing, please re-open if still occurs.
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.