linux issueshttps://source.puri.sm/Librem5/linux/-/issues2021-08-19T01:11:40Zhttps://source.puri.sm/Librem5/linux/-/issues/144spi nor flash (/dev/mtd0) not acessible2021-08-19T01:11:40ZGuido Guntherspi nor flash (/dev/mtd0) not acessiblethis happens during boot on birch:
```
[ 14.792318] m25p80 spi0.0: no pinctrl handle
[ 14.795613] m25p80 spi0.0: unrecognized JEDEC id bytes: ff ff ff ff ff ff
[ 14.802913] m25p80: probe of spi0.0 failed with error -2
```
so ther...this happens during boot on birch:
```
[ 14.792318] m25p80 spi0.0: no pinctrl handle
[ 14.795613] m25p80 spi0.0: unrecognized JEDEC id bytes: ff ff ff ff ff ff
[ 14.802913] m25p80: probe of spi0.0 failed with error -2
```
so there driver does not probe correctly and there's no `/dev/mtd0` at all.https://source.puri.sm/Librem5/linux/-/issues/143Redpine module needs power cycle after boot on Chestnut2023-10-03T16:17:47ZAngus Ainslieangus.ainslie@puri.smRedpine module needs power cycle after boot on ChestnutThe Wifi card is not automatically detected on chestnut flipping the HKS for Wifi gets the modules to probe correctly.The Wifi card is not automatically detected on chestnut flipping the HKS for Wifi gets the modules to probe correctly.Angus Ainslieangus.ainslie@puri.smAngus Ainslieangus.ainslie@puri.smhttps://source.puri.sm/Librem5/linux/-/issues/142dcss: display port support2023-10-03T16:17:47ZGuido Guntherdcss: display port supportneeded since the phone does dp over usb-cneeded since the phone does dp over usb-chttps://source.puri.sm/Librem5/linux/-/issues/141dcss: forward hdmi to 5.x2020-03-17T13:59:20ZGuido Guntherdcss: forward hdmi to 5.xwe left that behind in 4.18 and only moved the dsi part forward. gettings this to work on the devkit (while using mxsfb for dsi) would be a first step towards dual screen mode and future phone usage via usb-c.we left that behind in 4.18 and only moved the dsi part forward. gettings this to work on the devkit (while using mxsfb for dsi) would be a first step towards dual screen mode and future phone usage via usb-c.https://source.puri.sm/Librem5/linux/-/issues/140tps6598x: dp alt mode2020-09-06T10:43:39ZGuido Gunthertps6598x: dp alt modeIndependent on what we provide via imx8mq/dcss atm we want to enable this once a monitor is plugged in.
I'll look at that.Independent on what we provide via imx8mq/dcss atm we want to enable this once a monitor is plugged in.
I'll look at that.https://source.puri.sm/Librem5/linux/-/issues/139move to linux 5.5 / 5.62020-07-20T17:25:59ZGuido Gunthermove to linux 5.5 / 5.6We're accumulating more and more patches that already went upsteam. For further devfreq work it would be good to move to 5.5. or 5.6. Since 5.5 is in rc already syncing up with linux-next to aim in for 5.6 is likely more useful.We're accumulating more and more patches that already went upsteam. For further devfreq work it would be good to move to 5.5. or 5.6. Since 5.5 is in rc already syncing up with linux-next to aim in for 5.6 is likely more useful.https://source.puri.sm/Librem5/linux/-/issues/138bq25890: Don't provide capacity information when a fuel gauge is present2021-11-13T01:37:02ZGuido Guntherbq25890: Don't provide capacity information when a fuel gauge is presentWe added `POWER_SUPPLY_PROP_CAPACITY` for the devkit but we should only do this if we have a battery wired up since this otherwise confuses upower.
Already known but let's have a bug for it.We added `POWER_SUPPLY_PROP_CAPACITY` for the devkit but we should only do this if we have a battery wired up since this otherwise confuses upower.
Already known but let's have a bug for it.https://source.puri.sm/Librem5/linux/-/issues/137Enable BPF/cgroup based firewalling2020-11-12T15:46:40ZSebastian KrzyszkowiakEnable BPF/cgroup based firewallingsystemd complains:
```
Jan 05 03:38:40 pureos systemd[1]: File /lib/systemd/system/systemd-journald.service:12 configures an IP firewall (IPAddressDeny=any), but the local system does not support BPF/cgroup based firewalling.
Jan 05 03:...systemd complains:
```
Jan 05 03:38:40 pureos systemd[1]: File /lib/systemd/system/systemd-journald.service:12 configures an IP firewall (IPAddressDeny=any), but the local system does not support BPF/cgroup based firewalling.
Jan 05 03:38:40 pureos systemd[1]: Proceeding WITHOUT firewalling in effect! (This warning is only shown for the first loaded unit using IP firewalling.)
```https://source.puri.sm/Librem5/linux/-/issues/136Touch points getting stuck2022-04-19T07:26:16ZSebastian KrzyszkowiakTouch points getting stuckSometimes the kernel doesn't notice that the finger has been released from the touchscreen, resulting in a stuck touch point.
libinput debug-events:
```
# finger placed on screen
event1 TOUCH_DOWN +7.32s 0 (0) 38.33/46.74...Sometimes the kernel doesn't notice that the finger has been released from the touchscreen, resulting in a stuck touch point.
libinput debug-events:
```
# finger placed on screen
event1 TOUCH_DOWN +7.32s 0 (0) 38.33/46.74 (276.00/673.00mm)
event1 TOUCH_FRAME +7.32s
# finger released
#
# finger placed again
event1 TOUCH_MOTION +16.99s 0 (0) 81.11/62.99 (584.00/907.00mm)
event1 TOUCH_FRAME +16.99s
# finger released
event1 TOUCH_UP +17.05s
event1 TOUCH_FRAME +17.05s
```
evtest:
```
# finger placed on screen
Event: time 1578191602.590064, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 412
Event: time 1578191602.590064, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 463
Event: time 1578191602.590064, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 670
Event: time 1578191602.590064, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 1
Event: time 1578191602.590064, type 3 (EV_ABS), code 0 (ABS_X), value 463
Event: time 1578191602.590064, type 3 (EV_ABS), code 1 (ABS_Y), value 670
Event: time 1578191602.590064, -------------- SYN_REPORT ------------
# finger released
#
# finger placed again
Event: time 1578191614.366974, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 139
Event: time 1578191614.366974, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 861
Event: time 1578191614.366974, type 3 (EV_ABS), code 0 (ABS_X), value 139
Event: time 1578191614.366974, type 3 (EV_ABS), code 1 (ABS_Y), value 861
Event: time 1578191614.366974, -------------- SYN_REPORT ------------
# finger released
Event: time 1578191614.392739, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value -1
Event: time 1578191614.392739, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 0
Event: time 1578191614.392739, -------------- SYN_REPORT ------------
```
This is Birch - I never noticed such behavior on the devkit.https://source.puri.sm/Librem5/linux/-/issues/135BQ25895: Disable BC1.2 and Set IINLIM to Max Value2022-12-14T20:14:17ZEric KuzmenkoBQ25895: Disable BC1.2 and Set IINLIM to Max ValueThe following should be done:
* Set the lower four bits of 0x02 to zero (HVDCP_EN, MAXC_EN, FORCE_DPDM, and AUTO_DPDM_EN)
* After setting the lower four bits of 0x02 to zero then set FORCE_ICO to 1, MSB of 0x09 (must happen after settin...The following should be done:
* Set the lower four bits of 0x02 to zero (HVDCP_EN, MAXC_EN, FORCE_DPDM, and AUTO_DPDM_EN)
* After setting the lower four bits of 0x02 to zero then set FORCE_ICO to 1, MSB of 0x09 (must happen after setting lower four bits of 0x02 to zero and not before it)
* Set IINLIM\[5:0\]=111111 (3.25A), lower 6 bits of register 0x00 to all 1
It may be necessary to set FORCE_ICO to 1 each time a USB source is plugged in (if ICO_OPTIMIZED is still zero).https://source.puri.sm/Librem5/linux/-/issues/134tps6598x irq drains battery2020-03-04T14:24:16ZGuido Gunthertps6598x irq drains batterytop has
```
410 root -51 0 0 0 0 D 15,4 0,0 11:47.41 irq/58-0-003f
```
after 1.5h of operation. According to `/proc/interrupts`:
```
58: 86144 0 0 0 gpio-mxc 10 Level 0-0...top has
```
410 root -51 0 0 0 0 D 15,4 0,0 11:47.41 irq/58-0-003f
```
after 1.5h of operation. According to `/proc/interrupts`:
```
58: 86144 0 0 0 gpio-mxc 10 Level 0-003f
```
which is the `ti,tps6598x`. Also already known but i did no find a bug either.https://source.puri.sm/Librem5/linux/-/issues/133touch controller irq storm drains battery when screen is blanked2024-02-18T11:25:15ZGuido Gunthertouch controller irq storm drains battery when screen is blankedlong known but i've not found a bug:
```
[ 4491.190334] edt_ft5x06 2-0038: Unable to fetch data, error: -6
[ 4496.132554] edt_ft5x06_ts_isr: 15686 callbacks suppressed
```
only happens when screen is blanked due to the way lcd and touc...long known but i've not found a bug:
```
[ 4491.190334] edt_ft5x06 2-0038: Unable to fetch data, error: -6
[ 4496.132554] edt_ft5x06_ts_isr: 15686 callbacks suppressed
```
only happens when screen is blanked due to the way lcd and touch are wired up. i'll fix that.https://source.puri.sm/Librem5/linux/-/issues/132Second microphone near earpiece mute while on active call2022-12-28T18:19:50ZTodd WeaverSecond microphone near earpiece mute while on active callThere are instances where the earpiece is not sealed against the ear while on a call (due to proximity sensor not yet enabled, or not blanking the screen, and holding the head a small bit away from the earpiece), and the second microphon...There are instances where the earpiece is not sealed against the ear while on a call (due to proximity sensor not yet enabled, or not blanking the screen, and holding the head a small bit away from the earpiece), and the second microphone (top microphone) may feedback echo.https://source.puri.sm/Librem5/linux/-/issues/131No microphone input2020-01-07T11:17:26ZBob HamNo microphone inputI originally had no call audio sent to the network on my birch device and after investigating, it looks like there's no audio going to the codec's ALSA capture interface. This is what a recording looks like and it's the same wave every ...I originally had no call audio sent to the network on my birch device and after investigating, it looks like there's no audio going to the codec's ALSA capture interface. This is what a recording looks like and it's the same wave every time:
![recording](/uploads/14b5ee34756edf354be73db053e16b4d/recording.png)
The recording was made by:
1. Stopping and masking the `pulseaudio.socket` and `pulseaudio.service` systemd user units.
2. Setting the ALSA UCM verb and device like so:
```
alsaucm -n -b - <<EOF
open wm8962
set _verb Audio
set _enadev Handset
EOF
```
3. Recording from the ALSA device using
```
arecord -D hw:CARD=wm8962,DEV=0 -c 2 -f S16_LE -r 48000 t.wav
```
I've checked each of the relevant codec registers in the signal path while recording and I can find no reason that the microphone input isn't going through. Everything looks in order (note that the .dts sets the SAI2 clock, that is, the codec's MCLK pin, to 24576000 Hz):
| Register | Value (base 2) | Relevant bit(s) | Value
| ------ | ------ | ------ | ------ |
| R514 (0202h) GPIO 3 | 10011 | 4:0 GP3_FN [4:0] | 1_0011 = Digital Microphone Output Clock |
| R516 (0204h) GPIO 5 | 1000000000010100 | 4:0 GP5_FN [4:0] | 1_0100 = Digital Microphone Input Data |
| R25 (19h) Pwr Mgmt (1) | 10011111100 | 10 DMIC_ENA | 1 = Audio DSP input is from digital microphone interface |
| | | 3 ADCL_ENA - Left ADC Enable | 1 = Enabled |
| | | 2 ADCR_ENA - Right ADC Enable | 1 = Enabled |
| R21 (15h) Left ADC Volume | 11001000 | 7:0 ADCL_VOL [7:0] - Left ADC Digital Volume | C8 (Volume 3.000 dB) |
| R22 (16h) Right ADC Volume | 11001000 | 7:0 ADCR_VOL [7:0] - Right ADC Digital Volume | C8 (Volume 3.000 dB) |
| R5 (05h) ADC & DAC Control 1 | 11000 | 0 ADC_HPF_DIS - ADC High-Pass Filter Disable | 0 = Enable |
| R6 (06h) ADC & DAC Control 2 | 10000000001000 | 10 ADC_HPF_MODE - ADC High-Pass Filter Mode select | 0 = Hi-Fi mode (1st order) Note: ‘Hi-Fi Mode’ refers to the mode when ADC_HPF_MODE = 0 (first order filtering and a cut-off frequency of 3.5Hz at a sample rate of 44.1kHz);|
| R264 (0108h) LHPF1 | 0 | 0 LHPF_ENA - Low/High-Pass Filter mode select | 0 = Disable |
| R268 (010Ch) THREED1 | 0 | 0 THREED_ENA - 3D Surround Sound enable | 0 = Disabled |
| R256 (0100h) DF1 | 0 | 0 DF1_ENA - DF1 Enable in ADC path | 0 = Disabled |
| R16389 (4005h) SOUNDSTAGE_ENABLES_0 | 0 | 5 RTN_ADC_ENA - ADC ReTune enable | 0 = disabled |
| R276 (0114h) DRC 1 | 1100 | 0 DRC_ENA - DRC Enable | 0 = Disabled |
| R7 (07h) Audio Interface 0 | 1100010 | 8 ADC_LRSWAP - Swap left/right ADC data on the interface | 0 = Normal |
| R5 (05h) ADC & DAC Control 1 | 11000 | 6 ADCR_DAT_INV - Right ADC Invert | 0 = Right ADC output not inverted |
| | | 5 ADCL_DAT_INV - Left ADC Invert | 0 = Left ADC output not inverted |
| R285 (011Dh) Tloopback | 0 | 1 TLB_ENA - T-Loopback Enable | 0 = Disabled |
| R7 (07h) Audio Interface 0 | 1100010 | 10 AIFADC_TDM_MODE - ADC TDM Mode Select | 0 = Normal ADCDAT operation (1 stereo slot) |
| | | 8 ADC_LRSWAP - Swap left/right ADC data on the interface | 0 = Normal |
| | | 7 BCLK_INV - BCLK Invert | 0 = BCLK not inverted |
| | | 6 MSTR - Audio Interface Mode Select | 1 = Master mode |
| | | 4 LRCLK_INV - Right, left and I2S modes - LRCLK polarity | 0 = normal LRCLK polarity |
| | | 3:2 WL [1:0] - Digital Audio Interface Word Length | 00 = 16 bits |
| | | 1:0 FMT [1:0] - Digital Audio Interface Format| 10 = I2S Format |
| R9 (09h) Audio Interface 1 | 1100000000 | 2 ADC_COMP - ADC Companding Enable | 0 = disabled |
| R8 (08h) Clocking2 | 100111101010 | 11 CLKREG_OVD - Clock Configuration Override | 1 = Clocking registers are controlled as normal via Control Interface |
| | | 10:9 MCLK_SRC - MCLK source select | 00 = MCLK pin |
| | | 5 SYSCLK_ENA - SYSCLK enable | 1 = Enabled |
| | | 3:0 BCLK_DIV - BCLK Rate | 1010 = DSPCLK / 16 |
| R4 (04h) Clocking1 | 100010 | 10:9 DSPCLK_DIV [1:0] - DSP Clock Divider | 00 = MCLK |
| | | 8:6 ADCSYS_CLK_DIV [2:0] - ADC Sample Rate Divider | 000 = SYSCLK |
| | | 2:1 SYSCLK_DIV - SYSCLK Divider | 01 = MCLK / 2 |
| R56 (38h) Clocking 4 | 10100100001010 | 4:1 MCLK_RATE [3:0] - Selects the MCLK / fs ratio | 0101 = 512 |
| R27 (1Bh) Additional Control (3) | 10000 | 2:0 SAMPLE_RATE [2:0] - Selects the Sample Rate (fs) | 000 = 44.1kHz, 48kHz |
| | | 4 SAMPLE_RATE_INT_MODE - Selects the Integer or Fractional value of the SAMPLE_RATE register | 1 = 8k, 12k, 16k, 24k, 32k, 48k or 96kHz |
| R14 (0Eh) Audio Interface 2 | 100000 | 10:0 AIF_RATE [10:0] - LRCLK Rate = BCLK / AIF_RATE; Integer (LSB = 1) | 32 BCLKs per LRCLK |
| R23 (17h) Additional Control (1) | 101100001 | 5 ADC_HP - ADC Oversampling Ratio | 1 = High Performance (typically 128 x fs) |
Given that some users have reported working microphone input during calls, I'm tempted to suspect that this is a hardware issue.
The kernel package is `linux-image-5.3.0-librem5-h1 5.3.0+librem5.6`https://source.puri.sm/Librem5/linux/-/issues/130Touchscreen misses events and driver spews error messages2020-01-01T12:49:45ZBob HamTouchscreen misses events and driver spews error messagesSometimes I find the touchscreen misses presses and so forth. Often I find this in the kernel log:
```
[15237.097411] edt_ft5x06_ts_isr: 9192 callbacks suppressed
[15237.097436] edt_ft5x06 2-0038: Unable to fetch data, error: -6
[15237...Sometimes I find the touchscreen misses presses and so forth. Often I find this in the kernel log:
```
[15237.097411] edt_ft5x06_ts_isr: 9192 callbacks suppressed
[15237.097436] edt_ft5x06 2-0038: Unable to fetch data, error: -6
[15237.103615] edt_ft5x06 2-0038: Unable to fetch data, error: -6
[15237.109756] edt_ft5x06 2-0038: Unable to fetch data, error: -6
[15237.115955] edt_ft5x06 2-0038: Unable to fetch data, error: -6
[15237.122111] edt_ft5x06 2-0038: Unable to fetch data, error: -6
[15237.128270] edt_ft5x06 2-0038: Unable to fetch data, error: -6
[15237.134401] edt_ft5x06 2-0038: Unable to fetch data, error: -6
[15237.140555] edt_ft5x06 2-0038: Unable to fetch data, error: -6
[15237.146672] edt_ft5x06 2-0038: Unable to fetch data, error: -6
[15237.152799] edt_ft5x06 2-0038: Unable to fetch data, error: -6
[15242.101175] edt_ft5x06_ts_isr: 9403 callbacks suppressed
[15242.101209] edt_ft5x06 2-0038: Unable to fetch data, error: -6
[15242.107561] edt_ft5x06 2-0038: Unable to fetch data, error: -6
[15242.113822] edt_ft5x06 2-0038: Unable to fetch data, error: -6
[15242.120240] edt_ft5x06 2-0038: Unable to fetch data, error: -6
[15242.126487] edt_ft5x06 2-0038: Unable to fetch data, error: -6
[15242.132768] edt_ft5x06 2-0038: Unable to fetch data, error: -6
[15242.139005] edt_ft5x06 2-0038: Unable to fetch data, error: -6
[15242.145263] edt_ft5x06 2-0038: Unable to fetch data, error: -6
[15242.151505] edt_ft5x06 2-0038: Unable to fetch data, error: -6
[15242.157771] edt_ft5x06 2-0038: Unable to fetch data, error: -6
[15247.105071] edt_ft5x06_ts_isr: 9835 callbacks suppressed
[15247.105098] edt_ft5x06 2-0038: Unable to fetch data, error: -6
[15247.111875] edt_ft5x06 2-0038: Unable to fetch data, error: -6
[15247.118024] edt_ft5x06 2-0038: Unable to fetch data, error: -6
[15247.124184] edt_ft5x06 2-0038: Unable to fetch data, error: -6
[15247.130325] edt_ft5x06 2-0038: Unable to fetch data, error: -6
[15247.136481] edt_ft5x06 2-0038: Unable to fetch data, error: -6
[15247.142611] edt_ft5x06 2-0038: Unable to fetch data, error: -6
[15247.148737] edt_ft5x06 2-0038: Unable to fetch data, error: -6
[15247.154852] edt_ft5x06 2-0038: Unable to fetch data, error: -6
[15247.161008] edt_ft5x06 2-0038: Unable to fetch data, error: -6
[15252.109562] edt_ft5x06_ts_isr: 9540 callbacks suppressed
[15252.109588] edt_ft5x06 2-0038: Unable to fetch data, error: -6
[15252.115805] edt_ft5x06 2-0038: Unable to fetch data, error: -6
[15252.121967] edt_ft5x06 2-0038: Unable to fetch data, error: -6
[15252.128124] edt_ft5x06 2-0038: Unable to fetch data, error: -6
[15252.134279] edt_ft5x06 2-0038: Unable to fetch data, error: -6
[15252.140428] edt_ft5x06 2-0038: Unable to fetch data, error: -6
[15252.146560] edt_ft5x06 2-0038: Unable to fetch data, error: -6
[15252.152713] edt_ft5x06 2-0038: Unable to fetch data, error: -6
[15252.158822] edt_ft5x06 2-0038: Unable to fetch data, error: -6
[15252.164977] edt_ft5x06 2-0038: Unable to fetch data, error: -6
```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.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/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/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/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.