From: Kalle Valo <kvalo@kernel.org>
To: ath12k@lists.infradead.org
Subject: New warning in v6.11-rc1: BUG: using smp_processor_id() in preemptible [00000000] code: rtcwake/2121
Date: Thu, 01 Aug 2024 18:11:15 +0300 [thread overview]
Message-ID: <87a5hw8ei4.fsf@kernel.org> (raw)
Hi,
Just to make sure everyone is aware. I just updated the ath.git main
branch to v6.11-rc1 and I see a new warning in our suspend tests:
[ 546.233940] BUG: using smp_processor_id() in preemptible [00000000] code: rtcwake/2121
[ 546.233960] caller is debug_smp_processor_id+0x17/0x20
[ 546.233970] CPU: 5 UID: 0 PID: 2121 Comm: rtcwake Not tainted 6.11.0-rc1 #1685
[ 546.233975] Hardware name: Intel(R) Client Systems NUC8i7HVK/NUC8i7HVB, BIOS HNKBLi70.86A.0067.2021.0528.1339 05/28/2021
[ 546.233978] Call Trace:
[ 546.233981] <TASK>
[ 546.233985] dump_stack_lvl+0xa4/0xe0
[ 546.233991] dump_stack+0x10/0x20
[ 546.233995] check_preemption_disabled+0xce/0xe0
[ 546.234003] debug_smp_processor_id+0x17/0x20
[ 546.234008] hotplug_cpu__broadcast_tick_pull+0x20/0x280
[ 546.234017] takedown_cpu+0x197/0x410
There's a fix already which hopefully will be in v6.11-rc2:
Subject: [PATCH] tick/broadcast: Move per CPU pointer access into the atomic section
https://lore.kernel.org/all/87ttg56ers.ffs@tglx/
--
https://patchwork.kernel.org/project/linux-wireless/list/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
next reply other threads:[~2024-08-01 15:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-01 15:11 Kalle Valo [this message]
2024-08-05 10:12 ` New warning in v6.11-rc1: BUG: using smp_processor_id() in preemptible [00000000] code: rtcwake/2121 Kalle Valo
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=87a5hw8ei4.fsf@kernel.org \
--to=kvalo@kernel.org \
--cc=ath12k@lists.infradead.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.