dri-devel October 2011

dri-devel@lists.freedesktop.org

82 participants
530 discussions

[Bug 38452] New: ETQW: Renders garbage in some places
by bugzilla-daemon＠freedesktop.org 15 Aug '12

15 Aug '12

https://bugs.freedesktop.org/show_bug.cgi?id=38452 Summary: ETQW: Renders garbage in some places Product: Mesa Version: git Platform: Other OS/Version: All Status: NEW Severity: normal Priority: medium Component: Drivers/Gallium/r600 AssignedTo: dri-devel(a)lists.freedesktop.org ReportedBy: sa(a)whiz.se Created an attachment (id=48141) --> (https://bugs.freedesktop.org/attachment.cgi?id=48141) screenshot of bug As mentioned in bug 35434 there is a glitch in the game ETQW where the screen just renders garbage. It doesn't seem to be related to any settings in the game and is only reproducible on some places in some of the maps. The best description to reproduce the bug is the one given in bug 35434: "I know now exactly where this is reproductible. For example, in "area 22" map, start with Strogg (soldier), you will land on the right of the Strogg base, then just turn left (looking to the Cyclope), and there is artefact (or now freeze&shake). I noted that watching the Cyclope on this map always results in this behavior." I have also provided an apitrace which makes it easy to reproduce the problem: http://dl.dropbox.com/u/28577999/etqw.trace.7z (51M) System environment: -- system architecture: 32-bit -- Linux distribution: Debian unstable -- GPU: REDWOOD -- Model: XFX Radeon HD 5670 1GB -- Display connector: DVI -- xf86-video-ati: 6.14.2 -- xserver: 1.10.2 -- mesa: 2fe39b46e73aea37152777fe11d489e0b1bc3f92 -- drm: 2.4.25 -- kernel: 2.6.39.1 -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.

1 10

[Bug 27942] New: Screen garbled with GeForce 6150 Force 430
by bugzilla-daemon＠bugzilla.kernel.org 14 Aug '12

14 Aug '12

https://bugzilla.kernel.org/show_bug.cgi?id=27942 Summary: Screen garbled with GeForce 6150 Force 430 Product: Drivers Version: 2.5 Platform: All OS/Version: Linux Tree: Mainline Status: NEW Severity: high Priority: P1 Component: Video(DRI - non Intel) AssignedTo: drivers_video-dri(a)kernel-bugs.osdl.org ReportedBy: Larry.Finger(a)lwfinger.net Regression: No Created an attachment (id=45692) --> (https://bugzilla.kernel.org/attachment.cgi?id=45692) Dmesg output with nouveau enabled With kernel 2.6.38-rc2-Linus-00324-g70d1f36 (and earlier), running without a "nomodeset" option in the boot line results in a screen that appears to be sheared. From the colors, etc., it appears to be nearly correct. The lspci -nnkx output for the device is: 00:0d.0 VGA compatible controller [0300]: nVidia Corporation C61 [GeForce 6150SE nForce 430] [10de:03d0] (rev a2) Subsystem: Micro-Star International Co., Ltd. Device [1462:7309] 00: de 10 d0 03 07 00 b0 00 a2 00 00 03 00 00 00 00 10: 00 00 00 de 0c 00 00 c0 00 00 00 00 04 00 00 dd 20: 00 00 00 00 00 00 00 00 00 00 00 00 62 14 09 73 30: 00 00 e4 df 48 00 00 00 00 00 00 00 0a 01 00 00 --- Comment #1 from Larry Finger <Larry.Finger(a)lwfinger.net> 2011-02-01 03:37:39 --- Created an attachment (id=45712) --> (https://bugzilla.kernel.org/attachment.cgi?id=45712) Dmesg output with nouvea disabled with "nomodeset" -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching the assignee of the bug. ------------------------------------------------------------------------------ Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)! Finally, a world-class log management solution at an even better price-free! Download using promo code Free_Logger_4_Dev2Dev. Offer expires February 28th, so secure your free ArcSight Logger TODAY! http://p.sf.net/sfu/arcsight-sfd2d -- _______________________________________________ Dri-devel mailing list Dri-devel(a)lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel

1 4

[Bug 26812] New: Radeon module causes hard reset on modprobe
by bugzilla-daemon＠bugzilla.kernel.org 14 Aug '12

14 Aug '12

