dri-devel July 2013

dri-devel@lists.freedesktop.org

142 participants
850 discussions

[Bug 53391] New: nouveau: wrong display output order
by bugzilla-daemon＠bugzilla.kernel.org 08 Dec '21

08 Dec '21

https://bugzilla.kernel.org/show_bug.cgi?id=53391 Summary: nouveau: wrong display output order Product: Drivers Version: 2.5 Kernel Version: 3.8-rc6 Platform: All OS/Version: Linux Tree: Mainline Status: NEW Severity: normal Priority: P1 Component: Video(DRI - non Intel) AssignedTo: drivers_video-dri(a)kernel-bugs.osdl.org ReportedBy: stijn+bugs(a)linux-ipv6.be Regression: No My graphics card is a Gainward GTX480 (http://www.gainward.com/main/vgapro.php?id=238). It has 2 DVI outputs, and 1 mini HDMI output. The DVI outputs are numbered on the card, with DVI 1 being the closest to the PCIe slot, then DVI 2, and finally the mini HDMI. My primary (left) monitor, is connected to DVI 1, my secondary (right) monitor to DVI 2. When I boot the computer, the BIOS initializes and uses the monitor on DVI 1. Grub is displayed on the primary monitor, and the kernel initially outputs to the primary monitor as well. However, as soon as the nouveau module is loaded, the primary monitor goes to standby and the kernel now uses the secondary monitor (on DVI 2) as primary. When X starts (no Xorg.conf file), it is also displayed on the secondary monitor. When using either efifb, vesafb or uvesafb, the monitor on DVI 1 is always the primary monitor. X with nvidia.ko also uses DVI 1 as the primary display. Finally, when booting Windows, the startup screen is also displayed on the monitor connected to DVI 1. Here comes the weird part: when I am in X, and run xrandr, it does show 3 connected devices: DVI-I-1, DVI-I-2, and HDMI-1, with DVI-I-2 being the only active one. So it seems that in X, the output order is correct, but with nouveaufb the DVI connectors are swapped. I will attach the output of dmesg here. If anything else is needed, please let me know and I'll be happy to add it. -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching the assignee of the bug.

1 13

[Bug 51381] New: [drm:atom_op_jump] *ERROR* atombios stuck in loop for more than 5secs aborting, when disabled via vgaswitcheroo
by bugzilla-daemon＠bugzilla.kernel.org 11 May '21

11 May '21

https://bugzilla.kernel.org/show_bug.cgi?id=51381 Summary: [drm:atom_op_jump] *ERROR* atombios stuck in loop for more than 5secs aborting, when disabled via vgaswitcheroo Product: Drivers Version: 2.5 Kernel Version: Linux version 3.6.9-1-ARCH (tobias@T-POWA-LX) (gcc version 4.7.2 (GCC) ) #1 SMP PREEMPT Tue Dec 4 08:04:10 CET 2012 Platform: All OS/Version: Linux Tree: Mainline Status: NEW Severity: normal Priority: P1 Component: Video(DRI - non Intel) AssignedTo: drivers_video-dri(a)kernel-bugs.osdl.org ReportedBy: a(a)anrd.net Regression: Yes Created an attachment (id=88591) --> (https://bugzilla.kernel.org/attachment.cgi?id=88591) journald log After updating from 3.6.6 to 3.6.9 my laptop with Intel graphics and ATI HD 5650 will not resume from suspend. I use vgaswitcheroo to disable the ATI card at boot. On resume the computer almost hangs (I can press power button and wait 5 minutes for a proper shutdown, but no other interaction is possible). It logs a lot of messages saying: [drm:atom_op_jump] *ERROR* atombios stuck in loop for more than 5secs aborting [drm:atom_execute_table_locked] *ERROR* atombios stuck executing D098 (len 72, WS 0, PS 0) @ 0xD0C7 Steps to reproduce: echo "OFF" > /sys/kernel/debug/vgaswitcheroo/switch [suspend and resume] Actual results: Almost freeze. Expected results: Resume and work as normal. Log is attached, but if you need anything else just ask. -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching the assignee of the bug.

1 62

[Bug 58981] New: Bisected regression; boot failure with Radeon 9250 PCI 256MB + KMS
by bugzilla-daemon＠bugzilla.kernel.org 28 Jan '20

28 Jan '20

https://bugzilla.kernel.org/show_bug.cgi?id=58981 Summary: Bisected regression; boot failure with Radeon 9250 PCI 256MB + KMS Product: Drivers Version: 2.5 Kernel Version: 2.6.35,3.2.45,3.10-rc2 Platform: All OS/Version: Linux Tree: Mainline Status: NEW Severity: normal Priority: P1 Component: Video(DRI - non Intel) AssignedTo: drivers_video-dri(a)kernel-bugs.osdl.org ReportedBy: jdietrch(a)fastmail.fm Regression: Yes I have a Radeon 9250 PCI 256MB video card in my machine. I discovered that this machine would not boot with 3.2.45 when KMS was enabled by default in the kernel config. Immediately after the grub menu, the screen would go black and nothing more would happen. Or sometimes columns of character-sized "marks" would appear on the screen. In either case, though, the machine would not boot. So I went back to 2.6.33 and found that booting with KMS did work just fine there. So I used git bisect to find where the problem arose, and that pointed to this commit which was merged for 2.6.35: commit 6b8b1786a8c29ce6e32298b93ac8d4a18a2b11c4 Author: Jerome Glisse <jglisse(a)redhat.com> Date: Wed Apr 7 10:21:31 2010 +0000 drm/radeon/kms: enable use of unmappable VRAM V2 I confirmed this result of git bisect by checking out 2.6.35 final and reverting that one commit, and the resulting kernel booted fine with KMS enabled by default. I also tried 3.10-rc2 and that booted fine when I added radeon.modeset=0 to the kernel commandline. I will attach files with dmesg output and lspci. Please let me know if there is anything else I can do. I'll be happy to test a proposed fix if that would be helpful. Thank you, James Dietrich -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching the assignee of the bug.

1 6

[Bug 32556] New: screen flickers all the time with desktop image appearing only briefly
by bugzilla-daemon＠freedesktop.org 20 Nov '19

