linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: v4.18-rc2 on droid4: screen turns red
Date: Mon, 16 Jul 2018 23:26:08 -0700	[thread overview]
Message-ID: <20180717062608.GY99251@atomide.com> (raw)
In-Reply-To: <20180711102655.GA6864@amd>

* Pavel Machek <pavel@ucw.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

  parent reply	other threads:[~2018-07-17  6:26 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 [this message]
2018-08-01 18:58     ` Pavel Machek

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=20180717062608.GY99251@atomide.com \
    --to=tony@atomide.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    /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).