4.4 kernel since Chrome OS release 61 stopped working on Intel Gen3/4 GPUs
Reported by
kr...@flintos.io,
Dec 31 2017
|
||||
Issue descriptionChrome Version: 61.0.3163.140 Chrome OS Version: 9765.89.0 Chrome OS Platform: N/A Network info: N/A We are building images based on the amd64-generic board for old machines. Those machines have old Intel Gen3/4 GPUs, some with GMA 3150 and some with GMA 4500(8086:2a42). They worked without problem with R59/60. But since R61, they booted up into black screen and the OOBE screen never showed up. We cannot switch to frecon via Ctrl+Alt+F2, or reaching the system via network. We did some diagnostic work and found out that the problem was caused by the kernel(4.4) in R61. We built a hybrid image with the 4.4 kernel from R60 and reset of the part from R61, it worked. So it seems the changes of i915 DRM driver between R60 and R61 caused the problem. Steps To Reproduce: (1) Build amd64-generic board from R61 source (2) Boot the image on the system with Intel Gen3/4 GPUs (3) Expected Result: Boot into OOBE screen, like R60 did. Actual Result: Black screen. How frequently does this problem reproduce? (Always, sometimes, hard to reproduce?) Always. What is the impact to the user, and is there a workaround? If so, what is it? Not able to boot into OS. No workaround. Please provide any additional information below. Attach a screen shot or log if possible. For graphics-related bugs, please copy/paste the contents of the about:gpu page at the end of this report.
,
Jan 4 2018
We found via git bisect that since commit 0ad20c68470c5e19b1bded2ecf3257ee146e6809 this issue appeared. commit 0ad20c68470c5e19b1bded2ecf3257ee146e6809 Author: Chris Wilson <chris@chris-wilson.co.uk> Date: Fri Jul 1 17:23:28 2016 +0100 UPSTREAM: drm/i915: Simplify enabling user-interrupts with L3-remapping Borrow the idea from intel_lrc.c to precompute the mask of interrupts we wish to always enable to avoid having lots of conditionals inside the interrupt enabling. Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk> Reviewed-by: Tvrtko Ursulin <tvrtko.ursulin@intel.com> Link: http://patchwork.freedesktop.org/patch/msgid/1467390209-3576-19-git-send-email-chris@chris-wilson.co.uk (cherry picked from commit 61ff75ac20ffa6d0039f643234d0c5244070fb15) from drm-intel-next-2016-07-11 Signed-off-by: Tarun <tarun.vyas@intel.com> BUG=b:36446508 TEST=No regressions in KBL and APL based devices Change-Id: I5cfed9bb555c6151a84e8eefa0d826a8a7544a3f Reviewed-on: https://chromium-review.googlesource.com/460295 Commit-Ready: Sean Paul <seanpaul@chromium.org> Tested-by: Sean Paul <seanpaul@chromium.org> Reviewed-by: Sean Paul <seanpaul@chromium.org>
,
Jan 9 2018
,
Jan 9 2018
,
Jan 9 2018
Gen3 GPUs are deprecated from Chrome OS at this point. Per our support policy: https://support.google.com/chrome/a/answer/6220366?hl=en You can see that the Gen3-based devices (aka AC700, Chromebook Series 5 and of course Cr-48) are all end of life. We never shipped gen4 and gen5 devices, so these were never supported. So we have removed support for these completely, sorry.
,
Jan 11 2018
Sad to hear so. Anyway thanks for pointing this out. |
||||
►
Sign in to add a comment |
||||
Comment 1 by dtapu...@chromium.org
, Jan 2 2018