[Bug 5784] savage DRI: kernel oops when running glxgears in second X.org session

2005-12-30 Thread bugme-daemon
http://bugzilla.kernel.org/show_bug.cgi?id=5784 [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution|

[Bug 5148] [r300] Stale texture data used on first rendering

2005-12-30 Thread bugzilla-daemon
Please do not reply to this email: if you want to comment on the bug, go to the URL shown below and enter yourcomments there. https://bugs.freedesktop.org/show_bug.cgi?id=5148 --- Additional Comments From [EMAIL PROTECTED] 2005-12-30 22:42 ---

[Bug 5784] savage DRI: kernel oops when running glxgears in second X.org session

2005-12-30 Thread bugme-daemon
http://bugzilla.kernel.org/show_bug.cgi?id=5784 --- Additional Comments From [EMAIL PROTECTED] 2005-12-30 02:26 --- I have found out that not the very update to DRM version 1.0.1 keeps Mesa from segfaulting. As a matter of fact, what made the difference for me was loading the

[Bug 5784] savage DRI: kernel oops when running glxgears in second X.org session

2005-12-30 Thread bugme-daemon
http://bugzilla.kernel.org/show_bug.cgi?id=5784 --- Additional Comments From [EMAIL PROTECTED] 2005-12-30 04:14 --- Essentially the same problem occurs after bootig from a Ubuntu 6.04 alpha Live CD. The (modular) X server release is 7.0.0 RC4. The bug is thus not Red Hat specific. I

[Bug 5784] savage DRI: kernel oops when running glxgears in second X.org session

2005-12-30 Thread bugme-daemon
http://bugzilla.kernel.org/show_bug.cgi?id=5784 --- Additional Comments From [EMAIL PROTECTED] 2005-12-30 02:19 --- It is going into the kernel.. I'm just not sure whats changed.. my git tree might have it already in it... the savage driver hasn't moved in 4 months or so...

[Bug 5417] i915: initial scissor rect is empty

2005-12-30 Thread bugzilla-daemon
Please do not reply to this email: if you want to comment on the bug, go to the URL shown below and enter yourcomments there. https://bugs.freedesktop.org/show_bug.cgi?id=5417 [EMAIL PROTECTED] changed: What|Removed |Added

[Bug 5784] savage DRI: kernel oops when running glxgears in second X.org session

2005-12-30 Thread bugme-daemon
http://bugzilla.kernel.org/show_bug.cgi?id=5784 --- Additional Comments From [EMAIL PROTECTED] 2005-12-30 05:08 --- After rebuilding drm.ko and savage.ko from the current DRI snapshot savage-20051220-linux.i386.tar.bz2 and pushing the kernel modules into /lib/modules/`uname

Re: FreeBSD CURRENT + DRM + agp_ati

2005-12-30 Thread Felix Kühling
Am Donnerstag, den 29.12.2005, 20:40 -0500 schrieb Adam K Kirchhoff: [snip] What's really bizarre, however, is that if I set hw.dri.0.debug to 1, glxgears gets roughly 200 FPS, faster than software Mesa, but slower than it can get (undoubtedly due to the massive amounts of debugging

Re: FreeBSD CURRENT + DRM + agp_ati

2005-12-30 Thread Adam K Kirchhoff
Felix Kühling wrote: Am Donnerstag, den 29.12.2005, 20:40 -0500 schrieb Adam K Kirchhoff: [snip] What's really bizarre, however, is that if I set hw.dri.0.debug to 1, glxgears gets roughly 200 FPS, faster than software Mesa, but slower than it can get (undoubtedly due to the massive

DRI card reinitialization after suspend

2005-12-30 Thread Ben Gamari
Howdy all! What is the present status of S3 suspend support in the DRI? I ask because my laptop locks up with a scrambled screen on resume from S3 standby when using the radeon driver with DRI enabled. This is a known problem with the DRI drivers and as such, at least one workaround has be

Re: DRI card reinitialization after suspend

2005-12-30 Thread Benjamin Herrenschmidt
On Fri, 2005-12-30 at 13:27 -0500, Ben Gamari wrote: Howdy all! What is the present status of S3 suspend support in the DRI? I ask because my laptop locks up with a scrambled screen on resume from S3 standby when using the radeon driver with DRI enabled. This is a known problem with the DRI