From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751957AbdKVPea (ORCPT ); Wed, 22 Nov 2017 10:34:30 -0500 Received: from gherkin.frus.com ([192.158.254.49]:53668 "EHLO gherkin.frus.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751460AbdKVPe3 (ORCPT ); Wed, 22 Nov 2017 10:34:29 -0500 Date: Wed, 22 Nov 2017 09:34:27 -0600 From: Bob Tracy To: Tetsuo Handa Cc: linux-kernel@vger.kernel.org Subject: Re: [BUG] 4.14 regression: Xorg hangs on exit Message-ID: <20171122153427.GA5251@gherkin.frus.com> References: <20171121171235.GA22443@gherkin.frus.com> <20171122041141.GA1778@gherkin.frus.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.6.1 (2016-04-27) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Nov 22, 2017 at 10:23:25PM +0900, Tetsuo Handa wrote: > When you hit that problem next time, please capture SysRq-t and SysRq-m output > after logging in remotely. > > # dmesg -c > dmesg.txt > # echo t > /proc/sysrq-trigger > # echo m > /proc/sysrq-trigger > # dmesg -c >> dmesg.txt > # sleep 60 > # echo t > /proc/sysrq-trigger > # echo m > /proc/sysrq-trigger > # dmesg -c >> dmesg.txt Thanks. I figured there had to be a way to get a bit more insight into what was happening. System has been up for 12 hours without incident as I type this: Xorg has been started and exited multiple times with no issue. Still going to keep an eye on it for a while. --Bob