From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 105760] [4.17-rc1] RIP: smu7_populate_single_firmware_entry.isra.6+0x57/0xc0 [amdgpu] RSP: ffffa17901efb930 Date: Thu, 12 Jul 2018 06:34:05 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1040016053==" 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 3BE3E6EE5D for ; Thu, 12 Jul 2018 06:34:05 +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 --===============1040016053== Content-Type: multipart/alternative; boundary="15313772452.16e7.8378" Content-Transfer-Encoding: 7bit --15313772452.16e7.8378 Date: Thu, 12 Jul 2018 06:34:05 +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=3D105760 --- Comment #33 from Alex Deucher --- (In reply to Thomas Martitz from comment #21) >=20 > I assume this is some mapped memory and some HW component in the GPU writ= es > to it while the CPU is using it, isn't it? If so, the proper fix would be= to > prevent that but I don't know what's the proper way of doing it in this > context. The CPU is writing to a buffer that the GPU ultimately reads. Even if the = data in the buffer were corrupted by the GPU somehow, the CPU's pointer should s= till be valid. Can you add slub_debug=3DFPZU to the kernel command line in grub= and attach your dmesg output? --=20 You are receiving this mail because: You are the assignee for the bug.= --15313772452.16e7.8378 Date: Thu, 12 Jul 2018 06:34:05 +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 # 33 on bug 10576= 0 from Alex Deucher 
(In reply to Thomas Martitz from comment #21)
>=20
> I assume this is some mapped memory and some HW component in the GPU w=
rites
> to it while the CPU is using it, isn't it? If so, the proper fix would=
 be to
> prevent that but I don't know what's the proper way of doing it in this
> context.

The CPU is writing to a buffer that the GPU ultimately reads.  Even if the =
data
in the buffer were corrupted by the GPU somehow, the CPU's pointer should s=
till
be valid.  Can you add slub_debug=3DFPZU to the kernel command line in grub=
 and
attach your dmesg output?

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