[Bug 27211] endless PROTECTION_FAULT logs, Nouveau drm, TNT card
http://bugs.freedesktop.org/show_bug.cgi?id=27211 --- Comment #3 from Marcin Kościelnicki koria...@0x04.net 2010-03-21 01:48:30 PST --- It has to be nouveau.noaccel=1 if passed on main kernel line. -- Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. -- Download Intel#174; Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
[Bug 27211] endless PROTECTION_FAULT logs, Nouveau drm, TNT card
http://bugs.freedesktop.org/show_bug.cgi?id=27211 --- Comment #4 from Pekka Paalanen p...@iki.fi 2010-03-21 01:59:21 PST --- The noaccel parameter is a Nouveau module parameter, so either pass it to the nouveau module on load (modprobe.conf), or if nouveau is built-in, nouveau.noaccel=1 on kernel command line. Your X uses the Vesa driver? That will screw up the card, if Nouveau is loaded. Either use Nouveau DRM with Nouveau DDX, or no Nouveau at all with Vesa DDX. -- Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. -- Download Intel#174; Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Mesa3d-dev] New branch to switch st/dri to st_api.h
On Sun, Mar 21, 2010 at 5:19 PM, Sedat Dilek sedat.di...@googlemail.com wrote: Hi Chia-I (hope this is the first name), It is :) I've merged the branch. All Gallium DRI drivers now use st_api.h instead of st_public.h. If you notice any regression due the merge, please let me know so that I can work on it. The last days I have tested your gallium-st-api-dri GIT branch by merging into mesa master GIT. I was testing here with r300g st/dri on an RV515 radeon gfxcard. So, here is my positive feedback: Works here, lovely. Thanks for the inspiring feedback, and for testing out the branch. Even I see OpenArena got a boost from ~25fps (7.8 GIT) to ~32fps (master GIT incl. gallium-st-api-dri merge) $ cat oa_benchmark.txt s...@seduxbox:~/src/anholt_oa-benchmark$ openarena +exec anholt 21 | egrep -e '[0-9]+ frames' 840 frames 26.3 seconds 31.9 fps 9.0/31.3/90.0/9.9 ms Thanks for your work! Unless I have some magic power that I am not aware of, the boost should be attributed to r300g developers. -- o...@lunarg.com -- Download Intel#174; Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
[Bug 15276] latest git kernel: general protection fault: 0000 [#1]
https://bugzilla.kernel.org/show_bug.cgi?id=15276 --- Comment #58 from Michał Witkowski ne...@o2.pl 2010-03-21 15:02:26 --- Jerome, will the fix be merged into the mainline? Cheers, Michal -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are watching the assignee of the bug. -- Download Intel#174; Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
[PATCH] drm/radeon/kms: fix display bandwidth setup on rs4xx
From 9d0704674873023f27aee0d629ad9c93f07315b7 Mon Sep 17 00:00:00 2001 From: Alex Deucher alexdeuc...@gmail.com Date: Sun, 21 Mar 2010 11:09:24 -0400 Subject: [PATCH] drm/radeon/kms: fix display bandwidth setup on rs4xx I missed rs4xx in 7f1e613daf0fdd0884316ab25a749db3c671329e Fixes fdo bug 27219. Signed-off-by: Alex Deucher alexdeuc...@gmail.com --- drivers/gpu/drm/radeon/rs400.c |1 + 1 files changed, 1 insertions(+), 0 deletions(-) diff --git a/drivers/gpu/drm/radeon/rs400.c b/drivers/gpu/drm/radeon/rs400.c index a9e06b0..0181d08 100644 --- a/drivers/gpu/drm/radeon/rs400.c +++ b/drivers/gpu/drm/radeon/rs400.c @@ -263,6 +263,7 @@ void rs400_mc_init(struct radeon_device *rdev) base = (RREG32(RADEON_NB_TOM) 0x) 16; radeon_vram_location(rdev, rdev-mc, base); radeon_gtt_location(rdev, rdev-mc); + radeon_update_bandwidth_info(rdev); } uint32_t rs400_mc_rreg(struct radeon_device *rdev, uint32_t reg) -- 1.5.6.3 0001-drm-radeon-kms-fix-display-bandwidth-setup-on-rs4xx.patch Description: application/mbox -- Download Intel#174; Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev-- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
[Bug 27219] drm-radeon-testing branch bisected: Radeon xpress 200m freezes while booting
http://bugs.freedesktop.org/show_bug.cgi?id=27219 --- Comment #1 from Alex Deucher ag...@yahoo.com 2010-03-21 08:15:59 PST --- Created an attachment (id=34295) -- (http://bugs.freedesktop.org/attachment.cgi?id=34295) fix Whoops. I missed rs4xx in the conversion. this patch will fix it up. -- Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. -- Download Intel#174; Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
[Bug 27221] Big 3D performance regression and broken textures on R200
http://bugs.freedesktop.org/show_bug.cgi?id=27221 Alex Deucher ag...@yahoo.com changed: What|Removed |Added AssignedTo|xorg-driver-...@lists.x.org |dri- ||de...@lists.sourceforge.net -- Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. -- Download Intel#174; Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
[Bug 27221] Big 3D performance regression and broken textures on R200
http://bugs.freedesktop.org/show_bug.cgi?id=27221 --- Comment #4 from Pauli suok...@gmail.com 2010-03-21 08:25:51 PST --- What version of mesa are you using? What version of mesa was last to work? -- Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. -- Download Intel#174; Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
[Bug 27206] Blurred screen with latest drm-next-radeon and KMS
http://bugs.freedesktop.org/show_bug.cgi?id=27206 --- Comment #8 from Alex Deucher ag...@yahoo.com 2010-03-21 08:26:24 PST --- (In reply to comment #6) (In reply to comment #5) Created an attachment (id=34264) -- (http://bugs.freedesktop.org/attachment.cgi?id=34264) [details] [details] dmesg from garbled screen Kernel is compiled from up to date git drm-next-radeon on x86 platform with Fedora 12 userland. Plus all patches from: http://people.freedesktop.org/~agd5f/pm2/ which could all be applied cleanly. Which ones didn't apply? I wouldn't recommend that patch set unless you apply all of them (they apply to drm-radeon-testing). Do you still have problems without those patches applied? -- Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. -- Download Intel#174; Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
[Bug 27225] New: Radeon KMS fails on Xpress 200M
http://bugs.freedesktop.org/show_bug.cgi?id=27225 Summary: Radeon KMS fails on Xpress 200M Product: DRI Version: unspecified Platform: Other OS/Version: All Status: NEW Severity: normal Priority: medium Component: DRM/Radeon AssignedTo: dri-devel@lists.sourceforge.net ReportedBy: maarten.fonvi...@gmail.com On an Ubuntu Lucid installation (at the moment of writing still beta) KMS should be enabled on the Radeon Xpress 200M. But intialization of KMS does fail with the lines in attachment kms_fail.txt Apparently the driver doesn't like the card's memory, which I believe is an IGP card without memory itself. Next thing I tried was passing 'radeon agpmode=-1' to the module, to force it into PCI mode. (even though the card does say in lshw: description: VGA compatible controller product: RC410 [Radeon Xpress 200M] vendor: ATI Technologies Inc physical id: 5 bus info: p...@:01:05.0 version: 00 width: 32 bits clock: 66MHz capabilities: agp agp-3.0 pm msi cap_list configuration: latency=64 mingnt=8 resources: memory:c000-cfff(prefetchable) ioport:9800(size=256) memory:fe1f-fe1f memory:fe1cfe1d(prefetchable) and so I think is an AGP card and not a PCI(E) card) anyhow, this does seem to improve the situation, because now can KMS be loaded. But a new error appears: it says it fails the r100_ring_test with 0xCAFEDEAD. I don't know why it fails, I found multiple people with this problem on the internet, but nobody with a fix. The log of this one I will attach as kms_forceagp-1_fail.txt Notes: Tested: kernel 2.6.32(from lucid with DRM code), 2.6.33 and 2.6.34-rc1 Tested: DRM 2.4.18 (from lucid), 2.4.19+git20100318 (xorg-edgers repository) I load radeon in /etc/modules to force the loading of the driver in time to assure that the firmware does load in time (recommended by developers) Already thanks for your time, if you need more information/testing I am willing to of course. -- Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. -- Download Intel#174; Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
[Bug 27225] Radeon KMS fails on Xpress 200M
http://bugs.freedesktop.org/show_bug.cgi?id=27225 --- Comment #1 from Maarten Fonville maarten.fonvi...@gmail.com 2010-03-21 08:29:04 PST --- Created an attachment (id=34296) -- (http://bugs.freedesktop.org/attachment.cgi?id=34296) Normal failure -- Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. -- Download Intel#174; Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
[Bug 27225] Radeon KMS fails on Xpress 200M
http://bugs.freedesktop.org/show_bug.cgi?id=27225 --- Comment #2 from Maarten Fonville maarten.fonvi...@gmail.com 2010-03-21 08:29:24 PST --- Created an attachment (id=34297) -- (http://bugs.freedesktop.org/attachment.cgi?id=34297) Failure with forcing agpmode=-1 -- Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. -- Download Intel#174; Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
[Bug 27225] Radeon KMS fails on Xpress 200M
http://bugs.freedesktop.org/show_bug.cgi?id=27225 --- Comment #3 from Alex Deucher ag...@yahoo.com 2010-03-21 08:55:03 PST --- Created an attachment (id=34298) -- (http://bugs.freedesktop.org/attachment.cgi?id=34298) fix RS4xx+ IGP chips use an internal gart, however, some of them have the agp cap bits set in their pci configs. Make sure to clear the AGP flag as AGP will not work with them. -- Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. -- Download Intel#174; Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
[PATCH] drm/radeon/kms: never treat rs4xx as AGP
From 7ac6ef362be216990835bfb5a7a71fdcf6d04ff5 Mon Sep 17 00:00:00 2001
From: Alex Deucher alexdeuc...@gmail.com
Date: Sun, 21 Mar 2010 11:51:24 -0400
Subject: [PATCH] drm/radeon/kms: never treat rs4xx as AGP
RS4xx+ IGP chips use an internal gart, however,
some of them have the agp cap bits set in their pci
configs. Make sure to clear the AGP flag as AGP will
not work with them.
Should fix fdo bug 27225
Signed-off-by: Alex Deucher alexdeuc...@gmail.com
---
drivers/gpu/drm/radeon/radeon_device.c |8
1 files changed, 8 insertions(+), 0 deletions(-)
diff --git a/drivers/gpu/drm/radeon/radeon_device.c
b/drivers/gpu/drm/radeon/radeon_device.c
index 75f7b1e..8de9edd 100644
--- a/drivers/gpu/drm/radeon/radeon_device.c
+++ b/drivers/gpu/drm/radeon/radeon_device.c
@@ -563,6 +563,14 @@ int radeon_device_init(struct radeon_device *rdev,
return r;
radeon_check_arguments(rdev);
+ /* all of the newer IGP chips have an internal gart
+* However some rs4xx report as AGP, so remove that here.
+*/
+ if ((rdev-family = CHIP_RS400)
+ (rdev-flags RADEON_IS_AGP)) {
+ rdev-flags = ~RADEON_IS_AGP;
+ }
+
if (rdev-flags RADEON_IS_AGP radeon_agpmode == -1) {
radeon_agp_disable(rdev);
}
--
1.5.6.3
0001-drm-radeon-kms-never-treat-rs4xx-as-AGP.patch
Description: application/mbox
--
Download Intel#174; Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev--
___
Dri-devel mailing list
Dri-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dri-devel
[Bug 27225] Radeon KMS fails on Xpress 200M
http://bugs.freedesktop.org/show_bug.cgi?id=27225 Maarten Fonville maarten.fonvi...@gmail.com changed: What|Removed |Added CC||maarten.fonvi...@gmail.com --- Comment #4 from Maarten Fonville maarten.fonvi...@gmail.com 2010-03-21 09:14:28 PST --- I will try this fix immediately and *wow* you are fast :) and (hopefully) a hero ;) -- Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. -- Download Intel#174; Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [PATCH] drm/radeon/kms: never treat rs4xx as AGP
ARGH! typo in that patch. Correct version attached.
Alex
On Sun, Mar 21, 2010 at 11:56 AM, Alex Deucher alexdeuc...@gmail.com wrote:
From 7ac6ef362be216990835bfb5a7a71fdcf6d04ff5 Mon Sep 17 00:00:00 2001
From: Alex Deucher alexdeuc...@gmail.com
Date: Sun, 21 Mar 2010 11:51:24 -0400
Subject: [PATCH] drm/radeon/kms: never treat rs4xx as AGP
RS4xx+ IGP chips use an internal gart, however,
some of them have the agp cap bits set in their pci
configs. Make sure to clear the AGP flag as AGP will
not work with them.
Should fix fdo bug 27225
Signed-off-by: Alex Deucher alexdeuc...@gmail.com
---
drivers/gpu/drm/radeon/radeon_device.c | 8
1 files changed, 8 insertions(+), 0 deletions(-)
diff --git a/drivers/gpu/drm/radeon/radeon_device.c
b/drivers/gpu/drm/radeon/radeon_device.c
index 75f7b1e..8de9edd 100644
--- a/drivers/gpu/drm/radeon/radeon_device.c
+++ b/drivers/gpu/drm/radeon/radeon_device.c
@@ -563,6 +563,14 @@ int radeon_device_init(struct radeon_device *rdev,
return r;
radeon_check_arguments(rdev);
+ /* all of the newer IGP chips have an internal gart
+ * However some rs4xx report as AGP, so remove that here.
+ */
+ if ((rdev-family = CHIP_RS400)
+ (rdev-flags RADEON_IS_AGP)) {
+ rdev-flags = ~RADEON_IS_AGP;
+ }
+
if (rdev-flags RADEON_IS_AGP radeon_agpmode == -1) {
radeon_agp_disable(rdev);
}
--
1.5.6.3
0001-drm-radeon-kms-never-treat-rs4xx-as-AGP.patch
Description: application/mbox
--
Download Intel#174; Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev--
___
Dri-devel mailing list
Dri-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dri-devel
[Bug 27219] drm-radeon-testing branch bisected: Radeon xpress 200m freezes while booting
http://bugs.freedesktop.org/show_bug.cgi?id=27219 --- Comment #2 from Tom Stellard tstel...@gmail.com 2010-03-21 12:10:10 PST --- I applied the patch and now it works. Thanks. -- Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. -- Download Intel#174; Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
[Bug 15276] latest git kernel: general protection fault: 0000 [#1]
https://bugzilla.kernel.org/show_bug.cgi?id=15276 --- Comment #59 from Rafael J. Wysocki r...@sisk.pl 2010-03-21 19:45:21 --- Handled-By : Jérôme Glisse gli...@freedesktop.org -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are watching the assignee of the bug. -- Download Intel#174; Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
[Bug 27219] drm-radeon-testing branch bisected: Radeon xpress 200m freezes while booting
http://bugs.freedesktop.org/show_bug.cgi?id=27219 Alex Deucher ag...@yahoo.com changed: What|Removed |Added Status|NEW |RESOLVED Resolution||FIXED --- Comment #3 from Alex Deucher ag...@yahoo.com 2010-03-21 12:54:27 PST --- I've sent the corrected patch to Dave. -- Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. -- Download Intel#174; Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
[Bug 15293] Flash video laggy inside Firefox only with KMS
https://bugzilla.kernel.org/show_bug.cgi?id=15293 Rafael J. Wysocki r...@sisk.pl changed: What|Removed |Added Status|NEEDINFO|CLOSED Resolution||CODE_FIX -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are watching the assignee of the bug. -- Download Intel#174; Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
2.6.34-rc2: Reported regressions 2.6.32 - 2.6.33
[NOTE: Well, we seem to have two reports that are almost 2 months old and with patches. Somebody care to push those patches to Linus or say why they are invalid, pretty please?] This message contains a list of some post-2.6.32 regressions introduced before 2.6.33, 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.32 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 2010-03-21 133 38 34 2010-02-21 115 34 27 2010-02-15 112 34 31 2010-02-07 97 27 20 2010-02-01 85 26 21 2010-01-24 75 29 23 2010-01-10 55 33 21 2009-12-29 36 34 27 Unresolved regressions -- Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=15585 Subject : [Bisected Regression in 2.6.32.8] i915 with KMS enabled causes memorycorruption when resuming from suspend-to-disk Submitter : M. Vefa Bicakci bic...@superonline.com Date: 2010-03-13 5:11 (9 days old) First-Bad-Commit: http://git.kernel.org/git/linus/d8e0902806c0bd2ccc4f6a267ff52565a3ec933b Message-ID : 4b9b1e8f.5090...@superonline.com References : http://marc.info/?l=linux-kernelm=126845754409543w=2 Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=15544 Subject : black screen upon S3 resume, syslog has render error and page table error Submitter : Sanjoy Mahajan san...@mit.edu Date: 2010-03-16 00:45 (6 days old) Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=15534 Subject : 07ca:b808 crashing and breaking usb's Submitter : Alex Fiestas a...@eyeos.org Date: 2010-03-14 15:56 (8 days old) Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=15527 Subject : [BUG] NULL pointer dereference in i915_gem_object_save_bit_17_swizzle Submitter : Justin Madru jd...@gawab.com Date: 2010-03-04 9:00 (18 days old) First-Bad-Commit: http://git.kernel.org/git/linus/280b713b5b0fd84cf2469098aee88acbb5de859c Message-ID : 20100304090047.23689.qm...@info88.gawab.com References : http://marc.info/?l=linux-kernelm=126769366716380w=2 Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=15525 Subject : Blank screen after some time, after hibernation/suspend Submitter : cap...@matrix.inten.pl Date: 2010-03-12 17:24 (10 days old) Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=15502 Subject : render error detected, EIR: 0x0010 Submitter : Artem Anisimov aanisi...@inbox.ru Date: 2010-03-10 05:45 (12 days old) Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=15494 Subject : BUG: key 88013d4f4c70 not in .data! when loading microcode.ko Submitter : Alex Villacis Lasso avill...@ceibo.fiec.espol.edu.ec Date: 2010-03-09 16:28 (13 days old) Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=15474 Subject : r8169 fails to bring up ethernet Submitter : Matteo rootki...@yahoo.it Date: 2010-03-07 23:57 (15 days old) First-Bad-Commit: http://git.kernel.org/git/linus/ac1aa47b131416a6ff37eb1005a0a1d2541aad6c Handled-By : Francois Romieu rom...@fr.zoreil.com Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=15466 Subject : 2.6.33 dies on modprobe Submitter : M G Berberich berbe...@fmi.uni-passau.de Date: 2010-02-28 22:12 (22 days old) Message-ID : 20100228221257.ga8...@invalid References : http://marc.info/?l=linux-kernelm=126739570819208w=2 Handled-By : Américo Wang xiyou.wangc...@gmail.com Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=15465 Subject : 2.6.33 problems Submitter : wer...@guyane.dyn-o-saur.com Date: 2010-02-27 17:09 (23 days old) Message-ID : 1267290551.13...@guyane.dyn-o-saur.com References : http://marc.info/?l=linux-kernelm=126729183719672w=2 Handled-By : Tejun Heo t...@kernel.org Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=15454 Subject : r8169 exits with error -22 since 2.6.33 Submitter : Conrad Kostecki conik...@gmx.de Date: 2010-03-05 22:32 (17 days old) Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=15439 Subject : Laptop does consume more power when booted cold -- Thinkpad X200s Submitter :
2.6.34-rc2: Reported regressions from 2.6.33
[NOTES: * In this cycle the regressions reported by e-mail will only be put into the Bugzilla 1 week after they have been submitted, if not fixed in the meantime. The reason is that some regressions are fixed in less than a week time and there's no point listing them. [We also hope that people will try to fix bugs faster to avoid being listed. ;-)] If that works, we'll adopt it as a general rule. * All of the regressions reported by e-mail that are listed below have been put into the Bugzilla by Maciej, because I literally didn't have the time to do that (that's also why the summary reports are delayed). Thanks Maciej!] This message contains a list of some regressions from 2.6.33, 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.33, 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 2010-03-21 15 13 10 Unresolved regressions -- Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=15590 Subject : 2.6.34-rc1: regression: ^Z no longer stops sound Submitter : Pavel Machek pa...@ucw.cz Date: 2010-03-14 7:58 (8 days old) Message-ID : 20100314075831.ga13...@elf.ucw.cz References : http://marc.info/?l=linux-kernelm=126855353122623w=2 Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=15589 Subject : 2.6.34-rc1: Badness at fs/proc/generic.c:316 Submitter : Christian Kujau li...@nerdbynature.de Date: 2010-03-13 23:53 (9 days old) Message-ID : alpine.deb.2.01.1003131544340.5...@bogon.housecafe.de References : http://marc.info/?l=linux-kernelm=126852442903680w=2 Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=15584 Subject : 2.6.34-rc1: lockdep warning on geode subnotebook Submitter : Pavel Machek pa...@ucw.cz Date: 2010-03-13 10:51 (9 days old) Message-ID : 20100313105109.ga9...@elf.ucw.cz References : http://marc.info/?l=linux-kernelm=126847750927601w=2 Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=1 Subject : 2.6.34-rc1: kernel BUG at mm/slab.c:2989! Submitter : Américo Wang xiyou.wangc...@gmail.com Date: 2010-03-10 8:29 (12 days old) Message-ID : 2375c9f91003100029q7d64bbf7xce15eee97f7e2...@mail.gmail.com References : http://marc.info/?l=linux-kernelm=126820979017089w=2 Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=15549 Subject : [2.6.34-rc1][libata] regression? Submitter : Etienne Basset etienne.bas...@numericable.fr Date: 2010-03-09 21:47 (13 days old) Message-ID : 4b96c202.6050...@numericable.fr References : http://marc.info/?l=linux-kernelm=126817180811846w=2 Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=15548 Subject : BUG: key f70f4b50 not in .data Submitter : Sergey Senozhatsky sergey.senozhat...@gmail.com Date: 2010-03-09 10:27 (13 days old) Message-ID : 20100309102754.ga3...@swordfish.minsk.epam.com References : http://marc.info/?l=linux-kernelm=126813046113130w=2 Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=15533 Subject : i915 fails to set mode in 2.6.34-rc1, ok in 2.6.33-rc8 Submitter : Pete Zaitcev zait...@yahoo.com Date: 2010-03-13 20:37 (9 days old) Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=15518 Subject : CONFIG_NO_BOOTMEM=y breaks boot on 32bit Submitter : Daniel Vetter dan...@ffwll.ch Date: 2010-03-11 15:37 (11 days old) Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=15496 Subject : 2.6.34-rc1 crashes early while startup Submitter : Thomas Meyer tho...@m3y3r.de Date: 2010-03-09 19:40 (13 days old) Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=15495 Subject : Flood of SELinux denials on polkitd Submitter : Alex Villacis Lasso avill...@ceibo.fiec.espol.edu.ec Date: 2010-03-09 16:47 (13 days old) Regressions with patches Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=15537 Subject : 2.6.34-rc1 hangs for 30 seconds when trying to access the disk Submitter : Andrew Benton b3n...@gmail.com Date: 2010-03-14 23:26 (8 days old) Handled-By : Jeff Garzik jgar...@pobox.com Patch : http://bugzilla.kernel.org/attachment.cgi?id=25516 Bug-Entry :
[Bug 27221] Big 3D performance regression and broken textures on R200
http://bugs.freedesktop.org/show_bug.cgi?id=27221 --- Comment #5 from Ondrej Zary li...@rainbow-software.org 2010-03-21 14:24:09 PST --- mesa-7.7 (slackware-current) mesa-7.5.1 worked fine -- Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. -- Download Intel#174; Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
Resume problem with radeon+KMS (2.6.34-rc2 and before)
Hi, Some time ago I reported a problem with resuming from suspend to RAM on HP nx6325 with radeon+KMS. The problem was that the first resume always failed if the suspend was started from under X. Moreover, the resume went correctly until the last switch from the framebuffer console (which was now controlled by the radeon driver as well) to X that made the box hang hard. However, if the first resume was started from the (radeon-controlled) framebuffer console, the subsequent resume succeeded and all of the next attempts to suspend/resume succeeded, _regardless_ of the way the suspend was started. At that time Dave thought it might be a problem with the nx6325's graphics adapter that apparently was a crappy one, but today I found that _exactly_ the same behavior was observable on Acer Ferrari One, which was quite different, hardware-wise, from the old HP box. For this reason I think the problem is related to the driver itself rather than to the hardware or firmware. The problem is reproducible on both machines with the latest git kernel and the user space radeon_drv.so from openSUSE 11.2 (it says module version = 6.12.4 in the X log). The kernel and user space are 64-bit on both machines. [For completness, the Acer box suspends and resumes correctly with radeon.modeset=0 and s2ram -f -p -m.] Should I try a newer user space X driver? Or may the problem be related to the 64-bitness somehow? Rafael -- Download Intel#174; Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: Resume problem with radeon+KMS (2.6.34-rc2 and before)
2010/3/22 Rafael J. Wysocki r...@sisk.pl: Hi, Some time ago I reported a problem with resuming from suspend to RAM on HP nx6325 with radeon+KMS. Can you post the X.org log file? if you are really using 6.12.4 and not a backport then the userspace driver has no KMS support and it is trashing the system. Dave. The problem was that the first resume always failed if the suspend was started from under X. Moreover, the resume went correctly until the last switch from the framebuffer console (which was now controlled by the radeon driver as well) to X that made the box hang hard. However, if the first resume was started from the (radeon-controlled) framebuffer console, the subsequent resume succeeded and all of the next attempts to suspend/resume succeeded, _regardless_ of the way the suspend was started. At that time Dave thought it might be a problem with the nx6325's graphics adapter that apparently was a crappy one, but today I found that _exactly_ the same behavior was observable on Acer Ferrari One, which was quite different, hardware-wise, from the old HP box. For this reason I think the problem is related to the driver itself rather than to the hardware or firmware. The problem is reproducible on both machines with the latest git kernel and the user space radeon_drv.so from openSUSE 11.2 (it says module version = 6.12.4 in the X log). The kernel and user space are 64-bit on both machines. [For completness, the Acer box suspends and resumes correctly with radeon.modeset=0 and s2ram -f -p -m.] Should I try a newer user space X driver? Or may the problem be related to the 64-bitness somehow? Rafael -- To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/ -- Download Intel#174; Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
[Bug 27225] Radeon KMS fails on Xpress 200M
http://bugs.freedesktop.org/show_bug.cgi?id=27225 --- Comment #5 from Maarten Fonville maarten.fonvi...@gmail.com 2010-03-21 15:46:57 PST --- I can confirm the patch of Alex does work. So if this patch can gets commited soon into the mainline code it is 'fixed' -- Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. -- Download Intel#174; Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: Resume problem with radeon+KMS (2.6.34-rc2 and before)
On Sunday 21 March 2010, Dave Airlie wrote: 2010/3/22 Rafael J. Wysocki r...@sisk.pl: Hi, Some time ago I reported a problem with resuming from suspend to RAM on HP nx6325 with radeon+KMS. Can you post the X.org log file? if you are really using 6.12.4 and not a backport then the userspace driver has no KMS support and it is trashing the system. Appended below. Rafael X.Org X Server 1.6.5 Release Date: 2009-10-11 X Protocol Version 11, Revision 0 Build Operating System: openSUSE SUSE LINUX Current Operating System: Linux ferrari 2.6.34-rc2-rjw #2 SMP PREEMPT Sun Mar 21 15:27:27 CET 2010 x86_64 Build Date: 02 November 2009 12:04:43PM Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: /var/log/Xorg.0.log, Time: Sun Mar 21 22:32:50 2010 (==) Using config file: /etc/X11/xorg.conf (==) ServerLayout Layout[all] (**) |--Screen Screen[0] (0) (**) | |--Monitor Monitor[0] (**) | |--Device Device[0] (**) |--Input Device Keyboard[0] (**) |--Input Device Mouse[1] (**) Option ZapWarning on (**) Option AllowMouseOpenFail on (**) Option Xinerama off (==) Automatically adding devices (==) Automatically enabling devices (WW) The directory /usr/share/fonts/local does not exist. Entry deleted from font path. (WW) The directory /usr/share/fonts/PEX does not exist. Entry deleted from font path. (WW) The directory /usr/share/fonts/latin2/misc does not exist. Entry deleted from font path. (WW) The directory /usr/share/fonts/latin2/75dpi does not exist. Entry deleted from font path. (WW) The directory /usr/share/fonts/latin2/100dpi does not exist. Entry deleted from font path. (WW) The directory /usr/share/fonts/latin2/Type1 does not exist. Entry deleted from font path. (WW) The directory /usr/share/fonts/latin7/75dpi does not exist. Entry deleted from font path. (WW) The directory /usr/share/fonts/baekmuk does not exist. Entry deleted from font path. (WW) The directory /usr/share/fonts/japanese does not exist. Entry deleted from font path. (WW) The directory /usr/share/fonts/kwintv does not exist. Entry deleted from font path. (WW) The directory /usr/share/fonts/uni does not exist. Entry deleted from font path. (WW) The directory /usr/share/fonts/CID does not exist. Entry deleted from font path. (WW) The directory /usr/share/fonts/ucs/misc does not exist. Entry deleted from font path. (WW) The directory /usr/share/fonts/ucs/75dpi does not exist. Entry deleted from font path. (WW) The directory /usr/share/fonts/ucs/100dpi does not exist. Entry deleted from font path. (WW) The directory /usr/share/fonts/hellas/misc does not exist. Entry deleted from font path. (WW) The directory /usr/share/fonts/hellas/75dpi does not exist. Entry deleted from font path. (WW) The directory /usr/share/fonts/hellas/100dpi does not exist. Entry deleted from font path. (WW) The directory /usr/share/fonts/hellas/Type1 does not exist. Entry deleted from font path. (WW) The directory /usr/share/fonts/misc/sgi does not exist. Entry deleted from font path. (WW) The directory /usr/share/fonts/xtest does not exist. Entry deleted from font path. (WW) The directory /opt/kde3/share/fonts does not exist. Entry deleted from font path. (WW) The directory /usr/share/fonts/TTF/ does not exist. Entry deleted from font path. (WW) The directory /usr/share/fonts/OTF does not exist. Entry deleted from font path. (**) FontPath set to: /usr/share/fonts/misc:unscaled, /usr/share/fonts/75dpi:unscaled, /usr/share/fonts/100dpi:unscaled, /usr/share/fonts/Type1, /usr/share/fonts/URW, /usr/share/fonts/Speedo, /usr/share/fonts/cyrillic, /usr/share/fonts/truetype, /usr/share/fonts/misc:unscaled, /usr/share/fonts/truetype/, /usr/share/fonts/Type1/, /usr/share/fonts/100dpi:unscaled, /usr/share/fonts/75dpi:unscaled (**) Input device list set to /dev/gpmdata,/dev/input/mice (==) ModulePath set to /usr/lib64/xorg/modules/updates,/usr/lib64/xorg/modules (WW) AllowEmptyInput is on, devices using drivers 'kbd', 'mouse' or 'vmmouse' will be disabled. (WW) Disabling Keyboard[0] (WW) Disabling Mouse[1] (II) Loader magic: 0xcc0 (II) Module ABI versions: X.Org ANSI C Emulation: 0.4 X.Org Video Driver: 5.0 X.Org XInput driver : 4.0 X.Org Server Extension : 2.0 (II) Loader running on linux (++) using VT number 7 (--) PCI:*(0:1:5:0) 1002:9612:1025:029e rev 0, Mem @ 0xa000/268435456, 0x9fdf/65536, 0x9fe0/1048576, I/O @ 0x9000/256 (II) Open ACPI successful
Re: Resume problem with radeon+KMS (2.6.34-rc2 and before)
On Mon, Mar 22, 2010 at 9:07 AM, Rafael J. Wysocki r...@sisk.pl wrote: On Sunday 21 March 2010, Dave Airlie wrote: 2010/3/22 Rafael J. Wysocki r...@sisk.pl: Hi, Some time ago I reported a problem with resuming from suspend to RAM on HP nx6325 with radeon+KMS. Can you post the X.org log file? if you are really using 6.12.4 and not a backport then the userspace driver has no KMS support and it is trashing the system. Appended below. So your userspace is incompatible with KMS, so I'd suggest trying to get 6.12.191 or -ati git master, Dave. -- Download Intel#174; Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: Resume problem with radeon+KMS (2.6.34-rc2 and before)
On Monday 22 March 2010, Dave Airlie wrote: On Mon, Mar 22, 2010 at 9:07 AM, Rafael J. Wysocki r...@sisk.pl wrote: On Sunday 21 March 2010, Dave Airlie wrote: 2010/3/22 Rafael J. Wysocki r...@sisk.pl: Hi, Some time ago I reported a problem with resuming from suspend to RAM on HP nx6325 with radeon+KMS. Can you post the X.org log file? if you are really using 6.12.4 and not a backport then the userspace driver has no KMS support and it is trashing the system. Appended below. So your userspace is incompatible with KMS, so I'd suggest trying to get 6.12.191 or -ati git master, Thanks a lot, I will. Rafael -- Download Intel#174; Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: Resume problem with radeon+KMS (2.6.34-rc2 and before)
On Monday 22 March 2010, Rafael J. Wysocki wrote: On Monday 22 March 2010, Dave Airlie wrote: On Mon, Mar 22, 2010 at 9:07 AM, Rafael J. Wysocki r...@sisk.pl wrote: On Sunday 21 March 2010, Dave Airlie wrote: 2010/3/22 Rafael J. Wysocki r...@sisk.pl: Hi, Some time ago I reported a problem with resuming from suspend to RAM on HP nx6325 with radeon+KMS. Can you post the X.org log file? if you are really using 6.12.4 and not a backport then the userspace driver has no KMS support and it is trashing the system. Appended below. So your userspace is incompatible with KMS, so I'd suggest trying to get 6.12.191 or -ati git master, Thanks a lot, I will. Yeah, that actually helped, thanks! Rafael -- Download Intel#174; Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
[Bug 27225] Radeon KMS fails on Xpress 200M
http://bugs.freedesktop.org/show_bug.cgi?id=27225 Alex Deucher ag...@yahoo.com changed: What|Removed |Added Status|NEW |RESOLVED Resolution||FIXED --- Comment #6 from Alex Deucher ag...@yahoo.com 2010-03-21 16:45:03 PST --- corrected patch sent to Dave. -- Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. -- Download Intel#174; Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: Regression in i915 on 2.6.34-rc1
On Wed, 17 Mar 2010 08:26:59 -0700 Bjorn Helgaas bjorn.helg...@hp.com wrote: http://bugzilla.kernel.org/show_bug.cgi?id=15533 Any luck testing the patch from the bugzilla? I'd really like to get this figured out so we can get the fix in the next -rc and move on to the next _CRS issue :-) I was on vacation, sorry. Got to it today. In short, the test patch fails. Please see the dmesg with ACPI debugging in bugzilla as requested. -- Pete -- Download Intel#174; Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Mesa3d-dev] DRI SDK and modularized drivers.
On Fri, Mar 19, 2010 at 06:26:03PM +0100, Nicolai Haehnle wrote: On Thu, Mar 18, 2010 at 5:38 PM, Luc Verhaegen l...@skynet.be wrote: So, identify the volatile interfaces, and the more stable interfaces, and then isolate the volatile ones, and then you come to only one conclusion. Except that the Mesa core - classic driver interface also wants to change from time to time in non-trivial ways, and trying to force a separation there on people who don't want an additional set of compatibility issues to deal with is not exactly a friendly move. You have to see this in the global picture. Sure, now it adds one additional set of compatibility issues, but it allows for the removal or reduction of most of the compatibility issues we are actually hit by today; namely, those between the different driver specific bits. Those driver specific bits are, by their very nature, a lot more volatile. None of this work will stop interface changes, that's the last thing i or anyone else wants. It will however incur a tiny bit more overhead when making interface changes between drivers stacks and the outside. But that in itself is already outdone by the ease of making driver stack internal changes (where more of the pain exists now). The other advantages are all net gains. It may seem e.g. like the DRM interface is the worst because of rather large threads caused by certain kernel developer's problems, but that doesn't mean problems wouldn't be created by splitting other areas. Check the timestamps on my unichrome code: most of that work was done in november. And it's based on ideas that have been brewing since when i still was at suse (as suse, a company trying to sell service around the linux desktop, suffers from the current layout). So it had nothing to do with the nouveau spat at lkml recently. This little shouting match is just another symptom that shows that something is wrong with the current setup. In particular, the Mesa core - classic driver split only makes sense if there are enough people who are actually working on those drivers who would support the split. Otherwise, this is bound to lead straight into hell. In a way, the kernel people got it right: put all the drivers in one repository, and make building the whole package and having parallel put all the drivers in one repository? So, all of: * drm * firmware * libdrm * xorg * mesa/dri * mesa/gallium * libxvmc * libvdpau (add more here) of the same driver stack, in one repository? installations trivial. The (only?) issues with that in X.org are that: 1) there is a cultural aversion due to the bad experience with the horrible pre-modularization setup, and There was an SDK there, i never used it directly, i built my driver against the tree (which was easy too). But I became a _really_ happy camper when everyone shipped the xorg sdk per default, heck, i even have a full debian build system in unichrome, simply because the sdk allows for that. Now, about building the whole package... This is called a tinderbox, this is a part that's easily automated. The real question is: where is the most pain, and how can we reduce it. And the most pain is between the driver specific parts. 2) it wouldn't actually solve the DRM problems, because we want to have the DRM in our codebase, and the kernel people want to have it in theirs. The kernel people can have theirs. What stops anyone from getting the drm code of a released driver stack into the next kernel version? But when anyone decides they need a new driver stack which requires a new drm module, it should be easy to replace the stock kernel module. Luc Verhaegen. -- Download Intel#174; Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Mesa3d-dev] DRI SDK and modularized drivers.
On Fri, Mar 19, 2010 at 12:44:39PM -0500, Bridgman, John wrote: Pulling drm back out of the kernel tree seems like a hard sell, but the ddx/mesa hw driver/libdrm set seemed like it might be a good candidate for grouping. I guess the core question is whether we expect the X-to-ddx and mesa-to-hw-driver interfaces to be more or less volatile than the ddx-to-libdrm and mesa-hw-driver-to-libdrm interfaces over the next couple of years. On the core-to-driver interface side we have the Gallium3D and GL 3/4 work, and on the libdrm interface side we have ongoing improvements in memory management and command submission. Tough call. I guess another option would be a pseudo-modular approach where the code stays in the current trees but we adopt versioning and build/test procedures which treat ddx/mesahw/libdrm as a single code base even if the code is still living in multiple projects. That might be an easy first step, but repartitioning the code does seem like a better long-term approach. If the drm code were omitted from the proposal and we focused only on ddx/libdrm/mesahw would that help ? Well, to continue down the same path: It doesn't really matter how driver developers want to scatter their own different driver bits around today. It should be up to them. It shouldn't matter, but sadly it does (as you're forced to have them into the main trees). If those developers are free to choose how they want to handle this, then it will quickly become clear for some what the best mode of working for them really is, as opposed to being forced to work one way. Then there will be pressure from users, hw and distro vendors, who might like one or another way of working better. And i guess that this is what those reasoning against this are mostly afraid of. Ideas like this can no longer be swept under the carpet with impossible. Luc Verhaegen. -- Download Intel#174; Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Mesa3d-dev] DRI SDK and modularized drivers.
On Fri, Mar 19, 2010 at 11:33:02AM -0700, Ian Romanick wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I've been busy trying to get a release out the door, so I haven't looked at these patches yet. I won't have a chance to look at the patches until at least late next week. I also wasn't at FOSDEM, so I don't have any of the background info. I've grouped the slides and the recordings at the top of my blog entry about this. The patches themselves are actually copies of eachother, with minor differences to adjust for changes of the tree around it (there are 16 or so versions of the sdk done from 7.0 through 7.8). Any actual patch is small, and it is build system only. If these patches try to enforce a stable interface between core Mesa and the classic DRI drivers, we're not interested. At all. This has been discussed and rejected many, many times before. Ah, prepossession. Ask yourself, did the fact that xf86 video drivers were out of tree, ever stop anyone from _really_ bad api breakage stunts? The difference with in-tree and out-of-tree here is that out-of-tree should, theoretically, lead to more prudent interface changes. This without having to enforce anything, it happens naturally. Out of tree drivers never stop interface changes, they just make them a tiny bit more involved, and therefor, hopefully, causes the person making those changes to consider his actions a bit better. But as said in an earlier email, what you incur on overhead here you can easily make up in the driver internal interfaces. And then the other synergies come weighing in. Luc Verhaegen. -- Download Intel#174; Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
