[Kernel-packages] [Bug 1720660] Re: linux 4.13.0-13.14 ADT test failure with linux 4.13.0-13.14

[John Johansen]

yep thanks, fixed and pushed


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

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

Title:
  linux 4.13.0-13.14 ADT test failure with linux 4.13.0-13.14

Status in linux package in Ubuntu:
  Fix Released

Bug description:
  Testing failed on:
  amd64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-artful-canonical-kernel-team-bootstrap/artful/amd64/l/linux/20170930_151719_8c658@/log.gz
  i386: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-artful-canonical-kernel-team-bootstrap/artful/i386/l/linux/20170930_220543_8c658@/log.gz
  ppc64el: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-artful-canonical-kernel-team-bootstrap/artful/ppc64el/l/linux/20170930_164802_8c658@/log.gz

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1720660/+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 1567597] Re: implement 'complain mode' in seccomp for developer mode with snaps

[Tyler Hicks]

The Xenial and Zesty kernel patch sets have been sent to the kernel
team:

https://lists.ubuntu.com/archives/kernel-team/2017-October/087448.html
https://lists.ubuntu.com/archives/kernel-team/2017-October/087456.html

I've uploaded a libseccomp SRU to zesty-proposed. The Xenial SRU is
going to be trickier. It may require bring Zesty's libseccomp back to
Xenial due to the current version of libseccomp in Xenial not fully
supporting the seccomp(2) system call. That system call is needed to
verify kernel support of the SECCOMP_RET_LOG action that's needed for
devmode.

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

Title:
  implement 'complain mode' in seccomp for developer mode with snaps

Status in Snappy:
  In Progress
Status in libseccomp package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in libseccomp source package in Xenial:
  In Progress
Status in linux source package in Xenial:
  In Progress
Status in libseccomp source package in Zesty:
  In Progress
Status in linux source package in Zesty:
  In Progress

Bug description:
  A requirement for snappy is that a snap may be placed in developer
  mode which will put the security sandbox in complain mode such that
  violations against policy are logged, but permitted. In this manner
  learning tools can be written to parse the logs, etc and make
  developing on snappy easier.

  Unfortunately with seccomp only SCMP_ACT_KILL logs to dmesg and while
  we can set complain mode to permit all calls, they are not logged at
  this time. I've discussed this with upstream and we are working
  together on the approach. This may require a kernel patch and an
  update to libseccomp, to filing this bug for now as a placeholder and
  we'll add other tasks as necessary.

  UPDATE: ubuntu-core-launcher now supports the '@complain' directive
  that is a synonym for '@unrestricted' so people can at least turn on
  developer mode and not be blocked by seccomp. Proper complain mode for
  seccomp needs to still be implemented (this bug).

  [Impact]

  Snapd needs a way to log seccomp actions without blocking any syscalls
  in order to have a more useful complain mode. Such functionality has
  been acked upstream and patches are on their way into the Linux 4.14
  kernel (backported to 4.12.0-13.14 in artful).

  The corresponding libseccomp changes are still undergoing review
  (https://github.com/seccomp/libseccomp/pull/92). The pull request adds
  a number of new symbols and probably isn't appropriate to backport
  until upstream has acked the pull request. However, only a small part
  of that larger pull request is needed by snapd and that change can be
  safely backported since the only added symbol, the SCMP_ACT_LOG macro,
  must match the SECCOMP_RET_LOG macro that has already been approved
  and merged in the upstream Linux kernel.

  [libseccomp Test Case]

  A large number of tests are ran as part of the libseccomp build.
  However, the "live" tests which test libseccomp with actual kernel
  enforcement are not ran at that time. They can be manually exercised
  to help catch any regressions. Note that on Artful, there's an
  existing test failure (20-live-basic_die%%002-1):

  $ sudo apt build-dep -y libseccomp
  $ sudo apt install -y cython
  $ apt source libseccomp
  $ cd libseccomp-*
  $ autoreconf -ivf && ./configure --enable-python && make check-build
  $ (cd tests && ./regression -T live)

  All tests should pass on zesty (12 tests) and xenial (10 tests). On artful, 
you'll see one pre-existing failure:
  ...
  Test 20-live-basic_die%%002-1 result:   FAILURE 20-live-basic_die TRAP 
rc=159
  ...
  Regression Test Summary
   tests run: 12
   tests skipped: 0
   tests passed: 11
   tests failed: 1
   tests errored: 0
  

  

  Now we can build and run a small test program to test the SCMP_ACT_LOG
  action in the way that snapd wants to use it for developer mode:

  $ sudo apt install -y libseccomp-dev
  $ gcc -o lp1567597-test lp1567597-test.c -lseccomp
  $ ./lp1567597-test

  With a kernel that contains the logging patches and an updated
  libseccomp, the exit code should be 0 and you should have an entry in
  the system log that looks like this:

  audit: type=1326 audit(1505859630.994:69): auid=1000 uid=1000 gid=1000
  ses=2 pid=18451 comm="lp1567597-test"
  exe="/home/tyhicks/lp1567597-test" sig=0 arch=c03e syscall=2
  compat=0 ip=0x7f547352c5c0 code=0x7ffc

  If you have an updated libseccomp with an old kernel, you'll see that
  seccomp_init() fails due to the added compatibility check inside of
  libseccomp determines that the kernel doesn't have proper support for
  the new log action:

  $ ./lp1567597-test
  ERROR: seccomp_init: Invalid argument

  [Linux Kernel Test Case]

  All of the libseccomp 

[Kernel-packages] [Bug 1721676] Re: implement errno action logging in seccomp for strict mode with snaps

[Tyler Hicks]

The Xenial and Zesty kernel patch sets have been sent to the kernel
team:

https://lists.ubuntu.com/archives/kernel-team/2017-October/087448.html
https://lists.ubuntu.com/archives/kernel-team/2017-October/087456.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/1721676

Title:
  implement errno action logging in seccomp for strict mode with snaps

Status in Snappy:
  In Progress
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  In Progress
Status in linux source package in Zesty:
  In Progress
Status in linux source package in Artful:
  Fix Released

Bug description:
  A requirement for snappy is that security sandbox violations against
  policy are logged. In this manner learning tools can be written to
  parse the logs, etc and make developing on snappy easier.

  The current default seccomp action, in strict mode. is to kill the
  snap's thread that violated the policy but this is unfriendly to the
  developer and to the user. The desired action is to block the illegal
  system call and return an error with errno set to EPERM. However,
  seccomp does not emit log events when it takes that action. Seccomp
  should be updated to emit log events when taking the SECCOMP_RET_ERRNO
  action and then snappy can switch to the using that action when
  blocking illegal system calls.

  [Impact]

  Snapd needs a way to log SECCOMP_RET_ERRNO seccomp actions in order to
  have a more friendly strict mode. Such functionality has been merged
  upstream into 4.14-rc2.

  No libseccomp changes are needed at this time since snap-confine loads
  the BPF filter directly into the kernel without using libseccomp.

  [Test Case]

  Running the libseccomp "live" tests will exercise the kernel's seccomp
  enforcement and help to help catch any regressions. Note that on
  Artful, there's an existing test failure (20-live-
  basic_die%%002-1):

  $ sudo apt build-dep -y libseccomp
  $ sudo apt install -y cython
  $ apt source libseccomp
  $ cd libseccomp-*
  $ autoreconf -ivf && ./configure --enable-python && make check-build
  $ (cd tests && ./regression -T live)

  All tests should pass on zesty (12 tests) and xenial (10 tests). On artful, 
you'll see one pre-existing failure:
  ...
  Test 20-live-basic_die%%002-1 result: FAILURE 20-live-basic_die TRAP 
rc=159
  ...
  Regression Test Summary
   tests run: 12
   tests skipped: 0
   tests passed: 11
   tests failed: 1
   tests errored: 0
  

  

  Running the seccomp kernel selftests is also a great to exercise
  seccomp and the kernel patch set proposed for the SRU includes
  additional seccomp selftests. To build, enter into the root of the
  kernel source tree and build the seccomp test binary:

  $ make -C tools/testing/selftests TARGETS=seccomp

  Now you can execute tools/testing/selftests/seccomp/seccomp_bpf or
  even copy it to a test machine and run it there. On Xenial, 54/54
  tests should pass and 58/58 should pass on Zesty.

  

  Now we can run a single test to verify that SECCOMP_RET_ERRNO is
  logged when the application opts into it. First, verify that "errno"
  is listed in the actions_logged sysctl:

  $ cat /proc/sys/kernel/seccomp/actions_logged
  kill trap errno trace log

  Now, build and run the test program:

  $ gcc -o lp1721676-kernel-test lp1721676-kernel-test.c
  $ ./lp1721676-kernel-test
  SUCCESS: getpid() failed as expected: Operation not permitted

  It should have generated a message like this in /var/log/syslog:

  kernel: [79338.804966] audit: type=1326 audit(1507259221.875:27):
  auid=1000 uid=1000 gid=1000 ses=5 pid=3091 comm="lp1721676-kerne"
  exe="/home/tyhicks/lp1721676-kernel-test" sig=0 arch=c03e
  syscall=39 compat=0 ip=0x7fb91829c499 code=0x5

  Disable errno logging in the sysctl:

  $ echo kill trap trace log | sudo tee /proc/sys/kernel/seccomp/actions_logged
  kill trap trace log

  Rerun the test program and ensure that nothing was logged this time.

  [Regression Potential]

  The kernel patches received a lot of review between Kees and some
  others interested in improved seccomp logging. I authored the patches
  and feel comfortable/confident with my backported versions. They do
  not change the behavior of seccomp logging by default but offer ways
  applications to opt into more logging and, on the flipside, ways for
  the administrator to quite any additional logging.

To manage notifications about this bug go to:
https://bugs.launchpad.net/snappy/+bug/1721676/+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 1720660] Re: linux 4.13.0-13.14 ADT test failure with linux 4.13.0-13.14

[Seth Forshee]

Looks like there's a typo, s/assertEqaul/assertEqual/.

Traceback (most recent call last):
File "./test-kernel-security.py", line 675, in 
test_072_config_security_apparmor
  self.assertEqaul(self._get_config(default_apparmor_option), 'y')
  AttributeError: 'KernelSecurityTest' object has no attribute 'assertEqaul'

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

Title:
  linux 4.13.0-13.14 ADT test failure with linux 4.13.0-13.14

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Testing failed on:
  amd64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-artful-canonical-kernel-team-bootstrap/artful/amd64/l/linux/20170930_151719_8c658@/log.gz
  i386: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-artful-canonical-kernel-team-bootstrap/artful/i386/l/linux/20170930_220543_8c658@/log.gz
  ppc64el: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-artful-canonical-kernel-team-bootstrap/artful/ppc64el/l/linux/20170930_164802_8c658@/log.gz

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1720660/+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 1567597] Re: implement 'complain mode' in seccomp for developer mode with snaps

[Tyler Hicks]

** Description changed:

  A requirement for snappy is that a snap may be placed in developer mode
  which will put the security sandbox in complain mode such that
  violations against policy are logged, but permitted. In this manner
  learning tools can be written to parse the logs, etc and make developing
  on snappy easier.
  
  Unfortunately with seccomp only SCMP_ACT_KILL logs to dmesg and while we
  can set complain mode to permit all calls, they are not logged at this
  time. I've discussed this with upstream and we are working together on
  the approach. This may require a kernel patch and an update to
  libseccomp, to filing this bug for now as a placeholder and we'll add
  other tasks as necessary.
  
  UPDATE: ubuntu-core-launcher now supports the '@complain' directive that
  is a synonym for '@unrestricted' so people can at least turn on
  developer mode and not be blocked by seccomp. Proper complain mode for
  seccomp needs to still be implemented (this bug).
  
  [Impact]
  
  Snapd needs a way to log seccomp actions without blocking any syscalls
  in order to have a more useful complain mode. Such functionality has
  been acked upstream and patches are on their way into the Linux 4.14
  kernel (backported to 4.12.0-13.14 in artful).
  
  The corresponding libseccomp changes are still undergoing review
  (https://github.com/seccomp/libseccomp/pull/92). The pull request adds a
  number of new symbols and probably isn't appropriate to backport until
  upstream has acked the pull request. However, only a small part of that
  larger pull request is needed by snapd and that change can be safely
  backported since the only added symbol, the SCMP_ACT_LOG macro, must
  match the SECCOMP_RET_LOG macro that has already been approved and
  merged in the upstream Linux kernel.
  
  [libseccomp Test Case]
  
  A large number of tests are ran as part of the libseccomp build.
  However, the "live" tests which test libseccomp with actual kernel
  enforcement are not ran at that time. They can be manually exercised to
  help catch any regressions. Note that on Artful, there's an existing
  test failure (20-live-basic_die%%002-1):
  
  $ sudo apt build-dep -y libseccomp
  $ sudo apt install -y cython
  $ apt source libseccomp
  $ cd libseccomp-*
  $ autoreconf -ivf && ./configure --enable-python && make check-build
  $ (cd tests && ./regression -T live)
  
  All tests should pass on zesty (12 tests) and xenial (10 tests). On artful, 
you'll see one pre-existing failure:
  ...
  Test 20-live-basic_die%%002-1 result:   FAILURE 20-live-basic_die TRAP 
rc=159
  ...
  Regression Test Summary
   tests run: 12
   tests skipped: 0
   tests passed: 11
   tests failed: 1
   tests errored: 0
  
  
  
  
  Now we can build and run a small test program to test the SCMP_ACT_LOG
  action in the way that snapd wants to use it for developer mode:
  
  $ sudo apt install -y libseccomp-dev
  $ gcc -o lp1567597-test lp1567597-test.c -lseccomp
  $ ./lp1567597-test
  
  With a kernel that contains the logging patches and an updated
  libseccomp, the exit code should be 0 and you should have an entry in
  the system log that looks like this:
  
  audit: type=1326 audit(1505859630.994:69): auid=1000 uid=1000 gid=1000
  ses=2 pid=18451 comm="lp1567597-test" exe="/home/tyhicks/lp1567597-test"
  sig=0 arch=c03e syscall=2 compat=0 ip=0x7f547352c5c0 code=0x7ffc
  
  If you have an updated libseccomp with an old kernel, you'll see that
  seccomp_init() fails due to the added compatibility check inside of
  libseccomp determines that the kernel doesn't have proper support for
  the new log action:
  
  $ ./lp1567597-test
  ERROR: seccomp_init: Invalid argument
  
  [Linux Kernel Test Case]
  
  All of the libseccomp test cases apply here.
  
  
  
  Running the seccomp kernel selftests is also a great to exercise seccomp
  and the kernel patch set proposed for the SRU includes additional
  seccomp selftests. To build, enter into the root of the kernel source
  tree and build the seccomp test binary:
  
  $ make -C tools/testing/selftests TARGETS=seccomp
  
  Now you can execute tools/testing/selftests/seccomp/seccomp_bpf or even
  copy it to a test machine and run it there. On Xenial, 54/54 tests
  should pass and 58/58 should pass on Zesty.
  
+ 
+ 
+ Now we can run a single test to verify that SECCOMP_RET_LOG is logged
+ when the seccomp BPF evaluates to that action. First, verify that "log"
+ is listed in the actions_logged sysctl:
+ 
+ $ cat /proc/sys/kernel/seccomp/actions_logged
+ kill trap errno trace log
+ 
+ Now, build and run the test program:
+ 
+ $ gcc -o lp1567597-kernel-test lp1567597-kernel-test.c
+ $ ./1567597-kernel-test
+ SUCCESS!
+ 
+ It should have generated a message like this in /var/log/syslog:
+ 
+ audit: type=1326 audit(1507263417.752:60): auid=1000 uid=1000 

Re: [Kernel-packages] [Bug 1719945] Re: Silently fails in Wayland session

[Chris Halse Rogers]

It's certainly possible to log out, log in to an Xorg session, and then
log out again/reboot to switch to NVIDIA. *If* you know that's what you
need to do.

Since nvidia-settings silently fails *and* we default to Wayland if
possible users who don't know this is what you need to do will find it
very difficult to switch back from Intel.

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

Title:
  Silently fails in Wayland session

Status in nvidia-settings package in Ubuntu:
  Confirmed

Bug description:
  I've got an nvidia/intel hybrid laptop. In a Wayland session nvidia-
  settings fails silently when started from the shell. When started from
  a terminal, it prints:

  ERROR: Unable to load info from any available system

  and then quits.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: nvidia-settings 367.35-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1
  Uname: Linux 4.13.0-11-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Wed Sep 27 11:49:57 2017
  InstallationDate: Installed on 2017-09-20 (7 days ago)
  InstallationMedia: Ubuntu-GNOME 17.10 "Artful Aardvark" - Alpha amd64 
(20170919)
  SourcePackage: nvidia-settings
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-settings/+bug/1719945/+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 1567597] Re: implement 'complain mode' in seccomp for developer mode with snaps

[Tyler Hicks]

** Description changed:

  A requirement for snappy is that a snap may be placed in developer mode
  which will put the security sandbox in complain mode such that
  violations against policy are logged, but permitted. In this manner
  learning tools can be written to parse the logs, etc and make developing
  on snappy easier.
  
  Unfortunately with seccomp only SCMP_ACT_KILL logs to dmesg and while we
  can set complain mode to permit all calls, they are not logged at this
  time. I've discussed this with upstream and we are working together on
  the approach. This may require a kernel patch and an update to
  libseccomp, to filing this bug for now as a placeholder and we'll add
  other tasks as necessary.
  
  UPDATE: ubuntu-core-launcher now supports the '@complain' directive that
  is a synonym for '@unrestricted' so people can at least turn on
  developer mode and not be blocked by seccomp. Proper complain mode for
  seccomp needs to still be implemented (this bug).
  
  [Impact]
  
  Snapd needs a way to log seccomp actions without blocking any syscalls
  in order to have a more useful complain mode. Such functionality has
  been acked upstream and patches are on their way into the Linux 4.14
  kernel (backported to 4.12.0-13.14 in artful).
  
  The corresponding libseccomp changes are still undergoing review
  (https://github.com/seccomp/libseccomp/pull/92). The pull request adds a
  number of new symbols and probably isn't appropriate to backport until
  upstream has acked the pull request. However, only a small part of that
  larger pull request is needed by snapd and that change can be safely
  backported since the only added symbol, the SCMP_ACT_LOG macro, must
  match the SECCOMP_RET_LOG macro that has already been approved and
  merged in the upstream Linux kernel.
  
- [Test Case]
+ [libseccomp Test Case]
  
  A large number of tests are ran as part of the libseccomp build.
  However, the "live" tests which test libseccomp with actual kernel
  enforcement are not ran at that time. They can be manually exercised to
  help catch any regressions. Note that on Artful, there's an existing
  test failure (20-live-basic_die%%002-1):
  
  $ sudo apt build-dep -y libseccomp
  $ sudo apt install -y cython
  $ apt source libseccomp
  $ cd libseccomp-*
  $ autoreconf -ivf && ./configure --enable-python && make check-build
  $ (cd tests && ./regression -T live)
  
  All tests should pass on zesty (12 tests) and xenial (10 tests). On artful, 
you'll see one pre-existing failure:
  ...
  Test 20-live-basic_die%%002-1 result:   FAILURE 20-live-basic_die TRAP 
rc=159
  ...
  Regression Test Summary
   tests run: 12
   tests skipped: 0
   tests passed: 11
   tests failed: 1
   tests errored: 0
  
  
+ 
+ 
  Now we can build and run a small test program to test the SCMP_ACT_LOG
  action in the way that snapd wants to use it for developer mode:
  
  $ sudo apt install -y libseccomp-dev
  $ gcc -o lp1567597-test lp1567597-test.c -lseccomp
  $ ./lp1567597-test
  
  With a kernel that contains the logging patches and an updated
  libseccomp, the exit code should be 0 and you should have an entry in
  the system log that looks like this:
  
  audit: type=1326 audit(1505859630.994:69): auid=1000 uid=1000 gid=1000
  ses=2 pid=18451 comm="lp1567597-test" exe="/home/tyhicks/lp1567597-test"
  sig=0 arch=c03e syscall=2 compat=0 ip=0x7f547352c5c0 code=0x7ffc
  
  If you have an updated libseccomp with an old kernel, you'll see that
  seccomp_init() fails due to the added compatibility check inside of
  libseccomp determines that the kernel doesn't have proper support for
  the new log action:
  
  $ ./lp1567597-test
  ERROR: seccomp_init: Invalid argument
  
+ [Linux Kernel Test Case]
+ 
+ All of the libseccomp test cases apply here.
+ 
+ 
+ 
+ Running the seccomp kernel selftests is also a great to exercise seccomp
+ and the kernel patch set proposed for the SRU includes additional
+ seccomp selftests. To build, enter into the root of the kernel source
+ tree and build the seccomp test binary:
+ 
+ $ make -C tools/testing/selftests TARGETS=seccomp
+ 
+ Now you can execute tools/testing/selftests/seccomp/seccomp_bpf or even
+ copy it to a test machine and run it there. On Xenial, 54/54 tests
+ should pass and 58/58 should pass on Zesty.
+ 
  [Regression Potential]
  
  Relatively small since the core logic is in the kernel and we're only
  exposing the new action through libseccomp. The changes include smarts
  to query the kernel to see if the action is available in the kernel.
  Calling applications will not be able to use the action on older kernels
  that don't support it.

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

Title:
  implement 'complain mode' in seccomp for 

[Kernel-packages] [Bug 1721676] Re: implement errno action logging in seccomp for strict mode with snaps

[Tyler Hicks]

** Description changed:

  A requirement for snappy is that security sandbox violations against
  policy are logged. In this manner learning tools can be written to parse
  the logs, etc and make developing on snappy easier.
  
  The current default seccomp action, in strict mode. is to kill the
  snap's thread that violated the policy but this is unfriendly to the
  developer and to the user. The desired action is to block the illegal
  system call and return an error with errno set to EPERM. However,
  seccomp does not emit log events when it takes that action. Seccomp
  should be updated to emit log events when taking the SECCOMP_RET_ERRNO
  action and then snappy can switch to the using that action when blocking
  illegal system calls.
  
  [Impact]
  
  Snapd needs a way to log SECCOMP_RET_ERRNO seccomp actions in order to
  have a more friendly strict mode. Such functionality has been merged
  upstream into 4.14-rc2.
  
  No libseccomp changes are needed at this time since snap-confine loads
  the BPF filter directly into the kernel without using libseccomp.
  
  [Test Case]
  
  Running the libseccomp "live" tests will exercise the kernel's seccomp
  enforcement and help to help catch any regressions. Note that on Artful,
  there's an existing test failure (20-live-basic_die%%002-1):
  
  $ sudo apt build-dep -y libseccomp
  $ sudo apt install -y cython
  $ apt source libseccomp
  $ cd libseccomp-*
  $ autoreconf -ivf && ./configure --enable-python && make check-build
  $ (cd tests && ./regression -T live)
  
  All tests should pass on zesty (12 tests) and xenial (10 tests). On artful, 
you'll see one pre-existing failure:
  ...
  Test 20-live-basic_die%%002-1 result: FAILURE 20-live-basic_die TRAP 
rc=159
  ...
  Regression Test Summary
   tests run: 12
   tests skipped: 0
   tests passed: 11
   tests failed: 1
   tests errored: 0
  
  
+ 
+ 
+ Running the seccomp kernel selftests is also a great to exercise seccomp
+ and the kernel patch set proposed for the SRU includes additional
+ seccomp selftests. To build, enter into the root of the kernel source
+ tree and build the seccomp test binary:
+ 
+ $ make -C tools/testing/selftests TARGETS=seccomp
+ 
+ Now you can execute tools/testing/selftests/seccomp/seccomp_bpf or even
+ copy it to a test machine and run it there. On Xenial, 54/54 tests
+ should pass and 58/58 should pass on Zesty.
+ 
+ 
+ 
  Now we can run a single test to verify that SECCOMP_RET_ERRNO is logged
  when the application opts into it. First, verify that "errno" is listed
  in the actions_logged sysctl:
  
- $ cat /proc/sys/kernel/seccomp/actions_logged 
+ $ cat /proc/sys/kernel/seccomp/actions_logged
  kill trap errno trace log
  
  Now, build and run the test program:
  
- $ gcc -o lp1721676-kernel-test lp1721676-kernel-test.c 
- $ ./lp1721676-kernel-test 
+ $ gcc -o lp1721676-kernel-test lp1721676-kernel-test.c
+ $ ./lp1721676-kernel-test
  SUCCESS: getpid() failed as expected: Operation not permitted
  
  It should have generated a message like this in /var/log/syslog:
  
  kernel: [79338.804966] audit: type=1326 audit(1507259221.875:27):
  auid=1000 uid=1000 gid=1000 ses=5 pid=3091 comm="lp1721676-kerne"
  exe="/home/tyhicks/lp1721676-kernel-test" sig=0 arch=c03e syscall=39
  compat=0 ip=0x7fb91829c499 code=0x5
  
  Disable errno logging in the sysctl:
  
  $ echo kill trap trace log | sudo tee /proc/sys/kernel/seccomp/actions_logged
  kill trap trace log
  
  Rerun the test program and ensure that nothing was logged this time.
  
  [Regression Potential]
  
  The kernel patches received a lot of review between Kees and some others
  interested in improved seccomp logging. I authored the patches and feel
  comfortable/confident with my backported versions. They do not change
  the behavior of seccomp logging by default but offer ways applications
  to opt into more logging and, on the flipside, ways for the
  administrator to quite any additional logging.

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

Title:
  implement errno action logging in seccomp for strict mode with snaps

Status in Snappy:
  In Progress
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  In Progress
Status in linux source package in Zesty:
  In Progress
Status in linux source package in Artful:
  Fix Released

Bug description:
  A requirement for snappy is that security sandbox violations against
  policy are logged. In this manner learning tools can be written to
  parse the logs, etc and make developing on snappy easier.

  The current default seccomp action, in strict mode. is to kill the
  snap's thread that violated the policy but this is unfriendly to the
  developer and to the user. The desired action is 

[Kernel-packages] [Bug 1721394] Re: Cannot open nvidia-settings on pc with a hybrid device (or use prime-select), missing python

[Doug McMahon]

Ok, fresh install today's image
1. The manifest say python-minimal is included but it's not installed, 
$ apt-cache policy python-minimal
python-minimal:
  Installed: (none)
  Candidate: 2.7.14-2ubuntu1
  Version table:
 2.7.14-2ubuntu1 500
500 http://us.archive.ubuntu.com/ubuntu artful/main amd64 Packages

2. Also on the manifest but not installed are python2.7
python2.7-minimal

3. Installing nvidia-384 goes fine. If opening nvidia-settings after
install but *before* rebooting it actually opens.

4. After rebooting it fails to open as noted in the bug report description.
5. Installing python-minimal or python fixes this or maybe they just need to 
use python3

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

Title:
  Cannot open nvidia-settings on pc with a hybrid device (or use prime-
  select), missing python

Status in nvidia-prime package in Ubuntu:
  New
Status in nvidia-settings package in Ubuntu:
  New

Bug description:
  You would see -
  $ nvidia-settings
  ** Message: PRIME: Requires offloading
  ** Message: PRIME: is it supported? yes

  ** (nvidia-settings:1848): ERROR **: PRIME error: Failed to execute child 
process “/usr/bin/prime-select” (No such file or directory)
  Trace/breakpoint trap

  Additionally if trying to run prime-select you'd see -
  sudo: unable to execute /usr/bin/prime-select: No such file or directory

  One would need to go
   python3 /usr/bin/prime-select intel

  This is because the python package has been removed from image & isn't
  installed by either nvidia-settings or nvidia-prime.

  Please adjust this packages to either use python3 or dep to python

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: nvidia-settings 367.35-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Oct  4 17:16:44 2017
  InstallationDate: Installed on 2017-10-04 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20170929)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: nvidia-settings
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1721394/+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 1716258] Re: Keyboard input temporarily ignored when typing root encryption password

[Douglas H. Silva]

Tested kernel 4.13.4-200.fc26.x86_64, and is still reproducible. Arch is
free from this bug, but Fedora and Debian are not.

** Tags removed: kernel-fixed-upstream

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

Title:
  Keyboard input temporarily ignored when typing root encryption
  password

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Symptoms:

  The computer begins its boot process, then the root decryption
  password prompt appears (via Plymouth) and I start typing. The first
  letters are caught, but some letters are not captured. It's as if the
  keyboard shut down during a few seconds and then returned, and I could
  type the whole password properly.

  Things I tried:

  - Typing the password blindly (just inputting the entire password and hitting 
Enter without worrying about missing characters) but it rejected the password 
as incorrect.
  - Typing decryption password without Plymouth (this is not a Plymouth bug).

  
  This affects Debian 9 (didn't affect Debian 8), Fedora, Arch Linux and 
possibly others. It cannot be reproduced with Ubuntu or other distributions 
with old packages. Some component introduced this problem recently.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1716258/+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 1716301] Re: wifi driver: mt7601u not work on 16.04

[Kai-Heng Feng]

You can use modprobe conf to do that:

$ sudo -s
# echo "options mt7601u timeout=1000" >> /etc/modprobe.d/mt7601u.conf

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

Title:
  wifi driver: mt7601u not work on 16.04

Status in linux package in Ubuntu:
  Confirmed
Status in usb-modeswitch-data package in Ubuntu:
  New

Bug description:
  In the beginning, when the adapter is pluged in, it's mounted as a disk 
including driver files for Windows, and
  $> lsusb
  Bus 003 Device 010: ID 148f:2878 Ralink Technology, Corp.

  after eject the disk,
  $> lsusb
  Bus 003 Device 011: ID 148f:7601 Ralink Technology, Corp. MT7601U Wireless 
Adapter

  I tried following 3 drivers:
  1) the default mt7601u included in the kernel: 4.4.0-91-generic
  after eject the disk,
  $> lsmod|grep mt
  mt7601u 102400 0
  mac80211 737280 1 mt7601u
  cfg80211 565248 2 mac80211,mt7601u
  binfmt_misc 20480 1
  $> modinfo mt7601u
  filename: 
/lib/modules/4.4.0-91-generic/kernel/drivers/net/wireless/mediatek/mt7601u/mt7601u.ko
  srcversion: E8B632D369E0C2A9F1CF7D8
  alias: usb:v7392p7710d*dc*dsc*dp*ic*isc*ip*in*
  ..
  depends: mac80211,cfg80211
  intree: Y
  vermagic: 4.4.0-91-generic SMP mod_unload modversions

  $> dmesg
  // begin
  [ 4581.094119] usb 3-4: USB disconnect, device number 6
  [ 4584.872751] usb 3-4: new high-speed USB device number 7 using xhci_hcd
  [ 4585.001408] usb 3-4: New USB device found, idVendor=148f, idProduct=2878
  [ 4585.001413] usb 3-4: New USB device strings: Mfr=1, Product=2, 
