date:20181108

Need to check this for the next cycle, or it's been replaced by 1802233

** Changed in: ubuntu-kernel-tests
   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/1775858

Title:
  hwclock test failed on Power8 / Power9 system with Bionic kernel

Status in ubuntu-kernel-tests:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  $ /sbin/hwclock --debug --set --date "2004/10/20 04:10:00"
  hwclock from util-linux 2.31.1
  System Time: 1528467313.266333
  Trying to open: /dev/rtc0
  No usable clock interface found.
  hwclock: Cannot access the Hardware Clock via any known method.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-22-generic 4.15.0-22.24
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic ppc64le
  ApportVersion: 2.20.9-0ubuntu7.1
  Architecture: ppc64el
  Date: Fri Jun  8 14:05:13 2018
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcLoadAvg: 0.04 0.67 0.79 1/1401 6691
  ProcSwaps:
   Filename TypeSizeUsedPriority
   /swap.img   file 8388544 0   -2
  ProcVersion: Linux version 4.15.0-22-generic (buildd@bos02-ppc64el-009) (gcc 
version 7.3.0 (Ubuntu 7.3.0-16ubuntu3)) #24-Ubuntu SMP Wed May 16 12:12:37 UTC 
2018
  SourcePackage: linux-signed
  UpgradeStatus: No upgrade log present (probably fresh install)
  VarLogDump_list: total 0
  cpu_cores: Number of cores present = 40
  cpu_coreson: Number of cores online = 40
  cpu_dscr: DSCR is 0
  cpu_freq:
   min: 2.796 GHz (cpu 79)
   max: 2.850 GHz (cpu 81)
   avg: 2.823 GHz
  cpu_runmode:
   Could not retrieve current diagnostics mode,
   No kernel interface to firmware
  cpu_smt: SMT=4

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1775858/+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 1802454] Missing required logs.

This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:

apport-collect 1802454

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a comment stating that fact and change
the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the
Ubuntu Kernel Team.

** Changed in: linux (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/1802454

Title:
  fanotify10 in ubuntu_ltp_syscalls failed

Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  This is a new test case that landed 7 days ago.

  <<>>
  tag=fanotify10 stime=1541744937
  cmdline="fanotify10"
  contacts=""
  analysis=exit
  <<>>
  incrementing stop
  tst_device.c:230: INFO: Using test device LTP_DEV='/dev/loop1'
  tst_mkfs.c:90: INFO: Formatting /dev/loop1 with ext2 opts='' extra opts=''
  mke2fs 1.44.1 (24-Mar-2018)
  tst_test.c:1085: INFO: Timeout per run is 0h 05m 00s
  fanotify10.c:199: INFO: Test #0: ignore mount events created on a specific 
file
  fanotify10.c:187: PASS: group 0 got event: mask 20 pid=2840 fd=15
  fanotify10.c:187: PASS: group 1 got event: mask 20 pid=2840 fd=15
  fanotify10.c:187: PASS: group 2 got event: mask 20 pid=2840 fd=15
  fanotify10.c:264: PASS: group 0 (prio 1) with FAN_MARK_MOUNT and 
FAN_MARK_INODE ignore mask got no event
  fanotify10.c:264: PASS: group 1 (prio 1) with FAN_MARK_MOUNT and 
FAN_MARK_INODE ignore mask got no event
  fanotify10.c:264: PASS: group 2 (prio 1) with FAN_MARK_MOUNT and 
FAN_MARK_INODE ignore mask got no event
  fanotify10.c:264: PASS: group 0 (prio 2) with FAN_MARK_MOUNT and 
FAN_MARK_INODE ignore mask got no event
  fanotify10.c:264: PASS: group 1 (prio 2) with FAN_MARK_MOUNT and 
FAN_MARK_INODE ignore mask got no event
  fanotify10.c:264: PASS: group 2 (prio 2) with FAN_MARK_MOUNT and 
FAN_MARK_INODE ignore mask got no event
  fanotify10.c:199: INFO: Test #1: don't ignore mount events created on another 
file
  fanotify10.c:187: PASS: group 0 got event: mask 20 pid=2840 fd=15
  fanotify10.c:187: PASS: group 1 got event: mask 20 pid=2840 fd=15
  fanotify10.c:187: PASS: group 2 got event: mask 20 pid=2840 fd=15
  fanotify10.c:187: PASS: group 0 got event: mask 20 pid=2840 fd=15
  fanotify10.c:187: PASS: group 1 got event: mask 20 pid=2840 fd=15
  fanotify10.c:187: PASS: group 2 got event: mask 20 pid=2840 fd=15
  fanotify10.c:187: PASS: group 0 got event: mask 20 pid=2840 fd=15
  fanotify10.c:187: PASS: group 1 got event: mask 20 pid=2840 fd=15
  fanotify10.c:187: PASS: group 2 got event: mask 20 pid=2840 fd=15
  fanotify10.c:199: INFO: Test #2: ignore inode events created on a specific 
mount point
  fanotify10.c:187: PASS: group 0 got event: mask 20 pid=2840 fd=15
  fanotify10.c:187: PASS: group 1 got event: mask 20 pid=2840 fd=15
  fanotify10.c:187: PASS: group 2 got event: mask 20 pid=2840 fd=15
  fanotify10.c:258: FAIL: group 0 (prio 1) with FAN_MARK_INODE and 
FAN_MARK_MOUNT ignore mask got event
  fanotify10.c:258: FAIL: group 1 (prio 1) with FAN_MARK_INODE and 
FAN_MARK_MOUNT ignore mask got event
  fanotify10.c:258: FAIL: group 2 (prio 1) with FAN_MARK_INODE and 
FAN_MARK_MOUNT ignore mask got event
  fanotify10.c:258: FAIL: group 0 (prio 2) with FAN_MARK_INODE and 
FAN_MARK_MOUNT ignore mask got event
  fanotify10.c:258: FAIL: group 1 (prio 2) with FAN_MARK_INODE and 
FAN_MARK_MOUNT ignore mask got event
  fanotify10.c:258: FAIL: group 2 (prio 2) with FAN_MARK_INODE and 
FAN_MARK_MOUNT ignore mask got event
  fanotify10.c:199: INFO: Test #3: don't ignore inode events created on another 
mount point
  fanotify10.c:187: PASS: group 0 got event: mask 20 pid=2840 fd=15
  fanotify10.c:187: PASS: group 1 got event: mask 20 pid=2840 fd=15
  fanotify10.c:187: PASS: group 2 got event: mask 20 pid=2840 fd=15
  fanotify10.c:187: PASS: group 0 got event: mask 20 pid=2840 fd=15
  fanotify10.c:187: PASS: group 1 got event: mask 20 pid=2840 fd=15
  fanotify10.c:187: PASS: group 2 got event: mask 20 pid=2840 fd=15
  fanotify10.c:187: PASS: group 0 got event: mask 20 pid=2840 fd=15
  fanotify10.c:187: PASS: group 1 got event: mask 20 pid=2840 fd=15
  fanotify10.c:187: PASS: group 2 got event: mask 20 pid=2840 fd=15

  Summary:
  passed   30
  failed   6
  skipped  0
  warnings 0
  <<>>
  initiation_status="ok"
  duration=1 termination_type=exited termination_id=1 corefile=no
  cutime=0 cstime=1
  <<>>

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.18.0-11-generic 4.18.0-11.12~18.04.1
  ProcVersionSignature: User Name 4.18.0-11.12~18.04.1-generic 4.18.12
  Uname: Linux 4.18.0-11-generic x86_64

[Kernel-packages] [Bug 1802454] Re: fanotify10 in ubuntu_ltp_syscalls failed

Can be reproduced on different kernels.

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

Title:
  fanotify10 in ubuntu_ltp_syscalls failed

Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  New

Bug description:
  This is a new test case that landed 7 days ago.

  <<>>
  tag=fanotify10 stime=1541744937
  cmdline="fanotify10"
  contacts=""
  analysis=exit
  <<>>
  incrementing stop
  tst_device.c:230: INFO: Using test device LTP_DEV='/dev/loop1'
  tst_mkfs.c:90: INFO: Formatting /dev/loop1 with ext2 opts='' extra opts=''
  mke2fs 1.44.1 (24-Mar-2018)
  tst_test.c:1085: INFO: Timeout per run is 0h 05m 00s
  fanotify10.c:199: INFO: Test #0: ignore mount events created on a specific 
file
  fanotify10.c:187: PASS: group 0 got event: mask 20 pid=2840 fd=15
  fanotify10.c:187: PASS: group 1 got event: mask 20 pid=2840 fd=15
  fanotify10.c:187: PASS: group 2 got event: mask 20 pid=2840 fd=15
  fanotify10.c:264: PASS: group 0 (prio 1) with FAN_MARK_MOUNT and 
FAN_MARK_INODE ignore mask got no event
  fanotify10.c:264: PASS: group 1 (prio 1) with FAN_MARK_MOUNT and 
FAN_MARK_INODE ignore mask got no event
  fanotify10.c:264: PASS: group 2 (prio 1) with FAN_MARK_MOUNT and 
FAN_MARK_INODE ignore mask got no event
  fanotify10.c:264: PASS: group 0 (prio 2) with FAN_MARK_MOUNT and 
FAN_MARK_INODE ignore mask got no event
  fanotify10.c:264: PASS: group 1 (prio 2) with FAN_MARK_MOUNT and 
FAN_MARK_INODE ignore mask got no event
  fanotify10.c:264: PASS: group 2 (prio 2) with FAN_MARK_MOUNT and 
FAN_MARK_INODE ignore mask got no event
  fanotify10.c:199: INFO: Test #1: don't ignore mount events created on another 
file
  fanotify10.c:187: PASS: group 0 got event: mask 20 pid=2840 fd=15
  fanotify10.c:187: PASS: group 1 got event: mask 20 pid=2840 fd=15
  fanotify10.c:187: PASS: group 2 got event: mask 20 pid=2840 fd=15
  fanotify10.c:187: PASS: group 0 got event: mask 20 pid=2840 fd=15
  fanotify10.c:187: PASS: group 1 got event: mask 20 pid=2840 fd=15
  fanotify10.c:187: PASS: group 2 got event: mask 20 pid=2840 fd=15
  fanotify10.c:187: PASS: group 0 got event: mask 20 pid=2840 fd=15
  fanotify10.c:187: PASS: group 1 got event: mask 20 pid=2840 fd=15
  fanotify10.c:187: PASS: group 2 got event: mask 20 pid=2840 fd=15
  fanotify10.c:199: INFO: Test #2: ignore inode events created on a specific 
mount point
  fanotify10.c:187: PASS: group 0 got event: mask 20 pid=2840 fd=15
  fanotify10.c:187: PASS: group 1 got event: mask 20 pid=2840 fd=15
  fanotify10.c:187: PASS: group 2 got event: mask 20 pid=2840 fd=15
  fanotify10.c:258: FAIL: group 0 (prio 1) with FAN_MARK_INODE and 
FAN_MARK_MOUNT ignore mask got event
  fanotify10.c:258: FAIL: group 1 (prio 1) with FAN_MARK_INODE and 
FAN_MARK_MOUNT ignore mask got event
  fanotify10.c:258: FAIL: group 2 (prio 1) with FAN_MARK_INODE and 
FAN_MARK_MOUNT ignore mask got event
  fanotify10.c:258: FAIL: group 0 (prio 2) with FAN_MARK_INODE and 
FAN_MARK_MOUNT ignore mask got event
  fanotify10.c:258: FAIL: group 1 (prio 2) with FAN_MARK_INODE and 
FAN_MARK_MOUNT ignore mask got event
  fanotify10.c:258: FAIL: group 2 (prio 2) with FAN_MARK_INODE and 
FAN_MARK_MOUNT ignore mask got event
  fanotify10.c:199: INFO: Test #3: don't ignore inode events created on another 
mount point
  fanotify10.c:187: PASS: group 0 got event: mask 20 pid=2840 fd=15
  fanotify10.c:187: PASS: group 1 got event: mask 20 pid=2840 fd=15
  fanotify10.c:187: PASS: group 2 got event: mask 20 pid=2840 fd=15
  fanotify10.c:187: PASS: group 0 got event: mask 20 pid=2840 fd=15
  fanotify10.c:187: PASS: group 1 got event: mask 20 pid=2840 fd=15
  fanotify10.c:187: PASS: group 2 got event: mask 20 pid=2840 fd=15
  fanotify10.c:187: PASS: group 0 got event: mask 20 pid=2840 fd=15
  fanotify10.c:187: PASS: group 1 got event: mask 20 pid=2840 fd=15
  fanotify10.c:187: PASS: group 2 got event: mask 20 pid=2840 fd=15

  Summary:
  passed   30
  failed   6
  skipped  0
  warnings 0
  <<>>
  initiation_status="ok"
  duration=1 termination_type=exited termination_id=1 corefile=no
  cutime=0 cstime=1
  <<>>

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.18.0-11-generic 4.18.0-11.12~18.04.1
  ProcVersionSignature: User Name 4.18.0-11.12~18.04.1-generic 4.18.12
  Uname: Linux 4.18.0-11-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  Date: Fri Nov  9 06:24:06 2018
  SourcePackage: linux-signed-hwe-edge
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1802454/+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 1802454] [NEW] fanotify10 in ubuntu_ltp_syscalls failed

Public bug reported:

This is a new test case that landed 7 days ago.

<<>>
tag=fanotify10 stime=1541744937
cmdline="fanotify10"
contacts=""
analysis=exit
<<>>
incrementing stop
tst_device.c:230: INFO: Using test device LTP_DEV='/dev/loop1'
tst_mkfs.c:90: INFO: Formatting /dev/loop1 with ext2 opts='' extra opts=''
mke2fs 1.44.1 (24-Mar-2018)
tst_test.c:1085: INFO: Timeout per run is 0h 05m 00s
fanotify10.c:199: INFO: Test #0: ignore mount events created on a specific file
fanotify10.c:187: PASS: group 0 got event: mask 20 pid=2840 fd=15
fanotify10.c:187: PASS: group 1 got event: mask 20 pid=2840 fd=15
fanotify10.c:187: PASS: group 2 got event: mask 20 pid=2840 fd=15
fanotify10.c:264: PASS: group 0 (prio 1) with FAN_MARK_MOUNT and FAN_MARK_INODE 
ignore mask got no event
fanotify10.c:264: PASS: group 1 (prio 1) with FAN_MARK_MOUNT and FAN_MARK_INODE 
ignore mask got no event
fanotify10.c:264: PASS: group 2 (prio 1) with FAN_MARK_MOUNT and FAN_MARK_INODE 
ignore mask got no event
fanotify10.c:264: PASS: group 0 (prio 2) with FAN_MARK_MOUNT and FAN_MARK_INODE 
ignore mask got no event
fanotify10.c:264: PASS: group 1 (prio 2) with FAN_MARK_MOUNT and FAN_MARK_INODE 
ignore mask got no event
fanotify10.c:264: PASS: group 2 (prio 2) with FAN_MARK_MOUNT and FAN_MARK_INODE 
ignore mask got no event
fanotify10.c:199: INFO: Test #1: don't ignore mount events created on another 
file
fanotify10.c:187: PASS: group 0 got event: mask 20 pid=2840 fd=15
fanotify10.c:187: PASS: group 1 got event: mask 20 pid=2840 fd=15
fanotify10.c:187: PASS: group 2 got event: mask 20 pid=2840 fd=15
fanotify10.c:187: PASS: group 0 got event: mask 20 pid=2840 fd=15
fanotify10.c:187: PASS: group 1 got event: mask 20 pid=2840 fd=15
fanotify10.c:187: PASS: group 2 got event: mask 20 pid=2840 fd=15
fanotify10.c:187: PASS: group 0 got event: mask 20 pid=2840 fd=15
fanotify10.c:187: PASS: group 1 got event: mask 20 pid=2840 fd=15
fanotify10.c:187: PASS: group 2 got event: mask 20 pid=2840 fd=15
fanotify10.c:199: INFO: Test #2: ignore inode events created on a specific 
mount point
fanotify10.c:187: PASS: group 0 got event: mask 20 pid=2840 fd=15
fanotify10.c:187: PASS: group 1 got event: mask 20 pid=2840 fd=15
fanotify10.c:187: PASS: group 2 got event: mask 20 pid=2840 fd=15
fanotify10.c:258: FAIL: group 0 (prio 1) with FAN_MARK_INODE and FAN_MARK_MOUNT 
ignore mask got event
fanotify10.c:258: FAIL: group 1 (prio 1) with FAN_MARK_INODE and FAN_MARK_MOUNT 
ignore mask got event
fanotify10.c:258: FAIL: group 2 (prio 1) with FAN_MARK_INODE and FAN_MARK_MOUNT 
ignore mask got event
fanotify10.c:258: FAIL: group 0 (prio 2) with FAN_MARK_INODE and FAN_MARK_MOUNT 
ignore mask got event
fanotify10.c:258: FAIL: group 1 (prio 2) with FAN_MARK_INODE and FAN_MARK_MOUNT 
ignore mask got event
fanotify10.c:258: FAIL: group 2 (prio 2) with FAN_MARK_INODE and FAN_MARK_MOUNT 
ignore mask got event
fanotify10.c:199: INFO: Test #3: don't ignore inode events created on another 
mount point
fanotify10.c:187: PASS: group 0 got event: mask 20 pid=2840 fd=15
fanotify10.c:187: PASS: group 1 got event: mask 20 pid=2840 fd=15
fanotify10.c:187: PASS: group 2 got event: mask 20 pid=2840 fd=15
fanotify10.c:187: PASS: group 0 got event: mask 20 pid=2840 fd=15
fanotify10.c:187: PASS: group 1 got event: mask 20 pid=2840 fd=15
fanotify10.c:187: PASS: group 2 got event: mask 20 pid=2840 fd=15
fanotify10.c:187: PASS: group 0 got event: mask 20 pid=2840 fd=15
fanotify10.c:187: PASS: group 1 got event: mask 20 pid=2840 fd=15
fanotify10.c:187: PASS: group 2 got event: mask 20 pid=2840 fd=15

Summary:
passed   30
failed   6
skipped  0
warnings 0
<<>>
initiation_status="ok"
duration=1 termination_type=exited termination_id=1 corefile=no
cutime=0 cstime=1
<<>>

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-image-4.18.0-11-generic 4.18.0-11.12~18.04.1
ProcVersionSignature: User Name 4.18.0-11.12~18.04.1-generic 4.18.12
Uname: Linux 4.18.0-11-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.4
Architecture: amd64
Date: Fri Nov  9 06:24:06 2018
SourcePackage: linux-signed-hwe-edge
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: ubuntu-kernel-tests
 Importance: Undecided
 Status: New

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


** Tags: amd64 apport-bug bionic package-from-proposed uec-images

** Package changed: linux-signed-hwe-edge (Ubuntu) => linux (Ubuntu)

** Also affects: ubuntu-kernel-tests
   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/1802454

Title:
  fanotify10 in ubuntu_ltp_syscalls failed

Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  New

Bug description:
  This is a new test case that landed 7 days ago.

  <<>>
  tag=fanotify10 stime=1541744937
  cmdline="fanotify10"
  contacts=""
  analysis=exit
  <<>>

[Kernel-packages] [Bug 1789746] Re: getxattr: always handle namespaced attributes

2018-11-08 Thread Stéphane Graber

** Changed in: linux (Ubuntu Xenial)
   Status: Fix Committed => 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/1789746

Title:
  getxattr: always handle namespaced attributes

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Fix Released
Status in linux source package in Bionic:
  Fix Released
Status in linux source package in Cosmic:
  Fix Released

Bug description:
  
  == SRU Justification ==
  When running in a container with a user namespace, if you call getxattr
  with name = "system.posix_acl_access" and size % 8 != 4, then getxattr
  silently skips the user namespace fixup that it normally does resulting in
  un-fixed-up data being returned.
  This is caused by posix_acl_fix_xattr_to_user() being passed the total
  buffer size and not the actual size of the xattr as returned by
  vfs_getxattr().

  I have pushed a commit upstream that fixes this bug:

  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=82c9a927bc5df6e06b72d206d24a9d10cced4eb5

  This commit passes the actual length of the xattr as returned by
  vfs_getxattr() down.

  A reproducer for the issue is:

    touch acl_posix

    setfacl -m user:0:rwx acl_posix

  and the compile:

    #define _GNU_SOURCE
    #include 
    #include 
    #include 
    #include 
    #include 
    #include 
    #include 

    /* Run in user namespace with nsuid 0 mapped to uid != 0 on the host. */
    int main(int argc, void **argv)
    {
    ssize_t ret1, ret2;
    char buf1[128], buf2[132];
    int fret = EXIT_SUCCESS;
    char *file;

    if (argc < 2) {
    fprintf(stderr,
    "Please specify a file with "
    "\"system.posix_acl_access\" permissions set\n");
    _exit(EXIT_FAILURE);
    }
    file = argv[1];

    ret1 = getxattr(file, "system.posix_acl_access",
    buf1, sizeof(buf1));
    if (ret1 < 0) {
    fprintf(stderr, "%s - Failed to retrieve "
    "\"system.posix_acl_access\" "
    "from \"%s\"\n", strerror(errno), file);
    _exit(EXIT_FAILURE);
    }

    ret2 = getxattr(file, "system.posix_acl_access",
    buf2, sizeof(buf2));
    if (ret2 < 0) {
    fprintf(stderr, "%s - Failed to retrieve "
    "\"system.posix_acl_access\" "
    "from \"%s\"\n", strerror(errno), file);
    _exit(EXIT_FAILURE);
    }

    if (ret1 != ret2) {
    fprintf(stderr, "The value of \"system.posix_acl_"
    "access\" for file \"%s\" changed "
    "between two successive calls\n", file);
    _exit(EXIT_FAILURE);
    }

    for (ssize_t i = 0; i < ret2; i++) {
    if (buf1[i] == buf2[i])
    continue;

    fprintf(stderr,
    "Unexpected different in byte %zd: "
    "%02x != %02x\n", i, buf1[i], buf2[i]);
    fret = EXIT_FAILURE;
    }

    if (fret == EXIT_SUCCESS)
    fprintf(stderr, "Test passed\n");
    else
    fprintf(stderr, "Test failed\n");

    _exit(fret);
    }
  and run:

    ./tester acl_posix

  On a non-fixed up kernel this should return something like:

    root@c1:/# ./t
    Unexpected different in byte 16: ffa0 != 00
    Unexpected different in byte 17: ff86 != 00
    Unexpected different in byte 18: 01 != 00

  and on a fixed kernel:

    root@c1:~# ./t
    Test passed

  
  == Fix ==
  82c9a927bc5d ("getxattr: use correct xattr length")

  == Regression Potential ==
  Low.  One liner that passes the actual length of the xattr as returned by
  vfs_getxattr() down.

  == Test Case ==
  A test kernel was built with this patch and tested by the original bug 
reporter.
  The bug reporter states the test kernel resolved the bug.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1789746/+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 1802454] [NEW] fanotify10 in ubuntu_ltp_syscalls failed

2018-11-08 Thread Launchpad Bug Tracker

You have been subscribed to a public bug:

This is a new test case that landed 7 days ago.

<<>>
tag=fanotify10 stime=1541744937
cmdline="fanotify10"
contacts=""
analysis=exit
<<>>
incrementing stop
tst_device.c:230: INFO: Using test device LTP_DEV='/dev/loop1'
tst_mkfs.c:90: INFO: Formatting /dev/loop1 with ext2 opts='' extra opts=''
mke2fs 1.44.1 (24-Mar-2018)
tst_test.c:1085: INFO: Timeout per run is 0h 05m 00s
fanotify10.c:199: INFO: Test #0: ignore mount events created on a specific file
fanotify10.c:187: PASS: group 0 got event: mask 20 pid=2840 fd=15
fanotify10.c:187: PASS: group 1 got event: mask 20 pid=2840 fd=15
fanotify10.c:187: PASS: group 2 got event: mask 20 pid=2840 fd=15
fanotify10.c:264: PASS: group 0 (prio 1) with FAN_MARK_MOUNT and FAN_MARK_INODE 
ignore mask got no event
fanotify10.c:264: PASS: group 1 (prio 1) with FAN_MARK_MOUNT and FAN_MARK_INODE 
ignore mask got no event
fanotify10.c:264: PASS: group 2 (prio 1) with FAN_MARK_MOUNT and FAN_MARK_INODE 
ignore mask got no event
fanotify10.c:264: PASS: group 0 (prio 2) with FAN_MARK_MOUNT and FAN_MARK_INODE 
ignore mask got no event
fanotify10.c:264: PASS: group 1 (prio 2) with FAN_MARK_MOUNT and FAN_MARK_INODE 
ignore mask got no event
fanotify10.c:264: PASS: group 2 (prio 2) with FAN_MARK_MOUNT and FAN_MARK_INODE 
ignore mask got no event
fanotify10.c:199: INFO: Test #1: don't ignore mount events created on another 
file
fanotify10.c:187: PASS: group 0 got event: mask 20 pid=2840 fd=15
fanotify10.c:187: PASS: group 1 got event: mask 20 pid=2840 fd=15
fanotify10.c:187: PASS: group 2 got event: mask 20 pid=2840 fd=15
fanotify10.c:187: PASS: group 0 got event: mask 20 pid=2840 fd=15
fanotify10.c:187: PASS: group 1 got event: mask 20 pid=2840 fd=15
fanotify10.c:187: PASS: group 2 got event: mask 20 pid=2840 fd=15
fanotify10.c:187: PASS: group 0 got event: mask 20 pid=2840 fd=15
fanotify10.c:187: PASS: group 1 got event: mask 20 pid=2840 fd=15
fanotify10.c:187: PASS: group 2 got event: mask 20 pid=2840 fd=15
fanotify10.c:199: INFO: Test #2: ignore inode events created on a specific 
mount point
fanotify10.c:187: PASS: group 0 got event: mask 20 pid=2840 fd=15
fanotify10.c:187: PASS: group 1 got event: mask 20 pid=2840 fd=15
fanotify10.c:187: PASS: group 2 got event: mask 20 pid=2840 fd=15
fanotify10.c:258: FAIL: group 0 (prio 1) with FAN_MARK_INODE and FAN_MARK_MOUNT 
ignore mask got event
fanotify10.c:258: FAIL: group 1 (prio 1) with FAN_MARK_INODE and FAN_MARK_MOUNT 
ignore mask got event
fanotify10.c:258: FAIL: group 2 (prio 1) with FAN_MARK_INODE and FAN_MARK_MOUNT 
ignore mask got event
fanotify10.c:258: FAIL: group 0 (prio 2) with FAN_MARK_INODE and FAN_MARK_MOUNT 
ignore mask got event
fanotify10.c:258: FAIL: group 1 (prio 2) with FAN_MARK_INODE and FAN_MARK_MOUNT 
ignore mask got event
fanotify10.c:258: FAIL: group 2 (prio 2) with FAN_MARK_INODE and FAN_MARK_MOUNT 
ignore mask got event
fanotify10.c:199: INFO: Test #3: don't ignore inode events created on another 
mount point
fanotify10.c:187: PASS: group 0 got event: mask 20 pid=2840 fd=15
fanotify10.c:187: PASS: group 1 got event: mask 20 pid=2840 fd=15
fanotify10.c:187: PASS: group 2 got event: mask 20 pid=2840 fd=15
fanotify10.c:187: PASS: group 0 got event: mask 20 pid=2840 fd=15
fanotify10.c:187: PASS: group 1 got event: mask 20 pid=2840 fd=15
fanotify10.c:187: PASS: group 2 got event: mask 20 pid=2840 fd=15
fanotify10.c:187: PASS: group 0 got event: mask 20 pid=2840 fd=15
fanotify10.c:187: PASS: group 1 got event: mask 20 pid=2840 fd=15
fanotify10.c:187: PASS: group 2 got event: mask 20 pid=2840 fd=15

Summary:
passed   30
failed   6
skipped  0
warnings 0
<<>>
initiation_status="ok"
duration=1 termination_type=exited termination_id=1 corefile=no
cutime=0 cstime=1
<<>>

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-image-4.18.0-11-generic 4.18.0-11.12~18.04.1
ProcVersionSignature: User Name 4.18.0-11.12~18.04.1-generic 4.18.12
Uname: Linux 4.18.0-11-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.4
Architecture: amd64
Date: Fri Nov  9 06:24:06 2018
SourcePackage: linux-signed-hwe-edge
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug bionic package-from-proposed uec-images
-- 
fanotify10 in ubuntu_ltp_syscalls failed
https://bugs.launchpad.net/bugs/1802454
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to linux in Ubuntu.

-- 
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 1802260] Re: Please include modules for NVMe and USB HID in pc-kernel snap initrd

2018-11-08 Thread Robert Liu

applied this patch against lp:~ubuntu-kernel/ubuntu/+source/linux-
snap/+git/bionic then the issue is gone.

** Patch added: "add-nvme-and-usbhid.patch"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1802260/+attachment/5210613/+files/add-nvme-and-usbhid.patch

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

Title:
  Please include modules for NVMe and USB HID in pc-kernel snap initrd

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  When trying Ubuntu Core with the pc-kernel snap, the system showed
  'cannot find writable partition'. The system was stopped at the initrd
  stage and didn't accept any input.

  My system is using a NVMe disk and it seems the pc-kernel doesn't
  provide the related modules in its initrd. Also, it's not possible to
  enter the initramfs environment because of the lacking of USB HID
  modules.

  Is it possible to include these two categories of drivers in the
  initrd of pc-kernel, please?

  Verified both 4.4 and 4.15 (track 18) have the same issue.
  $ squashfuse pc-kernel_162.snap pc-kernel
  $ lsinitramfs pc-kernel/initrd.img |grep -E 'nvme|usbhid'
  [nothing is showed]
  $ fusermount -u pc-kernel
  $ squashfuse pc-kernel_165.snap pc-kernel
  $ lsinitramfs pc-kernel/initrd.img |grep -E 'nvme|usbhid'
  [nothing is showed]
  $ fusermount -u pc-kernel

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1802260/+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 1766076] Re: USB over thunderbolt turns off every once in a while

2018-11-08 Thread Kai-Heng Feng

What functions are in use? I simply plug the TB16 and I don't see this
issue over several days. So I need more information on how to reproduce
the issue.

** Changed in: linux (Ubuntu)
   Status: Confirmed => 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/1766076

Title:
  USB over thunderbolt turns off every once in a while

Status in Dell Sputnik:
  New
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I'm using a USB hub in the Dell TB16 (240W) connected to a Dell
  Precision 5520 using Thunderbolt 3.

  Every so often (can be several times in an hour if I'm really unlucky,
  some days it is less of a problem), the USB hub disconnects from the
  computer and the devices connected to it lose power and stop
  responding.

  disconnecting and reconnecting the USB cables has no effect. I can
  restore functionality by instructing the xhci_hcd driver to unbind
  from the USB 3.0 Host Controller in the dock and to rebind to it using
  the commands:

  echo -n ":0e:00.0" > /sys/bus/pci/drivers/xhci_hcd/unbind
  echo -n ":0e:00.0" > /sys/bus/pci/drivers/xhci_hcd/bind

  Here's the dmesg output when the USB hub disconnects:

  279278.102701] xhci_hcd :0e:00.0: ERROR unknown event type 15
  [279283.021802] xhci_hcd :0e:00.0: xHCI host not responding to stop 
endpoint command.
  [279283.022145] xhci_hcd :0e:00.0: xHCI host controller not responding, 
