dri-devel.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.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	[thread overview]
Message-ID: <bug-100306-502-ugh57M5XAh@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-100306-502@http.bugs.freedesktop.org/>


[-- Attachment #1.1: Type: text/plain, Size: 2425 bytes --]

https://bugs.freedesktop.org/show_bug.cgi?id=100306

--- Comment #28 from MirceaKitsune <sonichedgehog_hyperblast00@yahoo.com> ---
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 after
10 seconds the monitor shuts down. Other unrelated GPU crashes (such as those
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 once
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 want
it triggering any unnecessary arguments... if this is an attack then
investigating it as such might help in finding its source more quickly. There'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 with
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 any
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.

[-- Attachment #1.2: Type: text/html, Size: 3307 bytes --]

[-- Attachment #2: Type: text/plain, Size: 160 bytes --]

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  parent reply	other threads:[~2017-06-07 21:04 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-100306-502@http.bugs.freedesktop.org/>
2017-03-22  2:16 ` [Bug 100306] System randomly freezes or crashes to the login screen, glitches until rebooted bugzilla-daemon
2017-03-29 19:43 ` bugzilla-daemon
2017-04-02 15:04 ` bugzilla-daemon
2017-04-06  2:45 ` bugzilla-daemon
2017-04-06 11:51 ` bugzilla-daemon
2017-04-07  0:01 ` bugzilla-daemon
2017-04-07  0:35 ` bugzilla-daemon
2017-04-11  5:13 ` bugzilla-daemon
2017-04-14 14:01 ` bugzilla-daemon
2017-04-18  1:31 ` bugzilla-daemon
2017-04-20 13:23 ` bugzilla-daemon
2017-05-09 22:17 ` bugzilla-daemon
2017-05-19 12:58 ` bugzilla-daemon
2017-05-19 13:10 ` bugzilla-daemon
2017-05-19 13:37 ` bugzilla-daemon
2017-05-21 11:30 ` bugzilla-daemon
2017-05-23 20:18 ` bugzilla-daemon
2017-05-23 21:54 ` bugzilla-daemon
2017-05-29 20:42 ` bugzilla-daemon
2017-06-07 21:04 ` bugzilla-daemon [this message]
2017-06-08 23:44 ` bugzilla-daemon
2017-06-18 18:59 ` bugzilla-daemon
2017-07-05 13:14 ` bugzilla-daemon
2017-07-05 18:21 ` bugzilla-daemon
2017-08-02 13:31 ` bugzilla-daemon
2017-08-03 13:18 ` bugzilla-daemon
2017-08-04 12:32 ` bugzilla-daemon
2017-08-05 12:24 ` bugzilla-daemon
2017-08-05 13:31 ` bugzilla-daemon
2017-08-07 20:52 ` bugzilla-daemon
2017-08-07 21:30 ` bugzilla-daemon
2017-08-07 21:31 ` bugzilla-daemon
2017-08-07 21:35 ` bugzilla-daemon
2017-08-31 18:17 ` bugzilla-daemon
2017-08-31 18:38 ` bugzilla-daemon
2017-11-12 15:04 ` bugzilla-daemon
2019-09-25 17:58 ` bugzilla-daemon

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-100306-502-ugh57M5XAh@http.bugs.freedesktop.org/ \
    --to=bugzilla-daemon@freedesktop.org \
    --cc=dri-devel@lists.freedesktop.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).