Fibocom WWAN FM350-GL suspend error (notebook not suspend)

Bug #1990700 reported by Jan Cernohorsky
42
This bug affects 8 people
Affects Status Importance Assigned to Milestone
HWE Next
Fix Released
Undecided
Unassigned
linux (Ubuntu)
Fix Released
High
You-Sheng Yang
Jammy
Invalid
Undecided
Unassigned
Kinetic
Fix Released
High
You-Sheng Yang
Lunar
Fix Released
High
You-Sheng Yang
linux-oem-6.0 (Ubuntu)
Invalid
Undecided
Unassigned
Jammy
Fix Released
High
You-Sheng Yang
Kinetic
Invalid
Undecided
Unassigned
Lunar
Invalid
Undecided
Unassigned

Bug Description

[SRU Justification]

[Impact]

Fibocom WWAN FM350-GL equipped platform fails to suspend.

[Fix]

Full t7xx driver is still under development and some of them have
already accepted and merged in mainline kernel. The following commits
are once in the mainline and are reverted in v6.0:

  d20ef656f994 net: wwan: t7xx: Add AP CLDMA
  007f26f0d68e net: wwan: t7xx: Infrastructure for early port configuration
  140424d90165 net: wwan: t7xx: PCIe reset rescan
  87dae9e70bf7 net: wwan: t7xx: Enable devlink based fw flashing and
               coredump collection

The first patch implemented the other AP-CLDMA, and with that applied,
platforms in question may suspend and resume normally as every bits are in position.

However, while these patches had been reverted for another revision that is still being worked on by the hardware vendor, a minimum, sauced patch is created to work-around this first to meet project schedules, and will be reverted and superseded with a final, mainline landing revision.

[Test Case]

Trigger suspend and there should be no more suspend errors from t7xx:

  mtk_t7xx 0000:58:00.0: [PM] SAP suspend error: -110
  mtk_t7xx 0000:58:00.0: PM: pci_pm_suspend(): t7xx_pci_pm_suspend+0x0/0x20 [mtk_t7xx] returns -110
  mtk_t7xx 0000:58:00.0: PM: dpm_run_callback(): pci_pm_suspend+0x0/0x1a0 returns -110
  mtk_t7xx 0000:58:00.0: PM: failed to suspend async: error -110

[Where problems could occur]

The t7xx driver is still incomplete and we're staging aforementioned 4 patches in internal experimental kernels for development use.

[Other Info]

This affects Kinetic and above, so only Unstable, Kinetic and OEM-6.0 are nominated for fix.

========== original bug report ==========

Hi,
I found a "little" problem with Fibocom WWAN FM350-GL 5G modem in module mtk_t7xx . Power management for this modem is bad. When the notebook goes to sleep/suspend, kernel module mtk_t7xx return an error:

mtk_t7xx 0000:58:00.0: [PM] SAP suspend error: -110
mtk_t7xx 0000:58:00.0: PM: pci_pm_suspend(): t7xx_pci_pm_suspend+0x0/0x20 [mtk_t7xx] returns -110
mtk_t7xx 0000:58:00.0: PM: dpm_run_callback(): pci_pm_suspend+0x0/0x1a0 returns -110
mtk_t7xx 0000:58:00.0: PM: failed to suspend async: error -110

So power management failed to suspend:
PM: Some devices failed to suspend, or early wake event detected

And the notebook not suspend and wake up again.
It must be this module, because if I remove the module first (modprobe -r), the laptop goes to sleep and wakes up normally.
However, after reinserting the module, the modem no longer appears in the system.

Expected state: sleep occurs when the device is put to sleep - including the modem. When you wake up, you will wake up, including activating the modem and logging into the operator's network.

Description: Ubuntu 20.04.5 LTS
Release: 20.04

lspci -v:
58:00.0 Wireless controller [0d40]: MEDIATEK Corp. Device 4d75 (rev 01)
        Subsystem: Device 1cf8:3500
        Flags: bus master, fast devsel, latency 0, IRQ 17
        Memory at 601e800000 (64-bit, prefetchable) [size=32K]
        Memory at 5e800000 (64-bit, non-prefetchable) [size=8M]
        Memory at 601e000000 (64-bit, prefetchable) [size=8M]
        Capabilities: [80] Express Endpoint, MSI 00
        Capabilities: [d0] MSI-X: Enable+ Count=34 Masked-
        Capabilities: [e0] MSI: Enable- Count=1/32 Maskable+ 64bit+
        Capabilities: [f8] Power Management version 3
        Capabilities: [100] Vendor Specific Information: ID=1556 Rev=1 Len=008 <?>
        Capabilities: [108] Latency Tolerance Reporting
        Capabilities: [110] L1 PM Substates
        Capabilities: [200] Advanced Error Reporting
        Capabilities: [300] Secondary PCI Express
        Kernel driver in use: mtk_t7xx
        Kernel modules: mtk_t7xx