assume dead
  [279283.022161] r8152 4-1.2:1.0 enxd481d731b2b1: Tx status -108
  [279283.022199] xhci_hcd :0e:00.0: HC died; cleaning up
  [279283.07] usb 3-1.5: Failed to suspend device, error -22
  [279283.022234] usb 3-1: USB disconnect, device number 2
  [279283.022235] usb 3-1.1: USB disconnect, device number 3
  [279283.022236] usb 3-1.1.1: USB disconnect, device number 5
  [279283.022237] usb 3-1.1.1.1: USB disconnect, device number 8
  [279283.022238] usb 3-1.1.1.1.4: USB disconnect, device number 11
  [279283.022326] usb 4-1: USB disconnect, device number 2
  [279283.022328] usb 4-1.1: USB disconnect, device number 3
  [279283.022329] usb 4-1.1.1: USB disconnect, device number 5
  [279283.022998] usb 4-1.2: USB disconnect, device number 4
  [279283.191217] usb 3-1.1.1.5: USB disconnect, device number 9
  [279283.191730] usb 3-1.1.3: USB disconnect, device number 6
  [279283.260810] usb 3-1.1.5: USB disconnect, device number 7
  [279283.261350] usb 3-1.5: USB disconnect, device number 4

  Here's dmesg output during the USB host controller reset:

  279389.813889] xhci_hcd :0e:00.0: remove, state 1 

  
  [279389.813894] usb usb4: USB disconnect, device number 1 

   
  [279389.814103] xhci_hcd :0e:00.0: USB bus 4 deregistered 

   
  [279389.814107] xhci_hcd :0e:00.0: remove, state 1

   
  [279389.814110] usb usb3: USB disconnect, device number 1 

   
  [279389.881651] xhci_hcd :0e:00.0: USB bus 3 deregistered 

   
  [279389.882133] xhci_hcd :0e:00.0: xHCI Host Controller   

   
  [279389.882138] xhci_hcd :0e:00.0: new USB bus registered, assigned bus 
number 3
 
  [279389.949391] xhci_hcd :0e:00.0: hcc params 0x0200e081 hci version 
0x100 quirks 0x1410 

  [279389.949979] usb usb3: New USB device found, idVendor=1d6b, idProduct=0002 

   
  [279389.949981] usb usb3: New USB device strings: Mfr=3, Product=2, 
SerialNumber=1  
 
  [279389.949982] usb usb3: Product: xHCI Host Controller   

   
  [279389.949983] usb usb3: Manufacturer: Linux 4.15.0-15-generic xhci-hcd  

   
  [279389.949983] usb

[Kernel-packages] [Bug 1802341] Re: crash in ENA driver on removing an interface

2018-11-08 Thread Ubuntu Foundations Team Bug Bot

** Tags added: patch

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

Title:
  crash in ENA driver on removing an interface

Status in linux package in Ubuntu:
  In Progress
Status in linux-aws package in Ubuntu:
  In Progress
Status in linux source package in Xenial:
  In Progress
Status in linux-aws source package in Xenial:
  In Progress
Status in linux source package in Bionic:
  In Progress
Status in linux-aws source package in Bionic:
  In Progress
Status in linux source package in Cosmic:
  In Progress
Status in linux-aws source package in Cosmic:
  In Progress
Status in linux source package in Disco:
  In Progress
Status in linux-aws source package in Disco:
  In Progress

Bug description:
  Bug present in ENA since driver version 1.6; manifests as a crash only
  under some conditions.

  In ena_remove() we have the following stack call:
  ena_remove()
unregister_netdev()
ena_destroy_device()
  netif_carrier_off()
  
  Calling netif_carrier_off() causes linkwatch to try to handle the
  link change event on the already unregistered netdev, which leads
  to a read from an unreadable memory address.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1802341/+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 1797092] Re: xenial guest on arm64 drops to busybox under openstack bionic-rocky

2018-11-08 Thread Khaled El Mously

** Changed in: linux (Ubuntu Xenial)
   Status: Triaged => Fix Committed

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

Title:
  xenial guest on arm64 drops to busybox under openstack bionic-rocky

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Fix Committed
Status in linux source package in Bionic:
  Fix Released

Bug description:
  [Impact]
  on openstack rocky-bionic (with patch, see 1771662), xenial guests will fail 
to launch as they drop to the busybox prompt after booting. The reason is that 
the EFI firmware image switched to ACPI mode by default in bionic. We knew that 
was happening, and backported some minimal ACPI support to keep xenial guests 
booting (bug 1744754). But, now we're seeing guests panic when trying to 
initialize PCI.

  [Test Case]
  Deploy rocky-bionic OpenStack and try to launch a xenial guest.

  [Fix]
  Backport ACPI/PCIe support for arm64 from upstream.

  [ Regression Risk ]
  TLDR: Definitely warrants some regression testing on armhf/arm64, but 
regression risk seems low for other architectures. Here's a patch-by-patch risk 
analysis:

  > 0001-UBUNTU-Config-CONFIG_PCI_ECAM-y.patch
  Enables code that will be added in the next patch.

  > 0002-PCI-Provide-common-functions-for-ECAM-mapping.patch
  Only adds new code w/ no callers yet

  > 0003-PCI-generic-thunder-Use-generic-ECAM-API.patch
  As noted in the commit message:
  "The patch does not introduce any functional changes other than a very minor 
one: with the new code, on 64-bit platforms, we do just a single ioremap for 
the whole config space."

  > 0004-PCI-of-Move-PCI-I-O-space-management-to-PCI-core-cod.patch
  As noted, no functional change.

  > 0005-PCI-Move-ecam.h-to-linux-include-pci-ecam.h.patch
  As noted, no functional change.

  > 0006-PCI-Add-parent-device-field-to-ECAM-struct-pci_confi.patch
  This makes changes to the ecam code, but that was added in this series, so no 
regression risk there. The pci-thunder-pem changes will be regression tested on 
the hardware that uses that driver (Cavium ThunderX).

  > 0007-PCI-Add-pci_unmap_iospace-to-unmap-I-O-resources.patch
  Only adds new code, w/ no callers yet

  > 0008-PCI-ACPI-Support-I-O-resources-when-parsing-host-bri.patch
  Adds and calls a new function that is a no-op on !ARM (PCI_IOBASE is only 
defined on ARM). Also adds a call to pci_unmap_iospace(), which was added in a 
previous patch and is also a no-op on !ARM.

  > 0009-UBUNTU-Config-CONFIG_ACPI_MCFG-y.patch
  Enables code that will be added in the next patch.

  > 0010-PCI-ACPI-Add-generic-MCFG-table-handling.patch
  Adds parsing of a new ACPI table. A possible regression risk to platforms an 
MCFG table that were working fine w/ 4.4 and there's a latent bug in this 
parsing code.

  > 0011-PCI-Refactor-pci_bus_assign_domain_nr-for-CONFIG_PCI.patch
  As noted, no functional change intended.

  > 0012-PCI-Factor-DT-specific-pci_bus_find_domain_nr-code-o.patch
  Again, no functional change.

  > 0013-ARM64-PCI-Add-acpi_pci_bus_find_domain_nr.patch
  Only impacts ARM due to CONFIG_PCI_DOMAINS_GENERIC guard

  > 0014-ARM64-PCI-ACPI-support-for-legacy-IRQs-parsing-and-c.patch
  arm64-specific PCI initialization code - mitigate risk by regression testing 
on supported platforms (X-Gene, ThunderX).

  > 0015-ARM64-PCI-Support-ACPI-based-PCI-host-controller.patch
  Adds new code for arm64-ACPI support. We didn't previously support these 
devices, so regression risk is negligible.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1797092/+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 1799401] Re: linux: 4.4.0-139.165 -proposed tracker

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  backports: bug 1799403 (linux-aws), bug 1799404 (linux-lts-xenial)
  derivatives: bug 1799405 (linux-aws), bug 1799407 (linux-euclid), bug 1799408 
(linux-kvm), bug 1799409 (linux-raspi2), bug 1799410 (linux-snapdragon)
  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   regression-testing: Testing in progress
snap-certification-testing: Ready

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

Title:
  linux: 4.4.0-139.165 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Fix Released
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow snap-certification-testing series:
  Confirmed
Status in Kernel SRU Workflow snap-release-to-beta series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-candidate series:
  New
Status in Kernel SRU Workflow snap-release-to-edge series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-stable series:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Confirmed

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  backports: bug 1799403 (linux-aws), bug 1799404 (linux-lts-xenial)
  derivatives: bug 1799405 (linux-aws), bug 1799407 (linux-euclid), bug 1799408 
(linux-kvm), bug 1799409 (linux-raspi2), bug 1799410 (linux-snapdragon)
  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
snap-certification-testing: Ready

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1799401/+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 1799401] Re: linux: 4.4.0-139.165 -proposed tracker

4.4.0-139.165 - lowlatency
Regression test CMPL, RTB.

Test case ubuntu_performance_fio_aws does not exist in the database, please 
check
45 / 52 tests were run, missing: ubuntu_bpf_jit, ubuntu_cts_kernel, 
ubuntu_cve_kernel, ubuntu_ecryptfs, ubuntu_ltp_syscalls, ubuntu_zfs_fstest, 
ubuntu_zfs_xfs_generic, xfstests
Issue to note in amd64:
  ubuntu_kvm_unit_tests - 18 failed on gummo
  ubuntu_performance_fio_aws - test for nvidia project, should be skipped
  ubuntu_qrt_kernel_security - test_095_kernel_symbols_missing_proc_self_stack 
(bug 1802069)

4.4.0-139.165 - generic
Regression test CMPL, RTB.

51 / 52 tests were run, missing: ubuntu_ramfs_stress
Issue to note in amd64:
  ubuntu_kernel_selftests - passed after re-run
  ubuntu_kvm_unit_tests - 32 faile on amaura, 25 failed on michael, 31 failed 
on pepe
  ubuntu_ltp_syscalls - bind03 failed (bug 1788351) execveat03 failed (bug 
1786729) inotify07 failed with X/X-LTS/A kernel (bug 1774387) inotify08 failed 
with X/X-LTS/X-HWE/A kernel (bug 1775784) fanotify07/fanotify08 test timeouted 
(bug 1775165) fanotify09 timeouted (bug 1775153) mlock203 failed (bug 1793451)
  ubuntu_lxc - passed after re-run
  ubuntu_nbd_smoke_test - passed after re-run
  ubuntu_qrt_kernel_panic - missing keyctl package, passed after re-test
  ubuntu_qrt_kernel_security - test_095_kernel_symbols_missing_proc_self_stack 
(bug 1802069)
  xfstests - xfs generic/468 timed out

46 / 47 tests were run, missing: xfstests
Issue to note in arm64:
  hwclock - issue for HP m400 (bug 1716603)
  ubuntu_kvm_smoke_test - unable to create KVM with uvtool (bug 1749427)
  ubuntu_kvm_unit_tests - gicv2-ipi and gicv2-active on starmie pmu on 
ms10-34-mcdivittB0-kernel (bug 1751000)
  ubuntu_ltp_syscalls - bind03 failed (bug 1788351) execveat03 failed (bug 
1786729) inotify07 failed with X/X-LTS/A kernel (bug 1774387) inotify08 failed 
with X/X-LTS/X-HWE/A kernel (bug 1775784) fanotify07/fanotify08 test timeouted 
(bug 1775165) fanotify09 timeouted (bug 1775153) mlock203 failed (bug 1793451)
  ubuntu_qrt_kernel_panic - missing keyctl package, passed after re-test
  ubuntu_qrt_kernel_security - test_095_kernel_symbols_missing_proc_self_stack 
(bug 1802069)

Issue to note in i386:
  ubuntu_kvm_unit_tests - unable to build on X/T i386 (bug 1798007)
  ubuntu_ltp_syscalls - bind03 failed (bug 1788351) execveat03 failed (bug 
1786729) inotify07 failed with X/X-LTS/A kernel (bug 1774387) inotify08 failed 
with X/X-LTS/X-HWE/A kernel (bug 1775784) fanotify07/fanotify08 test timeouted 
(bug 1775165) fanotify09 timeouted (bug 1775153) mlock203 failed (bug 1793451)
  ubuntu_lxc - passed after re-run
  ubuntu_qrt_kernel_panic - missing keyctl package, passed after re-test
  ubuntu_qrt_kernel_security - test_095_kernel_symbols_missing_proc_self_stack 
(bug 1802069)
  xfstests - xfs generic/308 timed out, bug 1738152

Issue to note in ppc64le (P8):
  ubuntu_kvm_smoke_test - unable to create KVM with uvtool, bug 1755118
  ubuntu_ltp_syscalls - bind03 failed (bug 1788351) execveat03 failed (bug 
1786729) fallocate05, fsetxattr01, fgetxattr01, fsync01, preadv03, preadv03_64, 
pwritev03, pwritev03_64, setxattr01 (bug 1785198) inotify07 failed with 
X/X-LTS/A kernel (bug 1774387) inotify08 failed with X/X-LTS/X-HWE/A kernel 
(bug 1775784) fanotify07/fanotify08 test timeouted (bug 1775165) fanotify09 
timeouted (bug 1775153) mlock203 failed (bug 1793451)
  ubuntu_qrt_kernel_panic - missing keyctl package, passed after re-test
  ubuntu_qrt_kernel_security - test_095_kernel_symbols_missing_proc_self_stack 
(bug 1802069)
  xfstests - btrfs generic/176 timed out

Issue to note in s390x (Ubuntu on LPAR):
  libhugetlbfs - failed 11 killed by signal 7 bad config 1
  ubuntu_aufs_smoke_test - passed after re-run
  ubuntu_blktrace_smoke_test - passed after re-run
  ubuntu_bpf_jit - unable to insert test_bpf on Xenial s390x (bug 1768452)
  ubuntu_docker_smoke_test - passed after re-run
  ubuntu_ecryptfs - passed after re-run
  ubuntu_fan_smoke_test - passed after re-run
  ubuntu_kvm_smoke_test - uvtool issue (bug 1729854)
  ubuntu_loop_smoke_test - passed after re-run
  ubuntu_ltp_syscalls - bind03 failed (bug 1788351) execveat03 failed (bug 
1786729) inotify07 failed with X/X-LTS/A kernel (bug 1774387) inotify08 failed 
with X/X-LTS/X-HWE/A kernel (bug 1775784) fanotify07/fanotify08 test timeouted 
(bug 1775165) fanotify09 timeouted (bug 1775153) mlock203 failed (bug 1793451)
  ubuntu_lttng_smoke_test - passed after re-run
  ubuntu_nbd_smoke_test - passed after re-run
  ubuntu_qrt_apparmor - passed after re-run
  ubuntu_qrt_kernel_aslr_collisions - passed after re-run
  ubuntu_qrt_kernel_hardening - passed after re-run
  ubuntu_qrt_kernel_panic - passed after re-run
  ubuntu_qrt_kernel_security - test_095_kernel_symbols_missing_proc_self_stack 
(bug 1802069)
  ubuntu_quota_smoke_test - passed after re-run
  ubuntu_squashfs_smoke_test - passed after re-run
  ubuntu_stress_smoke_test - passed after re-run
  ubuntu_zfs_smoke_test -

[Kernel-packages] [Bug 1801975] Re: update to build for 4.19

2018-11-08 Thread Launchpad Bug Tracker

This bug was fixed in the package dm-writeboost - 2.2.9-1ubuntu1

---
dm-writeboost (2.2.9-1ubuntu1) disco; urgency=low

  * Merge from Debian unstable.  Remaining changes:
- Adding DEP8 functional test case
  * Fix building for linux 4.19 (LP: #1801975)
  * Fix calling dm_kcopyd_zero on linux 4.19 (LP: #1801975)

dm-writeboost (2.2.9-1) unstable; urgency=medium

  * New upstream release [June 2018].
+ fixed build on Linux 4.15 and 4.17 (Closes: #892064).
  * Standards-Version: 4.1.4.
  * Vcs URLs to Salsa.

 -- Thadeu Lima de Souza Cascardo   Wed, 07 Nov
2018 20:41:49 -0200

** Changed in: dm-writeboost (Ubuntu Disco)
   Status: In Progress => 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/1801975

Title:
  update to build for 4.19

Status in dm-writeboost package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in dm-writeboost source package in Disco:
  Fix Released
Status in linux source package in Disco:
  Invalid

Bug description:
  dm-writeboost-dkms fails to build on linux 4.19.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dm-writeboost/+bug/1801975/+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 1801642] Status changed to Confirmed

This change was made by a bot.

** Changed in: linux (Ubuntu)
   Status: New => 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/1801642

Title:
  Bluetooth mouse sleeps after 5 seconds of inactivity

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I'm having bluetooth mouse lag issue. After leaving it stationary for
  5 seconds, I have to move it for 2 seconds before the pointer starts
  moving.

  I recently upgraded to Cosmic 3 days ago (from Bionic). There was no
  issue in the first 3 days, including after suspend/restart/shutdown.
  This issue only appears starting today.

  I tried:
  1. Running 'bluetoothctl' and then 'scan off'. The command failed to run with 
'Failed to stop discovery: org.bluez.Error.Failed'.
  2. modprobe -r btusb, then modprobe it again.
  3. sudo sh -c 'echo N > /sys/module/drm_kms_helper/parameters/poll'
  4. Disabling wifi.

  $ apt-cache policy bluez
  5.50-0ubuntu1

  $uname -a; lspci -nnk | grep -iA2 net; lsusb; dmesg | grep -i bluetooth; 
dmesg | grep -i firmware; lsmod | grep bluetooth
  4.18.0-10-generic #11
  02:00.0 Network controller [0280]: Intel Corporation Wireless 7260 
[8086:08b1] (rev 73)
Subsystem: Intel Corporation Dual Band Wireless-N 7260 [8086:4460]
Kernel driver in use: iwlwifi
  03:00.1 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. 
RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [10ec:8168] (rev 12)
Subsystem: Dell RTL8111/8168/8411 PCI Express Gigabit Ethernet 
Controller [1028:05f9]
Kernel driver in use: r8169
Kernel modules: r8169
  Bus 001 Device 002: ID 8087:8000 Intel Corp. 
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 003 Device 003: ID 17e9:4301 DisplayLink 
  Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 002 Device 047: ID 04f3:0206 Elan Microelectronics Corp. 
  Bus 002 Device 006: ID 8087:07dc Intel Corp. 
  Bus 002 Device 034: ID 0461:4d51 Primax Electronics, Ltd 0Y357C PMX-MMOCZUL 
(B) [Dell Laser Mouse]
  Bus 002 Device 118: ID 0853:0132 Topre Corporation 
  Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  [  287.361153] hid-generic 0005:046D:B012.0005: input,hidraw2: BLUETOOTH HID 
v0.14 Keyboard [MX Master] on FC:F8:AE:33:C7:31
  bluetooth 548864  33 btrtl,btintel,btbcm,bnep,btusb,rfcomm
  ecdh_generic   24576  2 bluetooth

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: bluez 5.50-0ubuntu1
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  Uname: Linux 4.18.0-10-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Mon Nov  5 13:40:01 2018
  InstallationDate: Installed on 2018-07-08 (119 days ago)
  InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: Dell Inc. Inspiron 7537
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-10-generic 
root=/dev/mapper/ubuntu--mate--vg-root ro ipv6.disable=1 quiet splash 
i915.enable_psr=0
  SourcePackage: bluez
  UpgradeStatus: Upgraded to cosmic on 2018-11-02 (3 days ago)
  dmi.bios.date: 10/31/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A05
  dmi.board.name: 07PF9F
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnDellInc.:bvrA05:bd10/31/2013:svnDellInc.:pnInspiron7537:pvr:rvnDellInc.:rn07PF9F:rvrA00:cvnDellInc.:ct8:cvr0.1:
  dmi.product.family: Shark Bay ULT
  dmi.product.name: Inspiron 7537
  dmi.product.sku: Inspiron 7537
  dmi.sys.vendor: Dell Inc.
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: FC:F8:AE:33:C7:31  ACL MTU: 1021:5  SCO MTU: 96:5
UP RUNNING 
RX bytes:2380 acl:32 sco:0 events:208 errors:0
TX bytes:28560 acl:29 sco:0 commands:170 errors:0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1801642/+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 1801642] Re: Bluetooth mouse sleeps after 5 seconds of inactivity

2018-11-08 Thread Daniel van Vugt

First ensure you don't have 'tlp' installed.

Second, I can only answer by Googling. Maybe changing your kernel
command line to disable autosuspend of USB devices:

https://www.kernel.org/doc/html/v4.16/driver-api/usb/power-
management.html

** Package changed: bluez (Ubuntu) => linux (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/1801642

Title:
  Bluetooth mouse sleeps after 5 seconds of inactivity

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I'm having bluetooth mouse lag issue. After leaving it stationary for
  5 seconds, I have to move it for 2 seconds before the pointer starts
  moving.

  I recently upgraded to Cosmic 3 days ago (from Bionic). There was no
  issue in the first 3 days, including after suspend/restart/shutdown.
  This issue only appears starting today.

  I tried:
  1. Running 'bluetoothctl' and then 'scan off'. The command failed to run with 
'Failed to stop discovery: org.bluez.Error.Failed'.
  2. modprobe -r btusb, then modprobe it again.
  3. sudo sh -c 'echo N > /sys/module/drm_kms_helper/parameters/poll'
  4. Disabling wifi.

  $ apt-cache policy bluez
  5.50-0ubuntu1

  $uname -a; lspci -nnk | grep -iA2 net; lsusb; dmesg | grep -i bluetooth; 
dmesg | grep -i firmware; lsmod | grep bluetooth
  4.18.0-10-generic #11
  02:00.0 Network controller [0280]: Intel Corporation Wireless 7260 
[8086:08b1] (rev 73)
Subsystem: Intel Corporation Dual Band Wireless-N 7260 [8086:4460]
Kernel driver in use: iwlwifi
  03:00.1 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. 
RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [10ec:8168] (rev 12)
Subsystem: Dell RTL8111/8168/8411 PCI Express Gigabit Ethernet 
Controller [1028:05f9]
Kernel driver in use: r8169
Kernel modules: r8169
  Bus 001 Device 002: ID 8087:8000 Intel Corp. 
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 003 Device 003: ID 17e9:4301 DisplayLink 
  Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 002 Device 047: ID 04f3:0206 Elan Microelectronics Corp. 
  Bus 002 Device 006: ID 8087:07dc Intel Corp. 
  Bus 002 Device 034: ID 0461:4d51 Primax Electronics, Ltd 0Y357C PMX-MMOCZUL 
(B) [Dell Laser Mouse]
  Bus 002 Device 118: ID 0853:0132 Topre Corporation 
  Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  [  287.361153] hid-generic 0005:046D:B012.0005: input,hidraw2: BLUETOOTH HID 
v0.14 Keyboard [MX Master] on FC:F8:AE:33:C7:31
  bluetooth 548864  33 btrtl,btintel,btbcm,bnep,btusb,rfcomm
  ecdh_generic   24576  2 bluetooth

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: bluez 5.50-0ubuntu1
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  Uname: Linux 4.18.0-10-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Mon Nov  5 13:40:01 2018
  InstallationDate: Installed on 2018-07-08 (119 days ago)
  InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: Dell Inc. Inspiron 7537
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-10-generic 
root=/dev/mapper/ubuntu--mate--vg-root ro ipv6.disable=1 quiet splash 
i915.enable_psr=0
  SourcePackage: bluez
  UpgradeStatus: Upgraded to cosmic on 2018-11-02 (3 days ago)
  dmi.bios.date: 10/31/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A05
  dmi.board.name: 07PF9F
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnDellInc.:bvrA05:bd10/31/2013:svnDellInc.:pnInspiron7537:pvr:rvnDellInc.:rn07PF9F:rvrA00:cvnDellInc.:ct8:cvr0.1:
  dmi.product.family: Shark Bay ULT
  dmi.product.name: Inspiron 7537
  dmi.product.sku: Inspiron 7537
  dmi.sys.vendor: Dell Inc.
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: FC:F8:AE:33:C7:31  ACL MTU: 1021:5  SCO MTU: 96:5
UP RUNNING 
RX bytes:2380 acl:32 sco:0 events:208 errors:0
TX bytes:28560 acl:29 sco:0 commands:170 errors:0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1801642/+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 1499858] Re: bluetoothd[650]: Failed to obtain handles for "Service Changed" characteristic

2018-11-08 Thread Daniel van Vugt

** Tags removed: wily

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

Title:
  bluetoothd[650]: Failed to obtain handles for "Service Changed"
  characteristic

Status in bluez package in Ubuntu:
  Confirmed

Bug description:
  sep 25 11:03:01 username-530U3C-530U4C bluetoothd[650]: Failed to obtain 
handles for "Service Changed" characteristic
  sep 25 11:03:01 username-530U3C-530U4C bluetoothd[650]: Not enough free 
handles to register service
  sep 25 11:03:01 username-530U3C-530U4C bluetoothd[650]: Error adding Link 
Loss service
  sep 25 11:03:01 username-530U3C-530U4C bluetoothd[650]: Not enough free 
handles to register service
  sep 25 11:03:01 username-530U3C-530U4C bluetoothd[650]: Not enough free 
handles to register service
  sep 25 11:03:01 username-530U3C-530U4C bluetoothd[650]: Not enough free 
handles to register service
  sep 25 11:03:01 username-530U3C-530U4C bluetoothd[650]: Current Time Service 
could not be registered
  sep 25 11:03:01 username-530U3C-530U4C bluetoothd[650]: gatt-time-server: 
Input/output error (5)
  sep 25 11:03:01 username-530U3C-530U4C bluetoothd[650]: Not enough free 
handles to register service
  sep 25 11:03:01 username-530U3C-530U4C bluetoothd[650]: Not enough free 
handles to register service
  sep 25 11:03:01 username-530U3C-530U4C bluetoothd[650]: Sap driver 
initialization failed.
  sep 25 11:03:01 username-530U3C-530U4C bluetoothd[650]: sap-server: Operation 
not permitted (1)

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: bluez 5.34-0ubuntu1
  ProcVersionSignature: Ubuntu 4.2.0-11.13-generic 4.2.1
  Uname: Linux 4.2.0-11-generic x86_64
  ApportVersion: 2.19-0ubuntu1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Sep 25 16:37:42 2015
  InstallationDate: Installed on 2015-07-26 (61 days ago)
  InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Alpha amd64 (20150723)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.2.0-11-generic 
root=UUID=4f4435ca-b877-47a5-9065-3dd624c0514e ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  SourcePackage: bluez
  UdevLog: Error: [Errno 2] No existe el archivo o el directorio: 
'/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/15/2013
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: P14AAJ
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: SAMSUNG_NP1234567890
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: FAB1
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvrP14AAJ:bd04/15/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1:
  dmi.product.name: 530U3C/530U4C
  dmi.product.version: 0.1
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.
  hciconfig:
   hci0:Type: BR/EDR  Bus: USB
BD Address: C4:85:08:6C:01:0A  ACL MTU: 310:10  SCO MTU: 64:8
UP RUNNING PSCAN 
RX bytes:12620731 acl:54193 sco:0 events:799035 errors:0
TX bytes:447934374 acl:1637190 sco:0 commands:1459 errors:0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1499858/+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 1802260] Re: Please include modules for NVMe and USB HID in pc-kernel snap initrd

2018-11-08 Thread Robert Liu

The fix would be similar with this bug #1794279

** 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/1802260

Title:
  Please include modules for NVMe and USB HID in pc-kernel snap initrd

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  When trying Ubuntu Core with the pc-kernel snap, the system showed
  'cannot find writable partition'. The system was stopped at the initrd
  stage and didn't accept any input.

  My system is using a NVMe disk and it seems the pc-kernel doesn't
  provide the related modules in its initrd. Also, it's not possible to
  enter the initramfs environment because of the lacking of USB HID
  modules.

  Is it possible to include these two categories of drivers in the
  initrd of pc-kernel, please?

  Verified both 4.4 and 4.15 (track 18) have the same issue.
  $ squashfuse pc-kernel_162.snap pc-kernel
  $ lsinitramfs pc-kernel/initrd.img |grep -E 'nvme|usbhid'
  [nothing is showed]
  $ fusermount -u pc-kernel
  $ squashfuse pc-kernel_165.snap pc-kernel
  $ lsinitramfs pc-kernel/initrd.img |grep -E 'nvme|usbhid'
  [nothing is showed]
  $ fusermount -u pc-kernel

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1802260/+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 1802421] Re: Xenial: data corruption when using i40e with iommu

2018-11-08 Thread Daniel Axtens

** Description changed:

  A user reports that using an i40e with intel_iommu=on with the Xenial GA
  kernel causes data corruption. Using the Xenial HWE kernel or an out-of-
  tree driver more recent than the version shipped with Xenial solves the
  issue.
  
  [Impact]
  Corrupted data is returned from the network card intermittently. This is 
often noticeable when using apt, as the checksums are verified. If often leads 
to failure of apt operations. When there are no checksums done, this could lead 
to silent data corruption.
  
  [Fix]