SerialNumber=0
  [ 4585.001416] usb 3-4: Product: Љ
  [ 4585.001418] usb 3-4: Manufacturer: Љ
  [ 4585.001753] usb-storage 3-4:1.0: USB Mass Storage device detected
  [ 4585.001873] scsi host6: usb-storage 3-4:1.0
  [ 4586.001122] scsi 6:0:0:0: CD-ROM MediaTek Flash autorun 0.01 PQ: 0 ANSI: 0 
CCS
  [ 4586.001978] sr 6:0:0:0: [sr0] scsi3-mmc drive: 52x/52x cd/rw xa/form2 cdda 
tray
  [ 4586.002529] sr 6:0:0:0: Attached scsi CD-ROM sr0
  [ 4586.002716] sr 6:0:0:0: Attached scsi generic sg1 type 5
  [ 4619.658385] ISO 9660 Extensions: Microsoft Joliet Level 3
  [ 4619.691737] ISOFS: changing to secondary root
  [ 4691.563347] usb 3-4: USB disconnect, device number 7
  [ 4693.638315] usb 3-4: new high-speed USB device number 8 using xhci_hcd
  [ 4693.766896] usb 3-4: New USB device found, idVendor=148f, idProduct=2878
  [ 4693.766901] usb 3-4: New USB device strings: Mfr=1, Product=2, 
SerialNumber=0
  [ 4693.766903] usb 3-4: Product: Љ
  [ 4693.766905] usb 3-4: Manufacturer: Љ
  [ 4693.767338] usb-storage 3-4:1.0: USB Mass Storage device detected
  [ 4693.768063] scsi host7: usb-storage 3-4:1.0
  [ 4694.766737] scsi 7:0:0:0: CD-ROM MediaTek Flash autorun 0.01 PQ: 0 ANSI: 0 
CCS
  [ 4694.767423] sr 7:0:0:0: [sr0] scsi3-mmc drive: 52x/52x cd/rw xa/form2 cdda 
tray
  [ 4694.767908] sr 7:0:0:0: Attached scsi CD-ROM sr0
  [ 4694.768147] sr 7:0:0:0: Attached scsi generic sg1 type 5
  [ 4728.418255] ISO 9660 Extensions: Microsoft Joliet Level 3
  [ 4728.427856] ISOFS: changing to secondary root
  [ 4733.824182] sr 7:0:0:0: [sr0] tag#0 FAILED Result: hostbyte=DID_ERROR 
driverbyte=DRIVER_OK
  [ 4733.824190] sr 7:0:0:0: [sr0] tag#0 CDB: Start/Stop Unit 1b 00 00 00 02 00
  [ 4733.824218] usb 3-4: USB disconnect, device number 8
  [ 4733.824281] sr 7:0:0:0: [sr0] tag#0 FAILED Result: hostbyte=DID_ERROR 
driverbyte=DRIVER_OK
  [ 4733.824291] sr 7:0:0:0: [sr0] tag#0 CDB: Prevent/Allow Medium Removal 1e 
00 00 00 00 00
  [ 4734.099901] usb 3-4: new high-speed USB device number 9 using xhci_hcd
  [ 4734.238749] usb 3-4: New USB device found, idVendor=148f, idProduct=7601
  [ 4734.238754] usb 3-4: New USB device strings: Mfr=1, Product=2, 
SerialNumber=3
  [ 4734.238757] usb 3-4: Product: 802.11 n WLAN
  [ 4734.238772] usb 3-4: Manufacturer: MediaTek
  [ 4734.238775] usb 3-4: SerialNumber: 1.0
  [ 4735.432096] usb 3-4: reset high-speed USB device number 9 using xhci_hcd
  [ 4735.562543] mt7601u 3-4:1.0: ASIC revision: 76010001 MAC revision: 76010500
  [ 4735.563089] mt7601u 3-4:1.0: Firmware Version: 0.1.00 Build: 7640 Build 
time: 201302052146
  [ 4739.011624] mt7601u 3-4:1.0: Vendor request req:07 off:09a8 failed:-110
  [ 4742.131399] mt7601u 3-4:1.0: Vendor request req:02 off:09a8 failed:-110
  [ 4745.251254] mt7601u 3-4:1.0: Vendor request req:07 off:0734 failed:-110
  [ 4748.371056] mt7601u 3-4:1.0: Vendor request req:42 off:0230 failed:-110
  [ 4751.490880] mt7601u 3-4:1.0: Vendor request req:07 off:0080 failed:-110
  [ 4754.610694] mt7601u 3-4:1.0: Vendor request req:02 off:0080 failed:-110
  [ 4757.730501] mt7601u 3-4:1.0: Vendor request req:02 off:0080 failed:-110
  [ 4757.730548] mt7601u: probe of 3-4:1.0 failed with error -110
  [ 4757.730870] usbcore: registered new interface driver mt7601u
  // end 

  $> sudo ifconfig -a // do not 

[Kernel-packages] [Bug 1718159] Re: linux: 3.13.0-133.182 -proposed tracker

[Taihsiang Ho]

Hardware Certification have begun testing this -proposed kernel.

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

** Changed in: kernel-sru-workflow/certification-testing
 Assignee: Canonical Hardware Certification (canonical-hw-cert) => 
Taihsiang Ho (taihsiangho)

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

Title:
  linux: 3.13.0-133.182 -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:
  In Progress
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 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 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

  backports: 1718161
  derivatives:
  -- swm properties --
  boot-testing-requested: true
  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/1718159/+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 1711251] Re: vhost guest network randomly drops under stress (kvm)

[Po-Hsu Lin]

Hello IBM,

Do you have any update on this test result?
Thanks!

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

Title:
  vhost guest network randomly drops under stress (kvm)

Status in The Ubuntu-power-systems project:
  Fix Committed
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Zesty:
  Fix Committed

Bug description:
  == SRU Justification ==

  A vhost performance patch was introduced in the 4.10 kernel upstream,
  and is currently included in the Zesty 4.10 kernel:

  commit 809ecb9bca6a9424ccd392d67e368160f8b76c92
  Author: Jason Wang 
  Date:   Mon Dec 12 14:46:49 2016 +0800

  vhost: cache used event for better performance

  --

  However I recently hit a functional issue linked to this patch which
  would cause random guests to lose their network connection under
  stress.  This is not architecture specific and more likely to be hit
  with high network stress (i.e. lots of uperf instances).

  The patch author has now reverted this patch upstream:
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/vhost?id=8d65843c44269c21e95c98090d9bb4848d473853

  which reads:
  "
  Revert "vhost: cache used event for better performance"
  This reverts commit 809ecb9bca6a9424ccd392d67e368160f8b76c92. Since it
  was reported to break vhost_net. We want to cache used event and use
  it to check for notification. The assumption was that guest won't move
  the event idx back, but this could happen in fact when 16 bit index
  wraps around after 64K entries.

  Signed-off-by: Jason Wang 
  Acked-by: Michael S. Tsirkin 
  Signed-off-by: David S. Miller 
  "

  I am requesting this patch to revert the problematic one be pulled
  into Ubuntu Zesty (anything 4.10+).

  ---uname output---
  Linux p82qvirt 4.10.0-32-generic #36~16.04.1-Ubuntu SMP Wed Aug 9 09:19:19 
UTC 2017 ppc64le ppc64le ppc64le GNU/Linux

  Machine Type = 8247-22L

  ---Steps to Reproduce---
   I can recreate the scenario with the following setup:
   - on a 20core host, start 20 1core VMs
   - I have a single linux bridge assigned to all guests using virtio
   - start a uperf benchmark between each guest pair (10 total) using a high 
number of uperf nprocs (32)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1711251/+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 1721676] Re: implement errno action logging in seccomp for strict mode with snaps

[Tyler Hicks]

** Description changed:

  A requirement for snappy is that security sandbox violations against
  policy are logged. In this manner learning tools can be written to parse
  the logs, etc and make developing on snappy easier.
  
  The current default seccomp action, in strict mode. is to kill the
  snap's thread that violated the policy but this is unfriendly to the
  developer and to the user. The desired action is to block the illegal
  system call and return an error with errno set to EPERM. However,
  seccomp does not emit log events when it takes that action. Seccomp
  should be updated to emit log events when taking the SECCOMP_RET_ERRNO
  action and then snappy can switch to the using that action when blocking
  illegal system calls.
  
  [Impact]
  
  Snapd needs a way to log SECCOMP_RET_ERRNO seccomp actions in order to
  have a more friendly strict mode. Such functionality has been merged
  upstream into 4.14-rc2.
  
  No libseccomp changes are needed at this time since snap-confine loads
  the BPF filter directly into the kernel without using libseccomp.
  
  [Test Case]
  
  Running the libseccomp "live" tests will exercise the kernel's seccomp
  enforcement and help to help catch any regressions. Note that on Artful,
  there's an existing test failure (20-live-basic_die%%002-1):
  
  $ sudo apt build-dep -y libseccomp
  $ sudo apt install -y cython
  $ apt source libseccomp
  $ cd libseccomp-*
  $ autoreconf -ivf && ./configure --enable-python && make check-build
  $ (cd tests && ./regression -T live)
  
  All tests should pass on zesty (12 tests) and xenial (10 tests). On artful, 
you'll see one pre-existing failure:
  ...
  Test 20-live-basic_die%%002-1 result: FAILURE 20-live-basic_die TRAP 
rc=159
  ...
  Regression Test Summary
-  tests run: 12
-  tests skipped: 0
-  tests passed: 11
-  tests failed: 1
-  tests errored: 0
+  tests run: 12
+  tests skipped: 0
+  tests passed: 11
+  tests failed: 1
+  tests errored: 0
  
+ 
+ Now we can run a single test to verify that SECCOMP_RET_ERRNO is logged
+ when the application opts into it. First, verify that "errno" is listed
+ in the actions_logged sysctl:
+ 
+ $ cat /proc/sys/kernel/seccomp/actions_logged 
+ kill trap errno trace log
+ 
+ Now, build and run the test program:
+ 
+ $ gcc -o lp1721676-kernel-test lp1721676-kernel-test.c 
+ $ ./lp1721676-kernel-test 
+ SUCCESS: getpid() failed as expected: Operation not permitted
+ 
+ It should have generated a message like this in /var/log/syslog:
+ 
+ kernel: [79338.804966] audit: type=1326 audit(1507259221.875:27):
+ auid=1000 uid=1000 gid=1000 ses=5 pid=3091 comm="lp1721676-kerne"
+ exe="/home/tyhicks/lp1721676-kernel-test" sig=0 arch=c03e syscall=39
+ compat=0 ip=0x7fb91829c499 code=0x5
+ 
+ Disable errno logging in the sysctl:
+ 
+ $ echo kill trap trace log | sudo tee /proc/sys/kernel/seccomp/actions_logged
+ kill trap trace log
+ 
+ Rerun the test program and ensure that nothing was logged this time.
  
  [Regression Potential]
  
  The kernel patches received a lot of review between Kees and some others
  interested in improved seccomp logging. I authored the patches and feel
  comfortable/confident with my backported versions. They do not change
  the behavior of seccomp logging by default but offer ways applications
  to opt into more logging and, on the flipside, ways for the
  administrator to quite any additional logging.

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

Title:
  implement errno action logging in seccomp for strict mode with snaps

Status in Snappy:
  In Progress
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  In Progress
Status in linux source package in Zesty:
  In Progress
Status in linux source package in Artful:
  Fix Released

Bug description:
  A requirement for snappy is that security sandbox violations against
  policy are logged. In this manner learning tools can be written to
  parse the logs, etc and make developing on snappy easier.

  The current default seccomp action, in strict mode. is to kill the
  snap's thread that violated the policy but this is unfriendly to the
  developer and to the user. The desired action is to block the illegal
  system call and return an error with errno set to EPERM. However,
  seccomp does not emit log events when it takes that action. Seccomp
  should be updated to emit log events when taking the SECCOMP_RET_ERRNO
  action and then snappy can switch to the using that action when
  blocking illegal system calls.

  [Impact]

  Snapd needs a way to log SECCOMP_RET_ERRNO seccomp actions in order to
  have a more friendly strict mode. Such functionality has been merged
  upstream into 4.14-rc2.

  No libseccomp changes are needed at this time since snap-confine loads
  the BPF filter directly 

[Kernel-packages] [Bug 1708852] Re: Touchpad not detected

[Po-Hsu Lin]

Hello Nase and Raju,

I would like to encourage you guys to open a new bug report of your own, as 
it's unclear if your system is having the same hardware.
Please run "ubuntu-bug linux" command in a terminal (ctrl + alt + t) to do so.

Thank you.

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

Title:
  Touchpad not detected

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

Bug description:
  SRU Justifications:

  [Impact] 
  Touchpad on Lenovo ideapad 320-14IKB does not work.

  [Test Case]
  After adding the ID to the elan_i2c driver, the touchpad works.

  
  [Regression Potential]
  Very low.
  It only adds device ID to the driver, no functional changes.

  ---

  The touchpad is not working in any linux distribution, but works in
  Windows. It is not getting detected. Seems like a kernel bug.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-30-generic 4.10.0-30.34
  ProcVersionSignature: Ubuntu 4.10.0-30.34-generic 4.10.17
  Uname: Linux 4.10.0-30-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  matheus1504 F pulseaudio
  CurrentDesktop: GNOME
  Date: Sat Aug  5 12:58:21 2017
  InstallationDate: Installed on 2017-08-05 (0 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 5986:1127 Acer, Inc
   Bus 001 Device 003: ID 0cf3:e500 Atheros Communications, Inc.
   Bus 001 Device 002: ID 0101:0007
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 80YF
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-30-generic.efi.signed 
root=UUID=d7c89f65-c9a7-4e7f-9bce-ed58751f0619 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-30-generic N/A
   linux-backports-modules-4.10.0-30-generic  N/A
   linux-firmware 1.164.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/22/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 4WCN16WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: Cairo 4A
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40679 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad 320-14IKB
  dmi.modalias: 
dmi:bvnLENOVO:bvr4WCN16WW:bd02/22/2017:svnLENOVO:pn80YF:pvrLenovoideapad320-14IKB:rvnLENOVO:rnCairo4A:rvrSDK0J40679WIN:cvnLENOVO:ct10:cvrLenovoideapad320-14IKB:
  dmi.product.name: 80YF
  dmi.product.version: Lenovo ideapad 320-14IKB
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1708852/+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 1718143] Re: linux: 4.10.0-36.40 -proposed tracker

[Daniel Manrique]

Hardware Certification have completed testing this -proposed kernel. No
regressions were observed, results are available here:
http://people.canonical.com/~hwcert/sru-testing/zesty/4.10.0-36.40
/zesty-proposed-published.html

** Tags added: certification-testing-passed

** Changed in: kernel-sru-workflow/certification-testing
   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/1718143

Title:
  linux: 4.10.0-36.40 -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 upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Zesty:
  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: 1718145,1718146
  derivatives: 1718147
  -- swm properties --
  boot-testing-requested: true
  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/1718143/+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 1718149] Re: linux: 4.4.0-97.120 -proposed tracker

[Taihsiang Ho]

Hardware Certification have completed testing this -proposed kernel. No
regressions were observed, results are available here:
http://people.canonical.com/~hwcert/sru-testing/xenial/4.4.0-97.120
/xenial-proposed-published.html

** Tags added: certification-testing-passed

** Changed in: kernel-sru-workflow/certification-testing
   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/1718149

Title:
  linux: 4.4.0-97.120 -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 upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
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: 1718150,1718151
  derivatives: 1718153,1718154,1718155,1718156,1718157
  -- swm properties --
  boot-testing-requested: true
  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/1718149/+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 1696049] Comment bridged from LTC Bugzilla

[bugproxy]

--- Comment From hasri...@in.ibm.com 2017-10-05 22:37 EDT---
(In reply to comment #63)
> The reverse bisect reported the following commit as the fix:
>
> 8affebe ("xfs: fix off-by-one on max nr_pages in
> xfs_find_get_desired_pgoff()")
>
> I built a 17.04(Zesty) test kernel with a pick of this commit.  The test
> kernel can be downloaded from:
>
> http://kernel.ubuntu.com/~jsalisbury/lp1696049/
>
> Can you test this kernel and see if it resolves this bug?

The kernel provided resolves the issue.

Thanks,
Harish

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

Title:
  xfstest sanity checks on seek operations fails

Status in The Ubuntu-power-systems project:
  In Progress
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Zesty:
  In Progress
Status in linux source package in Artful:
  Fix Released

Bug description:
  == Comment: #0 - Harish Sriram 
  Issue:
  --
  xfstest fails with sanity checks on seek operations

  # uname -a
  Linux ltc-tuleta12 4.10.0-21-generic #23~16.04.1-Ubuntu SMP Tue May 2 
12:54:57 UTC 2017 ppc64le ppc64le ppc64le GNU/Linux

  Steps to reproduce:
  
  1. Create a loop device with xfs filesystem
  2. git clone git://git.kernel.org/pub/scm/fs/xfs/xfstests-dev.git; cd 
xfstests-dev
  3. make
  4. Create a local.config for running with created loop device
  5. Run xfstests-dev test  : ./check tests/generic/285 or ./check 
tests/generic/436

  The test 285 fails with following
  ...
  ...
  07. Test file with unwritten extents, only have dirty pages
  07.01 SEEK_HOLE expected 0 or 45056, got 0.   succ
  07.02 SEEK_HOLE expected 1 or 45056, got 1.   succ
  07.03 SEEK_DATA expected 40960 or 40960, got -1.  FAIL
  07.04 SEEK_DATA expected 40960 or 40960, got -1.  FAIL

  08. Test file with unwritten extents, only have unwritten pages
  08.01 SEEK_HOLE expected 0 or 45056, got 0.   succ
  08.02 SEEK_HOLE expected 1 or 45056, got 1.   succ
  08.03 SEEK_DATA expected 40960 or 40960, got -1.  FAIL
  08.04 SEEK_DATA expected 40960 or 40960, got -1.  FAIL

  The test 436 fails with 
  ...
  ...
  14. Test file with unwritten extents, small hole after pagevec dirty pages
  14.01 SEEK_HOLE expected 917504 or 4194304, got 3670016.  FAIL
  14.02 SEEK_HOLE expected 917504 or 4194304, got 3670016.  FAIL
  14.03 SEEK_HOLE expected 3670016 or 4194304, got 3670016. succ
  14.04 SEEK_DATA expected 0 or 0, got 0.   succ
  14.05 SEEK_DATA expected 1 or 1, got 1.   succ
  14.06 SEEK_DATA expected 2752512 or 2752512, got 2752512. succ

  seek sanity check failed!

  Full log is attached.

  == Comment: #6 - Harish Sriram

  commit 5375023ae1266553a7baa0845e82917d8803f48c
  Author: Jan Kara 
  Date:   Thu May 18 16:36:22 2017 -0700

  xfs: Fix missed holes in SEEK_HOLE implementation
  XFS SEEK_HOLE implementation could miss a hole in an unwritten extent as
  can be seen by the following command:
  
  xfs_io -c "falloc 0 256k" -c "pwrite 0 56k" -c "pwrite 128k 8k"
 -c "seek -h 0" file
  wrote 57344/57344 bytes at offset 0
  56 KiB, 14 ops; 0. sec (49.312 MiB/sec and 12623.9856 ops/sec)
  wrote 8192/8192 bytes at offset 131072
  8 KiB, 2 ops; 0. sec (70.383 MiB/sec and 18018.0180 ops/sec)
  Whence  Result
  HOLE139264
  
  Where we can see that hole at offset 56k was just ignored by SEEK_HOLE
  implementation. The bug is in xfs_find_get_desired_pgoff() which does
  not properly detect the case when pages are not contiguous.
  
  Fix the problem by properly detecting when found page has larger offset
  than expected.
  
  CC: sta...@vger.kernel.org
  Fixes: d126d43f631f996daeee5006714fed914be32368
  Signed-off-by: Jan Kara 
  Reviewed-by: Brian Foster 
  Reviewed-by: Darrick J. Wong 
  Signed-off-by: Darrick J. Wong 

  
  The above commit fixes the generic/436 test, but generic/285 still FAILS.

  The generic/285 failure is reproducible on most P8/P9 systems.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1696049/+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 1721676] Re: implement errno action logging in seccomp for strict mode with snaps

[Tyler Hicks]

The kernel patches for this feature have already been released in an
Artful kernel (4.12.0-13.14).

** Description changed:

  A requirement for snappy is that security sandbox violations against
  policy are logged. In this manner learning tools can be written to parse
  the logs, etc and make developing on snappy easier.
  
  The current default seccomp action, in strict mode. is to kill the
  snap's thread that violated the policy but this is unfriendly to the
  developer and to the user. The desired action is to block the illegal
  system call and return an error with errno set to EPERM. However,
  seccomp does not emit log events when it takes that action. Seccomp
  should be updated to emit log events when taking the SECCOMP_RET_ERRNO
  action and then snappy can switch to the using that action when blocking
  illegal system calls.
+ 
+ [Impact]
+ 
+ Snapd needs a way to log SECCOMP_RET_ERRNO seccomp actions in order to
+ have a more friendly strict mode. Such functionality has been merged
+ upstream into 4.14-rc2.
+ 
+ No libseccomp changes are needed at this time since snap-confine loads
+ the BPF filter directly into the kernel without using libseccomp.
+ 
+ [Test Case]
+ 
+ Running the libseccomp "live" tests will exercise the kernel's seccomp
+ enforcement and help to help catch any regressions. Note that on Artful,
+ there's an existing test failure (20-live-basic_die%%002-1):
+ 
+ $ sudo apt build-dep -y libseccomp
+ $ sudo apt install -y cython
+ $ apt source libseccomp
+ $ cd libseccomp-*
+ $ autoreconf -ivf && ./configure --enable-python && make check-build
+ $ (cd tests && ./regression -T live)
+ 
+ All tests should pass on zesty (12 tests) and xenial (10 tests). On artful, 
you'll see one pre-existing failure:
+ ...
+ Test 20-live-basic_die%%002-1 result: FAILURE 20-live-basic_die TRAP 
rc=159
+ ...
+ Regression Test Summary
+  tests run: 12
+  tests skipped: 0
+  tests passed: 11
+  tests failed: 1
+  tests errored: 0
+ 
+ 
+ [Regression Potential]
+ 
+ The kernel patches received a lot of review between Kees and some others
+ interested in improved seccomp logging. I authored the patches and feel
+ comfortable/confident with my backported versions. They do not change
+ the behavior of seccomp logging by default but offer ways applications
+ to opt into more logging and, on the flipside, ways for the
+ administrator to quite any additional logging.

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

Title:
  implement errno action logging in seccomp for strict mode with snaps

Status in Snappy:
  In Progress
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  In Progress
Status in linux source package in Zesty:
  In Progress
Status in linux source package in Artful:
  Fix Released

Bug description:
  A requirement for snappy is that security sandbox violations against
  policy are logged. In this manner learning tools can be written to
  parse the logs, etc and make developing on snappy easier.

  The current default seccomp action, in strict mode. is to kill the
  snap's thread that violated the policy but this is unfriendly to the
  developer and to the user. The desired action is to block the illegal
  system call and return an error with errno set to EPERM. However,
  seccomp does not emit log events when it takes that action. Seccomp
  should be updated to emit log events when taking the SECCOMP_RET_ERRNO
  action and then snappy can switch to the using that action when
  blocking illegal system calls.

  [Impact]

  Snapd needs a way to log SECCOMP_RET_ERRNO seccomp actions in order to
  have a more friendly strict mode. Such functionality has been merged
  upstream into 4.14-rc2.

  No libseccomp changes are needed at this time since snap-confine loads
  the BPF filter directly into the kernel without using libseccomp.

  [Test Case]

  Running the libseccomp "live" tests will exercise the kernel's seccomp
  enforcement and help to help catch any regressions. Note that on
  Artful, there's an existing test failure (20-live-
  basic_die%%002-1):

  $ sudo apt build-dep -y libseccomp
  $ sudo apt install -y cython
  $ apt source libseccomp
  $ cd libseccomp-*
  $ autoreconf -ivf && ./configure --enable-python && make check-build
  $ (cd tests && ./regression -T live)

  All tests should pass on zesty (12 tests) and xenial (10 tests). On artful, 
you'll see one pre-existing failure:
  ...
  Test 20-live-basic_die%%002-1 result: FAILURE 20-live-basic_die TRAP 
rc=159
  ...
  Regression Test Summary
   tests run: 12
   tests skipped: 0
   tests passed: 11
   tests failed: 1
   tests errored: 0
  

  [Regression Potential]

  The kernel patches received a lot of review between Kees and some
  others 

[Kernel-packages] [Bug 1721676] [NEW] implement errno action logging in seccomp for strict mode with snaps

[Tyler Hicks]

Public bug reported:

A requirement for snappy is that security sandbox violations against
policy are logged. In this manner learning tools can be written to parse
the logs, etc and make developing on snappy easier.

The current default seccomp action, in strict mode. is to kill the
snap's thread that violated the policy but this is unfriendly to the
developer and to the user. The desired action is to block the illegal
system call and return an error with errno set to EPERM. However,
seccomp does not emit log events when it takes that action. Seccomp
should be updated to emit log events when taking the SECCOMP_RET_ERRNO
action and then snappy can switch to the using that action when blocking
illegal system calls.

[Impact]

Snapd needs a way to log SECCOMP_RET_ERRNO seccomp actions in order to
have a more friendly strict mode. Such functionality has been merged
upstream into 4.14-rc2.

No libseccomp changes are needed at this time since snap-confine loads
the BPF filter directly into the kernel without using libseccomp.

[Test Case]

Running the libseccomp "live" tests will exercise the kernel's seccomp
enforcement and help to help catch any regressions. Note that on Artful,
there's an existing test failure (20-live-basic_die%%002-1):

$ sudo apt build-dep -y libseccomp
$ sudo apt install -y cython
$ apt source libseccomp
$ cd libseccomp-*
$ autoreconf -ivf && ./configure --enable-python && make check-build
$ (cd tests && ./regression -T live)

All tests should pass on zesty (12 tests) and xenial (10 tests). On artful, 
you'll see one pre-existing failure:
...
Test 20-live-basic_die%%002-1 result: FAILURE 20-live-basic_die TRAP rc=159
...
Regression Test Summary
 tests run: 12
 tests skipped: 0
 tests passed: 11
 tests failed: 1
 tests errored: 0


[Regression Potential]

The kernel patches received a lot of review between Kees and some others
interested in improved seccomp logging. I authored the patches and feel
comfortable/confident with my backported versions. They do not change
the behavior of seccomp logging by default but offer ways applications
to opt into more logging and, on the flipside, ways for the
administrator to quite any additional logging.

** Affects: snappy
 Importance: Medium
 Assignee: Tyler Hicks (tyhicks)
 Status: In Progress

** Affects: linux (Ubuntu)
 Importance: Undecided
 Assignee: Tyler Hicks (tyhicks)
 Status: Fix Released

** Affects: linux (Ubuntu Xenial)
 Importance: Undecided
 Assignee: Tyler Hicks (tyhicks)
 Status: In Progress

** Affects: linux (Ubuntu Zesty)
 Importance: Undecided
 Assignee: Tyler Hicks (tyhicks)
 Status: In Progress

** Affects: linux (Ubuntu Artful)
 Importance: Undecided
 Assignee: Tyler Hicks (tyhicks)
 Status: Fix Released

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

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

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

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

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

** Changed in: linux (Ubuntu Xenial)
 Assignee: (unassigned) => Tyler Hicks (tyhicks)

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

** Changed in: linux (Ubuntu Zesty)
 Assignee: (unassigned) => Tyler Hicks (tyhicks)

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

** Changed in: linux (Ubuntu Artful)
 Assignee: (unassigned) => Tyler Hicks (tyhicks)

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

Title:
  implement errno action logging in seccomp for strict mode with snaps

Status in Snappy:
  In Progress
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  In Progress
Status in linux source package in Zesty:
  In Progress
Status in linux source package in Artful:
  Fix Released

Bug description:
  A requirement for snappy is that security sandbox violations against
  policy are logged. In this manner learning tools can be written to
  parse the logs, etc and make developing on snappy easier.

  The current default seccomp action, in strict mode. is to kill the
  snap's thread that violated the policy but this is unfriendly to the
  developer and to the user. The desired action is to block the illegal
  system call and return an error with errno set to EPERM. However,
  seccomp does not emit log events when it takes that action. Seccomp
  should be updated to emit log events when taking the SECCOMP_RET_ERRNO
  action and then snappy can switch to the using that action when
  blocking illegal system calls.

  [Impact]

  Snapd needs a way to log SECCOMP_RET_ERRNO seccomp 

Re: [Kernel-packages] [Bug 1721394] Re: Cannot open nvidia-settings on pc with a hybrid device (or use prime-select), missing python

[Doug McMahon]

I wasn't really sure that it really needed the python package, it seems
toneed /usr/bin/python which should have been installed as it's provided by
the python-minimal package.
When nvidia-settings wouldn't start I just installed the python package
which brought in python-minimal, ect.

When I check the manifest for the current image python-minimal is listed.
Maybe I'll try a new install to make sure it is there after installing

On Oct 5, 2017 10:01 PM, "Jeremy Bicha"  wrote:

> Doug, if the package needs python, then it should be marked as a
> dependency.
>
> ** Changed in: nvidia-prime (Ubuntu)
>Status: Invalid => New
>
> ** Changed in: nvidia-settings (Ubuntu)
>Status: Invalid => New
>
> ** Tags added: rls-aa-incoming
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1721394
>
> Title:
>   Cannot open nvidia-settings on pc with a hybrid device (or use prime-
>   select), missing python
>
> Status in nvidia-prime package in Ubuntu:
>   New
> Status in nvidia-settings package in Ubuntu:
>   New
>
> Bug description:
>   You would see -
>   $ nvidia-settings
>   ** Message: PRIME: Requires offloading
>   ** Message: PRIME: is it supported? yes
>
>   ** (nvidia-settings:1848): ERROR **: PRIME error: Failed to execute
> child process “/usr/bin/prime-select” (No such file or directory)
>   Trace/breakpoint trap
>
>   Additionally if trying to run prime-select you'd see -
>   sudo: unable to execute /usr/bin/prime-select: No such file or directory
>
>   One would need to go
>python3 /usr/bin/prime-select intel
>
>   This is because the python package has been removed from image & isn't
>   installed by either nvidia-settings or nvidia-prime.
>
>   Please adjust this packages to either use python3 or dep to python
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 17.10
>   Package: nvidia-settings 367.35-0ubuntu1
>   ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
>   Uname: Linux 4.13.0-12-generic x86_64
>   NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
>   ApportVersion: 2.20.7-0ubuntu2
>   Architecture: amd64
>   CurrentDesktop: ubuntu:GNOME
>   Date: Wed Oct  4 17:16:44 2017
>   InstallationDate: Installed on 2017-10-04 (0 days ago)
>   InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20170929)
>   ProcEnviron:
>TERM=xterm-256color
>PATH=(custom, no user)
>XDG_RUNTIME_DIR=
>LANG=en_US.UTF-8
>SHELL=/bin/bash
>   SourcePackage: nvidia-settings
>   UpgradeStatus: No upgrade log present (probably fresh install)
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+
> bug/1721394/+subscriptions
>

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