lshw:
*-generic
                description: Wireless controller
                product: MEDIATEK Corp.
                vendor: MEDIATEK Corp.
                physical id: 0
                bus info: pci@0000:58:00.0
                version: 01
                width: 64 bits
                clock: 33MHz
                capabilities: pciexpress msix msi pm bus_master cap_list
                configuration: driver=mtk_t7xx latency=0
                resources: iomemory:600-5ff iomemory:600-5ff irq:17 memory:601e800000-601e807fff memory:5e800000-5effffff memory:601e000000-601e7fffff

modinfo:
modinfo mtk_t7xx
filename: /lib/modules/5.19.10-051910-generic/kernel/drivers/net/wwan/t7xx/mtk_t7xx.ko
license: GPL
description: MediaTek PCIe 5G WWAN modem T7xx driver
author: MediaTek Inc
srcversion: 5FA53465EA0167231B632D4
alias: pci:v000014C3d00004D75sv*sd*bc*sc*i*
depends:
retpoline: Y
intree: Y
name: mtk_t7xx
vermagic: 5.19.10-051910-generic SMP preempt mod_unload modversions
sig_id: PKCS#7
signer: Build time autogenerated kernel key
sig_key: 7E:38:36:48:BB:F2:74:0E:30:57:1B:6E:64:90:57:55:30:C5:AF:45
sig_hashalgo: sha512
signature: 78:1B:C9:7F:DE:D2:BE:87:EA:17:94:14:C2:51:3E:2C:75:03:76:0F:
                36:96:92:9B:88:48:B0:C8:73:E6:88:E4:A2:61:25:E9:16:E8:87:40:
                45:99:CC:50:FD:21:B0:BB:11:0E:B5:8F:CC:5F:47:7A:5E:00:BF:7D:
                77:50:A1:F5:00:24:DC:EF:E6:3E:A0:3B:0A:D7:2E:84:EC:FC:6B:4D:
                9E:42:CD:A2:07:C3:D9:F8:6E:7B:76:12:7F:B9:9B:70:6A:22:3D:09:
                4D:04:98:59:35:2A:95:D1:9A:B3:53:77:BE:E5:3E:50:51:18:D0:CE:
                9A:DB:3B:0E:DA:4D:05:5D:D1:5F:4F:6B:DB:98:47:F3:32:25:D8:AD:
                4E:CE:5F:3E:46:76:D9:F4:FA:28:F2:49:B3:3D:D1:5F:74:CF:69:39:
                D2:B0:64:3D:41:FB:55:1F:AB:D3:76:65:54:C6:06:6E:F7:01:F2:F7:
                CE:CF:6C:76:17:1B:AD:41:69:29:FB:F8:6B:F9:74:3F:65:6B:C5:63:
                98:76:D1:69:24:AA:7E:9D:D0:27:BF:AF:0B:C9:30:3C:1B:2A:AB:B9:
                29:22:D5:6B:16:AB:22:43:16:A0:F6:94:EA:78:E7:54:5F:9B:2D:DA:
                2E:9B:9F:81:E4:E0:B7:93:ED:9D:8F:79:19:1A:03:2C:00:C5:3A:99:
                A4:D0:14:6D:21:61:41:02:EC:8D:48:D5:13:0F:D7:AB:5E:B9:BF:17:
                FA:F3:8C:DE:62:A3:F1:5C:33:9C:FB:72:2F:BF:9F:BD:35:BC:F6:D4:
                DE:69:68:A7:80:FE:4C:ED:F8:02:97:66:CA:D0:7A:49:4A:A8:D5:C5:
                67:48:31:42:F9:41:FB:1A:74:52:97:6D:28:A0:2B:03:DA:73:BF:27:
                0E:84:45:33:40:2D:2F:A9:2C:0D:3A:A5:52:93:1B:E8:6D:27:CD:70:
                7E:56:CF:0C:8E:C7:6C:E0:A7:16:2A:FF:95:C5:DE:B7:97:D5:FB:92:
                28:EE:C6:98:1B:D7:06:A3:9D:26:31:09:1E:A8:09:D4:CF:0F:6C:4F:
                C5:EA:2E:BF:5E:02:02:54:15:A7:A7:86:07:B7:82:3B:C6:68:4A:2F:
                23:BB:DE:45:3D:52:0E:F2:D8:3B:57:E3:2B:AE:51:2A:E3:D1:DE:B7:
                F0:40:5A:0E:F4:8C:3F:40:0D:57:05:4C:5F:F3:32:8E:4A:A3:56:69:
                18:47:8A:F1:91:A2:D6:5F:E9:B3:63:DF:9A:68:0E:F6:37:17:F9:62:
                D8:50:60:AA:E1:45:1C:3E:FA:23:66:CE:6E:19:1C:B0:51:51:C1:CF:
                4E:D7:71:24:07:52:7E:7F:F6:78:FF:7E