- This was fixed somewhere post-4.4. Testing identified b32bfa17246d ("i40e: 
Drop packet split receive routine") which is part of a broader refactor. My 
theory is that iommu exposes an issue in the packet split receive routine and 
so removing it is sufficient to prevent the problem from occurring.
+ This was fixed somewhere post-4.4. Testing identified b32bfa17246d ("i40e: 
Drop packet split receive routine") which is part of a broader refactor. 
Picking this patch alone is sufficient to fix the issue. My theory is that 
iommu exposes an issue in the packet split receive routine and so removing it 
is sufficient to prevent the problem from occurring.
  
  [Test]
  A user tested a Xenial 4.4 kernel with this patch applied and it fixed their 
issue - no data corruption was observed. (The test repeatedly deletes the apt 
cache and then does apt update.)
  
  [Regression Potential]
  It's a messy change inside i40e, so the risk is that i40e will be broken in 
some subtle way we haven't noticed, or have performance issues. None of these 
have been observed so far.

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

Title:
  Xenial: data corruption when using i40e with iommu

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  A user reports that using an i40e with intel_iommu=on with the Xenial
  GA kernel causes data corruption. Using the Xenial HWE kernel or an
  out-of-tree driver more recent than the version shipped with Xenial
  solves the issue.

  [Impact]
  Corrupted data is returned from the network card intermittently. This is 
often noticeable when using apt, as the checksums are verified. If often leads 
to failure of apt operations. When there are no checksums done, this could lead 
to silent data corruption.

  [Fix]
  This was fixed somewhere post-4.4. Testing identified b32bfa17246d ("i40e: 
Drop packet split receive routine") which is part of a broader refactor. 
Picking this patch alone is sufficient to fix the issue. My theory is that 
iommu exposes an issue in the packet split receive routine and so removing it 
is sufficient to prevent the problem from occurring.

  [Test]
  A user tested a Xenial 4.4 kernel with this patch applied and it fixed their 
issue - no data corruption was observed. (The test repeatedly deletes the apt 
cache and then does apt update.)

  [Regression Potential]
  It's a messy change inside i40e, so the risk is that i40e will be broken in 
some subtle way we haven't noticed, or have performance issues. None of these 
have been observed so far.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1802421/+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 1802421] [NEW] Xenial: data corruption when using i40e with iommu

2018-11-08 Thread Daniel Axtens

Public bug reported:

A user reports that using an i40e with intel_iommu=on with the Xenial GA
kernel causes data corruption. Using the Xenial HWE kernel or an out-of-
tree driver more recent than the version shipped with Xenial solves the
issue.

[Impact]
Corrupted data is returned from the network card intermittently. This is often 
noticeable when using apt, as the checksums are verified. If often leads to 
failure of apt operations. When there are no checksums done, this could lead to 
silent data corruption.

[Fix]
This was fixed somewhere post-4.4. Testing identified b32bfa17246d ("i40e: Drop 
packet split receive routine") which is part of a broader refactor. Picking 
this patch alone is sufficient to fix the issue. My theory is that iommu 
exposes an issue in the packet split receive routine and so removing it is 
sufficient to prevent the problem from occurring.

[Test]
A user tested a Xenial 4.4 kernel with this patch applied and it fixed their 
issue - no data corruption was observed. (The test repeatedly deletes the apt 
cache and then does apt update.)

[Regression Potential]
It's a messy change inside i40e, so the risk is that i40e will be broken in 
some subtle way we haven't noticed, or have performance issues. None of these 
have been observed so far.

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: 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/1802421

Title:
  Xenial: data corruption when using i40e with iommu

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  A user reports that using an i40e with intel_iommu=on with the Xenial
  GA kernel causes data corruption. Using the Xenial HWE kernel or an
  out-of-tree driver more recent than the version shipped with Xenial
  solves the issue.

  [Impact]
  Corrupted data is returned from the network card intermittently. This is 
often noticeable when using apt, as the checksums are verified. If often leads 
to failure of apt operations. When there are no checksums done, this could lead 
to silent data corruption.

  [Fix]
  This was fixed somewhere post-4.4. Testing identified b32bfa17246d ("i40e: 
Drop packet split receive routine") which is part of a broader refactor. 
Picking this patch alone is sufficient to fix the issue. My theory is that 
iommu exposes an issue in the packet split receive routine and so removing it 
is sufficient to prevent the problem from occurring.

  [Test]
  A user tested a Xenial 4.4 kernel with this patch applied and it fixed their 
issue - no data corruption was observed. (The test repeatedly deletes the apt 
cache and then does apt update.)

  [Regression Potential]
  It's a messy change inside i40e, so the risk is that i40e will be broken in 
some subtle way we haven't noticed, or have performance issues. None of these 
have been observed so far.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1802421/+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 1801642] Re: Bluetooth mouse sleeps after 5 seconds of inactivity

2018-11-08 Thread Wajuz Donny

Day 5: Issue comes back again (after suspend). Those two unknown devices
switched back to "Good". This time I toggled one of them to "Bad" and
the issue is resolved.

How do I make the powertop changes permanent?

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

Title:
  Bluetooth mouse sleeps after 5 seconds of inactivity

Status in bluez package in Ubuntu:
  New

Bug description:
  I'm having bluetooth mouse lag issue. After leaving it stationary for
  5 seconds, I have to move it for 2 seconds before the pointer starts
  moving.

  I recently upgraded to Cosmic 3 days ago (from Bionic). There was no
  issue in the first 3 days, including after suspend/restart/shutdown.
  This issue only appears starting today.

  I tried:
  1. Running 'bluetoothctl' and then 'scan off'. The command failed to run with 
'Failed to stop discovery: org.bluez.Error.Failed'.
  2. modprobe -r btusb, then modprobe it again.
  3. sudo sh -c 'echo N > /sys/module/drm_kms_helper/parameters/poll'
  4. Disabling wifi.

  $ apt-cache policy bluez
  5.50-0ubuntu1

  $uname -a; lspci -nnk | grep -iA2 net; lsusb; dmesg | grep -i bluetooth; 
dmesg | grep -i firmware; lsmod | grep bluetooth
  4.18.0-10-generic #11
  02:00.0 Network controller [0280]: Intel Corporation Wireless 7260 
[8086:08b1] (rev 73)
Subsystem: Intel Corporation Dual Band Wireless-N 7260 [8086:4460]
Kernel driver in use: iwlwifi
  03:00.1 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. 
RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [10ec:8168] (rev 12)
Subsystem: Dell RTL8111/8168/8411 PCI Express Gigabit Ethernet 
Controller [1028:05f9]
Kernel driver in use: r8169
Kernel modules: r8169
  Bus 001 Device 002: ID 8087:8000 Intel Corp. 
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 003 Device 003: ID 17e9:4301 DisplayLink 
  Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 002 Device 047: ID 04f3:0206 Elan Microelectronics Corp. 
  Bus 002 Device 006: ID 8087:07dc Intel Corp. 
  Bus 002 Device 034: ID 0461:4d51 Primax Electronics, Ltd 0Y357C PMX-MMOCZUL 
(B) [Dell Laser Mouse]
  Bus 002 Device 118: ID 0853:0132 Topre Corporation 
  Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  [  287.361153] hid-generic 0005:046D:B012.0005: input,hidraw2: BLUETOOTH HID 
v0.14 Keyboard [MX Master] on FC:F8:AE:33:C7:31
  bluetooth 548864  33 btrtl,btintel,btbcm,bnep,btusb,rfcomm
  ecdh_generic   24576  2 bluetooth

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: bluez 5.50-0ubuntu1
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  Uname: Linux 4.18.0-10-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Mon Nov  5 13:40:01 2018
  InstallationDate: Installed on 2018-07-08 (119 days ago)
  InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: Dell Inc. Inspiron 7537
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-10-generic 
root=/dev/mapper/ubuntu--mate--vg-root ro ipv6.disable=1 quiet splash 
i915.enable_psr=0
  SourcePackage: bluez
  UpgradeStatus: Upgraded to cosmic on 2018-11-02 (3 days ago)
  dmi.bios.date: 10/31/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A05
  dmi.board.name: 07PF9F
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnDellInc.:bvrA05:bd10/31/2013:svnDellInc.:pnInspiron7537:pvr:rvnDellInc.:rn07PF9F:rvrA00:cvnDellInc.:ct8:cvr0.1:
  dmi.product.family: Shark Bay ULT
  dmi.product.name: Inspiron 7537
  dmi.product.sku: Inspiron 7537
  dmi.sys.vendor: Dell Inc.
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: FC:F8:AE:33:C7:31  ACL MTU: 1021:5  SCO MTU: 96:5
UP RUNNING 
RX bytes:2380 acl:32 sco:0 events:208 errors:0
TX bytes:28560 acl:29 sco:0 commands:170 errors:0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1801642/+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 1778011] Re: SRU: PRIME Power Saving mode draws too much power

2018-11-08 Thread Krzysztof Janowicz

@Andrew, @Alberto: Looks like many Thinkpad X1 Extreme users are
reporting the same issue where prime-select seems to work but does not
power of the nvidia card nor shows up in nvidia-settings. I followed the
instructions the same way Andrew did and got the same 'not found'
message. I assumed the packages are in updates by now and we should all
have them anyway. Apt tells me that 390.77-0ubuntu0.18.04.1 is the
newest version. Am I missing something? I have the same issue as I had
before (NVIDIA GTX 1050 TI). Thanks for your help.

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

Title:
  SRU: PRIME Power Saving mode draws too much power

Status in HWE Next:
  New
Status in gdm3 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Fix Released
Status in nvidia-prime package in Ubuntu:
  Fix Released
Status in nvidia-settings package in Ubuntu:
  Fix Released
Status in ubuntu-drivers-common package in Ubuntu:
  Fix Released
Status in gdm3 source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-390 source package in Bionic:
  Fix Released
Status in nvidia-prime source package in Bionic:
  Fix Released
Status in nvidia-settings source package in Bionic:
  Fix Released
Status in ubuntu-drivers-common source package in Bionic:
  Fix Released

Bug description:
  SRU Request:

  [Impact]
  Relying on the nouveau driver and on the vga switcheroo (to get around a 
change in systemd LP: #1777099) caused increased power consumption, and slowed 
down the switching process.

  Furthermore, if the main X/Xwayland session was started by Gdm when
  the nvidia driver was loaded, the session will keep the nvidia module
  loaded, and prevent the system from switching off the dGPU. Also, the
  nouveau driver will be loaded, if nvidia is not, and this can cause
  problems to unsupported NVIDIA GPUs.

  The solution involves the following changes:

  1) Solving the problem in systemd (LP: #1777099)

  2) Adding code in gpu-manager and in nvidia-prime to unload the nvidia
  modules, and to allow the PCI device to sleep.

  3) Making a slight change to the current patch in Gdm, used to call
  the PRIME scripts before and after a Gdm session (so that gpu-manager
  gets actually called on log out)

  4) Adding code in gpu-manager to kill the main X/Xwayland session on
  log out, if the session is preventing us from unloading the nvidia
  driver. A new X/Xwayland session will be created after unload the
  module.

  5) Removing the systemd service that loads nouveau from the nvidia
  packages.

  [Test Case]
  1) Enable the -proposed repository, and install the new 
"ubuntu-drivers-common", nvidia drivers, nvidia-prime, and gdm3 *

  2) Make sure the nvidia packages are installed, and enable performance mode 
(if it is already enabled, call "sudo prime-select intel" first):
  sudo prime-select nvidia

  3) Restart your computer and attach your /var/log/gpu-manager.log. see
  if the system boots correctly. If unsure, please attach your /var/log
  /gpu-manager.log and /var/log/Xorg.0.log

  4) Select power saving mode:
  sudo prime-select intel

  5) Log out and log back in

  6) Check if the nvidia driver is still loaded:
  lsmod | grep nvidia

  [Regression Potential]
  Low, as hybrid graphics support does not work correctly, and the changes only 
affect this use case.

  _
  * Steps to test the updates:

  1) Enable the bionic-proposed repositories

  2) Create /etc/apt/preferences.d/proposed-updates with the following
  content:

  Package: *
  Pin: release a=bionic-proposed
  Pin-Priority: 400

  3) Update the list of packages:

  sudo apt-get update

  4) Install the packages from -proposed using the following command:

  sudo apt install nvidia-driver-390/bionic-proposed gdm3/bionic-
  proposed ubuntu-drivers-common/bionic-proposed nvidia-prime/bionic-
  proposed nvidia-settings/bionic-proposed libnvidia-gl-390/bionic-
  proposed libnvidia-compute-390/bionic-proposed libnvidia-decode-390
  /bionic-proposed libnvidia-encode-390/bionic-proposed libnvidia-
  ifr1-390/bionic-proposed libnvidia-fbc1-390/bionic-proposed

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1778011/+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 1801642] Re: Bluetooth mouse sleeps after 5 seconds of inactivity

2018-11-08 Thread Wajuz Donny

** Changed in: bluez (Ubuntu)
   Status: Invalid => New

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

Title:
  Bluetooth mouse sleeps after 5 seconds of inactivity

Status in bluez package in Ubuntu:
  New

Bug description:
  I'm having bluetooth mouse lag issue. After leaving it stationary for
  5 seconds, I have to move it for 2 seconds before the pointer starts
  moving.

  I recently upgraded to Cosmic 3 days ago (from Bionic). There was no
  issue in the first 3 days, including after suspend/restart/shutdown.
  This issue only appears starting today.

  I tried:
  1. Running 'bluetoothctl' and then 'scan off'. The command failed to run with 
'Failed to stop discovery: org.bluez.Error.Failed'.
  2. modprobe -r btusb, then modprobe it again.
  3. sudo sh -c 'echo N > /sys/module/drm_kms_helper/parameters/poll'
  4. Disabling wifi.

  $ apt-cache policy bluez
  5.50-0ubuntu1

  $uname -a; lspci -nnk | grep -iA2 net; lsusb; dmesg | grep -i bluetooth; 
dmesg | grep -i firmware; lsmod | grep bluetooth
  4.18.0-10-generic #11
  02:00.0 Network controller [0280]: Intel Corporation Wireless 7260 
[8086:08b1] (rev 73)
Subsystem: Intel Corporation Dual Band Wireless-N 7260 [8086:4460]
Kernel driver in use: iwlwifi
  03:00.1 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. 
RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [10ec:8168] (rev 12)
Subsystem: Dell RTL8111/8168/8411 PCI Express Gigabit Ethernet 
Controller [1028:05f9]
Kernel driver in use: r8169
Kernel modules: r8169
  Bus 001 Device 002: ID 8087:8000 Intel Corp. 
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 003 Device 003: ID 17e9:4301 DisplayLink 
  Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 002 Device 047: ID 04f3:0206 Elan Microelectronics Corp. 
  Bus 002 Device 006: ID 8087:07dc Intel Corp. 
  Bus 002 Device 034: ID 0461:4d51 Primax Electronics, Ltd 0Y357C PMX-MMOCZUL 
(B) [Dell Laser Mouse]
  Bus 002 Device 118: ID 0853:0132 Topre Corporation 
  Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  [  287.361153] hid-generic 0005:046D:B012.0005: input,hidraw2: BLUETOOTH HID 
v0.14 Keyboard [MX Master] on FC:F8:AE:33:C7:31
  bluetooth 548864  33 btrtl,btintel,btbcm,bnep,btusb,rfcomm
  ecdh_generic   24576  2 bluetooth

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: bluez 5.50-0ubuntu1
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  Uname: Linux 4.18.0-10-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Mon Nov  5 13:40:01 2018
  InstallationDate: Installed on 2018-07-08 (119 days ago)
  InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: Dell Inc. Inspiron 7537
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-10-generic 
root=/dev/mapper/ubuntu--mate--vg-root ro ipv6.disable=1 quiet splash 
i915.enable_psr=0
  SourcePackage: bluez
  UpgradeStatus: Upgraded to cosmic on 2018-11-02 (3 days ago)
  dmi.bios.date: 10/31/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A05
  dmi.board.name: 07PF9F
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnDellInc.:bvrA05:bd10/31/2013:svnDellInc.:pnInspiron7537:pvr:rvnDellInc.:rn07PF9F:rvrA00:cvnDellInc.:ct8:cvr0.1:
  dmi.product.family: Shark Bay ULT
  dmi.product.name: Inspiron 7537
  dmi.product.sku: Inspiron 7537
  dmi.sys.vendor: Dell Inc.
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: FC:F8:AE:33:C7:31  ACL MTU: 1021:5  SCO MTU: 96:5
UP RUNNING 
RX bytes:2380 acl:32 sco:0 events:208 errors:0
TX bytes:28560 acl:29 sco:0 commands:170 errors:0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1801642/+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 1802350] Re: [Inspiron 5547, Realtek ALC3234, Speaker, Internal] Playback problem

2018-11-08 Thread Cristian Aravena Romero

This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:

apport-collect 1802350

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a comment stating that fact and change
the bug status to 'Confirmed'.

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

** Also affects: gnome-control-center (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: linux (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/1802350

Title:
  [Inspiron 5547, Realtek ALC3234, Speaker, Internal] Playback problem

Status in alsa-driver package in Ubuntu:
  New
Status in gnome-control-center package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  On a fresh install of ubutu 18.04 all sound work (youtube and system
  sounds) I connected external hdmi monitor with speakers. I switched
  audio output to hdmi in settings

  Then all audio was channeled to external monitor speakers (youtube and
  system sounds)

  Then I disconnected external monitor and did not touch the audio
  output

  Now only system sounds are working. Youtube in chrome does not work.
  Audio settings says internal speakers.

  Firefox youtube has audio normally

  After reboot same issue

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18
  Uname: Linux 4.15.0-38-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ed 1412 F pulseaudio
   /dev/snd/controlC1:  ed 1412 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Nov  8 12:28:37 2018
  InstallationDate: Installed on 2018-11-01 (6 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  PackageArchitecture: all
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Speaker, Internal
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: Only some of outputs are working
  Title: [Inspiron 5547, Realtek ALC3234, Speaker, Internal] Playback problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/24/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A11
  dmi.board.name: 0598GM
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A11
  dmi.modalias: 
dmi:bvnDellInc.:bvrA11:bd01/24/2018:svnDellInc.:pnInspiron5547:pvrA11:rvnDellInc.:rn0598GM:rvrA00:cvnDellInc.:ct8:cvrA11:
  dmi.product.family: 00
  dmi.product.name: Inspiron 5547
  dmi.product.version: A11
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1802350/+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 1799416] Re: linux-gcp: 4.15.0-1024.25 -proposed tracker

** Changed in: kernel-sru-workflow/automated-testing
   Status: Incomplete => Fix Released

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1799411
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   automated-testing: Testing FAILED
regression-testing: Testing in progress
stakeholder-signoff: Waiting for signoff
verification-testing: Testing in progress

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

Title:
  linux-gcp: 4.15.0-1024.25 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-beta series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-candidate series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-edge series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-stable series:
  Invalid
Status in Kernel SRU Workflow stakeholder-signoff series:
  Confirmed
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-gcp package in Ubuntu:
  Invalid
Status in linux-gcp source package in Bionic:
  Confirmed

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1799411
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
regression-testing: Testing in progress
stakeholder-signoff: Waiting for signoff
verification-testing: Testing in progress

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1799416/+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 1802382] Re: [860399.181468] watchdog: BUG: soft lockup - CPU#4 stuck for 23s! [kworker/4:2:9700]

2018-11-08 Thread Cristian Aravena Romero

Did this issue start happening after an update/upgrade? Was there a
prior kernel version where you were not having this particular problem?

Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.19 kernel[0].

If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag:
'kernel-bug-exists-upstream'.

Once testing of the upstream kernel is complete, please mark this bug as
"Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.19.1

** Changed in: linux (Ubuntu)
   Status: Confirmed => 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/1802382

Title:
  [860399.181468] watchdog: BUG: soft lockup - CPU#4 stuck for 23s!
  [kworker/4:2:9700]

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  system was halt after resume. I had to boot via Magic SysRq
  R-E-I-S-U-B routine.

  $ cat /proc/version_signature
  Ubuntu 4.15.0-38.41-generic 4.15.18

  ProblemType: KernelOops
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-36-generic 4.15.0-36.39
  ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18
  Uname: Linux 4.15.0-36-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  Annotation: Your system might become unstable now and might need to be 
restarted.
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  Date: Thu Nov  8 22:27:35 2018
  Failure: oops
  InstallationDate: Installed on 2018-06-01 (160 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: ASUSTeK COMPUTER INC. N550JV
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-38-generic 
root=UUID=d62c0813-bece-408d-8a4c-773ce7fbe368 ro quiet splash vt.handoff=1
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: kerneloops-daemon N/A
  SourcePackage: linux
  Title: [860399.181468] watchdog: BUG: soft lockup - CPU#4 stuck for 23s! 
[kworker/4:2:9700]
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/19/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: N550JV.208
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: N550JV
  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.:bvrN550JV.208:bd11/19/2013:svnASUSTeKCOMPUTERINC.:pnN550JV:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnN550JV:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: N
  dmi.product.name: N550JV
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1802382/+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 1752053] Re: nvidia-390 fails to boot graphical display

2018-11-08 Thread bblrlo

On KUbuntu 18.04 same problem with card GT630M and 390,396 nvidia drivers
#lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 18.04.1 LTS
Release:18.04
Codename:   bionic
# cat /etc/X11/default-display-manager 
/usr/bin/sddm

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

Title:
  nvidia-390 fails to boot graphical display

Status in mesa package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Fix Released
Status in xserver-xorg-video-nouveau package in Ubuntu:
  Invalid

Bug description:
  I'm using Bionic with the new 4.15 kernel. I've been using the
  nvidia-384 driver with no problem for a while.  Today I issued "sudo
  apt-get upgrade" and I was prompted to upgrade the nvidia driver to
  the nvidia-390.  After installing the driver and rebooting, I was only
  able to boot in to the tty terminal.  The graphical display failed to
  boot.  I have had similar problems with nvidia driver version 390 with
  Arch Linux and with Open Suse Tumbleweed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1752053/+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 1795808] Re: Xorg freeze when using nvidia driver 390

2018-11-08 Thread bblrlo

I have KUbuntu installed with sddm and have same problem with my GT630M
on 390 and 396 drivers.

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

Title:
  Xorg freeze when using nvidia driver 390

Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  Since the installation of Ubuntu 18.10, I get the login screen but
  once logged in I get a black screen. It happens only with the
  proprietary nvidia driver 390. If I remove the nvidia driver to use
  nouveau, it works.

  My graphic card is: NVIDIA Corporation GP104 [GeForce GTX 1070 Ti]

  So the automatic report in attachement will show you no nvidia driver
  installed. It's because I am doing this bug report after removing the
  nvidia driver to be able to get a desktop.

  In attachement I add the journalctl of the preview boot which failed
  with nvidia driver.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: xorg 1:7.7+19ubuntu8
  ProcVersionSignature: Ubuntu 4.18.0-8.9-generic 4.18.7
  Uname: Linux 4.18.0-8-generic x86_64
  ApportVersion: 2.20.10-0ubuntu11
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Oct  3 09:19:03 2018
  DistUpgraded: 2018-10-03 00:59:01,660 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
  DistroCodename: cosmic
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.2.18, 4.15.0-36-generic, x86_64: installed
   virtualbox, 5.2.18, 4.18.0-8-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: Continuously
  GpuHangReproducibility: Yes, I can easily reproduce it
  GpuHangStarted: Immediately after installing this version of Ubuntu
  GraphicsCard:
   NVIDIA Corporation GP104 [GeForce GTX 1070 Ti] [10de:1b82] (rev a1) (prog-if 
00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. GP104 [GeForce GTX 1070 Ti] [1043:8620]
  InstallationDate: Installed on 2017-09-17 (380 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170915)
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-8-generic 
root=UUID=567a9b2b-0864-450e-9cfe-dab7a54b9fce ro rootflags=subvol=@ quiet 
splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: Upgraded to cosmic on 2018-10-02 (0 days ago)
  dmi.bios.date: 09/28/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0501
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P8Z77-V LX2
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0501:bd09/28/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8Z77-VLX2:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.94-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.1-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1build1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3
  xserver.bootTime: Wed Oct  3 09:03:39 2018
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.20.1-3ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1795808/+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 1795292] Re: ELAN469D touch pad not working

2018-11-08 Thread Kenji

Figured out my wifi issue. Can't get it working with Linux Mint, not
sure why. Ubuntu works fine. I had to disable some options in my bios to
get wifi (AMD security off, boot mode legacy support, boot priorty
legacy first and OS optimized defaults enabled). Once I had those set, I
was able to go to the grub setup and do "nomodeset" and "noapic" which
makes it install and work with wifi. I tried the same options in Linux
Mint but it would not get past the initial boot/setup/grub, kept getting
kernel panics or ACIP errors. I can with "apci=off" but then wifi will
not enable and show it "disabled by hardware", and no FN keys re-enable
it. So I'll stick to Ubuntu for now, since wifi works at least. Still no
idea on the touchpad, I tried a few kernels (4.17, 4.18, 4.19), tried to
email someone from ELAN but got nothing so far :/

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

Title:
  ELAN469D touch pad not working

Status in Linux:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I installed Bionic Beaver and now upgraded to Cosmic Cuttlefish on
  this Lenovo Ideapad 330S-15ARR laptop.  The touch pad doesn't work in
  either.

  Some possibly relevant info from dmesg:
  i2c_hid i2c-ELAN469D:00: i2c-ELAN469D:00 supply vdd not found, using dummy 
