Seems the issue appears at least with my AMD RX580. I have another system with Intel and doesn't experience the same issue. I'll see if I open an upstream bug report later today. Stratos On Fri, Jul 10, 2020 at 7:06 AM Alin Marin Elena wrote:

fine here on Linux circassia 5.7.7-1.gcba119b-default #1 SMP Wed Jul 1 19:03:27 UTC 2020 (cba119b) x86_64 x86_64 x86_64 GNU/Linux

and intel card for video.

Regards, Alin

---Dr Alin Marin Elenahttp://alin.elena.space

---- On Thu, 09 Jul 2020 20:50:57 +0100 Stratos Zolotas wrote ----

...

Hello everyone,

Getting frequent crashes and KDE is not responsive (I can ssh to the box but even reboot hangs) after upgrading to the latest snapshot with kernel 5.7.7. Rebooting to kernel 5.7.5 seems to solve the problem.

The kernel log I have found is here: https://paste.opensuse.org/80509273

Any thoughts? -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

-- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

Made a report here: https://bugzilla.kernel.org/show_bug.cgi?id=207383 It seems that other users are affected since older kernel versions than mine and with different AMD GPU hardware. Up to now all of us seem to have multi-monitor setup. On Fri, Jul 10, 2020 at 9:59 AM John Janus wrote:

On Freitag, 10. Juli 2020 08:47:52 CEST Stratos Zolotas wrote:

...

Seems the issue appears at least with my AMD RX580. I have another system with Intel and doesn't experience the same issue. I'll see if I open an upstream bug report later today.

Stratos

On Fri, Jul 10, 2020 at 7:06 AM Alin Marin Elena wrote:

...

fine here on Linux circassia 5.7.7-1.gcba119b-default #1 SMP Wed Jul 1 19:03:27 UTC 2020 (cba119b) x86_64 x86_64 x86_64 GNU/Linux

and intel card for video.

Regards, Alin

---Dr Alin Marin Elenahttp://alin.elena.space

---- On Thu, 09 Jul 2020 20:50:57 +0100 Stratos Zolotas wrote ---->

...

Hello everyone,

Getting frequent crashes and KDE is not responsive (I can ssh to the box but even reboot hangs) after upgrading to the latest snapshot with kernel 5.7.7. Rebooting to kernel 5.7.5 seems to solve the problem.

The kernel log I have found is here: https://paste.opensuse.org/80509273

Any thoughts? -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

It works fine here with an RX480, so it might be more specific than just amdgpu.

-- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

-- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

On Freitag, 10. Juli 2020 13:34:17 CEST Stratos Zolotas wrote:

On Fri, Jul 10, 2020 at 9:59 AM John Janus wrote:

...

It works fine here with an RX480, so it might be more specific than just amdgpu.

Sorry for the double post.

John can you please clarify if you are on a single or multi-monitor setup? There is a discussion about that on the upstream bug report and maybe can help the devs pinpoint the issue.

I'm using a dual monitor setup with one 1920x1080 monitor and one 1680x1050 monitor. The computer ran at least 10 hours yesterday with kernel 5.7.7 -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

