Clutter run time error on Gallium RV350
Hello, I'm trying to jhbuild gnome-shell with a fedora 14 and an ATI radeon 9600 card. I can configure and make clutter library but then "make check" test shows a runtime issue . The standalone test which fails is "test_texture_pick_with_alpha". The full output of this test is attached. I was told on IRC it should be a driver issue. kernel-PAE.i686 2.6.35.11-83.fc14 mesa-dri-drivers.i686 7.9-5.fc14 -- next part -- [makerpm at localhost clutter]$ CLUTTER_DEBUG=all ./tests/conform/wrappers/test-texture-pick-with-alpha /conform/texture/test_texture_pick_with_alpha: Clutter-Message: [BACKEND] ./x11/clutter-backend-x11.c:357: XOpenDisplay on ':1.0' Clutter-Message: [BACKEND] ./x11/clutter-backend-x11.c:385: Getting the X screen Clutter-Message: [BACKEND] ./clutter-settings.c:174: New resolution: 96.00 Clutter-Message: [BACKEND] ./clutter-backend.c:194: Units per em: 14.40 Clutter-Message: [BACKEND] ./x11/clutter-backend-x11.c:274: Creating Core device manager Clutter-Message: [BACKEND] ./x11/clutter-device-manager-core-x11.c:600: Added core pointer device Clutter-Message: [BACKEND] ./x11/clutter-device-manager-core-x11.c:612: Added core keyboard device Clutter-Message: [MISC] ./clutter-input-device.c:1347: Associating device 'Core Pointer' to device 'Core Keyboard' Clutter-Message: [MISC] ./clutter-input-device.c:1347: Associating device 'Core Keyboard' to device 'Core Pointer' Clutter-Message: [BACKEND] ./x11/clutter-keymap-x11.c:263: Detectable autorepeat: supported Clutter-Message: [BACKEND] ./x11/clutter-backend-x11.c:210: Mapping XSETTING 'Gtk/FontName' to 'ClutterSettings:font-name' Clutter-Message: [BACKEND] ./clutter-settings.c:166: New font-name: Sans 8 Clutter-Message: [BACKEND] ./clutter-backend.c:205: Units per em: 9.60 Clutter-Message: [BACKEND] ./x11/clutter-backend-x11.c:210: Mapping XSETTING 'Net/DoubleClickTime' to 'ClutterSettings:double-click-time' Clutter-Message: [BACKEND] ./x11/clutter-backend-x11.c:210: Mapping XSETTING 'Xft/Antialias' to 'ClutterSettings:font-antialias' Clutter-Message: [BACKEND] ./clutter-settings.c:157: New font options: - font-name: Sans 8 - antialias: 1 - hinting:-1 - hint-style: - rgba: - dpi:96.00 Clutter-Message: [BACKEND] ./clutter-backend.c:205: Units per em: 9.60 Clutter-Message: [BACKEND] ./x11/clutter-backend-x11.c:210: Mapping XSETTING 'Xft/DPI' to 'ClutterSettings:font-dpi' Clutter-Message: [BACKEND] ./clutter-settings.c:174: New resolution: 96.21 Clutter-Message: [BACKEND] ./clutter-backend.c:194: Units per em: 9.64 Clutter-Message: [BACKEND] ./x11/clutter-backend-x11.c:210: Mapping XSETTING 'Xft/HintStyle' to 'ClutterSettings:font-hint-style' Clutter-Message: [BACKEND] ./clutter-settings.c:157: New font options: - font-name: Sans 8 - antialias: 1 - hinting:-1 - hint-style: hintslight - rgba: - dpi:96.21 Clutter-Message: [BACKEND] ./clutter-backend.c:205: Units per em: 9.64 Clutter-Message: [BACKEND] ./x11/clutter-backend-x11.c:210: Mapping XSETTING 'Xft/Hinting' to 'ClutterSettings:font-hinting' Clutter-Message: [BACKEND] ./clutter-settings.c:157: New font options: - font-name: Sans 8 - antialias: 1 - hinting:1 - hint-style: hintslight - rgba: - dpi:96.21 Clutter-Message: [BACKEND] ./clutter-backend.c:205: Units per em: 9.64 Clutter-Message: [BACKEND] ./x11/clutter-backend-x11.c:210: Mapping XSETTING 'Xft/RGBA' to 'ClutterSettings:font-subpixel-order' Clutter-Message: [BACKEND] ./clutter-settings.c:157: New font options: - font-name: Sans 8 - antialias: 1 - hinting:1 - hint-style: hintslight - rgba: none - dpi:96.21 Clutter-Message: [BACKEND] ./clutter-backend.c:205: Units per em: 9.64 Clutter-Message: [BACKEND] ./x11/clutter-backend-x11.c:461: X Display ':1.0'[0x990b700] opened (screen:0, root:330, dpi:96.212891) Clutter-Message: [MISC] ./clutter-feature.c:92: checking features Clutter-Message: [MISC] ./clutter-feature.c:96: allocating features data Clutter-Message: [BACKEND] ./glx/clutter-backend-glx.c:443: Retrieving GL fbconfig, dpy: 0x990b700, xscreen; 0x9915cc8 (0) Clutter-Message: [BACKEND] ./glx/clutter-backend-glx.c:485: Using the first available FBConfig Clutter-Message: [BACKEND] ./glx/clutter-backend-glx.c:579: Creating GLX Context (display: 0x990b700) Clutter-Message: [GL] ./glx/clutter-backend-glx.c:598: Setting direct context Clutter-Message: [BACKEND] ./glx/clutter-backend-glx.c:657: Selecting dummy 0x3a4 for the GLX context Clutter-Message: [BACKEND] ./glx/clutter-backend-glx.c:248: Checking features GL_VENDOR: X.Org R300 Project GL_RENDERER: Gallium 0.4 on RV350 GL_VERSION: 2.1 Mesa 7.9 GL_EXTENSIONS: GL_ARB_copy_buffer GL_ARB_depth_texture GL_ARB_draw_buffers GL_ARB_draw_elements_base_vertex GL_ARB_fragment_coord_conventions GL_ARB_fragment_program GL_ARB_fragment_program_shadow GL_ARB_fragment_shader GL_ARB_framebuffer_obje
2.6.38-rc5-git6: Reported regressions 2.6.36 -> 2.6.37
[NOTE: Can maintainers _please_ merge patches listed below, especially those that have been known for weeks?] This message contains a list of some post-2.6.36 regressions introduced before 2.6.37, for which there are no fixes in the mainline known to the tracking team. If any of them have been fixed already, please let us know. If you know of any other unresolved post-2.6.36 regressions, please let us know either and we'll add them to the list. Also, please let us know if any of the entries below are invalid. Each entry from the list will be sent additionally in an automatic reply to this message with CCs to the people involved in reporting and handling the issue. Listed regressions statistics: Date Total Pending Unresolved 2011-02-21 128 35 26 2011-02-13 126 36 30 2011-02-03 118 36 31 2010-12-30 85 32 26 2010-12-19 73 28 24 2010-12-03 55 25 19 2010-11-19 39 29 25 Unresolved regressions -- Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=29172 Subject : releasing loop on top of other loop leads to deadlock Submitter : Petr Uzel Date: 2011-02-15 10:00 (7 days old) Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=28812 Subject : DVI attached monitor is turned off while booting linux 2.6.37 and higher Submitter : Markus Heinz Date: 2011-02-10 19:33 (12 days old) Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=28772 Subject : oops in nfs_revalidate_mapping Submitter : Daniel Poelzleithner Date: 2011-02-10 13:59 (12 days old) Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=28662 Subject : i915 in kernel 2.6.38-rc4, high number of wakeups Submitter : Kan-Ru Chen Date: 2011-02-09 07:06 (13 days old) Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=28622 Subject : radeon video lockup Submitter : Daniel Poelzleithner Date: 2011-02-08 17:48 (14 days old) Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=28612 Subject : regular soft lockup Submitter : Alexandre Demers Date: 2011-02-08 16:39 (14 days old) Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=28582 Subject : whole system hang when start X Submitter : Gu Rui Date: 2011-02-08 08:33 (14 days old) First-Bad-Commit: http://git.kernel.org/linus/d5bb081b027b520f9e59b4fb8faea83a136ec15e Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=28332 Subject : [RV620] Can not re-enable LVDS after using HDMI only Submitter : Rafa? Mi?ecki Date: 2011-02-05 22:42 (17 days old) Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=27892 Subject : SNB: GPU hang with Slip xscreensaver Submitter : Takashi Iwai Date: 2011-01-31 12:06 (22 days old) Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=27842 Subject : [regression?] hang with 2.6.37 on a BTRFS test machine Submitter : Martin Steigerwald Date: 2011-01-23 12:06 (30 days old) Message-ID : <<201101231306.23069.Martin at lichtvoll.de>> References : http://marc.info/?l=linux-kernel&m=129578445613283&w=2 Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=27642 Subject : 2.6.37 says WARNING: at arch/x86/kernel/apic/apic.c:1287 setup_local_APIC+0x18f/0x263() Submitter : Rob Landley Date: 2011-01-18 13:11 (35 days old) Message-ID : <4D359188.3040408 at parallels.com> References : http://marc.info/?l=linux-kernel&m=129535632319892&w=2 Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=27402 Subject : Atheros adapter no longer loads firmware Submitter : Michal Vaner Date: 2011-01-23 15:29 (30 days old) First-Bad-Commit: http://git.kernel.org/linus/be93112accb42c5586a459683d71975cc70673ca Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=27152 Subject : VGA output broken at cold boot Submitter : Takashi Iwai Date: 2011-01-20 13:26 (33 days old) Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=27132 Subject : flush-btrfs gets into an infinite loop Submitter : Artem Anisimov Date: 2011-01-20 11:51 (33 days old) Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=26802 Subject : b43: Suspend failed Submitter : Patrick Matth?i Date: 2011-01-15 18:56 (38 days old) Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=26612 Subject : BUG in fs/inode.c:429 Submitter : Florian Kriener Date: 2011-01-06 16:35 (47 days old) Message-ID : <201101061735.40
[Bug 30002] [regression r300g] Menu problem in Tiny and Big
https://bugs.freedesktop.org/show_bug.cgi?id=30002 Marek Olšák changed: What|Removed |Added Status|NEW |RESOLVED Resolution||FIXED --- Comment #10 from Marek Olšák 2011-02-21 23:15:20 PST --- Fixed with a commit somewhere between e9ff76aa81d9bd973d46b7e46f1e4ece2112a5b7 and 9e872a5865c66ed0a518dd1c6c54e72f3afa71f1. Closing. There's a new regression, which is going to be fixed soon (there's already a patch for it on ML). -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 30002] [regression r300g] Menu problem in Tiny and Big
https://bugs.freedesktop.org/show_bug.cgi?id=30002 Marek Ol??k changed: What|Removed |Added Status|NEW |RESOLVED Resolution||FIXED --- Comment #10 from Marek Ol??k 2011-02-21 23:15:20 PST --- Fixed with a commit somewhere between e9ff76aa81d9bd973d46b7e46f1e4ece2112a5b7 and 9e872a5865c66ed0a518dd1c6c54e72f3afa71f1. Closing. There's a new regression, which is going to be fixed soon (there's already a patch for it on ML). -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug.
2.6.38-rc5-git6: Reported regressions from 2.6.37
This message contains a list of some regressions from 2.6.37, for which there are no fixes in the mainline known to the tracking team. If any of them have been fixed already, please let us know. If you know of any other unresolved regressions from 2.6.37, please let us know either and we'll add them to the list. Also, please let us know if any of the entries below are invalid. Each entry from the list will be sent additionally in an automatic reply to this message with CCs to the people involved in reporting and handling the issue. Listed regressions statistics: Date Total Pending Unresolved 2011-02-21 51 18 17 2011-02-12 39 20 18 2011-02-03 19 11 7 Unresolved regressions -- Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=29402 Subject : kernel panics while running ffsb scalability workloads on 2.6.38-rc1 through -rc5 Submitter : Eric Whitney Date: 2011-02-18 21:47 (4 days old) Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=29322 Subject : System lockup with 2.6.38-rc4+ Submitter : Chris Clayton Date: 2011-02-14 17:31 (8 days old) Message-ID : <201102141731.29331.chris2553 at googlemail.com> References : http://marc.info/?l=linux-kernel&m=129770471724602&w=2 Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=29252 Subject : IPv6 doesn't work in a kvm guest. Submitter : Kusanagi Kouichi Date: 2011-02-16 13:03 (6 days old) Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=29232 Subject : [VT-d] VT-d device passthrough fail to guest Submitter : xudong Date: 2011-02-16 08:56 (6 days old) Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=29202 Subject : 2.6.38-rc: fuse BUG, maybe related to detaching external usb drive without umounting Submitter : Florian Mickler Date: 2011-02-15 22:05 (7 days old) Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=29022 Subject : [REGRESSION? 2.6.38-rc4] nouveau NV50 screen freeze Submitter : Marc Date: 2011-02-13 12:29 (9 days old) Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=28882 Subject : Screen corruption and GPU hangs Submitter : Ko Mi Date: 2011-02-11 18:17 (11 days old) Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=28842 Subject : 2.6.38-rc3 regression ipv6 TFTP download with curl failing in getpeername? Submitter : Eric W. Biederman Date: 2011-02-08 9:41 (14 days old) Message-ID : References : http://marc.info/?l=linux-kernel&m=129715811421534&w=2 Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=28642 Subject : ACPI broken on DELL Latitude E6410 in 2.6.38-rc3 Submitter : Adam Kovari Date: 2011-02-08 22:22 (14 days old) Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=28562 Subject : [BUG] usb problems in .38-rc3+ Submitter : Ed Tomlinson Date: 2011-02-05 19:17 (17 days old) Message-ID : <201102051417.58953.edt at aei.ca> References : http://marc.info/?l=linux-kernel&m=129693391417607&w=2 Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=28522 Subject : Unable to mount FAT-formatted floppy on /dev/fd0, plus WARN_ON when using /dev/fd0u1440 Submitter : Alex Villacis Lasso Date: 2011-02-07 17:21 (15 days old) Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=28452 Subject : 2.6.38-rc3 regression on parisc: segfaults Submitter : Meelis Roos Date: 2011-02-01 22:00 (21 days old) Message-ID : References : http://marc.info/?l=linux-kernel&m=129659763426600&w=2 Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=28432 Subject : khugepaged: gets stuck when writing to USB flash, 2.6.38-rc2 Submitter : Jind?ich Makovi?ka Date: 2011-01-31 19:28 (22 days old) Message-ID : References : http://marc.info/?l=linux-kernel&m=129650210516627&w=2 Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=28422 Subject : kref and apparmor panic in 2.6.38-rc2. Submitter : Tao Ma Date: 2011-01-31 10:06 (22 days old) Message-ID : <4D46899B.80302 at tao.ma> References : http://marc.info/?l=linux-kernel&m=129646840303149&w=2 Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=28262 Subject : Slow resume from suspend/hibernate on Dell Inspiron M301Z Submitter : Luca Ferretti Date: 2011-02-05 12:37 (17 days old) Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=28102 Subject : New display errors in 2.6.38-rc2-00175-g6fb1b30 Submitter : Nico Schottelius Date
[Bug 29222] X cannot start up, screen flickers in console mode
https://bugzilla.kernel.org/show_bug.cgi?id=29222 Rafael J. Wysocki changed: What|Removed |Added Status|RESOLVED|CLOSED Resolution|INVALID |UNREPRODUCIBLE -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are watching the assignee of the bug. -- Index, Search & Analyze Logs and other IT data in Real-Time with Splunk Collect, index and harness all the fast moving IT data generated by your applications, servers and devices whether physical, virtual or in the cloud. Deliver compliance at lower cost and gain new business insights. Free Software Download: http://p.sf.net/sfu/splunk-dev2dev -- ___ Dri-devel mailing list Dri-devel at lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
[Bug 29632] v2.6.38-rc5 drm:radeon regression
https://bugzilla.kernel.org/show_bug.cgi?id=29632 Maciej Rutecki changed: What|Removed |Added Blocks||27352 -- 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 at lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
[Bug 29632] New: v2.6.38-rc5 drm:radeon regression
https://bugzilla.kernel.org/show_bug.cgi?id=29632 Summary: v2.6.38-rc5 drm:radeon regression 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 at kernel-bugs.osdl.org ReportedBy: maciej.rutecki at gmail.com CC: rjw at sisk.pl, maciej.rutecki at gmail.com Regression: Yes Subject: v2.6.38-rc5 drm:radeon regression Submitter : J?rg Otte Date : 2011-02-18 11:47 Message-ID : AANLkTi=6x93A11MzAjKyqO+7aP3t7QD8eMh7XVWp8GD6 at mail.gmail.com References : http://marc.info/?l=linux-kernel&m=129803001230359&w=2 This entry is being used for tracking a regression from 2.6.37. Please don't close it until the problem is fixed in the mainline. -- 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 at lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
[Bug 33674] KMS, kernel, Second Monitor becomes complete blur when loading fullscreen GL
https://bugs.freedesktop.org/show_bug.cgi?id=33674 --- Comment #3 from Øyvind Sæther 2011-02-21 19:43:16 PST --- Created an attachment (id=43633) --> (https://bugs.freedesktop.org/attachment.cgi?id=43633) How totally broken fullscreen OpenGL applications look kwin and other fullscreen opengl applications still show a total blurry mess on the second monitor as of kernel 2.6.38-rc5-git4. Completely broken and useless. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 33674] KMS, kernel, Second Monitor becomes complete blur when loading fullscreen GL
https://bugs.freedesktop.org/show_bug.cgi?id=33674 --- Comment #3 from ?yvind S?ther 2011-02-21 19:43:16 PST --- Created an attachment (id=43633) --> (https://bugs.freedesktop.org/attachment.cgi?id=43633) How totally broken fullscreen OpenGL applications look kwin and other fullscreen opengl applications still show a total blurry mess on the second monitor as of kernel 2.6.38-rc5-git4. Completely broken and useless. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug.
Re: [BUG] drm/i915 Screen corruption introduced by a00b10c360b35d6431a94cb
On Tue, February 22, 2011 04:25, Indan Zupancic wrote: > Hi, > > On Sun, February 20, 2011 14:21, Daniel Vetter wrote: >> Well, don't start jumping around, yet. These patches are just to rule out >> some theories. Now: Is it fixed with just the 2nd patch alone or do you need >> both >> patches? This is very important, so please test extensively whether there >> are really >> no corruptions with just the 2nd patch. > > I managed to create some corruption with an xterm above xpdf. It looks > different > than the original corruption, so I think it's safe to say it's a different > bug: > > http://img593.imageshack.us/i/ss1298340823.png > http://img203.imageshack.us/i/ss1298340776.png > > This was without xcompmgr running, I don't think I would have seen it > otherwise. > Actually, it turns out it's really easy to trigger as well, so I can more > easily > test patches now. Unfortunately I wasn't smart enough to store the bisecting > kernels, > gah! > > I tried with both your patches, as well as the HIC poking patch, but I still > get it. > > I'll try to pinpoint more exactly when this started to happen. Okay, I tried older kernels and I get it even with 2.6.34, so I think it's a bug in userspace, like intel-dri, or perhaps the intel X driver (though I get the same with an older version). Greetings, Indan ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
Re: [BUG] drm/i915 Screen corruption introduced by a00b10c360b35d6431a94cb
Hi, On Sun, February 20, 2011 14:21, Daniel Vetter wrote: > Well, don't start jumping around, yet. These patches are just to rule out > some theories. Now: Is it fixed with just the 2nd patch alone or do you need > both > patches? This is very important, so please test extensively whether there are > really > no corruptions with just the 2nd patch. I managed to create some corruption with an xterm above xpdf. It looks different than the original corruption, so I think it's safe to say it's a different bug: http://img593.imageshack.us/i/ss1298340823.png http://img203.imageshack.us/i/ss1298340776.png This was without xcompmgr running, I don't think I would have seen it otherwise. Actually, it turns out it's really easy to trigger as well, so I can more easily test patches now. Unfortunately I wasn't smart enough to store the bisecting kernels, gah! I tried with both your patches, as well as the HIC poking patch, but I still get it. I'll try to pinpoint more exactly when this started to happen. Greetings, Indan ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 29572] Radeon card reports wrong temperature when switched off
https://bugzilla.kernel.org/show_bug.cgi?id=29572 --- Comment #2 from Marco Trevisan (Trevi?o) 2011-02-21 16:24:51 --- Ok, both are wrong... But I'd prefer that 0? would be shown (also as a confirmation that the card is OFF) instead of an invalid value... -- 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 at lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
[Bug 28771] [RADEON:KMS::R300C:R300G] waiting for vline forced always on
https://bugs.freedesktop.org/show_bug.cgi?id=28771 --- Comment #33 from Sven Arvidsson 2011-02-21 16:22:38 PST --- (In reply to comment #32) > I'm still not sure if toggling vsync on/off inside an application is supposed > to work (it doesn't seem to with r300g in Sauerbraten or M.A.R.S. for > example). > What component should a bug be filed against in this case? > > At least M.A.R.S. seems to be using glXSwapIntervalSGI for vsync. Actually, forget about this part. It works, at least in MARS. Not sure about Sauerbraten, but it could be a bug in the game. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 28771] [RADEON:KMS::R300C:R300G] waiting for vline forced always on
https://bugs.freedesktop.org/show_bug.cgi?id=28771 --- Comment #33 from Sven Arvidsson 2011-02-21 16:22:38 PST --- (In reply to comment #32) > I'm still not sure if toggling vsync on/off inside an application is supposed > to work (it doesn't seem to with r300g in Sauerbraten or M.A.R.S. for > example). > What component should a bug be filed against in this case? > > At least M.A.R.S. seems to be using glXSwapIntervalSGI for vsync. Actually, forget about this part. It works, at least in MARS. Not sure about Sauerbraten, but it could be a bug in the game. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug.
[Bug 32319] Display fades to white screen instead of blanking out in DPMS mode on a Sony Vaio VPCEC3L1E
https://bugs.freedesktop.org/show_bug.cgi?id=32319 --- Comment #16 from Jure Repinc 2011-02-21 16:18:35 PST --- Created an attachment (id=43626) --> (https://bugs.freedesktop.org/attachment.cgi?id=43626) vbios-rom This is vbios from my laptop -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 32319] Display fades to white screen instead of blanking out in DPMS mode on a Sony Vaio VPCEC3L1E
https://bugs.freedesktop.org/show_bug.cgi?id=32319 --- Comment #16 from Jure Repinc 2011-02-21 16:18:35 PST --- Created an attachment (id=43626) --> (https://bugs.freedesktop.org/attachment.cgi?id=43626) vbios-rom This is vbios from my laptop -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug.
[Bug 32319] Display fades to white screen instead of blanking out in DPMS mode on a Sony Vaio VPCEC3L1E
https://bugs.freedesktop.org/show_bug.cgi?id=32319 --- Comment #15 from Jure Repinc 2011-02-21 16:17:09 PST --- I have the same problem on eMachines E640G laptop with the same integrated graphics (PCI ID is the same). I remember having this problem ever since the Evergreen support started to work. Currently I'm using kernel 2.6.38-rc5+ -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 32319] Display fades to white screen instead of blanking out in DPMS mode on a Sony Vaio VPCEC3L1E
https://bugs.freedesktop.org/show_bug.cgi?id=32319 --- Comment #15 from Jure Repinc 2011-02-21 16:17:09 PST --- I have the same problem on eMachines E640G laptop with the same integrated graphics (PCI ID is the same). I remember having this problem ever since the Evergreen support started to work. Currently I'm using kernel 2.6.38-rc5+ -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug.
[Bug 28771] [RADEON:KMS::R300C:R300G] waiting for vline forced always on
https://bugs.freedesktop.org/show_bug.cgi?id=28771 --- Comment #32 from Sven Arvidsson 2011-02-21 16:03:49 PST --- The need to manually configure drirc to use driver=dri2 is filed as bug 34401. I'm still not sure if toggling vsync on/off inside an application is supposed to work (it doesn't seem to with r300g in Sauerbraten or M.A.R.S. for example). What component should a bug be filed against in this case? At least M.A.R.S. seems to be using glXSwapIntervalSGI for vsync. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 28771] [RADEON:KMS::R300C:R300G] waiting for vline forced always on
https://bugs.freedesktop.org/show_bug.cgi?id=28771 --- Comment #32 from Sven Arvidsson 2011-02-21 16:03:49 PST --- The need to manually configure drirc to use driver=dri2 is filed as bug 34401. I'm still not sure if toggling vsync on/off inside an application is supposed to work (it doesn't seem to with r300g in Sauerbraten or M.A.R.S. for example). What component should a bug be filed against in this case? At least M.A.R.S. seems to be using glXSwapIntervalSGI for vsync. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug.
[Bug 29572] Radeon card reports wrong temperature when switched off
https://bugzilla.kernel.org/show_bug.cgi?id=29572 Alex Deucher changed: What|Removed |Added CC||alexdeucher at gmail.com --- Comment #1 from Alex Deucher 2011-02-21 15:38:00 --- When the GPU is powered down, the temperature is undefined as the hw sensor only works when the GPU is powered up and the mmio bar is mapped. 0?C or +2147355.6?C are both wrong. -- 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 at lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
2.6.38-rc5-git6: Reported regressions 2.6.36 -> 2.6.37
[NOTE: Can maintainers _please_ merge patches listed below, especially those that have been known for weeks?] This message contains a list of some post-2.6.36 regressions introduced before 2.6.37, for which there are no fixes in the mainline known to the tracking team. If any of them have been fixed already, please let us know. If you know of any other unresolved post-2.6.36 regressions, please let us know either and we'll add them to the list. Also, please let us know if any of the entries below are invalid. Each entry from the list will be sent additionally in an automatic reply to this message with CCs to the people involved in reporting and handling the issue. Listed regressions statistics: Date Total Pending Unresolved 2011-02-21 128 35 26 2011-02-13 126 36 30 2011-02-03 118 36 31 2010-12-30 85 32 26 2010-12-19 73 28 24 2010-12-03 55 25 19 2010-11-19 39 29 25 Unresolved regressions -- Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=29172 Subject : releasing loop on top of other loop leads to deadlock Submitter : Petr Uzel Date: 2011-02-15 10:00 (7 days old) Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=28812 Subject : DVI attached monitor is turned off while booting linux 2.6.37 and higher Submitter : Markus Heinz Date: 2011-02-10 19:33 (12 days old) Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=28772 Subject : oops in nfs_revalidate_mapping Submitter : Daniel Poelzleithner Date: 2011-02-10 13:59 (12 days old) Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=28662 Subject : i915 in kernel 2.6.38-rc4, high number of wakeups Submitter : Kan-Ru Chen Date: 2011-02-09 07:06 (13 days old) Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=28622 Subject : radeon video lockup Submitter : Daniel Poelzleithner Date: 2011-02-08 17:48 (14 days old) Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=28612 Subject : regular soft lockup Submitter : Alexandre Demers Date: 2011-02-08 16:39 (14 days old) Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=28582 Subject : whole system hang when start X Submitter : Gu Rui Date: 2011-02-08 08:33 (14 days old) First-Bad-Commit: http://git.kernel.org/linus/d5bb081b027b520f9e59b4fb8faea83a136ec15e Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=28332 Subject : [RV620] Can not re-enable LVDS after using HDMI only Submitter : Rafał Miłecki Date: 2011-02-05 22:42 (17 days old) Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=27892 Subject : SNB: GPU hang with Slip xscreensaver Submitter : Takashi Iwai Date: 2011-01-31 12:06 (22 days old) Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=27842 Subject : [regression?] hang with 2.6.37 on a BTRFS test machine Submitter : Martin Steigerwald Date: 2011-01-23 12:06 (30 days old) Message-ID : <<201101231306.23069.mar...@lichtvoll.de>> References : http://marc.info/?l=linux-kernel&m=129578445613283&w=2 Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=27642 Subject : 2.6.37 says WARNING: at arch/x86/kernel/apic/apic.c:1287 setup_local_APIC+0x18f/0x263() Submitter : Rob Landley Date: 2011-01-18 13:11 (35 days old) Message-ID : <4d359188.3040...@parallels.com> References : http://marc.info/?l=linux-kernel&m=129535632319892&w=2 Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=27402 Subject : Atheros adapter no longer loads firmware Submitter : Michal Vaner Date: 2011-01-23 15:29 (30 days old) First-Bad-Commit: http://git.kernel.org/linus/be93112accb42c5586a459683d71975cc70673ca Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=27152 Subject : VGA output broken at cold boot Submitter : Takashi Iwai Date: 2011-01-20 13:26 (33 days old) Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=27132 Subject : flush-btrfs gets into an infinite loop Submitter : Artem Anisimov Date: 2011-01-20 11:51 (33 days old) Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=26802 Subject : b43: Suspend failed Submitter : Patrick Matthäi Date: 2011-01-15 18:56 (38 days old) Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=26612 Subject : BUG in fs/inode.c:429 Submitter : Florian Kriener Date: 2011-01-06 16:35 (47 days old) Message-ID : <201101061735.40060.fl
[Bug 34280] r200 mesa-7.10 font distortion
https://bugs.freedesktop.org/show_bug.cgi?id=34280 Ian Romanick changed: What|Removed |Added Status|NEW |ASSIGNED AssignedTo|dri-devel@lists.freedesktop |i...@freedesktop.org |.org| --- Comment #6 from Ian Romanick 2011-02-21 14:34:36 PST --- (In reply to comment #3) > (In reply to comment #2) > > Can you bisect? > > Sure, I bisected to 5d1387b2da3626326410804026f8b92f1a121fdc > Ian Romanick, "ARB_texture_rg: Add R8, R16, RG88, and RG1616 internal > formats". That's pretty weird. I don't see how that change could impact r200. The only thing that seems to have a chance is if something weird happens in the GL_LUMINANCE8_ALPHA8 case. What happens if you apply this mini-patch? This isn't a fix, but it may help illuminate what's going wrong. diff --git a/src/mesa/drivers/dri/radeon/radeon_texture.c b/src/mesa/drivers/dri/radeon/radeon_texture.c index cf85a5b..75dc107 100644 --- a/src/mesa/drivers/dri/radeon/radeon_texture.c +++ b/src/mesa/drivers/dri/radeon/radeon_texture.c @@ -464,7 +464,7 @@ gl_format radeonChooseTextureFormat(struct gl_context * ctx, case GL_LUMINANCE12_ALPHA12: case GL_LUMINANCE16_ALPHA16: case GL_COMPRESSED_LUMINANCE_ALPHA: - return _dri_texformat_al88; + return radeonChooseTexFormat(rmesa, format, type, fbo); case GL_INTENSITY: case GL_INTENSITY4: -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 34280] r200 mesa-7.10 font distortion
https://bugs.freedesktop.org/show_bug.cgi?id=34280 Ian Romanick changed: What|Removed |Added Status|NEW |ASSIGNED AssignedTo|dri-devel at lists.freedesktop |idr at freedesktop.org |.org| --- Comment #6 from Ian Romanick 2011-02-21 14:34:36 PST --- (In reply to comment #3) > (In reply to comment #2) > > Can you bisect? > > Sure, I bisected to 5d1387b2da3626326410804026f8b92f1a121fdc > Ian Romanick, "ARB_texture_rg: Add R8, R16, RG88, and RG1616 internal > formats". That's pretty weird. I don't see how that change could impact r200. The only thing that seems to have a chance is if something weird happens in the GL_LUMINANCE8_ALPHA8 case. What happens if you apply this mini-patch? This isn't a fix, but it may help illuminate what's going wrong. diff --git a/src/mesa/drivers/dri/radeon/radeon_texture.c b/src/mesa/drivers/dri/radeon/radeon_texture.c index cf85a5b..75dc107 100644 --- a/src/mesa/drivers/dri/radeon/radeon_texture.c +++ b/src/mesa/drivers/dri/radeon/radeon_texture.c @@ -464,7 +464,7 @@ gl_format radeonChooseTextureFormat(struct gl_context * ctx, case GL_LUMINANCE12_ALPHA12: case GL_LUMINANCE16_ALPHA16: case GL_COMPRESSED_LUMINANCE_ALPHA: - return _dri_texformat_al88; + return radeonChooseTexFormat(rmesa, format, type, fbo); case GL_INTENSITY: case GL_INTENSITY4: -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug.
2.6.38-rc5-git6: Reported regressions from 2.6.37
This message contains a list of some regressions from 2.6.37, for which there are no fixes in the mainline known to the tracking team. If any of them have been fixed already, please let us know. If you know of any other unresolved regressions from 2.6.37, please let us know either and we'll add them to the list. Also, please let us know if any of the entries below are invalid. Each entry from the list will be sent additionally in an automatic reply to this message with CCs to the people involved in reporting and handling the issue. Listed regressions statistics: Date Total Pending Unresolved 2011-02-21 51 18 17 2011-02-12 39 20 18 2011-02-03 19 11 7 Unresolved regressions -- Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=29402 Subject : kernel panics while running ffsb scalability workloads on 2.6.38-rc1 through -rc5 Submitter : Eric Whitney Date: 2011-02-18 21:47 (4 days old) Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=29322 Subject : System lockup with 2.6.38-rc4+ Submitter : Chris Clayton Date: 2011-02-14 17:31 (8 days old) Message-ID : <201102141731.29331.chris2...@googlemail.com> References : http://marc.info/?l=linux-kernel&m=129770471724602&w=2 Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=29252 Subject : IPv6 doesn't work in a kvm guest. Submitter : Kusanagi Kouichi Date: 2011-02-16 13:03 (6 days old) Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=29232 Subject : [VT-d] VT-d device passthrough fail to guest Submitter : xudong Date: 2011-02-16 08:56 (6 days old) Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=29202 Subject : 2.6.38-rc: fuse BUG, maybe related to detaching external usb drive without umounting Submitter : Florian Mickler Date: 2011-02-15 22:05 (7 days old) Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=29022 Subject : [REGRESSION? 2.6.38-rc4] nouveau NV50 screen freeze Submitter : Marc Date: 2011-02-13 12:29 (9 days old) Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=28882 Subject : Screen corruption and GPU hangs Submitter : Ko Mi Date: 2011-02-11 18:17 (11 days old) Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=28842 Subject : 2.6.38-rc3 regression ipv6 TFTP download with curl failing in getpeername? Submitter : Eric W. Biederman Date: 2011-02-08 9:41 (14 days old) Message-ID : References : http://marc.info/?l=linux-kernel&m=129715811421534&w=2 Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=28642 Subject : ACPI broken on DELL Latitude E6410 in 2.6.38-rc3 Submitter : Adam Kovari Date: 2011-02-08 22:22 (14 days old) Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=28562 Subject : [BUG] usb problems in .38-rc3+ Submitter : Ed Tomlinson Date: 2011-02-05 19:17 (17 days old) Message-ID : <201102051417.58953@aei.ca> References : http://marc.info/?l=linux-kernel&m=129693391417607&w=2 Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=28522 Subject : Unable to mount FAT-formatted floppy on /dev/fd0, plus WARN_ON when using /dev/fd0u1440 Submitter : Alex Villacis Lasso Date: 2011-02-07 17:21 (15 days old) Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=28452 Subject : 2.6.38-rc3 regression on parisc: segfaults Submitter : Meelis Roos Date: 2011-02-01 22:00 (21 days old) Message-ID : References : http://marc.info/?l=linux-kernel&m=129659763426600&w=2 Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=28432 Subject : khugepaged: gets stuck when writing to USB flash, 2.6.38-rc2 Submitter : Jindřich Makovička Date: 2011-01-31 19:28 (22 days old) Message-ID : References : http://marc.info/?l=linux-kernel&m=129650210516627&w=2 Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=28422 Subject : kref and apparmor panic in 2.6.38-rc2. Submitter : Tao Ma Date: 2011-01-31 10:06 (22 days old) Message-ID : <4d46899b.80...@tao.ma> References : http://marc.info/?l=linux-kernel&m=129646840303149&w=2 Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=28262 Subject : Slow resume from suspend/hibernate on Dell Inspiron M301Z Submitter : Luca Ferretti Date: 2011-02-05 12:37 (17 days old) Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=28102 Subject : New display errors in 2.6.38-rc2-00175-g6fb1b30 Submitter : Nico Schottelius Date: 20
[Bug 28771] [RADEON:KMS::R300C:R300G] waiting for vline forced always on
https://bugs.freedesktop.org/show_bug.cgi?id=28771 --- Comment #31 from Alex Deucher 2011-02-21 13:51:51 PST --- vline waits for non-pageflipped swap buffers can be disabled in both radeon and intel with: Option "SwapbuffersWait" "False" in the device section of your xorg.conf -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 28771] [RADEON:KMS::R300C:R300G] waiting for vline forced always on
https://bugs.freedesktop.org/show_bug.cgi?id=28771 --- Comment #31 from Alex Deucher 2011-02-21 13:51:51 PST --- vline waits for non-pageflipped swap buffers can be disabled in both radeon and intel with: Option "SwapbuffersWait" "False" in the device section of your xorg.conf -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug.
[Bug 28771] [RADEON:KMS::R300C:R300G] waiting for vline forced always on
https://bugs.freedesktop.org/show_bug.cgi?id=28771 --- Comment #30 from Ian Romanick 2011-02-21 13:44:15 PST --- (In reply to comment #29) > Is there a similar bug filed for Intel driver? > > At least in RedHat's bugzilla there's a relevant patch: > https://bugzilla.redhat.com/show_bug.cgi?id=634200 I don't see any patches there. Is it perhaps hiding in the .srpm? -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 28771] [RADEON:KMS::R300C:R300G] waiting for vline forced always on
https://bugs.freedesktop.org/show_bug.cgi?id=28771 --- Comment #30 from Ian Romanick 2011-02-21 13:44:15 PST --- (In reply to comment #29) > Is there a similar bug filed for Intel driver? > > At least in RedHat's bugzilla there's a relevant patch: > https://bugzilla.redhat.com/show_bug.cgi?id=634200 I don't see any patches there. Is it perhaps hiding in the .srpm? -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug.
[Bug 34545] New: [gallium] segfault with vertarrays in mixed user/gpu buffers
https://bugs.freedesktop.org/show_bug.cgi?id=34545 Summary: [gallium] segfault with vertarrays in mixed user/gpu buffers Product: Mesa Version: git Platform: x86-64 (AMD64) OS/Version: Linux (All) Status: NEW Severity: normal Priority: medium Component: Drivers/Gallium/r300 AssignedTo: dri-devel@lists.freedesktop.org ReportedBy: wixorp...@gmail.com CC: mar...@gmail.com Created an attachment (id=43618) --> (https://bugs.freedesktop.org/attachment.cgi?id=43618) the test case Hello, while researching for bug 34418 I have encountered an segmentation fault trigerred when the __first__ vertex array is placed in user buffer and the second on gpu. When first array in on gpu and second in user buffer, invalid rendering occurs. This is gallium-wide (happens with both r300g and swrastg), although I cannot extract meaningful backtrace from swrastg. My shot is that is_interleaved_arrays in st_draw.c handles those cases incorrectly (at least that's the code that gave me inspiration to write the test). Interestingly, the backtraces from r300g have changed between HEAD and before-2a904fd6a0c (before "set vertex arrays state only when necessary"). This is propably correct. The current one is #0 radeon_add_reloc (rcs=0x7f5b1e508010, buf=0x0, rd=R300_DOMAIN_GTT, wd=0) at radeon_drm_cs.c:230 #1 radeon_drm_cs_add_reloc (rcs=0x7f5b1e508010, buf=0x0, rd=R300_DOMAIN_GTT, wd=0) at radeon_drm_cs.c:297 #2 0x7f5b1a79f032 in r300_emit_buffer_validate (r300=0x16993a0, do_validate_vertex_buffers=, index_buffer=) at r300_emit.c:1192 #3 0x7f5b1a7a21f1 in r300_emit_states (r300=0x16993a0, flags=, index_buffer=0x2, buffer_offset=0, index_bias=0) at r300_render.c:252 #4 0x7f5b1a7a3d95 in r300_draw_arrays (pipe=0x16993a0, info=) at r300_render.c:710 #5 r300_draw_vbo (pipe=0x16993a0, info=) at r300_render.c:775 #6 0x7f5b1a849de8 in st_draw_vbo (ctx=, arrays=, prims=, nr_prims=1, ib=0x0, index_bounds_valid=, min_index=0, max_index=31) at state_tracker/st_draw.c:717 #7 0x7f5b1a8e18fb in vbo_draw_arrays (ctx=0x16bb170, mode=6, start=0, count=, numInstances=1) at vbo/vbo_exec_array.c:615 #8 0x00400e1f in render () at immedcrash.c:15 while the old one is #0 0x7f74d66a823a in u_vbuf_mgr_set_vertex_buffers (mgrb=0x1ea5060, count=1, bufs=0x0) at util/u_vbuf_mgr.c:482 #1 0x7f74d64e50aa in r300_set_vertex_buffers (pipe=0x1eb6360, count=1, buffers=0x7fff228a33d0) at r300_state.c:1491 #2 0x7f74d6586fcf in st_draw_vbo (ctx=, arrays=, prims=, nr_prims=, ib=, index_bounds_valid=, min_index=0, max_index=31) at state_tracker/st_draw.c:707 #3 0x7f74d661ee4b in vbo_draw_arrays (ctx=0x1ee3f10, mode=6, start=0, count=, numInstances=1) at vbo/vbo_exec_array.c:593 #4 0x00400e1f in render () at immedcrash.c:15 -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 34545] New: [gallium] segfault with vertarrays in mixed user/gpu buffers
https://bugs.freedesktop.org/show_bug.cgi?id=34545 Summary: [gallium] segfault with vertarrays in mixed user/gpu buffers Product: Mesa Version: git Platform: x86-64 (AMD64) OS/Version: Linux (All) Status: NEW Severity: normal Priority: medium Component: Drivers/Gallium/r300 AssignedTo: dri-devel at lists.freedesktop.org ReportedBy: wixorpeek at gmail.com CC: maraeo at gmail.com Created an attachment (id=43618) --> (https://bugs.freedesktop.org/attachment.cgi?id=43618) the test case Hello, while researching for bug 34418 I have encountered an segmentation fault trigerred when the __first__ vertex array is placed in user buffer and the second on gpu. When first array in on gpu and second in user buffer, invalid rendering occurs. This is gallium-wide (happens with both r300g and swrastg), although I cannot extract meaningful backtrace from swrastg. My shot is that is_interleaved_arrays in st_draw.c handles those cases incorrectly (at least that's the code that gave me inspiration to write the test). Interestingly, the backtraces from r300g have changed between HEAD and before-2a904fd6a0c (before "set vertex arrays state only when necessary"). This is propably correct. The current one is #0 radeon_add_reloc (rcs=0x7f5b1e508010, buf=0x0, rd=R300_DOMAIN_GTT, wd=0) at radeon_drm_cs.c:230 #1 radeon_drm_cs_add_reloc (rcs=0x7f5b1e508010, buf=0x0, rd=R300_DOMAIN_GTT, wd=0) at radeon_drm_cs.c:297 #2 0x7f5b1a79f032 in r300_emit_buffer_validate (r300=0x16993a0, do_validate_vertex_buffers=, index_buffer=) at r300_emit.c:1192 #3 0x7f5b1a7a21f1 in r300_emit_states (r300=0x16993a0, flags=, index_buffer=0x2, buffer_offset=0, index_bias=0) at r300_render.c:252 #4 0x7f5b1a7a3d95 in r300_draw_arrays (pipe=0x16993a0, info=) at r300_render.c:710 #5 r300_draw_vbo (pipe=0x16993a0, info=) at r300_render.c:775 #6 0x7f5b1a849de8 in st_draw_vbo (ctx=, arrays=, prims=, nr_prims=1, ib=0x0, index_bounds_valid=, min_index=0, max_index=31) at state_tracker/st_draw.c:717 #7 0x7f5b1a8e18fb in vbo_draw_arrays (ctx=0x16bb170, mode=6, start=0, count=, numInstances=1) at vbo/vbo_exec_array.c:615 #8 0x00400e1f in render () at immedcrash.c:15 while the old one is #0 0x7f74d66a823a in u_vbuf_mgr_set_vertex_buffers (mgrb=0x1ea5060, count=1, bufs=0x0) at util/u_vbuf_mgr.c:482 #1 0x7f74d64e50aa in r300_set_vertex_buffers (pipe=0x1eb6360, count=1, buffers=0x7fff228a33d0) at r300_state.c:1491 #2 0x7f74d6586fcf in st_draw_vbo (ctx=, arrays=, prims=, nr_prims=, ib=, index_bounds_valid=, min_index=0, max_index=31) at state_tracker/st_draw.c:707 #3 0x7f74d661ee4b in vbo_draw_arrays (ctx=0x1ee3f10, mode=6, start=0, count=, numInstances=1) at vbo/vbo_exec_array.c:593 #4 0x00400e1f in render () at immedcrash.c:15 -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug.
[PATCH] i.MX23/28 framebuffer driver
On Fri, Feb 18, 2011 at 2:14 AM, James Simmons wrote: > >> I'm still in the learning-as-I-go phase here, so definitely not ready >> to propose a solution, but it does seem to me like there is room for >> some sort of kms-helper library here to handle more of the boilerplate >> xf86-video-* stuff.. ?I guess I'll have a better picture once I have a >> chance to add support for the various multi-monitor configurations. >> But certainly would be interested if anyone already has some ideas. > > I have been thinking about this as well. One of the short coming for DRM > on embedded platforms is the lack of a small well defined library that one > could use. Right now libkms only handles buffer allocation. The mode > setting is currently tied to the libdrm library. It would be nice to > seperate the two out more. Move the mode setting code to libkms and then > have libdrm be a wrapper around this. This way libdrm can both support > the legacy drm drivers and the new kms drivers at the same time. It also > makes a clear seperation. Jakob if you are willing to take this work I > will gladly seen you patches. the problem with that is libkms relies on libdrm, so you'd have a circular dependency. With the addition of the dumb ioctl to the kernel we can certainly avoid some of that dependency, but you guys are missing one important point about libkms, its meant to be a fallback. Why? well because most GPUs in reality have non-generic memory layouts, they prefer having tiled buffers for different things and different types of tiling. There is simply no nice way to abstract that out, since it depends on the userspace libraries that use this. Starting off with an untiled allocation for the frontbuffer can pretty much leave you messed up when you plug anything like acceleration in afterwards. I have been looking at this from the USB driver pov as well, and we can probably resurrect the old xf86-video-modesetting driver along with some code in the X server maybe, mesa also has a libkms fallback X driver that works quite well if just a bit messy to build (since its in mesa). Dave.
[Bug 29222] X cannot start up, screen flickers in console mode
https://bugzilla.kernel.org/show_bug.cgi?id=29222 Rafael J. Wysocki changed: What|Removed |Added Status|RESOLVED|CLOSED Resolution|INVALID |UNREPRODUCIBLE -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are watching the assignee of the bug. -- Index, Search & Analyze Logs and other IT data in Real-Time with Splunk Collect, index and harness all the fast moving IT data generated by your applications, servers and devices whether physical, virtual or in the cloud. Deliver compliance at lower cost and gain new business insights. Free Software Download: http://p.sf.net/sfu/splunk-dev2dev -- ___ Dri-devel mailing list dri-de...@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 29632] v2.6.38-rc5 drm:radeon regression
https://bugzilla.kernel.org/show_bug.cgi?id=29632 Maciej Rutecki changed: What|Removed |Added Blocks||27352 -- 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-de...@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 29632] New: v2.6.38-rc5 drm:radeon regression
https://bugzilla.kernel.org/show_bug.cgi?id=29632 Summary: v2.6.38-rc5 drm:radeon regression 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-...@kernel-bugs.osdl.org ReportedBy: maciej.rute...@gmail.com CC: r...@sisk.pl, maciej.rute...@gmail.com Regression: Yes Subject: v2.6.38-rc5 drm:radeon regression Submitter : Jörg Otte Date : 2011-02-18 11:47 Message-ID : AANLkTi=6x93a11mzajkyqo+7ap3t7qd8emh7xvwp8...@mail.gmail.com References : http://marc.info/?l=linux-kernel&m=129803001230359&w=2 This entry is being used for tracking a regression from 2.6.37. Please don't close it until the problem is fixed in the mainline. -- 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-de...@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
[PATCH] Implement drmGetCap() to query device/driver capabilities
From: Ben Skeggs
Signed-off-by: Ben Skeggs
---
include/drm/drm.h |7 +++
xf86drm.c |9 +
xf86drm.h |1 +
3 files changed, 17 insertions(+), 0 deletions(-)
diff --git a/include/drm/drm.h b/include/drm/drm.h
index 2ba7136..fd06c2a 100644
--- a/include/drm/drm.h
+++ b/include/drm/drm.h
@@ -612,6 +612,12 @@ struct drm_gem_open {
__u64 size;
};
+/** DRM_IOCTL_GET_CAP ioctl argument type */
+struct drm_get_cap {
+ __u64 capability;
+ __u64 value;
+};
+
#include "drm_mode.h"
#define DRM_IOCTL_BASE 'd'
@@ -632,6 +638,7 @@ struct drm_gem_open {
#define DRM_IOCTL_GEM_CLOSEDRM_IOW (0x09, struct drm_gem_close)
#define DRM_IOCTL_GEM_FLINKDRM_IOWR(0x0a, struct drm_gem_flink)
#define DRM_IOCTL_GEM_OPEN DRM_IOWR(0x0b, struct drm_gem_open)
+#define DRM_IOCTL_GET_CAP DRM_IOWR(0x0c, struct drm_get_cap)
#define DRM_IOCTL_SET_UNIQUE DRM_IOW( 0x10, struct drm_unique)
#define DRM_IOCTL_AUTH_MAGIC DRM_IOW( 0x11, struct drm_auth)
diff --git a/xf86drm.c b/xf86drm.c
index 799fcdd..5b060c9 100644
--- a/xf86drm.c
+++ b/xf86drm.c
@@ -810,6 +810,15 @@ drmVersionPtr drmGetLibVersion(int fd)
return (drmVersionPtr)version;
}
+uint64_t drmGetCap(int fd, uint64_t capability)
+{
+ struct drm_get_cap cap = { capability, 0 };
+
+ if (drmIoctl(fd, DRM_IOCTL_GET_CAP, &cap))
+ return 0;
+
+ return cap.value;
+}
/**
* Free the bus ID information.
diff --git a/xf86drm.h b/xf86drm.h
index 9b89f56..1c87b7f 100644
--- a/xf86drm.h
+++ b/xf86drm.h
@@ -542,6 +542,7 @@ extern int drmOpenControl(int minor);
extern int drmClose(int fd);
extern drmVersionPtr drmGetVersion(int fd);
extern drmVersionPtr drmGetLibVersion(int fd);
+extern uint64_t drmGetCap(int fd, uint64_t capability);
extern void drmFreeVersion(drmVersionPtr);
extern int drmGetMagic(int fd, drm_magic_t * magic);
extern char *drmGetBusid(int fd);
--
1.7.4
[PATCH] drm/core: add ioctl to query device/driver capabilities
From: Ben Skeggs
We're coming to see a need to have a set of generic capability checks in
the core DRM, in addition to the driver-specific ioctls that already
exist.
This patch defines an ioctl to do as such, but does not yet define any
capabilities.
Signed-off-by: Ben Skeggs
---
drivers/gpu/drm/drm_drv.c |1 +
drivers/gpu/drm/drm_ioctl.c | 13 +
include/drm/drm.h |7 +++
include/drm/drmP.h |9 +
4 files changed, 30 insertions(+), 0 deletions(-)
diff --git a/drivers/gpu/drm/drm_drv.c b/drivers/gpu/drm/drm_drv.c
index 271835a..ad86135 100644
--- a/drivers/gpu/drm/drm_drv.c
+++ b/drivers/gpu/drm/drm_drv.c
@@ -67,6 +67,7 @@ static struct drm_ioctl_desc drm_ioctls[] = {
DRM_IOCTL_DEF(DRM_IOCTL_GET_MAP, drm_getmap, 0),
DRM_IOCTL_DEF(DRM_IOCTL_GET_CLIENT, drm_getclient, 0),
DRM_IOCTL_DEF(DRM_IOCTL_GET_STATS, drm_getstats, 0),
+ DRM_IOCTL_DEF(DRM_IOCTL_GET_CAP, drm_getcap, 0),
DRM_IOCTL_DEF(DRM_IOCTL_SET_VERSION, drm_setversion, DRM_MASTER),
DRM_IOCTL_DEF(DRM_IOCTL_SET_UNIQUE, drm_setunique,
DRM_AUTH|DRM_MASTER|DRM_ROOT_ONLY),
diff --git a/drivers/gpu/drm/drm_ioctl.c b/drivers/gpu/drm/drm_ioctl.c
index 47db4df..15a244b 100644
--- a/drivers/gpu/drm/drm_ioctl.c
+++ b/drivers/gpu/drm/drm_ioctl.c
@@ -365,6 +365,19 @@ int drm_getstats(struct drm_device *dev, void *data,
}
/**
+ * Get device/driver capabilities
+ */
+int drm_getcap(struct drm_device *dev, void *data, struct drm_file *file_priv)
+{
+ struct drm_get_cap *req = data;
+
+ req->value = 0;
+ if (dev->driver->get_cap)
+ req->value = (*dev->driver->get_cap)(dev, req->capability);
+ return 0;
+}
+
+/**
* Setversion ioctl.
*
* \param inode device inode.
diff --git a/include/drm/drm.h b/include/drm/drm.h
index e5f7061..7254f1a 100644
--- a/include/drm/drm.h
+++ b/include/drm/drm.h
@@ -608,6 +608,12 @@ struct drm_gem_open {
__u64 size;
};
+/** DRM_IOCTL_GET_CAP ioctl argument type */
+struct drm_get_cap {
+ __u64 capability;
+ __u64 value;
+};
+
#include "drm_mode.h"
#define DRM_IOCTL_BASE 'd'
@@ -628,6 +634,7 @@ struct drm_gem_open {
#define DRM_IOCTL_GEM_CLOSEDRM_IOW (0x09, struct drm_gem_close)
#define DRM_IOCTL_GEM_FLINKDRM_IOWR(0x0a, struct drm_gem_flink)
#define DRM_IOCTL_GEM_OPEN DRM_IOWR(0x0b, struct drm_gem_open)
+#define DRM_IOCTL_GET_CAP DRM_IOWR(0x0c, struct drm_get_cap)
#define DRM_IOCTL_SET_UNIQUE DRM_IOW( 0x10, struct drm_unique)
#define DRM_IOCTL_AUTH_MAGIC DRM_IOW( 0x11, struct drm_auth)
diff --git a/include/drm/drmP.h b/include/drm/drmP.h
index fe29aad..a3d5ce8 100644
--- a/include/drm/drmP.h
+++ b/include/drm/drmP.h
@@ -869,6 +869,13 @@ struct drm_driver {
void (*debugfs_cleanup)(struct drm_minor *minor);
/**
+* Driver-specific routine to query capabilities of device/driver.
+*
+* If not present, core drm will assume a return value of 0.
+*/
+ u64 (*get_cap)(struct drm_device *dev, u64 cap);
+
+ /**
* Driver-specific constructor for drm_gem_objects, to set up
* obj->driver_private.
*
@@ -1264,6 +1271,8 @@ extern int drm_getclient(struct drm_device *dev, void
*data,
struct drm_file *file_priv);
extern int drm_getstats(struct drm_device *dev, void *data,
struct drm_file *file_priv);
+extern int drm_getcap(struct drm_device *dev, void *data,
+ struct drm_file *file_priv);
extern int drm_setversion(struct drm_device *dev, void *data,
struct drm_file *file_priv);
extern int drm_noop(struct drm_device *dev, void *data,
--
1.7.4
[Bug 34313] RV770 lock-up with OpenGL
https://bugs.freedesktop.org/show_bug.cgi?id=34313 --- Comment #11 from Bob Ham 2011-02-21 11:02:23 PST --- The above lockups are from Stellarium: http://www.stellarium.org/ However, Nexuiz and Doom 3 will also cause GPU lockups (and eventually system lockups.) -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 34313] RV770 lock-up with OpenGL
https://bugs.freedesktop.org/show_bug.cgi?id=34313 --- Comment #11 from Bob Ham 2011-02-21 11:02:23 PST --- The above lockups are from Stellarium: http://www.stellarium.org/ However, Nexuiz and Doom 3 will also cause GPU lockups (and eventually system lockups.) -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug.
[Bug 34313] RV770 lock-up with OpenGL
https://bugs.freedesktop.org/show_bug.cgi?id=34313 --- Comment #10 from Alex Deucher 2011-02-21 10:52:52 PST --- What specific programs cause the lockups? -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 34313] RV770 lock-up with OpenGL
https://bugs.freedesktop.org/show_bug.cgi?id=34313 --- Comment #10 from Alex Deucher 2011-02-21 10:52:52 PST --- What specific programs cause the lockups? -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug.
[Bug 28902] activated KMS leads to complete freeze when viewing BIG images in Iceweasel
https://bugzilla.kernel.org/show_bug.cgi?id=28902 --- Comment #7 from spamfang1199 at yahoo.de 2011-02-21 10:42:45 --- Created an attachment (id=48552) --> (https://bugzilla.kernel.org/attachment.cgi?id=48552) these are the crashlogs from 2.6.37 -- 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 at lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
[Bug 28902] activated KMS leads to complete freeze when viewing BIG images in Iceweasel
https://bugzilla.kernel.org/show_bug.cgi?id=28902 --- Comment #6 from spamfang1199 at yahoo.de 2011-02-21 10:41:25 --- Here i add some logs from 2 different crashes with 2.6.37. I archived them right after the crash by rebooting into runlevel 1, so that X was not started. -- 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 at lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
[Bug 29572] New: Radeon card reports wrong temperature when switched off
https://bugzilla.kernel.org/show_bug.cgi?id=29572 Summary: Radeon card reports wrong temperature when switched off 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 at kernel-bugs.osdl.org ReportedBy: mail at 3v1n0.net CC: mail at 3v1n0.net Regression: Yes In previous versions of the kernel (I've tested the 2.6.37 version) when the I switched off the radeon card using vga_switcheroo libsensors was correctly reporting that the radeon temperature was 0? (or invalid). This doesn't happen any more using the latest kernel, in fact (after the commit 20d391d72519527d2266a0166490118b40ff998d, I figure) when my radeon card has been switched off (or after a suspend/resume cycle) sensors indicates: radeon-pci-0100 Adapter: PCI adapter temp1: +2147355.6?C This is obiouvsly impossible. -- 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 at lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
[PATCH] drm/core: add ioctl to query device/driver capabilities
On Sun, Feb 20, 2011 at 8:17 PM, Ben Skeggs wrote:
> From: Ben Skeggs
>
> We're coming to see a need to have a set of generic capability checks in
> the core DRM, in addition to the driver-specific ioctls that already
> exist.
Looks good to me, just one comment: I don't think we need the driver
callout. We only need the drm get cap for generic drm features and
drm itself should know whether or not it has the support, typically by
looking at the driver_features flags.
Kristian
> This patch defines an ioctl to do as such, but does not yet define any
> capabilities.
>
> Signed-off-by: Ben Skeggs
> ---
> ?drivers/gpu/drm/drm_drv.c ? | ? ?1 +
> ?drivers/gpu/drm/drm_ioctl.c | ? 13 +
> ?include/drm/drm.h ? ? ? ? ? | ? ?7 +++
> ?include/drm/drmP.h ? ? ? ? ?| ? ?9 +
> ?4 files changed, 30 insertions(+), 0 deletions(-)
>
> diff --git a/drivers/gpu/drm/drm_drv.c b/drivers/gpu/drm/drm_drv.c
> index 271835a..ad86135 100644
> --- a/drivers/gpu/drm/drm_drv.c
> +++ b/drivers/gpu/drm/drm_drv.c
> @@ -67,6 +67,7 @@ static struct drm_ioctl_desc drm_ioctls[] = {
> ? ? ? ?DRM_IOCTL_DEF(DRM_IOCTL_GET_MAP, drm_getmap, 0),
> ? ? ? ?DRM_IOCTL_DEF(DRM_IOCTL_GET_CLIENT, drm_getclient, 0),
> ? ? ? ?DRM_IOCTL_DEF(DRM_IOCTL_GET_STATS, drm_getstats, 0),
> + ? ? ? DRM_IOCTL_DEF(DRM_IOCTL_GET_CAP, drm_getcap, 0),
> ? ? ? ?DRM_IOCTL_DEF(DRM_IOCTL_SET_VERSION, drm_setversion, DRM_MASTER),
>
> ? ? ? ?DRM_IOCTL_DEF(DRM_IOCTL_SET_UNIQUE, drm_setunique,
> DRM_AUTH|DRM_MASTER|DRM_ROOT_ONLY),
> diff --git a/drivers/gpu/drm/drm_ioctl.c b/drivers/gpu/drm/drm_ioctl.c
> index 47db4df..15a244b 100644
> --- a/drivers/gpu/drm/drm_ioctl.c
> +++ b/drivers/gpu/drm/drm_ioctl.c
> @@ -365,6 +365,19 @@ int drm_getstats(struct drm_device *dev, void *data,
> ?}
>
> ?/**
> + * Get device/driver capabilities
> + */
> +int drm_getcap(struct drm_device *dev, void *data, struct drm_file
> *file_priv)
> +{
> + ? ? ? struct drm_get_cap *req = data;
> +
> + ? ? ? req->value = 0;
> + ? ? ? if (dev->driver->get_cap)
> + ? ? ? ? ? ? ? req->value = (*dev->driver->get_cap)(dev, req->capability);
> + ? ? ? return 0;
> +}
> +
> +/**
> ?* Setversion ioctl.
> ?*
> ?* \param inode device inode.
> diff --git a/include/drm/drm.h b/include/drm/drm.h
> index e5f7061..7254f1a 100644
> --- a/include/drm/drm.h
> +++ b/include/drm/drm.h
> @@ -608,6 +608,12 @@ struct drm_gem_open {
> ? ? ? ?__u64 size;
> ?};
>
> +/** DRM_IOCTL_GET_CAP ioctl argument type */
> +struct drm_get_cap {
> + ? ? ? __u64 capability;
> + ? ? ? __u64 value;
> +};
> +
> ?#include "drm_mode.h"
>
> ?#define DRM_IOCTL_BASE ? ? ? ? ? ? ? ? 'd'
> @@ -628,6 +634,7 @@ struct drm_gem_open {
> ?#define DRM_IOCTL_GEM_CLOSE ? ? ? ? ? ?DRM_IOW (0x09, struct drm_gem_close)
> ?#define DRM_IOCTL_GEM_FLINK ? ? ? ? ? ?DRM_IOWR(0x0a, struct drm_gem_flink)
> ?#define DRM_IOCTL_GEM_OPEN ? ? ? ? ? ? DRM_IOWR(0x0b, struct drm_gem_open)
> +#define DRM_IOCTL_GET_CAP ? ? ? ? ? ? ?DRM_IOWR(0x0c, struct drm_get_cap)
>
> ?#define DRM_IOCTL_SET_UNIQUE ? ? ? ? ? DRM_IOW( 0x10, struct drm_unique)
> ?#define DRM_IOCTL_AUTH_MAGIC ? ? ? ? ? DRM_IOW( 0x11, struct drm_auth)
> diff --git a/include/drm/drmP.h b/include/drm/drmP.h
> index fe29aad..a3d5ce8 100644
> --- a/include/drm/drmP.h
> +++ b/include/drm/drmP.h
> @@ -869,6 +869,13 @@ struct drm_driver {
> ? ? ? ?void (*debugfs_cleanup)(struct drm_minor *minor);
>
> ? ? ? ?/**
> + ? ? ? ?* Driver-specific routine to query capabilities of device/driver.
> + ? ? ? ?*
> + ? ? ? ?* If not present, core drm will assume a return value of 0.
> + ? ? ? ?*/
> + ? ? ? u64 (*get_cap)(struct drm_device *dev, u64 cap);
> +
> + ? ? ? /**
> ? ? ? ? * Driver-specific constructor for drm_gem_objects, to set up
> ? ? ? ? * obj->driver_private.
> ? ? ? ? *
> @@ -1264,6 +1271,8 @@ extern int drm_getclient(struct drm_device *dev, void
> *data,
> ? ? ? ? ? ? ? ? ? ? ? ? struct drm_file *file_priv);
> ?extern int drm_getstats(struct drm_device *dev, void *data,
> ? ? ? ? ? ? ? ? ? ? ? ?struct drm_file *file_priv);
> +extern int drm_getcap(struct drm_device *dev, void *data,
> + ? ? ? ? ? ? ? ? ? ? struct drm_file *file_priv);
> ?extern int drm_setversion(struct drm_device *dev, void *data,
> ? ? ? ? ? ? ? ? ? ? ? ? ?struct drm_file *file_priv);
> ?extern int drm_noop(struct drm_device *dev, void *data,
> --
> 1.7.4
>
>
[Bug 28932] new avivo PLL calculation in Radeon driver fails with certain modelines
https://bugzilla.kernel.org/show_bug.cgi?id=28932 Florian Mickler changed: What|Removed |Added Status|RESOLVED|CLOSED --- Comment #9 from Florian Mickler 2011-02-21 08:42:00 --- Thx, closing. -- 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 at lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
[Bug 29572] Radeon card reports wrong temperature when switched off
https://bugzilla.kernel.org/show_bug.cgi?id=29572 --- Comment #2 from Marco Trevisan (Treviño) 2011-02-21 16:24:51 --- Ok, both are wrong... But I'd prefer that 0° would be shown (also as a confirmation that the card is OFF) instead of an invalid value... -- 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-de...@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
[PATCH] gpu: drm: nouveau: Remove unused variable to prevent compile warning.
On Sun, 2011-02-20 at 18:58 +0100, Ralf Thielow wrote:
> Remove unused variable "dev_priv" in function "nv50_vm_map_pgt" to
> prevent compile warning.
>
Thanks for this, however, it has already been fixed in the nouveau tree.
Ben.
> Signed-off-by: Ralf Thielow
> ---
> drivers/gpu/drm/nouveau/nv50_vm.c |1 -
> 1 files changed, 0 insertions(+), 1 deletions(-)
>
> diff --git a/drivers/gpu/drm/nouveau/nv50_vm.c
> b/drivers/gpu/drm/nouveau/nv50_vm.c
> index 459ff08..03c1a63 100644
> --- a/drivers/gpu/drm/nouveau/nv50_vm.c
> +++ b/drivers/gpu/drm/nouveau/nv50_vm.c
> @@ -31,7 +31,6 @@ void
> nv50_vm_map_pgt(struct nouveau_gpuobj *pgd, u32 pde,
> struct nouveau_gpuobj *pgt[2])
> {
> - struct drm_nouveau_private *dev_priv = pgd->dev->dev_private;
> u64 phys = 0xdeadcafeULL;
> u32 coverage = 0;
>
[PATCH 01/11] drm/nouveau: don't munge in drm_mm internals
On Fri, 2011-02-18 at 17:59 +0100, Daniel Vetter wrote:
> Nouveau was checking drm_mm internals on teardown to see whether the
> memory manager was initialized. Hide these internals in a small
> inline helper function.
>
> Cc: Ben Skeggs
> Signed-off-by: Daniel Vetter
Acked-by: Ben Skeggs
> ---
> drivers/gpu/drm/nouveau/nouveau_object.c |2 +-
> drivers/gpu/drm/nouveau/nv50_instmem.c |4 ++--
> drivers/gpu/drm/nouveau/nvc0_instmem.c |2 +-
> include/drm/drm_mm.h |5 +
> 4 files changed, 9 insertions(+), 4 deletions(-)
>
> diff --git a/drivers/gpu/drm/nouveau/nouveau_object.c
> b/drivers/gpu/drm/nouveau/nouveau_object.c
> index 30b6544..03adfe4 100644
> --- a/drivers/gpu/drm/nouveau/nouveau_object.c
> +++ b/drivers/gpu/drm/nouveau/nouveau_object.c
> @@ -909,7 +909,7 @@ nouveau_gpuobj_channel_takedown(struct nouveau_channel
> *chan)
> nouveau_vm_ref(NULL, &chan->vm, chan->vm_pd);
> nouveau_gpuobj_ref(NULL, &chan->vm_pd);
>
> - if (chan->ramin_heap.free_stack.next)
> + if (drm_mm_initialized(&chan->ramin_heap))
> drm_mm_takedown(&chan->ramin_heap);
> nouveau_gpuobj_ref(NULL, &chan->ramin);
> }
> diff --git a/drivers/gpu/drm/nouveau/nv50_instmem.c
> b/drivers/gpu/drm/nouveau/nv50_instmem.c
> index ea00418..300285a 100644
> --- a/drivers/gpu/drm/nouveau/nv50_instmem.c
> +++ b/drivers/gpu/drm/nouveau/nv50_instmem.c
> @@ -56,7 +56,7 @@ nv50_channel_del(struct nouveau_channel **pchan)
> nouveau_gpuobj_ref(NULL, &chan->ramfc);
> nouveau_vm_ref(NULL, &chan->vm, chan->vm_pd);
> nouveau_gpuobj_ref(NULL, &chan->vm_pd);
> - if (chan->ramin_heap.free_stack.next)
> + if (drm_mm_initialized(&chan->ramin_heap))
> drm_mm_takedown(&chan->ramin_heap);
> nouveau_gpuobj_ref(NULL, &chan->ramin);
> kfree(chan);
> @@ -259,7 +259,7 @@ nv50_instmem_takedown(struct drm_device *dev)
> nouveau_gpuobj_ref(NULL, &dev_priv->bar3_vm->pgt[0].obj[0]);
> nouveau_vm_ref(NULL, &dev_priv->bar3_vm, NULL);
>
> - if (dev_priv->ramin_heap.free_stack.next)
> + if (drm_mm_initialized(&dev_priv->ramin_heap))
> drm_mm_takedown(&dev_priv->ramin_heap);
>
> dev_priv->engine.instmem.priv = NULL;
> diff --git a/drivers/gpu/drm/nouveau/nvc0_instmem.c
> b/drivers/gpu/drm/nouveau/nvc0_instmem.c
> index c090917..82357d2 100644
> --- a/drivers/gpu/drm/nouveau/nvc0_instmem.c
> +++ b/drivers/gpu/drm/nouveau/nvc0_instmem.c
> @@ -67,7 +67,7 @@ nvc0_channel_del(struct nouveau_channel **pchan)
> return;
>
> nouveau_vm_ref(NULL, &chan->vm, NULL);
> - if (chan->ramin_heap.free_stack.next)
> + if (drm_mm_initialized(&chan->ramin_heap))
> drm_mm_takedown(&chan->ramin_heap);
> nouveau_gpuobj_ref(NULL, &chan->ramin);
> kfree(chan);
> diff --git a/include/drm/drm_mm.h b/include/drm/drm_mm.h
> index e391777..0d79146 100644
> --- a/include/drm/drm_mm.h
> +++ b/include/drm/drm_mm.h
> @@ -72,6 +72,11 @@ struct drm_mm {
> unsigned long scan_end;
> };
>
> +static inline bool drm_mm_initialized(struct drm_mm *mm)
> +{
> + return mm->free_stack.next;
> +}
> +
> /*
> * Basic range manager support (drm_mm.c)
> */
[Bug 34427] Graphical corruption when opening windows
https://bugs.freedesktop.org/show_bug.cgi?id=34427 --- Comment #4 from Alex Deucher 2011-02-21 07:43:29 PST --- Any chance you could track down which component is problematic (drm, ddx, or mesa) and bisect? -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 34427] Graphical corruption when opening windows
https://bugs.freedesktop.org/show_bug.cgi?id=34427 --- Comment #4 from Alex Deucher 2011-02-21 07:43:29 PST --- Any chance you could track down which component is problematic (drm, ddx, or mesa) and bisect? -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug.
[Bug 29572] Radeon card reports wrong temperature when switched off
https://bugzilla.kernel.org/show_bug.cgi?id=29572 Alex Deucher changed: What|Removed |Added CC||alexdeuc...@gmail.com --- Comment #1 from Alex Deucher 2011-02-21 15:38:00 --- When the GPU is powered down, the temperature is undefined as the hw sensor only works when the GPU is powered up and the mmio bar is mapped. 0°C or +2147355.6°C are both wrong. -- 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-de...@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 34534] resolution 3840x1024 stopped to work on HD5850 after switch to 2.6.37 kernel
https://bugs.freedesktop.org/show_bug.cgi?id=34534 --- Comment #4 from Peter Hercek 2011-02-21 07:27:55 PST --- Created an attachment (id=43606) --> (https://bugs.freedesktop.org/attachment.cgi?id=43606) xorg.log from 2.6.36.3 -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 34534] resolution 3840x1024 stopped to work on HD5850 after switch to 2.6.37 kernel
https://bugs.freedesktop.org/show_bug.cgi?id=34534 --- Comment #4 from Peter Hercek 2011-02-21 07:27:55 PST --- Created an attachment (id=43606) --> (https://bugs.freedesktop.org/attachment.cgi?id=43606) xorg.log from 2.6.36.3 -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug.
[Bug 34534] resolution 3840x1024 stopped to work on HD5850 after switch to 2.6.37 kernel
https://bugs.freedesktop.org/show_bug.cgi?id=34534 --- Comment #3 from Peter Hercek 2011-02-21 07:27:05 PST --- Created an attachment (id=43605) --> (https://bugs.freedesktop.org/attachment.cgi?id=43605) dmesg from 2.6.36.3 -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 34534] resolution 3840x1024 stopped to work on HD5850 after switch to 2.6.37 kernel
https://bugs.freedesktop.org/show_bug.cgi?id=34534 --- Comment #2 from Peter Hercek 2011-02-21 07:26:23 PST --- Created an attachment (id=43604) --> (https://bugs.freedesktop.org/attachment.cgi?id=43604) xorg.log from 2.6.37 -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 34534] resolution 3840x1024 stopped to work on HD5850 after switch to 2.6.37 kernel
https://bugs.freedesktop.org/show_bug.cgi?id=34534 --- Comment #3 from Peter Hercek 2011-02-21 07:27:05 PST --- Created an attachment (id=43605) --> (https://bugs.freedesktop.org/attachment.cgi?id=43605) dmesg from 2.6.36.3 -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug.
[Bug 34534] resolution 3840x1024 stopped to work on HD5850 after switch to 2.6.37 kernel
https://bugs.freedesktop.org/show_bug.cgi?id=34534 --- Comment #2 from Peter Hercek 2011-02-21 07:26:23 PST --- Created an attachment (id=43604) --> (https://bugs.freedesktop.org/attachment.cgi?id=43604) xorg.log from 2.6.37 -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug.
[Bug 34534] resolution 3840x1024 stopped to work on HD5850 after switch to 2.6.37 kernel
https://bugs.freedesktop.org/show_bug.cgi?id=34534 --- Comment #1 from Peter Hercek 2011-02-21 07:25:49 PST --- Created an attachment (id=43603) --> (https://bugs.freedesktop.org/attachment.cgi?id=43603) dmesg from 2.6.37 -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 34534] resolution 3840x1024 stopped to work on HD5850 after switch to 2.6.37 kernel
https://bugs.freedesktop.org/show_bug.cgi?id=34534 --- Comment #1 from Peter Hercek 2011-02-21 07:25:49 PST --- Created an attachment (id=43603) --> (https://bugs.freedesktop.org/attachment.cgi?id=43603) dmesg from 2.6.37 -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug.
[Bug 34534] New: resolution 3840x1024 stopped to work on HD5850 after switch to 2.6.37 kernel
https://bugs.freedesktop.org/show_bug.cgi?id=34534 Summary: resolution 3840x1024 stopped to work on HD5850 after switch to 2.6.37 kernel Product: DRI Version: unspecified Platform: x86-64 (AMD64) OS/Version: Linux (All) Status: NEW Severity: major Priority: medium Component: DRM/Radeon AssignedTo: dri-devel@lists.freedesktop.org ReportedBy: pher...@gmail.com Created an attachment (id=43602) --> (https://bugs.freedesktop.org/attachment.cgi?id=43602) example how root-tail output gets corrupted Resolution 3840x1024 stopped to work when I switched from 2.6.36.3 to 2.6.37. The image looks like it is stretched by about 50% and it is corrupted. I did bisect it and the the commit when it appeared the first time is: f9d9c36204243d81e9d4dd28e58ee335257847d2 title: drm/radeon/kms: implement display watermark support for evergreen -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 34534] New: resolution 3840x1024 stopped to work on HD5850 after switch to 2.6.37 kernel
https://bugs.freedesktop.org/show_bug.cgi?id=34534 Summary: resolution 3840x1024 stopped to work on HD5850 after switch to 2.6.37 kernel Product: DRI Version: unspecified Platform: x86-64 (AMD64) OS/Version: Linux (All) Status: NEW Severity: major Priority: medium Component: DRM/Radeon AssignedTo: dri-devel at lists.freedesktop.org ReportedBy: phercek at gmail.com Created an attachment (id=43602) --> (https://bugs.freedesktop.org/attachment.cgi?id=43602) example how root-tail output gets corrupted Resolution 3840x1024 stopped to work when I switched from 2.6.36.3 to 2.6.37. The image looks like it is stretched by about 50% and it is corrupted. I did bisect it and the the commit when it appeared the first time is: f9d9c36204243d81e9d4dd28e58ee335257847d2 title: drm/radeon/kms: implement display watermark support for evergreen -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug.
How to disable GPU acceleration?
Hi, I have the 3D graphics driver installed on my linux system. a. How do i disable hardware acceleration and make a 3D game use the libGLCore (s/w renderer) of Xserver (without uninstalling the 3D driver)? b. Are there 3D apps/games which work (however slow) if h/w acceleration is disabled? Thanks K
Re: [PATCH] drm/core: add ioctl to query device/driver capabilities
On Sun, Feb 20, 2011 at 8:17 PM, Ben Skeggs wrote:
> From: Ben Skeggs
>
> We're coming to see a need to have a set of generic capability checks in
> the core DRM, in addition to the driver-specific ioctls that already
> exist.
Looks good to me, just one comment: I don't think we need the driver
callout. We only need the drm get cap for generic drm features and
drm itself should know whether or not it has the support, typically by
looking at the driver_features flags.
Kristian
> This patch defines an ioctl to do as such, but does not yet define any
> capabilities.
>
> Signed-off-by: Ben Skeggs
> ---
> drivers/gpu/drm/drm_drv.c | 1 +
> drivers/gpu/drm/drm_ioctl.c | 13 +
> include/drm/drm.h | 7 +++
> include/drm/drmP.h | 9 +
> 4 files changed, 30 insertions(+), 0 deletions(-)
>
> diff --git a/drivers/gpu/drm/drm_drv.c b/drivers/gpu/drm/drm_drv.c
> index 271835a..ad86135 100644
> --- a/drivers/gpu/drm/drm_drv.c
> +++ b/drivers/gpu/drm/drm_drv.c
> @@ -67,6 +67,7 @@ static struct drm_ioctl_desc drm_ioctls[] = {
> DRM_IOCTL_DEF(DRM_IOCTL_GET_MAP, drm_getmap, 0),
> DRM_IOCTL_DEF(DRM_IOCTL_GET_CLIENT, drm_getclient, 0),
> DRM_IOCTL_DEF(DRM_IOCTL_GET_STATS, drm_getstats, 0),
> + DRM_IOCTL_DEF(DRM_IOCTL_GET_CAP, drm_getcap, 0),
> DRM_IOCTL_DEF(DRM_IOCTL_SET_VERSION, drm_setversion, DRM_MASTER),
>
> DRM_IOCTL_DEF(DRM_IOCTL_SET_UNIQUE, drm_setunique,
> DRM_AUTH|DRM_MASTER|DRM_ROOT_ONLY),
> diff --git a/drivers/gpu/drm/drm_ioctl.c b/drivers/gpu/drm/drm_ioctl.c
> index 47db4df..15a244b 100644
> --- a/drivers/gpu/drm/drm_ioctl.c
> +++ b/drivers/gpu/drm/drm_ioctl.c
> @@ -365,6 +365,19 @@ int drm_getstats(struct drm_device *dev, void *data,
> }
>
> /**
> + * Get device/driver capabilities
> + */
> +int drm_getcap(struct drm_device *dev, void *data, struct drm_file
> *file_priv)
> +{
> + struct drm_get_cap *req = data;
> +
> + req->value = 0;
> + if (dev->driver->get_cap)
> + req->value = (*dev->driver->get_cap)(dev, req->capability);
> + return 0;
> +}
> +
> +/**
> * Setversion ioctl.
> *
> * \param inode device inode.
> diff --git a/include/drm/drm.h b/include/drm/drm.h
> index e5f7061..7254f1a 100644
> --- a/include/drm/drm.h
> +++ b/include/drm/drm.h
> @@ -608,6 +608,12 @@ struct drm_gem_open {
> __u64 size;
> };
>
> +/** DRM_IOCTL_GET_CAP ioctl argument type */
> +struct drm_get_cap {
> + __u64 capability;
> + __u64 value;
> +};
> +
> #include "drm_mode.h"
>
> #define DRM_IOCTL_BASE 'd'
> @@ -628,6 +634,7 @@ struct drm_gem_open {
> #define DRM_IOCTL_GEM_CLOSE DRM_IOW (0x09, struct drm_gem_close)
> #define DRM_IOCTL_GEM_FLINK DRM_IOWR(0x0a, struct drm_gem_flink)
> #define DRM_IOCTL_GEM_OPEN DRM_IOWR(0x0b, struct drm_gem_open)
> +#define DRM_IOCTL_GET_CAP DRM_IOWR(0x0c, struct drm_get_cap)
>
> #define DRM_IOCTL_SET_UNIQUE DRM_IOW( 0x10, struct drm_unique)
> #define DRM_IOCTL_AUTH_MAGIC DRM_IOW( 0x11, struct drm_auth)
> diff --git a/include/drm/drmP.h b/include/drm/drmP.h
> index fe29aad..a3d5ce8 100644
> --- a/include/drm/drmP.h
> +++ b/include/drm/drmP.h
> @@ -869,6 +869,13 @@ struct drm_driver {
> void (*debugfs_cleanup)(struct drm_minor *minor);
>
> /**
> + * Driver-specific routine to query capabilities of device/driver.
> + *
> + * If not present, core drm will assume a return value of 0.
> + */
> + u64 (*get_cap)(struct drm_device *dev, u64 cap);
> +
> + /**
> * Driver-specific constructor for drm_gem_objects, to set up
> * obj->driver_private.
> *
> @@ -1264,6 +1271,8 @@ extern int drm_getclient(struct drm_device *dev, void
> *data,
> struct drm_file *file_priv);
> extern int drm_getstats(struct drm_device *dev, void *data,
> struct drm_file *file_priv);
> +extern int drm_getcap(struct drm_device *dev, void *data,
> + struct drm_file *file_priv);
> extern int drm_setversion(struct drm_device *dev, void *data,
> struct drm_file *file_priv);
> extern int drm_noop(struct drm_device *dev, void *data,
> --
> 1.7.4
>
>
___
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
[BUG] drm/i915 Screen corruption introduced by a00b10c360b35d6431a94cb
Hi Peter, The new corruption is "fixed" with daniel's patch from https://lkml.org/lkml/2011/2/20/25 On Mon, February 21, 2011 05:10, Peter Stuge wrote: > Indan Zupancic wrote: >> > Confirm I also have this issue on my X40, but there are other bugs >> > that are much more significant so I haven't bothered mentioning this. >> >> What issues? > > The one I confirmed is corrupted graphics within Gecko. I haven't had > Xv working for a long time either. Not sure if I've tried it with > this kernel though. Hmm, I recommend upgrading all the graphics userspace too then, current stuff works pretty well for me. > >> If it's backlight related, try my patch at: >> http://lkml.org/lkml/2011/2/16/447 > > Yeah also have backlight issue whenever the backlight level changes > by other means than Fn+Home/End. (Lid switch, screen blank) > I noticed the patch and that it solved the issue for someone. I'm not > too inconvenienced by this issue though. Well, it was for me, because I suspend all the time. > >> Or if the screen is black after suspend/screen blank > > Oh I've stopped using suspend since using KMS. I get way too angry > about all the state that I lose if resume fails so I don't risk it. I never had a failed resume with this laptop, not even once. But I avoided the early days of KMS because of all the instability. > >> Actually, a lot of bugs were recently introduced and fixed, with >> two months ago you're probably in the new-bugs-only period, so I >> can recommend trying 2.6.38-rc5. > > Yeah, I think it's time to pull Linus' git. I've been keeping an eye > on things i915 on the list for a good while already. There were coherency bugs for 855, but those seem to be fixed in the newer kernel too (2.6.37?), so another reason to upgrade. > >> This screen corruption is the only problem for me, but I don't do >> anything fancy with my laptop. The ipw2200 wireless driver is quite >> crappy, but it has always been as far as I know. > > I've used ipw2200 with great success for many years, but these days > I'm having fun (no, not at all) with ath9k where there is some very > fundamental hardware issue between laptop and card. I'd need to hook > up logic analyzer to say anything concrete, but I have no end of > problems with internal ath9k in my machine. It's completely unusable. My impression is that ipw2200's firmware is crappy. Everything is fine with a good signal, but with a bad one things don't work out too well after a time. > The only other annoying issue I have is that as wine enumerates > available screen resolutions i915 goes out to the VGA connector, > which on 855 always means a 600ms timeout when nothing is connected, > but this is a bit tricky because the hardware just can not tell if > anything is connected. I have the impression that got better too, but I haven't followed the development. Can't you just lower the timeout in the code, or let it cache the VGA status? The latter is what I'd expect the code to do. Running xrandr to see the modes takes 0.3s here. > I would be very happy if there was a knob for enabling/disabling the > VGA connector though. > > >> Good luck, > > Thanks, you too! I can recommend using PHC too, if you don't already: www.linux-phc.org With it I almost never have the fan running and it uses a lot less power when under load. (But don't use it till you got your system stable.) Greetings, Indan
[Bug 29502] Change to legacy algo to preferring lower post dividers breaks certain modelines
https://bugzilla.kernel.org/show_bug.cgi?id=29502 Chris Kennedy changed: What|Removed |Added Status|NEW |RESOLVED Resolution||CODE_FIX --- Comment #3 from Chris Kennedy 2011-02-21 06:11:50 --- Great, reverting works. Thanks, Chris -- 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 at lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
[PATCH 3/3] drm/vblank: Enable precise vblank timestamps for interlaced and doublescan modes.
Testing showed the current code can already handle doublescan
video modes just fine. A trivial tweak makes it work for interlaced
scanout as well.
Tested and shown to be precise on Radeon rv530, r600 and
Intel 945-GME.
Signed-off-by: Mario Kleiner
---
drivers/gpu/drm/drm_irq.c | 14 ++
1 files changed, 6 insertions(+), 8 deletions(-)
diff --git a/drivers/gpu/drm/drm_irq.c b/drivers/gpu/drm/drm_irq.c
index 891bf6d..2abcd15 100644
--- a/drivers/gpu/drm/drm_irq.c
+++ b/drivers/gpu/drm/drm_irq.c
@@ -493,6 +493,12 @@ void drm_calc_timestamping_constants(struct drm_crtc *crtc)
/* Dot clock in Hz: */
dotclock = (u64) crtc->hwmode.clock * 1000;
+ /* Fields of interlaced scanout modes are only halve a frame duration.
+* Double the dotclock to get halve the frame-/line-/pixelduration.
+*/
+ if (crtc->hwmode.flags & DRM_MODE_FLAG_INTERLACE)
+ dotclock *= 2;
+
/* Valid dotclock? */
if (dotclock > 0) {
/* Convert scanline length in pixels and video dot clock to
@@ -605,14 +611,6 @@ int drm_calc_vbltimestamp_from_scanoutpos(struct
drm_device *dev, int crtc,
return -EAGAIN;
}
- /* Don't know yet how to handle interlaced or
-* double scan modes. Just no-op for now.
-*/
- if (mode->flags & (DRM_MODE_FLAG_INTERLACE | DRM_MODE_FLAG_DBLSCAN)) {
- DRM_DEBUG("crtc %d: Noop due to unsupported mode.\n", crtc);
- return -ENOTSUPP;
- }
-
/* Get current scanout position with system timestamp.
* Repeat query up to DRM_TIMESTAMP_MAXRETRIES times
* if single query takes longer than max_error nanoseconds.
--
1.7.1
[PATCH 2/3] drm/vblank: Use memory barriers optimized for atomic_t instead of generics.
Documentation/atomic_ops.txt tells us that there are memory
barriers optimized for atomic_inc and other atomic_t ops.
Use these instead of smp_wmb(), and also to make the required
memory barriers around vblank counter increments more explicit.
Signed-off-by: Mario Kleiner
---
drivers/gpu/drm/drm_irq.c | 10 +++---
1 files changed, 7 insertions(+), 3 deletions(-)
diff --git a/drivers/gpu/drm/drm_irq.c b/drivers/gpu/drm/drm_irq.c
index 149805a..891bf6d 100644
--- a/drivers/gpu/drm/drm_irq.c
+++ b/drivers/gpu/drm/drm_irq.c
@@ -164,8 +164,10 @@ static void vblank_disable_and_save(struct drm_device
*dev, int crtc)
* available. In that case we can't account for this and just
* hope for the best.
*/
- if ((vblrc > 0) && (abs64(diff_ns) > 100))
+ if ((vblrc > 0) && (abs64(diff_ns) > 100)) {
atomic_inc(&dev->_vblank_count[crtc]);
+ smp_mb__after_atomic_inc();
+ }
/* Invalidate all timestamps while vblank irq's are off. */
clear_vblank_timestamps(dev, crtc);
@@ -858,10 +860,11 @@ static void drm_update_vblank_count(struct drm_device
*dev, int crtc)
if (rc) {
tslot = atomic_read(&dev->_vblank_count[crtc]) + diff;
vblanktimestamp(dev, crtc, tslot) = t_vblank;
- smp_wmb();
}
+ smp_mb__before_atomic_inc();
atomic_add(diff, &dev->_vblank_count[crtc]);
+ smp_mb__after_atomic_inc();
}
/**
@@ -1296,12 +1299,13 @@ void drm_handle_vblank(struct drm_device *dev, int crtc)
if (abs64(diff_ns) > DRM_REDUNDANT_VBLIRQ_THRESH_NS) {
/* Store new timestamp in ringbuffer. */
vblanktimestamp(dev, crtc, vblcount + 1) = tvblank;
- smp_wmb();
/* Increment cooked vblank count. This also atomically commits
* the timestamp computed above.
*/
+ smp_mb__before_atomic_inc();
atomic_inc(&dev->_vblank_count[crtc]);
+ smp_mb__after_atomic_inc();
} else {
DRM_DEBUG("crtc %d: Redundant vblirq ignored. diff_ns = %d\n",
crtc, (int) diff_ns);
--
1.7.1
[PATCH 1/3] drm/vblank: Use abs64(diff_ns) for s64 diff_ns instead of abs(diff_ns)
Use of abs() wrongly wrapped diff_ns to 32 bit, which gives a 1/4000
probability of a missed vblank increment at each vblank irq reenable
if the kms driver doesn't support high precision vblank timestamping.
Not a big deal in practice, but let's make it nice.
Signed-off-by: Mario Kleiner
---
drivers/gpu/drm/drm_irq.c |4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/gpu/drm/drm_irq.c b/drivers/gpu/drm/drm_irq.c
index 0054e95..149805a 100644
--- a/drivers/gpu/drm/drm_irq.c
+++ b/drivers/gpu/drm/drm_irq.c
@@ -164,7 +164,7 @@ static void vblank_disable_and_save(struct drm_device *dev,
int crtc)
* available. In that case we can't account for this and just
* hope for the best.
*/
- if ((vblrc > 0) && (abs(diff_ns) > 100))
+ if ((vblrc > 0) && (abs64(diff_ns) > 100))
atomic_inc(&dev->_vblank_count[crtc]);
/* Invalidate all timestamps while vblank irq's are off. */
@@ -1293,7 +1293,7 @@ void drm_handle_vblank(struct drm_device *dev, int crtc)
* e.g., due to spurious vblank interrupts. We need to
* ignore those for accounting.
*/
- if (abs(diff_ns) > DRM_REDUNDANT_VBLIRQ_THRESH_NS) {
+ if (abs64(diff_ns) > DRM_REDUNDANT_VBLIRQ_THRESH_NS) {
/* Store new timestamp in ringbuffer. */
vblanktimestamp(dev, crtc, vblcount + 1) = tvblank;
smp_wmb();
--
1.7.1
Vblank timestamping enhancements for drm-next and 2.6.38rc
Hi, the following three patches are some small improvements and fixes to the drm vblank timestamping. All fully tested on radeon rv530, r600 and on i915 with 945gme chipset. Please consider merging them for 2.6.38-rc as well. Thanks, -mario
[Bug 26552] Screen flickering with 2.6.37 [ATI X1600]
https://bugzilla.kernel.org/show_bug.cgi?id=26552 --- Comment #60 from Alex Deucher 2011-02-21 05:40:17 --- (In reply to comment #59) > > But killing upowerd makes the flickering go away. Ok, so it sounds like upowerd is polling the display every 30 seconds, so that is a upowerd bug rather than a driver bug. The driver will generate an event when a monitor is connected or disconnected, so upowerd should not be polling the displays manually. -- 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 at lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
[Bug 26552] Screen flickering with 2.6.37 [ATI X1600]
https://bugzilla.kernel.org/show_bug.cgi?id=26552 --- Comment #59 from Hugh Daschbach 2011-02-21 05:28:52 --- Very insightful question, thanks. The flickering goes away if I kill /usr/lib/upower/upowerd. The flickering was not present when I boot to a text console. It wasn't present when I started kdm. It did start as soon as my desktop started loading. It persisted even when I logged back out and switched to back to a text console. But killing upowerd makes the flickering go away. Many 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 at lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
[Bug 29502] Change to legacy algo to preferring lower post dividers breaks certain modelines
https://bugzilla.kernel.org/show_bug.cgi?id=29502 --- Comment #2 from Alex Deucher 2011-02-21 05:13:34 --- Created an attachment (id=48532) --> (https://bugzilla.kernel.org/attachment.cgi?id=48532) revert revert that patch. It's not needed any more as the bugs it originally fixed were fixed via an alternate method. -- 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 at lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
[BUG] drm/i915 Screen corruption introduced by a00b10c360b35d6431a94cb
Indan Zupancic wrote: > > Confirm I also have this issue on my X40, but there are other bugs > > that are much more significant so I haven't bothered mentioning this. > > What issues? The one I confirmed is corrupted graphics within Gecko. I haven't had Xv working for a long time either. Not sure if I've tried it with this kernel though. > If it's backlight related, try my patch at: > http://lkml.org/lkml/2011/2/16/447 Yeah also have backlight issue whenever the backlight level changes by other means than Fn+Home/End. (Lid switch, screen blank) I noticed the patch and that it solved the issue for someone. I'm not too inconvenienced by this issue though. > Or if the screen is black after suspend/screen blank Oh I've stopped using suspend since using KMS. I get way too angry about all the state that I lose if resume fails so I don't risk it. > Actually, a lot of bugs were recently introduced and fixed, with > two months ago you're probably in the new-bugs-only period, so I > can recommend trying 2.6.38-rc5. Yeah, I think it's time to pull Linus' git. I've been keeping an eye on things i915 on the list for a good while already. > This screen corruption is the only problem for me, but I don't do > anything fancy with my laptop. The ipw2200 wireless driver is quite > crappy, but it has always been as far as I know. I've used ipw2200 with great success for many years, but these days I'm having fun (no, not at all) with ath9k where there is some very fundamental hardware issue between laptop and card. I'd need to hook up logic analyzer to say anything concrete, but I have no end of problems with internal ath9k in my machine. It's completely unusable. The only other annoying issue I have is that as wine enumerates available screen resolutions i915 goes out to the VGA connector, which on 855 always means a 600ms timeout when nothing is connected, but this is a bit tricky because the hardware just can not tell if anything is connected. I would be very happy if there was a knob for enabling/disabling the VGA connector though. > Good luck, Thanks, you too! //Peter
[Bug 28932] new avivo PLL calculation in Radeon driver fails with certain modelines
https://bugzilla.kernel.org/show_bug.cgi?id=28932 Alex Deucher changed: What|Removed |Added CC||alexdeucher at gmail.com --- Comment #8 from Alex Deucher 2011-02-21 04:51:56 --- Comment 6 is not relevant to this bug and has been opened as a separate issue: bug 29502. -- 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 at lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
[Bug 26552] Screen flickering with 2.6.37 [ATI X1600]
https://bugzilla.kernel.org/show_bug.cgi?id=26552 --- Comment #58 from Alex Deucher 2011-02-21 04:28:06 --- (In reply to comment #57) > I see that this is closed as fixed. I've tested 2.6.38-rc5. I still see > flickering about once every thirty seconds on one head (analog) of a dual > monitor desktop system. Should I file a separate bug for this? Is this a regression? Is it the same commit(s) that's causing the problem for you? Flickering at a fixed interval like 30 seconds sounds like something is polling the display on a regular basis. Do you get the flickering in console before starting X or only after your desktop environment has loaded? -- 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 at lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
[Bug 34521] EnableColorTiling causes graphical distortion making X unusable
https://bugs.freedesktop.org/show_bug.cgi?id=34521 Michel Dänzer changed: What|Removed |Added Status|NEW |RESOLVED Resolution||DUPLICATE --- Comment #3 from Michel Dänzer 2011-02-21 04:26:58 PST --- *** This bug has been marked as a duplicate of bug 33929 *** -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 34521] EnableColorTiling causes graphical distortion making X unusable
https://bugs.freedesktop.org/show_bug.cgi?id=34521 Michel D?nzer changed: What|Removed |Added Status|NEW |RESOLVED Resolution||DUPLICATE --- Comment #3 from Michel D?nzer 2011-02-21 04:26:58 PST --- *** This bug has been marked as a duplicate of bug 33929 *** -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug.
[BUG] drm/i915 Screen corruption introduced by a00b10c360b35d6431a94cb
Hi, Feel free to ignore this post, it's a it of rambling. On Sun, February 20, 2011 11:55, Daniel Vetter wrote: > I've just noticed that one of the patches (the 2nd one) doesn't work > as advertised. Please retest with the attached one. I was wondering why that was, so I looked a bit closer: Old patch: diff --git a/drivers/gpu/drm/i915/i915_dma.c b/drivers/gpu/drm/i915/i915_dma.c index 17bd766..fbc21e3 100644 --- a/drivers/gpu/drm/i915/i915_dma.c +++ b/drivers/gpu/drm/i915/i915_dma.c @@ -763,7 +763,7 @@ static int i915_getparam(struct drm_device *dev, void *data, value = HAS_BLT(dev); break; case I915_PARAM_HAS_RELAXED_FENCING: - value = 1; + value = 0; break; case I915_PARAM_HAS_COHERENT_RINGS: value = 1; New patch: diff --git a/drivers/gpu/drm/i915/i915_dma.c b/drivers/gpu/drm/i915/i915_dma.c index 17bd766..d275c96 100644 --- a/drivers/gpu/drm/i915/i915_dma.c +++ b/drivers/gpu/drm/i915/i915_dma.c @@ -762,9 +762,6 @@ static int i915_getparam(struct drm_device *dev, void *data, case I915_PARAM_HAS_BLT: value = HAS_BLT(dev); break; - case I915_PARAM_HAS_RELAXED_FENCING: - value = 1; - break; case I915_PARAM_HAS_COHERENT_RINGS: value = 1; break; Looking at userspace intel-dri code it becomes clear why: gp.param = I915_PARAM_HAS_EXECBUF2; ret = drmIoctl(bufmgr_gem->fd, DRM_IOCTL_I915_GETPARAM, &gp); if (!ret) exec2 = 1; gp.param = I915_PARAM_HAS_BSD; ret = drmIoctl(bufmgr_gem->fd, DRM_IOCTL_I915_GETPARAM, &gp); bufmgr_gem->has_bsd = ret == 0; gp.param = I915_PARAM_HAS_BLT; ret = drmIoctl(bufmgr_gem->fd, DRM_IOCTL_I915_GETPARAM, &gp); bufmgr_gem->has_blt = ret == 0; gp.param = I915_PARAM_HAS_RELAXED_FENCING; ret = drmIoctl(bufmgr_gem->fd, DRM_IOCTL_I915_GETPARAM, &gp); bufmgr_gem->has_relaxed_fencing = ret == 0; The stupid code assumes that if an option is supported, the value is true too, while the kernel return code just tells whether it knows the option, and the value is copied to gp.value, but that's ignored by intel-dri! And a quick look at the other code gives a strong impression of lots of code dubplication with the kernel driver. More and more I'm getting the impression that you guys haven't gotten the interfaces between all bits right yet. All in all you seem to be somewhat in the same mess as filesystems are with overly complex interaction between the MM system, VFS and individual filesystems, all doing more or less the same in slightly different ways, instead of abstracting things properly. (Which is also just an impression, I haven't looked that close yet.) To give you an idea of a driver subsystem that does get it right: All the common libata code is 23k lines. (wc liba*) All the individual sata drivers code combined are 19k lines. (wc sata_*) DRM does it differently (only counting .c files): Common drm code is 21k i915 is 37k nouveau is 47k radeon is 68k And then there are the userspace drivers: xf86-video-intel/src/*.c is 16k drm/intel/ is 4k mesa/drivers/dri/i915/ is 22k Of course graphics drivers are a lot more complex than sata drivers, but because of that extra complexity it's a lot easier to make things even more compex by getting the interfaces wrong. So what I'm saying is, there seems a lot of room for improvements. The intel driver code I've seen is mostly busy with infrastructure stuff and talking to other bits and pieces, but it doesn't seem to do much actual work. To come back to the I915_PARAM_HAS_RELAXED_FENCING thing: Why is this interface there at all? It seems like a driver internal detail thing. Either it should be handled entirely in the kernel driver, and this interface wouldn't be there, or, if the userspace driver has to know about it, it should be entirely handled by the userspace driver and not done by the kernel driver at all. Another slightly annoying thing: The code is littered with gen checks, while very often the only difference is a register or size value. Why not put those in a gen specific hardware description structure which is used unconditionally, instead of having a lot of almost the same code? The current design seems overly complex and fragile, and I think you guys make it more difficult for yourself than necessary. Greetings, Indan
[Bug 34418] SuperTuxRacer 0.7/Warzone 2100 and r300g MemoryFault (64bit only)
https://bugs.freedesktop.org/show_bug.cgi?id=34418
--- Comment #11 from Wiktor Janas 2011-02-21 03:41:51 PST
---
I did tests with kwin crashes and they start with 2a904fd ("st/mesa: set vertex
arrays state only when necessary"). My system is 64-bit too, as indicated in
original bug report.
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug.
___
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 34418] SuperTuxRacer 0.7/Warzone 2100 and r300g MemoryFault (64bit only)
https://bugs.freedesktop.org/show_bug.cgi?id=34418
--- Comment #11 from Wiktor Janas 2011-02-21 03:41:51
PST ---
I did tests with kwin crashes and they start with 2a904fd ("st/mesa: set vertex
arrays state only when necessary"). My system is 64-bit too, as indicated in
original bug report.
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug.
[Bug 28902] activated KMS leads to complete freeze when viewing BIG images in Iceweasel
https://bugzilla.kernel.org/show_bug.cgi?id=28902 --- Comment #7 from spamfang1...@yahoo.de 2011-02-21 10:42:45 --- Created an attachment (id=48552) --> (https://bugzilla.kernel.org/attachment.cgi?id=48552) these are the crashlogs from 2.6.37 -- 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-de...@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 28902] activated KMS leads to complete freeze when viewing BIG images in Iceweasel
https://bugzilla.kernel.org/show_bug.cgi?id=28902 --- Comment #6 from spamfang1...@yahoo.de 2011-02-21 10:41:25 --- Here i add some logs from 2 different crashes with 2.6.37. I archived them right after the crash by rebooting into runlevel 1, so that X was not started. -- 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-de...@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 29572] New: Radeon card reports wrong temperature when switched off
https://bugzilla.kernel.org/show_bug.cgi?id=29572 Summary: Radeon card reports wrong temperature when switched off 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-...@kernel-bugs.osdl.org ReportedBy: m...@3v1n0.net CC: m...@3v1n0.net Regression: Yes In previous versions of the kernel (I've tested the 2.6.37 version) when the I switched off the radeon card using vga_switcheroo libsensors was correctly reporting that the radeon temperature was 0° (or invalid). This doesn't happen any more using the latest kernel, in fact (after the commit 20d391d72519527d2266a0166490118b40ff998d, I figure) when my radeon card has been switched off (or after a suspend/resume cycle) sensors indicates: radeon-pci-0100 Adapter: PCI adapter temp1: +2147355.6°C This is obiouvsly impossible. -- 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-de...@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
[BUG] drm/i915 Screen corruption introduced by a00b10c360b35d6431a94cb
Hi, On Sun, February 20, 2011 14:21, Daniel Vetter wrote: > Well, don't start jumping around, yet. These patches are just to rule > out some theories. I know, that's why I said I don't mind testing other patches. > Now: Is it fixed with just the 2nd patch alone or do you > need both patches? This is very important, so please test extensively > whether there are really no corruptions with just the 2nd patch. I only applied the 2nd version of the 2nd patch, no other patches. The horizontal garbage stripes are gone for sure. It's a lot easier to prove that something doesn't work than to prove it does, but I'll keep running it for a while and see if I can spot any other badness. If it's hard to trigger it's also very hard to find out what causes it. Without your 2nd patch I always get the garbage on certain webpages, so I'm quite confident that the original source is located for this particular problem. Greetings, Indan
[Bug 34427] Graphical corruption when opening windows
https://bugs.freedesktop.org/show_bug.cgi?id=34427 --- Comment #3 from Harald Judt 2011-02-21 01:43:42 PST --- No, Option "ColorTiling" is not in xorg.conf. I've added it now, but setting it to true or false makes no difference at all. Option "AccelMethod" "EXA" Option "EnablePageFlip" "on" Option "ColorTiling" "true" Option "ClockGating" "1" Option "DynamicPM" "on" I'd say it can't be page flipping either because the problems started quite some time before it was introduced. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 34427] Graphical corruption when opening windows
https://bugs.freedesktop.org/show_bug.cgi?id=34427 --- Comment #3 from Harald Judt 2011-02-21 01:43:42 PST --- No, Option "ColorTiling" is not in xorg.conf. I've added it now, but setting it to true or false makes no difference at all. Option "AccelMethod" "EXA" Option "EnablePageFlip" "on" Option "ColorTiling" "true" Option "ClockGating" "1" Option "DynamicPM" "on" I'd say it can't be page flipping either because the problems started quite some time before it was introduced. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug.
[Bug 34521] EnableColorTiling causes graphical distortion making X unusable
https://bugs.freedesktop.org/show_bug.cgi?id=34521 --- Comment #2 from James Broadhead 2011-02-21 01:28:13 PST --- Created an attachment (id=43591) --> (https://bugs.freedesktop.org/attachment.cgi?id=43591) Photograph of screen when bugging. Note: Picture is cut off by failed upload. See top half for bug info. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 34521] EnableColorTiling causes graphical distortion making X unusable
https://bugs.freedesktop.org/show_bug.cgi?id=34521 --- Comment #2 from James Broadhead 2011-02-21 01:28:13 PST --- Created an attachment (id=43591) --> (https://bugs.freedesktop.org/attachment.cgi?id=43591) Photograph of screen when bugging. Note: Picture is cut off by failed upload. See top half for bug info. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug.
[Bug 34521] EnableColorTiling causes graphical distortion making X unusable
https://bugs.freedesktop.org/show_bug.cgi?id=34521 --- Comment #1 from James Broadhead 2011-02-21 01:27:18 PST --- Created an attachment (id=43590) --> (https://bugs.freedesktop.org/attachment.cgi?id=43590) Xorg.0.log Xorg.0.log for completeness -- there is no error or warning info. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 34521] New: EnableColorTiling causes graphical distortion making X unusable
https://bugs.freedesktop.org/show_bug.cgi?id=34521 Summary: EnableColorTiling causes graphical distortion making X unusable Product: Mesa Version: 7.10 Platform: Other OS/Version: All Status: NEW Severity: normal Priority: medium Component: Drivers/Gallium/r600 AssignedTo: dri-devel@lists.freedesktop.org ReportedBy: jamesbroadh...@gmail.com With EnableColorTiling enabled, when I run certain programs, my X server becomes completely distorted, with screen elements rendering correctly, but in mis-positioned blocks all over the screen. X remains responsive, but I cannot return it to a usable state from the 'bugging' condition. There is no output in dmesg or Xorg.0.log relevant to this. Setup: Distro: Gentoo Kernels: linux-2.6.36, linux-2.6.37, linux-2.6.38-rc5 Driver : x11-drivers/xf86-video-ati-6.14.0 DDX : r600 (another user in #gentoo had this with r300) Mesa : media-libs/mesa-7.10 (gallium and classic) LibDRM: x11-libs/libdrm-2.4.23 X-Server: x11-base/xorg-server-1.9.4 KMS : Enabled EnablePageFlip : Enabled, Disabled EnableColorTiling: Enabled I originally encountered this bug with the 'classic' mesa renderer(?), but it affects 'gallium' also. Reproduction: EnableColorTiling >> /etc/X11/xorg.conf Start X Run Openoffice (Or some in-browser java applets, or Gogglesmm, or some elements of calibre) Hardware: 01:00.0 VGA compatible controller: ATI Technologies Inc RV770 [Radeon HD 4850] -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 34521] EnableColorTiling causes graphical distortion making X unusable
https://bugs.freedesktop.org/show_bug.cgi?id=34521 --- Comment #1 from James Broadhead 2011-02-21 01:27:18 PST --- Created an attachment (id=43590) --> (https://bugs.freedesktop.org/attachment.cgi?id=43590) Xorg.0.log Xorg.0.log for completeness -- there is no error or warning info. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug.
[Bug 34521] New: EnableColorTiling causes graphical distortion making X unusable
https://bugs.freedesktop.org/show_bug.cgi?id=34521 Summary: EnableColorTiling causes graphical distortion making X unusable Product: Mesa Version: 7.10 Platform: Other OS/Version: All Status: NEW Severity: normal Priority: medium Component: Drivers/Gallium/r600 AssignedTo: dri-devel at lists.freedesktop.org ReportedBy: jamesbroadhead at gmail.com With EnableColorTiling enabled, when I run certain programs, my X server becomes completely distorted, with screen elements rendering correctly, but in mis-positioned blocks all over the screen. X remains responsive, but I cannot return it to a usable state from the 'bugging' condition. There is no output in dmesg or Xorg.0.log relevant to this. Setup: Distro: Gentoo Kernels: linux-2.6.36, linux-2.6.37, linux-2.6.38-rc5 Driver : x11-drivers/xf86-video-ati-6.14.0 DDX : r600 (another user in #gentoo had this with r300) Mesa : media-libs/mesa-7.10 (gallium and classic) LibDRM: x11-libs/libdrm-2.4.23 X-Server: x11-base/xorg-server-1.9.4 KMS : Enabled EnablePageFlip : Enabled, Disabled EnableColorTiling: Enabled I originally encountered this bug with the 'classic' mesa renderer(?), but it affects 'gallium' also. Reproduction: EnableColorTiling >> /etc/X11/xorg.conf Start X Run Openoffice (Or some in-browser java applets, or Gogglesmm, or some elements of calibre) Hardware: 01:00.0 VGA compatible controller: ATI Technologies Inc RV770 [Radeon HD 4850] -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug.
[PATCH] Revert "drm/radeon/kms: switch back to min->max pll post divider iteration"
This reverts commit a6f9761743bf35b052180f4a8bdae4d2cc0465f6.
Remove this commit as it is no longer necessary. The relevant bugs
were fixed properly in:
drm/radeon/kms: hopefully fix pll issues for real (v3)
5b40ddf888398ce4cccbf3b9d0a18d90149ed7ff
drm/radeon/kms: add missing frac fb div flag for dce4+
9f4283f49f0a96a64c5a45fe56f0f8c942885eef
This commit also broke certain ~5 Mhz modes on old arcade monitors,
so reverting this commit fixes:
https://bugzilla.kernel.org/show_bug.cgi?id=29502
Signed-off-by: Alex Deucher
Cc: stable at kernel.org
---
drivers/gpu/drm/radeon/radeon_display.c |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/drivers/gpu/drm/radeon/radeon_display.c
b/drivers/gpu/drm/radeon/radeon_display.c
index 0e65709..3e7e7f9 100644
--- a/drivers/gpu/drm/radeon/radeon_display.c
+++ b/drivers/gpu/drm/radeon/radeon_display.c
@@ -971,7 +971,7 @@ void radeon_compute_pll_legacy(struct radeon_pll *pll,
max_fractional_feed_div = pll->max_frac_feedback_div;
}
- for (post_div = min_post_div; post_div <= max_post_div; ++post_div) {
+ for (post_div = max_post_div; post_div >= min_post_div; --post_div) {
uint32_t ref_div;
if ((pll->flags & RADEON_PLL_NO_ODD_POST_DIV) && (post_div & 1))
--
1.7.1.1
[PATCH] gpu: drm: nouveau: Remove unused variable to prevent compile warning.
Remove unused variable "dev_priv" in function "nv50_vm_map_pgt" to
prevent compile warning.
Signed-off-by: Ralf Thielow
---
drivers/gpu/drm/nouveau/nv50_vm.c |1 -
1 files changed, 0 insertions(+), 1 deletions(-)
diff --git a/drivers/gpu/drm/nouveau/nv50_vm.c
b/drivers/gpu/drm/nouveau/nv50_vm.c
index 459ff08..03c1a63 100644
--- a/drivers/gpu/drm/nouveau/nv50_vm.c
+++ b/drivers/gpu/drm/nouveau/nv50_vm.c
@@ -31,7 +31,6 @@ void
nv50_vm_map_pgt(struct nouveau_gpuobj *pgd, u32 pde,
struct nouveau_gpuobj *pgt[2])
{
- struct drm_nouveau_private *dev_priv = pgd->dev->dev_private;
u64 phys = 0xdeadcafeULL;
u32 coverage = 0;
--
1.7.1
___
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 26552] Screen flickering with 2.6.37 [ATI X1600]
https://bugzilla.kernel.org/show_bug.cgi?id=26552 Hugh Daschbach changed: What|Removed |Added CC||hdasch at gmail.com --- Comment #57 from Hugh Daschbach 2011-02-21 00:56:21 --- I see that this is closed as fixed. I've tested 2.6.38-rc5. I still see flickering about once every thirty seconds on one head (analog) of a dual monitor desktop system. Should I file a separate bug for this? 01:00.0 VGA compatible controller: ATI Technologies Inc RV710 [Radeon HD 4350] (prog-if 00 [VGA controller]) Subsystem: Hightech Information System Ltd. Device 2002 Flags: bus master, fast devsel, latency 0, IRQ 45 Memory at d000 (64-bit, prefetchable) [size=256M] Memory at fbde (64-bit, non-prefetchable) [size=64K] I/O ports at c000 [size=256] Expansion ROM at fbdc [disabled] [size=128K] Capabilities: Kernel driver in use: radeon Kernel modules: radeon -- 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 at lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
[Bug 28932] new avivo PLL calculation in Radeon driver fails with certain modelines
https://bugzilla.kernel.org/show_bug.cgi?id=28932 Florian Mickler changed: What|Removed |Added Status|RESOLVED|CLOSED --- Comment #9 from Florian Mickler 2011-02-21 08:42:00 --- Thx, closing. -- 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-de...@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 34418] SuperTuxRacer 0.7/Warzone 2100 and r300g MemoryFault (64bit only)
https://bugs.freedesktop.org/show_bug.cgi?id=34418 --- Comment #10 from Fabio Pedretti 2011-02-21 00:35:16 PST --- This is possibly a different bug (or also a gdb one), but when I run supertuxkart under gdb I get thousands of the following messages: [New Thread 0xb6afdb70 (LWP 9974)] [Thread 0xb6afdb70 (LWP 9974) exited] [New Thread 0xb6afdb70 (LWP 9975)] [Thread 0xb6afdb70 (LWP 9975) exited] and performance is less then half (fps are shown when pressing F12). Running without gdb or with RADEON_THREAD=0 + gdb fixes that. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 34418] SuperTuxRacer 0.7/Warzone 2100 and r300g MemoryFault (64bit only)
https://bugs.freedesktop.org/show_bug.cgi?id=34418 --- Comment #10 from Fabio Pedretti 2011-02-21 00:35:16 PST --- This is possibly a different bug (or also a gdb one), but when I run supertuxkart under gdb I get thousands of the following messages: [New Thread 0xb6afdb70 (LWP 9974)] [Thread 0xb6afdb70 (LWP 9974) exited] [New Thread 0xb6afdb70 (LWP 9975)] [Thread 0xb6afdb70 (LWP 9975) exited] and performance is less then half (fps are shown when pressing F12). Running without gdb or with RADEON_THREAD=0 + gdb fixes that. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug.
