Private bug reported:

[Description]
After resuming from states such as airplane mode, reboot, cold boot, s0ix and 
wwan radio disabled, user needs to manually connect using the "nmcli conn up 
<APN name>" command or turn off Mobile broadband and connect to the APN profile 
to be able to connect to cellular. Need more information why stalling is 
happening with reconnection using this kernel.

[Expected Result]
After resuming from the mentioned states, user should be able to establish 
Mobile broadband connection right after selecting the APN profile right away.

[Actual Result]
After resuming from the mentioned states, user is unable to establish Mobile 
broadband connection right after selecting the APN profile right away.

[Workaround]
User needs to manually reconnect to cellular by either of the following:
1) running nmcli conn up '<APN profile>'
2) turning off Mobile broadband and  then reconnecting to the APN profile via 
Mobile broadband GUI


In the attached zip file, modem logs were collected following the results:

[Airplane mode]
1 minute - PASS
5 minutes - FAIL
15 minutes - FAIL

[WWAN radio]
1 minute - PASS
5 minutes - PASS
15 minutes - FAIL

[S0ix]
1 minute - PASS
5 minutes - FAIL ([manufacturer unknown] model unknown/mobile broadband 
unavailable error appears)
15 minutes - N/A

According to Intel,

"In logs it is observed that there is ~1 minute gap between modem being
enabled back after airplane mode and pdp getting established.

This stall is not alone in MM. Syslog indicates that there is stall in
entire system level logging for almost a min. After this stall, MM is able to 
establish successful PDP connection within the same second."

Jul 13 16:05:56 ubuntu-ThinkPad-T14-Gen-3 systemd[1]:
systemd-rfkill.service: Succeeded.

Jul 13 16:06:51 ubuntu-ThinkPad-T14-Gen-3 ModemManager[811]: <info>
[modem1] 3GPP registration state changed (home -> idle)

Jul 13 16:06:51 ubuntu-ThinkPad-T14-Gen-3 ModemManager[811]: <info>
[modem1] state changed (connecting -> connected)

Jul 13 16:06:51 ubuntu-ThinkPad-T14-Gen-3 ModemManager[811]: <info>
[modem1] simple connect state (8/8): all done

"In the provided logs I can see that there is no issue or delay
observed in establishment of PDP connection. It is taking
approximately 4-6 seconds for PDP establishment.

Please find file level analysis as below."

radio.txt-

-------------

"Only one instance of airplane mode toggling was observed. PDP
re-established within ~4 seconds of switching off airplane mode and
within ~2 seconds of registration."

ModemManager[4773]: <debug> [1658906907.307452] [modem0] updating
power state: 'on'...

ModemManager[4773]: <info> [1658906909.236937] [modem0] state changed
(enabled -> registered)

ModemManager[4773]: <info> [1658906911.841261] [modem0] simple
connect started...

ModemManager[4773]: <info> [1658906911.854284] [modem0] state changed
(connecting -> connected)

s0ix.txt-

----------

"No instance of airplane mode toggling. During boot up PDP has been
established within the same second of PDP connection request."

ModemManager[5412]: <debug> [1658908777.915076] [modem0] updating
power state: 'on'...

ModemManager[5412]: <info> [1658908779.774030] [modem0] state changed
(enabled -> registered)

ModemManager[5412]: <info> [1658908789.113728] [modem0] simple
connect started...

ModemManager[5412]: <info> [1658908789.129582] [modem0] state changed
(connecting -> connected)

"There seems to be an issue with data connection observed later though.
MM is triggering PDP connection request and modem is responding
with error. Need to be analysed from modem end what is the issue."

ModemManager[5412]: <warn> [1658908877.516999] [modem1/bearer3]
connection attempt #1 failed: Unknown error

ModemManager[5412]: <warn> [1658908877.613880] [modem1/bearer3]
connection attempt #2 failed: Unknown error

ModemManager[5412]: <warn> [1658908877.717007] [modem1/bearer3]
connection attempt #3 failed: Unknown error

ModemManager[5412]: <warn> [1658908877.821648] [modem1/bearer3]
connection attempt #4 failed: Unknown error

ModemManager[5412]: <warn> [1658908877.933048] [modem1/bearer4]
connection attempt #1 failed: Unknown error

ModemManager[5412]: <warn> [1658908877.989101] [modem1/bearer5]
connection attempt #1 failed: Unknown error

ModemManager[5412]: <warn> [1658908878.073209] [modem1/bearer6]
connection attempt #1 failed: Unknown error

ModemManager[5412]: <warn> [1658908878.173125] [modem1/bearer4]
connection attempt #2 failed: Unknown error

ModemManager[5412]: <warn> [1658908878.253013] [modem1/bearer5]
connection attempt #2 failed: Unknown error

ModemManager[5412]: <warn> [1658908878.333056] [modem1/bearer6]
connection attempt #2 failed: Unknown error