regulator
  i2c_designware AMDI0010:01: controller timed out

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.18.0-7-generic 4.18.0-7.8
  ProcVersionSignature: Ubuntu 4.18.0-7.8-generic 4.18.5
  Uname: Linux 4.18.0-7-generic x86_64
  ApportVersion: 2.20.10-0ubuntu11
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  xorbit 2086 F pulseaudio
   /dev/snd/pcmC1D0p:   xorbit 2086 F...m pulseaudio
   /dev/snd/controlC0:  xorbit 2086 F pulseaudio
  CurrentDesktop: GNOME
  Date: Sun Sep 30 23:14:26 2018
  InstallationDate: Installed on 2018-09-20 (10 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: LENOVO 81FB
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-7-generic 
root=UUID=4d91f09e-6122-4dd4-81fc-482465f8f0e7 ro noapic processor.max_cstate=1 
rcu_nocbs=0-7 pcie_aspm=off pci=noaer quiet splash vt.handoff=1 
elan_i2c.dyndbg=+p
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-7-generic N/A
   linux-backports-modules-4.18.0-7-generic  N/A
   linux-firmware1.175
  SourcePackage: linux
  UpgradeStatus: Upgraded to cosmic on 2018-09-30 (0 days ago)
  dmi.bios.date: 06/08/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 7WCN22WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709WIN
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad 330S-15ARR
  dmi.modalias: 
dmi:bvnLENOVO:bvr7WCN22WW:bd06/08/2018:svnLENOVO:pn81FB:pvrLenovoideapad330S-15ARR:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoideapad330S-15ARR:
  dmi.product.family: ideapad 330S-15ARR
  dmi.product.name: 81FB
  dmi.product.sku: LENOVO_MT_81FB_BU_idea_FM_ideapad 330S-15ARR
  dmi.product.version: Lenovo ideapad 330S-15ARR
  dmi.sys.vendor: LENOVO
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu11
  Architecture: amd64
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 18.10
  InstallationDate: Installed on 2018-09-20 (13 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Tags:  cosmic
  Uname: Linux 4.19.0-041900rc6-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: Upgraded to cosmic on 2018-09-30 (2 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1795292/+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 1782716] Re: [drm:amdgpu_job_timedout [amdgpu]] ERROR ring gfx timeout

2018-11-08 Thread Alexandr Kara

Reproduced on Fedora (with kernel 4.18.16-300.fc29.x86_64).

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

Title:
  [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Running the 4.17.0-5-generic kernel on a ppc64le machine with a Radeon
  R9 Fury GPU

  
  0033:01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. 
[AMD/ATI] Fiji [Radeon R9 FURY / NANO Series] (rev ff)

  [ 2361.958847] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout, 
last signaled seq=8777, last emitted seq=8778
  [ 2362.080397] EEH: Frozen PHB#33-PE#0 detected
  [ 2362.080470] EEH: PE location: CPU2 Slot1 (16x), PHB location: N/A
  [ 2362.080568] CPU: 53 PID: 874 Comm: kworker/53:1 Not tainted 
4.17.0-5-generic #6-Ubuntu
  [ 2362.080575] Workqueue: events drm_sched_job_timedout [gpu_sched]
  [ 2362.080577] Call Trace:
  [ 2362.080584] [c000fb7078f0] [c0d275ac] dump_stack+0xb0/0xf4 
(unreliable)
  [ 2362.080590] [c000fb707930] [c003ba0c] 
eeh_dev_check_failure+0x5bc/0x5e0
  [ 2362.080593] [c000fb7079e0] [c003babc] 
eeh_check_failure+0x8c/0xd0
  [ 2362.080628] [c000fb707a20] [c0080cfa1b88] 
amdgpu_mm_rreg+0x280/0x2a0 [amdgpu]
  [ 2362.080676] [c000fb707a70] [c0080d04cf68] 
gmc_v8_0_check_soft_reset+0x30/0xe0 [amdgpu]
  [ 2362.080711] [c000fb707aa0] [c0080cfa1194] 
amdgpu_device_ip_check_soft_reset.part.1+0x8c/0x140 [amdgpu]
  [ 2362.080745] [c000fb707b30] [c0080cfa649c] 
amdgpu_device_gpu_recover+0x854/0xa40 [amdgpu]
  [ 2362.080799] [c000fb707c00] [c0080d0b97a4] 
amdgpu_job_timedout+0x5c/0x80 [amdgpu]
  [ 2362.080805] [c000fb707c70] [c0080c8f0040] 
drm_sched_job_timedout+0x38/0x60 [gpu_sched]
  [ 2362.080810] [c000fb707c90] [c0137928] 
process_one_work+0x298/0x580
  [ 2362.080813] [c000fb707d20] [c0137c98] worker_thread+0x88/0x610
  [ 2362.080817] [c000fb707dc0] [c0140958] kthread+0x1a8/0x1b0
  [ 2362.080822] [c000fb707e30] [c000b658] 
ret_from_kernel_thread+0x5c/0x84
  [ 2362.080827] [drm] IP block:gmc_v8_0 is hung!
  [ 2362.080832] [drm] IP block:tonga_ih is hung!
  [ 2362.080843] [drm] IP block:gfx_v8_0 is hung!
  [ 2362.080845] EEH: Detected PCI bus error on PHB#33-PE#0
  [ 2362.080847] EEH: This PCI device has failed 1 times in the last hour
  [ 2362.080849] EEH: Notify device drivers to shutdown
  [ 2362.080850] [drm] IP block:sdma_v3_0 is hung!
  [ 2362.080856] [drm] IP block:uvd_v6_0 is hung!
  [ 2362.080858] EEH: Collect temporary log
  [ 2362.080866] [drm] IP block:vce_v3_0 is hung!
  [ 2362.080867] [drm] GPU recovery disabled.
  [ 2362.080903] EEH: of node=0033:01:00.1
  [ 2362.080905] EEH: PCI device/vendor: 
  [ 2362.080907] EEH: PCI cmd/status register: 
  [ 2362.080908] EEH: PCI-E capabilities and status follow:
  [ 2362.080915] EEH: PCI-E 00:     
  [ 2362.080920] EEH: PCI-E 10:     
  [ 2362.080921] EEH: PCI-E 20:  
  [ 2362.080922] EEH: PCI-E AER capability register set follows:
  [ 2362.080928] EEH: PCI-E AER 00:     
  [ 2362.080933] EEH: PCI-E AER 10:     
  [ 2362.080938] EEH: PCI-E AER 20:     
  [ 2362.080940] EEH: PCI-E AER 30:   
  [ 2362.080941] EEH: of node=0033:01:00.0
  [ 2362.080943] EEH: PCI device/vendor: 
  [ 2362.080945] EEH: PCI cmd/status register: 
  [ 2362.080945] EEH: PCI-E capabilities and status follow:
  [ 2362.080951] EEH: PCI-E 00:     
  [ 2362.080956] EEH: PCI-E 10:     
  [ 2362.080957] EEH: PCI-E 20:  
  [ 2362.080958] EEH: PCI-E AER capability register set follows:
  [ 2362.080964] EEH: PCI-E AER 00:     
  [ 2362.080969] EEH: PCI-E AER 10:     
  [ 2362.080974] EEH: PCI-E AER 20:     
  [ 2362.080975] EEH: PCI-E AER 30:   
  [ 2362.080977] PHB4 PHB#51 Diag-data (Version: 1)
  [ 2362.080978] brdgCtl:0002
  [ 2362.080979] RootSts:00060020 00402000 c1010008 00100107 
  [ 2362.080980] RootErrSts:  0020 
  [ 2362.080981] PhbSts: 001c 001c
  [ 2362.080982] Lem:0001  0001
  [ 2362.080983] PhbErr: 00c0 0080 214898000240 
a0084000
  [ 2362.080984] RegbErr:0090 0010 483c 
0200
  [ 2362.080985] PE[000] A/B: 8000 8000
  [ 2362.080987] PE[..1fe] A/B: as above
  [ 2362.080988] PE[1ff] A/B: b740002a0100 8000
  [

[Kernel-packages] [Bug 1802382] Status changed to Confirmed

This change was made by a bot.

** Changed in: linux (Ubuntu)
   Status: New => 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/1802382

Title:
  [860399.181468] watchdog: BUG: soft lockup - CPU#4 stuck for 23s!
  [kworker/4:2:9700]

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  system was halt after resume. I had to boot via Magic SysRq
  R-E-I-S-U-B routine.

  $ cat /proc/version_signature
  Ubuntu 4.15.0-38.41-generic 4.15.18

  ProblemType: KernelOops
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-36-generic 4.15.0-36.39
  ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18
  Uname: Linux 4.15.0-36-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  Annotation: Your system might become unstable now and might need to be 
restarted.
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  Date: Thu Nov  8 22:27:35 2018
  Failure: oops
  InstallationDate: Installed on 2018-06-01 (160 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: ASUSTeK COMPUTER INC. N550JV
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-38-generic 
root=UUID=d62c0813-bece-408d-8a4c-773ce7fbe368 ro quiet splash vt.handoff=1
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: kerneloops-daemon N/A
  SourcePackage: linux
  Title: [860399.181468] watchdog: BUG: soft lockup - CPU#4 stuck for 23s! 
[kworker/4:2:9700]
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/19/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: N550JV.208
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: N550JV
  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.:bvrN550JV.208:bd11/19/2013:svnASUSTeKCOMPUTERINC.:pnN550JV:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnN550JV:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: N
  dmi.product.name: N550JV
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1802382/+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 1802382] [NEW] [860399.181468] watchdog: BUG: soft lockup - CPU#4 stuck for 23s! [kworker/4:2:9700]

2018-11-08 Thread alperyilmaz

Public bug reported:

system was halt after resume. I had to boot via Magic SysRq R-E-I-S-U-B
routine.

$ cat /proc/version_signature
Ubuntu 4.15.0-38.41-generic 4.15.18

ProblemType: KernelOops
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-36-generic 4.15.0-36.39
ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18
Uname: Linux 4.15.0-36-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
Annotation: Your system might become unstable now and might need to be 
restarted.
ApportVersion: 2.20.9-0ubuntu7.4
Architecture: amd64
Date: Thu Nov  8 22:27:35 2018
Failure: oops
InstallationDate: Installed on 2018-06-01 (160 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
MachineType: ASUSTeK COMPUTER INC. N550JV
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-38-generic 
root=UUID=d62c0813-bece-408d-8a4c-773ce7fbe368 ro quiet splash vt.handoff=1
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions: kerneloops-daemon N/A
SourcePackage: linux
Title: [860399.181468] watchdog: BUG: soft lockup - CPU#4 stuck for 23s! 
[kworker/4:2:9700]
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/19/2013
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: N550JV.208
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: N550JV
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.:bvrN550JV.208:bd11/19/2013:svnASUSTeKCOMPUTERINC.:pnN550JV:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnN550JV:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.family: N
dmi.product.name: N550JV
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.

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


** Tags: amd64 apport-kerneloops bionic kernel-oops

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

Title:
  [860399.181468] watchdog: BUG: soft lockup - CPU#4 stuck for 23s!
  [kworker/4:2:9700]

Status in linux package in Ubuntu:
  New

Bug description:
  system was halt after resume. I had to boot via Magic SysRq
  R-E-I-S-U-B routine.

  $ cat /proc/version_signature
  Ubuntu 4.15.0-38.41-generic 4.15.18

  ProblemType: KernelOops
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-36-generic 4.15.0-36.39
  ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18
  Uname: Linux 4.15.0-36-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  Annotation: Your system might become unstable now and might need to be 
restarted.
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  Date: Thu Nov  8 22:27:35 2018
  Failure: oops
  InstallationDate: Installed on 2018-06-01 (160 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: ASUSTeK COMPUTER INC. N550JV
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-38-generic 
root=UUID=d62c0813-bece-408d-8a4c-773ce7fbe368 ro quiet splash vt.handoff=1
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: kerneloops-daemon N/A
  SourcePackage: linux
  Title: [860399.181468] watchdog: BUG: soft lockup - CPU#4 stuck for 23s! 
[kworker/4:2:9700]
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/19/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: N550JV.208
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: N550JV
  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.:bvrN550JV.208:bd11/19/2013:svnASUSTeKCOMPUTERINC.:pnN550JV:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnN550JV:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: N
  dmi.product.name: N550JV
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1802382/+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 1802377] Status changed to Confirmed

This change was made by a bot.

** Changed in: linux (Ubuntu)
   Status: New => 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/1802377

Title:
  package linux-headers-4.15.0-38-generic 4.15.0-38.41 failed to
  install/upgrade: installed linux-headers-4.15.0-38-generic package
  post-installation script subprocess was killed by signal (Terminated)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Running do-system-upgrade from 16.04, the upgrade hung at this point.
  I left it overnight w/ no progress. Eventually ^C and had to continue
  dpkg by hand.

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: linux-headers-4.15.0-38-generic 4.15.0-38.41
  ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18
  Uname: Linux 4.15.0-38-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  AudioDevicesInUse:
   Cannot stat file /proc/3753/fd/1023: Permission denied
USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm1831 F pulseaudio
wiml   2922 F pulseaudio
  Date: Thu Nov  8 10:29:30 2018
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-trusty-amd64-osp1-20150720-0
  ErrorMessage: installed linux-headers-4.15.0-38-generic package 
post-installation script subprocess was killed by signal (Terminated)
  HibernationDevice: RESUME=UUID=d9fd3e2c-cbf5-4a52-ab57-518de5eca517
  InstallationDate: Installed on 2016-04-15 (937 days ago)
  InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 
20150720-04:06
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0c45:670c Microdia 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 13 9350
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-38-generic 
root=UUID=cadacae6-ffd6-4900-b9fb-4a1fa02d1a59 ro quiet splash vt.handoff=1
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Python3Details: /usr/bin/python3.6, Python 3.6.6, python3-minimal, 
3.6.5-3ubuntu1
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions: grub-pc N/A
  RfKill:
   1: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  Title: package linux-headers-4.15.0-38-generic 4.15.0-38.41 failed to 
install/upgrade: installed linux-headers-4.15.0-38-generic package 
post-installation script subprocess was killed by signal (Terminated)
  UpgradeStatus: Upgraded to bionic on 2018-11-08 (0 days ago)
  dmi.bios.date: 01/08/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.3
  dmi.board.name: 07TYC2
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.3:bd01/08/2016:svnDellInc.:pnXPS139350:pvr:rvnDellInc.:rn07TYC2:rvrA01: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/1802377/+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 1802377] [NEW] package linux-headers-4.15.0-38-generic 4.15.0-38.41 failed to install/upgrade: installed linux-headers-4.15.0-38-generic package post-installation script subproc

2018-11-08 Thread Wim Lewis

Public bug reported:

Running do-system-upgrade from 16.04, the upgrade hung at this point. I
left it overnight w/ no progress. Eventually ^C and had to continue dpkg
by hand.

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: linux-headers-4.15.0-38-generic 4.15.0-38.41
ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18
Uname: Linux 4.15.0-38-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.4
Architecture: amd64
AudioDevicesInUse:
 Cannot stat file /proc/3753/fd/1023: Permission denied
  USERPID ACCESS COMMAND
 /dev/snd/controlC0:  gdm1831 F pulseaudio
  wiml   2922 F pulseaudio
Date: Thu Nov  8 10:29:30 2018
DistributionChannelDescriptor:
 # This is a distribution channel descriptor
 # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor
 canonical-oem-somerville-trusty-amd64-osp1-20150720-0
ErrorMessage: installed linux-headers-4.15.0-38-generic package 
post-installation script subprocess was killed by signal (Terminated)
HibernationDevice: RESUME=UUID=d9fd3e2c-cbf5-4a52-ab57-518de5eca517
InstallationDate: Installed on 2016-04-15 (937 days ago)
InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 
20150720-04:06
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 0c45:670c Microdia 
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Dell Inc. XPS 13 9350
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-38-generic 
root=UUID=cadacae6-ffd6-4900-b9fb-4a1fa02d1a59 ro quiet splash vt.handoff=1
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
Python3Details: /usr/bin/python3.6, Python 3.6.6, python3-minimal, 
3.6.5-3ubuntu1
PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
RelatedPackageVersions: grub-pc N/A
RfKill:
 1: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
SourcePackage: linux
Title: package linux-headers-4.15.0-38-generic 4.15.0-38.41 failed to 
install/upgrade: installed linux-headers-4.15.0-38-generic package 
post-installation script subprocess was killed by signal (Terminated)
UpgradeStatus: Upgraded to bionic on 2018-11-08 (0 days ago)
dmi.bios.date: 01/08/2016
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.2.3
dmi.board.name: 07TYC2
dmi.board.vendor: Dell Inc.
dmi.board.version: A01
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.3:bd01/08/2016:svnDellInc.:pnXPS139350:pvr:rvnDellInc.:rn07TYC2:rvrA01:cvnDellInc.:ct9:cvr:
dmi.product.name: XPS 13 9350
dmi.sys.vendor: Dell Inc.

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


** Tags: amd64 apport-package bionic

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

Title:
  package linux-headers-4.15.0-38-generic 4.15.0-38.41 failed to
  install/upgrade: installed linux-headers-4.15.0-38-generic package
  post-installation script subprocess was killed by signal (Terminated)

Status in linux package in Ubuntu:
  New

Bug description:
  Running do-system-upgrade from 16.04, the upgrade hung at this point.
  I left it overnight w/ no progress. Eventually ^C and had to continue
  dpkg by hand.

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: linux-headers-4.15.0-38-generic 4.15.0-38.41
  ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18
  Uname: Linux 4.15.0-38-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  AudioDevicesInUse:
   Cannot stat file /proc/3753/fd/1023: Permission denied
USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm1831 F pulseaudio
wiml   2922 F pulseaudio
  Date: Thu Nov  8 10:29:30 2018
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-trusty-amd64-osp1-20150720-0
  ErrorMessage: installed linux-headers-4.15.0-38-generic package 
post-installation script subprocess was killed by signal (Terminated)
  HibernationDevice: RESUME=UUID=d9fd3e2c-cbf5-4a52-ab57-518de5eca517
  InstallationDate: Installed on 2016-04-15 (937 days ago)
  InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 
20150720-04:06
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0c45:670c Microdia 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 13 9350
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-38-generic 
root=UUID=cadacae6-ffd6-4900-b9fb-4a1fa02d1a59 ro quiet splash vt.handoff=1
  PulseList: Error: command ['pacmd', 'list'] failed

[Kernel-packages] [Bug 1802341] Re: crash in ENA driver on removing an interface

I've tested this on affected configurations.

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

Title:
  crash in ENA driver on removing an interface

Status in linux package in Ubuntu:
  In Progress
Status in linux-aws package in Ubuntu:
  In Progress
Status in linux source package in Xenial:
  In Progress
Status in linux-aws source package in Xenial:
  In Progress
Status in linux source package in Bionic:
  In Progress
Status in linux-aws source package in Bionic:
  In Progress
Status in linux source package in Cosmic:
  In Progress
Status in linux-aws source package in Cosmic:
  In Progress
Status in linux source package in Disco:
  In Progress
Status in linux-aws source package in Disco:
  In Progress

Bug description:
  Bug present in ENA since driver version 1.6; manifests as a crash only
  under some conditions.

  In ena_remove() we have the following stack call:
  ena_remove()
unregister_netdev()
ena_destroy_device()
  netif_carrier_off()
  
  Calling netif_carrier_off() causes linkwatch to try to handle the
  link change event on the already unregistered netdev, which leads
  to a read from an unreadable memory address.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1802341/+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 1797367] Re: Ubuntu 18.04.1 - [s390x] Kernel panic while stressing network bonding

2018-11-08 Thread Frank Heimes

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

** Changed in: ubuntu-z-systems
   Status: In Progress => Fix Committed

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

Title:
  Ubuntu 18.04.1 - [s390x] Kernel panic while stressing network bonding

Status in Ubuntu on IBM z Systems:
  Fix Committed
Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Bionic:
  Fix Committed
Status in linux source package in Cosmic:
  Fix Committed

Bug description:
  == SRU Justification ==

  While running a series of stress tests for network on a bond device on Ubuntu 
18.04.1 with kernel 4.15.0-36.39,
  kernel panic is observed (btw. also on non-bond devices).
  This looks like a race between disabling a qeth device and accessing debugfs.
  This is critical and leads repeatedly to a crash (sooner or later).

  == Fix ==

  e19e5be8b4ca ("s390/qeth: sanitize strings in debug messages")

  pre-reqs:
  750b162 ("s390/qeth: reduce hard-coded access to ccw channels")
  d857e11 ("s390/qeth: remove outdated portname debug msg")
  9d0a58f ("s390/qeth: avoid using is_multicast_ether_addr_64bits on (u8 *)[6]")
  8174aa8 ("s390/qeth: consolidate qeth MAC address helpers")
  4641b02 ("s390/qeth: don't keep track of MAC address's cast type")

  == Regression Potential ==

  Low, because:

  - limited to s390x
  - and again limited to qeth driver
  - patches a problem identified during testing
  - fix was tested by IBM before submitted

  == Test Case ==

  run:
 #!/bin/bash
 var=0
 while :
 do
  var=$((var + 1))
  echo "DBG count is $var"
  mkdir /tmp/DBGINFO
  dbginfo.sh -d /tmp/DBGINFO
  rm -rf /tmp/DBGINFO*
  echo "chzdev now is $var"
  chzdev -e 
  chzdev -d 
 done
  and in avg. in less than 20 cycles a crash happens (usually < 10).

  __

  == Comment: #0 - Athira Rajeev
  ---Problem Description---
  While running a series of stress tests for network bonding on UBUNTU 18.04.1 
with kernel 4.15.0-36.39, kernel panic is observed.
  There are two instance of panic experienced with the same test procedures one 
of which indicates to be a kernel BUG.

  Contact Information = Athira Rajeev , Waiki
  Wright < wa...@us.ibm.com >

  ---uname output---
  #39-Ubuntu SMP Mon Sep 24 16:13:24 UTC 2018 4.15.0-36.39

  Machine Type = This issue is observed on z13 system
   ---Debugger---
  A debugger was configured,

  ---Steps to Reproduce---
  This happens while running stress tests for network bonding. kernel memory 
exposure attempt is detected and the BUG() is called from the code snippet: 
mm/usercopy.c:72
  dump was configured and crash dump is available.
  Results of few crash commands like bt, log are added in Attachment

  Relevant part of dmesg pointing to kernel BUG

  <<>>
  [14746.977364] kernel BUG at 
/build/linux-PABIrW/linux-4.15.0/mm/usercopy.c:72!
  [14746.977377] illegal operation: 0001 ilc:1 [#1] SMP
  [14746.977378] Modules linked in: macsec vsock_diag vsock sctp_diag sctp 
dccp_diag dccp tcp_diag udp_diag raw_diag inet_diag unix_diag af_packet_diag 
netlink_diag bonding binfmt_misc qeth_l3 8021q garp mrp stp llc xt_tcpudp 
qeth_l2 nf_conntrack_ipv6 nf_defrag_ipv6 scsi_dh_rdac scsi_dh_emc scsi_dh_alua 
s390_trng ghash_s390 prng sha512_s390 sha256_s390 sha1_s390 sha_common chsc_sch 
eadm_sch nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack libcrc32c 
crc32_vx_s390 qeth ccwgroup ip6table_filter ip6_tables vfio_ccw vfio_mdev mdev 
vfio_iommu_type1 vfio iptable_filter sch_fq_codel ip_tables x_tables aes_s390 
des_s390 des_generic dm_crypt dm_service_time dm_multipath zfcp 
scsi_transport_fc qdio dasd_eckd_mod dasd_mod btrfs xor zstd_compress raid6_pq 
zlib_deflate
  [14746.977401] CPU: 1 PID: 20905 Comm: dump2tar Tainted: G   OE
4.15.0-36-generic #39-Ubuntu
  [14746.977403] Hardware name: IBM 3906 M02 757 (LPAR)
  [14746.977404] Krnl PSW : 0f2d230d 6abe14d5 
(__check_object_size+0x15a/0x1e0)
  [14746.977408]R:0 T:1 IO:1 EX:1 Key:0 M:1 W:0 P:0 AS:3 CC:2 PM:0 
RI:0 EA:3
  [14746.977410] Krnl GPRS: 0002 00e95334 0064 
0001e6518828
  [14746.977412]0037cc8e  00a9577c 

  [14746.977413]647b 0001d8c120a8 0001 
8088
  [14746.977433]0001d8c0a020 0090da38 0037cc8e 
00016fdfbcd0
  [14746.977440] Krnl Code: 0037cc82: c0200038ef69larl
%r2,a9ab54
    0037cc88: c0e5fff32838brasl   
%r14,1e1cf8
   #0037cc8e: a7f40001brc 
15,37cc90
   >0037cc92: e330d0080004lg  
%r3,8(%r13)

[Kernel-packages] [Bug 1802341] Re: crash in ENA driver on removing an interface

Attached patch, developed in conjunction with the ENA dev team, fixes
the problem.  This patch is soon-to-be submitted upstream.

** Patch added: "0001-UBUNTU-SAUCE-net-ena-fix-crash-during-ena_remove.patch"
   
https://bugs.launchpad.net/ubuntu/disco/+source/linux-aws/+bug/1802341/+attachment/5210458/+files/0001-UBUNTU-SAUCE-net-ena-fix-crash-during-ena_remove.patch

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

Title:
  crash in ENA driver on removing an interface

Status in linux package in Ubuntu:
  In Progress
Status in linux-aws package in Ubuntu:
  In Progress
Status in linux source package in Xenial:
  In Progress
Status in linux-aws source package in Xenial:
  In Progress
Status in linux source package in Bionic:
  In Progress
Status in linux-aws source package in Bionic:
  In Progress
Status in linux source package in Cosmic:
  In Progress
Status in linux-aws source package in Cosmic:
  In Progress
Status in linux source package in Disco:
  In Progress
Status in linux-aws source package in Disco:
  In Progress

Bug description:
  Bug present in ENA since driver version 1.6; manifests as a crash only
  under some conditions.

  In ena_remove() we have the following stack call:
  ena_remove()
unregister_netdev()
ena_destroy_device()
  netif_carrier_off()
  
  Calling netif_carrier_off() causes linkwatch to try to handle the
  link change event on the already unregistered netdev, which leads
  to a read from an unreadable memory address.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1802341/+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 1802358] [NEW] [Hyper-V] Fix IRQ spreading on NVMe devices with lower numbers of channels

2018-11-08 Thread Joshua R. Poulson

Public bug reported:

1. Patch to kernel/irq/affinity.c:
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-
next.git/commit/kernel/irq/affinity.c?h=next-20181108=b82592199032bf7c778f861b936287e37ebc9f62.

2. Patches to kernel/irq/matrix.c. There are three patches for this. The
first two from Fujitsu, and then there is the patch from Long that actually
makes the previous two work correctly.
a.
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/kernel/irq/matrix.c?h=next-20181108=8ffe4e61c06a48324cfd97f1199bb9838acce2f2
b.
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/kernel/irq/matrix.c?h=next-20181108=76f99ae5b54d48430d1f0c5512a84da0ff9761e0
c.
https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git/commit/?h=irq/core=e8da8794a7fd9eef1ec9a07f0d4897c68581c72b

We expect the tip patch to be applied to Linux-next soon.

genirq/affinity: Spread IRQs to all available NUMA nodes

If the number of NUMA nodes exceeds the number of MSI/MSI-X interrupts
which are allocated for a device, the interrupt affinity spreading code
fails to spread them across all nodes.

The reason is, that the spreading code starts from node 0 and continues up
to the number of interrupts requested for allocation. This leaves the nodes
past the last interrupt unused.

This results in interrupt concentration on the first nodes which violates
the assumption of the block layer that all nodes are covered evenly. As a
consequence the NUMA nodes above the number of interrupts are all assigned
to hardware queue 0 and therefore NUMA node 0, which results in bad
performance and has CPU hotplug implications, because queue 0 gets shut
down when the last CPU of node 0 is offlined.

Go over all NUMA nodes and assign them round-robin to all requested
interrupts to solve this.

irq/matrix: Split out the CPU selection code into a helper

Linux finds the CPU which has the lowest vector allocation count to spread
out the non managed interrupts across the possible target CPUs, but does
not do so for managed interrupts.

Split out the CPU selection code into a helper function for reuse. No
functional change.

irq/matrix: Spread managed interrupts on allocation

Linux spreads out the non managed interrupt across the possible target CPUs
to avoid vector space exhaustion.

Managed interrupts are treated differently, as for them the vectors are
reserved (with guarantee) when the interrupt descriptors are initialized.

When the interrupt is requested a real vector is assigned. The assignment
logic uses the first CPU in the affinity mask for assignment. If the
interrupt has more than one CPU in the affinity mask, which happens when a
multi queue device has less queues than CPUs, then doing the same search as
for non managed interrupts makes sense as it puts the interrupt on the
least interrupt plagued CPU. For single CPU affine vectors that's obviously
a NOOP.

Restructre the matrix allocation code so it does the 'best CPU' search, add
the sanity check for an empty affinity mask and adapt the call site in the
x86 vector management code.

genirq/matrix: Improve target CPU selection for managed interrupts.irq/core
On large systems with multiple devices of the same class (e.g. NVMe disks,
using managed interrupts), the kernel can affinitize these interrupts to a
small subset of CPUs instead of spreading them out evenly.

irq_matrix_alloc_managed() tries to select the CPU in the supplied cpumask
of possible target CPUs which has the lowest number of interrupt vectors
allocated.

This is done by searching the CPU with the highest number of available
vectors. While this is correct for non-managed CPUs it can select the wrong
CPU for managed interrupts. Under certain constellations this results in
affinitizing the managed interrupts of several devices to a single CPU in
a set.

The book keeping of available vectors works the following way:

1) Non-managed interrupts:

available is decremented when the interrupt is actually requested by
the device driver and a vector is assigned. It's incremented when the
interrupt and the vector are freed.

2) Managed interrupts:

Managed interrupts guarantee vector reservation when the MSI/MSI-X
functionality of a device is enabled, which is achieved by reserving
vectors in the bitmaps of the possible target CPUs. This reservation
decrements the available count on each possible target CPU.

When the interrupt is requested by the device driver then a vector is
allocated from the reserved region. The operation is reversed when the
interrupt is freed by the device driver. Neither of these operations
affect the available count.

The reservation persist up to the point where the MSI/MSI-X
functionality is disabled and only this operation increments the
available count again.

For non-managed interrupts the available count is the correct selection
criterion because the guaranteed

[Kernel-packages] [Bug 1802341] Re: crash in ENA driver on removing an interface

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

** Also affects: linux (Ubuntu Disco)
   Importance: Undecided
 Assignee: Kamal Mostafa (kamalmostafa)
   Status: In Progress

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

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

** Changed in: linux (Ubuntu Xenial)
 Assignee: (unassigned) => Kamal Mostafa (kamalmostafa)

** Changed in: linux (Ubuntu Bionic)
 Assignee: (unassigned) => Kamal Mostafa (kamalmostafa)

** Changed in: linux (Ubuntu Cosmic)
 Assignee: (unassigned) => Kamal Mostafa (kamalmostafa)

** Changed in: linux (Ubuntu Xenial)
   Status: New => In Progress

** Changed in: linux (Ubuntu Bionic)
   Status: New => In Progress

** Changed in: linux (Ubuntu Cosmic)
   Status: New => In Progress

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

** Changed in: linux-aws (Ubuntu Xenial)
   Status: New => In Progress

** Changed in: linux-aws (Ubuntu Xenial)
 Assignee: (unassigned) => Kamal Mostafa (kamalmostafa)

** Changed in: linux-aws (Ubuntu Bionic)
   Status: New => In Progress

** Changed in: linux-aws (Ubuntu Bionic)
 Assignee: (unassigned) => Kamal Mostafa (kamalmostafa)

** Changed in: linux-aws (Ubuntu Cosmic)
   Status: New => In Progress

** Changed in: linux-aws (Ubuntu Cosmic)
 Assignee: (unassigned) => Kamal Mostafa (kamalmostafa)

** Changed in: linux-aws (Ubuntu Disco)
   Status: New => In Progress

** Changed in: linux-aws (Ubuntu Disco)
 Assignee: (unassigned) => Kamal Mostafa (kamalmostafa)

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

Title:
  crash in ENA driver on removing an interface

Status in linux package in Ubuntu:
  In Progress
Status in linux-aws package in Ubuntu:
  In Progress
Status in linux source package in Xenial:
  In Progress
Status in linux-aws source package in Xenial:
  In Progress
Status in linux source package in Bionic:
  In Progress
Status in linux-aws source package in Bionic:
  In Progress
Status in linux source package in Cosmic:
  In Progress
Status in linux-aws source package in Cosmic:
  In Progress
Status in linux source package in Disco:
  In Progress
Status in linux-aws source package in Disco:
  In Progress

Bug description:
  Bug present in ENA since driver version 1.6; manifests as a crash only
  under some conditions.

  In ena_remove() we have the following stack call:
  ena_remove()
unregister_netdev()
ena_destroy_device()
  netif_carrier_off()
  
  Calling netif_carrier_off() causes linkwatch to try to handle the
  link change event on the already unregistered netdev, which leads
  to a read from an unreadable memory address.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1802341/+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 1775068] Re: Volume control not working Dell XPS 27 (7760)

2018-11-08 Thread Wojciech Solarczyk

Hi,

I'm currently on the Cosmic release, but I will install Xenial on
external usb and check 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/1775068

Title:
  Volume control not working Dell XPS 27 (7760)

Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Xenial:
  Fix Committed

Bug description:
  Pressing vol up/vol down show OSD change up/down but volume all time
  is at 100%.

  I found temporary fix:

  Add section:
  [Element Master]
  switch = mute
  volume = ignore

  To:
  /usr/share/pulseaudio/alsa-mixer/paths/analog-output.conf.common
  ---
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  trolinka   1610 F pulseaudio
   /dev/snd/controlC1:  trolinka   1610 F pulseaudio
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-06-02 (121 days ago)
  InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  Package: pulseaudio 1:11.1-1ubuntu7.1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18
  Tags:  bionic
  Uname: Linux 4.15.0-34-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dip lpadmin netdev plugdev sambashare scanner 
sudo vboxusers video
  _MarkForUpload: True
  dmi.bios.date: 07/13/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.4.0
  dmi.board.name: 0T12MX
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 13
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.4.0:bd07/13/2018:svnDellInc.:pnXPS7760AIO:pvr:rvnDellInc.:rn0T12MX:rvrA00:cvnDellInc.:ct13:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 7760 AIO
  dmi.sys.vendor: Dell Inc.
  ---
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  trolinka   1846 F pulseaudio
   /dev/snd/controlC1:  trolinka   1846 F pulseaudio
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-06-02 (122 days ago)
  InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  MachineType: Dell Inc. XPS 7760 AIO
  Package: pulseaudio 1:11.1-1ubuntu7.1
  PackageArchitecture: amd64
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic 
root=UUID=3df8d974-f6bb-455e-a7a6-a7099388ad54 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-36-generic N/A
   linux-backports-modules-4.15.0-36-generic  N/A
   linux-firmware 1.173.1
  Tags:  bionic
  Uname: Linux 4.15.0-36-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dip lpadmin netdev plugdev sambashare scanner 
sudo vboxusers video
  _MarkForUpload: True
  dmi.bios.date: 07/13/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.4.0
  dmi.board.name: 0T12MX
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 13
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.4.0:bd07/13/2018:svnDellInc.:pnXPS7760AIO:pvr:rvnDellInc.:rn0T12MX:rvrA00:cvnDellInc.:ct13:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 7760 AIO
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1775068/+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 1797990] Re: kdump fail due to an IRQ storm

2018-11-08 Thread Mauricio Faria de Oliveira

Attaching for documentation purposes,

Tarball with 'dmesg -t | sort' for boot/kexec & option disabled/enabled,
in Xenial, Bionic, Cosmic, Disco.

** Attachment added: "sf202166.dmesg.tar.xz"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1797990/+attachment/5210405/+files/sf202166.dmesg.tar.xz

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

Title:
  kdump fail due to an IRQ storm

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Trusty:
  Confirmed
Status in linux source package in Xenial:
  Confirmed
Status in linux source package in Bionic:
  Confirmed
Status in linux source package in Cosmic:
  Confirmed

Bug description:
  [Impact]

   * A kexec/crash kernel might get stuck and fail to boot
     (for crash kernel, kdump fails to collect a crashdump)
     if a PCI device is buggy/stuck/looping and triggers a
     continuous flood of MSI(X) interrupts (that the kernel
     does not yet know about).

   * This fix allowed to obtain crashdumps when debugging a
     heavy-load scenario, in which a (heavy-loaded) network
     adapter wouldn't stop triggering MSI-X interrupts ever
     after panic()->kdump kicked in.

   * This fix disables MSI(X) in all PCI devices on early
     boot (this is OK as it's (re-)enabled normally later)
     with a kernel cmdline parameter (disabled by default).

  [Test Case]

   * A synthetic test-case is not yet available, however,
     this particular system/workload triggered the problem
     consistently, and it was used for development/testing.

   * We'll update this bug once a synthetic test-case is
     available; we're working on patching QEMU for this.

   * $ cat /proc/cmdline
 <...> pci=clearmsi

 $ dmesg | grep 'Clearing MSI'
     [0.00] Clearing MSI/MSI-X enable bits early in boot (quirk)

   * The comparison of 'dmesg -t | sort' has been reviewed
     between option disabled/enabled on boot & kexec modes,
     and only expected differences found (MHz, PIDs, MIPS).

  [Regression Potential]

   * The potential area for regressions is early boot,
     particularly effects of applying quirks during PCI
     bus scan, which is changed/broader w/ these patches.

   * However, all quirks are applied based on PCI ID
     matching, so would only apply if actually targeting
     a new device.

   * Moreover, the new quirk is only applied based on
     a kernel cmdline parameter that is disabled by
     default, which constraints even more when this
     is actually in effect.

  [Other Info]

   * The patch series is still under review/discussion
     upstream, but it's relatively important for Ubuntu
     users at this point, and after internal discussions
     we decided to submit it for SRU.

   * These are links to the linux-pci archive with the
     patches [1, 2, 3]

     [1] [PATCH 1/3] x86/quirks: Scan all busses for early PCI quirks
     
https://lore.kernel.org/linux-pci/20181018183721.27467-1-gpicc...@canonical.com/

     [2] [PATCH 2/3] x86/PCI: Export find_cap() to be used in early PCI code
     
https://lore.kernel.org/linux-pci/20181018183721.27467-2-gpicc...@canonical.com/

     [3] [PATCH 3/3] x86/quirks: Add parameter to clear MSIs early on boot
     
https://lore.kernel.org/linux-pci/20181018183721.27467-3-gpicc...@canonical.com/

  [Original Description]

  We have reports of a kdump failure in Ubuntu (in x86 machine) that was
  narrowed down to a MSI irq storm coming from a PCI network device.

  The bug manifests as a lack of progress in the boot process of the
  kdump kernel, and a storm of kernel messages like:

  [...]
  [  342.265294] do_IRQ: 0.155 No irq handler for vector
  [  342.266916] do_IRQ: 0.155 No irq handler for vector
  [  347.258422] do_IRQ: 14053260 callbacks suppressed
  [...]

  The root cause of the issue is that the kdump kernel kexec process
  does not ensure PCI devices are reset and/or MSI capabilities are
  disabled, so a PCI device could produce a huge amount of PCI irqs
  which would take all the processing time for the CPU (specially since
  we restrict the kdump kernel to use one single CPU only).

  This was tested using upstream kernel version 4.18, and the problem 
reproduces.
  In the specific test scenario, the PCI NIC was an "Intel 82599ES 10-Gigabit 
[8086:10fb]" that was used in SR-IOV PCI passthrough mode (vfio_pci), under 
high load on the guest.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1797990/+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 1799453] Re: linux-kvm: 4.18.0-1004.4 -proposed tracker

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1799445
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   certification-testing: Testing in progress
verification-testing: Testing in progress

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

Title:
  linux-kvm: 4.18.0-1004.4 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-kvm package in Ubuntu:
  Confirmed
