From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 178421] [regression] Radeon Oops on shutdown
Date: Tue, 25 Oct 2016 03:15:34 +0000 [thread overview]
Message-ID: <bug-178421-2300-pYrWtReShk@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-178421-2300@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=178421
--- Comment #5 from Michel Dänzer <michel@daenzer.net> ---
(In reply to Jouni Mettälä from comment #0)
> I tried to bisect. There was some uncertainity. Still bisect said
> c0d5fb4d0d9224ccaad0475c9b58740873970e7e is the first bad commit.
That's a pure merge commit, so the problem can't really have started at that
commit. In order to avoid getting an incorrect bisection result again:
* Manually apply the patches referenced in comment 1 for each commit where
they're not applied yet
* Test every commit multiple times before marking it as "good"
* Only mark commits as "bad" which show exactly the same symptoms, otherwise
"skip" (for commits which fail to shut down / reboot for other reasons) or
"good"
--
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:[~2016-10-25 3:15 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-19 16:30 [Bug 178421] New: [regression] Radeon Oops on shutdown bugzilla-daemon
2016-10-19 16:34 ` [Bug 178421] " bugzilla-daemon
2016-10-21 0:38 ` bugzilla-daemon
2016-10-24 13:20 ` bugzilla-daemon
2016-10-24 13:27 ` bugzilla-daemon
2016-10-25 3:15 ` bugzilla-daemon [this message]
2016-10-30 11:01 ` bugzilla-daemon
2016-10-30 16:11 ` bugzilla-daemon
2016-10-30 23:49 ` bugzilla-daemon
2016-10-31 16:27 ` bugzilla-daemon
2016-10-31 21:52 ` bugzilla-daemon
2016-11-17 15:34 ` 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-178421-2300-pYrWtReShk@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).