Ubuntu 16.04: “Out of memory” errors after upgrade to 4.4.0-59

Post by lmns » Sun, Jan 29, 2017, 2:06 PM UTC

twic wrote: post #94

_0w8t wrote: post #75

Earlier quoted context omitted.

zswap makes swap useful on the server as it results in gradual slowdown when the system has used all the ram. And if the system runs at 75% of CPU, then there is room for such slowdown.

I hadn't heard of zswap [0]: "Zswap is a lightweight compressed cache for swap pages. It takes pages that are in the process of being swapped out and attempts to compress them into a dynamically allocated RAM-based memory pool. [...] Zswap is a new feature as of v3.11 [...] zswap is a work in progress and should be considered experimental." The return of RAM Doubler! The naming is initially confusing if you're alread…

Post by digi_owl » Sun, Jan 29, 2017, 2:58 PM UTC

lima wrote: post #137

JdeBP wrote: post #112

Earlier quoted context omitted.

andrewshadura is right. Here's just one of your items that is bunkum, for an example. > their own custom [...] init system of Upstart when they could have contributed to System upstart was developed several years, just under half a decade, before systemd even existed; it was used by Fedora for three years.

It's true though that Canonical consistently "does their own thing" and then fails to establish it as a standard for whatever reason (technical, political, CLA...). Anyone who adopted the new thing then has to migrate. Eucalyptus vs OpenStack (ever heard of Eucalyptus?) Bazaar vs Git (Git won) LaunchPad vs Github (LaunchPad is alive and well, but Github won the popularity contest) Wayland vs Mir (Wayland won) upstart…

Post by boomboomsubban » Sun, Jan 29, 2017, 3:19 PM UTC

dump12332-1 wrote: post #48

kev009 wrote: post #43

Earlier quoted context omitted.

Errr.. the linked article means no, it is not safe to just cron an apt-get upgrade. In theory Debian is maintaining ABI/API. In practice there are issues. Rolling releases in practice have better tradeoffs, but require continuous deployment. On a workstation there are really no significant issues. On a production infrastructure, you need to use poudriere to maintain your own repos and orchestrate a branching and inst…

>Errr.. the linked article means no, it is not safe to just cron an apt-get upgrade. In theory Debian is maintaining ABI/API. In practice there are issues. Rolling releases in practice have better tradeoffs, but require continuous deployment. On a workstation there are really no significant issues. On a production infrastructure, you need to use poudriere to maintain your own repos and orchestrate a branching and ins…

Post by polpo » Sun, Jan 29, 2017, 4:04 PM UTC

mrmondo wrote: post #2

It's not just a bunch of people setting cm.swappieness to 0 is it? That behaviour changed and now prevents going into swap /ever/ where it used to mean go into swap as a last resort. Changing it to 1 fixes the issue and will act like the old behaviour or only swapping as a last result. Regardless, it's things like this why we never recommend people use Ubuntu - years of poorly packaged and tested software. If you wan…

Post by cagey » Sun, Jan 29, 2017, 4:50 PM UTC

pacifika wrote: post #115

mianos wrote: post #77

Earlier quoted context omitted.

I used to use this to clean boot. dpkg -l 'linux- ' | sed '/^ii/!d;/'"$(uname -r | sed "s/\(. \)-\([^0-9]\+\)/\1/")"'/d;s/^[^ ]* [^ ]* \([^ ] \). /\1/;/[0-9]/!d' | xargs -p sudo apt-get -y purge

What does it do?

   # mystery one-liner from https://news.ycombinator.com/item?id=13513171
   # dpkg -l 'linux-' | sed '/^ii/!d;/'"$(uname -r | sed "s/\(.\)-\([^0-9]\+\)/\1/")"'/d;s/^[^ ]* [^ ]* \([^ ]\)./\1/;/[0-9]/!d' | xargs -p sudo apt-get -y purge
   # my corrected/improved version:
   noncurrent_kernel_pkgs() { dpkg -l 'linux-*[0-9]*' | sed '/^ii/!d;/'"$(uname -r | sed "s/\(.\)-\([^0-9]\+\)/\1/")"'/d;s/^ii *\([^ ][^ ]*\)[^ ]*.*/\1/' ; }
   # corrections/(possible-)improvements:
   # - dpkg -l 'linux-' # returns nothing
   # - dpkg -l 'linux-*[0-9]*' # moves 'pkgnm must contain a number' rule (last sed cmd in orig: '/[0-9]/!d') forward
   # - pkgnm isolation/extraction was broken (did dpkg output change?)

  kg@kg-VirtualBox:~$ noncurrent_kernel_pkgs
  linux-headers-4.4.0-43
  linux-headers-4.4.0-43-generic
  linux-headers-4.4.0-45
  linux-headers-4.4.0-45-generic
  linux-headers-4.4.0-53
  linux-headers-4.4.0-53-generic
  linux-headers-4.4.0-57
  linux-headers-4.4.0-57-generic
  linux-image-4.4.0-43-generic
  linux-image-4.4.0-45-generic
  linux-image-4.4.0-53-generic
  linux-image-4.4.0-57-generic
  linux-image-extra-4.4.0-43-generic
  linux-image-extra-4.4.0-45-generic
  linux-image-extra-4.4.0-53-generic
  linux-image-extra-4.4.0-57-generic
  kg@kg-VirtualBox:~$ uname -r
  4.4.0-59-generic
  kg@kg-VirtualBox:~$