Displaying 20 results from an estimated 31 matches for "kernel_thread_starter".
2015 Feb 25
7
virtio balloon: do not call blocking ops when !TASK_RUNNING
...756] [<000000000028a562>] __kmalloc+0x272/0x350
[ 0.839759] [<000000000058f824>] virtio_ccw_get_config+0x3c/0x100
[ 0.839762] [<000000000049fcb0>] balloon+0x1b8/0x330
[ 0.839765] [<00000000001529c8>] kthread+0x120/0x138
[ 0.839767] [<0000000000683c22>] kernel_thread_starter+0x6/0xc
[ 0.839770] [<0000000000683c1c>] kernel_thread_starter+0x0/0xc
[ 0.839772] no locks held by vballoon/46.
[ 0.839773] Last Breaking-Event-Address:
[ 0.839776] [<000000000015bf8a>] __might_sleep+0x8a/0x98
[ 0.839778] ---[ end trace d27fcdfa27273d7c ]---
The probl...
2015 Feb 25
7
virtio balloon: do not call blocking ops when !TASK_RUNNING
...756] [<000000000028a562>] __kmalloc+0x272/0x350
[ 0.839759] [<000000000058f824>] virtio_ccw_get_config+0x3c/0x100
[ 0.839762] [<000000000049fcb0>] balloon+0x1b8/0x330
[ 0.839765] [<00000000001529c8>] kthread+0x120/0x138
[ 0.839767] [<0000000000683c22>] kernel_thread_starter+0x6/0xc
[ 0.839770] [<0000000000683c1c>] kernel_thread_starter+0x0/0xc
[ 0.839772] no locks held by vballoon/46.
[ 0.839773] Last Breaking-Event-Address:
[ 0.839776] [<000000000015bf8a>] __might_sleep+0x8a/0x98
[ 0.839778] ---[ end trace d27fcdfa27273d7c ]---
The probl...
2014 Sep 11
3
blk-mq crash under KVM in multiqueue block code (with virtio-blk and ext4)
...00000000002b0cd0>] bdi_writeback_workfn+0x354/0x538
[ 66.438618] [<000000000014e3aa>] process_one_work+0x1aa/0x418
[ 66.438621] [<000000000014ef94>] worker_thread+0x48/0x524
[ 66.438625] [<00000000001560ca>] kthread+0xee/0x108
[ 66.438627] [<000000000067c76e>] kernel_thread_starter+0x6/0xc
[ 66.438628] [<000000000067c768>] kernel_thread_starter+0x0/0xc
[ 66.438629] Last Breaking-Event-Address:
[ 66.438631] [<00000000003edde8>] blk_mq_timeout_check+0x6c/0xb8
I looked into the dump, and the full function is (annotated by me to match the source code)
r2= ta...
2014 Sep 11
3
blk-mq crash under KVM in multiqueue block code (with virtio-blk and ext4)
...00000000002b0cd0>] bdi_writeback_workfn+0x354/0x538
[ 66.438618] [<000000000014e3aa>] process_one_work+0x1aa/0x418
[ 66.438621] [<000000000014ef94>] worker_thread+0x48/0x524
[ 66.438625] [<00000000001560ca>] kthread+0xee/0x108
[ 66.438627] [<000000000067c76e>] kernel_thread_starter+0x6/0xc
[ 66.438628] [<000000000067c768>] kernel_thread_starter+0x0/0xc
[ 66.438629] Last Breaking-Event-Address:
[ 66.438631] [<00000000003edde8>] blk_mq_timeout_check+0x6c/0xb8
I looked into the dump, and the full function is (annotated by me to match the source code)
r2= ta...
2013 Dec 17
2
[PATCH v4 RFC 0/3] virtio: add 'device_lost' to virtio_device
...] journal_write_superblock+0xa0/0x1fc
[<00000000003a3ed4>] journal_update_sb_log_tail+0x48/0x7c
[<000000000039e742>] journal_commit_transaction+0x1586/0x1aa0
[<00000000003a2a0e>] kjournald+0xfe/0x2a0
[<00000000001786fc>] kthread+0xd8/0xe0
[<0000000000698fee>] kernel_thread_starter+0x6/0xc
2 locks held by kjournald/1984:
... and end up in hang situations ...
PID: 13 TASK: 1e3f8000 CPU: 0 COMMAND: "kworker/u128:1"
#0 [1e2033e0] __schedule at 695ff2
#1 [1e203530] log_wait_commit at 3a28a6
#2 [1e2035a0] ext3_sync_fs at 328dea
#3 [1e2035d8] sync...
2013 Dec 17
2
[PATCH v4 RFC 0/3] virtio: add 'device_lost' to virtio_device
...] journal_write_superblock+0xa0/0x1fc
[<00000000003a3ed4>] journal_update_sb_log_tail+0x48/0x7c
[<000000000039e742>] journal_commit_transaction+0x1586/0x1aa0
[<00000000003a2a0e>] kjournald+0xfe/0x2a0
[<00000000001786fc>] kthread+0xd8/0xe0
[<0000000000698fee>] kernel_thread_starter+0x6/0xc
2 locks held by kjournald/1984:
... and end up in hang situations ...
PID: 13 TASK: 1e3f8000 CPU: 0 COMMAND: "kworker/u128:1"
#0 [1e2033e0] __schedule at 695ff2
#1 [1e203530] log_wait_commit at 3a28a6
#2 [1e2035a0] ext3_sync_fs at 328dea
#3 [1e2035d8] sync...
2018 Dec 20
0
4.20-rc6: WARNING: CPU: 30 PID: 197360 at net/core/flow_dissector.c:764 __skb_flow_dissect
...handle_tx_copy+0x18c/0x568 [vhost_net]
[85109.572140] [<000003ff801adab4>] handle_tx+0xbc/0x100 [vhost_net]
[85109.572145] [<000003ff8019bbe8>] vhost_worker+0xc8/0x128 [vhost]
[85109.572148] [<00000000001690b8>] kthread+0x140/0x160
[85109.572152] [<0000000000a84266>] kernel_thread_starter+0x6/0x10
[85109.572154] [<0000000000a84260>] kernel_thread_starter+0x0/0x10
[85109.572155] Last Breaking-Event-Address:
[85109.572156] [<000000000092e31c>] __skb_flow_dissect+0x1ec/0x1318
[85109.572158] ---[ end trace 97c040a6691bc000 ]---
2015 Feb 26
0
virtio balloon: do not call blocking ops when !TASK_RUNNING
...028a562>] __kmalloc+0x272/0x350
> [ 0.839759] [<000000000058f824>] virtio_ccw_get_config+0x3c/0x100
> [ 0.839762] [<000000000049fcb0>] balloon+0x1b8/0x330
> [ 0.839765] [<00000000001529c8>] kthread+0x120/0x138
> [ 0.839767] [<0000000000683c22>] kernel_thread_starter+0x6/0xc
> [ 0.839770] [<0000000000683c1c>] kernel_thread_starter+0x0/0xc
> [ 0.839772] no locks held by vballoon/46.
> [ 0.839773] Last Breaking-Event-Address:
> [ 0.839776] [<000000000015bf8a>] __might_sleep+0x8a/0x98
> [ 0.839778] ---[ end trace d27fcdf...
2015 Feb 26
0
virtio balloon: do not call blocking ops when !TASK_RUNNING
...028a562>] __kmalloc+0x272/0x350
> [ 0.839759] [<000000000058f824>] virtio_ccw_get_config+0x3c/0x100
> [ 0.839762] [<000000000049fcb0>] balloon+0x1b8/0x330
> [ 0.839765] [<00000000001529c8>] kthread+0x120/0x138
> [ 0.839767] [<0000000000683c22>] kernel_thread_starter+0x6/0xc
> [ 0.839770] [<0000000000683c1c>] kernel_thread_starter+0x0/0xc
> [ 0.839772] no locks held by vballoon/46.
> [ 0.839773] Last Breaking-Event-Address:
> [ 0.839776] [<000000000015bf8a>] __might_sleep+0x8a/0x98
> [ 0.839778] ---[ end trace d27fcdf...
2014 Sep 12
3
blk-mq crash under KVM in multiqueue block code (with virtio-blk and ext4)
...workfn+0x354/0x538
>> [ 66.438618] [<000000000014e3aa>] process_one_work+0x1aa/0x418
>> [ 66.438621] [<000000000014ef94>] worker_thread+0x48/0x524
>> [ 66.438625] [<00000000001560ca>] kthread+0xee/0x108
>> [ 66.438627] [<000000000067c76e>] kernel_thread_starter+0x6/0xc
>> [ 66.438628] [<000000000067c768>] kernel_thread_starter+0x0/0xc
>> [ 66.438629] Last Breaking-Event-Address:
>> [ 66.438631] [<00000000003edde8>] blk_mq_timeout_check+0x6c/0xb8
>>
>> I looked into the dump, and the full function is (anno...
2014 Sep 12
3
blk-mq crash under KVM in multiqueue block code (with virtio-blk and ext4)
...workfn+0x354/0x538
>> [ 66.438618] [<000000000014e3aa>] process_one_work+0x1aa/0x418
>> [ 66.438621] [<000000000014ef94>] worker_thread+0x48/0x524
>> [ 66.438625] [<00000000001560ca>] kthread+0xee/0x108
>> [ 66.438627] [<000000000067c76e>] kernel_thread_starter+0x6/0xc
>> [ 66.438628] [<000000000067c768>] kernel_thread_starter+0x0/0xc
>> [ 66.438629] Last Breaking-Event-Address:
>> [ 66.438631] [<00000000003edde8>] blk_mq_timeout_check+0x6c/0xb8
>>
>> I looked into the dump, and the full function is (anno...
2013 Dec 23
2
[PATCH v4 RFC 0/3] virtio: add 'device_lost' to virtio_device
...[<00000000003a3ed4>] journal_update_sb_log_tail+0x48/0x7c
>> [<000000000039e742>] journal_commit_transaction+0x1586/0x1aa0
>> [<00000000003a2a0e>] kjournald+0xfe/0x2a0
>> [<00000000001786fc>] kthread+0xd8/0xe0
>> [<0000000000698fee>] kernel_thread_starter+0x6/0xc
>> 2 locks held by kjournald/1984:
>>
>> ... and end up in hang situations ...
>>
>> PID: 13 TASK: 1e3f8000 CPU: 0 COMMAND: "kworker/u128:1"
>> #0 [1e2033e0] __schedule at 695ff2
>> #1 [1e203530] log_wait_commit at 3a2...
2013 Dec 23
2
[PATCH v4 RFC 0/3] virtio: add 'device_lost' to virtio_device
...[<00000000003a3ed4>] journal_update_sb_log_tail+0x48/0x7c
>> [<000000000039e742>] journal_commit_transaction+0x1586/0x1aa0
>> [<00000000003a2a0e>] kjournald+0xfe/0x2a0
>> [<00000000001786fc>] kthread+0xd8/0xe0
>> [<0000000000698fee>] kernel_thread_starter+0x6/0xc
>> 2 locks held by kjournald/1984:
>>
>> ... and end up in hang situations ...
>>
>> PID: 13 TASK: 1e3f8000 CPU: 0 COMMAND: "kworker/u128:1"
>> #0 [1e2033e0] __schedule at 695ff2
>> #1 [1e203530] log_wait_commit at 3a2...
2014 Sep 12
0
blk-mq crash under KVM in multiqueue block code (with virtio-blk and ext4)
...] bdi_writeback_workfn+0x354/0x538
> [ 66.438618] [<000000000014e3aa>] process_one_work+0x1aa/0x418
> [ 66.438621] [<000000000014ef94>] worker_thread+0x48/0x524
> [ 66.438625] [<00000000001560ca>] kthread+0xee/0x108
> [ 66.438627] [<000000000067c76e>] kernel_thread_starter+0x6/0xc
> [ 66.438628] [<000000000067c768>] kernel_thread_starter+0x0/0xc
> [ 66.438629] Last Breaking-Event-Address:
> [ 66.438631] [<00000000003edde8>] blk_mq_timeout_check+0x6c/0xb8
>
> I looked into the dump, and the full function is (annotated by me to match...
2017 Nov 17
2
4.14: WARNING: CPU: 4 PID: 2895 at block/blk-mq.c:1144 with virtio-blk
...47.652435] ([<0000000063709600>] 0x63709600)
[ 747.652436] [<0000000000187bcc>] process_one_work+0x264/0x4b8
[ 747.652438] [<0000000000187e78>] worker_thread+0x58/0x4f8
[ 747.652439] [<000000000018ee94>] kthread+0x144/0x168
[ 747.652439] [<00000000008f8a62>] kernel_thread_starter+0x6/0xc
[ 747.652440] [<00000000008f8a5c>] kernel_thread_starter+0x0/0xc
[ 747.652440] Last Breaking-Event-Address:
[ 747.652441] [<0000000000505860>] __blk_mq_run_hw_queue+0xd0/0x100
[ 747.652442] ---[ end trace 4a001a80379b18ba ]---
[ 747.652450] ------------[ cut here ]-----...
2017 Nov 17
2
4.14: WARNING: CPU: 4 PID: 2895 at block/blk-mq.c:1144 with virtio-blk
...47.652435] ([<0000000063709600>] 0x63709600)
[ 747.652436] [<0000000000187bcc>] process_one_work+0x264/0x4b8
[ 747.652438] [<0000000000187e78>] worker_thread+0x58/0x4f8
[ 747.652439] [<000000000018ee94>] kthread+0x144/0x168
[ 747.652439] [<00000000008f8a62>] kernel_thread_starter+0x6/0xc
[ 747.652440] [<00000000008f8a5c>] kernel_thread_starter+0x0/0xc
[ 747.652440] Last Breaking-Event-Address:
[ 747.652441] [<0000000000505860>] __blk_mq_run_hw_queue+0xd0/0x100
[ 747.652442] ---[ end trace 4a001a80379b18ba ]---
[ 747.652450] ------------[ cut here ]-----...
2014 Sep 17
0
blk-mq crash under KVM in multiqueue block code (with virtio-blk and ext4)
...38
>>> [ 66.438618] [<000000000014e3aa>] process_one_work+0x1aa/0x418
>>> [ 66.438621] [<000000000014ef94>] worker_thread+0x48/0x524
>>> [ 66.438625] [<00000000001560ca>] kthread+0xee/0x108
>>> [ 66.438627] [<000000000067c76e>] kernel_thread_starter+0x6/0xc
>>> [ 66.438628] [<000000000067c768>] kernel_thread_starter+0x0/0xc
>>> [ 66.438629] Last Breaking-Event-Address:
>>> [ 66.438631] [<00000000003edde8>] blk_mq_timeout_check+0x6c/0xb8
>>>
>>> I looked into the dump, and the ful...
2019 Apr 09
0
[RFC PATCH 02/12] virtio/s390: DMA support for virtio-ccw
...ccw_auto_online+0x26/0x58
> [<00000000001a61b6>] async_run_entry_fn+0x5e/0x158
> [<0000000000199322>] process_one_work+0x25a/0x668
> [<000000000019977a>] worker_thread+0x4a/0x428
> [<00000000001a1ae8>] kthread+0x150/0x170
> [<0000000000aeab3a>] kernel_thread_starter+0x6/0xc
> [<0000000000aeab34>] kernel_thread_starter+0x0/0xc
>
> [..]
>
> virtio_ccw 0.0.0301: no vq
> ---[ end trace d35815958c12cad3 ]---
> virtio_ccw 0.0.0300: no vq
> virtio_blk: probe of virtio1 failed with error -12
> virtio_blk: probe of virtio3 failed w...
2013 Dec 19
0
[PATCH v4 RFC 0/3] virtio: add 'device_lost' to virtio_device
...k+0xa0/0x1fc
> [<00000000003a3ed4>] journal_update_sb_log_tail+0x48/0x7c
> [<000000000039e742>] journal_commit_transaction+0x1586/0x1aa0
> [<00000000003a2a0e>] kjournald+0xfe/0x2a0
> [<00000000001786fc>] kthread+0xd8/0xe0
> [<0000000000698fee>] kernel_thread_starter+0x6/0xc
> 2 locks held by kjournald/1984:
>
> ... and end up in hang situations ...
>
> PID: 13 TASK: 1e3f8000 CPU: 0 COMMAND: "kworker/u128:1"
> #0 [1e2033e0] __schedule at 695ff2
> #1 [1e203530] log_wait_commit at 3a28a6
> #2 [1e2035a0] ext3_...
2018 Dec 20
0
4.20-rc6: WARNING: CPU: 30 PID: 197360 at net/core/flow_dissector.c:764 __skb_flow_dissect
...t]
>> [85109.572140] [<000003ff801adab4>] handle_tx+0xbc/0x100 [vhost_net]
>> [85109.572145] [<000003ff8019bbe8>] vhost_worker+0xc8/0x128 [vhost]
>> [85109.572148] [<00000000001690b8>] kthread+0x140/0x160
>> [85109.572152] [<0000000000a84266>] kernel_thread_starter+0x6/0x10
>> [85109.572154] [<0000000000a84260>] kernel_thread_starter+0x0/0x10
>> [85109.572155] Last Breaking-Event-Address:
>> [85109.572156] [<000000000092e31c>] __skb_flow_dissect+0x1ec/0x1318
>> [85109.572158] ---[ end trace 97c040a6691bc000 ]---
>