There’s a problem with the staging version - it didn’t build properly owing to a github glitch. It’s being worked on. Likely tomorrow will be fixed.
As @grahamh said, the kernel that enables this functionality wasn’t made available in staging when I made the post due to an issue with GitHub.
This is now pushed, so you should find that the necessary files are now generated when there is a crash if you update again
Thanks
Sam
This is also fixed in the staging repository if you update again
Sam
It still doesn’t work for me.
Maybe it’s not kernel panic?
First - congrats on the FEL. Second, no dice on the wifi crash.
Not sure on how to use that pastebin site, but the crash files are here: uhd_crash.tar.xz
Did another test today, another crash: uhd_crash_2.tar.xz
Something has definitely changed. Before I switched to Ethernet, I was experiencing crashes several times a day.
But after switching back to WiFi for this test, I have only experienced one crash in a week, so I can’t be of much help here.
Fortunately, @chris8 has uploaded some logs that show a possible problem with the Realtek 8822cs WiFi driver.
Every now and then it will play one UHD movie successfully but it has never played two in a row.
Did another test today but this time the video just froze, no auto-reboot and nothing in pstore after forced reboot.
I have also been having issues with playback. Playback is currently with 1080P videos and video will freeze for a few moments then exit out of playback to previous menu showing episode selections.
I also have vero v crash on high bitrate 4k videos. Using unifi wifi. Ill try and grab logs but system totally locks and I have to pull the power plug to get it going again.
I just did another test and ther system just froze like the last time, no logs in pstore after power cycling to reboot. The system freezing is the same I experienced when I first reported this issue over two years ago. The Vero V becomes totally unresponsive, does not respond to the remote, cannot shell in, does not respond to ping or arping.