[Kernel-packages] [Bug 2024427] Re: S3 stress issue for amdgpu Navi 31/Navi33

2023-10-07 Thread Jeroen Webb
My computer booted just fine with that file in /lib/firmware/amdgpu. I
downloaded it again after booting, just to make sure that it was the
right file version.

% ls -l /lib/firmware/amdgpu/gc_11_0_0_imu.bin 
-rw-r--r-- 1 root root 132352 Oct  7 09:36 
/lib/firmware/amdgpu/gc_11_0_0_imu.bin

% sha1sum /lib/firmware/amdgpu/gc_11_0_0_imu.bin
2587fa941d4645e5e38ce4067f630a5c6d51bc23  /lib/firmware/amdgpu/gc_11_0_0_imu.bin

% sha1sum Downloads/gc_11_0_0_imu\(1\).bin Downloads/gc_11_0_0_imu.bin 
2587fa941d4645e5e38ce4067f630a5c6d51bc23  Downloads/gc_11_0_0_imu(1).bin
2587fa941d4645e5e38ce4067f630a5c6d51bc23  Downloads/gc_11_0_0_imu.bin

% dpkg -l | grep firmware 
ii  amd64-microcode  
3.20191218.1ubuntu2.2 amd64 
   Processor microcode firmware for AMD CPUs
ii  firmware-sof-signed  2.0-1ubuntu4.1 
   all  Intel SOF 
firmware - signed
ii  intel-microcode  
3.20230808.0ubuntu0.22.04.1   amd64 
   Processor microcode firmware for Intel CPUs
ii  linux-firmware   
20220329.git681281e4-0ubuntu3.19  all   
   Firmware for Linux kernel drivers

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/2024427

Title:
  S3 stress issue for amdgpu Navi 31/Navi33

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Triaged
Status in linux-firmware package in Ubuntu:
  Fix Released
Status in linux-oem-6.1 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Invalid
Status in linux-firmware source package in Jammy:
  Fix Released
Status in linux-oem-6.1 source package in Jammy:
  Fix Released
Status in linux source package in Lunar:
  Fix Committed
Status in linux-firmware source package in Lunar:
  Fix Committed
Status in linux-oem-6.1 source package in Lunar:
  Invalid
Status in linux source package in Mantic:
  Triaged
Status in linux-firmware source package in Mantic:
  Fix Released
Status in linux-oem-6.1 source package in Mantic:
  Invalid

Bug description:
  [SRU Justification]

  BugLink: https://bugs.launchpad.net/bugs/2024427

  [Impact]

  Under stress testing it was reported that the amdgpu Navi31/Navi33 platforms
  will sometimes fail to wake from S3.

  [Fix]

  kernel patches:
  ac2f5739fdca drm/amdgpu/mes11: enable reg active poll
  a2fe4534bb38 drm/amd/amdgpu: update mes11 api def
  da9a8dc33da2 drm/amdgpu: reserve the old gc_11_0_*_mes.bin
  616843d5a11b drm/amd/amdgpu: introduce gc_*_mes_2.bin v2
  09bf14907d86 drm/amdgpu: declare firmware for new MES 11.0.4

  firmware patches:
  * Navi31: ffe1a41e2ddb amdgpu: update GC 11.0.0 firmware for amd.5.5 release
  * Navi33: a5d7b4df1a76 amdgpu: update GC 11.0.2 firmware for amd.5.5 release

  [Test Case]

  $ checkbox-cli run com.canonical.certification::stress-
  suspend-30-cycles-with-reboots-automated

  [Where problems could occur]

  Little we know about the firmware fixes. However, while with these commits 
have
  been pulled via stable kernel fixes, the driver begins to request new firmware
  blobs of a different filename.

  [Other Info]

  The kernel driver commits are in v6.4-rc1, backported to v6.3.4, v6.1.31, and
  partially (missing da9a8dc33da2, 616843d5a11b) v6.2.16. Only linux/lunar has 
