On 2019-08-16 16:18:20 [+0100], Julien Grall wrote:
> Sadly, I managed to hit the same BUG_ON() today with this patch
> applied on top v5.2-rt1-rebase. :/ Although, it is more difficult
> to hit than previously.
>
> [ 157.449545] 000: BUG: sleeping function called from invalid context at kernel/locking/rtmutex.c:968
> [ 157.449569] 000: in_atomic(): 1, irqs_disabled(): 0, pid: 990, name: kvm-vcpu-1
> [ 157.449579] 000: 2 locks held by kvm-vcpu-1/990:
> [ 157.449592] 000: #0: 00000000c2fc8217 (&vcpu->mutex){+.+.}, at: kvm_vcpu_ioctl+0x70/0xae0
> [ 157.449638] 000: #1: 0000000096863801 (&cpu_base->softirq_expiry_lock){+.+.}, at: hrtimer_grab_expiry_lock+0x24/0x40
> [ 157.449677] 000: Preemption disabled at:
> [ 157.449679] 000: [<ffff0000111a4538>] schedule+0x30/0xd8
> [ 157.449702] 000: CPU: 0 PID: 990 Comm: kvm-vcpu-1 Tainted: G W 5.2.0-rt1-00001-gd368139e892f #104
> [ 157.449712] 000: Hardware name: ARM LTD ARM Juno Development Platform/ARM Juno Development Platform, BIOS EDK II Jan 23 2017
> [ 157.449718] 000: Call trace:
> [ 157.449722] 000: dump_backtrace+0x0/0x130
> [ 157.449730] 000: show_stack+0x14/0x20
> [ 157.449738] 000: dump_stack+0xbc/0x104
> [ 157.449747] 000: ___might_sleep+0x198/0x238
> [ 157.449756] 000: rt_spin_lock+0x5c/0x70
> [ 157.449765] 000: hrtimer_grab_expiry_lock+0x24/0x40
> [ 157.449773] 000: hrtimer_cancel+0x1c/0x38
> [ 157.449780] 000: kvm_timer_vcpu_load+0x78/0x3e0
…
> I will do some debug and see what I can find.
which timer is this? Is there another one?
In the meantime I do a release with that patch included.
>
> Cheers,
Sebastian
_______________________________________________
kvmarm mailing list
kvmarm@xxxxxxxxxxxxxxxxxxxxx
https://lists.cs.columbia.edu/mailman/listinfo/kvmarm
