From: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
To: hansg@kernel.org, vadimp@nvidia.com,
David Thompson <davthompson@nvidia.com>
Cc: platform-driver-x86@vger.kernel.org,
linux-kernel@vger.kernel.org,
Shravan Kumar Ramani <shravankr@nvidia.com>
Subject: Re: [PATCH v2] platform/mellanox: mlxbf-pmc: add sysfs_attr_init() to count_clock init
Date: Wed, 15 Oct 2025 11:31:25 +0300 [thread overview]
Message-ID: <176051708584.2196.14874852596962553290.b4-ty@linux.intel.com> (raw)
In-Reply-To: <20251013155605.3589770-1-davthompson@nvidia.com>
On Mon, 13 Oct 2025 15:56:05 +0000, David Thompson wrote:
> The lock-related debug logic (CONFIG_LOCK_STAT) in the kernel is noting
> the following warning when the BlueField-3 SOC is booted:
>
> [ 10.231318] BUG: key ffff00008a3402a8 has not been registered!
> [ 10.237249] ------------[ cut here ]------------
> [ 10.241914] DEBUG_LOCKS_WARN_ON(1)
> [ 10.241927] WARNING: CPU: 4 PID: 592 at kernel/locking/lockdep.c:4801 lockdep_init_map_type+0x1d4/0x2a0
> <snip>
> [ 10.385415] Call trace:
> [ 10.385417] lockdep_init_map_type+0x1d4/0x2a0
> [ 10.385423] __kernfs_create_file+0x84/0x140
> [ 10.385428] sysfs_add_file_mode_ns+0xcc/0x1cc
> [ 10.385431] internal_create_group+0x110/0x3d4
> [ 10.385434] internal_create_groups.part.0+0x54/0xcc
> [ 10.385436] sysfs_create_groups+0x24/0x40
> [ 10.385438] device_add+0x6e8/0x93c
> [ 10.444559] device_register+0x28/0x40
> [ 10.448299] __hwmon_device_register+0x4b0/0x8a0
> [ 10.452907] devm_hwmon_device_register_with_groups+0x7c/0xe0
> [ 10.458641] mlxbf_pmc_probe+0x1e8/0x3e0 [mlxbf_pmc]
> [ 10.463598] platform_probe+0x70/0x110
>
> [...]
Thank you for your contribution, it has been applied to my local
review-ilpo-fixes branch. Note it will show up in the public
platform-drivers-x86/review-ilpo-fixes branch only once I've pushed my
local branch there, which might take a while.
The list of commits applied:
[1/1] platform/mellanox: mlxbf-pmc: add sysfs_attr_init() to count_clock init
commit: a7b4747d8e0e7871c3d4971cded1dcc9af6af9e9
--
i.
prev parent reply other threads:[~2025-10-15 8:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-13 15:56 David Thompson
2025-10-15 8:31 ` Ilpo Järvinen [this message]
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=176051708584.2196.14874852596962553290.b4-ty@linux.intel.com \
--to=ilpo.jarvinen@linux.intel.com \
--cc=davthompson@nvidia.com \
--cc=hansg@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=platform-driver-x86@vger.kernel.org \
--cc=shravankr@nvidia.com \
--cc=vadimp@nvidia.com \
/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
all inboxes | Powered by JetHome®