Hi,
I notice a regression report on Bugzilla [1]. Quoting from it:
> I'm having some weird issues with sleep mode on any 6.x Linux kernel version - it's a toss-up when I close the lid as to whether it will sleep properly or not - when it fails, the screen will lock, but it will not actually enter S3 sleep - it just blanks the screen, but the laptop stays on (and fan does too).
>
> Opening the lid after a failed sleep attempt turns on the screen instantaneously, and it doesn't even need to reconnect to WiFi - this doesn't happen when actually resuming from sleep, it takes a couple seconds for the screen to come on, and it then needs to reconnect the network.
>
> Following the failed attempt to enter sleep mode (closing the lid), the following entries appear in the system log -
>
> arkiron kernel: ACPI Error: Thread 3233415168 cannot release Mutex [ECMX] acquired by thread 3268191936 (20221020/exmutex-378)
> arkiron kernel: ACPI Error: Aborting method \_SB.PCI0.LPCB.ECDV._Q66 due to previous error (AE_AML_NOT_OWNER) (20221020/psparse-529)
> arkiron kernel: Non-boot CPUs are not disabled
>
> Now, the "Non-boot CPUs are not disabled" line stands out the most to me here, because successful sleep attempts won't have this line in the log.
>
> After the failed attempt above to sleep, I now close the lid again, and it seemingly goes to sleep successfully. After checking the log following this, I find two new error lines in the log -
>
> arkiron kernel: ACPI Error: Thread 3233415168 cannot release Mutex [ECMX] acquired by thread 3268191936 (20221020/exmutex-378)
> arkiron kernel: ACPI Error: Aborting method \_SB.PCI0.LPCB.ECDV._Q66 due to previous error (AE_AML_NOT_OWNER) (20221020/psparse-529)
>
> Note that this time the CPU line is missing, as expected for a successful sleep attempt.
>
> This happens on both latest stable Linux kernel 6.5 as well as the latest Linux LTS 6.1 kernel. The last kernel that this didn't happen on was Linux LTS 5.15 (any version), which is what I was running up until the Linux LTS 6.1 upgrade. At that point I tried switching back to mainline (6.5) to see if it would fix sleep issues, but it didn't help. Downgrading to Linux LTS 5.15 did fix the sleep issues and the laptop seems to sleep reliably now. Running LTS 5.15.131-1 without issue as I am making this report.
>
> I'm on a Dell Inspiron 15 5593 using BIOS ver 1.27.0 (latest as of now), running Arch Linux x86_64
See Bugzilla for the full thread.
Anyway, I'm adding it to regzbot:
#regzbot introduced: v5.15..v6.1 https://bugzilla.kernel.org/show_bug.cgi?id=217950
[1]: https://bugzilla.kernel.org/show_bug.cgi?id=217950
--
An old man doll... just what I always wanted! - Clara
On Tue, Sep 26, 2023 at 07:25:48AM +0700, Bagas Sanjaya wrote:
> Hi,
>
> I notice a regression report on Bugzilla [1]. Quoting from it:
>
> > I'm having some weird issues with sleep mode on any 6.x Linux kernel version - it's a toss-up when I close the lid as to whether it will sleep properly or not - when it fails, the screen will lock, but it will not actually enter S3 sleep - it just blanks the screen, but the laptop stays on (and fan does too).
> >
> > Opening the lid after a failed sleep attempt turns on the screen instantaneously, and it doesn't even need to reconnect to WiFi - this doesn't happen when actually resuming from sleep, it takes a couple seconds for the screen to come on, and it then needs to reconnect the network.
> >
> > Following the failed attempt to enter sleep mode (closing the lid), the following entries appear in the system log -
> >
> > arkiron kernel: ACPI Error: Thread 3233415168 cannot release Mutex [ECMX] acquired by thread 3268191936 (20221020/exmutex-378)
> > arkiron kernel: ACPI Error: Aborting method \_SB.PCI0.LPCB.ECDV._Q66 due to previous error (AE_AML_NOT_OWNER) (20221020/psparse-529)
> > arkiron kernel: Non-boot CPUs are not disabled
> >
> > Now, the "Non-boot CPUs are not disabled" line stands out the most to me here, because successful sleep attempts won't have this line in the log.
> >
> > After the failed attempt above to sleep, I now close the lid again, and it seemingly goes to sleep successfully. After checking the log following this, I find two new error lines in the log -
> >
> > arkiron kernel: ACPI Error: Thread 3233415168 cannot release Mutex [ECMX] acquired by thread 3268191936 (20221020/exmutex-378)
> > arkiron kernel: ACPI Error: Aborting method \_SB.PCI0.LPCB.ECDV._Q66 due to previous error (AE_AML_NOT_OWNER) (20221020/psparse-529)
> >
> > Note that this time the CPU line is missing, as expected for a successful sleep attempt.
> >
> > This happens on both latest stable Linux kernel 6.5 as well as the latest Linux LTS 6.1 kernel. The last kernel that this didn't happen on was Linux LTS 5.15 (any version), which is what I was running up until the Linux LTS 6.1 upgrade. At that point I tried switching back to mainline (6.5) to see if it would fix sleep issues, but it didn't help. Downgrading to Linux LTS 5.15 did fix the sleep issues and the laptop seems to sleep reliably now. Running LTS 5.15.131-1 without issue as I am making this report.
> >
> > I'm on a Dell Inspiron 15 5593 using BIOS ver 1.27.0 (latest as of now), running Arch Linux x86_64
>
> See Bugzilla for the full thread.
>
> Anyway, I'm adding it to regzbot:
>
> #regzbot introduced: v5.15..v6.1 https://bugzilla.kernel.org/show_bug.cgi?id=217950
>
> [1]: https://bugzilla.kernel.org/show_bug.cgi?id=217950
>
Hi Thorsten and all,
It seems like the BZ reporter is really busy with his college life; IOW
he can only bisect in the winter break [1]. Should I mark this regression
as inconclusive for now?
Thanks.
[1]: https://bugzilla.kernel.org/show_bug.cgi?id=217950#c5
--
An old man doll... just what I always wanted! - Clara
On 22.11.23 14:21, Bagas Sanjaya wrote:
> On Tue, Sep 26, 2023 at 07:25:48AM +0700, Bagas Sanjaya wrote:
>> I notice a regression report on Bugzilla [1]. Quoting from it:
>>> I'm having some weird issues with sleep mode on any 6.x Linux kernel version - it's a toss-up when I close the lid as to whether it will sleep properly or not - when it fails, the screen will lock, but it will not actually enter S3 sleep - it just blanks the screen, but the laptop stays on (and fan does too).
> [...]
>> #regzbot introduced: v5.15..v6.1 https://bugzilla.kernel.org/show_bug.cgi?id=217950
>>
>> [1]: https://bugzilla.kernel.org/show_bug.cgi?id=217950
>
> Hi Thorsten and all,
Bagas, please ask me things like this in private. Developers get enough
mail already, we should try our best to not increase the amount too much
with stuff that is just there for regression tracking stuff.
> It seems like the BZ reporter is really busy with his college life; IOW
> he can only bisect in the winter break [1]. Should I mark this regression
> as inconclusive for now?
Let's put it on regzbot's back-burner.
#regzbot backburner: will take a while until this is bisected
#regzbot ignore-activity
Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker' hat)
--
Everything you wanna know about Linux kernel regression tracking:
https://linux-regtracking.leemhuis.info/about/#tldr
That page also explains what to do if mails like this annoy you.
On Wed, Nov 22, 2023 at 05:55:20PM +0100, Linux regression tracking #update (Thorsten Leemhuis) wrote:
> On 22.11.23 14:21, Bagas Sanjaya wrote:
> > On Tue, Sep 26, 2023 at 07:25:48AM +0700, Bagas Sanjaya wrote:
> >> I notice a regression report on Bugzilla [1]. Quoting from it:
> >>> I'm having some weird issues with sleep mode on any 6.x Linux kernel version - it's a toss-up when I close the lid as to whether it will sleep properly or not - when it fails, the screen will lock, but it will not actually enter S3 sleep - it just blanks the screen, but the laptop stays on (and fan does too).
> > [...]
> >> #regzbot introduced: v5.15..v6.1 https://bugzilla.kernel.org/show_bug.cgi?id=217950
> >>
> >> [1]: https://bugzilla.kernel.org/show_bug.cgi?id=217950
> >
> > Hi Thorsten and all,
>
> Bagas, please ask me things like this in private. Developers get enough
> mail already, we should try our best to not increase the amount too much
> with stuff that is just there for regression tracking stuff.
Thanks for the pro tip.
>
> > It seems like the BZ reporter is really busy with his college life; IOW
> > he can only bisect in the winter break [1]. Should I mark this regression
> > as inconclusive for now?
>
> Let's put it on regzbot's back-burner.
>
> #regzbot backburner: will take a while until this is bisected
> #regzbot ignore-activity
>
Thanks for the handling!
--
An old man doll... just what I always wanted! - Clara