Bug 58658 - Minecraft menu broken on CAYMAN (caused by r600g: add htile support v16 patch)
Summary: Minecraft menu broken on CAYMAN (caused by r600g: add htile support v16 patch)
Status: RESOLVED FIXED
Alias: None
Product: Mesa
Classification: Unclassified
Component: Drivers/Gallium/r600 (show other bugs)
Version: git
Hardware: Other All
: medium normal
Assignee: Default DRI bug account
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-12-22 20:06 UTC by Thomas Rohloff
Modified: 2013-12-04 18:36 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:


Attachments
Screenshot of the broken menu. (104.31 KB, image/png)
2012-12-22 20:06 UTC, Thomas Rohloff
Details

Description Thomas Rohloff 2012-12-22 20:06:44 UTC
Created attachment 71997 [details]
Screenshot of the broken menu.

This is on newest mesa from git with kernel 3.8-rc1 (+ this patch: http://cgit.freedesktop.org/~agd5f/linux/commit/?h=drm-fixes-3.8&id=668bbc81baf0f34df832d8aca5c7d5e19a493c68 )

When the Mojang loading screen should stop and the menu should be rendered all that happens is that the menus background is rendered in one edge, see attachment.
Comment 1 Thomas Rohloff 2012-12-22 20:07:25 UTC
Sorry for the wrong mime-type. The screenshot is image/png, not text/plain.
Comment 2 Alex Deucher 2012-12-22 23:43:58 UTC
I suspect this is a mesa 3D driver issue rather than a kernel issue.  Was this working in the past?  Can you bisect?
Comment 3 Thomas Rohloff 2012-12-23 00:24:50 UTC
I'm not sure if it's mesa or kernel. Yes, it was working before last update (updated mesa + kernel).

I might be able to bisect later but atm my time is limited and as I don't even know what to bisect (kernel or mesa) it may take some time.
Comment 4 Thomas Rohloff 2012-12-23 21:42:32 UTC
Bisected mesa.

This is a mesa bug caused by http://cgit.freedesktop.org/mesa/mesa/commit/?id=6532eb17baff6e61b427f29e076883f8941ae664

Can anybody move this to the right place or do I have to re-create the report (and if so: Where) ?
Comment 5 Dmitry Cherkassov 2012-12-25 15:00:44 UTC
I can confirm that 6532eb17baff6e61b427f29e076883f8941ae664 causes problems.
glxgears start with black screen for few secs and then run at 0.8 FPS.
kernel radeon says smth like this:

[ 2077.626229] radeon 0000:01:00.0: GPU fault detected: 146 0x00239514
[ 2077.632491] radeon 0000:01:00.0:   VM_CONTEXT1_PROTECTION_FAULT_ADDR   0x00000000
[ 2077.639970] radeon 0000:01:00.0:   VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x00000000
Comment 6 Dmitry Cherkassov 2012-12-25 15:02:37 UTC
(In reply to comment #4)
> Bisected mesa.
> 
> This is a mesa bug caused by
> http://cgit.freedesktop.org/mesa/mesa/commit/
> ?id=6532eb17baff6e61b427f29e076883f8941ae664
> 
> Can anybody move this to the right place or do I have to re-create the
> report (and if so: Where) ?

Thomas, does glxgears work on your setup?
btw, what gpu exactly do you have this bug with?
Comment 7 Thomas Rohloff 2012-12-25 18:37:00 UTC
> does glxgears work on your setup?

I didn't test glxgears and am actually before this commit. Will try glxgears at my next bisecting round (for another bug).

> what gpu exactly do you have this bug with?

Sapphire Radeon HD 6950 (the one with dual BIOS and dual fans) with unlocked shaders (factory BIOS, not modded by me) and most likely with the locked BIOS, too, but there I can't tell really tell cause the GPU crashes right after compiz starts.

> kernel radeon says smth like this

I reported that, too. In fact I reported a few other bugs that seem all to be caused by this (and other) commits:
https://bugs.freedesktop.org/show_bug.cgi?id=58660
https://bugs.freedesktop.org/show_bug.cgi?id=58661
https://bugs.freedesktop.org/show_bug.cgi?id=58667

Help with bisecting is always welcome. :)
Comment 8 Thomas Rohloff 2012-12-25 21:03:57 UTC
> does glxgears work on your setup?

I tested it now and either it runs just fine or crashes the GPU instantly ( https://bugs.freedesktop.org/show_bug.cgi?id=58667 ).
Comment 9 Thomas Rohloff 2012-12-25 21:48:30 UTC
6532eb17baff6e61b427f29e076883f8941ae664 is not the cause of this bug (or damaged the hardware, but let's think positive for now) as I just had the exact same thing with a older mesa version. Also this seems to be connected with all other bug reports I listed above, especially the "GPU fault detected" from here: https://bugs.freedesktop.org/show_bug.cgi?id=58667

I'm still pre-bisecting (searching for a good commit) but as this bug sometimes needs hours to get triggered this may take very long.
Comment 10 Thomas Rohloff 2012-12-25 23:25:42 UTC
I did go back till http://cgit.freedesktop.org/mesa/mesa/commit/?id=6c99f2101fbd3edb7d5899c44ca9d984a3c0f8b6 and the bug is still there (not the crashes directly, at least I couldn't trigger them, but the error messages) so either this bug is really old or it's not a mesa bug (or, but that would be really bad: It damaged the hardware).
Comment 11 Thomas Rohloff 2012-12-25 23:26:34 UTC
Whoops, copy & pasting... The error messages + rendering errors occurred with that old commit.
Comment 12 Thomas Rohloff 2013-12-04 18:36:37 UTC
I didn#t use r600g for some time now (used fglrx instead) but now this finally seems to be fixed! :)


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.