linux issueshttps://source.puri.sm/Librem5/linux/-/issues2023-05-04T21:34:18Zhttps://source.puri.sm/Librem5/linux/-/issues/478Sparklan card does not support SAE (WPA3, OWE)2023-05-04T21:34:18ZSebastian KrzyszkowiakSparklan card does not support SAE (WPA3, OWE)Trying to connect to an AP using SAE (either WPA3 or OWE) does not work on Sparklan cards. User has to switch to WPA2 in order to connect.Trying to connect to an AP using SAE (either WPA3 or OWE) does not work on Sparklan cards. User has to switch to WPA2 in order to connect.https://source.puri.sm/Librem5/linux/-/issues/477After software update, no WiFi adapter found2023-05-02T20:31:56ZM GamboniAfter software update, no WiFi adapter foundMy Wi-Fi adapter has been flaky for a long time (*usually* working, but sometimes disappearing. When that would happen cycling the kill-switch or at worst a reboot would bring it back) but since April 31st it’s not coming up at all. I di...My Wi-Fi adapter has been flaky for a long time (*usually* working, but sometimes disappearing. When that would happen cycling the kill-switch or at worst a reboot would bring it back) but since April 31st it’s not coming up at all. I did a software update a few days before that, so I believe it's stopped working at that point.
There’s no Wi-Fi indicator at the top, opening Wi-Fi settings says “No Wi-Fi adapter found”. I tried flicking the kill switch up and down, rebooting, shutting down and restarting, waiting a couple hours (it used to appear a couple minutes after boot before).
Apparently some people had this issue because their `/boot` was full but `df -h /boot` says 35% used, 281M available which I suppose is plenty.
When I disable the kill switch (i.e. supposedly enable the adapter), the following lines appear in `dmesg -w`:
```
[ 751.655912] mmc1: new high speed SDIO card at address fffd
[ 751.657097] redpine_91x: rsi_probe: ***** 9116 Module *****
[ 751.657879] redpine_91x: redpine_hal_device_init: oper_mode = 5, coex_mode = 2
[ 751.659052] redpine_91x: Received Board Version Number: 10
[ 751.660155] redpine_91x: rsi_load_firmware: Loading file RS9116_NLINK_WLAN_BT_IMAGE.rps
[ 753.054966] redpine_91x: *** Flash is Empty ***
[ 753.054990] redpine_91x: FW Length = 329216 bytes
[ 753.055000] redpine_91x: ================================================
[ 753.055004] redpine_91x: ================ RSI Version Info ==============
[ 753.055009] redpine_91x: ================================================
[ 753.055014] redpine_91x: FW Version : 2.1.0.0
[ 753.055021] redpine_91x: RSI FW Version : 1610.2.1.ab.ffbf
[ 753.055030] redpine_91x: Driver Version : RS9116.NB0.NL.GNU.LNX.OSD.2.0.0.0024
[ 753.055036] redpine_91x: Operating mode : 5 [Wi-Fi STA + BT EDR]
[ 753.055042] redpine_91x: Firmware file : RS9116_NLINK_WLAN_BT_IMAGE.rps
[ 753.055047] redpine_91x: ================================================
[ 753.063343] redpine_91x: Burn Command Pass.. Upgrading the firmware
[ 756.635879] redpine_91x: bl_cmd: Command EOF_REACHED (45) writing failed..
[ 756.635905] redpine_91x: Firmware upgrade failed - attempt RAM load
[ 756.635911] redpine_91x: Ram file magic 0xa55a size 329152
[ 756.637265] redpine_91x: ================================================
[ 756.637274] redpine_91x: ================ RSI Version Info ==============
[ 756.637279] redpine_91x: ================================================
[ 756.637285] redpine_91x: FW Version : 2.1.0.0
[ 756.637292] redpine_91x: RSI FW Version : 1610.2.1.ab.ffbf
[ 756.637300] redpine_91x: Driver Version : RS9116.NB0.NL.GNU.LNX.OSD.2.0.0.0024
[ 756.637306] redpine_91x: Operating mode : 5 [Wi-Fi STA + BT EDR]
[ 756.637313] redpine_91x: Firmware file : RS9116_NLINK_WLAN_BT_IMAGE.rps
[ 756.637318] redpine_91x: ================================================
[ 756.684738] redpine_91x: ***** Firmware Loading successful *****
[ 756.684960] redpine_91x: RAM load successful
[ 756.684967] redpine_91x: ***** Firmware Loading successful *****
```
which I suppose imply the card was found?
I see that firmware file in `/usr/lib/firmware`:
`-rw-r–r-- 1 root root 329216 4 mai 2022 /usr/lib/firmware/RS9116_NLINK_WLAN_BT_IMAGE.rps`
Note that it reports the file is one year old.
However `nmcli device` doesn't find the card:
```
DEVICE TYPE STATE CONNECTION
cdc-wdm0 gsm connected Salt Internet - Postpaid
lxcbr0 bridge connected (externally) lxcbr0
usb0 ethernet unavailable --
lo loopback unmanaged --
```
(There should be a wlan0 somewhere there, right?)
`uname -r`:
`6.2.0-1-librem5`
The WWAN adapter works fine.
What can I try next?https://source.puri.sm/Librem5/linux/-/issues/476modem frequently disappears (ttyUSB1 timed out 10 consecutive times, marking ...2023-05-02T16:53:33ZMatthias Apitzmodem frequently disappears (ttyUSB1 timed out 10 consecutive times, marking modem as invalid)On an uptodate L5 with new modem firmware (but issue existed before already) I face from time to time the modem disappearing; `journalctl`shows:
```
Apr 25 09:08:15 pureos sudo[23493]: purism : TTY=pts/2 ; PWD=/home/purism ; USER=root ...On an uptodate L5 with new modem firmware (but issue existed before already) I face from time to time the modem disappearing; `journalctl`shows:
```
Apr 25 09:08:15 pureos sudo[23493]: purism : TTY=pts/2 ; PWD=/home/purism ; USER=root ; COMMAND=/usr/bin/apt update
Apr 25 09:08:15 pureos sudo[23493]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=1000)
Apr 25 09:09:00 pureos sudo[23493]: pam_unix(sudo:session): session closed for user root
Apr 25 09:09:59 pureos ModemManager[5761]: <warn> [modem4] port ttyUSB1 timed out 8 consecutive times
Apr 25 09:10:04 pureos ModemManager[5761]: <warn> [modem4] port ttyUSB1 timed out 9 consecutive times
Apr 25 09:10:07 pureos ModemManager[5761]: <warn> [modem4/bearer9] connection attempt #1 failed: Serial command timed out
Apr 25 09:10:07 pureos ModemManager[5761]: <info> [modem4] state changed (connecting -> registered)
Apr 25 09:10:07 pureos ModemManager[5761]: <info> [modem4/bearer9] connection #1 finished: duration 0s, tx: 0 bytes, rx: 0 bytes
Apr 25 09:10:07 pureos ModemManager[5761]: <error> [modem4] port ttyUSB1 timed out 10 consecutive times, marking modem as invalid
Apr 25 09:10:07 pureos mmsdtng[867]: ../plugins/modemmanager.c:modem_state_changed_cb() State Change: Old State: 10 New State: 8, Reason: 1
Apr 25 09:10:07 pureos mmsdtng[867]: ../plugins/modemmanager.c:mmsd_mm_get_modem_state() MM_MODEM_GOOD_STATE: 8
Apr 25 09:10:07 pureos mmsdtng[867]: ../plugins/modemmanager.c:mmsd_mm_state() MMSD_MM_STATE_READY
Apr 25 09:10:07 pureos mmsdtng[867]: ../plugins/modemmanager.c:mmsd_mm_state() Setting Bearer Handler
Apr 25 09:10:07 pureos mmsdtng[867]: ../src/service.c:mms_service_set_bearer_handler() service 0xaaaad27f8370 handler 0xaaaab6475a20
Apr 25 09:10:07 pureos NetworkManager[567]: <info> [1682406607.6709] modem["ttyUSB1"]: modem state changed, 'connecting' --> 'registered' (reason: user-requested)
Apr 25 09:10:07 pureos NetworkManager[567]: <warn> [1682406607.6712] modem-broadband[ttyUSB1]: failed to connect modem: Serial command timed out
Apr 25 09:10:07 pureos NetworkManager[567]: <info> [1682406607.6714] device (ttyUSB1): state change: prepare -> failed (reason 'unknown', sys-iface-state: 'managed')
Apr 25 09:10:07 pureos mmsdtng[867]: ../plugins/modemmanager.c:mmsd_modem_unavailable() Disabling Bearer Handler
Apr 25 09:10:07 pureos mmsdtng[867]: ../src/service.c:mms_service_set_bearer_handler() service 0xaaaad27f8370 handler (nil)
Apr 25 09:10:07 pureos mmsdtng[867]: ../plugins/modemmanager.c:mmsd_disconnect_from_sms_wap() Stopping watching SMS WAPs
Apr 25 09:10:07 pureos mmsdtng[867]: ../plugins/modemmanager.c:mmsd_mm_state() Modem vanished, Disabling plugin
Apr 25 09:10:07 pureos mmsdtng[867]: ../plugins/modemmanager.c:mmsd_mm_state() MMSD_MM_STATE_NO_MODEM
Apr 25 09:10:07 pureos mmsdtng[867]: ../plugins/modemmanager.c:cb_object_removed() Modem removed: /org/freedesktop/ModemManager1/Modem/4
Apr 25 09:10:07 pureos NetworkManager[567]: <warn> [1682406607.6798] device (ttyUSB1): Activation: failed for connection 'Fonic'
Apr 25 09:10:07 pureos NetworkManager[567]: <info> [1682406607.6823] device (ttyUSB1): state change: failed -> disconnected (reason 'none', sys-iface-state: 'managed')
Apr 25 09:10:07 pureos NetworkManager[567]: <info> [1682406607.6897] device (ttyUSB1): state change: disconnected -> unmanaged (reason 'removed', sys-iface-state: 'removed')
Apr 25 09:10:32 pureos sm.puri.OSK0.desktop[1285]: Debug: Tried file "/home/purism/.local/share/squeekboard/keyboards/terminal/us.yaml", but it's missing: No such file or directory (os error 2)
Apr 25 09:10:32 pureos sm.puri.OSK0.desktop[1285]: Info: Loaded layout Resource: terminal/us
Apr 25 09:10:34 pureos dbus-daemon[875]: [session uid=1000 pid=875] Activating service name='org.gnome.DejaDup' requested by ':1.29' (uid=1000 pid=1064 comm="/usr/libexec/phosh ")
Apr 25 09:10:34 pureos sm.puri.OSK0.desktop[1285]: Debug: Tried file "/home/purism/.local/share/squeekboard/keyboards/terminal/us.yaml", but it's missing: No such file or directory (os error 2)
Apr 25 09:10:34 pureos sm.puri.OSK0.desktop[1285]: Info: Loaded layout Resource: terminal/us
Apr 25 09:10:35 pureos dbus-daemon[875]: [session uid=1000 pid=875] Successfully activated service 'org.gnome.DejaDup'
Apr 25 09:10:35 pureos sm.puri.OSK0.desktop[1285]: Debug: Tried file "/home/purism/.local/share/squeekboard/keyboards/terminal/us.yaml", but it's missing: No such file or directory (os error 2)
Apr 25 09:10:35 pureos sm.puri.OSK0.desktop[1285]: Info: Loaded layout Resource: terminal/us
Apr 25 09:10:35 pureos deja-dup[23788]: g_object_set: assertion 'G_IS_OBJECT (object)' failed
Apr 25 09:10:35 pureos sm.puri.OSK0.desktop[1285]: Debug: Tried file "/home/purism/.local/share/squeekboard/keyboards/terminal/us.yaml", but it's missing: No such file or directory (os error 2)
Apr 25 09:10:35 pureos sm.puri.OSK0.desktop[1285]: Info: Loaded layout Resource: terminal/us
Apr 25 09:10:36 pureos sm.puri.OSK0.desktop[1285]: Debug: Tried file "/home/purism/.local/share/squeekboard/keyboards/terminal/us.yaml", but it's missing: No such file or directory (os error 2)
Apr 25 09:10:36 pureos sm.puri.OSK0.desktop[1285]: Info: Loaded layout Resource: terminal/us
Apr 25 09:10:42 pureos wpa_supplicant[628]: wlan0: WPA: Group rekeying completed with cc:ce:1e:7b:f5:b9 [GTK=CCMP]
Apr 25 09:10:42 pureos kernel: redpine_91x: Packet Dropped as Key ID not matched with both current and previous Key ID
Apr 25 09:10:42 pureos kernel: redpine_91x: Packet Dropped as Key ID not matched with both current and previous Key ID
Apr 25 09:10:53 pureos sm.puri.Phosh.desktop[6209]: Missing chrome or resource URL: resource://gre/modules/UpdateListener.jsm
Apr 25 09:10:53 pureos sm.puri.Phosh.desktop[6209]: Missing chrome or resource URL: resource://gre/modules/UpdateListener.sys.mjs
Apr 25 09:10:55 pureos systemd[843]: vte-spawn-d7951a5a-42b3-466c-a4a4-bd3dfdb5f19e.scope: Succeeded.
Apr 25 09:10:55 pureos systemd[843]: vte-spawn-d7951a5a-42b3-466c-a4a4-bd3dfdb5f19e.scope: Consumed 1.064s CPU time.
Apr 25 09:10:55 pureos systemd[843]: vte-spawn-2d3d46c0-02c6-4d5b-878d-927c2d6f2eeb.scope: Succeeded.
Apr 25 09:10:55 pureos systemd[843]: vte-spawn-2d3d46c0-02c6-4d5b-878d-927c2d6f2eeb.scope: Consumed 1min 29.398s CPU time.
Apr 25 09:10:56 pureos dbus-daemon[875]: [session uid=1000 pid=875] Activating via systemd: service name='org.freedesktop.Tracker1' unit='tracker-store.service' requested by ':1.2' (uid=1000 pid=872 comm="/usr/libexec/tracker-miner-fs ")
Apr 25 09:10:56 pureos systemd[843]: Starting Tracker metadata database store and lookup manager...
Apr 25 09:10:56 pureos dbus-daemon[875]: [session uid=1000 pid=875] Successfully activated service 'org.freedesktop.Tracker1'
Apr 25 09:10:56 pureos systemd[843]: Started Tracker metadata database store and lookup manager.
Apr 25 09:11:01 pureos yad[23844]: ../../../../../gdk/x11/gdkwindow-x11.c:5650 drawable is not a native X11 window
Apr 25 09:11:01 pureos phosh[1064]: Could not find application for app-id 'yad'
Apr 25 09:11:01 pureos sm.puri.OSK0.desktop[1285]: Debug: Tried file "/home/purism/.local/share/squeekboard/keyboards/terminal/us.yaml", but it's missing: No such file or directory (os error 2)
Apr 25 09:11:01 pureos sm.puri.OSK0.desktop[1285]: Info: Loaded layout Resource: terminal/us
Apr 25 09:11:03 pureos sm.puri.Phosh.desktop[23839]: /home/purism/Pictures/2023-04-25-091100.png|5|
Apr 25 09:11:09 pureos dbus-daemon[875]: [session uid=1000 pid=875] Activating via systemd: service name='org.freedesktop.Tracker1.Miner.Extract' unit='tracker-extract.service' requested by ':1.2' (uid=1000 pid=872 comm="/usr/libexec/tracker-miner-fs ")
```https://source.puri.sm/Librem5/linux/-/issues/475qmi_wwan netdev watchdog / xhci: Ring expansion failed2023-04-18T13:30:41ZMartin Kepplingerqmi_wwan netdev watchdog / xhci: Ring expansion failedafter literally letting the phone lie on the table doing nothing, after 3 days, suddenly the following happens, suggesting some kind of memory leak:
```
Apr 16 06:40:58 pureos kernel: ------------[ cut here ]------------
Apr 16 06:40:58...after literally letting the phone lie on the table doing nothing, after 3 days, suddenly the following happens, suggesting some kind of memory leak:
```
Apr 16 06:40:58 pureos kernel: ------------[ cut here ]------------
Apr 16 06:40:58 pureos kernel: NETDEV WATCHDOG: wwx2a413d796d06 (qmi_wwan): transmit queue 0 timed out
Apr 16 06:40:58 pureos kernel: WARNING: CPU: 0 PID: 0 at net/sched/sch_generic.c:525 dev_watchdog+0x280/0x2a0
Apr 16 06:40:58 pureos kernel: Modules linked in: brcmfmac_cyw bnep hci_uart btqca bluetooth brcmfmac brcmutil mtdblock mtd_blkdevs ofpart spi_nor mtd caam_jr caamhash_desc caamalg_desc crypto_engine st_lsm6dsx>
Apr 16 06:40:58 pureos kernel: ip_tables x_tables ipv6 uas usb_storage xhci_plat_hcd xhci_hcd usbcore dwc3 ulpi aes_ce_blk crct10dif_ce ghash_ce sha2_ce sha1_ce pwm_vibra cdns_mhdp_imx cdns_mhdp_drmcore udc_co>
Apr 16 06:40:58 pureos kernel: CPU: 0 PID: 0 Comm: swapper/0 Tainted: G C 6.2.10-librem5-00003-g9c48b1bed3ca #235
Apr 16 06:40:58 pureos kernel: Hardware name: Purism Librem 5r4 (DT)
Apr 16 06:40:58 pureos kernel: pstate: 60000005 (nZCv daif -PAN -UAO -TCO -DIT -SSBS BTYPE=--)
Apr 16 06:40:58 pureos kernel: pc : dev_watchdog+0x280/0x2a0
Apr 16 06:40:58 pureos kernel: lr : dev_watchdog+0x280/0x2a0
Apr 16 06:40:58 pureos kernel: sp : ffff800008003e00
Apr 16 06:40:58 pureos kernel: x29: ffff800008003e00 x28: ffff800009601d00 x27: 0000000000000002
Apr 16 06:40:58 pureos kernel: x26: ffff8000095f89e0 x25: ffff8000095f89e0 x24: ffff800009268008
Apr 16 06:40:58 pureos kernel: x23: ffff8000095f6000 x22: 0000000000000000 x21: ffff0000c1fc53dc
Apr 16 06:40:58 pureos kernel: x20: ffff0000c1fc5000 x19: ffff0000c1fc5488 x18: 00000000fffffffe
Apr 16 06:40:58 pureos kernel: x17: 6974203020657565 x16: 75712074696d736e x15: 617274203a296e61
Apr 16 06:40:58 pureos kernel: x14: 77775f696d712820 x13: 74756f2064656d69 x12: 7420302065756575
Apr 16 06:40:58 pureos kernel: x11: 00000000ffffdfff x10: 00000000ffffdfff x9 : ffff800008718f94
Apr 16 06:40:58 pureos kernel: x8 : 000000000002ffe8 x7 : 0000000000000000 x6 : 0000000000000000
Apr 16 06:40:58 pureos kernel: x5 : 0000000000000000 x4 : 0000000000000000 x3 : 0000000000000000
Apr 16 06:40:58 pureos kernel: x2 : 0000000000000000 x1 : 0000000000000000 x0 : ffff800009601d00
Apr 16 06:40:58 pureos kernel: Call trace:
Apr 16 06:40:58 pureos kernel: dev_watchdog+0x280/0x2a0
Apr 16 06:40:58 pureos kernel: call_timer_fn+0x3c/0x1cc
Apr 16 06:40:58 pureos kernel: expire_timers+0xcc/0x190
Apr 16 06:40:58 pureos kernel: run_timer_softirq+0xfc/0x260
Apr 16 06:40:58 pureos kernel: __do_softirq+0x120/0x3c0
Apr 16 06:40:58 pureos kernel: ____do_softirq+0x18/0x24
Apr 16 06:40:58 pureos kernel: call_on_irq_stack+0x2c/0x54
Apr 16 06:40:58 pureos kernel: do_softirq_own_stack+0x24/0x3c
Apr 16 06:40:58 pureos kernel: __irq_exit_rcu+0xb8/0xe0
Apr 16 06:40:58 pureos kernel: irq_exit_rcu+0x18/0x24
Apr 16 06:40:58 pureos kernel: el1_interrupt+0x38/0x70
Apr 16 06:40:58 pureos kernel: el1h_64_irq_handler+0x18/0x2c
Apr 16 06:40:58 pureos kernel: el1h_64_irq+0x64/0x68
Apr 16 06:40:58 pureos kernel: cpuidle_enter_state+0xbc/0x4b0
Apr 16 06:40:58 pureos kernel: cpuidle_enter+0x40/0x60
Apr 16 06:40:58 pureos kernel: do_idle+0x234/0x2c0
Apr 16 06:40:58 pureos kernel: cpu_startup_entry+0x2c/0x3c
Apr 16 06:40:58 pureos kernel: rest_init+0xf8/0x100
Apr 16 06:40:58 pureos kernel: arch_post_acpi_subsys_init+0x0/0x28
Apr 16 06:40:58 pureos kernel: start_kernel+0x708/0x748
Apr 16 06:40:58 pureos kernel: __primary_switched+0xbc/0xc4
Apr 16 06:40:58 pureos kernel: ---[ end trace 0000000000000000 ]---
Apr 16 14:28:28 pureos kernel: ------------[ cut here ]------------
Apr 16 14:28:28 pureos kernel: Failed to get suitable pool for 38200000.usb
Apr 16 14:28:28 pureos kernel: WARNING: CPU: 0 PID: 0 at kernel/dma/pool.c:279 dma_alloc_from_pool+0x90/0x1e0
Apr 16 14:28:28 pureos kernel: Modules linked in: brcmfmac_cyw bnep hci_uart btqca bluetooth brcmfmac brcmutil mtdblock mtd_blkdevs ofpart spi_nor mtd caam_jr caamhash_desc caamalg_desc crypto_engine st_lsm6dsx>
Apr 16 14:28:28 pureos kernel: ip_tables x_tables ipv6 uas usb_storage xhci_plat_hcd xhci_hcd usbcore dwc3 ulpi aes_ce_blk crct10dif_ce ghash_ce sha2_ce sha1_ce pwm_vibra cdns_mhdp_imx cdns_mhdp_drmcore udc_co>
Apr 16 14:28:28 pureos kernel: CPU: 0 PID: 0 Comm: swapper/0 Tainted: G WC 6.2.10-librem5-00003-g9c48b1bed3ca #235
Apr 16 14:28:28 pureos kernel: Hardware name: Purism Librem 5r4 (DT)
Apr 16 14:28:28 pureos kernel: pstate: 600000c5 (nZCv daIF -PAN -UAO -TCO -DIT -SSBS BTYPE=--)
Apr 16 14:28:28 pureos kernel: pc : dma_alloc_from_pool+0x90/0x1e0
Apr 16 14:28:28 pureos kernel: lr : dma_alloc_from_pool+0x90/0x1e0
Apr 16 14:28:28 pureos kernel: sp : ffff800008003850
Apr 16 14:28:28 pureos kernel: x29: ffff800008003850 x28: ffff8000098e5740 x27: 0000000000000000
Apr 16 14:28:28 pureos kernel: x26: ffff0000c0860600 x25: ffff800008003910 x24: ffff0000c0ad9010
Apr 16 14:28:28 pureos kernel: x23: ffff8000098e5720 x22: ffff8000080e0990 x21: ffff8000090c6178
Apr 16 14:28:28 pureos kernel: x20: 0000000000001000 x19: ffff0000d634e298 x18: ffff0000ff7a804c
Apr 16 14:28:28 pureos kernel: x17: ffff8000f64cc000 x16: 001fffffffffffff x15: f935e8b07ee39061
Apr 16 14:28:28 pureos kernel: x14: 0000000000000000 x13: 6273752e30303030 x12: 3032383320726f66
Apr 16 14:28:28 pureos kernel: x11: 00000000ffffdfff x10: 00000000ffffdfff x9 : ffff8000080b4a58
Apr 16 14:28:28 pureos kernel: x8 : 000000000002ffe8 x7 : c0000000ffffdfff x6 : 0000000000017ff4
Apr 16 14:28:28 pureos kernel: x5 : ffff0000ff735a08 x4 : 0000000000000000 x3 : 0000000000000027
Apr 16 14:28:28 pureos kernel: x2 : 0000000000000000 x1 : 0000000000000000 x0 : ffff800009601d00
Apr 16 14:28:28 pureos kernel: Call trace:
Apr 16 14:28:28 pureos kernel: dma_alloc_from_pool+0x90/0x1e0
Apr 16 14:28:28 pureos kernel: dma_direct_alloc+0x94/0x310
Apr 16 14:28:28 pureos kernel: dma_alloc_attrs+0x88/0x100
Apr 16 14:28:28 pureos kernel: dma_pool_alloc+0x11c/0x200
Apr 16 14:28:28 pureos kernel: xhci_segment_alloc+0x94/0x160 [xhci_hcd]
Apr 16 14:28:28 pureos kernel: xhci_alloc_segments_for_ring+0xe4/0x1d0 [xhci_hcd]
Apr 16 14:28:28 pureos kernel: xhci_ring_expansion+0x74/0x380 [xhci_hcd]
Apr 16 14:28:28 pureos kernel: prepare_ring+0x198/0x2c0 [xhci_hcd]
Apr 16 14:28:28 pureos kernel: prepare_transfer+0x88/0x170 [xhci_hcd]
Apr 16 14:28:28 pureos kernel: xhci_queue_bulk_tx+0xd4/0x910 [xhci_hcd]
Apr 16 14:28:28 pureos kernel: xhci_urb_enqueue+0x330/0x580 [xhci_hcd]
Apr 16 14:28:28 pureos kernel: usb_hcd_submit_urb+0xd0/0xa90 [usbcore]
Apr 16 14:28:28 pureos kernel: usb_submit_urb+0x1f0/0x670 [usbcore]
Apr 16 14:28:28 pureos kernel: rx_submit+0x148/0x310 [usbnet]
Apr 16 14:28:28 pureos kernel: rx_complete+0x200/0x330 [usbnet]
Apr 16 14:28:28 pureos kernel: __usb_hcd_giveback_urb+0xa4/0x164 [usbcore]
Apr 16 14:28:28 pureos kernel: usb_giveback_urb_bh+0xb0/0x1a0 [usbcore]
Apr 16 14:28:28 pureos kernel: tasklet_action_common.constprop.0+0x104/0x130
Apr 16 14:28:28 pureos kernel: tasklet_action+0x30/0x40
Apr 16 14:28:28 pureos kernel: __do_softirq+0x120/0x3c0
Apr 16 14:28:28 pureos kernel: ____do_softirq+0x18/0x24
Apr 16 14:28:28 pureos kernel: call_on_irq_stack+0x2c/0x54
Apr 16 14:28:28 pureos kernel: do_softirq_own_stack+0x24/0x3c
Apr 16 14:28:28 pureos kernel: __irq_exit_rcu+0xb8/0xe0
Apr 16 14:28:28 pureos kernel: irq_exit_rcu+0x18/0x24
Apr 16 14:28:28 pureos kernel: el1_interrupt+0x38/0x70
Apr 16 14:28:28 pureos kernel: el1h_64_irq_handler+0x18/0x2c
Apr 16 14:28:28 pureos kernel: el1h_64_irq+0x64/0x68
Apr 16 14:28:28 pureos kernel: cpuidle_enter_state+0xc0/0x4b0
Apr 16 14:28:28 pureos kernel: cpuidle_enter+0x40/0x60
Apr 16 14:28:28 pureos kernel: do_idle+0x234/0x2c0
Apr 16 14:28:28 pureos kernel: cpu_startup_entry+0x30/0x3c
Apr 16 14:28:28 pureos kernel: rest_init+0xf8/0x100
Apr 16 14:28:28 pureos kernel: arch_post_acpi_subsys_init+0x0/0x28
Apr 16 14:28:28 pureos kernel: start_kernel+0x708/0x748
Apr 16 14:28:28 pureos kernel: __primary_switched+0xbc/0xc4
Apr 16 14:28:28 pureos kernel: ---[ end trace 0000000000000000 ]---
Apr 16 14:28:28 pureos kernel: xhci-hcd xhci-hcd.4.auto: Ring expansion failed
Apr 16 14:28:28 pureos kernel: ------------[ cut here ]------------
Apr 16 14:28:28 pureos kernel: Failed to get suitable pool for 38200000.usb
Apr 16 14:28:28 pureos kernel: WARNING: CPU: 0 PID: 14 at kernel/dma/pool.c:279 dma_alloc_from_pool+0x90/0x1e0
Apr 16 14:28:28 pureos kernel: Modules linked in: brcmfmac_cyw bnep hci_uart btqca bluetooth brcmfmac brcmutil mtdblock mtd_blkdevs ofpart spi_nor mtd caam_jr caamhash_desc caamalg_desc crypto_engine st_lsm6dsx>
Apr 16 14:28:28 pureos kernel: ip_tables x_tables ipv6 uas usb_storage xhci_plat_hcd xhci_hcd usbcore dwc3 ulpi aes_ce_blk crct10dif_ce ghash_ce sha2_ce sha1_ce pwm_vibra cdns_mhdp_imx cdns_mhdp_drmcore udc_co>
Apr 16 14:28:28 pureos kernel: CPU: 0 PID: 14 Comm: ksoftirqd/0 Tainted: G WC 6.2.10-librem5-00003-g9c48b1bed3ca #235
Apr 16 14:28:28 pureos kernel: Hardware name: Purism Librem 5r4 (DT)
Apr 16 14:28:28 pureos kernel: pstate: 600000c5 (nZCv daIF -PAN -UAO -TCO -DIT -SSBS BTYPE=--)
Apr 16 14:28:28 pureos kernel: pc : dma_alloc_from_pool+0x90/0x1e0
Apr 16 14:28:28 pureos kernel: lr : dma_alloc_from_pool+0x90/0x1e0
Apr 16 14:28:28 pureos kernel: sp : ffff800009b036b0
Apr 16 14:28:28 pureos kernel: x29: ffff800009b036b0 x28: ffff8000098e5740 x27: 0000000000000000
Apr 16 14:28:28 pureos kernel: x26: ffff0000c0860600 x25: ffff800009b03770 x24: ffff0000c0ad9010
Apr 16 14:28:28 pureos kernel: x23: ffff8000098e5720 x22: ffff8000080e0990 x21: ffff8000090c6178
Apr 16 14:28:28 pureos kernel: x20: 0000000000001000 x19: ffff00000682c998 x18: ffff0000ff7a804c
Apr 16 14:28:28 pureos kernel: x17: 000000040044ffff x16: 001fffffffffffff x15: a313d2543da5da02
Apr 16 14:28:28 pureos kernel: x14: 0000000000000000 x13: 6273752e30303030 x12: 3032383320726f66
Apr 16 14:28:28 pureos kernel: x11: 00000000ffffdfff x10: 00000000ffffdfff x9 : ffff8000080b4a58
Apr 16 14:28:28 pureos kernel: x8 : 000000000002ffe8 x7 : c0000000ffffdfff x6 : 0000000000017ff4
Apr 16 14:28:28 pureos kernel: x5 : ffff0000ff735a08 x4 : 0000000000000000 x3 : 0000000000000027
Apr 16 14:28:28 pureos kernel: x2 : 0000000000000000 x1 : 0000000000000000 x0 : ffff0000c0254740
Apr 16 14:28:28 pureos kernel: Call trace:
Apr 16 14:28:28 pureos kernel: dma_alloc_from_pool+0x90/0x1e0
Apr 16 14:28:28 pureos kernel: dma_direct_alloc+0x94/0x310
Apr 16 14:28:28 pureos kernel: dma_alloc_attrs+0x88/0x100
Apr 16 14:28:28 pureos kernel: dma_pool_alloc+0x11c/0x200
Apr 16 14:28:28 pureos kernel: xhci_segment_alloc+0x94/0x160 [xhci_hcd]
Apr 16 14:28:28 pureos kernel: xhci_alloc_segments_for_ring+0xe4/0x1d0 [xhci_hcd]
Apr 16 14:28:28 pureos kernel: xhci_ring_expansion+0x74/0x380 [xhci_hcd]
Apr 16 14:28:28 pureos kernel: prepare_ring+0x198/0x2c0 [xhci_hcd]
Apr 16 14:28:28 pureos kernel: prepare_transfer+0x88/0x170 [xhci_hcd]
Apr 16 14:28:28 pureos kernel: xhci_queue_bulk_tx+0xd4/0x910 [xhci_hcd]
Apr 16 14:28:28 pureos kernel: xhci_urb_enqueue+0x330/0x580 [xhci_hcd]
Apr 16 14:28:28 pureos kernel: usb_hcd_submit_urb+0xd0/0xa90 [usbcore]
Apr 16 14:28:28 pureos kernel: usb_submit_urb+0x1f0/0x670 [usbcore]
Apr 16 14:28:28 pureos kernel: rx_submit+0x148/0x310 [usbnet]
Apr 16 14:28:28 pureos kernel: rx_alloc_submit+0x58/0x94 [usbnet]
Apr 16 14:28:28 pureos kernel: usbnet_bh+0x2d0/0x36c [usbnet]
Apr 16 14:28:28 pureos kernel: usbnet_bh_tasklet+0x1c/0x30 [usbnet]
Apr 16 14:28:28 pureos kernel: tasklet_action_common.constprop.0+0x104/0x130
Apr 16 14:28:28 pureos kernel: tasklet_action+0x30/0x40
Apr 16 14:28:28 pureos kernel: __do_softirq+0x120/0x3c0
Apr 16 14:28:28 pureos kernel: run_ksoftirqd+0x54/0x70
Apr 16 14:28:28 pureos kernel: smpboot_thread_fn+0x244/0x270
Apr 16 14:28:28 pureos kernel: kthread+0x114/0x120
Apr 16 14:28:28 pureos kernel: ret_from_fork+0x10/0x20
Apr 16 14:28:28 pureos kernel: ---[ end trace 0000000000000000 ]---
Apr 16 14:28:28 pureos kernel: xhci-hcd xhci-hcd.4.auto: Ring expansion failed
```
does NXP possibly have a workaround for us? https://community.nxp.com/t5/i-MX-Processors/imx8mq-yocto-4-9-51-ga-USB3-0-issue/m-p/857504 seen when searching real quick...https://source.puri.sm/Librem5/linux/-/issues/474WiFi stays "connected" when access point is out of range2023-04-28T09:33:50ZJan VlugWiFi stays "connected" when access point is out of rangeIt happens from time to time that the WiFi (according to the indicator in the top status bar) stays connected, even when I'm far out of range of the access points of that specific WiFi network. The network is than still "available" but d...It happens from time to time that the WiFi (according to the indicator in the top status bar) stays connected, even when I'm far out of range of the access points of that specific WiFi network. The network is than still "available" but does not work.
If I ping for example, I get the Destination Host Unreachable message.
If I disable the WiFi from the quick settings, the network starts working again (via 4G).
See the log for details:
[WiFi-connected-while-out-of-reach.log](/uploads/b3b8cb8998e7967472d6abf4113cfe8f/WiFi-connected-while-out-of-reach.log)
I left the house after roughly 15:35
Then you see in the log messages like this:
```
Apr 14 15:38:53 avalon kernel: redpine_91x: Antenna is changed to 3
Apr 14 15:39:19 avalon kernel: redpine_91x: Antenna is changed to 2
```
They keep appearing until I brought the interface down and up again:
```
Apr 14 16:08:18 avalon kernel: redpine_91x: <==== Interface DOWN ====>
Apr 14 16:10:16 avalon kernel: redpine_91x: <==== Interface UP ====>
```
At 16:10 I enabled WiFi hotspot, the issue happened before that.
Maybe related to issue #308.https://source.puri.sm/Librem5/linux/-/issues/473Modem disapears with USB debounce error2023-04-09T23:39:08ZAlistairModem disapears with USB debounce errorWhen running the `6.2.8-librem5.1` kernel and librem5-base 58 (on pmOS) I frequently see these error message and the modem disapears:
```
usb 1-1-port2: connect-debounce failed
```
This is the full dmesg
```
[ 1114.043878] usb 1-1.2: ...When running the `6.2.8-librem5.1` kernel and librem5-base 58 (on pmOS) I frequently see these error message and the modem disapears:
```
usb 1-1-port2: connect-debounce failed
```
This is the full dmesg
```
[ 1114.043878] usb 1-1.2: USB disconnect, device number 4
[ 1114.045556] option1 ttyUSB0: GSM modem (1-port) converter now disconnected from ttyUSB0
[ 1114.045654] option 1-1.2:1.0: device disconnected
[ 1114.046363] option1 ttyUSB1: GSM modem (1-port) converter now disconnected from ttyUSB1
[ 1114.046418] option 1-1.2:1.1: device disconnected
[ 1114.047034] option1 ttyUSB2: GSM modem (1-port) converter now disconnected from ttyUSB2
[ 1114.047107] option 1-1.2:1.2: device disconnected
[ 1114.047956] option1 ttyUSB3: GSM modem (1-port) converter now disconnected from ttyUSB3
[ 1114.048037] option 1-1.2:1.3: device disconnected
[ 1114.048409] qmi_wwan 1-1.2:1.4 wwan0: unregister 'qmi_wwan' usb-xhci-hcd.4.auto-1.2, WWAN/QMI device
[ 1114.307398] usb 1-1.2: new high-speed USB device number 5 using xhci-hcd
[ 1114.513689] usb 1-1.2: New USB device found, idVendor=2020, idProduct=2060, bcdDevice= 0.00
[ 1114.513755] usb 1-1.2: New USB device strings: Mfr=3, Product=2, SerialNumber=4
[ 1114.513762] usb 1-1.2: Product: Qualcomm CDMA Technologies MSM
[ 1114.513767] usb 1-1.2: Manufacturer: Qualcomm, Incorporated
[ 1114.641204] option 1-1.2:1.0: GSM modem (1-port) converter detected
[ 1114.641785] usb 1-1.2: GSM modem (1-port) converter now attached to ttyUSB0
[ 1114.642420] option 1-1.2:1.1: GSM modem (1-port) converter detected
[ 1114.643235] usb 1-1.2: GSM modem (1-port) converter now attached to ttyUSB1
[ 1114.643996] option 1-1.2:1.2: GSM modem (1-port) converter detected
[ 1114.645527] usb 1-1.2: GSM modem (1-port) converter now attached to ttyUSB2
[ 1114.646660] option 1-1.2:1.3: GSM modem (1-port) converter detected
[ 1114.647130] usb 1-1.2: GSM modem (1-port) converter now attached to ttyUSB3
[ 1114.672704] qmi_wwan 1-1.2:1.4: cdc-wdm0: USB WDM device
[ 1114.674076] qmi_wwan 1-1.2:1.4 wwan0: register 'qmi_wwan' at usb-xhci-hcd.4.auto-1.2, WWAN/QMI device, fe:96:c6:b1:e6:3c
[ 1119.551325] usb 1-1.2: USB disconnect, device number 5
[ 1119.553257] option1 ttyUSB0: GSM modem (1-port) converter now disconnected from ttyUSB0
[ 1119.553369] option 1-1.2:1.0: device disconnected
[ 1119.554824] option1 ttyUSB1: GSM modem (1-port) converter now disconnected from ttyUSB1
[ 1119.554991] option 1-1.2:1.1: device disconnected
[ 1119.556677] option1 ttyUSB2: GSM modem (1-port) converter now disconnected from ttyUSB2
[ 1119.556818] option 1-1.2:1.2: device disconnected
[ 1119.557847] option1 ttyUSB3: GSM modem (1-port) converter now disconnected from ttyUSB3
[ 1119.557939] option 1-1.2:1.3: device disconnected
[ 1119.558337] qmi_wwan 1-1.2:1.4 wwan0: unregister 'qmi_wwan' usb-xhci-hcd.4.auto-1.2, WWAN/QMI device
[ 1122.499309] usb 1-1-port2: connect-debounce failed
```
System suspend is disabled, so it isn't related to that.https://source.puri.sm/Librem5/linux/-/issues/472s5k3l6xx: support HKS-disconnection / module removal while streaming2023-04-05T09:12:44ZMartin Kepplingers5k3l6xx: support HKS-disconnection / module removal while streamingwe have a udev rule that simply unloads the module when the HKS disconnects the device. But for the rear camera, things a are not balanced **when streaming**:
```
[ 386.136907] ------------[ cut here ]------------
[ 386.136926] WARNIN...we have a udev rule that simply unloads the module when the HKS disconnects the device. But for the rear camera, things a are not balanced **when streaming**:
```
[ 386.136907] ------------[ cut here ]------------
[ 386.136926] WARNING: CPU: 3 PID: 2907 at drivers/regulator/core.c:2330 _regulator_put.part.0+0x160/0x170
[ 386.136950] Modules linked in: hi846 s5k3l6xx(-) aes_ce_ccm redpine_sdio redpine_91x bluetooth mac80211 cfg80211 qmi_wwan cdc_wdm usbnet option mii usb_wwan usbserial mousedev caam_jr caamhash_desc caamalg_desc crypto_engine usb_f_acm u_serial usb_f_ncm u_ether aes_ce_blk crct10dif_ce snd_soc_gtm601 ghash_ce hantro_vpu sha2_ce v4l2_vp9 sha1_ce snd_soc_simple_card v4l2_h264 v4l2_mem2mem snd_soc_imx_hdmi pwm_vibra snd_soc_simple_card_utils snd_soc_hdmi_codec snd_soc_wm8962 edt_ft5x06 st_lsm6dsx_spi dw9714 snd_soc_fsl_sai snd_soc_fsl_utils videobuf2_dma_contig videobuf2_memops st_magn_spi st_sensors_spi leds_lm3560 videobuf2_v4l2 videobuf2_common v4l2_fwnode v4l2_flash_led_class v4l2_async st_lsm6dsx_i2c imx_pcm_dma st_magn_i2c st_magn st_sensors_i2c st_lsm6dsx vcnl4000 st_sensors industrialio_triggered_buffer videodev gnss_mtk kfifo_buf gnss_serial mc gnss caam snd_soc_core imx2_wdt error snd_pcm_dmaengine snd_pcm snd_timer watchdog snd rfkill_hks soundcore rfkill libcomposite
[ 386.137173] ledtrig_timer ledtrig_pattern fuse zram ip_tables x_tables ipv6 uas usb_storage mtdblock mtd_blkdevs overlay ofpart xhci_plat_hcd xhci_hcd spi_nor usbcore mtd dwc3 ulpi cdns_mhdp_imx cdns_mhdp_drmcore drm_display_helper imx_dcss tps6598x udc_core bq25890_charger phy_fsl_imx8mq_usb usb_common typec clk_bd718x7 roles snvs_pwrkey imx_sdma virt_dma [last unloaded: imx8mq_mipi_csi2(C)]
[ 386.137272] CPU: 3 PID: 2907 Comm: rmmod Tainted: G C 6.1.22-librem5-00453-g7834de6cba92 #224
[ 386.137280] Hardware name: Purism Librem 5r4 (DT)
[ 386.137284] pstate: 80000005 (Nzcv daif -PAN -UAO -TCO -DIT -SSBS BTYPE=--)
[ 386.137291] pc : _regulator_put.part.0+0x160/0x170
[ 386.137299] lr : regulator_bulk_free+0x68/0x94
[ 386.137307] sp : ffff80000bff3b20
[ 386.137310] x29: ffff80000bff3b20 x28: ffff000028e88e80 x27: 0000000000000000
[ 386.137321] x26: 0000000000000000 x25: 0000000000000000 x24: ffff8000095289e0
[ 386.137331] x23: ffff8000091a7008 x22: ffff0000698680f8 x21: ffff800009701b00
[ 386.137342] x20: ffff00003a8bcd00 x19: ffff00003a8bcd00 x18: 0000000000000000
[ 386.137353] x17: 0000000000000000 x16: 0000000000000000 x15: 0000000000000000
[ 386.137363] x14: 000000000000001d x13: 0000000000000000 x12: 0000000000000000
[ 386.137373] x11: 0000000000000001 x10: ffff000009514ea8 x9 : ffff80000875a628
[ 386.137384] x8 : ffff80000884aff4 x7 : 0000000000000000 x6 : ffff000028e88e80
[ 386.137394] x5 : 0000000000000001 x4 : 0000000000000000 x3 : ffff800009701b00
[ 386.137404] x2 : ffff000028e88e80 x1 : 0000000000000000 x0 : 0000000000000001
[ 386.137415] Call trace:
[ 386.137419] _regulator_put.part.0+0x160/0x170
[ 386.137427] regulator_bulk_free+0x68/0x94
[ 386.137434] devm_regulator_bulk_release+0x24/0x30
[ 386.137441] release_nodes+0x64/0x104
[ 386.137450] devres_release_group+0xd4/0x140
[ 386.137457] i2c_device_remove+0x50/0xe0
[ 386.137465] device_remove+0x54/0x8c
[ 386.137475] device_release_driver_internal+0x1e4/0x250
[ 386.137483] driver_detach+0x58/0xa0
[ 386.137491] bus_remove_driver+0x64/0x100
[ 386.137498] driver_unregister+0x38/0x70
[ 386.137506] i2c_del_driver+0x5c/0xa4
[ 386.137511] s5k3l6xx_i2c_driver_exit+0x18/0xe9c [s5k3l6xx]
[ 386.137529] __arm64_sys_delete_module+0x184/0x31c
[ 386.137541] invoke_syscall+0x50/0x120
[ 386.137550] el0_svc_common.constprop.0+0xd4/0xf4
[ 386.137557] do_el0_svc+0x24/0x30
[ 386.137564] el0_svc+0x2c/0x84
[ 386.137573] el0t_64_sync_handler+0xb8/0xc0
[ 386.137580] el0t_64_sync+0x18c/0x190
[ 386.137587] ---[ end trace 0000000000000000 ]---
```
also, the focus driver needs to be taken into account.https://source.puri.sm/Librem5/linux/-/issues/471Both cameras fail to probe (on two Birch or Chestnut devices)2023-04-04T11:05:21ZRobert MaderBoth cameras fail to probe (on two Birch or Chestnut devices)Known affected versions:
- 6.1.19pureos1
- 6.1.21pureos1
I'm trying to use the cameras on two older testing devices (belonging to @tobias.bernard), but on both devices both cameras fail to probe. The following logs are printed do `dme...Known affected versions:
- 6.1.19pureos1
- 6.1.21pureos1
I'm trying to use the cameras on two older testing devices (belonging to @tobias.bernard), but on both devices both cameras fail to probe. The following logs are printed do `dmesg` during boot and when turning the hardware switch off and on again:
```
[ 147.124805] imx7_media_csi: module is from the staging directory, the quality is unknown, you have been warned.
[ 147.141683] imx7-csi 30a90000.csi: Registered csi capture as /dev/video0
[ 147.146024] imx7-csi 30b80000.csi: Registered csi capture as /dev/video1
[ 147.317030] imx8mq_mipi_csi2: module is from the staging directory, the quality is unknown, you have been warned.
[ 147.338116] imx8mq-mipi-csi2 30a70000.csi: Consider updating driver imx8mq-mipi-csi2 to match on endpoints
[ 147.345663] imx8mq-mipi-csi2 30b60000.csi: Consider updating driver imx8mq-mipi-csi2 to match on endpoints
[ 147.485112] s5k3l6xx 3-002d: using default 24000000 Hz clock frequency
[ 147.485331] s5k3l6xx 3-002d: GPIO lookup for consumer rstn
[ 147.485348] s5k3l6xx 3-002d: using device tree for GPIO lookup
[ 147.485492] of_get_named_gpiod_flags: parsed 'rstn-gpios' property of node '/soc@0/bus@30800000/i2c@30a50000/camera@2d[0]' - status (0)
[ 147.485712] gpio gpiochip0: Persistence not supported for GPIO 26
[ 147.485876] s5k3l6xx 3-002d: probe i2c ffff0000003b7000
[ 147.523351] s5k3l6xx: i2c_read: error during transfer (-11)
[ 147.533616] s5k3l6xx: probe of 3-002d failed with error -11
[ 147.616487] hi846 2-0020: GPIO lookup for consumer reset
[ 147.616674] hi846 2-0020: using device tree for GPIO lookup
[ 147.616792] of_get_named_gpiod_flags: parsed 'reset-gpios' property of node '/soc@0/bus@30800000/i2c@30a40000/camera@20[0]' - status (0)
[ 147.617009] gpio gpiochip0: Persistence not supported for GPIO 25
[ 147.617064] hi846 2-0020: GPIO lookup for consumer shutdown
[ 147.617074] hi846 2-0020: using device tree for GPIO lookup
[ 147.617145] of_get_named_gpiod_flags: parsed 'shutdown-gpios' property of node '/soc@0/bus@30800000/i2c@30a40000/camera@20[0]' - status (0)
[ 147.617206] gpio gpiochip4: Persistence not supported for GPIO 4
[ 147.635998] hi846 2-0020: i2c read error: -6
[ 147.654177] hi846: probe of 2-0020 failed with error -5
```
I hoped recent updates to the kernel in 6.1.21 would maybe help, but unfortunately they did not.https://source.puri.sm/Librem5/linux/-/issues/470Continuing modem resets with 6.1.19pureos12023-03-19T20:16:40ZSteve StevensContinuing modem resets with 6.1.19pureos1Creating as a new issue as the old one appears to be closed.
I've installed the kernel from landing, 6.1.19pureos1, and rebooted the l5 with it.
```
root@pureos:~# dpkg -l| grep linux-image
ii linux-image-6.0.0-1-librem5 6.0....Creating as a new issue as the old one appears to be closed.
I've installed the kernel from landing, 6.1.19pureos1, and rebooted the l5 with it.
```
root@pureos:~# dpkg -l| grep linux-image
ii linux-image-6.0.0-1-librem5 6.0.8pureos1 arm64 Linux 6.0 for the Librem 5 and its devkit
ii linux-image-6.1.0-1-librem5 6.1.19pureos1 arm64 Linux 6.1 for the Librem 5 and its devkit
ii linux-image-librem5 6.1.19pureos1 arm64 Linux kernel for the Librem 5 and its devkit
root@pureos:~# uname -r
6.1.0-1-librem5
```
Saw a reset of the modem(modem dissapeared from the phosh menu and came back, with a pause in audio), and attached dmesg logs for the last 15 minutes:
[librem5_modem_reset.log](/uploads/1911e4d2814d7c6a2e3b693e5da816af/librem5_modem_reset.log)https://source.puri.sm/Librem5/linux/-/issues/469edt_ft5x06_debugfs_upgrade_bin_write directly accesses user memory2023-03-15T22:58:24ZSebastian Krzyszkowiakedt_ft5x06_debugfs_upgrade_bin_write directly accesses user memorySeems like it's missing a `copy_from_user` call. This is clearly seen with `CONFIG_ARM64_SW_TTBR0_PAN` enabled, which enforces kernel/userspace memory boundary:
```
[ 76.187513] Unable to handle kernel access to user memory outside uacc...Seems like it's missing a `copy_from_user` call. This is clearly seen with `CONFIG_ARM64_SW_TTBR0_PAN` enabled, which enforces kernel/userspace memory boundary:
```
[ 76.187513] Unable to handle kernel access to user memory outside uaccess routines at virtual address 0000aaaaf7ed9d80
```
```
[ 76.463004] Call trace:
[ 76.465452] string+0x50/0x100
[ 76.468513] vsnprintf+0x170/0x750
[ 76.471919] snprintf+0x58/0x80
[ 76.475063] edt_ft5x06_debugfs_upgrade_bin_write+0xa8/0x350 [edt_ft5x06]
```https://source.puri.sm/Librem5/linux/-/issues/468Use the 200MHz parent for uart4 so that higher BT baud rates can be used.2023-03-15T12:24:23ZMartin KepplingerUse the 200MHz parent for uart4 so that higher BT baud rates can be used.I create this issue because I merged https://source.puri.sm/Librem5/linux/-/merge_requests/641 but then reverted it again because it introduced an error. Sorry about that Angus. If I understand it correctly, you think about changing `imx...I create this issue because I merged https://source.puri.sm/Librem5/linux/-/merge_requests/641 but then reverted it again because it introduced an error. Sorry about that Angus. If I understand it correctly, you think about changing `imx_register_uart_clocks()` instead anyways.https://source.puri.sm/Librem5/linux/-/issues/467caam_jr: RNG: Hardware error2024-01-07T01:15:29ZSebastian Krzyszkowiakcaam_jr: RNG: Hardware errorSometimes caam_jr goes into some bad state, breaking all sorts of things that rely on kernel's crypto subsystem (such as WiFi connection):
```
Mar 13 19:54:24 evergreen kernel: caam_jr 30902000.jr: 2000025b: CCB: desc idx 2: RNG: Hardwa...Sometimes caam_jr goes into some bad state, breaking all sorts of things that rely on kernel's crypto subsystem (such as WiFi connection):
```
Mar 13 19:54:24 evergreen kernel: caam_jr 30902000.jr: 2000025b: CCB: desc idx 2: RNG: Hardware error
Mar 13 19:54:34 evergreen kernel: caam_jr 30902000.jr: 2000005b: CCB: desc idx 0: RNG: Hardware error
Mar 13 19:54:44 evergreen kernel: caam_jr 30902000.jr: 2000005b: CCB: desc idx 0: RNG: Hardware error
Mar 13 19:56:51 evergreen kernel: caam_jr 30903000.jr: 2000055b: CCB: desc idx 5: RNG: Hardware error
Mar 13 19:56:52 evergreen kernel: caam_jr 30903000.jr: 2000175b: CCB: desc idx 23: RNG: Hardware error
Mar 13 19:56:52 evergreen kernel: caam_jr 30903000.jr: 2000175b: CCB: desc idx 23: RNG: Hardware error
Mar 13 19:56:52 evergreen kernel: caam_jr 30903000.jr: 2000175b: CCB: desc idx 23: RNG: Hardware error
Mar 13 19:56:52 evergreen kernel: caam_jr 30903000.jr: 2000175b: CCB: desc idx 23: RNG: Hardware error
Mar 13 19:56:52 evergreen kernel: caam_jr 30903000.jr: 20000b5b: CCB: desc idx 11: RNG: Hardware error
Mar 13 19:56:52 evergreen kernel: caam_jr 30903000.jr: 20000b5b: CCB: desc idx 11: RNG: Hardware error
Mar 13 19:56:53 evergreen kernel: caam_jr 30903000.jr: 20000b5b: CCB: desc idx 11: RNG: Hardware error
Mar 13 19:56:53 evergreen kernel: caam_jr 30903000.jr: 20000b5b: CCB: desc idx 11: RNG: Hardware error
Mar 13 19:56:53 evergreen kernel: caam_jr 30902000.jr: 2000005b: CCB: desc idx 0: RNG: Hardware error
Mar 13 19:57:03 evergreen kernel: caam_jr 30903000.jr: 2000055b: CCB: desc idx 5: RNG: Hardware error
Mar 13 19:57:04 evergreen kernel: caam_jr 30902000.jr: 2000005b: CCB: desc idx 0: RNG: Hardware error
Mar 13 19:57:05 evergreen kernel: caam_jr 30903000.jr: 2000115b: CCB: desc idx 17: RNG: Hardware error
Mar 13 19:57:05 evergreen kernel: caam_jr 30903000.jr: 2000115b: CCB: desc idx 17: RNG: Hardware error
Mar 13 19:57:05 evergreen kernel: caam_jr 30903000.jr: 2000115b: CCB: desc idx 17: RNG: Hardware error
Mar 13 19:57:05 evergreen kernel: caam_jr 30903000.jr: 2000115b: CCB: desc idx 17: RNG: Hardware error
Mar 13 19:57:05 evergreen kernel: caam_jr 30903000.jr: 2000115b: CCB: desc idx 17: RNG: Hardware error
Mar 13 19:57:05 evergreen kernel: caam_jr 30903000.jr: 2000115b: CCB: desc idx 17: RNG: Hardware error
Mar 13 19:57:05 evergreen kernel: caam_jr 30903000.jr: 2000115b: CCB: desc idx 17: RNG: Hardware error
Mar 13 19:57:05 evergreen kernel: caam_jr 30903000.jr: 2000115b: CCB: desc idx 17: RNG: Hardware error
Mar 13 19:57:09 evergreen kernel: caam_jr 30903000.jr: 2000115b: CCB: desc idx 17: RNG: Hardware error
Mar 13 19:57:09 evergreen kernel: caam_jr 30903000.jr: 2000115b: CCB: desc idx 17: RNG: Hardware error
Mar 13 19:57:14 evergreen kernel: caam_jr 30902000.jr: 2000005b: CCB: desc idx 0: RNG: Hardware error
Mar 13 19:57:25 evergreen kernel: caam_jr 30902000.jr: 2000005b: CCB: desc idx 0: RNG: Hardware error
Mar 13 19:57:35 evergreen kernel: caam_jr 30902000.jr: 2000005b: CCB: desc idx 0: RNG: Hardware error
Mar 13 19:57:45 evergreen kernel: caam_jr 30902000.jr: 2000005b: CCB: desc idx 0: RNG: Hardware error
Mar 13 19:57:55 evergreen kernel: caam_jr 30902000.jr: 2000005b: CCB: desc idx 0: RNG: Hardware error
Mar 13 19:58:06 evergreen kernel: caam_jr 30902000.jr: 2000005b: CCB: desc idx 0: RNG: Hardware error
Mar 13 19:58:16 evergreen kernel: caam_jr 30902000.jr: 2000005b: CCB: desc idx 0: RNG: Hardware error
Mar 13 19:58:26 evergreen kernel: caam_jr 30902000.jr: 2000005b: CCB: desc idx 0: RNG: Hardware error
Mar 13 19:58:36 evergreen kernel: caam_jr 30902000.jr: 2000005b: CCB: desc idx 0: RNG: Hardware error
Mar 13 19:58:47 evergreen kernel: caam_jr 30902000.jr: 2000005b: CCB: desc idx 0: RNG: Hardware error
Mar 13 19:58:57 evergreen kernel: caam_jr 30902000.jr: 2000005b: CCB: desc idx 0: RNG: Hardware error
Mar 13 19:59:07 evergreen kernel: caam_jr 30902000.jr: 2000005b: CCB: desc idx 0: RNG: Hardware error
Mar 13 19:59:17 evergreen kernel: caam_jr 30902000.jr: 2000005b: CCB: desc idx 0: RNG: Hardware error
```
I believe this usually happens some short time after resume from system suspend and stays until a reboot.https://source.puri.sm/Librem5/linux/-/issues/466Attaching Viewsonic VX2453MH-LED via USB-C/HDMI-Adapter does not work2023-03-08T19:18:29ZBenedikt WildenhainAttaching Viewsonic VX2453MH-LED via USB-C/HDMI-Adapter does not workHi,
I am currently using a Librem 5 Evergreen and try to connect it to an external screen Viewsonic VX2453MH-LED. The screen is not always detected, but when it gets detected, I can see some edid data (only checked via cat, contained VX...Hi,
I am currently using a Librem 5 Evergreen and try to connect it to an external screen Viewsonic VX2453MH-LED. The screen is not always detected, but when it gets detected, I can see some edid data (only checked via cat, contained VX2453 Series, so obviously related to the screen) and modes got detected. However, I cannot get any output on the screen. I mainly tested via the adapter delivered together with the Pinephone (not Pro), but also tried the Digitus DA70882 docking station, both work fine with a Dell notebook.
I currently use stock PureOS with 6.1.0-1-librem5 kernel.
When executing `echo 0x2f > /sys/module/drm/parameters/debug` and connecting the screen, I get the attached output. Would it make sense to use the kernel currently in development? Or should I get the l5devkit and try whether it works there? [screen-connect-hdmi-viewsonic-VX2453-Series](/uploads/a9f37d9629deeba79bff497c146cc422/screen-connect-hdmi-viewsonic-VX2453-Series)https://source.puri.sm/Librem5/linux/-/issues/465Rx fifo overflow2023-02-18T12:15:15ZDorota CzaplejewiczRx fifo overflowWhile trying to reproduce https://source.puri.sm/Librem5/millipixels/-/issues/65, I got the fllowing in the kernel logs:
```
[ 4747.021919] imx7-csi 30b80000.csi: Rx fifo overflow
```
It repeats, and, after closing Millipixels, this ap...While trying to reproduce https://source.puri.sm/Librem5/millipixels/-/issues/65, I got the fllowing in the kernel logs:
```
[ 4747.021919] imx7-csi 30b80000.csi: Rx fifo overflow
```
It repeats, and, after closing Millipixels, this appeared:
```
[ 4964.999644] csi: wait last EOF timeout
```
The error starts again after launching Millipixels. Screen is black, nothing special in Millipixels logs that I could see.
Using gstreamer or cam with libcamera, it fails to (de)queue buffers:
```
DISPLAY=:0 WL_DISPLAY=:0 LIBCAMERA_LOG_LEVELS="*:0" GST_DEBUG="libcamera*:7" GST_PLUGIN_PATH=/home/purism/caminstall/lib/aarch64-linux-gnu/gstreamer-1.0/ LD_LIBRARY_PATH=/home/purism/caminstall/lib/aarch64-linux-gnu/ gst-launch-1.0 libcamerasrc camera-name="/base/soc\@0/bus\@30800000/i2c\@30a50000/camera\@2d" ! 'video/x-raw,format=BGRA,width=1052,height=780' ! glimagesink
[...]
[1:25:24.133553733] [4986] DEBUG V4L2 v4l2_videodevice.cpp:1690 /dev/video1[31:cap]: Queueing buffer 2
[1:25:24.133732062] [4986] DEBUG V4L2 v4l2_videodevice.cpp:1690 /dev/video1[31:cap]: Queueing buffer 3
[1:25:24.133819426] [4986] DEBUG V4L2 v4l2_videodevice.cpp:1690 /dev/video1[31:cap]: Queueing buffer 4
[1:25:24.133907750] [4986] DEBUG V4L2 v4l2_videodevice.cpp:1690 /dev/video1[31:cap]: Queueing buffer 5
```https://source.puri.sm/Librem5/linux/-/issues/4646.2-rc8: nullpointer deref on DP connection2023-02-22T20:37:01ZMartin Kepplinger6.2-rc8: nullpointer deref on DP connectionthis is just to remember that -rc8 broke DP out. This may or may not stem from a downstream patch.
```
[ 173.796697] Unable to handle kernel NULL pointer dereference at virtual address 0000000000000000
[ 173.806066] Mem abort info:
[ ...this is just to remember that -rc8 broke DP out. This may or may not stem from a downstream patch.
```
[ 173.796697] Unable to handle kernel NULL pointer dereference at virtual address 0000000000000000
[ 173.806066] Mem abort info:
[ 173.809072] ESR = 0x0000000096000004
[ 173.813131] EC = 0x25: DABT (current EL), IL = 32 bits
[ 173.819108] SET = 0, FnV = 0
[ 173.822791] EA = 0, S1PTW = 0
[ 173.826559] FSC = 0x04: level 0 translation fault
[ 173.832509] Data abort info:
[ 173.835959] ISV = 0, ISS = 0x00000004
[ 173.840599] CM = 0, WnR = 0
[ 173.844178] user pgtable: 4k pages, 48-bit VAs, pgdp=000000007c0e0000
[ 173.851119] [0000000000000000] pgd=0000000000000000, p4d=0000000000000000
[ 173.858509] Internal error: Oops: 0000000096000004 [#1] PREEMPT SMP
[ 173.864797] Modules linked in: r8153_ecm cdc_ether r8152 aes_ce_ccm bnep qmi_wwan option usb_wwan usbserial cdc_wdm usb_f_acm u_serial usb_f_ecm usbnet mii caam_jr u_ether mousedev caamhash_desc caamalg_desc crypto_engine redpine_sdio redpine_91x aes_ce_blk crct10dif_ce ghash_ce sha2_ce bluetooth sha1_ce mac80211 hantro_vpu st_lsm6dsx_spi v4l2_vp9 v4l2_h264 snd_soc_gtm601 st_magn_spi v4l2_mem2mem imx7_media_csi snd_soc_simple_card st_sensors_spi pwm_vibra cfg80211 snd_soc_simple_card_utils videobuf2_dma_contig videobuf2_memops videobuf2_v4l2 st_magn_i2c vcnl4000 st_lsm6dsx_i2c videobuf2_common st_magn st_sensors_i2c st_lsm6dsx st_sensors imx8mq_mipi_csi2(C) leds_lm3560 dw9714 hi846 s5k3l6xx industrialio_triggered_buffer v4l2_fwnode v4l2_flash_led_class kfifo_buf v4l2_async snd_soc_wm8962 snd_soc_fsl_sai snd_soc_fsl_utils videodev imx_pcm_dma mc gnss_mtk gnss_serial edt_ft5x06 gnss caam error snd_soc_core snd_pcm_dmaengine snd_pcm imx2_wdt snd_timer watchdog snd rfkill_hks soundcore
[ 173.865133] rfkill libcomposite ledtrig_timer ledtrig_pattern fuse zram ip_tables x_tables ipv6 uas usb_storage mtdblock mtd_blkdevs overlay ofpart xhci_plat_hcd xhci_hcd usbcore spi_nor mtd cdns_mhdp_imx cdns_mhdp_drmcore dwc3 ulpi udc_core imx_dcss usb_common drm_display_helper phy_fsl_imx8mq_usb bq25890_charger tps6598x typec roles clk_bd718x7 snvs_pwrkey imx_sdma virt_dma
[ 173.972684] imx-pgc imx-pgc-domain.5: failed to enable regulator: -ETIMEDOUT
[ 173.985556] CPU: 0 PID: 1953 Comm: ifquery Tainted: G C 6.2.0-rc8-librem5-00354-ga9dd668f7168 #42
[ 173.985568] Hardware name: Purism Librem 5r4 (DT)
[ 173.985573] pstate: 80000005 (Nzcv daif -PAN -UAO -TCO -DIT -SSBS BTYPE=--)
[ 173.985582] pc : __pi_strlen+0x14/0x150
Message from syslogd@pureos at Feb 14 16:51:16 ...
kernel:[ 173.858509] Internal error: Oops: 0000000096000004 [#1] PREEMPT SMP
[ 174.018378] lr : rtnl_fill_ifinfo+0xf38/0x126c
[ 174.022848] sp : ffff80000c09b4b0
[ 174.026178] x29: ffff80000c09b4b0 x28: ffff00004ccfc7cc x27: ffff00004ccfc000
[ 174.033329] x26: ffff00004ccfc000 x25: 0000000000000ae4 x24: 0000000000000000
[ 174.040478] x23: ffff00004ccfcae4 x22: ffff00004ccfc570 x21: 0000000000000000
[ 174.047624] x20: ffff00000b50a000 x19: ffff0000591cbb00 x18: 0000000000000000
[ 174.054773] x17: 0000000000000000 x16: 0000000000000000 x15: 0000000000000000
[ 174.061918] x14: 0000000000000000 x13: 0000000000000000 x12: 0000000000000000
[ 174.069063] x11: 0000000000000000 x10: 0000000000000001 x9 : ffff800008ad95b4
[ 174.076208] x8 : 0101010101010101 x7 : 0000000000000000 x6 : 0000000000000ec0
[ 174.083353] x5 : ffff00004ccfcae8 x4 : 0000000000000000 x3 : ffff00004ccfc000
[ 174.090498] x2 : 0000000000000000 x1 : 0000000000000ae4 x0 : 0000000000000000
[ 174.096631] ------------[ cut here ]------------
[ 174.097645] Call trace:
[ 174.097649] __pi_strlen+0x14/0x150
[ 174.102286] [CRTC:36:crtc-0] vblank wait timed out
[ 174.104709] rtnl_dump_ifinfo+0x29c/0x670
[ 174.104719] netlink_dump+0x124/0x324
[ 174.104731] __netlink_dump_start+0x178/0x330
[ 174.104741] rtnetlink_rcv_msg+0x260/0x3a0
Message from syslogd@pureos at Feb 14 16:51:16 ...
kernel:[ 174.205417] Code: 92402c04 b200c3e8 f13fc09f 5400088c (a9400c02)
[ 174.109552] WARNING: CPU: 1 PID: 81 at drivers/gpu/drm/drm_atomic_helper.c:1618 drm_atomic_helper_wait_for_vblanks.part.0+0x284/0x2ac
[ 174.113011] netlink_rcv_skb+0x64/0x150
[ 174.117016] Modules linked in:
[ 174.120672] rtnetlink_rcv+0x20/0x30
[ 174.125026] r8153_ecm
[ 174.129116] netlink_unicast+0x278/0x340
[ 174.141108] cdc_ether
[ 174.144939] netlink_sendmsg+0x1e0/0x450
[ 174.147991] r8152
[ 174.151559] sock_sendmsg+0x5c/0x70
[ 174.153914] aes_ce_ccm
[ 174.157832] __sys_sendto+0x120/0x14c
[ 174.160187] bnep
[ 174.164105] __arm64_sys_sendto+0x30/0x40
[ 174.166113] qmi_wwan
[ 174.169597] invoke_syscall+0x50/0x120
[ 174.172039] option
[ 174.175696] el0_svc_common.constprop.0+0xd4/0xf4
[ 174.177617] usb_wwan
[ 174.181622] do_el0_svc+0x24/0x30
[ 174.183891] usbserial
[ 174.187634] el0_svc+0x2c/0x84
[ 174.189729] cdc_wdm
[ 174.194428] el0t_64_sync_handler+0xb8/0xc0
[ 174.196699] usb_f_acm
[ 174.200006] el0t_64_sync+0x190/0x194
[ 174.202362] u_serial
[ 174.205417] Code: 92402c04 b200c3e8 f13fc09f 5400088c (a9400c02)
[ 174.207593] usb_f_ecm
[ 174.211775] ---[ end trace 0000000000000000 ]---
```https://source.puri.sm/Librem5/linux/-/issues/463wm8962: Errors on system suspend2023-02-10T01:43:13ZSebastian Krzyszkowiakwm8962: Errors on system suspendWhen the audio device is active (for example because runtime suspend hasn't yet kicked in after the last time a sound was played), this gets logged in dmesg on system suspend:
```
[ 654.238567] wm8962 2-001a: ASoC: error at soc_componen...When the audio device is active (for example because runtime suspend hasn't yet kicked in after the last time a sound was played), this gets logged in dmesg on system suspend:
```
[ 654.238567] wm8962 2-001a: ASoC: error at soc_component_read_no_lock on wm8962.2-001a for register: [0x00000004] -16
[ 654.238596] wm8962 2-001a: Failed to read DSPCLK: -16
[ 654.238651] wm8962 2-001a: Failed to resume device: -13
[ 654.238659] wm8962 2-001a: ASoC: POST_PMD: TEMP_SPK event failed: -13
```
Sometimes there's also a loud pop coming from the speaker.https://source.puri.sm/Librem5/linux/-/issues/462upowerd spamming syslog with on_battery state2023-01-24T09:06:15ZMartin Kepplingerupowerd spamming syslog with on_battery statethis is what's happening (whithin one second) when the phone is charging. Very similar logs are printed when the phone is discharging. This is printed to the INFO loglevel which is definitely a bug. The device is doing *nothing* and ever...this is what's happening (whithin one second) when the phone is charging. Very similar logs are printed when the phone is discharging. This is printed to the INFO loglevel which is definitely a bug. The device is doing *nothing* and everything works as expected. Can this point to a kernel bug?
```
Jän 23 10:30:41 pureos upowerd[770]: TI:10:30:41 on_battery = no
Jän 23 10:30:41 pureos upowerd[770]: TI:10:30:41 on_battery = no
Jän 23 10:30:41 pureos upowerd[770]: TI:10:30:41 on_battery = no
Jän 23 10:30:41 pureos upowerd[770]: TI:10:30:41 on_battery = no
Jän 23 10:30:41 pureos upowerd[770]: TI:10:30:41 on_battery = no
Jän 23 10:30:41 pureos upowerd[770]: TI:10:30:41 on_battery = no
Jän 23 10:30:41 pureos upowerd[770]: TI:10:30:41 on_battery = no
Jän 23 10:30:41 pureos upowerd[770]: TI:10:30:41 Setup poll for 'max170xx_battery' every 120 seconds
Jän 23 10:30:41 pureos upowerd[770]: TI:10:30:41 on_battery = no
Jän 23 10:30:41 pureos upowerd[770]: TI:10:30:41 on_battery = no
Jän 23 10:30:41 pureos upowerd[770]: TI:10:30:41 on_battery = no
Jän 23 10:30:41 pureos upowerd[770]: TI:10:30:41 Setup poll for 'max170xx_battery' every 120 seconds
Jän 23 10:30:41 pureos upowerd[770]: TI:10:30:41 on_battery = no
Jän 23 10:30:41 pureos upowerd[770]: TI:10:30:41 on_battery = no
Jän 23 10:30:41 pureos upowerd[770]: TI:10:30:41 on_battery = no
Jän 23 10:30:41 pureos upowerd[770]: TI:10:30:41 Setup poll for 'max170xx_battery' every 120 seconds
Jän 23 10:30:41 pureos upowerd[770]: TI:10:30:41 on_battery = no
Jän 23 10:30:41 pureos upowerd[770]: TI:10:30:41 on_battery = no
Jän 23 10:30:41 pureos upowerd[770]: TI:10:30:41 on_battery = no
Jän 23 10:30:41 pureos upowerd[770]: TI:10:30:41 using min design voltage
Jän 23 10:30:41 pureos upowerd[770]: TI:10:30:41 on_battery = no
Jän 23 10:30:41 pureos upowerd[770]: TI:10:30:41 on_battery = no
Jän 23 10:30:41 pureos upowerd[770]: TI:10:30:41 SYSFS change /sys/devices/platform/soc@0/30800000.bus/30a50000.i2c/i2c-3/3-0036/power_supply/max170xx_battery
Jän 23 10:30:41 pureos upowerd[770]: TI:10:30:41 on_battery = no
Jän 23 10:30:41 pureos upowerd[770]: TI:10:30:41 on_battery = no
Jän 23 10:30:41 pureos upowerd[770]: TI:10:30:41 on_battery = no
Jän 23 10:30:41 pureos upowerd[770]: TI:10:30:41 on_battery = no
Jän 23 10:30:41 pureos upowerd[770]: TI:10:30:41 on_battery = no
Jän 23 10:30:41 pureos upowerd[770]: TI:10:30:41 on_battery = no
Jän 23 10:30:41 pureos upowerd[770]: TI:10:30:41 on_battery = no
Jän 23 10:30:41 pureos upowerd[770]: TI:10:30:41 Setup poll for 'max170xx_battery' every 120 seconds
Jän 23 10:30:41 pureos upowerd[770]: TI:10:30:41 on_battery = no
Jän 23 10:30:41 pureos upowerd[770]: TI:10:30:41 on_battery = no
Jän 23 10:30:41 pureos upowerd[770]: TI:10:30:41 on_battery = no
Jän 23 10:30:41 pureos upowerd[770]: TI:10:30:41 Setup poll for 'max170xx_battery' every 120 seconds
Jän 23 10:30:41 pureos upowerd[770]: TI:10:30:41 on_battery = no
Jän 23 10:30:41 pureos upowerd[770]: TI:10:30:41 on_battery = no
Jän 23 10:30:41 pureos upowerd[770]: TI:10:30:41 on_battery = no
Jän 23 10:30:41 pureos upowerd[770]: TI:10:30:41 Setup poll for 'max170xx_battery' every 120 seconds
Jän 23 10:30:41 pureos upowerd[770]: TI:10:30:41 on_battery = no
Jän 23 10:30:41 pureos upowerd[770]: TI:10:30:41 on_battery = no
Jän 23 10:30:41 pureos upowerd[770]: TI:10:30:41 on_battery = no
Jän 23 10:30:41 pureos upowerd[770]: TI:10:30:41 using min design voltage
Jän 23 10:30:41 pureos upowerd[770]: TI:10:30:41 on_battery = no
Jän 23 10:30:41 pureos upowerd[770]: TI:10:30:41 on_battery = no
Jän 23 10:30:41 pureos upowerd[770]: TI:10:30:41 SYSFS change /sys/devices/platform/soc@0/30800000.bus/30a50000.i2c/i2c-3/3-0036/power_supply/max170xx_battery
Jän 23 10:30:41 pureos upowerd[770]: TI:10:30:41 on_battery = no
Jän 23 10:30:41 pureos upowerd[770]: TI:10:30:41 deferring as others queued
Jän 23 10:30:41 pureos upowerd[770]: TI:10:30:41 deferring as others queued
Jän 23 10:30:41 pureos upowerd[770]: TI:10:30:41 saving in 600 seconds
Jän 23 10:30:41 pureos upowerd[770]: TI:10:30:41 on_battery = no
Jän 23 10:30:41 pureos upowerd[770]: TI:10:30:41 on_battery = no
Jän 23 10:30:41 pureos upowerd[770]: TI:10:30:41 on_battery = no
Jän 23 10:30:41 pureos upowerd[770]: TI:10:30:41 on_battery = no
Jän 23 10:30:41 pureos upowerd[770]: TI:10:30:41 on_battery = no
Jän 23 10:30:41 pureos upowerd[770]: TI:10:30:41 on_battery = no
Jän 23 10:30:41 pureos upowerd[770]: TI:10:30:41 Setup poll for 'max170xx_battery' every 120 seconds
Jän 23 10:30:41 pureos upowerd[770]: TI:10:30:41 on_battery = no
Jän 23 10:30:41 pureos upowerd[770]: TI:10:30:41 on_battery = no
Jän 23 10:30:41 pureos upowerd[770]: TI:10:30:41 on_battery = no
Jän 23 10:30:41 pureos upowerd[770]: TI:10:30:41 Setup poll for 'max170xx_battery' every 120 seconds
Jän 23 10:30:41 pureos upowerd[770]: TI:10:30:41 on_battery = no
Jän 23 10:30:41 pureos upowerd[770]: TI:10:30:41 on_battery = no
Jän 23 10:30:41 pureos upowerd[770]: TI:10:30:41 on_battery = no
Jän 23 10:30:41 pureos upowerd[770]: TI:10:30:41 Setup poll for 'max170xx_battery' every 120 seconds
Jän 23 10:30:41 pureos upowerd[770]: TI:10:30:41 on_battery = no
Jän 23 10:30:41 pureos upowerd[770]: TI:10:30:41 on_battery = no
Jän 23 10:30:41 pureos upowerd[770]: TI:10:30:41 on_battery = no
Jän 23 10:30:41 pureos upowerd[770]: TI:10:30:41 using min design voltage
Jän 23 10:30:41 pureos upowerd[770]: TI:10:30:41 on_battery = no
Jän 23 10:30:41 pureos upowerd[770]: TI:10:30:41 on_battery = no
Jän 23 10:30:41 pureos upowerd[770]: TI:10:30:41 SYSFS change /sys/devices/platform/soc@0/30800000.bus/30a50000.i2c/i2c-3/3-0036/power_supply/max170xx_battery
```https://source.puri.sm/Librem5/linux/-/issues/461USB port of GSM modem repeatedly suspended/resumed while phonecall is ongoing2023-03-08T00:07:55ZElias RudbergUSB port of GSM modem repeatedly suspended/resumed while phonecall is ongoingThis came up while trying different things related to modem "runtime suspend", related to https://source.puri.sm/Librem5/linux/-/issues/303
Using the current pureos/byzantium branch with the following dev_info() calls added in order to ...This came up while trying different things related to modem "runtime suspend", related to https://source.puri.sm/Librem5/linux/-/issues/303
Using the current pureos/byzantium branch with the following dev_info() calls added in order to see when runtime suspend/resume happens:
dev_info(&intf->dev, "This is qmi_wwan_suspend()\n");
dev_info(&intf->dev, "This is qmi_wwan_resume()\n");
dev_info(&udev->dev, "This is usb_port_suspend()\n");
dev_info(&udev->dev, "This is usb_port_resume()\n");
Those calls were added in the following places in the code, in drivers/net/usb/qmi_wwan.c and drivers/usb/core/hub.c:
```
diff --git a/drivers/net/usb/qmi_wwan.c b/drivers/net/usb/qmi_wwan.c
index 554d4e2a84a4..14885e055447 100644
--- a/drivers/net/usb/qmi_wwan.c
+++ b/drivers/net/usb/qmi_wwan.c
@@ -889,6 +889,7 @@ static int qmi_wwan_suspend(struct usb_interface *intf, pm_message_t message)
struct usbnet *dev = usb_get_intfdata(intf);
struct qmi_wwan_state *info = (void *)&dev->data;
int ret;
+ dev_info(&intf->dev, "This is qmi_wwan_suspend()\n");
/* Both usbnet_suspend() and subdriver->suspend() MUST return 0
* in system sleep context, otherwise, the resume callback has
@@ -911,6 +912,7 @@ static int qmi_wwan_resume(struct usb_interface *intf)
{
struct usbnet *dev = usb_get_intfdata(intf);
struct qmi_wwan_state *info = (void *)&dev->data;
+ dev_info(&intf->dev, "This is qmi_wwan_resume()\n");
int ret = 0;
bool callsub = (intf == info->control && info->subdriver &&
info->subdriver->resume);
diff --git a/drivers/usb/core/hub.c b/drivers/usb/core/hub.c
index 4c31872321ea..bda1b7ddaeeb 100644
--- a/drivers/usb/core/hub.c
+++ b/drivers/usb/core/hub.c
@@ -3364,6 +3364,7 @@ int usb_port_suspend(struct usb_device *udev, pm_message_t msg)
int port1 = udev->portnum;
int status;
bool really_suspend = true;
+ dev_info(&udev->dev, "This is usb_port_suspend()\n");
usb_lock_port(port_dev);
@@ -3656,6 +3657,7 @@ int usb_port_resume(struct usb_device *udev, pm_message_t msg)
int port1 = udev->portnum;
int status;
u16 portchange, portstatus;
+ dev_info(&udev->dev, "This is usb_port_resume()\n");
if (!test_and_set_bit(port1, hub->child_usage_bits)) {
status = pm_runtime_resume_and_get(&port_dev->dev);
```
So only those calls for extra logging, nothing else changed. With those changes, journalctl shows log messages each time those suspend and resume functions are called.
To my surprise, when a phonecall is ongoing, suspend and resume calls still happen, during the phonecall.
Example:
```
Jan 22 16:41:44 pureos ModemManager[804]: <info> [modem0/call0] call state changed: unknown -> ringing-in (incoming-new)
Jan 22 16:41:44 pureos gsd-color[1545]: unable to get EDID for xrandr-DSI-1: unable to get EDID for output
Jan 22 16:41:44 pureos pulseaudio[858]: ALSA woke us up to write new data to the device, but there was actually nothing to write.
Jan 22 16:41:44 pureos pulseaudio[858]: Most likely this is a bug in the ALSA driver 'snd_soc_simple_card'. Please report this issue to the ALSA developers.
Jan 22 16:41:44 pureos pulseaudio[858]: We were woken up with POLLOUT set -- however a subsequent snd_pcm_avail() returned 0 or another value < min_avail.
Jan 22 16:41:45 pureos phosh[2652]: The XKEYBOARD keymap compiler (xkbcomp) reports:
Jan 22 16:41:45 pureos phosh[2652]: > Warning: Unsupported maximum keycode 569, clipping.
Jan 22 16:41:45 pureos phosh[2652]: > X11 cannot support keycodes above 255.
Jan 22 16:41:45 pureos phosh[2652]: Errors from xkbcomp are not fatal to the X server
Jan 22 16:41:46 pureos kernel: qmi_wwan 1-1.2:1.4: This is qmi_wwan_suspend()
Jan 22 16:41:46 pureos kernel: usb 1-1.2: This is usb_port_suspend()
Jan 22 16:41:46 pureos kernel: usb 1-1: This is usb_port_suspend()
Jan 22 16:41:48 pureos ModemManager[804]: <info> [modem0/call0] user request to accept call
Jan 22 16:41:48 pureos kernel: usb 1-1: This is usb_port_resume()
Jan 22 16:41:48 pureos kernel: usb 1-1.2: This is usb_port_resume()
Jan 22 16:41:48 pureos kernel: qmi_wwan 1-1.2:1.4: This is qmi_wwan_resume()
Jan 22 16:41:48 pureos ModemManager[804]: <info> [modem0/call0] call is accepted
Jan 22 16:41:48 pureos ModemManager[804]: <info> [modem0/call0] call state changed: ringing-in -> active (accepted)
Jan 22 16:41:48 pureos pulseaudio[858]: Configured maximum latency is smaller than latency, using latency instead
Jan 22 16:41:48 pureos pulseaudio[858]: Cannot set requested sink latency of 66.67 ms, adjusting to 32.00 ms
Jan 22 16:41:48 pureos pulseaudio[858]: Cannot set requested source latency of 66.67 ms, adjusting to 32.00 ms
Jan 22 16:41:48 pureos pulseaudio[858]: Configured maximum latency is smaller than latency, using latency instead
Jan 22 16:41:48 pureos pulseaudio[858]: Cannot set requested sink latency of 66.67 ms, adjusting to 32.00 ms
Jan 22 16:41:48 pureos pulseaudio[858]: Cannot set requested source latency of 66.67 ms, adjusting to 32.00 ms
Jan 22 16:41:48 pureos pulseaudio[858]: Cannot set requested source latency of 66.67 ms, adjusting to 32.00 ms
Jan 22 16:41:48 pureos pulseaudio[858]: Cannot set requested sink latency of 66.67 ms, adjusting to 32.00 ms
Jan 22 16:41:48 pureos pulseaudio[858]: Doing resync
Jan 22 16:41:48 pureos pulseaudio[858]: Playback after capture (-14192), drop sink 5528
Jan 22 16:41:48 pureos pulseaudio[858]: ALSA woke us up to read new data from the device, but there was actually nothing to read.
Jan 22 16:41:48 pureos pulseaudio[858]: Most likely this is a bug in the ALSA driver 'snd_soc_simple_card'. Please report this issue to the ALSA developers.
Jan 22 16:41:48 pureos pulseaudio[858]: We were woken up with POLLIN set -- however a subsequent snd_pcm_avail() returned 0 or another value < min_avail.
Jan 22 16:41:48 pureos pulseaudio[858]: Doing resync
Jan 22 16:41:48 pureos pulseaudio[858]: Playback too far ahead (466), drop source 88
Jan 22 16:41:49 pureos pulseaudio[858]: Playback too far ahead (17501), drop source 3360
Jan 22 16:41:50 pureos kernel: qmi_wwan 1-1.2:1.4: This is qmi_wwan_suspend()
Jan 22 16:41:50 pureos kernel: usb 1-1.2: This is usb_port_suspend()
Jan 22 16:41:50 pureos pulseaudio[858]: Playback too far ahead (34308), drop source 6584
Jan 22 16:41:50 pureos kernel: usb 1-1: This is usb_port_suspend()
Jan 22 16:41:51 pureos pulseaudio[858]: Playback too far ahead (10116), drop source 1940
Jan 22 16:41:52 pureos pulseaudio[858]: Playback too far ahead (8912), drop source 1708
Jan 22 16:41:53 pureos pulseaudio[858]: Playback too far ahead (8914), drop source 1708
Jan 22 16:41:54 pureos pulseaudio[858]: Playback too far ahead (8500), drop source 1632
Jan 22 16:41:55 pureos kernel: usb 1-1: This is usb_port_resume()
Jan 22 16:41:55 pureos pulseaudio[858]: Playback too far ahead (9232), drop source 1772
Jan 22 16:41:55 pureos kernel: usb 1-1.2: This is usb_port_resume()
Jan 22 16:41:55 pureos kernel: qmi_wwan 1-1.2:1.4: This is qmi_wwan_resume()
Jan 22 16:41:56 pureos pulseaudio[858]: Playback too far ahead (7723), drop source 1480
Jan 22 16:41:57 pureos pulseaudio[858]: Playback too far ahead (6893), drop source 1320
Jan 22 16:41:57 pureos kernel: qmi_wwan 1-1.2:1.4: This is qmi_wwan_suspend()
Jan 22 16:41:57 pureos kernel: usb 1-1.2: This is usb_port_suspend()
Jan 22 16:41:58 pureos kernel: usb 1-1: This is usb_port_suspend()
Jan 22 16:41:58 pureos pulseaudio[858]: Playback too far ahead (6015), drop source 1152
Jan 22 16:41:59 pureos pulseaudio[858]: Playback too far ahead (8041), drop source 1540
Jan 22 16:42:00 pureos pulseaudio[858]: Playback too far ahead (9883), drop source 1896
Jan 22 16:42:01 pureos kernel: usb 1-1: This is usb_port_resume()
Jan 22 16:42:01 pureos pulseaudio[858]: Playback too far ahead (10297), drop source 1976
Jan 22 16:42:01 pureos kernel: usb 1-1.2: This is usb_port_resume()
Jan 22 16:42:01 pureos kernel: qmi_wwan 1-1.2:1.4: This is qmi_wwan_resume()
Jan 22 16:42:02 pureos pulseaudio[858]: Playback too far ahead (9963), drop source 1912
Jan 22 16:42:03 pureos pulseaudio[858]: Playback too far ahead (9986), drop source 1916
Jan 22 16:42:03 pureos kernel: qmi_wwan 1-1.2:1.4: This is qmi_wwan_suspend()
Jan 22 16:42:03 pureos kernel: usb 1-1.2: This is usb_port_suspend()
Jan 22 16:42:04 pureos kernel: usb 1-1: This is usb_port_suspend()
Jan 22 16:42:04 pureos pulseaudio[858]: Playback too far ahead (10255), drop source 1968
Jan 22 16:42:05 pureos pulseaudio[858]: Playback too far ahead (10031), drop source 1924
Jan 22 16:42:06 pureos pulseaudio[858]: Playback too far ahead (9927), drop source 1904
Jan 22 16:42:07 pureos pulseaudio[858]: Playback too far ahead (10170), drop source 1952
Jan 22 16:42:08 pureos pulseaudio[858]: Playback too far ahead (9819), drop source 1884
Jan 22 16:42:09 pureos pulseaudio[858]: Playback too far ahead (9690), drop source 1860
Jan 22 16:42:10 pureos pulseaudio[858]: Playback too far ahead (9979), drop source 1912
Jan 22 16:42:11 pureos pulseaudio[858]: Playback too far ahead (9768), drop source 1872
Jan 22 16:42:12 pureos pulseaudio[858]: Playback too far ahead (10451), drop source 2004
Jan 22 16:42:13 pureos pulseaudio[858]: Playback too far ahead (9863), drop source 1892
Jan 22 16:42:14 pureos pulseaudio[858]: Playback too far ahead (9876), drop source 1896
Jan 22 16:42:15 pureos pulseaudio[858]: Playback too far ahead (10086), drop source 1936
Jan 22 16:42:16 pureos pulseaudio[858]: Playback too far ahead (10003), drop source 1920
Jan 22 16:42:18 pureos pulseaudio[858]: Playback after capture (-55), drop sink 96
Jan 22 16:42:26 pureos kernel: usb 1-1: This is usb_port_resume()
Jan 22 16:42:27 pureos kernel: usb 1-1.2: This is usb_port_resume()
Jan 22 16:42:27 pureos kernel: qmi_wwan 1-1.2:1.4: This is qmi_wwan_resume()
[...]
[... many more suspend/resume calls ... ]
[...]
Jan 22 16:43:28 pureos ModemManager[804]: <info> [modem0/call0] user request to hangup call
Jan 22 16:43:28 pureos ModemManager[804]: <info> [modem0/call0] call state changed: active -> terminated (terminated)
```
In the above example, a phonecall started at 16:41:48 and while that call was ongoing there were many suspend/resume calls for the USB port called "usb 1-1.2" which is the modem's port. This does not seem right to me, I was expecting the modem to suspend only when not in use.
It looks like sometimes there are several seconds between usb_port_suspend() and usb_port_resume(), but somehow the phonecall was still active during that time and phonecall audio was heard so I guess the modem must have been active even though the USB port was suspended.
Is it okay for the modem's USB port to be suspended while a phonecall is ongoing?
Is the phonecall audio data not dependent on the USB port, the modem communicates through some other channel for that?
Could phonecall audio quality issues like https://source.puri.sm/Librem5/OS-issues/-/issues/312 be related to these suspend/resume operations happening during phonecalls?
(I tested also what happens while downloading a large file using `wget` using the mobile data connection, then is seemed the runtime suspend functions were never called while that download was ongoing. That seems reasonable, the modem was used during that time and then the kernel did not try to suspend it while it was used.)
According to https://www.kernel.org/doc/html/v4.16/driver-api/usb/power-management.html drivers that support autosuspend (which I guess the L5 modem's driver claims to do) should call some functions `usb_autopm_get_...()` and `usb_autopm_put_...()` and maybe also `usb_mark_last_busy()` to tell the kernel power management core about the device's activity so that the kernel will not try to suspend a device while it is active, could it be that something like that is missing?https://source.puri.sm/Librem5/linux/-/issues/460qmi_wwan 1-1.2:1.4: nonzero urb status received: -712023-01-26T08:00:19ZMartin Kepplingerqmi_wwan 1-1.2:1.4: nonzero urb status received: -71this happens while having the modem USB runtime PM disabled like so: https://source.puri.sm/Librem5/linux/-/issues/303#note_224564
this happened "randomly" while listening to music:
```
Jän 20 09:03:35.823265 pureos kernel: qmi_wwan 1-...this happens while having the modem USB runtime PM disabled like so: https://source.puri.sm/Librem5/linux/-/issues/303#note_224564
this happened "randomly" while listening to music:
```
Jän 20 09:03:35.823265 pureos kernel: qmi_wwan 1-1.2:1.4: nonzero urb status received: -71
Jän 20 09:03:35.884851 pureos kernel: qmi_wwan 1-1.2:1.4: wdm_int_callback - 0 bytes
Jän 20 09:03:35.920821 pureos kernel: qmi_wwan 1-1.2:1.4: nonzero urb status received: -71
Jän 20 09:03:35.930083 pureos kernel: qmi_wwan 1-1.2:1.4: wdm_int_callback - 0 bytes
Jän 20 09:03:35.937961 pureos kernel: qmi_wwan 1-1.2:1.4: nonzero urb status received: -71
Jän 20 09:03:35.942603 pureos kernel: qmi_wwan 1-1.2:1.4: wdm_int_callback - 0 bytes
Jän 20 09:03:35.945722 pureos kernel: qmi_wwan 1-1.2:1.4: nonzero urb status received: -71
Jän 20 09:03:35.947972 pureos kernel: qmi_wwan 1-1.2:1.4: wdm_int_callback - 0 bytes
Jän 20 09:03:35.949784 pureos kernel: qmi_wwan 1-1.2:1.4: nonzero urb status received: -71
Jän 20 09:03:35.951163 pureos kernel: qmi_wwan 1-1.2:1.4: wdm_int_callback - 0 bytes
Jän 20 09:03:35.952775 pureos kernel: qmi_wwan 1-1.2:1.4: nonzero urb status received: -71
Jän 20 09:03:35.954615 pureos kernel: qmi_wwan 1-1.2:1.4: wdm_int_callback - 0 bytes
Jän 20 09:03:35.995878 pureos kernel: qmi_wwan 1-1.2:1.4: nonzero urb status received: -71
Jän 20 09:03:36.003953 pureos kernel: qmi_wwan 1-1.2:1.4: wdm_int_callback - 0 bytes
Jän 20 09:03:36.007911 pureos kernel: qmi_wwan 1-1.2:1.4: nonzero urb status received: -71
Jän 20 09:03:36.010340 pureos kernel: qmi_wwan 1-1.2:1.4: wdm_int_callback - 0 bytes
Jän 20 09:03:36.011727 pureos kernel: qmi_wwan 1-1.2:1.4: nonzero urb status received: -71
Jän 20 09:03:36.013182 pureos kernel: qmi_wwan 1-1.2:1.4: wdm_int_callback - 0 bytes
Jän 20 09:03:36.014363 pureos kernel: qmi_wwan 1-1.2:1.4: nonzero urb status received: -71
Jän 20 09:03:36.015512 pureos kernel: qmi_wwan 1-1.2:1.4: wdm_int_callback - 0 bytes
Jän 20 09:03:36.016839 pureos kernel: qmi_wwan 1-1.2:1.4: nonzero urb status received: -71
Jän 20 09:03:36.018564 pureos kernel: qmi_wwan 1-1.2:1.4: wdm_int_callback - 0 bytes
Jän 20 09:03:36.022253 pureos kernel: usb 1-1.2: USB disconnect, device number 7
Jän 20 09:03:36.057074 pureos kernel: qmi_wwan 1-1.2:1.4: nonzero urb status received: -71
Jän 20 09:03:36.130129 pureos kernel: qmi_wwan 1-1.2:1.4: wdm_int_callback - 0 bytes
Jän 20 09:03:36.156751 pureos kernel: qmi_wwan 1-1.2:1.4: wdm_int_callback - usb_submit_urb failed with result -19
Jän 20 09:03:36.188478 pureos kernel: option1 ttyUSB0: GSM modem (1-port) converter now disconnected from ttyUSB0
Jän 20 09:03:36.268401 pureos kernel: option 1-1.2:1.0: device disconnected
Jän 20 09:03:36.294712 pureos kernel: option1 ttyUSB1: GSM modem (1-port) converter now disconnected from ttyUSB1
Jän 20 09:03:36.316568 pureos kernel: option 1-1.2:1.1: device disconnected
Jän 20 09:03:36.359635 pureos kernel: option1 ttyUSB2: GSM modem (1-port) converter now disconnected from ttyUSB2
Jän 20 09:03:36.380261 pureos kernel: option 1-1.2:1.2: device disconnected
Jän 20 09:03:36.410444 pureos kernel: option1 ttyUSB3: GSM modem (1-port) converter now disconnected from ttyUSB3
Jän 20 09:03:36.458283 pureos kernel: option 1-1.2:1.3: device disconnected
Jän 20 09:03:36.486098 pureos kernel: qmi_wwan 1-1.2:1.4 wwan0: unregister 'qmi_wwan' usb-xhci-hcd.4.auto-1.2, WWAN/QMI device
Jän 20 09:03:36.230207 pureos systemd-networkd[318]: wwan0: Link DOWN
Jän 20 09:03:36.351641 pureos ModemManager[5679]: Cannot read from istream: connection broken
Jän 20 09:03:36.230984 pureos systemd-networkd[318]: wwan0: Lost carrier
Jän 20 09:03:36.352121 pureos ModemManager[5679]: [/dev/cdc-wdm0] QMI endpoint hangup: removed
Jän 20 09:03:36.251002 pureos systemd-timesyncd[391]: No network connectivity, watching for changes.
Jän 20 09:03:36.352486 pureos ModemManager[5679]: <info> [modem3] connection to qmi-proxy for /dev/cdc-wdm0 lost, reprobing
Jän 20 09:03:36.470341 pureos usbguard-daemon[512]: uid=0 pid=492 result='SUCCESS' device.rule='allow id 2020:2060 serial "" name "Qualcomm CDMA Technologies MSM" hash "1E5MUAqBN4Iq7aIBy9C66mfhsybxqVMgqb0Zo2g0v>
Jän 20 09:03:36.478177 pureos ModemManager[5679]: [/dev/cdc-wdm0] Releasing 'wds' client with flags 'release-cid'...
Jän 20 09:03:36.657114 pureos mmsdtng[640]: ../plugins/modemmanager.c:mmsd_modem_unavailable() Disabling Bearer Handler
Jän 20 09:03:36.479015 pureos ModemManager[5679]: [/dev/cdc-wdm0] Unregistered 'wds' client with ID '3'
Jän 20 09:03:36.657142 pureos mmsdtng[640]: ../src/service.c:mms_service_set_bearer_handler() service 0xaaab00a1bcc0 handler (nil)
Jän 20 09:03:36.501997 pureos ModemManager[5679]: [/dev/cdc-wdm0] Releasing 'wds' client with flags 'release-cid'...
Jän 20 09:03:36.657159 pureos mmsdtng[640]: ../plugins/modemmanager.c:mmsd_disconnect_from_sms_wap() Stopping watching SMS WAPs
Jän 20 09:03:36.502512 pureos ModemManager[5679]: [/dev/cdc-wdm0] Unregistered 'wds' client with ID '2'
Jän 20 09:03:36.657372 pureos NetworkManager[434]: <info> [1674201816.6573] device (cdc-wdm0): state change: activated -> unmanaged (reason 'removed', sys-iface-state: 'removed')
Jän 20 09:03:36.531497 pureos ModemManager[5679]: [/dev/cdc-wdm0] Releasing 'voice' client with flags 'release-cid'...
Jän 20 09:03:36.657630 pureos mmsdtng[640]: ../plugins/modemmanager.c:mmsd_mm_state() Modem vanished, Disabling plugin
Jän 20 09:03:36.532306 pureos ModemManager[5679]: [/dev/cdc-wdm0] Unregistered 'voice' client with ID '1'
Jän 20 09:03:36.657647 pureos mmsdtng[640]: ../plugins/modemmanager.c:mmsd_mm_state() MMSD_MM_STATE_NO_MODEM
Jän 20 09:03:36.536389 pureos ModemManager[5679]: [/dev/cdc-wdm0] Releasing 'pdc' client with flags 'release-cid'...
Jän 20 09:03:36.657667 pureos mmsdtng[640]: ../plugins/modemmanager.c:cb_object_removed() Modem removed: /org/freedesktop/ModemManager1/Modem/3
Jän 20 09:03:36.565727 pureos ModemManager[5679]: [/dev/cdc-wdm0] Unregistered 'pdc' client with ID '1'
Jän 20 09:03:36.675769 pureos NetworkManager[434]: <info> [1674201816.6756] manager: NetworkManager state is now DISCONNECTED
Jän 20 09:03:36.609298 pureos ModemManager[5679]: [/dev/cdc-wdm0] Releasing 'loc' client with flags 'release-cid'...
Jän 20 09:03:36.612271 pureos ModemManager[5679]: [/dev/cdc-wdm0] Unregistered 'loc' client with ID '1'
Jän 20 09:03:36.630948 pureos ModemManager[5679]: [/dev/cdc-wdm0] Releasing 'uim' client with flags 'release-cid'...
Jän 20 09:03:36.631427 pureos ModemManager[5679]: [/dev/cdc-wdm0] Unregistered 'uim' client with ID '1'
Jän 20 09:03:36.633812 pureos ModemManager[5679]: [/dev/cdc-wdm0] Releasing 'wms' client with flags 'release-cid'...
Jän 20 09:03:36.633976 pureos ModemManager[5679]: [/dev/cdc-wdm0] Unregistered 'wms' client with ID '1'
Jän 20 09:03:36.634465 pureos ModemManager[5679]: [/dev/cdc-wdm0] Releasing 'wds' client with flags 'release-cid'...
Jän 20 09:03:36.634611 pureos ModemManager[5679]: [/dev/cdc-wdm0] Unregistered 'wds' client with ID '1'
Jän 20 09:03:36.634940 pureos ModemManager[5679]: [/dev/cdc-wdm0] Releasing 'nas' client with flags 'release-cid'...
Jän 20 09:03:36.635064 pureos ModemManager[5679]: [/dev/cdc-wdm0] Unregistered 'nas' client with ID '1'
Jän 20 09:03:36.635383 pureos ModemManager[5679]: [/dev/cdc-wdm0] Releasing 'dms' client with flags 'release-cid'...
Jän 20 09:03:36.635486 pureos ModemManager[5679]: [/dev/cdc-wdm0] Unregistered 'dms' client with ID '1'
Jän 20 09:03:36.657708 pureos ModemManager[5679]: <info> [base-manager] port ttyUSB1 released by device '/sys/devices/platform/soc@0/38200000.usb/xhci-hcd.4.auto/usb1/1-1/1-1.2'
Jän 20 09:03:36.664122 pureos ModemManager[5679]: <info> [base-manager] port ttyUSB0 released by device '/sys/devices/platform/soc@0/38200000.usb/xhci-hcd.4.auto/usb1/1-1/1-1.2'
Jän 20 09:03:36.683869 pureos ModemManager[5679]: <info> [base-manager] port ttyUSB2 released by device '/sys/devices/platform/soc@0/38200000.usb/xhci-hcd.4.auto/usb1/1-1/1-1.2'
Jän 20 09:03:36.687919 pureos ModemManager[5679]: <info> [base-manager] port ttyUSB3 released by device '/sys/devices/platform/soc@0/38200000.usb/xhci-hcd.4.auto/usb1/1-1/1-1.2'
Jän 20 09:03:36.734352 pureos upowerd[733]: TI:09:03:36 unhandled action 'unbind' on /sys/devices/platform/soc@0/38200000.usb/xhci-hcd.4.auto/usb1/1-1/1-1.2/1-1.2:1.3
Jän 20 09:03:36.740886 pureos upowerd[733]: TI:09:03:36 SYSFS remove /sys/devices/platform/soc@0/38200000.usb/xhci-hcd.4.auto/usb1/1-1/1-1.2/1-1.2:1.3
Jän 20 09:03:36.740886 pureos upowerd[733]: TI:09:03:36 ignoring remove event on /sys/devices/platform/soc@0/38200000.usb/xhci-hcd.4.auto/usb1/1-1/1-1.2/1-1.2:1.3
Jän 20 09:03:36.743625 pureos upowerd[733]: TI:09:03:36 SYSFS remove /sys/devices/platform/soc@0/38200000.usb/xhci-hcd.4.auto/usb1/1-1/1-1.2/1-1.2:1.4/usbmisc/cdc-wdm0
Jän 20 09:03:36.743625 pureos upowerd[733]: TI:09:03:36 ignoring remove event on /sys/devices/platform/soc@0/38200000.usb/xhci-hcd.4.auto/usb1/1-1/1-1.2/1-1.2:1.4/usbmisc/cdc-wdm0
Jän 20 09:03:36.743625 pureos upowerd[733]: TI:09:03:36 unhandled action 'unbind' on /sys/devices/platform/soc@0/38200000.usb/xhci-hcd.4.auto/usb1/1-1/1-1.2/1-1.2:1.2
Jän 20 09:03:36.742844 pureos ModemManager[5679]: <info> [base-manager] port cdc-wdm0 released by device '/sys/devices/platform/soc@0/38200000.usb/xhci-hcd.4.auto/usb1/1-1/1-1.2'
Jän 20 09:03:36.752056 pureos upowerd[733]: TI:09:03:36 unhandled action 'unbind' on /sys/devices/platform/soc@0/38200000.usb/xhci-hcd.4.auto/usb1/1-1/1-1.2/1-1.2:1.1
Jän 20 09:03:36.752056 pureos upowerd[733]: TI:09:03:36 unhandled action 'unbind' on /sys/devices/platform/soc@0/38200000.usb/xhci-hcd.4.auto/usb1/1-1/1-1.2/1-1.2:1.0
Jän 20 09:03:36.758865 pureos ModemManager[5679]: <info> [base-manager] port wwan0 released by device '/sys/devices/platform/soc@0/38200000.usb/xhci-hcd.4.auto/usb1/1-1/1-1.2'
Jän 20 09:03:36.759559 pureos NetworkManager[434]: <warn> [1674201816.7595] dns-sd-resolved[becf0d6c4ee70155]: send-updates SetLinkDomains@7 failed: GDBus.Error:org.freedesktop.resolve1.NoSuchLink: Link 7 not >
Jän 20 09:03:36.768894 pureos upowerd[733]: TI:09:03:36 unhandled action 'unbind' on /sys/devices/platform/soc@0/38200000.usb/xhci-hcd.4.auto/usb1/1-1/1-1.2/1-1.2:1.4
Jän 20 09:03:36.770385 pureos upowerd[733]: TI:09:03:36 SYSFS remove /sys/devices/platform/soc@0/38200000.usb/xhci-hcd.4.auto/usb1/1-1/1-1.2/1-1.2:1.1
Jän 20 09:03:36.770385 pureos upowerd[733]: TI:09:03:36 ignoring remove event on /sys/devices/platform/soc@0/38200000.usb/xhci-hcd.4.auto/usb1/1-1/1-1.2/1-1.2:1.1
Jän 20 09:03:36.776576 pureos upowerd[733]: TI:09:03:36 SYSFS remove /sys/devices/platform/soc@0/38200000.usb/xhci-hcd.4.auto/usb1/1-1/1-1.2/1-1.2:1.4
Jän 20 09:03:36.776576 pureos upowerd[733]: TI:09:03:36 ignoring remove event on /sys/devices/platform/soc@0/38200000.usb/xhci-hcd.4.auto/usb1/1-1/1-1.2/1-1.2:1.4
Jän 20 09:03:36.807196 pureos dbus-daemon[432]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.9' (uid=0 pid=434>
Jän 20 09:03:36.808526 pureos upowerd[733]: TI:09:03:36 SYSFS remove /sys/devices/platform/soc@0/38200000.usb/xhci-hcd.4.auto/usb1/1-1/1-1.2/1-1.2:1.0
Jän 20 09:03:36.808526 pureos upowerd[733]: TI:09:03:36 ignoring remove event on /sys/devices/platform/soc@0/38200000.usb/xhci-hcd.4.auto/usb1/1-1/1-1.2/1-1.2:1.0
Jän 20 09:03:36.819423 pureos upowerd[733]: TI:09:03:36 SYSFS remove /sys/devices/platform/soc@0/38200000.usb/xhci-hcd.4.auto/usb1/1-1/1-1.2/1-1.2:1.2
Jän 20 09:03:36.819423 pureos upowerd[733]: TI:09:03:36 ignoring remove event on /sys/devices/platform/soc@0/38200000.usb/xhci-hcd.4.auto/usb1/1-1/1-1.2/1-1.2:1.2
Jän 20 09:03:36.827300 pureos NetworkManager[434]: <warn> [1674201816.8272] modem-broadband[cdc-wdm0]: failed to disconnect modem: GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: No such interface “org.f>
Jän 20 09:03:36.830511 pureos upowerd[733]: TI:09:03:36 unhandled action 'unbind' on /sys/devices/platform/soc@0/38200000.usb/xhci-hcd.4.auto/usb1/1-1/1-1.2
Jän 20 09:03:36.843107 pureos upowerd[733]: TI:09:03:36 SYSFS remove /sys/devices/platform/soc@0/38200000.usb/xhci-hcd.4.auto/usb1/1-1/1-1.2
Jän 20 09:03:36.843107 pureos upowerd[733]: TI:09:03:36 ignoring remove event on /sys/devices/platform/soc@0/38200000.usb/xhci-hcd.4.auto/usb1/1-1/1-1.2
Jän 20 09:03:36.846369 pureos systemd[1]: Starting Network Manager Script Dispatcher Service...
Jän 20 09:03:36.875302 pureos gsd-xsettings[922]: Failed to get current UI legacy scaling factor
Jän 20 09:03:36.875333 pureos gsd-xsettings[922]: Failed to get current UI legacy scaling factor
Jän 20 09:03:36.893044 pureos dbus-daemon[432]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
Jän 20 09:03:36.895905 pureos systemd[1]: Started Network Manager Script Dispatcher Service.
Jän 20 09:03:36.906816 pureos PackageKit[1220]: uid 1000 is trying to obtain org.freedesktop.packagekit.system-sources-refresh auth (only_trusted:0)
Jän 20 09:03:36.917832 pureos gsd-color[902]: unable to get EDID for xrandr-DSI-1: unable to get EDID for output
Jän 20 09:03:36.932114 pureos PackageKit[1220]: uid 1000 obtained auth for org.freedesktop.packagekit.system-sources-refresh
Jän 20 09:03:37.804780 pureos goa-daemon[709]: goa_http_client_check() failed: 2 — Fehler beim Auflösen von »cloud.puri.sm«: Der Name oder der Dienst ist nicht bekannt
Jän 20 09:03:37.805573 pureos goa-daemon[709]: /org/gnome/OnlineAccounts/Accounts/account_1638277513_0: Setting AttentionNeeded to TRUE because EnsureCredentials() failed with: Ungültiges Passwort für Benutzer >
Jän 20 09:03:38.808352 pureos goa-daemon[709]: goa_http_client_check() failed: 2 — Fehler beim Auflösen von »cloud.puri.sm«: Der Name oder der Dienst ist nicht bekannt
Jän 20 09:03:40.829247 pureos PackageKit[1220]: refresh-cache transaction /4509_aadcadbd from uid 1000 finished with failed after 3893ms
Jän 20 09:03:40.840526 pureos gnome-software[1071]: not handling error no-network for action refresh: Cannot refresh cache whilst offline
Jän 20 09:03:40.883206 pureos gnome-software[1071]: not handling error download-failed for action unknown: Fehler beim Auflösen von »dl.flathub.org«: Der Name oder der Dienst ist nicht bekannt
Jän 20 09:03:40.959470 pureos gnome-software[1071]: not handling error download-failed for action download: failed to download https://odrs.gnome.org/1.0/reviews/api/ratings: Cannot resolve hostname
Jän 20 09:03:43.380655 pureos kernel: usb 1-1.2: new high-speed USB device number 8 using xhci-hcd
(reconnecting then...)
```https://source.puri.sm/Librem5/linux/-/issues/459brcmfmac: mmc1 takes more than 2 seconds to resume from system suspend2023-03-23T20:23:17ZSebastian Krzyszkowiakbrcmfmac: mmc1 takes more than 2 seconds to resume from system suspendWhen used with the Sparklan card, mmc1 is a gigantic outlier when it comes to resume from suspend time, being the biggest contributor to resume being slow.
Doing
```
echo 1 | sudo tee /sys/power/pm_print_times
```
reveals that resuming...When used with the Sparklan card, mmc1 is a gigantic outlier when it comes to resume from suspend time, being the biggest contributor to resume being slow.
Doing
```
echo 1 | sudo tee /sys/power/pm_print_times
```
reveals that resuming mmc1 bus takes about 2.3-2.5 seconds. The only other device that takes significant amount of time is USB bus, and even then all USB devices together sum up to only 1 second.
This doesn't happen with WiFi turned off via killswitch, nor with Redpine card, where resuming mmc1 takes about 100µs.