From: Stephen Boyd <sboyd@kernel.org>
To: "Brian Masney" <bmasney@redhat.com>,
"David Gow" <davidgow@google.com>,
"Johannes Berg" <johannes@sipsolutions.net>,
"Michael Turquette" <mturquette@baylibre.com>,
"Peng Fan" <peng.fan@oss.nxp.com>,
"Shuah Khan" <skhan@linuxfoundation.org>,
"Thomas Weißschuh" <thomas.weissschuh@linutronix.de>
Cc: linux-clk@vger.kernel.org, linux-kernel@vger.kernel.org,
Peng Fan <peng.fan@nxp.com>
Subject: Re: [PATCH v2] clk: Disable KUNIT_UML_PCI
Date: Mon, 02 Feb 2026 17:41:47 -0700 [thread overview]
Message-ID: <177007930707.4027.14638082184159958493@lazor> (raw)
In-Reply-To: <20251222-clk-v2-v2-1-83e1a5ed8c7e@nxp.com>
Quoting Peng Fan (OSS) (2025-12-22 00:06:33)
> From: Peng Fan <peng.fan@nxp.com>
>
> commit 031cdd3bc3f3 ("kunit: Enable PCI on UML without triggering WARN()")
> enables KUNIT_UML_PCI, but clk driver could not work with it.
> Deselect KUNIT_UML_PCI to avoid the failure. Dump as below:
> WARNING: CPU: 0 PID: 227 at lib/logic_iomem.c:141 __raw_readl+0xac/0xe0
> CPU: 0 UID: 0 PID: 227 Comm: kunit_try_catch Tainted: G
> Tainted: [N]=TEST
> Stack:
> a0883d00 00000001 00000000 ffffff00
> 603ef142 60044832 6002598b 00000000
> 00000000 600211b3 00000001 00000000
> Call Trace:
> [<6032534c>] ? __raw_readl+0xac/0xe0
> [<60044832>] ? dump_stack_lvl+0x57/0x73
> [<6002598b>] ? _printk+0x0/0x61
> [<600211b3>] ? __warn.cold+0x61/0xeb
> [<600212cc>] ? warn_slowpath_fmt+0x8f/0x9c
> [<6002123d>] ? warn_slowpath_fmt+0x0/0x9c
> [<6032534c>] ? __raw_readl+0xac/0xe0
> [<6002123d>] ? warn_slowpath_fmt+0x0/0x9c
> [<6029e2ad>] ? clk_gate_endisable+0xcd/0x110
> [<6029e315>] ? clk_gate_enable+0x15/0x20
> [<6028795e>] ? clk_core_enable+0x6e/0xf0
> [<60289f1f>] ? clk_enable+0x4f/0xa0
> [<602a06af>] ? clk_gate_test_enable+0xbf/0x360
> [<60053df9>] ? os_nsecs+0x29/0x40
> [<600cd300>] ? ktime_get_ts64+0x0/0x130
> [<600816c0>] ? to_kthread+0x0/0x50
> [<602507bb>] ? kunit_try_run_case+0x7b/0x100
> [<600816c0>] ? to_kthread+0x0/0x50
> [<60252aa0>] ? kunit_generic_run_threadfn_adapter+0x0/0x30
> [<60252ab2>] ? kunit_generic_run_threadfn_adapter+0x12/0x30
> [<60082091>] ? kthread+0xf1/0x270
> [<60047591>] ? new_thread_handler+0x41/0x60
> ---[ end trace 0000000000000000 ]---
Applied to clk-next
I see kunit.py runs olddefconfig so I didn't notice :/
prev parent reply other threads:[~2026-02-03 0:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-22 7:06 Peng Fan (OSS)
2025-12-22 17:23 ` Brian Masney
2026-02-03 0:41 ` Stephen Boyd [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=177007930707.4027.14638082184159958493@lazor \
--to=sboyd@kernel.org \
--cc=bmasney@redhat.com \
--cc=davidgow@google.com \
--cc=johannes@sipsolutions.net \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=peng.fan@nxp.com \
--cc=peng.fan@oss.nxp.com \
--cc=skhan@linuxfoundation.org \
--cc=thomas.weissschuh@linutronix.de \
/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®