Bug 211227
Summary: | [BISECTED][REGRESSION] Linux 5.10.7 breaks s3 resume on opal encrypted ssd | ||
---|---|---|---|
Product: | IO/Storage | Reporter: | chriscjsus |
Component: | SCSI | Assignee: | linux-scsi (linux-scsi) |
Status: | RESOLVED CODE_FIX | ||
Severity: | normal | CC: | bvanassche, stern |
Priority: | P1 | ||
Hardware: | x86-64 | ||
OS: | Linux | ||
Kernel Version: | 5.10.7 | Subsystem: | |
Regression: | Yes | Bisected commit-id: | |
Attachments: | Debug patch. |
Description
chriscjsus
2021-01-16 07:08:09 UTC
Thank you for having reported this. Please apply the attached patch to kernel v5.11 and report which kernel warnings are reported when booting the resulting patched kernel. Please note that the attached patch is not a fix but rather an attempt to extract more information about how the SED OPAL code is incompatible with the Linux power management model. Created attachment 295369 [details]
Debug patch.
I patched kernel 5.10.17 and there was no debug messages from your patch in either the console, dmesg, or the journal. I booted with parameters no_console_suspend=1 and ignore_loglevel. Your patch does however fix the issue. If I boot without your patch, resume from S3 hangs and I need to reboot using alt-sysreq-b. If I boot with your patch, resume from S3 is normal and the drive is obviously being unlocked. When power is cut from the drive during S3, it locks itself automatically and needs to be unlocked by the kernel on resume. Forgot to mention that CONFIG_PM=y in the kernel configs that I use. Fixed in 5.10.20 and 5.11.3. |