LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Linux - Software (https://www.linuxquestions.org/questions/linux-software-2/)
-   -   BUG: spinlock recursion on CPU#0, vbdblkq/75 (https://www.linuxquestions.org/questions/linux-software-2/bug-spinlock-recursion-on-cpu-0-vbdblkq-75-a-4175668957/)

diptendulinux 02-04-2020 06:21 AM

BUG: spinlock recursion on CPU#0, vbdblkq/75
 
Hello,

I am getting BUG: spinlock recursion on CPU#0, vbdblkq/75 in bio.c.
Here is the log report.
BUG: spinlock recursion on CPU#0, vbdblkq/75
lock: 0x8699f840, .magic: dead4ead, .owner: vbdblkq/75, .owner_cpu: -1
CPU: 0 PID: 75 Comm: vbdblkq Tainted: G O
00000000 00000000 85ea9d74 81594761 85df0000 85ea9da0 8158fc74 8176dc44
8699f840 dead4ead 85df03d4 0000004b ffffffff 8699f840 8177ce83 00000003
85ea9db0 8158fc9c 8699f840 8699f840 85ea9dcc 80ea417a 8661c500 00000000
Call Trace:
dump_stack+0x4b/0x75
spin_dump+0x9a/0xa2
spin_bug+0x20/0x24
do_raw_spin_lock+0x10a/0x140
_raw_spin_lock+0x1c/0x20
try_to_wake_up+0x130/0x2f0
default_wake_function+0x10/0x20
wake_bit_function+0x4d/0x70
__wake_up_bit+0x54/0x90
unlock_page+0x40/0x50
mpage_end_io+0x3d/0xa0
bio_endio+0x49/0x90
blk_update_request+0xa3/0x3e0
? preempt_count_sub+0x75/0x130
? blkq_server_thread+0xcc/0x770
__blk_end_request_all+0x27/0x90
blkq_server_thread+0xdc/0x770
? finish_wait+0x60/0x60
? vblkd_request+0xd0/0xd0
kthread+0xe2/0x100
? vblkd_request+0xd0/0xd0
ret_from_kernel_thread+0x1b/0x28
? kthread_create_on_node+0x120/0x120

Is there is really issue with spinlock or bio_endio is been called recursively. How to fix it?


Thanks,
Diptendu

smallpond 02-04-2020 01:58 PM

Code:

vbdblkq Tainted
Looks like you have installed a bad module in your kernel.

diptendulinux 02-05-2020 01:13 AM

Hi,

I have not updated any module or kernel and I am not been allowed to this. this issue is coming once in 3000 iteration and I am not sure why this issue is happening.

Thanks,
Diptendu

smallpond 02-05-2020 06:57 PM

The error message told you. The crash is in vblkd_request, and the module vbdblkq taints the kernel which means it is not part of the kernel source. You will have to find the author of vbdblkq to fix the problem.


All times are GMT -5. The time now is 04:57 PM.