linux issueshttps://source.puri.sm/Librem5/linux/-/issues2023-12-07T17:48:28Zhttps://source.puri.sm/Librem5/linux/-/issues/3Need earpiece support2023-12-07T17:48:28ZHeather EllsworthNeed earpiece supportFeature: https://source.puri.sm/Librem5/use-cases/issues/79, https://source.puri.sm/Librem5/use-cases/issues/108
There needs to be support for the Librem 5's earpiece added into the kernel.
Feature: https://source.puri.sm/Librem5/use-cases/issues/79, https://source.puri.sm/Librem5/use-cases/issues/108
There needs to be support for the Librem 5's earpiece added into the kernel.
Heather EllsworthHeather Ellsworthhttps://source.puri.sm/Librem5/linux/-/issues/45: Need microphone support2023-12-07T17:48:29ZHeather Ellsworth5: Need microphone supportFeature: https://source.puri.sm/Librem5/use-cases/issues/79
There needs to be support for the Librem 5's microphone added into the kernel.Feature: https://source.puri.sm/Librem5/use-cases/issues/79
There needs to be support for the Librem 5's microphone added into the kernel.https://source.puri.sm/Librem5/linux/-/issues/52: Need headphone and microphone support2023-07-20T12:51:59ZHeather Ellsworth2: Need headphone and microphone supportFeature: https://source.puri.sm/Librem5/use-cases/issues/79
There needs to be support for the Librem 5's headphone jack added into the kernel.
This means detecting an included analogue microphone independently of the headphones (where ...Feature: https://source.puri.sm/Librem5/use-cases/issues/79
There needs to be support for the Librem 5's headphone jack added into the kernel.
This means detecting an included analogue microphone independently of the headphones (where detection works).https://source.puri.sm/Librem5/linux/-/issues/6Need modem-audio support2023-07-20T12:52:00ZHeather EllsworthNeed modem-audio supportFeature: https://source.puri.sm/Librem5/use-cases/issues/79
There needs to be support for the Librem 5's modem audio added into the kernel.Feature: https://source.puri.sm/Librem5/use-cases/issues/79
There needs to be support for the Librem 5's modem audio added into the kernel.Last: Fuschia (W30-32)Angus Ainslieangus.ainslie@puri.smAngus Ainslieangus.ainslie@puri.smhttps://source.puri.sm/Librem5/linux/-/issues/7Kernel support for power management2024-03-07T05:40:28ZHeather EllsworthKernel support for power managementProper kernel support should exist for controlling the hardware's power on the Librem 5.
Deliverable: https://source.puri.sm/Librem5/deliverables-for-the-librem5-release/issues/2Proper kernel support should exist for controlling the hardware's power on the Librem 5.
Deliverable: https://source.puri.sm/Librem5/deliverables-for-the-librem5-release/issues/2Angus Ainslieangus.ainslie@puri.smAngus Ainslieangus.ainslie@puri.smhttps://source.puri.sm/Librem5/linux/-/issues/8nmcli reports "Error: Connection activation failed: (0) No reason given."2024-03-07T05:40:29ZAngus Ainslieangus.ainslie@puri.smnmcli reports "Error: Connection activation failed: (0) No reason given."Epic: https://source.puri.sm/Librem5/use-cases/issues/2
nmcli can't connect to a wifi network. This is with the 5.1-rc5
https://source.puri.sm/Librem5/linux-next/tree/f/5.1/plus_rsi
The driver seems to scan and find access points but r...Epic: https://source.puri.sm/Librem5/use-cases/issues/2
nmcli can't connect to a wifi network. This is with the 5.1-rc5
https://source.puri.sm/Librem5/linux-next/tree/f/5.1/plus_rsi
The driver seems to scan and find access points but refuses to connect
```
root@pureos:~# nmcli -v
nmcli tool, version 1.14.6
root@pureos:~# nmcli radio
WIFI-HW WIFI WWAN-HW WWAN
enabled enabled enabled enabled
root@pureos:~# nmcli device
DEVICE TYPE STATE CONNECTION
eth0 ethernet connected Wired connection 1
ttyUSB2 gsm disconnected --
wlan0 wifi disconnected --
lo loopback unmanaged --
root@pureos:~# nmcli device wifi rescan
root@pureos:~# [ 380.522871] rsi_91x: Antenna is changed to 2
nmcli device wifi list
IN-USE SSID MODE CHAN RATE SIGNAL BARS SECURITY
root@pureos:~# nmcli device wifi list
IN-USE SSID MODE CHAN RATE SIGNAL BARS SECURITY
Studio Infra 2 405 Mbit/s 100 ???? WPA2
Studio Infra 44 405 Mbit/s 89 ???? WPA2
-- Infra 6 405 Mbit/s 42 ??__ WPA2
Hilltop Infra 6 405 Mbit/s 42 ??__ WPA2
Hilltop2_up Infra 6 405 Mbit/s 39 ??__ WPA2
Hilltop2 Infra 9 405 Mbit/s 37 ??__ WPA2
Hilltop Infra 9 405 Mbit/s 37 ??__ WPA2
-- Infra 9 405 Mbit/s 35 ??__ WPA2
-- Infra 36 270 Mbit/s 14 ?___ WPA2
Hilltop Infra 36 270 Mbit/s 14 ?___ WPA2
-- Infra 36 130 Mbit/s 12 ?___ WPA2
Hilltop Infra 149 270 Mbit/s 9 ?___ WPA2
-- Infra 149 270 Mbit/s 9 ?___ WPA2
-- Infra 1 130 Mbit/s 0 ____ WPA2
root@pureos:~# nmcli device wifi connect Studio password xxxpasswordxxx
Error: Connection activation failed: (0) No reason given.
root@pureos:~# [ 481.092329] rsi_91x: Antenna is changed to 3
```Angus Ainslieangus.ainslie@puri.smAngus Ainslieangus.ainslie@puri.smhttps://source.puri.sm/Librem5/linux/-/issues/9Upstream the librem5 v5 devkit devicetree2024-03-07T05:40:29ZAngus Ainslieangus.ainslie@puri.smUpstream the librem5 v5 devkit devicetreeRelated feature: https://source.puri.sm/Librem5/use-cases/issues/56
Submit the librem5 devkit devicetree v5 changes to mainline.Related feature: https://source.puri.sm/Librem5/use-cases/issues/56
Submit the librem5 devkit devicetree v5 changes to mainline.Past: W16-18Angus Ainslieangus.ainslie@puri.smAngus Ainslieangus.ainslie@puri.smhttps://source.puri.sm/Librem5/linux/-/issues/11Write a devicetree for the librem5 phone2023-07-20T12:52:03ZAngus Ainslieangus.ainslie@puri.smWrite a devicetree for the librem5 phoneNeed to have a device tree to properly configure the phone
This is work for feature https://source.puri.sm/Librem5/use-cases/issues/57Need to have a device tree to properly configure the phone
This is work for feature https://source.puri.sm/Librem5/use-cases/issues/57Last: Romneya (W26-28)Angus Ainslieangus.ainslie@puri.smAngus Ainslieangus.ainslie@puri.smhttps://source.puri.sm/Librem5/linux/-/issues/12dwc3 gadget driver causes resume to fail2023-12-07T17:48:25ZAngus Ainslieangus.ainslie@puri.smdwc3 gadget driver causes resume to failFeature: https://source.puri.sm/Librem5/use-cases/issues/75
If the dwc3 driver is load during suspend to mem then resume will fail
depending issue: https://source.puri.sm/Librem5/linux-next/issues/64Feature: https://source.puri.sm/Librem5/use-cases/issues/75
If the dwc3 driver is load during suspend to mem then resume will fail
depending issue: https://source.puri.sm/Librem5/linux-next/issues/64Martin KepplingerMartin Kepplingerhttps://source.puri.sm/Librem5/linux/-/issues/13gpio-keys can't wake system2023-07-20T12:52:03ZAngus Ainslieangus.ainslie@puri.smgpio-keys can't wake systemPressing the keys doesn't wake the system from suspendPressing the keys doesn't wake the system from suspendPast: Tulip (W20 - 22)https://source.puri.sm/Librem5/linux/-/issues/14Upstream the librem5 v7 devkit devicetree2023-07-20T12:52:03ZAngus Ainslieangus.ainslie@puri.smUpstream the librem5 v7 devkit devicetreeRelated feature: use-cases#56
Submit the librem5 devkit devicetree v7 changes to mainline.Related feature: use-cases#56
Submit the librem5 devkit devicetree v7 changes to mainline.Past: Something SillyAngus Ainslieangus.ainslie@puri.smAngus Ainslieangus.ainslie@puri.smhttps://source.puri.sm/Librem5/linux/-/issues/15Get all the branches together2023-10-03T16:17:36ZGuido GuntherGet all the branches togetherFeature: https://source.puri.sm/Librem5/linux-next/issues/28
Let's get a linux-next with all the stuff:
- [x] linux-next: https://source.puri.sm/guido.gunther/linux-imx8/tree/f/next-20190430/devkit
- [x] nwl+mixel+dcss+imx-display-subs...Feature: https://source.puri.sm/Librem5/linux-next/issues/28
Let's get a linux-next with all the stuff:
- [x] linux-next: https://source.puri.sm/guido.gunther/linux-imx8/tree/f/next-20190430/devkit
- [x] nwl+mixel+dcss+imx-display-subsystem: https://source.puri.sm/guido.gunther/linux-imx8/find_file/f/next-20190430/devkit-drm-integration/v1-wip
- [x] etnaviv bo reloc hack (https://source.puri.sm/guido.gunther/linux-imx8/tree/imx8-4.18-drm-bo-reloc): https://source.puri.sm/guido.gunther/linux-imx8/tree/imx8-5.x-drm
- [x] @angus.ainslie branchesPast: Something Sillyhttps://source.puri.sm/Librem5/linux/-/issues/16Suspend and resume the devkit2023-07-20T12:52:03ZAngus Ainslieangus.ainslie@puri.smSuspend and resume the devkitEnsure the devkit can suspend and resume
https://source.puri.sm/Librem5/use-cases/issues/75
Ensure the devkit can suspend and resume
https://source.puri.sm/Librem5/use-cases/issues/75
Past: Tulip (W20 - 22)Angus Ainslieangus.ainslie@puri.smAngus Ainslieangus.ainslie@puri.smhttps://source.puri.sm/Librem5/linux/-/issues/18Get DVFS working on linux-next2019-11-27T17:54:00ZAngus Ainslieangus.ainslie@puri.smGet DVFS working on linux-nextDynamically adjust voltage and frequency levels of internal busses and DRAM in order to save power consuption.
How will an implementation look like and who will write it?
https://source.puri.sm/Librem5/linux-next/issues/17 - devfreq an...Dynamically adjust voltage and frequency levels of internal busses and DRAM in order to save power consuption.
How will an implementation look like and who will write it?
https://source.puri.sm/Librem5/linux-next/issues/17 - devfreq and interconnect drivers - is a subset of this.
use-cases#75Angus Ainslieangus.ainslie@puri.smAngus Ainslieangus.ainslie@puri.smhttps://source.puri.sm/Librem5/linux/-/issues/22Enable cpuidle work around2021-12-13T15:47:24ZAngus Ainslieangus.ainslie@puri.smEnable cpuidle work aroundThe cpuidle work around needs to be added and tested on mainline.
use-cases#75The cpuidle work around needs to be added and tested on mainline.
use-cases#75Last: Romneya (W26-28)Angus Ainslieangus.ainslie@puri.smAngus Ainslieangus.ainslie@puri.smhttps://source.puri.sm/Librem5/linux/-/issues/23rsi_sdio modprobe hung task2023-10-03T16:17:39ZAngus Ainslieangus.ainslie@puri.smrsi_sdio modprobe hung taskWhen trying to modprobe the Redpine rs9116 driver it hangs in rsi_handle_interrupt
https://source.puri.sm/angus.ainslie/linux-next/tree/f/next-20190430/redpine
```
root@pureos:~# modprobe rsi_sdio ...When trying to modprobe the Redpine rs9116 driver it hangs in rsi_handle_interrupt
https://source.puri.sm/angus.ainslie/linux-next/tree/f/next-20190430/redpine
```
root@pureos:~# modprobe rsi_sdio
[60478.113409] cfg80211: Loading compiled-in X.509 certificates for regulatory database
[60478.143276] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7'
[60478.150195] platform regulatory.0: Direct firmware load for regulatory.db failed with error -2
[60478.159282] platform regulatory.0: Falling back to syfs fallback for: regulatory.db
[60478.168829] cfg80211: failed to load regulatory.db
[60478.327486] Bluetooth: Core ver 2.22
[60478.331319] NET: Registered protocol family 31
[60478.335964] Bluetooth: HCI device and connection manager initialized
[60478.342608] Bluetooth: HCI socket layer initialized
[60478.347704] Bluetooth: L2CAP socket layer initialized
[60478.352993] Bluetooth: SCO socket layer initialized
[60478.404831] rsi_91x: rsi_probe: ***** 9116 Module *****
[60478.410403] rsi_91x: rsi_hal_device_init: oper_mode = 13, coex_mode = 2
[60478.419607] rsi_91x: ***** Loading Firmware from Flash *****
[60478.427794] rsi_91x: ***** Loaded Firmware to RAM - Waiting for Card Ready *****
[60658.726011] INFO: task irq/32-mmc1:1657 blocked for more than 120 seconds.
[60658.733199] Not tainted 5.1.0-rc7-next-20190430-00015-gf0147bce959a-dirty #166
[60658.741285] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[60658.749454] irq/32-mmc1 D 0 1657 2 0x00000028
[60658.755180] Call trace:
[60658.757739] __switch_to+0xb4/0x1b8
[60658.761388] __schedule+0x1e4/0x498
[60658.765032] schedule+0x38/0xc8
[60658.768315] schedule_timeout+0x1f0/0x368
[60658.772503] wait_for_common+0xb4/0x170
[60658.776509] wait_for_completion+0x14/0x20
[60658.780788] mmc_wait_for_req_done+0x28/0x130
[60658.785337] mmc_wait_for_req+0x80/0xf0
[60658.789344] mmc_io_rw_extended+0x260/0x2c0
[60658.793712] sdio_io_rw_ext_helper+0xb4/0x200
[60658.798261] sdio_readsb+0x1c/0x28
[60658.801817] rsi_sdio_read_register_multiple+0x48/0x98 [rsi_sdio]
[60658.808178] rsi_sdio_host_intf_read_pkt+0x24/0x80 [rsi_sdio]
[60658.814177] rsi_interrupt_handler+0x14c/0x448 [rsi_sdio]
[60658.819814] rsi_handle_interrupt+0x30/0x40 [rsi_sdio]
[60658.825177] process_sdio_pending_irqs+0x48/0x180
[60658.830088] sdio_run_irqs+0x48/0x70
[60658.833813] sdhci_thread_irq+0x90/0xd8
[60658.837822] irq_thread_fn+0x28/0x78
[60658.841558] irq_thread+0x124/0x1c0
[60658.845204] kthread+0x124/0x128
[60658.848578] ret_from_fork+0x10/0x18
```
https://source.puri.sm/Librem5/linux/-/issues/24Reduce VINDPM to 3.9V2020-09-03T14:48:49ZEric KuzmenkoReduce VINDPM to 3.9VCurrently, the charge controller's (BQ25896's) VINDPM (0x0D) register is getting reduced to 3.9V in U-Boot but seems to be getting reset when the kernel boots. The value it should have is 0x8D.
Doing this can help prevent resets, it dro...Currently, the charge controller's (BQ25896's) VINDPM (0x0D) register is getting reduced to 3.9V in U-Boot but seems to be getting reset when the kernel boots. The value it should have is 0x8D.
Doing this can help prevent resets, it drops the minimum VBUS threshold to its lowest possible value.Angus Ainslieangus.ainslie@puri.smAngus Ainslieangus.ainslie@puri.smhttps://source.puri.sm/Librem5/linux/-/issues/25Needs to ship librem-evk.dtb as well2022-11-04T11:08:48ZGuido GuntherNeeds to ship librem-evk.dtb as wellSince the kernel sent upstream uses the same board name `Purism Librem 5 devkit` (and doesn't change to appending the board revision (as suggested)) but uses a different dtb name (`imx8mq-librem5-devkit.dtb`) we need to ship a dtb with t...Since the kernel sent upstream uses the same board name `Purism Librem 5 devkit` (and doesn't change to appending the board revision (as suggested)) but uses a different dtb name (`imx8mq-librem5-devkit.dtb`) we need to ship a dtb with the above name as well in order not break kernel installations.
I had a look at flash-kernel if there are ways around this but didn't spot anything. Other workarounds like dumping files in /etc/flash-kernel are even more cumbersome to maintain.https://source.puri.sm/Librem5/linux/-/issues/26Upstream the librem5 v12 devkit devicetree2023-12-14T08:00:30ZHeather EllsworthUpstream the librem5 v12 devkit devicetreeRelated feature: use-cases#56
Submit the librem5 devkit devicetree v12 changes to mainline.Related feature: use-cases#56
Submit the librem5 devkit devicetree v12 changes to mainline.Past: Tulip (W20 - 22)Angus Ainslieangus.ainslie@puri.smAngus Ainslieangus.ainslie@puri.smhttps://source.puri.sm/Librem5/linux/-/issues/27Release linux-next based image for testing2019-06-27T01:55:12ZHeather EllsworthRelease linux-next based image for testingFeature: https://source.puri.sm/Librem5/linux-next/issues/28
All of the various linux-next branches have been brought together (see https://source.puri.sm/Librem5/linux-next/issues/15). The next step is to release an image for testing.Feature: https://source.puri.sm/Librem5/linux-next/issues/28
All of the various linux-next branches have been brought together (see https://source.puri.sm/Librem5/linux-next/issues/15). The next step is to release an image for testing.https://source.puri.sm/Librem5/linux/-/issues/28Image should boot 5.X kernel2022-11-04T11:09:00ZHeather EllsworthImage should boot 5.X kernelEpic: https://source.puri.sm/Librem5/use-cases/issues/7
The phone will ultimately ship with a 5.X kernel, so we will need the image to be built and shipped with the latest linux-next kernel.
- [x] [Release linux-next kernel for testing]...Epic: https://source.puri.sm/Librem5/use-cases/issues/7
The phone will ultimately ship with a 5.X kernel, so we will need the image to be built and shipped with the latest linux-next kernel.
- [x] [Release linux-next kernel for testing](https://source.puri.sm/Librem5/linux-next/issues/27)
- [x] [Get all the branches together](https://source.puri.sm/Librem5/linux-next/issues/15)
- [x] [Trim defconfig](https://source.puri.sm/Librem5/linux-next/issues/29)
- [ ] [Phone Essentials List](https://source.puri.sm/Librem5/Apps_Issues/issues/64)
- [ ] [Screen won't turn on after 3hrs+ of blanked and idle charging while powered on](https://source.puri.sm/Librem5/linux-next/issues/148)Last: Poppy (W24-26)https://source.puri.sm/Librem5/linux/-/issues/29Trim defconfig2019-05-22T11:34:10ZGuido GuntherTrim defconfigThe [drm one](https://source.puri.sm/guido.gunther/linux-imx8/tree/f/next-20190514/devkit-drm-integration/v1-wip) is too tiny while the one at https://source.puri.sm/Librem5/linux-next/tree/imx8-linux-next-devkit is too big (takes too lo...The [drm one](https://source.puri.sm/guido.gunther/linux-imx8/tree/f/next-20190514/devkit-drm-integration/v1-wip) is too tiny while the one at https://source.puri.sm/Librem5/linux-next/tree/imx8-linux-next-devkit is too big (takes too long to build and produces a too big kernel, causes work on forward ports)
Needed for #28 Past: Tulip (W20 - 22)https://source.puri.sm/Librem5/linux/-/issues/30Bring back HDMI2020-09-15T15:55:36ZGuido GuntherBring back HDMIEpic: https://source.puri.sm/Librem5/use-cases/issues/108
Our current drm code does not carry the HDMI code from NXP.Epic: https://source.puri.sm/Librem5/use-cases/issues/108
Our current drm code does not carry the HDMI code from NXP.https://source.puri.sm/Librem5/linux/-/issues/31Implement short press of power button2019-05-23T08:16:31ZHeather EllsworthImplement short press of power buttonFeature: https://source.puri.sm/Librem5/use-cases/issues/47
The power button should have two modes: long press to turn the phone on/off and short press to turn the screen on/off. The long press functionality has already been implemented...Feature: https://source.puri.sm/Librem5/use-cases/issues/47
The power button should have two modes: long press to turn the phone on/off and short press to turn the screen on/off. The long press functionality has already been implemented for turning the devkit off (doesn't work for turning devkit on - see https://source.puri.sm/Librem5/linux-next/issues/32) but the short press functionality needs to be implemented.https://source.puri.sm/Librem5/linux/-/issues/32power button: long press doesn't turn on devkit2019-05-28T13:59:09ZHeather Ellsworthpower button: long press doesn't turn on devkitFeature: https://source.puri.sm/Librem5/use-cases/issues/87
I would expect that a long press of the power button on the devkit would turn off the devkit and then another long press would turn it back on. Currently, a long press will tur...Feature: https://source.puri.sm/Librem5/use-cases/issues/87
I would expect that a long press of the power button on the devkit would turn off the devkit and then another long press would turn it back on. Currently, a long press will turn off the devkit correctly, but another long press does nothing to turn on the devkit. @angus.ainslie suggested that this is likely due to the pmic being in the wrong state at power off.
Instead, to turn on the devkit, the usb cable needs to be unplugged and replugged into the workstation.https://source.puri.sm/Librem5/linux/-/issues/34Support devkit camera2022-01-17T11:33:39ZGuido GuntherSupport devkit cameraEpic: https://source.puri.sm/Librem5/use-cases/issues/104, https://source.puri.sm/Librem5/use-cases/issues/108
Will be done by forward porting our code from 4.18. I'll be working on this.
See similar [Support front phone camera](https:...Epic: https://source.puri.sm/Librem5/use-cases/issues/104, https://source.puri.sm/Librem5/use-cases/issues/108
Will be done by forward porting our code from 4.18. I'll be working on this.
See similar [Support front phone camera](https://source.puri.sm/Librem5/linux-next/issues/43) and [Support rear phone camera](https://source.puri.sm/Librem5/linux-next/issues/44)
# Dependencies
- [ ] [Use mainline ov5640 driver](https://source.puri.sm/Librem5/linux-next/issues/35)
https://source.puri.sm/Librem5/linux/-/issues/36ov5640: allow higher resolutions2021-09-07T16:48:44ZGuido Guntherov5640: allow higher resolutionsAt least the 4.18 variant would block on resoltions != 640x480. Let's recheck with a cleaned up driver.At least the 4.18 variant would block on resoltions != 640x480. Let's recheck with a cleaned up driver.https://source.puri.sm/Librem5/linux/-/issues/37Debug sound on linux-next2023-04-11T10:33:35ZAngus Ainslieangus.ainslie@puri.smDebug sound on linux-nextEpic: https://source.puri.sm/Librem5/use-cases/issues/1, https://source.puri.sm/Librem5/use-cases/issues/95, https://source.puri.sm/Librem5/use-cases/issues/108
To test sound you can use alsabat.
```
alsabat -D plughw:CARD=sgtl5000,DEV...Epic: https://source.puri.sm/Librem5/use-cases/issues/1, https://source.puri.sm/Librem5/use-cases/issues/95, https://source.puri.sm/Librem5/use-cases/issues/108
To test sound you can use alsabat.
```
alsabat -D plughw:CARD=sgtl5000,DEV=0 -c2 --saveplay default_dual.wav --standalone
```
The sgtl5000 some times doesn't come up or does come up but can't read/write.
```
root@pureos:~# aplay -D plughw:CARD=sgtl5000,DEV=0 default_dual.wav
Playing WAVE 'default_dual.wav' : Signed 16 bit Little Endian, Rate 48000 Hz, Stereo
aplay: pcm_write:2053: write error: Input/output error
```
In this state we see a high number of sai and HP_DET interrupts.
```
root@pureos:~# cat /proc/interrupts | grep sai
19: 0 0 0 0 GPCv2 90 Edge sai
29: 1175024 0 0 0 GPCv2 96 Edge sai
root@pureos:~# cat /proc/interrupts | grep HP
128: 35536 0 0 0 gpio-mxc 20 Edge HP_DET
```Past: Edelweiss (W22-24)Angus Ainslieangus.ainslie@puri.smAngus Ainslieangus.ainslie@puri.smhttps://source.puri.sm/Librem5/linux/-/issues/39gpio_keys and battery_cpufreq test failures2021-01-18T10:14:08ZHeather Ellsworthgpio_keys and battery_cpufreq test failures### devkit setup
Image: https://arm01.puri.sm/job/manual/job/devkit-latest_linux-next_image_build/62/
kernel: 5.2.0-rc2-next-20190528-g0e8e80ff1
librem5-devkit-check: 0.0.3~141.gbp76bb8e
### librem5-devkit-check failures
```
purism@...### devkit setup
Image: https://arm01.puri.sm/job/manual/job/devkit-latest_linux-next_image_build/62/
kernel: 5.2.0-rc2-next-20190528-g0e8e80ff1
librem5-devkit-check: 0.0.3~141.gbp76bb8e
### librem5-devkit-check failures
```
purism@pureos:~$ librem5-devkit-check
=============================================================================================== test session starts ===============================================================================================
platform linux -- Python 3.7.3rc1, pytest-3.10.1, py-1.7.0, pluggy-0.8.0
rootdir: /usr/share/librem5-devkit/check, inifile:
collected 6 items
test_battery_charger.py . [ 16%]
test_cpufreq.py F [ 33%]
test_gpio_keys.py F [ 50%]
test_magn.py . [ 66%]
test_panel_brightness.py . [ 83%]
test_usb_hub.py . [100%]
==================================================================================================== FAILURES =====================================================================================================
______________________________________________________________________________________________ test_battery_cpufreq _______________________________________________________________________________________________
def test_battery_cpufreq():
> assert("1000000" in open("/sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_min_freq").read())
E FileNotFoundError: [Errno 2] No such file or directory: '/sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_min_freq'
test_cpufreq.py:2: FileNotFoundError
_________________________________________________________________________________________________ test_gpio_keys __________________________________________________________________________________________________
def test_gpio_keys():
"Test if we have a evdev named 'gpio-keys'"
devices = [evdev.InputDevice(path).name for path in evdev.list_devices()]
> assert("gpio-keys" in devices)
E AssertionError: assert 'gpio-keys' in []
test_gpio_keys.py:7: AssertionError
================================================================================================ warnings summary =================================================================================================
/usr/lib/python3/dist-packages/_pytest/cacheprovider.py:58
/usr/lib/python3/dist-packages/_pytest/cacheprovider.py:58: PytestWarning: could not create cache path /usr/share/librem5-devkit/check/.pytest_cache/v/cache/stepwise
PytestWarning(fmt.format(**args) if args else fmt), self._config
/usr/lib/python3/dist-packages/_pytest/cacheprovider.py:58: PytestWarning: could not create cache path /usr/share/librem5-devkit/check/.pytest_cache/v/cache/nodeids
PytestWarning(fmt.format(**args) if args else fmt), self._config
/usr/lib/python3/dist-packages/_pytest/cacheprovider.py:58: PytestWarning: could not create cache path /usr/share/librem5-devkit/check/.pytest_cache/v/cache/lastfailed
PytestWarning(fmt.format(**args) if args else fmt), self._config
-- Docs: https://docs.pytest.org/en/latest/warnings.html
================================================================================= 2 failed, 4 passed, 3 warnings in 0.66 seconds ==================================================================================
```https://source.puri.sm/Librem5/linux/-/issues/40Touch Controller Sometimes Not Responsive2019-07-23T14:29:36ZEric KuzmenkoTouch Controller Sometimes Not ResponsiveEvery so often my capacitive touch panel doesn't respond to input. I believe what is happening is that the CAPTOUCH_INT# pin is sometimes not being properly brought LOW during boot, causing its 7-bit I2C slave address to be **0x14** inst...Every so often my capacitive touch panel doesn't respond to input. I believe what is happening is that the CAPTOUCH_INT# pin is sometimes not being properly brought LOW during boot, causing its 7-bit I2C slave address to be **0x14** instead of **0x5D**.
I have been trying to verify this is the case for the past hour or so by resetting my board over and over waiting for the touch screen to stop responding but have not gotten it into this failed state yet. Once I get it to do this I will run i2cdetect to find out if this is in fact what is happening.https://source.puri.sm/Librem5/linux/-/issues/41Upstream the librem5 v15 devkit devicetree2019-06-22T15:53:23ZHeather EllsworthUpstream the librem5 v15 devkit devicetreeRelated feature: use-cases#56
Submited the librem5 devkit devicetree v15 changes to mainline and waiting on feedback to see if more changes are needed or it is accepted.Related feature: use-cases#56
Submited the librem5 devkit devicetree v15 changes to mainline and waiting on feedback to see if more changes are needed or it is accepted.Last: Poppy (W24-26)Angus Ainslieangus.ainslie@puri.smAngus Ainslieangus.ainslie@puri.smhttps://source.puri.sm/Librem5/linux/-/issues/43Support front (selfie) phone camera2023-03-28T07:51:20ZHeather EllsworthSupport front (selfie) phone cameraEpic: https://source.puri.sm/Librem5/use-cases/issues/104, https://source.puri.sm/Librem5/use-cases/issues/108
The kernel should have support for the front (screen side) phone camera shipping on the phone.
See similar [Support devkit c...Epic: https://source.puri.sm/Librem5/use-cases/issues/104, https://source.puri.sm/Librem5/use-cases/issues/108
The kernel should have support for the front (screen side) phone camera shipping on the phone.
See similar [Support devkit camera](https://source.puri.sm/Librem5/linux-next/issues/34) and [Support rear phone camera](https://source.puri.sm/Librem5/linux-next/issues/44)
# Dependencies
- [ ] [Phone Essentials List](https://source.puri.sm/Librem5/Apps_Issues/issues/64)Evg++Martin KepplingerMartin Kepplingerhttps://source.puri.sm/Librem5/linux/-/issues/44Support rear (big) phone camera2022-11-26T16:02:13ZHeather EllsworthSupport rear (big) phone cameraEpic: https://source.puri.sm/Librem5/use-cases/issues/104, https://source.puri.sm/Librem5/use-cases/issues/108
The kernel should have support for the rear phone camera shipping on the phone.
See similar [Support devkit camera](https://...Epic: https://source.puri.sm/Librem5/use-cases/issues/104, https://source.puri.sm/Librem5/use-cases/issues/108
The kernel should have support for the rear phone camera shipping on the phone.
See similar [Support devkit camera](https://source.puri.sm/Librem5/linux-next/issues/34) and [Support front phone camera](https://source.puri.sm/Librem5/linux-next/issues/43)
# Dependencies
- [ ] [Phone Essentials List](https://source.puri.sm/Librem5/Apps_Issues/issues/64)
- [ ] [Screen won't turn on after 3hrs+ of blanked and idle charging while powered on](https://source.puri.sm/Librem5/linux-next/issues/148)EvgDorota CzaplejewiczDorota Czaplejewiczhttps://source.puri.sm/Librem5/linux/-/issues/45Support phone LCD panel2023-12-07T17:48:30ZHeather EllsworthSupport phone LCD panelEpic: https://source.puri.sm/Librem5/use-cases/issues/108, https://source.puri.sm/Librem5/use-cases/issues/67
The kernel should have support for the LCD panel shipping on the phone.
- [ ] [Phone Essentials List](https://source.puri.sm/L...Epic: https://source.puri.sm/Librem5/use-cases/issues/108, https://source.puri.sm/Librem5/use-cases/issues/67
The kernel should have support for the LCD panel shipping on the phone.
- [ ] [Phone Essentials List](https://source.puri.sm/Librem5/Apps_Issues/issues/64)
- [ ] [Screen won't turn on after 3hrs+ of blanked and idle charging while powered on](https://source.puri.sm/Librem5/linux-next/issues/148)https://source.puri.sm/Librem5/linux/-/issues/46Support touch controller2020-01-28T01:44:55ZHeather EllsworthSupport touch controllerEpic: https://source.puri.sm/Librem5/use-cases/issues/108, https://source.puri.sm/Librem5/use-cases/issues/67
The kernel should have support for the touch controller shipping on the phone.
- [ ] [Phone Essentials List](https://source.pu...Epic: https://source.puri.sm/Librem5/use-cases/issues/108, https://source.puri.sm/Librem5/use-cases/issues/67
The kernel should have support for the touch controller shipping on the phone.
- [ ] [Phone Essentials List](https://source.puri.sm/Librem5/Apps_Issues/issues/64)
- [ ] [Screen won't turn on after 3hrs+ of blanked and idle charging while powered on](https://source.puri.sm/Librem5/linux-next/issues/148)https://source.puri.sm/Librem5/linux/-/issues/47Support an external screen2020-10-30T14:35:05ZHeather EllsworthSupport an external screenEpic: https://source.puri.sm/Librem5/use-cases/issues/108, https://source.puri.sm/Librem5/use-cases/issues/67
Users will want to connect their phone to an external screen. It is also worth noting that some backers signed up for the opti...Epic: https://source.puri.sm/Librem5/use-cases/issues/108, https://source.puri.sm/Librem5/use-cases/issues/67
Users will want to connect their phone to an external screen. It is also worth noting that some backers signed up for the option that includes a phone and an external monitor, so we absolutely must support this.
The phone will output display port data and we want to use this with an HDMI monitor. The work required is:
* convert display port to HDMI to get HDMI out
* get display port changes into mainline (more complex than HDMI)
* look at USB-C parts
* runtime switches
We also need to decide if we want to support the use of the touch LCD panel *at the same time* as the external screen or not.
- [ ] [Phone Essentials List](https://source.puri.sm/Librem5/Apps_Issues/issues/64)
- [x] [Screen won't turn on after 3hrs+ of blanked and idle charging while powered on](https://source.puri.sm/Librem5/linux-next/issues/148)EvgGuido GuntherGuido Guntherhttps://source.puri.sm/Librem5/linux/-/issues/48Redpine driver only returns 1 access point2019-12-13T19:44:47ZAngus Ainslieangus.ainslie@puri.smRedpine driver only returns 1 access pointFeature: https://source.puri.sm/Librem5/use-cases/issues/109
Before connecting to an access point over 50 APs are available. Once a connection has been made a scan only shows the connected ap.
root@pureos:~# nmcli device wifi list
IN-...Feature: https://source.puri.sm/Librem5/use-cases/issues/109
Before connecting to an access point over 50 APs are available. Once a connection has been made a scan only shows the connected ap.
root@pureos:~# nmcli device wifi list
IN-USE SSID MODE CHAN RATE SIGNAL BARS SECURITY
* HomeWireless Infra 9 195 Mbit/s 78 ▂▄▆_ WPA1 WPA2https://source.puri.sm/Librem5/linux/-/issues/49Redpine driver has inconsistent throughput2020-06-22T08:36:39ZAngus Ainslieangus.ainslie@puri.smRedpine driver has inconsistent throughputFeature: https://source.puri.sm/Librem5/use-cases/issues/109
iperf3 tests show very inconsistent rates for exactly the same HW and SW setup. The lower rates are unacceptable for real world use. This throughput degradation is seen at 2.4...Feature: https://source.puri.sm/Librem5/use-cases/issues/109
iperf3 tests show very inconsistent rates for exactly the same HW and SW setup. The lower rates are unacceptable for real world use. This throughput degradation is seen at 2.4GHz and 5GHz.
```
-----------------------------------------------------------
Server listening on 5201
-----------------------------------------------------------
Accepted connection from 172.16.16.180, port 57484
[ 5] local 172.16.16.6 port 5201 connected to 172.16.16.180 port 57486
[ ID] Interval Transfer Bandwidth
[ 5] 0.00-1.00 sec 0.00 Bytes 0.00 bits/sec
[ 5] 1.00-2.00 sec 0.00 Bytes 0.00 bits/sec
[ 5] 2.00-3.00 sec 2.83 KBytes 23.2 Kbits/sec
[ 5] 3.00-4.00 sec 28.3 KBytes 232 Kbits/sec
[ 5] 4.00-5.00 sec 8.48 KBytes 69.5 Kbits/sec
[ 5] 5.00-6.00 sec 0.00 Bytes 0.00 bits/sec
[ 5] 6.00-7.00 sec 24.0 KBytes 197 Kbits/sec
[ 5] 7.00-8.00 sec 0.00 Bytes 0.00 bits/sec
[ 5] 8.00-9.00 sec 0.00 Bytes 0.00 bits/sec
[ 5] 9.00-10.00 sec 0.00 Bytes 0.00 bits/sec
[ 5] 10.00-10.39 sec 2.83 KBytes 59.2 Kbits/sec
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval Transfer Bandwidth
[ 5] 0.00-10.39 sec 0.00 Bytes 0.00 bits/sec sender
[ 5] 0.00-10.39 sec 66.5 KBytes 52.4 Kbits/sec receiver
-----------------------------------------------------------
Server listening on 5201
-----------------------------------------------------------
Accepted connection from 172.16.16.180, port 43352
[ 5] local 172.16.16.6 port 5201 connected to 172.16.16.180 port 43354
[ ID] Interval Transfer Bandwidth
[ 5] 0.00-1.00 sec 1.75 MBytes 14.7 Mbits/sec
[ 5] 1.00-2.00 sec 714 KBytes 5.85 Mbits/sec
[ 5] 2.00-3.00 sec 424 KBytes 3.48 Mbits/sec
[ 5] 3.00-4.00 sec 1.03 MBytes 8.67 Mbits/sec
[ 5] 4.00-5.00 sec 1.28 MBytes 10.7 Mbits/sec
[ 5] 5.00-6.00 sec 749 KBytes 6.14 Mbits/sec
[ 5] 6.00-7.00 sec 1005 KBytes 8.24 Mbits/sec
[ 5] 7.00-8.00 sec 1.16 MBytes 9.74 Mbits/sec
[ 5] 8.00-9.00 sec 1.37 MBytes 11.5 Mbits/sec
[ 5] 9.00-10.00 sec 1.40 MBytes 11.8 Mbits/sec
[ 5] 10.00-10.00 sec 17.0 KBytes 37.0 Mbits/sec
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval Transfer Bandwidth
[ 5] 0.00-10.00 sec 0.00 Bytes 0.00 bits/sec sender
[ 5] 0.00-10.00 sec 10.8 MBytes 9.10 Mbits/sec receiver
```https://source.puri.sm/Librem5/linux/-/issues/50Redpine module does not unload cleanly2020-01-21T08:44:53ZAngus Ainslieangus.ainslie@puri.smRedpine module does not unload cleanlyFeature: https://source.puri.sm/Librem5/use-cases/issues/109
During system shutdown the redpine driver does not unload cleanly
```
[71220.768155] rsi_91x: SDIO Bus shutdown =====> ...Feature: https://source.puri.sm/Librem5/use-cases/issues/109
During system shutdown the redpine driver does not unload cleanly
```
[71220.768155] rsi_91x: SDIO Bus shutdown =====> [35/1915]
[71220.772603] WARNING: CPU: 3 PID: 1 at drivers/net/wireless/rsi/rsi_91x_mac80211.c:2650 rsi_config_wowlan+0x150/0x178
[rsi_91x]
[71220.783991] Modules linked in: rsi_sdio rsi_91x aes_ce_ccm bnep bluetooth mac80211 cfg80211 option qmi_wwan usb_wwan
cdc_wdm usbnet usbserial mii mousedev xhci_plat_hcd xhci_hcd usbcore aes_ce_blk crypto_simd st_magn_spi st_sensors_spi t
cpci tcpm roles typec bq25890_charger crct10dif_ce st_magn_i2c st_magn st_sensors_i2c st_sensors industrialio_triggered_
buffer kfifo_buf goodix ghash_ce sha2_ce snd_soc_sgtl5000 sha1_ce snd_soc_simple_card snd_soc_fsl_sai snd_soc_simple_car
d_utils imx_pcm_dma_v2 snd_soc_gtm601 imx2_wdt watchdog gpio_vibra snd_soc_core snvs_pwrkey snd_pcm_dmaengine usb_f_acm
u_serial snd_pcm snd_timer usb_f_rndis snd qoriq_thermal imx_sdma soundcore virt_dma dwc3 ulpi phy_fsl_imx8mq_usb g_mult
i usb_f_mass_storage u_ether libcomposite udc_core usb_common ip_tables x_tables ipv6 nf_defrag_ipv6 [last unloaded: rsi
_91x]
[71220.857626] CPU: 3 PID: 1 Comm: systemd-shutdow Tainted: G W 5.2.0-rc3-next-20190607-gaecb15545 #1
[71220.867883] Hardware name: Purism Librem 5 devkit (DT)
[71220.873019] pstate: 40000005 (nZcv daif -PAN -UAO)
[71220.877816] pc : rsi_config_wowlan+0x150/0x178 [rsi_91x]
[71220.883133] lr : rsi_config_wowlan+0x30/0x178 [rsi_91x]
[71220.888354] sp : ffff8000a7c93c40
[71220.891665] x29: ffff8000a7c93c40 x28: ffff8000a7c88000
[71220.896975] x27: 0000000000000000 x26: 0000000000000000
[71220.902285] x25: ffff0000109eac38 x24: ffff000010bba040
[71220.907594] x23: ffff8000a733c088 x22: ffff80008345d0b8
[71220.912904] x21: ffff800080898000 x20: 0000000000000000
[71220.918214] x19: ffff8000771c7000 x18: ffffffffffffffff
[71220.923524] x17: 0000000000000000 x16: 0000000000000000
[71220.928834] x15: ffff000010b385c8 x14: ffff800127c93937
[71220.934144] x13: ffff8000a7c93945 x12: ffff000010bee0a2
[71220.939453] x11: 0000000000000000 x10: 0000000005f5e0ff
[71220.944762] x9 : 0000000000000000 x8 : 0000000000000001
[71220.950072] x7 : ffff0000104d57d8 x6 : ffff000010bcbc78
[71220.955382] x5 : 0000000000000000 x4 : 0000000000000000
[71220.960691] x3 : ffff8000a7c93c40 x2 : ffff8000a7c93c10
[71220.966001] x1 : ac514d4daaa86300 x0 : 0000000000000000
[71220.971311] Call trace:
[71220.973763] rsi_config_wowlan+0x150/0x178 [rsi_91x]
[71220.978730] rsi_shutdown+0x4c/0xd8 [rsi_sdio]
[71220.983177] device_shutdown+0x104/0x1e0
[71220.987100] kernel_restart_prepare+0x34/0x40
[71220.991454] kernel_restart+0x14/0x78
[71220.995114] __se_sys_reboot+0x108/0x218
[71220.999035] __arm64_sys_reboot+0x18/0x20
[71221.003045] el0_svc_common.constprop.0+0xb0/0x168
[71221.007834] el0_svc_handler+0x18/0x20
[71221.011581] el0_svc+0x8/0xc
[71221.014459] ---[ end trace 786c11767fdff785 ]---
[71221.019092] rsi_91x: WoW triggers not enabled
[71221.023480] rsi_91x: Failed to configure WoWLAN
[71221.028386] rsi_91x: Waiting for interrupts to be cleared..
[71221.028408] rsi_91x: .
[71221.033996] rsi_91x:
[71221.033996] Interrupts cleared
```https://source.puri.sm/Librem5/linux/-/issues/51Redpine modules takes upto 180 seconds to connect2019-11-05T15:11:57ZAngus Ainslieangus.ainslie@puri.smRedpine modules takes upto 180 seconds to connectFeature: https://source.puri.sm/Librem5/use-cases/issues/109
Below the driver module is loaded 166 seconds after boot
```
[ 166.494274] rsi_91x: rsi_probe: ***** 9116 Module *****
[ 166.499604] rsi_91x: rsi_hal_device_init: oper_mod...Feature: https://source.puri.sm/Librem5/use-cases/issues/109
Below the driver module is loaded 166 seconds after boot
```
[ 166.494274] rsi_91x: rsi_probe: ***** 9116 Module *****
[ 166.499604] rsi_91x: rsi_hal_device_init: oper_mode = 13, coex_mode = 2
[ 166.508516] rsi_91x: ***** Loading Firmware from Flash *****
[ 166.516378] rsi_91x: ***** Loaded Firmware to RAM - Waiting for Card Ready *****
[ 169.615002] rsi_91x: rsi_send_bt_reg_params: Sending BT reg frame
[ 169.633700] rsi_91x: HCI module init done...
[ 169.633818] rsi_91x: RSI HCI DEVICE "hci0" open
[ 169.646882] rsi_91x: Max Stations Allowed = 1
[ 169.717591] rsi_91x: ===> Interface UP <===
[ 169.730585] rsi_91x: ===> Interface DOWN <===
[ 169.741467] rsi_91x: ===> Interface UP <===
[ 180.270818] rsi_91x: ===> Interface DOWN <===
[ 180.280564] rsi_91x: ===> Interface UP <===
```
Almost 100 seconds later a connection is established
```
[ 262.954641] wlan0: authenticate with b0:4e:26:7b:9d:3d
[ 262.960028] wlan0: send auth to b0:4e:26:7b:9d:3d (try 1/3)
[ 262.969086] wlan0: authenticated
[ 262.987728] wlan0: associate with b0:4e:26:7b:9d:3d (try 1/3)
[ 262.998668] wlan0: RX AssocResp from b0:4e:26:7b:9d:3d (capab=0x431 status=0 aid=3)
[ 263.020816] wlan0: associated
[ 263.041221] rsi_91x: rsi_hal_key_config: Cipher 0xfac04 key_type: 1 key_len: 16
[ 263.042227] rsi_91x: EAPOL 4 confirm
[ 263.048572] rsi_91x: rsi_mac80211_set_key: RSI set_key
[ 263.057995] rsi_91x: rsi_hal_key_config: Cipher 0xfac02 key_type: 2 key_len: 32
[ 263.065389] rsi_91x: rsi_mac80211_set_key: RSI set_key
[ 263.071584] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
```https://source.puri.sm/Librem5/linux/-/issues/53Redpine module fails after toggling #disable line.2019-09-23T13:41:09ZAngus Ainslieangus.ainslie@puri.smRedpine module fails after toggling #disable line.Feature: https://source.puri.sm/Librem5/use-cases/issues/109
The redpine driver module can't reload after the #disable line has been toggled.
```
root@pureos:~# modprobe rsi_sdio
[ 1767.179736] RSI-SDIO WLAN: probe of mmc1:fffd:1 faile...Feature: https://source.puri.sm/Librem5/use-cases/issues/109
The redpine driver module can't reload after the #disable line has been toggled.
```
root@pureos:~# modprobe rsi_sdio
[ 1767.179736] RSI-SDIO WLAN: probe of mmc1:fffd:1 failed with error -110
```https://source.puri.sm/Librem5/linux/-/issues/54CPU Thermal throttling2019-10-24T11:46:48ZHeather EllsworthCPU Thermal throttlingFeature: https://source.puri.sm/Librem5/use-cases/issues/75
We don't want the phone to be unusably hot (and breaking the [first law of thermodynamics](https://en.wikipedia.org/wiki/First_law_of_thermodynamics) is not allowed) so this is...Feature: https://source.puri.sm/Librem5/use-cases/issues/75
We don't want the phone to be unusably hot (and breaking the [first law of thermodynamics](https://en.wikipedia.org/wiki/First_law_of_thermodynamics) is not allowed) so this issue is to track the efforts to try and control the heat produced by the phone.
Last: Fuschia (W30-32)https://source.puri.sm/Librem5/linux/-/issues/55Resets on GSM network scans2019-10-31T10:17:34ZGuido GuntherResets on GSM network scansEven with a fan (linux-emcraft#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 reboo...Even with a fan (linux-emcraft#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.https://source.puri.sm/Librem5/linux/-/issues/56cpufreq on-demand doesn't reach 1.0 GHz on zero CPU load2019-09-09T11:18:12ZMartin Kepplingercpufreq on-demand doesn't reach 1.0 GHz on zero CPU loadThe CPUs switch between 1.3 and 1.5 Ghz but, even when load drops to 0 for a long time, they won't slow down to 1.0 Ghz. Using the "powersave" governor, we can manually force 1.0 Ghz: `echo powersave > /sys/devices/system/cpu/cpufreq/pol...The CPUs switch between 1.3 and 1.5 Ghz but, even when load drops to 0 for a long time, they won't slow down to 1.0 Ghz. Using the "powersave" governor, we can manually force 1.0 Ghz: `echo powersave > /sys/devices/system/cpu/cpufreq/policy0/scaling_governor`.
use-cases#75Last: Romneya (W26-28)https://source.puri.sm/Librem5/linux/-/issues/57Redpine can't maintain connection to paired BT device2019-12-11T23:41:31ZAngus Ainslieangus.ainslie@puri.smRedpine can't maintain connection to paired BT deviceFeature: https://source.puri.sm/Librem5/use-cases/issues/109
redpine module can pair but won't maintain a connection to devices
```
[bluetooth]# connect 00:23:01:42:48:13 ...Feature: https://source.puri.sm/Librem5/use-cases/issues/109
redpine module can pair but won't maintain a connection to devices
```
[bluetooth]# connect 00:23:01:42:48:13
Attempting to connect to 00:23:01:42:48:13
Failed to connect: org.bluez.Error.Failed
[CHG] Device 00:23:01:42:48:13 Connected: yes
[CHG] Device 00:23:01:42:48:13 Connected: no
[CHG] Device 00:23:01:42:48:13 Connected: yes
[CHG] Device 00:23:01:42:48:13 Connected: no
[bluetooth]# info 00:23:01:42:48:13
Device 00:23:01:42:48:13 (public)
Name: iSport Wireless
Alias: iSport Wireless
Class: 0x00240404
Icon: audio-card
Paired: yes
Trusted: yes
Blocked: no
Connected: no
LegacyPairing: no
UUID: Headset (00001108-0000-1000-8000-00805f9b34fb)
UUID: Audio Sink (0000110b-0000-1000-8000-00805f9b34fb)
UUID: A/V Remote Control Target (0000110c-0000-1000-8000-00805f9b34fb)
UUID: A/V Remote Control (0000110e-0000-1000-8000-00805f9b34fb)
UUID: Handsfree (0000111e-0000-1000-8000-00805f9b34fb)
```https://source.puri.sm/Librem5/linux/-/issues/58Redpine module fails to find pairable devices2019-11-20T19:35:51ZAngus Ainslieangus.ainslie@puri.smRedpine module fails to find pairable devicesFeature: https://source.puri.sm/Librem5/use-cases/issues/109
Bluetooth keyboard at 1M distance isn't found during scan for pairable devices.Feature: https://source.puri.sm/Librem5/use-cases/issues/109
Bluetooth keyboard at 1M distance isn't found during scan for pairable devices.https://source.puri.sm/Librem5/linux/-/issues/59Ethernet issues2021-03-22T15:24:08ZBob HamEthernet issuesSince the switch to recent images with 5.x, I keep getting networking issues. The first kernel I used had great trouble with the network and was completely unusable. The current kernel I'm using, 5.2.0-rc5-gfd2301817, has problems afte...Since the switch to recent images with 5.x, I keep getting networking issues. The first kernel I used had great trouble with the network and was completely unusable. The current kernel I'm using, 5.2.0-rc5-gfd2301817, has problems after a while:
```
[21509.093254] INFO: task kworker/2:0:3974 blocked for more than 120 seconds.
[21509.100204] Not tainted 5.2.0-rc5-gfd2301817 #1
[21509.105296] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[21509.113192] kworker/2:0 D 0 3974 2 0x00000028
[21509.128979] Workqueue: ipv6_addrconf addrconf_verify_work [ipv6]
[21509.145101] Call trace:
[21509.157728] __switch_to+0xac/0x1b0
[21509.171446] __schedule+0x1e0/0x488
[21509.185132] schedule+0x38/0xc8
[21509.198467] schedule_preempt_disabled+0x20/0x38
[21509.213240] __mutex_lock.isra.1+0x1a0/0x4c0
[21509.227734] __mutex_lock_slowpath+0x10/0x18
[21509.242200] mutex_lock+0x38/0x40
[21509.255714] rtnl_lock+0x14/0x20
[21509.259013] addrconf_verify_work+0xc/0x20 [ipv6]
[21509.263739] process_one_work+0x1dc/0x338
[21509.267831] worker_thread+0x48/0x430
[21509.271528] kthread+0xf4/0x120
[21509.274687] ret_from_fork+0x10/0x18
...
[21629.928046] INFO: task systemd-network:339 blocked for more than 120 seconds.
[21629.935277] Not tainted 5.2.0-rc5-gfd2301817 #1
[21629.940365] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[21629.948207] systemd-network D 0 339 1 0x00000801
[21629.948216] Call trace:
[21629.948233] __switch_to+0xac/0x1b0
[21629.948241] __schedule+0x1e0/0x488
[21629.948247] schedule+0x38/0xc8
[21629.948253] schedule_preempt_disabled+0x20/0x38
[21629.948260] __mutex_lock.isra.1+0x1a0/0x4c0
[21629.948265] __mutex_lock_slowpath+0x10/0x18
[21629.948271] mutex_lock+0x38/0x40
[21629.948282] rtnetlink_rcv_msg+0xe4/0x390
[21629.964028] netlink_rcv_skb+0xe8/0x130
[21629.969938] rtnetlink_rcv+0x14/0x20
[21629.976582] netlink_unicast+0x188/0x208
[21629.985514] netlink_sendmsg+0x26c/0x338
[21629.993086] sock_sendmsg+0x18/0x30
[21630.007312] __sys_sendto+0xb8/0x138
[21630.021343] __arm64_sys_sendto+0x20/0x30
[21630.021351] el0_svc_common.constprop.0+0xb0/0x168
[21630.021355] el0_svc_handler+0x18/0x20
[21630.021359] el0_svc+0x8/0xc
[21630.021393] INFO: task NetworkManager:541 blocked for more than 120 seconds.
[21630.035183] Not tainted 5.2.0-rc5-gfd2301817 #1
[21630.049268] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[21630.049272] NetworkManager D 0 541 1 0x00000000
[21630.049278] Call trace:
[21630.049288] __switch_to+0xac/0x1b0
[21630.049296] __schedule+0x1e0/0x488
[21630.161458] schedule+0x38/0xc8
[21630.164620] schedule_preempt_disabled+0x20/0x38
[21630.169249] __mutex_lock.isra.1+0x1a0/0x4c0
[21630.173575] __mutex_lock_slowpath+0x10/0x18
[21630.177867] mutex_lock+0x38/0x40
[21630.181195] rtnetlink_rcv_msg+0xe4/0x390
[21630.185216] netlink_rcv_skb+0xe8/0x130
[21630.189070] rtnetlink_rcv+0x14/0x20
[21630.192667] netlink_unicast+0x188/0x208
[21630.196626] netlink_sendmsg+0x26c/0x338
[21630.200562] sock_sendmsg+0x18/0x30
[21630.204059] ___sys_sendmsg+0x27c/0x2a8
[21630.207897] __sys_sendmsg+0x60/0xb8
[21630.211492] __arm64_sys_sendmsg+0x1c/0x28
[21630.215605] el0_svc_common.constprop.0+0xb0/0x168
[21630.220406] el0_svc_handler+0x18/0x20
[21630.224180] el0_svc+0x8/0xc
[21630.227129] INFO: task kworker/2:0:3974 blocked for more than 241 seconds.
[21630.234019] Not tainted 5.2.0-rc5-gfd2301817 #1
[21630.239080] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[21630.246929] kworker/2:0 D 0 3974 2 0x00000028
[21630.252511] Workqueue: ipv6_addrconf addrconf_verify_work [ipv6]
[21630.258548] Call trace:
[21630.261026] __switch_to+0xac/0x1b0
[21630.264530] __schedule+0x1e0/0x488
[21630.268028] schedule+0x38/0xc8
[21630.271169] schedule_preempt_disabled+0x20/0x38
[21630.275807] __mutex_lock.isra.1+0x1a0/0x4c0
[21630.280101] __mutex_lock_slowpath+0x10/0x18
[21630.284412] mutex_lock+0x38/0x40
[21630.287729] rtnl_lock+0x14/0x20
[21630.291029] addrconf_verify_work+0xc/0x20 [ipv6]
[21630.295788] process_one_work+0x1dc/0x338
[21630.299813] worker_thread+0x48/0x430
[21630.303487] kthread+0xf4/0x120
[21630.306663] ret_from_fork+0x10/0x18
...
[21750.769567] INFO: task systemd-network:339 blocked for more than 241 seconds.
[21750.776731] Not tainted 5.2.0-rc5-gfd2301817 #1
[21750.781820] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[21750.789667] systemd-network D 0 339 1 0x00000801
[21750.789675] Call trace:
[21750.789689] __switch_to+0xac/0x1b0
[21750.789698] __schedule+0x1e0/0x488
[21750.805374] schedule+0x38/0xc8
[21750.805381] schedule_preempt_disabled+0x20/0x38
[21750.811353] __mutex_lock.isra.1+0x1a0/0x4c0
[21750.825012] __mutex_lock_slowpath+0x10/0x18
[21750.825016] mutex_lock+0x38/0x40
[21750.825027] rtnetlink_rcv_msg+0xe4/0x390
[21750.832793] netlink_rcv_skb+0xe8/0x130
[21750.832801] rtnetlink_rcv+0x14/0x20
[21750.847255] netlink_unicast+0x188/0x208
[21750.847261] netlink_sendmsg+0x26c/0x338
[21750.861718] sock_sendmsg+0x18/0x30
[21750.861724] __sys_sendto+0xb8/0x138
[21750.869065] __arm64_sys_sendto+0x20/0x30
[21750.869078] el0_svc_common.constprop.0+0xb0/0x168
[21750.883089] el0_svc_handler+0x18/0x20
[21750.883095] el0_svc+0x8/0xc
[21750.896888] INFO: task NetworkManager:541 blocked for more than 241 seconds.
[21750.975029] Not tainted 5.2.0-rc5-gfd2301817 #1
[21750.980108] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[21750.987966] NetworkManager D 0 541 1 0x00000000
[21750.993526] Call trace:
[21750.996007] __switch_to+0xac/0x1b0
[21750.999529] __schedule+0x1e0/0x488
[21751.003030] schedule+0x38/0xc8
[21751.006204] schedule_preempt_disabled+0x20/0x38
[21751.010861] __mutex_lock.isra.1+0x1a0/0x4c0
[21751.015148] __mutex_lock_slowpath+0x10/0x18
[21751.019429] mutex_lock+0x38/0x40
[21751.022756] rtnetlink_rcv_msg+0xe4/0x390
[21751.026835] netlink_rcv_skb+0xe8/0x130
[21751.030699] rtnetlink_rcv+0x14/0x20
[21751.034286] netlink_unicast+0x188/0x208
[21751.038218] netlink_sendmsg+0x26c/0x338
[21751.042193] sock_sendmsg+0x18/0x30
[21751.045717] ___sys_sendmsg+0x27c/0x2a8
[21751.049566] __sys_sendmsg+0x60/0xb8
[21751.053141] __arm64_sys_sendmsg+0x1c/0x28
[21751.057269] el0_svc_common.constprop.0+0xb0/0x168
[21751.062130] el0_svc_handler+0x18/0x20
[21751.065909] el0_svc+0x8/0xc
[21751.068877] INFO: task kworker/2:0:3974 blocked for more than 362 seconds.
[21751.075784] Not tainted 5.2.0-rc5-gfd2301817 #1
[21751.080866] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[21751.088713] kworker/2:0 D 0 3974 2 0x00000028
[21751.094366] Workqueue: ipv6_addrconf addrconf_verify_work [ipv6]
[21751.100441] Call trace:
[21751.102914] __switch_to+0xac/0x1b0
[21751.106416] __schedule+0x1e0/0x488
[21751.109914] schedule+0x38/0xc8
[21751.113107] schedule_preempt_disabled+0x20/0x38
[21751.117756] __mutex_lock.isra.1+0x1a0/0x4c0
[21751.122040] __mutex_lock_slowpath+0x10/0x18
[21751.126319] mutex_lock+0x38/0x40
[21751.129696] rtnl_lock+0x14/0x20
[21751.132995] addrconf_verify_work+0xc/0x20 [ipv6]
[21751.137717] process_one_work+0x1dc/0x338
[21751.141736] worker_thread+0x48/0x430
[21751.145428] kthread+0xf4/0x120
[21751.148623] ret_from_fork+0x10/0x18
[21871.609162] INFO: task systemd-network:339 blocked for more than 362 seconds.
[21871.616374] Not tainted 5.2.0-rc5-gfd2301817 #1
[21871.621471] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[21871.629338] systemd-network D 0 339 1 0x00000801
[21871.634898] Call trace:
[21871.637398] __switch_to+0xac/0x1b0
[21871.640892] __schedule+0x1e0/0x488
[21871.644396] schedule+0x38/0xc8
[21871.647550] schedule_preempt_disabled+0x20/0x38
[21871.652266] __mutex_lock.isra.1+0x1a0/0x4c0
[21871.656577] __mutex_lock_slowpath+0x10/0x18
[21871.660861] mutex_lock+0x38/0x40
[21871.664203] rtnetlink_rcv_msg+0xe4/0x390
[21871.668260] netlink_rcv_skb+0xe8/0x130
[21871.672148] rtnetlink_rcv+0x14/0x20
[21871.675756] netlink_unicast+0x188/0x208
[21871.679690] netlink_sendmsg+0x26c/0x338
[21871.683625] sock_sendmsg+0x18/0x30
[21871.687212] __sys_sendto+0xb8/0x138
[21871.690820] __arm64_sys_sendto+0x20/0x30
[21871.694847] el0_svc_common.constprop.0+0xb0/0x168
[21871.699664] el0_svc_handler+0x18/0x20
[21871.703469] el0_svc+0x8/0xc
[21871.706412] INFO: task NetworkManager:541 blocked for more than 362 seconds.
[21871.713500] Not tainted 5.2.0-rc5-gfd2301817 #1
[21871.718560] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[21871.726450] NetworkManager D 0 541 1 0x00000000
[21871.731967] Call trace:
[21871.734434] __switch_to+0xac/0x1b0
[21871.737973] __schedule+0x1e0/0x488
[21871.741506] schedule+0x38/0xc8
[21871.744650] schedule_preempt_disabled+0x20/0x38
[21871.749300] __mutex_lock.isra.1+0x1a0/0x4c0
[21871.753582] __mutex_lock_slowpath+0x10/0x18
[21871.757923] mutex_lock+0x38/0x40
[21871.761280] rtnetlink_rcv_msg+0xe4/0x390
[21871.765304] netlink_rcv_skb+0xe8/0x130
[21871.769152] rtnetlink_rcv+0x14/0x20
[21871.772760] netlink_unicast+0x188/0x208
[21871.776730] netlink_sendmsg+0x26c/0x338
[21871.780668] sock_sendmsg+0x18/0x30
[21871.784188] ___sys_sendmsg+0x27c/0x2a8
[21871.788035] __sys_sendmsg+0x60/0xb8
[21871.791696] __arm64_sys_sendmsg+0x1c/0x28
[21871.795857] el0_svc_common.constprop.0+0xb0/0x168
[21871.800662] el0_svc_handler+0x18/0x20
[21871.804423] el0_svc+0x8/0xc
[21871.807436] INFO: task kworker/2:0:3974 blocked for more than 483 seconds.
[21871.814359] Not tainted 5.2.0-rc5-gfd2301817 #1
[21871.819427] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[21871.827341] kworker/2:0 D 0 3974 2 0x00000028
[21871.832920] Workqueue: ipv6_addrconf addrconf_verify_work [ipv6]
[21871.838968] Call trace:
[21871.841457] __switch_to+0xac/0x1b0
[21871.844975] __schedule+0x1e0/0x488
[21871.848493] schedule+0x38/0xc8
[21871.851647] schedule_preempt_disabled+0x20/0x38
[21871.856276] __mutex_lock.isra.1+0x1a0/0x4c0
[21871.860633] __mutex_lock_slowpath+0x10/0x18
[21871.864940] mutex_lock+0x38/0x40
[21871.868278] rtnl_lock+0x14/0x20
[21871.871582] addrconf_verify_work+0xc/0x20 [ipv6]
[21871.876332] process_one_work+0x1dc/0x338
[21871.880390] worker_thread+0x48/0x430
[21871.884092] kthread+0xf4/0x120
[21871.887248] ret_from_fork+0x10/0x18
```
In this instance, existing SSH connections were up and working but attempts to make new SSH connections failed. Sudo consistently froze immediately and refused to be backgrounded. The following appeared in the process list:
```
3974 ? D 0:00 \_ [kworker/2:0+ipv6_addrconf]
4911 ? D 0:06 \_ [kworker/u8:3+events_unbound]
339 ? Ds 0:00 /lib/systemd/systemd-networkd
541 ? Dsl 0:15 /usr/sbin/NetworkManager --no-daemon
4986 pts/0 D+ 0:00 | \_ sudo journalctl -b -k
5050 pts/1 D+ 0:00 | \_ sudo ls
4940 ? Ds 0:00 \_ /usr/sbin/sshd -D -R
4965 ? Ds 0:00 \_ /usr/sbin/sshd -D -R
4969 ? Ds 0:00 \_ /usr/sbin/sshd -D -R
4896 ? Ds 0:00 /lib/systemd/systemd-networkd
4910 ? Ds 0:00 /lib/systemd/systemd-networkd
4944 ? Ds 0:00 /lib/systemd/systemd-networkd
4958 ? Ds 0:00 /lib/systemd/systemd-networkd
4972 ? Ds 0:00 /lib/systemd/systemd-networkd
5023 ? Ds 0:00 /lib/systemd/systemd-networkd
5036 ? Ds 0:00 /lib/systemd/systemd-networkd
```https://source.puri.sm/Librem5/linux/-/issues/60please enable rfkill2019-07-16T16:47:46ZGuido Guntherplease enable rfkillin the drm tree i have
```
CONFIG_RFKILL=m
CONFIG_RFKILL_GPIO=m
```in the drm tree i have
```
CONFIG_RFKILL=m
CONFIG_RFKILL_GPIO=m
```https://source.puri.sm/Librem5/linux/-/issues/64rtcwake can't wake the system from suspend2019-11-15T12:46:25ZAngus Ainslieangus.ainslie@puri.smrtcwake can't wake the system from suspendFeature: https://source.puri.sm/Librem5/use-cases/issues/75
Power button and volume buttons don't wake the system from suspend
EDIT: the following doesn't work either, and this issue is mainly about rtcwake:
rtcwake does wake the syst...Feature: https://source.puri.sm/Librem5/use-cases/issues/75
Power button and volume buttons don't wake the system from suspend
EDIT: the following doesn't work either, and this issue is mainly about rtcwake:
rtcwake does wake the system
rtcwake -m mem -s 10Last: Fuschia (W30-32)Martin KepplingerMartin Kepplingerhttps://source.puri.sm/Librem5/linux/-/issues/65devkit: needs an idea about battery level2019-07-24T16:34:52ZGuido Guntherdevkit: needs an idea about battery levelwith https://source.puri.sm/Librem5/upower we get proper charging / not charging indicators but we don't have a battery capacity yet. Maybe we can use simple-battery to build this and people can modify downstream when using different bat...with https://source.puri.sm/Librem5/upower we get proper charging / not charging indicators but we don't have a battery capacity yet. Maybe we can use simple-battery to build this and people can modify downstream when using different batteries.https://source.puri.sm/Librem5/linux/-/issues/66No mainline driver for accel LSM9DS12019-07-16T11:47:58ZAngus Ainslieangus.ainslie@puri.smNo mainline driver for accel LSM9DS1there is an out of tree driver we could use until ST ( or someone else ) comes on with something for mainline
https://github.com/jsagfr/lsm9ds1there is an out of tree driver we could use until ST ( or someone else ) comes on with something for mainline
https://github.com/jsagfr/lsm9ds1https://source.puri.sm/Librem5/linux/-/issues/67LCD artifacts2019-11-27T10:41:35ZDorota CzaplejewiczLCD artifactsThe LCD displays artifacts on the vertical borders of high contrast areas, where bright stripes a pixels or two wide intrude onto the other side. It's constantly changing, and rather noticeable with 10 of them happening at the same time ...The LCD displays artifacts on the vertical borders of high contrast areas, where bright stripes a pixels or two wide intrude onto the other side. It's constantly changing, and rather noticeable with 10 of them happening at the same time in a single word.
It looks like a localized phase artifact, kind of like this: http://www.lagom.nl/lcd-test/img/clockphase-wrong-2.gif , but not visible on a uniform background.https://source.puri.sm/Librem5/linux/-/issues/68Check that the VPU is not running2020-02-20T09:28:34ZMartin KepplingerCheck that the VPU is not runningAngus noticed that the vpu temperature is even higher than others. So we "should double check the imx8 clock initialization and see if that clock is off".
AFAIK there isn't any driver for it yet in mainline or development for it.
use-c...Angus noticed that the vpu temperature is even higher than others. So we "should double check the imx8 clock initialization and see if that clock is off".
AFAIK there isn't any driver for it yet in mainline or development for it.
use-cases#75https://source.puri.sm/Librem5/linux/-/issues/69ping activated upon outbound ping2022-02-28T10:00:08ZTodd Weaverping activated upon outbound pingReproduction:
1. power on devkit
2. use wifi on devkit
3. see ip address of devkit
4. ping ip address of devkit from another machine (see host unreachable)
5. ping out from devkit
6. see inbound ping respond
```
Linux pureos 5.2.0-gafd1...Reproduction:
1. power on devkit
2. use wifi on devkit
3. see ip address of devkit
4. ping ip address of devkit from another machine (see host unreachable)
5. ping out from devkit
6. see inbound ping respond
```
Linux pureos 5.2.0-gafd16fece #1 SMP PREEMPT Tue Jul 9 14:16:30 PDT 2019 aarch64 GNU/Linux
```
Notice in the below ping unresponsive in the left pane (laptop) then becomes responsive
```
From 192.168.1.68 icmp_seq=116 Destination Host Unreachable
From 192.168.1.68 icmp_seq=118 Destination Host Unreachable
64 bytes from 192.168.1.144: icmp_seq=121 ttl=64 time=875 ms
64 bytes from 192.168.1.144: icmp_seq=122 ttl=64 time=4.45 ms
```
It becomes responsive DUE TO the outbound ping command
```
purism@pureos:~$ sudo ping 192.168.1.68
PING 192.168.1.68 (192.168.1.68) 56(84) bytes of data.
64 bytes from 192.168.1.68: icmp_seq=1 ttl=64 time=122 ms
64 bytes from 192.168.1.68: icmp_seq=2 ttl=64 time=5.69 ms
```
![Screenshot_from_2019-07-14_18-55-16](/uploads/87be80eea9e8f65ff53a70425b977f1a/Screenshot_from_2019-07-14_18-55-16.png)https://source.puri.sm/Librem5/linux/-/issues/70cpufreq in 5.2 missing2024-02-18T11:25:37ZGuido Gunthercpufreq in 5.2 missingIt seems cpufreq went missing in 5.2:
```
# librem5-devkit-check
=============================================================================================== test session starts ======================================================...It seems cpufreq went missing in 5.2:
```
# librem5-devkit-check
=============================================================================================== test session starts ===============================================================================================
platform linux -- Python 3.7.3, pytest-3.10.1, py-1.7.0, pluggy-0.8.0
model: Purism Librem 5 devkit
kernel: Linux pureos 5.2.0-gef814e5c7 #1 SMP PREEMPT Sun Jul 14 16:27:34 PDT 2019 aarch64 GNU/Linux
image gitrev: 256fdadfaef7af8cfff128f55719b662fcf284c0
rootdir: /usr/share/librem5-devkit/check, inifile:
collected 11 items
test_audio.py .. [ 18%]
test_battery_charger.py . [ 27%]
test_cpufreq.py F [ 36%]
test_gpio_keys.py . [ 45%]
test_magn.py F [ 54%]
test_modem.py .. [ 72%]
test_panel_brightness.py . [ 81%]
test_touch.py . [ 90%]
test_usb_hub.py . [100%]
==================================================================================================== FAILURES =====================================================================================================
__________________________________________________________________________________________________ test_cpufreq ___________________________________________________________________________________________________
def test_cpufreq():
> assert("1000000" in open("/sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_min_freq").read())
E FileNotFoundError: [Errno 2] No such file or directory: '/sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_min_freq'
test_cpufreq.py:2: FileNotFoundError
```Martin KepplingerMartin Kepplingerhttps://source.puri.sm/Librem5/linux/-/issues/72The WWAN modem has to wake up the system from S3 suspend2020-02-12T12:04:32ZMartin KepplingerThe WWAN modem has to wake up the system from S3 suspend... on incoming SMS / call.
use-cases#75... on incoming SMS / call.
use-cases#75https://source.puri.sm/Librem5/linux/-/issues/74Support video decoding using the VPU (using gstreamer)2021-06-09T16:03:33ZMartin KepplingerSupport video decoding using the VPU (using gstreamer)Don't confuse this with https://source.puri.sm/Librem5/linux-next/issues/68 which only makes sure it's disabled until we can close this very issue (have support).
* Test and enhance what is being worked on upstream: https://lore.kernel....Don't confuse this with https://source.puri.sm/Librem5/linux-next/issues/68 which only makes sure it's disabled until we can close this very issue (have support).
* Test and enhance what is being worked on upstream: https://lore.kernel.org/linux-media/?q=hantro
* Testing: most probably using gstreamer's gst-launch-1.0 (zero-copy, performance debugging, ...)
* Also important: Document what exact codecs and containers are supported in what exact levels. i.e. what video files users can throw at it.
* nice-to-have: Have good support for a free codeoc like VP9https://source.puri.sm/Librem5/linux/-/issues/75create imx8-5.3-devkit branch and put it into current images2019-10-02T07:48:51ZMartin Kepplingercreate imx8-5.3-devkit branch and put it into current images(this might be boring, especially for @angus.ainslie and @guido.gunther and more like a note to myself, but it applies as long as we put 5.2 in the current images.)
* create a branch `imx8-5.3-devkit` that currently is the same commit ...(this might be boring, especially for @angus.ainslie and @guido.gunther and more like a note to myself, but it applies as long as we put 5.2 in the current images.)
* create a branch `imx8-5.3-devkit` that currently is the same commit as the imx8-linux-next-dev branch HEAD (but just stays at 5.3-rcX or 5.3 no matter what we do with the -next branch)
* is it ok to drop 5.2 in the build script? I guess so. nothing special about it. all our changes are in 5.3 AFAIK.
* our 5.3 based tree has new features needed for userspace and it adds no value to backport stuff
* 5.3-rcX is basically identical to the 5.3 release and stable enough for us. no need to wait.
* switch from 5.2 to 5.3 in https://source.puri.sm/Librem5/image-builder/blob/master/conf/board#L85
* add a new jenkins kernel build (?) similar to https://arm01.puri.sm/job/Kernel_builds/job/kernel_devkit_linux-next_imx8-5.2-devkit/ ?
* advantage: we can then branch out into a real -next in our main -next branch if one would want tohttps://source.puri.sm/Librem5/linux/-/issues/76`poweroff` leaves board unbootable without power cycle2019-10-04T07:56:21ZGuido Gunther`poweroff` leaves board unbootable without power cycleShutting down with `poweroff` doesn't make the bord wake up on power button press. I have to
- unplug the usb-c cable
- remove the battery
put either of these back in to boot the board. Am i missing something obvious here?Shutting down with `poweroff` doesn't make the bord wake up on power button press. I have to
- unplug the usb-c cable
- remove the battery
put either of these back in to boot the board. Am i missing something obvious here?https://source.puri.sm/Librem5/linux/-/issues/78Enable ftrace in kernel2019-08-27T14:51:50ZKyle RankinEnable ftrace in kernelI would like to provide opensnitch on the Librem 5 (https://github.com/evilsocket/opensnitch) and it requires ftrace (CONFIG_FTRACE) to be enabled in the kernel.
Could you please enable this in our kernel?I would like to provide opensnitch on the Librem 5 (https://github.com/evilsocket/opensnitch) and it requires ftrace (CONFIG_FTRACE) to be enabled in the kernel.
Could you please enable this in our kernel?https://source.puri.sm/Librem5/linux/-/issues/80Rebase 5.3 kernel in linux-next2023-12-14T08:00:28ZAngus Ainslieangus.ainslie@puri.smRebase 5.3 kernel in linux-nextBring MRs in for 5.3 kernelBring MRs in for 5.3 kernelNext: Bud (W34-36)Angus Ainslieangus.ainslie@puri.smAngus Ainslieangus.ainslie@puri.smhttps://source.puri.sm/Librem5/linux/-/issues/81cpuidle_cooling_register use after free2019-09-12T09:05:43ZAngus Ainslieangus.ainslie@puri.smcpuidle_cooling_register use after freeJust got a use after free warning in the 5.3-rc6 kernel
[ 1.151665] ------------[ cut here ]------------
[ 1.156497] refcount_t: increment on 0; use-after-free.
[ 1.162008] W...Just got a use after free warning in the 5.3-rc6 kernel
[ 1.151665] ------------[ cut here ]------------
[ 1.156497] refcount_t: increment on 0; use-after-free.
[ 1.162008] WARNING: CPU: 2 PID: 1 at lib/refcount.c:156 refcount_inc_checked+0x40/0x48
[ 1.170345] Modules linked in:
[ 1.173534] CPU: 2 PID: 1 Comm: swapper/0 Not tainted 5.3.0-rc6-00111-g8d6dae8619b6 #222
[ 1.181961] Hardware name: Purism Librem 5 devkit (DT)
[ 1.187316] pstate: 80000005 (Nzcv daif -PAN -UAO)
[ 1.192310] pc : refcount_inc_checked+0x40/0x48
[ 1.197032] lr : refcount_inc_checked+0x40/0x48
[ 1.201751] sp : ffff8000a7d5fc90
[ 1.205205] x29: ffff8000a7d5fc90 x28: 0000000000000000
[ 1.210741] x27: ffff8000a7d5fd10 x26: ffff000010d68000
[ 1.216278] x25: ffff000010d68f70 x24: ffff000010d68000
[ 1.221814] x23: 0000000000000000 x22: ffff000010e72060
[ 1.227351] x21: 0000000000000000 x20: 0000000000000000
[ 1.232887] x19: ffff8000a7eafe00 x18: ffffffffffffffff
[ 1.238423] x17: 0000000000000001 x16: 0000000000000000
[ 1.243959] x15: ffff000010d685c8 x14: ffff800127d5f997
[ 1.249495] x13: ffff8000a7d5f9a5 x12: ffff000010d88000
[ 1.255031] x11: 0000000005f5e0ff x10: ffff000010d685f0
[ 1.260567] x9 : ffff000010d46018 x8 : 000000000000052b
[ 1.266103] x7 : 0000000000000006 x6 : 0000000000000001
[ 1.271639] x5 : ffff00001010cbe4 x4 : 0000000000000001
[ 1.277175] x3 : 0000000000000001 x2 : ffff8000a7d80000
[ 1.282711] x1 : d5e73df49852f500 x0 : 0000000000000000
[ 1.288247] Call trace:
[ 1.290800] refcount_inc_checked+0x40/0x48
[ 1.295165] cpuidle_cooling_register+0x138/0x2ac
[ 1.300068] arm_idle_init+0x130/0x190
[ 1.303979] do_one_initcall+0x50/0x298
[ 1.307980] kernel_init_freeable+0x300/0x3a4
[ 1.312523] kernel_init+0x18/0x110
[ 1.316160] ret_from_fork+0x10/0x1c
[ 1.319890] ---[ end trace 469e581645c9b0ba ]---Martin KepplingerMartin Kepplingerhttps://source.puri.sm/Librem5/linux/-/issues/82Redpoine warning on reboot2019-08-28T13:55:36ZAngus Ainslieangus.ainslie@puri.smRedpoine warning on rebootThe redpine driver issues a warninng during shutdown
```
[ 168.852416] systemd-shutdown[1]: All loop devices detached.
[ 168.861709] [948]: Remounting '/' read-only in with options 'errors=remount-ro'.
[ 168.869606] [948]: Failed to ...The redpine driver issues a warninng during shutdown
```
[ 168.852416] systemd-shutdown[1]: All loop devices detached.
[ 168.861709] [948]: Remounting '/' read-only in with options 'errors=remount-ro'.
[ 168.869606] [948]: Failed to remount '/' read-only: Device or resource busy
[ 168.889646] rsi_91x: SDIO Bus shutdown =====>
[ 168.894369] WARNING: CPU: 3 PID: 1 at drivers/net/wireless/rsi/rsi_91x_mac80211.c:2650 rsi_config_wowlan+0x14c/0x178]
[ 168.906231] Modules linked in: aes_ce_ccm qmi_wwan option cdc_wdm usb_wwan usbnet mii usbserial bnep mousedev xhci_p6
[ 168.980794] CPU: 3 PID: 1 Comm: systemd-shutdow Not tainted 5.2.0-00097-gef814e5c7b41 #224
[ 168.989400] Hardware name: Purism Librem 5 devkit (DT)
[ 168.994753] pstate: 40000005 (nZcv daif -PAN -UAO)
[ 168.999757] pc : rsi_config_wowlan+0x14c/0x178 [rsi_91x]
[ 169.005302] lr : rsi_config_wowlan+0x30/0x178 [rsi_91x]
[ 169.010742] sp : ffff8000a7c93c40
[ 169.014194] x29: ffff8000a7c93c40 x28: ffff8000a7c88000
[ 169.019727] x27: 0000000000000000 x26: 0000000000000000
[ 169.025261] x25: ffff0000109f5ec8 x24: ffff000010bc9040
[ 169.030795] x23: ffff8000a72b5888 x22: ffff000010c1c000
[ 169.036330] x21: ffff8000a03c50b8 x20: ffff8000a7d46000
[ 169.041864] x19: 0000000000000000 x18: 000000000000000d
[ 169.047398] x17: 0000000000000001 x16: 0000000000000000
[ 169.052932] x15: ffff8000a73c1f90 x14: ffff8000a685d088
[ 169.058466] x13: 0000000000000001 x12: 0000000000000000
[ 169.064000] x11: ffff8000a7c93be8 x10: ffff8000a7c93c10
[ 169.069534] x9 : 00000000ffffffd0 x8 : 0000000000000001
[ 169.075069] x7 : ffff8000a73ca900 x6 : 00000000022ca217
[ 169.080603] x5 : 000000000000008c x4 : 0000000000000003
[ 169.086136] x3 : 0000000000000001 x2 : ffff8000a1eb2000
[ 169.091670] x1 : bf280b3a49c74300 x0 : 0000000000000000
[ 169.097205] Call trace:
[ 169.099766] rsi_config_wowlan+0x14c/0x178 [rsi_91x]
[ 169.104942] rsi_shutdown+0x4c/0xd0 [rsi_sdio]
[ 169.109577] device_shutdown+0x10c/0x1f0
[ 169.113668] kernel_restart_prepare+0x34/0x40
[ 169.118206] kernel_restart+0x14/0x78
[ 169.122021] __se_sys_reboot+0x108/0x210
[ 169.126108] __arm64_sys_reboot+0x18/0x20
[ 169.130288] el0_svc_common.constprop.0+0x64/0x160
[ 169.135279] el0_svc_handler+0x18/0x20
[ 169.139186] el0_svc+0x8/0xc
[ 169.142187] ---[ end trace db5fd2e9b200317c ]---
[ 169.147108] rsi_91x: WoW triggers not enabled
[ 169.151683] rsi_91x: Failed to configure WoWLAN
[ 169.156938] rsi_91x: Waiting for interrupts to be cleared..
[ 169.157515] rsi_91x: .
[ 169.163338] rsi_91x:
[ 169.163338] Interrupts cleared
[ 169.211382] imx2-wdt 30280000.watchdog: Device shutdown: Expect reboot!
[ 169.224370] reboot: Restarting system
```https://source.puri.sm/Librem5/linux/-/issues/83ldo5 regulator breaks S3 suspend2019-12-09T11:30:14ZMartin Kepplingerldo5 regulator breaks S3 suspendFeature: https://source.puri.sm/Librem5/use-cases/issues/75
initial tests and reports on the **devkit**: https://source.puri.sm/Librem5/linux-next/issues/64
```
root@pureos:/home/purism# rtcwake -d rtc0 -m mem -s 5
rtcwake: assuming RT...Feature: https://source.puri.sm/Librem5/use-cases/issues/75
initial tests and reports on the **devkit**: https://source.puri.sm/Librem5/linux-next/issues/64
```
root@pureos:/home/purism# rtcwake -d rtc0 -m mem -s 5
rtcwake: assuming RTC uses UTC ...
rtcwake: wakeup from "mem" using rtc0 at Thu Jan 1 00:02:09 1970
[ 130.134386] ldo5: failed to disable
[ 130.134394] imx-pgc imx-pgc-domain.0: failed to disable regulator: -13
[ 130.661490] phy phy-30a00300.dphy.0: Could not get DPHY lock (-110)!
[ 130.661499] phy phy-30a00300.dphy.0: phy poweron failed --> -110
[ 130.661509] imx-nwl-dsi 30a00000.mipi_dsi: [drm:nwl_dsi_enable] *ERROR* Failed to power on DPHY (-110)
```https://source.puri.sm/Librem5/linux/-/issues/84cpu idle cooling driver breaks S3 suspend2019-12-09T11:21:57ZMartin Kepplingercpu idle cooling driver breaks S3 suspendFeature: https://source.puri.sm/Librem5/use-cases/issues/75
initial tests and reports on the **devkit**: https://source.puri.sm/Librem5/linux-next/issues/64
our out-of-tree cooling driver (`CONFIG_CPU_IDLE_THERMAL=y`) that uses cpu-idl...Feature: https://source.puri.sm/Librem5/use-cases/issues/75
initial tests and reports on the **devkit**: https://source.puri.sm/Librem5/linux-next/issues/64
our out-of-tree cooling driver (`CONFIG_CPU_IDLE_THERMAL=y`) that uses cpu-idle (autor: Daniel Lezcano) breaks S3 suspend. for the bugreport, see: https://lore.kernel.org/linux-pm/34b1ed94-1223-60ec-ac4f-0b32be67eab2@linaro.org/https://source.puri.sm/Librem5/linux/-/issues/85S3 resume sometimes hangs up the GPU / etnaviv2023-12-07T17:48:35ZMartin KepplingerS3 resume sometimes hangs up the GPU / etnavivFeature: https://source.puri.sm/Librem5/use-cases/issues/75
when resuming from suspend, I sometimes get:
```
[ 1265.539186] etnaviv-gpu 38000000.gpu: recover hung GPU!
[ 1266.179170] etnaviv-gpu 38000000.gpu: recover hung GPU!
[ 1266.8...Feature: https://source.puri.sm/Librem5/use-cases/issues/75
when resuming from suspend, I sometimes get:
```
[ 1265.539186] etnaviv-gpu 38000000.gpu: recover hung GPU!
[ 1266.179170] etnaviv-gpu 38000000.gpu: recover hung GPU!
[ 1266.819181] etnaviv-gpu 38000000.gpu: recover hung GPU!
[ 1267.459696] etnaviv-gpu 38000000.gpu: recover hung GPU!
[ 1268.099711] etnaviv-gpu 38000000.gpu: recover hung GPU!
[ 1270.499717] etnaviv-gpu 38000000.gpu: recover hung GPU!
[ 1271.139698] etnaviv-gpu 38000000.gpu: recover hung GPU!
[ 1271.779167] etnaviv-gpu 38000000.gpu: recover hung GPU!
[ 1272.419174] etnaviv-gpu 38000000.gpu: recover hung GPU!
[ 1273.059167] etnaviv-gpu 38000000.gpu: recover hung GPU!
[ 1273.699711] etnaviv-gpu 38000000.gpu: recover hung GPU!
[ 1274.339157] etnaviv-gpu 38000000.gpu: recover hung GPU!
[ 1274.979149] etnaviv-gpu 38000000.gpu: recover hung GPU!
[ 1278.499174] etnaviv-gpu 38000000.gpu: recover hung GPU!
[ 1279.139169] etnaviv-gpu 38000000.gpu: recover hung GPU!
[ 1279.779173] etnaviv-gpu 38000000.gpu: recover hung GPU!
[ 1280.419678] etnaviv-gpu 38000000.gpu: recover hung GPU!
```https://source.puri.sm/Librem5/linux/-/issues/86S3 resume sometimes triggers mmc1 interrupt timeout2019-12-17T14:02:08ZMartin KepplingerS3 resume sometimes triggers mmc1 interrupt timeoutFeature: https://source.puri.sm/Librem5/use-cases/issues/75
```
[ 185.571412] mmc1: Timeout waiting for hardware interrupt.
[ 185.571418] mmc1: sdhci: ============ SDHCI REGISTER DUMP ===========
[ 185.571423] mmc1: sdhci: Sys addr: ...Feature: https://source.puri.sm/Librem5/use-cases/issues/75
```
[ 185.571412] mmc1: Timeout waiting for hardware interrupt.
[ 185.571418] mmc1: sdhci: ============ SDHCI REGISTER DUMP ===========
[ 185.571423] mmc1: sdhci: Sys addr: 0x00000000 | Version: 0x00000002
[ 185.571428] mmc1: sdhci: Blk size: 0x00000100 | Blk cnt: 0x00000001
[ 185.571433] mmc1: sdhci: Argument: 0x91820100 | Trn mode: 0x00000003
[ 185.571438] mmc1: sdhci: Present: 0x01f88008 | Host ctl: 0x00000013
[ 185.571442] mmc1: sdhci: Power: 0x00000002 | Blk gap: 0x00000080
[ 185.571446] mmc1: sdhci: Wake-up: 0x00000008 | Clock: 0x0000003f
[ 185.571450] mmc1: sdhci: Timeout: 0x0000008f | Int stat: 0x00000000
[ 185.571454] mmc1: sdhci: Int enab: 0x007f1003 | Sig enab: 0x007f1003
[ 185.571458] mmc1: sdhci: ACmd stat: 0x00000000 | Slot int: 0x00008402
[ 185.571463] mmc1: sdhci: Caps: 0x07eb0000 | Caps_1: 0x8000b407
[ 185.571467] mmc1: sdhci: Cmd: 0x0000353a | Max curr: 0x00ffffff
[ 185.571471] mmc1: sdhci: Resp[0]: 0x00002000 | Resp[1]: 0x00000000
[ 185.571475] mmc1: sdhci: Resp[2]: 0x00000000 | Resp[3]: 0x00000000
[ 185.571479] mmc1: sdhci: Host ctl2: 0x00000000
[ 185.571484] mmc1: sdhci: ADMA Err: 0x00000000 | ADMA Ptr: 0x00000000
[ 185.571486] mmc1: sdhci: ============================================
```https://source.puri.sm/Librem5/linux/-/issues/88Switch to softpin2023-04-11T10:33:40ZGuido GuntherSwitch to softpinBackport the etnaviv per process mmu patches to 5.3 and update mesa to use that for softpin. This needs a coordinated kernel/mesa update. Debian experimental has mesa 1.19.2~rc3 which has most of the changes.Backport the etnaviv per process mmu patches to 5.3 and update mesa to use that for softpin. This needs a coordinated kernel/mesa update. Debian experimental has mesa 1.19.2~rc3 which has most of the changes.https://source.puri.sm/Librem5/linux/-/issues/89investigate IMX8MQ_CLK_NOC2020-07-20T17:21:14ZGuido Guntherinvestigate IMX8MQ_CLK_NOCnxp's bsp has
```
/* increase NOC clock to achieve best DDR access performance */
clk_set_rate(clks[IMX8MQ_CLK_NOC], clk_get_rate(clks[IMX8MQ_SYS1_PLL_800M]));
```
which gives
```
noc 1 1 ...nxp's bsp has
```
/* increase NOC clock to achieve best DDR access performance */
clk_set_rate(clks[IMX8MQ_CLK_NOC], clk_get_rate(clks[IMX8MQ_SYS1_PLL_800M]));
```
which gives
```
noc 1 1 0 800000000 0 0 50000
```
while we have
```
noc 1 1 0 400000000 0 0 50000
```https://source.puri.sm/Librem5/linux/-/issues/91Redpine firmware loaded from flash doesn't report version number2019-11-05T15:11:57ZAngus Ainslieangus.ainslie@puri.smRedpine firmware loaded from flash doesn't report version numberThe code path for loading firmware from flash is different from the ram firmware loading. In the flash loading case the LMAC version number does not get populated.
```
root@pureos:~# cat /sys/kernel/debug/phy0/version
Driver : RS9116.NB...The code path for loading firmware from flash is different from the ram firmware loading. In the flash loading case the LMAC version number does not get populated.
```
root@pureos:~# cat /sys/kernel/debug/phy0/version
Driver : RS9116.NB0.NL.PURISM.LNX.1.3
LMAC : 0.0.0.0
```https://source.puri.sm/Librem5/linux/-/issues/92Set SD2_VSELECT HIGH2019-10-01T20:52:41ZEric KuzmenkoSet SD2_VSELECT HIGHIn order to make SDHC2 use a 1.8V logic level SD2_VSELECT used on the dev kit SoM must be set as logic HIGH.
SD2_VSELECT is controlled by GPIO1_IO04.In order to make SDHC2 use a 1.8V logic level SD2_VSELECT used on the dev kit SoM must be set as logic HIGH.
SD2_VSELECT is controlled by GPIO1_IO04.Angus Ainslieangus.ainslie@puri.smAngus Ainslieangus.ainslie@puri.smhttps://source.puri.sm/Librem5/linux/-/issues/93Unified librem5_defconfig2020-11-17T16:33:11ZGuido GuntherUnified librem5_defconfigAt least imx8-{current,next}-devkit don't use the unified `librem_defconig` that we used for the phone bringup. Can this be fixed since it prevents me from enabling other options since it's not clear where these should go without causing...At least imx8-{current,next}-devkit don't use the unified `librem_defconig` that we used for the phone bringup. Can this be fixed since it prevents me from enabling other options since it's not clear where these should go without causing more work down the road or options getting lost.https://source.puri.sm/Librem5/linux/-/issues/94enable CONFIG_CGROUP_FREEZER2019-10-07T21:42:27ZGuido Guntherenable CONFIG_CGROUP_FREEZERthis is needed for anbox accoring the librem5-devkit-channelthis is needed for anbox accoring the librem5-devkit-channelhttps://source.puri.sm/Librem5/linux/-/issues/95enable DM_CRYPT2019-10-01T18:32:18ZGuido Guntherenable DM_CRYPTwe had this one, please reenablewe had this one, please reenablehttps://source.puri.sm/Librem5/linux/-/issues/96enable CONFIG_FS_F2FS2019-10-01T18:31:02ZGuido Guntherenable CONFIG_FS_F2FS@angus.ainslie just so this does not get forgotten: as asked on `-kernel` a while ago please enable CONFIG_FS_F2FS
```
CONFIG_F2FS_FS=m
CONFIG_F2FS_STAT_FS=y
CONFIG_F2FS_FS_XATTR=y
CONFIG_F2FS_FS_POSIX_ACL=y
CONFIG_F2FS_FS_SECURITY=y
CO...@angus.ainslie just so this does not get forgotten: as asked on `-kernel` a while ago please enable CONFIG_FS_F2FS
```
CONFIG_F2FS_FS=m
CONFIG_F2FS_STAT_FS=y
CONFIG_F2FS_FS_XATTR=y
CONFIG_F2FS_FS_POSIX_ACL=y
CONFIG_F2FS_FS_SECURITY=y
CONFIG_F2FS_FS_ENCRYPTION=y
```
no urgency since i have this in my local builds, can happen after #93https://source.puri.sm/Librem5/linux/-/issues/100Redpine module does not support WOW2022-01-12T16:25:52ZAngus Ainslieangus.ainslie@puri.smRedpine module does not support WOWWithout Wake on Wireless (WOW) the redpine module won't be able to wake us from sleep.Without Wake on Wireless (WOW) the redpine module won't be able to wake us from sleep.https://source.puri.sm/Librem5/linux/-/issues/101repository hygiene2019-11-27T18:31:44ZGuido Guntherrepository hygieneit seems MRs should currently go against `imx8-current-librem5` so we should
- make this the repos default branch so MRs pick the right branch
- drop imx8-current-devkit since this is confusing (and alredy confused community members)
i...it seems MRs should currently go against `imx8-current-librem5` so we should
- make this the repos default branch so MRs pick the right branch
- drop imx8-current-devkit since this is confusing (and alredy confused community members)
i can make the changes but wanted to check with @angus.ainslie to net break one of his workflows.https://source.puri.sm/Librem5/linux/-/issues/103Add batch names to device tree files names and board type2020-07-16T08:54:06ZGuido GuntherAdd batch names to device tree files names and board typeWith birch moving into place we should
- rename `arch/arm64/boot/dts/freescale/imx8mq-librem5.dts` to `arch/arm64/boot/dts/freescale/imx8mq-librem5.dtsi`
- add `arch/arm64/boot/dts/freescale/imx8mq-librem5-aspen.dts` and `arch/arm64/boo...With birch moving into place we should
- rename `arch/arm64/boot/dts/freescale/imx8mq-librem5.dts` to `arch/arm64/boot/dts/freescale/imx8mq-librem5.dtsi`
- add `arch/arm64/boot/dts/freescale/imx8mq-librem5-aspen.dts` and `arch/arm64/boot/dts/freescale/imx8mq-librem5-birch.dts`
- adjust the `model` in each dts accordingly, e.g. `Purism Librem 5 Aspen`
- adjust any further hardware chanegs
so we can distinguish the batches later on for updates from userspace and to identify customer devices and to e.g. pick the right uboot / dtb file when updating.https://source.puri.sm/Librem5/linux/-/issues/105review wakeup-source configs in devicetree2019-12-17T14:29:08ZMartin Kepplingerreview wakeup-source configs in devicetreeFeature: https://source.puri.sm/Librem5/use-cases/issues/75
sometimes the system would currently just resume after suspending. also, the console wakes it up.
review our dts for possible unnecessary wakeup sources for real-life workloads.Feature: https://source.puri.sm/Librem5/use-cases/issues/75
sometimes the system would currently just resume after suspending. also, the console wakes it up.
review our dts for possible unnecessary wakeup sources for real-life workloads.https://source.puri.sm/Librem5/linux/-/issues/106Dev Kit VSYS_MIN Too Low2020-04-14T15:20:46ZEric KuzmenkoDev Kit VSYS_MIN Too LowVSYS_MIN on the Dev Kit device tree must be 3.5V or higher.VSYS_MIN on the Dev Kit device tree must be 3.5V or higher.Angus Ainslieangus.ainslie@puri.smAngus Ainslieangus.ainslie@puri.smhttps://source.puri.sm/Librem5/linux/-/issues/107build kernels with a stable kver2022-08-23T10:11:05ZGuido Guntherbuild kernels with a stable kvercurrently each build debian package has the git revision in the package name, that is great for development but for long term maintenance we want to creat specific packages like
`linux-image-5.4.0-1-librem5`
that is
`linux-iamge-<ups...currently each build debian package has the git revision in the package name, that is great for development but for long term maintenance we want to creat specific packages like
`linux-image-5.4.0-1-librem5`
that is
`linux-iamge-<upstream-version>-<abi-version>-librem5`
since we otherwise fill up user partitions quickly. These package will then be built with `deb-pkg` instead of `bindeb-pkg` so we can (hopefully) upload them to the pureos archive. the `amber-phone` images can then pull in these instaed of fetching latest, this also gives us a testing period in `amber-phone-staging`.
this involves several components, just starting here since we need to build such package first (i guess manually would even be o.k. as a start)https://source.puri.sm/Librem5/linux/-/issues/108drop our old etnaviv BO management2023-12-07T17:48:40ZGuido Guntherdrop our old etnaviv BO managementjust a single revert but i want to test it first und so i don't forgetjust a single revert but i want to test it first und so i don't forgethttps://source.puri.sm/Librem5/linux/-/issues/109Power Button Not Turning Device Back On2020-03-23T17:46:30ZEric KuzmenkoPower Button Not Turning Device Back OnThe power button no longer turns the device back on after the PMIC is shut down (this worked on kernel 5.3.0-g8908ba21f).
I can tell that BUCK6 (VDD_3V3) is turning on when the power button is pressed because the red LED becomes illumin...The power button no longer turns the device back on after the PMIC is shut down (this worked on kernel 5.3.0-g8908ba21f).
I can tell that BUCK6 (VDD_3V3) is turning on when the power button is pressed because the red LED becomes illuminated after pressing it but it does not bring up the SoC. This means the issue is likely has something to do with how the PMIC is configured to handle the button press events in one of its I2C registers (e.g. something like C1_SHORT_PUSH_EN, C1_LONG_PUSH_EN, etc).
In Matrix @angus.ainslie mentioned this commit as a potential suspect (though he said reverting this would prevent the screen blanking function: https://source.puri.sm/Librem5/linux-next/commit/6f9f6dec1a089a4e31da464e289fb4c61f4e38e9
The workaround for this issue is to press and hold the power button for 15-18 seconds or so in order to cause the BQ25895 charge controller to hard-reset the entire device.Angus Ainslieangus.ainslie@puri.smAngus Ainslieangus.ainslie@puri.smhttps://source.puri.sm/Librem5/linux/-/issues/110Battery doesn't charge2021-02-03T13:57:04ZAngus Ainslieangus.ainslie@puri.smBattery doesn't chargeEN_SNK doesn't turn on the BQ25896EN_SNK doesn't turn on the BQ25896https://source.puri.sm/Librem5/linux/-/issues/111Cellular modem hardware kill switch activation2020-04-06T18:15:53ZTodd WeaverCellular modem hardware kill switch activationReproduction:
1. Cellular ON
2. Cellular turned OFF
3. Active connection still visible
![hks-cellular-not-triggered](/uploads/562801dda3ecf0735503d887f0a69b05/hks-cellular-not-triggered.webm)Reproduction:
1. Cellular ON
2. Cellular turned OFF
3. Active connection still visible
![hks-cellular-not-triggered](/uploads/562801dda3ecf0735503d887f0a69b05/hks-cellular-not-triggered.webm)Angus Ainslieangus.ainslie@puri.smAngus Ainslieangus.ainslie@puri.smhttps://source.puri.sm/Librem5/linux/-/issues/112system shutdown doesn't work on linux-next2019-12-04T17:43:19ZMartin Kepplingersystem shutdown doesn't work on linux-nextrunning: https://source.puri.sm/martin.kepplinger/linux-next/commits/next-20191203/librem5
the following, as can be seen, takes "forever" until the board shuts down:
```
[ OK ] Reached target Shutdown.
[ OK ] Reached target Final S...running: https://source.puri.sm/martin.kepplinger/linux-next/commits/next-20191203/librem5
the following, as can be seen, takes "forever" until the board shuts down:
```
[ OK ] Reached target Shutdown.
[ OK ] Reached target Final Step.
[ OK ] Started Power-Off.
[ OK ] Reached target Power-Off.
[ 285.640686] printk: systemd-shutdow: 52 output lines suppressed due to ratelimiting
[ 285.690524] systemd-shutdown[1]: Syncing filesystems and block devices.
[ 285.748499] systemd-shutdown[1]: Sending SIGTERM to remaining processes...
[ 285.765379] systemd-journald[279]: Received SIGTERM from PID 1 (systemd-shutdow).
[ 363.615165] INFO: task qmi-proxy:534 blocked for more than 120 seconds.
[ 363.621812] Not tainted 5.4.0-next-20191203-librem5-00005-g589ded0936f7 #14
[ 363.629337] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[ 363.637388] qmi-proxy D 0 534 1 0x0000082d
[ 363.642891] Call trace:
[ 363.645359] __switch_to+0xc0/0x210
[ 363.648878] __schedule+0x288/0x5a8
[ 363.652380] schedule+0x48/0x100
[ 363.655627] wdm_flush+0xe8/0x128 [cdc_wdm]
[ 363.659840] filp_close+0x3c/0x90
[ 363.663170] put_files_struct+0x110/0x118
[ 363.667192] exit_files+0x44/0x58
[ 363.670512] do_exit+0x2a8/0x9f8
[ 363.673767] do_group_exit+0x48/0xa8
[ 363.677357] get_signal+0xec/0x828
[ 363.680772] do_notify_resume+0x30c/0x468
[ 363.684808] work_pending+0x8/0x14
[ 375.764807] systemd-shutdown[1]: Sending SIGKILL to remaining processes...
[ 375.778374] systemd-shutdown[1]: Sending SIGKILL to PID 534 (qmi-proxy).
[ 465.789929] systemd-shutdown[1]: Unmounting file systems.
[ 465.798316] [757]: Remounting '/' read-only in with options 'errors=remount-ro'.
[ 465.818562] [757]: Failed to remount '/' read-only: Device or resource busy
[ 465.826512] systemd-shutdown[1]: Not all file systems unmounted, 1 left.
[ 465.833311] systemd-shutdown[1]: Deactivating swaps.
[ 465.838471] systemd-shutdown[1]: All swaps deactivated.
[ 465.843737] systemd-shutdown[1]: Detaching loop devices.
[ 465.852775] systemd-shutdown[1]: All loop devices detached.
[ 465.858375] systemd-shutdown[1]: Detaching DM devices.
[ 465.863722] systemd-shutdown[1]: All DM devices detached.
[ 465.870004] systemd-shutdown[1]: Unmounting file systems.
[ 465.877736] [758]: Remounting '/' read-only in with options 'errors=remount-ro'.
[ 465.885347] [758]: Failed to remount '/' read-only: Device or resource busy
[ 465.893069] systemd-shutdown[1]: Not all file systems unmounted, 1 left.
[ 465.965278] reboot: Power down
```https://source.puri.sm/Librem5/linux/-/issues/11350% packet loss to redpine module in birch device2021-02-26T02:09:04ZBob Ham50% packet loss to redpine module in birch deviceAfter connecting to an open wireless network and pinging the device from another host:
```
138 packets transmitted, 68 received, +4 errors, 50.7246% packet loss, time 1046ms
rtt min/avg/max/mdev = 1.327/17.759/872.240/104.491 ms, pipe 4...After connecting to an open wireless network and pinging the device from another host:
```
138 packets transmitted, 68 received, +4 errors, 50.7246% packet loss, time 1046ms
rtt min/avg/max/mdev = 1.327/17.759/872.240/104.491 ms, pipe 4
```
This unfortunately makes remote SSH unusable.Angus Ainslieangus.ainslie@puri.smAngus Ainslieangus.ainslie@puri.smhttps://source.puri.sm/Librem5/linux/-/issues/114USB devices connected through a hub are not seen by the kernel on birch device2021-02-01T17:46:13ZBob HamUSB devices connected through a hub are not seen by the kernel on birch deviceI've tried to connect both a j5 Create JCA374 and Startech HB30C3AGEPD hub. One end of the thick type-C to type-C cable is plugged into the wall wart and the other end is plugged into the hub's power port. The hub's cable is plugged in...I've tried to connect both a j5 Create JCA374 and Startech HB30C3AGEPD hub. One end of the thick type-C to type-C cable is plugged into the wall wart and the other end is plugged into the hub's power port. The hub's cable is plugged into the type-C socket on the birch device.
In both cases, the battery icon in the status bar in phosh changes to the charging icon. However, no devices connected to the hub's ports are seen by the kernel. On the j5 Create hub, a mouse plugged in does not get powered up. On the Startech hub, the mouse is powered up (lights come on) but nothing is seen by the kernel. Devices on my KVM switch are not seen. None of the on-board devices in either hub, in particular the Ethernet NIC (the motivation for getting the USB port working), are seen by the kernel.
This is very similar to the behaviour described in linux-emcraft#41.https://source.puri.sm/Librem5/linux/-/issues/115Clock doesn't keep time across power-down and later power-up2020-01-03T03:47:23ZTodd WeaverClock doesn't keep time across power-down and later power-up# What problem did you encounter
The clock does not keep time current upon power-up.
## What is the current behaviour?
Power down at 11:03am; wait 10 minutes; power-up it shows 11:03am (and will until a network connection updates it)....# What problem did you encounter
The clock does not keep time current upon power-up.
## What is the current behaviour?
Power down at 11:03am; wait 10 minutes; power-up it shows 11:03am (and will until a network connection updates it).
## What is the expected behaviour?
Hardware clock is set, and is used to show current time.
## How to reproduce
1. Power down; note actual time.
2. Wait a few minutes.
3. Power up; note it was the same time as power-down.
```
purism@pureos:~$ dpkg -s phosh
Package: phosh
Status: install ok installed
Priority: optional
Section: x11
Installed-Size: 804
Maintainer: Guido Günther <agx@sigxcpu.org>
Architecture: arm64
Version: 0.1.4
Provides: notification-daemon, polkit-1-auth-agent
Depends: dconf-gsettings-backend | gsettings-backend, libc6 (>= 2.17), libcairo2 (>= 1.2.4), libgcr-base-3-1 (>= 3.8.0), libgcr-ui-3-1 (>= 3.8.0), libgdk-pixbuf2.0-0 (>= 2.22.0), libglib2.0-0 (>= 2.53.2), libgnome-desktop-3-17 (>= 3.17.92), libgtk-3-0 (>= 3.21.5), libhandy-0.0-0 (>= 0.0.11), libnm0 (>= 1.0.0), libpam0g (>= 0.99.7.1), libpango-1.0-0 (>= 1.22.0), libpangocairo-1.0-0 (>= 1.14.0), libpolkit-agent-1-0 (>= 0.99), libpolkit-gobject-1-0 (>= 0.94), libpulse-mainloop-glib0 (>= 0.99.1), libpulse0 (>= 0.99.1), libsecret-1-0 (>= 0.7), libupower-glib3 (>= 0.99.4-3~), libwayland-client0 (>= 1.9.91), fonts-lato
Recommends: gnome-session, phoc
Description: Pure Wayland shell for mobile devices
Phosh is a simple shell for Wayland compositors speaking the layer-surface
protocol. It currently supports
.
* a lockscreen
* brightness control and nighlight
* the gcr system-prompter interface
* acting as a polkit auth agent
* enough of org.gnome.Mutter.DisplayConfig to make gnome-settings-daemon happy
* a homebutton that toggles a simple favorites menu
* status icons for battery, wwan and wifi
.
If you're not working on a Wayland compositor then this package is likely not
very useful for you.
Homepage: https://source.puri.sm/Librem5/phosh
purism@pureos:~$ uname -a
Linux pureos 5.3.0-librem5-g24b9d535b #1 SMP PREEMPT Fri Nov 29 13:19:16 PST 2019 aarch64 GNU/Linux
```
# What hardware are you running phosh on?
- Librem 5 Birchhttps://source.puri.sm/Librem5/linux/-/issues/117g_multi warning on unload2021-09-07T16:32:53ZDorota Czaplejewiczg_multi warning on unload`g_multi` gives a warning in `composite_unbind`. This might be related to other weird behaviour relating to USB interfaces, like the failure to modprobe `g_mass_storage` afterwards.
Main warning
```
purism@pureos:~$ sudo rmmod g_multi
...`g_multi` gives a warning in `composite_unbind`. This might be related to other weird behaviour relating to USB interfaces, like the failure to modprobe `g_mass_storage` afterwards.
Main warning
```
purism@pureos:~$ sudo rmmod g_multi
purism@pureos:~$ dmesg | tail -n 55
[ 119.022298] etnaviv-gpu 38000000.gpu: genpd_runtime_resume()
[ 119.271498] etnaviv-gpu 38000000.gpu: genpd_runtime_suspend()
[ 119.501821] etnaviv-gpu 38000000.gpu: genpd_runtime_resume()
[ 119.751267] etnaviv-gpu 38000000.gpu: genpd_runtime_suspend()
[ 125.021949] etnaviv-gpu 38000000.gpu: genpd_runtime_resume()
[ 125.273166] etnaviv-gpu 38000000.gpu: genpd_runtime_suspend()
[ 139.445443] etnaviv-gpu 38000000.gpu: genpd_runtime_resume()
[ 139.694193] etnaviv-gpu 38000000.gpu: genpd_runtime_suspend()
[ 143.269795] etnaviv-gpu 38000000.gpu: genpd_runtime_suspend()
[ 148.932523] etnaviv-gpu 38000000.gpu: genpd_runtime_resume()
[ 149.269298] etnaviv-gpu 38000000.gpu: genpd_runtime_suspend()
[ 154.665207] ------------[ cut here ]------------
[ 154.665307] WARNING: CPU: 1 PID: 1047 at drivers/usb/gadget/composite.c:2010 __composite_unbind+0x4c/0xe8 [libcomposite]
[ 154.665311] Modules linked in: usb_f_acm u_serial usb_f_rndis g_multi(-) usb_f_mass_storage u_ether libcomposite aes_ce_ccm rfcomm bnep redpine_sdio redpine_91x aes_ce_blk crypto_simd bluetooth mac80211 crct10dif_ce ghash_ce cfg80211 sha2_ce sha1_ce rfkill st_lsm6dsx_spi pwm_vibra snd_soc_gtm601 st_magn_spi st_sensors_spi mousedev bq25890_charger snd_soc_wm8962 st_magn_i2c vcnl4000 st_magn st_sensors_i2c st_lsm6dsx_i2c st_sensors st_lsm6dsx industrialio_triggered_buffer kfifo_buf tps6598x typec m25p80 spi_nor mtd snvs_pwrkey imx2_wdt imx_sdma virt_dma watchdog ip_tables x_tables ipv6 nf_defrag_ipv6 uas usb_storage xhci_plat_hcd xhci_hcd usbcore dwc3 ulpi udc_core usb_common phy_fsl_imx8mq_usb
[ 154.665435] CPU: 1 PID: 1047 Comm: rmmod Not tainted 5.3.0-librem5-h1 #1
[ 154.665439] Hardware name: Purism Librem 5 (DT)
[ 154.665445] pstate: 80000005 (Nzcv daif -PAN -UAO)
[ 154.665462] pc : __composite_unbind+0x4c/0xe8 [libcomposite]
[ 154.665479] lr : __composite_unbind+0x4c/0xe8 [libcomposite]
[ 154.665483] sp : ffff80007a60fd10
[ 154.665486] x29: ffff80007a60fd10 x28: ffff80007bb30dc0
[ 154.665493] x27: 0000000000000000 x26: 0000000000000000
[ 154.665500] x25: 0000000056000000 x24: 0000000000000015
[ 154.665507] x23: 0000000000000001 x22: ffff000008d4e0e0
[ 154.665514] x21: ffff8000a47913b8 x20: ffff8000a4787810
[ 154.665521] x19: ffff8000a670ee00 x18: 0000000000000000
[ 154.665528] x17: 0000000000000000 x16: 0000000000000000
[ 154.665535] x15: ffffffffffffffff x14: 5355007465676461
[ 154.665542] x13: 000000000000fb34 x12: ffff000010fb2000
[ 154.665549] x11: ffff000010e98000 x10: ffff000010fb26f0
[ 154.665555] x9 : 0000000000000000 x8 : 0000000000000004
[ 154.665562] x7 : 000000000000104a x6 : ffff8000bf95aad8
[ 154.665569] x5 : ffff8000bf95aad8 x4 : 0000000000000000
[ 154.665575] x3 : 0000000000000001 x2 : d6d2cfd9f0666900
[ 154.665582] x1 : 0000000000000000 x0 : 0000000000000024
[ 154.665588] Call trace:
[ 154.665606] __composite_unbind+0x4c/0xe8 [libcomposite]
[ 154.665621] composite_unbind+0x24/0x30 [libcomposite]
[ 154.665643] usb_gadget_remove_driver+0x40/0xa0 [udc_core]
[ 154.665659] usb_gadget_unregister_driver+0xc4/0xf8 [udc_core]
[ 154.665675] usb_composite_unregister+0x20/0x30 [libcomposite]
[ 154.665687] multi_driver_exit+0x18/0xb10 [g_multi]
[ 154.665699] __arm64_sys_delete_module+0x184/0x240
[ 154.665710] el0_svc_common.constprop.0+0x98/0x170
[ 154.665716] el0_svc_handler+0x2c/0x38
[ 154.665723] el0_svc+0x8/0xc
[ 154.665728] ---[ end trace a0aeb8ec3385f501 ]---
[ 154.668478] device: 'lun0': device_unregister
[ 154.668577] PM: Removing info for No Bus:lun0
[ 154.669024] device: 'ttyGS0': device_unregister
[ 154.669187] PM: Removing info for No Bus:ttyGS0
[ 154.671785] printk: console [ttyGS-1] disabled
[ 154.682692] PM: Removing info for No Bus:usb0
[ 155.018314] etnaviv-gpu 38000000.gpu: genpd_runtime_resume()
[ 155.268970] etnaviv-gpu 38000000.gpu: genpd_runtime_suspend()
```
Mass storage failure:
```
purism@pureos:~$ sudo modprobe g_mass_storage file=/var/lib/mass_storage_dummy stall=0
```
```
[ 458.299377] Mass Storage Function, version: 2009/09/11
[ 458.299392] LUN: removable file: (no medium)
[ 458.299439] device: 'lun0': device_add
[ 458.299487] PM: Adding info for No Bus:lun0
[ 458.299523] LUN: file: /var/lib/mass_storage_dummy
[ 458.299532] Number of LUNs=1
[ 458.299773] g_mass_storage gadget: Mass Storage Gadget, version: 2009/09/11
[ 458.299782] g_mass_storage gadget: userspace failed to provide iSerialNumber
[ 458.299790] g_mass_storage gadget: g_mass_storage ready
[ 458.302173] dwc3 38100000.usb: failed to enable ep0in
```
Nothing in lsusb, but rmmod works.https://source.puri.sm/Librem5/linux/-/issues/118Brightness slider seems linear2019-12-21T18:17:46ZDorota CzaplejewiczBrightness slider seems linearThe brightness slider's halfway setting is not that different from its full setting, and the lower part of the range makes little differences enormous.
There needs to be a mapping somewhere in the pipeline to make the slider-power relat...The brightness slider's halfway setting is not that different from its full setting, and the lower part of the range makes little differences enormous.
There needs to be a mapping somewhere in the pipeline to make the slider-power relationship closer to how humans perceive brightness.https://source.puri.sm/Librem5/linux/-/issues/119Does not notice when a modem goes away2020-09-15T15:51:43ZGuido GuntherDoes not notice when a modem goes awaywhen toggling of the kill switch the modem stays visible in `ModemManager`:
```sh
$ mmcli -L
/org/freedesktop/ModemManager1/Modem/1 [manufacturer unknown] model unknown
```
when doing a `mmcli -r -m 0` it correctly vanishes. I don't th...when toggling of the kill switch the modem stays visible in `ModemManager`:
```sh
$ mmcli -L
/org/freedesktop/ModemManager1/Modem/1 [manufacturer unknown] model unknown
```
when doing a `mmcli -r -m 0` it correctly vanishes. I don't think MM has a way to correctly notice this except for polling (and we certainly don't want it to wake up a suspended modem) so i'm not yet sure what's the best thing to do here.https://source.puri.sm/Librem5/linux/-/issues/121Need a minimal DT for linux-next2019-12-16T16:40:10ZGuido GuntherNeed a minimal DT for linux-nextA minimal DT for the Libre5 that works on mainline linux-next would be great to test upstream submissions that affect the phone only. @martin.kepplinger since you're using linux-next as well, did you look at that already? (it would also ...A minimal DT for the Libre5 that works on mainline linux-next would be great to test upstream submissions that affect the phone only. @martin.kepplinger since you're using linux-next as well, did you look at that already? (it would also be a good seed for initial mainline submission).https://source.puri.sm/Librem5/linux/-/issues/122GNSS UART Interface No Longer Working2019-12-18T09:23:27ZEric KuzmenkoGNSS UART Interface No Longer WorkingI tested using `screen` to observe the data coming from the GNSS's UART interface on the recent "linux-image-5.3.0-librem5-dirty_5.3.0-librem5-dirty-492_arm64" kernel but I got nothing. So I flashed a really old image from back in early ...I tested using `screen` to observe the data coming from the GNSS's UART interface on the recent "linux-image-5.3.0-librem5-dirty_5.3.0-librem5-dirty-492_arm64" kernel but I got nothing. So I flashed a really old image from back in early September and verified that it's not a hardware-related issue. So something along the way has broken.
Here's a snippet of what I get using the old image, the new image/kernel yield nothing (omitting personal info):
```
purism@pureos:~$ uname -a
Linux pureos 5.2.0-g46caa519a #1 SMP PREEMPT Fri Sep 6 07:11:29 PDT 2019 aarch64 GNU/Linux
purism@pureos:~$ sudo screen /dev/ttymxc1 9600
$GP,,0.0,030917,,,N*7C
...
...
...
```https://source.puri.sm/Librem5/linux/-/issues/123IMU sensor orientation on Birch board2020-03-31T12:53:27ZMartin KepplingerIMU sensor orientation on Birch boardTo me it seems like the orientation of the lsm9ds1 IMU sensor is 180 degrees (bottom up) rotated on the Birch board. @eric.kuzmenko is that so?
test:
`sudo apt install iio-sensor-proxy`
reboot
`monitor-sensor`
move the phone and com...To me it seems like the orientation of the lsm9ds1 IMU sensor is 180 degrees (bottom up) rotated on the Birch board. @eric.kuzmenko is that so?
test:
`sudo apt install iio-sensor-proxy`
reboot
`monitor-sensor`
move the phone and compare with what's printed.
haven't done that, but if so, I guess we need to describe that properly in Linux ( iio mount_matrix support ?) and/or systemd ( https://github.com/systemd/systemd/blob/master/hwdb.d/60-sensor.hwdb )https://source.puri.sm/Librem5/linux/-/issues/124Birch locks up: mmc0: Timeout waiting for hardware interrupt after xhci not r...2021-08-24T09:04:22ZMartin KepplingerBirch locks up: mmc0: Timeout waiting for hardware interrupt after xhci not responding(too often to work reliably) my Birch device locks up the following way. I see this from day 1 I got the device, on our 5.3 current kernels:
```
[ 47.081762] xhci-hcd xhci-hcd.3.auto: xHCI host controller not responding, assume dead
[...(too often to work reliably) my Birch device locks up the following way. I see this from day 1 I got the device, on our 5.3 current kernels:
```
[ 47.081762] xhci-hcd xhci-hcd.3.auto: xHCI host controller not responding, assume dead
[ 47.089734] xhci-hcd xhci-hcd.3.auto: HC died; cleaning up
[ 57.569654] mmc0: Timeout waiting for hardware interrupt.
[ 57.575062] mmc0: sdhci: ============ SDHCI REGISTER DUMP ===========
[ 57.581503] mmc0: sdhci: Sys addr: 0x00000068 | Version: 0x00000002
[ 57.587943] mmc0: sdhci: Blk size: 0x00000200 | Blk cnt: 0x00000000
[ 57.594384] mmc0: sdhci: Argument: 0x002de2c0 | Trn mode: 0x0000002b
[ 57.600824] mmc0: sdhci: Present: 0x01f88008 | Host ctl: 0x00000031
[ 57.607264] mmc0: sdhci: Power: 0x00000002 | Blk gap: 0x00000080
[ 57.613704] mmc0: sdhci: Wake-up: 0x00000008 | Clock: 0x0000000f
[ 57.620144] mmc0: sdhci: Timeout: 0x0000008f | Int stat: 0x00000003
[ 57.626584] mmc0: sdhci: Int enab: 0x117f100b | Sig enab: 0x117f100b
[ 57.633024] mmc0: sdhci: ACmd stat: 0x00000000 | Slot int: 0x00008402
[ 57.639464] mmc0: sdhci: Caps: 0x07eb0000 | Caps_1: 0x8000b407
[ 57.645904] mmc0: sdhci: Cmd: 0x0000193a | Max curr: 0x00ffffff
[ 57.652344] mmc0: sdhci: Resp[0]: 0x00000900 | Resp[1]: 0xffffffff
[ 57.658783] mmc0: sdhci: Resp[2]: 0x328f5903 | Resp[3]: 0x00000900
[ 57.665223] mmc0: sdhci: Host ctl2: 0x00000088
[ 57.669667] mmc0: sdhci: ADMA Err: 0x00000000 | ADMA Ptr: 0xfec45268
[ 57.676106] mmc0: sdhci: ============================================
[ 68.577644] rcu: INFO: rcu_preempt detected stalls on CPUs/tasks:
[ 68.583743] rcu: 0-...!: (14 GPs behind) idle=754/0/0x0 softirq=12186/12186 fqs=0
[ 68.591401] rcu: 1-...!: (12 GPs behind) idle=d14/0/0x0 softirq=11271/11272 fqs=0
[ 68.599058] rcu: 2-...!: (18 GPs behind) idle=8e0/0/0x0 softirq=10355/10355 fqs=0
[ 68.606800] rcu: rcu_preempt kthread starved for 5252 jiffies! g11953 f0x0 RCU_GP_WAIT_FQS(5) ->state=0x0 ->cpu=3
[ 68.617058] rcu: RCU grace-period kthread stack dump:
```
It doesn't happen in every session, and it also happens that I see the "mmc0 timeout" only, during startup already, which then does not fully hang the system. A bit confusing, I know.
Who else sees these lock-ups?
Sidenote: I've had the same mmc timeouts on mmc1 too, which I solved by removing and properly re-inserting the wifi card.https://source.puri.sm/Librem5/linux/-/issues/125Screen blank, screen resume, first click shows clock drop-down menu2020-08-27T06:57:09ZTodd WeaverScreen blank, screen resume, first click shows clock drop-down menu# What problem did you encounter
Clock drop-down menu appears after first click upon screen resume
## What is the current behaviour?
First tap/touch/click after screen resume (from blank) shows the clock.
## What is the expected beha...# What problem did you encounter
Clock drop-down menu appears after first click upon screen resume
## What is the current behaviour?
First tap/touch/click after screen resume (from blank) shows the clock.
## What is the expected behaviour?
First tap is accepted for what it is.
## How to reproduce
1. Blank screen
2. Resume screen
3. Tap anywhere
4. See clock menu
![librem-5-birch-clock-menu-2019-12-07](/uploads/efeed0859efce628c852af9699206787/librem-5-birch-clock-menu-2019-12-07.webm)
# Which version did you encounter the bug in?
- [ ] I Compiled it myself. If you compiled phosh from source please provide the
git revision via e.g. by running ``git log -1 --pretty=oneline`` and pasting
the output below.
- [x] I used the precompiled Debian package (e.g. by running a prebuilt
image). Please paste the output oof ``dpkg -s phosh`` below.
```
purism@pureos:~$ dpkg -s phosh
Package: phosh
Status: install ok installed
Priority: optional
Section: x11
Installed-Size: 804
Maintainer: Guido Günther <agx@sigxcpu.org>
Architecture: arm64
Version: 0.1.4
Provides: notification-daemon, polkit-1-auth-agent
Depends: dconf-gsettings-backend | gsettings-backend, libc6 (>= 2.17), libcairo2 (>= 1.2.4), libgcr-base-3-1 (>= 3.8.0), libgcr-ui-3-1 (>= 3.8.0), libgdk-pixbuf2.0-0 (>= 2.22.0), libglib2.0-0 (>= 2.53.2), libgnome-desktop-3-17 (>= 3.17.92), libgtk-3-0 (>= 3.21.5), libhandy-0.0-0 (>= 0.0.11), libnm0 (>= 1.0.0), libpam0g (>= 0.99.7.1), libpango-1.0-0 (>= 1.22.0), libpangocairo-1.0-0 (>= 1.14.0), libpolkit-agent-1-0 (>= 0.99), libpolkit-gobject-1-0 (>= 0.94), libpulse-mainloop-glib0 (>= 0.99.1), libpulse0 (>= 0.99.1), libsecret-1-0 (>= 0.7), libupower-glib3 (>= 0.99.4-3~), libwayland-client0 (>= 1.9.91), fonts-lato
Recommends: gnome-session, phoc
Description: Pure Wayland shell for mobile devices
Phosh is a simple shell for Wayland compositors speaking the layer-surface
protocol. It currently supports
.
* a lockscreen
* brightness control and nighlight
* the gcr system-prompter interface
* acting as a polkit auth agent
* enough of org.gnome.Mutter.DisplayConfig to make gnome-settings-daemon happy
* a homebutton that toggles a simple favorites menu
* status icons for battery, wwan and wifi
.
If you're not working on a Wayland compositor then this package is likely not
very useful for you.
Homepage: https://source.puri.sm/Librem5/phosh
purism@pureos:~$
```
# What hardware are you running phosh on?
- [ ] amd64 qemu image
- [x] Librem 5 Birch
- [ ] nested compositor. If so please give the full command you start phosh
with.
- [ ] other (please elaborte)
```
purism@pureos:~$ uname -a
Linux pureos 5.3.0-librem5-g24b9d535b #1 SMP PREEMPT Fri Nov 29 13:19:16 PST 2019 aarch64 GNU/Linux
purism@pureos:~$
```https://source.puri.sm/Librem5/linux/-/issues/126librem5: fully turn off backlight2019-12-19T14:05:24ZGuido Guntherlibrem5: fully turn off backlightthe backlight showed a light glim even when brightness set to zero on the phone. what worked on the devkit fails on the phone due to missing code to shut down the regulator. patch forthcoming.the backlight showed a light glim even when brightness set to zero on the phone. what worked on the devkit fails on the phone due to missing code to shut down the regulator. patch forthcoming.https://source.puri.sm/Librem5/linux/-/issues/127resume Birch2019-12-20T09:50:03ZMartin Kepplingerresume Birchhttps://source.puri.sm/Librem5/use-cases/issues/75
This is about testing on linux-next after 5.5-rc2 (ongoing); and with *mainline* ATF in u-boot.
unlike on the devkit, on Birch the system won't resume (the console should do it, but i'...https://source.puri.sm/Librem5/use-cases/issues/75
This is about testing on linux-next after 5.5-rc2 (ongoing); and with *mainline* ATF in u-boot.
unlike on the devkit, on Birch the system won't resume (the console should do it, but i've set the volume buttons to wakeup-sources just in case)
```
[ 63.173700] Disabling non-boot CPUs ...
[ 63.178945] device: 'index0': device_unregister
[ 63.183857] device: 'index1': device_unregister
[ 63.188775] device: 'index2': device_unregister
[ 63.193771] device: 'cache': device_unregister
[ 63.200449] CPU1: shutdown
[ 63.203373] psci: CPU1 killed (polled 0 ms)
[ 63.217185] device: 'index0': device_unregister
[ 63.222041] device: 'index1': device_unregister
[ 63.226868] device: 'index2': device_unregister
[ 63.231697] device: 'cache': device_unregister
[ 63.238389] CPU2: shutdown
[ 63.241166] psci: CPU2 killed (polled 0 ms)
[ 63.255455] device: 'index0': device_unregister
[ 63.260326] device: 'index1': device_unregister
[ 63.265287] device: 'index2': device_unregister
[ 63.270156] device: 'cache': device_unregister
[ 63.277005] CPU3: shutdown
[ 63.280012] psci: CPU3 killed (polled 0 ms)
[ 63.296854] Checking wakeup interrupts
```https://source.puri.sm/Librem5/linux/-/issues/128tps6598x_interrupt: failed to read events and interrupt storm2020-01-14T11:32:07ZDorota Czaplejewicztps6598x_interrupt: failed to read events and interrupt stormNot sure exactly what I did, but:
- killed gsd-power
- killed it again
- unlocked the screen
- possibly pressed the power button
- left the phone for a few minutes
- noticed blank screen with backlight on and no power button reaction
- ...Not sure exactly what I did, but:
- killed gsd-power
- killed it again
- unlocked the screen
- possibly pressed the power button
- left the phone for a few minutes
- noticed blank screen with backlight on and no power button reaction
- restarted phosh
As a result, a lot of:
> Dec 24 13:31:43 pureos kernel: tps6598x 0-003f: tps6598x_interrupt: failed to read events
and irq/58-0-003f topping the CPU.