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: Fri, 03 Nov 2017 09:12:07 +0000 [thread overview]
Message-ID: <bug-196197-2300-gUwZX2fZLt@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 #12 from Michel Dänzer (michel@daenzer.net) ---
(In reply to Andreas Brogle from comment #7)
> The last 7 turns caused a kernel panic, all the 4.10.0-rc1 versions. I
> declared them as bad with git bisect.
In cases like this, where it's not possible to test a commit for the problem
being bisected, one needs to run
git bisect skip
instead of "bad".
> 0fc1223f0e77a748f7040562faaa7027f7db71ca is the first bad commit
> commit 0fc1223f0e77a748f7040562faaa7027f7db71ca
> Author: Rajat Jain <rajatja@google.com>
> Date: Mon Jan 2 22:34:10 2017 -0800
>
> PCI/ASPM: Add L1 substate capability structure register definitions
Does this commit boot and exhibit the problem? If so, does the previous commit
boot and not exhibit the problem?
--
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-11-03 9:12 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
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 [this message]
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-gUwZX2fZLt@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.