linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: pavel@ucw.cz (Pavel Machek)
To: linux-arm-kernel@lists.infradead.org
Subject: Linux fails to start secondary cores when system resumes from Suspend-to-RAM
Date: Fri, 30 Dec 2016 21:10:59 +0100	[thread overview]
Message-ID: <20161230201059.GB22935@amd> (raw)
In-Reply-To: <4dc90086-180d-df9a-297f-6f4680de7bdd@free.fr>

Hi!

On Thu 2016-12-29 15:27:12, Mason wrote:
> On Thu, Dec 15, 2016 at 11:18 PM, Mason wrote:
> 
> > However, while Linux successfully starts the secondary cores when
> > the system first boots, it fails when the system resumes from "S3".
> 
> Oh boy...
> 
> Turns out the firmware was, in fact, (upon resume) stomping over parts
> of the Linux memory image in RAM, triggering all kinds of "interesting"
> nasal demons when Linux ran (or, more accurately, limped).

Well... firmware is always fun :-). Good that it got solved...

									Pavel
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 181 bytes
Desc: Digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20161230/7f8c5b18/attachment.sig>

      reply	other threads:[~2016-12-30 20:10 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-15 15:18 Linux fails to start secondary cores when system resumes from Suspend-to-RAM Mason
2016-12-16  5:14 ` Yu Chen
2016-12-16  7:25   ` Mason
2016-12-29 12:10     ` Mason
2016-12-29 14:27       ` Mason
2016-12-30 20:10         ` Pavel Machek [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=20161230201059.GB22935@amd \
    --to=pavel@ucw.cz \
    --cc=linux-arm-kernel@lists.infradead.org \
    /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;
as well as URLs for NNTP newsgroup(s).