https://bugs.freedesktop.org/show_bug.cgi?id=109955
--- Comment #108 from Wilko Bartels ---
Did u try the amdgpu-pro driver as well?
i just did four runs of glmark and it just went through for me. going up to
1600mhz shader clock. tested both closed and opensource drivers. vega pulse
here.
mesa
https://bugs.freedesktop.org/show_bug.cgi?id=111482
--- Comment #20 from Andrew Sheldon ---
(In reply to Leon from comment #19)
> By the way, since I have a x470 mb, it cannot be related to PCI express 4.0.
> It's also not related to dual displays, since I'm running just one.
Not necessarily. So
https://bugs.freedesktop.org/show_bug.cgi?id=111691
--- Comment #12 from Andre Klapper ---
Nearly nobody knows which versions are shipped by some distribution in some
release. Please always provide version information - thanks.
--
You are receiving this mail because:
You are the assignee for th
https://bugs.freedesktop.org/show_bug.cgi?id=111482
--- Comment #21 from Robert ---
(In reply to Leon from comment #18)
> I have the same problem. Sapphire 5700 XT Nitro, x470 motherboard (asrock
> taichi), running arch with kernel 5.3.1. My resolution is 2560x1440 144Hz,
> with 30Watts idle and
https://bugs.freedesktop.org/show_bug.cgi?id=111848
Bug ID: 111848
Summary: AMDGPU and display fails after resume from suspend
Product: DRI
Version: unspecified
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
https://bugs.freedesktop.org/show_bug.cgi?id=111848
--- Comment #1 from Martin Jørgensen ---
Created attachment 145563
--> https://bugs.freedesktop.org/attachment.cgi?id=145563&action=edit
dmesg output after wakeup
--
You are receiving this mail because:
You are the assignee for the bug._
https://bugs.freedesktop.org/show_bug.cgi?id=111848
--- Comment #2 from Martin Jørgensen ---
Created attachment 145564
--> https://bugs.freedesktop.org/attachment.cgi?id=145564&action=edit
basic info
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=111848
--- Comment #3 from Martin Jørgensen ---
Created attachment 145565
--> https://bugs.freedesktop.org/attachment.cgi?id=145565&action=edit
demidecode output
--
You are receiving this mail because:
You are the assignee for the bug._
https://bugs.freedesktop.org/show_bug.cgi?id=111848
--- Comment #4 from Martin Jørgensen ---
Created attachment 145566
--> https://bugs.freedesktop.org/attachment.cgi?id=145566&action=edit
lsinitramfs output
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=111848
--- Comment #5 from Martin Jørgensen ---
Created attachment 145567
--> https://bugs.freedesktop.org/attachment.cgi?id=145567&action=edit
lshw log
--
You are receiving this mail because:
You are the assignee for the bug.__
https://bugs.freedesktop.org/show_bug.cgi?id=111848
--- Comment #7 from Martin Jørgensen ---
Created attachment 145569
--> https://bugs.freedesktop.org/attachment.cgi?id=145569&action=edit
lspic -nn output
--
You are receiving this mail because:
You are the assignee for the bug.__
https://bugs.freedesktop.org/show_bug.cgi?id=111848
--- Comment #6 from Martin Jørgensen ---
Created attachment 145568
--> https://bugs.freedesktop.org/attachment.cgi?id=145568&action=edit
lsmod amdgpu
--
You are receiving this mail because:
You are the assignee for the bug.__
https://bugs.freedesktop.org/show_bug.cgi?id=111848
--- Comment #8 from Martin Jørgensen ---
Created attachment 145570
--> https://bugs.freedesktop.org/attachment.cgi?id=145570&action=edit
lspci -vnn output
--
You are receiving this mail because:
You are the assignee for the bug._
https://bugs.freedesktop.org/show_bug.cgi?id=111848
--- Comment #9 from Martin Jørgensen ---
Created attachment 145571
--> https://bugs.freedesktop.org/attachment.cgi?id=145571&action=edit
modinfo amdgpu output
--
You are receiving this mail because:
You are the assignee for the bug._
https://bugs.freedesktop.org/show_bug.cgi?id=111848
--- Comment #10 from Martin Jørgensen ---
Created attachment 145572
--> https://bugs.freedesktop.org/attachment.cgi?id=145572&action=edit
package log output
--
You are receiving this mail because:
You are the assignee for the bug.___
https://bugs.freedesktop.org/show_bug.cgi?id=111848
--- Comment #11 from Martin Jørgensen ---
Created attachment 145573
--> https://bugs.freedesktop.org/attachment.cgi?id=145573&action=edit
uname -a output
--
You are receiving this mail because:
You are the assignee for the bug.__
https://bugs.freedesktop.org/show_bug.cgi?id=111848
--- Comment #12 from Martin Jørgensen ---
Created attachment 145574
--> https://bugs.freedesktop.org/attachment.cgi?id=145574&action=edit
Xorg log
--
You are receiving this mail because:
You are the assignee for the bug._
https://bugs.freedesktop.org/show_bug.cgi?id=111691
--- Comment #13 from Michael Haworth ---
running Xubuntu 19.10 - version information below (sorry for not providing it
earlier):
linux-firmware (1.182) eoan; urgency=medium
* Rebase against
git://git.kernel.org/pub/scm/linux/kernel/git/firmw
https://bugs.freedesktop.org/show_bug.cgi?id=111691
--- Comment #14 from Michael Haworth ---
Created attachment 145575
--> https://bugs.freedesktop.org/attachment.cgi?id=145575&action=edit
xorg log on xubuntu 19.10 (where bug is not present)
--
You are receiving this mail because:
You are the
https://bugs.freedesktop.org/show_bug.cgi?id=111849
Bug ID: 111849
Summary: X11 blank screen when starting plasma on amdgpu
Product: DRI
Version: unspecified
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
https://bugs.freedesktop.org/show_bug.cgi?id=111482
--- Comment #22 from Leon ---
(In reply to Andrew Sheldon from comment #20)
> (In reply to Leon from comment #19)
> > By the way, since I have a x470 mb, it cannot be related to PCI express 4.0.
> > It's also not related to dual displays, since
https://bugs.freedesktop.org/show_bug.cgi?id=109955
--- Comment #109 from jeroenimo ---
(In reply to Wilko Bartels from comment #108)
> Did u try the amdgpu-pro driver as well?
> i just did four runs of glmark and it just went through for me. going up to
> 1600mhz shader clock. tested both closed
https://bugs.freedesktop.org/show_bug.cgi?id=109955
--- Comment #110 from Rodney A Morris ---
(In reply to Rodney A Morris from comment #104)
> (In reply to Mauro Gaspari from comment #103)
> > (In reply to Rodney A Morris from comment #101)
> > > (In reply to Rodney A Morris from comment #99)
>
https://bugs.freedesktop.org/show_bug.cgi?id=111747
--- Comment #10 from CI Bug Log ---
A CI Bug Log filter associated to this bug has been updated:
{- TGL: igt@* -incomplete - Abort requested by .* terminating children -}
{+ TGL: igt@* -incomplete - Abort requested by .* terminating children +}
https://bugs.freedesktop.org/show_bug.cgi?id=111747
--- Comment #11 from CI Bug Log ---
A CI Bug Log filter associated to this bug has been updated:
{- TGL: igt@* -incomplete - Abort requested by .* terminating children -}
{+ TGL: igt@* -incomplete - Abort requested by .* terminating children +}
https://bugs.freedesktop.org/show_bug.cgi?id=110886
--- Comment #22 from Kai-Heng Feng ---
(In reply to Andrey Grodzovsky from comment #21)
> In fact please rebase latest drm-next from here -
> https://cgit.freedesktop.org/~agd5f/linux/log/?h=amd-staging-drm-next, there
> are 2 changes by Alex in
https://bugs.freedesktop.org/show_bug.cgi?id=110886
--- Comment #23 from Kai-Heng Feng ---
Created attachment 145576
--> https://bugs.freedesktop.org/attachment.cgi?id=145576&action=edit
journalctl last boot kernel message
--
You are receiving this mail because:
You are the assignee for the b
https://bugs.freedesktop.org/show_bug.cgi?id=111847
--- Comment #1 from Sebastián Lacuesta ---
Well, just updated drivers in Windows, used sound from TV. Then reboot on Linux
and problem solved. I have rebooted several times on Linux before doing this
and problem persisted. Now it looks everythin
On Thu, Sep 26, 2019 at 04:24:47PM +0800, Sandy Huang wrote:
> These new format is supported by some rockchip socs:
>
> DRM_FORMAT_NV12_10/DRM_FORMAT_NV21_10
> DRM_FORMAT_NV16_10/DRM_FORMAT_NV61_10
> DRM_FORMAT_NV24_10/DRM_FORMAT_NV42_10
>
> Signed-off-by: Sandy Huang
> ---
> drivers/gpu/drm/dr
On Fri, Sep 27, 2019 at 06:31:24PM -0700, Jeykumar Sankaran wrote:
> The mode_config max width/height values determine the maximum
> resolution the pixel reader can handle. But the same values are
> used to restrict the size of the framebuffer creation. Hardware's
> with scaling blocks can operate
https://bugzilla.kernel.org/show_bug.cgi?id=202043
Martin Böh (mar...@outlook.de) changed:
What|Removed |Added
CC||mar...@outlook.de
--- Co
On Wed, Sep 25, 2019 at 03:58:31PM -0700, Derek Basehore wrote:
> Devicetree systems can set panel orientation via a panel binding, but
> there's no way, as is, to propagate this setting to the connector,
> where the property need to be added.
> To address this, this patch sets orientation, as well
On Fri, Sep 27, 2019 at 9:57 PM Steven Price wrote:
>
> On 27/09/2019 14:46, Qiang Yu wrote:
> > drm_gem_objects_lookup does not use user space bo handles
> > directly and left the user to kernel copy work to a new
> > interface drm_gem_objects_lookup_user.
> >
> > This is for driver like lima whi
On Mon, Sep 23, 2019 at 12:39:20PM +, Simon Ser wrote:
> Currently the property docs don't specify whether it's okay for two planes to
> have the same zpos value and what user-space should expect in this case.
>
> The rule mentionned in the past was to disambiguate with object IDs. However
> s
On Mon, Sep 23, 2019 at 10:10:26AM +, Mihail Atanassov wrote:
> When initially turning a crtc on, drm_reset_vblank_timestamp will
> set the vblank timestamp to 0 for any driver that doesn't provide
> a ->get_vblank_timestamp() hook.
>
> Unfortunately, the FLIP_COMPLETE event depends on that ti
https://bugs.freedesktop.org/show_bug.cgi?id=111729
--- Comment #2 from p...@phi-gamma.net ---
I can confirm this bug.
Same phenomenology here with 5.2.11, two screens, and a
01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Lexa
PRO [Radeon RX 550/550X] (rev c7)
Sep 29
36 matches
Mail list logo