mmcli -L:
 /org/freedesktop/ModemManager1/Modem/0 [generic] MBIM [14C3:4D75]

Any idea?
Thank you.
With best regards Jan
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.24
Architecture: amd64
CasperMD5CheckResult: skip
DistroRelease: Ubuntu 20.04
InstallationDate: Installed on 2021-04-10 (532 days ago)
InstallationMedia: Kubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1)
Package: linux (not installed)
ProcEnviron:
 LANGUAGE=cs:en_US
 TERM=xterm-256color
 PATH=(custom, no user)
 LANG=cs_CZ.UTF-8
 SHELL=/bin/bash
Tags: focal
Uname: Linux 5.19.10-051910-generic x86_64
UnreportableReason: The running kernel is not an Ubuntu kernel
UpgradeStatus: Upgraded to focal on 2022-09-22 (1 days ago)
UserGroups: N/A
_MarkForUpload: True

Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote : Missing required logs.

This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:

apport-collect 1990700

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

Changed in linux (Ubuntu):
status: New → Incomplete
Revision history for this message
Jan Cernohorsky (jan-cernohorsky) wrote : ProcCpuinfoMinimal.txt

apport information

tags: added: apport-collected focal
description: updated
Revision history for this message
You-Sheng Yang (vicamo) wrote :

It was reported internally that following patch series fixed this issue:

  87dae9e70bf7 net: wwan: t7xx: Enable devlink based fw flashing and coredump collection
  140424d90165 net: wwan: t7xx: PCIe reset rescan
  007f26f0d68e net: wwan: t7xx: Infrastructure for early port configuration
  d20ef656f994 net: wwan: t7xx: Add AP CLDMA

However, they were then reverted in netdev-next in commit bf294c3feafe ("Revert "Merge branch 'wwan-t7xx-fw-flashing-and-coredump-support'""), so we're still waiting for the updates from chip vendor.

AceLan Kao (acelankao)
tags: added: oem-priority originate-from-1991204 somerville
Revision history for this message
Muralidharan (sethurmu) wrote :

Hi Vicamo,

We wanted to request you to take this attached patch in the email and let us know if this patch helps in this suspend resume issue.

diff -Naur t7xx/t7xx_pci.c t7xx_new/t7xx_pci.c
--- t7xx/t7xx_pci.c 2022-06-27 11:56:21.240049223 +0530
+++ t7xx_new/t7xx_pci.c 2022-06-27 19:20:19.120801177 +0530
@@ -308,13 +308,6 @@
   goto abort_suspend;
  }

