From: Jon <jf...@pd...> - 2006-01-05 01:07:52
|
I have a ATI AIW Radeon 9800 Pro (r350), I'm getting plenty of freezing with r300 DRI module. I tried Quake3 (wont get past beginning of opening game video, locks computer solid) and Xmoto (lasts for a few seconds than computer locks) GLXGears runs fine and for a long time, no freezing. (10755 frames in 5.0 sec = 2151 FPS etc) I'm using FreeBSD 6.0 Stable, I just built from cvs at freedesktop.org Mesa3D ,DRM kernel module and the r300 DRI module. Is their anything I can test or do? -- Thanks dmesg drm0: <ATI Radeon NH R350 9800 Pro> port 0xc000-0xc0ff mem 0xd8000000-0xdfffffff,0xe8020000-0xe802ffff irq 9 at device 0.0 on pci1 info: [drm] AGP at 0xd0000000 128MB info: [drm] Initialized radeon 1.21.0 20051229 info: [drm] Loading R300 Microcode ------------------- glxinfo No ctx->FragmentProgram._Current!! name of display: :0.0 display: :0 screen: 0 direct rendering: Yes server glx vendor string: SGI server glx version string: 1.2 server glx extensions: GLX_ARB_multisample, GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_EXT_import_context, GLX_OML_swap_method, GLX_SGI_make_current_read, GLX_SGIS_multisample, GLX_SGIX_hyperpipe, GLX_SGIX_swap_barrier, GLX_SGIX_fbconfig client glx vendor string: SGI client glx version string: 1.4 client glx extensions: GLX_ARB_get_proc_address, GLX_ARB_multisample, GLX_EXT_import_context, GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_MESA_allocate_memory, GLX_MESA_swap_control, GLX_MESA_swap_frame_usage, GLX_OML_swap_method, GLX_OML_sync_control, GLX_SGI_make_current_read, GLX_SGI_swap_control, GLX_SGI_video_sync, GLX_SGIS_multisample, GLX_SGIX_fbconfig, GLX_SGIX_pbuffer, GLX_SGIX_visual_select_group GLX extensions: GLX_ARB_get_proc_address, GLX_ARB_multisample, GLX_EXT_import_context, GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_MESA_swap_control, GLX_MESA_swap_frame_usage, GLX_OML_swap_method, GLX_SGI_video_sync, GLX_SGIS_multisample, GLX_SGIX_fbconfig OpenGL vendor string: Tungsten Graphics, Inc. OpenGL renderer string: Mesa DRI R300 20040924 AGP 1x x86/MMX/SSE2 TCL OpenGL version string: 1.3 Mesa 6.5 OpenGL extensions: GL_ARB_fragment_program, GL_ARB_imaging, GL_ARB_multisample, GL_ARB_multitexture, GL_ARB_texture_border_clamp, GL_ARB_texture_compression, GL_ARB_texture_cube_map, GL_ARB_texture_env_add, GL_ARB_texture_env_combine, GL_ARB_texture_env_crossbar, GL_ARB_texture_env_dot3, GL_ARB_texture_mirrored_repeat, GL_ARB_texture_rectangle, GL_ARB_transpose_matrix, GL_ARB_vertex_buffer_object, GL_ARB_vertex_program, GL_ARB_window_pos, GL_EXT_abgr, GL_EXT_bgra, GL_EXT_blend_color, GL_EXT_blend_equation_separate, GL_EXT_blend_func_separate, GL_EXT_blend_minmax, GL_EXT_blend_subtract, GL_EXT_clip_volume_hint, GL_EXT_compiled_vertex_array, GL_EXT_convolution, GL_EXT_copy_texture, GL_EXT_draw_range_elements, GL_EXT_histogram, GL_EXT_packed_depth_stencil, GL_EXT_packed_pixels, GL_EXT_polygon_offset, GL_EXT_rescale_normal, GL_EXT_secondary_color, GL_EXT_separate_specular_color, GL_EXT_stencil_wrap, GL_EXT_subtexture, GL_EXT_texture, GL_EXT_texture3D, GL_EXT_texture_edge_clamp, GL_EXT_texture_env_add, GL_EXT_texture_env_combine, GL_EXT_texture_env_dot3, GL_EXT_texture_filter_anisotropic, GL_EXT_texture_lod_bias, GL_EXT_texture_mirror_clamp, GL_EXT_texture_object, GL_EXT_texture_rectangle, GL_EXT_vertex_array, GL_APPLE_packed_pixels, GL_ATI_blend_equation_separate, GL_ATI_texture_env_combine3, GL_ATI_texture_mirror_once, GL_IBM_rasterpos_clip, GL_IBM_texture_mirrored_repeat, GL_INGR_blend_func_separate, GL_MESA_pack_invert, GL_MESA_ycbcr_texture, GL_MESA_window_pos, GL_NV_blend_square, GL_NV_light_max_exponent, GL_NV_texture_rectangle, GL_NV_texgen_reflection, GL_NV_vertex_program, GL_OES_read_format, GL_SGI_color_matrix, GL_SGI_color_table, GL_SGIS_generate_mipmap, GL_SGIS_texture_border_clamp, GL_SGIS_texture_edge_clamp, GL_SGIS_texture_lod glu version: 1.3 glu extensions: GLU_EXT_nurbs_tessellator, GLU_EXT_object_space_tess visual x bf lv rg d st colorbuffer ax dp st accumbuffer ms cav id dep cl sp sz l ci b ro r g b a bf th cl r g b a ns b eat ---------------------------------------------------------------------- 0x23 24 tc 0 32 0 r . . 8 8 8 8 0 24 0 0 0 0 0 0 0 None 0x24 24 tc 0 32 0 r . . 8 8 8 8 0 24 8 0 0 0 0 0 0 None 0x25 24 tc 0 32 0 r . . 8 8 8 8 0 24 0 16 16 16 16 0 0 Slow 0x26 24 tc 0 32 0 r . . 8 8 8 8 0 24 8 16 16 16 16 0 0 Slow 0x27 24 tc 0 32 0 r y . 8 8 8 8 0 24 0 0 0 0 0 0 0 None 0x28 24 tc 0 32 0 r y . 8 8 8 8 0 24 8 0 0 0 0 0 0 None 0x29 24 tc 0 32 0 r y . 8 8 8 8 0 24 0 16 16 16 16 0 0 Slow 0x2a 24 tc 0 32 0 r y . 8 8 8 8 0 24 8 16 16 16 16 0 0 Slow 0x2b 24 dc 0 32 0 r . . 8 8 8 8 0 24 0 0 0 0 0 0 0 None 0x2c 24 dc 0 32 0 r . . 8 8 8 8 0 24 8 0 0 0 0 0 0 None 0x2d 24 dc 0 32 0 r . . 8 8 8 8 0 24 0 16 16 16 16 0 0 Slow 0x2e 24 dc 0 32 0 r . . 8 8 8 8 0 24 8 16 16 16 16 0 0 Slow 0x2f 24 dc 0 32 0 r y . 8 8 8 8 0 24 0 0 0 0 0 0 0 None 0x30 24 dc 0 32 0 r y . 8 8 8 8 0 24 8 0 0 0 0 0 0 None 0x31 24 dc 0 32 0 r y . 8 8 8 8 0 24 0 16 16 16 16 0 0 Slow 0x32 24 dc 0 32 0 r y . 8 8 8 8 0 24 8 16 16 16 16 0 0 Slow |
From: Aapo T. <ae...@ra...> - 2006-01-05 02:51:16
|
On Wed, 04 Jan 2006 21:07:41 -0400 Jon <jf...@pd...> wrote: > I have a ATI AIW Radeon 9800 Pro (r350), I'm getting plenty of freezing > with r300 DRI module. I tried Quake3 (wont get past beginning of opening > game video, locks computer solid) and Xmoto (lasts for a few seconds > than computer locks) GLXGears runs fine and for a long time, no > freezing. (10755 frames in 5.0 sec = 2151 FPS etc) I'm using FreeBSD 6.0 > Stable, I just built from cvs at freedesktop.org Mesa3D ,DRM kernel > module and the r300 DRI module. > Is their anything I can test or do? This is a known problem with r9500, r9700 and r9800 cards. You can initialize the card with official drivers. No other fix beyond that exist nor is being planned on. -- Aapo Tahkola |
From: khaqq <kh...@fr...> - 2006-01-05 03:05:08
|
On Thu, 5 Jan 2006 04:51:31 +0000 Aapo Tahkola <ae...@ra...> wrote: > On Wed, 04 Jan 2006 21:07:41 -0400 > Jon <jf...@pd...> wrote: > > > I have a ATI AIW Radeon 9800 Pro (r350), I'm getting plenty of freezing > > with r300 DRI module. I tried Quake3 (wont get past beginning of opening > > game video, locks computer solid) and Xmoto (lasts for a few seconds > > than computer locks) GLXGears runs fine and for a long time, no > > freezing. (10755 frames in 5.0 sec = 2151 FPS etc) I'm using FreeBSD 6.0 > > Stable, I just built from cvs at freedesktop.org Mesa3D ,DRM kernel > > module and the r300 DRI module. > > Is their anything I can test or do? > > This is a known problem with r9500, r9700 and r9800 cards. > You can initialize the card with official drivers. > No other fix beyond that exist nor is being planned on. Unless I am missing something, I believe there are no "official drivers" for FreeBSD from ATI at this point. khaqq |
From: Anish M. <mis...@os...> - 2006-01-05 04:32:49
|
On Wednesday 04 January 2006 10:05 pm, khaqq wrote: > On Thu, 5 Jan 2006 04:51:31 +0000 > > Aapo Tahkola <ae...@ra...> wrote: > > On Wed, 04 Jan 2006 21:07:41 -0400 > > > > Jon <jf...@pd...> wrote: > > > I have a ATI AIW Radeon 9800 Pro (r350), I'm getting plenty of > > > freezing with r300 DRI module. I tried Quake3 (wont get past > > > beginning of opening game video, locks computer solid) and > > > Xmoto (lasts for a few seconds than computer locks) GLXGears > > > runs fine and for a long time, no freezing. (10755 frames in > > > 5.0 sec =3D 2151 FPS etc) I'm using FreeBSD 6.0 Stable, I just > > > built from cvs at freedesktop.org Mesa3D ,DRM kernel module and > > > the r300 DRI module. > > > Is their anything I can test or do? > > > > This is a known problem with r9500, r9700 and r9800 cards. > > You can initialize the card with official drivers. > > No other fix beyond that exist nor is being planned on. > > Unless I am missing something, I believe there are no > "official drivers" for FreeBSD from ATI at this point. Someone is working with ATI on it and just posted something last week=20 to the FreeBSD current mailling list. A search should turn up=20 something. =2D-=20 Anish Mistry |
From: Adam K K. <ad...@vo...> - 2006-01-05 11:09:57
|
Aapo Tahkola wrote: >On Wed, 04 Jan 2006 21:07:41 -0400 >Jon <jf...@pd...> wrote: > > > >>I have a ATI AIW Radeon 9800 Pro (r350), I'm getting plenty of freezing >>with r300 DRI module. I tried Quake3 (wont get past beginning of opening >>game video, locks computer solid) and Xmoto (lasts for a few seconds >>than computer locks) GLXGears runs fine and for a long time, no >>freezing. (10755 frames in 5.0 sec = 2151 FPS etc) I'm using FreeBSD 6.0 >>Stable, I just built from cvs at freedesktop.org Mesa3D ,DRM kernel >>module and the r300 DRI module. >>Is their anything I can test or do? >> >> > >This is a known problem with r9500, r9700 and r9800 cards. >You can initialize the card with official drivers. >No other fix beyond that exist nor is being planned on. > > > My only concern is that the r300 driver is now making it onto more and more machines, either through Xorg, or just by being packaged by their distribution. Many of these machines will have those cards that will lockup almost immediately when a 3D application (other than glxgears) is launched. Instead of having all these people think that Xorg (or the DRI) is just an unstable POS, it might make sense to have the server automatically disable 3D on those cards unless the users specifies an option ("EnableUnstableDRIon9800Hardware") in their xorg.conf file. Adam |
From: Michel <mi...@da...> - 2006-01-05 11:28:18
|
On Thu, 2006-01-05 at 06:09 -0500, Adam K Kirchhoff wrote: >=20 > [...] it might make sense to have the server=20 > automatically disable 3D on those cards unless the users specifies an=20 > option ("EnableUnstableDRIon9800Hardware") in their xorg.conf file. Agreed, except that IMHO it should be the standard (in some other drivers) Option "DRI", the default of which should be something like * (at least problematic) r300 cards: disabled * other cards: current behaviour (enabled if the "dri" module is loaded, disabled otherwise) When the option is enabled explicitly, the driver should load the "dri" module if necessary. This option will also be useful to manage which of several cards enables the DRI. Now, somebody get his hands dirty. :) --=20 Earthling Michel D=C3=A4nzer | Debian (powerpc), X and DRI develop= er Libre software enthusiast | http://svcs.affero.net/rm.php?r=3Ddaenzer |
From: Adam K K. <ad...@vo...> - 2006-01-05 11:32:04
|
Michel D=C3=A4nzer wrote: >On Thu, 2006-01-05 at 06:09 -0500, Adam K Kirchhoff wrote: > =20 > >>[...] it might make sense to have the server=20 >>automatically disable 3D on those cards unless the users specifies an=20 >>option ("EnableUnstableDRIon9800Hardware") in their xorg.conf file. >> =20 >> > >Agreed, except that IMHO it should be the standard (in some other >drivers) Option "DRI", the default of which should be something like > > * (at least problematic) r300 cards: disabled > * other cards: current behaviour (enabled if the "dri" module is > loaded, disabled otherwise) > >When the option is enabled explicitly, the driver should load the "dri" >module if necessary. > >This option will also be useful to manage which of several cards enables >the DRI. > >Now, somebody get his hands dirty. :) > > > =20 > As long as there's an explanation in the Xorg logfile which explains why=20 the DRI option was disabled in that case :-)=20 Adam |
From: Jerome G. <j.g...@gm...> - 2006-01-05 04:38:04
|
On 1/5/06, Jon <jf...@pd...> wrote: > I have a ATI AIW Radeon 9800 Pro (r350), I'm getting plenty of freezing > with r300 DRI module. I tried Quake3 (wont get past beginning of opening > game video, locks computer solid) and Xmoto (lasts for a few seconds > than computer locks) GLXGears runs fine and for a long time, no > freezing. (10755 frames in 5.0 sec =3D 2151 FPS etc) I'm using FreeBSD 6.= 0 > Stable, I just built from cvs at freedesktop.org Mesa3D ,DRM kernel > module and the r300 DRI module. > Is their anything I can test or do? > -- Thanks I have been trying to track down the issue during last few month. No success so far, maybe i am not a good hunter ;). Anyway could you test to first run an xserver with fglrx (no need for the drm module) and then run a server with r300 and see if you still have lockup (you shouldn't) thus i know you probably face the same lockup as i do. best, Jerome Glisse |
From: Benjamin H. <be...@ke...> - 2006-01-05 06:00:20
|
On Thu, 2006-01-05 at 02:30 +0100, Jerome Glisse wrote: > On 1/5/06, Jon <jf...@pd...> wrote: > > I have a ATI AIW Radeon 9800 Pro (r350), I'm getting plenty of freezing > > with r300 DRI module. I tried Quake3 (wont get past beginning of opening > > game video, locks computer solid) and Xmoto (lasts for a few seconds > > than computer locks) GLXGears runs fine and for a long time, no > > freezing. (10755 frames in 5.0 sec = 2151 FPS etc) I'm using FreeBSD 6.0 > > Stable, I just built from cvs at freedesktop.org Mesa3D ,DRM kernel > > module and the r300 DRI module. > > Is their anything I can test or do? > > -- Thanks > > I have been trying to track down the issue during last few month. > No success so far, maybe i am not a good hunter ;). Anyway could > you test to first run an xserver with fglrx (no need for the drm module) > and then run a server with r300 and see if you still have lockup > (you shouldn't) thus i know you probably face the same lockup as > i do. Have you tried checking what's going on with the card memory map ? (values of MC_AGP_LOCATION, MC_FB_LOCATION, CONFIG_MEMSIZE, CONFIG_APER_SIZE, HDP control and how they are munged by X and DRI ? There is definitely a bug or two lurking around when we have CONFIG_APER_SIZE smaller than CONFIG_MEMSIZE that might be causing those lockups). Ben. |
From: Jerome G. <j.g...@gm...> - 2006-01-05 10:05:46
|
On 1/5/06, Benjamin Herrenschmidt <be...@ke...> wrote: > On Thu, 2006-01-05 at 02:30 +0100, Jerome Glisse wrote: > > On 1/5/06, Jon <jf...@pd...> wrote: > > > I have a ATI AIW Radeon 9800 Pro (r350), I'm getting plenty of freezi= ng > > > with r300 DRI module. I tried Quake3 (wont get past beginning of open= ing > > > game video, locks computer solid) and Xmoto (lasts for a few seconds > > > than computer locks) GLXGears runs fine and for a long time, no > > > freezing. (10755 frames in 5.0 sec =3D 2151 FPS etc) I'm using FreeBS= D 6.0 > > > Stable, I just built from cvs at freedesktop.org Mesa3D ,DRM kernel > > > module and the r300 DRI module. > > > Is their anything I can test or do? > > > -- Thanks > > > > I have been trying to track down the issue during last few month. > > No success so far, maybe i am not a good hunter ;). Anyway could > > you test to first run an xserver with fglrx (no need for the drm module= ) > > and then run a server with r300 and see if you still have lockup > > (you shouldn't) thus i know you probably face the same lockup as > > i do. > > Have you tried checking what's going on with the card memory map ? > (values of MC_AGP_LOCATION, MC_FB_LOCATION, CONFIG_MEMSIZE, > CONFIG_APER_SIZE, HDP control and how they are munged by X and DRI ? > There is definitely a bug or two lurking around when we have > CONFIG_APER_SIZE smaller than CONFIG_MEMSIZE that might be causing those > lockups). So far i have quite ignored such things. I will take a closer look to that, i haven't even tested your patch on that. I will give it a try. best, Jerome Glisse |
From: Benjamin H. <be...@ke...> - 2006-01-05 10:23:38
|
On Thu, 2006-01-05 at 11:05 +0100, Jerome Glisse wrote: > On 1/5/06, Benjamin Herrenschmidt <be...@ke...> wrote: > > On Thu, 2006-01-05 at 02:30 +0100, Jerome Glisse wrote: > > > On 1/5/06, Jon <jf...@pd...> wrote: > > > > I have a ATI AIW Radeon 9800 Pro (r350), I'm getting plenty of freezing > > > > with r300 DRI module. I tried Quake3 (wont get past beginning of opening > > > > game video, locks computer solid) and Xmoto (lasts for a few seconds > > > > than computer locks) GLXGears runs fine and for a long time, no > > > > freezing. (10755 frames in 5.0 sec = 2151 FPS etc) I'm using FreeBSD 6.0 > > > > Stable, I just built from cvs at freedesktop.org Mesa3D ,DRM kernel > > > > module and the r300 DRI module. > > > > Is their anything I can test or do? > > > > -- Thanks > > > > > > I have been trying to track down the issue during last few month. > > > No success so far, maybe i am not a good hunter ;). Anyway could > > > you test to first run an xserver with fglrx (no need for the drm module) > > > and then run a server with r300 and see if you still have lockup > > > (you shouldn't) thus i know you probably face the same lockup as > > > i do. > > > > Have you tried checking what's going on with the card memory map ? > > (values of MC_AGP_LOCATION, MC_FB_LOCATION, CONFIG_MEMSIZE, > > CONFIG_APER_SIZE, HDP control and how they are munged by X and DRI ? > > There is definitely a bug or two lurking around when we have > > CONFIG_APER_SIZE smaller than CONFIG_MEMSIZE that might be causing those > > lockups). > > So far i have quite ignored such things. I will take a closer look > to that, i haven't even tested your patch on that. I will give it > a try. You may have to hack the kernel DRM too so that it puts the same values in there, currently, it's broken too. Ben. |
From: Adam K K. <ad...@vo...> - 2006-01-06 22:02:10
|
Benjamin Herrenschmidt wrote: >On Thu, 2006-01-05 at 11:05 +0100, Jerome Glisse wrote: > > >>On 1/5/06, Benjamin Herrenschmidt <be...@ke...> wrote: >> >> >>>On Thu, 2006-01-05 at 02:30 +0100, Jerome Glisse wrote: >>> >>> >>>>On 1/5/06, Jon <jf...@pd...> wrote: >>>> >>>> >>>>>I have a ATI AIW Radeon 9800 Pro (r350), I'm getting plenty of freezing >>>>>with r300 DRI module. I tried Quake3 (wont get past beginning of opening >>>>>game video, locks computer solid) and Xmoto (lasts for a few seconds >>>>>than computer locks) GLXGears runs fine and for a long time, no >>>>>freezing. (10755 frames in 5.0 sec = 2151 FPS etc) I'm using FreeBSD 6.0 >>>>>Stable, I just built from cvs at freedesktop.org Mesa3D ,DRM kernel >>>>>module and the r300 DRI module. >>>>>Is their anything I can test or do? >>>>>-- Thanks >>>>> >>>>> >>>>I have been trying to track down the issue during last few month. >>>>No success so far, maybe i am not a good hunter ;). Anyway could >>>>you test to first run an xserver with fglrx (no need for the drm module) >>>>and then run a server with r300 and see if you still have lockup >>>>(you shouldn't) thus i know you probably face the same lockup as >>>>i do. >>>> >>>> >>>Have you tried checking what's going on with the card memory map ? >>>(values of MC_AGP_LOCATION, MC_FB_LOCATION, CONFIG_MEMSIZE, >>>CONFIG_APER_SIZE, HDP control and how they are munged by X and DRI ? >>>There is definitely a bug or two lurking around when we have >>>CONFIG_APER_SIZE smaller than CONFIG_MEMSIZE that might be causing those >>>lockups). >>> >>> >>So far i have quite ignored such things. I will take a closer look >>to that, i haven't even tested your patch on that. I will give it >>a try. >> >> > >You may have to hack the kernel DRM too so that it puts the same values >in there, currently, it's broken too. > >Ben. > > > Is it safe to say that this is only a problem for cards with 256 bit memory interfaces? From http://en.wikipedia.org/wiki/Radeon_9700_core: Radeon 9700 275 256-bit Radeon 9800 325 256-bit Radeon 9700 Pro 325 256-bit Radeon 9800 Pro 380 256-bit Radeon 9800 XT 412 256-bit Do all these experience the same lockups? Then with the X300 - X850, I think it's only the X800 and X850 cards have 256-bit interfaces, correct? Do X800 cards experience the same lockups? Adam |
From: Alex D. <ale...@gm...> - 2006-01-06 22:05:42
|
On 1/6/06, Adam K Kirchhoff <ad...@vo...> wrote: > Benjamin Herrenschmidt wrote: > > >On Thu, 2006-01-05 at 11:05 +0100, Jerome Glisse wrote: > > > > > >>On 1/5/06, Benjamin Herrenschmidt <be...@ke...> wrote: > >> > >> > >>>On Thu, 2006-01-05 at 02:30 +0100, Jerome Glisse wrote: > >>> > >>> > >>>>On 1/5/06, Jon <jf...@pd...> wrote: > >>>> > >>>> > >>>>>I have a ATI AIW Radeon 9800 Pro (r350), I'm getting plenty of freez= ing > >>>>>with r300 DRI module. I tried Quake3 (wont get past beginning of ope= ning > >>>>>game video, locks computer solid) and Xmoto (lasts for a few seconds > >>>>>than computer locks) GLXGears runs fine and for a long time, no > >>>>>freezing. (10755 frames in 5.0 sec =3D 2151 FPS etc) I'm using FreeB= SD 6.0 > >>>>>Stable, I just built from cvs at freedesktop.org Mesa3D ,DRM kernel > >>>>>module and the r300 DRI module. > >>>>>Is their anything I can test or do? > >>>>>-- Thanks > >>>>> > >>>>> > >>>>I have been trying to track down the issue during last few month. > >>>>No success so far, maybe i am not a good hunter ;). Anyway could > >>>>you test to first run an xserver with fglrx (no need for the drm modu= le) > >>>>and then run a server with r300 and see if you still have lockup > >>>>(you shouldn't) thus i know you probably face the same lockup as > >>>>i do. > >>>> > >>>> > >>>Have you tried checking what's going on with the card memory map ? > >>>(values of MC_AGP_LOCATION, MC_FB_LOCATION, CONFIG_MEMSIZE, > >>>CONFIG_APER_SIZE, HDP control and how they are munged by X and DRI ? > >>>There is definitely a bug or two lurking around when we have > >>>CONFIG_APER_SIZE smaller than CONFIG_MEMSIZE that might be causing tho= se > >>>lockups). > >>> > >>> > >>So far i have quite ignored such things. I will take a closer look > >>to that, i haven't even tested your patch on that. I will give it > >>a try. > >> > >> > > > >You may have to hack the kernel DRM too so that it puts the same values > >in there, currently, it's broken too. > > > >Ben. > > > > > > > > Is it safe to say that this is only a problem for cards with 256 bit > memory interfaces? From http://en.wikipedia.org/wiki/Radeon_9700_core: > > Radeon 9700 275 256-bit > Radeon 9800 325 256-bit > Radeon 9700 Pro 325 256-bit > Radeon 9800 Pro 380 256-bit > Radeon 9800 XT 412 256-bit > > > Do all these experience the same lockups? I think 9500s have the same problem. > > Then with the X300 - X850, I think it's only the X800 and X850 cards > have 256-bit interfaces, correct? Do X800 cards experience the same > lockups? > no problems on my pcie x800 Alex > Adam > > > |
From: Luca <kro...@gm...> - 2006-01-07 15:13:26
|
Il Fri, Jan 06, 2006 at 05:05:03PM -0500, Alex Deucher ha scritto: > On 1/6/06, Adam K Kirchhoff <ad...@vo...> wrote: > > Benjamin Herrenschmidt wrote: > > > > >On Thu, 2006-01-05 at 11:05 +0100, Jerome Glisse wrote: > > > > > > > > >>On 1/5/06, Benjamin Herrenschmidt <be...@ke...> wrote: > > >> > > >> > > >>>On Thu, 2006-01-05 at 02:30 +0100, Jerome Glisse wrote: > > >>> > > >>> > > >>>>On 1/5/06, Jon <jf...@pd...> wrote: > > >>>> > > >>>> > > >>>>>I have a ATI AIW Radeon 9800 Pro (r350), I'm getting plenty of freezing > > >>>>>with r300 DRI module. I tried Quake3 (wont get past beginning of opening > > >>>>>game video, locks computer solid) and Xmoto (lasts for a few seconds > > >>>>>than computer locks) GLXGears runs fine and for a long time, no > > >>>>>freezing. (10755 frames in 5.0 sec = 2151 FPS etc) I'm using FreeBSD 6.0 > > >>>>>Stable, I just built from cvs at freedesktop.org Mesa3D ,DRM kernel > > >>>>>module and the r300 DRI module. > > >>>>>Is their anything I can test or do? > > >>>>>-- Thanks > > >>>>> > > >>>>> > > >>>>I have been trying to track down the issue during last few month. > > >>>>No success so far, maybe i am not a good hunter ;). Anyway could > > >>>>you test to first run an xserver with fglrx (no need for the drm module) > > >>>>and then run a server with r300 and see if you still have lockup > > >>>>(you shouldn't) thus i know you probably face the same lockup as > > >>>>i do. > > >>>> > > >>>> > > >>>Have you tried checking what's going on with the card memory map ? > > >>>(values of MC_AGP_LOCATION, MC_FB_LOCATION, CONFIG_MEMSIZE, > > >>>CONFIG_APER_SIZE, HDP control and how they are munged by X and DRI ? > > >>>There is definitely a bug or two lurking around when we have > > >>>CONFIG_APER_SIZE smaller than CONFIG_MEMSIZE that might be causing those > > >>>lockups). > > >>> > > >>> > > >>So far i have quite ignored such things. I will take a closer look > > >>to that, i haven't even tested your patch on that. I will give it > > >>a try. > > >> > > >> > > > > > >You may have to hack the kernel DRM too so that it puts the same values > > >in there, currently, it's broken too. > > > > > >Ben. > > > > > > > > > > > > > Is it safe to say that this is only a problem for cards with 256 bit > > memory interfaces? From http://en.wikipedia.org/wiki/Radeon_9700_core: > > > > Radeon 9700 275 256-bit > > Radeon 9800 325 256-bit > > Radeon 9700 Pro 325 256-bit > > Radeon 9800 Pro 380 256-bit > > Radeon 9800 XT 412 256-bit > > > > > > Do all these experience the same lockups? > > I think 9500s have the same problem. I've a 9500 Pro: 01:00.0 VGA compatible controller: ATI Technologies Inc Radeon R300 NE [Radeon 9500 Pro] I sometimes use blender and it seems rock solid. I've now tried UT (the first one - it's the only game that I've here...) and it randomly locks up: sometimes it happens after a few minutes, sometimes it takes 20-30 minutes... so it seems a different problem. Luca -- Home: http://kronoz.cjb.net Io mi ricordo sempre il compleanno della mia ragazza: cade il giorno dopo di quando lei me lo ricorda |
From: Rune P. <ru...@me...> - 2006-01-06 22:07:33
|
Adam K Kirchhoff wrote: > Then with the X300 - X850, I think it's only the X800 and X850 cards > have 256-bit interfaces, correct? Do X800 cards experience the same > lockups? My X800 XT is working fine, the only real problem I have with lockups are with Quake 3 and is unrelated. Rune Petersen |
From: Aapo T. <ae...@ra...> - 2006-01-07 21:02:41
|
On Fri, 06 Jan 2006 23:07:30 +0100 Rune Petersen <ru...@me...> wrote: > Adam K Kirchhoff wrote: > > Then with the X300 - X850, I think it's only the X800 and X850 cards > > have 256-bit interfaces, correct? Do X800 cards experience the same > > lockups? Yes, my x850 pro had the same problem although the symptoms were very different from what others have reported. See bug #5294. > > My X800 XT is working fine, the only real problem I have with lockups > are with Quake 3 and is unrelated. Im a bit dubious your problem not being related as I had some similar problems with q3. Could you test if "manytex -size 512 512 -n 100" works? It should lock immediately if theres some problem as indirect buffers kept in gart get tampered over by texture uploads. -- Aapo Tahkola |
From: Rune P. <ru...@me...> - 2006-01-07 22:58:58
|
Aapo Tahkola wrote: >>My X800 XT is working fine, the only real problem I have with lockups >>are with Quake 3 and is unrelated. > > > Im a bit dubious your problem not being related as I had some similar problems with q3. > Could you test if "manytex -size 512 512 -n 100" works? > It should lock immediately if theres some problem as indirect buffers kept in gart get tampered over by texture uploads. > Looks fine, and no lockup. Rune Petersen |
From: Aapo T. <ae...@ra...> - 2006-01-07 23:28:55
|
On Sat, 07 Jan 2006 23:58:44 +0100 Rune Petersen <ru...@me...> wrote: > Aapo Tahkola wrote: > >>My X800 XT is working fine, the only real problem I have with lockups > >>are with Quake 3 and is unrelated. > > > > > > Im a bit dubious your problem not being related as I had some similar problems with q3. > > Could you test if "manytex -size 512 512 -n 100" works? > > It should lock immediately if theres some problem as indirect buffers kept in gart get tampered over by texture uploads. > > > > Looks fine, and no lockup. Alright. Have you been able to reproduce this with any other app? Perhaps if it hits in menus it might be able to track it down but I wouldnt try it otherwise. Also, does it lock always at the same time or is it random? -- Aapo Tahkola |
From: Rune P. <ru...@me...> - 2006-01-08 00:34:07
|
Aapo Tahkola wrote: > On Sat, 07 Jan 2006 23:58:44 +0100 > Rune Petersen <ru...@me...> wrote: > > >>Aapo Tahkola wrote: >> >>>>My X800 XT is working fine, the only real problem I have with lockups >>>>are with Quake 3 and is unrelated. >>> >>> >>>Im a bit dubious your problem not being related as I had some similar problems with q3. >>>Could you test if "manytex -size 512 512 -n 100" works? >>>It should lock immediately if theres some problem as indirect buffers kept in gart get tampered over by texture uploads. >>> >> >>Looks fine, and no lockup. > > > Alright. Have you been able to reproduce this with any other app? > Perhaps if it hits in menus it might be able to track it down but I wouldnt try it otherwise. > Also, does it lock always at the same time or is it random? > No only Quake 3. in-game lockups are rare, most happens when loading maps (might be locking up on the first frame) the worst map is Q3DM0, which might help track it down. Also r_texturebits "32" vs. r_texturebits "16" increases the chance of a lockup. Rune Petersen |
From: Aapo T. <ae...@ra...> - 2006-01-08 01:30:21
Attachments:
q3_render_ign.patch
|
On Sun, 08 Jan 2006 01:33:56 +0100 Rune Petersen <ru...@me...> wrote: > Aapo Tahkola wrote: > > On Sat, 07 Jan 2006 23:58:44 +0100 > > Rune Petersen <ru...@me...> wrote: > > > > > >>Aapo Tahkola wrote: > >> > >>>>My X800 XT is working fine, the only real problem I have with lockups > >>>>are with Quake 3 and is unrelated. > >>> > >>> > >>>Im a bit dubious your problem not being related as I had some similar problems with q3. > >>>Could you test if "manytex -size 512 512 -n 100" works? > >>>It should lock immediately if theres some problem as indirect buffers kept in gart get tampered over by texture uploads. > >>> > >> > >>Looks fine, and no lockup. > > > > > > Alright. Have you been able to reproduce this with any other app? > > Perhaps if it hits in menus it might be able to track it down but I wouldnt try it otherwise. > > Also, does it lock always at the same time or is it random? > > > > No only Quake 3. in-game lockups are rare, most happens when loading > maps (might be locking up on the first frame) the worst map is Q3DM0, > which might help track it down. Also r_texturebits "32" vs. > r_texturebits "16" increases the chance of a lockup. Could you try Q3DM0 with this patch applied to r300_render.c ? It should ignore all rendering commands at around time leaving menu. Let me know if you cant reproduce the lock with it. BTW, "killall -15 quake3.x86; xrandr -s 0" might be handy if it doesnt lock... -- Aapo Tahkola |
From: Benjamin H. <be...@ke...> - 2006-01-06 22:24:44
|
> Is it safe to say that this is only a problem for cards with 256 bit > memory interfaces? From http://en.wikipedia.org/wiki/Radeon_9700_core: > > Radeon 9700 275 256-bit > Radeon 9800 325 256-bit > Radeon 9700 Pro 325 256-bit > Radeon 9800 Pro 380 256-bit > Radeon 9800 XT 412 256-bit > > > Do all these experience the same lockups? > > Then with the X300 - X850, I think it's only the X800 and X850 cards > have 256-bit interfaces, correct? Do X800 cards experience the same > lockups? Interesting... could be a bandwidth setting issue too then. Ben. |
From: Jerome G. <j.g...@gm...> - 2006-01-06 23:36:20
|
On 1/5/06, Benjamin Herrenschmidt <be...@ke...> wrote: > > Have you tried checking what's going on with the card memory map ? > (values of MC_AGP_LOCATION, MC_FB_LOCATION, CONFIG_MEMSIZE, > CONFIG_APER_SIZE, HDP control and how they are munged by X and DRI ? > There is definitely a bug or two lurking around when we have > CONFIG_APER_SIZE smaller than CONFIG_MEMSIZE that might be causing those > lockups). It seems to be related to card memory map, with your patch (radeon mem fix) i have no lockups (at least no during last 10 minutes) but as i update many things and have tweaks in many place i will double check that... In the mean time if more people could test with your patch (even if their regression with it on some hardware) see if this fix the lockup for them. I will also take a closer look at fglrx dump on this configuration. best, Jerome Glisse |
From: Jerome G. <j.g...@gm...> - 2006-01-07 00:03:32
|
On 1/7/06, Jerome Glisse <j.g...@gm...> wrote: > On 1/5/06, Benjamin Herrenschmidt <be...@ke...> wrote: > > > > Have you tried checking what's going on with the card memory map ? > > (values of MC_AGP_LOCATION, MC_FB_LOCATION, CONFIG_MEMSIZE, > > CONFIG_APER_SIZE, HDP control and how they are munged by X and DRI ? > > There is definitely a bug or two lurking around when we have > > CONFIG_APER_SIZE smaller than CONFIG_MEMSIZE that might be causing thos= e > > lockups). > > It seems to be related to card memory map, with your patch > (radeon mem fix) i have no lockups (at least no during last > 10 minutes) but as i update many things and have tweaks > in many place i will double check that... > > In the mean time if more people could test with your patch > (even if their regression with it on some hardware) see if > this fix the lockup for them. More people testing benh patch on radeon 9800 (or any other radeon that used to lockup) are welcome: http://lists.freedesktop.org/archives/xorg/2005-December/011679.html http://lists.freedesktop.org/archives/xorg/2005-December/011717.html It really seems to fix it. I have been on ut2004 for several minutes without a lockups while it used lockup pretty fast the card before. I will give a look a fglrx way to setup all this. best, Jerome Glisse |
From: Benjamin H. <be...@ke...> - 2006-01-07 00:21:08
|
> More people testing benh patch on radeon 9800 (or any other > radeon that used to lockup) are welcome: > > http://lists.freedesktop.org/archives/xorg/2005-December/011679.html > http://lists.freedesktop.org/archives/xorg/2005-December/011717.html > > It really seems to fix it. I have been on ut2004 for several minutes > without a lockups while it used lockup pretty fast the card before. > I will give a look a fglrx way to setup all this. Again, you really want to also check what the kernel DRI does though as it may stomp over your settings. There are lurking bugs in both sides (which is why I can't merge those patches as-is). I'll work on an attempt at fixing both sides soon. Ben. |
From: Boris P. <bo...@za...> - 2006-01-07 00:46:23
|
Jerome Glisse wrote: > On 1/7/06, Jerome Glisse <j.g...@gm...> wrote: > >>On 1/5/06, Benjamin Herrenschmidt <be...@ke...> wrote: >> >>>Have you tried checking what's going on with the card memory map ? >>>(values of MC_AGP_LOCATION, MC_FB_LOCATION, CONFIG_MEMSIZE, >>>CONFIG_APER_SIZE, HDP control and how they are munged by X and DRI ? >>>There is definitely a bug or two lurking around when we have >>>CONFIG_APER_SIZE smaller than CONFIG_MEMSIZE that might be causing those >>>lockups). >> >>It seems to be related to card memory map, with your patch >>(radeon mem fix) i have no lockups (at least no during last >>10 minutes) but as i update many things and have tweaks >>in many place i will double check that... >> >>In the mean time if more people could test with your patch >>(even if their regression with it on some hardware) see if >>this fix the lockup for them. > > > More people testing benh patch on radeon 9800 (or any other > radeon that used to lockup) are welcome: > > http://lists.freedesktop.org/archives/xorg/2005-December/011679.html > http://lists.freedesktop.org/archives/xorg/2005-December/011717.html > > It really seems to fix it. I have been on ut2004 for several minutes > without a lockups while it used lockup pretty fast the card before. > I will give a look a fglrx way to setup all this. > > best, > Jerome Glisse > A bit late to the discussion, but I have a radeon 9800 pro and with r300 and no ati drivers it works really great for a couple of hours straight inside some 3d games. ... Then it locks up. I don't think a 10 minute test is enough. People don't use 3d programs, and especially not games for 10 minutes. I didn't try the patch yet. I'll try it sometime during the week and report what happens. Boris Peterbarg |