[Rpi4] Big delay showing video (and frequent crashes)

lnoferin · May 19, 2024 at 9:15 PM

My hardware: raspberry pi4 with 4gb of ram, a HiFiBerry audio and a hard disk connected via usb

Software: Libreelec 12.0 with aeon nox skin

From some weeks (also before the switch from 11.X to 12.0 version, nothing changed) I have a lot of delay trying to see normal videos (taken from a nfs server but nothing changed switching to samba and also from the system disc).

If I look into the kodi log I cannot see anything, as the system was freezed: when the video starts I can see many errors in kodi.log like

Code

2024-05-19 21:57:10.706 T:8076  warning <general>: OutputPicture - timeout waiting for buffer

If I look in dmesg I can see this error:

Code

[13638.659236] WARNING: CPU: 2 PID: 6833 at __vb2_queue_cancel+0x26c/0x2e0 [videobuf2_common]
[13638.659261] Modules linked in: 8021q rfcomm brcmfmac_wcc brcmfmac brcmutil rpivid_hevc(C) bcm2835_isp(C) bcm2835_codec(C) v4l2_mem2mem bcm2835_mmal_vchiq(C) hci_uart btbcm videobuf2_dma_contig videobuf2_memops videobuf2_v4l2 cfg80211 bluetooth videodev snd_bcm2835(C) ecdh_generic snd_soc_wm8804_i2c videobuf2_common ecc snd_soc_bcm2835_i2s rfkill snd_soc_rpi_wm8804_soundcard snd_soc_wm8804 mc nvmem_rmem pkcs8_key_parser fuse nfnetlink
[13638.659341] CPU: 2 PID: 6833 Comm: VideoPlayer Tainted: G         C         6.6.28 #1
[13638.659348] Hardware name: Raspberry Pi 4 Model B Rev 1.1 (DT)
[13638.659352] pstate: 80000005 (Nzcv daif -PAN -UAO -TCO -DIT -SSBS BTYPE=--)
[13638.659357] pc : __vb2_queue_cancel+0x26c/0x2e0 [videobuf2_common]
[13638.659369] lr : __vb2_queue_cancel+0x40/0x2e0 [videobuf2_common]
[13638.659379] sp : ffffffc087063ae0
[13638.659383] x29: ffffffc087063ae0 x28: ffffff8043c34d28 x27: ffffff804587a000
[13638.659394] x26: 0000000000000000 x25: ffffffc087063d28 x24: ffffff80cde85300
[13638.659403] x23: 0000000000000000 x22: 0000000000000000 x21: ffffff80525fe828
[13638.659413] x20: ffffff80525fe828 x19: ffffff80525fe828 x18: ffffffffffffffff
[13638.659421] x17: 00000001870638b0 x16: 0000000000000000 x15: 0000000000000003
[13638.659431] x14: 0000000000000004 x13: ffffff804bb00028 x12: 0000000000000000
[13638.659439] x11: ffffff804d96ce78 x10: ffffff804d96cdb0 x9 : ffffffc07a155a8c
[13638.659448] x8 : ffffff804d96cdd8 x7 : 0000000000000000 x6 : 0000000000000000
[13638.659457] x5 : ffffff8043c3601c x4 : 0000000000000000 x3 : 0000000000000000
[13638.659465] x2 : ffffff80499c1b80 x1 : 0000000000000000 x0 : 0000000000000004
[13638.659474] Call trace:
[13638.659478]  __vb2_queue_cancel+0x26c/0x2e0 [videobuf2_common]
[13638.659489]  vb2_core_streamoff+0x2c/0xd0 [videobuf2_common]
[13638.659498]  vb2_streamoff+0x20/0x78 [videobuf2_v4l2]
[13638.659509]  v4l2_m2m_streamoff+0x80/0x1d8 [v4l2_mem2mem]
[13638.659520]  v4l2_m2m_ioctl_streamoff+0x20/0xe38 [v4l2_mem2mem]
[13638.659530]  v4l_streamoff+0x2c/0x40 [videodev]
[13638.659551]  __video_do_ioctl+0x334/0x408 [videodev]
[13638.659568]  video_usercopy+0x2bc/0x6e0 [videodev]
[13638.659584]  video_ioctl2+0x20/0x40 [videodev]
[13638.659600]  v4l2_ioctl+0x48/0x70 [videodev]
[13638.659616]  __arm64_sys_ioctl+0xc4/0xf0
[13638.659628]  invoke_syscall+0x50/0x128
[13638.659637]  el0_svc_common.constprop.0+0x48/0xf0
[13638.659644]  do_el0_svc+0x24/0x38
[13638.659650]  el0_svc+0x40/0xe8
[13638.659655]  el0t_64_sync_handler+0x120/0x130
[13638.659659]  el0t_64_sync+0x190/0x198
[13638.659665] ---[ end trace 0000000000000000 ]---
[13638.876961] hrtimer: interrupt took 172885 ns

Display More

Could the problem coming from some extension because it started after I installed some extension to the skin but I cannot understand the wrong one?

EDIT: the dmesg error seems to be unrelated to the problem because sometime it does not appear

**Da Flex** · May 19, 2024 at 9:46 PM

