On Mon, 15 Aug 2022 16:55:50 +1000, Michael Ellerman wrote:
> The recent change to get_phb_number() causes a DEBUG_ATOMIC_SLEEP
> warning on some systems:
>
> BUG: sleeping function called from invalid context at
> kernel/locking/mutex.c:580
> in_atomic(): 1, irqs_disabled(): 0, non_block: 0,
On Monday 15 August 2022 16:55:50 Michael Ellerman wrote:
> The recent change to get_phb_number() causes a DEBUG_ATOMIC_SLEEP
> warning on some systems:
>
> BUG: sleeping function called from invalid context at
> kernel/locking/mutex.c:580
> in_atomic(): 1, irqs_disabled(): 0, non_block: 0, p
On Mon, Aug 15, 2022 at 04:55:50PM +1000, Michael Ellerman wrote:
> The recent change to get_phb_number() causes a DEBUG_ATOMIC_SLEEP
> warning on some systems:
>
> BUG: sleeping function called from invalid context at
> kernel/locking/mutex.c:580
> in_atomic(): 1, irqs_disabled(): 0, non_blo
The recent change to get_phb_number() causes a DEBUG_ATOMIC_SLEEP
warning on some systems:
BUG: sleeping function called from invalid context at
kernel/locking/mutex.c:580
in_atomic(): 1, irqs_disabled(): 0, non_block: 0, pid: 1, name: swapper
preempt_count: 1, expected: 0
RCU nest depth: