[Bug 48455] New: Enabling R600_STREAMOUT causes graphical corruption
https://bugs.freedesktop.org/show_bug.cgi?id=48455 Bug #: 48455 Summary: Enabling R600_STREAMOUT causes graphical corruption Classification: Unclassified Product: Mesa Version: git Platform: x86-64 (AMD64) OS/Version: Linux (All) Status: NEW Severity: major Priority: medium Component: Drivers/DRI/R600 AssignedTo: dri-devel@lists.freedesktop.org ReportedBy: m...@baloneygeek.com I use Mesa from Git (on an Arch Linux box), and build a new copy weekly. Since the last two weeks, keeping R600_STREAMOUT enabled in my /etc/environment file leads to severe graphical corruption (the screen is completely garbled), making it unusable on my Gnome 3 based system. Both GDM and GNOME-Shell exhibit this corruption, making it impossible to conduct tests on the system. Here are some relevant outputs: /etc/environment: LIBGL_DRIVERS_PATH=/opt/mesa-master/lib/xorg/modules/dri VDPAU_DRIVER=r600 R600_GLSL130=1 #R600_STREAMOUT=1 Keeping the last line enabled causes issues. Also, uname -a: Linux bg14ina-laptop 3.3.1-2-ck #1 SMP PREEMPT Thu Apr 5 18:01:36 EDT 2012 x86_64 Intel(R) Core(TM)2 Duo CPU T6670 @ 2.20GHz GenuineIntel GNU/Linux glxinfo | grep -i opengl: OpenGL vendor string: X.Org OpenGL renderer string: Gallium 0.4 on AMD RV710 OpenGL version string: 2.1 Mesa 8.1-devel (git-c653287) OpenGL shading language version string: 1.30 Relevant line from lspci:01:00.0 VGA compatible controller: Advanced Micro Devices [AMD] nee ATI RV710 [Mobility Radeon HD 4300 Series] The card is a 512 MB ATI Mobility Radeon HD4330, (VID:PID = 1002:9552) Other software versions are: xorg-server 1.12.0.901-1 xf86-video-ati 6.14.4-2 libdrm 2.4.33-1 libtxc_dxtn 1.0.1-2 The flags to configure when building Mesa from git: ./configure --prefix=/opt/mesa-master --with-dri-driverdir=/opt/mesa-master/lib/xorg/modules/dri --with-gallium-drivers=r300,r600,swrast --with-dri-drivers=swrast --enable-texture-float --enable-glx-tls --enable-xcb --enable-shared-dricore --enable-gbm --enable-gallium-gbm --enable-xvmc --enable-vdpau --enable-gallium-g3dvl --enable-osmesa --enable-xorg --enable-shared-glapi --enable-gles1 --enable-gles2 --enable-openvg --enable-gallium-egl If there's anything else I can post, please let me know. -- 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 48417] DisplayPort --> HDMI X server freezes when I power off monitor
https://bugs.freedesktop.org/show_bug.cgi?id=48417 Alex Deucher changed: What|Removed |Added AssignedTo|xorg-driver-...@lists.x.org |dri-devel@lists.freedesktop ||.org QAContact|xorg-t...@lists.x.org | Product|xorg|DRI Component|Driver/Radeon |DRM/Radeon -- 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 48422] Radeon KMS fails on Radeon X850XT (R480) graphics card
https://bugs.freedesktop.org/show_bug.cgi?id=48422 --- Comment #3 from Alex Deucher 2012-04-09 05:41:43 PDT --- Should be fixed with this patch: http://lists.freedesktop.org/archives/dri-devel/2012-April/020963.html -- 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
[PATCH] nouveau: Set special lane map for the right chipset
The refactoring of the nv50 logic, introduced in 8663bc7c, modified the test for the special lane map used on some Apple computers with Nvidia chipsets. The tested MBA3,1 would still boot, but resume from suspend stopped working. This patch restores the old test, which fixes the problem. Signed-off-by: Henrik Rydberg --- drivers/gpu/drm/nouveau/nv50_sor.c |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/gpu/drm/nouveau/nv50_sor.c b/drivers/gpu/drm/nouveau/nv50_sor.c index a7844ab..2746402 100644 --- a/drivers/gpu/drm/nouveau/nv50_sor.c +++ b/drivers/gpu/drm/nouveau/nv50_sor.c @@ -42,7 +42,7 @@ nv50_sor_dp_lane_map(struct drm_device *dev, struct dcb_entry *dcb, u8 lane) struct drm_nouveau_private *dev_priv = dev->dev_private; static const u8 nvaf[] = { 24, 16, 8, 0 }; /* thanks, apple.. */ static const u8 nv50[] = { 16, 8, 0, 24 }; - if (dev_priv->card_type == 0xaf) + if (dev_priv->chipset == 0xaf) return nvaf[lane]; return nv50[lane]; } -- 1.7.9.5 ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
Re: i915_driver_irq_handler: irq 42: nobody cared
On Fri, 30 Mar 2012 11:45:43 +0100 Chris Wilson wrote: > On Fri, 30 Mar 2012 11:59:28 +0200, Jiri Slaby wrote: > > I don't know what to dump more, because iir is obviously zero too. What > > other sources of interrupts are on the (G33) chip? > > IIR is the master interrupt, with chained secondary interrupt statuses. > If IIR is 0, the interrupt wasn't raised by the GPU. I've actually seen cases where one of the PIPE*STAT regs is stuck, and even if IIR is 0 we still get interrupts... Jiri can you verify the PIPE*STAT regs have bits set, maybe one or more we don't check for? -- Jesse Barnes, Intel Open Source Technology Center signature.asc Description: PGP signature ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
Re: i915_driver_irq_handler: irq 42: nobody cared [generic IRQ handling broken?]
On Sat, 7 Apr 2012 00:40:28 +0200 (CEST) Thomas Gleixner wrote: > You know what? suspend calls free_irq() via i915_drm_freeze() -> > drm_irq_uninstall() and the resume code calls request_irq() again. > free_irq() removes the action and request_irq installs it fresh. Yeah this is a known issue with the DRM code, I thought Dave had a fix queued a long time ago though... Dave? -- Jesse Barnes, Intel Open Source Technology Center signature.asc Description: PGP signature ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 48472] New: GPU Lockup while running demo in wine
https://bugs.freedesktop.org/show_bug.cgi?id=48472 Bug #: 48472 Summary: GPU Lockup while running demo in wine Classification: Unclassified Product: Mesa Version: git Platform: x86-64 (AMD64) OS/Version: Linux (All) Status: NEW Severity: major Priority: medium Component: Drivers/Gallium/r600 AssignedTo: dri-devel@lists.freedesktop.org ReportedBy: nathanhirscha...@verfriemelt.org While running Razor 1911 - Scene is dead (http://www.chiptune.com/razor/rzr-the_scene_is_dead.zip) in wine I get a GPU Lockup: [ 690.049988] radeon :01:00.0: GPU lockup CP stall for more than 10233msec [ 690.049993] GPU lockup (waiting for 0x2749 last fence id 0x2746) [ 690.051188] radeon :01:00.0: GPU softreset [ 690.051191] radeon :01:00.0: R_008010_GRBM_STATUS=0xE5700030 [ 690.051193] radeon :01:00.0: R_008014_GRBM_STATUS2=0x00110103 [ 690.051195] radeon :01:00.0: R_000E50_SRBM_STATUS=0x20C0 [ 690.051202] radeon :01:00.0: R_008020_GRBM_SOFT_RESET=0x7FEE [ 690.066201] radeon :01:00.0: R_008020_GRBM_SOFT_RESET=0x0001 [ 690.082204] radeon :01:00.0: R_008010_GRBM_STATUS=0xA0003030 [ 690.082206] radeon :01:00.0: R_008014_GRBM_STATUS2=0x0003 [ 690.082208] radeon :01:00.0: R_000E50_SRBM_STATUS=0x200080C0 [ 690.083209] radeon :01:00.0: GPU reset succeed [ 690.103443] [drm] PCIE GART of 512M enabled (table at 0x0004). [ 690.103467] radeon :01:00.0: WB enabled [ 690.134854] [drm] ring test succeeded in 1 usecs [ 690.134861] [drm] ib test succeeded in 1 usecs I'm using mesa-git (c653287) with Linux 3.2.13 (Arch Linux) and Xorg 1.12.0.901 on a Thinkpad R500 (which has the following VGA Controller: 01:00.0 VGA compatible controller: Advanced Micro Devices [AMD] nee ATI RV620 [Mobility Radeon HD 3400 Series] (Mobility Radeon HD 3450) Attached the a logfile with WINEDEBUG=+wgl,+opengl. Seems like the lockup occurs while the following message appears (Line 1232): trace:opengl:wine_glDrawArrays (7, 0, 4) I hope I attached all important files/infos - If I forgot something, let me know. -- 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 48472] GPU Lockup while running demo in wine
https://bugs.freedesktop.org/show_bug.cgi?id=48472 --- Comment #1 from nathanhi 2012-04-09 10:19:23 PDT --- Here is the wine-logfile: http://deepserve.info/blar/rzr-the_scene_is_dead.2.log Seems that 5MB are way too big for Bugzilla to handle. Forgot to mention: This demo definitely runs in WINE, so this may not be a wine bug! -- 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
Re: i915_driver_irq_handler: irq 42: nobody cared [generic IRQ handling broken?]
>> You know what? suspend calls free_irq() via i915_drm_freeze() -> >> drm_irq_uninstall() and the resume code calls request_irq() again. >> free_irq() removes the action and request_irq installs it fresh. > > Yeah this is a known issue with the DRM code, I thought Dave had a > fix queued a long time ago though... Dave? /me doesn't remember seeing one but maybe this one? http://lists.freedesktop.org/archives/dri-devel/2011-August/013407.html probably fell down a hole. Dave. ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 43078] New: Radeon power management issue with KMS
https://bugzilla.kernel.org/show_bug.cgi?id=43078 Summary: Radeon power management issue with KMS Product: Drivers Version: 2.5 Kernel Version: 3.3.1 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: k.mor...@gmail.com Regression: Yes I'm using a self compiled vanilla kernel in LMDE distro. When I updated my kernel from 3.2.13 to 3.3.1 following error appeared: [6.258971] NMI: PCI system error (SERR) for reason a1 on CPU 0. [6.258971] Dazed and confused, but trying to continue In the previous version of kernel I would not see such an error until activating the power management via KMS. In this version of kernel error appears without activation of power management. So I think power management is activating automatically in this version of kernel. -- # dmesg | egrep "drm|radeon" [5.767423] [drm] Initialized drm 1.1.0 20060810 [6.255434] [drm] radeon kernel modesetting enabled. [6.255722] [drm] initializing kernel modesetting (RV515 0x1002:0x7145 0x1028:0x2003). [6.255742] [drm] register mmio base: 0xEFDF [6.255744] [drm] register mmio size: 65536 [6.255900] [drm] Generation 2 PCI interface, using max accessible memory [6.255905] radeon :01:00.0: VRAM: 256M 0x - 0x0FFF (128M used) [6.255909] radeon :01:00.0: GTT: 512M 0x1000 - 0x2FFF [6.255922] [drm] Supports vblank timestamp caching Rev 1 (10.10.2010). [6.255924] [drm] Driver supports precise vblank timestamp query. [6.255964] radeon :01:00.0: irq 44 for MSI/MSI-X [6.255974] radeon :01:00.0: radeon: using MSI. [6.255994] [drm] radeon: irq initialized. [6.257873] [drm] Detected VRAM RAM=256M, BAR=256M [6.257876] [drm] RAM width 64bits DDR [6.258024] [drm] radeon: 128M of VRAM memory ready [6.258026] [drm] radeon: 512M of GTT memory ready. [6.258049] [drm] GART: num cpu pages 131072, num gpu pages 131072 [6.258503] [drm] radeon: ib pool ready. [6.259579] [drm] radeon: 1 quad pipes, 1 z pipes initialized. [6.260640] [drm] PCIE GART of 512M enabled (table at 0x0004). [6.260658] radeon :01:00.0: WB enabled [6.260661] [drm] fence driver on ring 0 use gpu addr 0x1000 and cpu addr 0xff964000 [6.260712] [drm] Loading R500 Microcode [6.441299] [drm] radeon: ring at 0x10001000 [6.441335] [drm] ring test succeeded in 10 usecs [6.441477] [drm] ib test succeeded in 0 usecs [6.441717] [drm] Radeon Display Connectors [6.441719] [drm] Connector 0: [6.441721] [drm] VGA [6.441723] [drm] DDC: 0x7e40 0x7e40 0x7e44 0x7e44 0x7e48 0x7e48 0x7e4c 0x7e4c [6.441725] [drm] Encoders: [6.441727] [drm] CRT1: INTERNAL_KLDSCP_DAC1 [6.441728] [drm] Connector 1: [6.441730] [drm] LVDS [6.441732] [drm] DDC: 0x7e30 0x7e30 0x7e34 0x7e34 0x7e38 0x7e38 0x7e3c 0x7e3c [6.441734] [drm] Encoders: [6.441735] [drm] LCD1: INTERNAL_LVTM1 [6.441737] [drm] Connector 2: [6.441738] [drm] S-video [6.441740] [drm] Encoders: [6.441741] [drm] TV1: INTERNAL_KLDSCP_DAC2 [6.441760] [drm] radeon: power management initialized [6.876927] [drm] fb mappable at 0xD00C [6.876930] [drm] vram apper at 0xD000 [6.876931] [drm] size 4096000 [6.876933] [drm] fb depth is 24 [6.876934] [drm]pitch is 5120 [6.877089] fbcon: radeondrmfb (fb0) is primary device [7.240397] fb0: radeondrmfb frame buffer device [7.240399] drm: registered panic notifier [7.240404] [drm] Initialized radeon 2.13.0 20080528 for :01:00.0 on minor 0 -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are watching the assignee of the bug. ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 48472] GPU Lockup while running demo (rzr - the scene is dead) in wine
https://bugs.freedesktop.org/show_bug.cgi?id=48472 nathanhi changed: What|Removed |Added Summary|GPU Lockup while running|GPU Lockup while running |demo in wine|demo (rzr - the scene is ||dead) in wine -- 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 48472] GPU Lockup while running demo (rzr - the scene is dead) in wine
https://bugs.freedesktop.org/show_bug.cgi?id=48472 --- Comment #2 from Vadim 2012-04-09 12:59:12 PDT --- Created attachment 59693 --> https://bugs.freedesktop.org/attachment.cgi?id=59693 [PATCH] r600g: check gpr count limit The problem is that some shader requires too much registers. I suspect it's caused by the loop unrolling. TGSI source for that shader uses 161 temps. This patch doesn't solve the real problem, but it will prevent the lockups with r600g and allow to detect the problem by printing the error message. Also it may allow the app to run almost as expected (maybe with minor rendering problems). -- 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
[PATCH 02/26] radeon_cp: Remove unneeded tests for NULL before calling release_firmware()
release_firmware() does its own tests for NULL pointers so there's no need to explicitly test before calling it. Signed-off-by: Jesper Juhl --- drivers/gpu/drm/radeon/radeon_cp.c | 12 1 file changed, 4 insertions(+), 8 deletions(-) diff --git a/drivers/gpu/drm/radeon/radeon_cp.c b/drivers/gpu/drm/radeon/radeon_cp.c index 0ebb7d4..ef67e18 100644 --- a/drivers/gpu/drm/radeon/radeon_cp.c +++ b/drivers/gpu/drm/radeon/radeon_cp.c @@ -1827,14 +1827,10 @@ void radeon_do_release(struct drm_device * dev) r600_do_cleanup_cp(dev); else radeon_do_cleanup_cp(dev); - if (dev_priv->me_fw) { - release_firmware(dev_priv->me_fw); - dev_priv->me_fw = NULL; - } - if (dev_priv->pfp_fw) { - release_firmware(dev_priv->pfp_fw); - dev_priv->pfp_fw = NULL; - } + release_firmware(dev_priv->me_fw); + dev_priv->me_fw = NULL; + release_firmware(dev_priv->pfp_fw); + dev_priv->pfp_fw = NULL; } } -- 1.7.10 -- Jesper Juhlhttp://www.chaosbits.net/ Don't top-post http://www.catb.org/jargon/html/T/top-post.html Plain text mails only, please. ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 48472] GPU Lockup while running demo (rzr - the scene is dead) in wine
https://bugs.freedesktop.org/show_bug.cgi?id=48472 --- Comment #3 from nathanhi 2012-04-09 14:03:47 PDT --- Comment on attachment 59693 --> https://bugs.freedesktop.org/attachment.cgi?id=59693 [PATCH] r600g: check gpr count limit Review of attachment 59693: --> (https://bugs.freedesktop.org/page.cgi?id=splinter.html&bug=48472&attachment=59693) - Works like a charm, thanks! Doesn't seem like there are any rendition errors at all! -- 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 48472] GPU Lockup while running demo (rzr - the scene is dead) in wine
https://bugs.freedesktop.org/show_bug.cgi?id=48472 nathanhi changed: What|Removed |Added Status|NEW |RESOLVED Resolution||WORKSFORME --- Comment #4 from nathanhi 2012-04-09 14:04:50 PDT --- Thanks! -- 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 48472] GPU Lockup while running demo (rzr - the scene is dead) in wine
https://bugs.freedesktop.org/show_bug.cgi?id=48472 nathanhi changed: What|Removed |Added Resolution|WORKSFORME |FIXED --- Comment #5 from nathanhi 2012-04-09 14:05:04 PDT --- - -- 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 48424] Fix warnings/errors reported by clang's scan-build tool
https://bugs.freedesktop.org/show_bug.cgi?id=48424 --- Comment #2 from Chad Versace 2012-04-09 14:30:44 UTC --- Thanks for doing this. Here's my review of mesa/main/extensions.c. mesa/main/extensions.c:730: Thanks. I just submitted a patch for this memory leak. You're CC'd. mesa/main/extensions.c:866: false positive -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are on the CC list for the bug. ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 48417] DisplayPort --> HDMI X server freezes when I power off monitor
https://bugs.freedesktop.org/show_bug.cgi?id=48417 --- Comment #2 from Doug 2012-04-09 16:42:50 PDT --- Created attachment 59702 --> https://bugs.freedesktop.org/attachment.cgi?id=59702 truncated dmesg output from bug reproduced bug for new output -- 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 48417] DisplayPort --> HDMI X server freezes when I power off monitor
https://bugs.freedesktop.org/show_bug.cgi?id=48417 --- Comment #3 from Doug 2012-04-09 17:18:30 UTC --- Bug consistently occurs from pressing power button on ASUS monitor. However, less severe than first thought because GNOME 3 screen/power management tools work ok and put monitor into powersaving mode/off eventually without pressing button. Monitor not completely shut off that way; power button shows standby. Wakes without problem from GNOME 3-initiated powersave. -- 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 26891] Radeon KMS on Macs with EFI boot
https://bugs.freedesktop.org/show_bug.cgi?id=26891 --- Comment #18 from James Tyrrell 2012-04-09 20:15:22 PDT --- What would it take to get this patch into mainline? Like I said before I have a MacBook Pro 8,3 and the patch works for me, allowing me to boot via EFI and use the Radeon graphics card to power my Apple Thunderbolt Display. This is something that was only possible when booting via BIOS. -- 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 48455] New: Enabling R600_STREAMOUT causes graphical corruption
https://bugs.freedesktop.org/show_bug.cgi?id=48455 Bug #: 48455 Summary: Enabling R600_STREAMOUT causes graphical corruption Classification: Unclassified Product: Mesa Version: git Platform: x86-64 (AMD64) OS/Version: Linux (All) Status: NEW Severity: major Priority: medium Component: Drivers/DRI/R600 AssignedTo: dri-devel at lists.freedesktop.org ReportedBy: me at BaloneyGeek.com I use Mesa from Git (on an Arch Linux box), and build a new copy weekly. Since the last two weeks, keeping R600_STREAMOUT enabled in my /etc/environment file leads to severe graphical corruption (the screen is completely garbled), making it unusable on my Gnome 3 based system. Both GDM and GNOME-Shell exhibit this corruption, making it impossible to conduct tests on the system. Here are some relevant outputs: /etc/environment: LIBGL_DRIVERS_PATH=/opt/mesa-master/lib/xorg/modules/dri VDPAU_DRIVER=r600 R600_GLSL130=1 #R600_STREAMOUT=1 Keeping the last line enabled causes issues. Also, uname -a: Linux bg14ina-laptop 3.3.1-2-ck #1 SMP PREEMPT Thu Apr 5 18:01:36 EDT 2012 x86_64 Intel(R) Core(TM)2 Duo CPU T6670 @ 2.20GHz GenuineIntel GNU/Linux glxinfo | grep -i opengl: OpenGL vendor string: X.Org OpenGL renderer string: Gallium 0.4 on AMD RV710 OpenGL version string: 2.1 Mesa 8.1-devel (git-c653287) OpenGL shading language version string: 1.30 Relevant line from lspci:01:00.0 VGA compatible controller: Advanced Micro Devices [AMD] nee ATI RV710 [Mobility Radeon HD 4300 Series] The card is a 512 MB ATI Mobility Radeon HD4330, (VID:PID = 1002:9552) Other software versions are: xorg-server 1.12.0.901-1 xf86-video-ati 6.14.4-2 libdrm 2.4.33-1 libtxc_dxtn 1.0.1-2 The flags to configure when building Mesa from git: ./configure --prefix=/opt/mesa-master --with-dri-driverdir=/opt/mesa-master/lib/xorg/modules/dri --with-gallium-drivers=r300,r600,swrast --with-dri-drivers=swrast --enable-texture-float --enable-glx-tls --enable-xcb --enable-shared-dricore --enable-gbm --enable-gallium-gbm --enable-xvmc --enable-vdpau --enable-gallium-g3dvl --enable-osmesa --enable-xorg --enable-shared-glapi --enable-gles1 --enable-gles2 --enable-openvg --enable-gallium-egl If there's anything else I can post, please let me know. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug.
[Bug 48417] DisplayPort --> HDMI X server freezes when I power off monitor
https://bugs.freedesktop.org/show_bug.cgi?id=48417 Alex Deucher changed: What|Removed |Added AssignedTo|xorg-driver-ati at lists.x.org |dri-devel at lists.freedesktop ||.org QAContact|xorg-team at lists.x.org | Product|xorg|DRI Component|Driver/Radeon |DRM/Radeon -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug.
[Bug 48422] Radeon KMS fails on Radeon X850XT (R480) graphics card
https://bugs.freedesktop.org/show_bug.cgi?id=48422 --- Comment #3 from Alex Deucher 2012-04-09 05:41:43 PDT --- Should be fixed with this patch: http://lists.freedesktop.org/archives/dri-devel/2012-April/020963.html -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug.
[PATCH] nouveau: Set special lane map for the right chipset
The refactoring of the nv50 logic, introduced in 8663bc7c, modified the test for the special lane map used on some Apple computers with Nvidia chipsets. The tested MBA3,1 would still boot, but resume from suspend stopped working. This patch restores the old test, which fixes the problem. Signed-off-by: Henrik Rydberg --- drivers/gpu/drm/nouveau/nv50_sor.c |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/gpu/drm/nouveau/nv50_sor.c b/drivers/gpu/drm/nouveau/nv50_sor.c index a7844ab..2746402 100644 --- a/drivers/gpu/drm/nouveau/nv50_sor.c +++ b/drivers/gpu/drm/nouveau/nv50_sor.c @@ -42,7 +42,7 @@ nv50_sor_dp_lane_map(struct drm_device *dev, struct dcb_entry *dcb, u8 lane) struct drm_nouveau_private *dev_priv = dev->dev_private; static const u8 nvaf[] = { 24, 16, 8, 0 }; /* thanks, apple.. */ static const u8 nv50[] = { 16, 8, 0, 24 }; - if (dev_priv->card_type == 0xaf) + if (dev_priv->chipset == 0xaf) return nvaf[lane]; return nv50[lane]; } -- 1.7.9.5
i915_driver_irq_handler: irq 42: nobody cared
On Fri, 30 Mar 2012 11:45:43 +0100 Chris Wilson wrote: > On Fri, 30 Mar 2012 11:59:28 +0200, Jiri Slaby wrote: > > I don't know what to dump more, because iir is obviously zero too. What > > other sources of interrupts are on the (G33) chip? > > IIR is the master interrupt, with chained secondary interrupt statuses. > If IIR is 0, the interrupt wasn't raised by the GPU. I've actually seen cases where one of the PIPE*STAT regs is stuck, and even if IIR is 0 we still get interrupts... Jiri can you verify the PIPE*STAT regs have bits set, maybe one or more we don't check for? -- Jesse Barnes, Intel Open Source Technology Center -- next part -- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 836 bytes Desc: not available URL: <http://lists.freedesktop.org/archives/dri-devel/attachments/20120409/f50f7a99/attachment.pgp>
i915_driver_irq_handler: irq 42: nobody cared [generic IRQ handling broken?]
On Sat, 7 Apr 2012 00:40:28 +0200 (CEST) Thomas Gleixner wrote: > You know what? suspend calls free_irq() via i915_drm_freeze() -> > drm_irq_uninstall() and the resume code calls request_irq() again. > free_irq() removes the action and request_irq installs it fresh. Yeah this is a known issue with the DRM code, I thought Dave had a fix queued a long time ago though... Dave? -- Jesse Barnes, Intel Open Source Technology Center -- next part -- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 836 bytes Desc: not available URL: <http://lists.freedesktop.org/archives/dri-devel/attachments/20120409/f2bc660f/attachment.pgp>
[Bug 48472] New: GPU Lockup while running demo in wine
https://bugs.freedesktop.org/show_bug.cgi?id=48472 Bug #: 48472 Summary: GPU Lockup while running demo in wine Classification: Unclassified Product: Mesa Version: git Platform: x86-64 (AMD64) OS/Version: Linux (All) Status: NEW Severity: major Priority: medium Component: Drivers/Gallium/r600 AssignedTo: dri-devel at lists.freedesktop.org ReportedBy: nathanhirschauer at verfriemelt.org While running Razor 1911 - Scene is dead (http://www.chiptune.com/razor/rzr-the_scene_is_dead.zip) in wine I get a GPU Lockup: [ 690.049988] radeon :01:00.0: GPU lockup CP stall for more than 10233msec [ 690.049993] GPU lockup (waiting for 0x2749 last fence id 0x2746) [ 690.051188] radeon :01:00.0: GPU softreset [ 690.051191] radeon :01:00.0: R_008010_GRBM_STATUS=0xE5700030 [ 690.051193] radeon :01:00.0: R_008014_GRBM_STATUS2=0x00110103 [ 690.051195] radeon :01:00.0: R_000E50_SRBM_STATUS=0x20C0 [ 690.051202] radeon :01:00.0: R_008020_GRBM_SOFT_RESET=0x7FEE [ 690.066201] radeon :01:00.0: R_008020_GRBM_SOFT_RESET=0x0001 [ 690.082204] radeon :01:00.0: R_008010_GRBM_STATUS=0xA0003030 [ 690.082206] radeon :01:00.0: R_008014_GRBM_STATUS2=0x0003 [ 690.082208] radeon :01:00.0: R_000E50_SRBM_STATUS=0x200080C0 [ 690.083209] radeon :01:00.0: GPU reset succeed [ 690.103443] [drm] PCIE GART of 512M enabled (table at 0x0004). [ 690.103467] radeon :01:00.0: WB enabled [ 690.134854] [drm] ring test succeeded in 1 usecs [ 690.134861] [drm] ib test succeeded in 1 usecs I'm using mesa-git (c653287) with Linux 3.2.13 (Arch Linux) and Xorg 1.12.0.901 on a Thinkpad R500 (which has the following VGA Controller: 01:00.0 VGA compatible controller: Advanced Micro Devices [AMD] nee ATI RV620 [Mobility Radeon HD 3400 Series] (Mobility Radeon HD 3450) Attached the a logfile with WINEDEBUG=+wgl,+opengl. Seems like the lockup occurs while the following message appears (Line 1232): trace:opengl:wine_glDrawArrays (7, 0, 4) I hope I attached all important files/infos - If I forgot something, let me know. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug.
[Bug 48472] GPU Lockup while running demo in wine
https://bugs.freedesktop.org/show_bug.cgi?id=48472 --- Comment #1 from nathanhi 2012-04-09 10:19:23 PDT --- Here is the wine-logfile: http://deepserve.info/blar/rzr-the_scene_is_dead.2.log Seems that 5MB are way too big for Bugzilla to handle. Forgot to mention: This demo definitely runs in WINE, so this may not be a wine bug! -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug.
i915_driver_irq_handler: irq 42: nobody cared [generic IRQ handling broken?]
>> You know what? suspend calls free_irq() via i915_drm_freeze() -> >> drm_irq_uninstall() and the resume code calls request_irq() again. >> free_irq() removes the action and request_irq installs it fresh. > > Yeah this is a known issue with the DRM code, I thought Dave had a > fix queued a long time ago though... ?Dave? /me doesn't remember seeing one but maybe this one? http://lists.freedesktop.org/archives/dri-devel/2011-August/013407.html probably fell down a hole. Dave.
[Bug 43078] New: Radeon power management issue with KMS
https://bugzilla.kernel.org/show_bug.cgi?id=43078 Summary: Radeon power management issue with KMS Product: Drivers Version: 2.5 Kernel Version: 3.3.1 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: k.moradi at gmail.com Regression: Yes I'm using a self compiled vanilla kernel in LMDE distro. When I updated my kernel from 3.2.13 to 3.3.1 following error appeared: [6.258971] NMI: PCI system error (SERR) for reason a1 on CPU 0. [6.258971] Dazed and confused, but trying to continue In the previous version of kernel I would not see such an error until activating the power management via KMS. In this version of kernel error appears without activation of power management. So I think power management is activating automatically in this version of kernel. -- # dmesg | egrep "drm|radeon" [5.767423] [drm] Initialized drm 1.1.0 20060810 [6.255434] [drm] radeon kernel modesetting enabled. [6.255722] [drm] initializing kernel modesetting (RV515 0x1002:0x7145 0x1028:0x2003). [6.255742] [drm] register mmio base: 0xEFDF [6.255744] [drm] register mmio size: 65536 [6.255900] [drm] Generation 2 PCI interface, using max accessible memory [6.255905] radeon :01:00.0: VRAM: 256M 0x - 0x0FFF (128M used) [6.255909] radeon :01:00.0: GTT: 512M 0x1000 - 0x2FFF [6.255922] [drm] Supports vblank timestamp caching Rev 1 (10.10.2010). [6.255924] [drm] Driver supports precise vblank timestamp query. [6.255964] radeon :01:00.0: irq 44 for MSI/MSI-X [6.255974] radeon :01:00.0: radeon: using MSI. [6.255994] [drm] radeon: irq initialized. [6.257873] [drm] Detected VRAM RAM=256M, BAR=256M [6.257876] [drm] RAM width 64bits DDR [6.258024] [drm] radeon: 128M of VRAM memory ready [6.258026] [drm] radeon: 512M of GTT memory ready. [6.258049] [drm] GART: num cpu pages 131072, num gpu pages 131072 [6.258503] [drm] radeon: ib pool ready. [6.259579] [drm] radeon: 1 quad pipes, 1 z pipes initialized. [6.260640] [drm] PCIE GART of 512M enabled (table at 0x0004). [6.260658] radeon :01:00.0: WB enabled [6.260661] [drm] fence driver on ring 0 use gpu addr 0x1000 and cpu addr 0xff964000 [6.260712] [drm] Loading R500 Microcode [6.441299] [drm] radeon: ring at 0x10001000 [6.441335] [drm] ring test succeeded in 10 usecs [6.441477] [drm] ib test succeeded in 0 usecs [6.441717] [drm] Radeon Display Connectors [6.441719] [drm] Connector 0: [6.441721] [drm] VGA [6.441723] [drm] DDC: 0x7e40 0x7e40 0x7e44 0x7e44 0x7e48 0x7e48 0x7e4c 0x7e4c [6.441725] [drm] Encoders: [6.441727] [drm] CRT1: INTERNAL_KLDSCP_DAC1 [6.441728] [drm] Connector 1: [6.441730] [drm] LVDS [6.441732] [drm] DDC: 0x7e30 0x7e30 0x7e34 0x7e34 0x7e38 0x7e38 0x7e3c 0x7e3c [6.441734] [drm] Encoders: [6.441735] [drm] LCD1: INTERNAL_LVTM1 [6.441737] [drm] Connector 2: [6.441738] [drm] S-video [6.441740] [drm] Encoders: [6.441741] [drm] TV1: INTERNAL_KLDSCP_DAC2 [6.441760] [drm] radeon: power management initialized [6.876927] [drm] fb mappable at 0xD00C [6.876930] [drm] vram apper at 0xD000 [6.876931] [drm] size 4096000 [6.876933] [drm] fb depth is 24 [6.876934] [drm]pitch is 5120 [6.877089] fbcon: radeondrmfb (fb0) is primary device [7.240397] fb0: radeondrmfb frame buffer device [7.240399] drm: registered panic notifier [7.240404] [drm] Initialized radeon 2.13.0 20080528 for :01:00.0 on minor 0 -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are watching the assignee of the bug.
[Bug 48472] GPU Lockup while running demo (rzr - the scene is dead) in wine
https://bugs.freedesktop.org/show_bug.cgi?id=48472 nathanhi changed: What|Removed |Added Summary|GPU Lockup while running|GPU Lockup while running |demo in wine|demo (rzr - the scene is ||dead) in wine -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug.
[Bug 48472] GPU Lockup while running demo (rzr - the scene is dead) in wine
https://bugs.freedesktop.org/show_bug.cgi?id=48472 --- Comment #2 from Vadim 2012-04-09 12:59:12 PDT --- Created attachment 59693 --> https://bugs.freedesktop.org/attachment.cgi?id=59693 [PATCH] r600g: check gpr count limit The problem is that some shader requires too much registers. I suspect it's caused by the loop unrolling. TGSI source for that shader uses 161 temps. This patch doesn't solve the real problem, but it will prevent the lockups with r600g and allow to detect the problem by printing the error message. Also it may allow the app to run almost as expected (maybe with minor rendering problems). -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug.
[PATCH 02/26] radeon_cp: Remove unneeded tests for NULL before calling release_firmware()
release_firmware() does its own tests for NULL pointers so there's no need to explicitly test before calling it. Signed-off-by: Jesper Juhl --- drivers/gpu/drm/radeon/radeon_cp.c | 12 1 file changed, 4 insertions(+), 8 deletions(-) diff --git a/drivers/gpu/drm/radeon/radeon_cp.c b/drivers/gpu/drm/radeon/radeon_cp.c index 0ebb7d4..ef67e18 100644 --- a/drivers/gpu/drm/radeon/radeon_cp.c +++ b/drivers/gpu/drm/radeon/radeon_cp.c @@ -1827,14 +1827,10 @@ void radeon_do_release(struct drm_device * dev) r600_do_cleanup_cp(dev); else radeon_do_cleanup_cp(dev); - if (dev_priv->me_fw) { - release_firmware(dev_priv->me_fw); - dev_priv->me_fw = NULL; - } - if (dev_priv->pfp_fw) { - release_firmware(dev_priv->pfp_fw); - dev_priv->pfp_fw = NULL; - } + release_firmware(dev_priv->me_fw); + dev_priv->me_fw = NULL; + release_firmware(dev_priv->pfp_fw); + dev_priv->pfp_fw = NULL; } } -- 1.7.10 -- Jesper Juhlhttp://www.chaosbits.net/ Don't top-post http://www.catb.org/jargon/html/T/top-post.html Plain text mails only, please.
[Bug 48472] GPU Lockup while running demo (rzr - the scene is dead) in wine
https://bugs.freedesktop.org/show_bug.cgi?id=48472 --- Comment #3 from nathanhi 2012-04-09 14:03:47 PDT --- Comment on attachment 59693 --> https://bugs.freedesktop.org/attachment.cgi?id=59693 [PATCH] r600g: check gpr count limit Review of attachment 59693: --> (https://bugs.freedesktop.org/page.cgi?id=splinter.html&bug=48472&attachment=59693) - Works like a charm, thanks! Doesn't seem like there are any rendition errors at all! -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug.
[Bug 48472] GPU Lockup while running demo (rzr - the scene is dead) in wine
https://bugs.freedesktop.org/show_bug.cgi?id=48472 nathanhi changed: What|Removed |Added Status|NEW |RESOLVED Resolution||WORKSFORME --- Comment #4 from nathanhi 2012-04-09 14:04:50 PDT --- Thanks! -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug.
[Bug 48472] GPU Lockup while running demo (rzr - the scene is dead) in wine
https://bugs.freedesktop.org/show_bug.cgi?id=48472 nathanhi changed: What|Removed |Added Resolution|WORKSFORME |FIXED --- Comment #5 from nathanhi 2012-04-09 14:05:04 PDT --- - -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug.
[Bug 48424] Fix warnings/errors reported by clang's scan-build tool
https://bugs.freedesktop.org/show_bug.cgi?id=48424 --- Comment #2 from Chad Versace 2012-04-09 14:30:44 UTC --- Thanks for doing this. Here's my review of mesa/main/extensions.c. mesa/main/extensions.c:730: Thanks. I just submitted a patch for this memory leak. You're CC'd. mesa/main/extensions.c:866: false positive -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are on the CC list for the bug.
[Bug 48417] DisplayPort --> HDMI X server freezes when I power off monitor
https://bugs.freedesktop.org/show_bug.cgi?id=48417 --- Comment #2 from Doug 2012-04-09 16:42:50 PDT --- Created attachment 59702 --> https://bugs.freedesktop.org/attachment.cgi?id=59702 truncated dmesg output from bug reproduced bug for new output -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug.
[Bug 48417] DisplayPort --> HDMI X server freezes when I power off monitor
https://bugs.freedesktop.org/show_bug.cgi?id=48417 --- Comment #3 from Doug 2012-04-09 17:18:30 UTC --- Bug consistently occurs from pressing power button on ASUS monitor. However, less severe than first thought because GNOME 3 screen/power management tools work ok and put monitor into powersaving mode/off eventually without pressing button. Monitor not completely shut off that way; power button shows standby. Wakes without problem from GNOME 3-initiated powersave. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug.