dri-devel.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 207763] Noisy Screen in Linux with kernel 5
Date: Thu, 28 May 2020 07:38:50 +0000	[thread overview]
Message-ID: <bug-207763-2300-MxN8RQHcfY@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-207763-2300@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=207763

--- Comment #3 from Mohammad Naeim (xunilarium@gmail.com) ---
(In reply to Alex Deucher from comment #1)
> Does reverting:
> 
> commit 33b3ad3788aba846fc8b9a065fe2685a0b64f713
> Author: Christoph Hellwig <hch@lst.de>
> Date:   Thu Aug 15 09:27:00 2019 +0200
> 
>     drm/radeon: handle PCIe root ports with addressing limitations
>     
>     radeon uses a need_dma32 flag to indicate to the drm core that some
>     allocations need to be done using GFP_DMA32, but it only checks the
>     device addressing capabilities to make that decision.  Unfortunately
>     PCIe root ports that have limited addressing exist as well.  Use the
>     dma_addressing_limited instead to also take those into account.
>     
>     Reviewed-by: Christian König <christian.koenig@amd.com>
>     Reported-by: Atish Patra <Atish.Patra@wdc.com>
>     Signed-off-by: Christoph Hellwig <hch@lst.de>
>     Signed-off-by: Alex Deucher <alexander.deucher@amd.com>
> 
> 
> Fix the issue?

I did this and the issue still exists:
https://www.reddit.com/r/linuxquestions/comments/gqrk3m/noisy_screen_in_linux_with_kernel_5/

-- 
You are receiving this mail because:
You are watching the assignee of the bug.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  parent reply	other threads:[~2020-05-28  7:38 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-17  8:29 [Bug 207763] New: Noisy Screen in Linux with kernel 5 bugzilla-daemon
2020-05-17 16:42 ` [Bug 207763] " bugzilla-daemon
2020-05-28  7:37 ` bugzilla-daemon
2020-05-28  7:38 ` bugzilla-daemon [this message]
2020-08-17 15:13 ` bugzilla-daemon
2020-09-16 20:51 ` bugzilla-daemon
2020-09-16 22:06 ` bugzilla-daemon
2021-02-06 16:34 ` bugzilla-daemon
2021-02-06 16:37 ` bugzilla-daemon
2021-12-12 16:55 ` bugzilla-daemon
2021-12-12 16:57 ` bugzilla-daemon

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-207763-2300-MxN8RQHcfY@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@bugzilla.kernel.org \
    --cc=dri-devel@lists.freedesktop.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).