[Bug 97666] Kernel "NULL pointer dereference" with MST monitor on HSW

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Thu Oct 13 01:50:19 UTC 2016


https://bugs.freedesktop.org/show_bug.cgi?id=97666

--- Comment #24 from Carlos Santa <carlos.santa at intel.com> ---
To make the bisect more simpler I moved the bisection to the drm-intel tree
instead of the Ubuntu one.

Using the following two commits as starting point for the bisect:

Bad commit:  a4fce9cb782ad340ee5576a38e934e5e75832dc6
Good commit: 14740bb25ec36fe4ce8042af3eb48aeb45e5bc13

the commit that introduced the null pointer seems to be this one:

27d4efc5591a5853de54713bc717de73c8951e17 is the first bad commit
commit 27d4efc5591a5853de54713bc717de73c8951e17
Author: Ville Syrjälä <ville.syrjala at linux.intel.com>
Date:   Mon Oct 3 10:55:15 2016 +0300

    drm/i915: Move long hpd handling into the hotplug work

    We can't rely on connector->status in the detect() hook if the long hpd
    was already handled by the dig_port_work as that won't update
    connector->status. Thus we have to defer the long hpd handling entirely
    until the hotplug work runs to avoid the double long hpd handling
    the "detect_done" flag is trying to prevent.

    We'll start to depend on connector->status being up to date in a
    following patch.

    Cc: Damien Cassou <damien at cassou.me>
    Cc: freedesktop.org at gp.mailgun.org
    Cc: Arno <blouin.arno at gmail.com>
    Cc: Shubhangi Shrivastava <shubhangi.shrivastava at intel.com>
    Cc: Sivakumar Thulasimani <sivakumar.thulasimani at intel.com>
    Cc: Ander Conselvan de Oliveira <conselvan2 at gmail.com>
    Cc: stable at vger.kernel.org
    Tested-by: Arno <blouin.arno at gmail.com>
    Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=83348
    Signed-off-by: Ville Syrjälä <ville.syrjala at linux.intel.com>
    Link:
http://patchwork.freedesktop.org/patch/msgid/1475481316-8194-1-git-send-email-ville.syrjala@linux.intel.com
    Reviewed-by: Ander Conselvan de Oliveira <conselvan2 at gmail.com>


which makes sense since there are changes related to display port. I'll
continue tomorrow looking into the changes.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are on the CC list for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/intel-gfx-bugs/attachments/20161013/ac14732a/attachment.html>


More information about the intel-gfx-bugs mailing list