All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: "Rafael J. Wysocki" <rjw@rjwysocki.net>
Cc: kernel list <linux-kernel@vger.kernel.org>,
	Linux-pm mailing list <linux-pm@lists.osdl.org>
Subject: Re: 3.20-rc0: GUI dies on resume, then systemd gots sigill
Date: Wed, 18 Feb 2015 20:00:52 +0100	[thread overview]
Message-ID: <20150218190052.GA25491@amd> (raw)
In-Reply-To: <2254794.AHR7M2FYHX@vostro.rjw.lan>

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

  reply	other threads:[~2015-02-18 19:00 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-18  9:46 3.20-rc0: GUI dies on resume, then systemd gots sigill Pavel Machek
2015-02-18 16:39 ` Rafael J. Wysocki
2015-02-18 19:00   ` Pavel Machek [this message]
2015-02-18 19:11     ` Pavel Machek
2015-02-18 20:38       ` Pavel Machek
2015-03-02 10:32         ` Pavel Machek
2015-02-19  1:09     ` Rafael J. Wysocki

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20150218190052.GA25491@amd \
    --to=pavel@ucw.cz \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@lists.osdl.org \
    --cc=rjw@rjwysocki.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.