https://bugzilla.kernel.org/show_bug.cgi?id=26812 Summary: Radeon module causes hard reset on modprobe Product: Drivers Version: 2.5 Kernel Version: 2.6.37-git9 Platform: All OS/Version: Linux Tree: Mainline Status: NEW Severity: normal Priority: P1 Component: Video(DRI - non Intel) AssignedTo: drivers_video-dri(a)kernel-bugs.osdl.org ReportedBy: mjevans1983(a)gmail.com Regression: No I'm using the git snapshots between when Linus merged from drm-core-next and when network drivers were merged (breaks build). If there is a better patch relative to a released source I'll gladly test it too; however the other sources I tried also had similar issues. When radeon.ko (or build in init) starts the screens blank and a few seconds later the system completely reboots. This is 100% repeatable. I have firmware from Arch's (AUR) linux-firmware-git package installed, /lib/firmware pointed as the source, and the relevant blobs for the recent ATI/AMD GPUs. When built as a module I can modprobe radeon to trigger the exact same behavior. Problems debugging: * It resets so hard there isn't a peep from netconsole. * It resets so hard that my disks loose md raid sync and need to completely rebuild (yeah, I know, I'll add a write-intent log before I test this again next time...; it wasn't an issue before I got the brainwave of making it a module to try to give netconsole/syslog time to get setup.) How can I possibly approach isolating this? Even a link to the correct documentation would be helpful. -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching the assignee of the bug. ------------------------------------------------------------------------------ Protect Your Site and Customers from Malware Attacks Learn about various malware tactics and how to avoid them. Understand malware threats, the impact they can have on your business, and how you can protect your company and customers by using code signing. http://p.sf.net/sfu/oracle-sfdevnl -- _______________________________________________ Dri-devel mailing list Dri-devel(a)lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel

1 7

[Bug 41231] New: GL_INVALID_ENUM when using glxinfo -l
by bugzilla-daemon＠freedesktop.org 08 Aug '12

08 Aug '12

https://bugs.freedesktop.org/show_bug.cgi?id=41231 Summary: GL_INVALID_ENUM when using glxinfo -l Product: Mesa Version: git Platform: x86-64 (AMD64) OS/Version: Linux (All) Status: NEW Severity: minor Priority: medium Component: Drivers/Gallium/r600 AssignedTo: dri-devel(a)lists.freedesktop.org ReportedBy: stefano.teso(a)gmail.com Hi, using git 455a19b1b3d7ca0a40c65d89e45209dbd8ac7b35, and running: $ glxinfo -l > /dev/null makes mesa sad: Mesa: User error: GL_INVALID_ENUM in glGetIntegerv(pname=GL_MAX_COLOR_MATRIX_STACK_DEPTH) Mesa: User error: GL_INVALID_ENUM in glGetConvolutionParameteriv This doesn't happen with stock mesa 7.11, nor when using LIBGL_ALWAYS_SOFTWARE=1. The driver is r600g, the device is: 01:00.0 VGA compatible controller: ATI Technologies Inc Robson CE [AMD Radeon HD 6300 Series] I'm using debian unstable FWIW. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.

1 3

[Bug 40296] New: Bad rendering on madebyevan.com/webgl-water/
by bugzilla-daemon＠freedesktop.org 08 Aug '12

08 Aug '12

https://bugs.freedesktop.org/show_bug.cgi?id=40296 Summary: Bad rendering on madebyevan.com/webgl-water/ Product: Mesa Version: unspecified Platform: Other OS/Version: All Status: NEW Severity: normal Priority: medium Component: Drivers/Gallium/r600 AssignedTo: dri-devel(a)lists.freedesktop.org ReportedBy: jeff(a)infidigm.net 03:00.0 VGA compatible controller: ATI Technologies Inc Redwood [Radeon HD 5670] You can see the problem in the screenshot. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.

1 3

[Bug 37047] New: [RADEON:KMS:R600G] broadbandmap.gov crashes firefox/iceweasel when webgl is enabled
by bugzilla-daemon＠freedesktop.org 08 Aug '12

08 Aug '12

