linux-emcraft issueshttps://source.puri.sm/Librem5/linux-emcraft/-/issues2019-12-06T14:36:14Zhttps://source.puri.sm/Librem5/linux-emcraft/-/issues/41Using my devkit powered through a j5 Create JCA374 results in resets2019-12-06T14:36:14ZBob HamUsing my devkit powered through a j5 Create JCA374 results in resetsI have the supplied wall wart connected directly to the Power In port on the JCA374 with the supplied USB cable and then the JCA374 plugged directly into the devkit's USB port. The devkit resets at random, usually during boot and thus e...I have the supplied wall wart connected directly to the Power In port on the JCA374 with the supplied USB cable and then the JCA374 plugged directly into the devkit's USB port. The devkit resets at random, usually during boot and thus entering into boot loops but also after having successfully booted.https://source.puri.sm/Librem5/linux-emcraft/-/issues/36Underruns happen playing audio through the SGTL50002019-04-17T12:57:56ZBob HamUnderruns happen playing audio through the SGTL5000Playing audio files through the SGTL5000 results in buffer xruns and consequent audio dropouts. Having investigated this, the xruns are definitely not a DMA issue and are underruns caused by the absence of incoming ioctl()s from userspa...Playing audio files through the SGTL5000 results in buffer xruns and consequent audio dropouts. Having investigated this, the xruns are definitely not a DMA issue and are underruns caused by the absence of incoming ioctl()s from userspace to transfer the audio data. The underruns occur playing audio files from a tmpfs filesystem so hardware storage I/O is not the culprit. There is no regular pattern to the timing of the underruns; there may be many underruns in succession or it may be difficult to see any underrun at all. Rebooting the board seems to disrupt the pattern of underruns.
I've conducted the same tests on the Nitrogen i.MX 6 board which also has an SGTL5000 and found no underruns or any other problems.
I suspect this may be related to the periodic general peaks in latency highlighted by linux-emcraft#33.https://source.puri.sm/Librem5/linux-emcraft/-/issues/35Sometimes adjusting the Lineout control in alsamixer results in all mixer ope...2019-03-07T16:39:07ZBob HamSometimes adjusting the Lineout control in alsamixer results in all mixer operations returning "Resource temporarily unavailable"The Lineout control will firstly go to zero, then trying to run alsamixer again will always result in "Resource temporarily unavailable"The Lineout control will firstly go to zero, then trying to run alsamixer again will always result in "Resource temporarily unavailable"https://source.puri.sm/Librem5/linux-emcraft/-/issues/34aplay sometimes errors out with "write error: Input/output error"2019-03-07T16:39:17ZBob Hamaplay sometimes errors out with "write error: Input/output error"Sometimes while playing an audio file through the SGTL5000, the sound stops and after a significant pause, aplay reports:
```
aplay: pcm_write:2053: write error: Input/output error
```Sometimes while playing an audio file through the SGTL5000, the sound stops and after a significant pause, aplay reports:
```
aplay: pcm_write:2053: write error: Input/output error
```https://source.puri.sm/Librem5/linux-emcraft/-/issues/33Serial output periodically slows to a crawl2019-03-11T11:47:24ZBob HamSerial output periodically slows to a crawlThis video of the output of "dmesg" from a serial console shows the serial output periodically slowing to a crawl:
![laggy-serial](/uploads/b5eb8e521db11f82405ff9f07e0c836f/laggy-serial.webm)
This may be a similar symptom to wider issu...This video of the output of "dmesg" from a serial console shows the serial output periodically slowing to a crawl:
![laggy-serial](/uploads/b5eb8e521db11f82405ff9f07e0c836f/laggy-serial.webm)
This may be a similar symptom to wider issues of general lack of responsiveness.https://source.puri.sm/Librem5/linux-emcraft/-/issues/20System unresponsive if Using HDMI But No Monitor Present2019-01-09T12:34:36ZEric KuzmenkoSystem unresponsive if Using HDMI But No Monitor PresentAt least on the test image shipped with the dev kits by default, the touch controller input is not very responsive if you are using the HDMI device tree but no monitor is connected to the mini-HDMI receptacle.At least on the test image shipped with the dev kits by default, the touch controller input is not very responsive if you are using the HDMI device tree but no monitor is connected to the mini-HDMI receptacle.https://source.puri.sm/Librem5/linux-emcraft/-/issues/19Pulseaudio fails to open SGTL5000 codec in stereo mode resulting in no audio ...2019-01-18T20:10:59ZBob HamPulseaudio fails to open SGTL5000 codec in stereo mode resulting in no audio from speakerPulseAudio fails to open the sgtl5000 card in stereo mode. On the devkit, the speaker is attached to the right line out channel rather than the left (/mono) channel and so there is no sound from PulseAudio.
```
Jan 07 16:04:32 pureos p...PulseAudio fails to open the sgtl5000 card in stereo mode. On the devkit, the speaker is attached to the right line out channel rather than the left (/mono) channel and so there is no sound from PulseAudio.
```
Jan 07 16:04:32 pureos pulseaudio[2443]: D: [pulseaudio] alsa-mixer.c: Looking at profile output:analog-stereo
Jan 07 16:04:32 pureos pulseaudio[2443]: D: [pulseaudio] alsa-mixer.c: Checking for playback on Analog Stereo (analog-stereo)
Jan 07 16:04:32 pureos pulseaudio[2443]: D: [pulseaudio] alsa-util.c: Trying front:0 with SND_PCM_NO_AUTO_FORMAT ...
Jan 07 16:04:32 pureos pulseaudio[2443]: I: [pulseaudio] (alsa-lib)conf.c: Unknown parameters 0
Jan 07 16:04:32 pureos pulseaudio[2443]: I: [pulseaudio] (alsa-lib)pcm.c: Unknown PCM front:0
Jan 07 16:04:32 pureos pulseaudio[2443]: I: [pulseaudio] alsa-util.c: Error opening PCM device front:0: Invalid argument
```
There is no "front" PCM device for the sgtl5000 which is what PulseAudio is trying to open:
```
purism@pureos:~$ aplay -L
null
Discard all samples (playback) or generate zero samples (capture)
jack
JACK Audio Connection Kit
pulse
PulseAudio Sound Server
default:CARD=sgtl5000
sgtl5000,
Default Audio Device
sysdefault:CARD=sgtl5000
sgtl5000,
Default Audio Device
dmix:CARD=sgtl5000,DEV=0
sgtl5000,
Direct sample mixing device
dsnoop:CARD=sgtl5000,DEV=0
sgtl5000,
Direct sample snooping device
hw:CARD=sgtl5000,DEV=0
sgtl5000,
Direct hardware device without any conversions
plughw:CARD=sgtl5000,DEV=0
sgtl5000,
Hardware device with all software conversions
usbstream:CARD=sgtl5000
sgtl5000
USB Stream Output
purism@pureos:~$
```
As I understand it, the "front" device is a standard PCM virtual device created by the default alsalib configuration, in `/usr/share/alsa/alsa.conf` and `/usr/share/alsa/pcm/`. I'm not sure yet why it's failing to create the "front" device for the sgtl5000 but presumably there will be something "standard" that's missing from the sgtl5000's driver.https://source.puri.sm/Librem5/linux-emcraft/-/issues/18SD card not always detected2019-01-15T17:11:28ZGhost UserSD card not always detectedThe SD card (sda) seems to only be present when loading u-boot from eMMC and booting from the eMMC stock image. The following scenarios have strange results:
```
u-boot on eMMC -> Linux over fastboot -> eMMC rootfs: system boots, sda av...The SD card (sda) seems to only be present when loading u-boot from eMMC and booting from the eMMC stock image. The following scenarios have strange results:
```
u-boot on eMMC -> Linux over fastboot -> eMMC rootfs: system boots, sda available
u-boot on eMMC -> Linux over fastboot -> SD rootfs: kernel hangs waiting for sda
u-boot on USB -> Linux over fastboot -> eMMC rootfs: system boots, sda unavailable
u-boot on USB -> Linux over fastboot -> SD rootfs: kernel hangs waiting for sda
```
- 'u-boot on eMMC' means I'm booting from eMMC, interrupted u-boot when booting and ran 'fastboot 0'
- 'u-boot on USB' means I loaded u-boot using uuu
- 'Linux over fastboot' means I loaded the kernel and device tree using uuu
- 'eMMC rootfs' means I set 'root=/dev/mmcblkp2' in bootargs
- 'SD rootfs' means I set 'root=/dev/sda' in bootargshttps://source.puri.sm/Librem5/linux-emcraft/-/issues/15USB 3 errors and consistent issues2019-03-08T19:09:02ZBob HamUSB 3 errors and consistent issuesConnecting a hub to the USB 3 port in host mode results in consistent and various issues on the USB bus and regular printing of the following errors:
```
[ 25.362355] tcpci 0-0052: TCPC fault - I2C Interface Error
...
[ 25.412987] t...Connecting a hub to the USB 3 port in host mode results in consistent and various issues on the USB bus and regular printing of the following errors:
```
[ 25.362355] tcpci 0-0052: TCPC fault - I2C Interface Error
...
[ 25.412987] tcpci 0-0052: TCPC fault - All Registers Reset To Default
```
With the `I2C Interface Error` being by far the most prevalent. Some of the issues on the bus from various different boots include:
```
[ 20.481986] usb 1-1: can't set config #1, error -71
```
```
[ 25.376295] usb 1-1-port3: cannot reset (err = -71)
[ 25.382750] usb 1-1-port3: cannot reset (err = -71)
[ 25.389620] usb 1-1-port3: cannot reset (err = -71)
[ 25.394730] usb 1-1: USB disconnect, device number 2
[ 25.399889] usb 1-1-port3: cannot reset (err = -71)
[ 25.405616] usb 1-1-port3: attempt power cycle
[ 25.412987] tcpci 0-0052: TCPC fault - All Registers Reset To Default
```
```
[ 325.192560] usb 1-1.1.2-port1: Cannot enable. Maybe the USB cable is bad?
```
https://source.puri.sm/Librem5/linux-emcraft/-/issues/24YongXing LCD panel (and others) not detected on HDMI2019-01-14T10:29:52ZDorota CzaplejewiczYongXing LCD panel (and others) not detected on HDMIHDMI stubbornly doesn't work for some on the team for an unknown reason. Hardware damage is not ruled out.
Symptom: the board boots, but nothing is ever shown on the screen, and it doesn't go out of standby mode.
Setup: a no-name Mini-...HDMI stubbornly doesn't work for some on the team for an unknown reason. Hardware damage is not ruled out.
Symptom: the board boots, but nothing is ever shown on the screen, and it doesn't go out of standby mode.
Setup: a no-name Mini-HDMI → HDMI dongle (<4cm with the plug, competes for space with the USB plug), a HDMI → $foo cable, a display
Displays:
- a 1080x1920 (portrait), HDMI YongXing LCD panel (attached data from this one)
- DELL E207WFP 1680x1050 DVI
The cable plug/unplug events look like this:
```
[ 4201.094069] [drm:drm_sysfs_hotplug_event] generating hotplug event
[ 4201.118251] [drm:drm_add_display_info] HDMI-A-1: No deep color support on this HDMI sink.
[ 4201.118272] [drm:drm_add_display_info] HDMI-A-1: No deep color support on this HDMI sink.
[ 4201.118463] [drm:drm_mode_object_get] OBJ ID: 42 (2)
[ 4201.118487] [drm:drm_mode_object_get] OBJ ID: 46 (1)
[ 4201.118496] [drm:drm_mode_object_get] OBJ ID: 42 (3)
[ 4201.118500] [drm:drm_mode_object_get] OBJ ID: 42 (4)
[ 4201.118518] [drm:drm_mode_object_put] OBJ ID: 42 (5)
[ 4201.118523] [drm:drm_mode_object_put] OBJ ID: 42 (4)
[ 4201.118528] [drm:drm_mode_object_put] OBJ ID: 47 (1)
[ 4201.118534] [drm:drm_mode_object_put] OBJ ID: 46 (2)
[ 4201.118539] [drm] HDMI/DP Cable Plug In
[ 4217.822047] [drm:drm_sysfs_hotplug_event] generating hotplug event
[ 4217.822256] [drm:drm_mode_object_put] OBJ ID: 43 (1)
[ 4217.822271] [drm:drm_mode_object_put] OBJ ID: 42 (3)
[ 4217.822330] [drm] HDMI/DP Cable Plug Out
```
modetest output:
```
trying to open device 'imx-drm'...done
Connectors:
id encoder status name size (mm) modes encoders
42 0 disconnected HDMI-A-1 0x0 0 41
props:
1 EDID:
flags: immutable blob
blobs:
value:
2 DPMS:
flags: enum
enums: On=0 Standby=1 Suspend=2 Off=3
value: 0
5 link-status:
flags: enum
enums: Good=0 Bad=1
value: 0
6 non-desktop:
flags: immutable range
values: 0 1
value: 0
19 CRTC_ID:
flags: object
value: 0
```
fbset output:
```
root@pureos:~# fbset "640x480 60Hz 32bit (GTF)"
ioctl FBIOPUT_VSCREENINFO: Invalid argument
```
and, most confusingly:
```
root@pureos:~# cat /sys/class/drm/card1-HDMI-A-1/status
connected
root@pureos:~# cat /sys/class/drm/card1-HDMI-A-1/modes
root@pureos:~#
```
TODO: run with `drm.debug=0x2f` on the kernel command linehttps://source.puri.sm/Librem5/linux-emcraft/-/issues/6bluetooth hid support2018-12-18T17:49:08ZGuido Guntherbluetooth hid supportfor external keyboard and mice.for external keyboard and mice.https://source.puri.sm/Librem5/linux-emcraft/-/issues/4mmc1 has a high number of interrupts2018-12-18T15:25:44ZAngus Ainslieangus.ainslie@puri.smmmc1 has a high number of interruptsWith the driver loaded but no traffic the RS9166 module is generating excessive interruptsWith the driver loaded but no traffic the RS9166 module is generating excessive interruptshttps://source.puri.sm/Librem5/linux-emcraft/-/issues/3arch_timer has an unusually high number of interrupts2024-03-28T13:13:56ZAngus Ainslieangus.ainslie@puri.smarch_timer has an unusually high number of interruptsOn an idle system the arch_timer interrupts as very highOn an idle system the arch_timer interrupts as very high