Status in linux-kvm source package in Cosmic:
  Confirmed

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1799445
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
verification-testing: Testing in progress

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1799453/+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 1799451] Re: linux-azure: 4.18.0-1004.4 -proposed tracker

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1799445
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   certification-testing: Testing in progress
regression-testing: Testing in progress
stakeholder-signoff: Waiting for signoff
verification-testing: Testing in progress

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

Title:
  linux-azure: 4.18.0-1004.4 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow stakeholder-signoff series:
  Confirmed
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-azure package in Ubuntu:
  Confirmed
Status in linux-azure source package in Cosmic:
  Confirmed

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1799445
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
regression-testing: Testing in progress
stakeholder-signoff: Waiting for signoff
verification-testing: Testing in progress

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1799451/+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

Re: [Kernel-packages] [Bug 1791427] Re: Touchpad and/or trackpoint stop working after S3 suspend on Lenovo X1 Carbon 6th

2018-11-08 Thread NJ

That is informative. Thank you. However: Lenovo support tends to be
clueless with Linux, so finding out from Lenovo when this fix will ever
appear is hard. Might you or someone else be able to advise on that?

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

Title:
  Touchpad and/or trackpoint stop working after S3 suspend on Lenovo X1
  Carbon 6th

Status in linux package in Ubuntu:
  Triaged

Bug description:
  Ubuntu 18.04.1

  Terminology in case we use different terms:
  touchpad - just the rectangular touch-sensitive surface below the keyboard 
(xinput lists it as Synaptics TM3288-011)
  trackpoint - the red thingy built into the keyboard + 3 physical buttons 
below the keyboard (trackpoint and buttons are integrated together; listed in 
xinput as TPPS/2 Elan TrackPoint)

  On September 7th, 2018, Lenovo has issued a BIOS update (v1.30), which
  enables proper S3 deep sleep state - users no longer have to patch
  DSDT tables to get it. It can be enabled in the BIOS settings. In X1
  carbon 6th generation models that have NFC, when laptop wakes from
  suspend by opening the lid, in most cases both touchpad and trackpoint
  stop working completely. They are also no longer listed when running
  xinput command. Sometimes just one of them stops working, usually the
  trackpoint. In some rare cases it is possible to bring them back by
  using these commands:

  echo -n none > /sys/devices/platform/i8042/serio1/drvctl
  echo -n reconnect > /sys/devices/platform/i8042/serio1/drvctl
  rmmod psmouse
  modprobe psmouse

  These worked properly when waking up from S2Idle sleep state (had
  these in a script that runs after waking the machine from suspend),
  but with S3 deep sleep these rarely work and the only way to bring
  back touchpad and/or trackpoint is turning off the machine and turning
  it on (restart does not help).

  I could not find any pattern that would show when the input devices
  stop working or start working again using the commands mentioned
  above. It's completely random from my perspective.

  This is happening on the standard issue 4.15.0-33-generic kernel that
  shipped with my Ubuntu 18.04 (with updates), as well as with newer
  mainline kernels, such as the newest point versions of 4.17, 4.18 and
  4.19 RC2.

  This happens regardless of whether "blacklist i2c_i801" is commented
  out in /etc/modprobe.d/blacklist.conf or not. It happens regardless of
  whether "psmouse.synaptics_intertouch=1" is passed as grub parameter.
  Presence of TLP does not make it better, nor worse.

  It appears that non-NFC models are not affected. I know at least one
  Arch Linux user who has the exact same model, but without this issue.
  I'm using synaptics driver (no libinput installed), he uses libinput
  and doesn't have synaptics, if that information is of any use.
  Libinput does not seem to help.

  This forum thread also has more details from users who updated their
  BIOS to get S3 suspend: https://forums.lenovo.com/t5/Linux-
  Discussion/X1-Carbon-Gen-6-cannot-enter-deep-sleep-S3-state-aka-
  Suspend-to/td-p/3998182/page/27

  Another related thread:
  https://bbs.archlinux.org/viewtopic.php?id=236367

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-33-generic 4.15.0-33.36
  ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
  Uname: Linux 4.15.0-33-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   maciej 2651 F...m pulseaudio
   /dev/snd/controlC0:  maciej 2651 F pulseaudio
  CurrentDesktop: i3
  Date: Sat Sep  8 13:45:43 2018
  HibernationDevice: RESUME=UUID=3116dcb0-d91e-4b2a-8166-43b7a9a9d36e
  InstallationDate: Installed on 2018-07-21 (49 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 13d3:56b2 IMC Networks 
   Bus 001 Device 002: ID 04b4:0060 Cypress Semiconductor Corp. Wireless 
optical mouse
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 20KH006KPB
  ProcFB:
   0 EFI VGA
   1 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-33-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash psmouse.synaptics_intertouch=1 
vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-33-generic N/A
   linux-backports-modules-4.15.0-33-generic  N/A
   linux-firmware 1.173.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/31/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N23ET55W (1.30 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20KH006KPB
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN

[Kernel-packages] [Bug 1797990] Re: kdump fail due to an IRQ storm

2018-11-08 Thread Mauricio Faria de Oliveira

Patch set v2 submitted to the kernel-team mailing list
for Xenial, Bionic, Cosmic, Disco.

[SRU X][PATCH v2 0/3] Add kernel parameter 'pci=clearmsi' to clear MSI(X)s 
early on boot
https://lists.ubuntu.com/archives/kernel-team/2018-November/096631.html

[SRU B][PATCH v2 0/3] Add kernel parameter 'pci=clearmsi' to clear MSI(X)s 
early on boot
https://lists.ubuntu.com/archives/kernel-team/2018-November/096635.html

[SRU C][PATCH v2 0/3] Add kernel parameter 'pci=clearmsi' to clear MSI(X)s 
early on boot
https://lists.ubuntu.com/archives/kernel-team/2018-November/096642.html

[D][PATCH v2 0/3] Add kernel parameter 'pci=clearmsi' to clear MSI(X)s early on 
boot
https://lists.ubuntu.com/archives/kernel-team/2018-November/096646.html

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

Title:
  kdump fail due to an IRQ storm

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Trusty:
  Confirmed
Status in linux source package in Xenial:
  Confirmed
Status in linux source package in Bionic:
  Confirmed
Status in linux source package in Cosmic:
  Confirmed

Bug description:
  [Impact]

   * A kexec/crash kernel might get stuck and fail to boot
     (for crash kernel, kdump fails to collect a crashdump)
     if a PCI device is buggy/stuck/looping and triggers a
     continuous flood of MSI(X) interrupts (that the kernel
     does not yet know about).

   * This fix allowed to obtain crashdumps when debugging a
     heavy-load scenario, in which a (heavy-loaded) network
     adapter wouldn't stop triggering MSI-X interrupts ever
     after panic()->kdump kicked in.

   * This fix disables MSI(X) in all PCI devices on early
     boot (this is OK as it's (re-)enabled normally later)
     with a kernel cmdline parameter (disabled by default).

  [Test Case]

   * A synthetic test-case is not yet available, however,
     this particular system/workload triggered the problem
     consistently, and it was used for development/testing.

   * We'll update this bug once a synthetic test-case is
     available; we're working on patching QEMU for this.

   * $ cat /proc/cmdline
 <...> pci=clearmsi

 $ dmesg | grep 'Clearing MSI'
     [0.00] Clearing MSI/MSI-X enable bits early in boot (quirk)

   * The comparison of 'dmesg -t | sort' has been reviewed
     between option disabled/enabled on boot & kexec modes,
     and only expected differences found (MHz, PIDs, MIPS).

  [Regression Potential]

   * The potential area for regressions is early boot,
     particularly effects of applying quirks during PCI
     bus scan, which is changed/broader w/ these patches.

   * However, all quirks are applied based on PCI ID
     matching, so would only apply if actually targeting
     a new device.

   * Moreover, the new quirk is only applied based on
     a kernel cmdline parameter that is disabled by
     default, which constraints even more when this
     is actually in effect.

  [Other Info]

   * The patch series is still under review/discussion
     upstream, but it's relatively important for Ubuntu
     users at this point, and after internal discussions
     we decided to submit it for SRU.

   * These are links to the linux-pci archive with the
     patches [1, 2, 3]

     [1] [PATCH 1/3] x86/quirks: Scan all busses for early PCI quirks
     
https://lore.kernel.org/linux-pci/20181018183721.27467-1-gpicc...@canonical.com/

     [2] [PATCH 2/3] x86/PCI: Export find_cap() to be used in early PCI code
     
https://lore.kernel.org/linux-pci/20181018183721.27467-2-gpicc...@canonical.com/

     [3] [PATCH 3/3] x86/quirks: Add parameter to clear MSIs early on boot
     
https://lore.kernel.org/linux-pci/20181018183721.27467-3-gpicc...@canonical.com/

  [Original Description]

  We have reports of a kdump failure in Ubuntu (in x86 machine) that was
  narrowed down to a MSI irq storm coming from a PCI network device.

  The bug manifests as a lack of progress in the boot process of the
  kdump kernel, and a storm of kernel messages like:

  [...]
  [  342.265294] do_IRQ: 0.155 No irq handler for vector
  [  342.266916] do_IRQ: 0.155 No irq handler for vector
  [  347.258422] do_IRQ: 14053260 callbacks suppressed
  [...]

  The root cause of the issue is that the kdump kernel kexec process
  does not ensure PCI devices are reset and/or MSI capabilities are
  disabled, so a PCI device could produce a huge amount of PCI irqs
  which would take all the processing time for the CPU (specially since
  we restrict the kdump kernel to use one single CPU only).

  This was tested using upstream kernel version 4.18, and the problem 
reproduces.
  In the specific test scenario, the PCI NIC was an "Intel 82599ES 10-Gigabit 
[8086:10fb]" that was used in SR-IOV PCI passthrough mode (vfio_pci), under 
high load on the guest.

To manage notifications about this bug go to:

[Kernel-packages] [Bug 1800805] Re: linux-azure: 4.15.0-1031.32~16.04.1 -proposed tracker

** Changed in: kernel-sru-workflow/automated-testing
   Status: Incomplete => Fix Released

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1799411
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   automated-testing: Testing FAILED
regression-testing: Testing in progress
stakeholder-signoff: Waiting for signoff
verification-testing: Testing in progress

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

Title:
  linux-azure: 4.15.0-1031.32~16.04.1 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-beta series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-candidate series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-edge series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-stable series:
  Invalid
Status in Kernel SRU Workflow stakeholder-signoff series:
  Confirmed
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-azure package in Ubuntu:
  Invalid
Status in linux-azure source package in Xenial:
  Confirmed

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1799411
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
regression-testing: Testing in progress
stakeholder-signoff: Waiting for signoff
verification-testing: Testing in progress

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1800805/+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 1801114] Re: linux-aws: 4.18.0-1004.5 -proposed tracker

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1799445
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   certification-testing: Testing in progress
regression-testing: Testing in progress
verification-testing: Testing in progress

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

Title:
  linux-aws: 4.18.0-1004.5 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-aws package in Ubuntu:
  Invalid
Status in linux-aws source package in Cosmic:
  Confirmed

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1799445
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
regression-testing: Testing in progress
verification-testing: Testing in progress

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1801114/+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 1799453] Re: linux-kvm: 4.18.0-1004.4 -proposed tracker

Certification tests not needed for cloud kernels.

** Changed in: kernel-sru-workflow/certification-testing
   Status: Confirmed => Invalid

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

Title:
  linux-kvm: 4.18.0-1004.4 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-kvm package in Ubuntu:
  Confirmed
Status in linux-kvm source package in Cosmic:
  Confirmed

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1799445
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
verification-testing: Testing in progress

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1799453/+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 1799451] Re: linux-azure: 4.18.0-1004.4 -proposed tracker

Certification tests not needed for cloud kernels.

** Changed in: kernel-sru-workflow/certification-testing
   Status: Confirmed => Invalid

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

Title:
  linux-azure: 4.18.0-1004.4 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow stakeholder-signoff series:
  Confirmed
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-azure package in Ubuntu:
  Confirmed
Status in linux-azure source package in Cosmic:
  Confirmed

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1799445
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
regression-testing: Testing in progress
stakeholder-signoff: Waiting for signoff
verification-testing: Testing in progress

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1799451/+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 1799416] Re: linux-gcp: 4.15.0-1024.25 -proposed tracker

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1799411
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Testing FAILED
regression-testing: Testing in progress
+   stakeholder-signoff: Waiting for signoff
verification-testing: Testing in progress

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

Title:
  linux-gcp: 4.15.0-1024.25 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-beta series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-candidate series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-edge series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-stable series:
  Invalid
Status in Kernel SRU Workflow stakeholder-signoff series:
  Confirmed
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-gcp package in Ubuntu:
  Invalid
Status in linux-gcp source package in Bionic:
  Confirmed

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1799411
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Testing FAILED
regression-testing: Testing in progress
stakeholder-signoff: Waiting for signoff
verification-testing: Testing in progress

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1799416/+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 1799452] Re: linux-gcp: 4.18.0-1003.4 -proposed tracker

Certification tests not needed for cloud kernels.

** Changed in: kernel-sru-workflow/certification-testing
   Status: Confirmed => Invalid

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

Title:
  linux-gcp: 4.18.0-1003.4 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-beta series:
  Invalid
Status in Kernel SRU Workflow snap-release-to-candidate series:
  Invalid
Status in Kernel SRU Workflow snap-release-to-edge series:
  Invalid
Status in Kernel SRU Workflow snap-release-to-stable series:
  Invalid
Status in Kernel SRU Workflow stakeholder-signoff series:
  In Progress
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-gcp package in Ubuntu:
  Confirmed
Status in linux-gcp source package in Cosmic:
  Confirmed

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1799445
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
regression-testing: Testing in progress
stakeholder-signoff: Waiting for signoff
verification-testing: Testing in progress

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1799452/+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 1799452] Re: linux-gcp: 4.18.0-1003.4 -proposed tracker

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1799445
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   certification-testing: Testing in progress
regression-testing: Testing in progress
+   stakeholder-signoff: Waiting for signoff
verification-testing: Testing in progress

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

Title:
  linux-gcp: 4.18.0-1003.4 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-beta series:
  Invalid
Status in Kernel SRU Workflow snap-release-to-candidate series:
  Invalid
Status in Kernel SRU Workflow snap-release-to-edge series:
  Invalid
Status in Kernel SRU Workflow snap-release-to-stable series:
  Invalid
Status in Kernel SRU Workflow stakeholder-signoff series:
  In Progress
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-gcp package in Ubuntu:
  Confirmed
Status in linux-gcp source package in Cosmic:
  Confirmed

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1799445
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
regression-testing: Testing in progress
stakeholder-signoff: Waiting for signoff
verification-testing: Testing in progress

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1799452/+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 1801114] Re: linux-aws: 4.18.0-1004.5 -proposed tracker

Certification tests not needed for cloud kernels.

** Changed in: kernel-sru-workflow/certification-testing
   Status: Confirmed => Invalid

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

Title:
  linux-aws: 4.18.0-1004.5 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-aws package in Ubuntu:
  Invalid
Status in linux-aws source package in Cosmic:
  Confirmed

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1799445
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
regression-testing: Testing in progress
verification-testing: Testing in progress

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1801114/+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 1799452] Re: linux-gcp: 4.18.0-1003.4 -proposed tracker

2018-11-08 Thread Andy Whitcroft

This kernel needs a nvidia specific blob to be released before it is
releasable.

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

Title:
  linux-gcp: 4.18.0-1003.4 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-beta series:
  Invalid
Status in Kernel SRU Workflow snap-release-to-candidate series:
  Invalid
Status in Kernel SRU Workflow snap-release-to-edge series:
  Invalid
Status in Kernel SRU Workflow snap-release-to-stable series:
  Invalid
Status in Kernel SRU Workflow stakeholder-signoff series:
  In Progress
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-gcp package in Ubuntu:
  Confirmed
Status in linux-gcp source package in Cosmic:
  Confirmed

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1799445
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
regression-testing: Testing in progress
stakeholder-signoff: Waiting for signoff
verification-testing: Testing in progress

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1799452/+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 1795292] Re: ELAN469D touch pad not working

2018-11-08 Thread FF8Jake

So far, my wifi has worked consistently, but maybe I am just lucky.
Considering the random nature of the keyboard, it makes me wonder if
some of us seeing ELAN in dmesg and some not is also pure luck of the
draw on that bootup as well.

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

Title:
  ELAN469D touch pad not working

Status in Linux:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I installed Bionic Beaver and now upgraded to Cosmic Cuttlefish on
  this Lenovo Ideapad 330S-15ARR laptop.  The touch pad doesn't work in
  either.

  Some possibly relevant info from dmesg:
  i2c_hid i2c-ELAN469D:00: i2c-ELAN469D:00 supply vdd not found, using dummy 
regulator
  i2c_designware AMDI0010:01: controller timed out

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.18.0-7-generic 4.18.0-7.8
  ProcVersionSignature: Ubuntu 4.18.0-7.8-generic 4.18.5
  Uname: Linux 4.18.0-7-generic x86_64
  ApportVersion: 2.20.10-0ubuntu11
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  xorbit 2086 F pulseaudio
   /dev/snd/pcmC1D0p:   xorbit 2086 F...m pulseaudio
   /dev/snd/controlC0:  xorbit 2086 F pulseaudio
  CurrentDesktop: GNOME
  Date: Sun Sep 30 23:14:26 2018
  InstallationDate: Installed on 2018-09-20 (10 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: LENOVO 81FB
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-7-generic 
root=UUID=4d91f09e-6122-4dd4-81fc-482465f8f0e7 ro noapic processor.max_cstate=1 
rcu_nocbs=0-7 pcie_aspm=off pci=noaer quiet splash vt.handoff=1 
elan_i2c.dyndbg=+p
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-7-generic N/A
   linux-backports-modules-4.18.0-7-generic  N/A
   linux-firmware1.175
  SourcePackage: linux
  UpgradeStatus: Upgraded to cosmic on 2018-09-30 (0 days ago)
  dmi.bios.date: 06/08/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 7WCN22WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709WIN
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad 330S-15ARR
  dmi.modalias: 
dmi:bvnLENOVO:bvr7WCN22WW:bd06/08/2018:svnLENOVO:pn81FB:pvrLenovoideapad330S-15ARR:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoideapad330S-15ARR:
  dmi.product.family: ideapad 330S-15ARR
  dmi.product.name: 81FB
  dmi.product.sku: LENOVO_MT_81FB_BU_idea_FM_ideapad 330S-15ARR
  dmi.product.version: Lenovo ideapad 330S-15ARR
  dmi.sys.vendor: LENOVO
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu11
  Architecture: amd64
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 18.10
  InstallationDate: Installed on 2018-09-20 (13 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Tags:  cosmic
  Uname: Linux 4.19.0-041900rc6-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: Upgraded to cosmic on 2018-09-30 (2 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1795292/+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 1799416] Re: linux-gcp: 4.15.0-1024.25 -proposed tracker

2018-11-08 Thread Andy Whitcroft

This kernel needs a nvidia specific blob to be released before it is
releasable.

** Also affects: kernel-sru-workflow/stakeholder-signoff
   Importance: Undecided
   Status: New

** Changed in: kernel-sru-workflow/stakeholder-signoff
   Status: New => Confirmed

** Changed in: kernel-sru-workflow/stakeholder-signoff
 Assignee: (unassigned) => Andy Whitcroft (apw)

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

Title:
  linux-gcp: 4.15.0-1024.25 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-beta series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-candidate series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-edge series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-stable series:
  Invalid
Status in Kernel SRU Workflow stakeholder-signoff series:
  Confirmed
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-gcp package in Ubuntu:
  Invalid
Status in linux-gcp source package in Bionic:
  Confirmed

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1799411
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Testing FAILED
regression-testing: Testing in progress
stakeholder-signoff: Waiting for signoff
verification-testing: Testing in progress

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1799416/+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 1801349] Re: zpool create -f lxd /dev/vdb fails on cosmic (18.10) -- func27

2018-11-08 Thread Colin Ian King

Hi Alex,

Is it possible to get the necessary commands to allow me to create the
instances so I can do some experimental changes? I'm wrestling with
getting a sane debugging environment with the instance you provided.

Colin

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

Title:
  zpool create -f lxd /dev/vdb fails on cosmic (18.10) -- func27

Status in OpenStack LXD Charm:
  New
Status in linux package in Ubuntu:
  In Progress

Bug description:
  Test: tests/gate-basic-cosmic-rocky

  As part of the config, the lxd charm creates a pool device depending
  on the config.  The test config is:

  lxd_config = {
  'block-devices': '/dev/vdb',
  'ephemeral-unmount': '/mnt',
  'storage-type': 'zfs',
  'overwrite': True
  }

  The config drive is normally mounted on /mnt, and the lxd charm
  umounts it as part of the start up.  The /etc/fstab on the unit is:

  # cat /etc/fstab 
  LABEL=cloudimg-rootfs   /ext4   defaults0 0
  LABEL=UEFI  /boot/efi   vfatdefaults0 0
  /dev/vdb/mntauto
defaults,nofail,x-systemd.requires=cloud-init.service,comment=cloudconfig   
0   2
  /dev/vdcnoneswapsw,comment=cloudconfig  0   0

  
  However, even after umount-ing the /mnt off of /dev/vdb, the zpool create 
command still fails:

  # zpool create -f lxd /dev/vdb
  /dev/vdb is in use and contains a unknown filesystem.

  
  If the /etc/fstab is edited so that /dev/vdb is *never* mounted and then 
rebooted, then the zpool create command succeeds:

  # zpool list
  NAME   SIZE  ALLOC   FREE  EXPANDSZ   FRAGCAP  DEDUP  HEALTH  ALTROOT
  lxd   14.9G   106K  14.9G - 0% 0%  1.00x  ONLINE  -

  # zpool status lxd
pool: lxd
   state: ONLINE
scan: none requested
  config:

  NAMESTATE READ WRITE CKSUM
  lxd ONLINE   0 0 0
vdb   ONLINE   0 0 0

  errors: No known data errors

  Something odd is going on with cosmic (18.10) and the combination of
  lxd, zfs and the kernel

  lxd version: 3.6
  zfsutils-linux/cosmic,now 0.7.9-3ubuntu6
  Linux: 4.18.0-10-generic

To manage notifications about this bug go to:
https://bugs.launchpad.net/charm-lxd/+bug/1801349/+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 1802341] [NEW] crash in ENA driver on removing an interface

Public bug reported:

Bug present in ENA since driver version 1.6; manifests as a crash only
under some conditions.

In ena_remove() we have the following stack call:
ena_remove()
  unregister_netdev()
  ena_destroy_device()
netif_carrier_off()

Calling netif_carrier_off() causes linkwatch to try to handle the
link change event on the already unregistered netdev, which leads
to a read from an unreadable memory address.

** Affects: linux (Ubuntu)
 Importance: Undecided
 Assignee: Kamal Mostafa (kamalmostafa)
 Status: 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/1802341

Title:
  crash in ENA driver on removing an interface

Status in linux package in Ubuntu:
  In Progress

Bug description:
  Bug present in ENA since driver version 1.6; manifests as a crash only
  under some conditions.

  In ena_remove() we have the following stack call:
  ena_remove()
unregister_netdev()
ena_destroy_device()
  netif_carrier_off()
  
  Calling netif_carrier_off() causes linkwatch to try to handle the
  link change event on the already unregistered netdev, which leads
  to a read from an unreadable memory address.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1802341/+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 1801743] Re: Suspend fails in Kubuntu 18.04 but works fine in Kubuntu 17.10

2018-11-08 Thread Igors

Last entry in /var/log/kern.log for the incomplete shutdown seems to be

rfkill: input handler enabled

This is the last line before timings went to zeros last time, and it was
just 1 second before the line "Stopping system logging service" in the
syslog.

lspci -v output:
https://pastebin.com/S2yGLfAE

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

Title:
  Suspend fails in Kubuntu 18.04 but works fine in Kubuntu 17.10

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After upgrading to kubuntu 18.04 resuming from suspend fails in most
  cases on my laptop. When trying to resume the power LED is turned on,
  but the screen stays black and the system does not respond at all.
  Switching to another virtual terminal is not possible and closing the
  lid again does not show any effect. The hardware is a Dell Latitude
  e7440 with core i7 4600U and intel graphics only. The only way to
  change the status is a hard shut-down by long pressing the power
  button. The last message in kern.log is:

  PM: suspend entry (deep)

  The described problem is similar to bug #1774950. However, the latter
  is considered to be fixed with kernel 4.15.0-38 while my problem
  persists with this kernel.

  Output of 'sudo lspci -vnvn' is attached, the result of 'cat
  /proc/version_signature' is:

  Ubuntu 4.15.0-38.41-generic 4.15.18
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  graeser2116 F pulseaudio
   /dev/snd/controlC0:  graeser2116 F pulseaudio
  CurrentDesktop: KDE
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-precise-amd64-20130203-1
  DistroRelease: Ubuntu 18.04
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=none
  InstallationDate: Installed on 2014-03-20 (1690 days ago)
  InstallationMedia: Ubuntu 12.04 "Precise" - Build amd64 LIVE Binary 
20130203-13:50
  MachineType: Dell Inc. Latitude E7440
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-38-generic 
root=UUID=25e09413-4977-401f-a034-0465b444518b ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-38-generic N/A
   linux-backports-modules-4.15.0-38-generic  N/A
   linux-firmware 1.173.1
  Tags:  bionic
  Uname: Linux 4.15.0-38-generic x86_64
  UpgradeStatus: Upgraded to bionic on 2018-10-15 (20 days ago)
  UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 02/02/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A14
  dmi.board.name: 0WK2DM
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA14:bd02/02/2015:svnDellInc.:pnLatitudeE7440:pvr01:rvnDellInc.:rn0WK2DM:rvr:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E7440
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1801743/+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 1799451] Re: linux-azure: 4.18.0-1004.4 -proposed tracker

** Changed in: kernel-sru-workflow/automated-testing
   Status: Incomplete => Fix Released

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1799445
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   automated-testing: Testing FAILED
certification-testing: Testing in progress
regression-testing: Testing in progress
stakeholder-signoff: Waiting for signoff
verification-testing: Testing in progress

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

Title:
  linux-azure: 4.18.0-1004.4 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow stakeholder-signoff series:
  Confirmed
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-azure package in Ubuntu:
  Confirmed
Status in linux-azure source package in Cosmic:
  Confirmed

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1799445
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
certification-testing: Testing in progress
regression-testing: Testing in progress
stakeholder-signoff: Waiting for signoff
verification-testing: Testing in progress

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1799451/+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 1799452] Re: linux-gcp: 4.18.0-1003.4 -proposed tracker

2018-11-08 Thread Andy Whitcroft

** Also affects: kernel-sru-workflow/stakeholder-signoff
   Importance: Undecided
   Status: New

** Changed in: kernel-sru-workflow/stakeholder-signoff
   Status: New => In Progress

** Changed in: kernel-sru-workflow/stakeholder-signoff
 Assignee: (unassigned) => Andy Whitcroft (apw)

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

Title:
  linux-gcp: 4.18.0-1003.4 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-beta series:
  Invalid
Status in Kernel SRU Workflow snap-release-to-candidate series:
  Invalid
Status in Kernel SRU Workflow snap-release-to-edge series:
  Invalid
Status in Kernel SRU Workflow snap-release-to-stable series:
  Invalid
Status in Kernel SRU Workflow stakeholder-signoff series:
  In Progress
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-gcp package in Ubuntu:
  Confirmed
Status in linux-gcp source package in Cosmic:
  Confirmed

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1799445
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
certification-testing: Testing in progress
regression-testing: Testing in progress
verification-testing: Testing in progress

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1799452/+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 1748565] Re: Kernel regularly logs: Bluetooth: hci0: last event is not cmd complete (0x0f)

2018-11-08 Thread Jason Croy

I've just installed Blueberry on Arch Linux 4.18.17.a-1-hardened and I get this 
bug as well. 
dmesg shows several 'not cmd complete' followed by an input remap. I have only 
ever seen the message pop up when the Blueberry device manager is open. Last 
format (read: last week) I used Blueman and did not have this issue so the 
fault may lie in Blueberry. Skipping still occurs without Blueberry open but no 
errors are logged. 

...
[ 1544.104905] Bluetooth: hci0: last event is not cmd complete (0x0f)
[ 1555.393338] input: 48:D6:D5:BB:12:02 as /devices/virtual/input/input54
...
[ 1663.107882] Bluetooth: hci0: last event is not cmd complete (0x0f)
[ 1668.694434] input: 48:D6:D5:BB:12:02 as /devices/virtual/input/input55
... etc

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

Title:
  Kernel regularly logs: Bluetooth: hci0: last event is not cmd complete
  (0x0f)

Status in Linux:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in Fedora:
  New

Bug description:
  Hello,

  dmesg:
  [ 3363.056494] Bluetooth: hci0: last event is not cmd complete (0x0f)

  Regards,
  --
  Cristian

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-9-generic 4.15.0-9.10
  ProcVersionSignature: Ubuntu 4.15.0-9.10-generic 4.15.2
  Uname: Linux 4.15.0-9-generic x86_64
  ApportVersion: 2.20.8-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  caravena   1811 F pulseaudio
  CurrentDesktop: ubuntu-communitheme:ubuntu:GNOME
  Date: Fri Feb  9 20:35:29 2018
  InstallationDate: Installed on 2017-10-13 (119 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-9-generic 
root=UUID=707d0f89-4b1d-4432-9d50-6058dc4c1ee9 ro rootflags=subvol=@ quiet 
splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-9-generic N/A
   linux-backports-modules-4.15.0-9-generic  N/A
   linux-firmware1.170
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/15/2013
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: P14AAJ
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: SAMSUNG_NP1234567890
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: FAB1
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvrP14AAJ:bd04/15/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1:
  dmi.product.family: ChiefRiver System
  dmi.product.name: 530U3C/530U4C
  dmi.product.version: 0.1
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1748565/+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 1797990] Re: kdump fail due to an IRQ storm

2018-11-08 Thread Mauricio Faria de Oliveira

** Description changed:

  [Impact]
  
   * A kexec/crash kernel might get stuck and fail to boot
     (for crash kernel, kdump fails to collect a crashdump)
     if a PCI device is buggy/stuck/looping and triggers a
     continuous flood of MSI(X) interrupts (that the kernel
     does not yet know about).
  
   * This fix allowed to obtain crashdumps when debugging a
     heavy-load scenario, in which a (heavy-loaded) network
     adapter wouldn't stop triggering MSI-X interrupts ever
     after panic()->kdump kicked in.
  
   * This fix disables MSI(X) in all PCI devices on early
     boot (this is OK as it's (re-)enabled normally later)
     with a kernel cmdline parameter (disabled by default).
  
  [Test Case]
  
   * A synthetic test-case is not yet available, however,
     this particular system/workload triggered the problem
     consistently, and it was used for development/testing.
  
   * We'll update this bug once a synthetic test-case is
     available; we're working on patching QEMU for this.
  
-  * $ dmesg | grep 'Clearing MSI'
-[0.00] Clearing MSI/MSI-X enable bits early in boot (quirk)
+  * $ cat /proc/cmdline
+<...> pci=clearmsi
  
-  * The comparison of 'dmesg -t | sort' has been reviewed
-between option disabled/enabled on boot & kexec modes,
-and only expected differences found (MHz, PIDs, MIPS).
+$ dmesg | grep 'Clearing MSI'
+    [0.00] Clearing MSI/MSI-X enable bits early in boot (quirk)
+ 
+  * The comparison of 'dmesg -t | sort' has been reviewed
+    between option disabled/enabled on boot & kexec modes,
+    and only expected differences found (MHz, PIDs, MIPS).
  
  [Regression Potential]
  
   * The potential area for regressions is early boot,
     particularly effects of applying quirks during PCI
     bus scan, which is changed/broader w/ these patches.
  
   * However, all quirks are applied based on PCI ID
     matching, so would only apply if actually targeting
     a new device.
  
   * Moreover, the new quirk is only applied based on
     a kernel cmdline parameter that is disabled by
     default, which constraints even more when this
     is actually in effect.
  
  [Other Info]
  
   * The patch series is still under review/discussion
     upstream, but it's relatively important for Ubuntu
     users at this point, and after internal discussions
     we decided to submit it for SRU.
  
   * These are links to the linux-pci archive with the
     patches [1, 2, 3]
  
     [1] [PATCH 1/3] x86/quirks: Scan all busses for early PCI quirks
     
https://lore.kernel.org/linux-pci/20181018183721.27467-1-gpicc...@canonical.com/
  
     [2] [PATCH 2/3] x86/PCI: Export find_cap() to be used in early PCI code
     
https://lore.kernel.org/linux-pci/20181018183721.27467-2-gpicc...@canonical.com/
  
     [3] [PATCH 3/3] x86/quirks: Add parameter to clear MSIs early on boot
     
https://lore.kernel.org/linux-pci/20181018183721.27467-3-gpicc...@canonical.com/
  
  [Original Description]
  
  We have reports of a kdump failure in Ubuntu (in x86 machine) that was
  narrowed down to a MSI irq storm coming from a PCI network device.
  
  The bug manifests as a lack of progress in the boot process of the kdump
  kernel, and a storm of kernel messages like:
  
  [...]
  [  342.265294] do_IRQ: 0.155 No irq handler for vector
  [  342.266916] do_IRQ: 0.155 No irq handler for vector
  [  347.258422] do_IRQ: 14053260 callbacks suppressed
  [...]
  
  The root cause of the issue is that the kdump kernel kexec process does
  not ensure PCI devices are reset and/or MSI capabilities are disabled,
  so a PCI device could produce a huge amount of PCI irqs which would take
  all the processing time for the CPU (specially since we restrict the
  kdump kernel to use one single CPU only).
  
  This was tested using upstream kernel version 4.18, and the problem 
reproduces.
  In the specific test scenario, the PCI NIC was an "Intel 82599ES 10-Gigabit 
[8086:10fb]" that was used in SR-IOV PCI passthrough mode (vfio_pci), under 
high load on the guest.

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

Title:
  kdump fail due to an IRQ storm

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Trusty:
  Confirmed
Status in linux source package in Xenial:
  Confirmed
Status in linux source package in Bionic:
  Confirmed
Status in linux source package in Cosmic:
  Confirmed

Bug description:
  [Impact]

   * A kexec/crash kernel might get stuck and fail to boot
     (for crash kernel, kdump fails to collect a crashdump)
     if a PCI device is buggy/stuck/looping and triggers a
     continuous flood of MSI(X) interrupts (that the kernel
     does not yet know about).

   * This fix allowed to obtain crashdumps when debugging a
     heavy-load scenario, in which a (heavy-loaded) network
     adapter wouldn't stop

[Kernel-packages] [Bug 1795292] Re: ELAN469D touch pad not working

2018-11-08 Thread Kenji

Indeed I tried as well, did not work either. I may make an account and
ask the user which kernel version they used. Also seeing they keyboard
issue, very strange. And my wifi says "disabled by button/airplane mode
on" but there is no button the laptop, and my BIOS has wifi "enabled",
so not sure why that doesn't work either.

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

Title:
  ELAN469D touch pad not working

Status in Linux:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I installed Bionic Beaver and now upgraded to Cosmic Cuttlefish on
  this Lenovo Ideapad 330S-15ARR laptop.  The touch pad doesn't work in
  either.

  Some possibly relevant info from dmesg:
  i2c_hid i2c-ELAN469D:00: i2c-ELAN469D:00 supply vdd not found, using dummy 
regulator
  i2c_designware AMDI0010:01: controller timed out

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.18.0-7-generic 4.18.0-7.8
  ProcVersionSignature: Ubuntu 4.18.0-7.8-generic 4.18.5
  Uname: Linux 4.18.0-7-generic x86_64
  ApportVersion: 2.20.10-0ubuntu11
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  xorbit 2086 F pulseaudio
   /dev/snd/pcmC1D0p:   xorbit 2086 F...m pulseaudio
   /dev/snd/controlC0:  xorbit 2086 F pulseaudio
  CurrentDesktop: GNOME
  Date: Sun Sep 30 23:14:26 2018
  InstallationDate: Installed on 2018-09-20 (10 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: LENOVO 81FB
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-7-generic 
root=UUID=4d91f09e-6122-4dd4-81fc-482465f8f0e7 ro noapic processor.max_cstate=1 
rcu_nocbs=0-7 pcie_aspm=off pci=noaer quiet splash vt.handoff=1 
elan_i2c.dyndbg=+p
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-7-generic N/A
   linux-backports-modules-4.18.0-7-generic  N/A
   linux-firmware1.175
  SourcePackage: linux
  UpgradeStatus: Upgraded to cosmic on 2018-09-30 (0 days ago)
  dmi.bios.date: 06/08/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 7WCN22WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709WIN
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad 330S-15ARR
  dmi.modalias: 
dmi:bvnLENOVO:bvr7WCN22WW:bd06/08/2018:svnLENOVO:pn81FB:pvrLenovoideapad330S-15ARR:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoideapad330S-15ARR:
  dmi.product.family: ideapad 330S-15ARR
  dmi.product.name: 81FB
  dmi.product.sku: LENOVO_MT_81FB_BU_idea_FM_ideapad 330S-15ARR
  dmi.product.version: Lenovo ideapad 330S-15ARR
  dmi.sys.vendor: LENOVO
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu11
  Architecture: amd64
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 18.10
  InstallationDate: Installed on 2018-09-20 (13 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Tags:  cosmic
  Uname: Linux 4.19.0-041900rc6-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: Upgraded to cosmic on 2018-09-30 (2 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1795292/+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 1801743] Re: Suspend fails in Kubuntu 18.04 but works fine in Kubuntu 17.10

2018-11-08 Thread Igors

Unfortunately, not for me. We have a bunch of (theoretically) identical
computers in a new classroom, and on one of them this issue is present.
Similarly as described by Carsten Gräser (graeser): last entry in
kern.log, running fan and no reaction to either keyboard or power
button, last message on screen being

A start job is running for Hold until boot process finishes up (21s / no
limit).

Only the power button is blinking, not steady, and with addition of
similar problems at the shutdown (NOT at the reboot, except for the long
delay). It seems that the system thinks from certain gauges that it is
suspended or powered down, but some part of it is not. Last message for
the failed shutdown is

reboot: Power down

and then everything stays as if there would be the classic message "It's
now safe to power off Your computer", with screen on and fan running.

To reinstate, installing the upstream kernel 4.19.1 did not help on this
issue. Some 30 PCs of identical hardware do not have this problem.

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

Title:
  Suspend fails in Kubuntu 18.04 but works fine in Kubuntu 17.10

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After upgrading to kubuntu 18.04 resuming from suspend fails in most
  cases on my laptop. When trying to resume the power LED is turned on,
  but the screen stays black and the system does not respond at all.
  Switching to another virtual terminal is not possible and closing the
  lid again does not show any effect. The hardware is a Dell Latitude
  e7440 with core i7 4600U and intel graphics only. The only way to
  change the status is a hard shut-down by long pressing the power
  button. The last message in kern.log is:

  PM: suspend entry (deep)

  The described problem is similar to bug #1774950. However, the latter
  is considered to be fixed with kernel 4.15.0-38 while my problem
  persists with this kernel.

  Output of 'sudo lspci -vnvn' is attached, the result of 'cat
  /proc/version_signature' is:

  Ubuntu 4.15.0-38.41-generic 4.15.18
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  graeser2116 F pulseaudio
   /dev/snd/controlC0:  graeser2116 F pulseaudio
  CurrentDesktop: KDE
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-precise-amd64-20130203-1
  DistroRelease: Ubuntu 18.04
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=none
  InstallationDate: Installed on 2014-03-20 (1690 days ago)
  InstallationMedia: Ubuntu 12.04 "Precise" - Build amd64 LIVE Binary 
20130203-13:50
  MachineType: Dell Inc. Latitude E7440
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-38-generic 
root=UUID=25e09413-4977-401f-a034-0465b444518b ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-38-generic N/A
   linux-backports-modules-4.15.0-38-generic  N/A
   linux-firmware 1.173.1
  Tags:  bionic
  Uname: Linux 4.15.0-38-generic x86_64
  UpgradeStatus: Upgraded to bionic on 2018-10-15 (20 days ago)
  UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 02/02/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A14
  dmi.board.name: 0WK2DM
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA14:bd02/02/2015:svnDellInc.:pnLatitudeE7440:pvr01:rvnDellInc.:rn0WK2DM:rvr:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E7440
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1801743/+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 1801349] Re: zpool create -f lxd /dev/vdb fails on cosmic (18.10) -- func27

2018-11-08 Thread Alex Kavanagh

Colin, sorry, no; it's the bug that 'found' the issue; it's basically
saying that we aren't enabling a particular gate test (i.e. it's staying
dev-) due to this bug.

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

Title:
  zpool create -f lxd /dev/vdb fails on cosmic (18.10) -- func27

Status in OpenStack LXD Charm:
  New
Status in linux package in Ubuntu:
  In Progress

Bug description:
  Test: tests/gate-basic-cosmic-rocky

  As part of the config, the lxd charm creates a pool device depending
  on the config.  The test config is:

  lxd_config = {
  'block-devices': '/dev/vdb',
  'ephemeral-unmount': '/mnt',
  'storage-type': 'zfs',
  'overwrite': True
  }

  The config drive is normally mounted on /mnt, and the lxd charm
  umounts it as part of the start up.  The /etc/fstab on the unit is:

  # cat /etc/fstab 
  LABEL=cloudimg-rootfs   /ext4   defaults0 0
  LABEL=UEFI  /boot/efi   vfatdefaults0 0
  /dev/vdb/mntauto
defaults,nofail,x-systemd.requires=cloud-init.service,comment=cloudconfig   
0   2
  /dev/vdcnoneswapsw,comment=cloudconfig  0   0

  
  However, even after umount-ing the /mnt off of /dev/vdb, the zpool create 
command still fails:

  # zpool create -f lxd /dev/vdb
  /dev/vdb is in use and contains a unknown filesystem.

  
  If the /etc/fstab is edited so that /dev/vdb is *never* mounted and then 
rebooted, then the zpool create command succeeds:

  # zpool list
  NAME   SIZE  ALLOC   FREE  EXPANDSZ   FRAGCAP  DEDUP  HEALTH  ALTROOT
  lxd   14.9G   106K  14.9G - 0% 0%  1.00x  ONLINE  -

  # zpool status lxd
pool: lxd
   state: ONLINE
scan: none requested
  config:

  NAMESTATE READ WRITE CKSUM
  lxd ONLINE   0 0 0
vdb   ONLINE   0 0 0

  errors: No known data errors

  Something odd is going on with cosmic (18.10) and the combination of
  lxd, zfs and the kernel

  lxd version: 3.6
  zfsutils-linux/cosmic,now 0.7.9-3ubuntu6
  Linux: 4.18.0-10-generic

To manage notifications about this bug go to:
https://bugs.launchpad.net/charm-lxd/+bug/1801349/+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 1791427] Re: Touchpad and/or trackpoint stop working after S3 suspend on Lenovo X1 Carbon 6th

2018-11-08 Thread AaronMa

Root cause should be broke communication via PS/2 bus.

Current touchpad with smbus support still needs PS/2 commands to confirm
the info and capabilities.

This bug had been reported to Lenovo, waiting for fw update to fix this
issue.

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

Title:
  Touchpad and/or trackpoint stop working after S3 suspend on Lenovo X1
  Carbon 6th

Status in linux package in Ubuntu:
  Triaged

Bug description:
  Ubuntu 18.04.1

  Terminology in case we use different terms:
  touchpad - just the rectangular touch-sensitive surface below the keyboard 
(xinput lists it as Synaptics TM3288-011)
  trackpoint - the red thingy built into the keyboard + 3 physical buttons 
below the keyboard (trackpoint and buttons are integrated together; listed in 
xinput as TPPS/2 Elan TrackPoint)

  On September 7th, 2018, Lenovo has issued a BIOS update (v1.30), which
  enables proper S3 deep sleep state - users no longer have to patch
  DSDT tables to get it. It can be enabled in the BIOS settings. In X1
  carbon 6th generation models that have NFC, when laptop wakes from
  suspend by opening the lid, in most cases both touchpad and trackpoint
  stop working completely. They are also no longer listed when running
  xinput command. Sometimes just one of them stops working, usually the
  trackpoint. In some rare cases it is possible to bring them back by
  using these commands:

  echo -n none > /sys/devices/platform/i8042/serio1/drvctl
  echo -n reconnect > /sys/devices/platform/i8042/serio1/drvctl
  rmmod psmouse
  modprobe psmouse

  These worked properly when waking up from S2Idle sleep state (had
  these in a script that runs after waking the machine from suspend),
  but with S3 deep sleep these rarely work and the only way to bring
  back touchpad and/or trackpoint is turning off the machine and turning
  it on (restart does not help).

  I could not find any pattern that would show when the input devices
  stop working or start working again using the commands mentioned
  above. It's completely random from my perspective.

  This is happening on the standard issue 4.15.0-33-generic kernel that
  shipped with my Ubuntu 18.04 (with updates), as well as with newer
  mainline kernels, such as the newest point versions of 4.17, 4.18 and
  4.19 RC2.

  This happens regardless of whether "blacklist i2c_i801" is commented
  out in /etc/modprobe.d/blacklist.conf or not. It happens regardless of
  whether "psmouse.synaptics_intertouch=1" is passed as grub parameter.
  Presence of TLP does not make it better, nor worse.

  It appears that non-NFC models are not affected. I know at least one
  Arch Linux user who has the exact same model, but without this issue.
  I'm using synaptics driver (no libinput installed), he uses libinput
  and doesn't have synaptics, if that information is of any use.
  Libinput does not seem to help.

  This forum thread also has more details from users who updated their
  BIOS to get S3 suspend: https://forums.lenovo.com/t5/Linux-
  Discussion/X1-Carbon-Gen-6-cannot-enter-deep-sleep-S3-state-aka-
  Suspend-to/td-p/3998182/page/27

  Another related thread:
  https://bbs.archlinux.org/viewtopic.php?id=236367

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-33-generic 4.15.0-33.36
  ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
  Uname: Linux 4.15.0-33-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   maciej 2651 F...m pulseaudio
   /dev/snd/controlC0:  maciej 2651 F pulseaudio
  CurrentDesktop: i3
  Date: Sat Sep  8 13:45:43 2018
  HibernationDevice: RESUME=UUID=3116dcb0-d91e-4b2a-8166-43b7a9a9d36e
  InstallationDate: Installed on 2018-07-21 (49 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 13d3:56b2 IMC Networks 
   Bus 001 Device 002: ID 04b4:0060 Cypress Semiconductor Corp. Wireless 
optical mouse
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 20KH006KPB
  ProcFB:
   0 EFI VGA
   1 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-33-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash psmouse.synaptics_intertouch=1 
vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-33-generic N/A
   linux-backports-modules-4.15.0-33-generic  N/A
   linux-firmware 1.173.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/31/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N23ET55W (1.30 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20KH006KPB
  dmi.board.vendor: LENOVO

[Kernel-packages] [Bug 1801349] Re: zpool create -f lxd /dev/vdb fails on cosmic (18.10) -- func27

2018-11-08 Thread Colin Ian King

Is the above commit a fix to this issue?

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

Title:
  zpool create -f lxd /dev/vdb fails on cosmic (18.10) -- func27

Status in OpenStack LXD Charm:
  New
Status in linux package in Ubuntu:
  In Progress

Bug description:
  Test: tests/gate-basic-cosmic-rocky

  As part of the config, the lxd charm creates a pool device depending
  on the config.  The test config is:

  lxd_config = {
  'block-devices': '/dev/vdb',
  'ephemeral-unmount': '/mnt',
  'storage-type': 'zfs',
  'overwrite': True
  }

  The config drive is normally mounted on /mnt, and the lxd charm
  umounts it as part of the start up.  The /etc/fstab on the unit is:

  # cat /etc/fstab 
  LABEL=cloudimg-rootfs   /ext4   defaults0 0
  LABEL=UEFI  /boot/efi   vfatdefaults0 0
  /dev/vdb/mntauto
defaults,nofail,x-systemd.requires=cloud-init.service,comment=cloudconfig   
0   2
  /dev/vdcnoneswapsw,comment=cloudconfig  0   0

  
  However, even after umount-ing the /mnt off of /dev/vdb, the zpool create 
command still fails:

  # zpool create -f lxd /dev/vdb
  /dev/vdb is in use and contains a unknown filesystem.

  
  If the /etc/fstab is edited so that /dev/vdb is *never* mounted and then 
rebooted, then the zpool create command succeeds:

  # zpool list
  NAME   SIZE  ALLOC   FREE  EXPANDSZ   FRAGCAP  DEDUP  HEALTH  ALTROOT
  lxd   14.9G   106K  14.9G - 0% 0%  1.00x  ONLINE  -

  # zpool status lxd
pool: lxd
   state: ONLINE
scan: none requested
  config:

  NAMESTATE READ WRITE CKSUM
  lxd ONLINE   0 0 0
vdb   ONLINE   0 0 0

  errors: No known data errors

  Something odd is going on with cosmic (18.10) and the combination of
  lxd, zfs and the kernel

  lxd version: 3.6
  zfsutils-linux/cosmic,now 0.7.9-3ubuntu6
  Linux: 4.18.0-10-generic

To manage notifications about this bug go to:
https://bugs.launchpad.net/charm-lxd/+bug/1801349/+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 1800859] Re: Fail to suspend properly in Ubuntu 18.10 (Also occurred in 18.04)

2018-11-08 Thread Tony Corbett

4 days of running the 4.13 kernel and every time I close the lid on this
laptop it's suspending and resuming without fail as it should.

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

Title:
  Fail to suspend properly in Ubuntu 18.10 (Also occurred in 18.04)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  This has all the hallmarks of Bug #1774950 excepting that no amount of
  kernel reversion seems to solve the problem.

  System sporadically works fine, but mostly fails to suspend properly
  according to /var/log/kern.log ...

  $ lsb_release -rd
  Description:  Ubuntu 18.10
  Release:  18.10

  $ cat /proc/version_signature 
  Ubuntu 4.18.0-10.11-generic 4.18.12

  $ lscpu
  Architecture:x86_64
  CPU op-mode(s):  32-bit, 64-bit
  Byte Order:  Little Endian
  CPU(s):  4
  On-line CPU(s) list: 0-3
  Thread(s) per core:  2
  Core(s) per socket:  2
  Socket(s):   1
  NUMA node(s):1
  Vendor ID:   AuthenticAMD
  CPU family:  21
  Model:   101
  Model name:  AMD A12-9700P RADEON R7, 10 COMPUTE CORES 4C+6G
  Stepping:1
  CPU MHz: 1582.715
  CPU max MHz: 2500.
  CPU min MHz: 1300.
  BogoMIPS:4990.76
  Virtualisation:  AMD-V
  L1d cache:   32K
  L1i cache:   96K
  L2 cache:1024K
  NUMA node0 CPU(s):   0-3
  Flags:   fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca 
cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb 
rdtscp lm constant_tsc rep_good acc_power nopl nonstop_tsc cpuid extd_apicid 
aperfmperf pni pclmulqdq monitor ssse3 fma cx16 sse4_1 sse4_2 movbe popcnt aes 
xsave avx f16c rdrand lahf_lm cmp_legacy svm extapic cr8_legacy abm sse4a 
misalignsse 3dnowprefetch osvw ibs xop skinit wdt lwp fma4 tce nodeid_msr tbm 
topoext perfctr_core perfctr_nb bpext ptsc mwaitx cpb hw_pstate ssbd vmmcall 
fsgsbase bmi1 avx2 smep bmi2 xsaveopt arat npt lbrv svm_lock nrip_save 
tsc_scale vmcb_clean flushbyasid decodeassists pausefilter pfthreshold avic 
v_vmsave_vmload vgif overflow_recov

  $ sudo lspci -vnvn 
  00:00.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 15h 
(Models 60h-6fh) Processor Root Complex [1022:1576]
Subsystem: Hewlett-Packard Company Family 15h (Models 60h-6fh) 
Processor Root Complex [103c:81f9]
Control: I/O- Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- 
Capabilities: [64] MSI: Enable+ Count=1/4 Maskable- 64bit+
Address: fee08004  Data: 4021
Capabilities: [74] HyperTransport: MSI Mapping Enable+ Fixed+

  00:01.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. 
[AMD/ATI] Wani [Radeon R5/R6/R7 Graphics] [1002:9874] (rev c9) (prog-if 00 [VGA 
controller])
Subsystem: Hewlett-Packard Company Wani [Radeon R5/R6/R7 Graphics] 
[103c:81f9]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Capabilities: [50] Power Management version 3
Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA 
PME(D0-,D1+,D2+,D3hot+,D3cold-)
Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [58] Express (v2) Root Complex Integrated Endpoint, MSI 00
DevCap: MaxPayload 256 bytes, PhantFunc 0
ExtTag+ RBE+
DevCtl: Report errors: Correctable- Non-Fatal- Fatal- 
Unsupported-
RlxdOrd+ ExtTag+ PhantFunc- AuxPwr- NoSnoop+
MaxPayload 128 bytes, MaxReadReq 512 bytes
DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr- 
TransPend-
DevCap2: Completion Timeout: Not Supported, TimeoutDis-, LTR-, 
OBFF Not Supported
DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, LTR-, 
OBFF Disabled
Capabilities: [a0] MSI: Enable+ Count=1/1 Maskable- 64bit+
Address: fee0  Data: 
Capabilities: [100 v1] Vendor Specific Information: ID=0001 Rev=1 
Len=010 
Capabilities: [270 v1] #19
Capabilities: [2b0 v1] Address Translation Service (ATS)
ATSCap: Invalidate Queue Depth: 00
ATSCtl: Enable+, Smallest Translation Unit: 00
Capabilities: [2c0 v1] Page Request Interface (PRI)
PRICtl: Enable+ Reset-
PRISta: RF- UPRGI- Stopped+
Page Request Capacity: 0020, Page Request Allocation: 
0020
Capabilities: [2d0 v1] Process Address Space ID (PASID)
PASIDCap:

[Kernel-packages] [Bug 1787405] Comment bridged from LTC Bugzilla

2018-11-08 Thread bugproxy

--- Comment From aekro...@us.ibm.com 2018-11-08 10:35 EDT---
I successfully tested the guest support on backport for ap on the 18.04 ubuntu 
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/1787405

Title:
  [19.04 FEAT] Guest-dedicated Crypto Adapters

Status in Ubuntu on IBM z Systems:
  Triaged
Status in libvirt package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Triaged
Status in qemu package in Ubuntu:
  Incomplete

Bug description:
  == SRU Justification ==

  (Kernel SRU)

  Allow kvm to dedicate crypto adapters (and domains) as passthrough devices to 
a KVM guest such that the hypervisor cannot observe the communication of the 
guest with the device.
  (Since all kernel patches/commits are from kernel 4.19, they will 
automagically land in 'Disco'.)

  == Fix ==

  9ea5972 ("KVM: s390: vsie: simulate VCPU SIE entry/exit")
  3194cdb ("KVM: s390: introduce and use KVM_REQ_VSIE_RESTART")
  e585b24 ("KVM: s390: refactor crypto initialization")
  1fde573 ("s390: vfio-ap: base implementation of VFIO AP device driver")
  65f0671 ("s390: vfio-ap: register matrix device with VFIO mdev framework")
  96d152b ("s390: vfio-ap: sysfs interfaces to configure adapters")
  3211da0 ("s390: vfio-ap: sysfs interfaces to configure domains")
  3b1eab7 ("s390: vfio-ap: sysfs interfaces to configure control domains")
  81b2b4b ("s390: vfio-ap: sysfs interface to view matrix mdev matrix")
  4210459 ("KVM: s390: interface to clear CRYCB masks")
  258287c ("s390: vfio-ap: implement mediated device open callback")
  e06670c ("s390: vfio-ap: implement VFIO_DEVICE_GET_INFO ioctl")
  46a7263 ("s390: vfio-ap: zeroize the AP queues")
  cd8a377 ("s390: vfio-ap: implement VFIO_DEVICE_RESET ioctl")
  6cc571b ("KVM: s390: Clear Crypto Control Block when using vSIE")
  d6f6959 ("KVM: s390: vsie: Do the CRYCB validation first")
  3af84de ("KVM: s390: vsie: Make use of CRYCB FORMAT2 clear")
  56019f9 ("KVM: s390: vsie: Allow CRYCB FORMAT-2")
  19fd83a ("KVM: s390: vsie: allow CRYCB FORMAT-1")
  6ee7409 ("KVM: s390: vsie: allow CRYCB FORMAT-0")
  c9ba8c2 ("KVM: s390: vsie: allow guest FORMAT-0 CRYCB on host FORMAT-1")
  6b79de4 ("KVM: s390: vsie: allow guest FORMAT-1 CRYCB on host FORMAT-2")
  9ee71f2 ("KVM: s390: vsie: allow guest FORMAT-0 CRYCB on host FORMAT-2")
  37940fb ("KVM: s390: device attrs to enable/disable AP interpretation")
  112c24d ("KVM: s390: CPU model support for AP virtualization")
  492a6be ("s390: doc: detailed specifications for AP virtualization")

  <-- till here in 'kvm/next'
  (https://git.kernel.org/pub/scm/virt/kvm/kvm.git/) -->

  8e41bd5 ("KVM: s390: fix locking for crypto setting error path")
  0e237e4 ("KVM: s390: Tracing APCB changes")
  76c7829 ("s390: vfio-ap: setup APCB mask using KVM dedicated function")

  <-- till here in 'kvms390/next'
  (https://git.kernel.org/pub/scm/linux/kernel/git/kvms390/linux.git/)
  -->

  <-- In addition to that some prereqs for the 'ap/crypto' driver are
  necessary -->

  ea3c418 ("s390/zcrypt: Add ZAPQ inline function.")
  df80c03 ("s390/zcrypt: Review inline assembler constraints.")
  f1b0a43 ("s390/zcrypt: Integrate ap_asm.h into include/asm/ap.h.")
  2395103 ("s390/zcrypt: fix ap_instructions_available() returncodes")
  7e0bdbe ("s390/zcrypt: AP bus support for alternate driver(s)")
  3d8f60d3 ("s390/zcrypt: hex string mask improvements for apmask and aqmask.")
  fa108f9 ("s390/zcrypt: remove VLA usage from the AP bus")

  <--
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1787405/comments/12
  -->

  == PATCH ==

  Above git commits are all from 4.19.
  The git commands for 4.18 would be:

  $ git cherry-pick 

  (112c24d "KVM: s390: CPU model support for AP virtualization" may have
  a trivial merge conflict with the etoken patch)

  $ git cherry-pick 

  $ git cherry-pick 

  == Regression Potential ==

  Low to mid:

  - mid because in summary there are a lot of changes, but low
  - they are all limited to the s390x architecture
  - and again limited to KVM/s390x, vfio-ap and the zcrypt (aka ap) driver
  - Test kernel was built for testting.

  == Test Case ==

  Setup a system for KVM use on an s390x LPAR that has CryptoExpress (aka 
crypto-) adapters installed.
  Verify that the AP bus created a sysfs device for each APQN, like:
  /sys/devices/ap/card04/04.0006
  /sys/devices/ap/card04/04.0047
  /sys/devices/ap/card0a/0a.0006
  /sys/devices/ap/card0a/0a.0047
  Verify the APQN range via the following two sysfs files:
  /sys/bus/ap/apmask
  /sys/bus/ap/aqmask
  Configure and start a guest.
  More details see: 492a6be ("s390: doc: detailed specifications for AP 
virtualization")
  But for that an updated qemu and libvirt should be in place - that's 
addressed in LP1787405, too.
  (So this is only the kernel part of that ticket.)
  __

  Description:
  Allow kvm to dedicate crypto adapters (and domains) as

[Kernel-packages] [Bug 1773165] Re: openvswitch-datapath-dkms kernel module is not getting loaded

2018-11-08 Thread Andrei Andone

Hello everybody,

The problem is that we have added functionality to the kernel module.
Since dkms now comes with the kernel itself, how can we add our functionality 
to it?

Is there a way to gracefully replace the openvswitch kmod with our own,
also, in order to build the kernel module against the kernel we would
need to at least patch the existing openvswitch.h file that comes with
the kernel-headers. Is that an option?

Regards,
Andrei

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

Title:
  openvswitch-datapath-dkms kernel module is not getting loaded

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

Bug description:
  Distributor ID: Ubuntu
  Description: Ubuntu 16.04.4 LTS
  Release: 16.04
  Codename: xenial

  Kernel version: 4.4.0-127-generic
  OVS version: 2.7.0

  
  # Issue description
  openvswitch-datapath-dkms kernelmodule is not getting loaded

  
  # Error from dmesg
  [10863.380564] openvswitch: module verification failed: signature and/or 
required key missing - tainting kernel
  [10863.381804] openvswitch: exports duplicate symbol dst_cache_destroy (owned 
by kernel)
  [10863.517173] openvswitch: exports duplicate symbol dst_cache_destroy (owned 
by kernel)
  [10878.094250] openvswitch: exports duplicate symbol dst_cache_destroy (owned 
by kernel)

  
  #Error from syslog
  May 24 08:37:06 dev65 kernel: [76508.361496] openvswitch: exports duplicate 
symbol dst_cache_destroy (owned by kernel)
  May 24 08:37:06 dev65 openvswitch-switch[18336]: modprobe: ERROR: could not 
insert 'openvswitch': Exec format error
  May 24 08:37:06 dev65 openvswitch-switch[18336]:  * Inserting openvswitch 
module

  
  #installation logs:
  Selecting previously unselected package openvswitch-datapath-dkms.
  (Reading database ... 84707 files and directories currently installed.)
  Preparing to unpack openvswitch-datapath-dkms_2.7.0-1_all.deb ...
  Unpacking openvswitch-datapath-dkms (2.7.0-1) ...
  Setting up openvswitch-datapath-dkms (2.7.0-1) ...

  Creating symlink /var/lib/dkms/openvswitch/2.7.0/source ->
   /usr/src/openvswitch-2.7.0

  DKMS: add completed.

  Kernel preparation unnecessary for this kernel.  Skipping...

  Building module:
  cleaning build area(bad exit status: 2)
  ./configure --with-linux='/lib/modules/4.4.0-127-generic/build' && make -C 
datapath/linux..
  cleaning build area(bad exit status: 2)

  DKMS: build completed.

  openvswitch:
  Running module version sanity check.
   - Original module
   - Installation
 - Installing to /lib/modules/4.4.0-127-generic/updates/dkms/

  vport-geneve.ko:
  Running module version sanity check.
   - Original module
   - Installation
 - Installing to /lib/modules/4.4.0-127-generic/updates/dkms/

  vport-gre.ko:
  Running module version sanity check.
   - Original module
   - Installation
 - Installing to /lib/modules/4.4.0-127-generic/updates/dkms/

  vport-lisp.ko:
  Running module version sanity check.
   - Original module
   - Installation
 - Installing to /lib/modules/4.4.0-127-generic/updates/dkms/

  vport-stt.ko:
  Running module version sanity check.
   - Original module
   - Installation
 - Installing to /lib/modules/4.4.0-127-generic/updates/dkms/

  vport-vxlan.ko:
  Running module version sanity check.
   - Original module
   - Installation
 - Installing to /lib/modules/4.4.0-127-generic/updates/dkms/

  depmod

  DKMS: install completed.

  
  #Dpkg status
  dpkg -l | grep openvswitch
  ii  openvswitch-common   2.7.0-1  
  amd64Open vSwitch common components
  ii  openvswitch-datapath-dkms2.7.0-1  
  all  Open vSwitch datapath module source - DKMS version
  ii  openvswitch-switch   2.7.0-1  
  amd64Open vSwitch switch implementations
  ii  python-openvswitch   2.6.1-0ubuntu5.2~cloud0  
  all  Python bindings for Open vSwitch

  #lsmod status
  No modules are listing for openvswitch-datapath-dkms

  #modprobe error
  modprobe openvswitch
  modprobe: ERROR: could not insert 'openvswitch': Exec format error
  --- 
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.4.0-127-generic.
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20.1-0ubuntu2.17
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', 
'/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  Card0.Amixer.info: Error: [Errno 2] No such file or directory
  Card0.Amixer.values: Error: [Errno 2] No such file

[Kernel-packages] [Bug 1797367] Re: Ubuntu 18.04.1 - [s390x] Kernel panic while stressing network bonding

** Changed in: linux (Ubuntu Bionic)
   Status: In Progress => Fix Committed

** Changed in: linux (Ubuntu Cosmic)
   Status: In Progress => Fix Committed

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

Title:
  Ubuntu 18.04.1 - [s390x] Kernel panic while stressing network bonding

Status in Ubuntu on IBM z Systems:
  In Progress
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Bionic:
  Fix Committed
Status in linux source package in Cosmic:
  Fix Committed

Bug description:
  == SRU Justification ==

  While running a series of stress tests for network on a bond device on Ubuntu 
18.04.1 with kernel 4.15.0-36.39,
  kernel panic is observed (btw. also on non-bond devices).
  This looks like a race between disabling a qeth device and accessing debugfs.
  This is critical and leads repeatedly to a crash (sooner or later).

  == Fix ==

  e19e5be8b4ca ("s390/qeth: sanitize strings in debug messages")

  pre-reqs:
  750b162 ("s390/qeth: reduce hard-coded access to ccw channels")
  d857e11 ("s390/qeth: remove outdated portname debug msg")
  9d0a58f ("s390/qeth: avoid using is_multicast_ether_addr_64bits on (u8 *)[6]")
  8174aa8 ("s390/qeth: consolidate qeth MAC address helpers")
  4641b02 ("s390/qeth: don't keep track of MAC address's cast type")

  == Regression Potential ==

  Low, because:

  - limited to s390x
  - and again limited to qeth driver
  - patches a problem identified during testing
  - fix was tested by IBM before submitted

  == Test Case ==

  run:
 #!/bin/bash
 var=0
 while :
 do
  var=$((var + 1))
  echo "DBG count is $var"
  mkdir /tmp/DBGINFO
  dbginfo.sh -d /tmp/DBGINFO
  rm -rf /tmp/DBGINFO*
  echo "chzdev now is $var"
  chzdev -e 
  chzdev -d 
 done
  and in avg. in less than 20 cycles a crash happens (usually < 10).

  __

  == Comment: #0 - Athira Rajeev
  ---Problem Description---
  While running a series of stress tests for network bonding on UBUNTU 18.04.1 
with kernel 4.15.0-36.39, kernel panic is observed.
  There are two instance of panic experienced with the same test procedures one 
of which indicates to be a kernel BUG.

  Contact Information = Athira Rajeev , Waiki
  Wright < wa...@us.ibm.com >

  ---uname output---
  #39-Ubuntu SMP Mon Sep 24 16:13:24 UTC 2018 4.15.0-36.39

  Machine Type = This issue is observed on z13 system
   ---Debugger---
  A debugger was configured,

  ---Steps to Reproduce---
  This happens while running stress tests for network bonding. kernel memory 
exposure attempt is detected and the BUG() is called from the code snippet: 
mm/usercopy.c:72
  dump was configured and crash dump is available.
  Results of few crash commands like bt, log are added in Attachment

  Relevant part of dmesg pointing to kernel BUG

  <<>>
  [14746.977364] kernel BUG at 
/build/linux-PABIrW/linux-4.15.0/mm/usercopy.c:72!
  [14746.977377] illegal operation: 0001 ilc:1 [#1] SMP
  [14746.977378] Modules linked in: macsec vsock_diag vsock sctp_diag sctp 
dccp_diag dccp tcp_diag udp_diag raw_diag inet_diag unix_diag af_packet_diag 
netlink_diag bonding binfmt_misc qeth_l3 8021q garp mrp stp llc xt_tcpudp 
qeth_l2 nf_conntrack_ipv6 nf_defrag_ipv6 scsi_dh_rdac scsi_dh_emc scsi_dh_alua 
s390_trng ghash_s390 prng sha512_s390 sha256_s390 sha1_s390 sha_common chsc_sch 
eadm_sch nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack libcrc32c 
crc32_vx_s390 qeth ccwgroup ip6table_filter ip6_tables vfio_ccw vfio_mdev mdev 
vfio_iommu_type1 vfio iptable_filter sch_fq_codel ip_tables x_tables aes_s390 
des_s390 des_generic dm_crypt dm_service_time dm_multipath zfcp 
scsi_transport_fc qdio dasd_eckd_mod dasd_mod btrfs xor zstd_compress raid6_pq 
zlib_deflate
  [14746.977401] CPU: 1 PID: 20905 Comm: dump2tar Tainted: G   OE
4.15.0-36-generic #39-Ubuntu
  [14746.977403] Hardware name: IBM 3906 M02 757 (LPAR)
  [14746.977404] Krnl PSW : 0f2d230d 6abe14d5 
(__check_object_size+0x15a/0x1e0)
  [14746.977408]R:0 T:1 IO:1 EX:1 Key:0 M:1 W:0 P:0 AS:3 CC:2 PM:0 
RI:0 EA:3
  [14746.977410] Krnl GPRS: 0002 00e95334 0064 
0001e6518828
  [14746.977412]0037cc8e  00a9577c 

  [14746.977413]647b 0001d8c120a8 0001 
8088
  [14746.977433]0001d8c0a020 0090da38 0037cc8e 
00016fdfbcd0
  [14746.977440] Krnl Code: 0037cc82: c0200038ef69larl
%r2,a9ab54
    0037cc88: c0e5fff32838brasl   
%r14,1e1cf8
   #0037cc8e: a7f40001brc 
15,37cc90
   >0037cc92: e330d0080004lg  
%r3,8(%r13)

[Kernel-packages] [Bug 1797367] Re: Ubuntu 18.04.1 - [s390x] Kernel panic while stressing network bonding

** Changed in: linux (Ubuntu Cosmic)
   Importance: Undecided => High

** Changed in: linux (Ubuntu Cosmic)
   Status: New => 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/1797367

Title:
  Ubuntu 18.04.1 - [s390x] Kernel panic while stressing network bonding

Status in Ubuntu on IBM z Systems:
  In Progress
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Bionic:
  Fix Committed
Status in linux source package in Cosmic:
  Fix Committed

Bug description:
  == SRU Justification ==

  While running a series of stress tests for network on a bond device on Ubuntu 
18.04.1 with kernel 4.15.0-36.39,
  kernel panic is observed (btw. also on non-bond devices).
  This looks like a race between disabling a qeth device and accessing debugfs.
  This is critical and leads repeatedly to a crash (sooner or later).

  == Fix ==

  e19e5be8b4ca ("s390/qeth: sanitize strings in debug messages")

  pre-reqs:
  750b162 ("s390/qeth: reduce hard-coded access to ccw channels")
  d857e11 ("s390/qeth: remove outdated portname debug msg")
  9d0a58f ("s390/qeth: avoid using is_multicast_ether_addr_64bits on (u8 *)[6]")
  8174aa8 ("s390/qeth: consolidate qeth MAC address helpers")
  4641b02 ("s390/qeth: don't keep track of MAC address's cast type")

  == Regression Potential ==

  Low, because:

  - limited to s390x
  - and again limited to qeth driver
  - patches a problem identified during testing
  - fix was tested by IBM before submitted

  == Test Case ==

  run:
 #!/bin/bash
 var=0
 while :
 do
  var=$((var + 1))
  echo "DBG count is $var"
  mkdir /tmp/DBGINFO
  dbginfo.sh -d /tmp/DBGINFO
  rm -rf /tmp/DBGINFO*
  echo "chzdev now is $var"
  chzdev -e 
  chzdev -d 
 done
  and in avg. in less than 20 cycles a crash happens (usually < 10).

  __

  == Comment: #0 - Athira Rajeev
  ---Problem Description---
  While running a series of stress tests for network bonding on UBUNTU 18.04.1 
with kernel 4.15.0-36.39, kernel panic is observed.
  There are two instance of panic experienced with the same test procedures one 
of which indicates to be a kernel BUG.

  Contact Information = Athira Rajeev , Waiki
  Wright < wa...@us.ibm.com >

  ---uname output---
  #39-Ubuntu SMP Mon Sep 24 16:13:24 UTC 2018 4.15.0-36.39

  Machine Type = This issue is observed on z13 system
   ---Debugger---
  A debugger was configured,

  ---Steps to Reproduce---
  This happens while running stress tests for network bonding. kernel memory 
exposure attempt is detected and the BUG() is called from the code snippet: 
mm/usercopy.c:72
  dump was configured and crash dump is available.
  Results of few crash commands like bt, log are added in Attachment

  Relevant part of dmesg pointing to kernel BUG

  <<>>
  [14746.977364] kernel BUG at 
/build/linux-PABIrW/linux-4.15.0/mm/usercopy.c:72!
  [14746.977377] illegal operation: 0001 ilc:1 [#1] SMP
  [14746.977378] Modules linked in: macsec vsock_diag vsock sctp_diag sctp 
dccp_diag dccp tcp_diag udp_diag raw_diag inet_diag unix_diag af_packet_diag 
netlink_diag bonding binfmt_misc qeth_l3 8021q garp mrp stp llc xt_tcpudp 
qeth_l2 nf_conntrack_ipv6 nf_defrag_ipv6 scsi_dh_rdac scsi_dh_emc scsi_dh_alua 
s390_trng ghash_s390 prng sha512_s390 sha256_s390 sha1_s390 sha_common chsc_sch 
eadm_sch nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack libcrc32c 
crc32_vx_s390 qeth ccwgroup ip6table_filter ip6_tables vfio_ccw vfio_mdev mdev 
vfio_iommu_type1 vfio iptable_filter sch_fq_codel ip_tables x_tables aes_s390 
des_s390 des_generic dm_crypt dm_service_time dm_multipath zfcp 
scsi_transport_fc qdio dasd_eckd_mod dasd_mod btrfs xor zstd_compress raid6_pq 
zlib_deflate
  [14746.977401] CPU: 1 PID: 20905 Comm: dump2tar Tainted: G   OE
4.15.0-36-generic #39-Ubuntu
  [14746.977403] Hardware name: IBM 3906 M02 757 (LPAR)
  [14746.977404] Krnl PSW : 0f2d230d 6abe14d5 
(__check_object_size+0x15a/0x1e0)
  [14746.977408]R:0 T:1 IO:1 EX:1 Key:0 M:1 W:0 P:0 AS:3 CC:2 PM:0 
RI:0 EA:3
  [14746.977410] Krnl GPRS: 0002 00e95334 0064 
0001e6518828
  [14746.977412]0037cc8e  00a9577c 

  [14746.977413]647b 0001d8c120a8 0001 
8088
  [14746.977433]0001d8c0a020 0090da38 0037cc8e 
00016fdfbcd0
  [14746.977440] Krnl Code: 0037cc82: c0200038ef69larl
%r2,a9ab54
    0037cc88: c0e5fff32838brasl   
%r14,1e1cf8
   #0037cc8e: a7f40001brc 
15,37cc90
   >0037cc92: e330d0080004lg  
%r3,8(%r13)

[Kernel-packages] [Bug 1802283] Re: system freezes

2018-11-08 Thread Cristian Aravena Romero

Unfortunately, we cannot work on this bug because your description
didn't include enough information. You may find it helpful to read "How
to report bugs effectively"
http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful
if you would then provide a more complete description of the problem.

We have instructions on debugging some types of problems at
http://wiki.ubuntu.com/DebuggingProcedures.

At a minimum, we need:
1. The specific steps or actions you took that caused you to encounter the 
problem.
2. The behavior you expected. 
3. The behavior you actually encountered (in as much detail as possible).

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

Title:
  system freezes

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  My system freezes once every second day or so.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.18.0-10-generic 4.18.0-10.11
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  Uname: Linux 4.18.0-10-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  jnns   2519 F pulseaudio
   /dev/snd/controlC0:  jnns   2519 F pulseaudio
  CurrentDesktop: GNOME
  Date: Thu Nov  8 12:07:32 2018
  HibernationDevice: RESUME=UUID=18edd09d-0a58-4464-accb-11ff57fc4327
  InstallationDate: Installed on 2018-08-05 (95 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: LENOVO 20KGS5DU00
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/usr/bin/fish
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-10-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash mem_sleep_default=deep 
vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-10-generic N/A
   linux-backports-modules-4.18.0-10-generic  N/A
   linux-firmware 1.175
  SourcePackage: linux
  UpgradeStatus: Upgraded to cosmic on 2018-10-10 (29 days ago)
  dmi.bios.date: 09/17/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N23ET56W (1.31 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20KGS5DU00
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN23ET56W(1.31):bd09/17/2018:svnLENOVO:pn20KGS5DU00:pvrThinkPadX1Carbon6th:rvnLENOVO:rn20KGS5DU00:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Carbon 6th
  dmi.product.name: 20KGS5DU00
  dmi.product.sku: LENOVO_MT_20KG_BU_Think_FM_ThinkPad X1 Carbon 6th
  dmi.product.version: ThinkPad X1 Carbon 6th
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1802283/+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 1795292] Re: ELAN469D touch pad not working

2018-11-08 Thread FF8Jake

Hi Kenji,

Compiled the 4.18 kernel last night with the proposed changes, but have
no luck. In fact, I have noticed that my keyboard doesn't work 1 out of
3 or so boots either.

I also attempted this by adding additional ACPI IDs based on how people
were doing it in the Github history for the file elan_i2c_core.c (adding
both ELAN061E and ELAN469D). No difference.

I don't compile the Linux kernel every day though, so would really like
someone else to confirm on this one.

Thanks!
Jake

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

Title:
  ELAN469D touch pad not working

Status in Linux:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I installed Bionic Beaver and now upgraded to Cosmic Cuttlefish on
  this Lenovo Ideapad 330S-15ARR laptop.  The touch pad doesn't work in
  either.

  Some possibly relevant info from dmesg:
  i2c_hid i2c-ELAN469D:00: i2c-ELAN469D:00 supply vdd not found, using dummy 
regulator
  i2c_designware AMDI0010:01: controller timed out

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.18.0-7-generic 4.18.0-7.8
  ProcVersionSignature: Ubuntu 4.18.0-7.8-generic 4.18.5
  Uname: Linux 4.18.0-7-generic x86_64
  ApportVersion: 2.20.10-0ubuntu11
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  xorbit 2086 F pulseaudio
   /dev/snd/pcmC1D0p:   xorbit 2086 F...m pulseaudio
   /dev/snd/controlC0:  xorbit 2086 F pulseaudio
  CurrentDesktop: GNOME
  Date: Sun Sep 30 23:14:26 2018
  InstallationDate: Installed on 2018-09-20 (10 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: LENOVO 81FB
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-7-generic 
root=UUID=4d91f09e-6122-4dd4-81fc-482465f8f0e7 ro noapic processor.max_cstate=1 
rcu_nocbs=0-7 pcie_aspm=off pci=noaer quiet splash vt.handoff=1 
elan_i2c.dyndbg=+p
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-7-generic N/A
   linux-backports-modules-4.18.0-7-generic  N/A
   linux-firmware1.175
  SourcePackage: linux
  UpgradeStatus: Upgraded to cosmic on 2018-09-30 (0 days ago)
  dmi.bios.date: 06/08/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 7WCN22WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709WIN
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad 330S-15ARR
  dmi.modalias: 
dmi:bvnLENOVO:bvr7WCN22WW:bd06/08/2018:svnLENOVO:pn81FB:pvrLenovoideapad330S-15ARR:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoideapad330S-15ARR:
  dmi.product.family: ideapad 330S-15ARR
  dmi.product.name: 81FB
  dmi.product.sku: LENOVO_MT_81FB_BU_idea_FM_ideapad 330S-15ARR
  dmi.product.version: Lenovo ideapad 330S-15ARR
  dmi.sys.vendor: LENOVO
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu11
  Architecture: amd64
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 18.10
  InstallationDate: Installed on 2018-09-20 (13 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Tags:  cosmic
  Uname: Linux 4.19.0-041900rc6-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: Upgraded to cosmic on 2018-09-30 (2 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1795292/+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 1802283] Re: system freezes

2018-11-08 Thread jnns

Thank you for your help, Christian. I added the last boot log as you
requested and will try the 4.19 kernel.

** Attachment added: "prev_boot.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1802283/+attachment/5210375/+files/prev_boot.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/1802283

Title:
  system freezes

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  My system freezes once every second day or so.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.18.0-10-generic 4.18.0-10.11
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  Uname: Linux 4.18.0-10-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  jnns   2519 F pulseaudio
   /dev/snd/controlC0:  jnns   2519 F pulseaudio
  CurrentDesktop: GNOME
  Date: Thu Nov  8 12:07:32 2018
  HibernationDevice: RESUME=UUID=18edd09d-0a58-4464-accb-11ff57fc4327
  InstallationDate: Installed on 2018-08-05 (95 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: LENOVO 20KGS5DU00
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/usr/bin/fish
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-10-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash mem_sleep_default=deep 
vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-10-generic N/A
   linux-backports-modules-4.18.0-10-generic  N/A
   linux-firmware 1.175
  SourcePackage: linux
  UpgradeStatus: Upgraded to cosmic on 2018-10-10 (29 days ago)
  dmi.bios.date: 09/17/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N23ET56W (1.31 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20KGS5DU00
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN23ET56W(1.31):bd09/17/2018:svnLENOVO:pn20KGS5DU00:pvrThinkPadX1Carbon6th:rvnLENOVO:rn20KGS5DU00:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Carbon 6th
  dmi.product.name: 20KGS5DU00
  dmi.product.sku: LENOVO_MT_20KG_BU_Think_FM_ThinkPad X1 Carbon 6th
  dmi.product.version: ThinkPad X1 Carbon 6th
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1802283/+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 1799445] Re: linux: 4.18.0-11.12 -proposed tracker

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  backports: bug 1799447 (linux-hwe-edge), bug 1799448 (linux-azure-edge)
  derivatives: bug 1799449 (linux-raspi2), bug 1799450 (linux-aws), bug 1799451 
(linux-azure), bug 1799452 (linux-gcp), bug 1799453 (linux-kvm)
  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Testing FAILED
-   certification-testing: Testing in progress
regression-testing: Testing in progress
verification-testing: Testing 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/1799445

Title:
  linux: 4.18.0-11.12 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Cosmic:
  Confirmed

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  backports: bug 1799447 (linux-hwe-edge), bug 1799448 (linux-azure-edge)
  derivatives: bug 1799449 (linux-raspi2), bug 1799450 (linux-aws), bug 1799451 
(linux-azure), bug 1799452 (linux-gcp), bug 1799453 (linux-kvm)
  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Testing FAILED
regression-testing: Testing in progress
verification-testing: Testing in progress

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1799445/+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 1802306] PulseList.txt

apport information

** Attachment added: "PulseList.txt"
   
https://bugs.launchpad.net/bugs/1802306/+attachment/5210363/+files/PulseList.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/1802306

Title:
  Network connectivity dropping after a few minutes on Intel Corporation
  Wireless 8265 / 8275 (rev 78), ThinkPad T480s

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  STR:
   - connect to Mozilla or Mozilla Guest wifi networks

  After a few seconds / minutes (less than three in general), no more
  network connectivity, but no error reported in dmesg. Only solution is
  to disconnect / reconnect network.

  To date, it does not happen at home, connected on a Netgear R7000 AP, the 
issue is somehow triggered by the infra at Mozilla (Paris office).
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  alex   2871 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 18.10
  HibernationDevice: RESUME=LABEL="Swap"
  InstallationDate: Installed on 2012-11-03 (2196 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
  MachineType: LENOVO 20L7CTO1WW
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic 
root=UUID=45c5d738-161a-4a73-9614-c529fdf655be ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-10-generic N/A
   linux-backports-modules-4.18.0-10-generic  N/A
   linux-firmware 1.175
  Tags:  cosmic
  Uname: Linux 4.18.0-10-generic x86_64
  UpgradeStatus: Upgraded to cosmic on 2018-10-22 (17 days ago)
  UserGroups: adm cdrom dialout dip disk docker kismet libvirt libvirtd lpadmin 
plugdev sambashare sudo vboxusers video
  _MarkForUpload: True
  dmi.bios.date: 09/13/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N22ET49W (1.26 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20L7CTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN22ET49W(1.26):bd09/13/2018:svnLENOVO:pn20L7CTO1WW:pvrThinkPadT480s:rvnLENOVO:rn20L7CTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T480s
  dmi.product.name: 20L7CTO1WW
  dmi.product.sku: LENOVO_MT_20L7_BU_Think_FM_ThinkPad T480s
  dmi.product.version: ThinkPad T480s
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1802306/+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 1802306] RfKill.txt

apport information

** Attachment added: "RfKill.txt"
   https://bugs.launchpad.net/bugs/1802306/+attachment/5210364/+files/RfKill.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/1802306

Title:
  Network connectivity dropping after a few minutes on Intel Corporation
  Wireless 8265 / 8275 (rev 78), ThinkPad T480s

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  STR:
   - connect to Mozilla or Mozilla Guest wifi networks

  After a few seconds / minutes (less than three in general), no more
  network connectivity, but no error reported in dmesg. Only solution is
  to disconnect / reconnect network.

  To date, it does not happen at home, connected on a Netgear R7000 AP, the 
issue is somehow triggered by the infra at Mozilla (Paris office).
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  alex   2871 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 18.10
  HibernationDevice: RESUME=LABEL="Swap"
  InstallationDate: Installed on 2012-11-03 (2196 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
  MachineType: LENOVO 20L7CTO1WW
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic 
root=UUID=45c5d738-161a-4a73-9614-c529fdf655be ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-10-generic N/A
   linux-backports-modules-4.18.0-10-generic  N/A
   linux-firmware 1.175
  Tags:  cosmic
  Uname: Linux 4.18.0-10-generic x86_64
  UpgradeStatus: Upgraded to cosmic on 2018-10-22 (17 days ago)
  UserGroups: adm cdrom dialout dip disk docker kismet libvirt libvirtd lpadmin 
plugdev sambashare sudo vboxusers video
  _MarkForUpload: True
  dmi.bios.date: 09/13/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N22ET49W (1.26 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20L7CTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN22ET49W(1.26):bd09/13/2018:svnLENOVO:pn20L7CTO1WW:pvrThinkPadT480s:rvnLENOVO:rn20L7CTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T480s
  dmi.product.name: 20L7CTO1WW
  dmi.product.sku: LENOVO_MT_20L7_BU_Think_FM_ThinkPad T480s
  dmi.product.version: ThinkPad T480s
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1802306/+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 1790513] Re: kdump-config status - not ready to kdump with v4.18 kernel

2018-11-08 Thread Dimitri John Ledkov

** Branch unlinked: lp:~xnox/britney/hints-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/1790513

Title:
  kdump-config status - not ready to kdump with v4.18 kernel

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

Bug description:
  As part of the makedumpfile autopkgtest, a test is done to make sure one can 
dump the kernel.
  The test executes

  $ kdump-config status

  and expects to find that it is ready to kdump, however it is not.

  The check fails at:
  $ cat /sys/kernel/kexec_crash_loaded

  Previously it was 1, but now it is 0.

  Is this intentional? Do we need to change something in makedumpfile?
  Or is something missing in the kernel?

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.18.0-7-generic 4.18.0-7.8
  ProcVersionSignature: Ubuntu 4.18.0-7.8-generic 4.18.5
  Uname: Linux 4.18.0-7-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.10-0ubuntu9
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  xnox   9240 F pulseaudio
   /dev/snd/controlC1:  xnox   9240 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Sep  3 17:07:41 2018
  HibernationDevice: RESUME=UUID=2bf263f1-753f-4b2e-92a6-b00381515e0c
  InstallationDate: Installed on 2012-01-12 (2425 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130318)
  MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-7-generic 
root=UUID=6669d411-80c3-41cc-a629-ad84e1ee6854 ro splash crashkernel=384M-:128M 
crashkernel=384M-2G:128M,2G-:256M crashkernel=384M-2G:128M,2G-:256M 
crashkernel=384M-:128M vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-7-generic N/A
   linux-backports-modules-4.18.0-7-generic  N/A
   linux-firmware1.175
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: Upgraded to cosmic on 2018-06-25 (69 days ago)
  dmi.bios.date: 08/13/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F18g
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z77X-D3H
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF18g:bd08/13/2013:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ77X-D3H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: To be filled by O.E.M.
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1790513/+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 1797367] Re: Ubuntu 18.04.1 - [s390x] Kernel panic while stressing network bonding

** Also affects: linux (Ubuntu Cosmic)
   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/1797367

Title:
  Ubuntu 18.04.1 - [s390x] Kernel panic while stressing network bonding

Status in Ubuntu on IBM z Systems:
  In Progress
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Bionic:
  In Progress
Status in linux source package in Cosmic:
  New

Bug description:
  == SRU Justification ==

  While running a series of stress tests for network on a bond device on Ubuntu 
18.04.1 with kernel 4.15.0-36.39,
  kernel panic is observed (btw. also on non-bond devices).
  This looks like a race between disabling a qeth device and accessing debugfs.
  This is critical and leads repeatedly to a crash (sooner or later).

  == Fix ==

  e19e5be8b4ca ("s390/qeth: sanitize strings in debug messages")

  pre-reqs:
  750b162 ("s390/qeth: reduce hard-coded access to ccw channels")
  d857e11 ("s390/qeth: remove outdated portname debug msg")
  9d0a58f ("s390/qeth: avoid using is_multicast_ether_addr_64bits on (u8 *)[6]")
  8174aa8 ("s390/qeth: consolidate qeth MAC address helpers")
  4641b02 ("s390/qeth: don't keep track of MAC address's cast type")

  == Regression Potential ==

  Low, because:

  - limited to s390x
  - and again limited to qeth driver
  - patches a problem identified during testing
  - fix was tested by IBM before submitted

  == Test Case ==

  run:
 #!/bin/bash
 var=0
 while :
 do
  var=$((var + 1))
  echo "DBG count is $var"
  mkdir /tmp/DBGINFO
  dbginfo.sh -d /tmp/DBGINFO
  rm -rf /tmp/DBGINFO*
  echo "chzdev now is $var"
  chzdev -e 
  chzdev -d 
 done
  and in avg. in less than 20 cycles a crash happens (usually < 10).

  __

  == Comment: #0 - Athira Rajeev
  ---Problem Description---
  While running a series of stress tests for network bonding on UBUNTU 18.04.1 
with kernel 4.15.0-36.39, kernel panic is observed.
  There are two instance of panic experienced with the same test procedures one 
of which indicates to be a kernel BUG.

  Contact Information = Athira Rajeev , Waiki
  Wright < wa...@us.ibm.com >

  ---uname output---
  #39-Ubuntu SMP Mon Sep 24 16:13:24 UTC 2018 4.15.0-36.39

  Machine Type = This issue is observed on z13 system
   ---Debugger---
  A debugger was configured,

  ---Steps to Reproduce---
  This happens while running stress tests for network bonding. kernel memory 
exposure attempt is detected and the BUG() is called from the code snippet: 
mm/usercopy.c:72
  dump was configured and crash dump is available.
  Results of few crash commands like bt, log are added in Attachment

  Relevant part of dmesg pointing to kernel BUG

  <<>>
  [14746.977364] kernel BUG at 
/build/linux-PABIrW/linux-4.15.0/mm/usercopy.c:72!
  [14746.977377] illegal operation: 0001 ilc:1 [#1] SMP
  [14746.977378] Modules linked in: macsec vsock_diag vsock sctp_diag sctp 
dccp_diag dccp tcp_diag udp_diag raw_diag inet_diag unix_diag af_packet_diag 
netlink_diag bonding binfmt_misc qeth_l3 8021q garp mrp stp llc xt_tcpudp 
qeth_l2 nf_conntrack_ipv6 nf_defrag_ipv6 scsi_dh_rdac scsi_dh_emc scsi_dh_alua 
s390_trng ghash_s390 prng sha512_s390 sha256_s390 sha1_s390 sha_common chsc_sch 
eadm_sch nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack libcrc32c 
crc32_vx_s390 qeth ccwgroup ip6table_filter ip6_tables vfio_ccw vfio_mdev mdev 
vfio_iommu_type1 vfio iptable_filter sch_fq_codel ip_tables x_tables aes_s390 
des_s390 des_generic dm_crypt dm_service_time dm_multipath zfcp 
scsi_transport_fc qdio dasd_eckd_mod dasd_mod btrfs xor zstd_compress raid6_pq 
zlib_deflate
  [14746.977401] CPU: 1 PID: 20905 Comm: dump2tar Tainted: G   OE
4.15.0-36-generic #39-Ubuntu
  [14746.977403] Hardware name: IBM 3906 M02 757 (LPAR)
  [14746.977404] Krnl PSW : 0f2d230d 6abe14d5 
(__check_object_size+0x15a/0x1e0)
  [14746.977408]R:0 T:1 IO:1 EX:1 Key:0 M:1 W:0 P:0 AS:3 CC:2 PM:0 
RI:0 EA:3
  [14746.977410] Krnl GPRS: 0002 00e95334 0064 
0001e6518828
  [14746.977412]0037cc8e  00a9577c 

  [14746.977413]647b 0001d8c120a8 0001 
8088
  [14746.977433]0001d8c0a020 0090da38 0037cc8e 
00016fdfbcd0
  [14746.977440] Krnl Code: 0037cc82: c0200038ef69larl
%r2,a9ab54
    0037cc88: c0e5fff32838brasl   
%r14,1e1cf8
   #0037cc8e: a7f40001brc 
15,37cc90
   >0037cc92: e330d0080004lg  
%r3,8(%r13)
    0037cc98: e320d004lg  
%r2,0(%r13)

[Kernel-packages] [Bug 1799445] Re: linux: 4.18.0-11.12 -proposed tracker

2018-11-08 Thread Taihsiang Ho

** Changed in: kernel-sru-workflow/certification-testing
   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/1799445

Title:
  linux: 4.18.0-11.12 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Cosmic:
  Confirmed

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  backports: bug 1799447 (linux-hwe-edge), bug 1799448 (linux-azure-edge)
  derivatives: bug 1799449 (linux-raspi2), bug 1799450 (linux-aws), bug 1799451 
(linux-azure), bug 1799452 (linux-gcp), bug 1799453 (linux-kvm)
  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Testing FAILED
regression-testing: Testing in progress
verification-testing: Testing in progress

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1799445/+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 1802306] ProcCpuinfo.txt

apport information

** Attachment added: "ProcCpuinfo.txt"
   
https://bugs.launchpad.net/bugs/1802306/+attachment/5210358/+files/ProcCpuinfo.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/1802306

Title:
  Network connectivity dropping after a few minutes on Intel Corporation
  Wireless 8265 / 8275 (rev 78), ThinkPad T480s

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  STR:
   - connect to Mozilla or Mozilla Guest wifi networks

  After a few seconds / minutes (less than three in general), no more
  network connectivity, but no error reported in dmesg. Only solution is
  to disconnect / reconnect network.

  To date, it does not happen at home, connected on a Netgear R7000 AP, the 
issue is somehow triggered by the infra at Mozilla (Paris office).
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  alex   2871 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 18.10
  HibernationDevice: RESUME=LABEL="Swap"
  InstallationDate: Installed on 2012-11-03 (2196 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
  MachineType: LENOVO 20L7CTO1WW
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic 
root=UUID=45c5d738-161a-4a73-9614-c529fdf655be ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-10-generic N/A
   linux-backports-modules-4.18.0-10-generic  N/A
   linux-firmware 1.175
  Tags:  cosmic
  Uname: Linux 4.18.0-10-generic x86_64
  UpgradeStatus: Upgraded to cosmic on 2018-10-22 (17 days ago)
  UserGroups: adm cdrom dialout dip disk docker kismet libvirt libvirtd lpadmin 
plugdev sambashare sudo vboxusers video
  _MarkForUpload: True
  dmi.bios.date: 09/13/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N22ET49W (1.26 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20L7CTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN22ET49W(1.26):bd09/13/2018:svnLENOVO:pn20L7CTO1WW:pvrThinkPadT480s:rvnLENOVO:rn20L7CTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T480s
  dmi.product.name: 20L7CTO1WW
  dmi.product.sku: LENOVO_MT_20L7_BU_Think_FM_ThinkPad T480s
  dmi.product.version: ThinkPad T480s
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1802306/+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 1799184] Re: [18.04 FEAT] zcrypt DD: introduce APQN tags to support deterministic driver binding

** Changed in: linux (Ubuntu Bionic)
   Status: In Progress => Fix Committed

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

Title:
  [18.04 FEAT] zcrypt DD: introduce APQN tags to support deterministic
  driver binding

Status in Ubuntu on IBM z Systems:
  In Progress
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Bionic:
  Fix Committed

Bug description:
  == SRU Justification ==

  APQN tags in the zcrypt device driver are required to support
  deterministic driver binding

  With the introduction of KVM hw crypto virtualization (on s390x) the driver 
bound to an AP queue device is no longer unique determined.
  Therefore a deterministic hot plugging semantics of AP queues that may be 
bound to multiple drivers is needed.
  With the three listed commits here it will be possible to configure an AP 
queue (APQN) as being bound to a particular driver even if the associate hw 
gets intermittently lost and reconnected.

  == Fixes ==

  ac2b96f351d7d222 ("s390/zcrypt: code beautify")
  7e0bdbe5c21cb831 ("s390/zcrypt: AP bus support for alternate driver(s)")
  3d8f60d38e249f98 ("s390/zcrypt: hex string mask improvements for apmask and 
aqmask")

  == Patches ==

  Git-commit: ac2b96f351d7d222
  
https://github.com/torvalds/linux/commit/ac2b96f351d7d222c46e524feca03005f3fa8d75
  Author: Harald Freudenberger 
  Date:   Fri Aug 17 12:36:01 2018 +0200
  s390/zcrypt: code beautify
  Code beautify by following most of the checkpatch suggestions:
   - SPDX license identifier line complains by checkpatch
   - missing space or newline complains by checkpatch
   - octal numbers for permssions complains by checkpatch
   - renaming of static sysfs functions complains by checkpatch
   - fix of block comment complains by checkpatch
   - fix printf like calls where function name instead of %s __func__
     was used
   - __packed instead of __attribute__((packed))
   - init to zero for static variables removed
   - use of DEVICE_ATTR_RO and DEVICE_ATTR_RW macros

  No functional code changes or API changes!

  Signed-off-by: Harald Freudenberger 
  Signed-off-by: Martin Schwidefsky 

  ===

  Git-commit 7e0bdbe5c21cb831
  
https://github.com/torvalds/linux/commit/7e0bdbe5c21cb8316a694e46ad5aad339f6894a6
  Author: Harald Freudenberger 
  Date:   Fri Jul 20 08:36:53 2018 +0200
  s390/zcrypt: AP bus support for alternate driver(s)
  The current AP bus, AP devices and AP device drivers implementation
  uses a clearly defined mapping for binding AP devices to AP device
  drivers. So for example a CEX6C queue will always be bound to the
  cex4queue device driver.

  The Linux Device Driver model has no sensitivity for more than one
  device driver eligible for one device type. If there exist more than
  one drivers matching to the device type, simple all drivers are tried
  consecutively.  There is no way to determine and influence the probing
  order of the drivers.

  With KVM there is a need to provide additional device drivers matching
  to the very same type of AP devices. With a simple implementation the
  KVM drivers run in competition to the regular drivers. Whichever
  'wins' a device depends on build order and implementation details
  within the common Linux Device Driver Model and is not
  deterministic. However, a userspace process could figure out which
  device should be bound to which driver and sort out the correct
  binding by manipulating attributes in the sysfs.

  If for security reasons a AP device must not get bound to the 'wrong'
  device driver the sorting out has to be done within the Linux kernel
  by the AP bus code. This patch modifies the behavior of the AP bus
  for probing drivers for devices in a way that two sets of drivers are
  usable. Two new bitmasks 'apmask' and 'aqmask' are used to mark a
  subset of the APQN range for 'usable by the ap bus and the default
  drivers' or 'not usable by the default drivers and thus available for
  alternate drivers like vfio-xxx'. So an APQN which is addressed by
  this masking only the default drivers will be probed. In contrary an
  APQN which is not addressed by the masks will never be probed and
  bound to default drivers but onny to alternate drivers.

  Eventually the two masks give a way to divide the range of APQNs into
  two pools: one pool of APQNs used by the AP bus and the default
  drivers and thus via zcrypt drivers available to the userspace of the
  system. And another pool where no zcrypt drivers are bound to and
  which can be used by alternate drivers (like vfio-xxx) for their
  needs. This division is hot-plug save and makes sure a APQN assigned
  to an alternate driver is at no time somehow exploitable by the wrong
  party.

  The two masks are located in sysfs at /sys/bus/ap/apmask and
  /sys/bus/ap/aqmask.  The mask syntax is exactly the same as the
  already existing mask

[Kernel-packages] [Bug 1802306] WifiSyslog.txt

apport information

** Attachment added: "WifiSyslog.txt"
   
https://bugs.launchpad.net/bugs/1802306/+attachment/5210366/+files/WifiSyslog.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/1802306

Title:
  Network connectivity dropping after a few minutes on Intel Corporation
  Wireless 8265 / 8275 (rev 78), ThinkPad T480s

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  STR:
   - connect to Mozilla or Mozilla Guest wifi networks

  After a few seconds / minutes (less than three in general), no more
  network connectivity, but no error reported in dmesg. Only solution is
  to disconnect / reconnect network.

  To date, it does not happen at home, connected on a Netgear R7000 AP, the 
issue is somehow triggered by the infra at Mozilla (Paris office).
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  alex   2871 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 18.10
  HibernationDevice: RESUME=LABEL="Swap"
  InstallationDate: Installed on 2012-11-03 (2196 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
  MachineType: LENOVO 20L7CTO1WW
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic 
root=UUID=45c5d738-161a-4a73-9614-c529fdf655be ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-10-generic N/A
   linux-backports-modules-4.18.0-10-generic  N/A
   linux-firmware 1.175
  Tags:  cosmic
  Uname: Linux 4.18.0-10-generic x86_64
  UpgradeStatus: Upgraded to cosmic on 2018-10-22 (17 days ago)
  UserGroups: adm cdrom dialout dip disk docker kismet libvirt libvirtd lpadmin 
plugdev sambashare sudo vboxusers video
  _MarkForUpload: True
  dmi.bios.date: 09/13/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N22ET49W (1.26 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20L7CTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN22ET49W(1.26):bd09/13/2018:svnLENOVO:pn20L7CTO1WW:pvrThinkPadT480s:rvnLENOVO:rn20L7CTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T480s
  dmi.product.name: 20L7CTO1WW
  dmi.product.sku: LENOVO_MT_20L7_BU_Think_FM_ThinkPad T480s
  dmi.product.version: ThinkPad T480s
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1802306/+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 1799401] Re: linux: 4.4.0-139.165 -proposed tracker

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  backports: bug 1799403 (linux-aws), bug 1799404 (linux-lts-xenial)
  derivatives: bug 1799405 (linux-aws), bug 1799407 (linux-euclid), bug 1799408 
(linux-kvm), bug 1799409 (linux-raspi2), bug 1799410 (linux-snapdragon)
  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
regression-testing: Testing in progress
snap-certification-testing: Ready
-   verification-testing: Testing 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/1799401

Title:
  linux: 4.4.0-139.165 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Fix Released
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow snap-certification-testing series:
  Confirmed
Status in Kernel SRU Workflow snap-release-to-beta series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-candidate series:
  New
Status in Kernel SRU Workflow snap-release-to-edge series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-stable series:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Confirmed

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  backports: bug 1799403 (linux-aws), bug 1799404 (linux-lts-xenial)
  derivatives: bug 1799405 (linux-aws), bug 1799407 (linux-euclid), bug 1799408 
(linux-kvm), bug 1799409 (linux-raspi2), bug 1799410 (linux-snapdragon)
  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
regression-testing: Testing in progress
snap-certification-testing: Ready

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1799401/+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 1801124] Re: linux-aws: 4.4.0-1072.82 -proposed tracker

** Changed in: kernel-sru-workflow/verification-testing
   Status: Confirmed => Fix Released

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1799401
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
regression-testing: Testing in progress
-   verification-testing: Testing in progress

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

Title:
  linux-aws: 4.4.0-1072.82 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-beta series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-candidate series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-edge series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-stable series:
  Invalid
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux-aws package in Ubuntu:
  Invalid
Status in linux-aws source package in Xenial:
  Confirmed

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1799401
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
regression-testing: Testing in progress

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1801124/+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 1802306] Status changed to Confirmed

This change was made by a bot.

** Changed in: linux (Ubuntu)
   Status: New => 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/1802306

Title:
  Network connectivity dropping after a few minutes on Intel Corporation
  Wireless 8265 / 8275 (rev 78), ThinkPad T480s

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  STR:
   - connect to Mozilla or Mozilla Guest wifi networks

  After a few seconds / minutes (less than three in general), no more
  network connectivity, but no error reported in dmesg. Only solution is
  to disconnect / reconnect network.

  To date, it does not happen at home, connected on a Netgear R7000 AP, the 
issue is somehow triggered by the infra at Mozilla (Paris office).
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  alex   2871 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 18.10
  HibernationDevice: RESUME=LABEL="Swap"
  InstallationDate: Installed on 2012-11-03 (2196 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
  MachineType: LENOVO 20L7CTO1WW
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic 
root=UUID=45c5d738-161a-4a73-9614-c529fdf655be ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-10-generic N/A
   linux-backports-modules-4.18.0-10-generic  N/A
   linux-firmware 1.175
  Tags:  cosmic
  Uname: Linux 4.18.0-10-generic x86_64
  UpgradeStatus: Upgraded to cosmic on 2018-10-22 (17 days ago)
  UserGroups: adm cdrom dialout dip disk docker kismet libvirt libvirtd lpadmin 
plugdev sambashare sudo vboxusers video
  _MarkForUpload: True
  dmi.bios.date: 09/13/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N22ET49W (1.26 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20L7CTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN22ET49W(1.26):bd09/13/2018:svnLENOVO:pn20L7CTO1WW:pvrThinkPadT480s:rvnLENOVO:rn20L7CTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T480s
  dmi.product.name: 20L7CTO1WW
  dmi.product.sku: LENOVO_MT_20L7_BU_Think_FM_ThinkPad T480s
  dmi.product.version: ThinkPad T480s
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1802306/+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 1802306] UdevDb.txt

apport information

** Attachment added: "UdevDb.txt"
   https://bugs.launchpad.net/bugs/1802306/+attachment/5210365/+files/UdevDb.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/1802306

Title:
  Network connectivity dropping after a few minutes on Intel Corporation
  Wireless 8265 / 8275 (rev 78), ThinkPad T480s

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  STR:
   - connect to Mozilla or Mozilla Guest wifi networks

  After a few seconds / minutes (less than three in general), no more
  network connectivity, but no error reported in dmesg. Only solution is
  to disconnect / reconnect network.

  To date, it does not happen at home, connected on a Netgear R7000 AP, the 
issue is somehow triggered by the infra at Mozilla (Paris office).
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  alex   2871 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 18.10
  HibernationDevice: RESUME=LABEL="Swap"
  InstallationDate: Installed on 2012-11-03 (2196 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
  MachineType: LENOVO 20L7CTO1WW
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic 
root=UUID=45c5d738-161a-4a73-9614-c529fdf655be ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-10-generic N/A
   linux-backports-modules-4.18.0-10-generic  N/A
   linux-firmware 1.175
  Tags:  cosmic
  Uname: Linux 4.18.0-10-generic x86_64
  UpgradeStatus: Upgraded to cosmic on 2018-10-22 (17 days ago)
  UserGroups: adm cdrom dialout dip disk docker kismet libvirt libvirtd lpadmin 
plugdev sambashare sudo vboxusers video
  _MarkForUpload: True
  dmi.bios.date: 09/13/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N22ET49W (1.26 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20L7CTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN22ET49W(1.26):bd09/13/2018:svnLENOVO:pn20L7CTO1WW:pvrThinkPadT480s:rvnLENOVO:rn20L7CTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T480s
  dmi.product.name: 20L7CTO1WW
  dmi.product.sku: LENOVO_MT_20L7_BU_Think_FM_ThinkPad T480s
  dmi.product.version: ThinkPad T480s
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1802306/+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 1802306] Re: Network connectivity dropping after a few minutes on Intel Corporation Wireless 8265 / 8275 (rev 78), ThinkPad T480s

After extensive playing with iwlwifi, I could stop the issue by doing either:
 - modprobe iwlwifi 11n_disable=1
 - blacklist the v36 firmware /lib/firmware/iwlwifi-8265-36.ucode, driver picks 
v34 which seems to be stable

I tested the two releases of v36: 36.7596afd4.0 and 36.e91976c0.0, both
expose the same issue.

Given the impact on speed, I've chose the second solution as a
workaround.

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

Title:
  Network connectivity dropping after a few minutes on Intel Corporation
  Wireless 8265 / 8275 (rev 78), ThinkPad T480s

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  STR:
   - connect to Mozilla or Mozilla Guest wifi networks

  After a few seconds / minutes (less than three in general), no more
  network connectivity, but no error reported in dmesg. Only solution is
  to disconnect / reconnect network.

  To date, it does not happen at home, connected on a Netgear R7000 AP, the 
issue is somehow triggered by the infra at Mozilla (Paris office).
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  alex   2871 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 18.10
  HibernationDevice: RESUME=LABEL="Swap"
  InstallationDate: Installed on 2012-11-03 (2196 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
  MachineType: LENOVO 20L7CTO1WW
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic 
root=UUID=45c5d738-161a-4a73-9614-c529fdf655be ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-10-generic N/A
   linux-backports-modules-4.18.0-10-generic  N/A
   linux-firmware 1.175
  Tags:  cosmic
  Uname: Linux 4.18.0-10-generic x86_64
  UpgradeStatus: Upgraded to cosmic on 2018-10-22 (17 days ago)
  UserGroups: adm cdrom dialout dip disk docker kismet libvirt libvirtd lpadmin 
plugdev sambashare sudo vboxusers video
  _MarkForUpload: True
  dmi.bios.date: 09/13/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N22ET49W (1.26 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20L7CTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN22ET49W(1.26):bd09/13/2018:svnLENOVO:pn20L7CTO1WW:pvrThinkPadT480s:rvnLENOVO:rn20L7CTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T480s
  dmi.product.name: 20L7CTO1WW
  dmi.product.sku: LENOVO_MT_20L7_BU_Think_FM_ThinkPad T480s
  dmi.product.version: ThinkPad T480s
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1802306/+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 1799408] Re: linux-kvm: 4.4.0-1037.43 -proposed tracker

** Changed in: kernel-sru-workflow/verification-testing
   Status: Confirmed => Fix Released

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1799401
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true
- reason:
-   verification-testing: Testing in progress

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

Title:
  linux-kvm: 4.4.0-1037.43 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux-kvm package in Ubuntu:
  Invalid
Status in linux-kvm source package in Xenial:
  Confirmed

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1799401
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1799408/+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 1801123] Re: linux-aws: 4.4.0-1034.37 -proposed tracker

** Changed in: kernel-sru-workflow/verification-testing
   Status: Confirmed => Fix Released

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1799401
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
regression-testing: Testing in progress
-   verification-testing: Testing in progress

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

Title:
  linux-aws: 4.4.0-1034.37 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux-aws package in Ubuntu:
  Invalid
Status in linux-aws source package in Trusty:
  Confirmed

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1799401
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
regression-testing: Testing in progress

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1801123/+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 1799184] Re: [18.04 FEAT] zcrypt DD: introduce APQN tags to support deterministic driver binding

2018-11-08 Thread Frank Heimes

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

** Changed in: ubuntu-z-systems
   Status: In Progress => Fix Committed

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

Title:
  [18.04 FEAT] zcrypt DD: introduce APQN tags to support deterministic
  driver binding

Status in Ubuntu on IBM z Systems:
  Fix Committed
Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Bionic:
  Fix Committed

Bug description:
  == SRU Justification ==

  APQN tags in the zcrypt device driver are required to support
  deterministic driver binding

  With the introduction of KVM hw crypto virtualization (on s390x) the driver 
bound to an AP queue device is no longer unique determined.
  Therefore a deterministic hot plugging semantics of AP queues that may be 
bound to multiple drivers is needed.
  With the three listed commits here it will be possible to configure an AP 
queue (APQN) as being bound to a particular driver even if the associate hw 
gets intermittently lost and reconnected.

  == Fixes ==

  ac2b96f351d7d222 ("s390/zcrypt: code beautify")
  7e0bdbe5c21cb831 ("s390/zcrypt: AP bus support for alternate driver(s)")
  3d8f60d38e249f98 ("s390/zcrypt: hex string mask improvements for apmask and 
aqmask")

  == Patches ==

  Git-commit: ac2b96f351d7d222
  
https://github.com/torvalds/linux/commit/ac2b96f351d7d222c46e524feca03005f3fa8d75
  Author: Harald Freudenberger 
  Date:   Fri Aug 17 12:36:01 2018 +0200
  s390/zcrypt: code beautify
  Code beautify by following most of the checkpatch suggestions:
   - SPDX license identifier line complains by checkpatch
   - missing space or newline complains by checkpatch
   - octal numbers for permssions complains by checkpatch
   - renaming of static sysfs functions complains by checkpatch
   - fix of block comment complains by checkpatch
   - fix printf like calls where function name instead of %s __func__
     was used
   - __packed instead of __attribute__((packed))
   - init to zero for static variables removed
   - use of DEVICE_ATTR_RO and DEVICE_ATTR_RW macros

  No functional code changes or API changes!

  Signed-off-by: Harald Freudenberger 
  Signed-off-by: Martin Schwidefsky 

  ===

  Git-commit 7e0bdbe5c21cb831
  
https://github.com/torvalds/linux/commit/7e0bdbe5c21cb8316a694e46ad5aad339f6894a6
  Author: Harald Freudenberger 
  Date:   Fri Jul 20 08:36:53 2018 +0200
  s390/zcrypt: AP bus support for alternate driver(s)
  The current AP bus, AP devices and AP device drivers implementation
  uses a clearly defined mapping for binding AP devices to AP device
  drivers. So for example a CEX6C queue will always be bound to the
  cex4queue device driver.

  The Linux Device Driver model has no sensitivity for more than one
  device driver eligible for one device type. If there exist more than
  one drivers matching to the device type, simple all drivers are tried
  consecutively.  There is no way to determine and influence the probing
  order of the drivers.

  With KVM there is a need to provide additional device drivers matching
  to the very same type of AP devices. With a simple implementation the
  KVM drivers run in competition to the regular drivers. Whichever
  'wins' a device depends on build order and implementation details
  within the common Linux Device Driver Model and is not
  deterministic. However, a userspace process could figure out which
  device should be bound to which driver and sort out the correct
  binding by manipulating attributes in the sysfs.

  If for security reasons a AP device must not get bound to the 'wrong'
  device driver the sorting out has to be done within the Linux kernel
  by the AP bus code. This patch modifies the behavior of the AP bus
  for probing drivers for devices in a way that two sets of drivers are
  usable. Two new bitmasks 'apmask' and 'aqmask' are used to mark a
  subset of the APQN range for 'usable by the ap bus and the default
  drivers' or 'not usable by the default drivers and thus available for
  alternate drivers like vfio-xxx'. So an APQN which is addressed by
  this masking only the default drivers will be probed. In contrary an
  APQN which is not addressed by the masks will never be probed and
  bound to default drivers but onny to alternate drivers.

  Eventually the two masks give a way to divide the range of APQNs into
  two pools: one pool of APQNs used by the AP bus and the default
  drivers and thus via zcrypt drivers available to the userspace of the
  system. And another pool where no zcrypt drivers are bound to and
  which can be used by alternate drivers (like vfio-xxx) for their
  needs. This division is hot-plug save and makes sure a APQN assigned
  to an alternate driver is at no time somehow exploitable by the wrong
  party.

  The two masks are located in sysfs at /sys/bus/ap/apmask and
  /sys/bus/ap/aqmask.

[Kernel-packages] [Bug 1802306] AlsaInfo.txt

apport information

** Attachment added: "AlsaInfo.txt"
   
https://bugs.launchpad.net/bugs/1802306/+attachment/5210352/+files/AlsaInfo.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/1802306

Title:
  Network connectivity dropping after a few minutes on Intel Corporation
  Wireless 8265 / 8275 (rev 78), ThinkPad T480s

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  STR:
   - connect to Mozilla or Mozilla Guest wifi networks

  After a few seconds / minutes (less than three in general), no more
  network connectivity, but no error reported in dmesg. Only solution is
  to disconnect / reconnect network.

  To date, it does not happen at home, connected on a Netgear R7000 AP, the 
issue is somehow triggered by the infra at Mozilla (Paris office).
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  alex   2871 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 18.10
  HibernationDevice: RESUME=LABEL="Swap"
  InstallationDate: Installed on 2012-11-03 (2196 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
  MachineType: LENOVO 20L7CTO1WW
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic 
root=UUID=45c5d738-161a-4a73-9614-c529fdf655be ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-10-generic N/A
   linux-backports-modules-4.18.0-10-generic  N/A
   linux-firmware 1.175
  Tags:  cosmic
  Uname: Linux 4.18.0-10-generic x86_64
  UpgradeStatus: Upgraded to cosmic on 2018-10-22 (17 days ago)
  UserGroups: adm cdrom dialout dip disk docker kismet libvirt libvirtd lpadmin 
plugdev sambashare sudo vboxusers video
  _MarkForUpload: True
  dmi.bios.date: 09/13/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N22ET49W (1.26 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20L7CTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN22ET49W(1.26):bd09/13/2018:svnLENOVO:pn20L7CTO1WW:pvrThinkPadT480s:rvnLENOVO:rn20L7CTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T480s
  dmi.product.name: 20L7CTO1WW
  dmi.product.sku: LENOVO_MT_20L7_BU_Think_FM_ThinkPad T480s
  dmi.product.version: ThinkPad T480s
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1802306/+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 1802306] IwConfig.txt

apport information

** Attachment added: "IwConfig.txt"
   
https://bugs.launchpad.net/bugs/1802306/+attachment/5210355/+files/IwConfig.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/1802306

Title:
  Network connectivity dropping after a few minutes on Intel Corporation
  Wireless 8265 / 8275 (rev 78), ThinkPad T480s

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  STR:
   - connect to Mozilla or Mozilla Guest wifi networks

  After a few seconds / minutes (less than three in general), no more
  network connectivity, but no error reported in dmesg. Only solution is
  to disconnect / reconnect network.

  To date, it does not happen at home, connected on a Netgear R7000 AP, the 
issue is somehow triggered by the infra at Mozilla (Paris office).
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  alex   2871 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 18.10
  HibernationDevice: RESUME=LABEL="Swap"
  InstallationDate: Installed on 2012-11-03 (2196 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
  MachineType: LENOVO 20L7CTO1WW
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic 
root=UUID=45c5d738-161a-4a73-9614-c529fdf655be ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-10-generic N/A
   linux-backports-modules-4.18.0-10-generic  N/A
   linux-firmware 1.175
  Tags:  cosmic
  Uname: Linux 4.18.0-10-generic x86_64
  UpgradeStatus: Upgraded to cosmic on 2018-10-22 (17 days ago)
  UserGroups: adm cdrom dialout dip disk docker kismet libvirt libvirtd lpadmin 
plugdev sambashare sudo vboxusers video
  _MarkForUpload: True
  dmi.bios.date: 09/13/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N22ET49W (1.26 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20L7CTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN22ET49W(1.26):bd09/13/2018:svnLENOVO:pn20L7CTO1WW:pvrThinkPadT480s:rvnLENOVO:rn20L7CTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T480s
  dmi.product.name: 20L7CTO1WW
  dmi.product.sku: LENOVO_MT_20L7_BU_Think_FM_ThinkPad T480s
  dmi.product.version: ThinkPad T480s
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1802306/+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 1802306] ProcInterrupts.txt

apport information

** Attachment added: "ProcInterrupts.txt"
   
https://bugs.launchpad.net/bugs/1802306/+attachment/5210361/+files/ProcInterrupts.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/1802306

Title:
  Network connectivity dropping after a few minutes on Intel Corporation
  Wireless 8265 / 8275 (rev 78), ThinkPad T480s

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  STR:
   - connect to Mozilla or Mozilla Guest wifi networks

  After a few seconds / minutes (less than three in general), no more
  network connectivity, but no error reported in dmesg. Only solution is
  to disconnect / reconnect network.

  To date, it does not happen at home, connected on a Netgear R7000 AP, the 
issue is somehow triggered by the infra at Mozilla (Paris office).
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  alex   2871 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 18.10
  HibernationDevice: RESUME=LABEL="Swap"
  InstallationDate: Installed on 2012-11-03 (2196 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
  MachineType: LENOVO 20L7CTO1WW
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic 
root=UUID=45c5d738-161a-4a73-9614-c529fdf655be ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-10-generic N/A
   linux-backports-modules-4.18.0-10-generic  N/A
   linux-firmware 1.175
  Tags:  cosmic
  Uname: Linux 4.18.0-10-generic x86_64
  UpgradeStatus: Upgraded to cosmic on 2018-10-22 (17 days ago)
  UserGroups: adm cdrom dialout dip disk docker kismet libvirt libvirtd lpadmin 
plugdev sambashare sudo vboxusers video
  _MarkForUpload: True
  dmi.bios.date: 09/13/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N22ET49W (1.26 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20L7CTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN22ET49W(1.26):bd09/13/2018:svnLENOVO:pn20L7CTO1WW:pvrThinkPadT480s:rvnLENOVO:rn20L7CTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T480s
  dmi.product.name: 20L7CTO1WW
  dmi.product.sku: LENOVO_MT_20L7_BU_Think_FM_ThinkPad T480s
  dmi.product.version: ThinkPad T480s
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1802306/+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 1802306] Lsusb.txt

apport information

** Attachment added: "Lsusb.txt"
   https://bugs.launchpad.net/bugs/1802306/+attachment/5210357/+files/Lsusb.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/1802306

Title:
  Network connectivity dropping after a few minutes on Intel Corporation
  Wireless 8265 / 8275 (rev 78), ThinkPad T480s

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  STR:
   - connect to Mozilla or Mozilla Guest wifi networks

  After a few seconds / minutes (less than three in general), no more
  network connectivity, but no error reported in dmesg. Only solution is
  to disconnect / reconnect network.

  To date, it does not happen at home, connected on a Netgear R7000 AP, the 
issue is somehow triggered by the infra at Mozilla (Paris office).
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  alex   2871 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 18.10
  HibernationDevice: RESUME=LABEL="Swap"
  InstallationDate: Installed on 2012-11-03 (2196 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
  MachineType: LENOVO 20L7CTO1WW
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic 
root=UUID=45c5d738-161a-4a73-9614-c529fdf655be ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-10-generic N/A
   linux-backports-modules-4.18.0-10-generic  N/A
   linux-firmware 1.175
  Tags:  cosmic
  Uname: Linux 4.18.0-10-generic x86_64
  UpgradeStatus: Upgraded to cosmic on 2018-10-22 (17 days ago)
  UserGroups: adm cdrom dialout dip disk docker kismet libvirt libvirtd lpadmin 
plugdev sambashare sudo vboxusers video
  _MarkForUpload: True
  dmi.bios.date: 09/13/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N22ET49W (1.26 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20L7CTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN22ET49W(1.26):bd09/13/2018:svnLENOVO:pn20L7CTO1WW:pvrThinkPadT480s:rvnLENOVO:rn20L7CTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T480s
  dmi.product.name: 20L7CTO1WW
  dmi.product.sku: LENOVO_MT_20L7_BU_Think_FM_ThinkPad T480s
  dmi.product.version: ThinkPad T480s
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1802306/+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 1802306] ProcModules.txt

apport information

** Attachment added: "ProcModules.txt"
   
https://bugs.launchpad.net/bugs/1802306/+attachment/5210362/+files/ProcModules.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/1802306

Title:
  Network connectivity dropping after a few minutes on Intel Corporation
  Wireless 8265 / 8275 (rev 78), ThinkPad T480s

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  STR:
   - connect to Mozilla or Mozilla Guest wifi networks

  After a few seconds / minutes (less than three in general), no more
  network connectivity, but no error reported in dmesg. Only solution is
  to disconnect / reconnect network.

  To date, it does not happen at home, connected on a Netgear R7000 AP, the 
issue is somehow triggered by the infra at Mozilla (Paris office).
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  alex   2871 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 18.10
  HibernationDevice: RESUME=LABEL="Swap"
  InstallationDate: Installed on 2012-11-03 (2196 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
  MachineType: LENOVO 20L7CTO1WW
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic 
root=UUID=45c5d738-161a-4a73-9614-c529fdf655be ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-10-generic N/A
   linux-backports-modules-4.18.0-10-generic  N/A
   linux-firmware 1.175
  Tags:  cosmic
  Uname: Linux 4.18.0-10-generic x86_64
  UpgradeStatus: Upgraded to cosmic on 2018-10-22 (17 days ago)
  UserGroups: adm cdrom dialout dip disk docker kismet libvirt libvirtd lpadmin 
plugdev sambashare sudo vboxusers video
  _MarkForUpload: True
  dmi.bios.date: 09/13/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N22ET49W (1.26 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20L7CTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN22ET49W(1.26):bd09/13/2018:svnLENOVO:pn20L7CTO1WW:pvrThinkPadT480s:rvnLENOVO:rn20L7CTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T480s
  dmi.product.name: 20L7CTO1WW
  dmi.product.sku: LENOVO_MT_20L7_BU_Think_FM_ThinkPad T480s
  dmi.product.version: ThinkPad T480s
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1802306/+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 1802306] Lspci.txt