netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Regressions <regressions@lists.linux.dev>,
	Linux Networking <netdev@vger.kernel.org>,
	Linux Intel Wireless WAN <linuxwwan@intel.com>
Cc: M Chetan Kumar <m.chetan.kumar@linux.intel.com>,
	"David S. Miller" <davem@davemloft.net>,
	Loic Poulain <loic.poulain@linaro.org>,
	Sergey Ryazanov <ryazanov.s.a@gmail.com>,
	Johannes Berg <johannes@sipsolutions.net>
Subject: Fwd: Intel 7560 LTE Modem stops working after resuming from standby
Date: Thu, 12 Oct 2023 16:52:50 +0700	[thread overview]
Message-ID: <267abf02-4b60-4a2e-92cd-709e3da6f7d3@gmail.com> (raw)

Hi,

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

See Bugzilla for the full thread.

Anyway, I'm adding this regression to regzbot:

#regzbot introduced: e4f5073d53be6c https://bugzilla.kernel.org/show_bug.cgi?id=217996
#regzbot title: pm support for Intel 7560 makes the modem stops working after resume

Thanks.

[1]: https://bugzilla.kernel.org/show_bug.cgi?id=217996

-- 
An old man doll... just what I always wanted! - Clara

             reply	other threads:[~2023-10-12  9:52 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-12  9:52 Bagas Sanjaya [this message]
2023-10-12 16:54 ` Intel 7560 LTE Modem stops working after resuming from standby Loic Poulain
2023-10-13  0:04   ` Bagas Sanjaya
2023-10-16 13:18     ` Loic Poulain
2023-10-17  7:08       ` Bagas Sanjaya
2023-10-12 23:57 ` Fwd: " Bagas Sanjaya

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=267abf02-4b60-4a2e-92cd-709e3da6f7d3@gmail.com \
    --to=bagasdotme@gmail.com \
    --cc=davem@davemloft.net \
    --cc=johannes@sipsolutions.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxwwan@intel.com \
    --cc=loic.poulain@linaro.org \
    --cc=m.chetan.kumar@linux.intel.com \
    --cc=netdev@vger.kernel.org \
    --cc=regressions@lists.linux.dev \
    --cc=ryazanov.s.a@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).