[Touch-packages] [Bug 1898421] Re: Suspend - takes 30 seconds to fully suspend
Initial report used an old desktop, below is the output from a Renoir laptop. [ 1134.925114] PM: suspend entry (s2idle) [ 1134.936220] Filesystems sync: 0.011 seconds [ 1134.936483] Freezing user space processes ... (elapsed 0.002 seconds) done. [ 1134.938761] OOM killer disabled. [ 1134.938762] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done. [ 1134.940031] printk: Suspending console(s) (use no_console_suspend to debug) [ 1134.962659] sd 1:0:0:0: [sda] Synchronizing SCSI cache [ 1134.963415] sd 1:0:0:0: [sda] Stopping disk [ 1135.266599] [drm] free PSP TMR buffer [ 1135.313789] ACPI: EC: interrupt blocked [ 1135.331004] amdgpu :02:00.0: refused to change power state from D0 to D3hot [ 1135.331007] xhci_hcd :02:00.4: refused to change power state from D0 to D3hot [ 1150.496373] ACPI: EC: interrupt unblocked [ 1150.537397] sd 1:0:0:0: [sda] Starting disk [ 1150.556055] [drm] PCIE GART of 1024M enabled (table at 0x00F40090). [ 1150.556092] [drm] PSP is resuming... [ 1150.575984] [drm] reserve 0x40 from 0xf41fc0 for PSP TMR [ 1150.848719] ata1: SATA link down (SStatus 0 SControl 300) [ 1150.899613] amdgpu: SMU is resuming... [ 1150.899660] amdgpu: dpm has been disabled [ 1150.899676] amdgpu: SMU is resumed successfully! [ 1151.011434] ata2: SATA link up 6.0 Gbps (SStatus 133 SControl 300) [ 1151.016213] ata2.00: configured for UDMA/133 [ 1151.144093] [drm] kiq ring mec 2 pipe 1 q 0 [ 1151.152943] [drm] DMUB hardware initialized: version=0x0001 [ 1151.282435] [drm] Failed to add display topology, DTM TA is not initialized. [ 1151.309163] [drm] VCN decode and encode initialized successfully(under DPG Mode). [ 1151.309272] [drm] JPEG decode initialized successfully. [ 1151.309578] amdgpu :02:00.0: amdgpu: ring gfx uses VM inv eng 0 on hub 0 [ 1151.309581] amdgpu :02:00.0: amdgpu: ring comp_1.0.0 uses VM inv eng 1 on hub 0 [ 1151.309582] amdgpu :02:00.0: amdgpu: ring comp_1.1.0 uses VM inv eng 4 on hub 0 [ 1151.309584] amdgpu :02:00.0: amdgpu: ring comp_1.2.0 uses VM inv eng 5 on hub 0 [ 1151.309586] amdgpu :02:00.0: amdgpu: ring comp_1.3.0 uses VM inv eng 6 on hub 0 [ 1151.309588] amdgpu :02:00.0: amdgpu: ring comp_1.0.1 uses VM inv eng 7 on hub 0 [ 1151.309589] amdgpu :02:00.0: amdgpu: ring comp_1.1.1 uses VM inv eng 8 on hub 0 [ 1151.309591] amdgpu :02:00.0: amdgpu: ring comp_1.2.1 uses VM inv eng 9 on hub 0 [ 1151.309593] amdgpu :02:00.0: amdgpu: ring comp_1.3.1 uses VM inv eng 10 on hub 0 [ 1151.309595] amdgpu :02:00.0: amdgpu: ring kiq_2.1.0 uses VM inv eng 11 on hub 0 [ 1151.309596] amdgpu :02:00.0: amdgpu: ring sdma0 uses VM inv eng 0 on hub 1 [ 1151.309598] amdgpu :02:00.0: amdgpu: ring vcn_dec uses VM inv eng 1 on hub 1 [ 1151.309600] amdgpu :02:00.0: amdgpu: ring vcn_enc0 uses VM inv eng 4 on hub 1 [ 1151.309601] amdgpu :02:00.0: amdgpu: ring vcn_enc1 uses VM inv eng 5 on hub 1 [ 1151.309603] amdgpu :02:00.0: amdgpu: ring jpeg_dec uses VM inv eng 6 on hub 1 [ 1151.318752] OOM killer enabled. [ 1151.318754] Restarting tasks ... done. [ 1151.343199] PM: suspend exit [ 1158.309787] [drm] Failed to add display topology, DTM TA is not initialized. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1898421 Title: Suspend - takes 30 seconds to fully suspend Status in systemd package in Ubuntu: New Bug description: Using `systemctl suspend` or suspending through the power menu takes 30 seconds for the system to fully suspend. Expected: The system suspends in under 2 seconds (e.g. check Arch Linux) Actual: The system takes 30 seconds to suspend (31.44 seconds using a stopwatch) Description: Ubuntu 20.04.1 LTS Release: 20.04 Codename: focal DMESG: [ 8521.093270] PM: suspend entry (deep) [ 8521.104938] Filesystems sync: 0.011 seconds [ 8521.182123] Freezing user space processes ... (elapsed 0.004 seconds) done. [ 8521.187004] OOM killer disabled. [ 8521.187005] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done. [ 8521.188754] printk: Suspending console(s) (use no_console_suspend to debug) [ 8521.219072] sd 1:0:0:0: [sda] Synchronizing SCSI cache [ 8521.219621] sd 1:0:0:0: [sda] Stopping disk [ 8521.958776] ACPI: Preparing to enter system sleep state S3 [ 8521.960793] PM: Saving platform NVS memory [ 8521.961025] Disabling non-boot CPUs ... [ 8521.961558] IRQ 26: no longer affine to CPU1 [ 8521.962593] smpboot: CPU 1 is now offline [ 8521.964649] IRQ 18: no longer affine to CPU2 [ 8521.965669] smpboot: CPU 2 is now offline [ 8521.967970] IRQ 27: no longer affine to CPU3 [ 8521.968991] smpboot: CPU 3 is now offline [ 8521.970958] ACPI: Low-level resume complete [ 8521.970958] PM: Restoring platform NVS memory [ 8521.976827] Enabling non-boot CPUs ... [ 8521.976893] x86:
[Touch-packages] [Bug 1898421] [NEW] Suspend - takes 30 seconds to fully suspend
Public bug reported: Using `systemctl suspend` or suspending through the power menu takes 30 seconds for the system to fully suspend. Expected: The system suspends in under 2 seconds (e.g. check Arch Linux) Actual: The system takes 30 seconds to suspend (31.44 seconds using a stopwatch) Description:Ubuntu 20.04.1 LTS Release:20.04 Codename: focal DMESG: [ 8521.093270] PM: suspend entry (deep) [ 8521.104938] Filesystems sync: 0.011 seconds [ 8521.182123] Freezing user space processes ... (elapsed 0.004 seconds) done. [ 8521.187004] OOM killer disabled. [ 8521.187005] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done. [ 8521.188754] printk: Suspending console(s) (use no_console_suspend to debug) [ 8521.219072] sd 1:0:0:0: [sda] Synchronizing SCSI cache [ 8521.219621] sd 1:0:0:0: [sda] Stopping disk [ 8521.958776] ACPI: Preparing to enter system sleep state S3 [ 8521.960793] PM: Saving platform NVS memory [ 8521.961025] Disabling non-boot CPUs ... [ 8521.961558] IRQ 26: no longer affine to CPU1 [ 8521.962593] smpboot: CPU 1 is now offline [ 8521.964649] IRQ 18: no longer affine to CPU2 [ 8521.965669] smpboot: CPU 2 is now offline [ 8521.967970] IRQ 27: no longer affine to CPU3 [ 8521.968991] smpboot: CPU 3 is now offline [ 8521.970958] ACPI: Low-level resume complete [ 8521.970958] PM: Restoring platform NVS memory [ 8521.976827] Enabling non-boot CPUs ... [ 8521.976893] x86: Booting SMP configuration: [ 8521.976894] smpboot: Booting Node 0 Processor 1 APIC 0x2 [ 8521.983510] CPU1 is up [ 8521.983545] smpboot: Booting Node 0 Processor 2 APIC 0x3 [ 8521.990199] CPU2 is up [ 8521.990234] smpboot: Booting Node 0 Processor 3 APIC 0x1 [ 8521.996937] CPU3 is up [ 8521.999566] ACPI: Waking up from system sleep state S3 [ 8522.039068] usb usb3: root hub lost power or was reset [ 8522.039085] usb usb4: root hub lost power or was reset [ 8522.039093] usb usb5: root hub lost power or was reset [ 8522.039149] usb usb6: root hub lost power or was reset [ 8522.039172] usb usb7: root hub lost power or was reset [ 8522.039207] usb usb8: root hub lost power or was reset [ 8522.046933] [drm] enabling PCIE gen 2 link speeds, disable with radeon.pcie_gen2=0 [ 8522.053105] [drm] PCIE GART of 1024M enabled (table at 0x00162000). [ 8522.053201] radeon :01:00.0: WB enabled [ 8522.053204] radeon :01:00.0: fence driver on ring 0 use gpu addr 0x4c00 and cpu addr 0x2d5e699f [ 8522.053207] radeon :01:00.0: fence driver on ring 3 use gpu addr 0x4c0c and cpu addr 0x6b3686a1 [ 8522.053999] radeon :01:00.0: fence driver on ring 5 use gpu addr 0x00072118 and cpu addr 0x556b4497 [ 8522.054407] sd 1:0:0:0: [sda] Starting disk [ 8522.070310] [drm] ring test on 0 succeeded in 2 usecs [ 8522.070320] [drm] ring test on 3 succeeded in 6 usecs [ 8522.139382] mt7601u 1-5:1.0: Error: MCU response pre-completed! [ 8522.167009] mt7601u 1-5:1.0: EEPROM ver:0c fae:00 [ 8522.246061] [drm] ring test on 5 succeeded in 2 usecs [ 8522.246069] [drm] UVD initialized successfully. [ 8522.246206] [drm] ib test on ring 0 succeeded in 0 usecs [ 8522.246333] [drm] ib test on ring 3 succeeded in 0 usecs [ 8522.372750] ata1: SATA link down (SStatus 0 SControl 300) [ 8522.420793] ata4: SATA link down (SStatus 0 SControl 300) [ 8522.420965] ata5: SATA link down (SStatus 0 SControl 300) [ 8522.420984] ata6: SATA link down (SStatus 0 SControl 300) [ 8522.421015] ata3: SATA link down (SStatus 0 SControl 300) [ 8522.534422] usb 4-2: reset low-speed USB device number 3 using uhci_hcd [ 8522.586417] ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 300) [ 8522.589674] ata2.00: configured for UDMA/133 [ 8522.589762] ata2.00: Enabling discard_zeroes_data [ 8522.910492] [drm] ib test on ring 5 succeeded [ 8523.114411] usb 4-1: reset low-speed USB device number 2 using uhci_hcd [ 8523.467722] OOM killer enabled. [ 8523.467723] Restarting tasks ... [ 8523.469565] pci :00:1e.0: PCI bridge to [bus 03] [ 8523.469623] pci :00:1e.0: PCI bridge to [bus 03] [ 8523.469671] pci :00:1e.0: PCI bridge to [bus 03] [ 8523.469723] pci :00:1e.0: PCI bridge to [bus 03] [ 8523.469769] pci :00:1e.0: PCI bridge to [bus 03] [ 8523.469816] pci :00:1e.0: PCI bridge to [bus 03] [ 8523.486043] rfkill: input handler enabled [ 8523.494520] done. [ 8523.496289] PM: suspend exit [ 8523.511552] rfkill: input handler disabled [ 8541.280829] check: Corrupted low memory at de236a5f (c6e8 phys) = 4000 ** Affects: systemd (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1898421 Title: Suspend - takes 30 seconds to fully suspend Status in systemd package in Ubuntu: New Bug description: Using `systemctl suspend` or suspending through the power menu takes 30 seconds
[Touch-packages] [Bug 1898420] [NEW] ModemManager - USB Tethering not working
Public bug reported: When ModemManager.service is running (the default for a long time) - usb tethering is not working on Ubuntu. The bug is 100% reproducible for a few years. It might be working for few seconds but very quickly stops. I need to stop the service with systemctl and reconnect a device that provides usb tethering for the connection to work. Expected: USB tethering works out of the box Actual: USB tethering is not working while ModemManager.service is running Distributor ID: Ubuntu Description:Ubuntu 20.04.1 LTS Release:20.04 Codename: focal ** Affects: modemmanager (Ubuntu) Importance: Undecided Status: New ** Description changed: When ModemManager.service is running (the default for a long time) - usb tethering is not working on Ubuntu. The bug is 100% reproducible for a few years. It might be working for few seconds but very quickly stops. I need to stop the service with systemctl and reconnect a device that provides usb tethering for the connection to work. + + Expected: + USB tethering works out of the box + + Actual: + USB tethering is not working while ModemManager.service is running + + Distributor ID: Ubuntu + Description: Ubuntu 20.04.1 LTS + Release: 20.04 + Codename: focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/1898420 Title: ModemManager - USB Tethering not working Status in modemmanager package in Ubuntu: New Bug description: When ModemManager.service is running (the default for a long time) - usb tethering is not working on Ubuntu. The bug is 100% reproducible for a few years. It might be working for few seconds but very quickly stops. I need to stop the service with systemctl and reconnect a device that provides usb tethering for the connection to work. Expected: USB tethering works out of the box Actual: USB tethering is not working while ModemManager.service is running Distributor ID: Ubuntu Description: Ubuntu 20.04.1 LTS Release: 20.04 Codename: focal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1898420/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
