From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.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 [thread overview]
Message-ID: <bug-106225-502-cFx4FrpNan@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-106225-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 702 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=106225
--- Comment #20 from Michel Dänzer <michel@daenzer.net> ---
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?
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1533 bytes --]
[-- Attachment #2: Type: text/plain, Size: 160 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2018-05-02 9:08 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-24 22:54 [Bug 106225] Kernel panic after modesetting (not on every boot) on ryzen 5 2400g bugzilla-daemon
2018-04-25 8:11 ` bugzilla-daemon
2018-04-25 22:36 ` bugzilla-daemon
2018-04-26 8:54 ` bugzilla-daemon
2018-04-26 8:55 ` bugzilla-daemon
2018-04-26 23:03 ` bugzilla-daemon
2018-04-27 8:07 ` bugzilla-daemon
2018-04-27 13:21 ` bugzilla-daemon
2018-04-27 15:01 ` bugzilla-daemon
2018-04-27 16:05 ` bugzilla-daemon
2018-04-27 16:42 ` bugzilla-daemon
2018-04-27 16:50 ` bugzilla-daemon
2018-04-27 17:14 ` bugzilla-daemon
2018-04-30 8:55 ` bugzilla-daemon
2018-04-30 9:35 ` bugzilla-daemon
2018-04-30 10:15 ` bugzilla-daemon
2018-04-30 10:32 ` bugzilla-daemon
2018-04-30 11:26 ` bugzilla-daemon
2018-04-30 13:00 ` bugzilla-daemon
2018-05-01 0:21 ` bugzilla-daemon
2018-05-02 9:08 ` bugzilla-daemon [this message]
2018-05-02 22:18 ` bugzilla-daemon
2018-05-03 9:03 ` bugzilla-daemon
2018-05-03 9:11 ` bugzilla-daemon
2018-05-03 10:38 ` bugzilla-daemon
2018-05-03 21:46 ` bugzilla-daemon
2018-05-07 9:58 ` bugzilla-daemon
2018-05-25 16:01 ` bugzilla-daemon
2018-05-25 23:12 ` bugzilla-daemon
2018-05-26 0:06 ` bugzilla-daemon
2018-05-28 14:29 ` bugzilla-daemon
2018-05-31 21:56 ` bugzilla-daemon
2018-06-12 19:08 ` bugzilla-daemon
2018-07-12 15:26 ` bugzilla-daemon
2018-07-12 15:28 ` bugzilla-daemon
2018-07-12 15:33 ` bugzilla-daemon
2018-08-02 9:35 ` bugzilla-daemon
2018-09-06 21:29 ` bugzilla-daemon
2018-09-07 7:42 ` bugzilla-daemon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-106225-502-cFx4FrpNan@http.bugs.freedesktop.org/ \
--to=bugzilla-daemon@freedesktop.org \
--cc=dri-devel@lists.freedesktop.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.