https://bugs.freedesktop.org/show_bug.cgi?id=37047 Summary: [RADEON:KMS:R600G] broadbandmap.gov crashes firefox/iceweasel when webgl is enabled Product: Mesa Version: git Platform: All OS/Version: All Status: NEW Severity: normal Priority: medium Component: Drivers/Gallium/r600 AssignedTo: dri-devel(a)lists.freedesktop.org ReportedBy: bpaterni(a)gmail.com broadbandmap.gov does appear to be making use of webgl if it is exposed. Running iceweasel in debug mode produces the following: Mesa: User error: GL_INVALID_ENUM in glGetIntegerv(pname=GL_MAX_VERTEX_OUTPUT_COMPONENTS) Mesa: User error: GL_INVALID_ENUM in glGetIntegerv(pname=GL_MAX_VERTEX_OUTPUT_COMPONENTS) [New Thread 0x7fffbf7ff700 (LWP 25412)] [New Thread 0x7fffbeffe700 (LWP 25413)] Mesa: User error: GL_INVALID_ENUM in glGetIntegerv(pname=GL_MAX_VERTEX_OUTPUT_COMPONENTS) Program received signal SIGSEGV, Segmentation fault. 0x00007fffc17be5df in dri2FlushFrontBuffer (driDrawable=0x7fffc51bb420, loaderPrivate=0x7fffc2cb7cc0) at dri2_glx.c:460 460 struct glx_display *priv = __glXInitialize(pdraw->base.psc->dpy); (gdb) bt #0 0x00007fffc17be5df in dri2FlushFrontBuffer (driDrawable=0x7fffc51bb420, loaderPrivate=0x7fffc2cb7cc0) at dri2_glx.c:460 #1 0x00007fffc03bd400 in dri_st_framebuffer_flush_front (stfbi=<value optimized out>, statt=<value optimized out>) at dri_drawable.c:104 #2 0x00007fffc03bca34 in dri_unbind_context (cPriv=<value optimized out>) at dri_context.c:152 #3 0x00007fffc039f676 in driUnbindContext (pcp=0x7fffc4b31640) at ../../../../src/mesa/drivers/dri/common/dri_util.c:117 #4 0x00007fffc17be089 in dri2_unbind_context (context=0x7fffc4859a20, new=0x7fffd1d93840) at dri2_glx.c:172 #5 0x00007fffc1795c05 in MakeContextCurrent (dpy=0x7ffff6d76000, draw=25168521, read=25168521, gc_user=0x7fffd1d93840) at glxcurrent.c:258 #6 0x00007ffff56a9b17 in ?? () from /usr/lib/xulrunner-2.0/libxul.so #7 0x00007ffff56a8fd1 in ?? () from /usr/lib/xulrunner-2.0/libxul.so #8 0x00007ffff56a9159 in mozilla::gl::GLContextProviderGLX::CreateOffscreen(gfxIntSize const&, mozilla::gl::ContextFormat const&) () from /usr/lib/xulrunner-2.0/libxul.so #9 0x00007ffff4fe525e in ?? () from /usr/lib/xulrunner-2.0/libxul.so #10 0x00007ffff502b1af in ?? () from /usr/lib/xulrunner-2.0/libxul.so #11 0x00007ffff502b6ba in ?? () from /usr/lib/xulrunner-2.0/libxul.so #12 0x00007ffff5361e78 in ?? () from /usr/lib/xulrunner-2.0/libxul.so #13 0x00007ffff666e9eb in ?? () from /usr/lib/xulrunner-2.0/libmozjs.so #14 0x00007ffff6677fc5 in ?? () from /usr/lib/xulrunner-2.0/libmozjs.so #15 0x00007ffff6679b05 in ?? () from /usr/lib/xulrunner-2.0/libmozjs.so #16 0x00007ffff65f2584 in JS_EvaluateUCScriptForPrincipalsVersion () from /usr/lib/xulrunner-2.0/libmozjs.so #17 0x00007ffff50d954e in ?? () from /usr/lib/xulrunner-2.0/libxul.so #18 0x00007ffff4fbbc2b in ?? () from /usr/lib/xulrunner-2.0/libxul.so #19 0x00007ffff4fbc684 in ?? () from /usr/lib/xulrunner-2.0/libxul.so #20 0x00007ffff4fbd72b in ?? () from /usr/lib/xulrunner-2.0/libxul.so #21 0x00007ffff4fbda54 in ?? () from /usr/lib/xulrunner-2.0/libxul.so #22 0x00007ffff4d43733 in ?? () from /usr/lib/xulrunner-2.0/libxul.so #23 0x00007ffff5640a8b in NS_InvokeByIndex_P () from /usr/lib/xulrunner-2.0/libxul.so #24 0x00007ffff531e216 in ?? () from /usr/lib/xulrunner-2.0/libxul.so #25 0x00007ffff5323402 in ?? () from /usr/lib/xulrunner-2.0/libxul.so #26 0x00007ffff666e9eb in ?? () from /usr/lib/xulrunner-2.0/libmozjs.so #27 0x00007ffff6677fc5 in ?? () from /usr/lib/xulrunner-2.0/libmozjs.so #28 0x00007ffff6678462 in ?? () from /usr/lib/xulrunner-2.0/libmozjs.so #29 0x00007ffff6679313 in ?? () from /usr/lib/xulrunner-2.0/libmozjs.so #30 0x00007ffff65f2011 in JS_CallFunctionValue () from /usr/lib/xulrunner-2.0/libmozjs.so #31 0x00007ffff53190f5 in ?? () from /usr/lib/xulrunner-2.0/libxul.so #32 0x00007ffff5314aa1 in ?? () from /usr/lib/xulrunner-2.0/libxul.so #33 0x00007ffff5641625 in ?? () from /usr/lib/xulrunner-2.0/libxul.so #34 0x00007ffff5640b13 in ?? () from /usr/lib/xulrunner-2.0/libxul.so #35 0x00007fffc70a6720 in ?? () #36 0x00007fffc1c7c850 in ?? () #37 0x00007fffc6da9ce0 in ?? () #38 0x0000000000000000 in ?? () ----System Info---- Debian unstable/experimental running distro provided Linux 2.6.39-rc5-amd64 iceweasel version: 4.0.1-2 libdrm, xf86-video-ati @ git OpenGL renderer string: Gallium 0.4 on AMD RV770 OpenGL version string: 2.1 Mesa 7.11-devel (git-9d792d0) -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.

1 2

[Bug 33255] New: Crash using webgl (firefox 4b9)
by bugzilla-daemon＠freedesktop.org 08 Aug '12

08 Aug '12

https://bugs.freedesktop.org/show_bug.cgi?id=33255 Summary: Crash using webgl (firefox 4b9) Product: Mesa Version: 7.9 Platform: x86-64 (AMD64) OS/Version: Linux (All) Status: NEW Severity: normal Priority: medium Component: Drivers/Gallium/r300 AssignedTo: dri-devel(a)lists.freedesktop.org ReportedBy: 0enjolras0(a)laposte.net hy, I get this error : *********************************WARN_ONCE********************************* File r300_state.c function r300SetupRSUnit line 1521 Don't know how to satisfy InputsRead=0x00004000 *************************************************************************** trying MOZ_GLX_IGNORE_BLACKLIST=1 firefox -P -no-remote on gentoo. setting layers.accelerate-all true in about:config * firefox : Mozilla Firefox 4.0b9 Mozilla i386 build for linux. * OpenGL vendor string: X.Org R300 Project OpenGL renderer string: Gallium 0.4 on RS690 * kernel 2.6.36 vanilla. regards. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.

1 7

[Bug 33635] New: RV620 : Webgl : conformance-tests : 5248/5325 , firefox 4b10
by bugzilla-daemon＠freedesktop.org 08 Aug '12

08 Aug '12

https://bugs.freedesktop.org/show_bug.cgi?id=33635 Summary: RV620 : Webgl : conformance-tests : 5248/5325 , firefox 4b10 Product: Mesa Version: git Platform: Other OS/Version: All Status: NEW Severity: normal Priority: medium Component: Drivers/Gallium/r600 AssignedTo: dri-devel(a)lists.freedesktop.org ReportedBy: aderumier(a)odiso.com Hi, not sure is the good place to post result of WebGL Conformance Test Runner, but it's my results with RV620 chipset, r600g with all git from today. Results: (5248 of 5325 passed, 3 timed out) conformance/context-lost-restored.html(*timeout*) conformance/gl-get-active-attribute.html (15 of 16 passed) failed: successfullyParsed should be true. Threw exception ReferenceError: successfullyParsed is not defined conformance/gl-get-calls.html (72 of 75 passed) failed: context.getParameter(context.MAX_FRAGMENT_UNIFORM_VECTORS) >= 16 should be true. Was false. failed: context.getParameter(context.MAX_VARYING_VECTORS) >= 8 should be true. Was false. failed: context.getParameter(context.MAX_VERTEX_UNIFORM_VECTORS) >= 128 should be true. Was false. conformance/gl-getshadersource.html (1 of 3 passed) failed: source should be abc//defＮＯＴＡＳＣＩＩ. Was . failed: getError expected: NO_ERROR. Was INVALID_VALUE : Should be no errors. conformance/gl-min-attribs.html (2 of 3 passed) failed: Should render 255,127,64,32 conformance/gl-min-uniforms.html (4 of 6 passed) failed: Should render 255,127,64,32 failed: Should render 32,64,127,255 conformance/gl-uniform-arrays.html (68 of 76 passed) failed: value put in (15) matches value pulled out (16) failed: value put in (14) matches value pulled out (16) failed: value put in ([14, 13]) matches value pulled out ([16, 15]) failed: value put in ([12, 11]) matches value pulled out ([16, 15]) failed: value put in ([13, 12, 11]) matches value pulled out ([16, 15, 14]) failed: value put in ([10, 9, 8]) matches value pulled out ([16, 15, 14]) failed: value put in ([12, 11, 10, 9]) matches value pulled out ([16, 15, 14, 13]) failed: value put in ([8, 7, 6, 5]) matches value pulled out ([16, 15, 14, 13]) conformance/glsl-conformance.html (102 of 104 passed) failed: [vshader/fshaderWith256CharacterIdentifier]: shared that uses 256 character identifier should succeed failed: [shaders/misc/non-ascii-comments.vert/fshader]: Non ascii comments in source should succeed conformance/invalid-passed-params.html (50 of 74 passed) failed: context.getError() should be 1281. Was 0. failed: context.getError() should be 1281. Was 0. failed: context.getError() should be 1281. Was 0. failed: context.getError() should be 1281. Was 0. failed: context.getError() should be 1281. Was 0. failed: context.getError() should be 1281. Was 0. failed: context.getError() should be 1281. Was 0. failed: context.getError() should be 1281. Was 0. failed: context.getError() should be 1281. Was 0. failed: context.getError() should be 1281. Was 0. failed: context.getError() should be 1281. Was 0. failed: context.getError() should be 1281. Was 0. failed: context.getError() should be 1281. Was 0. failed: context.getError() should be 1281. Was 0. failed: context.getError() should be 1281. Was 0. failed: context.getError() should be 1281. Was 0. failed: context.getError() should be 1281. Was 0. failed: context.getError() should be 1281. Was 0. failed: context.getError() should be 1281. Was 0. failed: context.getError() should be 1281. Was 0. failed: context.getError() should be 1281. Was 0. failed: context.getError() should be 1281. Was 0. failed: context.getError() should be 1281. Was 0. failed: context.getError() should be 1281. Was 0. conformance/oes-standard-derivatives.html (7 of 8 passed) failed: successfullyParsed should be true. Threw exception ReferenceError: successfullyParsed is not defined conformance/point-size.html (1 of 2 passed) failed: Drawing a point of size 1 touched pixels that should not be touched conformance/read-pixels-test.html (121 of 125 passed) failed: getError expected: INVALID_OPERATION. Was INVALID_ENUM : Should not be able to read as RGB / UNSIGNED_BYTE failed: getError expected: INVALID_OPERATION. Was INVALID_ENUM : Should not be able to read as RGBA / UNSIGNED_SHORT_5_5_5_1 failed: getError expected: INVALID_OPERATION. Was INVALID_ENUM : Should not be able to read as RGBA / UNSIGNED_SHORT_4_4_4_4 failed: getError expected: INVALID_OPERATION. Was INVALID_ENUM : Should not be able to read as ALPHA / UNSIGNED_BYTE conformance/tex-image-and-sub-image-2d-with-video.html(*timeout*) conformance/texture-npot.html (25 of 26 passed) failed: POT cubemap with TEXTURE_MIN_FILTER set to LINEAR_MIPMAP_LINEAR should draw conformance/uniform-location.html (24 of 25 passed) failed: contextA.getUniform(programS, locationArray1) should be 5. Was 4. conformance/uninitialized-test.html (16 of 19 passed) failed: non-zero pixel values are wrong failed: non-zero pixel values are wrong failed: non-zero pixel values are wrong conformance/webgl-specific.html (31 of 40 passed) failed: gl.stencilMaskSeparate(gl.FRONT, 1) expected: NO_ERROR. Was INVALID_OPERATION. failed: gl.drawArrays(gl.TRIANGLES, 0, 0) expected: INVALID_OPERATION. Was NO_ERROR. failed: gl.stencilMaskSeparate(gl.BACK, 1) expected: NO_ERROR. Was INVALID_OPERATION. failed: gl.stencilFuncSeparate(gl.BACK, gl.ALWAYS, 1, 255) expected: NO_ERROR. Was INVALID_OPERATION. failed: gl.drawArrays(gl.TRIANGLES, 0, 0) expected: INVALID_OPERATION. Was NO_ERROR. failed: gl.stencilFuncSeparate(gl.FRONT, gl.ALWAYS, 1, 255) expected: NO_ERROR. Was INVALID_OPERATION. failed: gl.stencilFuncSeparate(gl.BACK, gl.ALWAYS, 1, 1) expected: NO_ERROR. Was INVALID_OPERATION. failed: gl.drawArrays(gl.TRIANGLES, 0, 0) expected: INVALID_OPERATION. Was NO_ERROR. failed: gl.stencilFuncSeparate(gl.FRONT, gl.ALWAYS, 1, 1) expected: NO_ERROR. Was INVALID_OPERATION. more/conformance/quickCheckAPI.html (0 of 1 passed) failed: testValidArgs more/conformance/webGLArrays.html(*timeout*) more/functions/copyTexImage2D.html (1 of 2 passed) failed: testRoundtrip more/functions/copyTexSubImage2D.html (1 of 2 passed) failed: testRoundtrip more/functions/copyTexSubImage2DBadArgs.html (0 of 1 passed) failed: testTexImage2D more/functions/deleteBufferBadArgs.html (0 of 1 passed) failed: testDeleteBuffer more/functions/texImage2DBadArgs.html (0 of 1 passed) failed: testTexImage2D more/functions/texSubImage2DBadArgs.html (0 of 1 passed) failed: testTexImage2D more/functions/texSubImage2DHTMLBadArgs.html (0 of 1 passed) failed: testTexImage2D more/functions/uniformiBadArgs.html (0 of 1 passed) failed: testUniformf more/functions/uniformMatrixBadArgs.html (0 of 1 passed) failed: testUniformf more/functions/vertexAttribBadArgs.html (0 of 1 passed) failed: testVertexAttrib -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.

1 1

[Bug 33867] New: [bisected] Graphics corruption related to pageflip ioctl support in 2.6.38-rc*
by bugzilla-daemon＠freedesktop.org 22 Jul '12

22 Jul '12

https://bugs.freedesktop.org/show_bug.cgi?id=33867 Summary: [bisected] Graphics corruption related to pageflip ioctl support in 2.6.38-rc* Product: DRI Version: DRI CVS Platform: x86-64 (AMD64) OS/Version: Linux (All) Status: NEW Severity: normal Priority: medium Component: DRM/Radeon AssignedTo: dri-devel(a)lists.freedesktop.org ReportedBy: dawitbro(a)sbcglobal.net Created an attachment (id=42887) --> (https://bugs.freedesktop.org/attachment.cgi?id=42887) Commits not present in 2.6.37 applied to local branch I am troubleshooting some graphics corruption I noticed when testing the post-2.6.37 commits from drm-airlied git (drm-fixes in this case). I was trying to produce a kernel as close as possible to the latest stable release (since 2.6.38 is very early in the rc stage) with all of the newest radeon-related features. This is a preliminary report, and may turn out to be invalid, because the kernel I am using is actually a local branch from v2.6.37 with only the commits from drm-airlied relevant to my hardware individually cherry-picked. I have bisected the problem down to a specific commit, but if I made any errors during the cherry-pick process then this report is useless. I plan to confirm that the problem is real tomorrow, by building directly from the drm-airlied/drm-fixes tree (which was the most up-to-date tree I could find today). As I will report below, there is some similarity with https://bugs.freedesktop.org/show_bug.cgi?id=33515 and that is the only reason I decided to report my findings before I am really sure there is a problem. Hopefully this will help Michel and other devs save some time and trouble if my guess (that my bug is related) turns out to be correct. ---------------------- OK, here is what I have done so far: 1. I made a local git branch based on v2.6.37. 2. I identified commits I wanted from drm-airlied/drm-fixes (Feb. 2, 2011) 3. Because of GPU lockups recently cured by Alex Deucher, I picked one particular commit first (1e644d6d, "drm/radeon/kms: re-emit full context state for evergreen blits"); without this, testing would be pointless since my GPU would just lock up when trying and 3D app. 4. I then cherry-picked the rest of the commits I had chosen, in order from oldest to newest (according to 'git log'). See attached file, 'applied-cherry-picks.txt', if interested in specifics. Everything actually seemed to be working fine; I only happened to notice a small glitch. I use a locally-built game called 'prboom-plus' with my original Ultimate DOOM WAD file to test Radeon support (in kernels, Mesa, xf86-video-ati, etc.). When a game begins, there is a melt-down animation which transitions into the new game; there is a similar (I would have guessed identical before) melting effect when the player is killed but hits the space bar to restart the game. In this second melting effect, after being killed, the "melted" part of the screen was all black, a clear regression. Before today's testing, I had been using a straight 2.6.37 kernel with the patch from Alex I mentioned in item 3 above. With that kernel, both melting effects work fine. That seems to rule out a problem with xorg-server, mesa, libdrm, or xf86-video-ati. I decided to try bisecting the issue. I built kernels from the first and last commits listed in the attached file: 1e644d6d and dca0d612. The former was "good" and the latter "bad". The bisect jumped to 204663c4 and 18007401 next -- both were "bad". The next jump, 65705962, caused 'prboom-plus' to hang during the second kind of melting; I was able to SSH into the machine and 'kill -9' the game. Since there was a series of TTM related changes in that series of commits, I used 'git bisect skip' until I was presented with a commit before or after the TTM series; I tested the kernels (all hung on the second melt), but told git to skip them; the ones I pretended to skip were eba67093, 95762c2b, and 702adba2. I was offered 147666fb, and it was "bad" but did not hang during the second kind of melt. Continuing, the bisect took me back to 2357cbe5, which hung X so that it could not be killed with 'kill -9'; I had to reboot via SSH. I skipped ecf7ace9 and 68c4fa31 without building kernels. The bisect then went to d6ea8886 and b6724405, which hung (so I pretended to skip them). I skipped 96726fe50 without building. The bisect moved to 3e4ea742, which hung, and 6f34be50, which also hung. Interestingly, f5a80209 was perfectly OK. This meant that the last commit I tested was the first bad commit. I had been skipping the commits causing hangs because I expected the hang to be a temporary problem resolved somewhere in the middle of the list; I believed this because of the fact the first and last commits in my list did _not_ produce hanging kernels. Of course, I was actually building most of the kernels that I "skipped", so I knew they were "bad" even if git did not. To sum up. the first three cherry-picks (applied to v2.6.37) were fine: 1e644d6dce366a7bae22484f60133b61ba322911 drm/radeon/kms: re-emit full context state for evergreen blits 27641c3f003e7f3b6585c01d8a788883603eb262 drm/vblank: Add support for precise vblank timestamping. f5a8020903932624cf020dc72455a10a3e005087 drm/kms/radeon: Add support for precise vblank timestamping. The commit which introduced the hangs -- and these happened entirely predictably and consistently: when the second kind of "melt" in 'prboom-plus' occurs -- was 6f34be50bd1bdd2ff3c955940e033a80d05f248a drm/radeon/kms: add pageflip ioctl support (v3) After a series of several TTM-related commits, the hanging was resolved and the second kind of melt would display in all black instead, beginning at this commit: 147666fb3b93b8c484f562da33a37f886ddff768 drm/radeon: Use the ttm execbuf utilities As I mentioned above, these results are preliminary; I will try builds directly from drm-airlied tomorrow since we are snowed-in here in Michigan, and I don't have to work tomorrow. My problems with hangs sound very similar to f.d.o. bug #33515. This may also be related to #33418, since that user (Erdem) is using 2.6.38-rc1. Hardware: Radeon HD 5750 (Evergreen JUNIPER) Software: kernel 2.6.37 + commits as described above libdrm 2.4.23 xorg-server 1.9.3.902 xf86-video-ati 6.13.99 (git commit 3dc28c86 of Jan. 27) mesa 7.11.0 (git commit 11b15c4d of Jan 30), r600g -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.