I believe I may be experiencing the same issue, but I'm not certain if it's identical. Since updating my laptop (running tumbleweed) to the 5.7.7 kernel last week with the Jul. 9 release, Xorg crashes whenever something makes use of the radeon. My laptop is an Asus V301L, and lspci reports the hardware: 00:02.0 VGA compatible controller: Intel Corporation Haswell-ULT Integrated Graphics Controller (rev 09) (prog-if 00 [VGA controller]) 04:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Mars LE [Radeon HD 8530M / R5 M240] (prog-if 00 [VGA controller]) PRIME offloading makes use of the Radeon, which I believe is a Southern Islands OLAND chipset. I use Plasma for my desktop. Under tumbleweed kernel 5.7.5-1.2, I could run glxgears, firefox playing youtube videos, and factorio acceptably well. Under 5.7.7-1.2, glxgears shows a black, unchanging window. Running radeontop simultaneously shows that the radeon has usage levels I'd associate with running a GL-rendering workload on it, but nothing is sent to the display. Playing youtube videos in firefox, and loading factorio both cause Xorg to crash with SIGABRT. It isn't happening randomly for me, it's happening specifically when something is trying to make use of the radeon. I get kernel messages in syslog (like "radeon 0000:04:00.0: WB enabled") whenever I run something with the DRI_PRIME=1 environment, which I infer are the result of some initialization sequence. I see no errors from the kernel-level/dmesg upon Xorg crashing. Looking through backtraces I suspect low-level drivers are responsible, however. I'm still investigating the sequence of events, but I haven't figured out running X under gdb yet, and it will probably involve slowly poking at an ssh session from my phone. Not a covnenient setup for debugging graphics-stack issues. I'll post more specifics when I can get something useful from a backtrace. It's been a very long time since I've built custom kernels, and I'm not looking forward to attempting to bisect the issue, given reports that many commits simply don't compile at all. I can trigger the crashes very reliably. I'm about to become more committed to using borg for backups prior to every zypper dup, as it's now not possible for me to revert to a working system. :( On 7/10/20, Stratos Zolotas wrote:

On Fri, Jul 10, 2020 at 2:57 PM John Janus wrote:

...

...

I'm using a dual monitor setup with one 1920x1080 monitor and one 1680x1050 monitor. The computer ran at least 10 hours yesterday with kernel 5.7.7

Thank you for the feedback.

Got the "bug" in 15 minutes today with 5.7.7, running for 3-4 hours now with 5.7.5 with no issues...Bad thing is that neither upstream they seem to have an idea about what is causing it... -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

-- Chris Riddoch http://www.syntacticsugar.org/ -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

I'm only using the laptop's built-in screen, so no, this isn't under a multi-monitor setup. I have seen that bug report, yes. I'm unsure if it's the same issue, because I'm not getting segfaults from the *kernel*. Xorg is crashing. Also, I suspect that the intel + radeon prime offloading complicates the issue. Still, it's very possible that the same root cause could manifest in different ways with variations between systems, and the multiple bugzilla reports of issues with radeon graphics with 5.7.7 clearly indicate significant regressions. To try to narrow things down, I've tested under other window managers, and can reproduce my issues regardless of window manager. I've been a software developer for some time, but I've never worked on kernel code. I suspect the radeon drivers are probably not the most straightforward place to start... On 7/13/20, Chan wrote:

Are you running multiple monitors? In either case, have you looked at this kernel bug report: https://bugzilla.kernel.org/show_bug.cgi?id=207383 ? It's definitely not a localised issue if yours is the same.

On 14/7/20 10:56 am, Chris Riddoch wrote:

...

I believe I may be experiencing the same issue, but I'm not certain if it's identical. Since updating my laptop (running tumbleweed) to the 5.7.7 kernel last week with the Jul. 9 release, Xorg crashes whenever something makes use of the radeon.

My laptop is an Asus V301L, and lspci reports the hardware: 00:02.0 VGA compatible controller: Intel Corporation Haswell-ULT Integrated Graphics Controller (rev 09) (prog-if 00 [VGA controller]) 04:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Mars LE [Radeon HD 8530M / R5 M240] (prog-if 00 [VGA controller])

PRIME offloading makes use of the Radeon, which I believe is a Southern Islands OLAND chipset.

I use Plasma for my desktop. Under tumbleweed kernel 5.7.5-1.2, I could run glxgears, firefox playing youtube videos, and factorio acceptably well. Under 5.7.7-1.2, glxgears shows a black, unchanging window. Running radeontop simultaneously shows that the radeon has usage levels I'd associate with running a GL-rendering workload on it, but nothing is sent to the display. Playing youtube videos in firefox, and loading factorio both cause Xorg to crash with SIGABRT.

It isn't happening randomly for me, it's happening specifically when something is trying to make use of the radeon. I get kernel messages in syslog (like "radeon 0000:04:00.0: WB enabled") whenever I run something with the DRI_PRIME=1 environment, which I infer are the result of some initialization sequence.

I see no errors from the kernel-level/dmesg upon Xorg crashing. Looking through backtraces I suspect low-level drivers are responsible, however. I'm still investigating the sequence of events, but I haven't figured out running X under gdb yet, and it will probably involve slowly poking at an ssh session from my phone. Not a covnenient setup for debugging graphics-stack issues. I'll post more specifics when I can get something useful from a backtrace.

It's been a very long time since I've built custom kernels, and I'm not looking forward to attempting to bisect the issue, given reports that many commits simply don't compile at all. I can trigger the crashes very reliably.

I'm about to become more committed to using borg for backups prior to every zypper dup, as it's now not possible for me to revert to a working system. :(

On 7/10/20, Stratos Zolotas wrote:

...

On Fri, Jul 10, 2020 at 2:57 PM John Janus wrote:

...

I'm using a dual monitor setup with one 1920x1080 monitor and one 1680x1050 monitor. The computer ran at least 10 hours yesterday with kernel 5.7.7

Thank you for the feedback.

Got the "bug" in 15 minutes today with 5.7.7, running for 3-4 hours now with 5.7.5 with no issues...Bad thing is that neither upstream they seem to have an idea about what is causing it... -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

-- Chris Riddoch http://www.syntacticsugar.org/ -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org