Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
Date:   Wed, 22 Nov 2017 09:34:27 -0600
From:   Bob Tracy <rct@gherkin.frus.com>
To:     Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>
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>
 <f1ac0ac6-04ad-0311-70d0-6c907a7fee2e@I-love.SAKURA.ne.jp>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <f1ac0ac6-04ad-0311-70d0-6c907a7fee2e@I-love.SAKURA.ne.jp>
User-Agent: Mutt/1.6.1 (2016-04-27)
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

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

From 1584772768763066341@xxx Wed Nov 22 13:24:46 +0000 2017
X-GM-THRID: 1584697727601529641
X-Gmail-Labels: Inbox,Category Forums,HistoricalUnread