From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.sourceforge.net
Subject: [Bug 35192] BUG() in radeon driver with ATI Technologies Inc RV515 [Radeon X1300]
Date: Mon, 16 May 2011 23:38:39 GMT [thread overview]
Message-ID: <201105162338.p4GNcd5C012979@demeter1.kernel.org> (raw)
In-Reply-To: <bug-35192-2300@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=35192
--- Comment #1 from Anthony Basile <blueness@gentoo.org> 2011-05-16 23:38:38 ---
Bisecting shows that reverting 737a3bb9416ce2a7c7a4170852473a4fcc9c67e8 fixed
the problem. The patch is in comment 28 of the Gentoo bug report.
--
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
------------------------------------------------------------------------------
Achieve unprecedented app performance and reliability
What every C/C++ and Fortran developer should know.
Learn how Intel has extended the reach of its next-generation tools
to help boost performance applications - inlcuding clusters.
http://p.sf.net/sfu/intel-dev2devmay
--
_______________________________________________
Dri-devel mailing list
Dri-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dri-devel
next prev parent reply other threads:[~2011-05-16 23:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-16 0:02 [Bug 35192] New: BUG() in radeon driver with ATI Technologies Inc RV515 [Radeon X1300] bugzilla-daemon
2011-05-16 23:38 ` bugzilla-daemon [this message]
2011-05-18 21:53 ` [Bug 35192] " bugzilla-daemon
2011-05-18 22:56 ` bugzilla-daemon
2011-05-18 22:58 ` bugzilla-daemon
2011-05-19 14:05 ` bugzilla-daemon
2011-05-19 18:16 ` bugzilla-daemon
2011-07-05 10:31 ` bugzilla-daemon
2012-06-13 15:05 ` bugzilla-daemon
2012-06-13 15:06 ` 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=201105162338.p4GNcd5C012979@demeter1.kernel.org \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=dri-devel@lists.sourceforge.net \
/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.