From: bugzilla-daemon@kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 220554] New: Display powers off after every update.
Date: Mon, 08 Sep 2025 23:51:03 +0000 [thread overview]
Message-ID: <bug-220554-2300@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=220554
Bug ID: 220554
Summary: Display powers off after every update.
Product: Drivers
Version: 2.5
Hardware: ARM
OS: Linux
Status: NEW
Severity: normal
Priority: P3
Component: Video(DRI - non Intel)
Assignee: drivers_video-dri@kernel-bugs.osdl.org
Reporter: vicencb@gmail.com
Regression: No
The behaviour happens since 6.17. Tested on rc2 and rc5.
It does not happen on 6.16.
The platform is gru/kevin (arm64,RK3399) with the Panfrost DRM driver.
When it boots in console mode, the blinking of the cursor keeps the display on.
If it is turned off via /sys/class/graphics/fbcon/cursor_blink, then the
display briefly shows each key press presented on screen for less than one
second and then powers off.
When starting the graphical mode (wayland), if there are no applications
drawing on the screen, the only way to keep the display on is by continuously
moving the mouse.
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
next reply other threads:[~2025-09-08 23:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-08 23:51 bugzilla-daemon [this message]
2025-09-08 23:53 ` [Bug 220554] Display powers off after every update bugzilla-daemon
2025-09-09 18:15 ` bugzilla-daemon
2025-09-09 21:33 ` bugzilla-daemon
2025-09-09 21:45 ` bugzilla-daemon
2025-09-09 21:47 ` bugzilla-daemon
2025-09-10 18:28 ` bugzilla-daemon
2025-09-10 18:29 ` bugzilla-daemon
2025-09-10 21:56 ` 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-220554-2300@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@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.