← Back to team overview

kernel-packages team mailing list archive

[Bug 1132789] Re: linux-image-3.2.0-38-generic & winbind issue

 

[Expired for linux (Ubuntu) because there has been no activity for 60
days.]

** Changed in: linux (Ubuntu)
       Status: Incomplete => Expired

-- 
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/1132789

Title:
  linux-image-3.2.0-38-generic & winbind issue

Status in “linux” package in Ubuntu:
  Expired

Bug description:
  On ubuntu 12.04.1 client with authorized Windows AD account (through
  samba/winbind 3.6.3), there seems to be a bug when kernel 3.2.0-38 is
  applied. ps or pgrep is causing a "cannot allocate memory" error and
  the cpu is temporarily maxed out more or less.

  An strace from ps running on -38 kernel (Ubuntu 3.2.0-38.60-generic
  3.2.37) gives:

  mmap(NULL, 135168, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x7f4053c48000
  mremap(0x7f4053c48000, 135168, 266240, MREMAP_MAYMOVE) = 0x7f4053c07000
  mremap(0x7f4053c07000, 266240, 528384, MREMAP_MAYMOVE) = 0x7f4053b86000
  mremap(0x7f4053b86000, 528384, 1052672, MREMAP_MAYMOVE) = 0x7f4052e78000
  mremap(0x7f4052e78000, 1052672, 2101248, MREMAP_MAYMOVE) = 0x7f4052c77000
  mremap(0x7f4052c77000, 2101248, 4198400, MREMAP_MAYMOVE) = 0x7f4052876000
  mremap(0x7f4052876000, 4198400, 8392704, MREMAP_MAYMOVE) = 0x7f4052075000
  mremap(0x7f4052075000, 8392704, 16781312, MREMAP_MAYMOVE) = 0x7f4051074000
  mremap(0x7f4051074000, 16781312, 33558528, MREMAP_MAYMOVE) = 0x7f404f073000
  mremap(0x7f404f073000, 33558528, 67112960, MREMAP_MAYMOVE) = 0x7f404b072000
  mremap(0x7f404b072000, 67112960, 134221824, MREMAP_MAYMOVE) = 0x7f4043071000
  mremap(0x7f4043071000, 134221824, 268439552, MREMAP_MAYMOVE) = 0x7f4033070000
  mremap(0x7f4033070000, 268439552, 536875008, MREMAP_MAYMOVE) = 0x7f401306f000
  mremap(0x7f401306f000, 536875008, 1073745920, MREMAP_MAYMOVE) = 0x7f3fd306e000
  mremap(0x7f3fd306e000, 1073745920, 2147487744, MREMAP_MAYMOVE) = -1 EFAULT (Bad address)
  mmap(NULL, 2147487744, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = -1     ENOMEM (Cannot allocate memory)
  brk(0x8074e000)                         = 0x745000
  mmap(NULL, 2147618816, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = -1     ENOMEM (Cannot allocate memory)
  open("/sys/devices/system/cpu/online", O_RDONLY|O_CLOEXEC) = 6
  read(6, "0\n", 8192)                    = 2
  close(6)                                = 0
  mmap(NULL, 134217728, PROT_NONE, MAP_PRIVATE|MAP_ANONYMOUS|MAP_NORESERVE, -1, 0) =     0x7f3ecb04c000
  munmap(0x7f3ecb04c000, 16465920)        = 0
  munmap(0x7f3ed0000000, 50642944)        = 0
  mprotect(0x7f3ecc000000, 135168, PROT_READ|PROT_WRITE) = 0
  mmap(NULL, 2147487744, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = -1     ENOMEM (Cannot allocate memory)
  write(2, "xrealloc: realloc(-2147483648) f"..., 37xrealloc: realloc(-2147483648) failed) = 37
  write(2, "Cannot allocate memory\n", 23Cannot allocate memory
  ) = 23
  exit_group(1)                           = ?

  If i go back to 37, it works fine again.

  Also seen on server 12.04  http://askubuntu.com/questions/258180/why-
  does-running-ps-results-in-cannot-allocate-memory-error/259253#259253

  attached dump is from virtualbox instance, same result regardless of
  virtual machine or not.

  Br,

  Björn

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1132789/+subscriptions