dri-devel.lists.freedesktop.org archive mirror
 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: Thu, 02 Aug 2018 17:21:53 +0000	[thread overview]
Message-ID: <bug-107432-502-VToVTd2HHg@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-107432-502@http.bugs.freedesktop.org/>


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

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

--- Comment #5 from Robert Strube <rstrube@gmail.com> ---
So I've been conducting lots of additional investigation with both the vanilla
kernel (4.18-rc7) and the kernel with your patch.

I took more time to try to recreate the scenarios that cause the crash
(monitoring system resources, etc.) and this is when I realized that my
swapfile was very small (only 2GB).

Short story - Upon further investigation I don't believe this is a bug with
DRM/amdgpu but rather the crash was caused because I simply ran out of memory
*and* swapspace combined.

I feel a little silly about this, I'm running Ubuntu 18.04 and I guess the
default swapfile size is 2GB.  I'm used to using swap partions which are the
same size as the system RAM, so I never considered that I could be running out
of *both*.

I think at this point it's safe to close the bug.  I'm going to increase my
swapfile size to 16GB and monitor my system more closely.  If I get the hard
system crash I'll first determine if I ran out of swap, and then if it appears
I had enough swap, I'll reopen this bug.

Thanks for your assistance!

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

[-- Attachment #1.2: Type: text/html, Size: 2062 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-02 17:21 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 [this message]
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-VToVTd2HHg@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).