I'd like to note that I tested/verified BOTH these kernel version in
their respective Proposed states that have the ipvs fix. We really
most need the 16.04 4.15 hwe kernel released, which appears to be in
progress but this is a bionic bug so its unclear if another step is
required.
These
Thanks, that source change makes sense. Hopefully now that the similar
bug:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1819786
Has been marked with a status of "Fix Released" we can get a similar
result here?
--
You received this bug notification because you are a member of Ubuntu
The test kernel supplied for the 4.15 kernel in the 18.04LTS release
fixed the identical issue there:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1819786
With our wider 16.04 deployment with the HWE 4.15 kernel we'd especially wish
to see the same version of the fix applied here too.
Well, my apologies. I retract my skepticism! Your referenced -47
kernel above appears to have fixed the problem, while the stock -47
kernel showed the failure when I tested it this evening first (I already
had the distributed 4.15.0-47 kernel installed, then I removed it and
installed your
Thanks for getting back to me on this. Sorry for the slow response, did not
get (or see?) an email notification about an update.
I'll try the -47 kernel you referenced but I'm skeptical since the
failure occurs on the -46 and the -47 doesn't show any changelog for the
ipvs refcount issue. Nor
** Tags added: bionic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1817247
Title:
4.15 kernel's ip_vs module gets refcount errors with --ops usage
To manage notifications about this bug go to:
This report does not appear to have received any human's attention yet
at Ubuntu, even though it was written weeks ago and is a significant
performance/functionality concern that the --ops facility can not be
used as is. It must be patched. Unfortunately for us in the interim,
it was discovered
Public bug reported:
On our 16.04LTS (and earlier) systems we used the ipvsadm --ops UDP
support (one-packet scheduling) to get a better distribution amongst
our real servers behind the load-balancer for some small subset of
applications.
This has worked fine through the 4.4.0-xxx kernels. But
** Description changed:
On our 16.04LTS system we use the ipvsadm --ops UDP support (one-packet
scheduling) to get a better distribution amongst our real servers behind
the load-balancer for some small subset of applications.
This has worked fine through the 4.4.0-xxx kernels. But
Public bug reported:
On our 16.04LTS system we use the ipvsadm --ops UDP support (one-packet
scheduling) to get a better distribution amongst our real servers behind
the load-balancer for some small subset of applications.
This has worked fine through the 4.4.0-xxx kernels. But when we
started
Thanks so much for the rapid turnaround on this report guys. I've
modified the tag to the verification-done-trusty, as requested. I
pulled down all the linux-image, source, and dbgsyms for the
3.13.0-97.144 kernel from proposed for installing/testing. I verified
the source code manually as
** Tags added: verified-test-kernel-works
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1618299
Title:
IPv6 with LVS Performance issue in latest 3.13LTS kernels
To manage notifications about this
Joseph, the commits you've included appear to be correct to me. I've
tested this kernel as best I can without the dbgsym package. I really
could use that package so I could verify the performance with "perf" as
well as use "systemtap" to verify stuff is going down the right paths.
But I did use
Thanks so much Joseph! My apologies on not seeing this earlier that you
had a test kernel ready, I was offsite almost all of last week and
swamped. Will download it now and test it later this evening or
tomorrow morning in my test rig. By any chance, so as to aid my
systemtap monitoring, do you
Public bug reported:
We experienced a major performance regression between 12.04's 3.2 kernels
and 14.04's 3.13 kernels when using IPv6 with the LVS load-balancing
facility. Through analysis of perf events and a workaround we've
determined that an upstream fix is available which addresses the
I too have the nautilus read-only misbehavior on the very latest
12.04LTS (x86_64) system and have the following observations, including
a simple-enough workaround since running into this problem quite a while
back
I can cause the false read-only behavior on demand by first inserting a
Summary:
Tried 3.11rc7, very happy with how it behaved in our testing. Tried
this week's 3.12rc5, disappointed that a step backwards was taken
on that one for us. The difference for us was in the low memory killer
that was configured in the 3.11rc7 build but not the 3.12rc5 system.
Details
Christopher, its looks like I actually have a reasonable record of the
VMWare version I was using for this reproduction despite having
regularly updated my VMWare. . The VMWare installer has a log that
shows that at the time of the reproduction/report here I was running the
VMWare vmplayer 4.0.4
for that.
-- Marc --
On Fri, Aug 9, 2013 at 7:35 PM, Christopher M. Penalver
christopher.m.penal...@gmail.com wrote:
Marc Hasson, could you please test the latest upstream kernel available
following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow
additional upstream developers
So, its been many weeks without any kind of acknowledgement of either my
previous note in this bug from March nor the 10.04 variant I filed in
bug #1161202 for the 10.04 base.
Is there any way to get a response of anything further to do on these
matters? You guys have the scripts/description and
** Tags added: kernel-bug-exists-upstream
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1154876
Title:
3.2.0-38 and earlier systems hang with heavy memory usage
To manage notifications about this
Public bug reported:
The purpose of this bug is to report/emphasize the severe number of
system hangs, which require power-cycling, on our deployment of servers
running the 10.04LTS (Lucid) release. The issue here is essentially
identical to that reported for the 3.2 kernels on 12.04LTS in bug
Public bug reported:
As the summary says, we are unable to find the linux-image-3.2.0-31
-generic-dbgsym*.ddeb package. We need this for our kernel so that we
can get more effective crash dumps. We have many systems deployed with
the 3.2.0-31 kernel and its not convenient to upgrade them at
** Attachment added: Requested lspci-vnvn.log
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1160674/+attachment/3599940/+files/lspci-vnvn.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
My testing on the 3.9 kernel has been underway since the note above, its
surpassed 11 days of running the loads from the scripts attached, and
even higher. The previous 3.2 and 3.5 kernel testing never exceeded 4.5
days before hanging solidly, and usually were less.
So, the 3.9 kernel appears to
Sure Joseph, in progress. I have the 3.9 kernel you referenced now
running my tests on my 12.04 system. Its so far behaving normally, it
will likely take a few days to know whether there is any difference as
far as the hang is concerned.
Just for the record, I had previously tested with: linux-
Public bug reported:
Background
We've been experiencing mysterious hangs on our 2.6.38-16 Ubuntu 10.04
systems in the field. The systems have large amounts of memory and disk,
along with up to a couple dozen CPU threads. Our operations folks have
to power-cycle the machines to recover them,
** Attachment added: boot up messages until standard running state of OOMs
spew out
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1154876/+attachment/3573090/+files/console_boot_output.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Attachment added: dmesg file from boot, mostly duplicates start of
console_boot_output.txt
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1154876/+attachment/3573109/+files/dmesg_of_boot.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Attachment added: last messages on serial console when system hung
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1154876/+attachment/3573110/+files/console_last_output.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: kdb session demo'ing where system is spinning
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1154876/+attachment/3573111/+files/console_kdb_session.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: Machine environment and script/data used in our testbed
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1154876/+attachment/3573112/+files/reproduction_info.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Attachment added: Requested version.log
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1154876/+attachment/3573113/+files/version.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1154876
** Attachment added: Requested lspci-vnvn.log
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1154876/+attachment/3573114/+files/lspci-vnvn.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
34 matches
Mail list logo
