All of 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: Thu, 10 Sep 2020 04:19:29 +0000	[thread overview]
Message-ID: <bug-209163-2300-ER9faHZ4nE@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 #8 from Satish patel (satish.in@outlook.in) ---
(In reply to Christian König from comment #6)
> You are running out of VRAM, not system memory.
> 
> Can you test this on an up to date kernel as well?

Is there any way to restrict not utilize full VRAM by AMDGPU module parameter
settings ? same application running with on same hardware in Gnome desktop 
(Centos 7) with kernel 3.10.xx.1127 . 

I am getting error when Utilize same application in X Windows and getting error
after 19 hours.  where same application running more than 7 days with above
Operating system and kernel version.

-- 
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-10  4:19 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
2020-09-09 18:26 ` bugzilla-daemon
2020-09-10  4:08 ` bugzilla-daemon
2020-09-10  4:19 ` bugzilla-daemon [this message]
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-ER9faHZ4nE@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 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.