[Kernel-packages] [Bug 1710649] [NEW] Artful update to v4.12.7 stable release

[Seth Forshee]

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 v4.12.7 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 v4.12.7 stable release shall be
applied:

ppp: Fix false xmit recursion detect with two ppp devices
ppp: fix xmit recursion detection on ppp channels
tcp: avoid setting cwnd to invalid ssthresh after cwnd reduction states
net: fix keepalive code vs TCP_FASTOPEN_CONNECT
ipv6: set rt6i_protocol properly in the route when it is installed
bpf, s390: fix jit branch offset related to ldimm64
net/mlx4_en: don't set CHECKSUM_COMPLETE on SCTP packets
net: sched: set xt_tgchk_param par.net properly in ipt_init_target
net: sched: set xt_tgchk_param par.nft_compat as 0 in ipt_init_target
tcp: fastopen: tcp_connect() must refresh the route
qmi_wwan: fix NULL deref on disconnect
net: avoid skb_warn_bad_offload false positives on UFO
igmp: Fix regression caused by igmp sysctl namespace code.
udp: consistently apply ufo or fragmentation
packet: fix tp_reserve race in packet_set_ring
scsi: sg: only check for dxfer_len greater than 256M
btrfs: Remove false alert when fiemap range is smaller than on-disk extent
Linux 4.12.7

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

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


** Tags: kernel-stable-tracking-bug

** Tags added: kernel-stable-tracking-bug

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

** 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 v4.12.7 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 v4.12.7 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 v4.12.7 stable release shall be
+ applied:
  
-The following patches from the v4.12.7 stable release shall be
- applied:
+ ppp: Fix false xmit recursion detect with two ppp devices
+ ppp: fix xmit recursion detection on ppp channels
+ tcp: avoid setting cwnd to invalid ssthresh after cwnd reduction states
+ net: fix keepalive code vs TCP_FASTOPEN_CONNECT
+ ipv6: set rt6i_protocol properly in the route when it is installed
+ bpf, s390: fix jit branch offset related to ldimm64
+ net/mlx4_en: don't set CHECKSUM_COMPLETE on SCTP packets
+ net: sched: set xt_tgchk_param par.net properly in ipt_init_target
+ net: sched: set xt_tgchk_param par.nft_compat as 0 in ipt_init_target
+ tcp: fastopen: tcp_connect() must refresh the route
+ qmi_wwan: fix NULL deref on disconnect
+ net: avoid skb_warn_bad_offload false positives on UFO
+ igmp: Fix regression caused by igmp sysctl namespace code.
+ udp: consistently apply ufo or fragmentation
+ packet: fix tp_reserve race in packet_set_ring
+ scsi: sg: only check for dxfer_len greater than 256M
+ btrfs: Remove false alert when fiemap range is smaller than on-disk extent
+ Linux 4.12.7

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

Title:
  Artful update to v4.12.7 stable release

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

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 v4.12.7 upstream stable
    

[Kernel-packages] [Bug 1707875] Re: include support for Python bindings in "perf"

[Manoj Iyer]

** Tags added: triage-g

** Tags removed: triage-g
** Tags added: triage-a

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

Title:
  include support for Python bindings in "perf"

Status in The Ubuntu-power-systems project:
  New
Status in linux package in Ubuntu:
  New

Bug description:
  == Comment: #0 - Paul A. Clarke  - 2017-07-26 09:59:57 ==
  ---Problem Description---
  Request to build python bindings support with perf.

  ---Steps to Reproduce---
   Ubuntu-17.04# perf script -g python
  Python scripting not supported.  Install libpython and rebuild perf to enable 
it.
  For example:
# apt-get install python-dev (ubuntu)
# yum install python-devel (Fedora)
etc.
   
  Userspace tool common name: perf 
   
  Userspace rpm: linux-tools-common 

  Userspace tool obtained from project website:  na

  == Comment: #2 - MAMATHA INAMDAR  - 2017-08-01 05:02:34 
==
  After installing libpython, downloaded ubuntu 17.04 linux source code and 
compiled perf tool then it works fine.

  # ./perf script  -g python 
  generated Python script: perf-script.py

  but when I run perf tool without rebuilding after installing libpython
  it shows an error

  # perf script  -g python 
  Python scripting not supported.  Install libpython and rebuild perf to enable 
it.
  For example:
# apt-get install python-dev (ubuntu)
# yum install python-devel (Fedora)
etc.
  root@p8wookie:/home/Mamatha/ubuntu/ubuntu-zesty/tools/perf# perf --version
  perf version 4.10.17

  == Comment: #3 - MAMATHA INAMDAR  - 2017-08-01 05:03:44 
==
  Request to build python bindings support with perf.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1707875/+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 1686019] Comment bridged from LTC Bugzilla

[bugproxy]

--- Comment From jos...@br.ibm.com 2017-08-14 09:53 EDT---
The patches are applied.

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

Title:
  Ubuntu 16.04.3: Qemu fails on P9

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

Bug description:
  Trying to start KVM on Ubuntu 16.04.3 with QEMU from dgibson 2.10
  tree[1], I see the following error when trying to boot a 17.04 image.

  8000 DISK : "QEMU QEMU HARDDISK2.5+"
  Populating /pci@8002000
  No NVRAM common partition, re-initializing...
  Scanning USB 
  Using default console: /vdevice/vty@7100
   ted RAM kernel at 40 (17995b0 bytes) C08FF
Welcome to Open Firmware

Copyright (c) 2004, 2011 IBM Corporation All rights reserved.
This program and the accompanying materials are made available
under the terms of the BSD License available at
http://www.opensource.org/licenses/bsd-license.php

  Booting from memory...
  OF stdout device is: /vdevice/vty@7100
  Preparing to boot Linux version 4.10.0-19-generic (buildd@bos01-ppc64el-009) 
(gcc version 6.3.0 20170321 (Ubuntu 6.3.0-10ubuntu1) ) #21-Ubuntu SMP Thu Apr 6 
17:03:05 UTC 2017 (Ubuntu 4.10.0-19.21-generic 4.10.8)
  Detected machine type: 0101
  command line: debug initcall_debug udbg-immortal console=/dev/hvc0
  Max number of cores passed to firmware: 2048 (NR_CPUS = 2048)
  Calling ibm,client-architecture-support... done
  memory layout at init:
memory_limit :  (16 MB aligned)
alloc_bottom : 01bb
alloc_top: 1000
alloc_top_hi : 8000
rmo_top  : 1000
ram_top  : 8000
  instantiating rtas at 0x0daf... done
  prom_hold_cpus: skipped
  copying OF device tree...
  Building dt strings...
  Building dt structure...
  Device tree strings 0x041c -> 0x041c09fd
  Device tree struct  0x041d -> 0x041e
  Quiescing Open Firmware ...
  Booting Linux via __start() @ 0x0040 ...

  
  I tried to add some debug options as "debug initcall_debug udbg-immortal 
console=/dev/hvc0" but no luck. 

  [1] https://github.com/dgibson/qemu.git branch ppc-for-2.10
   
  ---uname output---
  4.10.0-19

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1686019/+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

[Frank Heimes]

** Changed in: ubuntu-power-systems
   Status: New => In Progress

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

Title:
  xfstest sanity checks on seek operations fails

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

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 1689365] Re: ibmvscsis: Do not send aborted task response

[Manoj Iyer]

** Changed in: ubuntu-power-systems
   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/1689365

Title:
  ibmvscsis: Do not send aborted task response

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

Bug description:
  [Impact]
  ibmvscsis: Do not send aborted task response

  The driver is sending a response to the actual scsi op that was
  aborted by an abort task TM, while LIO is sending a response to
  the abort task TM.

  ibmvscsis_tgt does not send the response to the client until
  release_cmd time. The reason for this was because if we did it
  at queue_status time, then the client would be free to reuse the
  tag for that command, but we're still using the tag until the
  command is released at release_cmd time, so we chose to delay
  sending the response until then. That then caused this issue, because
  release_cmd is always called, even if queue_status is not.

  SCSI spec says that the initiator that sends the abort task
  TM NEVER gets a response to the aborted op and with the current
  code it will send a response. Thus this fix will remove that response
  if the CMD_T_ABORTED && !CMD_T_TAS.

  Another case with a small timing window is the case where if LIO sends a
  TMR_DOES_NOT_EXIST, and the release_cmd callback is called for the TMR Abort
  cmd before the release_cmd for the (attemped) aborted cmd, then we need to
  ensure that we send the response for the (attempted) abort cmd to the client
  before we send the response for the TMR Abort cmd.

  [Test Case]
  As per comment #11, this requires sending manual abort signals to trigger the 
bug.

  [Fix]
  ibmvscsis: Fix the incorrect req_lim_delta
  ibmvscsis: Clear left-over abort_cmd pointers
  ibmvscsis: Do not send aborted task response
  target: Fix unknown fabric callback queue-full errors

  [Regression Potential]
  Patches are confined to ibmvscsi driver and target driver.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1689365/+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 1635597] Re: Ubuntu16.10:talclp1: Kdump failed with multipath disk

[Manoj Iyer]

** Changed in: makedumpfile (Ubuntu)
 Assignee: Louis Bouchard (louis) => David Britton (davidpbritton)

** Changed in: makedumpfile (Ubuntu Trusty)
 Assignee: Louis Bouchard (louis) => David Britton (davidpbritton)

** Changed in: makedumpfile (Ubuntu Xenial)
 Assignee: Louis Bouchard (louis) => David Britton (davidpbritton)

** Changed in: makedumpfile (Ubuntu Zesty)
 Assignee: Louis Bouchard (louis) => David Britton (davidpbritton)

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

Title:
  Ubuntu16.10:talclp1: Kdump failed with multipath disk

Status in The Ubuntu-power-systems project:
  In Progress
Status in linux package in Ubuntu:
  Invalid
Status in makedumpfile package in Ubuntu:
  In Progress
Status in linux source package in Trusty:
  Invalid
Status in makedumpfile source package in Trusty:
  Confirmed
Status in linux source package in Xenial:
  Invalid
Status in makedumpfile source package in Xenial:
  Confirmed
Status in linux source package in Zesty:
  Invalid
Status in makedumpfile source package in Zesty:
  Confirmed

Bug description:
  Problem  Description
  ==
  On talclp1, I enabled kdump. But kdump failed and it drop to BusyBox.

  root@talclp1:~# echo c> /proc/sysrq-trigger
  [  132.643690] sysrq: SysRq : Trigger a crash
  [  132.643739] Unable to handle kernel paging request for data at address 
