Bug 58372 - [KMS][Cayman] Garbled screen and gpu crash with 6950 with drm-next
Summary: [KMS][Cayman] Garbled screen and gpu crash with 6950 with drm-next
Status: RESOLVED FIXED
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Radeon (show other bugs)
Version: XOrg git
Hardware: Other All
: medium normal
Assignee: Default DRI bug account
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-12-16 18:15 UTC by Serkan Hosca
Modified: 2013-03-11 15:48 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments
dmesg with drm-next (276.15 KB, text/plain)
2012-12-16 18:15 UTC, Serkan Hosca
no flags Details
dmesg with linus git (63.98 KB, text/plain)
2012-12-16 18:16 UTC, Serkan Hosca
no flags Details
dmesg with drm-fixes-3.8 (83.31 KB, text/plain)
2012-12-21 01:40 UTC, Serkan Hosca
no flags Details
dmesg with linus rc3 drm-fixes-3.8 as of jan 13 before crash (310.42 KB, text/plain)
2013-01-13 05:42 UTC, Serkan Hosca
no flags Details

Description Serkan Hosca 2012-12-16 18:15:30 UTC
Created attachment 71594 [details]
dmesg with drm-next

Using linus + airlied's drm-next produces garbled screen and gpu crashes after login.

Using mesa git and xf86-ati git.
Comment 1 Serkan Hosca 2012-12-16 18:16:03 UTC
Created attachment 71595 [details]
dmesg with linus git
Comment 2 Serkan Hosca 2012-12-16 18:20:53 UTC
Forgot to add, using lightdm + cinnamon on arch
Comment 3 Alexandre Demers 2012-12-16 21:32:22 UTC
If you can, could you bisect?
Comment 4 Serkan Hosca 2012-12-16 23:32:20 UTC
bisect result:

0d0b3e7443bed6b49cb90fe7ddc4b5578a83a88d is the first bad commit
commit 0d0b3e7443bed6b49cb90fe7ddc4b5578a83a88d
Author: Jerome Glisse <jglisse@redhat.com>
Date:   Wed Nov 28 13:47:55 2012 -0500

    drm/radeon: use cached memory when evicting for vram on non agp
    
    Force the use of cached memory when evicting from vram on non agp
    hardware. Also force write combine on agp hw. This is to insure
    the minimum cache type change when allocating memory and improving
    memory eviction especialy on pci/pcie hw.
    
    Signed-off-by: Jerome Glisse <jglisse@redhat.com>

:040000 040000 c917ebaa086f5efea9928e707d97bdb90ef6919935d6eaaa7b1115d9e3696c200da139695c19ad15 M     drivers
Comment 6 Serkan Hosca 2012-12-17 02:42:42 UTC
(In reply to comment #5)
> Does your kernel tree have this patch?
> http://cgit.freedesktop.org/~airlied/linux/commit/drivers/gpu/drm/radeon/
> radeon_object.c?h=drm-next&id=dd54fee7d440c4a9756cce2c24a50c15e4c17ccb

Yea i have that commit.
Comment 7 Serkan Hosca 2012-12-21 01:40:07 UTC
Created attachment 71883 [details]
dmesg with drm-fixes-3.8

The dmesg message changed after merging in drm-fixes-3.8:

[drm:evergreen_vm_reg_valid] *ERROR* Invalid register 0x8040 in CS
Comment 8 Alex Deucher 2012-12-21 01:51:47 UTC
(In reply to comment #7)
> Created attachment 71883 [details]
> dmesg with drm-fixes-3.8
> 
> The dmesg message changed after merging in drm-fixes-3.8:
> 
> [drm:evergreen_vm_reg_valid] *ERROR* Invalid register 0x8040 in CS

That's a different bug.  Please file a new one for that.  what you are seeing is due to a change in mesa:
http://cgit.freedesktop.org/mesa/mesa/commit/?id=24b1206ab2dcd506aaac3ef656aebc8bc20cd27a
Comment 9 Alexandre Demers 2012-12-22 18:59:36 UTC
(In reply to comment #8)
> (In reply to comment #7)
> > Created attachment 71883 [details]
> > dmesg with drm-fixes-3.8
> > 
> > The dmesg message changed after merging in drm-fixes-3.8:
> > 
> > [drm:evergreen_vm_reg_valid] *ERROR* Invalid register 0x8040 in CS
> 
> That's a different bug.  Please file a new one for that.  what you are
> seeing is due to a change in mesa:
> http://cgit.freedesktop.org/mesa/mesa/commit/
> ?id=24b1206ab2dcd506aaac3ef656aebc8bc20cd27a

Opening it, I'm hitting the same bug.
Comment 10 Serkan Hosca 2012-12-22 21:35:23 UTC
(In reply to comment #9)
> (In reply to comment #8)
> > (In reply to comment #7)
> > > Created attachment 71883 [details]
> > > dmesg with drm-fixes-3.8
> > > 
> > > The dmesg message changed after merging in drm-fixes-3.8:
> > > 
> > > [drm:evergreen_vm_reg_valid] *ERROR* Invalid register 0x8040 in CS
> > 
> > That's a different bug.  Please file a new one for that.  what you are
> > seeing is due to a change in mesa:
> > http://cgit.freedesktop.org/mesa/mesa/commit/
> > ?id=24b1206ab2dcd506aaac3ef656aebc8bc20cd27a
> 
> Opening it, I'm hitting the same bug.

You need this:
http://cgit.freedesktop.org/~agd5f/linux/commit/?h=drm-fixes-3.8&id=668bbc81baf0f34df832d8aca5c7d5e19a493c68
Comment 11 Serkan Hosca 2013-01-13 05:34:37 UTC
No change with linus git rc3 as of today + drm-fixes-3.8  with mesa at e09a5846cdab01a3bf04ac8c11e352d85b89b4af and -ati at 102ee4a24e4c9ba0c0b65d3ca8599dc7e0216c1e. It floods the dmesg after login and computer freezes.

I tried switching to gdm but i dont't even get to the login screen, computer freezes.

I tried openbox, i was able to login and ran glxgears, some 3d screensavers but the computer froze when i tried some webgl demos. I saw a couple of:
radeon: The kernel rejected CS, see dmesg for more information
in the terminal and the same dmesg flood and the computer freezes.
Comment 12 Serkan Hosca 2013-01-13 05:42:14 UTC
Created attachment 72948 [details]
dmesg with linus rc3 drm-fixes-3.8 as of jan 13 before crash
Comment 13 Serkan Hosca 2013-03-11 15:48:03 UTC
This is fixed with 3.8 release and mesa git master


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.