New bug/crash from 15 days with new ES release

Hex

If its a bluetooth device it might not be triggering Joystick connected/disconnected events. That is the only reason for this assert to fail.

darknior

@pjft How do you want i update it ?
Can i do an apt-get update / upgrade ? I never do it on pi to break nothing ...

I have 4 x360 controllers with Microsoft Bluetooth adapter, and the Keyboard is the Rii ... i love it :p

https://www.amazon.fr/gp/product/B00X365POY/ref=oh_aui_detailpage_o04_s01?ie=UTF8&psc=1

How can i remove power saving feature ?

herb_fargus

@darknior xbox 360 controllers don't use bluetooth.

meleu

@darknior said in New bug/crash from 15 days with new ES release:

How do you want i update it ?

https://retropie.org.uk/docs/Updating-RetroPie/

Hex

@darknior To disable PowerSaver

Settings > Other Settings > PowerSaver Modes > Disabed

darknior

@herb_fargus Yes i know, i think the problem come after, when the keyboard shut down alone, i write it before. It use bluetooth. I don't know i'm like you, and i give the error line code.

@meleu I know that, i use all of that every day at this moment to work on my project.
I want to know how to update bluetooth only like write @pjft . For my part i update nothing. Only ES and core with the Retropi-setup

@Hex Ok thanks i will try this night to see if the pi crash or not. thanks

Because the problem was not only the crash and return to command line, it is that i must reboot the PI because i can never connect back the keyboard :(

Hex

Chances are that the problem stems from Bluetooth keyboard shutting down without informing ES.

Can you try booting into ES and then connecting your Bluetooth keyboard?

darknior

@hex I do it every day, and try it now, it do nothing when i take the keyboard on. It works fine and the PI don't crash.

My PowerSaver Modes was already Disabed ... i forgot this lol
I put it default to try. i don't know what are doing extended and instant options.

pjft

@darknior sorry, I wasn't suggesting you to update it - it was more a question of had you updated it recently, and whether that update would be causing the problems.

As I said, nothing really changed on the ES front that I'm aware of, though I can check tomorrow, so I'm not really sure why you'd only have started to observe this now.

Hex

@pjft Considering that he has PS options I am guessing he is running >v2.5

pjft

@hex I was referring to the Bluetooth drivers or OS, as I don't think anything changed in ES's InputManager, but maybe I'm mistaken.

darknior

@pjft From yesterday i activate the Power Saver option to default, my PI not crashing again.
I'll let it work like that several days to see ...

Hex

@pjft This is the first time that PS enabled solved a problem :)

@darknior The problem is present in ES. PS enabled (default) might just be hiding it due to the wake ups and sleeps. Try reproducing it using PS disabled. If you are able to reproduce it consistently then we have a bug.

ttusoulfan

so i have been having a similar issue,except that when i go to install the roms it gives the a similar error.

darknior

Ok @Hex . Tonight i let it with the option enable, and if it not crash, tomorrow i will disabling it again.
But how to help you to repair it ? Can i have some logs ?

Hex

Do not connect any bluetooth devices while testing. I will not need logs as the error is an assert failing. So I can study it based on if it fails due to PS.

Can you tell me if you have screensaver enabled? and of what type?

ChauncyBlack

I can confirm this freezing during idle is caused by a recent emulation station update. I'm running on a combination of RPi3, Retropie 4.2, a known good SD card, and 2 Logitech wireless Rumblepad 2 joysticks. The system had been running flawlessly until my most recent updates of installed base packages (via apt-get update/upgrade), kernel (via rpi-update, currently at 4.9.45), and Retropie packages (via retropie_setup.sh), about a week ago (around August 20 or so). Previous full system update took place around end of June or beginning of July, and had been running fine. Once this freezing behavior started, I thought maybe the update process had corrupted the file system (as it has happened to me before), so I did a completely clean install using the 7/5/17 raspian lite image (last official Jesse release) and a manual install of the retropie script (git clone, etc.). The problem immediately reappeared.

I am using a wired network connection; wifi is on but unused. Bluetooth is on, but no devices are connected. If left idle after booting into emulation station, the system will soft-hang in about an hour, with video and joysticks becoming unresponsive. If I attempt to log in via ssh, the terminal appears to hang, but I can Ctrl-C out of the hung logon process and get a prompt. A dmesg query returns a number of repeated warning about a hung kworker thread being unresponsive for over 120 seconds. That repeats in the log 4 or 5 times, and then the log ends. The process id of the hung kworker thread changes every time. A query with "journalctl -p 3 -xb" gives similar error messages. I haven't been able to find anything else in the logs. At this point in the process, if I attempt a "sudo reboot", my terminal session terminates, but the RPi never actually reboots.

I have found that if I restart the system and quit out of emulation station to the command line, the system remains responsive and functions as expected (e.g. I can login via terminal normally, I can reboot, and dmesg and journalctl behave and expected) and has done so for about six hours since my last reboot.

Hope that helps.

pjft

The file in question hasn't been changed since April, and it has been only for minor maintenance issues. :/

Unless it'd be related to something with Power Savings (which I'm not clear that it would, given the reports from @darknior ), we might be on the wrong track here.

@ChauncyBlack does this also happen if you disable Power Savings?

Sano

FYI , someone had similar errors 7 months ago (no PS at the time) :
https://retropie.org.uk/forum/topic/7744/repeatable-crash-w-bluetooth-error

Could it be related to SDL ?

pjft

@sano My bet is that it is indeed related to ES input management via SDL or the underlying OS drivers, and has been there for a while now. But without hard evidence it's hard to narrow down what may be affecting this.