** Changed in: linux (Ubuntu)
Status: In Progress => Fix Released
** Changed in: linux (Ubuntu Trusty)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
On Tuesday, March 01, 2016 at 17:41, Joseph Salisbury wrote:
> Thanks for the update, Oskar. Would you say this bug is now resolved?
> If so, I can close it.
Yeah, so far so good, feel free to close it!
Regards,
Oskar
--
You received this bug notification because you are a member of Ubuntu
Thanks for the update, Oskar. Would you say this bug is now resolved?
If so, I can close it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1499203
Title:
memory leak in hv_storvsc
On Friday, December 11, 2015 at 09:58, Oskar Liljeblad wrote:
> > > Would it be possible for you test test the latest mainline kernel, to
> > > see if the memory leak happens there as well? It can be downloaded
> > > from:
> > >
> > > http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.4-rc4-wily/
On Wednesday, December 09, 2015 at 13:17, Oskar Liljeblad wrote:
> > Would it be possible for you test test the latest mainline kernel, to
> > see if the memory leak happens there as well? It can be downloaded
> > from:
> >
> > http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.4-rc4-wily/
>
> It
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Joseph Salisbury (jsalisbury)
** Changed in: linux (Ubuntu Trusty)
Assignee: (unassigned) => Joseph Salisbury (jsalisbury)
** Changed in: linux (Ubuntu Trusty)
Status: Confirmed => In Progress
** Changed in: linux (Ubuntu)
Thanks for testing! I'm going to review the commits in mainline to see
if anything sticks out as the fix. Otherwise, we can perform a
"Reverse" bisect to identify the exact commit that fixes this.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
On Tuesday, December 08, 2015 at 18:53, Joseph Salisbury wrote:
> Would it be possible for you test test the latest mainline kernel, to
> see if the memory leak happens there as well? It can be downloaded
> from:
>
> http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.4-rc4-wily/
It is running now
Would it be possible for you test test the latest mainline kernel, to
see if the memory leak happens there as well? It can be downloaded
from:
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.4-rc4-wily/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
On Tuesday, October 20, 2015 at 19:29, Joseph Salisbury wrote:
> Actually that is a 32 bit test kernel and that bug is specific to 32
> bit. So you can disregard by last request in comment #16.
Any update on this?
Thanks
Oskar
--
You received this bug notification because you are a member of
I think this bug may be due to the same commit as in bug 1495983. I
built a test kernel for that bug. Can you test the Trusty test kernel
and see if it resolves this bug as well? It can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1495983/patched-kernel/trusty
Actually that is a 32 bit test kernel and that bug is specific to 32
bit. So you can disregard by last request in comment #16.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1499203
Title:
memory
On Friday, October 09, 2015 at 06:59, Oskar Liljeblad wrote:
> > > To see if it is the cause of this issue, I built a test kernel with a
> > > revert of commit 97b2591. The test kernel can be downloaded from:
> > >
> > > http://kernel.ubuntu.com/~jsalisbury/lp1499203/
[..]
> The
On Wednesday, October 07, 2015 at 08:57, Oskar Liljeblad wrote:
> > To see if it is the cause of this issue, I built a test kernel with a
> > revert of commit 97b2591. The test kernel can be downloaded from:
> >
> > http://kernel.ubuntu.com/~jsalisbury/lp1499203/
> >
> > Can you test this
On Tuesday, October 06, 2015 at 21:24, Joseph Salisbury wrote:
> To see if it is the cause of this issue, I built a test kernel with a
> revert of commit 97b2591. The test kernel can be downloaded from:
>
> http://kernel.ubuntu.com/~jsalisbury/lp1499203/
>
> Can you test this kernel and see if
To see if it is the cause of this issue, I built a test kernel with a
revert of commit 97b2591. The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1499203/
Can you test this kernel and see if it resolves this bug? If it does
not, we would have to perform a kernel
After a couple of days of uptime with 3.13.0-59 it seems there are no leaks, at
least not like before. There are no kmalloc-512 allocations by hv_storsvc at
all. Total Slab memory is 3.63% of MemTotal, and SUnreclaim is 0.41%. (4GB
MemTotal.)
Regards,
Oskar Liljeblad
On Wednesday, September 30,
I'd like to see if this is a regression. Would it be possible for you to test
the Ubuntu-3.13.0-59 kernel? It can be downloaded from:
https://launchpad.net/~ubuntu-security/+archive/ubuntu/ppa/+build/7723132
You would need to install the linux-image and linux-image-extra .deb
packages.
Thanks
Hi! I've installed the 3.13.0-59 kernel below on one of the (most)
troubled machines. We should be able to see results in less than a
day or so. I will get back to you!
Thanks
Oskar
On Wednesday, September 30, 2015 at 17:46, Joseph Salisbury wrote:
> I'd like to see if this is a regression.
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
** Tags added: kernel-da-key kernel-hyper-v
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1499203
Title:
memory leak in hv_storvsc
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1499203
Title:
memory leak in hv_storvsc (3.13.0-63-generic)
To manage
apport information
** Tags added: apport-collected
** Description changed:
Slab and SUnreclaim values in /proc/meminfo keep increasing. On one
servers it reached 85% of physical memory after 14 days - but on most
other servers it increases more slowly. I checked /proc/slabinfo and
22 matches
Mail list logo
