dri-devel February 2011

dri-devel@lists.freedesktop.org

84 participants
466 discussions

[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 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 30383] New: r600c: GPU lockup / driver hang when playing ufoai
by bugzilla-daemon＠freedesktop.org 02 May '12

02 May '12

https://bugs.freedesktop.org/show_bug.cgi?id=30383 Summary: r600c: GPU lockup / driver hang when playing ufoai Product: Mesa Version: git Platform: Other OS/Version: All Status: NEW Severity: normal Priority: medium Component: Drivers/DRI/R600 AssignedTo: dri-devel(a)lists.freedesktop.org ReportedBy: edwintorok(a)gmail.com Kernel bug reported here: https://bugzilla.kernel.org/show_bug.cgi?id=19102 Trying to play this game: ufoai.ninex.info, as soon as you choose to enter a mission there is a GPU lockup and then the radeon driver hangs. It is impossible to switch to the console, or otherwise kill the game at this point. I can ssh in, but there is no way to get back X into a working state (or killing it either). Only a reboot helps. This happens using r600 classic driver from git mesa. Tried it twice: locked up system both times. -- 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 29412] New: fans running at full-speed after resume from suspend with radeon and KMS
by bugzilla-daemon＠bugzilla.kernel.org 16 Apr '12

16 Apr '12

https://bugzilla.kernel.org/show_bug.cgi?id=29412 Summary: fans running at full-speed after resume from suspend with radeon and KMS Product: Drivers Version: 2.5 Kernel Version: 2.6.38-rc5+ 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: jon+bugzilla.kernel.org(a)alcopop.org Regression: No Hi, Originally reported against the wrong product, here: https://bugzilla.kernel.org/show_bug.cgi?id=18552 I have an ATI Radeon X850XT PCIE card plugged into an Intel DG35EC motherboard. With kernels since 2.6.32-rc1 and most recently tested with mainline commit 2a324ce7b79a3a90cc2d4ade5d5f960a99000caa (2.6.38-rc5+), if I attempt a suspend-to-ram, upon resume, the fan on my ATI card remains at full speed (loud), and does not throttle back to quiet (normal behaviour). Booting with 'radeon.modeset=0' prevents this. Please let me know what further information is needed. Thanks! -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching the assignee of the bug. ------------------------------------------------------------------------------ The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: Pinpoint memory and threading errors before they happen. Find and fix more than 250 security defects in the development cycle. Locate bottlenecks in serial and parallel code that limit performance. http://p.sf.net/sfu/intel-dev2devfeb -- _______________________________________________ Dri-devel mailing list Dri-devel(a)lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel

1 18

Re: 2.6.35-rc4 Graphics performance issue and freeing invalid memtype messages on boot.
by Andrew Morton 03 Apr '12

03 Apr '12

(Rafael, Maciej: two probably-separate post-2.6.34 regressions here) On Tue, 06 Jul 2010 22:22:17 +1000 Andrew Hendry <andrew.hendry(a)gmail.com> wrote: > > Some extra messages when booting with -rc4. Didn't get them in -rc3. > [ 1.387013] swapper:1 freeing invalid memtype bf788000-bf789000 > [ 1.387409] swapper:1 freeing invalid memtype bf789000-bf78a000 > [ 5.999675] modprobe:548 freeing invalid memtype d0000000-d0040000 > [ 6.068347] modprobe:548 freeing invalid memtype d0140000-d0150000 > [ 6.068647] modprobe:548 freeing invalid memtype d0150000-d0160000 > [ 6.069661] modprobe:548 freeing invalid memtype d0170000-d01f0000 > [ 6.085969] modprobe:548 freeing invalid memtype d01f0000-d0200000 > [ 6.087673] modprobe:548 freeing invalid memtype d0210000-d0220000 > [ 6.087900] modprobe:548 freeing invalid memtype d0220000-d0230000 > [ 6.088092] modprobe:548 freeing invalid memtype d0230000-d0240000 > [ 6.088317] modprobe:548 freeing invalid memtype d0240000-d0250000 hrmpf, one of those wonderful messages where neither it nor its source code give you any clue regarding what caused it nor how to fix it. please, apply this: --- a/arch/x86/mm/pat.c~a +++ a/arch/x86/mm/pat.c @@ -359,7 +359,7 @@ int free_memtype(u64 start, u64 end) entry = rbt_memtype_erase(start, end); spin_unlock(&memtype_lock); - if (!entry) { + if (WARN_ON(!entry)) { printk(KERN_INFO "%s:%d freeing invalid memtype %Lx-%Lx\n", current->comm, current->pid, start, end); return -EINVAL; and let's at least see where it's coming from. > Not sure if its related, but also have a noticeable performance issue with graphics under rc4. > Dragging and resizing windows, screen updates, and jumpy cursor are all slow. > Playing a full screen video under vlc gets only 1-2 frames per second, but plays fine under rc3. > Tested a kernel compile, it was roughly the same. > Userspace is ubunutu 10.04 64bit. > > Any hints? Otherwise will start a bisect tomorrow night. > > Config attached, lspci, rc3 and rc4 boot messages below: What graphics hardware are you using?

3 3

[Bug 27922] New: setting graphics mode for text console with video= instead of vga= does not work
by bugzilla-daemon＠bugzilla.kernel.org 05 Mar '12

05 Mar '12

https://bugzilla.kernel.org/show_bug.cgi?id=27922 Summary: setting graphics mode for text console with video= instead of vga= does not work Product: Drivers Version: 2.5 Kernel Version: 2.6.38-0.0.7 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: estellnb(a)gmail.com Regression: No I have stated "video=1920x1200-24@60" on my kernel command line. Instead it initializes a 80x25 text console with a low resolution of sth. like 640x480 or so. The video kernel command line is said to be the future replacement of vga= modes by the Xorg development team (vga= is said to be no more compatible with Xorg`s video mode initialization). Is it already implemented? If yes a fallback to a similar Vesa graphics mode with Vesa safe/restore mode on vt-switch may be an additional opportunity. occurs with and without kernel modesetting. -- 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 3

[Bug 34457] New: Radeon Driver reports EDID errors every 10 seconds
by bugzilla-daemon＠freedesktop.org 29 Feb '12

29 Feb '12

https://bugs.freedesktop.org/show_bug.cgi?id=34457 Summary: Radeon Driver reports EDID errors every 10 seconds Product: DRI Version: unspecified Platform: x86-64 (AMD64) OS/Version: Linux (All) Status: NEW Severity: major Priority: medium Component: DRM/Radeon AssignedTo: dri-devel(a)lists.freedesktop.org ReportedBy: nsun.freesoul(a)gmail.com Created an attachment (id=43526) --> (https://bugs.freedesktop.org/attachment.cgi?id=43526) dmesg Radeon Driver reports EDID errors every 10 seconds, which causes related log files increased over 100M in size every day. OS: Ubuntu Maverick 10.10 Desktop Kernel_version: Ubuntu 2.6.35-25.44-generic 2.6.35.10 Mother Board: ECS A740GM-M Chipset: AMD 740G, integrated ATI Radeon 2100 -- 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

← Newer
1
...
10
11
12
13
14
15
16
...
47
Older →

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

dri-devel February 2011