From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 106225] Kernel panic after modesetting (not on every boot) on ryzen 5 2400g Date: Wed, 02 May 2018 09:08:53 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0858638846==" Return-path: Received: from culpepper.freedesktop.org (culpepper.freedesktop.org [131.252.210.165]) by gabe.freedesktop.org (Postfix) with ESMTP id E55FC6E528 for ; Wed, 2 May 2018 09:08:52 +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 --===============0858638846== Content-Type: multipart/alternative; boundary="15252521320.2a45.25051" Content-Transfer-Encoding: 7bit --15252521320.2a45.25051 Date: Wed, 2 May 2018 09:08:52 +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=3D106225 --- Comment #20 from Michel D=C3=A4nzer --- Now I notice there's another report for firmware_parser_create+0xa9b/0xd90. What does faddr2line say for that? Though it's weird that KASAN claims the memory written in firmware_parser_create was freed from rcu_cpu_kthread. If that's accurate[0= ], it might indicate a lower level issue. [0] There is some doubt about that due to the "Frankenkernel monster". :) D= oes enabling CONFIG_DEBUG_INFO_REDUCED as well allow you to keep debugging symb= ols for everything, or at least for the vmlinuz image? --=20 You are receiving this mail because: You are the assignee for the bug.= --15252521320.2a45.25051 Date: Wed, 2 May 2018 09:08:52 +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 # 20 on bug 10622= 5 from Michel D=C3=A4nzer 
Now I notice there's another report for firmware_parser_create=
+0xa9b/0xd90.
What does faddr2line say for that?

Though it's weird that KASAN claims the memory written in
firmware_parser_create was freed from rcu_cpu_kthread. If that's accurate[0=
],
it might indicate a lower level issue.

[0] There is some doubt about that due to the "Frankenkernel monster&q=
uot;. :) Does
enabling CONFIG_DEBUG_INFO_REDUCED as well allow you to keep debugging symb=
ols
for everything, or at least for the vmlinuz image?

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