Re: 4.13 breaks suspend to ram wakeup
From: Ming Lei
Date: Wed Sep 20 2017 - 21:29:22 EST
On Thu, Sep 21, 2017 at 12:48 AM, Norbert Preining <preining@xxxxxxxx> wrote:
> Dear all,
> thanks for the quick feedback.
> On Wed, 20 Sep 2017, Ming Lei wrote:
>> Looks your issue is very similar with Oleksandr's report:
> Indeed, I am using dm-crypt (full disk encryption) and
> Any suggestion what should be selected instead?
The previous reports are all with blk-mq enabled, since it is quite easy to
reproduce on blk-mq, but in theory there should be such issue on
block legacy when the request pool is used up, that means it can be
a bit hard to trigger in this case.
So could you share us how often it is triggered? and what is your underlying
disk behind dm-crypt?
BTW, you can debug and collect some dmesg log during system suspend/resume
without serial console:
1) pass 'no_console_suspend' to kernel cmdline
2) start a vga console via 'ctrl + alt + F1/F2/...'
3) run the following commands to start system suspend test:
echo 9 > /proc/sys/kernel/printk
echo devices > /sys/power/pm_test
echo mem > /sys/power/state
4) system will be waken up after 5 seconds
5) if the current console is hang after system resume, either you
wait for the hang log is triggered in console after 2 minutes, or you
can try to login from another vga console via 'ctrl + alt + F2/F3/...' and
try to collect dmesg log to see if there is hang
>> And Oleksandr tested the following patchset can fix his issue:
> Do you have a patch against 4.13? I tried applying the following
> patches from git format-patch ebb2c2437d8008d467969
> to current 4.13, but without success.
> (I don't want to play with .14-pre kernels by now.)
Please get the patches backported to v4.13 in the following tree: