All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 94081] New: [radeon 3.18 regression] GPU reset recovery fails
Date: Sun, 01 Mar 2015 19:02:03 +0000	[thread overview]
Message-ID: <bug-94081-2300@https.bugzilla.kernel.org/> (raw)

https://bugzilla.kernel.org/show_bug.cgi?id=94081

            Bug ID: 94081
           Summary: [radeon 3.18 regression] GPU reset recovery fails
           Product: Drivers
           Version: 2.5
    Kernel Version: 3.18.x
          Hardware: All
                OS: Linux
              Tree: Mainline
            Status: NEW
          Severity: normal
          Priority: P1
         Component: Video(DRI - non Intel)
          Assignee: drivers_video-dri@kernel-bugs.osdl.org
          Reporter: jan.vesely@rutgers.edu
        Regression: No

starting with kernel-3.18 (fedora version) fails to recover from OpenCL induced
GPU loockup.
reproducer:
Run noise-hurl.xml OpenCL test in gegl library:
[354672.707822] radeon 0000:01:00.0: ring 0 stalled for more than 10020msec

on 3.17 (fedora again) I observe one or two display flashes, and full recovery.

starting with 3.18 I see the flash, and the dispaly stays frozen. the task
itself(gegl) stays in uninteruptible state

Here are the relevant lines from dmesg on 3.18:
[354672.707822] radeon 0000:01:00.0: ring 0 stalled for more than 10020msec
[354672.707828] radeon 0000:01:00.0: GPU lockup (current fence id
0x00000000007778a3 last fence id 0x00000000007778b3 on ring 0)
[354672.828879] radeon 0000:01:00.0: Saved 503 dwords of commands on ring 0.
[354672.828898] radeon 0000:01:00.0: GPU softreset: 0x00000009
[354672.828900] radeon 0000:01:00.0:   GRBM_STATUS               = 0xA0433828
[354672.828902] radeon 0000:01:00.0:   GRBM_STATUS_SE0           = 0x08000007
[354672.828903] radeon 0000:01:00.0:   GRBM_STATUS_SE1           = 0x00000007
[354672.828905] radeon 0000:01:00.0:   SRBM_STATUS               = 0x20000AC0
[354672.828907] radeon 0000:01:00.0:   SRBM_STATUS2              = 0x00000000
[354672.828908] radeon 0000:01:00.0:   R_008674_CP_STALLED_STAT1 = 0x00000000
[354672.828910] radeon 0000:01:00.0:   R_008678_CP_STALLED_STAT2 = 0x00018000
[354672.828912] radeon 0000:01:00.0:   R_00867C_CP_BUSY_STAT     = 0x00010002
[354672.828913] radeon 0000:01:00.0:   R_008680_CP_STAT          = 0x80038647
[354672.828915] radeon 0000:01:00.0:   R_00D034_DMA_STATUS_REG   = 0x44C83D57
[354672.842214] radeon 0000:01:00.0: GRBM_SOFT_RESET=0x00007F6B
[354672.842267] radeon 0000:01:00.0: SRBM_SOFT_RESET=0x00000100
[354672.843423] radeon 0000:01:00.0:   GRBM_STATUS               = 0x00003828
[354672.843425] radeon 0000:01:00.0:   GRBM_STATUS_SE0           = 0x00000007
[354672.843426] radeon 0000:01:00.0:   GRBM_STATUS_SE1           = 0x00000007
[354672.843428] radeon 0000:01:00.0:   SRBM_STATUS               = 0x200000C0
[354672.843429] radeon 0000:01:00.0:   SRBM_STATUS2              = 0x00000000
[354672.843431] radeon 0000:01:00.0:   R_008674_CP_STALLED_STAT1 = 0x00000000
[354672.843432] radeon 0000:01:00.0:   R_008678_CP_STALLED_STAT2 = 0x00000000
[354672.843434] radeon 0000:01:00.0:   R_00867C_CP_BUSY_STAT     = 0x00000000
[354672.843435] radeon 0000:01:00.0:   R_008680_CP_STAT          = 0x00000000
[354672.843437] radeon 0000:01:00.0:   R_00D034_DMA_STATUS_REG   = 0x44C83D57
[354672.843456] radeon 0000:01:00.0: GPU reset succeeded, trying to resume
[354672.865723] [drm] enabling PCIE gen 2 link speeds, disable with
radeon.pcie_gen2=0
[354672.868296] [drm] PCIE GART of 1024M enabled (table at 0x0000000000274000).
[354672.868388] radeon 0000:01:00.0: WB enabled
[354672.868390] radeon 0000:01:00.0: fence driver on ring 0 use gpu addr
0x0000000040000c00 and cpu addr 0xffff880401c54c00
[354672.868391] radeon 0000:01:00.0: fence driver on ring 3 use gpu addr
0x0000000040000c0c and cpu addr 0xffff880401c54c0c
[354672.869865] radeon 0000:01:00.0: fence driver on ring 5 use gpu addr
0x0000000000072118 and cpu addr 0xffffc900062b2118
[354672.886233] [drm] ring test on 0 succeeded in 3 usecs
[354672.886244] [drm] ring test on 3 succeeded in 7 usecs
[354673.063433] [drm] ring test on 5 succeeded in 2 usecs
[354673.063441] [drm] UVD initialized successfully.
[354673.187403] [drm] ib test on ring 0 succeeded in 0 usecs
[354673.187432] [drm] ib test on ring 3 succeeded in 0 usecs

-- 
You are receiving this mail because:
You are watching the assignee of the bug.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel

             reply	other threads:[~2015-03-01 19:02 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-01 19:02 bugzilla-daemon [this message]
2015-03-01 19:05 ` [Bug 94081] [radeon 3.18 regression] GPU reset recovery fails bugzilla-daemon
2015-03-02  6:58 ` bugzilla-daemon
2015-03-04 21:10 ` bugzilla-daemon
2015-03-05  1:12 ` bugzilla-daemon

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=bug-94081-2300@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@bugzilla.kernel.org \
    --cc=dri-devel@lists.freedesktop.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.