Displaying 20 results from an estimated 37 matches for "__blk_mq_run_hw_queue".
2017 Dec 19
1
Xen PV DomU running Kernel 4.14.5-1.el7.elrepo.x86_64: xl -v vcpu-set <domU> <val> triggers domU kernel WARNING, then domU becomes unresponsive
...--color=auto -l /var/tmp
>
> At a first glance it appears the issue is in 4.14.5 kernel. Stack traces
> follow:
>
> -----CentOS 6 kernel-ml-4.14.5-1.el6.elrepo.x86_64 start here-----
> ------------[ cut here ]------------
> WARNING: CPU: 4 PID: 60 at block/blk-mq.c:1144
> __blk_mq_run_hw_queue+0x9e/0xc0
> Modules linked in: intel_cstate(-) ipt_REJECT nf_reject_ipv4
> nf_conntrack_ipv4 nf_defrag_ipv4 xt_multiport iptable_filter ip_tables
> ip6t_REJECT nf_reject_ipv6 nf_conntrack_ipv6 nf_defrag_ipv6 xt_state
> nf_conntrack libcrc32c ip6table_filter ip6_tables dm_mod dax
> xe...
2017 Dec 12
5
Xen PV DomU running Kernel 4.14.5-1.el7.elrepo.x86_64: xl -v vcpu-set <domU> <val> triggers domU kernel WARNING, then domU becomes unresponsive
...8 2612 pts/4 D+ 11:47 0:00 ls
--color=auto -l /var/tmp
At a first glance it appears the issue is in 4.14.5 kernel. Stack traces
follow:
-----CentOS 6 kernel-ml-4.14.5-1.el6.elrepo.x86_64 start here-----
------------[ cut here ]------------
WARNING: CPU: 4 PID: 60 at block/blk-mq.c:1144
__blk_mq_run_hw_queue+0x9e/0xc0
Modules linked in: intel_cstate(-) ipt_REJECT nf_reject_ipv4
nf_conntrack_ipv4 nf_defrag_ipv4 xt_multiport iptable_filter ip_tables
ip6t_REJECT nf_reject_ipv6 nf_conntrack_ipv6 nf_defrag_ipv6 xt_state
nf_conntrack libcrc32c ip6table_filter ip6_tables dm_mod dax
xen_netfront crc32_pclm...
2017 Dec 19
0
Xen PV DomU running Kernel 4.14.5-1.el7.elrepo.x86_64: xl -v vcpu-set <domU> <val> triggers domU kernel WARNING, then domU becomes unresponsive
...>
>> At a first glance it appears the issue is in 4.14.5 kernel. Stack traces
>> follow:
>>
>> -----CentOS 6 kernel-ml-4.14.5-1.el6.elrepo.x86_64 start here-----
>> ------------[ cut here ]------------
>> WARNING: CPU: 4 PID: 60 at block/blk-mq.c:1144
>> __blk_mq_run_hw_queue+0x9e/0xc0
>> Modules linked in: intel_cstate(-) ipt_REJECT nf_reject_ipv4
>> nf_conntrack_ipv4 nf_defrag_ipv4 xt_multiport iptable_filter ip_tables
>> ip6t_REJECT nf_reject_ipv6 nf_conntrack_ipv6 nf_defrag_ipv6 xt_state
>> nf_conntrack libcrc32c ip6table_filter ip6_tables dm...
2017 Nov 17
2
4.14: WARNING: CPU: 4 PID: 2895 at block/blk-mq.c:1144 with virtio-blk
When doing cpu hotplug in a KVM guest with virtio blk I get warnings like
747.652408] ------------[ cut here ]------------
[ 747.652410] WARNING: CPU: 4 PID: 2895 at block/blk-mq.c:1144 __blk_mq_run_hw_queue+0xd4/0x100
[ 747.652410] Modules linked in: dm_multipath
[ 747.652412] CPU: 4 PID: 2895 Comm: kworker/4:1H Tainted: G W 4.14.0+ #191
[ 747.652412] Hardware name: IBM 2964 NC9 704 (KVM/Linux)
[ 747.652414] Workqueue: kblockd blk_mq_run_work_fn
[ 747.652414] task: 0000000060680000 t...
2017 Nov 17
2
4.14: WARNING: CPU: 4 PID: 2895 at block/blk-mq.c:1144 with virtio-blk
When doing cpu hotplug in a KVM guest with virtio blk I get warnings like
747.652408] ------------[ cut here ]------------
[ 747.652410] WARNING: CPU: 4 PID: 2895 at block/blk-mq.c:1144 __blk_mq_run_hw_queue+0xd4/0x100
[ 747.652410] Modules linked in: dm_multipath
[ 747.652412] CPU: 4 PID: 2895 Comm: kworker/4:1H Tainted: G W 4.14.0+ #191
[ 747.652412] Hardware name: IBM 2964 NC9 704 (KVM/Linux)
[ 747.652414] Workqueue: kblockd blk_mq_run_work_fn
[ 747.652414] task: 0000000060680000 t...
2017 Nov 21
2
4.14: WARNING: CPU: 4 PID: 2895 at block/blk-mq.c:1144 with virtio-blk (also 4.12 stable)
...1b604c148eea109e93b30d M include
adding Christoph FWIW, your patch triggers the following on 4.14 when doing a cpu hotplug (adding a
CPU) and then accessing a virtio-blk device.
747.652408] ------------[ cut here ]------------
[ 747.652410] WARNING: CPU: 4 PID: 2895 at block/blk-mq.c:1144 __blk_mq_run_hw_queue+0xd4/0x100
[ 747.652410] Modules linked in: dm_multipath
[ 747.652412] CPU: 4 PID: 2895 Comm: kworker/4:1H Tainted: G W 4.14.0+ #191
[ 747.652412] Hardware name: IBM 2964 NC9 704 (KVM/Linux)
[ 747.652414] Workqueue: kblockd blk_mq_run_work_fn
[ 747.652414] task: 0000000060680000 t...
2017 Nov 21
2
4.14: WARNING: CPU: 4 PID: 2895 at block/blk-mq.c:1144 with virtio-blk (also 4.12 stable)
...1b604c148eea109e93b30d M include
adding Christoph FWIW, your patch triggers the following on 4.14 when doing a cpu hotplug (adding a
CPU) and then accessing a virtio-blk device.
747.652408] ------------[ cut here ]------------
[ 747.652410] WARNING: CPU: 4 PID: 2895 at block/blk-mq.c:1144 __blk_mq_run_hw_queue+0xd4/0x100
[ 747.652410] Modules linked in: dm_multipath
[ 747.652412] CPU: 4 PID: 2895 Comm: kworker/4:1H Tainted: G W 4.14.0+ #191
[ 747.652412] Hardware name: IBM 2964 NC9 704 (KVM/Linux)
[ 747.652414] Workqueue: kblockd blk_mq_run_work_fn
[ 747.652414] task: 0000000060680000 t...
2014 Oct 30
3
kernel BUG at drivers/block/virtio_blk.c:172
...0000000001 ffff88022f2f0170 0000000000000000 ffff88022f2e3400
[ 2.807018] ffff880034d27820 0000000000000000 ffff88022f2f0000 ffff88022f2e3408
[ 2.807018] ffff880034d27868 ffffffff812e0628 ffff88022e8c0000 0000000000000003
[ 2.807018] Call Trace:
[ 2.807018] [<ffffffff812e0628>] __blk_mq_run_hw_queue+0x1c8/0x330
[ 2.807018] [<ffffffff812d233f>] ? part_round_stats+0x4f/0x60
[ 2.807018] [<ffffffff812e0da0>] blk_mq_run_hw_queue+0x70/0xa0
[ 2.807018] [<ffffffff812e1e68>] blk_sq_make_request+0x258/0x380
[ 2.807018] [<ffffffff812d32e0>] generic_make_request+0xe...
2014 Oct 30
3
kernel BUG at drivers/block/virtio_blk.c:172
...0000000001 ffff88022f2f0170 0000000000000000 ffff88022f2e3400
[ 2.807018] ffff880034d27820 0000000000000000 ffff88022f2f0000 ffff88022f2e3408
[ 2.807018] ffff880034d27868 ffffffff812e0628 ffff88022e8c0000 0000000000000003
[ 2.807018] Call Trace:
[ 2.807018] [<ffffffff812e0628>] __blk_mq_run_hw_queue+0x1c8/0x330
[ 2.807018] [<ffffffff812d233f>] ? part_round_stats+0x4f/0x60
[ 2.807018] [<ffffffff812e0da0>] blk_mq_run_hw_queue+0x70/0xa0
[ 2.807018] [<ffffffff812e1e68>] blk_sq_make_request+0x258/0x380
[ 2.807018] [<ffffffff812d32e0>] generic_make_request+0xe...
2014 Nov 07
2
kernel BUG at drivers/block/virtio_blk.c:172!
...0000000001 ffff8800d8375870 0000000000000001 ffff8800d82c4c00
[ 64.670008] ffff8800d9f3b7e0 0000000000000000 ffff8800d8375700 ffff8800d82c4c48
[ 64.670008] ffff8800d9f3b828 ffffffff813ec258 ffff8800d82c8000 0000000000000001
[ 64.670008] Call Trace:
[ 64.670008] [<ffffffff813ec258>] __blk_mq_run_hw_queue+0x1c8/0x330
[ 64.670008] [<ffffffff813ecd80>] blk_mq_run_hw_queue+0x70/0x90
[ 64.670008] [<ffffffff813ee0cd>] blk_sq_make_request+0x24d/0x5c0
[ 64.670008] [<ffffffff813dec68>] generic_make_request+0xf8/0x150
[ 64.670008] [<ffffffff813ded38>] submit_bio+0x78/0x190...
2014 Nov 07
2
kernel BUG at drivers/block/virtio_blk.c:172!
...0000000001 ffff8800d8375870 0000000000000001 ffff8800d82c4c00
[ 64.670008] ffff8800d9f3b7e0 0000000000000000 ffff8800d8375700 ffff8800d82c4c48
[ 64.670008] ffff8800d9f3b828 ffffffff813ec258 ffff8800d82c8000 0000000000000001
[ 64.670008] Call Trace:
[ 64.670008] [<ffffffff813ec258>] __blk_mq_run_hw_queue+0x1c8/0x330
[ 64.670008] [<ffffffff813ecd80>] blk_mq_run_hw_queue+0x70/0x90
[ 64.670008] [<ffffffff813ee0cd>] blk_sq_make_request+0x24d/0x5c0
[ 64.670008] [<ffffffff813dec68>] generic_make_request+0xf8/0x150
[ 64.670008] [<ffffffff813ded38>] submit_bio+0x78/0x190...
2015 Oct 01
2
req->nr_phys_segments > queue_max_segments (was Re: kernel BUG at drivers/block/virtio_blk.c:172!)
...ff880622d4c478 0000000000000000 ffff88061ff33bd8 ffff88061fb2f
>>> 0000000000000001 ffff88061fb2fc00 ffff88061ff33c30 0000000000000
>>> ffff88061eef3540 0000000000000000 ffff88061ff33c98 ffffffffb43eb
>>>
>>> Call Trace:
>>> [<ffffffffb43eb500>] __blk_mq_run_hw_queue+0x1d0/0x370
>>> [<ffffffffb43eb315>] blk_mq_run_hw_queue+0x95/0xb0
>>> [<ffffffffb43ec804>] blk_mq_flush_plug_list+0x129/0x140
>>> [<ffffffffb43e33d8>] blk_finish_plug+0x18/0x50
>>> [<ffffffffb45e3bea>] dmcrypt_write+0x1da/0x1f0
>&g...
2015 Oct 01
2
req->nr_phys_segments > queue_max_segments (was Re: kernel BUG at drivers/block/virtio_blk.c:172!)
...ff880622d4c478 0000000000000000 ffff88061ff33bd8 ffff88061fb2f
>>> 0000000000000001 ffff88061fb2fc00 ffff88061ff33c30 0000000000000
>>> ffff88061eef3540 0000000000000000 ffff88061ff33c98 ffffffffb43eb
>>>
>>> Call Trace:
>>> [<ffffffffb43eb500>] __blk_mq_run_hw_queue+0x1d0/0x370
>>> [<ffffffffb43eb315>] blk_mq_run_hw_queue+0x95/0xb0
>>> [<ffffffffb43ec804>] blk_mq_flush_plug_list+0x129/0x140
>>> [<ffffffffb43e33d8>] blk_finish_plug+0x18/0x50
>>> [<ffffffffb45e3bea>] dmcrypt_write+0x1da/0x1f0
>&g...
2017 Aug 10
2
[PATCH 1/2] virtio: Reduce BUG if total_sg > virtqueue size to WARN.
On Thu, Aug 10, 2017 at 05:40:34PM +0100, Richard W.M. Jones wrote:
> If using indirect descriptors, you can make the total_sg as large as
> you want.
That would be a spec violation though, even if it happens to
work on current QEMU.
The spec says:
A driver MUST NOT create a descriptor chain longer than the Queue Size of the device.
What prompted this patch? Do we ever encounter this
2017 Aug 10
2
[PATCH 1/2] virtio: Reduce BUG if total_sg > virtqueue size to WARN.
On Thu, Aug 10, 2017 at 05:40:34PM +0100, Richard W.M. Jones wrote:
> If using indirect descriptors, you can make the total_sg as large as
> you want.
That would be a spec violation though, even if it happens to
work on current QEMU.
The spec says:
A driver MUST NOT create a descriptor chain longer than the Queue Size of the device.
What prompted this patch? Do we ever encounter this
2017 Nov 21
2
4.14: WARNING: CPU: 4 PID: 2895 at block/blk-mq.c:1144 with virtio-blk
On 11/20/2017 09:52 PM, Jens Axboe wrote:
> On 11/20/2017 01:49 PM, Christian Borntraeger wrote:
>>
>>
>> On 11/20/2017 08:42 PM, Jens Axboe wrote:
>>> On 11/20/2017 12:29 PM, Christian Borntraeger wrote:
>>>>
>>>>
>>>> On 11/20/2017 08:20 PM, Bart Van Assche wrote:
>>>>> On Fri, 2017-11-17 at 15:42 +0100, Christian
2017 Nov 21
2
4.14: WARNING: CPU: 4 PID: 2895 at block/blk-mq.c:1144 with virtio-blk
On 11/20/2017 09:52 PM, Jens Axboe wrote:
> On 11/20/2017 01:49 PM, Christian Borntraeger wrote:
>>
>>
>> On 11/20/2017 08:42 PM, Jens Axboe wrote:
>>> On 11/20/2017 12:29 PM, Christian Borntraeger wrote:
>>>>
>>>>
>>>> On 11/20/2017 08:20 PM, Bart Van Assche wrote:
>>>>> On Fri, 2017-11-17 at 15:42 +0100, Christian
2015 Oct 01
2
req->nr_phys_segments > queue_max_segments (was Re: kernel BUG at drivers/block/virtio_blk.c:172!)
...80622d4c478 0000000000000000 ffff88061ff33bd8 ffff88061fb2f
>>> 0000000000000001 ffff88061fb2fc00 ffff88061ff33c30 0000000000000
>>> ffff88061eef3540 0000000000000000 ffff88061ff33c98 ffffffffb43eb
>>>
>>> Call Trace:
>>> [<ffffffffb43eb500>] __blk_mq_run_hw_queue+0x1d0/0x370
>>> [<ffffffffb43eb315>] blk_mq_run_hw_queue+0x95/0xb0
>>> [<ffffffffb43ec804>] blk_mq_flush_plug_list+0x129/0x140
>>> [<ffffffffb43e33d8>] blk_finish_plug+0x18/0x50
>>> [<ffffffffb45e3bea>] dmcrypt_write+0x1da/0x1f0
&g...
2015 Oct 01
2
req->nr_phys_segments > queue_max_segments (was Re: kernel BUG at drivers/block/virtio_blk.c:172!)
...80622d4c478 0000000000000000 ffff88061ff33bd8 ffff88061fb2f
>>> 0000000000000001 ffff88061fb2fc00 ffff88061ff33c30 0000000000000
>>> ffff88061eef3540 0000000000000000 ffff88061ff33c98 ffffffffb43eb
>>>
>>> Call Trace:
>>> [<ffffffffb43eb500>] __blk_mq_run_hw_queue+0x1d0/0x370
>>> [<ffffffffb43eb315>] blk_mq_run_hw_queue+0x95/0xb0
>>> [<ffffffffb43ec804>] blk_mq_flush_plug_list+0x129/0x140
>>> [<ffffffffb43e33d8>] blk_finish_plug+0x18/0x50
>>> [<ffffffffb45e3bea>] dmcrypt_write+0x1da/0x1f0
&g...
2014 Nov 11
2
kernel BUG at drivers/block/virtio_blk.c:172!
...---------[ cut here ]------------
kernel BUG at drivers/block/virtio_blk.c:172!
invalid opcode: 0000 [#1] SMP
CPU: 1 PID: 3343 Comm: mount Not tainted 3.18.0-rc4+ #55
RIP: 0010:[<ffffffff81561027>]
[<ffffffff81561027>] virtio_queue_rq+0x277/0x280
Call Trace:
[<ffffffff8142e908>] __blk_mq_run_hw_queue+0x1a8/0x300
[<ffffffff8142f00d>] blk_mq_run_hw_queue+0x6d/0x90
[<ffffffff8143003e>] blk_sq_make_request+0x23e/0x360
[<ffffffff81422e20>] generic_make_request+0xc0/0x110
[<ffffffff81422ed9>] submit_bio+0x69/0x130
[<ffffffff812f013d>] _xfs_buf_ioapply+0x2bd/0x410
[...