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

From: Pavel Machek
Date: Wed Feb 18 2015 - 14:01:00 EST


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?
(cesky, pictures)
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at
Please read the FAQ at