Summary: | [bisected drm-intel-next] kernel oops when start compiz | ||||||
---|---|---|---|---|---|---|---|
Product: | DRI | Reporter: | wang,jinjin <jinjin.wang> | ||||
Component: | DRM/Intel | Assignee: | Chris Wilson <chris> | ||||
Status: | CLOSED FIXED | QA Contact: | |||||
Severity: | normal | ||||||
Priority: | medium | CC: | daniel, jbarnes, linux | ||||
Version: | unspecified | ||||||
Hardware: | All | ||||||
OS: | Linux (All) | ||||||
Whiteboard: | |||||||
i915 platform: | i915 features: | ||||||
Attachments: |
|
Description
wang,jinjin
2010-11-01 02:06:41 UTC
Platform? Looks like one of the self-checks for the mappable+fencing failed. I tested it on Pineview 32bit Created attachment 39995 [details] [review] drop map/fence distinction Does this patch help? Applied on top of 8c1812ad4 (Merge branch 'drm-intel-fixes' into drm-intel-next) and work for me. (Asus eeepc 1005he, graphics 945gm) I patched it to Kernel: (drm-intel-next)27153f72d04bcd83b3a66e219418a21d6269553b and tested it worked for me.So, the issue will not happen now. I am sorry. I tested the newest commit commit 27153f72d04bcd83b3a66e219418a21d6269553b Author: Chris Wilson <chris@chris-wilson.co.uk> Date: Tue Nov 2 11:17:23 2010 +0000 It had not been patched, so the issue still had. So, I wil reopen it firstly and verify the commit patched later. commit 085ce2643713830cf772c12c1a16da9d0ba83f36 Author: Chris Wilson <chris@chris-wilson.co.uk> Date: Wed Nov 3 09:27:53 2010 +0000 drm/i915: Ensure that if we ever try to pin+fence it is mappable. When merging Daniel's full-gtt patches I had a set of tweaks which I thought I had undone. I was half right... Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=31286 Reported-by: jinjin.wang@intel.com Reported-by: Alexey Fisher <bug-track@fisher-privat.net> Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk> With the 085ce2643713830cf772c12c1a16da9d0ba83f36 , the issue will be fixed. Closing old verified. |
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.