Le 14/02/2022 à 10:35, Peter Zijlstra a écrit :
> On Sun, Feb 13, 2022 at 12:05:50AM +0100, Paul Menzel wrote:
>
>> [0.012154][T1] BUG: sleeping function called from invalid context at
>
>> [0.022443][T1] [c84837d0] [c0961aac] >
>> dump_stack_lvl+0xa0/0xec (unre
On Sun, Feb 13, 2022 at 12:05:50AM +0100, Paul Menzel wrote:
> [0.012154][T1] BUG: sleeping function called from invalid context at
> [0.022443][T1] [c84837d0] [c0961aac] >
> dump_stack_lvl+0xa0/0xec (unreliable)
> [0.023356][T1] [c8483820] [c0
Dear Paul,
Am 13.02.22 um 15:45 schrieb Paul E. McKenney:
On Sun, Feb 13, 2022 at 08:39:13AM +0100, Paul Menzel wrote:
Am 13.02.22 um 00:48 schrieb Paul E. McKenney:
On Sun, Feb 13, 2022 at 12:05:50AM +0100, Paul Menzel wrote:
[…]
Running rcutorture on the POWER8 system IBM S822LC with
>From console.log, I see
[ 0.012154][ T1] BUG: sleeping function called from invalid
context at include/linux/sched/mm.h:256
[0.013128][T1] in_atomic(): 0, irqs_disabled(): 1, non_block:
0, pid: 1, name: swapper/0
>From ___might_sleep, I see
9506 if ((preempt_count_equal
On Sun, Feb 13, 2022 at 11:19:09AM +0800, Zhouyi Zhou wrote:
> I think the key to the problem lies in your attached console.log
> (pasted below), at times 0.014987 and 0.015995, I see there are two
> locks (cpu_hotplug_lock and jump_label_mutex) holded while
> kmem_cache_alloc calls __might_resche
eturn -1;
return 0;
}
I will try to think it over in the coming days.
[0.012154][ T1] BUG: sleeping function called from invalid
context at include/linux/sched/mm.h:256
[0.013128][T1] in_atomic(): 0, irqs_disabled(): 1, non_block:
0, pid: 1, name: swapper/0
[0.01401