Title:
  Cannot open nvidia-settings on pc with a hybrid device (or use prime-
  select), missing python

Status in nvidia-prime package in Ubuntu:
  New
Status in nvidia-settings package in Ubuntu:
  New

Bug description:
  You would see -
  $ nvidia-settings
  ** Message: PRIME: Requires offloading
  ** Message: PRIME: is it supported? yes

  ** (nvidia-settings:1848): ERROR **: PRIME error: Failed to execute child 
process “/usr/bin/prime-select” (No such file or directory)
  Trace/breakpoint trap

  Additionally if trying to run prime-select you'd see -
  sudo: unable to execute /usr/bin/prime-select: No such file or directory

  One would need to go
   python3 /usr/bin/prime-select intel

  This is because the python package has been removed from image & isn't
  installed by either nvidia-settings or nvidia-prime.

  Please adjust this packages to either use python3 or dep to python

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: nvidia-settings 367.35-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Oct  4 17:16:44 2017
  InstallationDate: Installed on 2017-10-04 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20170929)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: nvidia-settings
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1721394/+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 1567597] Re: implement 'complain mode' in seccomp for developer mode with snaps

[Tyler Hicks]

** Changed in: snappy
   Status: Confirmed => In Progress

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

Title:
  implement 'complain mode' in seccomp for developer mode with snaps

Status in Snappy:
  In Progress
Status in libseccomp package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in libseccomp source package in Xenial:
  In Progress
Status in linux source package in Xenial:
  In Progress
Status in libseccomp source package in Zesty:
  In Progress
Status in linux source package in Zesty:
  In Progress

Bug description:
  A requirement for snappy is that a snap may be placed in developer
  mode which will put the security sandbox in complain mode such that
  violations against policy are logged, but permitted. In this manner
  learning tools can be written to parse the logs, etc and make
  developing on snappy easier.

  Unfortunately with seccomp only SCMP_ACT_KILL logs to dmesg and while
  we can set complain mode to permit all calls, they are not logged at
  this time. I've discussed this with upstream and we are working
  together on the approach. This may require a kernel patch and an
  update to libseccomp, to filing this bug for now as a placeholder and
  we'll add other tasks as necessary.

  UPDATE: ubuntu-core-launcher now supports the '@complain' directive
  that is a synonym for '@unrestricted' so people can at least turn on
  developer mode and not be blocked by seccomp. Proper complain mode for
  seccomp needs to still be implemented (this bug).

  [Impact]

  Snapd needs a way to log seccomp actions without blocking any syscalls
  in order to have a more useful complain mode. Such functionality has
  been acked upstream and patches are on their way into the Linux 4.14
  kernel (backported to 4.12.0-13.14 in artful).

  The corresponding libseccomp changes are still undergoing review
  (https://github.com/seccomp/libseccomp/pull/92). The pull request adds
  a number of new symbols and probably isn't appropriate to backport
  until upstream has acked the pull request. However, only a small part
  of that larger pull request is needed by snapd and that change can be
  safely backported since the only added symbol, the SCMP_ACT_LOG macro,
  must match the SECCOMP_RET_LOG macro that has already been approved
  and merged in the upstream Linux kernel.

  [Test Case]

  A large number of tests are ran as part of the libseccomp build.
  However, the "live" tests which test libseccomp with actual kernel
  enforcement are not ran at that time. They can be manually exercised
  to help catch any regressions. Note that on Artful, there's an
  existing test failure (20-live-basic_die%%002-1):

  $ sudo apt build-dep -y libseccomp
  $ sudo apt install -y cython
  $ apt source libseccomp
  $ cd libseccomp-*
  $ autoreconf -ivf && ./configure --enable-python && make check-build
  $ (cd tests && ./regression -T live)

  All tests should pass on zesty (12 tests) and xenial (10 tests). On artful, 
you'll see one pre-existing failure:
  ...
  Test 20-live-basic_die%%002-1 result:   FAILURE 20-live-basic_die TRAP 
rc=159
  ...
  Regression Test Summary
   tests run: 12
   tests skipped: 0
   tests passed: 11
   tests failed: 1
   tests errored: 0
  

  Now we can build and run a small test program to test the SCMP_ACT_LOG
  action in the way that snapd wants to use it for developer mode:

  $ sudo apt install -y libseccomp-dev
  $ gcc -o lp1567597-test lp1567597-test.c -lseccomp
  $ ./lp1567597-test

  With a kernel that contains the logging patches and an updated
  libseccomp, the exit code should be 0 and you should have an entry in
  the system log that looks like this:

  audit: type=1326 audit(1505859630.994:69): auid=1000 uid=1000 gid=1000
  ses=2 pid=18451 comm="lp1567597-test"
  exe="/home/tyhicks/lp1567597-test" sig=0 arch=c03e syscall=2
  compat=0 ip=0x7f547352c5c0 code=0x7ffc

  If you have an updated libseccomp with an old kernel, you'll see that
  seccomp_init() fails due to the added compatibility check inside of
  libseccomp determines that the kernel doesn't have proper support for
  the new log action:

  $ ./lp1567597-test
  ERROR: seccomp_init: Invalid argument

  [Regression Potential]

  Relatively small since the core logic is in the kernel and we're only
  exposing the new action through libseccomp. The changes include smarts
  to query the kernel to see if the action is available in the kernel.
  Calling applications will not be able to use the action on older
  kernels that don't support it.

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

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

[Kernel-packages] [Bug 1721394] Re: Cannot open nvidia-settings on pc with a hybrid device (or use prime-select), missing python

[Jeremy Bicha]

Doug, if the package needs python, then it should be marked as a
dependency.

** Changed in: nvidia-prime (Ubuntu)
   Status: Invalid => New

** Changed in: nvidia-settings (Ubuntu)
   Status: Invalid => New

** Tags added: rls-aa-incoming

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

Title:
  Cannot open nvidia-settings on pc with a hybrid device (or use prime-
  select), missing python

Status in nvidia-prime package in Ubuntu:
  New
Status in nvidia-settings package in Ubuntu:
  New

Bug description:
  You would see -
  $ nvidia-settings
  ** Message: PRIME: Requires offloading
  ** Message: PRIME: is it supported? yes

  ** (nvidia-settings:1848): ERROR **: PRIME error: Failed to execute child 
process “/usr/bin/prime-select” (No such file or directory)
  Trace/breakpoint trap

  Additionally if trying to run prime-select you'd see -
  sudo: unable to execute /usr/bin/prime-select: No such file or directory

  One would need to go
   python3 /usr/bin/prime-select intel

  This is because the python package has been removed from image & isn't
  installed by either nvidia-settings or nvidia-prime.

  Please adjust this packages to either use python3 or dep to python

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: nvidia-settings 367.35-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Oct  4 17:16:44 2017
  InstallationDate: Installed on 2017-10-04 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20170929)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: nvidia-settings
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1721394/+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 1588632] Re: Please upgrade to zfs 0.6.5.7

[Andreas Hasenack]

Artful has 0.6.5.11, FTR.

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

Title:
  Please upgrade to zfs 0.6.5.7

Status in linux package in Ubuntu:
  Confirmed
Status in zfs-linux package in Ubuntu:
  Fix Released

Bug description:
  Version 0.6.5.7 was released 21 ago, this is the changelog:
  https://github.com/zfsonlinux/zfs/releases/tag/zfs-0.6.5.7

  Since Ubuntu is now shipping ZFS we can't rely on the ppa anymore to
  provide up to date packages. This point release also fixes a few minor
  bugs and supports Linux 4.6.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1588632/+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 1716301] Re: wifi driver: mt7601u not work on 16.04

[chenzero]

Hi, I am not sure where to add this timeout ?
in the /etc/sysctl.conf, or in the /boot/grub/grub.cfg
Thanks!

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

Title:
  wifi driver: mt7601u not work on 16.04

Status in linux package in Ubuntu:
  Confirmed
Status in usb-modeswitch-data package in Ubuntu:
  New

Bug description:
  In the beginning, when the adapter is pluged in, it's mounted as a disk 
including driver files for Windows, and
  $> lsusb
  Bus 003 Device 010: ID 148f:2878 Ralink Technology, Corp.

  after eject the disk,
  $> lsusb
  Bus 003 Device 011: ID 148f:7601 Ralink Technology, Corp. MT7601U Wireless 
Adapter

  I tried following 3 drivers:
  1) the default mt7601u included in the kernel: 4.4.0-91-generic
  after eject the disk,
  $> lsmod|grep mt
  mt7601u 102400 0
  mac80211 737280 1 mt7601u
  cfg80211 565248 2 mac80211,mt7601u
  binfmt_misc 20480 1
  $> modinfo mt7601u
  filename: 
/lib/modules/4.4.0-91-generic/kernel/drivers/net/wireless/mediatek/mt7601u/mt7601u.ko
  srcversion: E8B632D369E0C2A9F1CF7D8
  alias: usb:v7392p7710d*dc*dsc*dp*ic*isc*ip*in*
  ..
  depends: mac80211,cfg80211
  intree: Y
  vermagic: 4.4.0-91-generic SMP mod_unload modversions

  $> dmesg
  // begin
  [ 4581.094119] usb 3-4: USB disconnect, device number 6
  [ 4584.872751] usb 3-4: new high-speed USB device number 7 using xhci_hcd
  [ 4585.001408] usb 3-4: New USB device found, idVendor=148f, idProduct=2878
  [ 4585.001413] usb 3-4: New USB device strings: Mfr=1, Product=2, 
SerialNumber=0
  [ 4585.001416] usb 3-4: Product: Љ
  [ 4585.001418] usb 3-4: Manufacturer: Љ
  [ 4585.001753] usb-storage 3-4:1.0: USB Mass Storage device detected
  [ 4585.001873] scsi host6: usb-storage 3-4:1.0
  [ 4586.001122] scsi 6:0:0:0: CD-ROM MediaTek Flash autorun 0.01 PQ: 0 ANSI: 0 
CCS
  [ 4586.001978] sr 6:0:0:0: [sr0] scsi3-mmc drive: 52x/52x cd/rw xa/form2 cdda 
tray
  [ 4586.002529] sr 6:0:0:0: Attached scsi CD-ROM sr0
  [ 4586.002716] sr 6:0:0:0: Attached scsi generic sg1 type 5
  [ 4619.658385] ISO 9660 Extensions: Microsoft Joliet Level 3
  [ 4619.691737] ISOFS: changing to secondary root
  [ 4691.563347] usb 3-4: USB disconnect, device number 7
  [ 4693.638315] usb 3-4: new high-speed USB device number 8 using xhci_hcd
  [ 4693.766896] usb 3-4: New USB device found, idVendor=148f, idProduct=2878
  [ 4693.766901] usb 3-4: New USB device strings: Mfr=1, Product=2, 
SerialNumber=0
  [ 4693.766903] usb 3-4: Product: Љ
  [ 4693.766905] usb 3-4: Manufacturer: Љ
  [ 4693.767338] usb-storage 3-4:1.0: USB Mass Storage device detected
  [ 4693.768063] scsi host7: usb-storage 3-4:1.0
  [ 4694.766737] scsi 7:0:0:0: CD-ROM MediaTek Flash autorun 0.01 PQ: 0 ANSI: 0 
CCS
  [ 4694.767423] sr 7:0:0:0: [sr0] scsi3-mmc drive: 52x/52x cd/rw xa/form2 cdda 
tray
  [ 4694.767908] sr 7:0:0:0: Attached scsi CD-ROM sr0
  [ 4694.768147] sr 7:0:0:0: Attached scsi generic sg1 type 5
  [ 4728.418255] ISO 9660 Extensions: Microsoft Joliet Level 3
  [ 4728.427856] ISOFS: changing to secondary root
  [ 4733.824182] sr 7:0:0:0: [sr0] tag#0 FAILED Result: hostbyte=DID_ERROR 
driverbyte=DRIVER_OK
  [ 4733.824190] sr 7:0:0:0: [sr0] tag#0 CDB: Start/Stop Unit 1b 00 00 00 02 00
  [ 4733.824218] usb 3-4: USB disconnect, device number 8
  [ 4733.824281] sr 7:0:0:0: [sr0] tag#0 FAILED Result: hostbyte=DID_ERROR 
driverbyte=DRIVER_OK
  [ 4733.824291] sr 7:0:0:0: [sr0] tag#0 CDB: Prevent/Allow Medium Removal 1e 
00 00 00 00 00
  [ 4734.099901] usb 3-4: new high-speed USB device number 9 using xhci_hcd
  [ 4734.238749] usb 3-4: New USB device found, idVendor=148f, idProduct=7601
  [ 4734.238754] usb 3-4: New USB device strings: Mfr=1, Product=2, 
SerialNumber=3
  [ 4734.238757] usb 3-4: Product: 802.11 n WLAN
  [ 4734.238772] usb 3-4: Manufacturer: MediaTek
  [ 4734.238775] usb 3-4: SerialNumber: 1.0
  [ 4735.432096] usb 3-4: reset high-speed USB device number 9 using xhci_hcd
  [ 4735.562543] mt7601u 3-4:1.0: ASIC revision: 76010001 MAC revision: 76010500
  [ 4735.563089] mt7601u 3-4:1.0: Firmware Version: 0.1.00 Build: 7640 Build 
time: 201302052146
  [ 4739.011624] mt7601u 3-4:1.0: Vendor request req:07 off:09a8 failed:-110
  [ 4742.131399] mt7601u 3-4:1.0: Vendor request req:02 off:09a8 failed:-110
  [ 4745.251254] mt7601u 3-4:1.0: Vendor request req:07 off:0734 failed:-110
  [ 4748.371056] mt7601u 3-4:1.0: Vendor request req:42 off:0230 failed:-110
  [ 4751.490880] mt7601u 3-4:1.0: Vendor request req:07 off:0080 failed:-110
  [ 4754.610694] mt7601u 3-4:1.0: Vendor request req:02 off:0080 failed:-110
  [ 4757.730501] mt7601u 3-4:1.0: Vendor request req:02 off:0080 failed:-110
  [ 4757.730548] mt7601u: probe of 3-4:1.0 failed with error -110
  [ 4757.730870] usbcore: registered new interface driver mt7601u
  // end 

  $> sudo ifconfig -a // do not list any 

Re: [Kernel-packages] [Bug 1696154] Comment bridged from LTC Bugzilla

[Steve Langasek]

On Thu, Oct 05, 2017 at 01:52:46AM -, bugproxy wrote:
> --- Comment From gcwil...@us.ibm.com 2017-10-04 17:33 EDT---
> I have received the KEK from Emily in person.

> --- Comment From gcwil...@us.ibm.com 2017-10-04 18:16 EDT---

> BTW, I learned from Emily that Canonical plans to issue Power keys/certs
> separately from those for the x86 UEFI shim.  So moving from SHA-512 to
> SHA-256 may not be much of a priority from a reuse point of view.  If we
> need any key changes, it would be good to send them before or during next
> week while Emily will be in NY meeting with vorlon.

Yes, if you need the hash changed from SHA512 to SHA256 on the 2048-bit db
key, please let us know this week so that we can arrange to have a new ESL
signed.

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

Title:
  [17.10 FEAT] Sign POWER host/NV kernels

Status in Launchpad itself:
  Fix Committed
Status in The Ubuntu-power-systems project:
  In Progress
Status in linux package in Ubuntu:
  In Progress
Status in linux-signed package in Ubuntu:
  In Progress

Bug description:
  Feature Description:

  Sign POWER host and NV kernels with sign-file in anticipation of POWER
  secure boot.  Provide the  associated certificate.  Ideally it would
  be possible to reuse the UEFI shim private key and certificate used to
  sign and verify x86_64 kernels.  More details to follow.  Guest
  kernels will be addressed in a future separate feature request.

  
  Business Case: 

  As a system administrator I want to verify the integrity of my kernels
  so that I can prevent malicious kernels from being executed.

  Use Case:

  Signed POWER kernels will be validated by OPAL as OpenPOWER systems
  boot when keys are properly installed and the system is booted in
  secure mode.

  
  Test Case:

  Sign and install a POWER kernel on an OpenPOWER machine with a
  firmware level that supports secure boot.  Install a PK, distro KEK
  certificat, and distro DB certificate.  Boot the system and verify
  that it will boot the kernel.  Negative tests:  Separately remove the
  signature, install an usigned kernel, and modify the kernel image and
  test that the kernel will not boot.

To manage notifications about this bug go to:
https://bugs.launchpad.net/launchpad/+bug/1696154/+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 1721477] Re: Xenial update to 4.4.89 stable release

[Thadeu Lima de Souza Cascardo]

** Changed in: linux (Ubuntu Xenial)
   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/1721477

Title:
  Xenial update to 4.4.89 stable release

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

Bug description:
  SRU Justification

  Impact:
     The upstream process for stable tree updates is quite similar
     in scope to the Ubuntu SRU process, e.g., each patch has to
     demonstrably fix a bug, and each patch is vetted by upstream
     by originating either directly from a mainline/stable Linux tree or
     a minimally backported form of that patch. The 4.4.89 upstream stable
     patch set is now available. It should be included in the Ubuntu
     kernel as well.

     git://git.kernel.org/

  TEST CASE: TBD

  The following patches from the 4.4.89 stable release shall be applied:
  * ipv6: accept 64k - 1 packet length in ip6_find_1stfragopt()
  * ipv6: add rcu grace period before freeing fib6_node
  * ipv6: fix sparse warning on rt6i_node
  * qlge: avoid memcpy buffer overflow
  * Revert "net: phy: Correctly process PHY_HALTED in phy_stop_machine()"
  * Revert "net: use lib/percpu_counter API for fragmentation mem accounting"
  * Revert "net: fix percpu memory leaks"
  * gianfar: Fix Tx flow control deactivation
  * ipv6: fix memory leak with multiple tables during netns destruction
  * ipv6: fix typo in fib6_net_exit()
  * f2fs: check hot_data for roll-forward recovery
  * x86/fsgsbase/64: Report FSBASE and GSBASE correctly in core dumps
  * md/raid5: release/flush io in raid5_do_work()
  * nfsd: Fix general protection fault in release_lock_stateid()
  * mm: prevent double decrease of nr_reserved_highatomic
  * tty: improve tty_insert_flip_char() fast path
  * tty: improve tty_insert_flip_char() slow path
  * tty: fix __tty_insert_flip_char regression
  * Input: i8042 - add Gigabyte P57 to the keyboard reset table
  * MIPS: math-emu: .: Fix quiet NaN propagation
  * MIPS: math-emu: .: Fix cases of both inputs zero
  * MIPS: math-emu: .: Fix cases of both inputs negative
  * MIPS: math-emu: .: Fix cases of input values with opposite
signs
  * MIPS: math-emu: .: Fix cases of both infinite inputs
  * MIPS: math-emu: MINA.: Fix some cases of infinity and zero inputs
  * crypto: AF_ALG - remove SGL terminator indicator when chaining
  * ext4: fix incorrect quotaoff if the quota feature is enabled
  * ext4: fix quota inconsistency during orphan cleanup for read-only mounts
  * powerpc: Fix DAR reporting when alignment handler faults
  * block: Relax a check in blk_start_queue()
  * md/bitmap: disable bitmap_resize for file-backed bitmaps.
  * skd: Avoid that module unloading triggers a use-after-free
  * skd: Submit requests to firmware before triggering the doorbell
  * scsi: zfcp: fix queuecommand for scsi_eh commands when DIX enabled
  * scsi: zfcp: add handling for FCP_RESID_OVER to the fcp ingress path
  * scsi: zfcp: fix capping of unsuccessful GPN_FT SAN response trace records
  * scsi: zfcp: fix passing fsf_req to SCSI trace on TMF to correlate with HBA
  * scsi: zfcp: fix missing trace records for early returns in TMF eh handlers
  * scsi: zfcp: fix payload with full FCP_RSP IU in SCSI trace records
  * scsi: zfcp: trace HBA FSF response by default on dismiss or timedout late
response
  * scsi: zfcp: trace high part of "new" 64 bit SCSI LUN
  * scsi: megaraid_sas: Check valid aen class range to avoid kernel panic
  * scsi: megaraid_sas: Return pended IOCTLs with cmd_status
MFI_STAT_WRONG_STATE in case adapter is dead
  * scsi: storvsc: fix memory leak on ring buffer busy
  * scsi: sg: remove 'save_scat_len'
  * scsi: sg: use standard lists for sg_requests
  * scsi: sg: off by one in sg_ioctl()
  * scsi: sg: factor out sg_fill_request_table()
  * scsi: sg: fixup infoleak when using SG_GET_REQUEST_TABLE
  * scsi: qla2xxx: Fix an integer overflow in sysfs code
  * ftrace: Fix selftest goto location on error
  * tracing: Apply trace_clock changes to instance max buffer
  * ARC: Re-enable MMU upon Machine Check exception
  * PCI: shpchp: Enable bridge bus mastering if MSI is enabled
  * media: v4l2-compat-ioctl32: Fix timespec conversion
  * media: uvcvideo: Prevent heap overflow when accessing mapped controls
  * bcache: initialize dirty stripes in flash_dev_run()
  * bcache: Fix leak of bdev reference
  * bcache: do not subtract sectors_to_gc for bypassed IO
  * bcache: correct cache_dirty_target in __update_writeback_rate()
  * bcache: Correct return value for sysfs attach errors
  * bcache: fix for gc and write-back race
  * bcache: fix bch_hprint crash and improve output
  * ftrace: Fix memleak when unregistering dynamic ops when tracing 

[Kernel-packages] [Bug 1718195] Re: Xenial update to 4.4.88 stable release

[Thadeu Lima de Souza Cascardo]

** Changed in: linux (Ubuntu Xenial)
   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/1718195

Title:
  Xenial update to 4.4.88 stable release

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

Bug description:
  SRU Justification

  Impact:
     The upstream process for stable tree updates is quite similar
     in scope to the Ubuntu SRU process, e.g., each patch has to
     demonstrably fix a bug, and each patch is vetted by upstream
     by originating either directly from a mainline/stable Linux tree or
     a minimally backported form of that patch. The 4.4.88 upstream stable
     patch set is now available. It should be included in the Ubuntu
     kernel as well.

     git://git.kernel.org/

  TEST CASE: TBD

  The following patches from the 4.4.88 stable release shall be applied:
  * usb: quirks: add delay init quirk for Corsair Strafe RGB keyboard
  * USB: serial: option: add support for D-Link DWM-157 C1
  * usb: Add device quirk for Logitech HD Pro Webcam C920-C
  * usb:xhci:Fix regression when ATI chipsets detected
  * USB: core: Avoid race of async_completed() w/ usbdev_release()
  * staging/rts5208: fix incorrect shift to extract upper nybble
  * driver core: bus: Fix a potential double free
  * intel_th: pci: Add Cannon Lake PCH-H support
  * intel_th: pci: Add Cannon Lake PCH-LP support
  * ath10k: fix memory leak in rx ring buffer allocation
  * rtlwifi: rtl_pci_probe: Fix fail path of _rtl_pci_find_adapter
  * Bluetooth: Add support of 13d3:3494 RTL8723BE device
  * dlm: avoid double-free on error path in dlm_device_{register,unregister}
  * mwifiex: correct channel stat buffer overflows
  * drm/nouveau/pci/msi: disable MSI on big-endian platforms by default
  * workqueue: Fix flag collision
  * cs5536: add support for IDE controller variant
  * scsi: sg: protect against races between mmap() and SG_SET_RESERVED_SIZE
  * scsi: sg: recheck MMAP_IO request length with lock held
  * drm: adv7511: really enable interrupts for EDID detection
  * drm/bridge: adv7511: Fix mutex deadlock when interrupts are disabled
  * drm/bridge: adv7511: Use work_struct to defer hotplug handing to out of irq
context
  * drm/bridge: adv7511: Switch to using drm_kms_helper_hotplug_event()
  * drm/bridge: adv7511: Re-write the i2c address before EDID probing
  * btrfs: resume qgroup rescan on rw remount
  * locktorture: Fix potential memory leak with rw lock test
  * ALSA: msnd: Optimize / harden DSP and MIDI loops
  * ARM: 8692/1: mm: abort uaccess retries upon fatal signal
  * NFS: Fix 2 use after free issues in the I/O code
  * xfs: XFS_IS_REALTIME_INODE() should be false if no rt device present
  * Linux 4.4.88

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1718195/+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 1721550] Re: Xenial update to 4.4.90 stable release

[Thadeu Lima de Souza Cascardo]

** Changed in: linux (Ubuntu Xenial)
   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/1721550

Title:
  Xenial update to 4.4.90 stable release

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

Bug description:
  SRU Justification

  Impact:
     The upstream process for stable tree updates is quite similar
     in scope to the Ubuntu SRU process, e.g., each patch has to
     demonstrably fix a bug, and each patch is vetted by upstream
     by originating either directly from a mainline/stable Linux tree or
     a minimally backported form of that patch. The 4.4.90 upstream stable
     patch set is now available. It should be included in the Ubuntu
     kernel as well.

     git://git.kernel.org/

  TEST CASE: TBD

  The following patches from the 4.4.90 stable release shall be applied:
  * cifs: release auth_key.response for reconnect.
  * mac80211: flush hw_roc_start work before cancelling the ROC
  * KVM: PPC: Book3S: Fix race and leak in kvm_vm_ioctl_create_spapr_tce()
  * tracing: Fix trace_pipe behavior for instance traces
  * tracing: Erase irqsoff trace with empty write
  * md/raid5: fix a race condition in stripe batch
  * md/raid5: preserve STRIPE_ON_UNPLUG_LIST in break_stripe_batch_list
  * scsi: scsi_transport_iscsi: fix the issue that iscsi_if_rx doesn't parse
nlmsg properly
  * crypto: talitos - Don't provide setkey for non hmac hashing algs.
  * crypto: talitos - fix sha224
  * KEYS: fix writing past end of user-supplied buffer in keyring_read()
  * KEYS: prevent creating a different user's keyrings
  * KEYS: prevent KEYCTL_READ on negative key
  * powerpc/pseries: Fix parent_dn reference leak in add_dt_node()
  * Fix SMB3.1.1 guest authentication to Samba
  * SMB: Validate negotiate (to protect against downgrade) even if signing off
  * SMB3: Don't ignore O_SYNC/O_DSYNC and O_DIRECT flags
  * vfs: Return -ENXIO for negative SEEK_HOLE / SEEK_DATA offsets
  * nl80211: check for the required netlink attributes presence
  * bsg-lib: don't free job in bsg_prepare_job
  * seccomp: fix the usage of get/put_seccomp_filter() in seccomp_get_filter()
  * arm64: Make sure SPsel is always set
  * arm64: fault: Route pte translation faults via do_translation_fault
  * KVM: VMX: Do not BUG() on out-of-bounds guest IRQ
  * kvm: nVMX: Don't allow L2 to access the hardware CR8
  * PCI: Fix race condition with driver_override
  * btrfs: fix NULL pointer dereference from free_reloc_roots()
  * btrfs: propagate error to btrfs_cmp_data_prepare caller
  * btrfs: prevent to set invalid default subvolid
  * x86/fpu: Don't let userspace set bogus xcomp_bv
  * gfs2: Fix debugfs glocks dump
  * timer/sysclt: Restrict timer migration sysctl values to 0 and 1
  * KVM: VMX: do not change SN bit in vmx_update_pi_irte()
  * KVM: VMX: remove WARN_ON_ONCE in kvm_vcpu_trigger_posted_interrupt
  * cxl: Fix driver use count
  * dmaengine: mmp-pdma: add number of requestors
  * ARM: pxa: add the number of DMA requestor lines
  * ARM: pxa: fix the number of DMA requestor lines
  * KVM: VMX: use cmpxchg64
  * video: fbdev: aty: do not leak uninitialized padding in clk to userspace
  * swiotlb-xen: implement xen_swiotlb_dma_mmap callback
  * fix xen_swiotlb_dma_mmap prototype
  * Linux 4.4.90

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1721550/+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 1721650] [NEW] zfs-dkms 0.6.5.6-0ubuntu18: zfs kernel module failed to build

[rebroad]

Public bug reported:

just installed 16.04 LTS (downloaded today) and tried to install zfs -
no other packages installed yet.

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: zfs-dkms 0.6.5.6-0ubuntu18
ProcVersionSignature: Ubuntu 4.10.0-35.39~16.04.1-generic 4.10.17
Uname: Linux 4.10.0-35-generic x86_64
NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: amd64
DKMSBuildLog:
 DKMS make.log for zfs-0.6.5.6 for kernel 4.10.0-35-generic (x86_64)
 Thu  5 Oct 22:36:13 BST 2017
 make: *** No targets specified and no makefile found. Stop.
DKMSKernelVersion: 4.10.0-35-generic
Date: Thu Oct  5 22:36:20 2017
InstallationDate: Installed on 2017-10-05 (0 days ago)
InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801)
PackageVersion: 0.6.5.6-0ubuntu18
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.2
 apt  1.2.24
SourcePackage: zfs-linux
Title: zfs-dkms 0.6.5.6-0ubuntu18: zfs kernel module failed to build
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package xenial

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

Title:
  zfs-dkms 0.6.5.6-0ubuntu18: zfs kernel module failed to build

Status in zfs-linux package in Ubuntu:
  New

Bug description:
  just installed 16.04 LTS (downloaded today) and tried to install zfs -
  no other packages installed yet.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: zfs-dkms 0.6.5.6-0ubuntu18
  ProcVersionSignature: Ubuntu 4.10.0-35.39~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-35-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  DKMSBuildLog:
   DKMS make.log for zfs-0.6.5.6 for kernel 4.10.0-35-generic (x86_64)
   Thu  5 Oct 22:36:13 BST 2017
   make: *** No targets specified and no makefile found. Stop.
  DKMSKernelVersion: 4.10.0-35-generic
  Date: Thu Oct  5 22:36:20 2017
  InstallationDate: Installed on 2017-10-05 (0 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  PackageVersion: 0.6.5.6-0ubuntu18
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.24
  SourcePackage: zfs-linux
  Title: zfs-dkms 0.6.5.6-0ubuntu18: zfs kernel module failed to build
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1721650/+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 1721643] [NEW] dmidecode fails to read SMBIOS on Apple Mac hardware

