Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752579AbaBWEBN (ORCPT ); Sat, 22 Feb 2014 23:01:13 -0500 Received: from mail-oa0-f41.google.com ([209.85.219.41]:61680 "EHLO mail-oa0-f41.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752542AbaBWEBM (ORCPT ); Sat, 22 Feb 2014 23:01:12 -0500 MIME-Version: 1.0 X-Originating-IP: [42.61.198.132] In-Reply-To: References: Date: Sun, 23 Feb 2014 12:01:11 +0800 Message-ID: Subject: Re: nouveau graphical corruption in 3.13.2 From: Daniel J Blueman To: Ilia Mirkin Cc: Ben Skeggs , Dave Airlie , "nouveau@lists.freedesktop.org" , "dri-devel@lists.freedesktop.org" , Linux Kernel , Maarten Lankhorst , Marcin Slusarz 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 On 23 February 2014 11:48, Ilia Mirkin wrote: > On Sat, Feb 22, 2014 at 10:45 PM, Daniel J Blueman wrote: >> On 9 February 2014 02:57, Ilia Mirkin wrote: >>> On Sat, Feb 8, 2014 at 10:38 AM, Daniel J Blueman wrote: >>>> Interestingly, there was graphical failure booting 3.6.11, even >>>> nvidia-current fails to initialise, but these two issues could be due >>>> to running the Xorg stack in Ubuntu 14.04 pre-release. Using >>>> nouveau.noaccel=1 works great for the first X session, but after >>>> logging out, lightdm and the next session experiences this consistent >>>> screen corruption: >>>> >>>> http://quora.org/nouveau-corruption.jpg >>> >>> Does that just happen in 3.6.11 or even in 3.13? If the latter, that. >>> points to some key lack of understanding of... something. With >>> noaccel, we're not using pgraph or anything fancy -- it's just a >>> framebuffer, basically. So if we can't even render _that_ right... >>> >>> Hopefully someone else will pipe up re your other issues -- my >>> knowledge base on this is exhausted :( >> >> Interestingly, it turns out that the screen corruption occurs on every >> boot (booting with nouveau.noaccel=1 for now), and I can consistently >> work around it by one suspend-resume cycle. > > Does booting with nouveau.config=NvForcePost=1 help? Still no cigar with nouveau.config=NvForcePost=1. I meant to add that restarting X or changing resolutions doesn't resolve the issue. The corruption is consistently 16-pixel wide by 1 high stippling on a consistent address range of the framebuffer. Thanks, Daniel -- Daniel J Blueman -- 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/