dri-devel July 2017

dri-devel@lists.freedesktop.org

212 participants
1542 discussions

[Bug 100666] amdgpu coolers never stoping linux
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=100666 Bug ID: 100666 Summary: amdgpu coolers never stoping linux Product: DRI Version: unspecified Hardware: All OS: Linux (All) Status: NEW Severity: normal Priority: medium Component: DRM/AMDgpu Assignee: dri-devel(a)lists.freedesktop.org Reporter: denji0k(a)gmail.com * Ubuntu 17.04, Kernel-4.10 * Gigabyte Radeon™ RX 480 WINDFORCE 8G rev1.0 * http://www.gigabyte.com/Graphics-Card/GV-RX480WF2-8GD-rev-10 * https://gist.github.com/anonymous/2e8964de6e8bf37d3a3b52dc7d213078 1. On Windows 10 & macOS coolers may be parked in mode 0 rpm. AMDGPU "pwm1_enable" can work only in mode=1, it is interesting that the rotation speed static. How hard can it be to implement? The initial implementation with support for throttling of the cooler. Have already been implemented, not enough reading VBIOS from EFI settings to automatically stop the cooler in idle. EFI VBIOS for macOS & Windows driver detected coolers supported noise fan 0% to idle card, but not linux amdgpu.... Lzzy can change /sys/class/drm/card0/device/power meters/hwmon1/pwm1=0 revs but under load it is fraught with burnout, nv support coolers speed pwm1_enable * 0=NONE - Card control PW? * 1=MANUAL * 2=AUTO - OS control PW? 2. When parking in cooler 0 rpm gauge still shows the rotation of coolers (lm-sensors), but the physical status LED/Fan stopped # echo 0 | tee /sys/class/drm/card0/device/hwmon/hwmon1/pwm1 # sensors amdgpu-pci-0100 Adapter: PCI adapter fan1: 875 RPM temp1: +38.0°C (crit = +0.0°C, hyst = +0.0°C) fan1: 875 RPM ? $ cat /sys/class/drm/card0/device/power_dpm_force_performance_level auto $ cat /sys/class/drm/card0/device/power_dpm_state performance $ cat /sys/class/drm/card0/device/hwmon/hwmon1/pwm1 81 $ cat /sys/class/drm/card0/device/hwmon/hwmon1/pwm1_min 0 $ cat /sys/class/drm/card0/device/hwmon/hwmon1/pwm1_max 255 $ echo 0 | sudo tee /sys/class/drm/card0/device/hwmon/hwmon1/pwm1_enable $ cat /sys/class/drm/card0/device/hwmon/hwmon1/pwm1_enable 1 $ echo 0 | sudo tee /sys/class/drm/card0/device/hwmon/hwmon1/pwm1_enable $ cat /sys/class/drm/card0/device/hwmon/hwmon1/pwm1_enable 1 $ echo 2 | sudo tee /sys/class/drm/card0/device/hwmon/hwmon1/pwm1_enable $ cat /sys/class/drm/card0/device/hwmon/hwmon1/pwm1_enable 1 $ lsb_release -dcr Description: Ubuntu 17.04 Release: 17.04 Codename: zesty $ uname -rmv 4.10.0-19-generic #21-Ubuntu SMP Thu Apr 6 17:04:57 UTC 2017 x86_64 $ DRI_PRIME=1 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: X.Org OpenGL renderer string: Gallium 0.4 on AMD POLARIS10 (DRM 3.9.0 / 4.10.0-19-generic, LLVM 4.0.0) OpenGL core profile version string: 4.5 (Core Profile) Mesa 17.0.3 OpenGL core profile shading language version string: 4.50 OpenGL version string: 3.0 Mesa 17.0.3 OpenGL shading language version string: 1.30 OpenGL ES profile version string: OpenGL ES 3.1 Mesa 17.0.3 OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.10 $ LC_ALL=C dmesg -Tx | grep -E "drm|radeon" kern :info : [Tue Apr 11 00:03:04 2017] [drm] Initialized kern :info : [Tue Apr 11 00:03:04 2017] [drm] amdgpu kernel modesetting enabled. kern :info : [Tue Apr 11 00:03:04 2017] fb: switching to amdgpudrmfb from EFI VGA kern :info : [Tue Apr 11 00:03:04 2017] [drm] initializing kernel modesetting (POLARIS10 0x1002:0x67DF 0x1458:0x22DF 0xC7). kern :info : [Tue Apr 11 00:03:04 2017] [drm] register mmio base: 0xEFE00000 kern :info : [Tue Apr 11 00:03:04 2017] [drm] register mmio size: 262144 kern :info : [Tue Apr 11 00:03:04 2017] [drm] doorbell mmio base: 0xE0000000 kern :info : [Tue Apr 11 00:03:04 2017] [drm] doorbell mmio size: 2097152 kern :info : [Tue Apr 11 00:03:04 2017] [drm] probing gen 2 caps for device 8086:1901 = 261ad03/e kern :info : [Tue Apr 11 00:03:04 2017] [drm] probing mlw for device 8086:1901 = 261ad03 kern :info : [Tue Apr 11 00:03:04 2017] [drm] UVD is enabled in VM mode kern :info : [Tue Apr 11 00:03:04 2017] [drm] VCE enabled in VM mode kern :info : [Tue Apr 11 00:03:04 2017] [drm] GPU post is not needed kern :info : [Tue Apr 11 00:03:04 2017] [drm] Detected VRAM RAM=8192M, BAR=256M kern :info : [Tue Apr 11 00:03:04 2017] [drm] RAM width 256bits GDDR5 kern :info : [Tue Apr 11 00:03:04 2017] [drm] amdgpu: 8192M of VRAM memory ready kern :info : [Tue Apr 11 00:03:04 2017] [drm] amdgpu: 8192M of GTT memory ready. kern :info : [Tue Apr 11 00:03:04 2017] [drm] GART: num cpu pages 2097152, num gpu pages 2097152 kern :info : [Tue Apr 11 00:03:04 2017] [drm] PCIE GART of 8192M enabled (table at 0x0000000000040000). kern :info : [Tue Apr 11 00:03:04 2017] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013). kern :info : [Tue Apr 11 00:03:04 2017] [drm] Driver supports precise vblank timestamp query. kern :info : [Tue Apr 11 00:03:04 2017] [drm] amdgpu: irq initialized. kern :info : [Tue Apr 11 00:03:04 2017] [drm] AMDGPU Display Connectors kern :info : [Tue Apr 11 00:03:04 2017] [drm] Connector 0: kern :info : [Tue Apr 11 00:03:04 2017] [drm] DP-1 kern :info : [Tue Apr 11 00:03:04 2017] [drm] HPD6 kern :info : [Tue Apr 11 00:03:04 2017] [drm] DDC: 0x4868 0x4868 0x4869 0x4869 0x486a 0x486a 0x486b 0x486b kern :info : [Tue Apr 11 00:03:04 2017] [drm] Encoders: kern :info : [Tue Apr 11 00:03:04 2017] [drm] DFP1: INTERNAL_UNIPHY2 kern :info : [Tue Apr 11 00:03:04 2017] [drm] Connector 1: kern :info : [Tue Apr 11 00:03:04 2017] [drm] DP-2 kern :info : [Tue Apr 11 00:03:04 2017] [drm] HPD4 kern :info : [Tue Apr 11 00:03:04 2017] [drm] DDC: 0x4870 0x4870 0x4871 0x4871 0x4872 0x4872 0x4873 0x4873 kern :info : [Tue Apr 11 00:03:04 2017] [drm] Encoders: kern :info : [Tue Apr 11 00:03:04 2017] [drm] DFP2: INTERNAL_UNIPHY2 kern :info : [Tue Apr 11 00:03:04 2017] [drm] Connector 2: kern :info : [Tue Apr 11 00:03:04 2017] [drm] DP-3 kern :info : [Tue Apr 11 00:03:04 2017] [drm] HPD1 kern :info : [Tue Apr 11 00:03:04 2017] [drm] DDC: 0x486c 0x486c 0x486d 0x486d 0x486e 0x486e 0x486f 0x486f kern :info : [Tue Apr 11 00:03:04 2017] [drm] Encoders: kern :info : [Tue Apr 11 00:03:04 2017] [drm] DFP3: INTERNAL_UNIPHY1 kern :info : [Tue Apr 11 00:03:04 2017] [drm] Connector 3: kern :info : [Tue Apr 11 00:03:04 2017] [drm] HDMI-A-1 kern :info : [Tue Apr 11 00:03:04 2017] [drm] HPD5 kern :info : [Tue Apr 11 00:03:04 2017] [drm] DDC: 0x4874 0x4874 0x4875 0x4875 0x4876 0x4876 0x4877 0x4877 kern :info : [Tue Apr 11 00:03:04 2017] [drm] Encoders: kern :info : [Tue Apr 11 00:03:04 2017] [drm] DFP4: INTERNAL_UNIPHY1 kern :info : [Tue Apr 11 00:03:04 2017] [drm] Connector 4: kern :info : [Tue Apr 11 00:03:04 2017] [drm] DVI-D-1 kern :info : [Tue Apr 11 00:03:04 2017] [drm] HPD3 kern :info : [Tue Apr 11 00:03:04 2017] [drm] DDC: 0x487c 0x487c 0x487d 0x487d 0x487e 0x487e 0x487f 0x487f kern :info : [Tue Apr 11 00:03:04 2017] [drm] Encoders: kern :info : [Tue Apr 11 00:03:04 2017] [drm] DFP5: INTERNAL_UNIPHY kern :info : [Tue Apr 11 00:03:04 2017] [drm] Found UVD firmware Version: 1.79 Family ID: 16 kern :info : [Tue Apr 11 00:03:04 2017] [drm] Found VCE firmware Version: 52.4 Binary ID: 3 kern :info : [Tue Apr 11 00:03:04 2017] [drm] ring test on 0 succeeded in 15 usecs kern :info : [Tue Apr 11 00:03:04 2017] [drm] ring test on 1 succeeded in 28 usecs kern :info : [Tue Apr 11 00:03:04 2017] [drm] ring test on 2 succeeded in 28 usecs kern :info : [Tue Apr 11 00:03:04 2017] [drm] ring test on 3 succeeded in 13 usecs kern :info : [Tue Apr 11 00:03:04 2017] [drm] ring test on 4 succeeded in 13 usecs kern :info : [Tue Apr 11 00:03:04 2017] [drm] ring test on 5 succeeded in 13 usecs kern :info : [Tue Apr 11 00:03:04 2017] [drm] ring test on 6 succeeded in 14 usecs kern :info : [Tue Apr 11 00:03:04 2017] [drm] ring test on 7 succeeded in 13 usecs kern :info : [Tue Apr 11 00:03:04 2017] [drm] ring test on 8 succeeded in 13 usecs kern :info : [Tue Apr 11 00:03:04 2017] [drm] ring test on 9 succeeded in 6 usecs kern :info : [Tue Apr 11 00:03:04 2017] [drm] ring test on 10 succeeded in 6 usecs kern :info : [Tue Apr 11 00:03:04 2017] [drm] ring test on 11 succeeded in 1 usecs kern :info : [Tue Apr 11 00:03:04 2017] [drm] UVD initialized successfully. kern :info : [Tue Apr 11 00:03:05 2017] [drm] ring test on 12 succeeded in 10 usecs kern :info : [Tue Apr 11 00:03:05 2017] [drm] ring test on 13 succeeded in 5 usecs kern :info : [Tue Apr 11 00:03:05 2017] [drm] VCE initialized successfully. kern :info : [Tue Apr 11 00:03:05 2017] [drm] fb mappable at 0xD136F000 kern :info : [Tue Apr 11 00:03:05 2017] [drm] vram apper at 0xD0000000 kern :info : [Tue Apr 11 00:03:05 2017] [drm] size 8294400 kern :info : [Tue Apr 11 00:03:05 2017] [drm] fb depth is 24 kern :info : [Tue Apr 11 00:03:05 2017] [drm] pitch is 7680 kern :info : [Tue Apr 11 00:03:05 2017] fbcon: amdgpudrmfb (fb0) is primary device kern :info : [Tue Apr 11 00:03:05 2017] amdgpu 0000:01:00.0: fb0: amdgpudrmfb frame buffer device kern :info : [Tue Apr 11 00:03:05 2017] [drm] ib test on ring 0 succeeded kern :info : [Tue Apr 11 00:03:05 2017] [drm] ib test on ring 1 succeeded kern :info : [Tue Apr 11 00:03:05 2017] [drm] ib test on ring 2 succeeded kern :info : [Tue Apr 11 00:03:05 2017] [drm] ib test on ring 3 succeeded kern :info : [Tue Apr 11 00:03:05 2017] [drm] ib test on ring 4 succeeded kern :info : [Tue Apr 11 00:03:05 2017] [drm] ib test on ring 5 succeeded kern :info : [Tue Apr 11 00:03:05 2017] [drm] ib test on ring 6 succeeded kern :info : [Tue Apr 11 00:03:05 2017] [drm] ib test on ring 7 succeeded kern :info : [Tue Apr 11 00:03:05 2017] [drm] ib test on ring 8 succeeded kern :info : [Tue Apr 11 00:03:05 2017] [drm] ib test on ring 9 succeeded kern :info : [Tue Apr 11 00:03:05 2017] [drm] ib test on ring 10 succeeded kern :info : [Tue Apr 11 00:03:05 2017] [drm] ib test on ring 11 succeeded kern :info : [Tue Apr 11 00:03:05 2017] [drm] ib test on ring 12 succeeded kern :info : [Tue Apr 11 00:03:05 2017] [drm] Initialized amdgpu 3.9.0 20150101 for 0000:01:00.0 on minor 0 -- You are receiving this mail because: You are the assignee for the bug.