ModemManager[5412]: <warn> [1658908878.440927] [modem1/bearer4]
connection attempt #3 failed: Unknown error

ModemManager[5412]: <warn> [1658908878.521164] [modem1/bearer5]
connection attempt #3 failed: Unknown error

ModemManager[5412]: <warn> [1658908878.601119] [modem1/bearer6]
connection attempt #3 failed: Unknown error

ModemManager[5412]: <warn> [1658908878.684948] [modem1/bearer4]
connection attempt #4 failed: Unknown error

ModemManager[5412]: <warn> [1658908878.753110] [modem1/bearer5]
connection attempt #4 failed: Unknown error

ModemManager[5412]: <warn> [1658908878.825084] [modem1/bearer6]
connection attempt #4 failed: Unknown error

radio.txt-

------------

"Only one instance of airplane mode toggling was observed. PDP
re-established within ~6 seconds of switching off airplane mode and
within ~4 seconds of registration."

ModemManager[5105]: <debug> [1658907769.656770] [modem0] updating
power state: 'on'...

ModemManager[5105]: <info> [1658907771.215538] [modem0] state changed
(enabled -> registered)

ModemManager[5105]: <info> [1658907775.095099] [modem0] simple
connect started...

ModemManager[5105]: <info> [1658907775.105951] [modem0] state changed
(connecting -> connected)

"There seems to be an issue with data connection observed later though.
MM is triggering PDP connection request and modem is responding with
error."

[Environment]
System: Griffin (T14 Gen 3)
OS: Ubuntu 20.04.4 LTS
Kernel: 5.15.0-33-generic (hwe-kernel)
CPU: 12th Gen Intel Core i7-1280P
GPU: llvmpipe (LLVM 12.0.0)
FW: SMS45506246_bender_209766_modem_M2_7560_NAND_row_signed_LENOVO_LINUX
Sim card - Softbank, AU/KDDI (Japanese sim cards)

** Affects: linux (Ubuntu)
     Importance: Undecided
         Status: New


** Tags: ihv-intel

** Attachment added: "modem logs, sosreport before and after issue happened"
   
https://bugs.launchpad.net/bugs/1983071/+attachment/5605806/+files/07292022.zip

** Information type changed from Public to Private Security

** Information type changed from Private Security to Public Security

** Information type changed from Public Security to Private

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1983071

Title:
  [L860-R+] Need to manually reconnect to cellular after waking from
  cold boot/reboot/airplane mode/wwan radio disabled/reboot/s0ix state

Status in linux package in Ubuntu:
  New

Bug description:
  [Description]
  After resuming from states such as airplane mode, reboot, cold boot, s0ix and 
wwan radio disabled, user needs to manually connect using the "nmcli conn up 
<APN name>" command or turn off Mobile broadband and connect to the APN profile 
to be able to connect to cellular. Need more information why stalling is 
happening with reconnection using this kernel.

  [Expected Result]
  After resuming from the mentioned states, user should be able to establish 
Mobile broadband connection right after selecting the APN profile right away.

  [Actual Result]
  After resuming from the mentioned states, user is unable to establish Mobile 
broadband connection right after selecting the APN profile right away.

  [Workaround]
  User needs to manually reconnect to cellular by either of the following:
  1) running nmcli conn up '<APN profile>'
  2) turning off Mobile broadband and  then reconnecting to the APN profile via 
Mobile broadband GUI

  
  In the attached zip file, modem logs were collected following the results:

  [Airplane mode]
  1 minute - PASS
  5 minutes - FAIL
  15 minutes - FAIL

  [WWAN radio]
  1 minute - PASS
  5 minutes - PASS
  15 minutes - FAIL

  [S0ix]
  1 minute - PASS
  5 minutes - FAIL ([manufacturer unknown] model unknown/mobile broadband 
unavailable error appears)
  15 minutes - N/A

  According to Intel,

  "In logs it is observed that there is ~1 minute gap between modem being
  enabled back after airplane mode and pdp getting established.

  This stall is not alone in MM. Syslog indicates that there is stall in
  entire system level logging for almost a min. After this stall, MM is able to 
