[Bug 106804] New: i195: modesetting stops working on kernel 4.17, works fine on 4.16
bugzilla-daemon at freedesktop.org
bugzilla-daemon at freedesktop.org
Mon Jun 4 04:32:35 UTC 2018
https://bugs.freedesktop.org/show_bug.cgi?id=106804
Bug ID: 106804
Summary: i195: modesetting stops working on kernel 4.17, works
fine on 4.16
Product: DRI
Version: XOrg git
Hardware: Other
OS: All
Status: NEW
Severity: normal
Priority: medium
Component: DRM/Intel
Assignee: intel-gfx-bugs at lists.freedesktop.org
Reporter: arekm at maven.pl
QA Contact: intel-gfx-bugs at lists.freedesktop.org
CC: intel-gfx-bugs at lists.freedesktop.org
Created attachment 140000
--> https://bugs.freedesktop.org/attachment.cgi?id=140000&action=edit
xorg log
xserver 1.20, kernel 4.17 and modesetting fails:
[ 126.170] (EE) modeset(0): failed to set mode: Invalid argument
while it works fine on 4.16 kernel.
Bisected to commit below and indeed, reverting it on current
kernel git makes the problem go away.
commit e995ca0b8139c5f6807095464e969931b443f55a
Author: Ville Syrjälä <ville.syrjala at linux.intel.com>
Date: Tue Nov 14 20:32:58 2017 +0200
drm/i915: Provide a device level .mode_valid() hook
We never support certain mode flags etc. Reject those early on in the
mode_config.mode_valid() hook. That allows us to remove some duplicated
checks from the connector .mode_valid() hooks, and it guarantees that
we never see those flags even from user mode as the
mode_config.mode_valid() hooks gets executed for those as well.
Signed-off-by: Ville Syrjälä <ville.syrjala at linux.intel.com>
Link:
https://patchwork.freedesktop.org/patch/msgid/20171114183258.16976-11-ville.syrjala@linux.intel.com
Reviewed-by: Daniel Vetter <daniel.vetter at ffwll.ch>
--
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee 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/20180604/dfd44748/attachment.html>
More information about the intel-gfx-bugs
mailing list