All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Michel Dänzer" <michel@daenzer.net>
To: Andy Lutomirski <luto@amacapital.net>
Cc: xorg-driver-ati@lists.x.org, DRI <dri-devel@lists.freedesktop.org>
Subject: Re: Radeon lockup on 3.8.5-201.fc18.x86_64
Date: Tue, 23 Apr 2013 07:55:04 +0200	[thread overview]
Message-ID: <1366696504.27050.93.camel@thor.local> (raw)
In-Reply-To: <CALCETrX6oPf0zLzoU4wjkUjpP8DLoV-Z9+dnH1=J_fu-3Pap7g@mail.gmail.com>

On Mon, 2013-04-22 at 16:19 -0700, Andy Lutomirski wrote: 
> On Thu, Apr 18, 2013 at 2:12 PM, Alex Deucher <alexdeucher@gmail.com> wrote:
> > On Thu, Apr 18, 2013 at 5:11 PM, Andy Lutomirski <luto@amacapital.net> wrote:
> >> On Mon, Apr 8, 2013 at 7:01 AM, Alex Deucher <alexdeucher@gmail.com> wrote:
> >>> On Fri, Apr 5, 2013 at 5:11 PM, Andy Lutomirski <luto@amacapital.net> wrote:
> >>>> Every day or so, I'll click something and my screens go blank for a
> >>>> second or two.  dmesg complains about a lockup, and afterwards
> >>>> everything is painfully slow.  (Even switching focus to other emacs
> >>>> windows takes a second or two.)  Once this happens, if I restart X, I
> >>>> get a blank screen, although the mouse still works and I can switch
> >>>> VTs and use the console.
> >>>
> >>> Try disabling hyperZ.  Set env var R600_HYPERZ=0 (mesa 9.1) or
> >>> R600_DEBUG=nohyperz (mesa git).
> >>
> >> It lasted longer.  I have both of those environment variables set on
> >> the Xorg process but not on clients.  Do  I need it everywhere?
> >
> > For anything that uses the 3D driver.
> 
> This didn't appear to fix it, although it may have fixed some
> graphical glitches in gmail's compose window.

Seems rather unlikely that's directly related to HyperZ, but who knows.


> [350788.530966] radeon 0000:08:00.0: GPU lockup CP stall for more than 40769msec
> [350788.530970] radeon 0000:08:00.0: GPU lockup (waiting for
> 0x000000000000178f last fence id 0x000000000000178e)
> [350788.532047] radeon 0000:08:00.0: Saved 103 dwords of commands on ring 0.
> [350788.532051] radeon 0000:08:00.0: GPU softreset: 0x00000003
> [350788.547792] radeon 0000:08:00.0:   GRBM_STATUS               = 0xA0003828
> [350788.547794] radeon 0000:08:00.0:   GRBM_STATUS_SE0           = 0x00000007
> [350788.547797] radeon 0000:08:00.0:   GRBM_STATUS_SE1           = 0x00000007
> [350788.547799] radeon 0000:08:00.0:   SRBM_STATUS               = 0x200000C0
> [350788.547802] radeon 0000:08:00.0:   R_008674_CP_STALLED_STAT1 = 0x00000000
> [350788.547805] radeon 0000:08:00.0:   R_008678_CP_STALLED_STAT2 = 0x00000000
> [350788.547807] radeon 0000:08:00.0:   R_00867C_CP_BUSY_STAT     = 0x00000004
> [350788.547810] radeon 0000:08:00.0:   R_008680_CP_STAT          = 0x80008647
> [350788.547811] radeon 0000:08:00.0:   GRBM_SOFT_RESET=0x00007F6B
> [350788.547866] radeon 0000:08:00.0:   GRBM_STATUS               = 0x00003828
> [350788.547869] radeon 0000:08:00.0:   GRBM_STATUS_SE0           = 0x00000007
> [350788.547872] radeon 0000:08:00.0:   GRBM_STATUS_SE1           = 0x00000007
> [350788.547874] radeon 0000:08:00.0:   SRBM_STATUS               = 0x200000C0
> [350788.547877] radeon 0000:08:00.0:   R_008674_CP_STALLED_STAT1 = 0x00000000
> [350788.547879] radeon 0000:08:00.0:   R_008678_CP_STALLED_STAT2 = 0x00000000
> [350788.547882] radeon 0000:08:00.0:   R_00867C_CP_BUSY_STAT     = 0x00000000
> [350788.547884] radeon 0000:08:00.0:   R_008680_CP_STAT          = 0x00000000
> [350788.565361] radeon 0000:08:00.0: GPU reset succeeded, trying to resume
> [350788.583801] [drm] probing gen 2 caps for device 8086:1d1a = 2/0
> [350788.583807] [drm] enabling PCIE gen 2 link speeds, disable with
> radeon.pcie_gen2=0
> [350788.590840] [drm] PCIE GART of 512M enabled (table at 0x0000000000040000).
> [350788.590976] radeon 0000:08:00.0: WB enabled
> [350788.590978] radeon 0000:08:00.0: fence driver on ring 0 use gpu
> addr 0x0000000040000c00 and cpu addr 0xffff880442f58c00
> [350788.590979] radeon 0000:08:00.0: fence driver on ring 3 use gpu
> addr 0x0000000040000c0c and cpu addr 0xffff880442f58c0c
> [350788.607480] [drm] ring test on 0 succeeded in 2 usecs
> [350788.607560] [drm] ring test on 3 succeeded in 1 usecs
> [350788.615053] [drm] ib test on ring 0 succeeded in 0 usecs
> [350788.615133] [drm] ib test on ring 3 succeeded in 1 usecs
> 
> I'm not convinced there's an actual hang.  40 seconds is a long time,
> and I've only ever seen this when clicking something, and when this
> happens, the screen goes blank immediately (not after a 40 second
> delay).

