From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 107229] Metro 2033 Redux hangs
Date: Sat, 04 Aug 2018 11:34:52 +0000 [thread overview]
Message-ID: <bug-107229-502-5Dk0EWiGJt@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-107229-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 721 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=107229
--- Comment #7 from Alexander Tsoy <alexander@tsoy.me> ---
Created attachment 140964
--> https://bugs.freedesktop.org/attachment.cgi?id=140964&action=edit
dmesg
Same problem with the latest amd-staging-drm-next (commit
bf1fd52b0632cd17ac875432a36d3e92be96d8cb). Now the kernel gives me the
following errors:
[ 324.552371] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR*
amdgpu_cs_list_validate(validated) failed.
[ 324.561030] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Not enough memory for
command submission!
And with CONFIG_TRANSPARENT_HUGEPAGE=y the same kernel works fine.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1552 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-04 11:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-14 20:38 [Bug 107229] Metro 2033 Redux hangs bugzilla-daemon
2018-07-14 20:44 ` bugzilla-daemon
2018-07-15 16:52 ` bugzilla-daemon
2018-07-16 9:44 ` bugzilla-daemon
2018-07-16 10:15 ` bugzilla-daemon
2018-07-16 10:18 ` bugzilla-daemon
2018-07-16 10:19 ` bugzilla-daemon
2018-08-04 11:34 ` bugzilla-daemon [this message]
2019-11-19 8:43 ` 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-107229-502-5Dk0EWiGJt@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