linux-kernel - Re: Intel 7560 LTE Modem stops working after resuming from standby

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: <CAMZdPi9RDSAsA8bCwN1f-4v3Ahqh8+eFLTArdyE5qZeocAMhtQ@mail.gmail.com>
Date:   Thu, 12 Oct 2023 18:54:11 +0200
From:   Loic Poulain <loic.poulain@...aro.org>
To:     Bagas Sanjaya <bagasdotme@...il.com>,
        M Chetan Kumar <m.chetan.kumar@...ux.intel.com>
Cc:     Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Linux Regressions <regressions@...ts.linux.dev>,
        Linux Networking <netdev@...r.kernel.org>,
        Linux Intel Wireless WAN <linuxwwan@...el.com>,
        "David S. Miller" <davem@...emloft.net>,
        Sergey Ryazanov <ryazanov.s.a@...il.com>,
        Johannes Berg <johannes@...solutions.net>
Subject: Re: Intel 7560 LTE Modem stops working after resuming from standby

Hi Chetan,

On Thu, 12 Oct 2023 at 11:52, Bagas Sanjaya <bagasdotme@...il.com> wrote:
> I notice a regression report on Bugzilla [1]. Quoting from it:
>
> > I noticed a few days ago, after Fedora moved to Kernel 6.5, that my Intel LTE Modem was not working anymore after resuming from standby.
> >
> > The journal listed this error message multiple times:
> > kernel: iosm 0000:01:00.0: msg timeout
> >
> > It took me a while to determine the root cause of the problem, since the modem did not work either in the following warm reboots.
> > Only a shutdown revived the modem.
> >
> > I did a bisection of the error and I was able to find the culprit:
> >
> > [e4f5073d53be6cec0c654fac98372047efb66947] net: wwan: iosm: enable runtime pm support for 7560

Any quick fix for this issue? alternatively we will probably revert e4f5073d53.

Regards,
Loic