All of lore.kernel.org
 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: Sun, 18 Jun 2017 18:59:30 +0000	[thread overview]
Message-ID: <bug-100306-502-cNOiiy1igD@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-100306-502@http.bugs.freedesktop.org/>


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

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

--- Comment #30 from MirceaKitsune <sonichedgehog_hyperblast00@yahoo.com> ---
Created attachment 132030
  --> https://bugs.freedesktop.org/attachment.cgi?id=132030&action=edit
Photo of the corrupt image on the screen

I have discovered some very important details today. Everyone following up on
the report, please see this comment!

Recently I realized that a useful test would be to jump into a different run
level once I notice the crash, in order to see how the system behaves there. A
few minutes ago another freeze took place, so I instantly hit Control + Alt +
F1 to go to a console. What I noticed was pretty remarkable and sheds light on
a few aspects:

I could keep typing in the console for nearly 10 seconds, but after that the
exact same behavior still took place (monitor turned itself on and off two
times then the image froze). This time however I was able to toggle the NumLock
led a minute after the crash, while also seeing the HDD led still working; That
means this is not (always) a total system freeze such as a Kernel panic...
instead it appears to be the image output corrupting and staying that way,
freezing only specific components with it (I was still unable to issue a blind
reboot command for instance). To put everything into an approximate timeline,
this is what happened:

00 seconds in: The crash occurs.
02 seconds in: I notice and instantly hit Control + Alt + F1.
05 seconds in: I'm taken to a console where everything works fine: I see the
blinking cursor, can write my login and password, etc.
12 seconds in: Suddenly the monitor turns off and back on several times, then
the image remains frozen in place.

This time however, the screen did not remain turned off or black. Instead it
stayed stuck in a state showing corrupt lines and rectangles of random colors.
I took a photo of my screen with my smartphone, which I attached to this issue.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 3104 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-18 18:59 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
2017-06-08 23:44 ` bugzilla-daemon
2017-06-18 18:59 ` bugzilla-daemon [this message]
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-cNOiiy1igD@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.