From: bugzilla-daemon@bugzilla.kernel.org
To: linuxppc-dev@lists.ozlabs.org
Subject: [Bug 213221] New: Lockdep self tests failing on e6500 system
Date: Wed, 26 May 2021 14:33:41 +0000 [thread overview]
Message-ID: <bug-213221-206035@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=213221
Bug ID: 213221
Summary: Lockdep self tests failing on e6500 system
Product: Platform Specific/Hardware
Version: 2.5
Kernel Version: 5.12.6
Hardware: All
OS: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: PPC-64
Assignee: platform_ppc-64@kernel-bugs.osdl.org
Reporter: mail@jakemoroni.com
Regression: No
Created attachment 296989
--> https://bugzilla.kernel.org/attachment.cgi?id=296989&action=edit
lcokdep self test failures
Hello,
I noticed that some of the lockdep self tests are failing on my device. The
system is based on an NXP T2080 SoC, which has four 64-bit Power PC e6500 cores
(2 threads each).
See attached log.
I'm running kernel 5.12.6 straight from kernel dot org. No modifications.
For what it's worth, I have been experiencing random instability issues, which
is what prompted me to enable lock debugging in the first place.
Thanks,
- Jake
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
reply other threads:[~2021-05-26 14:34 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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-213221-206035@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.