All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 107432] Periodic complete system lockup with Vega M and Kernel 4.18-rc6+
Date: Fri, 03 Aug 2018 17:32:44 +0000	[thread overview]
Message-ID: <bug-107432-502-vspqhIWGa3@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-107432-502@http.bugs.freedesktop.org/>


[-- Attachment #1.1: Type: text/plain, Size: 1029 bytes --]

https://bugs.freedesktop.org/show_bug.cgi?id=107432

--- Comment #7 from Robert Strube <rstrube@gmail.com> ---
(In reply to Michel Dänzer from comment #6)
> Well, https://bugs.freedesktop.org/attachment.cgi?id=140903 definitely shows
> an amdgpu issue exacerbating the memory pressure situation — it tries to
> allocate 4M of physically contiguous memory. My patch fixes that. Can you
> confirm that the patch at least doesn't cause any additional issues of its
> own?

Hey! Good point.

I ran the custom kernel for a couple days without issue.  Would you like me to
do some more testing? I went back to vanilla 4.18-rc7 - but I'd be happy to
make my daily driver 4.18-rc7 with the patch.

My understanding is that kvmalloc is a slightly safer way of allocating memory
as compared to kmalloc - in that it doesn't necessarily need the memory to be
contiguous.  The downside is that it's not quite a performant.  Is this
correct?

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 2048 bytes --]

[-- Attachment #2: Type: text/plain, Size: 160 bytes --]

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  parent reply	other threads:[~2018-08-03 17:32 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-31  1:10 [Bug 107432] Periodic complete system lockup with Vega M and Kernel 4.18-rc6+ bugzilla-daemon
2018-07-31  1:31 ` bugzilla-daemon
2018-07-31  9:00 ` bugzilla-daemon
2018-07-31  9:09 ` bugzilla-daemon
2018-08-02  5:47 ` bugzilla-daemon
2018-08-02  5:59 ` bugzilla-daemon
2018-08-02  8:16 ` bugzilla-daemon
2018-08-02 17:21 ` bugzilla-daemon
2018-08-02 17:23 ` bugzilla-daemon
2018-08-03  7:32 ` bugzilla-daemon
2018-08-03 17:32 ` bugzilla-daemon [this message]
2018-08-06 18:33 ` bugzilla-daemon
2018-08-14 10:52 ` bugzilla-daemon
2018-10-05 20:59 ` bugzilla-daemon
2018-10-09 10:01 ` bugzilla-daemon
2018-10-23 23:24 ` 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-107432-502-vspqhIWGa3@http.bugs.freedesktop.org/ \
    --to=bugzilla-daemon@freedesktop.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.