Summary: | [845g regression] machine lockup during KMS takeover | ||||||
---|---|---|---|---|---|---|---|
Product: | DRI | Reporter: | Chris Wilson <chris> | ||||
Component: | DRM/Intel | Assignee: | Ville Syrjala <ville.syrjala> | ||||
Status: | CLOSED FIXED | QA Contact: | Intel GFX Bugs mailing list <intel-gfx-bugs> | ||||
Severity: | blocker | ||||||
Priority: | high | CC: | intel-gfx-bugs | ||||
Version: | XOrg git | ||||||
Hardware: | Other | ||||||
OS: | All | ||||||
Whiteboard: | |||||||
i915 platform: | i915 features: | ||||||
Attachments: |
|
Description
Chris Wilson
2013-09-23 13:36:22 UTC
Created attachment 86374 [details] [review] One possible idea The bisect result is a bit odd since the patch in question doesn't change the places where we touch the hardware. The only real new bug I can immediately spot is the mode->clock in intel_crtc_mode_get(). Not sure if that's even relevant to this machine, but here's a patch to try anyway. That allow the machines to boot, I don't have a display yet, but that regression is already well known. Sigh. Looks like I compiled out fbcon a while back... So far it looks like it is working. Time to check suspend again. Fix merged: commit 1b44b14fc9504de74ab9ac5359a087d1377bb87e Author: Ville Syrjälä <ville.syrjala@linux.intel.com> Date: Mon Sep 23 17:48:20 2013 +0300 drm/i915: Fix intel_crtc_mode_get() mode clock |
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.