Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932721AbbGHH3m (ORCPT ); Wed, 8 Jul 2015 03:29:42 -0400 Received: from mail-wg0-f50.google.com ([74.125.82.50]:35233 "EHLO mail-wg0-f50.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932515AbbGHH3d (ORCPT ); Wed, 8 Jul 2015 03:29:33 -0400 Date: Wed, 8 Jul 2015 09:32:18 +0200 From: Daniel Vetter To: Michal Hocko Cc: Daniel Vetter , Jani Nikula , Ander Conselvan de Oliveira , LKML , dri-devel@lists.freedesktop.org, "intel-gfx@lists.freedesktop.org" , "Roper, Matthew D" Subject: Re: WARNING: CPU: 0 PID: 3634 at drivers/gpu/drm/drm_irq.c:1141 drm_wait_one_vblank Message-ID: <20150708073218.GA7568@phenom.ffwll.local> Mail-Followup-To: Michal Hocko , Jani Nikula , Ander Conselvan de Oliveira , LKML , dri-devel@lists.freedesktop.org, "intel-gfx@lists.freedesktop.org" , "Roper, Matthew D" References: <20150630115707.GA4578@dhcp22.suse.cz> <20150630143249.GA30960@phenom.ffwll.local> <20150630160743.GA4590@dhcp22.suse.cz> <20150630165929.GB30960@phenom.ffwll.local> <20150630201335.GA4496@dhcp22.suse.cz> <20150701082639.GE30960@phenom.ffwll.local> <20150701121241.GB5010@dhcp22.suse.cz> <87twtoukvo.fsf@intel.com> <20150707084358.GS7568@phenom.ffwll.local> <20150708064017.GA5335@dhcp22.suse.cz> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20150708064017.GA5335@dhcp22.suse.cz> X-Operating-System: Linux phenom 4.0.0-rc3+ User-Agent: Mutt/1.5.23 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1161 Lines: 28 On Wed, Jul 08, 2015 at 08:40:17AM +0200, Michal Hocko wrote: > I have just tried to boot 4.2-rc1 and cannot seem to reproduce the issue > anymore. > > On Tue 07-07-15 10:43:58, Daniel Vetter wrote: > [...] > > Can you please > > boot with drm.debug=0xf (lots more nois in dmesg with this) and reproduce? > > I only need the last few pages before the WARNING backtrace, just to > > understand a bit better what's going on there. > > And 0xf debug level seem to paper over the problem because I do not see > the warning even with 4.1 where I am able to reproduce this reliably. > This suggests this is a timing sensitive issue. Ok that's starting to get nasty. Can you please test what happens when you boot with drm.vblankoffdelay=0 and whether drm.vblankoffdelay=1000 has an effect on reproduction rate? No debug output needed. -Daniel -- Daniel Vetter Software Engineer, Intel Corporation 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/