date:20170829

** Package changed: linux-meta (Ubuntu) => linux (Ubuntu)

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

Title:
  package linux-image-generic 4.4.0.93.98 failed to install/upgrade:
  依存関係の問題 - 設定を見送ります

Status in linux package in Ubuntu:
  New

Bug description:
  An error keeps showing all the time.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-image-generic 4.4.0.93.98
  ProcVersionSignature: Ubuntu 4.4.0-92.115-generic 4.4.76
  Uname: Linux 4.4.0-92-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  cercel 1589 F pulseaudio
   /dev/snd/controlC0:  cercel 1589 F pulseaudio
   /dev/snd/controlC1:  cercel 1589 F pulseaudio
  Date: Tue Aug 29 09:12:17 2017
  ErrorMessage: 依存関係の問題 - 設定を見送ります
  HibernationDevice: RESUME=UUID=2f9ea4eb-db18-4e97-8c6a-c29bd0b47b46
  InstallationDate: Installed on 2017-08-14 (14 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  IwConfig:
   enp2s0no wireless extensions.
   
   lono wireless extensions.
  MachineType: Gigabyte Technology Co., Ltd. H81M-S2H
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-92-generic.efi.signed 
root=UUID=051c84c8-cdd1-4c3e-9f87-3418934f163c ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc N/A
  RfKill:
   
  SourcePackage: linux-meta
  Title: package linux-image-generic 4.4.0.93.98 failed to install/upgrade: 
依存関係の問題 - 設定を見送ります
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/11/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F2
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H81M-S2H
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF2:bd08/11/2015:svnGigabyteTechnologyCo.,Ltd.:pnH81M-S2H:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnH81M-S2H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: H81M-S2H
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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

[Kernel-packages] [Bug 1713638] Re: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu1~1.1: bcmwl kernel module failed to build

2017-08-29 Thread Apport retracing service

** Tags removed: need-duplicate-check

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

Title:
  bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu1~1.1: bcmwl kernel
  module failed to build

Status in bcmwl package in Ubuntu:
  New

Bug description:
  bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu1~1.1: bcmwl kernel
  module failed to build

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu1~1.1
  ProcVersionSignature: Ubuntu 4.11.0-14.20~16.04.1-generic 4.11.12
  Uname: Linux 4.11.0-14-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  DKMSKernelVersion: 4.11.0-14-generic
  Date: Sun Aug 27 20:05:06 2017
  DuplicateSignature: 
dkms:bcmwl-kernel-source:6.30.223.271+bdcom-0ubuntu1~1.1:/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c:2922:10:
 error: ‘struct net_device’ has no member named ‘last_rx’
  InstallationDate: Installed on 2016-09-21 (342 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  PackageVersion: 6.30.223.271+bdcom-0ubuntu1~1.1
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.19
  SourcePackage: bcmwl
  Title: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu1~1.1: bcmwl kernel 
module failed to build
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

Re: [Kernel-packages] [Bug 1700834] Re: Intel i40e PF reset under load

2017-08-29 Thread Björn Zettergren

>
> There is one additional upstream commit required to fully fix this,
> please see bug 1713553.
>

Ah, nice! Thanks for pointing it out, i had not found it myself. I solved
my problems temporarily by adding i40e 2.0.30 driver as dkms to my current
system and will follow the other bug (the i40e 2.1.26 leaked memory at an
alarming rate, but that's a story for a different bugreport maybe).

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

Title:
  Intel i40e PF reset under load

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

Bug description:
  SRU Justification:

  Impact:

Using an Intel i40e network device, under heavy traffic load with
  TSO enabled, the device will spontaneously reset itself and issue errors
  similar to the following:

  Jun 14 14:09:51 hostname kernel: [4253913.851053] i40e :05:00.1: TX 
driver issue detected, PF reset issued 
  Jun 14 14:09:53 hostname kernel: [4253915.476283] i40e :05:00.1: TX 
driver issue detected, PF reset issued 
  Jun 14 14:09:54 hostname kernel: [4253917.411264] i40e :05:00.1: TX 
driver issue detected, PF reset issued 

This causes a full reset of the PF, which causes an interruption
  in traffic flow.

In this case, these errors arise from a bug in the i40e device
  driver introduced by commit:

  commit 584a837e26408c66e87df87a022faa6a54c2b020
  Author: Alexander Duyck 
  Date:   Wed Feb 17 11:02:50 2016 -0800

  i40e/i40evf: Rewrite logic for 8 descriptor per packet check

This patch was added to the Xenial kernel beginning with version
  4.4.0-8.23.  This bug does not manifest on any other Ubuntu kernel series.

  
  Fix:

  This error is resolved upstream by:

  commit 3f3f7cb875c0f621485644d4fd7453b0d37f00e4
  Author: Alexander Duyck 
  Date:   Wed Mar 30 16:15:37 2016 -0700

  i40e/i40evf: Limit TSO to 7 descriptors for payload instead of 8 per 
packet
  
This fix was never backported into the Xenial 4.4 kernel series.
  

  Testcase:

In this case, the issue occurs at a customer site using i40e based
  Intel network cards with SR-IOV enabled.  Under heavy load, the card will
  reset itself as described.  The customer has tested the 3f3f7cb875c patch
  in their environment and confirmed that it resolves the issue.

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

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

[Kernel-packages] [Bug 1713576] Re: More migrations with constant load

2017-08-29 Thread Andrew Cloke

** Also affects: ubuntu-power-systems
   Importance: Undecided
   Status: New

** Changed in: ubuntu-power-systems
   Importance: Undecided => High

** Changed in: ubuntu-power-systems
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

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

Title:
  More migrations with constant load

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

Bug description:
  == Comment: #0 - PUVICHAKRAVARTHY RAMACHANDRAN  - 2017-08-06 13:44:45 ==
  ---Problem Description---
  Significantly higher number of task migrations when the load is fixed but not 
balanced across cores.
   
  ---uname output---
  Linux isvbos3 4.10.0-29-generic #33~16.04.1-Ubuntu SMP Tue Jul 25 18:17:06 
UTC 2017 ppc64le ppc64le ppc64le GNU/Linux
   
  ---Additional Hardware Info---
  Power9 dd2.0 

  Machine Type = Power9 
   
  ---Steps to Reproduce---
   Benchmark : Multithreaded - cpu intensive. The system had 2 socket/ 32 
cores/ SMT4 mode.

  When 64 threads was run - the migrations were less over 10s interval.
  when 80 threads were run - the migrations were very high.

  Ideally, it should have been very minimal, as the over all load was constant
   
  == Comment: #3 - SRIKAR DRONAMRAJU - 2017-08-11 06:56:47 ==
  As suspected (commit :  05b40e0577 : "sched/fair: Prefer sibiling only if 
local group is under-utilized")
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=05b40e0577
  should fix the problem

  Ran ' perf stat -a -r 5 -e sched:sched_migrate_task 
/home/srikar/work/ebizzy-0.3/ebizzy -t 35 -S 100'
  to detect the problem and verify the fix

  Here is perf stat without fix.

  Performance counter stats for 'system wide' (5 runs):

   7,758  sched:sched_migrate_task
  ( +-  1.28% )

   100.015658079 seconds time elapsed
  ( +-  0.00% )

  perf stat with fix.

  Performance counter stats for 'system wide' (5 runs):

 415  sched:sched_migrate_task
  ( +- 11.74% )

   100.016021787 seconds time elapsed
  ( +-  0.00% )

  
  git describe on upstream kernel says v4.11-rc2
  # git describe 05b40e0577
  v4.11-rc2-227-g05b40e0

  == Comment: #4 - SRIKAR DRONAMRAJU - 2017-08-11 07:05:37 ==
  Attaching the patch that needs to be applied to fix this bug.
  Verified that patch fixes the problem.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1713576/+subscriptions

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

[Kernel-packages] [Bug 1713575] Re: Vlun resize request could fail with cxlflash driver

2017-08-29 Thread Andrew Cloke

** Also affects: ubuntu-power-systems
   Importance: Undecided
   Status: New

** Changed in: ubuntu-power-systems
   Importance: Undecided => High

** Changed in: ubuntu-power-systems
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

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

Title:
  Vlun resize request could fail with cxlflash driver

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

Bug description:
  == Comment: #0 - UMA KRISHNAN  - 2017-08-28 12:14:12 ==
  ---Problem Description---
  Recently a regression in cxlflash driver was identified and a fix has been 
upstreamed to  kernel.org. We would like to get that included in Xenial 16.04.3 
SRU (HWE v4.10 kernel). Even though regression patch is the very last one, I 
have also listed the missing patches in-between, that are minor and will be 
easier for further cxlflash updates to Xenial.

  eeac8cda2c957e156093933b860eec09e488fe15 scsi: cxlflash: return -EFAULT if 
copy_from_user() fails
  9ff870417e56b1fb7b15b2cda74de639d3cd8559 scsi: cxlflash: Fix an error 
handling path in 'cxlflash_disk_attach()'
  48a17ad5931c3832eec68411620bc3527021c193 scsi: cxlflash: Remove unnecessary 
existence check
  1a9e394154e34728f58c1f697b993aaaf89a4db2 scsi: cxlflash: Avoid double mutex 
unlock
  07a191f762a7b8d0db13c38036380927116e29bb scsi: cxlflash: Fix vlun resize 
failure in the shrink path
   
  ---Steps to Reproduce---
   Vlun resize request could fail after updating to a kernel that includes 
Commit 565180723294 ("scsi: cxlflash: SISlite updates to support 4 ports")

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1713575/+subscriptions

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

[Kernel-packages] [Bug 1713642] [NEW] package linux-image-4.10.0-33-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 128

2017-08-29 Thread Neil Groves

Public bug reported:

This happened during a routine system update. The update was triggered
by selecting "Update All" from the notification area running a Gnome 3
shell. Perhaps a related issue is a continual failure to update a
logitech bluetooth receiver firmware. This never completes, and perhaps
messes up the dependencies.

ProblemType: Package
DistroRelease: Ubuntu 17.04
Package: linux-image-4.10.0-33-generic (not installed)
ProcVersionSignature: Ubuntu 4.10.0-32.36-generic 4.10.17
Uname: Linux 4.10.0-32-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.4-0ubuntu4.5
Architecture: amd64
Date: Mon Aug 28 15:49:34 2017
ErrorMessage: subprocess new pre-installation script returned error exit status 
128
HibernationDevice: RESUME=UUID=e4700f4b-00b7-4d9f-845d-c5cf7052e75d
InstallationDate: Installed on 2016-03-17 (529 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
IwConfig:
 lono wireless extensions.
 
 enp12s0   no wireless extensions.
 
 enp8s0no wireless extensions.
MachineType: Gigabyte Technology Co., Ltd. P67A-UD7
ProcFB:
 
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-32-generic 
root=UUID=ecfd487c-51d8-42cd-9892-a0c3c8de9efb ro 
usbhid.quirks=1b1c:1b13:0x2408
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions: grub-pc 2.02~beta3-4ubuntu2.2
RfKill:
 
SourcePackage: linux
Title: package linux-image-4.10.0-33-generic (not installed) failed to 
install/upgrade: subprocess new pre-installation script returned error exit 
status 128
UpgradeStatus: Upgraded to zesty on 2017-04-18 (132 days ago)
dmi.bios.date: 03/31/2011
dmi.bios.vendor: Award Software International, Inc.
dmi.bios.version: F8
dmi.board.name: P67A-UD7
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF8:bd03/31/2011:svnGigabyteTechnologyCo.,Ltd.:pnP67A-UD7:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnP67A-UD7:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
dmi.product.name: P67A-UD7
dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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


** Tags: amd64 apport-package zesty

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

Title:
  package linux-image-4.10.0-33-generic (not installed) failed to
  install/upgrade: subprocess new pre-installation script returned error
  exit status 128

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This happened during a routine system update. The update was triggered
  by selecting "Update All" from the notification area running a Gnome 3
  shell. Perhaps a related issue is a continual failure to update a
  logitech bluetooth receiver firmware. This never completes, and
  perhaps messes up the dependencies.

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-33-generic (not installed)
  ProcVersionSignature: Ubuntu 4.10.0-32.36-generic 4.10.17
  Uname: Linux 4.10.0-32-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  Date: Mon Aug 28 15:49:34 2017
  ErrorMessage: subprocess new pre-installation script returned error exit 
status 128
  HibernationDevice: RESUME=UUID=e4700f4b-00b7-4d9f-845d-c5cf7052e75d
  InstallationDate: Installed on 2016-03-17 (529 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  IwConfig:
   lono wireless extensions.
   
   enp12s0   no wireless extensions.
   
   enp8s0no wireless extensions.
  MachineType: Gigabyte Technology Co., Ltd. P67A-UD7
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-32-generic 
root=UUID=ecfd487c-51d8-42cd-9892-a0c3c8de9efb ro 
usbhid.quirks=1b1c:1b13:0x2408
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc 2.02~beta3-4ubuntu2.2
  RfKill:
   
  SourcePackage: linux
  Title: package linux-image-4.10.0-33-generic (not installed) failed to 
install/upgrade: subprocess new pre-installation script returned error exit 
status 128
  UpgradeStatus: Upgraded to zesty on 2017-04-18 (132 days ago)
  dmi.bios.date: 03/31/2011
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F8
  dmi.board.name: P67A-UD7
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF8:bd03/31/2011:svnGigabyteTechnologyCo.,Ltd.:pnP67A-UD7:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnP67A-UD7:rvr:cvnGigabyteTechnologyCo

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

This change was made by a bot.

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

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

Title:
  package linux-image-4.10.0-33-generic (not installed) failed to
  install/upgrade: subprocess new pre-installation script returned error
  exit status 128

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This happened during a routine system update. The update was triggered
  by selecting "Update All" from the notification area running a Gnome 3
  shell. Perhaps a related issue is a continual failure to update a
  logitech bluetooth receiver firmware. This never completes, and
  perhaps messes up the dependencies.

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-33-generic (not installed)
  ProcVersionSignature: Ubuntu 4.10.0-32.36-generic 4.10.17
  Uname: Linux 4.10.0-32-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  Date: Mon Aug 28 15:49:34 2017
  ErrorMessage: subprocess new pre-installation script returned error exit 
status 128
  HibernationDevice: RESUME=UUID=e4700f4b-00b7-4d9f-845d-c5cf7052e75d
  InstallationDate: Installed on 2016-03-17 (529 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  IwConfig:
   lono wireless extensions.
   
   enp12s0   no wireless extensions.
   
   enp8s0no wireless extensions.
  MachineType: Gigabyte Technology Co., Ltd. P67A-UD7
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-32-generic 
root=UUID=ecfd487c-51d8-42cd-9892-a0c3c8de9efb ro 
usbhid.quirks=1b1c:1b13:0x2408
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc 2.02~beta3-4ubuntu2.2
  RfKill:
   
  SourcePackage: linux
  Title: package linux-image-4.10.0-33-generic (not installed) failed to 
install/upgrade: subprocess new pre-installation script returned error exit 
status 128
  UpgradeStatus: Upgraded to zesty on 2017-04-18 (132 days ago)
  dmi.bios.date: 03/31/2011
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F8
  dmi.board.name: P67A-UD7
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF8:bd03/31/2011:svnGigabyteTechnologyCo.,Ltd.:pnP67A-UD7:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnP67A-UD7:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: P67A-UD7
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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

[Kernel-packages] [Bug 1713642] Re: package linux-image-4.10.0-33-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 128

2017-08-29 Thread Apport retracing service

** Tags removed: need-duplicate-check

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

Title:
  package linux-image-4.10.0-33-generic (not installed) failed to
  install/upgrade: subprocess new pre-installation script returned error
  exit status 128

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This happened during a routine system update. The update was triggered
  by selecting "Update All" from the notification area running a Gnome 3
  shell. Perhaps a related issue is a continual failure to update a
  logitech bluetooth receiver firmware. This never completes, and
  perhaps messes up the dependencies.

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-33-generic (not installed)
  ProcVersionSignature: Ubuntu 4.10.0-32.36-generic 4.10.17
  Uname: Linux 4.10.0-32-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  Date: Mon Aug 28 15:49:34 2017
  ErrorMessage: subprocess new pre-installation script returned error exit 
status 128
  HibernationDevice: RESUME=UUID=e4700f4b-00b7-4d9f-845d-c5cf7052e75d
  InstallationDate: Installed on 2016-03-17 (529 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  IwConfig:
   lono wireless extensions.
   
   enp12s0   no wireless extensions.
   
   enp8s0no wireless extensions.
  MachineType: Gigabyte Technology Co., Ltd. P67A-UD7
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-32-generic 
root=UUID=ecfd487c-51d8-42cd-9892-a0c3c8de9efb ro 
usbhid.quirks=1b1c:1b13:0x2408
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc 2.02~beta3-4ubuntu2.2
  RfKill:
   
  SourcePackage: linux
  Title: package linux-image-4.10.0-33-generic (not installed) failed to 
install/upgrade: subprocess new pre-installation script returned error exit 
status 128
  UpgradeStatus: Upgraded to zesty on 2017-04-18 (132 days ago)
  dmi.bios.date: 03/31/2011
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F8
  dmi.board.name: P67A-UD7
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF8:bd03/31/2011:svnGigabyteTechnologyCo.,Ltd.:pnP67A-UD7:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnP67A-UD7:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: P67A-UD7
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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

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

This change was made by a bot.

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

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

Title:
  package linux-image-generic 4.4.0.93.98 failed to install/upgrade:
  依存関係の問題 - 設定を見送ります

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  An error keeps showing all the time.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-image-generic 4.4.0.93.98
  ProcVersionSignature: Ubuntu 4.4.0-92.115-generic 4.4.76
  Uname: Linux 4.4.0-92-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  cercel 1589 F pulseaudio
   /dev/snd/controlC0:  cercel 1589 F pulseaudio
   /dev/snd/controlC1:  cercel 1589 F pulseaudio
  Date: Tue Aug 29 09:12:17 2017
  ErrorMessage: 依存関係の問題 - 設定を見送ります
  HibernationDevice: RESUME=UUID=2f9ea4eb-db18-4e97-8c6a-c29bd0b47b46
  InstallationDate: Installed on 2017-08-14 (14 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  IwConfig:
   enp2s0no wireless extensions.
   
   lono wireless extensions.
  MachineType: Gigabyte Technology Co., Ltd. H81M-S2H
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-92-generic.efi.signed 
root=UUID=051c84c8-cdd1-4c3e-9f87-3418934f163c ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc N/A
  RfKill:
   
  SourcePackage: linux-meta
  Title: package linux-image-generic 4.4.0.93.98 failed to install/upgrade: 
依存関係の問題 - 設定を見送ります
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/11/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F2
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H81M-S2H
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF2:bd08/11/2015:svnGigabyteTechnologyCo.,Ltd.:pnH81M-S2H:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnH81M-S2H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: H81M-S2H
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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

[Kernel-packages] [Bug 1705748] Re: Samsung SSD 960 EVO 500GB refused to change power state

2017-08-29 Thread Kai-Heng Feng

I built a kernel with the quirk. Please try it without the nvme_core
kernel parameter.

http://people.canonical.com/~khfeng/pm961/

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

Title:
  Samsung SSD 960 EVO 500GB refused to change power state

Status in linux package in Ubuntu:
  In Progress

Bug description:
  Originally thought my issue was same as this:
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678184
  but requested to report as separate bug

  System becomes unusable at seemingly random times but especially after
  resume from suspend due to disk 'disappearing' becoming inaccessible,
  with hundreds of I/O errors logged.

  After viewing the above bug report yesterday as a quick temporary fix I added 
kernel param, updated grub, etc with:
  GRUB_CMDLINE_LINUX_DEFAULT="nvme_core.default_ps_max_latency_us=0"

  System appears to have been stable for the last day, but is presumably
  using more power than it should.

  System, drive details below:

  M2 nvme drive: Samsung SSD 960 EVO 500GB

  Ubuntu 4.10.0-26.30~16.04.1-generic 4.10.17

  M/B Asus Prime B350m-A
  Ryzen 1600 cpu

  Jul 20 16:32:59 phs08 kernel: [ 190.893571] INVALID_DEVICE_REQUEST 
device=00:00.0 address=0xfffdf800 flags=0x0a00]
  Jul 20 16:33:05 phs08 kernel: [ 197.010928] nvme :01:00.0: controller is 
down; will reset: CSTS=0x, PCI_STATUS=0x
  Jul 20 16:33:05 phs08 kernel: [ 197.046980] pci_raw_set_power_state: 4 
callbacks suppressed
  Jul 20 16:33:05 phs08 kernel: [ 197.046985] nvme :01:00.0: Refused to 
change power state, currently in D3
  Jul 20 16:33:05 phs08 kernel: [ 197.047163] nvme nvme0: Removing after probe 
failure status: -19
  Jul 20 16:33:05 phs08 kernel: [ 197.047182] nvme0n1: detected capacity change 
from 500107862016 to 0
  Jul 20 16:33:05 phs08 kernel: [ 197.047793] blk_update_request: I/O error, 
dev nvme0n1, sector 0

  
  nvme list

  /dev/nvme0n1 S3EUNX0J305518L Samsung SSD 960 EVO 500GB 1.2 1 125.20 GB
  / 500.11 GB 512 B + 0 B 2B7QCXE7

  sudo nvme id-ctrl /dev/nvme0

  NVME Identify Controller:
  vid : 0x144d
  ssvid : 0x144d
  sn : S3EUNX0J305518L
  mn : Samsung SSD 960 EVO 500GB
  fr : 2B7QCXE7
  rab : 2
  ieee : 002538
  cmic : 0
  mdts : 9
  cntlid : 2
  ver : 10200
  rtd3r : 7a120
  rtd3e : 4c4b40
  oaes : 0
  oacs : 0x7
  acl : 7
  aerl : 3
  frmw : 0x16
  lpa : 0x3
  elpe : 63
  npss : 4
  avscc : 0x1
  apsta : 0x1
  wctemp : 350
  cctemp : 352
  mtfa : 0
  hmpre : 0
  hmmin : 0
  tnvmcap : 500107862016
  unvmcap : 0
  rpmbs : 0
  sqes : 0x66
  cqes : 0x44
  nn : 1
  oncs : 0x1f
  fuses : 0
  fna : 0x5
  vwc : 0x1
  awun : 255
  awupf : 0
  nvscc : 1
  acwu : 0
  sgls : 0
  ps 0 : mp:6.04W operational enlat:0 exlat:0 rrt:0 rrl:0
rwt:0 rwl:0 idle_power:- active_power:-
  ps 1 : mp:5.09W operational enlat:0 exlat:0 rrt:1 rrl:1
rwt:1 rwl:1 idle_power:- active_power:-
  ps 2 : mp:4.08W operational enlat:0 exlat:0 rrt:2 rrl:2
rwt:2 rwl:2 idle_power:- active_power:-
  ps 3 : mp:0.0400W non-operational enlat:210 exlat:1500 rrt:3 rrl:3
rwt:3 rwl:3 idle_power:- active_power:-
  ps 4 : mp:0.0050W non-operational enlat:2200 exlat:6000 rrt:4 rrl:4
rwt:4 rwl:4 idle_power:- active_power:-
  --- 
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  drgrumpy   2192 F pulseaudio
   /dev/snd/pcmC1D0p:   drgrumpy   2192 F...m pulseaudio
   /dev/snd/controlC1:  drgrumpy   2192 F pulseaudio
  DistroRelease: Linux 18.2
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=a6896cdd-6bac-4e7f-9e13-55460859c3ec
  InstallationDate: Installed on 2017-07-06 (15 days ago)
  InstallationMedia: Linux Mint 18.2 "Sonya" - Release amd64 20170628
  IwConfig:
   lono wireless extensions.
   
   enp37s0   no wireless extensions.
  MachineType: System manufacturer System Product Name
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=en_GB:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-26-generic 
root=UUID=f7ae652b-cbf6-48b8-bc6a-d3963957ab57 ro 
nvme_core.default_ps_max_latency_us=0
  ProcVersionSignature: Ubuntu 4.10.0-26.30~16.04.1-generic 4.10.17
  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.10.0-26-generic N/A
   linux-backports-modules-4.10.0-26-generic  N/A
   linux-firmware 1.157.11
  RfKill:
   
  Tags:  sonya
  Uname: Linux 4.10.0-26-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 06/20/2

[Kernel-packages] [Bug 1705378] Re: ideapad_laptop don't support v310-14isk

2017-08-29 Thread Anthony Wong

** Changed in: hwe-next
   Status: Fix Committed => Fix Released

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

Title:
  ideapad_laptop don't support v310-14isk

Status in HWE Next:
  Fix Released
Status in Linux:
  Incomplete
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Fix Released
Status in linux source package in Zesty:
  Fix Released

Bug description:
  we found the wireless and bluetooth can't work, the device had driver
  already, just wereo blocked by ideapad_laptop module. After remove it,
  it works fine.

  $ sudo rfkill list
  0: ideapad_wlan: Wireless LAN
  Soft blocked: no
  Hard blocked: yes
  1: ideapad_bluetooth: Bluetooth
  Soft blocked: no
  Hard blocked: yes
  2: hci0: Bluetooth
  Soft blocked: no
  Hard blocked: no
  3: phy0: Wireless LAN
  Soft blocked: no
  Hard blocked: no

  SRU Justification
  =

  [Impact]
  wireless and bluetooth were blocked by ideapad_laptop module.

  [Fix]
  Fix it by adding those models to no_hw_rfkill_list.

  [Test Case]
  Wireless and BT works fine.

  [Regression Potential]
  This patch add several dmi entry in struct.
  Regression Potential is low.

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

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

Re: [Kernel-packages] [Bug 1567597] Re: implement 'complain mode' in seccomp for developer mode with snaps

2017-08-29 Thread Zygmunt Krynicki

Hey Tyler, thank you for the update, this looks very promising indeed.

I'd like to ask about two aspects:

- detection, how can we detect that this feature is available? Shall
we just compile a program and see if it loads on snapd startup?
- golang, we use golang bindings to libseccomp and we will need to
adjust them to expose the new APIs (presumably). Is this something you
plan to handle as well?

Thanks
ZK

On Mon, Aug 28, 2017 at 3:15 PM, Tyler Hicks  wrote:
> The kernel patches were committed to the Ubuntu Artful kernel git repo:
> https://lists.ubuntu.com/archives/kernel-team/2017-August/086714.html
>
> ** Changed in: linux (Ubuntu)
>Status: In Progress => Fix Committed
>
> --
> You received this bug notification because you are a member of Snappy
> Developers, which is subscribed to Snappy.
> Matching subscriptions: xxx-bugs-on-snapd
> https://bugs.launchpad.net/bugs/1567597
>
> Title:
>   implement 'complain mode' in seccomp for developer mode with snaps
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/snappy/+bug/1567597/+subscriptions

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

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

Status in Snappy:
  In Progress
Status in libseccomp package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Fix Committed

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

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

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

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

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

[Kernel-packages] [Bug 1713653] [NEW] Test 069 from ubuntu_zfs_xfs_generic causes kernel panic on Artful zKVM

2017-08-29 Thread Po-Hsu Lin

Public bug reported:

This issue can be easily reproduced on our zKVM node (s2lp6g004)

09:09:49 INFO | Running: 
/home/ubuntu/autotest/client/tests/ubuntu_zfs_xfs_generic/ubuntu_zfs_xfs_generic.sh
 069 /home/ubuntu/autotest/client/tmp/ubuntu_zfs_xfs_generic/src
09:09:49 DEBUG| Running 
'/home/ubuntu/autotest/client/tests/ubuntu_zfs_xfs_generic/ubuntu_zfs_xfs_generic.sh
 069 /home/ubuntu/autotest/client/tmp/ubuntu_zfs_xfs_generic/src'
09:09:49 DEBUG| [stdout] Creating zfs pool testpool..
09:09:49 DEBUG| [stdout] Creating zfs file systems test and scratch in 
testpool..
09:09:49 DEBUG| [stdout] VDEVs in 
/home/ubuntu/autotest/client/tmp/ubuntu_zfs_xfs_generic/src
09:09:49 DEBUG| [stdout] FSTYP -- zfs
09:09:49 DEBUG| [stdout] PLATFORM  -- Linux/s390x s2lp6g004 
4.12.0-12-generic
09:09:49 DEBUG| [stdout] MKFS_OPTIONS  -- testpool/scratch
09:09:49 DEBUG| [stdout] MOUNT_OPTIONS -- testpool/scratch /mnt/scratch
09:09:49 DEBUG| [stdout] 
Connection to s2lp6g004 closed by remote host.

ubuntu@s2lp6g004:~$ [ 1471.034292] Out of memory: Kill process 4199 (python) 
score 24 or sacrifice child
[ 1471.034298] Killed process 4493 (sh) total-vm:2268kB, anon-rss:0kB, 
file-rss:504kB, shmem-rss:0kB
[ 1471.067172] Out of memory: Kill process 4199 (python) score 24 or sacrifice 
child
[ 1471.067176] Killed process 4199 (python) total-vm:122940kB, anon-rss:0kB, 
file-rss:1420kB, shmem-rss:0kB
[ 1471.069927] Out of memory: Kill process 4496 (autotest-local) score 8 or 
sacrifice child
[ 1471.069931] Killed process 14411 (autotest-local) total-vm:21872kB, 
anon-rss:192kB, file-rss:1008kB, shmem-rss:0kB
[ 1471.082995] Out of memory: Kill process 4496 (autotest-local) score 8 or 
sacrifice child
[ 1471.082997] Killed process 4497 (autotest-local) total-vm:21872kB, 
anon-rss:0kB, file-rss:360kB, shmem-rss:0kB
[ 1471.104838] Out of memory: Kill process 4496 (autotest-local) score 8 or 
sacrifice child
[ 1471.104842] Killed process 4498 (autotest-local) total-vm:21872kB, 
anon-rss:0kB, file-rss:360kB, shmem-rss:0kB
[ 1471.132957] Out of memory: Kill process 4496 (autotest-local) score 8 or 
sacrifice child
[ 1471.132960] Killed process 4496 (autotest-local) total-vm:21872kB, 
anon-rss:0kB, file-rss:3144kB, shmem-rss:0kB
[ 1471.154586] Out of memory: Kill process 14413 (autotest-local) score 7 or 
sacrifice child
[ 1471.154588] Killed process 14413 (autotest-local) total-vm:21872kB, 
anon-rss:0kB, file-rss:360kB, shmem-rss:0kB
[ 1471.174634] Out of memory: Kill process 14414 (autotest-local) score 7 or 
sacrifice child
[ 1471.174637] Killed process 14414 (autotest-local) total-vm:21872kB, 
anon-rss:0kB, file-rss:360kB, shmem-rss:0kB
[ 1471.177964] Out of memory: Kill process 2482 (ovs-vswitchd) score 3 or 
sacrifice child
[ 1471.177966] Killed process 2482 (ovs-vswitchd) total-vm:7448kB, 
anon-rss:856kB, file-rss:6412kB, shmem-rss:0kB
[ 1471.208758] Out of memory: Kill process 4148 (sshd) score 2 or sacrifice 
child
[ 1471.208760] Killed process 4198 (sshd) total-vm:10648kB, anon-rss:0kB, 
file-rss:2032kB, shmem-rss:0kB
[ 1471.303038] Out of memory: Kill process 14807 (check) score 2 or sacrifice 
child
[ 1471.303041] Killed process 15112 (069) total-vm:5832kB, anon-rss:0kB, 
file-rss:1316kB, shmem-rss:0kB
[ 1471.332361] Out of memory: Kill process 14807 (check) score 2 or sacrifice 
child
[ 1471.332364] Killed process 14807 (check) total-vm:5820kB, anon-rss:0kB, 
file-rss:1192kB, shmem-rss:0kB
[ 1471.352704] Out of memory: Kill process 3407 (bash) score 1 or sacrifice 
child
[ 1471.352706] Killed process 3407 (bash) total-vm:5404kB, anon-rss:0kB, 
file-rss:1444kB, shmem-rss:0kB
[ 1471.407768] Out of memory: Kill process 3386 (systemd) score 1 or sacrifice 
child
[ 1471.407772] Killed process 3387 ((sd-pam)) total-vm:13084kB, anon-rss:0kB, 
file-rss:0kB, shmem-rss:0kB
[ 1471.427874] Out of memory: Kill process 3386 (systemd) score 1 or sacrifice 
child
[ 1471.427877] Killed process 3386 (systemd) total-vm:11252kB, anon-rss:0kB, 
file-rss:2204kB, shmem-rss:0kB
[ 1471.448535] Out of memory: Kill process 2390 (polkitd) score 1 or sacrifice 
child
[ 1471.448541] Killed process 2390 (polkitd) total-vm:231004kB, anon-rss:0kB, 
file-rss:1856kB, shmem-rss:0kB
[ 1471.464663] Out of memory: Kill process 2343 (accounts-daemon) score 1 or 
sacrifice child
[ 1471.464667] Killed process 2343 (accounts-daemon) total-vm:230840kB, 
anon-rss:0kB, file-rss:1796kB, shmem-rss:0kB
[ 1471.493818] Out of memory: Kill process 4148 (sshd) score 1 or sacrifice 
child
[ 1471.493820] Killed process 4148 (sshd) total-vm:10648kB, anon-rss:0kB, 
file-rss:1572kB, shmem-rss:0kB
[ 1471.512756] Out of memory: Kill process 2345 (rsyslogd) score 1 or sacrifice 
child
[ 1471.512763] Killed process 2345 (rsyslogd) total-vm:225636kB, anon-rss:0kB, 
file-rss:1632kB, shmem-rss:0kB
[ 1471.641242] Out of memory: Kill process 2646 (systemd-resolve) score 1 or 
sacrifice child
[ 1471.641249] Killed process 2646 (systemd-resolve) total-vm:9072kB, 
anon-rss:0kB, file-rs

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

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

apport-collect 1713653

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

Title:
  Test 069 from ubuntu_zfs_xfs_generic causes kernel panic on Artful
  zKVM

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  This issue can be easily reproduced on our zKVM node (s2lp6g004) by
  running the ubuntu_zfs_xfs_generic test suite.

  The "virsh list" command will show that it's "crashed" after this
  happens.

  09:09:49 INFO | Running: 
/home/ubuntu/autotest/client/tests/ubuntu_zfs_xfs_generic/ubuntu_zfs_xfs_generic.sh
 069 /home/ubuntu/autotest/client/tmp/ubuntu_zfs_xfs_generic/src
  09:09:49 DEBUG| Running 
'/home/ubuntu/autotest/client/tests/ubuntu_zfs_xfs_generic/ubuntu_zfs_xfs_generic.sh
 069 /home/ubuntu/autotest/client/tmp/ubuntu_zfs_xfs_generic/src'
  09:09:49 DEBUG| [stdout] Creating zfs pool testpool..
  09:09:49 DEBUG| [stdout] Creating zfs file systems test and scratch in 
testpool..
  09:09:49 DEBUG| [stdout] VDEVs in 
/home/ubuntu/autotest/client/tmp/ubuntu_zfs_xfs_generic/src
  09:09:49 DEBUG| [stdout] FSTYP -- zfs
  09:09:49 DEBUG| [stdout] PLATFORM  -- Linux/s390x s2lp6g004 
4.12.0-12-generic
  09:09:49 DEBUG| [stdout] MKFS_OPTIONS  -- testpool/scratch
  09:09:49 DEBUG| [stdout] MOUNT_OPTIONS -- testpool/scratch /mnt/scratch
  09:09:49 DEBUG| [stdout]
  Connection to s2lp6g004 closed by remote host.

  ubuntu@s2lp6g004:~$ [ 1471.034292] Out of memory: Kill process 4199 (python) 
score 24 or sacrifice child
  [ 1471.034298] Killed process 4493 (sh) total-vm:2268kB, anon-rss:0kB, 
file-rss:504kB, shmem-rss:0kB
  [ 1471.067172] Out of memory: Kill process 4199 (python) score 24 or 
sacrifice child
  [ 1471.067176] Killed process 4199 (python) total-vm:122940kB, anon-rss:0kB, 
file-rss:1420kB, shmem-rss:0kB
  [ 1471.069927] Out of memory: Kill process 4496 (autotest-local) score 8 or 
sacrifice child
  [ 1471.069931] Killed process 14411 (autotest-local) total-vm:21872kB, 
anon-rss:192kB, file-rss:1008kB, shmem-rss:0kB
  [ 1471.082995] Out of memory: Kill process 4496 (autotest-local) score 8 or 
sacrifice child
  [ 1471.082997] Killed process 4497 (autotest-local) total-vm:21872kB, 
anon-rss:0kB, file-rss:360kB, shmem-rss:0kB
  [ 1471.104838] Out of memory: Kill process 4496 (autotest-local) score 8 or 
sacrifice child
  [ 1471.104842] Killed process 4498 (autotest-local) total-vm:21872kB, 
anon-rss:0kB, file-rss:360kB, shmem-rss:0kB
  [ 1471.132957] Out of memory: Kill process 4496 (autotest-local) score 8 or 
sacrifice child
  [ 1471.132960] Killed process 4496 (autotest-local) total-vm:21872kB, 
anon-rss:0kB, file-rss:3144kB, shmem-rss:0kB
  [ 1471.154586] Out of memory: Kill process 14413 (autotest-local) score 7 or 
sacrifice child
  [ 1471.154588] Killed process 14413 (autotest-local) total-vm:21872kB, 
anon-rss:0kB, file-rss:360kB, shmem-rss:0kB
  [ 1471.174634] Out of memory: Kill process 14414 (autotest-local) score 7 or 
sacrifice child
  [ 1471.174637] Killed process 14414 (autotest-local) total-vm:21872kB, 
anon-rss:0kB, file-rss:360kB, shmem-rss:0kB
  [ 1471.177964] Out of memory: Kill process 2482 (ovs-vswitchd) score 3 or 
sacrifice child
  [ 1471.177966] Killed process 2482 (ovs-vswitchd) total-vm:7448kB, 
anon-rss:856kB, file-rss:6412kB, shmem-rss:0kB
  [ 1471.208758] Out of memory: Kill process 4148 (sshd) score 2 or sacrifice 
child
  [ 1471.208760] Killed process 4198 (sshd) total-vm:10648kB, anon-rss:0kB, 
file-rss:2032kB, shmem-rss:0kB
  [ 1471.303038] Out of memory: Kill process 14807 (check) score 2 or sacrifice 
child
  [ 1471.303041] Killed process 15112 (069) total-vm:5832kB, anon-rss:0kB, 
file-rss:1316kB, shmem-rss:0kB
  [ 1471.332361] Out of memory: Kill process 14807 (check) score 2 or sacrifice 
child
  [ 1471.332364] Killed process 14807 (check) total-vm:5820kB, anon-rss:0kB, 
file-rss:1192kB, shmem-rss:0kB
  [ 1471.352704] Out of memory: Kill process 3407 (bash) score 1 or sacrifice 
child
  [ 1471.352706] Killed process 3407 (bash) total-vm:5404kB, anon-rss:0kB, 
file-rss:1444kB, shmem-rss:0kB
  [ 1471.407768] Out of memory: Kill process 3386 (systemd) score 1 or 
sacrifice child
  [ 1471.407772] Killed process 3387 ((sd-pam)) total-vm:13084kB, anon-rss:0kB, 
file-rss:0kB, shmem-rss:0kB
  [ 1471.427874] Out of memory: Kill process 3386 (systemd) score

[Kernel-packages] [Bug 1713653] Re: Test 069 from ubuntu_zfs_xfs_generic causes kernel panic on Artful zKVM

2017-08-29 Thread Po-Hsu Lin

** Description changed:

- This issue can be easily reproduced on our zKVM node (s2lp6g004)
+ This issue can be easily reproduced on our zKVM node (s2lp6g004) by
+ running the ubuntu_zfs_xfs_generic test suite.
+ 
+ The virsh list will show that it's "crashed" after this happens.
  
  09:09:49 INFO | Running: 
/home/ubuntu/autotest/client/tests/ubuntu_zfs_xfs_generic/ubuntu_zfs_xfs_generic.sh
 069 /home/ubuntu/autotest/client/tmp/ubuntu_zfs_xfs_generic/src
  09:09:49 DEBUG| Running 
'/home/ubuntu/autotest/client/tests/ubuntu_zfs_xfs_generic/ubuntu_zfs_xfs_generic.sh
 069 /home/ubuntu/autotest/client/tmp/ubuntu_zfs_xfs_generic/src'
  09:09:49 DEBUG| [stdout] Creating zfs pool testpool..
  09:09:49 DEBUG| [stdout] Creating zfs file systems test and scratch in 
testpool..
  09:09:49 DEBUG| [stdout] VDEVs in 
/home/ubuntu/autotest/client/tmp/ubuntu_zfs_xfs_generic/src
  09:09:49 DEBUG| [stdout] FSTYP -- zfs
  09:09:49 DEBUG| [stdout] PLATFORM  -- Linux/s390x s2lp6g004 
4.12.0-12-generic
  09:09:49 DEBUG| [stdout] MKFS_OPTIONS  -- testpool/scratch
  09:09:49 DEBUG| [stdout] MOUNT_OPTIONS -- testpool/scratch /mnt/scratch
- 09:09:49 DEBUG| [stdout] 
+ 09:09:49 DEBUG| [stdout]
  Connection to s2lp6g004 closed by remote host.
  
  ubuntu@s2lp6g004:~$ [ 1471.034292] Out of memory: Kill process 4199 (python) 
score 24 or sacrifice child
  [ 1471.034298] Killed process 4493 (sh) total-vm:2268kB, anon-rss:0kB, 
file-rss:504kB, shmem-rss:0kB
  [ 1471.067172] Out of memory: Kill process 4199 (python) score 24 or 
sacrifice child
  [ 1471.067176] Killed process 4199 (python) total-vm:122940kB, anon-rss:0kB, 
file-rss:1420kB, shmem-rss:0kB
  [ 1471.069927] Out of memory: Kill process 4496 (autotest-local) score 8 or 
sacrifice child
  [ 1471.069931] Killed process 14411 (autotest-local) total-vm:21872kB, 
anon-rss:192kB, file-rss:1008kB, shmem-rss:0kB
  [ 1471.082995] Out of memory: Kill process 4496 (autotest-local) score 8 or 
sacrifice child
  [ 1471.082997] Killed process 4497 (autotest-local) total-vm:21872kB, 
anon-rss:0kB, file-rss:360kB, shmem-rss:0kB
  [ 1471.104838] Out of memory: Kill process 4496 (autotest-local) score 8 or 
sacrifice child
  [ 1471.104842] Killed process 4498 (autotest-local) total-vm:21872kB, 
anon-rss:0kB, file-rss:360kB, shmem-rss:0kB
  [ 1471.132957] Out of memory: Kill process 4496 (autotest-local) score 8 or 
sacrifice child
  [ 1471.132960] Killed process 4496 (autotest-local) total-vm:21872kB, 
anon-rss:0kB, file-rss:3144kB, shmem-rss:0kB
  [ 1471.154586] Out of memory: Kill process 14413 (autotest-local) score 7 or 
sacrifice child
  [ 1471.154588] Killed process 14413 (autotest-local) total-vm:21872kB, 
anon-rss:0kB, file-rss:360kB, shmem-rss:0kB
  [ 1471.174634] Out of memory: Kill process 14414 (autotest-local) score 7 or 
sacrifice child
  [ 1471.174637] Killed process 14414 (autotest-local) total-vm:21872kB, 
anon-rss:0kB, file-rss:360kB, shmem-rss:0kB
  [ 1471.177964] Out of memory: Kill process 2482 (ovs-vswitchd) score 3 or 
sacrifice child
  [ 1471.177966] Killed process 2482 (ovs-vswitchd) total-vm:7448kB, 
anon-rss:856kB, file-rss:6412kB, shmem-rss:0kB
  [ 1471.208758] Out of memory: Kill process 4148 (sshd) score 2 or sacrifice 
child
  [ 1471.208760] Killed process 4198 (sshd) total-vm:10648kB, anon-rss:0kB, 
file-rss:2032kB, shmem-rss:0kB
  [ 1471.303038] Out of memory: Kill process 14807 (check) score 2 or sacrifice 
child
  [ 1471.303041] Killed process 15112 (069) total-vm:5832kB, anon-rss:0kB, 
file-rss:1316kB, shmem-rss:0kB
  [ 1471.332361] Out of memory: Kill process 14807 (check) score 2 or sacrifice 
child
  [ 1471.332364] Killed process 14807 (check) total-vm:5820kB, anon-rss:0kB, 
file-rss:1192kB, shmem-rss:0kB
  [ 1471.352704] Out of memory: Kill process 3407 (bash) score 1 or sacrifice 
child
  [ 1471.352706] Killed process 3407 (bash) total-vm:5404kB, anon-rss:0kB, 
file-rss:1444kB, shmem-rss:0kB
  [ 1471.407768] Out of memory: Kill process 3386 (systemd) score 1 or 
sacrifice child
  [ 1471.407772] Killed process 3387 ((sd-pam)) total-vm:13084kB, anon-rss:0kB, 
file-rss:0kB, shmem-rss:0kB
  [ 1471.427874] Out of memory: Kill process 3386 (systemd) score 1 or 
sacrifice child
  [ 1471.427877] Killed process 3386 (systemd) total-vm:11252kB, anon-rss:0kB, 
file-rss:2204kB, shmem-rss:0kB
  [ 1471.448535] Out of memory: Kill process 2390 (polkitd) score 1 or 
sacrifice child
  [ 1471.448541] Killed process 2390 (polkitd) total-vm:231004kB, anon-rss:0kB, 
file-rss:1856kB, shmem-rss:0kB
  [ 1471.464663] Out of memory: Kill process 2343 (accounts-daemon) score 1 or 
sacrifice child
  [ 1471.464667] Killed process 2343 (accounts-daemon) total-vm:230840kB, 
anon-rss:0kB, file-rss:1796kB, shmem-rss:0kB
  [ 1471.493818] Out of memory: Kill process 4148 (sshd) score 1 or sacrifice 
child
  [ 1471.493820] Killed process 4148 (sshd) total-vm:10648kB, anon-rss:0kB, 
file-rss:1572kB, shmem-rss:0kB
  [ 1471.512756] Out of memory: Kill process 2345 (rsyslogd) scor

[Kernel-packages] [Bug 1454450] Re: Bluetooth mouse laggy and erratic

2017-08-29 Thread Vasilis

Update. I replaced my USB bluetooth dongle Bluetooth V4.0 to a very old
one V2.0 and since a week now I have no problems with any keyboard or
with the mouse.

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

Title:
  Bluetooth mouse laggy and erratic

Status in bluez package in Ubuntu:
  Confirmed
Status in linux-firmware package in Ubuntu:
  Confirmed

Bug description:
  I installed Ubuntu 15.04 (64 bit) on a DELL XPS 13 (model 9343, bios
  A03) notebook. I use a DELL bluetooth mouse but sometimes it behaves
  erratically (laggy, jumpy). The problem happens after a few (sometimes
  one) suspend and resume. I am attaching below some info on my system.
  Thank you.

  cribari@darwin4:~$ uname -a; lspci -nnk | grep -iA2 net; lsusb; dmesg | grep 
-i bluetooth; dmesg | grep -i firmware; lsmod | grep bluetooth
  Linux darwin4 3.19.0-17-generic #17-Ubuntu SMP Wed May 6 16:46:12 UTC 2015 
x86_64 x86_64 x86_64 GNU/Linux
  02:00.0 Network controller [0280]: Broadcom Corporation BCM4352 802.11ac 
Wireless Network Adapter [14e4:43b1] (rev 03)
   Subsystem: Dell Device [1028:0019]
   Kernel driver in use: wl
  Bus 003 Device 002: ID 8087:8001 Intel Corp.
  Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 001 Device 004: ID 0c45:670c Microdia
  Bus 001 Device 003: ID 04f3:20d0 Elan Microelectronics Corp.
  Bus 001 Device 002: ID 0a5c:216f Broadcom Corp.
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  [2.174367] Bluetooth: Core ver 2.20
  [2.174669] Bluetooth: HCI device and connection manager initialized
  [2.174792] Bluetooth: HCI socket layer initialized
  [2.174795] Bluetooth: L2CAP socket layer initialized
  [2.175449] Bluetooth: SCO socket layer initialized
  [2.592936] Bluetooth: hci0: BCM: patching hci_ver=06 hci_rev=1624 
lmp_ver=06 lmp_subver=220e
  [3.203438] Bluetooth: hci0: BCM: firmware hci_ver=06 hci_rev=1624 
lmp_ver=06 lmp_subver=220e
  [3.542418] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
  [3.542421] Bluetooth: BNEP filters: protocol multicast
  [3.542425] Bluetooth: BNEP socket layer initialized
  [3.551641] Bluetooth: RFCOMM TTY layer initialized
  [3.551649] Bluetooth: RFCOMM socket layer initialized
  [3.551654] Bluetooth: RFCOMM ver 1.11
  [   26.569283] Bluetooth: HIDP (Human Interface Emulation) ver 1.2
  [   26.569287] Bluetooth: HIDP socket layer initialized
  [   26.576971] input: Dell Travel Mouse WM524 as 
/devices/pci:00/:00:14.0/usb1/1-3/1-3:1.0/bluetooth/hci0/hci0:11/0005:046D:B00E.0003/input/input15
  [   26.577172] hid-generic 0005:046D:B00E.0003: input,hidraw2: BLUETOOTH HID 
v8.00 Mouse [Dell Travel Mouse WM524] on ac:d1:b8:c0:6f:5c
  [   72.448281] input: Dell Travel Mouse WM524 as 
/devices/pci:00/:00:14.0/usb1/1-3/1-3:1.0/bluetooth/hci0/hci0:12/0005:046D:B00E.0004/input/input16
  [   72.448526] hid-generic 0005:046D:B00E.0004: input,hidraw2: BLUETOOTH HID 
v8.00 Mouse [Dell Travel Mouse WM524] on ac:d1:b8:c0:6f:5c
  [ 2994.842547] input: Dell Travel Mouse WM524 as 
/devices/pci:00/:00:14.0/usb1/1-3/1-3:1.0/bluetooth/hci0/hci0:13/0005:046D:B00E.0005/input/input17
  [ 2994.842810] hid-generic 0005:046D:B00E.0005: input,hidraw2: BLUETOOTH HID 
v8.00 Mouse [Dell Travel Mouse WM524] on ac:d1:b8:c0:6f:5c
  [ 3694.214037] Bluetooth: hci0: BCM: patching hci_ver=06 hci_rev=1000 
lmp_ver=06 lmp_subver=220e
  [ 3694.861578] Bluetooth: hci0: BCM: firmware hci_ver=06 hci_rev=1624 
lmp_ver=06 lmp_subver=220e
  [ 3811.777260] input: Dell Travel Mouse WM524 as 
/devices/pci:00/:00:14.0/usb1/1-3/1-3:1.0/bluetooth/hci0/hci0:11/0005:046D:B00E.0006/input/input20
  [ 3811.777571] hid-generic 0005:046D:B00E.0006: input,hidraw2: BLUETOOTH HID 
v8.00 Mouse [Dell Travel Mouse WM524] on ac:d1:b8:c0:6f:5c
  [ 5579.876192] Modules linked in: huawei_cdc_ncm cdc_wdm cdc_ncm option 
usb_wwan usbserial usbnet mii uas usb_storage hid_generic hidp nvram msr 
binfmt_misc rfcomm bnep nls_iso8859_1 intel_rapl iosf_mbi x86_pkg_temp_thermal 
dell_wmi sparse_keymap intel_powerclamp coretemp kvm_intel kvm crct10dif_pclmul 
dell_laptop dcdbas btusb crc32_pclmul bluetooth ghash_clmulni_intel 
hid_multitouch aesni_intel aes_x86_64 lrw uvcvideo gf128mul videobuf2_vmalloc 
glue_helper wl(POE) videobuf2_memops ablk_helper videobuf2_core cryptd 
v4l2_common videodev media joydev i915_bpo serio_raw i915 dell_led rtsx_pci_ms 
intel_ips memstick snd_hda_codec_realtek snd_soc_rt286 snd_hda_codec_generic 
cfg80211 snd_soc_core drm_kms_helper mei_me lpc_ich shpchp mei snd_compress 
snd_hda_intel snd_hda_controller drm snd_hda_codec i2c_algo_bit
  [ 5579.876223] Workqueue: hci0 hci_power_on [bluetooth]
  [ 5579.876261]  [] hci_dev_do_open+0xe1/0xa90 [bluetooth]
  [ 5579.876266]  [] hci_power_on+0x40/0x200 [bluetooth]
  [ 557

[Kernel-packages] [Bug 1713653] Re: Test 069 from ubuntu_zfs_xfs_generic causes kernel panic on Artful zKVM

2017-08-29 Thread Po-Hsu Lin

This issue does not exist after expanding the memory from 1G to 2G.
Thus I'm closing this.

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

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

Title:
  Test 069 from ubuntu_zfs_xfs_generic causes kernel panic on Artful
  zKVM

Status in linux package in Ubuntu:
  Invalid

Bug description:
  This issue can be easily reproduced on our zKVM node (s2lp6g004) by
  running the ubuntu_zfs_xfs_generic test suite.

  The "virsh list" command will show that it's "crashed" after this
  happens.

  09:09:49 INFO | Running: 
/home/ubuntu/autotest/client/tests/ubuntu_zfs_xfs_generic/ubuntu_zfs_xfs_generic.sh
 069 /home/ubuntu/autotest/client/tmp/ubuntu_zfs_xfs_generic/src
  09:09:49 DEBUG| Running 
'/home/ubuntu/autotest/client/tests/ubuntu_zfs_xfs_generic/ubuntu_zfs_xfs_generic.sh
 069 /home/ubuntu/autotest/client/tmp/ubuntu_zfs_xfs_generic/src'
  09:09:49 DEBUG| [stdout] Creating zfs pool testpool..
  09:09:49 DEBUG| [stdout] Creating zfs file systems test and scratch in 
testpool..
  09:09:49 DEBUG| [stdout] VDEVs in 
/home/ubuntu/autotest/client/tmp/ubuntu_zfs_xfs_generic/src
  09:09:49 DEBUG| [stdout] FSTYP -- zfs
  09:09:49 DEBUG| [stdout] PLATFORM  -- Linux/s390x s2lp6g004 
4.12.0-12-generic
  09:09:49 DEBUG| [stdout] MKFS_OPTIONS  -- testpool/scratch
  09:09:49 DEBUG| [stdout] MOUNT_OPTIONS -- testpool/scratch /mnt/scratch
  09:09:49 DEBUG| [stdout]
  Connection to s2lp6g004 closed by remote host.

  ubuntu@s2lp6g004:~$ [ 1471.034292] Out of memory: Kill process 4199 (python) 
score 24 or sacrifice child
  [ 1471.034298] Killed process 4493 (sh) total-vm:2268kB, anon-rss:0kB, 
file-rss:504kB, shmem-rss:0kB
  [ 1471.067172] Out of memory: Kill process 4199 (python) score 24 or 
sacrifice child
  [ 1471.067176] Killed process 4199 (python) total-vm:122940kB, anon-rss:0kB, 
file-rss:1420kB, shmem-rss:0kB
  [ 1471.069927] Out of memory: Kill process 4496 (autotest-local) score 8 or 
sacrifice child
  [ 1471.069931] Killed process 14411 (autotest-local) total-vm:21872kB, 
anon-rss:192kB, file-rss:1008kB, shmem-rss:0kB
  [ 1471.082995] Out of memory: Kill process 4496 (autotest-local) score 8 or 
sacrifice child
  [ 1471.082997] Killed process 4497 (autotest-local) total-vm:21872kB, 
anon-rss:0kB, file-rss:360kB, shmem-rss:0kB
  [ 1471.104838] Out of memory: Kill process 4496 (autotest-local) score 8 or 
sacrifice child
  [ 1471.104842] Killed process 4498 (autotest-local) total-vm:21872kB, 
anon-rss:0kB, file-rss:360kB, shmem-rss:0kB
  [ 1471.132957] Out of memory: Kill process 4496 (autotest-local) score 8 or 
sacrifice child
  [ 1471.132960] Killed process 4496 (autotest-local) total-vm:21872kB, 
anon-rss:0kB, file-rss:3144kB, shmem-rss:0kB
  [ 1471.154586] Out of memory: Kill process 14413 (autotest-local) score 7 or 
sacrifice child
  [ 1471.154588] Killed process 14413 (autotest-local) total-vm:21872kB, 
anon-rss:0kB, file-rss:360kB, shmem-rss:0kB
  [ 1471.174634] Out of memory: Kill process 14414 (autotest-local) score 7 or 
sacrifice child
  [ 1471.174637] Killed process 14414 (autotest-local) total-vm:21872kB, 
anon-rss:0kB, file-rss:360kB, shmem-rss:0kB
  [ 1471.177964] Out of memory: Kill process 2482 (ovs-vswitchd) score 3 or 
sacrifice child
  [ 1471.177966] Killed process 2482 (ovs-vswitchd) total-vm:7448kB, 
anon-rss:856kB, file-rss:6412kB, shmem-rss:0kB
  [ 1471.208758] Out of memory: Kill process 4148 (sshd) score 2 or sacrifice 
child
  [ 1471.208760] Killed process 4198 (sshd) total-vm:10648kB, anon-rss:0kB, 
file-rss:2032kB, shmem-rss:0kB
  [ 1471.303038] Out of memory: Kill process 14807 (check) score 2 or sacrifice 
child
  [ 1471.303041] Killed process 15112 (069) total-vm:5832kB, anon-rss:0kB, 
file-rss:1316kB, shmem-rss:0kB
  [ 1471.332361] Out of memory: Kill process 14807 (check) score 2 or sacrifice 
child
  [ 1471.332364] Killed process 14807 (check) total-vm:5820kB, anon-rss:0kB, 
file-rss:1192kB, shmem-rss:0kB
  [ 1471.352704] Out of memory: Kill process 3407 (bash) score 1 or sacrifice 
child
  [ 1471.352706] Killed process 3407 (bash) total-vm:5404kB, anon-rss:0kB, 
file-rss:1444kB, shmem-rss:0kB
  [ 1471.407768] Out of memory: Kill process 3386 (systemd) score 1 or 
sacrifice child
  [ 1471.407772] Killed process 3387 ((sd-pam)) total-vm:13084kB, anon-rss:0kB, 
file-rss:0kB, shmem-rss:0kB
  [ 1471.427874] Out of memory: Kill process 3386 (systemd) score 1 or 
sacrifice child
  [ 1471.427877] Killed process 3386 (systemd) total-vm:11252kB, anon-rss:0kB, 
file-rss:2204kB, shmem-rss:0kB
  [ 1471.448535] Out of memory: Kill process 2390 (polkitd) score 1 or 
sacrifice child
  [ 1471.448541] Killed process 2390 (polkitd) total-vm:231004kB, anon-rss:0kB, 
file-rss:1856kB, shmem-rss:0kB
  [ 1471.464663] Out of memory: Kill process 2343 (accounts-daemon) score 1 or 
sacrifice child
  [ 1471.464667] Kil

[Kernel-packages] [Bug 1709032] Re: Creating conntrack entry failure with kernel 4.4.0-89

2017-08-29 Thread Jakub Libosvar

We enabled back our failing CI tests after switching to kernel
4.4.0-92.115 and everything went back to normal. Current 4.4.0-93.116
works just fine too. Thanks a lot for a quick help! I think you can
close this bug as resolved :)

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

Title:
  Creating conntrack entry failure with kernel 4.4.0-89

Status in Linux:
  Confirmed
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Xenial:
  Fix Released

Bug description:
  The functional job failure rate is at 100%. Every time some test gets
  stuck and job is killed after timeout.

  logstash query:
  
http://logstash.openstack.org/#dashboard/file/logstash.json?query=build_name%3A%5C
  %22gate-neutron-dsvm-functional-ubuntu-
  
xenial%5C%22%20AND%20tags%3Aconsole%20AND%20message%3A%5C%22Killed%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20timeout%20-s%209%5C%22

  2017-08-05 12:36:50.127672 | /home/jenkins/workspace/gate-neutron-
  dsvm-functional-ubuntu-xenial/devstack-gate/functions.sh: line 1129:
  15261 Killed  timeout -s 9 ${REMAINING_TIME}m bash -c
  "source $WORKSPACE/devstack-gate/functions.sh && $cmd"

  There are a few test executors left, which means there are more tests
  stuck:

  stack15468 15445 15468  0.0  0.0   328   796 /bin/sh -c 
OS_STDOUT_CAPTURE=${OS_STDOUT_CAPTURE:-1} \ 
OS_STDERR_CAPTURE=${OS_STDERR_CAPTURE:-1} \ OS_LOG_CAPTURE=${OS_LOG_CAPTURE:-1} 
\ OS_TEST_TIMEOUT=${OS_TEST_TIMEOUT:-160} \ ${PYTHON:-python} -m subunit.run 
discover -t ./ ${OS_TEST_PATH:-./neutron/tests/unit}  --load-list /tmp/tmpDTLPoX
  stack15469 15468 15469  1.5  1.8 139332 150008 python -m subunit.run 
discover -t ./ ./neutron/tests/functional --load-list /tmp/tmpDTLPoX
  stack15470 15445 15470  0.0  0.0   328   700 /bin/sh -c 
OS_STDOUT_CAPTURE=${OS_STDOUT_CAPTURE:-1} \ 
OS_STDERR_CAPTURE=${OS_STDERR_CAPTURE:-1} \ OS_LOG_CAPTURE=${OS_LOG_CAPTURE:-1} 
\ OS_TEST_TIMEOUT=${OS_TEST_TIMEOUT:-160} \ ${PYTHON:-python} -m subunit.run 
discover -t ./ ${OS_TEST_PATH:-./neutron/tests/unit}  --load-list /tmp/tmpICNqRQ
  stack15471 15470 15471  1.6  2.0 152056 164812 python -m subunit.run 
discover -t ./ ./neutron/tests/functional --load-list /tmp/tmpICNqRQ
  stack15474 15445 15474  0.0  0.0   328   792 /bin/sh -c 
OS_STDOUT_CAPTURE=${OS_STDOUT_CAPTURE:-1} \ 
OS_STDERR_CAPTURE=${OS_STDERR_CAPTURE:-1} \ OS_LOG_CAPTURE=${OS_LOG_CAPTURE:-1} 
\ OS_TEST_TIMEOUT=${OS_TEST_TIMEOUT:-160} \ ${PYTHON:-python} -m subunit.run 
discover -t ./ ${OS_TEST_PATH:-./neutron/tests/unit}  --load-list /tmp/tmpe646Tl
  stack15475 15474 15475  1.6  1.9 149972 162516 python -m subunit.run 
discover -t ./ ./neutron/tests/functional --load-list /tmp/tmpe646Tl
  stack15476 15445 15476  0.0  0.0   328   804 /bin/sh -c 
OS_STDOUT_CAPTURE=${OS_STDOUT_CAPTURE:-1} \ 
OS_STDERR_CAPTURE=${OS_STDERR_CAPTURE:-1} \ OS_LOG_CAPTURE=${OS_LOG_CAPTURE:-1} 
\ OS_TEST_TIMEOUT=${OS_TEST_TIMEOUT:-160} \ ${PYTHON:-python} -m subunit.run 
discover -t ./ ${OS_TEST_PATH:-./neutron/tests/unit}  --load-list /tmp/tmpv2ovhz
  stack15477 15476 15477  1.2  1.8 136760 149160 python -m subunit.run 
discover -t ./ ./neutron/tests/functional --load-list /tmp/tmpv2ovhz
  stack15478 15445 15478  0.0  0.0   328   712 /bin/sh -c 
OS_STDOUT_CAPTURE=${OS_STDOUT_CAPTURE:-1} \ 
OS_STDERR_CAPTURE=${OS_STDERR_CAPTURE:-1} \ OS_LOG_CAPTURE=${OS_LOG_CAPTURE:-1} 
\ OS_TEST_TIMEOUT=${OS_TEST_TIMEOUT:-160} \ ${PYTHON:-python} -m subunit.run 
discover -t ./ ${OS_TEST_PATH:-./neutron/tests/unit}  --load-list /tmp/tmpDqXE8S
  stack15479 15478 15479  1.5  1.9 148784 161004 python -m subunit.run 
discover -t ./ ./neutron/tests/functional --load-list /tmp/tmpDqXE8S
  stack15480 15445 15480  0.0  0.0   328   804 /bin/sh -c 
OS_STDOUT_CAPTURE=${OS_STDOUT_CAPTURE:-1} \ 
OS_STDERR_CAPTURE=${OS_STDERR_CAPTURE:-1} \ OS_LOG_CAPTURE=${OS_LOG_CAPTURE:-1} 
\ OS_TEST_TIMEOUT=${OS_TEST_TIMEOUT:-160} \ ${PYTHON:-python} -m subunit.run 
discover -t ./ ${OS_TEST_PATH:-./neutron/tests/unit}  --load-list /tmp/tmpTmmShS
  stack15482 15480 15482  1.6  1.9 148856 161516 python -m subunit.run 
discover -t ./ ./neutron/tests/functional --load-list /tmp/tmpTmmShS

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

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

[Kernel-packages] [Bug 1713467] Re: linux-aws: -proposed tracker

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

** Description changed:

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

** Description changed:

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

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

Title:
  linux-aws:  -proposed tracker

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

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

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

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

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

[Kernel-packages] [Bug 1713462] Re: linux: 4.4.0-94.117 -proposed tracker

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

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

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

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  backports: 1713463
  derivatives: 1713464,1713465,1713467,1713468,1713469
+ kernel-stable-phase-changed:Tuesday, 29. August 2017 09:02 UTC
+ kernel-stable-phase:Uploaded

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  backports: 1713463
  derivatives: 1713464,1713465,1713467,1713468,1713469
  kernel-stable-phase-changed:Tuesday, 29. August 2017 09:02 UTC
  kernel-stable-phase:Uploaded
+ 
+ -- swm properties --
+ phase: Uploaded

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

Title:
  linux: 4.4.0-94.117 -proposed tracker

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

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

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

  backports: 1713463
  derivatives: 1713464,1713465,1713467,1713468,1713469
  kernel-stable-phase-changed:Tuesday, 29. August 2017 09:02 UTC
  kernel-stable-phase:Uploaded

  -- swm properties --
  phase: Uploaded

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

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

[Kernel-packages] [Bug 1712857] Re: inode-flags stressor is reporting directory errors on startup

2017-08-29 Thread Colin Ian King

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

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

Title:
  inode-flags stressor is reporting directory errors on startup

Status in linux package in Ubuntu:
  Fix Released

Bug description:
  Running more than 1 stressor instance throws up the following issue:

stress-ng: debug: [26676] 4 processors online, 4 processors configured
stress-ng: info:  [26676] dispatching hogs: 4 inode-flags
stress-ng: debug: [26676] cache allocate: reducing cache level from L3 (too 
high) to L1
stress-ng: debug: [26676] cache allocate: default cache size: 64K
stress-ng: debug: [26676] starting stressors
stress-ng: debug: [26677] stress-ng-inode-flags: started [26677] (instance 
0)
stress-ng: debug: [26678] stress-ng-inode-flags: started [26678] (instance 
1)
stress-ng: debug: [26679] stress-ng-inode-flags: started [26679] (instance 
2)
stress-ng: debug: [26676] 4 stressors spawned
stress-ng: debug: [26680] stress-ng-inode-flags: started [26680] (instance 
3)
stress-ng: fail:  [26680] stress-ng-inode-flags: mkdir failed, errno=1 
(Operation not permitted)
stress-ng: debug: [26680] stress-ng-inode-flags: exited [26680] (instance 3)
stress-ng: debug: [26678] stress-ng-inode-flags: exited [26678] (instance 1)
stress-ng: debug: [26677] stress-ng-inode-flags: exited [26677] (instance 0)
stress-ng: debug: [26679] stress-ng-inode-flags: exited [26679] (instance 2)
stress-ng: debug: [26676] process [26677] terminated
stress-ng: debug: [26676] process [26678] terminated
stress-ng: debug: [26676] process [26679] terminated
stress-ng: error: [26676] process 26680 (stress-ng-inode_flags) terminated 
with an error, exit status=1 (stress-ng core failure)
stress-ng: debug: [26676] process [26680] terminated
stress-ng: info:  [26676] unsuccessful run completed in 5.37s

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

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

[Kernel-packages] [Bug 1701222] Re: [Hyper-V] LIS daemons fail to start after disable/re-enable VM integration services

2017-08-29 Thread Ionut Lenghel

I have tested the kernel provided. The issue still occurs.

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

Title:
  [Hyper-V] LIS daemons fail to start after disable/re-enable VM
  integration services

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

Bug description:
  Issue description: Hyper-V daemons fail to start after disable/re-
  enable VM integration services.

  Platform: host independent
  Affected daemons - KVP, FCOPY and VSS.

  Distribution name and release: Ubuntu 16.04, Ubuntu 17.04
  Kernel version: 4.11.0-rc7-next-20170421 (for Ubuntu 16.04), 
4.10.0-19-generic (for Ubuntu 17.04)

  Repro rate: 100%

  Steps to reproduce:
  1.Start VM with Guest Services enabled (FCopy daemon starts automatically)
  2.Go to File > Settings > Integration Services, uncheck Guest Services 
and apply (FCopy daemon will stop at this point)
  3.Re-enable Guest Services from VM Settings (Fcopy daemon is not running).
  This is the issue. systemd monitors for the service and if we have the hook 
for the Guest Service, it tries to start the daemon again.
  systemd attempt to start any of the LIS daemons will fail, but manually 
executing the daemon binary, it will start the daemon.

  Additional Info:
  - the steps above can be repro'd with KVP / Data Exchange integration service 
as well.
  - Manually starting hv_fcopy_daemon works fine.
  - other distros (RHEL) does not have this behavior, the LIS daemons are 
started automatically by systemd once we re-enable the integration service.

  On the upstream kernel and the upstream hv daemons, these messages are 
recorded in syslog, once we re-enable the Guest service:
  HV_FCOPY: pread failed: Bad file descriptor
  systemd[1]: hv-fcopy-daemon.service: Main process exited, code=exited, 
status=1/FAILURE
  systemd[1]: hv-fcopy-daemon.service: Unit entered failed state.
  systemd[1]: hv-fcopy-daemon.service: Failed with result 'exit-code'.

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

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

[Kernel-packages] [Bug 1713684] [NEW] Wi-Fi card not accessible

2017-08-29 Thread Kon Mal

Public bug reported:

I did a "sudo apt dist-upgrade" and I reboot my computer. After that was
like my Wi-Fi device was damaged. I booted through the older kernel and
the problem wasn't there.

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


** Tags: kernel-bug

** Summary changed:

- Wi-Fi cord not accessible
+ Wi-Fi card not accessible

** Tags removed: kernel
** Tags added: kernel-bug

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

Title:
  Wi-Fi card not accessible

Status in linux package in Ubuntu:
  New

Bug description:
  I did a "sudo apt dist-upgrade" and I reboot my computer. After that
  was like my Wi-Fi device was damaged. I booted through the older
  kernel and the problem wasn't there.

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

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

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

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

apport-collect 1713684

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

Title:
  Wi-Fi card not accessible

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I did a "sudo apt dist-upgrade" and I reboot my computer. After that
  was like my Wi-Fi device was damaged. I booted through the older
  kernel and the problem wasn't there.

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

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

[Kernel-packages] [Bug 1713467] Re: linux-aws: -proposed tracker

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

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

Title:
  linux-aws:  -proposed tracker

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

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

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

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

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

[Kernel-packages] [Bug 1713470] Re: linux: 4.10.0-34.38 -proposed tracker

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

Title:
  linux: 4.10.0-34.38 -proposed tracker

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

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

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

  backports: 1713471,1713472
  derivatives: 1713473
  kernel-stable-phase-changed:Monday, 28. August 2017 19:32 UTC
  kernel-stable-phase:Uploaded

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

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

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

[Kernel-packages] [Bug 1713458] Re: linux-lts-trusty: -proposed tracker

** Changed in: linux-lts-trusty (Ubuntu Precise)
   Status: New => Confirmed

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

Title:
  linux-lts-trusty:  -proposed tracker

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

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

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

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

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

[Kernel-packages] [Bug 1713459] Re: linux: -proposed tracker

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

Title:
  linux:  -proposed tracker

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

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

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

  backports: 1713461
  derivatives:

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

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

[Kernel-packages] [Bug 1713462] Re: linux: 4.4.0-94.117 -proposed tracker

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

Title:
  linux: 4.4.0-94.117 -proposed tracker

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

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

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

  backports: 1713463
  derivatives: 1713464,1713465,1713467,1713468,1713469
  kernel-stable-phase-changed:Tuesday, 29. August 2017 09:02 UTC
  kernel-stable-phase:Uploaded

  -- swm properties --
  phase: Uploaded

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

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

[Kernel-packages] [Bug 1713461] Re: linux-lts-vivid: -proposed tracker

** Changed in: linux-lts-vivid (Ubuntu Trusty)
   Status: New => Confirmed

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

Title:
  linux-lts-vivid:  -proposed tracker

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

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

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

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

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

[Kernel-packages] [Bug 1709293] Re: linux-lts-trusty: 3.13.0-129.178~precise1 -proposed tracker

** Changed in: kernel-sru-workflow/promote-to-security
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Andy 
Whitcroft (apw)

** Changed in: kernel-sru-workflow/promote-to-security
   Status: Confirmed => In Progress

** Changed in: kernel-sru-workflow/promote-to-updates
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Andy 
Whitcroft (apw)

** Changed in: kernel-sru-workflow/promote-to-updates
   Status: Confirmed => In Progress

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

Title:
  linux-lts-trusty: 3.13.0-129.178~precise1 -proposed tracker

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

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1709292
  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/1709293/+subscriptions

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

[Kernel-packages] [Bug 1713455] Re: linux: -proposed tracker

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

Title:
  linux:  -proposed tracker

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

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

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

  backports: 
  derivatives:

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

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

[Kernel-packages] [Bug 1713456] Re: linux: -proposed tracker

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

Title:
  linux:  -proposed tracker

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

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

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

  backports: 1713458
  derivatives:

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

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

[Kernel-packages] [Bug 1713691] [NEW] kernel: xhci_hcd 0000:00:14.0: WARN Event TRB for slot 2 ep 16 with no TDs queued?

2017-08-29 Thread dino99

Public bug reported:

I have a new canon pixma mx475 printer plugged via usb2 port.
And journalctl is flooded each time i power on that printer, with this error.
"kernel: xhci_hcd :00:14.0: WARN Event TRB for slot 2 ep 16 with no TDs 
queued?"

Googling around that issue, many distro had warn about that; and
upstream has also proposed a solution:
https://lkml.org/lkml/2017/2/14/768

Please patch the ubuntu's kernels until upstream make it default.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: linux-image-4.12.0-12-generic 4.12.0-12.13
ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8
Uname: Linux 4.12.0-12-generic x86_64
ApportVersion: 2.20.6-0ubuntu7
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  oem1500 F pulseaudio
CurrentDesktop: GNOME
Date: Tue Aug 29 12:12:44 2017
EcryptfsInUse: Yes
HibernationDevice: RESUME=UUID=06a0e343-7443-402b-a607-1fe53f3c1ac3
IwConfig:
 lono wireless extensions.
 
 enp2s0no wireless extensions.
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 002: ID 046d:c062 Logitech, Inc. M-UAS144 [LS1 Laser Mouse]
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.12.0-12-generic 
root=UUID=8a00317c-669e-447c-bc40-1e06010b49ca ro
RelatedPackageVersions:
 linux-restricted-modules-4.12.0-12-generic N/A
 linux-backports-modules-4.12.0-12-generic  N/A
 linux-firmware 1.167
RfKill:
 
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/07/2016
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P7.00
dmi.board.name: B150M-HDV
dmi.board.vendor: ASRock
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP7.00:bd10/07/2016:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB150M-HDV:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.family: To Be Filled By O.E.M.
dmi.product.name: To Be Filled By O.E.M.
dmi.product.version: To Be Filled By O.E.M.
dmi.sys.vendor: To Be Filled By O.E.M.

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


** Tags: amd64 apport-bug artful package-from-proposed wayland-session

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

Title:
  kernel: xhci_hcd :00:14.0: WARN Event TRB for slot 2 ep 16 with no
  TDs queued?

Status in linux package in Ubuntu:
  New

Bug description:
  I have a new canon pixma mx475 printer plugged via usb2 port.
  And journalctl is flooded each time i power on that printer, with this error.
  "kernel: xhci_hcd :00:14.0: WARN Event TRB for slot 2 ep 16 with no TDs 
queued?"

  Googling around that issue, many distro had warn about that; and
  upstream has also proposed a solution:
  https://lkml.org/lkml/2017/2/14/768

  Please patch the ubuntu's kernels until upstream make it default.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.12.0-12-generic 4.12.0-12.13
  ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8
  Uname: Linux 4.12.0-12-generic x86_64
  ApportVersion: 2.20.6-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  oem1500 F pulseaudio
  CurrentDesktop: GNOME
  Date: Tue Aug 29 12:12:44 2017
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=06a0e343-7443-402b-a607-1fe53f3c1ac3
  IwConfig:
   lono wireless extensions.
   
   enp2s0no wireless extensions.
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 046d:c062 Logitech, Inc. M-UAS144 [LS1 Laser Mouse]
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.12.0-12-generic 
root=UUID=8a00317c-669e-447c-bc40-1e06010b49ca ro
  RelatedPackageVersions:
   linux-restricted-modules-4.12.0-12-generic N/A
   linux-backports-modules-4.12.0-12-generic  N/A
   linux-firmware 1.167
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/07/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P7.00
  dmi.board.name: B150M-HDV
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP7.00:bd10/07/2016:svnToBeFilledByO.E.M.:pnToB

[Kernel-packages] [Bug 1709293] Re: linux-lts-trusty: 3.13.0-129.178~precise1 -proposed tracker

The package has been published and the bug is being set to Fix Released


** Changed in: kernel-sru-workflow/promote-to-security
   Status: In Progress => Fix Released

** Changed in: kernel-sru-workflow/promote-to-updates
   Status: In Progress => Fix Released

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

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1709292
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true
+ kernel-stable-phase:Released
+ kernel-stable-phase-changed:Tuesday, 29. August 2017 10:31 UTC

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1709292
- phase: Promoted to proposed
+ phase: Released
  proposed-announcement-sent: true
  proposed-testing-requested: true
- kernel-stable-phase:Released
- kernel-stable-phase-changed:Tuesday, 29. August 2017 10:31 UTC

** Tags removed: kernel-release-tracking-bug-live

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

Title:
  linux-lts-trusty: 3.13.0-129.178~precise1 -proposed tracker

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

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1709292
  phase: Released
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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

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

This change was made by a bot.

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

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

Title:
  kernel: xhci_hcd :00:14.0: WARN Event TRB for slot 2 ep 16 with no
  TDs queued?

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have a new canon pixma mx475 printer plugged via usb2 port.
  And journalctl is flooded each time i power on that printer, with this error.
  "kernel: xhci_hcd :00:14.0: WARN Event TRB for slot 2 ep 16 with no TDs 
queued?"

  Googling around that issue, many distro had warn about that; and
  upstream has also proposed a solution:
  https://lkml.org/lkml/2017/2/14/768

  Please patch the ubuntu's kernels until upstream make it default.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.12.0-12-generic 4.12.0-12.13
  ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8
  Uname: Linux 4.12.0-12-generic x86_64
  ApportVersion: 2.20.6-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  oem1500 F pulseaudio
  CurrentDesktop: GNOME
  Date: Tue Aug 29 12:12:44 2017
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=06a0e343-7443-402b-a607-1fe53f3c1ac3
  IwConfig:
   lono wireless extensions.
   
   enp2s0no wireless extensions.
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 046d:c062 Logitech, Inc. M-UAS144 [LS1 Laser Mouse]
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.12.0-12-generic 
root=UUID=8a00317c-669e-447c-bc40-1e06010b49ca ro
  RelatedPackageVersions:
   linux-restricted-modules-4.12.0-12-generic N/A
   linux-backports-modules-4.12.0-12-generic  N/A
   linux-firmware 1.167
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/07/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P7.00
  dmi.board.name: B150M-HDV
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP7.00:bd10/07/2016:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB150M-HDV:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

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

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

[Kernel-packages] [Bug 1709294] Re: linux: 3.19.0-92.100 -proposed tracker

The package has been published and the bug is being set to Fix Released


** Changed in: kernel-sru-workflow/promote-to-security
   Status: Confirmed => Fix Released

** Changed in: kernel-sru-workflow/promote-to-updates
   Status: Confirmed => Fix Released

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

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  backports: 1709295
  derivatives:
  -- swm properties --
  boot-testing-requested: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true
+ kernel-stable-phase-changed:Tuesday, 29. August 2017 11:01 UTC
+ kernel-stable-phase:Released

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  backports: 1709295
  derivatives:
  -- swm properties --
  boot-testing-requested: true
- phase: Promoted to proposed
+ phase: Released
  proposed-announcement-sent: true
  proposed-testing-requested: true
- kernel-stable-phase-changed:Tuesday, 29. August 2017 11:01 UTC
- kernel-stable-phase:Released

** Tags removed: kernel-release-tracking-bug-live

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

Title:
  linux: 3.19.0-92.100 -proposed tracker

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

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

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

  backports: 1709295
  derivatives:
  -- swm properties --
  boot-testing-requested: true
  phase: Released
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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

[Kernel-packages] [Bug 1709032] Re: Creating conntrack entry failure with kernel 4.4.0-89

2017-08-29 Thread Dr. Jens Harbott

** Tags removed: verification-needed-xenial
** Tags added: 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/1709032

Title:
  Creating conntrack entry failure with kernel 4.4.0-89

Status in Linux:
  Confirmed
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Xenial:
  Fix Released

Bug description:
  The functional job failure rate is at 100%. Every time some test gets
  stuck and job is killed after timeout.

  logstash query:
  
http://logstash.openstack.org/#dashboard/file/logstash.json?query=build_name%3A%5C
  %22gate-neutron-dsvm-functional-ubuntu-
  
xenial%5C%22%20AND%20tags%3Aconsole%20AND%20message%3A%5C%22Killed%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20timeout%20-s%209%5C%22

  2017-08-05 12:36:50.127672 | /home/jenkins/workspace/gate-neutron-
  dsvm-functional-ubuntu-xenial/devstack-gate/functions.sh: line 1129:
  15261 Killed  timeout -s 9 ${REMAINING_TIME}m bash -c
  "source $WORKSPACE/devstack-gate/functions.sh && $cmd"

  There are a few test executors left, which means there are more tests
  stuck:

  stack15468 15445 15468  0.0  0.0   328   796 /bin/sh -c 
OS_STDOUT_CAPTURE=${OS_STDOUT_CAPTURE:-1} \ 
OS_STDERR_CAPTURE=${OS_STDERR_CAPTURE:-1} \ OS_LOG_CAPTURE=${OS_LOG_CAPTURE:-1} 
\ OS_TEST_TIMEOUT=${OS_TEST_TIMEOUT:-160} \ ${PYTHON:-python} -m subunit.run 
discover -t ./ ${OS_TEST_PATH:-./neutron/tests/unit}  --load-list /tmp/tmpDTLPoX
  stack15469 15468 15469  1.5  1.8 139332 150008 python -m subunit.run 
discover -t ./ ./neutron/tests/functional --load-list /tmp/tmpDTLPoX
  stack15470 15445 15470  0.0  0.0   328   700 /bin/sh -c 
OS_STDOUT_CAPTURE=${OS_STDOUT_CAPTURE:-1} \ 
OS_STDERR_CAPTURE=${OS_STDERR_CAPTURE:-1} \ OS_LOG_CAPTURE=${OS_LOG_CAPTURE:-1} 
\ OS_TEST_TIMEOUT=${OS_TEST_TIMEOUT:-160} \ ${PYTHON:-python} -m subunit.run 
discover -t ./ ${OS_TEST_PATH:-./neutron/tests/unit}  --load-list /tmp/tmpICNqRQ
  stack15471 15470 15471  1.6  2.0 152056 164812 python -m subunit.run 
discover -t ./ ./neutron/tests/functional --load-list /tmp/tmpICNqRQ
  stack15474 15445 15474  0.0  0.0   328   792 /bin/sh -c 
OS_STDOUT_CAPTURE=${OS_STDOUT_CAPTURE:-1} \ 
OS_STDERR_CAPTURE=${OS_STDERR_CAPTURE:-1} \ OS_LOG_CAPTURE=${OS_LOG_CAPTURE:-1} 
\ OS_TEST_TIMEOUT=${OS_TEST_TIMEOUT:-160} \ ${PYTHON:-python} -m subunit.run 
discover -t ./ ${OS_TEST_PATH:-./neutron/tests/unit}  --load-list /tmp/tmpe646Tl
  stack15475 15474 15475  1.6  1.9 149972 162516 python -m subunit.run 
discover -t ./ ./neutron/tests/functional --load-list /tmp/tmpe646Tl
  stack15476 15445 15476  0.0  0.0   328   804 /bin/sh -c 
OS_STDOUT_CAPTURE=${OS_STDOUT_CAPTURE:-1} \ 
OS_STDERR_CAPTURE=${OS_STDERR_CAPTURE:-1} \ OS_LOG_CAPTURE=${OS_LOG_CAPTURE:-1} 
\ OS_TEST_TIMEOUT=${OS_TEST_TIMEOUT:-160} \ ${PYTHON:-python} -m subunit.run 
discover -t ./ ${OS_TEST_PATH:-./neutron/tests/unit}  --load-list /tmp/tmpv2ovhz
  stack15477 15476 15477  1.2  1.8 136760 149160 python -m subunit.run 
discover -t ./ ./neutron/tests/functional --load-list /tmp/tmpv2ovhz
  stack15478 15445 15478  0.0  0.0   328   712 /bin/sh -c 
OS_STDOUT_CAPTURE=${OS_STDOUT_CAPTURE:-1} \ 
OS_STDERR_CAPTURE=${OS_STDERR_CAPTURE:-1} \ OS_LOG_CAPTURE=${OS_LOG_CAPTURE:-1} 
\ OS_TEST_TIMEOUT=${OS_TEST_TIMEOUT:-160} \ ${PYTHON:-python} -m subunit.run 
discover -t ./ ${OS_TEST_PATH:-./neutron/tests/unit}  --load-list /tmp/tmpDqXE8S
  stack15479 15478 15479  1.5  1.9 148784 161004 python -m subunit.run 
discover -t ./ ./neutron/tests/functional --load-list /tmp/tmpDqXE8S
  stack15480 15445 15480  0.0  0.0   328   804 /bin/sh -c 
OS_STDOUT_CAPTURE=${OS_STDOUT_CAPTURE:-1} \ 
OS_STDERR_CAPTURE=${OS_STDERR_CAPTURE:-1} \ OS_LOG_CAPTURE=${OS_LOG_CAPTURE:-1} 
\ OS_TEST_TIMEOUT=${OS_TEST_TIMEOUT:-160} \ ${PYTHON:-python} -m subunit.run 
discover -t ./ ${OS_TEST_PATH:-./neutron/tests/unit}  --load-list /tmp/tmpTmmShS
  stack15482 15480 15482  1.6  1.9 148856 161516 python -m subunit.run 
discover -t ./ ./neutron/tests/functional --load-list /tmp/tmpTmmShS

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

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

[Kernel-packages] [Bug 1713467] Re: linux-aws: 4.4.0-1033.42 -proposed tracker

2017-08-29 Thread Kleber Sacilotto de Souza

** Summary changed:

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

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

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

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

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

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

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

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

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

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

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

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

[Kernel-packages] [Bug 1713729] [NEW] Xenial update to 4.4.84 stable release

Public bug reported:


SRU Justification

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

   git://git.kernel.org/

TEST CASE: TBD

   The following patches from the 4.4.84 stable release shall be
applied:

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

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


** Tags: kernel-stable-tracking-bug

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

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

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

Title:
  Xenial update to 4.4.84 stable release

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

Bug description:
  
  SRU Justification

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

 git://git.kernel.org/

  TEST CASE: TBD

 The following patches from the 4.4.84 stable release shall be
  applied:

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

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

[Kernel-packages] [Bug 1670634] Re: blk-mq: possible deadlock on CPU hot(un)plug

2017-08-29 Thread Juerg Haefliger

Sorry for the late reply, I'm just getting around looking at this. Yes,
I do have access to the folder now, thanks!

Questions: Is this setup currently working with another distribution and
you're just experiencing issues when running Ubuntu? If so, what's that
other distro and kernel? Also, can you give me a high-level overview of
your storage architecture?

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

Title:
  blk-mq: possible deadlock on CPU hot(un)plug

Status in Ubuntu on IBM z Systems:
  Triaged
Status in linux package in Ubuntu:
  Triaged

Bug description:
  == Comment: #0 - Carsten Jacobi  - 2017-03-07 03:35:31 ==
  I'm evaluating Ubuntu-Xenial on z for development purposes, the test system 
is installed in an LPAR with one FCP-LUN which is accessable by 4 pathes (all 
pathes are configured).
  The system hangs regularly when I make packages with "pdebuild" using the 
pbuilder packaging suit.
  The local Linux development team helped me out with a pre-analysis that I can 
post here (thanks a lot for that):

  With the default settings and under a certain workload,
  blk_mq seems to get into a presumed "deadlock".
  Possibly this happens on CPU hot(un)plug.

  After the I/O stalled, a dump was pulled manually.
  The following information is from the crash dump pre-analysis.

  $ zgetdump -i dump.0
  General dump info:
Dump format: elf
Version: 1
UTS node name..: mclint
UTS kernel release.: 4.4.0-65-generic
UTS kernel version.: #86-Ubuntu SMP Thu Feb 23 17:54:37 UTC 2017
System arch: s390x (64 bit)
CPU count (online).: 2
Dump memory range..: 8192 MB
  Memory map:
 - 0001b831afff (7043 MB)
0001b831b000 - 0001 (1149 MB)

  Things look similarly with HWE kernel ubuntu16.04-4.8.0-34.36~16.04.1.

KERNEL: vmlinux.full
  DUMPFILE: dump.0
  CPUS: 2
  DATE: Fri Mar  3 14:31:07 2017
UPTIME: 02:11:20
  LOAD AVERAGE: 13.00, 12.92, 11.37
 TASKS: 411
  NODENAME: mclint
   RELEASE: 4.4.0-65-generic
   VERSION: #86-Ubuntu SMP Thu Feb 23 17:54:37 UTC 2017
   MACHINE: s390x  (unknown Mhz)
MEMORY: 7.8 GB
 PANIC: ""
   PID: 0
   COMMAND: "swapper/0"
  TASK: bad528  (1 of 2)  [THREAD_INFO: b78000]
   CPU: 0
 STATE: TASK_RUNNING (ACTIVE)
  INFO: no panic task found

  crash> dev -d
  MAJOR GENDISKNAME   REQUEST_QUEUE  TOTAL ASYNC  SYNC   DRV
  ...
  8 1e1d6d800  sda1e1d51210  0 23151 4294944145 
N/A(MQ)
  8 1e4e06800  sdc2081b180 23148 4294944148 
N/A(MQ)
  8 1f07800sdb20c75680 23195 4294944101 
N/A(MQ)
  8 1e4e06000  sdd1e4e31210  0 23099 4294944197 
N/A(MQ)
252 1e1d6c800  dm-0   1e1d51b18  9 1 8 
N/A(MQ)
  ...

  So both dm-mpath and sd have requests pending in their block multiqueue.
  The large numbers of sd look strange and seem to be the unsigned formatting 
of the values shown for async multiplied by -1.

  [0.798256] Linux version 4.4.0-65-generic (buildd@z13-011) (gcc version 
5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.4) ) #86-Ubuntu SMP Thu Feb 23 
17:54:37 UTC 2017 (Ubuntu 4.4.0-65.86-generic 4.4.49)
  [0.798262] setup: Linux is running natively in 64-bit mode
  [0.798290] setup: Max memory size: 8192MB
  [0.798298] setup: Reserving 196MB of memory at 7996MB for crashkernel 
(System RAM: 7996MB)

  [0.836923] Kernel command line: root=/dev/mapper/mclint_vg-root
  rootflags=subvol=@ crashkernel=196M BOOT_IMAGE=0

  [ 5281.179428] INFO: task xfsaild/dm-11:1604 blocked for more than 120 
seconds.
  [ 5281.179437]   Not tainted 4.4.0-65-generic #86-Ubuntu
  [ 5281.179438] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [ 5281.179440] xfsaild/dm-11   D 007bcf52 0  1604  2 
0x
  [ 5281.179444]0001e931c230 001a6964 0001e6f9b958 
0001e6f9b9d8
0001e15795f0 0001e6f9b988 00ce8c00 
0001ea805c70
0001ea805c00 00ba5ed0 0001e931c1d0 
0001e1579b20
0001ea805c00 0001e15795f0 0001ea805c00 

007d3978 007bc9f8 0001e6f9b9d8 
0001e6f9ba40
  [ 5281.179454] Call Trace:
  [ 5281.179461] ([<007bc9f8>] __schedule+0x300/0x810)
  [ 5281.179462]  [<007bcf52>] schedule+0x4a/0xb0
  [ 5281.179465]  [<007c02aa>] schedule_timeout+0x232/0x2a8
  [ 5281.179466]  [<007bde50>] wait_for_common+0x110/0x1c8
  [ 5281.179472]  [<0017b602>] flush_work+0x42/0x58
  [ 5281.179564]  [<03ff805e14b

[Kernel-packages] [Bug 1713729] Re: Xenial update to 4.4.84 stable release

Skipped "netfilter: nf_ct_ext: fix possible panic after
nf_ct_extend_unregister" because it was already applied for bug #1713729
Creating conntrack entry failure with kernel 4.4.0-89.

Adjusted file to patch of "perf/x86: Fix LBR related crashes on Intel
Atom" to match changes introduced by bug #1559914 Disable multi-record
PEBS on Merom. Patch did apply cleanly to new location.

** Description changed:

+ SRU Justification
  
- SRU Justification
+ Impact:
+    The upstream process for stable tree updates is quite similar
+    in scope to the Ubuntu SRU process, e.g., each patch has to
+    demonstrably fix a bug, and each patch is vetted by upstream
+    by originating either directly from a mainline/stable Linux tree or
+    a minimally backported form of that patch. The 4.4.84 upstream stable
+    patch set is now available. It should be included in the Ubuntu
+    kernel as well.
  
- Impact:
-The upstream process for stable tree updates is quite similar
-in scope to the Ubuntu SRU process, e.g., each patch has to
-demonstrably fix a bug, and each patch is vetted by upstream
-by originating either directly from a mainline/stable Linux tree or
-a minimally backported form of that patch. The 4.4.84 upstream stable
-patch set is now available. It should be included in the Ubuntu
-kernel as well.
+    git://git.kernel.org/
  
-git://git.kernel.org/
+ TEST CASE: TBD
  
- TEST CASE: TBD
- 
-The following patches from the 4.4.84 stable release shall be
- applied:
+ The following patches from the 4.4.84 stable release shall be applied:
+ * audit: Fix use after free in audit_remove_watch_rule()
+ * parisc: pci memory bar assignment fails with 64bit kernels on dino/cujo
+ * crypto: x86/sha1 - Fix reads beyond the number of blocks passed
+ * Input: elan_i2c - add ELAN0608 to the ACPI table
+ * Input: elan_i2c - Add antoher Lenovo ACPI ID for upcoming Lenovo NB
+ * ALSA: seq: 2nd attempt at fixing race creating a queue
+ * ALSA: usb-audio: Apply sample rate quirk to Sennheiser headset
+ * ALSA: usb-audio: Add mute TLV for playback volumes on C-Media devices
+ * mm/mempolicy: fix use after free when calling get_mempolicy
+ * mm: revert x86_64 and arm64 ELF_ET_DYN_BASE base changes
+ * xen: fix bio vec merging
+ * x86/asm/64: Clear AC on NMI entries
+ * irqchip/atmel-aic: Fix unbalanced of_node_put() in aic_common_irq_fixup()
+ * irqchip/atmel-aic: Fix unbalanced refcount in aic_common_rtc_irq_fixup()
+ * Sanitize 'move_pages()' permission checks
+ * pids: make task_tgid_nr_ns() safe
+ * perf/x86: Fix LBR related crashes on Intel Atom
+ * usb: optimize acpi companion search for usb port devices
+ * usb: qmi_wwan: add D-Link DWM-222 device ID
+ * Linux 4.4.84

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

Title:
  Xenial update to 4.4.84 stable release

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

Bug description:
  SRU Justification

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

     git://git.kernel.org/

  TEST CASE: TBD

  The following patches from the 4.4.84 stable release shall be applied:
  * audit: Fix use after free in audit_remove_watch_rule()
  * parisc: pci memory bar assignment fails with 64bit kernels on dino/cujo
  * crypto: x86/sha1 - Fix reads beyond the number of blocks passed
  * Input: elan_i2c - add ELAN0608 to the ACPI table
  * Input: elan_i2c - Add antoher Lenovo ACPI ID for upcoming Lenovo NB
  * ALSA: seq: 2nd attempt at fixing race creating a queue
  * ALSA: usb-audio: Apply sample rate quirk to Sennheiser headset
  * ALSA: usb-audio: Add mute TLV for playback volumes on C-Media devices
  * mm/mempolicy: fix use after free when calling get_mempolicy
  * mm: revert x86_64 and arm64 ELF_ET_DYN_BASE base changes
  * xen: fix bio vec merging
  * x86/asm/64: Clear AC on NMI entries
  * irqchip/atmel-aic: Fix unbalanced of_node_put() in aic_common_irq_fixup()
  * irqchip/atmel-aic: Fix unbalanced refcount in aic_common_rtc_irq_fixup()
  * Sanitize 'move_pages()' permission checks
  * pids: make task_tgid_nr_ns() safe
  * perf/x86: Fix LBR related crashes on Intel Atom
  * usb: optimize acpi companion search for usb port devices
  * usb: qmi_wwan: add D-Link DWM-222 device ID
  * Linux 4.4.84

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

[Kernel-packages] [Bug 1713467] Re: linux-aws: 4.4.0-1033.42 -proposed tracker

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

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

** Description changed:

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

** Description changed:

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

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

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

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

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

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

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

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

[Kernel-packages] [Bug 1709784] Re: KVM on 16.04.3 throws an error

2017-08-29 Thread Amartey Pearson

I ran into this issue as well, and confirmed with the kernel built above
(http://kernel.ubuntu.com/~jsalisbury/lp1709784/xenial/) that things now
work again.  Thanks!

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

Title:
  KVM on 16.04.3 throws an error

Status in The Ubuntu-power-systems project:
  In Progress
Status in linux package in Ubuntu:
  In Progress
Status in qemu package in Ubuntu:
  Won't Fix
Status in linux source package in Xenial:
  In Progress
Status in linux source package in Zesty:
  Invalid

Bug description:
  Problem Description
  
  KVM on Ubuntu 16.04.3 throws an error when used
   
  ---uname output---
  Linux bastion-1 4.4.0-89-generic #112-Ubuntu SMP Mon Jul 31 19:37:08 UTC 2017 
ppc64le ppc64le ppc64le GNU/Linux
   
  Machine Type =  8348-21C Habanero 
   
  ---Steps to Reproduce---
   Install 16.04.3

  install KVM like:

  apt-get install libvirt-bin qemu qemu-slof qemu-system qemu-utils

  then exit and log back in so virsh will work without sudo

  then run my spawn script

  $ cat spawn.sh
  #!/bin/bash

  img=$1
  qemu-system-ppc64 \
  -machine pseries,accel=kvm,usb=off -cpu host -m 512 \
  -display none -nographic \
  -net nic -net user \
  -drive "file=$img"

  with a freshly downloaded ubuntu cloud image

  sudo ./spawn.sh xenial-server-cloudimg-ppc64el-disk1.img

  And I get nothing on the output.

  and errors in dmesg

  
  ubuntu@bastion-1:~$ [  340.180295] Facility 'TM' unavailable, exception at 
0xd000148b7f10, MSR=90009033
  [  340.180399] Oops: Unexpected facility unavailable exception, sig: 6 [#1]
  [  340.180513] SMP NR_CPUS=2048 NUMA PowerNV
  [  340.180547] Modules linked in: xt_CHECKSUM iptable_mangle ipt_MASQUERADE 
nf_nat_masquerade_ipv4 iptable_nat nf_nat_ipv4 nf_nat nf_conntrack_ipv4 
nf_defrag_ipv4 xt_conntrack nf_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp 
bridge stp llc ebtable_filter ebtables ip6table_filter ip6_tables 
iptable_filter ip_tables x_tables kvm_hv kvm binfmt_misc joydev input_leds 
mac_hid opal_prd ofpart cmdlinepart powernv_flash ipmi_powernv ipmi_msghandler 
mtd at24 uio_pdrv_genirq uio ibmpowernv powernv_rng vmx_crypto 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 raid1 raid0 multipath 
linear mlx4_en hid_generic usbhid hid uas usb_storage ast i2c_algo_bit bnx2x 
ttm drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops mlx4_core drm 
ahci vxlan libahci ip6_udp_tunnel udp_tunnel mdio libcrc32c
  [  340.181331] CPU: 46 PID: 5252 Comm: qemu-system-ppc Not tainted 
4.4.0-89-generic #112-Ubuntu
  [  340.181382] task: c01e34c30b50 ti: c01e34ce4000 task.ti: 
c01e34ce4000
  [  340.181432] NIP: d000148b7f10 LR: d00014822a14 CTR: 
d000148b7e40
  [  340.181475] REGS: c01e34ce77b0 TRAP: 0f60   Not tainted  
(4.4.0-89-generic)
  [  340.181519] MSR: 90009033   CR: 22024848  
XER: 
  [  340.181629] CFAR: d000148b7ea4 SOFTE: 1 
  GPR00: d00014822a14 c01e34ce7a30 d000148cc018 c01e37bc 
  GPR04: c01db9ac c01e34ce7bc0   
  GPR08: 0001 c01e34c30b50 0001 d000148278f8 
  GPR12: d000148b7e40 cfb5b500  001f 
  GPR16: 3fff91c3 0080 3fffa8e34390 3fff9242f200 
  GPR20: 3fff92430010 01001de5c030 3fff9242eb60 100c1ff0 
  GPR24: 3fffc91fe990 3fff91c10028  c01e37bc 
  GPR28:  c01db9ac c01e37bc c01db9ac 
  [  340.182315] NIP [d000148b7f10] kvmppc_vcpu_run_hv+0xd0/0xff0 [kvm_hv]
  [  340.182357] LR [d00014822a14] kvmppc_vcpu_run+0x44/0x60 [kvm]
  [  340.182394] Call Trace:
  [  340.182413] [c01e34ce7a30] [c01e34ce7ab0] 0xc01e34ce7ab0 
(unreliable)
  [  340.182468] [c01e34ce7b70] [d00014822a14] 
kvmppc_vcpu_run+0x44/0x60 [kvm]
  [  340.182522] [c01e34ce7ba0] [d0001481f674] 
kvm_arch_vcpu_ioctl_run+0x64/0x170 [kvm]
  [  340.182581] [c01e34ce7be0] [d00014813918] 
kvm_vcpu_ioctl+0x528/0x7b0 [kvm]
  [  340.182634] [c01e34ce7d40] [c02fffa0] do_vfs_ioctl+0x480/0x7d0
  [  340.182678] [c01e34ce7de0] [c03003c4] SyS_ioctl+0xd4/0xf0
  [  340.182723] [c01e34ce7e30] [c0009204] system_call+0x38/0xb4
  [  340.182766] Instruction dump:
  [  340.182788] e92d02a0 e9290a50 e9290108 792a07e3 41820058 e92d02a0 e9290a50 
e9290108 
  [  340.182863] 7927e8a4 78e71f87 40820ed8 e92d02a0 <7d4022a6> f9490ee8 
e92d02a0 7d4122a6 
  [  340.182938] ---[ end trace bc5080cb7d18f102 ]---
  [  340.276202] 

  
  This was with the latest ubuntu cloud image. I get the same thing when trying 
to use virt-in

[Kernel-packages] [Bug 1713729] Re: Xenial update to 4.4.84 stable release

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

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

** Changed in: linux (Ubuntu Xenial)
 Assignee: (unassigned) => Stefan Bader (smb)

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

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

Title:
  Xenial update to 4.4.84 stable release

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

Bug description:
  SRU Justification

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

     git://git.kernel.org/

  TEST CASE: TBD

  The following patches from the 4.4.84 stable release shall be applied:
  * audit: Fix use after free in audit_remove_watch_rule()
  * parisc: pci memory bar assignment fails with 64bit kernels on dino/cujo
  * crypto: x86/sha1 - Fix reads beyond the number of blocks passed
  * Input: elan_i2c - add ELAN0608 to the ACPI table
  * Input: elan_i2c - Add antoher Lenovo ACPI ID for upcoming Lenovo NB
  * ALSA: seq: 2nd attempt at fixing race creating a queue
  * ALSA: usb-audio: Apply sample rate quirk to Sennheiser headset
  * ALSA: usb-audio: Add mute TLV for playback volumes on C-Media devices
  * mm/mempolicy: fix use after free when calling get_mempolicy
  * mm: revert x86_64 and arm64 ELF_ET_DYN_BASE base changes
  * xen: fix bio vec merging
  * x86/asm/64: Clear AC on NMI entries
  * irqchip/atmel-aic: Fix unbalanced of_node_put() in aic_common_irq_fixup()
  * irqchip/atmel-aic: Fix unbalanced refcount in aic_common_rtc_irq_fixup()
  * Sanitize 'move_pages()' permission checks
  * pids: make task_tgid_nr_ns() safe
  * perf/x86: Fix LBR related crashes on Intel Atom
  * usb: optimize acpi companion search for usb port devices
  * usb: qmi_wwan: add D-Link DWM-222 device ID
  * Linux 4.4.84

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

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

[Kernel-packages] [Bug 1713729] Re: Xenial update to 4.4.84 stable release

Additionally had to revert "UBUNTU: SAUCE: (no-up) ALSA: usb-audio: Add
quirk for sennheiser officerunner" which was applied for bug #1642572
because the same USB ID was now added by "ALSA: usb-audio: Apply sample
rate quirk to Sennheiser headset".

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

Title:
  Xenial update to 4.4.84 stable release

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

Bug description:
  SRU Justification

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

     git://git.kernel.org/

  TEST CASE: TBD

  The following patches from the 4.4.84 stable release shall be applied:
  * audit: Fix use after free in audit_remove_watch_rule()
  * parisc: pci memory bar assignment fails with 64bit kernels on dino/cujo
  * crypto: x86/sha1 - Fix reads beyond the number of blocks passed
  * Input: elan_i2c - add ELAN0608 to the ACPI table
  * Input: elan_i2c - Add antoher Lenovo ACPI ID for upcoming Lenovo NB
  * ALSA: seq: 2nd attempt at fixing race creating a queue
  * ALSA: usb-audio: Apply sample rate quirk to Sennheiser headset
  * ALSA: usb-audio: Add mute TLV for playback volumes on C-Media devices
  * mm/mempolicy: fix use after free when calling get_mempolicy
  * mm: revert x86_64 and arm64 ELF_ET_DYN_BASE base changes
  * xen: fix bio vec merging
  * x86/asm/64: Clear AC on NMI entries
  * irqchip/atmel-aic: Fix unbalanced of_node_put() in aic_common_irq_fixup()
  * irqchip/atmel-aic: Fix unbalanced refcount in aic_common_rtc_irq_fixup()
  * Sanitize 'move_pages()' permission checks
  * pids: make task_tgid_nr_ns() safe
  * perf/x86: Fix LBR related crashes on Intel Atom
  * usb: optimize acpi companion search for usb port devices
  * usb: qmi_wwan: add D-Link DWM-222 device ID
  * Linux 4.4.84

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

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

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

2017-08-29 Thread bugproxy

--- Comment From y...@cn.ibm.com 2017-08-29 10:07 EDT---
Hello,

May I know when we can get the test kernel fix?  Thank you!

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

Title:
  kernel panic -not syncing: Fatal exception: panic_on_oops

Status in Ubuntu on IBM z Systems:
  New
Status in linux package in Ubuntu:
  New

Bug description:
  == Comment: #0 - QI YE  - 2017-08-02 04:11:25 ==
  ---Problem Description---
  Ubuntu got kernel panic

  ---uname output---
  #110-Ubuntu SMP Tue Jul 18 12:56:43 UTC 2017 s390x s390x s390x GNU/Linux
   
  ---Debugger Data---
  PID: 10991  TASK: 19872a0e8 CPU: 2   COMMAND: "hyperkube"
   LOWCORE INFO:
-psw  : 0x0004c0018000 0x00115fa6
-function : pcpu_delegate at 115fa6
-prefix   : 0x7fe42000
-cpu timer: 0x7ffab2827828aa50
-clock cmp: 0xd2eb8b31445e4200
-general registers:
   0x0004e001 0x001283b6
   0xc001 0x8380fcb8
   0x00115f9e 0x0056f6e2
   0x0004 0x00cf9070
   0x0001f3bfc000 0x00112fd8
   0x0001c72bb400 0x0002
   0x7fffc000 0x007c9ef0
   0x00115f9e 0x8380fc18
-access registers:
   0x03ff 0x7910 00 00
   00 00 00 00
   00 00 00 00
   00 00 00 00
-control registers:
   0x14066a12 0x7e6d81c7
   0x00011140 00
   0x2aef 0x0400
   0x5000 0x7e6d81c7
   00 00
   00 00
   00 0x00cfc007
   0xdb00 0x00011280
-floating point registers:
   0x409c7e258000 0x401de4e0
   00 0x3fd24407ab0e073a
   0x3ff0 0x3fee
   0x3fef218f8a7a41a0 0x3fee
   0x0080 00
   0x03ff7f80 0x02aa4940e9e0
   0xd401 0x03ffe81fe110
   00 0x03fff2cfe638

   #0 [8380fc78] smp_find_processor_id at 1160f8
   #1 [8380fc90] machine_kexec at 1135d4
   #2 [8380fcb8] crash_kexec at 1fbb8a
   #3 [8380fd88] panic at 27d0e0
   #4 [8380fe28] die at 1142cc
   #5 [8380fe90] do_low_address at 12215e
   #6 [8380fea8] pgm_check_handler at 7c2ab4
   PSW:  070520018000 02aa267e0e42 (user space)
   GPRS:   02aa2c4fd690 0001
 02aa2c4fd690 03ff7fffee38  0002
 00029c0f 00c42001ea00 0001 0001
 00c42001c5c8 00c42082c1a0 02aa2666325e 03ff7fffed90 
   
  Contact Information = Chee Ye / y...@cn.ibm.com 
   
  Stack trace output:
   no
   
  Oops output:
   [43200.761465] docker0: port 10(vethb9132e9) entered forwarding state
  [50008.560926] hrtimer: interrupt took 1698076 ns
  [123483.768984] systemd[1]: apt-daily.timer: Adding 7h 34min 22.582204s 
random time.
  [123483.930058] systemd[1]: apt-daily.timer: Adding 2h 18min 14.857162s 
random time.
  [123484.064879] systemd[1]: apt-daily.timer: Adding 10h 46min 2.301756s 
random time.
  [123484.824760] systemd[1]: apt-daily.timer: Adding 6h 16min 22.178655s 
random time.
  [153113.703126] conntrack: generic helper won't handle protocol 47. Please 
consider loading the specific helper module.
  [477085.704538] Low-address protection: 0004 ilc:2 [#1] SMP
  [477085.704551] Modules linked in: xt_physdev veth xt_recent xt_comment 
xt_mark xt_nat ipt_MASQUERADE nf_nat_masquerade_ipv4 xfrm_user xfrm_algo 
iptable_nat nf_nat_ipv4 xt_addrtype nf_nat br_netfilter bridge stp llc aufs 
ipt_REJECT nf_reject_ipv4 xt_tcpudp nf_conntrack_ipv4 nf_defrag_ipv4 
xt_conntrack nf_conntrack iptable_filter ip_tables x_tables ghash_s390 prng 
aes_s390 des_s390 des_generic sha512_s390 qeth_l2 sha256_s390 qeth sha1_s390 
qdio sha_common ccwgroup vmur dasd_eckd_mod dasd_mod
  [477085.705522] CPU: 2 PID: 10991 Comm: hyperkube Not tainted 
4.4.0-87-generic #110-Ubuntu
  [477085.705525] task: 00019872a0e8 ti: 8380c000 task.ti: 
8380c000
  [477085.705529] User PSW : 070520018000 02aa267e0e42
  [477085.705532]R:0 T:1 IO:1 EX:1 Key:0 M:1 W:0 P:1 AS:0 CC:2 PM:0 
EA:3
  User GPRS:   02aa2c4fd690 
0001
  [477085.705539]02aa2c4fd690 03ff7fffee38  
0002
  [477085.705553]00029c0f 00c42001ea00 0001 
0001
  [477085.705554]00c42001c5c8 00c42082c1a0 02aa2666325e 
03ff7fffe

[Kernel-packages] [Bug 1667750] Re: xhci_hcd: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 2 comp_code 13

2017-08-29 Thread Johann Hartwig Hauschild

Hi,

I don't have the errormessages in the kern.log, but flipping bits ...

$ uname -a
Linux elaine 4.10.0-33-generic #37-Ubuntu SMP Fri Aug 11 10:55:28 UTC 2017 
x86_64 x86_64 x86_64 GNU/Linux

Ethernet via TB16:
$ for i in 1 2 3 4; do curl -s 
http://de.releases.ubuntu.com/zesty/ubuntu-17.04-server-amd64.img -o $i.iso; 
md5sum $i.iso; done
807c26430cc62c89791917d3c40d48cb  1.iso
1971174b82abbfecbe9c05c1671e2458  2.iso
28e15ec270bdc4b2f67e1bbd0a8f0663  3.iso
f7149fe9015467e4db9093d0ca133dfe  4.iso

Ethernet via builtin:
$ for i in 1 2 3 4; do curl -s 
http://de.releases.ubuntu.com/zesty/ubuntu-17.04-server-amd64.img -o $i.iso; 
md5sum $i.iso; done
4672ce371fb3c1170a9e71bc4b2810b9  1.iso
4672ce371fb3c1170a9e71bc4b2810b9  2.iso
4672ce371fb3c1170a9e71bc4b2810b9  3.iso
4672ce371fb3c1170a9e71bc4b2810b9  4.iso

Same cable, same switch

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

Title:
  xhci_hcd: ERROR Transfer event TRB DMA ptr not part of current TD
  ep_index 2 comp_code 13

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Fix Released
Status in linux source package in Zesty:
  Fix Released
Status in linux source package in Artful:
  Fix Released
Status in linux package in Arch Linux:
  New
Status in linux package in Debian:
  New
Status in linux package in Fedora:
  Unknown

Bug description:
  [SRU Justification]

  [Impact] 
  Dell TB16 docking station has issue to use gigabit ethernet. The ethernet
  will disconnect unless it's changed to 100Mb/s.

  
  [Test Case]
  Download some big files from the web.
  User confirms the patch fixes the issue.

  [Regression Potential] 
  This patch only effects ASMEDIA's ASM1042A.
  The regression potential is low, also limited to the specific device.

  ---

  My system contains a Realtek Semiconductor Corp. RTL8153 Gigabit
  Ethernet Adapter which is on usb3 bus in my docking station (Dell
  TB16) which is attached to my laptop (Dell XPS9550) via Thunderbolt 3.

  I get usb related kernel error messages when I initiate a high speed
  transfer (by issuing wget http://cdimage.ubuntu.com/daily-live/current
  /zesty-desktop-amd64.iso) and the download fails.

  This does not happened when the Ethernet adapter is connected to a
  100Mb/s switch, but only when connected to 1000Mb/s. It also does not
  happened with slow traffic (e.g. web page browsing). This is not a new
  bug with kernel 4.10, but has been going on since at least 4.7 and
  maybe (probably?) since forever. I'm aware of several others with this
  configuration (RTL8153 on usb3 behind thunderbolt 3) that have the
  same issue. This bug is also not specific to Ubuntu; I also get it on
  Arch Linux. I've also tested and seen this bug with several different
  models of thunderbolt 3 docks.

  Here are the relevant kernel log messages:

  Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: ERROR Transfer event 
TRB DMA ptr not part of current TD ep_index 2 comp_code 13
  Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: Looking for event-dma 
0004777d9010 trb-start 000475a14fe0 trb-end 000475a14fe0 seg-start 
000475a14000 seg-end 000475a14ff0
  Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: ERROR Transfer event 
TRB DMA ptr not part of current TD ep_index 2 comp_code 13
  Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: Looking for event-dma 
0004777d9020 trb-start 000475a14fe0 trb-end 000475a14fe0 seg-start 
000475a14000 seg-end 000475a14ff0
  Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: ERROR Transfer event 
TRB DMA ptr not part of current TD ep_index 2 comp_code 13
  Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: Looking for event-dma 
0004777d9030 trb-start 000475a14fe0 trb-end 000475a14fe0 seg-start 
000475a14000 seg-end 000475a14ff0
  Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: ERROR Transfer event 
TRB DMA ptr not part of current TD ep_index 2 comp_code 13
  Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: Looking for event-dma 
0004777d9040 trb-start 000475a14fe0 trb-end 000475a14fe0 seg-start 
000475a14000 seg-end 000475a14ff0
  Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: ERROR Transfer event 
TRB DMA ptr not part of current TD ep_index 2 comp_code 13
  Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: Looking for event-dma 
0004777d9050 trb-start 000475a14fe0 trb-end 000475a14fe0 seg-start 
000475a14000 seg-end 000475a14ff0
  Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: ERROR Transfer event 
TRB DMA ptr not part of current TD ep_index 2 comp_code 13
  Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: Looking for event-dma 
0004777d9060 trb-start 000475a14fe0 trb-end 000475a14fe0 seg-start 
000475a14000 seg-end 000475a14

[Kernel-packages] [Bug 1667750] Re: xhci_hcd: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 2 comp_code 13

2017-08-29 Thread dino99

:
4.12 IS NOT FIXED
so the needed patch is not automatically added with the latest kernels

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1713691

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

Title:
  xhci_hcd: ERROR Transfer event TRB DMA ptr not part of current TD
  ep_index 2 comp_code 13

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Fix Released
Status in linux source package in Zesty:
  Fix Released
Status in linux source package in Artful:
  Fix Released
Status in linux package in Arch Linux:
  New
Status in linux package in Debian:
  New
Status in linux package in Fedora:
  Unknown

Bug description:
  [SRU Justification]

  [Impact] 
  Dell TB16 docking station has issue to use gigabit ethernet. The ethernet
  will disconnect unless it's changed to 100Mb/s.

  
  [Test Case]
  Download some big files from the web.
  User confirms the patch fixes the issue.

  [Regression Potential] 
  This patch only effects ASMEDIA's ASM1042A.
  The regression potential is low, also limited to the specific device.

  ---

  My system contains a Realtek Semiconductor Corp. RTL8153 Gigabit
  Ethernet Adapter which is on usb3 bus in my docking station (Dell
  TB16) which is attached to my laptop (Dell XPS9550) via Thunderbolt 3.

  I get usb related kernel error messages when I initiate a high speed
  transfer (by issuing wget http://cdimage.ubuntu.com/daily-live/current
  /zesty-desktop-amd64.iso) and the download fails.

  This does not happened when the Ethernet adapter is connected to a
  100Mb/s switch, but only when connected to 1000Mb/s. It also does not
  happened with slow traffic (e.g. web page browsing). This is not a new
  bug with kernel 4.10, but has been going on since at least 4.7 and
  maybe (probably?) since forever. I'm aware of several others with this
  configuration (RTL8153 on usb3 behind thunderbolt 3) that have the
  same issue. This bug is also not specific to Ubuntu; I also get it on
  Arch Linux. I've also tested and seen this bug with several different
  models of thunderbolt 3 docks.

  Here are the relevant kernel log messages:

  Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: ERROR Transfer event 
TRB DMA ptr not part of current TD ep_index 2 comp_code 13
  Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: Looking for event-dma 
0004777d9010 trb-start 000475a14fe0 trb-end 000475a14fe0 seg-start 
000475a14000 seg-end 000475a14ff0
  Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: ERROR Transfer event 
TRB DMA ptr not part of current TD ep_index 2 comp_code 13
  Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: Looking for event-dma 
0004777d9020 trb-start 000475a14fe0 trb-end 000475a14fe0 seg-start 
000475a14000 seg-end 000475a14ff0
  Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: ERROR Transfer event 
TRB DMA ptr not part of current TD ep_index 2 comp_code 13
  Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: Looking for event-dma 
0004777d9030 trb-start 000475a14fe0 trb-end 000475a14fe0 seg-start 
000475a14000 seg-end 000475a14ff0
  Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: ERROR Transfer event 
TRB DMA ptr not part of current TD ep_index 2 comp_code 13
  Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: Looking for event-dma 
0004777d9040 trb-start 000475a14fe0 trb-end 000475a14fe0 seg-start 
000475a14000 seg-end 000475a14ff0
  Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: ERROR Transfer event 
TRB DMA ptr not part of current TD ep_index 2 comp_code 13
  Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: Looking for event-dma 
0004777d9050 trb-start 000475a14fe0 trb-end 000475a14fe0 seg-start 
000475a14000 seg-end 000475a14ff0
  Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: ERROR Transfer event 
TRB DMA ptr not part of current TD ep_index 2 comp_code 13
  Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: Looking for event-dma 
0004777d9060 trb-start 000475a14fe0 trb-end 000475a14fe0 seg-start 
000475a14000 seg-end 000475a14ff0
  Feb 24 16:42:39 ubuntu kernel: xhci_hcd :0e:00.0: ERROR Transfer event 
TRB DMA ptr not part of current TD ep_index 2 comp_code 13
  Feb 24 16:42:39 ubuntu kernel: xhci_hcd :0e:00.0: Looking for event-dma 
0004777d9070 trb-start 000475a14fe0 trb-end 000475a14fe0 seg-start 
000475a14000 seg-end 000475a14ff0
  Feb 24 16:42:39 ubuntu kernel: xhci_hcd :0e:00.0: ERROR Transfer event 
TRB DMA ptr not part of current TD ep_index 2 comp_code 13
  Feb 24 16:42:39 ubuntu kernel: xhci_hcd :0e:00.0: Looking for event-dma 
0004777d9080 trb-start 000475a14fe0 trb-end 000475a14fe0 seg-start 
000

Re: [Kernel-packages] [Bug 1709257] Re: [Bug] Harrisonville: pnd2_edac always fail to load on B1 stepping Harrisonville SDP

On Tue, Aug 29, 2017 at 02:08:52AM -, quanxian wrote:
> >From comment#2, patch bfd4473b850c was not pushed into upstream.
> Currently it has been in upstream now.
> 
> Comment from upstream
> "
> The patch "bfd4473b850c i2c: i801: Restore the presence state of P2SB PCI 
> device after reading BAR" has been pushed on the 'for-next' branch of I2C 
> maintainer Wolfram Sang.
> '

@quanxian: Yes I noticed that, in fact I cherry-picked the commit from
the i2c tree when applying to artful (hadn't yet hit linux-next).

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

Title:
  [Bug] Harrisonville: pnd2_edac always fail to load on B1 stepping
  Harrisonville SDP

Status in intel:
  New
Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Artful:
  Fix Committed

Bug description:
  Description:
  During our EDAC validation on Wind River Linux 9, we found pnd2_edac manually 
load always fails on B1 stepping Harrisonville SDP.
  Error info as below:
  root@intel-x86-64:~# uname -r
  4.8.20-WR9.0.0.5_standard
  root@intel-x86-64:~# dmesg |grep -i edac
  [   11.949838] EDAC MC: Ver: 3.0.0
  [   11.954312] EDAC DEBUG: edac_mc_sysfs_init: device mc created
  [   12.060157] EDAC DEBUG: pnd2_init:
  [   12.060160] EDAC DEBUG: pnd2_probe:
  [   12.060167] EDAC DEBUG: dnv_rd_reg: Read b_cr_tolud_pci=_8000
  [   12.060169] EDAC DEBUG: dnv_rd_reg: Read 
b_cr_touud_lo_pci=_8000
  [   12.060172] EDAC DEBUG: dnv_rd_reg: Read 
b_cr_touud_hi_pci=_0004
  [   12.060228] EDAC DEBUG: dnv_rd_reg: Read 
b_cr_asym_mem_region0_mchbar=_
  [   12.060239] EDAC DEBUG: dnv_rd_reg: Read 
b_cr_asym_mem_region1_mchbar=_
  [   12.060247] EDAC DEBUG: dnv_rd_reg: Read 
b_cr_mot_out_base_mchbar=_
  [   12.060255] EDAC DEBUG: dnv_rd_reg: Read 
b_cr_mot_out_mask_mchbar=_
  [   12.078301] Modules linked in: pnd2_edac(+) edac_core x86_pkg_temp_thermal 
i2c_i801 intel_powerclamp matroxfb_base matroxfb_g450 matroxfb_accel 
matroxfb_DAC1064 g450_pll matroxfb_misc i2c_ismt i2c_smbus coretemp 
crct10dif_pclmul crct10dif_common aesni_intel aes_x86_64 glue_helper lrw 
gf128mul ablk_helper cryptd efi_pstore efivars acpi_cpufreq tpm_tis 
tpm_tis_core softdog efivarfs
  [   12.143390]  [] ? dnv_rd_reg+0x128/0x220 [pnd2_edac]
  [   12.148890]  [] dnv_rd_reg+0x128/0x220 [pnd2_edac]
  [   12.148896]  [] pnd2_init+0x22b/0x809 [pnd2_edac]
  [   12.148961] EDAC pnd2: Failed to register device with error -19.
  [   12.180813] EDAC DEBUG: pnd2_init:
  [   12.180814] EDAC DEBUG: pnd2_probe:
  [   12.180841] EDAC DEBUG: dnv_rd_reg: Read b_cr_tolud_pci=_8000
  [   12.180937] EDAC DEBUG: dnv_rd_reg: Read 
b_cr_touud_lo_pci=_8000
  [   12.180969] EDAC DEBUG: dnv_rd_reg: Read 
b_cr_touud_hi_pci=_0004
  [   12.181129] EDAC DEBUG: dnv_rd_reg: Read 
b_cr_asym_mem_region0_mchbar=_
  [   12.181299] EDAC DEBUG: dnv_rd_reg: Read 
b_cr_asym_mem_region1_mchbar=_
  [   12.181425] EDAC DEBUG: dnv_rd_reg: Read 
b_cr_mot_out_base_mchbar=_
  [   12.181671] EDAC DEBUG: dnv_rd_reg: Read 
b_cr_mot_out_mask_mchbar=_
  [   12.181810] EDAC pnd2: Failed to register device with error -19.
  root@intel-x86-64:~# dmesg -c > dmesg.clear_14.D91.log
  root@intel-x86-64:~# modprobe edac_core
  root@intel-x86-64:~# modprobe pnd2_edac
  modprobe: ERROR: could not insert 'pnd2_edac': No such device
  root@intel-x86-64:~# dmesg
  [  194.524122] EDAC DEBUG: pnd2_init:
  [  194.524126] EDAC DEBUG: pnd2_probe:
  [  194.524135] EDAC DEBUG: dnv_rd_reg: Read b_cr_tolud_pci=_8000
  [  194.524139] EDAC DEBUG: dnv_rd_reg: Read 
b_cr_touud_lo_pci=_8000
  [  194.524143] EDAC DEBUG: dnv_rd_reg: Read 
b_cr_touud_hi_pci=_0004
  [  194.524211] EDAC DEBUG: dnv_rd_reg: Read 
b_cr_asym_mem_region0_mchbar=_
  [  194.524226] EDAC DEBUG: dnv_rd_reg: Read 
b_cr_asym_mem_region1_mchbar=_
  [  194.524239] EDAC DEBUG: dnv_rd_reg: Read 
b_cr_mot_out_base_mchbar=_
  [  194.524252] EDAC DEBUG: dnv_rd_reg: Read 
b_cr_mot_out_mask_mchbar=_
  [  194.524264] EDAC pnd2: Failed to register device with error -19.
  root@intel-x86-64:~# dmidecode -t bios | grep Version
  Version: HAVLCRB1.X64.0014.D91.1704200405

  Target Kernel: 4.14
  Target Release: 18.04
  if 17.10, it will need back porting

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

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

[Kernel-packages] [Bug 1713456] Re: linux: 3.13.0-130.179 -proposed tracker

2017-08-29 Thread Kleber Sacilotto de Souza

** Summary changed:

- linux:  -proposed tracker
+ linux: 3.13.0-130.179 -proposed tracker

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

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

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

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

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

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

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

Title:
  linux: 3.13.0-130.179 -proposed tracker

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

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

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

  backports: 1713458
  derivatives:

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

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

[Kernel-packages] [Bug 1713276] Re: CVE-2017-9417 “Broadpwn”

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

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

** Changed in: linux-firmware (Ubuntu)
 Assignee: (unassigned) => Seth Forshee (sforshee)

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

Title:
  CVE-2017-9417 “Broadpwn”

Status in linux-firmware package in Ubuntu:
  Confirmed

Bug description:
  Broadcom BCM43xx Wi-Fi chips allow remote attackers to execute
  arbitrary code via unspecified vectors, aka the "Broadpwn" issue.

  Cypress (was Broadcom) have given the Raspberry Pi foundation new
  releases of the WiFi and Bluetooth firmware to fix the problem.  See
  https://github.com/raspberrypi/linux/issues/1342#issuecomment-321221748

  The pre-release files found at the above link are now included in the
  latest release of raspbian stretch.

  Would it be possible to include these new files in the linux-firmware
  package?  Please note at the moment the package is missing the file
  brcmfmac43430-sdio.txt.  Without this file the wifi does not work on
  the raspberry pi 3.

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

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

[Kernel-packages] [Bug 1712345] Re: sort ABI files with C.UTF-8 locale

2017-08-29 Thread Kleber Sacilotto de Souza

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

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

Title:
  sort ABI files with C.UTF-8 locale

Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Precise:
  New
Status in linux source package in Trusty:
  Fix Committed
Status in linux source package in Vivid:
  New
Status in linux source package in Xenial:
  Fix Committed
Status in linux source package in Zesty:
  Fix Committed
Status in linux source package in Artful:
  Incomplete

Bug description:
  Whenever we update the ABI files, the files may be sorted in a
  different order, even though their contents are the same. That happens
  because the system updating the ABI files may use a different locale
  than the one that was used previously.

  Always using the C.UTF-8 locale should fix that.

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

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

[Kernel-packages] [Bug 1679898] Re: [Hyper-V] Ubuntu VM crash during Hyper-V backup or live migration after installing kernel 4.4.0-72

2017-08-29 Thread Dave

In our environment we're running windows 2016 datacenter with Ubuntu
16.04 VMs (latest 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/1679898

Title:
  [Hyper-V] Ubuntu VM crash during Hyper-V backup or live migration
  after installing kernel 4.4.0-72

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

Bug description:
  Description:Ubuntu 14.04.5 LTS
  Release:14.04

  Hi, after installing kernel 4.4.0-67 or later I cannot backup my Ubuntu VM's 
on Hyper-V.
  Microsoft Hyper-v 2012r2 Gen2 VMs

  See Attachment for what happens is immediately after backup starts I
  get an error.

  Eventually the kernel reports it has run out of memory and the machine
  just continuously scrolls errors message related to page allocation.

  When reseting the virtual machine no logs can be found of the problem.

  kernel 4.4.0-72-generic problem still here

  DistroRelease: Ubuntu 14.04
  InstallationDate: Installed on 2016-02-20 (409 days ago)
  InstallationMedia: Ubuntu-Server 14.04.3 LTS "Trusty Tahr" - Beta amd64 
(20150805)
  Package: linux-image-4.4.0-72-generic 4.4.0-72.93~14.04.1
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 4.4.0-72.93~14.04.1-generic 4.4.49
  SourcePackage: linux-lts-xenial
  Tags:  trusty
  Uname: Linux 4.4.0-72-generic x86_64
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Apr  5 12:05 seq
   crw-rw 1 root audio 116, 33 Apr  5 12:05 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.14.1-0ubuntu3.23
  Architecture: amd64
  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
  HibernationDevice: RESUME=/dev/mapper/ubuntu--vg-swap_1
  InstallationDate: Installed on 2016-02-20 (409 days ago)
  InstallationMedia: Ubuntu-Server 14.04.3 LTS "Trusty Tahr" - Beta amd64 
(20150805)
  IwConfig:
   lono wireless extensions.
   
   eth1  no wireless extensions.
   
   eth0  no wireless extensions.
  Lspci:
   
  Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize 
libusb: -99
  MachineType: Microsoft Corporation Virtual Machine
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=C
   SHELL=/bin/bash
  ProcFB: 0 hyperv_fb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-72-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro
  ProcVersionSignature: Ubuntu 4.4.0-72.93~14.04.1-generic 4.4.49
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-72-generic N/A
   linux-backports-modules-4.4.0-72-generic  N/A
   linux-firmware1.127.23
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  trusty
  Uname: Linux 4.4.0-72-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 11/26/2012
  dmi.bios.vendor: Microsoft Corporation
  dmi.bios.version: Hyper-V UEFI Release v1.0
  dmi.board.asset.tag: None
  dmi.board.name: Virtual Machine
  dmi.board.vendor: Microsoft Corporation
  dmi.board.version: Hyper-V UEFI Release v1.0
  dmi.chassis.asset.tag: 5894-4187-8369-8212-0547-2747-15
  dmi.chassis.type: 3
  dmi.chassis.vendor: Microsoft Corporation
  dmi.chassis.version: Hyper-V UEFI Release v1.0
  dmi.modalias: 
dmi:bvnMicrosoftCorporation:bvrHyper-VUEFIReleasev1.0:bd11/26/2012:svnMicrosoftCorporation:pnVirtualMachine:pvrHyper-VUEFIReleasev1.0:rvnMicrosoftCorporation:rnVirtualMachine:rvrHyper-VUEFIReleasev1.0:cvnMicrosoftCorporation:ct3:cvrHyper-VUEFIReleasev1.0:
  dmi.product.name: Virtual Machine
  dmi.product.version: Hyper-V UEFI Release v1.0
  dmi.sys.vendor: Microsoft Corporation
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Apr 10 10:33 seq
   crw-rw 1 root audio 116, 33 Apr 10 10:33 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.14.1-0ubuntu3.23
  Architecture: amd64
  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
  HibernationDevice: RESUME=/dev/mapper/ubuntu--vg-swap_1
  InstallationDate: Installed on 2016-02-20 (414 days ago)
  InstallationMedia: Ubuntu-Server 14.04.3 LTS "Trusty Tahr" - Beta amd64 
(20150805)
  IwConfig:
   lono wireless extensions.
   
   eth1  no wireless extensions.
   
   eth0  no wireless extensions.
  Lspci:
   
  Lsusb: Error: command [

[Kernel-packages] [Bug 1713467] Re: linux-aws: 4.4.0-1033.42 -proposed tracker

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
+ boot-testing-requested: true
  kernel-stable-master-bug: 1713462
  phase: Uploaded

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

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

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

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

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

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

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

[Kernel-packages] [Bug 1713470] Re: linux: 4.10.0-34.38 -proposed tracker

2017-08-29 Thread Łukasz Zemczak

** Changed in: kernel-sru-workflow/promote-to-proposed
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Łukasz 
Zemczak (sil2100)

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

Title:
  linux: 4.10.0-34.38 -proposed tracker

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

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

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

  backports: 1713471,1713472
  derivatives: 1713473
  kernel-stable-phase-changed:Monday, 28. August 2017 19:32 UTC
  kernel-stable-phase:Uploaded

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

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

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

[Kernel-packages] [Bug 1713535] Re: No /dev/watchdog on NUC6CAYS devices with iTCO_wdt

apport information

** Tags added: apport-collected xenial

** Description changed:

  It looks like iTCO_wdt won't properly setup a /dev/watchdog device on
  Intel recent Celeron NUCs (NUC6CAYS).
  
  ```
  # uname -a
  Linux player-ef15 4.11.0-14-generic #20~16.04.1-Ubuntu SMP Wed Aug 9 09:06:22 
UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
  # lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 16.04.3 LTS
  Release:  16.04
  Codename: xenial
  ```
  
  Modules are properly loaded (but looks like it is not used)
  
  ```
  # lsmod | grep -e dog -e wdt
  iTCO_wdt   16384  0
  iTCO_vendor_support16384  1 iTCO_wdt
  ```
  
  No device found in kernel.log:
  ```
  Aug 28 18:49:56 player-ef15 kernel: [   14.192689] iTCO_vendor_support: 
vendor-support=0
  Aug 28 18:49:56 player-ef15 kernel: [   14.198585] iTCO_wdt: Intel TCO 
WatchDog Timer Driver v1.11
  ```
  
  No device found by the service:
  
  ```
  # service watchdog status
  ● watchdog.service - watchdog daemon
     Loaded: loaded (/lib/systemd/system/watchdog.service; enabled; vendor 
preset: enabled)
     Active: active (running) since lun. 2017-08-28 18:49:56 CEST; 17s ago
    Process: 2763 ExecStart=/bin/sh -c [ $run_watchdog != 1 ] || exec 
/usr/sbin/watchdog $watchdog_options (code=exited, status=0/SUCCESS)
    Process: 2758 ExecStartPre=/bin/sh -c [ -z "${watchdog_module}" ] || [ 
"${watchdog_module}" = "none" ] || /sbin/modprobe $watchdog_module 
(code=exited, status=0/SUCCESS)
   Main PID: 2768 (watchdog)
  Tasks: 1
     Memory: 732.0K
    CPU: 13ms
     CGroup: /system.slice/watchdog.service
     └─2768 /usr/sbin/watchdog
  
  août 28 18:49:56 player-ef15 systemd[1]: Started watchdog daemon.
  août 28 18:49:56 player-ef15 watchdog[2768]: starting daemon (5.14):
  août 28 18:49:56 player-ef15 watchdog[2768]: int=1s realtime=yes sync=no 
soft=no mla=0 mem=0
  août 28 18:49:56 player-ef15 watchdog[2768]: ping: no machine to check
  août 28 18:49:56 player-ef15 watchdog[2768]: file: no file to check
  août 28 18:49:56 player-ef15 watchdog[2768]: pidfile: no server process to 
check
  août 28 18:49:56 player-ef15 watchdog[2768]: interface: no interface to check
  août 28 18:49:56 player-ef15 watchdog[2768]: temperature: no sensors to check
  août 28 18:49:56 player-ef15 watchdog[2768]: test=none(0) repair=none(0) 
alive=/dev/watchdog heartbeat=none to=root no_act=no force=no
  août 28 18:49:56 player-ef15 watchdog[2768]: cannot open /dev/watchdog (errno 
= 2 = 'No such file or directory')
  ```
+ --- 
+ ApportVersion: 2.20.1-0ubuntu2.10
+ Architecture: amd64
+ AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D10p', 
'/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', 
'/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', 
'/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
+ DistroRelease: Ubuntu 16.04
+ HibernationDevice: RESUME=UUID=912a4deb-6713-4f38-8c3a-8280e9c732cf
+ InstallationDate: Installed on 2017-08-28 (1 days ago)
+ InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
+ Lsusb:
+  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
+  Bus 001 Device 004: ID 8087:0aa7 Intel Corp. 
+  Bus 001 Device 003: ID 046d:c05a Logitech, Inc. M90/M100 Optical Mouse
+  Bus 001 Device 002: ID 04ca:0027 Lite-On Technology Corp. 
+  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
+ Package: linux (not installed)
+ ProcFB: 0 inteldrmfb
+ ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.11.0-14-generic 
root=UUID=25140007-3f56-4beb-8070-e96eabdb6319 ro quiet splash net.ifnames=0 
vt.handoff=7
+ ProcVersionSignature: Ubuntu 4.11.0-14.20~16.04.1-generic 4.11.12
+ 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.11.0-14-generic N/A
+  linux-backports-modules-4.11.0-14-generic  N/A
+  linux-firmware 1.157.11
+ Tags:  xenial
+ Uname: Linux 4.11.0-14-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm audio cdrom dialout dip lpadmin mongodb plugdev pulse-access 
sambashare sudo video www-data
+ _MarkForUpload: True
+ dmi.bios.date: 11/24/2016
+ dmi.bios.vendor: Intel Corp.
+ dmi.bios.version: AYAPLCEL.86A.0029.2016.1124.1625
+ dmi.board.name: NUC6CAYB
+ dmi.board.vendor: Intel Corporation
+ dmi.board.version: J23203-402
+ dmi.chassis.type: 3
+ dmi.modalias: 
dmi:bvnIntelCorp.:bvrAYAPLCEL.86A.0029.2016.1124.1625:bd11/24/2016:svn:pn:pvr:rvnIntelCorporation:rnNUC6CAYB:rvrJ23203-402:cvn:ct3:cvr:

** Attachment added: "AlsaInfo.txt"
   
https://bugs.launchpad.net/bugs/1713535/+attachment/4940867/+files/AlsaInfo.txt

-- 
You received this bug notification because you are a mem

[Kernel-packages] [Bug 1713535] CurrentDmesg.txt

apport information

** Attachment added: "CurrentDmesg.txt"
   
https://bugs.launchpad.net/bugs/1713535/+attachment/4940869/+files/CurrentDmesg.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/1713535

Title:
  No /dev/watchdog on NUC6CAYS devices with iTCO_wdt

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  It looks like iTCO_wdt won't properly setup a /dev/watchdog device on
  Intel recent Celeron NUCs (NUC6CAYS).

  ```
  # uname -a
  Linux player-ef15 4.11.0-14-generic #20~16.04.1-Ubuntu SMP Wed Aug 9 09:06:22 
UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
  # lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 16.04.3 LTS
  Release:  16.04
  Codename: xenial
  ```

  Modules are properly loaded (but looks like it is not used)

  ```
  # lsmod | grep -e dog -e wdt
  iTCO_wdt   16384  0
  iTCO_vendor_support16384  1 iTCO_wdt
  ```

  No device found in kernel.log:
  ```
  Aug 28 18:49:56 player-ef15 kernel: [   14.192689] iTCO_vendor_support: 
vendor-support=0
  Aug 28 18:49:56 player-ef15 kernel: [   14.198585] iTCO_wdt: Intel TCO 
WatchDog Timer Driver v1.11
  ```

  No device found by the service:

  ```
  # service watchdog status
  ● watchdog.service - watchdog daemon
     Loaded: loaded (/lib/systemd/system/watchdog.service; enabled; vendor 
preset: enabled)
     Active: active (running) since lun. 2017-08-28 18:49:56 CEST; 17s ago
    Process: 2763 ExecStart=/bin/sh -c [ $run_watchdog != 1 ] || exec 
/usr/sbin/watchdog $watchdog_options (code=exited, status=0/SUCCESS)
    Process: 2758 ExecStartPre=/bin/sh -c [ -z "${watchdog_module}" ] || [ 
"${watchdog_module}" = "none" ] || /sbin/modprobe $watchdog_module 
(code=exited, status=0/SUCCESS)
   Main PID: 2768 (watchdog)
  Tasks: 1
     Memory: 732.0K
    CPU: 13ms
     CGroup: /system.slice/watchdog.service
     └─2768 /usr/sbin/watchdog

  août 28 18:49:56 player-ef15 systemd[1]: Started watchdog daemon.
  août 28 18:49:56 player-ef15 watchdog[2768]: starting daemon (5.14):
  août 28 18:49:56 player-ef15 watchdog[2768]: int=1s realtime=yes sync=no 
soft=no mla=0 mem=0
  août 28 18:49:56 player-ef15 watchdog[2768]: ping: no machine to check
  août 28 18:49:56 player-ef15 watchdog[2768]: file: no file to check
  août 28 18:49:56 player-ef15 watchdog[2768]: pidfile: no server process to 
check
  août 28 18:49:56 player-ef15 watchdog[2768]: interface: no interface to check
  août 28 18:49:56 player-ef15 watchdog[2768]: temperature: no sensors to check
  août 28 18:49:56 player-ef15 watchdog[2768]: test=none(0) repair=none(0) 
alive=/dev/watchdog heartbeat=none to=root no_act=no force=no
  août 28 18:49:56 player-ef15 watchdog[2768]: cannot open /dev/watchdog (errno 
= 2 = 'No such file or directory')
  ```
  --- 
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D10p', 
'/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', 
'/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', 
'/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=912a4deb-6713-4f38-8c3a-8280e9c732cf
  InstallationDate: Installed on 2017-08-28 (1 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0aa7 Intel Corp. 
   Bus 001 Device 003: ID 046d:c05a Logitech, Inc. M90/M100 Optical Mouse
   Bus 001 Device 002: ID 04ca:0027 Lite-On Technology Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.11.0-14-generic 
root=UUID=25140007-3f56-4beb-8070-e96eabdb6319 ro quiet splash net.ifnames=0 
vt.handoff=7
  ProcVersionSignature: Ubuntu 4.11.0-14.20~16.04.1-generic 4.11.12
  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.11.0-14-generic N/A
   linux-backports-modules-4.11.0-14-generic  N/A
   linux-firmware 1.157.11
  Tags:  xenial
  Uname: Linux 4.11.0-14-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dialout dip lpadmin mongodb plugdev pulse-access 
sambashare sudo video www-data
  _MarkForUpload: True
  dmi.bios.date: 11/24/2016
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: AYAPLCEL.86A.0029.2016.1124.1625
  dmi.board.name: NUC6CAYB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: J23203-402
  dmi.chassis.ty

[Kernel-packages] [Bug 1713535] CRDA.txt

apport information

** Attachment added: "CRDA.txt"
   https://bugs.launchpad.net/bugs/1713535/+attachment/4940868/+files/CRDA.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/1713535

Title:
  No /dev/watchdog on NUC6CAYS devices with iTCO_wdt

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  It looks like iTCO_wdt won't properly setup a /dev/watchdog device on
  Intel recent Celeron NUCs (NUC6CAYS).

  ```
  # uname -a
  Linux player-ef15 4.11.0-14-generic #20~16.04.1-Ubuntu SMP Wed Aug 9 09:06:22 
UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
  # lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 16.04.3 LTS
  Release:  16.04
  Codename: xenial
  ```

  Modules are properly loaded (but looks like it is not used)

  ```
  # lsmod | grep -e dog -e wdt
  iTCO_wdt   16384  0
  iTCO_vendor_support16384  1 iTCO_wdt
  ```

  No device found in kernel.log:
  ```
  Aug 28 18:49:56 player-ef15 kernel: [   14.192689] iTCO_vendor_support: 
vendor-support=0
  Aug 28 18:49:56 player-ef15 kernel: [   14.198585] iTCO_wdt: Intel TCO 
WatchDog Timer Driver v1.11
  ```

  No device found by the service:

  ```
  # service watchdog status
  ● watchdog.service - watchdog daemon
     Loaded: loaded (/lib/systemd/system/watchdog.service; enabled; vendor 
preset: enabled)
     Active: active (running) since lun. 2017-08-28 18:49:56 CEST; 17s ago
    Process: 2763 ExecStart=/bin/sh -c [ $run_watchdog != 1 ] || exec 
/usr/sbin/watchdog $watchdog_options (code=exited, status=0/SUCCESS)
    Process: 2758 ExecStartPre=/bin/sh -c [ -z "${watchdog_module}" ] || [ 
"${watchdog_module}" = "none" ] || /sbin/modprobe $watchdog_module 
(code=exited, status=0/SUCCESS)
   Main PID: 2768 (watchdog)
  Tasks: 1
     Memory: 732.0K
    CPU: 13ms
     CGroup: /system.slice/watchdog.service
     └─2768 /usr/sbin/watchdog

  août 28 18:49:56 player-ef15 systemd[1]: Started watchdog daemon.
  août 28 18:49:56 player-ef15 watchdog[2768]: starting daemon (5.14):
  août 28 18:49:56 player-ef15 watchdog[2768]: int=1s realtime=yes sync=no 
soft=no mla=0 mem=0
  août 28 18:49:56 player-ef15 watchdog[2768]: ping: no machine to check
  août 28 18:49:56 player-ef15 watchdog[2768]: file: no file to check
  août 28 18:49:56 player-ef15 watchdog[2768]: pidfile: no server process to 
check
  août 28 18:49:56 player-ef15 watchdog[2768]: interface: no interface to check
  août 28 18:49:56 player-ef15 watchdog[2768]: temperature: no sensors to check
  août 28 18:49:56 player-ef15 watchdog[2768]: test=none(0) repair=none(0) 
alive=/dev/watchdog heartbeat=none to=root no_act=no force=no
  août 28 18:49:56 player-ef15 watchdog[2768]: cannot open /dev/watchdog (errno 
= 2 = 'No such file or directory')
  ```
  --- 
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D10p', 
'/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', 
'/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', 
'/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=912a4deb-6713-4f38-8c3a-8280e9c732cf
  InstallationDate: Installed on 2017-08-28 (1 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0aa7 Intel Corp. 
   Bus 001 Device 003: ID 046d:c05a Logitech, Inc. M90/M100 Optical Mouse
   Bus 001 Device 002: ID 04ca:0027 Lite-On Technology Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.11.0-14-generic 
root=UUID=25140007-3f56-4beb-8070-e96eabdb6319 ro quiet splash net.ifnames=0 
vt.handoff=7
  ProcVersionSignature: Ubuntu 4.11.0-14.20~16.04.1-generic 4.11.12
  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.11.0-14-generic N/A
   linux-backports-modules-4.11.0-14-generic  N/A
   linux-firmware 1.157.11
  Tags:  xenial
  Uname: Linux 4.11.0-14-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dialout dip lpadmin mongodb plugdev pulse-access 
sambashare sudo video www-data
  _MarkForUpload: True
  dmi.bios.date: 11/24/2016
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: AYAPLCEL.86A.0029.2016.1124.1625
  dmi.board.name: NUC6CAYB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: J23203-402
  dmi.chassis.type: 3
  dmi.modal

[Kernel-packages] [Bug 1713535] Lspci.txt

apport information

** Attachment added: "Lspci.txt"
   https://bugs.launchpad.net/bugs/1713535/+attachment/4940872/+files/Lspci.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/1713535

Title:
  No /dev/watchdog on NUC6CAYS devices with iTCO_wdt

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  It looks like iTCO_wdt won't properly setup a /dev/watchdog device on
  Intel recent Celeron NUCs (NUC6CAYS).

  ```
  # uname -a
  Linux player-ef15 4.11.0-14-generic #20~16.04.1-Ubuntu SMP Wed Aug 9 09:06:22 
UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
  # lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 16.04.3 LTS
  Release:  16.04
  Codename: xenial
  ```

  Modules are properly loaded (but looks like it is not used)

  ```
  # lsmod | grep -e dog -e wdt
  iTCO_wdt   16384  0
  iTCO_vendor_support16384  1 iTCO_wdt
  ```

  No device found in kernel.log:
  ```
  Aug 28 18:49:56 player-ef15 kernel: [   14.192689] iTCO_vendor_support: 
vendor-support=0
  Aug 28 18:49:56 player-ef15 kernel: [   14.198585] iTCO_wdt: Intel TCO 
WatchDog Timer Driver v1.11
  ```

  No device found by the service:

  ```
  # service watchdog status
  ● watchdog.service - watchdog daemon
     Loaded: loaded (/lib/systemd/system/watchdog.service; enabled; vendor 
preset: enabled)
     Active: active (running) since lun. 2017-08-28 18:49:56 CEST; 17s ago
    Process: 2763 ExecStart=/bin/sh -c [ $run_watchdog != 1 ] || exec 
/usr/sbin/watchdog $watchdog_options (code=exited, status=0/SUCCESS)
    Process: 2758 ExecStartPre=/bin/sh -c [ -z "${watchdog_module}" ] || [ 
"${watchdog_module}" = "none" ] || /sbin/modprobe $watchdog_module 
(code=exited, status=0/SUCCESS)
   Main PID: 2768 (watchdog)
  Tasks: 1
     Memory: 732.0K
    CPU: 13ms
     CGroup: /system.slice/watchdog.service
     └─2768 /usr/sbin/watchdog

  août 28 18:49:56 player-ef15 systemd[1]: Started watchdog daemon.
  août 28 18:49:56 player-ef15 watchdog[2768]: starting daemon (5.14):
  août 28 18:49:56 player-ef15 watchdog[2768]: int=1s realtime=yes sync=no 
soft=no mla=0 mem=0
  août 28 18:49:56 player-ef15 watchdog[2768]: ping: no machine to check
  août 28 18:49:56 player-ef15 watchdog[2768]: file: no file to check
  août 28 18:49:56 player-ef15 watchdog[2768]: pidfile: no server process to 
check
  août 28 18:49:56 player-ef15 watchdog[2768]: interface: no interface to check
  août 28 18:49:56 player-ef15 watchdog[2768]: temperature: no sensors to check
  août 28 18:49:56 player-ef15 watchdog[2768]: test=none(0) repair=none(0) 
alive=/dev/watchdog heartbeat=none to=root no_act=no force=no
  août 28 18:49:56 player-ef15 watchdog[2768]: cannot open /dev/watchdog (errno 
= 2 = 'No such file or directory')
  ```
  --- 
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D10p', 
'/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', 
'/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', 
'/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=912a4deb-6713-4f38-8c3a-8280e9c732cf
  InstallationDate: Installed on 2017-08-28 (1 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0aa7 Intel Corp. 
   Bus 001 Device 003: ID 046d:c05a Logitech, Inc. M90/M100 Optical Mouse
   Bus 001 Device 002: ID 04ca:0027 Lite-On Technology Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.11.0-14-generic 
root=UUID=25140007-3f56-4beb-8070-e96eabdb6319 ro quiet splash net.ifnames=0 
vt.handoff=7
  ProcVersionSignature: Ubuntu 4.11.0-14.20~16.04.1-generic 4.11.12
  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.11.0-14-generic N/A
   linux-backports-modules-4.11.0-14-generic  N/A
   linux-firmware 1.157.11
  Tags:  xenial
  Uname: Linux 4.11.0-14-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dialout dip lpadmin mongodb plugdev pulse-access 
sambashare sudo video www-data
  _MarkForUpload: True
  dmi.bios.date: 11/24/2016
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: AYAPLCEL.86A.0029.2016.1124.1625
  dmi.board.name: NUC6CAYB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: J23203-402
  dmi.chassis.type: 3
  dmi.mod

[Kernel-packages] [Bug 1713535] IwConfig.txt

apport information

** Attachment added: "IwConfig.txt"
   
https://bugs.launchpad.net/bugs/1713535/+attachment/4940870/+files/IwConfig.txt

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

Title:
  No /dev/watchdog on NUC6CAYS devices with iTCO_wdt

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  It looks like iTCO_wdt won't properly setup a /dev/watchdog device on
  Intel recent Celeron NUCs (NUC6CAYS).

  ```
  # uname -a
  Linux player-ef15 4.11.0-14-generic #20~16.04.1-Ubuntu SMP Wed Aug 9 09:06:22 
UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
  # lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 16.04.3 LTS
  Release:  16.04
  Codename: xenial
  ```

  Modules are properly loaded (but looks like it is not used)

  ```
  # lsmod | grep -e dog -e wdt
  iTCO_wdt   16384  0
  iTCO_vendor_support16384  1 iTCO_wdt
  ```

  No device found in kernel.log:
  ```
  Aug 28 18:49:56 player-ef15 kernel: [   14.192689] iTCO_vendor_support: 
vendor-support=0
  Aug 28 18:49:56 player-ef15 kernel: [   14.198585] iTCO_wdt: Intel TCO 
WatchDog Timer Driver v1.11
  ```

  No device found by the service:

  ```
  # service watchdog status
  ● watchdog.service - watchdog daemon
     Loaded: loaded (/lib/systemd/system/watchdog.service; enabled; vendor 
preset: enabled)
     Active: active (running) since lun. 2017-08-28 18:49:56 CEST; 17s ago
    Process: 2763 ExecStart=/bin/sh -c [ $run_watchdog != 1 ] || exec 
/usr/sbin/watchdog $watchdog_options (code=exited, status=0/SUCCESS)
    Process: 2758 ExecStartPre=/bin/sh -c [ -z "${watchdog_module}" ] || [ 
"${watchdog_module}" = "none" ] || /sbin/modprobe $watchdog_module 
(code=exited, status=0/SUCCESS)
   Main PID: 2768 (watchdog)
  Tasks: 1
     Memory: 732.0K
    CPU: 13ms
     CGroup: /system.slice/watchdog.service
     └─2768 /usr/sbin/watchdog

  août 28 18:49:56 player-ef15 systemd[1]: Started watchdog daemon.
  août 28 18:49:56 player-ef15 watchdog[2768]: starting daemon (5.14):
  août 28 18:49:56 player-ef15 watchdog[2768]: int=1s realtime=yes sync=no 
soft=no mla=0 mem=0
  août 28 18:49:56 player-ef15 watchdog[2768]: ping: no machine to check
  août 28 18:49:56 player-ef15 watchdog[2768]: file: no file to check
  août 28 18:49:56 player-ef15 watchdog[2768]: pidfile: no server process to 
check
  août 28 18:49:56 player-ef15 watchdog[2768]: interface: no interface to check
  août 28 18:49:56 player-ef15 watchdog[2768]: temperature: no sensors to check
  août 28 18:49:56 player-ef15 watchdog[2768]: test=none(0) repair=none(0) 
alive=/dev/watchdog heartbeat=none to=root no_act=no force=no
  août 28 18:49:56 player-ef15 watchdog[2768]: cannot open /dev/watchdog (errno 
= 2 = 'No such file or directory')
  ```
  --- 
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D10p', 
'/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', 
'/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', 
'/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=912a4deb-6713-4f38-8c3a-8280e9c732cf
  InstallationDate: Installed on 2017-08-28 (1 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0aa7 Intel Corp. 
   Bus 001 Device 003: ID 046d:c05a Logitech, Inc. M90/M100 Optical Mouse
   Bus 001 Device 002: ID 04ca:0027 Lite-On Technology Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.11.0-14-generic 
root=UUID=25140007-3f56-4beb-8070-e96eabdb6319 ro quiet splash net.ifnames=0 
vt.handoff=7
  ProcVersionSignature: Ubuntu 4.11.0-14.20~16.04.1-generic 4.11.12
  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.11.0-14-generic N/A
   linux-backports-modules-4.11.0-14-generic  N/A
   linux-firmware 1.157.11
  Tags:  xenial
  Uname: Linux 4.11.0-14-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dialout dip lpadmin mongodb plugdev pulse-access 
sambashare sudo video www-data
  _MarkForUpload: True
  dmi.bios.date: 11/24/2016
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: AYAPLCEL.86A.0029.2016.1124.1625
  dmi.board.name: NUC6CAYB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: J23203-402
  dmi.chassis.type: 3

[Kernel-packages] [Bug 1713535] JournalErrors.txt

apport information

** Attachment added: "JournalErrors.txt"
   
https://bugs.launchpad.net/bugs/1713535/+attachment/4940871/+files/JournalErrors.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/1713535

Title:
  No /dev/watchdog on NUC6CAYS devices with iTCO_wdt

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  It looks like iTCO_wdt won't properly setup a /dev/watchdog device on
  Intel recent Celeron NUCs (NUC6CAYS).

  ```
  # uname -a
  Linux player-ef15 4.11.0-14-generic #20~16.04.1-Ubuntu SMP Wed Aug 9 09:06:22 
UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
  # lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 16.04.3 LTS
  Release:  16.04
  Codename: xenial
  ```

  Modules are properly loaded (but looks like it is not used)

  ```
  # lsmod | grep -e dog -e wdt
  iTCO_wdt   16384  0
  iTCO_vendor_support16384  1 iTCO_wdt
  ```

  No device found in kernel.log:
  ```
  Aug 28 18:49:56 player-ef15 kernel: [   14.192689] iTCO_vendor_support: 
vendor-support=0
  Aug 28 18:49:56 player-ef15 kernel: [   14.198585] iTCO_wdt: Intel TCO 
WatchDog Timer Driver v1.11
  ```

  No device found by the service:

  ```
  # service watchdog status
  ● watchdog.service - watchdog daemon
     Loaded: loaded (/lib/systemd/system/watchdog.service; enabled; vendor 
preset: enabled)
     Active: active (running) since lun. 2017-08-28 18:49:56 CEST; 17s ago
    Process: 2763 ExecStart=/bin/sh -c [ $run_watchdog != 1 ] || exec 
/usr/sbin/watchdog $watchdog_options (code=exited, status=0/SUCCESS)
    Process: 2758 ExecStartPre=/bin/sh -c [ -z "${watchdog_module}" ] || [ 
"${watchdog_module}" = "none" ] || /sbin/modprobe $watchdog_module 
(code=exited, status=0/SUCCESS)
   Main PID: 2768 (watchdog)
  Tasks: 1
     Memory: 732.0K
    CPU: 13ms
     CGroup: /system.slice/watchdog.service
     └─2768 /usr/sbin/watchdog

  août 28 18:49:56 player-ef15 systemd[1]: Started watchdog daemon.
  août 28 18:49:56 player-ef15 watchdog[2768]: starting daemon (5.14):
  août 28 18:49:56 player-ef15 watchdog[2768]: int=1s realtime=yes sync=no 
soft=no mla=0 mem=0
  août 28 18:49:56 player-ef15 watchdog[2768]: ping: no machine to check
  août 28 18:49:56 player-ef15 watchdog[2768]: file: no file to check
  août 28 18:49:56 player-ef15 watchdog[2768]: pidfile: no server process to 
check
  août 28 18:49:56 player-ef15 watchdog[2768]: interface: no interface to check
  août 28 18:49:56 player-ef15 watchdog[2768]: temperature: no sensors to check
  août 28 18:49:56 player-ef15 watchdog[2768]: test=none(0) repair=none(0) 
alive=/dev/watchdog heartbeat=none to=root no_act=no force=no
  août 28 18:49:56 player-ef15 watchdog[2768]: cannot open /dev/watchdog (errno 
= 2 = 'No such file or directory')
  ```
  --- 
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D10p', 
'/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', 
'/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', 
'/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=912a4deb-6713-4f38-8c3a-8280e9c732cf
  InstallationDate: Installed on 2017-08-28 (1 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0aa7 Intel Corp. 
   Bus 001 Device 003: ID 046d:c05a Logitech, Inc. M90/M100 Optical Mouse
   Bus 001 Device 002: ID 04ca:0027 Lite-On Technology Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.11.0-14-generic 
root=UUID=25140007-3f56-4beb-8070-e96eabdb6319 ro quiet splash net.ifnames=0 
vt.handoff=7
  ProcVersionSignature: Ubuntu 4.11.0-14.20~16.04.1-generic 4.11.12
  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.11.0-14-generic N/A
   linux-backports-modules-4.11.0-14-generic  N/A
   linux-firmware 1.157.11
  Tags:  xenial
  Uname: Linux 4.11.0-14-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dialout dip lpadmin mongodb plugdev pulse-access 
sambashare sudo video www-data
  _MarkForUpload: True
  dmi.bios.date: 11/24/2016
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: AYAPLCEL.86A.0029.2016.1124.1625
  dmi.board.name: NUC6CAYB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: J23203-402
  dmi.chassis.

[Kernel-packages] [Bug 1713535] ProcCpuinfo.txt

apport information

** Attachment added: "ProcCpuinfo.txt"
   
https://bugs.launchpad.net/bugs/1713535/+attachment/4940873/+files/ProcCpuinfo.txt

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

Title:
  No /dev/watchdog on NUC6CAYS devices with iTCO_wdt

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  It looks like iTCO_wdt won't properly setup a /dev/watchdog device on
  Intel recent Celeron NUCs (NUC6CAYS).

  ```
  # uname -a
  Linux player-ef15 4.11.0-14-generic #20~16.04.1-Ubuntu SMP Wed Aug 9 09:06:22 
UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
  # lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 16.04.3 LTS
  Release:  16.04
  Codename: xenial
  ```

  Modules are properly loaded (but looks like it is not used)

  ```
  # lsmod | grep -e dog -e wdt
  iTCO_wdt   16384  0
  iTCO_vendor_support16384  1 iTCO_wdt
  ```

  No device found in kernel.log:
  ```
  Aug 28 18:49:56 player-ef15 kernel: [   14.192689] iTCO_vendor_support: 
vendor-support=0
  Aug 28 18:49:56 player-ef15 kernel: [   14.198585] iTCO_wdt: Intel TCO 
WatchDog Timer Driver v1.11
  ```

  No device found by the service:

  ```
  # service watchdog status
  ● watchdog.service - watchdog daemon
     Loaded: loaded (/lib/systemd/system/watchdog.service; enabled; vendor 
preset: enabled)
     Active: active (running) since lun. 2017-08-28 18:49:56 CEST; 17s ago
    Process: 2763 ExecStart=/bin/sh -c [ $run_watchdog != 1 ] || exec 
/usr/sbin/watchdog $watchdog_options (code=exited, status=0/SUCCESS)
    Process: 2758 ExecStartPre=/bin/sh -c [ -z "${watchdog_module}" ] || [ 
"${watchdog_module}" = "none" ] || /sbin/modprobe $watchdog_module 
(code=exited, status=0/SUCCESS)
   Main PID: 2768 (watchdog)
  Tasks: 1
     Memory: 732.0K
    CPU: 13ms
     CGroup: /system.slice/watchdog.service
     └─2768 /usr/sbin/watchdog

  août 28 18:49:56 player-ef15 systemd[1]: Started watchdog daemon.
  août 28 18:49:56 player-ef15 watchdog[2768]: starting daemon (5.14):
  août 28 18:49:56 player-ef15 watchdog[2768]: int=1s realtime=yes sync=no 
soft=no mla=0 mem=0
  août 28 18:49:56 player-ef15 watchdog[2768]: ping: no machine to check
  août 28 18:49:56 player-ef15 watchdog[2768]: file: no file to check
  août 28 18:49:56 player-ef15 watchdog[2768]: pidfile: no server process to 
check
  août 28 18:49:56 player-ef15 watchdog[2768]: interface: no interface to check
  août 28 18:49:56 player-ef15 watchdog[2768]: temperature: no sensors to check
  août 28 18:49:56 player-ef15 watchdog[2768]: test=none(0) repair=none(0) 
alive=/dev/watchdog heartbeat=none to=root no_act=no force=no
  août 28 18:49:56 player-ef15 watchdog[2768]: cannot open /dev/watchdog (errno 
= 2 = 'No such file or directory')
  ```
  --- 
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D10p', 
'/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', 
'/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', 
'/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=912a4deb-6713-4f38-8c3a-8280e9c732cf
  InstallationDate: Installed on 2017-08-28 (1 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0aa7 Intel Corp. 
   Bus 001 Device 003: ID 046d:c05a Logitech, Inc. M90/M100 Optical Mouse
   Bus 001 Device 002: ID 04ca:0027 Lite-On Technology Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.11.0-14-generic 
root=UUID=25140007-3f56-4beb-8070-e96eabdb6319 ro quiet splash net.ifnames=0 
vt.handoff=7
  ProcVersionSignature: Ubuntu 4.11.0-14.20~16.04.1-generic 4.11.12
  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.11.0-14-generic N/A
   linux-backports-modules-4.11.0-14-generic  N/A
   linux-firmware 1.157.11
  Tags:  xenial
  Uname: Linux 4.11.0-14-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dialout dip lpadmin mongodb plugdev pulse-access 
sambashare sudo video www-data
  _MarkForUpload: True
  dmi.bios.date: 11/24/2016
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: AYAPLCEL.86A.0029.2016.1124.1625
  dmi.board.name: NUC6CAYB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: J23203-402
  dmi.chassis.type

[Kernel-packages] [Bug 1713535] ProcCpuinfoMinimal.txt

apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1713535/+attachment/4940874/+files/ProcCpuinfoMinimal.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/1713535

Title:
  No /dev/watchdog on NUC6CAYS devices with iTCO_wdt

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  It looks like iTCO_wdt won't properly setup a /dev/watchdog device on
  Intel recent Celeron NUCs (NUC6CAYS).

  ```
  # uname -a
  Linux player-ef15 4.11.0-14-generic #20~16.04.1-Ubuntu SMP Wed Aug 9 09:06:22 
UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
  # lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 16.04.3 LTS
  Release:  16.04
  Codename: xenial
  ```

  Modules are properly loaded (but looks like it is not used)

  ```
  # lsmod | grep -e dog -e wdt
  iTCO_wdt   16384  0
  iTCO_vendor_support16384  1 iTCO_wdt
  ```

  No device found in kernel.log:
  ```
  Aug 28 18:49:56 player-ef15 kernel: [   14.192689] iTCO_vendor_support: 
vendor-support=0
  Aug 28 18:49:56 player-ef15 kernel: [   14.198585] iTCO_wdt: Intel TCO 
WatchDog Timer Driver v1.11
  ```

  No device found by the service:

  ```
  # service watchdog status
  ● watchdog.service - watchdog daemon
     Loaded: loaded (/lib/systemd/system/watchdog.service; enabled; vendor 
preset: enabled)
     Active: active (running) since lun. 2017-08-28 18:49:56 CEST; 17s ago
    Process: 2763 ExecStart=/bin/sh -c [ $run_watchdog != 1 ] || exec 
/usr/sbin/watchdog $watchdog_options (code=exited, status=0/SUCCESS)
    Process: 2758 ExecStartPre=/bin/sh -c [ -z "${watchdog_module}" ] || [ 
"${watchdog_module}" = "none" ] || /sbin/modprobe $watchdog_module 
(code=exited, status=0/SUCCESS)
   Main PID: 2768 (watchdog)
  Tasks: 1
     Memory: 732.0K
    CPU: 13ms
     CGroup: /system.slice/watchdog.service
     └─2768 /usr/sbin/watchdog

  août 28 18:49:56 player-ef15 systemd[1]: Started watchdog daemon.
  août 28 18:49:56 player-ef15 watchdog[2768]: starting daemon (5.14):
  août 28 18:49:56 player-ef15 watchdog[2768]: int=1s realtime=yes sync=no 
soft=no mla=0 mem=0
  août 28 18:49:56 player-ef15 watchdog[2768]: ping: no machine to check
  août 28 18:49:56 player-ef15 watchdog[2768]: file: no file to check
  août 28 18:49:56 player-ef15 watchdog[2768]: pidfile: no server process to 
check
  août 28 18:49:56 player-ef15 watchdog[2768]: interface: no interface to check
  août 28 18:49:56 player-ef15 watchdog[2768]: temperature: no sensors to check
  août 28 18:49:56 player-ef15 watchdog[2768]: test=none(0) repair=none(0) 
alive=/dev/watchdog heartbeat=none to=root no_act=no force=no
  août 28 18:49:56 player-ef15 watchdog[2768]: cannot open /dev/watchdog (errno 
= 2 = 'No such file or directory')
  ```
  --- 
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D10p', 
'/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', 
'/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', 
'/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=912a4deb-6713-4f38-8c3a-8280e9c732cf
  InstallationDate: Installed on 2017-08-28 (1 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0aa7 Intel Corp. 
   Bus 001 Device 003: ID 046d:c05a Logitech, Inc. M90/M100 Optical Mouse
   Bus 001 Device 002: ID 04ca:0027 Lite-On Technology Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.11.0-14-generic 
root=UUID=25140007-3f56-4beb-8070-e96eabdb6319 ro quiet splash net.ifnames=0 
vt.handoff=7
  ProcVersionSignature: Ubuntu 4.11.0-14.20~16.04.1-generic 4.11.12
  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.11.0-14-generic N/A
   linux-backports-modules-4.11.0-14-generic  N/A
   linux-firmware 1.157.11
  Tags:  xenial
  Uname: Linux 4.11.0-14-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dialout dip lpadmin mongodb plugdev pulse-access 
sambashare sudo video www-data
  _MarkForUpload: True
  dmi.bios.date: 11/24/2016
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: AYAPLCEL.86A.0029.2016.1124.1625
  dmi.board.name: NUC6CAYB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: J23203-402
  dm

[Kernel-packages] [Bug 1713535] RfKill.txt

apport information

** Attachment added: "RfKill.txt"
   https://bugs.launchpad.net/bugs/1713535/+attachment/4940878/+files/RfKill.txt

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

Title:
  No /dev/watchdog on NUC6CAYS devices with iTCO_wdt

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  It looks like iTCO_wdt won't properly setup a /dev/watchdog device on
  Intel recent Celeron NUCs (NUC6CAYS).

  ```
  # uname -a
  Linux player-ef15 4.11.0-14-generic #20~16.04.1-Ubuntu SMP Wed Aug 9 09:06:22 
UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
  # lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 16.04.3 LTS
  Release:  16.04
  Codename: xenial
  ```

  Modules are properly loaded (but looks like it is not used)

  ```
  # lsmod | grep -e dog -e wdt
  iTCO_wdt   16384  0
  iTCO_vendor_support16384  1 iTCO_wdt
  ```

  No device found in kernel.log:
  ```
  Aug 28 18:49:56 player-ef15 kernel: [   14.192689] iTCO_vendor_support: 
vendor-support=0
  Aug 28 18:49:56 player-ef15 kernel: [   14.198585] iTCO_wdt: Intel TCO 
WatchDog Timer Driver v1.11
  ```

  No device found by the service:

  ```
  # service watchdog status
  ● watchdog.service - watchdog daemon
     Loaded: loaded (/lib/systemd/system/watchdog.service; enabled; vendor 
preset: enabled)
     Active: active (running) since lun. 2017-08-28 18:49:56 CEST; 17s ago
    Process: 2763 ExecStart=/bin/sh -c [ $run_watchdog != 1 ] || exec 
/usr/sbin/watchdog $watchdog_options (code=exited, status=0/SUCCESS)
    Process: 2758 ExecStartPre=/bin/sh -c [ -z "${watchdog_module}" ] || [ 
"${watchdog_module}" = "none" ] || /sbin/modprobe $watchdog_module 
(code=exited, status=0/SUCCESS)
   Main PID: 2768 (watchdog)
  Tasks: 1
     Memory: 732.0K
    CPU: 13ms
     CGroup: /system.slice/watchdog.service
     └─2768 /usr/sbin/watchdog

  août 28 18:49:56 player-ef15 systemd[1]: Started watchdog daemon.
  août 28 18:49:56 player-ef15 watchdog[2768]: starting daemon (5.14):
  août 28 18:49:56 player-ef15 watchdog[2768]: int=1s realtime=yes sync=no 
soft=no mla=0 mem=0
  août 28 18:49:56 player-ef15 watchdog[2768]: ping: no machine to check
  août 28 18:49:56 player-ef15 watchdog[2768]: file: no file to check
  août 28 18:49:56 player-ef15 watchdog[2768]: pidfile: no server process to 
check
  août 28 18:49:56 player-ef15 watchdog[2768]: interface: no interface to check
  août 28 18:49:56 player-ef15 watchdog[2768]: temperature: no sensors to check
  août 28 18:49:56 player-ef15 watchdog[2768]: test=none(0) repair=none(0) 
alive=/dev/watchdog heartbeat=none to=root no_act=no force=no
  août 28 18:49:56 player-ef15 watchdog[2768]: cannot open /dev/watchdog (errno 
= 2 = 'No such file or directory')
  ```
  --- 
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D10p', 
'/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', 
'/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', 
'/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=912a4deb-6713-4f38-8c3a-8280e9c732cf
  InstallationDate: Installed on 2017-08-28 (1 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0aa7 Intel Corp. 
   Bus 001 Device 003: ID 046d:c05a Logitech, Inc. M90/M100 Optical Mouse
   Bus 001 Device 002: ID 04ca:0027 Lite-On Technology Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.11.0-14-generic 
root=UUID=25140007-3f56-4beb-8070-e96eabdb6319 ro quiet splash net.ifnames=0 
vt.handoff=7
  ProcVersionSignature: Ubuntu 4.11.0-14.20~16.04.1-generic 4.11.12
  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.11.0-14-generic N/A
   linux-backports-modules-4.11.0-14-generic  N/A
   linux-firmware 1.157.11
  Tags:  xenial
  Uname: Linux 4.11.0-14-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dialout dip lpadmin mongodb plugdev pulse-access 
sambashare sudo video www-data
  _MarkForUpload: True
  dmi.bios.date: 11/24/2016
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: AYAPLCEL.86A.0029.2016.1124.1625
  dmi.board.name: NUC6CAYB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: J23203-402
  dmi.chassis.type: 3
  dmi.m

[Kernel-packages] [Bug 1713535] ProcModules.txt

apport information

** Attachment added: "ProcModules.txt"
   
https://bugs.launchpad.net/bugs/1713535/+attachment/4940877/+files/ProcModules.txt

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

Title:
  No /dev/watchdog on NUC6CAYS devices with iTCO_wdt

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  It looks like iTCO_wdt won't properly setup a /dev/watchdog device on
  Intel recent Celeron NUCs (NUC6CAYS).

  ```
  # uname -a
  Linux player-ef15 4.11.0-14-generic #20~16.04.1-Ubuntu SMP Wed Aug 9 09:06:22 
UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
  # lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 16.04.3 LTS
  Release:  16.04
  Codename: xenial
  ```

  Modules are properly loaded (but looks like it is not used)

  ```
  # lsmod | grep -e dog -e wdt
  iTCO_wdt   16384  0
  iTCO_vendor_support16384  1 iTCO_wdt
  ```

  No device found in kernel.log:
  ```
  Aug 28 18:49:56 player-ef15 kernel: [   14.192689] iTCO_vendor_support: 
vendor-support=0
  Aug 28 18:49:56 player-ef15 kernel: [   14.198585] iTCO_wdt: Intel TCO 
WatchDog Timer Driver v1.11
  ```

  No device found by the service:

  ```
  # service watchdog status
  ● watchdog.service - watchdog daemon
     Loaded: loaded (/lib/systemd/system/watchdog.service; enabled; vendor 
preset: enabled)
     Active: active (running) since lun. 2017-08-28 18:49:56 CEST; 17s ago
    Process: 2763 ExecStart=/bin/sh -c [ $run_watchdog != 1 ] || exec 
/usr/sbin/watchdog $watchdog_options (code=exited, status=0/SUCCESS)
    Process: 2758 ExecStartPre=/bin/sh -c [ -z "${watchdog_module}" ] || [ 
"${watchdog_module}" = "none" ] || /sbin/modprobe $watchdog_module 
(code=exited, status=0/SUCCESS)
   Main PID: 2768 (watchdog)
  Tasks: 1
     Memory: 732.0K
    CPU: 13ms
     CGroup: /system.slice/watchdog.service
     └─2768 /usr/sbin/watchdog

  août 28 18:49:56 player-ef15 systemd[1]: Started watchdog daemon.
  août 28 18:49:56 player-ef15 watchdog[2768]: starting daemon (5.14):
  août 28 18:49:56 player-ef15 watchdog[2768]: int=1s realtime=yes sync=no 
soft=no mla=0 mem=0
  août 28 18:49:56 player-ef15 watchdog[2768]: ping: no machine to check
  août 28 18:49:56 player-ef15 watchdog[2768]: file: no file to check
  août 28 18:49:56 player-ef15 watchdog[2768]: pidfile: no server process to 
check
  août 28 18:49:56 player-ef15 watchdog[2768]: interface: no interface to check
  août 28 18:49:56 player-ef15 watchdog[2768]: temperature: no sensors to check
  août 28 18:49:56 player-ef15 watchdog[2768]: test=none(0) repair=none(0) 
alive=/dev/watchdog heartbeat=none to=root no_act=no force=no
  août 28 18:49:56 player-ef15 watchdog[2768]: cannot open /dev/watchdog (errno 
= 2 = 'No such file or directory')
  ```
  --- 
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D10p', 
'/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', 
'/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', 
'/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=912a4deb-6713-4f38-8c3a-8280e9c732cf
  InstallationDate: Installed on 2017-08-28 (1 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0aa7 Intel Corp. 
   Bus 001 Device 003: ID 046d:c05a Logitech, Inc. M90/M100 Optical Mouse
   Bus 001 Device 002: ID 04ca:0027 Lite-On Technology Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.11.0-14-generic 
root=UUID=25140007-3f56-4beb-8070-e96eabdb6319 ro quiet splash net.ifnames=0 
vt.handoff=7
  ProcVersionSignature: Ubuntu 4.11.0-14.20~16.04.1-generic 4.11.12
  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.11.0-14-generic N/A
   linux-backports-modules-4.11.0-14-generic  N/A
   linux-firmware 1.157.11
  Tags:  xenial
  Uname: Linux 4.11.0-14-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dialout dip lpadmin mongodb plugdev pulse-access 
sambashare sudo video www-data
  _MarkForUpload: True
  dmi.bios.date: 11/24/2016
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: AYAPLCEL.86A.0029.2016.1124.1625
  dmi.board.name: NUC6CAYB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: J23203-402
  dmi.chassis.type

[Kernel-packages] [Bug 1713535] WifiSyslog.txt

apport information

** Attachment added: "WifiSyslog.txt"
   
https://bugs.launchpad.net/bugs/1713535/+attachment/4940880/+files/WifiSyslog.txt

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

Title:
  No /dev/watchdog on NUC6CAYS devices with iTCO_wdt

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  It looks like iTCO_wdt won't properly setup a /dev/watchdog device on
  Intel recent Celeron NUCs (NUC6CAYS).

  ```
  # uname -a
  Linux player-ef15 4.11.0-14-generic #20~16.04.1-Ubuntu SMP Wed Aug 9 09:06:22 
UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
  # lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 16.04.3 LTS
  Release:  16.04
  Codename: xenial
  ```

  Modules are properly loaded (but looks like it is not used)

  ```
  # lsmod | grep -e dog -e wdt
  iTCO_wdt   16384  0
  iTCO_vendor_support16384  1 iTCO_wdt
  ```

  No device found in kernel.log:
  ```
  Aug 28 18:49:56 player-ef15 kernel: [   14.192689] iTCO_vendor_support: 
vendor-support=0
  Aug 28 18:49:56 player-ef15 kernel: [   14.198585] iTCO_wdt: Intel TCO 
WatchDog Timer Driver v1.11
  ```

  No device found by the service:

  ```
  # service watchdog status
  ● watchdog.service - watchdog daemon
     Loaded: loaded (/lib/systemd/system/watchdog.service; enabled; vendor 
preset: enabled)
     Active: active (running) since lun. 2017-08-28 18:49:56 CEST; 17s ago
    Process: 2763 ExecStart=/bin/sh -c [ $run_watchdog != 1 ] || exec 
/usr/sbin/watchdog $watchdog_options (code=exited, status=0/SUCCESS)
    Process: 2758 ExecStartPre=/bin/sh -c [ -z "${watchdog_module}" ] || [ 
"${watchdog_module}" = "none" ] || /sbin/modprobe $watchdog_module 
(code=exited, status=0/SUCCESS)
   Main PID: 2768 (watchdog)
  Tasks: 1
     Memory: 732.0K
    CPU: 13ms
     CGroup: /system.slice/watchdog.service
     └─2768 /usr/sbin/watchdog

  août 28 18:49:56 player-ef15 systemd[1]: Started watchdog daemon.
  août 28 18:49:56 player-ef15 watchdog[2768]: starting daemon (5.14):
  août 28 18:49:56 player-ef15 watchdog[2768]: int=1s realtime=yes sync=no 
soft=no mla=0 mem=0
  août 28 18:49:56 player-ef15 watchdog[2768]: ping: no machine to check
  août 28 18:49:56 player-ef15 watchdog[2768]: file: no file to check
  août 28 18:49:56 player-ef15 watchdog[2768]: pidfile: no server process to 
check
  août 28 18:49:56 player-ef15 watchdog[2768]: interface: no interface to check
  août 28 18:49:56 player-ef15 watchdog[2768]: temperature: no sensors to check
  août 28 18:49:56 player-ef15 watchdog[2768]: test=none(0) repair=none(0) 
alive=/dev/watchdog heartbeat=none to=root no_act=no force=no
  août 28 18:49:56 player-ef15 watchdog[2768]: cannot open /dev/watchdog (errno 
= 2 = 'No such file or directory')
  ```
  --- 
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D10p', 
'/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', 
'/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', 
'/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=912a4deb-6713-4f38-8c3a-8280e9c732cf
  InstallationDate: Installed on 2017-08-28 (1 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0aa7 Intel Corp. 
   Bus 001 Device 003: ID 046d:c05a Logitech, Inc. M90/M100 Optical Mouse
   Bus 001 Device 002: ID 04ca:0027 Lite-On Technology Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.11.0-14-generic 
root=UUID=25140007-3f56-4beb-8070-e96eabdb6319 ro quiet splash net.ifnames=0 
vt.handoff=7
  ProcVersionSignature: Ubuntu 4.11.0-14.20~16.04.1-generic 4.11.12
  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.11.0-14-generic N/A
   linux-backports-modules-4.11.0-14-generic  N/A
   linux-firmware 1.157.11
  Tags:  xenial
  Uname: Linux 4.11.0-14-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dialout dip lpadmin mongodb plugdev pulse-access 
sambashare sudo video www-data
  _MarkForUpload: True
  dmi.bios.date: 11/24/2016
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: AYAPLCEL.86A.0029.2016.1124.1625
  dmi.board.name: NUC6CAYB
  dmi.board.vendor:

[Kernel-packages] [Bug 1713535] ProcEnviron.txt

apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/1713535/+attachment/4940875/+files/ProcEnviron.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/1713535

Title:
  No /dev/watchdog on NUC6CAYS devices with iTCO_wdt

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  It looks like iTCO_wdt won't properly setup a /dev/watchdog device on
  Intel recent Celeron NUCs (NUC6CAYS).

  ```
  # uname -a
  Linux player-ef15 4.11.0-14-generic #20~16.04.1-Ubuntu SMP Wed Aug 9 09:06:22 
UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
  # lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 16.04.3 LTS
  Release:  16.04
  Codename: xenial
  ```

  Modules are properly loaded (but looks like it is not used)

  ```
  # lsmod | grep -e dog -e wdt
  iTCO_wdt   16384  0
  iTCO_vendor_support16384  1 iTCO_wdt
  ```

  No device found in kernel.log:
  ```
  Aug 28 18:49:56 player-ef15 kernel: [   14.192689] iTCO_vendor_support: 
vendor-support=0
  Aug 28 18:49:56 player-ef15 kernel: [   14.198585] iTCO_wdt: Intel TCO 
WatchDog Timer Driver v1.11
  ```

  No device found by the service:

  ```
  # service watchdog status
  ● watchdog.service - watchdog daemon
     Loaded: loaded (/lib/systemd/system/watchdog.service; enabled; vendor 
preset: enabled)
     Active: active (running) since lun. 2017-08-28 18:49:56 CEST; 17s ago
    Process: 2763 ExecStart=/bin/sh -c [ $run_watchdog != 1 ] || exec 
/usr/sbin/watchdog $watchdog_options (code=exited, status=0/SUCCESS)
    Process: 2758 ExecStartPre=/bin/sh -c [ -z "${watchdog_module}" ] || [ 
"${watchdog_module}" = "none" ] || /sbin/modprobe $watchdog_module 
(code=exited, status=0/SUCCESS)
   Main PID: 2768 (watchdog)
  Tasks: 1
     Memory: 732.0K
    CPU: 13ms
     CGroup: /system.slice/watchdog.service
     └─2768 /usr/sbin/watchdog

  août 28 18:49:56 player-ef15 systemd[1]: Started watchdog daemon.
  août 28 18:49:56 player-ef15 watchdog[2768]: starting daemon (5.14):
  août 28 18:49:56 player-ef15 watchdog[2768]: int=1s realtime=yes sync=no 
soft=no mla=0 mem=0
  août 28 18:49:56 player-ef15 watchdog[2768]: ping: no machine to check
  août 28 18:49:56 player-ef15 watchdog[2768]: file: no file to check
  août 28 18:49:56 player-ef15 watchdog[2768]: pidfile: no server process to 
check
  août 28 18:49:56 player-ef15 watchdog[2768]: interface: no interface to check
  août 28 18:49:56 player-ef15 watchdog[2768]: temperature: no sensors to check
  août 28 18:49:56 player-ef15 watchdog[2768]: test=none(0) repair=none(0) 
alive=/dev/watchdog heartbeat=none to=root no_act=no force=no
  août 28 18:49:56 player-ef15 watchdog[2768]: cannot open /dev/watchdog (errno 
= 2 = 'No such file or directory')
  ```
  --- 
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D10p', 
'/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', 
'/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', 
'/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=912a4deb-6713-4f38-8c3a-8280e9c732cf
  InstallationDate: Installed on 2017-08-28 (1 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0aa7 Intel Corp. 
   Bus 001 Device 003: ID 046d:c05a Logitech, Inc. M90/M100 Optical Mouse
   Bus 001 Device 002: ID 04ca:0027 Lite-On Technology Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.11.0-14-generic 
root=UUID=25140007-3f56-4beb-8070-e96eabdb6319 ro quiet splash net.ifnames=0 
vt.handoff=7
  ProcVersionSignature: Ubuntu 4.11.0-14.20~16.04.1-generic 4.11.12
  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.11.0-14-generic N/A
   linux-backports-modules-4.11.0-14-generic  N/A
   linux-firmware 1.157.11
  Tags:  xenial
  Uname: Linux 4.11.0-14-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dialout dip lpadmin mongodb plugdev pulse-access 
sambashare sudo video www-data
  _MarkForUpload: True
  dmi.bios.date: 11/24/2016
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: AYAPLCEL.86A.0029.2016.1124.1625
  dmi.board.name: NUC6CAYB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: J23203-402
  dmi.chassis.type

[Kernel-packages] [Bug 1713535] ProcInterrupts.txt

apport information

** Attachment added: "ProcInterrupts.txt"
   
https://bugs.launchpad.net/bugs/1713535/+attachment/4940876/+files/ProcInterrupts.txt

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

Title:
  No /dev/watchdog on NUC6CAYS devices with iTCO_wdt

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  It looks like iTCO_wdt won't properly setup a /dev/watchdog device on
  Intel recent Celeron NUCs (NUC6CAYS).

  ```
  # uname -a
  Linux player-ef15 4.11.0-14-generic #20~16.04.1-Ubuntu SMP Wed Aug 9 09:06:22 
UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
  # lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 16.04.3 LTS
  Release:  16.04
  Codename: xenial
  ```

  Modules are properly loaded (but looks like it is not used)

  ```
  # lsmod | grep -e dog -e wdt
  iTCO_wdt   16384  0
  iTCO_vendor_support16384  1 iTCO_wdt
  ```

  No device found in kernel.log:
  ```
  Aug 28 18:49:56 player-ef15 kernel: [   14.192689] iTCO_vendor_support: 
vendor-support=0
  Aug 28 18:49:56 player-ef15 kernel: [   14.198585] iTCO_wdt: Intel TCO 
WatchDog Timer Driver v1.11
  ```

  No device found by the service:

  ```
  # service watchdog status
  ● watchdog.service - watchdog daemon
     Loaded: loaded (/lib/systemd/system/watchdog.service; enabled; vendor 
preset: enabled)
     Active: active (running) since lun. 2017-08-28 18:49:56 CEST; 17s ago
    Process: 2763 ExecStart=/bin/sh -c [ $run_watchdog != 1 ] || exec 
/usr/sbin/watchdog $watchdog_options (code=exited, status=0/SUCCESS)
    Process: 2758 ExecStartPre=/bin/sh -c [ -z "${watchdog_module}" ] || [ 
"${watchdog_module}" = "none" ] || /sbin/modprobe $watchdog_module 
(code=exited, status=0/SUCCESS)
   Main PID: 2768 (watchdog)
  Tasks: 1
     Memory: 732.0K
    CPU: 13ms
     CGroup: /system.slice/watchdog.service
     └─2768 /usr/sbin/watchdog

  août 28 18:49:56 player-ef15 systemd[1]: Started watchdog daemon.
  août 28 18:49:56 player-ef15 watchdog[2768]: starting daemon (5.14):
  août 28 18:49:56 player-ef15 watchdog[2768]: int=1s realtime=yes sync=no 
soft=no mla=0 mem=0
  août 28 18:49:56 player-ef15 watchdog[2768]: ping: no machine to check
  août 28 18:49:56 player-ef15 watchdog[2768]: file: no file to check
  août 28 18:49:56 player-ef15 watchdog[2768]: pidfile: no server process to 
check
  août 28 18:49:56 player-ef15 watchdog[2768]: interface: no interface to check
  août 28 18:49:56 player-ef15 watchdog[2768]: temperature: no sensors to check
  août 28 18:49:56 player-ef15 watchdog[2768]: test=none(0) repair=none(0) 
alive=/dev/watchdog heartbeat=none to=root no_act=no force=no
  août 28 18:49:56 player-ef15 watchdog[2768]: cannot open /dev/watchdog (errno 
= 2 = 'No such file or directory')
  ```
  --- 
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D10p', 
'/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', 
'/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', 
'/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=912a4deb-6713-4f38-8c3a-8280e9c732cf
  InstallationDate: Installed on 2017-08-28 (1 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0aa7 Intel Corp. 
   Bus 001 Device 003: ID 046d:c05a Logitech, Inc. M90/M100 Optical Mouse
   Bus 001 Device 002: ID 04ca:0027 Lite-On Technology Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.11.0-14-generic 
root=UUID=25140007-3f56-4beb-8070-e96eabdb6319 ro quiet splash net.ifnames=0 
vt.handoff=7
  ProcVersionSignature: Ubuntu 4.11.0-14.20~16.04.1-generic 4.11.12
  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.11.0-14-generic N/A
   linux-backports-modules-4.11.0-14-generic  N/A
   linux-firmware 1.157.11
  Tags:  xenial
  Uname: Linux 4.11.0-14-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dialout dip lpadmin mongodb plugdev pulse-access 
sambashare sudo video www-data
  _MarkForUpload: True
  dmi.bios.date: 11/24/2016
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: AYAPLCEL.86A.0029.2016.1124.1625
  dmi.board.name: NUC6CAYB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: J23203-402
  dmi.chassi

[Kernel-packages] [Bug 1713535] UdevDb.txt

apport information

** Attachment added: "UdevDb.txt"
   https://bugs.launchpad.net/bugs/1713535/+attachment/4940879/+files/UdevDb.txt

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

Title:
  No /dev/watchdog on NUC6CAYS devices with iTCO_wdt

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  It looks like iTCO_wdt won't properly setup a /dev/watchdog device on
  Intel recent Celeron NUCs (NUC6CAYS).

  ```
  # uname -a
  Linux player-ef15 4.11.0-14-generic #20~16.04.1-Ubuntu SMP Wed Aug 9 09:06:22 
UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
  # lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 16.04.3 LTS
  Release:  16.04
  Codename: xenial
  ```

  Modules are properly loaded (but looks like it is not used)

  ```
  # lsmod | grep -e dog -e wdt
  iTCO_wdt   16384  0
  iTCO_vendor_support16384  1 iTCO_wdt
  ```

  No device found in kernel.log:
  ```
  Aug 28 18:49:56 player-ef15 kernel: [   14.192689] iTCO_vendor_support: 
vendor-support=0
  Aug 28 18:49:56 player-ef15 kernel: [   14.198585] iTCO_wdt: Intel TCO 
WatchDog Timer Driver v1.11
  ```

  No device found by the service:

  ```
  # service watchdog status
  ● watchdog.service - watchdog daemon
     Loaded: loaded (/lib/systemd/system/watchdog.service; enabled; vendor 
preset: enabled)
     Active: active (running) since lun. 2017-08-28 18:49:56 CEST; 17s ago
    Process: 2763 ExecStart=/bin/sh -c [ $run_watchdog != 1 ] || exec 
/usr/sbin/watchdog $watchdog_options (code=exited, status=0/SUCCESS)
    Process: 2758 ExecStartPre=/bin/sh -c [ -z "${watchdog_module}" ] || [ 
"${watchdog_module}" = "none" ] || /sbin/modprobe $watchdog_module 
(code=exited, status=0/SUCCESS)
   Main PID: 2768 (watchdog)
  Tasks: 1
     Memory: 732.0K
    CPU: 13ms
     CGroup: /system.slice/watchdog.service
     └─2768 /usr/sbin/watchdog

  août 28 18:49:56 player-ef15 systemd[1]: Started watchdog daemon.
  août 28 18:49:56 player-ef15 watchdog[2768]: starting daemon (5.14):
  août 28 18:49:56 player-ef15 watchdog[2768]: int=1s realtime=yes sync=no 
soft=no mla=0 mem=0
  août 28 18:49:56 player-ef15 watchdog[2768]: ping: no machine to check
  août 28 18:49:56 player-ef15 watchdog[2768]: file: no file to check
  août 28 18:49:56 player-ef15 watchdog[2768]: pidfile: no server process to 
check
  août 28 18:49:56 player-ef15 watchdog[2768]: interface: no interface to check
  août 28 18:49:56 player-ef15 watchdog[2768]: temperature: no sensors to check
  août 28 18:49:56 player-ef15 watchdog[2768]: test=none(0) repair=none(0) 
alive=/dev/watchdog heartbeat=none to=root no_act=no force=no
  août 28 18:49:56 player-ef15 watchdog[2768]: cannot open /dev/watchdog (errno 
= 2 = 'No such file or directory')
  ```
  --- 
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D10p', 
'/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', 
'/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', 
'/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=912a4deb-6713-4f38-8c3a-8280e9c732cf
  InstallationDate: Installed on 2017-08-28 (1 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0aa7 Intel Corp. 
   Bus 001 Device 003: ID 046d:c05a Logitech, Inc. M90/M100 Optical Mouse
   Bus 001 Device 002: ID 04ca:0027 Lite-On Technology Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.11.0-14-generic 
root=UUID=25140007-3f56-4beb-8070-e96eabdb6319 ro quiet splash net.ifnames=0 
vt.handoff=7
  ProcVersionSignature: Ubuntu 4.11.0-14.20~16.04.1-generic 4.11.12
  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.11.0-14-generic N/A
   linux-backports-modules-4.11.0-14-generic  N/A
   linux-firmware 1.157.11
  Tags:  xenial
  Uname: Linux 4.11.0-14-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dialout dip lpadmin mongodb plugdev pulse-access 
sambashare sudo video www-data
  _MarkForUpload: True
  dmi.bios.date: 11/24/2016
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: AYAPLCEL.86A.0029.2016.1124.1625
  dmi.board.name: NUC6CAYB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: J23203-402
  dmi.chassis.type: 3
  dmi.m

[Kernel-packages] [Bug 1713470] Re: linux: 4.10.0-34.38 -proposed tracker

2017-08-29 Thread Łukasz Zemczak

** Changed in: kernel-sru-workflow/promote-to-proposed
   Status: Confirmed => In Progress

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

Title:
  linux: 4.10.0-34.38 -proposed tracker

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

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

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

  backports: 1713471,1713472
  derivatives: 1713473
  kernel-stable-phase-changed:Monday, 28. August 2017 19:32 UTC
  kernel-stable-phase:Uploaded

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

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

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

[Kernel-packages] [Bug 1713458] Re: linux-lts-trusty: -proposed tracker

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

** Description changed:

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

** Description changed:

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

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

Title:
  linux-lts-trusty:  -proposed tracker

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

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

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

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

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

[Kernel-packages] [Bug 1713456] Re: linux: 3.13.0-130.179 -proposed tracker

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

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

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  backports: 1713458
  derivatives:
+ kernel-stable-phase-changed:Tuesday, 29. August 2017 16:01 UTC
+ kernel-stable-phase:Uploaded

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  backports: 1713458
  derivatives:
  kernel-stable-phase-changed:Tuesday, 29. August 2017 16:01 UTC
  kernel-stable-phase:Uploaded
+ 
+ -- swm properties --
+ phase: Uploaded

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

Title:
  linux: 3.13.0-130.179 -proposed tracker

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

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

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

  backports: 1713458
  derivatives:
  kernel-stable-phase-changed:Tuesday, 29. August 2017 16:01 UTC
  kernel-stable-phase:Uploaded

  -- swm properties --
  phase: Uploaded

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

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

[Kernel-packages] [Bug 1511511] Re: USB keyboard stops working after pressing extended key

2017-08-29 Thread Alejandro Díaz-Caro

@Kai-Heng Feng: Could you please upload a patch, or the sources, or the config 
file, or whatever change you have made to the kernel, so those with other 
distributions (like me) can also test it?
I am on Arch Linux with kernel 4.12.8.

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

Title:
  USB keyboard stops working after pressing extended key

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  USB keyboard Cougar K500 gaming keyboard has some additional extended
  keys, all of them making the keyboard stop responding if pressed under
  linux. The device is recovered only by unplugging the USB and plugging
  it again.

  The keyboard has been tested under Ubuntu 14.04.3 LTS, Ubuntu 15.04
  and Ubuntu 15.10 (the latter running as virtualbox guest). All tests
  failed with exactly the same behaviour.

  USB ID is: "060b:500a Solid Year".

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: linux-image-4.2.0-16-generic 4.2.0-16.19 [modified: 
boot/vmlinuz-4.2.0-16-generic]
  ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
  Uname: Linux 4.2.0-16-generic x86_64
  ApportVersion: 2.19.1-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pinfli 1055 F pulseaudio
  Date: Thu Oct 29 19:33:23 2015
  HibernationDevice: RESUME=UUID=f68f4b91-ea68-4e4b-9a10-8ed5bca2efbe
  InstallationDate: Installed on 2015-10-24 (5 days ago)
  InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Release amd64 
(20151021)
  IwConfig:
   enp0s3no wireless extensions.
   
   lono wireless extensions.
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 002: ID 060b:500a Solid Year 
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: innotek GmbH VirtualBox
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-16-generic 
root=UUID=523dfd8b-b825-47e3-a116-cb85f901386c ro quiet splash
  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.2.0-16-generic N/A
   linux-backports-modules-4.2.0-16-generic  N/A
   linux-firmware1.149
  RfKill:
   
  SourcePackage: linux
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH

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

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

[Kernel-packages] [Bug 1713765] [NEW] Consider "s390/mm: avoid empty zero pages for KVM guests to avoid postcopy hangs" for Artful

2017-08-29 Thread ChristianEhrhardt

Public bug reported:

Hi,
there is this patch in discussion [1].

If I read correctly between the lines that is supposed to go to -stable trees 
as well as to linxu-s390x next (4.14) submissions.
But the change is rather big and we have to consider taking that early or as 
SRU or not at all.

I wanted to ask the kernel Team to keep an eye on that discussion and take the 
patch into consideration - IMHO it might change KVM behavior on s390 quite a 
bit.
So I'm not sure how SRUable it is while on Artful we migth add it rather soon 
before release.

To some extend we should wait for the discussion on the upstreaming, but
then I wanted to make you aware asap.

[1]: https://lists.gnu.org/archive/html/qemu-devel/2017-08/msg05286.html

** Affects: linux (Ubuntu)
 Importance: Undecided
 Assignee: Seth Forshee (sforshee)
 Status: Incomplete


** Tags: artful

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => Seth Forshee (sforshee)

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

Title:
  Consider "s390/mm: avoid empty zero pages for KVM guests to avoid
  postcopy hangs" for Artful

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hi,
  there is this patch in discussion [1].

  If I read correctly between the lines that is supposed to go to -stable trees 
as well as to linxu-s390x next (4.14) submissions.
  But the change is rather big and we have to consider taking that early or as 
SRU or not at all.

  I wanted to ask the kernel Team to keep an eye on that discussion and take 
the patch into consideration - IMHO it might change KVM behavior on s390 quite 
a bit.
  So I'm not sure how SRUable it is while on Artful we migth add it rather soon 
before release.

  To some extend we should wait for the discussion on the upstreaming,
  but then I wanted to make you aware asap.

  [1]: https://lists.gnu.org/archive/html/qemu-
  devel/2017-08/msg05286.html

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

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

[Kernel-packages] [Bug 1713765] Re: Consider upcoming patch for Artful

2017-08-29 Thread ChristianEhrhardt

Also asking Lou to reverse mirror and let Christian Borntraeger (Author)
be added on the mirror of this.

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

Title:
  Consider "s390/mm: avoid empty zero pages for KVM guests to avoid
  postcopy hangs" for Artful

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hi,
  there is this patch in discussion [1].

  If I read correctly between the lines that is supposed to go to -stable trees 
as well as to linxu-s390x next (4.14) submissions.
  But the change is rather big and we have to consider taking that early or as 
SRU or not at all.

  I wanted to ask the kernel Team to keep an eye on that discussion and take 
the patch into consideration - IMHO it might change KVM behavior on s390 quite 
a bit.
  So I'm not sure how SRUable it is while on Artful we migth add it rather soon 
before release.

  To some extend we should wait for the discussion on the upstreaming,
  but then I wanted to make you aware asap.

  [1]: https://lists.gnu.org/archive/html/qemu-
  devel/2017-08/msg05286.html

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

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

[Kernel-packages] [Bug 1712508] Re: Disappearing screen and flickering after upgrade to 16.04

2017-08-29 Thread udippel

#6:
It says different over there. Nevermind. I don't want to break my system, since
I need it.

I was able to boot with an old 3.13.0-kernel, still lingering in my grub menu.
And I can confirm that everything works perfectly well with that kernel.

I also can confirm that my suspicion with the iommu seems to be wrong,
since with this kernel it shows the same line; that is it doesn't
recognize the bug on Ironlike neither, and yet comes up properly.

In a nutshell: since it runs perfectly okay on an old kernel, I dare to
add 'Confirmed', though without any 'upstream' -attribute.

I also add the dmesg with that kernel. Maybe the experts can spot the
difference that make the screen flicker. At least, I hope so.

** Attachment added: "Screen works perfectly okay with old kernel - dmesg"

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1712508/+attachment/4940882/+files/dmesg_3_13_0_46

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

Title:
Disappearing screen and flickering after upgrade to 16.04

Status in linux package in Ubuntu:
Confirmed

Bug description:
I have two Lenovo T410s that I upgraded from 14.04 to 16.04.
Since then, one is working fine while the other shows mainly an ever
disappearing screen and flickering.

I have asked here:
https://askubuntu.com/questions/947233/i-upgraded-from-kubuntu-14-04-lts-to-16-04-lts-and-now-my-screen-shows-up-and-di?noredirect=1#comment1506995_947233
I also found I am not the only one:
https://askubuntu.com/questions/927407/flickering-screen-with-intel-graphics-on-ubuntu-17-04?noredirect=1#comment1507937_927407
The latter has tried pretty much that could be tried already, to no avail.

I think that I can help with this problem, since my two T410s are
identical in hard- and software, including BIOS, except that one is a
type 2924 (with NVIDIA-card, though disabled in the BIOS), and the
other one is a 2904 (without NVIDIA card).

I have checked for differences at boot time and found DMAR as major
difference:
T410s, 2924: [ 0.335616] DMAR: Disabling batched IOTLB flush on Ironlake
T410s, 2904: [ 0.355681] DMAR: BIOS has allocated no shadow GTT; disabling
IOMMU for graphics

Should this be initially at the root of the problem, I'd consider the
kernel package as responsible, therefore I marked it as above.

The outputs of lspci -k | grep -EA3 'VGA|3D|Display' are identical to
the point.

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

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

[Kernel-packages] [Bug 1713765] Re: Consider "s390/mm: avoid empty zero pages for KVM guests to avoid postcopy hangs" for Artful

** Summary changed:

- Consider upcoming patch for Artful
+ Consider "s390/mm: avoid empty zero pages for KVM guests to avoid postcopy 
hangs" for Artful

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

Title:
  Consider "s390/mm: avoid empty zero pages for KVM guests to avoid
  postcopy hangs" for Artful

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hi,
  there is this patch in discussion [1].

  If I read correctly between the lines that is supposed to go to -stable trees 
as well as to linxu-s390x next (4.14) submissions.
  But the change is rather big and we have to consider taking that early or as 
SRU or not at all.

  I wanted to ask the kernel Team to keep an eye on that discussion and take 
the patch into consideration - IMHO it might change KVM behavior on s390 quite 
a bit.
  So I'm not sure how SRUable it is while on Artful we migth add it rather soon 
before release.

  To some extend we should wait for the discussion on the upstreaming,
  but then I wanted to make you aware asap.

  [1]: https://lists.gnu.org/archive/html/qemu-
  devel/2017-08/msg05286.html

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

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

[Kernel-packages] [Bug 1713765] Re: Consider "s390/mm: avoid empty zero pages for KVM guests to avoid postcopy hangs" for Artful

Looks like the patch just was only just sent yesterday, will give it a
couple days to see if it collects any feedback or acks.

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

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

Title:
  Consider "s390/mm: avoid empty zero pages for KVM guests to avoid
  postcopy hangs" for Artful

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hi,
  there is this patch in discussion [1].

  If I read correctly between the lines that is supposed to go to -stable trees 
as well as to linxu-s390x next (4.14) submissions.
  But the change is rather big and we have to consider taking that early or as 
SRU or not at all.

  I wanted to ask the kernel Team to keep an eye on that discussion and take 
the patch into consideration - IMHO it might change KVM behavior on s390 quite 
a bit.
  So I'm not sure how SRUable it is while on Artful we migth add it rather soon 
before release.

  To some extend we should wait for the discussion on the upstreaming,
  but then I wanted to make you aware asap.

  [1]: https://lists.gnu.org/archive/html/qemu-
  devel/2017-08/msg05286.html

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

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

[Kernel-packages] [Bug 1713470] Re: linux: 4.10.0-34.38 -proposed tracker

2017-08-29 Thread Łukasz Zemczak

** Changed in: kernel-sru-workflow/promote-to-proposed
   Status: In Progress => Fix Committed

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

Title:
  linux: 4.10.0-34.38 -proposed tracker

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

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

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

  backports: 1713471,1713472
  derivatives: 1713473
  kernel-stable-phase-changed:Monday, 28. August 2017 19:32 UTC
  kernel-stable-phase:Uploaded

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

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

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

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

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

apport-collect 1713765

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

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

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

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

** Tags added: artful

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

Title:
  Consider "s390/mm: avoid empty zero pages for KVM guests to avoid
  postcopy hangs" for Artful

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hi,
  there is this patch in discussion [1].

  If I read correctly between the lines that is supposed to go to -stable trees 
as well as to linxu-s390x next (4.14) submissions.
  But the change is rather big and we have to consider taking that early or as 
SRU or not at all.

  I wanted to ask the kernel Team to keep an eye on that discussion and take 
the patch into consideration - IMHO it might change KVM behavior on s390 quite 
a bit.
  So I'm not sure how SRUable it is while on Artful we migth add it rather soon 
before release.

  To some extend we should wait for the discussion on the upstreaming,
  but then I wanted to make you aware asap.

  [1]: https://lists.gnu.org/archive/html/qemu-
  devel/2017-08/msg05286.html

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

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

[Kernel-packages] [Bug 1713467] Re: linux-aws: 4.4.0-1033.42 -proposed tracker

** Changed in: kernel-sru-workflow/promote-to-proposed
   Status: New => Confirmed

** Tags added: block-proposed-xenial

** Tags added: block-proposed

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

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

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

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

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

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

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

[Kernel-packages] [Bug 1713456] Re: linux: 3.13.0-130.179 -proposed tracker

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

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

Title:
  linux: 3.13.0-130.179 -proposed tracker

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

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

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

  backports: 1713458
  derivatives:
  kernel-stable-phase-changed:Tuesday, 29. August 2017 16:01 UTC
  kernel-stable-phase:Uploaded

  -- swm properties --
  phase: Uploaded

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

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

[Kernel-packages] [Bug 1713462] Re: linux: 4.4.0-94.117 -proposed tracker

** Changed in: kernel-sru-workflow/promote-to-proposed
   Status: New => Confirmed

** Tags added: block-proposed-xenial

** Tags added: block-proposed

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  backports: 1713463
  derivatives: 1713464,1713465,1713467,1713468,1713469
  kernel-stable-phase-changed:Tuesday, 29. August 2017 09:02 UTC
  kernel-stable-phase:Uploaded
  
  -- swm properties --
+ boot-testing-requested: true
  phase: Uploaded

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

Title:
  linux: 4.4.0-94.117 -proposed tracker

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

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

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

  backports: 1713463
  derivatives: 1713464,1713465,1713467,1713468,1713469
  kernel-stable-phase-changed:Tuesday, 29. August 2017 09:02 UTC
  kernel-stable-phase:Uploaded

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

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

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

[Kernel-packages] [Bug 1710019] Re: support GICv3 ITS save/restore & migration

2017-08-29 Thread Vijaya Kumar Kilari

Hi Dann,

Yes, I will upstream the patch.

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

Title:
  support GICv3 ITS save/restore & migration

Status in linux package in Ubuntu:
  Triaged
Status in qemu package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Won't Fix
Status in qemu source package in Xenial:
  Triaged
Status in linux source package in Zesty:
  Triaged
Status in qemu source package in Zesty:
  In Progress

Bug description:
  [Impact]
  Virtual machines on GICv3-based ARM systems cannot be saved/restored or 
migrated.
  This feature was added in QEMU 2.10.

  [Test Case]
  ubuntu@grotrian:~$ sudo virsh save 7936-0 7936-0.sav

  Domain 7936-0 saved to 7936-0.sav

  ubuntu@grotrian:~$ sudo virsh restore 7396-0.sav
  error: Failed to restore domain from 7396-0.sav
  error: operation failed: job: unexpectedly failed

  ubuntu@grotrian:~$ sudo tail -3 /var/log/libvirt/qemu/7936-0.log 
  2017-08-10T21:26:38.217427Z qemu-system-aarch64: State blocked by 
non-migratable device 'arm_gicv3_its'
  2017-08-10T21:26:38.217565Z qemu-system-aarch64: load of migration failed: 
Invalid argument
  2017-08-10 21:26:38.217+: shutting down, reason=failed

  [Regression Risk]

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

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

[Kernel-packages] [Bug 1688625] Re: Linux does not recognize the Hantick touchpad as a touchpad and does not enable all the functions

2017-08-29 Thread slimbook

We assemble the pieces.
The touchpad manufacturer does not support Linux and refuses to give it.

I just need the hardware ID: AH6Q.bGO0sOimOM3 to be recognized as touchpad, it 
does not matter if it uses the protocol of libinput or evdev, because both 
protocols allow to configure the natural scrolling. 
But Ubuntu says that this hardware is a mouse and does not display the option 
to activate the natural scrolling.

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

Title:
  Linux does not recognize the Hantick touchpad as a touchpad and does
  not enable all the functions

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hello,
  We have laptops with touchpad Hantick, that on Miscrosft Windows work with 
Elan driver.

  Linux does not recognize the Hantick touchpad as a touchpad and does
  not enable all the functions of evdev or libinput.

  Thanks
  

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-77-generic 4.4.0-77.98
  ProcVersionSignature: Ubuntu 4.4.0-77.98-generic 4.4.59
  Uname: Linux 4.4.0-77-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  slimbook   1720 F pulseaudio
  CurrentDesktop: Unity
  Date: Fri May  5 20:01:33 2017
  HibernationDevice: RESUME=UUID=eef047d2-92ea-4166-a300-7a4de6af1448
  InstallationDate: Installed on 2017-05-05 (0 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 090c:037c Silicon Motion, Inc. - Taiwan (formerly 
Feiya Technology Corp.) 300k Pixel Camera
   Bus 001 Device 003: ID 8087:0a2a Intel Corp.
   Bus 001 Device 002: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: SLIMBOOK KATANA
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-77-generic.efi.signed 
root=UUID=00a6febb-4980-4147-a2e8-29930aed3d30 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-77-generic N/A
   linux-backports-modules-4.4.0-77-generic  N/A
   linux-firmware1.157.8
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/25/2016
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 16L
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: KATANA
  dmi.board.vendor: SLIMBOOK
  dmi.board.version: Type2 - Board Version
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: SLIMBOOK
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvr16L:bd07/25/2016:svnSLIMBOOK:pnKATANA:pvrTBDbyOEM:rvnSLIMBOOK:rnKATANA:rvrType2-BoardVersion:cvnSLIMBOOK:ct10:cvrChassisVersion:
  dmi.product.name: KATANA
  dmi.product.version: TBD by OEM
  dmi.sys.vendor: SLIMBOOK

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

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

[Kernel-packages] [Bug 1713773] [NEW] package linux-image-generic 4.4.0.93.98 failed to install/upgrade: проблемы зависимостей — оставляем не настроенным

2017-08-29 Thread rolmops

Public bug reported:

package linux-image-generic 4.4.0.93.98 failed to install/upgrade:
проблемы зависимостей — оставляем не настроенным

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: linux-image-generic 4.4.0.93.98
ProcVersionSignature: Ubuntu 4.4.0-92.115-generic 4.4.76
Uname: Linux 4.4.0-92-generic i686
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: i386
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  lts16  1724 F pulseaudio
Date: Tue Aug 29 19:44:16 2017
ErrorMessage: проблемы зависимостей — оставляем не настроенным
HibernationDevice: RESUME=UUID=98368513-6fb3-4199-9db4-47c090908d4c
InstallationDate: Installed on 2017-05-27 (94 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release i386 (20160719)
MachineType: ASUSTeK COMPUTER INC. 1025C
ProcFB: 0 psbdrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-92-generic 
root=UUID=404fdaa5-0645-4283-aeee-41c8e61442dc ro quiet splash
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu3.12
SourcePackage: linux
Title: package linux-image-generic 4.4.0.93.98 failed to install/upgrade: 
проблемы зависимостей — оставляем не настроенным
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/08/2012
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1025C.0801
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: 1025C
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: x.xx
dmi.chassis.asset.tag: 0x
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: x.x
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1025C.0801:bd03/08/2012:svnASUSTeKCOMPUTERINC.:pn1025C:pvrx.x:rvnASUSTeKCOMPUTERINC.:rn1025C:rvrx.xx:cvnASUSTeKCOMPUTERINC.:ct10:cvrx.x:
dmi.product.name: 1025C
dmi.product.version: x.x
dmi.sys.vendor: ASUSTeK COMPUTER INC.

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


** Tags: apport-package i386 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/1713773

Title:
  package linux-image-generic 4.4.0.93.98 failed to install/upgrade:
  проблемы зависимостей — оставляем не настроенным

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  package linux-image-generic 4.4.0.93.98 failed to install/upgrade:
  проблемы зависимостей — оставляем не настроенным

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-image-generic 4.4.0.93.98
  ProcVersionSignature: Ubuntu 4.4.0-92.115-generic 4.4.76
  Uname: Linux 4.4.0-92-generic i686
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  lts16  1724 F pulseaudio
  Date: Tue Aug 29 19:44:16 2017
  ErrorMessage: проблемы зависимостей — оставляем не настроенным
  HibernationDevice: RESUME=UUID=98368513-6fb3-4199-9db4-47c090908d4c
  InstallationDate: Installed on 2017-05-27 (94 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release i386 (20160719)
  MachineType: ASUSTeK COMPUTER INC. 1025C
  ProcFB: 0 psbdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-92-generic 
root=UUID=404fdaa5-0645-4283-aeee-41c8e61442dc ro quiet splash
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu3.12
  SourcePackage: linux
  Title: package linux-image-generic 4.4.0.93.98 failed to install/upgrade: 
проблемы зависимостей — оставляем не настроенным
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/08/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1025C.0801
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: 1025C
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: x.xx
  dmi.chassis.asset.tag: 0x
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: x.x
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1025C.0801:bd03/08/2012:svnASUSTeKCOMPUTERINC.:pn1025C:pvrx.x:rvnASUSTeKCOMPUTERINC.:rn1025C:rvrx.xx:cvnASUSTeKCOMPUTERINC.:ct10:cvrx.x:
  dmi.product.name: 1025C
  dmi.product.version: x.x
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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

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

This change was made by a bot.

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

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

Title:
  package linux-image-generic 4.4.0.93.98 failed to install/upgrade:
  проблемы зависимостей — оставляем не настроенным

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  package linux-image-generic 4.4.0.93.98 failed to install/upgrade:
  проблемы зависимостей — оставляем не настроенным

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-image-generic 4.4.0.93.98
  ProcVersionSignature: Ubuntu 4.4.0-92.115-generic 4.4.76
  Uname: Linux 4.4.0-92-generic i686
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  lts16  1724 F pulseaudio
  Date: Tue Aug 29 19:44:16 2017
  ErrorMessage: проблемы зависимостей — оставляем не настроенным
  HibernationDevice: RESUME=UUID=98368513-6fb3-4199-9db4-47c090908d4c
  InstallationDate: Installed on 2017-05-27 (94 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release i386 (20160719)
  MachineType: ASUSTeK COMPUTER INC. 1025C
  ProcFB: 0 psbdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-92-generic 
root=UUID=404fdaa5-0645-4283-aeee-41c8e61442dc ro quiet splash
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu3.12
  SourcePackage: linux
  Title: package linux-image-generic 4.4.0.93.98 failed to install/upgrade: 
проблемы зависимостей — оставляем не настроенным
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/08/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1025C.0801
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: 1025C
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: x.xx
  dmi.chassis.asset.tag: 0x
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: x.x
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1025C.0801:bd03/08/2012:svnASUSTeKCOMPUTERINC.:pn1025C:pvrx.x:rvnASUSTeKCOMPUTERINC.:rn1025C:rvrx.xx:cvnASUSTeKCOMPUTERINC.:ct10:cvrx.x:
  dmi.product.name: 1025C
  dmi.product.version: x.x
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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

[Kernel-packages] [Bug 1713787] [NEW] linux 4.4.0-93 triggers call traces related to the bonding module

2017-08-29 Thread Simon Déziel

Public bug reported:

== Regression details ==

Since the rolled out 4.4.0-93, we are getting many ~identical call
traces that look like this:

[ cut here ]
WARNING: CPU: 0 PID:  at 
/build/linux-YyUNAI/linux-4.4.0/net/core/dev.c:2445 
skb_warn_bad_offload+0xd1/0x120()
bond0: caps=(0x0fd97ba9, 0x) len=1487 data_len=0 
gso_size=1440 gso_type=6 ip_summed=0
Modules linked in: binfmt_misc nf_log_ipv6 nf_conntrack_ipv6 nf_defrag_ipv6 
ip6table_filter ip6_tables nf_log_ipv4 nf_log_common xt_LOG xt_tcpudp 
nf_conntrack_ipv4 nf_defrag_ipv4 xt_owner xt_conntrack nf_conntrack 
iptable_filter ip_tables x_tables 8021q garp mrp bonding ipmi_devintf dcdbas 
intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp crct10dif_pclmul 
ipmi_ssif crc32_pclmul bridge ghash_clmulni_intel stp llc aesni_intel 
aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd vhost_net vhost macvtap 
macvlan sb_edac edac_core kvm_intel kvm ipmi_si 8250_fintek ipmi_msghandler 
lpc_ich irqbypass shpchp mei_me mei acpi_power_meter mac_hid drbd lru_cache 
autofs4 btrfs xor raid6_pq bnx2x mxm_wmi vxlan ip6_udp_tunnel tg3 udp_tunnel 
ahci mdio ptp libcrc32c libahci megaraid_sas pps_core fjes wmi
CPU: 0 PID:  Comm: qemu-system-x86 Not tainted 4.4.0-93-generic #116-Ubuntu
Hardware name: Dell Inc. PowerEdge R830/0VVT0H, BIOS 1.3.4 11/09/2016
 0286 f5a0655ded96de87 88bd7f2038c0 813f9f83
 88bd7f203908 81d6f780 88bd7f2038f8 810812f2
 88b6e118e000 8a3d17f52000 0006 0081
Call Trace:
   [] dump_stack+0x63/0x90
 [] warn_slowpath_common+0x82/0xc0
 [] warn_slowpath_fmt+0x5c/0x80
 [] ? ___ratelimit+0xa2/0xe0
 [] skb_warn_bad_offload+0xd1/0x120
 [] __skb_gso_segment+0xfd/0x110
 [] validate_xmit_skb.isra.97.part.98+0x10d/0x2b0
 [] __dev_queue_xmit+0x582/0x590
 [] dev_queue_xmit+0x10/0x20
 [] vlan_dev_hard_start_xmit+0x98/0x120 [8021q]
 [] dev_hard_start_xmit+0x249/0x3d0
 [] __dev_queue_xmit+0x526/0x590
 [] dev_queue_xmit+0x10/0x20
 [] br_dev_queue_push_xmit+0x7a/0x140 [bridge]
 [] br_forward_finish+0x3d/0xb0 [bridge]
 [] ? br_handle_frame_finish+0x3a0/0x620 [bridge]
 [] __br_forward+0xa6/0x130 [bridge]
 [] br_forward+0x87/0x90 [bridge]
 [] br_handle_frame_finish+0x3a0/0x620 [bridge]
 [] ? __netif_receive_skb_core+0x364/0xa60
 [] ? dev_gro_receive+0x1c0/0x3c0
 [] br_handle_frame+0x174/0x2b0 [bridge]
 [] ? tg3_poll_work+0x4cb/0xf10 [tg3]
 [] ? __netif_receive_skb+0x18/0x60
 [] __netif_receive_skb_core+0x364/0xa60
 [] ? napi_gro_flush+0x5a/0x80
 [] __netif_receive_skb+0x18/0x60
 [] process_backlog+0xa8/0x150
 [] net_rx_action+0x21e/0x360
 [] __do_softirq+0x101/0x290
 [] do_softirq_own_stack+0x1c/0x30
   [] do_softirq.part.19+0x38/0x40
 [] do_softirq+0x1d/0x20
 [] netif_rx_ni+0x33/0x80
 [] tun_get_user+0x506/0x880
 [] tun_chr_write_iter+0x57/0x70
 [] do_iter_readv_writev+0x6c/0xa0
 [] do_readv_writev+0x18f/0x230
 [] vfs_writev+0x39/0x50
 [] SyS_writev+0x59/0xf0
 [] entry_SYSCALL_64_fastpath+0x16/0x71
---[ end trace 9fe5c984ff319e6a ]---

For now this doesn't seem to have any user visible impact but we are not
paying close attention to latencies/packet losses.

Discovered in version:  linux-image-4.4.0-93-generic 4.4.0-93.116
Last known good version: linux-image-4.4.0-92-generic 4.4.0-92.115

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-93-generic 4.4.0-93.116
ProcVersionSignature: Ubuntu 4.4.0-93.116-generic 4.4.79
Uname: Linux 4.4.0-93-generic x86_64
AlsaDevices:
 total 0
 crw-rw 1 root audio 116,  1 Aug 28 12:27 seq
 crw-rw 1 root audio 116, 33 Aug 28 12:27 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
AudioDevicesInUse: Error: [Errno 2] No such file or directory: 'fuser'
Date: Tue Aug 29 13:46:12 2017
HibernationDevice: RESUME=/dev/mapper/vghost-swap
InstallationDate: Installed on 2017-04-01 (149 days ago)
InstallationMedia: Ubuntu-Server 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.8)
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
Lsusb:
 Bus 002 Device 002: ID 8087:8002 Intel Corp. 
 Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 001 Device 003: ID 413c:a001 Dell Computer Corp. Hub
 Bus 001 Device 002: ID 8087:800a Intel Corp. 
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Dell Inc. PowerEdge R830
PciMultimedia:
 
ProcFB: 0 EFI VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-93-generic.efi.signed 
root=/dev/mapper/vghost-root ro panic=300
RelatedPackageVersions:
 linux-restricted-modules-4.4.0-93-generic N/A
 linux-backports-modules-4.4.0-93-generic  N/A
 linux-firmware1.157.11
RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date:

[Kernel-packages] [Bug 1713787] Re: linux 4.4.0-93 triggers call traces related to the bonding module

2017-08-29 Thread Simon Déziel

So far those messages were only noticed on 2 of our hypervisor nodes.
I'm attaching the relevant extracts of dmesg on those 2 machines.

** Attachment added: "multiple-dmesg.tgz"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1713787/+attachment/4940943/+files/multiple-dmesg.tgz

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

Title:
  linux 4.4.0-93 triggers call traces related to the bonding module

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  == Regression details ==

  Since the rolled out 4.4.0-93, we are getting many ~identical call
  traces that look like this:

  [ cut here ]
  WARNING: CPU: 0 PID:  at 
/build/linux-YyUNAI/linux-4.4.0/net/core/dev.c:2445 
skb_warn_bad_offload+0xd1/0x120()
  bond0: caps=(0x0fd97ba9, 0x) len=1487 data_len=0 
gso_size=1440 gso_type=6 ip_summed=0
  Modules linked in: binfmt_misc nf_log_ipv6 nf_conntrack_ipv6 nf_defrag_ipv6 
ip6table_filter ip6_tables nf_log_ipv4 nf_log_common xt_LOG xt_tcpudp 
nf_conntrack_ipv4 nf_defrag_ipv4 xt_owner xt_conntrack nf_conntrack 
iptable_filter ip_tables x_tables 8021q garp mrp bonding ipmi_devintf dcdbas 
intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp crct10dif_pclmul 
ipmi_ssif crc32_pclmul bridge ghash_clmulni_intel stp llc aesni_intel 
aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd vhost_net vhost macvtap 
macvlan sb_edac edac_core kvm_intel kvm ipmi_si 8250_fintek ipmi_msghandler 
lpc_ich irqbypass shpchp mei_me mei acpi_power_meter mac_hid drbd lru_cache 
autofs4 btrfs xor raid6_pq bnx2x mxm_wmi vxlan ip6_udp_tunnel tg3 udp_tunnel 
ahci mdio ptp libcrc32c libahci megaraid_sas pps_core fjes wmi
  CPU: 0 PID:  Comm: qemu-system-x86 Not tainted 4.4.0-93-generic 
#116-Ubuntu
  Hardware name: Dell Inc. PowerEdge R830/0VVT0H, BIOS 1.3.4 11/09/2016
   0286 f5a0655ded96de87 88bd7f2038c0 813f9f83
   88bd7f203908 81d6f780 88bd7f2038f8 810812f2
   88b6e118e000 8a3d17f52000 0006 0081
  Call Trace:
 [] dump_stack+0x63/0x90
   [] warn_slowpath_common+0x82/0xc0
   [] warn_slowpath_fmt+0x5c/0x80
   [] ? ___ratelimit+0xa2/0xe0
   [] skb_warn_bad_offload+0xd1/0x120
   [] __skb_gso_segment+0xfd/0x110
   [] validate_xmit_skb.isra.97.part.98+0x10d/0x2b0
   [] __dev_queue_xmit+0x582/0x590
   [] dev_queue_xmit+0x10/0x20
   [] vlan_dev_hard_start_xmit+0x98/0x120 [8021q]
   [] dev_hard_start_xmit+0x249/0x3d0
   [] __dev_queue_xmit+0x526/0x590
   [] dev_queue_xmit+0x10/0x20
   [] br_dev_queue_push_xmit+0x7a/0x140 [bridge]
   [] br_forward_finish+0x3d/0xb0 [bridge]
   [] ? br_handle_frame_finish+0x3a0/0x620 [bridge]
   [] __br_forward+0xa6/0x130 [bridge]
   [] br_forward+0x87/0x90 [bridge]
   [] br_handle_frame_finish+0x3a0/0x620 [bridge]
   [] ? __netif_receive_skb_core+0x364/0xa60
   [] ? dev_gro_receive+0x1c0/0x3c0
   [] br_handle_frame+0x174/0x2b0 [bridge]
   [] ? tg3_poll_work+0x4cb/0xf10 [tg3]
   [] ? __netif_receive_skb+0x18/0x60
   [] __netif_receive_skb_core+0x364/0xa60
   [] ? napi_gro_flush+0x5a/0x80
   [] __netif_receive_skb+0x18/0x60
   [] process_backlog+0xa8/0x150
   [] net_rx_action+0x21e/0x360
   [] __do_softirq+0x101/0x290
   [] do_softirq_own_stack+0x1c/0x30
 [] do_softirq.part.19+0x38/0x40
   [] do_softirq+0x1d/0x20
   [] netif_rx_ni+0x33/0x80
   [] tun_get_user+0x506/0x880
   [] tun_chr_write_iter+0x57/0x70
   [] do_iter_readv_writev+0x6c/0xa0
   [] do_readv_writev+0x18f/0x230
   [] vfs_writev+0x39/0x50
   [] SyS_writev+0x59/0xf0
   [] entry_SYSCALL_64_fastpath+0x16/0x71
  ---[ end trace 9fe5c984ff319e6a ]---

  For now this doesn't seem to have any user visible impact but we are
  not paying close attention to latencies/packet losses.

  Discovered in version:  linux-image-4.4.0-93-generic 4.4.0-93.116
  Last known good version: linux-image-4.4.0-92-generic 4.4.0-92.115

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-93-generic 4.4.0-93.116
  ProcVersionSignature: Ubuntu 4.4.0-93.116-generic 4.4.79
  Uname: Linux 4.4.0-93-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Aug 28 12:27 seq
   crw-rw 1 root audio 116, 33 Aug 28 12:27 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: [Errno 2] No such file or directory: 'fuser'
  Date: Tue Aug 29 13:46:12 2017
  HibernationDevice: RESUME=/dev/mapper/vghost-swap
  InstallationDate: Installed on 2017-04-01 (149 days ago)
  InstallationMedia: Ubuntu-Server 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.8)
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb:
   Bus 002 Device 002: ID 8087:8002 Intel Corp. 
   Bus 002 Dev

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

This change was made by a bot.

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

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

Title:
  linux 4.4.0-93 triggers call traces related to the bonding module

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  == Regression details ==

  Since the rolled out 4.4.0-93, we are getting many ~identical call
  traces that look like this:

  [ cut here ]
  WARNING: CPU: 0 PID:  at 
/build/linux-YyUNAI/linux-4.4.0/net/core/dev.c:2445 
skb_warn_bad_offload+0xd1/0x120()
  bond0: caps=(0x0fd97ba9, 0x) len=1487 data_len=0 
gso_size=1440 gso_type=6 ip_summed=0
  Modules linked in: binfmt_misc nf_log_ipv6 nf_conntrack_ipv6 nf_defrag_ipv6 
ip6table_filter ip6_tables nf_log_ipv4 nf_log_common xt_LOG xt_tcpudp 
nf_conntrack_ipv4 nf_defrag_ipv4 xt_owner xt_conntrack nf_conntrack 
iptable_filter ip_tables x_tables 8021q garp mrp bonding ipmi_devintf dcdbas 
intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp crct10dif_pclmul 
ipmi_ssif crc32_pclmul bridge ghash_clmulni_intel stp llc aesni_intel 
aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd vhost_net vhost macvtap 
macvlan sb_edac edac_core kvm_intel kvm ipmi_si 8250_fintek ipmi_msghandler 
lpc_ich irqbypass shpchp mei_me mei acpi_power_meter mac_hid drbd lru_cache 
autofs4 btrfs xor raid6_pq bnx2x mxm_wmi vxlan ip6_udp_tunnel tg3 udp_tunnel 
ahci mdio ptp libcrc32c libahci megaraid_sas pps_core fjes wmi
  CPU: 0 PID:  Comm: qemu-system-x86 Not tainted 4.4.0-93-generic 
#116-Ubuntu
  Hardware name: Dell Inc. PowerEdge R830/0VVT0H, BIOS 1.3.4 11/09/2016
   0286 f5a0655ded96de87 88bd7f2038c0 813f9f83
   88bd7f203908 81d6f780 88bd7f2038f8 810812f2
   88b6e118e000 8a3d17f52000 0006 0081
  Call Trace:
 [] dump_stack+0x63/0x90
   [] warn_slowpath_common+0x82/0xc0
   [] warn_slowpath_fmt+0x5c/0x80
   [] ? ___ratelimit+0xa2/0xe0
   [] skb_warn_bad_offload+0xd1/0x120
   [] __skb_gso_segment+0xfd/0x110
   [] validate_xmit_skb.isra.97.part.98+0x10d/0x2b0
   [] __dev_queue_xmit+0x582/0x590
   [] dev_queue_xmit+0x10/0x20
   [] vlan_dev_hard_start_xmit+0x98/0x120 [8021q]
   [] dev_hard_start_xmit+0x249/0x3d0
   [] __dev_queue_xmit+0x526/0x590
   [] dev_queue_xmit+0x10/0x20
   [] br_dev_queue_push_xmit+0x7a/0x140 [bridge]
   [] br_forward_finish+0x3d/0xb0 [bridge]
   [] ? br_handle_frame_finish+0x3a0/0x620 [bridge]
   [] __br_forward+0xa6/0x130 [bridge]
   [] br_forward+0x87/0x90 [bridge]
   [] br_handle_frame_finish+0x3a0/0x620 [bridge]
   [] ? __netif_receive_skb_core+0x364/0xa60
   [] ? dev_gro_receive+0x1c0/0x3c0
   [] br_handle_frame+0x174/0x2b0 [bridge]
   [] ? tg3_poll_work+0x4cb/0xf10 [tg3]
   [] ? __netif_receive_skb+0x18/0x60
   [] __netif_receive_skb_core+0x364/0xa60
   [] ? napi_gro_flush+0x5a/0x80
   [] __netif_receive_skb+0x18/0x60
   [] process_backlog+0xa8/0x150
   [] net_rx_action+0x21e/0x360
   [] __do_softirq+0x101/0x290
   [] do_softirq_own_stack+0x1c/0x30
 [] do_softirq.part.19+0x38/0x40
   [] do_softirq+0x1d/0x20
   [] netif_rx_ni+0x33/0x80
   [] tun_get_user+0x506/0x880
   [] tun_chr_write_iter+0x57/0x70
   [] do_iter_readv_writev+0x6c/0xa0
   [] do_readv_writev+0x18f/0x230
   [] vfs_writev+0x39/0x50
   [] SyS_writev+0x59/0xf0
   [] entry_SYSCALL_64_fastpath+0x16/0x71
  ---[ end trace 9fe5c984ff319e6a ]---

  For now this doesn't seem to have any user visible impact but we are
  not paying close attention to latencies/packet losses.

  Discovered in version:  linux-image-4.4.0-93-generic 4.4.0-93.116
  Last known good version: linux-image-4.4.0-92-generic 4.4.0-92.115

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-93-generic 4.4.0-93.116
  ProcVersionSignature: Ubuntu 4.4.0-93.116-generic 4.4.79
  Uname: Linux 4.4.0-93-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Aug 28 12:27 seq
   crw-rw 1 root audio 116, 33 Aug 28 12:27 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: [Errno 2] No such file or directory: 'fuser'
  Date: Tue Aug 29 13:46:12 2017
  HibernationDevice: RESUME=/dev/mapper/vghost-swap
  InstallationDate: Installed on 2017-04-01 (149 days ago)
  InstallationMedia: Ubuntu-Server 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.8)
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb:
   Bus 002 Device 002: ID 8087:8002 Intel Corp. 
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 003: ID 413c:a001 Dell Computer Corp. Hub
   Bus 001 Device 002: ID 8087:800a Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002

[Kernel-packages] [Bug 1713787] Re: linux 4.4.0-93 triggers call traces

2017-08-29 Thread Simon Déziel

I'm now seeing similar traces on a wildly different machine that's not
using the bonding module. All machines are KVM hypervisors with
VHOST_NET_ENABLED=1. I'm attaching multiple dmesg extract from 3
machines, 2 PowerEdge R830 and 1 old Core 2 Duo/Xeon.

** Summary changed:

- linux 4.4.0-93 triggers call traces related to the bonding module
+ linux 4.4.0-93 triggers call traces

** Attachment removed: "multiple-dmesg.tgz"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1713787/+attachment/4940943/+files/multiple-dmesg.tgz

** Attachment added: "multiple-dmesg.tgz"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1713787/+attachment/4940999/+files/multiple-dmesg.tgz

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

Title:
  linux 4.4.0-93 triggers call traces

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  == Regression details ==

  Since the rolled out 4.4.0-93, we are getting many ~identical call
  traces that look like this:

  [ cut here ]
  WARNING: CPU: 0 PID:  at 
/build/linux-YyUNAI/linux-4.4.0/net/core/dev.c:2445 
skb_warn_bad_offload+0xd1/0x120()
  bond0: caps=(0x0fd97ba9, 0x) len=1487 data_len=0 
gso_size=1440 gso_type=6 ip_summed=0
  Modules linked in: binfmt_misc nf_log_ipv6 nf_conntrack_ipv6 nf_defrag_ipv6 
ip6table_filter ip6_tables nf_log_ipv4 nf_log_common xt_LOG xt_tcpudp 
nf_conntrack_ipv4 nf_defrag_ipv4 xt_owner xt_conntrack nf_conntrack 
iptable_filter ip_tables x_tables 8021q garp mrp bonding ipmi_devintf dcdbas 
intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp crct10dif_pclmul 
ipmi_ssif crc32_pclmul bridge ghash_clmulni_intel stp llc aesni_intel 
aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd vhost_net vhost macvtap 
macvlan sb_edac edac_core kvm_intel kvm ipmi_si 8250_fintek ipmi_msghandler 
lpc_ich irqbypass shpchp mei_me mei acpi_power_meter mac_hid drbd lru_cache 
autofs4 btrfs xor raid6_pq bnx2x mxm_wmi vxlan ip6_udp_tunnel tg3 udp_tunnel 
ahci mdio ptp libcrc32c libahci megaraid_sas pps_core fjes wmi
  CPU: 0 PID:  Comm: qemu-system-x86 Not tainted 4.4.0-93-generic 
#116-Ubuntu
  Hardware name: Dell Inc. PowerEdge R830/0VVT0H, BIOS 1.3.4 11/09/2016
   0286 f5a0655ded96de87 88bd7f2038c0 813f9f83
   88bd7f203908 81d6f780 88bd7f2038f8 810812f2
   88b6e118e000 8a3d17f52000 0006 0081
  Call Trace:
 [] dump_stack+0x63/0x90
   [] warn_slowpath_common+0x82/0xc0
   [] warn_slowpath_fmt+0x5c/0x80
   [] ? ___ratelimit+0xa2/0xe0
   [] skb_warn_bad_offload+0xd1/0x120
   [] __skb_gso_segment+0xfd/0x110
   [] validate_xmit_skb.isra.97.part.98+0x10d/0x2b0
   [] __dev_queue_xmit+0x582/0x590
   [] dev_queue_xmit+0x10/0x20
   [] vlan_dev_hard_start_xmit+0x98/0x120 [8021q]
   [] dev_hard_start_xmit+0x249/0x3d0
   [] __dev_queue_xmit+0x526/0x590
   [] dev_queue_xmit+0x10/0x20
   [] br_dev_queue_push_xmit+0x7a/0x140 [bridge]
   [] br_forward_finish+0x3d/0xb0 [bridge]
   [] ? br_handle_frame_finish+0x3a0/0x620 [bridge]
   [] __br_forward+0xa6/0x130 [bridge]
   [] br_forward+0x87/0x90 [bridge]
   [] br_handle_frame_finish+0x3a0/0x620 [bridge]
   [] ? __netif_receive_skb_core+0x364/0xa60
   [] ? dev_gro_receive+0x1c0/0x3c0
   [] br_handle_frame+0x174/0x2b0 [bridge]
   [] ? tg3_poll_work+0x4cb/0xf10 [tg3]
   [] ? __netif_receive_skb+0x18/0x60
   [] __netif_receive_skb_core+0x364/0xa60
   [] ? napi_gro_flush+0x5a/0x80
   [] __netif_receive_skb+0x18/0x60
   [] process_backlog+0xa8/0x150
   [] net_rx_action+0x21e/0x360
   [] __do_softirq+0x101/0x290
   [] do_softirq_own_stack+0x1c/0x30
 [] do_softirq.part.19+0x38/0x40
   [] do_softirq+0x1d/0x20
   [] netif_rx_ni+0x33/0x80
   [] tun_get_user+0x506/0x880
   [] tun_chr_write_iter+0x57/0x70
   [] do_iter_readv_writev+0x6c/0xa0
   [] do_readv_writev+0x18f/0x230
   [] vfs_writev+0x39/0x50
   [] SyS_writev+0x59/0xf0
   [] entry_SYSCALL_64_fastpath+0x16/0x71
  ---[ end trace 9fe5c984ff319e6a ]---

  For now this doesn't seem to have any user visible impact but we are
  not paying close attention to latencies/packet losses.

  Discovered in version:  linux-image-4.4.0-93-generic 4.4.0-93.116
  Last known good version: linux-image-4.4.0-92-generic 4.4.0-92.115

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-93-generic 4.4.0-93.116
  ProcVersionSignature: Ubuntu 4.4.0-93.116-generic 4.4.79
  Uname: Linux 4.4.0-93-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Aug 28 12:27 seq
   crw-rw 1 root audio 116, 33 Aug 28 12:27 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: [Errno 2] No such file or directory: 'fuser'
  D

[Kernel-packages] [Bug 1710019] Re: support GICv3 ITS save/restore & migration

2017-08-29 Thread dann frazier

** Patch added: "qemu-zesty-gicv3sr.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1710019/+attachment/4940998/+files/qemu-zesty-gicv3sr.debdiff

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

Title:
  support GICv3 ITS save/restore & migration

Status in linux package in Ubuntu:
  Triaged
Status in qemu package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Won't Fix
Status in qemu source package in Xenial:
  Triaged
Status in linux source package in Zesty:
  Triaged
Status in qemu source package in Zesty:
  In Progress

Bug description:
  [Impact]
  Virtual machines on GICv3-based ARM systems cannot be saved/restored or 
migrated.
  This feature was added in QEMU 2.10.

  [Test Case]
  ubuntu@grotrian:~$ sudo virsh save 7936-0 7936-0.sav

  Domain 7936-0 saved to 7936-0.sav

  ubuntu@grotrian:~$ sudo virsh restore 7396-0.sav
  error: Failed to restore domain from 7396-0.sav
  error: operation failed: job: unexpectedly failed

  ubuntu@grotrian:~$ sudo tail -3 /var/log/libvirt/qemu/7936-0.log 
  2017-08-10T21:26:38.217427Z qemu-system-aarch64: State blocked by 
non-migratable device 'arm_gicv3_its'
  2017-08-10T21:26:38.217565Z qemu-system-aarch64: load of migration failed: 
Invalid argument
  2017-08-10 21:26:38.217+: shutting down, reason=failed

  [Regression Risk]

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

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

[Kernel-packages] [Bug 1710019] Re: support GICv3 ITS save/restore & migration

2017-08-29 Thread Ubuntu Foundations Team Bug Bot

** Tags added: patch

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

Title:
  support GICv3 ITS save/restore & migration

Status in linux package in Ubuntu:
  Triaged
Status in qemu package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Won't Fix
Status in qemu source package in Xenial:
  Triaged
Status in linux source package in Zesty:
  Triaged
Status in qemu source package in Zesty:
  In Progress

Bug description:
  [Impact]
  Virtual machines on GICv3-based ARM systems cannot be saved/restored or 
migrated.
  This feature was added in QEMU 2.10.

  [Test Case]
  ubuntu@grotrian:~$ sudo virsh save 7936-0 7936-0.sav

  Domain 7936-0 saved to 7936-0.sav

  ubuntu@grotrian:~$ sudo virsh restore 7396-0.sav
  error: Failed to restore domain from 7396-0.sav
  error: operation failed: job: unexpectedly failed

  ubuntu@grotrian:~$ sudo tail -3 /var/log/libvirt/qemu/7936-0.log 
  2017-08-10T21:26:38.217427Z qemu-system-aarch64: State blocked by 
non-migratable device 'arm_gicv3_its'
  2017-08-10T21:26:38.217565Z qemu-system-aarch64: load of migration failed: 
Invalid argument
  2017-08-10 21:26:38.217+: shutting down, reason=failed

  [Regression Risk]

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

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

[Kernel-packages] [Bug 1713817] [NEW] package linux-image-4.4.0-93-generic 4.4.0-93.116 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1

2017-08-29 Thread Jose Netto

Public bug reported:

upgrading dell 5888 from 14.04 to 16.04

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-93-generic 4.4.0-93.116
ProcVersionSignature: Ubuntu 3.13.0-129.178-generic 3.13.11-ckt39
Uname: Linux 3.13.0-129-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  vieira 2565 F pulseaudio
 /dev/snd/controlC0:  vieira 2565 F pulseaudio
Date: Tue Aug 29 16:25:13 2017
DistributionChannelDescriptor:
 # This is a distribution channel descriptor
 # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor
 canonical-oem-somerville-trusty-amd64-20140620-0
ErrorMessage: subprocess installed post-installation script returned error exit 
status 2
HibernationDevice: RESUME=UUID=84e4d87b-1933-4fe3-8ec9-f33c2ee0e6c0
InstallationDate: Installed on 2016-08-30 (364 days ago)
InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 
20140620-04:25
MachineType: Dell Inc. Inspiron 5558
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-129-generic 
root=UUID=caaf48b0-872b-4ec4-9b79-ecb5a1215b61 ro quiet splash radeon.modeset=0 
nouveau.modeset=0
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions: grub-pc N/A
SourcePackage: linux
StagingDrivers: rts5139
Title: package linux-image-4.4.0-93-generic 4.4.0-93.116 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
UpgradeStatus: Upgraded to xenial on 2017-08-29 (0 days ago)
dmi.bios.date: 07/12/2016
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A11
dmi.board.name: 0R392V
dmi.board.vendor: Dell Inc.
dmi.board.version: A01
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvrA11:bd07/12/2016:svnDellInc.:pnInspiron5558:pvr01:rvnDellInc.:rn0R392V:rvrA01:cvnDellInc.:ct9:cvr:
dmi.product.name: Inspiron 5558
dmi.product.version: 01
dmi.sys.vendor: Dell Inc.

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


** Tags: amd64 apport-package staging 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/1713817

Title:
  package linux-image-4.4.0-93-generic 4.4.0-93.116 failed to
  install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools
  exited with return code 1

Status in linux package in Ubuntu:
  New

Bug description:
  upgrading dell 5888 from 14.04 to 16.04

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-93-generic 4.4.0-93.116
  ProcVersionSignature: Ubuntu 3.13.0-129.178-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-129-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  vieira 2565 F pulseaudio
   /dev/snd/controlC0:  vieira 2565 F pulseaudio
  Date: Tue Aug 29 16:25:13 2017
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-trusty-amd64-20140620-0
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 2
  HibernationDevice: RESUME=UUID=84e4d87b-1933-4fe3-8ec9-f33c2ee0e6c0
  InstallationDate: Installed on 2016-08-30 (364 days ago)
  InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 
20140620-04:25
  MachineType: Dell Inc. Inspiron 5558
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-129-generic 
root=UUID=caaf48b0-872b-4ec4-9b79-ecb5a1215b61 ro quiet splash radeon.modeset=0 
nouveau.modeset=0
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc N/A
  SourcePackage: linux
  StagingDrivers: rts5139
  Title: package linux-image-4.4.0-93-generic 4.4.0-93.116 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  UpgradeStatus: Upgraded to xenial on 2017-08-29 (0 days ago)
  dmi.bios.date: 07/12/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A11
  dmi.board.name: 0R392V
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA11:bd07/12/2016:svnDellInc.:pnInspiron5558:pvr01:rvnDellInc.:rn0R392V:rvrA01:cvnDellInc.:ct9:cvr:
  dmi.product.name: Inspiron 5558
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1713817] Re: package linux-image-4.4.0-93-generic 4.4.0-93.116 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1

2017-08-29 Thread Apport retracing service

** Tags removed: need-duplicate-check

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

Title:
  package linux-image-4.4.0-93-generic 4.4.0-93.116 failed to
  install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools
  exited with return code 1

Status in linux package in Ubuntu:
  New

Bug description:
  upgrading dell 5888 from 14.04 to 16.04

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-93-generic 4.4.0-93.116
  ProcVersionSignature: Ubuntu 3.13.0-129.178-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-129-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  vieira 2565 F pulseaudio
   /dev/snd/controlC0:  vieira 2565 F pulseaudio
  Date: Tue Aug 29 16:25:13 2017
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-trusty-amd64-20140620-0
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 2
  HibernationDevice: RESUME=UUID=84e4d87b-1933-4fe3-8ec9-f33c2ee0e6c0
  InstallationDate: Installed on 2016-08-30 (364 days ago)
  InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 
20140620-04:25
  MachineType: Dell Inc. Inspiron 5558
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-129-generic 
root=UUID=caaf48b0-872b-4ec4-9b79-ecb5a1215b61 ro quiet splash radeon.modeset=0 
nouveau.modeset=0
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc N/A
  SourcePackage: linux
  StagingDrivers: rts5139
  Title: package linux-image-4.4.0-93-generic 4.4.0-93.116 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  UpgradeStatus: Upgraded to xenial on 2017-08-29 (0 days ago)
  dmi.bios.date: 07/12/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A11
  dmi.board.name: 0R392V
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA11:bd07/12/2016:svnDellInc.:pnInspiron5558:pvr01:rvnDellInc.:rn0R392V:rvrA01:cvnDellInc.:ct9:cvr:
  dmi.product.name: Inspiron 5558
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1713770] [NEW] USN-3405-1 kernel cause kernel panic when using mandos

2017-08-29 Thread Launchpad Bug Tracker

You have been subscribed to a public bug:

When mandos is installed, kernel panics and doesn't get password from
mandos server.  Since it happens so early in the boot, the panic isn't
in the logs.  On machine that don't have mandos installed, kernel boots
fine.  The linux-image-4.4.0-92-generic kernel works fine.

sorry, I had to say I didn't know which package is was in order to
submit the bug report, it's linux-image-4.4.0-93-generic.

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


** Tags: bot-comment
-- 
USN-3405-1 kernel cause kernel panic when using mandos
https://bugs.launchpad.net/bugs/1713770
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to linux in Ubuntu.

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

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