[Kernel-packages] [Bug 1662378] Re: many OOMs on busy xenial IMAP server with lots of available memory

2017-02-23 Thread Paul Collins
Zero OOMs after 4 days of uptime (they started after 2 days previously) so I'd say this is fixed. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1662378 Title: many OOMs on busy xenial

[Kernel-packages] [Bug 1662378] Re: many OOMs on busy xenial IMAP server with lots of available memory

2017-02-14 Thread Paul Collins
I've scheduled install/reboot for Sunday evening UTC, and should be able to report back a few days after that. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1662378 Title: many OOMs on

[Kernel-packages] [Bug 1662378] Re: many OOMs on busy xenial IMAP server with lots of available memory

2017-02-06 Thread Paul Collins
** Attachment added: "lspci-vnvn.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1662378/+attachment/4814448/+files/lspci-vnvn.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu.

[Kernel-packages] [Bug 1662378] [NEW] many OOMs on busy xenial IMAP server with lots of available memory

2017-02-06 Thread Paul Collins
Public bug reported: We recently noticed that a busy xenial IMAP server with about 22 days uptime has been logging a lot of OOM messages. The machine has 24G of memory. Below please find some typical memory info. I noted that there was about 11G of memory allocated to slab, and since all of

[Kernel-packages] [Bug 1602577] Re: [arm64] compute nodes unstable after upgrading from 4.2 to 4.4 kernel

2016-08-10 Thread Paul Collins
Kernel from #24 fails to boot with the following, and keeps looping. Unclear if it's due to a problem with our system or with the kernel. I've sought advice from someone more familiar with the hardware we're using and will update with any further info. 306 bytes read in 18 ms (16.6 KiB/s) ##