https://bugs.freedesktop.org/show_bug.cgi?id=112079
Bug ID: 112079
Summary: X lockups with HWCursor enabled - Navi 5700 XT
Product: DRI
Version: DRI git
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
> -Original Message-
> From: Ville Syrjälä
> Sent: Monday, October 14, 2019 10:42 PM
> To: Lin, Wayne
> Cc: dri-devel@lists.freedesktop.org; intel-...@lists.freedesktop.org
> Subject: Re: [PATCH 4/4] drm/edid: Prep for HDMI VIC aspect ratio (WIP)
>
> On Mon, Oct 14, 2019 at 09:27:07AM
On 2019/10/21 上午7:41, Parav Pandit wrote:
-Original Message-
From: Jason Wang
Sent: Thursday, October 17, 2019 5:49 AM
To: k...@vger.kernel.org; linux-s...@vger.kernel.org; linux-
ker...@vger.kernel.org; dri-devel@lists.freedesktop.org; intel-
g...@lists.freedesktop.org; intel-gvt-..
On 2019/10/18 下午10:20, Cornelia Huck wrote:
On Thu, 17 Oct 2019 18:48:35 +0800
Jason Wang wrote:
This patch introduces a new mdev transport for virtio. This is used to
use kernel virtio driver to drive the mediated device that is capable
of populating virtqueue directly.
A new virtio-mdev d
On 2019/10/18 下午9:30, Cornelia Huck wrote:
On Fri, 18 Oct 2019 18:55:02 +0800
Jason Wang wrote:
On 2019/10/18 下午5:46, Cornelia Huck wrote:
On Thu, 17 Oct 2019 18:48:34 +0800
Jason Wang wrote:
+ * @get_vendor_id: Get virtio vendor id
+ * @mdev: media
On 18-10-19, 17:41, Arnd Bergmann wrote:
> The mach/hardware.h is included in lots of places, and it provides
> three different things on pxa:
>
> - the cpu_is_pxa* macros
> - an indirect inclusion of mach/addr-map.h
> - the __REG() and io_pv2() helper macros
>
> Split it up into separate and ma
https://bugs.freedesktop.org/show_bug.cgi?id=111481
--- Comment #118 from Andrew Sheldon ---
(In reply to Daniel Suarez from comment #117)
> Test out kernel 5.4rc4, it should have addressed this I believe.
If you're referring to: drm/amdgpu/sdma5: fix mask value of POLL_REGMEM packet
for pipe syn
We have done some tests on three of Intel + nVidia configuration
systems with OEM _OSI strings removed - while some bugs are still
observed, ex. one out of three has suspend/resume issues, no system
crashes were observed - the biggest issue that worries us.
The positive results give us confident t
https://bugs.freedesktop.org/show_bug.cgi?id=111762
--- Comment #2 from Andrew Sheldon ---
As a workaround, use upp instead as a workaround (write to the powerplay binary
directly). See: https://github.com/sibradzic/upp
I suggest using 5.4-rcX as AMD's wip kernels (amd-staging-drm-next and
drm-n
https://bugs.freedesktop.org/show_bug.cgi?id=111481
--- Comment #117 from Daniel Suarez ---
(In reply to Mark Dietzer from comment #115)
> For me it seems to happen commonly when I watch 60fps video (YouTube) using
> Firefox on my RX 5700 XT (currently on Fedora 31 with latest distro
> packages).
> -Original Message-
> From: Jason Wang
> Sent: Thursday, October 17, 2019 5:49 AM
> To: k...@vger.kernel.org; linux-s...@vger.kernel.org; linux-
> ker...@vger.kernel.org; dri-devel@lists.freedesktop.org; intel-
> g...@lists.freedesktop.org; intel-gvt-...@lists.freedesktop.org;
> kwankh
> -Original Message-
> From: Jason Wang
> Sent: Thursday, October 17, 2019 5:49 AM
> To: k...@vger.kernel.org; linux-s...@vger.kernel.org; linux-
> ker...@vger.kernel.org; dri-devel@lists.freedesktop.org; intel-
> g...@lists.freedesktop.org; intel-gvt-...@lists.freedesktop.org;
> kwankh
> -Original Message-
> From: kvm-ow...@vger.kernel.org On Behalf
> Of Jason Wang
> Sent: Thursday, October 17, 2019 5:49 AM
> To: k...@vger.kernel.org; linux-s...@vger.kernel.org; linux-
> ker...@vger.kernel.org; dri-devel@lists.freedesktop.org; intel-
> g...@lists.freedesktop.org; inte
https://bugs.freedesktop.org/show_bug.cgi?id=112071
zamundaa...@gmail.com changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://bugs.freedesktop.org/show_bug.cgi?id=111481
--- Comment #116 from Shmerl ---
Metrics bug is something with powerplay, that's a different one from sdma
timeouts. It happens when you query amdgpu sensors concurrently. To avoid it,
simply don't query them (like using ksysguard or any other G
https://bugs.freedesktop.org/show_bug.cgi?id=111481
--- Comment #115 from Mark Dietzer ---
For me it seems to happen commonly when I watch 60fps video (YouTube) using
Firefox on my RX 5700 XT (currently on Fedora 31 with latest distro packages).
Even 4K video at 30fps does not seem to cause any i
The pixel fetcher FIFO depth was just hardcoded to 48
which works fine as long as the framebuffer is 32BPP
and the DSI output is RGB888.
We will need more elaborate handling for some buffer
formats and displays, so start to improve this function
by setting reasonable defaults for 32, 24 and 16 BPP
https://bugs.freedesktop.org/show_bug.cgi?id=111481
--- Comment #114 from Shmerl ---
Just to clarify. Is this affecting only OpenGL code paths? Firefox with
WebRender is for example using OpenGL. I.e. can those hangs be a problem with
radeonsi doing something incorrectly, or it's for sure a bug i
https://bugzilla.kernel.org/show_bug.cgi?id=203033
m...@sijmenschoon.nl changed:
What|Removed |Added
CC||m...@sijmenschoon.nl
--- Comment #
https://bugzilla.kernel.org/show_bug.cgi?id=204241
Mario (ker...@catmail.app) changed:
What|Removed |Added
CC||ker...@catmail.app
--- Comme
https://bugs.freedesktop.org/show_bug.cgi?id=112071
zamundaa...@gmail.com changed:
What|Removed |Added
CC||zamundaa...@gmail.com
--- Commen
https://bugs.freedesktop.org/show_bug.cgi?id=112071
--- Comment #3 from zamundaa...@gmail.com ---
Created attachment 145781
--> https://bugs.freedesktop.org/attachment.cgi?id=145781&action=edit
dmesg output
--
You are receiving this mail because:
You are the assignee for the bug.__
https://bugs.freedesktop.org/show_bug.cgi?id=112071
--- Comment #2 from zamundaa...@gmail.com ---
Created attachment 145780
--> https://bugs.freedesktop.org/attachment.cgi?id=145780&action=edit
/var/log/Xorg.0.log
--
You are receiving this mail because:
You are the assignee for the bug.___
https://bugs.freedesktop.org/show_bug.cgi?id=112071
--- Comment #1 from Alex Deucher ---
Please attach your dmesg output and xorg log (if using X).
--
You are receiving this mail because:
You are the assignee for the bug.___
dri-devel mailing list
dri
https://bugs.freedesktop.org/show_bug.cgi?id=110674
--- Comment #167 from Alex Deucher ---
(In reply to Peter Hercek from comment #166)
> I got the crash after 4 days of use. It looks the same as before:
> ring sdma0 timeout, gpu reset (allegedly successful), many skipped IBs, and
> failure to in
Fastboot is not working on an Asus T100HA, it gives the following
relevant messages / errors:
dsi pll div 000201e6, ctrl 80080100
fastset mismatch in dsi_pll.ctrl (expected 0x80100100, found 0x80080100)
fastset mismatch in dsi_pll.div (expected 0x0002008e, found 0x000201e6)
The problem seems t
Since commit 051a6d8d3ca0 ("drm/i915: Move LUT programming to happen after
vblank waits"), I am seeing an ugly colored flash of the first few display
lines on 2 Cherry Trail devices when the gamma table gets set for the first
time. A blue flash on a GPD win and a yellow flash on an Asus T100HA.
Th
https://bugzilla.kernel.org/show_bug.cgi?id=205279
Bug ID: 205279
Summary: BUG: KASAN: global-out-of-bounds in
read_indirect_azalia_reg+0x69/0x100 [amdgpu]
Product: Drivers
Version: 2.5
Kernel Version: 5.4.0-rc3+
Hardwa
https://bugzilla.kernel.org/show_bug.cgi?id=204805
ilkka.pr...@gmail.com changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://bugzilla.kernel.org/show_bug.cgi?id=205277
--- Comment #2 from Pelle van Gils (pe...@vangils.xyz) ---
(In reply to Pelle van Gils from comment #1)
> Created attachment 285585 [details]
> proposed patch
>
> added proposed fix
with this patch applied (and the debug patch) dmesg output is:
https://bugzilla.kernel.org/show_bug.cgi?id=205277
--- Comment #1 from Pelle van Gils (pe...@vangils.xyz) ---
Created attachment 285585
--> https://bugzilla.kernel.org/attachment.cgi?id=285585&action=edit
proposed patch
added proposed fix
--
You are receiving this mail because:
You are watchi
Inside dma-fence-chain, we use a cmpxchg on an RCU-protected pointer. To
avoid the sparse warning for using the RCU pointer directly, we have to
cast away the __rcu annotation. However, we don't need to use void*
everywhere and can stick to the dma_fence*.
Signed-off-by: Chris Wilson
---
drivers
A few very simple testcases to exercise the dma-fence-chain API.
Signed-off-by: Chris Wilson
---
drivers/dma-buf/Makefile | 3 +-
drivers/dma-buf/selftests.h | 1 +
drivers/dma-buf/st-dma-fence-chain.c | 713 +++
3 files changed, 716 insertions(+)
Whenever we walk along the dma-fence-chain, we prune signaled links to
keep the chain nice and tidy. This leads to situations where we can
prune a link and report the earlier fence as the target seqno --
violating our own consistency checks that the seqno is not more advanced
than the last element
https://bugzilla.kernel.org/show_bug.cgi?id=205277
Bug ID: 205277
Summary: [amd powerplay] vega10: soc voltage for power state 7
is not changed by overdrive.
Product: Drivers
Version: 2.5
Kernel Version: 5.4.0-rc3
Hardw
Am 18.10.19 um 22:36 schrieb Jason Gunthorpe:
> On Thu, Oct 17, 2019 at 04:47:20PM +, Koenig, Christian wrote:
>
>>> get_user_pages/hmm_range_fault() and invalidate_range_start() both are
>>> called while holding mm->map_sem, so they are always serialized.
>> Not even remotely.
>>
>> For callin
https://bugs.freedesktop.org/show_bug.cgi?id=111481
--- Comment #113 from Daniel Suarez ---
(In reply to Shmerl from comment #112)
> (In reply to Jeremy Attali from comment #111)
> > I confirm I'm also still getting some hangs from time to time. Mostly I
> > think after a resume from Suspend.
>
The 'functions' directive is not only for functions, but also works for
structs/unions. So the name is misleading. This patch renames it to
'identifiers', which specific the functions/types to be included in
documentation. We keep the old name as an alias of the new one before
all documentation are
https://bugs.freedesktop.org/show_bug.cgi?id=108942
--- Comment #4 from tempel.jul...@gmail.com ---
I wonder why this is still an issue (linux 5.3.4, showing 30W with lowest
clocks and voltages) if it already worked with Polaris 11 some years ago.
--
You are receiving this mail because:
You are
https://bugs.freedesktop.org/show_bug.cgi?id=111762
--- Comment #1 from tempel.jul...@gmail.com ---
Still happens with current 5.5-wip/drm-next kernels.
I don't know if it is supposed to be implemented, but there seems to be some
bug apart from that:
Just reading sysfs entries at "/sys/class/drm/c
https://bugs.freedesktop.org/show_bug.cgi?id=109332
tempel.jul...@gmail.com changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|--
https://bugs.freedesktop.org/show_bug.cgi?id=112071
Bug ID: 112071
Summary: 5700 XT: ppfeaturemask doesn't work with iGPU
multi-monitor
Product: DRI
Version: DRI git
Hardware: x86-64 (AMD64)
OS: Linux (All)
Hello,
I tried another script for the semantic patch language out.
This source code analysis approach points a call of the member
function “get_config_mode” out for further considerations
according to the implementation of the function “mdfld_dsi_output_init”.
https://git.kernel.org/pub/scm/linux/
43 matches
Mail list logo
