From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753058AbbBRQP4 (ORCPT ); Wed, 18 Feb 2015 11:15:56 -0500 Received: from v094114.home.net.pl ([79.96.170.134]:51333 "HELO v094114.home.net.pl" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with SMTP id S1752157AbbBRQPy (ORCPT ); Wed, 18 Feb 2015 11:15:54 -0500 From: "Rafael J. Wysocki" To: Pavel Machek Cc: kernel list , Linux-pm mailing list Subject: Re: 3.20-rc0: GUI dies on resume, then systemd gots sigill Date: Wed, 18 Feb 2015 17:39:08 +0100 Message-ID: <2254794.AHR7M2FYHX@vostro.rjw.lan> User-Agent: KMail/4.11.5 (Linux/3.19.0+; KDE/4.11.5; x86_64; ; ) In-Reply-To: <20150218094631.GA3352@amd> References: <20150218094631.GA3352@amd> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="utf-8" Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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. Rafael