Summary: | lockup during gameplay of Batman series of games | ||
---|---|---|---|
Product: | Mesa | Reporter: | farmboy0+freedesktop |
Component: | Drivers/Gallium/radeonsi | Assignee: | Default DRI bug account <dri-devel> |
Status: | RESOLVED FIXED | QA Contact: | Default DRI bug account <dri-devel> |
Severity: | normal | ||
Priority: | medium | CC: | vedran |
Version: | git | ||
Hardware: | Other | ||
OS: | All | ||
Whiteboard: | |||
i915 platform: | i915 features: | ||
Attachments: |
Journalctl log of the crash
ddebug info |
Description
farmboy0+freedesktop
2016-08-01 13:09:52 UTC
Is this Tonga (380/380X) or some other card? Mobile Tonga it seems. @farmboy0 Does lockups happens with regular wine? I remember cases when Catalyst can lockup using wine-csmt too... just a note that wine-csmt isn't perfect always so check regular wine too. (In reply to smoki from comment #2) > Mobile Tonga it seems. Desktop and mobile chip have the same PCI ID, that's why I ask [1]. I might be able to test Batman on my 380X to confirm the issue. [1] https://pci-ids.ucw.cz/read/PC/1002/6938 At least AMD listing 00, F0, F1 revs... so pci-ids project might try to differinate descriptions somehow by revs too: http://developer.amd.com/resources/ati-catalyst-pc-vendor-id-1002-li/ For the bug, i suspect it is one of those "as soon as threading is pushed lockup happens" ;) This is a desktop Sapphire 380X. I'll try with normal wine, I *think* I tried that already and it also locked up but Ill test again to be sure. Yep , also locking up with normal wine. To test just run the benchmark. It will lock up there and in the normal game. (In reply to farmboy0+freedesktop from comment #6) > Yep , also locking up with normal wine. > > To test just run the benchmark. It will lock up there and in the normal game. How much hassle is to get Batman working? Is it more than wine Steam.exe, Install Batman, Play? If not, I could try it tomorrow. I *think* you need DotNet installed in your prefix. My Steam install resides there at least. Otherwise yeah Install and play should suffice. You might want to remove the intro movies they are annyoing. Instructions can be found in the PC Gaming Wiki. I'm going to attach part of a journalctl log of the hang/crash. This is an Arch Linux host using the regular 'linux' Arch Linux kernel (version 4.7), Mesa 12.0.1, and Wine 1.9.17 (no matter if I use -staging or -gaming-nine) with a Sapphire R9 280X 3GB GDDR5 OC DUAL-X GPU. A video of the crash as it happens: http://nanosector.ddns.net:9090/BGLL0XLY/file_309.mp4 Note that I don't know how long that video will be up for. I've tried mesa-git to see if that eliminates the issue, but it behaves in the same manner. Created attachment 125998 [details]
Journalctl log of the crash
Created attachment 126123 [details]
ddebug info
Looks like this patch fixes the problem: https://lists.freedesktop.org/archives/mesa-dev/2016-December/137213.html GPU hangs in Batman Arkham: Origins were fixed by this commit: https://cgit.freedesktop.org/mesa/mesa/commit/?id=6dc96de303290e8d1fc294da478c4f370be98dea Closing. |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.