mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Rafael J. Wysocki" <rjw@rjwysocki.net>
To: Pavel Machek <pavel@ucw.cz>
Cc: kernel list <linux-kernel@vger.kernel.org>,
	Linux PM list <linux-pm@vger.kernel.org>,
	Daniel Vetter <daniel.vetter@ffwll.ch>
Subject: Re: 3.20-rc0: GUI dies on resume, then systemd gots sigill
Date: Thu, 19 Feb 2015 02:09:27 +0100	[thread overview]
Message-ID: <2244262.p04RxBg4Pz@vostro.rjw.lan> (raw)
In-Reply-To: <20150218190052.GA25491@amd>

On Wednesday, February 18, 2015 08:00:52 PM Pavel Machek wrote:
> 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?

I'm at a conference, so not really.

CCing Daniel though, he may be able to help.

Rafael


      parent reply	other threads:[~2015-02-19  0:46 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-18  9:46 Pavel Machek
2015-02-18 16:39 ` Rafael J. Wysocki
2015-02-18 19:00   ` Pavel Machek
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 [this message]

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=2244262.p04RxBg4Pz@vostro.rjw.lan \
    --to=rjw@rjwysocki.net \
    --cc=daniel.vetter@ffwll.ch \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=pavel@ucw.cz \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®