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: Fri, 19 May 2017 12:58:30 +0000
Message-ID:
References:
Mime-Version: 1.0
Content-Type: multipart/mixed; boundary="===============2122527318=="
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 BAF406E02F
for ; Fri, 19 May 2017 12:58:30 +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
--===============2122527318==
Content-Type: multipart/alternative; boundary="14951987100.c9eC.8991";
charset="UTF-8"
--14951987100.c9eC.8991
Date: Fri, 19 May 2017 12:58:30 +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
MirceaKitsune changed:
What |Removed |Added
----------------------------------------------------------------------------
Priority|high |highest
Severity|major |critical
--- Comment #21 from MirceaKitsune -=
--
Once again, I'm dealing with at least one system crash per day. The latest =
one
happens even after upgrading to the 4.11.0 Kernel, meaning the error was po=
rted
to it as well.
Why are the developers so incapable this time? This has been happening for
nearly 3 darn months! The problem has been fixed twice, and each time it's
returned after over 2 weeks. Can someone please explain what the heck is go=
ing
on here? At this stage, it feels like someone is actively developing and
updating this freeze against the latest system components... I don't even s=
ee
how it could survive through this many package updates by chance alone, it =
is
ridiculous.
And please don't lecture me on how this is free software, and I should only=
be
complaining if I was actually paying the developers: There is a limit beyond
which an important piece of software, be it a free Linux distribution or
component, can break and stay broken. To literally be unable to keep a syst=
em
running without the image suddenly freezing and the monitor shutting down e=
very
single day, for over a quarter of an year... that goes far beyond that limi=
t.
I'm sorry for the outburst, but at this stage I think something needed to be
said. I did not expect something like this to get dragged so far, and that =
I'd
be unable to keep my system running for months. I'm going to bump the sever=
ity
of this issue again, in hopes that someone can please take a look at it so I
can run my system normally again! Thank you.
--=20
You are receiving this mail because:
You are the assignee for the bug.=
--14951987100.c9eC.8991
Date: Fri, 19 May 2017 12:58:30 +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
MirceaKitsune
changed
bug 10030=
6
| What |
Removed |
Added |
| Priority |
high
|
highest
|
| Severity |
major
|
critical
|
Comme=
nt # 21
on bug 10030=
6
from MirceaKitsune=
span>
Once again, I'm dealing with at least one system crash per day=
. The latest one
happens even after upgrading to the 4.11.0 Kernel, meaning the error was po=
rted
to it as well.
Why are the developers so incapable this time? This has been happening for
nearly 3 darn months! The problem has been fixed twice, and each time it's
returned after over 2 weeks. Can someone please explain what the heck is go=
ing
on here? At this stage, it feels like someone is actively developing and
updating this freeze against the latest system components... I don't even s=
ee
how it could survive through this many package updates by chance alone, it =
is
ridiculous.
And please don't lecture me on how this is free software, and I should only=
be
complaining if I was actually paying the developers: There is a limit beyond
which an important piece of software, be it a free Linux distribution or
component, can break and stay broken. To literally be unable to keep a syst=
em
running without the image suddenly freezing and the monitor shutting down e=
very
single day, for over a quarter of an year... that goes far beyond that limi=
t.
I'm sorry for the outburst, but at this stage I think something needed to be
said. I did not expect something like this to get dragged so far, and that =
I'd
be unable to keep my system running for months. I'm going to bump the sever=
ity
of this issue again, in hopes that someone can please take a look at it so I
can run my system normally again! Thank you.
You are receiving this mail because:
- You are the assignee for the bug.
=
--14951987100.c9eC.8991--
--===============2122527318==
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: base64
Content-Disposition: inline
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs
IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHBzOi8vbGlz
dHMuZnJlZWRlc2t0b3Aub3JnL21haWxtYW4vbGlzdGluZm8vZHJpLWRldmVsCg==
--===============2122527318==--