to
  be fixed.

  For the firmware parts, they have been included in linux-firmware/mantic,
  leaving linux-firmware/lunar and linux-firmware/jammy to be fixed.

  == original bug report ==

  amdgppu update is needed to fix some potential Navi31/Navi33 S3 issue.

  amdgpu:
  ac2f5739fdca drm/amdgpu/mes11: enable reg active poll
  a2fe4534bb38 drm/amd/amdgpu: update mes11 api def
  da9a8dc33da2 drm/amdgpu: reserve the old gc_11_0_*_mes.bin
  616843d5a11b drm/amd/amdgpu: introduce gc_*_mes_2.bin v2
  09bf14907d86 drm/amdgpu: declare firmware for new MES 11.0.4

  Navi31:
  
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=ffe1a41e2ddbc39109b12d95dcac282d90eba8fc
  Navi33:
  
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=a5d7b4df1a76f82e2ecb725cc1b56ce111830bac

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2024427/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 2024427] Re: S3 stress issue for amdgpu Navi 31/Navi33

2023-10-07 Thread Jeroen Webb
I believe this is the right journal. It has a couple of amdgpu call
stacks.

I had a lot of restarts trying to get stuff working.

I'll try out that specific file later today.

** Attachment added: "6db523c73ff64c62a3703c38cd11bad9.journal"
   
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2024427/+attachment/5707633/+files/6db523c73ff64c62a3703c38cd11bad9.journal

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/2024427

Title:
  S3 stress issue for amdgpu Navi 31/Navi33

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Triaged
Status in linux-firmware package in Ubuntu:
  Fix Released
Status in linux-oem-6.1 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Invalid
Status in linux-firmware source package in Jammy:
  Fix Released
Status in linux-oem-6.1 source package in Jammy:
  Fix Released
Status in linux source package in Lunar:
  Fix Committed
Status in linux-firmware source package in Lunar:
  Fix Committed
Status in linux-oem-6.1 source package in Lunar:
  Invalid
Status in linux source package in Mantic:
  Triaged
Status in linux-firmware source package in Mantic:
  Fix Released
Status in linux-oem-6.1 source package in Mantic:
  Invalid

Bug description:
  [SRU Justification]

  BugLink: https://bugs.launchpad.net/bugs/2024427

  [Impact]

  Under stress testing it was reported that the amdgpu Navi31/Navi33 platforms
  will sometimes fail to wake from S3.

  [Fix]

  kernel patches:
  ac2f5739fdca drm/amdgpu/mes11: enable reg active poll
  a2fe4534bb38 drm/amd/amdgpu: update mes11 api def
  da9a8dc33da2 drm/amdgpu: reserve the old gc_11_0_*_mes.bin
  616843d5a11b drm/amd/amdgpu: introduce gc_*_mes_2.bin v2
  09bf14907d86 drm/amdgpu: declare firmware for new MES 11.0.4

  firmware patches:
  * Navi31: ffe1a41e2ddb amdgpu: update GC 11.0.0 firmware for amd.5.5 release
  * Navi33: a5d7b4df1a76 amdgpu: update GC 11.0.2 firmware for amd.5.5 release

  [Test Case]

  $ checkbox-cli run com.canonical.certification::stress-
  suspend-30-cycles-with-reboots-automated

  [Where problems could occur]

  Little we know about the firmware fixes. However, while with these commits 
have
  been pulled via stable kernel fixes, the driver begins to request new firmware
  blobs of a different filename.

  [Other Info]

  The kernel driver commits are in v6.4-rc1, backported to v6.3.4, v6.1.31, and
  partially (missing da9a8dc33da2, 616843d5a11b) v6.2.16. Only linux/lunar has 
to
  be fixed.

  For the firmware parts, they have been included in linux-firmware/mantic,
  leaving linux-firmware/lunar and linux-firmware/jammy to be fixed.

  == original bug report ==

  amdgppu update is needed to fix some potential Navi31/Navi33 S3 issue.

  amdgpu:
  ac2f5739fdca drm/amdgpu/mes11: enable reg active poll
  a2fe4534bb38 drm/amd/amdgpu: update mes11 api def
  da9a8dc33da2 drm/amdgpu: reserve the old gc_11_0_*_mes.bin
  616843d5a11b drm/amd/amdgpu: introduce gc_*_mes_2.bin v2
  09bf14907d86 drm/amdgpu: declare firmware for new MES 11.0.4

  Navi31:
  
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=ffe1a41e2ddbc39109b12d95dcac282d90eba8fc
  Navi33:
  
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=a5d7b4df1a76f82e2ecb725cc1b56ce111830bac

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2024427/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 2024427] Re: S3 stress issue for amdgpu Navi 31/Navi33

2023-10-06 Thread Jeroen Webb
I upgraded to linux-firmware_20220329.git681281e4-0ubuntu3.19 last night
and I couldn't start my computer without going into recovery mode this
morning. There were a few warnings about missing firmware in the apt
logs, but when I googled them, the usual response is "that's normal".

