All of lore.kernel.org
 help / color / mirror / Atom feed
From: Philippe Gerum <rpm@xenomai.org>
To: Florian Bezdeka <florian.bezdeka@siemens.com>
Cc: xenomai@lists.linux.dev,  Jan Kiszka <jan.kiszka@siemens.com>
Subject: Re: Dovetail 6.15: x86: Invalid wait context
Date: Thu, 05 Jun 2025 10:00:29 +0200	[thread overview]
Message-ID: <87tt4ubote.fsf@xenomai.org> (raw)
In-Reply-To: <ee6e634d9d87ef52670dbb9ce91d7080b8640a71.camel@siemens.com> (Florian Bezdeka's message of "Tue, 03 Jun 2025 15:55:30 +0200")

Florian Bezdeka <florian.bezdeka@siemens.com> writes:

> Hi Philippe,
>
> the following is taken from our CI, testing Dovetail 6.15.
> On x86 we have an invalid wait context reported:
>
> [  151.574032] 
> [  151.574039] =============================
> [  151.574043] [ BUG: Invalid wait context ]
> [  151.574046] 6.15.0 #1 Not tainted
> [  151.574048] -----------------------------
> [  151.574048] swapper/0/0 is trying to lock:
> [  151.574050] ffffffff841174c0 (&state->readq){....}-{3:3}, at: __wake_up+0x21/0x60
> [  151.574063] other info that might help us debug this:
> [  151.574064] context-{2:2}
> [  151.574065] no locks held by swapper/0/0.
> [  151.574066] stack backtrace:
> [  151.574073] CPU: 0 UID: 0 PID: 0 Comm: swapper/0 Not tainted 6.15.0 #1 PREEMPT(full) 
> [  151.574078] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-debian-1.16.3-2~bpo12+1 04/01/2014
> [  151.574079] IRQ stage: Linux
> [  151.574083] Call Trace:
> [  151.574086]  <IRQ>
> [  151.574088]  dump_stack_lvl+0x79/0xe0
> [  151.574095]  __lock_acquire+0x942/0xbf0
> [  151.574104]  lock_acquire+0xe2/0x2f0
> [  151.574107]  ? __wake_up+0x21/0x60
> [  151.574111]  ? find_held_lock+0x2b/0x80
> [  151.574115]  _raw_spin_lock_irqsave+0x49/0x60
> [  151.574120]  ? __wake_up+0x21/0x60
> [  151.574122]  __wake_up+0x21/0x60
> [  151.574125]  xnpipe_wakeup_proc+0x152/0x590
> [  151.574132]  handle_synthetic_irq+0xc2/0x250
> [  151.574137]  arch_do_IRQ_pipelined+0xca/0x180
> [  151.574141]  </IRQ>
> [  151.574142]  <TASK>
> [  151.574144]  sync_current_irq_stage+0xaa/0x110
> [  151.574147]  inband_irq_enable+0x42/0x60
> [  151.574151]  cpuidle_idle_call+0x17d/0x200
> [  151.574155]  do_idle+0x89/0xd0
> [  151.574158]  cpu_startup_entry+0x29/0x30
> [  151.574160]  rest_init+0xf0/0x190
> [  151.574164]  start_kernel+0x632/0x700
> [  151.574179]  x86_64_start_reservations+0x18/0x30
> [  151.574185]  x86_64_start_kernel+0x78/0x80
> [  151.574188]  common_startup_64+0x13e/0x148
> [  151.574198]  </TASK>
>
> That seems to be triggered by the Xenomai 3 smokey testsuite.
>
> Any ideas?

Does this happen when full preemption is disabled on x86?

-- 
Philippe.

  reply	other threads:[~2025-06-05  8:00 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-03 13:55 Dovetail 6.15: x86: Invalid wait context Florian Bezdeka
2025-06-05  8:00 ` Philippe Gerum [this message]
2025-06-05  8:14   ` Florian Bezdeka
2025-06-05 16:21     ` Bezdeka, Florian
2025-06-05 17:56       ` Philippe Gerum
2025-06-22 13:06         ` Florian Bezdeka
2025-07-11  8:40     ` Philippe Gerum
2025-07-14 14:57       ` Florian Bezdeka
2025-07-19 13:24         ` Philippe Gerum
2025-07-19 15:25           ` Philippe Gerum
2025-07-28 14:37             ` Florian Bezdeka
2025-08-20 11:15               ` Bezdeka, Florian
2025-08-20 14:03                 ` Philippe Gerum

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=87tt4ubote.fsf@xenomai.org \
    --to=rpm@xenomai.org \
    --cc=florian.bezdeka@siemens.com \
    --cc=jan.kiszka@siemens.com \
    --cc=xenomai@lists.linux.dev \
    /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.