linux-kernel - Re: nouveau graphical corruption in 3.13.2

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CAKb7UvjkHsGZ_NbEFpV1pL04uMPtiOvcJAHt3m3VNvkjeNWFXA@mail.gmail.com>
Date:	Sat, 22 Feb 2014 22:48:23 -0500
From:	Ilia Mirkin <imirkin@...m.mit.edu>
To:	Daniel J Blueman <daniel@...ra.org>
Cc:	Ben Skeggs <bskeggs@...hat.com>, Dave Airlie <airlied@...ux.ie>,
	"nouveau@...ts.freedesktop.org" <nouveau@...ts.freedesktop.org>,
	"dri-devel@...ts.freedesktop.org" <dri-devel@...ts.freedesktop.org>,
	Linux Kernel <linux-kernel@...r.kernel.org>,
	Maarten Lankhorst <maarten.lankhorst@...onical.com>,
	Marcin Slusarz <marcin.slusarz@...il.com>
Subject: Re: nouveau graphical corruption in 3.13.2

On Sat, Feb 22, 2014 at 10:45 PM, Daniel J Blueman <daniel@...ra.org> wrote:
> On 9 February 2014 02:57, Ilia Mirkin <imirkin@...m.mit.edu> wrote:
>> On Sat, Feb 8, 2014 at 10:38 AM, Daniel J Blueman <daniel@...ra.org> 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?
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/