From: Daniel Vetter <daniel.vetter@ffwll.ch>
To: Chris Wilson <chris@chris-wilson.co.uk>,
Sedat Dilek <sedat.dilek@gmail.com>,
Daniel Vetter <daniel.vetter@ffwll.ch>,
Jani Nikula <jani.nikula@linux.intel.com>,
Stephen Rothwell <sfr@canb.auug.org.au>,
intel-gfx <intel-gfx@lists.freedesktop.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
DRI <dri-devel@lists.freedesktop.org>,
linux-next <linux-next@vger.kernel.org>
Subject: Re: [Intel-gfx] linux-next: Tree for Jul 25 [ call-trace: drm | drm-intel related? ]
Date: Fri, 26 Jul 2013 10:52:00 +0200 [thread overview]
Message-ID: <CAKMK7uGb5=-Ur4hJiVAviYeGKpup0ScHzsf436jHXEsKar+bCQ@mail.gmail.com> (raw)
In-Reply-To: <20130726085035.GJ13295@cantiga.alporthouse.com>
On Fri, Jul 26, 2013 at 10:50 AM, Chris Wilson <chris@chris-wilson.co.uk> wrote:
> On Fri, Jul 26, 2013 at 10:27:03AM +0200, Sedat Dilek wrote:
>> On Fri, Jul 26, 2013 at 10:25 AM, Sedat Dilek <sedat.dilek@gmail.com> wrote:
>> > ...
>> > ... but does not start as well, so it seems to be a kernel-issue as
>> > assumed (2nd confirmation).
>> >
>> > X.log attached.
>> >
>>
>> Now, really w/ promised attachment.
>
> Yes, same failure (GTT mmaps) but at a later point, and UXA has no
> fallback plan.
I'm running igt on my machines here to prep a new -next test cycle,
and gtt mmaps seem to fail across the board :( Currently I'd wager
that the vma offset manager is the culprit, since I've only recently
pulled that stuff in from drm-next.
-Daniel
--
Daniel Vetter
Software Engineer, Intel Corporation
+41 (0) 79 365 57 48 - http://blog.ffwll.ch
next prev parent reply other threads:[~2013-07-26 8:52 UTC|newest]
Thread overview: 57+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-25 8:54 linux-next: Tree for Jul 25 [ call-trace: drm | drm-intel related? ] Sedat Dilek
2013-07-25 9:44 ` [Intel-gfx] " Jani Nikula
2013-07-25 10:02 ` Sedat Dilek
2013-07-25 10:05 ` Sedat Dilek
2013-07-25 10:21 ` Jani Nikula
2013-07-25 10:37 ` Sedat Dilek
2013-07-25 10:37 ` Sedat Dilek
2013-07-25 13:36 ` [Intel-gfx] " Daniel Vetter
2013-07-25 14:23 ` Sedat Dilek
2013-07-25 14:27 ` Daniel Vetter
2013-07-25 15:03 ` Sedat Dilek
2013-07-25 15:05 ` Daniel Vetter
2013-07-25 15:34 ` Sedat Dilek
2013-07-25 16:11 ` Sedat Dilek
2013-07-25 16:31 ` Chris Wilson
2013-07-25 16:35 ` Sedat Dilek
2013-07-25 16:35 ` Sedat Dilek
2013-07-25 17:01 ` [Intel-gfx] " Chris Wilson
2013-07-25 17:15 ` Sedat Dilek
2013-07-25 17:15 ` Sedat Dilek
2013-07-25 17:26 ` [Intel-gfx] " Chris Wilson
2013-07-25 17:52 ` Sedat Dilek
2013-07-25 17:52 ` Sedat Dilek
2013-07-25 17:55 ` [Intel-gfx] " Sedat Dilek
2013-07-25 17:55 ` Sedat Dilek
2013-07-25 18:03 ` [Intel-gfx] " Sedat Dilek
2013-07-25 18:03 ` Sedat Dilek
2013-07-25 18:45 ` [Intel-gfx] " Chris Wilson
2013-07-25 18:50 ` Sedat Dilek
2013-07-25 19:00 ` Chris Wilson
2013-07-25 19:12 ` Sedat Dilek
2013-07-25 19:22 ` Chris Wilson
2013-07-25 19:32 ` Sedat Dilek
2013-07-25 20:07 ` Sedat Dilek
2013-07-25 21:52 ` Chris Wilson
2013-07-25 23:21 ` Sedat Dilek
2013-07-25 23:25 ` Chris Wilson
2013-07-26 7:15 ` Sedat Dilek
2013-07-26 7:26 ` Chris Wilson
2013-07-26 8:25 ` Sedat Dilek
2013-07-26 8:25 ` Sedat Dilek
2013-07-26 8:27 ` [Intel-gfx] " Sedat Dilek
2013-07-26 8:50 ` Chris Wilson
2013-07-26 8:52 ` Daniel Vetter [this message]
2013-07-26 9:02 ` Sedat Dilek
2013-07-26 9:11 ` Sedat Dilek
2013-07-26 9:16 ` Daniel Vetter
2013-07-26 9:24 ` [PATCH] drm/gem: fix mmap vma size calculations David Herrmann
2013-07-26 10:09 ` [PATCH v2] " David Herrmann
2013-07-26 20:15 ` Daniel Vetter
2013-07-30 7:41 ` Sedat Dilek
2013-07-30 7:52 ` Sedat Dilek
2013-07-31 16:46 ` David Herrmann
2013-07-31 17:13 ` Sedat Dilek
2013-07-26 9:32 ` [Intel-gfx] linux-next: Tree for Jul 25 [ call-trace: drm | drm-intel related? ] Sedat Dilek
2013-07-26 10:34 ` Sedat Dilek
2013-07-25 18:03 ` Chris Wilson
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='CAKMK7uGb5=-Ur4hJiVAviYeGKpup0ScHzsf436jHXEsKar+bCQ@mail.gmail.com' \
--to=daniel.vetter@ffwll.ch \
--cc=chris@chris-wilson.co.uk \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sedat.dilek@gmail.com \
--cc=sfr@canb.auug.org.au \
/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.