Hi,
I'm stumped by a weird development in measured CPU utilization when testing an
upgrade path from 3.14.70 to 4.4.14.
I'm running, on identical hardware (2 4-core Xeon E5420), a HA
(active/standby) pair of firewall/loadbalancer VMs. The OS on the host and the
VM is identical - openSUSE 13.1
On Monday 12 January 2015 08:51:54 Eric Dumazet wrote:
> On Mon, 2015-01-12 at 17:39 +0100, Patrick Schaaf wrote:
> >
> > Not to comment on the ifalias thing, which I think is unneccessary,
> > too, but matching on interface names instead of only ifindex, is
> > definit
On Monday 12 January 2015 17:22:57 Patrick McHardy wrote:
> On 12.01, Patrick Schaaf wrote:
> >
> > Interfaces come and go through many different actions. There's the admin
> > downing and upping stuff like bridges or bonds. There's stuff like libvirt
> >
On Sunday 15 November 2015 16:58:33 Grant Zhang wrote:
>
> Have you tried the two patches Eric mentioned? One of my 4.1.11 server
> just hanged with very similar stack trace and I am wondering whether the
> aforementioned patches would help.
Sorry, Grant - I'm sticking to 3.14.xx for now.
best r
Dear kernel developers,
I recently started to upgrade my production hosts and VMs from the 3.14 series
to 4.1 kernels, starting with 4.1.6. Yesterday, for the second time after I
started these upgrades, I experienced one of our webserver VMs hanging.
The first time this happened, the VM hung co
5 matches
Mail list logo
