From: bugzilla-daemon@bugzilla.kernel.org
To: linuxppc-dev@lists.ozlabs.org
Subject: [Bug 200055] [Bisected][Regression] WARNING: CPU: 0 PID: 1 at kernel/locking/lockdep.c:3214 .__lockdep_init_map+0x260/0x270
Date: Mon, 28 Dec 2020 14:23:12 +0000 [thread overview]
Message-ID: <bug-200055-206035-fYfUgbupKV@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-200055-206035@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=200055
Erhard F. (erhard_f@mailbox.org) changed:
What |Removed |Added
----------------------------------------------------------------------------
Attachment #283675|0 |1
is obsolete| |
Attachment #283677|0 |1
is obsolete| |
--- Comment #22 from Erhard F. (erhard_f@mailbox.org) ---
Created attachment 294375
--> https://bugzilla.kernel.org/attachment.cgi?id=294375&action=edit
dmesg (kernel 5.11-rc1, G5 11,2)
Still in 5.11-rc1.
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2020-12-28 14:27 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 ` [Bug 200055] WARNING: CPU: 0 PID: 1 at kernel/locking/lockdep.c:3214 .__lockdep_init_map+0x260/0x270 bugzilla-daemon
2019-07-14 10:47 ` 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 ` bugzilla-daemon [this message]
2020-12-28 14:23 ` [Bug 200055] [Bisected][Regression] " 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-fYfUgbupKV@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).