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

2016-10-05 Thread bugproxy
--- Comment From ckuma...@in.ibm.com 2016-10-06 01:24 EDT---
Externalizing comment 61 and 62
-
The Same test is causing problem in ubuntu kernel version 4.8.0-17-generic.
Got below call traces:
[48755.933755]  112-...: (2 ticks this GP) idle=b95/140/0 
softirq=11738/11738 fqs=2829432
[48755.933979]  118-...: (5 ticks this GP) idle=011/140/0 
softirq=6041/6041 fqs=2829432
[48755.934264]  (detected by 29, t=11947979 jiffies, g=5047, c=5046, q=1984242)
[48692.907932] Call Trace:
[48692.907934] [c017e8a83980] [c00d57f8] irq_exit+0x98/0x100 
(unreliable)
[48692.907936] [c017e8a839a0] [c0024810] timer_interrupt+0xa0/0xe0
[48692.907938] [c017e8a839d0] [c0002814] 
decrementer_common+0x114/0x180
[48692.907942] --- interrupt: 901 at _cond_resched+0x0/0xa0
LR = stutter_wait+0x8c/0x130 [torture]
[48692.907945] [c017e8a83cc0] [d000158e0348] 
torture_rwlock_write_lock_irq+0x30/0x60 [locktorture] (unreliable)
[48692.907948] [c017e8a83cf0] [d000158e0a88] 
lock_torture_writer+0xc0/0x270 [locktorture]
[48692.907950] [c017e8a83d80] [c00fd120] kthread+0x110/0x130
[48692.907954] [c017e8a83e30] [c00098f0] 
ret_from_kernel_thread+0x5c/0x6c

This call traces keeps displaying from the time we execute the script and 
system is in hanged state.
---

Issue is seen in ubuntu 16.10 as well.

---

Canonical,

May we have some attention on this issue.

Thanks,
Chandan

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

Title:
  NMI watchdog: BUG: soft lockup errors when we execute lock_torture_wr
  tests

Status in linux package in Ubuntu:
  Triaged
Status in linux-lts-xenial package in Ubuntu:
  Triaged
Status in linux source package in Vivid:
  Incomplete

Bug description:
  ---Problem Description---
  NMI watchdog: BUG: soft lockup errors when we execute lock_torture_wr tests

  ---uname output---
  Linux alp15 3.19.0-18-generic #18~14.04.1-Ubuntu SMP Wed May 20 09:40:36 UTC 
2015 ppc64le ppc64le ppc64le GNU/Linux
   
  Machine Type = P8 

  ---Steps to Reproduce---
  Install a P8 Power VM LPAR with Ubuntu 14.04.2 ISO.
  Then install the Ubuntu 14.04.3 kernel on the same and reboot.
  Then compile and build the LTP latest test suites on the same.

  root@alp15:~# tar -xvf ltp-full-20150420.tar.bz2
  root@alp15:~# cd ltp-full-20150420/
  root@alp15:~/ltp-full-20150420# ls
  aclocal.m4  configure execltp.in  install-sh  Makefile  
READMErunltplite.shtestcasesutils
  autom4te.cache  configure.ac  IDcheck.sh  lib Makefile.release  
README.kernel_config  runtest  testscripts  ver_linux
  config.guessCOPYING   include ltpmenu missing   
runalltests.shscenario_groups  TODO VERSION
  config.sub  doc   INSTALL m4  pan   
runltpscripts  tools
  root@alp15:~/ltp-full-20150420# ./configure
  root@alp15:~/ltp-full-20150420# make
  root@alp15:~/ltp-full-20150420# make install

  root@alp15:/opt/ltp/testcases/bin# ./lock_torture.sh
  lock_torture 1 TINFO : estimate time 6.00 min
  lock_torture 1 TINFO : spin_lock: running 60 sec...

  Message from syslogd@alp15 at Thu Jun 18 01:23:32 2015 ...
  alp15 vmunix: [  308.034386] NMI watchdog: BUG: soft lockup - CPU#10 stuck 
for 21s! [lock_torture_wr:2337]

  Message from syslogd@alp15 at Thu Jun 18 01:23:32 2015 ...
  alp15 vmunix: [  308.034389] NMI watchdog: BUG: soft lockup - CPU#6 stuck for 
22s! [lock_torture_wr:2331]

  Message from syslogd@alp15 at Thu Jun 18 01:23:32 2015 ...
  alp15 vmunix: [  308.034394] NMI watchdog: BUG: soft lockup - CPU#0 stuck for 
22s! [lock_torture_wr:2339]

  Message from syslogd@alp15 at Thu Jun 18 01:23:32 2015 ...
  alp15 vmunix: [  308.034396] NMI watchdog: BUG: soft lockup - CPU#3 stuck for 
22s! [lock_torture_wr:2346]

  Message from syslogd@alp15 at Thu Jun 18 01:23:32 2015 ...
  alp15 vmunix: [  308.034398] NMI watchdog: BUG: soft lockup - CPU#7 stuck for 
21s! [lock_torture_wr:2334]

  Message from syslogd@alp15 at Thu Jun 18 01:23:32 2015 ...
  alp15 vmunix: [  308.034410] NMI watchdog: BUG: soft lockup - CPU#11 stuck 
for 22s! [lock_torture_wr:2321]

  Message from syslogd@alp15 at Thu Jun 18 01:23:32 2015 ...
  alp15 vmunix: [  308.034412] NMI watchdog: BUG: soft lockup - CPU#9 stuck for 
22s! [lock_torture_wr:2333]

  Message from syslogd@alp15 at Thu Jun 18 01:23:32 2015 ...
  alp15 vmunix: [  308.038386] NMI watchdog: BUG: soft lockup - CPU#14 stuck 
for 22s! [lock_torture_wr:2327]

   
  Stack trace output:
   root@alp15:~# dmesg | more
  [ 1717.146881] lock_torture_wr R  running task
  [ 1717.146881]
  [ 1717.146885] 0  2555  2 0x0804
  [ 1717.146887] Call Trace:
  [ 1717.146894] [c00c7551b820] [c00c7551b860] 0xc00c7551b860 
(unreliable)
  [ 

[Kernel-packages] [Bug 1602577] Re: [arm64] compute nodes unstable after upgrading from 4.2 to 4.4 kernel

2016-10-05 Thread Junien Fridrick
Compute node is still up. I think we can consider upstream 4.4.23 to be
good.

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

Title:
  [arm64] compute nodes unstable after upgrading from 4.2 to 4.4 kernel

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

Bug description:
  Hi,

  In order to investigate bug LP#1531768, we upgraded some arm64 compute
  nodes (swirlices) to a 4.4 kernel. I think it made the VMs work
  better, but the hosts became extremely unstable.

  After some time, getting a shell on them would be impossible.
  Connecting on the VSP, you'd get a prompt, and once you typed your
  username and password, you'd see the motd but the shell would never
  spawn.

  Because of these instability issues, all the arm64 compute nodes are
  now back on 4.2. However, we managed to capture "perf record" data
  when a host was failing. I'll attach it to the bug. Perhaps it will
  give you hints as to what we can do to help you troubleshoot this bug
  further.

  Once we have your instructions, we'll happily reboot one (or a few)
  nodes to 4.4 to continue troubleshooting.

  Thanks !
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jul 12 12:54 seq
   crw-rw 1 root audio 116, 33 Jul 12 12:54 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: arm64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: Error: [Errno 2] No such file or directory
  DistroRelease: Ubuntu 14.04
  Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize 
libusb: -99
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: console=ttyS0,9600n8r ro compat_uts_machine=armv7l
  ProcVersionSignature: Ubuntu 4.2.0-41.48~14.04.1-generic 4.2.8-ckt11
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-41-generic N/A
   linux-backports-modules-4.2.0-41-generic  N/A
   linux-firmware1.127.22
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  trusty uec-images
  Uname: Linux 4.2.0-41-generic aarch64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True

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

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


[Kernel-packages] [Bug 1628279] Re: python utilities script suffix (.py) should be removed as per Policy 10.4

2016-10-05 Thread Richard Laager
This is installing the files using the old names, and symlinking using
the new ones. Is that intentional? I expected it would install using the
new names and symlinks for the old ones.

** Tags removed: verification-done
** Tags added: verification-needed

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

Title:
  python utilities script suffix (.py) should be removed as per Policy
  10.4

Status in zfs-linux package in Ubuntu:
  Fix Released
Status in zfs-linux source package in Xenial:
  Fix Committed

Bug description:
  [Impact]

  The zfs utilities scripts shipped with debian and ubuntu such as :

  * arc_summary.py : Provides a summary of the statistics
  * arcstat.py : Print out ZFS ARC Statistics exported via kstat(1)
  * dbufstat.py : Print out statistics for all cached dmu buffers

  should be renamed according to Policy 10.4 :
  https://www.debian.org/doc/debian-policy/ch-files.html#s-scripts

  "When scripts are installed into a directory in the system PATH, the
  script name should not include an extension such as .sh or .pl that
  denotes the scripting language currently used to implement it."

  Ideally, this should be fixed and upstreamed to Debian (or to zfslinux
  upstream) as well.

  [Test Case]

   * Install zfsutils-linux
   * List files

   $ dpkg -L zfsutils-linux | egrep "arc|dbufstat"
     /usr/sbin/arc_summary.py
     /usr/sbin/arcstat.py
     /usr/sbin/dbufstat.py

  [Regression Potential]

   * none expected, this is a trivial change that simply rename the
  scripts to remove the extension (.py) with a simple 'mv' before the
  dh_install invocation in order to get this expected result :

  $ dpkg -L zfsutils-linux | egrep -i "arc|dbuf"
    /usr/sbin/arc_summary
    /usr/sbin/arcstat
    /usr/sbin/dbufstat

  Yakkety include the renaming as shown above.

  Xenial will have a symlink to not break user experience until next release 
upgrade:
  
https://bugs.launchpad.net/ubuntu/xenial/+source/zfs-linux/+bug/1628279/comments/19

  So user will be able to use both for instance : arcstat.py or arcstat

  
  [Other Info]

   * Justification/argument for Xenial
  https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1628279/comments/13
  https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1628279/comments/14

  * Debian bug
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=839645

   * Upstream (ZoL) is reluctant to change it at upstream code level.
  https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1628279/comments/2

   * This has been flag by Adam Conrad
  https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1574342/comments/19

   * Debian policy
  https://www.debian.org/doc/debian-policy/ch-files.html#s-scripts

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

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


[Kernel-packages] [Bug 1630857] Re: Dell Precision Trackpoint not working after suspend

2016-10-05 Thread AceLan Kao
** Tags added: originate-from-1623292 somerville

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

Title:
   Dell Precision Trackpoint not working after suspend

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  In Progress

Bug description:
  Steps:
  1) Install Ubuntu 16.04
  2) Enter Desktop.
  3) Suspend system.
  4) Using the trackpoint.
  5) Click the left button with DualPoint stick.
  6) Click the right button with DualPoint stick.
  7) Click the middle button with DualPoint stick.
  8) Double-click the left button with DualPoint stick.

  Expected results: Trackpoint and DualPoint stick can work after
  suspend.

  Actual results: Trackpoing and DualPoint stick not working after
  suspend.

  Manufacturer: Dell Inc.

  ProductName: Precision 7500

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

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


[Kernel-packages] [Bug 1630857] Re: Dell Precision Trackpoint not working after suspend

2016-10-05 Thread AceLan Kao
This issue could be fixed by this commit

commit 04fd4cb0b098789725d04e9d4a7e7dda373b1121
Author: Kai-Heng Feng 
Date:   Mon Sep 19 15:41:39 2016 +0800

HID: alps: fix stick device not working after resume

The stick device does not work after resume, add U1_SP_ABS_MODE flag can
make the device work after resume.

This has been discovered by pure guesswork, based on how the existing code 
uses
U1_TP_ABS_MODE flag on both initialization and resume.

I also tested the the patch on an ALPS touchpad without stick device, did 
not
notice any side effect on suspend/resume, so I made the U1_SP_ABS_MODE flag
mandatory.

[jkos...@suse.cz: made changelog more verbose]
Signed-off-by: Kai-Heng Feng 
Signed-off-by: Jiri Kosina 

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

Title:
   Dell Precision Trackpoint not working after suspend

Status in linux package in Ubuntu:
  In Progress

Bug description:
  Steps:
  1) Install Ubuntu 16.04
  2) Enter Desktop.
  3) Suspend system.
  4) Using the trackpoint.
  5) Click the left button with DualPoint stick.
  6) Click the right button with DualPoint stick.
  7) Click the middle button with DualPoint stick.
  8) Double-click the left button with DualPoint stick.

  Expected results: Trackpoint and DualPoint stick can work after
  suspend.

  Actual results: Trackpoing and DualPoint stick not working after
  suspend.

  Manufacturer: Dell Inc.

  ProductName: Precision 7500

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

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


[Kernel-packages] [Bug 1630279] onza (i386) - tests ran: 19, failed: 0

2016-10-05 Thread Brad Figg
tests ran:  19, failed: 0;
  
http://kernel.ubuntu.com/testing/4.8.0-21.23/onza__4.8.0-21.23__2016-10-06_04-05-00/results-index.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/1630279

Title:
  linux: 4.8.0-21.23 -proposed tracker

Status in Kernel Development Workflow:
  In Progress
Status in Kernel Development Workflow automated-testing series:
  New
Status in Kernel Development Workflow prepare-package series:
  Confirmed
Status in Kernel Development Workflow prepare-package-meta series:
  Confirmed
Status in Kernel Development Workflow prepare-package-signed series:
  Confirmed
Status in Kernel Development Workflow promote-to-proposed series:
  New
Status in Kernel Development Workflow promote-to-release series:
  New
Status in Kernel Development Workflow regression-testing series:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Yakkety:
  Confirmed

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

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

  kernel-phase-changed:Tuesday, 04. October 2016 15:16 UTC
  kernel-phase:Packaging

  -- swm properties --
  derivative-trackers-created: true
  phase: Packaging

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-development-workflow/+bug/1630279/+subscriptions

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


[Kernel-packages] [Bug 1630857] [NEW] Dell Precision Trackpoint not working after suspend

2016-10-05 Thread AceLan Kao
Public bug reported:

Steps:
1) Install Ubuntu 16.04
2) Enter Desktop.
3) Suspend system.
4) Using the trackpoint.
5) Click the left button with DualPoint stick.
6) Click the right button with DualPoint stick.
7) Click the middle button with DualPoint stick.
8) Double-click the left button with DualPoint stick.

Expected results: Trackpoint and DualPoint stick can work after suspend.

Actual results: Trackpoing and DualPoint stick not working after
suspend.

Manufacturer: Dell Inc.

ProductName: Precision 7500

** Affects: linux (Ubuntu)
 Importance: Undecided
 Assignee: AceLan Kao (acelankao)
 Status: In Progress

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

Title:
   Dell Precision Trackpoint not working after suspend

Status in linux package in Ubuntu:
  In Progress

Bug description:
  Steps:
  1) Install Ubuntu 16.04
  2) Enter Desktop.
  3) Suspend system.
  4) Using the trackpoint.
  5) Click the left button with DualPoint stick.
  6) Click the right button with DualPoint stick.
  7) Click the middle button with DualPoint stick.
  8) Double-click the left button with DualPoint stick.

  Expected results: Trackpoint and DualPoint stick can work after
  suspend.

  Actual results: Trackpoing and DualPoint stick not working after
  suspend.

  Manufacturer: Dell Inc.

  ProductName: Precision 7500

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

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


[Kernel-packages] [Bug 1483343] Re: NMI watchdog: BUG: soft lockup errors when we execute lock_torture_wr tests

2016-10-05 Thread bugproxy
** Tags removed: targetmilestone-inin14044
** Tags added: targetmilestone-inin1610

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

Title:
  NMI watchdog: BUG: soft lockup errors when we execute lock_torture_wr
  tests

Status in linux package in Ubuntu:
  Triaged
Status in linux-lts-xenial package in Ubuntu:
  Triaged
Status in linux source package in Vivid:
  Incomplete

Bug description:
  ---Problem Description---
  NMI watchdog: BUG: soft lockup errors when we execute lock_torture_wr tests

  ---uname output---
  Linux alp15 3.19.0-18-generic #18~14.04.1-Ubuntu SMP Wed May 20 09:40:36 UTC 
2015 ppc64le ppc64le ppc64le GNU/Linux
   
  Machine Type = P8 

  ---Steps to Reproduce---
  Install a P8 Power VM LPAR with Ubuntu 14.04.2 ISO.
  Then install the Ubuntu 14.04.3 kernel on the same and reboot.
  Then compile and build the LTP latest test suites on the same.

  root@alp15:~# tar -xvf ltp-full-20150420.tar.bz2
  root@alp15:~# cd ltp-full-20150420/
  root@alp15:~/ltp-full-20150420# ls
  aclocal.m4  configure execltp.in  install-sh  Makefile  
READMErunltplite.shtestcasesutils
  autom4te.cache  configure.ac  IDcheck.sh  lib Makefile.release  
README.kernel_config  runtest  testscripts  ver_linux
  config.guessCOPYING   include ltpmenu missing   
runalltests.shscenario_groups  TODO VERSION
  config.sub  doc   INSTALL m4  pan   
runltpscripts  tools
  root@alp15:~/ltp-full-20150420# ./configure
  root@alp15:~/ltp-full-20150420# make
  root@alp15:~/ltp-full-20150420# make install

  root@alp15:/opt/ltp/testcases/bin# ./lock_torture.sh
  lock_torture 1 TINFO : estimate time 6.00 min
  lock_torture 1 TINFO : spin_lock: running 60 sec...

  Message from syslogd@alp15 at Thu Jun 18 01:23:32 2015 ...
  alp15 vmunix: [  308.034386] NMI watchdog: BUG: soft lockup - CPU#10 stuck 
for 21s! [lock_torture_wr:2337]

  Message from syslogd@alp15 at Thu Jun 18 01:23:32 2015 ...
  alp15 vmunix: [  308.034389] NMI watchdog: BUG: soft lockup - CPU#6 stuck for 
22s! [lock_torture_wr:2331]

  Message from syslogd@alp15 at Thu Jun 18 01:23:32 2015 ...
  alp15 vmunix: [  308.034394] NMI watchdog: BUG: soft lockup - CPU#0 stuck for 
22s! [lock_torture_wr:2339]

  Message from syslogd@alp15 at Thu Jun 18 01:23:32 2015 ...
  alp15 vmunix: [  308.034396] NMI watchdog: BUG: soft lockup - CPU#3 stuck for 
22s! [lock_torture_wr:2346]

  Message from syslogd@alp15 at Thu Jun 18 01:23:32 2015 ...
  alp15 vmunix: [  308.034398] NMI watchdog: BUG: soft lockup - CPU#7 stuck for 
21s! [lock_torture_wr:2334]

  Message from syslogd@alp15 at Thu Jun 18 01:23:32 2015 ...
  alp15 vmunix: [  308.034410] NMI watchdog: BUG: soft lockup - CPU#11 stuck 
for 22s! [lock_torture_wr:2321]

  Message from syslogd@alp15 at Thu Jun 18 01:23:32 2015 ...
  alp15 vmunix: [  308.034412] NMI watchdog: BUG: soft lockup - CPU#9 stuck for 
22s! [lock_torture_wr:2333]

  Message from syslogd@alp15 at Thu Jun 18 01:23:32 2015 ...
  alp15 vmunix: [  308.038386] NMI watchdog: BUG: soft lockup - CPU#14 stuck 
for 22s! [lock_torture_wr:2327]

   
  Stack trace output:
   root@alp15:~# dmesg | more
  [ 1717.146881] lock_torture_wr R  running task
  [ 1717.146881]
  [ 1717.146885] 0  2555  2 0x0804
  [ 1717.146887] Call Trace:
  [ 1717.146894] [c00c7551b820] [c00c7551b860] 0xc00c7551b860 
(unreliable)
  [ 1717.146899] [c00c7551b860] [c00b4fb0] __do_softirq+0x220/0x3b0
  [ 1717.146904] [c00c7551b960] [c00b5478] irq_exit+0x98/0x100
  [ 1717.146909] [c00c7551b980] [c001fa54] timer_interrupt+0xa4/0xe0
  [ 1717.146913] [c00c7551b9b0] [c0002758] 
decrementer_common+0x158/0x180
  [ 1717.146922] --- interrupt: 901 at _raw_write_lock+0x68/0xc0
  [ 1717.146922] LR = torture_rwlock_write_lock+0x28/0x40 [locktorture]
  [ 1717.146927] [c00c7551bca0] [c00c7551bcd0] 0xc00c7551bcd0 
(unreliable)
  [ 1717.146934] [c00c7551bcd0] [dd4810b8] 
torture_rwlock_write_lock+0x28/0x40 [locktorture]
  [ 1717.146939] [c00c7551bcf0] [dd480578] 
lock_torture_writer+0x98/0x210 [locktorture]
  [ 1717.146944] [c00c7551bd80] [c00da4d4] kthread+0x114/0x140
  [ 1717.146948] [c00c7551be30] [c000956c] 
ret_from_kernel_thread+0x5c/0x70
  [ 1717.146951] Task dump for CPU 10:
  [ 1717.146953] lock_torture_wr R  running task0  2537  2 
0x0804
  [ 1717.146957] Call Trace:
  [ 1717.146961] [c00c7557b820] [c00c7557b860] 0xc00c7557b860 
(unreliable)
  [ 1717.146966] [c00c7557b860] [c00b4fb0] __do_softirq+0x220/0x3b0
  [ 1717.146970] [c00c7557b960] [c00b5478] irq_exit+0x98/0x100
  [ 1717.146975] [c00c7557b980] [c001fa54] 

[Kernel-packages] [Bug 1624267] Re: PCI quirk required for correct access to configuration space of NFP 4000/6000

2016-10-05 Thread Pragnesh Sampat
** Tags removed: verification-needed-trusty
** Tags added: verification-done-trusty

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

Title:
  PCI quirk required for correct access to configuration space of NFP
  4000/6000

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Trusty:
  Fix Committed

Bug description:
  The Netronome NFP 4000/6000 intelligent NICs have an erratum erratum where
  reading/writing to PCI config space addresses above 0x600 can cause the NFP
  to generate PCIe completion timeouts. This can result in a system hanging.

  This may be avoided by setting the PCI config size correctly and
  updating the PCI subsystem to honour config sizes between
  PCI_CFG_SPACE_EXP_SIZE (4096) and PCI_CFG_SPACE_SIZE (256).

  This problem is resolves in upstream linux since v4.5.

  Backports have also been requested to upstream linux stable back to v3.10
  and have so far been included in v4.4.10, v4.1.32, v4.18.41 and queued
  up for v3.10 stable.

  I would like to request that the same backports be made to the Ubuntu 13.0
  kernel for Trusty 14.04 LTS. They are as follows:

  
  commit c2e771b02792d222cbcd9617fe71482a64f52647
  Author: Simon Horman 
  Date:   Fri Dec 11 11:30:12 2015 +0900

  PCI: Limit config space size for Netronome NFP4000
  
  Like the NFP6000, the NFP4000 as an erratum where reading/writing to PCI
  config space addresses above 0x600 can cause the NFP to generate PCIe
  completion timeouts.
  
  Limit the NFP4000's PF's config space size to 0x600 bytes as is already
  done for the NFP6000.
  
  The NFP4000's VF is 0x6004 (PCI_DEVICE_ID_NETRONOME_NFP6000_VF), the same
  device ID as the NFP6000's VF.  Thus, its config space is already limited
  by the existing use of quirk_nfp6000().
  
  Signed-off-by: Simon Horman 
  Signed-off-by: Bjorn Helgaas 

  commit 69874ec233871a62e1bc8c89e643993af93a8630
  Author: Simon Horman 
  Date:   Fri Dec 11 11:30:11 2015 +0900

  PCI: Add Netronome NFP4000 PF device ID
  
  Add the device ID for the PF of the NFP4000.  The device ID for the VF,
  0x6003, is already present as PCI_DEVICE_ID_NETRONOME_NFP6000_VF.
  
  Signed-off-by: Simon Horman 
  Signed-off-by: Bjorn Helgaas 

  commit 9f33a2ae59f24452c1076749deb615bccd435ca9
  Author: Jason S. McMullan 
  Date:   Wed Sep 30 15:35:07 2015 +0900

  PCI: Limit config space size for Netronome NFP6000 family
  
  The NFP6000 has an erratum where reading/writing to PCI config space
  addresses above 0x600 can cause the NFP to generate PCIe completion
  timeouts.
  
  Limit the NFP6000's config space size to 0x600 bytes.
  
  Signed-off-by: Jason S. McMullan 
  [simon: edited changelog]
  Signed-off-by: Simon Horman 
  Signed-off-by: Bjorn Helgaas 

  commit a755e169031dac9ebaed03302c4921687c271d62
  Author: Jason S. McMullan 
  Date:   Wed Sep 30 15:35:06 2015 +0900

  PCI: Add Netronome vendor and device IDs
  
  Device IDs for the Netronome NFP3200, NFP3240, NFP6000, and NFP6000 SR-IOV
  devices.
  
  Signed-off-by: Jason S. McMullan 
  [simon: edited changelog]
  Signed-off-by: Simon Horman 
  Signed-off-by: Bjorn Helgaas 

  commit c20aecf6963d1273d8f6d61c042b4845441ca592
  Author: Jason S. McMullan 
  Date:   Wed Sep 30 15:35:05 2015 +0900

  PCI: Support PCIe devices with short cfg_size
  
  If a device quirk modifies the pci_dev->cfg_size to be less than
  PCI_CFG_SPACE_EXP_SIZE (4096), but greater than PCI_CFG_SPACE_SIZE (256),
  the PCI sysfs interface truncates the readable size to PCI_CFG_SPACE_SIZE.
  
  Allow sysfs access to config space up to cfg_size, even if the device
  doesn't support the entire 4096-byte PCIe config space.
  
  Note that pci_read_config() and pci_write_config() limit access to
  dev->cfg_size even though pcie_config_attr contains 4096 (the maximum
  size).
  
  Signed-off-by: Jason S. McMullan 
  [simon: edited changelog]
  Signed-off-by: Simon Horman 
  [bhelgaas: more changelog edits]
  Signed-off-by: Bjorn Helgaas 

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post 

[Kernel-packages] [Bug 1624267] Re: PCI quirk required for correct access to configuration space of NFP 4000/6000

2016-10-05 Thread Pragnesh Sampat
Attached logs that show 4.4.0-41 was installed on 2 systems with the
proposed patch applied and system booted and the patch verified.

** Attachment added: "Verification logs for qurik_nfp6000"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1624267/+attachment/4755623/+files/quirk_nfp6000-4.4.0-41-verification-logs.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/1624267

Title:
  PCI quirk required for correct access to configuration space of NFP
  4000/6000

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Trusty:
  Fix Committed

Bug description:
  The Netronome NFP 4000/6000 intelligent NICs have an erratum erratum where
  reading/writing to PCI config space addresses above 0x600 can cause the NFP
  to generate PCIe completion timeouts. This can result in a system hanging.

  This may be avoided by setting the PCI config size correctly and
  updating the PCI subsystem to honour config sizes between
  PCI_CFG_SPACE_EXP_SIZE (4096) and PCI_CFG_SPACE_SIZE (256).

  This problem is resolves in upstream linux since v4.5.

  Backports have also been requested to upstream linux stable back to v3.10
  and have so far been included in v4.4.10, v4.1.32, v4.18.41 and queued
  up for v3.10 stable.

  I would like to request that the same backports be made to the Ubuntu 13.0
  kernel for Trusty 14.04 LTS. They are as follows:

  
  commit c2e771b02792d222cbcd9617fe71482a64f52647
  Author: Simon Horman 
  Date:   Fri Dec 11 11:30:12 2015 +0900

  PCI: Limit config space size for Netronome NFP4000
  
  Like the NFP6000, the NFP4000 as an erratum where reading/writing to PCI
  config space addresses above 0x600 can cause the NFP to generate PCIe
  completion timeouts.
  
  Limit the NFP4000's PF's config space size to 0x600 bytes as is already
  done for the NFP6000.
  
  The NFP4000's VF is 0x6004 (PCI_DEVICE_ID_NETRONOME_NFP6000_VF), the same
  device ID as the NFP6000's VF.  Thus, its config space is already limited
  by the existing use of quirk_nfp6000().
  
  Signed-off-by: Simon Horman 
  Signed-off-by: Bjorn Helgaas 

  commit 69874ec233871a62e1bc8c89e643993af93a8630
  Author: Simon Horman 
  Date:   Fri Dec 11 11:30:11 2015 +0900

  PCI: Add Netronome NFP4000 PF device ID
  
  Add the device ID for the PF of the NFP4000.  The device ID for the VF,
  0x6003, is already present as PCI_DEVICE_ID_NETRONOME_NFP6000_VF.
  
  Signed-off-by: Simon Horman 
  Signed-off-by: Bjorn Helgaas 

  commit 9f33a2ae59f24452c1076749deb615bccd435ca9
  Author: Jason S. McMullan 
  Date:   Wed Sep 30 15:35:07 2015 +0900

  PCI: Limit config space size for Netronome NFP6000 family
  
  The NFP6000 has an erratum where reading/writing to PCI config space
  addresses above 0x600 can cause the NFP to generate PCIe completion
  timeouts.
  
  Limit the NFP6000's config space size to 0x600 bytes.
  
  Signed-off-by: Jason S. McMullan 
  [simon: edited changelog]
  Signed-off-by: Simon Horman 
  Signed-off-by: Bjorn Helgaas 

  commit a755e169031dac9ebaed03302c4921687c271d62
  Author: Jason S. McMullan 
  Date:   Wed Sep 30 15:35:06 2015 +0900

  PCI: Add Netronome vendor and device IDs
  
  Device IDs for the Netronome NFP3200, NFP3240, NFP6000, and NFP6000 SR-IOV
  devices.
  
  Signed-off-by: Jason S. McMullan 
  [simon: edited changelog]
  Signed-off-by: Simon Horman 
  Signed-off-by: Bjorn Helgaas 

  commit c20aecf6963d1273d8f6d61c042b4845441ca592
  Author: Jason S. McMullan 
  Date:   Wed Sep 30 15:35:05 2015 +0900

  PCI: Support PCIe devices with short cfg_size
  
  If a device quirk modifies the pci_dev->cfg_size to be less than
  PCI_CFG_SPACE_EXP_SIZE (4096), but greater than PCI_CFG_SPACE_SIZE (256),
  the PCI sysfs interface truncates the readable size to PCI_CFG_SPACE_SIZE.
  
  Allow sysfs access to config space up to cfg_size, even if the device
  doesn't support the entire 4096-byte PCIe config space.
  
  Note that pci_read_config() and pci_write_config() limit access to
  dev->cfg_size even though pcie_config_attr contains 4096 (the maximum
  size).
  
  Signed-off-by: Jason S. McMullan 
  [simon: edited changelog]
  Signed-off-by: Simon Horman 
  [bhelgaas: more changelog 

[Kernel-packages] [Bug 1630279] onza (amd64) - tests ran: 19, failed: 0

2016-10-05 Thread Brad Figg
tests ran:  19, failed: 0;
  
http://kernel.ubuntu.com/testing/4.8.0-21.23/onza__4.8.0-21.23__2016-10-06_02-45-00/results-index.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/1630279

Title:
  linux: 4.8.0-21.23 -proposed tracker

Status in Kernel Development Workflow:
  In Progress
Status in Kernel Development Workflow automated-testing series:
  New
Status in Kernel Development Workflow prepare-package series:
  Confirmed
Status in Kernel Development Workflow prepare-package-meta series:
  Confirmed
Status in Kernel Development Workflow prepare-package-signed series:
  Confirmed
Status in Kernel Development Workflow promote-to-proposed series:
  New
Status in Kernel Development Workflow promote-to-release series:
  New
Status in Kernel Development Workflow regression-testing series:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Yakkety:
  Confirmed

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

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

  kernel-phase-changed:Tuesday, 04. October 2016 15:16 UTC
  kernel-phase:Packaging

  -- swm properties --
  derivative-trackers-created: true
  phase: Packaging

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-development-workflow/+bug/1630279/+subscriptions

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


[Kernel-packages] [Bug 1630279] onza (i386) - tests ran: 22, failed: 1

2016-10-05 Thread Brad Figg
tests ran:  22, failed: 1;
  
http://kernel.ubuntu.com/testing/4.8.0-21.23/onza__4.8.0-21.23__2016-10-06_00-41-00/results-index.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/1630279

Title:
  linux: 4.8.0-21.23 -proposed tracker

Status in Kernel Development Workflow:
  In Progress
Status in Kernel Development Workflow automated-testing series:
  New
Status in Kernel Development Workflow prepare-package series:
  Confirmed
Status in Kernel Development Workflow prepare-package-meta series:
  Confirmed
Status in Kernel Development Workflow prepare-package-signed series:
  Confirmed
Status in Kernel Development Workflow promote-to-proposed series:
  New
Status in Kernel Development Workflow promote-to-release series:
  New
Status in Kernel Development Workflow regression-testing series:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Yakkety:
  Confirmed

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

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

  kernel-phase-changed:Tuesday, 04. October 2016 15:16 UTC
  kernel-phase:Packaging

  -- swm properties --
  derivative-trackers-created: true
  phase: Packaging

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-development-workflow/+bug/1630279/+subscriptions

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


[Kernel-packages] [Bug 1625912] Re: Kernel option usbhid.mousepoll=1 is now ignored

2016-10-05 Thread Daniel van Vugt
Sorry, no I don't recall.

I do however have a second machine running xenial rather than yakkety
that I'm yet to test. So that might help...

Unfortunately I've also changed machines between it last working and
now. So this might be a USB hardware fault but I struggle to see how
that would prevent something as slow as 1000 mouse events per second
from working. So I'm hoping and assuming it's just a kernel regression.

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

Title:
  Kernel option usbhid.mousepoll=1 is now ignored

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Kernel option usbhid.mousepoll=1 is now ignored.

  I can see in /proc/cmdline that I still have usbhid.mousepoll=1 but in
  real testing with Mir clients I'm only getting 125Hz input instead of
  the expected 1000Hz.

  Just a few months ago at least it was working (with the same mouse but
  different PC).

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: linux-image-4.4.0-9136-generic 4.4.0-9136.55
  ProcVersionSignature: Ubuntu 4.4.0-9136.55-generic 4.4.16
  Uname: Linux 4.4.0-9136-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/hwC0D0', 
'/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/controlC0', 
'/dev/snd/by-path', '/dev/snd/hwC1D2', '/dev/snd/pcmC1D2c', 
'/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/controlC1', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Date: Wed Sep 21 11:59:24 2016
  HibernationDevice: RESUME=UUID=14362a37-9d65-44cb-af81-5694ee7c17c1
  InstallationDate: Installed on 2016-07-11 (72 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160710)
  IwConfig:
   lono wireless extensions.
   
   eno1  no wireless extensions.
  MachineType: LENOVO 30AJS05700
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-9136-generic.efi.signed 
root=UUID=81044886-888d-4a06-893c-d740f91759e0 ro quiet splash 
usbhid.mousepoll=1 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.4.0-9136-generic N/A
   linux-backports-modules-4.4.0-9136-generic  N/A
   linux-firmware  1.161
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/02/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: FBKTB6AUS
  dmi.board.name: SHARKBAY
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50519 PRO
  dmi.chassis.type: 7
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnLENOVO:bvrFBKTB6AUS:bd08/02/2015:svnLENOVO:pn30AJS05700:pvrThinkStationP300:rvnLENOVO:rnSHARKBAY:rvrSDK0E50519PRO:cvnToBeFilledByO.E.M.:ct7:cvrToBeFilledByO.E.M.:
  dmi.product.name: 30AJS05700
  dmi.product.version: ThinkStation P300
  dmi.sys.vendor: LENOVO

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

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


[Kernel-packages] [Bug 1630279] dwalin (amd64) - tests ran: 136, failed: 0

2016-10-05 Thread Brad Figg
tests ran: 136, failed: 0;
  
http://kernel.ubuntu.com/testing/4.8.0-21.23/dwalin__4.8.0-21.23__2016-10-06_00-27-00/results-index.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/1630279

Title:
  linux: 4.8.0-21.23 -proposed tracker

Status in Kernel Development Workflow:
  In Progress
Status in Kernel Development Workflow automated-testing series:
  New
Status in Kernel Development Workflow prepare-package series:
  Confirmed
Status in Kernel Development Workflow prepare-package-meta series:
  Confirmed
Status in Kernel Development Workflow prepare-package-signed series:
  Confirmed
Status in Kernel Development Workflow promote-to-proposed series:
  New
Status in Kernel Development Workflow promote-to-release series:
  New
Status in Kernel Development Workflow regression-testing series:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Yakkety:
  Confirmed

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

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

  kernel-phase-changed:Tuesday, 04. October 2016 15:16 UTC
  kernel-phase:Packaging

  -- swm properties --
  derivative-trackers-created: true
  phase: Packaging

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-development-workflow/+bug/1630279/+subscriptions

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


[Kernel-packages] [Bug 1588637] Re: iwlwifi: Microcode SW error detected. Restarting 0x2000000

2016-10-05 Thread Valentin Neacsu
I had the same issue as reported here. I noticed at boot that the driver
was failing to load its primary firmware choice, falling back to a
different version:

[3.538299] iwlwifi :04:00.0: Direct firmware load for 
iwlwifi-7260-17.ucode failed with error -2
[3.541299] iwlwifi :04:00.0: loaded firmware version 16.242414.0 
op_mode iwlmvm

I checked /lib/firmware and the highest version I had there was
iwlwifi-7260-16.ucode, which corresponds to 16.242414.0 in the logs
above. I decided to rename iwlwifi-7260-16.ucode to prevent it from
being loaded, as this would allow the driver to fall back onto the next
best firmware file, iwlwifi-7260-13.ucode. This didn't help.

To fix this problem I looked at
https://wireless.wiki.kernel.org/en/users/drivers/iwlwifi#firmware and
downloaded iwlwifi-7260-17.ucode (via git) and copied it into
/lib/firmware, then rebooted. I haven't had any issue since applying
this fix, where previously I'd be getting a firmware crash once every
15-30 minutes.

This new firmware file is not present in linux-firmware 1.157.3 that I have on 
my Xenial box, but it does seem to be included in linux-firmware 1.161 as part 
of Yakkety, so I suggest downloading and installing it:
https://launchpad.net/ubuntu/yakkety/amd64/linux-firmware/1.161

It would be great if this update was pushed to Xenial as well in order
to mitigate the issues we're seeing.

Judging by the fact that downgrading to a previous firmware version
didn't seem to help (so the issue was not caused by a firmware upgrade),
but upgrading did help, I suspect that a recent change in iwlwifi or the
kernel is causing the wifi to fail unless it is using the new firmware
in iwlwifi-7260-17.ucode.

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

Title:
   iwlwifi: Microcode SW error detected. Restarting 0x200

Status in linux package in Ubuntu:
  Triaged

Bug description:
  My wifi won't work after I wake my laptop up from standby.

  This problem looks quite the same as #1099487 or #944271.

  But I experienced this bug on Xenial with 4.4.0-22-generic (amd64).

  A `sudo modprobe -r iwlwifi && sudo modprobe iwlwifi` doesn't solve
  the problem. (A reboot does.)

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-22-generic 4.4.0-22.40
  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.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  niklas 2175 F pulseaudio
   /dev/snd/controlC0:  niklas 2175 F pulseaudio
  CurrentDesktop: KDE
  Date: Fri Jun  3 08:23:06 2016
  InstallationDate: Installed on 2015-12-11 (174 days ago)
  InstallationMedia: Kubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  IwConfig:
   eth0  no wireless extensions.

   lono wireless extensions.

   lxcbr0no wireless extensions.
  MachineType: LENOVO 20E8S00600
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.4.0-22-generic.efi.signed 
root=UUID=67485aa6-c665-4c53-bf41-328307d0cbf0 ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-22-generic N/A
   linux-backports-modules-4.4.0-22-generic  N/A
   linux-firmware1.157
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/24/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: JHET20WW (1.00 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: Intel powered classmate PC
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrJHET20WW(1.00):bd02/24/2015:svnLENOVO:pn20E8S00600:pvrThinkPad11e:rvnLENOVO:rnIntelpoweredclassmatePC:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.name: 20E8S00600
  dmi.product.version: ThinkPad 11e
  dmi.sys.vendor: LENOVO

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

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


[Kernel-packages] [Bug 1630459] Re: Ralink rt5390 unstable connection on ubuntu 16.04.1

2016-10-05 Thread Christopher M. Penalver
** Tags added: needs-full-computer-model needs-full-router-
model+firmware

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

Title:
  Ralink rt5390 unstable connection on ubuntu 16.04.1

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 16.04.1 with all updates. Default kernel, default driver, and
  default NetworkManager setup. Wifi connection drops often and/or
  became slow. I tried disabling NetworkManager and installing Wicd for
  network management. All working ok since then.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-38-generic 4.4.0-38.57
  ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
  Uname: Linux 4.4.0-38-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  julio  1402 F pulseaudio
  CurrentDesktop: Unity
  Date: Wed Oct  5 08:45:26 2016
  InstallationDate: Installed on 2016-10-03 (1 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: Hewlett-Packard HP Pavilion g6 Notebook PC
  ProcEnviron:
   LANGUAGE=es_ES
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=es_ES.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-38-generic 
root=UUID=76af3e82-8ad6-45c9-973b-e711401f288e ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-38-generic N/A
   linux-backports-modules-4.4.0-38-generic  N/A
   linux-firmware1.157.3
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/17/2013
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.24
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 1840
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 56.32
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.24:bd01/17/2013:svnHewlett-Packard:pnHPPaviliong6NotebookPC:pvr07911020561620100:rvnHewlett-Packard:rn1840:rvr56.32:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.name: HP Pavilion g6 Notebook PC
  dmi.product.version: 07911020561620100
  dmi.sys.vendor: Hewlett-Packard

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

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


[Kernel-packages] [Bug 1626749] Re: autofs set $USER to "root" instead of current user

2016-10-05 Thread Fabio
I had the same problem after doing a "do-release-upgrade" from 14.04 to 16.04 
on October 5, 2016.
The kernel installed by default was 4.4.0-38.

After reading this thread I installed 4.4.0-40.60.
With both 4.4.0-38 and 4.4.0-40.60 I have the problem of $USER being mapped to 
root instead of to the current user.

I then installed kernel 4.4.0-36 (which I'm using on other VMs that were
upgraded a few weeks back) and everything worked just fine.

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

Title:
  autofs set $USER to "root" instead of current user

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Since last kernel upgrade from 4.4.0-36 to 4.4.0-38 automount failed to mount 
remote smb FS.
  The configuration file use $USER, $UID and $GID variables :
  i.e. :
  music 
-fstype=cifs,credentials=/home/$USER/.creds-file,user=$USER,uid=$UID,gid=$GID 
://192.168.1.9/music

  When a user account try to mount the FS, automount complain :

   >> error 2 (No such file or directory) opening credential file
  /home/root/.creds-file

  $USER, $UID and $GID are now sets with root variables instead of user
  account variables

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: autofs 5.1.1-1ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
  Uname: Linux 4.4.0-38-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Thu Sep 22 23:17:27 2016
  ExecutablePath: /usr/sbin/automount
  InstallationDate: Installed on 2016-02-07 (228 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  ProcEnviron:
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
  SourcePackage: autofs
  UpgradeStatus: Upgraded to xenial on 2016-04-28 (147 days ago)
  --- 
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nicolas1941 F pulseaudio
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=1ad9a17c-8b27-4436-a024-6c9ae99a5b87
  InstallationDate: Installed on 2016-02-07 (228 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: Sony Corporation SVS1511R9ES
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=fr_FR
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-38-generic.efi.signed 
root=UUID=df815dd3-2e1b-42d3-aef8-1823eb5d4f75 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
  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.4.0-38-generic N/A
   linux-backports-modules-4.4.0-38-generic  N/A
   linux-firmware1.157.3
  Tags:  xenial
  Uname: Linux 4.4.0-38-generic x86_64
  UpgradeStatus: Upgraded to xenial on 2016-04-28 (147 days ago)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 03/30/2012
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: R0140C5
  dmi.board.asset.tag: N/A
  dmi.board.name: VAIO
  dmi.board.vendor: Sony Corporation
  dmi.board.version: N/A
  dmi.chassis.asset.tag: N/A
  dmi.chassis.type: 10
  dmi.chassis.vendor: Sony Corporation
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrR0140C5:bd03/30/2012:svnSonyCorporation:pnSVS1511R9ES:pvrC60AGQAL:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A:
  dmi.product.name: SVS1511R9ES
  dmi.product.version: C60AGQAL
  dmi.sys.vendor: Sony Corporation

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

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


[Kernel-packages] [Bug 1630279] modoc (ppc64el) - tests ran: 136, failed: 0

2016-10-05 Thread Brad Figg
tests ran: 136, failed: 0;
  
http://kernel.ubuntu.com/testing/4.8.0-21.23/modoc__4.8.0-21.23__2016-10-05_23-50-00/results-index.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/1630279

Title:
  linux: 4.8.0-21.23 -proposed tracker

Status in Kernel Development Workflow:
  In Progress
Status in Kernel Development Workflow automated-testing series:
  New
Status in Kernel Development Workflow prepare-package series:
  Confirmed
Status in Kernel Development Workflow prepare-package-meta series:
  Confirmed
Status in Kernel Development Workflow prepare-package-signed series:
  Confirmed
Status in Kernel Development Workflow promote-to-proposed series:
  New
Status in Kernel Development Workflow promote-to-release series:
  New
Status in Kernel Development Workflow regression-testing series:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Yakkety:
  Confirmed

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

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

  kernel-phase-changed:Tuesday, 04. October 2016 15:16 UTC
  kernel-phase:Packaging

  -- swm properties --
  derivative-trackers-created: true
  phase: Packaging

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-development-workflow/+bug/1630279/+subscriptions

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


[Kernel-packages] [Bug 1630279] onza (amd64) - tests ran: 35, failed: 1

2016-10-05 Thread Brad Figg
tests ran:  35, failed: 1;
  
http://kernel.ubuntu.com/testing/4.8.0-21.23/onza__4.8.0-21.23__2016-10-05_23-11-00/results-index.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/1630279

Title:
  linux: 4.8.0-21.23 -proposed tracker

Status in Kernel Development Workflow:
  In Progress
Status in Kernel Development Workflow automated-testing series:
  New
Status in Kernel Development Workflow prepare-package series:
  Confirmed
Status in Kernel Development Workflow prepare-package-meta series:
  Confirmed
Status in Kernel Development Workflow prepare-package-signed series:
  Confirmed
Status in Kernel Development Workflow promote-to-proposed series:
  New
Status in Kernel Development Workflow promote-to-release series:
  New
Status in Kernel Development Workflow regression-testing series:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Yakkety:
  Confirmed

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

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

  kernel-phase-changed:Tuesday, 04. October 2016 15:16 UTC
  kernel-phase:Packaging

  -- swm properties --
  derivative-trackers-created: true
  phase: Packaging

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-development-workflow/+bug/1630279/+subscriptions

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


[Kernel-packages] [Bug 1630279] modoc (ppc64el) - tests ran: 19, failed: 6

2016-10-05 Thread Brad Figg
tests ran:  19, failed: 6;
  
http://kernel.ubuntu.com/testing/4.8.0-21.23/modoc__4.8.0-21.23__2016-10-05_22-47-00/results-index.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/1630279

Title:
  linux: 4.8.0-21.23 -proposed tracker

Status in Kernel Development Workflow:
  In Progress
Status in Kernel Development Workflow automated-testing series:
  New
Status in Kernel Development Workflow prepare-package series:
  Confirmed
Status in Kernel Development Workflow prepare-package-meta series:
  Confirmed
Status in Kernel Development Workflow prepare-package-signed series:
  Confirmed
Status in Kernel Development Workflow promote-to-proposed series:
  New
Status in Kernel Development Workflow promote-to-release series:
  New
Status in Kernel Development Workflow regression-testing series:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Yakkety:
  Confirmed

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

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

  kernel-phase-changed:Tuesday, 04. October 2016 15:16 UTC
  kernel-phase:Packaging

  -- swm properties --
  derivative-trackers-created: true
  phase: Packaging

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-development-workflow/+bug/1630279/+subscriptions

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


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

2016-10-05 Thread John Johansen
** Changed in: apparmor
   Status: New => Fix Committed

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

Title:
  Regression tests can not detect binfmt_elf mmpa semantic change

Status in AppArmor:
  Fix Committed
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Yakkety:
  In Progress

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

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

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

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


[Kernel-packages] [Bug 1630279] modoc (ppc64el) - tests ran: 35, failed: 4

2016-10-05 Thread Brad Figg
tests ran:  35, failed: 4;
  
http://kernel.ubuntu.com/testing/4.8.0-21.23/modoc__4.8.0-21.23__2016-10-05_20-50-00/results-index.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/1630279

Title:
  linux: 4.8.0-21.23 -proposed tracker

Status in Kernel Development Workflow:
  In Progress
Status in Kernel Development Workflow automated-testing series:
  New
Status in Kernel Development Workflow prepare-package series:
  Confirmed
Status in Kernel Development Workflow prepare-package-meta series:
  Confirmed
Status in Kernel Development Workflow prepare-package-signed series:
  Confirmed
Status in Kernel Development Workflow promote-to-proposed series:
  New
Status in Kernel Development Workflow promote-to-release series:
  New
Status in Kernel Development Workflow regression-testing series:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Yakkety:
  Confirmed

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

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

  kernel-phase-changed:Tuesday, 04. October 2016 15:16 UTC
  kernel-phase:Packaging

  -- swm properties --
  derivative-trackers-created: true
  phase: Packaging

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-development-workflow/+bug/1630279/+subscriptions

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


[Kernel-packages] [Bug 1630279] onza (amd64) - tests ran: 5, failed: 3

2016-10-05 Thread Brad Figg
tests ran:   5, failed: 3;
  
http://kernel.ubuntu.com/testing/4.8.0-21.23/onza__4.8.0-21.23__2016-10-05_20-14-00/results-index.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/1630279

Title:
  linux: 4.8.0-21.23 -proposed tracker

Status in Kernel Development Workflow:
  In Progress
Status in Kernel Development Workflow automated-testing series:
  New
Status in Kernel Development Workflow prepare-package series:
  Confirmed
Status in Kernel Development Workflow prepare-package-meta series:
  Confirmed
Status in Kernel Development Workflow prepare-package-signed series:
  Confirmed
Status in Kernel Development Workflow promote-to-proposed series:
  New
Status in Kernel Development Workflow promote-to-release series:
  New
Status in Kernel Development Workflow regression-testing series:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Yakkety:
  Confirmed

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

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

  kernel-phase-changed:Tuesday, 04. October 2016 15:16 UTC
  kernel-phase:Packaging

  -- swm properties --
  derivative-trackers-created: true
  phase: Packaging

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-development-workflow/+bug/1630279/+subscriptions

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


[Kernel-packages] [Bug 1630279] dwalin (amd64) - tests ran: 5, failed: 3

2016-10-05 Thread Brad Figg
tests ran:   5, failed: 3;
  
http://kernel.ubuntu.com/testing/4.8.0-21.23/dwalin__4.8.0-21.23__2016-10-05_20-08-00/results-index.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/1630279

Title:
  linux: 4.8.0-21.23 -proposed tracker

Status in Kernel Development Workflow:
  In Progress
Status in Kernel Development Workflow automated-testing series:
  New
Status in Kernel Development Workflow prepare-package series:
  Confirmed
Status in Kernel Development Workflow prepare-package-meta series:
  Confirmed
Status in Kernel Development Workflow prepare-package-signed series:
  Confirmed
Status in Kernel Development Workflow promote-to-proposed series:
  New
Status in Kernel Development Workflow promote-to-release series:
  New
Status in Kernel Development Workflow regression-testing series:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Yakkety:
  Confirmed

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

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

  kernel-phase-changed:Tuesday, 04. October 2016 15:16 UTC
  kernel-phase:Packaging

  -- swm properties --
  derivative-trackers-created: true
  phase: Packaging

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-development-workflow/+bug/1630279/+subscriptions

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


[Kernel-packages] [Bug 1630279] s2lp6g002 (s390x.zKVM) - tests ran: 64, failed: 0

2016-10-05 Thread Brad Figg
tests ran:  64, failed: 0;
  
http://kernel.ubuntu.com/testing/4.8.0-21.23/s2lp6g002__4.8.0-21.23__2016-10-05_21-48-00/results-index.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/1630279

Title:
  linux: 4.8.0-21.23 -proposed tracker

Status in Kernel Development Workflow:
  In Progress
Status in Kernel Development Workflow automated-testing series:
  New
Status in Kernel Development Workflow prepare-package series:
  Confirmed
Status in Kernel Development Workflow prepare-package-meta series:
  Confirmed
Status in Kernel Development Workflow prepare-package-signed series:
  Confirmed
Status in Kernel Development Workflow promote-to-proposed series:
  New
Status in Kernel Development Workflow promote-to-release series:
  New
Status in Kernel Development Workflow regression-testing series:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Yakkety:
  Confirmed

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

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

  kernel-phase-changed:Tuesday, 04. October 2016 15:16 UTC
  kernel-phase:Packaging

  -- swm properties --
  derivative-trackers-created: true
  phase: Packaging

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-development-workflow/+bug/1630279/+subscriptions

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


[Kernel-packages] [Bug 1630774] Missing required logs.

2016-10-05 Thread Brad Figg
This bug is missing log files that will aid in diagnosing the problem.
>From a terminal window please run:

apport-collect 1630774

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

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

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

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

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

Title:
  kernel invalid opcode in intel_powerclamp

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  kernel error on VMware Fusion when booting to graphical login

  
  invalid opcode:  [#1] SMP
  Modules linked in: ipmi_msghandler intel_powerclamp coretemp crct10dif_pclmul 
crc32_pclmul ghash_clmulni_intel vmw_balloon aesni_intel aes_x86_64 lrw 
glue_helper ablk_helper cryptd intel_rapl_perf joydev input_leds serio_raw 
snd_ens1371 snd_ac97_codec gameport ac97_bus snd_pcm binfmt_misc snd_seq_midi 
snd_seq_midi_event snd_rawmidi uvcvideo videobuf2_vmalloc videobuf2_memops 
videobuf2_v4l2 videobuf2_core videodev media snd_seq btusb btrtl btbcm 
snd_seq_device btintel snd_timer bluetooth snd soundcore shpchp i2c_piix4 
vmw_vmci nfit floppy(+) mac_hid parport_pc ppdev lp parport ip_tables x_tables 
autofs4 hid_generic usbhid hid psmouse vmwgfx ttm drm_kms_helper syscopyarea 
sysfillrect sysimgblt fb_sys_fops drm ahci libahci e1000 mptspi mptscsih 
mptbase scsi_transport_spi pata_acpi fjes
  CPU: 0 PID: 806 Comm: kidle_inject/0 Not tainted 4.8.0-19-generic #21-Ubuntu
  Hardware name: VMware, Inc. VMware Virtual Platform/440BX Desktop Reference 
Platform, BIOS 6.00 07/02/2015
  task: 9e70f1ce1c80 task.stack: 9e70f679
  RIP: 0010:[]  [] clamp_thread+0x2b8/0x5d0 
[intel_powerclamp]
  RSP: 0018:9e70f6793e00  EFLAGS: 00010246
  RAX: 9e70f6790008 RBX: fffee2fe RCX: 
  RDX:  RSI: 0246 RDI: 0246
  RBP: 9e70f6793ec0 R08: 9e70f679 R09: 
  R10: afb504000afb5041 R11: 9e70fa619ac0 R12: 93958160
  R13: 9e70f679 R14:  R15: 9e70f679
  FS:  () GS:9e70fa60() knlGS:
  CS:  0010 DS:  ES:  CR0: 80050033
  CR2: 7ffd50464ff8 CR3: b89db000 CR4: 001406f0
  Stack:
    0005 c073e5d8 c073ea40
    0003  9e70f6790008
    9e70fa60ff68 fffee2fe c073c0a0
  Call Trace:
   [] ? pkg_state_counter+0xa0/0xa0 [intel_powerclamp]
   [] ? powerclamp_set_cur_state+0x170/0x170 
[intel_powerclamp]
   [] ? powerclamp_set_cur_state+0x170/0x170 
[intel_powerclamp]
   [] kthread+0xd8/0xf0
   [] ret_from_fork+0x1f/0x40
   [] ? kthread_create_on_node+0x1e0/0x1e0
  Code: d2 e9 ba 00 00 00 eb 19 0f 1f 00 0f ae f0 65 48 8b 04 25 04 69 01 00 0f 
ae b8 08 c0 ff ff 0f ae f0 31 d2 48 8b 44 24 38 48 89 d1 <0f> 01 c8 49 8b 45 08 
a8 08 75 0b b9 01 00 00 00 4c 89 f0 0f 01 
  RIP  [] clamp_thread+0x2b8/0x5d0 [intel_powerclamp]
   RSP 
  ---[ end trace fb2ec9f1e269d231 ]---

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

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


[Kernel-packages] [Bug 1630279] kernel02 (s390x.zVM) - tests ran: 2, failed: 0

2016-10-05 Thread Brad Figg
tests ran:   2, failed: 0;
  
http://kernel.ubuntu.com/testing/4.8.0-21.23/kernel02__4.8.0-21.23__2016-10-05_21-35-00/results-index.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/1630279

Title:
  linux: 4.8.0-21.23 -proposed tracker

Status in Kernel Development Workflow:
  In Progress
Status in Kernel Development Workflow automated-testing series:
  New
Status in Kernel Development Workflow prepare-package series:
  Confirmed
Status in Kernel Development Workflow prepare-package-meta series:
  Confirmed
Status in Kernel Development Workflow prepare-package-signed series:
  Confirmed
Status in Kernel Development Workflow promote-to-proposed series:
  New
Status in Kernel Development Workflow promote-to-release series:
  New
Status in Kernel Development Workflow regression-testing series:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Yakkety:
  Confirmed

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

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

  kernel-phase-changed:Tuesday, 04. October 2016 15:16 UTC
  kernel-phase:Packaging

  -- swm properties --
  derivative-trackers-created: true
  phase: Packaging

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-development-workflow/+bug/1630279/+subscriptions

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


[Kernel-packages] [Bug 1630279] kernel02 (s390x.zVM) - tests ran: 64, failed: 1

2016-10-05 Thread Brad Figg
tests ran:  64, failed: 1;
  
http://kernel.ubuntu.com/testing/4.8.0-21.23/kernel02__4.8.0-21.23__2016-10-05_21-38-00/results-index.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/1630279

Title:
  linux: 4.8.0-21.23 -proposed tracker

Status in Kernel Development Workflow:
  In Progress
Status in Kernel Development Workflow automated-testing series:
  New
Status in Kernel Development Workflow prepare-package series:
  Confirmed
Status in Kernel Development Workflow prepare-package-meta series:
  Confirmed
Status in Kernel Development Workflow prepare-package-signed series:
  Confirmed
Status in Kernel Development Workflow promote-to-proposed series:
  New
Status in Kernel Development Workflow promote-to-release series:
  New
Status in Kernel Development Workflow regression-testing series:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Yakkety:
  Confirmed

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

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

  kernel-phase-changed:Tuesday, 04. October 2016 15:16 UTC
  kernel-phase:Packaging

  -- swm properties --
  derivative-trackers-created: true
  phase: Packaging

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-development-workflow/+bug/1630279/+subscriptions

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


[Kernel-packages] [Bug 1630279] s2lp6g002 (s390x.zKVM) - tests ran: 2, failed: 0

2016-10-05 Thread Brad Figg
tests ran:   2, failed: 0;
  
http://kernel.ubuntu.com/testing/4.8.0-21.23/s2lp6g002__4.8.0-21.23__2016-10-05_21-45-00/results-index.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/1630279

Title:
  linux: 4.8.0-21.23 -proposed tracker

Status in Kernel Development Workflow:
  In Progress
Status in Kernel Development Workflow automated-testing series:
  New
Status in Kernel Development Workflow prepare-package series:
  Confirmed
Status in Kernel Development Workflow prepare-package-meta series:
  Confirmed
Status in Kernel Development Workflow prepare-package-signed series:
  Confirmed
Status in Kernel Development Workflow promote-to-proposed series:
  New
Status in Kernel Development Workflow promote-to-release series:
  New
Status in Kernel Development Workflow regression-testing series:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Yakkety:
  Confirmed

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

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

  kernel-phase-changed:Tuesday, 04. October 2016 15:16 UTC
  kernel-phase:Packaging

  -- swm properties --
  derivative-trackers-created: true
  phase: Packaging

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-development-workflow/+bug/1630279/+subscriptions

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


[Kernel-packages] [Bug 1630279] s2lp6g002 (s390x.zKVM) - tests ran: 83, failed: 4

2016-10-05 Thread Brad Figg
tests ran:  83, failed: 4;
  
http://kernel.ubuntu.com/testing/4.8.0-21.23/s2lp6g002__4.8.0-21.23__2016-10-05_21-16-00/results-index.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/1630279

Title:
  linux: 4.8.0-21.23 -proposed tracker

Status in Kernel Development Workflow:
  In Progress
Status in Kernel Development Workflow automated-testing series:
  New
Status in Kernel Development Workflow prepare-package series:
  Confirmed
Status in Kernel Development Workflow prepare-package-meta series:
  Confirmed
Status in Kernel Development Workflow prepare-package-signed series:
  Confirmed
Status in Kernel Development Workflow promote-to-proposed series:
  New
Status in Kernel Development Workflow promote-to-release series:
  New
Status in Kernel Development Workflow regression-testing series:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Yakkety:
  Confirmed

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

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

  kernel-phase-changed:Tuesday, 04. October 2016 15:16 UTC
  kernel-phase:Packaging

  -- swm properties --
  derivative-trackers-created: true
  phase: Packaging

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-development-workflow/+bug/1630279/+subscriptions

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


[Kernel-packages] [Bug 1630279] kernel02 (s390x.zVM) - tests ran: 83, failed: 5

2016-10-05 Thread Brad Figg
tests ran:  83, failed: 5;
  
http://kernel.ubuntu.com/testing/4.8.0-21.23/kernel02__4.8.0-21.23__2016-10-05_20-50-00/results-index.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/1630279

Title:
  linux: 4.8.0-21.23 -proposed tracker

Status in Kernel Development Workflow:
  In Progress
Status in Kernel Development Workflow automated-testing series:
  New
Status in Kernel Development Workflow prepare-package series:
  Confirmed
Status in Kernel Development Workflow prepare-package-meta series:
  Confirmed
Status in Kernel Development Workflow prepare-package-signed series:
  Confirmed
Status in Kernel Development Workflow promote-to-proposed series:
  New
Status in Kernel Development Workflow promote-to-release series:
  New
Status in Kernel Development Workflow regression-testing series:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Yakkety:
  Confirmed

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

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

  kernel-phase-changed:Tuesday, 04. October 2016 15:16 UTC
  kernel-phase:Packaging

  -- swm properties --
  derivative-trackers-created: true
  phase: Packaging

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-development-workflow/+bug/1630279/+subscriptions

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


[Kernel-packages] [Bug 1630774] [NEW] kernel invalid opcode in intel_powerclamp

2016-10-05 Thread Vinson Lee
Public bug reported:

kernel error on VMware Fusion when booting to graphical login


invalid opcode:  [#1] SMP
Modules linked in: ipmi_msghandler intel_powerclamp coretemp crct10dif_pclmul 
crc32_pclmul ghash_clmulni_intel vmw_balloon aesni_intel aes_x86_64 lrw 
glue_helper ablk_helper cryptd intel_rapl_perf joydev input_leds serio_raw 
snd_ens1371 snd_ac97_codec gameport ac97_bus snd_pcm binfmt_misc snd_seq_midi 
snd_seq_midi_event snd_rawmidi uvcvideo videobuf2_vmalloc videobuf2_memops 
videobuf2_v4l2 videobuf2_core videodev media snd_seq btusb btrtl btbcm 
snd_seq_device btintel snd_timer bluetooth snd soundcore shpchp i2c_piix4 
vmw_vmci nfit floppy(+) mac_hid parport_pc ppdev lp parport ip_tables x_tables 
autofs4 hid_generic usbhid hid psmouse vmwgfx ttm drm_kms_helper syscopyarea 
sysfillrect sysimgblt fb_sys_fops drm ahci libahci e1000 mptspi mptscsih 
mptbase scsi_transport_spi pata_acpi fjes
CPU: 0 PID: 806 Comm: kidle_inject/0 Not tainted 4.8.0-19-generic #21-Ubuntu
Hardware name: VMware, Inc. VMware Virtual Platform/440BX Desktop Reference 
Platform, BIOS 6.00 07/02/2015
task: 9e70f1ce1c80 task.stack: 9e70f679
RIP: 0010:[]  [] clamp_thread+0x2b8/0x5d0 
[intel_powerclamp]
RSP: 0018:9e70f6793e00  EFLAGS: 00010246
RAX: 9e70f6790008 RBX: fffee2fe RCX: 
RDX:  RSI: 0246 RDI: 0246
RBP: 9e70f6793ec0 R08: 9e70f679 R09: 
R10: afb504000afb5041 R11: 9e70fa619ac0 R12: 93958160
R13: 9e70f679 R14:  R15: 9e70f679
FS:  () GS:9e70fa60() knlGS:
CS:  0010 DS:  ES:  CR0: 80050033
CR2: 7ffd50464ff8 CR3: b89db000 CR4: 001406f0
Stack:
  0005 c073e5d8 c073ea40
  0003  9e70f6790008
  9e70fa60ff68 fffee2fe c073c0a0
Call Trace:
 [] ? pkg_state_counter+0xa0/0xa0 [intel_powerclamp]
 [] ? powerclamp_set_cur_state+0x170/0x170 [intel_powerclamp]
 [] ? powerclamp_set_cur_state+0x170/0x170 [intel_powerclamp]
 [] kthread+0xd8/0xf0
 [] ret_from_fork+0x1f/0x40
 [] ? kthread_create_on_node+0x1e0/0x1e0
Code: d2 e9 ba 00 00 00 eb 19 0f 1f 00 0f ae f0 65 48 8b 04 25 04 69 01 00 0f 
ae b8 08 c0 ff ff 0f ae f0 31 d2 48 8b 44 24 38 48 89 d1 <0f> 01 c8 49 8b 45 08 
a8 08 75 0b b9 01 00 00 00 4c 89 f0 0f 01 
RIP  [] clamp_thread+0x2b8/0x5d0 [intel_powerclamp]
 RSP 
---[ end trace fb2ec9f1e269d231 ]---

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

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

Title:
  kernel invalid opcode in intel_powerclamp

Status in linux package in Ubuntu:
  New

Bug description:
  kernel error on VMware Fusion when booting to graphical login

  
  invalid opcode:  [#1] SMP
  Modules linked in: ipmi_msghandler intel_powerclamp coretemp crct10dif_pclmul 
crc32_pclmul ghash_clmulni_intel vmw_balloon aesni_intel aes_x86_64 lrw 
glue_helper ablk_helper cryptd intel_rapl_perf joydev input_leds serio_raw 
snd_ens1371 snd_ac97_codec gameport ac97_bus snd_pcm binfmt_misc snd_seq_midi 
snd_seq_midi_event snd_rawmidi uvcvideo videobuf2_vmalloc videobuf2_memops 
videobuf2_v4l2 videobuf2_core videodev media snd_seq btusb btrtl btbcm 
snd_seq_device btintel snd_timer bluetooth snd soundcore shpchp i2c_piix4 
vmw_vmci nfit floppy(+) mac_hid parport_pc ppdev lp parport ip_tables x_tables 
autofs4 hid_generic usbhid hid psmouse vmwgfx ttm drm_kms_helper syscopyarea 
sysfillrect sysimgblt fb_sys_fops drm ahci libahci e1000 mptspi mptscsih 
mptbase scsi_transport_spi pata_acpi fjes
  CPU: 0 PID: 806 Comm: kidle_inject/0 Not tainted 4.8.0-19-generic #21-Ubuntu
  Hardware name: VMware, Inc. VMware Virtual Platform/440BX Desktop Reference 
Platform, BIOS 6.00 07/02/2015
  task: 9e70f1ce1c80 task.stack: 9e70f679
  RIP: 0010:[]  [] clamp_thread+0x2b8/0x5d0 
[intel_powerclamp]
  RSP: 0018:9e70f6793e00  EFLAGS: 00010246
  RAX: 9e70f6790008 RBX: fffee2fe RCX: 
  RDX:  RSI: 0246 RDI: 0246
  RBP: 9e70f6793ec0 R08: 9e70f679 R09: 
  R10: afb504000afb5041 R11: 9e70fa619ac0 R12: 93958160
  R13: 9e70f679 R14:  R15: 9e70f679
  FS:  () GS:9e70fa60() knlGS:
  CS:  0010 DS:  ES:  CR0: 80050033
  CR2: 7ffd50464ff8 CR3: b89db000 CR4: 001406f0
  Stack:
    0005 c073e5d8 c073ea40
    0003  9e70f6790008
    9e70fa60ff68 fffee2fe c073c0a0
  Call Trace:
   [] ? 

[Kernel-packages] [Bug 1630663] Re: suspend/standby hangs in linux 4.4.0 amd64

2016-10-05 Thread Matt
** Tags added: kernel-bug-exists-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/1630663

Title:
  suspend/standby hangs in linux 4.4.0 amd64

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Suspend/Standby worked fine previously under i386 packages, but after
  cross-migrating to amd64, system just hangs and i have to do a hard
  power off (hold power button for 5 seconds).

  i saw notes for #1574125
  (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1574125) where
  people were asked to run `ubuntu-bug linux` so i'm throwing my hat in
  here too.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-38-generic 4.4.0-38.57
  ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
  Uname: Linux 4.4.0-38-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  matt   2675 F pulseaudio
  CurrentDesktop: XFCE
  Date: Wed Oct  5 12:06:58 2016
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=8e82784b-cfa3-4bba-80da-b5f41edcc3f9
  InstallationDate: Installed on 2015-12-01 (308 days ago)
  InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release i386 (20151021)
  MachineType: Hewlett-Packard HP Pavilion dv6500 Notebook PC
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-38-generic 
root=UUID=876adde4-2234-4aa2-9c31-88e8435400d6 ro
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-38-generic N/A
   linux-backports-modules-4.4.0-38-generic  N/A
   linux-firmware1.157.3
  SourcePackage: linux
  UpgradeStatus: Upgraded to xenial on 2016-04-22 (166 days ago)
  dmi.bios.date: 11/25/2008
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: F.59
  dmi.board.name: 30CC
  dmi.board.vendor: Quanta
  dmi.board.version: 79.2E
  dmi.chassis.type: 10
  dmi.chassis.vendor: Quanta
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.59:bd11/25/2008:svnHewlett-Packard:pnHPPaviliondv6500NotebookPC:pvrRev1:rvnQuanta:rn30CC:rvr79.2E:cvnQuanta:ct10:cvrN/A:
  dmi.product.name: HP Pavilion dv6500 Notebook PC
  dmi.product.version: Rev 1
  dmi.sys.vendor: Hewlett-Packard

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

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


[Kernel-packages] [Bug 1625805] Re: arm64 kernel panic for l2 mmu with unity8 session snap

2016-10-05 Thread kevin gunn
@ppisati - didi you need anything else?

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

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

Title:
  arm64 kernel panic for l2 mmu with unity8 session snap

Status in Snappy:
  New
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  we are running the unity8 session snap on amd64 without any problems.
  to setup and reproduce the problem follow the "on Dragonboard" section of 
  
https://docs.google.com/document/d/1o-jKITqUxRsujmN3OwRj3wRnn6dgblKuvrhKjeN8-Wc

  You can also find the panic signature at line 3276 of the attached
  syslog.

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

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


[Kernel-packages] [Bug 1630279] s2lp6g002 (s390x.zKVM) - tests ran: 136, failed: 27

2016-10-05 Thread Brad Figg
tests ran: 136, failed: 27;
  
http://kernel.ubuntu.com/testing/4.8.0-21.23/s2lp6g002__4.8.0-21.23__2016-10-05_20-53-00/results-index.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/1630279

Title:
  linux: 4.8.0-21.23 -proposed tracker

Status in Kernel Development Workflow:
  In Progress
Status in Kernel Development Workflow automated-testing series:
  New
Status in Kernel Development Workflow prepare-package series:
  Confirmed
Status in Kernel Development Workflow prepare-package-meta series:
  Confirmed
Status in Kernel Development Workflow prepare-package-signed series:
  Confirmed
Status in Kernel Development Workflow promote-to-proposed series:
  New
Status in Kernel Development Workflow promote-to-release series:
  New
Status in Kernel Development Workflow regression-testing series:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Yakkety:
  Confirmed

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

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

  kernel-phase-changed:Tuesday, 04. October 2016 15:16 UTC
  kernel-phase:Packaging

  -- swm properties --
  derivative-trackers-created: true
  phase: Packaging

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-development-workflow/+bug/1630279/+subscriptions

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


[Kernel-packages] [Bug 1630279] kernel02 (s390x.zVM) - tests ran: 136, failed: 135

2016-10-05 Thread Brad Figg
tests ran: 136, failed: 135;
  
http://kernel.ubuntu.com/testing/4.8.0-21.23/kernel02__4.8.0-21.23__2016-10-05_20-43-00/results-index.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/1630279

Title:
  linux: 4.8.0-21.23 -proposed tracker

Status in Kernel Development Workflow:
  In Progress
Status in Kernel Development Workflow automated-testing series:
  New
Status in Kernel Development Workflow prepare-package series:
  Confirmed
Status in Kernel Development Workflow prepare-package-meta series:
  Confirmed
Status in Kernel Development Workflow prepare-package-signed series:
  Confirmed
Status in Kernel Development Workflow promote-to-proposed series:
  New
Status in Kernel Development Workflow promote-to-release series:
  New
Status in Kernel Development Workflow regression-testing series:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Yakkety:
  Confirmed

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

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

  kernel-phase-changed:Tuesday, 04. October 2016 15:16 UTC
  kernel-phase:Packaging

  -- swm properties --
  derivative-trackers-created: true
  phase: Packaging

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-development-workflow/+bug/1630279/+subscriptions

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


[Kernel-packages] [Bug 1630279] s2lp6g002 (s390x.zKVM) - tests ran: 19, failed: 7

2016-10-05 Thread Brad Figg
tests ran:  19, failed: 7;
  
http://kernel.ubuntu.com/testing/4.8.0-21.23/s2lp6g002__4.8.0-21.23__2016-10-05_20-32-00/results-index.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/1630279

Title:
  linux: 4.8.0-21.23 -proposed tracker

Status in Kernel Development Workflow:
  In Progress
Status in Kernel Development Workflow automated-testing series:
  New
Status in Kernel Development Workflow prepare-package series:
  Confirmed
Status in Kernel Development Workflow prepare-package-meta series:
  Confirmed
Status in Kernel Development Workflow prepare-package-signed series:
  Confirmed
Status in Kernel Development Workflow promote-to-proposed series:
  New
Status in Kernel Development Workflow promote-to-release series:
  New
Status in Kernel Development Workflow regression-testing series:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Yakkety:
  Confirmed

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

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

  kernel-phase-changed:Tuesday, 04. October 2016 15:16 UTC
  kernel-phase:Packaging

  -- swm properties --
  derivative-trackers-created: true
  phase: Packaging

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-development-workflow/+bug/1630279/+subscriptions

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


[Kernel-packages] [Bug 1630279] kernel02 (s390x.zVM) - tests ran: 19, failed: 8

2016-10-05 Thread Brad Figg
tests ran:  19, failed: 8;
  
http://kernel.ubuntu.com/testing/4.8.0-21.23/kernel02__4.8.0-21.23__2016-10-05_20-31-00/results-index.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/1630279

Title:
  linux: 4.8.0-21.23 -proposed tracker

Status in Kernel Development Workflow:
  In Progress
Status in Kernel Development Workflow automated-testing series:
  New
Status in Kernel Development Workflow prepare-package series:
  Confirmed
Status in Kernel Development Workflow prepare-package-meta series:
  Confirmed
Status in Kernel Development Workflow prepare-package-signed series:
  Confirmed
Status in Kernel Development Workflow promote-to-proposed series:
  New
Status in Kernel Development Workflow promote-to-release series:
  New
Status in Kernel Development Workflow regression-testing series:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Yakkety:
  Confirmed

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

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

  kernel-phase-changed:Tuesday, 04. October 2016 15:16 UTC
  kernel-phase:Packaging

  -- swm properties --
  derivative-trackers-created: true
  phase: Packaging

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-development-workflow/+bug/1630279/+subscriptions

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


[Kernel-packages] [Bug 1629960] Re: Suspend Fails

2016-10-05 Thread Robert Venters
Thanks Joseph!  Unfortunately (and so very frustratingly), I'm not able
to replicate the issue at this time.  My machine had been impacted
through all of last week and, as of testing further today, my machine is
suspending successfully.

I'm not familiar with updating the status under this condition, so
please change as appropriate.  If the issue continues, I'll install the
upstream kernel and test further prior to providing further feedback.

-Robert

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

Title:
  Suspend Fails

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  When putting the system to suspend, the following occurs:
  - All monitors go to sleep
  - System activity stops (HDD, network, etc.)
  - System stays powered on and does not suspend (power light, fans, etc.)

  No keystrokes have been found to recover from this state.  Ultimately,
  the system needs to be rebooted.  Holding the power button to kill the
  system, then reboot, seems to be the only resolution.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-38-generic 4.4.0-38.57
  ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
  Uname: Linux 4.4.0-38-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ro1r2n22865 F pulseaudio
   /dev/snd/controlC2:  ro1r2n22865 F pulseaudio
   /dev/snd/controlC1:  ro1r2n22865 F pulseaudio
  Date: Mon Oct  3 11:09:35 2016
  HibernationDevice: RESUME=/dev/mapper/crypt-swap_1
  InstallationDate: Installed on 2016-06-16 (108 days ago)
  InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.3)
  MachineType: Dell Inc. Latitude E5440
  ProcEnviron:
   LANGUAGE=en_US:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-38-generic 
root=/dev/mapper/crypt-root ro quiet splash vt.handoff=7
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-38-generic N/A
   linux-backports-modules-4.4.0-38-generic  N/A
   linux-firmware1.157.3
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/02/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A13
  dmi.board.asset.tag: 217469
  dmi.board.name: 05JPFR
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.asset.tag: 217469
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA13:bd09/02/2015:svnDellInc.:pnLatitudeE5440:pvr00:rvnDellInc.:rn05JPFR:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E5440
  dmi.product.version: 00
  dmi.sys.vendor: Dell Inc.

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

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


[Kernel-packages] [Bug 1630279] s2lp6g002 (s390x.zKVM) - tests ran: 32, failed: 1

2016-10-05 Thread Brad Figg
tests ran:  32, failed: 1;
  
http://kernel.ubuntu.com/testing/4.8.0-21.23/s2lp6g002__4.8.0-21.23__2016-10-05_19-52-00/results-index.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/1630279

Title:
  linux: 4.8.0-21.23 -proposed tracker

Status in Kernel Development Workflow:
  In Progress
Status in Kernel Development Workflow automated-testing series:
  New
Status in Kernel Development Workflow prepare-package series:
  Confirmed
Status in Kernel Development Workflow prepare-package-meta series:
  Confirmed
Status in Kernel Development Workflow prepare-package-signed series:
  Confirmed
Status in Kernel Development Workflow promote-to-proposed series:
  New
Status in Kernel Development Workflow promote-to-release series:
  New
Status in Kernel Development Workflow regression-testing series:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Yakkety:
  Confirmed

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

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

  kernel-phase-changed:Tuesday, 04. October 2016 15:16 UTC
  kernel-phase:Packaging

  -- swm properties --
  derivative-trackers-created: true
  phase: Packaging

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-development-workflow/+bug/1630279/+subscriptions

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


[Kernel-packages] [Bug 1630279] kernel02 (s390x.zVM) - tests ran: 32, failed: 5

2016-10-05 Thread Brad Figg
tests ran:  32, failed: 5;
  
http://kernel.ubuntu.com/testing/4.8.0-21.23/kernel02__4.8.0-21.23__2016-10-05_19-35-00/results-index.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/1630279

Title:
  linux: 4.8.0-21.23 -proposed tracker

Status in Kernel Development Workflow:
  In Progress
Status in Kernel Development Workflow automated-testing series:
  New
Status in Kernel Development Workflow prepare-package series:
  Confirmed
Status in Kernel Development Workflow prepare-package-meta series:
  Confirmed
Status in Kernel Development Workflow prepare-package-signed series:
  Confirmed
Status in Kernel Development Workflow promote-to-proposed series:
  New
Status in Kernel Development Workflow promote-to-release series:
  New
Status in Kernel Development Workflow regression-testing series:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Yakkety:
  Confirmed

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

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

  kernel-phase-changed:Tuesday, 04. October 2016 15:16 UTC
  kernel-phase:Packaging

  -- swm properties --
  derivative-trackers-created: true
  phase: Packaging

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-development-workflow/+bug/1630279/+subscriptions

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


[Kernel-packages] [Bug 1602577] Re: [arm64] compute nodes unstable after upgrading from 4.2 to 4.4 kernel

2016-10-05 Thread Martin Pitt
My lxd-armhf1 node that is supposedly running on 4.4.23-040423-generic
(on the compute host) has worked fine for the last 13 hours.

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

Title:
  [arm64] compute nodes unstable after upgrading from 4.2 to 4.4 kernel

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

Bug description:
  Hi,

  In order to investigate bug LP#1531768, we upgraded some arm64 compute
  nodes (swirlices) to a 4.4 kernel. I think it made the VMs work
  better, but the hosts became extremely unstable.

  After some time, getting a shell on them would be impossible.
  Connecting on the VSP, you'd get a prompt, and once you typed your
  username and password, you'd see the motd but the shell would never
  spawn.

  Because of these instability issues, all the arm64 compute nodes are
  now back on 4.2. However, we managed to capture "perf record" data
  when a host was failing. I'll attach it to the bug. Perhaps it will
  give you hints as to what we can do to help you troubleshoot this bug
  further.

  Once we have your instructions, we'll happily reboot one (or a few)
  nodes to 4.4 to continue troubleshooting.

  Thanks !
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jul 12 12:54 seq
   crw-rw 1 root audio 116, 33 Jul 12 12:54 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: arm64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: Error: [Errno 2] No such file or directory
  DistroRelease: Ubuntu 14.04
  Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize 
libusb: -99
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: console=ttyS0,9600n8r ro compat_uts_machine=armv7l
  ProcVersionSignature: Ubuntu 4.2.0-41.48~14.04.1-generic 4.2.8-ckt11
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-41-generic N/A
   linux-backports-modules-4.2.0-41-generic  N/A
   linux-firmware1.127.22
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  trusty uec-images
  Uname: Linux 4.2.0-41-generic aarch64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True

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

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


[Kernel-packages] [Bug 1630279] modoc (ppc64el) - tests ran: 2, failed: 1

2016-10-05 Thread Brad Figg
tests ran:   2, failed: 1;
  
http://kernel.ubuntu.com/testing/4.8.0-21.23/modoc__4.8.0-21.23__2016-10-05_19-37-00/results-index.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/1630279

Title:
  linux: 4.8.0-21.23 -proposed tracker

Status in Kernel Development Workflow:
  In Progress
Status in Kernel Development Workflow automated-testing series:
  New
Status in Kernel Development Workflow prepare-package series:
  Confirmed
Status in Kernel Development Workflow prepare-package-meta series:
  Confirmed
Status in Kernel Development Workflow prepare-package-signed series:
  Confirmed
Status in Kernel Development Workflow promote-to-proposed series:
  New
Status in Kernel Development Workflow promote-to-release series:
  New
Status in Kernel Development Workflow regression-testing series:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Yakkety:
  Confirmed

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

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

  kernel-phase-changed:Tuesday, 04. October 2016 15:16 UTC
  kernel-phase:Packaging

  -- swm properties --
  derivative-trackers-created: true
  phase: Packaging

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-development-workflow/+bug/1630279/+subscriptions

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


[Kernel-packages] [Bug 1630279] onza (i386) - tests ran: 10, failed: 1

2016-10-05 Thread Brad Figg
tests ran:  10, failed: 1;
  
http://kernel.ubuntu.com/testing/4.8.0-21.23/onza__4.8.0-21.23__2016-10-05_18-39-00/results-index.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/1630279

Title:
  linux: 4.8.0-21.23 -proposed tracker

Status in Kernel Development Workflow:
  In Progress
Status in Kernel Development Workflow automated-testing series:
  New
Status in Kernel Development Workflow prepare-package series:
  Confirmed
Status in Kernel Development Workflow prepare-package-meta series:
  Confirmed
Status in Kernel Development Workflow prepare-package-signed series:
  Confirmed
Status in Kernel Development Workflow promote-to-proposed series:
  New
Status in Kernel Development Workflow promote-to-release series:
  New
Status in Kernel Development Workflow regression-testing series:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Yakkety:
  Confirmed

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

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

  kernel-phase-changed:Tuesday, 04. October 2016 15:16 UTC
  kernel-phase:Packaging

  -- swm properties --
  derivative-trackers-created: true
  phase: Packaging

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-development-workflow/+bug/1630279/+subscriptions

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


[Kernel-packages] [Bug 1630279] s2lp6g002 (s390x.zKVM) - tests ran: 4, failed: 3

2016-10-05 Thread Brad Figg
tests ran:   4, failed: 3;
  
http://kernel.ubuntu.com/testing/4.8.0-21.23/s2lp6g002__4.8.0-21.23__2016-10-05_18-21-00/results-index.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/1630279

Title:
  linux: 4.8.0-21.23 -proposed tracker

Status in Kernel Development Workflow:
  In Progress
Status in Kernel Development Workflow automated-testing series:
  New
Status in Kernel Development Workflow prepare-package series:
  Confirmed
Status in Kernel Development Workflow prepare-package-meta series:
  Confirmed
Status in Kernel Development Workflow prepare-package-signed series:
  Confirmed
Status in Kernel Development Workflow promote-to-proposed series:
  New
Status in Kernel Development Workflow promote-to-release series:
  New
Status in Kernel Development Workflow regression-testing series:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Yakkety:
  Confirmed

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

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

  kernel-phase-changed:Tuesday, 04. October 2016 15:16 UTC
  kernel-phase:Packaging

  -- swm properties --
  derivative-trackers-created: true
  phase: Packaging

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-development-workflow/+bug/1630279/+subscriptions

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


[Kernel-packages] [Bug 1630279] kernel02 (s390x.zVM) - tests ran: 4, failed: 3

2016-10-05 Thread Brad Figg
tests ran:   4, failed: 3;
  
http://kernel.ubuntu.com/testing/4.8.0-21.23/kernel02__4.8.0-21.23__2016-10-05_18-31-00/results-index.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/1630279

Title:
  linux: 4.8.0-21.23 -proposed tracker

Status in Kernel Development Workflow:
  In Progress
Status in Kernel Development Workflow automated-testing series:
  New
Status in Kernel Development Workflow prepare-package series:
  Confirmed
Status in Kernel Development Workflow prepare-package-meta series:
  Confirmed
Status in Kernel Development Workflow prepare-package-signed series:
  Confirmed
Status in Kernel Development Workflow promote-to-proposed series:
  New
Status in Kernel Development Workflow promote-to-release series:
  New
Status in Kernel Development Workflow regression-testing series:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Yakkety:
  Confirmed

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

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

  kernel-phase-changed:Tuesday, 04. October 2016 15:16 UTC
  kernel-phase:Packaging

  -- swm properties --
  derivative-trackers-created: true
  phase: Packaging

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-development-workflow/+bug/1630279/+subscriptions

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


[Kernel-packages] [Bug 1590590] Re: Touchpad not recognized on Dell Latitude E7470 Ultrabook

2016-10-05 Thread bagl0312
I have the same problem with a new dell latitude e7370

$xinput list

⎡ Virtual core pointer  id=2[master pointer  (3)]
⎜   ↳ Virtual core XTEST pointerid=4[slave  pointer  (2)]
⎜   ↳ ELAN Touchscreen  id=11   [slave  pointer  (2)]
⎜   ↳ ImPS/2 Generic Wheel Mouseid=14   [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)]
↳ Power Button  id=8[slave  keyboard (3)]
↳ Sleep Button  id=9[slave  keyboard (3)]
↳ Integrated_Webcam_HD  id=12   [slave  keyboard (3)]
↳ AT Translated Set 2 keyboard  id=13   [slave  keyboard (3)]
↳ Dell WMI hotkeys  id=15   [slave  keyboard (3)]
↳ DELL Wireless hotkeys id=16   [slave  keyboard (3)]

Ubuntu 16.04

$ uname -a
Linux nbbag7 4.4.0-38-generic #57-Ubuntu SMP Tue Sep 6 15:42:33 UTC 2016 x86_64 
x86_64 x86_64 GNU/Linux

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

Title:
  Touchpad not recognized on Dell Latitude E7470 Ultrabook

Status in linux package in Ubuntu:
  Triaged
Status in xserver-xorg-input-synaptics package in Ubuntu:
  Confirmed

Bug description:
  Expected: Touchpad settings available in Mouse & Touchpad Settings
  dialog

  Actual result: Touchpad settings missing entirely

  
  Details:
  The touchpad on my Dell Ultrabook (Latitude E7470) functions mostly. 

  The settings for the touchpad are not available at all in the Mouse
  and Touchpad settings (see http://i.imgur.com/YRGiOrj.png).

  Two-finger scrolling works as expected except it's using "Natural
  Scrolling" by default and there is no way to change it.

  xinput list does not display a touchpad at all:

  ⎡ Virtual core pointerid=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ ELAN Touchscreenid=11   [slave  pointer 
 (2)]
  ⎜   ↳ ImPS/2 Generic Wheel Mouse  id=13   [slave  pointer 
 (2)]
  ⎣ Virtual core keyboard   id=3[master keyboard (2)]
  ↳ Virtual core XTEST keyboard id=5[slave  
keyboard (3)]
  ↳ Power Buttonid=6[slave  
keyboard (3)]
  ↳ Video Bus   id=7[slave  
keyboard (3)]
  ↳ Power Buttonid=8[slave  
keyboard (3)]
  ↳ Sleep Buttonid=9[slave  
keyboard (3)]
  ↳ Integrated_Webcam_FHD   id=10   [slave  
keyboard (3)]
  ↳ AT Translated Set 2 keyboardid=12   [slave  
keyboard (3)]
  ↳ Dell WMI hotkeysid=14   [slave  
keyboard (3)]
  ↳ DELL Wireless hotkeys   id=15   [slave  
keyboard (3)]

  
  /proc/bus/input/devices lists the device as a "Generic Wheel Mouse"

  Output of `lsb_release -rd`:
  Description:  Ubuntu 16.04 LTS
  Release:  16.04

  xserver-xorg-input-synaptics version information:
  xserver-xorg-input-synaptics:
Installed: 1.8.2-1ubuntu3
Candidate: 1.8.2-1ubuntu3
Version table:
   *** 1.8.2-1ubuntu3 500
  500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status

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

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


[Kernel-packages] [Bug 1630279] dwalin (amd64) - tests ran: 10, failed: 1

2016-10-05 Thread Brad Figg
tests ran:  10, failed: 1;
  
http://kernel.ubuntu.com/testing/4.8.0-21.23/dwalin__4.8.0-21.23__2016-10-05_18-15-00/results-index.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/1630279

Title:
  linux: 4.8.0-21.23 -proposed tracker

Status in Kernel Development Workflow:
  In Progress
Status in Kernel Development Workflow automated-testing series:
  New
Status in Kernel Development Workflow prepare-package series:
  Confirmed
Status in Kernel Development Workflow prepare-package-meta series:
  Confirmed
Status in Kernel Development Workflow prepare-package-signed series:
  Confirmed
Status in Kernel Development Workflow promote-to-proposed series:
  New
Status in Kernel Development Workflow promote-to-release series:
  New
Status in Kernel Development Workflow regression-testing series:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Yakkety:
  Confirmed

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

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

  kernel-phase-changed:Tuesday, 04. October 2016 15:16 UTC
  kernel-phase:Packaging

  -- swm properties --
  derivative-trackers-created: true
  phase: Packaging

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-development-workflow/+bug/1630279/+subscriptions

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


[Kernel-packages] [Bug 1630390] Re: I/O Errors on eMMC Drives during Ubuntu Install

2016-10-05 Thread John
Is there a server daily build?

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

Title:
  I/O Errors on eMMC Drives during Ubuntu Install

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  While attempting to install ubuntu server (16.04.1) on an Intel Atom
  based SoM with integrated eMMC flash for onboard storage (4GB samsung
  flash chip), the install fails towards the end of the package install
  section due to I/O errors by the kernel. Error are similar to the one
  below:

  Buffer I/O error on dev mmcblk0p2, logical block 9914, lost async page
  write

  Obviously I can't produce a log of the exact output since the I/O
  error prevents the log from being written. I can take a screenshot if
  that would be helpful.

  Seems like this is related to Bug # 1422338

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-38-generic 4.4.0-38.57
  ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
  Uname: Linux 4.4.0-38-generic x86_64
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.4.0-38-generic.
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', 
'/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1p', 
'/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer'
  Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer'
  Date: Tue Oct  4 17:45:55 2016
  HibernationDevice: RESUME=UUID=8114b5ee-bc41-438f-8d0d-96ec310e2dce
  InstallationDate: Installed on 2016-10-04 (0 days ago)
  InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 0483:df11 STMicroelectronics STM Device in DFU Mode
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Default string Default string
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-38-generic.efi.signed 
root=UUID=a3bce84b-fbfd-4767-9b05-a0357d6d3329 ro
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-38-generic N/A
   linux-backports-modules-4.4.0-38-generic  N/A
   linux-firmware1.157.3
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/02/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5.11
  dmi.board.asset.tag: Default string
  dmi.board.name: Aptio CRB
  dmi.board.vendor: AMI Corporation
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 2
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5.11:bd09/02/2016:svnDefaultstring:pnDefaultstring:pvrDefaultstring:rvnAMICorporation:rnAptioCRB:rvrDefaultstring:cvnDefaultstring:ct2:cvrDefaultstring:
  dmi.product.name: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Default string

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

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


[Kernel-packages] [Bug 1630279] modoc (ppc64el) - tests ran: 10, failed: 1

2016-10-05 Thread Brad Figg
tests ran:  10, failed: 1;
  
http://kernel.ubuntu.com/testing/4.8.0-21.23/modoc__4.8.0-21.23__2016-10-05_18-30-00/results-index.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/1630279

Title:
  linux: 4.8.0-21.23 -proposed tracker

Status in Kernel Development Workflow:
  In Progress
Status in Kernel Development Workflow automated-testing series:
  New
Status in Kernel Development Workflow prepare-package series:
  Confirmed
Status in Kernel Development Workflow prepare-package-meta series:
  Confirmed
Status in Kernel Development Workflow prepare-package-signed series:
  Confirmed
Status in Kernel Development Workflow promote-to-proposed series:
  New
Status in Kernel Development Workflow promote-to-release series:
  New
Status in Kernel Development Workflow regression-testing series:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Yakkety:
  Confirmed

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

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

  kernel-phase-changed:Tuesday, 04. October 2016 15:16 UTC
  kernel-phase:Packaging

  -- swm properties --
  derivative-trackers-created: true
  phase: Packaging

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-development-workflow/+bug/1630279/+subscriptions

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


[Kernel-packages] [Bug 1626679] Re: NVMe triggering kernel panic followed by "bad: scheduling from the idle thread!"

2016-10-05 Thread Paul Graydon
There isn't a kernel in proposed at the moment, but I've tested using
the latest in yakkety and it seems to be working fine.

I don't have a simple replication case for the bug, unfortunately.  It
just seems to happen for (hand-wavey guess) 50% of boots.

So far I've got this 4.8.0-19-generic kernel to boot several times over
without problem.  I'll keep rebooting and rebooting the server in the
background today, just in case, while I focus on other stuff.

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

Title:
  NVMe triggering kernel panic followed by "bad: scheduling from the
  idle thread!"

Status in linux package in Ubuntu:
  Triaged

Bug description:
  On an NVMe system I'm using, Ubuntu 16.04.1 regularly seems to trigger
  off a kernel panic against somepart of the NVMe driver it looks like,
  after which the logs get filled with entries over and over again of:

  "bad: scheduling from the idle thread!"

  Here's the initial stack trace that seems to trigger off the bug:

  Sep 22 15:51:46 ubuntu kernel: [   97.478175] [ cut here 
]
  Sep 22 15:51:46 ubuntu kernel: [   97.478185] WARNING: CPU: 13 PID: 0 at 
/build/linux-dcxD3m/linux-4.4.0/kernel/irq/manage.c:1438 
__free_irq+0x1d2/0x280()
  Sep 22 15:51:46 ubuntu kernel: [   97.478188] Trying to free IRQ 38 from IRQ 
context!
  Sep 22 15:51:46 ubuntu kernel: [   97.478191] Modules linked in: 
nls_iso8859_1 ipmi_ssif intel_rapl x86_pkg_temp_thermal intel_powerclamp 
coretemp kvm_intel kvm irqbypass ioatdma me
  i_me sb_edac shpchp edac_core lpc_ich mei 8250_fintek ipmi_msghandler mac_hid 
ib_iser rdma_cm iw_cm ib_cm ib_sa ib_mad ib_core ib_addr autofs4 btrfs 
iscsi_tcp libiscsi_tcp libiscsi
  scsi_transport_iscsi raid10 raid456 async_raid6_recov async_memcpy async_pq 
async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear 
crct10dif_pclmul ixgbe crc32_pclmu
  l dca vxlan aesni_intel ip6_udp_tunnel udp_tunnel aes_x86_64 lrw gf128mul ptp 
glue_helper ahci ablk_helper pps_core cryptd nvme libahci mdio wmi fjes
  Sep 22 15:51:46 ubuntu kernel: [   97.478257] CPU: 13 PID: 0 Comm: swapper/13 
Not tainted 4.4.0-31-generic #50-Ubuntu
  Sep 22 15:51:46 ubuntu kernel: [   97.478260] Hardware name: Oracle 
Corporation ORACLE SERVER X5-2/ASM,MOTHERBOARD,1U, BIOS 30080100 04/13/2016
  Sep 22 15:51:46 ubuntu kernel: [   97.478263]  0286 
4fea3140a01056a3 883f7f743b10 813f1143
  Sep 22 15:51:46 ubuntu kernel: [   97.478267]  883f7f743b58 
81cb61f8 883f7f743b48 81081102
  Sep 22 15:51:46 ubuntu kernel: [   97.478271]  0026 
883f5b2ea700 0026 
  Sep 22 15:51:46 ubuntu kernel: [   97.478275] Call Trace:
  Sep 22 15:51:46 ubuntu kernel: [   97.478277][] 
dump_stack+0x63/0x90
  Sep 22 15:51:46 ubuntu kernel: [   97.478290]  [] 
warn_slowpath_common+0x82/0xc0
  Sep 22 15:51:46 ubuntu kernel: [   97.478294]  [] 
warn_slowpath_fmt+0x5c/0x80
  Sep 22 15:51:46 ubuntu kernel: [   97.478299]  [] ? 
try_to_grab_pending+0xb3/0x160
  Sep 22 15:51:46 ubuntu kernel: [   97.478302]  [] 
__free_irq+0x1d2/0x280
  Sep 22 15:51:46 ubuntu kernel: [   97.478306]  [] 
free_irq+0x3c/0x90
  Sep 22 15:51:46 ubuntu kernel: [   97.478314]  [] 
nvme_suspend_queue+0x89/0xb0 [nvme]
  Sep 22 15:51:46 ubuntu kernel: [   97.478320]  [] 
nvme_disable_admin_queue+0x27/0x90 [nvme]
  Sep 22 15:51:46 ubuntu kernel: [   97.478325]  [] 
nvme_dev_disable+0x29e/0x2c0 [nvme]
  Sep 22 15:51:46 ubuntu kernel: [   97.478330]  [] ? 
__nvme_process_cq+0x210/0x210 [nvme]
  Sep 22 15:51:46 ubuntu kernel: [   97.478334]  [] ? 
dev_warn+0x6c/0x90
  Sep 22 15:51:46 ubuntu kernel: [   97.478340]  [] 
nvme_timeout+0x110/0x1d0 [nvme]
  Sep 22 15:51:46 ubuntu kernel: [   97.478344]  [] ? 
cpumask_next_and+0x2f/0x40
  Sep 22 15:51:46 ubuntu kernel: [   97.478348]  [] ? 
load_balance+0x18c/0x980
  Sep 22 15:51:46 ubuntu kernel: [   97.478354]  [] 
blk_mq_rq_timed_out+0x2f/0x70
  Sep 22 15:51:46 ubuntu kernel: [   97.478358]  [] 
blk_mq_check_expired+0x4e/0x80
  Sep 22 15:51:46 ubuntu kernel: [   97.478363]  [] 
bt_for_each+0xd8/0xe0
  Sep 22 15:51:46 ubuntu kernel: [   97.478367]  [] ? 
blk_mq_rq_timed_out+0x70/0x70
  Sep 22 15:51:46 ubuntu kernel: [   97.478370]  [] ? 
blk_mq_rq_timed_out+0x70/0x70
  Sep 22 15:51:46 ubuntu kernel: [   97.478375]  [] 
blk_mq_queue_tag_busy_iter+0x47/0xc0
  Sep 22 15:51:46 ubuntu kernel: [   97.478379]  [] ? 
blk_mq_attempt_merge+0xb0/0xb0
  Sep 22 15:51:46 ubuntu kernel: [   97.478383]  [] 
blk_mq_rq_timer+0x41/0xf0
  Sep 22 15:51:46 ubuntu kernel: [   97.478389]  [] 
call_timer_fn+0x35/0x120
  Sep 22 15:51:46 ubuntu kernel: [   97.478393]  [] ? 
blk_mq_attempt_merge+0xb0/0xb0
  Sep 22 15:51:46 ubuntu kernel: [   97.478397]  [] 
run_timer_softirq+0x23a/0x2f0
  Sep 22 15:51:46 ubuntu kernel: [   97.478403]  [] 
__do_softirq+0x101/0x290
  Sep 22 

[Kernel-packages] [Bug 1626983] Re: [Ubuntu16.10]KV4.8: kernel livepatch config options are not set

2016-10-05 Thread bugproxy
** Tags added: bugnameltc-146670 severity-critical

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

Title:
  [Ubuntu16.10]KV4.8: kernel livepatch config options are not set

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

Bug description:
  ---Problem Description---
  Kernel LivePatch config options are not set
   
  ---uname output---
  Linux HostName 4.8.0-11-generic #12-Ubuntu SMP Sat Sep 17 19:58:16 UTC 2016 
ppc64le ppc64le ppc64le GNU/Linux
   
  Machine Type = 8348-21C 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   Check for the following config options in the config file of 4.8.0 kernel 
version.
  CONFIG_HAVE_LIVEPATCH=Y
  CONFIG_LIVEPATCH=Y

  # grep LIVEPATCH /boot/config-4.8.0-11-generic
  #
   
  Contact Information = nasas...@in.ibm.com 
   
  Stack trace output:
   no
   
  Oops output:
   no
   
  System Dump Info:
The system is not configured to capture a system dump.
   
  *Additional Instructions for nasas...@in.ibm.com: 
  -Attach sysctl -a output output to the bug.

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

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


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

2016-10-05 Thread bugproxy
--- Comment From hbath...@in.ibm.com 2016-10-05 14:49 EDT---
(In reply to comment #29)
> Hello Hari,
>
> It seems that there is another issue now, correct? Should we open a new
> defect for it, or, just track it here? I think that Canonical's action is
> not clear at this moment.

Hi Breno,

There is a bug opened already for the makedumpfile issue (Bug 146571 / LP Bug 
1626269)
Praveen mentioned. This issue can be considered resolved/verified.

Thanks
Hari

--- Comment From hbath...@in.ibm.com 2016-10-05 14:53 EDT---
Based on (In reply to comment #30)
> (In reply to comment #29)
> > Hello Hari,
> >
> > It seems that there is another issue now, correct? Should we open a new
> > defect for it, or, just track it here? I think that Canonical's action is
> > not clear at this moment.
>
> Hi Breno,
>
> There is a bug opened already for the makedumpfile issue (Bug 146571 / LP
> Bug 1626269)
> Praveen mentioned. This issue can be considered resolved/verified.

as the fix patches are in 4.8-rc3 and 16.10 is now based on 4.8, the fixes
must be in...

>
> Thanks
> Hari

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

Title:
  In Ubuntu16.10:Fadump fails as Kernel panic reported while
  dumping-,console got hung on 32TB Brazos System (kdump)

Status in linux package in Ubuntu:
  Triaged

Bug description:
  == Comment: #0 - Praveen K. Pandey  - 2016-07-17 
02:37:31 ==
  Hi 

   In Ubuntu16.10 I  I tried fadump in Brazos system (32TB Memory and
  192 core) , when trigger panic in kernel panic occur and console got
  hung.

  Reproducible Step:

  1- Install Ubuntu16.10
  2- boot system with 31TB and 192 Core 
  3- configure fadump in system 
  4- verify fadump in system that it is running 
  5- Trigger panic in system

  Actual Result

  Not able  to take Fadump , kernel panic and console got hung

  Expected Result

  Fadump will be captured

  Log:

  root@ltc-brazos1:~# kdump-config show
  DUMP_MODE:fadump
  USE_KDUMP:1
  KDUMP_SYSCTL: kernel.panic_on_oops=1
  KDUMP_COREDIR:/var/crash
 /var/lib/kdump/vmlinuz: symbolic link to /boot/vmlinux-4.4.0-30-generic
  kdump initrd: 
 /var/lib/kdump/initrd.img: symbolic link to 
/var/lib/kdump/initrd.img-4.4.0-30-generic
  current state:ready to fadump
  root@ltc-brazos1:~# 

  root@ltc-brazos1:~# cat /proc/cmdline 
  BOOT_IMAGE=/boot/vmlinux-4.4.0-30-generic 
root=UUID=516c4b1b-6700-4b55-bd37-d61c4c5af6af ro quiet splash fadump=on 
fadump_reserve_mem=4096M crashkernel=4096M
  root@ltc-brazos1:~# 

  ltc-brazos1 login: [  442.749993] sysrq: SysRq : Trigger a crash  

  
  [  442.750031] Unable to handle kernel paging request for data at address 
0x  
  
  [  442.750037] Faulting instruction address: 0xc0670014   

  
  [  442.750043] Oops: Kernel access of bad area, sig: 11 [#1]  

  
  [  442.750047] SMP NR_CPUS=2048 NUMA pSeries  

  
  [  442.750053] Modules linked in: pseries_rng btrfs xor raid6_pq rtc_generic 
sunrpc autofs4 ses enclosure ipr
   
  [  442.750068] CPU: 157 PID: 403890 Comm: bash Not tainted 4.4.0-30-generic 
#49-Ubuntu  

  [  442.750074] task: c3f97b0af640 ti: c3f97b104000 task.ti: 
c3f97b104000

  [  442.750079] NIP: c0670014 LR: c06710c8 CTR: 
c066ffe0
 
  [  442.750083] REGS: c3f97b107990 TRAP: 0300   Not tainted  
(4.4.0-30-generic)  

  [  442.750088] MSR: 80009033   CR: 2824  
XER: 0001   
 
  [  442.750100] CFAR: c0008468 DAR:  DSISR: 4200 
SOFTE: 1

  GPR00: c06710c8 c3f97b107c10 c15b5d00 0063

  
  GPR04: c1faba749c50 

[Kernel-packages] [Bug 1616107] Re: Kernel oops + system freeze on network-bridge shutdown

2016-10-05 Thread jwiegley
6 weeks later what's the fix for this? I think we can safely assume that
this bug affects everyone using a bridged bnx2x device and 16.04.

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

Title:
  Kernel oops + system freeze on network-bridge shutdown

Status in bridge-utils package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in bridge-utils source package in Xenial:
  Confirmed
Status in linux source package in Xenial:
  Confirmed
Status in bridge-utils source package in Yakkety:
  Confirmed

Bug description:
  A Kernel oops leaves Ubuntu 16.04 unusable when a network bridge is
  brought down on a HPE 530SFP+ 10GBit NIC that uses bnx2x as a driver.
  This error does not appear in Ubuntu 14.04 however.

  The error is reproducible whenever issuing the commands "shutdown",
  "service networking stop" or "brctl delbr br0". Manually creating the
  bridge and subsequently bringing it down results in the same error.

  /var/log/kern.log:
  [...]
  Aug 23 15:09:46 base1 kernel: [  617.996677] device ens1f0 left promiscuous 
mode
  Aug 23 15:09:46 base1 kernel: [  617.996699] br0: port 1(ens1f0) entered 
disabled state
  Aug 23 15:09:46 base1 kernel: [  617.996730] BUG: unable to handle kernel 
NULL pointer dereference at 00d2
  Aug 23 15:09:46 base1 kernel: [  618.008306] IP: [] 
__vlan_flush+0x18/0x60 [bridge]
  Aug 23 15:09:46 base1 kernel: [  618.020549] PGD 10374c0067 PUD 1033927067 
PMD 0
  Aug 23 15:09:46 base1 kernel: [  618.032773] Oops: 0002 [#1] SMP
  Aug 23 15:09:46 base1 kernel: [  618.044434] Modules linked in: nls_iso8859_1 
ipmi_ssif intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel 
kvm irqbypass sb_edac edac_core joydev bridge stp llc input_leds hpilo lpc_ich 
ioatdma ipmi_si ipmi_msghandler shpchp mac_hid acpi_power_meter ib_iser rdma_cm 
iw_cm ib_cm ib_sa ib_mad ib_core ib_addr iscsi_tcp libiscsi_tcp libiscsi 
scsi_transport_iscsi autofs4 btrfs raid10 raid456 async_raid6_recov 
async_memcpy async_pq async_xor async_tx xor raid6_pq raid0 multipath linear 
raid1 hid_generic crct10dif_pclmul crc32_pclmul aesni_intel aes_x86_64 lrw 
gf128mul glue_helper ablk_helper cryptd igb usbhid hid bnx2x dca ahci 
i2c_algo_bit vxlan libahci ip6_udp_tunnel udp_tunnel ptp pps_core mdio 
libcrc32c wmi fjes
  Aug 23 15:09:46 base1 kernel: [  618.058563] CPU: 3 PID: 4049 Comm: brctl Not 
tainted 4.4.0-34-generic #53-Ubuntu
  Aug 23 15:09:46 base1 kernel: [  618.058564] Hardware name: HP ProLiant DL120 
Gen9/ProLiant DL120 Gen9, BIOS P86 05/05/2016
  Aug 23 15:09:46 base1 kernel: [  618.058574] task: 881030676040 ti: 
8810341e4000 task.ti: 8810341e4000
  Aug 23 15:09:46 base1 kernel: [  618.058576] RIP: 0010:[]  
[] __vlan_flush+0x18/0x60 [bridge]
  Aug 23 15:09:46 base1 kernel: [  618.058754] RSP: 0018:8810341e7d68  
EFLAGS: 00010206
  Aug 23 15:09:46 base1 kernel: [  618.058769] RAX:  RBX: 
 RCX: 
  Aug 23 15:09:46 base1 kernel: [  618.058774] RDX: 881038470848 RSI: 
 RDI: 
  Aug 23 15:09:46 base1 kernel: [  618.058775] RBP: 8810341e7d78 R08: 
 R09: 8170d949
  Aug 23 15:09:46 base1 kernel: [  618.058776] R10: ead61340 R11: 
8810329d2c00 R12: 00c0
  Aug 23 15:09:46 base1 kernel: [  618.058777] R13: 881030044000 R14: 
881038470840 R15: 
  Aug 23 15:09:46 base1 kernel: [  618.058782] FS:  7f9aebc94700() 
GS:88107fcc() knlGS:
  Aug 23 15:09:46 base1 kernel: [  618.058789] CS:  0010 DS:  ES:  CR0: 
80050033
  Aug 23 15:09:46 base1 kernel: [  618.058790] CR2: 00d2 CR3: 
00102fe83000 CR4: 001406e0
  Aug 23 15:09:46 base1 kernel: [  618.058802] Stack:
  Aug 23 15:09:46 base1 kernel: [  618.058806]   
8810356a4c00 8810341e7d98 c0489258
  Aug 23 15:09:46 base1 kernel: [  618.058822]  8810356a4c00 
881038470840 8810341e7dc0 c0479bd8
  Aug 23 15:09:46 base1 kernel: [  618.058825]  881038470838 
881038470848 88103847 8810341e7df8
  Aug 23 15:09:46 base1 kernel: [  618.058827] Call Trace:
  Aug 23 15:09:46 base1 kernel: [  618.058863]  [] 
nbp_vlan_flush+0x28/0x65 [bridge]
  Aug 23 15:09:46 base1 kernel: [  618.058870]  [] 
del_nbp+0x98/0x130 [bridge]
  Aug 23 15:09:46 base1 kernel: [  618.058889]  [] 
br_dev_delete+0x42/0xb0 [bridge]
  Aug 23 15:09:46 base1 kernel: [  618.058895]  [] 
br_del_bridge+0x4a/0x70 [bridge]
  Aug 23 15:09:46 base1 kernel: [  618.058911]  [] 
br_ioctl_deviceless_stub+0x153/0x230 [bridge]
  Aug 23 15:09:46 base1 kernel: [  618.058984]  [] ? 
security_file_alloc+0x33/0x50
  Aug 23 15:09:46 base1 kernel: [  618.059095]  [] 
sock_ioctl+0x215/0x290
  Aug 23 15:09:46 base1 kernel: [  618.059121]  [] 

[Kernel-packages] [Bug 1630279] kernel02 (s390x.zVM) - tests ran: 10, failed: 2

2016-10-05 Thread Brad Figg
tests ran:  10, failed: 2;
  
http://kernel.ubuntu.com/testing/4.8.0-21.23/kernel02__4.8.0-21.23__2016-10-05_18-02-00/results-index.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/1630279

Title:
  linux: 4.8.0-21.23 -proposed tracker

Status in Kernel Development Workflow:
  In Progress
Status in Kernel Development Workflow automated-testing series:
  New
Status in Kernel Development Workflow prepare-package series:
  Confirmed
Status in Kernel Development Workflow prepare-package-meta series:
  Confirmed
Status in Kernel Development Workflow prepare-package-signed series:
  Confirmed
Status in Kernel Development Workflow promote-to-proposed series:
  New
Status in Kernel Development Workflow promote-to-release series:
  New
Status in Kernel Development Workflow regression-testing series:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Yakkety:
  Confirmed

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

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

  kernel-phase-changed:Tuesday, 04. October 2016 15:16 UTC
  kernel-phase:Packaging

  -- swm properties --
  derivative-trackers-created: true
  phase: Packaging

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-development-workflow/+bug/1630279/+subscriptions

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


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

2016-10-05 Thread bugproxy
--- Comment From vipar...@in.ibm.com 2016-10-05 14:30 EDT---
Found below patch submitted upstream to enable VFIO KVM device
for powerpc

Subject: KVM: PPC: Finish enabling VFIO KVM device on POWER

Link: https://patchwork.ozlabs.org/patch/655305/

Not accepted upstream yet.

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

Title:
  QEMU throws failure msg while booting guest with SRIOV VF

Status in linux package in Ubuntu:
  New

Bug description:
  == Comment: #10 - VIPIN K. PARASHAR  - 2016-10-04 
02:39:30 ==
  (In reply to comment #9)
  > I took a quick look to this one and also noticed these 2 links:
  > https://bugzilla.redhat.com/show_bug.cgi?id=1237034
  > http://marc.info/?l=linux-kernel=143737274332400=2
  > and it looks like to avoid these message maybe just need to have this in
  > config file:
  > CONFIG_KVM_VFIO=y
  > I think we have that in powerkvm but not in Ubuntu KVM.

  On x86 running Ubuntu 16.04
  ==
  $ lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 16.04.1 LTS
  Release:  16.04
  Codename: xenial
  $ head /proc/cpuinfo 
  processor : 0
  vendor_id : GenuineIntel
  cpu family: 6
  model : 61
  model name: Intel(R) Core(TM) i5-5300U CPU @ 2.30GHz
  stepping  : 4
  microcode : 0x22
  cpu MHz   : 2300.179
  cache size: 3072 KB
  physical id   : 0
  $ uname -a
  Linux Workstation 4.4.0-38-generic #57-Ubuntu SMP Tue Sep 6 15:42:33 UTC 2016 
x86_64 x86_64 x86_64 GNU/Linux
  $ grep CONFIG_KVM_VFIO /boot/config-4.4.0-38-generic 
  CONFIG_KVM_VFIO=y
  $

  On PowerPC
   
  # lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu Yakkety Yak (development branch)
  Release:  16.10
  Codename: yakkety
  # head /proc/cpuinfo
  processor : 0
  cpu   : POWER8E (raw), altivec supported
  clock : 2061.00MHz
  revision  : 2.1 (pvr 004b 0201)

  processor : 1
  cpu   : POWER8E (raw), altivec supported
  clock : 2061.00MHz
  revision  : 2.1 (pvr 004b 0201)

  # uname -a
  Linux c158f2u09os 4.8.0-17-generic #19 SMP Thu Sep 29 12:03:21 CDT 2016 
ppc64le ppc64le ppc64le GNU/Linux
  # grep CONFIG_KVM_VFIO /boot/config-4.8.0-17-generic 
  #

  I see that CONFIG_KVM_VFIO is enabled on x86 running Ubuntu 16.04
  while ppc64 running 16.10 doesn't have it enabled.

  == Comment: #9 - Carol L. Soto  - 2016-09-30 16:25:32 ==
  I took a quick look to this one and also noticed these 2 links:
  https://bugzilla.redhat.com/show_bug.cgi?id=1237034
  http://marc.info/?l=linux-kernel=143737274332400=2
  and it looks like to avoid these message maybe just need to have this in 
config file:
  CONFIG_KVM_VFIO=y
  I think we have that in powerkvm but not in Ubuntu KVM.

  == Comment: #6 - VIPIN K. PARASHAR  - 2016-09-23 
06:50:22 ==
  $ git log 178a787502123b0 -1
  commit 178a787502123b01499c5a4617b94bb69ad49dd5
  Author: David Gibson 
  Date:   Mon Feb 1 11:14:15 2016 +1100

  vfio: Enable VFIO device for powerpc
  
  ec53500f "kvm: Add VFIO device" added a special KVM pseudo-device which is
  used to handle any necessary interactions between KVM and VFIO.
  
  Currently that device is built on x86 and ARM, but not powerpc, although
  powerpc does support both KVM and VFIO.  This makes things awkward in
  userspace
  
  Currently qemu prints an alarming error message if you attempt to use VFIO
  and it can't initialize the KVM VFIO device.  We don't want to remove the
  warning, because lack of the KVM VFIO device could mean coherency problems
  on x86.  On powerpc, however, the error is harmless but looks disturbing,
  and a test based on host architecture in qemu would be ugly, and break if
  we do need the KVM VFIO device for something important in future.
  
  There's nothing preventing the KVM VFIO device from being built for
  powerpc, so this patch turns it on.  It won't actually do anything, since
  we don't define any of the arch_*() hooks, but it will make qemu happy and
  we can extend it in future if we need to.
  
  Signed-off-by: David Gibson 
  Reviewed-by: Eric Auger 
  Signed-off-by: Paul Mackerras 
  $ 

  $ git describe --contains 178a787502123b
  v4.6-rc1~141^2~49^2~20
  $ 

  
  Commit (178a7875) seems to have enabled VFIO devices for powerpc.
  But this commit should already be available since 4.6 kernel and ubuntu is
  using 4.7 kernel here, so this should be already in.

  
  == Comment: #0 - SRIKANTH B. AITHAL  - 2016-09-15 
12:31:49 ==
  ---Problem Description---
 

[Kernel-packages] [Bug 1619918] Re: lsattr 32bit does not work on 64bit kernel (Inappropriate ioctl error)

2016-10-05 Thread Brad Figg
** Tags removed: verification-needed-vivid verification-needed-xenial
** Tags added: verification-done-vivid verification-done-xenial

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

Title:
  lsattr 32bit does not work on 64bit kernel (Inappropriate ioctl error)

Status in e2fsprogs package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Fix Released
Status in e2fsprogs source package in Trusty:
  Invalid
Status in linux source package in Trusty:
  Triaged
Status in e2fsprogs source package in Vivid:
  Invalid
Status in linux source package in Vivid:
  Fix Committed
Status in e2fsprogs source package in Xenial:
  Invalid
Status in linux source package in Xenial:
  Fix Committed
Status in e2fsprogs source package in Yakkety:
  Invalid
Status in linux source package in Yakkety:
  Fix Released

Bug description:
  I run an amd64 kernel on trusty.  The e2fsprogs package was still the
  32 bit i386 variety.  This lead to the following situation (for
  essentially all files on a btrfs partition).

  $ lsattr 
/lib/modules/3.13.0-95-generic/kernel/drivers/staging/lustre/lustre/ptlrpc/ptlrpc.ko
  lsattr: Inappropriate ioctl for device While reading flags on 
/lib/modules/3.13.0-95-generic/kernel/drivers/staging/lustre/lustre/ptlrpc/ptlrpc.ko

  The problem was resolved by installing e2fsprogs:amd64.

  https://patchwork.kernel.org/patch/7517361/ might be related.

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

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


[Kernel-packages] [Bug 1630279] s2lp6g002 (s390x.zKVM) - tests ran: 10, failed: 2

2016-10-05 Thread Brad Figg
tests ran:  10, failed: 2;
  
http://kernel.ubuntu.com/testing/4.8.0-21.23/s2lp6g002__4.8.0-21.23__2016-10-05_18-02-00/results-index.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/1630279

Title:
  linux: 4.8.0-21.23 -proposed tracker

Status in Kernel Development Workflow:
  In Progress
Status in Kernel Development Workflow automated-testing series:
  New
Status in Kernel Development Workflow prepare-package series:
  Confirmed
Status in Kernel Development Workflow prepare-package-meta series:
  Confirmed
Status in Kernel Development Workflow prepare-package-signed series:
  Confirmed
Status in Kernel Development Workflow promote-to-proposed series:
  New
Status in Kernel Development Workflow promote-to-release series:
  New
Status in Kernel Development Workflow regression-testing series:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Yakkety:
  Confirmed

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

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

  kernel-phase-changed:Tuesday, 04. October 2016 15:16 UTC
  kernel-phase:Packaging

  -- swm properties --
  derivative-trackers-created: true
  phase: Packaging

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-development-workflow/+bug/1630279/+subscriptions

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


[Kernel-packages] [Bug 1627108] Re: X1Carbon comes to a crawl during high CPU usage tasks

2016-10-05 Thread Joseph Salisbury
I built the next test kernel, up to the following commit:
5048c2af078d5976895d521262a8802ea791f3b0

The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1627108

Can you test that kernel and report back if it has the bug or not? I
will build the next test kernel based on your test results.

Thanks in advance

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

Title:
  X1Carbon comes to a crawl during high CPU usage tasks

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

Bug description:
  My X1Carbon becomes quite laggy, the cursor hangs for a few seconds
  and then resumes while my system is compiling some code, or lets says
  PyCharm is indexing things or Android Studio is compiling some code. I
  was using 4.4 on Xenial a few days ago and everything was working just
  fine. Installed Yakkety and this issue happens.

  I will downgrade the kernel and see if that mitigates the issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: linux-image-4.8.0-15-generic 4.8.0-15.16
  ProcVersionSignature: Ubuntu 4.8.0-15.16-generic 4.8.0-rc7
  Uname: Linux 4.8.0-15-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC1D0p:   om26er 3390 F...m pulseaudio
   /dev/snd/controlC1:  om26er 3390 F pulseaudio
   /dev/snd/controlC0:  om26er 3390 F pulseaudio
  CurrentDesktop: Unity
  Date: Fri Sep 23 21:40:34 2016
  HibernationDevice: RESUME=UUID=a92c85ab-cca3-4afc-abf1-3516f193129e
  InstallationDate: Installed on 2016-09-21 (1 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160921)
  MachineType: LENOVO 20BSCTO1WW
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-15-generic.efi.signed 
root=UUID=01b0a4a0-d791-46e8-a212-1f769cff3a4b ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-15-generic N/A
   linux-backports-modules-4.8.0-15-generic  N/A
   linux-firmware1.161
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/13/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N14ET32W (1.10 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20BSCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN14ET32W(1.10):bd08/13/2015:svnLENOVO:pn20BSCTO1WW:pvrThinkPadX1Carbon3rd:rvnLENOVO:rn20BSCTO1WW:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.name: 20BSCTO1WW
  dmi.product.version: ThinkPad X1 Carbon 3rd
  dmi.sys.vendor: LENOVO

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

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


[Kernel-packages] [Bug 1625912] Re: Kernel option usbhid.mousepoll=1 is now ignored

2016-10-05 Thread Joseph Salisbury
Do you happen to recall the last kernel version that did not exhibit
this issue?  We can perform a kernel bisect if we identify the last good
kernel version and the first bad one.

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

Title:
  Kernel option usbhid.mousepoll=1 is now ignored

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Kernel option usbhid.mousepoll=1 is now ignored.

  I can see in /proc/cmdline that I still have usbhid.mousepoll=1 but in
  real testing with Mir clients I'm only getting 125Hz input instead of
  the expected 1000Hz.

  Just a few months ago at least it was working (with the same mouse but
  different PC).

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: linux-image-4.4.0-9136-generic 4.4.0-9136.55
  ProcVersionSignature: Ubuntu 4.4.0-9136.55-generic 4.4.16
  Uname: Linux 4.4.0-9136-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/hwC0D0', 
'/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/controlC0', 
'/dev/snd/by-path', '/dev/snd/hwC1D2', '/dev/snd/pcmC1D2c', 
'/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/controlC1', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Date: Wed Sep 21 11:59:24 2016
  HibernationDevice: RESUME=UUID=14362a37-9d65-44cb-af81-5694ee7c17c1
  InstallationDate: Installed on 2016-07-11 (72 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160710)
  IwConfig:
   lono wireless extensions.
   
   eno1  no wireless extensions.
  MachineType: LENOVO 30AJS05700
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-9136-generic.efi.signed 
root=UUID=81044886-888d-4a06-893c-d740f91759e0 ro quiet splash 
usbhid.mousepoll=1 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.4.0-9136-generic N/A
   linux-backports-modules-4.4.0-9136-generic  N/A
   linux-firmware  1.161
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/02/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: FBKTB6AUS
  dmi.board.name: SHARKBAY
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50519 PRO
  dmi.chassis.type: 7
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnLENOVO:bvrFBKTB6AUS:bd08/02/2015:svnLENOVO:pn30AJS05700:pvrThinkStationP300:rvnLENOVO:rnSHARKBAY:rvrSDK0E50519PRO:cvnToBeFilledByO.E.M.:ct7:cvrToBeFilledByO.E.M.:
  dmi.product.name: 30AJS05700
  dmi.product.version: ThinkStation P300
  dmi.sys.vendor: LENOVO

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

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


[Kernel-packages] [Bug 1627408] Re: Severe graphics regression with mainline kernel v4.7.5 on Broadwell 5500U

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

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

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

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

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

Title:
  Severe graphics regression with mainline kernel v4.7.5 on Broadwell
  5500U

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

Bug description:
  I would like to report a severe graphics regression, involving
  frequent rainbow-glitching and flickering on a x64 computer with Intel
  Broadwell 5500U processor w/ integrated graphics. This issue was not
  present on kernel v4.7.4, which I will continue to use. Due to
  unfortunate issues with Broadwell integrated graphics support,
  virtually every kernel build in the 4.8 release chain as well as the
  newest v4.7.5 kernel have this issue. Dramatic multicolored patches
  and glitched areas appear frequently when using my computer with these
  kernels installed. The behavior is very similar to that of the
  Broadwell graphics issues present in kernel version 4.6.x. Please fix
  this issue, I don't understand why NEWER kernels are actually causing
  significant graphical problems with older hardware.

  I am running Ubuntu 16.04.1 LTS on an HP Spectre x360 4102dx with an Intel
  Broadwell 5500U core i7 processor with integrated intel Broadwell GT2 graphics

  Here is my system configuration:

  H/W path   Device Class  Description
  
system HP Spectre x360 Convertible 
(N5R94UA#ABA)
  /0bus802D
  /0/0  memory 64KiB BIOS
  /0/10 memory 32KiB L1 cache
  /0/11 memory 32KiB L1 cache
  /0/12 memory 256KiB L2 cache
  /0/13 memory 4MiB L3 cache
  /0/14 processor  Intel(R) Core(TM) i7-5500U CPU @ 
2.40GHz
  /0/16 memory 8GiB System Memory
  /0/16/0   memory 4GiB Row of chips Synchronous 1600 
MHz (0.6 ns)
  /0/16/1   memory 4GiB Row of chips Synchronous 1600 
MHz (0.6 ns)
  /0/100bridge Broadwell-U Host Bridge -OPI
  /0/100/2  displayBroadwell-U Integrated Graphics
  /0/100/3  multimedia Broadwell-U Audio Controller
  /0/100/14 busWildcat Point-LP USB xHCI Controller
  /0/100/14/0usb2   busxHCI Host Controller
  /0/100/14/1usb1   busxHCI Host Controller
  /0/100/14/1/1 input  USB Receiver
  /0/100/14/1/3 multimedia HP Truevision Full HD
  /0/100/14/1/4 input  Touchscreen
  /0/100/14/1/5 input  ITE Device(8350)
  /0/100/14/1/7 communication  Bluetooth wireless interface
  /0/100/16 communication  Wildcat Point-LP MEI Controller #1
  /0/100/1b multimedia Wildcat Point-LP High Definition 
Audio Controller
  /0/100/1c bridge Wildcat Point-LP PCI Express Root 
Port #2
  /0/100/1c/0   genericRTS5227 PCI Express Card Reader
  /0/100/1c.2   bridge Wildcat Point-LP PCI Express Root 
Port #3
  /0/100/1c.2/0  wlo1   networkWireless 7265
  /0/100/1f bridge Wildcat Point-LP LPC Controller
  /0/100/1f.2   storageWildcat Point-LP SATA Controller 
[AHCI Mode]
  /0/100/1f.3   busWildcat Point-LP SMBus Controller
  /0/1   scsi0  storage
  /0/1/0.0.0 /dev/sda   disk   512GB SAMSUNG MZNTE512
  /0/1/0.0.0/1   /dev/sda1  volume 449MiB Windows NTFS volume
  /0/1/0.0.0/2   /dev/sda2  volume 98MiB Windows FAT volume
  /0/1/0.0.0/3   /dev/sda3  volume 15MiB reserved partition
  /0/1/0.0.0/4   /dev/sda4  volume 15EiB Windows FAT volume
  /0/1/0.0.0/5   /dev/sda5  volume 807MiB Windows NTFS volume
  /0/1/0.0.0/6   /dev/sda6  volume 97GiB Windows NTFS volume
  /0/1/0.0.0/7   /dev/sda7  volume 89GiB EXT4 volume
  /0/1/0.0.0/8   /dev/sda8  volume 8098MiB Linux swap volume
  /1power  PK03056XL

To manage 

[Kernel-packages] [Bug 1627108] Re: X1Carbon comes to a crawl during high CPU usage tasks

2016-10-05 Thread Omer Akram
Ok, that is a good kernel. My test is `stress -c 4` and it works fine
i.e. system performance does not degrade.

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

Title:
  X1Carbon comes to a crawl during high CPU usage tasks

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

Bug description:
  My X1Carbon becomes quite laggy, the cursor hangs for a few seconds
  and then resumes while my system is compiling some code, or lets says
  PyCharm is indexing things or Android Studio is compiling some code. I
  was using 4.4 on Xenial a few days ago and everything was working just
  fine. Installed Yakkety and this issue happens.

  I will downgrade the kernel and see if that mitigates the issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: linux-image-4.8.0-15-generic 4.8.0-15.16
  ProcVersionSignature: Ubuntu 4.8.0-15.16-generic 4.8.0-rc7
  Uname: Linux 4.8.0-15-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC1D0p:   om26er 3390 F...m pulseaudio
   /dev/snd/controlC1:  om26er 3390 F pulseaudio
   /dev/snd/controlC0:  om26er 3390 F pulseaudio
  CurrentDesktop: Unity
  Date: Fri Sep 23 21:40:34 2016
  HibernationDevice: RESUME=UUID=a92c85ab-cca3-4afc-abf1-3516f193129e
  InstallationDate: Installed on 2016-09-21 (1 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160921)
  MachineType: LENOVO 20BSCTO1WW
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-15-generic.efi.signed 
root=UUID=01b0a4a0-d791-46e8-a212-1f769cff3a4b ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-15-generic N/A
   linux-backports-modules-4.8.0-15-generic  N/A
   linux-firmware1.161
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/13/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N14ET32W (1.10 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20BSCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN14ET32W(1.10):bd08/13/2015:svnLENOVO:pn20BSCTO1WW:pvrThinkPadX1Carbon3rd:rvnLENOVO:rn20BSCTO1WW:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.name: 20BSCTO1WW
  dmi.product.version: ThinkPad X1 Carbon 3rd
  dmi.sys.vendor: LENOVO

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

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


[Kernel-packages] [Bug 1629880] Re: Ubuntu won't launch after the Ubuntu, with Linux 4.4.0-39 generic update

2016-10-05 Thread Joseph Salisbury
So you can boot your system if you select the -38 kernel from the GRUB
menu but not the -39?

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

** Tags added: kernel-da-key

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

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

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

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

Title:
  Ubuntu won't launch after the Ubuntu, with Linux 4.4.0-39 generic
  update

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

Bug description:
  I am running Linux Ubuntu 16.04 LTS, and I've discussed in a thread at
  'Ask Ubuntu: System update almost broke the system' about the Kernel
  Bug — as suggested by a local user boddhi.zazen — that I experienced
  as I was running my system updates. The problem occurs with "Ubuntu,
  with Linux 4.4.0-39 generic", although I am still able to access
  Ubuntu with the older "Ubuntu, with Linux 4.4.0-38 generic" via
  "+Advanced options for Ubuntu".

  Here's what happened:

  1. I first ran the upgrade procedures through terminal as usual: sudo apt-get 
update, sudo apt-get upgrade, sudo apt-get autoremove, and sudo apt-get 
autoremove
  2. However, I was told that "4 not upgraded", so I decided to run Software 
Updater as well, and there was indeed updates available concerning "Ubuntu 
base". I installed those successfully, and decided to proceed with restart my 
system.

  After the restart, my system doesn't start though. Instead, I receive
  the following error message:

  <-- THE BEGINNING, NOT PART OF THE ERROR MESSAGE -->
  [ 1.452270] genirq: Flags mismatch irq 0. 0080 (nvme0q0) vs. 00015a00 
(timer)
  [ 1.452551] iounmap: bad address c90001b88000
  Scanning for Btrfs filesystems
  Gave up waiting for root device. Common problems:
   - Boot args (cat /proc/cmdline)
- Check rootdelay= (did the system wait for the right device?)
- Check root= (did the system wait for the right device?)
   - Missing modules (cat /proc/modules; ls /dev)
  ALERT! UUID=a5ccaf22-ffde-44c2-8c59-84a851f9fd90 does not exist. Dropping to 
shell!

  BusyBox v1.222.1 (Ubuntu 1:1.22.0-15ubuntu1) built-in shell (ash)
  Enter 'help' for a list of built-in commands.

  (initramfs)
  <-- THE END, NOT PART OF THE ERROR MESSAGE -->

  I was able to recover my system through the "+Advanced options for
  Ubuntu", which I opened after. There I had total of nine choices,
  three options for each version. I first tried the "recovery version"
  of the latest one, but it didn't work. After that, I tried the
  "generic version" of the second latest, and — thank God — that one
  managed to recover my system! I believe the package is called linux-
  image-4.4.0-39-generic ("Ubuntu, with Linux 4.4.0-38 generic" in the
  menu")

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: ubuntu-release-upgrader-core 1:16.04.16
  ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
  Uname: Linux 4.4.0-38-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CrashDB: ubuntu
  Date: Mon Oct  3 16:19:33 2016
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: release-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)
  VarLogDistupgradeTermlog:

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

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


[Kernel-packages] [Bug 1630663] Re: suspend/standby hangs in linux 4.4.0 amd64

2016-10-05 Thread Joseph Salisbury
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.8 kernel[0].

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

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

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


Thanks in advance.

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


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

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

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

Title:
  suspend/standby hangs in linux 4.4.0 amd64

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Suspend/Standby worked fine previously under i386 packages, but after
  cross-migrating to amd64, system just hangs and i have to do a hard
  power off (hold power button for 5 seconds).

  i saw notes for #1574125
  (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1574125) where
  people were asked to run `ubuntu-bug linux` so i'm throwing my hat in
  here too.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-38-generic 4.4.0-38.57
  ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
  Uname: Linux 4.4.0-38-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  matt   2675 F pulseaudio
  CurrentDesktop: XFCE
  Date: Wed Oct  5 12:06:58 2016
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=8e82784b-cfa3-4bba-80da-b5f41edcc3f9
  InstallationDate: Installed on 2015-12-01 (308 days ago)
  InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release i386 (20151021)
  MachineType: Hewlett-Packard HP Pavilion dv6500 Notebook PC
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-38-generic 
root=UUID=876adde4-2234-4aa2-9c31-88e8435400d6 ro
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-38-generic N/A
   linux-backports-modules-4.4.0-38-generic  N/A
   linux-firmware1.157.3
  SourcePackage: linux
  UpgradeStatus: Upgraded to xenial on 2016-04-22 (166 days ago)
  dmi.bios.date: 11/25/2008
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: F.59
  dmi.board.name: 30CC
  dmi.board.vendor: Quanta
  dmi.board.version: 79.2E
  dmi.chassis.type: 10
  dmi.chassis.vendor: Quanta
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.59:bd11/25/2008:svnHewlett-Packard:pnHPPaviliondv6500NotebookPC:pvrRev1:rvnQuanta:rn30CC:rvr79.2E:cvnQuanta:ct10:cvrN/A:
  dmi.product.name: HP Pavilion dv6500 Notebook PC
  dmi.product.version: Rev 1
  dmi.sys.vendor: Hewlett-Packard

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

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


[Kernel-packages] [Bug 1630390] Re: I/O Errors on eMMC Drives during Ubuntu Install

2016-10-05 Thread Joseph Salisbury
** Tags added: kernel-da-key

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

Title:
  I/O Errors on eMMC Drives during Ubuntu Install

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  While attempting to install ubuntu server (16.04.1) on an Intel Atom
  based SoM with integrated eMMC flash for onboard storage (4GB samsung
  flash chip), the install fails towards the end of the package install
  section due to I/O errors by the kernel. Error are similar to the one
  below:

  Buffer I/O error on dev mmcblk0p2, logical block 9914, lost async page
  write

  Obviously I can't produce a log of the exact output since the I/O
  error prevents the log from being written. I can take a screenshot if
  that would be helpful.

  Seems like this is related to Bug # 1422338

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-38-generic 4.4.0-38.57
  ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
  Uname: Linux 4.4.0-38-generic x86_64
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.4.0-38-generic.
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', 
'/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1p', 
'/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer'
  Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer'
  Date: Tue Oct  4 17:45:55 2016
  HibernationDevice: RESUME=UUID=8114b5ee-bc41-438f-8d0d-96ec310e2dce
  InstallationDate: Installed on 2016-10-04 (0 days ago)
  InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 0483:df11 STMicroelectronics STM Device in DFU Mode
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Default string Default string
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-38-generic.efi.signed 
root=UUID=a3bce84b-fbfd-4767-9b05-a0357d6d3329 ro
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-38-generic N/A
   linux-backports-modules-4.4.0-38-generic  N/A
   linux-firmware1.157.3
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/02/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5.11
  dmi.board.asset.tag: Default string
  dmi.board.name: Aptio CRB
  dmi.board.vendor: AMI Corporation
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 2
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5.11:bd09/02/2016:svnDefaultstring:pnDefaultstring:pvrDefaultstring:rvnAMICorporation:rnAptioCRB:rvrDefaultstring:cvnDefaultstring:ct2:cvrDefaultstring:
  dmi.product.name: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Default string

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

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


[Kernel-packages] [Bug 1630459] Re: Ralink rt5390 unstable connection on ubuntu 16.04.1

2016-10-05 Thread Joseph Salisbury
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.8 kernel[0].

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

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

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


Thanks in advance.

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


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

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

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

Title:
  Ralink rt5390 unstable connection on ubuntu 16.04.1

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 16.04.1 with all updates. Default kernel, default driver, and
  default NetworkManager setup. Wifi connection drops often and/or
  became slow. I tried disabling NetworkManager and installing Wicd for
  network management. All working ok since then.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-38-generic 4.4.0-38.57
  ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
  Uname: Linux 4.4.0-38-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  julio  1402 F pulseaudio
  CurrentDesktop: Unity
  Date: Wed Oct  5 08:45:26 2016
  InstallationDate: Installed on 2016-10-03 (1 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: Hewlett-Packard HP Pavilion g6 Notebook PC
  ProcEnviron:
   LANGUAGE=es_ES
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=es_ES.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-38-generic 
root=UUID=76af3e82-8ad6-45c9-973b-e711401f288e ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-38-generic N/A
   linux-backports-modules-4.4.0-38-generic  N/A
   linux-firmware1.157.3
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/17/2013
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.24
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 1840
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 56.32
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.24:bd01/17/2013:svnHewlett-Packard:pnHPPaviliong6NotebookPC:pvr07911020561620100:rvnHewlett-Packard:rn1840:rvr56.32:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.name: HP Pavilion g6 Notebook PC
  dmi.product.version: 07911020561620100
  dmi.sys.vendor: Hewlett-Packard

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

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


[Kernel-packages] [Bug 1625788] Re: linux: 3.19.0-70.78 -proposed tracker

2016-10-05 Thread Brad Figg
** Changed in: kernel-sru-workflow/regression-testing
   Status: Confirmed => Fix Released

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

Title:
  linux: 3.19.0-70.78 -proposed tracker

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

Bug description:
  This bug is for tracking the 3.19.0-70.78 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 --
  derivative-trackers-created: 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/1625788/+subscriptions

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


[Kernel-packages] [Bug 1626604] Re: linux: 3.13.0-97.144 -proposed tracker

2016-10-05 Thread Brad Figg
** Tags added: regression-testing-passed

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

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

Title:
  linux: 3.13.0-97.144 -proposed tracker

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

Bug description:
  This bug is for tracking the 3.13.0-97.144 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 --
  derivative-trackers-created: 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/1626604/+subscriptions

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


[Kernel-packages] [Bug 1628204] Re: linux: 4.4.0-41.61 -proposed tracker

2016-10-05 Thread Brad Figg
** Tags added: regression-testing-passed

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

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

Title:
  linux: 4.4.0-41.61 -proposed tracker

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

Bug description:
  This bug is for tracking the 4.4.0-41.61 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
  derivative-trackers-created: 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/1628204/+subscriptions

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


[Kernel-packages] [Bug 1625788] Re: linux: 3.19.0-70.78 -proposed tracker

2016-10-05 Thread Brad Figg
** Tags added: regression-testing-passed

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

Title:
  linux: 3.19.0-70.78 -proposed tracker

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

Bug description:
  This bug is for tracking the 3.19.0-70.78 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 --
  derivative-trackers-created: 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/1625788/+subscriptions

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


[Kernel-packages] [Bug 1629730] onza (amd64) - tests ran: 10, failed: 1

2016-10-05 Thread Brad Figg
tests ran:  10, failed: 1;
  
http://kernel.ubuntu.com/testing/4.8.0-20.22/onza__4.8.0-20.22__2016-10-05_16-02-00/results-index.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/1629730

Title:
  linux: 4.8.0-20.22 -proposed tracker

Status in Kernel Development Workflow:
  In Progress
Status in Kernel Development Workflow automated-testing series:
  New
Status in Kernel Development Workflow prepare-package series:
  Fix Released
Status in Kernel Development Workflow prepare-package-meta series:
  Fix Released
Status in Kernel Development Workflow prepare-package-signed series:
  Fix Released
Status in Kernel Development Workflow promote-to-proposed series:
  Confirmed
Status in Kernel Development Workflow promote-to-release series:
  New
Status in Kernel Development Workflow regression-testing series:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Yakkety:
  Confirmed

Bug description:
  This bug is for tracking the 4.8.0-20.22 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
  derivative-trackers-created: true
  phase: Uploaded

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-development-workflow/+bug/1629730/+subscriptions

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


[Kernel-packages] [Bug 1627108] Re: X1Carbon comes to a crawl during high CPU usage tasks

2016-10-05 Thread Joseph Salisbury
I built the next test kernel, up to the following commit:
52770c37db2c0ee5585dae2de3d19c8453f1e8dc

The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1627108

Can you test that kernel and report back if it has the bug or not? I
will build the next test kernel based on your test results.

Thanks in advance

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

Title:
  X1Carbon comes to a crawl during high CPU usage tasks

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

Bug description:
  My X1Carbon becomes quite laggy, the cursor hangs for a few seconds
  and then resumes while my system is compiling some code, or lets says
  PyCharm is indexing things or Android Studio is compiling some code. I
  was using 4.4 on Xenial a few days ago and everything was working just
  fine. Installed Yakkety and this issue happens.

  I will downgrade the kernel and see if that mitigates the issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: linux-image-4.8.0-15-generic 4.8.0-15.16
  ProcVersionSignature: Ubuntu 4.8.0-15.16-generic 4.8.0-rc7
  Uname: Linux 4.8.0-15-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC1D0p:   om26er 3390 F...m pulseaudio
   /dev/snd/controlC1:  om26er 3390 F pulseaudio
   /dev/snd/controlC0:  om26er 3390 F pulseaudio
  CurrentDesktop: Unity
  Date: Fri Sep 23 21:40:34 2016
  HibernationDevice: RESUME=UUID=a92c85ab-cca3-4afc-abf1-3516f193129e
  InstallationDate: Installed on 2016-09-21 (1 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160921)
  MachineType: LENOVO 20BSCTO1WW
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-15-generic.efi.signed 
root=UUID=01b0a4a0-d791-46e8-a212-1f769cff3a4b ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-15-generic N/A
   linux-backports-modules-4.8.0-15-generic  N/A
   linux-firmware1.161
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/13/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N14ET32W (1.10 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20BSCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN14ET32W(1.10):bd08/13/2015:svnLENOVO:pn20BSCTO1WW:pvrThinkPadX1Carbon3rd:rvnLENOVO:rn20BSCTO1WW:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.name: 20BSCTO1WW
  dmi.product.version: ThinkPad X1 Carbon 3rd
  dmi.sys.vendor: LENOVO

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

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


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

2016-10-05 Thread bugproxy
--- Comment From manju...@in.ibm.com 2016-10-05 12:40 EDT---
Issue recreates on today's kernel: 4.8.0-17-generic..   Please let us know when 
will the patch gets included to yakkety..

Thanks,
Manju

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

Title:
  ISST-LTE:pVM:roselp2:ubuntu 16.10: crash failed to check vmcore of 4.8
  kernel

Status in crash package in Ubuntu:
  In Progress

Bug description:
  == Comment: #0 - Ping Tian Han  - 2016-09-22 03:05:36 ==
  ---Problem Description---
  crash cannot check vmcore of 4.8 kernel. 

  Then when trying to check the core with crash:

  % sudo crash /usr/lib/debug/boot/vmlinux-4.8.0-14-generic
  /var/crash/201609212349/vmcore.201609212349

  crash 7.1.5
  Copyright (C) 2002-2016  Red Hat, Inc.
  Copyright (C) 2004, 2005, 2006, 2010  IBM Corporation
  Copyright (C) 1999-2006  Hewlett-Packard Co
  Copyright (C) 2005, 2006, 2011, 2012  Fujitsu Limited
  Copyright (C) 2006, 2007  VA Linux Systems Japan K.K.
  Copyright (C) 2005, 2011  NEC Corporation
  Copyright (C) 1999, 2002, 2007  Silicon Graphics, Inc.
  Copyright (C) 1999, 2000, 2001, 2002  Mission Critical Linux, Inc.
  This program is free software, covered by the GNU General Public License,
  and you are welcome to change it and/or distribute copies of it under
  certain conditions.  Enter "help copying" to see the conditions.
  This program has absolutely no warranty.  Enter "help warranty" for details.

  GNU gdb (GDB) 7.6
  Copyright (C) 2013 Free Software Foundation, Inc.
  License GPLv3+: GNU GPL version 3 or later 
  This is free software: you are free to change and redistribute it.
  There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
  and "show warranty" for details.
  This GDB was configured as "powerpc64le-unknown-linux-gnu"...

  please wait... (gathering kmem slab cache data)
  crash: invalid kernel virtual address: 7aa9fe0100  type: "pmd page"

   
  ---uname output---
  Linux roselp2 4.8.0-14-generic #15-Ubuntu SMP Tue Sep 20 21:59:33 UTC 2016 
ppc64le ppc64le ppc64le GNU/Linux
   
  Machine Type = IBM,8286-42A, lpar 
   
  ---Steps to Reproduce---
   1. install 4.8 kernel
  2. trigger kdump to get vmcore
  3. check the vmcore with crash

  
  == Comment: #8 - Hari Krishna Bathini  - 2016-09-24 14:12:23 ==
  The below commit is needed for vtop address translation to succeed

commit 182914debbb9a2671ef644027fedd339aa9c80e0
Author: Dave Anderson 
Date:   Fri Sep 23 09:09:15 2016 -0400

  With the introduction of radix MMU in Power ISA 3.0, there are
  changes in kernel page table management accommodating it.  This patch
  series makes appropriate changes here to work for such kernels.
  Also, this series fixes a few bugs along the way:
  
ppc64: fix vtop page translation for 4K pages
ppc64: Use kernel terminology for each level in 4-level page table
ppc64/book3s: address changes in kernel v4.5
ppc64/book3s: address change in page flags for PowerISA v3.0
ppc64: use physical addresses and unfold pud for 64K page size
ppc64/book3s: support big endian Linux page tables
  
  The patches are needed for Linux v4.5 and later kernels on all
  ppc64 hardware.
  (hbath...@linux.vnet.ibm.com)
  --

  Also, the below commit is needed

commit 8ceb1ac628bf6a0a7f0bbfff030ec93081bca4cd
Author: Dave Anderson 
Date:   Mon May 23 11:23:01 2016 -0400

  Fix for Linux commit 0139aa7b7fa12ceef095d99dc36606a5b10ab83a, which
  renamed the page._count member to page._refcount.  Without the patch,
  certain "kmem" commands fail with the "kmem: invalid structure member
  offset: page_count".
  (ander...@redhat.com)

  Thanks
  Hari

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

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


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

2016-10-05 Thread Brad Figg
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/1630663

Title:
  suspend/standby hangs in linux 4.4.0 amd64

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Suspend/Standby worked fine previously under i386 packages, but after
  cross-migrating to amd64, system just hangs and i have to do a hard
  power off (hold power button for 5 seconds).

  i saw notes for #1574125
  (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1574125) where
  people were asked to run `ubuntu-bug linux` so i'm throwing my hat in
  here too.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-38-generic 4.4.0-38.57
  ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
  Uname: Linux 4.4.0-38-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  matt   2675 F pulseaudio
  CurrentDesktop: XFCE
  Date: Wed Oct  5 12:06:58 2016
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=8e82784b-cfa3-4bba-80da-b5f41edcc3f9
  InstallationDate: Installed on 2015-12-01 (308 days ago)
  InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release i386 (20151021)
  MachineType: Hewlett-Packard HP Pavilion dv6500 Notebook PC
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-38-generic 
root=UUID=876adde4-2234-4aa2-9c31-88e8435400d6 ro
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-38-generic N/A
   linux-backports-modules-4.4.0-38-generic  N/A
   linux-firmware1.157.3
  SourcePackage: linux
  UpgradeStatus: Upgraded to xenial on 2016-04-22 (166 days ago)
  dmi.bios.date: 11/25/2008
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: F.59
  dmi.board.name: 30CC
  dmi.board.vendor: Quanta
  dmi.board.version: 79.2E
  dmi.chassis.type: 10
  dmi.chassis.vendor: Quanta
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.59:bd11/25/2008:svnHewlett-Packard:pnHPPaviliondv6500NotebookPC:pvrRev1:rvnQuanta:rn30CC:rvr79.2E:cvnQuanta:ct10:cvrN/A:
  dmi.product.name: HP Pavilion dv6500 Notebook PC
  dmi.product.version: Rev 1
  dmi.sys.vendor: Hewlett-Packard

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

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


[Kernel-packages] [Bug 1630663] [NEW] suspend/standby hangs in linux 4.4.0 amd64

2016-10-05 Thread Matt
Public bug reported:

Suspend/Standby worked fine previously under i386 packages, but after
cross-migrating to amd64, system just hangs and i have to do a hard
power off (hold power button for 5 seconds).

i saw notes for #1574125
(https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1574125) where
people were asked to run `ubuntu-bug linux` so i'm throwing my hat in
here too.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-38-generic 4.4.0-38.57
ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
Uname: Linux 4.4.0-38-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  matt   2675 F pulseaudio
CurrentDesktop: XFCE
Date: Wed Oct  5 12:06:58 2016
EcryptfsInUse: Yes
HibernationDevice: RESUME=UUID=8e82784b-cfa3-4bba-80da-b5f41edcc3f9
InstallationDate: Installed on 2015-12-01 (308 days ago)
InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release i386 (20151021)
MachineType: Hewlett-Packard HP Pavilion dv6500 Notebook PC
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-38-generic 
root=UUID=876adde4-2234-4aa2-9c31-88e8435400d6 ro
RelatedPackageVersions:
 linux-restricted-modules-4.4.0-38-generic N/A
 linux-backports-modules-4.4.0-38-generic  N/A
 linux-firmware1.157.3
SourcePackage: linux
UpgradeStatus: Upgraded to xenial on 2016-04-22 (166 days ago)
dmi.bios.date: 11/25/2008
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: F.59
dmi.board.name: 30CC
dmi.board.vendor: Quanta
dmi.board.version: 79.2E
dmi.chassis.type: 10
dmi.chassis.vendor: Quanta
dmi.chassis.version: N/A
dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.59:bd11/25/2008:svnHewlett-Packard:pnHPPaviliondv6500NotebookPC:pvrRev1:rvnQuanta:rn30CC:rvr79.2E:cvnQuanta:ct10:cvrN/A:
dmi.product.name: HP Pavilion dv6500 Notebook PC
dmi.product.version: Rev 1
dmi.sys.vendor: Hewlett-Packard

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


** Tags: amd64 apport-bug xenial

** Attachment added: "lspci-vnvn.log"
   
https://bugs.launchpad.net/bugs/1630663/+attachment/4755220/+files/lspci-vnvn.log

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

Title:
  suspend/standby hangs in linux 4.4.0 amd64

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Suspend/Standby worked fine previously under i386 packages, but after
  cross-migrating to amd64, system just hangs and i have to do a hard
  power off (hold power button for 5 seconds).

  i saw notes for #1574125
  (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1574125) where
  people were asked to run `ubuntu-bug linux` so i'm throwing my hat in
  here too.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-38-generic 4.4.0-38.57
  ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
  Uname: Linux 4.4.0-38-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  matt   2675 F pulseaudio
  CurrentDesktop: XFCE
  Date: Wed Oct  5 12:06:58 2016
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=8e82784b-cfa3-4bba-80da-b5f41edcc3f9
  InstallationDate: Installed on 2015-12-01 (308 days ago)
  InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release i386 (20151021)
  MachineType: Hewlett-Packard HP Pavilion dv6500 Notebook PC
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-38-generic 
root=UUID=876adde4-2234-4aa2-9c31-88e8435400d6 ro
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-38-generic N/A
   linux-backports-modules-4.4.0-38-generic  N/A
   linux-firmware1.157.3
  SourcePackage: linux
  UpgradeStatus: Upgraded to xenial on 2016-04-22 (166 days ago)
  dmi.bios.date: 11/25/2008
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: F.59
  dmi.board.name: 30CC
  dmi.board.vendor: Quanta
  dmi.board.version: 79.2E
  dmi.chassis.type: 10
  dmi.chassis.vendor: Quanta
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.59:bd11/25/2008:svnHewlett-Packard:pnHPPaviliondv6500NotebookPC:pvrRev1:rvnQuanta:rn30CC:rvr79.2E:cvnQuanta:ct10:cvrN/A:
  dmi.product.name: HP Pavilion dv6500 Notebook PC
  dmi.product.version: Rev 1
  dmi.sys.vendor: Hewlett-Packard

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

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


[Kernel-packages] [Bug 1630663] Re: suspend/standby hangs

2016-10-05 Thread Matt
** Attachment added: "version.log"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1630663/+attachment/4755237/+files/version.log

** Summary changed:

- suspend/standby hangs
+ suspend/standby hangs in linux 4.4.0 amd64

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

Title:
  suspend/standby hangs in linux 4.4.0 amd64

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Suspend/Standby worked fine previously under i386 packages, but after
  cross-migrating to amd64, system just hangs and i have to do a hard
  power off (hold power button for 5 seconds).

  i saw notes for #1574125
  (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1574125) where
  people were asked to run `ubuntu-bug linux` so i'm throwing my hat in
  here too.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-38-generic 4.4.0-38.57
  ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
  Uname: Linux 4.4.0-38-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  matt   2675 F pulseaudio
  CurrentDesktop: XFCE
  Date: Wed Oct  5 12:06:58 2016
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=8e82784b-cfa3-4bba-80da-b5f41edcc3f9
  InstallationDate: Installed on 2015-12-01 (308 days ago)
  InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release i386 (20151021)
  MachineType: Hewlett-Packard HP Pavilion dv6500 Notebook PC
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-38-generic 
root=UUID=876adde4-2234-4aa2-9c31-88e8435400d6 ro
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-38-generic N/A
   linux-backports-modules-4.4.0-38-generic  N/A
   linux-firmware1.157.3
  SourcePackage: linux
  UpgradeStatus: Upgraded to xenial on 2016-04-22 (166 days ago)
  dmi.bios.date: 11/25/2008
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: F.59
  dmi.board.name: 30CC
  dmi.board.vendor: Quanta
  dmi.board.version: 79.2E
  dmi.chassis.type: 10
  dmi.chassis.vendor: Quanta
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.59:bd11/25/2008:svnHewlett-Packard:pnHPPaviliondv6500NotebookPC:pvrRev1:rvnQuanta:rn30CC:rvr79.2E:cvnQuanta:ct10:cvrN/A:
  dmi.product.name: HP Pavilion dv6500 Notebook PC
  dmi.product.version: Rev 1
  dmi.sys.vendor: Hewlett-Packard

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

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


[Kernel-packages] [Bug 1627108] Re: X1Carbon comes to a crawl during high CPU usage tasks

2016-10-05 Thread Omer Akram
Same results. This build is infected as well.

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

Title:
  X1Carbon comes to a crawl during high CPU usage tasks

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

Bug description:
  My X1Carbon becomes quite laggy, the cursor hangs for a few seconds
  and then resumes while my system is compiling some code, or lets says
  PyCharm is indexing things or Android Studio is compiling some code. I
  was using 4.4 on Xenial a few days ago and everything was working just
  fine. Installed Yakkety and this issue happens.

  I will downgrade the kernel and see if that mitigates the issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: linux-image-4.8.0-15-generic 4.8.0-15.16
  ProcVersionSignature: Ubuntu 4.8.0-15.16-generic 4.8.0-rc7
  Uname: Linux 4.8.0-15-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC1D0p:   om26er 3390 F...m pulseaudio
   /dev/snd/controlC1:  om26er 3390 F pulseaudio
   /dev/snd/controlC0:  om26er 3390 F pulseaudio
  CurrentDesktop: Unity
  Date: Fri Sep 23 21:40:34 2016
  HibernationDevice: RESUME=UUID=a92c85ab-cca3-4afc-abf1-3516f193129e
  InstallationDate: Installed on 2016-09-21 (1 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160921)
  MachineType: LENOVO 20BSCTO1WW
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-15-generic.efi.signed 
root=UUID=01b0a4a0-d791-46e8-a212-1f769cff3a4b ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-15-generic N/A
   linux-backports-modules-4.8.0-15-generic  N/A
   linux-firmware1.161
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/13/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N14ET32W (1.10 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20BSCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN14ET32W(1.10):bd08/13/2015:svnLENOVO:pn20BSCTO1WW:pvrThinkPadX1Carbon3rd:rvnLENOVO:rn20BSCTO1WW:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.name: 20BSCTO1WW
  dmi.product.version: ThinkPad X1 Carbon 3rd
  dmi.sys.vendor: LENOVO

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

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


[Kernel-packages] [Bug 1629205] Re: regression: with linux-image-4.4.0-38-generic autofs tries to acess folders as root instead of the user

2016-10-05 Thread Tim Gardner
Robert - add ignore files to your ABI directory. For example,

echo 1 > debian.master/abi/4.4.0-41.61/amd64/ignore
echo 1 > debian.master/abi/4.4.0-41.61/amd64/ignore.modules

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

Title:
  regression: with linux-image-4.4.0-38-generic autofs tries to acess
  folders as root instead of the user

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Running with linux-image-4.4.0-38-generic autofs is not working
  properly anymore: when I try to access a autofs-monitored folder as
  normal user "joe" the environment variable $AUTOFS_USER inside the
  auto mounter map script is set to "root" instead of the user "joe".

  A little background information: in our setup the autofs master map
  /etc/auto.master contains a line:

  /mnt/cifs   /etc/auto.cifs-shares --timeout=300 --verbose

  The script /etc/auto.cifs-shares contains for debugging purposes the
  lines:

  DEBUG=true
  $DEBUG && logger -p debug -- "$0: running 'env|grep AUTOFS':"
  $DEBUG && logger -p debug -- "$(env|grep AUTOFS)"

  and

  if test "$1" = "$AUTOFS_USER" ; then
  ## First generate automount map
  [..]
  else
  logger -p debug -- "$0: Error: User '$AUTOFS_USER' tried to access 
wrong directory '$1'"
  fi

  
  Which yields to the following errors in the logs:

  Sep 29 17:03:20 pcXX root[7613]: AUTOFS_SHOST=pc203re3
   AUTOFS_HOME=/root
   AUTOFS_GID=0
   AUTOFS_UID=0
   AUTOFS_GROUP=root
   AUTOFS_USER=root
  Sep 29 17:03:20 pcXX root[7614]: /etc/auto.cifs-shares: Error: User 
'root' tried to access wrong directory 'joe'
  Sep 29 17:03:20 pcXX automount[7557]: lookup(program): lookup for joe 
failed
  Sep 29 17:03:20 pcXX automount[7557]: failed to mount /mnt/cifs/joe

  
  So for some reason autofs with this kernel gets the environment variables 
wrong.
  Running an older Kernel like linux-image-4.4.0-36-generic does not show this 
problem and the cifs shares work as expected.

  other Info:
  lsb_release -rd
  Description:Ubuntu 16.04.1 LTS
  Release:16.04

  uname -r
  4.4.0-38-generic

  If you need any further info or testing, please let me know.

  Thanks,
  Robert Euhus

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-38-generic 4.4.0-38.57
  ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
  Uname: Linux 4.4.0-38-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  euhus  1711 F pulseaudio
  CurrentDesktop: GNOME
  Date: Fri Sep 30 09:36:31 2016
  HibernationDevice: RESUME=UUID=1aae5293-ed3d-4dae-a8b5-54d831262f4a
  IwConfig:
   lono wireless extensions.
   
   enp0s31f6  no wireless extensions.
  MachineType: Dell Inc. OptiPlex 5040
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-38-generic 
root=UUID=adae86bf-dc79-4962-aa5f-41a1a037c8ec ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-38-generic N/A
   linux-backports-modules-4.4.0-38-generic  N/A
   linux-firmware1.157.3
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/15/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.7
  dmi.board.name: 0R790T
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 3
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.7:bd01/15/2016:svnDellInc.:pnOptiPlex5040:pvr:rvnDellInc.:rn0R790T:rvrA00:cvnDellInc.:ct3:cvr:
  dmi.product.name: OptiPlex 5040
  dmi.sys.vendor: Dell Inc.

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

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


[Kernel-packages] [Bug 1627108] Re: X1Carbon comes to a crawl during high CPU usage tasks

2016-10-05 Thread Joseph Salisbury
I built the next test kernel, up to the following commit:
55392c4c06204c8149dc09cf474691f1cc3c

The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1627108

Can you test that kernel and report back if it has the bug or not? I
will build the next test kernel based on your test results.

Thanks in advance

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

Title:
  X1Carbon comes to a crawl during high CPU usage tasks

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

Bug description:
  My X1Carbon becomes quite laggy, the cursor hangs for a few seconds
  and then resumes while my system is compiling some code, or lets says
  PyCharm is indexing things or Android Studio is compiling some code. I
  was using 4.4 on Xenial a few days ago and everything was working just
  fine. Installed Yakkety and this issue happens.

  I will downgrade the kernel and see if that mitigates the issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: linux-image-4.8.0-15-generic 4.8.0-15.16
  ProcVersionSignature: Ubuntu 4.8.0-15.16-generic 4.8.0-rc7
  Uname: Linux 4.8.0-15-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC1D0p:   om26er 3390 F...m pulseaudio
   /dev/snd/controlC1:  om26er 3390 F pulseaudio
   /dev/snd/controlC0:  om26er 3390 F pulseaudio
  CurrentDesktop: Unity
  Date: Fri Sep 23 21:40:34 2016
  HibernationDevice: RESUME=UUID=a92c85ab-cca3-4afc-abf1-3516f193129e
  InstallationDate: Installed on 2016-09-21 (1 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160921)
  MachineType: LENOVO 20BSCTO1WW
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-15-generic.efi.signed 
root=UUID=01b0a4a0-d791-46e8-a212-1f769cff3a4b ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-15-generic N/A
   linux-backports-modules-4.8.0-15-generic  N/A
   linux-firmware1.161
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/13/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N14ET32W (1.10 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20BSCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN14ET32W(1.10):bd08/13/2015:svnLENOVO:pn20BSCTO1WW:pvrThinkPadX1Carbon3rd:rvnLENOVO:rn20BSCTO1WW:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.name: 20BSCTO1WW
  dmi.product.version: ThinkPad X1 Carbon 3rd
  dmi.sys.vendor: LENOVO

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

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


[Kernel-packages] [Bug 1625788] onza (i386) - tests ran: 10, failed: 0

2016-10-05 Thread Brad Figg
tests ran:  10, failed: 0;
  
http://kernel.ubuntu.com/testing/3.19.0-70.78/onza__3.19.0-70.78__2016-10-05_14-40-00/results-index.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/1625788

Title:
  linux: 3.19.0-70.78 -proposed tracker

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

Bug description:
  This bug is for tracking the 3.19.0-70.78 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 --
  derivative-trackers-created: 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/1625788/+subscriptions

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


[Kernel-packages] [Bug 1627108] Re: X1Carbon comes to a crawl during high CPU usage tasks

2016-10-05 Thread Omer Akram
Tested, the latest kernel build that you provided is bad as well.

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

Title:
  X1Carbon comes to a crawl during high CPU usage tasks

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

Bug description:
  My X1Carbon becomes quite laggy, the cursor hangs for a few seconds
  and then resumes while my system is compiling some code, or lets says
  PyCharm is indexing things or Android Studio is compiling some code. I
  was using 4.4 on Xenial a few days ago and everything was working just
  fine. Installed Yakkety and this issue happens.

  I will downgrade the kernel and see if that mitigates the issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: linux-image-4.8.0-15-generic 4.8.0-15.16
  ProcVersionSignature: Ubuntu 4.8.0-15.16-generic 4.8.0-rc7
  Uname: Linux 4.8.0-15-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC1D0p:   om26er 3390 F...m pulseaudio
   /dev/snd/controlC1:  om26er 3390 F pulseaudio
   /dev/snd/controlC0:  om26er 3390 F pulseaudio
  CurrentDesktop: Unity
  Date: Fri Sep 23 21:40:34 2016
  HibernationDevice: RESUME=UUID=a92c85ab-cca3-4afc-abf1-3516f193129e
  InstallationDate: Installed on 2016-09-21 (1 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160921)
  MachineType: LENOVO 20BSCTO1WW
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-15-generic.efi.signed 
root=UUID=01b0a4a0-d791-46e8-a212-1f769cff3a4b ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-15-generic N/A
   linux-backports-modules-4.8.0-15-generic  N/A
   linux-firmware1.161
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/13/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N14ET32W (1.10 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20BSCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN14ET32W(1.10):bd08/13/2015:svnLENOVO:pn20BSCTO1WW:pvrThinkPadX1Carbon3rd:rvnLENOVO:rn20BSCTO1WW:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.name: 20BSCTO1WW
  dmi.product.version: ThinkPad X1 Carbon 3rd
  dmi.sys.vendor: LENOVO

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

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


[Kernel-packages] [Bug 1629205] Re: regression: with linux-image-4.4.0-38-generic autofs tries to acess folders as root instead of the user

2016-10-05 Thread Robert Euhus
Thanks for the offer Joseph! I have read your answer a bit late, so I am
already on my 9th kernel (all good so far). The docs were quite good and
I have wanted to try out "that bisect thing" for quite a while :)

(It's just a bit annoying that it takes about half an hour to compile on
a i5-6500 with 16G RAM. I had expected a bit less.)

But now I have run into the problem, that I cannot build the current
bisect point.

I have cloned the kernel repo via
git clone git://kernel.ubuntu.com/ubuntu/ubuntu-xenial.git

I have attached the git bisect log up to the current point.

When the compile is just about to be finished it fails with:

EE: 36 symbols changed hash and weren't ignored
II: Module hash change summary...
vmlinux : 36
II: Done
debian/rules.d/4-checks.mk:3: die Regel für Ziel „abi-check-generic“ scheiterte 
  
make: *** [abi-check-generic] Fehler 1

Sorry it's in German, I can redo it in english. I will attach a longer
trace.

I have always compiled doing a clean first:
fakeroot debian/rules clean && fakeroot debian/rules binary-headers 
binary-generic

So how do I go on from here?

** Attachment added: "git bisect log"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1629205/+attachment/4755113/+files/git_bisect_log

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

Title:
  regression: with linux-image-4.4.0-38-generic autofs tries to acess
  folders as root instead of the user

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Running with linux-image-4.4.0-38-generic autofs is not working
  properly anymore: when I try to access a autofs-monitored folder as
  normal user "joe" the environment variable $AUTOFS_USER inside the
  auto mounter map script is set to "root" instead of the user "joe".

  A little background information: in our setup the autofs master map
  /etc/auto.master contains a line:

  /mnt/cifs   /etc/auto.cifs-shares --timeout=300 --verbose

  The script /etc/auto.cifs-shares contains for debugging purposes the
  lines:

  DEBUG=true
  $DEBUG && logger -p debug -- "$0: running 'env|grep AUTOFS':"
  $DEBUG && logger -p debug -- "$(env|grep AUTOFS)"

  and

  if test "$1" = "$AUTOFS_USER" ; then
  ## First generate automount map
  [..]
  else
  logger -p debug -- "$0: Error: User '$AUTOFS_USER' tried to access 
wrong directory '$1'"
  fi

  
  Which yields to the following errors in the logs:

  Sep 29 17:03:20 pcXX root[7613]: AUTOFS_SHOST=pc203re3
   AUTOFS_HOME=/root
   AUTOFS_GID=0
   AUTOFS_UID=0
   AUTOFS_GROUP=root
   AUTOFS_USER=root
  Sep 29 17:03:20 pcXX root[7614]: /etc/auto.cifs-shares: Error: User 
'root' tried to access wrong directory 'joe'
  Sep 29 17:03:20 pcXX automount[7557]: lookup(program): lookup for joe 
failed
  Sep 29 17:03:20 pcXX automount[7557]: failed to mount /mnt/cifs/joe

  
  So for some reason autofs with this kernel gets the environment variables 
wrong.
  Running an older Kernel like linux-image-4.4.0-36-generic does not show this 
problem and the cifs shares work as expected.

  other Info:
  lsb_release -rd
  Description:Ubuntu 16.04.1 LTS
  Release:16.04

  uname -r
  4.4.0-38-generic

  If you need any further info or testing, please let me know.

  Thanks,
  Robert Euhus

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-38-generic 4.4.0-38.57
  ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
  Uname: Linux 4.4.0-38-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  euhus  1711 F pulseaudio
  CurrentDesktop: GNOME
  Date: Fri Sep 30 09:36:31 2016
  HibernationDevice: RESUME=UUID=1aae5293-ed3d-4dae-a8b5-54d831262f4a
  IwConfig:
   lono wireless extensions.
   
   enp0s31f6  no wireless extensions.
  MachineType: Dell Inc. OptiPlex 5040
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-38-generic 
root=UUID=adae86bf-dc79-4962-aa5f-41a1a037c8ec ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-38-generic N/A
   linux-backports-modules-4.4.0-38-generic  N/A
   linux-firmware1.157.3
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/15/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.7
  dmi.board.name: 0R790T
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 3
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 

[Kernel-packages] [Bug 1629205] Re: regression: with linux-image-4.4.0-38-generic autofs tries to acess folders as root instead of the user

2016-10-05 Thread Robert Euhus
** Attachment added: "The current git status"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1629205/+attachment/4755115/+files/git_status

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

Title:
  regression: with linux-image-4.4.0-38-generic autofs tries to acess
  folders as root instead of the user

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Running with linux-image-4.4.0-38-generic autofs is not working
  properly anymore: when I try to access a autofs-monitored folder as
  normal user "joe" the environment variable $AUTOFS_USER inside the
  auto mounter map script is set to "root" instead of the user "joe".

  A little background information: in our setup the autofs master map
  /etc/auto.master contains a line:

  /mnt/cifs   /etc/auto.cifs-shares --timeout=300 --verbose

  The script /etc/auto.cifs-shares contains for debugging purposes the
  lines:

  DEBUG=true
  $DEBUG && logger -p debug -- "$0: running 'env|grep AUTOFS':"
  $DEBUG && logger -p debug -- "$(env|grep AUTOFS)"

  and

  if test "$1" = "$AUTOFS_USER" ; then
  ## First generate automount map
  [..]
  else
  logger -p debug -- "$0: Error: User '$AUTOFS_USER' tried to access 
wrong directory '$1'"
  fi

  
  Which yields to the following errors in the logs:

  Sep 29 17:03:20 pcXX root[7613]: AUTOFS_SHOST=pc203re3
   AUTOFS_HOME=/root
   AUTOFS_GID=0
   AUTOFS_UID=0
   AUTOFS_GROUP=root
   AUTOFS_USER=root
  Sep 29 17:03:20 pcXX root[7614]: /etc/auto.cifs-shares: Error: User 
'root' tried to access wrong directory 'joe'
  Sep 29 17:03:20 pcXX automount[7557]: lookup(program): lookup for joe 
failed
  Sep 29 17:03:20 pcXX automount[7557]: failed to mount /mnt/cifs/joe

  
  So for some reason autofs with this kernel gets the environment variables 
wrong.
  Running an older Kernel like linux-image-4.4.0-36-generic does not show this 
problem and the cifs shares work as expected.

  other Info:
  lsb_release -rd
  Description:Ubuntu 16.04.1 LTS
  Release:16.04

  uname -r
  4.4.0-38-generic

  If you need any further info or testing, please let me know.

  Thanks,
  Robert Euhus

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-38-generic 4.4.0-38.57
  ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
  Uname: Linux 4.4.0-38-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  euhus  1711 F pulseaudio
  CurrentDesktop: GNOME
  Date: Fri Sep 30 09:36:31 2016
  HibernationDevice: RESUME=UUID=1aae5293-ed3d-4dae-a8b5-54d831262f4a
  IwConfig:
   lono wireless extensions.
   
   enp0s31f6  no wireless extensions.
  MachineType: Dell Inc. OptiPlex 5040
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-38-generic 
root=UUID=adae86bf-dc79-4962-aa5f-41a1a037c8ec ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-38-generic N/A
   linux-backports-modules-4.4.0-38-generic  N/A
   linux-firmware1.157.3
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/15/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.7
  dmi.board.name: 0R790T
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 3
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.7:bd01/15/2016:svnDellInc.:pnOptiPlex5040:pvr:rvnDellInc.:rn0R790T:rvrA00:cvnDellInc.:ct3:cvr:
  dmi.product.name: OptiPlex 5040
  dmi.sys.vendor: Dell Inc.

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

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


[Kernel-packages] [Bug 1629205] Re: regression: with linux-image-4.4.0-38-generic autofs tries to acess folders as root instead of the user

2016-10-05 Thread Robert Euhus
** Attachment added: "longer trace of the build error"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1629205/+attachment/4755114/+files/build-error.log

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

Title:
  regression: with linux-image-4.4.0-38-generic autofs tries to acess
  folders as root instead of the user

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Running with linux-image-4.4.0-38-generic autofs is not working
  properly anymore: when I try to access a autofs-monitored folder as
  normal user "joe" the environment variable $AUTOFS_USER inside the
  auto mounter map script is set to "root" instead of the user "joe".

  A little background information: in our setup the autofs master map
  /etc/auto.master contains a line:

  /mnt/cifs   /etc/auto.cifs-shares --timeout=300 --verbose

  The script /etc/auto.cifs-shares contains for debugging purposes the
  lines:

  DEBUG=true
  $DEBUG && logger -p debug -- "$0: running 'env|grep AUTOFS':"
  $DEBUG && logger -p debug -- "$(env|grep AUTOFS)"

  and

  if test "$1" = "$AUTOFS_USER" ; then
  ## First generate automount map
  [..]
  else
  logger -p debug -- "$0: Error: User '$AUTOFS_USER' tried to access 
wrong directory '$1'"
  fi

  
  Which yields to the following errors in the logs:

  Sep 29 17:03:20 pcXX root[7613]: AUTOFS_SHOST=pc203re3
   AUTOFS_HOME=/root
   AUTOFS_GID=0
   AUTOFS_UID=0
   AUTOFS_GROUP=root
   AUTOFS_USER=root
  Sep 29 17:03:20 pcXX root[7614]: /etc/auto.cifs-shares: Error: User 
'root' tried to access wrong directory 'joe'
  Sep 29 17:03:20 pcXX automount[7557]: lookup(program): lookup for joe 
failed
  Sep 29 17:03:20 pcXX automount[7557]: failed to mount /mnt/cifs/joe

  
  So for some reason autofs with this kernel gets the environment variables 
wrong.
  Running an older Kernel like linux-image-4.4.0-36-generic does not show this 
problem and the cifs shares work as expected.

  other Info:
  lsb_release -rd
  Description:Ubuntu 16.04.1 LTS
  Release:16.04

  uname -r
  4.4.0-38-generic

  If you need any further info or testing, please let me know.

  Thanks,
  Robert Euhus

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-38-generic 4.4.0-38.57
  ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
  Uname: Linux 4.4.0-38-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  euhus  1711 F pulseaudio
  CurrentDesktop: GNOME
  Date: Fri Sep 30 09:36:31 2016
  HibernationDevice: RESUME=UUID=1aae5293-ed3d-4dae-a8b5-54d831262f4a
  IwConfig:
   lono wireless extensions.
   
   enp0s31f6  no wireless extensions.
  MachineType: Dell Inc. OptiPlex 5040
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-38-generic 
root=UUID=adae86bf-dc79-4962-aa5f-41a1a037c8ec ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-38-generic N/A
   linux-backports-modules-4.4.0-38-generic  N/A
   linux-firmware1.157.3
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/15/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.7
  dmi.board.name: 0R790T
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 3
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.7:bd01/15/2016:svnDellInc.:pnOptiPlex5040:pvr:rvnDellInc.:rn0R790T:rvrA00:cvnDellInc.:ct3:cvr:
  dmi.product.name: OptiPlex 5040
  dmi.sys.vendor: Dell Inc.

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

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


[Kernel-packages] [Bug 1628279] Re: python utilities script suffix (.py) should be removed as per Policy 10.4

2016-10-05 Thread Eric Desrochers
I confirmed it works as expected :

root@test01:~# dpkg -l | grep -i zfsutils-linux
ii  zfsutils-linux 0.6.5.6-0ubuntu14   amd64
Native OpenZFS management utilities for Linux

root@test01:~# cat /etc/lsb-release 
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=16.04
DISTRIB_CODENAME=xenial
DISTRIB_DESCRIPTION="Ubuntu 16.04 LTS"

root@test01:~# ls -altr /usr/sbin/arc*
-rwxr-xr-x 1 root root 40752 Oct  5 09:05 /usr/sbin/arc_summary.py
-rwxr-xr-x 1 root root 13058 Oct  5 09:05 /usr/sbin/arcstat.py
lrwxrwxrwx 1 root root14 Oct  5 09:05 /usr/sbin/arc_summary -> 
arc_summary.py
lrwxrwxrwx 1 root root10 Oct  5 09:05 /usr/sbin/arcstat -> arcstat.py
root@test01:~# ls -altr /usr/sbin/dbufstat
lrwxrwxrwx 1 root root 11 Oct  5 09:05 /usr/sbin/dbufstat -> dbufstat.py

Eric


** Tags added: verification-done

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

Title:
  python utilities script suffix (.py) should be removed as per Policy
  10.4

Status in zfs-linux package in Ubuntu:
  Fix Released
Status in zfs-linux source package in Xenial:
  Fix Committed

Bug description:
  [Impact]

  The zfs utilities scripts shipped with debian and ubuntu such as :

  * arc_summary.py : Provides a summary of the statistics
  * arcstat.py : Print out ZFS ARC Statistics exported via kstat(1)
  * dbufstat.py : Print out statistics for all cached dmu buffers

  should be renamed according to Policy 10.4 :
  https://www.debian.org/doc/debian-policy/ch-files.html#s-scripts

  "When scripts are installed into a directory in the system PATH, the
  script name should not include an extension such as .sh or .pl that
  denotes the scripting language currently used to implement it."

  Ideally, this should be fixed and upstreamed to Debian (or to zfslinux
  upstream) as well.

  [Test Case]

   * Install zfsutils-linux
   * List files

   $ dpkg -L zfsutils-linux | egrep "arc|dbufstat"
     /usr/sbin/arc_summary.py
     /usr/sbin/arcstat.py
     /usr/sbin/dbufstat.py

  [Regression Potential]

   * none expected, this is a trivial change that simply rename the
  scripts to remove the extension (.py) with a simple 'mv' before the
  dh_install invocation in order to get this expected result :

  $ dpkg -L zfsutils-linux | egrep -i "arc|dbuf"
    /usr/sbin/arc_summary
    /usr/sbin/arcstat
    /usr/sbin/dbufstat

  Yakkety include the renaming as shown above.

  Xenial will have a symlink to not break user experience until next release 
upgrade:
  
https://bugs.launchpad.net/ubuntu/xenial/+source/zfs-linux/+bug/1628279/comments/19

  So user will be able to use both for instance : arcstat.py or arcstat

  
  [Other Info]

   * Justification/argument for Xenial
  https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1628279/comments/13
  https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1628279/comments/14

  * Debian bug
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=839645

   * Upstream (ZoL) is reluctant to change it at upstream code level.
  https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1628279/comments/2

   * This has been flag by Adam Conrad
  https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1574342/comments/19

   * Debian policy
  https://www.debian.org/doc/debian-policy/ch-files.html#s-scripts

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

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


[Kernel-packages] [Bug 1627198] Re: 4.8.0 kernels do not complete boot process on VM

2016-10-05 Thread Barry Warsaw
Confirmed that Yakkety main kernel boots and logs into the desktop.

% uname -a
Linux anarchist 4.8.0-040800rc1-generic #201609281024 SMP Wed Sep 28 14:26:22 
UTC 2016 x86_64 x86_64 x86_64 GNU/Linux
% dpkg-query -W linux-image-generic
linux-image-generic 4.8.0.19.28

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

Title:
  4.8.0 kernels do not complete boot process on VM

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Fix Released
Status in linux-raspi2 package in Ubuntu:
  Fix Committed
Status in linux source package in Yakkety:
  Fix Released
Status in linux-raspi2 source package in Yakkety:
  Fix Committed

Bug description:
  On my native amd64 box, 4.8.0-15 works just fine, but on my VMWare
  Fusion 8.5 system, none of the 4.8.0 kernels complete the boot
  process.  I tried 4.8.0-15 from yakkety and 4.8.0-16 from yakkety-
  proposed.

  Currently  I am seeing the last message in my console at boot up as:

  [ OK ] Started Bluetooth service

  and then... it just sits there.

  Through the use of snapshots, restores, and package bisects, I've
  definitively narrowed it to linux-generic linux-image-generic and
  linux-headers-generic.

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

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


[Kernel-packages] [Bug 1626983] Re: [Ubuntu16.10]KV4.8: kernel livepatch config options are not set

2016-10-05 Thread bugproxy
** Tags removed: bugnameltc-146670 severity-critical

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

Title:
  [Ubuntu16.10]KV4.8: kernel livepatch config options are not set

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

Bug description:
  ---Problem Description---
  Kernel LivePatch config options are not set
   
  ---uname output---
  Linux HostName 4.8.0-11-generic #12-Ubuntu SMP Sat Sep 17 19:58:16 UTC 2016 
ppc64le ppc64le ppc64le GNU/Linux
   
  Machine Type = 8348-21C 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   Check for the following config options in the config file of 4.8.0 kernel 
version.
  CONFIG_HAVE_LIVEPATCH=Y
  CONFIG_LIVEPATCH=Y

  # grep LIVEPATCH /boot/config-4.8.0-11-generic
  #
   
  Contact Information = nasas...@in.ibm.com 
   
  Stack trace output:
   no
   
  Oops output:
   no
   
  System Dump Info:
The system is not configured to capture a system dump.
   
  *Additional Instructions for nasas...@in.ibm.com: 
  -Attach sysctl -a output output to the bug.

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

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


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

2016-10-05 Thread bugproxy
--- Comment From bren...@br.ibm.com 2016-10-05 10:23 EDT---
Hello Hari,

It seems that there is another issue now, correct? Should we open a new
defect for it, or, just track it here? I think that Canonical's action
is not clear at this moment.

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

Title:
  In Ubuntu16.10:Fadump fails as Kernel panic reported while
  dumping-,console got hung on 32TB Brazos System (kdump)

Status in linux package in Ubuntu:
  Triaged

Bug description:
  == Comment: #0 - Praveen K. Pandey  - 2016-07-17 
02:37:31 ==
  Hi 

   In Ubuntu16.10 I  I tried fadump in Brazos system (32TB Memory and
  192 core) , when trigger panic in kernel panic occur and console got
  hung.

  Reproducible Step:

  1- Install Ubuntu16.10
  2- boot system with 31TB and 192 Core 
  3- configure fadump in system 
  4- verify fadump in system that it is running 
  5- Trigger panic in system

  Actual Result

  Not able  to take Fadump , kernel panic and console got hung

  Expected Result

  Fadump will be captured

  Log:

  root@ltc-brazos1:~# kdump-config show
  DUMP_MODE:fadump
  USE_KDUMP:1
  KDUMP_SYSCTL: kernel.panic_on_oops=1
  KDUMP_COREDIR:/var/crash
 /var/lib/kdump/vmlinuz: symbolic link to /boot/vmlinux-4.4.0-30-generic
  kdump initrd: 
 /var/lib/kdump/initrd.img: symbolic link to 
/var/lib/kdump/initrd.img-4.4.0-30-generic
  current state:ready to fadump
  root@ltc-brazos1:~# 

  root@ltc-brazos1:~# cat /proc/cmdline 
  BOOT_IMAGE=/boot/vmlinux-4.4.0-30-generic 
root=UUID=516c4b1b-6700-4b55-bd37-d61c4c5af6af ro quiet splash fadump=on 
fadump_reserve_mem=4096M crashkernel=4096M
  root@ltc-brazos1:~# 

  ltc-brazos1 login: [  442.749993] sysrq: SysRq : Trigger a crash  

  
  [  442.750031] Unable to handle kernel paging request for data at address 
0x  
  
  [  442.750037] Faulting instruction address: 0xc0670014   

  
  [  442.750043] Oops: Kernel access of bad area, sig: 11 [#1]  

  
  [  442.750047] SMP NR_CPUS=2048 NUMA pSeries  

  
  [  442.750053] Modules linked in: pseries_rng btrfs xor raid6_pq rtc_generic 
sunrpc autofs4 ses enclosure ipr
   
  [  442.750068] CPU: 157 PID: 403890 Comm: bash Not tainted 4.4.0-30-generic 
#49-Ubuntu  

  [  442.750074] task: c3f97b0af640 ti: c3f97b104000 task.ti: 
c3f97b104000

  [  442.750079] NIP: c0670014 LR: c06710c8 CTR: 
c066ffe0
 
  [  442.750083] REGS: c3f97b107990 TRAP: 0300   Not tainted  
(4.4.0-30-generic)  

  [  442.750088] MSR: 80009033   CR: 2824  
XER: 0001   
 
  [  442.750100] CFAR: c0008468 DAR:  DSISR: 4200 
SOFTE: 1

  GPR00: c06710c8 c3f97b107c10 c15b5d00 0063

  
  GPR04: c1faba749c50 c1faba75b4e0 c0001f3efe7c 0313 
  GPR08: 0007 0001  c0001f3efe7cecb8 
  GPR12: c066ffe0 cbc9d380  2200 
  GPR16: 10170dc8 01001ef401d8 10140f58 100c7570 
  GPR20:  1017dd58 10153618 1017b608 
  GPR24: 37c9e7b4 0001 c14f8e58 0004 
  GPR28: c14f9218 0063 c14b11dc  
  [  442.750165] NIP [c0670014] sysrq_handle_crash+0x34/0x50
  [  442.750170] LR [c06710c8] __handle_sysrq+0xe8/0x270
  [  442.750174] Call Trace:
  [  442.750179] [c3f97b107c10] [c0e08f28] 
_fw_tigon_tg3_bin_name+0x2ce58/0x342b0 (unreliable)
  [  442.750186] [c3f97b107c30] 

[Kernel-packages] [Bug 1629260] Re: drdb kernal 4 crash

2016-10-05 Thread G. Kooistra
We had installed the mainline kernel on two machines and tested it again.
The issue still remains. One of the two machines get slow, lost the drdb 
connection en begin to hang.

The other machine works fine (just like before).



** Attachment added: "drdb status.png"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1629260/+attachment/4755072/+files/drdb%20status.png

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

Title:
  drdb kernal 4 crash

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  After upgrading ubuntu 14.04 LTS from kernal 3 to kernal 4.4.0-38-generic, we 
got issues with DRBD.
  Especially during high load, the drdb kernal will gif issues.

  The DRBD status go's to a timeout and the server becomes unstable (also the 
KVM's running on it) and afther some minutes/hours, the system hangs.
  Only a hard reset is possible.

  This problem randomly appear after a few minutes / hours / days.

  Got this issue on multiple servers.
  The workaround is to go back to the old kernel.

  Logfiles:
  https://ubuntuforums.org/showthread.php?t=2336150

  
  Ubuntu version: 
  Description:Ubuntu 14.04.5 LTS
  Release:14.04

  drbd8-utils:
Installed: 2:8.4.4-1ubuntu1
Candidate: 2:8.4.4-1ubuntu1
Version table:
   *** 2:8.4.4-1ubuntu1 0
  500 http://nl.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
  100 /var/lib/dpkg/status

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

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


[Kernel-packages] [Bug 539851] Local representation

2016-10-05 Thread bgrade
*** This bug is a duplicate of bug 992346 ***
https://bugs.launchpad.net/bugs/992346

Good day!

We are looking for employees working remotely.

My name is Jessie, I am the personnel manager of a large International company.
Most of the work you can do from home, that is, at a distance.

Salary is $2200-$5100.

If you are interested in this offer, please visit 
Our Site

Best regards!

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

Title:
  [drm:radeon_dvi_detect] *ERROR* HDMI Type A-1: probed a monitor but
  no|invalid EDID

Status in Linux:
  Confirmed
Status in linux package in Ubuntu:
  Incomplete
Status in linux package in Arch Linux:
  New

Bug description:
  This is a show stopper with my 10.04 system that I am currently
  running on.

  I have:
  02:00.0 VGA compatible controller: ATI Technologies Inc RV630 [Radeon HD 2600 
Series]
  02:00.1 Audio device: ATI Technologies Inc RV630/M76 audio device [Radeon HD 
2600 Series]

  This is connected to a LCD TV using HDMi, running the latest kernel
  breaks the xserver and I am dripped out into the shell with the same
  error messages in the log below. I am writing this on the previous
  kernel version so it does work.

  kern.log:
  
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/539851/+attachment/2985553/+files/kern.log

  Description:  Ubuntu lucid (development branch)
  Release:  10.04

  ProblemType: Bug
  Architecture: amd64
  Date: Tue Mar 16 19:47:32 2010
  DistroRelease: Ubuntu 10.04
  DkmsStatus: Error: [Errno 2] No such file or directory
  InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Alpha amd64 (20100224.1)
  Package: xorg 1:7.5+3ubuntu1
  ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-14-generic 
root=UUID=eddccd76-9229-43b5-9279-57dd02e07efa ro quiet splash
  ProcEnviron:
   PATH=(cususername, no user)
   LANG=en_GB.utf8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 2.6.32-14.20-generic
  SourcePackage: xorg
  Uname: Linux 2.6.32-14-generic x86_64
  dmi.bios.date: 01/09/2007
  dmi.bios.vendor: Phoenix Technologies, LTD
  dmi.bios.version: 6.00 PG
  dmi.board.name: NF-MCP61
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd01/09/2007:svn:pn:pvr:rvn:rnNF-MCP61:rvr:cvn:ct3:cvr:
  glxinfo: Error: [Errno 2] No such file or directory
  system:
   distro: Ubuntu
   codename:   lucid
   architecture:   x86_64
   kernel: 2.6.32-14-generic

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

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


[Kernel-packages] [Bug 1629260] Re: drdb kernal 4 crash

2016-10-05 Thread G. Kooistra
** Tags added: kernel-bug-exists-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/1629260

Title:
  drdb kernal 4 crash

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  After upgrading ubuntu 14.04 LTS from kernal 3 to kernal 4.4.0-38-generic, we 
got issues with DRBD.
  Especially during high load, the drdb kernal will gif issues.

  The DRBD status go's to a timeout and the server becomes unstable (also the 
KVM's running on it) and afther some minutes/hours, the system hangs.
  Only a hard reset is possible.

  This problem randomly appear after a few minutes / hours / days.

  Got this issue on multiple servers.
  The workaround is to go back to the old kernel.

  Logfiles:
  https://ubuntuforums.org/showthread.php?t=2336150

  
  Ubuntu version: 
  Description:Ubuntu 14.04.5 LTS
  Release:14.04

  drbd8-utils:
Installed: 2:8.4.4-1ubuntu1
Candidate: 2:8.4.4-1ubuntu1
Version table:
   *** 2:8.4.4-1ubuntu1 0
  500 http://nl.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
  100 /var/lib/dpkg/status

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

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


[Kernel-packages] [Bug 1628187] Re: vNIC driver missing in 4.8 kernel package

2016-10-05 Thread bugproxy
** Tags removed: targetmilestone-inin---
** Tags added: targetmilestone-inin1610

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

Title:
  vNIC driver missing in 4.8 kernel package

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

Bug description:
  == Comment: #0 - Ping Tian Han - 2016-09-22 01:20:10 ==
  ---Problem Description---
  There is on "ibmvnic" in 4.8.0-14-generic package:

  root@roselp2:~# uname -a
  Linux roselp2 4.8.0-14-generic #15-Ubuntu SMP Tue Sep 20 21:59:33 UTC 2016 
ppc64le ppc64le ppc64le GNU/Linux
  root@roselp2:~# modprobe ibmvnic
  modprobe: FATAL: Module ibmvnic not found in directory 
/lib/modules/4.8.0-14-generic
  root@roselp2:~# 

  so the vNIC device which  works well under 4.4 kernel doens't work
  now.

  == Comment: #6 - Kevin W. Rudd - 2016-09-27 11:49:32 ==
  From Bug 146781, this is still an issue with 4.8.0-17:

  ---
  Have installed lpar  using virtual  Ether adapter and after installation am 
not able to find vnic adapters 

  root@miglp2:~# modprobe ibmvnic
  modprobe: FATAL: Module ibmvnic not found in directory 
/lib/modules/4.8.0-17-generic
  root@miglp2:~#

  root@miglp2:~# ifconfig -a
  ibmveth2: flags=4163  mtu 1500
  inet 10.33.15.21  netmask 255.255.0.0  broadcast 10.33.255.255
  inet6 fe80::140f:bbff:fe6b:9502  prefixlen 64  scopeid 0x20
  inet6 2002:903:15f:1130:140f:bbff:fe6b:9502  prefixlen 64  scopeid 
0x0
  inet6 2002:926:3e2:1130:140f:bbff:fe6b:9502  prefixlen 64  scopeid 
0x0
  ether 16:0f:bb:6b:95:02  txqueuelen 1000  (Ethernet)
  RX packets 437923  bytes 29797431 (29.7 MB)
  RX errors 0  dropped 0  overruns 0  frame 0
  TX packets 153  bytes 13014 (13.0 KB)
  TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
  device interrupt 19

  lo: flags=73  mtu 65536
  inet 127.0.0.1  netmask 255.0.0.0
  inet6 ::1  prefixlen 128  scopeid 0x10
  loop  txqueuelen 1  (Local Loopback)
  RX packets 326  bytes 24184 (24.1 KB)
  RX errors 0  dropped 0  overruns 0  frame 0
  TX packets 326  bytes 24184 (24.1 KB)
  TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
  ---

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

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


[Kernel-packages] [Bug 1619552] Re: Failed to acknowledge elog: /sys/firmware/opal/elog/0x5018d709/acknowledge (2:No such file or directory)

2016-10-05 Thread Tim Gardner
Mukesh - you need to get your developers to look at this failure to
boot.

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

Title:
  Failed to acknowledge elog:
  /sys/firmware/opal/elog/0x5018d709/acknowledge (2:No such file or
  directory)

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

Bug description:
  == Comment: #0 - Mukesh K. Ojha  - 2016-09-02 02:10:14 ==
  ---Problem Description---
  Kernel is failed to free the kobject while acknowledging the error log which 
has been notified two times.
   
  Contact Information = Contact Information =  mukeo...@in.ibm.com 
   
  ---uname output---
  Ubuntu 16.04.01 LTS
   
  Machine Type = All power machine 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   
  Steps to reproduce:
  1.Boot the system to petitboot.
  2. Issue FSP Soft reset of Service Processor From ASMI page.
  3. After FSP comes up, boot the system to host OS.
  4. In the host OS seen the failure to acknowledge for one of elog.

  
  root@p8wookie ~]# service opal_errd status
  Redirecting to /bin/systemctl status  opal_errd.service
  opal_errd.service - opal_errd (PowerNV platform error handling) Service
 Loaded: loaded (/usr/lib/systemd/system/opal_errd.service; enabled)
 Active: active (running) since Wed 2016-08-03 07:55:03 CDT; 2min 4s ago
Process: 3452 ExecStart=/usr/libexec/ppc64-diag/opal_errd start 
(code=exited, status=0/SUCCESS)
   Main PID: 3497 (opal_errd)
 CGroup: /system.slice/opal_errd.service
 ??3497 /usr/sbin/opal_errd

  Aug 03 07:57:03 p8wookie.aus.stglabs.ibm.com ELOG[3497]: 
LID[5018d709]::SRC[B1763435]::Other Subsystems::Informational Event::No service 
action required
  Aug 03 07:57:03 p8wookie.aus.stglabs.ibm.com ELOG[3497]: Failed to 
acknowledge elog: /sys/firmware/opal/elog/0x5018d709/acknowledge (2:No such 
file or directory)
  Aug 03 07:57:04 p8wookie.aus.stglabs.ibm.com ELOG[3497]: 
LID[5018d709]::SRC[B1763435]::Other Subsystems::Informational Event::No service 
action required
  Aug 03 07:57:04 p8wookie.aus.stglabs.ibm.com ELOG[3497]: Failed to 
acknowledge elog: /sys/firmware/opal/elog/0x5018d709/acknowledge (2:No such 
file or directory)
  Aug 03 07:57:05 p8wookie.aus.stglabs.ibm.com ELOG[3497]: 
LID[5018d709]::SRC[B1763435]::Other Subsystems::Informational Event::No service 
action required
  Aug 03 07:57:05 p8wookie.aus.stglabs.ibm.com ELOG[3497]: Failed to 
acknowledge elog: /sys/firmware/opal/elog/0x5018d709/acknowledge (2:No such 
file or directory)
  Aug 03 07:57:06 p8wookie.aus.stglabs.ibm.com ELOG[3497]: 
LID[5018d709]::SRC[B1763435]::Other Subsystems::Informational Event::No service 
action required
  Aug 03 07:57:06 p8wookie.aus.stglabs.ibm.com ELOG[3497]: Failed to 
acknowledge elog: /sys/firmware/opal/elog/0x5018d709/acknowledge (2:No such 
file or directory)
  Aug 03 07:57:07 p8wookie.aus.stglabs.ibm.com ELOG[3497]: 
LID[5018d709]::SRC[B1763435]::Other Subsystems::Informational Event::No service 
action required
  Aug 03 07:57:07 p8wookie.aus.stglabs.ibm.com ELOG[3497]: Failed to 
acknowledge elog: /sys/firmware/opal/elog/0x5018d709/acknowledge (2:No such 
file or directory)


  
  [root@p8wookie ~]# cd /sys/firmware/opal/elog/
  [root@p8wookie elog]# ls
  0x5018d709
  [root@p8wookie elog]# 
   
  Stack trace output:
   no
   
  Oops output:
   no
   
  System Dump Info:
The system is not configured to capture a system dump.
   
  *Additional Instructions for Contact Information =  mukeo...@in.ibm.com: 
  -Attach sysctl -a output output to the bug.

  == Comment: #1 - Mukesh K. Ojha  - 2016-09-02 02:12:45 ==
  Upstream commit :

  commit a9cbf0b2195b695cbcaa4e2770948c212e9a
  Author: Mukesh Ojha 
  Date:   Mon Aug 22 12:17:44 2016 +0530

  powerpc/powernv : Drop reference added by kset_find_obj()
  
  In a situation, where Linux kernel gets notified about duplicate error log
  from OPAL, it is been observed that kernel fails to remove sysfs entries
  (/sys/firmware/opal/elog/0x) of such error logs. This is because,
  we currently search the error log/dump kobject in the kset list via
  'kset_find_obj()' routine. Which eventually increment the reference count
  by one, once it founds the kobject.

  
  Above patch is the solution of this bugzilla.

  Kindly pull this patch in for both Ubuntu 16.04 LTS and Ubuntu 16.10.

  -Mukesh

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

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

[Kernel-packages] [Bug 1628187] Re: vNIC driver missing in 4.8 kernel package

2016-10-05 Thread bugproxy
** Tags added: bugnameltc-146617 severity-critical

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

Title:
  vNIC driver missing in 4.8 kernel package

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

Bug description:
  == Comment: #0 - Ping Tian Han - 2016-09-22 01:20:10 ==
  ---Problem Description---
  There is on "ibmvnic" in 4.8.0-14-generic package:

  root@roselp2:~# uname -a
  Linux roselp2 4.8.0-14-generic #15-Ubuntu SMP Tue Sep 20 21:59:33 UTC 2016 
ppc64le ppc64le ppc64le GNU/Linux
  root@roselp2:~# modprobe ibmvnic
  modprobe: FATAL: Module ibmvnic not found in directory 
/lib/modules/4.8.0-14-generic
  root@roselp2:~# 

  so the vNIC device which  works well under 4.4 kernel doens't work
  now.

  == Comment: #6 - Kevin W. Rudd - 2016-09-27 11:49:32 ==
  From Bug 146781, this is still an issue with 4.8.0-17:

  ---
  Have installed lpar  using virtual  Ether adapter and after installation am 
not able to find vnic adapters 

  root@miglp2:~# modprobe ibmvnic
  modprobe: FATAL: Module ibmvnic not found in directory 
/lib/modules/4.8.0-17-generic
  root@miglp2:~#

  root@miglp2:~# ifconfig -a
  ibmveth2: flags=4163  mtu 1500
  inet 10.33.15.21  netmask 255.255.0.0  broadcast 10.33.255.255
  inet6 fe80::140f:bbff:fe6b:9502  prefixlen 64  scopeid 0x20
  inet6 2002:903:15f:1130:140f:bbff:fe6b:9502  prefixlen 64  scopeid 
0x0
  inet6 2002:926:3e2:1130:140f:bbff:fe6b:9502  prefixlen 64  scopeid 
0x0
  ether 16:0f:bb:6b:95:02  txqueuelen 1000  (Ethernet)
  RX packets 437923  bytes 29797431 (29.7 MB)
  RX errors 0  dropped 0  overruns 0  frame 0
  TX packets 153  bytes 13014 (13.0 KB)
  TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
  device interrupt 19

  lo: flags=73  mtu 65536
  inet 127.0.0.1  netmask 255.0.0.0
  inet6 ::1  prefixlen 128  scopeid 0x10
  loop  txqueuelen 1  (Local Loopback)
  RX packets 326  bytes 24184 (24.1 KB)
  RX errors 0  dropped 0  overruns 0  frame 0
  TX packets 326  bytes 24184 (24.1 KB)
  TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
  ---

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

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


[Kernel-packages] [Bug 1609242] Re: Kernels 4.3-4.8 result in blackscreen - Intel Ivybridge

2016-10-05 Thread harry
Same issue as before. As with all of the 4.1 kernels, the screen freezes
before going into Plymouth.  Only the cursor is visible and I have to
manually restart the computer.

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

Title:
  Kernels 4.3-4.8 result in blackscreen - Intel Ivybridge

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

Bug description:
  When I install Ubuntu 16.04 on my computer the screen goes blank at
  login. I can blindly login and it boots but I cannot use the display
  (external monitor through HDMI).

  I've looked online for an answer to this issue but could not find a
  solution.  However, many people report this issue in forums with the
  4.4x kernel.

  On my main computer, I upgraded from 14.04 to 16.04.1. On this
  computer I was able to switch back to the 3.13 kernel which *does
  work*.

  On the same computer, if I use a 16.04 live CD, it does the same
  thing.  The screen goes blank.

  UEFI may be part of the issue as well.  I have it disabled in bios
  (set to legacy mode) but when I first boot, it seems to go into UEFI
  mode first and then, after rebooting with  it shows
  me the list of kernels. I can select the kernel from there but if I
  use a 4.4x kernel, it blanks out at encryption passphrase screen.

  There are also people with similar issues on AskUbuntu.

  Here's some basic HW info.  If you require more, please ask.

  sudo lshw | head
  zbox
  description: Notebook
  product: ZBOX-ID18 (NA)
  vendor: ZOTAC
  version: XX
  serial: G211X
  width: 64 bits
  capabilities: smbios-2.7 dmi-2.7 vsyscall32
  configuration: boot=normal chassis=notebook family=NA sku=NA 
uuid=00020003-0004-0005-0006-000700080009
    *-core

  sudo lshw -C display
    *-display
     description: VGA compatible controller
     product: 3rd Gen Core processor Graphics Controller
     vendor: Intel Corporation
     physical id: 2
     bus info: pci@:00:02.0
     version: 09
     width: 64 bits
     clock: 33MHz
     capabilities: msi pm vga_controller bus_master cap_list rom
     configuration: driver=i915 latency=0
     resources: irq:45 memory:f780-f7bf memory:e000-efff 
ioport:f000(size=64)

  lsb_release -rd
  Description:  Ubuntu 16.04.1 LTS
  Release:  16.04
  ---
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  user5536 F pulseaudio
  DistroRelease: Ubuntu 16.04
  HibernationDevice: #RESUME=UUID=edaa55c6-eb56-43fb-8004-495948b72b38
  InstallationDate: Installed on 2014-07-23 (743 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140313)
  MachineType: ZOTAC ZBOX-ID18
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-92-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash
  ProcVersionSignature: Ubuntu 3.13.0-92.139-generic 3.13.11-ckt39
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-92-generic N/A
   linux-backports-modules-3.13.0-92-generic  N/A
   linux-firmware 1.157.2
  RfKill:

  StagingDrivers: rts5139
  Tags:  xenial staging
  Uname: Linux 3.13.0-92-generic x86_64
  UpgradeStatus: Upgraded to xenial on 2016-07-31 (3 days ago)
  UserGroups:

  _MarkForUpload: True
  dmi.bios.date: 03/13/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: B211P011
  dmi.board.asset.tag: NA
  dmi.board.name: ZBOX-ID18
  dmi.board.vendor: ZOTAC
  dmi.board.version: XX
  dmi.chassis.asset.tag: NA
  dmi.chassis.type: 10
  dmi.chassis.vendor: NA
  dmi.chassis.version: NA
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrB211P011:bd03/13/2014:svnZOTAC:pnZBOX-ID18:pvrXX:rvnZOTAC:rnZBOX-ID18:rvrXX:cvnNA:ct10:cvrNA:
  dmi.product.name: ZBOX-ID18
  dmi.product.version: XX
  dmi.sys.vendor: ZOTAC

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

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


[Kernel-packages] [Bug 1607920] Re: zfs services fail on firstboot if zfs-utils is integrated into the deployment image

2016-10-05 Thread Andy Whitcroft
Hello Dave, or anyone else affected,

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

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

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

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

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

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

Title:
  zfs services fail on firstboot if zfs-utils is integrated into the
  deployment image

Status in sysvinit package in Ubuntu:
  Won't Fix
Status in zfs-linux package in Ubuntu:
  Fix Released
Status in sysvinit source package in Xenial:
  Won't Fix
Status in zfs-linux source package in Xenial:
  Fix Committed

Bug description:
  [Impact]

   * zfs services fail on firstboot if zfs-utils is integrated into the
  deployment image.

   * Output from systemd -
  sudo systemctl --failed
  UNIT LOAD ACTIVE SUB DESCRIPTION
  ● zfs-import-scan.service loaded failed failed Import ZFS pools by device 
scanning
  ● zfs-mount.service loaded failed failed Mount ZFS filesystems

   * This is particularly frustrating for users who use automated
  monitoring as it means virtual machines must always be restarted
  before showing as clean.

   * This failure is due to zfs services starting up before /etc/mtab
  has a chance to be symlinked to /proc/mounts.

  [Test Case]

   1. Grab a stock xenial image, and unpack it and add zfs-utils to it.  Repack 
it.
   2. Boot machine
   3. Check systemctl --failed.

  [Regression Potential]

   * none expected, patch has been intensively tested by the upsteam zfs
  test script suite.

   * This is a upstream commit merge in 0.7.0.

   * A ubuntu package has been tested (including the upstream commit) by
  a user of the community facing this bug, and confirmed it addresses
  the problem (see comment #7).

  [Other Info]

  * The "reading" is redirected to /proc/self/mounts. 
  The writing to /etc/mtab. Some distros still need that. The current hope is 
to replace the writing (and maybe reading) with libmount, in a second phase.

  
   * Upstream commit : 
https://github.com/zfsonlinux/zfs/commit/792517389fad5c495a2738b61c2e9c65dedaaa9a

   * Upstream bug: https://github.com/zfsonlinux/zfs/issues/4680

   * Debian bug : https://bugs.debian.org/cgi-
  bin/bugreport.cgi?bug=839071

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

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


[Kernel-packages] [Bug 1628279] Re: python utilities script suffix (.py) should be removed as per Policy 10.4

2016-10-05 Thread Andy Whitcroft
Hello Eric, or anyone else affected,

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

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

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

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

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

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

Title:
  python utilities script suffix (.py) should be removed as per Policy
  10.4

Status in zfs-linux package in Ubuntu:
  Fix Released
Status in zfs-linux source package in Xenial:
  Fix Committed

Bug description:
  [Impact]

  The zfs utilities scripts shipped with debian and ubuntu such as :

  * arc_summary.py : Provides a summary of the statistics
  * arcstat.py : Print out ZFS ARC Statistics exported via kstat(1)
  * dbufstat.py : Print out statistics for all cached dmu buffers

  should be renamed according to Policy 10.4 :
  https://www.debian.org/doc/debian-policy/ch-files.html#s-scripts

  "When scripts are installed into a directory in the system PATH, the
  script name should not include an extension such as .sh or .pl that
  denotes the scripting language currently used to implement it."

  Ideally, this should be fixed and upstreamed to Debian (or to zfslinux
  upstream) as well.

  [Test Case]

   * Install zfsutils-linux
   * List files

   $ dpkg -L zfsutils-linux | egrep "arc|dbufstat"
     /usr/sbin/arc_summary.py
     /usr/sbin/arcstat.py
     /usr/sbin/dbufstat.py

  [Regression Potential]

   * none expected, this is a trivial change that simply rename the
  scripts to remove the extension (.py) with a simple 'mv' before the
  dh_install invocation in order to get this expected result :

  $ dpkg -L zfsutils-linux | egrep -i "arc|dbuf"
    /usr/sbin/arc_summary
    /usr/sbin/arcstat
    /usr/sbin/dbufstat

  Yakkety include the renaming as shown above.

  Xenial will have a symlink to not break user experience until next release 
upgrade:
  
https://bugs.launchpad.net/ubuntu/xenial/+source/zfs-linux/+bug/1628279/comments/19

  So user will be able to use both for instance : arcstat.py or arcstat

  
  [Other Info]

   * Justification/argument for Xenial
  https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1628279/comments/13
  https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1628279/comments/14

  * Debian bug
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=839645

   * Upstream (ZoL) is reluctant to change it at upstream code level.
  https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1628279/comments/2

   * This has been flag by Adam Conrad
  https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1574342/comments/19

   * Debian policy
  https://www.debian.org/doc/debian-policy/ch-files.html#s-scripts

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

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


[Kernel-packages] [Bug 1607920] Re: zfs services fail on firstboot if zfs-utils is integrated into the deployment image

2016-10-05 Thread Eric Desrochers
@apw

With regard to the translation 

The commit has been intensively tested in different scenarios/env/...
and of course with the "ZFS Test Suite"[1] which include functionality,
perf, and stress tests.

All the tests were reported as successful.

I hope this answer your questions and addresses your concern.

Let rlaager and I know if you need more clarifications.

[1] - https://github.com/zfsonlinux/zfs/tree/master/tests

Eric

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

Title:
  zfs services fail on firstboot if zfs-utils is integrated into the
  deployment image

Status in sysvinit package in Ubuntu:
  Won't Fix
Status in zfs-linux package in Ubuntu:
  Fix Released
Status in sysvinit source package in Xenial:
  Won't Fix
Status in zfs-linux source package in Xenial:
  In Progress

Bug description:
  [Impact]

   * zfs services fail on firstboot if zfs-utils is integrated into the
  deployment image.

   * Output from systemd -
  sudo systemctl --failed
  UNIT LOAD ACTIVE SUB DESCRIPTION
  ● zfs-import-scan.service loaded failed failed Import ZFS pools by device 
scanning
  ● zfs-mount.service loaded failed failed Mount ZFS filesystems

   * This is particularly frustrating for users who use automated
  monitoring as it means virtual machines must always be restarted
  before showing as clean.

   * This failure is due to zfs services starting up before /etc/mtab
  has a chance to be symlinked to /proc/mounts.

  [Test Case]

   1. Grab a stock xenial image, and unpack it and add zfs-utils to it.  Repack 
it.
   2. Boot machine
   3. Check systemctl --failed.

  [Regression Potential]

   * none expected, patch has been intensively tested by the upsteam zfs
  test script suite.

   * This is a upstream commit merge in 0.7.0.

   * A ubuntu package has been tested (including the upstream commit) by
  a user of the community facing this bug, and confirmed it addresses
  the problem (see comment #7).

  [Other Info]

  * The "reading" is redirected to /proc/self/mounts. 
  The writing to /etc/mtab. Some distros still need that. The current hope is 
to replace the writing (and maybe reading) with libmount, in a second phase.

  
   * Upstream commit : 
https://github.com/zfsonlinux/zfs/commit/792517389fad5c495a2738b61c2e9c65dedaaa9a

   * Upstream bug: https://github.com/zfsonlinux/zfs/issues/4680

   * Debian bug : https://bugs.debian.org/cgi-
  bin/bugreport.cgi?bug=839071

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

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


[Kernel-packages] [Bug 1630279] Re: linux: 4.8.0-21.23 -proposed tracker

2016-10-05 Thread Andy Whitcroft
** Tags added: block-proposed

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

Title:
  linux: 4.8.0-21.23 -proposed tracker

Status in Kernel Development Workflow:
  In Progress
Status in Kernel Development Workflow automated-testing series:
  New
Status in Kernel Development Workflow prepare-package series:
  Confirmed
Status in Kernel Development Workflow prepare-package-meta series:
  Confirmed
Status in Kernel Development Workflow prepare-package-signed series:
  Confirmed
Status in Kernel Development Workflow promote-to-proposed series:
  New
Status in Kernel Development Workflow promote-to-release series:
  New
Status in Kernel Development Workflow regression-testing series:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Yakkety:
  Confirmed

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

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

  kernel-phase-changed:Tuesday, 04. October 2016 15:16 UTC
  kernel-phase:Packaging

  -- swm properties --
  derivative-trackers-created: true
  phase: Packaging

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-development-workflow/+bug/1630279/+subscriptions

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


[Kernel-packages] [Bug 1607920] Re: zfs services fail on firstboot if zfs-utils is integrated into the deployment image

2016-10-05 Thread Eric Desrochers
@apw

To answer your question: 
"Also as you are changing MNTTAB is there any reason not to be using that here?"

The "reading" is redirected to /proc/self/mounts and the "writing" to
/etc/mtab, but if it doesn't exist, that's fine. ZFS just won't update
/etc/mtab.

Ideally, ZFS should be integrated with libmount in a second phase (ZoL
maintainers are aware that eventually a 2nd is needed to integrate
libmount), until then /proc/self/mounts is a viable solution to address
issues cause by mtab.

Eric

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

Title:
  zfs services fail on firstboot if zfs-utils is integrated into the
  deployment image

Status in sysvinit package in Ubuntu:
  Won't Fix
Status in zfs-linux package in Ubuntu:
  Fix Released
Status in sysvinit source package in Xenial:
  Won't Fix
Status in zfs-linux source package in Xenial:
  In Progress

Bug description:
  [Impact]

   * zfs services fail on firstboot if zfs-utils is integrated into the
  deployment image.

   * Output from systemd -
  sudo systemctl --failed
  UNIT LOAD ACTIVE SUB DESCRIPTION
  ● zfs-import-scan.service loaded failed failed Import ZFS pools by device 
scanning
  ● zfs-mount.service loaded failed failed Mount ZFS filesystems

   * This is particularly frustrating for users who use automated
  monitoring as it means virtual machines must always be restarted
  before showing as clean.

   * This failure is due to zfs services starting up before /etc/mtab
  has a chance to be symlinked to /proc/mounts.

  [Test Case]

   1. Grab a stock xenial image, and unpack it and add zfs-utils to it.  Repack 
it.
   2. Boot machine
   3. Check systemctl --failed.

  [Regression Potential]

   * none expected, patch has been intensively tested by the upsteam zfs
  test script suite.

   * This is a upstream commit merge in 0.7.0.

   * A ubuntu package has been tested (including the upstream commit) by
  a user of the community facing this bug, and confirmed it addresses
  the problem (see comment #7).

  [Other Info]

  * The "reading" is redirected to /proc/self/mounts. 
  The writing to /etc/mtab. Some distros still need that. The current hope is 
to replace the writing (and maybe reading) with libmount, in a second phase.

  
   * Upstream commit : 
https://github.com/zfsonlinux/zfs/commit/792517389fad5c495a2738b61c2e9c65dedaaa9a

   * Upstream bug: https://github.com/zfsonlinux/zfs/issues/4680

   * Debian bug : https://bugs.debian.org/cgi-
  bin/bugreport.cgi?bug=839071

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

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


  1   2   >