[thetravellor]

Public bug reported:

Package Version:

dmidecode/xenial-updates,now 3.0-2ubuntu0.1 amd64 [installed,automatic]

Ubuntu Version

Distributor ID: Ubuntu
Description:Ubuntu 16.04.3 LTS
Release:16.04
Codename:   xenial

Xenial 16.04LTS

Kernel Version:

Linux family 4.4.0-96-generic #119-Ubuntu SMP Tue Sep 12 14:59:54 UTC
2017 x86_64 x86_64 x86_64 GNU/Linux

Hardware:
Vendor: Apple Inc.
Manufacturer: Apple Inc.
Manufacturer: Apple Inc.
Manufacturer: Apple Inc.
String 1: Apple ROM Version.  BIOS ID:  MM71.

Problem:

dmidecode consistently produces the following error at the end of every
output:

"Invalid entry length (0). DMI table is broken! Stop."

Why is this a problem? It breaks systems management tools which use
dmidecode to gather information about system status, rendering the tools
ineffective (opennms and observium both affected).

Suggested fix: reading on the internet suggests that such a bug has been
observed on other platforms before and was resolved by using a version
of dmidecode based upon 3.1 solves the problem. If willing backport
dmidecode from artful?

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


** Tags: hardware

** Attachment added: "Output from systems management tool affected by dmidecode 
bug"
   
https://bugs.launchpad.net/bugs/1721643/+attachment/4963164/+files/Capture.PNG

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

Title:
  dmidecode fails to read SMBIOS on Apple Mac hardware

Status in dmidecode package in Ubuntu:
  New

Bug description:
  Package Version:

  dmidecode/xenial-updates,now 3.0-2ubuntu0.1 amd64
  [installed,automatic]

  Ubuntu Version

  Distributor ID: Ubuntu
  Description:Ubuntu 16.04.3 LTS
  Release:16.04
  Codename:   xenial

  Xenial 16.04LTS

  Kernel Version:

  Linux family 4.4.0-96-generic #119-Ubuntu SMP Tue Sep 12 14:59:54 UTC
  2017 x86_64 x86_64 x86_64 GNU/Linux

  Hardware:
  Vendor: Apple Inc.
  Manufacturer: Apple Inc.
  Manufacturer: Apple Inc.
  Manufacturer: Apple Inc.
  String 1: Apple ROM Version.  BIOS ID:  MM71.

  Problem:

  dmidecode consistently produces the following error at the end of
  every output:

  "Invalid entry length (0). DMI table is broken! Stop."

  Why is this a problem? It breaks systems management tools which use
  dmidecode to gather information about system status, rendering the
  tools ineffective (opennms and observium both affected).

  Suggested fix: reading on the internet suggests that such a bug has
  been observed on other platforms before and was resolved by using a
  version of dmidecode based upon 3.1 solves the problem. If willing
  backport dmidecode from artful?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dmidecode/+bug/1721643/+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 1708604] Re: Backport recent bbr bugfixes to 4.10 kernel

[Thadeu Lima de Souza Cascardo]

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

Title:
  Backport recent bbr bugfixes to 4.10 kernel

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Xenial:
  Confirmed
Status in linux source package in Zesty:
  Fix Committed

Bug description:
  4.10 kernel is commonly used to test BBR Congestion Control
  deployments.

  Recent net-next pull in 4.13-rc1 had a bunch of fixes for the initial BBR 
release, namely:
  4aea287e90dd61a48268ff2994b56f9799441b62 tcp_bbr: cut pacing rate only if 
filled pipe
  f19fd62dafaf1ed6cf615dba655b82fa9df59074 tcp_bbr: introduce 
bbr_bw_to_pacing_rate() helper
  79135b89b8af304456bd67916b80116ddf03d7b6 tcp_bbr: introduce 
bbr_init_pacing_rate_from_rtt() helper
  1d3648eb5d1fe9ed3d095ed8fa19ad11ca4c8bc0 tcp_bbr: remove sk_pacing_rate=0 
transient during init
  32984565574da7ed3afa10647bb4020d7a9e6c93 tcp_bbr: init pacing rate on first 
RTT sample

  All of them marked as 'Fixes: 0f8782ea1497 ("tcp_bbr: add BBR
  congestion control")', which makes them legitimate bugfixes.

  All of them constrained to `net/ipv4/tcp_bbr.c` and should be trivial
  to cherrypick into 4.10.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1708604/+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 1720660] Re: linux 4.13.0-13.14 ADT test failure with linux 4.13.0-13.14

[John Johansen]

Marking it Fix Released. Please re-open if you find you still have
issues.


** Changed in: linux (Ubuntu)
   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/1720660

Title:
  linux 4.13.0-13.14 ADT test failure with linux 4.13.0-13.14

Status in linux package in Ubuntu:
  Fix Released

Bug description:
  Testing failed on:
  amd64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-artful-canonical-kernel-team-bootstrap/artful/amd64/l/linux/20170930_151719_8c658@/log.gz
  i386: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-artful-canonical-kernel-team-bootstrap/artful/i386/l/linux/20170930_220543_8c658@/log.gz
  ppc64el: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-artful-canonical-kernel-team-bootstrap/artful/ppc64el/l/linux/20170930_164802_8c658@/log.gz

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1720660/+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 1721070] Re: powerpc/64s: Add workaround for P9 vector CI load issuenext

[Joseph Salisbury]

I also built a 4.10 based test kernel(16.04.3).  It required commit
ccd3cd361 and a3d96f70c1 as prerequisites. The test kernel can be
downloaded from:

http://kernel.ubuntu.com/~jsalisbury/lp1721070/zesty

Can you test this kernel and see if it resolves 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/1721070

Title:
  powerpc/64s: Add workaround for P9 vector CI load issuenext

Status in The Ubuntu-power-systems project:
  In Progress
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Zesty:
  Triaged
Status in linux source package in Artful:
  In Progress

Bug description:
  -- Problem Description --
  POWER9 DD2.1 and earlier has an issue where some cache inhibited
  vector load will return bad data. The workaround is two part, one
  firmware/microcode part triggers HMI interrupts when hitting such
  loads, the other part is this patch which then emulates the
  instructions in Linux.

  The affected instructions are limited to lxvd2x, lxvw4x, lxvb16x and
  lxvh8x.

  When an instruction triggers the HMI, all threads in the core will be
  sent to the HMI handler, not just the one running the vector load.

  In general, these spurious HMIs are detected by the emulation code and
  we just return back to the running process. Unfortunately, if a
  spurious interrupt occurs on a vector load that's to normal memory we
  have no way to detect that it's spurious (unless we walk the page
  tables, which is very expensive). In this case we emulate the load but
  we need do so using a vector load itself to ensure 128bit atomicity is
  preserved.

  Some additional debugfs emulated instruction counters are added also.

  In order to solve this bug, we need to cherry pick the following patch

  
https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git/commit/?h=next=5080332c2c893118dbc18755f35c8b0131cf0fc4

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1721070/+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 1720660] Re: linux 4.13.0-13.14 ADT test failure with linux 4.13.0-13.14

[John Johansen]

Fixed in

commit 393d5cca6af1070709f2baaf291d16e27fbea366
Author: John Johansen 
Date:   Thu Oct 5 13:50:51 2017 -0700

Fix test-kernel-security.py when LSM stacking based kernel is used.

In the LSM stacking kernel DEFAULT_SECURITY_APPARMOR is not set instead
SECURITY_APPARMOR_STACKED is used to indicate it is part of the default
stack.

BugLink: http://bugs.launchpad.net/bugs/1720660
Signed-off-by: John Johansen 

diff --git a/scripts/test-kernel-security.py b/scripts/test-kernel-security.py
index 2625f9aa..9eecdca5 100755
--- a/scripts/test-kernel-security.py
+++ b/scripts/test-kernel-security.py
@@ -668,7 +668,7 @@ class KernelSecurityTest(testlib.TestlibCase):
 '''CONFIG_SECURITY_APPARMOR enabled'''
 
 self.assertEqual(self._get_config('SECURITY_APPARMOR'), 'y')
-self.assertEqual(self._get_config('DEFAULT_SECURITY_APPARMOR'), 'y')
+self.assertTrue(self._get_config('DEFAULT_SECURITY_APPARMOR') == 'y' 
or self._get_config('CONFIG_SECURITY_APPARMOR_STACKED') == 'y')
 
self.assertEqual(self._get_config('SECURITY_APPARMOR_BOOTPARAM_VALUE'), '1')
 
 # Hardy and newer


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

Title:
  linux 4.13.0-13.14 ADT test failure with linux 4.13.0-13.14

Status in linux package in Ubuntu:
  Fix Committed

Bug description:
  Testing failed on:
  amd64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-artful-canonical-kernel-team-bootstrap/artful/amd64/l/linux/20170930_151719_8c658@/log.gz
  i386: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-artful-canonical-kernel-team-bootstrap/artful/i386/l/linux/20170930_220543_8c658@/log.gz
  ppc64el: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-artful-canonical-kernel-team-bootstrap/artful/ppc64el/l/linux/20170930_164802_8c658@/log.gz

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1720660/+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 1515513] Re: /boot/initrd.img-*.old-dkms files left behind

[Brian Murray]

I've uploaded fixes to all releases previously identified as worth
fixing which remove the .old-dkms file after its been created.

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

Title:
  /boot/initrd.img-*.old-dkms files left behind

Status in dkms package in Ubuntu:
  In Progress
Status in initramfs-tools package in Ubuntu:
  Confirmed
Status in dkms source package in Xenial:
  Fix Committed
Status in initramfs-tools source package in Xenial:
  New
Status in dkms source package in Zesty:
  Fix Committed
Status in initramfs-tools source package in Zesty:
  New
Status in dkms package in Debian:
  New

Bug description:
  [Impact]
  If a dkms package is installed which has REMAKE_INITRD or the same setting 
has be manually configured by a user then when a kernel is removed its possible 
for an ".old-dkms" file to be left in /boot with no associated kernel.

  [Test Case]
  On a system with two old kernels and one new kernel available in -updates:
  1) install r8168-dkms
  2) install the dkms module for the old kernel e.g. 'sudo dkms install -m 
r8168 -v 8.041.00 -k 4.4.0-31-generic'
  3) upgrade your kernel e.g. "sudo apt install linux-image-generic'
  4) sudo apt autoremove
  5) observe something like "initrd.img-4.4.0-31-generic.old-dkms" in /boot 
without a corresponding "initrd.img-4.4.0-31-generic"

  With the version of dkms in -proposed, the .old-dkms file will be
  removed when the kernel is auto removed.

  [Regression Potential]
  Somebody out there might expect the .old-dkms file to be kept, but that seems 
like an odd expectation.

  One notices *.old-dkms files being left behind still sitting on the
  disk after purging the related kernel. This can cause /boot to become
  full, and when it gets really bad, even sudo apt-get autoremove won't
  fix the problem - only deleting the old-dkms files manually solves the
  problem.

  Note:  Filling up the /boot partition causes updates to fail.

  ProblemType: BugDistroRelease: Ubuntu 15.04
  Package: dkms 2.2.0.3-2ubuntu3.3
  ProcVersionSignature: Ubuntu 3.19.0-28.30-generic 3.19.8-ckt5
  Uname: Linux 3.19.0-28-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1.7
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Thu Nov 12 08:17:10 2015
  InstallationDate: Installed on 2015-05-05 (190 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  PackageArchitecture: allSourcePackage: dkms
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/1515513/+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 1721070] Re: powerpc/64s: Add workaround for P9 vector CI load issuenext

[Joseph Salisbury]

The commits are in the master branch:

0f5d387 powerpc/64s: Add workaround for P9 vector CI load issue
d401742 powerpc/mce: Move 64-bit machine check code into mce.c
1e3dad9 UBUNTU: Ubuntu-4.13.0-12.13
1f46464 UBUNTU: [Config] CONFIG_I2C_XLP9XX=m


I'll check to ensure I tar'd up the right tree.

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

** Changed in: linux (Ubuntu Zesty)
   Status: New => Triaged

** Changed in: linux (Ubuntu Zesty)
   Importance: Undecided => Critical

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

Title:
  powerpc/64s: Add workaround for P9 vector CI load issuenext

Status in The Ubuntu-power-systems project:
  In Progress
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Zesty:
  Triaged
Status in linux source package in Artful:
  In Progress

Bug description:
  -- Problem Description --
  POWER9 DD2.1 and earlier has an issue where some cache inhibited
  vector load will return bad data. The workaround is two part, one
  firmware/microcode part triggers HMI interrupts when hitting such
  loads, the other part is this patch which then emulates the
  instructions in Linux.

  The affected instructions are limited to lxvd2x, lxvw4x, lxvb16x and
  lxvh8x.

  When an instruction triggers the HMI, all threads in the core will be
  sent to the HMI handler, not just the one running the vector load.

  In general, these spurious HMIs are detected by the emulation code and
  we just return back to the running process. Unfortunately, if a
  spurious interrupt occurs on a vector load that's to normal memory we
  have no way to detect that it's spurious (unless we walk the page
  tables, which is very expensive). In this case we emulate the load but
  we need do so using a vector load itself to ensure 128bit atomicity is
  preserved.

  Some additional debugfs emulated instruction counters are added also.

  In order to solve this bug, we need to cherry pick the following patch

  
https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git/commit/?h=next=5080332c2c893118dbc18755f35c8b0131cf0fc4

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1721070/+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 1721065] Re: NULL pointer dereference in tty_write() in kernel 4.4.0-93.116+

[Joseph Salisbury]

I built a X test kernel with a pick of commit e55afd11a4835.  The test
kernel can be downloaded from:

http://kernel.ubuntu.com/~jsalisbury/lp1721065/

Can you test this kernel and see if it resolves this bug?

** Changed in: linux (Ubuntu Xenial)
 Assignee: (unassigned) => Joseph Salisbury (jsalisbury)

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => Joseph Salisbury (jsalisbury)

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

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

Title:
  NULL pointer dereference in tty_write() in kernel 4.4.0-93.116+

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

Bug description:
  Sometimes an Ubuntu kernel 4.4.0-93+ panics in the following way:

  [   11.185347] BUG: unable to handle kernel NULL pointer dereference at   
(null)
  [   11.185778] IP: [] tty_write+0x83/0x2d0
  [   11.186115] PGD 0 
  [   11.186270] Oops:  [#1] SMP 
  [   11.186506] Modules linked in: prl_fs(POE) prl_eth(POE) gpio_ich ppdev 
snd_intel8x0 snd_ac97_codec ac97_bus snd_pcm s
  nd_timer input_leds snd serio_raw soundcore lpc_ich shpchp sbs prl_tg(POE) 
sbshc pvpanic parport_pc parport mac_hid auto
  fs4 psmouse ahci libahci pata_acpi fjes
  [   11.188034] CPU: 0 PID: 1 Comm: systemd Tainted: P   OE   
4.4.0-96-generic #119-Ubuntu
  [   11.188482] Hardware name: Parallels Software International Inc. Parallels 
Virtual Platform/Parallels Virtual Platfor
  m, BIOS 13.1.0 (43104) 09/26/2017
  [   11.189156] task: 88003db8 ti: 88003db88000 task.ti: 
88003db88000
  [   11.189546] RIP: 0010:[]  [] 
tty_write+0x83/0x2d0
  [   11.189964] RSP: :88003db8bcc8  EFLAGS: 00010246
  [   11.190255] RAX:  RBX: 8800392dd800 RCX: 

  [   11.190628] RDX:  RSI:  RDI: 
8800392dd828
  [   11.191002] RBP: 88003db8bd18 R08: 88003db88000 R09: 

  [   11.191398] R10: 005c R11: 00401ce0 R12: 
002f
  [   11.191775] R13: 88003584ae70 R14: 55c8eab15f20 R15: 
88003584ae00
  [   11.192152] FS:  7f649d1418c0() GS:88003de0() 
knlGS:
  [   11.192573] CS:  0010 DS:  ES:  CR0: 80050033
  [   11.192882] CR2:  CR3: 3d3b6000 CR4: 
06f0
  [   11.193264] Stack:
  [   11.193404]   813953ba 88003db8bd08 
813493bd
  [   11.193837]  002f 88003584ae00 55c8eab15f20 
88003584ae70
  [   11.194267]  002f 88003db8bf18 88003db8bd28 
8120f878
  [   11.194700] Call Trace:
  [   11.194884]  [] ? apparmor_file_permission+0x1a/0x20
  [   11.195248]  [] ? security_file_permission+0x3d/0xc0
  [   11.195621]  [] __vfs_write+0x18/0x40
  [   11.195916]  [] vfs_write+0xa9/0x1a0
  [   11.196202]  [] redirected_tty_write+0x60/0xa0
  [   11.196532]  [] ? tty_write+0x2d0/0x2d0
  [   11.196830]  [] do_loop_readv_writev+0x75/0xa0
  [   11.197160]  [] ? tty_write+0x2d0/0x2d0
  [   11.197458]  [] do_readv_writev+0x212/0x230
  [   11.198439]  [] ? do_vfs_ioctl+0x29f/0x490
  [   11.199374]  [] vfs_writev+0x39/0x50
  [   11.200268]  [] SyS_writev+0x59/0xf0
  [   11.201144]  [] ? SyS_ioctl+0x79/0x90
  [   11.202049]  [] entry_SYSCALL_64_fastpath+0x16/0x71
  [   11.202980] Code: 47 02 00 00 48 8b 93 e0 01 00 00 83 e2 02 0f 85 37 02 00 
00 48 83 78 50 00 0f 84 38 02 00 00 48 89 df e8 11 7f 00 00 48 89 45 b0 <48> 8b 
00 48 8b 40 40 48 89 c2 48 89 45 c0 48 c7 c0 fb ff ff ff 
  [   11.208047] RIP  [] tty_write+0x83/0x2d0
  [   11.208942]  RSP 
  [   11.209713] CR2: 
  [   11.210517] ---[ end trace 3b933544655b49b8 ]---
  [   11.335210] Kernel panic - not syncing: Attempted to kill init! 
exitcode=0x0009
  [   11.335210] 
  [   11.337095] Kernel Offset: disabled
  [   11.338184] ---[ end Kernel panic - not syncing: Attempted to kill init! 
exitcode=0x0009

  The crash occurs here

  1227 static ssize_t tty_write(struct file *file, const char __user *buf,
  [...]
  1243 ld = tty_ldisc_ref_wait(tty);
  1244 if (!ld->ops->write) // <===
  1245 ret = -EIO;
  1246 else
  1247 ret = do_tty_write(ld->ops->write, tty, file, buf, 
count);

  because tty_ldisc_ref_wait() returned NULL.

  It seems the issue has been introduced into 4.4.0-93+ kernels
  by the fix for the bug #1709126: according to the version 4.4.0-93.116
  changelog the patch "tty: Destroy ldisc instance on hangup" 
(https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=892d1fa7eaaed9d3c04954cb140c34ebc3393932)
 that allowed
  tty_ldisc_ref_wait() to return NULL has been backported 
 

[Kernel-packages] [Bug 1721070] Re: powerpc/64s: Add workaround for P9 vector CI load issuenext

[Joseph Salisbury]

I do see them in that tar file.  Can you run:

tar -xvf lp1721070-source.tar 
cd ubuntu-artful/
git log --oneline

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

Title:
  powerpc/64s: Add workaround for P9 vector CI load issuenext

Status in The Ubuntu-power-systems project:
  In Progress
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Zesty:
  Triaged
Status in linux source package in Artful:
  In Progress

Bug description:
  -- Problem Description --
  POWER9 DD2.1 and earlier has an issue where some cache inhibited
  vector load will return bad data. The workaround is two part, one
  firmware/microcode part triggers HMI interrupts when hitting such
  loads, the other part is this patch which then emulates the
  instructions in Linux.

  The affected instructions are limited to lxvd2x, lxvw4x, lxvb16x and
  lxvh8x.

  When an instruction triggers the HMI, all threads in the core will be
  sent to the HMI handler, not just the one running the vector load.

  In general, these spurious HMIs are detected by the emulation code and
  we just return back to the running process. Unfortunately, if a
  spurious interrupt occurs on a vector load that's to normal memory we
  have no way to detect that it's spurious (unless we walk the page
  tables, which is very expensive). In this case we emulate the load but
  we need do so using a vector load itself to ensure 128bit atomicity is
  preserved.

  Some additional debugfs emulated instruction counters are added also.

  In order to solve this bug, we need to cherry pick the following patch

  
https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git/commit/?h=next=5080332c2c893118dbc18755f35c8b0131cf0fc4

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1721070/+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 1515513] Re: /boot/initrd.img-*.old-dkms files left behind

[Brian Murray]

** Changed in: dkms (Ubuntu)
   Status: Fix Released => In Progress

** Tags removed: verification-needed-xenial verification-needed-zesty
** Tags added: verification-failed-xenial verification-failed-zesty

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

Title:
  /boot/initrd.img-*.old-dkms files left behind

Status in dkms package in Ubuntu:
  In Progress
Status in initramfs-tools package in Ubuntu:
  Confirmed
Status in dkms source package in Xenial:
  Fix Committed
Status in initramfs-tools source package in Xenial:
  New
Status in dkms source package in Zesty:
  Fix Committed
Status in initramfs-tools source package in Zesty:
  New
Status in dkms package in Debian:
  New

Bug description:
  [Impact]
  If a dkms package is installed which has REMAKE_INITRD or the same setting 
has be manually configured by a user then when a kernel is removed its possible 
for an ".old-dkms" file to be left in /boot with no associated kernel.

  [Test Case]
  On a system with two old kernels and one new kernel available in -updates:
  1) install r8168-dkms
  2) install the dkms module for the old kernel e.g. 'sudo dkms install -m 
r8168 -v 8.041.00 -k 4.4.0-31-generic'
  3) upgrade your kernel e.g. "sudo apt install linux-image-generic'
  4) sudo apt autoremove
  5) observe something like "initrd.img-4.4.0-31-generic.old-dkms" in /boot 
without a corresponding "initrd.img-4.4.0-31-generic"

  With the version of dkms in -proposed, the .old-dkms file will be
  removed when the kernel is auto removed.

  [Regression Potential]
  Somebody out there might expect the .old-dkms file to be kept, but that seems 
like an odd expectation.

  One notices *.old-dkms files being left behind still sitting on the
  disk after purging the related kernel. This can cause /boot to become
  full, and when it gets really bad, even sudo apt-get autoremove won't
  fix the problem - only deleting the old-dkms files manually solves the
  problem.

  Note:  Filling up the /boot partition causes updates to fail.

  ProblemType: BugDistroRelease: Ubuntu 15.04
  Package: dkms 2.2.0.3-2ubuntu3.3
  ProcVersionSignature: Ubuntu 3.19.0-28.30-generic 3.19.8-ckt5
  Uname: Linux 3.19.0-28-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1.7
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Thu Nov 12 08:17:10 2015
  InstallationDate: Installed on 2015-05-05 (190 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  PackageArchitecture: allSourcePackage: dkms
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/1515513/+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 1721070] Re: powerpc/64s: Add workaround for P9 vector CI load issuenext

[Breno Leitão]

Joseph,

Which branch did you use? I can't find the commits at master or master-
next:

[root@ltc-wspoon9 ubuntu-artful]# git log --oneline js-master | head -n 20
1e3dad9 UBUNTU: Ubuntu-4.13.0-12.13
1f46464 UBUNTU: [Config] CONFIG_I2C_XLP9XX=m
39ae1ca perf/x86: Fix data source decoding for Skylake
f473bf9 perf/x86: Move Nehalem PEBS code to flag
a8725d5 UBUNTU: [Config] CONFIG_DRM_VBOXVIDEO=n
30d9497 UBUNTU: [Config] Disable CONFIG_IPMMU_VMSA on arm64
806240e scsi: cxlflash: Fix vlun resize failure in the shrink path
69f4910 fs: aio: fix the increment of aio-nr and counting against aio-max-nr
675f3cd UBUNTU: [Config] CONFIG_PINCTRL_DENVERTON=m
ebaccf7 libnvdimm, btt: rework error clearing
4bda159 libnvdimm: fix potential deadlock while clearing errors
adfc036 libnvdimm, btt: cache sector_size in arena_info
b79a931 libnvdimm, btt: ensure that flags were also unchanged during a map_read
45f43c2 libnvdimm, btt: refactor map entry operations with macros
36a7c4e libnvdimm, btt: fix a missed NVDIMM_IO_ATOMIC case in the write path
3f6cafd dax: move all DAX radix tree defs to fs/dax.c
52522e9 dax: remove DAX code from page_cache_tree_insert()
54585e3 dax: use common 4k zero page for dax mmap reads
7b6956d dax: relocate some dax functions
a9342b2 mm: add vm_insert_mixed_mkwrite()


[root@ltc-wspoon9 ubuntu-artful]# git log --oneline js-master-next | head -n 20
f30326f4 UBUNTU: Start new release
ba39ad1 UBUNTU: Ubuntu-4.13.0-15.16
655913c Revert "powerpc/powernv: Add IMC OPAL APIs"
4bab524 Revert "powerpc/powernv: Detect and create IMC device"
192a8d2 Revert "powerpc/perf: Add nest IMC PMU support"
1b9f175 Revert "powerpc/powernv: Add support for powercap framework"
386a56a Revert "powerpc/powernv: Add support to set power-shifting-ratio"
8dc96fd Revert "powerpc/powernv: Enable PCI peer-to-peer"
fdea4c4 Revert "powerpc/powernv/vas: Define macros, register fields and 
structures"
258fa77 Revert "powerpc/powernv: Move GET_FIELD/SET_FIELD to vas.h"
efb0381 Revert "powerpc/powernv/vas: Define vas_init() and vas_exit()"
18c0c36 Revert "powerpc/powernv/vas: Define helpers to access MMIO regions"
b717098 Revert "powerpc/powernv/vas: Define helpers to init window context"
cef2434 Revert "powerpc/powernv/vas: Define helpers to alloc/free windows"
8d6ed22 Revert "powerpc/powernv/vas: Define vas_rx_win_open() interface"
15b835b Revert "powerpc/powernv/vas: Define vas_win_close() interface"
47073e3 Revert "powerpc/powernv/vas: Define vas_tx_win_open()"
5afb9ea Revert "powerpc/powernv/vas: Define copy/paste interfaces"
9cf4ce8 Revert "UBUNTU: [Config] CONFIG_PPC_VAS=y"
b22a1be Revert "crypto/nx: Rename nx842_powernv_function as icswx function"

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

Title:
  powerpc/64s: Add workaround for P9 vector CI load issuenext

Status in The Ubuntu-power-systems project:
  In Progress
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Artful:
  In Progress

Bug description:
  -- Problem Description --
  POWER9 DD2.1 and earlier has an issue where some cache inhibited
  vector load will return bad data. The workaround is two part, one
  firmware/microcode part triggers HMI interrupts when hitting such
  loads, the other part is this patch which then emulates the
  instructions in Linux.

  The affected instructions are limited to lxvd2x, lxvw4x, lxvb16x and
  lxvh8x.

  When an instruction triggers the HMI, all threads in the core will be
  sent to the HMI handler, not just the one running the vector load.

  In general, these spurious HMIs are detected by the emulation code and
  we just return back to the running process. Unfortunately, if a
  spurious interrupt occurs on a vector load that's to normal memory we
  have no way to detect that it's spurious (unless we walk the page
  tables, which is very expensive). In this case we emulate the load but
  we need do so using a vector load itself to ensure 128bit atomicity is
  preserved.

  Some additional debugfs emulated instruction counters are added also.

  In order to solve this bug, we need to cherry pick the following patch

  
https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git/commit/?h=next=5080332c2c893118dbc18755f35c8b0131cf0fc4

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1721070/+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 1721581] Re: general protection fault: 0000 [#1] SMP

[Joseph Salisbury]

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.14 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.14-rc3

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

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

Title:
  general protection fault:  [#1] SMP

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  After trying to install the latest virtualbox modules on kernel
  4.13.0-15-generic

  ProblemType: KernelOops
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-15-generic 4.13.0-15.16
  ProcVersionSignature: Ubuntu 4.13.0-15.16-generic 4.13.4
  Uname: Linux 4.13.0-15-generic x86_64
  Annotation: Your system might become unstable now and might need to be 
restarted.
  ApportVersion: 2.20.7-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  kurt   2054 F pulseaudio
   /dev/snd/controlC0:  kurt   2054 F pulseaudio
  Date: Thu Oct  5 09:08:17 2017
  Failure: oops
  InstallationDate: Installed on 2017-09-27 (7 days ago)
  InstallationMedia: Ubuntu-MATE 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: System manufacturer System Product Name
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-15-generic 
root=UUID=aaffeebb-74e4-459a-97e4-6989dc00c62c ro quiet splash vt.handoff=7
  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
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  Title: general protection fault:  [#1] SMP
  UpgradeStatus: Upgraded to artful on 2017-09-27 (7 days ago)
  dmi.bios.date: 09/07/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3029
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: M4A89TD PRO USB3
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3029:bd09/07/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM4A89TDPROUSB3:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1721581/+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 1721070] Re: powerpc/64s: Add workaround for P9 vector CI load issuenext

[Joseph Salisbury]

The source code for the kernel posted in comment #3 is the ubuntu-artful
repo with commits ccd3cd361 and 5080332c2c89 on top.

The artful repo is available at:
git://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/artful

Both commits were clean picks and did not need back porting.

I also tar'd up the source I used and put it here as the file name 
lp1721070-source.tar:
http://kernel.ubuntu.com/~jsalisbury/lp1721070/

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

Title:
  powerpc/64s: Add workaround for P9 vector CI load issuenext

Status in The Ubuntu-power-systems project:
  In Progress
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Artful:
  In Progress

Bug description:
  -- Problem Description --
  POWER9 DD2.1 and earlier has an issue where some cache inhibited
  vector load will return bad data. The workaround is two part, one
  firmware/microcode part triggers HMI interrupts when hitting such
  loads, the other part is this patch which then emulates the
  instructions in Linux.

  The affected instructions are limited to lxvd2x, lxvw4x, lxvb16x and
  lxvh8x.

  When an instruction triggers the HMI, all threads in the core will be
  sent to the HMI handler, not just the one running the vector load.

  In general, these spurious HMIs are detected by the emulation code and
  we just return back to the running process. Unfortunately, if a
  spurious interrupt occurs on a vector load that's to normal memory we
  have no way to detect that it's spurious (unless we walk the page
  tables, which is very expensive). In this case we emulate the load but
  we need do so using a vector load itself to ensure 128bit atomicity is
  preserved.

  Some additional debugfs emulated instruction counters are added also.

  In order to solve this bug, we need to cherry pick the following patch

  
https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git/commit/?h=next=5080332c2c893118dbc18755f35c8b0131cf0fc4

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1721070/+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 1720359] Re: Controller lockup detected on ProLiant DL380 Gen9 with P440 Controller

