All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 108898] GPU hangs with GfxBench Manhattan GL tests
Date: Thu, 29 Nov 2018 11:36:19 +0000	[thread overview]
Message-ID: <bug-108898-502@http.bugs.freedesktop.org/> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 1667 bytes --]

https://bugs.freedesktop.org/show_bug.cgi?id=108898

            Bug ID: 108898
           Summary: GPU hangs with GfxBench Manhattan GL tests
           Product: Mesa
           Version: git
          Hardware: Other
                OS: All
            Status: NEW
          Severity: normal
          Priority: medium
         Component: Drivers/Gallium/radeonsi
          Assignee: dri-devel@lists.freedesktop.org
          Reporter: eero.t.tamminen@intel.com
        QA Contact: dri-devel@lists.freedesktop.org

Setup:
- FullHD monitor (through HDMI KVM)
- HadesCanyon KBL i7-8809G ([AMD/ATI] Vega [Radeon RX Vega M] (rev c0))
- Ubuntu 18.04
- drm-tip git kernel v4.20-rc4 (i.e. kernel.org v4.20-rc4 kernel + latest drm
code from yesterday)
- Mesa git (c120dbfe4d) with AMD VEGAM renderer
- X server git version
- Proprietary GfxBench v5, but public GfxBench v4 should have same tests:
  http://gfxbench.com

Test-cases:
* Manhattan 3.0 offscreen:
  bin/testfw_app --gfx glfw --gl_api desktop_core --width 1920 --height 1080
--fullscreen 1 --test_id gl_manhattan_off
* Manhattan 3.1 onscreen:
  bin/testfw_app --gfx glfw --gl_api desktop_core --width 1920 --height 1080
--fullscreen 1 --test_id gl_manhattan31

Expected outcome:
* No GPU timeouts

Actual outcome:
* 1 out of 3 runs gives in dmesg:
[ 2817.689624] [drm:drm_sched_job_timedout [gpu_sched]] *ERROR* ring gfx
timeout, but soft recovered

NOTE: These were happening already when we started testing this machine in mid
October, with Mesa 18cc65edf8480 & drm-tip kernel v4.19-rc8.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 3072 bytes --]

[-- Attachment #2: Type: text/plain, Size: 160 bytes --]

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

             reply	other threads:[~2018-11-29 11:36 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-29 11:36 bugzilla-daemon [this message]
2018-11-30 13:40 ` [Bug 108898] (Recoverable) GPU hangs with GfxBench Manhattan GL tests bugzilla-daemon
2018-12-13 12:09 ` bugzilla-daemon
2019-01-03 16:20 ` bugzilla-daemon
2019-02-07  9:33 ` bugzilla-daemon
2019-03-06 12:09 ` bugzilla-daemon
2019-03-22 11:18 ` bugzilla-daemon
2019-05-09 14:23 ` bugzilla-daemon
2019-05-17 11:45 ` bugzilla-daemon
2019-09-17 10:16 ` bugzilla-daemon
2019-09-25 18:31 ` bugzilla-daemon
2019-11-07 13:53 ` 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-108898-502@http.bugs.freedesktop.org/ \
    --to=bugzilla-daemon@freedesktop.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.