Re: [r300] VBO broken by changes in mesa

2006-11-18 Thread Rune Petersen
Keith Whitwell wrote:
> Rune Petersen wrote:
>> Hi,
>>
>> A patch for making sure VBO's are mapped breaks r300:
>>
>> http://marc.theaimsgroup.com/?l=mesa3d-cvs&m=116364446305536&w=2
>>
>> It would appear we "just" need to add _ae_(un)map_vbos() the right
>> places in radeon_vtxfmt_a.c.
> 
> Rune, my expectation was that the change wouldn't break drivers, but
> that doing the _ae_map/unmap externally would reduce the performance
> impact of the change.

> I can't debug r300 unfortunately, so if adding the explict map/unmap
> helps, go ahead and do so, but could you also post me stacktraces of the
> crash (I assume its a crash?) so I can figure out what the underlying
> problem might be?

I am not that familiar with this code, I did try and all I got was a
segfault in map =)

Your assert caught something:

backtrace:
#0  0xe410 in __kernel_vsyscall ()
#1  0xa7d4c811 in raise () from /lib/tls/i686/cmov/libc.so.6
#2  0xa7d4dfb9 in abort () from /lib/tls/i686/cmov/libc.so.6
#3  0xa7d45fbf in __assert_fail () from /lib/tls/i686/cmov/libc.so.6
#4  0xa78c8bc6 in _ae_invalidate_state (ctx=0x0, new_state=4195328)
at main/api_arrayelt.c:1299
#5  0xa7936a0d in _tnl_InvalidateState (ctx=0x80ebdc0, new_state=4195328)
at tnl/t_context.c:158
#6  0xa78bb00a in r300InvalidateState (ctx=0x80ebdc0, new_state=4195328)
at r300_state.c:1878
#7  0xa790b6ac in _mesa_update_state_locked (ctx=0x80ebdc0)
at main/state.c:1107
#8  0xa790b6ea in _mesa_update_state (ctx=0x80ebdc0) at main/state.c:1118
#9  0xa793c265 in _tnl_playback_vertex_list (ctx=0x80ebdc0, data=0x8794c10)
at tnl/t_save_playback.c:198
#10 0xa79399a2 in _save_compile_vertex_list (ctx=0x80ebdc0)
at tnl/t_save_api.c:306
#11 0xa79399e8 in _tnl_SaveFlushVertices (ctx=0x80ebdc0)
at tnl/t_save_api.c:1577
#12 0xa78e16fb in _mesa_EndList () at main/dlist.c:6814
#13 0x08050d6b in ?? ()
#14 0x08068fd4 in ?? ()
#15 0xa7f7e310 in glutMainLoop () at glut_event.c:967
#16 0x0804c02e in ?? ()


Rune Petersen

-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
--
___
Dri-devel mailing list
Dri-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dri-devel


[Bug 8758] savage driver bug: Support for non power of two textures missing

2006-11-18 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=8758  
 




--- Additional Comments From [EMAIL PROTECTED]  2006-11-18 13:37 ---
I filed bug 9077 for this.  
 
 
--   
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email 
 
--- You are receiving this mail because: ---
You are the assignee for the bug, or are watching the assignee.

-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
--
___
Dri-devel mailing list
Dri-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dri-devel


Re: [r300] VBO broken by changes in mesa

2006-11-18 Thread Keith Whitwell
Rune Petersen wrote:
> Hi,
> 
> A patch for making sure VBO's are mapped breaks r300:
> 
> http://marc.theaimsgroup.com/?l=mesa3d-cvs&m=116364446305536&w=2
> 
> It would appear we "just" need to add _ae_(un)map_vbos() the right
> places in radeon_vtxfmt_a.c.

Rune, my expectation was that the change wouldn't break drivers, but 
that doing the _ae_map/unmap externally would reduce the performance 
impact of the change.

I can't debug r300 unfortunately, so if adding the explict map/unmap 
helps, go ahead and do so, but could you also post me stacktraces of the 
crash (I assume its a crash?) so I can figure out what the underlying 
problem might be?

Keith

-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
--
___
Dri-devel mailing list
Dri-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dri-devel


[Bug 4607] Crashes after resume with Savage DRI

2006-11-18 Thread bugme-daemon
http://bugzilla.kernel.org/show_bug.cgi?id=4607





