** 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
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/
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 d
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
Public bug reported:
After upgrading linux-firmware from 1.190.5 to 1.197 (as part of the
upgrade from Ubuntu 20.10 to 21.04), I started experiencing frequent and
severe GPU instability. When this happens, I see this error in dmesg:
[20061.061069] amdgpu :03:00.0: amdgpu: [gfxhub0] retry
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 p
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
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,
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-firmw
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
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
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
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:
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
15 matches
Mail list logo
