<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEEDINFO " title="NEEDINFO - [drm/i915] Displayport connected screen reports Signal Error after update to 5.1 kernel" href="https://bugs.freedesktop.org/show_bug.cgi?id=110782#c12">Comment # 12</a> on <a class="bz_bug_link bz_status_NEEDINFO " title="NEEDINFO - [drm/i915] Displayport connected screen reports Signal Error after update to 5.1 kernel" href="https://bugs.freedesktop.org/show_bug.cgi?id=110782">bug 110782</a> from <a class="email" href="mailto:Blubberbub@protonmail.com" title="Blubberbub@protonmail.com">Blubberbub@protonmail.com</a> <pre>I attached the requested dmesg log for drm-tip at 43905c26d4fd15cba890e62f271befc0eca8de4c: <a href="attachment.cgi?id=144424" name="attach_144424" title="bad dmesg log with drm.debug=0x1e log_buf_len=4M on drm-tip at 43905c26d4fd15cba890e62f271befc0eca8de4c">attachment 144424</a> <a href="attachment.cgi?id=144424&action=edit" title="bad dmesg log with drm.debug=0x1e log_buf_len=4M on drm-tip at 43905c26d4fd15cba890e62f271befc0eca8de4c">[details]</a> I did another test with the current drm-tip at f384132bcdd8670478b99a2a71753e1595305dce and the problem also appears with that version. (dmesg log in <a href="attachment.cgi?id=144473" name="attach_144473" title="bad dmesg log with drm.debug=0x1e log_buf_len=4M on drm-tip at f384132bcdd8670478b99a2a71753e1595305dce">attachment 144473</a> <a href="attachment.cgi?id=144473&action=edit" title="bad dmesg log with drm.debug=0x1e log_buf_len=4M on drm-tip at f384132bcdd8670478b99a2a71753e1595305dce">[details]</a>) I also added the `xrandr --verbose` output of a good and a bad version as attachments <a href="attachment.cgi?id=144474" name="attach_144474" title="xrandr --verbose on good kernel linux-lts 4.19.47-1">attachment 144474</a> <a href="attachment.cgi?id=144474&action=edit" title="xrandr --verbose on good kernel linux-lts 4.19.47-1">[details]</a> (good) and <a href="attachment.cgi?id=144475" name="attach_144475" title="xrandr --verbose on bad drm-tip f384132bcdd8670478b99a2a71753e1595305dce (problems occur with DP2-3)">attachment 144475</a> <a href="attachment.cgi?id=144475&action=edit" title="xrandr --verbose on bad drm-tip f384132bcdd8670478b99a2a71753e1595305dce (problems occur with DP2-3)">[details]</a> (bad). There are some differences, but to me it looks like xrandr doesn't see any problems with the screen "DP2-3", which is an "EIZO FlexScan EV2436W". I did another step of git bisect: > $ git bisect log > git bisect start > # good: [6ee2c3f93d50b2a9aa7bee32bf16b924f2d98596] Arch Linux kernel v5.0.13-arch1 > git bisect good 6ee2c3f93d50b2a9aa7bee32bf16b924f2d98596 > # bad: [8ec0a2cba38f896ebae3c05518c1fc9463db6c0c] Arch Linux kernel v5.1.2-arch1 > git bisect bad 8ec0a2cba38f896ebae3c05518c1fc9463db6c0c > # good: [1c163f4c7b3f621efff9b28a47abb36f7378d783] Linux 5.0 > git bisect good 1c163f4c7b3f621efff9b28a47abb36f7378d783 > # good: [b5dd0c658c31b469ccff1b637e5124851e7a4a1c] Merge branch 'akpm' (patches from Andrew) > git bisect good b5dd0c658c31b469ccff1b637e5124851e7a4a1c > # bad: [cf0240a755b8b3df51b0b857b03309a666611d58] Merge tag 'pinctrl-v5.1-1' of git://git.kernel.org/pub/scm/linux/kern > git bisect bad cf0240a755b8b3df51b0b857b03309a666611d58 > # bad: [80201fe175cbf7f3e372f53eba0a881a702ad926] Merge tag 'for-5.1/block-20190302' of git://git.kernel.dk/linux-block > git bisect bad 80201fe175cbf7f3e372f53eba0a881a702ad926 > # bad: [5ea3998d56346975c2701df18fb5b6e3ab5c8d9e] Merge tag 'drm-intel-next-2019-02-07' of git://anongit.freedesktop.or > git bisect bad 5ea3998d56346975c2701df18fb5b6e3ab5c8d9e > # bad: [968bf969b47df2481022b9a05eaab02948eec088] drm/i915: Fix skl srckey mask bits > git bisect bad 968bf969b47df2481022b9a05eaab02948eec088 > # good: [25f9cebd7a52ddf15405d74fb5fd4c374f301983] drm/i915: Show all active engines on hangcheck > git bisect good 25f9cebd7a52ddf15405d74fb5fd4c374f301983 > # good: [f42fb2317ffcbd005eeb22b1e49020821a11e23a] Merge drm/drm-next into drm-intel-next-queued > git bisect good f42fb2317ffcbd005eeb22b1e49020821a11e23a > # bad: [85baa5dbf79163026dcb78f742294c522e176432] drm/i915: Update DRIVER_DATE to 20190124 > git bisect bad 85baa5dbf79163026dcb78f742294c522e176432 which means the error was probably introduced between f42fb2317ffcbd005eeb22b1e49020821a11e23a and 85baa5dbf79163026dcb78f742294c522e176432: <a href="https://cgit.freedesktop.org/drm-tip/log/?qt=range&q=f42fb2317ffcbd005eeb22b1e49020821a11e23a..85baa5dbf79163026dcb78f742294c522e176432">https://cgit.freedesktop.org/drm-tip/log/?qt=range&q=f42fb2317ffcbd005eeb22b1e49020821a11e23a..85baa5dbf79163026dcb78f742294c522e176432</a>+ (I don't see any mentions of DP there, though) I'm not feeling very comfortable doing more bisect steps, because i don't know if these commits are considered "safe to run on real hardware" and i really don't want to brick my device running a very experimental hardware driver when I already know that there is at least one bug in it. What other information can i give you?</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> <li>You are the QA Contact for the bug.</li> <li>You are on the CC list for the bug.</li> </ul> </body> </html>