Snapshot 20240514 causing problems with Firefox
![](https://seccdn.libravatar.org/avatar/92bd73dabc3ee0b4343e34bdb61ac1f7.jpg?s=120&d=mm&r=g)
Hello, I updated from 20240512 to 20240514 this morning, rebooted and logged in. I started Thunderbird and Firefox (125.0.3) and after reloading 3-4 tabs the screen went black, I saw the text console and then got the login prompt again. After logging in again I only started Firefox. It reported a crash. I reloaded some tabs and.. Firefox crashes again, taking X11 with it again. I logged in once more and was able to reproduce the problem. I'm using saved sessions in Firefox, the tabs I opened were the same I open every day. As I need the system for work I decided to roll back to the latest snapshot before the update. Now everything works fine again. No idea what in snapshot 20240514 causes the problem, I will not be able to look at it before Friday evening. When looking at the updated packages in 20240514 I have no idea what might cause these crashes. Cheers, Oliver -- PGP Public Key available at https://pgp.mit.edu/ Key fingerprint = 3264 280C 05B1 572F 3F0B 42B8 1E7B 2D9D 063B D507
![](https://seccdn.libravatar.org/avatar/d44eef0af67eb8d1cea3abe443ba966a.jpg?s=120&d=mm&r=g)
Hello,
In the Message;
Subject : Snapshot 20240514 causing problems with Firefox
Message-ID : <84f8440d-27dd-4b25-a68a-b00fb15cd676@schwabedissen.name>
Date & Time: Thu, 16 May 2024 08:15:01 +0200
[OS] == Oliver Schwabedissen
![](https://seccdn.libravatar.org/avatar/92bd73dabc3ee0b4343e34bdb61ac1f7.jpg?s=120&d=mm&r=g)
Am 16.05.24 um 10:13 schrieb Masaru Nomiya:
Could it be a video driver issue stemming from a kernel update, I think.
You using the video driver for Intel, aren't you?
Might be the kernel update, but no, I'm using an ATI graphics card using amdgpu driver. Hardware Class: graphics card Model: "ATI VGA compatible controller" Vendor: pci 0x1002 "ATI Technologies Inc" Device: pci 0x743f SubVendor: pci 0x1043 "ASUSTeK Computer Inc." SubDevice: pci 0x05d9 Revision: 0xc1 Driver: "amdgpu" Driver Modules: "amdgpu" Regards, Oliver -- PGP Public Key available at https://pgp.mit.edu/ Key fingerprint = 3264 280C 05B1 572F 3F0B 42B8 1E7B 2D9D 063B D507
![](https://seccdn.libravatar.org/avatar/d44eef0af67eb8d1cea3abe443ba966a.jpg?s=120&d=mm&r=g)
Hello,
In the Message;
Subject : Re: Snapshot 20240514 causing problems with Firefox
Message-ID : <1b6cf965-1d3b-4682-8386-bc1842e3b6cc@schwabedissen.name>
Date & Time: Thu, 16 May 2024 15:06:57 +0200
[OS] == Oliver Schwabedissen
![](https://seccdn.libravatar.org/avatar/92bd73dabc3ee0b4343e34bdb61ac1f7.jpg?s=120&d=mm&r=g)
Am 16.05.24 um 23:06 schrieb Masaru Nomiya:
Hello,
In the Message;
Subject : Re: Snapshot 20240514 causing problems with Firefox Message-ID : <1b6cf965-1d3b-4682-8386-bc1842e3b6cc@schwabedissen.name> Date & Time: Thu, 16 May 2024 15:06:57 +0200
[OS] == Oliver Schwabedissen
has written: OS> Am 16.05.24 um 10:13 schrieb Masaru Nomiya: MN> > Could it be a video driver issue stemming from a kernel update, I think.
MN> > You using the video driver for Intel, aren't you?
OS> Might be the kernel update, but no, I'm using an ATI graphics OS> card using amdgpu driver. [...] OS> Driver: "amdgpu" OS> Driver Modules: "amdgpu"
If I were you, I would look into the possibility of using a proprietary driver?
I switched from Nvidia to AMD graphics with my new PC _because_ I wanted to get rid of the Nvidia proprietary driver which often caused problems (especially after kernel updates). Oliver
![](https://seccdn.libravatar.org/avatar/ee9bbd05d9d63586be92d140d88859b1.jpg?s=120&d=mm&r=g)
On 5/18/24 03:24, Oliver Schwabedissen wrote:
Am 16.05.24 um 23:06 schrieb Masaru Nomiya:
Hello,
In the Message;
Subject : Re: Snapshot 20240514 causing problems with Firefox Message-ID : <1b6cf965-1d3b-4682-8386-bc1842e3b6cc@schwabedissen.name> Date & Time: Thu, 16 May 2024 15:06:57 +0200
[OS] == Oliver Schwabedissen
has written: OS> Am 16.05.24 um 10:13 schrieb Masaru Nomiya: MN> > Could it be a video driver issue stemming from a kernel update, I think. MN> > You using the video driver for Intel, aren't you?
OS> Might be the kernel update, but no, I'm using an ATI graphics OS> card using amdgpu driver. [...] OS> Driver: "amdgpu" OS> Driver Modules: "amdgpu"
If I were you, I would look into the possibility of using a proprietary driver?
I switched from Nvidia to AMD graphics with my new PC _because_ I wanted to get rid of the Nvidia proprietary driver which often caused problems (especially after kernel updates).
Oliver There are a number of reports of successfully fixing this issue, by making sure that resizable BAR is enabled in your system BIOS, if you're using AMD Graphics.
Not saying that it will fix your issue, but it seems to be fixing it for lots of folks.
![](https://seccdn.libravatar.org/avatar/3f7b5596ccf58d1378834249859dcb9e.jpg?s=120&d=mm&r=g)
On Mon, May 20, 2024 at 5:19 PM Shawn W Dunn
Oliver There are a number of reports of successfully fixing this issue, by making sure that resizable BAR is enabled in your system BIOS, if you're using AMD Graphics.
Not saying that it will fix your issue, but it seems to be fixing it for lots of folks.
Did that earlier today after reading it here. Up to now seems stable without the crashes I was experiencing. I am with an AMD GPU.
![](https://seccdn.libravatar.org/avatar/18b5ba5cf24476fd60bb8c704803fb5d.jpg?s=120&d=mm&r=g)
Yeah I was almost sure I had it enabled, but it was only partially enabled
and didn't actually work when looking at dmesg.
When enabling it fully I stopped getting crashes here also. So I indeed had
the same problem.
Den mån 20 maj 2024 kl 16:45 skrev Stratos Zolotas
On Mon, May 20, 2024 at 5:19 PM Shawn W Dunn
wrote: Oliver There are a number of reports of successfully fixing this issue, by making sure that resizable BAR is enabled in your system BIOS, if you're using AMD Graphics.
Not saying that it will fix your issue, but it seems to be fixing it for lots of folks.
Did that earlier today after reading it here. Up to now seems stable without the crashes I was experiencing. I am with an AMD GPU.
![](https://seccdn.libravatar.org/avatar/3f7b5596ccf58d1378834249859dcb9e.jpg?s=120&d=mm&r=g)
On Mon, May 20, 2024 at 7:28 PM Ernst Persson
Yeah I was almost sure I had it enabled, but it was only partially enabled and didn't actually work when looking at dmesg. When enabling it fully I stopped getting crashes here also. So I indeed had the same problem.
My motherboard has only "off or auto" option, and it was at "off", seems "auto" works for my setup at least (cross fingers).
![](https://seccdn.libravatar.org/avatar/3af26b63955b9162f06c0f82c86231ac.jpg?s=120&d=mm&r=g)
On 16/05/2024 15.06, Oliver Schwabedissen wrote:
Might be the kernel update, but no, I'm using an ATI graphics card using amdgpu driver.
There were reports of AMD graphics trouble with 6.8.9 - you should stay on 6.8.8 until 6.9.x comes around. https://www.reddit.com/r/openSUSE/comments/1cu63ye/opensuse_tw_kernel_688_mo... https://gitlab.freedesktop.org/drm/amd/-/issues/3343 Ciao Bernhard M.
![](https://seccdn.libravatar.org/avatar/576391bd11ddfd711cdb528aeca24927.jpg?s=120&d=mm&r=g)
In data sabato 18 maggio 2024 16:50:53 CEST, Bernhard M. Wiedemann via openSUSE Factory ha scritto:
There were reports of AMD graphics trouble with 6.8.9 - you should stay on 6.8.8 until 6.9.x comes around.
Indeed, empirically (this happens also with Plasma) most applications using any kind of effect will crash with SIGBUS. So I second the recommendation of staying with 6.8.8.
![](https://seccdn.libravatar.org/avatar/92bd73dabc3ee0b4343e34bdb61ac1f7.jpg?s=120&d=mm&r=g)
Am 16.05.24 um 08:15 schrieb Oliver Schwabedissen:
Hello,
I updated from 20240512 to 20240514 this morning, rebooted and logged in. I started Thunderbird and Firefox (125.0.3) and after reloading 3-4 tabs the screen went black, I saw the text console and then got the login prompt again.
After logging in again I only started Firefox. It reported a crash. I reloaded some tabs and.. Firefox crashes again, taking X11 with it again. I logged in once more and was able to reproduce the problem. I'm using saved sessions in Firefox, the tabs I opened were the same I open every day.
As I need the system for work I decided to roll back to the latest snapshot before the update. Now everything works fine again. No idea what in snapshot 20240514 causes the problem, I will not be able to look at it before Friday evening. When looking at the updated packages in 20240514 I have no idea what might cause these crashes.
I'm now at snapshot 20240516 and was able to track the problem down to a special website. It shows the data of my heat pump at the vendor's cloud. As soon as I display the data of the sensors and actuators as a graphic, Firefox crashes reproducibly. No problems with Chrome. So I'm using Chrome for this website for the moment and will wait for Firefox 126.0 which seems to be in the pipeline already. Regards, Oliver -- PGP Public Key available at https://pgp.mit.edu/ Key fingerprint = 3264 280C 05B1 572F 3F0B 42B8 1E7B 2D9D 063B D507
participants (7)
-
Bernhard M. Wiedemann
-
Ernst Persson
-
Luca Beltrame
-
Masaru Nomiya
-
Oliver Schwabedissen
-
Shawn W Dunn
-
Stratos Zolotas