flip_done timed out on 5.10.52-v7l+ #1440 with vc4-kms-v3d #4493
Comments
It appears that, for some reason, the [ And |
|
If you stop kodi starting from boot do you still see the flip_done message? |
|
Phil, I might have mixed up my test results from #4489 and thus redid the test: http://paste.debian.net/1206148/ (this is with kodi running) After the reboot without kodi startup, indeed the error messages of the HifiBerry DAC and flip_done do not show up: Once I manually start kodi, the errors show up in Details about kodiIt is installed from apt. The pipplware repository is the source (I think): My kodi installation does bring up a bigpicture screensaver after some timeout. I would need to check the exact addon name, in case this is relevant to you. Kindly instruct what further information you need. |
|
I'd like to know the resolution kodi is switching to. If hdmi output stops immediately you may not be able to see that on display. Can you paste output of: (if that does exist try |
|
On the not rebooted system, below you find the desired dri state: http://paste.debian.net/1206150/ I now did a reboot while having the TV switched on (a ~8 year old Grundig model). It happily boots to console, as kodi service is still disabled. Once starting kodi from console (via ssh), the TV immediately goes first black and one second later to blue, indicating "no signal". Now I for testing purposes commented the |
|
Thanks for the updated log - that does show the correct CMA size. |
|
The dri status looks okay. It thinks it is driving |
|
Also did this setup work on a previous kernel? Do you know what the last working kernel was? |
|
According to apt, this was the conducted upgrade of firmware/kernel: Certainly, the kernel deployed by the 1.20210527 package could be looked up - to me it is not obvious where. Before reporting the issue I was operating on without noticing issues. Now on 5.10.52-v7l+, I gave fkms informationBeware that the following output is from me now running again on kodi.log (until startup finished): kms
This is identical to the fkms edid (expected, but I guess you never know.
|
|
kodi.log with kms and debug logging enabled would be useful (enable debug logging, restart kodi then grab kodi.log when you've got flip_done error). |
|
Finally I got the chance to do the test with kms and debug logging activated in kodi. Honestly, I'm not sure if the test went fine. I can confirm that once I manually initiated the kodi start, the display lost signal, but the kodi.log does not seem to contain enlightening output: It seems that me enabling debug logging did not stick ( |
|
I'm having the same issue on 2 Pi4's. Here is the rest of kodi.log after waiting a few minutes when the display output turns off kodi loads for a minutes then it's back to "no signal" but the kodi process is still running: I think you can safely ignore the 4096x2160 resolution as I'm normally using a 1080p TV and the problem is the same. And here is the same Pi and same monitor with a fresh image of LibreELEC, the only "hardware difference being that Raspberry Pi OS boots from iSCSI while libreelec boots from an SD card. |
Can you clarify if you meant that there is no problem (i.e. display is working), or "no apparent problem" in log (but display is broken). |
|
Sorry if that wasn't clear. In the first log from Raspberry Pi OS running Kodi I experience the same problem as PeterPablo. The second log is just running the latest LibreELEC to compare which works fine with approximately the same config.txt |
|
@Axionkt can you report |
|
@popcornmix Sure. I'm running Kodi 18.7 on Raspberry Pi OS Raspbian GNU/Linux 10 (buster)Raspberry Pi OS vcgencmd version
Raspberry Pi OS vcgencmd bootloader_version
Raspberry Pi OS config.txt
Raspberry Pi OS uname -a
Linux RPi4-2 5.10.52-v7l+ #1441 SMP Tue Aug 3 18:11:56 BST 2021 armv7l GNU/Linux Raspberry Pi OS dmesg
Raspberry Pi OS kodi.log when the display finally starts
Raspberry Pi OS kodi.log when the display stops again
LibreELECLibreELEC vcgencmd version
LibreELEC vcgencmd bootloader_version
LibreELEC config.txt
LibreELEC dmesg
|
|
I tried to pinpoint when the issue appeared using rpi-update on a freshly installed and updated RPiOS Lite image. Kodi works fine with this version: dmesg
Kodi takes very long to start with this version. When it starts CEC doesn't work and it crashes after ~1 minute dmesg
If it helps, as soon as I have enough time I'll try the modifications 1 by 1 between these 2 commits. |
|
So I had the time to find which commit causes the issue I also tried to update the firmware to pieeprom-2021-07-06 with the kernel updated up to this commit but no luck. If I go back to the previous commit (30606f3e2f1dbe7c68e11a6bfac1d3fd258305f2) Kodi starts normally, CEC works and it seems to experience no crashes from my limited testing. |
|
So, I can't tell what exactly worked around the issue but compiling Kodi 19.3 from the popcornmix bullseye branch and starting it with the same parameters as before works. |
|
This has probably been fixed by the firmware update mentioned in #4540 |
|
In the meanwhile I'm in the process of migrating to a freshly setup bullseye Raspberry Pi OS image (32bit). Here, running under kms, the apt supplied kodi works flawlessly. Thus I'll close this issue. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Applying
dtoverlay=vc4-kms-v3don an up-to-date Raspberry Pi OS and system yieldsflip_doneerror messages every 10s. Note that kodi is started on boot.Once I return to
fkmsthe system and rebootdmesgstays clean. Ref.raspinfo:http://paste.debian.net/1206037/
Is this possibly related to #4320?
Best regards
Peter
The text was updated successfully, but these errors were encountered: