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: Thu, 02 Aug 2018 05:47:50 +0000 [thread overview]
Message-ID: <bug-107432-502-CzCEFcg40Y@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-107432-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 1867 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=107432
--- Comment #3 from Robert Strube <rstrube@gmail.com> ---
(In reply to Michel Dänzer from comment #2)
> Created attachment 140905 [details] [review]
> Use kvmalloc in amdgpu_uvd_suspend
>
> Does this patch help by any chance?
>
> If not, can you bisect between 4.18-rc1 and -rc6? Note that from your
> description, you'll need to test for at least one day before declaring a
> commit good (if you hit a failure, you can immediately declare that commit
> bad).
Hi Michel,
Thank you for the patch. I've rebuilt the kernel with the changes in your
patch and am currently going to test it out over the next several days.
I've noticed that the problem seems to occur when there is a large amount of
memory pressure (e.g. I'm running a VM where I've allocated lots of memory),
and almost always after I've just opened a new application windows. Perhaps a
web browser, text editor, etc.
Today I had a scenario (running the vanilla 4.18-rc7) where I simply ran out of
memory *BUT* this occurred in the absence of opening up a new application
window, and the system was able to recover gracefully.
I do have 16GB of RAM in my system, but I can easily hit the limit by running a
VM and opening several applications.
Should I conduct tests with memory pressure applied to see if your patch
addresses the issue? Are we trying to simulate the same scenario as before?
I'll report back my results.
P.S. I've attached another dmesg.log from the out of memory problems I ran into
today (again running on vanilla 4.18-rc7 and not using your patch) so you can
compare the two scenarios. This scenario did not result in a complete system
lockup, so something different must have occurred.
Thanks!
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 3083 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
next prev parent reply other threads:[~2018-08-02 5:47 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 [this message]
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
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-CzCEFcg40Y@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 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).