We need to make sure implementations don't cheat and don't have a
possible schedule/blocking point deeply burried where review can't
catch it.
I'm not sure whether this is the best way to make sure all the
might_sleep() callsites trigger, and it's a bit ugly in the code flow.
But it gets the job
https://bugs.freedesktop.org/show_bug.cgi?id=108781
--- Comment #18 from freedesk...@nuclearsunshine.com ---
I just hit this as well with 4.19 on Fedora and a R9 390X - Grub shows fine,
then no video output after that (monitor goes into power save), and boot
doesn't seem to continue (no disk
https://bugs.freedesktop.org/show_bug.cgi?id=106175
--- Comment #58 from Nicholas Kazlauskas ---
(In reply to Brandon Wright from comment #55)
> Created attachment 142558 [details] [review]
> Patch that "fixes" the problem.
>
> I've attached a patch that fixes the problem for me. It copies
https://bugs.freedesktop.org/show_bug.cgi?id=106175
--- Comment #61 from tempel.jul...@gmail.com ---
Thanks a lot @ Brandon Wright, your patch really does the trick. I also totally
agree on your opinion that it should be mainlined as at least a temporary
solution (and also get backported to older
https://bugs.freedesktop.org/show_bug.cgi?id=105733
--- Comment #51 from Allan ---
Tried to install the RX480 on the other PC : the card is too big that it
touches the RAM slot's tabs. Can't install it.
In time, seems like the errors delay a little bit when setting
randomize_va_space=0. Was
https://bugs.freedesktop.org/show_bug.cgi?id=108781
--- Comment #19 from Jim Haddad ---
This happened to me 7 days ago when Fedora replaced kernel-4.18.18-300.fc29
with kernel-4.19.2-300.fc29. Also on kernel-4.19.3-300.fc29 from yesterday.
On a different hard drive I tried rawhide and
https://bugs.freedesktop.org/show_bug.cgi?id=107978
--- Comment #17 from Shmerl ---
(In reply to Nicholas Kazlauskas from comment #13)
>
> This does help narrow down the problem, thanks.
Is there any chance of fixing this in 4.20?
--
You are receiving this mail because:
You are the assignee
https://bugs.freedesktop.org/show_bug.cgi?id=106175
--- Comment #63 from bmil...@gmail.com ---
(In reply to Brandon Wright from comment #62)
> (In reply to tempel.julian from comment #61)
> > I just noticed that it works fine with xf86-video-amdgpu driver, but with
> > modesetting driver, xorg or
https://bugs.freedesktop.org/show_bug.cgi?id=105733
--- Comment #52 from fin4...@hotmail.com ---
To prevent random kernel lock ups with Ryzen, fix this with bios, set to
Typical Current Idle in the bios Advanced/AMD CBS menu.
Use latest AMD wip kernel and Oibaf ppa Mesa. Disable display
https://bugs.freedesktop.org/show_bug.cgi?id=105733
--- Comment #53 from fin4...@hotmail.com ---
Created attachment 142573
--> https://bugs.freedesktop.org/attachment.cgi?id=142573=edit
AMD wip kernel config with 1000Hz timer
--
You are receiving this mail because:
You are the assignee for
Hi Boris,
Just because I happened to read the docs in here, one typo below:
On Thu, Nov 22, 2018 at 12:23:29PM +0100, Boris Brezillon wrote:
>We have 3 drivers defining the "underscan", "underscan hborder" and
>"underscan vborder" properties (radeon, amd and nouveau) and we are
>about to add the
Am 22.11.18 um 17:51 schrieb Daniel Vetter:
> Just a bit of paranoia, since if we start pushing this deep into
> callchains it's hard to spot all places where an mmu notifier
> implementation might fail when it's not allowed to.
>
> Cc: Andrew Morton
> Cc: Michal Hocko
> Cc: "Christian König"
>
https://bugs.freedesktop.org/show_bug.cgi?id=106175
--- Comment #62 from Brandon Wright ---
(In reply to tempel.julian from comment #61)
> I just noticed that it works fine with xf86-video-amdgpu driver, but with
> modesetting driver, xorg or the driver freezes when starting/logging in. Not
>
Am 22.11.18 um 17:51 schrieb Daniel Vetter:
> We need to make sure implementations don't cheat and don't have a
> possible schedule/blocking point deeply burried where review can't
> catch it.
>
> I'm not sure whether this is the best way to make sure all the
> might_sleep() callsites trigger, and
https://bugs.freedesktop.org/show_bug.cgi?id=106175
--- Comment #64 from Nicholas Kazlauskas ---
Created attachment 142574
--> https://bugs.freedesktop.org/attachment.cgi?id=142574=edit
0001-drm-amd-display-Add-fast-path-for-legacy-cursor-plan.patch
This patch is similar to the async_update
From: Philip Yang
[ Upstream commit c837243ff4017f493c7d6f4ab57278d812a86859 ]
The bug limits the IH ring wptr address to 40bit. When the system memory
is bigger than 1TB, the bus address is more than 40bit, this causes the
interrupt cannot be handled and cleared correctly.
Reviewed-by:
https://bugs.freedesktop.org/show_bug.cgi?id=108844
Bug ID: 108844
Summary: not a crical prblem
Product: DRI
Version: XOrg git
Hardware: x86-64 (AMD64)
OS: All
Status: NEW
Severity: minor
https://bugs.freedesktop.org/show_bug.cgi?id=108845
Bug ID: 108845
Summary: login button not working as expected
Product: DRI
Version: DRI git
Hardware: All
OS: All
Status: NEW
Severity: normal
https://bugs.freedesktop.org/show_bug.cgi?id=108845
jyotiba changed:
What|Removed |Added
URL||http://www.newtours.demoaut
https://bugs.freedesktop.org/show_bug.cgi?id=106175
--- Comment #65 from bmil...@gmail.com ---
(In reply to Nicholas Kazlauskas from comment #64)
> Created attachment 142574 [details] [review]
> 0001-drm-amd-display-Add-fast-path-for-legacy-cursor-plan.patch
>
> This patch is similar to the
https://bugs.freedesktop.org/show_bug.cgi?id=106175
--- Comment #66 from Brandon Wright ---
(In reply to bmilreu from comment #65)
> Is there an easy way to backport this to 4.19 mainline? Would be very useful
> to integrate the fix into stable kernels.
>
> As it is currently it wont work on
Hi all,
Today's linux-next merge of the drm-misc tree got a conflict in:
drivers/gpu/drm/Makefile
between commit:
2bb42410b1bd ("drm: Remove drm_global.{c,h} v2")
from the drm tree and commit:
c6fdea6e1a19 ("drm: Merge drm_info.c into drm_debugfs.c")
from the drm-misc tree.
I fixed
Hi Linus,
Regular drm fixes pull for rc4.
amdgpu: Vega20 fixes, firmware loading fix, panel display fix, override fix
i915: Sandybridge lockup fix, fastboot DSI panel fix, GPU hang on
Broxton, GPU reloc fixes on pineview/bearlake
ast: screen blurring fix, cursor appearance fix
udmabuf: mmap fix
Hi Helen,
On Fri, Nov 23, 2018 at 8:31 AM Helen Koike wrote:
>
> Hi Tomasz,
>
> On 11/20/18 4:48 AM, Tomasz Figa wrote:
> > Hi Helen,
> >
> > On Tue, Nov 20, 2018 at 4:08 AM Helen Koike
> > wrote:
> >>
> >> From: Enric Balletbo i Serra
> >>
> >> Add support to async updates of cursors by
On 2018年11月22日 19:30, Christian König wrote:
Am 22.11.18 um 07:52 schrieb zhoucm1:
On 2018年11月15日 19:12, Christian König wrote:
Implement finding the right timeline point in drm_syncobj_find_fence.
Signed-off-by: Christian König
---
drivers/gpu/drm/drm_syncobj.c | 10 +-
1
Hi,
I have recently tried to use dpm=1 with the amdgpu driver for the 4.19.x
kernel, but unfortunately the screen just went black. This is a regression
from the 4.18.x kernel.
I have attached the full dmesg log, but the relevant section look to be:
[8.958679] WARNING: CPU: 0 PID: 320 at
https://bugs.freedesktop.org/show_bug.cgi?id=108843
Bug ID: 108843
Summary: Laptop with ATI RX 580 doesn't turn the screen on when
resuming.
Product: DRI
Version: DRI git
Hardware: x86-64 (AMD64)
OS: Linux
https://bugs.freedesktop.org/show_bug.cgi?id=108843
--- Comment #1 from alex14...@yahoo.com ---
Created attachment 142583
--> https://bugs.freedesktop.org/attachment.cgi?id=142583=edit
Kernel config file
--
You are receiving this mail because:
You are the assignee for the
Hi Michael,
On Fri, Nov 23, 2018 at 1:58 PM Michael Zoran wrote:
>
> On Fri, 2018-11-23 at 11:27 +0900, Tomasz Figa wrote:
> >
> > The point here is not about setting and resetting the plane->fb
> > pointer. It's about what happens inside
> > drm_atomic_set_fb_for_plane().
> >
> > It calls
https://bugs.freedesktop.org/show_bug.cgi?id=108845
Tapani Pälli changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
101 - 130 of 130 matches
Mail list logo
