From: bugzilla-daemon@bugzilla.kernel.org
To: linuxppc-dev@lists.ozlabs.org
Subject: [Bug 200055] WARNING: CPU: 0 PID: 1 at kernel/locking/lockdep.c:3214 .__lockdep_init_map+0x260/0x270
Date: Sun, 14 Jul 2019 10:46:08 +0000 [thread overview]
Message-ID: <bug-200055-206035-KsIYST9c7z@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-200055-206035@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=200055
--- Comment #15 from Erhard F. (erhard_f@mailbox.org) ---
Created attachment 283675
--> https://bugzilla.kernel.org/attachment.cgi?id=283675&action=edit
dmesg.txt (G5 11,2 + kernel 4.9.184)
By running some older kernels from the stable series I noticed that 4.4.x and
4.9.x are not affected by this lockdep issue. First stable series it shows up
is 4.14.x.
I am rather curious what a bisect will throw up when I have time to do it. ;)
--
You are receiving this mail because:
You are watching the assignee of the bug.
next parent reply other threads:[~2019-07-14 10:47 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-200055-206035@https.bugzilla.kernel.org/>
2019-07-14 10:46 ` bugzilla-daemon [this message]
2019-07-14 10:47 ` [Bug 200055] WARNING: CPU: 0 PID: 1 at kernel/locking/lockdep.c:3214 .__lockdep_init_map+0x260/0x270 bugzilla-daemon
2019-07-14 10:48 ` bugzilla-daemon
2019-07-14 10:49 ` bugzilla-daemon
2019-07-27 22:47 ` bugzilla-daemon
2019-07-27 22:48 ` bugzilla-daemon
2019-07-27 23:00 ` bugzilla-daemon
2020-12-28 14:23 ` [Bug 200055] [Bisected][Regression] " bugzilla-daemon
2020-12-28 14:23 ` bugzilla-daemon
2022-03-12 22:07 ` bugzilla-daemon
2022-03-12 22:08 ` bugzilla-daemon
2022-03-12 22:08 ` 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-200055-206035-KsIYST9c7z@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.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.