[Bug 15444] Draw polygon has one pixel bias if PolygonMode is GL_LINE)

http://bugs.freedesktop.org/show_bug.cgi?id=15444 --- Comment #2 from WuNian <[EMAIL PROTECTED]> 2008-04-13 22:44:47 PST --- Created an attachment (id=15888) --> (http://bugs.freedesktop.org/attachment.cgi?id=15888) test case -- Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi

[Bug 15444] Draw polygon has one pixel bias if PolygonMode is GL_LINE)

http://bugs.freedesktop.org/show_bug.cgi?id=15444 WuNian <[EMAIL PROTECTED]> changed: What|Removed |Added Summary|DrawPixel has one pixel bias|Draw polygon has one pixel

[Bug 10344] [2.6.25-rc6] possible regression: X server dying

http://bugzilla.kernel.org/show_bug.cgi?id=10344 [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |REJECTED Resolution|

[Bug 10344] [2.6.25-rc6] possible regression: X server dying

http://bugzilla.kernel.org/show_bug.cgi?id=10344 [EMAIL PROTECTED] changed: What|Removed |Added OtherBugsDependingO|9832| nThis|

[Bug 15477] full screen is white when use compiz

http://bugs.freedesktop.org/show_bug.cgi?id=15477 --- Comment #2 from WuNian <[EMAIL PROTECTED]> 2008-04-13 17:57:33 PST --- (In reply to comment #1) > Hey, if you start compiz in a terminal, you may see "failed to create > drawable" I can see this message too and the screen is black. > me

[Bug 7661] R200 lockup

http://bugzilla.kernel.org/show_bug.cgi?id=7661 [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |REJECTED Resolution|

[Bug 14221] [i965 64bit] ut2004 run abort on mesa 7.0.3 rc1

http://bugs.freedesktop.org/show_bug.cgi?id=14221 --- Comment #5 from vaLentin <[EMAIL PROTECTED]> 2008-04-13 14:55:00 PST --- When trying Mesa 7.0.2 with the following patch applied to it: https://bugs.freedesktop.org/show_bug.cgi?id=13492 I get the results described in the current bug rep

[Bug 15480] r200 vertex program regression

http://bugs.freedesktop.org/show_bug.cgi?id=15480 --- Comment #4 from Andrew Randrianasulu <[EMAIL PROTECTED]> 2008-04-13 06:09:05 PST --- from 'gdb doom.x86': Mesa: User error: GL_INVALID_ENUM in glProgramEnvParameter(target) Mesa: User error: GL_INVALID_ENUM in glProgramEnvParameter(targe

[Bug 7770] PCI domain mismatch between X server and kernel, leaving clients unable to use direct rendering

http://bugs.freedesktop.org/show_bug.cgi?id=7770 --- Comment #37 from Marcin Kurek <[EMAIL PROTECTED]> 2008-04-13 03:25:54 PST --- True. With recent mesa patch GL works just fine here only the number of visuals decreased a lot: visual x bf lv rg d st colorbuffer ax dp st accumbuffer m

[Bug 15480] r200 vertex program regression

http://bugs.freedesktop.org/show_bug.cgi?id=15480 --- Comment #3 from Markus Amsler <[EMAIL PROTECTED]> 2008-04-13 03:02:57 PST --- r300 had the same regression fixed with commit 85e816882d8cd136e041c915698314ed1110e2f2. Your patch looks correct. To debug segfaults, use gdb to get a backtrac

[Bug 14937] Intel i915 hard lockup when using vsync-synchronized swapping

http://bugs.freedesktop.org/show_bug.cgi?id=14937 --- Comment #5 from Michel Dänzer <[EMAIL PROTECTED]> 2008-04-13 02:56:16 PST --- (In reply to comment #4) > Note that the tasklet callback function may also be called from normal process > context if the tasklet couldn't acquire the DRM lock

[Bug 14937] Intel i915 hard lockup when using vsync-synchronized swapping

http://bugs.freedesktop.org/show_bug.cgi?id=14937 --- Comment #4 from Michel Dänzer <[EMAIL PROTECTED]> 2008-04-13 02:54:10 PST --- (In reply to comment #2) > Data that is shared between a hard interrupt handler and a tasklet or a normal > process should use spin_lock_irqsave() whereas data

[Bug 15441] "Error: couldn't find RGB GLX visual or fbconfig" after upgrading to current git

http://bugs.freedesktop.org/show_bug.cgi?id=15441 Bernhard Rosenkraenzer <[EMAIL PROTECTED]> changed: What|Removed |Added Status|NEW |RESOLVED

[Bug 14937] Intel i915 hard lockup when using vsync-synchronized swapping

http://bugs.freedesktop.org/show_bug.cgi?id=14937 --- Comment #3 from Mike Isely <[EMAIL PROTECTED]> 2008-04-13 01:41:39 PST --- Interesting. I was unaware of spin_lock_bh(), but having looked at it now I agree. If I had seen it before, I would have used it. But for what it's worth, I didn

[Bug 14937] Intel i915 hard lockup when using vsync-synchronized swapping

http://bugs.freedesktop.org/show_bug.cgi?id=14937 Thomas Hellström <[EMAIL PROTECTED]> changed: What|Removed |Added Status|RESOLVED|REOPENED R