Messages in this thread | | | Date | Thu, 15 Mar 2012 10:49:14 -0400 | From | Dave Jones <> | Subject | Re: inode->i_wb_list corruption. |
| |
On Thu, Mar 15, 2012 at 10:08:03PM +0800, Petr Tesařík wrote:
> > i915_drm_thaw is a deep nest of functions though, so this is going to be > > hard to track down where that write is coming from. Because the corruption > > seems to happen to pages that are already allocated, we probably can't > > even rely on DEBUG_PAGEALLOC, though it might be worth trying. > > If it you believe it could be written by the CPU, I can try to catch the > instruction that writes to this memory. My plan is as follows:
Given that the corruption pattern looks like pixel data, it's likely that the writing is being done by the GPU, not the CPU, so debug registers won't trap it.
Dave
-- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |