Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1758142Ab3GZIwJ (ORCPT ); Fri, 26 Jul 2013 04:52:09 -0400 Received: from mail-oa0-f44.google.com ([209.85.219.44]:63913 "EHLO mail-oa0-f44.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753446Ab3GZIwB (ORCPT ); Fri, 26 Jul 2013 04:52:01 -0400 MIME-Version: 1.0 X-Originating-IP: [178.83.130.250] In-Reply-To: <20130726085035.GJ13295@cantiga.alporthouse.com> References: <20130725192248.GA13295@cantiga.alporthouse.com> <20130725215259.GB13295@cantiga.alporthouse.com> <20130725232556.GF13295@cantiga.alporthouse.com> <20130726072646.GH13295@cantiga.alporthouse.com> <20130726085035.GJ13295@cantiga.alporthouse.com> Date: Fri, 26 Jul 2013 10:52:00 +0200 Message-ID: Subject: Re: [Intel-gfx] linux-next: Tree for Jul 25 [ call-trace: drm | drm-intel related? ] From: Daniel Vetter To: Chris Wilson , Sedat Dilek , Daniel Vetter , Jani Nikula , Stephen Rothwell , intel-gfx , Linux Kernel Mailing List , DRI , linux-next Content-Type: text/plain; charset=ISO-8859-1 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1092 Lines: 29 On Fri, Jul 26, 2013 at 10:50 AM, Chris Wilson 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 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 -- 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/