From: bugzilla-daemon@kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 216806] New: [Raven Ridge] console disappears after framebuffer device loads
Date: Tue, 13 Dec 2022 20:37:31 +0000 [thread overview]
Message-ID: <bug-216806-2300@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=216806
Bug ID: 216806
Summary: [Raven Ridge] console disappears after framebuffer
device loads
Product: Drivers
Version: 2.5
Kernel Version: 6.0.8
Hardware: AMD
OS: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: Video(DRI - non Intel)
Assignee: drivers_video-dri@kernel-bugs.osdl.org
Reporter: vinibali1@gmail.com
Regression: No
Created attachment 303402
--> https://bugzilla.kernel.org/attachment.cgi?id=303402&action=edit
dmesg - debug drm, no dc
I have an HP c645 Chromebook with Ryzen 3 3250C APU.
Everytime, when the FB/DRM loads and vgaconsole get's deactivated, the console
freezes. I tried many common kernel parameters so far with no luck.
By default it freezes back in the boot sequence,
using amdgpu.dc=0 it freezes after the tty shows the login text.
I attached the logs with debug drm flags, with disabling the Display Core
driver, the last message is some BT device load message and right after that I
found the DRM load.
--
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:[~2022-12-13 20:37 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-13 20:37 bugzilla-daemon [this message]
2022-12-13 20:42 ` [Bug 216806] [Raven Ridge] console disappears after framebuffer device loads bugzilla-daemon
2022-12-14 9:45 ` bugzilla-daemon
2022-12-14 15:02 ` bugzilla-daemon
2022-12-14 15:08 ` bugzilla-daemon
2022-12-21 13:56 ` bugzilla-daemon
2023-09-29 16:44 ` bugzilla-daemon
2023-09-30 10:33 ` bugzilla-daemon
2023-09-30 14:13 ` 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-216806-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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox