From: Thomas Hellstrom <thellstrom@vmware.com>
To: Daniel Vetter <daniel@ffwll.ch>
Cc: Thomas Meyer <thomas@m3y3r.de>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
DRI mailing list <dri-devel@lists.freedesktop.org>
Subject: Re: [i915] BUG: Bad page state in process Xorg
Date: Fri, 22 Nov 2013 18:06:03 +0100 [thread overview]
Message-ID: <528F8EFB.4040400@vmware.com> (raw)
In-Reply-To: <CAKMK7uEHo3N-R5W6m_-gyEkuq0WPN=YUzJUpdG=MeznPcY2Haw@mail.gmail.com>
On 11/22/2013 05:18 PM, Daniel Vetter wrote:
> On Fri, Nov 22, 2013 at 4:54 PM, Thomas Meyer <thomas@m3y3r.de> wrote:
>>> Am 22.11.2013 um 11:55 schrieb Daniel Vetter <daniel@ffwll.ch>:
>>>
>>> On Fri, Nov 22, 2013 at 11:36 AM, Dave Airlie <airlied@linux.ie> wrote:
>>>>> Hi,
>>>> cc'ing mailing list,
>>>>
>>>> Daniel any ideas?
>>> Nope, not really :( And no ideas how to triage this further - if it
>>> takes 9 days to hit it eventually we'll have a real hard time. Or does
>>> this happen even after just a short X run?
>> Seems to happen every time while stopping the x server. Also after a short run time.
>>
>> The current fedora 3.11 kernel doesn't show this bug. I'm using fedora 19, with a self compiled kernel.
>>
>> I did turn on config-debug-pagealloc but this didn't show any wrongness.
> In that case I think the bisect is the fastest way to insight - atm
> I'm really at loss what could be wrong here.
From the error messages it looks like whatever's responsible for
clearing page->mapping doesn't do it for these pages,
(shmem code?).
/Thomas
> -Daniel
next prev parent reply other threads:[~2013-11-22 17:06 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-20 20:55 [i915] BUG: Bad page state in process Xorg Thomas Meyer
2013-11-22 10:36 ` Dave Airlie
2013-11-22 10:55 ` Daniel Vetter
2013-11-22 15:54 ` Thomas Meyer
2013-11-22 16:18 ` Daniel Vetter
2013-11-22 17:06 ` Thomas Hellstrom [this message]
2013-11-22 10:55 ` Chris Wilson
2013-11-22 15:56 ` Thomas Meyer
-- strict thread matches above, loose matches on Subject: below --
2013-11-25 13:17 thomas
2013-11-25 13:23 ` Rob Clark
2013-11-30 8:33 ` Thomas Meyer
2013-11-30 13:55 ` Rob Clark
2013-12-04 22:33 ` Thomas Meyer
2013-11-16 13:46 ^[[i915] " Thomas Meyer
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=528F8EFB.4040400@vmware.com \
--to=thellstrom@vmware.com \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=thomas@m3y3r.de \
/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