dri-devel September 2014

dri-devel@lists.freedesktop.org

173 participants
1045 discussions

[Bug 82055] New: [HAWAII] Running some programs, when HW acceleration is on, causes X to spike in CPU usage → unresponsive desktop
by bugzilla-daemon＠freedesktop.org 25 Nov '14

25 Nov '14

https://bugs.freedesktop.org/show_bug.cgi?id=82055 Priority: medium Bug ID: 82055 Assignee: dri-devel(a)lists.freedesktop.org Summary: [HAWAII] Running some programs, when HW acceleration is on, causes X to spike in CPU usage → unresponsive desktop Severity: normal Classification: Unclassified OS: Linux (All) Reporter: kai(a)dev.carbon-project.org Hardware: x86-64 (AMD64) Status: NEW Version: git Component: Drivers/Gallium/radeonsi Product: Mesa When running certain programs (eg. MediathekView) or watching recorded broadcasts on Twitch, X starts going up in CPU usage and the desktop becomes unresponsive, until you kill the stream or the program has finished its draw operations (can take several seconds). Interestingly enough, YouTube videos are not affected. In both cases I had HW video acceleration on (through settings in /etc/adobe/mms.conf), without HW acceleration the plugin is just consuming ridiculous amounts of CPU cycles. The problem with Twitch is independent off chosen video quality. My desktop environment is KDE 4.13.3 with desktop effects enabled (compositing type=OpenGL 3.1, render target=native), disabling them has no effect on this issue. I haven't seen these issues with my previous HD7850 (also using Glamor), therefore I think this is separate to bug 68524. My stack is (base: Debian Testing): GPU: Hawaii PRO [Radeon R9 290] (ChipID = 0x67b1) Linux: Git:~agdf5/linux:drm-next-3.17-rebased-on-fixes:fa053e7263 (calls itself 3.16-rc6) + attachment 93015 [details] [review] libdrm: Git:master/libdrm-2.4.56 LLVM: SVN:trunk/r214546 (3.6 snapshot) libclc: Git:master/5b48f170c8 Mesa: Git:master/e41cc45361 DDX: Git:master/4b5060f357 + Patch from http://lists.x.org/archives/xorg-driver-ati/2014-July/026517.html X: 2:1.16.0-2 (1.16.0) Let me know, if you need further information. -- You are receiving this mail because: You are the assignee for the bug.

1 15

[Bug 82667] New: "Distance" game closed alpha: Changing shadow settings segfaults
by bugzilla-daemon＠freedesktop.org 25 Nov '14

25 Nov '14

https://bugs.freedesktop.org/show_bug.cgi?id=82667 Priority: medium Bug ID: 82667 Assignee: dri-devel(a)lists.freedesktop.org Summary: "Distance" game closed alpha: Changing shadow settings segfaults Severity: normal Classification: Unclassified OS: Linux (All) Reporter: haagch(a)frickel.club Hardware: Other Status: NEW Version: git Component: Drivers/Gallium/radeonsi Product: Mesa Created attachment 104682 --> https://bugs.freedesktop.org/attachment.cgi?id=104682&action=edit full backtrace For people who are part of the Closed Alpha and want to test: It doesn't happen when changing the shadow levels between active levels. But when changing shadows from off to any level or from any level to off, this segfault happens every time. 00:02.0 VGA compatible controller: Intel Corporation 3rd Gen Core processor Graphics Controller (rev 09) 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Wimbledon XT [Radeon HD 7970M] (rev ff) It does not crash when I run it on intel. It also does not crash when I run it on llvmpipe. So it is possibly related to PRIME rather than radeonsi, unfortunately I can't test without PRIME. mesa git, linux 3.16, launched in steam with: DRI_PRIME=1 GALLIUM_HUD="fps,VRAM-usage+GTT-usage" %command% It happens with both dri3 offloading and with LIBGL_DRI3_DISABLE=1 -- You are receiving this mail because: You are the assignee for the bug.

1 4

[Bug 31532] New: rv670 AGP gart + gallium - GPU lockups. PCIE gart runs but stalls.
by bugzilla-daemon＠freedesktop.org 19 Nov '14

19 Nov '14

https://bugs.freedesktop.org/show_bug.cgi?id=31532 Summary: rv670 AGP gart + gallium - GPU lockups. PCIE gart runs but stalls. Product: Mesa Version: git Platform: Other OS/Version: All Status: NEW Severity: normal Priority: medium Component: Drivers/Gallium/r600 AssignedTo: dri-devel(a)lists.freedesktop.org ReportedBy: lists(a)andyfurniss.entadsl.com Running d-r-t kernels, xserver 1.9 and git mesa, ddx, lib drm. Any non trivial mesa demo with r600g will cause a gpu lockup/reset unless I use PCIE gart and turn off writebacks. Tiling on/off makes no difference. Not a regression AFAICT, this box was retired a while back, before 600g was really usable, so I don't have and have been unable to find a time when it ever worked. Classic KMS + AGP gart works OK. Both Classic KMS and Gallium with agpmode=-1 have stalling problems. Classic runs demos fine, but will stall for 1/2 sec on some games and some levels eg. openarena anholt is OK but other levels will stutter a bit. These do not show with latencytop. Classic + UMS does not stall. Gallium has far worse stalling problems than classic. Some mesa demos will stall, gearbox shows the most - up to a second when running sometimes more at start. Latency top will show gallium stalls - radeon_fence_wait often shows 488ms but never more. Long stalls such as when starting games/demos seem to be in - radeon_cs_ioctl I have seen 3000ms for games and 1000ms for demos. Openarena anholt demo 600g behaves strangely - it will stall so much while loading and rendering the first few frames that this takes minutes. After this the demo will run at full speed to completion (sometimes stalls again midway). Benchmark results have shown it took 8 seconds to render one of the early frames - 840 frames 45.0 seconds 18.7 fps 7.0/53.5/8004.0/23.7 ms. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.

1 7

[PATCH 0/2] drm/exynos: use drm generic mmap interface
by Inki Dae 19 Nov '14

19 Nov '14

This patch set removes unnecessary DRM_EXYNOS_GEM_MAP_OFFSET interface which isn't used anymore and also uses drm generic mmap interface instead of a mmap interface specific to Exynos drm. So this patch set removes a existing mmap interface and relevant codes specific to Exynos drm. Inki Dae (2): drm/exynos: remove DRM_EXYNOS_GEM_MAP_OFFSET ioctl drm/exynos: use drm generic mmap interface drivers/gpu/drm/exynos/exynos_drm_drv.c | 28 --------- drivers/gpu/drm/exynos/exynos_drm_drv.h | 1 - drivers/gpu/drm/exynos/exynos_drm_gem.c | 101 +++++-------------------------- drivers/gpu/drm/exynos/exynos_drm_gem.h | 14 ----- include/uapi/drm/exynos_drm.h | 40 ------------ 5 files changed, 14 insertions(+), 170 deletions(-) -- 1.7.9.5

5 15

[Bug 83416] New: [radeonsi] Serious Sam 3 lockup during its start
by bugzilla-daemon＠freedesktop.org 18 Nov '14

18 Nov '14

https://bugs.freedesktop.org/show_bug.cgi?id=83416 Priority: medium Bug ID: 83416 Assignee: dri-devel(a)lists.freedesktop.org Summary: [radeonsi] Serious Sam 3 lockup during its start Severity: major Classification: Unclassified OS: Linux (All) Reporter: lordheavym(a)gmail.com Hardware: x86-64 (AMD64) Status: NEW Version: git Component: Drivers/Gallium/radeonsi Product: Mesa Created attachment 105638 --> https://bugs.freedesktop.org/attachment.cgi?id=105638&action=edit kernel.log file with kernel 3.17rc3 * Tested with both kernel 3.16.1 and kernel 3.17rc3, with and without hyperz * OpenGL renderer string: Gallium 0.4 on AMD PITCAIRN * OpenGL core profile version string: 3.3 (Core Profile) Mesa 10.4.0-devel (git-021e84f) I can reproduce the lockup with the trace: http://pkgbuild.com/~lcarlier/trace/Sam3.tar.xz -- You are receiving this mail because: You are the assignee for the bug.

1 20

[Bug 83611] New: Kernel NULL pointer dereference when using tlp on a laptop with AMD video card.
by bugzilla-daemon＠bugzilla.kernel.org 18 Nov '14

18 Nov '14

https://bugzilla.kernel.org/show_bug.cgi?id=83611 Bug ID: 83611 Summary: Kernel NULL pointer dereference when using tlp on a laptop with AMD video card. Product: Drivers Version: 2.5 Kernel Version: 3.16.1 Hardware: x86-64 OS: Linux Tree: Mainline Status: NEW Severity: high Priority: P1 Component: Video(DRI - non Intel) Assignee: drivers_video-dri(a)kernel-bugs.osdl.org Reporter: yshuiv7(a)gmail.com Regression: No relevant dmesg: ACPI: \_SB_.PCI0.LPCB.EC0_.ECRD: 1 arguments were passed to a non-method ACPI object (RegionField) (20140424/nsarguments-230) ACPI: \_SB_.PCI0.LPCB.EC0_.ECRD: 1 arguments were passed to a non-method ACPI object (RegionField) (20140424/nsarguments-230) input: ThinkPad Extra Buttons as /devices/platform/thinkpad_acpi/input/input14 ATOM BIOS: Lenovo/Compal [drm] GPU not posted. posting now... radeon 0000:05:00.0: VRAM: 2048M 0x0000000000000000 - 0x000000007FFFFFFF (2048M used) radeon 0000:05:00.0: GTT: 1024M 0x0000000080000000 - 0x00000000BFFFFFFF [drm] Detected VRAM RAM=2048M, BAR=256M [drm] RAM width 128bits DDR [TTM] Zone kernel: Available graphics memory: 4049972 kiB [TTM] Zone dma32: Available graphics memory: 2097152 kiB [TTM] Initializing pool allocator [TTM] Initializing DMA pool allocator [drm] radeon: 2048M of VRAM memory ready [drm] radeon: 1024M of GTT memory ready. [drm] Loading VERDE Microcode [drm] radeon/VERDE_mc2.bin: 31500 bytes [drm] Internal thermal controller without fan control [drm] probing gen 2 caps for device 8086:9c18 = 5323c42/0 [drm] radeon: dpm initialized [drm] GART: num cpu pages 262144, num gpu pages 262144 [drm] probing gen 2 caps for device 8086:9c18 = 5323c42/0 [drm] PCIE gen 2 link speeds already enabled [drm] PCIE GART of 1024M enabled (table at 0x0000000000276000). radeon 0000:05:00.0: WB enabled radeon 0000:05:00.0: fence driver on ring 0 use gpu addr 0x0000000080000c00 and cpu addr 0xffff88024d04fc00 radeon 0000:05:00.0: fence driver on ring 1 use gpu addr 0x0000000080000c04 and cpu addr 0xffff88024d04fc04 radeon 0000:05:00.0: fence driver on ring 2 use gpu addr 0x0000000080000c08 and cpu addr 0xffff88024d04fc08 radeon 0000:05:00.0: fence driver on ring 3 use gpu addr 0x0000000080000c0c and cpu addr 0xffff88024d04fc0c radeon 0000:05:00.0: fence driver on ring 4 use gpu addr 0x0000000080000c10 and cpu addr 0xffff88024d04fc10 radeon 0000:05:00.0: fence driver on ring 5 use gpu addr 0x0000000000075a18 and cpu addr 0xffffc900121b5a18 [drm] Supports vblank timestamp caching Rev 2 (21.10.2013). [drm] Driver supports precise vblank timestamp query. radeon 0000:05:00.0: irq 68 for MSI/MSI-X radeon 0000:05:00.0: radeon: using MSI. [drm] radeon: irq initialized. 32]: wlp4s0: soliciting a DHCP lease BUG: unable to handle kernel NULL pointer dereference at 0000000000000080 IP: [<ffffffffa060aefb>] dce6_bandwidth_update+0x4b/0x110 [radeon] PGD 252511067 PUD 24ee99067 PMD 0 Oops: 0000 [#1] PREEMPT SMP Modules linked in: ses enclosure ecb btusb uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_core v4l2_common uas bluetooth videodev thinkpad_acpi nvram media usb_storage 6lowpan_iphc crc16 intel_rapl joydev mousedev x86_pkg_temp_thermal intel_powerclamp kvm_intel kvm crct10dif_pclmul crc32_pclmul ghash_clmulni_intel aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd arc4 iTCO_wdt iwlmvm mac80211 iTCO_vendor_support i915(+) radeon(+) mac_hid microcode serio_raw psmouse evdev pcspkr ttm iwlwifi dw_dmac dw_dmac_core drm_kms_helper thermal battery cfg80211 gpio_lynxpoint drm ideapad_laptop r8169 rtsx_pci_ms memstick sparse_keymap rfkill mii fan 8250_dw video mei_me mei ac i2c_hid spi_pxa2xx_platform i2c_designware_platform intel_gtt i2c_i801 i2c_algo_bit i2c_designware_core i2c_core button shpchp lpc_ich snd_hda_codec_realtek snd_hda_codec_generic snd_hda_intel snd_hda_controller snd_hda_codec snd_hwdep snd_pcm snd_timer snd soundcore processor coretemp hwmon acpi_call(O) btrfs xor hid_generic usbhid hid raid6_pq sd_mod crc_t10dif crct10dif_common rtsx_pci_sdmmc atkbd libps2 ahci libahci crc32c_intel libata scsi_mod ehci_pci ehci_hcd xhci_hcd usbcore rtsx_pci usb_common i8042 serio sdhci_acpi sdhci led_class mmc_core CPU: 0 PID: 407 Comm: tlp Tainted: G O 3.16.1-1-ARCH #1 Hardware name: LENOVO 20347/Lenovo Y40-70, BIOS 99CN24WW(V1.07) 07/28/2014 task: ffff88024d1028c0 ti: ffff88024ecb8000 task.ti: ffff88024ecb8000 RIP: 0010:[<ffffffffa060aefb>] [<ffffffffa060aefb>] dce6_bandwidth_update+0x4b/0x110 [radeon] RSP: 0018:ffff88024ecbbdf0 EFLAGS: 00010246 RAX: ffff88024ef68498 RBX: ffff88024ef68000 RCX: ffff88024ef684c8 RDX: 0000000000000000 RSI: 00000000000004b0 RDI: ffff88024ef68000 RBP: ffff88024ecbbe20 R08: ffff88024d2699e6 R09: 00000000000004b0 R10: 0000000000000005 R11: ffffea00026a1500 R12: ffff88024ef68000 R13: 0000000000000000 R14: ffff88024ef69738 R15: ffff88024ef69048 FS: 00007f869e36c700(0000) GS:ffff88025f200000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 0000000000000080 CR3: 000000025256b000 CR4: 00000000001407f0 Stack: 000000008830c49b ffff88024ef68000 ffff88024ef69710 0000000000000000 ffff88024ef69738 ffff88024ef69048 ffff88024ecbbe60 ffffffffa05e824e ffff88024ecbbf08 ffff88024ef68000 000000000000000c ffff88009acd44b0 Call Trace: [<ffffffffa05e824e>] radeon_pm_compute_clocks+0x62e/0x8f0 [radeon] [<ffffffffa05e8ad7>] radeon_set_dpm_state+0x87/0x100 [radeon] [<ffffffff8139f978>] dev_attr_store+0x18/0x30 [<ffffffff812384da>] sysfs_kf_write+0x3a/0x50 [<ffffffff81237a4e>] kernfs_fop_write+0xee/0x180 [<ffffffff811c1f87>] vfs_write+0xb7/0x200 [<ffffffff811c2bf9>] SyS_write+0x59/0xd0 [<ffffffff811df9c2>] ? __close_fd+0x82/0xa0 [<ffffffff81530be9>] system_call_fastpath+0x16/0x1b Code: 94 24 68 20 00 00 85 d2 0f 8e d1 00 00 00 83 ea 01 49 8d 84 24 98 04 00 00 45 31 ed 49 8d 8c d4 a0 04 00 00 0f 1f 40 00 48 8b 10 <80> ba 80 00 00 00 01 41 83 dd ff 48 83 c0 08 48 39 c8 75 e9 49 RIP [<ffffffffa060aefb>] dce6_bandwidth_update+0x4b/0x110 [radeon] RSP <ffff88024ecbbdf0> CR2: 0000000000000080 ---[ end trace 7264449ae2a0d879 ]--- -- You are receiving this mail because: You are watching the assignee of the bug.

1 6

[Bug 64376] New: radeon fatal error during GPU init (Radeon 5850, KVM GPU passthrough)
by bugzilla-daemon＠freedesktop.org 18 Nov '14

18 Nov '14

https://bugs.freedesktop.org/show_bug.cgi?id=64376 Priority: medium Bug ID: 64376 Assignee: dri-devel(a)lists.freedesktop.org Summary: radeon fatal error during GPU init (Radeon 5850, KVM GPU passthrough) Severity: normal Classification: Unclassified OS: Linux (All) Reporter: luke-jr+freedesktopbugs(a)utopios.org Hardware: Other Status: NEW Version: XOrg CVS Component: DRM/Radeon Product: DRI Booting on a KVM instance tested to work fine with fglrx: [ 3.771157] [drm] Initialized drm 1.1.0 20060810 [ 4.006077] [drm] radeon kernel modesetting enabled. [ 4.006350] ACPI: PCI Interrupt Link [LNKA] enabled at IRQ 11 [ 4.006714] [drm] initializing kernel modesetting (CYPRESS 0x1002:0x6899 0x1458:0x21E4). [ 4.006723] [drm] register mmio base: 0xFEB80000 [ 4.006724] [drm] register mmio size: 131072 [ 4.006785] radeon 0000:00:05.0: Expecting atombios for evergreen GPU [ 4.006786] radeon 0000:00:05.0: Fatal error during GPU init [ 4.006789] [drm] radeon: finishing device. [ 4.006792] [TTM] Memory type 2 has not been initialized [ 4.008077] radeon: probe of 0000:00:05.0 failed with error -22 -- You are receiving this mail because: You are the assignee for the bug.

