Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932162Ab3GBFbo (ORCPT ); Tue, 2 Jul 2013 01:31:44 -0400 Received: from mail-wi0-f176.google.com ([209.85.212.176]:54437 "EHLO mail-wi0-f176.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932097Ab3GBFbm (ORCPT ); Tue, 2 Jul 2013 01:31:42 -0400 MIME-Version: 1.0 Reply-To: sedat.dilek@gmail.com In-Reply-To: References: Date: Tue, 2 Jul 2013 07:31:41 +0200 Message-ID: Subject: Re: linux-next: Tree for Jul 1 [ drm-intel-next: Several call-traces ] From: Sedat Dilek To: Daniel Vetter Cc: "Barnes, Jesse" , Stephen Rothwell , linux-next , Linux Kernel Mailing List , intel-gfx , DRI , Dave Airlie Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2447 Lines: 68 On Mon, Jul 1, 2013 at 11:03 AM, Sedat Dilek wrote: > On Mon, Jul 1, 2013 at 10:52 AM, Daniel Vetter wrote: >> On Mon, Jul 1, 2013 at 10:49 AM, Sedat Dilek wrote: >>> On Mon, Jul 1, 2013 at 9:59 AM, Stephen Rothwell wrote: >>>> Hi all, >>>> >>>> Changes since 20130628: >>>> >>>> The regulator tree gained a build failure so I used the version from >>>> next-20130628. >>>> >>>> The trivial tree gained a conflict against the fbdev tree. >>>> >>>> The arm-soc tree gained a conflict against the net-next tree. >>>> >>>> The akpm tree lost a few patches that turned up elsewhere and I removed 2 >>>> that were causing run time problems. >>>> >>> >>> [ CC drm and drm-intel folks ] >>> >>> [ Did not check any relevant MLs ] >>> >>> Please, see attached dmesg output. >> >> Clock mismatch, one for Jesse to figure out. Note that this patch is >> for 3.12, I simply haven't yet gotten around to properly split my >> patch queue so a few spilled into -next. I'll do that now. > > I like lightspeed-fast replies :-). > > Guess "drm/i915: get mode clock when reading the pipe config v9" [1] > is the cause. > Problem solved by applying these patches to next-20130701 from intel-gfx patchwork-service [0]: [1/2] drm/i915: fixup messages in pipe_config_compare [2/2] drm/i915: get clock config when checking CRTC state too AFAICS 2/2 was folded into updated "drm/i915: get mode clock when reading the pipe config v9" [3]. It would be kind to be CCed on the patches and get also some credits. Also a CC to the report in linux-next should IMHO be done. - Sedat - [0] https://patchwork.kernel.org/project/intel-gfx/list/ [1] https://patchwork.kernel.org/patch/2809031/ [2] https://patchwork.kernel.org/patch/2809021/ [3] http://cgit.freedesktop.org/~danvet/drm-intel/commit/?h=drm-intel-nightly&id=f1f644dc66cbaf5a4c7dcde683361536b41885b9 > - Sedat - > > [1] http://cgit.freedesktop.org/~danvet/drm-intel/commit/?h=drm-intel-next-queued&id=d325d8b4f351f9d45e7c8baabf581fd21f343133 > >> -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/