All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 196247] AMD FirePro W5130M - Radeon driver - ring 0 stalled
Date: Sun, 02 Jul 2017 14:12:02 +0000	[thread overview]
Message-ID: <bug-196247-2300-1s02Vo5YHQ@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-196247-2300@https.bugzilla.kernel.org/>

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

Mathias (mat42x@yahoo.de) changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
 Attachment #257291|0                           |1
        is obsolete|                            |

--- Comment #3 from Mathias (mat42x@yahoo.de) ---
Created attachment 257293
  --> https://bugzilla.kernel.org/attachment.cgi?id=257293&action=edit
Output of sudo lspvi -vvv

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

  parent reply	other threads:[~2017-07-02 14:12 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-02 13:49 [Bug 196247] New: AMD FirePro W5130M (Dell 3510 notebook) - radeon driver - ring 0 stalled bugzilla-daemon
2017-07-02 13:51 ` [Bug 196247] " bugzilla-daemon
2017-07-02 13:51 ` bugzilla-daemon
2017-07-02 13:55 ` bugzilla-daemon
2017-07-02 13:56 ` [Bug 196247] AMD FirePro W5130M - Radeon " bugzilla-daemon
2017-07-02 14:10 ` bugzilla-daemon
2017-07-02 14:12 ` bugzilla-daemon [this message]
2017-07-04 22:16 ` bugzilla-daemon
2017-10-23 15:26 ` bugzilla-daemon
2017-10-23 16:32 ` bugzilla-daemon
2020-02-28 22:26 ` 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-196247-2300-1s02Vo5YHQ@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.