<html>
<head>
<base href="https://bugs.freedesktop.org/">
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - Kernel panic after modesetting (not on every boot) on ryzen 5 2400g"
href="https://bugs.freedesktop.org/show_bug.cgi?id=106225#c20">Comment # 20</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - Kernel panic after modesetting (not on every boot) on ryzen 5 2400g"
href="https://bugs.freedesktop.org/show_bug.cgi?id=106225">bug 106225</a>
from <span class="vcard"><a class="email" href="mailto:michel@daenzer.net" title="Michel Dänzer <michel@daenzer.net>"> <span class="fn">Michel Dänzer</span></a>
</span></b>
<pre>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". :) Does
enabling CONFIG_DEBUG_INFO_REDUCED as well allow you to keep debugging symbols
for everything, or at least for the vmlinuz image?</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>