All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 91790] TONGA hang in amdgpu_ring_lock
Date: Thu, 03 Sep 2015 11:46:00 +0000	[thread overview]
Message-ID: <bug-91790-502-EaZPp7jQYl@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-91790-502@http.bugs.freedesktop.org/>


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

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

--- Comment #15 from Andy Furniss <adf.lists@gmail.com> ---
(In reply to Andy Furniss from comment #13)
> (In reply to Mathias Tillman from comment #11)
> > (In reply to Alex Deucher from comment #10)
> > > Created attachment 118056 [details] [review] [review] [review]
> > > possible fix
> > > 
> > > I think this patch should fix it.
> > 
> > No luck here I'm afraid - I'm having a hard time reproducing it during
> > normal desktop usage (with or without the patch), but it did lockup while
> > running Unigine Valley.
> 
> I see drm-next-4.3 is now ahead again, haven't tested that yet.
> 
> With patch + drm-next-4.3-wip, I haven't yet managed to lock valley - but
> I've only had time to do a couple of runs (45 min then 90 min) from a clean
> boot. Maybe later when I've been up a while doing other things I'll try
> harder.
> 
> Patch doesn't apply with git apply - did it by hand.

I managed to lock it, seems that doing "something" between runs changes things,
or first runs are lucky.

FWIW I tried running Unreal 4.5 ElementalDemo after my long runs and I got a
signal 7.

After I later locked/hung valley I rebooted and tried again elemental from a
clean boot and it ran OK, but after quitting. it now gives signal 7 again if I
try to start it.

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

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

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

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

  parent reply	other threads:[~2015-09-03 11:46 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-28  8:49 [Bug 91790] TONGA hang in amdgpu_ring_lock bugzilla-daemon
2015-08-28 10:30 ` bugzilla-daemon
2015-08-28 12:31 ` bugzilla-daemon
2015-08-28 12:46 ` bugzilla-daemon
2015-08-28 12:54 ` bugzilla-daemon
2015-08-28 16:03 ` bugzilla-daemon
2015-08-28 16:07 ` bugzilla-daemon
2015-09-01 18:20 ` bugzilla-daemon
2015-09-01 19:58 ` bugzilla-daemon
2015-09-02  9:15 ` bugzilla-daemon
2015-09-02 20:09 ` bugzilla-daemon
2015-09-02 20:40 ` bugzilla-daemon
2015-09-03  8:56 ` bugzilla-daemon
2015-09-03 10:24 ` bugzilla-daemon
2015-09-03 11:34 ` bugzilla-daemon
2015-09-03 11:46 ` bugzilla-daemon [this message]
2019-11-19  8:06 ` 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-91790-502-EaZPp7jQYl@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.