linux-kernel - Re: [PM] bfcc1e67ff: kernel-selftests.breakpoints.step_after_suspend

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <e526de16-5efd-6474-20e1-3f96a2e3c524@intel.com>
Date:   Thu, 14 Oct 2021 21:23:37 +0200
From:   "Rafael J. Wysocki" <rafael.j.wysocki@...el.com>
To:     Florian Fainelli <f.fainelli@...il.com>
CC:     LKML <linux-kernel@...r.kernel.org>,
        Linux Memory Management List <linux-mm@...ck.org>,
        <lkp@...ts.01.org>, <lkp@...el.com>,
        kernel test robot <oliver.sang@...el.com>
Subject: Re: [PM] bfcc1e67ff:
 kernel-selftests.breakpoints.step_after_suspend_test.fail

On 10/14/2021 6:26 PM, Florian Fainelli wrote:
> On 10/14/21 12:57 AM, kernel test robot wrote:
>>
>> Greeting,
>>
>> FYI, we noticed the following commit (built with gcc-9):
>>
>> commit: bfcc1e67ff1e4aa8bfe2ca57f99390fc284c799d ("PM: sleep: Do not assume that "mem" is always present")
>> https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git master
>>
>>
>> in testcase: kernel-selftests
>> version: kernel-selftests-x86_64-c8c9111a-1_20210929
>> with following parameters:
>>
>> 	group: group-00
>> 	ucode: 0x11
>>
>> test-description: The kernel contains a set of "self tests" under the tools/testing/selftests/ directory. These are intended to be small unit tests to exercise individual code paths in the kernel.
>> test-url: https://www.kernel.org/doc/Documentation/kselftest.txt
>>
>>
>> on test machine: 288 threads 2 sockets Intel(R) Xeon Phi(TM) CPU 7295 @ 1.50GHz with 80G memory
>>
>> caused below changes (please refer to attached dmesg/kmsg for entire log/backtrace):
>>
>>
>>
>>
>> If you fix the issue, kindly add following tag
>> Reported-by: kernel test robot <oliver.sang@...el.com>
> Thanks for your report. Assuming that the code responsible for
> registering the suspend operations is drivers/acpi/sleep.c for your
> platform, and that acpi_sleep_suspend_setup() iterated over all possible
> sleep states, your platform must somehow be returning that ACPI_STATE_S3
> is not a supported state somehow?
>
> Rafael have you ever encountered something like that?

Yes, there are systems with ACPI that don't support S3.


>>
>> TAP version 13
>> 1..2
>> # selftests: breakpoints: step_after_suspend_test
>> # TAP version 13
>> # Bail out! Failed to enter Suspend state
>> # # Totals: pass:0 fail:0 xfail:0 xpass:0 skip:0 error:0
>> not ok 1 selftests: breakpoints: step_after_suspend_test # exit=1
>>
>>
>>
>> To reproduce:
>>
>>          git clone https://github.com/intel/lkp-tests.git
>>          cd lkp-tests
>>          sudo bin/lkp install job.yaml           # job file is attached in this email
>>          bin/lkp split-job --compatible job.yaml # generate the yaml file for lkp run
>>          sudo bin/lkp run generated-yaml-file
>>
>>          # if come across any failure that blocks the test,
>>          # please remove ~/.lkp and /lkp dir to run from a clean state.
>>
>>
>>
>> ---
>> 0DAY/LKP+ Test Infrastructure                   Open Source Technology Center
>> https://lists.01.org/hyperkitty/list/lkp@lists.01.org       Intel Corporation
>>
>> Thanks,
>> Oliver Sang
>>
>