I sometimes get this crash:
Mar 15 09:04:13 avalon kernel: Unable to handle kernel paging request at virtual address ffff800081312181
Mar 15 09:04:13 avalon kernel: Mem abort info:
Mar 15 09:04:13 avalon kernel: ESR = 0x0000000096000047
Mar 15 09:04:13 avalon kernel: EC = 0x25: DABT (current EL), IL = 32 bits
Mar 15 09:04:13 avalon kernel: SET = 0, FnV = 0
Mar 15 09:04:13 avalon kernel: EA = 0, S1PTW = 0
Mar 15 09:04:13 avalon kernel: FSC = 0x07: level 3 translation fault
Mar 15 09:04:13 avalon kernel: Data abort info:
Mar 15 09:04:13 avalon kernel: ISV = 0, ISS = 0x00000047, ISS2 = 0x00000000
Mar 15 09:04:13 avalon kernel: CM = 0, WnR = 1, TnD = 0, TagAccess = 0
Mar 15 09:04:13 avalon kernel: GCS = 0, Overlay = 0, DirtyBit = 0, Xs = 0
Mar 15 09:04:13 avalon kernel: swapper pgtable: 4k pages, 48-bit VAs, pgdp=00000000819e8000
Mar 15 09:04:13 avalon kernel: [ffff800081312181] pgd=10000000fffff003, p4d=10000000fffff003, pud=10000000ffffe003, pmd=10000000ffffa003, pte=0000000000000000
Mar 15 09:04:13 avalon kernel: bq25890-charger 3-006a: Upstream supply changed: 1.
Mar 15 09:04:13 avalon kernel: Internal error: Oops: 0000000096000047 [#1] PREEMPT SMP
Mar 15 09:04:13 avalon kernel: Modules linked in: aes_ce_ccm algif_hash algif_skcipher af_alg rfcomm bnep
Mar 15 09:04:13 avalon kernel: bq25890-charger 3-006a: Disabling OTG_EN pin
Mar 15 09:04:13 avalon kernel: st_magn_i2c st_sensors_i2c st_magn st_sensors st_lsm6dsx_i2c st_lsm6dsx_spi st_lsm6dsx usb_f_acm u_serial usb_f_ncm u_ether caam_jr caamhash_desc caamalg_des>
Mar 15 09:04:13 avalon kernel: mtdblock
Mar 15 09:04:13 avalon kernel: bq25890-charger 3-006a: Upstream supply changed: 1.
Mar 15 09:04:13 avalon kernel: mtd_blkdevs overlay ofpart xhci_plat_hcd spi_nor xhci_hcd mtd usbcore aes_ce_blk crct10dif_ce ghash_ce sha2_ce sha1_ce pwm_vibra dwc3 ulpi udc_core cdns_mhdp>
Mar 15 09:04:13 avalon kernel: CPU: 1 PID: 560 Comm: NetworkManager Not tainted 6.6.0-1-librem5 #1
Mar 15 09:04:13 avalon kernel: Hardware name: Purism Librem 5r4 (DT)
Mar 15 09:04:13 avalon kernel: pstate: 800000c5 (Nzcv daIF -PAN -UAO -TCO -DIT -SSBS BTYPE=--)
Mar 15 09:04:13 avalon kernel: bq25890-charger 3-006a: Disabling OTG_EN pin
Mar 15 09:04:13 avalon kernel: pc : queued_spin_lock_slowpath+0x374/0x488
Mar 15 09:04:13 avalon kernel: lr : _raw_spin_lock_irqsave+0x80/0xa0
Mar 15 09:04:13 avalon kernel: sp : ffff8000850abb20
Mar 15 09:04:13 avalon kernel: x29: ffff8000850abb20 x28: ffff000008693a00 x27: 0000000000000000
Mar 15 09:04:13 avalon kernel: x26: 0000000000000000 x25: 0000000000000000 x24: 0000000000000001
Mar 15 09:04:13 avalon kernel: x23: 0000000000000000 x22: ffff800081312100 x21: ffff8000812ff008
Mar 15 09:04:13 avalon kernel: x20: ffff0000a49bc100 x19: ffff00001a3b814c x18: 0000000000000000
Mar 15 09:04:13 avalon kernel: x17: 0000000000000000 x16: 0000000000000000 x15: 0000ffffded160d8
Mar 15 09:04:13 avalon kernel: x14: ffffffffffffffff x13: 0000000000000020 x12: 0101010101010101
Mar 15 09:04:13 avalon kernel: x11: 7f7f7f7f7f7f7f7f x10: 00007fffc86f7d30 x9 : ffff800080d18890
Mar 15 09:04:13 avalon snapd[569]: udevmon.go:149: udev event error: Unable to parse uevent, err: cannot parse libudev event: invalid env data
Mar 15 09:04:13 avalon snapd[569]: udevmon.go:149: udev event error: Unable to parse uevent, err: cannot parse libudev event: invalid env data
Mar 15 09:04:13 avalon kernel: x8 : 0101010101010101 x7 : 0000000080808080 x6 : 0000000000000051
Mar 15 09:04:13 avalon kernel: x5 : 0000000000080000 x4 : ffff800081312130 x3 : ffff800081312130
Mar 15 09:04:13 avalon kernel: x2 : 0000000000000000 x1 : ffff0000a49bc100 x0 : ffff0000a49bc108
Mar 15 09:04:13 avalon kernel: Call trace:
Mar 15 09:04:13 avalon kernel: queued_spin_lock_slowpath+0x374/0x488
Mar 15 09:04:13 avalon kernel: _raw_spin_lock_irqsave+0x80/0xa0
Mar 15 09:04:13 avalon kernel: __pm_runtime_resume+0x44/0xa0
Mar 15 09:04:13 avalon kernel: dev_ethtool+0x1a0/0x1a30
Mar 15 09:04:13 avalon kernel: dev_ioctl+0x2a4/0x3f0
Mar 15 09:04:13 avalon kernel: sock_do_ioctl+0xc0/0x108
Mar 15 09:04:13 avalon kernel: sock_ioctl+0x120/0x378
Mar 15 09:04:13 avalon kernel: __arm64_sys_ioctl+0xb0/0x100
Mar 15 09:04:13 avalon kernel: invoke_syscall+0x50/0x128
Mar 15 09:04:13 avalon kernel: el0_svc_common.constprop.0+0x48/0xf0
Mar 15 09:04:13 avalon kernel: do_el0_svc+0x24/0x38
Mar 15 09:04:13 avalon kernel: el0_svc+0x30/0x88
Mar 15 09:04:13 avalon kernel: el0t_64_sync_handler+0xc0/0xc8
Mar 15 09:04:13 avalon kernel: el0t_64_sync+0x190/0x198
Mar 15 09:04:13 avalon kernel: Code: 91002020 8b0402c4 f863d8c6 aa0403e3 (f8266861)
Mar 15 09:04:13 avalon kernel: bq25890-charger 3-006a: Upstream supply changed: 1.
Mar 15 09:04:13 avalon kernel: ---[ end trace 0000000000000000 ]---
I asked him to report back if the problem reappears
the user reported this after trying 6.5 and returning to 6.6:
just for other users that will happen to ask for help on such an issue I want to inform you that I removed the battery, hold for >18 seconds the power button (with no power connected or battery), re-inserted the battery and suspend works again with kernel 6.6 as it was working before.
Martin Kepplinger (caf270ba) at 17 Mar 16:02
Document changes and release 6.6.22pureos1~byz1 into byzantium
Martin Kepplinger (8e4be61e) at 17 Mar 15:26
Document changes and release 6.6.22pureos1~byz1 into byzantium
... and 503 more commits
Martin Kepplinger (2b445969) at 17 Mar 13:01
Document changes and release 6.6.22pureos1 into crimson
Martin Kepplinger (a58050e4) at 17 Mar 11:55
Document changes and release 6.6.22pureos1 into crimson
... and 501 more commits
I confirm that I have the above mentioned kernel oops also twice in my journal. Both are on the same day.
Maybe this is related to Device is not authorized for usage
messages.
I see that message for different usb devices 53 times on the day when the oops happened. But in total 88 times in my full journal.
This message is often preceded by logging from the bq25890-charger
, like for example:
Mar 07 16:36:36 avalon kernel: bq25890-charger 3-006a: Upstream supply changed: 0.
Mar 07 16:36:36 avalon kernel: bq25890-charger 3-006a: Enabling OTG_EN pin
Mar 07 16:36:36 avalon kernel: bq25890-charger 3-006a: Upstream supply changed: 0.
Mar 07 16:36:36 avalon kernel: bq25890-charger 3-006a: Enabling OTG_EN pin
Mar 07 16:36:36 avalon snapd[596]: udevmon.go:149: udev event error: Unable to parse uevent, err: cannot parse libudev event: invalid env data
Mar 07 16:36:36 avalon kernel: bq25890-charger 3-006a: Upstream supply changed: 0.
Mar 07 16:36:36 avalon kernel: bq25890-charger 3-006a: Enabling OTG_EN pin
Mar 07 16:36:36 avalon kernel: xhci-hcd xhci-hcd.5.auto: xHCI Host Controller
Mar 07 16:36:36 avalon kernel: xhci-hcd xhci-hcd.5.auto: new USB bus registered, assigned bus number 3
Mar 07 16:36:36 avalon kernel: xhci-hcd xhci-hcd.5.auto: hcc params 0x0220fe6c hci version 0x110 quirks 0x0000000000000010
Mar 07 16:36:36 avalon kernel: xhci-hcd xhci-hcd.5.auto: irq 208, io mem 0x38100000
Mar 07 16:36:36 avalon kernel: xhci-hcd xhci-hcd.5.auto: xHCI Host Controller
Mar 07 16:36:36 avalon kernel: xhci-hcd xhci-hcd.5.auto: new USB bus registered, assigned bus number 4
Mar 07 16:36:36 avalon kernel: xhci-hcd xhci-hcd.5.auto: Host supports USB 3.0 SuperSpeed
Mar 07 16:36:36 avalon kernel: bq25890-charger 3-006a: Upstream supply changed: 0.
Mar 07 16:36:36 avalon kernel: bq25890-charger 3-006a: Enabling OTG_EN pin
Mar 07 16:36:36 avalon kernel: usb usb3: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 6.06
Mar 07 16:36:36 avalon kernel: usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Mar 07 16:36:36 avalon kernel: usb usb3: Product: xHCI Host Controller
Mar 07 16:36:36 avalon kernel: usb usb3: Manufacturer: Linux 6.6.0-1-librem5 xhci-hcd
Mar 07 16:36:36 avalon kernel: usb usb3: SerialNumber: xhci-hcd.5.auto
Mar 07 16:36:36 avalon kernel: hub 3-0:1.0: USB hub found
Mar 07 16:36:36 avalon kernel: hub 3-0:1.0: 1 port detected
Mar 07 16:36:36 avalon kernel: usb usb4: We don't know the algorithms for LPM for this host, disabling LPM.
Mar 07 16:36:36 avalon kernel: usb usb4: New USB device found, idVendor=1d6b, idProduct=0003, bcdDevice= 6.06
Mar 07 16:36:36 avalon kernel: usb usb4: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Mar 07 16:36:36 avalon kernel: usb usb4: Product: xHCI Host Controller
Mar 07 16:36:36 avalon kernel: usb usb4: Manufacturer: Linux 6.6.0-1-librem5 xhci-hcd
Mar 07 16:36:36 avalon kernel: usb usb4: SerialNumber: xhci-hcd.5.auto
Mar 07 16:36:36 avalon kernel: hub 4-0:1.0: USB hub found
Mar 07 16:36:36 avalon kernel: hub 4-0:1.0: 1 port detected
Mar 07 16:36:36 avalon kernel: bq25890-charger 3-006a: Upstream supply changed: 0.
Mar 07 16:36:36 avalon kernel: bq25890-charger 3-006a: Enabling OTG_EN pin
Mar 07 16:36:36 avalon kernel: bq25890-charger 3-006a: Upstream supply changed: 0.
Mar 07 16:36:36 avalon kernel: bq25890-charger 3-006a: Enabling OTG_EN pin
Mar 07 16:36:36 avalon snapd[596]: udevmon.go:149: udev event error: Unable to parse uevent, err: cannot parse libudev event: invalid env data
Mar 07 16:36:36 avalon snapd[596]: udevmon.go:149: udev event error: Unable to parse uevent, err: cannot parse libudev event: invalid env data
Mar 07 16:36:36 avalon snapd[596]: udevmon.go:149: udev event error: Unable to parse uevent, err: cannot parse libudev event: invalid env data
Mar 07 16:36:36 avalon snapd[596]: udevmon.go:149: udev event error: Unable to parse uevent, err: cannot parse libudev event: invalid env data
Mar 07 16:36:36 avalon usbguard-daemon[686]: uid=0 pid=606 result='SUCCESS' device.rule='allow id 1d6b:0002 serial "xhci-hcd.5.auto" name "xHCI Host Controller" hash "U1nFyrkh8NpSDAU6gmicq7>
Mar 07 16:36:36 avalon usbguard-daemon[686]: uid=0 pid=606 result='SUCCESS' device.system_name='/devices/platform/soc@0/38100000.usb/xhci-hcd.5.auto/usb3' target.new='allow' device.rule='al>
Mar 07 16:36:36 avalon usbguard-daemon[686]: uid=0 pid=606 result='SUCCESS' device.rule='allow id 1d6b:0003 serial "xhci-hcd.5.auto" name "xHCI Host Controller" hash "G/QjSJzB6wJUsQhzW88okv>
Mar 07 16:36:36 avalon usbguard-daemon[686]: uid=0 pid=606 result='SUCCESS' device.system_name='/devices/platform/soc@0/38100000.usb/xhci-hcd.5.auto/usb4' target.new='allow' device.rule='al>
Mar 07 16:36:36 avalon kernel: bq25890-charger 3-006a: Upstream supply changed: 0.
Mar 07 16:36:36 avalon kernel: bq25890-charger 3-006a: Enabling OTG_EN pin
Mar 07 16:36:36 avalon kernel: bq25890-charger 3-006a: Upstream supply changed: 0.
Mar 07 16:36:36 avalon kernel: bq25890-charger 3-006a: Enabling OTG_EN pin
Mar 07 16:36:36 avalon kernel: bq25890-charger 3-006a: Upstream supply changed: 1.
Mar 07 16:36:36 avalon kernel: bq25890-charger 3-006a: Disabling OTG_EN pin
Mar 07 16:36:37 avalon kernel: bq25890-charger 3-006a: Upstream supply changed: 1.
Mar 07 16:36:37 avalon kernel: bq25890-charger 3-006a: Disabling OTG_EN pin
Mar 07 16:36:38 avalon kernel: usb 3-1: new high-speed USB device number 2 using xhci-hcd
Mar 07 16:36:38 avalon kernel: usb 3-1: New USB device found, idVendor=0bda, idProduct=5421, bcdDevice= 2.04
Mar 07 16:36:38 avalon kernel: usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
Mar 07 16:36:38 avalon kernel: usb 3-1: Product: 4-Port USB 2.0 Hub
Mar 07 16:36:38 avalon kernel: usb 3-1: Manufacturer: Generic
Mar 07 16:36:38 avalon kernel: usb 3-1: Device is not authorized for usage
This is also in line with my feeling that these "half hangs" seem to occur after plugging in or removing a USB cable to charge, or stop charging the Librem 5.
If it would be useful, I could provide the full journal on request.
I checked my journal (from February 22 until March 13) more thoroughly for stack traces.
I see similar stack traces to the one mentioned above quite often:
# journalctl | grep WARNING.*scan | wc -l
52
They seem to happen after a resume from suspend.
I doubt now if this problem really results in a hang of the Librem 5.
Note that I still use the Redpine WiFi module.
asked the client to try kernel 6.5
This was reported by a user
With the recent updates (to kernel 6.6.0) my L5 can not suspend anymore. But it was suspending before.
I have tried to resolve this with the help of the forum but it seems we cannot debug the problem. The discussion is here:
https://forums.puri.sm/t/does-suspend-work-for-you/22910/33
where I posted dmesg and log files. The only message is that the non bootable CPUs are not killed anymore. It tries to suspend and gets back on immediately. sudo systemctl suspend does the same.
in dmesg we see
[ 168.453324] Disabling non-boot CPUs … [ 168.453336] Wakeup pending. Abort CPU freeze [ 168.453338] Non-boot CPUs are not disabled
If this looks like a kernel problem
Below I have pasted the relevant part of journalctl
Mar 04 18:32:38 pureos systemd[1]: Starting Suspend…
Mar 04 18:32:38 pureos systemd-sleep[1981]: Suspending system…
Mar 04 18:32:38 pureos kernel: PM: suspend entry (deep)
Mar 04 18:32:39 pureos kernel: Filesystems sync: 0.028 seconds
Mar 04 18:32:39 pureos kernel: Freezing user space processes
Mar 04 18:32:39 pureos kernel: Freezing user space processes completed
(elapsed 0.009 seconds)
Mar 04 18:32:39 pureos kernel: OOM killer disabled.
Mar 04 18:32:39 pureos kernel: Freezing remaining freezable tasks
Mar 04 18:32:39 pureos kernel: Freezing remaining freezable tasks
completed (elapsed 0.001 seconds)
Mar 04 18:32:39 pureos kernel: printk: Suspending console(s) (use
no_console_suspend to debug)
Mar 04 18:32:39 pureos kernel: Disabling non-boot CPUs …
Mar 04 18:32:39 pureos kernel: psci: CPU1 killed (polled 0 ms)
Mar 04 18:32:39 pureos kernel: psci: CPU2 killed (polled 0 ms)
Mar 04 18:32:39 pureos kernel: psci: CPU3 killed (polled 4 ms)
Mar 04 18:32:39 pureos kernel: Enabling non-boot CPUs …
Mar 04 18:32:39 pureos kernel: Detected VIPT I-cache on CPU1
Mar 04 18:32:39 pureos kernel: GICv3: CPU1: found redistributor 1
region 0:0x00000000388a0000
Mar 04 18:32:39 pureos kernel: CPU1: Booted secondary processor
0x0000000001 [0x410fd034]
Mar 04 18:32:39 pureos kernel: CPU1 is up
Mar 04 18:32:39 pureos kernel: Detected VIPT I-cache on CPU2
Mar 04 18:32:39 pureos kernel: GICv3: CPU2: found redistributor 2
region 0:0x00000000388c0000
Mar 04 18:32:39 pureos kernel: CPU2: Booted secondary processor
0x0000000002 [0x410fd034]
Mar 04 18:32:39 pureos kernel: CPU2 is up
Mar 04 18:32:39 pureos kernel: Detected VIPT I-cache on CPU3
Mar 04 18:32:39 pureos kernel: GICv3: CPU3: found redistributor 3
region 0:0x00000000388e0000
Mar 04 18:32:39 pureos kernel: CPU3: Booted secondary processor
0x0000000003 [0x410fd034]
Mar 04 18:32:39 pureos kernel: CPU3 is up
Mar 04 18:32:39 pureos kernel: caam 30900000.crypto: registering rng-
caam
Mar 04 18:32:39 pureos kernel: OOM killer enabled.
Mar 04 18:32:39 pureos kernel: Restarting tasks … done.
Mar 04 18:32:39 pureos kernel: random: crng reseeded on system
resumption
Mar 04 18:32:39 pureos kernel: thermal thermal_zone3: failed to read
out thermal zone (-61)
Mar 04 18:32:39 pureos kernel: PM: suspend exit
Mar 04 18:32:39 pureos systemd-sleep[1981]: System resumed.
I just got something matching the issue description with this kernel oops:
Mär 11 14:27:30 evergreen106b5 kernel: Unable to handle kernel NULL pointer dereference at virtual address 0000000000000000
Mär 11 14:27:30 evergreen106b5 kernel: Mem abort info:
Mär 11 14:27:30 evergreen106b5 kernel: ESR = 0x0000000096000004
Mär 11 14:27:30 evergreen106b5 kernel: EC = 0x25: DABT (current EL), IL = 32 bits
Mär 11 14:27:30 evergreen106b5 kernel: SET = 0, FnV = 0
Mär 11 14:27:30 evergreen106b5 kernel: EA = 0, S1PTW = 0
Mär 11 14:27:30 evergreen106b5 kernel: FSC = 0x04: level 0 translation fault
Mär 11 14:27:30 evergreen106b5 kernel: Data abort info:
Mär 11 14:27:30 evergreen106b5 kernel: ISV = 0, ISS = 0x00000004, ISS2 = 0x00000000
Mär 11 14:27:30 evergreen106b5 kernel: CM = 0, WnR = 0, TnD = 0, TagAccess = 0
Mär 11 14:27:30 evergreen106b5 kernel: GCS = 0, Overlay = 0, DirtyBit = 0, Xs = 0
Mär 11 14:27:30 evergreen106b5 kernel: user pgtable: 4k pages, 48-bit VAs, pgdp=0000000047815000
Mär 11 14:27:30 evergreen106b5 kernel: [0000000000000000] pgd=0000000000000000, p4d=0000000000000000
Mär 11 14:27:30 evergreen106b5 kernel: Internal error: Oops: 0000000096000004 [#1] PREEMPT SMP
Mär 11 14:27:30 evergreen106b5 kernel: Modules linked in: bnep nft_masq nft_chain_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 bridge stp nf_tables libcrc32c aes_ce_ccm snd_seq_dummy snd_seq snd_seq_device usb_f_acm u_serial usb_f_ncm u_ether st_magn_i2c st_sens>
Mär 11 14:27:30 evergreen106b5 kernel: snd_timer watchdog snd caam virt_dma error soundcore rfkill_hks imx_rproc leds_pwm_multicolor led_class_multicolor cfg80211 rfkill libcomposite fuse ledtrig_timer nfnetlink ip_tables x_tables ipv6 autofs4 xhci_plat_hcd xhci_hcd usb>
Mär 11 14:27:30 evergreen106b5 kernel: CPU: 1 PID: 24813 Comm: sudo Not tainted 6.6.0-1-librem5 #1
Mär 11 14:27:30 evergreen106b5 kernel: Hardware name: Purism Librem 5r4 (DT)
Mär 11 14:27:30 evergreen106b5 kernel: pstate: 80000005 (Nzcv daif -PAN -UAO -TCO -DIT -SSBS BTYPE=--)
Mär 11 14:27:30 evergreen106b5 kernel: pc : __pi_strlen+0x14/0x150
Mär 11 14:27:30 evergreen106b5 kernel: lr : rtnl_fill_ifinfo+0xf58/0x1250
Mär 11 14:27:30 evergreen106b5 kernel: sp : ffff800086a2b4e0
Mär 11 14:27:30 evergreen106b5 kernel: x29: ffff800086a2b4e0 x28: ffff0000359df000 x27: 00000000000007f8
Mär 11 14:27:30 evergreen106b5 kernel: x26: ffff0000359df000 x25: 0000000000000b1c x24: ffff0000359df58c
Mär 11 14:27:30 evergreen106b5 kernel: x23: ffff0000359df000 x22: ffff0000359dfb1c x21: fffffc00002742c0
Mär 11 14:27:30 evergreen106b5 kernel: x20: 0000000000000000 x19: ffff000007854f00 x18: 0000000000000000
Mär 11 14:27:30 evergreen106b5 kernel: x17: 0000000000000000 x16: 0000000000000000 x15: 0000000000000000
Mär 11 14:27:30 evergreen106b5 kernel: x14: 0000000000000000 x13: 0000000000000000 x12: 0000000000000000
Mär 11 14:27:30 evergreen106b5 kernel: x11: 0000000000000000 x10: 0000000000000000 x9 : ffff80008075d98c
Mär 11 14:27:30 evergreen106b5 kernel: x8 : 0101010101010101 x7 : 0000000000000000 x6 : 0000000000000000
Mär 11 14:27:30 evergreen106b5 kernel: x5 : ffff0000359dfb21 x4 : 0000000000000000 x3 : 0000000000000b24
Mär 11 14:27:30 evergreen106b5 kernel: x2 : 0000000000000001 x1 : fffffc00002742c0 x0 : 0000000000000000
Mär 11 14:27:30 evergreen106b5 kernel: Call trace:
Mär 11 14:27:30 evergreen106b5 kernel: __pi_strlen+0x14/0x150
Mär 11 14:27:30 evergreen106b5 kernel: rtnl_dump_ifinfo+0x2cc/0x6b0
Mär 11 14:27:30 evergreen106b5 kernel: netlink_dump+0x114/0x2e0
Mär 11 14:27:30 evergreen106b5 kernel: __netlink_dump_start+0x1bc/0x2b8
Mär 11 14:27:30 evergreen106b5 kernel: rtnetlink_rcv_msg+0x264/0x390
Mär 11 14:27:30 evergreen106b5 kernel: netlink_rcv_skb+0x64/0x138
Mär 11 14:27:30 evergreen106b5 kernel: rtnetlink_rcv+0x20/0x38
Mär 11 14:27:30 evergreen106b5 kernel: netlink_unicast+0x1cc/0x2d8
Mär 11 14:27:30 evergreen106b5 kernel: netlink_sendmsg+0x1d8/0x460
Mär 11 14:27:30 evergreen106b5 kernel: __sock_sendmsg+0x64/0xc0
Mär 11 14:27:30 evergreen106b5 kernel: __sys_sendto+0x114/0x178
Mär 11 14:27:30 evergreen106b5 kernel: __arm64_sys_sendto+0x30/0x48
Mär 11 14:27:30 evergreen106b5 kernel: invoke_syscall+0x50/0x128
Mär 11 14:27:30 evergreen106b5 kernel: el0_svc_common.constprop.0+0x48/0xf0
Mär 11 14:27:30 evergreen106b5 kernel: do_el0_svc+0x24/0x38
Mär 11 14:27:30 evergreen106b5 kernel: el0_svc+0x30/0x88
Mär 11 14:27:30 evergreen106b5 kernel: el0t_64_sync_handler+0x100/0x130
Mär 11 14:27:30 evergreen106b5 kernel: el0t_64_sync+0x190/0x198
Mär 11 14:27:30 evergreen106b5 kernel: Code: 92402c04 b200c3e8 f13fc09f 5400088c (a9400c02)
Mär 11 14:27:30 evergreen106b5 kernel: ---[ end trace 0000000000000000 ]---
Confirming. My Librem 5 has the same issue. You described the issue well. Indeed it is difficult to describe it. Maybe related to issue #495.
since the few latest kernel upgrade, my L5 half hangs very often. By half hang I mean parts of the system hang. Phosh works, but it is impossible to sudo anything (sudo ls will hang forever before asking for a password). It is impossible to reboot cleanly, switching the hks seemingly does nothing (the 4G, wifi symbol stays here even when turn off). I have collected 2 logs that should contain the relevant parts. They're a bit long because I'm never sure when exactly the problem occurs since this happens mostly during charge. I also don't know if charging is causing the issue, of just staying active for a long time (sleep is deactivated during charging).