From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 196197] [drm:r600_ring_test [radeon]] *ERROR* radeon: ring 0 test failed (scratch(0x8504)=0xCAFEDEAD)
Date: Thu, 29 Jun 2017 02:44:04 +0000 [thread overview]
Message-ID: <bug-196197-2300-ZgcdIYMw14@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-196197-2300@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=196197
--- Comment #3 from Michel Dänzer (michel@daenzer.net) ---
(In reply to Andreas Brogle from comment #2)
> # git bisect log
> git bisect start
> # bad: [c1ae3cfa0e89fa1a7ecc4c99031f5e9ae99d9201] Linux 4.11-rc1
> git bisect bad c1ae3cfa0e89fa1a7ecc4c99031f5e9ae99d9201
> # good: [7089db84e356562f8ba737c29e472cc42d530dbc] Linux 4.10-rc8
> git bisect good 7089db84e356562f8ba737c29e472cc42d530dbc
That's just the start of bisecting. Now you need to keep testing the kernel
built from the next commit checked out by git bisect. If the ring test failure
happens, run "git bisect bad". If it doesn't happen and the GPU works normally
after bootup, run "git bisect good". If anything else happens, e.g. the
compiled kernel doesn't boot at all, run "git bisect skip". After repeating
this a number (normally about tens) of times, git bisect will either specify
the first bad commit or the minimum range of candidates.
--
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-06-29 2:44 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-27 8:53 [Bug 196197] New: [drm:r600_ring_test [radeon]] *ERROR* radeon: ring 0 test failed (scratch(0x8504)=0xCAFEDEAD) bugzilla-daemon
2017-06-27 8:59 ` [Bug 196197] " bugzilla-daemon
2017-06-27 17:24 ` bugzilla-daemon
2017-06-29 2:44 ` bugzilla-daemon [this message]
2017-06-29 9:26 ` bugzilla-daemon
2017-06-29 9:45 ` bugzilla-daemon
2017-06-30 7:41 ` bugzilla-daemon
2017-06-30 14:09 ` bugzilla-daemon
2017-07-13 17:42 ` bugzilla-daemon
2017-07-17 15:16 ` bugzilla-daemon
2017-07-21 12:38 ` bugzilla-daemon
2017-11-02 19:34 ` bugzilla-daemon
2017-11-03 9:12 ` bugzilla-daemon
2017-12-19 16:51 ` bugzilla-daemon
2017-12-19 20:19 ` bugzilla-daemon
2017-12-19 21:13 ` bugzilla-daemon
2017-12-20 10:44 ` bugzilla-daemon
2017-12-20 11:14 ` bugzilla-daemon
2018-01-18 18:43 ` 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-196197-2300-ZgcdIYMw14@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;
as well as URLs for NNTP newsgroup(s).