establish successful PDP connection within the same second."

  Jul 13 16:05:56 ubuntu-ThinkPad-T14-Gen-3 systemd[1]:
  systemd-rfkill.service: Succeeded.

  Jul 13 16:06:51 ubuntu-ThinkPad-T14-Gen-3 ModemManager[811]: <info>
  [modem1] 3GPP registration state changed (home -> idle)

  Jul 13 16:06:51 ubuntu-ThinkPad-T14-Gen-3 ModemManager[811]: <info>
  [modem1] state changed (connecting -> connected)

  Jul 13 16:06:51 ubuntu-ThinkPad-T14-Gen-3 ModemManager[811]: <info>
  [modem1] simple connect state (8/8): all done

  "In the provided logs I can see that there is no issue or delay
  observed in establishment of PDP connection. It is taking
  approximately 4-6 seconds for PDP establishment.

  Please find file level analysis as below."

  radio.txt-

  -------------

  "Only one instance of airplane mode toggling was observed. PDP
  re-established within ~4 seconds of switching off airplane mode and
  within ~2 seconds of registration."

  ModemManager[4773]: <debug> [1658906907.307452] [modem0] updating
  power state: 'on'...

  ModemManager[4773]: <info> [1658906909.236937] [modem0] state changed
  (enabled -> registered)

  ModemManager[4773]: <info> [1658906911.841261] [modem0] simple
  connect started...

  ModemManager[4773]: <info> [1658906911.854284] [modem0] state changed
  (connecting -> connected)

  s0ix.txt-

  ----------

  "No instance of airplane mode toggling. During boot up PDP has been
  established within the same second of PDP connection request."

  ModemManager[5412]: <debug> [1658908777.915076] [modem0] updating
  power state: 'on'...

  ModemManager[5412]: <info> [1658908779.774030] [modem0] state changed
  (enabled -> registered)

  ModemManager[5412]: <info> [1658908789.113728] [modem0] simple
  connect started...

  ModemManager[5412]: <info> [1658908789.129582] [modem0] state changed
  (connecting -> connected)

  "There seems to be an issue with data connection observed later though.
  MM is triggering PDP connection request and modem is responding
  with error. Need to be analysed from modem end what is the issue."

  ModemManager[5412]: <warn> [1658908877.516999] [modem1/bearer3]
  connection attempt #1 failed: Unknown error

  ModemManager[5412]: <warn> [1658908877.613880] [modem1/bearer3]
  connection attempt #2 failed: Unknown error

  ModemManager[5412]: <warn> [1658908877.717007] [modem1/bearer3]
  connection attempt #3 failed: Unknown error

  ModemManager[5412]: <warn> [1658908877.821648] [modem1/bearer3]
  connection attempt #4 failed: Unknown error

  ModemManager[5412]: <warn> [1658908877.933048] [modem1/bearer4]
  connection attempt #1 failed: Unknown error

  ModemManager[5412]: <warn> [1658908877.989101] [modem1/bearer5]
  connection attempt #1 failed: Unknown error

  ModemManager[5412]: <warn> [1658908878.073209] [modem1/bearer6]
  connection attempt #1 failed: Unknown error

  ModemManager[5412]: <warn> [1658908878.173125] [modem1/bearer4]
  connection attempt #2 failed: Unknown error

  ModemManager[5412]: <warn> [1658908878.253013] [modem1/bearer5]
  connection attempt #2 failed: Unknown error

  ModemManager[5412]: <warn> [1658908878.333056] [modem1/bearer6]
  connection attempt #2 failed: Unknown error

  ModemManager[5412]: <warn> [1658908878.440927] [modem1/bearer4]
  connection attempt #3 failed: Unknown error

  ModemManager[5412]: <warn> [1658908878.521164] [modem1/bearer5]
  connection attempt #3 failed: Unknown error

  ModemManager[5412]: <warn> [1658908878.601119] [modem1/bearer6]
  connection attempt #3 failed: Unknown error

  ModemManager[5412]: <warn> [1658908878.684948] [modem1/bearer4]
  connection attempt #4 failed: Unknown error

  ModemManager[5412]: <warn> [1658908878.753110] [modem1/bearer5]
  connection attempt #4 failed: Unknown error

  ModemManager[5412]: <warn> [1658908878.825084] [modem1/bearer6]
  connection attempt #4 failed: Unknown error

  radio.txt-

  ------------

  "Only one instance of airplane mode toggling was observed. PDP
  re-established within ~6 seconds of switching off airplane mode and
  within ~4 seconds of registration."

  ModemManager[5105]: <debug> [1658907769.656770] [modem0] updating
  power state: 'on'...

  ModemManager[5105]: <info> [1658907771.215538] [modem0] state changed
  (enabled -> registered)

  ModemManager[5105]: <info> [1658907775.095099] [modem0] simple
  connect started...

  ModemManager[5105]: <info> [1658907775.105951] [modem0] state changed
  (connecting -> connected)

  "There seems to be an issue with data connection observed later though.
  MM is triggering PDP connection request and modem is responding with
  error."

  [Environment]
  System: Griffin (T14 Gen 3)
  OS: Ubuntu 20.04.4 LTS
  Kernel: 5.15.0-33-generic (hwe-kernel)
  CPU: 12th Gen Intel Core i7-1280P
  GPU: llvmpipe (LLVM 12.0.0)
  FW: SMS45506246_bender_209766_modem_M2_7560_NAND_row_signed_LENOVO_LINUX
  Sim card - Softbank, AU/KDDI (Japanese sim cards)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1983071/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to     : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to