From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@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 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1594618180==" Return-path: Received: from culpepper.freedesktop.org (unknown [131.252.210.165]) by gabe.freedesktop.org (Postfix) with ESMTP id 443EC6F0DF for ; Thu, 6 Nov 2014 15:02:24 -0800 (PST) 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 --===============1594618180== Content-Type: multipart/alternative; boundary="1415314944.6aFE50.24492"; charset="UTF-8" --1415314944.6aFE50.24492 Date: Thu, 6 Nov 2014 23:02:24 +0000 MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" https://bugs.freedesktop.org/show_bug.cgi?id=85866 --- Comment #5 from boombatower --- 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. --1415314944.6aFE50.24492 Date: Thu, 6 Nov 2014 23:02:24 +0000 MIME-Version: 1.0 Content-Type: text/html; charset="UTF-8"

Comment # 5 on bug 85866 from 
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.
--1415314944.6aFE50.24492-- --===============1594618180== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHA6Ly9saXN0 cy5mcmVlZGVza3RvcC5vcmcvbWFpbG1hbi9saXN0aW5mby9kcmktZGV2ZWwK --===============1594618180==--