[Eric Desrochers]

The GOOD commit (found via a git bisect) is the following :

git show e2c7b433f729cedb32514480af8cbdf2fe5cf264
commit e2c7b433f729cedb32514480af8cbdf2fe5cf264
Author: Yadan Fan 
Date:   Fri Jun 23 17:40:05 2017 +0800

scsi: hpsa: limit transfer length to 1MB

The hpsa firmware will bypass the cache for any request larger than 1MB,
so we should cap the request size to avoid any performance degradation
in kernels later than v4.3

This degradation is caused from d2be537c3ba3568acd79cd178327b842e60d035e,
which changed max_sectors_kb to 1280k, but the hardware is able to work
fine with it, so the true fix should be from hpsa driver.

Signed-off-by: Yadan Fan 
Reviewed-by: Johannes Thumshirn 
Acked-by: Don Brace 
Signed-off-by: Martin K. Petersen 

diff --git a/drivers/scsi/hpsa.c b/drivers/scsi/hpsa.c
index 8914eab..4f7cdb2 100644
--- a/drivers/scsi/hpsa.c
+++ b/drivers/scsi/hpsa.c
@@ -938,7 +938,7 @@ static struct scsi_host_template hpsa_driver_template = {
 #endif
.sdev_attrs = hpsa_sdev_attrs,
.shost_attrs = hpsa_shost_attrs,
-   .max_sectors = 8192,
+   .max_sectors = 1024,
.no_write_same = 1,
 };


** Also affects: linux (Ubuntu Artful)
   Importance: Medium
 Assignee: Eric Desrochers (slashd)
   Status: In Progress

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

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

** Also affects: linux (Ubuntu Zesty)
   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/1720359

Title:
  Controller lockup detected on ProLiant DL380 Gen9 with P440 Controller

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Trusty:
  New
Status in linux source package in Xenial:
  New
Status in linux source package in Zesty:
  New
Status in linux source package in Artful:
  In Progress

Bug description:
  Deploying ceph osd on Trusty/14.04 (LTS) with Ubuntu 4.4 series kernel
  on HP HW[1] system triggers "Controller lockup"[2]

  [1] - HW
  System Information
   Manufacturer: HP
   Product Name: ProLiant DL380 Gen9

  BIOS
    Vendor: HP
    Version: P89
    Release Date: 02/17/2017

  Smart Array Controller
   Smart Array P440 Controller

  [2] - /var/log/kern.log
  ...
  ceph-osd: 2017-09-26 15:34:42.259205 7f99a3d38700  1 heartbeat_map is_healthy 
'FileStore::op_tp thread 0x7f99ad69d700' had timed out after 60
  eph-osd: 2017-09-26 15:34:42.259215 7f99a553b700  1 heartbeat_map is_healthy 
'FileStore::op_tp thread 0x7f99ace9c700' had timed out after 60
  ceph-osd: 2017-09-26 15:34:42.259219 7f99a553b700  1 heartbeat_map is_healthy 
'FileStore::op_tp thread 0x7f99ad69d700' had timed out after 60
  hpsa :08:00.0: Controller lockup detected: 0x00130001 after 30
  hpsa :08:00.0: hpsa_send_abort_ioaccel2: Tag:0x:0190: unknown 
abort service response 0x00
  

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1720359/+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 1721394] Re: Cannot open nvidia-settings on pc with a hybrid device (or use prime-select), missing python

[Doug McMahon]

going to mark invalid, how this install, (Beta amd64 (20170929) ended up 
without python-minimal is unknown.
Could have been from bad behavior from unattended-upgrades. 
For historical info it had been removed as seen here when I installed python
Commit Log for Wed Oct  4 17:19:48 2017


Installed the following packages:
libpython-stdlib (2.7.14-2ubuntu1)
python (2.7.14-2ubuntu1)
python-minimal (2.7.14-2ubuntu1)
python2.7 (2.7.14-2ubuntu2)
python2.7-minimal (2.7.14-2ubuntu2)


** Changed in: nvidia-prime (Ubuntu)
   Status: New => Invalid

** Changed in: nvidia-settings (Ubuntu)
   Status: New => Invalid

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

Title:
  Cannot open nvidia-settings on pc with a hybrid device (or use prime-
  select), missing python

Status in nvidia-prime package in Ubuntu:
  Invalid
Status in nvidia-settings package in Ubuntu:
  Invalid

Bug description:
  You would see -
  $ nvidia-settings
  ** Message: PRIME: Requires offloading
  ** Message: PRIME: is it supported? yes

  ** (nvidia-settings:1848): ERROR **: PRIME error: Failed to execute child 
process “/usr/bin/prime-select” (No such file or directory)
  Trace/breakpoint trap

  Additionally if trying to run prime-select you'd see -
  sudo: unable to execute /usr/bin/prime-select: No such file or directory

  One would need to go
   python3 /usr/bin/prime-select intel

  This is because the python package has been removed from image & isn't
  installed by either nvidia-settings or nvidia-prime.

  Please adjust this packages to either use python3 or dep to python

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: nvidia-settings 367.35-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Oct  4 17:16:44 2017
  InstallationDate: Installed on 2017-10-04 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20170929)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: nvidia-settings
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1721394/+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 1721346] Re: BUG: unable to handle kernel paging request at f84eb3cc

[Clownfishy]

I have just updated to my system and no longer get a freeze after login but
there is a delay after I open say Chrome browser and the GNOME interface
seems to reset itself.  If I try to un maximimise Chrome, it logs me out
and I have to log in again. Just to clarify, I was using the
xserver-xorg-video-nouveau
driver. If I try using the NVIDIA legacy binary driver - version 304.137
driver, there is a massive delay and the system is unusable for about 2
minutes as the screen/gnome seems to be crashing. Once this is finished,
the computer is then fine. I sometimes get a message that GNOME has crashed
but there is not enough memory to produce a report. I am now back using the
xserver-xorg-video-nouveau driver. I had the same problems described above
using 17.04 but not 16.10.

On 5 October 2017 at 17:09, Joseph Salisbury  wrote:

> Do you have a way to reproduce this bug, or was it a one time event?
>
> Would it be possible for you to test the latest upstream kernel? Refer
> to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
> v4.14 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.14-rc3
>
>
> ** Changed in: linux (Ubuntu)
>Importance: Undecided => Medium
>
> ** Changed in: linux (Ubuntu)
>Status: Confirmed => Incomplete
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1721346
>
> Title:
>   BUG: unable to handle kernel paging request at f84eb3cc
>
> Status in linux package in Ubuntu:
>   Incomplete
>
> Bug description:
>   Hangs after I login to linux before providing the GNOME GUI.  Started
>   in recovery mode with lower graphics settings and this works but
>   provided this error after login.
>
>   ProblemType: KernelOops
>   DistroRelease: Ubuntu 17.10
>   Package: linux-image-4.13.0-12-generic 4.13.0-12.13
>   ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
>   Uname: Linux 4.13.0-12-generic i686
>   Annotation: Your system might become unstable now and might need to be
> restarted.
>   ApportVersion: 2.20.7-0ubuntu2
>   Architecture: i386
>   AudioDevicesInUse:
>USERPID ACCESS COMMAND
>/dev/snd/controlC0:  gdm2400 F pulseaudio
> clownfish   2871 F pulseaudio
>   Date: Wed Oct  4 18:15:31 2017
>   DuplicateSignature: BUG: unable to handle kernel paging request at
> location EIP: nvkm_ramht_search+0x68/0xa0 [nouveau]
>   Failure: oops
>   InstallationDate: Installed on 2017-07-25 (71 days ago)
>   InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release i386
> (20170412)
>   MachineType: Dell Inc. Precision M90
>   ProcFB:
>
>   ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-12-generic
> root=UUID=7a8d75fd-cfc9-4561-a976-d3d78d36c120 ro recovery nomodeset
>   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: BUG: unable to handle kernel paging request at f84eb3cc
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   dmi.bios.date: 10/16/2008
>   dmi.bios.vendor: Dell Inc.
>   dmi.bios.version: A08
>   dmi.board.name: 0YD632
>   dmi.board.vendor: Dell Inc.
>   dmi.chassis.type: 8
>   dmi.chassis.vendor: Dell Inc.
>   dmi.modalias: dmi:bvnDellInc.:bvrA08:bd10/16/2008:svnDellInc.:
> pnPrecisionM90:pvr:rvnDellInc.:rn0YD632:rvr:cvnDellInc.:ct8:cvr:
>   dmi.product.name: Precision M90
>   dmi.sys.vendor: Dell Inc.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/
> 1721346/+subscriptions
>


-- 
Kind Regards

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

Title:
  BUG: unable to handle kernel paging request at f84eb3cc

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hangs after I login to linux before providing the GNOME GUI.  Started
  in recovery mode with lower graphics settings and this works but
  provided this error after login.

  ProblemType: KernelOops
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-12-generic 4.13.0-12.13
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic i686
  Annotation: Your system might become unstable now and might need to be 
restarted.
  ApportVersion: 2.20.7-0ubuntu2
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm2400 F pulseaudio
 

[Kernel-packages] [Bug 1515513] Re: /boot/initrd.img-*.old-dkms files left behind

[Brian Murray]

The verification of this has failed as the fix was incorrect.

Removing linux-image-4.10.0-19-generic (4.10.0-19.21) ...
Examining /etc/kernel/prerm.d.
run-parts: executing /etc/kernel/prerm.d/dkms 4.10.0-19-generic 
/boot/vmlinuz-4.10.0-19-generic
removed '/boot/initrd.img-4.10.0-19-generic.old-dkms'
dkms: removing: r8168 8.043.02 (4.10.0-19-generic) (x86_64)

 Uninstall Beginning 
Module:  r8168
Version: 8.043.02
Kernel:  4.10.0-19-generic (x86_64)
-

Status: Before uninstall, this module version was ACTIVE on this kernel.

r8168.ko:
 - Uninstallation
   - Deleting from: /lib/modules/4.10.0-19-generic/updates/dkms/
 - Original module
   - No original module was found for this module on this kernel.
   - Use the dkms install command to reinstall any previous module version.

depmod...

Backing up initrd.img-4.10.0-19-generic to 
/boot/initrd.img-4.10.0-19-generic.old-dkms
Making new initrd.img-4.10.0-19-generic
(If next boot fails, revert to initrd.img-4.10.0-19-generic.old-dkms image)
update-initramfs...

DKMS: uninstall completed.
Examining /etc/kernel/postrm.d .

The .old-dkms file is removed before a new one is created (see the
Backing up bits). So the remove_initrd_backup run needs to be reordered
for after the dkms call.

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

Title:
  /boot/initrd.img-*.old-dkms files left behind

Status in dkms package in Ubuntu:
  Fix Released
Status in initramfs-tools package in Ubuntu:
  Confirmed
Status in dkms source package in Xenial:
  Fix Committed
Status in initramfs-tools source package in Xenial:
  New
Status in dkms source package in Zesty:
  Fix Committed
Status in initramfs-tools source package in Zesty:
  New
Status in dkms package in Debian:
  New

Bug description:
  [Impact]
  If a dkms package is installed which has REMAKE_INITRD or the same setting 
has be manually configured by a user then when a kernel is removed its possible 
for an ".old-dkms" file to be left in /boot with no associated kernel.

  [Test Case]
  On a system with two old kernels and one new kernel available in -updates:
  1) install r8168-dkms
  2) install the dkms module for the old kernel e.g. 'sudo dkms install -m 
r8168 -v 8.041.00 -k 4.4.0-31-generic'
  3) upgrade your kernel e.g. "sudo apt install linux-image-generic'
  4) sudo apt autoremove
  5) observe something like "initrd.img-4.4.0-31-generic.old-dkms" in /boot 
without a corresponding "initrd.img-4.4.0-31-generic"

  With the version of dkms in -proposed, the .old-dkms file will be
  removed when the kernel is auto removed.

  [Regression Potential]
  Somebody out there might expect the .old-dkms file to be kept, but that seems 
like an odd expectation.

  One notices *.old-dkms files being left behind still sitting on the
  disk after purging the related kernel. This can cause /boot to become
  full, and when it gets really bad, even sudo apt-get autoremove won't
  fix the problem - only deleting the old-dkms files manually solves the
  problem.

  Note:  Filling up the /boot partition causes updates to fail.

  ProblemType: BugDistroRelease: Ubuntu 15.04
  Package: dkms 2.2.0.3-2ubuntu3.3
  ProcVersionSignature: Ubuntu 3.19.0-28.30-generic 3.19.8-ckt5
  Uname: Linux 3.19.0-28-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1.7
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Thu Nov 12 08:17:10 2015
  InstallationDate: Installed on 2015-05-05 (190 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  PackageArchitecture: allSourcePackage: dkms
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/1515513/+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 1721070] Re: powerpc/64s: Add workaround for P9 vector CI load issuenext

[Breno Leitão]

Joseph,

Do you have a kernel source for this package that I can take a deeper
look?

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

Title:
  powerpc/64s: Add workaround for P9 vector CI load issuenext

Status in The Ubuntu-power-systems project:
  In Progress
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Artful:
  In Progress

Bug description:
  -- Problem Description --
  POWER9 DD2.1 and earlier has an issue where some cache inhibited
  vector load will return bad data. The workaround is two part, one
  firmware/microcode part triggers HMI interrupts when hitting such
  loads, the other part is this patch which then emulates the
  instructions in Linux.

  The affected instructions are limited to lxvd2x, lxvw4x, lxvb16x and
  lxvh8x.

  When an instruction triggers the HMI, all threads in the core will be
  sent to the HMI handler, not just the one running the vector load.

  In general, these spurious HMIs are detected by the emulation code and
  we just return back to the running process. Unfortunately, if a
  spurious interrupt occurs on a vector load that's to normal memory we
  have no way to detect that it's spurious (unless we walk the page
  tables, which is very expensive). In this case we emulate the load but
  we need do so using a vector load itself to ensure 128bit atomicity is
  preserved.

  Some additional debugfs emulated instruction counters are added also.

  In order to solve this bug, we need to cherry pick the following patch

  
https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git/commit/?h=next=5080332c2c893118dbc18755f35c8b0131cf0fc4

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1721070/+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 1703742] Re: Transparent hugepages should default to enabled=madvise

[Kamal Mostafa]

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

** No longer affects: linux-gke (Ubuntu Yakkety)

** No longer affects: linux-gke (Ubuntu Zesty)

** No longer affects: linux-gke (Ubuntu Artful)

** Changed in: linux-gke (Ubuntu Xenial)
   Status: New => Fix Committed

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

** Changed in: linux-gke (Ubuntu)
   Status: New => Fix Committed

** Changed in: linux-gke (Ubuntu)
 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/1703742

Title:
  Transparent hugepages should default to enabled=madvise

Status in linux package in Ubuntu:
  Fix Released
Status in linux-gke package in Ubuntu:
  Fix Committed
Status in linux source package in Xenial:
  In Progress
Status in linux-gke source package in Xenial:
  Fix Committed
Status in linux source package in Yakkety:
  Won't Fix
Status in linux source package in Zesty:
  In Progress
Status in linux source package in Artful:
  Fix Released

Bug description:
  Ubuntu kernels should default transparent_hugepages to
  enabled=madvise, not enabled=always

  (this corresponds to TRANSPARENT_HUGEPAGE_MADVISE=y in .config).

  I've blogged about this at some length here:
  https://blog.nelhage.com/post/transparent-hugepages/ but here is a
  summary:

  Transparent Hugepages are a feature that allows the kernel to attempt
  to automatically back any anonymous maps with "huge" 2MiB page tables,
  instead of the normal 4k entries. It can produce small net performance
  gains in certain benchmarks, but also has numerous downsides, in the
  form of apparent memory leaks and 30% slowdowns or worse for some
  applications. Many popular pieces of software now refuse to run with
  hugepages enabled because of known performance issues.

  Examples of problem reports:
  MongoDB: https://docs.mongodb.com/manual/tutorial/transparent-huge-pages/
  Oracle: 
https://blogs.oracle.com/linux/entry/performance_issues_with_transparent_huge
  Splunk: 
https://docs.splunk.com/Documentation/Splunk/6.5.2/ReleaseNotes/SplunkandTHP
  Go runtime: https://github.com/golang/go/issues/8832
  jemalloc: 
https://blog.digitalocean.com/transparent-huge-pages-and-alternative-memory-allocators/
  node.js: https://github.com/nodejs/node/issues/11077

  Setting `enabled=madvise` enables applications that know they benefit
  from transparent huge pages to opt-in to this feature, while
  eliminating all the problematic behavior for other applications. Note
  also that transparent hugepage settings don't affect the use of
  explicit hugepages via hugetlbfs or mmap(…, MAP_HUGETLB, …)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1703742/+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 1720930] Re: wlp3s0: failed to remove key (1, ff:ff:ff:ff:ff:ff) from hardware (-22)

[Dylan Borg]

The DKMS isues should be fixable by disabling "AMD Secure Memory
Encryption" i.e. SME support in the 4.14 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/1720930

Title:
  wlp3s0: failed to remove key (1, ff:ff:ff:ff:ff:ff) from hardware
  (-22)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  When running artful on a new Zenbook Pro (uses Intel Wireless 8265), I
  get a hung shutdown with the message "wlp3s0: failed to remove key (1,
  ff:ff:ff:ff:ff:ff) from hardware (-22)". The kernel is also trying to
  load firmware versions that do not exist on the system i.e. versions
  33 then 32 of the firmware. It then seems to load version 31 of the
  firmware. Wireless features seem to work normally. The issues are just
  at shutdown time.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-12-generic 4.13.0-12.13 [modified: 
boot/vmlinuz-4.13.0-12-generic]
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dylan  1621 F pulseaudio
  CurrentDesktop: GNOME
  Date: Tue Oct  3 06:12:13 2017
  HibernationDevice: RESUME=UUID=2b6908b4-d463-4170-9be5-556145c71a0e
  InstallationDate: Installed on 2017-10-02 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20171002)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 002: ID 13d3:5755 IMC Networks 
   Bus 001 Device 004: ID 04f3:0903 Elan Microelectronics Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. UX550VE
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-12-generic 
root=UUID=aa3dfd29-caf8-4882-906e-1b31b672d2c2 ro quiet splash threadirqs 
acpi_osi=! acpi_osi=Linux acpi_backlight=native vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-12-generic N/A
   linux-backports-modules-4.13.0-12-generic  N/A
   linux-firmware 1.168
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/05/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX550VE.300
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX550VE
  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.:bvrUX550VE.300:bd06/05/2017:svnASUSTeKCOMPUTERINC.:pnUX550VE:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX550VE:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: UX
  dmi.product.name: UX550VE
  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/1720930/+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 1710976] Re: Livepatch motd enhancement to show people how livepatch can help protect systems.

[Steve Langasek]

I believe no code changes are needed to the linux package.

** Changed in: linux (Ubuntu)
   Status: Triaged => Invalid

** Changed in: update-notifier (Ubuntu)
   Status: New => Triaged

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

Title:
  Livepatch motd enhancement to show people how livepatch can help
  protect systems.

Status in linux package in Ubuntu:
  Invalid
Status in update-notifier package in Ubuntu:
  Triaged

Bug description:
  This is a request to add an enhancement in our motd.d to inform users
  of the following:

  1) that livepatch is available for their platform/kernel if they don't
  have it set up and installed right now.

  2) When a system is protected by livepatch, and the system is
  currently patched (i.e., canonical-livepatch has active patches
  applied).

  3) when a system is protected by livepatch and no livepatches exist
  yet for the kernel version, a single line message of 'This system is
  protected by canonical-livepatch." or similar.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1710976/+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 1721345] Re: ALC295 codec seems to have Master and PCM channels swapped

[Dylan Borg]

The DKMS isues should be fixable by disabling "AMD Secure Memory
Encryption" i.e. SME support in the 4.14 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/1721345

Title:
  ALC295 codec seems to have Master and PCM channels swapped

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  When trying to use pulseaudio to control volume on my ASUS Zenbook Pro
  UX550VE *uses AC295 audio codec) I noticed that pulseuadio is varying
  the Master ALSA channel. If I vary that channel in alsamixer I get no
  variation in volume. If I vary the PCM channel instead I get the
  desired effect that volume buttons should have. Since pulseaudio
  varies the Master channel by default and does not respect any
  configuration settings telling it to use other settings, I suggest
  swapping these two channels so that pulseaudio works out of the box.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-12-generic 4.13.0-12.13 [modified: 
boot/vmlinuz-4.13.0-12-generic]
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dylan  1532 F pulseaudio
  CurrentDesktop: GNOME
  Date: Wed Oct  4 19:25:38 2017
  HibernationDevice: RESUME=UUID=2b6908b4-d463-4170-9be5-556145c71a0e
  InstallationDate: Installed on 2017-10-02 (1 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20171002)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 002: ID 13d3:5755 IMC Networks 
   Bus 001 Device 004: ID 04f3:0903 Elan Microelectronics Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. UX550VE
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-12-generic 
root=UUID=aa3dfd29-caf8-4882-906e-1b31b672d2c2 ro quiet splash threadirqs 
acpi_osi=! acpi_osi=Linux acpi_backlight=native vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-12-generic N/A
   linux-backports-modules-4.13.0-12-generic  N/A
   linux-firmware 1.168
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/05/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX550VE.300
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX550VE
  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.:bvrUX550VE.300:bd06/05/2017:svnASUSTeKCOMPUTERINC.:pnUX550VE:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX550VE:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: UX
  dmi.product.name: UX550VE
  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/1721345/+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 1710976] Re: Livepatch motd enhancement to show people how livepatch can help protect systems.

[David Britton]

** Changed in: update-notifier (Ubuntu)
 Assignee: Steve Langasek (vorlon) => Andreas Hasenack (ahasenack)

** Changed in: linux (Ubuntu)
 Assignee: Steve Langasek (vorlon) => Andreas Hasenack (ahasenack)

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

Title:
  Livepatch motd enhancement to show people how livepatch can help
  protect systems.

Status in linux package in Ubuntu:
  Triaged
Status in update-notifier package in Ubuntu:
  New

Bug description:
  This is a request to add an enhancement in our motd.d to inform users
  of the following:

  1) that livepatch is available for their platform/kernel if they don't
  have it set up and installed right now.

  2) When a system is protected by livepatch, and the system is
  currently patched (i.e., canonical-livepatch has active patches
  applied).

  3) when a system is protected by livepatch and no livepatches exist
  yet for the kernel version, a single line message of 'This system is
  protected by canonical-livepatch." or similar.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1710976/+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 1721345] Re: ALC295 codec seems to have Master and PCM channels swapped

[Dylan Borg]

This is the installtion output:
dylan@zenbook-pro:~/Downloads/kdebs$ sudo dpkg -i *.deb
[sudo] password for dylan: 
Selecting previously unselected package linux-headers-4.14.0-041400rc3.
(Reading database ... 288569 files and directories currently installed.)
Preparing to unpack 
linux-headers-4.14.0-041400rc3_4.14.0-041400rc3.201710011930_all.deb ...
Unpacking linux-headers-4.14.0-041400rc3 (4.14.0-041400rc3.201710011930) ...
Selecting previously unselected package linux-headers-4.14.0-041400rc3-generic.
Preparing to unpack 
linux-headers-4.14.0-041400rc3-generic_4.14.0-041400rc3.201710011930_amd64.deb 
...
Unpacking linux-headers-4.14.0-041400rc3-generic 
(4.14.0-041400rc3.201710011930) ...
Selecting previously unselected package linux-image-4.14.0-041400rc3-generic.
Preparing to unpack 
linux-image-4.14.0-041400rc3-generic_4.14.0-041400rc3.201710011930_amd64.deb ...
Examining /etc/kernel/preinst.d/
run-parts: executing /etc/kernel/preinst.d/intel-microcode 
4.14.0-041400rc3-generic /boot/vmlinuz-4.14.0-041400rc3-generic
Done.
Unpacking linux-image-4.14.0-041400rc3-generic (4.14.0-041400rc3.201710011930) 
...
Setting up linux-headers-4.14.0-041400rc3 (4.14.0-041400rc3.201710011930) ...
Setting up linux-headers-4.14.0-041400rc3-generic 
(4.14.0-041400rc3.201710011930) ...
Examining /etc/kernel/header_postinst.d.
run-parts: executing /etc/kernel/header_postinst.d/dkms 
4.14.0-041400rc3-generic /boot/vmlinuz-4.14.0-041400rc3-generic
ERROR (dkms apport): kernel package linux-headers-4.14.0-041400rc3-generic is 
not supported
Error! Bad return status for module build on kernel: 4.14.0-041400rc3-generic 
(x86_64)
Consult /var/lib/dkms/nvidia-387/387.12/build/make.log for more information.
Setting up linux-image-4.14.0-041400rc3-generic (4.14.0-041400rc3.201710011930) 
...
Running depmod.
update-initramfs: deferring update (hook will be called later)
Examining /etc/kernel/postinst.d.
run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 
4.14.0-041400rc3-generic /boot/vmlinuz-4.14.0-041400rc3-generic
run-parts: executing /etc/kernel/postinst.d/dkms 4.14.0-041400rc3-generic 
/boot/vmlinuz-4.14.0-041400rc3-generic
ERROR (dkms apport): kernel package linux-headers-4.14.0-041400rc3-generic is 
not supported
Error! Bad return status for module build on kernel: 4.14.0-041400rc3-generic 
(x86_64)
Consult /var/lib/dkms/nvidia-387/387.12/build/make.log for more information.
run-parts: executing /etc/kernel/postinst.d/initramfs-tools 
4.14.0-041400rc3-generic /boot/vmlinuz-4.14.0-041400rc3-generic
update-initramfs: Generating /boot/initrd.img-4.14.0-041400rc3-generic
run-parts: executing /etc/kernel/postinst.d/unattended-upgrades 
4.14.0-041400rc3-generic /boot/vmlinuz-4.14.0-041400rc3-generic
run-parts: executing /etc/kernel/postinst.d/update-notifier 
4.14.0-041400rc3-generic /boot/vmlinuz-4.14.0-041400rc3-generic
run-parts: executing /etc/kernel/postinst.d/zz-update-grub 
4.14.0-041400rc3-generic /boot/vmlinuz-4.14.0-041400rc3-generic
Generating grub configuration file ...
Found linux image: /boot/vmlinuz-4.14.0-041400rc3-generic
Found initrd image: /boot/initrd.img-4.14.0-041400rc3-generic
Found linux image: /boot/vmlinuz-4.13.0-15-generic
Found initrd image: /boot/initrd.img-4.13.0-15-generic
Found linux image: /boot/vmlinuz-4.13.0-14-generic
Found initrd image: /boot/initrd.img-4.13.0-14-generic
Found linux image: /boot/vmlinuz-4.13.0-12-generic
Found initrd image: /boot/initrd.img-4.13.0-12-generic
Found memtest86+ image: /boot/memtest86+.elf
Found memtest86+ image: /boot/memtest86+.bin
done

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

Title:
  ALC295 codec seems to have Master and PCM channels swapped

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  When trying to use pulseaudio to control volume on my ASUS Zenbook Pro
  UX550VE *uses AC295 audio codec) I noticed that pulseuadio is varying
  the Master ALSA channel. If I vary that channel in alsamixer I get no
  variation in volume. If I vary the PCM channel instead I get the
  desired effect that volume buttons should have. Since pulseaudio
  varies the Master channel by default and does not respect any
  configuration settings telling it to use other settings, I suggest
  swapping these two channels so that pulseaudio works out of the box.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-12-generic 4.13.0-12.13 [modified: 
boot/vmlinuz-4.13.0-12-generic]
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dylan  1532 F pulseaudio
  CurrentDesktop: GNOME
  Date: Wed Oct  4 19:25:38 2017
  HibernationDevice: 

[Kernel-packages] [Bug 1721345] Re: ALC295 codec seems to have Master and PCM channels swapped

[Dylan Borg]

NO, this is a fresh install on brand new hardware. Also I need the
nvidia driver to work on thsi system which is impossible for now with
the the 4.14 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/1721345

Title:
  ALC295 codec seems to have Master and PCM channels swapped

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  When trying to use pulseaudio to control volume on my ASUS Zenbook Pro
  UX550VE *uses AC295 audio codec) I noticed that pulseuadio is varying
  the Master ALSA channel. If I vary that channel in alsamixer I get no
  variation in volume. If I vary the PCM channel instead I get the
  desired effect that volume buttons should have. Since pulseaudio
  varies the Master channel by default and does not respect any
  configuration settings telling it to use other settings, I suggest
  swapping these two channels so that pulseaudio works out of the box.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-12-generic 4.13.0-12.13 [modified: 
boot/vmlinuz-4.13.0-12-generic]
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dylan  1532 F pulseaudio
  CurrentDesktop: GNOME
  Date: Wed Oct  4 19:25:38 2017
  HibernationDevice: RESUME=UUID=2b6908b4-d463-4170-9be5-556145c71a0e
  InstallationDate: Installed on 2017-10-02 (1 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20171002)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 002: ID 13d3:5755 IMC Networks 
   Bus 001 Device 004: ID 04f3:0903 Elan Microelectronics Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. UX550VE
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-12-generic 
root=UUID=aa3dfd29-caf8-4882-906e-1b31b672d2c2 ro quiet splash threadirqs 
acpi_osi=! acpi_osi=Linux acpi_backlight=native vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-12-generic N/A
   linux-backports-modules-4.13.0-12-generic  N/A
   linux-firmware 1.168
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/05/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX550VE.300
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX550VE
  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.:bvrUX550VE.300:bd06/05/2017:svnASUSTeKCOMPUTERINC.:pnUX550VE:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX550VE:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: UX
  dmi.product.name: UX550VE
  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/1721345/+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 1721345] Re: ALC295 codec seems to have Master and PCM channels swapped

[Dylan Borg]

** Attachment added: "dkms log"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1721345/+attachment/4963026/+files/make.log

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

