linux-emcraft issueshttps://source.puri.sm/Librem5/linux-emcraft/-/issues2019-09-30T18:17:49Zhttps://source.puri.sm/Librem5/linux-emcraft/-/issues/39redpine wifi module not keepingup with scan requests2019-09-30T18:17:49ZGuido Guntherredpine wifi module not keepingup with scan requestsEpic: https://source.puri.sm/Librem5/use-cases/issues/2
Feature: https://source.puri.sm/Librem5/use-cases/issues/109
I was looking into why the signal strength never gets updated
and it seems the wifi driver is not keeping up with scan...Epic: https://source.puri.sm/Librem5/use-cases/issues/2
Feature: https://source.puri.sm/Librem5/use-cases/issues/109
I was looking into why the signal strength never gets updated
and it seems the wifi driver is not keeping up with scan requests:
```
$ journalctl -b 0 | grep -i scan
Apr 23 09:11:05 pureos wpa_supplicant[1492]: wlan0: Reject scan trigger since one is already pending
Apr 23 09:11:35 pureos wpa_supplicant[1492]: wlan0: Reject scan trigger since one is already pending
Apr 23 09:11:41 pureos NetworkManager[1991]: <debug> [1556010701.2887] device[0xaaaaefb668c0] (wlan0): wifi-scan: scanning requested but not allowed at this time
Apr 23 09:11:41 pureos NetworkManager[1991]: <debug> [1556010701.2889] device[0xaaaaefb668c0] (wlan0): wifi-scan: scheduled in 43 seconds (interval now 43 seconds)
Apr 23 09:12:05 pureos wpa_supplicant[1492]: wlan0: Reject scan trigger since one is already pending
Apr 23 09:12:24 pureos NetworkManager[1991]: <debug> [1556010744.2919] device[0xaaaaefb668c0] (wlan0): wifi-scan: scanning requested but not allowed at this time
Apr 23 09:12:24 pureos NetworkManager[1991]: <debug> [1556010744.2921] device[0xaaaaefb668c0] (wlan0): wifi-scan: scheduled in 43 seconds (interval now 43 seconds)
Apr 23 09:12:35 pureos wpa_supplicant[1492]: wlan0: Reject scan trigger since one is already pending
Apr 23 09:13:05 pureos wpa_supplicant[1492]: wlan0: Reject scan trigger since one is already pending
Apr 23 09:13:07 pureos NetworkManager[1991]: <debug> [1556010787.2897] device[0xaaaaefb668c0] (wlan0): wifi-scan: scanning requested but not allowed at this time
Apr 23 09:13:07 pureos NetworkManager[1991]: <debug> [1556010787.2898] device[0xaaaaefb668c0] (wlan0): wifi-scan: scheduled in 43 seconds (interval now 43 seconds)
Apr 23 09:13:35 pureos wpa_supplicant[1492]: wlan0: Reject scan trigger since one is already pending
Apr 23 09:13:47 pureos NetworkManager[1991]: <debug> [1556010827.5903] device[0xaaaaefb668c0] (wlan0): wifi-scan: scanning requested
Apr 23 09:13:47 pureos NetworkManager[1991]: <debug> [1556010827.5904] device[0xaaaaefb668c0] (wlan0): wifi-scan: no SSIDs to probe scan
Apr 23 09:13:47 pureos NetworkManager[1991]: <debug> [1556010827.5906] device[0xaaaaefb668c0] (wlan0): add_pending_action (1): 'wifi-scan'
Apr 23 09:13:47 pureos NetworkManager[1991]: <debug> [1556010827.5906] device[0xaaaaefb668c0] (wlan0): wifi-scan: scheduled in 43 seconds (interval now 63 seconds)
Apr 23 09:13:47 pureos wpa_supplicant[1492]: wlan0: Reject scan trigger since one is already pending
Apr 23 09:13:47 pureos NetworkManager[1991]: <debug> [1556010827.5940] sup-iface[0xaaaaefaab160,wlan0]: could not get scan request result: GDBus.Error:fi.w1.wpa_supplicant1.Interface.ScanError: Scan request rejected
Apr 23 09:14:05 pureos wpa_supplicant[1492]: wlan0: Reject scan trigger since one is already pending
Apr 23 09:14:35 pureos wpa_supplicant[1492]: wlan0: Reject scan trigger since one is already pending
Apr 23 09:15:05 pureos wpa_supplicant[1492]: wlan0: Reject scan trigger since one is already pending
Apr 23 09:15:35 pureos wpa_supplicant[1492]: wlan0: Reject scan trigger since one is already pending
Apr 23 09:16:05 pureos wpa_supplicant[1492]: wlan0: Reject scan trigger since one is already pending
Apr 23 09:16:36 pureos wpa_supplicant[1492]: wlan0: Reject scan trigger since one is already pending
Apr 23 09:17:06 pureos wpa_supplicant[1492]: wlan0: Reject scan trigger since one is already pending
Apr 23 09:17:36 pureos wpa_supplicant[1492]: wlan0: Reject scan trigger since one is already pending
Apr 23 09:18:06 pureos wpa_supplicant[1492]: wlan0: Reject scan trigger since one is already pending
```
This is
```
Linux pureos 4.18.11-g25a8cc5f #1 SMP PREEMPT Fri Apr 12 01:28:06 PDT 2019 aarch64 GNU/Linux
```https://source.puri.sm/Librem5/linux-emcraft/-/issues/27Resets on GSM network scans2019-06-23T12:22:20ZGuido GuntherResets on GSM network scansEven with a fan (#22) I can get it to reboot pretty easily (using the supplied wall wart or powered via a USB3 port) by just inserting a SIM card. I have bad reception here and the frequent network scans make the board reboot. This gets ...Even with a fan (#22) I can get it to reboot pretty easily (using the supplied wall wart or powered via a USB3 port) by just inserting a SIM card. I have bad reception here and the frequent network scans make the board reboot. This gets better once I stop modem manager as soon as I stop ModemManager.https://source.puri.sm/Librem5/linux-emcraft/-/issues/21Touchscreen controller driver constantly resets itself2019-01-31T09:00:45ZClayton CraftTouchscreen controller driver constantly resets itselfImmediately after the GTP driver is loaded on boot, the kernel log is spammed with these messages (multiple per second), quickly filling up the kernel log:
```
[ 11.343001] <<GTP-ERR>>[_do_i2c_write:428] I2c transfer error! (-6)
[ 1...Immediately after the GTP driver is loaded on boot, the kernel log is spammed with these messages (multiple per second), quickly filling up the kernel log:
```
[ 11.343001] <<GTP-ERR>>[_do_i2c_write:428] I2c transfer error! (-6)
[ 11.343003] <<GTP-INF>>[gt1x_reset_guitar:810] GTP RESET!
[ 11.446948] <<GTP-ERR>>[_do_i2c_write:428] I2c transfer error! (-6)
[ 11.446950] <<GTP-INF>>[gt1x_reset_guitar:810] GTP RESET!
```
[dmesg](/uploads/9cdf1cc614ed086697ac2e1ada58fa18/dmesg)https://source.puri.sm/Librem5/linux-emcraft/-/issues/20System unresponsive if Using HDMI But No Monitor Present2019-01-09T12:34:36ZEric KuzmenkoSystem unresponsive if Using HDMI But No Monitor PresentAt least on the test image shipped with the dev kits by default, the touch controller input is not very responsive if you are using the HDMI device tree but no monitor is connected to the mini-HDMI receptacle.At least on the test image shipped with the dev kits by default, the touch controller input is not very responsive if you are using the HDMI device tree but no monitor is connected to the mini-HDMI receptacle.https://source.puri.sm/Librem5/linux-emcraft/-/issues/19Pulseaudio fails to open SGTL5000 codec in stereo mode resulting in no audio ...2019-01-18T20:10:59ZBob HamPulseaudio fails to open SGTL5000 codec in stereo mode resulting in no audio from speakerPulseAudio fails to open the sgtl5000 card in stereo mode. On the devkit, the speaker is attached to the right line out channel rather than the left (/mono) channel and so there is no sound from PulseAudio.
```
Jan 07 16:04:32 pureos p...PulseAudio fails to open the sgtl5000 card in stereo mode. On the devkit, the speaker is attached to the right line out channel rather than the left (/mono) channel and so there is no sound from PulseAudio.
```
Jan 07 16:04:32 pureos pulseaudio[2443]: D: [pulseaudio] alsa-mixer.c: Looking at profile output:analog-stereo
Jan 07 16:04:32 pureos pulseaudio[2443]: D: [pulseaudio] alsa-mixer.c: Checking for playback on Analog Stereo (analog-stereo)
Jan 07 16:04:32 pureos pulseaudio[2443]: D: [pulseaudio] alsa-util.c: Trying front:0 with SND_PCM_NO_AUTO_FORMAT ...
Jan 07 16:04:32 pureos pulseaudio[2443]: I: [pulseaudio] (alsa-lib)conf.c: Unknown parameters 0
Jan 07 16:04:32 pureos pulseaudio[2443]: I: [pulseaudio] (alsa-lib)pcm.c: Unknown PCM front:0
Jan 07 16:04:32 pureos pulseaudio[2443]: I: [pulseaudio] alsa-util.c: Error opening PCM device front:0: Invalid argument
```
There is no "front" PCM device for the sgtl5000 which is what PulseAudio is trying to open:
```
purism@pureos:~$ aplay -L
null
Discard all samples (playback) or generate zero samples (capture)
jack
JACK Audio Connection Kit
pulse
PulseAudio Sound Server
default:CARD=sgtl5000
sgtl5000,
Default Audio Device
sysdefault:CARD=sgtl5000
sgtl5000,
Default Audio Device
dmix:CARD=sgtl5000,DEV=0
sgtl5000,
Direct sample mixing device
dsnoop:CARD=sgtl5000,DEV=0
sgtl5000,
Direct sample snooping device
hw:CARD=sgtl5000,DEV=0
sgtl5000,
Direct hardware device without any conversions
plughw:CARD=sgtl5000,DEV=0
sgtl5000,
Hardware device with all software conversions
usbstream:CARD=sgtl5000
sgtl5000
USB Stream Output
purism@pureos:~$
```
As I understand it, the "front" device is a standard PCM virtual device created by the default alsalib configuration, in `/usr/share/alsa/alsa.conf` and `/usr/share/alsa/pcm/`. I'm not sure yet why it's failing to create the "front" device for the sgtl5000 but presumably there will be something "standard" that's missing from the sgtl5000's driver.https://source.puri.sm/Librem5/linux-emcraft/-/issues/13GPU texture issues and hung tasks accessing the GPU2019-06-25T07:57:51ZBob HamGPU texture issues and hung tasks accessing the GPUThe GPU clearly has issues displaying textures. Please see this video:
![texture-issues](/uploads/860f22d7481ad74bbc122a313edb3d73/texture-issues.webm)
I presume this is a kernel DRM issue as these problems aren't present with phosh/r...The GPU clearly has issues displaying textures. Please see this video:
![texture-issues](/uploads/860f22d7481ad74bbc122a313edb3d73/texture-issues.webm)
I presume this is a kernel DRM issue as these problems aren't present with phosh/rootston on the Nitrogen board.https://source.puri.sm/Librem5/linux-emcraft/-/issues/9Nullpointer deref in redpine driver breaks Wifi2019-03-08T16:50:40ZJosh FlemingNullpointer deref in redpine driver breaks Wifi# What problem did you encounter
NetworkManager (or wpa_supplicant) Becomes unresponsive after connecting to wifi.
## What is the actual behaviour?
After connecting to wifi with nmtui, commands like: `ip addr` that depend on NetworkMana...# What problem did you encounter
NetworkManager (or wpa_supplicant) Becomes unresponsive after connecting to wifi.
## What is the actual behaviour?
After connecting to wifi with nmtui, commands like: `ip addr` that depend on NetworkManager sometimes don't respond. Also the wifi connection doesn't seem to actually connect after reboot.
## What is the expected behaviour?
After connecting wifi, connections should work after reboot, and `ip addr` and other commands should print expected results.
## How to reproduce
* Run through the steps to flash the main image here: https://developer.puri.sm/Librem5/Development_Environment/Boards/imx8.html
* Once the flash is complete reboot with ethernet, HDMI, and USB attached
* Connect to the device over USB with picocom as documented in the above linked documentation.
* Test `ip addr` get an expected response, also ping a known domain to test connectivity. Everything looks good at this point.
* Update with `apt update` then `apt upgrade`
* Reboot with reboot button
* Once again Connect over USB and test `ip addr` get an expected response, also ping a known domain to test connectivity. Everything still looks good.
* Use `nmtui` to connect to a wifi access point.
* Reboot with reboot button
* Try `ip addr` no response given, in fact ctrl-c won't quit the process.
* Reboot with reboot button
* Try `nmcli d s` devices are listed wifi is shown as disconnected
* `nmcli d wifi list` won't list any access points
* `nmcli d wifi rescan` returns `Error: Scanning not allowed while already scanning.`
* `nmtui` shows no wifi access points either.
* Pinging a domain returns no response and ctrl-c will not exit the process.
* Reboot with reboot button.
* Once the Reboot button is pressed the the GUI shell leaves the screen, but does not reboot. The three lights above the battery are all solid green.
* Unplug / Remove battery & Replug USB
* Try `nmcli d s` Response: `Error: Could not create NMClient object: Timeout was reached.`
* Run `systemctl status NetworkManager` results (included below) include a warning about "sup-iface" though the full warning is cut off
* Run `journalctl -xe` results (included below) include errors related to NetworkManager and wpa_supplicant
* At this point if I reboot I still have network access through ethernet, upon reboot I can look at nmtui which intermittently doesn't load at all or loats with no wifi access points, or loads claiming it's connected to my access point.
* With ethernet disconnected, if I ping an ip address it responds as unreachable, even when nmtui claims it's connected to an access point.
* Also booting with ethernet disconnected takes much longer than without. (at least once I've tried to connect to an access point) With ethernet connected The boot process is within 5-10 seconds until the GUI shows on the monitor. With ethernet disconnected, the boot process sits with the 4 penguins on the screen for just over 2 minutes. I'm assuming this is while it's attempting to find a network.
# What hardware are you running on?
Librem5 devkit
# Relevant OS information
## Which kernel are you using?
`Linux pureos 4.18.11-g59f358aa #1 SMP PREEMPT Tue Dec 18 13:54:35 PST 2018 aarch64 GNU/Linux`
## Which OS are you using?
``
PRETTY_NAME="Debian GNU/Linux buster/sid"
NAME="Debian GNU/Linux"
ID=debian
HOME_URL="https://www.debian.org/"
SUPPORT_URL="https://www.debian.org/support"
BUG_REPORT_URL="https://bugs.debian.org/"
``
## Any other information that may be helpful?
Depending on the nature of the issue, you may consider adding the output of:
* lsblk (for mounting issues)
* lsusb (for usb attachment issues)
```
# systemctl status NetworkManager
● NetworkManager.service - Network Manager
Loaded: loaded (/lib/systemd/system/NetworkManager.service; enabled; vendor p
Active: active (running) since Sun 2018-12-23 03:02:48 UTC; 2min 25s ago
Docs: man:NetworkManager(8)
Main PID: 2339 (NetworkManager)
Tasks: 3 (limit: 3216)
Memory: 10.4M
CGroup: /system.slice/NetworkManager.service
└─2339 /usr/sbin/NetworkManager --no-daemon
Dec 23 03:03:12 pureos dhclient[2793]: bound to 192.168.43.3 -- renewal in 1554
Dec 23 03:03:12 pureos NetworkManager[2339]: <info> [1545534192.4146] policy: s
Dec 23 03:03:12 pureos NetworkManager[2339]: <info> [1545534192.4178] device (w
Dec 23 03:03:12 pureos NetworkManager[2339]: <info> [1545534192.4273] manager:
Dec 23 03:03:15 pureos NetworkManager[2339]: <info> [1545534195.5804] supplican
Dec 23 03:03:15 pureos NetworkManager[2339]: <info> [1545534195.5806] device (w
Dec 23 03:03:15 pureos NetworkManager[2339]: <warn> [1545534195.5954] sup-iface
Dec 23 03:03:15 pureos NetworkManager[2339]: <info> [1545534195.5964] device (w
Dec 23 03:03:15 pureos NetworkManager[2339]: <info> [1545534195.6012] dhcp4 (wl
Dec 23 03:03:15 pureos NetworkManager[2339]: <info> [1545534195.6013] dhcp4 (wl
```
* any journalctl logs that look suspicious
```
# journalctl -xe
-- Unit UNIT has finished starting up.
--
-- The start-up result is RESULT.
Dec 23 03:03:09 pureos systemd[2764]: Startup finished in 164ms.
-- Subject: User manager start-up is now complete
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- The user manager instance for user 0 has been started. All services queued
-- for starting have been started. Note that other services might still be start
-- up or be started at any later time.
--
-- Startup of the manager took 164551 microseconds.
Dec 23 03:03:10 pureos login[2776]: ROOT LOGIN on '/dev/ttyGS0'
Dec 23 03:03:10 pureos systemd[2764]: Started D-Bus User Message Bus.
-- Subject: Unit UNIT has finished start-up
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- Unit UNIT has finished starting up.
--
-- The start-up result is RESULT.
Dec 23 03:03:10 pureos wpa_supplicant[2328]: wlan0: CTRL-EVENT-REGDOM-CHANGE ini
Dec 23 03:03:11 pureos wpa_supplicant[2328]: wlan0: SME: Trying to authenticate
Dec 23 03:03:11 pureos kernel: wlan0: authenticate with 02:1a:11:f7:78:9b
Dec 23 03:03:11 pureos kernel: wlan0: send auth to 02:1a:11:f7:78:9b (try 1/3)
Dec 23 03:03:11 pureos wpa_supplicant[2328]: wlan0: Trying to associate with 02:
Dec 23 03:03:11 pureos kernel: wlan0: authenticated
Dec 23 03:03:11 pureos kernel: wlan0: associate with 02:1a:11:f7:78:9b (try 1/3)
Dec 23 03:03:11 pureos wpa_supplicant[2328]: wlan0: Associated with 02:1a:11:f7:
Dec 23 03:03:11 pureos wpa_supplicant[2328]: wlan0: CTRL-EVENT-SUBNET-STATUS-UPD
Dec 23 03:03:11 pureos kernel: wlan0: RX AssocResp from 02:1a:11:f7:78:9b (capab
Dec 23 03:03:11 pureos kernel: wlan0: associated
Dec 23 03:03:11 pureos NetworkManager[2339]: <info> [1545534191.8545] device (w
Dec 23 03:03:11 pureos NetworkManager[2339]: <info> [1545534191.8628] device (w
Dec 23 03:03:11 pureos kernel: wlan0: Limiting TX power to 30 (30 - 0) dBm as ad
Dec 23 03:03:11 pureos wpa_supplicant[2328]: wlan0: CTRL-EVENT-SIGNAL-CHANGE abo
Dec 23 03:03:12 pureos NetworkManager[2339]: <info> [1545534192.0038] device (w
Dec 23 03:03:12 pureos kernel: rsi_91x: EAPOL 4 confirm
Dec 23 03:03:12 pureos kernel: rsi_91x: rsi_hal_key_config: Cipher 0xfac04 key_t
Dec 23 03:03:12 pureos kernel: rsi_91x: rsi_mac80211_set_key: RSI set_key
Dec 23 03:03:12 pureos wpa_supplicant[2328]: wlan0: WPA: Key negotiation complet
Dec 23 03:03:12 pureos wpa_supplicant[2328]: wlan0: CTRL-EVENT-CONNECTED - Conne
Dec 23 03:03:12 pureos systemd-networkd[2267]: wlan0: Gained carrier
Dec 23 03:03:12 pureos kernel: rsi_91x: rsi_hal_key_config: Cipher 0xfac04 key_t
Dec 23 03:03:12 pureos kernel: rsi_91x: rsi_mac80211_set_key: RSI set_key
Dec 23 03:03:12 pureos kernel: IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link become
Dec 23 03:03:12 pureos NetworkManager[2339]: <info> [1545534192.0382] device (w
Dec 23 03:03:12 pureos NetworkManager[2339]: <info> [1545534192.0383] device (w
Dec 23 03:03:12 pureos NetworkManager[2339]: <info> [1545534192.0402] device (w
Dec 23 03:03:12 pureos NetworkManager[2339]: <info> [1545534192.0428] dhcp4 (wl
Dec 23 03:03:12 pureos NetworkManager[2339]: <info> [1545534192.0482] dhcp4 (wl
Dec 23 03:03:12 pureos dhclient[2793]: DHCPREQUEST for 192.168.43.3 on wlan0 to
Dec 23 03:03:12 pureos dhclient[2793]: DHCPACK of 192.168.43.3 from 192.168.43.1
Dec 23 03:03:12 pureos NetworkManager[2339]: <info> [1545534192.3899] dhcp4 (wl
Dec 23 03:03:12 pureos NetworkManager[2339]: <info> [1545534192.3902] dhcp4 (wl
Dec 23 03:03:12 pureos NetworkManager[2339]: <info> [1545534192.3903] dhcp4 (wl
Dec 23 03:03:12 pureos NetworkManager[2339]: <info> [1545534192.3903] dhcp4 (wl
Dec 23 03:03:12 pureos NetworkManager[2339]: <info> [1545534192.3904] dhcp4 (wl
Dec 23 03:03:12 pureos NetworkManager[2339]: <info> [1545534192.3904] dhcp4 (wl
Dec 23 03:03:12 pureos NetworkManager[2339]: <info> [1545534192.3904] dhcp4 (wl
Dec 23 03:03:12 pureos NetworkManager[2339]: <info> [1545534192.3971] device (w
Dec 23 03:03:12 pureos NetworkManager[2339]: <info> [1545534192.4004] device (w
Dec 23 03:03:12 pureos NetworkManager[2339]: <info> [1545534192.4013] device (w
Dec 23 03:03:12 pureos dhclient[2793]: bound to 192.168.43.3 -- renewal in 1554
Dec 23 03:03:12 pureos NetworkManager[2339]: <info> [1545534192.4146] policy: s
Dec 23 03:03:12 pureos NetworkManager[2339]: <info> [1545534192.4178] device (w
Dec 23 03:03:12 pureos gsd-sharing[2551]: Failed to StopUnit service: GDBus.Erro
Dec 23 03:03:12 pureos gsd-sharing[2551]: Failed to StopUnit service: GDBus.Erro
Dec 23 03:03:12 pureos gsd-sharing[2551]: Failed to StopUnit service: GDBus.Erro
Dec 23 03:03:12 pureos gsd-sharing[2551]: Failed to StopUnit service: GDBus.Erro
Dec 23 03:03:12 pureos dbus-daemon[2311]: [system] Activating via systemd: servi
Dec 23 03:03:12 pureos NetworkManager[2339]: <info> [1545534192.4273] manager:
Dec 23 03:03:12 pureos systemd[1]: Starting Network Manager Script Dispatcher Se
-- Subject: Unit NetworkManager-dispatcher.service has begun start-up
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- Unit NetworkManager-dispatcher.service has begun starting up.
Dec 23 03:03:12 pureos wpa_supplicant[2328]: wlan0: CTRL-EVENT-SIGNAL-CHANGE abo
Dec 23 03:03:12 pureos dbus-daemon[2311]: [system] Successfully activated servic
Dec 23 03:03:12 pureos systemd[1]: Started Network Manager Script Dispatcher Ser
-- Subject: Unit NetworkManager-dispatcher.service has finished start-up
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- Unit NetworkManager-dispatcher.service has finished starting up.
--
-- The start-up result is RESULT.
Dec 23 03:03:12 pureos nm-dispatcher[2803]: req:1 'up' [wlan0]: new request (1 s
Dec 23 03:03:12 pureos nm-dispatcher[2803]: req:1 'up' [wlan0]: start running or
Dec 23 03:03:12 pureos nm-dispatcher[2803]: req:2 'connectivity-change': new req
Dec 23 03:03:12 pureos nm-dispatcher[2803]: req:2 'connectivity-change': start r
Dec 23 03:03:13 pureos systemd-networkd[2267]: wlan0: Gained IPv6LL
Dec 23 03:03:15 pureos wpa_supplicant[2328]: wlan0: CTRL-EVENT-SIGNAL-CHANGE abo
Dec 23 03:03:15 pureos kernel: Unable to handle kernel NULL pointer dereference
Dec 23 03:03:15 pureos kernel: Mem abort info:
Dec 23 03:03:15 pureos kernel: ESR = 0x96000004
Dec 23 03:03:15 pureos kernel: Exception class = DABT (current EL), IL = 32 bi
Dec 23 03:03:15 pureos kernel: SET = 0, FnV = 0
Dec 23 03:03:15 pureos kernel: EA = 0, S1PTW = 0
Dec 23 03:03:15 pureos kernel: Data abort info:
Dec 23 03:03:15 pureos kernel: ISV = 0, ISS = 0x00000004
Dec 23 03:03:15 pureos kernel: CM = 0, WnR = 0
Dec 23 03:03:15 pureos kernel: user pgtable: 4k pages, 48-bit VAs, pgdp = 000000
Dec 23 03:03:15 pureos kernel: [00000000000000d0] pgd=0000000000000000
Dec 23 03:03:15 pureos kernel: Internal error: Oops: 96000004 [#1] PREEMPT SMP
Dec 23 03:03:15 pureos kernel: Modules linked in: aes_ce_ccm qmi_wwan cdc_wdm us
Dec 23 03:03:15 pureos kernel: CPU: 2 PID: 2328 Comm: wpa_supplicant Not tainted
Dec 23 03:03:15 pureos kernel: Hardware name: Purism Librem 5 devkit (DT)
Dec 23 03:03:15 pureos kernel: pstate: 20000005 (nzCv daif -PAN -UAO)
Dec 23 03:03:15 pureos kernel: pc : rsi_send_probe_request+0x16c/0x328 [rsi_91x]
Dec 23 03:03:15 pureos kernel: lr : rsi_send_probe_request+0x158/0x328 [rsi_91x]
Dec 23 03:03:15 pureos kernel: sp : ffff8000a1eaf7e0
Dec 23 03:03:15 pureos kernel: x29: ffff8000a1eaf7e0 x28: ffff80008c9c8bb8
Dec 23 03:03:15 pureos kernel: x27: ffff8000a73c30c8 x26: ffff80008c9c8bb8
Dec 23 03:03:15 pureos kernel: x25: ffff8000a73c23d9 x24: 0000000000000000
Dec 23 03:03:15 pureos kernel: x23: 000000000000007a x22: ffff8000a1f92c40
Dec 23 03:03:15 pureos kernel: x21: 0000000000000001 x20: ffff8000a73c2000
Dec 23 03:03:15 pureos kernel: x19: 000000000000000e x18: ffff000008b76000
Dec 23 03:03:15 pureos kernel: x17: 0000000000000000 x16: 0000000000000000
Dec 23 03:03:15 pureos kernel: x15: ffff8000a1f92c00 x14: 0100000000000000
Dec 23 03:03:15 pureos kernel: x13: 00000000ff01006e x12: 1a2d6c6048302418
Dec 23 03:03:15 pureos kernel: x11: 120c080100000000 x10: 0000000000000100
Dec 23 03:03:15 pureos kernel: x9 : 0000000000000000 x8 : 0000ff01006e1a2d
Dec 23 03:03:15 pureos kernel: x7 : 6c60483004322418 x6 : ffff8000a73c242b
Dec 23 03:03:15 pureos kernel: x5 : ffff8000abf85e30 x4 : 0000000000000008
Dec 23 03:03:15 pureos kernel: x3 : 0000000000000000 x2 : ffffffffffffffca
Dec 23 03:03:15 pureos kernel: x1 : ffff8000a1f92e4a x0 : ffff8000a73c23d9
Dec 23 03:03:15 pureos kernel: Process wpa_supplicant (pid: 2328, stack limit =
Dec 23 03:03:15 pureos kernel: Call trace:
Dec 23 03:03:15 pureos kernel: rsi_send_probe_request+0x16c/0x328 [rsi_91x]
Dec 23 03:03:15 pureos kernel: rsi_mac80211_hw_scan_start+0x168/0x200 [rsi_91x]
Dec 23 03:03:15 pureos kernel: __ieee80211_start_scan+0x260/0x818
Dec 23 03:03:15 pureos kernel: ieee80211_request_scan+0x34/0x58
Dec 23 03:03:15 pureos kernel: ieee80211_scan+0x58/0xd0
Dec 23 03:03:15 pureos kernel: nl80211_trigger_scan+0x5ac/0x820
Dec 23 03:03:15 pureos kernel: genl_family_rcv_msg+0x248/0x368
Dec 23 03:03:15 pureos kernel: genl_rcv_msg+0x60/0xa8
Dec 23 03:03:15 pureos kernel: netlink_rcv_skb+0xf0/0x138
Dec 23 03:03:15 pureos kernel: genl_rcv+0x3c/0x50
Dec 23 03:03:15 pureos kernel: netlink_unicast+0x198/0x218
Dec 23 03:03:15 pureos kernel: netlink_sendmsg+0x274/0x340
Dec 23 03:03:15 pureos kernel: sock_sendmsg+0x34/0x50
Dec 23 03:03:15 pureos kernel: ___sys_sendmsg+0x28c/0x2b8
Dec 23 03:03:15 pureos kernel: __sys_sendmsg+0x78/0xd0
Dec 23 03:03:15 pureos kernel: sys_sendmsg+0x38/0x48
Dec 23 03:03:15 pureos kernel: el0_svc_naked+0x30/0x34
Dec 23 03:03:15 pureos kernel: Code: 54fffba1 110062f7 7101e2ff 540002c9 (f9406b
Dec 23 03:03:15 pureos kernel: ---[ end trace 15322be8d420ef7f ]---
Dec 23 03:03:15 pureos systemd[1]: wpa_supplicant.service: Main process exited,
Dec 23 03:03:15 pureos systemd[1]: wpa_supplicant.service: Failed with result 's
Dec 23 03:03:15 pureos NetworkManager[2339]: <info> [1545534195.5804] supplican
Dec 23 03:03:15 pureos NetworkManager[2339]: <info> [1545534195.5806] device (w
Dec 23 03:03:15 pureos NetworkManager[2339]: <warn> [1545534195.5954] sup-iface
Dec 23 03:03:15 pureos NetworkManager[2339]: <info> [1545534195.5964] device (w
Dec 23 03:03:15 pureos NetworkManager[2339]: <info> [1545534195.6012] dhcp4 (wl
Dec 23 03:03:15 pureos NetworkManager[2339]: <info> [1545534195.6013] dhcp4 (wl
```