Hmm, now that you mention this, I notice in your original report it
claims that the CP stalled for 'more than 5102593msec', which is clearly
bogus. Looks like something's wrong with the lockup detection. 
Did this start after a kernel update or something like that?


-- 
Earthling Michel Dänzer           |                   http://www.amd.com
Libre software enthusiast         |          Debian, X and DRI developer
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel

  reply	other threads:[~2013-04-23  5:55 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-05 21:11 Radeon lockup on 3.8.5-201.fc18.x86_64 Andy Lutomirski
2013-04-08 14:01 ` Alex Deucher
2013-04-18 21:11   ` Andy Lutomirski
     [not found]     ` <CALCETrVEF5eR0kdWFP32GXeQCSnDp-5CBZU=UQyJ8L1LZAk+ww-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-04-18 21:12       ` Alex Deucher
     [not found]         ` <CADnq5_MuMipJNeBRMMuCyu=-tga7yACCS89MAgHr5XW=wjHjSw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-04-22 23:19           ` Andy Lutomirski
2013-04-23  5:55             ` Michel Dänzer [this message]
     [not found]               ` <1366696504.27050.93.camel-2h6evNeVVYGs1BDpvl8NfQ@public.gmane.org>
2013-04-23 17:08                 ` Andy Lutomirski
2013-04-23 17:15                   ` Michel Dänzer
     [not found]                     ` <1366737313.27050.181.camel-2h6evNeVVYGs1BDpvl8NfQ@public.gmane.org>
2013-04-23 19:31                       ` Andy Lutomirski
     [not found]                         ` <CALCETrWZpCH7tWGAHJ2PePHFivXmj8B1rxMRzJh+c27=Fz5+3w-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-06-11 23:23                           ` [PATCH] radeon: Fix a false positive lockup after 10s of inactivity Andy Lutomirski
     [not found]                             ` <abba1962f03200b03c3deb16bd3e690393f4596e.1370992898.git.luto-kltTT9wpgjJwATOyAt5JVQ@public.gmane.org>
2013-06-12 10:26                               ` Michel Dänzer
2013-06-12 11:20                                 ` Christian König
2013-06-12 13:56                                 ` Jerome Glisse
2013-06-13 21:22                                   ` Andy Lutomirski
     [not found]                                     ` <CALCETrV_UsTiGNOmQ7BiO7mHAb3UaiPsWG_7X7HyMJ33SbNq0A-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-06-18 18:12                                       ` Andy Lutomirski

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1366696504.27050.93.camel@thor.local \
    --to=michel@daenzer.net \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=luto@amacapital.net \
    --cc=xorg-driver-ati@lists.x.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.