From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 205521] New: 5.3.11 update broke AMDGPU Raven Ridge
Date: Thu, 14 Nov 2019 06:15:28 +0000 [thread overview]
Message-ID: <bug-205521-2300@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=205521
Bug ID: 205521
Summary: 5.3.11 update broke AMDGPU Raven Ridge
Product: Drivers
Version: 2.5
Kernel Version: 5.3.11 and up
Hardware: x86-64
OS: Linux
Tree: Mainline
Status: NEW
Severity: blocking
Priority: P1
Component: Video(DRI - non Intel)
Assignee: drivers_video-dri@kernel-bugs.osdl.org
Reporter: luya@fedoraproject.org
Regression: No
Created attachment 285903
--> https://bugzilla.kernel.org/attachment.cgi?id=285903&action=edit
dmesg reporting broken amd raven ridge firmware
AMD Raven Ridge firware is currently broken with the recent stable kernel
release resulting a blank screen on boot and preventing booting on the login
screen either graphical and text mode.
Extract from boot:
nov 13 13:53:55 kernel: amdgpu 0000:03:00.0: Direct firmware load for
amdgpu/raven_gpu_info.bin failed with error -2
nov 13 13:53:55 kernel: amdgpu 0000:03:00.0: Failed to load gpu_info firmware
"amdgpu/raven_gpu_info.bin"
nov 13 13:53:55 kernel: amdgpu 0000:03:00.0: Fatal error during GPU init
--
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:[~2019-11-14 6:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-14 6:15 bugzilla-daemon [this message]
2019-11-14 6:16 ` [Bug 205521] 5.3.11 update broke AMDGPU Raven Ridge bugzilla-daemon
2019-11-14 6:16 ` bugzilla-daemon
2019-11-14 7:40 ` bugzilla-daemon
2019-11-14 13:56 ` bugzilla-daemon
2019-11-14 16:58 ` bugzilla-daemon
2019-11-15 16:07 ` 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-205521-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.