[Kernel-packages] [Bug 2049689] Re: linux-image-5.15.0-94-generic breaks partprobe on empty loopback device

[Martin Pitt]

** Tags added: jammy regression-release

** Tags removed: regression-release
** Tags added: regression-update

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed in Ubuntu.
https://bugs.launchpad.net/bugs/2049689

Title:
  linux-image-5.15.0-94-generic breaks partprobe on empty loopback
  device

Status in linux package in Ubuntu:
  New
Status in linux-signed package in Ubuntu:
  New
Status in linux source package in Jammy:
  New
Status in linux-signed source package in Jammy:
  New

Bug description:
  This is with the kernel from jammy-proposed (linux-
  image-5.15.0-94-generic 5.15.0-94.104).

  Do this:

  # dd if=/dev/zero of=/tmp/file bs=1M count=50
  # partprobe "$(losetup --show --find /tmp/file)"

  Notice this very odd error message:

  Error: Partition(s) 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15,
  16, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 31, 32,
  33, 34, 35, 36, 37, 38, 39, 40, 41, 42, 43, 44, 45, 46, 47, 48, 49,
  50, 51, 52, 53, 54, 55, 56, 57, 58, 59, 60, 61, 62, 63, 64 on
  /dev/loop2 have been written, but we have been unable to inform the
  kernel of the change, probably because it/they are in use.  As a
  result, the old partition(s) will remain in use.  You should reboot
  now before making further changes.

  That's a result of an ioctl changing its error code in an incompatible
  way between kernel versions 5.15.0.91.88 and 5.15.0.94.91, confusing
  partprobe.

  5.15.0.91.88:
  ioctl(3, BLKPG, {op=BLKPG_DEL_PARTITION, flags=0, datalen=152, data={start=0, 
length=0, pno=1, devname="", volname=""}}) = -1 ENXIO (No such device or 
address)

  5.15.0.94.91:
  ioctl(3, BLKPG, {op=BLKPG_DEL_PARTITION, flags=0, datalen=152, data={start=0, 
length=0, pno=1, devname="", volname=""}}) = -1 EINVAL (Invalid argument)

  This is a userspace API break which impacts GNU parted and util-linux
  (as confirmed by the util-linux maintainer).

  This issue was discovered as part of Cockpit CI here:
  https://github.com/cockpit-project/bots/pull/5793

  This issue is being discussed on LKML here (with a patch likely to
  land soon): https://lkml.org/lkml/2024/1/15/147

  lsb_release -rd:
  Description:  Ubuntu 22.04.3 LTS
  Release:  22.04

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


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 2049689] Re: linux-image-5.15.0-94-generic breaks partprobe on empty loopback device

[Martin Pitt]

** Also affects: linux (Ubuntu Jammy)
   Importance: Undecided
   Status: New

** Also affects: linux-signed (Ubuntu Jammy)
   Importance: Undecided
   Status: New

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

Title:
  linux-image-5.15.0-94-generic breaks partprobe on empty loopback
  device

Status in linux package in Ubuntu:
  New
Status in linux-signed package in Ubuntu:
  New
Status in linux source package in Jammy:
  New
Status in linux-signed source package in Jammy:
  New

Bug description:
  This is with the kernel from jammy-proposed (linux-
  image-5.15.0-94-generic 5.15.0-94.104).

  Do this:

  # dd if=/dev/zero of=/tmp/file bs=1M count=50
  # partprobe "$(losetup --show --find /tmp/file)"

  Notice this very odd error message:

  Error: Partition(s) 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15,
  16, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 31, 32,
  33, 34, 35, 36, 37, 38, 39, 40, 41, 42, 43, 44, 45, 46, 47, 48, 49,
  50, 51, 52, 53, 54, 55, 56, 57, 58, 59, 60, 61, 62, 63, 64 on
  /dev/loop2 have been written, but we have been unable to inform the
  kernel of the change, probably because it/they are in use.  As a
  result, the old partition(s) will remain in use.  You should reboot
  now before making further changes.

  That's a result of an ioctl changing its error code in an incompatible
  way between kernel versions 5.15.0.91.88 and 5.15.0.94.91, confusing
  partprobe.

  5.15.0.91.88:
  ioctl(3, BLKPG, {op=BLKPG_DEL_PARTITION, flags=0, datalen=152, data={start=0, 
length=0, pno=1, devname="", volname=""}}) = -1 ENXIO (No such device or 
address)

  5.15.0.94.91:
  ioctl(3, BLKPG, {op=BLKPG_DEL_PARTITION, flags=0, datalen=152, data={start=0, 
length=0, pno=1, devname="", volname=""}}) = -1 EINVAL (Invalid argument)

  This is a userspace API break which impacts GNU parted and util-linux
  (as confirmed by the util-linux maintainer).

  This issue was discovered as part of Cockpit CI here:
  https://github.com/cockpit-project/bots/pull/5793

  This issue is being discussed on LKML here (with a patch likely to
  land soon): https://lkml.org/lkml/2024/1/15/147

  lsb_release -rd:
  Description:  Ubuntu 22.04.3 LTS
  Release:  22.04

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


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 2049689] Re: linux-image-5.15.0-94-generic breaks partprobe on empty loopback device

[Martin Pitt]

** Also affects: linux (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  linux-image-5.15.0-94-generic breaks partprobe on empty loopback
  device

Status in linux package in Ubuntu:
  New
Status in linux-signed package in Ubuntu:
  New

Bug description:
  This is with the kernel from jammy-proposed (linux-
  image-5.15.0-94-generic 5.15.0-94.104).

  Do this:

  # dd if=/dev/zero of=/tmp/file bs=1M count=50
  # partprobe "$(losetup --show --find /tmp/file)"

  Notice this very odd error message:

  Error: Partition(s) 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15,
  16, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 31, 32,
  33, 34, 35, 36, 37, 38, 39, 40, 41, 42, 43, 44, 45, 46, 47, 48, 49,
  50, 51, 52, 53, 54, 55, 56, 57, 58, 59, 60, 61, 62, 63, 64 on
  /dev/loop2 have been written, but we have been unable to inform the
  kernel of the change, probably because it/they are in use.  As a
  result, the old partition(s) will remain in use.  You should reboot
  now before making further changes.

  That's a result of an ioctl changing its error code in an incompatible
  way between kernel versions 5.15.0.91.88 and 5.15.0.94.91, confusing
  partprobe.

  5.15.0.91.88:
  ioctl(3, BLKPG, {op=BLKPG_DEL_PARTITION, flags=0, datalen=152, data={start=0, 
length=0, pno=1, devname="", volname=""}}) = -1 ENXIO (No such device or 
address)

  5.15.0.94.91:
  ioctl(3, BLKPG, {op=BLKPG_DEL_PARTITION, flags=0, datalen=152, data={start=0, 
length=0, pno=1, devname="", volname=""}}) = -1 EINVAL (Invalid argument)

  This is a userspace API break which impacts GNU parted and util-linux
  (as confirmed by the util-linux maintainer).

  This issue was discovered as part of Cockpit CI here:
  https://github.com/cockpit-project/bots/pull/5793

  This issue is being discussed on LKML here (with a patch likely to
  land soon): https://lkml.org/lkml/2024/1/15/147

  lsb_release -rd:
  Description:  Ubuntu 22.04.3 LTS
  Release:  22.04

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


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1861053] Re: no fatrace output in focal

[Martin Pitt]

** Changed in: fatrace (Ubuntu)
   Status: New => Incomplete

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

Title:
  no fatrace output in focal

Status in fatrace package in Ubuntu:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hello, fatrace in focal doesn't seem to work for me in focal.

  Start fatrace in one terminal, and perform file operations in another
  terminal: man man, echo hi > hi, echo hi > /run/user/1000/hi, etc.

  sarnold@millbarge:~$ sudo fatrace
  [sudo] password for sarnold: 
  ^Csarnold@millbarge:~$ sudo strace -yy fatrace
  execve("/usr/sbin/fatrace", ["fatrace"], 0x7ffcc89ad9c8 /* 15 vars */) = 0
  brk(NULL)   = 0x55c9a1947000
  arch_prctl(0x3001 /* ARCH_??? */, 0x7ffd18dbde80) = -1 EINVAL (Invalid 
argument)
  access("/etc/ld.so.preload", R_OK)  = -1 ENOENT (No such file or 
directory)
  openat(AT_FDCWD, "/etc/ld.so.cache", O_RDONLY|O_CLOEXEC) = 3
  fstat(3, {st_mode=S_IFREG|0644, st_size=71040, ...}) = 0
  mmap(NULL, 71040, PROT_READ, MAP_PRIVATE, 3, 0) = 
0x7f3539b15000
  close(3)  = 0
  openat(AT_FDCWD, "/lib/x86_64-linux-gnu/libc.so.6", O_RDONLY|O_CLOEXEC) = 
3
  read(3, 
"\177ELF\2\1\1\3\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0\360r\2\0\0\0\0\0"..., 832) = 832
  lseek(3, 64, SEEK_SET) = 64
  read(3, 
"\6\0\0\0\4\0\0\0@\0\0\0\0\0\0\0@\0\0\0\0\0\0\0@\0\0\0\0\0\0\0"..., 784) = 784
  lseek(3, 848, SEEK_SET) = 848
  read(3, 
"\4\0\0\0\20\0\0\0\5\0\0\0GNU\0\2\0\0\300\4\0\0\0\3\0\0\0\0\0\0\0", 32) = 32
  lseek(3, 880, SEEK_SET) = 880
  read(3, 
"\4\0\0\0\24\0\0\0\3\0\0\0GNU\0u\343\342\331Yj\256%\0230\256~\363\371\32\204"...,
 68) = 68
  fstat(3, {st_mode=S_IFREG|0755, 
st_size=2025032, ...}) = 0
  mmap(NULL, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 
0x7f3539b13000
  lseek(3, 64, SEEK_SET) = 64
  read(3, 
"\6\0\0\0\4\0\0\0@\0\0\0\0\0\0\0@\0\0\0\0\0\0\0@\0\0\0\0\0\0\0"..., 784) = 784
  lseek(3, 848, SEEK_SET) = 848
  read(3, 
"\4\0\0\0\20\0\0\0\5\0\0\0GNU\0\2\0\0\300\4\0\0\0\3\0\0\0\0\0\0\0", 32) = 32
  lseek(3, 880, SEEK_SET) = 880
  read(3, 
"\4\0\0\0\24\0\0\0\3\0\0\0GNU\0u\343\342\331Yj\256%\0230\256~\363\371\32\204"...,
 68) = 68
  mmap(NULL, 2032984, PROT_READ, MAP_PRIVATE|MAP_DENYWRITE, 
3, 0) = 0x7f3539922000
  mmap(0x7f3539947000, 1540096, PROT_READ|PROT_EXEC, 
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 
0x25000) = 0x7f3539947000
  mmap(0x7f3539abf000, 303104, PROT_READ, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 
3, 0x19d000) = 0x7f3539abf000
  mmap(0x7f3539b09000, 24576, PROT_READ|PROT_WRITE, 
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 
0x1e6000) = 0x7f3539b09000
  mmap(0x7f3539b0f000, 13656, PROT_READ|PROT_WRITE, 
MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0x7f3539b0f000
  close(3) = 0
  arch_prctl(ARCH_SET_FS, 0x7f3539b14580) = 0
  mprotect(0x7f3539b09000, 12288, PROT_READ) = 0
  mprotect(0x55c99fee8000, 4096, PROT_READ) = 0
  mprotect(0x7f3539b53000, 4096, PROT_READ) = 0
  munmap(0x7f3539b15000, 71040)   = 0
  getpid()= 120700
  fanotify_init(FAN_CLASS_NOTIF, O_RDONLY|O_LARGEFILE) = 
3
  brk(NULL)   = 0x55c9a1947000
  brk(0x55c9a1968000) = 0x55c9a1968000
  openat(AT_FDCWD, "/proc/self/mounts", O_RDONLY|O_CLOEXEC) = 
4
  fstat(4, {st_mode=S_IFREG|0444, st_size=0, ...}) = 0
  read(4, "sysfs /sys sysfs rw,nosuid,nodev"..., 1024) = 
1024
  access("sysfs", F_OK)   = -1 ENOENT (No such file or 
directory)
  access("proc", F_OK)= -1 ENOENT (No such file or 
directory)
  access("udev", F_OK)= -1 ENOENT (No such file or 
directory)
  access("devpts", F_OK)  = -1 ENOENT (No such file or 
directory)
  access("tmpfs", F_OK)   = -1 ENOENT (No such file or 
directory)
  access("rpool/ROOT/ubuntu", F_OK)   = -1 ENOENT (No such file or 
directory)
  access("securityfs", F_OK)  = -1 ENOENT (No such file or 
directory)
  access("tmpfs", F_OK)   = -1 ENOENT (No such file or 
directory)
  access("tmpfs", F_OK)   = -1 ENOENT (No such file or 
directory)
  access("tmpfs", F_OK)   = -1 ENOENT (No such file or 
directory)
  access("cgroup2", F_OK) = -1 ENOENT (No such file or 
directory)
  access("cgroup", F_OK)  = -1 ENOENT (No such file or 
directory)
  access("pstore", F_OK)  = -1 ENOENT (No such file or 
directory)
  access("efivarfs", F_OK)= -1 ENOENT (No such file or 
directory)
  read(4, "de=700 0 0\ncgroup /sys/fs/cgroup"..., 1024) = 
1024
  access("none", F_OK)= -1 ENOENT (No such file or 
directory)
  access("cgroup", F_OK)  = -1 ENOENT (No such file or 
directory)
  access("cgroup", F_OK)  = -1 ENOENT (No such file or 
directory)
  

[Kernel-packages] [Bug 1861053] Re: no fatrace output in focal

[Martin Pitt]

FTR, I just ran fatrace a lot in a current Ubuntu 20.04 VM to debug
#1885188, and it seems fine.

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

Title:
  no fatrace output in focal

Status in fatrace package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hello, fatrace in focal doesn't seem to work for me in focal.

  Start fatrace in one terminal, and perform file operations in another
  terminal: man man, echo hi > hi, echo hi > /run/user/1000/hi, etc.

  sarnold@millbarge:~$ sudo fatrace
  [sudo] password for sarnold: 
  ^Csarnold@millbarge:~$ sudo strace -yy fatrace
  execve("/usr/sbin/fatrace", ["fatrace"], 0x7ffcc89ad9c8 /* 15 vars */) = 0
  brk(NULL)   = 0x55c9a1947000
  arch_prctl(0x3001 /* ARCH_??? */, 0x7ffd18dbde80) = -1 EINVAL (Invalid 
argument)
  access("/etc/ld.so.preload", R_OK)  = -1 ENOENT (No such file or 
directory)
  openat(AT_FDCWD, "/etc/ld.so.cache", O_RDONLY|O_CLOEXEC) = 3
  fstat(3, {st_mode=S_IFREG|0644, st_size=71040, ...}) = 0
  mmap(NULL, 71040, PROT_READ, MAP_PRIVATE, 3, 0) = 
0x7f3539b15000
  close(3)  = 0
  openat(AT_FDCWD, "/lib/x86_64-linux-gnu/libc.so.6", O_RDONLY|O_CLOEXEC) = 
3
  read(3, 
"\177ELF\2\1\1\3\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0\360r\2\0\0\0\0\0"..., 832) = 832
  lseek(3, 64, SEEK_SET) = 64
  read(3, 
"\6\0\0\0\4\0\0\0@\0\0\0\0\0\0\0@\0\0\0\0\0\0\0@\0\0\0\0\0\0\0"..., 784) = 784
  lseek(3, 848, SEEK_SET) = 848
  read(3, 
"\4\0\0\0\20\0\0\0\5\0\0\0GNU\0\2\0\0\300\4\0\0\0\3\0\0\0\0\0\0\0", 32) = 32
  lseek(3, 880, SEEK_SET) = 880
  read(3, 
"\4\0\0\0\24\0\0\0\3\0\0\0GNU\0u\343\342\331Yj\256%\0230\256~\363\371\32\204"...,
 68) = 68
  fstat(3, {st_mode=S_IFREG|0755, 
st_size=2025032, ...}) = 0
  mmap(NULL, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 
0x7f3539b13000
  lseek(3, 64, SEEK_SET) = 64
  read(3, 
"\6\0\0\0\4\0\0\0@\0\0\0\0\0\0\0@\0\0\0\0\0\0\0@\0\0\0\0\0\0\0"..., 784) = 784
  lseek(3, 848, SEEK_SET) = 848
  read(3, 
"\4\0\0\0\20\0\0\0\5\0\0\0GNU\0\2\0\0\300\4\0\0\0\3\0\0\0\0\0\0\0", 32) = 32
  lseek(3, 880, SEEK_SET) = 880
  read(3, 
"\4\0\0\0\24\0\0\0\3\0\0\0GNU\0u\343\342\331Yj\256%\0230\256~\363\371\32\204"...,
 68) = 68
  mmap(NULL, 2032984, PROT_READ, MAP_PRIVATE|MAP_DENYWRITE, 
3, 0) = 0x7f3539922000
  mmap(0x7f3539947000, 1540096, PROT_READ|PROT_EXEC, 
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 
0x25000) = 0x7f3539947000
  mmap(0x7f3539abf000, 303104, PROT_READ, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 
3, 0x19d000) = 0x7f3539abf000
  mmap(0x7f3539b09000, 24576, PROT_READ|PROT_WRITE, 
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 
0x1e6000) = 0x7f3539b09000
  mmap(0x7f3539b0f000, 13656, PROT_READ|PROT_WRITE, 
MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0x7f3539b0f000
  close(3) = 0
  arch_prctl(ARCH_SET_FS, 0x7f3539b14580) = 0
  mprotect(0x7f3539b09000, 12288, PROT_READ) = 0
  mprotect(0x55c99fee8000, 4096, PROT_READ) = 0
  mprotect(0x7f3539b53000, 4096, PROT_READ) = 0
  munmap(0x7f3539b15000, 71040)   = 0
  getpid()= 120700
  fanotify_init(FAN_CLASS_NOTIF, O_RDONLY|O_LARGEFILE) = 
3
  brk(NULL)   = 0x55c9a1947000
  brk(0x55c9a1968000) = 0x55c9a1968000
  openat(AT_FDCWD, "/proc/self/mounts", O_RDONLY|O_CLOEXEC) = 
4
  fstat(4, {st_mode=S_IFREG|0444, st_size=0, ...}) = 0
  read(4, "sysfs /sys sysfs rw,nosuid,nodev"..., 1024) = 
1024
  access("sysfs", F_OK)   = -1 ENOENT (No such file or 
directory)
  access("proc", F_OK)= -1 ENOENT (No such file or 
directory)
  access("udev", F_OK)= -1 ENOENT (No such file or 
directory)
  access("devpts", F_OK)  = -1 ENOENT (No such file or 
directory)
  access("tmpfs", F_OK)   = -1 ENOENT (No such file or 
directory)
  access("rpool/ROOT/ubuntu", F_OK)   = -1 ENOENT (No such file or 
directory)
  access("securityfs", F_OK)  = -1 ENOENT (No such file or 
directory)
  access("tmpfs", F_OK)   = -1 ENOENT (No such file or 
directory)
  access("tmpfs", F_OK)   = -1 ENOENT (No such file or 
directory)
  access("tmpfs", F_OK)   = -1 ENOENT (No such file or 
directory)
  access("cgroup2", F_OK) = -1 ENOENT (No such file or 
directory)
  access("cgroup", F_OK)  = -1 ENOENT (No such file or 
directory)
  access("pstore", F_OK)  = -1 ENOENT (No such file or 
directory)
  access("efivarfs", F_OK)= -1 ENOENT (No such file or 
directory)
  read(4, "de=700 0 0\ncgroup /sys/fs/cgroup"..., 1024) = 
1024
  access("none", F_OK)= -1 ENOENT (No such file or 
directory)
  access("cgroup", F_OK)  = -1 ENOENT (No such file or 
directory)
  access("cgroup", F_OK)  = -1 ENOENT (No such 

[Kernel-packages] [Bug 1682077] Re: nested KVM fails - KVM: entry failed, hardware error 0x0

[Martin Pitt]

This happens in about half of the xenial semaphoreci.com instances as
well:

$ uname -a
Linux semaphore-light-1809b 4.4.0-131-generic #157-Ubuntu SMP Thu Jul 12 
15:51:36 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

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

Title:
  nested KVM fails  - KVM: entry failed, hardware error 0x0

Status in linux package in Ubuntu:
  Confirmed
Status in linux-lts-xenial package in Ubuntu:
  Confirmed

Bug description:
  Hello,

  We just noticed that systemd's autopkgtests have started failing often
  on amd64 for all releases, when run in Canonical's scalingstack cloud.

  This is nested KVM I think.

  TEST RUN: Basic systemd setup
  + /usr/bin/qemu-system-x86_64 -smp 1 -net none -m 512M -nographic -kernel 
/boot/vmlinuz-4.10.0-19-generic -drive 
format=raw,cache=unsafe,file=/var/tmp/systemd-test.unFR7V/rootdisk.img -initrd 
/boot/initrd.img-4.10.0-19-generic -machine accel=kvm -enable-kvm -cpu host 
-append 'root=/dev/sda1 raid=noautodetect loglevel=2 init=/lib/systemd/systemd 
ro console=ttyS0 selinux=0 systemd.unified_cgroup_hierarchy=no  '
  KVM: entry failed, hardware error 0x0
  EAX= EBX= ECX= EDX=000206a1
  ESI= EDI= EBP= ESP=
  EIP=fff0 EFL=0002 [---] CPL=0 II=0 A20=1 SMM=0 HLT=0
  ES =   9300
  CS =f000   9b00
  SS =   9300
  DS =   9300
  FS =   9300
  GS =   9300
  LDT=   8200
  TR =   8b00
  GDT=  
  IDT=  
  CR0=6010 CR2= CR3= CR4=
  DR0= DR1= DR2= 
DR3= 
  DR6=0ff0 DR7=0400
  EFER=
  Code=d8 66 e8 d8 a2 ff ff 66 5b 66 83 c4 08 66 5b 66 5e 66 c3 90  5b e0 
00 f0 30 36 2f 32 33 2f 39 39 00 fc 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

  I have observed a failure on the compute node (region lgw01)

Linux amemasu 4.4.0-59-generic #80~14.04.1-Ubuntu SMP Fri Jan 6
  18:02:02 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux

  and a pass of the exact same package on the compute node (region
  lcy01)

Linux kissel 3.13.0-95-generic #142-Ubuntu SMP Fri Aug 12 17:00:09
  UTC 2016 x86_64 x86_64 x86_64 GNU/Linux

  Here's an example log-

https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-zesty-ci-train-ppa-service-2713/zesty/amd64/s/systemd/20170411_182221_b8bea@/log.gz

  I found bug #1329434 which looks more or less identical and was fixed
  for 3.13. Perhaps it regressed in 4.4?

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1787396] Re: ss crashes when using --no-header

[Martin Pitt]

I confirm this on Ubuntu 18.04 (bionic) with 4.15.0-2ubuntu1. It is
fixed in 18.10 (cosmic) with  4.18.0-1ubuntu2.

** Also affects: iproute2 (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Changed in: iproute2 (Ubuntu Bionic)
   Status: New => Confirmed

** Changed in: iproute2 (Ubuntu)
   Status: Confirmed => Fix Released

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to iproute2 in Ubuntu.
Matching subscriptions: iproute2
https://bugs.launchpad.net/bugs/1787396

Title:
  ss crashes when using --no-header

Status in iproute2 package in Ubuntu:
  Fix Released
Status in iproute2 source package in Bionic:
  Confirmed

Bug description:
  Steps to reproduce:

  1) Listen on port 8989:
  $ nc -l 8989 &

  2) Check that ss can list this listener:
  $ ss --no-header -nto state listening 'sport = 8989'
  010.0.0.0:8989  0.0.0.0:*

  3) Ask ss to list listeners on a port where nothing listens
  $ kill %1 # stops nc
  $ ss --no-header -nto state listening 'sport = 8989'
  Segmentation fault (core dumped)

  In the above, removing "--no-header" avoids the segfault.

  
  Additional information:

  $ lsb_release -rd
  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04
  $ apt-cache policy iproute2
  iproute2:
Installed: 4.15.0-2ubuntu1
Candidate: 4.15.0-2ubuntu1
Version table:
   *** 4.15.0-2ubuntu1 500
  500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: iproute2 4.15.0-2ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18
  Uname: Linux 4.15.0-32-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Aug 16 08:17:52 2018
  InstallationDate: Installed on 2018-07-15 (32 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180714)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  SourcePackage: iproute2
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1696480] Re: python3-dbusmock / test_no_adapters test fails with bluez 5.45

[Martin Pitt]

I released 0.16.8 upstream and uploaded it to Debian unstable, from
where it should autosync into Ubuntu devel soon.

** Changed in: python-dbusmock (Ubuntu)
   Status: Triaged => Fix Committed

** Changed in: python-dbusmock
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1696480

Title:
  python3-dbusmock / test_no_adapters test fails with bluez 5.45

Status in python-dbusmock:
  Fix Released
Status in bluez package in Ubuntu:
  Invalid
Status in python-dbusmock package in Ubuntu:
  Fix Committed

Bug description:
  
https://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html#bluez
  http://autopkgtest.ubuntu.com/packages/p/python-dbusmock/artful/amd64

  With bluez 5.45 python3-dbusmock tests fail with:

  ==
  FAIL: test_no_adapters (__main__.TestBlueZ5)
  --
  Traceback (most recent call last):
    File "./test_bluez5.py", line 107, in test_no_adapters
  self.assertEqual([l for l in out if 'Waiting to connect' not in l], [])
  AssertionError: Lists differ: ['org.freedesktop.DBus.Mock.MethodCalled', 
'registered', 'unregistered'] != []

  First list contains 3 additional elements.
  First extra element 0:
  'org.freedesktop.DBus.Mock.MethodCalled'

  - ['org.freedesktop.DBus.Mock.MethodCalled', 'registered', 'unregistered']
  + []

  --

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: bluez 5.45-0ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15
  Uname: Linux 4.10.0-22-generic x86_64
  ApportVersion: 2.20.5-0ubuntu4
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Wed Jun  7 18:01:13 2017
  InstallationDate: Installed on 2013-09-03 (1372 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130902)
  InterestingModules: bnep bluetooth
  MachineType: ASUSTeK COMPUTER INC. UX32VD
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-22-generic.efi.signed 
root=UUID=1004226d-a9db-46c7-bd28-eca0806c12f2 ro pcie_aspm=force 
drm.vblankoffdelay=1 i915.semaphores=1 init=/lib/systemd/systemd-bootchart
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/29/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX32VD.214
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX32VD
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX32VD.214:bd01/29/2013:svnASUSTeKCOMPUTERINC.:pnUX32VD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX32VD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: UX32VD
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  hciconfig:

  rfkill:
   0: phy0: Wireless LAN
    Soft blocked: no
    Hard blocked: no
  upstart.bluetooth.override: manual

To manage notifications about this bug go to:
https://bugs.launchpad.net/python-dbusmock/+bug/1696480/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1696480] Re: python3-dbusmock / test_no_adapters test fails with bluez 5.45

[Martin Pitt]

Thanks Daniel! PR merged upstream. There are a few other test
deprecation warnings/failures I'm looking into before doing a release.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1696480

Title:
  python3-dbusmock / test_no_adapters test fails with bluez 5.45

Status in python-dbusmock:
  Fix Committed
Status in bluez package in Ubuntu:
  Invalid
Status in python-dbusmock package in Ubuntu:
  Triaged

Bug description:
  
https://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html#bluez
  http://autopkgtest.ubuntu.com/packages/p/python-dbusmock/artful/amd64

  With bluez 5.45 python3-dbusmock tests fail with:

  ==
  FAIL: test_no_adapters (__main__.TestBlueZ5)
  --
  Traceback (most recent call last):
    File "./test_bluez5.py", line 107, in test_no_adapters
  self.assertEqual([l for l in out if 'Waiting to connect' not in l], [])
  AssertionError: Lists differ: ['org.freedesktop.DBus.Mock.MethodCalled', 
'registered', 'unregistered'] != []

  First list contains 3 additional elements.
  First extra element 0:
  'org.freedesktop.DBus.Mock.MethodCalled'

  - ['org.freedesktop.DBus.Mock.MethodCalled', 'registered', 'unregistered']
  + []

  --

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: bluez 5.45-0ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15
  Uname: Linux 4.10.0-22-generic x86_64
  ApportVersion: 2.20.5-0ubuntu4
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Wed Jun  7 18:01:13 2017
  InstallationDate: Installed on 2013-09-03 (1372 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130902)
  InterestingModules: bnep bluetooth
  MachineType: ASUSTeK COMPUTER INC. UX32VD
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-22-generic.efi.signed 
root=UUID=1004226d-a9db-46c7-bd28-eca0806c12f2 ro pcie_aspm=force 
drm.vblankoffdelay=1 i915.semaphores=1 init=/lib/systemd/systemd-bootchart
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/29/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX32VD.214
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX32VD
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX32VD.214:bd01/29/2013:svnASUSTeKCOMPUTERINC.:pnUX32VD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX32VD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: UX32VD
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  hciconfig:

  rfkill:
   0: phy0: Wireless LAN
    Soft blocked: no
    Hard blocked: no
  upstart.bluetooth.override: manual

To manage notifications about this bug go to:
https://bugs.launchpad.net/python-dbusmock/+bug/1696480/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1645631] Re: Sending files fails because obex not loaded

[Martin Pitt]

** No longer affects: systemd (Ubuntu)

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1645631

Title:
  Sending files fails because obex not loaded

Status in bluez package in Ubuntu:
  New
Status in gnome-bluetooth package in Ubuntu:
  New

Bug description:
  If I run bluetooth-sendto from command line and try to send the file,
  it quits after selecting the target device with following command line
  output:

  "Acquiring proxy failed: Error calling StartServiceByName for
  org.bluez.obex: GDBus.Error:org.freedesktop.systemd1.NoSuchUnit: Unit
  dbus-org.bluez.obex.service not found."

  After I run "systemctl --user start obex", it proceeds to send the
  file. Even then it for some reason gets stuck, but I do not know what
  causes it and it is probably a different problem.

  This system is upgraded from xenial.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: gnome-bluetooth 3.20.0-1ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-27.29-generic 4.8.1
  Uname: Linux 4.8.0-27-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  Date: Tue Nov 29 11:04:11 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-09-12 (77 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  ProcEnviron:
   LANGUAGE=fi
   TERM=xterm
   PATH=(custom, no user)
   LANG=C
   SHELL=/bin/bash
  SourcePackage: gnome-bluetooth
  UpgradeStatus: Upgraded to yakkety on 2016-11-01 (27 days ago)

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1303275] Re: dkms_packages.py crashed with TypeError in __main__: Type str doesn't support the buffer API

[Martin Pitt]

** Changed in: dkms (Ubuntu Trusty)
 Assignee: Martin Pitt (pitti) => (unassigned)

** No longer affects: dkms (Ubuntu Wily)

** Changed in: dkms (Ubuntu Trusty)
   Status: New => Triaged

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to dkms in Ubuntu.
https://bugs.launchpad.net/bugs/1303275

Title:
  dkms_packages.py crashed with TypeError in __main__: Type str doesn't
  support the buffer API

Status in dkms package in Ubuntu:
  Fix Released
Status in dkms source package in Trusty:
  Triaged

Bug description:
  happened on upgrade from 13.10 to 14.04

  ProblemType: Crash
  DistroRelease: Ubuntu 14.04
  Package: dkms 2.2.0.3-1.1ubuntu5
  ProcVersionSignature: Ubuntu 3.8.0-19.30-generic 3.8.8
  Uname: Linux 3.8.0-19-generic x86_64
  ApportVersion: 2.14.1-0ubuntu1
  Architecture: amd64
  Date: Sun Apr  6 11:19:45 2014
  ExecutablePath: /usr/share/apport/package-hooks/dkms_packages.py
  InstallationDate: Installed on 2013-03-29 (372 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130328)
  InterpreterPath: /usr/bin/python3.4
  PackageArchitecture: all
  ProcCmdline: python3 /usr/share/apport/package-hooks/dkms_packages.py -m 
nvidia-331-updates -v 331.38 -k 3.13.0-23-generic
  PythonArgs: ['/usr/share/apport/package-hooks/dkms_packages.py', '-m', 
'nvidia-331-updates', '-v', '331.38', '-k', '3.13.0-23-generic']
  SourcePackage: dkms
  Title: dkms_packages.py crashed with TypeError in __main__: Type str doesn't 
support the buffer API
  Traceback:
   Traceback (most recent call last):
 File "/usr/share/apport/package-hooks/dkms_packages.py", line 87, in 

   if 'Segmentation fault' in report['DKMSBuildLog']:
   TypeError: Type str doesn't support the buffer API
  UpgradeStatus: Upgraded to trusty on 2014-04-06 (0 days ago)
  UserGroups:

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1398859] Re: unmounting NTFS causes mount.ntfs process to get stuck in eternal kernel deep sleep

[Martin Pitt]

I also see this with exfat, so it rather seems to be related to fuse (as
both ntfs-3g and exfat use fuse). Curiously I do not see this when
running the tests on my laptop or on the Scalingstack cloud infra, just
when I run them in QEMU.

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

Title:
  unmounting NTFS causes mount.ntfs process to get stuck in eternal
  kernel deep sleep

Status in linux package in Ubuntu:
  Confirmed
Status in udisks2 package in Ubuntu:
  Fix Released

Bug description:
  Since Mid-November the udisks2 test (https://jenkins.qa.ubuntu.com/job
  /vivid-adt-udisks2/? shows it happened between Nov 13 and 19) exhibits
  a regression with NTFS: Unmounting causes the ntfs-3g process to go
  into kernel deep sleep and umount hangs forever.

  This can be reproduced with

sudo apt install ntfs-3g
sudo modprobe scsi_debug
# check dmesg which drive this created; e. g. /dev/sda
sudo mkntfs -F /dev/sda
sudo mount /dev/sda /mnt

  Now you have a process which is happy:
  root 12821  0.0  0.0  15272  1948 ?Ss   15:49   0:00 
/sbin/mount.ntfs /dev/sda /mnt -o rw

  You can work with /mnt, edit files, etc. But now unmount:

sudo umount /mnt

  This never returns, and  the process goes into uninterruptible kernel
  sleep ("D"):

  root 12928  0.0  0.0  15272  1948 ?Ds   15:55   0:00
  /sbin/mount.ntfs /dev/sda /mnt -o rw

  The strace for the umount until the hang is

  ubuntu@autopkgtest:~$ sudo strace -vvtts1024 -p 12928
  Process 12928 attached
  15:56:17.938299 read(4, 
"0\0\0\0\2\0\0\0\2\0\0\0\0\0\0\0\1\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\1\0\0\0\0\0\0\0",
 135168) = 48
  15:56:22.338931 read(4, 
"(\0\0\0&\0\0\0\3\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0",
 135168) = 40
  15:56:22.339637 sendto(5, "<29>Dec  3 15:56:22 ntfs-3g[12928]: Unmounting 
/dev/sda ()\n", 59, MSG_NOSIGNAL, NULL, 0) = 59
  15:56:22.340509 fsync(3)= 0
  15:56:22.341188 fcntl(3, F_SETLK, {type=F_UNLCK, whence=SEEK_SET, start=0, 
len=0}) = 0
  15:56:22.341759 close(3

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: ntfs-3g 1:2013.1.13AR.1-2ubuntu3
  ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7
  Uname: Linux 3.16.0-25-generic x86_64
  ApportVersion: 2.15-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Dec  3 15:48:12 2014
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-11-20 (13 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Alpha amd64 (20141119)
  SourcePackage: ntfs-3g
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1398859] Re: unmounting NTFS causes mount.ntfs process to get stuck in eternal kernel deep sleep

[Martin Pitt]

> Curiously I do not see this when running the tests on my laptop

And of course in the minute I write this it does happen again (I ran the
test maybe 20 times today, and only just now it happened):

[11359.569157] INFO: task systemd-udevd:341 blocked for more than 120 seconds.
[11359.569163]   Not tainted 4.8.0-29-generic 
#31~lp1626436ProposedWithTwoPatches
[11359.569165] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this 
message.
[11359.569167] systemd-udevd   D a31788e77ba8 0   341  1 0x0100
[11359.569173]  a31788e77ba8 00ff84c71a68 a3149967 
a31788e82ac0
[11359.569177]  88e77db0 a31788e78000 a317893bc070 
a317893bc088
[11359.569179]  a31788e77be0 a3149cf771c0 a31788e77bc0 
85296905
[11359.569182] Call Trace:
[11359.569190]  [] schedule+0x35/0x80
[11359.569193]  [] rwsem_down_read_failed+0x103/0x160
[11359.569197]  [] call_rwsem_down_read_failed+0x18/0x30
[11359.569200]  [] down_read+0x20/0x40
[11359.569202]  [] get_super.part.7+0x95/0xd0
[11359.569204]  [] get_super+0x26/0x30
[11359.569208]  [] fsync_bdev+0x18/0x60
[11359.569211]  [] invalidate_partition+0x24/0x50
[11359.569213]  [] rescan_partitions+0x53/0x2b0
[11359.569216]  [] ? security_capable+0x48/0x60
[11359.569218]  [] __blkdev_reread_part+0x65/0x70
[11359.569220]  [] blkdev_reread_part+0x23/0x40
[11359.569222]  [] blkdev_ioctl+0x425/0x910
[11359.569225]  [] ? __seccomp_filter+0x67/0x260
[11359.569228]  [] block_ioctl+0x3d/0x50
[11359.569231]  [] do_vfs_ioctl+0xa3/0x610
[11359.569233]  [] ? __secure_computing+0x43/0xe0
[11359.569236]  [] ? syscall_trace_enter+0xce/0x2f0
[11359.569239]  [] SyS_ioctl+0x79/0x90
[11359.569241]  [] do_syscall_64+0x5e/0xc0
[11359.569244]  [] entry_SYSCALL64_slow_path+0x25/0x25
[11359.569320] INFO: task mount.ntfs:15670 blocked for more than 120 seconds.
[11359.569323]   Not tainted 4.8.0-29-generic 
#31~lp1626436ProposedWithTwoPatches
[11359.569324] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this 
message.
[11359.569325] mount.ntfs  D a314d0d1bd68 0 15670   5268 0x
[11359.569329]  a314d0d1bd68 00010003 a3178bef9c80 
a3149967
[11359.569332]  3d862ecf a314d0d1c000 a3149cf771dc 
a3149967
[11359.569334]   a3149cf771e0 a314d0d1bd80 
85296905
[11359.569337] Call Trace:
[11359.569340]  [] schedule+0x35/0x80
[11359.569342]  [] schedule_preempt_disabled+0xe/0x10
[11359.569344]  [] __mutex_lock_slowpath+0xb9/0x130
[11359.569347]  [] mutex_lock+0x1f/0x30
[11359.569350]  [] blkdev_put+0x20/0x110
[11359.569352]  [] blkdev_close+0x34/0x70
[11359.569354]  [] __fput+0xe7/0x230
[11359.569356]  [] fput+0xe/0x10
[11359.569358]  [] task_work_run+0x80/0xa0
[11359.569361]  [] exit_to_usermode_loop+0xc2/0xd0
[11359.569363]  [] syscall_return_slowpath+0x4e/0x60
[11359.569366]  [] entry_SYSCALL_64_fastpath+0xa6/0xa8


root 15670  0.0  0.0  16040   460 ?Ds   10:41   0:00 
/sbin/mount.ntfs /dev/sdb /run/media/root/553BDB6430706196 -o 
rw,nodev,nosuid,uid=0,gid=0,uhelper=udisks2


(uninterruptible kernel deep sleep, 'D' state).

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

Title:
  unmounting NTFS causes mount.ntfs process to get stuck in eternal
  kernel deep sleep

Status in linux package in Ubuntu:
  Confirmed
Status in udisks2 package in Ubuntu:
  Fix Released

Bug description:
  Since Mid-November the udisks2 test (https://jenkins.qa.ubuntu.com/job
  /vivid-adt-udisks2/? shows it happened between Nov 13 and 19) exhibits
  a regression with NTFS: Unmounting causes the ntfs-3g process to go
  into kernel deep sleep and umount hangs forever.

  This can be reproduced with

sudo apt install ntfs-3g
sudo modprobe scsi_debug
# check dmesg which drive this created; e. g. /dev/sda
sudo mkntfs -F /dev/sda
sudo mount /dev/sda /mnt

  Now you have a process which is happy:
  root 12821  0.0  0.0  15272  1948 ?Ss   15:49   0:00 
/sbin/mount.ntfs /dev/sda /mnt -o rw

  You can work with /mnt, edit files, etc. But now unmount:

sudo umount /mnt

  This never returns, and  the process goes into uninterruptible kernel
  sleep ("D"):

  root 12928  0.0  0.0  15272  1948 ?Ds   15:55   0:00
  /sbin/mount.ntfs /dev/sda /mnt -o rw

  The strace for the umount until the hang is

  ubuntu@autopkgtest:~$ sudo strace -vvtts1024 -p 12928
  Process 12928 attached
  15:56:17.938299 read(4, 
"0\0\0\0\2\0\0\0\2\0\0\0\0\0\0\0\1\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\1\0\0\0\0\0\0\0",
 135168) = 48
  15:56:22.338931 read(4, 
"(\0\0\0&\0\0\0\3\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0",
 135168) = 40
  15:56:22.339637 sendto(5, "<29>Dec  3 15:56:22 ntfs-3g[12928]: Unmounting 
/dev/sda ()\n", 59, MSG_NOSIGNAL, NULL, 0) = 59
  15:56:22.340509 fsync(3)   

[Kernel-packages] [Bug 1424676] Proposed package removed from archive

[Martin Pitt]

The version of bcmwl in the proposed pocket of Precise that was
purported to fix this bug report has been removed because the bugs that
were to be fixed by the upload were not verified in a timely (105 days)
fashion.

** Changed in: bcmwl (Ubuntu Precise)
   Status: New => Won't Fix

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bcmwl in Ubuntu.
https://bugs.launchpad.net/bugs/1424676

Title:
  bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu2: bcmwl kernel module
  failed to build with kernel 4.0 [error: ‘STATION_INFO_TX_BITRATE’
  undeclared (first use in this function)]

Status in bcmwl package in Ubuntu:
  Fix Released
Status in bcmwl source package in Precise:
  Won't Fix
Status in bcmwl source package in Vivid:
  Won't Fix

Bug description:
  bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu2: bcmwl kernel module
  failed to build

  ProblemType: Package
  DistroRelease: Ubuntu 15.04
  Package: bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu2
  ProcVersionSignature: Ubuntu 3.18.0-13.14-generic 3.18.5
  Uname: Linux 3.18.0-13-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.16.1-0ubuntu2
  Architecture: amd64
  DKMSKernelVersion: 4.0.0-04rc1-generic
  Date: Mon Feb 23 18:14:07 2015
  DuplicateSignature: 
dkms:bcmwl-kernel-source:6.30.223.248+bdcom-0ubuntu2:/var/lib/dkms/bcmwl/6.30.223.248+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.c:1444:20:
 error: ‘STATION_INFO_TX_BITRATE’ undeclared (first use in this function)
  InstallationDate: Installed on 2014-11-22 (93 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Alpha amd64 (20141121)
  PackageVersion: 6.30.223.248+bdcom-0ubuntu2
  SourcePackage: bcmwl
  Title: bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu2: bcmwl kernel module 
failed to build
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1415880] Re: 14e4:4365 bcmwl-kernel source: fix for null pointer crash

[Martin Pitt]

The version of bcmwl in the proposed pocket of Precise that was
purported to fix this bug report has been removed because the bugs that
were to be fixed by the upload were not verified in a timely (105 days)
fashion.

** Changed in: bcmwl (Ubuntu Precise)
   Status: Fix Committed => Won't Fix

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bcmwl in Ubuntu.
https://bugs.launchpad.net/bugs/1415880

Title:
  14e4:4365 bcmwl-kernel source: fix for null pointer crash

Status in Dell Sputnik:
  Confirmed
Status in bcmwl package in Ubuntu:
  Fix Released
Status in bcmwl source package in Precise:
  Won't Fix
Status in bcmwl source package in Vivid:
  Won't Fix
Status in bcmwl source package in Wily:
  Fix Released

Bug description:
  [Impact]

   * bcmwl does not compile on new kernels (or HWE kernels)
   * bcmwl suffers from null reference bug 

  [Test Case]

   * public PPA provided to community and feedback
   * based on patch available to other distros
   * comment #42

  [Regression Potential]

   * for changes on kernel support it may not compile (tested with 3.2, 3.13, 
3.18 and 4.2)
   * for the null reference change -> proved to fix problem for community based 
on feedback

  [Other Info]

  Original bug description:

  The bcmwl package as of now misses one patch for a bug that occurs
  with BCM43142 and possibly other broadcom chipsets that will look like
  random disconnects, poor wifi signal and kernel warnings, See also
  #1379524.

  Adding the patch is a fairly simple process:

  * put the patch file in /usr/src/bcmwl-6.30.223.248+bdcom/patches
  * add the following line to  /usr/src/bcmwl-6.30.223.248+bdcom/dkms.conf
  PATCH[7]="0014-null-pointer-crash.patch"
  * run: /usr/lib/dkms/common.postinst bcmwl 6.30.223.248+bdcom 
/usr/share/bcmwl x86_64 $(uname -r)

  This has fixed the issue for me. Edit: I just wanted to add that I did
  not write the patch; I merely downloaded it from a paste that was
  linked from the respective AUR package.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu1 [modified: 
usr/src/bcmwl-6.30.223.248+bdcom/dkms.conf]
  ProcVersionSignature: Ubuntu 3.16.0-29.39-generic 3.16.7-ckt2
  Uname: Linux 3.16.0-29-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.14.7-0ubuntu8.1
  Architecture: amd64
  CurrentDesktop: LXDE
  Date: Thu Jan 29 13:15:17 2015
  InstallationDate: Installed on 2015-01-26 (3 days ago)
  InstallationMedia: Lubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  SourcePackage: bcmwl
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/dell-sputnik/+bug/1415880/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1424676] Re: bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu2: bcmwl kernel module failed to build with kernel 4.0 [error: ‘STATION_INFO_TX_BITRATE’ undeclared (first use in this

[Martin Pitt]

The version of bcmwl in the proposed pocket of Precise that was
purported to fix this bug report has been removed because the bugs that
were to be fixed by the upload were not verified in a timely (105 days)
fashion.

** Also affects: bcmwl (Ubuntu Precise)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bcmwl in Ubuntu.
https://bugs.launchpad.net/bugs/1424676

Title:
  bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu2: bcmwl kernel module
  failed to build with kernel 4.0 [error: ‘STATION_INFO_TX_BITRATE’
  undeclared (first use in this function)]

Status in bcmwl package in Ubuntu:
  Fix Released
Status in bcmwl source package in Precise:
  Won't Fix
Status in bcmwl source package in Vivid:
  Won't Fix

Bug description:
  bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu2: bcmwl kernel module
  failed to build

  ProblemType: Package
  DistroRelease: Ubuntu 15.04
  Package: bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu2
  ProcVersionSignature: Ubuntu 3.18.0-13.14-generic 3.18.5
  Uname: Linux 3.18.0-13-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.16.1-0ubuntu2
  Architecture: amd64
  DKMSKernelVersion: 4.0.0-04rc1-generic
  Date: Mon Feb 23 18:14:07 2015
  DuplicateSignature: 
dkms:bcmwl-kernel-source:6.30.223.248+bdcom-0ubuntu2:/var/lib/dkms/bcmwl/6.30.223.248+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.c:1444:20:
 error: ‘STATION_INFO_TX_BITRATE’ undeclared (first use in this function)
  InstallationDate: Installed on 2014-11-22 (93 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Alpha amd64 (20141121)
  PackageVersion: 6.30.223.248+bdcom-0ubuntu2
  SourcePackage: bcmwl
  Title: bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu2: bcmwl kernel module 
failed to build
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1424676] Proposed package removed from archive

[Martin Pitt]

The version of bcmwl in the proposed pocket of Precise that was
purported to fix this bug report has been removed because the bugs that
were to be fixed by the upload were not verified in a timely (105 days)
fashion.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bcmwl in Ubuntu.
https://bugs.launchpad.net/bugs/1424676

Title:
  bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu2: bcmwl kernel module
  failed to build with kernel 4.0 [error: ‘STATION_INFO_TX_BITRATE’
  undeclared (first use in this function)]

Status in bcmwl package in Ubuntu:
  Fix Released
Status in bcmwl source package in Precise:
  Won't Fix
Status in bcmwl source package in Vivid:
  Won't Fix

Bug description:
  bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu2: bcmwl kernel module
  failed to build

  ProblemType: Package
  DistroRelease: Ubuntu 15.04
  Package: bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu2
  ProcVersionSignature: Ubuntu 3.18.0-13.14-generic 3.18.5
  Uname: Linux 3.18.0-13-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.16.1-0ubuntu2
  Architecture: amd64
  DKMSKernelVersion: 4.0.0-04rc1-generic
  Date: Mon Feb 23 18:14:07 2015
  DuplicateSignature: 
dkms:bcmwl-kernel-source:6.30.223.248+bdcom-0ubuntu2:/var/lib/dkms/bcmwl/6.30.223.248+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.c:1444:20:
 error: ‘STATION_INFO_TX_BITRATE’ undeclared (first use in this function)
  InstallationDate: Installed on 2014-11-22 (93 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Alpha amd64 (20141121)
  PackageVersion: 6.30.223.248+bdcom-0ubuntu2
  SourcePackage: bcmwl
  Title: bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu2: bcmwl kernel module 
failed to build
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1626436] Re: [4.8 regression] boot has become very slow

[Martin Pitt]

> http://kernel.ubuntu.com/~jsalisbury/lp1626436/yakkety-proposed-
patched

This is a GOOD kernel as well -- booting is almost as fast as with 4.4,
and the load doesn't explode under sbuild either.

I'm a bit confused now, I thought we already tried the two patches in
isolation -- but I think *only* against 4.6 and/or 4.7, not against 4.8.
But so much the better. ☺

Thanks for your efforts Joseph, much appreciated!

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

Title:
  [4.8 regression] boot has become very slow

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Yakkety:
  In Progress

Bug description:
  With yakkety's recent update from linux 4.4 to 4.8 booting has become
  a lot slower. It's not one service in particular, but without "quiet"
  and "splash" you can now easily read every single line instead of that
  whole wall of text zipping by. It now takes over 20s instead of ~10
  seconds to boot.

  This is even more dramatic when factoring out the recent boot hang of
  NetworkManager (bug 1622893) and disabling lightdm:

    sudo systemctl mask NetworkManager NetworkManager-wait-online
  lightdm

  then booting with 4.4 takes 1.5s and with 4.8 19.5s (!).

  Some excerps from systemd-analyze blame:

  4.4:
     474ms postfix@-.service
     395ms lxd-containers.service
     305ms networking.service

  4.8:
    4.578s postfix@-.service
    7.300s lxd-containers.service
    6.285s networking.service

  I attach the full outputs of critical-chain and analyze for 4.4 and
  4.8 for reference.

  This is much less noticeable in the running system. There is no
  immediate feeling of sluggishness (although my system is by and large
  idle).

  I compared the time of sbuilding colord under similar circumstances
  (-j4, building on tmpfs, thus no hard disk delays; running with fully
  pre-loaded apt-cacher-ng thus no random network delays), and with 4.4
  it takes 6.5 minutes and with 4.8 it takes 7.5. So that got a bit
  slower, but much less dramatically than during boot, so this is either
  happening when a lot of processes run in parallel, or is perhaps
  related to setting up cgroups.

  One thing I noticed that during sbuild in 4.8 "top" shows ridiculous
  loads (~ 250) under 4.8, while it's around 4 or 5 under 4.4. But that
  doesn't reflect in actual sluggishness, so this might be just an
  unrelated bug.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: linux-image-4.8.0-11-generic 4.8.0-11.12
  ProcVersionSignature: Ubuntu 4.8.0-11.12-generic 4.8.0-rc6
  Uname: Linux 4.8.0-11-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   martin 3049 F...m pulseaudio
   /dev/snd/pcmC0D0p:   martin 3049 F...m pulseaudio
   /dev/snd/controlC0:  martin 3049 F pulseaudio
  Date: Thu Sep 22 09:42:56 2016
  EcryptfsInUse: Yes
  MachineType: LENOVO 2324CTO
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.8.0-11-generic.efi.signed 
root=UUID=f86539b0-3a1b-4372-83b0-acdd029ade68 ro rootflags=subvol=@ 
systemd.debug-shell
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-11-generic N/A
   linux-backports-modules-4.8.0-11-generic  N/A
   linux-firmware1.161
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/09/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G2ET95WW (2.55 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2324CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: 0B98401 Pro
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG2ET95WW(2.55):bd07/09/2013:svnLENOVO:pn2324CTO:pvrThinkPadX230:rvnLENOVO:rn2324CTO:rvr0B98401Pro:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 2324CTO
  dmi.product.version: ThinkPad X230
  dmi.sys.vendor: LENOVO

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1626436] Re: [4.8 regression] boot has become very slow

[Martin Pitt]

> I noticed the comment does not have the download link. It is:
> http://kernel.ubuntu.com/~jsalisbury/lp1626436/mailine-with-two-commits/

Bazinga! Perhaps unexpectedly, this is a GOOD kernel -- boot speed is
comparable with 4.4, there is no high load after booting any more, and
shutdown is fast as well.

Thanks!

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

Title:
  [4.8 regression] boot has become very slow

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Yakkety:
  In Progress

Bug description:
  With yakkety's recent update from linux 4.4 to 4.8 booting has become
  a lot slower. It's not one service in particular, but without "quiet"
  and "splash" you can now easily read every single line instead of that
  whole wall of text zipping by. It now takes over 20s instead of ~10
  seconds to boot.

  This is even more dramatic when factoring out the recent boot hang of
  NetworkManager (bug 1622893) and disabling lightdm:

    sudo systemctl mask NetworkManager NetworkManager-wait-online
  lightdm

  then booting with 4.4 takes 1.5s and with 4.8 19.5s (!).

  Some excerps from systemd-analyze blame:

  4.4:
     474ms postfix@-.service
     395ms lxd-containers.service
     305ms networking.service

  4.8:
    4.578s postfix@-.service
    7.300s lxd-containers.service
    6.285s networking.service

  I attach the full outputs of critical-chain and analyze for 4.4 and
  4.8 for reference.

  This is much less noticeable in the running system. There is no
  immediate feeling of sluggishness (although my system is by and large
  idle).

  I compared the time of sbuilding colord under similar circumstances
  (-j4, building on tmpfs, thus no hard disk delays; running with fully
  pre-loaded apt-cacher-ng thus no random network delays), and with 4.4
  it takes 6.5 minutes and with 4.8 it takes 7.5. So that got a bit
  slower, but much less dramatically than during boot, so this is either
  happening when a lot of processes run in parallel, or is perhaps
  related to setting up cgroups.

  One thing I noticed that during sbuild in 4.8 "top" shows ridiculous
  loads (~ 250) under 4.8, while it's around 4 or 5 under 4.4. But that
  doesn't reflect in actual sluggishness, so this might be just an
  unrelated bug.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: linux-image-4.8.0-11-generic 4.8.0-11.12
  ProcVersionSignature: Ubuntu 4.8.0-11.12-generic 4.8.0-rc6
  Uname: Linux 4.8.0-11-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   martin 3049 F...m pulseaudio
   /dev/snd/pcmC0D0p:   martin 3049 F...m pulseaudio
   /dev/snd/controlC0:  martin 3049 F pulseaudio
  Date: Thu Sep 22 09:42:56 2016
  EcryptfsInUse: Yes
  MachineType: LENOVO 2324CTO
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.8.0-11-generic.efi.signed 
root=UUID=f86539b0-3a1b-4372-83b0-acdd029ade68 ro rootflags=subvol=@ 
systemd.debug-shell
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-11-generic N/A
   linux-backports-modules-4.8.0-11-generic  N/A
   linux-firmware1.161
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/09/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G2ET95WW (2.55 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2324CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: 0B98401 Pro
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG2ET95WW(2.55):bd07/09/2013:svnLENOVO:pn2324CTO:pvrThinkPadX230:rvnLENOVO:rn2324CTO:rvr0B98401Pro:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 2324CTO
  dmi.product.version: ThinkPad X230
  dmi.sys.vendor: LENOVO

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1642192] Re: i386 4.9 in -proposed fails to boot in cloud instances

[Martin Pitt]

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

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

Title:
  i386 4.9 in -proposed fails to boot in cloud instances

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I noticed a forever-looping test of linuxinfo on i386 this morning.
  This test upgrades the kernel to 4.9 in -proposed; as soon as that
  reboots, the VM never comes back. nova console-log shows:

  [1.581188] Freeing unused kernel memory: 996K (dcc37000 - dcd3)
  [1.582525] Write protecting the kernel text: 8300k
  [1.583624] Write protecting the kernel read-only data: 3344k
  [1.584845] NX-protecting the kernel data: 6036k
  [1.585921] [ cut here ]
  [1.586861] WARNING: CPU: 0 PID: 1 at 
/build/linux-UWDXbt/linux-4.9.0/arch/x86/mm/dump_pagetables.c:225 
note_page+0x6a1/0x880
  [1.589199] x86/mm: Found insecure W+X mapping at address 
c00a/0xc00a
  [1.590657] Modules linked in:
  [1.591305] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 4.9.0-1-generic 
#2-Ubuntu
  [1.592809] Hardware name: OpenStack Foundation OpenStack Nova, BIOS Bochs 
01/01/2011
  [1.593188]  dae89e70 dc3e0b05 dae89eb4 dca47958 dae89ea0 dc07299a 
dca47920 dae89ed4
  [1.593188]  0001 dca47958 00e1 dc068db1 00e1 dae89f34 
8000 
  [1.593188]  dae89ec0 dc072a06 0009  dae89eb4 dca47920 
dae89ed4 76601e21
  [1.593188] Call Trace:
  [1.593188]  [] dump_stack+0x58/0x73
  [1.593188]  [] __warn+0xea/0x110
  [1.593188]  [] ? note_page+0x6a1/0x880
  [1.593188]  [] warn_slowpath_fmt+0x46/0x60
  [1.593188]  [] note_page+0x6a1/0x880
  [1.593188]  [] ptdump_walk_pgd_level_core+0x1f5/0x300
  [1.593188]  [] ptdump_walk_pgd_level_checkwx+0x16/0x20
  [1.593188]  [] mark_rodata_ro+0xfd/0x130
  [1.593188]  [] ? rest_init+0x70/0x70
  [1.593188]  [] kernel_init+0x2c/0x100
  [1.593188]  [] ? schedule_tail+0x11/0x50
  [1.593188]  [] ? rest_init+0x70/0x70
  [1.593188]  [] ret_from_fork+0x1b/0x28
  [1.613361] ---[ end trace d63b34644638754d ]---
  [1.614368] x86/mm: Checked W+X mappings: FAILED, 96 W+X pages found.
  ...
  Begin: Waiting for root file system ... Begin: Running /scripts/local-block 
... done.
  Begin: Running /scripts/local-block ... done.
  [... repeating some 50 times... ]
  Begin: Running /scripts/local-block ... done.
  done.
  Gave up waiting for root device.  Common problems:
   - Boot args (cat /proc/cmdline)
 - Check rootdelay= (did the system wait long enough?)
 - Check root= (did the system wait for the right device?)
   - Missing modules (cat /proc/modules; ls /dev)
  ALERT!  UUID=ac6eb865-17d6-469d-b58e-8c0d49174fe4 does not exist.  Dropping 
to a shell!

  
  BusyBox v1.22.1 (Ubuntu 1:1.22.0-19ubuntu2) built-in shell (ash)
  Enter 'help' for a list of built-in commands.

  (initramfs)

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1642192] [NEW] i386 4.9 in -proposed fails to boot in cloud instances

[Martin Pitt]

Public bug reported:

I noticed a forever-looping test of linuxinfo on i386 this morning. This
test upgrades the kernel to 4.9 in -proposed; as soon as that reboots,
the VM never comes back. nova console-log shows:

[1.581188] Freeing unused kernel memory: 996K (dcc37000 - dcd3)
[1.582525] Write protecting the kernel text: 8300k
[1.583624] Write protecting the kernel read-only data: 3344k
[1.584845] NX-protecting the kernel data: 6036k
[1.585921] [ cut here ]
[1.586861] WARNING: CPU: 0 PID: 1 at 
/build/linux-UWDXbt/linux-4.9.0/arch/x86/mm/dump_pagetables.c:225 
note_page+0x6a1/0x880
[1.589199] x86/mm: Found insecure W+X mapping at address c00a/0xc00a
[1.590657] Modules linked in:
[1.591305] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 4.9.0-1-generic 
#2-Ubuntu
[1.592809] Hardware name: OpenStack Foundation OpenStack Nova, BIOS Bochs 
01/01/2011
[1.593188]  dae89e70 dc3e0b05 dae89eb4 dca47958 dae89ea0 dc07299a dca47920 
dae89ed4
[1.593188]  0001 dca47958 00e1 dc068db1 00e1 dae89f34 8000 

[1.593188]  dae89ec0 dc072a06 0009  dae89eb4 dca47920 dae89ed4 
76601e21
[1.593188] Call Trace:
[1.593188]  [] dump_stack+0x58/0x73
[1.593188]  [] __warn+0xea/0x110
[1.593188]  [] ? note_page+0x6a1/0x880
[1.593188]  [] warn_slowpath_fmt+0x46/0x60
[1.593188]  [] note_page+0x6a1/0x880
[1.593188]  [] ptdump_walk_pgd_level_core+0x1f5/0x300
[1.593188]  [] ptdump_walk_pgd_level_checkwx+0x16/0x20
[1.593188]  [] mark_rodata_ro+0xfd/0x130
[1.593188]  [] ? rest_init+0x70/0x70
[1.593188]  [] kernel_init+0x2c/0x100
[1.593188]  [] ? schedule_tail+0x11/0x50
[1.593188]  [] ? rest_init+0x70/0x70
[1.593188]  [] ret_from_fork+0x1b/0x28
[1.613361] ---[ end trace d63b34644638754d ]---
[1.614368] x86/mm: Checked W+X mappings: FAILED, 96 W+X pages found.
...
Begin: Waiting for root file system ... Begin: Running /scripts/local-block ... 
done.
Begin: Running /scripts/local-block ... done.
[... repeating some 50 times... ]
Begin: Running /scripts/local-block ... done.
done.
Gave up waiting for root device.  Common problems:
 - Boot args (cat /proc/cmdline)
   - Check rootdelay= (did the system wait long enough?)
   - Check root= (did the system wait for the right device?)
 - Missing modules (cat /proc/modules; ls /dev)
ALERT!  UUID=ac6eb865-17d6-469d-b58e-8c0d49174fe4 does not exist.  Dropping to 
a shell!


BusyBox v1.22.1 (Ubuntu 1:1.22.0-19ubuntu2) built-in shell (ash)
Enter 'help' for a list of built-in commands.

(initramfs)

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: bot-stop-nagging

** Tags added: bot-stop-nagging

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

Title:
  i386 4.9 in -proposed fails to boot in cloud instances

Status in linux package in Ubuntu:
  New

Bug description:
  I noticed a forever-looping test of linuxinfo on i386 this morning.
  This test upgrades the kernel to 4.9 in -proposed; as soon as that
  reboots, the VM never comes back. nova console-log shows:

  [1.581188] Freeing unused kernel memory: 996K (dcc37000 - dcd3)
  [1.582525] Write protecting the kernel text: 8300k
  [1.583624] Write protecting the kernel read-only data: 3344k
  [1.584845] NX-protecting the kernel data: 6036k
  [1.585921] [ cut here ]
  [1.586861] WARNING: CPU: 0 PID: 1 at 
/build/linux-UWDXbt/linux-4.9.0/arch/x86/mm/dump_pagetables.c:225 
note_page+0x6a1/0x880
  [1.589199] x86/mm: Found insecure W+X mapping at address 
c00a/0xc00a
  [1.590657] Modules linked in:
  [1.591305] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 4.9.0-1-generic 
#2-Ubuntu
  [1.592809] Hardware name: OpenStack Foundation OpenStack Nova, BIOS Bochs 
01/01/2011
  [1.593188]  dae89e70 dc3e0b05 dae89eb4 dca47958 dae89ea0 dc07299a 
dca47920 dae89ed4
  [1.593188]  0001 dca47958 00e1 dc068db1 00e1 dae89f34 
8000 
  [1.593188]  dae89ec0 dc072a06 0009  dae89eb4 dca47920 
dae89ed4 76601e21
  [1.593188] Call Trace:
  [1.593188]  [] dump_stack+0x58/0x73
  [1.593188]  [] __warn+0xea/0x110
  [1.593188]  [] ? note_page+0x6a1/0x880
  [1.593188]  [] warn_slowpath_fmt+0x46/0x60
  [1.593188]  [] note_page+0x6a1/0x880
  [1.593188]  [] ptdump_walk_pgd_level_core+0x1f5/0x300
  [1.593188]  [] ptdump_walk_pgd_level_checkwx+0x16/0x20
  [1.593188]  [] mark_rodata_ro+0xfd/0x130
  [1.593188]  [] ? rest_init+0x70/0x70
  [1.593188]  [] kernel_init+0x2c/0x100
  [1.593188]  [] ? schedule_tail+0x11/0x50
  [1.593188]  [] ? rest_init+0x70/0x70
  [1.593188]  [] ret_from_fork+0x1b/0x28
  [1.613361] ---[ end trace d63b34644638754d ]---
  [1.614368] x86/mm: Checked W+X mappings: 

[Kernel-packages] [Bug 1626436] Re: [4.8 regression] boot has become very slow

[Martin Pitt]

ah, just 4 sounds fine indeed. I did test 4.9-rc5 yesterday already (see
comment #57),  just not sure if that includes "the" the two commits.

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

Title:
  [4.8 regression] boot has become very slow

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Yakkety:
  In Progress

Bug description:
  With yakkety's recent update from linux 4.4 to 4.8 booting has become
  a lot slower. It's not one service in particular, but without "quiet"
  and "splash" you can now easily read every single line instead of that
  whole wall of text zipping by. It now takes over 20s instead of ~10
  seconds to boot.

  This is even more dramatic when factoring out the recent boot hang of
  NetworkManager (bug 1622893) and disabling lightdm:

    sudo systemctl mask NetworkManager NetworkManager-wait-online
  lightdm

  then booting with 4.4 takes 1.5s and with 4.8 19.5s (!).

  Some excerps from systemd-analyze blame:

  4.4:
     474ms postfix@-.service
     395ms lxd-containers.service
     305ms networking.service

  4.8:
    4.578s postfix@-.service
    7.300s lxd-containers.service
    6.285s networking.service

  I attach the full outputs of critical-chain and analyze for 4.4 and
  4.8 for reference.

  This is much less noticeable in the running system. There is no
  immediate feeling of sluggishness (although my system is by and large
  idle).

  I compared the time of sbuilding colord under similar circumstances
  (-j4, building on tmpfs, thus no hard disk delays; running with fully
  pre-loaded apt-cacher-ng thus no random network delays), and with 4.4
  it takes 6.5 minutes and with 4.8 it takes 7.5. So that got a bit
  slower, but much less dramatically than during boot, so this is either
  happening when a lot of processes run in parallel, or is perhaps
  related to setting up cgroups.

  One thing I noticed that during sbuild in 4.8 "top" shows ridiculous
  loads (~ 250) under 4.8, while it's around 4 or 5 under 4.4. But that
  doesn't reflect in actual sluggishness, so this might be just an
  unrelated bug.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: linux-image-4.8.0-11-generic 4.8.0-11.12
  ProcVersionSignature: Ubuntu 4.8.0-11.12-generic 4.8.0-rc6
  Uname: Linux 4.8.0-11-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   martin 3049 F...m pulseaudio
   /dev/snd/pcmC0D0p:   martin 3049 F...m pulseaudio
   /dev/snd/controlC0:  martin 3049 F pulseaudio
  Date: Thu Sep 22 09:42:56 2016
  EcryptfsInUse: Yes
  MachineType: LENOVO 2324CTO
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.8.0-11-generic.efi.signed 
root=UUID=f86539b0-3a1b-4372-83b0-acdd029ade68 ro rootflags=subvol=@ 
systemd.debug-shell
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-11-generic N/A
   linux-backports-modules-4.8.0-11-generic  N/A
   linux-firmware1.161
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/09/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G2ET95WW (2.55 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2324CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: 0B98401 Pro
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG2ET95WW(2.55):bd07/09/2013:svnLENOVO:pn2324CTO:pvrThinkPadX230:rvnLENOVO:rn2324CTO:rvr0B98401Pro:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 2324CTO
  dmi.product.version: ThinkPad X230
  dmi.sys.vendor: LENOVO

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1626436] Re: [4.8 regression] boot has become very slow

[Martin Pitt]

> http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.9-rc5/

This still shows unchanged behaviour: slow boot and shutdown, and high
load after boot. So unfortunately it didn't magically fix itself :(

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

Title:
  [4.8 regression] boot has become very slow

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Yakkety:
  In Progress

Bug description:
  With yakkety's recent update from linux 4.4 to 4.8 booting has become
  a lot slower. It's not one service in particular, but without "quiet"
  and "splash" you can now easily read every single line instead of that
  whole wall of text zipping by. It now takes over 20s instead of ~10
  seconds to boot.

  This is even more dramatic when factoring out the recent boot hang of
  NetworkManager (bug 1622893) and disabling lightdm:

    sudo systemctl mask NetworkManager NetworkManager-wait-online
  lightdm

  then booting with 4.4 takes 1.5s and with 4.8 19.5s (!).

  Some excerps from systemd-analyze blame:

  4.4:
     474ms postfix@-.service
     395ms lxd-containers.service
     305ms networking.service

  4.8:
    4.578s postfix@-.service
    7.300s lxd-containers.service
    6.285s networking.service

  I attach the full outputs of critical-chain and analyze for 4.4 and
  4.8 for reference.

  This is much less noticeable in the running system. There is no
  immediate feeling of sluggishness (although my system is by and large
  idle).

  I compared the time of sbuilding colord under similar circumstances
  (-j4, building on tmpfs, thus no hard disk delays; running with fully
  pre-loaded apt-cacher-ng thus no random network delays), and with 4.4
  it takes 6.5 minutes and with 4.8 it takes 7.5. So that got a bit
  slower, but much less dramatically than during boot, so this is either
  happening when a lot of processes run in parallel, or is perhaps
  related to setting up cgroups.

  One thing I noticed that during sbuild in 4.8 "top" shows ridiculous
  loads (~ 250) under 4.8, while it's around 4 or 5 under 4.4. But that
  doesn't reflect in actual sluggishness, so this might be just an
  unrelated bug.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: linux-image-4.8.0-11-generic 4.8.0-11.12
  ProcVersionSignature: Ubuntu 4.8.0-11.12-generic 4.8.0-rc6
  Uname: Linux 4.8.0-11-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   martin 3049 F...m pulseaudio
   /dev/snd/pcmC0D0p:   martin 3049 F...m pulseaudio
   /dev/snd/controlC0:  martin 3049 F pulseaudio
  Date: Thu Sep 22 09:42:56 2016
  EcryptfsInUse: Yes
  MachineType: LENOVO 2324CTO
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.8.0-11-generic.efi.signed 
root=UUID=f86539b0-3a1b-4372-83b0-acdd029ade68 ro rootflags=subvol=@ 
systemd.debug-shell
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-11-generic N/A
   linux-backports-modules-4.8.0-11-generic  N/A
   linux-firmware1.161
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/09/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G2ET95WW (2.55 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2324CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: 0B98401 Pro
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG2ET95WW(2.55):bd07/09/2013:svnLENOVO:pn2324CTO:pvrThinkPadX230:rvnLENOVO:rn2324CTO:rvr0B98401Pro:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 2324CTO
  dmi.product.version: ThinkPad X230
  dmi.sys.vendor: LENOVO

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1626436] Re: [4.8 regression] boot has become very slow

[Martin Pitt]

Is there something which could help to cut down the bisect? I had a
theory in comment 12 about the plethora of cgroup related uevents.

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

Title:
  [4.8 regression] boot has become very slow

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Yakkety:
  In Progress

Bug description:
  With yakkety's recent update from linux 4.4 to 4.8 booting has become
  a lot slower. It's not one service in particular, but without "quiet"
  and "splash" you can now easily read every single line instead of that
  whole wall of text zipping by. It now takes over 20s instead of ~10
  seconds to boot.

  This is even more dramatic when factoring out the recent boot hang of
  NetworkManager (bug 1622893) and disabling lightdm:

    sudo systemctl mask NetworkManager NetworkManager-wait-online
  lightdm

  then booting with 4.4 takes 1.5s and with 4.8 19.5s (!).

  Some excerps from systemd-analyze blame:

  4.4:
     474ms postfix@-.service
     395ms lxd-containers.service
     305ms networking.service

  4.8:
    4.578s postfix@-.service
    7.300s lxd-containers.service
    6.285s networking.service

  I attach the full outputs of critical-chain and analyze for 4.4 and
  4.8 for reference.

  This is much less noticeable in the running system. There is no
  immediate feeling of sluggishness (although my system is by and large
  idle).

  I compared the time of sbuilding colord under similar circumstances
  (-j4, building on tmpfs, thus no hard disk delays; running with fully
  pre-loaded apt-cacher-ng thus no random network delays), and with 4.4
  it takes 6.5 minutes and with 4.8 it takes 7.5. So that got a bit
  slower, but much less dramatically than during boot, so this is either
  happening when a lot of processes run in parallel, or is perhaps
  related to setting up cgroups.

  One thing I noticed that during sbuild in 4.8 "top" shows ridiculous
  loads (~ 250) under 4.8, while it's around 4 or 5 under 4.4. But that
  doesn't reflect in actual sluggishness, so this might be just an
  unrelated bug.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: linux-image-4.8.0-11-generic 4.8.0-11.12
  ProcVersionSignature: Ubuntu 4.8.0-11.12-generic 4.8.0-rc6
  Uname: Linux 4.8.0-11-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   martin 3049 F...m pulseaudio
   /dev/snd/pcmC0D0p:   martin 3049 F...m pulseaudio
   /dev/snd/controlC0:  martin 3049 F pulseaudio
  Date: Thu Sep 22 09:42:56 2016
  EcryptfsInUse: Yes
  MachineType: LENOVO 2324CTO
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.8.0-11-generic.efi.signed 
root=UUID=f86539b0-3a1b-4372-83b0-acdd029ade68 ro rootflags=subvol=@ 
systemd.debug-shell
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-11-generic N/A
   linux-backports-modules-4.8.0-11-generic  N/A
   linux-firmware1.161
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/09/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G2ET95WW (2.55 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2324CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: 0B98401 Pro
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG2ET95WW(2.55):bd07/09/2013:svnLENOVO:pn2324CTO:pvrThinkPadX230:rvnLENOVO:rn2324CTO:rvr0B98401Pro:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 2324CTO
  dmi.product.version: ThinkPad X230
  dmi.sys.vendor: LENOVO

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1626436] Re: [4.8 regression] boot has become very slow

[Martin Pitt]

>
http://kernel.ubuntu.com/~jsalisbury/lp1626436/e257ef55ce51d7ec399193ee85acda8b8759d930

Still GOOD.

Thanks!

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

Title:
  [4.8 regression] boot has become very slow

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Yakkety:
  In Progress

Bug description:
  With yakkety's recent update from linux 4.4 to 4.8 booting has become
  a lot slower. It's not one service in particular, but without "quiet"
  and "splash" you can now easily read every single line instead of that
  whole wall of text zipping by. It now takes over 20s instead of ~10
  seconds to boot.

  This is even more dramatic when factoring out the recent boot hang of
  NetworkManager (bug 1622893) and disabling lightdm:

    sudo systemctl mask NetworkManager NetworkManager-wait-online
  lightdm

  then booting with 4.4 takes 1.5s and with 4.8 19.5s (!).

  Some excerps from systemd-analyze blame:

  4.4:
     474ms postfix@-.service
     395ms lxd-containers.service
     305ms networking.service

  4.8:
    4.578s postfix@-.service
    7.300s lxd-containers.service
    6.285s networking.service

  I attach the full outputs of critical-chain and analyze for 4.4 and
  4.8 for reference.

  This is much less noticeable in the running system. There is no
  immediate feeling of sluggishness (although my system is by and large
  idle).

  I compared the time of sbuilding colord under similar circumstances
  (-j4, building on tmpfs, thus no hard disk delays; running with fully
  pre-loaded apt-cacher-ng thus no random network delays), and with 4.4
  it takes 6.5 minutes and with 4.8 it takes 7.5. So that got a bit
  slower, but much less dramatically than during boot, so this is either
  happening when a lot of processes run in parallel, or is perhaps
  related to setting up cgroups.

  One thing I noticed that during sbuild in 4.8 "top" shows ridiculous
  loads (~ 250) under 4.8, while it's around 4 or 5 under 4.4. But that
  doesn't reflect in actual sluggishness, so this might be just an
  unrelated bug.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: linux-image-4.8.0-11-generic 4.8.0-11.12
  ProcVersionSignature: Ubuntu 4.8.0-11.12-generic 4.8.0-rc6
  Uname: Linux 4.8.0-11-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   martin 3049 F...m pulseaudio
   /dev/snd/pcmC0D0p:   martin 3049 F...m pulseaudio
   /dev/snd/controlC0:  martin 3049 F pulseaudio
  Date: Thu Sep 22 09:42:56 2016
  EcryptfsInUse: Yes
  MachineType: LENOVO 2324CTO
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.8.0-11-generic.efi.signed 
root=UUID=f86539b0-3a1b-4372-83b0-acdd029ade68 ro rootflags=subvol=@ 
systemd.debug-shell
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-11-generic N/A
   linux-backports-modules-4.8.0-11-generic  N/A
   linux-firmware1.161
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/09/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G2ET95WW (2.55 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2324CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: 0B98401 Pro
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG2ET95WW(2.55):bd07/09/2013:svnLENOVO:pn2324CTO:pvrThinkPadX230:rvnLENOVO:rn2324CTO:rvr0B98401Pro:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 2324CTO
  dmi.product.version: ThinkPad X230
  dmi.sys.vendor: LENOVO

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1626436] Re: [4.8 regression] boot has become very slow

[Martin Pitt]

>
http://kernel.ubuntu.com/~jsalisbury/lp1626436/58f8b094e96f12e899bf767fc658c165908065d4

GOOD

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

Title:
  [4.8 regression] boot has become very slow

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Yakkety:
  In Progress

Bug description:
  With yakkety's recent update from linux 4.4 to 4.8 booting has become
  a lot slower. It's not one service in particular, but without "quiet"
  and "splash" you can now easily read every single line instead of that
  whole wall of text zipping by. It now takes over 20s instead of ~10
  seconds to boot.

  This is even more dramatic when factoring out the recent boot hang of
  NetworkManager (bug 1622893) and disabling lightdm:

    sudo systemctl mask NetworkManager NetworkManager-wait-online
  lightdm

  then booting with 4.4 takes 1.5s and with 4.8 19.5s (!).

  Some excerps from systemd-analyze blame:

  4.4:
     474ms postfix@-.service
     395ms lxd-containers.service
     305ms networking.service

  4.8:
    4.578s postfix@-.service
    7.300s lxd-containers.service
    6.285s networking.service

  I attach the full outputs of critical-chain and analyze for 4.4 and
  4.8 for reference.

  This is much less noticeable in the running system. There is no
  immediate feeling of sluggishness (although my system is by and large
  idle).

  I compared the time of sbuilding colord under similar circumstances
  (-j4, building on tmpfs, thus no hard disk delays; running with fully
  pre-loaded apt-cacher-ng thus no random network delays), and with 4.4
  it takes 6.5 minutes and with 4.8 it takes 7.5. So that got a bit
  slower, but much less dramatically than during boot, so this is either
  happening when a lot of processes run in parallel, or is perhaps
  related to setting up cgroups.

  One thing I noticed that during sbuild in 4.8 "top" shows ridiculous
  loads (~ 250) under 4.8, while it's around 4 or 5 under 4.4. But that
  doesn't reflect in actual sluggishness, so this might be just an
  unrelated bug.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: linux-image-4.8.0-11-generic 4.8.0-11.12
  ProcVersionSignature: Ubuntu 4.8.0-11.12-generic 4.8.0-rc6
  Uname: Linux 4.8.0-11-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   martin 3049 F...m pulseaudio
   /dev/snd/pcmC0D0p:   martin 3049 F...m pulseaudio
   /dev/snd/controlC0:  martin 3049 F pulseaudio
  Date: Thu Sep 22 09:42:56 2016
  EcryptfsInUse: Yes
  MachineType: LENOVO 2324CTO
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.8.0-11-generic.efi.signed 
root=UUID=f86539b0-3a1b-4372-83b0-acdd029ade68 ro rootflags=subvol=@ 
systemd.debug-shell
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-11-generic N/A
   linux-backports-modules-4.8.0-11-generic  N/A
   linux-firmware1.161
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/09/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G2ET95WW (2.55 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2324CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: 0B98401 Pro
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG2ET95WW(2.55):bd07/09/2013:svnLENOVO:pn2324CTO:pvrThinkPadX230:rvnLENOVO:rn2324CTO:rvr0B98401Pro:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 2324CTO
  dmi.product.version: ThinkPad X230
  dmi.sys.vendor: LENOVO

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1626436] Re: [4.8 regression] boot has become very slow

[Martin Pitt]

>
http://kernel.ubuntu.com/~jsalisbury/lp1626436/1acd010152138644f63d743e165161edc780fc32

GOOD

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

Title:
  [4.8 regression] boot has become very slow

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Yakkety:
  In Progress

Bug description:
  With yakkety's recent update from linux 4.4 to 4.8 booting has become
  a lot slower. It's not one service in particular, but without "quiet"
  and "splash" you can now easily read every single line instead of that
  whole wall of text zipping by. It now takes over 20s instead of ~10
  seconds to boot.

  This is even more dramatic when factoring out the recent boot hang of
  NetworkManager (bug 1622893) and disabling lightdm:

    sudo systemctl mask NetworkManager NetworkManager-wait-online
  lightdm

  then booting with 4.4 takes 1.5s and with 4.8 19.5s (!).

  Some excerps from systemd-analyze blame:

  4.4:
     474ms postfix@-.service
     395ms lxd-containers.service
     305ms networking.service

  4.8:
    4.578s postfix@-.service
    7.300s lxd-containers.service
    6.285s networking.service

  I attach the full outputs of critical-chain and analyze for 4.4 and
  4.8 for reference.

  This is much less noticeable in the running system. There is no
  immediate feeling of sluggishness (although my system is by and large
  idle).

  I compared the time of sbuilding colord under similar circumstances
  (-j4, building on tmpfs, thus no hard disk delays; running with fully
  pre-loaded apt-cacher-ng thus no random network delays), and with 4.4
  it takes 6.5 minutes and with 4.8 it takes 7.5. So that got a bit
  slower, but much less dramatically than during boot, so this is either
  happening when a lot of processes run in parallel, or is perhaps
  related to setting up cgroups.

  One thing I noticed that during sbuild in 4.8 "top" shows ridiculous
  loads (~ 250) under 4.8, while it's around 4 or 5 under 4.4. But that
  doesn't reflect in actual sluggishness, so this might be just an
  unrelated bug.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: linux-image-4.8.0-11-generic 4.8.0-11.12
  ProcVersionSignature: Ubuntu 4.8.0-11.12-generic 4.8.0-rc6
  Uname: Linux 4.8.0-11-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   martin 3049 F...m pulseaudio
   /dev/snd/pcmC0D0p:   martin 3049 F...m pulseaudio
   /dev/snd/controlC0:  martin 3049 F pulseaudio
  Date: Thu Sep 22 09:42:56 2016
  EcryptfsInUse: Yes
  MachineType: LENOVO 2324CTO
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.8.0-11-generic.efi.signed 
root=UUID=f86539b0-3a1b-4372-83b0-acdd029ade68 ro rootflags=subvol=@ 
systemd.debug-shell
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-11-generic N/A
   linux-backports-modules-4.8.0-11-generic  N/A
   linux-firmware1.161
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/09/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G2ET95WW (2.55 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2324CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: 0B98401 Pro
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG2ET95WW(2.55):bd07/09/2013:svnLENOVO:pn2324CTO:pvrThinkPadX230:rvnLENOVO:rn2324CTO:rvr0B98401Pro:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 2324CTO
  dmi.product.version: ThinkPad X230
  dmi.sys.vendor: LENOVO

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1626436] Re: [4.8 regression] boot has become very slow

[Martin Pitt]

>
http://kernel.ubuntu.com/~jsalisbury/lp1626436/a0d3c7c5c07cfbe00ab89438ddf82482f5a99422

Still GOOD.

I'm becoming a bit nervous, but I just re-tested 4.7rc1 again and it's
still bad.

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

Title:
  [4.8 regression] boot has become very slow

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Yakkety:
  In Progress

Bug description:
  With yakkety's recent update from linux 4.4 to 4.8 booting has become
  a lot slower. It's not one service in particular, but without "quiet"
  and "splash" you can now easily read every single line instead of that
  whole wall of text zipping by. It now takes over 20s instead of ~10
  seconds to boot.

  This is even more dramatic when factoring out the recent boot hang of
  NetworkManager (bug 1622893) and disabling lightdm:

    sudo systemctl mask NetworkManager NetworkManager-wait-online
  lightdm

  then booting with 4.4 takes 1.5s and with 4.8 19.5s (!).

  Some excerps from systemd-analyze blame:

  4.4:
     474ms postfix@-.service
     395ms lxd-containers.service
     305ms networking.service

  4.8:
    4.578s postfix@-.service
    7.300s lxd-containers.service
    6.285s networking.service

  I attach the full outputs of critical-chain and analyze for 4.4 and
  4.8 for reference.

  This is much less noticeable in the running system. There is no
  immediate feeling of sluggishness (although my system is by and large
  idle).

  I compared the time of sbuilding colord under similar circumstances
  (-j4, building on tmpfs, thus no hard disk delays; running with fully
  pre-loaded apt-cacher-ng thus no random network delays), and with 4.4
  it takes 6.5 minutes and with 4.8 it takes 7.5. So that got a bit
  slower, but much less dramatically than during boot, so this is either
  happening when a lot of processes run in parallel, or is perhaps
  related to setting up cgroups.

  One thing I noticed that during sbuild in 4.8 "top" shows ridiculous
  loads (~ 250) under 4.8, while it's around 4 or 5 under 4.4. But that
  doesn't reflect in actual sluggishness, so this might be just an
  unrelated bug.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: linux-image-4.8.0-11-generic 4.8.0-11.12
  ProcVersionSignature: Ubuntu 4.8.0-11.12-generic 4.8.0-rc6
  Uname: Linux 4.8.0-11-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   martin 3049 F...m pulseaudio
   /dev/snd/pcmC0D0p:   martin 3049 F...m pulseaudio
   /dev/snd/controlC0:  martin 3049 F pulseaudio
  Date: Thu Sep 22 09:42:56 2016
  EcryptfsInUse: Yes
  MachineType: LENOVO 2324CTO
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.8.0-11-generic.efi.signed 
root=UUID=f86539b0-3a1b-4372-83b0-acdd029ade68 ro rootflags=subvol=@ 
systemd.debug-shell
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-11-generic N/A
   linux-backports-modules-4.8.0-11-generic  N/A
   linux-firmware1.161
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/09/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G2ET95WW (2.55 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2324CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: 0B98401 Pro
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG2ET95WW(2.55):bd07/09/2013:svnLENOVO:pn2324CTO:pvrThinkPadX230:rvnLENOVO:rn2324CTO:rvr0B98401Pro:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 2324CTO
  dmi.product.version: ThinkPad X230
  dmi.sys.vendor: LENOVO

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1531768] Re: [arm64] lockups some time after booting

[Martin Pitt]

I propose to close this. This is clearly fixed with 4.4 on the host, and
rolling that out is covered by bug 1602577.

It can be closed for auto-package-testing either way as our arm64 nova
compute nodes now run 4.4.23.

** Changed in: linux (Ubuntu)
   Status: Confirmed => Fix Released

** Changed in: auto-package-testing
   Status: Triaged => Fix Released

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

Title:
  [arm64] lockups some time after booting

Status in Auto Package Testing:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released

Bug description:
  I created an 8 CPU arm64 instance on Canonical's Scalingstack (which I
  want to use for armhf autopkgtesting in LXD). I started with wily as
  that has lxd available (it's not yet available in trusty nor the PPA
  for arm64).

  However, pretty much any LXD task that I do (I haven't tried much
  else) on this machine takes unbearably long. A simple "lxc profile set
  default raw.lxc lxc.seccomp=" or "lxc list" takes several minutes.

  I see tons of

  [ 1020.971955] rcu_sched kthread starved for 6000 jiffies! g1095 c1094 f0x0
  [ 1121.166926] INFO: task fsnotify_mark:69 blocked for more than 120 seconds.

  in dmesg (the attached apport info has the complete dmesg).

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: linux-image-4.2.0-22-generic 4.2.0-22.27
  ProcVersionSignature: User Name 4.2.0-22.27-generic 4.2.6
  Uname: Linux 4.2.0-22-generic aarch64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jan  7 09:18 seq
   crw-rw 1 root audio 116, 33 Jan  7 09:18 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: arm64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  Date: Thu Jan  7 09:24:01 2016
  IwConfig:
   eth0  no wireless extensions.

   lono wireless extensions.

   lxcbr0no wireless extensions.
  Lspci:
   00:00.0 Host bridge [0600]: Red Hat, Inc. Device [1b36:0008]
    Subsystem: Red Hat, Inc Device [1af4:1100]
    Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
    Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB:

  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-22-generic 
root=LABEL=cloudimg-rootfs earlyprintk
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-22-generic N/A
   linux-backports-modules-4.2.0-22-generic  N/A
   linux-firmware1.149.3
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/auto-package-testing/+bug/1531768/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1626436] Re: [4.8 regression] boot has become very slow

[Martin Pitt]

>
http://kernel.ubuntu.com/~jsalisbury/lp1626436/07b75260ebc2c789724c594d7eaf0194fa47b3be

GOOD

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

Title:
  [4.8 regression] boot has become very slow

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Yakkety:
  In Progress

Bug description:
  With yakkety's recent update from linux 4.4 to 4.8 booting has become
  a lot slower. It's not one service in particular, but without "quiet"
  and "splash" you can now easily read every single line instead of that
  whole wall of text zipping by. It now takes over 20s instead of ~10
  seconds to boot.

  This is even more dramatic when factoring out the recent boot hang of
  NetworkManager (bug 1622893) and disabling lightdm:

    sudo systemctl mask NetworkManager NetworkManager-wait-online
  lightdm

  then booting with 4.4 takes 1.5s and with 4.8 19.5s (!).

  Some excerps from systemd-analyze blame:

  4.4:
     474ms postfix@-.service
     395ms lxd-containers.service
     305ms networking.service

  4.8:
    4.578s postfix@-.service
    7.300s lxd-containers.service
    6.285s networking.service

  I attach the full outputs of critical-chain and analyze for 4.4 and
  4.8 for reference.

  This is much less noticeable in the running system. There is no
  immediate feeling of sluggishness (although my system is by and large
  idle).

  I compared the time of sbuilding colord under similar circumstances
  (-j4, building on tmpfs, thus no hard disk delays; running with fully
  pre-loaded apt-cacher-ng thus no random network delays), and with 4.4
  it takes 6.5 minutes and with 4.8 it takes 7.5. So that got a bit
  slower, but much less dramatically than during boot, so this is either
  happening when a lot of processes run in parallel, or is perhaps
  related to setting up cgroups.

  One thing I noticed that during sbuild in 4.8 "top" shows ridiculous
  loads (~ 250) under 4.8, while it's around 4 or 5 under 4.4. But that
  doesn't reflect in actual sluggishness, so this might be just an
  unrelated bug.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: linux-image-4.8.0-11-generic 4.8.0-11.12
  ProcVersionSignature: Ubuntu 4.8.0-11.12-generic 4.8.0-rc6
  Uname: Linux 4.8.0-11-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   martin 3049 F...m pulseaudio
   /dev/snd/pcmC0D0p:   martin 3049 F...m pulseaudio
   /dev/snd/controlC0:  martin 3049 F pulseaudio
  Date: Thu Sep 22 09:42:56 2016
  EcryptfsInUse: Yes
  MachineType: LENOVO 2324CTO
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.8.0-11-generic.efi.signed 
root=UUID=f86539b0-3a1b-4372-83b0-acdd029ade68 ro rootflags=subvol=@ 
systemd.debug-shell
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-11-generic N/A
   linux-backports-modules-4.8.0-11-generic  N/A
   linux-firmware1.161
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/09/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G2ET95WW (2.55 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2324CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: 0B98401 Pro
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG2ET95WW(2.55):bd07/09/2013:svnLENOVO:pn2324CTO:pvrThinkPadX230:rvnLENOVO:rn2324CTO:rvr0B98401Pro:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 2324CTO
  dmi.product.version: ThinkPad X230
  dmi.sys.vendor: LENOVO

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1626436] Re: [4.8 regression] boot has become very slow

[Martin Pitt]

> The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1626436/0efacbbaee1e94e9942da0912f5b46ffd45a74bd

This is a GOOD kernel.

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

Title:
  [4.8 regression] boot has become very slow

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Yakkety:
  In Progress

Bug description:
  With yakkety's recent update from linux 4.4 to 4.8 booting has become
  a lot slower. It's not one service in particular, but without "quiet"
  and "splash" you can now easily read every single line instead of that
  whole wall of text zipping by. It now takes over 20s instead of ~10
  seconds to boot.

  This is even more dramatic when factoring out the recent boot hang of
  NetworkManager (bug 1622893) and disabling lightdm:

    sudo systemctl mask NetworkManager NetworkManager-wait-online
  lightdm

  then booting with 4.4 takes 1.5s and with 4.8 19.5s (!).

  Some excerps from systemd-analyze blame:

  4.4:
     474ms postfix@-.service
     395ms lxd-containers.service
     305ms networking.service

  4.8:
    4.578s postfix@-.service
    7.300s lxd-containers.service
    6.285s networking.service

  I attach the full outputs of critical-chain and analyze for 4.4 and
  4.8 for reference.

  This is much less noticeable in the running system. There is no
  immediate feeling of sluggishness (although my system is by and large
  idle).

  I compared the time of sbuilding colord under similar circumstances
  (-j4, building on tmpfs, thus no hard disk delays; running with fully
  pre-loaded apt-cacher-ng thus no random network delays), and with 4.4
  it takes 6.5 minutes and with 4.8 it takes 7.5. So that got a bit
  slower, but much less dramatically than during boot, so this is either
  happening when a lot of processes run in parallel, or is perhaps
  related to setting up cgroups.

  One thing I noticed that during sbuild in 4.8 "top" shows ridiculous
  loads (~ 250) under 4.8, while it's around 4 or 5 under 4.4. But that
  doesn't reflect in actual sluggishness, so this might be just an
  unrelated bug.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: linux-image-4.8.0-11-generic 4.8.0-11.12
  ProcVersionSignature: Ubuntu 4.8.0-11.12-generic 4.8.0-rc6
  Uname: Linux 4.8.0-11-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   martin 3049 F...m pulseaudio
   /dev/snd/pcmC0D0p:   martin 3049 F...m pulseaudio
   /dev/snd/controlC0:  martin 3049 F pulseaudio
  Date: Thu Sep 22 09:42:56 2016
  EcryptfsInUse: Yes
  MachineType: LENOVO 2324CTO
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.8.0-11-generic.efi.signed 
root=UUID=f86539b0-3a1b-4372-83b0-acdd029ade68 ro rootflags=subvol=@ 
systemd.debug-shell
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-11-generic N/A
   linux-backports-modules-4.8.0-11-generic  N/A
   linux-firmware1.161
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/09/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G2ET95WW (2.55 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2324CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: 0B98401 Pro
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG2ET95WW(2.55):bd07/09/2013:svnLENOVO:pn2324CTO:pvrThinkPadX230:rvnLENOVO:rn2324CTO:rvr0B98401Pro:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 2324CTO
  dmi.product.version: ThinkPad X230
  dmi.sys.vendor: LENOVO

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1626436] Re: [4.8 regression] boot has become very slow

[Martin Pitt]

>
http://kernel.ubuntu.com/~jsalisbury/lp1626436/4a5219edcdae52bfb5eea0dfc2a7bd575961dad7

I do see the files now. Sorry for the delay, travel/sprint and all.

This is a GOOD kernel.

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

Title:
  [4.8 regression] boot has become very slow

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Yakkety:
  In Progress

Bug description:
  With yakkety's recent update from linux 4.4 to 4.8 booting has become
  a lot slower. It's not one service in particular, but without "quiet"
  and "splash" you can now easily read every single line instead of that
  whole wall of text zipping by. It now takes over 20s instead of ~10
  seconds to boot.

  This is even more dramatic when factoring out the recent boot hang of
  NetworkManager (bug 1622893) and disabling lightdm:

    sudo systemctl mask NetworkManager NetworkManager-wait-online
  lightdm

  then booting with 4.4 takes 1.5s and with 4.8 19.5s (!).

  Some excerps from systemd-analyze blame:

  4.4:
     474ms postfix@-.service
     395ms lxd-containers.service
     305ms networking.service

  4.8:
    4.578s postfix@-.service
    7.300s lxd-containers.service
    6.285s networking.service

  I attach the full outputs of critical-chain and analyze for 4.4 and
  4.8 for reference.

  This is much less noticeable in the running system. There is no
  immediate feeling of sluggishness (although my system is by and large
  idle).

  I compared the time of sbuilding colord under similar circumstances
  (-j4, building on tmpfs, thus no hard disk delays; running with fully
  pre-loaded apt-cacher-ng thus no random network delays), and with 4.4
  it takes 6.5 minutes and with 4.8 it takes 7.5. So that got a bit
  slower, but much less dramatically than during boot, so this is either
  happening when a lot of processes run in parallel, or is perhaps
  related to setting up cgroups.

  One thing I noticed that during sbuild in 4.8 "top" shows ridiculous
  loads (~ 250) under 4.8, while it's around 4 or 5 under 4.4. But that
  doesn't reflect in actual sluggishness, so this might be just an
  unrelated bug.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: linux-image-4.8.0-11-generic 4.8.0-11.12
  ProcVersionSignature: Ubuntu 4.8.0-11.12-generic 4.8.0-rc6
  Uname: Linux 4.8.0-11-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   martin 3049 F...m pulseaudio
   /dev/snd/pcmC0D0p:   martin 3049 F...m pulseaudio
   /dev/snd/controlC0:  martin 3049 F pulseaudio
  Date: Thu Sep 22 09:42:56 2016
  EcryptfsInUse: Yes
  MachineType: LENOVO 2324CTO
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.8.0-11-generic.efi.signed 
root=UUID=f86539b0-3a1b-4372-83b0-acdd029ade68 ro rootflags=subvol=@ 
systemd.debug-shell
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-11-generic N/A
   linux-backports-modules-4.8.0-11-generic  N/A
   linux-firmware1.161
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/09/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G2ET95WW (2.55 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2324CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: 0B98401 Pro
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG2ET95WW(2.55):bd07/09/2013:svnLENOVO:pn2324CTO:pvrThinkPadX230:rvnLENOVO:rn2324CTO:rvr0B98401Pro:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 2324CTO
  dmi.product.version: ThinkPad X230
  dmi.sys.vendor: LENOVO

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1634132] Update Released

[Martin Pitt]

The verification of the Stable Release Update for makedumpfile has
completed successfully and the package has now been released to
-updates.  Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to makedumpfile in Ubuntu.
https://bugs.launchpad.net/bugs/1634132

Title:
  using hugepages/hugepagesz causes kexec'd kernel to OOM

Status in makedumpfile package in Ubuntu:
  Fix Released
Status in makedumpfile source package in Trusty:
  Fix Released
Status in makedumpfile source package in Xenial:
  Fix Released
Status in makedumpfile source package in Yakkety:
  Fix Released
Status in makedumpfile source package in Zesty:
  Fix Released

Bug description:
  [Impact]
  Users of kdump won't be able to dump if their system uses 
hugepages/hugepagesz on the cmdline.

  [Test Case]
  1) Install crashdump
  2) Boot machine with hugepages= or hugepagesz= set to a significant amount of 
memory
  3) Try to crash with 'echo 'c' | sudo tee /proc/sysrq-trigger'

  [Regression Potential]
  If users really want to have hugepages/hugepagesz on the kexec'd kernel for 
kdump they can add this via KDUMP_CMDLINE_APPEND in /etc/default/kdump-tools.
  This patch should also potentially go upstream.

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1634132] Update Released

[Martin Pitt]

The verification of the Stable Release Update for makedumpfile has
completed successfully and the package has now been released to
-updates.  Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to makedumpfile in Ubuntu.
https://bugs.launchpad.net/bugs/1634132

Title:
  using hugepages/hugepagesz causes kexec'd kernel to OOM

Status in makedumpfile package in Ubuntu:
  Fix Released
Status in makedumpfile source package in Trusty:
  Fix Released
Status in makedumpfile source package in Xenial:
  Fix Released
Status in makedumpfile source package in Yakkety:
  Fix Released
Status in makedumpfile source package in Zesty:
  Fix Released

Bug description:
  [Impact]
  Users of kdump won't be able to dump if their system uses 
hugepages/hugepagesz on the cmdline.

  [Test Case]
  1) Install crashdump
  2) Boot machine with hugepages= or hugepagesz= set to a significant amount of 
memory
  3) Try to crash with 'echo 'c' | sudo tee /proc/sysrq-trigger'

  [Regression Potential]
  If users really want to have hugepages/hugepagesz on the kexec'd kernel for 
kdump they can add this via KDUMP_CMDLINE_APPEND in /etc/default/kdump-tools.
  This patch should also potentially go upstream.

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1634132] Update Released

[Martin Pitt]

The verification of the Stable Release Update for makedumpfile has
completed successfully and the package has now been released to
-updates.  Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to makedumpfile in Ubuntu.
https://bugs.launchpad.net/bugs/1634132

Title:
  using hugepages/hugepagesz causes kexec'd kernel to OOM

Status in makedumpfile package in Ubuntu:
  Fix Released
Status in makedumpfile source package in Trusty:
  Fix Released
Status in makedumpfile source package in Xenial:
  Fix Released
Status in makedumpfile source package in Yakkety:
  Fix Released
Status in makedumpfile source package in Zesty:
  Fix Released

Bug description:
  [Impact]
  Users of kdump won't be able to dump if their system uses 
hugepages/hugepagesz on the cmdline.

  [Test Case]
  1) Install crashdump
  2) Boot machine with hugepages= or hugepagesz= set to a significant amount of 
memory
  3) Try to crash with 'echo 'c' | sudo tee /proc/sysrq-trigger'

  [Regression Potential]
  If users really want to have hugepages/hugepagesz on the kexec'd kernel for 
kdump they can add this via KDUMP_CMDLINE_APPEND in /etc/default/kdump-tools.
  This patch should also potentially go upstream.

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1626436] Re: [4.8 regression] boot has become very slow

[Martin Pitt]

>
http://kernel.ubuntu.com/~jsalisbury/lp1626436/4a5219edcdae52bfb5eea0dfc2a7bd575961dad7

this is empty

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

Title:
  [4.8 regression] boot has become very slow

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Yakkety:
  In Progress

Bug description:
  With yakkety's recent update from linux 4.4 to 4.8 booting has become
  a lot slower. It's not one service in particular, but without "quiet"
  and "splash" you can now easily read every single line instead of that
  whole wall of text zipping by. It now takes over 20s instead of ~10
  seconds to boot.

  This is even more dramatic when factoring out the recent boot hang of
  NetworkManager (bug 1622893) and disabling lightdm:

    sudo systemctl mask NetworkManager NetworkManager-wait-online
  lightdm

  then booting with 4.4 takes 1.5s and with 4.8 19.5s (!).

  Some excerps from systemd-analyze blame:

  4.4:
     474ms postfix@-.service
     395ms lxd-containers.service
     305ms networking.service

  4.8:
    4.578s postfix@-.service
    7.300s lxd-containers.service
    6.285s networking.service

  I attach the full outputs of critical-chain and analyze for 4.4 and
  4.8 for reference.

  This is much less noticeable in the running system. There is no
  immediate feeling of sluggishness (although my system is by and large
  idle).

  I compared the time of sbuilding colord under similar circumstances
  (-j4, building on tmpfs, thus no hard disk delays; running with fully
  pre-loaded apt-cacher-ng thus no random network delays), and with 4.4
  it takes 6.5 minutes and with 4.8 it takes 7.5. So that got a bit
  slower, but much less dramatically than during boot, so this is either
  happening when a lot of processes run in parallel, or is perhaps
  related to setting up cgroups.

  One thing I noticed that during sbuild in 4.8 "top" shows ridiculous
  loads (~ 250) under 4.8, while it's around 4 or 5 under 4.4. But that
  doesn't reflect in actual sluggishness, so this might be just an
  unrelated bug.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: linux-image-4.8.0-11-generic 4.8.0-11.12
  ProcVersionSignature: Ubuntu 4.8.0-11.12-generic 4.8.0-rc6
  Uname: Linux 4.8.0-11-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   martin 3049 F...m pulseaudio
   /dev/snd/pcmC0D0p:   martin 3049 F...m pulseaudio
   /dev/snd/controlC0:  martin 3049 F pulseaudio
  Date: Thu Sep 22 09:42:56 2016
  EcryptfsInUse: Yes
  MachineType: LENOVO 2324CTO
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.8.0-11-generic.efi.signed 
root=UUID=f86539b0-3a1b-4372-83b0-acdd029ade68 ro rootflags=subvol=@ 
systemd.debug-shell
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-11-generic N/A
   linux-backports-modules-4.8.0-11-generic  N/A
   linux-firmware1.161
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/09/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G2ET95WW (2.55 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2324CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: 0B98401 Pro
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG2ET95WW(2.55):bd07/09/2013:svnLENOVO:pn2324CTO:pvrThinkPadX230:rvnLENOVO:rn2324CTO:rvr0B98401Pro:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 2324CTO
  dmi.product.version: ThinkPad X230
  dmi.sys.vendor: LENOVO

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1626436] Re: [4.8 regression] boot has become very slow

[Martin Pitt]

> I built the another test kernel, up to the same commit:
a7fd20d1c476af4563e66865213474a2f9f473a4

This is GOOD.

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

Title:
  [4.8 regression] boot has become very slow

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Yakkety:
  In Progress

Bug description:
  With yakkety's recent update from linux 4.4 to 4.8 booting has become
  a lot slower. It's not one service in particular, but without "quiet"
  and "splash" you can now easily read every single line instead of that
  whole wall of text zipping by. It now takes over 20s instead of ~10
  seconds to boot.

  This is even more dramatic when factoring out the recent boot hang of
  NetworkManager (bug 1622893) and disabling lightdm:

    sudo systemctl mask NetworkManager NetworkManager-wait-online
  lightdm

  then booting with 4.4 takes 1.5s and with 4.8 19.5s (!).

  Some excerps from systemd-analyze blame:

  4.4:
     474ms postfix@-.service
     395ms lxd-containers.service
     305ms networking.service

  4.8:
    4.578s postfix@-.service
    7.300s lxd-containers.service
    6.285s networking.service

  I attach the full outputs of critical-chain and analyze for 4.4 and
  4.8 for reference.

  This is much less noticeable in the running system. There is no
  immediate feeling of sluggishness (although my system is by and large
  idle).

  I compared the time of sbuilding colord under similar circumstances
  (-j4, building on tmpfs, thus no hard disk delays; running with fully
  pre-loaded apt-cacher-ng thus no random network delays), and with 4.4
  it takes 6.5 minutes and with 4.8 it takes 7.5. So that got a bit
  slower, but much less dramatically than during boot, so this is either
  happening when a lot of processes run in parallel, or is perhaps
  related to setting up cgroups.

  One thing I noticed that during sbuild in 4.8 "top" shows ridiculous
  loads (~ 250) under 4.8, while it's around 4 or 5 under 4.4. But that
  doesn't reflect in actual sluggishness, so this might be just an
  unrelated bug.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: linux-image-4.8.0-11-generic 4.8.0-11.12
  ProcVersionSignature: Ubuntu 4.8.0-11.12-generic 4.8.0-rc6
  Uname: Linux 4.8.0-11-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   martin 3049 F...m pulseaudio
   /dev/snd/pcmC0D0p:   martin 3049 F...m pulseaudio
   /dev/snd/controlC0:  martin 3049 F pulseaudio
  Date: Thu Sep 22 09:42:56 2016
  EcryptfsInUse: Yes
  MachineType: LENOVO 2324CTO
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.8.0-11-generic.efi.signed 
root=UUID=f86539b0-3a1b-4372-83b0-acdd029ade68 ro rootflags=subvol=@ 
systemd.debug-shell
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-11-generic N/A
   linux-backports-modules-4.8.0-11-generic  N/A
   linux-firmware1.161
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/09/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G2ET95WW (2.55 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2324CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: 0B98401 Pro
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG2ET95WW(2.55):bd07/09/2013:svnLENOVO:pn2324CTO:pvrThinkPadX230:rvnLENOVO:rn2324CTO:rvr0B98401Pro:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 2324CTO
  dmi.product.version: ThinkPad X230
  dmi.sys.vendor: LENOVO

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1626436] Re: [4.8 regression] boot has become very slow

[Martin Pitt]

> In the meantime, it might be worthwhile to test v4.9-rc2. It's available from:
> http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.9-rc2/

Still slow boot/high load, i. e. BAD.

> I built the another test kernel, up to the same commit:
> 7afd16f882887c9adc69cd1794f5e5723217

That's GOOD.

Thanks!

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

Title:
  [4.8 regression] boot has become very slow

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Yakkety:
  In Progress

Bug description:
  With yakkety's recent update from linux 4.4 to 4.8 booting has become
  a lot slower. It's not one service in particular, but without "quiet"
  and "splash" you can now easily read every single line instead of that
  whole wall of text zipping by. It now takes over 20s instead of ~10
  seconds to boot.

  This is even more dramatic when factoring out the recent boot hang of
  NetworkManager (bug 1622893) and disabling lightdm:

    sudo systemctl mask NetworkManager NetworkManager-wait-online
  lightdm

  then booting with 4.4 takes 1.5s and with 4.8 19.5s (!).

  Some excerps from systemd-analyze blame:

  4.4:
     474ms postfix@-.service
     395ms lxd-containers.service
     305ms networking.service

  4.8:
    4.578s postfix@-.service
    7.300s lxd-containers.service
    6.285s networking.service

  I attach the full outputs of critical-chain and analyze for 4.4 and
  4.8 for reference.

  This is much less noticeable in the running system. There is no
  immediate feeling of sluggishness (although my system is by and large
  idle).

  I compared the time of sbuilding colord under similar circumstances
  (-j4, building on tmpfs, thus no hard disk delays; running with fully
  pre-loaded apt-cacher-ng thus no random network delays), and with 4.4
  it takes 6.5 minutes and with 4.8 it takes 7.5. So that got a bit
  slower, but much less dramatically than during boot, so this is either
  happening when a lot of processes run in parallel, or is perhaps
  related to setting up cgroups.

  One thing I noticed that during sbuild in 4.8 "top" shows ridiculous
  loads (~ 250) under 4.8, while it's around 4 or 5 under 4.4. But that
  doesn't reflect in actual sluggishness, so this might be just an
  unrelated bug.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: linux-image-4.8.0-11-generic 4.8.0-11.12
  ProcVersionSignature: Ubuntu 4.8.0-11.12-generic 4.8.0-rc6
  Uname: Linux 4.8.0-11-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   martin 3049 F...m pulseaudio
   /dev/snd/pcmC0D0p:   martin 3049 F...m pulseaudio
   /dev/snd/controlC0:  martin 3049 F pulseaudio
  Date: Thu Sep 22 09:42:56 2016
  EcryptfsInUse: Yes
  MachineType: LENOVO 2324CTO
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.8.0-11-generic.efi.signed 
root=UUID=f86539b0-3a1b-4372-83b0-acdd029ade68 ro rootflags=subvol=@ 
systemd.debug-shell
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-11-generic N/A
   linux-backports-modules-4.8.0-11-generic  N/A
   linux-firmware1.161
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/09/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G2ET95WW (2.55 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2324CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: 0B98401 Pro
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG2ET95WW(2.55):bd07/09/2013:svnLENOVO:pn2324CTO:pvrThinkPadX230:rvnLENOVO:rn2324CTO:rvr0B98401Pro:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 2324CTO
  dmi.product.version: ThinkPad X230
  dmi.sys.vendor: LENOVO

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1626436] Re: [4.8 regression] boot has become very slow

[Martin Pitt]

> I built the first test kernel, up to the following commit:
> 7afd16f882887c9adc69cd1794f5e5723217

Like Florian, the result isn't unambiguous. It for sure boots much
faster than 4.7/4.8 (~ 3s kernel + 5s userspace), but still much slower
than 4.4. But this could be attributed to the #1 issue above. So I
*think* this kernel is still "good" (but not quite as clearly as for
Florian).

If it isn't too much trouble, would it be possible to apply the two
patches on every bisected kernel to make the results more distinct?

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

Title:
  [4.8 regression] boot has become very slow

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Yakkety:
  In Progress

Bug description:
  With yakkety's recent update from linux 4.4 to 4.8 booting has become
  a lot slower. It's not one service in particular, but without "quiet"
  and "splash" you can now easily read every single line instead of that
  whole wall of text zipping by. It now takes over 20s instead of ~10
  seconds to boot.

  This is even more dramatic when factoring out the recent boot hang of
  NetworkManager (bug 1622893) and disabling lightdm:

    sudo systemctl mask NetworkManager NetworkManager-wait-online
  lightdm

  then booting with 4.4 takes 1.5s and with 4.8 19.5s (!).

  Some excerps from systemd-analyze blame:

  4.4:
     474ms postfix@-.service
     395ms lxd-containers.service
     305ms networking.service

  4.8:
    4.578s postfix@-.service
    7.300s lxd-containers.service
    6.285s networking.service

  I attach the full outputs of critical-chain and analyze for 4.4 and
  4.8 for reference.

  This is much less noticeable in the running system. There is no
  immediate feeling of sluggishness (although my system is by and large
  idle).

  I compared the time of sbuilding colord under similar circumstances
  (-j4, building on tmpfs, thus no hard disk delays; running with fully
  pre-loaded apt-cacher-ng thus no random network delays), and with 4.4
  it takes 6.5 minutes and with 4.8 it takes 7.5. So that got a bit
  slower, but much less dramatically than during boot, so this is either
  happening when a lot of processes run in parallel, or is perhaps
  related to setting up cgroups.

  One thing I noticed that during sbuild in 4.8 "top" shows ridiculous
  loads (~ 250) under 4.8, while it's around 4 or 5 under 4.4. But that
  doesn't reflect in actual sluggishness, so this might be just an
  unrelated bug.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: linux-image-4.8.0-11-generic 4.8.0-11.12
  ProcVersionSignature: Ubuntu 4.8.0-11.12-generic 4.8.0-rc6
  Uname: Linux 4.8.0-11-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   martin 3049 F...m pulseaudio
   /dev/snd/pcmC0D0p:   martin 3049 F...m pulseaudio
   /dev/snd/controlC0:  martin 3049 F pulseaudio
  Date: Thu Sep 22 09:42:56 2016
  EcryptfsInUse: Yes
  MachineType: LENOVO 2324CTO
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.8.0-11-generic.efi.signed 
root=UUID=f86539b0-3a1b-4372-83b0-acdd029ade68 ro rootflags=subvol=@ 
systemd.debug-shell
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-11-generic N/A
   linux-backports-modules-4.8.0-11-generic  N/A
   linux-firmware1.161
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/09/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G2ET95WW (2.55 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2324CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: 0B98401 Pro
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG2ET95WW(2.55):bd07/09/2013:svnLENOVO:pn2324CTO:pvrThinkPadX230:rvnLENOVO:rn2324CTO:rvr0B98401Pro:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 2324CTO
  dmi.product.version: ThinkPad X230
  dmi.sys.vendor: LENOVO

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1626436] Re: [4.8 regression] boot has become very slow

[Martin Pitt]

Thanks Florian and Joseph! With the two patches it's definitively a lot
better! Boot times without NM and lightdm:

4.4: 1.5s
4.8.0-22 (zesty): 16.8s
4.8.0-26 (Joseph's kernel): 8.4s

So still quite far from what we used to have, but already twice as fast
as the current y/z kernel.

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

Title:
  [4.8 regression] boot has become very slow

Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Yakkety:
  Triaged

Bug description:
  With yakkety's recent update from linux 4.4 to 4.8 booting has become
  a lot slower. It's not one service in particular, but without "quiet"
  and "splash" you can now easily read every single line instead of that
  whole wall of text zipping by. It now takes over 20s instead of ~10
  seconds to boot.

  This is even more dramatic when factoring out the recent boot hang of
  NetworkManager (bug 1622893) and disabling lightdm:

    sudo systemctl mask NetworkManager NetworkManager-wait-online
  lightdm

  then booting with 4.4 takes 1.5s and with 4.8 19.5s (!).

  Some excerps from systemd-analyze blame:

  4.4:
     474ms postfix@-.service
     395ms lxd-containers.service
     305ms networking.service

  4.8:
    4.578s postfix@-.service
    7.300s lxd-containers.service
    6.285s networking.service

  I attach the full outputs of critical-chain and analyze for 4.4 and
  4.8 for reference.

  This is much less noticeable in the running system. There is no
  immediate feeling of sluggishness (although my system is by and large
  idle).

  I compared the time of sbuilding colord under similar circumstances
  (-j4, building on tmpfs, thus no hard disk delays; running with fully
  pre-loaded apt-cacher-ng thus no random network delays), and with 4.4
  it takes 6.5 minutes and with 4.8 it takes 7.5. So that got a bit
  slower, but much less dramatically than during boot, so this is either
  happening when a lot of processes run in parallel, or is perhaps
  related to setting up cgroups.

  One thing I noticed that during sbuild in 4.8 "top" shows ridiculous
  loads (~ 250) under 4.8, while it's around 4 or 5 under 4.4. But that
  doesn't reflect in actual sluggishness, so this might be just an
  unrelated bug.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: linux-image-4.8.0-11-generic 4.8.0-11.12
  ProcVersionSignature: Ubuntu 4.8.0-11.12-generic 4.8.0-rc6
  Uname: Linux 4.8.0-11-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   martin 3049 F...m pulseaudio
   /dev/snd/pcmC0D0p:   martin 3049 F...m pulseaudio
   /dev/snd/controlC0:  martin 3049 F pulseaudio
  Date: Thu Sep 22 09:42:56 2016
  EcryptfsInUse: Yes
  MachineType: LENOVO 2324CTO
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.8.0-11-generic.efi.signed 
root=UUID=f86539b0-3a1b-4372-83b0-acdd029ade68 ro rootflags=subvol=@ 
systemd.debug-shell
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-11-generic N/A
   linux-backports-modules-4.8.0-11-generic  N/A
   linux-firmware1.161
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/09/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G2ET95WW (2.55 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2324CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: 0B98401 Pro
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG2ET95WW(2.55):bd07/09/2013:svnLENOVO:pn2324CTO:pvrThinkPadX230:rvnLENOVO:rn2324CTO:rvr0B98401Pro:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 2324CTO
  dmi.product.version: ThinkPad X230
  dmi.sys.vendor: LENOVO

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1634519] Re: linux autopkgtest: eternal hang/ BUG: soft lockup

[Martin Pitt]

Second run: Nothing useful at all in "nova console-log" (just the normal
boot up to "login:"), test output tail is

07:32:01 DEBUG| [stdout] nice PASSED
07:32:11 DEBUG| [stdout] null PASSED
07:32:21 DEBUG| [stdout] opcode PASSED
07:32:31 DEBUG| [stdout] open PASSED
07:32:41 DEBUG| [stdout] personality PASSED
07:32:51 DEBUG| [stdout] pipe PASSED
07:33:01 DEBUG| [stdout] poll PASSED

dmesg tail is more interesting, as it has some trace:

[1.568250] AppArmor: AppArmor sha1 policy hashing enabled   


[21/1103]
[1.569433] ima: No TPM chip found, activating TPM-bypass!
[1.570642] evm: HMAC attrs: 0x1
[1.571783]   Magic number: 4:640:161
[1.572860] rtc_cmos 00:00: setting system clock to 2016-10-21 04:10:09 UTC 
(1477023009)
[1.574813] BIOS EDD facility v0.16 2004-Jun-25, 0 devices found
[1.576127] EDD information not available.
[1.577057] PM: Hibernation image not present or could not be loaded.
[1.653017] isapnp: No Plug & Play device found
[1.654764] Freeing unused kernel memory: 984K (d3c21000 - d3d17000)
[1.656407] Write protecting the kernel text: 8252k
[1.657711] Write protecting the kernel read-only data: 3324k
[1.658992] NX-protecting the kernel data: 6084k
[1.660357] [ cut here ]
[1.661352] WARNING: CPU: 0 PID: 1 at 
/build/linux-yFroJZ/linux-4.8.0/arch/x86/mm/dump_pagetables.c:225 
note_page+0x6a1/0x880
[1.663740] x86/mm: Found insecure W+X mapping at address c00a/0xc00a
[1.665280] Modules linked in:
[1.666020] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 4.8.0-26-generic 
#28-Ubuntu
[1.667603] Hardware name: OpenStack Foundation OpenStack Nova, BIOS Bochs 
01/01/2011
[1.669270]  d3b54967 625585ec 00200286 d7cabe70 d33da625 d7cabeb4 d3a38b68 
d7cabea0
[1.669270]  d3071b9a d3a38b30 d7cabed4 0001 d3a38b68 00e1 d30682a1 
00e1
[1.669270]  d7cabf34 8000  d7cabec0 d3071c06 0009  
d7cabeb4
[1.669270] Call Trace:
[1.669270]  [] dump_stack+0x58/0x73
[1.669270]  [] __warn+0xea/0x110
[1.669270]  [] ? note_page+0x6a1/0x880
[1.669270]  [] warn_slowpath_fmt+0x46/0x60
[1.669270]  [] note_page+0x6a1/0x880
[1.669270]  [] ptdump_walk_pgd_level_core+0x1f5/0x300
[1.669270]  [] ptdump_walk_pgd_level_checkwx+0x16/0x20
[1.669270]  [] mark_rodata_ro+0xfd/0x130
[1.669270]  [] kernel_init+0x2c/0x100
[1.669270]  [] ? schedule_tail+0x11/0x50
[1.669270]  [] ret_from_kernel_thread+0xe/0x24
[1.669270]  [] ? rest_init+0x70/0x70
[1.688344] ---[ end trace c05a9abbb5340752 ]---
[1.689410] x86/mm: Checked W+X mappings: FAILED, 96 W+X pages found.
[1.708425] random: systemd-udevd: uninitialized urandom read (16 bytes read)
[1.710325] random: udevadm: uninitialized urandom read (16 bytes read)
[1.710853] random: udevadm: uninitialized urandom read (16 bytes read)
[1.711745] random: udevadm: uninitialized urandom read (16 bytes read)
[1.711864] random: udevadm: uninitialized urandom read (16 bytes read)
[1.712433] random: udevadm: uninitialized urandom read (16 bytes read)
[1.712560] random: udevadm: uninitialized urandom read (16 bytes read)
[1.712670] random: udevadm: uninitialized urandom read (16 bytes read)
[1.712787] random: udevadm: uninitialized urandom read (16 bytes read)
[1.712907] random: udevadm: uninitialized urandom read (16 bytes read)
[1.763408] virtio_net virtio0 ens2: renamed from eth0
[1.787845] input: VirtualPS/2 VMware VMMouse as 
/devices/platform/i8042/serio1/input/input4
[1.790353] input: VirtualPS/2 VMware VMMouse as 
/devices/platform/i8042/serio1/input/input3
[1.809191] FDC 0 is a S82078B
[1.960057] raid6: mmxx1gen()  1882 MB/s
[2.028044] raid6: mmxx2gen()  3964 MB/s
[2.096071] raid6: sse1x1   gen()  1800 MB/s
[2.164055] raid6: sse1x2   gen()  3682 MB/s
[2.232054] raid6: sse2x1   gen()  3614 MB/s
[2.300046] raid6: sse2x1   xor()  3707 MB/s
[2.368047] raid6: sse2x2   gen()  6710 MB/s
[2.436044] raid6: sse2x2   xor()  4994 MB/s
[2.437024] raid6: using algorithm sse2x2 gen() 6710 MB/s
[2.438174] raid6:  xor() 4994 MB/s, rmw enabled
[2.439221] raid6: using ssse3x1 recovery algorithm
[2.445977] xor: automatically using best checksumming function: avx
[2.506401] Btrfs loaded, crc32c=crc32c-intel
[2.579605] EXT4-fs (vda1): mounted filesystem with ordered data mode. Opts: 
(null)
[2.686394] ip_tables: (C) 2000-2006 Netfilter Core Team
[2.689931] random: fast init done
[2.725766] systemd[1]: systemd 231 running in system mode. (+PAM +AUDIT 
+SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS 
+ACL +XZ -LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD +IDN)
[

[Kernel-packages] [Bug 1634519] Re: linux autopkgtest: eternal hang/ BUG: soft lockup

[Martin Pitt]

The tests (both yakkety and zesty) are still looping, I'm afraid. I
didn't see the "BUG soft lockup" in the one instance I was watching.
There were no obvious kernel call traces in dmesg, and the test output
tail is just:

06:27:14 DEBUG| [stdout] 
Killed
DEBUG - Leave sh
ERROR - The command (AUTOTEST_PATH=/home/ubuntu/autotest sudo -E 
autotest/client/autotest-local --verbose 
autotest/client/tests/ubuntu_qrt_apparmor/control) return
ed a non-zero exit status (137).
ERROR - 06:03:39 INFO | Writing results to 
/tmp/autopkgtest.XDxmzj/build.2sj/linux-4.8.0/autotest/client/results/default
ERROR - 06:03:39 DEBUG| Initializing the state engine
ERROR - 06:03:39 DEBUG| Persistent state client.steps now set to []
ERROR - 06:03:39 DEBUG| Persistent option harness now set to None
ERROR - 06:03:39 DEBUG| Persistent option harness_args now set to None
ERROR - 06:03:39 DEBUG| Selected harness: standalone
ERROR - 06:03:39 INFO | START   timestamp=1477029819
localtime=Oct 21 06:03:39
ERROR - 06:03:39 DEBUG| Persistent state client._record_indent now set to 1
ERROR - 06:03:39 DEBUG| Test has timeout: 7200 sec.
ERROR - 06:03:39 INFO | START   ubuntu_qrt_apparmor.setup   
ubuntu_qrt_apparmor.setup   timestamp=1477029819timeout=7200
localtime=Oct 21 06
:03:39
ERROR - 06:03:39 DEBUG| Persistent state client._record_indent now set to 2
ERROR - 06:03:39 DEBUG| Persistent state client.unexpected_reboot now set to 
('ubuntu_qrt_apparmor.setup', 'ubuntu_qrt_apparmor.setup')
ERROR - 06:03:39 DEBUG| Waiting for pid 2611 for 7200 seconds
ERROR - 06:03:39 DEBUG| Running 'apt-get update'
[...]
ERROR - 06:05:02 DEBUG| [stdout] Unpacking libgraphite2-3:i386 (1.3.8-1ubuntu1) 
...
ERROR - 06:05:02 DEBUG| [stdout] Selecting previously unselected package 
libharfbuzz0b:i386.
ERROR - 06:05:02 DEBUG| [stdout] Preparing to unpack 
.../035-libharfbuzz0b_1.2.7-1_i386.deb ...
ERROR - 06:05:02 DEBUG| [stdout] Unpacking libharfbuzz0b:i386 (1.2.7-1) ...
ERROR - 06:05:02 DEBUG| [stdout] Selecting previously unselected package 
libpangoft2-1.0-0:i386.
ERROR - 06:05:02 DEBUG| [stdout] Preparing to unpack 
.../036-libpangoft2-1.0-0_1.40.3-2_i386.deb ...
ERROR - 06:05:02 DEBUG| [stdout] Unpacking libpangoft2-1.0-0:i386 (1.40.3-2) ...
Killed
Connection to 10.220.46.18 closed by remote host.
Exit request sent.
autopkgtest [06:31:15]: ERROR: testbed failure: testbed auxverb failed with 
exit code 255

So this time it seems apt gets killed. The VM went away after that, so I
don't have it any more for investigation.

I'm watching another current run and will get its journalctl -f and test
output tail, and will then kill the current runs again as there are a
lot of them, they loop, and they block large amounts of capacity.

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

Title:
  linux autopkgtest: eternal hang/ BUG: soft lockup

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Following up to bug 1632252, tests still hang (but not due to the
  suspend issue any more). In a local QEMU run:

  $ autopkgtest --testname ubuntu-regression-suite linux -- qemu 
--ram-size=4096 -o /var/cache/martin /srv/vm/autopkgtest-yakkety-amd64.img
  [...]
  14:46:41 DEBUG| [stdout] Test icebp [Ok]
  14:46:41 DEBUG| [stdout] Test int 3 trap [Ok]
  14:46:41 DEBUG| [stdout] selftests: breakpoint_test [PASS]

  and since then (1 hour) it's hung. But now I still can log into ttyS0.
  dmesg is almost empty:

  [ 5501.499217] ata2.01: NODEV after polling detection
  [ 5501.500138] ata2.00: configured for MWDMA2

  (something in the test clears the ring buffer), and journalctl
  confirms that suspend/resume worked fine:

  Oct 18 14:47:11 autopkgtest kernel: PM: suspend of devices complete after 
65.273 msecs
  Oct 18 14:47:11 autopkgtest kernel: PM: late suspend of devices complete 
after 0.172 msecs
  Oct 18 14:47:11 autopkgtest kernel: PM: noirq suspend of devices complete 
after 1.963 msecs
  Oct 18 14:47:11 autopkgtest kernel: ACPI: Preparing to enter system sleep 
state S3
  Oct 18 14:47:11 autopkgtest kernel: PM: Saving platform NVS memory
  Oct 18 14:47:11 autopkgtest kernel: Disabling non-boot CPUs ...
  Oct 18 14:47:11 autopkgtest kernel: kvm-clock: cpu 0, msr 1:3fff4001, primary 
cpu clock, resume
  Oct 18 14:47:11 autopkgtest kernel: ACPI: Low-level resume complete
  Oct 18 14:47:11 autopkgtest kernel: PM: Restoring platform NVS memory
  Oct 18 14:47:11 autopkgtest kernel: ACPI: Waking up from system sleep state S3
  Oct 18 14:47:11 autopkgtest kernel: PM: noirq resume of devices complete 
after 6.973 msecs
  Oct 18 14:47:11 autopkgtest kernel: PM: early resume of devices complete 
after 0.105 msecs
  Oct 18 14:47:11 autopkgtest kernel: pci :00:01.0: PIIX3: Enabling Passive 
Release
  Oct 18 14:47:11 autopkgtest kernel: rtc_cmos 00:00: System wakeup disabled by 
ACPI
  Oct 18 14:47:11 

[Kernel-packages] [Bug 1626436] Re: [4.8 regression] boot has become very slow

[Martin Pitt]

> 4.7-rc1: http://kernel.ubuntu.com/~kernel-
ppa/mainline/v4.7-rc1-yakkety/

bad

Thanks Joseph for taking this!

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

Title:
  [4.8 regression] boot has become very slow

Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Yakkety:
  Triaged

Bug description:
  With yakkety's recent update from linux 4.4 to 4.8 booting has become
  a lot slower. It's not one service in particular, but without "quiet"
  and "splash" you can now easily read every single line instead of that
  whole wall of text zipping by. It now takes over 20s instead of ~10
  seconds to boot.

  This is even more dramatic when factoring out the recent boot hang of
  NetworkManager (bug 1622893) and disabling lightdm:

    sudo systemctl mask NetworkManager NetworkManager-wait-online
  lightdm

  then booting with 4.4 takes 1.5s and with 4.8 19.5s (!).

  Some excerps from systemd-analyze blame:

  4.4:
     474ms postfix@-.service
     395ms lxd-containers.service
     305ms networking.service

  4.8:
    4.578s postfix@-.service
    7.300s lxd-containers.service
    6.285s networking.service

  I attach the full outputs of critical-chain and analyze for 4.4 and
  4.8 for reference.

  This is much less noticeable in the running system. There is no
  immediate feeling of sluggishness (although my system is by and large
  idle).

  I compared the time of sbuilding colord under similar circumstances
  (-j4, building on tmpfs, thus no hard disk delays; running with fully
  pre-loaded apt-cacher-ng thus no random network delays), and with 4.4
  it takes 6.5 minutes and with 4.8 it takes 7.5. So that got a bit
  slower, but much less dramatically than during boot, so this is either
  happening when a lot of processes run in parallel, or is perhaps
  related to setting up cgroups.

  One thing I noticed that during sbuild in 4.8 "top" shows ridiculous
  loads (~ 250) under 4.8, while it's around 4 or 5 under 4.4. But that
  doesn't reflect in actual sluggishness, so this might be just an
  unrelated bug.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: linux-image-4.8.0-11-generic 4.8.0-11.12
  ProcVersionSignature: Ubuntu 4.8.0-11.12-generic 4.8.0-rc6
  Uname: Linux 4.8.0-11-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   martin 3049 F...m pulseaudio
   /dev/snd/pcmC0D0p:   martin 3049 F...m pulseaudio
   /dev/snd/controlC0:  martin 3049 F pulseaudio
  Date: Thu Sep 22 09:42:56 2016
  EcryptfsInUse: Yes
  MachineType: LENOVO 2324CTO
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.8.0-11-generic.efi.signed 
root=UUID=f86539b0-3a1b-4372-83b0-acdd029ade68 ro rootflags=subvol=@ 
systemd.debug-shell
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-11-generic N/A
   linux-backports-modules-4.8.0-11-generic  N/A
   linux-firmware1.161
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/09/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G2ET95WW (2.55 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2324CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: 0B98401 Pro
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG2ET95WW(2.55):bd07/09/2013:svnLENOVO:pn2324CTO:pvrThinkPadX230:rvnLENOVO:rn2324CTO:rvr0B98401Pro:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 2324CTO
  dmi.product.version: ThinkPad X230
  dmi.sys.vendor: LENOVO

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1626436] Re: [4.8 regression] boot has become very slow

[Martin Pitt]

> 4.5 final: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.5-wily/

good

> 4.6 final: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.6-yakkety/

good

> 4.7 final: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.7/

bad

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

Title:
  [4.8 regression] boot has become very slow

Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Yakkety:
  Triaged

Bug description:
  With yakkety's recent update from linux 4.4 to 4.8 booting has become
  a lot slower. It's not one service in particular, but without "quiet"
  and "splash" you can now easily read every single line instead of that
  whole wall of text zipping by. It now takes over 20s instead of ~10
  seconds to boot.

  This is even more dramatic when factoring out the recent boot hang of
  NetworkManager (bug 1622893) and disabling lightdm:

    sudo systemctl mask NetworkManager NetworkManager-wait-online
  lightdm

  then booting with 4.4 takes 1.5s and with 4.8 19.5s (!).

  Some excerps from systemd-analyze blame:

  4.4:
     474ms postfix@-.service
     395ms lxd-containers.service
     305ms networking.service

  4.8:
    4.578s postfix@-.service
    7.300s lxd-containers.service
    6.285s networking.service

  I attach the full outputs of critical-chain and analyze for 4.4 and
  4.8 for reference.

  This is much less noticeable in the running system. There is no
  immediate feeling of sluggishness (although my system is by and large
  idle).

  I compared the time of sbuilding colord under similar circumstances
  (-j4, building on tmpfs, thus no hard disk delays; running with fully
  pre-loaded apt-cacher-ng thus no random network delays), and with 4.4
  it takes 6.5 minutes and with 4.8 it takes 7.5. So that got a bit
  slower, but much less dramatically than during boot, so this is either
  happening when a lot of processes run in parallel, or is perhaps
  related to setting up cgroups.

  One thing I noticed that during sbuild in 4.8 "top" shows ridiculous
  loads (~ 250) under 4.8, while it's around 4 or 5 under 4.4. But that
  doesn't reflect in actual sluggishness, so this might be just an
  unrelated bug.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: linux-image-4.8.0-11-generic 4.8.0-11.12
  ProcVersionSignature: Ubuntu 4.8.0-11.12-generic 4.8.0-rc6
  Uname: Linux 4.8.0-11-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   martin 3049 F...m pulseaudio
   /dev/snd/pcmC0D0p:   martin 3049 F...m pulseaudio
   /dev/snd/controlC0:  martin 3049 F pulseaudio
  Date: Thu Sep 22 09:42:56 2016
  EcryptfsInUse: Yes
  MachineType: LENOVO 2324CTO
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.8.0-11-generic.efi.signed 
root=UUID=f86539b0-3a1b-4372-83b0-acdd029ade68 ro rootflags=subvol=@ 
systemd.debug-shell
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-11-generic N/A
   linux-backports-modules-4.8.0-11-generic  N/A
   linux-firmware1.161
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/09/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G2ET95WW (2.55 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2324CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: 0B98401 Pro
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG2ET95WW(2.55):bd07/09/2013:svnLENOVO:pn2324CTO:pvrThinkPadX230:rvnLENOVO:rn2324CTO:rvr0B98401Pro:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 2324CTO
  dmi.product.version: ThinkPad X230
  dmi.sys.vendor: LENOVO

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1634132] Re: using hugepages/hugepagesz causes kexec'd kernel to OOM

[Martin Pitt]

Hello Chris, or anyone else affected,

Accepted makedumpfile into yakkety-proposed. The package will build now
and be available at
https://launchpad.net/ubuntu/+source/makedumpfile/1:1.6.0-2ubuntu1.1 in
a few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed.  Your feedback will aid us getting this update
out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, and change the tag
from verification-needed to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed.  In either case, details of your testing will help
us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Changed in: makedumpfile (Ubuntu Yakkety)
   Status: In Progress => Fix Committed

** Tags added: verification-needed

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to makedumpfile in Ubuntu.
https://bugs.launchpad.net/bugs/1634132

Title:
  using hugepages/hugepagesz causes kexec'd kernel to OOM

Status in makedumpfile package in Ubuntu:
  Fix Released
Status in makedumpfile source package in Trusty:
  In Progress
Status in makedumpfile source package in Xenial:
  In Progress
Status in makedumpfile source package in Yakkety:
  Fix Committed
Status in makedumpfile source package in Zesty:
  Fix Released

Bug description:
  [Impact]
  Users of kdump won't be able to dump if their system uses 
hugepages/hugepagesz on the cmdline.

  [Test Case]
  1) Install crashdump
  2) Boot machine with hugepages= or hugepagesz= set to a significant amount of 
memory
  3) Try to crash with 'echo 'c' | sudo tee /proc/sysrq-trigger'

  [Regression Potential]
  If users really want to have hugepages/hugepagesz on the kexec'd kernel for 
kdump they can add this via KDUMP_CMDLINE_APPEND in /etc/default/kdump-tools.
  This patch should also potentially go upstream.

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1626436] Re: [4.8 regression] boot has become very slow

[Martin Pitt]

** Description changed:

  With yakkety's recent update from linux 4.4 to 4.8 booting has become a
  lot slower. It's not one service in particular, but without "quiet" and
  "splash" you can now easily read every single line instead of that whole
  wall of text zipping by. It now takes over 20s instead of ~10 seconds to
  boot.
  
  This is even more dramatic when factoring out the recent boot hang of
  NetworkManager (bug 1622893) and disabling lightdm:
  
-   sudo systemctl mask NetworkManager NetworkManager-wait-online lightdm
+   sudo systemctl mask NetworkManager NetworkManager-wait-online lightdm
  
  then booting with 4.4 takes 1.5s and with 4.8 19.5s (!).
  
  Some excerps from systemd-analyze blame:
  
  4.4:
-474ms postfix@-.service
-395ms lxd-containers.service
-305ms networking.service
+    474ms postfix@-.service
+    395ms lxd-containers.service
+    305ms networking.service
  
  4.8:
-   4.578s postfix@-.service
-   7.300s lxd-containers.service
-   6.285s networking.service
+   4.578s postfix@-.service
+   7.300s lxd-containers.service
+   6.285s networking.service
  
  I attach the full outputs of critical-chain and analyze for 4.4 and 4.8
  for reference.
  
- 
- This is much less noticeable in the running system. There is no immediate 
feeling of sluggishness (although my system is by and large idle).
+ This is much less noticeable in the running system. There is no
+ immediate feeling of sluggishness (although my system is by and large
+ idle).
  
  I compared the time of sbuilding colord under similar circumstances
  (-j4, building on tmpfs, thus no hard disk delays; running with fully
  pre-loaded apt-cacher-ng thus no random network delays), and with 4.4 it
  takes 6.5 minutes and with 4.8 it takes 7.5. So that got a bit slower,
  but much less dramatically than during boot, so this is either happening
  when a lot of processes run in parallel, or is perhaps related to
  setting up cgroups.
  
  One thing I noticed that during sbuild in 4.8 "top" shows ridiculous
- loads (~ 250) under 4.8, while it's around 4 or 5 under 4.8. But that
+ loads (~ 250) under 4.8, while it's around 4 or 5 under 4.4. But that
  doesn't reflect in actual sluggishness, so this might be just an
  unrelated bug.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: linux-image-4.8.0-11-generic 4.8.0-11.12
  ProcVersionSignature: Ubuntu 4.8.0-11.12-generic 4.8.0-rc6
  Uname: Linux 4.8.0-11-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
-  USERPID ACCESS COMMAND
-  /dev/snd/pcmC0D0c:   martin 3049 F...m pulseaudio
-  /dev/snd/pcmC0D0p:   martin 3049 F...m pulseaudio
-  /dev/snd/controlC0:  martin 3049 F pulseaudio
+  USERPID ACCESS COMMAND
+  /dev/snd/pcmC0D0c:   martin 3049 F...m pulseaudio
+  /dev/snd/pcmC0D0p:   martin 3049 F...m pulseaudio
+  /dev/snd/controlC0:  martin 3049 F pulseaudio
  Date: Thu Sep 22 09:42:56 2016
  EcryptfsInUse: Yes
  MachineType: LENOVO 2324CTO
  ProcEnviron:
-  TERM=linux
-  PATH=(custom, no user)
-  XDG_RUNTIME_DIR=
-  LANG=de_DE.UTF-8
-  SHELL=/bin/bash
+  TERM=linux
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=de_DE.UTF-8
+  SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.8.0-11-generic.efi.signed 
root=UUID=f86539b0-3a1b-4372-83b0-acdd029ade68 ro rootflags=subvol=@ 
systemd.debug-shell
  RelatedPackageVersions:
-  linux-restricted-modules-4.8.0-11-generic N/A
-  linux-backports-modules-4.8.0-11-generic  N/A
-  linux-firmware1.161
+  linux-restricted-modules-4.8.0-11-generic N/A
+  linux-backports-modules-4.8.0-11-generic  N/A
+  linux-firmware1.161
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/09/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G2ET95WW (2.55 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2324CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: 0B98401 Pro
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG2ET95WW(2.55):bd07/09/2013:svnLENOVO:pn2324CTO:pvrThinkPadX230:rvnLENOVO:rn2324CTO:rvr0B98401Pro:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 2324CTO
  dmi.product.version: ThinkPad X230
  dmi.sys.vendor: LENOVO

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

Title:
  [4.8 regression] boot has become very slow

Status in linux package in Ubuntu:
  Triaged

Bug description:
  With yakkety's recent update from linux 4.4 to 4.8 booting has become
  a lot slower. It's not one service in particular, but without "quiet"
  and "splash" you can 

[Kernel-packages] [Bug 1635171] Re: IPv6 Privacy Extensions do not work

[Martin Pitt]

** Package changed: systemd (Ubuntu) => linux (Ubuntu)

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

Title:
  IPv6 Privacy Extensions do not work

Status in linux package in Ubuntu:
  New

Bug description:
  On my Ubuntu 14.04.5 Server IPv6 Privacy Extensions do not work any
  more after upgrading to kernel 3.13.0-100-generic, although privacy
  extensions are enabled in the config:

  root@Sputnik:~# cat /etc/sysctl.d/10-ipv6-privacy.conf | grep tempaddr
  net.ipv6.conf.all.use_tempaddr = 2
  net.ipv6.conf.default.use_tempaddr = 2

  Although the privacy extensions seem to be enabled generally, they are
  somehow not enabled for my primary network interface eth0:

  root@Sputnik:~# sysctl -a | grep tempaddr
  net.ipv6.conf.all.use_tempaddr = 2
  net.ipv6.conf.default.use_tempaddr = 2
  net.ipv6.conf.eth0.use_tempaddr = 0
  net.ipv6.conf.lo.use_tempaddr = -1
  net.ipv6.conf.wlan0.use_tempaddr = 2

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1632252] Re: linux autopkgtest kills sshd in testbed

[Martin Pitt]

Indeed we did get a "proper" timeout now \o/

https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
/autopkgtest-yakkety/yakkety/amd64/l/linux/20161018_180219_53396@/log.gz

So closing this one, and using bug 1634519 for the new timeout.

** Changed in: linux (Ubuntu Yakkety)
   Status: Confirmed => Fix Released

** Changed in: linux (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  linux autopkgtest kills sshd in testbed

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Yakkety:
  Fix Released

Bug description:
  The current linux autopkgtests in yakkety are caught in an eternal
  "temporary failure" retry loop. They stopped timing out, but in the
  middle of the tests they kill sshd.

  Tail of test output:

  09:01:00 DEBUG| [stdout]   preparing apparmor_2.10.95-4ubuntu5.dsc... done
  09:01:00 DEBUG| [stdout] 
  09:01:40 ERROR| [stderr] Run libapparmor testsuite (with python3) ... ok
  09:01:40 ERROR| [stderr] test_parser_testsuite (__main__.ApparmorTestsuites)
  09:01:48 DEBUG| [stdout]   preparing apparmor_2.10.95-4ubuntu5.dsc... done
  09:01:48 DEBUG| [stdout] 
  09:19:27 ERROR| [stderr] Run parser regression tests ... ok
  09:19:27 ERROR| [stderr] test_regression_testsuite 
(__main__.ApparmorTestsuites)
  09:19:33 DEBUG| [stdout]   preparing apparmor_2.10.95-4ubuntu5.dsc... done
  09:19:33 DEBUG| [stdout] 
  Killed
  Killed
  Connection to 10.220.42.236 closed by remote host.
  Exit request sent.
  autopkgtest [09:24:42]: ERROR: testbed failure: testbed auxverb failed with 
exit code 255

  Console output during the test:

  Ubuntu 16.10 autopkgtest ttyS0

  autopkgtest login: [ 3512.996305] AppArmor: change_hat: Invalid input '^open'
  [ 3513.000678] AppArmor: change_hat: Invalid input '^'[ 3513.013965] 
AppArmor: change_hat: Invalid input, NULL hat and NULL magic
  [ 3513.019831] AppArmor: change_hat: Invalid input, NULL hat and NULL magic
  [ 3513.024872] AppArmor: change_hat: Invalid input '^open'AppArmor: 
change_hat: Invalid input '^'
  [ 3513.026539] AppArmor: change_hat: Invalid input '^'[ 3638.281408] Out of 
memory: Kill process 587 (rsyslogd) score 8 or sacrifice child
  [ 3638.284907] Killed process 587 (rsyslogd) total-vm:107460kB, 
anon-rss:67892kB, file-rss:2548kB, shmem-rss:0kB
  [ 3638.306990] Out of memory: Kill process 300 (systemd-journal) score 2 or 
sacrifice child
  [ 3638.308985] Killed process 300 (systemd-journal) total-vm:46184kB, 
anon-rss:460kB, file-rss:3752kB, shmem-rss:15412kB
  [ 3638.319337] Out of memory: Kill process 2636 (autotest-local) score 1 or 
sacrifice child
  [ 3638.320394] Killed process 10325 (autotest-local) total-vm:18092kB, 
anon-rss:7296kB, file-rss:3544kB, shmem-rss:0kB
  [ 3638.345419] Out of memory: Kill process 2636 (autotest-local) score 1 or 
sacrifice child
  [ 3638.347095] Killed process 2638 (autotest-local) total-vm:17836kB, 
anon-rss:7160kB, file-rss:1752kB, shmem-rss:0kB
  [ 3638.368917] Out of memory: Kill process 2636 (autotest-local) score 1 or 
sacrifice child
  [ 3638.369954] Killed process 2637 (autotest-local) total-vm:17836kB, 
anon-rss:7160kB, file-rss:1684kB, shmem-rss:0kB
  [ 3638.479196] Out of memory: Kill process 2636 (autotest-local) score 1 or 
sacrifice child
  [ 3638.482968] Killed process 2636 (autotest-local) total-vm:17836kB, 
anon-rss:7248kB, file-rss:5864kB, shmem-rss:0kB
  [ 3638.501050] Out of memory: Kill process 10619 (python) score 1 or 
sacrifice child
  [ 3638.502022] Killed process 14752 (make) total-vm:6052kB, anon-rss:196kB, 
file-rss:2032kB, shmem-rss:0kB
  [ 3638.511243] Out of memory: Kill process 10619 (python) score 1 or 
sacrifice child
  [ 3638.512224] Killed process 10619 (python) total-vm:16752kB, 
anon-rss:5836kB, file-rss:6148kB, shmem-rss:0kB
  [ 3638.525104] Out of memory: Kill process 3382 (python) score 0 or sacrifice 
child
  [ 3638.526060] Killed process 3382 (python) total-vm:21296kB, 
anon-rss:3732kB, file-rss:4080kB, shmem-rss:0kB
  [ 3638.545114] Out of memory: Kill process 553 (haveged) score 0 or sacrifice 
child
  [ 3638.546068] Killed process 553 (haveged) total-vm:8028kB, anon-rss:4780kB, 
file-rss:1468kB, shmem-rss:0kB
  [ 3638.573449] Out of memory: Kill process 10373 (sshd) score 0 or sacrifice 
child
  [ 3638.574353] Killed process 11430 (sshd) total-vm:1kB, anon-rss:1712kB, 
file-rss:2960kB, shmem-rss:0kB
  [ 3638.591696] Out of memory: Kill process 10373 (sshd) score 0 or sacrifice 
child
  [ 3638.595493] Killed process 10373 (sshd) total-vm:13460kB, anon-rss:752kB, 
file-rss:5476kB, shmem-rss:4kB
  [ 3638.605938] Out of memory: Kill process 898 (sshd) score 0 or sacrifice 
child
  [ 3638.607617] Killed process 911 (sshd) total-vm:13804kB, anon-rss:1120kB, 
file-rss:3184kB, shmem-rss:0kB
  [ 3638.626950] Out of memory: Kill 

[Kernel-packages] [Bug 1632252] Re: linux autopkgtest kills sshd in testbed

[Martin Pitt]

It's better now -- in my local QEMU test the last output is now

14:46:41 DEBUG| [stdout] Test icebp [Ok]
14:46:41 DEBUG| [stdout] Test int 3 trap [Ok]
14:46:41 DEBUG| [stdout] selftests: breakpoint_test [PASS]

and since then (1 hour) it's hung. But now I still can log into ttyS0.
dmesg is almost empty:

[ 5501.499217] ata2.01: NODEV after polling detection
[ 5501.500138] ata2.00: configured for MWDMA2

(something in the test clears the ring buffer), and journalctl confirms
that suspend/resume worked fine:

Oct 18 14:47:11 autopkgtest kernel: PM: suspend of devices complete after 
65.273 msecs
Oct 18 14:47:11 autopkgtest kernel: PM: late suspend of devices complete after 
0.172 msecs
Oct 18 14:47:11 autopkgtest kernel: PM: noirq suspend of devices complete after 
1.963 msecs
Oct 18 14:47:11 autopkgtest kernel: ACPI: Preparing to enter system sleep state 
S3
Oct 18 14:47:11 autopkgtest kernel: PM: Saving platform NVS memory
Oct 18 14:47:11 autopkgtest kernel: Disabling non-boot CPUs ...
Oct 18 14:47:11 autopkgtest kernel: kvm-clock: cpu 0, msr 1:3fff4001, primary 
cpu clock, resume
Oct 18 14:47:11 autopkgtest kernel: ACPI: Low-level resume complete
Oct 18 14:47:11 autopkgtest kernel: PM: Restoring platform NVS memory
Oct 18 14:47:11 autopkgtest kernel: ACPI: Waking up from system sleep state S3
Oct 18 14:47:11 autopkgtest kernel: PM: noirq resume of devices complete after 
6.973 msecs
Oct 18 14:47:11 autopkgtest kernel: PM: early resume of devices complete after 
0.105 msecs
Oct 18 14:47:11 autopkgtest kernel: pci :00:01.0: PIIX3: Enabling Passive 
Release
Oct 18 14:47:11 autopkgtest kernel: rtc_cmos 00:00: System wakeup disabled by 
ACPI
Oct 18 14:47:11 autopkgtest kernel: PM: resume of devices complete after 8.898 
msecs
Oct 18 14:47:11 autopkgtest kernel: PM: Finishing wakeup.
Oct 18 14:47:11 autopkgtest systemd[1]: Time has been changed
Oct 18 14:47:11 autopkgtest systemd[1]: apt-daily.timer: Adding 10h 56min 
28.694439s random time.
Oct 18 14:47:11 autopkgtest systemd[3986]: Time has been changed
Oct 18 14:47:11 autopkgtest kernel: Restarting tasks ... done.
Oct 18 14:47:11 autopkgtest sudo[30731]: pam_unix(sudo:session): session closed 
for user root
Oct 18 14:47:11 autopkgtest kernel: ata2.01: NODEV after polling detection
Oct 18 14:47:11 autopkgtest kernel: ata2.00: configured for MWDMA2

But also, no messages beyond that (last message one hour ago).

Colin wants a new bug for this, so I filed bug 1634519.

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

Title:
  linux autopkgtest kills sshd in testbed

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Yakkety:
  Confirmed

Bug description:
  The current linux autopkgtests in yakkety are caught in an eternal
  "temporary failure" retry loop. They stopped timing out, but in the
  middle of the tests they kill sshd.

  Tail of test output:

  09:01:00 DEBUG| [stdout]   preparing apparmor_2.10.95-4ubuntu5.dsc... done
  09:01:00 DEBUG| [stdout] 
  09:01:40 ERROR| [stderr] Run libapparmor testsuite (with python3) ... ok
  09:01:40 ERROR| [stderr] test_parser_testsuite (__main__.ApparmorTestsuites)
  09:01:48 DEBUG| [stdout]   preparing apparmor_2.10.95-4ubuntu5.dsc... done
  09:01:48 DEBUG| [stdout] 
  09:19:27 ERROR| [stderr] Run parser regression tests ... ok
  09:19:27 ERROR| [stderr] test_regression_testsuite 
(__main__.ApparmorTestsuites)
  09:19:33 DEBUG| [stdout]   preparing apparmor_2.10.95-4ubuntu5.dsc... done
  09:19:33 DEBUG| [stdout] 
  Killed
  Killed
  Connection to 10.220.42.236 closed by remote host.
  Exit request sent.
  autopkgtest [09:24:42]: ERROR: testbed failure: testbed auxverb failed with 
exit code 255

  Console output during the test:

  Ubuntu 16.10 autopkgtest ttyS0

  autopkgtest login: [ 3512.996305] AppArmor: change_hat: Invalid input '^open'
  [ 3513.000678] AppArmor: change_hat: Invalid input '^'[ 3513.013965] 
AppArmor: change_hat: Invalid input, NULL hat and NULL magic
  [ 3513.019831] AppArmor: change_hat: Invalid input, NULL hat and NULL magic
  [ 3513.024872] AppArmor: change_hat: Invalid input '^open'AppArmor: 
change_hat: Invalid input '^'
  [ 3513.026539] AppArmor: change_hat: Invalid input '^'[ 3638.281408] Out of 
memory: Kill process 587 (rsyslogd) score 8 or sacrifice child
  [ 3638.284907] Killed process 587 (rsyslogd) total-vm:107460kB, 
anon-rss:67892kB, file-rss:2548kB, shmem-rss:0kB
  [ 3638.306990] Out of memory: Kill process 300 (systemd-journal) score 2 or 
sacrifice child
  [ 3638.308985] Killed process 300 (systemd-journal) total-vm:46184kB, 
anon-rss:460kB, file-rss:3752kB, shmem-rss:15412kB
  [ 3638.319337] Out of memory: Kill process 2636 (autotest-local) score 1 or 
sacrifice child
  [ 3638.320394] Killed process 10325 (autotest-local) total-vm:18092kB, 
anon-rss:7296kB, file-rss:3544kB, shmem-rss:0kB
  [ 3638.345419] Out of memory: Kill 

[Kernel-packages] [Bug 1634519] Re: linux autopkgtest: eternal hang/ BUG: soft lockup

[Martin Pitt]

The local QEMU run also doesn't time out cleanly:


qqemu-system-x86_64: /build/qemu-3KpUoe/qemu-2.6.1+dfsg/hw/char/serial.c:231: 
serial_xmit: Assertion `!(s->lsr & UART_LSR_TEMT)' failed.
autopkgtest [16:03:27]: ERROR: timed out on command "[...]" (kind: test)
autopkgtest [16:03:28]: test ubuntu-regression-suite: ---]
Traceback (most recent call last):
  File "/tmp/autopkgtest-virt-qemu._36vlf46/runcmd", line 63, in 
s.connect('/tmp/autopkgtest-virt-qemu._36vlf46/ttyS1')
ConnectionRefusedError: [Errno 111] Connection refused

I. e. it also breaks the status of ttyS1 somehow.

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

Title:
  linux autopkgtest: eternal hang/ BUG: soft lockup

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Following up to bug 1632252, tests still hang (but not due to the
  suspend issue any more). In a local QEMU run:

  $ autopkgtest --testname ubuntu-regression-suite linux -- qemu 
--ram-size=4096 -o /var/cache/martin /srv/vm/autopkgtest-yakkety-amd64.img
  [...]
  14:46:41 DEBUG| [stdout] Test icebp [Ok]
  14:46:41 DEBUG| [stdout] Test int 3 trap [Ok]
  14:46:41 DEBUG| [stdout] selftests: breakpoint_test [PASS]

  and since then (1 hour) it's hung. But now I still can log into ttyS0.
  dmesg is almost empty:

  [ 5501.499217] ata2.01: NODEV after polling detection
  [ 5501.500138] ata2.00: configured for MWDMA2

  (something in the test clears the ring buffer), and journalctl
  confirms that suspend/resume worked fine:

  Oct 18 14:47:11 autopkgtest kernel: PM: suspend of devices complete after 
65.273 msecs
  Oct 18 14:47:11 autopkgtest kernel: PM: late suspend of devices complete 
after 0.172 msecs
  Oct 18 14:47:11 autopkgtest kernel: PM: noirq suspend of devices complete 
after 1.963 msecs
  Oct 18 14:47:11 autopkgtest kernel: ACPI: Preparing to enter system sleep 
state S3
  Oct 18 14:47:11 autopkgtest kernel: PM: Saving platform NVS memory
  Oct 18 14:47:11 autopkgtest kernel: Disabling non-boot CPUs ...
  Oct 18 14:47:11 autopkgtest kernel: kvm-clock: cpu 0, msr 1:3fff4001, primary 
cpu clock, resume
  Oct 18 14:47:11 autopkgtest kernel: ACPI: Low-level resume complete
  Oct 18 14:47:11 autopkgtest kernel: PM: Restoring platform NVS memory
  Oct 18 14:47:11 autopkgtest kernel: ACPI: Waking up from system sleep state S3
  Oct 18 14:47:11 autopkgtest kernel: PM: noirq resume of devices complete 
after 6.973 msecs
  Oct 18 14:47:11 autopkgtest kernel: PM: early resume of devices complete 
after 0.105 msecs
  Oct 18 14:47:11 autopkgtest kernel: pci :00:01.0: PIIX3: Enabling Passive 
Release
  Oct 18 14:47:11 autopkgtest kernel: rtc_cmos 00:00: System wakeup disabled by 
ACPI
  Oct 18 14:47:11 autopkgtest kernel: PM: resume of devices complete after 
8.898 msecs
  Oct 18 14:47:11 autopkgtest kernel: PM: Finishing wakeup.
  Oct 18 14:47:11 autopkgtest systemd[1]: Time has been changed
  Oct 18 14:47:11 autopkgtest systemd[1]: apt-daily.timer: Adding 10h 56min 
28.694439s random time.
  Oct 18 14:47:11 autopkgtest systemd[3986]: Time has been changed
  Oct 18 14:47:11 autopkgtest kernel: Restarting tasks ... done.
  Oct 18 14:47:11 autopkgtest sudo[30731]: pam_unix(sudo:session): session 
closed for user root
  Oct 18 14:47:11 autopkgtest kernel: ata2.01: NODEV after polling detection
  Oct 18 14:47:11 autopkgtest kernel: ata2.00: configured for MWDMA2

  But also, no messages beyond that (last message one hour ago).

  On the currently running amd64 yakkety test on the ifrastructure, the
  int trap bug fails:

  13:15:46 DEBUG| [stdout] Test icebp [Ok]
  13:15:46 DEBUG| [stdout] Test int 3 trap [Failed]
  13:15:46 DEBUG| [stdout] selftests: breakpoint_test [PASS]

  and then it's apparently hung at exactly the same problem. But unlike
  with local QEMU I cannot ssh in any more (Connection refused), and
  console-log shows trouble:

  autopkgtest login: [ 1927.192886] AppArmor: change_hat: Invalid input '^open'
  [ 1927.194060] AppArmor: change_hat: Invalid input '^'[ 1927.198501] 
AppArmor: change_hat: Invalid input, NULL hat and NULL magic
  [ 1927.203181] AppArmor: change_hat: Invalid input, NULL hat and NULL magic
  [ 1927.207249] AppArmor: change_hat: Invalid input '^open'AppArmor: 
change_hat: Invalid input '^'
  [ 1927.208826] AppArmor: change_hat: Invalid input '^'[[0;32m  OK  [0m] 
Stopped target Graphical Interface.
  [[0;32m  OK  [0m] Stopped target Multi-User System.
   Stopping OpenBSD Secure Shell server...
   Stopping autopkgtest root shell on ttyS1...
  [ 2909.360975] NMI watchdog: BUG: soft lockup - CPU#3 stuck for 22s! 
[swapper/3:0]
  [ 2937.360965] NMI watchdog: BUG: soft lockup - CPU#3 stuck for 22s! 
[swapper/3:0]
  [ 2941.368025] INFO: rcu_sched self-detected stall on CPU
  [ 2941.368095]  3-...: (1 GPs behind) idle=ea7/2/0 softirq=53/53 
fqs=6600 
  [ 2941.368095]   

[Kernel-packages] [Bug 1634519] [NEW] linux autopkgtest: eternal hang/ BUG: soft lockup

[Martin Pitt]

Public bug reported:

Following up to bug 1632252, tests still hang (but not due to the
suspend issue any more). In a local QEMU run:

$ autopkgtest --testname ubuntu-regression-suite linux -- qemu --ram-size=4096 
-o /var/cache/martin /srv/vm/autopkgtest-yakkety-amd64.img
[...]
14:46:41 DEBUG| [stdout] Test icebp [Ok]
14:46:41 DEBUG| [stdout] Test int 3 trap [Ok]
14:46:41 DEBUG| [stdout] selftests: breakpoint_test [PASS]

and since then (1 hour) it's hung. But now I still can log into ttyS0.
dmesg is almost empty:

[ 5501.499217] ata2.01: NODEV after polling detection
[ 5501.500138] ata2.00: configured for MWDMA2

(something in the test clears the ring buffer), and journalctl confirms
that suspend/resume worked fine:

Oct 18 14:47:11 autopkgtest kernel: PM: suspend of devices complete after 
65.273 msecs
Oct 18 14:47:11 autopkgtest kernel: PM: late suspend of devices complete after 
0.172 msecs
Oct 18 14:47:11 autopkgtest kernel: PM: noirq suspend of devices complete after 
1.963 msecs
Oct 18 14:47:11 autopkgtest kernel: ACPI: Preparing to enter system sleep state 
S3
Oct 18 14:47:11 autopkgtest kernel: PM: Saving platform NVS memory
Oct 18 14:47:11 autopkgtest kernel: Disabling non-boot CPUs ...
Oct 18 14:47:11 autopkgtest kernel: kvm-clock: cpu 0, msr 1:3fff4001, primary 
cpu clock, resume
Oct 18 14:47:11 autopkgtest kernel: ACPI: Low-level resume complete
Oct 18 14:47:11 autopkgtest kernel: PM: Restoring platform NVS memory
Oct 18 14:47:11 autopkgtest kernel: ACPI: Waking up from system sleep state S3
Oct 18 14:47:11 autopkgtest kernel: PM: noirq resume of devices complete after 
6.973 msecs
Oct 18 14:47:11 autopkgtest kernel: PM: early resume of devices complete after 
0.105 msecs
Oct 18 14:47:11 autopkgtest kernel: pci :00:01.0: PIIX3: Enabling Passive 
Release
Oct 18 14:47:11 autopkgtest kernel: rtc_cmos 00:00: System wakeup disabled by 
ACPI
Oct 18 14:47:11 autopkgtest kernel: PM: resume of devices complete after 8.898 
msecs
Oct 18 14:47:11 autopkgtest kernel: PM: Finishing wakeup.
Oct 18 14:47:11 autopkgtest systemd[1]: Time has been changed
Oct 18 14:47:11 autopkgtest systemd[1]: apt-daily.timer: Adding 10h 56min 
28.694439s random time.
Oct 18 14:47:11 autopkgtest systemd[3986]: Time has been changed
Oct 18 14:47:11 autopkgtest kernel: Restarting tasks ... done.
Oct 18 14:47:11 autopkgtest sudo[30731]: pam_unix(sudo:session): session closed 
for user root
Oct 18 14:47:11 autopkgtest kernel: ata2.01: NODEV after polling detection
Oct 18 14:47:11 autopkgtest kernel: ata2.00: configured for MWDMA2

But also, no messages beyond that (last message one hour ago).

On the currently running amd64 yakkety test on the ifrastructure, the
int trap bug fails:

13:15:46 DEBUG| [stdout] Test icebp [Ok]
13:15:46 DEBUG| [stdout] Test int 3 trap [Failed]
13:15:46 DEBUG| [stdout] selftests: breakpoint_test [PASS]

and then it's apparently hung at exactly the same problem. But unlike
with local QEMU I cannot ssh in any more (Connection refused), and
console-log shows trouble:

autopkgtest login: [ 1927.192886] AppArmor: change_hat: Invalid input '^open'
[ 1927.194060] AppArmor: change_hat: Invalid input '^'[ 1927.198501] AppArmor: 
change_hat: Invalid input, NULL hat and NULL magic
[ 1927.203181] AppArmor: change_hat: Invalid input, NULL hat and NULL magic
[ 1927.207249] AppArmor: change_hat: Invalid input '^open'AppArmor: change_hat: 
Invalid input '^'
[ 1927.208826] AppArmor: change_hat: Invalid input '^'[[0;32m  OK  [0m] Stopped 
target Graphical Interface.
[[0;32m  OK  [0m] Stopped target Multi-User System.
 Stopping OpenBSD Secure Shell server...
 Stopping autopkgtest root shell on ttyS1...
[ 2909.360975] NMI watchdog: BUG: soft lockup - CPU#3 stuck for 22s! 
[swapper/3:0]
[ 2937.360965] NMI watchdog: BUG: soft lockup - CPU#3 stuck for 22s! 
[swapper/3:0]
[ 2941.368025] INFO: rcu_sched self-detected stall on CPU
[ 2941.368095]  3-...: (1 GPs behind) idle=ea7/2/0 softirq=53/53 
fqs=6600 
[ 2941.368095]   (t=15000 jiffies g=205236 c=205235 q=134637)
[ 2969.360984] NMI watchdog: BUG: soft lockup - CPU#3 stuck for 22s! 
[swapper/3:0]
[ 2997.360987] NMI watchdog: BUG: soft lockup - CPU#3 stuck for 22s! 
[swapper/3:0]
[ 3021.796060] INFO: task systemd:1 blocked for more than 120 seconds.
[ 3021.797626]   Tainted: GW  OEL  4.8.0-25-generic #27-Ubuntu
[ 3021.797627] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this 
message.
[ 3021.797727] INFO: task systemd-journal:285 blocked for more than 120 seconds.
[ 3021.797728]   Tainted: GW  OEL  4.8.0-25-generic #27-Ubuntu
[ 3021.797728] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this 
message.
[ 3021.797772] INFO: task kworker/1:2:303 blocked for more than 120 seconds.
[ 3021.797772]   Tainted: GW  OEL  4.8.0-25-generic #27-Ubuntu
[ 3021.797773] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this 
message.
[ 3021.797814] INFO: task kworker/2:2:350 blocked for more 

[Kernel-packages] [Bug 1632252] Re: linux autopkgtest kills sshd in testbed

[Martin Pitt]

With the QEMU runner this gets further, but it fails for me with

14:33:01 DEBUG| Running 'git clone 
https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/yakkety 
linux'
14:33:01 ERROR| [stderr] Cloning into 'linux'...
autopkgtest [16:02:54]: ERROR: timed out on command "..." (kind: test)
autopkgtest [16:02:54]: test ubuntu-regression-suite: ---]
Exception in thread copyin:
OSError: [Errno 28] No space left on device

Which bears the questions:

 (1) why is this timing out -- shouldn't failures like this cause an
immediate exit? ISTM that the test suite is very prone to just hanging
when anything goes wrong; can this be robustified somehow?

 (2) Is it really necessary to clone the entire kernel for the test?
This will both take ages (it is running through a proxy in the infra!)
and also take lots of disk space. If this just needs a few files, can
you get them individually instead? If this needs to compile some
helper/test binaries, can this happen during package build and you ship
them in linux-source, linux-tools-XX, or maybe the -dbgsym package?

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

Title:
  linux autopkgtest kills sshd in testbed

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Yakkety:
  Confirmed

Bug description:
  The current linux autopkgtests in yakkety are caught in an eternal
  "temporary failure" retry loop. They stopped timing out, but in the
  middle of the tests they kill sshd.

  Tail of test output:

  09:01:00 DEBUG| [stdout]   preparing apparmor_2.10.95-4ubuntu5.dsc... done
  09:01:00 DEBUG| [stdout] 
  09:01:40 ERROR| [stderr] Run libapparmor testsuite (with python3) ... ok
  09:01:40 ERROR| [stderr] test_parser_testsuite (__main__.ApparmorTestsuites)
  09:01:48 DEBUG| [stdout]   preparing apparmor_2.10.95-4ubuntu5.dsc... done
  09:01:48 DEBUG| [stdout] 
  09:19:27 ERROR| [stderr] Run parser regression tests ... ok
  09:19:27 ERROR| [stderr] test_regression_testsuite 
(__main__.ApparmorTestsuites)
  09:19:33 DEBUG| [stdout]   preparing apparmor_2.10.95-4ubuntu5.dsc... done
  09:19:33 DEBUG| [stdout] 
  Killed
  Killed
  Connection to 10.220.42.236 closed by remote host.
  Exit request sent.
  autopkgtest [09:24:42]: ERROR: testbed failure: testbed auxverb failed with 
exit code 255

  Console output during the test:

  Ubuntu 16.10 autopkgtest ttyS0

  autopkgtest login: [ 3512.996305] AppArmor: change_hat: Invalid input '^open'
  [ 3513.000678] AppArmor: change_hat: Invalid input '^'[ 3513.013965] 
AppArmor: change_hat: Invalid input, NULL hat and NULL magic
  [ 3513.019831] AppArmor: change_hat: Invalid input, NULL hat and NULL magic
  [ 3513.024872] AppArmor: change_hat: Invalid input '^open'AppArmor: 
change_hat: Invalid input '^'
  [ 3513.026539] AppArmor: change_hat: Invalid input '^'[ 3638.281408] Out of 
memory: Kill process 587 (rsyslogd) score 8 or sacrifice child
  [ 3638.284907] Killed process 587 (rsyslogd) total-vm:107460kB, 
anon-rss:67892kB, file-rss:2548kB, shmem-rss:0kB
  [ 3638.306990] Out of memory: Kill process 300 (systemd-journal) score 2 or 
sacrifice child
  [ 3638.308985] Killed process 300 (systemd-journal) total-vm:46184kB, 
anon-rss:460kB, file-rss:3752kB, shmem-rss:15412kB
  [ 3638.319337] Out of memory: Kill process 2636 (autotest-local) score 1 or 
sacrifice child
  [ 3638.320394] Killed process 10325 (autotest-local) total-vm:18092kB, 
anon-rss:7296kB, file-rss:3544kB, shmem-rss:0kB
  [ 3638.345419] Out of memory: Kill process 2636 (autotest-local) score 1 or 
sacrifice child
  [ 3638.347095] Killed process 2638 (autotest-local) total-vm:17836kB, 
anon-rss:7160kB, file-rss:1752kB, shmem-rss:0kB
  [ 3638.368917] Out of memory: Kill process 2636 (autotest-local) score 1 or 
sacrifice child
  [ 3638.369954] Killed process 2637 (autotest-local) total-vm:17836kB, 
anon-rss:7160kB, file-rss:1684kB, shmem-rss:0kB
  [ 3638.479196] Out of memory: Kill process 2636 (autotest-local) score 1 or 
sacrifice child
  [ 3638.482968] Killed process 2636 (autotest-local) total-vm:17836kB, 
anon-rss:7248kB, file-rss:5864kB, shmem-rss:0kB
  [ 3638.501050] Out of memory: Kill process 10619 (python) score 1 or 
sacrifice child
  [ 3638.502022] Killed process 14752 (make) total-vm:6052kB, anon-rss:196kB, 
file-rss:2032kB, shmem-rss:0kB
  [ 3638.511243] Out of memory: Kill process 10619 (python) score 1 or 
sacrifice child
  [ 3638.512224] Killed process 10619 (python) total-vm:16752kB, 
anon-rss:5836kB, file-rss:6148kB, shmem-rss:0kB
  [ 3638.525104] Out of memory: Kill process 3382 (python) score 0 or sacrifice 
child
  [ 3638.526060] Killed process 3382 (python) total-vm:21296kB, 
anon-rss:3732kB, file-rss:4080kB, shmem-rss:0kB
  [ 3638.545114] Out of memory: Kill process 553 (haveged) score 0 or sacrifice 
child
  [ 3638.546068] Killed process 553 (haveged) total-vm:8028kB, 

[Kernel-packages] [Bug 1632252] Re: linux autopkgtest kills sshd in testbed

[Martin Pitt]

I am able to reproduce this locally by using the "ssh" runner on a
manually started QEMU instance, instead of the "qemu" runner directly;
so this is much easier to investigate.

First this needs a small new feature in autopkgtest's ssh runner:
https://anonscm.debian.org/cgit/autopkgtest/autopkgtest.git/commit/?id=9aa6fdbef
. Easiest to just run autopkgtest from git (see reproducer below).

 * Take a standard autopkgtest yakkety image (autopkgtest-buildvm-
ubuntu-cloud) and run it in QEMU:

  qemu-system-x86_64 -enable-kvm -m 4096 -smp 2 -nographic -drive
file=path/to/autopkgtest-yakkety-amd64.img,if=virtio -net
nic,model=virtio -net user,hostfwd=tcp::22000-:22

 * Log in (ubuntu/ubuntu) and scp/install your host's ssh key info
~/.ssh/authorized_keys

 * Run the test:

   git clone https://anonscm.debian.org/git/autopkgtest/autopkgtest.git
   autopkgtest/runner/autopkgtest --testname ubuntu-regression-suite linux -- 
ssh -H localhost -l ubuntu -p 22000 --reboot --capability=isolation-machine 
--capability=revert --capability=revert-full-system

This takes an hour or so, then the test fails with "testbed failure:
testbed auxverb failed with exit code 255" and the console (in qemu) is
completely dead. So notably this fails later than on the production
infra (where it OOM-kills sshd during AppArmor tests), here it fails
right after

  12:39:40 DEBUG| [stdout] selftests: breakpoint_test [PASS]

but this could be variance due to the infra instances having more CPUs
and memory, or it's just an artifact of truncating the log earlier.

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

Title:
  linux autopkgtest kills sshd in testbed

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Yakkety:
  Confirmed

Bug description:
  The current linux autopkgtests in yakkety are caught in an eternal
  "temporary failure" retry loop. They stopped timing out, but in the
  middle of the tests they kill sshd.

  Tail of test output:

  09:01:00 DEBUG| [stdout]   preparing apparmor_2.10.95-4ubuntu5.dsc... done
  09:01:00 DEBUG| [stdout] 
  09:01:40 ERROR| [stderr] Run libapparmor testsuite (with python3) ... ok
  09:01:40 ERROR| [stderr] test_parser_testsuite (__main__.ApparmorTestsuites)
  09:01:48 DEBUG| [stdout]   preparing apparmor_2.10.95-4ubuntu5.dsc... done
  09:01:48 DEBUG| [stdout] 
  09:19:27 ERROR| [stderr] Run parser regression tests ... ok
  09:19:27 ERROR| [stderr] test_regression_testsuite 
(__main__.ApparmorTestsuites)
  09:19:33 DEBUG| [stdout]   preparing apparmor_2.10.95-4ubuntu5.dsc... done
  09:19:33 DEBUG| [stdout] 
  Killed
  Killed
  Connection to 10.220.42.236 closed by remote host.
  Exit request sent.
  autopkgtest [09:24:42]: ERROR: testbed failure: testbed auxverb failed with 
exit code 255

  Console output during the test:

  Ubuntu 16.10 autopkgtest ttyS0

  autopkgtest login: [ 3512.996305] AppArmor: change_hat: Invalid input '^open'
  [ 3513.000678] AppArmor: change_hat: Invalid input '^'[ 3513.013965] 
AppArmor: change_hat: Invalid input, NULL hat and NULL magic
  [ 3513.019831] AppArmor: change_hat: Invalid input, NULL hat and NULL magic
  [ 3513.024872] AppArmor: change_hat: Invalid input '^open'AppArmor: 
change_hat: Invalid input '^'
  [ 3513.026539] AppArmor: change_hat: Invalid input '^'[ 3638.281408] Out of 
memory: Kill process 587 (rsyslogd) score 8 or sacrifice child
  [ 3638.284907] Killed process 587 (rsyslogd) total-vm:107460kB, 
anon-rss:67892kB, file-rss:2548kB, shmem-rss:0kB
  [ 3638.306990] Out of memory: Kill process 300 (systemd-journal) score 2 or 
sacrifice child
  [ 3638.308985] Killed process 300 (systemd-journal) total-vm:46184kB, 
anon-rss:460kB, file-rss:3752kB, shmem-rss:15412kB
  [ 3638.319337] Out of memory: Kill process 2636 (autotest-local) score 1 or 
sacrifice child
  [ 3638.320394] Killed process 10325 (autotest-local) total-vm:18092kB, 
anon-rss:7296kB, file-rss:3544kB, shmem-rss:0kB
  [ 3638.345419] Out of memory: Kill process 2636 (autotest-local) score 1 or 
sacrifice child
  [ 3638.347095] Killed process 2638 (autotest-local) total-vm:17836kB, 
anon-rss:7160kB, file-rss:1752kB, shmem-rss:0kB
  [ 3638.368917] Out of memory: Kill process 2636 (autotest-local) score 1 or 
sacrifice child
  [ 3638.369954] Killed process 2637 (autotest-local) total-vm:17836kB, 
anon-rss:7160kB, file-rss:1684kB, shmem-rss:0kB
  [ 3638.479196] Out of memory: Kill process 2636 (autotest-local) score 1 or 
sacrifice child
  [ 3638.482968] Killed process 2636 (autotest-local) total-vm:17836kB, 
anon-rss:7248kB, file-rss:5864kB, shmem-rss:0kB
  [ 3638.501050] Out of memory: Kill process 10619 (python) score 1 or 
sacrifice child
  [ 3638.502022] Killed process 14752 (make) total-vm:6052kB, anon-rss:196kB, 
file-rss:2032kB, shmem-rss:0kB
  [ 3638.511243] Out of memory: Kill process 10619 (python) score 1 or 
sacrifice child
  [ 3638.512224] 

[Kernel-packages] [Bug 1632252] Re: linux autopkgtest kills sshd in testbed

[Martin Pitt]

After the hang, even SysRq doesn't work (I tried "sync" with Ctrl+A b s
-- Ctrl+A b is the QEMU console key combo for sending SysRq, see Ctrl-A
?)

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

Title:
  linux autopkgtest kills sshd in testbed

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Yakkety:
  Confirmed

Bug description:
  The current linux autopkgtests in yakkety are caught in an eternal
  "temporary failure" retry loop. They stopped timing out, but in the
  middle of the tests they kill sshd.

  Tail of test output:

  09:01:00 DEBUG| [stdout]   preparing apparmor_2.10.95-4ubuntu5.dsc... done
  09:01:00 DEBUG| [stdout] 
  09:01:40 ERROR| [stderr] Run libapparmor testsuite (with python3) ... ok
  09:01:40 ERROR| [stderr] test_parser_testsuite (__main__.ApparmorTestsuites)
  09:01:48 DEBUG| [stdout]   preparing apparmor_2.10.95-4ubuntu5.dsc... done
  09:01:48 DEBUG| [stdout] 
  09:19:27 ERROR| [stderr] Run parser regression tests ... ok
  09:19:27 ERROR| [stderr] test_regression_testsuite 
(__main__.ApparmorTestsuites)
  09:19:33 DEBUG| [stdout]   preparing apparmor_2.10.95-4ubuntu5.dsc... done
  09:19:33 DEBUG| [stdout] 
  Killed
  Killed
  Connection to 10.220.42.236 closed by remote host.
  Exit request sent.
  autopkgtest [09:24:42]: ERROR: testbed failure: testbed auxverb failed with 
exit code 255

  Console output during the test:

  Ubuntu 16.10 autopkgtest ttyS0

  autopkgtest login: [ 3512.996305] AppArmor: change_hat: Invalid input '^open'
  [ 3513.000678] AppArmor: change_hat: Invalid input '^'[ 3513.013965] 
AppArmor: change_hat: Invalid input, NULL hat and NULL magic
  [ 3513.019831] AppArmor: change_hat: Invalid input, NULL hat and NULL magic
  [ 3513.024872] AppArmor: change_hat: Invalid input '^open'AppArmor: 
change_hat: Invalid input '^'
  [ 3513.026539] AppArmor: change_hat: Invalid input '^'[ 3638.281408] Out of 
memory: Kill process 587 (rsyslogd) score 8 or sacrifice child
  [ 3638.284907] Killed process 587 (rsyslogd) total-vm:107460kB, 
anon-rss:67892kB, file-rss:2548kB, shmem-rss:0kB
  [ 3638.306990] Out of memory: Kill process 300 (systemd-journal) score 2 or 
sacrifice child
  [ 3638.308985] Killed process 300 (systemd-journal) total-vm:46184kB, 
anon-rss:460kB, file-rss:3752kB, shmem-rss:15412kB
  [ 3638.319337] Out of memory: Kill process 2636 (autotest-local) score 1 or 
sacrifice child
  [ 3638.320394] Killed process 10325 (autotest-local) total-vm:18092kB, 
anon-rss:7296kB, file-rss:3544kB, shmem-rss:0kB
  [ 3638.345419] Out of memory: Kill process 2636 (autotest-local) score 1 or 
sacrifice child
  [ 3638.347095] Killed process 2638 (autotest-local) total-vm:17836kB, 
anon-rss:7160kB, file-rss:1752kB, shmem-rss:0kB
  [ 3638.368917] Out of memory: Kill process 2636 (autotest-local) score 1 or 
sacrifice child
  [ 3638.369954] Killed process 2637 (autotest-local) total-vm:17836kB, 
anon-rss:7160kB, file-rss:1684kB, shmem-rss:0kB
  [ 3638.479196] Out of memory: Kill process 2636 (autotest-local) score 1 or 
sacrifice child
  [ 3638.482968] Killed process 2636 (autotest-local) total-vm:17836kB, 
anon-rss:7248kB, file-rss:5864kB, shmem-rss:0kB
  [ 3638.501050] Out of memory: Kill process 10619 (python) score 1 or 
sacrifice child
  [ 3638.502022] Killed process 14752 (make) total-vm:6052kB, anon-rss:196kB, 
file-rss:2032kB, shmem-rss:0kB
  [ 3638.511243] Out of memory: Kill process 10619 (python) score 1 or 
sacrifice child
  [ 3638.512224] Killed process 10619 (python) total-vm:16752kB, 
anon-rss:5836kB, file-rss:6148kB, shmem-rss:0kB
  [ 3638.525104] Out of memory: Kill process 3382 (python) score 0 or sacrifice 
child
  [ 3638.526060] Killed process 3382 (python) total-vm:21296kB, 
anon-rss:3732kB, file-rss:4080kB, shmem-rss:0kB
  [ 3638.545114] Out of memory: Kill process 553 (haveged) score 0 or sacrifice 
child
  [ 3638.546068] Killed process 553 (haveged) total-vm:8028kB, anon-rss:4780kB, 
file-rss:1468kB, shmem-rss:0kB
  [ 3638.573449] Out of memory: Kill process 10373 (sshd) score 0 or sacrifice 
child
  [ 3638.574353] Killed process 11430 (sshd) total-vm:1kB, anon-rss:1712kB, 
file-rss:2960kB, shmem-rss:0kB
  [ 3638.591696] Out of memory: Kill process 10373 (sshd) score 0 or sacrifice 
child
  [ 3638.595493] Killed process 10373 (sshd) total-vm:13460kB, anon-rss:752kB, 
file-rss:5476kB, shmem-rss:4kB
  [ 3638.605938] Out of memory: Kill process 898 (sshd) score 0 or sacrifice 
child
  [ 3638.607617] Killed process 911 (sshd) total-vm:13804kB, anon-rss:1120kB, 
file-rss:3184kB, shmem-rss:0kB
  [ 3638.626950] Out of memory: Kill process 898 (sshd) score 0 or sacrifice 
child
  [ 3638.627839] Killed process 898 (sshd) total-vm:13460kB, anon-rss:744kB, 
file-rss:5436kB, shmem-rss:4kB
  [ 3638.641735] Out of memory: Kill process 900 (systemd) score 0 or sacrifice 
child
  [ 3638.643448] Killed process 901 

[Kernel-packages] [Bug 1626436] Re: [4.8 regression] boot has become very slow

[Martin Pitt]

Confirmed with 4.8.0-040800.201610022031 from http://kernel.ubuntu.com
/~kernel-ppa/mainline/v4.8/

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

Title:
  [4.8 regression] boot has become very slow

Status in linux package in Ubuntu:
  Triaged

Bug description:
  With yakkety's recent update from linux 4.4 to 4.8 booting has become
  a lot slower. It's not one service in particular, but without "quiet"
  and "splash" you can now easily read every single line instead of that
  whole wall of text zipping by. It now takes over 20s instead of ~10
  seconds to boot.

  This is even more dramatic when factoring out the recent boot hang of
  NetworkManager (bug 1622893) and disabling lightdm:

sudo systemctl mask NetworkManager NetworkManager-wait-online
  lightdm

  then booting with 4.4 takes 1.5s and with 4.8 19.5s (!).

  Some excerps from systemd-analyze blame:

  4.4:
 474ms postfix@-.service
 395ms lxd-containers.service
 305ms networking.service

  4.8:
4.578s postfix@-.service
7.300s lxd-containers.service
6.285s networking.service

  I attach the full outputs of critical-chain and analyze for 4.4 and
  4.8 for reference.

  
  This is much less noticeable in the running system. There is no immediate 
feeling of sluggishness (although my system is by and large idle).

  I compared the time of sbuilding colord under similar circumstances
  (-j4, building on tmpfs, thus no hard disk delays; running with fully
  pre-loaded apt-cacher-ng thus no random network delays), and with 4.4
  it takes 6.5 minutes and with 4.8 it takes 7.5. So that got a bit
  slower, but much less dramatically than during boot, so this is either
  happening when a lot of processes run in parallel, or is perhaps
  related to setting up cgroups.

  One thing I noticed that during sbuild in 4.8 "top" shows ridiculous
  loads (~ 250) under 4.8, while it's around 4 or 5 under 4.8. But that
  doesn't reflect in actual sluggishness, so this might be just an
  unrelated bug.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: linux-image-4.8.0-11-generic 4.8.0-11.12
  ProcVersionSignature: Ubuntu 4.8.0-11.12-generic 4.8.0-rc6
  Uname: Linux 4.8.0-11-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   martin 3049 F...m pulseaudio
   /dev/snd/pcmC0D0p:   martin 3049 F...m pulseaudio
   /dev/snd/controlC0:  martin 3049 F pulseaudio
  Date: Thu Sep 22 09:42:56 2016
  EcryptfsInUse: Yes
  MachineType: LENOVO 2324CTO
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.8.0-11-generic.efi.signed 
root=UUID=f86539b0-3a1b-4372-83b0-acdd029ade68 ro rootflags=subvol=@ 
systemd.debug-shell
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-11-generic N/A
   linux-backports-modules-4.8.0-11-generic  N/A
   linux-firmware1.161
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/09/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G2ET95WW (2.55 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2324CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: 0B98401 Pro
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG2ET95WW(2.55):bd07/09/2013:svnLENOVO:pn2324CTO:pvrThinkPadX230:rvnLENOVO:rn2324CTO:rvr0B98401Pro:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 2324CTO
  dmi.product.version: ThinkPad X230
  dmi.sys.vendor: LENOVO

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1632252] Re: linux autopkgtest kills sshd in testbed

[Martin Pitt]

It is still happening. I was running journalctl -f on the testbed while
it ran, and was able to copy the last 9000 lines of scrollback from
tmux.

** Attachment added: "journal"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1632252/+attachment/4762321/+files/journal.txt

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

Title:
  linux autopkgtest kills sshd in testbed

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Yakkety:
  Confirmed

Bug description:
  The current linux autopkgtests in yakkety are caught in an eternal
  "temporary failure" retry loop. They stopped timing out, but in the
  middle of the tests they kill sshd.

  Tail of test output:

  09:01:00 DEBUG| [stdout]   preparing apparmor_2.10.95-4ubuntu5.dsc... done
  09:01:00 DEBUG| [stdout] 
  09:01:40 ERROR| [stderr] Run libapparmor testsuite (with python3) ... ok
  09:01:40 ERROR| [stderr] test_parser_testsuite (__main__.ApparmorTestsuites)
  09:01:48 DEBUG| [stdout]   preparing apparmor_2.10.95-4ubuntu5.dsc... done
  09:01:48 DEBUG| [stdout] 
  09:19:27 ERROR| [stderr] Run parser regression tests ... ok
  09:19:27 ERROR| [stderr] test_regression_testsuite 
(__main__.ApparmorTestsuites)
  09:19:33 DEBUG| [stdout]   preparing apparmor_2.10.95-4ubuntu5.dsc... done
  09:19:33 DEBUG| [stdout] 
  Killed
  Killed
  Connection to 10.220.42.236 closed by remote host.
  Exit request sent.
  autopkgtest [09:24:42]: ERROR: testbed failure: testbed auxverb failed with 
exit code 255

  Console output during the test:

  Ubuntu 16.10 autopkgtest ttyS0

  autopkgtest login: [ 3512.996305] AppArmor: change_hat: Invalid input '^open'
  [ 3513.000678] AppArmor: change_hat: Invalid input '^'[ 3513.013965] 
AppArmor: change_hat: Invalid input, NULL hat and NULL magic
  [ 3513.019831] AppArmor: change_hat: Invalid input, NULL hat and NULL magic
  [ 3513.024872] AppArmor: change_hat: Invalid input '^open'AppArmor: 
change_hat: Invalid input '^'
  [ 3513.026539] AppArmor: change_hat: Invalid input '^'[ 3638.281408] Out of 
memory: Kill process 587 (rsyslogd) score 8 or sacrifice child
  [ 3638.284907] Killed process 587 (rsyslogd) total-vm:107460kB, 
anon-rss:67892kB, file-rss:2548kB, shmem-rss:0kB
  [ 3638.306990] Out of memory: Kill process 300 (systemd-journal) score 2 or 
sacrifice child
  [ 3638.308985] Killed process 300 (systemd-journal) total-vm:46184kB, 
anon-rss:460kB, file-rss:3752kB, shmem-rss:15412kB
  [ 3638.319337] Out of memory: Kill process 2636 (autotest-local) score 1 or 
sacrifice child
  [ 3638.320394] Killed process 10325 (autotest-local) total-vm:18092kB, 
anon-rss:7296kB, file-rss:3544kB, shmem-rss:0kB
  [ 3638.345419] Out of memory: Kill process 2636 (autotest-local) score 1 or 
sacrifice child
  [ 3638.347095] Killed process 2638 (autotest-local) total-vm:17836kB, 
anon-rss:7160kB, file-rss:1752kB, shmem-rss:0kB
  [ 3638.368917] Out of memory: Kill process 2636 (autotest-local) score 1 or 
sacrifice child
  [ 3638.369954] Killed process 2637 (autotest-local) total-vm:17836kB, 
anon-rss:7160kB, file-rss:1684kB, shmem-rss:0kB
  [ 3638.479196] Out of memory: Kill process 2636 (autotest-local) score 1 or 
sacrifice child
  [ 3638.482968] Killed process 2636 (autotest-local) total-vm:17836kB, 
anon-rss:7248kB, file-rss:5864kB, shmem-rss:0kB
  [ 3638.501050] Out of memory: Kill process 10619 (python) score 1 or 
sacrifice child
  [ 3638.502022] Killed process 14752 (make) total-vm:6052kB, anon-rss:196kB, 
file-rss:2032kB, shmem-rss:0kB
  [ 3638.511243] Out of memory: Kill process 10619 (python) score 1 or 
sacrifice child
  [ 3638.512224] Killed process 10619 (python) total-vm:16752kB, 
anon-rss:5836kB, file-rss:6148kB, shmem-rss:0kB
  [ 3638.525104] Out of memory: Kill process 3382 (python) score 0 or sacrifice 
child
  [ 3638.526060] Killed process 3382 (python) total-vm:21296kB, 
anon-rss:3732kB, file-rss:4080kB, shmem-rss:0kB
  [ 3638.545114] Out of memory: Kill process 553 (haveged) score 0 or sacrifice 
child
  [ 3638.546068] Killed process 553 (haveged) total-vm:8028kB, anon-rss:4780kB, 
file-rss:1468kB, shmem-rss:0kB
  [ 3638.573449] Out of memory: Kill process 10373 (sshd) score 0 or sacrifice 
child
  [ 3638.574353] Killed process 11430 (sshd) total-vm:1kB, anon-rss:1712kB, 
file-rss:2960kB, shmem-rss:0kB
  [ 3638.591696] Out of memory: Kill process 10373 (sshd) score 0 or sacrifice 
child
  [ 3638.595493] Killed process 10373 (sshd) total-vm:13460kB, anon-rss:752kB, 
file-rss:5476kB, shmem-rss:4kB
  [ 3638.605938] Out of memory: Kill process 898 (sshd) score 0 or sacrifice 
child
  [ 3638.607617] Killed process 911 (sshd) total-vm:13804kB, anon-rss:1120kB, 
file-rss:3184kB, shmem-rss:0kB
  [ 3638.626950] Out of memory: Kill process 898 (sshd) score 0 or sacrifice 
child
  [ 3638.627839] Killed process 898 (sshd) total-vm:13460kB, anon-rss:744kB, 
file-rss:5436kB, 

[Kernel-packages] [Bug 1624540] Re: please have lxd recommend zfs

[Martin Pitt]

> The udev event is going to fire before the pool is imported.

So how does a pool get imported, what triggers that if it's not block
devices appearing? Whatever does that import, couldn't that start
zed.service then instead of the udev rule?

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1624540

Title:
  please have lxd recommend zfs

Status in lxd package in Ubuntu:
  Incomplete
Status in zfs-linux package in Ubuntu:
  Confirmed

Bug description:
  Since ZFS is now in Main (Bug #1532198), LXD should recommend the ZFS
  userspace package, such that 'sudo lxd init' just works.

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1630069] Re: Regression tests can not detect binfmt_elf mmpa semantic change

[Martin Pitt]

Hello John, or anyone else affected,

Accepted apparmor into xenial-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/apparmor/2.10.95-0ubuntu2.5 in a
few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed.  Your feedback will aid us getting this update
out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, and change the tag
from verification-needed to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed.  In either case, details of your testing will help
us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Changed in: apparmor (Ubuntu Xenial)
   Status: In Progress => Fix Committed

** Tags added: verification-needed

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

Title:
  Regression tests can not detect binfmt_elf mmpa semantic change

Status in AppArmor:
  Fix Committed
Status in apparmor package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Fix Released
Status in apparmor source package in Xenial:
  Fix Committed
Status in linux source package in Xenial:
  New
Status in apparmor source package in Yakkety:
  Won't Fix
Status in linux source package in Yakkety:
  Fix Released

Bug description:
  == apparmor SRU ==

  [Impact]

   * The exec_stack.sh regression test fails due to a behavior change in 4.8
     kernels from this patch:

     commit 9f834ec18defc369d73ccf9e87a2790bfa05bf46
     Author: Linus Torvalds 
     Date: Mon Aug 22 16:41:46 2016 -0700

     binfmt_elf: switch to new creds when switching to new mm

   * The regression tests were fixed for this kernel change but they were fixed
     in a way that always assumed that kernel change is present. They should 
have
     been adjusted so that they act differently according to whether or not the
     kernel change is present (it is a change that could end up being backported
     through the stable trees).

  [Test Case]

   $ apt-get source apparmor # make sure this fetches the new apparmor source
   $ sudo apt-get install libapparmor-dev
   $ cd tests/regression/apparmor
   $ make USE_SYSTEM=1
   $ sudo bash exec_stack.sh

   The previous command should result in no output and return value of
  0.

  [Regression Potential]

   * This is an extremely low risk change since it only touches regression
     testing code that is not user-facing.

  [Other]

   * Fixed in upstream lp:apparmor tree:

     https://bazaar.launchpad.net/~apparmor-
  dev/apparmor/master/revision/3558

  == Original description ==

  The regression tests are currently hard coded to the semantics of mmap
  in binfmt_elf

  With the recent upstream commit
  9f834ec18defc369d73ccf9e87a2790bfa05bf46 the cred used for the mmap
  changed resulting in test failures. The tests have been patched for
  this change but it results in the test breaking for everyone using
  upstream releases against pre 4.8 kernels.

To manage notifications about this bug go to:
https://bugs.launchpad.net/apparmor/+bug/1630069/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1632252] [NEW] linux autopkgtest kills sshd in testbed

[Martin Pitt]

Public bug reported:

The current linux autopkgtests in yakkety are caught in an eternal
"temporary failure" retry loop. They stopped timing out, but in the
middle of the tests they kill sshd.

Tail of test output:

09:01:00 DEBUG| [stdout]   preparing apparmor_2.10.95-4ubuntu5.dsc... done
09:01:00 DEBUG| [stdout] 
09:01:40 ERROR| [stderr] Run libapparmor testsuite (with python3) ... ok
09:01:40 ERROR| [stderr] test_parser_testsuite (__main__.ApparmorTestsuites)
09:01:48 DEBUG| [stdout]   preparing apparmor_2.10.95-4ubuntu5.dsc... done
09:01:48 DEBUG| [stdout] 
09:19:27 ERROR| [stderr] Run parser regression tests ... ok
09:19:27 ERROR| [stderr] test_regression_testsuite (__main__.ApparmorTestsuites)
09:19:33 DEBUG| [stdout]   preparing apparmor_2.10.95-4ubuntu5.dsc... done
09:19:33 DEBUG| [stdout] 
Killed
Killed
Connection to 10.220.42.236 closed by remote host.
Exit request sent.
autopkgtest [09:24:42]: ERROR: testbed failure: testbed auxverb failed with 
exit code 255

Console output during the test:

Ubuntu 16.10 autopkgtest ttyS0

autopkgtest login: [ 3512.996305] AppArmor: change_hat: Invalid input '^open'
[ 3513.000678] AppArmor: change_hat: Invalid input '^'[ 3513.013965] AppArmor: 
change_hat: Invalid input, NULL hat and NULL magic
[ 3513.019831] AppArmor: change_hat: Invalid input, NULL hat and NULL magic
[ 3513.024872] AppArmor: change_hat: Invalid input '^open'AppArmor: change_hat: 
Invalid input '^'
[ 3513.026539] AppArmor: change_hat: Invalid input '^'[ 3638.281408] Out of 
memory: Kill process 587 (rsyslogd) score 8 or sacrifice child
[ 3638.284907] Killed process 587 (rsyslogd) total-vm:107460kB, 
anon-rss:67892kB, file-rss:2548kB, shmem-rss:0kB
[ 3638.306990] Out of memory: Kill process 300 (systemd-journal) score 2 or 
sacrifice child
[ 3638.308985] Killed process 300 (systemd-journal) total-vm:46184kB, 
anon-rss:460kB, file-rss:3752kB, shmem-rss:15412kB
[ 3638.319337] Out of memory: Kill process 2636 (autotest-local) score 1 or 
sacrifice child
[ 3638.320394] Killed process 10325 (autotest-local) total-vm:18092kB, 
anon-rss:7296kB, file-rss:3544kB, shmem-rss:0kB
[ 3638.345419] Out of memory: Kill process 2636 (autotest-local) score 1 or 
sacrifice child
[ 3638.347095] Killed process 2638 (autotest-local) total-vm:17836kB, 
anon-rss:7160kB, file-rss:1752kB, shmem-rss:0kB
[ 3638.368917] Out of memory: Kill process 2636 (autotest-local) score 1 or 
sacrifice child
[ 3638.369954] Killed process 2637 (autotest-local) total-vm:17836kB, 
anon-rss:7160kB, file-rss:1684kB, shmem-rss:0kB
[ 3638.479196] Out of memory: Kill process 2636 (autotest-local) score 1 or 
sacrifice child
[ 3638.482968] Killed process 2636 (autotest-local) total-vm:17836kB, 
anon-rss:7248kB, file-rss:5864kB, shmem-rss:0kB
[ 3638.501050] Out of memory: Kill process 10619 (python) score 1 or sacrifice 
child
[ 3638.502022] Killed process 14752 (make) total-vm:6052kB, anon-rss:196kB, 
file-rss:2032kB, shmem-rss:0kB
[ 3638.511243] Out of memory: Kill process 10619 (python) score 1 or sacrifice 
child
[ 3638.512224] Killed process 10619 (python) total-vm:16752kB, anon-rss:5836kB, 
file-rss:6148kB, shmem-rss:0kB
[ 3638.525104] Out of memory: Kill process 3382 (python) score 0 or sacrifice 
child
[ 3638.526060] Killed process 3382 (python) total-vm:21296kB, anon-rss:3732kB, 
file-rss:4080kB, shmem-rss:0kB
[ 3638.545114] Out of memory: Kill process 553 (haveged) score 0 or sacrifice 
child
[ 3638.546068] Killed process 553 (haveged) total-vm:8028kB, anon-rss:4780kB, 
file-rss:1468kB, shmem-rss:0kB
[ 3638.573449] Out of memory: Kill process 10373 (sshd) score 0 or sacrifice 
child
[ 3638.574353] Killed process 11430 (sshd) total-vm:1kB, anon-rss:1712kB, 
file-rss:2960kB, shmem-rss:0kB
[ 3638.591696] Out of memory: Kill process 10373 (sshd) score 0 or sacrifice 
child
[ 3638.595493] Killed process 10373 (sshd) total-vm:13460kB, anon-rss:752kB, 
file-rss:5476kB, shmem-rss:4kB
[ 3638.605938] Out of memory: Kill process 898 (sshd) score 0 or sacrifice child
[ 3638.607617] Killed process 911 (sshd) total-vm:13804kB, anon-rss:1120kB, 
file-rss:3184kB, shmem-rss:0kB
[ 3638.626950] Out of memory: Kill process 898 (sshd) score 0 or sacrifice child
[ 3638.627839] Killed process 898 (sshd) total-vm:13460kB, anon-rss:744kB, 
file-rss:5436kB, shmem-rss:4kB
[ 3638.641735] Out of memory: Kill process 900 (systemd) score 0 or sacrifice 
child
[ 3638.643448] Killed process 901 ((sd-pam)) total-vm:10360kB, anon-rss:1300kB, 
file-rss:48kB, shmem-rss:0kB
[ 3638.652509] Out of memory: Kill process 900 (systemd) score 0 or sacrifice 
child
[ 3638.653656] Killed process 900 (systemd) total-vm:9288kB, anon-rss:640kB, 
file-rss:4928kB, shmem-rss:0kB
[ 3638.665935] Out of memory: Kill process 11431 (bash) score 0 or sacrifice 
child
[ 3638.666823] Killed process 10819 (dmesg) total-vm:4236kB, anon-rss:84kB, 
file-rss:880kB, shmem-rss:0kB
[ 3638.675625] Out of memory: Kill process 11431 (bash) score 0 or sacrifice 
child
[ 3638.676541] Killed process 

[Kernel-packages] [Bug 1589905] Update Released

[Martin Pitt]

The verification of the Stable Release Update for linux-firmware has
completed successfully and the package has now been released to
-updates.  Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/1589905

Title:
  Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter [168c:003e]
  is not supported

Status in HWE Next:
  Triaged
Status in linux-firmware package in Ubuntu:
  Fix Released
Status in linux-firmware source package in Xenial:
  Fix Released
Status in linux-firmware source package in Yakkety:
  Fix Released

Bug description:
  Firmware for this card isn't in the current linux-firmware package.
  Latest upstream firmware is also tested but doesn't work either.

  The only working firmware is extracted from Windows driver. By
  comparing the md5sum, the only different file is
  ath10k/QCA6174/hw3.0/board.bin (upstream is cb37c6, and Windows is
  df5ba1), we need Qualcomm to upstream the file to fix this issue.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1589905/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1626436] Re: [4.8 regression] boot has become very slow

[Martin Pitt]

This could potentially be related to changes with cgroups -- creating
them did not cause any uevent in 4.4, but with 4.8 they do:

  sudo systemctl stop systemd-timesyncd
  udevadm monitor  -k  # in another terminal
  sudo systemctl start systemd-timesyncd

KERNEL[393.260769] add  
/kernel/slab/:atA-192/cgroup/dentry(1623:systemd-timesyncd.service) (cgroup)
KERNEL[393.261031] add  
/kernel/slab/inode_cache/cgroup/inode_cache(1623:systemd-timesyncd.service) 
(cgroup)
KERNEL[393.261850] add  
/kernel/slab/shmem_inode_cache/cgroup/shmem_inode_cache(1623:systemd-timesyncd.service)
 (cgroup)
KERNEL[393.262358] add  
/kernel/slab/:tA-192/cgroup/cred_jar(1623:systemd-timesyncd.service) 
(cgroup)
KERNEL[393.262636] add  
/kernel/slab/proc_inode_cache/cgroup/proc_inode_cache(1623:systemd-timesyncd.service)
 (cgroup)
KERNEL[393.452990] add  
/kernel/slab/:tA-0001024/cgroup/mm_struct(1623:systemd-timesyncd.service) 
(cgroup)
KERNEL[393.453082] add  
/kernel/slab/:tA-200/cgroup/vm_area_struct(1623:systemd-timesyncd.service) 
(cgroup)
KERNEL[393.453251] add  
/kernel/slab/:tA-064/cgroup/anon_vma_chain(1623:systemd-timesyncd.service) 
(cgroup)
KERNEL[393.453369] add  
/kernel/slab/anon_vma/cgroup/anon_vma(1623:systemd-timesyncd.service) (cgroup)
KERNEL[393.456909] add  
/kernel/slab/sock_inode_cache/cgroup/sock_inode_cache(1623:systemd-timesyncd.service)
 (cgroup)
KERNEL[393.457974] add  
/kernel/slab/:t-256/cgroup/kmalloc-256(1623:systemd-timesyncd.service) 
(cgroup)
KERNEL[393.458205] add  
/kernel/slab/:t-512/cgroup/kmalloc-512(1623:systemd-timesyncd.service) 
(cgroup)
KERNEL[393.460718] add  
/kernel/slab/:tA-0003648/cgroup/task_struct(1623:systemd-timesyncd.service) 
(cgroup)
KERNEL[393.462292] add  
/kernel/slab/:tA-128/cgroup/pid(1623:systemd-timesyncd.service) (cgroup)
KERNEL[393.465448] add  
/kernel/slab/:t-0001024/cgroup/kmalloc-1024(1623:systemd-timesyncd.service) 
(cgroup)

Which means that there will be a corresponding number of udev workers
running. At boot there is a *lot* of cgroup action due to lots of
services being started, while this is relatively quiet during runtime.
This is consistent with a slow boot but normal behaviour/feeling at
runtime.

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

Title:
  [4.8 regression] boot has become very slow

Status in linux package in Ubuntu:
  Triaged

Bug description:
  With yakkety's recent update from linux 4.4 to 4.8 booting has become
  a lot slower. It's not one service in particular, but without "quiet"
  and "splash" you can now easily read every single line instead of that
  whole wall of text zipping by. It now takes over 20s instead of ~10
  seconds to boot.

  This is even more dramatic when factoring out the recent boot hang of
  NetworkManager (bug 1622893) and disabling lightdm:

sudo systemctl mask NetworkManager NetworkManager-wait-online
  lightdm

  then booting with 4.4 takes 1.5s and with 4.8 19.5s (!).

  Some excerps from systemd-analyze blame:

  4.4:
 474ms postfix@-.service
 395ms lxd-containers.service
 305ms networking.service

  4.8:
4.578s postfix@-.service
7.300s lxd-containers.service
6.285s networking.service

  I attach the full outputs of critical-chain and analyze for 4.4 and
  4.8 for reference.

  
  This is much less noticeable in the running system. There is no immediate 
feeling of sluggishness (although my system is by and large idle).

  I compared the time of sbuilding colord under similar circumstances
  (-j4, building on tmpfs, thus no hard disk delays; running with fully
  pre-loaded apt-cacher-ng thus no random network delays), and with 4.4
  it takes 6.5 minutes and with 4.8 it takes 7.5. So that got a bit
  slower, but much less dramatically than during boot, so this is either
  happening when a lot of processes run in parallel, or is perhaps
  related to setting up cgroups.

  One thing I noticed that during sbuild in 4.8 "top" shows ridiculous
  loads (~ 250) under 4.8, while it's around 4 or 5 under 4.8. But that
  doesn't reflect in actual sluggishness, so this might be just an
  unrelated bug.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: linux-image-4.8.0-11-generic 4.8.0-11.12
  ProcVersionSignature: Ubuntu 4.8.0-11.12-generic 4.8.0-rc6
  Uname: Linux 4.8.0-11-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   martin 3049 F...m pulseaudio
   /dev/snd/pcmC0D0p:   martin 3049 F...m pulseaudio
   /dev/snd/controlC0:  martin 3049 F pulseaudio
  Date: Thu Sep 22 09:42:56 2016
  EcryptfsInUse: Yes
  MachineType: LENOVO 2324CTO
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   

[Kernel-packages] [Bug 1626436] Re: [4.8 regression] boot has become very slow

[Martin Pitt]

For the record, I tried Joseph's test bisect kernel in bug 1627108, and
this does not fix it, so this is not a duplicate of bug 1627108:

4.4.0-9136 (previous yakkety): 2.849s (kernel) + 4.639s (userspace)
4.8.0-19 (current yakkety): 5.145s (kernel) + 11.825s (userspace)
4.7.0-040700rc3 (from Joseph): 3.735s (kernel) + 14.810s (userspace)

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

Title:
  [4.8 regression] boot has become very slow

Status in linux package in Ubuntu:
  Triaged

Bug description:
  With yakkety's recent update from linux 4.4 to 4.8 booting has become
  a lot slower. It's not one service in particular, but without "quiet"
  and "splash" you can now easily read every single line instead of that
  whole wall of text zipping by. It now takes over 20s instead of ~10
  seconds to boot.

  This is even more dramatic when factoring out the recent boot hang of
  NetworkManager (bug 1622893) and disabling lightdm:

sudo systemctl mask NetworkManager NetworkManager-wait-online
  lightdm

  then booting with 4.4 takes 1.5s and with 4.8 19.5s (!).

  Some excerps from systemd-analyze blame:

  4.4:
 474ms postfix@-.service
 395ms lxd-containers.service
 305ms networking.service

  4.8:
4.578s postfix@-.service
7.300s lxd-containers.service
6.285s networking.service

  I attach the full outputs of critical-chain and analyze for 4.4 and
  4.8 for reference.

  
  This is much less noticeable in the running system. There is no immediate 
feeling of sluggishness (although my system is by and large idle).

  I compared the time of sbuilding colord under similar circumstances
  (-j4, building on tmpfs, thus no hard disk delays; running with fully
  pre-loaded apt-cacher-ng thus no random network delays), and with 4.4
  it takes 6.5 minutes and with 4.8 it takes 7.5. So that got a bit
  slower, but much less dramatically than during boot, so this is either
  happening when a lot of processes run in parallel, or is perhaps
  related to setting up cgroups.

  One thing I noticed that during sbuild in 4.8 "top" shows ridiculous
  loads (~ 250) under 4.8, while it's around 4 or 5 under 4.8. But that
  doesn't reflect in actual sluggishness, so this might be just an
  unrelated bug.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: linux-image-4.8.0-11-generic 4.8.0-11.12
  ProcVersionSignature: Ubuntu 4.8.0-11.12-generic 4.8.0-rc6
  Uname: Linux 4.8.0-11-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   martin 3049 F...m pulseaudio
   /dev/snd/pcmC0D0p:   martin 3049 F...m pulseaudio
   /dev/snd/controlC0:  martin 3049 F pulseaudio
  Date: Thu Sep 22 09:42:56 2016
  EcryptfsInUse: Yes
  MachineType: LENOVO 2324CTO
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.8.0-11-generic.efi.signed 
root=UUID=f86539b0-3a1b-4372-83b0-acdd029ade68 ro rootflags=subvol=@ 
systemd.debug-shell
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-11-generic N/A
   linux-backports-modules-4.8.0-11-generic  N/A
   linux-firmware1.161
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/09/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G2ET95WW (2.55 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2324CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: 0B98401 Pro
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG2ET95WW(2.55):bd07/09/2013:svnLENOVO:pn2324CTO:pvrThinkPadX230:rvnLENOVO:rn2324CTO:rvr0B98401Pro:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 2324CTO
  dmi.product.version: ThinkPad X230
  dmi.sys.vendor: LENOVO

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1627108] Re: X1Carbon comes to a crawl during high CPU usage tasks

[Martin Pitt]

FTR, I tested #29 which works for Omer, but not for me, so bug 1626436
is not a duplicate.

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

Title:
  X1Carbon comes to a crawl during high CPU usage tasks

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Yakkety:
  In Progress

Bug description:
  My X1Carbon becomes quite laggy, the cursor hangs for a few seconds
  and then resumes while my system is compiling some code, or lets says
  PyCharm is indexing things or Android Studio is compiling some code. I
  was using 4.4 on Xenial a few days ago and everything was working just
  fine. Installed Yakkety and this issue happens.

  I will downgrade the kernel and see if that mitigates the issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: linux-image-4.8.0-15-generic 4.8.0-15.16
  ProcVersionSignature: Ubuntu 4.8.0-15.16-generic 4.8.0-rc7
  Uname: Linux 4.8.0-15-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC1D0p:   om26er 3390 F...m pulseaudio
   /dev/snd/controlC1:  om26er 3390 F pulseaudio
   /dev/snd/controlC0:  om26er 3390 F pulseaudio
  CurrentDesktop: Unity
  Date: Fri Sep 23 21:40:34 2016
  HibernationDevice: RESUME=UUID=a92c85ab-cca3-4afc-abf1-3516f193129e
  InstallationDate: Installed on 2016-09-21 (1 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160921)
  MachineType: LENOVO 20BSCTO1WW
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-15-generic.efi.signed 
root=UUID=01b0a4a0-d791-46e8-a212-1f769cff3a4b ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-15-generic N/A
   linux-backports-modules-4.8.0-15-generic  N/A
   linux-firmware1.161
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/13/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N14ET32W (1.10 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20BSCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN14ET32W(1.10):bd08/13/2015:svnLENOVO:pn20BSCTO1WW:pvrThinkPadX1Carbon3rd:rvnLENOVO:rn20BSCTO1WW:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.name: 20BSCTO1WW
  dmi.product.version: ThinkPad X1 Carbon 3rd
  dmi.sys.vendor: LENOVO

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1626466] Re: [Yakkety] suspend fail and reboot while resuming

[Martin Pitt]

** Package changed: systemd (Ubuntu) => linux (Ubuntu)

** Tags added: kernel-4.8

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

Title:
  [Yakkety] suspend fail and reboot while resuming

Status in linux package in Ubuntu:
  New

Bug description:
  Using 16.04 daily image: 20160919(downloading date)
  With testing package for 4.8 kernel: ppa:canonical-kernel-team/unstable

  Suspend by closing lid or setting menu, both randomly(2 out of 3
  times) cause system reboot after suspend.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: systemd 231-6git1
  ProcVersionSignature: Ubuntu 4.8.0-14.15-generic 4.8.0-rc7
  Uname: Linux 4.8.0-14-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Sep 22 18:07:09 2016
  InstallationDate: Installed on 2016-09-22 (0 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160918)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0bda:5682 Realtek Semiconductor Corp. 
   Bus 001 Device 003: ID 04f3:20d0 Elan Microelectronics Corp. 
   Bus 001 Device 002: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 13 9350
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-14-generic.efi.signed 
root=UUID=5ce90c47-3ebd-4119-9522-ad3d23f95ce3 ro quiet splash vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/14/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.4.4
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.4.4:bd06/14/2016:svnDellInc.:pnXPS139350:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 13 9350
  dmi.sys.vendor: Dell Inc.

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

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

[Martin Pitt]

Great news! until that happens, is there any harm in leaving 4.8 or
4.4.23 running on the current compute nodes?

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

Title:
  [arm64] compute nodes unstable after upgrading from 4.2 to 4.4 kernel

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Xenial:
  In Progress

Bug description:
  Hi,

  In order to investigate bug LP#1531768, we upgraded some arm64 compute
  nodes (swirlices) to a 4.4 kernel. I think it made the VMs work
  better, but the hosts became extremely unstable.

  After some time, getting a shell on them would be impossible.
  Connecting on the VSP, you'd get a prompt, and once you typed your
  username and password, you'd see the motd but the shell would never
  spawn.

  Because of these instability issues, all the arm64 compute nodes are
  now back on 4.2. However, we managed to capture "perf record" data
  when a host was failing. I'll attach it to the bug. Perhaps it will
  give you hints as to what we can do to help you troubleshoot this bug
  further.

  Once we have your instructions, we'll happily reboot one (or a few)
  nodes to 4.4 to continue troubleshooting.

  Thanks !
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jul 12 12:54 seq
   crw-rw 1 root audio 116, 33 Jul 12 12:54 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: arm64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: Error: [Errno 2] No such file or directory
  DistroRelease: Ubuntu 14.04
  Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize 
libusb: -99
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: console=ttyS0,9600n8r ro compat_uts_machine=armv7l
  ProcVersionSignature: Ubuntu 4.2.0-41.48~14.04.1-generic 4.2.8-ckt11
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-41-generic N/A
   linux-backports-modules-4.2.0-41-generic  N/A
   linux-firmware1.127.22
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  trusty uec-images
  Uname: Linux 4.2.0-41-generic aarch64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1626436] Re: [4.8 regression] boot has become very slow

[Martin Pitt]

Still confirmed with yesterday's 4.8.0-19.21.

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

Title:
  [4.8 regression] boot has become very slow

Status in linux package in Ubuntu:
  Triaged

Bug description:
  With yakkety's recent update from linux 4.4 to 4.8 booting has become
  a lot slower. It's not one service in particular, but without "quiet"
  and "splash" you can now easily read every single line instead of that
  whole wall of text zipping by. It now takes over 20s instead of ~10
  seconds to boot.

  This is even more dramatic when factoring out the recent boot hang of
  NetworkManager (bug 1622893) and disabling lightdm:

sudo systemctl mask NetworkManager NetworkManager-wait-online
  lightdm

  then booting with 4.4 takes 1.5s and with 4.8 19.5s (!).

  Some excerps from systemd-analyze blame:

  4.4:
 474ms postfix@-.service
 395ms lxd-containers.service
 305ms networking.service

  4.8:
4.578s postfix@-.service
7.300s lxd-containers.service
6.285s networking.service

  I attach the full outputs of critical-chain and analyze for 4.4 and
  4.8 for reference.

  
  This is much less noticeable in the running system. There is no immediate 
feeling of sluggishness (although my system is by and large idle).

  I compared the time of sbuilding colord under similar circumstances
  (-j4, building on tmpfs, thus no hard disk delays; running with fully
  pre-loaded apt-cacher-ng thus no random network delays), and with 4.4
  it takes 6.5 minutes and with 4.8 it takes 7.5. So that got a bit
  slower, but much less dramatically than during boot, so this is either
  happening when a lot of processes run in parallel, or is perhaps
  related to setting up cgroups.

  One thing I noticed that during sbuild in 4.8 "top" shows ridiculous
  loads (~ 250) under 4.8, while it's around 4 or 5 under 4.8. But that
  doesn't reflect in actual sluggishness, so this might be just an
  unrelated bug.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: linux-image-4.8.0-11-generic 4.8.0-11.12
  ProcVersionSignature: Ubuntu 4.8.0-11.12-generic 4.8.0-rc6
  Uname: Linux 4.8.0-11-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   martin 3049 F...m pulseaudio
   /dev/snd/pcmC0D0p:   martin 3049 F...m pulseaudio
   /dev/snd/controlC0:  martin 3049 F pulseaudio
  Date: Thu Sep 22 09:42:56 2016
  EcryptfsInUse: Yes
  MachineType: LENOVO 2324CTO
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.8.0-11-generic.efi.signed 
root=UUID=f86539b0-3a1b-4372-83b0-acdd029ade68 ro rootflags=subvol=@ 
systemd.debug-shell
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-11-generic N/A
   linux-backports-modules-4.8.0-11-generic  N/A
   linux-firmware1.161
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/09/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G2ET95WW (2.55 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2324CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: 0B98401 Pro
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG2ET95WW(2.55):bd07/09/2013:svnLENOVO:pn2324CTO:pvrThinkPadX230:rvnLENOVO:rn2324CTO:rvr0B98401Pro:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 2324CTO
  dmi.product.version: ThinkPad X230
  dmi.sys.vendor: LENOVO

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1626737] Re: [4.8.0-14/ppc64el regression] rmmod scsi_debug keeps causing kernel oops

[Martin Pitt]

I didn't find a simpler reproducer on the CLI, and the systemd test now
does not call rmmod any more, so there's no handle on this any more.

** Changed in: linux (Ubuntu)
   Status: Confirmed => Invalid

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

Title:
  [4.8.0-14/ppc64el regression] rmmod scsi_debug keeps causing kernel
  oops

Status in linux package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Fix Released

Bug description:
  Since upgrading to 4.8.0-14, the "storage" autopkgtest of systemd is
  broken. This uses scsi_debug to get a test hard drive, which is reset
  between the test through unloading/reloading the module. This has
  worked fine so far (and still works on amd64/i386), but now regularly
  triggers a kernel oops:

  [  161.120362] Unable to handle kernel paging request for data at address 
0x
  [  161.120468] Faulting instruction address: 0xc0538ecc
  [  161.120517] Oops: Kernel access of bad area, sig: 11 [#1]
  [  161.120555] SMP NR_CPUS=2048 NUMA pSeries
  [  161.120595] Modules linked in: dm_crypt dm_mod xts algif_skcipher af_alg 
sd_mod sg xt_TCPMSS xt_tcpudp iptable_mangle ghash_generic gf128mul vmx_crypto 
virtio_balloon ip_tables x_tables autofs4 ext4 crc16 jbd2 fscrypto mbcache 
crc32c_generic btrfs xor raid6_pq ohci_pci ehci_pci ohci_hcd virtio_blk 
virtio_net ehci_hcd usbcore crc32c_vpmsum usb_common virtio_pci virtio_ring 
virtio [last unloaded: scsi_debug]
  [  161.121016] CPU: 0 PID: 5473 Comm: rmmod Not tainted 4.8.0-15-generic 
#16-Ubuntu
  [  161.121067] task: c0005ae51980 task.stack: c0005ef58000
  [  161.121110] NIP: c0538ecc LR: c0538ee0 CTR: 
c00f7250
  [  161.121162] REGS: c0005ef5b9f0 TRAP: 0300   Not tainted  
(4.8.0-15-generic)
  [  161.121213] MSR: 80010280b033   
CR: 28002444  XER: 2000
  [  161.121390] CFAR: c009a8e0 DAR:  DSISR: 4000 
SOFTE: 1 
 GPR00: c0538e98 c0005ef5bc70 c0f67b00 
 
 GPR04: d1302018 0002  
c10d7b00 
 GPR08: c0fa7b00 0063 0073 
0004 
 GPR12: 28002844 cfb8  
 
 GPR16:  0100331f11f0 384b3890 
384b3848 
 GPR20: 384b3830 384b3870 384b38a8 
384b3888 
 GPR24: 3fffd23d6e70 c0ebdec8 fffe 
d1302018 
 GPR28: c0ebdeb8   
 
  [  161.122099] NIP [c0538ecc] ddebug_remove_module+0x8c/0x160
  [  161.122143] LR [c0538ee0] ddebug_remove_module+0xa0/0x160
  [  161.122186] Call Trace:
  [  161.122205] [c0005ef5bc70] [c0538e98] 
ddebug_remove_module+0x58/0x160 (unreliable)
  [  161.122280] [c0005ef5bd10] [c018961c] free_module+0x21c/0x3c0
  [  161.122333] [c0005ef5bd60] [c0189a38] 
SyS_delete_module+0x278/0x2f0
  [  161.122394] [c0005ef5be30] [c00095e0] system_call+0x38/0x108
  [  161.122445] Instruction dump:
  [  161.122472] 3d42fff5 e92a63b8 7fa9e000 7d3d4b78 ebe9 419e00bc 7d3e4b78 
3b40fffe 
  [  161.122561] 4818 7fbfe000 7ffdfb78 7ffefb78  419e0060 
e87e0010 7f64db78 
  [  161.122651] ---[ end trace 5f19b96c7077a0e0 ]---

  This isn't reproducible by merely loading and unloading the module, it
  apparently needs to get some actual exercise. I'll find a simpler
  reproducer than running the systemd test tomorrow morning.

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1627108] Re: X1Carbon comes to a crawl during high CPU usage tasks

[Martin Pitt]

I filed bug 1626436 which is similar; I wanted to try
http://kernel.ubuntu.com/~jsalisbury/lp1627108 but that is empty?

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

Title:
  X1Carbon comes to a crawl during high CPU usage tasks

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Yakkety:
  In Progress

Bug description:
  My X1Carbon becomes quite laggy, the cursor hangs for a few seconds
  and then resumes while my system is compiling some code, or lets says
  PyCharm is indexing things or Android Studio is compiling some code. I
  was using 4.4 on Xenial a few days ago and everything was working just
  fine. Installed Yakkety and this issue happens.

  I will downgrade the kernel and see if that mitigates the issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: linux-image-4.8.0-15-generic 4.8.0-15.16
  ProcVersionSignature: Ubuntu 4.8.0-15.16-generic 4.8.0-rc7
  Uname: Linux 4.8.0-15-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC1D0p:   om26er 3390 F...m pulseaudio
   /dev/snd/controlC1:  om26er 3390 F pulseaudio
   /dev/snd/controlC0:  om26er 3390 F pulseaudio
  CurrentDesktop: Unity
  Date: Fri Sep 23 21:40:34 2016
  HibernationDevice: RESUME=UUID=a92c85ab-cca3-4afc-abf1-3516f193129e
  InstallationDate: Installed on 2016-09-21 (1 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160921)
  MachineType: LENOVO 20BSCTO1WW
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-15-generic.efi.signed 
root=UUID=01b0a4a0-d791-46e8-a212-1f769cff3a4b ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-15-generic N/A
   linux-backports-modules-4.8.0-15-generic  N/A
   linux-firmware1.161
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/13/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N14ET32W (1.10 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20BSCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN14ET32W(1.10):bd08/13/2015:svnLENOVO:pn20BSCTO1WW:pvrThinkPadX1Carbon3rd:rvnLENOVO:rn20BSCTO1WW:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.name: 20BSCTO1WW
  dmi.product.version: ThinkPad X1 Carbon 3rd
  dmi.sys.vendor: LENOVO

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

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

[Martin Pitt]

My lxd-armhf1 node that is supposedly running on 4.4.23-040423-generic
(on the compute host) has worked fine for the last 13 hours.

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

Title:
  [arm64] compute nodes unstable after upgrading from 4.2 to 4.4 kernel

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Xenial:
  In Progress

Bug description:
  Hi,

  In order to investigate bug LP#1531768, we upgraded some arm64 compute
  nodes (swirlices) to a 4.4 kernel. I think it made the VMs work
  better, but the hosts became extremely unstable.

  After some time, getting a shell on them would be impossible.
  Connecting on the VSP, you'd get a prompt, and once you typed your
  username and password, you'd see the motd but the shell would never
  spawn.

  Because of these instability issues, all the arm64 compute nodes are
  now back on 4.2. However, we managed to capture "perf record" data
  when a host was failing. I'll attach it to the bug. Perhaps it will
  give you hints as to what we can do to help you troubleshoot this bug
  further.

  Once we have your instructions, we'll happily reboot one (or a few)
  nodes to 4.4 to continue troubleshooting.

  Thanks !
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jul 12 12:54 seq
   crw-rw 1 root audio 116, 33 Jul 12 12:54 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: arm64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: Error: [Errno 2] No such file or directory
  DistroRelease: Ubuntu 14.04
  Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize 
libusb: -99
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: console=ttyS0,9600n8r ro compat_uts_machine=armv7l
  ProcVersionSignature: Ubuntu 4.2.0-41.48~14.04.1-generic 4.2.8-ckt11
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-41-generic N/A
   linux-backports-modules-4.2.0-41-generic  N/A
   linux-firmware1.127.22
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  trusty uec-images
  Uname: Linux 4.2.0-41-generic aarch64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1630245] Re: after starting ubuntu 16.10 -- no keyboard, no mouse

[Martin Pitt]

** Package changed: systemd (Ubuntu) => linux (Ubuntu)

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

Title:
  after starting ubuntu 16.10 -- no keyboard, no mouse

Status in linux package in Ubuntu:
  New

Bug description:
  After starting Ubuntu 16.10 keyboard and mouse are dead. Since it
  works with an older kernel but not with the latest one, I'd assume the
  newer kernel does not initialize the devices the right way.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: systemd 231-9git1
  ProcVersionSignature: Ubuntu 4.4.0-9136.55-generic 4.4.16
  Uname: Linux 4.4.0-9136-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  Date: Tue Oct  4 15:27:52 2016
  InstallationDate: Installed on 2012-12-12 (1391 days ago)
  InstallationMedia: Ubuntu-Server 12.04.1 LTS "Precise Pangolin" - Release 
amd64 (20120817.3)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub
   Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: VMware, Inc. VMware Virtual Platform
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-9136-generic 
root=/dev/mapper/test--tps--ubuntu--muc-root ro vga=789 consoleblank=0
  SourcePackage: systemd
  UpgradeStatus: Upgraded to yakkety on 2013-02-11 (1330 days ago)
  dmi.bios.date: 07/02/2015
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: 6.00
  dmi.board.name: 440BX Desktop Reference Platform
  dmi.board.vendor: Intel Corporation
  dmi.board.version: None
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 1
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd07/02/2015:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
  dmi.product.name: VMware Virtual Platform
  dmi.product.version: None
  dmi.sys.vendor: VMware, Inc.

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

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

[Martin Pitt]

@Joseph: I don't know what is running on the compute hosts, I don't have
access to those. I suppose that Junien used the kernel you offered in
comment #26, though?

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

Title:
  [arm64] compute nodes unstable after upgrading from 4.2 to 4.4 kernel

Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Xenial:
  Triaged

Bug description:
  Hi,

  In order to investigate bug LP#1531768, we upgraded some arm64 compute
  nodes (swirlices) to a 4.4 kernel. I think it made the VMs work
  better, but the hosts became extremely unstable.

  After some time, getting a shell on them would be impossible.
  Connecting on the VSP, you'd get a prompt, and once you typed your
  username and password, you'd see the motd but the shell would never
  spawn.

  Because of these instability issues, all the arm64 compute nodes are
  now back on 4.2. However, we managed to capture "perf record" data
  when a host was failing. I'll attach it to the bug. Perhaps it will
  give you hints as to what we can do to help you troubleshoot this bug
  further.

  Once we have your instructions, we'll happily reboot one (or a few)
  nodes to 4.4 to continue troubleshooting.

  Thanks !
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jul 12 12:54 seq
   crw-rw 1 root audio 116, 33 Jul 12 12:54 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: arm64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: Error: [Errno 2] No such file or directory
  DistroRelease: Ubuntu 14.04
  Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize 
libusb: -99
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: console=ttyS0,9600n8r ro compat_uts_machine=armv7l
  ProcVersionSignature: Ubuntu 4.2.0-41.48~14.04.1-generic 4.2.8-ckt11
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-41-generic N/A
   linux-backports-modules-4.2.0-41-generic  N/A
   linux-firmware1.127.22
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  trusty uec-images
  Uname: Linux 4.2.0-41-generic aarch64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1624540] Re: please have lxd recommend zfs

[Martin Pitt]

> I believe the zed systemd unit should at the very least be modified
not to start inside containers

That can be done with ConditionVirtualization=!container

> (b) there were an /etc/default/zed which enabled one to disable zed
altogether.

Please don't do that. /etc/default files should never have been mis-used
for enabling/disabling services -- there already is update-rc.d
enable/disable for that (or the more direct systemctl enable/disable
now).

> we could have a unit list "RequiresFilesystem" with "zfs" and so have
zfs-zed kick in as soon as any zfs mount occurs

There is no direct way to express this; but IMHO a sufficient
approximation is to start it if a zfs file system exists? That can be
done with an udev rule like

  ACTION!="remove", SUBSYSTEM=="block", ENV{ID_FS_TYPE}=="zfs",
ENV{SYSTEMD_WANTS}+="zed.service"

Note that I don't know the precise value of ID_FS_TYPE for zpools, and
the precise name of the service you want to start.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1624540

Title:
  please have lxd recommend zfs

Status in lxd package in Ubuntu:
  Incomplete
Status in zfs-linux package in Ubuntu:
  Confirmed

Bug description:
  Since ZFS is now in Main (Bug #1532198), LXD should recommend the ZFS
  userspace package, such that 'sudo lxd init' just works.

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

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

[Martin Pitt]

Both of my instances have been working happily for three days now. SHIP
IT! :-)

Many thanks to the kernel team and Junien!

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

Title:
  [arm64] compute nodes unstable after upgrading from 4.2 to 4.4 kernel

Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Xenial:
  Triaged

Bug description:
  Hi,

  In order to investigate bug LP#1531768, we upgraded some arm64 compute
  nodes (swirlices) to a 4.4 kernel. I think it made the VMs work
  better, but the hosts became extremely unstable.

  After some time, getting a shell on them would be impossible.
  Connecting on the VSP, you'd get a prompt, and once you typed your
  username and password, you'd see the motd but the shell would never
  spawn.

  Because of these instability issues, all the arm64 compute nodes are
  now back on 4.2. However, we managed to capture "perf record" data
  when a host was failing. I'll attach it to the bug. Perhaps it will
  give you hints as to what we can do to help you troubleshoot this bug
  further.

  Once we have your instructions, we'll happily reboot one (or a few)
  nodes to 4.4 to continue troubleshooting.

  Thanks !
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jul 12 12:54 seq
   crw-rw 1 root audio 116, 33 Jul 12 12:54 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: arm64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: Error: [Errno 2] No such file or directory
  DistroRelease: Ubuntu 14.04
  Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize 
libusb: -99
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: console=ttyS0,9600n8r ro compat_uts_machine=armv7l
  ProcVersionSignature: Ubuntu 4.2.0-41.48~14.04.1-generic 4.2.8-ckt11
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-41-generic N/A
   linux-backports-modules-4.2.0-41-generic  N/A
   linux-firmware1.127.22
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  trusty uec-images
  Uname: Linux 4.2.0-41-generic aarch64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1531768] Re: [arm64] lockups some time after booting

[Martin Pitt]

For the record, I now use two arm64 xenial (4.4) instances on a host
with kernel 4.8, and things are looking really good. See latest posts to
bug 1602577.

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

Title:
  [arm64] lockups some time after booting

Status in Auto Package Testing:
  Triaged
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I created an 8 CPU arm64 instance on Canonical's Scalingstack (which I
  want to use for armhf autopkgtesting in LXD). I started with wily as
  that has lxd available (it's not yet available in trusty nor the PPA
  for arm64).

  However, pretty much any LXD task that I do (I haven't tried much
  else) on this machine takes unbearably long. A simple "lxc profile set
  default raw.lxc lxc.seccomp=" or "lxc list" takes several minutes.

  I see tons of

  [ 1020.971955] rcu_sched kthread starved for 6000 jiffies! g1095 c1094 f0x0
  [ 1121.166926] INFO: task fsnotify_mark:69 blocked for more than 120 seconds.

  in dmesg (the attached apport info has the complete dmesg).

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: linux-image-4.2.0-22-generic 4.2.0-22.27
  ProcVersionSignature: User Name 4.2.0-22.27-generic 4.2.6
  Uname: Linux 4.2.0-22-generic aarch64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jan  7 09:18 seq
   crw-rw 1 root audio 116, 33 Jan  7 09:18 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: arm64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  Date: Thu Jan  7 09:24:01 2016
  IwConfig:
   eth0  no wireless extensions.

   lono wireless extensions.

   lxcbr0no wireless extensions.
  Lspci:
   00:00.0 Host bridge [0600]: Red Hat, Inc. Device [1b36:0008]
    Subsystem: Red Hat, Inc Device [1af4:1100]
    Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
    Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB:

  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-22-generic 
root=LABEL=cloudimg-rootfs earlyprintk
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-22-generic N/A
   linux-backports-modules-4.2.0-22-generic  N/A
   linux-firmware1.149.3
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/auto-package-testing/+bug/1531768/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

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

[Martin Pitt]

My two arm64 instances had been idle for 16 hours, and after that fully
busy with running tests for about 5 hours. So from my POV, the 4.8
kernel does not have the RCU hang (bug 1531768) any more, or at least
much less noticeable. And apparently the host has survived about 24
hours as well now. I don't know what "after some time" in the bug
description translates to (minutes? hours? days?), but so far this is
looking pretty good \o/

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

Title:
  [arm64] compute nodes unstable after upgrading from 4.2 to 4.4 kernel

Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Xenial:
  Triaged

Bug description:
  Hi,

  In order to investigate bug LP#1531768, we upgraded some arm64 compute
  nodes (swirlices) to a 4.4 kernel. I think it made the VMs work
  better, but the hosts became extremely unstable.

  After some time, getting a shell on them would be impossible.
  Connecting on the VSP, you'd get a prompt, and once you typed your
  username and password, you'd see the motd but the shell would never
  spawn.

  Because of these instability issues, all the arm64 compute nodes are
  now back on 4.2. However, we managed to capture "perf record" data
  when a host was failing. I'll attach it to the bug. Perhaps it will
  give you hints as to what we can do to help you troubleshoot this bug
  further.

  Once we have your instructions, we'll happily reboot one (or a few)
  nodes to 4.4 to continue troubleshooting.

  Thanks !
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jul 12 12:54 seq
   crw-rw 1 root audio 116, 33 Jul 12 12:54 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: arm64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: Error: [Errno 2] No such file or directory
  DistroRelease: Ubuntu 14.04
  Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize 
libusb: -99
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: console=ttyS0,9600n8r ro compat_uts_machine=armv7l
  ProcVersionSignature: Ubuntu 4.2.0-41.48~14.04.1-generic 4.2.8-ckt11
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-41-generic N/A
   linux-backports-modules-4.2.0-41-generic  N/A
   linux-firmware1.127.22
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  trusty uec-images
  Uname: Linux 4.2.0-41-generic aarch64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

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

[Martin Pitt]

My two instances have been up and idle for 1:30 hours by now. They don't
have any actual lxd workload due to bug 1628946 (juju deploy currently
fails), but the original hang bug actually happened on idle boxes. Thus,
so far so good :-)

I'll check again tomorrow.

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

Title:
  [arm64] compute nodes unstable after upgrading from 4.2 to 4.4 kernel

Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Xenial:
  Triaged

Bug description:
  Hi,

  In order to investigate bug LP#1531768, we upgraded some arm64 compute
  nodes (swirlices) to a 4.4 kernel. I think it made the VMs work
  better, but the hosts became extremely unstable.

  After some time, getting a shell on them would be impossible.
  Connecting on the VSP, you'd get a prompt, and once you typed your
  username and password, you'd see the motd but the shell would never
  spawn.

  Because of these instability issues, all the arm64 compute nodes are
  now back on 4.2. However, we managed to capture "perf record" data
  when a host was failing. I'll attach it to the bug. Perhaps it will
  give you hints as to what we can do to help you troubleshoot this bug
  further.

  Once we have your instructions, we'll happily reboot one (or a few)
  nodes to 4.4 to continue troubleshooting.

  Thanks !
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jul 12 12:54 seq
   crw-rw 1 root audio 116, 33 Jul 12 12:54 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: arm64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: Error: [Errno 2] No such file or directory
  DistroRelease: Ubuntu 14.04
  Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize 
libusb: -99
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: console=ttyS0,9600n8r ro compat_uts_machine=armv7l
  ProcVersionSignature: Ubuntu 4.2.0-41.48~14.04.1-generic 4.2.8-ckt11
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-41-generic N/A
   linux-backports-modules-4.2.0-41-generic  N/A
   linux-firmware1.127.22
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  trusty uec-images
  Uname: Linux 4.2.0-41-generic aarch64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1626564] Re: 4.8 regression: SLAB is being used instead of SLUB

[Martin Pitt]

> it seems the issue is not 100% solved, but is much much much less
probable.

I confirm this in bug 1626436 -- boot time is a bit faster and load now
"only" ~ 35 instead of ~ 250, but it's still a huge regression compared
to 4.4.

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

Title:
  4.8 regression: SLAB is being used instead of SLUB

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Yakkety:
  Fix Released

Bug description:
  We're seeing hundreds of kernel worker threads being spawned with some
  actions, for example, after booting the desktop and hutting the
  brightness keys causes this.  On investigation, this occurs when
  CONFIG_SLAB is being used.

  1. Ubuntu traditionally uses CONFIG_SLUB, so we should use that instead of 
CONFIG_SLAB (why was it changed for Yakkety?)
  2. With CONFIG_SLUB I cannot reproduce the issue of the hundreds for worker 
threads
  3 CONFIG_SLUB seems more performant on the boot too over SLAB.

  Please re-enable the CONFIG_SLUB allocator as per the 4.4. Xenial
  configs.

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1626436] Re: [4.8 regression] boot has become very slow

[Martin Pitt]

Unduplicating. This still happens with 4.8.0-17 from the PPA, both the
slow boots and the high load times. It got a fair bit better, though
(load of ~ 35 instead of ~ 250), but still a huge regression compared to
4.4.

** This bug is no longer a duplicate of bug 1626564
   4.8 regression: SLAB is being used instead of SLUB

** Changed in: linux (Ubuntu)
   Status: In Progress => Triaged

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

Title:
  [4.8 regression] boot has become very slow

Status in linux package in Ubuntu:
  Triaged

Bug description:
  With yakkety's recent update from linux 4.4 to 4.8 booting has become
  a lot slower. It's not one service in particular, but without "quiet"
  and "splash" you can now easily read every single line instead of that
  whole wall of text zipping by. It now takes over 20s instead of ~10
  seconds to boot.

  This is even more dramatic when factoring out the recent boot hang of
  NetworkManager (bug 1622893) and disabling lightdm:

sudo systemctl mask NetworkManager NetworkManager-wait-online
  lightdm

  then booting with 4.4 takes 1.5s and with 4.8 19.5s (!).

  Some excerps from systemd-analyze blame:

  4.4:
 474ms postfix@-.service
 395ms lxd-containers.service
 305ms networking.service

  4.8:
4.578s postfix@-.service
7.300s lxd-containers.service
6.285s networking.service

  I attach the full outputs of critical-chain and analyze for 4.4 and
  4.8 for reference.

  
  This is much less noticeable in the running system. There is no immediate 
feeling of sluggishness (although my system is by and large idle).

  I compared the time of sbuilding colord under similar circumstances
  (-j4, building on tmpfs, thus no hard disk delays; running with fully
  pre-loaded apt-cacher-ng thus no random network delays), and with 4.4
  it takes 6.5 minutes and with 4.8 it takes 7.5. So that got a bit
  slower, but much less dramatically than during boot, so this is either
  happening when a lot of processes run in parallel, or is perhaps
  related to setting up cgroups.

  One thing I noticed that during sbuild in 4.8 "top" shows ridiculous
  loads (~ 250) under 4.8, while it's around 4 or 5 under 4.8. But that
  doesn't reflect in actual sluggishness, so this might be just an
  unrelated bug.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: linux-image-4.8.0-11-generic 4.8.0-11.12
  ProcVersionSignature: Ubuntu 4.8.0-11.12-generic 4.8.0-rc6
  Uname: Linux 4.8.0-11-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   martin 3049 F...m pulseaudio
   /dev/snd/pcmC0D0p:   martin 3049 F...m pulseaudio
   /dev/snd/controlC0:  martin 3049 F pulseaudio
  Date: Thu Sep 22 09:42:56 2016
  EcryptfsInUse: Yes
  MachineType: LENOVO 2324CTO
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.8.0-11-generic.efi.signed 
root=UUID=f86539b0-3a1b-4372-83b0-acdd029ade68 ro rootflags=subvol=@ 
systemd.debug-shell
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-11-generic N/A
   linux-backports-modules-4.8.0-11-generic  N/A
   linux-firmware1.161
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/09/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G2ET95WW (2.55 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2324CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: 0B98401 Pro
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG2ET95WW(2.55):bd07/09/2013:svnLENOVO:pn2324CTO:pvrThinkPadX230:rvnLENOVO:rn2324CTO:rvr0B98401Pro:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 2324CTO
  dmi.product.version: ThinkPad X230
  dmi.sys.vendor: LENOVO

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1627052] Re: 4.8.0-16.17: genirq: Flags mismatch serial vs goldfish_pdev_bus

[Martin Pitt]

This bug also trivially reproduces in local QEMU, so can easily be
tested locally as well. So thankfully this doesn't seem to be some
Scalingstack quirk.

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

Title:
  4.8.0-16.17: genirq: Flags mismatch serial vs goldfish_pdev_bus

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Yakkety:
  Fix Committed

Bug description:
  I usually run kvm with '-serial stdio' after adding
  GRUB_CMDLINE_LINUX_DEFAULT="console=ttyS0" to /etc/default/grub.  This
  will give me a serial console where I can login and, more important,
  get kernel logs.

  After install 4.8.0-16.17 I'm unable to login in the serial console,
  and I'm getting a lot of messages:

genirq: Flags mismatch irq 4.  (serial) vs. 0080
  (goldfish_pdev_bus)

  System seems to be working fine otherwise.

  4.8.0-15.16 didn't show this behaviour.

  The obvious suspect commits are the "SAUCE: irqchip/gicv3-its:*" in
  -16, although the several config changes may also be involved.

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1627052] Re: 4.8.0-16.17: genirq: Flags mismatch serial vs goldfish_pdev_bus

[Martin Pitt]

I confirm that 4.8.0-17 in the PPA boots on Scalingstack instances
again. Thanks!

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

Title:
  4.8.0-16.17: genirq: Flags mismatch serial vs goldfish_pdev_bus

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Yakkety:
  Fix Committed

Bug description:
  I usually run kvm with '-serial stdio' after adding
  GRUB_CMDLINE_LINUX_DEFAULT="console=ttyS0" to /etc/default/grub.  This
  will give me a serial console where I can login and, more important,
  get kernel logs.

  After install 4.8.0-16.17 I'm unable to login in the serial console,
  and I'm getting a lot of messages:

genirq: Flags mismatch irq 4.  (serial) vs. 0080
  (goldfish_pdev_bus)

  System seems to be working fine otherwise.

  4.8.0-15.16 didn't show this behaviour.

  The obvious suspect commits are the "SAUCE: irqchip/gicv3-its:*" in
  -16, although the several config changes may also be involved.

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1627052] Re: 4.8.0-16.17: genirq: Flags mismatch serial vs goldfish_pdev_bus

[Martin Pitt]

This seems to break instance boots on scalingstack i386 and amd64
completely. I get thousands of these messages in console-log, and it
never actually boots up. This breaks all autopkgtesting.

** Changed in: linux (Ubuntu Yakkety)
   Importance: Medium => Critical

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

Title:
  4.8.0-16.17: genirq: Flags mismatch serial vs goldfish_pdev_bus

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Yakkety:
  Fix Committed

Bug description:
  I usually run kvm with '-serial stdio' after adding
  GRUB_CMDLINE_LINUX_DEFAULT="console=ttyS0" to /etc/default/grub.  This
  will give me a serial console where I can login and, more important,
  get kernel logs.

  After install 4.8.0-16.17 I'm unable to login in the serial console,
  and I'm getting a lot of messages:

genirq: Flags mismatch irq 4.  (serial) vs. 0080
  (goldfish_pdev_bus)

  System seems to be working fine otherwise.

  4.8.0-15.16 didn't show this behaviour.

  The obvious suspect commits are the "SAUCE: irqchip/gicv3-its:*" in
  -16, although the several config changes may also be involved.

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1626436] Re: [4.8 regression] boot has become very slow

[Martin Pitt]

*** This bug is a duplicate of bug 1626564 ***
https://bugs.launchpad.net/bugs/1626564

As far as I understand Andy, bug 1626564 is the root cause, thus duping.

** This bug has been marked a duplicate of bug 1626564
   4.8 regression: SLAB is being used instead of SLUB

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

Title:
  [4.8 regression] boot has become very slow

Status in linux package in Ubuntu:
  In Progress

Bug description:
  With yakkety's recent update from linux 4.4 to 4.8 booting has become
  a lot slower. It's not one service in particular, but without "quiet"
  and "splash" you can now easily read every single line instead of that
  whole wall of text zipping by. It now takes over 20s instead of ~10
  seconds to boot.

  This is even more dramatic when factoring out the recent boot hang of
  NetworkManager (bug 1622893) and disabling lightdm:

sudo systemctl mask NetworkManager NetworkManager-wait-online
  lightdm

  then booting with 4.4 takes 1.5s and with 4.8 19.5s (!).

  Some excerps from systemd-analyze blame:

  4.4:
 474ms postfix@-.service
 395ms lxd-containers.service
 305ms networking.service

  4.8:
4.578s postfix@-.service
7.300s lxd-containers.service
6.285s networking.service

  I attach the full outputs of critical-chain and analyze for 4.4 and
  4.8 for reference.

  
  This is much less noticeable in the running system. There is no immediate 
feeling of sluggishness (although my system is by and large idle).

  I compared the time of sbuilding colord under similar circumstances
  (-j4, building on tmpfs, thus no hard disk delays; running with fully
  pre-loaded apt-cacher-ng thus no random network delays), and with 4.4
  it takes 6.5 minutes and with 4.8 it takes 7.5. So that got a bit
  slower, but much less dramatically than during boot, so this is either
  happening when a lot of processes run in parallel, or is perhaps
  related to setting up cgroups.

  One thing I noticed that during sbuild in 4.8 "top" shows ridiculous
  loads (~ 250) under 4.8, while it's around 4 or 5 under 4.8. But that
  doesn't reflect in actual sluggishness, so this might be just an
  unrelated bug.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: linux-image-4.8.0-11-generic 4.8.0-11.12
  ProcVersionSignature: Ubuntu 4.8.0-11.12-generic 4.8.0-rc6
  Uname: Linux 4.8.0-11-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   martin 3049 F...m pulseaudio
   /dev/snd/pcmC0D0p:   martin 3049 F...m pulseaudio
   /dev/snd/controlC0:  martin 3049 F pulseaudio
  Date: Thu Sep 22 09:42:56 2016
  EcryptfsInUse: Yes
  MachineType: LENOVO 2324CTO
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.8.0-11-generic.efi.signed 
root=UUID=f86539b0-3a1b-4372-83b0-acdd029ade68 ro rootflags=subvol=@ 
systemd.debug-shell
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-11-generic N/A
   linux-backports-modules-4.8.0-11-generic  N/A
   linux-firmware1.161
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/09/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G2ET95WW (2.55 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2324CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: 0B98401 Pro
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG2ET95WW(2.55):bd07/09/2013:svnLENOVO:pn2324CTO:pvrThinkPadX230:rvnLENOVO:rn2324CTO:rvr0B98401Pro:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 2324CTO
  dmi.product.version: ThinkPad X230
  dmi.sys.vendor: LENOVO

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1626737] Re: [4.8.0-14/ppc64el regression] rmmod scsi_debug keeps causing kernel oops

[Martin Pitt]

I adjusted the test to avoid "rmmod scsi_debug":
https://anonscm.debian.org/cgit/pkg-
systemd/systemd.git/commit/?id=be77e470d8

So there's still a bug there, but it won't block testing any more at
least. And rmmod is always a bit brittle anyway, so let's avoid it.

** Changed in: systemd (Ubuntu)
   Importance: Undecided => Medium

** Changed in: systemd (Ubuntu)
   Status: New => Fix Committed

** Changed in: systemd (Ubuntu)
 Assignee: (unassigned) => Martin Pitt (pitti)

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

Title:
  [4.8.0-14/ppc64el regression] rmmod scsi_debug keeps causing kernel
  oops

Status in linux package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Fix Committed

Bug description:
  Since upgrading to 4.8.0-14, the "storage" autopkgtest of systemd is
  broken. This uses scsi_debug to get a test hard drive, which is reset
  between the test through unloading/reloading the module. This has
  worked fine so far (and still works on amd64/i386), but now regularly
  triggers a kernel oops:

  [  161.120362] Unable to handle kernel paging request for data at address 
0x
  [  161.120468] Faulting instruction address: 0xc0538ecc
  [  161.120517] Oops: Kernel access of bad area, sig: 11 [#1]
  [  161.120555] SMP NR_CPUS=2048 NUMA pSeries
  [  161.120595] Modules linked in: dm_crypt dm_mod xts algif_skcipher af_alg 
sd_mod sg xt_TCPMSS xt_tcpudp iptable_mangle ghash_generic gf128mul vmx_crypto 
virtio_balloon ip_tables x_tables autofs4 ext4 crc16 jbd2 fscrypto mbcache 
crc32c_generic btrfs xor raid6_pq ohci_pci ehci_pci ohci_hcd virtio_blk 
virtio_net ehci_hcd usbcore crc32c_vpmsum usb_common virtio_pci virtio_ring 
virtio [last unloaded: scsi_debug]
  [  161.121016] CPU: 0 PID: 5473 Comm: rmmod Not tainted 4.8.0-15-generic 
#16-Ubuntu
  [  161.121067] task: c0005ae51980 task.stack: c0005ef58000
  [  161.121110] NIP: c0538ecc LR: c0538ee0 CTR: 
c00f7250
  [  161.121162] REGS: c0005ef5b9f0 TRAP: 0300   Not tainted  
(4.8.0-15-generic)
  [  161.121213] MSR: 80010280b033 <SF,VEC,VSX,EE,FP,ME,IR,DR,RI,LE,TM[E]>  
CR: 28002444  XER: 2000
  [  161.121390] CFAR: c009a8e0 DAR:  DSISR: 4000 
SOFTE: 1 
 GPR00: c0538e98 c0005ef5bc70 c0f67b00 
 
 GPR04: d1302018 0002  
c10d7b00 
 GPR08: c0fa7b00 0063 0073 
0004 
 GPR12: 28002844 cfb8  
 
 GPR16:  0100331f11f0 384b3890 
384b3848 
 GPR20: 384b3830 384b3870 384b38a8 
384b3888 
 GPR24: 3fffd23d6e70 c0ebdec8 fffe 
d1302018 
 GPR28: c0ebdeb8   
 
  [  161.122099] NIP [c0538ecc] ddebug_remove_module+0x8c/0x160
  [  161.122143] LR [c0538ee0] ddebug_remove_module+0xa0/0x160
  [  161.122186] Call Trace:
  [  161.122205] [c0005ef5bc70] [c0538e98] 
ddebug_remove_module+0x58/0x160 (unreliable)
  [  161.122280] [c0005ef5bd10] [c018961c] free_module+0x21c/0x3c0
  [  161.122333] [c0005ef5bd60] [c0189a38] 
SyS_delete_module+0x278/0x2f0
  [  161.122394] [c0005ef5be30] [c00095e0] system_call+0x38/0x108
  [  161.122445] Instruction dump:
  [  161.122472] 3d42fff5 e92a63b8 7fa9e000 7d3d4b78 ebe9 419e00bc 7d3e4b78 
3b40fffe 
  [  161.122561] 4818 7fbfe000 7ffdfb78 7ffefb78  419e0060 
e87e0010 7f64db78 
  [  161.122651] ---[ end trace 5f19b96c7077a0e0 ]---

  This isn't reproducible by merely loading and unloading the module, it
  apparently needs to get some actual exercise. I'll find a simpler
  reproducer than running the systemd test tomorrow morning.

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1626737] Re: [4.8.0-14/ppc64el regression] rmmod scsi_debug keeps causing kernel oops

[Martin Pitt]

** Also affects: systemd (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  [4.8.0-14/ppc64el regression] rmmod scsi_debug keeps causing kernel
  oops

Status in linux package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  New

Bug description:
  Since upgrading to 4.8.0-14, the "storage" autopkgtest of systemd is
  broken. This uses scsi_debug to get a test hard drive, which is reset
  between the test through unloading/reloading the module. This has
  worked fine so far (and still works on amd64/i386), but now regularly
  triggers a kernel oops:

  [  161.120362] Unable to handle kernel paging request for data at address 
0x
  [  161.120468] Faulting instruction address: 0xc0538ecc
  [  161.120517] Oops: Kernel access of bad area, sig: 11 [#1]
  [  161.120555] SMP NR_CPUS=2048 NUMA pSeries
  [  161.120595] Modules linked in: dm_crypt dm_mod xts algif_skcipher af_alg 
sd_mod sg xt_TCPMSS xt_tcpudp iptable_mangle ghash_generic gf128mul vmx_crypto 
virtio_balloon ip_tables x_tables autofs4 ext4 crc16 jbd2 fscrypto mbcache 
crc32c_generic btrfs xor raid6_pq ohci_pci ehci_pci ohci_hcd virtio_blk 
virtio_net ehci_hcd usbcore crc32c_vpmsum usb_common virtio_pci virtio_ring 
virtio [last unloaded: scsi_debug]
  [  161.121016] CPU: 0 PID: 5473 Comm: rmmod Not tainted 4.8.0-15-generic 
#16-Ubuntu
  [  161.121067] task: c0005ae51980 task.stack: c0005ef58000
  [  161.121110] NIP: c0538ecc LR: c0538ee0 CTR: 
c00f7250
  [  161.121162] REGS: c0005ef5b9f0 TRAP: 0300   Not tainted  
(4.8.0-15-generic)
  [  161.121213] MSR: 80010280b033   
CR: 28002444  XER: 2000
  [  161.121390] CFAR: c009a8e0 DAR:  DSISR: 4000 
SOFTE: 1 
 GPR00: c0538e98 c0005ef5bc70 c0f67b00 
 
 GPR04: d1302018 0002  
c10d7b00 
 GPR08: c0fa7b00 0063 0073 
0004 
 GPR12: 28002844 cfb8  
 
 GPR16:  0100331f11f0 384b3890 
384b3848 
 GPR20: 384b3830 384b3870 384b38a8 
384b3888 
 GPR24: 3fffd23d6e70 c0ebdec8 fffe 
d1302018 
 GPR28: c0ebdeb8   
 
  [  161.122099] NIP [c0538ecc] ddebug_remove_module+0x8c/0x160
  [  161.122143] LR [c0538ee0] ddebug_remove_module+0xa0/0x160
  [  161.122186] Call Trace:
  [  161.122205] [c0005ef5bc70] [c0538e98] 
ddebug_remove_module+0x58/0x160 (unreliable)
  [  161.122280] [c0005ef5bd10] [c018961c] free_module+0x21c/0x3c0
  [  161.122333] [c0005ef5bd60] [c0189a38] 
SyS_delete_module+0x278/0x2f0
  [  161.122394] [c0005ef5be30] [c00095e0] system_call+0x38/0x108
  [  161.122445] Instruction dump:
  [  161.122472] 3d42fff5 e92a63b8 7fa9e000 7d3d4b78 ebe9 419e00bc 7d3e4b78 
3b40fffe 
  [  161.122561] 4818 7fbfe000 7ffdfb78 7ffefb78  419e0060 
e87e0010 7f64db78 
  [  161.122651] ---[ end trace 5f19b96c7077a0e0 ]---

  This isn't reproducible by merely loading and unloading the module, it
  apparently needs to get some actual exercise. I'll find a simpler
  reproducer than running the systemd test tomorrow morning.

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1626436] Re: [4.8 regression] boot has become very slow

[Martin Pitt]

For the record, Andy already has/knows the fix for this.

** Changed in: linux (Ubuntu)
   Status: Confirmed => In Progress

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

Title:
  [4.8 regression] boot has become very slow

Status in linux package in Ubuntu:
  In Progress

Bug description:
  With yakkety's recent update from linux 4.4 to 4.8 booting has become
  a lot slower. It's not one service in particular, but without "quiet"
  and "splash" you can now easily read every single line instead of that
  whole wall of text zipping by. It now takes over 20s instead of ~10
  seconds to boot.

  This is even more dramatic when factoring out the recent boot hang of
  NetworkManager (bug 1622893) and disabling lightdm:

sudo systemctl mask NetworkManager NetworkManager-wait-online
  lightdm

  then booting with 4.4 takes 1.5s and with 4.8 19.5s (!).

  Some excerps from systemd-analyze blame:

  4.4:
 474ms postfix@-.service
 395ms lxd-containers.service
 305ms networking.service

  4.8:
4.578s postfix@-.service
7.300s lxd-containers.service
6.285s networking.service

  I attach the full outputs of critical-chain and analyze for 4.4 and
  4.8 for reference.

  
  This is much less noticeable in the running system. There is no immediate 
feeling of sluggishness (although my system is by and large idle).

  I compared the time of sbuilding colord under similar circumstances
  (-j4, building on tmpfs, thus no hard disk delays; running with fully
  pre-loaded apt-cacher-ng thus no random network delays), and with 4.4
  it takes 6.5 minutes and with 4.8 it takes 7.5. So that got a bit
  slower, but much less dramatically than during boot, so this is either
  happening when a lot of processes run in parallel, or is perhaps
  related to setting up cgroups.

  One thing I noticed that during sbuild in 4.8 "top" shows ridiculous
  loads (~ 250) under 4.8, while it's around 4 or 5 under 4.8. But that
  doesn't reflect in actual sluggishness, so this might be just an
  unrelated bug.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: linux-image-4.8.0-11-generic 4.8.0-11.12
  ProcVersionSignature: Ubuntu 4.8.0-11.12-generic 4.8.0-rc6
  Uname: Linux 4.8.0-11-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   martin 3049 F...m pulseaudio
   /dev/snd/pcmC0D0p:   martin 3049 F...m pulseaudio
   /dev/snd/controlC0:  martin 3049 F pulseaudio
  Date: Thu Sep 22 09:42:56 2016
  EcryptfsInUse: Yes
  MachineType: LENOVO 2324CTO
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.8.0-11-generic.efi.signed 
root=UUID=f86539b0-3a1b-4372-83b0-acdd029ade68 ro rootflags=subvol=@ 
systemd.debug-shell
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-11-generic N/A
   linux-backports-modules-4.8.0-11-generic  N/A
   linux-firmware1.161
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/09/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G2ET95WW (2.55 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2324CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: 0B98401 Pro
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG2ET95WW(2.55):bd07/09/2013:svnLENOVO:pn2324CTO:pvrThinkPadX230:rvnLENOVO:rn2324CTO:rvr0B98401Pro:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 2324CTO
  dmi.product.version: ThinkPad X230
  dmi.sys.vendor: LENOVO

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1626737] [NEW] [4.8.0-14/ppc64el regression] rmmod scsi_debug keeps causing kernel oops

[Martin Pitt]

Public bug reported:

Since upgrading to 4.8.0-14, the "storage" autopkgtest of systemd is
broken. This uses scsi_debug to get a test hard drive, which is reset
between the test through unloading/reloading the module. This has worked
fine so far (and still works on amd64/i386), but now regularly triggers
a kernel oops:

[  161.120362] Unable to handle kernel paging request for data at address 
0x
[  161.120468] Faulting instruction address: 0xc0538ecc
[  161.120517] Oops: Kernel access of bad area, sig: 11 [#1]
[  161.120555] SMP NR_CPUS=2048 NUMA pSeries
[  161.120595] Modules linked in: dm_crypt dm_mod xts algif_skcipher af_alg 
sd_mod sg xt_TCPMSS xt_tcpudp iptable_mangle ghash_generic gf128mul vmx_crypto 
virtio_balloon ip_tables x_tables autofs4 ext4 crc16 jbd2 fscrypto mbcache 
crc32c_generic btrfs xor raid6_pq ohci_pci ehci_pci ohci_hcd virtio_blk 
virtio_net ehci_hcd usbcore crc32c_vpmsum usb_common virtio_pci virtio_ring 
virtio [last unloaded: scsi_debug]
[  161.121016] CPU: 0 PID: 5473 Comm: rmmod Not tainted 4.8.0-15-generic 
#16-Ubuntu
[  161.121067] task: c0005ae51980 task.stack: c0005ef58000
[  161.121110] NIP: c0538ecc LR: c0538ee0 CTR: c00f7250
[  161.121162] REGS: c0005ef5b9f0 TRAP: 0300   Not tainted  
(4.8.0-15-generic)
[  161.121213] MSR: 80010280b033   
CR: 28002444  XER: 2000
[  161.121390] CFAR: c009a8e0 DAR:  DSISR: 4000 
SOFTE: 1 
   GPR00: c0538e98 c0005ef5bc70 c0f67b00 
 
   GPR04: d1302018 0002  
c10d7b00 
   GPR08: c0fa7b00 0063 0073 
0004 
   GPR12: 28002844 cfb8  
 
   GPR16:  0100331f11f0 384b3890 
384b3848 
   GPR20: 384b3830 384b3870 384b38a8 
384b3888 
   GPR24: 3fffd23d6e70 c0ebdec8 fffe 
d1302018 
   GPR28: c0ebdeb8   
 
[  161.122099] NIP [c0538ecc] ddebug_remove_module+0x8c/0x160
[  161.122143] LR [c0538ee0] ddebug_remove_module+0xa0/0x160
[  161.122186] Call Trace:
[  161.122205] [c0005ef5bc70] [c0538e98] 
ddebug_remove_module+0x58/0x160 (unreliable)
[  161.122280] [c0005ef5bd10] [c018961c] free_module+0x21c/0x3c0
[  161.122333] [c0005ef5bd60] [c0189a38] 
SyS_delete_module+0x278/0x2f0
[  161.122394] [c0005ef5be30] [c00095e0] system_call+0x38/0x108
[  161.122445] Instruction dump:
[  161.122472] 3d42fff5 e92a63b8 7fa9e000 7d3d4b78 ebe9 419e00bc 7d3e4b78 
3b40fffe 
[  161.122561] 4818 7fbfe000 7ffdfb78 7ffefb78  419e0060 e87e0010 
7f64db78 
[  161.122651] ---[ end trace 5f19b96c7077a0e0 ]---

This isn't reproducible by merely loading and unloading the module, it
apparently needs to get some actual exercise. I'll find a simpler
reproducer than running the systemd test tomorrow morning.

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: Confirmed


** Tags: bot-stop-nagging kernel-4.8

** Tags added: bot-stop-nagging

** Summary changed:

- [4.8 regression] rmmod scsi_debug keeps causing kernel oops
+ [4.8.0-14/ppc64el regression] rmmod scsi_debug keeps causing kernel oops

** Changed in: linux (Ubuntu)
   Status: New => Confirmed

** Tags added: kernel-4.8

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

Title:
  [4.8.0-14/ppc64el regression] rmmod scsi_debug keeps causing kernel
  oops

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Since upgrading to 4.8.0-14, the "storage" autopkgtest of systemd is
  broken. This uses scsi_debug to get a test hard drive, which is reset
  between the test through unloading/reloading the module. This has
  worked fine so far (and still works on amd64/i386), but now regularly
  triggers a kernel oops:

  [  161.120362] Unable to handle kernel paging request for data at address 
0x
  [  161.120468] Faulting instruction address: 0xc0538ecc
  [  161.120517] Oops: Kernel access of bad area, sig: 11 [#1]
  [  161.120555] SMP NR_CPUS=2048 NUMA pSeries
  [  161.120595] Modules linked in: dm_crypt dm_mod xts algif_skcipher af_alg 
sd_mod sg xt_TCPMSS xt_tcpudp iptable_mangle ghash_generic gf128mul vmx_crypto 
virtio_balloon ip_tables x_tables autofs4 ext4 crc16 jbd2 fscrypto mbcache 
crc32c_generic btrfs xor raid6_pq ohci_pci ehci_pci ohci_hcd virtio_blk 
virtio_net ehci_hcd usbcore crc32c_vpmsum usb_common virtio_pci virtio_ring 
virtio [last unloaded: scsi_debug]
  [  161.121016] CPU: 0 PID: 5473 Comm: rmmod Not tainted 4.8.0-15-generic 
#16-Ubuntu
  

[Kernel-packages] [Bug 1626651] Re: brightness keys are handled slower in Yakkety than Xenial

[Martin Pitt]

Changing tasks as this is somewhere between unity-settings-daemon and
polkit.

** Package changed: linux (Ubuntu) => unity-settings-daemon (Ubuntu)

** Changed in: unity-settings-daemon (Ubuntu)
   Status: Incomplete => Triaged

** Package changed: systemd (Ubuntu) => policykit-1 (Ubuntu)

** Changed in: policykit-1 (Ubuntu)
   Status: Incomplete => Triaged

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

Title:
  brightness keys are handled slower in Yakkety than Xenial

Status in policykit-1 package in Ubuntu:
  Triaged
Status in unity-settings-daemon package in Ubuntu:
  Triaged

Bug description:
  I've noticed on Lenovo X220 and X230 laptops that pressing brightness
  keys on Yakkety seems less responsive and slower than Xenial.  I ran
  forkstat on Xenial and just observed udev being forked off:

  Xenial:
  $ sudo forkstat
  Time Event  PID  Info  Duration Process
  17:37:35 fork273 parent  /lib/systemd/systemd-udevd
  17:37:35 fork   1977 child   /lib/systemd/systemd-udevd
  17:37:35 exit   1977  00.008 /lib/systemd/systemd-udevd

  Whereas on Yakkety, there is far more activity:
  Time Event  PID  Info  Duration Process
  16:35:34 fork   2626 parent  update-notifier
  16:35:34 fork   2645 child   update-notifier
  16:35:34 exec   2645 /usr/bin/python3 
/usr/share/apport/apport-checkreports
  16:35:34 exit   26452560.221 /usr/bin/python3 
/usr/share/apport/apport-checkreports
  16:35:34 fork   2626 parent  update-notifier
  16:35:34 fork   2646 child   update-notifier
  16:35:34 exec   2646 /usr/bin/python3 
/usr/share/apport/apport-checkreports --system
  16:35:34 exit   26462560.188 /usr/bin/python3 
/usr/share/apport/apport-checkreports --system
  16:35:36 fork   1576 parent  
/usr/lib/unity-settings-daemon/unity-settings-daemon
  16:35:36 fork   2647 child   
/usr/lib/unity-settings-daemon/unity-settings-daemon
  16:35:36 exec   2647 
/usr/lib/unity-settings-daemon/usd-backlight-helper --get-max-brightness
  16:35:36 exit   2647  00.008 
/usr/lib/unity-settings-daemon/usd-backlight-helper --get-max-brightness
  16:35:36 fork   1576 parent  
/usr/lib/unity-settings-daemon/unity-settings-daemon
  16:35:36 fork   2648 child   
/usr/lib/unity-settings-daemon/unity-settings-daemon
  16:35:36 exec   2648 
/usr/lib/unity-settings-daemon/usd-backlight-helper --get-brightness
  16:35:36 exit   2648  00.006 
/usr/lib/unity-settings-daemon/usd-backlight-helper --get-brightness
  16:35:36 fork   1576 parent  
/usr/lib/unity-settings-daemon/unity-settings-daemon
  16:35:36 fork   2649 child   
/usr/lib/unity-settings-daemon/unity-settings-daemon
  16:35:36 exec   2649 
/usr/lib/unity-settings-daemon/usd-backlight-helper --get-brightness
  16:35:36 exit   2649  00.007 
/usr/lib/unity-settings-daemon/usd-backlight-helper --get-brightness
  16:35:36 fork   1576 parent  
/usr/lib/unity-settings-daemon/unity-settings-daemon
  16:35:36 fork   2650 child   
/usr/lib/unity-settings-daemon/unity-settings-daemon
  16:35:36 exec   2650 
/usr/lib/unity-settings-daemon/usd-backlight-helper --get-max-brightness
  16:35:36 exit   2650  00.006 
/usr/lib/unity-settings-daemon/usd-backlight-helper --get-max-brightness
  16:35:36 fork   1576 parent  
/usr/lib/unity-settings-daemon/unity-settings-daemon
  16:35:36 fork   2651 child   
/usr/lib/unity-settings-daemon/unity-settings-daemon
  16:35:36 exec   2651 pkexec 
/usr/lib/unity-settings-daemon/usd-backlight-helper --set-brightness 2250
  16:35:36 clone  2651 parent  pkexec 
/usr/lib/unity-settings-daemon/usd-backlight-helper --set-brightness 2250
  16:35:36 clone  2652 thread  pkexec 
/usr/lib/unity-settings-daemon/usd-backlight-helper --set-brightness 2250
  16:35:36 clone  2651 parent  pkexec 
/usr/lib/unity-settings-daemon/usd-backlight-helper --set-brightness 2250
  16:35:36 clone  2653 thread  pkexec 
/usr/lib/unity-settings-daemon/usd-backlight-helper --set-brightness 2250
  16:35:36 fork  1 parent  /sbin/init splash
  16:35:36 fork   2654 child   /sbin/init splash
  Time Event  PID  Info  Duration Process
  16:35:36 fork233 parent  /lib/systemd/systemd-udevd
  16:35:36 fork   2655 child   /lib/systemd/systemd-udevd
  16:35:36 fork233 parent  /lib/systemd/systemd-udevd
  16:35:36 fork   2656 child   /lib/systemd/systemd-udevd
  16:35:36 fork233 parent  /lib/systemd/systemd-udevd
  16:35:36 fork   2657 child   /lib/systemd/systemd-udevd
  16:35:36 fork233 parent  /lib/systemd/systemd-udevd
  16:35:36 fork   2658 child 

[Kernel-packages] [Bug 1626651] Re: brightness keys are handled slower in Yakkety than Xenial

[Martin Pitt]

I just dist-upgraded again, and with 4.8.0-14 my brightness keys work
again (bug 1626429). Under i3 (no unity-settings-daemon), I get a tame
and immediate reaction:

UDEV  [38372.886325] change   
/devices/pci:00/:00:02.0/backlight/acpi_video0 (backlight)
ACTION=change
DEVPATH=/devices/pci:00/:00:02.0/backlight/acpi_video0
ID_PATH=pci-:00:02.0
ID_PATH_TAG=pci-_00_02_0
SEQNUM=2735
SOURCE=hotkey
SUBSYSTEM=backlight
SYSTEMD_WANTS=systemd-backlight@backlight:acpi_video0.service
TAGS=:systemd:
USEC_INITIALIZED=9377712


21:07:21 fork   1298 parent  /lib/systemd/systemd-udevd
21:07:21 fork  25614 child   /lib/systemd/systemd-udevd
21:07:21 exit  25614  00.002 /lib/systemd/systemd-udevd

which matches the one uevent, but there is no userspace helper involved.
Brightness change still works as it's hardwired into the driver. This
proves that with just kernel and udev rules there is no delay and waste.

Under unity, with unity-settings-daemon, I now confirm the flurry of
userspace action. The main pain point is the pkexec in

  pkexec /usr/lib/unity-settings-daemon/usd-backlight-helper --get-
brightness

as that starts a full new PAM session, including systemd --user and
other expensive stuff. Our /etc/pam.d/polkit-1 pulls in "common-
session"; when changing this to "common-session-noninteractive" it
becomes muuuch cheaper, but this would again be wrong for cases where we
actually do want to run a new session for whatever we run there -- I'm
trying to think about cases where this would break. I. e. should pk-exec
behave more like "su" or "su -".

It would probably be best to grep the archive for usage of pk-exec,
review whether any of it requires an interactive PAM session, and if not
switch it to noninteractive.

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

Title:
  brightness keys are handled slower in Yakkety than Xenial

Status in policykit-1 package in Ubuntu:
  Triaged
Status in unity-settings-daemon package in Ubuntu:
  Triaged

Bug description:
  I've noticed on Lenovo X220 and X230 laptops that pressing brightness
  keys on Yakkety seems less responsive and slower than Xenial.  I ran
  forkstat on Xenial and just observed udev being forked off:

  Xenial:
  $ sudo forkstat
  Time Event  PID  Info  Duration Process
  17:37:35 fork273 parent  /lib/systemd/systemd-udevd
  17:37:35 fork   1977 child   /lib/systemd/systemd-udevd
  17:37:35 exit   1977  00.008 /lib/systemd/systemd-udevd

  Whereas on Yakkety, there is far more activity:
  Time Event  PID  Info  Duration Process
  16:35:34 fork   2626 parent  update-notifier
  16:35:34 fork   2645 child   update-notifier
  16:35:34 exec   2645 /usr/bin/python3 
/usr/share/apport/apport-checkreports
  16:35:34 exit   26452560.221 /usr/bin/python3 
/usr/share/apport/apport-checkreports
  16:35:34 fork   2626 parent  update-notifier
  16:35:34 fork   2646 child   update-notifier
  16:35:34 exec   2646 /usr/bin/python3 
/usr/share/apport/apport-checkreports --system
  16:35:34 exit   26462560.188 /usr/bin/python3 
/usr/share/apport/apport-checkreports --system
  16:35:36 fork   1576 parent  
/usr/lib/unity-settings-daemon/unity-settings-daemon
  16:35:36 fork   2647 child   
/usr/lib/unity-settings-daemon/unity-settings-daemon
  16:35:36 exec   2647 
/usr/lib/unity-settings-daemon/usd-backlight-helper --get-max-brightness
  16:35:36 exit   2647  00.008 
/usr/lib/unity-settings-daemon/usd-backlight-helper --get-max-brightness
  16:35:36 fork   1576 parent  
/usr/lib/unity-settings-daemon/unity-settings-daemon
  16:35:36 fork   2648 child   
/usr/lib/unity-settings-daemon/unity-settings-daemon
  16:35:36 exec   2648 
/usr/lib/unity-settings-daemon/usd-backlight-helper --get-brightness
  16:35:36 exit   2648  00.006 
/usr/lib/unity-settings-daemon/usd-backlight-helper --get-brightness
  16:35:36 fork   1576 parent  
/usr/lib/unity-settings-daemon/unity-settings-daemon
  16:35:36 fork   2649 child   
/usr/lib/unity-settings-daemon/unity-settings-daemon
  16:35:36 exec   2649 
/usr/lib/unity-settings-daemon/usd-backlight-helper --get-brightness
  16:35:36 exit   2649  00.007 
/usr/lib/unity-settings-daemon/usd-backlight-helper --get-brightness
  16:35:36 fork   1576 parent  
/usr/lib/unity-settings-daemon/unity-settings-daemon
  16:35:36 fork   2650 child   
/usr/lib/unity-settings-daemon/unity-settings-daemon
  16:35:36 exec   2650 
/usr/lib/unity-settings-daemon/usd-backlight-helper --get-max-brightness
  16:35:36 exit   2650  00.006 
/usr/lib/unity-settings-daemon/usd-backlight-helper --get-max-brightness
  16:35:36 fork   1576 

[Kernel-packages] [Bug 1626429] Re: [4.8 regression][ThinkPad X230] brightness change keys do not work any more

[Martin Pitt]

So this did break with -10 and -11, but was fixed again in -14.

** Changed in: linux (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  [4.8 regression][ThinkPad X230] brightness change keys do not work any
  more

Status in linux package in Ubuntu:
  Fix Released

Bug description:
  With yakkety's recent update from linux 4.4 to 4.8 my brightness keys
  stopped working. They are not handled in software via evdev events (on
  most platforms you just get a KEY_BRIGHTNESS{UP ../../../:00:02.0
  -r--r--r-- 1 root root 4096 Sep 22 09:45 max_brightness
  drwxr-xr-x 2 root root0 Sep 22 09:45 power
  lrwxrwxrwx 1 root root0 Sep 22 09:45 subsystem -> 
../../../../../class/backlight
  -r--r--r-- 1 root root 4096 Sep 22 09:45 type
  -rw-r--r-- 1 root root 4096 Sep 22 09:45 uevent

  /sys/class/backlight/intel_backlight/:
  -r--r--r-- 1 root root 4096 Sep 22 09:46 actual_brightness
  -rw-r--r-- 1 root root 4096 Sep 22 09:46 bl_power
  -rw-r--r-- 1 root root 4096 Sep 22 09:46 brightness
  lrwxrwxrwx 1 root root0 Sep 22 09:46 device -> ../../card0-LVDS-1
  -r--r--r-- 1 root root 4096 Sep 22 09:46 max_brightness
  drwxr-xr-x 2 root root0 Sep 22 09:46 power
  lrwxrwxrwx 1 root root0 Sep 22 09:46 subsystem -> 
../../../../../../../class/backlight
  -r--r--r-- 1 root root 4096 Sep 22 09:46 type
  -rw-r--r-- 1 root root 4096 Sep 22 09:46 uevent

  While in 4.8 I only have intel_backlight and acpi_video0 is missing
  completely.

  I. e. in 4.4 this command works:

echo 12 | sudo tee /sys/class/backlight/acpi_video0/brightness

  and I suppose this is the moral equivalent of what happens when I
  press the brightness keys,  i. e. these keys seem to be handled by the
  acpi_video0 driver instead of intel_backlight.

  The intel driver still actually works, I can do

echo 1000 | sudo tee /sys/class/backlight/intel_backlight/brightness

  but this isn't connected to the keys any more.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: linux-image-4.8.0-11-generic 4.8.0-11.12
  ProcVersionSignature: Ubuntu 4.8.0-11.12-generic 4.8.0-rc6
  Uname: Linux 4.8.0-11-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   martin 3049 F...m pulseaudio
   /dev/snd/pcmC0D0p:   martin 3049 F...m pulseaudio
   /dev/snd/controlC0:  martin 3049 F pulseaudio
  Date: Thu Sep 22 09:42:56 2016
  EcryptfsInUse: Yes
  MachineType: LENOVO 2324CTO
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.8.0-11-generic.efi.signed 
root=UUID=f86539b0-3a1b-4372-83b0-acdd029ade68 ro rootflags=subvol=@ 
systemd.debug-shell
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-11-generic N/A
   linux-backports-modules-4.8.0-11-generic  N/A
   linux-firmware1.161
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/09/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G2ET95WW (2.55 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2324CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: 0B98401 Pro
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG2ET95WW(2.55):bd07/09/2013:svnLENOVO:pn2324CTO:pvrThinkPadX230:rvnLENOVO:rn2324CTO:rvr0B98401Pro:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 2324CTO
  dmi.product.version: ThinkPad X230
  dmi.sys.vendor: LENOVO

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1626429] Re: [4.8 regression][ThinkPad X230] brightness change keys do not work any more

[Martin Pitt]

** Attachment added: "pitti's x230 acpidump"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1626429/+attachment/4746382/+files/acpidump-x230.log

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

Title:
  [4.8 regression][ThinkPad X230] brightness change keys do not work any
  more

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  With yakkety's recent update from linux 4.4 to 4.8 my brightness keys
  stopped working. They are not handled in software via evdev events (on
  most platforms you just get a KEY_BRIGHTNESS{UP ../../../:00:02.0
  -r--r--r-- 1 root root 4096 Sep 22 09:45 max_brightness
  drwxr-xr-x 2 root root0 Sep 22 09:45 power
  lrwxrwxrwx 1 root root0 Sep 22 09:45 subsystem -> 
../../../../../class/backlight
  -r--r--r-- 1 root root 4096 Sep 22 09:45 type
  -rw-r--r-- 1 root root 4096 Sep 22 09:45 uevent

  /sys/class/backlight/intel_backlight/:
  -r--r--r-- 1 root root 4096 Sep 22 09:46 actual_brightness
  -rw-r--r-- 1 root root 4096 Sep 22 09:46 bl_power
  -rw-r--r-- 1 root root 4096 Sep 22 09:46 brightness
  lrwxrwxrwx 1 root root0 Sep 22 09:46 device -> ../../card0-LVDS-1
  -r--r--r-- 1 root root 4096 Sep 22 09:46 max_brightness
  drwxr-xr-x 2 root root0 Sep 22 09:46 power
  lrwxrwxrwx 1 root root0 Sep 22 09:46 subsystem -> 
../../../../../../../class/backlight
  -r--r--r-- 1 root root 4096 Sep 22 09:46 type
  -rw-r--r-- 1 root root 4096 Sep 22 09:46 uevent

  While in 4.8 I only have intel_backlight and acpi_video0 is missing
  completely.

  I. e. in 4.4 this command works:

echo 12 | sudo tee /sys/class/backlight/acpi_video0/brightness

  and I suppose this is the moral equivalent of what happens when I
  press the brightness keys,  i. e. these keys seem to be handled by the
  acpi_video0 driver instead of intel_backlight.

  The intel driver still actually works, I can do

echo 1000 | sudo tee /sys/class/backlight/intel_backlight/brightness

  but this isn't connected to the keys any more.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: linux-image-4.8.0-11-generic 4.8.0-11.12
  ProcVersionSignature: Ubuntu 4.8.0-11.12-generic 4.8.0-rc6
  Uname: Linux 4.8.0-11-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   martin 3049 F...m pulseaudio
   /dev/snd/pcmC0D0p:   martin 3049 F...m pulseaudio
   /dev/snd/controlC0:  martin 3049 F pulseaudio
  Date: Thu Sep 22 09:42:56 2016
  EcryptfsInUse: Yes
  MachineType: LENOVO 2324CTO
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.8.0-11-generic.efi.signed 
root=UUID=f86539b0-3a1b-4372-83b0-acdd029ade68 ro rootflags=subvol=@ 
systemd.debug-shell
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-11-generic N/A
   linux-backports-modules-4.8.0-11-generic  N/A
   linux-firmware1.161
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/09/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G2ET95WW (2.55 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2324CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: 0B98401 Pro
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG2ET95WW(2.55):bd07/09/2013:svnLENOVO:pn2324CTO:pvrThinkPadX230:rvnLENOVO:rn2324CTO:rvr0B98401Pro:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 2324CTO
  dmi.product.version: ThinkPad X230
  dmi.sys.vendor: LENOVO

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1626651] Re: brightness keys are handled slower in Yakkety than Xenial

[Martin Pitt]

This looks like one keypress would cause a massive spew of uevents
and/or evdev events. Can you please run  "sudo evtest" and "udevadm
monitor -e", then press a brightness key once, then ^C both and
copy the output?

I don't get this on my ThinkPad X230, I have the opposite problem
(brightness keys not working at all any more with 4.8 due to acpi_video0
disappearing, bug 1626429).

** Changed in: ubuntu
   Status: New => Incomplete

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

Title:
  brightness keys are handled slower in Yakkety than Xenial

Status in linux package in Ubuntu:
  Incomplete
Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  I've noticed on Lenovo X220 and X230 laptops that pressing brightness
  keys on Yakkety seems less responsive and slower than Xenial.  I ran
  forkstat on Xenial and just observed udev being forked off:

  Xenial:
  $ sudo forkstat
  Time Event  PID  Info  Duration Process
  17:37:35 fork273 parent  /lib/systemd/systemd-udevd
  17:37:35 fork   1977 child   /lib/systemd/systemd-udevd
  17:37:35 exit   1977  00.008 /lib/systemd/systemd-udevd

  Whereas on Yakkety, there is far more activity:
  Time Event  PID  Info  Duration Process
  16:35:34 fork   2626 parent  update-notifier
  16:35:34 fork   2645 child   update-notifier
  16:35:34 exec   2645 /usr/bin/python3 
/usr/share/apport/apport-checkreports
  16:35:34 exit   26452560.221 /usr/bin/python3 
/usr/share/apport/apport-checkreports
  16:35:34 fork   2626 parent  update-notifier
  16:35:34 fork   2646 child   update-notifier
  16:35:34 exec   2646 /usr/bin/python3 
/usr/share/apport/apport-checkreports --system
  16:35:34 exit   26462560.188 /usr/bin/python3 
/usr/share/apport/apport-checkreports --system
  16:35:36 fork   1576 parent  
/usr/lib/unity-settings-daemon/unity-settings-daemon
  16:35:36 fork   2647 child   
/usr/lib/unity-settings-daemon/unity-settings-daemon
  16:35:36 exec   2647 
/usr/lib/unity-settings-daemon/usd-backlight-helper --get-max-brightness
  16:35:36 exit   2647  00.008 
/usr/lib/unity-settings-daemon/usd-backlight-helper --get-max-brightness
  16:35:36 fork   1576 parent  
/usr/lib/unity-settings-daemon/unity-settings-daemon
  16:35:36 fork   2648 child   
/usr/lib/unity-settings-daemon/unity-settings-daemon
  16:35:36 exec   2648 
/usr/lib/unity-settings-daemon/usd-backlight-helper --get-brightness
  16:35:36 exit   2648  00.006 
/usr/lib/unity-settings-daemon/usd-backlight-helper --get-brightness
  16:35:36 fork   1576 parent  
/usr/lib/unity-settings-daemon/unity-settings-daemon
  16:35:36 fork   2649 child   
/usr/lib/unity-settings-daemon/unity-settings-daemon
  16:35:36 exec   2649 
/usr/lib/unity-settings-daemon/usd-backlight-helper --get-brightness
  16:35:36 exit   2649  00.007 
/usr/lib/unity-settings-daemon/usd-backlight-helper --get-brightness
  16:35:36 fork   1576 parent  
/usr/lib/unity-settings-daemon/unity-settings-daemon
  16:35:36 fork   2650 child   
/usr/lib/unity-settings-daemon/unity-settings-daemon
  16:35:36 exec   2650 
/usr/lib/unity-settings-daemon/usd-backlight-helper --get-max-brightness
  16:35:36 exit   2650  00.006 
/usr/lib/unity-settings-daemon/usd-backlight-helper --get-max-brightness
  16:35:36 fork   1576 parent  
/usr/lib/unity-settings-daemon/unity-settings-daemon
  16:35:36 fork   2651 child   
/usr/lib/unity-settings-daemon/unity-settings-daemon
  16:35:36 exec   2651 pkexec 
/usr/lib/unity-settings-daemon/usd-backlight-helper --set-brightness 2250
  16:35:36 clone  2651 parent  pkexec 
/usr/lib/unity-settings-daemon/usd-backlight-helper --set-brightness 2250
  16:35:36 clone  2652 thread  pkexec 
/usr/lib/unity-settings-daemon/usd-backlight-helper --set-brightness 2250
  16:35:36 clone  2651 parent  pkexec 
/usr/lib/unity-settings-daemon/usd-backlight-helper --set-brightness 2250
  16:35:36 clone  2653 thread  pkexec 
/usr/lib/unity-settings-daemon/usd-backlight-helper --set-brightness 2250
  16:35:36 fork  1 parent  /sbin/init splash
  16:35:36 fork   2654 child   /sbin/init splash
  Time Event  PID  Info  Duration Process
  16:35:36 fork233 parent  /lib/systemd/systemd-udevd
  16:35:36 fork   2655 child   /lib/systemd/systemd-udevd
  16:35:36 fork233 parent  /lib/systemd/systemd-udevd
  16:35:36 fork   2656 child   /lib/systemd/systemd-udevd
  16:35:36 fork233 parent  /lib/systemd/systemd-udevd
  16:35:36 fork   2657 child   /lib/systemd/systemd-udevd
  16:35:36 fork233 parent

[Kernel-packages] [Bug 1626651] Re: brightness keys are handled slower in Yakkety than Xenial

[Martin Pitt]

Oh, forgot: for evtest you might need to try with several devices, such
as "ThinkPad Extra Buttons" and the actual keyboard.

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

Title:
  brightness keys are handled slower in Yakkety than Xenial

Status in linux package in Ubuntu:
  Incomplete
Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  I've noticed on Lenovo X220 and X230 laptops that pressing brightness
  keys on Yakkety seems less responsive and slower than Xenial.  I ran
  forkstat on Xenial and just observed udev being forked off:

  Xenial:
  $ sudo forkstat
  Time Event  PID  Info  Duration Process
  17:37:35 fork273 parent  /lib/systemd/systemd-udevd
  17:37:35 fork   1977 child   /lib/systemd/systemd-udevd
  17:37:35 exit   1977  00.008 /lib/systemd/systemd-udevd

  Whereas on Yakkety, there is far more activity:
  Time Event  PID  Info  Duration Process
  16:35:34 fork   2626 parent  update-notifier
  16:35:34 fork   2645 child   update-notifier
  16:35:34 exec   2645 /usr/bin/python3 
/usr/share/apport/apport-checkreports
  16:35:34 exit   26452560.221 /usr/bin/python3 
/usr/share/apport/apport-checkreports
  16:35:34 fork   2626 parent  update-notifier
  16:35:34 fork   2646 child   update-notifier
  16:35:34 exec   2646 /usr/bin/python3 
/usr/share/apport/apport-checkreports --system
  16:35:34 exit   26462560.188 /usr/bin/python3 
/usr/share/apport/apport-checkreports --system
  16:35:36 fork   1576 parent  
/usr/lib/unity-settings-daemon/unity-settings-daemon
  16:35:36 fork   2647 child   
/usr/lib/unity-settings-daemon/unity-settings-daemon
  16:35:36 exec   2647 
/usr/lib/unity-settings-daemon/usd-backlight-helper --get-max-brightness
  16:35:36 exit   2647  00.008 
/usr/lib/unity-settings-daemon/usd-backlight-helper --get-max-brightness
  16:35:36 fork   1576 parent  
/usr/lib/unity-settings-daemon/unity-settings-daemon
  16:35:36 fork   2648 child   
/usr/lib/unity-settings-daemon/unity-settings-daemon
  16:35:36 exec   2648 
/usr/lib/unity-settings-daemon/usd-backlight-helper --get-brightness
  16:35:36 exit   2648  00.006 
/usr/lib/unity-settings-daemon/usd-backlight-helper --get-brightness
  16:35:36 fork   1576 parent  
/usr/lib/unity-settings-daemon/unity-settings-daemon
  16:35:36 fork   2649 child   
/usr/lib/unity-settings-daemon/unity-settings-daemon
  16:35:36 exec   2649 
/usr/lib/unity-settings-daemon/usd-backlight-helper --get-brightness
  16:35:36 exit   2649  00.007 
/usr/lib/unity-settings-daemon/usd-backlight-helper --get-brightness
  16:35:36 fork   1576 parent  
/usr/lib/unity-settings-daemon/unity-settings-daemon
  16:35:36 fork   2650 child   
/usr/lib/unity-settings-daemon/unity-settings-daemon
  16:35:36 exec   2650 
/usr/lib/unity-settings-daemon/usd-backlight-helper --get-max-brightness
  16:35:36 exit   2650  00.006 
/usr/lib/unity-settings-daemon/usd-backlight-helper --get-max-brightness
  16:35:36 fork   1576 parent  
/usr/lib/unity-settings-daemon/unity-settings-daemon
  16:35:36 fork   2651 child   
/usr/lib/unity-settings-daemon/unity-settings-daemon
  16:35:36 exec   2651 pkexec 
/usr/lib/unity-settings-daemon/usd-backlight-helper --set-brightness 2250
  16:35:36 clone  2651 parent  pkexec 
/usr/lib/unity-settings-daemon/usd-backlight-helper --set-brightness 2250
  16:35:36 clone  2652 thread  pkexec 
/usr/lib/unity-settings-daemon/usd-backlight-helper --set-brightness 2250
  16:35:36 clone  2651 parent  pkexec 
/usr/lib/unity-settings-daemon/usd-backlight-helper --set-brightness 2250
  16:35:36 clone  2653 thread  pkexec 
/usr/lib/unity-settings-daemon/usd-backlight-helper --set-brightness 2250
  16:35:36 fork  1 parent  /sbin/init splash
  16:35:36 fork   2654 child   /sbin/init splash
  Time Event  PID  Info  Duration Process
  16:35:36 fork233 parent  /lib/systemd/systemd-udevd
  16:35:36 fork   2655 child   /lib/systemd/systemd-udevd
  16:35:36 fork233 parent  /lib/systemd/systemd-udevd
  16:35:36 fork   2656 child   /lib/systemd/systemd-udevd
  16:35:36 fork233 parent  /lib/systemd/systemd-udevd
  16:35:36 fork   2657 child   /lib/systemd/systemd-udevd
  16:35:36 fork233 parent  /lib/systemd/systemd-udevd
  16:35:36 fork   2658 child   /lib/systemd/systemd-udevd
  16:35:36 fork233 parent  /lib/systemd/systemd-udevd
  16:35:36 fork   2659 child   /lib/systemd/systemd-udevd
  16:35:36 exit   2659  00.005 /lib/systemd/systemd-udevd
  16:35:36 exit   

[Kernel-packages] [Bug 1625100] Re: systemd test failure with linux 4.8.0-11.12: scsi_debug missing in ppc64el, systemd-tmpfiles crash

[Martin Pitt]

This was fixed in -14, scsi_debug is back.

** Changed in: linux (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  systemd test failure with linux 4.8.0-11.12: scsi_debug missing in
  ppc64el, systemd-tmpfiles crash

Status in linux package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Invalid

Bug description:
  Testing failed on:
  amd64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-yakkety-canonical-kernel-team-unstable/yakkety/amd64/s/systemd/20160918_093714@/log.gz
  ppc64el: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-yakkety-canonical-kernel-team-unstable/yakkety/ppc64el/s/systemd/20160918_231904@/log.gz

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1625100] Re: systemd test failure with linux 4.8.0-11.12: scsi_debug missing in ppc64el, systemd-tmpfiles crash

[Martin Pitt]

http://autopkgtest.ubuntu.com/packages/s/systemd/yakkety/ppc64el passed
a few times again, and that tmpfiles crash never reproduced.

** Changed in: systemd (Ubuntu)
   Status: Confirmed => Fix Released

** Changed in: systemd (Ubuntu)
   Status: Fix Released => Invalid

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

Title:
  systemd test failure with linux 4.8.0-11.12: scsi_debug missing in
  ppc64el, systemd-tmpfiles crash

Status in linux package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Invalid

Bug description:
  Testing failed on:
  amd64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-yakkety-canonical-kernel-team-unstable/yakkety/amd64/s/systemd/20160918_093714@/log.gz
  ppc64el: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-yakkety-canonical-kernel-team-unstable/yakkety/ppc64el/s/systemd/20160918_231904@/log.gz

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1608499] Update Released

[Martin Pitt]

The verification of the Stable Release Update for dkms has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to dkms in Ubuntu.
https://bugs.launchpad.net/bugs/1608499

Title:
  Parallel depmod failure with dkms autoinstall

Status in dkms package in Ubuntu:
  Fix Released
Status in dkms source package in Trusty:
  Fix Released
Status in dkms source package in Xenial:
  Fix Released

Bug description:
  Description of problem
  --

  "dkms autoinstall" installs DKMS modules in parallel, potentially executing
  several depmod instances in parallel.

  The resulting race condition causes depmod to fail and dkms install as
  well.

  This problem is critical because some DKMS modules can be left in "built"
  state after a kernel upgrade, thus the kernel modules will not be re-installed
  in /lib/modules/.

  Ubuntu release
  --
  # lsb_release -rd
  Description:  Ubuntu 16.04 LTS
  Release:  16.04

  DKMS package version
  

  # apt-cache policy dkms
  dkms:
Installed: 2.2.0.3-2ubuntu11
Candidate: 2.2.0.3-2ubuntu11
Version table:
   *** 2.2.0.3-2ubuntu11 500
  500 http://fr.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  500 http://fr.archive.ubuntu.com/ubuntu xenial/main i386 Packages
  100 /var/lib/dpkg/status

  Steps to reproduce
  --

  Add 2 simple DKMS modules, mod1 and mod2 (test case in attachment) with
  "dkms add", then run "dkms autoinstall".

  # dkms add mod1 ; dkms add mod2

  Creating symlink /var/lib/dkms/mod1/1.0/source ->
   /usr/src/mod1-1.0

  DKMS: add completed.

  Creating symlink /var/lib/dkms/mod2/1.0/source ->
   /usr/src/mod2-1.0

  DKMS: add completed.

  # dkms autoinstall

  Kernel preparation unnecessary for this kernel.  Skipping...

  Building module:
  cleaning build area...
  Kernel preparation unnecessary for this kernel.  Skipping...

  Building module:
  cleaning build area
  .make KERNELRELEASE=4.4.0-28-generic -C /lib/modules/4.4.0-28-generic/build 
SUBDIRS=/var/lib/dkms/mod2/1.0/build S=/var/lib/dkms/mod2/1.0/build modules...
  make KERNELRELEASE=4.4.0-28-generic -C /lib/modules/4.4.0-28-generic/build 
SUBDIRS=/var/lib/dkms/mod1/1.0/build S=/var/lib/dkms/mod1/1.0/build modules.

  cleaning build area...cleaning build area.

  
  DKMS: build completed.

  DKMS: build completed.

  mod2.ko:
  Running module version sanity check.

  mod1.ko:
  Running module version sanity check.
   - Original module
 - No original module exists within this kernel
   - Installation
 - Installing to /lib/modules/4.4.0-28-generic/updates/dkms/
   - Original module
 - No original module exists within this kernel
   - Installation
 - Installing to /lib/modules/4.4.0-28-generic/updates/dkms/

  
  depmod...depmod...(bad exit status: 1)

   Uninstall Beginning 
  Module:  mod2
  Version: 1.0
  Kernel:  4.4.0-28-generic (x86_64)
  -

  
  DKMS: install completed.

  Status: Before uninstall, this module version was ACTIVE on this
  kernel.

  mod2.ko:
   - Uninstallation
 - Deleting from: /lib/modules/4.4.0-28-generic/updates/dkms/
   - Original module
 - No original module was found for this module on this kernel.
 - Use the dkms install command to reinstall any previous module version.

  depmod

  DKMS: uninstall completed.
  Error! Problems with depmod detected.  Automatically uninstalling this module.
  DKMS: Install Failed (depmod problems).  Module rolled back to built state.

  root@ubuntu1604:~/dkms-depmod# dkms status
  mod1, 1.0, 4.4.0-28-generic, x86_64: installed
  mod2, 1.0, 4.4.0-28-generic, x86_64: built

  => mod2 should be in "installed" state as well.

  # modinfo mod1
  filename:   /lib/modules/4.4.0-28-generic/updates/dkms/mod1.ko
  author: 6WIND
  license:GPL
  srcversion: 8D30BAE7A8F4D38F20AEB57
  depends:
  vermagic:   4.4.0-28-generic SMP mod_unload modversions 

  # modinfo mod2
  modinfo: ERROR: Module mod2 not found.

  Solution
  

  The problem is fixed in dkms official repository by commit
  
https://github.com/dell-oss/dkms/commit/00114cbc0a1f8c0aa5143808205d1a7cc9e58d3b
  (also in attachment).

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net

[Kernel-packages] [Bug 1626158] Re: image won't boot after upgrading to yakkety's 4.8 kernel because efi

[Martin Pitt]

> CONFIG_FAT_DEFAULT_IOCHARSET somehow got changed to utf8 instead of
iso8859-1.

Related: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=833238

TL;DR: Use this:
  CONFIG_FAT_DEFAULT_IOCHARSET="ascii"
  FAT_DEFAULT_UTF8=y

** Bug watch added: Debian Bug tracker #833238
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=833238

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

Title:
  image won't boot after upgrading to yakkety's 4.8 kernel because efi

Status in cloud-images:
  Confirmed
Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Xenial:
  New

Bug description:
  If I use a relatively recent yakkety daily with uvt-kvm,

  com.ubuntu.cloud.daily:server:16.10:amd64 20160918

  and upgrade the kernel to the latest kernel (which happens to be 4.8),
  my VM won't boot any more. kern.log has:

  http://paste.ubuntu.com/23211671/

  and systemd complains that,

  [FAILED] Failed to mount /boot/efi
  See 'systemctl status boot-efi.mount' for details.

  and dumps me to a recovery console. Of course, I don't have EFI since
  I'm booting this thing on KVM. The problem here (I think) is that
  /boot/efi is in /etc/fstab, and systemd fails to boot when anything in
  /etc/fstab doesn't work.

  If I comment /boot/efi out of /etc/fstab, it boots just fine.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-images/+bug/1626158/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1626394] Re: 4.8 dropped CONFIG_ATA=y (breaks systemd's TEST-08-ISSUE-2730 upstream test)

[Martin Pitt]

Talked to Andy on IRC, and dropping these drivers was not intended. I
agree we should keep the most common ones built in, especially for cloud
instances; there it would really be beneficial to drop initrds
completely (see bug 1592684), as they are just bloat there.

** Changed in: systemd (Ubuntu)
   Status: In Progress => Won't Fix

** Changed in: systemd (Ubuntu)
Milestone: ubuntu-16.09 => None

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

Title:
  4.8 dropped CONFIG_ATA=y (breaks systemd's TEST-08-ISSUE-2730 upstream
  test)

Status in linux package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Won't Fix

Bug description:
  Since the kernel upgrade from 4.4 to 4.8 in yakkety, systemd's
  TEST-08-ISSUE-2730 upstream test now consistently fails with:

  + timeout --foreground 180 /usr/bin/qemu-system-x86_64 -smp 1 -net none -m 
512M -nographic -kernel /boot/vmlinuz-4.8.0-14-generic -drive 
format=raw,cache=unsafe,file=/var/tmp/systemd-test.4jlHRw/rootdisk.img -append 
'root=/dev/sda1 raid=noautodetect loglevel=2 init=/lib/systemd/systemd ro 
console=ttyS0 selinux=0 systemd.unified_cgroup_hierarchy=no  '
  warning: TCG doesn't support requested feature: CPUID.01H:ECX.vmx [bit 5]
  [1.491760] Kernel panic - not syncing: VFS: Unable to mount root fs on 
unknown-block(0,0)
  [1.492153] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 4.8.0-14-generic 
#15-Ubuntu
  [1.492153] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 
Ubuntu-1.8.2-1ubuntu1 04/01/2014
  [1.492153]  0086 35700369 a8b59c24 
97201dd45000
  [1.492153]  97201e9afea0 a8987431 0010 
97201e9afeb0
  [1.492153]  97201e9afe48 35700369 97201e9afe58 
97201e9afeb8
  [1.492153] Call Trace:
  [1.492153]  [] ? dump_stack+0x5c/0x78
  [1.492153]  [] ? panic+0xe4/0x226
  [1.492153]  [] ? mount_block_root+0x284/0x2c0
  [1.492153]  [] ? set_debug_rodata+0xc/0xc
  [1.492153]  [] ? prepare_namespace+0x12b/0x180
  [1.492153]  [] ? kernel_init_freeable+0x1dd/0x1ed
  [1.492153]  [] ? kernel_init+0xa/0x100
  [1.492153]  [] ? ret_from_fork+0x1f/0x40
  [1.492153]  [] ? rest_init+0x80/0x80
  [1.492153] Kernel Offset: 0x2780 from 0x8100 (relocation 
range: 0x8000-0xbfff)
  [1.492153] ---[ end Kernel panic - not syncing: VFS: Unable to mount root 
fs on unknown-block(0,0)
  qemu-system-x86_64: terminating on signal 15 from pid 8784

  This only happens on amd64, i386 and ppc64el are fine.
  http://autopkgtest.ubuntu.com/packages/systemd/yakkety/amd64

  I'll investigate more details, filing this for getting a reference for
  the britney hint.

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1626394] Re: 4.8 dropped CONFIG_ATA=y (breaks systemd's TEST-08-ISSUE-2730 upstream test)

[Martin Pitt]

> This only happens on amd64, i386 and ppc64el are fine.

FTR, this is because we run the qemu tests only on amd64. i386 also has
CONFIG_ATA=m now.

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

Title:
  4.8 dropped CONFIG_ATA=y (breaks systemd's TEST-08-ISSUE-2730 upstream
  test)

Status in linux package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  In Progress

Bug description:
  Since the kernel upgrade from 4.4 to 4.8 in yakkety, systemd's
  TEST-08-ISSUE-2730 upstream test now consistently fails with:

  + timeout --foreground 180 /usr/bin/qemu-system-x86_64 -smp 1 -net none -m 
512M -nographic -kernel /boot/vmlinuz-4.8.0-14-generic -drive 
format=raw,cache=unsafe,file=/var/tmp/systemd-test.4jlHRw/rootdisk.img -append 
'root=/dev/sda1 raid=noautodetect loglevel=2 init=/lib/systemd/systemd ro 
console=ttyS0 selinux=0 systemd.unified_cgroup_hierarchy=no  '
  warning: TCG doesn't support requested feature: CPUID.01H:ECX.vmx [bit 5]
  [1.491760] Kernel panic - not syncing: VFS: Unable to mount root fs on 
unknown-block(0,0)
  [1.492153] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 4.8.0-14-generic 
#15-Ubuntu
  [1.492153] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 
Ubuntu-1.8.2-1ubuntu1 04/01/2014
  [1.492153]  0086 35700369 a8b59c24 
97201dd45000
  [1.492153]  97201e9afea0 a8987431 0010 
97201e9afeb0
  [1.492153]  97201e9afe48 35700369 97201e9afe58 
97201e9afeb8
  [1.492153] Call Trace:
  [1.492153]  [] ? dump_stack+0x5c/0x78
  [1.492153]  [] ? panic+0xe4/0x226
  [1.492153]  [] ? mount_block_root+0x284/0x2c0
  [1.492153]  [] ? set_debug_rodata+0xc/0xc
  [1.492153]  [] ? prepare_namespace+0x12b/0x180
  [1.492153]  [] ? kernel_init_freeable+0x1dd/0x1ed
  [1.492153]  [] ? kernel_init+0xa/0x100
  [1.492153]  [] ? ret_from_fork+0x1f/0x40
  [1.492153]  [] ? rest_init+0x80/0x80
  [1.492153] Kernel Offset: 0x2780 from 0x8100 (relocation 
range: 0x8000-0xbfff)
  [1.492153] ---[ end Kernel panic - not syncing: VFS: Unable to mount root 
fs on unknown-block(0,0)
  qemu-system-x86_64: terminating on signal 15 from pid 8784

  This only happens on amd64, i386 and ppc64el are fine.
  http://autopkgtest.ubuntu.com/packages/systemd/yakkety/amd64

  I'll investigate more details, filing this for getting a reference for
  the britney hint.

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1626394] Re: 4.8/amd64 dropped CONFIG_ATA=y (breaks systemd's TEST-08-ISSUE-2730 upstream test)

[Martin Pitt]

This is the first test that boots the root disk without an initrd.
Indeed booting it with debug shows that the kernel detects no hard disks
then (in particular not /dev/sda1), thus the boot fails like that.

With 4.4, or with 4.8 and booting with an initrd it detects the sda hard
drive again:

[2.374065] ata1: PATA max MWDMA2 cmd 0x1f0 ctl 0x3f6 bmdma 0xc000 irq 14
[2.383381] ata2: PATA max MWDMA2 cmd 0x170 ctl 0x376 bmdma 0xc008 irq 15
[2.563557] ata2.01: NODEV after polling detection
[2.583452] ata1.01: NODEV after polling detection
[2.600806] ata1.00: ATA-7: QEMU HARDDISK, 2.5+, max UDMA/100
[2.617551] ata1.00: 819200 sectors, multi 16: LBA48 
[2.632337] ata2.00: ATAPI: QEMU DVD-ROM, 2.5+, max UDMA/100
[2.649576] ata2.00: configured for MWDMA2
[2.662298] ata1.00: configured for MWDMA2
[2.671218] scsi 0:0:0:0: Direct-Access ATA  QEMU HARDDISK2.5+ 
PQ: 0 ANSI: 5

I think this is due to this config change:

$ grep CONFIG_ATA= config-4.*
config-4.4.0-9136-generic:CONFIG_ATA=y
config-4.8.0-14-generic:CONFIG_ATA=m

Which would by and large mean that it is now impossible to boot without
an initrd. I don't think this is desirable, as it could actually lead to
regressions on existing machines.


** Summary changed:

- 4.8 update breaks systemd's TEST-08-ISSUE-2730 upstream test
+ 4.8/amd64 dropped CONFIG_ATA=y (breaks systemd's TEST-08-ISSUE-2730 upstream 
test)

** Summary changed:

- 4.8/amd64 dropped CONFIG_ATA=y (breaks systemd's TEST-08-ISSUE-2730 upstream 
test)
+ 4.8 dropped CONFIG_ATA=y (breaks systemd's TEST-08-ISSUE-2730 upstream test)

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

Title:
  4.8 dropped CONFIG_ATA=y (breaks systemd's TEST-08-ISSUE-2730 upstream
  test)

Status in linux package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  In Progress

Bug description:
  Since the kernel upgrade from 4.4 to 4.8 in yakkety, systemd's
  TEST-08-ISSUE-2730 upstream test now consistently fails with:

  + timeout --foreground 180 /usr/bin/qemu-system-x86_64 -smp 1 -net none -m 
512M -nographic -kernel /boot/vmlinuz-4.8.0-14-generic -drive 
format=raw,cache=unsafe,file=/var/tmp/systemd-test.4jlHRw/rootdisk.img -append 
'root=/dev/sda1 raid=noautodetect loglevel=2 init=/lib/systemd/systemd ro 
console=ttyS0 selinux=0 systemd.unified_cgroup_hierarchy=no  '
  warning: TCG doesn't support requested feature: CPUID.01H:ECX.vmx [bit 5]
  [1.491760] Kernel panic - not syncing: VFS: Unable to mount root fs on 
unknown-block(0,0)
  [1.492153] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 4.8.0-14-generic 
#15-Ubuntu
  [1.492153] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 
Ubuntu-1.8.2-1ubuntu1 04/01/2014
  [1.492153]  0086 35700369 a8b59c24 
97201dd45000
  [1.492153]  97201e9afea0 a8987431 0010 
97201e9afeb0
  [1.492153]  97201e9afe48 35700369 97201e9afe58 
97201e9afeb8
  [1.492153] Call Trace:
  [1.492153]  [] ? dump_stack+0x5c/0x78
  [1.492153]  [] ? panic+0xe4/0x226
  [1.492153]  [] ? mount_block_root+0x284/0x2c0
  [1.492153]  [] ? set_debug_rodata+0xc/0xc
  [1.492153]  [] ? prepare_namespace+0x12b/0x180
  [1.492153]  [] ? kernel_init_freeable+0x1dd/0x1ed
  [1.492153]  [] ? kernel_init+0xa/0x100
  [1.492153]  [] ? ret_from_fork+0x1f/0x40
  [1.492153]  [] ? rest_init+0x80/0x80
  [1.492153] Kernel Offset: 0x2780 from 0x8100 (relocation 
range: 0x8000-0xbfff)
  [1.492153] ---[ end Kernel panic - not syncing: VFS: Unable to mount root 
fs on unknown-block(0,0)
  qemu-system-x86_64: terminating on signal 15 from pid 8784

  This only happens on amd64, i386 and ppc64el are fine.
  http://autopkgtest.ubuntu.com/packages/systemd/yakkety/amd64

  I'll investigate more details, filing this for getting a reference for
  the britney hint.

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1626436] Re: [4.8 regression] boot has become very slow

[Martin Pitt]

I do not see this in QEMU (even with -smp 4), only on my laptop. At this
point I'm not sure if it is specific to my ThinkPad X230 or happens for
others too.

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

Title:
  [4.8 regression] boot has become very slow

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  With yakkety's recent update from linux 4.4 to 4.8 booting has become
  a lot slower. It's not one service in particular, but without "quiet"
  and "splash" you can now easily read every single line instead of that
  whole wall of text zipping by. It now takes over 20s instead of ~10
  seconds to boot.

  This is even more dramatic when factoring out the recent boot hang of
  NetworkManager (bug 1622893) and disabling lightdm:

sudo systemctl mask NetworkManager NetworkManager-wait-online
  lightdm

  then booting with 4.4 takes 1.5s and with 4.8 19.5s (!).

  Some excerps from systemd-analyze blame:

  4.4:
 474ms postfix@-.service
 395ms lxd-containers.service
 305ms networking.service

  4.8:
4.578s postfix@-.service
7.300s lxd-containers.service
6.285s networking.service

  I attach the full outputs of critical-chain and analyze for 4.4 and
  4.8 for reference.

  
  This is much less noticeable in the running system. There is no immediate 
feeling of sluggishness (although my system is by and large idle).

  I compared the time of sbuilding colord under similar circumstances
  (-j4, building on tmpfs, thus no hard disk delays; running with fully
  pre-loaded apt-cacher-ng thus no random network delays), and with 4.4
  it takes 6.5 minutes and with 4.8 it takes 7.5. So that got a bit
  slower, but much less dramatically than during boot, so this is either
  happening when a lot of processes run in parallel, or is perhaps
  related to setting up cgroups.

  One thing I noticed that during sbuild in 4.8 "top" shows ridiculous
  loads (~ 250) under 4.8, while it's around 4 or 5 under 4.8. But that
  doesn't reflect in actual sluggishness, so this might be just an
  unrelated bug.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: linux-image-4.8.0-11-generic 4.8.0-11.12
  ProcVersionSignature: Ubuntu 4.8.0-11.12-generic 4.8.0-rc6
  Uname: Linux 4.8.0-11-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   martin 3049 F...m pulseaudio
   /dev/snd/pcmC0D0p:   martin 3049 F...m pulseaudio
   /dev/snd/controlC0:  martin 3049 F pulseaudio
  Date: Thu Sep 22 09:42:56 2016
  EcryptfsInUse: Yes
  MachineType: LENOVO 2324CTO
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.8.0-11-generic.efi.signed 
root=UUID=f86539b0-3a1b-4372-83b0-acdd029ade68 ro rootflags=subvol=@ 
systemd.debug-shell
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-11-generic N/A
   linux-backports-modules-4.8.0-11-generic  N/A
   linux-firmware1.161
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/09/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G2ET95WW (2.55 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2324CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: 0B98401 Pro
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG2ET95WW(2.55):bd07/09/2013:svnLENOVO:pn2324CTO:pvrThinkPadX230:rvnLENOVO:rn2324CTO:rvr0B98401Pro:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 2324CTO
  dmi.product.version: ThinkPad X230
  dmi.sys.vendor: LENOVO

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp