From: Marc Zyngier <marc.zyngier@arm.com>
To: Masahiro Yamada <yamada.masahiro@socionext.com>,
Thomas Gleixner <tglx@linutronix.de>
Cc: Tomi Sarvela <tomi.p.sarvela@intel.com>,
Martin Peres <martin.peres@linux.intel.com>,
Jeffy Chen <jeffy.chen@rock-chips.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Suspend-resume failure on Intel Eagle Lake Core2Duo
Date: Thu, 3 Aug 2017 09:41:49 +0100 [thread overview]
Message-ID: <fdf71b0f-dd38-60e5-d96e-caedc2754a0b@arm.com> (raw)
In-Reply-To: <CAK7LNAQZB+VqWSxjfmjnzDJx3q1i-Da1SAaqbC4099qK7OwAfg@mail.gmail.com>
Hi Masahiro,
On 03/08/17 08:32, Masahiro Yamada wrote:
> Hi.
>
> 2017-08-01 0:55 GMT+09:00 Thomas Gleixner <tglx@linutronix.de>:
>> On Mon, 31 Jul 2017, Tomi Sarvela wrote:
>>> On 31/07/17 18:06, Thomas Gleixner wrote:
>>>> Can you please remove the patch. And try the following:
>>>>
>>>> # echo N > /sys/module/printk/parameters/console_suspend
>>>>
>>>> # echo mem > /sys/power/state
>>>>
>>>> and log the output of the serial console. That way we might get a clue
>>>> where it gets stuck.
>>>
>>> I'm afraid it hangs right away. No response from SSH, no output to serial.
>>
>> What means hangs right away? Is there no output at all on the serial
>> console? Or does it just stop at some point?
>>
>> Thanks,
>>
>> tglx
>>
>
> Sorry for jumping in.
> Finally, I found this thread.
>
>
> My environment is completely different (ARM64 board),
> I am also suffering from a hibernation problem
> since this commit.
>
>
> I get no response on the serial console
> after "Restarting tasks ... done." log message.
>
>
> By reverting bf22ff45bed6 ("genirq: Avoid unnecessary low level
> irq function calls", I can get hibernation working again.
>
>
> SW info:
> defconfig: arch/arm64/configs/defconfig
> DT : arch/arm64/boot/dts/socionext/uniphier-ld20-ref.dts
> PSCI : ARM Trusted Firmware
>
>
> SoC info:
> CPU : Cortex-A72 * 2 + Cortex-A53 * 2
> irqchip : GICv3 (drivers/irq/irq-gic-v3.c)
Let me take an educated guess: It feels like your firmware doesn't
save/restore the GIC context across suspend/resume. Is that something
you could check, assuming you have access to the firmware source code?
Thanks,
M.
--
Jazz is not dead. It just smells funny...
next prev parent reply other threads:[~2017-08-03 8:41 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-24 13:45 Suspend-resume failure on Intel Eagle Lake Core2Duo Martin Peres
2017-07-24 15:28 ` Thomas Gleixner
2017-07-24 15:41 ` Martin Peres
2017-07-24 16:35 ` Thomas Gleixner
2017-07-24 16:37 ` Martin Peres
2017-07-25 7:01 ` Tomi Sarvela
2017-07-26 13:47 ` Martin Peres
2017-07-26 14:26 ` Thomas Gleixner
2017-07-27 7:36 ` Tomi Sarvela
2017-07-27 7:42 ` Thomas Gleixner
2017-07-27 8:12 ` Tomi Sarvela
2017-07-27 19:42 ` Thomas Gleixner
2017-07-27 20:13 ` Thomas Gleixner
2017-07-27 21:08 ` Thomas Gleixner
2017-07-28 12:29 ` Tomi Sarvela
2017-07-28 12:42 ` Thomas Gleixner
2017-07-28 13:15 ` Thomas Gleixner
2017-07-28 13:25 ` Tomi Sarvela
2017-07-28 14:13 ` Thomas Gleixner
2017-07-28 14:46 ` Tomi Sarvela
2017-07-28 14:50 ` Thomas Gleixner
2017-07-28 14:55 ` Tomi Sarvela
2017-07-28 16:26 ` Thomas Gleixner
2017-07-31 7:21 ` Tomi Sarvela
2017-07-31 7:45 ` Thomas Gleixner
2017-07-31 7:55 ` Tomi Sarvela
2017-07-31 8:29 ` Thomas Gleixner
2017-07-31 8:41 ` Tomi Sarvela
2017-07-31 14:04 ` Thomas Gleixner
2017-07-31 14:13 ` Tomi Sarvela
2017-07-31 15:06 ` Thomas Gleixner
2017-07-31 15:44 ` Tomi Sarvela
2017-07-31 15:55 ` Thomas Gleixner
2017-08-03 7:32 ` Masahiro Yamada
2017-08-03 8:23 ` Peter Zijlstra
2017-08-03 8:41 ` Marc Zyngier [this message]
2017-08-03 12:52 ` Masahiro Yamada
2017-08-03 13:30 ` Marc Zyngier
2017-08-07 4:45 ` Masahiro Yamada
2017-08-07 8:17 ` Marc Zyngier
2017-08-08 1:30 ` Masahiro Yamada
2017-08-08 7:39 ` Marc Zyngier
2017-08-09 4:03 ` Masahiro Yamada
2017-07-31 8:35 ` Thomas Gleixner
2017-07-28 12:34 ` Martin Peres
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=fdf71b0f-dd38-60e5-d96e-caedc2754a0b@arm.com \
--to=marc.zyngier@arm.com \
--cc=jeffy.chen@rock-chips.com \
--cc=linux-kernel@vger.kernel.org \
--cc=martin.peres@linux.intel.com \
--cc=tglx@linutronix.de \
--cc=tomi.p.sarvela@intel.com \
--cc=yamada.masahiro@socionext.com \
/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).