Possibly related (same subject, not in this thread)

• 2019-07-27 · [Bug 200055] WARNING: CPU: 0 PID: 1 at kernel/locking/lockdep.c:3214 .__lockdep_init_map+0x260/0x270 · <hidden>
• 2019-07-27 · [Bug 200055] WARNING: CPU: 0 PID: 1 at kernel/locking/lockdep.c:3214 .__lockdep_init_map+0x260/0x270 · <hidden>
• 2019-07-27 · [Bug 200055] WARNING: CPU: 0 PID: 1 at kernel/locking/lockdep.c:3214 .__lockdep_init_map+0x260/0x270 · <hidden>
• 2019-07-14 · [Bug 200055] WARNING: CPU: 0 PID: 1 at kernel/locking/lockdep.c:3214 .__lockdep_init_map+0x260/0x270 · <hidden>
• 2019-07-14 · [Bug 200055] WARNING: CPU: 0 PID: 1 at kernel/locking/lockdep.c:3214 .__lockdep_init_map+0x260/0x270 · <hidden>

https://bugzilla.kernel.org/show_bug.cgi?id=200055

--- Comment #17 from Erhard F. (erhard_f@mailbox.org) ---

Created attachment 283679
  --> https://bugzilla.kernel.org/attachment.cgi?id=283679&action=edit
4.9.184 kernel .config (G5 11,2)

-- 
You are receiving this mail because:
You are watching the assignee of the bug.