1 16

[Bug 35192] New: BUG() in radeon driver with ATI Technologies Inc RV515 [Radeon X1300]
by bugzilla-daemon＠bugzilla.kernel.org 13 Jun '12

13 Jun '12

https://bugzilla.kernel.org/show_bug.cgi?id=35192 URL: http://bugs.gentoo.org/show_bug.cgi?id=359281 Summary: BUG() in radeon driver with ATI Technologies Inc RV515 [Radeon X1300] Product: Drivers Version: 2.5 Kernel Version: 2.6.37 and 2.6.38 Platform: All OS/Version: Linux Tree: Mainline Status: NEW Severity: normal Priority: P1 Component: Video(DRI - non Intel) AssignedTo: drivers_video-dri(a)kernel-bugs.osdl.org ReportedBy: blueness(a)gentoo.org Regression: Yes A regression in kernels 2.6.37 up to 2.6.38.6 hits a BUG() in the radeon driver with the following hardware (as reported by lspci -kv) 02:00.0 VGA compatible controller: ATI Technologies Inc RV515 [Radeon X1300] (prog-if 00 [VGA controller]) Subsystem: ATI Technologies Inc All-in-Wonder 2006 PCI-E Edition Flags: bus master, fast devsel, latency 0, IRQ 40 Memory at e0000000 (64-bit, prefetchable) [size=256M] Memory at fd9f0000 (64-bit, non-prefetchable) [size=64K] I/O ports at ce00 [size=256] Expansion ROM at fd9c0000 [disabled] [size=128K] Capabilities: [50] Power Management version 2 Capabilities: [58] Express Endpoint, MSI 00 Capabilities: [80] MSI: Enable+ Count=1/1 Maskable- 64bit+ Kernel driver in use: radeon The BUG() is kernel tried to execute NX-protected page - exploit attempt? (uid: 0) BUG: unable to handle kernel paging request at ffffffff81c0e711 IP: [<ffffffff81c0e711>] platform_device_register_resndata+0x0/0x8c PGD 1ae5067 PUD 1ae9063 PMD 3c473063 PTE 8000000001c0e163 Oops: 0011 [#1] SMP last sysfs file: /sys/devices/system/cpu/cpu1/cache/index2/shared_cpu_map CPU 0 Pid: 1627, comm: X Tainted: G W 2.6.38.6 #1 HP Pavilion 061 ER900AA-ABA a1430n/NAGAMI RIP: 0010:[<ffffffff81c0e711>] [<ffffffff81c0e711>] platform_device_register_resndata+0x0/0x8c RSP: 0018:ffff88003a2b3d30 EFLAGS: 00010246 RAX: 0000000000000000 RBX: ffff88003cb81000 RCX: 0000000000000000 RDX: 0000000000000000 RSI: ffffffff81a41cbb RDI: 0000000000000000 RBP: ffff88003a2b3d88 R08: 0000000000000000 R09: 0000000000000000 R10: ffff88003a340000 R11: 00000000effff000 R12: 0000000000000000 R13: ffff88003cb80800 R14: ffff88003abeaa80 R15: 0000000000000001 FS: 00007f40b4c72880(0000) GS:ffff88003fc00000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: ffffffff81c0e711 CR3: 000000003a2a8000 CR4: 00000000000006f0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400 Process X (pid: 1627, threadinfo ffff88003a2b2000, task ffff88003d3ef1a0) Stack: ffffffff8133aa29 0000000000000000 0000000000000001 ffff88003a2b3de8 ffffffff811681fc ffff88003a2b3df8 ffff88003abeaa80 ffff88003cb80800 0000000000000040 0000000040786440 0000000000000078 ffff88003a2b3ea8 Call Trace: [<ffffffff8133aa29>] ? radeon_cp_init+0xd79/0x1180 [<ffffffff811681fc>] ? ext4_file_write+0x6c/0x2a0 [<ffffffff81317439>] drm_ioctl+0x389/0x4d0 [<ffffffff81339cb0>] ? radeon_cp_init+0x0/0x1180 [<ffffffff8110ddfb>] do_vfs_ioctl+0x9b/0x510 [<ffffffff8110e2bf>] sys_ioctl+0x4f/0x80 [<ffffffff81002e2b>] system_call_fastpath+0x16/0x1b Code: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 <00> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 RIP [<ffffffff81c0e711>] platform_device_register_resndata+0x0/0x8c RSP <ffff88003a2b3d30> CR2: ffffffff81c0e711 ---[ end trace f569524e57c84b79 ]--- More detail is avaiable in the following gentoo bug: http://bugs.gentoo.org/show_bug.cgi?id=359281 We're looking into doing the git-bisect now. -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching the assignee of the bug. ------------------------------------------------------------------------------ Achieve unprecedented app performance and reliability What every C/C++ and Fortran developer should know. Learn how Intel has extended the reach of its next-generation tools to help boost performance applications - inlcuding clusters. http://p.sf.net/sfu/intel-dev2devmay -- _______________________________________________ Dri-devel mailing list Dri-devel(a)lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel

1 9

← Newer
1
...
26
27
28
29
30
31
32
...
53
Older →

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

dri-devel October 2011