0x
  [  132.643745] Faulting instruction address: 0xc05c28f4
  [  132.643749] Oops: Kernel access of bad area, sig: 11 [#1]
  [  132.643753] SMP NR_CPUS=2048 NUMA pSeries
  [  132.643758] Modules linked in: fuse ufs qnx4 hfsplus hfs minix ntfs msdos 
jfs rpadlpar_io rpaphp rpcsec_gss_krb5 nfsv4 dccp_diag cifs nfs dns_resolver 
dccp tcp_diag fscache udp_diag inet_diag unix_diag af_packet_diag netlink_diag 
binfmt_misc xfs libcrc32c pseries_rng rng_core ghash_generic gf128mul 
vmx_crypto sg nfsd auth_rpcgss nfs_acl lockd grace sunrpc ip_tables x_tables 
autofs4 ext4 crc16 jbd2 fscrypto mbcache crc32c_generic btrfs xor raid6_pq 
dm_round_robin sr_mod sd_mod cdrom ses enclosure scsi_transport_sas ibmveth 
crc32c_vpmsum ipr scsi_dh_emc scsi_dh_rdac scsi_dh_alua dm_multipath dm_mod
  [  132.643819] CPU: 49 PID: 10174 Comm: bash Not tainted 4.8.0-15-generic 
#16-Ubuntu
  [  132.643824] task: c00111767080 task.stack: c000d82e
  [  132.643828] NIP: c05c28f4 LR: c05c39d8 CTR: 
c05c28c0
  [  132.643832] REGS: c000d82e3990 TRAP: 0300   Not tainted  
(4.8.0-15-generic)
  [  132.643836] MSR: 80009033   CR: 28242422  
XER: 0001
  [  132.643848] CFAR: c00087d0 DAR:  DSISR: 4200 
SOFTE: 1
  GPR00: c05c39d8 c000d82e3c10 c0f67b00 0063
  GPR04: c0011d04a9b8 c0011d05f7e0 c0047fb0 00015998
  GPR08: 0007 0001  0001
  GPR12: c05c28c0 c7b4b900  2200
  GPR16: 10170dc8 01002b566368 10140f58 100c7570
  GPR20:  1017dd58 10153618 1017b608
  GPR24: 3e87a294 0001 c0ebff60 0004
  GPR28: c0ec0320 0063 c0e72a90 
  [  132.643906] NIP [c05c28f4] sysrq_handle_crash+0x34/0x50
  [  132.643911] LR [c05c39d8] __handle_sysrq+0xe8/0x280
  [  132.643914] Call Trace:
  [  132.643917] [c000d82e3c10] [c0a245e8] 0xc0a245e8 
(unreliable)
  [  132.643923] [c000d82e3c30] [c05c39d8] __handle_sysrq+0xe8/0x280
  [  132.643928] [c000d82e3cd0] [c05c4188] 
write_sysrq_trigger+0x78/0xa0
  [  132.643935] [c000d82e3d00] [c03ad770] proc_reg_write+0xb0/0x110
  [  132.643941] [c000d82e3d50] [c030fc3c] __vfs_write+0x6c/0xe0
  [  132.643946] [c000d82e3d90] [c0311144] vfs_write+0xd4/0x240
  [  132.643950] [c000d82e3de0] [c0312e5c] SyS_write+0x6c/0x110
  [  132.643957] [c000d82e3e30] [c00095e0] system_call+0x38/0x108
  [  132.643961] Instruction dump:
  [  132.643963] 38425240 7c0802a6 f8010010 f821ffe1 6000 6000 3d220019 
3949ba60
  [  132.643972] 3921 912a 7c0004ac 3940 <992a> 38210020 
e8010010 7c0803a6
  [  132.643981] ---[ end trace eed6bbcd2c3bdfdf ]---
  [  132.646105]
  [  132.646176] Sending IPI to other CPUs
  [  132.647490] IPI complete
  I'm in purgatory
   -> smp_release_cpus()
  spinning_secondaries = 104
   <- smp_release_cpus()
  [2.011346] alg: hash: Test 1 failed for crc32c-vpmsum
  [2.729254] sd 0:2:0:0: [sda] Assuming drive cache: write through
  [2.731554] sd 1:2:5:0: [sdn] Assuming drive cache: write through
  [2.739087] sd 1:2:4:0: [sdm] Assuming drive cache: write through
  [2.739089] sd 1:2:6:0: 

[Kernel-packages] [Bug 1696375] Re: cpupower suggests installation of non-existent linux-cloud-tools-generic package

[Manoj Iyer]

IBM, could you please validate this on 16.04.3 and report back here is
this issue is fixed or still valid?

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

Title:
  cpupower suggests installation of non-existent linux-cloud-tools-
  generic package

Status in The Ubuntu-power-systems project:
  Triaged
Status in linux package in Ubuntu:
  Triaged

Bug description:
  Problem Description
  ===
  cpupower suggests installation of non-existent linux-cloud-tools-generic 
package

  Problem occurs on an IBM POWER 16.04 LTS system. Unknown whether it
  occurs on other architectures or later releases.

  When run _without package "linux-tools-$(uname -r)" installed_,
  cpupower will issue a complaint, suggesting to install (among others),
  some linux-cloud-tools-*-generic packages:

  $ cpupower
  WARNING: cpupower not found for kernel 4.4.0-75

You may need to install the following packages for this specific kernel:
  linux-tools-4.4.0-75-generic
  linux-cloud-tools-4.4.0-75-generic

You may also want to install one of the following packages to keep up to 
date:
  linux-tools-generic
  linux-cloud-tools-generic

  However, those linux-cloud-tools-*-generic package appear not to exist
  --at least not in the default repos.

  Package linux-cloud-tools-common exists, but none of the *-generic
  packages are available:

  $ apt-cache policy "linux-cloud-*"
  $ cat xxx
  linux-cloud-tools-common:
Installed: (none)
Candidate: 4.4.0-78.99
Version table:
   4.4.0-78.99 500
  500 http://ports.ubuntu.com/ubuntu-ports xenial-proposed/main ppc64el 
Packages
   4.4.0-77.98 500
  500 http://us.ports.ubuntu.com/ubuntu-ports xenial-updates/main 
ppc64el Packages
   4.4.0-75.96 500
  500 http://us.ports.ubuntu.com/ubuntu-ports xenial-updates/main 
ppc64el Packages
  500 http://ports.ubuntu.com/ubuntu-ports xenial-security/main ppc64el 
Packages
  [...]
   4.4.0-21.37 500
  500 http://us.ports.ubuntu.com/ubuntu-ports xenial/main ppc64el 
Packages

  
  The cpupower command works (at least doesn't give this complaint) if the 
appropriate linux-tools-$(uname -r) (perhaps via linux-tools-generic) is 
installed, so the cloud package is maybe not needed (as least for some 
functionality).

  I think the fix is to either: 
  a) supply the cloud packages for POWER, or 
  b) remove the non-existent packages from cpupower's complaint message.
   
  ---uname output---
  Linux fs3 4.4.0-75-generic #96-Ubuntu SMP Thu Apr 20 09:55:30 UTC 2017 
ppc64le ppc64le ppc64le GNU/Linux
   
  Machine Type = Firestone 
   
  ---Steps to Reproduce---
   Install linux-tools-common but NOT linux-tools-*-generic on a POWER 16.04 
LTS system, then run cpupower.

  Userspace rpm: linux-tools-common

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1696375/+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 1655280] Re: ISST-LTE:pVM:roselp4:ubuntu 16.04.2: cp: error reading '/proc/vmcore': Bad address when trying to dump vmcore

[Manoj Iyer]

** Changed in: ubuntu-power-systems
   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/1655280

Title:
  ISST-LTE:pVM:roselp4:ubuntu 16.04.2: cp: error reading '/proc/vmcore':
  Bad address when trying to dump vmcore

Status in The Ubuntu-power-systems project:
  Triaged
Status in linux package in Ubuntu:
  New

Bug description:
  == Comment: #0 - Ping Tian Han  - 2017-01-09 02:51:00 ==
  ---Problem Description---
  Vmcore cannot be saved when triggering bug 150353 on roselp4:

  Copying data   : [  2.0 %] \/usr/sbin/kdump-config: line 
591:  5502 Bus error   makedumpfile $MAKEDUMP_ARGS $vmcore_file 
$KDUMP_CORETEMP
  [  512.833872] kdump-tools[5450]:  * kdump-tools: makedumpfile failed, 
falling back to 'cp'
  [  573.595449] kdump-tools[5450]: cp: error reading '/proc/vmcore': Bad 
address
  [  573.605717] kdump-tools[5450]:  * kdump-tools: failed to save vmcore in 
/var/crash/201701090223
  [  573.765417] kdump-tools[5450]:  * running makedumpfile --dump-dmesg 
/proc/vmcore /var/crash/201701090223/dmesg.201701090223
  [  574.285506] kdump-tools[5450]: The kernel version is not supported.
  [  574.285672] kdump-tools[5450]: The makedumpfile operation may be 
incomplete.
  [  574.285767] kdump-tools[5450]: The dmesg log is saved to 
/var/crash/201701090223/dmesg.201701090223.
  [  574.305422] kdump-tools[5450]: makedumpfile Completed.
  [  574.315363] kdump-tools[5450]:  * kdump-tools: saved dmesg content in 
/var/crash/201701090223
  [  574.615688] kdump-tools[5450]: Mon, 09 Jan 2017 02:24:26 -0600
  [  574.705384] kdump-tools[5450]: Rebooting.
   Stopping ifup for ib0...
  [  OK  ] Stopped ifup for ib0.
  [ 1008.579897] reboot: Restarting system
   
  Contact Information = Ping Tian Han/pt...@cn.ibm.com Carrie 
Mitsuyoshi/carri...@us.ibm.com 
   
  ---uname output---
  Linux roselp4 4.8.0-34-generic #36~16.04.1-Ubuntu SMP Wed Dec 21 18:53:20 UTC 
2016 ppc64le ppc64le ppc64le GNU/Linux
   
  Machine Type = lpar 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   1. config kdump on roselp4
  2. try to trigger bug 150353

   
  *Additional Instructions for Ping Tian Han/pt...@cn.ibm.com Carrie 
Mitsuyoshi/carri...@us.ibm.com: 
  -Post a private note with access information to the machine that the bug is 
occuring on.

  == Comment: #3 - Brahadambal Srinivasan  -
  2017-01-10 02:42:25 ==

  root@roselp4:~# cat /proc/cmdline
  BOOT_IMAGE=/boot/vmlinux-4.8.0-34-generic 
root=UUID=0bcf3431-df8b-499c-9a13-33070f242e0c ro splash quiet 
crashkernel=384M-:512M

  root@roselp4:~# dmesg | grep Reser
  [0.00] Reserving 512MB of memory at 128MB for crashkernel (System 
RAM: 21760MB)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1655280/+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 1709300] Re: linux-aws: 4.4.0-1032.41 -proposed tracker

[Brad Figg]

** Changed in: kernel-sru-workflow/prepare-package
   Status: In Progress => Fix Released

** Changed in: kernel-sru-workflow/prepare-package-meta
   Status: In Progress => Fix Released

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  kernel-stable-master-bug: 1709296
  phase: Packaging
+ kernel-stable-phase-changed:Monday, 14. August 2017 13:33 UTC
+ kernel-stable-phase:Uploaded

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  kernel-stable-master-bug: 1709296
- phase: Packaging
- kernel-stable-phase-changed:Monday, 14. August 2017 13:33 UTC
- kernel-stable-phase:Uploaded
+ phase: Uploaded

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

Title:
  linux-aws: 4.4.0-1032.41 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  New
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:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-aws package in Ubuntu:
  Invalid
Status in linux-aws source package in Xenial:
  Confirmed

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  kernel-stable-master-bug: 1709296
  phase: Uploaded

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1709300/+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 1705493] Re: [4.4][backport] Multiple partitions are not supported on a bcache device

[Dmitrii Shcherbakov]

SRU request thread:

https://lists.ubuntu.com/archives/kernel-team/2017-July/086054.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/1705493

Title:
  [4.4][backport] Multiple partitions are not supported on a bcache
  device

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

Bug description:
  Support for adding partitions on bcache devices only landed in 4.10:

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

  Although it is a small change, it is not backported to any of the
  xenial kernels and it only exists naturally in 4.10.

  ➜ ubuntu-xenial git:(master) git tag 
--contains=b8c0d911ac5285e6be8967713271a51bdc5a936a
  Ubuntu-hwe-4.10.0-13.15_16.04.2
  Ubuntu-hwe-4.10.0-14.16_16.04.1
  Ubuntu-hwe-4.10.0-19.21_16.04.1
  Ubuntu-hwe-4.10.0-20.22_16.04.1
  Ubuntu-hwe-4.10.0-21.23_16.04.1
  Ubuntu-hwe-4.10.0-22.24_16.04.1
  Ubuntu-hwe-4.10.0-25.29_16.04.1
  Ubuntu-hwe-4.10.0-26.30_16.04.1
  Ubuntu-hwe-4.10.0-28.32_16.04.1
  Ubuntu-hwe-edge-4.10.0-9.11_16.04.2
  Ubuntu-lts-4.10.0-10.12_16.04.1
  Ubuntu-lts-4.10.0-11.13_16.04.1
  Ubuntu-lts-4.10.0-12.14_16.04.1
  Ubuntu-lts-4.10.0-13.15_16.04.1
  Ubuntu-lts-4.10.0-7.9_16.04.1
  Ubuntu-lts-4.10.0-8.10_16.04.1
  Ubuntu-lts-4.10.0-9.11_16.04.1
  Ubuntu-lts-4.10.0-9.11_16.04.2

  This will prevent usage of multiple partitions on the same device
  which is the case when data and journal are collocated.

  Also, the lack of that feature prevents dmcrypt usage as multiple
  partitions are created on a device in this case.

  
  Could that be backported to the 4.4 kernel?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1705493/+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 1707663] Re: include scsi_debug module on linux-image package

[Kleber Sacilotto de Souza]

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

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

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

Title:
  include scsi_debug module on linux-image package

Status in linux-aws package in Ubuntu:
  Invalid
Status in linux-gke package in Ubuntu:
  Invalid
Status in linux-aws source package in Xenial:
  Fix Committed
Status in linux-gke source package in Xenial:
  Fix Committed

Bug description:
  The systemd autopkgtest 'storage' testcase needs to load the
  scsi_debug module to perform its tests. The testcase is currently
  failing on the following custom kernels:

  * linux-aws: doesn't ship the scsi_debug module
  * linux-gke: ships the scsi_debug module on the linux-image-extra-*-gke 
module, however the package is not installed by autopkgtest since it's not 
installed by the linux-image-gke meta-package.

  linux-aws (4.4.0-1027.36) -
  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
  /autopkgtest-
  xenial/xenial/amd64/s/systemd/20170731_111630_98aef@/log.gz

  linux-gke (4.4.0-1023.23) -
  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
  /autopkgtest-
  xenial/xenial/amd64/s/systemd/20170731_111633_b6dbe@/log.gz

  One solution would be to include the scsi_debug.ko module on the
  linux-aws and linux-gke linux-image package so it would be available
  for the testcase. The module is very small (130KB on gke), it won't be
  automatically loaded on the system and it doesn't affect the normal
  operation when loaded.

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

[Kleber Sacilotto de Souza]

** Summary changed:

- linux-aws:  -proposed tracker
+ linux-aws: 4.4.0-1032.41 -proposed tracker

** Changed in: kernel-sru-workflow/prepare-package
   Status: Confirmed => In Progress

** Changed in: kernel-sru-workflow/prepare-package
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Kleber 
Sacilotto de Souza (kleber-souza)

** Changed in: kernel-sru-workflow/prepare-package-meta
   Status: New => In Progress

** Changed in: kernel-sru-workflow/prepare-package-meta
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Kleber 
Sacilotto de Souza (kleber-souza)

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

Title:
  linux-aws: 4.4.0-1032.41 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  In Progress
Status in Kernel SRU Workflow prepare-package-meta series:
  In Progress
Status in Kernel SRU Workflow promote-to-proposed series:
  New
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:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-aws package in Ubuntu:
  Invalid
