Comment # 52 on bug 1028575 from Michal Srb

This bug was assigned to the llvm maintainer to build llvm package with the
commit r280589 reverted for testing. I have inherited it now.

However, based on the additional information it doesn't look like it is a bug
in llvm. User-space can do whatever it wants, if it causes lockups, it is bug
in kernel.

The dmesg you posted is useful. It definitely looks like locking problem. The
other warnings are probably just caused by the earlier errors. However, the
dmesg doesn't look complete - there may have been some errors before the ones
in the log. Can you try to get dmesg again, this time complete? Ideally showing
everything from boot until the lockup.

To address some of your earlier comments:
(In reply to Mircea Kitsune from comment #15)
> I feel that at this point, I should express my disappointment regarding the
> lack of attention this report has received over the course of a month. I
> marked it as high priority (which I believe it is), posted about this on the
> forum, and wrote about it to the Factory mailing list (where it was
> completely ignored). To this day, I still have no idea what this is or when
> and how it might be fixed.

You are running Tumbleweed - bleeding edge. And this issue is likely hardware
specific - if we don't have your hardware, all we can do is guess what may be
wrong.

(In reply to Mircea Kitsune from comment #46)
> Mesa: User error: GL_INVALID_OPERATION in glTexSubImage2D(invalid texture
> image)

Some application is using OpenGL badly. It shouldn't cause issue like this.

(In reply to Mircea Kitsune from comment #48)
> I find it remarkable how the cause of the crash appears to have immediately
> changed after me making the comment above yesterday; I tested my theory that
> desktop effects are the root for 2 months, yet the moment I publish my
> observations the behavior changes in less than a day. This further makes me
> concerned that someone might be deliberately programming this crash using
> vulnerabilities in system components, solely for how strange this
> coincidence is.

Nah, locking issues are typically random and rare. That makes them hard to
reproduce and debug. Nobody is hacking you.

(In reply to Mircea Kitsune from comment #49)
> Created attachment 735281 [details]
> Memtest86 screenshot

Your system memory is ok, that's good, but says nothing about GPU.