Title:
  ALC295 codec seems to have Master and PCM channels swapped

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  When trying to use pulseaudio to control volume on my ASUS Zenbook Pro
  UX550VE *uses AC295 audio codec) I noticed that pulseuadio is varying
  the Master ALSA channel. If I vary that channel in alsamixer I get no
  variation in volume. If I vary the PCM channel instead I get the
  desired effect that volume buttons should have. Since pulseaudio
  varies the Master channel by default and does not respect any
  configuration settings telling it to use other settings, I suggest
  swapping these two channels so that pulseaudio works out of the box.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-12-generic 4.13.0-12.13 [modified: 
boot/vmlinuz-4.13.0-12-generic]
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dylan  1532 F pulseaudio
  CurrentDesktop: GNOME
  Date: Wed Oct  4 19:25:38 2017
  HibernationDevice: RESUME=UUID=2b6908b4-d463-4170-9be5-556145c71a0e
  InstallationDate: Installed on 2017-10-02 (1 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20171002)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 002: ID 13d3:5755 IMC Networks 
   Bus 001 Device 004: ID 04f3:0903 Elan Microelectronics Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. UX550VE
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-12-generic 
root=UUID=aa3dfd29-caf8-4882-906e-1b31b672d2c2 ro quiet splash threadirqs 
acpi_osi=! acpi_osi=Linux acpi_backlight=native vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-12-generic N/A
   linux-backports-modules-4.13.0-12-generic  N/A
   linux-firmware 1.168
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/05/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX550VE.300
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX550VE
  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.:bvrUX550VE.300:bd06/05/2017:svnASUSTeKCOMPUTERINC.:pnUX550VE:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX550VE:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: UX
  dmi.product.name: UX550VE
  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/1721345/+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 1719290] Comment bridged from LTC Bugzilla

[bugproxy]

--- Comment From michael.holz...@de.ibm.com 2017-10-05 12:52 EDT---
(In reply to comment #11)
> @hws @michael.holzheu @schwidefsky
>
> It seems like schwidefsky updated s390 config upstream in v4.12 to remove
> -CONFIG_DEBUG_FS=y for the zfcpdump_defconfig. Meaning any Linux on Z
> systems using v4.12+ default zfcpdump_defconfig from upstream linux source
> tree will get a bad configuration. It seems counter productive to ask all
> downstreams to patch for this config issue.
>
> Are you going to get in touch with schwidefsky to re-introduce
> CONFIG_DEBUG_FS=y in the zfcpdump_defconfig and get it applied in the stable
> trees too?

I already discussed this with Martin Schwidefsky and we decided *not* to
go via stable but instead "warn" Ubuntu explicitly.

AFAIK you are the only official distribution that uses 4.13 for zfcpdump
- therefore IMHO this should be sufficient.

> Also, i believe zfcpdump-kernel that we currently ship does have debugfs
> enabled. Are you using zfcpdump-kernel as provided in ubuntu?

I did not check anything - this bugzilla was just a heads-up.

> But we will
> note and will explicitely enable CONFIG_DEBUG_FS=y when we refress
> zfcpdump-kernel with v4.13+.

Thanks.

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

Title:
  CONFIG_DEBUG_FS is not enabled by "make zfcpdump_defconfig" with
  Ubuntu 17.10 (kernel 4.13)

Status in Ubuntu on IBM z Systems:
  Incomplete
Status in linux package in Ubuntu:
  Fix Committed
Status in linux-hwe package in Ubuntu:
  Incomplete
Status in zfcpdump-kernel package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 17.10 uses kernel 4.13.

  We just found out that on this kernel version CONFIG_DEBUG_FS is not
  enabled by "make zfcpdump_defconfig".

  This makes zfcpdump fail with the following error message:

  ERROR: Unable to mount debugfs 
  No such file or directory

  Patch solving this problem is attached

  As reference following bugzilla
  As reference h
  IBM bugzilla for enabling zfcpdump: 
https://bugzilla.linux.ibm.com/show_bug.cgi?id=139974

  or Launchpad 
  https://bugs.launchpad.net/ubuntu/+source/s390-tools/+bug/1565841

  == Comment: #1 - Heinz-Werner Seeck  -
  2017-09-25 06:00:23 ==

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1719290/+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 1721589] [NEW] same mount-point after rename dataset

[davidak]

Public bug reported:

we renamed a lot of datasets and some of them are still mounted on the
old mount-point.

reboot or zfs-mountservice restart solves it.

---

Ubuntu: 16.04.3 LTS
Kernel: 4.4.0-93-generic
zfsutils-linux: 0.6.5.6-0ubuntu18

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

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

Title:
  same mount-point after rename dataset

Status in zfs-linux package in Ubuntu:
  New

Bug description:
  we renamed a lot of datasets and some of them are still mounted on the
  old mount-point.

  reboot or zfs-mountservice restart solves it.

  ---

  Ubuntu: 16.04.3 LTS
  Kernel: 4.4.0-93-generic
  zfsutils-linux: 0.6.5.6-0ubuntu18

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1721589/+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 1719853] Re: Plantronics P610 does not support sample rate reading

[Tim De Pauw]

That one seems to be working like a treat. No errors in `dmesg` and it
picks up the device as it should in Hangouts on both Chrome and
Chromium.

Just to confirm:

$ uname -a
Linux chowchow 4.13.0-13-generic #14~1719853 SMP Sat Sep 30 23:19:40 CST 2017 
x86_64 x86_64 x86_64 GNU/Linux


** Tags added: kernel-fixed-upstream

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

Title:
  Plantronics P610 does not support sample rate reading

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  As per
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1622763/comments/29
  and https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1709282 , I
  believe the USB ID 0x047F 0xC02F needs to be added to quirks.c in
  order for me to use my Plantronics P610. Thanks!

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

[Ubuntu Kernel Bot]

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

Title:
  general protection fault:  [#1] SMP

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After trying to install the latest virtualbox modules on kernel
  4.13.0-15-generic

  ProblemType: KernelOops
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-15-generic 4.13.0-15.16
  ProcVersionSignature: Ubuntu 4.13.0-15.16-generic 4.13.4
  Uname: Linux 4.13.0-15-generic x86_64
  Annotation: Your system might become unstable now and might need to be 
restarted.
  ApportVersion: 2.20.7-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  kurt   2054 F pulseaudio
   /dev/snd/controlC0:  kurt   2054 F pulseaudio
  Date: Thu Oct  5 09:08:17 2017
  Failure: oops
  InstallationDate: Installed on 2017-09-27 (7 days ago)
  InstallationMedia: Ubuntu-MATE 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: System manufacturer System Product Name
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-15-generic 
root=UUID=aaffeebb-74e4-459a-97e4-6989dc00c62c ro quiet splash vt.handoff=7
  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
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  Title: general protection fault:  [#1] SMP
  UpgradeStatus: Upgraded to artful on 2017-09-27 (7 days ago)
  dmi.bios.date: 09/07/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3029
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: M4A89TD PRO USB3
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3029:bd09/07/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM4A89TDPROUSB3:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1721581/+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 1721582] Re: general protection fault: 0000 [#1] SMP

[Hans Joachim Desserud]

*** This bug is a duplicate of bug 1721581 ***
https://bugs.launchpad.net/bugs/1721581

** This bug has been marked a duplicate of bug 1721581
   general protection fault:  [#1] SMP

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

Title:
  general protection fault:  [#1] SMP

Status in linux package in Ubuntu:
  New

Bug description:
  After trying to install the latest virtualbox modules on kernel
  4.13.0-15-generic

  ProblemType: KernelOops
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-15-generic 4.13.0-15.16
  ProcVersionSignature: Ubuntu 4.13.0-15.16-generic 4.13.4
  Uname: Linux 4.13.0-15-generic x86_64
  Annotation: Your system might become unstable now and might need to be 
restarted.
  ApportVersion: 2.20.7-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  kurt   2054 F pulseaudio
   /dev/snd/controlC0:  kurt   2054 F pulseaudio
  Date: Thu Oct  5 09:08:17 2017
  Failure: oops
  InstallationDate: Installed on 2017-09-27 (7 days ago)
  InstallationMedia: Ubuntu-MATE 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: System manufacturer System Product Name
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-15-generic 
root=UUID=aaffeebb-74e4-459a-97e4-6989dc00c62c ro quiet splash vt.handoff=7
  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
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  Title: general protection fault:  [#1] SMP
  UpgradeStatus: Upgraded to artful on 2017-09-27 (7 days ago)
  dmi.bios.date: 09/07/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3029
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: M4A89TD PRO USB3
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3029:bd09/07/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM4A89TDPROUSB3:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1721582/+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 1721482] Re: watchdog: BUG: soft lockup - CPU#1 stuck for 22s! [CompositorTileW:29904]

[Mynk]

This was a one time thing. Things are smooth now. I really can't put my
finger on what might have caused the problem.

On Thu, Oct 5, 2017 at 9:36 PM, Joseph Salisbury <
joseph.salisb...@canonical.com> wrote:

> Can you reproduce this bug, or was it a one time event?
>
>
> ** Changed in: linux (Ubuntu)
>Importance: Undecided => Medium
>
> ** Changed in: linux (Ubuntu)
>Status: Confirmed => Incomplete
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1721482
>
> Title:
>   watchdog: BUG: soft lockup - CPU#1 stuck for 22s!
>   [CompositorTileW:29904]
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/
> 1721482/+subscriptions
>


-- 
--
मयंक  रुंगटा
MAnY thANKs 
http://www.khulamanch.org/
--

*#MustWatch A Blade of Grass
 - an
amazing talk by Anju Venkat*


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

Title:
  watchdog: BUG: soft lockup - CPU#1 stuck for 22s!
  [CompositorTileW:29904]

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  The system went crazy. Was trying to install gcs-fuse just before
  that. But did not get to it. Just the update command. Not sure if that
  installed something.

  ProblemType: KernelOops
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-12-generic 4.13.0-12.13
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  Annotation: Your system might become unstable now and might need to be 
restarted.
  ApportVersion: 2.20.7-0ubuntu2
  Architecture: amd64
  Date: Thu Oct  5 13:42:59 2017
  Failure: oops
  HibernationDevice: RESUME=UUID=b323f77c-20bc-438b-9710-755bb2592319
  InstallationDate: Installed on 2016-11-11 (327 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  IwConfig:
   enp3s0no wireless extensions.
   
   lono wireless extensions.
  MachineType: Gigabyte Technology Co., Ltd. GA-78LMT-USB3
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-12-generic 
root=UUID=263d9caf-87e3-4a97-beeb-d45e5ded94f6 ro quiet splash
  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
  RfKill:
   
  SourcePackage: linux
  Title: watchdog: BUG: soft lockup - CPU#1 stuck for 22s! 
[CompositorTileW:29904]
  UpgradeStatus: Upgraded to artful on 2017-08-02 (63 days ago)
  dmi.bios.date: 04/23/2013
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: FA
  dmi.board.name: GA-78LMT-USB3
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrFA:bd04/23/2013:svnGigabyteTechnologyCo.,Ltd.:pnGA-78LMT-USB3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-78LMT-USB3:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: GA-78LMT-USB3
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1721482/+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 159968] RE

[Kennedyshead]

Check 
[Bug 159968] Re: ButtonPress and ButtonRelease of button 4 are generated by 
left click of synaptic touch pad

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

Title:
  ButtonPress and ButtonRelease of button 4 are generated by left click
  of synaptic touch pad

Status in linux package in Ubuntu:
  Expired

Bug description:
  I have Xnote C1 which has synaptic touchpad with two buttons - left
  and right button.  Left button acts like scroll down button and right
  button acts like scroll button of mouse.  screen is scrolled down on
  pressing left button and  is scrolled up on pressing right button.

  xev prints the following message when click left button:

  ButtonPress event, serial 31, synthetic NO, window 0x381,
  root 0x1a5, subw 0x0, time 180885017, (53,85), root:(872,643),
  state 0x0, button 4, same_screen YES

  ButtonPress event, serial 31, synthetic NO, window 0x381,
  root 0x1a5, subw 0x0, time 180885092, (53,85), root:(872,643),
  state 0x800, button 1, same_screen YES

  ButtonRelease event, serial 31, synthetic NO, window 0x381,
  root 0x1a5, subw 0x0, time 180885153, (53,85), root:(872,643),
  state 0x900, button 1, same_screen YES

  ButtonRelease event, serial 31, synthetic NO, window 0x381,
  root 0x1a5, subw 0x0, time 180885153, (53,85), root:(872,643),
  state 0x800, button 4, same_screen YES

  
  the following message comes from /proc/bus/input/devices:

  I: Bus=0017 Vendor=0001 Product=0001 Version=0100
  N: Name="Macintosh mouse button emulation"
  P: Phys=
  S: Sysfs=/class/input/input0
  U: Uniq=
  H: Handlers=mouse0 event0 
  B: EV=7
  B: KEY=7 0 0 0 0
  B: REL=3

  I: Bus=0011 Vendor=0001 Product=0001 Version=ab41
  N: Name="AT Translated Set 2 keyboard"
  P: Phys=isa0060/serio0/input0
  S: Sysfs=/class/input/input1
  U: Uniq=
  H: Handlers=kbd event1 
  B: EV=120013
  B: KEY=40200 3802078f840d001 fedfffef fbfe
  B: MSC=10
  B: LED=7

  I: Bus=0011 Vendor=0002 Product=0007 Version=01b1
  N: Name="SynPS/2 Synaptics TouchPad"
  P: Phys=isa0060/serio2/input0
  S: Sysfs=/class/input/input2
  U: Uniq=
  H: Handlers=mouse1 event2 
  B: EV=b
  B: KEY=6420 70003 0 0 0 0
  B: ABS=1103

  I: Bus=0019 Vendor= Product=0002 Version=
  N: Name="Power Button (FF)"
  P: Phys=button_power/button/input0
  S: Sysfs=/class/input/input3
  U: Uniq=
  H: Handlers=kbd event3 
  B: EV=3
  B: KEY=10 0

  I: Bus=0019 Vendor= Product=0005 Version=
  N: Name="Lid Switch"
  P: Phys=PNP0C0D/button/input0
  S: Sysfs=/class/input/input4
  U: Uniq=
  H: Handlers=event4 
  B: EV=21
  B: SW=1

  I: Bus=0019 Vendor= Product=0001 Version=
  N: Name="Power Button (CM)"
  P: Phys=PNP0C0C/button/input0
  S: Sysfs=/class/input/input5
  U: Uniq=
  H: Handlers=kbd event5 
  B: EV=3
  B: KEY=10 0

  I: Bus=0019 Vendor= Product=0003 Version=
  N: Name="Sleep Button (CM)"
  P: Phys=PNP0C0E/button/input0
  S: Sysfs=/class/input/input6
  U: Uniq=
  H: Handlers=kbd event6 
  B: EV=3
  B: KEY=4000 0 0

  synaptic touchpad is configured like the bellow in /etc/X11/xorg.conf:

  Section "InputDevice"
Identifier  "Configured Mouse"
Driver  "mouse"
Option  "CorePointer"
Option  "Device""/dev/input/mice"
Option  "Protocol"  "ImPS/2"
Option  "ZAxisMapping"  "4 5"
Option  "Emulate3Buttons"   "true"
  EndSection

  Section "InputDevice"
Identifier  "Synaptics Touchpad"
Driver  "synaptics"
Option  "SendCoreEvents""true"
Option  "Device""/dev/psaux"
Option  "Protocol"  "auto-dev"
Option  "HorizEdgeScroll"   "0"
Option  "SHMConfig" "on"
  EndSection

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/159968/+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 1237776] Re: EHCI _hcd kernel

[Joseph Salisbury]

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.14 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.14-rc3

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

** Tags added: kernel-da-key

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

Title:
  EHCI _hcd kernel

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I exhausted all resources on how to install or repair ehci_hcd kernel.
  I like more info on what I need done.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1237776/+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 1721345] Re: ALC295 codec seems to have Master and PCM channels swapped

[Joseph Salisbury]

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.14 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.14-rc3

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

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

Title:
  ALC295 codec seems to have Master and PCM channels swapped

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  When trying to use pulseaudio to control volume on my ASUS Zenbook Pro
  UX550VE *uses AC295 audio codec) I noticed that pulseuadio is varying
  the Master ALSA channel. If I vary that channel in alsamixer I get no
  variation in volume. If I vary the PCM channel instead I get the
  desired effect that volume buttons should have. Since pulseaudio
  varies the Master channel by default and does not respect any
  configuration settings telling it to use other settings, I suggest
  swapping these two channels so that pulseaudio works out of the box.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-12-generic 4.13.0-12.13 [modified: 
boot/vmlinuz-4.13.0-12-generic]
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dylan  1532 F pulseaudio
  CurrentDesktop: GNOME
  Date: Wed Oct  4 19:25:38 2017
  HibernationDevice: RESUME=UUID=2b6908b4-d463-4170-9be5-556145c71a0e
  InstallationDate: Installed on 2017-10-02 (1 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20171002)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 002: ID 13d3:5755 IMC Networks 
   Bus 001 Device 004: ID 04f3:0903 Elan Microelectronics Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. UX550VE
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-12-generic 
root=UUID=aa3dfd29-caf8-4882-906e-1b31b672d2c2 ro quiet splash threadirqs 
acpi_osi=! acpi_osi=Linux acpi_backlight=native vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-12-generic N/A
   linux-backports-modules-4.13.0-12-generic  N/A
   linux-firmware 1.168
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/05/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX550VE.300
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX550VE
  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.:bvrUX550VE.300:bd06/05/2017:svnASUSTeKCOMPUTERINC.:pnUX550VE:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX550VE:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: UX
  dmi.product.name: UX550VE
  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/1721345/+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 1721400] Re: Screen dim during encryption unlock prompt

[Joseph Salisbury]

Does this issue go away if you boot back into the prior kernel?

Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.14 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.14-rc3


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

** Tags added: kernel-da-key

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

** Also affects: linux (Ubuntu Artful)
   Importance: Medium
   Status: 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/1721400

Title:
  Screen dim during encryption unlock prompt

Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Artful:
  Incomplete

Bug description:
  In Artful, since 4.13 kernel, the screen gets super dim after the grub
  prompt while displaying the  hard drive encryption unlock screen.
  Soon after unlocking the hard drive, the screen returns to normal
  brightness, but it's hard to even see that the unlock screen is being
  displayed.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-12-generic 4.13.0-12.13
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  ApportVersion: 2.20.7-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  jbarnett   2842 F pulseaudio
   /dev/snd/controlC3:  jbarnett   2842 F pulseaudio
   /dev/snd/controlC0:  jbarnett   2842 F pulseaudio
   /dev/snd/controlC1:  jbarnett   2842 F pulseaudio
  CurrentDesktop: GNOME
  Date: Wed Oct  4 14:36:01 2017
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=dd225ec0-47f4-49d8-a51c-a2547f8eb945
  InstallationDate: Installed on 2015-08-21 (775 days ago)
  InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Alpha amd64 (20150819)
  MachineType: Apple Inc. MacBookPro11,4
  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=/vmlinuz-4.13.0-12-generic.efi.signed 
root=/dev/mapper/ubuntu--gnome--vg-root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-12-generic N/A
   linux-backports-modules-4.13.0-12-generic  N/A
   linux-firmware 1.168
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/05/2015
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MBP114.88Z.0172.B04.1506051511
  dmi.board.name: Mac-06F11FD93F0323C5
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookPro11,4
  dmi.chassis.type: 9
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-06F11FD93F0323C5
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMBP114.88Z.0172.B04.1506051511:bd06/05/2015:svnAppleInc.:pnMacBookPro11,4:pvr1.0:rvnAppleInc.:rnMac-06F11FD93F0323C5:rvrMacBookPro11,4:cvnAppleInc.:ct9:cvrMac-06F11FD93F0323C5:
  dmi.product.family: MacBook Pro
  dmi.product.name: MacBookPro11,4
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1721400/+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 1721314] Re: general protection fault: 0000 [#1] SMP

[Joseph Salisbury]

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.14 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.14-rc3

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

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

Title:
  general protection fault:  [#1] SMP

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Computer froze up, had to hard restart.

  ProblemType: KernelOops
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-12-generic 4.13.0-12.13
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  Annotation: Your system might become unstable now and might need to be 
restarted.
  ApportVersion: 2.20.7-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  kurt   1539 F pulseaudio
   /dev/snd/controlC0:  kurt   1539 F pulseaudio
  Date: Wed Oct  4 09:47:06 2017
  Failure: oops
  InstallationDate: Installed on 2017-09-27 (7 days ago)
  InstallationMedia: Ubuntu-MATE 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: System manufacturer System Product Name
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-12-generic 
root=UUID=aaffeebb-74e4-459a-97e4-6989dc00c62c ro quiet splash vt.handoff=7
  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
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  Title: general protection fault:  [#1] SMP
  UpgradeStatus: Upgraded to artful on 2017-09-27 (7 days ago)
  dmi.bios.date: 09/07/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3029
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: M4A89TD PRO USB3
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3029:bd09/07/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM4A89TDPROUSB3:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1721314/+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 1721482] Re: watchdog: BUG: soft lockup - CPU#1 stuck for 22s! [CompositorTileW:29904]

[Joseph Salisbury]

Can you reproduce this bug, or was it a one time event?


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

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

Title:
  watchdog: BUG: soft lockup - CPU#1 stuck for 22s!
  [CompositorTileW:29904]

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  The system went crazy. Was trying to install gcs-fuse just before
  that. But did not get to it. Just the update command. Not sure if that
  installed something.

  ProblemType: KernelOops
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-12-generic 4.13.0-12.13
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  Annotation: Your system might become unstable now and might need to be 
restarted.
  ApportVersion: 2.20.7-0ubuntu2
  Architecture: amd64
  Date: Thu Oct  5 13:42:59 2017
  Failure: oops
  HibernationDevice: RESUME=UUID=b323f77c-20bc-438b-9710-755bb2592319
  InstallationDate: Installed on 2016-11-11 (327 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  IwConfig:
   enp3s0no wireless extensions.
   
   lono wireless extensions.
  MachineType: Gigabyte Technology Co., Ltd. GA-78LMT-USB3
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-12-generic 
root=UUID=263d9caf-87e3-4a97-beeb-d45e5ded94f6 ro quiet splash
  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
  RfKill:
   
  SourcePackage: linux
  Title: watchdog: BUG: soft lockup - CPU#1 stuck for 22s! 
[CompositorTileW:29904]
  UpgradeStatus: Upgraded to artful on 2017-08-02 (63 days ago)
  dmi.bios.date: 04/23/2013
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: FA
  dmi.board.name: GA-78LMT-USB3
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrFA:bd04/23/2013:svnGigabyteTechnologyCo.,Ltd.:pnGA-78LMT-USB3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-78LMT-USB3:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: GA-78LMT-USB3
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1721482/+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 1721271] Re: Bluetooth and Wifi: coexistence Problem

[Joseph Salisbury]

This issue appears to be an upstream bug, since you tested the latest
upstream kernel. Would it be possible for you to open an upstream bug
report[0]? That will allow the upstream Developers to examine the issue,
and may provide a quicker resolution to the bug.

Please follow the instructions on the wiki page[0]. The first step is to
email the appropriate mailing list. If no response is received, then a
bug may be opened on bugzilla.kernel.org.

Once this bug is reported upstream, please add the tag: 'kernel-bug-
reported-upstream'.

[0] https://wiki.ubuntu.com/Bugs/Upstream/kernel

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

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

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

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

Title:
  Bluetooth and Wifi: coexistence Problem

Status in linux package in Ubuntu:
  Triaged

Bug description:
  I'm currently running kernel 4.13.0-12 on Ubuntu 17.10 (daily) and
  have noticed that with my Intel Corporation Wireless 8260 (rev 3a)
  there appears to be a problem with buetooth and wifi coexistence.

  Unless I disable bluetooth and/or wifi I am unable to connect to the
  opposite to which I have disabled.

  Adding:

  options iwlwifi bt_coex_active=0 swcrypto=1 11n_disable=8

  To:

  /etc/modprobe.d/iwlwifi.conf

  Solve the problem. This is a reversion to less functionality as on
  earlier kernels (default kernel on 17.04) this did not occur.

  This would appear to be a problem that has previously been identified
  with earlier versions of the Intel hardware (see
  https://wiki.debian.org/iwlwifi#Troubleshooting) but not with the
  8260.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-12-generic 4.13.0-12.13 [modified: 
boot/vmlinuz-4.13.0-12-generic]
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  ApportVersion: 2.20.7-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jdtanner   1141 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Oct  4 15:44:16 2017
  InstallationDate: Installed on 2017-10-03 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20170930)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2b Intel Corp.
   Bus 001 Device 002: ID 05c8:03a2 Cheng Uei Precision Industry Co., Ltd 
(Foxlink)
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Timi TM1613
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-12-generic 
root=UUID=a5c4f10c-8a3a-4c18-b858-a72fd6c5aa2c ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-12-generic N/A
   linux-backports-modules-4.13.0-12-generic  N/A
   linux-firmware 1.168
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/28/2016
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: A06
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: TM1613
  dmi.board.vendor: Timi
  dmi.board.version: A06
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Timi
  dmi.chassis.version: A06
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrA06:bd10/28/2016:svnTimi:pnTM1613:pvrA06:rvnTimi:rnTM1613:rvrA06:cvnTimi:ct10:cvrA06:
  dmi.product.family: Timibook
  dmi.product.name: TM1613
  dmi.product.version: A06
  dmi.sys.vendor: Timi

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1721271/+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 1721346] Re: BUG: unable to handle kernel paging request at f84eb3cc

[Joseph Salisbury]

Do you have a way to reproduce this bug, or was it a one time event?

Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.14 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.14-rc3


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

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

Title:
  BUG: unable to handle kernel paging request at f84eb3cc

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hangs after I login to linux before providing the GNOME GUI.  Started
  in recovery mode with lower graphics settings and this works but
  provided this error after login.

  ProblemType: KernelOops
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-12-generic 4.13.0-12.13
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic i686
  Annotation: Your system might become unstable now and might need to be 
restarted.
  ApportVersion: 2.20.7-0ubuntu2
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm2400 F pulseaudio
clownfish   2871 F pulseaudio
  Date: Wed Oct  4 18:15:31 2017
  DuplicateSignature: BUG: unable to handle kernel paging request at location 
EIP: nvkm_ramht_search+0x68/0xa0 [nouveau]
  Failure: oops
  InstallationDate: Installed on 2017-07-25 (71 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release i386 (20170412)
  MachineType: Dell Inc. Precision M90
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-12-generic 
root=UUID=7a8d75fd-cfc9-4561-a976-d3d78d36c120 ro recovery nomodeset
  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: BUG: unable to handle kernel paging request at f84eb3cc
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/16/2008
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A08
  dmi.board.name: 0YD632
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA08:bd10/16/2008:svnDellInc.:pnPrecisionM90:pvr:rvnDellInc.:rn0YD632:rvr:cvnDellInc.:ct8:cvr:
  dmi.product.name: Precision M90
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1721346/+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 1721582] [NEW] general protection fault: 0000 [#1] SMP

[Kurt Semler]

Public bug reported:

After trying to install the latest virtualbox modules on kernel
4.13.0-15-generic

ProblemType: KernelOops
DistroRelease: Ubuntu 17.10
Package: linux-image-4.13.0-15-generic 4.13.0-15.16
ProcVersionSignature: Ubuntu 4.13.0-15.16-generic 4.13.4
Uname: Linux 4.13.0-15-generic x86_64
Annotation: Your system might become unstable now and might need to be 
restarted.
ApportVersion: 2.20.7-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  kurt   2054 F pulseaudio
 /dev/snd/controlC0:  kurt   2054 F pulseaudio
Date: Thu Oct  5 09:08:17 2017
Failure: oops
InstallationDate: Installed on 2017-09-27 (7 days ago)
InstallationMedia: Ubuntu-MATE 17.04 "Zesty Zapus" - Release amd64 (20170412)
MachineType: System manufacturer System Product Name
ProcFB: 0 nouveaufb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-15-generic 
root=UUID=aaffeebb-74e4-459a-97e4-6989dc00c62c ro quiet splash vt.handoff=7
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
RfKill:
 0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
SourcePackage: linux
Title: general protection fault:  [#1] SMP
UpgradeStatus: Upgraded to artful on 2017-09-27 (7 days ago)
dmi.bios.date: 09/07/2012
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 3029
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: M4A89TD PRO USB3
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3029:bd09/07/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM4A89TDPROUSB3:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.family: To Be Filled By O.E.M.
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer

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


** Tags: amd64 apport-kerneloops artful kernel-oops package-from-proposed

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

Title:
  general protection fault:  [#1] SMP

Status in linux package in Ubuntu:
  New

Bug description:
  After trying to install the latest virtualbox modules on kernel
  4.13.0-15-generic

  ProblemType: KernelOops
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-15-generic 4.13.0-15.16
  ProcVersionSignature: Ubuntu 4.13.0-15.16-generic 4.13.4
  Uname: Linux 4.13.0-15-generic x86_64
  Annotation: Your system might become unstable now and might need to be 
restarted.
  ApportVersion: 2.20.7-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  kurt   2054 F pulseaudio
   /dev/snd/controlC0:  kurt   2054 F pulseaudio
  Date: Thu Oct  5 09:08:17 2017
  Failure: oops
  InstallationDate: Installed on 2017-09-27 (7 days ago)
  InstallationMedia: Ubuntu-MATE 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: System manufacturer System Product Name
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-15-generic 
root=UUID=aaffeebb-74e4-459a-97e4-6989dc00c62c ro quiet splash vt.handoff=7
  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
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  Title: general protection fault:  [#1] SMP
  UpgradeStatus: Upgraded to artful on 2017-09-27 (7 days ago)
  dmi.bios.date: 09/07/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3029
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: M4A89TD PRO USB3
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3029:bd09/07/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM4A89TDPROUSB3:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

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

[Kernel-packages] [Bug 1690085] Re: Ryzen 1800X freeze - rcu_sched detected stalls on CPUs/tasks

[Stuart Page]

I finally managed to figure out how to compile a kernel with RCU_NOCB
and disabled ASLR as Alex Jones mentioned, and it appears to have worked
for me and another guy who helped me put the tutorial together:

http://blog.programster.org/ubuntu-16-04-compile-custom-kernel-for-ryzen

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

Title:
  Ryzen 1800X freeze - rcu_sched detected stalls on CPUs/tasks

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

Bug description:
  Hi,

  
  We aregetting various kernel crash on a pretty new config.
  We're using Ryzen 1800X CPU with X370 Gaming Pro Carbon MB (7A32V1) using 
latest BIOS available (1.52)

  We are running Ubuntu 17.04 (amd64), we've tried different kernel version, 
native one and releases from http://kernel.ubuntu.com/~kernel-ppa/mainline/ too.
  Tested kernel version:

  native 17.04 kernel
  4.10.15

  Issues are the same, we're getting random freeze on the machine.

  Here is kern.log entry when happening :

  May 10 22:41:56 dev2 kernel: [24366.186246] INFO: rcu_sched detected stalls 
on CPUs/tasks:
  May 10 22:41:56 dev2 kernel: [24366.187618] 0-...: (1 GPs behind) 
idle=49b/1/0 softirq=28561/28563 fqs=913449
  May 10 22:41:56 dev2 kernel: [24366.188977] (detected by 12, t=1860207 
jiffies, g=10001, c=1, q=4656)
  May 10 22:41:56 dev2 kernel: [24366.190344] Task dump for CPU 0:
  May 10 22:41:56 dev2 kernel: [24366.190345] swapper/0   R  running task   
 0 0  0 0x0008
  May 10 22:41:56 dev2 kernel: [24366.190348] Call Trace:
  May 10 22:41:56 dev2 kernel: [24366.190354]  ? native_safe_halt+0x6/0x10
  May 10 22:41:56 dev2 kernel: [24366.190355]  ? default_idle+0x20/0xd0
  May 10 22:41:56 dev2 kernel: [24366.190358]  ? arch_cpu_idle+0xf/0x20
  May 10 22:41:56 dev2 kernel: [24366.190360]  ? default_idle_call+0x23/0x30
  May 10 22:41:56 dev2 kernel: [24366.190362]  ? do_idle+0x16f/0x200
  May 10 22:41:56 dev2 kernel: [24366.190364]  ? cpu_startup_entry+0x71/0x80
  May 10 22:41:56 dev2 kernel: [24366.190366]  ? rest_init+0x77/0x80
  May 10 22:41:56 dev2 kernel: [24366.190368]  ? start_kernel+0x464/0x485
  May 10 22:41:56 dev2 kernel: [24366.190369]  ? 
early_idt_handler_array+0x120/0x120
  May 10 22:41:56 dev2 kernel: [24366.190371]  ? 
x86_64_start_reservations+0x24/0x26
  May 10 22:41:56 dev2 kernel: [24366.190372]  ? x86_64_start_kernel+0x14d/0x170
  May 10 22:41:56 dev2 kernel: [24366.190373]  ? start_cpu+0x14/0x14
  May 10 22:44:56 dev2 kernel: [24546.188093] INFO: rcu_sched detected stalls 
on CPUs/tasks:
  May 10 22:44:56 dev2 kernel: [24546.189461] 0-...: (1 GPs behind) 
idle=49b/1/0 softirq=28561/28563 fqs=935027
  May 10 22:44:56 dev2 kernel: [24546.190823] (detected by 14, t=1905212 
jiffies, g=10001, c=1, q=4740)
  May 10 22:44:56 dev2 kernel: [24546.192191] Task dump for CPU 0:
  May 10 22:44:56 dev2 kernel: [24546.192192] swapper/0   R  running task   
 0 0  0 0x0008
  May 10 22:44:56 dev2 kernel: [24546.192195] Call Trace:
  May 10 22:44:56 dev2 kernel: [24546.192199]  ? native_safe_halt+0x6/0x10
  May 10 22:44:56 dev2 kernel: [24546.192201]  ? default_idle+0x20/0xd0
  May 10 22:44:56 dev2 kernel: [24546.192203]  ? arch_cpu_idle+0xf/0x20
  May 10 22:44:56 dev2 kernel: [24546.192204]  ? default_idle_call+0x23/0x30
  May 10 22:44:56 dev2 kernel: [24546.192206]  ? do_idle+0x16f/0x200
  May 10 22:44:56 dev2 kernel: [24546.192208]  ? cpu_startup_entry+0x71/0x80
  May 10 22:44:56 dev2 kernel: [24546.192210]  ? rest_init+0x77/0x80
  May 10 22:44:56 dev2 kernel: [24546.192211]  ? start_kernel+0x464/0x485
  May 10 22:44:56 dev2 kernel: [24546.192213]  ? 
early_idt_handler_array+0x120/0x120
  May 10 22:44:56 dev2 kernel: [24546.192214]  ? 
x86_64_start_reservations+0x24/0x26
  May 10 22:44:56 dev2 kernel: [24546.192215]  ? x86_64_start_kernel+0x14d/0x170
  May 10 22:44:56 dev2 kernel: [24546.192217]  ? start_cpu+0x14/0x14

  Depending on the kernel version, we've got NMI watchdog errors related to CPU 
stuck (mentioning the CPU core id, which is random).
  Crash is happening randomly, but in general after some hours (3-4h).

  Now, we've installed kernel 4.11.0-041100-generic #201705041534 this morning 
and waiting for crash...
  For now, the machine is not "used", at least, it's not CPU stressed...

  
  Thanks
  --- 
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  DistroRelease: Ubuntu 17.04
  InstallationDate: Installed on 2017-05-09 (1 days ago)
  InstallationMedia: Ubuntu-Server 17.04 "Zesty Zapus" - Release amd64 
(20170412)
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  Tags:  zesty
  Uname: Linux 4.11.0-041100-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log 

[Kernel-packages] [Bug 1721349] Re: BUG: Bad rss-counter state mm:ffff9cc26037c000 idx:2 val:-96

[Joseph Salisbury]

Do you have a way to reproduce this bug, or was it a one time event?

Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.14 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.14-rc3


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

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

Title:
  BUG: Bad rss-counter state mm:9cc26037c000 idx:2 val:-96

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  apport showed up on login

  ProblemType: KernelOops
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-12-generic 4.13.0-12.13 [modified: 
boot/vmlinuz-4.13.0-12-generic]
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Annotation: Your system might become unstable now and might need to be 
restarted.
  ApportVersion: 2.20.7-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm1121 F pulseaudio
dylan  1539 F pulseaudio
  Date: Wed Oct  4 07:46:08 2017
  Failure: oops
  HibernationDevice: RESUME=UUID=2b6908b4-d463-4170-9be5-556145c71a0e
  InstallationDate: Installed on 2017-10-02 (1 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20171002)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 002: ID 13d3:5755 IMC Networks 
   Bus 001 Device 004: ID 04f3:0903 Elan Microelectronics Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. UX550VE
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-12-generic 
root=UUID=aa3dfd29-caf8-4882-906e-1b31b672d2c2 ro quiet splash threadirqs 
acpi_osi=! acpi_osi=Linux acpi_backlight=native vt.handoff=7
  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: BUG: Bad rss-counter state mm:9cc26037c000 idx:2 val:-96
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/05/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX550VE.300
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX550VE
  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.:bvrUX550VE.300:bd06/05/2017:svnASUSTeKCOMPUTERINC.:pnUX550VE:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX550VE:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: UX
  dmi.product.name: UX550VE
  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/1721349/+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 1721581] [NEW] general protection fault: 0000 [#1] SMP

[Kurt Semler]

Public bug reported:

After trying to install the latest virtualbox modules on kernel
4.13.0-15-generic

ProblemType: KernelOops
DistroRelease: Ubuntu 17.10
Package: linux-image-4.13.0-15-generic 4.13.0-15.16
ProcVersionSignature: Ubuntu 4.13.0-15.16-generic 4.13.4
Uname: Linux 4.13.0-15-generic x86_64
Annotation: Your system might become unstable now and might need to be 
restarted.
ApportVersion: 2.20.7-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  kurt   2054 F pulseaudio
 /dev/snd/controlC0:  kurt   2054 F pulseaudio
Date: Thu Oct  5 09:08:17 2017
Failure: oops
InstallationDate: Installed on 2017-09-27 (7 days ago)
InstallationMedia: Ubuntu-MATE 17.04 "Zesty Zapus" - Release amd64 (20170412)
MachineType: System manufacturer System Product Name
ProcFB: 0 nouveaufb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-15-generic 
root=UUID=aaffeebb-74e4-459a-97e4-6989dc00c62c ro quiet splash vt.handoff=7
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
RfKill:
 0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
SourcePackage: linux
Title: general protection fault:  [#1] SMP
UpgradeStatus: Upgraded to artful on 2017-09-27 (7 days ago)
dmi.bios.date: 09/07/2012
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 3029
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: M4A89TD PRO USB3
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3029:bd09/07/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM4A89TDPROUSB3:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.family: To Be Filled By O.E.M.
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer

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


** Tags: amd64 apport-kerneloops artful kernel-oops package-from-proposed

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

Title:
  general protection fault:  [#1] SMP

Status in linux package in Ubuntu:
  New

Bug description:
  After trying to install the latest virtualbox modules on kernel
  4.13.0-15-generic

  ProblemType: KernelOops
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-15-generic 4.13.0-15.16
  ProcVersionSignature: Ubuntu 4.13.0-15.16-generic 4.13.4
  Uname: Linux 4.13.0-15-generic x86_64
  Annotation: Your system might become unstable now and might need to be 
restarted.
  ApportVersion: 2.20.7-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  kurt   2054 F pulseaudio
   /dev/snd/controlC0:  kurt   2054 F pulseaudio
  Date: Thu Oct  5 09:08:17 2017
  Failure: oops
  InstallationDate: Installed on 2017-09-27 (7 days ago)
  InstallationMedia: Ubuntu-MATE 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: System manufacturer System Product Name
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-15-generic 
root=UUID=aaffeebb-74e4-459a-97e4-6989dc00c62c ro quiet splash vt.handoff=7
  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
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  Title: general protection fault:  [#1] SMP
  UpgradeStatus: Upgraded to artful on 2017-09-27 (7 days ago)
  dmi.bios.date: 09/07/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3029
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: M4A89TD PRO USB3
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3029:bd09/07/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM4A89TDPROUSB3:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

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

[Kernel-packages] [Bug 1721483] Re: watchdog: BUG: soft lockup - CPU#1 stuck for 22s! [CompositorTileW:29904]

[Joseph Salisbury]

*** This bug is a duplicate of bug 1721482 ***
https://bugs.launchpad.net/bugs/1721482

** This bug has been marked a duplicate of bug 1721482
   watchdog: BUG: soft lockup - CPU#1 stuck for 22s! [CompositorTileW:29904]

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

Title:
  watchdog: BUG: soft lockup - CPU#1 stuck for 22s!
  [CompositorTileW:29904]

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  One issue has led to the collapse of the system. Multiple bugs being
  reported.

  ProblemType: KernelOops
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-12-generic 4.13.0-12.13
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  Annotation: Your system might become unstable now and might need to be 
restarted.
  ApportVersion: 2.20.7-0ubuntu2
  Architecture: amd64
  Date: Thu Oct  5 13:49:05 2017
  Failure: oops
  HibernationDevice: RESUME=UUID=b323f77c-20bc-438b-9710-755bb2592319
  InstallationDate: Installed on 2016-11-11 (327 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  IwConfig:
   enp3s0no wireless extensions.
   
   lono wireless extensions.
  MachineType: Gigabyte Technology Co., Ltd. GA-78LMT-USB3
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-12-generic 
root=UUID=263d9caf-87e3-4a97-beeb-d45e5ded94f6 ro quiet splash
  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
  RfKill:
   
  SourcePackage: linux
  Title: watchdog: BUG: soft lockup - CPU#1 stuck for 22s! 
[CompositorTileW:29904]
  UpgradeStatus: Upgraded to artful on 2017-08-02 (63 days ago)
  dmi.bios.date: 04/23/2013
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: FA
  dmi.board.name: GA-78LMT-USB3
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrFA:bd04/23/2013:svnGigabyteTechnologyCo.,Ltd.:pnGA-78LMT-USB3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-78LMT-USB3:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: GA-78LMT-USB3
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1721483/+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 1721350] Re: BUG: Bad rss-counter state mm:ffff9cc26037c000 idx:2 val:-96

[Joseph Salisbury]

*** This bug is a duplicate of bug 1721349 ***
https://bugs.launchpad.net/bugs/1721349

** This bug has been marked a duplicate of bug 1721349
   BUG: Bad rss-counter state mm:9cc26037c000 idx:2 val:-96

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

Title:
  BUG: Bad rss-counter state mm:9cc26037c000 idx:2 val:-96

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  apport showed up on login

  ProblemType: KernelOops
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-12-generic 4.13.0-12.13 [modified: 
boot/vmlinuz-4.13.0-12-generic]
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Annotation: Your system might become unstable now and might need to be 
restarted.
  ApportVersion: 2.20.7-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm1121 F pulseaudio
dylan  1539 F pulseaudio
  Date: Wed Oct  4 07:45:08 2017
  Failure: oops
  HibernationDevice: RESUME=UUID=2b6908b4-d463-4170-9be5-556145c71a0e
  InstallationDate: Installed on 2017-10-02 (1 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20171002)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 002: ID 13d3:5755 IMC Networks 
   Bus 001 Device 004: ID 04f3:0903 Elan Microelectronics Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. UX550VE
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-12-generic 
root=UUID=aa3dfd29-caf8-4882-906e-1b31b672d2c2 ro quiet splash threadirqs 
acpi_osi=! acpi_osi=Linux acpi_backlight=native vt.handoff=7
  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: BUG: Bad rss-counter state mm:9cc26037c000 idx:2 val:-96
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/05/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX550VE.300
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX550VE
  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.:bvrUX550VE.300:bd06/05/2017:svnASUSTeKCOMPUTERINC.:pnUX550VE:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX550VE:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: UX
  dmi.product.name: UX550VE
  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/1721350/+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 1719731] Re: Suspending Lubuntu 16.04.3 results in network manager stops working

[Mark]

Also is there any chance that the error is linked to
https://ubuntuforums.org/showthread.php?t=2371537 where I reported that
I cannot connect to a specific wifi (I can on Windows 10 though) and a
specific router?

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

Title:
  Suspending Lubuntu 16.04.3 results in network manager stops working

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hello, as per title I noticed that when I suspend Lubuntu 16.04.3 the
  network manager stops working or better it behaves weird. I noticed 4
  behaviors in different occasions:

  1) Enable networking and enable wifi are toggled but the connection I
  used before suspending is not shown (others are).

  2) Enable networking and enable wifi are toggled but no Wi-Fi
  connections are displayed.

  3) The icon changes to loading but it gets stuck, sometimes it just
  stays like that until I restart the network manager or sometimes it
  unstucks and connects, but instead of showing the "internet bars" for
  Wi-Fi it shows the icon as when you connect to a wired connection.

  3)The network manager menu is grey and you can't click anything (no
  connections are shown).

  The only way I have is either to restart nm-applet or restart Lubuntu.

  I have seen this behavior for maybe 3 days, therefore I am assuming
  one package was updated and the update messes up with the suspending
  system.

  The Network Manager I have is 1.2.6-0ubuntu0.16.04.1 and Xfce Power
  Manager is 1.4.4-4ubuntu2.

  Can someone investigate?
  Has anyone else experienced this? 
  If more info are needed I will try to do my best :)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1719731/+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 1719731] Re: Suspending Lubuntu 16.04.3 results in network manager stops working

[Mark]

Hello sorry for the late reply.

I am not familiar with playing around the upstream kernel, this is my
only machine and I cannot break anything :/

I have another kernerl version: Linux 4.4.0-93-generic I tried and it
has the same behavior.

Today I notice that Power Manager shows a GDBUS.Error, so maybe that's
the problem?

I attached a screenshot where you can see the complete error:
https://s1.postimg.org/2p5omsk99b/Screenshot_from_2017-10-05_16-38-41.png


As you can see at the bottom the icon displayed is the one used for wired 
networks however I am connected to a wifi network.

Hope it helps.

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

Title:
  Suspending Lubuntu 16.04.3 results in network manager stops working

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hello, as per title I noticed that when I suspend Lubuntu 16.04.3 the
  network manager stops working or better it behaves weird. I noticed 4
  behaviors in different occasions:

  1) Enable networking and enable wifi are toggled but the connection I
  used before suspending is not shown (others are).

  2) Enable networking and enable wifi are toggled but no Wi-Fi
  connections are displayed.

  3) The icon changes to loading but it gets stuck, sometimes it just
  stays like that until I restart the network manager or sometimes it
  unstucks and connects, but instead of showing the "internet bars" for
  Wi-Fi it shows the icon as when you connect to a wired connection.

  3)The network manager menu is grey and you can't click anything (no
  connections are shown).

  The only way I have is either to restart nm-applet or restart Lubuntu.

  I have seen this behavior for maybe 3 days, therefore I am assuming
  one package was updated and the update messes up with the suspending
  system.

  The Network Manager I have is 1.2.6-0ubuntu0.16.04.1 and Xfce Power
  Manager is 1.4.4-4ubuntu2.

  Can someone investigate?
  Has anyone else experienced this? 
  If more info are needed I will try to do my best :)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1719731/+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 1696049] Re: xfstest sanity checks on seek operations fails

[Joseph Salisbury]

The reverse bisect reported the following commit as the fix:

8affebe ("xfs: fix off-by-one on max nr_pages in
xfs_find_get_desired_pgoff()")

I built a 17.04(Zesty) test kernel with a pick of this commit.  The test
kernel can be downloaded from:

http://kernel.ubuntu.com/~jsalisbury/lp1696049/

Can you test this kernel and see if it resolves 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/1696049

Title:
  xfstest sanity checks on seek operations fails

Status in The Ubuntu-power-systems project:
  In Progress
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Zesty:
  In Progress
Status in linux source package in Artful:
  Fix Released

Bug description:
  == Comment: #0 - Harish Sriram 
  Issue:
  --
  xfstest fails with sanity checks on seek operations

  # uname -a
  Linux ltc-tuleta12 4.10.0-21-generic #23~16.04.1-Ubuntu SMP Tue May 2 
12:54:57 UTC 2017 ppc64le ppc64le ppc64le GNU/Linux

  Steps to reproduce:
  
  1. Create a loop device with xfs filesystem
  2. git clone git://git.kernel.org/pub/scm/fs/xfs/xfstests-dev.git; cd 
xfstests-dev
  3. make
  4. Create a local.config for running with created loop device
  5. Run xfstests-dev test  : ./check tests/generic/285 or ./check 
tests/generic/436

  The test 285 fails with following
  ...
  ...
  07. Test file with unwritten extents, only have dirty pages
  07.01 SEEK_HOLE expected 0 or 45056, got 0.   succ
  07.02 SEEK_HOLE expected 1 or 45056, got 1.   succ
  07.03 SEEK_DATA expected 40960 or 40960, got -1.  FAIL
  07.04 SEEK_DATA expected 40960 or 40960, got -1.  FAIL

  08. Test file with unwritten extents, only have unwritten pages
  08.01 SEEK_HOLE expected 0 or 45056, got 0.   succ
  08.02 SEEK_HOLE expected 1 or 45056, got 1.   succ
  08.03 SEEK_DATA expected 40960 or 40960, got -1.  FAIL
  08.04 SEEK_DATA expected 40960 or 40960, got -1.  FAIL

  The test 436 fails with 
  ...
  ...
  14. Test file with unwritten extents, small hole after pagevec dirty pages
  14.01 SEEK_HOLE expected 917504 or 4194304, got 3670016.  FAIL
  14.02 SEEK_HOLE expected 917504 or 4194304, got 3670016.  FAIL
  14.03 SEEK_HOLE expected 3670016 or 4194304, got 3670016. succ
  14.04 SEEK_DATA expected 0 or 0, got 0.   succ
  14.05 SEEK_DATA expected 1 or 1, got 1.   succ
  14.06 SEEK_DATA expected 2752512 or 2752512, got 2752512. succ

  seek sanity check failed!

  Full log is attached.

  == Comment: #6 - Harish Sriram

  commit 5375023ae1266553a7baa0845e82917d8803f48c
  Author: Jan Kara 
  Date:   Thu May 18 16:36:22 2017 -0700

  xfs: Fix missed holes in SEEK_HOLE implementation
  XFS SEEK_HOLE implementation could miss a hole in an unwritten extent as
  can be seen by the following command:
  
  xfs_io -c "falloc 0 256k" -c "pwrite 0 56k" -c "pwrite 128k 8k"
 -c "seek -h 0" file
  wrote 57344/57344 bytes at offset 0
  56 KiB, 14 ops; 0. sec (49.312 MiB/sec and 12623.9856 ops/sec)
  wrote 8192/8192 bytes at offset 131072
  8 KiB, 2 ops; 0. sec (70.383 MiB/sec and 18018.0180 ops/sec)
  Whence  Result
  HOLE139264
  
  Where we can see that hole at offset 56k was just ignored by SEEK_HOLE
  implementation. The bug is in xfs_find_get_desired_pgoff() which does
  not properly detect the case when pages are not contiguous.
  
  Fix the problem by properly detecting when found page has larger offset
  than expected.
  
  CC: sta...@vger.kernel.org
  Fixes: d126d43f631f996daeee5006714fed914be32368
  Signed-off-by: Jan Kara 
  Reviewed-by: Brian Foster 
  Reviewed-by: Darrick J. Wong 
  Signed-off-by: Darrick J. Wong 

  
  The above commit fixes the generic/436 test, but generic/285 still FAILS.

  The generic/285 failure is reproducible on most P8/P9 systems.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1696049/+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 1721373] Re: linux: 4.13.0-15.16 -proposed tracker

[Brad Figg]

** Changed in: kernel-development-workflow/automated-testing
   Status: New => Confirmed

** Changed in: kernel-development-workflow/promote-to-proposed
   Status: Fix Committed => Fix Released

** Changed in: kernel-development-workflow/regression-testing
   Status: New => Confirmed

** Description changed:

  This bug is for tracking the 4.13.0-15.16 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 --
  phase: Uploaded
+ kernel-phase:Promoted to proposed
+ kernel-phase-changed:Thursday, 05. October 2017 14:32 UTC

** Description changed:

  This bug is for tracking the 4.13.0-15.16 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 --
- phase: Uploaded
- kernel-phase:Promoted to proposed
- kernel-phase-changed:Thursday, 05. October 2017 14:32 UTC
+ phase: Promoted to proposed
+ proposed-announcement-sent: true
+ proposed-testing-requested: true

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

Title:
  linux: 4.13.0-15.16 -proposed tracker

Status in Kernel Development Workflow:
  In Progress
Status in Kernel Development Workflow automated-testing series:
  Confirmed
Status in Kernel Development Workflow prepare-package series:
  Fix Released
Status in Kernel Development Workflow prepare-package-meta series:
  Fix Released
Status in Kernel Development Workflow prepare-package-signed series:
  Fix Released
Status in Kernel Development Workflow promote-to-proposed series:
  Fix Released
Status in Kernel Development Workflow promote-to-release series:
  New
Status in Kernel Development Workflow regression-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Artful:
  Confirmed

Bug description:
  This bug is for tracking the 4.13.0-15.16 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 --
  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-development-workflow/+bug/1721373/+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 1721558] Re: ubuntu-regression-suite fails in xenial

[Dimitri John Ledkov]

This all for xenial ADT tests.

** Tags added: xenial

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

Title:
  ubuntu-regression-suite fails in xenial

Status in linux-aws package in Ubuntu:
  New
Status in linux-azure package in Ubuntu:
  New
Status in linux-gcp package in Ubuntu:
  New
Status in linux-gke package in Ubuntu:
  New
Status in linux-hwe package in Ubuntu:
  New
Status in linux-hwe-edge package in Ubuntu:
  New
Status in linux-kvm package in Ubuntu:
  New
Status in linux-aws source package in Xenial:
  New
Status in linux-azure source package in Xenial:
  New
Status in linux-gcp source package in Xenial:
  New
Status in linux-gke source package in Xenial:
  New
Status in linux-hwe source package in Xenial:
  New
Status in linux-hwe-edge source package in Xenial:
  New
Status in linux-kvm source package in Xenial:
  New

Bug description:
  ubuntu-regression-suite fails in xenial

  autopkgtest [22:34:48]: test ubuntu-regression-suite: [---
  Source Package Version: 4.4.0-1035.44
  Running Kernel Version: 4.4.0-96.119
  ERROR: running version does not match source package

  Please note autopkgtests have quite elaborate setup for the kernels,
  thus I'm guessing that some of the setup is not done right, and the
  VMs are still running generic kernel instead of customized kernel.

  Maybe a reboot mark is needed in the ubuntu-regression-suite case to
  reboot the system if Source != Running. And if that doesn't help
  either, then fail the test?

  This affects a few packages which all trip up ADT testing whenever I
  SRU systemd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1721558/+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 1721558] [NEW] ubuntu-regression-suite fails in xenial

[Dimitri John Ledkov]

Public bug reported:

ubuntu-regression-suite fails in xenial

autopkgtest [22:34:48]: test ubuntu-regression-suite: [---
Source Package Version: 4.4.0-1035.44
Running Kernel Version: 4.4.0-96.119
ERROR: running version does not match source package

Please note autopkgtests have quite elaborate setup for the kernels,
thus I'm guessing that some of the setup is not done right, and the VMs
are still running generic kernel instead of customized kernel.

Maybe a reboot mark is needed in the ubuntu-regression-suite case to
reboot the system if Source != Running. And if that doesn't help either,
then fail the test?

This affects a few packages which all trip up ADT testing whenever I SRU
systemd.

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

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

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

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

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

** Affects: linux-hwe-edge (Ubuntu)
 Importance: Undecided
 Status: New

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

** Affects: linux-aws (Ubuntu Xenial)
 Importance: Undecided
 Status: New

** Affects: linux-azure (Ubuntu Xenial)
 Importance: Undecided
 Status: New

** Affects: linux-gcp (Ubuntu Xenial)
 Importance: Undecided
 Status: New

** Affects: linux-gke (Ubuntu Xenial)
 Importance: Undecided
 Status: New

** Affects: linux-hwe (Ubuntu Xenial)
 Importance: Undecided
 Status: New

** Affects: linux-hwe-edge (Ubuntu Xenial)
 Importance: Undecided
 Status: New

** Affects: linux-kvm (Ubuntu Xenial)
 Importance: Undecided
 Status: New


** Tags: adt-fail xenial

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

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

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

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

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

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

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

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

Title:
  ubuntu-regression-suite fails in xenial

Status in linux-aws package in Ubuntu:
  New
Status in linux-azure package in Ubuntu:
  New
Status in linux-gcp package in Ubuntu:
  New
Status in linux-gke package in Ubuntu:
  New
Status in linux-hwe package in Ubuntu:
  New
Status in linux-hwe-edge package in Ubuntu:
  New
Status in linux-kvm package in Ubuntu:
  New
Status in linux-aws source package in Xenial:
  New
Status in linux-azure source package in Xenial:
  New
Status in linux-gcp source package in Xenial:
  New
Status in linux-gke source package in Xenial:
  New
Status in linux-hwe source package in Xenial:
  New
Status in linux-hwe-edge source package in Xenial:
  New
Status in linux-kvm source package in Xenial:
  New

Bug description:
  ubuntu-regression-suite fails in xenial

  autopkgtest [22:34:48]: test ubuntu-regression-suite: [---
  Source Package Version: 4.4.0-1035.44
  Running Kernel Version: 4.4.0-96.119
  ERROR: running version does not match source package

  Please note autopkgtests have quite elaborate setup for the kernels,
  thus I'm guessing that some of the setup is not done right, and the
  VMs are still running generic kernel instead of customized kernel.

  Maybe a reboot mark is needed in the ubuntu-regression-suite case to
  reboot the system if Source != Running. And if that doesn't help
  either, then fail the test?

  This affects a few packages which all trip up ADT testing whenever I
  SRU systemd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1721558/+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 1721558] Re: ubuntu-regression-suite fails in xenial

[Dimitri John Ledkov]

The command ran is of this form:

autopkgtest [19:55:28]: host juju-prod-ues-proposed-migration-machine-3;
command line: /home/ubuntu/autopkgtest/runner/autopkgtest --output-dir
/tmp/autopkgtest-work.iw5t9p35/out --timeout-copy=6000 --setup-commands
/home/ubuntu/autopkgtest-cloud/worker-config-production/setup-
canonical.sh --setup-commands /home/ubuntu/autopkgtest/setup-commands
/setup-testbed --apt-pocket=proposed --apt-upgrade linux-aws
--env=ADT_TEST_TRIGGERS=systemd/229-4ubuntu20 -- ssh -s
/home/ubuntu/autopkgtest/ssh-setup/nova -- --flavor autopkgtest --name
adt-xenial-amd64-linux-aws-20170919-195523 --image 'ubuntu/ubuntu-
xenial-.*-amd64-server' --keyname testbed-juju-prod-ues-proposed-
migration-machine-3 --net-id=net_ues_proposed_migration -e
''"'"'http_proxy=http://squid.internal:3128'"'"'' -e
''"'"'https_proxy=http://squid.internal:3128'"'"'' -e
''"'"'no_proxy=127.0.0.1,127.0.1.1,localhost,localdomain,novalocal,internal,archive.ubuntu.com,security.ubuntu.com,ddebs.ubuntu.com,changelogs.ubuntu.com,ppa.launchpad.net'"'"''
--mirror=http://ftpmaster.internal/ubuntu


I guess the crutial bit is that it is a test of: linux-aws with 
ADT_TEST_TRIGGERS=systemd/229-4ubuntu20

meaning some of the adt magic w.r.t. kernel setup does not kick in, i
think.

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

Title:
  ubuntu-regression-suite fails in xenial

Status in linux-aws package in Ubuntu:
  New
Status in linux-azure package in Ubuntu:
  New
Status in linux-gcp package in Ubuntu:
  New
Status in linux-gke package in Ubuntu:
  New
Status in linux-hwe package in Ubuntu:
  New
Status in linux-hwe-edge package in Ubuntu:
  New
Status in linux-kvm package in Ubuntu:
  New
Status in linux-aws source package in Xenial:
  New
Status in linux-azure source package in Xenial:
  New
Status in linux-gcp source package in Xenial:
  New
Status in linux-gke source package in Xenial:
  New
Status in linux-hwe source package in Xenial:
  New
Status in linux-hwe-edge source package in Xenial:
  New
Status in linux-kvm source package in Xenial:
  New

Bug description:
  ubuntu-regression-suite fails in xenial

  autopkgtest [22:34:48]: test ubuntu-regression-suite: [---
  Source Package Version: 4.4.0-1035.44
  Running Kernel Version: 4.4.0-96.119
  ERROR: running version does not match source package

  Please note autopkgtests have quite elaborate setup for the kernels,
  thus I'm guessing that some of the setup is not done right, and the
  VMs are still running generic kernel instead of customized kernel.

  Maybe a reboot mark is needed in the ubuntu-regression-suite case to
  reboot the system if Source != Running. And if that doesn't help
  either, then fail the test?

  This affects a few packages which all trip up ADT testing whenever I
  SRU systemd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1721558/+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 1719210] Re: Bluetooth audio to A2DP headset no longer works following upgrade from 4.12 to 4.13 in artful

[Peter Rhone]

@ Kai-Heng Feng (kaihengfeng)
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1719210/comments/6

Since my bug has been marked as a duplicate of this one, I'll respond to your 
comment here.
Yes, the bug exists for me all kernels > 4.12, up to and including 4.14-rc3.
I can no longer use my Sony Bluetooth Speaker SRS-XB40.

@Bowsher's hack of putting 
options bt_coex_active=0 
in /etc/modprobe.d/iwlwifi.conf 
is no solution, since I need both BT and WiFi.

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

Title:
  Bluetooth audio to A2DP headset no longer works following upgrade from
  4.12 to 4.13 in artful

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Using artful kernel 4.12.0-13.14, Bluetooth audio works great.

  Upgrading to artful kernel 4.13.0-11.12, there are severe Bluetooth
  audio issues which have manifested in a variety of weird ways:

  1) Playback would stall after 10-20 seconds
  2) Upon removing the device and attempting to redo pairing, no devices could 