Status in linux-aws source package in Xenial:
  Confirmed

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  kernel-stable-master-bug: 1709296
  phase: Packaging

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1709300/+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 1709749] Re: Docker hangs with xfs using aufs storage driver

[Seth Forshee]

** Description changed:

+ SRU Justification
+ 
+ Impact: Running the yum command in a Centos/RHEL container causes the
+ process to hang enter uninterruptible sleep mode if /var/lib/docker is
+ hosted on an XFS filesystem while the AUFS storage driver is used.
+ 
+ Fix: Commit e34c81ff96415c64ca827ec30e7935454d26c1d3 from upstream aufs-
+ standalone. Requires prerequisite commit
+ b4d3dcc92a13d53952fe6e9a640201ef87475302.
+ 
+ Test Case: Test scenario described above. Kernel with fixes applied has
+ been confirmed by reporter to fix the issue.
+ 
+ Regression Potential: Both patches have been in upstream aufs-standalone
+ for a while now and included in the artful kernel as well as currently
+ being included in the upstream branch for 4.10. Therefore they are well
+ tested and unlikely to cause regressions.
+ 
+ ---
+ 
  1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> 
About Ubuntu
  Ubuntu 16.04 and 17.04
  
  2) The version of the package you are using, via 'apt-cache policy pkgname' 
or by checking in Software Center
  kernel 4.10.0-28-generic
  
  3) What you expected to happen
  
  Docker with AUFS on XFS works.
  
  4) What happened instead
  
  It hangs up
  
  ---
  
  As reported in https://github.com/moby/moby/issues/34361 , AUFS on XFS
  needs this fix for kernel 4.10:
  
https://github.com/sfjro/aufs4-standalone/commit/e34c81ff96415c64ca827ec30e7935454d26c1d3

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

Title:
  Docker hangs with xfs using aufs storage driver

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

Bug description:
  SRU Justification

  Impact: Running the yum command in a Centos/RHEL container causes the
  process to hang enter uninterruptible sleep mode if /var/lib/docker is
  hosted on an XFS filesystem while the AUFS storage driver is used.

  Fix: Commit e34c81ff96415c64ca827ec30e7935454d26c1d3 from upstream
  aufs-standalone. Requires prerequisite commit
  b4d3dcc92a13d53952fe6e9a640201ef87475302.

  Test Case: Test scenario described above. Kernel with fixes applied
  has been confirmed by reporter to fix the issue.

  Regression Potential: Both patches have been in upstream aufs-
  standalone for a while now and included in the artful kernel as well
  as currently being included in the upstream branch for 4.10. Therefore
  they are well tested and unlikely to cause regressions.

  ---

  1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> 
About Ubuntu
  Ubuntu 16.04 and 17.04

  2) The version of the package you are using, via 'apt-cache policy pkgname' 
or by checking in Software Center
  kernel 4.10.0-28-generic

  3) What you expected to happen

  Docker with AUFS on XFS works.

  4) What happened instead

  It hangs up

  ---

  As reported in https://github.com/moby/moby/issues/34361 , AUFS on XFS
  needs this fix for kernel 4.10:
  
https://github.com/sfjro/aufs4-standalone/commit/e34c81ff96415c64ca827ec30e7935454d26c1d3

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1709749/+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 1709749] Re: AUFS on XFS needs fix for kernel 4.10

[Seth Forshee]

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

** Summary changed:

- AUFS on XFS needs fix for kernel 4.10
+ Docker hangs with xfs using aufs storage driver

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

Title:
  Docker hangs with xfs using aufs storage driver

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

Bug description:
  SRU Justification

  Impact: Running the yum command in a Centos/RHEL container causes the
  process to hang enter uninterruptible sleep mode if /var/lib/docker is
  hosted on an XFS filesystem while the AUFS storage driver is used.

  Fix: Commit e34c81ff96415c64ca827ec30e7935454d26c1d3 from upstream
  aufs-standalone. Requires prerequisite commit
  b4d3dcc92a13d53952fe6e9a640201ef87475302.

  Test Case: Test scenario described above. Kernel with fixes applied
  has been confirmed by reporter to fix the issue.

  Regression Potential: Both patches have been in upstream aufs-
  standalone for a while now and included in the artful kernel as well
  as currently being included in the upstream branch for 4.10. Therefore
  they are well tested and unlikely to cause regressions.

  ---

  1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> 
About Ubuntu
  Ubuntu 16.04 and 17.04

  2) The version of the package you are using, via 'apt-cache policy pkgname' 
or by checking in Software Center
  kernel 4.10.0-28-generic

  3) What you expected to happen

  Docker with AUFS on XFS works.

  4) What happened instead

  It hangs up

  ---

  As reported in https://github.com/moby/moby/issues/34361 , AUFS on XFS
  needs this fix for kernel 4.10:
  
https://github.com/sfjro/aufs4-standalone/commit/e34c81ff96415c64ca827ec30e7935454d26c1d3

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1709749/+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 1700657] Re: Touchpad not detected in Lenovo X1 Yoga / Yoga 720-15IKB

[Mattia]

I downloaded the kernel source (newest stable), added the line you
mentioned and compiled it. It works for me.

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

Title:
  Touchpad not detected in Lenovo X1 Yoga / Yoga 720-15IKB

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Fix Committed

Bug description:
  Touchpad is not automatically detected in 14.04, 16.04 or 17.04. I
  tried in live mode and after full installation. I was able to connect
  an external mouse and a bluetooth mouse and both worked. I checked my
  xinput list and no sign:

  ⎡ Virtual core pointerid=2[master pointer
  (3)] ⎜   ↳ Virtual core XTEST pointer  id=4[slave
  pointer  (2)] ⎜   ↳ Wacom HID 50FE Finger touch id=12
  [slave  pointer  (2)] ⎜   ↳ Wacom HID 50FE Pen stylus
  id=13[slave  pointer  (2)] ⎜   ↳ Wacom HID 50FE Pen eraser
  id=16[slave  pointer  (2)] ⎜   ↳ byron's trackpad
  id=17[slave  pointer  (2)] ⎣ Virtual core keyboard
  id=3[master keyboard (2)]↳ Virtual core XTEST keyboard
  id=5[slave  keyboard (3)]↳ Power Button
  id=6[slave  keyboard (3)]↳ Video Bus
  id=7[slave  keyboard (3)]↳ Video Bus
  id=8[slave  keyboard (3)]↳ Power Button
  id=9[slave  keyboard (3)]↳ Apple Inc. Magic Keyboard
  id=10[slave  keyboard (3)]↳ EasyCamera
  id=11[slave  keyboard (3)]↳ Ideapad extra buttons
  id=14[slave  keyboard (3)]↳ AT Translated Set 2 keyboard
  id=15[slave  keyboard (3)]

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-24-generic 4.10.0-24.28
  ProcVersionSignature: Ubuntu 4.10.0-24.28-generic 4.10.15
  Uname: Linux 4.10.0-24-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  byron  1794 F pulseaudio
  CurrentDesktop: Unity:Unity7
  Date: Mon Jun 26 16:51:37 2017
  InstallationDate: Installed on 2017-06-26 (0 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: LENOVO 80X7
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-24-generic.efi.signed 
root=UUID=39280165-1a70-4b0d-b1fa-3b01e8bc1e25 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-24-generic N/A
   linux-backports-modules-4.10.0-24-generic  N/A
   linux-firmware 1.164
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/12/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 4MCN20WW(V1.06)
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: Lenovo YOGA 720-15IKB
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo YOGA 720-15IKB
  dmi.modalias: 
dmi:bvnLENOVO:bvr4MCN20WW(V1.06):bd04/12/2017:svnLENOVO:pn80X7:pvrLenovoYOGA720-15IKB:rvnLENOVO:rnLenovoYOGA720-15IKB:rvrSDK0J40709WIN:cvnLENOVO:ct31:cvrLenovoYOGA720-15IKB:
  dmi.product.name: 80X7
  dmi.product.version: Lenovo YOGA 720-15IKB
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1700657/+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 1708495] Re: usb 3-1: Warning! Unlikely big volume range (=10361), cval->res is probably wrong.

[Kai-Heng Feng]

Then it's just a warning, can be safely ignored.

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

Title:
  usb 3-1: Warning! Unlikely big volume range (=10361), cval->res is
  probably wrong.

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hello,

  dmesg:
  [   51.235163] input: Plantronics Plantronics C310 as 
/devices/pci:00/:00:14.0/usb3/3-1/3-1:1.3/0003:047F:C022.0002/input/input12
  [   51.242659] usb 3-1: Warning! Unlikely big volume range (=10361), 
cval->res is probably wrong.
  [   51.242666] usb 3-1: [11] FU [Sidetone Playback Volume] ch = 1, val = 
0/10361/1
  [   51.247916] usbcore: registered new interface driver snd-usb-audio
  [   51.294684] plantronics 0003:047F:C022.0002: input,hiddev0,hidraw1: USB 
HID v1.11 Device [Plantronics Plantronics C310] on usb-:00:14.0-1/input3

  Regards,
  --
  Cristian

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.11.0-10-generic 4.11.0-10.15
  ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8
  Uname: Linux 4.11.0-10-generic x86_64
  ApportVersion: 2.20.6-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  caravena   1452 F pulseaudio
   /dev/snd/controlC0:  caravena   1452 F pulseaudio
  CurrentDesktop: GNOME
  Date: Thu Aug  3 13:16:37 2017
  HibernationDevice: RESUME=UUID=360bd2d2-4f44-4311-86d6-4781ac81ee87
  InstallationDate: Installed on 2017-07-05 (28 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.11.0-10-generic 
root=UUID=6b614287-8ce5-49c5-b66d-e92fa9568c2b ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.11.0-10-generic N/A
   linux-backports-modules-4.11.0-10-generic  N/A
   linux-firmware 1.167
  SourcePackage: linux
  UpgradeStatus: Upgraded to artful on 2017-07-05 (28 days ago)
  dmi.bios.date: 04/15/2013
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: P14AAJ
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: SAMSUNG_NP1234567890
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: FAB1
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvrP14AAJ:bd04/15/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1:
  dmi.product.name: 530U3C/530U4C
  dmi.product.version: 0.1
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1708495/+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 1708495] Re: usb 3-1: Warning! Unlikely big volume range (=10361), cval->res is probably wrong.

[Cristian Aravena Romero]

Hello Kai-Heng,

> Does volume work?

Yes

Regards,
--
Cristian

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

Title:
  usb 3-1: Warning! Unlikely big volume range (=10361), cval->res is
  probably wrong.

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hello,

  dmesg:
  [   51.235163] input: Plantronics Plantronics C310 as 
/devices/pci:00/:00:14.0/usb3/3-1/3-1:1.3/0003:047F:C022.0002/input/input12
  [   51.242659] usb 3-1: Warning! Unlikely big volume range (=10361), 
cval->res is probably wrong.
  [   51.242666] usb 3-1: [11] FU [Sidetone Playback Volume] ch = 1, val = 
0/10361/1
  [   51.247916] usbcore: registered new interface driver snd-usb-audio
  [   51.294684] plantronics 0003:047F:C022.0002: input,hiddev0,hidraw1: USB 
HID v1.11 Device [Plantronics Plantronics C310] on usb-:00:14.0-1/input3

  Regards,
  --
  Cristian

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.11.0-10-generic 4.11.0-10.15
  ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8
  Uname: Linux 4.11.0-10-generic x86_64
  ApportVersion: 2.20.6-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  caravena   1452 F pulseaudio
   /dev/snd/controlC0:  caravena   1452 F pulseaudio
  CurrentDesktop: GNOME
  Date: Thu Aug  3 13:16:37 2017
  HibernationDevice: RESUME=UUID=360bd2d2-4f44-4311-86d6-4781ac81ee87
  InstallationDate: Installed on 2017-07-05 (28 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.11.0-10-generic 
root=UUID=6b614287-8ce5-49c5-b66d-e92fa9568c2b ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.11.0-10-generic N/A
   linux-backports-modules-4.11.0-10-generic  N/A
   linux-firmware 1.167
  SourcePackage: linux
  UpgradeStatus: Upgraded to artful on 2017-07-05 (28 days ago)
  dmi.bios.date: 04/15/2013
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: P14AAJ
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: SAMSUNG_NP1234567890
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: FAB1
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvrP14AAJ:bd04/15/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1:
  dmi.product.name: 530U3C/530U4C
  dmi.product.version: 0.1
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1708495/+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 1710601] Re: bluetoothctl fails to connect

[doru001]

** Description changed:

