dri-devel.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 109206] Kernel 4.20 amdgpu fails to load firmware on Ryzen 2500U
Date: Wed, 22 May 2019 08:42:01 +0000	[thread overview]
Message-ID: <bug-109206-502-VDgOpcQ1LV@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-109206-502@http.bugs.freedesktop.org/>


[-- Attachment #1.1: Type: text/plain, Size: 2249 bytes --]

https://bugs.freedesktop.org/show_bug.cgi?id=109206

--- Comment #44 from Ondrej Lang <ondrej@lang.sk> ---
Created attachment 144316
  --> https://bugs.freedesktop.org/attachment.cgi?id=144316&action=edit
Kernel log 5.1.3 showing amdgpu drm crash

Experiencing the same problem. On boot with any kernel > 4.20, the graphics is
not initialized, few scrambled lines appear at the bottom of the screen and
then the screen goes blank. The system actually boots as when I entered my
credentials (on the black screen) and did "cat dmesg > dmesg.txt", when I
rebooted with kernel 4.19 the file was there (I have attached it to this
thread). The relevant portion of the dmesg log is:

[    5.133929] [drm] REG_WAIT timeout 1us * 100000 tries -
mpc1_assert_idle_mpcc line:103
[    5.134034] WARNING: CPU: 2 PID: 367 at
drivers/gpu/drm/amd/amdgpu/../display/dc/dc_helper.c:277
generic_reg_wait.cold.0+0x29/0x30 [amdgpu]
...
[    5.134925]  drm_dev_register+0x111/0x150 [drm]
[    5.135335] [drm] Display Core initialized with v3.2.17!
[    5.642999] [drm:hwss_edp_wait_for_hpd_ready [amdgpu]] *ERROR*
hwss_edp_wait_for_hpd_ready: wait timed out!
[    6.142512] [drm:hwss_edp_wait_for_hpd_ready [amdgpu]] *ERROR*
hwss_edp_wait_for_hpd_ready: wait timed out!
[    6.143119] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
[    6.143121] [drm] Driver supports precise vblank timestamp query.
[    6.158613] [drm] VCN decode and encode initialized successfully(under SPG
Mode).
[    6.161822] [drm] Cannot find any crtc or sizes
[    6.188933] [drm] Initialized amdgpu 3.30.0 20150101 for 0000:04:00.0 on
minor 0

I can also confirm that as a workaround, removing/moving file
/lib/firmware/amdgpu/raven_dmcu.bin and regenerating the initramfs ("mkinitcpio
-p linux" on Arch linux) allows the 5.1.3 kernel to boot normally (I can also
start an X session and everything seems to be fine) and there are no drm errors
in dmesg anymore.

System:
HP ENVY x360 Convertible 15-bq1xx/83C6, BIOS F.20 12/25/2018
Kernel: 5.1.3-arch1-1-ARCH
Grub kernel parameters: amd_iommu=on iommu=pt idle=nomwait

If you need anything else let me know

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 3241 bytes --]

[-- Attachment #2: Type: text/plain, Size: 159 bytes --]

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  parent reply	other threads:[~2019-05-22  8:42 UTC|newest]

Thread overview: 72+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-01 17:20 [Bug 109206] Kernel 4.20 amdgpu fails to load firmware on Ryzen 2500U bugzilla-daemon
2019-01-01 17:25 ` bugzilla-daemon
2019-01-04 15:08 ` bugzilla-daemon
2019-01-04 21:59 ` bugzilla-daemon
2019-01-04 22:00 ` bugzilla-daemon
2019-01-14 14:17 ` bugzilla-daemon
2019-01-29 13:41 ` bugzilla-daemon
2019-01-31 21:35 ` bugzilla-daemon
2019-02-02 11:47 ` bugzilla-daemon
2019-02-02 16:32 ` bugzilla-daemon
2019-02-08 15:21 ` bugzilla-daemon
2019-02-13  1:48 ` bugzilla-daemon
2019-02-19  5:38 ` bugzilla-daemon
2019-02-19 11:26 ` bugzilla-daemon
2019-02-19 19:27 ` bugzilla-daemon
2019-02-19 20:36 ` bugzilla-daemon
2019-02-20  5:06 ` bugzilla-daemon
2019-02-20 21:07 ` bugzilla-daemon
2019-02-22 17:33 ` bugzilla-daemon
2019-02-22 21:27 ` bugzilla-daemon
2019-03-03 20:22 ` bugzilla-daemon
2019-03-05 19:24 ` bugzilla-daemon
2019-03-07  6:08 ` bugzilla-daemon
2019-03-07  6:12 ` bugzilla-daemon
2019-03-07  6:18 ` bugzilla-daemon
2019-03-07 11:07 ` bugzilla-daemon
2019-03-12  4:41 ` bugzilla-daemon
2019-03-12 15:20 ` bugzilla-daemon
2019-04-04 14:13 ` bugzilla-daemon
2019-04-04 18:27 ` bugzilla-daemon
2019-04-04 18:35 ` bugzilla-daemon
2019-04-08 13:18 ` bugzilla-daemon
2019-04-08 13:18 ` bugzilla-daemon
2019-04-08 18:52 ` bugzilla-daemon
2019-04-09 17:45 ` bugzilla-daemon
2019-04-14  2:29 ` bugzilla-daemon
2019-04-15 13:57 ` bugzilla-daemon
2019-04-25 15:55 ` bugzilla-daemon
2019-04-25 19:10 ` bugzilla-daemon
2019-04-25 23:01 ` bugzilla-daemon
2019-05-01 21:05 ` bugzilla-daemon
2019-05-02  3:17 ` bugzilla-daemon
2019-05-02  6:36 ` bugzilla-daemon
2019-05-03 20:20 ` bugzilla-daemon
2019-05-22  8:42 ` bugzilla-daemon [this message]
2019-05-27 16:43 ` bugzilla-daemon
2019-06-06 15:13 ` bugzilla-daemon
2019-06-07  9:15 ` bugzilla-daemon
2019-06-07 13:52 ` bugzilla-daemon
2019-06-11 16:56 ` bugzilla-daemon
2019-06-12  9:47 ` bugzilla-daemon
2019-06-15 11:57 ` bugzilla-daemon
2019-07-02 13:41 ` bugzilla-daemon
2019-07-11  9:52 ` bugzilla-daemon
2019-07-12  3:39 ` bugzilla-daemon
2019-07-12  7:49 ` bugzilla-daemon
2019-07-12 13:10 ` bugzilla-daemon
2019-07-12 15:24 ` bugzilla-daemon
2019-07-12 23:09 ` bugzilla-daemon
2019-07-13  9:41 ` bugzilla-daemon
2019-07-14 20:21   ` Mihai
2019-07-14 20:22 ` bugzilla-daemon
2019-07-18 14:10 ` bugzilla-daemon
2019-07-18 18:17 ` bugzilla-daemon
2019-07-29 14:02 ` bugzilla-daemon
2019-11-14  7:38 ` bugzilla-daemon
2019-11-14  7:41 ` [Bug 109206] Kernel 5.3.11 and onward amdgpu fails to load firmware on Raven Ridge bugzilla-daemon
2019-11-14 13:58 ` bugzilla-daemon
2019-11-14 14:51 ` bugzilla-daemon
2019-11-14 14:51 ` [Bug 109206] Kernel 4.20 amdgpu fails to load firmware on Ryzen 2500U bugzilla-daemon
2019-11-14 16:58 ` bugzilla-daemon
2019-11-16 12:27 ` 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-109206-502-VDgOpcQ1LV@http.bugs.freedesktop.org/ \
    --to=bugzilla-daemon@freedesktop.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).