--- Additional Comments From [EMAIL PROTECTED]  2006-11-18 12:39 ---
It seems like I can avoid the crashes with Option "BusType" "PCI" alone. Using
Option "DmaMode" "None" alone helps for glxgears, but crashes with other 3D
screensavers.

--- You are receiving this mail because: ---
You are the assignee for the bug, or are watching the assignee.

-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
--
___
Dri-devel mailing list
Dri-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dri-devel


[Bug 9074] New: X locks with black screen on startup with ATI RV370 5B64 [FireGL V3100 (PCIE)]

2006-11-18 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=9074  
 
   Summary: X locks with black screen on startup with ATI RV370 5B64
[FireGL V3100 (PCIE)]
   Product: DRI
   Version: XOrg CVS
  Platform: PC
OS/Version: Linux
Status: NEW
  Severity: normal
  Priority: P2
 Component: DRM modules
AssignedTo: dri-devel@lists.sourceforge.net
ReportedBy: [EMAIL PROTECTED]


My machine has the same problem as the unrelated comment at the end of Bug 5341.
Starting X brings my machine to a crawl and X is permanently unkillable and
blank. Remote access from another machine allows me to log in and restart the
computer.

If I move radeon.ko out of the way, X starts normally.

This is on x86_64 FC6, but I also tried drm.ko and radeon.ko built from git.
  
 
 
--   
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email 
 
--- You are receiving this mail because: ---
You are the assignee for the bug, or are watching the assignee.

-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
--
___
Dri-devel mailing list
Dri-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dri-devel


[Bug 9011] r300_dri and new Mesa give libGL error: XF86DRIQueryDirectRenderingCapable returned false

2006-11-18 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=9011  
 




--- Additional Comments From [EMAIL PROTECTED]  2006-11-18 08:40 ---
I hope you take care about these messages because,
have kids in a room playng tuxrace and work in a closed one with beryl
is a great setup for a single PC.

Closing the system
only the upper side( 1/5 ) of the screen became black after X shoutdown
and here it look like the console messages are printed out,
but I can't read them.

I think I can dup my display( I'll give a try to this ) but I can't use busId
02:00:00  to setup the first X server.
Sound this strange?  
 
 
--   
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email 
 
--- You are receiving this mail because: ---
You are the assignee for the bug, or are watching the assignee.

-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
--
___
Dri-devel mailing list
Dri-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dri-devel


[r300] VBO broken by changes in mesa

2006-11-18 Thread Rune Petersen
Hi,

A patch for making sure VBO's are mapped breaks r300:

http://marc.theaimsgroup.com/?l=mesa3d-cvs&m=116364446305536&w=2

It would appear we "just" need to add _ae_(un)map_vbos() the right
places in radeon_vtxfmt_a.c.


Rune Petersen

-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
--
___
Dri-devel mailing list
Dri-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dri-devel


[Bug 8250] Warcraft player avatars not rendered correctly when GL_ARB_vertex_program enabled.

2006-11-18 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=8250  
 




--- Additional Comments From [EMAIL PROTECTED]  2006-11-18 04:55 ---
(In reply to comment #29)
> Well, I've got some trouble sometimes with xscreensaver not getting direct
> rendering (where all other apps work). However, I can reproduce it with direct
> rendering, if I set tcl_mode to 0 or 1. So there definitely is a problem here,
> it certainly should look the same regardless of tcl mode.

I am running with tcl_mode = 1.

> It could be related to warcraft problems, though that's difficult to say.

Naturally, if you don't have a Warcraft account ;-). However, the current
problems are visible at the login screen and so no account would be needed. All
you would need would be the trial client.  
 
 
--   
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email 
 
--- You are receiving this mail because: ---
You are the assignee for the bug, or are watching the assignee.

-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
--
___
Dri-devel mailing list
Dri-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dri-devel


[Bug 9042] r300 - unsupported vertex format in vertex Array

2006-11-18 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=9042  
 




--- Additional Comments From [EMAIL PROTECTED]  2006-11-18 03:14 ---
r300 gpus cannot natively support this. One could mirror the VOBs as floats 
though.  
 
 
--   
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email 
 
--- You are receiving this mail because: ---
You are the assignee for the bug, or are watching the assignee.

-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
--
___
Dri-devel mailing list
Dri-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dri-devel