be found to pair with
  3) After the device ended up reverting to low quality mono HSP mode, it could 
not be switched back to A2DP

  This is all rather vague - sorry - but it felt better to get notice of
  this regression into the bugtracker sooner rather than later.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-11-generic 4.13.0-11.12
  ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1
  Uname: Linux 4.13.0-11-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  maxb   2091 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Sep 24 21:24:00 2017
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=635db8ca-b352-4622-87eb-08f74460324b
  InstallationDate: Installed on 2016-08-16 (404 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: HP HP Spectre Notebook
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-11-generic 
root=UUID=4989886a-f95e-4802-ab51-dcbf53167aeb ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-11-generic N/A
   linux-backports-modules-4.13.0-11-generic  N/A
   linux-firmware 1.168
  SourcePackage: linux
  UpgradeStatus: Upgraded to artful on 2017-08-31 (23 days ago)
  dmi.bios.date: 02/21/2017
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.31
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 81A0
  dmi.board.vendor: HP
  dmi.board.version: 48.54
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.31:bd02/21/2017:svnHP:pnHPSpectreNotebook:pvrType1ProductConfigId:rvnHP:rn81A0:rvr48.54:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP S=SPT
  dmi.product.name: HP Spectre Notebook
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1719210/+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 1721550] Re: Xenial update to 4.4.90 stable release

[Stefan Bader]

Fixed up "KEYS: prevent creating a different user's keyrings" because it
failed to apply cleanly as we carry a delta for bug #1569924 "linux: Add
UEFI keyring for externally signed modules".

Fixed up "cxl: Fix driver use count" because it failed to apply cleanly
as we carry a delta for bug #1588468 "CAPI: CGZIP AFU contexts do not
receive interrupts after heavy afu open/close".

** Description changed:

+ SRU Justification
  
- SRU Justification
+ Impact:
+    The upstream process for stable tree updates is quite similar
+    in scope to the Ubuntu SRU process, e.g., each patch has to
+    demonstrably fix a bug, and each patch is vetted by upstream
+    by originating either directly from a mainline/stable Linux tree or
+    a minimally backported form of that patch. The 4.4.90 upstream stable
+    patch set is now available. It should be included in the Ubuntu
+    kernel as well.
  
- Impact:
-The upstream process for stable tree updates is quite similar
-in scope to the Ubuntu SRU process, e.g., each patch has to
-demonstrably fix a bug, and each patch is vetted by upstream
-by originating either directly from a mainline/stable Linux tree or
-a minimally backported form of that patch. The 4.4.90 upstream stable
-patch set is now available. It should be included in the Ubuntu
-kernel as well.
+    git://git.kernel.org/
  
-git://git.kernel.org/
+ TEST CASE: TBD
  
- TEST CASE: TBD
- 
-The following patches from the 4.4.90 stable release shall be
- applied:
+ The following patches from the 4.4.90 stable release shall be applied:
+ * cifs: release auth_key.response for reconnect.
+ * mac80211: flush hw_roc_start work before cancelling the ROC
+ * KVM: PPC: Book3S: Fix race and leak in kvm_vm_ioctl_create_spapr_tce()
+ * tracing: Fix trace_pipe behavior for instance traces
+ * tracing: Erase irqsoff trace with empty write
+ * md/raid5: fix a race condition in stripe batch
+ * md/raid5: preserve STRIPE_ON_UNPLUG_LIST in break_stripe_batch_list
+ * scsi: scsi_transport_iscsi: fix the issue that iscsi_if_rx doesn't parse
+   nlmsg properly
+ * crypto: talitos - Don't provide setkey for non hmac hashing algs.
+ * crypto: talitos - fix sha224
+ * KEYS: fix writing past end of user-supplied buffer in keyring_read()
+ * KEYS: prevent creating a different user's keyrings
+ * KEYS: prevent KEYCTL_READ on negative key
+ * powerpc/pseries: Fix parent_dn reference leak in add_dt_node()
+ * Fix SMB3.1.1 guest authentication to Samba
+ * SMB: Validate negotiate (to protect against downgrade) even if signing off
+ * SMB3: Don't ignore O_SYNC/O_DSYNC and O_DIRECT flags
+ * vfs: Return -ENXIO for negative SEEK_HOLE / SEEK_DATA offsets
+ * nl80211: check for the required netlink attributes presence
+ * bsg-lib: don't free job in bsg_prepare_job
+ * seccomp: fix the usage of get/put_seccomp_filter() in seccomp_get_filter()
+ * arm64: Make sure SPsel is always set
+ * arm64: fault: Route pte translation faults via do_translation_fault
+ * KVM: VMX: Do not BUG() on out-of-bounds guest IRQ
+ * kvm: nVMX: Don't allow L2 to access the hardware CR8
+ * PCI: Fix race condition with driver_override
+ * btrfs: fix NULL pointer dereference from free_reloc_roots()
+ * btrfs: propagate error to btrfs_cmp_data_prepare caller
+ * btrfs: prevent to set invalid default subvolid
+ * x86/fpu: Don't let userspace set bogus xcomp_bv
+ * gfs2: Fix debugfs glocks dump
+ * timer/sysclt: Restrict timer migration sysctl values to 0 and 1
+ * KVM: VMX: do not change SN bit in vmx_update_pi_irte()
+ * KVM: VMX: remove WARN_ON_ONCE in kvm_vcpu_trigger_posted_interrupt
+ * cxl: Fix driver use count
+ * dmaengine: mmp-pdma: add number of requestors
+ * ARM: pxa: add the number of DMA requestor lines
+ * ARM: pxa: fix the number of DMA requestor lines
+ * KVM: VMX: use cmpxchg64
+ * video: fbdev: aty: do not leak uninitialized padding in clk to userspace
+ * swiotlb-xen: implement xen_swiotlb_dma_mmap callback
+ * fix xen_swiotlb_dma_mmap prototype
+ * Linux 4.4.90

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

Title:
  Xenial update to 4.4.90 stable release

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  In Progress

Bug description:
  SRU Justification

  Impact:
     The upstream process for stable tree updates is quite similar
     in scope to the Ubuntu SRU process, e.g., each patch has to
     demonstrably fix a bug, and each patch is vetted by upstream
     by originating either directly from a mainline/stable Linux tree or
     a minimally backported form of that patch. The 4.4.90 upstream stable
     patch set is now available. It should be included in the Ubuntu
     kernel as well.

     git://git.kernel.org/

  TEST CASE: 

[Kernel-packages] [Bug 1721550] [NEW] Xenial update to 4.4.90 stable release

[Stefan Bader]

Public bug reported:


SRU Justification

Impact:
   The upstream process for stable tree updates is quite similar
   in scope to the Ubuntu SRU process, e.g., each patch has to
   demonstrably fix a bug, and each patch is vetted by upstream
   by originating either directly from a mainline/stable Linux tree or
   a minimally backported form of that patch. The 4.4.90 upstream stable
   patch set is now available. It should be included in the Ubuntu
   kernel as well.

   git://git.kernel.org/

TEST CASE: TBD

   The following patches from the 4.4.90 stable release shall be
applied:

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

** Affects: linux (Ubuntu Xenial)
 Importance: Medium
 Assignee: Stefan Bader (smb)
 Status: In Progress


** Tags: kernel-stable-tracking-bug

** Tags added: kernel-stable-tracking-bug

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

** Changed in: linux (Ubuntu Xenial)
   Importance: Undecided => Medium

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

** Changed in: linux (Ubuntu Xenial)
 Assignee: (unassigned) => Stefan Bader (smb)

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

Title:
  Xenial update to 4.4.90 stable release

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  In Progress

Bug description:
  
  SRU Justification

  Impact:
 The upstream process for stable tree updates is quite similar
 in scope to the Ubuntu SRU process, e.g., each patch has to
 demonstrably fix a bug, and each patch is vetted by upstream
 by originating either directly from a mainline/stable Linux tree or
 a minimally backported form of that patch. The 4.4.90 upstream stable
 patch set is now available. It should be included in the Ubuntu
 kernel as well.

 git://git.kernel.org/

  TEST CASE: TBD

 The following patches from the 4.4.90 stable release shall be
  applied:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1721550/+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 1721538] Re: Remove vmbus-rdma driver from Xenial kernel

[Marcelo Cerri]

https://lists.ubuntu.com/archives/kernel-team/2017-October/087428.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/1721538

Title:
  Remove vmbus-rdma driver from Xenial kernel

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

Bug description:
  SRU Justification:

  Impact: in order to properly support infiniband for Azure A8/A9,
  H-series, and NC24/NV24 instances, multiple versions of the driver
  must be maintained and userspace must be responsible for selecting the
  correct version of the driver.

  That's already supported in the linux-azure kernel with the userspace
  logic implemented in the Windows Azure Linux Agent. The Xenial kernel
  is carrying a single version of the RDMA which might cause problems if
  the host OS requires a different version of the driver.

  Fix: remove the driver located at "drivers/infiniband/hw/vmbus-rdma/"
  from the Xenial kernel and keep support to it only in linux-azure.

  Testcase: the module "hv_network_direct.ko" should not be included in
  the linux-image or linux-image-extra packages.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1721538/+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 1702250] Re: [Feature] WIFI: firmware update

[Leann Ogasawara]

** Changed in: intel
   Status: New => Fix Released

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

Title:
  [Feature] WIFI: firmware update

Status in intel:
  Fix Released
Status in linux-firmware package in Ubuntu:
  Fix Released

Bug description:
  Intel released new versions of the firmware for Intel Wireless devices.
  3168, 3165 and 7265D get -29.ucode
  8260 and 8265 get -31.ucode

  Target Release: 17.10

To manage notifications about this bug go to:
https://bugs.launchpad.net/intel/+bug/1702250/+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 1720239] Re: linux: 4.13.0-13.14 -proposed tracker

[Seth Forshee]

*** This bug is a duplicate of bug 1721373 ***
https://bugs.launchpad.net/bugs/1721373

** This bug is no longer a duplicate of bug 1721122
   linux: 4.13.0-14.15 -proposed tracker
** This bug has been marked a duplicate of bug 1721373
   linux: 4.13.0-15.16 -proposed tracker

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

Title:
  linux: 4.13.0-13.14 -proposed tracker

Status in Kernel Development Workflow:
  In Progress
Status in Kernel Development Workflow automated-testing series:
  New
Status in Kernel Development Workflow prepare-package series:
  Confirmed
Status in Kernel Development Workflow prepare-package-meta series:
  New
Status in Kernel Development Workflow prepare-package-signed series:
  New
Status in Kernel Development Workflow promote-to-proposed series:
  New
Status in Kernel Development Workflow promote-to-release series:
  New
Status in Kernel Development Workflow regression-testing series:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Artful:
  Confirmed

Bug description:
  This bug is for tracking the 4.13.0-13.14 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

  kernel-phase:Packaging
  kernel-phase-changed:Thursday, 28. September 2017 21:02 UTC

  -- swm properties --
  phase: Packaging

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-development-workflow/+bug/1720239/+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 1721122] Re: linux: 4.13.0-14.15 -proposed tracker

[Seth Forshee]

*** This bug is a duplicate of bug 1721373 ***
https://bugs.launchpad.net/bugs/1721373

** This bug has been marked a duplicate of bug 1721373
   linux: 4.13.0-15.16 -proposed tracker

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

Title:
  linux: 4.13.0-14.15 -proposed tracker

Status in Kernel Development Workflow:
  In Progress
Status in Kernel Development Workflow automated-testing series:
  Incomplete
Status in Kernel Development Workflow prepare-package series:
  Fix Released
Status in Kernel Development Workflow prepare-package-meta series:
  Fix Released
Status in Kernel Development Workflow prepare-package-signed series:
  Fix Released
Status in Kernel Development Workflow promote-to-proposed series:
  Fix Released
Status in Kernel Development Workflow promote-to-release series:
  New
Status in Kernel Development Workflow regression-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Artful:
  Confirmed

Bug description:
  This bug is for tracking the 4.13.0-14.15 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 --
  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-development-workflow/+bug/1721122/+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 1721538] Re: Remove vmbus-rdma driver from Xenial kernel

[Marcelo Cerri]

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

** Changed in: linux (Ubuntu Xenial)
   Importance: Undecided => Medium

** Changed in: linux (Ubuntu Xenial)
 Assignee: (unassigned) => Marcelo Cerri (mhcerri)

** Description changed:

  SRU Justification:
  
  Impact: in order to properly support infiniband for Azure A8/A9,
  H-series, and NC24/NV24 instances, multiple versions of the driver must
  be maintained and userspace must be responsible for selecting the
  correct version of the driver.
  
  That's already supported in the linux-azure kernel with the userspace
  logic implemented in the Windows Azure Linux Agent. The Xenial kernel is
  carrying a single version of the RDMA which might cause problems if the
  host OS requires a different version of the driver.
  
  Fix: remove the driver located at "drivers/infiniband/hw/vmbus-rdma/"
  from the Xenial kernel and keep support to it only in linux-azure.
  
- Testcase: the module "hv_network_direct.ko" should not be include in the
- linux-image or linux-image-extra packages.
+ Testcase: the module "hv_network_direct.ko" should not be included in
+ the linux-image or linux-image-extra packages.

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

Title:
  Remove vmbus-rdma driver from Xenial kernel

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

Bug description:
  SRU Justification:

  Impact: in order to properly support infiniband for Azure A8/A9,
  H-series, and NC24/NV24 instances, multiple versions of the driver
  must be maintained and userspace must be responsible for selecting the
  correct version of the driver.

  That's already supported in the linux-azure kernel with the userspace
  logic implemented in the Windows Azure Linux Agent. The Xenial kernel
  is carrying a single version of the RDMA which might cause problems if
  the host OS requires a different version of the driver.

  Fix: remove the driver located at "drivers/infiniband/hw/vmbus-rdma/"
  from the Xenial kernel and keep support to it only in linux-azure.

  Testcase: the module "hv_network_direct.ko" should not be included in
  the linux-image or linux-image-extra packages.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1721538/+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 1721538] Re: Remove vmbus-rdma driver from Xenial kernel

[Stefan Bader]

** Also affects: linux (Ubuntu Xenial)
   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/1721538

Title:
  Remove vmbus-rdma driver from Xenial kernel

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

Bug description:
  SRU Justification:

  Impact: in order to properly support infiniband for Azure A8/A9,
  H-series, and NC24/NV24 instances, multiple versions of the driver
  must be maintained and userspace must be responsible for selecting the
  correct version of the driver.

  That's already supported in the linux-azure kernel with the userspace
  logic implemented in the Windows Azure Linux Agent. The Xenial kernel
  is carrying a single version of the RDMA which might cause problems if
  the host OS requires a different version of the driver.

  Fix: remove the driver located at "drivers/infiniband/hw/vmbus-rdma/"
  from the Xenial kernel and keep support to it only in linux-azure.

  Testcase: the module "hv_network_direct.ko" should not be included in
  the linux-image or linux-image-extra packages.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1721538/+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 1719290] Re: CONFIG_DEBUG_FS is not enabled by "make zfcpdump_defconfig" with Ubuntu 17.10 (kernel 4.13)

[Seth Forshee]

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

Title:
  CONFIG_DEBUG_FS is not enabled by "make zfcpdump_defconfig" with
  Ubuntu 17.10 (kernel 4.13)

Status in Ubuntu on IBM z Systems:
  Incomplete
Status in linux package in Ubuntu:
  Fix Committed
Status in linux-hwe package in Ubuntu:
  Incomplete
Status in zfcpdump-kernel package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 17.10 uses kernel 4.13.

  We just found out that on this kernel version CONFIG_DEBUG_FS is not
  enabled by "make zfcpdump_defconfig".

  This makes zfcpdump fail with the following error message:

  ERROR: Unable to mount debugfs 
  No such file or directory

  Patch solving this problem is attached

  As reference following bugzilla
  As reference h
  IBM bugzilla for enabling zfcpdump: 
https://bugzilla.linux.ibm.com/show_bug.cgi?id=139974

  or Launchpad 
  https://bugs.launchpad.net/ubuntu/+source/s390-tools/+bug/1565841

  == Comment: #1 - Heinz-Werner Seeck  -
  2017-09-25 06:00:23 ==

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1719290/+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 1721538] [NEW] Remove vmbus-rdma driver from Xenial kernel

[Marcelo Cerri]

Public bug reported:

SRU Justification:

Impact: in order to properly support infiniband for Azure A8/A9,
H-series, and NC24/NV24 instances, multiple versions of the driver must
be maintained and userspace must be responsible for selecting the
correct version of the driver.

That's already supported in the linux-azure kernel with the userspace
logic implemented in the Windows Azure Linux Agent. The Xenial kernel is
carrying a single version of the RDMA which might cause problems if the
host OS requires a different version of the driver.

Fix: remove the driver located at "drivers/infiniband/hw/vmbus-rdma/"
from the Xenial kernel and keep support to it only in linux-azure.

Testcase: the module "hv_network_direct.ko" should not be include in the
linux-image or linux-image-extra packages.

** Affects: linux (Ubuntu)
 Importance: Medium
 Assignee: Marcelo Cerri (mhcerri)
 Status: In Progress

** Affects: linux (Ubuntu Xenial)
 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/1721538

Title:
  Remove vmbus-rdma driver from Xenial kernel

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Xenial:
  New

Bug description:
  SRU Justification:

  Impact: in order to properly support infiniband for Azure A8/A9,
  H-series, and NC24/NV24 instances, multiple versions of the driver
  must be maintained and userspace must be responsible for selecting the
  correct version of the driver.

  That's already supported in the linux-azure kernel with the userspace
  logic implemented in the Windows Azure Linux Agent. The Xenial kernel
  is carrying a single version of the RDMA which might cause problems if
  the host OS requires a different version of the driver.

  Fix: remove the driver located at "drivers/infiniband/hw/vmbus-rdma/"
  from the Xenial kernel and keep support to it only in linux-azure.

  Testcase: the module "hv_network_direct.ko" should not be include in
  the linux-image or linux-image-extra packages.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1721538/+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 1721373] Re: linux: 4.13.0-15.16 -proposed tracker

[Brad Figg]

** Changed in: kernel-development-workflow/prepare-package
   Status: Confirmed => Fix Released

** Changed in: kernel-development-workflow/prepare-package
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Seth Forshee 
(sforshee)

** Changed in: kernel-development-workflow/prepare-package-meta
   Status: New => Confirmed

** Changed in: kernel-development-workflow/prepare-package-signed
   Status: New => Confirmed

** Changed in: kernel-development-workflow/promote-to-proposed
   Status: New => Fix Committed

** Tags added: block-proposed-artful

** Tags added: block-proposed

** Changed in: kernel-development-workflow/prepare-package-meta
   Status: Confirmed => Fix Released

** Changed in: kernel-development-workflow/prepare-package-meta
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Seth Forshee 
(sforshee)

** Changed in: kernel-development-workflow/prepare-package-signed
   Status: Confirmed => Fix Released

** Changed in: kernel-development-workflow/prepare-package-signed
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Seth Forshee 
(sforshee)

** Description changed:

  This bug is for tracking the 4.13.0-15.16 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
  
- kernel-phase-changed:Wednesday, 04. October 2017 19:31 UTC
- kernel-phase:Packaging
- 
  -- swm properties --
  phase: Packaging
+ kernel-phase-changed:Thursday, 05. October 2017 11:32 UTC
+ kernel-phase:Uploaded

** Description changed:

  This bug is for tracking the 4.13.0-15.16 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 --
- phase: Packaging
- kernel-phase-changed:Thursday, 05. October 2017 11:32 UTC
- kernel-phase:Uploaded
+ phase: Uploaded

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

Title:
  linux: 4.13.0-15.16 -proposed tracker

Status in Kernel Development Workflow:
  In Progress
Status in Kernel Development Workflow automated-testing series:
  New
Status in Kernel Development Workflow prepare-package series:
  Fix Released
Status in Kernel Development Workflow prepare-package-meta series:
  Fix Released
Status in Kernel Development Workflow prepare-package-signed series:
  Fix Released
Status in Kernel Development Workflow promote-to-proposed series:
  Fix Committed
Status in Kernel Development Workflow promote-to-release series:
  New
Status in Kernel Development Workflow regression-testing series:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Artful:
  Confirmed

Bug description:
  This bug is for tracking the 4.13.0-15.16 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 --
  phase: Uploaded

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-development-workflow/+bug/1721373/+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 1721511] Re: [Xenial] update OpenNSL kernel modules to 6.5.10

[Jesse Sung]

** Tags added: hohhot originate-from-1719941

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

Title:
  [Xenial] update OpenNSL kernel modules to 6.5.10

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  In Progress

Bug description:
  Currently we have 6.4.10 in the Xenial kernel. The latest OpenNSL
  Sep-27 release[1] updates kernel modules to 6.5.10.

  Since the module doesn't load automatically, this update shouldn't
  have any impact for people don't use the module.

  For the module itself, it loads without problem on a test system.

  [1] https://github.com/Broadcom-Switch/OpenNSL/tree/v3.4.1.5

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1721511/+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 1721511] [NEW] [Xenial] update OpenNSL kernel modules to 6.5.10

[Jesse Sung]

Public bug reported:

Currently we have 6.4.10 in the Xenial kernel. The latest OpenNSL Sep-27
release[1] updates kernel modules to 6.5.10.

Since the module doesn't load automatically, this update shouldn't have
any impact for people don't use the module.

For the module itself, it loads without problem on a test system.

[1] https://github.com/Broadcom-Switch/OpenNSL/tree/v3.4.1.5

** Affects: linux (Ubuntu)
 Importance: Undecided
 Assignee: Jesse Sung (wenchien)
 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/1721511

Title:
  [Xenial] update OpenNSL kernel modules to 6.5.10

Status in linux package in Ubuntu:
  In Progress

Bug description:
  Currently we have 6.4.10 in the Xenial kernel. The latest OpenNSL
  Sep-27 release[1] updates kernel modules to 6.5.10.

  Since the module doesn't load automatically, this update shouldn't
  have any impact for people don't use the module.

  For the module itself, it loads without problem on a test system.

  [1] https://github.com/Broadcom-Switch/OpenNSL/tree/v3.4.1.5

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1721511/+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 1711283] Comment bridged from LTC Bugzilla

[bugproxy]

--- Comment From nasas...@in.ibm.com 2017-10-05 05:58 EDT---
On a PowerVM machine seeing more failures with the 4.13.0-12-generic kernel

selftests:  mmap_bench [FAIL]
selftests:  futex_bench [FAIL]
selftests:  memcpy_64 [FAIL]
selftests:  count_instructions [FAIL]
selftests:  reg_access_test [FAIL]
selftests:  event_attributes_test [FAIL]
selftests:  cycles_test [FAIL]
selftests:  cycles_with_freeze_test [FAIL]
selftests:  pmc56_overflow_test [FAIL]
selftests:  ebb_vs_cpu_event_test [FAIL]
selftests:  cpu_event_vs_ebb_test [FAIL]
selftests:  cpu_event_pinned_vs_ebb_test [FAIL]
selftests:  task_event_vs_ebb_test [FAIL]
selftests:  task_event_pinned_vs_ebb_test [FAIL]
selftests:  multi_ebb_procs_test [FAIL]
selftests:  multi_counter_test [FAIL]
selftests:  pmae_handling_test [FAIL]
selftests:  close_clears_pmcc_test [FAIL]
selftests:  instruction_count_test [FAIL]
selftests:  fork_cleanup_test [FAIL]
selftests:  ebb_on_child_test [FAIL]
selftests:  ebb_on_willing_child_test [FAIL]
selftests:  back_to_back_ebbs_test [FAIL]
selftests:  lost_exception_test [FAIL]
selftests:  no_handler_test [FAIL]
selftests:  cycles_with_mmcr2_test [FAIL]
selftests:  memcmp [FAIL]
selftests:  tm-resched-dscr [FAIL]
selftests:  tm-vmx-unavail [FAIL]
selftests:  ptrace-tm-spd-gpr [FAIL]

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

Title:
  few kernel selftest failed on Ubuntu 17.10

Status in The Ubuntu-power-systems project:
  Triaged
Status in linux package in Ubuntu:
  Triaged

Bug description:
  == Comment: #0 - Harish Sriram  - 2017-08-01 05:11:09 ==
  Problem Description
  
  Few kernel selftest failed on Ubuntu 17.10

  Environment
  --
  Kernel Build:  4.11.0-10-generic
  System Name : ltc-test-ci2
  Model  : 8247-22L
  Platform:  PowerNV ( P8 )

  Uname output
  ---
  # uname -a
  Linux ltc-test-ci2 4.11.0-10-generic #15-Ubuntu SMP Thu Jun 29 15:02:54 UTC 
2017 ppc64le ppc64le ppc64le GNU/Linux

  Steps to reproduce:
  
  1. Get kernel source using apt source
  2. Start powerpc specific tests

  The following FAILS are observed.
  selftests:  cycles_test [FAIL]
  selftests:  cycles_with_freeze_test [FAIL]
  selftests:  pmc56_overflow_test [FAIL]
  selftests:  ebb_vs_cpu_event_test [FAIL]
  selftests:  cpu_event_vs_ebb_test [FAIL]
  selftests:  task_event_vs_ebb_test [FAIL]
  selftests:  multi_ebb_procs_test [FAIL]
  selftests:  multi_counter_test [FAIL]
  selftests:  pmae_handling_test [FAIL]
  selftests:  close_clears_pmcc_test [FAIL]
  selftests:  instruction_count_test [FAIL]
  selftests:  ebb_on_willing_child_test [FAIL]
  selftests:  back_to_back_ebbs_test [FAIL]
  selftests:  lost_exception_test [FAIL]
  selftests:  cycles_with_mmcr2_test [FAIL]
  selftests:  tm-vmxcopy [FAIL]

  Full run log is attached.

  == Comment: #5 - Harish Sriram  - 2017-08-08 03:33:36 ==
  With the latest ubuntu mainline kernel 4.13-rc4 from 
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.13-rc4/, I see following 
additional failures

  selftests:  ptrace-gpr [FAIL]
  selftests:  ptrace-tm-gpr [FAIL]
  selftests:  ptrace-tm-spd-gpr [FAIL]

  # uname -a
  Linux ltc-test-ci2 4.13.0-041300rc4-generic #201708062231 SMP Mon Aug 7 
03:29:19 UTC 2017 ppc64le ppc64le ppc64le GNU/Linux

  Thanks,
  Harish

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1711283/+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 1721482] Status changed to Confirmed

[Ubuntu Kernel Bot]

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

Title:
  watchdog: BUG: soft lockup - CPU#1 stuck for 22s!
  [CompositorTileW:29904]

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The system went crazy. Was trying to install gcs-fuse just before
  that. But did not get to it. Just the update command. Not sure if that
  installed something.

  ProblemType: KernelOops
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-12-generic 4.13.0-12.13
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  Annotation: Your system might become unstable now and might need to be 
restarted.
  ApportVersion: 2.20.7-0ubuntu2
  Architecture: amd64
  Date: Thu Oct  5 13:42:59 2017
  Failure: oops
  HibernationDevice: RESUME=UUID=b323f77c-20bc-438b-9710-755bb2592319
  InstallationDate: Installed on 2016-11-11 (327 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  IwConfig:
   enp3s0no wireless extensions.
   
   lono wireless extensions.
  MachineType: Gigabyte Technology Co., Ltd. GA-78LMT-USB3
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-12-generic 
root=UUID=263d9caf-87e3-4a97-beeb-d45e5ded94f6 ro quiet splash
  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
  RfKill:
   
  SourcePackage: linux
  Title: watchdog: BUG: soft lockup - CPU#1 stuck for 22s! 
[CompositorTileW:29904]
  UpgradeStatus: Upgraded to artful on 2017-08-02 (63 days ago)
  dmi.bios.date: 04/23/2013
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: FA
  dmi.board.name: GA-78LMT-USB3
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrFA:bd04/23/2013:svnGigabyteTechnologyCo.,Ltd.:pnGA-78LMT-USB3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-78LMT-USB3:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: GA-78LMT-USB3
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

[Ubuntu Kernel Bot]

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

Title:
  watchdog: BUG: soft lockup - CPU#1 stuck for 22s!
  [CompositorTileW:29904]

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  One issue has led to the collapse of the system. Multiple bugs being
  reported.

  ProblemType: KernelOops
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-12-generic 4.13.0-12.13
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  Annotation: Your system might become unstable now and might need to be 
restarted.
  ApportVersion: 2.20.7-0ubuntu2
  Architecture: amd64
  Date: Thu Oct  5 13:49:05 2017
  Failure: oops
  HibernationDevice: RESUME=UUID=b323f77c-20bc-438b-9710-755bb2592319
  InstallationDate: Installed on 2016-11-11 (327 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  IwConfig:
   enp3s0no wireless extensions.
   
   lono wireless extensions.
  MachineType: Gigabyte Technology Co., Ltd. GA-78LMT-USB3
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-12-generic 
root=UUID=263d9caf-87e3-4a97-beeb-d45e5ded94f6 ro quiet splash
  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
  RfKill:
   
  SourcePackage: linux
  Title: watchdog: BUG: soft lockup - CPU#1 stuck for 22s! 
[CompositorTileW:29904]
  UpgradeStatus: Upgraded to artful on 2017-08-02 (63 days ago)
  dmi.bios.date: 04/23/2013
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: FA
  dmi.board.name: GA-78LMT-USB3
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrFA:bd04/23/2013:svnGigabyteTechnologyCo.,Ltd.:pnGA-78LMT-USB3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-78LMT-USB3:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: GA-78LMT-USB3
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1721483/+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