dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 209163] amdgpu: The CS has been cancelled because the context is lost
Date: Wed, 09 Sep 2020 18:17:09 +0000	[thread overview]
Message-ID: <bug-209163-2300-RnadTx0Kid@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-209163-2300@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=209163

--- Comment #5 from Satish patel (satish.in@outlook.in) ---
(In reply to Christian König from comment #4)
> This is expected behavior, your application tries to use more memory than
> physical available:
> 
> [71804.930003] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Not enough memory for
> command submission!
> 
> That is most likely a bug in the application, e.g. a memory leak.

Dear Mr. Konig, 

Thanks for your reply , But I would like to inform and describe same
application running up to 10 days until  Physical memory and swap memory not
utilized in CentOS 7 (gnome display ) with kernel 3.10.0-1127.el7.x86_64. 

But same application has error "amdgpu: The CS has been cancelled because the
context is lost" even system utilize only  75% physical memory from Total 5.83
GB Physical memory  and 1% swap memory from 15 GB swap partition. This Error ,
I am getting in Kernel 4.9.118. Why system crash ( Display flickering and touch
screen not responding) and not utilize swap memory area ? . But CPU and memory
utilization showing when monitoring from other system .

-- 
You are receiving this mail because:
You are watching the assignee of the bug.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  parent reply	other threads:[~2020-09-09 18:17 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-05 13:56 [Bug 209163] New: amdgpu: The CS has been cancelled because the context is lost bugzilla-daemon
2020-09-05 14:05 ` [Bug 209163] " bugzilla-daemon
2020-09-05 14:05 ` bugzilla-daemon
2020-09-05 14:15 ` bugzilla-daemon
2020-09-09  9:59 ` bugzilla-daemon
2020-09-09 11:03 ` bugzilla-daemon
2020-09-09 18:17 ` bugzilla-daemon [this message]
2020-09-09 18:26 ` bugzilla-daemon
2020-09-10  4:08 ` bugzilla-daemon
2020-09-10  4:19 ` bugzilla-daemon
2020-09-10  8:39 ` 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-209163-2300-RnadTx0Kid@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@bugzilla.kernel.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