Open valscion opened 7 years ago
I got this again, and now with allegro.log enabled, here's the contents:
https://gist.github.com/valscion/e787514dd0163d7a6f41444723734f4a
And again, adding even more logging output for this:
https://gist.github.com/valscion/69eae32756c2d17772753a349a4b4271
Actually, it might just be that the logging slowed the starting up down so that the program might actually become responsive again. I'll have to make sure it isn't the case.
Could you perhaps compile the examples that come with Allegro 5 sources and try to run them all, or at least the screen related ones? That could give us some better idea of where the problem might be.
On 11 Aug 2017 10:47 p.m., "Vesa Laakso" notifications@github.com wrote:
And again, adding even more logging output for this:
https://gist.github.com/valscion/69eae32756c2d17772753a349a4b4271
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/liballeg/allegro5/issues/798#issuecomment-321914934, or mute the thread https://github.com/notifications/unsubscribe-auth/AAEWeSQpDeD2ZDPsrg_F6JTSueHfNOgsks5sXL3MgaJpZM4O1EOq .
Nah, I'm pretty certain that both of those logs are realistic. I see a gpuRestart log being generated in system logs:
Soo... a DMA Engine Error?!?
Could you perhaps compile the examples that come with Allegro 5 sources and try to run them all, or at least the screen related ones? That could give us some better idea of where the problem might be.
Yeah, I'll try that. I'm sorry if I keep spamming your email as I debug this further 😅
http://themacblog.com/how-to/fix-kernel-nvdaopengl-channel-exception/
It may be a HW problem, or so I read after googling the error.
As for spamming, could you perhaps wait until you have run all example programs and collected all logs you think relevant and then post them in one big message? It a bit hard to follow this thread if you post your results immediately when you get them.
KR, B.
On 11 Aug 2017 10:55 p.m., "Vesa Laakso" notifications@github.com wrote:
Could you perhaps compile the examples that come with Allegro 5 sources and try to run them all, or at least the screen related ones? That could give us some better idea of where the problem might be.
Yeah, I'll try that. I'm sorry if I keep spamming your email as I debug this further 😅
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/liballeg/allegro5/issues/798#issuecomment-321916627, or mute the thread https://github.com/notifications/unsubscribe-auth/AAEWeZFco_z_svkUE2NkRC_dD3X9wpYRks5sXL-4gaJpZM4O1EOq .
It may be a HW problem, or so I read after googling the error.
Yeah, I'm afraid that might be the case. However it's strange that I've only ever encountered this with Allegro, and that I can consistently reproduce this on Allegro with a few tries.
As for spamming, could you perhaps wait until you have run all example programs and collected all logs you think relevant and then post them in one big message? It a bit hard to follow this thread if you post your results immediately when you get them.
The trouble is, I'm not sure which logs are relevant and I'm afraid I'm gonna forget to post some critical piece of information so I just... send all the things once I hit a failure.
I'll try to be a bit more methodological with my logging and group them together.
I wanted to split this particular failure out from #796 so I could shed some more insight and logs particulary for the case when I:
speed
demo appIn this case, also the title of the window seems to not be retina ready, which is strange.
I checked system logs, and saw this being generated in all sys logs:
It tells that more details can be found from a specific log file:
The gpuRestart log file was generated successfully.
Here's the full logs:: https://gist.github.com/valscion/4ac8cd5c88a63c40856ef0d961a55cf5
This seems to be what happened, as seen from the gpuRestart log: