#RETROARCH KEEPS CRASHING DRIVERS#
#RETROARCH KEEPS CRASHING UPDATE#
#RETROARCH KEEPS CRASHING PATCH#

> Fixes: 7817949314a2 ('sna/dri2: Avoiding marking a pending-signal on a > And yes, this is indeed a fix to one of the debug patches that intended > Window is destroyed, we still must allow that flip to proceed or else > scanout until the future flip is performed.

#RETROARCH KEEPS CRASHING UPDATE#

> When the pending flip is queued, we update all the Windows to use the > sna/dri2: Complete the final flip in a chain after the window is (In reply to Chris Wilson from comment #190) Reported-and-tested-by: Rafael Ristovski įixes: 5008e874edd34 ('drm/i915: Make wait_for_flips interruptible.') Signal context, if the cursor blocks then it will stall both the inputĪnd output chains causing bad stuttering and horrible UX. Screen updates, in particular page flips. The legacy cursor ioctl expects to be asynchronous with respect to other I'm thinking about trying Linux 4.7-rc4 but I don't know whether that will help or not. That said, I want to help but I don't know what else to do anymore. I don't know what else to try, I apologize if I said something stupid.

Worked fine with UXA back then but not SNA, etc. I try xf86-video-intel with the stock arch kernel, and it fails, I reboot with modesetting/glamor and it works. I mean, it worked fine during the 4.5 kernels, then it regressed in 4.6, but if I compile 4.6 myself it works, it doesn't with the -ARCH kernel though. Yes, this is why I'm getting confused, too many variables. > Reporting that glamor works is the same as saying that if you don't use the That should be enough to work out the trigger. > You reported that a change in kernel configuration is enough to change the (In reply to Chris Wilson from comment #124) It's a case of RetroArch hanging and not being able to do anything until I press F on the app again and then I can move between menus or quit the app. This is also an app hang (RetroArch hang) and not a X hang, it is the same problem you said you was able to reproduce. I also run the same identical Arch Linux setup on both.

I'm not sure how it can be hardware/setup dependent since I was able to reproduce this on my ThinkPad as well as it happens on my desktop, and they both have different hardware. > older kernel just in case, but such a bug would also likely to be > looks like), so far it hasn't found a fresh hang. Modulo a bug in the testcase itself (or at least so it > In xf86-video-intel/test/dri2-race I have tests for everything we have > RetroArch, the video just also paused 2-3 seconds between changing modes.

#RETROARCH KEEPS CRASHING DRIVERS#

Next, quit Retroarch and reopen it, go to Settings -> Drivers -> Video and change the driver to vulkan. Once the game is running, go to the Retroarch menu -> Quick Menu -> Options and change the GFX Plugin to angrylion and RSP plugin to cxd4. > This time didn't hang when switching between fullscreen/windowed in First you need to start a game up in the core using the gl driver. > Xorg.0.log with debug=full and kernel 4.5.0 > (In reply to Diego Viola from comment #82) (In reply to Chris Wilson from comment #85) Xorg.0.log with debug=full and kernel 4.5.0 Xorg.0.log with latest driver and debug=full

#RETROARCH KEEPS CRASHING PATCH#

Xorg.0.log with patch applied and debug=fullįorce AttendClient after DRI2DrawableGone Xorg.0.log with latest crash after trying the patch Follow-up question here.Xorg.0.log backtrace with xf86-video-intel-git 2.99.7bebe12-1 by using hdmi_force_hotplug=1 in /boot/config.txt then plugging in a screen should show an input, and plugging in a keyboard and hitting the space bar a bit should show something on the screen (or not).

Where is a place to get more specific support for this kind of broad, vague problems?Ī comment made by Goldilocks to determine the difference if it really crashes or I just can log in.

What might I do the log this behaviour?.

Where should I look to narrow this down?.

When it crashes I can't login or reach it in any way.

The external drive is externally powered.

Neither had problems with an older Pi model.

I tried 2 different power supplies for the Pi.

Pulling the plug and reinserting it creates a successful reboot. It crashed last night when it was idling, and does so a few times a week. And a external hard drive with videos on it. I know my problem is too vague to solve the root problem.

Retroarch keeps crashing