1 17

[Bug 29579] New: 2.6.35 with RV630 AGP does not enable KMS/DRM
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=29579 Summary: 2.6.35 with RV630 AGP does not enable KMS/DRM Product: DRI Version: XOrg CVS Platform: x86 (IA32) OS/Version: Linux (All) Status: NEW Severity: normal Priority: medium Component: DRM/Radeon AssignedTo: dri-devel(a)lists.freedesktop.org ReportedBy: juho-mikko.pellinen(a)lut.fi Created an attachment (id=37860) --> (https://bugs.freedesktop.org/attachment.cgi?id=37860) 2.6.35 Xorg.0.log with radeon.modeset=0 I'm having problems with getting KMS to work with 2.6.35. I have earlier configuration with 2.6.34 and KMS works as it should. When booting up I get framebuffer console and X starts without errors. Steps to reproduce: 1. copy working config from 2.6.34 to 2.6.35 2. make oldconfig and double check the differing options, none related to drm/radeon 3. compile kernel, boot it with different configurations 4. drm does not initialize, framebuffer console does not came up, X can't open dri 6. If I boot with radeon.modeset=0 drm initializes. I have tried number of kernel configs without any success. Prior to this I consulted #radeon, but it couldn't find any problems with my configuration. Normally I compile things as modules and it works quite well. AGP-drivers are compiled as modules/in kernel and load before radeon/drm. I have tried 2.6.35 vanilla, -rc2, -rc4, -rc6, -rc6, -gentoo-r1 . They all fail the same way. Any ideas how to get KMS working again? My hardware: RV630 AGP (HD2600 Pro AGP) nForce3 chipset CPU Athlon64 3xxx+ lscpi: 00:00.0 Host bridge: nVidia Corporation nForce3 250Gb Host Bridge (rev a1) 00:01.0 ISA bridge: nVidia Corporation nForce3 250Gb LPC Bridge (rev a2) 00:01.1 SMBus: nVidia Corporation nForce 250Gb PCI System Management (rev a1) 00:02.0 USB Controller: nVidia Corporation CK8S USB Controller (rev a1) 00:02.1 USB Controller: nVidia Corporation CK8S USB Controller (rev a1) 00:02.2 USB Controller: nVidia Corporation nForce3 EHCI USB 2.0 Controller (rev a2) 00:05.0 Bridge: nVidia Corporation CK8S Ethernet Controller (rev a2) 00:06.0 Multimedia audio controller: nVidia Corporation nForce3 250Gb AC'97 Audio Controller (rev a1) 00:08.0 IDE interface: nVidia Corporation CK8S Parallel ATA Controller (v2.5) (rev a2) 00:0a.0 IDE interface: nVidia Corporation nForce3 Serial ATA Controller (rev a2) 00:0b.0 PCI bridge: nVidia Corporation nForce3 250Gb AGP Host to PCI Bridge (rev a2) 00:0e.0 PCI bridge: nVidia Corporation nForce3 250Gb PCI-to-PCI Bridge (rev a2) 00:18.0 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] HyperTransport Technology Configuration 00:18.1 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Address Map 00:18.2 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] DRAM Controller 00:18.3 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Miscellaneous Control 01:00.0 VGA compatible controller: ATI Technologies Inc RV630 PRO AGP [Radeon HD 2600 PRO AGP] 02:06.0 Ethernet controller: VIA Technologies, Inc. VT6105/VT6106S [Rhine-III] (rev 86) 02:07.0 Multimedia audio controller: Creative Labs SB Audigy (rev 03) 02:07.1 Input device controller: Creative Labs SB Audigy Game Port (rev 03) 02:07.2 FireWire (IEEE 1394): Creative Labs SB Audigy FireWire Port 02:08.0 Multimedia audio controller: C-Media Electronics Inc CM8738 (rev 10) -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.

1 33

[Bug 100591] [AMD APU A9-9410] Kernel hang when using graphics acceleration
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=100591 Bug ID: 100591 Summary: [AMD APU A9-9410] Kernel hang when using graphics acceleration Product: DRI Version: XOrg git Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: normal Priority: medium Component: DRM/AMDgpu Assignee: dri-devel(a)lists.freedesktop.org Reporter: ben.davenportray(a)gmail.com Kernel hangs hard whenever it has to do anything graphics accelerated or too cpu intensive (two laravel web server instances / opening chromium / opening YouTube on Firefox / I look at it too hard). It won't even let me switch to another console, forcing me to hard reboot. I am unable to see anything using `journalctl -xe` when my system goes down; either the log just stops or the file is corrupted, though I also don't know what I am looking for. I was able to confirm that it wasn't thermal overheating, and chip diagnostics say that it is okay. Linux 4.9.20 xorg-xserver 1.19.2 -- You are receiving this mail because: You are the assignee for the bug.

1 11

[Bug 100460] AMDGPU system hang with Slic3r Prusa Edition
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=100460 Bug ID: 100460 Summary: AMDGPU system hang with Slic3r Prusa Edition Product: DRI Version: unspecified Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: major Priority: medium Component: DRM/AMDgpu Assignee: dri-devel(a)lists.freedesktop.org Reporter: greg(a)chown.ath.cx The 3D printing software Slic3r Prusa Edition uses OpenGL to render 3D views of objects and a preview of the tool path. The tool path preview causes system hangs for me with AMDGPU and RadeonSI, with the latest mainline code of all components involved (Linux 4.11rc4, Mesa git, LLVM svn). It seems to be memory management related. It looks like there may be a deadlock of some sort. Here's how to reproduce. I wasn't able to record a working trace. 1. Download Slic3r Prusa Edition 1.33.8 from https://github.com/prusa3d/Slic3r/releases/tag/version_1.33.8 (AppImage is the easy choice) 2. Get the model "LASER CAT - Voronoi Style" from http://www.thingiverse.com/thing:179266/#files (e.g. Laser_Cat_-_Voronoi_coarse.stl) 3. Start Slic3r, abort setup wizard. Default settings are fine. 4. Press "Add..." and select the .stl file 5. Press "Slice now" in the right panel 6. Select "Preview" in the bottom tab list This results in a hanging system. The kernel's hang detection is triggered after a while: 66929.634087] NMI watchdog: BUG: soft lockup - CPU#1 stuck for 23s! [perl5.22.0:21405] [66929.634087] Modules linked in: ufs qnx4 hfsplus hfs minix ntfs msdos jfs xfs libcrc32c ccm nvram f71882fg arc4 rt2800usb rt2x00usb rt2800lib rt2x00lib mac80211 cfg80211 input_leds joydev pci_stub vboxpci(OE) vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) binfmt_misc nls_iso8859_1 edac_mce_amd edac_core kvm_amd kvm irqbypass crct10dif_pclmul crc32_pclmul ghash_clmulni_intel snd_seq_midi pcbc snd_seq_midi_event snd_rawmidi snd_hda_codec_realtek snd_hda_codec_generic snd_hda_codec_hdmi snd_seq snd_hda_intel snd_hda_codec snd_hda_core snd_hwdep aesni_intel aes_x86_64 crypto_simd glue_helper cryptd snd_pcm fam15h_power k10temp snd_seq_device i2c_piix4 snd_timer snd soundcore shpchp tpm_infineon mac_hid cpuid msr parport_pc ppdev lp parport autofs4 btrfs xor raid6_pq hid_generic usbhid hid uas usb_storage amdkfd [66929.634087] amd_iommu_v2 amdgpu i2c_algo_bit ttm drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops drm ahci r8169 libahci mii wmi fjes video [66929.634087] CPU: 1 PID: 21405 Comm: perl5.22.0 Tainted: G OE 4.11.0-041100rc1-generic #201703051731 [66929.634087] Hardware name: MSI MS-7721/A68HM-P33 (MS-7721), BIOS V34.4 12/15/2014 [66929.634087] task: ffffa0f8eb574380 task.stack: ffffb6f146c1c000 [66929.634087] RIP: 0010:_raw_spin_unlock_irqrestore+0x15/0x20 [66929.634087] RSP: 0018:ffffb6f146c1f780 EFLAGS: 00000282 ORIG_RAX: ffffffffffffff10 [66929.634087] RAX: 0000000000000002 RBX: 0000000000000000 RCX: 0000000000000000 [66929.634087] RDX: 0000000000000000 RSI: 0000000000000282 RDI: 0000000000000282 [66929.634087] RBP: ffffb6f146c1f780 R08: 0000000000000000 R09: ffffa0f8cd1bd380 [66929.634087] R10: ffffb6f14571e628 R11: 000000000001ef18 R12: 0000000000000001 [66929.634087] R13: ffffa0f8cd1bd380 R14: ffffa0f8eb512940 R15: 0000000000000001 [66929.634087] FS: 00007f6b3c771700(0000) GS:ffffa0f8fec80000(0000) knlGS:0000000000000000 [66929.634087] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [66929.634087] CR2: 00007f69a3195000 CR3: 00000003d9548000 CR4: 00000000000406e0 [66929.634087] Call Trace: [66929.634087] alloc_iova+0x21c/0x240 [66929.634087] alloc_iova_fast+0xa6/0x200 [66929.634087] dma_ops_alloc_iova.isra.23+0x6b/0x80 [66929.634087] __map_single.isra.24+0x49/0x1b0 [66929.634087] map_page+0x64/0x80 [66929.634087] amdgpu_ttm_tt_populate+0xe9/0x270 [amdgpu] [66929.634087] ttm_tt_bind+0x2b/0x60 [ttm] [66929.634087] ttm_bo_handle_move_mem+0x535/0x5b0 [ttm] [66929.634087] ? shmem_alloc_inode+0x1a/0x30 [66929.634087] ttm_bo_validate+0x13e/0x150 [ttm] [66929.634087] ttm_bo_init+0x243/0x430 [ttm] [66929.634087] amdgpu_bo_create_restricted+0x4ae/0x5b0 [amdgpu] [66929.634087] ? amdgpu_update_memory_usage+0xe0/0xe0 [amdgpu] [66929.634087] amdgpu_bo_create+0xed/0x1f0 [amdgpu] [66929.634087] amdgpu_gem_object_create+0xba/0x150 [amdgpu] [66929.634087] amdgpu_gem_create_ioctl+0xa4/0x130 [amdgpu] [66929.634087] drm_ioctl+0x209/0x4c0 [drm] [66929.634087] ? amdgpu_gem_object_close+0x130/0x130 [amdgpu] [66929.634087] ? __handle_mm_fault+0x953/0x10e0 [66929.634087] ? do_mmap+0x445/0x510 [66929.634087] ? common_mmap+0x45/0x50 [66929.634087] amdgpu_drm_ioctl+0x4f/0x90 [amdgpu] [66929.634087] do_vfs_ioctl+0xa3/0x600 [66929.634087] ? handle_mm_fault+0xd0/0x240 [66929.634087] ? __check_object_size+0x100/0x19d [66929.634087] SyS_ioctl+0x79/0x90 [66929.634087] entry_SYSCALL_64_fastpath+0x1e/0xad [66929.634087] RIP: 0033:0x7f6b3b31e357 [66929.634087] RSP: 002b:00007fff75cc5b98 EFLAGS: 00000246 ORIG_RAX: 0000000000000010 [66929.634087] RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 00007f6b3b31e357 [66929.634087] RDX: 00007fff75cc5be0 RSI: 00000000c0206440 RDI: 000000000000000e [66929.634087] RBP: 0000000000c3c000 R08: 00000000072c11c0 R09: 0000000000000001 [66929.634087] R10: 00007f6b3b5e5bc8 R11: 0000000000000246 R12: 000000000000c000 [66929.634087] R13: 0000000006bac130 R14: 00007f6a30c3a010 R15: 0000000000000002 [66929.634087] Code: 08 74 0b 65 81 25 58 dc b3 59 ff ff ff 7f 89 d0 5d c3 90 90 90 90 0f 1f 44 00 00 55 48 89 e5 c6 07 00 0f 1f 40 00 48 89 f7 57 9d <0f> 1f 44 00 00 5d c3 0f 1f 40 00 0f 1f 44 00 00 55 48 89 e5 c6 The application possibly might not behave well, but this should never happen nonetheless. -- You are receiving this mail because: You are the assignee for the bug.

1 1

[Bug 100399] Kernel invalid opcode on unbinding amdgpu
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=100399 Bug ID: 100399 Summary: Kernel invalid opcode on unbinding amdgpu Product: DRI Version: unspecified Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: normal Priority: medium Component: DRM/AMDgpu Assignee: dri-devel(a)lists.freedesktop.org Reporter: nospam(a)kota.moe I'm not sure where is the best place to post this report, so let me know if there is a better place than here. I have a RX480 GPU that I use with amdgpu on linux 4.11.0-rc3+ (compiled with the Ubuntu 4.8.0 lowlatency config), and everything seemingly works fine until I try to unbind amdgpu from the device. This also happened with linux 4.10.0-rc3+ I've reproduced this regardless of whether the amdgpu device is the primary or secondary display device, and whether X is active or not. Observe: $ lspci | grep AMD 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 470/480] (rev c7) 01:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Device aaf0 $ echo 01:00.0 | sudo tee /sys/bus/pci/devices/01:00.0/driver/unbind Segmentation Fault At this point, the system becomes unstable and some system calls seems to just hang (not sure which exactly, but sudo and ps a breaks). Trying to shut down the system also hangs. dmesg output: [ 86.993436] ------------[ cut here ]------------ [ 86.993439] kernel BUG at drivers/gpu/drm/amd/amdgpu/gfx_v8_0.c:6930! [ 86.993442] invalid opcode: 0000 [#1] PREEMPT SMP [ 86.993443] Modules linked in: ipt_MASQUERADE nf_nat_masquerade_ipv4 xt_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp iptable_filter nf_nat_h323 nf_conntrack_h323 nf_nat_pptp nf_nat_proto_gre nf_conntrack_pptp nf_conntrack_proto_gre nf_nat_tftp nf_conntrack_tftp nf_nat_sip nf_conntrack_sip nf_nat_irc nf_conntrack_irc nf_nat_ftp nf_conntrack_ftp iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack libcrc32c ip_tables x_tables bnep bridge stp llc binfmt_misc dm_snapshot dm_bufio nls_iso8859_1 intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc aesni_intel aes_x86_64 crypto_simd glue_helper cryptd intel_cstate intel_rapl_perf input_leds serio_raw joydev snd_hda_codec_realtek snd_hda_codec_generic snd_hda_codec_hdmi [ 86.993488] mei_me snd_hda_intel mei snd_hda_codec snd_hda_core intel_pch_thermal snd_hwdep snd_pcm snd_timer snd soundcore hci_uart btbcm btqca btintel bluetooth intel_lpss_acpi intel_lpss shpchp acpi_als acpi_pad mac_hid kfifo_buf tpm_infineon industrialio kvm_intel kvm irqbypass it87 hwmon_vid parport_pc ppdev lp parport autofs4 btrfs xor raid6_pq hid_generic usbhid mxm_wmi amdkfd amd_iommu_v2 i915 amdgpu ttm drm_kms_helper igb e1000e syscopyarea sysfillrect dca psmouse nvme sysimgblt ptp fb_sys_fops nvme_core firewire_ohci pps_core i2c_algo_bit drm ahci firewire_core crc_itu_t libahci wmi video pinctrl_sunrisepoint i2c_hid pinctrl_intel hid fjes [ 86.993519] CPU: 5 PID: 2955 Comm: tee Not tainted 4.11.0-rc3+ #1 [ 86.993521] Hardware name: Gigabyte Technology Co., Ltd. Z170X-UD5/Z170X-UD5-CF, BIOS F4 10/21/2015 [ 86.993523] task: ffff8ee839f4d880 task.stack: ffffacb00624c000 [ 86.993539] RIP: 0010:gfx_v8_0_kiq_set_interrupt_state+0xce/0xe0 [amdgpu] [ 86.993541] RSP: 0018:ffffacb00624fb68 EFLAGS: 00010046 [ 86.993543] RAX: 0000000000000000 RBX: ffff8ee855f6b2d8 RCX: 0000000000000000 [ 86.993545] RDX: 0000000000000000 RSI: ffff8ee855f6c750 RDI: ffff8ee855f68000 [ 86.993546] RBP: ffffacb00624fba8 R08: 000000000001e640 R09: ffffffffc039bcb9 [ 86.993548] R10: fffff1f06155f200 R11: 0000000000000000 R12: ffff8ee855f68000 [ 86.993550] R13: ffff8ee855f6b548 R14: ffff8ee855f6c750 R15: 0000000000000000 [ 86.993552] FS: 00007f1260269700(0000) GS:ffff8ee881d40000(0000) knlGS:0000000000000000 [ 86.993555] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 86.993556] CR2: 000055651d517908 CR3: 0000000831b78000 CR4: 00000000003406e0 [ 86.993558] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 [ 86.993560] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 [ 86.993562] Call Trace: [ 86.993572] ? amdgpu_irq_disable_all+0x89/0xe0 [amdgpu] [ 86.993582] amdgpu_irq_uninstall+0x17/0x20 [amdgpu] [ 86.993589] drm_irq_uninstall+0x8e/0x170 [drm] [ 86.993598] amdgpu_irq_fini+0x83/0xc0 [amdgpu] [ 86.993606] tonga_ih_sw_fini+0x12/0x30 [amdgpu] [ 86.993613] amdgpu_fini+0x2c5/0x490 [amdgpu] [ 86.993620] amdgpu_device_fini+0x53/0x160 [amdgpu] [ 86.993626] amdgpu_driver_unload_kms+0x4f/0xa0 [amdgpu] [ 86.993632] drm_dev_unregister+0x3c/0xe0 [drm] [ 86.993637] drm_put_dev+0x36/0x70 [drm] [ 86.993643] amdgpu_pci_remove+0x15/0x20 [amdgpu] [ 86.993646] pci_device_remove+0x39/0xc0 [ 86.993649] device_release_driver_internal+0x155/0x210 [ 86.993651] device_release_driver+0x12/0x20 [ 86.993653] unbind_store+0x10d/0x160 [ 86.993655] drv_attr_store+0x25/0x30 [ 86.993657] sysfs_kf_write+0x37/0x40 [ 86.993659] kernfs_fop_write+0x120/0x1a0 [ 86.993662] __vfs_write+0x37/0x160 [ 86.993665] ? apparmor_file_permission+0x1a/0x20 [ 86.993667] ? security_file_permission+0x3b/0xc0 [ 86.993669] vfs_write+0xb8/0x1b0 [ 86.993672] SyS_write+0x55/0xc0 [ 86.993674] entry_SYSCALL_64_fastpath+0x1e/0xad [ 86.993676] RIP: 0033:0x7f125fd9f6e0 [ 86.993678] RSP: 002b:00007ffe60a95358 EFLAGS: 00000246 ORIG_RAX: 0000000000000001 [ 86.993681] RAX: ffffffffffffffda RBX: 000000000126e090 RCX: 00007f125fd9f6e0 [ 86.993682] RDX: 000000000000000d RSI: 00007ffe60a95400 RDI: 0000000000000003 [ 86.993684] RBP: 0000000000000000 R08: 000000000126e520 R09: 0000000000000000 [ 86.993686] R10: 0000000000000837 R11: 0000000000000246 R12: 0000000000000000 [ 86.993688] R13: 000000000000002d R14: 000000000126f590 R15: 000000000126e090 [ 86.993690] Code: ff 25 ff ff ff df 31 c9 be b4 30 00 00 89 c2 48 89 df e8 86 9a fb ff 31 d2 44 89 e6 48 89 df e8 e9 96 fb ff 25 ff ff ff df eb b6 <0f> 0b 0f 0b 0f 1f 40 00 66 2e 0f 1f 84 00 00 00 00 00 55 48 89 [ 86.993716] RIP: gfx_v8_0_kiq_set_interrupt_state+0xce/0xe0 [amdgpu] RSP: ffffacb00624fb68 [ 86.993719] ---[ end trace 36bcf8facd6b3d68 ]--- [ 86.993722] note: tee[2955] exited with preempt_count 1 -- You are receiving this mail because: You are the assignee for the bug.

1 11

[Bug 100058] NULL pointer dereference when blacklisting radeon
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=100058 Bug ID: 100058 Summary: NULL pointer dereference when blacklisting radeon Product: DRI Version: XOrg git Hardware: Other OS: Linux (All) Status: NEW Severity: normal Priority: medium Component: General Assignee: dri-devel(a)lists.freedesktop.org Reporter: adam.wolk(a)tintagel.pl Created attachment 130063 --> https://bugs.freedesktop.org/attachment.cgi?id=130063&action=edit system log from multiple reboots I noticed my external display constantly turning on and off unless a DRI app is active (ie. running DRI_PRIME=1 glxgears). I was suggested to blacklist the `radeon` driver as I am using `amdgpu` and I proceeded to do this. Blacklisting the driver results in the system not being able to boot. >From the first attempts I caught those 2 screenshots: https://imgur.com/AjG7IgB,xEi2L4B https://imgur.com/xEi2L4B my last attempt revealed a kernel null pointer dereference that was logged in journalctl (other errors; stack traces were not logged) https://gist.github.com/mulander/6f4d8bfc0fe73af25ee2c95014754822 I'm attaching all journalctl entries since today, search it for 'BUG' to see the boot with the null pointer dereference. It was started with radeon blacklisted on boot. I tried several blacklisting methods including modprobe.conf & regenerating initramfs. [mulander@napalm ~]$ uname -a Linux napalm 4.9.11-1-ARCH #1 SMP PREEMPT Sun Feb 19 13:45:52 UTC 2017 x86_64 GNU/Linux [mulander@napalm ~]$ lspci 00:00.0 Host bridge: Intel Corporation Haswell-ULT DRAM Controller (rev 0b) 00:02.0 VGA compatible controller: Intel Corporation Haswell-ULT Integrated Graphics Controller (rev 0b) 00:03.0 Audio device: Intel Corporation Haswell-ULT HD Audio Controller (rev 0b) 00:14.0 USB controller: Intel Corporation 8 Series USB xHCI HC (rev 04) 00:16.0 Communication controller: Intel Corporation 8 Series HECI #0 (rev 04) 00:1b.0 Audio device: Intel Corporation 8 Series HD Audio Controller (rev 04) 00:1c.0 PCI bridge: Intel Corporation 8 Series PCI Express Root Port 3 (rev e4) 00:1c.3 PCI bridge: Intel Corporation 8 Series PCI Express Root Port 4 (rev e4) 00:1c.4 PCI bridge: Intel Corporation 8 Series PCI Express Root Port 5 (rev e4) 00:1d.0 USB controller: Intel Corporation 8 Series USB EHCI #1 (rev 04) 00:1f.0 ISA bridge: Intel Corporation 8 Series LPC Controller (rev 04) 00:1f.2 SATA controller: Intel Corporation 8 Series SATA Controller 1 [AHCI mode] (rev 04) 00:1f.3 SMBus: Intel Corporation 8 Series SMBus Controller (rev 04) 01:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 10) 02:00.0 Network controller: Qualcomm Atheros QCA9565 / AR9565 Wireless Network Adapter (rev 01) 03:00.0 Display controller: Advanced Micro Devices, Inc. [AMD/ATI] Sun LE [Radeon HD 8550M / R5 M230] lsmod Module Size Used by ctr 16384 6 ccm 20480 3 hid_generic 16384 0 usbhid 49152 0 joydev 20480 0 mousedev 20480 0 amdgpu 1499136 0 snd_hda_codec_hdmi 45056 1 amdkfd 122880 1 amd_iommu_v2 20480 1 amdkfd intel_rapl 20480 0 x86_pkg_temp_thermal 16384 0 intel_powerclamp 16384 0 coretemp 16384 0 kvm 524288 0 radeon 1478656 4 irqbypass 16384 1 kvm intel_cstate 16384 0 ttm 86016 2 amdgpu,radeon intel_rapl_perf 16384 0 snd_soc_rt5640 110592 0 snd_soc_rl6231 16384 1 snd_soc_rt5640 ppdev 20480 0 snd_soc_core 188416 1 snd_soc_rt5640 snd_hda_codec_conexant 24576 1 snd_hda_codec_generic 69632 1 snd_hda_codec_conexant snd_hda_intel 32768 7 snd_hda_codec 106496 4 snd_hda_intel,snd_hda_codec_conexant,snd_hda_codec_hdmi,snd_hda_codec_generic snd_compress 20480 1 snd_soc_core evdev 24576 15 snd_hda_core 65536 5 snd_hda_intel,snd_hda_codec_conexant,snd_hda_codec,snd_hda_codec_hdmi,snd_hda_codec_generic snd_pcm_dmaengine 16384 1 snd_soc_core snd_hwdep 16384 1 snd_hda_codec psmouse 131072 0 ideapad_laptop 24576 0 pcspkr 16384 0 input_leds 16384 0 sparse_keymap 16384 1 ideapad_laptop arc4 16384 2 mac_hid 16384 0 r8169 77824 0 ath9k 131072 0 ath9k_common 32768 1 ath9k ath9k_hw 442368 2 ath9k,ath9k_common uvcvideo 86016 0 ath 28672 3 ath9k_hw,ath9k,ath9k_common videobuf2_vmalloc 16384 1 uvcvideo videobuf2_memops 16384 1 videobuf2_vmalloc ath3k 20480 0 btusb 40960 0 videobuf2_v4l2 20480 1 uvcvideo mac80211 688128 1 ath9k videobuf2_core 36864 2 uvcvideo,videobuf2_v4l2 btrtl 16384 1 btusb btbcm 16384 1 btusb btintel 16384 1 btusb videodev 151552 3 uvcvideo,videobuf2_core,videobuf2_v4l2 rtsx_usb_ms 20480 0 bluetooth 499712 6 btrtl,btintel,btbcm,ath3k,btusb media 32768 2 uvcvideo,videodev memstick 16384 1 rtsx_usb_ms snd_pcm 90112 9 snd_hda_intel,snd_hda_codec,snd_pcm_dmaengine,snd_hda_core,snd_soc_rt5640,snd_hda_codec_hdmi,snd_soc_core cfg80211 516096 4 mac80211,ath9k,ath,ath9k_common mii 16384 1 r8169 battery 20480 0 rfkill 20480 5 bluetooth,ideapad_laptop,cfg80211 wmi 16384 1 ideapad_laptop ac97_bus 16384 1 snd_soc_core i2c_hid 20480 0 hid 114688 3 i2c_hid,hid_generic,usbhid fjes 28672 0 elan_i2c 32768 0 i915 1204224 12 parport_pc 28672 0 parport 40960 2 parport_pc,ppdev video 36864 2 i915,ideapad_laptop mei_me 36864 0 spi_pxa2xx_platform 24576 0 8250_dw 16384 0 i2c_designware_platform 16384 0 drm_kms_helper 126976 3 amdgpu,radeon,i915 drm 294912 13 amdgpu,radeon,i915,ttm,drm_kms_helper snd_soc_sst_acpi 16384 0 intel_gtt 20480 1 i915 snd_soc_sst_match 16384 1 snd_soc_sst_acpi syscopyarea 16384 1 drm_kms_helper sysfillrect 16384 1 drm_kms_helper sysimgblt 16384 1 drm_kms_helper fb_sys_fops 16384 1 drm_kms_helper i2c_algo_bit 16384 3 amdgpu,radeon,i915 snd_timer 28672 1 snd_pcm snd 69632 22 snd_compress,snd_hda_intel,snd_hwdep,snd_hda_codec_conexant,snd_hda_codec,snd_timer,snd_hda_codec_hdmi,snd_hda_codec_generic,snd_soc_core,snd_pcm lpc_ich 24576 0 mei 86016 1 mei_me shpchp 32768 0 soc_button_array 16384 0 i2c_i801 24576 0 i2c_designware_core 20480 1 i2c_designware_platform i2c_smbus 16384 1 i2c_i801 soundcore 16384 1 snd tpm_tis 16384 0 tpm_tis_core 20480 1 tpm_tis tpm 36864 2 tpm_tis,tpm_tis_core ac 16384 0 button 16384 1 i915 sch_fq_codel 20480 5 ip_tables 28672 0 x_tables 28672 1 ip_tables ext4 528384 3 crc16 16384 2 bluetooth,ext4 jbd2 90112 1 ext4 fscrypto 24576 1 ext4 mbcache 16384 4 ext4 algif_skcipher 20480 0 af_alg 16384 1 algif_skcipher dm_crypt 28672 1 dm_mod 106496 12 dm_crypt sr_mod 24576 0 sd_mod 36864 3 cdrom 53248 1 sr_mod rtsx_usb_sdmmc 28672 0 rtsx_usb 20480 2 rtsx_usb_sdmmc,rtsx_usb_ms serio_raw 16384 0 atkbd 24576 0 libps2 16384 2 atkbd,psmouse crct10dif_pclmul 16384 0 crc32_pclmul 16384 0 crc32c_intel 24576 0 ghash_clmulni_intel 16384 0 ahci 36864 2 libahci 28672 1 ahci aesni_intel 167936 9 xhci_pci 16384 0 aes_x86_64 20480 1 aesni_intel lrw 16384 1 aesni_intel xhci_hcd 172032 1 xhci_pci gf128mul 16384 1 lrw glue_helper 16384 1 aesni_intel ablk_helper 16384 1 aesni_intel cryptd 20480 4 ablk_helper,ghash_clmulni_intel,aesni_intel libata 212992 2 ahci,libahci ehci_pci 16384 0 ehci_hcd 73728 1 ehci_pci usbcore 208896 9 uvcvideo,usbhid,ehci_hcd,xhci_pci,rtsx_usb,ath3k,btusb,xhci_hcd,ehci_pci scsi_mod 159744 3 sd_mod,libata,sr_mod usb_common 16384 1 usbcore i8042 28672 1 ideapad_laptop serio 20480 6 serio_raw,atkbd,psmouse,i8042 sdhci_acpi 16384 0 sdhci 40960 1 sdhci_acpi led_class 16384 4 rtsx_usb_sdmmc,sdhci,input_leds,ath9k mmc_core 122880 3 rtsx_usb_sdmmc,sdhci,sdhci_acpi -- You are receiving this mail because: You are the assignee for the bug.

1 16

[Bug 29445] New: Linux 2.6.34 kernel Radeon KMS driver freezes my computer sometimes
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=29445 Summary: Linux 2.6.34 kernel Radeon KMS driver freezes my computer sometimes 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: 0453411800(a)netti.fi Created an attachment (id=37682) --> (https://bugs.freedesktop.org/attachment.cgi?id=37682) /var/log/dmesg I use the kernel radeon driver with a Radeon Mobility R300 on a Toshiba laptop. The driver in 2.6.32 works fine and also the non-KMS driver in 2.6.34. However, when I enable the KMS driver (and disable the framebuffer drivers) in the 2.6.34 kernel, my computer freezes after a while of using X. If I don't start X the new KMS driver works fine. The outputs of dmesg, Xorg.0.log, and glxinfo are attached separately. In the case when I collected the above output, the bug manifested when I changed back to the virtual desktop of a running audio application (foobar2000 under wine). Access to the USB port with an external hard disk died at that moment. Usually the entire computer freezes (including keyboard, mouse, etc), but sometimes the bug seems to just disable the USB system. It only happens when the KMS driver is active so I file the bug here and not at the USB system or elsewhere. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.

1 17

[Bug 99967] RX 480 sclk clock speed lowers when under load
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=99967 Bug ID: 99967 Summary: RX 480 sclk clock speed lowers when under load Product: DRI Version: unspecified Hardware: Other OS: All Status: NEW Severity: normal Priority: medium Component: DRM/AMDgpu Assignee: dri-devel(a)lists.freedesktop.org Reporter: haagch(a)frickel.club Created attachment 129917 --> https://bugs.freedesktop.org/attachment.cgi?id=129917&action=edit screenshot with echo manual > power_dpm_force_performance_level My GPU is the factory overclocked XFX Radeon RX 480 XXX OC, this might have something to do with it. I noticed this on agd5d/drm-next-4.12-wip and found similar behavior on 4.10, 4.9 and 4.8. It's even affected even with echo manual > /sys/class/drm/card0/device/power_dpm_force_performance_level I've made a screenshot of radeon-profile on linux 4.8.14 and annotated it. Steps I took: echo manual > /sys/class/drm/card0/device/power_dpm_force_performance_level echo 7 > /sys/class/drm/card0/device/pp_dpm_sclk then started unigine-heaven, closed it, waited a couple of seconds, started furmark, closed it, waited a couple of seconds and then ran another echo 7 > /sys/class/drm/card0/device/pp_dpm_sclk When the GPU is "relatively" idle (just displaying the desktop with a browser, etc.) this doesn't happen. I can echo any number in /sys/class/drm/card0/device/pp_dpm_sclk and it sticks. But when I start applications that put some stress on the GPU, the sclk clock lowers - and stays on a lower level even when the load is gone, until another number is echo'ed into /sys/class/drm/card0/device/pp_dpm_sclk -- You are receiving this mail because: You are the assignee for the bug.

1 4

[Bug 29217] New: After pm-suspend the second monitor shows garbled output on evergreen card (kms)
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=29217 Summary: After pm-suspend the second monitor shows garbled output on evergreen card (kms) Product: DRI Version: DRI CVS Platform: x86-64 (AMD64) OS/Version: Linux (All) Status: NEW Severity: normal Priority: medium Component: DRM/Radeon AssignedTo: dri-devel(a)lists.freedesktop.org ReportedBy: bugs.xorg(a)boris64.net Created an attachment (id=37311) --> (https://bugs.freedesktop.org/attachment.cgi?id=37311) digicam picture of both monitors After resuming a previous (via pm-suspend) suspended system the second monitor only shows a garbled picture. Running xrandr to switch resolution seems to work, but the picture still ist truncated. This is a kms/multihead configuration. Used software: Kernel-2.6.35-rc5 latest xf86-video-ati from git latest libdrm from git latest mesa from git -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.

1 14

[Bug 99907] linux-firmware 2017-02-17 update causes varying breaks in AMDGPU for recent cards
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=99907 Bug ID: 99907 Summary: linux-firmware 2017-02-17 update causes varying breaks in AMDGPU for recent cards Product: DRI Version: unspecified Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: normal Priority: medium Component: DRM/AMDgpu Assignee: dri-devel(a)lists.freedesktop.org Reporter: saunders.52(a)wright.edu Currently on Arch Linux after they shipped an update to the linux-firmware set (20170217.12987ca-1), there's been reports of various issues ranging from power management failing to in my case (AMD Radeon RX 460) Xorg failing to work at all (it either blinks and goes back to a frozen VT as the GPU hangs, or the GPU hangs on a full-screen corruption of some kind.) This is broken on both kernel 4.9.11 and 4.10 in my testing, on Xorg 1.19.1. The system still responds to SSH connections, but fails to shutdown properly if attempted over that. Tracker link: https://bugs.archlinux.org/task/53042 I've traced it back to a specific commit to linux-firmware, 7a110b85a46d7f884f4ac712ff52e02ed57234bd, https://git.kernel.org/cgit/linux/kernel/git/firmware/linux-firmware.git/co…, pushed to the git repo on 2-17-17, which updates a large subset of the firmware images used by AMDGPU. Seeing as how this is a binary file set, I'm really not sure how to proceed from here in testing it to give any more useful information here. Apologies if this is the wrong place to report a firmware issue, but I was unsure where to file it otherwise. -- You are receiving this mail because: You are the assignee for the bug.

1 24

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

dri-devel July 2017