Some good and bad news: I have been testing this in a running Gnome 3
environment.  I decided to start testing on console.  On console, all
kernels seem to fail using crypt swap.  This suggests to me that failure
must depend on current memory usage, dirty ratio, or some such runtime

However, the good news, I have kernel messages on console.  I'm
attaching a screen shot, since none of them get written to syslog.  A
typical message is: task dm_write:xxx blocked for more than 120 seconds

There are no problems when not using dm_crypt for swap, i.e. 'normal'

** Attachment added: "Screenshot of console error messages during hang"

You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.

  Cryptoswap not working in Bionic

Status in linux package in Ubuntu:
Status in linux source package in Bionic:

Bug description:
  I have cryptoswap set up both with the 2 GB default swap file and an 8
  GB swap partition with 8 GB of ram.  However, the system does not use
  this swap when it should.  For example, if I run a little test code
  which attempts to allocate 10 GB of memory in 1 GB chuncks, the system
  hangs with no obvious use of swap.  E.g. running top shows no swap use
  before the hang.  However, if I replace cryptoswap by standard swap,
  it works as expected: allocates the requested memory and exits, using
  swap.  Of course, my disk is slow, so this takes some time but it does

  I originally noticed this problem when compiling a very large
  application.  The system would hang on ld.  I've checked hardware
  using memtest and stress.  No problems.  This took me days to track
  down but I'm 99% certain now that the problem is with cryptoswap.  If
  I compile with cryptoswap: hang.  If I compile with standard swap: no

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-13-generic 4.15.0-13.14
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
   /dev/snd/controlC1:  weinberg   2425 F.... pulseaudio
   /dev/snd/controlC0:  weinberg   2425 F.... pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr  9 11:57:23 2018
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=8d33a538-4ec4-418d-b277-be1a9a1c1113
  InstallationDate: Installed on 2018-03-12 (28 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180114)
  MachineType: LENOVO 20ARA0S100
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic 
root=UUID=b6683bc1-7dd5-4afd-8e70-f69253403b71 ro quiet splash vt.handoff=1
   linux-restricted-modules-4.15.0-13-generic N/A
   linux-backports-modules-4.15.0-13-generic  N/A
   linux-firmware                             1.173
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install) 03/19/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GJET74WW (2.24 )
  dmi.board.asset.tag: Not Available 20ARA0S100
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
dmi:bvnLENOVO:bvrGJET74WW(2.24):bd03/19/2014:svnLENOVO:pn20ARA0S100:pvrThinkPadT440s:rvnLENOVO:rn20ARA0S100:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: ThinkPad T440s 20ARA0S100
  dmi.product.version: ThinkPad T440s
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:

Mailing list:
Post to     :
Unsubscribe :
More help   :

Reply via email to