- bluetooth stopped working after some update, probably to bluez5 
- before it was working flawlessly following 
https://wiki.archlinux.org/index.php/Bluetooth#Configuration_via_the_CLI 
- now $ bluetoothctl shows no typed characters, $ sudo bluetoothctl works well 
until I try to connect the device: 
- [bluetooth]# connect A8:7E:33:FC:6D:15 
+ bluetooth stopped working after some update, probably to bluez5
+ before it was working flawlessly following 
https://wiki.archlinux.org/index.php/Bluetooth#Configuration_via_the_CLI
+ now $ bluetoothctl shows no typed characters, $ sudo bluetoothctl works well 
until I try to connect the device:
+ [bluetooth]# connect A8:7E:33:FC:6D:15
  Attempting to connect to A8:7E:33:FC:6D:15
  [CHG] Device A8:7E:33:FC:6D:15 Connected: yes
  Failed to connect: org.bluez.Error.NotAvailable
  [CHG] Device A8:7E:33:FC:6D:15 Connected: no
  [CHG] Device A8:7E:33:FC:6D:15 RSSI: -81
  [CHG] Device A8:7E:33:FC:6D:15 RSSI: -63
  [CHG] Device A8:7E:33:FC:6D:15 RSSI: -73
  [CHG] Device A8:7E:33:FC:6D:15 RSSI: -65
  [CHG] Device A8:7E:33:FC:6D:15 RSSI: -79
  [CHG] Device A8:7E:33:FC:6D:15 RSSI: -61
  [CHG] Device A8:7E:33:FC:6D:15 RSSI: -75
  [CHG] Device A8:7E:33:FC:6D:15 RSSI: -63
  
  I am using bluez 5.37-0ubuntu5 under Ubuntu 16.04.3 LTS, updated to the
  day.
  
- I found errors in logs: 
+ I found errors in logs:
  aug 13 17:34:25 george bluetoothd[752]: Starting SDP server
  aug 13 17:34:26 george ModemManager[738]:   ModemManager (version 
1.4.12) starting in system bus...
  aug 13 17:34:26 george kernel: Bluetooth: BNEP (Ethernet Emulation) ver 1.3
  aug 13 17:34:26 george kernel: Bluetooth: BNEP filters: protocol multicast
  aug 13 17:34:26 george kernel: Bluetooth: BNEP socket layer initialized
  aug 13 17:34:26 george bluetoothd[752]: Bluetooth management interface 1.10 
initialized
  aug 13 17:34:26 george dbus[702]: [system] Activating via systemd: service 
name='org.freedesktop.hostname1' unit='dbus-org.fre
  aug 13 17:34:26 george bluetoothd[752]: Failed to obtain handles for "Service 
Changed" characteristic
  aug 13 17:34:26 george bluetoothd[752]: Not enough free handles to register 
service
  aug 13 17:34:26 george bluetoothd[752]: Error adding Link Loss service
  aug 13 17:34:26 george bluetoothd[752]: Not enough free handles to register 
service
  aug 13 17:34:26 george bluetoothd[752]: Not enough free handles to register 
service
  aug 13 17:34:26 george bluetoothd[752]: Not enough free handles to register 
service
  aug 13 17:34:26 george bluetoothd[752]: Current Time Service could not be 
registered
  aug 13 17:34:26 george bluetoothd[752]: gatt-time-server: Input/output error 
(5)
  aug 13 17:34:26 george bluetoothd[752]: Not enough free handles to register 
service
  aug 13 17:34:26 george bluetoothd[752]: Not enough free handles to register 
service
  aug 13 17:34:26 george bluetoothd[752]: Sap driver initialization failed.
  aug 13 17:34:26 george bluetoothd[752]: sap-server: Operation not permitted 
(1)
  
  aug 13 17:35:00 george dbus[702]: [system] Rejected send message, 2 matched 
rules; type="method_call", sender=":1.22" (uid=100
  aug 13 17:35:14 george sudo[1199]: user : TTY=pts/0 ; PWD=/home/user ; 
USER=root ; COMMAND=/usr/bin/bluetoothctl
  aug 13 17:35:14 george sudo[1199]: pam_unix(sudo:session): session opened for 
user root by user(uid=0)
  aug 13 17:35:23 george systemd[1]: Starting Stop ureadahead data collection...
  aug 13 17:35:23 george systemd[1]: Started Stop ureadahead data collection.
  aug 13 17:35:23 george systemd[1]: Stopped Read required files in advance.
  aug 13 17:43:26 george sudo[1199]: pam_unix(sudo:session): session closed for 
user root
  aug 13 17:47:44 george sshd[1389]: Accepted publickey for user from 
192.168.69.200 port 57812 ssh2: RSA SHA256:MQ3JEM2k/Yw2jzz
  aug 13 17:47:44 george sshd[1389]: pam_unix(sshd:session): session opened for 
user user by (uid=0)
  aug 13 17:47:44 george systemd-logind[742]: New session 2 of user user.
  aug 13 17:47:44 george systemd[1]: Started Session 2 of user user.
  aug 13 17:47:52 george sudo[1431]: user : TTY=pts/1 ; PWD=/home/user ; 
USER=root ; COMMAND=/usr/bin/bluetoothctl
  aug 13 17:47:52 george sudo[1431]: pam_unix(sudo:session): session opened for 
user root by user(uid=0)
  aug 13 17:49:30 george /usr/lib/snapd/snapd[685]: snapmgr.go:422: No snaps to 
auto-refresh found
  aug 13 17:49:30 george systemd[1]: Starting Cleanup of Temporary 
Directories...
  aug 13 17:49:30 george snapd[685]: 2017/08/13 17:49:30.803962 snapmgr.go:422: 
No snaps to auto-refresh found
  aug 13 17:49:30 george systemd-tmpfiles[1459]: 
[/usr/lib/tmpfiles.d/var.conf:14] Duplicate line for path "/var/log", ignoring.
  aug 13 17:49:31 george systemd[1]: Started Cleanup of Temporary Directories.
  aug 13 17:53:16 george sudo[1520]: user : TTY=pts/0 ; PWD=/var/log ; 
USER=root ; COMMAND=/usr/bin/vim -R dmesg
  aug 13 17:53:16 george sudo[1520]: 

[Kernel-packages] [Bug 1710601] [NEW] bluetoothctl fails to connect

[doru001]

Public bug reported:

bluetooth stopped working after some update, probably to bluez5
before it was working flawlessly following 
https://wiki.archlinux.org/index.php/Bluetooth#Configuration_via_the_CLI
now $ bluetoothctl shows no typed characters, $ sudo bluetoothctl works well 
until I try to connect the device:
[bluetooth]# connect A8:7E:33:FC:6D:15
Attempting to connect to A8:7E:33:FC:6D:15
[CHG] Device A8:7E:33:FC:6D:15 Connected: yes
Failed to connect: org.bluez.Error.NotAvailable
[CHG] Device A8:7E:33:FC:6D:15 Connected: no
[CHG] Device A8:7E:33:FC:6D:15 RSSI: -81
[CHG] Device A8:7E:33:FC:6D:15 RSSI: -63
[CHG] Device A8:7E:33:FC:6D:15 RSSI: -73
[CHG] Device A8:7E:33:FC:6D:15 RSSI: -65
[CHG] Device A8:7E:33:FC:6D:15 RSSI: -79
[CHG] Device A8:7E:33:FC:6D:15 RSSI: -61
[CHG] Device A8:7E:33:FC:6D:15 RSSI: -75
[CHG] Device A8:7E:33:FC:6D:15 RSSI: -63

I am using bluez 5.37-0ubuntu5 under Ubuntu 16.04.3 LTS, updated to the
day.

I found errors in logs:
aug 13 17:34:25 george bluetoothd[752]: Starting SDP server
aug 13 17:34:26 george ModemManager[738]:   ModemManager (version 1.4.12) 
starting in system bus...
aug 13 17:34:26 george kernel: Bluetooth: BNEP (Ethernet Emulation) ver 1.3
aug 13 17:34:26 george kernel: Bluetooth: BNEP filters: protocol multicast
aug 13 17:34:26 george kernel: Bluetooth: BNEP socket layer initialized
aug 13 17:34:26 george bluetoothd[752]: Bluetooth management interface 1.10 
initialized
aug 13 17:34:26 george dbus[702]: [system] Activating via systemd: service 
name='org.freedesktop.hostname1' unit='dbus-org.fre
aug 13 17:34:26 george bluetoothd[752]: Failed to obtain handles for "Service 
Changed" characteristic
aug 13 17:34:26 george bluetoothd[752]: Not enough free handles to register 
service
aug 13 17:34:26 george bluetoothd[752]: Error adding Link Loss service
aug 13 17:34:26 george bluetoothd[752]: Not enough free handles to register 
service
aug 13 17:34:26 george bluetoothd[752]: Not enough free handles to register 
service
aug 13 17:34:26 george bluetoothd[752]: Not enough free handles to register 
service
aug 13 17:34:26 george bluetoothd[752]: Current Time Service could not be 
registered
aug 13 17:34:26 george bluetoothd[752]: gatt-time-server: Input/output error (5)
aug 13 17:34:26 george bluetoothd[752]: Not enough free handles to register 
service
aug 13 17:34:26 george bluetoothd[752]: Not enough free handles to register 
service
aug 13 17:34:26 george bluetoothd[752]: Sap driver initialization failed.
aug 13 17:34:26 george bluetoothd[752]: sap-server: Operation not permitted (1)

aug 13 17:35:00 george dbus[702]: [system] Rejected send message, 2 matched 
rules; type="method_call", sender=":1.22" (uid=100
aug 13 17:35:14 george sudo[1199]: user : TTY=pts/0 ; PWD=/home/user ; 
USER=root ; COMMAND=/usr/bin/bluetoothctl
aug 13 17:35:14 george sudo[1199]: pam_unix(sudo:session): session opened for 
user root by user(uid=0)
aug 13 17:35:23 george systemd[1]: Starting Stop ureadahead data collection...
aug 13 17:35:23 george systemd[1]: Started Stop ureadahead data collection.
aug 13 17:35:23 george systemd[1]: Stopped Read required files in advance.
aug 13 17:43:26 george sudo[1199]: pam_unix(sudo:session): session closed for 
user root
aug 13 17:47:44 george sshd[1389]: Accepted publickey for user from 
192.168.69.200 port 57812 ssh2: RSA SHA256:MQ3JEM2k/Yw2jzz
aug 13 17:47:44 george sshd[1389]: pam_unix(sshd:session): session opened for 
user user by (uid=0)
aug 13 17:47:44 george systemd-logind[742]: New session 2 of user user.
aug 13 17:47:44 george systemd[1]: Started Session 2 of user user.
aug 13 17:47:52 george sudo[1431]: user : TTY=pts/1 ; PWD=/home/user ; 
USER=root ; COMMAND=/usr/bin/bluetoothctl
aug 13 17:47:52 george sudo[1431]: pam_unix(sudo:session): session opened for 
user root by user(uid=0)
aug 13 17:49:30 george /usr/lib/snapd/snapd[685]: snapmgr.go:422: No snaps to 
auto-refresh found
aug 13 17:49:30 george systemd[1]: Starting Cleanup of Temporary Directories...
aug 13 17:49:30 george snapd[685]: 2017/08/13 17:49:30.803962 snapmgr.go:422: 
No snaps to auto-refresh found
aug 13 17:49:30 george systemd-tmpfiles[1459]: 
[/usr/lib/tmpfiles.d/var.conf:14] Duplicate line for path "/var/log", ignoring.
aug 13 17:49:31 george systemd[1]: Started Cleanup of Temporary Directories.
aug 13 17:53:16 george sudo[1520]: user : TTY=pts/0 ; PWD=/var/log ; 
USER=root ; COMMAND=/usr/bin/vim -R dmesg
aug 13 17:53:16 george sudo[1520]: pam_unix(sudo:session): session opened for 
user root by user(uid=0)
aug 13 17:53:18 george sudo[1520]: pam_unix(sudo:session): session closed for 
user root

these errors are common, as you can see in comments to this bug report:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1490349

user@george:~$ lsmod | grep bt\\\|blue
btusb  40960  0
btrtl  16384  1 btusb
btbcm  16384  1 btusb
btintel16384  1 btusb
bluetooth 479232  24 

[Kernel-packages] [Bug 1709812] Re: linux: 4.4.0-92.115 -proposed tracker

[Stefan Bader]

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

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

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

Title:
  linux: 4.4.0-92.115 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Invalid
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: 1709813
  derivatives: 1709814,1709815,1709816,1709817
  -- 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/1709812/+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 1709816] Re: linux-aws: 4.4.0-1031.40 -proposed tracker

[Stefan Bader]

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

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

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

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

Title:
  linux-aws: 4.4.0-1031.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:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Invalid
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  Invalid
Status in linux-aws package in Ubuntu:
  Invalid
Status in linux-aws source package in Xenial:
  Confirmed

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1709812
  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/1709816/+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 1709812] Re: linux: 4.4.0-92.115 -proposed tracker

[Stefan Bader]

** Changed in: kernel-sru-workflow/automated-testing
   Status: Incomplete => 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/1709812

Title:
  linux: 4.4.0-92.115 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Invalid
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: 1709813
  derivatives: 1709814,1709815,1709816,1709817
  -- 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/1709812/+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 1696154] Re: [17.10 FEAT] Sign POWER host/NV kernels

[Andy Whitcroft]

Deployment to production seems successful.  I have uploaded a modified
kernel to a PPA and built a signed kernel image from that.  I am
attaching that signed kernel and the public key component of the signing
key for it.  NOTE: this key is _not_ a final official canonical key it
is a key for a PPA and for testing only.

There are two files:

  vmlinux-4.11.0-13-generic.opal.signed -- this is the bootable signed binary
  opal.x509 -- the DER format public key with which this binary is signed

Any testing, review appreciated.  Please report back to this bug.

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

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

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

** Changed in: linux-signed (Ubuntu)
   Importance: Critical => High

** Changed in: linux-signed (Ubuntu)
 Assignee: (unassigned) => Andy Whitcroft (apw)

** Attachment added: "opal.x509"
   
https://bugs.launchpad.net/ubuntu/+source/linux-signed/+bug/1696154/+attachment/4932055/+files/opal.x509

-- 
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/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 1709816] Re: linux-aws: 4.4.0-1031.40 -proposed tracker

[Brad Figg]

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

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

Title:
  linux-aws: 4.4.0-1031.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:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-aws package in Ubuntu:
  Invalid
Status in linux-aws source package in Xenial:
  Confirmed

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1709812
  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/1709816/+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 1708043] Re: Lenovo X1 Carbon Gen5 fails to resume

[Mika Westerberg]

This definitely sounds like a platform/configuration issue rather than a
driver 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/1708043

Title:
  Lenovo X1 Carbon Gen5 fails to resume

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Last week it worked fine, this week however if I open the lid for it
  to resume the power light flashes for a bit, then comes on solid, the
  but screen stays blank and the machine is unresponsive. I have to
  power it off / on again in order to use it. It might be related to the
  APST issue with Samsung NVMe SSDs, I'm not sure.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.11.0-10-generic 4.11.0-10.15
  ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8
  Uname: Linux 4.11.0-10-generic x86_64
  ApportVersion: 2.20.6-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   dean   1652 F...m pulseaudio
   /dev/snd/controlC0:  dean   1652 F pulseaudio
  CurrentDesktop: GNOME
  Date: Tue Aug  1 17:39:20 2017
  HibernationDevice: RESUME=UUID=fb0675d7-391c-4293-a2c5-d283708f1284
  InstallationDate: Installed on 2017-07-23 (9 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170720)
  MachineType: LENOVO 20HRCTO1WW
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.11.0-10-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash 
nvme_core.default_ps_max_latency_us=0 vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.11.0-10-generic N/A
   linux-backports-modules-4.11.0-10-generic  N/A
   linux-firmware 1.167
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/04/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1MET37W (1.22 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20HRCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1MET37W(1.22):bd07/04/2017:svnLENOVO:pn20HRCTO1WW:pvrThinkPadX1Carbon5th:rvnLENOVO:rn20HRCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.name: 20HRCTO1WW
  dmi.product.version: ThinkPad X1 Carbon 5th
  dmi.sys.vendor: LENOVO
  --- 
  ApportVersion: 2.20.6-0ubuntu4
  Architecture: amd64
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 17.10
  InstallationDate: Installed on 2017-07-23 (9 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170720)
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Tags:  artful wayland-session
  Uname: Linux 4.13.0-041300rc3-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1708043/+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 1709626] Re: Kernel Oops - unable to handle kernel paging request; RIP is at free_pipe_info+0x57/0x90

[Erik Hoeschler]

Hey Joseph,

I will test the latest upstream kernel.

I think the problem wasn't there on version: 4.4.0-71-generic. With this
kernel we had another problem which was fixed in 4.4.0-87-generic so we
switched over to this version.

Will update this report in a few days.

Thanks in advance
Erik

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

Title:
  Kernel Oops - unable to handle kernel paging request; RIP is at
  free_pipe_info+0x57/0x90

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hi,

  I'm running a Docker swarm with 5 Nodes. Each node is getting this
  kernel oops pretty frequently, i would say once a day. I'm not able to
  reproduce it effectively but it seem's to happen in case a docker
  stack consisting of approx. 40 containers gets deployed.

  Thanks in advance!

  Description:  Ubuntu 16.04.3 LTS
  Release:  16.04

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-87-generic 4.4.0-87.110
  ProcVersionSignature: Ubuntu 4.4.0-87.110-generic 4.4.73
  Uname: Linux 4.4.0-87-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Aug  9 10:23 seq
   crw-rw 1 root audio 116, 33 Aug  9 10:23 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: [Errno 2] No such file or directory: 'fuser'
  Date: Wed Aug  9 15:31:53 2017
  HibernationDevice: RESUME=/dev/mapper/vg00-lv_swap
  InstallationDate: Installed on 2016-06-01 (434 days ago)
  InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.3)
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  MachineType: VMware, Inc. VMware Virtual Platform
  PciMultimedia:
   
  ProcEnviron:
   LANGUAGE=en_US:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 svgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-87-generic 
root=/dev/mapper/vg00-lv_root ro cgroup_enable=memory swapaccount=1
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-87-generic N/A
   linux-backports-modules-4.4.0-87-generic  N/A
   linux-firmware1.157.11
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/21/2015
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: 6.00
  dmi.board.name: 440BX Desktop Reference Platform
  dmi.board.vendor: Intel Corporation
  dmi.board.version: None
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 1
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd09/21/2015:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
  dmi.product.name: VMware Virtual Platform
  dmi.product.version: None
  dmi.sys.vendor: VMware, Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1709626/+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 1454903] Re: Btrfs Fails to Mount Drive - btrfs-transaction blocked for more than 120 seconds.

[Daniel]

@Alexej Do you have more information about the fix? Which version?
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/1454903

Title:
  Btrfs Fails to Mount Drive - btrfs-transaction blocked for more than
  120 seconds.

Status in linux package in Ubuntu:
  Fix Released

Bug description:
  Call Trace:
  kernel:  880408609800 8803e9cba200 8803d06f7398 8803bc89fe00
  kernel:  00014200 88040ce9f5c0 880407f9d850 8803bc89fdd8
  kernel:  8803bc89fdc8 880407f9d850 00014200 8803bc89ffd8
  kernel: btrfs-transacti D 8803bc89fdc8 0  4187  2 0x
  kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this 
message.
  kernel:   Not tainted 3.19.0-16-generic #16-Ubuntu
  kernel: INFO: task btrfs-transacti:4187 blocked for more than 120 seconds.
  kernel:  [] system_call_fastpath+0x16/0x1b
  kernel:  [] SyS_mount+0x8b/0xd0
  kernel:  [] do_mount+0x204/0xb20
  kernel:  [] vfs_kern_mount+0x6b/0x120
  kernel:  [] ? __alloc_percpu+0x15/0x20
  kernel:  [] mount_fs+0x38/0x1c0
  kernel:  [] btrfs_mount+0x850/0x920 [btrfs]
  kernel:  [] open_ctree+0x1813/0x2090 [btrfs]
  kernel:  [] ? replay_one_extent+0x6b0/0x6b0 [btrfs]
  kernel:  [] btrfs_recover_log_trees+0x1d4/0x470 [btrfs]
  kernel:  [] walk_log_tree+0xbb/0x1a0 [btrfs]
  kernel:  [] walk_down_log_tree+0x1d9/0x420 [btrfs]
  kernel:  [] ? alloc_extent_buffer+0x34/0x350 [btrfs]
  kernel:  [] insert_orphan_item+0x5e/0x90 [btrfs]

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: linux-image-3.19.0-16-generic 3.19.0-16.16
  ProcVersionSignature: Ubuntu 3.19.0-16.16-generic 3.19.3
  Uname: Linux 3.19.0-16-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jdfalk 3444 F pulseaudio
  Date: Wed May 13 19:03:10 2015
  HibernationDevice: RESUME=/dev/mapper/sda5_crypt
  InstallationDate: Installed on 2015-05-10 (4 days ago)
  InstallationMedia: Ubuntu-Server 15.04 "Vivid Vervet" - Release amd64 
(20150422)
  MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-16-generic.efi.signed 
root=UUID=51a981ad-aeb0-4bd7-91c6-2d493155c812 ro rootflags=subvol=@ 
crashkernel=384M-:128M
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-3.19.0-16-generic N/A
   linux-backports-modules-3.19.0-16-generic  N/A
   linux-firmware 1.143
  RfKill:
   
  SourcePackage: linux
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/06/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F18i
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z77X-D3H
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF18i:bd01/06/2014:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ77X-D3H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  --- 
  ApportVersion: 2.17.2-0ubuntu1
  Architecture: amd64
  DistroRelease: Ubuntu 15.04
  InstallationDate: Installed on 2015-05-10 (5 days ago)
  InstallationMedia: Ubuntu-Server 15.04 "Vivid Vervet" - Release amd64 
(20150422)
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Tags:  vivid
  Uname: Linux 4.1.0-040100rc3-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1454903/+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 1680904] Re: zesty unable to handle kernel NULL pointer dereference

[Sam Stenvall]

Can someone comment here once a fix for the HWE kernel in Ubuntu 16.04
is available? I'm currently using one of the custom builds from earlier
in this thread but I haven't yet been able to confirm whether it fixes
the issue or not.

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

Title:
  zesty unable to handle kernel NULL pointer dereference

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  In Progress
Status in linux-hwe package in Ubuntu:
  Confirmed
Status in linux source package in Zesty:
  Fix Committed
Status in linux-hwe source package in Zesty:
  Confirmed

Bug description:
  Upgraded to zesty about a week ago. Ran into this on latest kernel.
  (during high load, nothing in particular seems to cause it to happen).

  Did not happen with previous (4.10.0.14.16) kernel. Only after update
  to 4.10.0.15.17, has happened about 3 times since then (or other
  crashes), this is the one I could capture.

  kern.log entries below. Let me know if you need anything else from me.

  Thanks!

  
  Apr  7 11:20:28 doe kernel: [26003.796278] BUG: unable to handle kernel NULL 
pointer dereference at 0018
  Apr  7 11:20:28 doe kernel: [26003.796375] IP: 
gen8_ppgtt_alloc_page_directories.isra.38+0x115/0x250 [i915]
  Apr  7 11:20:28 doe kernel: [26003.796404] PGD 0
  Apr  7 11:20:28 doe kernel: [26003.796405]
  Apr  7 11:20:28 doe kernel: [26003.796427] Oops: 0002 [#1] SMP
  Apr  7 11:20:28 doe kernel: [26003.796441] Modules linked in: xt_REDIRECT 
nf_nat_redirect xt_hl scsi_transport_iscsi binfmt_misc veth ip6table_nat 
nf_conntrack_ipv6 nf_defrag_ipv6 nf_nat_ipv6 ip6table_filter ip6_tables 
ipt_MASQUERADE nf_nat_masquerade_ipv4 xt_CHECKSUM xt_comment xt_tcpudp 
iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack 
libcrc32c iptable_mangle iptable_filter ccm rfcomm bridge stp llc cmac bnep 
zfs(PO) zunicode(PO) zavl(PO) zcommon(PO) znvpair(PO) spl(O) nls_iso8859_1 
hid_multitouch joydev i2c_designware_platform i2c_designware_core 
snd_hda_codec_hdmi snd_soc_skl snd_soc_skl_ipc snd_soc_sst_ipc snd_soc_sst_dsp 
snd_hda_codec_realtek snd_hda_ext_core snd_soc_sst_match snd_hda_codec_generic 
snd_soc_core snd_compress ac97_bus snd_pcm_dmaengine snd_hda_intel 
snd_hda_codec snd_hda_core asus_nb_wmi
  Apr  7 11:20:28 doe kernel: [26003.796722]  snd_hwdep asus_wmi sparse_keymap 
snd_pcm arc4 snd_seq_midi snd_seq_midi_event snd_rawmidi snd_seq snd_seq_device 
iwlmvm snd_timer mac80211 intel_rapl x86_pkg_temp_thermal snd intel_powerclamp 
uvcvideo coretemp kvm_intel iwlwifi videobuf2_vmalloc kvm videobuf2_memops 
irqbypass videobuf2_v4l2 intel_cstate videobuf2_core intel_rapl_perf cfg80211 
videodev input_leds serio_raw media shpchp soundcore btusb btrtl hci_uart btbcm 
elan_i2c btqca btintel acpi_als int3403_thermal bluetooth kfifo_buf 
industrialio mac_hid idma64 mei_me virt_dma intel_pch_thermal acpi_pad 
int3400_thermal intel_lpss_pci int3402_thermal mei intel_lpss_acpi 
acpi_thermal_rel processor_thermal_device intel_lpss tpm_crb 
int340x_thermal_zone int3406_thermal intel_soc_dts_iosf asus_wireless 
parport_pc ppdev lp parport ip_tables
  Apr  7 11:20:28 doe kernel: [26003.797026]  x_tables autofs4 algif_skcipher 
af_alg dm_crypt crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc i915 
aesni_intel aes_x86_64 crypto_simd glue_helper cryptd i2c_algo_bit 
drm_kms_helper syscopyarea sysfillrect ahci sysimgblt libahci fb_sys_fops drm 
wmi i2c_hid hid pinctrl_sunrisepoint video pinctrl_intel fjes
  Apr  7 11:20:28 doe kernel: [26003.797142] CPU: 0 PID: 8418 Comm: 
chromium-browse Tainted: P   O4.10.0-15-generic #17-Ubuntu
  Apr  7 11:20:28 doe kernel: [26003.797175] Hardware name: ASUSTeK COMPUTER 
INC. UX305CA/UX305CA, BIOS UX305CA.201 09/11/2015
  Apr  7 11:20:28 doe kernel: [26003.797206] task: 9bbaa201dc00 task.stack: 
c25b5ea8c000
  Apr  7 11:20:28 doe kernel: [26003.797250] RIP: 
0010:gen8_ppgtt_alloc_page_directories.isra.38+0x115/0x250 [i915]
  Apr  7 11:20:28 doe kernel: [26003.797279] RSP: 0018:c25b5ea8f880 EFLAGS: 
00010246
  Apr  7 11:20:28 doe kernel: [26003.797299] RAX: 9bba689be580 RBX: 
0003 RCX: 0003
  Apr  7 11:20:28 doe kernel: [26003.797325] RDX:  RSI: 
9bbae7c0a000 RDI: 9bbba0418000
  Apr  7 11:20:28 doe kernel: [26003.797351] RBP: c25b5ea8f8d8 R08: 
 R09: 
  Apr  7 11:20:28 doe kernel: [26003.797378] R10:  R11: 
0041 R12: 9bbb5f00a000
  Apr  7 11:20:28 doe kernel: [26003.797405] R13: 9bbba932bb10 R14: 
fff97000 R15: 8000
  Apr  7 11:20:28 doe kernel: [26003.797440] FS:  7f70bd1df6c0() 
GS:93c0() knlGS:
  Apr  7 11:20:28 doe kernel: [26003.797470] CS:  0010 DS:  ES:  CR0: 
80050033
  Apr  7 11:20:28 doe kernel: 

[Kernel-packages] [Bug 1681904] Re: WLan not working after Kernel update (HWE)

[davidak]

Maybe there was "no space left on device" on /boot once, but i don't
know exactly.

My workaround is to use a Dell device now to be able to work.

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

Title:
  WLan not working after Kernel update (HWE)

Status in bcmwl package in Ubuntu:
  New
Status in linux package in Ubuntu:
  In Progress

Bug description:
  After the update from 4.8.0.44 to newer versions, wifi stopped
  working.

  The controller is still found with `lshw -class network`, but wifi is
  not displayed in Network Manager.

  Hardware is Broadcom BCM4331 802.11a/b/g/n.

  What additional informations do you need to resolve this?

  -

  Apple MacBookPro10,2 from ~2012
  elementary OS 0.4 Loki (based on Ubuntu 16.04 LTS) with HWE-Stack
  --- 
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  davidak2186 F pulseaudio
  DistroRelease: elementary 0.4
  HibernationDevice: RESUME=UUID=f8624e3d-378a-4777-8889-1f2f01f83989
  InstallationDate: Installed on 2016-10-26 (188 days ago)
  InstallationMedia: elementary OS 0.4 "Loki" - Stable amd64 (20160909)
  IwConfig:
   ens9  no wireless extensions.
   
   docker0   no wireless extensions.
   
   lono wireless extensions.
  MachineType: Apple Inc. MacBookPro10,2
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-20-generic 
root=/dev/mapper/elementary--vg-root ro splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-20-generic N/A
   linux-backports-modules-4.10.0-20-generic  N/A
   linux-firmware 1.157.8
  RfKill:
   0: hci0: Bluetooth
Soft blocked: yes
Hard blocked: no
  Tags:  loki loki
  Uname: Linux 4.10.0-20-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: docker
  _MarkForUpload: True
  dmi.bios.date: 09/13/2015
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MBP102.88Z.0106.B0A.1509130955
  dmi.board.asset.tag: Base Board Asset Tag#
  dmi.board.name: Mac-AFD8A9D944EA4843
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookPro10,2
  dmi.chassis.type: 10
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-AFD8A9D944EA4843
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMBP102.88Z.0106.B0A.1509130955:bd09/13/2015:svnAppleInc.:pnMacBookPro10,2:pvr1.0:rvnAppleInc.:rnMac-AFD8A9D944EA4843:rvrMacBookPro10,2:cvnAppleInc.:ct10:cvrMac-AFD8A9D944EA4843:
  dmi.product.name: MacBookPro10,2
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1681904/+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 1699845] Re: System not booting after kernel upgrade to 4.10.0-22, problem persists with 4.10.0-23

[Pierpaolo Pilla]

Update after only a day: again system not booting with new kernel
4.10.17-041017...  I'm back to booting with 4.10.0-21.

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

Title:
  System not booting after kernel upgrade to 4.10.0-22, problem persists
  with 4.10.0-23

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I am on Ubuntu Studio Zesty (17.04).

  Since upgrade to Linux 4.10.0-22 system boot freezes, only way out is
  hard shutdown.  I am currently booting from 4.10.0-21.

  I can provide journalctl -b1 (where previous boot is with faulty
  kernel) on request.

  Thank you

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: ubuntu-release-upgrader-core 1:17.04.8
  ProcVersionSignature: Ubuntu 4.10.0-21.23-lowlatency 4.10.11
  Uname: Linux 4.10.0-21-lowlatency x86_64
  ApportVersion: 2.20.4-0ubuntu4.1
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: XFCE
  Date: Thu Jun 22 17:46:53 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-03-21 (92 days ago)
  InstallationMedia: Ubuntu-Studio 16.10 "Yakkety Yak" - Release amd64 
(20161012.1)
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=it_IT
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubuntu-release-upgrader
  Symptom: release-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)
  VarLogDistupgradeAptlog:
   Log time: 2017-06-06 21:25:15.195734
   Starting pkgProblemResolver with broken count: 0
   Starting 2 pkgProblemResolver with broken count: 0
   Done

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1699845/+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 1708480] Missing required logs.

[Ubuntu Kernel Bot]

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

apport-collect 1708480

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

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

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

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

** Tags added: zesty

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

Title:
  Ubuntu 17.04/17.10 Screen Tearing on Intel KabyLake Graphics Cards

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Upon upgrading to 17.04 (also confirmed in 17.10), heavy, almost
  constant screen tearing presents itself immediately at the graphical
  or text splash page (i.e., before the operating system loads).  The
  tearing continues after reaching the lock screen and logging in.  The
  tearing is nearly constant, stopping only for certain actions like
  using the mouse or typing.

  The screen tearing can be "fixed" by issuing i915.enable_rc6=0 in the
  boot parameter.  However, this is a false fix as it turns off
  important power management functions and, as a consequence, the fan
  runs constantly and on high.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1708480/+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 1708480] Re: Ubuntu 17.04/17.10 Screen Tearing on Intel KabyLake Graphics Cards

[Timo Aaltonen]

** Package changed: xserver-xorg-video-intel (Ubuntu) => linux (Ubuntu)

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

Title:
  Ubuntu 17.04/17.10 Screen Tearing on Intel KabyLake Graphics Cards

Status in linux package in Ubuntu:
  New

Bug description:
  Upon upgrading to 17.04 (also confirmed in 17.10), heavy, almost
  constant screen tearing presents itself immediately at the graphical
  or text splash page (i.e., before the operating system loads).  The
  tearing continues after reaching the lock screen and logging in.  The
  tearing is nearly constant, stopping only for certain actions like
  using the mouse or typing.

  The screen tearing can be "fixed" by issuing i915.enable_rc6=0 in the
  boot parameter.  However, this is a false fix as it turns off
  important power management functions and, as a consequence, the fan
  runs constantly and on high.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1708480/+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 1708480] [NEW] Ubuntu 17.04/17.10 Screen Tearing on Intel KabyLake Graphics Cards

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

Upon upgrading to 17.04 (also confirmed in 17.10), heavy, almost
constant screen tearing presents itself immediately at the graphical or
text splash page (i.e., before the operating system loads).  The tearing
continues after reaching the lock screen and logging in.  The tearing is
nearly constant, stopping only for certain actions like using the mouse
or typing.

The screen tearing can be "fixed" by issuing i915.enable_rc6=0 in the
boot parameter.  However, this is a false fix as it turns off important
power management functions and, as a consequence, the fan runs
constantly and on high.

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


** Tags: bot-comment intel
-- 
Ubuntu 17.04/17.10 Screen Tearing on Intel KabyLake Graphics Cards
https://bugs.launchpad.net/bugs/1708480
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to linux in Ubuntu.

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

[Kernel-packages] [Bug 1707887] Re: Failed to build libhugetlbfs-2.20 from source on 4.4 / 3.13 Trusty ARM64

[Po-Hsu Lin]

** Tags added: bot-stop-nagging

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

Title:
  Failed to build libhugetlbfs-2.20 from source on 4.4 / 3.13 Trusty
  ARM64

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  It will fail to build libhugetlbfs verison 2.20 for SRU regression-
  test on 3.13 ARM64

  It's ok on 4.10 / 4.4 ARM64, but not 4.4.0-88.111~14.04.1 and
  3.13.0-126.175 ARM64

  Looks like it's failing with:
  LD64 (hugelink_rw test) obj64/linkhuge_rw
  /usr/bin/ld: final link failed: File truncated

  This is not a regression. As this issue has been seen before.

  Complete make log:
  $ make
 VERSION
  version string: 2.20
 CC64 obj64/elflink.o
 AS64 obj64/sys-aarch64elf.o
 CC64 obj64/hugeutils.o
 CC64 obj64/version.o
 CC64 obj64/init.o
 CC64 obj64/morecore.o
 CC64 obj64/debug.o
 CC64 obj64/alloc.o
 CC64 obj64/shm.o
 CC64 obj64/kernel-features.o
 LD64 (shared) obj64/libhugetlbfs.so
 AR64 obj64/libhugetlbfs.a
 CC64 obj64/init_privutils.o
 LD64 (shared) obj64/libhugetlbfs_privutils.so
 CCHOST obj/init_privutils.o
 CCHOST obj/debug.o
 CCHOST obj/hugeutils.o
 CCHOST obj/kernel-features.o
 ARHOST obj/libhugetlbfs_privutils.a
 CC64 obj64/gethugepagesize.o
 CC64 obj64/testutils.o
 CC64 obj64/libtestutils.o
 LD64 (lib test) obj64/gethugepagesize
 CC64 obj64/test_root.o
 LD64 (lib test) obj64/test_root
 CC64 obj64/find_path.o
 LD64 (lib test) obj64/find_path
 CC64 obj64/unlinked_fd.o
 LD64 (lib test) obj64/unlinked_fd
 CC64 obj64/misalign.o
 LD64 (lib test) obj64/misalign
 CC64 obj64/readback.o
 LD64 (lib test) obj64/readback
 CC64 obj64/truncate.o
 LD64 (lib test) obj64/truncate
 CC64 obj64/shared.o
 LD64 (lib test) obj64/shared
 CC64 obj64/private.o
 LD64 (lib test) obj64/private
 CC64 obj64/fork-cow.o
 LD64 (lib test) obj64/fork-cow
 CC64 obj64/empty_mounts.o
 LD64 (lib test) obj64/empty_mounts
 CC64 obj64/large_mounts.o
 LD64 (lib test) obj64/large_mounts
 CC64 obj64/meminfo_nohuge.o
 LD64 (lib test) obj64/meminfo_nohuge
 CC64 obj64/ptrace-write-hugepage.o
 LD64 (lib test) obj64/ptrace-write-hugepage
 CC64 obj64/icache-hygiene.o
  icache-hygiene.c: In function ‘test_once’:
  icache-hygiene.c:158:11: warning: ignoring return value of ‘ftruncate’, 
declared with attribute warn_unused_result [-Wunused-result]
ftruncate(fd, 0);
 ^
  icache-hygiene.c:162:12: warning: ignoring return value of ‘ftruncate’, 
declared with attribute warn_unused_result [-Wunused-result]
 ftruncate(fd, 0);
  ^
  icache-hygiene.c:171:11: warning: ignoring return value of ‘ftruncate’, 
declared with attribute warn_unused_result [-Wunused-result]
ftruncate(fd, hpage_size);
 ^
  icache-hygiene.c:177:11: warning: ignoring return value of ‘ftruncate’, 
declared with attribute warn_unused_result [-Wunused-result]
ftruncate(fd, 0);
 ^
 LD64 (lib test) obj64/icache-hygiene
 CC64 obj64/slbpacaflush.o
 LD64 (lib test) obj64/slbpacaflush
 CC64 obj64/chunk-overcommit.o
 LD64 (lib test) obj64/chunk-overcommit
 CC64 obj64/mprotect.o
 LD64 (lib test) obj64/mprotect
 CC64 obj64/alloc-instantiate-race.o
  alloc-instantiate-race.c: In function ‘thread_racer’:
  alloc-instantiate-race.c:114:6: warning: variable ‘rc’ set but not used 
[-Wunused-but-set-variable]
int rc;
^
 LD64 (lib test) obj64/alloc-instantiate-race
 CC64 obj64/mlock.o
 LD64 (lib test) obj64/mlock
 CC64 obj64/truncate_reserve_wraparound.o
 LD64 (lib test) obj64/truncate_reserve_wraparound
 CC64 obj64/truncate_sigbus_versus_oom.o
 LD64 (lib test) obj64/truncate_sigbus_versus_oom
 CC64 obj64/map_high_truncate_2.o
 LD64 (lib test) obj64/map_high_truncate_2
 CC64 obj64/truncate_above_4GB.o
 LD64 (lib test) obj64/truncate_above_4GB
 CC64 obj64/direct.o
 LD64 (lib test) obj64/direct
 CC64 obj64/misaligned_offset.o
 LD64 (lib test) obj64/misaligned_offset
 CC64 obj64/brk_near_huge.o
 LD64 (lib test) obj64/brk_near_huge
 CC64 obj64/task-size-overrun.o
 LD64 (lib test) obj64/task-size-overrun
 CC64 obj64/stack_grow_into_huge.o
 LD64 (lib test) obj64/stack_grow_into_huge
 CC64 obj64/counters.o
 LD64 (lib test) obj64/counters
 CC64 obj64/quota.o
 LD64 (lib test) obj64/quota
 CC64 obj64/heap-overflow.o
 

[Kernel-packages] [Bug 1708495] Re: usb 3-1: Warning! Unlikely big volume range (=10361), cval->res is probably wrong.

[Kai-Heng Feng]

Does volume work?

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

Title:
  usb 3-1: Warning! Unlikely big volume range (=10361), cval->res is
  probably wrong.

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hello,

  dmesg:
  [   51.235163] input: Plantronics Plantronics C310 as 
/devices/pci:00/:00:14.0/usb3/3-1/3-1:1.3/0003:047F:C022.0002/input/input12
  [   51.242659] usb 3-1: Warning! Unlikely big volume range (=10361), 
cval->res is probably wrong.
  [   51.242666] usb 3-1: [11] FU [Sidetone Playback Volume] ch = 1, val = 
0/10361/1
  [   51.247916] usbcore: registered new interface driver snd-usb-audio
  [   51.294684] plantronics 0003:047F:C022.0002: input,hiddev0,hidraw1: USB 
HID v1.11 Device [Plantronics Plantronics C310] on usb-:00:14.0-1/input3

  Regards,
  --
  Cristian

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.11.0-10-generic 4.11.0-10.15
  ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8
  Uname: Linux 4.11.0-10-generic x86_64
  ApportVersion: 2.20.6-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  caravena   1452 F pulseaudio
   /dev/snd/controlC0:  caravena   1452 F pulseaudio
  CurrentDesktop: GNOME
  Date: Thu Aug  3 13:16:37 2017
  HibernationDevice: RESUME=UUID=360bd2d2-4f44-4311-86d6-4781ac81ee87
  InstallationDate: Installed on 2017-07-05 (28 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.11.0-10-generic 
root=UUID=6b614287-8ce5-49c5-b66d-e92fa9568c2b ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.11.0-10-generic N/A
   linux-backports-modules-4.11.0-10-generic  N/A
   linux-firmware 1.167
  SourcePackage: linux
  UpgradeStatus: Upgraded to artful on 2017-07-05 (28 days ago)
  dmi.bios.date: 04/15/2013
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: P14AAJ
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: SAMSUNG_NP1234567890
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: FAB1
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvrP14AAJ:bd04/15/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1:
  dmi.product.name: 530U3C/530U4C
  dmi.product.version: 0.1
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1708495/+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 1707395] Re: Synaptics touchpad does not work at all

[Kai-Heng Feng]

Can you try mainline kernel 4.11, 4.12?

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

Title:
  Synaptics touchpad does not work at all

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  My synaptics touchpad is not working because it is not being detected.
  It happens since I upgraded to Ubuntu 17.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-28-generic 4.10.0-28.32
  ProcVersionSignature: Ubuntu 4.10.0-28.32-generic 4.10.17
  Uname: Linux 4.10.0-28-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC1D0p:   saguti 8628 F...m pulseaudio
   /dev/snd/controlC1:  saguti 8628 F pulseaudio
   /dev/snd/controlC0:  saguti 8628 F pulseaudio
  CurrentDesktop: GNOME
  Date: Sat Jul 29 08:25:15 2017
  HibernationDevice: RESUME=UUID=dece2035-1a42-4d1e-8304-9f2e23921132
  InstallationDate: Installed on 2016-07-24 (369 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  MachineType: Acer Aspire V3-472G
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-28-generic.efi.signed 
root=UUID=c4a143c7-b490-423a-9645-ff2ffe57a345 ro quiet splash 
intel_pstate=disable "acp_osi=!Windows 2013" vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-28-generic N/A
   linux-backports-modules-4.10.0-28-generic  N/A
   linux-firmware 1.164.1
  SourcePackage: linux
  UpgradeStatus: Upgraded to zesty on 2017-07-29 (0 days ago)
  dmi.bios.date: 09/24/2014
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.21
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: EA40_HB
  dmi.board.vendor: Acer
  dmi.board.version: Type2 - A01 Board Version
  dmi.chassis.type: 10
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.21:bd09/24/2014:svnAcer:pnAspireV3-472G:pvrTBDbyOEM:rvnAcer:rnEA40_HB:rvrType2-A01BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion:
  dmi.product.name: Aspire V3-472G
  dmi.product.version: TBD by OEM
  dmi.sys.vendor: Acer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1707395/+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 1584557] Re: Seagate external drive causes SCSI bus resets when UAS enabled

[Kai-Heng Feng]

wdeurholt,

Do you mean "options usb-storage quirks=07ab:fca1:u" can solve the
issue?

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

Title:
  Seagate external drive causes SCSI bus resets when UAS enabled

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Seagate STEA1000400 external USB hard disk (USB ID 0bc2:2322) causes
  continuous SCSI bus resets by default. As a workaround, disabling UAS
  causes the device to work fine.

  To disable UAS, I created a file in /etc/modprobe.d with the following 
contents:
  options usb-storage quirks=0bc2:02322:u

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: ubuntu-release-upgrader-core 1:16.04.14
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CrashDB: ubuntu
  Date: Sun May 22 22:02:26 2016
  InstallationDate: Installed on 2012-10-07 (1323 days ago)
  InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 
(20120822.4)
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubuntu-release-upgrader
  Symptom: ubuntu-release-upgrader
  UpgradeStatus: Upgraded to xenial on 2016-04-09 (43 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1584557/+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 1709294] Re: linux: 3.19.0-92.100 -proposed tracker

[Po-Hsu Lin]

Vivid image is not available on MaaS.

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

Title:
  linux: 3.19.0-92.100 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
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:
  Confirmed
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:
  Invalid
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Vivid:
  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: 1709295
  derivatives:
  kernel-stable-phase-changed:Friday, 11. August 2017 12:02 UTC
  kernel-stable-phase:Uploaded

  -- swm properties --
  boot-testing-requested: true
  phase: Uploaded

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1709294/+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 801993] Re: package firmware-b43-lpphy-installer 1:014-3ubuntu1 failed to install/upgrade: ErrorMessage: subprocess installed post-installation script returned error exit status

[William Grant]

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

** Attachment removed: "D123CE840C1398C81B746C0862089076.jpg"
   
https://bugs.launchpad.net/ubuntu/+source/b43-fwcutter/+bug/801993/+attachment/4908517/+files/D123CE840C1398C81B746C0862089076.jpg

** Attachment removed: "E04F2AA3C016138E.jpg"
   
https://bugs.launchpad.net/ubuntu/+source/b43-fwcutter/+bug/801993/+attachment/4928023/+files/E04F2AA3C016138E.jpg

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

Title:
  package firmware-b43-lpphy-installer 1:014-3ubuntu1 failed to
  install/upgrade: ErrorMessage: subprocess installed post-installation
  script returned error exit status 1

Status in b43-fwcutter package in Ubuntu:
  Confirmed

Bug description:
  when upgrading to 11.10 beta from 10.04

  ProblemType: Package
  DistroRelease: Ubuntu 11.10
  Package: firmware-b43-lpphy-installer 1:014-3ubuntu1
  ProcVersionSignature: Ubuntu 2.6.38-10.44-generic 2.6.38.7
  Uname: Linux 2.6.38-10-generic i686
  Architecture: i386
  Date: Sun Jun 26 00:32:41 2011
  ErrorMessage: ErrorMessage: subprocess installed post-installation script 
returned error exit status 1
  InstallationMedia: Ubuntu 10.04.2 LTS "Lucid Lynx" - Release i386 (20110211.1)
  PackageArchitecture: all
  SourcePackage: b43-fwcutter
  Title: package firmware-b43-lpphy-installer 1:014-3ubuntu1 failed to 
install/upgrade: ErrorMessage: subprocess installed post-installation script 
returned error exit status 1
  UpgradeStatus: Upgraded to oneiric on 2011-06-25 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/b43-fwcutter/+bug/801993/+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 1681904] Re: WLan not working after Kernel update (HWE)

[Kai-Heng Feng]

No idea why the header package is not installed - it should be
automatically pulled by meta package.

I guess something went wrong in the upgrade process?

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

Title:
  WLan not working after Kernel update (HWE)

Status in bcmwl package in Ubuntu:
  New
Status in linux package in Ubuntu:
  In Progress

Bug description:
  After the update from 4.8.0.44 to newer versions, wifi stopped
  working.

  The controller is still found with `lshw -class network`, but wifi is
  not displayed in Network Manager.

  Hardware is Broadcom BCM4331 802.11a/b/g/n.

  What additional informations do you need to resolve this?

  -

  Apple MacBookPro10,2 from ~2012
  elementary OS 0.4 Loki (based on Ubuntu 16.04 LTS) with HWE-Stack
  --- 
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  davidak2186 F pulseaudio
  DistroRelease: elementary 0.4
  HibernationDevice: RESUME=UUID=f8624e3d-378a-4777-8889-1f2f01f83989
  InstallationDate: Installed on 2016-10-26 (188 days ago)
  InstallationMedia: elementary OS 0.4 "Loki" - Stable amd64 (20160909)
  IwConfig:
   ens9  no wireless extensions.
   
   docker0   no wireless extensions.
   
   lono wireless extensions.
  MachineType: Apple Inc. MacBookPro10,2
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-20-generic 
root=/dev/mapper/elementary--vg-root ro splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-20-generic N/A
   linux-backports-modules-4.10.0-20-generic  N/A
   linux-firmware 1.157.8
  RfKill:
   0: hci0: Bluetooth
Soft blocked: yes
Hard blocked: no
  Tags:  loki loki
  Uname: Linux 4.10.0-20-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: docker
  _MarkForUpload: True
  dmi.bios.date: 09/13/2015
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MBP102.88Z.0106.B0A.1509130955
  dmi.board.asset.tag: Base Board Asset Tag#
  dmi.board.name: Mac-AFD8A9D944EA4843
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookPro10,2
  dmi.chassis.type: 10
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-AFD8A9D944EA4843
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMBP102.88Z.0106.B0A.1509130955:bd09/13/2015:svnAppleInc.:pnMacBookPro10,2:pvr1.0:rvnAppleInc.:rnMac-AFD8A9D944EA4843:rvrMacBookPro10,2:cvnAppleInc.:ct10:cvrMac-AFD8A9D944EA4843:
  dmi.product.name: MacBookPro10,2
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1681904/+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 1710501] Re: can't open synaptic package manager

[kevinek]

Have not been able to yet as I am away from home and that computer till
tomorrow. Will do then let you know

Sent from my Windows 10 phone

From: Po-Hsu Lin
Sent: 14 August 2017 03:30
To: ke...@tesco.net
Subject: [Bug 1710501] Re: can't open synaptic package manager

Did you try to change your repository setting before this?

Can you paste the log of the following command:

sudo apt-get update
sudo apt-get dist-upgrade -y

Thanks

-- 
You received this bug notification because you are subscribed to the bug
report.
https://bugs.launchpad.net/bugs/1710501

Title:
  can't open synaptic package manager

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

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

Title:
  can't open synaptic package manager

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  When I try and open synaptic package man. I get this message.
  E: The package linux-image-4.10.0-23-generic needs to be reinstalled, but I 
can't find an archive for it.
  E: Internal error opening cache (1). Please report.

  Before this the software updater is showing 1 update but does not
  update it, I click on install and it says installing a few moments but
  then returns to showing one update to be done?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1710501/+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 839157] Re: Bluetooth applet (OBEX send/browse) does not work since Natty (after bluetoothd 4.84 exactly)

[William Grant]

** Attachment removed: "13882650E77CD1D8.jpg"
   
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/839157/+attachment/4924174/+files/13882650E77CD1D8.jpg

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

Title:
  Bluetooth applet (OBEX send/browse) does not work since Natty (after
  bluetoothd 4.84 exactly)

Status in bluez package in Ubuntu:
  Expired
Status in gnome-bluetooth package in Ubuntu:
  Invalid

Bug description:
  I have Ubuntu Natty 11.04 and a Nokia N81 (Symbian S60v3.1). In Ubuntu
  10.04 (Lucid) and 10.10 (Maverick) bluetooth file transfers do work
  fast and stable on my hardware. Since Natty it stopped working all
  together!

  UPDATE 26-2-2012: everything works again if the executable
  /usr/sbin/bluetoothd (4.91 in Natty) is replaced with 4.84 or earlier.
  I verified this workaround on several machines and with the Live-CD of
  Natty. Precise alpha 2 is affected too. (see also my comment 30 below)

  The attachment shows  the output of "sudo hcidump -XYt" when browsing
  fails (bluetooth-applet - menu -  - Browse files...)

  Running " bluetooth-applet -d" in a terminal and trying to browse and send 
files shows this:
  ** Message: adding killswitch idx 1 state KILLSWITCH_STATE_UNBLOCKED
  ** Message: adding killswitch idx 4 state KILLSWITCH_STATE_UNBLOCKED
  ** Message: killswitch 1 is KILLSWITCH_STATE_UNBLOCKED
  ** Message: killswitch 4 is KILLSWITCH_STATE_UNBLOCKED
  ** Message: killswitches state KILLSWITCH_STATE_UNBLOCKED
  ** (bluetooth-applet:4108): DEBUG: Unhandled UUID 
111b--1000-8000-00805f9b34fb (0x111b)
  ** (bluetooth-applet:4108): DEBUG: Unhandled UUID 
5005--1000-8000-0002ee01 (0x5005)
  ** (bluetooth-applet:4108): DEBUG: Unhandled UUID 
