https://bugs.freedesktop.org/show_bug.cgi?id=106175
--- Comment #27 from tempel.jul...@gmail.com ---
Is this commit related to it?
https://lists.freedesktop.org/archives/amd-gfx/2018-October/027726.html
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=107928
--- Comment #7 from Matthew Vaughn ---
I am able to reproduce this bug report in every detail on my machine. The only
difference is that I am never present to directly observe the driver deadlock;
it always occurs when I have left the machine id
https://bugs.freedesktop.org/show_bug.cgi?id=107928
--- Comment #8 from Matthew Vaughn ---
Created attachment 142018
--> https://bugs.freedesktop.org/attachment.cgi?id=142018&action=edit
Trimmed dmesg logs
--
You are receiving this mail because:
You are the assignee for the bug.__
https://bugs.freedesktop.org/show_bug.cgi?id=108356
Bug ID: 108356
Summary: AMD DC: Mullins APU: Possible race condition between
vblank interrupt and atomic pageflip
Product: DRI
Version: DRI git
Hardware: Other
https://bugs.freedesktop.org/show_bug.cgi?id=108356
--- Comment #1 from Mauro Rossi ---
Created attachment 142020
--> https://bugs.freedesktop.org/attachment.cgi?id=142020&action=edit
Screen slightly affected
--
You are receiving this mail because:
You are the assignee for the bug.___
https://bugs.freedesktop.org/show_bug.cgi?id=108356
--- Comment #2 from Mauro Rossi ---
Created attachment 142021
--> https://bugs.freedesktop.org/attachment.cgi?id=142021&action=edit
Screen affected up to one third of screen
--
You are receiving this mail because:
You are the assignee for th
https://bugs.freedesktop.org/show_bug.cgi?id=107928
Matthew Vaughn changed:
What|Removed |Added
Attachment #142018|0 |1
is obsolete|
Hi Thomas,
> that the access() handler took a shortcut when the new locking order
> was established
There is no new locking order, the access handler is just for debugging
and ignoring the correct locking order between mmap_sem and bo_reserve.
That this is throwing a lockdep warning is perfect
https://bugs.freedesktop.org/show_bug.cgi?id=107266
--- Comment #7 from robert ---
All Polaris are experiencing ring errors on mainline kernels, its not just Pro
Duo Polaris.
# lspci | grep VGA
01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI]
Ellesmere [Radeon RX 470/48
_64 0:18.30-641594.el7
Replaced:
vulkan-amdgpu-pro.x86_64 0:18.30-641594.el7
Complete!
[19:24][20181014-1]# yum upgrade
Loaded plugins: aliases, changelog, copr, langpacks, priorities, product-id,
protectbase, ps, search-disabled-repos, subscription-manager,
Hi,
On Mon, Oct 8, 2018 at 1:48 PM Daniel Drake wrote:
> I recently filed a bug report regarding graphics corruption seen on
> Gemini Lake platforms:
> https://bugs.freedesktop.org/show_bug.cgi?id=108085
>
> This has been reproduced on multiple distros on products from at least
> 4 vendors. It se
Commit b24413180f5600bcb3bb70fbed5cf186b60864bd
'License cleanup: add SPDX GPL-2.0 license identifier to files with no license'
incorrectly added "SPDX-License-Identifier: GPL-2.0" to a file with MIT
license text. Change the SPDX identifier to match the license text.
Signed-off-by: Jonathan Gray
Commit b24413180f5600bcb3bb70fbed5cf186b60864bd added
"SPDX-License-Identifier: GPL-2.0" to files which previously had no
license, change this to MIT for radeon matching the license text of the
other radeon files.
Signed-off-by: Jonathan Gray
---
drivers/gpu/drm/radeon/mkregtable.c | 2
https://bugs.freedesktop.org/show_bug.cgi?id=108361
Bug ID: 108361
Summary: Radeon/Xorg crash during boot with Radeon R5 M230
Product: DRI
Version: unspecified
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
On Sun, Oct 14, 2018 at 8:20 PM Koenig, Christian
wrote:
>
> Hi Thomas,
>
> > that the access() handler took a shortcut when the new locking order
> > was established
> There is no new locking order, the access handler is just for debugging
> and ignoring the correct locking order between mmap_se
15 matches
Mail list logo