- ret = t7xx_send_pm_request(t7xx_dev, H2D_CH_SUSPEND_REQ_AP);
- if (ret) {
- t7xx_send_pm_request(t7xx_dev, H2D_CH_RESUME_REQ);
- dev_err(&pdev->dev, "[PM] SAP suspend error: %d\n", ret);
- goto abort_suspend;
- }
-
  list_for_each_entry(entity, &t7xx_dev->md_pm_entities, entity) {
   if (entity->suspend_late)
    entity->suspend_late(t7xx_dev, entity->entity_param);

Thanks and Best Regards,
Murali

Revision history for this message
Lorenzo J. Lucchini (ljl) wrote :

Just a FYI: I reported this bug as well, concerning a closely related Fibocom modem on an Asus Expertbook laptop to Fedora at https://bugzilla.redhat.com/show_bug.cgi?id=2131366

I have not as yet been able to try the patch because I've never built a kernel on Fedora and currently I'm stuck. In other words I'm an idiot. I'll let you know if I figure it out, but meanwhile I thought it just might be useful to know there is another bug report on this.

Revision history for this message
You-Sheng Yang (vicamo) wrote :
description: updated
description: updated
You-Sheng Yang (vicamo)
Changed in linux-oem-6.0 (Ubuntu Jammy):
status: New → In Progress
importance: Undecided → High
assignee: nobody → You-Sheng Yang (vicamo)
Changed in linux-oem-6.0 (Ubuntu Kinetic):
status: New → Invalid
Changed in linux-oem-6.0 (Ubuntu Lunar):
status: New → Invalid
Changed in linux (Ubuntu Lunar):
status: Incomplete → In Progress
importance: Undecided → High
assignee: nobody → You-Sheng Yang (vicamo)
Changed in linux (Ubuntu Jammy):
status: New → Invalid
Changed in linux (Ubuntu Kinetic):
status: New → In Progress
importance: Undecided → High
assignee: nobody → You-Sheng Yang (vicamo)
Revision history for this message
Muralidharan (sethurmu) wrote :

Hi Vicamo,

We had a detailed discussion on this.
We would suggest to use the patch with below commit id
d20ef656f994 net: wwan: t7xx: Add AP CLDMA
instead of the earlier shared workaround for resolution of the suspend issue.

This patch can be integrated without dependency with any other patch and
this would fix the suspend resume issue.

Please do not take the other three patches.
This patch would not cause any other side effect.

Thanks and Best Regards,
Murali

Revision history for this message
Graham Jenkins (grahamjenkins) wrote :

This affects me as well, same exact symptoms, but I'm in the same boat at Lorenzo 4 comments above.

Pardon my inexperience in kernel module building, but if this is relevant with my Fedora 36 install, I would be willing to build and test this, however I would need a pointer at a wiki/docs on where to obtain source and how to activate.

Specifications:
Levovo ThinkPad P1 Gen 5 with optional Fibocom FM350-GL 5G SUB6 Modem
Fedora 36: Relatively fresh install, though I have been messing with the sleep options trying to get it to stay suspended
Gnome Wayland, but tested with KDE Plasma X11 and the problem is identical
Linux 6.0.5-200.fc36.x86_64

Some excepts from journalctl:
kernel: mtk_t7xx 0000:08:00.0: [PM] SAP suspend error: -110
kernel: mtk_t7xx 0000:08:00.0: PM: pci_pm_suspend(): t7xx_pci_pm_suspend+0x0/0x20 [mtk_t7xx] returns -110
kernel: mtk_t7xx 0000:08:00.0: PM: dpm_run_callback(): pci_pm_suspend+0x0/0x160 returns -110
kernel: mtk_t7xx 0000:08:00.0: PM: failed to suspend async: error -110
kernel: PM: Some devices failed to suspend, or early wake event detected

lspci for device:
08:00.0 Wireless controller [0d40]: MEDIATEK Corp. Device 4d75 (rev 01)
  Subsystem: Device 1cf8:3502
  Flags: bus master, fast devsel, latency 0, IRQ 16, IOMMU group 19
  Memory at 625c800000 (64-bit, prefetchable) [size=32K]
  Memory at b4800000 (64-bit, non-prefetchable) [size=8M]
  Memory at 625c000000 (64-bit, prefetchable) [size=8M]
  Capabilities: [80] Express Endpoint, MSI 00
  Capabilities: [d0] MSI-X: Enable+ Count=34 Masked-
  Capabilities: [e0] MSI: Enable- Count=1/32 Maskable+ 64bit+
  Capabilities: [f8] Power Management version 3
  Capabilities: [100] Vendor Specific Information: ID=1556 Rev=1 Len=008 <?>
  Capabilities: [108] Latency Tolerance Reporting
  Capabilities: [110] L1 PM Substates
  Capabilities: [200] Advanced Error Reporting
  Capabilities: [300] Secondary PCI Express
  Kernel driver in use: mtk_t7xx
  Kernel modules: mtk_t7xx

Ping me if I can help, thank you!

Timo Aaltonen (tjaalton)
Changed in linux-oem-6.0 (Ubuntu Jammy):
status: In Progress → Fix Committed
Changed in linux (Ubuntu Kinetic):
status: In Progress → Fix Committed
Timo Aaltonen (tjaalton)
tags: added: verification-needed-jammy
Revision history for this message
You-Sheng Yang (vicamo) wrote :

verified linux-oem-6.0/jammy version 6.0.0-1008.8.

tags: added: verification-done-jammy
removed: verification-needed-jammy
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote :

This bug is awaiting verification that the linux/5.19.0-27.28 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-kinetic' to 'verification-done-kinetic'. If the problem still exists, change the tag 'verification-needed-kinetic' to 'verification-failed-kinetic'.

If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you!

tags: added: kernel-spammed-kinetic-linux verification-needed-kinetic
Revision history for this message
Launchpad Janitor (janitor) wrote :
Download full text (48.0 KiB)

This bug was fixed in the package linux-oem-6.0 - 6.0.0-1008.8

---------------
linux-oem-6.0 (6.0.0-1008.8) jammy; urgency=medium

  * jammy/linux-oem-6.0: 6.0.0-1008.8 -proposed tracker (LP: #1996347)

  * Packaging resync (LP: #1786013)
    - debian/dkms-versions -- update from kernel-versions (main/2022.11.14)

  * Fix a race condition with AMD PMF and Thinkpad-ACPI (LP: #1993242)
    - platform/x86/amd/pmf: Fix undefined reference to platform_profile
    - platform/x86/amd/pmf: Fix clang unused variable warning
    - platform/x86/amd/pmf: install notify handler after acpi init

  * Screen freeze after resuming from suspend (nvme0: I/O timeout)
    (LP: #1996048)
    - SAUCE: PCI: vmd: Disable MSI remapping after suspend

  * Fibocom WWAN FM350-GL suspend error (notebook not suspend) (LP: #1990700)
    - net: wwan: t7xx: Add AP CLDMA

  * Add some ACPI device IDs for Intel HID device (LP: #1995453)
    - platform/x86/intel/hid: Add some ACPI device IDs

  * amd_sfh modprobe fails when no sensor reported from AMD MP2 (LP: #1993240)
    - HID: amd_sfh: Change dev_err to dev_dbg for additional debug info

  * Jammy update: v6.0.9 upstream stable release (LP: #1996785)
    - drm/i915/gvt: Add missing vfio_unregister_group_dev() call
    - m68k: Rework BI_VIRT_RNG_SEED as BI_RNG_SEED
    - KVM: debugfs: Return retval of simple_attr_open() if it fails
    - drm/i915: Allow more varied alternate fixed modes for panels
    - drm/i915: Simplify intel_panel_add_edid_alt_fixed_modes()
    - drm/i915/sdvo: Grab mode_config.mutex during LVDS init to avoid WARNs
    - drm/amd/display: Acquire FCLK DPM levels on DCN32
    - drm/amd/display: Limit dcn32 to 1950Mhz display clock
    - drm/amd/display: Set memclk levels to be at least 1 for dcn32
    - drm/amdkfd: handle CPU fault on COW mapping
    - drm/amdkfd: Fix NULL pointer dereference in svm_migrate_to_ram()
    - cxl/region: Recycle region ids
    - HID: wacom: Fix logic used for 3rd barrel switch emulation
    - hwspinlock: qcom: correct MMIO max register for newer SoCs
    - phy: stm32: fix an error code in probe
    - wifi: cfg80211: silence a sparse RCU warning
    - wifi: cfg80211: fix memory leak in query_regdb_file()
    - soundwire: qcom: reinit broadcast completion
    - soundwire: qcom: check for outanding writes before doing a read
    - ALSA: arm: pxa: pxa2xx-ac97-lib: fix return value check of
      platform_get_irq()
    - spi: mediatek: Fix package division error
    - bpf, verifier: Fix memory leak in array reallocation for stack state
    - bpf, sockmap: Fix the sk->sk_forward_alloc warning of sk_stream_kill_queues
    - wifi: mac80211: fix general-protection-fault in ieee80211_subif_start_xmit()
    - wifi: mac80211: Set TWT Information Frame Disabled bit as 1
    - bpftool: Fix NULL pointer dereference when pin {PROG, MAP, LINK} without
      FILE
    - HID: hyperv: fix possible memory leak in mousevsc_probe()
    - drm/vc4: hdmi: Fix HSM clock too low on Pi4
    - bpf, sock_map: Move cancel_work_sync() out of sock lock
    - PCI: hv: Fix the definition of vector in hv_compose_msi_msg()
    - bpf: Add helper macro bpf_for_each_reg_in_vstate
    - bpf: Fix wrong reg type conversi...

Changed in linux-oem-6.0 (Ubuntu Jammy):
status: Fix Committed → Fix Released
Revision history for this message
Launchpad Janitor (janitor) wrote :
Download full text (100.4 KiB)

This bug was fixed in the package linux - 5.19.0-28.29

---------------
linux (5.19.0-28.29) kinetic; urgency=medium

  * kinetic/linux: 5.19.0-28.29 -proposed tracker (LP: #1999746)

  * mm:vma05 in ubuntu_ltp fails with '[vdso] bug not patched' on kinetic/linux
    5.19.0-27.28 (LP: #1999094)
    - fix coredump breakage

linux (5.19.0-27.28) kinetic; urgency=medium

  * kinetic/linux: 5.19.0-27.28 -proposed tracker (LP: #1997794)

  * Packaging resync (LP: #1786013)
    - debian/dkms-versions -- update from kernel-versions (main/2022.11.14)

  * selftests/.../nat6to4 breaks the selftests build (LP: #1996536)
    - [Config] Disable selftests/net/bpf/nat6to4

  * Expose built-in trusted and revoked certificates (LP: #1996892)
    - [Packaging] Expose built-in trusted and revoked certificates

  * support for same series backports versioning numbers (LP: #1993563)
    - [Packaging] sameport -- add support for sameport versioning

  * Add cs35l41 firmware loading support (LP: #1995957)
    - ASoC: cs35l41: Move cs35l41 exit hibernate function into shared code
    - ASoC: cs35l41: Add common cs35l41 enter hibernate function
    - ASoC: cs35l41: Do not print error when waking from hibernation
    - ALSA: hda: cs35l41: Don't dereference fwnode handle
    - ALSA: hda: cs35l41: Allow compilation test on non-ACPI configurations
    - ALSA: hda: cs35l41: Drop wrong use of ACPI_PTR()
    - ALSA: hda: cs35l41: Consolidate selections under SND_HDA_SCODEC_CS35L41
    - ALSA: hda: hda_cs_dsp_ctl: Add Library to support CS_DSP ALSA controls
    - ALSA: hda: hda_cs_dsp_ctl: Add apis to write the controls directly
    - ALSA: hda: cs35l41: Save codec object inside component struct
    - ALSA: hda: cs35l41: Add initial DSP support and firmware loading
    - ALSA: hda: cs35l41: Save Subsystem ID inside CS35L41 Driver
    - ALSA: hda: cs35l41: Support reading subsystem id from ACPI
    - ALSA: hda: cs35l41: Support multiple load paths for firmware
    - ALSA: hda: cs35l41: Support Speaker ID for laptops
    - ALSA: hda: cs35l41: Support Hibernation during Suspend
    - ALSA: hda: cs35l41: Read Speaker Calibration data from UEFI variables
    - ALSA: hda: hda_cs_dsp_ctl: Add fw id strings
    - ALSA: hda: cs35l41: Add defaulted values into dsp bypass config sequence
    - ALSA: hda: cs35l41: Support Firmware switching and reloading
    - ALSA: hda: cs35l41: Add module parameter to control firmware load
    - Revert "ALSA: hda: cs35l41: Allow compilation test on non-ACPI
      configurations"
    - ALSA: hda/realtek: More robust component matching for CS35L41
    - [Config] updateconfigs for SND_HDA_CS_DSP_CONTROLS

  * Fibocom WWAN FM350-GL suspend error (notebook not suspend) (LP: #1990700)
    - net: wwan: t7xx: Add AP CLDMA

  * Screen cannot turn on after screen off with Matrox G200eW3 [102b:0536]
    (LP: #1995573)
    - drm/mgag200: Optimize damage clips
    - drm/mgag200: Add FB_DAMAGE_CLIPS support
    - drm/mgag200: Enable atomic gamma lut update

  * TEE Support for CCP driver (LP: #1991608)
    - crypto: ccp: Add support for TEE for PCI ID 0x14CA

  * AMD Cezanne takes 5 minutes to wake up from suspend (LP: #1993715)
    - platform/x86/amd: pmc: Read...

Changed in linux (Ubuntu Kinetic):
status: Fix Committed → Fix Released
Revision history for this message
You-Sheng Yang (vicamo) wrote :

linux/lunar fixed since Ubuntu-6.1.0-1.1 via Ubuntu-unstable-6.1.0-8.8.

Changed in linux (Ubuntu Lunar):
status: In Progress → Fix Released
Changed in hwe-next:
status: New → Fix Released
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote :

This bug is awaiting verification that the linux-ibm/5.19.0-1015.16 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-kinetic' to 'verification-done-kinetic'. If the problem still exists, change the tag 'verification-needed-kinetic' to 'verification-failed-kinetic'.

If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you!

tags: added: kernel-spammed-kinetic-linux-ibm
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote :

This bug is awaiting verification that the linux-aws/5.19.0-1018.19 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-kinetic' to 'verification-done-kinetic'. If the problem still exists, change the tag 'verification-needed-kinetic' to 'verification-failed-kinetic'.

If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you!

tags: added: kernel-spammed-kinetic-linux-aws
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote :

This bug is awaiting verification that the linux-azure/5.19.0-1017.18 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-kinetic' to 'verification-done-kinetic'. If the problem still exists, change the tag 'verification-needed-kinetic' to 'verification-failed-kinetic'.

If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you!

tags: added: kernel-spammed-kinetic-linux-azure
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote :

This bug is awaiting verification that the linux-aws-5.19/5.19.0-1019.20~22.04.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy' to 'verification-done-jammy'. If the problem still exists, change the tag 'verification-needed-jammy' to 'verification-failed-jammy'.

If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you!

tags: added: kernel-spammed-jammy-linux-aws-5.19 verification-needed-jammy
removed: verification-done-jammy
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote :

This bug is awaiting verification that the linux-lowlatency-hwe-5.19/5.19.0-1017.18~22.04.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy' to 'verification-done-jammy'. If the problem still exists, change the tag 'verification-needed-jammy' to 'verification-failed-jammy'.

If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you!

tags: added: kernel-spammed-jammy-linux-lowlatency-hwe-5.19
Revision history for this message
Markus Kohli (ophion-ch) wrote (last edit ):

Regarding https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1990700/comments/13:
I'm still seeing the same issue on Ubuntu 22.10 with mainline kernel 6.1.8 and 6.1.9.
Did this somehow get kicked again, or am I misinterpreting the kernel-versions?

Dmesg states:
[ 93.276679] mtk_t7xx 0000:57:00.0: [PM] SAP suspend error: -110
[ 93.276736] mtk_t7xx 0000:57:00.0: PM: pci_pm_suspend(): t7xx_pci_pm_suspend+0x0/0x20 [mtk_t7xx] returns -110
[ 93.276800] mtk_t7xx 0000:57:00.0: PM: dpm_run_callback(): pci_pm_suspend+0x0/0x1b0 returns -110
[ 93.276832] mtk_t7xx 0000:57:00.0: PM: failed to suspend async: error -110
[ 93.277194] PM: Some devices failed to suspend, or early wake event detected

Kernel:
Linux zephyr 6.1.9-060109-generic #202302010835 SMP PREEMPT_DYNAMIC Wed Feb 1 08:41:31 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

Revision history for this message
Jan Cernohorsky (jan-cernohorsky) wrote :

Hi,
after testing fixed kernels (v6.xx+) I have still same problem - notebook cannot go to sleep/suspend mode.
Error mtk_t7xx 0000:58:00.0: PM: failed to suspend async: error -110 is gone. When I suspend my notebook, it will wake up in a moment.
It must be the modem because when I replace it with another one everything works fine.
Can I provide any additional information to possibly resolve this issue?

Thank you.
With best regards,
John

Revision history for this message
Jan Cernohorsky (jan-cernohorsky) wrote :

Hi,
another peculiarity is that the modem pretends not to support 5G networks, although according to the manufacturer it should - supported modes:

  --------------------------------
  General | path: /org/freedesktop/ModemManager1/Modem/0
           | device id: 82abc72cff5381e11a96d650c8cfdcf1ae4d838e
  --------------------------------
  Hardware | manufacturer: generic
           | model: MBIM [14C3:4D75]
           | firmware revision: 81600.0000.00.29.18.01_VF
           | C01
           | h/w revision: V1.0.6
           | supported: gsm-umts, lte
           | current: gsm-umts, lte
           | equipment id: 862146050381233
  --------------------------------
  System | device: /sys/devices/pci0000:00/0000:00:1c.5/0000:58:00.0
           | drivers: mtk_t7xx
           | plugin: generic
           | primary port: wwan0mbim0
           | ports: wwan0 (net), wwan0at0 (at), wwan0mbim0 (mbim)
  --------------------------------
  Status | unlock retries: sim-pin2 (3)
           | state: registered
           | power state: on
           | access tech: lte
           | signal quality: 64% (recent)
  --------------------------------
  Modes | supported: allowed: 3g, 4g; preferred: none
           | current: allowed: 3g, 4g; preferred: none
  --------------------------------
  IP | supported: ipv4, ipv6, ipv4v6
  --------------------------------
  3GPP | imei: ---
           | enabled locks: fixed-dialing
           | operator id: 23003
           | operator name: Vodafone CZ
           | registration: home
  --------------------------------
  3GPP EPS | ue mode of operation: csps-2
           | initial bearer path: /org/freedesktop/ModemManager1/Bearer/0
  --------------------------------
  SIM | primary sim path: /org/freedesktop/ModemManager1/SIM/0
           | sim slot paths: slot 1: /org/freedesktop/ModemManager1/SIM/0 (active)
           | slot 2: /org/freedesktop/ModemManager1/SIM/1

Revision history for this message
Markus Kohli (ophion-ch) wrote :

About the 5G support:
nm-applet reports LTE, but it does work on 5G.
I just got 400+ Mbps yesterday when testing, which obviously is not LTE.
Might just be a naming issue there.
The sleep issue persists however, latest tests with 6.1.12 are the same as before.

Revision history for this message
Graham Jenkins (grahamjenkins) wrote :

Update: I recently switched back from Fedora (36?) that was successfully suspending with a manually installed kernel update (preventing other auto updates).
I am currently running Ubuntu 22.04 with a fresh install, suspend is failing.
Kernels tested:
5.1.17 (default) - Doesn't display modem
6.3.3 (latest available mainline) - Grub output displayed "mtk_t7xx .... : Port AT is not opened, drop packets" and hung there, not booting
6.1.0 Briefly displayed this error but booted. Displays modem in network manager, offers 3G,4G,5G in settings.
After a clean boot and attempted suspend I have the following output:

journalctl | grep t7xx:

May 19 11:12:16 host kernel: mtk_t7xx 0000:08:00.0: enabling device (0000 -> 0002)
May 19 11:12:16 hostname kernel: mtk_t7xx 0000:08:00.0: Port AT is not opened, drop packets
May 19 11:12:56 hostname kernel: mtk_t7xx 0000:08:00.0: [PM] SAP suspend error: -110
May 19 11:12:56 hostname kernel: mtk_t7xx 0000:08:00.0: PM: pci_pm_suspend(): t7xx_pci_pm_suspend+0x0/0x20 [mtk_t7xx] returns -110
May 19 11:12:56 hostname kernel: mtk_t7xx 0000:08:00.0: PM: dpm_run_callback(): pci_pm_suspend+0x0/0x1b0 returns -110
May 19 11:12:56 hostname kernel: mtk_t7xx 0000:08:00.0: PM: failed to suspend async: error -110
May 19 11:12:59 hostname kernel: mtk_t7xx 0000:08:00.0: [PM] SAP suspend error: -110
May 19 11:12:59 hostname kernel: mtk_t7xx 0000:08:00.0: PM: pci_pm_suspend(): t7xx_pci_pm_suspend+0x0/0x20 [mtk_t7xx] returns -110
May 19 11:12:59 hostname kernel: mtk_t7xx 0000:08:00.0: PM: dpm_run_callback(): pci_pm_suspend+0x0/0x1b0 returns -110
May 19 11:12:59 hostname kernel: mtk_t7xx 0000:08:00.0: PM: failed to suspend async: error -110

Are there specific kernel versions that have the fix (eg there was a regression) or is there other information/logs I can provide to help?

Revision history for this message
Graham Jenkins (grahamjenkins) wrote :

Correction: The default kernel was 5.17.0

I have additionally tested 5.19.0 and 6.0.0 (both mentioned as being fixed above)
All throw the same errors with Linux S3 sleep mode as well as default Windows/Linux set in bios.

Revision history for this message
Kajanos (kajanos) wrote :
Download full text (3.3 KiB)

Kernel - 6.4.0-060400-generic
Lenovo T14s Gen3 AMD

  -----------------------------------
  General | path: /org/freedesktop/ModemManager1/Modem/0
            | device id: 6ee2f6acfa74a3d63c3e99f5cc7ccca6d2617199
  -----------------------------------
  Hardware | manufacturer: generic
            | model: MBIM [14C3:4D75]
            | firmware revision: 81600.0000.00.29.21.24_DT
            | D64
            | h/w revision: V1.0.6
            | supported: gsm-umts, lte, 5gnr
            | current: gsm-umts, lte, 5gnr
            | equipment id: 016177000091627
  -----------------------------------
  System | device: /sys/devices/pci0000:00/0000:00:02.3/0000:02:00.0
            | drivers: mtk_t7xx
            | plugin: generic
            | primary port: wwan0mbim0
            | ports: wwan0 (net), wwan0at0 (at), wwan0mbim0 (mbim)
  -----------------------------------
  Status | lock: sim-pin2
            | unlock retries: sim-pin2 (3)
            | state: disabled
            | power state: low
  -----------------------------------
  Modes | supported: allowed: 3g; preferred: none
            | allowed: 4g; preferred: none
            | allowed: 3g, 4g; preferred: none
            | allowed: 5g; preferred: none
            | allowed: 3g, 5g; preferred: none
            | allowed: 4g, 5g; preferred: none
            | allowed: 3g, 4g, 5g; preferred: none
            | current: allowed: any; preferred: none
  -----------------------------------
  IP | supported: ipv4, ipv6, ipv4v6
  -----------------------------------
  3GPP | imei: 016177000091627
            | enabled locks: fixed-dialing
            | packet service state: detached
  -----------------------------------
  3GPP EPS | ue mode of operation: csps-2
            | initial bearer ip type: ipv4v6
  -----------------------------------
  3GPP 5GNR | mico mode: disabled
  -----------------------------------
  SIM | primary sim path: /org/freedesktop/ModemManager1/SIM/0
            | sim slot paths: slot 1: none
            | slot 2: /org/freedesktop/ModemManager1/SIM/0 (active)

[ 0.836904] mtk_t7xx 0000:02:00.0: enabling device (0000 -> 0002)
[ 11.102115] mtk_t7xx 0000:02:00.0: Port AT is not opened, drop packets
[ 13.016761] mtk_t7xx 0000:02:00.0: Port AT is not opened, drop packets
[ 42.071283] mtk_t7xx 0000:02:00.0: [PM] SAP suspend error: -110
[ 42.071329] mtk_t7xx 0000:02:00.0: can't suspend (t7xx_pci_pm_runtime_suspend [mtk_t7xx] returned -110)
[ 68.432657] mtk_t7xx 0000:02:00.0: Failed to send skb: -22
[ 68.432671] mtk_t7xx 0000:02:00.0: Write error on MBIM port, -22
[ 78.442101] mtk_t7xx 0000:02:00.0: Failed ...

Read more...

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.