From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 209401] New: arm64: display locks on rk3399 gru-kevin chromebook
Date: Sat, 26 Sep 2020 10:00:03 +0000 [thread overview]
Message-ID: <bug-209401-2300@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=209401
Bug ID: 209401
Summary: arm64: display locks on rk3399 gru-kevin chromebook
Product: Drivers
Version: 2.5
Kernel Version: 5.4 and up
Hardware: ARM
OS: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: Video(DRI - non Intel)
Assignee: drivers_video-dri@kernel-bugs.osdl.org
Reporter: mps@arvanta.net
Regression: No
on arm64 rockchip rk3399 chromebook gru-kevin display locks at random time,
sometimes few times on the day (2-3 times) but on some days it can happen 10
and more times. suspend2ram and resume unlock display and it works until next
random lock.
This behavior started on linux kernel version 5.4 and up. On 5.3 and lower
kernels this doesn't happen (at least I didn't noticed it anytime)
I'm attaching part from dmesg output which shows errors when the display locks
and goes blank (dark).
--
You are receiving this mail because:
You are watching the assignee of the bug.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next reply other threads:[~2020-09-26 10:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-26 10:00 bugzilla-daemon [this message]
2020-09-26 10:01 ` [Bug 209401] arm64: display locks on rk3399 gru-kevin chromebook bugzilla-daemon
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=bug-209401-2300@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=dri-devel@lists.freedesktop.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.