https://bugs.freedesktop.org/show_bug.cgi?id=105733
Allan changed:
What|Removed |Added
Priority|medium |highest
Severity|critical
https://bugs.freedesktop.org/show_bug.cgi?id=105733
Bug ID: 105733
Summary: Amdgpu randomly hangs and only ssh works. Mouse cursor
moves sometimes but does nothing. Keyboard stops
working.
Product: DRI
Version: XO
https://bugzilla.kernel.org/show_bug.cgi?id=199101
--- Comment #5 from Thomas Crider (tcride...@gmail.com) ---
Created attachment 274921
--> https://bugzilla.kernel.org/attachment.cgi?id=274921&action=edit
Output from journalctl -k on 4.16.0-rc6-VEGA
--
You are receiving this mail because:
You
https://bugzilla.kernel.org/show_bug.cgi?id=199101
Thomas Crider (tcride...@gmail.com) changed:
What|Removed |Added
CC||tcride...@gmail.com
We are an atomic driver so the gamma LUT should also be exposed as a
CRTC property through the DRM atomic color management. This will also
take care of the legacy path for us.
Signed-off-by: Stefan Schake
---
v2: Use drm_color_lut_size for LUT length
drivers/gpu/drm/vc4/vc4_crtc.c | 24
The hardware supports a CTM with S0.9 values. We therefore only allow
a value of 1.0 or fractional only and reject all others with integer
parts. This restriction is mostly inconsequential in practice since
commonly used transformation matrices have all scalars <= 1.0.
Signed-off-by: Stefan Schake
From: Eric Anholt
At least the RGBA expand field we should have been setting, because we
aren't expanding correctly for 565 -> . Other registers are ones
that may be interesting for various projects that have been discussed.
Signed-off-by: Eric Anholt
Cc: Stefan Schake
---
v2: New in the
We only have one hardware block to do the CTM and need to reject
attempts to enable it for multiple CRTCs simultaneously.
Signed-off-by: Stefan Schake
---
v2: No change
drivers/gpu/drm/vc4/vc4_crtc.c | 11 +++
1 file changed, 11 insertions(+)
diff --git a/drivers/gpu/drm/vc4/vc4_crtc.c
This series adds support for the gamma and CTM properties to VC4.
I've sent the necessary register defs as part of the series this
time around to give the full picture.
The CTM support is somewhat limited in that we can only enable it for one
CRTC at a time and coefficients are S0.9 in hardware. T
https://bugzilla.kernel.org/show_bug.cgi?id=199123
--- Comment #12 from david becerra (davidbecerrapor...@gmail.com) ---
linux amd-staging drm-next has also a choppy cursor but its less severe
linux 4.15 is still good
--
You are receiving this mail because:
You are watching the assignee of the b
https://bugs.freedesktop.org/show_bug.cgi?id=105729
--- Comment #1 from ejr.ph...@gmail.com ---
Hi, I might have this bug as well on i3wm. I believe it's the same, flickering
when mouse movement occurs. However it's not flickering, it's more like it's
locking the framebuffer and preventing any dra
https://bugs.freedesktop.org/show_bug.cgi?id=104064
--- Comment #49 from taij...@posteo.de ---
(In reply to Bjorn from comment #48)
> I managed to compile and test drm-next-4.17-wip, commit
> a611dd16c69025b6df115427af0a5d63ae9f5145.
>
> I can confirm that I did not see the amdgpu crash on boot a
https://bugs.freedesktop.org/show_bug.cgi?id=104064
--- Comment #48 from Bjorn ---
I managed to compile and test drm-next-4.17-wip, commit
a611dd16c69025b6df115427af0a5d63ae9f5145.
I can confirm that I did not see the amdgpu crash on boot any more. However,
suspend/resume still hangs my laptop.
On 03/22/2018 03:27 PM, Ville Syrjala wrote:
From: Ville Syrjälä
We'll need access to the plane state during .atomic_enable().
Some more details in the commit message would be useful. It is
not clear to me why this change is being made.
___
dri-dev
On 03/23/2018 10:35 AM, Ville Syrjala wrote:
From: Ville Syrjälä
mipi_dbi_enable_flush() wants to call the fb->dirty() hook from the
bowels of the .atomic_enable() hook. That prevents us from taking the
plane mutex in fb->dirty() unless we also plumb down the acquire
context.
Instead it seems
https://bugs.freedesktop.org/show_bug.cgi?id=105624
Sylvain BERTRAND changed:
What|Removed |Added
Resolution|--- |FIXED
Status|NEW
On Sun, Mar 18, 2018 at 04:40:59PM +, sylvain.bertr...@gmail.com wrote:
> I bisected a commit which broke my amd tahiti xt support.
> bad commit:83e3c46158720af39eef49e7066ee091e60e773a
> last good commit:f97eb9dba72fadc7c3ee1ed585246450fa927127
Tested today commit: my linux kernel is booting
https://bugs.freedesktop.org/show_bug.cgi?id=104001
--- Comment #29 from mikhail.v.gavri...@gmail.com ---
[ 69.089101] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout,
last signaled seq=897, last emitted seq=899
[ 69.089176] [drm] No hardware hang detected. Did some blocks stall?
[
https://bugs.freedesktop.org/show_bug.cgi?id=105317
--- Comment #3 from mikhail.v.gavri...@gmail.com ---
[ 463.172901] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout,
last signaled seq=26958, last emitted seq=26960
[ 463.172985] [drm] No hardware hang detected. Did some blocks stall
Hi Martin,
> Le 24 mars 2018 à 12:00, Martin Blumenstingl
> a écrit :
>
> Hello Hans, Hi Neil,
>
> (apologies in advance if any of this is wrong, I don't have any CEC
> capable TV so I can't test it)
>
> On Fri, Mar 23, 2018 at 1:59 PM, Hans Verkuil wrote:
>> From: Hans Verkuil
>>
>> Some
https://bugs.freedesktop.org/show_bug.cgi?id=95058
Mez changed:
What|Removed |Added
CC||mezcalb...@hotmail.com
--- Comment #3 from Mez --
https://bugs.freedesktop.org/show_bug.cgi?id=105018
--- Comment #26 from Mez ---
Also propably related:
https://bugs.freedesktop.org/show_bug.cgi?id=101580
--
You are receiving this mail because:
You are the assignee for the bug.___
dri-devel mailing
https://bugs.freedesktop.org/show_bug.cgi?id=105018
Mez changed:
What|Removed |Added
CC||mezcalb...@hotmail.com
--- Comment #25 from Mez
https://bugs.freedesktop.org/show_bug.cgi?id=105530
--- Comment #7 from Mez ---
This occurs for me on the below Polaris system as well. Timing matches the
dates in this thread. I've always had Tearfree option on though and it didn't
occur before these last few weeks.
OS: Ubuntu 18.04 bionic
Kern
https://bugs.freedesktop.org/show_bug.cgi?id=105729
Jan Vlug changed:
What|Removed |Added
See Also||https://bugzilla.suse.com/s
https://bugs.freedesktop.org/show_bug.cgi?id=105729
Jan Vlug changed:
What|Removed |Added
See Also||https://launchpad.net/bugs/
https://bugs.freedesktop.org/show_bug.cgi?id=96868
Jan Vlug changed:
What|Removed |Added
See Also||https://bugs.freedesktop.or
https://bugs.freedesktop.org/show_bug.cgi?id=105729
Jan Vlug changed:
What|Removed |Added
See Also||https://bugs.freedesktop.or
https://bugs.freedesktop.org/show_bug.cgi?id=105729
Jan Vlug changed:
What|Removed |Added
See Also||https://bugzilla.redhat.com
https://bugs.freedesktop.org/show_bug.cgi?id=105729
Jan Vlug changed:
What|Removed |Added
See Also||https://bugs.freedesktop.or
https://bugs.freedesktop.org/show_bug.cgi?id=105729
Jan Vlug changed:
What|Removed |Added
See Also||https://bugs.freedesktop.or
https://bugs.freedesktop.org/show_bug.cgi?id=83262
Jan Vlug changed:
What|Removed |Added
See Also||https://bugs.freedesktop.or
https://bugs.freedesktop.org/show_bug.cgi?id=105729
Bug ID: 105729
Summary: AMD Radeon flickering on Gnome Wayland after wake from
suspend
Product: DRI
Version: unspecified
Hardware: Other
OS: All
On Tuesday 20 March 2018 02:56 AM, Stefan Agner wrote:
The function dsi_get_cmd_fmt returns enum dsi_cmd_dst_format,
use the correct enum value also for MIPI_DSI_FMT_RGB666/_PACKED.
This has been discovered using clang:
drivers/gpu/drm/msm/dsi/dsi_host.c:743:35: warning: implicit conversion
https://bugs.freedesktop.org/show_bug.cgi?id=99275
--- Comment #36 from Jan Vlug ---
see also https://gitlab.gnome.org/GNOME/mutter/issues/22
--
You are receiving this mail because:
You are the assignee for the bug.___
dri-devel mailing list
dri-devel
https://bugs.freedesktop.org/show_bug.cgi?id=100726
--- Comment #12 from Jan Vlug ---
Maybe related to:
https://gitlab.gnome.org/GNOME/mutter/issues/22
--
You are receiving this mail because:
You are the assignee for the bug.___
dri-devel mailing list
https://bugs.freedesktop.org/show_bug.cgi?id=105728
Paul Menzel changed:
What|Removed |Added
Summary|radeon_init takes longer|radeon_init takes longer
https://bugs.freedesktop.org/show_bug.cgi?id=105728
Paul Menzel changed:
What|Removed |Added
CC||pmenzel+bugs.freedesktop@mo
https://bugs.freedesktop.org/show_bug.cgi?id=105728
Bug ID: 105728
Summary: radeon_init takes longer than a few seconds
Product: DRI
Version: DRI git
Hardware: Other
OS: All
Status: NEW
Severity: normal
https://bugs.freedesktop.org/show_bug.cgi?id=105030
--- Comment #2 from Paul Menzel ---
(In reply to Christian König from comment #1)
> You could bisect, but I would say in general that is desired behavior.
>
> We must make sure that the hardware is correctly powered up before
> continuing here.
On 23 March 2018 at 17:31, Ville Syrjälä wrote:
> On Fri, Mar 23, 2018 at 05:00:11PM +, Daniel Stone wrote:
>> On 23 March 2018 at 14:49, Ville Syrjälä
>> wrote:
>> > On Fri, Mar 23, 2018 at 01:45:52PM +, Daniel Stone wrote:
>> >> + for (i = 0; i < ARRAY_SIZE(r->handles); i++) {
>> >
Hi Nipun,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on linus/master]
[also build test ERROR on v4.16-rc6]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.com/0day-ci/linux/commits/Nipun-Gu
https://bugs.freedesktop.org/show_bug.cgi?id=105725
hjpries...@gmail.com changed:
What|Removed |Added
Hardware|Other |x86-64 (AMD64)
CC
https://bugs.freedesktop.org/show_bug.cgi?id=105725
Bug ID: 105725
Summary: WARNING: CPU: 0 PID: 487 at
drivers/gpu/drm/amd/amdgpu/../display
/dc/gpio/gpio_base.c:64 dal_gpio_open_ex+0xc/0x30
[amdgpu]
Pro
https://bugs.freedesktop.org/show_bug.cgi?id=99923
--- Comment #23 from network...@rkmail.ru ---
Same problem here, Mesa git master 4a8ef1f5d4c5fc96194be65045e6a3d4f5b9f913,
LLVM 7 r328326, kernel 4.15.12, TAHITI + amdgpu kernel module.
It looks a bit different with R600_DEBUG=nir, but still brok
https://bugs.freedesktop.org/show_bug.cgi?id=105412
--- Comment #9 from Vasya ---
(In reply to Michel Dänzer from comment #8)
> It seems clear that the problem you're seeing is not related to
> sync-to-vblank.
>
> Since you say the problem started after updating the kernel, it's probably
> best
46 matches
Mail list logo
