Re: [Xen-devel] WARNING: at drivers/xen/gntdev.c:426 unmap_if_in_range+0x5d/0x60 [xen_gntdev]()

2014-12-16 Thread Christopher S. Aker
On Dec 15, 2014, at 6:11 AM, David Vrabel wrote: > On 11/12/14 15:12, Christopher S. Aker wrote: >> Xen: 4.4.2-pre (28573:f6f6236af933) + xsa111, xsa112, xsa114 >> Dom0: 3.17.4 >> >> Things go badly after a day or four. We've hit this on a number of >>

Re: [Xen-devel] WARNING: at drivers/xen/gntdev.c:426 unmap_if_in_range+0x5d/0x60 [xen_gntdev]()

2014-12-14 Thread Christopher S. Aker
> On Dec 11, 2014, at 10:12 AM, Christopher S. Aker wrote: > > Xen: 4.4.2-pre (28573:f6f6236af933) + xsa111, xsa112, xsa114 > Dom0: 3.17.4 > > Things go badly after a day or four. We've hit this on a number of > previously healthy hosts, since moving from 3.10.x d

[Xen-devel] WARNING: at drivers/xen/gntdev.c:426 unmap_if_in_range+0x5d/0x60 [xen_gntdev]()

2014-12-11 Thread Christopher S. Aker
Xen: 4.4.2-pre (28573:f6f6236af933) + xsa111, xsa112, xsa114 Dom0: 3.17.4 Things go badly after a day or four. We've hit this on a number of previously healthy hosts, since moving from 3.10.x dom0 to 3.17.4: printk: 5441 messages suppressed. grant_table.c:567:d0 Failed to obtain maptrack handle

[Xen-devel] netback: Carrier off / Carrier on again, rinse, repeat

2014-12-11 Thread Christopher S. Aker
Xen: 4.4.2-pre (28573:f6f6236af933) + xsa111, xsa112, xsa114 Dom0: 3.17.4 We recently moved our dom0 from 3.10.x to 3.17.4, in order to avoid a netback host crash that has been plaguing us. After doing so, the new multi-queue netback stuff constantly on/offs carrier on the vif, spamming the con