[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.LRH.2.02.1808061008520.9697@file01.intranet.prod.int.rdu2.redhat.com>
Date: Mon, 6 Aug 2018 10:13:19 -0400 (EDT)
From: Mikulas Patocka <mpatocka@...hat.com>
To: Marcin Wojtas <mw@...ihalf.com>
cc: Ard Biesheuvel <ard.biesheuvel@...aro.org>,
Robin Murphy <robin.murphy@....com>,
Thomas Petazzoni <thomas.petazzoni@...e-electrons.com>,
Joao Pinto <Joao.Pinto@...opsys.com>,
Catalin Marinas <catalin.marinas@....com>,
linux-pci@...r.kernel.org, Will Deacon <will.deacon@....com>,
Russell King - ARM Linux <linux@...linux.org.uk>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Matt Sealey <neko@...uhatsu.net>,
Jingoo Han <jingoohan1@...il.com>,
linux-arm-kernel@...ts.infradead.org
Subject: Re: framebuffer corruption due to overlapping stp instructions on
arm64
On Mon, 6 Aug 2018, Marcin Wojtas wrote:
> > Hi Marcin,
> >
> > Could you please try running his reproducer?
>
> This is exactly what I plan to do, as soon as I can plug my GFX card
> back to the board (tomorrow). Just to remain aligned - is it ok, if I
> boot my debian with GT630 plugged, compile the program with -O2 and
> simlply run it on /dev/fb0?
>
> Best regards,
> Marcin
Yes - when you run it, don't switch consoles (it will obviously trigger
false warning), don't move the mouse to the upper left corner, and if you
want to run it in the long term, turn off console blanking.
Mikulas
Powered by blists - more mailing lists