Bug 89447 - [bisected] [radeonsi+wine_d3dadapter+Bioshock] GPU lockup 8 minutes after start
Summary: [bisected] [radeonsi+wine_d3dadapter+Bioshock] GPU lockup 8 minutes after start
Status: RESOLVED FIXED
Alias: None
Product: Mesa
Classification: Unclassified
Component: Drivers/Gallium/radeonsi (show other bugs)
Version: git
Hardware: x86 (IA32) Linux (All)
: medium normal
Assignee: Default DRI bug account
QA Contact: Default DRI bug account
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-03-05 20:38 UTC by Arek Ruśniak
Modified: 2017-01-02 20:32 UTC (History)
0 users

See Also:
i915 platform:
i915 features:

Attachments
dmesg linux_4rc2 (67.27 KB, text/plain)
2015-03-05 20:38 UTC, Arek Ruśniak 		Details
dmesg linux 3.19 (460.42 KB, text/plain)
2015-03-05 21:45 UTC, Arek Ruśniak 		Details
View All

Description Arek Ruśniak 2015-03-05 20:38:50 UTC 
Created attachment 114043 [details]
dmesg linux_4rc2

cape verde 
kernel 4rc2/3.19 x86 
llvm svn230872
radeon git
xorg 1.17.1
mesa git

git bisect... gives this:

5f1cef76f9bbaae772120dcb38e0b98d68a93f26 is the first bad commit
commit 5f1cef76f9bbaae772120dcb38e0b98d68a93f26
Author: Marek Olšák <marek.olsak@amd.com>
Date:   Sat Feb 7 13:19:38 2015 +0100

    r600g,radeonsi: use fences to implement PIPE_QUERY_GPU_FINISHED
    
    Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=89014
    
    Reviewed-by: Michel Dänzer <michel.daenzer@amd.com>

:040000 040000 aae0244556c43c9d03243992143a8c9fc0128977 7f320431b51c3f55f243448b0b5dc3031feb6abb M	src


64bit system is affected too but GPU was hung after about one hour.
Comment 1 Arek Ruśniak 2015-03-05 21:45:00 UTC 
Created attachment 114044 [details]
dmesg linux 3.19

maybe it will be more useful.

PS
It happen only with nine, without native d3dx9 there is no lockups.
Comment 2 Arek Ruśniak 2017-01-02 20:32:31 UTC 
Few month ago when I checked Bioshock 1, there was no problem with wine-nine, probably no one care even me at last

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.