From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 102322] System crashes after "[drm] IP block:gmc_v8_0 is hung!" / [drm] IP block:sdma_v3_0 is hung! Date: Thu, 28 Jun 2018 10:33:22 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0591171573==" Return-path: Received: from culpepper.freedesktop.org (culpepper.freedesktop.org [IPv6:2610:10:20:722:a800:ff:fe98:4b55]) by gabe.freedesktop.org (Postfix) with ESMTP id 4020D6ECD3 for ; Thu, 28 Jun 2018 10:33:22 +0000 (UTC) In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dri-devel-bounces@lists.freedesktop.org Sender: "dri-devel" To: dri-devel@lists.freedesktop.org List-Id: dri-devel@lists.freedesktop.org --===============0591171573== Content-Type: multipart/alternative; boundary="15301820021.973c.3907" Content-Transfer-Encoding: 7bit --15301820021.973c.3907 Date: Thu, 28 Jun 2018 10:33:22 +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=3D102322 --- Comment #17 from Andrey Grodzovsky --- (In reply to Alex Deucher from comment #16) > (In reply to Andrey Grodzovsky from comment #15) > > I think it just means systems with large VRAM so it will require large = BAR > > for mapping. But I am not sure on that point. >=20 > That's correct. the updates are done with the CPU rather than the GPU > (SDMA). The default BAR size on most systems is usually 256MB for 32 bit > compatibility so the window for CPU access to vram (where the page tables > live) is limited. Thanks Alex. dwagner, this is obviously just a work around and not a fix. It points to s= ome problem with SDMA packets, if you want to continue exploring we can try to = dump some fence traces and SDMA HW ring content to examine the latest packets be= fore the hang happened. --=20 You are receiving this mail because: You are the assignee for the bug.= --15301820021.973c.3907 Date: Thu, 28 Jun 2018 10:33:22 +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

Comme= nt # 17 on bug 10232= 2 from Andrey Grodzovsky 
(In reply to Alex Deucher from comment #16)
> (In reply to Andrey Grodzovsky from comment #15)
> > I think it just means systems with large VRAM so it will require =
large BAR
> > for mapping. But I am not sure on that point.
>=20
> That's correct.  the updates are done with the CPU rather than the GPU
> (SDMA).  The default BAR size on most systems is usually 256MB for 32 =
bit
> compatibility so the window for CPU access to vram (where the page tab=
les
> live) is limited.

Thanks Alex.

dwagner, this is obviously just a work around and not a fix. It points to s=
ome
problem with SDMA packets, if you want to continue exploring we can try to =
dump
some fence traces and SDMA HW ring content to examine the latest packets be=
fore
the hang happened.

You are receiving this mail because:
  • You are the assignee for the bug.
= --15301820021.973c.3907-- --===============0591171573== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHBzOi8vbGlz dHMuZnJlZWRlc2t0b3Aub3JnL21haWxtYW4vbGlzdGluZm8vZHJpLWRldmVsCg== --===============0591171573==--