I played around with a pretty good chunk of settings in BIOS, such as
Resizable BAR, but it consistently hangs right after "JPEG decode is
enabled in VM mode".

In recovery mode, I only have access to one monitor; I believe that's by
design.

GPU: RX 7900 XT
Kernel: 6.2.0-34-generic

I installed my other GPU during my lunch break, an RX 6700 XT, and it
booted up just fine in normal mode.

I also tried linux-firmware_20220329.git681281e4-0ubuntu3.20 and it has
the same behavior.

W: Possible missing firmware /lib/firmware/amdgpu/ip_discovery.bin for module 
amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/vega10_cap.bin for module 
amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/sienna_cichlid_cap.bin for 
module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/navi12_cap.bin for module 
amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/aldebaran_cap.bin for module 
amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/gc_11_0_0_toc.bin for module 
amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/sienna_cichlid_mes1.bin for 
module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/sienna_cichlid_mes.bin for 
module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/navi10_mes.bin for module 
amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/gc_11_0_3_mes.bin for module 
amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/gc_11_0_2_mes_2.bin for 
module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/gc_11_0_0_mes_2.bin for 
module amdgpu

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/2024427

Title:
  S3 stress issue for amdgpu Navi 31/Navi33

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Triaged
Status in linux-firmware package in Ubuntu:
  Fix Released
Status in linux-oem-6.1 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Invalid
Status in linux-firmware source package in Jammy:
  Fix Released
Status in linux-oem-6.1 source package in Jammy:
  Fix Released
Status in linux source package in Lunar:
  Fix Committed
Status in linux-firmware source package in Lunar:
  Fix Committed
Status in linux-oem-6.1 source package in Lunar:
  Invalid
Status in linux source package in Mantic:
  Triaged
Status in linux-firmware source package in Mantic:
  Fix Released
Status in linux-oem-6.1 source package in Mantic:
  Invalid

Bug description:
  [SRU Justification]

  BugLink: https://bugs.launchpad.net/bugs/2024427

  [Impact]

  Under stress testing it was reported that the amdgpu Navi31/Navi33 platforms
  will sometimes fail to wake from S3.

  [Fix]

  kernel patches:
  ac2f5739fdca drm/amdgpu/mes11: enable reg active poll
  a2fe4534bb38 drm/amd/amdgpu: update mes11 api def
  da9a8dc33da2 drm/amdgpu: reserve the old gc_11_0_*_mes.bin
  616843d5a11b drm/amd/amdgpu: introduce gc_*_mes_2.bin v2
  09bf14907d86 drm/amdgpu: declare firmware for new MES 11.0.4

  firmware patches:
  * Navi31: ffe1a41e2ddb amdgpu: update GC 11.0.0 firmware for amd.5.5 release
  * Navi33: a5d7b4df1a76 amdgpu: update GC 11.0.2 firmware for amd.5.5 release

  [Test Case]

  $ checkbox-cli run com.canonical.certification::stress-
  suspend-30-cycles-with-reboots-automated

  [Where problems could occur]

  Little we know about the firmware fixes. However, while with these commits 
have
  been pulled via stable kernel fixes, the driver begins to request new firmware
  blobs of a different filename.

  [Other Info]

  The kernel driver commits are in v6.4-rc1, backported to v6.3.4, v6.1.31, and
  partially (missing da9a8dc33da2, 616843d5a11b) v6.2.16. Only linux/lunar has 
to
  be fixed.

  For the firmware parts, they have been included in linux-firmware/mantic,
  leaving linux-firmware/lunar and linux-firmware/jammy to be fixed.

  == original bug report ==

  amdgppu update is needed to fix some potential Navi31/Navi33 S3 issue.

  amdgpu:
  ac2f5739fdca drm/amdgpu/mes11: enable reg active poll
  a2fe4534bb38 drm/amd/amdgpu: update mes11 api def
  da9a8dc33da2 drm/amdgpu: reserve the old gc_11_0_*_mes.bin
  616843d5a11b drm/amd/amdgpu: introduce gc_*_mes_2.bin v2
  09bf14907d86 drm/amdgpu: declare firmware for new MES 11.0.4

  Navi31:
  
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=ffe1a41e2ddbc39109b12d95dcac282d90eba8fc
  Navi33:
  
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=a5d7b4df1a76f82e2ecb725cc1b56ce111830bac

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2024427/+subscriptions


--