Re: Stalls in qemu with host running 6.1 (everything stuck at mmap_read_lock())

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 12. 01. 23, 7:07, Jiri Slaby wrote:
I have rebooted to a fresh kernel which 1) have lockdep enabled, and 2) I have debuginfo for. So next time this happens, I can print held locks

For the time being:

>  Showing all locks held in the system:
>  1 lock held by rcu_tasks_kthre/11:
> #0: ffffffffb097a550 (rcu_tasks.tasks_gp_mutex){+.+.}-{3:3}, at: rcu_tasks_one_gp+0x2b/0x3d0
>  1 lock held by rcu_tasks_rude_/12:
> #0: ffffffffb097a2d0 (rcu_tasks_rude.tasks_gp_mutex){+.+.}-{3:3}, at: rcu_tasks_one_gp+0x2b/0x3d0
>  1 lock held by rcu_tasks_trace/13:
> #0: ffffffffb097a010 (rcu_tasks_trace.tasks_gp_mutex){+.+.}-{3:3}, at: rcu_tasks_one_gp+0x2b/0x3d0
>  1 lock held by in:imklog/1308:
> #0: ffff9538d81364e8 (&f->f_pos_lock){+.+.}-{3:3}, at: __fdget_pos+0x4c/0x60
>  2 locks held by plasmashell/6865:
> #0: ffff95393f6092e8 (&f->f_pos_lock){+.+.}-{3:3}, at: __fdget_pos+0x4c/0x60 > #1: ffff9538dc2aa458 (&mm->mmap_lock#2){++++}-{3:3}, at: __access_remote_vm+0x4f/0x3c0
>  1 lock held by fuse mainloop/9772:
> #0: ffff953a578a7468 (&pipe->mutex/1){+.+.}-{3:3}, at: splice_file_to_pipe+0x26/0xd0
>  1 lock held by fuse mainloop/9773:
> #0: ffff953a578a7e68 (&pipe->mutex/1){+.+.}-{3:3}, at: splice_file_to_pipe+0x26/0xd0
>  1 lock held by fuse mainloop/25378:
> #0: ffff9538d3d8c868 (&pipe->mutex/1){+.+.}-{3:3}, at: splice_file_to_pipe+0x26/0xd0
>  1 lock held by qemu-kvm/31097:
>  6 locks held by qemu-kvm/31098:
> #0: ffff953a062080b0 (&vcpu->mutex){+.+.}-{3:3}, at: kvm_vcpu_ioctl+0x77/0x6d0 [kvm] > #1: ffff9538c6e838e8 (&serio->lock){-.-.}-{2:2}, at: serio_interrupt+0x24/0x90 > #2: ffff9538c6e80230 (&dev->event_lock){-.-.}-{2:2}, at: input_event+0x3c/0x80 > #3: ffffffffb097af60 (rcu_read_lock){....}-{1:2}, at: input_pass_values.part.0+0x5/0x270 > #4: ffffffffb097af60 (rcu_read_lock){....}-{1:2}, at: __handle_sysrq+0x5/0xa0 > #5: ffffffffb097af60 (rcu_read_lock){....}-{1:2}, at: debug_show_all_locks+0x15/0x16b
>  1 lock held by qemu-kvm/31099:
>  3 locks held by qemu-kvm/31100:
>  1 lock held by qemu-kvm/31819:
> #0: ffff9538dc2aa458 (&mm->mmap_lock#2){++++}-{3:3}, at: __vm_munmap+0x95/0x170
>  1 lock held by qemu-kvm/31935:
> #0: ffff9538dc2aa458 (&mm->mmap_lock#2){++++}-{3:3}, at: do_madvise.part.0+0xe8/0x2a0
>  1 lock held by dmesg/31873:
> #0: ffff9538ef6000d0 (&user->lock){+.+.}-{3:3}, at: devkmsg_read+0x4b/0x230
>  1 lock held by ps/31996:
> #0: ffff9538dc2aa458 (&mm->mmap_lock#2){++++}-{3:3}, at: __access_remote_vm+0x4f/0x3c0


and dump a kcore (kdump is set up).

Going to trigger a dump now.

--
js
suse labs




[Index of Archives]     [KVM ARM]     [KVM ia64]     [KVM ppc]     [Virtualization Tools]     [Spice Development]     [Libvirt]     [Libvirt Users]     [Linux USB Devel]     [Linux Audio Users]     [Yosemite Questions]     [Linux Kernel]     [Linux SCSI]     [XFree86]

  Powered by Linux