From: Dave Jones <davej@redhat.com>
To: "Petr Tesařík" <petr@tesarici.cz>
Cc: Yang Bai <hamo.by@gmail.com>,
Fengguang Wu <fengguang.wu@intel.com>,
Linux Kernel <linux-kernel@vger.kernel.org>,
Fedora Kernel Team <kernel-team@fedoraproject.org>,
kernel@tesarici.cz
Subject: Re: inode->i_wb_list corruption.
Date: Thu, 15 Mar 2012 10:49:14 -0400 [thread overview]
Message-ID: <20120315144914.GB5409@redhat.com> (raw)
In-Reply-To: <201203152208.04168.petr@tesarici.cz>
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
next prev parent reply other threads:[~2012-03-15 14:49 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-15 14:08 inode->i_wb_list corruption Petr Tesařík
2012-03-15 14:22 ` Dave Airlie
2012-03-15 14:49 ` Dave Jones [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-03-06 18:51 Dave Jones
2012-03-06 21:03 ` Jan Kara
2012-03-07 7:26 ` Fengguang Wu
2012-03-07 10:42 ` Jan Kara
2012-03-09 8:34 ` Yang Bai
2012-03-09 14:57 ` Dave Jones
2012-03-09 15:19 ` Dave Jones
2012-03-09 16:14 ` Yang Bai
2012-03-09 18:00 ` Dave Jones
2012-03-09 20:08 ` Keith Packard
2012-03-09 20:19 ` Josh Boyer
2012-03-09 22:44 ` Keith Packard
2012-03-12 21:13 ` Josh Boyer
2012-03-12 21:27 ` David Woodhouse
2012-03-12 23:26 ` Dave Jones
2012-03-13 0:06 ` Keith Packard
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20120315144914.GB5409@redhat.com \
--to=davej@redhat.com \
--cc=fengguang.wu@intel.com \
--cc=hamo.by@gmail.com \
--cc=kernel-team@fedoraproject.org \
--cc=kernel@tesarici.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=petr@tesarici.cz \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.