Emulator Crashing

Help and Support Vero 4K / Vero 4K +
1

Was running Link to the Past fine for the past couple weeks. Performed the November update, went to play it again today and it locks my entire system. I SSH in and it had errors a few times (and took literal minutes to actually connect) but I finally got it to do a sudo reboot command.

I think the problem is at the end of the log file I grabbed. If you scroll to the bottom you’ll see a bunch of “Create - Error Creating” lines.
https://paste.osmc.tv/uveyeniqow

Any thoughts?

Also, Happy Thanksgiving to everyone in the states!

2 
2019-11-28 16:51:12.210 T:3878662880   ERROR: Previous line repeats 51 times.
2019-11-28 16:51:13.639 T:3878662880   ERROR: AddOnLog: Joystick Support: ScanEvents: failed to read joystick "Xbox 360 Wireless Receiver" on /dev/input/js0 - 19 (No such device)
2019-11-28 16:51:14.348 T:4022330080   ERROR: CAESinkALSA - snd_pcm_writei(-32) Broken pipe - trying to recover
2019-11-28 16:51:21.944 T:3878662880   ERROR: AddOnLog: Joystick Support: ScanEvents: failed to read joystick "Xbox 360 Wireless Receiver" on /dev/input/js0 - 19 (No such device)
2019-11-28 16:51:23.002 T:4022330080   ERROR: CAESinkALSA - snd_pcm_writei(-32) Broken pipe - trying to recover
2019-11-28 16:51:24.127 T:3887055584   ERROR: AddOnLog: Joystick Support: ScanForJoysticks: can't open /dev/input/js0 (errno=13)
2019-11-28 16:51:25.114 T:3887055584  NOTICE: UnregisterRemovedDevices - device removed from joystick/peripheral.joystick/0: Xbox 360 Wireless Receiver (0000:0000)
2019-11-28 16:51:25.752 T:4022330080   ERROR: CAESinkALSA - snd_pcm_writei(-32) Broken pipe - trying to recover

Seems to be an issue with the controller

3

Well, since you could SSH in, it’s not locked up! :wink:

After you SSH in, you can run top, (or better install htop) to see what process is using the CPU.

To install htop:

sudo apt install htop
4

@Toast I think this is the most likely culprit. I was switching between controllers to try and figure it out. I even unplugged the receiver and it didn’t change anything. (Which I think is why those errors are showing up).

What finally fixed it was unplugging the receiver, rebooting the Vero, and then plugging it back in. At least it seems to have stabilized for now.

@bmillham I’ll install htop in the event I have more problems. Lock is probably the wrong word, but I think you know what I meant. Something was causing high utilization. SSH was unbearably slow to use (and even the sudo reboot would error out a few times) but persistence pays off I suppose. :wink: