linux-kernel - Re: Nouveau crashes in 4.6-rc on arm64

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]

Date:	Fri, 8 Apr 2016 02:27:31 -0400
From:	Ilia Mirkin <imirkin@...m.mit.edu>
To:	Alexandre Courbot <acourbot@...dia.com>
Cc:	Robin Murphy <robin.murphy@....com>,
	"dri-devel@...ts.freedesktop.org" <dri-devel@...ts.freedesktop.org>,
	linux-arm-kernel@...ts.infradead.org,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: Nouveau crashes in 4.6-rc on arm64

On Fri, Apr 8, 2016 at 12:47 AM, Alexandre Courbot <acourbot@...dia.com> wrote:
> Hi Robin,
>
> On 04/07/2016 08:50 PM, Robin Murphy wrote:
>>
>> Hello,
>>
>> With 4.6-rc2 (and -rc1) I'm seeing Nouveau blowing up at boot, from the
>> look of it by dereferencing some offset from NULL inside
>> nouveau_fbcon_imageblit(). My setup is an old XFX 7600GT card plugged
>> into an ARM Juno r1 board, which works fine with 4.5 and earlier.
>>
>> Attached are a couple of logs from booting arm64 defconfig plus DRM and
>> Nouveau enabled - the second also has framebuffer console rotation
>> turned on, which interestingly seems to move the point of failure, and
>> the display does eventually come up to show the tail end of the panic in
>> that case.
>>
>> I might be able to find time for a full bisection next week if isn't
>> something sufficiently obvious to anyone who knows this driver.
>
>
> Looking at the log it is not clear to me what could be causing this. I can
> boot 4.6-rc2 with a GM206 card without any issue. A bisect would indeed be
> useful here.

Presumably not on an arm64 board though. This is happening in the
memcpy done somewhere in fbcon, when doing an OUT_RINGp if the
backtrace is to be believed. This means that the fifo is somehow not
writable, or not set, or ... something. Also note that it's a G73 (aka
pre-G80), so very different paths being taken through the driver.

  -ilia