Vero V crashes during playback - WIFI connected

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.

https://paste.osmc.tv/oluwopexom.coffee

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.

The pastebin system won’t handle pstore logs yet.

They need to be fetched manually.

Sam

Haven’t heard any news but noticed an update in the devel repository and did another test playing UHD over wifi after undating.

Crash results are here: uhd_crash_3.tar.xz

1 Like

I am going to add persistent store logs to My OSMC’s logging system shortly.
I’ll let you know when this in staging.

Sam

Had another crash today after latest update in staging.

Most times I can play a compressed downloaded UHD. And every now and then can make through a “full bitrate” ripped UHD, but never two in a row. It’s basically unreliable.

Also have still noticed the random delays when shelled in via ssh where the terminal stops responding for a bit. For some reason I think this is a big clue. If this kind of pause happens with a high bitrate playback something has to give.

Having the same issues with an eero network, so kind of confirms it does not appear to be a specific WAP or WAP brand causing the issue. I can pretty much reproduce it when seeking back and forth repeatedly on a 4K mkv, but sometimes it happens just during playback of 4K mkv’s. I then have to power cycle the Vero, as nothing responds.

Noting I’m using Jellyfin to stream video, so that’s another datapoint.

I just wanted to add another data point to Oberon’s feedback.

I have been experiencing (for months) the exact problem. Wifi is using Asus XT8 AiMesh mesh network. Remote filesystem is mounted as NFS via /etc/fstab. I spent the last few months tweaking the connection protocol to the remote filesystem (tried WebDav, SMB, various buffering options) before finding this specific discussion thread.

In my case, if I watch the movie through without much seeking, I rarely notice any crashes. However, regular seeking will sooner or later induce a crash as described above. The Vero V locks up and the only way to resume is to disconnect the power.

The evidence is anecdotal, but as per other posters the locking up seems more prevalent on more “heavyweight” MKVs (4K, Dolby Vision) rather than small 1-2 gig web ripped movies.

Having the same issues on an asus access point, smaller files are usually ok, but 4k ones crash after 3 to 4 minutes, forcing a power off to make it work again.

Latest crash after updating to latest staging.

uhd_crash_4.tar.xz