dri-devel May 2015

dri-devel@lists.freedesktop.org

191 participants
1132 discussions

[Bug 90378] GPU lockups in Left 4 Dead 2
by bugzilla-daemon＠freedesktop.org 01 Aug '15

01 Aug '15

https://bugs.freedesktop.org/show_bug.cgi?id=90378 Bug ID: 90378 Summary: GPU lockups in Left 4 Dead 2 Product: Mesa Version: git Hardware: Other OS: All Status: NEW Severity: normal Priority: medium Component: Drivers/Gallium/radeonsi Assignee: dri-devel(a)lists.freedesktop.org Reporter: daniel(a)constexpr.org QA Contact: dri-devel(a)lists.freedesktop.org Created attachment 115653 --> https://bugs.freedesktop.org/attachment.cgi?id=115653&action=edit dmesg output While playing L4D2 today I got a lot of GPU lockups. While the lockups seem to happen randomly, they are fairly easy to reproduce in the third chapter (The Mall) of the Dead Center campaign. I recorded an apitrace while encountering 3 lockups and there seem to be at least a couple of lockups each time I retrace it: http://constexpr.org/tmp/L4D2-radeonsi.trace.xz (507 MiB) At least driver was able to successfully reset the GPU each time. There also seem to be some infrequent rendering glitches. Probably related to bug 89228, and possibly bug 90217, bug 90284 and/or bug 89954 (all reports of lockups with Source engine games). GPU; Radeon HD 7950 (TAHITI) Mesa 10.6.0-devel (git-3bdbc1e) LLVM r236436 Linux 4.0.1-gentoo The above logs and apitrace were recorded with unsafe-fp-math enbled (see bug 89069 comment 34) but the lockups also happen without it. I also noticed some VM fault messages in dmesg while running L4D2 without unsafe-fp-math. -- You are receiving this mail because: You are the assignee for the bug.

1 14

[Bug 88978] [bisected] [SI Scheduler] Graphical corruption in Dota 2
by bugzilla-daemon＠freedesktop.org 01 Aug '15

01 Aug '15

https://bugs.freedesktop.org/show_bug.cgi?id=88978 Bug ID: 88978 Summary: [bisected] [SI Scheduler] Graphical corruption in Dota 2 Product: Mesa Version: git Hardware: All OS: All Status: NEW Severity: normal Priority: medium Component: Drivers/Gallium/radeonsi Assignee: dri-devel(a)lists.freedesktop.org Reporter: commendsarnex(a)gmail.com QA Contact: dri-devel(a)lists.freedesktop.org CC: tstellar(a)gmail.com Hi guys. If I use LLVM git, I get these graphical glitches in Dota 2 native. https://i.imgur.com/I4vyWFt.jpg The bug has been bisected to LLVM: 51a3c27d6e0c66cc8d2d1da8e9205fec7b74ca5c R600/SI: Define a schedule model and enable the generic machine scheduler I'm using Mesa git, Kernel 3.18.5 and Linux Mint. Thanks alot, sarnex -- You are receiving this mail because: You are the assignee for the bug.

1 21

[Bug 90484] LLVM >=r237140 causes gpu lockups Spec Ops: The Line
by bugzilla-daemon＠freedesktop.org 31 Jul '15

31 Jul '15

https://bugs.freedesktop.org/show_bug.cgi?id=90484 Bug ID: 90484 Summary: LLVM >=r237140 causes gpu lockups Spec Ops: The Line Product: Mesa Version: git Hardware: Other OS: All Status: NEW Severity: normal Priority: medium Component: Drivers/Gallium/radeonsi Assignee: dri-devel(a)lists.freedesktop.org Reporter: arek.rusi(a)gmail.com QA Contact: dri-devel(a)lists.freedesktop.org Created attachment 115840 --> https://bugs.freedesktop.org/attachment.cgi?id=115840&action=edit dmesg I can't even start gameplay, gpu lockups a few seconds after intro in game menu. cape verde first bad combo: llvm >=r237140 + mesa git llvm r237139 (or 3.6) + mesa git works really good. -- You are receiving this mail because: You are the assignee for the bug.

1 9

[Bug 83998] New: Oopses on R9270X using UVD since radeon/uvd: use PIPE_USAGE_STAGING for msg&fb buffers
by bugzilla-daemon＠freedesktop.org 30 Jul '15

30 Jul '15

https://bugs.freedesktop.org/show_bug.cgi?id=83998 Priority: medium Bug ID: 83998 Assignee: dri-devel(a)lists.freedesktop.org Summary: Oopses on R9270X using UVD since radeon/uvd: use PIPE_USAGE_STAGING for msg&fb buffers Severity: normal Classification: Unclassified OS: All Reporter: adf.lists(a)gmail.com Hardware: Other Status: NEW Version: git Component: Drivers/Gallium/radeonsi Product: Mesa R9270X Getting rareish Oopses and once oomkiller since - commit 6327b584155d040ae089e65fd6747186bdd9666b Author: Christian König <christian.koenig(a)amd.com> Date: Thu Sep 11 09:50:00 2014 +0200 radeon/uvd: use PIPE_USAGE_STAGING for msg&fb buffers That better matches the actual userspace use case, the kernel will force it to VRAM if the hardware requires it. To trigger this I need to repeatedly start mplayer using uvd - it's takes some time, I ended up making a script to do it for me while AFK. I am 99% sure the above is it - I spent a day and a half trying on the commit before (radeon/video: use the hw to initial clear the buffers) with no crash. The Oopses don't mention radeon or uvd. They will hit as soon as mplayer launches before it renders anything - screen locked, no mouse cursor or vt switch but SysRq works, box is still up in some ways for a while (one time I had music playing for 30s-1min after). One time oomkiller put on its blindfold and ran around killing :-) -- You are receiving this mail because: You are the assignee for the bug.

1 11

[Bug 60254] New: agd5f wip kernel Oops when provoking GPU lock.
by bugzilla-daemon＠freedesktop.org 30 Jul '15

30 Jul '15

