All of lore.kernel.org
 help / color / mirror / Atom feed
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: Tue, 27 Jun 2017 17:24:21 +0000	[thread overview]
Message-ID: <bug-196197-2300-grmZvi4Zn8@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 #2 from Andreas Brogle (anbro@ok.de) ---
Hello,

Sorry, I've read the git dokumentation half the day, anyway I don't understand
how bisect works and how to use it.

Is the following what you need ?

# 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


What I have done is downloading from
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/
the original kernel sources, compiled them and tested them
4.12-rc7 (bad)
4.11-rc1 (bad)
4.10-rc8 (good)

The bug arises with 4.11 and still persists in 4.12, so as I assumed the step
from 4.10 to 4.11 should be eamined.

Thanks,
Andreas

-- 
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-06-27 17:24 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 [this message]
2017-06-29  2:44 ` bugzilla-daemon
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-grmZvi4Zn8@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.