From mboxrd@z Thu Jan 1 00:00:00 1970 From: pavel@ucw.cz (Pavel Machek) Date: Fri, 30 Dec 2016 21:10:59 +0100 Subject: Linux fails to start secondary cores when system resumes from Suspend-to-RAM In-Reply-To: <4dc90086-180d-df9a-297f-6f4680de7bdd@free.fr> References: <8c3c6592-1e9a-10d3-2a89-c22a2a23cf4b@free.fr> <9134f2dd-73f6-73d5-30a0-3129d5440d0a@free.fr> <4dc90086-180d-df9a-297f-6f4680de7bdd@free.fr> Message-ID: <20161230201059.GB22935@amd> To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org 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: