linux-kernel - Re: v4.18-rc2 on droid4: screen turns red

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: <20180717062608.GY99251@atomide.com>
Date:   Mon, 16 Jul 2018 23:26:08 -0700
From:   Tony Lindgren <tony@...mide.com>
To:     Pavel Machek <pavel@....cz>
Cc:     kernel list <linux-kernel@...r.kernel.org>,
        linux-arm-kernel <linux-arm-kernel@...ts.infradead.org>,
        linux-omap@...r.kernel.org, sre@...nel.org, nekit1000@...il.com,
        mpartap@....net, merlijn@...zup.org
Subject: Re: v4.18-rc2 on droid4: screen turns red

* Pavel Machek <pavel@....cz> [180711 10:30]:
> Hi!
> 
> > After longer inactivity, attempt to wake up the screen results in
> > screen being completely red. Not too useful. I can still connect over
> > ssh.
> 
> Still there in -rc4 :-(. But happens only once in a few days for me...
> 
> When X is shut down, text console works ok.

FYI, I've been chasing an occasional hang with lapdock and it might
be related to the usb phy switching between usb and uart mode
spontaneously. And then the usb traffic can cause a sysrq trigger
potentially when the glitch happens. Not sure yet why it happens, it
might be related to lost cpcap interrupts still.

Anyways, so far looks like doing the following may have prevented
it. Well at least for about four days of uptime now:

# echo 0 > /proc/sys/kernel/sysrq

And no red screens here yet either. Care to check if this might
somehow also prevent your red screen issue?

Regards,

Tony