5601--1000-8000-0002ee01 (0x5601)
  ** Message: killswitch 1 is KILLSWITCH_STATE_UNBLOCKED
  ** Message: killswitch 4 is KILLSWITCH_STATE_UNBLOCKED
  ** Message: killswitches state KILLSWITCH_STATE_UNBLOCKED
  ** (bluetooth-sendto:4120): DEBUG: Unhandled UUID 
111b--1000-8000-00805f9b34fb (0x111b)
  ** (bluetooth-sendto:4120): DEBUG: Unhandled UUID 
5005--1000-8000-0002ee01 (0x5005)
  ** (bluetooth-sendto:4120): DEBUG: Unhandled UUID 
5601--1000-8000-0002ee01 (0x5601)

  And I saw interesting lines in /var/log/auth.log:
  oliverhp dbus-daemon: [system] Rejected send message, 2 matched rules; 
type="method_return", sender=":1.99" (uid=0 pid=3356 comm="/usr/sbin/bluetoothd 
--udev ") interface="(unset)" member="(unset)" error name="(unset)" 
requested_reply=0 destination=":1.139" (uid=1000 pid=3768 
comm="bluetooth-applet -d "))

  ProblemType: Bug
  DistroRelease: Ubuntu 11.04
  Package: bluez 4.91-0ubuntu1
  ProcVersionSignature: Ubuntu 2.6.38-11.48-generic 2.6.38.8
  Uname: Linux 2.6.38-11-generic i686
  Architecture: i386
  Date: Fri Sep  2 00:10:38 2011
  EcryptfsInUse: Yes
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427)
  InterestingModules: rfcomm sco bnep l2cap btusb bluetooth
  MachineType: Hewlett-Packard HP Compaq nx8220 (PY517EA#ABD)
  PccardctlIdent:
   Socket 0:
     no product info available
  PccardctlStatus:
   Socket 0:
     no card
  ProcEnviron:
   LANGUAGE=de_CH:en
   PATH=(custom, user)
   LANG=de_CH.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.38-11-generic 
root=UUID=a4380962-8df8-486d-a8e3-2232227f97aa ro nosplash elevator=deadline
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/24/2009
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68DTV Ver. F.18
  dmi.board.name: 0934
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 43.1D
  dmi.chassis.asset.tag: oliverhp
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68DTVVer.F.18:bd07/24/2009:svnHewlett-Packard:pnHPCompaqnx8220(PY517EA#ABD):pvrF.18:rvnHewlett-Packard:rn0934:rvrKBCVersion43.1D:cvnHewlett-Packard:ct10:cvr:
  dmi.product.name: HP Compaq nx8220 (PY517EA#ABD)
  dmi.product.version: F.18
  dmi.sys.vendor: Hewlett-Packard
  hciconfig:
   hci0:Type: BR/EDR  Bus: USB
    BD Address: 00:16:41:7C:AC:64  ACL MTU: 377:10  SCO MTU: 16:0
    UP RUNNING PSCAN ISCAN
    RX bytes:11936 acl:127 sco:0 events:287 errors:0
    TX bytes:3254 acl:110 sco:0 commands:102 errors:0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/839157/+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 1709749] Re: AUFS on XFS needs fix for kernel 4.10

[Akihiro Suda]

Yes, I confirmed that the lp1709749 kernel works as expected.
Thank you for the work.

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

Title:
  AUFS on XFS needs fix for kernel 4.10

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Zesty:
  Incomplete

Bug description:
  1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> 
About Ubuntu
  Ubuntu 16.04 and 17.04

  2) The version of the package you are using, via 'apt-cache policy pkgname' 
or by checking in Software Center
  kernel 4.10.0-28-generic

  3) What you expected to happen

  Docker with AUFS on XFS works.

  4) What happened instead

  It hangs up

  ---

  As reported in https://github.com/moby/moby/issues/34361 , AUFS on XFS
  needs this fix for kernel 4.10:
  
https://github.com/sfjro/aufs4-standalone/commit/e34c81ff96415c64ca827ec30e7935454d26c1d3

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

Title:
  Nec/Renasas 27xxx2 May also need Quirk in 17.04, no problem in 16.04?
  Logitech C920 Webcam/Zoneminder/Startech

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  In trying to build a zoneminder server, I think I stumbled on a kernel
  bug. It  seems to have snuck in sometime between 16.04 desktop
  promoted to server, and 17.04 server promoted to desktop.

  The suggestion is that the very popular Nec/Renasas 27xxx2 may need
  "quirk" in the kernel.

  Timeline:

  
  (Scene 1)

  Loaded 16.04 Ubuntu Desktop
  Promoted Desktop to Studio
  Promoted Desktop to Server
  Added Zoneminder
  Needed more cams, added Startech  PEXUSB3S44V NEC/Renesasa 27XXX2 based card 
for more USB channels.
  Everything worked quite well. Some errors in ZM but no DMESG as far as I 
recall. 

  (Scene 2)
  Wiped the drive. 
  Loaded 17.04 Server
  Now getting messages in DMESG complaining of thousands of errors:
  [96415.044917] handle_tx_event: 516 callbacks suppressed
  [96415.044924] xhci_hcd :0c:00.0: WARN Successful completion on short TX: 
needs XHCI_TRUST_TX_LENGTH quirk?

  
  Messages suggest "quirk" is the solution.
  a)Researched usb 3.0 "quirk'
  b)Noticed it's really a "thing" 
  c)Couldn't find recipe for patching kernel for NEC/Renases "quirk" fix. 

  (Scene 3)
  Anecdotes suggest Nec/Renasas firmware is to blame.
  a) Kernel indicates 2024 firmaware
  b) Startech website has 2026 firmware. 
  c) VERY IMPORTANT! WindowCentric GUI instructions do not translate between 
ASCII and HEX. So if your Startech is on channels 9, 10, 11, and 12 from 
perspective of Windows, you must translate into 09, 0A, 0B, and 0C when editing 
runfile for effective firmware update of all 4 controllers. Yes, for the 4 
channel controller, count them: 4. 
  d) Firmware updated. 

  (Scene 4) 
  Rebooted with new Startech/Nec/Renases 2026 firmware. 
  SAME OLD PLETHORA OF ERRORS

  (Scene 5)
  I give up. 

  It may well be worth noting that there are no errors from DMESG until some 
seconds after the first webcam is attached to the Startech.
   
  And I can't overemphasize the fact that I don't think I had any DMESG errors 
under Desktop 16.04 

  I think the file attached represents DMESG immediately before the
  errors start going nuts. My theory is that ZM does lazy polls on
  missing cams but once it gets 'hold if the cam and sucking data the
  quirk bug surfaces.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-32-generic 4.10.0-32.36
  ProcVersionSignature: Ubuntu 4.10.0-32.36-generic 4.10.17
  Uname: Linux 4.10.0-32-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jeff  12776 F pulseaudio
   /dev/snd/controlC3:  jeff  12776 F pulseaudio
   /dev/snd/controlC2:  jeff  12776 F pulseaudio
   /dev/snd/controlC1:  jeff  12776 F pulseaudio
  Date: Sun Aug 13 16:48:41 2017
  MachineType: Supermicro X9SRE/X9SRE-3F/X9SRi/X9SRi-3F
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB:
   0 mgadrmfb
   1 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-32-generic 
root=UUID=4f802241-4254-4d61-9231-d7e16de36a3d 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:
   linux-restricted-modules-4.10.0-32-generic N/A
   linux-backports-modules-4.10.0-32-generic  N/A
   linux-firmware 1.164.1
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/31/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3.2a
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: X9SRE/X9SRE-3F/X9SRi/X9SRi-3F
  dmi.board.vendor: Supermicro
  dmi.board.version: 0123456789
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 17
  dmi.chassis.vendor: Supermicro
  dmi.chassis.version: 0123456789
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3.2a:bd08/31/2015:svnSupermicro:pnX9SRE/X9SRE-3F/X9SRi/X9SRi-3F:pvr0123456789:rvnSupermicro:rnX9SRE/X9SRE-3F/X9SRi/X9SRi-3F:rvr0123456789:cvnSupermicro:ct17:cvr0123456789:
  dmi.product.name: X9SRE/X9SRE-3F/X9SRi/X9SRi-3F
  dmi.product.version: 0123456789
  dmi.sys.vendor: Supermicro

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

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

[Kernel-packages] [Bug 1710548] [NEW] Nec/Renasas 27xxx2 May also need Quirk in 17.04, no problem in 16.04? Logitech C920 Webcam/Zoneminder/Startech

[Jeffrey Miller]

Public bug reported:

In trying to build a zoneminder server, I think I stumbled on a kernel
bug. It  seems to have snuck in sometime between 16.04 desktop promoted
to server, and 17.04 server promoted to desktop.

The suggestion is that the very popular Nec/Renasas 27xxx2 may need
"quirk" in the kernel.

Timeline:


(Scene 1)

Loaded 16.04 Ubuntu Desktop
Promoted Desktop to Studio
Promoted Desktop to Server
Added Zoneminder
Needed more cams, added Startech  PEXUSB3S44V NEC/Renesasa 27XXX2 based card 
for more USB channels.
Everything worked quite well. Some errors in ZM but no DMESG as far as I 
recall. 

(Scene 2)
Wiped the drive. 
Loaded 17.04 Server
Now getting messages in DMESG complaining of thousands of errors:
[96415.044917] handle_tx_event: 516 callbacks suppressed
[96415.044924] xhci_hcd :0c:00.0: WARN Successful completion on short TX: 
needs XHCI_TRUST_TX_LENGTH quirk?


Messages suggest "quirk" is the solution.
a)Researched usb 3.0 "quirk'
b)Noticed it's really a "thing" 
c)Couldn't find recipe for patching kernel for NEC/Renases "quirk" fix. 

(Scene 3)
Anecdotes suggest Nec/Renasas firmware is to blame.
a) Kernel indicates 2024 firmaware
b) Startech website has 2026 firmware. 
c) VERY IMPORTANT! WindowCentric GUI instructions do not translate between 
ASCII and HEX. So if your Startech is on channels 9, 10, 11, and 12 from 
perspective of Windows, you must translate into 09, 0A, 0B, and 0C when editing 
runfile for effective firmware update of all 4 controllers. Yes, for the 4 
channel controller, count them: 4. 
d) Firmware updated. 

(Scene 4) 
Rebooted with new Startech/Nec/Renases 2026 firmware. 
SAME OLD PLETHORA OF ERRORS

(Scene 5)
I give up. 

It may well be worth noting that there are no errors from DMESG until some 
seconds after the first webcam is attached to the Startech.
 
And I can't overemphasize the fact that I don't think I had any DMESG errors 
under Desktop 16.04 

I think the file attached represents DMESG immediately before the errors
start going nuts. My theory is that ZM does lazy polls on missing cams
but once it gets 'hold if the cam and sucking data the quirk bug
surfaces.

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: linux-image-4.10.0-32-generic 4.10.0-32.36
ProcVersionSignature: Ubuntu 4.10.0-32.36-generic 4.10.17
Uname: Linux 4.10.0-32-generic x86_64
ApportVersion: 2.20.4-0ubuntu4.5
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  jeff  12776 F pulseaudio
 /dev/snd/controlC3:  jeff  12776 F pulseaudio
 /dev/snd/controlC2:  jeff  12776 F pulseaudio
 /dev/snd/controlC1:  jeff  12776 F pulseaudio
Date: Sun Aug 13 16:48:41 2017
MachineType: Supermicro X9SRE/X9SRE-3F/X9SRi/X9SRi-3F
ProcEnviron:
 LANGUAGE=en_US
 TERM=xterm-256color
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcFB:
 0 mgadrmfb
 1 nouveaufb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-32-generic 
root=UUID=4f802241-4254-4d61-9231-d7e16de36a3d 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:
 linux-restricted-modules-4.10.0-32-generic N/A
 linux-backports-modules-4.10.0-32-generic  N/A
 linux-firmware 1.164.1
RfKill:
 
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/31/2015
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 3.2a
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: X9SRE/X9SRE-3F/X9SRi/X9SRi-3F
dmi.board.vendor: Supermicro
dmi.board.version: 0123456789
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 17
dmi.chassis.vendor: Supermicro
dmi.chassis.version: 0123456789
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3.2a:bd08/31/2015:svnSupermicro:pnX9SRE/X9SRE-3F/X9SRi/X9SRi-3F:pvr0123456789:rvnSupermicro:rnX9SRE/X9SRE-3F/X9SRi/X9SRi-3F:rvr0123456789:cvnSupermicro:ct17:cvr0123456789:
dmi.product.name: X9SRE/X9SRE-3F/X9SRi/X9SRi-3F
dmi.product.version: 0123456789
dmi.sys.vendor: Supermicro

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


** Tags: amd64 apport-bug zesty

** Attachment added: "The Queit B4 The Storm"
   
https://bugs.launchpad.net/bugs/1710548/+attachment/4931944/+files/dmesg.4.txt

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

Title:
  Nec/Renasas 27xxx2 May also need Quirk in 17.04, no problem in 16.04?
  Logitech C920 Webcam/Zoneminder/Startech

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  In trying to build a zoneminder server, I think I stumbled on a kernel
  bug. It  seems to have snuck in sometime between 16.04 desktop
  promoted to server, and 17.04 server promoted to desktop.

  The suggestion is that the very popular Nec/Renasas 27xxx2