Every once and a while, my Librem 5 will get stuck or hang, sometimes with “Unknown Applications” not being able to close. Yesterday, I couldn’t run the “ip a” command, it would just get stuck forever. I also the chatty application hung and I couldn’t kill it with “sudo killall -9 chatty”. Usually, when I run into these issues, I go to reboot and then it shuts off and then when I finally get it to start, the issue goes away for a while. Being annoyed by these kinds of events happening more frequently, I checked the logs and noticed issues with the wireless networking, which has access to the 5GHz router and the physical switch was turned on. The following errors showed up when running “sudo dmesg”:
[ 23.983519] iio iio:device3: DRDY on pin INT2 specified, but sensor does not support interrupts
[ 23.985689] iio iio:device3: interrupts active high level
[ 24.575991] configfs-gadget.g1 gadget.0: HOST MAC 52:16:bb:aa:73:af
[ 24.576017] configfs-gadget.g1 gadget.0: MAC 06:a1:24:be:e8:95
[ 25.325822] loop11: detected capacity change from 0 to 8
[ 26.524256] systemd-journald[463]: File /var/log/journal/6247ed61609c498c829346c1e3a0c661/user-1000.journal corrupted or uncleanly shut down, renaming and replacing.
[ 27.758736] brcmfmac_cyw: brcmf_cyw_attach: executing
[ 27.812910] brcmfmac: brcmf_c_process_txcap_blob: no txcap_blob available (err=-2)
[ 27.825235] brcmfmac: brcmf_c_preinit_dcmds: Firmware: BCM43752/2 wl0: Jul 13 2020 18:32:45 version 18.35.387.23.7 (b328500@shgit) (wlan=r880297) FWID 01-f50fdff0
[ 28.719125] Bluetooth: Core ver 2.22
[ 28.719680] NET: Registered PF_BLUETOOTH protocol family
[ 28.719693] Bluetooth: HCI device and connection manager initialized
[ 28.719709] Bluetooth: HCI socket layer initialized
[ 28.719717] Bluetooth: L2CAP socket layer initialized
[ 28.719736] Bluetooth: SCO socket layer initialized
[ 28.729215] Bluetooth: HCI UART driver ver 2.3
[ 28.729236] Bluetooth: HCI UART protocol H4 registered
[ 28.729240] Bluetooth: HCI UART protocol BCSP registered
[ 28.729244] Bluetooth: HCI UART protocol ATH3K registered
[ 28.729346] Bluetooth: HCI UART protocol Three-wire (H5) registered
[ 28.729388] Bluetooth: HCI UART protocol QCA registered
[ 28.729423] Bluetooth: HCI UART protocol Marvell registered
[ 28.877379] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[ 28.877415] Bluetooth: BNEP socket layer initialized
[ 28.885635] Bluetooth: MGMT ver 1.22
[ 28.889042] [drm] Connector status: 0
[ 28.895745] NET: Registered PF_ALG protocol family
[ 28.942799] Bluetooth: RFCOMM TTY layer initialized
[ 28.942837] Bluetooth: RFCOMM socket layer initialized
[ 28.942863] Bluetooth: RFCOMM ver 1.11
[ 30.271096] ieee80211 phy0: brcmf_p2p_create_p2pdev: timeout occurred
[ 30.277650] ieee80211 phy0: brcmf_cfg80211_add_iface: add iface p2p-dev-wlan0 type 10 failed: err=-5
[ 38.099345] Key type cifs.idmap registered
[ 38.101044] CIFS: No dialect specified on mount. Default has changed to a more secure dialect, SMB2.1 or later (e.g. SMB3.1.1), from CIFS (SMB1). To use the less secure SMB1 dialect to access old servers which do not support SMB3.1.1 (or even SMB3 or SMB2.1) specify vers=1.0 on mount.
On other devices, it seems they addressed some of these stability issues with these chipsets by adjusting the wifi signal power? Am I the only one that has networking issues like this from time to time?
It’s also worth mentioning that sometimes, I will see a dialog pop-up which will say something like:
“Authentication Required”
"Enter password for wifi network “[RouterName]” (non-5 GHz)
I usually close this because it doesn’t pre-fill the password with the last password used and there’s no check-box for remember password or anything like that. Also, why does it not prompt for the 5 GHz SSID when this happens? If it’s already connected to the 5 GHz bands, why prompt for another SSID?
I also experience this sometimes. It is interesting that this could be related to wifi. I usually face these issues while at work, where I am not connected to wifi at all. I will try to keep the wifi kill switch enabled when not at home to see if that helps
Most of the time, I usually leave my wifi switch on. I did notice that I had “automatically connect” configured for the 2.4 GHz band. I suspect by disabling “automatically connect” for that connection that will at least get rid of the random connection prompts, but it may be a completely separate issue from the applications not being able to be closed or killed issue. I think those network errors could be related, because I certainly could not run network related commands without them doing nothing indefinitely. At another time I even tried to restart the NetworkManager service with “sudo systemctl restart NetworkManager” and it also would hang. It’s almost like the drivers themselves are getting hung up causing every other application trying to use the network drivers to get stuck (including the SMS chatty application).
Maybe. If I’m not mistaken the kernel update from yesterday or so might fix that. Unfortunately, I was not able to really pinpoint the issue. Actually, I think there might be a few issues that have similar symptoms, or that might trigger each other.
Would be decent if that update did fix the half hang thing because it’s pretty annoying to not be able to use my Nexdock or have my phone go offline and people trying to call me and just get my voicemail.
I wonder what it means that “Direct firmware load for brcm/brcmfmac43752-sdio.purism,librem5r4.bin failed with error -2” and “no txcap_blob available (err=-2)”. Here is what I see after booting up.
$ sudo dmesg | grep brcmf
[ 23.344845] brcmfmac: F1 signature read @0x18000000=0x1042aae8
[ 23.356857] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43752-sdio for chip BCM43752/2
[ 23.365832] brcmfmac mmc1:0001:1: Direct firmware load for brcm/brcmfmac43752-sdio.purism,librem5r4.bin failed with error -2
[ 28.471898] brcmfmac: brcmf_c_process_txcap_blob: no txcap_blob available (err=-2)
[ 28.481677] brcmfmac: brcmf_c_preinit_dcmds: Firmware: BCM43752/2 wl0: Jul 13 2020 18:32:45 version 18.35.387.23.7 (b328500@shgit) (wlan=r880297) FWID 01-f50fdff0
[ 30.887660] ieee80211 phy0: brcmf_p2p_create_p2pdev: timeout occurred
[ 30.894242] ieee80211 phy0: brcmf_cfg80211_add_iface: add iface p2p-dev-wlan0 type 10 failed: err=-5
I was able to get a dmesg log today when the connectivity failed again. sudo used to segfault or hang before. The phone was not plugged in into anything for at least an hour when it happened.
a dmesg log
$ sudo dmesg --level=err
[63521.351777] usb 3-1.4: Device is not authorized for usage
[63529.369797] usb 3-1.4: Device is not authorized for usage
[63537.453564] usb 3-1.4: Device is not authorized for usage
[63545.506449] usb 3-1.4: Device is not authorized for usage
[63553.583027] usb 3-1.4: Device is not authorized for usage
[63561.720667] usb 3-1.4: Device is not authorized for usage
[63569.828024] usb 3-1.4: Device is not authorized for usage
[63577.865435] usb 3-1.4: Device is not authorized for usage
[63585.888416] usb 3-1.4: Device is not authorized for usage
[63594.055708] usb 3-1.4: Device is not authorized for usage
[63602.067498] usb 3-1.4: Device is not authorized for usage
[63610.156919] usb 3-1.4: Device is not authorized for usage
[63618.269580] usb 3-1.4: Device is not authorized for usage
[63626.273088] usb 3-1.4: Device is not authorized for usage
[63634.404163] usb 3-1.4: Device is not authorized for usage
[63642.510951] usb 3-1.4: Device is not authorized for usage
[63650.522124] usb 3-1.4: Device is not authorized for usage
[63658.610299] usb 3-1.4: Device is not authorized for usage
[63666.669734] usb 3-1.4: Device is not authorized for usage
[63674.779850] usb 3-1.4: Device is not authorized for usage
[63682.875326] usb 3-1.4: Device is not authorized for usage
[63690.949898] usb 3-1.4: Device is not authorized for usage
[63699.007140] usb 3-1.4: Device is not authorized for usage
[63707.094580] usb 3-1.4: Device is not authorized for usage
[63715.186693] usb 3-1.4: Device is not authorized for usage
[63723.219503] usb 3-1.4: Device is not authorized for usage
[63731.333393] usb 3-1.4: Device is not authorized for usage
[63739.437998] usb 3-1.4: Device is not authorized for usage
[63747.487741] usb 3-1.4: Device is not authorized for usage
[63755.575586] usb 3-1.4: Device is not authorized for usage
[63763.677382] usb 3-1.4: Device is not authorized for usage
[63771.870383] usb 3-1.4: Device is not authorized for usage
[63779.818219] usb 3-1.4: Device is not authorized for usage
[63787.934143] usb 3-1.4: Device is not authorized for usage
[63795.987461] usb 3-1.4: Device is not authorized for usage
[63804.055366] usb 3-1.4: Device is not authorized for usage
[63812.108491] usb 3-1.4: Device is not authorized for usage
[63820.182669] usb 3-1.4: Device is not authorized for usage
[63828.318015] usb 3-1.4: Device is not authorized for usage
[63836.346526] usb 3-1.4: Device is not authorized for usage
[63844.450754] usb 3-1.4: Device is not authorized for usage
[63852.455148] usb 3-1.4: Device is not authorized for usage
[63860.564629] usb 3-1.4: Device is not authorized for usage
[63868.656135] usb 3-1.4: Device is not authorized for usage
[63876.726357] usb 3-1.4: Device is not authorized for usage
[63884.835990] usb 3-1.4: Device is not authorized for usage
[63892.856076] usb 3-1.4: Device is not authorized for usage
[63900.992712] usb 3-1.4: Device is not authorized for usage
[63909.048663] usb 3-1.4: Device is not authorized for usage
[63917.112374] usb 3-1.4: Device is not authorized for usage
[63925.208519] usb 3-1.4: Device is not authorized for usage
[63933.264470] usb 3-1.4: Device is not authorized for usage
[63941.380632] usb 3-1.4: Device is not authorized for usage
[63949.438830] usb 3-1.4: Device is not authorized for usage
[63957.704908] usb 3-1.4: Device is not authorized for usage
[63965.619223] usb 3-1.4: Device is not authorized for usage
[63973.676214] usb 3-1.4: Device is not authorized for usage
[63981.771841] usb 3-1.4: Device is not authorized for usage
[63989.915352] usb 3-1.4: Device is not authorized for usage
[63997.927455] usb 3-1.4: Device is not authorized for usage
[64005.988323] usb 3-1.4: Device is not authorized for usage
[64014.265145] usb 3-1.4: Device is not authorized for usage
[64022.188488] usb 3-1.4: Device is not authorized for usage
[64030.273405] usb 3-1.4: Device is not authorized for usage
[64038.335845] usb 3-1.4: Device is not authorized for usage
[64046.451999] usb 3-1.4: Device is not authorized for usage
[64054.474917] usb 3-1.4: Device is not authorized for usage
[64062.572666] usb 3-1.4: Device is not authorized for usage
[64070.841760] usb 3-1.4: Device is not authorized for usage
[64078.757634] usb 3-1.4: Device is not authorized for usage
[64086.828968] usb 3-1.4: Device is not authorized for usage
[64094.869970] usb 3-1.4: Device is not authorized for usage
[64102.981460] usb 3-1.4: Device is not authorized for usage
[64111.039705] usb 3-1.4: Device is not authorized for usage
[64119.108522] usb 3-1.4: Device is not authorized for usage
[64127.166100] usb 3-1.4: Device is not authorized for usage
[64135.301241] usb 3-1.4: Device is not authorized for usage
[64143.408711] usb 3-1.4: Device is not authorized for usage
[64151.498675] usb 3-1.4: Device is not authorized for usage
[64159.576807] usb 3-1.4: Device is not authorized for usage
[64167.648182] usb 3-1.4: Device is not authorized for usage
[64175.850832] usb 3-1.4: Device is not authorized for usage
[64183.780295] usb 3-1.4: Device is not authorized for usage
[64191.880790] usb 3-1.4: Device is not authorized for usage
[64199.971298] usb 3-1.4: Device is not authorized for usage
[64208.011750] usb 3-1.4: Device is not authorized for usage
[64216.128013] usb 3-1.4: Device is not authorized for usage
[64224.242266] usb 3-1.4: Device is not authorized for usage
[64232.275810] usb 3-1.4: Device is not authorized for usage
[64240.599738] usb 3-1.4: Device is not authorized for usage
[64248.439606] usb 3-1.4: Device is not authorized for usage
[64256.554205] usb 3-1.4: Device is not authorized for usage
[64264.649769] usb 3-1.4: Device is not authorized for usage
[64272.689483] usb 3-1.4: Device is not authorized for usage
[64280.773033] usb 3-1.4: Device is not authorized for usage
[64288.867683] usb 3-1.4: Device is not authorized for usage
[64296.889569] usb 3-1.4: Device is not authorized for usage
[64304.987132] usb 3-1.4: Device is not authorized for usage
[64313.108478] usb 3-1.4: Device is not authorized for usage
[64321.213125] usb 3-1.4: Device is not authorized for usage
[64329.459239] usb 3-1.4: Device is not authorized for usage
[64337.388796] usb 3-1.4: Device is not authorized for usage
[64345.398668] usb 3-1.4: Device is not authorized for usage
[64353.539080] usb 3-1.4: Device is not authorized for usage
[64361.602104] usb 3-1.4: Device is not authorized for usage
[64369.615303] usb 3-1.4: Device is not authorized for usage
[64377.741427] usb 3-1.4: Device is not authorized for usage
[64386.006643] usb 3-1.4: Device is not authorized for usage
[64393.859882] usb 3-1.4: Device is not authorized for usage
[64401.950498] usb 3-1.4: Device is not authorized for usage
[64410.038781] usb 3-1.4: Device is not authorized for usage
[64418.112210] usb 3-1.4: Device is not authorized for usage
[64426.180090] usb 3-1.4: Device is not authorized for usage
[64434.262767] usb 3-1.4: Device is not authorized for usage
[64442.343060] usb 3-1.4: Device is not authorized for usage
[64450.407693] usb 3-1.4: Device is not authorized for usage
[64458.459915] usb 3-1.4: Device is not authorized for usage
[64466.527065] usb 3-1.4: Device is not authorized for usage
[64474.594222] usb 3-1.4: Device is not authorized for usage
[64482.697528] usb 3-1.4: Device is not authorized for usage
[64490.787010] usb 3-1.4: Device is not authorized for usage
[64498.913544] usb 3-1.4: Device is not authorized for usage
[64506.892701] usb 3-1.4: Device is not authorized for usage
[64514.961638] usb 3-1.4: Device is not authorized for usage
[64523.099506] usb 3-1.4: Device is not authorized for usage
[64531.146835] usb 3-1.4: Device is not authorized for usage
[64539.190184] usb 3-1.4: Device is not authorized for usage
[64547.316509] usb 3-1.4: Device is not authorized for usage
[64555.397298] usb 3-1.4: Device is not authorized for usage
[64563.461370] usb 3-1.4: Device is not authorized for usage
[64571.583721] usb 3-1.4: Device is not authorized for usage
[64579.678385] usb 3-1.4: Device is not authorized for usage
[64587.717118] usb 3-1.4: Device is not authorized for usage
[64595.823025] usb 3-1.4: Device is not authorized for usage
[64603.876382] usb 3-1.4: Device is not authorized for usage
[64612.058348] usb 3-1.4: Device is not authorized for usage
[64620.082226] usb 3-1.4: Device is not authorized for usage
[64628.195865] usb 3-1.4: Device is not authorized for usage
[64636.230427] usb 3-1.4: Device is not authorized for usage
[64644.305187] usb 3-1.4: Device is not authorized for usage
[64652.377301] usb 3-1.4: Device is not authorized for usage
[64660.433122] usb 3-1.4: Device is not authorized for usage
[64668.605376] usb 3-1.4: Device is not authorized for usage
[64676.591816] usb 3-1.4: Device is not authorized for usage
[64684.721003] usb 3-1.4: Device is not authorized for usage
[64692.725755] usb 3-1.4: Device is not authorized for usage
[64700.846765] usb 3-1.4: Device is not authorized for usage
[64708.876888] usb 3-1.4: Device is not authorized for usage
[64716.984958] usb 3-1.4: Device is not authorized for usage
[64725.085677] usb 3-1.4: Device is not authorized for usage
[64733.140792] usb 3-1.4: Device is not authorized for usage
[64741.206963] usb 3-1.4: Device is not authorized for usage
[64749.287753] usb 3-1.4: Device is not authorized for usage
[64757.404580] usb 3-1.4: Device is not authorized for usage
[64765.653797] usb 3-1.4: Device is not authorized for usage
[64773.533626] usb 3-1.4: Device is not authorized for usage
[64781.625340] usb 3-1.4: Device is not authorized for usage
[64789.683051] usb 3-1.4: Device is not authorized for usage
[64797.767176] usb 3-1.4: Device is not authorized for usage
[64805.825660] usb 3-1.4: Device is not authorized for usage
[64813.917161] usb 3-1.4: Device is not authorized for usage
[64821.948673] usb 3-1.4: Device is not authorized for usage
[64830.055491] usb 3-1.4: Device is not authorized for usage
[64838.191677] usb 3-1.4: Device is not authorized for usage
[64846.281561] usb 3-1.4: Device is not authorized for usage
[64854.382021] usb 3-1.4: Device is not authorized for usage
[64862.440590] usb 3-1.4: Device is not authorized for usage
[64870.505416] usb 3-1.4: Device is not authorized for usage
[64878.524384] usb 3-1.4: Device is not authorized for usage
[64886.719331] usb 3-1.4: Device is not authorized for usage
[64894.750869] usb 3-1.4: Device is not authorized for usage
[64902.879013] usb 3-1.4: Device is not authorized for usage
[64910.901599] usb 3-1.4: Device is not authorized for usage
[64919.009192] usb 3-1.4: Device is not authorized for usage
[64927.122493] usb 3-1.4: Device is not authorized for usage
[64935.242913] usb 3-1.4: Device is not authorized for usage
[64943.296337] usb 3-1.4: Device is not authorized for usage
[64951.368029] usb 3-1.4: Device is not authorized for usage
[64959.445632] usb 3-1.4: Device is not authorized for usage
[64967.482630] usb 3-1.4: Device is not authorized for usage
[64975.595363] usb 3-1.4: Device is not authorized for usage
[64983.657756] usb 3-1.4: Device is not authorized for usage
[64991.737011] usb 3-1.4: Device is not authorized for usage
[64999.899606] usb 3-1.4: Device is not authorized for usage
[65007.862511] usb 3-1.4: Device is not authorized for usage
[65015.963475] usb 3-1.4: Device is not authorized for usage
[65024.057347] usb 3-1.4: Device is not authorized for usage
[65032.135400] usb 3-1.4: Device is not authorized for usage
[65040.229867] usb 3-1.4: Device is not authorized for usage
[65048.262355] usb 3-1.4: Device is not authorized for usage
[65056.389055] usb 3-1.4: Device is not authorized for usage
[65064.495226] usb 3-1.4: Device is not authorized for usage
[65072.541246] usb 3-1.4: Device is not authorized for usage
[65080.643034] usb 3-1.4: Device is not authorized for usage
[65088.704814] usb 3-1.4: Device is not authorized for usage
[65096.829456] usb 3-1.4: Device is not authorized for usage
[65104.828805] usb 3-1.4: Device is not authorized for usage
[65112.946587] usb 3-1.4: Device is not authorized for usage
[65121.003599] usb 3-1.4: Device is not authorized for usage
[65129.115278] usb 3-1.4: Device is not authorized for usage
[65137.128038] usb 3-1.4: Device is not authorized for usage
[65145.278555] usb 3-1.4: Device is not authorized for usage
[65153.353447] usb 3-1.4: Device is not authorized for usage
[65161.449727] usb 3-1.4: Device is not authorized for usage
[65169.505636] usb 3-1.4: Device is not authorized for usage
[65177.596540] usb 3-1.4: Device is not authorized for usage
[65185.649660] usb 3-1.4: Device is not authorized for usage
[65193.730244] usb 3-1.4: Device is not authorized for usage
[65201.884424] usb 3-1.4: Device is not authorized for usage
[65209.919075] usb 3-1.4: Device is not authorized for usage
[65217.978225] usb 3-1.4: Device is not authorized for usage
[65226.054638] usb 3-1.4: Device is not authorized for usage
[65234.146550] usb 3-1.4: Device is not authorized for usage
[65242.259567] usb 3-1.4: Device is not authorized for usage
[65250.400400] usb 3-1.4: Device is not authorized for usage
[65258.452855] usb 3-1.4: Device is not authorized for usage
[65266.626071] usb 3-1.4: Device is not authorized for usage
[65274.603949] usb 3-1.4: Device is not authorized for usage
[65282.616603] usb 3-1.4: Device is not authorized for usage
[65290.677500] usb 3-1.4: Device is not authorized for usage
[65298.787206] usb 3-1.4: Device is not authorized for usage
[65306.886099] usb 3-1.4: Device is not authorized for usage
[65314.930033] usb 3-1.4: Device is not authorized for usage
[65323.034730] usb 3-1.4: Device is not authorized for usage
[65331.165649] usb 3-1.4: Device is not authorized for usage
[65339.238183] usb 3-1.4: Device is not authorized for usage
[65347.287108] usb 3-1.4: Device is not authorized for usage
[65355.399650] usb 3-1.4: Device is not authorized for usage
[65363.493269] usb 3-1.4: Device is not authorized for usage
[65371.604535] usb 3-1.4: Device is not authorized for usage
[65379.656189] usb 3-1.4: Device is not authorized for usage
[65387.724005] usb 3-1.4: Device is not authorized for usage
[65395.834199] usb 3-1.4: Device is not authorized for usage
[65403.875365] usb 3-1.4: Device is not authorized for usage
[65412.030211] usb 3-1.4: Device is not authorized for usage
[65420.059813] usb 3-1.4: Device is not authorized for usage
[65428.191248] usb 3-1.4: Device is not authorized for usage
[65436.234798] usb 3-1.4: Device is not authorized for usage
[65444.292099] usb 3-1.4: Device is not authorized for usage
[65452.342716] usb 3-1.4: Device is not authorized for usage
[65460.398434] usb 3-1.4: Device is not authorized for usage
[65468.632084] usb 3-1.4: Device is not authorized for usage
[65476.589935] usb 3-1.4: Device is not authorized for usage
[65484.643351] usb 3-1.4: Device is not authorized for usage
[65492.726899] usb 3-1.4: Device is not authorized for usage
[65500.812035] usb 3-1.4: Device is not authorized for usage
[65508.872260] usb 3-1.4: Device is not authorized for usage
[65517.034177] usb 3-1.4: Device is not authorized for usage
[65525.050388] usb 3-1.4: Device is not authorized for usage
[65533.147950] usb 3-1.4: Device is not authorized for usage
[65541.219868] usb 3-1.4: Device is not authorized for usage
[65549.436734] usb 3-1.4: Device is not authorized for usage
[65557.383020] usb 3-1.4: Device is not authorized for usage
[65565.507908] usb 3-1.4: Device is not authorized for usage
[65573.544500] usb 3-1.4: Device is not authorized for usage
[65581.622226] usb 3-1.4: Device is not authorized for usage
[65589.663457] usb 3-1.4: Device is not authorized for usage
[65597.770342] usb 3-1.4: Device is not authorized for usage
[65605.785613] usb 3-1.4: Device is not authorized for usage
[65613.896796] usb 3-1.4: Device is not authorized for usage
[65621.965052] usb 3-1.4: Device is not authorized for usage
[65623.761135] usb 3-1.4: cannot submit urb (err = -19)
[65623.766333] usb 3-1.4: cannot submit urb 0, error -19: no device
[65623.785225] tps6598x 0-003f: The interrupt is masked , how did it fire ?? 380100a
[65627.321207] edt_ft5x06 2-0038: Unable to fetch data, error: -6
[65983.543468] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43752-sdio for chip BCM43752/2
[65988.691672] brcmfmac: brcmf_c_process_txcap_blob: no txcap_blob available (err=-2)
[65988.701795] brcmfmac: brcmf_c_preinit_dcmds: Firmware: BCM43752/2 wl0: Jul 13 2020 18:32:45 version 18.35.387.23.7 (b328500@shgit) (wlan=r880297) FWID 01-f50fdff0
[65991.151938] ieee80211 phy1: brcmf_p2p_create_p2pdev: timeout occurred
[65991.158423] ieee80211 phy1: brcmf_cfg80211_add_iface: add iface p2p-dev-wlan0 type 10 failed: err=-5
[66898.837465] edt_ft5x06 2-0038: Unable to fetch data, error: -6
[67567.894065] edt_ft5x06 2-0038: Unable to fetch data, error: -6
[68124.641850] edt_ft5x06 2-0038: Unable to fetch data, error: -6
[72890.722143] edt_ft5x06 2-0038: Unable to fetch data, error: -6
The kernel was updated recently.
$ uname -a
Linux pureos 6.6.0-1-librem5 #1 SMP PREEMPT Mon May 6 16:09:52 EDT 2024 aarch64 GNU/Linux
It occurred again today. I booted the phone, connected it to a USB-C display, opened a flatpak GNOME Web, clicked this forum to load, opened Files, opened a text file with gedit, and then GNOME Web failed to load the page with “Socket I/O timed out”. I launched the terminal and issued sudo dmesg, which hung and did not return the shell. I opened another tab and collected journalctl -b. Below is the output of journalctl -b -p 0..3 --no-pager. Hardware kill switches did not work.
-- Journal begins at Fri 2024-05-17 09:54:08 EEST, ends at Fri 2024-05-17 19:09:12 EEST. --
May 17 18:49:05 pureos systemd-modules-load[429]: Failed to find module 'lp'
May 17 18:49:05 pureos systemd-modules-load[429]: Failed to find module 'ppdev'
May 17 18:49:05 pureos systemd-modules-load[429]: Failed to find module 'parport_pc'
May 17 18:49:06 pureos kernel: debugfs: File 'Capture' in directory 'dapm' already present!
May 17 18:49:06 pureos kernel: brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43752-sdio for chip BCM43752/2
May 17 18:49:07 pureos systemd-udevd[467]: sda1: /usr/lib/udev/rules.d/85-librem5-storage.rules:7 Failed to write ATTR{/sys/devices/platform/soc@0/38200000.usb/xhci-hcd.4.auto/usb1/1-1/1-1.1/1-1.1:1.0/host0/target0:0:0/0:0:0:0/block/sda/sda1/queue/rotational}, ignoring: No such file or directory
May 17 18:49:10 pureos pipewire[793]: Failed to receive portal pid: org.freedesktop.DBus.Error.NameHasNoOwner: Could not get PID of name 'org.freedesktop.portal.Desktop': no such name
May 17 18:49:11 pureos kernel: brcmfmac: brcmf_c_process_txcap_blob: no txcap_blob available (err=-2)
May 17 18:49:11 pureos kernel: brcmfmac: brcmf_c_preinit_dcmds: Firmware: BCM43752/2 wl0: Jul 13 2020 18:32:45 version 18.35.387.23.7 (b328500@shgit) (wlan=r880297) FWID 01-f50fdff0
May 17 18:49:12 pureos bluetoothd[931]: profiles/sap/server.c:sap_server_register() Sap driver initialization failed.
May 17 18:49:12 pureos bluetoothd[931]: sap-server: Operation not permitted (1)
May 17 18:49:12 pureos pulseaudio[794]: Found duplicated D-Bus path for adapter /org/bluez/hci0
May 17 18:49:12 pureos pulseaudio[794]: Found duplicated D-Bus path for device /org/bluez/hci0/dev_34_88_5D_80_F2_24
May 17 18:49:12 pureos bluetoothd[931]: Set device flags return status: Invalid Parameters
May 17 18:49:14 pureos kernel: ieee80211 phy0: brcmf_p2p_create_p2pdev: timeout occurred
May 17 18:49:14 pureos kernel: ieee80211 phy0: brcmf_cfg80211_add_iface: add iface p2p-dev-wlan0 type 10 failed: err=-5
May 17 18:49:14 pureos wpa_supplicant[631]: Failed to create interface p2p-dev-wlan0: -5 (Input/output error)
May 17 18:49:14 pureos wpa_supplicant[631]: nl80211: Failed to create a P2P Device interface p2p-dev-wlan0
May 17 18:49:28 pureos kernel: Unable to handle kernel paging request at virtual address 0000656361667265
May 17 18:49:28 pureos kernel: Mem abort info:
May 17 18:49:28 pureos kernel: ESR = 0x0000000096000004
May 17 18:49:28 pureos kernel: EC = 0x25: DABT (current EL), IL = 32 bits
May 17 18:49:28 pureos kernel: SET = 0, FnV = 0
May 17 18:49:28 pureos kernel: EA = 0, S1PTW = 0
May 17 18:49:28 pureos kernel: FSC = 0x04: level 0 translation fault
May 17 18:49:28 pureos kernel: Data abort info:
May 17 18:49:28 pureos kernel: ISV = 0, ISS = 0x00000004, ISS2 = 0x00000000
May 17 18:49:28 pureos kernel: CM = 0, WnR = 0, TnD = 0, TagAccess = 0
May 17 18:49:28 pureos kernel: GCS = 0, Overlay = 0, DirtyBit = 0, Xs = 0
May 17 18:49:28 pureos kernel: user pgtable: 4k pages, 48-bit VAs, pgdp=000000005da6a000
May 17 18:49:28 pureos kernel: [0000656361667265] pgd=0000000000000000, p4d=0000000000000000
May 17 18:49:28 pureos kernel: Internal error: Oops: 0000000096000004 [#1] PREEMPT SMP
May 17 18:49:28 pureos kernel: power_supply max170xx_battery: driver failed to report `status' property: -110
May 17 18:49:28 pureos kernel: power_supply max170xx_battery: driver failed to report `charge_now' property: -110
May 17 18:49:28 pureos kernel: Code: 92402c04 b200c3e8 f13fc09f 5400088c (a9400c02)
May 17 18:49:28 pureos kernel: usb 3-1: Device is not authorized for usage
May 17 18:49:28 pureos kernel: usb 4-1: Device is not authorized for usage
May 17 18:49:29 pureos kernel: usb 3-1.1: Device is not authorized for usage
May 17 18:49:29 pureos kernel: usb 4-1.3: Device is not authorized for usage
May 17 18:49:29 pureos kernel: usb 3-1.3: Device is not authorized for usage
May 17 18:49:30 pureos kernel: usb 3-1.4: Device is not authorized for usage
May 17 18:50:22 pureos systemd[1]: Failed to start Network Manager Wait Online.
May 17 18:54:03 pureos systemd[753]: Failed to start flatpak portal.
May 17 18:55:28 pureos systemd[1]: Failed to start Hostname Service.
May 17 19:05:43 pureos systemd[1]: Failed to start Hostname Service.
Today I had a call drop and then I went to run sudo dmesg, but it hung. Then I tried to run sudo journalctl and it hung also. So then I tried pinging the device and it failed. This leads me to think that this network device or its drivers is causing the majority of the problems.
Yeah, I just tried sudo -i and it hangs too. When I try to pull down the top of the screen and turn off the software switch for wifi, it doesn’t actually turn off. How do I know what type of WLAN card I have? That seems to be the most likely culprit. As an experiment, I’m going to use the hardware switch for the wireless chip and see if that makes the issues go away.
Also rebooting takes forever! It’s possible this portion may have to do with trying to mount a local share.
I see a lot of logging. Probably this is one way of determining the card you have. The Redpine module was used before the Sparklan module.
I see exactly the same with the WiFi switch not working.
And also with the long time for reboots. Actually, I thought it did not reboot at all and I long press the power button. The first time the Librem 5 boots after that it is sometimes still in a strange state.