linux-kernel - Re: [regression] Bug 216782 - resume from suspend broken on Asus UX305FA

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>] [day] [month] [year] [list]

Message-ID: <dec37fc9-1a69-74dc-d613-d806c732ffd7@leemhuis.info>
Date:   Thu, 8 Dec 2022 19:41:27 +0100
From:   Thorsten Leemhuis <regressions@...mhuis.info>
To:     Bjorn Helgaas <bhelgaas@...gle.com>
Cc:     "regressions@...ts.linux.dev" <regressions@...ts.linux.dev>,
        Linux PCI <linux-pci@...r.kernel.org>,
        LKML <linux-kernel@...r.kernel.org>,
        Linux PM <linux-pm@...r.kernel.org>,
        Tasev Nikola <tasev.stefanoska@...net.be>
Subject: Re: [regression] Bug 216782 - resume from suspend broken on Asus UX305FA

Hi, this is your Linux kernel regression tracker.

On 08.12.22 15:43, Thorsten Leemhuis wrote:
> 
> I noticed a regression report in bugzilla.kernel.org. It afaics needs
> more debugging, but I nevertheless want add it to the tracking.

Bjorn, if you have a minute, could you please take a quick look at this
please: https://bugzilla.kernel.org/show_bug.cgi?id=216782

To quote

```
> Starting from kernel 6.1-rc1 for the first time in 8 years the
> resume
> from suspend is broken on my Asus UX305FA. After resume the sysrsq keys
> do not work and a hard reset is the only solution for shutdown, the
> screen is black, keyboard and mouse do not respond.
> 
> After bisecting the first bad commit is:
> 
> commit a47126ec29f538e1197862919f94d3b6668144a4
> Author: Bjorn Helgaas <bhelgaas@...gle.com>
> Date:   Fri Sep 9 15:24:57 2022 -0500
> 
>     PCI/PTM: Cache PTM Capability offset
>     
>     Cache the PTM Capability offset instead of searching for it every time we
>     enable/disable PTM or save/restore PTM state.  No functional change
>     intended.
```

The reporter has some trouble with the bisection (see the ticket for
details), but it looks a bit like the problems are actually caused by
that patch or something in that series.

Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker' hat)

P.S.: As the Linux kernel's regression tracker I deal with a lot of
reports and sometimes miss something important when writing mails like
this. If that's the case here, don't hesitate to tell me in a public
reply, it's in everyone's interest to set the public record straight.