1 4

[Bug 83500] New: si_dma_copy_tile causes GPU hangs
by bugzilla-daemon＠freedesktop.org 17 Nov '14

17 Nov '14

https://bugs.freedesktop.org/show_bug.cgi?id=83500 Priority: medium Bug ID: 83500 Assignee: dri-devel(a)lists.freedesktop.org Summary: si_dma_copy_tile causes GPU hangs Severity: normal Classification: Unclassified OS: Linux (All) Reporter: greg(a)chown.ath.cx Hardware: x86-64 (AMD64) Status: NEW Version: git Component: Drivers/Gallium/radeonsi Product: Mesa Created attachment 105745 --> https://bugs.freedesktop.org/attachment.cgi?id=105745&action=edit Workaround Async DMA linear to tiled copies are causing GPU hangs in some cases. On Cape Verde, I can easily triggers this as described in [1]. The game Brutal Legend also triggers similar hangs when it streams assets while gameplay. Disabling usage of this function and using the resource_copy_region fallback instead fixes all hangs. The attached patch does that. [1] https://bugs.freedesktop.org/show_bug.cgi?id=79980#c124 -- You are receiving this mail because: You are the assignee for the bug.

1 10

[Bug 29226] New: on r600 3d applications are rendered too bright
by bugzilla-daemon＠freedesktop.org 11 Nov '14

11 Nov '14

https://bugs.freedesktop.org/show_bug.cgi?id=29226 Summary: on r600 3d applications are rendered too bright Product: DRI Version: unspecified Platform: x86-64 (AMD64) OS/Version: All Status: NEW Severity: normal Priority: medium Component: DRM/Radeon AssignedTo: dri-devel(a)lists.freedesktop.org ReportedBy: hramrach(a)centrum.cz I am running r600 card with 2.6.34 kernel and Mesa 7.8.2. ATI Technologies Inc RV710 [Radeon HD 4350] Since switching to the card I noticed rendering issues the most prominent being incorrect colors. The colors of many objects seem overly bright and lack saturation, the lighted areas show large patches of white or nearly white color. The UI which is 2d/unlit looks OK and so do glxgears. This does not happen on r300 card or Intel card. I tried running planeshift with software rendering and the character preview after logging in looked much better. However, after running with software renderer the issue is gone. This might be because planeshift calculates some lighting information during runtime and it was changed by the calculations performed on the software renderer. Planeshift can be found at http://www.planeshift.it/download.html I am not sure what the exact issue is. So far I was unable to reproduce it visibly with a trivial program. However, it also happens when running a 3D program through wine. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.

1 19

[Bug 79659] New: R9 270X lockup with unigine valley since radeonsi: enable ARB_sample_shading
by bugzilla-daemon＠freedesktop.org 11 Nov '14

11 Nov '14

https://bugs.freedesktop.org/show_bug.cgi?id=79659 Priority: medium Bug ID: 79659 Assignee: dri-devel(a)lists.freedesktop.org Summary: R9 270X lockup with unigine valley since radeonsi: enable ARB_sample_shading Severity: normal Classification: Unclassified OS: Linux (All) Reporter: adf.lists(a)gmail.com Hardware: x86-64 (AMD64) Status: NEW Version: git Component: Drivers/Gallium/radeonsi Product: Mesa R9 270X since - commit f98a7d89be5d307c7a80fbde028a610f4377c3b9 Author: Marek Olšák <marek.olsak(a)amd.com> Date: Wed May 7 13:15:41 2014 +0200 radeonsi: enable ARB_sample_shading unigine valley run like - vblank_mode=0 MESA_GLSL_VERSION_OVERRIDE=330 MESA_GL_VERSION_OVERRIDE=3.3 ./valley will gpu lock then hard lock if I don't sysrq sub quickly enough Jun 4 21:59:31 ph4 kernel: radeon 0000:01:00.0: ring 3 stalled for more than 10003msec Jun 4 21:59:31 ph4 kernel: radeon 0000:01:00.0: GPU lockup (waiting for 0x000000000000d8a9 last fence id 0x000000000000d8a7 on ring 3) Jun 4 21:59:31 ph4 kernel: radeon 0000:01:00.0: failed to get a new IB (-35) Jun 4 21:59:32 ph4 kernel: radeon 0000:01:00.0: Saved 1677 dwords of commands on ring 0. Jun 4 21:59:32 ph4 kernel: radeon 0000:01:00.0: GPU softreset: 0x0000004D Jun 4 21:59:32 ph4 kernel: radeon 0000:01:00.0: GRBM_STATUS = 0xF7D20028 Jun 4 21:59:32 ph4 kernel: radeon 0000:01:00.0: GRBM_STATUS_SE0 = 0xEC400000 Jun 4 21:59:32 ph4 kernel: radeon 0000:01:00.0: GRBM_STATUS_SE1 = 0xEDC00000 Jun 4 21:59:32 ph4 kernel: radeon 0000:01:00.0: SRBM_STATUS = 0x200400C0 Jun 4 21:59:32 ph4 kernel: radeon 0000:01:00.0: SRBM_STATUS2 = 0x00000000 Jun 4 21:59:32 ph4 kernel: radeon 0000:01:00.0: R_008674_CP_STALLED_STAT1 = 0x00000000 Jun 4 21:59:32 ph4 kernel: radeon 0000:01:00.0: R_008678_CP_STALLED_STAT2 = 0x40000000 Jun 4 21:59:32 ph4 kernel: radeon 0000:01:00.0: R_00867C_CP_BUSY_STAT = 0x00008006 Jun 4 21:59:32 ph4 kernel: radeon 0000:01:00.0: R_008680_CP_STAT = 0x80228647 Jun 4 21:59:32 ph4 kernel: radeon 0000:01:00.0: R_00D034_DMA_STATUS_REG = 0x44483106 Jun 4 21:59:32 ph4 kernel: radeon 0000:01:00.0: R_00D834_DMA_STATUS_REG = 0x44C83D57 Jun 4 21:59:32 ph4 kernel: radeon 0000:01:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x00000000 Jun 4 21:59:32 ph4 kernel: radeon 0000:01:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x00000000 Jun 4 21:59:33 ph4 kernel: radeon 0000:01:00.0: GRBM_SOFT_RESET=0x0000DDFF Jun 4 21:59:33 ph4 kernel: radeon 0000:01:00.0: SRBM_SOFT_RESET=0x00100100 Jun 4 21:59:33 ph4 kernel: radeon 0000:01:00.0: GRBM_STATUS = 0x00003028 Jun 4 21:59:33 ph4 kernel: radeon 0000:01:00.0: GRBM_STATUS_SE0 = 0x00000006 Jun 4 21:59:33 ph4 kernel: radeon 0000:01:00.0: GRBM_STATUS_SE1 = 0x00000006 Jun 4 21:59:33 ph4 kernel: radeon 0000:01:00.0: SRBM_STATUS = 0x200400C0 Jun 4 21:59:33 ph4 kernel: radeon 0000:01:00.0: SRBM_STATUS2 = 0x00000000 Jun 4 21:59:33 ph4 kernel: radeon 0000:01:00.0: R_008674_CP_STALLED_STAT1 = 0x00000000 Jun 4 21:59:33 ph4 kernel: radeon 0000:01:00.0: R_008678_CP_STALLED_STAT2 = 0x00000000 Jun 4 21:59:33 ph4 kernel: radeon 0000:01:00.0: R_00867C_CP_BUSY_STAT = 0x00000000 Jun 4 21:59:33 ph4 kernel: radeon 0000:01:00.0: R_008680_CP_STAT = 0x00000000 Jun 4 21:59:33 ph4 kernel: radeon 0000:01:00.0: R_00D034_DMA_STATUS_REG = 0x44C83D57 Jun 4 21:59:33 ph4 kernel: radeon 0000:01:00.0: R_00D834_DMA_STATUS_REG = 0x44C83D57 Jun 4 21:59:33 ph4 kernel: radeon 0000:01:00.0: GPU reset succeeded, trying to resume Jun 4 21:59:33 ph4 kernel: [drm] probing gen 2 caps for device 1022:9603 = 300d02/0 Jun 4 21:59:33 ph4 kernel: [drm] PCIE gen 2 link speeds already enabled Jun 4 21:59:33 ph4 kernel: [drm] PCIE GART of 1024M enabled (table at 0x0000000000276000). Jun 4 21:59:33 ph4 kernel: radeon 0000:01:00.0: WB enabled Jun 4 21:59:33 ph4 kernel: radeon 0000:01:00.0: fence driver on ring 0 use gpu addr 0x0000000080000c00 and cpu addr 0xffff8800cc194c00 Jun 4 21:59:33 ph4 kernel: radeon 0000:01:00.0: fence driver on ring 1 use gpu addr 0x0000000080000c04 and cpu addr 0xffff8800cc194c04 Jun 4 21:59:33 ph4 kernel: radeon 0000:01:00.0: fence driver on ring 2 use gpu addr 0x0000000080000c08 and cpu addr 0xffff8800cc194c08 Jun 4 21:59:33 ph4 kernel: radeon 0000:01:00.0: fence driver on ring 3 use gpu addr 0x0000000080000c0c and cpu addr 0xffff8800cc194c0c Jun 4 21:59:33 ph4 kernel: radeon 0000:01:00.0: fence driver on ring 4 use gpu addr 0x0000000080000c10 and cpu addr 0xffff8800cc194c10 Jun 4 21:59:33 ph4 kernel: radeon 0000:01:00.0: fence driver on ring 5 use gpu addr 0x0000000000075a18 and cpu addr 0xffffc900105b5a18 Jun 4 21:59:33 ph4 kernel: [drm] ring test on 0 succeeded in 3 usecs Jun 4 21:59:33 ph4 kernel: [drm] ring test on 1 succeeded in 1 usecs Jun 4 21:59:33 ph4 kernel: [drm] ring test on 2 succeeded in 1 usecs Jun 4 21:59:33 ph4 kernel: [drm] ring test on 3 succeeded in 2 usecs Jun 4 21:59:33 ph4 kernel: [drm] ring test on 4 succeeded in 1 usecs Jun 4 21:59:33 ph4 kernel: [drm] ring test on 5 succeeded in 2 usecs Jun 4 21:59:33 ph4 kernel: [drm] UVD initialized successfully. Jun 4 21:59:43 ph4 kernel: radeon 0000:01:00.0: ring 0 stalled for more than 10000msec Jun 4 21:59:43 ph4 kernel: radeon 0000:01:00.0: GPU lockup (waiting for 0x000000000002dc5a last fence id 0x000000000002dc3f on ring 0) Jun 4 21:59:43 ph4 kernel: [drm:r600_ib_test] *ERROR* radeon: fence wait failed (-35). Jun 4 21:59:43 ph4 kernel: [drm:radeon_ib_ring_tests] *ERROR* radeon: failed testing IB on GFX ring (-35). Jun 4 21:59:43 ph4 kernel: radeon 0000:01:00.0: ib ring test failed (-35). Jun 4 21:59:44 ph4 kernel: radeon 0000:01:00.0: GPU softreset: 0x00000048 Jun 4 21:59:44 ph4 kernel: radeon 0000:01:00.0: GRBM_STATUS = 0xA0003028 Jun 4 21:59:44 ph4 kernel: radeon 0000:01:00.0: GRBM_STATUS_SE0 = 0x00000006 Jun 4 21:59:44 ph4 kernel: radeon 0000:01:00.0: GRBM_STATUS_SE1 = 0x00000006 Jun 4 21:59:44 ph4 kernel: radeon 0000:01:00.0: SRBM_STATUS = 0x200400C0 Jun 4 21:59:44 ph4 kernel: radeon 0000:01:00.0: SRBM_STATUS2 = 0x00000000 Jun 4 21:59:44 ph4 kernel: radeon 0000:01:00.0: R_008674_CP_STALLED_STAT1 = 0x00000000 Jun 4 21:59:44 ph4 kernel: radeon 0000:01:00.0: R_008678_CP_STALLED_STAT2 = 0x00010000 Jun 4 21:59:44 ph4 kernel: radeon 0000:01:00.0: R_00867C_CP_BUSY_STAT = 0x00400002 Jun 4 21:59:44 ph4 kernel: radeon 0000:01:00.0: R_008680_CP_STAT = 0x84010243 Jun 4 21:59:44 ph4 kernel: radeon 0000:01:00.0: R_00D034_DMA_STATUS_REG = 0x44C83D57 Jun 4 21:59:44 ph4 kernel: radeon 0000:01:00.0: R_00D834_DMA_STATUS_REG = 0x44C83D57 Jun 4 21:59:44 ph4 kernel: radeon 0000:01:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x00000000 Jun 4 21:59:44 ph4 kernel: radeon 0000:01:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x00000000 Jun 4 21:59:44 ph4 kernel: SysRq : Emergency Sync Jun 4 21:59:44 ph4 kernel: Emergency Sync complete Jun 4 21:59:44 ph4 kernel: radeon 0000:01:00.0: GRBM_SOFT_RESET=0x0000DDFF Jun 4 21:59:44 ph4 kernel: radeon 0000:01:00.0: SRBM_SOFT_RESET=0x00000100 Jun 4 21:59:44 ph4 kernel: radeon 0000:01:00.0: GRBM_STATUS = 0x00003028 Jun 4 21:59:44 ph4 kernel: radeon 0000:01:00.0: GRBM_STATUS_SE0 = 0x00000006 Jun 4 21:59:44 ph4 kernel: radeon 0000:01:00.0: GRBM_STATUS_SE1 = 0x00000006 Jun 4 21:59:44 ph4 kernel: radeon 0000:01:00.0: SRBM_STATUS = 0x200400C0 Jun 4 21:59:44 ph4 kernel: radeon 0000:01:00.0: SRBM_STATUS2 = 0x00000000 Jun 4 21:59:44 ph4 kernel: radeon 0000:01:00.0: R_008674_CP_STALLED_STAT1 = 0x00000000 Jun 4 21:59:44 ph4 kernel: radeon 0000:01:00.0: R_008678_CP_STALLED_STAT2 = 0x00000000 Jun 4 21:59:44 ph4 kernel: radeon 0000:01:00.0: R_00867C_CP_BUSY_STAT = 0x00000000 Jun 4 21:59:44 ph4 kernel: radeon 0000:01:00.0: R_008680_CP_STAT = 0x00000000 Jun 4 21:59:44 ph4 kernel: radeon 0000:01:00.0: R_00D034_DMA_STATUS_REG = 0x44C83D57 Jun 4 21:59:44 ph4 kernel: radeon 0000:01:00.0: R_00D834_DMA_STATUS_REG = 0x44C83D57 Jun 4 21:59:44 ph4 kernel: radeon 0000:01:00.0: GPU reset succeeded, trying to resume -- You are receiving this mail because: You are the assignee for the bug.

1 19

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

dri-devel September 2014