From: Pavel Machek <pavel@ucw.cz>
To: Tony Lindgren <tony@atomide.com>
Cc: kernel list <linux-kernel@vger.kernel.org>,
linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
linux-omap@vger.kernel.org, sre@kernel.org, nekit1000@gmail.com,
mpartap@gmx.net, merlijn@wizzup.org
Subject: Re: v4.18-rc2 on droid4: screen turns red
Date: Wed, 1 Aug 2018 20:58:29 +0200 [thread overview]
Message-ID: <20180801185829.GD26087@amd> (raw)
In-Reply-To: <20180717062608.GY99251@atomide.com>
[-- Attachment #1: Type: text/plain, Size: 1260 bytes --]
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?
Looks like red screens are pretty seldom :-(. I did not see it since
that report. (But I stopped using Droid 4 as my primary phone after it
lost some SMS.)
Best regards,
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
prev parent reply other threads:[~2018-08-01 18:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-30 13:18 v4.18-rc2 on droid4: screen turns red Pavel Machek
2018-07-11 10:26 ` Pavel Machek
2018-07-11 10:58 ` Marcel Partap (unterwegs)
2018-07-11 13:39 ` Tony Lindgren
2018-07-17 6:26 ` Tony Lindgren
2018-08-01 18:58 ` Pavel Machek [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180801185829.GD26087@amd \
--to=pavel@ucw.cz \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=merlijn@wizzup.org \
--cc=mpartap@gmx.net \
--cc=nekit1000@gmail.com \
--cc=sre@kernel.org \
--cc=tony@atomide.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).