From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 107652] amdgpu couldn't resume after suspend
Date: Thu, 30 Aug 2018 20:01:56 +0000 [thread overview]
Message-ID: <bug-107652-502-YygSxKdqgN@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-107652-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 960 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=107652
--- Comment #11 from Andrey Grodzovsky <andrey.grodzovsky@amd.com> ---
I see from the log that your failure was on 0 order allocation (1 page) in zone
NORMAL but this ZONE still had enough 1 page blocks and even larger blocks to
fulfill your request so that strange.
The only problem I see from the logs is that your free memory in zone NORMAL
was lower then min watermark watermark, which AFAIK this should have triggered
kswapd to start swapping out memory. I do see you have already some pages in
swap so maybe that it.
Any way , I can't understand why exactly that failed from the logs. Possibly
some memory leaks.
Please add cat /sys/kernel/debug/dri/0/amdgpu_gem_info immdialy before and
after suspend operation to see how much memory the driver allocated.
I will try to ask people from #mm about your log.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1729 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-30 20:01 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-21 21:05 [Bug 107652] amdgpu couldn't resume after suspend bugzilla-daemon
2018-08-21 21:05 ` bugzilla-daemon
2018-08-28 16:54 ` bugzilla-daemon
2018-08-28 20:28 ` bugzilla-daemon
2018-08-28 20:29 ` bugzilla-daemon
2018-08-28 22:18 ` bugzilla-daemon
2018-08-29 4:27 ` bugzilla-daemon
2018-08-29 4:27 ` bugzilla-daemon
2018-08-29 4:29 ` bugzilla-daemon
2018-08-29 4:30 ` bugzilla-daemon
2018-08-29 15:57 ` bugzilla-daemon
2018-08-30 20:01 ` bugzilla-daemon [this message]
2018-08-31 3:51 ` bugzilla-daemon
2018-08-31 3:52 ` bugzilla-daemon
2018-09-20 19:21 ` bugzilla-daemon
2018-09-21 3:21 ` bugzilla-daemon
2018-09-21 3:22 ` bugzilla-daemon
2019-01-09 17:47 ` bugzilla-daemon
2019-11-19 8:48 ` 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-107652-502-YygSxKdqgN@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.