Bug#1002553: firmware-amd-graphics: Memory clock always at 100% (thinkpads w/ryzen 3XXXu)
Source: firmware-nonfree Source-Version: 20220913-1 On Tue, Jun 21, 2022 at 03:06:19PM -0300, ng wrote: > I tried on a separate partition to run Fedora with the firmware 20220310, > and it works correctly there. You were right. The updated update raven VCN firmware is now included since the 20220913-1 update. Upstream commit: https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?h=20220310=efcfe180c92302c4eec8ed6cfb26dadc0b391fbe Regards, Salvatore
Bug#1002553: firmware-amd-graphics: Memory clock always at 100% (thinkpads w/ryzen 3XXXu)
I tried on a separate partition to run Fedora with the firmware 20220310, and it works correctly there. You were right. Have a nice day. El 12/06/22 a las 8:38, Diederik de Haas escribió: Control: tag -1 - moreinfo Control: forwarded -1 https://gitlab.freedesktop.org/drm/amd/-/issues/1455 Control: tag -1 fixed-upstream On Sunday, 12 June 2022 06:59:12 CEST ng wrote: Hi, I went on and installed the respective image from https://snapshot.debian.org/package/linux/5.10.46-5/#linux-image-5.10.0-8-am d64-unsigned_5.10.46-5 and had no luck, no change whatsoever. Hi! Thanks for testing, then this is a separate issue. https://lore.kernel.org/linux-firmware/CADnq5_PYhDcR3tNYgzQ-uz80Nf++oMPsF3=huk+qcgntiy_...@mail.gmail.com/ is where a fix has been proposed+merged upstream (date: 2022-02-28). An update of the firmware to version >= 20220310 _should_ fix this issue. If such a version becomes available, could you test whether it indeed fixes your issue and report your findings back to this bug report? TIA, Diederik
Processed: Re: Bug#1002553: firmware-amd-graphics: Memory clock always at 100% (thinkpads w/ryzen 3XXXu)
Processing control commands: > tag -1 - moreinfo Bug #1002553 [firmware-amd-graphics] firmware-amd-graphics: Memory clock always at 100% (thinkpads w/ryzen 3XXXu) Removed tag(s) moreinfo. > forwarded -1 https://gitlab.freedesktop.org/drm/amd/-/issues/1455 Bug #1002553 [firmware-amd-graphics] firmware-amd-graphics: Memory clock always at 100% (thinkpads w/ryzen 3XXXu) Set Bug forwarded-to-address to 'https://gitlab.freedesktop.org/drm/amd/-/issues/1455'. > tag -1 fixed-upstream Bug #1002553 [firmware-amd-graphics] firmware-amd-graphics: Memory clock always at 100% (thinkpads w/ryzen 3XXXu) Added tag(s) fixed-upstream. -- 1002553: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1002553 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1002553: firmware-amd-graphics: Memory clock always at 100% (thinkpads w/ryzen 3XXXu)
Control: tag -1 - moreinfo Control: forwarded -1 https://gitlab.freedesktop.org/drm/amd/-/issues/1455 Control: tag -1 fixed-upstream On Sunday, 12 June 2022 06:59:12 CEST ng wrote: > Hi, I went on and installed the respective image from > https://snapshot.debian.org/package/linux/5.10.46-5/#linux-image-5.10.0-8-am > d64-unsigned_5.10.46-5 and had no luck, no change whatsoever. Hi! Thanks for testing, then this is a separate issue. https://lore.kernel.org/linux-firmware/CADnq5_PYhDcR3tNYgzQ-uz80Nf++oMPsF3=huk+qcgntiy_...@mail.gmail.com/ is where a fix has been proposed+merged upstream (date: 2022-02-28). An update of the firmware to version >= 20220310 _should_ fix this issue. If such a version becomes available, could you test whether it indeed fixes your issue and report your findings back to this bug report? TIA, Diederik signature.asc Description: This is a digitally signed message part.
Bug#1002553: firmware-amd-graphics: Memory clock always at 100% (thinkpads w/ryzen 3XXXu)
Hi, I went on and installed the respective image from https://snapshot.debian.org/package/linux/5.10.46-5/#linux-image-5.10.0-8-amd64-unsigned_5.10.46-5 and had no luck, no change whatsoever. Later next week I'll try running Fedora or Arch on a different drive to see if it has been corrected on the firmware/kernel side, like the git said. El 10/06/22 a las 10:57, Diederik de Haas escribió: Could you try *downgrading* your kernel to 5.10.46-5, to be found here: https://snapshot.debian.org/package/linux/5.10.46-5/#linux-image-5.10.0-8-amd64-unsigned_5.10.46-5 The reason for this is https://bugs.debian.org/990312 with a possible similar cause and therefor solution, which was part of 5.10.46-3. The fix was reverting 2 commits wrt 'CP_MEC_DOORBELL_RANGE' and in kernel 5.10.61 there was another commit related to that, and I'd like to know if that caused a regression. I don't expect it, but it's better to verify. The symptom of bug 990312 were easy to detect with: cat /sys/class/drm/card0/device/gpu_busy_percent
Bug#1002553: firmware-amd-graphics: Memory clock always at 100% (thinkpads w/ryzen 3XXXu)
Control: tag -1 moreinfo On Thu, 23 Dec 2021 20:38:24 -0500 Nelson G wrote: > Package: firmware-amd-graphics > Version: 20210315-3 > > Several Thinkpads with the ryzen 3xxx cpu have a certain bug, using the tool > 'radeontop' you can check that the Memory Clock is always at 100.00% > (draining battery, etc). > > Kernel: Linux 5.10.0-10-amd64 (SMP w/8 CPU threads) Could you try *downgrading* your kernel to 5.10.46-5, to be found here: https://snapshot.debian.org/package/linux/5.10.46-5/#linux-image-5.10.0-8-amd64-unsigned_5.10.46-5 The reason for this is https://bugs.debian.org/990312 with a possible similar cause and therefor solution, which was part of 5.10.46-3. The fix was reverting 2 commits wrt 'CP_MEC_DOORBELL_RANGE' and in kernel 5.10.61 there was another commit related to that, and I'd like to know if that caused a regression. I don't expect it, but it's better to verify. The symptom of bug 990312 were easy to detect with: cat /sys/class/drm/card0/device/gpu_busy_percent signature.asc Description: This is a digitally signed message part.
Bug#1002553: firmware-amd-graphics: Memory clock always at 100% (thinkpads w/ryzen 3XXXu)
Package: firmware-amd-graphics Version: 20210315-3 Severity: wishlist Dear Maintainer, Several Thinkpads with the ryzen 3xxx cpu have a certain bug, using the tool 'radeontop' you can check that the Memory Clock is always at 100.00% (draining battery, etc). The patch seems to be on it's way (VCN firmware); it would be great if you guys can keep an eye on this: https://gitlab.freedesktop.org/drm/amd/-/issues/1455 This bug is moderate/severe. Hopefully we can get this fix for stable directly or through backports. Sorry if I filed this bug in the wrong way or against the wrong package. Happy holidays! -- System Information: Debian Release: 11.2 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.10.0-10-amd64 (SMP w/8 CPU threads) Locale: LANG=es_CO.UTF-8, LC_CTYPE=es_CO.UTF-8 (charmap=UTF-8), LANGUAGE=es_CO:es Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled firmware-amd-graphics depends on no packages. firmware-amd-graphics recommends no packages. Versions of packages firmware-amd-graphics suggests: ii initramfs-tools 0.140
