From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753302AbbBRTA5 (ORCPT ); Wed, 18 Feb 2015 14:00:57 -0500 Received: from atrey.karlin.mff.cuni.cz ([195.113.26.193]:50457 "EHLO atrey.karlin.mff.cuni.cz" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752472AbbBRTAz (ORCPT ); Wed, 18 Feb 2015 14:00:55 -0500 Date: Wed, 18 Feb 2015 20:00:52 +0100 From: Pavel Machek To: "Rafael J. Wysocki" Cc: kernel list , Linux-pm mailing list Subject: Re: 3.20-rc0: GUI dies on resume, then systemd gots sigill Message-ID: <20150218190052.GA25491@amd> References: <20150218094631.GA3352@amd> <2254794.AHR7M2FYHX@vostro.rjw.lan> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <2254794.AHR7M2FYHX@vostro.rjw.lan> User-Agent: Mutt/1.5.23 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi! On Wed 2015-02-18 17:39:08, Rafael J. Wysocki wrote: > On Wednesday, February 18, 2015 10:46:32 AM Pavel Machek wrote: > > Hi! > > > > In 3.19, suspend/resume was rock solid. > > > > 3.20-rc0, after resume, I could see X windows dying. So I tried to log > > in on text console, but at that point got a note about SIGILL from > > systemd (and dead system). syslog ilustrates it nicely. > > > > Any ideas? > > The dying X may be a graphics driver problem. > > Have you tried to suspend/resume without X? > > The systemd failure after the failing resume indicates that something was > stuck somewhere or we corrupted memory. It looks like everyone and their dog gets SIGILL, so... yes, I'll try without X, no, I don't think it will make difference. For the record, 796e1c55717e9a6ff5c81b12289ffa1ffd919b6f is bad. Does it work for you? Do you have any Intel graphics machine nearby? Pavel -- (english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html