From: Matthew <jackdachef@gmail.com>
To: "Bill Davidsen" <davidsen@tmr.com>
Cc: linux-kernel@vger.kernel.org, mingo@chiara.csoma.elte.hu
Subject: Re: [patch/backport] CFS scheduler, -v22, for v2.6.23-rc8, v2.6.22.8, v2.6.21.7, v2.6.20.20
Date: Tue, 2 Oct 2007 11:06:24 +0200 [thread overview]
Message-ID: <e85b9d30710020206w7563d93fp23a09e66ddb319fd@mail.gmail.com> (raw)
In-Reply-To: <47003742.5090604@tmr.com>
> Try setting features to 14. That helps my similar issues.
Hi Bill,
thanks, but unfortunately that didn't help,
with 2.6.23-rc8 it's already set to 29,
it happens with 2.6.23-rc8 & with the new scheduler
what I found out so far:
it definitely is using 3D acceleration:
glxgears -info
GL_RENDERER = GeForce 7600 GT/PCI/SSE2
GL_VERSION = 2.1.1 NVIDIA 100.14.19
GL_VENDOR = NVIDIA Corporation
GL_EXTENSIONS = GL_ARB_color_buffer_float GL_ARB_depth_texture
GL_ARB_draw_buffers GL_ARB_fragment_program
GL_ARB_fragment_program_shadow GL_ARB_fragment_shader
GL_ARB_half_float_pixel GL_ARB_imaging GL_ARB_multisample
GL_ARB_multitexture GL_ARB_occlusion_query GL_ARB_pixel_buffer_object
GL_ARB_point_parameters GL_ARB_point_sprite GL_ARB_shadow
GL_ARB_shader_objects GL_ARB_shading_language_100
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_dot3
GL_ARB_texture_float GL_ARB_texture_mirrored_repeat
GL_ARB_texture_non_power_of_two GL_ARB_texture_rectangle
GL_ARB_transpose_matrix GL_ARB_vertex_buffer_object
GL_ARB_vertex_program GL_ARB_vertex_shader GL_ARB_window_pos
GL_ATI_draw_buffers GL_ATI_texture_float GL_ATI_texture_mirror_once
GL_S3_s3tc GL_EXT_texture_env_add 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_compiled_vertex_array GL_EXT_Cg_shader GL_EXT_depth_bounds_test
GL_EXT_draw_range_elements GL_EXT_fog_coord GL_EXT_framebuffer_blit
GL_EXT_framebuffer_multisample GL_EXT_framebuffer_object
GL_EXT_gpu_program_parameters GL_EXT_multi_draw_arrays
GL_EXT_packed_depth_stencil GL_EXT_packed_pixels
GL_EXT_pixel_buffer_object GL_EXT_point_parameters
GL_EXT_rescale_normal GL_EXT_secondary_color
GL_EXT_separate_specular_color GL_EXT_shadow_funcs
GL_EXT_stencil_two_side GL_EXT_stencil_wrap GL_EXT_texture3D
GL_EXT_texture_compression_s3tc GL_EXT_texture_cube_map
GL_EXT_texture_edge_clamp GL_EXT_texture_env_combine
GL_EXT_texture_env_dot3 GL_EXT_texture_filter_anisotropic
GL_EXT_texture_lod GL_EXT_texture_lod_bias GL_EXT_texture_mirror_clamp
GL_EXT_texture_object GL_EXT_texture_sRGB GL_EXT_timer_query
GL_EXT_vertex_array GL_IBM_rasterpos_clip
GL_IBM_texture_mirrored_repeat GL_KTX_buffer_region GL_NV_blend_square
GL_NV_copy_depth_to_color GL_NV_depth_clamp GL_NV_fence
GL_NV_float_buffer GL_NV_fog_distance GL_NV_fragment_program
GL_NV_fragment_program_option GL_NV_fragment_program2
GL_NV_framebuffer_multisample_coverage GL_NV_half_float
GL_NV_light_max_exponent GL_NV_multisample_filter_hint
GL_NV_occlusion_query GL_NV_packed_depth_stencil
GL_NV_pixel_data_range GL_NV_point_sprite GL_NV_primitive_restart
GL_NV_register_combiners GL_NV_register_combiners2
GL_NV_texgen_reflection GL_NV_texture_compression_vtc
GL_NV_texture_env_combine4 GL_NV_texture_expand_normal
GL_NV_texture_rectangle GL_NV_texture_shader GL_NV_texture_shader2
GL_NV_texture_shader3 GL_NV_vertex_array_range
GL_NV_vertex_array_range2 GL_NV_vertex_program GL_NV_vertex_program1_1
GL_NV_vertex_program2 GL_NV_vertex_program2_option
GL_NV_vertex_program3 GL_NVX_conditional_render
GL_SGIS_generate_mipmap GL_SGIS_texture_lod GL_SGIX_depth_texture
GL_SGIX_shadow GL_SUN_slice_accum
it's some kind of AIGLX:
GLX_EXT_texture_from_pixmap -> nvidia-native handling of compiz
* there are no problems with the metacity window manager
* it only occurs with compiz being enabled
* and it also happens with disabled "fair group cpu scheduler" (with
the new scheduler)
so it might be a problem with either the graphics driver (tainted !)
or the window manager (compiz),
compiz-fusion 0.6 will be out soon so I'll check it out if that will help
if it gotten clear until now:
the old & new cfs scheduler work perfectly fine:
no hickups & the like with default window manager (== metacity)
so the problem might be somewhere else
I'll collect scheduler configuration with the script posted by Ingo in
the next following days
(pretty busy right now)
thanks
Mat
next prev parent reply other threads:[~2007-10-02 9:06 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-29 11:11 Matthew
2007-09-30 15:43 ` Ingo Molnar
[not found] ` <e85b9d30709300943rded9801xddc6ca0a4773ff53@mail.gmail.com>
2007-09-30 16:45 ` Fwd: " Matthew
2007-09-30 17:27 ` Ingo Molnar
2007-09-30 23:54 ` Bill Davidsen
2007-10-02 9:06 ` Matthew [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-09-26 11:13 Ingo Molnar
2007-09-26 13:33 ` S.Çağlar Onur
2007-09-26 13:48 ` Ingo Molnar
2007-09-28 20:26 ` Alejandro Riveira Fernández
2007-09-29 2:20 ` Henrique de Moraes Holschuh
2007-09-29 16:51 ` Alejandro Riveira Fernández
2007-09-30 15:26 ` Ingo Molnar
2007-10-02 18:12 ` Alejandro Riveira Fernández
2007-10-26 18:56 ` [patch/backport] CFS scheduler, -v22, for v2.6.23-rc8, v2.6.22.8,v2.6.21.7, v2.6.20.20 Fortier,Vincent [Montreal]
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=e85b9d30710020206w7563d93fp23a09e66ddb319fd@mail.gmail.com \
--to=jackdachef@gmail.com \
--cc=davidsen@tmr.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@chiara.csoma.elte.hu \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome