https://bugs.freedesktop.org/show_bug.cgi?id=105819
--- Comment #8 from Greg White ---
Same here, Vega 56 / kernel 4.19rc3. Tried mesa 18.3 master and 18.2, llvm 8
(svn) and llvm 6 on Arch linux; libdrm is all at current git head. This
reproduces very easily and quickly using chrome and the web
https://bugs.freedesktop.org/show_bug.cgi?id=107946
--- Comment #2 from Dave Johnson ---
Created attachment 141578
--> https://bugs.freedesktop.org/attachment.cgi?id=141578&action=edit
dmesg output from broken system, kernel 4.18
--
You are receiving this mail because:
You are the assignee fo
https://bugs.freedesktop.org/show_bug.cgi?id=107946
--- Comment #1 from Dave Johnson ---
Created attachment 141577
--> https://bugs.freedesktop.org/attachment.cgi?id=141577&action=edit
dmesg output from a working system, kernel 4.16
--
You are receiving this mail because:
You are the assignee
https://bugs.freedesktop.org/show_bug.cgi?id=107946
Bug ID: 107946
Summary: AMDGPU regression, multi-head not working on 4.18,
4.19RC3, but does on 4.16
Product: DRI
Version: XOrg git
Hardware: x86-64 (AMD64)
https://bugzilla.kernel.org/show_bug.cgi?id=201067
--- Comment #8 from Dave Johnson (d...@locochino.com) ---
Update: for my possibly-separate-issue I can confirm that multi-head works on
4.16.13 and not 4.19_RC3
For now I'm staying on 4.16 as it's working perfectly back there.
--
You are receiv
https://bugzilla.kernel.org/show_bug.cgi?id=201067
--- Comment #7 from Dave Johnson (d...@locochino.com) ---
(In reply to Nicholas Kazlauskas from comment #6)
> I think you're referencing this patch:
>
> https://patchwork.freedesktop.org/patch/238065/
>
> Which should be fixed in 4.18.
>
> Plea
Hi Dave,
On Saturday, 15 September 2018 17:26:42 EEST Laurent Pinchart wrote:
> Hi Dave,
>
> The following changes since commit 2dc7bad71cd310dc94d1c9907909324dd2b0618f:
>
> Merge tag 'drm-misc-next-2018-09-13' of git://anongit.freedesktop.org/drm/
> drm-misc into drm-next (2018-09-14 09:43:16
https://bugzilla.kernel.org/show_bug.cgi?id=201139
Bug ID: 201139
Summary: amdgpu: [drm] enabling link 1 failed: 15 (vega)
Product: Drivers
Version: 2.5
Kernel Version: 4.19-rc3
Hardware: All
OS: Linux
Tree: M
https://bugs.freedesktop.org/show_bug.cgi?id=107873
--- Comment #7 from Zebediah Figura ---
(In reply to Timothy Arceri from comment #5)
> Ok I think this is a regression with wine staging. First of all I can
> confirm this is not a RADV bug setting +r_renderapi 1 in launch options for
> steam la
Hi Dave,
The following changes since commit 2dc7bad71cd310dc94d1c9907909324dd2b0618f:
Merge tag 'drm-misc-next-2018-09-13' of git://anongit.freedesktop.org/drm/
drm-misc into drm-next (2018-09-14 09:43:16 +1000)
are available in the Git repository at:
git://linuxtv.org/pinchartl/media.git t
https://bugs.freedesktop.org/show_bug.cgi?id=100390
--- Comment #10 from Christoph Berliner ---
Thank you all for your efforts. Problem solved.
I have tested the game today and its playable without any glitches using mesa
18.2 so far.
System and driver information:
System:Host: home Kernel:
https://bugs.freedesktop.org/show_bug.cgi?id=107873
--- Comment #6 from Ahmed Elsayed ---
I can start the game with Vulkan but it stops loading at 99%, but with opengl,
I can hear the menu sounds but I can see only the red fog.
I filed a bug in Wine but no one answered me.
https://bugs.winehq.o
No, the problem is the function pointer analysis.
In other words the KIQ ring is sometimes used in atomic and even interrupt
context.
But the UVD ring is never used in atomic context.
But I don't see a way a static analysis could ever figure that out.
Regards,
Christian.
Am 15.09.2018 11:18 s
amdgpu_ring_alloc() does call amdgpu_uvd_begin_use(), but never in the call
chain you proposed.
Thinking about it I actually don't see a way a statically analysis could ever
figure that out.
Christian.
Am 15.09.2018 11:05 schrieb Jia-Ju Bai :
Thanks for your reply.
On 2018/9/15 17:01, Koenig,
Sorry to say that but your analysis tool is buggy.
The proposed call paths will never trigger.
Regards,
Christian.
Am 15.09.2018 10:59 schrieb Jia-Ju Bai :
The driver may sleep with holding a spinlock.
The function call paths (from bottom to top) in Linux-4.17 are:
[FUNC] mutex_lock_nested
driv
15 matches
Mail list logo