From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 196635] amdgpu clinfo hangs with SI
Date: Wed, 16 Aug 2017 06:17:21 +0000 [thread overview]
Message-ID: <bug-196635-2300-zDJtjFuQls@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-196635-2300@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=196635
--- Comment #10 from Michel Dänzer (michel@daenzer.net) ---
(In reply to Janpieter Sollie from comment #9)
> It won't be easy to point to the problem: in 4.10, it hit a triple fault and
> then crashed with dpm enabled. do you want a bisection from that one(see
> 194899) to the current status or do I need to do something else?
Hmm, I guess I misread the bug description as meaning it worked properly
before. If that's not the case, there's probably no point in bisecting.
--
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
next prev parent reply other threads:[~2017-08-16 6:17 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-10 15:13 [Bug 196635] New: amdgpu clinfo hangs with SI bugzilla-daemon
2017-08-10 15:14 ` [Bug 196635] " bugzilla-daemon
2017-08-10 16:33 ` bugzilla-daemon
2017-08-11 3:31 ` bugzilla-daemon
2017-08-11 3:33 ` bugzilla-daemon
2017-08-11 3:35 ` bugzilla-daemon
2017-08-11 3:37 ` bugzilla-daemon
2017-08-14 10:07 ` bugzilla-daemon
2017-08-15 6:14 ` bugzilla-daemon
2017-08-15 6:25 ` bugzilla-daemon
2017-08-16 5:34 ` bugzilla-daemon
2017-08-16 6:17 ` bugzilla-daemon [this message]
2017-08-22 11:33 ` bugzilla-daemon
2017-08-23 1:20 ` bugzilla-daemon
2017-08-25 3:57 ` 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-196635-2300-zDJtjFuQls@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox