Bug 100681

Summary: F1 2015 glitches (letters mainly)
Product: Mesa Reporter: jdruel
Component: Drivers/Gallium/radeonsiAssignee: Default DRI bug account <dri-devel>
Status: RESOLVED FIXED QA Contact: Default DRI bug account <dri-devel>
Severity: normal    
Priority: medium CC: jdruel, mail
Version: git   
Hardware: x86-64 (AMD64)   
OS: Linux (All)   
Whiteboard:
i915 platform: i915 features:
Attachments: glitches on f1 2015

Description jdruel 2017-04-14 06:29:53 UTC
Created attachment 130840 [details]
glitches on f1 2015

Running f1 2015 launched from steam-native on ArchLinux, latest mesa-git (91024).
Letters are very blurry (looks like there's some snow on the screen).
Hardware: i7-4770k, r9 fury
Testing on a track, I also had a freeze after 30s of gameplay.
Comment 1 Michel Dänzer 2017-04-14 07:04:03 UTC
Apparently this is an LLVM regression, someone needs to bisect.
Comment 2 Christoph Haag 2017-04-14 09:29:48 UTC
Should be between llvm 299913 and 300035.
Comment 3 Andy Furniss 2017-04-17 11:35:10 UTC
Possibly 300023

https://bugs.llvm.org/show_bug.cgi?id=32666
Comment 4 Michel Dänzer 2017-04-18 02:04:53 UTC
(In reply to Andy Furniss from comment #3)
> Possibly 300023
> 
> https://bugs.llvm.org/show_bug.cgi?id=32666

Usually the quickest way to a solution in cases like this is to report the regression directly to the author of the regressing change, with llvm-commits@lists.llvm.org in Cc.
Comment 5 Andy Furniss 2017-04-18 18:51:30 UTC
OK, I sent a mail - awaiting moderation for the cc as I am not on any llvm lists.

I did try to add the author as cc on the tracker when I filed the bug, but no luck, it would be handy if committers could join the bug tracker of the projects they commit to, (with the email they use to commit).
Comment 6 Michel Dänzer 2017-04-20 02:20:34 UTC
Might be fixed with LLVM r300791.
Comment 7 jdruel 2017-04-20 13:14:51 UTC
Tried with llvm300824. Pb solved. Thanks. I'm closing the bug report.

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.