search for: kick_pending_request_queues

Hello, A friend of mine was having weird ocasional crashes on migration, and I took a look at the problem The VM is a very stripped down ubuntu 12.04 environment (3.2.0 kernel) with a total of 96MB of RAM, but this appears to be a generic driver problem still present in upstream. The symptoms were that on about 5% of migrations, one or more block devices would fail to come back on resume. The

...ff88001a914000 000005fc00000000 000000000000000f 0000000000000002 0000000000000001 ffff88001a968820 ffffffff00000001 ffff88001a968800 0000000000000000 ffff88001a96ba50 Call Trace: <IRQ> <0> [<ffffffff803a8d0a>] ? blk_invoke_request_fn+0x1e/0x3f [<ffffffff803f24c3>] ? kick_pending_request_queues+0x18/0x24 [<ffffffff803f2f7a>] ? blkif_interrupt+0x1a0/0x1c2 [<ffffffff80248d4b>] ? handle_IRQ_event+0x2c/0x61 [<ffffffff8024a538>] ? handle_level_irq+0x5c/0xa0 [<ffffffff802114d4>] ? do_IRQ+0x57/0xb3 [<ffffffff803d2c68>] ? xen_evtchn_do_upcall+0x89/0xeb [&...

...t;] do_blkif_request+0x6bf/0x8a0 [xen_blkfront] [ 32.304945] [<ffffffff812eb0e2>] ? __freed_request+0x92/0xa0 [ 32.304951] [<ffffffff812eb6e3>] __blk_run_queue+0x33/0x40 [ 32.304957] [<ffffffff812eb719>] blk_start_queue+0x29/0x40 [ 32.304964] [<ffffffffa000bf51>] kick_pending_request_queues+0x21/0x30 [xen_blkfront] [ 32.304975] [<ffffffffa000c6ce>] blkif_interrupt+0x76e/0x820 [xen_blkfront] [ 32.304986] [<ffffffff811dcc8b>] ? kmem_cache_free+0x1bb/0x1f0 [ 32.304995] [<ffffffff8113079e>] handle_irq_event_percpu+0x3e/0x1e0 [ 32.305003] [<ffffffff8113097d...

...62 c12e0000 c0266a8e 00000000 c12e0000 c026759c c12e0000 00000000 00000802 00000000 00000200 c12e0000 c02f8387 c119bf78 c03056b9 c02f6db2 c119bf70 00000000 00000200 00080000 00000000 c02674b0 c12b2a60 c119a000 Call Trace: [<c0264862>] xenbus_dev_ok+0x32/0x60 [<c0266a8e>] kick_pending_request_queues+0x1e/0x40 [<c026759c>] watch_for_status+0xec/0x140 [<c02674b0>] watch_for_status+0x0/0x140 [<c0264e77>] xenwatch_thread+0x87/0x140 [<c01363c0>] autoremove_wake_function+0x0/0x60 [<c0264df0>] xenwatch_thread+0x0/0x140 [<c0135ea7>] kthread+0xc7/0xd0 [<c01...

On 01/06/2018 03:16 AM, Dmitry Melekhov wrote: > The same problem with latest centos 6 kernel,i.e. with meltdown fix. > > I can't see console output, because I have it on "cloud" provider > hosting :-) > > > > 06.01.2018 05:13, Shaun Reitan ?????: >> Broken! >> >> For those of you looking for a PV enabled client Kernel for CentOS Linux

...0 > [? 587.145018]? [<ffffffffa0000cc3>] do_blkif_request+0x683/0x850 > [xen_blkfront] > [? 587.145018]? [<ffffffff812906c3>] __blk_run_queue+0x33/0x40 > [? 587.145018]? [<ffffffff812906f9>] blk_start_queue+0x29/0x40 > [? 587.145018]? [<ffffffffa0000eb1>] > kick_pending_request_queues+0x21/0x30 [xen_blkfront] > [? 587.145018]? [<ffffffffa0001487>] blkif_interrupt+0x5c7/0x670 > [xen_blkfront] > [? 587.145018]? [<ffffffff810f735e>] handle_irq_event_percpu+0x3e/0x1e0 > [? 587.145018]? [<ffffffff810f753d>] handle_irq_event+0x3d/0x60 > [? 587.145018]?...

...oc_grant_references+0x15/0x30 [ 587.145018] [<ffffffffa0000cc3>] do_blkif_request+0x683/0x850 [xen_blkfront] [ 587.145018] [<ffffffff812906c3>] __blk_run_queue+0x33/0x40 [ 587.145018] [<ffffffff812906f9>] blk_start_queue+0x29/0x40 [ 587.145018] [<ffffffffa0000eb1>] kick_pending_request_queues+0x21/0x30 [xen_blkfront] [ 587.145018] [<ffffffffa0001487>] blkif_interrupt+0x5c7/0x670 [xen_blkfront] [ 587.145018] [<ffffffff810f735e>] handle_irq_event_percpu+0x3e/0x1e0 [ 587.145018] [<ffffffff810f753d>] handle_irq_event+0x3d/0x60 [ 587.145018] [<ffffffff810fa1c7&g...

...f/0x8a0 > [xen_blkfront] > [ 32.304945] [<ffffffff812eb0e2>] ? __freed_request+0x92/0xa0 > [ 32.304951] [<ffffffff812eb6e3>] __blk_run_queue+0x33/0x40 > [ 32.304957] [<ffffffff812eb719>] blk_start_queue+0x29/0x40 > [ 32.304964] [<ffffffffa000bf51>] kick_pending_request_queues+0x21/0x30 > [xen_blkfront] > [ 32.304975] [<ffffffffa000c6ce>] blkif_interrupt+0x76e/0x820 > [xen_blkfront] > [ 32.304986] [<ffffffff811dcc8b>] ? kmem_cache_free+0x1bb/0x1f0 > [ 32.304995] [<ffffffff8113079e>] handle_irq_event_percpu+0x3e/0x1e0 > [ 32....

...diff --git a/drivers/block/xen-blkfront.c b/drivers/block/xen-blkfront.c index 2c1fe8d..68737bd 100644 --- a/drivers/block/xen-blkfront.c +++ b/drivers/block/xen-blkfront.c @@ -2442,6 +2442,7 @@ static void blkfront_connect(struct blkfront_info *info) for (i = 0; i < info->nr_rings; i++) kick_pending_request_queues(&info->rinfo[i]); + /* FIXME: handle error. */ device_add_disk(&info->xbdev->dev, info->gd, NULL); info->is_ready = 1; diff --git a/drivers/block/xsysace.c b/drivers/block/xsysace.c index edafc73..7683337 100644 --- a/drivers/block/xsysace.c +++ b/drivers/block/xsysac...

Hi, I''m currently trying to install xapi on debian (unstable), following the following wiki page: http://wiki.xensource.com/xenwiki/XAPI_on_debian 1. Install squeeze 32-bits (it''s not specified on the wiki, but I guess it wont work with 64-bit as the xapi *.deb files are for 32). note: you must leave an unused 1mb partition somewhere when creating your

Unlike full virtualization in which the virtual machine provides the same platform interface as running natively on the hardware, paravirtualization requires modification to the guest operating system to work with the platform interface provided by the hypervisor. Xen was designed with performance in mind. Calls to the hypervisor are minimized, batched if necessary, and non-critical codepaths

The race condition is noticed between disk_add() and disk attributes, on virtio-blk hotplug. Userspace listens to the KOBJ_ADD uevent generated in add_disk(). At that point we haven't created the serial attribute file, therefore depending on how fast udev reacts, the /dev/disk/by-id/ entry doesn't always get created. As pointed out by Christoph Hellwig in the specific fix [1], virtio-blk

The race condition is noticed between disk_add() and disk attributes, on virtio-blk hotplug. Userspace listens to the KOBJ_ADD uevent generated in add_disk(). At that point we haven't created the serial attribute file, therefore depending on how fast udev reacts, the /dev/disk/by-id/ entry doesn't always get created. As pointed out by Christoph Hellwig in the specific fix [1], virtio-blk

This patch series implements the Linux Xen guest in terms of the paravirt-ops interface. The features in implemented this patch series are: * domU only * UP only (most code is SMP-safe, but there's no way to create a new vcpu) * writable pagetables, with late pinning/early unpinning (no shadow pagetable support) * supports both PAE and non-PAE modes * xen console * virtual block

This patch series implements the Linux Xen guest in terms of the paravirt-ops interface. The features in implemented this patch series are: * domU only * UP only (most code is SMP-safe, but there's no way to create a new vcpu) * writable pagetables, with late pinning/early unpinning (no shadow pagetable support) * supports both PAE and non-PAE modes * xen console * virtual block

This patch series implements the Linux Xen guest in terms of the paravirt-ops interface. The features in implemented this patch series are: * domU only * UP only (most code is SMP-safe, but there's no way to create a new vcpu) * writable pagetables, with late pinning/early unpinning (no shadow pagetable support) * supports both PAE and non-PAE modes * xen console * virtual block

This is an attempt to fix the issue that some disks' sysfs attributes are not ready at the time its KOBJ_ADD event is sent. The symptom is during device hotplug, udev may fail to find certain attributes, such as serial or wwn, of the disk. As a result the /dev/disk/by-id entries are not created. The cause is device_add_disk emits the uevent before returning, and the callers have to create

This is an attempt to fix the issue that some disks' sysfs attributes are not ready at the time its KOBJ_ADD event is sent. The symptom is during device hotplug, udev may fail to find certain attributes, such as serial or wwn, of the disk. As a result the /dev/disk/by-id entries are not created. The cause is device_add_disk emits the uevent before returning, and the callers have to create

Hi Andi, This patch series implements the Linux Xen guest as a paravirt_ops backend. The features in implemented this patch series are: * domU only * UP only (most code is SMP-safe, but there's no way to create a new vcpu) * writable pagetables, with late pinning/early unpinning (no shadow pagetable support) * supports both PAE and non-PAE modes * xen hvc console (console=hvc0) *

Hi Andi, This patch series implements the Linux Xen guest as a paravirt_ops backend. The features in implemented this patch series are: * domU only * UP only (most code is SMP-safe, but there's no way to create a new vcpu) * writable pagetables, with late pinning/early unpinning (no shadow pagetable support) * supports both PAE and non-PAE modes * xen hvc console (console=hvc0) *