Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751810AbaDXGDh (ORCPT ); Thu, 24 Apr 2014 02:03:37 -0400 Received: from mail-ig0-f181.google.com ([209.85.213.181]:55689 "EHLO mail-ig0-f181.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751724AbaDXGDE (ORCPT ); Thu, 24 Apr 2014 02:03:04 -0400 MIME-Version: 1.0 X-Originating-IP: [84.73.67.144] In-Reply-To: <20140424055023.GA31221@nuc-i3427.alporthouse.com> References: <20140423202248.GA3621@amd.pavel.ucw.cz> <20140423220952.GA3627@amd.pavel.ucw.cz> <20140424055023.GA31221@nuc-i3427.alporthouse.com> Date: Thu, 24 Apr 2014 08:03:04 +0200 Message-ID: Subject: Re: 3.15-rc2: i915 regression: only top 20% of screen works in X From: Daniel Vetter To: Chris Wilson , Pavel Machek , Daniel Vetter , intel-gfx , "Rafael J. Wysocki" , dri-devel , kernel list , Jiri Kosina Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Apr 24, 2014 at 7:50 AM, Chris Wilson wrote: > That says that i915.ko failed to initialise the GPU (or rather the GPU > wasn't responding) and bailed during module load. The key line here is > > [drm:init_ring_common] *ERROR* render ring initialization failed ctl > 0001f001 head 00002034 tail 00000000 start 0012f000 > > Jiri has been seeing a similar issue creep in during resume, but it is > not reliable enough to bisect. Is your boot failure reliable enough to > bisect? Also drm-intel-nightly should mitigate this failure and allow > i915.ko to continue to load and run X, which would be worth testing to > make sure that works as intended. Oh right, g4x going beserk :( Apparently something changed in 3.15 somewhere which made this much more likely, but like Chris said in Jiri's case it's too unreliable to reproduce for a bisect. We've had this come&go pretty much ever since kms support was merged and never tracked it down. The bug is https://bugs.freedesktop.org/show_bug.cgi?id=76554 Like Chris said please test latest drm-intel-nighlty from http://cgit.freedesktop.org/drm-intel to make sure that the recently merged mitigation measures work properly. But those won't get your gpu back, only the display and it's only for 3.16. We're still hunting a proper fix for 3.15. And if you can indeed reliably reproduce this a bisect could be really useful. -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/