https://bugs.freedesktop.org/show_bug.cgi?id=60254 Priority: medium Bug ID: 60254 Assignee: dri-devel(a)lists.freedesktop.org Summary: agd5f wip kernel Oops when provoking GPU lock. Severity: normal Classification: Unclassified OS: All Reporter: lists(a)andyfurniss.entadsl.com Hardware: Other Status: NEW Version: XOrg CVS Component: DRM/Radeon Product: DRI The GPU lock with Rv670 and openarena is nothing new - it seems to have been a feature for almost a year (I haven't used rv670 for most of that time). On noticing the new gpu reset code in drm-next-3.9-wip I decided to provoke it on my AGP box and got - Feb 3 20:46:56 nf7 kernel: radeon 0000:02:00.0: GPU lockup CP stall for more than 10000msec Feb 3 20:46:56 nf7 kernel: radeon 0000:02:00.0: GPU lockup (waiting for 0x00000000000111c8 last fence id 0x00000000000111c6) Feb 3 20:46:56 nf7 kernel: radeon 0000:02:00.0: f51df600 unpin not necessary Feb 3 20:46:56 nf7 kernel: radeon 0000:02:00.0: Saved 217 dwords of commands on ring 0. Feb 3 20:46:56 nf7 kernel: BUG: unable to handle kernel paging request at f87aec0c Feb 3 20:46:56 nf7 kernel: IP: [<fa033a3e>] radeon_fence_process+0x7e/0x160 [radeon] Feb 3 20:46:56 nf7 kernel: *pde = 3702f067 *pte = 00000000 Feb 3 20:46:56 nf7 kernel: Oops: 0000 [#1] PREEMPT Feb 3 20:46:56 nf7 kernel: Modules linked in: radeon fbcon font bitblit ttm softcursor drm_kms_helper drm fb fbdev i2c_algo_bit i2c_core cfbcopyarea cfbimgblt cfbfillrect ehci_pci ehci_hcd nvidia_agp agpgart ohci_hcd usbhid usbcore usb_common snd_intel8x0 snd_ac97_codec ac97_bus forcedeth Feb 3 20:46:56 nf7 kernel: Pid: 2511, comm: openarena.i386 Not tainted 3.8.0-rc3-gc7fb5ff #1 /NF7-S/NF7 (nVidia-nForce2) Feb 3 20:46:56 nf7 kernel: EIP: 0060:[<fa033a3e>] EFLAGS: 00210246 CPU: 0 Feb 3 20:46:56 nf7 kernel: EIP is at radeon_fence_process+0x7e/0x160 [radeon] Feb 3 20:46:56 nf7 kernel: EAX: f87aec0c EBX: f73b2848 ECX: f73b2848 EDX: 00000000 Feb 3 20:46:56 nf7 kernel: ESI: 00000000 EDI: f73b2000 EBP: e4765d8c ESP: e4765d58 Feb 3 20:46:56 nf7 kernel: DS: 007b ES: 007b FS: 0000 GS: 0033 SS: 0068 Feb 3 20:46:56 nf7 kernel: CR0: 8005003b CR2: f87aec0c CR3: 1e75f000 CR4: 000007d0 Feb 3 20:46:56 nf7 kernel: DR0: 00000000 DR1: 00000000 DR2: 00000000 DR3: 00000000 Feb 3 20:46:56 nf7 kernel: DR6: ffff0ff0 DR7: 00000400 Feb 3 20:46:56 nf7 kernel: Process openarena.i386 (pid: 2511, ti=e4764000 task=f70ad2b0 task.ti=e4764000) Feb 3 20:46:56 nf7 kernel: Stack: Feb 3 20:46:56 nf7 kernel: c13d4e58 00765d7c 00000018 f73b2848 f73b2888 00000872 00000003 00000872 Feb 3 20:46:56 nf7 kernel: 00000000 0000000c 00000003 f73b2a5c e4765e0c e4765da4 fa034850 f73b2000 Feb 3 20:46:56 nf7 kernel: f73b2000 f73b2a5c e4765e0c e4765dc4 fa049bb8 f73b28e8 00000000 c12b06cd Feb 3 20:46:56 nf7 kernel: Call Trace: Feb 3 20:46:56 nf7 kernel: [<c13d4e58>] ? sub_preempt_count+0x8/0x80 Feb 3 20:46:56 nf7 kernel: [<fa034850>] radeon_fence_count_emitted+0x20/0x90 [radeon] Feb 3 20:46:56 nf7 kernel: [<fa049bb8>] radeon_ring_backup+0x38/0x100 [radeon] Feb 3 20:46:56 nf7 kernel: [<c12b06cd>] ? _dev_info+0x2d/0x30 Feb 3 20:46:56 nf7 kernel: [<fa020b22>] radeon_gpu_reset+0x62/0x1d0 [radeon] Feb 3 20:46:56 nf7 kernel: [<f8be99c6>] ? ttm_bo_unreserve+0x26/0x50 [ttm] Feb 3 20:46:56 nf7 kernel: [<fa04821d>] radeon_gem_handle_lockup.part.2+0xd/0x20 [radeon] Feb 3 20:46:56 nf7 kernel: [<fa048b13>] radeon_gem_wait_idle_ioctl+0xb3/0xd0 [radeon] Feb 3 20:46:56 nf7 kernel: [<fa048a60>] ? radeon_gem_busy_ioctl+0xf0/0xf0 [radeon] Feb 3 20:46:56 nf7 kernel: [<f8af9e82>] drm_ioctl+0x402/0x460 [drm] Feb 3 20:46:56 nf7 kernel: [<fa048a60>] ? radeon_gem_busy_ioctl+0xf0/0xf0 [radeon] Feb 3 20:46:56 nf7 kernel: [<c104f469>] ? ktime_add_safe+0x9/0x60 Feb 3 20:46:56 nf7 kernel: [<c104fe80>] ? hrtimer_forward+0xa0/0x190 Feb 3 20:46:56 nf7 kernel: [<f8af9a80>] ? drm_copy_field+0x80/0x80 [drm] Feb 3 20:46:56 nf7 kernel: [<c10eb65a>] do_vfs_ioctl+0x7a/0x590 Feb 3 20:46:56 nf7 kernel: [<c101ef0b>] ? lapic_next_event+0x1b/0x20 Feb 3 20:46:56 nf7 kernel: [<c106978d>] ? clockevents_program_event+0x9d/0x150 Feb 3 20:46:56 nf7 kernel: [<c106ab18>] ? tick_program_event+0x28/0x30 Feb 3 20:46:56 nf7 kernel: [<c1050612>] ? hrtimer_interrupt+0x182/0x2f0 Feb 3 20:46:56 nf7 kernel: [<c13d4e58>] ? sub_preempt_count+0x8/0x80 Feb 3 20:46:56 nf7 kernel: [<c1048cf9>] ? __rcu_read_unlock+0x9/0x60 Feb 3 20:46:56 nf7 kernel: [<c10f4bc7>] ? fget_light+0x77/0xd0 Feb 3 20:46:56 nf7 kernel: [<c10ebbac>] sys_ioctl+0x3c/0x70 Feb 3 20:46:56 nf7 kernel: [<c13d7ffa>] sysenter_do_call+0x12/0x22 Feb 3 20:46:56 nf7 kernel: Code: 8b 4d d4 8d 84 51 f0 00 00 00 8b 74 c7 08 89 75 e0 8b 74 c7 0c 8b 45 d8 83 c0 08 80 bf ec 0d 00 00 00 0f 84 bf 00 00 00 8b 40 0c <8b> 00 39 45 e8 8b 4d ec 89 c3 ba 01 00 00 00 0f 47 ce 39 f1 77 Feb 3 20:46:56 nf7 kernel: EIP: [<fa033a3e>] radeon_fence_process+0x7e/0x160 [radeon] SS:ESP 0068:e4765d58 Feb 3 20:46:56 nf7 kernel: CR2: 00000000f87aec0c Feb 3 20:46:56 nf7 kernel: ---[ end trace 457588a7cbc40235 ]--- -- You are receiving this mail because: You are the assignee for the bug.

1 5

[Bug 88493] No hdmi audio an agd5f 3.20-wip since consolidate audio_get_pin() functions
by bugzilla-daemon＠freedesktop.org 30 Jul '15

30 Jul '15

https://bugs.freedesktop.org/show_bug.cgi?id=88493 Bug ID: 88493 Summary: No hdmi audio an agd5f 3.20-wip since consolidate audio_get_pin() functions Product: DRI Version: XOrg git Hardware: Other OS: All Status: NEW Severity: normal Priority: medium Component: DRM/Radeon Assignee: dri-devel(a)lists.freedesktop.org Reporter: adf.lists(a)gmail.com R9270X - audio not perfect normally, but there is none at all after - bead330b1af6fce76aedac9f89d20edcaeae27b3 is the first bad commit commit bead330b1af6fce76aedac9f89d20edcaeae27b3 Author: Slava Grigorev <slava.grigorev(a)amd.com> Date: Tue Dec 2 15:22:43 2014 -0500 radeon/audio: consolidate audio_get_pin() functions There is also another minor issue on head, but I haven't had time to bisect and it doesn't always show. If I bring TV up after booting with TV off there are a few pix of pink on left of screen - doing anything that resets mode/on/off or if on from boot avoids. Didn't see it in the bisect - first was bad so I guess it's in the other half. -- You are receiving this mail because: You are the assignee for the bug.

1 18

[Bug 70227] New: OpenCL reaper-prime app crashes due to atomic_or unimplemented
by bugzilla-daemon＠freedesktop.org 29 Jul '15

29 Jul '15

https://bugs.freedesktop.org/show_bug.cgi?id=70227 Priority: medium Bug ID: 70227 Assignee: dri-devel(a)lists.freedesktop.org Summary: OpenCL reaper-prime app crashes due to atomic_or unimplemented Severity: normal Classification: Unclassified OS: All Reporter: alexxy(a)gentoo.org Hardware: Other Status: NEW Version: git Component: Drivers/Gallium/r600 Product: Mesa Miner app https://github.com/arnuschky/primecoin-reaper.git crashes with ./reaper \|||||||||||||||||||||/ - Reaper v13 64-bit - - PRIME BETA 2 - - coded by mtrlt - /|||||||||||||||||||||\ Warning: unknown property "use_gpu" in configuration file. I'm now mining primecoin! Share thread started GeneratePrimeTable() : setting nSievePercentage = 1, nSieveSize = 100000 GeneratePrimeTable() : prime table [1, 100000] generated with 9592 primes Available CPU mining algorithms: hp7 Using default: hp7 Creating 1 CPU thread. 1...Warning: can't set thread priority done List of platforms: 0 Default Using platform number 0 Using device 0 OpenCL device 0........ Compiling kernel... this could take up to 2 minutes. 2 warnings generated. Building kernel CalculateMultipliers Building kernel Sieve Building kernel Combine Building kernel Fermat done Compiling kernel... this could take up to 2 minutes. 2 warnings generated. Building kernel CalculateMultipliers Building kernel Sieve Building kernel Combine Building kernel Fermat 0x7f735cdadd00: i32 = GlobalAddress<i32 (...)* @atomic_or> 0 [ORD=104] Stack dump: 0. Running pass 'Function Pass Manager' on module 'radeon'. 1. Running pass 'AMDGPU DAG->DAG Pattern Instruction Selection' on function '@Sieve' Segmentation fault -- You are receiving this mail because: You are the assignee for the bug.

1 3

[Bug 88719] While using nine gallium tracker and wine Dark Souls 2 causes gpu hang
by bugzilla-daemon＠freedesktop.org 28 Jul '15

28 Jul '15

https://bugs.freedesktop.org/show_bug.cgi?id=88719 Bug ID: 88719 Summary: While using nine gallium tracker and wine Dark Souls 2 causes gpu hang Product: DRI Version: XOrg git Hardware: Other OS: All Status: NEW Severity: normal Priority: medium Component: DRM/Radeon Assignee: dri-devel(a)lists.freedesktop.org Reporter: sobkas(a)gmail.com Created attachment 112683 --> https://bugs.freedesktop.org/attachment.cgi?id=112683&action=edit A console log from gpu hang While using nine gallium tracker and wine Dark Souls 2 causes gpu hang It happens in no mans wharf while entering shacks or in the last bonfire of old iron crown dlc. It can be worked around by adding R600_DEBUG=notiling to env. Kernel: 3.19.0-rc5-00119-gb942c65-dirty with resume patches: https://bugs.freedesktop.org/attachment.cgi?id=112527 https://bugs.freedesktop.org/attachment.cgi?id=112528 Mesa: I have tried mesa git master(bc6e57e019bd2399a70acabcad21217aadf2944c), https://github.com/iXit/Mesa-3D.git(both rebased on top of mesa git and clean 5ff32e24921c86b087085929e86720cc5b64be35 with additional fix for crash during the start) There was no difference Video card: 01:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Juniper XT [Radeon HD 6770] [1002:68ba] I have opened a bug on github: https://github.com/iXit/Mesa-3D/issues/63 and other person was able to reproduce it: https://github.com/iXit/Mesa-3D/issues/59#issuecomment-70933707 -- You are receiving this mail because: You are the assignee for the bug.

1 5

[Bug 90681] Radeon Kernel Oops & Lockup when switching on DisplayPort attached monitor
by bugzilla-daemon＠freedesktop.org 21 Jul '15

21 Jul '15

