All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 205521] 5.3.11 update broke AMDGPU Raven Ridge
Date: Fri, 15 Nov 2019 16:07:49 +0000	[thread overview]
Message-ID: <bug-205521-2300-dvXI8ki9FQ@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-205521-2300@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=205521

Luya Tshimbalanga (luya@fedoraproject.org) changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|---                         |UNREPRODUCIBLE

--- Comment #5 from Luya Tshimbalanga (luya@fedoraproject.org) ---
I am closing this report for now as I reinstalled the system. The update
proceeded normally with the result:

sudo lsinitrd /boot/initramfs-5.3.11-300.fc31.x86_64.img | grep raven           
-rw-r--r--   2 root     root        86528 Jul 24 15:24
usr/lib/firmware/amdgpu/raven2_asd.bin
-rw-r--r--   1 root     root         9344 Jul 24 15:24
usr/lib/firmware/amdgpu/raven2_ce.bin
-rw-r--r--   1 root     root          316 Jul 24 15:24
usr/lib/firmware/amdgpu/raven2_gpu_info.bin
-rw-r--r--   1 root     root        17536 Jul 24 15:24
usr/lib/firmware/amdgpu/raven2_me.bin
-rw-r--r--   2 root     root       268048 Jul 24 15:24
usr/lib/firmware/amdgpu/raven2_mec2.bin
-rw-r--r--   2 root     root            0 Jul 24 15:24
usr/lib/firmware/amdgpu/raven2_mec.bin
-rw-r--r--   1 root     root        21632 Jul 24 15:24
usr/lib/firmware/amdgpu/raven2_pfp.bin
-rw-r--r--   1 root     root        38324 Jul 24 15:24
usr/lib/firmware/amdgpu/raven2_rlc.bin
-rw-r--r--   1 root     root        17408 Jul 24 15:24
usr/lib/firmware/amdgpu/raven2_sdma.bin
-rw-r--r--   1 root     root       343456 Jul 24 15:24
usr/lib/firmware/amdgpu/raven2_vcn.bin
-rw-r--r--   1 root     root        78336 Jul 24 15:24
usr/lib/firmware/amdgpu/raven_asd.bin
-rw-r--r--   1 root     root         9344 Jul 24 15:24
usr/lib/firmware/amdgpu/raven_ce.bin
-rw-r--r--   1 root     root        23152 Jul 24 15:24
usr/lib/firmware/amdgpu/raven_dmcu.bin
-rw-r--r--   2 root     root          316 Jul 24 15:24
usr/lib/firmware/amdgpu/raven_gpu_info.bin
-rw-r--r--   1 root     root        39084 Jul 24 15:24
usr/lib/firmware/amdgpu/raven_kicker_rlc.bin
-rw-r--r--   1 root     root        17536 Jul 24 15:24
usr/lib/firmware/amdgpu/raven_me.bin
-rw-r--r--   2 root     root       268048 Jul 24 15:24
usr/lib/firmware/amdgpu/raven_mec2.bin
-rw-r--r--   2 root     root            0 Jul 24 15:24
usr/lib/firmware/amdgpu/raven_mec.bin
-rw-r--r--   1 root     root        21632 Jul 24 15:24
usr/lib/firmware/amdgpu/raven_pfp.bin
-rw-r--r--   1 root     root        39084 Jul 24 15:24
usr/lib/firmware/amdgpu/raven_rlc.bin
-rw-r--r--   2 root     root        17408 Jul 24 15:24
usr/lib/firmware/amdgpu/raven_sdma.bin
-rw-r--r--   2 root     root       341728 Jul 24 15:24
usr/lib/firmware/amdgpu/raven_vcn.bin

It appears dracut somehow managed to not install the firmware prior to the
failure. I can no longer reproduce it with a reinstall.

-- 
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

      parent reply	other threads:[~2019-11-15 16:07 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-14  6:15 [Bug 205521] New: 5.3.11 update broke AMDGPU Raven Ridge bugzilla-daemon
2019-11-14  6:16 ` [Bug 205521] " 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 [this message]

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-dvXI8ki9FQ@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.