Just to correct a few of the targets on this issue.
* The reverts mentioned in #30 need to be pulled into linux-firmware for focal.
* They're already included in jammy.
** Changed in: amd
Status: New => Fix Released
** No longer affects: mesa (Ubuntu)
** Also affects: linux-firmware
Hirsute is EOL so closing this bug. Please open a new one if the problem
still persists with one of the supported series.
** Changed in: linux-firmware (Ubuntu Hirsute)
Status: Incomplete => Won't Fix
--
You received this bug notification because you are a member of Kernel
Packages,
Hello Juerg,
Em quinta-feira, 20 de janeiro de 2022, às 12:32:48 -03, Juerg Haefliger
escreveu:
> If you want this fixed in Ubuntu I need to know what series are
> affected. Hirsute goes EOL at the end of the month. Are Impish and/or
> Jammy working or affected as well?
I upgraded to Impish a
If you want this fixed in Ubuntu I need to know what series are
affected. Hirsute goes EOL at the end of the month. Are Impish and/or
Jammy working or affected as well?
** Changed in: linux-firmware (Ubuntu Hirsute)
Status: Confirmed => Incomplete
--
You received this bug notification
No more crashes with firmware
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-
firmware.git/snapshot/linux-firmware-20211027.tar.gz and kernel 5.15.6.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in
** Changed in: linux-firmware (Ubuntu)
Assignee: Seth Forshee (sforshee) => (unassigned)
--
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/1928393
Title:
linux-firmware 1.197
@antonio-petricca, What series? What kernel?
I can produce a hirsute linux-firmware package with the reverted sdma
firmware but need someone to verify it on hirsute with the hirsute
kernel. Any takers? Or have you all moved on to impish?
--
You received this bug notification because you are a
With latest firmare
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-
firmware.git/snapshot/linux-firmware-20211027.tar.gz is much more
stable.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
** Also affects: mesa (Ubuntu Hirsute)
Importance: Undecided
Status: New
** Also affects: linux-firmware (Ubuntu Hirsute)
Importance: Undecided
Status: New
** No longer affects: mesa (Ubuntu Hirsute)
** Changed in: mesa (Ubuntu)
Status: Confirmed => Invalid
**
@antonio-petricca, sorry but 5.15.2 is not a supported Ubuntu kernel and
especially not on Bionic with (old) Bionic firmware.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
I have the same issue on:
Dell E5495
AMD Ryzen 7 PRO 2700U w/ Radeon Vega Mobile Gfx
16Gb RAM
Linux Mint 19.3 (Ubuntu 18.04)
Kernel 5.15.2
Linux Firmware 1.173.20
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
The reverts are in the latest firmware tree:
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/amdgpu?id=d7b50e61669dc137924337d03d09b8986eb752a3
Hi. I'm picking up this ticket from Seth. Reading through the history it
seems it's still an open issue? My understanding is that upstream
'fixed' this by reverting fw blobs in version 20210818. I can produce a
linux-firmware test package for hirsute 20.04 with these reverts if
necessary. Just let
Hello,
I’d just like to report that I haven’t seen this problem in a while. The
last time I see the “retry page fault” messages in my log was on August 9.
I’ve been using the ‘amdgpu/picasso*‘ files from linux-firmware commit
c46b8c364b82 (“ice: update package file to 1.3.26.0”) so apparently
It is the Blue-Tooth Driver.
I Got This Too on my
Acer Aspire F5-573 series "Laptop"
There is a sticker that says "Intel i-5 core" Know amd is a possablity ?
I Do not think My Processor Is an amd?
Also It set my Screen Res to like 1377x768 (Its a 6k screen) 17" screen
When I was On Windows "Yes I
I have similar messages in journalctl:
Package: linux-firmware
Version: 1.197.3
Aug 29 16:58:44 dagon kernel: amdgpu :03:00.0: amdgpu: [mmhub] page fault
(src_id:0 ring:0 vmid:1 pasid:32778, for process vivaldi-bin pid 1673 thread
vivaldi-bi:cs0 pid 1699)
Aug 29 16:58:44 dagon kernel:
It happened to me too
** Attachment added: "Crash log of amdgpu driver"
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1928393/+attachment/5516220/+files/amdgu_crash.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
Hello,
For some reason, in the past week or so this bug has been freezing my
machine every couple of days or so (I’m surprised that AMD wasn’t able
to reproduce the problem yet¹). You can imagine how “pleasant” it makes
using this computer.
Today I got an interesting error in dmesg, perhaps
Em segunda-feira, 12 de julho de 2021, às 15:12:19 -03, Alex Deucher
escreveu:
> Does the latest firmware in the firmware git tree help?
> https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.g
> it/log/amdgpu
I updated the picasso* files from commit:
d79c26779d45 amdgpu:
After updating to linux-firmware commit d79c26779d45906 the problems
persist on Lenovo Thinkpad E585:
amdgpu :05:00.0: amdgpu: [gfxhub0] retry page fault (src_id:0 ring:0
vmid:1 pasid:32769, for process Xorg pid 1336 thread Xorg:cs0 pid 1862)
--
You received this bug notification because
@alexander-deucher
CPU model: AMD Ryzen 7 2700U with Radeon Vega Mobile Gfx
Kernel: 5.10.49
Firmware:
VCE feature version: 0, firmware version: 0x
UVD feature version: 0, firmware version: 0x
MC feature version: 0, firmware version: 0x
ME feature version: 52, firmware
There is an upstream bug report
https://bugzilla.kernel.org/show_bug.cgi?id=213391
Comment 9 suggest: "downgrade the firmware."
Comment 15 claims: "20210315 seems to work fine here (on an E595)."
** Bug watch added: Linux Kernel Bug Tracker #213391
Does the latest firmware in the firmware git tree help?
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/log/amdgpu
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
Also affected:
Ubuntu version: 21.04
Linux kernel: 5.11.0-22-generic x86_64
CPU model: AMD Ryzen 5 2500U with Radeon Vega Mobile Gfx
GPU: 05:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI]
Raven Ridge [Radeon Vega Series / Radeon Vega Mobile Series] (rev c4)
Laptop model:
Em quinta-feira, 17 de junho de 2021, às 00:45:30 -03, Thiago Jung
Bauermann escreveu:
> > > I think it may be related to a change in mesa. Specifically mesa
> > > commit
> > > 820dec3f7c7. For more info see
> > > https://gitlab.freedesktop.org/mesa/mesa/-/issues/4866
> >
> > I’ll run with
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: mesa (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
I was finally able to spend a bit of time on this. Unfortunately, there’s
not much to report back.
Em terça-feira, 8 de junho de 2021, às 15:13:36 -03, Thiago Jung Bauermann
escreveu:
> Em terça-feira, 8 de junho de 2021, às 10:30:24 -03, Alex Deucher
escreveu:
> > Can you narrow down which
21.04 comes with Mesa 21.0.1 which does not seem to have 820dec3f7c7
--
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/1928393
Title:
linux-firmware 1.197 causes kernel to report
** Bug watch added: gitlab.freedesktop.org/drm/amd/-/issues #1598
https://gitlab.freedesktop.org/drm/amd/-/issues/1598
** Bug watch added: gitlab.freedesktop.org/drm/amd/-/issues #920
https://gitlab.freedesktop.org/drm/amd/-/issues/920
--
You received this bug notification because you are
Thanks for your input.
Em terça-feira, 8 de junho de 2021, às 10:30:24 -03, Alex Deucher escreveu:
> Can you narrow down which specific firmware file causes the problem?
Ok, I will try.
Also, is it possible and/or worthwhile trying to bisect firmware versions from
the linux-firmware repo? How
Here's a PPA build with the mesa fix Alex mentioned backported:
https://launchpad.net/~superm1/+archive/ubuntu/lp1928393
If you can follow the directions to add that PPA and upgrade to that
mesa package you can see if that indeed fixes it.
** Also affects: mesa (Ubuntu)
Importance: Undecided
Can you narrow down which specific firmware file causes the problem? We
haven't been able to repro this.
I think it may be related to a change in mesa. Specifically mesa commit
820dec3f7c7. For more info see
https://gitlab.freedesktop.org/mesa/mesa/-/issues/4866
** Bug watch added:
Maybe folks at AMD can chime in? Picasso FW regressed.
** Also affects: amd
Importance: Undecided
Status: New
--
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/1928393
Em quarta-feira, 26 de maio de 2021, às 16:46:14 -03, Thiago Jung Bauermann
escreveu:
> But perhaps the upstream version is not too bad?
I take this back. I've been running with the upstream picasso* files since
Wednesday, and I just had two freezes in less than one hour.
linux-firmware
Over the weekend I was finally able to revert back to the previous versions
of the org.freedesktop.Platform and org.freedesktop.Platform.GL.default
flatpak runtimes. It turns out that the `flatpak history` command wasn't
necessay for the rollback.
Em sexta-feira, 14 de maio de 2021, às
Em sábado, 15 de maio de 2021, às 11:24:17 -03, Thiago Jung Bauermann
escreveu:
> Unexpectedly, 1.197 is now reliable too! I have been running it for about
> half a day (which is more than what was possible before) and it is fine.
After 4 days of stability I just had the retry page fault problem
The latest upstream firmware is stable, so I reverted back to 1.197 so that
I could test only the picasso* files.
Before doing that, I decided to run for a while with pristine linux-
firmware 1.197 to double-check that the bug happens quickly.
Unexpectedly, 1.197 is now reliable too! I have
On Fri, May 14, 2021 at 06:01:50PM -, Thiago Jung Bauermann wrote:
> Ah, ok. This morning I went ahead and overwrote the whole of /lib/firmware/
> amdgpu/ with the files from the latest commit of the upstream linux-
> firmware git repo you mention below. It's been only a little over 2 hours,
Hello Seth,
Thank you for the quick and detailed response.
Em sexta-feira, 14 de maio de 2021, às 13:14:22 -03, Seth Forshee escreveu:
> Before we revert we should see if newer firmware fixes the issue, and
> make sure we are only changing the specific firmware files for your
> hardware.
Ok,
Before we revert we should see if newer firmware fixes the issue, and
make sure we are only changing the specific firmware files for your
hardware.
I think your hardware is the "Picasso" series. Can you try the
following? If you are unsure about any of the following steps, let me
know and I can
This is the dmesg of an instance where I was able to continue using the
laptop despite the GPU bug (in the case of the dmesg I attached
previously, I had to ssh in to the machine to turn it off).
Notice that there are two instances of the retry page fault, one of them
right within 15 minutes of
41 matches
Mail list logo