https://bugs.freedesktop.org/show_bug.cgi?id=90681 Bug ID: 90681 Summary: Radeon Kernel Oops & Lockup when switching on DisplayPort attached monitor Product: DRI Version: unspecified Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: major Priority: medium Component: DRM/Radeon Assignee: dri-devel(a)lists.freedesktop.org Reporter: bradfirj(a)fstab.me Created attachment 116079 --> https://bugs.freedesktop.org/attachment.cgi?id=116079&action=edit journalctl output for crash Switching my DisplayPort attached monitor on (or off and then on again) while booted to multiuser target (no Xorg or Wayland) causes a kernel Oops, followed by soft-lockups which render the system unusable. Doing the same while at the full Graphical target causes gnome-shell to crash, but it is possible to recover the system by logging in again. The kernel error and IP are: >May 24 23:25:28 fedora-workstation.home kernel: BUG: unable to handle kernel NULL pointer dereference at 00000000000003b0 >May 24 23:25:28 fedora-workstation.home kernel: IP: [<ffffffffa0152055>] radeon_connector_edid+0x5/0x70 [radeon] Full journal from a reproduction of the bug will be attached, as will lspci -nn. I have isolated this using git bisect to the following commit (the patch for which is attached to this bug). This is a commit currently part of the linux-stable tree and lies between 4.0.2 and 4.0.3 >016a255b7835ee7e49a3eba3c14ba0bc0221a4f8 is the first bad commit >commit 016a255b7835ee7e49a3eba3c14ba0bc0221a4f8 >Author: Alex Deucher <alexander.deucher(a)amd.com> >Date: Tue Apr 7 09:52:42 2015 -0400 > > drm/radeon: only mark audio as connected if the monitor supports it (v3) > > commit 0f55db36d49d45b80eff0c0a2a498766016f458b upstream. > > Otherwise the driver may try and send audio which may confuse the > monitor. > > v2: set pin to NULL if no audio > v3: avoid crash with analog encoders > > Signed-off-by: Alex Deucher <alexander.deucher(a)amd.com> > Signed-off-by: Greg Kroah-Hartman <gregkh(a)linuxfoundation.org>> > >:040000 040000 de0366a6790f5c91d175bcb89cb34956bbe72b26 >bbdb5734961f824558152c7c34a840c78bc3a9a9 M drivers -- You are receiving this mail because: You are the assignee for the bug.

1 14

[PATCH 0/5] i.MX5/6 mem2mem scaler
by Philipp Zabel 14 Jul '15

14 Jul '15

Hi, this series uses the IPU IC post-processing task, to implement a mem2mem device for scaling and colorspace conversion. regards Philipp Philipp Zabel (3): gpu: ipu-v3: Add missing IDMAC channel names gpu: ipu-v3: Add mem2mem image conversion support to IC gpu: ipu-v3: Register scaler platform device Sascha Hauer (2): [media] imx-ipu: Add ipu media common code [media] imx-ipu: Add i.MX IPUv3 scaler driver drivers/gpu/ipu-v3/ipu-common.c | 2 + drivers/gpu/ipu-v3/ipu-ic.c | 787 ++++++++++++++++++++++++- drivers/media/platform/Kconfig | 2 + drivers/media/platform/Makefile | 1 + drivers/media/platform/imx/Kconfig | 11 + drivers/media/platform/imx/Makefile | 2 + drivers/media/platform/imx/imx-ipu-scaler.c | 869 ++++++++++++++++++++++++++++ drivers/media/platform/imx/imx-ipu.c | 313 ++++++++++ drivers/media/platform/imx/imx-ipu.h | 36 ++ include/video/imx-ipu-v3.h | 49 +- 10 files changed, 2055 insertions(+), 17 deletions(-) create mode 100644 drivers/media/platform/imx/Kconfig create mode 100644 drivers/media/platform/imx/Makefile create mode 100644 drivers/media/platform/imx/imx-ipu-scaler.c create mode 100644 drivers/media/platform/imx/imx-ipu.c create mode 100644 drivers/media/platform/imx/imx-ipu.h -- 2.1.4

3 10

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

dri-devel May 2015