From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 203627] New: [Regression] Boot fails with linux-firmware 20190514
Date: Fri, 17 May 2019 04:39:18 +0000 [thread overview]
Message-ID: <bug-203627-2300@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=203627
Bug ID: 203627
Summary: [Regression] Boot fails with linux-firmware 20190514
Product: Drivers
Version: 2.5
Kernel Version: 4.19.44
Hardware: All
OS: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: Video(DRI - non Intel)
Assignee: drivers_video-dri@kernel-bugs.osdl.org
Reporter: mezin.alexander@gmail.com
Regression: No
After commit
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=2579167548be33afb1fe2a9a5c141561ee5a8bbe
system doesn't boot anymore with kernels 4.19.x (at least 4.19.40 and 4.19.44).
5.1 boots fine.
Displays turn off early when amdgpu driver loads, never turn on again. Can't
reach the system over ssh. Also can't get any logs from journald (that boot
attempt just doesn't get recorded)
GPU: RX Vega 64 (Sapphire Nitro+)
Dual 4K displays connected over DisplayPort
--
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-05-17 4:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-17 4:39 bugzilla-daemon [this message]
2019-05-17 4:39 ` [Bug 203627] [Regression] Boot fails with linux-firmware 20190514 bugzilla-daemon
2019-05-23 1:39 ` bugzilla-daemon
2019-05-26 3:29 ` bugzilla-daemon
2019-05-27 18:38 ` bugzilla-daemon
2019-06-01 0:31 ` bugzilla-daemon
2019-06-12 2:47 ` 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-203627-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 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).