20 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=32556 Summary: screen flickers all the time with desktop image appearing only briefly Product: DRI Version: unspecified Platform: Other OS/Version: All Status: NEW Severity: critical Priority: medium Component: DRM/Radeon AssignedTo: dri-devel(a)lists.freedesktop.org ReportedBy: 3ntr0p13(a)gmail.com Created an attachment (id=41344) --> (https://bugs.freedesktop.org/attachment.cgi?id=41344) dmesg Machine is the same as in bug report 28331 although with different software components: Acer Aspire L5100 with an AMD Athlon 64 X2 Dual Core Processor 4000+, this time running a 64 bits debian squeeze. The machine is a small factor desktop machine designed around laptop components, so the graphic card is an integrated radeon x1200. When running a linux vanilla kernel 2.6.37-rc6, the screen flickers all the time making the machine unusable, while with debian kernel 2.6.32-5 such "flick to black" event occur from time to time, making it annoying but usable. While booting with radeon.modeset=0 the problem doesn't exhibits itself The following packages version from debian squeeze are installed: xserver-xorg 1:7.5+8 xserver-xorg-core 2:1.7.7-10 xserver-xorg-video-radeon 1:6.13.1-2+squeeze1 Please find attached Xorg.0.log, dmesg, register dumps for ums and kms for that machine (when booted on 2.6.37-rc6). Regards, Gildas -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.

1 38

[Bug 32422] New: Large images displayed in Firefox appear corrupted
by bugzilla-daemon＠freedesktop.org 20 Nov '19

20 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=32422 Summary: Large images displayed in Firefox appear corrupted Product: DRI Version: unspecified Platform: x86 (IA32) OS/Version: Linux (All) Status: NEW Severity: normal Priority: medium Component: DRM/Radeon AssignedTo: dri-devel(a)lists.freedesktop.org ReportedBy: da_fox(a)mad.scientist.com Created an attachment (id=41150) --> (https://bugs.freedesktop.org/attachment.cgi?id=41150) Picture describing a thousand words. "A picture says more than a thousand words" (aka see attachment) This is what happens when I try to view the XKCD "Online Communities 2" map (http://xkcd.com/802_large/) or other large images in firefox. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.

1 21

[Bug 67359] New: No direct rendering with Radeon HD 7750
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=67359 Priority: medium Bug ID: 67359 Assignee: dri-devel(a)lists.freedesktop.org Summary: No direct rendering with Radeon HD 7750 Severity: normal Classification: Unclassified OS: Linux (All) Reporter: 74.schutt(a)gmail.com Hardware: x86-64 (AMD64) Status: NEW Version: unspecified Component: DRM/Radeon Product: DRI Created attachment 83043 --> https://bugs.freedesktop.org/attachment.cgi?id=83043&action=edit Xorg.0.log for no direct rendering I've got a Radeon HD 7750: 01:00.0 VGA compatible controller: Advanced Micro Devices [AMD] nee ATI Cape Verde PRO [Radeon HD 7750] and I'm not getting direct rendering: # grep rendering /var/log/Xorg.0.log [ 33.034] (WW) RADEON(0): Direct rendering disabled # glxinfo | grep string server glx vendor string: SGI server glx version string: 1.4 client glx vendor string: Mesa Project and SGI client glx version string: 1.4 OpenGL vendor string: VMware, Inc. OpenGL renderer string: Gallium 0.4 on llvmpipe (LLVM 3.1, 256 bits) OpenGL version string: 2.1 Mesa 9.1.4 OpenGL shading language version string: 1.20 # ls -l /dev/dri/* crw-rw----+ 1 root video 226, 0 Jul 26 07:41 /dev/dri/card0 crw-rw---- 1 root video 226, 64 Jul 26 07:41 /dev/dri/controlD64 and my username is in the video group: # grep video /etc/group video:x:27:root,jim I'm running Gentoo with a kernel.org kernel: 3.11.0-rc2-00185-g07bc9dc My system is built on an Asus PC8WS motherboard with UEFI BIOS. It's all new, and I've never had working direct rendering on this system. I build my kernel with the Radeon driver built in, and firmware included: # egrep "RADEON|EXTRA" .config CONFIG_EXTRA_FIRMWARE="radeon/VERDE_ce.bin radeon/VERDE_mc.bin radeon/VERDE_me.bin radeon/VERDE_pfp.bin radeon/VERDE_rlc.bin radeon/VERDE_smc.bin radeon/TAHITI_uvd.bin" CONFIG_EXTRA_FIRMWARE_DIR="/lib/firmware" CONFIG_DRM_RADEON=y # CONFIG_DRM_RADEON_UMS is not set # CONFIG_FB_RADEON is not set AFAIK the firmware is the most recent available: # sha1sum /lib/firmware/radeon/{VERDE,TAHITI_uvd}* 9cda1adf01acdbf7de9171524828603b74edfcd6 /lib/firmware/radeon/VERDE_ce.bin b7993a2036b59a1b5bf6b5433d614f5c97596487 /lib/firmware/radeon/VERDE_mc.bin 29caf82d03f6bc6299777e23c028ec76dad51a71 /lib/firmware/radeon/VERDE_me.bin 3ccb727b909b4e6496cb48fda1e888671bfde19a /lib/firmware/radeon/VERDE_pfp.bin 8ba612da9ffedc0df18ed3593a2e65cb76f058f3 /lib/firmware/radeon/VERDE_rlc.bin 56ac1628276545c4ff1cd682461e4609547d79f4 /lib/firmware/radeon/VERDE_smc.bin 28c406a7dc5d3a223b79e5e76c35d7bb845071e3 /lib/firmware/radeon/TAHITI_uvd.bin Here's the main Gentoo X package versions I'm running: media-libs/mesa-9.1.4 x11-base/xorg-drivers-1.13 x11-base/xorg-server-1.13.4 x11-base/xorg-x11-7.4-r2 I've attached an X server log, and here's everything from dmesg that appears to be related to graphics: [ 0.000000] Command line: BOOT_IMAGE=(hd1,gpt1)/efi/linux/vmlinuz-3.11.0-rc2-00185-g07bc9dc root=LABEL=sys_root ro acpi_enforce_resources=lax radeon.dpm=1 [ 0.000000] Kernel command line: BOOT_IMAGE=(hd1,gpt1)/efi/linux/vmlinuz-3.11.0-rc2-00185-g07bc9dc root=LABEL=sys_root ro acpi_enforce_resources=lax radeon.dpm=1 [ 0.322036] efifb: probing for efifb [ 0.322127] efifb: framebuffer at 0xe0000000, mapped to 0xffffc9000ad00000, using 1984k, total 1984k [ 0.322129] efifb: mode is 800x600x32, linelength=3328, pages=1 [ 0.322131] efifb: scrolling: redraw [ 0.322133] efifb: Truecolor: size=8:8:8:8, shift=24:16:8:0 [ 0.324356] fb0: EFI VGA frame buffer device [ 0.364525] [drm] Initialized drm 1.1.0 20060810 [ 0.365086] [drm] radeon kernel modesetting enabled. [ 0.365636] fb: conflicting fb hw usage radeondrmfb vs EFI VGA - removing generic driver [ 0.366329] [drm] initializing kernel modesetting (VERDE 0x1002:0x683F 0x1787:0x200B). [ 0.366909] [drm] register mmio base: 0xF7E00000 [ 0.367456] [drm] register mmio size: 262144 [ 0.368707] radeon 0000:01:00.0: VRAM: 1024M 0x0000000000000000 - 0x000000003FFFFFFF (1024M used) [ 0.369287] radeon 0000:01:00.0: GTT: 512M 0x0000000040000000 - 0x000000005FFFFFFF [ 0.369865] [drm] Detected VRAM RAM=1024M, BAR=256M [ 0.370434] [drm] RAM width 128bits DDR [ 0.371017] [TTM] Zone kernel: Available graphics memory: 8209962 kiB [ 0.371579] [TTM] Zone dma32: Available graphics memory: 2097152 kiB [ 0.372135] [TTM] Initializing pool allocator [ 0.372687] [TTM] Initializing DMA pool allocator [ 0.373243] [drm] radeon: 1024M of VRAM memory ready [ 0.373782] [drm] radeon: 512M of GTT memory ready. [ 0.374830] [drm] GART: num cpu pages 131072, num gpu pages 131072 [ 0.375584] [drm] probing gen 2 caps for device 8086:151 = 261ad03/e [ 0.376105] [drm] PCIE gen 3 link speeds already enabled [ 0.376635] [drm] Loading VERDE Microcode [ 0.692398] [drm] PCIE GART of 512M enabled (table at 0x0000000000276000). [ 0.693008] radeon 0000:01:00.0: WB enabled [ 0.693520] radeon 0000:01:00.0: fence driver on ring 0 use gpu addr 0x0000000040000c00 and cpu addr 0xffff88040df85c00 [ 0.694569] radeon 0000:01:00.0: fence driver on ring 1 use gpu addr 0x0000000040000c04 and cpu addr 0xffff88040df85c04 [ 0.695675] radeon 0000:01:00.0: fence driver on ring 2 use gpu addr 0x0000000040000c08 and cpu addr 0xffff88040df85c08 [ 0.696817] radeon 0000:01:00.0: fence driver on ring 3 use gpu addr 0x0000000040000c0c and cpu addr 0xffff88040df85c0c [ 0.697977] radeon 0000:01:00.0: fence driver on ring 4 use gpu addr 0x0000000040000c10 and cpu addr 0xffff88040df85c10 [ 0.699201] radeon 0000:01:00.0: fence driver on ring 5 use gpu addr 0x0000000000075a18 and cpu addr 0xffffc9000b035a18 [ 0.700458] [drm] Supports vblank timestamp caching Rev 1 (10.10.2010). [ 0.701095] [drm] Driver supports precise vblank timestamp query. [ 0.701749] radeon 0000:01:00.0: irq 40 for MSI/MSI-X [ 0.701756] radeon 0000:01:00.0: radeon: using MSI. [ 0.702420] [drm] radeon: irq initialized. [ 0.722205] [drm] ring test on 0 succeeded in 2 usecs [ 0.722843] [drm] ring test on 1 succeeded in 1 usecs [ 0.723458] [drm] ring test on 2 succeeded in 1 usecs [ 0.724127] [drm] ring test on 3 succeeded in 4 usecs [ 0.724731] [drm] ring test on 4 succeeded in 4 usecs [ 1.901452] [drm:r600_uvd_init] *ERROR* UVD not responding, trying to reset the VCPU!!! [ 2.922147] [drm:r600_uvd_init] *ERROR* UVD not responding, trying to reset the VCPU!!! [ 3.943124] [drm:r600_uvd_init] *ERROR* UVD not responding, trying to reset the VCPU!!! [ 4.964083] [drm:r600_uvd_init] *ERROR* UVD not responding, trying to reset the VCPU!!! [ 5.984845] [drm:r600_uvd_init] *ERROR* UVD not responding, trying to reset the VCPU!!! [ 7.005588] [drm:r600_uvd_init] *ERROR* UVD not responding, trying to reset the VCPU!!! [ 8.026315] [drm:r600_uvd_init] *ERROR* UVD not responding, trying to reset the VCPU!!! [ 9.047036] [drm:r600_uvd_init] *ERROR* UVD not responding, trying to reset the VCPU!!! [ 10.067738] [drm:r600_uvd_init] *ERROR* UVD not responding, trying to reset the VCPU!!! [ 11.088419] [drm:r600_uvd_init] *ERROR* UVD not responding, trying to reset the VCPU!!! [ 11.109017] [drm:r600_uvd_init] *ERROR* UVD not responding, giving up!!! [ 11.109588] [drm:si_startup] *ERROR* radeon: failed initializing UVD (-1). [ 11.110974] [drm] ib test on ring 0 succeeded in 0 usecs [ 11.111448] [drm] ib test on ring 1 succeeded in 0 usecs [ 11.111895] [drm] ib test on ring 2 succeeded in 0 usecs [ 11.112319] [drm] ib test on ring 3 succeeded in 0 usecs [ 11.112720] [drm] ib test on ring 4 succeeded in 1 usecs [ 11.113577] [drm] Radeon Display Connectors [ 11.113901] [drm] Connector 0: [ 11.114201] [drm] DP-1 [ 11.114476] [drm] HPD4 [ 11.114737] [drm] DDC: 0x6540 0x6540 0x6544 0x6544 0x6548 0x6548 0x654c 0x654c [ 11.115013] [drm] Encoders: [ 11.115276] [drm] DFP1: INTERNAL_UNIPHY2 [ 11.115540] [drm] Connector 1: [ 11.115796] [drm] HDMI-A-1 [ 11.116053] [drm] HPD1 [ 11.116311] [drm] DDC: 0x6570 0x6570 0x6574 0x6574 0x6578 0x6578 0x657c 0x657c [ 11.116601] [drm] Encoders: [ 11.116890] [drm] DFP2: INTERNAL_UNIPHY2 [ 11.117173] [drm] Connector 2: [ 11.117438] [drm] DVI-I-1 [ 11.117706] [drm] HPD2 [ 11.117973] [drm] DDC: 0x6560 0x6560 0x6564 0x6564 0x6568 0x6568 0x656c 0x656c [ 11.118272] [drm] Encoders: [ 11.118573] [drm] DFP3: INTERNAL_UNIPHY [ 11.118882] [drm] CRT1: INTERNAL_KLDSCP_DAC1 [ 11.119229] [drm] Internal thermal controller with fan control [ 11.119604] [drm] probing gen 2 caps for device 8086:151 = 261ad03/e [ 11.119965] == power state 0 == [ 11.120314] ui class: none [ 11.120663] internal class: boot [ 11.121003] caps: [ 11.121326] uvd vclk: 0 dclk: 0 [ 11.121645] power level 0 sclk: 30000 mclk: 14900 vddc: 950 vddci: 900 pcie gen: 3 [ 11.121995] status: c r b [ 11.122353] == power state 1 == [ 11.122710] ui class: performance [ 11.123075] internal class: none [ 11.123435] caps: [ 11.123789] uvd vclk: 0 dclk: 0 [ 11.124147] power level 0 sclk: 30000 mclk: 15000 vddc: 825 vddci: 900 pcie gen: 3 [ 11.124539] power level 1 sclk: 40000 mclk: 112500 vddc: 950 vddci: 950 pcie gen: 3 [ 11.124925] power level 2 sclk: 80000 mclk: 112500 vddc: 1100 vddci: 950 pcie gen: 3 [ 11.125303] status: [ 11.125678] == power state 2 == [ 11.126051] ui class: none [ 11.126427] internal class: uvd [ 11.126811] caps: video [ 11.127179] uvd vclk: 72000 dclk: 56000 [ 11.127544] power level 0 sclk: 40000 mclk: 112500 vddc: 950 vddci: 950 pcie gen: 3 [ 11.127933] power level 1 sclk: 40000 mclk: 112500 vddc: 950 vddci: 950 pcie gen: 3 [ 11.128315] power level 2 sclk: 80000 mclk: 112500 vddc: 1100 vddci: 950 pcie gen: 3 [ 11.128704] status: [ 11.129092] == power state 3 == [ 11.129470] ui class: none [ 11.129839] internal class: ulv [ 11.130208] caps: [ 11.130574] uvd vclk: 0 dclk: 0 [ 11.130934] power level 0 sclk: 30000 mclk: 15000 vddc: 800 vddci: 900 pcie gen: 3 [ 11.131314] power level 1 sclk: 30000 mclk: 15000 vddc: 800 vddci: 900 pcie gen: 3 [ 11.131680] power level 2 sclk: 30000 mclk: 15000 vddc: 800 vddci: 900 pcie gen: 3 [ 11.132040] status: [ 11.136916] switching from power state: [ 11.137280] ui class: none [ 11.137644] internal class: boot [ 11.137998] caps: [ 11.138332] uvd vclk: 0 dclk: 0 [ 11.138671] power level 0 sclk: 30000 mclk: 14900 vddc: 950 vddci: 900 pcie gen: 3 [ 11.139037] status: c b [ 11.139402] switching to power state: [ 11.139768] ui class: performance [ 11.140137] internal class: none [ 11.140494] caps: [ 11.140840] uvd vclk: 0 dclk: 0 [ 11.141184] power level 0 sclk: 30000 mclk: 15000 vddc: 825 vddci: 900 pcie gen: 3 [ 11.141543] power level 1 sclk: 40000 mclk: 112500 vddc: 950 vddci: 950 pcie gen: 3 [ 11.141909] power level 2 sclk: 80000 mclk: 112500 vddc: 1100 vddci: 950 pcie gen: 3 [ 11.142278] status: r [ 11.143477] [drm] radeon: dpm initialized [ 11.180331] [drm] fb mappable at 0xE1388000 [ 11.180709] [drm] vram apper at 0xE0000000 [ 11.181071] [drm] size 9216000 [ 11.181435] [drm] fb depth is 24 [ 11.181796] [drm] pitch is 7680 [ 11.182142] fb: conflicting fb hw usage radeondrmfb vs EFI VGA - removing generic driver [ 11.182567] fbcon: radeondrmfb (fb1) is primary device [ 11.182604] switching from power state: [ 11.182605] ui class: performance [ 11.182605] internal class: none [ 11.182606] caps: [ 11.182606] uvd vclk: 0 dclk: 0 [ 11.182607] power level 0 sclk: 30000 mclk: 15000 vddc: 825 vddci: 900 pcie gen: 3 [ 11.182608] power level 1 sclk: 40000 mclk: 112500 vddc: 950 vddci: 950 pcie gen: 3 [ 11.182608] power level 2 sclk: 80000 mclk: 112500 vddc: 1100 vddci: 950 pcie gen: 3 [ 11.182609] status: c r [ 11.182609] switching to power state: [ 11.182609] ui class: performance [ 11.182610] internal class: none [ 11.182610] caps: [ 11.182610] uvd vclk: 0 dclk: 0 [ 11.182611] power level 0 sclk: 30000 mclk: 15000 vddc: 825 vddci: 900 pcie gen: 3 [ 11.182612] power level 1 sclk: 40000 mclk: 112500 vddc: 950 vddci: 950 pcie gen: 3 [ 11.182612] power level 2 sclk: 80000 mclk: 112500 vddc: 1100 vddci: 950 pcie gen: 3 [ 11.182613] status: c r [ 11.841979] radeon 0000:01:00.0: fb1: radeondrmfb frame buffer device [ 11.842679] radeon 0000:01:00.0: registered panic notifier [ 11.843386] [drm] Initialized radeon 2.34.0 20080528 for 0000:01:00.0 on minor 0 Any ideas about what I might be doing wrong would be greatly appreciated. Please let me know what other information might be needed to work this out. Thanks -- Jim -- You are receiving this mail because: You are the assignee for the bug.

1 6

[Bug 67178] New: discrete radeon HD 6400M/7400M intense heating even though it's "off"
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=67178 Priority: medium Bug ID: 67178 Assignee: dri-devel(a)lists.freedesktop.org Summary: discrete radeon HD 6400M/7400M intense heating even though it's "off" Severity: normal Classification: Unclassified OS: Linux (All) Reporter: tpo_deb(a)sourcepole.ch Hardware: x86-64 (AMD64) Status: NEW Version: XOrg CVS Component: DRM/Radeon Product: DRI kernel 3.11-rc1 (also tested with 3.10 from Debian, 3.7, 3,2) # lspci -vnnn | grep VGA 00:02.0 VGA compatible controller [0300]: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller]) 01:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Seymour [Radeon HD 6400M/7400M Series] [1002:6760] (rev ff) (prog-if ff) This is a HP Pavillon dv7 6130ez Sometimes, at random, the radeon card goes into full heat production mode. This seems to occur a while (a few minutes?) after wakeup from resume, however I'm not sure about that. Suspending and resuming the laptop a few times (1 <= x <= ~4) seems to calm the card down again. Power consumption according to powertop goes from ~14W up to ~50W. This happens even though the card should be in theory switched off. Aka: # cat /sys/kernel/debug/vgaswitcheroo/switch 0:IGD:+:Pwr:0000:00:02.0 1:DIS: :Off:0000:01:00.0 # echo IGD > /sys/kernel/debug/vgaswitcheroo/switch # echo OFF > /sys/kernel/debug/vgaswitcheroo/switch doesn't seem to have no effect whatsoever. It *seems* that setting "radeon.dpm=1" kernel boot options and then: # echo "battery" > /sys/class/drm/card$no/device/power_dpm_state puts the card in an "active" but "relatively low" power consumption mode. It is then using about 20W (instead of the "normal" ~14W) so it's continuously faning out slightly warm air. And it "seems that when the card is running in this mode, then it won't get so often, or ever (I'm not very sure) into the berserk heating mode. The lowest observed power consumption of the laptop is ~7W. It'd be very nice if it'd be possible to shut the card down electrically via software and stay in this 7W mode. -- You are receiving this mail because: You are the assignee for the bug.

1 3

[Bug 67169] New: Black screen after waking from sleep
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=67169 Priority: medium Bug ID: 67169 Assignee: dri-devel(a)lists.freedesktop.org Summary: Black screen after waking from sleep Severity: normal Classification: Unclassified OS: All Reporter: marco(a)scannadinari.co.uk Hardware: Other Status: NEW Version: 9.1 Component: Drivers/DRI/Radeon Product: Mesa Created attachment 82813 --> https://bugs.freedesktop.org/attachment.cgi?id=82813&action=edit xorg log Waking the screen from sleep wakes it but all i get is a black screen. I am able to type and change ttys, etc, but after `systemctl restart gdm` as root the screen gets 'No signal'. The setting that causes this is GNOME's 'Blank screen' option in Settings>Power>Blank Screen I can confirm that AMD's proprietary drivers fix this. -- You are receiving this mail because: You are the assignee for the bug.

1 9

[Bug 67002] New: evergreen: after resume from suspend-to-ram operation is really slow with the latest DPM changes
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=67002 Priority: medium Bug ID: 67002 Assignee: dri-devel(a)lists.freedesktop.org Summary: evergreen: after resume from suspend-to-ram operation is really slow with the latest DPM changes Severity: normal Classification: Unclassified OS: Linux (All) Reporter: jackdachef(a)gmail.com Hardware: x86-64 (AMD64) Status: NEW Version: XOrg CVS Component: DRM/Radeon Product: DRI Using the drm-code from drm-fixes-3.11 branch (http://cgit.freedesktop.org/~agd5f/linux/log/?h=drm-fixes-3.11) against a 3.10 final kernel as explained in following post (http://phoronix.com/forums/showthread.php?82357-drm-fixes-3-11-with-3-10-st…) the card used is a HD5850, evergreen; ~amd64 Gentoo Linux, Intel Core i7 860, gcc 4.8.1, 2.17 I tested suspend-to-ram which in a prior state of drm-next would lock up the box (so much progress has been made - yay ! :) ): via following command: pm-suspend --quirk-dpms-on --quirk-s3-mode --quirk-vbe-post --quirk-vga-mode3 launched from VT1 (no X running) first things noticable: it takes longer (compared to the non-DPM driver) to turn off the computer so I first thought that it had hardlocked (fans were still spinning, screen turned off, harddisks +/- off - after some time the box went to suspend/sleep) it also takes longer to resume and for the screen to turn on following behavior is observable after the resume from suspend-to-ram: dmesg shows: [ 178.031724] [drm:r600_uvd_init] *ERROR* UVD not responding, trying to reset the VCPU!!! [ 178.430546] e1000e: eth0 NIC Link is Up 100 Mbps Full Duplex, Flow Control: Rx [ 178.430652] e1000e 0000:00:19.0 eth0: 10/100 speed: disabling TSO [ 179.052821] [drm:r600_uvd_init] *ERROR* UVD not responding, trying to reset the VCPU!!! [ 180.073918] [drm:r600_uvd_init] *ERROR* UVD not responding, trying to reset the VCPU!!! [ 181.095014] [drm:r600_uvd_init] *ERROR* UVD not responding, trying to reset the VCPU!!! [ 182.116110] [drm:r600_uvd_init] *ERROR* UVD not responding, trying to reset the VCPU!!! [ 182.120733] ata1: link is slow to respond, please be patient (ready=0) [ 182.122735] ata3: link is slow to respond, please be patient (ready=0) [ 182.128740] ata5: link is slow to respond, please be patient (ready=0) [ 182.130763] ata6: link is slow to respond, please be patient (ready=0) [ 183.137207] [drm:r600_uvd_init] *ERROR* UVD not responding, trying to reset the VCPU!!! [ 184.158303] [drm:r600_uvd_init] *ERROR* UVD not responding, trying to reset the VCPU!!! [ 185.179399] [drm:r600_uvd_init] *ERROR* UVD not responding, trying to reset the VCPU!!! [ 186.200496] [drm:r600_uvd_init] *ERROR* UVD not responding, trying to reset the VCPU!!! [ 186.817477] ata1: COMRESET failed (errno=-16) [ 186.819524] ata3: COMRESET failed (errno=-16) [ 186.825487] ata5: COMRESET failed (errno=-16) [ 186.827492] ata6: COMRESET failed (errno=-16) [ 187.221593] [drm:r600_uvd_init] *ERROR* UVD not responding, trying to reset the VCPU!!! [ 187.241615] [drm:r600_uvd_init] *ERROR* UVD not responding, giving up!!! [ 187.241618] [drm:evergreen_startup] *ERROR* radeon: error initializing UVD (-1). [ 187.241650] [drm] ib test on ring 0 succeeded in 0 usecs [ 187.241683] [drm] ib test on ring 3 succeeded in 1 usecs [ 187.246731] switching from power state: [ 187.246732] ui class: none [ 187.246733] internal class: boot [ 187.246733] caps: video [ 187.246734] uvd vclk: 0 dclk: 0 [ 187.246734] power level 0 sclk: 40000 mclk: 90000 vddc: 1000 vddci: 0 [ 187.246735] power level 1 sclk: 40000 mclk: 90000 vddc: 1000 vddci: 0 [ 187.246735] power level 2 sclk: 40000 mclk: 90000 vddc: 1000 vddci: 0 [ 187.246736] status: c b [ 187.246736] switching to power state: [ 187.246737] ui class: performance [ 187.246737] internal class: none [ 187.246738] caps: single_disp video [ 187.246738] uvd vclk: 0 dclk: 0 [ 187.246739] power level 0 sclk: 15700 mclk: 30000 vddc: 950 vddci: 1100 [ 187.246739] power level 1 sclk: 55000 mclk: 90000 vddc: 1038 vddci: 1100 [ 187.246740] power level 2 sclk: 72500 mclk: 100000 vddc: 1088 vddci: 1100 [ 187.246740] status: r [ 188.350006] ata3: SATA link up 3.0 Gbps (SStatus 123 SControl 300) [ 188.380064] ata3.00: configured for UDMA/133 [ 188.380117] sd 2:0:0:0: [sdb] Starting disk [ 188.511188] ata6: SATA link up 3.0 Gbps (SStatus 123 SControl 300) [ 188.523242] ata6.00: configured for UDMA/133 [ 188.523276] sd 5:0:0:0: [sdd] Starting disk [ 190.500189] ata5: SATA link up 3.0 Gbps (SStatus 123 SControl 300) [ 190.513376] ata5.00: configured for UDMA/133 [ 190.513455] sd 4:0:0:0: [sdc] Starting disk [ 191.462213] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300) [ 191.506493] ata1.00: configured for UDMA/133 [ 191.506573] sd 0:0:0:0: [sda] Starting disk [ 192.356977] [drm:atom_op_jump] *ERROR* atombios stuck in loop for more than 5secs aborting [ 192.356978] [drm:atom_execute_table_locked] *ERROR* atombios stuck executing D3DE (len 55, WS 0, PS 0) @ 0xD401 [ 192.376632] PM: resume of devices complete after 15600.251 msecs so suspend & resume works but with caveats - now wanted to see how X is running: launched up lightdm & logged into xfce4.10 : compiz-fusion (0.8*)/compositing is very very slow: e.g. when grabbing a window at the top with left mouse button and trying to move it - it moves only for several millimeters on screen (22'' screen with 1920x1080 resolution) - thus unusable when switching to xfwm4 (running Xfce4.10) moving windows around is somewhat acceptable - appears even fluid, launching up chromium and switching between tabs via ctrl + pgup/pgdown is noticably laggy launching glxgears via gnome-terminal - it seemingly looks ok (gears smoothly turning) [FPS locked to around 60] running glxgears via: R600_LLVM=0 vblank_mode=0 glxgears there's noticable, "micro"-stuttering and the FPS is around 260-290 if I recall correctly echo low > /sys/class/drm/card0/device/power_dpm_force_performance_level or echo high > /sys/class/drm/card0/device/power_dpm_force_performance_level doesn't make a difference - also FPS is significantly lower compared to "normal" operation (around 10x faster, e.g. 2900-3600 FPS with the non-DPM and "high" profile) next step was launching gnome-terminal from the below panel, then after sudo su -> dmesg and wanted to do further tests (e.g. sensors output) -> X crashed [ 973.217246] radeon 0000:01:00.0: GPU lockup CP stall for more than 10000msec [ 973.217254] radeon 0000:01:00.0: GPU lockup (waiting for 0x0000000000000199 last fence id 0x0000000000000198) X (or lightdm) couldn't be launched after that anymore, VT output was still shown - so I restarted via shutdown -r now hope that information helps in tracking down this issue I really love this new driver - now only operation after resume needs to work also, since I used it quite a lot :) (it does work with the non-DPM) similar message and behavior was seen on july 3rd/4th after several hours of operation & uptime (no suspend and resume): [ 973.217246] radeon 0000:01:00.0: GPU lockup CP stall for more than 10000msec [ 973.217254] radeon 0000:01:00.0: GPU lockup (waiting for 0x0000000000000199 last fence id 0x0000000000000198) -- You are receiving this mail because: You are the assignee for the bug.

1 15

[Bug 66963] New: r600: linux 3.11RC1 isn't booting with radeon.dpm=1 option in grub
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=66963 Priority: medium Bug ID: 66963 Assignee: dri-devel(a)lists.freedesktop.org Summary: r600: linux 3.11RC1 isn't booting with radeon.dpm=1 option in grub Severity: blocker Classification: Unclassified OS: Linux (All) Reporter: ken20001(a)ukr.net Hardware: x86-64 (AMD64) Status: NEW Version: unspecified Component: DRM/Radeon Product: DRI Linux 3.11RC1 isnt' booting with radeon.dpm=1 option in grub: screen becomes blank after grub trying to boot it. Without radeon.dpm=1 option system boots well. So, it seems, DPM isn't working. Graphics: Radeon HD2600 XT Linux: 3.11RC1 OS: Kubuntu 13.04 KDE: 4.11 beta2 Please, ask me for any additional info needed to help fix this issue. -- You are receiving this mail because: You are the assignee for the bug.

1 307

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

dri-devel July 2013