All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pierre Gondois <pierre.gondois@arm.com>
To: Mike Galbraith <efault@gmx.de>, linux-rt-users@vger.kernel.org
Cc: Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
	Thomas Gleixner <tglx@linutronix.de>
Subject: Re: v6.1-rt4 rpi4 boot time atomic_sleep splat
Date: Mon, 28 Nov 2022 09:40:48 +0100	[thread overview]
Message-ID: <859aadda-c971-d16b-44a1-4e15ef49bf8b@arm.com> (raw)
In-Reply-To: <1806ff76592576c6e6dba91f09ce661b7c75a9a9.camel@gmx.de>

Hello Mike,
There is a patch-set currently ongoing aiming to solve this at:
   https://lore.kernel.org/all/20221121171217.3581004-1-pierre.gondois@arm.com/

Regards,
Pierre

On 11/27/22 06:10, Mike Galbraith wrote:
> Sole splat seen during brief master usability test drive.
> 
> (older rpi kernel is still way better idea, but it's improving.. boots,
> runs and hdmi audio started working)
> 
> [    0.007076] smp: Bringing up secondary CPUs ...
> [    0.008304] Detected PIPT I-cache on CPU1
> [    0.008377] BUG: sleeping function called from invalid context at kernel/locking/spinlock_rt.c:46
> [    0.008384] in_atomic(): 1, irqs_disabled(): 128, non_block: 0, pid: 0, name: swapper/1
> [    0.008391] preempt_count: 1, expected: 0
> [    0.008396] RCU nest depth: 1, expected: 1
> [    0.008400] Preemption disabled at:
> [    0.008403] [<ffffffd3244ca8e0>] migrate_enable+0x40/0x170
> [    0.008425] CPU: 1 PID: 0 Comm: swapper/1 Not tainted 6.1.0.g0b1dcc2-rt4 #25
> [    0.008437] Hardware name: Raspberry Pi 4 Model B Rev 1.4 (DT)
> [    0.008442] Call trace:
> [    0.008445]  dump_backtrace.part.0+0xe8/0xf4
> [    0.008455]  show_stack+0x20/0x50
> [    0.008463]  dump_stack_lvl+0x64/0x80
> [    0.008477]  dump_stack+0x18/0x34
> [    0.008488]  __might_resched+0x15c/0x1c0
> [    0.008502]  rt_spin_lock+0x38/0xd0
> [    0.008514]  rmqueue_bulk+0x68/0x850
> [    0.008529]  get_page_from_freelist+0xbe4/0xfa0
> [    0.008542]  __alloc_pages+0x14c/0xf70
> [    0.008554]  new_slab+0x2f0/0x374
> [    0.008569]  ___slab_alloc+0x5f0/0xbcc
> [    0.008584]  __kmem_cache_alloc_node+0xd0/0x380
> [    0.008591]  __kmalloc+0x6c/0x1c0
> [    0.008603]  detect_cache_attributes+0x448/0x564
> [    0.008620]  update_siblings_masks+0x30/0x304
> [    0.008631]  store_cpu_topology+0x48/0x60
> [    0.008640]  secondary_start_kernel+0xc8/0x144
> [    0.008656]  __secondary_switched+0xb0/0xb4
> [    0.008752] CPU1: Booted secondary processor 0x0000000001 [0x410fd083]
> [    0.010180] Detected PIPT I-cache on CPU2
> [    0.010300] CPU2: Booted secondary processor 0x0000000002 [0x410fd083]
> [    0.011522] Detected PIPT I-cache on CPU3
> [    0.011649] CPU3: Booted secondary processor 0x0000000003 [0x410fd083]
> [    0.011768] smp: Brought up 1 node, 4 CPUs
> 

  reply	other threads:[~2022-11-28  8:41 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-27  5:10 v6.1-rt4 rpi4 boot time atomic_sleep splat Mike Galbraith
2022-11-28  8:40 ` Pierre Gondois [this message]
2022-11-28  8:42   ` Sebastian Andrzej Siewior
2023-05-31  8:43 He Zhe
2023-06-05  9:59 ` Pierre Gondois

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=859aadda-c971-d16b-44a1-4e15ef49bf8b@arm.com \
    --to=pierre.gondois@arm.com \
    --cc=bigeasy@linutronix.de \
    --cc=efault@gmx.de \
    --cc=linux-rt-users@vger.kernel.org \
    --cc=tglx@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 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.