From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 34313] RV770 lock-up with OpenGL
Date: Fri, 27 May 2011 16:01:34 -0700 (PDT) [thread overview]
Message-ID: <20110527230134.90A1313004F@annarchy.freedesktop.org> (raw)
In-Reply-To: <bug-34313-502@http.bugs.freedesktop.org/>
https://bugs.freedesktop.org/show_bug.cgi?id=34313
--- Comment #24 from Bob Ham <rah@bash.sh> 2011-05-27 16:01:34 PDT ---
In the previously described bisect, I failed to mention that the tree had been
restricted to drivers/gpu/drm/radeon. Using the log of that bisect as a
starting point for a bisect of the whole tree, I arrived at the following,
similar report:
There are only 'skip'ped commits left to test.
The first bad commit could be any of:
b7ae5056c94a8191c1fd0b5697707377516c0c5d
c9220b0f7cbd1d2272426aa81a72ae2f6582bb71
We cannot bisect more!
The first is the same skipped (weird timing out kernel) commit as the
restricted bisect but the second possibility is different and from TTM:
Merge branch 'drm-fixes' of /home/airlied/kernel/linux-2.6 into drm-core-next
http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=b7ae5056c94a8191c1fd0b5697707377516c0c5d
drm/ttm: add unlocked variant of new manager put node.
http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=c9220b0f7cbd1d2272426aa81a72ae2f6582bb71
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
next prev parent reply other threads:[~2011-05-27 23:01 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-15 23:38 [Bug 34313] New: RV770 lock-up with OpenGL bugzilla-daemon
2011-02-15 23:39 ` [Bug 34313] " bugzilla-daemon
2011-02-15 23:39 ` bugzilla-daemon
2011-02-15 23:40 ` bugzilla-daemon
2011-02-15 23:43 ` bugzilla-daemon
2011-02-16 1:15 ` bugzilla-daemon
2011-02-16 23:57 ` bugzilla-daemon
2011-02-16 23:58 ` bugzilla-daemon
2011-02-16 23:58 ` bugzilla-daemon
2011-02-16 23:59 ` bugzilla-daemon
2011-02-16 23:59 ` bugzilla-daemon
2011-02-21 18:52 ` bugzilla-daemon
2011-02-21 19:02 ` bugzilla-daemon
2011-03-31 18:56 ` bugzilla-daemon
2011-03-31 19:16 ` bugzilla-daemon
2011-04-11 13:00 ` bugzilla-daemon
2011-04-11 13:03 ` bugzilla-daemon
2011-04-25 17:01 ` bugzilla-daemon
2011-05-16 15:07 ` bugzilla-daemon
2011-05-16 15:18 ` bugzilla-daemon
2011-05-16 22:36 ` bugzilla-daemon
2011-05-22 2:55 ` bugzilla-daemon
2011-05-22 16:09 ` bugzilla-daemon
2011-05-22 17:01 ` bugzilla-daemon
2011-05-27 16:47 ` bugzilla-daemon
2011-05-27 16:50 ` bugzilla-daemon
2011-05-27 23:01 ` bugzilla-daemon [this message]
2012-11-02 14:41 ` bugzilla-daemon
2012-11-02 14:47 ` bugzilla-daemon
2019-11-19 8:18 ` 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=20110527230134.90A1313004F@annarchy.freedesktop.org \
--to=bugzilla-daemon@freedesktop.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).