From: Dave Jones <davej@redhat.com>
To: Chris Mason <chris.mason@fusionio.com>,
Linux Kernel <linux-kernel@vger.kernel.org>,
Daniel Vetter <daniel.vetter@ffwll.ch>,
Chris Mason <clmason@fusionio.com>
Subject: Re: memory corruption, possibly caused by i915
Date: Wed, 2 Jan 2013 11:30:10 -0500 [thread overview]
Message-ID: <20130102163010.GB14219@redhat.com> (raw)
In-Reply-To: <20130102160115.GB12838@shiny>
On Wed, Jan 02, 2013 at 11:01:15AM -0500, Chris Mason wrote:
> > [52460.280346] BUG: Bad page map in process panel-6-systray pte:ffff8800b665a0e8 pmd:b6659067
> > [52460.280848] addr:00000038bf3fd000 vm_flags:00000070 anon_vma: (null) mapping:ffff88011052fd98 index:1fd
> > [52460.281547] vma->vm_ops->fault: filemap_fault+0x0/0x470
> > [52460.281878] vma->vm_file->f_op->mmap: btrfs_file_mmap+0x0/0x60 [btrfs]
> >
> > It's falling over in btrfs's mmap op, but I think it's just the victim here,
> > of something else corrupting what had been mmaped in the panel process.
>
> It's a btrfs file, but this isn't in our mmap op. The traces are
> finding bad pages at unmap time.
Sorry, bad wording on my part.
> > Daniel, can you think of additional sanity checks that could be added to
> > the i915 driver ? (Even if at the expense of speed: a CONFIG_DEBUG option
> > to prove correctness would be very worthwhile imo)
>
> If the bad pages are getting all the way to btrfs,
> CONFIG_DEBUG_PAGE_ALOC may help? You've got lockdep on so maybe you
> already enabled it.
Yeah, already enabled.
Thanks.
Dave.
next prev parent reply other threads:[~2013-01-02 16:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-02 15:52 memory corruption, possibly caused by i915 Dave Jones
2013-01-02 16:01 ` Chris Mason
2013-01-02 16:30 ` Dave Jones [this message]
2013-01-02 21:08 ` Hugh Dickins
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=20130102163010.GB14219@redhat.com \
--to=davej@redhat.com \
--cc=chris.mason@fusionio.com \
--cc=clmason@fusionio.com \
--cc=daniel.vetter@ffwll.ch \
--cc=linux-kernel@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox