From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 85491] radeon 0000:01:00.0: Fatal error during GPU init
Date: Wed, 26 Nov 2014 03:32:38 +0000 [thread overview]
Message-ID: <bug-85491-2300-g2fkYPTdlh@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-85491-2300@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=85491
--- Comment #16 from Michel Dänzer <michel@daenzer.net> ---
(In reply to Marek from comment #15)
> The result of bisection is that the first bad commit is:
>
> e5558d1a516fa6924fa8d53152b665d4c26f142e Merge branches 'dma-api',
> 'pci/virtualization', 'pci/msi', 'pci/misc' and 'pci/resource' into next
In general, if the result of a bisection is a merge commit, it indicates
something might have gone wrong during the bisection. In this case, I suspect
the problem might not happen every time even with affected kernels, so you need
to test several times before declaring a commit good.
You can double-check this by testing commit
e5558d1a516fa6924fa8d53152b665d4c26f142e again several times. Does it happen
every time? If yes, test its parent commit(s) again several times. Does it
never happen? If the answer to either question is no, I'm afraid you need to
start the bisection again.
--
You are receiving this mail because:
You are watching the assignee of the bug.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2014-11-26 3:32 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-02 21:36 [Bug 85491] New: radeon 0000:01:00.0: Fatal error during GPU init bugzilla-daemon
2014-10-02 21:36 ` [Bug 85491] " bugzilla-daemon
2014-10-02 21:37 ` bugzilla-daemon
2014-10-02 21:37 ` bugzilla-daemon
2014-10-02 21:38 ` bugzilla-daemon
2014-10-02 21:43 ` bugzilla-daemon
2014-10-03 5:06 ` bugzilla-daemon
2014-10-03 13:30 ` bugzilla-daemon
2014-10-04 15:06 ` bugzilla-daemon
2014-10-04 15:07 ` bugzilla-daemon
2014-10-04 15:08 ` bugzilla-daemon
2014-11-11 19:43 ` bugzilla-daemon
2014-11-11 19:44 ` bugzilla-daemon
2014-11-11 19:45 ` bugzilla-daemon
2014-11-13 3:35 ` bugzilla-daemon
2014-11-17 15:35 ` bugzilla-daemon
2014-11-25 10:21 ` bugzilla-daemon
2014-11-26 3:32 ` bugzilla-daemon [this message]
2014-11-26 3:52 ` bugzilla-daemon
2014-11-27 7:58 ` bugzilla-daemon
2014-12-03 21:36 ` 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-85491-2300-g2fkYPTdlh@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.