The OutputPicture - timeout waiting for buffer warning is normal (I've just learned that myself).

Try again with the default skin.

**chewitt** · May 20, 2024 at 4:11 AM

The timeout messages are harmless. The kernel splat is undesirable but ultimately harmless too (it's a WARNING, not an ERROR).

TL/DR: If you don't know what something is in a log, always share the entire log, because then you share all the actually useful info and not just the couple of irrelevant bits that you (wrongly) guessed were important.

lnoferin · May 20, 2024 at 2:24 PM

Quote from Da Flex

Try again with the default skin.

I am trying with estuary skin but nothing changed

Quote from chewitt

The timeout messages are harmless. The kernel splat is undesirable but ultimately harmless too (it's a WARNING, not an ERROR).

Yes, understood!

Quote from chewitt

TL/DR: If you don't know what something is in a log, always share the entire log, because then you share all the actually useful info and not just the couple of irrelevant bits that you (wrongly) guessed were important.

I am trying to look at the debug log (enabled from the skin menu) but it became really too verbose: which log module should I have to enable to look for my problem?

**Da Flex** · May 20, 2024 at 2:37 PM

This maybe sounds like magic, but try without any HiFiBerry driver activated at config.txt (and of course reboot).

lnoferin · May 20, 2024 at 2:54 PM

Quote from lnoferin

I am trying to look at the debug log (enabled from the skin menu) but it became really too verbose: which log module should I have to enable to look for my problem?

This is a log with some log module enabled with estuary skin trying to see a movie in the samba share:

debian Pastezone

I think the relevant lines are 517-518: almost five minutes waiting to start the reproduction.

**Da Flex** · May 20, 2024 at 3:01 PM

Quote from lnoferin

https://paste.debian.net/1317495/

Code

2024-05-20 15:41:02.962 T:7382     info <general>: Disabled debug logging due to GUI setting. Level 0.

Not helpful.

Please provide a full debug log.

How to post a log (wiki)

1. Enable debugging in Settings>System Settings>Logging
2. Restart Kodi
3. Replicate the problem
4. Generate a log URL (do not post/upload logs to the forum)

use "Settings > LibreELEC > System > Paste system logs" or run "pastekodi" over SSH, then post the URL link

lnoferin · May 20, 2024 at 3:05 PM

Quote from Da Flex

This maybe sounds like magic, but try without any HiFiBerry driver activated at config.txt (and of course reboot).

Tried but nothing changed.

**Da Flex** · May 20, 2024 at 3:10 PM

Quote from lnoferin

Tried but nothing changed.

Does that mean you still have audio without the config.txt driver entry?

I heard that HiFiBerry cards are now auto-detected.

lnoferin · May 20, 2024 at 3:16 PM

Quote from Da Flex

Does that mean you still have audio without the config.txt driver entry?

Yes

Quote from Da Flex

I heard that HiFiBerry cards are now auto-detected.

I don't think so because the soundcard does not appear anymore in the audio devices listed by kodi.

**Da Flex** · May 20, 2024 at 3:20 PM

Quote from lnoferin

I don't think so because the soundcard does not appear anymore in the audio devices listed by kodi.

So you get HiFiBerry sound without having a HiFiBerry card in the audio output device list?

lnoferin · May 20, 2024 at 3:30 PM

Quote from Da Flex

So you get HiFiBerry sound without having a HiFiBerry card in the audio output device list?

No, I removed the hifberry in config.txt to try for my problem and rebooted but now I cannot use the hifiberry and I am using the hdmi audio output.

(Normally I switch between the two audio devices - plus bluetooth - via the audio chooser addon)

**Da Flex** · May 20, 2024 at 3:33 PM

Thanks. Please post a link to a log now.

lnoferin · May 20, 2024 at 3:37 PM

Quote from Da Flex
Code
2024-05-20 15:41:02.962 T:7382     info <general>: Disabled debug logging due to GUI setting. Level 0.
Not helpful.
Please provide a full debug log.

How to post a log (wiki)

1. Enable debugging in Settings>System Settings>Logging
2. Restart Kodi
3. Replicate the problem
4. Generate a log URL (do not post/upload logs to the forum)

use "Settings > LibreELEC > System > Paste system logs" or run "pastekodi" over SSH, then post the URL link

Here the full log, without hifiberry in config.txt

https://paste.libreelec.tv/arriving-flamingo.log

P.S.: thanks a lot for your help!

**chewitt** · May 20, 2024 at 3:45 PM

Banned add-ons are installed. No support.

Official:Forum rules/Banned add-ons - Official Kodi Wiki

lnoferin · May 20, 2024 at 3:49 PM

Quote from chewitt

Banned add-ons are installed. No support.
https://kodi.wiki/view/Official:Forum_rules/Banned_add-ons

Urca, it's a very old installation and I did not remember what addon was installed from time to time.

Sorry

**Da Flex** · May 20, 2024 at 3:50 PM

Code

2024-05-20 16:27:42.819 T:3339    debug <general>: NFS: Context for 192.168.1.100/export/Musica not open - get a new context.
2024-05-20 16:27:42.820 T:3339    debug <general>: NFS: version: 3
2024-05-20 16:27:42.826 T:3339    debug <general>: NFS: Connected to server 192.168.1.100 and export /export/Musica
2024-05-20 16:27:42.826 T:3339    debug <general>: NFS Server max read chunksize (1048576) is bigger than client setting - Using client value 131072
2024-05-20 16:27:42.826 T:3339    debug <general>: NFS Server max write chunksize (1048576) is bigger than client setting - Using client value 131072
2024-05-20 16:27:42.826 T:3339    debug <general>: NFS: chunks: r/w 131072/131072
2024-05-20 16:27:42.828 T:3339    error <general>: NFS: Failed to stat(export/Musica/I/I Mother Earth/Dig/folder.jpg) stat call failed with "NFS: Lookup of /I/I Mother Earth/Dig/folder.jpg failed with NFS3ERR_NOENT(-2)"

Try without NFS. If you have the option to update to NFSv4 on your server, please do.

lnoferin · May 20, 2024 at 4:32 PM

Code

2024-05-20 16:27:42.820 T:3339    debug <general>: NFS: version: 3

Try without NFS. If you have the option to update to NFSv4 on your server, please do.

But the videos are on a samba share and the music works fine!