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?
>
> Did init 3, login as root, suspend, and yes, systemd got SIGILL.
Tried it on desktop machine, when I press the power buton machine
power ups CD rom, but that's pretty much it. Not even power LED turns
on.
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures)
http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
