From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 85866] Desktop environment becomes unresponsive, but mouse can move after distro update
Date: Thu, 06 Nov 2014 23:02:24 +0000 [thread overview]
Message-ID: <bug-85866-502-it37O0nDpv@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-85866-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 1522 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=85866
--- Comment #5 from boombatower <jimmy@boombatower.com> ---
Alright, I am unable to get a dmesg log after crashes since my system is
completely unresponsive...even to ssh from another machine.
I setup a watch -n 10 of dmesg to dump to file so I'll be able to grab it on
reboot.
I have identified 3 district crash states. All three start the same way,
everything freezes except mouse, then:
- screen will flash once or twice and drop to black screen
- screen will flash once or twice and drop to tty7 (instead of 8) which has
boot log with last message saying (starting X)
- third state it will do the second one, but allow I can switch to another tty
screen as the machine is responsive after that, just x is dead.
The Xorg log differs between the first two states (see attachments): "xorg.log
from crash" (being state one), and "xorg.log closed and dropped to tty" (being
state two).
I have seen the machine be stable for 12+ hours and then die while locked and
displays off, other times it dies after 3-4 min, and others a couple hours. I
cannot find a correlation between what I am doing (or applications open) when
it dies (and the example of being entirely away seems to support that).
Is there some reasonable instructions for performing a git bisect? I am
familiar with all sorts of development, but not a kernel developer. Is it safe
to assume this is in the driver and not Xorg?
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2370 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2014-11-06 23:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-85866-502@http.bugs.freedesktop.org/>
2014-11-05 6:07 ` [Bug 85866] Desktop environment becomes unresponsive, but mouse can move after distro update bugzilla-daemon
2014-11-06 21:55 ` bugzilla-daemon
2014-11-06 21:55 ` bugzilla-daemon
2014-11-06 23:02 ` bugzilla-daemon [this message]
2014-11-07 2:34 ` bugzilla-daemon
2014-11-07 8:44 ` bugzilla-daemon
2014-11-10 2:36 ` bugzilla-daemon
2014-11-10 3:59 ` bugzilla-daemon
2014-11-10 9:38 ` bugzilla-daemon
2014-11-13 5:01 ` 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-85866-502-it37O0nDpv@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