From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org Subject: [Bug 102349] nv4x crashing with plasmashell - gdb log included Date: Thu, 24 Aug 2017 03:58:18 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============2101231833==" Return-path: In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: nouveau-bounces-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org Sender: "Nouveau" To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org List-Id: nouveau.vger.kernel.org --===============2101231833== Content-Type: multipart/alternative; boundary="15035470971.70aD0.1210"; charset="UTF-8" --15035470971.70aD0.1210 Date: Thu, 24 Aug 2017 03:58:17 +0000 MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://bugs.freedesktop.org/ Auto-Submitted: auto-generated https://bugs.freedesktop.org/show_bug.cgi?id=3D102349 --- Comment #5 from Ilia Mirkin --- Actually I have to admit... while I had a plausible explanation for the fir= st instance, I do not for the second. Context deletion correctly cleans this s= tuff up, nv30_state_validate should check if a new context is being used and set= up the new pointers. The way nv30 handles bufctx stuff is different than nv50+, and I don't think it's with good reason. I may try rewriting it. --=20 You are receiving this mail because: You are the assignee for the bug.= --15035470971.70aD0.1210 Date: Thu, 24 Aug 2017 03:58:17 +0000 MIME-Version: 1.0 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://bugs.freedesktop.org/ Auto-Submitted: auto-generated

Commen= t # 5 on bug 10234= 9 from Ilia Mirkin 
Actually I have to admit... while I had a plausible explanatio=
n for the first
instance, I do not for the second. Context deletion correctly cleans this s=
tuff
up, nv30_state_validate should check if a new context is being used and set=
 up
the new pointers.

The way nv30 handles bufctx stuff is different than nv50+, and I don't think
it's with good reason. I may try rewriting it.

You are receiving this mail because:
  • You are the assignee for the bug.
= --15035470971.70aD0.1210-- --===============2101231833== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KTm91dmVhdSBt YWlsaW5nIGxpc3QKTm91dmVhdUBsaXN0cy5mcmVlZGVza3RvcC5vcmcKaHR0cHM6Ly9saXN0cy5m cmVlZGVza3RvcC5vcmcvbWFpbG1hbi9saXN0aW5mby9ub3V2ZWF1Cg== --===============2101231833==--