All of lore.kernel.org
 help / color / mirror / Atom feed
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: Thu, 27 Nov 2014 07:58:59 +0000	[thread overview]
Message-ID: <bug-85491-2300-Ulu0NZ5Cxd@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 #18 from Marek <kordikmarek@gmail.com> ---
It seemd weird also to me, that result of the bisect was a merge so I tried to
build one of parents of this wrong merge commit (before Michael's comment) and
then I was merging to the parent the other parents one by one:

Parent: 518a6a34f645897ec3440e5cbcf53ced3493ee1c - good - I startded with this
one
Parent: 14574674e461077a9f4dd5eae050f622e8b8c084 - good - I merged this to the
commit above
Parent: 3cb30b73ad71b384c6289243d4ccd31ab90bce6f - good - I merged this to the
commit above
Parent: 034cd97ebda4062eb4402a6cf963ccd262caa86a - good - I merged this to the
commit above
Parent: 9edbcd2252b5ef148177c9f2c11a56469cf5db52 - good - I merged this to the
commit above
Parent: 67d29b5c6c40e91b124695e9250c2fd24915e24a - bad

After Dave's comment I decided to merge commit
67d29b5c6c40e91b124695e9250c2fd24915e24a as the last. Based on this I think
that it is possible that the commit we are looking for is one of commits
between 67d29b5c6c40e91b124695e9250c2fd24915e24a and
0b2d70764bb39242dcc49c0ebd10fcb8258ce5fa

-- 
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

  parent reply	other threads:[~2014-11-27  7:59 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
2014-11-26  3:52 ` bugzilla-daemon
2014-11-27  7:58 ` bugzilla-daemon [this message]
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-Ulu0NZ5Cxd@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.