linux-kernel - Re: 3.20-rc0: GUI dies on resume, then systemd gots sigill

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <2254794.AHR7M2FYHX@vostro.rjw.lan>
Date:	Wed, 18 Feb 2015 17:39:08 +0100
From:	"Rafael J. Wysocki" <rjw@...ysocki.net>
To:	Pavel Machek <pavel@....cz>
Cc:	kernel list <linux-kernel@...r.kernel.org>,
	Linux-pm mailing list <linux-pm@...ts.osdl.org>
Subject: Re: 3.20-rc0: GUI dies on resume, then systemd gots sigill

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

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/