From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 100306] System randomly freezes or crashes to the login screen, glitches until rebooted Date: Wed, 07 Jun 2017 21:04:00 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1841887755==" Return-path: Received: from culpepper.freedesktop.org (culpepper.freedesktop.org [IPv6:2610:10:20:722:a800:ff:fe98:4b55]) by gabe.freedesktop.org (Postfix) with ESMTP id 062E96E2ED for ; Wed, 7 Jun 2017 21:04:00 +0000 (UTC) In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dri-devel-bounces@lists.freedesktop.org Sender: "dri-devel" To: dri-devel@lists.freedesktop.org List-Id: dri-devel@lists.freedesktop.org --===============1841887755== Content-Type: multipart/alternative; boundary="14968694390.e43a.2058"; charset="UTF-8" --14968694390.e43a.2058 Date: Wed, 7 Jun 2017 21:03:59 +0000 MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://bugs.freedesktop.org/ Auto-Submitted: auto-generated https://bugs.freedesktop.org/show_bug.cgi?id=3D100306 --- Comment #28 from MirceaKitsune -= -- After another two weeks of absence, the issue was apparently reimplemented = on top of Kernel 4.11.3 + Mesa 17.1.1 + Plasma 5.10.0, likely sometime during = the last few days. The behavior is once again identical, with alt-tab switching= or desktop effects causing everything but the mouse pointer to freeze then aft= er 10 seconds the monitor shuts down. Other unrelated GPU crashes (such as tho= se caused by some games) behave by the classic model, where the entire system simple freezes in place at once... that's a very different result from this freeze, and likely confirms this is a different type of crash. At this point I have almost no doubt this is an attack that's being deliberately programmed, and manually reimplemented on top of new drivers o= nce it gets fixed. The cycle seems to be that a kernel or driver update resolves the issue, then the creators of the crash require about two weeks to patch = it and reimplement the exact same functionality. This is the 4th time the story repeats. I tried steering away from this possibility until I was sure, as I didn't w= ant it triggering any unnecessary arguments... if this is an attack then investigating it as such might help in finding its source more quickly. The= re's simply no way something this precise could happen by itself for nearly half= an year, always coming back with the exact same effects after a period of absence... all despite radical changes to nearly every driver and system component, which would have no doubt altered the behavior of the initial problem in some form. Therefore I hope everyone can see why I'm now going w= ith this theory and greatly considering the option of malicious intent. I have no idea how the virus (?) could be updated on my computer, as it's likely not through the package update system directly. However I suspect it= 's using a constant series of vulnerabilities in one or more system components, which should be fixed by the developers if they exist. I would appreciate a= ny ideas on both how the malicious code might be inserted into the computer, as well as finding the vulnerability within radeon / Mesa / X11 / etc that it exploits. Please let me know what your thoughts are! --=20 You are receiving this mail because: You are the assignee for the bug.= --14968694390.e43a.2058 Date: Wed, 7 Jun 2017 21:03:59 +0000 MIME-Version: 1.0 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://bugs.freedesktop.org/ Auto-Submitted: auto-generated

Comme= nt # 28 on bug 10030= 6 from MirceaKitsune
After another two weeks of absence, the issue was apparently r=
eimplemented on
top of Kernel 4.11.3 + Mesa 17.1.1 + Plasma 5.10.0, likely sometime during =
the
last few days. The behavior is once again identical, with alt-tab switching=
 or
desktop effects causing everything but the mouse pointer to freeze then aft=
er
10 seconds the monitor shuts down. Other unrelated GPU crashes (such as tho=
se
caused by some games) behave by the classic model, where the entire system
simple freezes in place at once... that's a very different result from this
freeze, and likely confirms this is a different type of crash.

At this point I have almost no doubt this is an attack that's being
deliberately programmed, and manually reimplemented on top of new drivers o=
nce
it gets fixed. The cycle seems to be that a kernel or driver update resolves
the issue, then the creators of the crash require about two weeks to patch =
it
and reimplement the exact same functionality. This is the 4th time the story
repeats.

I tried steering away from this possibility until I was sure, as I didn't w=
ant
it triggering any unnecessary arguments... if this is an attack then
investigating it as such might help in finding its source more quickly. The=
re's
simply no way something this precise could happen by itself for nearly half=
 an
year, always coming back with the exact same effects after a period of
absence... all despite radical changes to nearly every driver and system
component, which would have no doubt altered the behavior of the initial
problem in some form. Therefore I hope everyone can see why I'm now going w=
ith
this theory and greatly considering the option of malicious intent.

I have no idea how the virus (?) could be updated on my computer, as it's
likely not through the package update system directly. However I suspect it=
's
using a constant series of vulnerabilities in one or more system components,
which should be fixed by the developers if they exist. I would appreciate a=
ny
ideas on both how the malicious code might be inserted into the computer, as
well as finding the vulnerability within radeon / Mesa / X11 / etc that it
exploits. Please let me know what your thoughts are!


You are receiving this mail because:
  • You are the assignee for the bug.
= --14968694390.e43a.2058-- --===============1841887755== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHBzOi8vbGlz dHMuZnJlZWRlc2t0b3Aub3JnL21haWxtYW4vbGlzdGluZm8vZHJpLWRldmVsCg== --===============1841887755==--