[Kernel-packages] [Bug 1722109] Re: iwlwifi regression in artful - intermittent total packet loss

2017-12-07 Thread Bryan Petty
I upgraded my Dell 5520 laptop from Zesty to Artful over a month ago
now, and I'm seeing behavior pretty much exactly as described by Max,
starting immediately after the upgrade. I've been stuck either plugging
into my wired ethernet adapter, tethering with my phone, or just living
without connectivity because the wifi connection has been so unreliable.
Sometimes (frequently right after a clean boot) it works just fine, and
I'm having no problems meeting sustained, reliable, fast speeds for
maybe a minute, but it breaks down pretty quickly (sometimes even just
after just 10 to 15 seconds after wifi connects), and I see nothing but
long windows of 100% packet loss. If I monitor long enough, it seems to
recover for a brief window of time, but pretty quickly goes right back
to 100% packet loss (in windows of maybe 30 seconds to a few minutes).

This has been observed even today with the latest 4.13.0-19-generic
kernel.

For the first week or two after the upgrade, I've been trying to
determine if it was just limited to specific access points I was using,
but I've observed this same behavior while connected to 3 different
locations, with 3 wildly different wifi systems.

I also thought it might be the wifi adapter drivers in a kernel upgrade
(this laptop has a builtin Intel Wireless 8265 card, using iwlwifi), so
I picked up an Archer T4UH V2 (based on the Realtek RTL8812AU chipset)
just in case using a different wifi driver would be enough to have
working wifi again, but I'm seeing the same behavior with that adapter
as well.

So it certainly seems related to wifi functionality only, but also not
driver specific.

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

Title:
  iwlwifi regression in artful - intermittent total packet loss

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Recently I have been experiencing intermitted total packet loss over
  wifi.

  I've already been looking at another issue in which Bluetooth
  coexistence seems to be causing controller hardware to crash - bug
  1719210 - so I'm rather suspicious of the updated iwlwifi microcode
  that is used by newer kernel versions.

  Unfortunately, I don't have a good reproduction recipe, as the fault
  doesn't seem to occur immediately after boot, nor is it an absolute
  failure of connectivity - from a user perspective, it feels like, for
  example, the website you are using is responding exceptionally slowly.
  It is only on testing multiple remote sites, and finding that
  rebooting into an earlier kernel fixes the issue, that it is apparent
  that it's a local OS problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-12-generic 4.13.0-12.13
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  ApportVersion: 2.20.7-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  maxb   1859 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct  8 19:10:31 2017
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=635db8ca-b352-4622-87eb-08f74460324b
  InstallationDate: Installed on 2016-08-16 (418 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: HP HP Spectre Notebook
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-12-generic 
root=UUID=4989886a-f95e-4802-ab51-dcbf53167aeb ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-12-generic N/A
   linux-backports-modules-4.13.0-12-generic  N/A
   linux-firmware 1.169
  SourcePackage: linux
  UpgradeStatus: Upgraded to artful on 2017-08-31 (37 days ago)
  dmi.bios.date: 02/21/2017
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.31
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 81A0
  dmi.board.vendor: HP
  dmi.board.version: 48.54
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.31:bd02/21/2017:svnHP:pnHPSpectreNotebook:pvrType1ProductConfigId:rvnHP:rn81A0:rvr48.54:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP S=SPT
  dmi.product.name: HP Spectre Notebook
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP

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

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


[Kernel-packages] [Bug 1737103] [NEW] Bluetooth devices list is not shown. When bluetooth is turned on, only "searching for devices..." dialogues shows and no device is recognised.

2017-12-07 Thread Maliha Binte Nur
Public bug reported:

Release:17.10
bluetooth:
  Installed: (none)
  Candidate: 5.46-0ubuntu3
  Version table:
 5.46-0ubuntu3 500
500 http://bd.archive.ubuntu.com/ubuntu artful/universe amd64 Packages
500 http://bd.archive.ubuntu.com/ubuntu artful/universe i386 Packages


When bluetooth is turned on, only "searching for devices..." dialogue shows and 
no device is recognised.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: bluetooth (not installed)
ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
Uname: Linux 4.13.0-17-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.7-0ubuntu3.6
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Fri Dec  8 11:45:42 2017
InstallationDate: Installed on 2017-10-07 (61 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
InterestingModules: rfcomm bnep btusb bluetooth
MachineType: ASUSTeK COMPUTER INC. X555LNB
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-17-generic.efi.signed 
root=UUID=9e3fdf07-9929-4ebb-ba34-39a7bec3d779 ro quiet splash vt.handoff=7
SourcePackage: bluez
UpgradeStatus: Upgraded to artful on 2017-12-03 (4 days ago)
dmi.bios.date: 12/19/2014
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: X555LNB.303
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: X555LNB
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX555LNB.303:bd12/19/2014:svnASUSTeKCOMPUTERINC.:pnX555LNB:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX555LNB:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.family: X
dmi.product.name: X555LNB
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.
hciconfig:
 hci0:  Type: Primary  Bus: USB
BD Address: B8:86:87:94:B4:76  ACL MTU: 1021:8  SCO MTU: 64:1
UP RUNNING PSCAN ISCAN 
RX bytes:5659 acl:0 sco:0 events:675 errors:0
TX bytes:9566 acl:0 sco:0 commands:594 errors:0

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


** Tags: amd64 apport-bug artful wayland-session

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

Title:
  Bluetooth devices list is not shown. When bluetooth is turned on, only
  "searching for devices..." dialogues shows and no device is
  recognised.

Status in bluez package in Ubuntu:
  New

Bug description:
  Release:  17.10
  bluetooth:
Installed: (none)
Candidate: 5.46-0ubuntu3
Version table:
   5.46-0ubuntu3 500
  500 http://bd.archive.ubuntu.com/ubuntu artful/universe amd64 Packages
  500 http://bd.archive.ubuntu.com/ubuntu artful/universe i386 Packages

  
  When bluetooth is turned on, only "searching for devices..." dialogue shows 
and no device is recognised.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: bluetooth (not installed)
  ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
  Uname: Linux 4.13.0-17-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.7-0ubuntu3.6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Dec  8 11:45:42 2017
  InstallationDate: Installed on 2017-10-07 (61 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: ASUSTeK COMPUTER INC. X555LNB
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-17-generic.efi.signed 
root=UUID=9e3fdf07-9929-4ebb-ba34-39a7bec3d779 ro quiet splash vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: Upgraded to artful on 2017-12-03 (4 days ago)
  dmi.bios.date: 12/19/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X555LNB.303
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X555LNB
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX555LNB.303:bd12/19/2014:svnASUSTeKCOMPUTERINC.:pnX555LNB:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX555LNB:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: X
  dmi.product.name: X555LNB
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: B8:86:87:94:B4:76  ACL MTU: 1021:8  SCO MTU: 64:1
UP RUNNING PSCAN ISCAN 
RX bytes:5659 acl:0 sco:0 events:675 errors:0
TX bytes:9566 acl:0 sco:0 commands:594 errors:0

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

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

[Kernel-packages] [Bug 1712858] Re: system freezes occasionally for several minutes

2017-12-07 Thread Launchpad Bug Tracker
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  system freezes occasionally for several minutes

Status in linux package in Ubuntu:
  Expired
Status in pulseaudio package in Ubuntu:
  Expired

Bug description:
  Occasionally, the system freezes: display does not show mouse move,
  clock display does not update itself, ssh impossible. But the machine
  remains pingable. This lasts for 2 to 20 minutes.

  This is with Ubuntu 16.04.2, now upgraded to kernel version
  4.8.0-46-generic.

  At the end of the freeze, a bunch of messages get written to
  /var/log/syslog. Examples:

  Aug 19 00:03:48 quimper rtkit-daemon[2276]: The canary thread is apparently 
starving. Taking action.
  Aug 19 00:03:48 quimper rtkit-daemon[2276]: Demoting known real-time threads.
  Aug 19 00:03:48 quimper rtkit-daemon[2276]: Successfully demoted thread 2607 
of process 2275 (n/a).
  Aug 19 00:03:48 quimper rtkit-daemon[2276]: Successfully demoted thread 2606 
of process 2275 (n/a).
  Aug 19 00:03:48 quimper rtkit-daemon[2276]: Successfully demoted thread 2604 
of process 2275 (n/a).
  Aug 19 00:03:48 quimper rtkit-daemon[2276]: Successfully demoted thread 2275 
of process 2275 (n/a).
  Aug 19 00:03:48 quimper rtkit-daemon[2276]: Demoted 4 threads.

  Aug 19 08:06:19 quimper rtkit-daemon[2276]: The canary thread is apparently 
starving. Taking action.
  Aug 19 08:06:19 quimper rtkit-daemon[2276]: Demoting known real-time threads.
  Aug 19 08:06:19 quimper rtkit-daemon[2276]: Successfully demoted thread 2607 
of process 2275 (n/a).
  Aug 19 08:06:19 quimper rtkit-daemon[2276]: Successfully demoted thread 2606 
of process 2275 (n/a).
  Aug 19 08:06:19 quimper rtkit-daemon[2276]: Successfully demoted thread 2604 
of process 2275 (n/a).
  Aug 19 08:06:19 quimper rtkit-daemon[2276]: Successfully demoted thread 2275 
of process 2275 (n/a).
  Aug 19 08:06:19 quimper rtkit-daemon[2276]: Demoted 4 threads.
  Aug 19 08:06:20 quimper systemd[1]: systemd-udevd.service: Watchdog timeout 
(limit 3min)!
  Aug 19 08:06:20 quimper systemd[1]: systemd-udevd.service: Main process 
exited, code=killed, status=6/ABRT
  Aug 19 08:06:20 quimper systemd[1]: systemd-udevd.service: Unit entered 
failed state.
  Aug 19 08:06:20 quimper systemd[1]: systemd-udevd.service: Failed with result 
'signal'.
  Aug 19 08:06:20 quimper systemd[1]: systemd-udevd.service: Service has no 
hold-off time, scheduling restart.
  Aug 19 08:06:20 quimper systemd[1]: Stopped udev Kernel Device Manager.
  Aug 19 08:06:20 quimper systemd[1]: Starting udev Kernel Device Manager...
  Aug 19 08:06:24 quimper systemd[1]: Started udev Kernel Device Manager.

  Aug 19 15:04:55 quimper rtkit-daemon[2276]: The canary thread is apparently 
starving. Taking action.
  Aug 19 15:04:55 quimper rtkit-daemon[2276]: Demoting known real-time threads.
  Aug 19 15:04:55 quimper rtkit-daemon[2276]: Successfully demoted thread 2607 
of process 2275 (n/a).
  Aug 19 15:04:55 quimper rtkit-daemon[2276]: Successfully demoted thread 2606 
of process 2275 (n/a).
  Aug 19 15:04:55 quimper rtkit-daemon[2276]: Successfully demoted thread 2604 
of process 2275 (n/a).
  Aug 19 15:04:55 quimper rtkit-daemon[2276]: Successfully demoted thread 2275 
of process 2275 (n/a).
  Aug 19 15:04:55 quimper rtkit-daemon[2276]: Demoted 4 threads.
  Aug 19 15:04:55 quimper systemd[1]: systemd-timesyncd.service: Watchdog 
timeout (limit 3min)!
  Aug 19 15:04:59 quimper systemd[1]: systemd-timesyncd.service: Main process 
exited, code=killed, status=6/ABRT
  Aug 19 15:04:59 quimper systemd[1]: systemd-timesyncd.service: Unit entered 
failed state.
  Aug 19 15:04:59 quimper systemd[1]: systemd-timesyncd.service: Failed with 
result 'signal'.
  Aug 19 15:05:00 quimper systemd[1]: systemd-timesyncd.service: Service has no 
hold-off time, scheduling restart.
  Aug 19 15:05:00 quimper systemd[1]: Stopped Network Time Synchronization.
  Aug 19 15:05:00 quimper systemd[1]: Starting Network Time Synchronization...
  Aug 19 15:05:00 quimper systemd[1]: Started Network Time Synchronization.
  Aug 19 15:05:00 quimper systemd-timesyncd[26894]: Synchronized to time server 
91.189.89.198:123 (ntp.ubuntu.com).

  Aug 20 06:03:28 quimper rtkit-daemon[2276]: The canary thread is apparently 
starving. Taking action.
  Aug 20 06:03:28 quimper rtkit-daemon[2276]: Demoting known real-time threads.
  Aug 20 06:03:28 quimper rtkit-daemon[2276]: Successfully demoted thread 2607 
of process 2275 (n/a).
  Aug 20 06:03:28 quimper rtkit-daemon[2276]: Successfully demoted thread 2606 
of process 2275 (n/a).
  Aug 20 06:03:28 quimper rtkit-daemon[2276]: Successfully demoted thread 2604 
of process 2275 (n/a).
  Aug 20 06:03:28 quimper rtkit-daemon[2276]: Successfully demoted thread 2275 
of 

[Kernel-packages] [Bug 1712858] Re: system freezes occasionally for several minutes

2017-12-07 Thread Launchpad Bug Tracker
[Expired for pulseaudio (Ubuntu) because there has been no activity for
60 days.]

** Changed in: pulseaudio (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  system freezes occasionally for several minutes

Status in linux package in Ubuntu:
  Expired
Status in pulseaudio package in Ubuntu:
  Expired

Bug description:
  Occasionally, the system freezes: display does not show mouse move,
  clock display does not update itself, ssh impossible. But the machine
  remains pingable. This lasts for 2 to 20 minutes.

  This is with Ubuntu 16.04.2, now upgraded to kernel version
  4.8.0-46-generic.

  At the end of the freeze, a bunch of messages get written to
  /var/log/syslog. Examples:

  Aug 19 00:03:48 quimper rtkit-daemon[2276]: The canary thread is apparently 
starving. Taking action.
  Aug 19 00:03:48 quimper rtkit-daemon[2276]: Demoting known real-time threads.
  Aug 19 00:03:48 quimper rtkit-daemon[2276]: Successfully demoted thread 2607 
of process 2275 (n/a).
  Aug 19 00:03:48 quimper rtkit-daemon[2276]: Successfully demoted thread 2606 
of process 2275 (n/a).
  Aug 19 00:03:48 quimper rtkit-daemon[2276]: Successfully demoted thread 2604 
of process 2275 (n/a).
  Aug 19 00:03:48 quimper rtkit-daemon[2276]: Successfully demoted thread 2275 
of process 2275 (n/a).
  Aug 19 00:03:48 quimper rtkit-daemon[2276]: Demoted 4 threads.

  Aug 19 08:06:19 quimper rtkit-daemon[2276]: The canary thread is apparently 
starving. Taking action.
  Aug 19 08:06:19 quimper rtkit-daemon[2276]: Demoting known real-time threads.
  Aug 19 08:06:19 quimper rtkit-daemon[2276]: Successfully demoted thread 2607 
of process 2275 (n/a).
  Aug 19 08:06:19 quimper rtkit-daemon[2276]: Successfully demoted thread 2606 
of process 2275 (n/a).
  Aug 19 08:06:19 quimper rtkit-daemon[2276]: Successfully demoted thread 2604 
of process 2275 (n/a).
  Aug 19 08:06:19 quimper rtkit-daemon[2276]: Successfully demoted thread 2275 
of process 2275 (n/a).
  Aug 19 08:06:19 quimper rtkit-daemon[2276]: Demoted 4 threads.
  Aug 19 08:06:20 quimper systemd[1]: systemd-udevd.service: Watchdog timeout 
(limit 3min)!
  Aug 19 08:06:20 quimper systemd[1]: systemd-udevd.service: Main process 
exited, code=killed, status=6/ABRT
  Aug 19 08:06:20 quimper systemd[1]: systemd-udevd.service: Unit entered 
failed state.
  Aug 19 08:06:20 quimper systemd[1]: systemd-udevd.service: Failed with result 
'signal'.
  Aug 19 08:06:20 quimper systemd[1]: systemd-udevd.service: Service has no 
hold-off time, scheduling restart.
  Aug 19 08:06:20 quimper systemd[1]: Stopped udev Kernel Device Manager.
  Aug 19 08:06:20 quimper systemd[1]: Starting udev Kernel Device Manager...
  Aug 19 08:06:24 quimper systemd[1]: Started udev Kernel Device Manager.

  Aug 19 15:04:55 quimper rtkit-daemon[2276]: The canary thread is apparently 
starving. Taking action.
  Aug 19 15:04:55 quimper rtkit-daemon[2276]: Demoting known real-time threads.
  Aug 19 15:04:55 quimper rtkit-daemon[2276]: Successfully demoted thread 2607 
of process 2275 (n/a).
  Aug 19 15:04:55 quimper rtkit-daemon[2276]: Successfully demoted thread 2606 
of process 2275 (n/a).
  Aug 19 15:04:55 quimper rtkit-daemon[2276]: Successfully demoted thread 2604 
of process 2275 (n/a).
  Aug 19 15:04:55 quimper rtkit-daemon[2276]: Successfully demoted thread 2275 
of process 2275 (n/a).
  Aug 19 15:04:55 quimper rtkit-daemon[2276]: Demoted 4 threads.
  Aug 19 15:04:55 quimper systemd[1]: systemd-timesyncd.service: Watchdog 
timeout (limit 3min)!
  Aug 19 15:04:59 quimper systemd[1]: systemd-timesyncd.service: Main process 
exited, code=killed, status=6/ABRT
  Aug 19 15:04:59 quimper systemd[1]: systemd-timesyncd.service: Unit entered 
failed state.
  Aug 19 15:04:59 quimper systemd[1]: systemd-timesyncd.service: Failed with 
result 'signal'.
  Aug 19 15:05:00 quimper systemd[1]: systemd-timesyncd.service: Service has no 
hold-off time, scheduling restart.
  Aug 19 15:05:00 quimper systemd[1]: Stopped Network Time Synchronization.
  Aug 19 15:05:00 quimper systemd[1]: Starting Network Time Synchronization...
  Aug 19 15:05:00 quimper systemd[1]: Started Network Time Synchronization.
  Aug 19 15:05:00 quimper systemd-timesyncd[26894]: Synchronized to time server 
91.189.89.198:123 (ntp.ubuntu.com).

  Aug 20 06:03:28 quimper rtkit-daemon[2276]: The canary thread is apparently 
starving. Taking action.
  Aug 20 06:03:28 quimper rtkit-daemon[2276]: Demoting known real-time threads.
  Aug 20 06:03:28 quimper rtkit-daemon[2276]: Successfully demoted thread 2607 
of process 2275 (n/a).
  Aug 20 06:03:28 quimper rtkit-daemon[2276]: Successfully demoted thread 2606 
of process 2275 (n/a).
  Aug 20 06:03:28 quimper rtkit-daemon[2276]: Successfully demoted thread 2604 
of process 2275 (n/a).
  Aug 20 06:03:28 quimper rtkit-daemon[2276]: Successfully demoted thread 

[Kernel-packages] [Bug 1737033] Re: upgrading linux-image package to 4.4.0-103.126 breaks Ceph network file system connection

2017-12-07 Thread Po-Hsu Lin
Good to know, thanks!
We do have some ceph related change from 4.4.0-101 to 4.4.0-103
https://launchpad.net/ubuntu/+source/linux/4.4.0-103.126

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

Title:
  upgrading linux-image package to 4.4.0-103.126 breaks Ceph network
  file system connection

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

Bug description:
  After clients have upgraded to 4.4.0-103.126 they can no longer
  connect to the Ceph network.

  Using the Grub menu to boot the previous kernel fixes the issue.

  The error in dmesg is:

  [   46.811897] FS-Cache: Loaded
  [   46.843670] Key type ceph registered
  [   46.844177] libceph: loaded (mon/osd proto 15/24)
  [   46.863107] FS-Cache: Netfs 'ceph' registered for caching
  [   46.863116] ceph: loaded (mds proto 32)
  [   46.884392] libceph: client3354099 fsid 
2efbeab1-4903-4c4c-8365-6778afecbcbd
  [   46.886856] libceph: mon0 10.10.2.111:6789 session established
  [   46.897487] ceph: problem parsing mds trace -5
  [   46.897491] ceph: mds parse_reply err -5
  [   46.897492] ceph: mdsc_handle_reply got corrupt reply mds0(tid:1)

  All clients are running ceph client version:
  ii  ceph-fs-common10.2.9-0ubuntu0.16.04.1

  Server nodes are running 10.2.6 packages as supplied by Ceph.

  All 10.2.* versions are compatible. Using the previous kernel allows the 
connection to work.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.14
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  lightdm1310 F pulseaudio
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=9e3c38ba-10bd-4183-b073-68d9d9a30a9b
  IwConfig: Error: [Errno 2] No such file or directory
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: innotek GmbH VirtualBox
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US
   SHELL=/bin/bash
  ProcFB: 0 vboxdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-103-generic 
root=UUID=5a37e891-beb9-477f-b934-3c05651acf68 ro quiet splash
  ProcVersionSignature: Ubuntu 4.4.0-103.126-generic 4.4.98
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-103-generic N/A
   linux-backports-modules-4.4.0-103-generic  N/A
   linux-firmware 1.157.14
  RfKill:
   
  Tags:  xenial xenial
  Uname: Linux 4.4.0-103-generic x86_64
  UnreportableReason: The report belongs to a package that is not installed.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: False
  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/ceph/+bug/1737033/+subscriptions

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


[Kernel-packages] [Bug 1737033] Re: upgrading linux-image package to 4.4.0-103.126 breaks Ceph network file system connection

2017-12-07 Thread Benjamin Long
4.4.0-101 is the one they upgraded from. I'm not seeing 4.4.0.102
anywhere. It's not in the available package list of the machine I'm in
front of right now.

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

Title:
  upgrading linux-image package to 4.4.0-103.126 breaks Ceph network
  file system connection

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

Bug description:
  After clients have upgraded to 4.4.0-103.126 they can no longer
  connect to the Ceph network.

  Using the Grub menu to boot the previous kernel fixes the issue.

  The error in dmesg is:

  [   46.811897] FS-Cache: Loaded
  [   46.843670] Key type ceph registered
  [   46.844177] libceph: loaded (mon/osd proto 15/24)
  [   46.863107] FS-Cache: Netfs 'ceph' registered for caching
  [   46.863116] ceph: loaded (mds proto 32)
  [   46.884392] libceph: client3354099 fsid 
2efbeab1-4903-4c4c-8365-6778afecbcbd
  [   46.886856] libceph: mon0 10.10.2.111:6789 session established
  [   46.897487] ceph: problem parsing mds trace -5
  [   46.897491] ceph: mds parse_reply err -5
  [   46.897492] ceph: mdsc_handle_reply got corrupt reply mds0(tid:1)

  All clients are running ceph client version:
  ii  ceph-fs-common10.2.9-0ubuntu0.16.04.1

  Server nodes are running 10.2.6 packages as supplied by Ceph.

  All 10.2.* versions are compatible. Using the previous kernel allows the 
connection to work.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.14
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  lightdm1310 F pulseaudio
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=9e3c38ba-10bd-4183-b073-68d9d9a30a9b
  IwConfig: Error: [Errno 2] No such file or directory
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: innotek GmbH VirtualBox
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US
   SHELL=/bin/bash
  ProcFB: 0 vboxdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-103-generic 
root=UUID=5a37e891-beb9-477f-b934-3c05651acf68 ro quiet splash
  ProcVersionSignature: Ubuntu 4.4.0-103.126-generic 4.4.98
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-103-generic N/A
   linux-backports-modules-4.4.0-103-generic  N/A
   linux-firmware 1.157.14
  RfKill:
   
  Tags:  xenial xenial
  Uname: Linux 4.4.0-103-generic x86_64
  UnreportableReason: The report belongs to a package that is not installed.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: False
  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/ceph/+bug/1737033/+subscriptions

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


[Kernel-packages] [Bug 1737033] Re: upgrading linux-image package to 4.4.0-103.126 breaks Ceph network file system connection

2017-12-07 Thread Po-Hsu Lin
Hello,
for the "previous kernel", do you mean 4.4.0-102 or 4.4.0-101?
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/1737033

Title:
  upgrading linux-image package to 4.4.0-103.126 breaks Ceph network
  file system connection

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

Bug description:
  After clients have upgraded to 4.4.0-103.126 they can no longer
  connect to the Ceph network.

  Using the Grub menu to boot the previous kernel fixes the issue.

  The error in dmesg is:

  [   46.811897] FS-Cache: Loaded
  [   46.843670] Key type ceph registered
  [   46.844177] libceph: loaded (mon/osd proto 15/24)
  [   46.863107] FS-Cache: Netfs 'ceph' registered for caching
  [   46.863116] ceph: loaded (mds proto 32)
  [   46.884392] libceph: client3354099 fsid 
2efbeab1-4903-4c4c-8365-6778afecbcbd
  [   46.886856] libceph: mon0 10.10.2.111:6789 session established
  [   46.897487] ceph: problem parsing mds trace -5
  [   46.897491] ceph: mds parse_reply err -5
  [   46.897492] ceph: mdsc_handle_reply got corrupt reply mds0(tid:1)

  All clients are running ceph client version:
  ii  ceph-fs-common10.2.9-0ubuntu0.16.04.1

  Server nodes are running 10.2.6 packages as supplied by Ceph.

  All 10.2.* versions are compatible. Using the previous kernel allows the 
connection to work.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.14
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  lightdm1310 F pulseaudio
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=9e3c38ba-10bd-4183-b073-68d9d9a30a9b
  IwConfig: Error: [Errno 2] No such file or directory
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: innotek GmbH VirtualBox
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US
   SHELL=/bin/bash
  ProcFB: 0 vboxdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-103-generic 
root=UUID=5a37e891-beb9-477f-b934-3c05651acf68 ro quiet splash
  ProcVersionSignature: Ubuntu 4.4.0-103.126-generic 4.4.98
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-103-generic N/A
   linux-backports-modules-4.4.0-103-generic  N/A
   linux-firmware 1.157.14
  RfKill:
   
  Tags:  xenial xenial
  Uname: Linux 4.4.0-103-generic x86_64
  UnreportableReason: The report belongs to a package that is not installed.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: False
  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/ceph/+bug/1737033/+subscriptions

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


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

2017-12-07 Thread bugproxy
--- Comment From y...@cn.ibm.com 2017-12-07 20:44 EDT---
(In reply to comment #7)
> The kernel in use (4.4.0.45) is quite outdated and roughly a year old:
> https://launchpad.net/ubuntu/xenial/s390x/linux-generic
> Please check if the problem also exists with latest kernel 4.4
> (like today 4.4.0.101.106 or soon newer ...)

OK. We will update the system at a proper time window. We cannot reboot
they system recently. I will update it here when it's done. 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/1734691

Title:
  Got disk i/o failure when vary cpu offline via chcpu command (Ubuntu
  running on LPAR)

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

Bug description:
  Got disk i/o failure when offline CPU via chcpu command
   
  ---uname output---
  4.4.0-45-generic #66-Ubuntu
   
  Machine Type = z13 - 2964 
   
  ---Debugger---
  A debugger is not configured
   
  Contact Information = y...@cn.ibm.com 
   
  Stack trace output:
   no
   
  Oops output:
   no
   
  System Dump Info:
The system is not configured to capture a system dump.
   
  -Attach sysctl -a output output to the bug.

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

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


[Kernel-packages] [Bug 1724232] Re: sysfs: cannot create duplicate filename '/devices/pci0000:00/0000:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:256'

2017-12-07 Thread Alexandre Bourget
Hitting this with 4.13.0-17-generic

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

Title:
  sysfs: cannot create duplicate filename
  '/devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:256'

Status in linux package in Ubuntu:
  Triaged

Bug description:
  [Impact]

  bluetooth can not be used. 
  Steps to reproduce:

  - Connect bluetooth headset
  - Wait a few minutes, switch profile

  Result:

  - The bluetooth device is disconnected and the following traces are
  printed in dmesg

  [  104.514539] Bluetooth: hci0 SCO packet for unknown connection handle 0
  [  104.514544] Bluetooth: hci0 SCO packet for unknown connection handle 0
  [  104.524525] Bluetooth: hci0 SCO packet for unknown connection handle 0
  [  104.524530] Bluetooth: hci0 SCO packet for unknown connection handle 0
  [  104.524531] Bluetooth: hci0 SCO packet for unknown connection handle 0
  [  106.587815] Bluetooth: hci0 SCO packet for unknown connection handle 258
  [  133.101575] sysfs: cannot create duplicate filename 
'/devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:256'
  [  133.101593] [ cut here ]
  [  133.101603] WARNING: CPU: 1 PID: 382 at 
/build/linux-XO_uEE/linux-4.13.0/fs/sysfs/dir.c:31 sysfs_warn_dup+0x56/0x70
  [  133.101605] Modules linked in: cmac rfcomm ccm 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 libcrc32c ipt_REJECT 
nf_reject_ipv4 xt_tcpudp bridge stp llc ebtable_filter ebtables ip6table_filter 
ip6_tables iptable_filter bnep arc4 nls_iso8859_1 snd_hda_codec_hdmi hid_alps 
iwlmvm mac80211 snd_soc_skl snd_hda_codec_realtek snd_soc_skl_ipc 
snd_hda_codec_generic snd_soc_sst_ipc iwlwifi snd_soc_sst_dsp snd_hda_ext_core 
snd_soc_sst_match cfg80211 snd_soc_core rtsx_pci_ms snd_compress memstick 
ac97_bus snd_pcm_dmaengine dell_rbtn dell_laptop dell_smm_hwmon intel_rapl 
x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm irqbypass 
crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc aesni_intel
  [  133.101672]  aes_x86_64 crypto_simd glue_helper cryptd intel_cstate 
intel_rapl_perf serio_raw dell_wmi dell_smbios wmi_bmof dcdbas snd_hda_intel 
snd_usb_audio snd_hda_codec snd_hda_core snd_usbmidi_lib snd_hwdep snd_pcm 
joydev shpchp snd_seq_midi idma64 snd_seq_midi_event virt_dma snd_rawmidi 
snd_seq cdc_mbim cdc_wdm qcserial mei_me mei cdc_ncm usb_wwan usbnet 
snd_seq_device usbserial mii snd_timer intel_lpss_pci snd uvcvideo 
videobuf2_vmalloc videobuf2_memops soundcore videobuf2_v4l2 videobuf2_core 
input_leds videodev media btusb processor_thermal_device btrtl 
intel_pch_thermal intel_soc_dts_iosf hci_uart btbcm serdev btqca btintel 
bluetooth ecdh_generic intel_lpss_acpi intel_lpss int3403_thermal 
int340x_thermal_zone intel_hid int3400_thermal tpm_crb sparse_keymap 
acpi_thermal_rel acpi_als acpi_pad
  [  133.101743]  kfifo_buf mac_hid industrialio parport_pc ppdev lp parport 
ip_tables x_tables autofs4 hid_generic uas usb_storage usbhid i915 i2c_algo_bit 
drm_kms_helper rtsx_pci_sdmmc e1000e syscopyarea sysfillrect sysimgblt 
fb_sys_fops ptp nvme pps_core nvme_core drm rtsx_pci wmi i2c_hid hid video 
pinctrl_sunrisepoint pinctrl_intel
  [  133.101783] CPU: 1 PID: 382 Comm: kworker/u9:1 Not tainted 
4.13.0-16-generic #19-Ubuntu
  [  133.101785] Hardware name: Dell Inc. Latitude 7380/0KK5D1, BIOS 1.6.4 
08/29/2017
  [  133.101815] Workqueue: hci0 hci_rx_work [bluetooth]
  [  133.101818] task: 990d1105 task.stack: ba328203c000
  [  133.101824] RIP: 0010:sysfs_warn_dup+0x56/0x70
  [  133.101827] RSP: 0018:ba328203fb80 EFLAGS: 00010282
  [  133.101829] RAX: 0073 RBX: 990d0dbc8000 RCX: 

  [  133.101831] RDX:  RSI: 990d2e48dc78 RDI: 
990d2e48dc78
  [  133.101833] RBP: ba328203fb98 R08: 0001 R09: 
03ef
  [  133.101834] R10: 0001 R11:  R12: 
990cbafc8060
  [  133.101836] R13: 990d19e8bbb8 R14: 990cbad4aa88 R15: 
990c944c2c50
  [  133.101839] FS:  () GS:990d2e48() 
knlGS:
  [  133.101841] CS:  0010 DS:  ES:  CR0: 80050033
  [  133.101843] CR2: 7f536eb7000c CR3: 0002ec209000 CR4: 
003406e0
  [  133.101845] DR0:  DR1:  DR2: 

  [  133.101846] DR3:  DR6: fffe0ff0 DR7: 
0400
  [  133.101848] Call Trace:
  [  133.101855]  sysfs_create_dir_ns+0x77/0x90
  [  133.101861]  kobject_add_internal+0xac/0x2b0
  [  133.101864]  kobject_add+0x71/0xd0
  [  133.101871]  ? kfree_const+0x20/0x30
  [  133.101878]  device_add+0x12c/0x680
  [  133.101907]  hci_conn_add_sysfs+0x49/0xc0 [bluetooth]
  [  133.101932]  

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

2017-12-07 Thread matt
apport information

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

Title:
  Lenovo Ideapad320 Touchpad Right Click Not Working

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hello,
   
  I am having issues with my touch pad. The touch pad in general works but it 
will not allow me drag windows or highlight items as well as I cannot right 
click. My Lenovo Ideapad320 is dual booted with Ubuntu 16.04.3 LTS & I believe 
my kernel version is 4.10.0-40-generic. Any ideas/suggestions? On the windows 
side everything works fine. Also external mouse works fine.

  Thanxxx
  --- 
  ApportVersion: 2.20.1-0ubuntu2.13
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  matukai1739 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=343c6b76-3abe-473f-8fbe-5b5cc8a2c7ce
  InstallationDate: Installed on 2017-12-02 (5 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 003: ID 5986:210f Acer, Inc 
   Bus 001 Device 002: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 80XL
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-40-generic.efi.signed 
root=UUID=6a6efca5-21ea-4048-bb96-a6c8a8c966f3 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.10.0-40.44~16.04.1-generic 4.10.17
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-40-generic N/A
   linux-backports-modules-4.10.0-40-generic  N/A
   linux-firmware 1.157.14
  Tags:  xenial
  Uname: Linux 4.10.0-40-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/31/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 4WCN28WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad 320-15IKB
  dmi.modalias: 
dmi:bvnLENOVO:bvr4WCN28WW:bd08/31/2017:svnLENOVO:pn80XL:pvrLenovoideapad320-15IKB:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoideapad320-15IKB:
  dmi.product.name: 80XL
  dmi.product.version: Lenovo ideapad 320-15IKB
  dmi.sys.vendor: LENOVO

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

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


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

2017-12-07 Thread matt
apport information

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

Title:
  Lenovo Ideapad320 Touchpad Right Click Not Working

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hello,
   
  I am having issues with my touch pad. The touch pad in general works but it 
will not allow me drag windows or highlight items as well as I cannot right 
click. My Lenovo Ideapad320 is dual booted with Ubuntu 16.04.3 LTS & I believe 
my kernel version is 4.10.0-40-generic. Any ideas/suggestions? On the windows 
side everything works fine. Also external mouse works fine.

  Thanxxx
  --- 
  ApportVersion: 2.20.1-0ubuntu2.13
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  matukai1739 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=343c6b76-3abe-473f-8fbe-5b5cc8a2c7ce
  InstallationDate: Installed on 2017-12-02 (5 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 003: ID 5986:210f Acer, Inc 
   Bus 001 Device 002: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 80XL
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-40-generic.efi.signed 
root=UUID=6a6efca5-21ea-4048-bb96-a6c8a8c966f3 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.10.0-40.44~16.04.1-generic 4.10.17
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-40-generic N/A
   linux-backports-modules-4.10.0-40-generic  N/A
   linux-firmware 1.157.14
  Tags:  xenial
  Uname: Linux 4.10.0-40-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/31/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 4WCN28WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad 320-15IKB
  dmi.modalias: 
dmi:bvnLENOVO:bvr4WCN28WW:bd08/31/2017:svnLENOVO:pn80XL:pvrLenovoideapad320-15IKB:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoideapad320-15IKB:
  dmi.product.name: 80XL
  dmi.product.version: Lenovo ideapad 320-15IKB
  dmi.sys.vendor: LENOVO

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

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


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

2017-12-07 Thread matt
apport information

** Attachment added: "ProcInterrupts.txt"
   
https://bugs.launchpad.net/bugs/1737060/+attachment/5019915/+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/1737060

Title:
  Lenovo Ideapad320 Touchpad Right Click Not Working

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hello,
   
  I am having issues with my touch pad. The touch pad in general works but it 
will not allow me drag windows or highlight items as well as I cannot right 
click. My Lenovo Ideapad320 is dual booted with Ubuntu 16.04.3 LTS & I believe 
my kernel version is 4.10.0-40-generic. Any ideas/suggestions? On the windows 
side everything works fine. Also external mouse works fine.

  Thanxxx
  --- 
  ApportVersion: 2.20.1-0ubuntu2.13
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  matukai1739 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=343c6b76-3abe-473f-8fbe-5b5cc8a2c7ce
  InstallationDate: Installed on 2017-12-02 (5 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 003: ID 5986:210f Acer, Inc 
   Bus 001 Device 002: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 80XL
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-40-generic.efi.signed 
root=UUID=6a6efca5-21ea-4048-bb96-a6c8a8c966f3 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.10.0-40.44~16.04.1-generic 4.10.17
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-40-generic N/A
   linux-backports-modules-4.10.0-40-generic  N/A
   linux-firmware 1.157.14
  Tags:  xenial
  Uname: Linux 4.10.0-40-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/31/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 4WCN28WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad 320-15IKB
  dmi.modalias: 
dmi:bvnLENOVO:bvr4WCN28WW:bd08/31/2017:svnLENOVO:pn80XL:pvrLenovoideapad320-15IKB:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoideapad320-15IKB:
  dmi.product.name: 80XL
  dmi.product.version: Lenovo ideapad 320-15IKB
  dmi.sys.vendor: LENOVO

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

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


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

2017-12-07 Thread matt
apport information

** Attachment added: "UdevDb.txt"
   https://bugs.launchpad.net/bugs/1737060/+attachment/5019919/+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/1737060

Title:
  Lenovo Ideapad320 Touchpad Right Click Not Working

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hello,
   
  I am having issues with my touch pad. The touch pad in general works but it 
will not allow me drag windows or highlight items as well as I cannot right 
click. My Lenovo Ideapad320 is dual booted with Ubuntu 16.04.3 LTS & I believe 
my kernel version is 4.10.0-40-generic. Any ideas/suggestions? On the windows 
side everything works fine. Also external mouse works fine.

  Thanxxx
  --- 
  ApportVersion: 2.20.1-0ubuntu2.13
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  matukai1739 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=343c6b76-3abe-473f-8fbe-5b5cc8a2c7ce
  InstallationDate: Installed on 2017-12-02 (5 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 003: ID 5986:210f Acer, Inc 
   Bus 001 Device 002: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 80XL
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-40-generic.efi.signed 
root=UUID=6a6efca5-21ea-4048-bb96-a6c8a8c966f3 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.10.0-40.44~16.04.1-generic 4.10.17
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-40-generic N/A
   linux-backports-modules-4.10.0-40-generic  N/A
   linux-firmware 1.157.14
  Tags:  xenial
  Uname: Linux 4.10.0-40-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/31/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 4WCN28WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad 320-15IKB
  dmi.modalias: 
dmi:bvnLENOVO:bvr4WCN28WW:bd08/31/2017:svnLENOVO:pn80XL:pvrLenovoideapad320-15IKB:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoideapad320-15IKB:
  dmi.product.name: 80XL
  dmi.product.version: Lenovo ideapad 320-15IKB
  dmi.sys.vendor: LENOVO

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

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


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

2017-12-07 Thread matt
apport information

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

Title:
  Lenovo Ideapad320 Touchpad Right Click Not Working

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hello,
   
  I am having issues with my touch pad. The touch pad in general works but it 
will not allow me drag windows or highlight items as well as I cannot right 
click. My Lenovo Ideapad320 is dual booted with Ubuntu 16.04.3 LTS & I believe 
my kernel version is 4.10.0-40-generic. Any ideas/suggestions? On the windows 
side everything works fine. Also external mouse works fine.

  Thanxxx
  --- 
  ApportVersion: 2.20.1-0ubuntu2.13
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  matukai1739 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=343c6b76-3abe-473f-8fbe-5b5cc8a2c7ce
  InstallationDate: Installed on 2017-12-02 (5 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 003: ID 5986:210f Acer, Inc 
   Bus 001 Device 002: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 80XL
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-40-generic.efi.signed 
root=UUID=6a6efca5-21ea-4048-bb96-a6c8a8c966f3 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.10.0-40.44~16.04.1-generic 4.10.17
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-40-generic N/A
   linux-backports-modules-4.10.0-40-generic  N/A
   linux-firmware 1.157.14
  Tags:  xenial
  Uname: Linux 4.10.0-40-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/31/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 4WCN28WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad 320-15IKB
  dmi.modalias: 
dmi:bvnLENOVO:bvr4WCN28WW:bd08/31/2017:svnLENOVO:pn80XL:pvrLenovoideapad320-15IKB:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoideapad320-15IKB:
  dmi.product.name: 80XL
  dmi.product.version: Lenovo ideapad 320-15IKB
  dmi.sys.vendor: LENOVO

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

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


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

2017-12-07 Thread matt
apport information

** Attachment added: "ProcCpuinfo.txt"
   
https://bugs.launchpad.net/bugs/1737060/+attachment/5019912/+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/1737060

Title:
  Lenovo Ideapad320 Touchpad Right Click Not Working

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hello,
   
  I am having issues with my touch pad. The touch pad in general works but it 
will not allow me drag windows or highlight items as well as I cannot right 
click. My Lenovo Ideapad320 is dual booted with Ubuntu 16.04.3 LTS & I believe 
my kernel version is 4.10.0-40-generic. Any ideas/suggestions? On the windows 
side everything works fine. Also external mouse works fine.

  Thanxxx
  --- 
  ApportVersion: 2.20.1-0ubuntu2.13
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  matukai1739 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=343c6b76-3abe-473f-8fbe-5b5cc8a2c7ce
  InstallationDate: Installed on 2017-12-02 (5 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 003: ID 5986:210f Acer, Inc 
   Bus 001 Device 002: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 80XL
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-40-generic.efi.signed 
root=UUID=6a6efca5-21ea-4048-bb96-a6c8a8c966f3 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.10.0-40.44~16.04.1-generic 4.10.17
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-40-generic N/A
   linux-backports-modules-4.10.0-40-generic  N/A
   linux-firmware 1.157.14
  Tags:  xenial
  Uname: Linux 4.10.0-40-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/31/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 4WCN28WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad 320-15IKB
  dmi.modalias: 
dmi:bvnLENOVO:bvr4WCN28WW:bd08/31/2017:svnLENOVO:pn80XL:pvrLenovoideapad320-15IKB:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoideapad320-15IKB:
  dmi.product.name: 80XL
  dmi.product.version: Lenovo ideapad 320-15IKB
  dmi.sys.vendor: LENOVO

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

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


[Kernel-packages] [Bug 1737060] PulseList.txt

2017-12-07 Thread matt
apport information

** Attachment added: "PulseList.txt"
   
https://bugs.launchpad.net/bugs/1737060/+attachment/5019917/+files/PulseList.txt

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

Title:
  Lenovo Ideapad320 Touchpad Right Click Not Working

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hello,
   
  I am having issues with my touch pad. The touch pad in general works but it 
will not allow me drag windows or highlight items as well as I cannot right 
click. My Lenovo Ideapad320 is dual booted with Ubuntu 16.04.3 LTS & I believe 
my kernel version is 4.10.0-40-generic. Any ideas/suggestions? On the windows 
side everything works fine. Also external mouse works fine.

  Thanxxx
  --- 
  ApportVersion: 2.20.1-0ubuntu2.13
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  matukai1739 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=343c6b76-3abe-473f-8fbe-5b5cc8a2c7ce
  InstallationDate: Installed on 2017-12-02 (5 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 003: ID 5986:210f Acer, Inc 
   Bus 001 Device 002: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 80XL
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-40-generic.efi.signed 
root=UUID=6a6efca5-21ea-4048-bb96-a6c8a8c966f3 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.10.0-40.44~16.04.1-generic 4.10.17
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-40-generic N/A
   linux-backports-modules-4.10.0-40-generic  N/A
   linux-firmware 1.157.14
  Tags:  xenial
  Uname: Linux 4.10.0-40-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/31/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 4WCN28WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad 320-15IKB
  dmi.modalias: 
dmi:bvnLENOVO:bvr4WCN28WW:bd08/31/2017:svnLENOVO:pn80XL:pvrLenovoideapad320-15IKB:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoideapad320-15IKB:
  dmi.product.name: 80XL
  dmi.product.version: Lenovo ideapad 320-15IKB
  dmi.sys.vendor: LENOVO

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

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


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

2017-12-07 Thread matt
apport information

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

Title:
  Lenovo Ideapad320 Touchpad Right Click Not Working

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hello,
   
  I am having issues with my touch pad. The touch pad in general works but it 
will not allow me drag windows or highlight items as well as I cannot right 
click. My Lenovo Ideapad320 is dual booted with Ubuntu 16.04.3 LTS & I believe 
my kernel version is 4.10.0-40-generic. Any ideas/suggestions? On the windows 
side everything works fine. Also external mouse works fine.

  Thanxxx
  --- 
  ApportVersion: 2.20.1-0ubuntu2.13
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  matukai1739 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=343c6b76-3abe-473f-8fbe-5b5cc8a2c7ce
  InstallationDate: Installed on 2017-12-02 (5 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 003: ID 5986:210f Acer, Inc 
   Bus 001 Device 002: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 80XL
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-40-generic.efi.signed 
root=UUID=6a6efca5-21ea-4048-bb96-a6c8a8c966f3 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.10.0-40.44~16.04.1-generic 4.10.17
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-40-generic N/A
   linux-backports-modules-4.10.0-40-generic  N/A
   linux-firmware 1.157.14
  Tags:  xenial
  Uname: Linux 4.10.0-40-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/31/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 4WCN28WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad 320-15IKB
  dmi.modalias: 
dmi:bvnLENOVO:bvr4WCN28WW:bd08/31/2017:svnLENOVO:pn80XL:pvrLenovoideapad320-15IKB:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoideapad320-15IKB:
  dmi.product.name: 80XL
  dmi.product.version: Lenovo ideapad 320-15IKB
  dmi.sys.vendor: LENOVO

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

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


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

2017-12-07 Thread matt
apport information

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

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

Title:
  Lenovo Ideapad320 Touchpad Right Click Not Working

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hello,
   
  I am having issues with my touch pad. The touch pad in general works but it 
will not allow me drag windows or highlight items as well as I cannot right 
click. My Lenovo Ideapad320 is dual booted with Ubuntu 16.04.3 LTS & I believe 
my kernel version is 4.10.0-40-generic. Any ideas/suggestions? On the windows 
side everything works fine. Also external mouse works fine.

  Thanxxx
  --- 
  ApportVersion: 2.20.1-0ubuntu2.13
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  matukai1739 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=343c6b76-3abe-473f-8fbe-5b5cc8a2c7ce
  InstallationDate: Installed on 2017-12-02 (5 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 003: ID 5986:210f Acer, Inc 
   Bus 001 Device 002: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 80XL
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-40-generic.efi.signed 
root=UUID=6a6efca5-21ea-4048-bb96-a6c8a8c966f3 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.10.0-40.44~16.04.1-generic 4.10.17
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-40-generic N/A
   linux-backports-modules-4.10.0-40-generic  N/A
   linux-firmware 1.157.14
  Tags:  xenial
  Uname: Linux 4.10.0-40-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/31/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 4WCN28WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad 320-15IKB
  dmi.modalias: 
dmi:bvnLENOVO:bvr4WCN28WW:bd08/31/2017:svnLENOVO:pn80XL:pvrLenovoideapad320-15IKB:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoideapad320-15IKB:
  dmi.product.name: 80XL
  dmi.product.version: Lenovo ideapad 320-15IKB
  dmi.sys.vendor: LENOVO

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

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


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

2017-12-07 Thread matt
apport information

** Attachment added: "ProcModules.txt"
   
https://bugs.launchpad.net/bugs/1737060/+attachment/5019916/+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/1737060

Title:
  Lenovo Ideapad320 Touchpad Right Click Not Working

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hello,
   
  I am having issues with my touch pad. The touch pad in general works but it 
will not allow me drag windows or highlight items as well as I cannot right 
click. My Lenovo Ideapad320 is dual booted with Ubuntu 16.04.3 LTS & I believe 
my kernel version is 4.10.0-40-generic. Any ideas/suggestions? On the windows 
side everything works fine. Also external mouse works fine.

  Thanxxx
  --- 
  ApportVersion: 2.20.1-0ubuntu2.13
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  matukai1739 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=343c6b76-3abe-473f-8fbe-5b5cc8a2c7ce
  InstallationDate: Installed on 2017-12-02 (5 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 003: ID 5986:210f Acer, Inc 
   Bus 001 Device 002: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 80XL
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-40-generic.efi.signed 
root=UUID=6a6efca5-21ea-4048-bb96-a6c8a8c966f3 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.10.0-40.44~16.04.1-generic 4.10.17
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-40-generic N/A
   linux-backports-modules-4.10.0-40-generic  N/A
   linux-firmware 1.157.14
  Tags:  xenial
  Uname: Linux 4.10.0-40-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/31/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 4WCN28WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad 320-15IKB
  dmi.modalias: 
dmi:bvnLENOVO:bvr4WCN28WW:bd08/31/2017:svnLENOVO:pn80XL:pvrLenovoideapad320-15IKB:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoideapad320-15IKB:
  dmi.product.name: 80XL
  dmi.product.version: Lenovo ideapad 320-15IKB
  dmi.sys.vendor: LENOVO

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

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


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

2017-12-07 Thread matt
apport information

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

Title:
  Lenovo Ideapad320 Touchpad Right Click Not Working

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hello,
   
  I am having issues with my touch pad. The touch pad in general works but it 
will not allow me drag windows or highlight items as well as I cannot right 
click. My Lenovo Ideapad320 is dual booted with Ubuntu 16.04.3 LTS & I believe 
my kernel version is 4.10.0-40-generic. Any ideas/suggestions? On the windows 
side everything works fine. Also external mouse works fine.

  Thanxxx
  --- 
  ApportVersion: 2.20.1-0ubuntu2.13
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  matukai1739 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=343c6b76-3abe-473f-8fbe-5b5cc8a2c7ce
  InstallationDate: Installed on 2017-12-02 (5 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 003: ID 5986:210f Acer, Inc 
   Bus 001 Device 002: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 80XL
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-40-generic.efi.signed 
root=UUID=6a6efca5-21ea-4048-bb96-a6c8a8c966f3 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.10.0-40.44~16.04.1-generic 4.10.17
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-40-generic N/A
   linux-backports-modules-4.10.0-40-generic  N/A
   linux-firmware 1.157.14
  Tags:  xenial
  Uname: Linux 4.10.0-40-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/31/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 4WCN28WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad 320-15IKB
  dmi.modalias: 
dmi:bvnLENOVO:bvr4WCN28WW:bd08/31/2017:svnLENOVO:pn80XL:pvrLenovoideapad320-15IKB:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoideapad320-15IKB:
  dmi.product.name: 80XL
  dmi.product.version: Lenovo ideapad 320-15IKB
  dmi.sys.vendor: LENOVO

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

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


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

2017-12-07 Thread matt
apport information

** Attachment added: "RfKill.txt"
   https://bugs.launchpad.net/bugs/1737060/+attachment/5019918/+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/1737060

Title:
  Lenovo Ideapad320 Touchpad Right Click Not Working

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hello,
   
  I am having issues with my touch pad. The touch pad in general works but it 
will not allow me drag windows or highlight items as well as I cannot right 
click. My Lenovo Ideapad320 is dual booted with Ubuntu 16.04.3 LTS & I believe 
my kernel version is 4.10.0-40-generic. Any ideas/suggestions? On the windows 
side everything works fine. Also external mouse works fine.

  Thanxxx
  --- 
  ApportVersion: 2.20.1-0ubuntu2.13
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  matukai1739 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=343c6b76-3abe-473f-8fbe-5b5cc8a2c7ce
  InstallationDate: Installed on 2017-12-02 (5 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 003: ID 5986:210f Acer, Inc 
   Bus 001 Device 002: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 80XL
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-40-generic.efi.signed 
root=UUID=6a6efca5-21ea-4048-bb96-a6c8a8c966f3 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.10.0-40.44~16.04.1-generic 4.10.17
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-40-generic N/A
   linux-backports-modules-4.10.0-40-generic  N/A
   linux-firmware 1.157.14
  Tags:  xenial
  Uname: Linux 4.10.0-40-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/31/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 4WCN28WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad 320-15IKB
  dmi.modalias: 
dmi:bvnLENOVO:bvr4WCN28WW:bd08/31/2017:svnLENOVO:pn80XL:pvrLenovoideapad320-15IKB:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoideapad320-15IKB:
  dmi.product.name: 80XL
  dmi.product.version: Lenovo ideapad 320-15IKB
  dmi.sys.vendor: LENOVO

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

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


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

2017-12-07 Thread matt
apport information

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

Title:
  Lenovo Ideapad320 Touchpad Right Click Not Working

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hello,
   
  I am having issues with my touch pad. The touch pad in general works but it 
will not allow me drag windows or highlight items as well as I cannot right 
click. My Lenovo Ideapad320 is dual booted with Ubuntu 16.04.3 LTS & I believe 
my kernel version is 4.10.0-40-generic. Any ideas/suggestions? On the windows 
side everything works fine. Also external mouse works fine.

  Thanxxx
  --- 
  ApportVersion: 2.20.1-0ubuntu2.13
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  matukai1739 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=343c6b76-3abe-473f-8fbe-5b5cc8a2c7ce
  InstallationDate: Installed on 2017-12-02 (5 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 003: ID 5986:210f Acer, Inc 
   Bus 001 Device 002: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 80XL
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-40-generic.efi.signed 
root=UUID=6a6efca5-21ea-4048-bb96-a6c8a8c966f3 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.10.0-40.44~16.04.1-generic 4.10.17
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-40-generic N/A
   linux-backports-modules-4.10.0-40-generic  N/A
   linux-firmware 1.157.14
  Tags:  xenial
  Uname: Linux 4.10.0-40-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/31/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 4WCN28WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad 320-15IKB
  dmi.modalias: 
dmi:bvnLENOVO:bvr4WCN28WW:bd08/31/2017:svnLENOVO:pn80XL:pvrLenovoideapad320-15IKB:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoideapad320-15IKB:
  dmi.product.name: 80XL
  dmi.product.version: Lenovo ideapad 320-15IKB
  dmi.sys.vendor: LENOVO

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

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


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

2017-12-07 Thread matt
apport information

** Attachment added: "IwConfig.txt"
   
https://bugs.launchpad.net/bugs/1737060/+attachment/5019909/+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/1737060

Title:
  Lenovo Ideapad320 Touchpad Right Click Not Working

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hello,
   
  I am having issues with my touch pad. The touch pad in general works but it 
will not allow me drag windows or highlight items as well as I cannot right 
click. My Lenovo Ideapad320 is dual booted with Ubuntu 16.04.3 LTS & I believe 
my kernel version is 4.10.0-40-generic. Any ideas/suggestions? On the windows 
side everything works fine. Also external mouse works fine.

  Thanxxx
  --- 
  ApportVersion: 2.20.1-0ubuntu2.13
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  matukai1739 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=343c6b76-3abe-473f-8fbe-5b5cc8a2c7ce
  InstallationDate: Installed on 2017-12-02 (5 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 003: ID 5986:210f Acer, Inc 
   Bus 001 Device 002: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 80XL
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-40-generic.efi.signed 
root=UUID=6a6efca5-21ea-4048-bb96-a6c8a8c966f3 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.10.0-40.44~16.04.1-generic 4.10.17
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-40-generic N/A
   linux-backports-modules-4.10.0-40-generic  N/A
   linux-firmware 1.157.14
  Tags:  xenial
  Uname: Linux 4.10.0-40-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/31/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 4WCN28WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad 320-15IKB
  dmi.modalias: 
dmi:bvnLENOVO:bvr4WCN28WW:bd08/31/2017:svnLENOVO:pn80XL:pvrLenovoideapad320-15IKB:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoideapad320-15IKB:
  dmi.product.name: 80XL
  dmi.product.version: Lenovo ideapad 320-15IKB
  dmi.sys.vendor: LENOVO

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

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


[Kernel-packages] [Bug 1737060] Re: Lenovo Ideapad320 Touchpad Right Click Not Working

2017-12-07 Thread matt
apport information

** Tags added: apport-collected xenial

** Description changed:

  Hello,
   
  I am having issues with my touch pad. The touch pad in general works but it 
will not allow me drag windows or highlight items as well as I cannot right 
click. My Lenovo Ideapad320 is dual booted with Ubuntu 16.04.3 LTS & I believe 
my kernel version is 4.10.0-40-generic. Any ideas/suggestions? On the windows 
side everything works fine. Also external mouse works fine.
  
  Thanxxx
+ --- 
+ ApportVersion: 2.20.1-0ubuntu2.13
+ Architecture: amd64
+ AudioDevicesInUse:
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC0:  matukai1739 F pulseaudio
+ CurrentDesktop: Unity
+ DistroRelease: Ubuntu 16.04
+ HibernationDevice: RESUME=UUID=343c6b76-3abe-473f-8fbe-5b5cc8a2c7ce
+ InstallationDate: Installed on 2017-12-02 (5 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 003: ID 5986:210f Acer, Inc 
+  Bus 001 Device 002: ID 8087:0a2a Intel Corp. 
+  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
+ MachineType: LENOVO 80XL
+ Package: linux (not installed)
+ ProcFB: 0 inteldrmfb
+ ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-40-generic.efi.signed 
root=UUID=6a6efca5-21ea-4048-bb96-a6c8a8c966f3 ro quiet splash vt.handoff=7
+ ProcVersionSignature: Ubuntu 4.10.0-40.44~16.04.1-generic 4.10.17
+ RelatedPackageVersions:
+  linux-restricted-modules-4.10.0-40-generic N/A
+  linux-backports-modules-4.10.0-40-generic  N/A
+  linux-firmware 1.157.14
+ Tags:  xenial
+ Uname: Linux 4.10.0-40-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
+ _MarkForUpload: True
+ dmi.bios.date: 08/31/2017
+ dmi.bios.vendor: LENOVO
+ dmi.bios.version: 4WCN28WW
+ dmi.board.asset.tag: NO Asset Tag
+ dmi.board.name: LNVNB161216
+ dmi.board.vendor: LENOVO
+ dmi.board.version: SDK0J40709 WIN
+ dmi.chassis.asset.tag: NO Asset Tag
+ dmi.chassis.type: 10
+ dmi.chassis.vendor: LENOVO
+ dmi.chassis.version: Lenovo ideapad 320-15IKB
+ dmi.modalias: 
dmi:bvnLENOVO:bvr4WCN28WW:bd08/31/2017:svnLENOVO:pn80XL:pvrLenovoideapad320-15IKB:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoideapad320-15IKB:
+ dmi.product.name: 80XL
+ dmi.product.version: Lenovo ideapad 320-15IKB
+ dmi.sys.vendor: LENOVO

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

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

Title:
  Lenovo Ideapad320 Touchpad Right Click Not Working

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hello,
   
  I am having issues with my touch pad. The touch pad in general works but it 
will not allow me drag windows or highlight items as well as I cannot right 
click. My Lenovo Ideapad320 is dual booted with Ubuntu 16.04.3 LTS & I believe 
my kernel version is 4.10.0-40-generic. Any ideas/suggestions? On the windows 
side everything works fine. Also external mouse works fine.

  Thanxxx
  --- 
  ApportVersion: 2.20.1-0ubuntu2.13
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  matukai1739 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=343c6b76-3abe-473f-8fbe-5b5cc8a2c7ce
  InstallationDate: Installed on 2017-12-02 (5 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 003: ID 5986:210f Acer, Inc 
   Bus 001 Device 002: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 80XL
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-40-generic.efi.signed 
root=UUID=6a6efca5-21ea-4048-bb96-a6c8a8c966f3 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.10.0-40.44~16.04.1-generic 4.10.17
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-40-generic N/A
   linux-backports-modules-4.10.0-40-generic  N/A
   linux-firmware 1.157.14
  Tags:  xenial
  Uname: Linux 4.10.0-40-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/31/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 4WCN28WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo 

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

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

apport-collect 1737060

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

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

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

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

** Tags added: zesty

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

Title:
  Lenovo Ideapad320 Touchpad Right Click Not Working

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hello,
   
  I am having issues with my touch pad. The touch pad in general works but it 
will not allow me drag windows or highlight items as well as I cannot right 
click. My Lenovo Ideapad320 is dual booted with Ubuntu 16.04.3 LTS & I believe 
my kernel version is 4.10.0-40-generic. Any ideas/suggestions? On the windows 
side everything works fine. Also external mouse works fine.

  Thanxxx

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

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


[Kernel-packages] [Bug 1737060] [NEW] Lenovo Ideapad320 Touchpad Right Click Not Working

2017-12-07 Thread matt
Public bug reported:

Hello,
 
I am having issues with my touch pad. The touch pad in general works but it 
will not allow me drag windows or highlight items as well as I cannot right 
click. My Lenovo Ideapad320 is dual booted with Ubuntu 16.04.3 LTS & I believe 
my kernel version is 4.10.0-40-generic. Any ideas/suggestions? On the windows 
side everything works fine. Also external mouse works fine.

Thanxxx

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


** Tags: 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/1737060

Title:
  Lenovo Ideapad320 Touchpad Right Click Not Working

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hello,
   
  I am having issues with my touch pad. The touch pad in general works but it 
will not allow me drag windows or highlight items as well as I cannot right 
click. My Lenovo Ideapad320 is dual booted with Ubuntu 16.04.3 LTS & I believe 
my kernel version is 4.10.0-40-generic. Any ideas/suggestions? On the windows 
side everything works fine. Also external mouse works fine.

  Thanxxx

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

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


[Kernel-packages] [Bug 1737033] Re: upgrading linux-image package to 4.4.0-103.126 breaks Ceph network file system connection

2017-12-07 Thread Benjamin Long
** Also affects: ceph (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  upgrading linux-image package to 4.4.0-103.126 breaks Ceph network
  file system connection

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

Bug description:
  After clients have upgraded to 4.4.0-103.126 they can no longer
  connect to the Ceph network.

  Using the Grub menu to boot the previous kernel fixes the issue.

  The error in dmesg is:

  [   46.811897] FS-Cache: Loaded
  [   46.843670] Key type ceph registered
  [   46.844177] libceph: loaded (mon/osd proto 15/24)
  [   46.863107] FS-Cache: Netfs 'ceph' registered for caching
  [   46.863116] ceph: loaded (mds proto 32)
  [   46.884392] libceph: client3354099 fsid 
2efbeab1-4903-4c4c-8365-6778afecbcbd
  [   46.886856] libceph: mon0 10.10.2.111:6789 session established
  [   46.897487] ceph: problem parsing mds trace -5
  [   46.897491] ceph: mds parse_reply err -5
  [   46.897492] ceph: mdsc_handle_reply got corrupt reply mds0(tid:1)

  All clients are running ceph client version:
  ii  ceph-fs-common10.2.9-0ubuntu0.16.04.1

  Server nodes are running 10.2.6 packages as supplied by Ceph.

  All 10.2.* versions are compatible. Using the previous kernel allows the 
connection to work.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.14
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  lightdm1310 F pulseaudio
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=9e3c38ba-10bd-4183-b073-68d9d9a30a9b
  IwConfig: Error: [Errno 2] No such file or directory
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: innotek GmbH VirtualBox
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US
   SHELL=/bin/bash
  ProcFB: 0 vboxdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-103-generic 
root=UUID=5a37e891-beb9-477f-b934-3c05651acf68 ro quiet splash
  ProcVersionSignature: Ubuntu 4.4.0-103.126-generic 4.4.98
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-103-generic N/A
   linux-backports-modules-4.4.0-103-generic  N/A
   linux-firmware 1.157.14
  RfKill:
   
  Tags:  xenial xenial
  Uname: Linux 4.4.0-103-generic x86_64
  UnreportableReason: The report belongs to a package that is not installed.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: False
  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/ceph/+bug/1737033/+subscriptions

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


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

2017-12-07 Thread Benjamin Long
apport information

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

Title:
  upgrading linux-image package to 4.4.0-103.126 breaks Ceph network
  file system connection

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After clients have upgraded to 4.4.0-103.126 they can no longer
  connect to the Ceph network.

  Using the Grub menu to boot the previous kernel fixes the issue.

  The error in dmesg is:

  [   46.811897] FS-Cache: Loaded
  [   46.843670] Key type ceph registered
  [   46.844177] libceph: loaded (mon/osd proto 15/24)
  [   46.863107] FS-Cache: Netfs 'ceph' registered for caching
  [   46.863116] ceph: loaded (mds proto 32)
  [   46.884392] libceph: client3354099 fsid 
2efbeab1-4903-4c4c-8365-6778afecbcbd
  [   46.886856] libceph: mon0 10.10.2.111:6789 session established
  [   46.897487] ceph: problem parsing mds trace -5
  [   46.897491] ceph: mds parse_reply err -5
  [   46.897492] ceph: mdsc_handle_reply got corrupt reply mds0(tid:1)

  All clients are running ceph client version:
  ii  ceph-fs-common10.2.9-0ubuntu0.16.04.1

  Server nodes are running 10.2.6 packages as supplied by Ceph.

  All 10.2.* versions are compatible. Using the previous kernel allows the 
connection to work.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.14
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  lightdm1310 F pulseaudio
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=9e3c38ba-10bd-4183-b073-68d9d9a30a9b
  IwConfig: Error: [Errno 2] No such file or directory
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: innotek GmbH VirtualBox
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US
   SHELL=/bin/bash
  ProcFB: 0 vboxdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-103-generic 
root=UUID=5a37e891-beb9-477f-b934-3c05651acf68 ro quiet splash
  ProcVersionSignature: Ubuntu 4.4.0-103.126-generic 4.4.98
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-103-generic N/A
   linux-backports-modules-4.4.0-103-generic  N/A
   linux-firmware 1.157.14
  RfKill:
   
  Tags:  xenial xenial
  Uname: Linux 4.4.0-103-generic x86_64
  UnreportableReason: The report belongs to a package that is not installed.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: False
  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/1737033/+subscriptions

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


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

2017-12-07 Thread Benjamin Long
apport information

** Attachment added: "ProcModules.txt"
   
https://bugs.launchpad.net/bugs/1737033/+attachment/5019866/+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/1737033

Title:
  upgrading linux-image package to 4.4.0-103.126 breaks Ceph network
  file system connection

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After clients have upgraded to 4.4.0-103.126 they can no longer
  connect to the Ceph network.

  Using the Grub menu to boot the previous kernel fixes the issue.

  The error in dmesg is:

  [   46.811897] FS-Cache: Loaded
  [   46.843670] Key type ceph registered
  [   46.844177] libceph: loaded (mon/osd proto 15/24)
  [   46.863107] FS-Cache: Netfs 'ceph' registered for caching
  [   46.863116] ceph: loaded (mds proto 32)
  [   46.884392] libceph: client3354099 fsid 
2efbeab1-4903-4c4c-8365-6778afecbcbd
  [   46.886856] libceph: mon0 10.10.2.111:6789 session established
  [   46.897487] ceph: problem parsing mds trace -5
  [   46.897491] ceph: mds parse_reply err -5
  [   46.897492] ceph: mdsc_handle_reply got corrupt reply mds0(tid:1)

  All clients are running ceph client version:
  ii  ceph-fs-common10.2.9-0ubuntu0.16.04.1

  Server nodes are running 10.2.6 packages as supplied by Ceph.

  All 10.2.* versions are compatible. Using the previous kernel allows the 
connection to work.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.14
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  lightdm1310 F pulseaudio
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=9e3c38ba-10bd-4183-b073-68d9d9a30a9b
  IwConfig: Error: [Errno 2] No such file or directory
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: innotek GmbH VirtualBox
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US
   SHELL=/bin/bash
  ProcFB: 0 vboxdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-103-generic 
root=UUID=5a37e891-beb9-477f-b934-3c05651acf68 ro quiet splash
  ProcVersionSignature: Ubuntu 4.4.0-103.126-generic 4.4.98
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-103-generic N/A
   linux-backports-modules-4.4.0-103-generic  N/A
   linux-firmware 1.157.14
  RfKill:
   
  Tags:  xenial xenial
  Uname: Linux 4.4.0-103-generic x86_64
  UnreportableReason: The report belongs to a package that is not installed.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: False
  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/1737033/+subscriptions

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


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

2017-12-07 Thread Benjamin Long
apport information

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

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

Title:
  upgrading linux-image package to 4.4.0-103.126 breaks Ceph network
  file system connection

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After clients have upgraded to 4.4.0-103.126 they can no longer
  connect to the Ceph network.

  Using the Grub menu to boot the previous kernel fixes the issue.

  The error in dmesg is:

  [   46.811897] FS-Cache: Loaded
  [   46.843670] Key type ceph registered
  [   46.844177] libceph: loaded (mon/osd proto 15/24)
  [   46.863107] FS-Cache: Netfs 'ceph' registered for caching
  [   46.863116] ceph: loaded (mds proto 32)
  [   46.884392] libceph: client3354099 fsid 
2efbeab1-4903-4c4c-8365-6778afecbcbd
  [   46.886856] libceph: mon0 10.10.2.111:6789 session established
  [   46.897487] ceph: problem parsing mds trace -5
  [   46.897491] ceph: mds parse_reply err -5
  [   46.897492] ceph: mdsc_handle_reply got corrupt reply mds0(tid:1)

  All clients are running ceph client version:
  ii  ceph-fs-common10.2.9-0ubuntu0.16.04.1

  Server nodes are running 10.2.6 packages as supplied by Ceph.

  All 10.2.* versions are compatible. Using the previous kernel allows the 
connection to work.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.14
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  lightdm1310 F pulseaudio
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=9e3c38ba-10bd-4183-b073-68d9d9a30a9b
  IwConfig: Error: [Errno 2] No such file or directory
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: innotek GmbH VirtualBox
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US
   SHELL=/bin/bash
  ProcFB: 0 vboxdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-103-generic 
root=UUID=5a37e891-beb9-477f-b934-3c05651acf68 ro quiet splash
  ProcVersionSignature: Ubuntu 4.4.0-103.126-generic 4.4.98
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-103-generic N/A
   linux-backports-modules-4.4.0-103-generic  N/A
   linux-firmware 1.157.14
  RfKill:
   
  Tags:  xenial xenial
  Uname: Linux 4.4.0-103-generic x86_64
  UnreportableReason: The report belongs to a package that is not installed.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: False
  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/1737033/+subscriptions

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


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

2017-12-07 Thread Benjamin Long
apport information

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

Title:
  upgrading linux-image package to 4.4.0-103.126 breaks Ceph network
  file system connection

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After clients have upgraded to 4.4.0-103.126 they can no longer
  connect to the Ceph network.

  Using the Grub menu to boot the previous kernel fixes the issue.

  The error in dmesg is:

  [   46.811897] FS-Cache: Loaded
  [   46.843670] Key type ceph registered
  [   46.844177] libceph: loaded (mon/osd proto 15/24)
  [   46.863107] FS-Cache: Netfs 'ceph' registered for caching
  [   46.863116] ceph: loaded (mds proto 32)
  [   46.884392] libceph: client3354099 fsid 
2efbeab1-4903-4c4c-8365-6778afecbcbd
  [   46.886856] libceph: mon0 10.10.2.111:6789 session established
  [   46.897487] ceph: problem parsing mds trace -5
  [   46.897491] ceph: mds parse_reply err -5
  [   46.897492] ceph: mdsc_handle_reply got corrupt reply mds0(tid:1)

  All clients are running ceph client version:
  ii  ceph-fs-common10.2.9-0ubuntu0.16.04.1

  Server nodes are running 10.2.6 packages as supplied by Ceph.

  All 10.2.* versions are compatible. Using the previous kernel allows the 
connection to work.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.14
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  lightdm1310 F pulseaudio
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=9e3c38ba-10bd-4183-b073-68d9d9a30a9b
  IwConfig: Error: [Errno 2] No such file or directory
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: innotek GmbH VirtualBox
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US
   SHELL=/bin/bash
  ProcFB: 0 vboxdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-103-generic 
root=UUID=5a37e891-beb9-477f-b934-3c05651acf68 ro quiet splash
  ProcVersionSignature: Ubuntu 4.4.0-103.126-generic 4.4.98
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-103-generic N/A
   linux-backports-modules-4.4.0-103-generic  N/A
   linux-firmware 1.157.14
  RfKill:
   
  Tags:  xenial xenial
  Uname: Linux 4.4.0-103-generic x86_64
  UnreportableReason: The report belongs to a package that is not installed.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: False
  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/1737033/+subscriptions

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


[Kernel-packages] [Bug 1737033] Re: upgrading linux-image package to 4.4.0-103.126 breaks Ceph network file system connection

2017-12-07 Thread Benjamin Long
apport information

** Tags added: apport-collected xenial

** Description changed:

  After clients have upgraded to 4.4.0-103.126 they can no longer connect
  to the Ceph network.
  
  Using the Grub menu to boot the previous kernel fixes the issue.
  
  The error in dmesg is:
  
  [   46.811897] FS-Cache: Loaded
  [   46.843670] Key type ceph registered
  [   46.844177] libceph: loaded (mon/osd proto 15/24)
  [   46.863107] FS-Cache: Netfs 'ceph' registered for caching
  [   46.863116] ceph: loaded (mds proto 32)
  [   46.884392] libceph: client3354099 fsid 
2efbeab1-4903-4c4c-8365-6778afecbcbd
  [   46.886856] libceph: mon0 10.10.2.111:6789 session established
  [   46.897487] ceph: problem parsing mds trace -5
  [   46.897491] ceph: mds parse_reply err -5
  [   46.897492] ceph: mdsc_handle_reply got corrupt reply mds0(tid:1)
  
  All clients are running ceph client version:
  ii  ceph-fs-common10.2.9-0ubuntu0.16.04.1
  
  Server nodes are running 10.2.6 packages as supplied by Ceph.
  
- All 10.2.* versions are compatible. Using the previous kernel allows the
- connection to work.
+ All 10.2.* versions are compatible. Using the previous kernel allows the 
connection to work.
+ --- 
+ ApportVersion: 2.20.1-0ubuntu2.14
+ Architecture: amd64
+ AudioDevicesInUse:
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC0:  lightdm1310 F pulseaudio
+ DistroRelease: Ubuntu 16.04
+ HibernationDevice: RESUME=UUID=9e3c38ba-10bd-4183-b073-68d9d9a30a9b
+ IwConfig: Error: [Errno 2] No such file or directory
+ Lsusb:
+  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
+  Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet
+  Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
+ MachineType: innotek GmbH VirtualBox
+ Package: linux (not installed)
+ ProcEnviron:
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  LANG=en_US
+  SHELL=/bin/bash
+ ProcFB: 0 vboxdrmfb
+ ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-103-generic 
root=UUID=5a37e891-beb9-477f-b934-3c05651acf68 ro quiet splash
+ ProcVersionSignature: Ubuntu 4.4.0-103.126-generic 4.4.98
+ PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
+ RelatedPackageVersions:
+  linux-restricted-modules-4.4.0-103-generic N/A
+  linux-backports-modules-4.4.0-103-generic  N/A
+  linux-firmware 1.157.14
+ RfKill:
+  
+ Tags:  xenial xenial
+ Uname: Linux 4.4.0-103-generic x86_64
+ UnreportableReason: The report belongs to a package that is not installed.
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups:
+  
+ _MarkForUpload: False
+ 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

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

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

Title:
  upgrading linux-image package to 4.4.0-103.126 breaks Ceph network
  file system connection

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After clients have upgraded to 4.4.0-103.126 they can no longer
  connect to the Ceph network.

  Using the Grub menu to boot the previous kernel fixes the issue.

  The error in dmesg is:

  [   46.811897] FS-Cache: Loaded
  [   46.843670] Key type ceph registered
  [   46.844177] libceph: loaded (mon/osd proto 15/24)
  [   46.863107] FS-Cache: Netfs 'ceph' registered for caching
  [   46.863116] ceph: loaded (mds proto 32)
  [   46.884392] libceph: client3354099 fsid 
2efbeab1-4903-4c4c-8365-6778afecbcbd
  [   46.886856] libceph: mon0 10.10.2.111:6789 session established
  [   46.897487] ceph: problem parsing mds trace -5
  [   46.897491] ceph: mds parse_reply err -5
  [   46.897492] ceph: mdsc_handle_reply got corrupt reply mds0(tid:1)

  All clients are running ceph client version:
  ii  ceph-fs-common10.2.9-0ubuntu0.16.04.1

  Server nodes are running 10.2.6 packages as supplied by Ceph.

  All 10.2.* versions are compatible. Using the previous kernel allows the 
connection to work.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.14
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  lightdm1310 F pulseaudio
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=9e3c38ba-10bd-4183-b073-68d9d9a30a9b
  IwConfig: 

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

2017-12-07 Thread Benjamin Long
apport information

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

Title:
  upgrading linux-image package to 4.4.0-103.126 breaks Ceph network
  file system connection

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After clients have upgraded to 4.4.0-103.126 they can no longer
  connect to the Ceph network.

  Using the Grub menu to boot the previous kernel fixes the issue.

  The error in dmesg is:

  [   46.811897] FS-Cache: Loaded
  [   46.843670] Key type ceph registered
  [   46.844177] libceph: loaded (mon/osd proto 15/24)
  [   46.863107] FS-Cache: Netfs 'ceph' registered for caching
  [   46.863116] ceph: loaded (mds proto 32)
  [   46.884392] libceph: client3354099 fsid 
2efbeab1-4903-4c4c-8365-6778afecbcbd
  [   46.886856] libceph: mon0 10.10.2.111:6789 session established
  [   46.897487] ceph: problem parsing mds trace -5
  [   46.897491] ceph: mds parse_reply err -5
  [   46.897492] ceph: mdsc_handle_reply got corrupt reply mds0(tid:1)

  All clients are running ceph client version:
  ii  ceph-fs-common10.2.9-0ubuntu0.16.04.1

  Server nodes are running 10.2.6 packages as supplied by Ceph.

  All 10.2.* versions are compatible. Using the previous kernel allows the 
connection to work.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.14
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  lightdm1310 F pulseaudio
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=9e3c38ba-10bd-4183-b073-68d9d9a30a9b
  IwConfig: Error: [Errno 2] No such file or directory
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: innotek GmbH VirtualBox
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US
   SHELL=/bin/bash
  ProcFB: 0 vboxdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-103-generic 
root=UUID=5a37e891-beb9-477f-b934-3c05651acf68 ro quiet splash
  ProcVersionSignature: Ubuntu 4.4.0-103.126-generic 4.4.98
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-103-generic N/A
   linux-backports-modules-4.4.0-103-generic  N/A
   linux-firmware 1.157.14
  RfKill:
   
  Tags:  xenial xenial
  Uname: Linux 4.4.0-103-generic x86_64
  UnreportableReason: The report belongs to a package that is not installed.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: False
  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/1737033/+subscriptions

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


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

2017-12-07 Thread Benjamin Long
apport information

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

Title:
  upgrading linux-image package to 4.4.0-103.126 breaks Ceph network
  file system connection

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After clients have upgraded to 4.4.0-103.126 they can no longer
  connect to the Ceph network.

  Using the Grub menu to boot the previous kernel fixes the issue.

  The error in dmesg is:

  [   46.811897] FS-Cache: Loaded
  [   46.843670] Key type ceph registered
  [   46.844177] libceph: loaded (mon/osd proto 15/24)
  [   46.863107] FS-Cache: Netfs 'ceph' registered for caching
  [   46.863116] ceph: loaded (mds proto 32)
  [   46.884392] libceph: client3354099 fsid 
2efbeab1-4903-4c4c-8365-6778afecbcbd
  [   46.886856] libceph: mon0 10.10.2.111:6789 session established
  [   46.897487] ceph: problem parsing mds trace -5
  [   46.897491] ceph: mds parse_reply err -5
  [   46.897492] ceph: mdsc_handle_reply got corrupt reply mds0(tid:1)

  All clients are running ceph client version:
  ii  ceph-fs-common10.2.9-0ubuntu0.16.04.1

  Server nodes are running 10.2.6 packages as supplied by Ceph.

  All 10.2.* versions are compatible. Using the previous kernel allows the 
connection to work.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.14
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  lightdm1310 F pulseaudio
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=9e3c38ba-10bd-4183-b073-68d9d9a30a9b
  IwConfig: Error: [Errno 2] No such file or directory
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: innotek GmbH VirtualBox
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US
   SHELL=/bin/bash
  ProcFB: 0 vboxdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-103-generic 
root=UUID=5a37e891-beb9-477f-b934-3c05651acf68 ro quiet splash
  ProcVersionSignature: Ubuntu 4.4.0-103.126-generic 4.4.98
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-103-generic N/A
   linux-backports-modules-4.4.0-103-generic  N/A
   linux-firmware 1.157.14
  RfKill:
   
  Tags:  xenial xenial
  Uname: Linux 4.4.0-103-generic x86_64
  UnreportableReason: The report belongs to a package that is not installed.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: False
  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/1737033/+subscriptions

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


[Kernel-packages] [Bug 1737033] Re: upgrading linux-image package to 4.4.0-103.126 breaks Ceph network file system connection

2017-12-07 Thread Benjamin Long
Please note that while the apport report is from a virtualbox VM, this
is happening across my entire network. All my workstation are having the
same issue, and all are 'fixed' by booting with the previous kernel.

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

Title:
  upgrading linux-image package to 4.4.0-103.126 breaks Ceph network
  file system connection

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After clients have upgraded to 4.4.0-103.126 they can no longer
  connect to the Ceph network.

  Using the Grub menu to boot the previous kernel fixes the issue.

  The error in dmesg is:

  [   46.811897] FS-Cache: Loaded
  [   46.843670] Key type ceph registered
  [   46.844177] libceph: loaded (mon/osd proto 15/24)
  [   46.863107] FS-Cache: Netfs 'ceph' registered for caching
  [   46.863116] ceph: loaded (mds proto 32)
  [   46.884392] libceph: client3354099 fsid 
2efbeab1-4903-4c4c-8365-6778afecbcbd
  [   46.886856] libceph: mon0 10.10.2.111:6789 session established
  [   46.897487] ceph: problem parsing mds trace -5
  [   46.897491] ceph: mds parse_reply err -5
  [   46.897492] ceph: mdsc_handle_reply got corrupt reply mds0(tid:1)

  All clients are running ceph client version:
  ii  ceph-fs-common10.2.9-0ubuntu0.16.04.1

  Server nodes are running 10.2.6 packages as supplied by Ceph.

  All 10.2.* versions are compatible. Using the previous kernel allows the 
connection to work.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.14
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  lightdm1310 F pulseaudio
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=9e3c38ba-10bd-4183-b073-68d9d9a30a9b
  IwConfig: Error: [Errno 2] No such file or directory
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: innotek GmbH VirtualBox
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US
   SHELL=/bin/bash
  ProcFB: 0 vboxdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-103-generic 
root=UUID=5a37e891-beb9-477f-b934-3c05651acf68 ro quiet splash
  ProcVersionSignature: Ubuntu 4.4.0-103.126-generic 4.4.98
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-103-generic N/A
   linux-backports-modules-4.4.0-103-generic  N/A
   linux-firmware 1.157.14
  RfKill:
   
  Tags:  xenial xenial
  Uname: Linux 4.4.0-103-generic x86_64
  UnreportableReason: The report belongs to a package that is not installed.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: False
  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/1737033/+subscriptions

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


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

2017-12-07 Thread Benjamin Long
apport information

** Attachment added: "UdevDb.txt"
   https://bugs.launchpad.net/bugs/1737033/+attachment/5019867/+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/1737033

Title:
  upgrading linux-image package to 4.4.0-103.126 breaks Ceph network
  file system connection

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After clients have upgraded to 4.4.0-103.126 they can no longer
  connect to the Ceph network.

  Using the Grub menu to boot the previous kernel fixes the issue.

  The error in dmesg is:

  [   46.811897] FS-Cache: Loaded
  [   46.843670] Key type ceph registered
  [   46.844177] libceph: loaded (mon/osd proto 15/24)
  [   46.863107] FS-Cache: Netfs 'ceph' registered for caching
  [   46.863116] ceph: loaded (mds proto 32)
  [   46.884392] libceph: client3354099 fsid 
2efbeab1-4903-4c4c-8365-6778afecbcbd
  [   46.886856] libceph: mon0 10.10.2.111:6789 session established
  [   46.897487] ceph: problem parsing mds trace -5
  [   46.897491] ceph: mds parse_reply err -5
  [   46.897492] ceph: mdsc_handle_reply got corrupt reply mds0(tid:1)

  All clients are running ceph client version:
  ii  ceph-fs-common10.2.9-0ubuntu0.16.04.1

  Server nodes are running 10.2.6 packages as supplied by Ceph.

  All 10.2.* versions are compatible. Using the previous kernel allows the 
connection to work.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.14
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  lightdm1310 F pulseaudio
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=9e3c38ba-10bd-4183-b073-68d9d9a30a9b
  IwConfig: Error: [Errno 2] No such file or directory
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: innotek GmbH VirtualBox
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US
   SHELL=/bin/bash
  ProcFB: 0 vboxdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-103-generic 
root=UUID=5a37e891-beb9-477f-b934-3c05651acf68 ro quiet splash
  ProcVersionSignature: Ubuntu 4.4.0-103.126-generic 4.4.98
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-103-generic N/A
   linux-backports-modules-4.4.0-103-generic  N/A
   linux-firmware 1.157.14
  RfKill:
   
  Tags:  xenial xenial
  Uname: Linux 4.4.0-103-generic x86_64
  UnreportableReason: The report belongs to a package that is not installed.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: False
  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/1737033/+subscriptions

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


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

2017-12-07 Thread Benjamin Long
apport information

** Attachment added: "ProcInterrupts.txt"
   
https://bugs.launchpad.net/bugs/1737033/+attachment/5019865/+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/1737033

Title:
  upgrading linux-image package to 4.4.0-103.126 breaks Ceph network
  file system connection

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After clients have upgraded to 4.4.0-103.126 they can no longer
  connect to the Ceph network.

  Using the Grub menu to boot the previous kernel fixes the issue.

  The error in dmesg is:

  [   46.811897] FS-Cache: Loaded
  [   46.843670] Key type ceph registered
  [   46.844177] libceph: loaded (mon/osd proto 15/24)
  [   46.863107] FS-Cache: Netfs 'ceph' registered for caching
  [   46.863116] ceph: loaded (mds proto 32)
  [   46.884392] libceph: client3354099 fsid 
2efbeab1-4903-4c4c-8365-6778afecbcbd
  [   46.886856] libceph: mon0 10.10.2.111:6789 session established
  [   46.897487] ceph: problem parsing mds trace -5
  [   46.897491] ceph: mds parse_reply err -5
  [   46.897492] ceph: mdsc_handle_reply got corrupt reply mds0(tid:1)

  All clients are running ceph client version:
  ii  ceph-fs-common10.2.9-0ubuntu0.16.04.1

  Server nodes are running 10.2.6 packages as supplied by Ceph.

  All 10.2.* versions are compatible. Using the previous kernel allows the 
connection to work.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.14
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  lightdm1310 F pulseaudio
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=9e3c38ba-10bd-4183-b073-68d9d9a30a9b
  IwConfig: Error: [Errno 2] No such file or directory
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: innotek GmbH VirtualBox
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US
   SHELL=/bin/bash
  ProcFB: 0 vboxdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-103-generic 
root=UUID=5a37e891-beb9-477f-b934-3c05651acf68 ro quiet splash
  ProcVersionSignature: Ubuntu 4.4.0-103.126-generic 4.4.98
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-103-generic N/A
   linux-backports-modules-4.4.0-103-generic  N/A
   linux-firmware 1.157.14
  RfKill:
   
  Tags:  xenial xenial
  Uname: Linux 4.4.0-103-generic x86_64
  UnreportableReason: The report belongs to a package that is not installed.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: False
  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/1737033/+subscriptions

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


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

2017-12-07 Thread Benjamin Long
apport information

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

Title:
  upgrading linux-image package to 4.4.0-103.126 breaks Ceph network
  file system connection

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After clients have upgraded to 4.4.0-103.126 they can no longer
  connect to the Ceph network.

  Using the Grub menu to boot the previous kernel fixes the issue.

  The error in dmesg is:

  [   46.811897] FS-Cache: Loaded
  [   46.843670] Key type ceph registered
  [   46.844177] libceph: loaded (mon/osd proto 15/24)
  [   46.863107] FS-Cache: Netfs 'ceph' registered for caching
  [   46.863116] ceph: loaded (mds proto 32)
  [   46.884392] libceph: client3354099 fsid 
2efbeab1-4903-4c4c-8365-6778afecbcbd
  [   46.886856] libceph: mon0 10.10.2.111:6789 session established
  [   46.897487] ceph: problem parsing mds trace -5
  [   46.897491] ceph: mds parse_reply err -5
  [   46.897492] ceph: mdsc_handle_reply got corrupt reply mds0(tid:1)

  All clients are running ceph client version:
  ii  ceph-fs-common10.2.9-0ubuntu0.16.04.1

  Server nodes are running 10.2.6 packages as supplied by Ceph.

  All 10.2.* versions are compatible. Using the previous kernel allows the 
connection to work.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.14
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  lightdm1310 F pulseaudio
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=9e3c38ba-10bd-4183-b073-68d9d9a30a9b
  IwConfig: Error: [Errno 2] No such file or directory
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: innotek GmbH VirtualBox
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US
   SHELL=/bin/bash
  ProcFB: 0 vboxdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-103-generic 
root=UUID=5a37e891-beb9-477f-b934-3c05651acf68 ro quiet splash
  ProcVersionSignature: Ubuntu 4.4.0-103.126-generic 4.4.98
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-103-generic N/A
   linux-backports-modules-4.4.0-103-generic  N/A
   linux-firmware 1.157.14
  RfKill:
   
  Tags:  xenial xenial
  Uname: Linux 4.4.0-103-generic x86_64
  UnreportableReason: The report belongs to a package that is not installed.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: False
  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/1737033/+subscriptions

-- 
Mailing list: https://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 1736816] Re: system freezed

2017-12-07 Thread Nilanjan
i did a fresh install of ubuntu 17.10 . No , i did not do any system update
.

On Dec 8, 2017 2:30 AM, "Joseph Salisbury" 
wrote:

> Did this issue start happening after an update/upgrade?  Was there a
> prior kernel version where you were not having this particular problem?
>
> Would it be possible for you to test the latest upstream kernel? Refer
> to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
> v4.15 kernel[0].
>
> If this bug is fixed in the mainline kernel, please add the following
> tag 'kernel-fixed-upstream'.
>
> If the mainline kernel does not fix this bug, please add the tag:
> 'kernel-bug-exists-upstream'.
>
> Once testing of the upstream kernel is complete, please mark this bug as
> "Confirmed".
>
>
> Thanks in advance.
>
> [0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.15-rc2
>
>
> ** Changed in: linux (Ubuntu)
>Importance: Undecided => Medium
>
> ** Changed in: linux (Ubuntu)
>Status: Confirmed => Incomplete
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1736816
>
> Title:
>   system freezed
>
> Status in linux package in Ubuntu:
>   Incomplete
>
> Bug description:
>   laptop freezed with no response at all. no keyboard keys were working
>   . this suddenly happened when i just typing into the word processor.
>
>   my laptop has 6gb RAM and 1TB HDD
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 17.10
>   Package: linux-image-4.13.0-16-generic 4.13.0-16.19 [modified:
> boot/vmlinuz-4.13.0-16-generic]
>   ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
>   Uname: Linux 4.13.0-16-generic x86_64
>   ApportVersion: 2.20.7-0ubuntu3
>   Architecture: amd64
>   AudioDevicesInUse:
>USERPID ACCESS COMMAND
>/dev/snd/controlC1:  nilanjan   1424 F pulseaudio
>/dev/snd/controlC0:  nilanjan   1424 F pulseaudio
>   CurrentDesktop: ubuntu:GNOME
>   Date: Thu Dec  7 04:02:06 2017
>   InstallationDate: Installed on 2017-12-04 (2 days ago)
>   InstallationMedia: It
>   MachineType: Dell Inc. Inspiron 3537
>   ProcFB: 0 inteldrmfb
>   ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic
> root=UUID=59520f57-087f-4c11-8c5c-580195d38855 ro quiet splash
> vt.handoff=7
>   RelatedPackageVersions:
>linux-restricted-modules-4.13.0-16-generic N/A
>linux-backports-modules-4.13.0-16-generic  N/A
>linux-firmware 1.169
>   SourcePackage: linux
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   dmi.bios.date: 04/30/2014
>   dmi.bios.vendor: Dell Inc.
>   dmi.bios.version: A08
>   dmi.board.name: 0N7YKW
>   dmi.board.vendor: Dell Inc.
>   dmi.board.version: A00
>   dmi.chassis.type: 8
>   dmi.chassis.vendor: Dell Inc.
>   dmi.chassis.version: A08
>   dmi.modalias: dmi:bvnDellInc.:bvrA08:bd04/30/2014:svnDellInc.:
> pnInspiron3537:pvrA08:rvnDellInc.:rn0N7YKW:rvrA00:cvnDellInc.:ct8:cvrA08:
>   dmi.product.family: 00
>   dmi.product.name: Inspiron 3537
>   dmi.product.version: A08
>   dmi.sys.vendor: Dell Inc.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/
> 1736816/+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/1736816

Title:
  system freezed

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  laptop freezed with no response at all. no keyboard keys were working
  . this suddenly happened when i just typing into the word processor.

  my laptop has 6gb RAM and 1TB HDD

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-16-generic 4.13.0-16.19 [modified: 
boot/vmlinuz-4.13.0-16-generic]
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  nilanjan   1424 F pulseaudio
   /dev/snd/controlC0:  nilanjan   1424 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Dec  7 04:02:06 2017
  InstallationDate: Installed on 2017-12-04 (2 days ago)
  InstallationMedia: It
  MachineType: Dell Inc. Inspiron 3537
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=59520f57-087f-4c11-8c5c-580195d38855 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-16-generic N/A
   linux-backports-modules-4.13.0-16-generic  N/A
   linux-firmware 1.169
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/30/2014
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A08
  dmi.board.name: 0N7YKW
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A08

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

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

apport-collect 1737033

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

Title:
  upgrading linux-image package to 4.4.0-103.126 breaks Ceph network
  file system connection

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  After clients have upgraded to 4.4.0-103.126 they can no longer
  connect to the Ceph network.

  Using the Grub menu to boot the previous kernel fixes the issue.

  The error in dmesg is:

  [   46.811897] FS-Cache: Loaded
  [   46.843670] Key type ceph registered
  [   46.844177] libceph: loaded (mon/osd proto 15/24)
  [   46.863107] FS-Cache: Netfs 'ceph' registered for caching
  [   46.863116] ceph: loaded (mds proto 32)
  [   46.884392] libceph: client3354099 fsid 
2efbeab1-4903-4c4c-8365-6778afecbcbd
  [   46.886856] libceph: mon0 10.10.2.111:6789 session established
  [   46.897487] ceph: problem parsing mds trace -5
  [   46.897491] ceph: mds parse_reply err -5
  [   46.897492] ceph: mdsc_handle_reply got corrupt reply mds0(tid:1)

  All clients are running ceph client version:
  ii  ceph-fs-common10.2.9-0ubuntu0.16.04.1

  Server nodes are running 10.2.6 packages as supplied by Ceph.

  All 10.2.* versions are compatible. Using the previous kernel allows
  the connection to work.

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

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


[Kernel-packages] [Bug 1737033] [NEW] upgrading linux-image package to 4.4.0-103.126 breaks Ceph network file system connection

2017-12-07 Thread Benjamin Long
Public bug reported:

After clients have upgraded to 4.4.0-103.126 they can no longer connect
to the Ceph network.

Using the Grub menu to boot the previous kernel fixes the issue.

The error in dmesg is:

[   46.811897] FS-Cache: Loaded
[   46.843670] Key type ceph registered
[   46.844177] libceph: loaded (mon/osd proto 15/24)
[   46.863107] FS-Cache: Netfs 'ceph' registered for caching
[   46.863116] ceph: loaded (mds proto 32)
[   46.884392] libceph: client3354099 fsid 2efbeab1-4903-4c4c-8365-6778afecbcbd
[   46.886856] libceph: mon0 10.10.2.111:6789 session established
[   46.897487] ceph: problem parsing mds trace -5
[   46.897491] ceph: mds parse_reply err -5
[   46.897492] ceph: mdsc_handle_reply got corrupt reply mds0(tid:1)

All clients are running ceph client version:
ii  ceph-fs-common10.2.9-0ubuntu0.16.04.1

Server nodes are running 10.2.6 packages as supplied by Ceph.

All 10.2.* versions are compatible. Using the previous kernel allows the
connection to work.

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


** Tags: ceph cephfs

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

Title:
  upgrading linux-image package to 4.4.0-103.126 breaks Ceph network
  file system connection

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  After clients have upgraded to 4.4.0-103.126 they can no longer
  connect to the Ceph network.

  Using the Grub menu to boot the previous kernel fixes the issue.

  The error in dmesg is:

  [   46.811897] FS-Cache: Loaded
  [   46.843670] Key type ceph registered
  [   46.844177] libceph: loaded (mon/osd proto 15/24)
  [   46.863107] FS-Cache: Netfs 'ceph' registered for caching
  [   46.863116] ceph: loaded (mds proto 32)
  [   46.884392] libceph: client3354099 fsid 
2efbeab1-4903-4c4c-8365-6778afecbcbd
  [   46.886856] libceph: mon0 10.10.2.111:6789 session established
  [   46.897487] ceph: problem parsing mds trace -5
  [   46.897491] ceph: mds parse_reply err -5
  [   46.897492] ceph: mdsc_handle_reply got corrupt reply mds0(tid:1)

  All clients are running ceph client version:
  ii  ceph-fs-common10.2.9-0ubuntu0.16.04.1

  Server nodes are running 10.2.6 packages as supplied by Ceph.

  All 10.2.* versions are compatible. Using the previous kernel allows
  the connection to work.

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

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


[Kernel-packages] [Bug 1736816] Re: system freezed

2017-12-07 Thread Joseph Salisbury
Did this issue start happening after an update/upgrade?  Was there a
prior kernel version where you were not having this particular problem?

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

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

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

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


Thanks in advance.

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


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

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

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

Title:
  system freezed

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  laptop freezed with no response at all. no keyboard keys were working
  . this suddenly happened when i just typing into the word processor.

  my laptop has 6gb RAM and 1TB HDD

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-16-generic 4.13.0-16.19 [modified: 
boot/vmlinuz-4.13.0-16-generic]
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  nilanjan   1424 F pulseaudio
   /dev/snd/controlC0:  nilanjan   1424 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Dec  7 04:02:06 2017
  InstallationDate: Installed on 2017-12-04 (2 days ago)
  InstallationMedia: It
  MachineType: Dell Inc. Inspiron 3537
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=59520f57-087f-4c11-8c5c-580195d38855 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-16-generic N/A
   linux-backports-modules-4.13.0-16-generic  N/A
   linux-firmware 1.169
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/30/2014
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A08
  dmi.board.name: 0N7YKW
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A08
  dmi.modalias: 
dmi:bvnDellInc.:bvrA08:bd04/30/2014:svnDellInc.:pnInspiron3537:pvrA08:rvnDellInc.:rn0N7YKW:rvrA00:cvnDellInc.:ct8:cvrA08:
  dmi.product.family: 00
  dmi.product.name: Inspiron 3537
  dmi.product.version: A08
  dmi.sys.vendor: Dell Inc.

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

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


[Kernel-packages] [Bug 1736808] Re: Changes to overlay lowerdir produce kernel file-caps error

2017-12-07 Thread Joseph Salisbury
** Tags added: kernel-da-key

** Tags added: artful bionic

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

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

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

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

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

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

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

Title:
  Changes to overlay lowerdir produce kernel file-caps error

Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Artful:
  Triaged
Status in linux source package in Bionic:
  Triaged

Bug description:
  In 4.13+ kernels, if you replace an executable file on the lowerdir of
  an Overlay union (such that its inode changes), the system will no
  longer allow you to execute the file via the upperdir. The changes
  introduced to the kernel in this commit...

  
https://github.com/torvalds/linux/commit/8db6c34f1dbc8e06aa016a9b829b06902c3e1340

  ... cause it to report a file security capabilities error.

  ---

  Replication steps and result:

  1. Set up an Overlay union containing some executable files. In my
  case i have an ext4 lowerdir and a tmpfs upperdir, but i don't think
  it matters.

  2. Verify that executing some file (/bin/true for example) on the
  upperdir works.

  3. Replace that file on the lowerdir using mv, rsync, or similar.

  4. Attempt to execute the file on the upperdir again — it will fail.
  The shell will give either 126 or 127 as the return status.

  5. Check the kernel log. A message like the following appears:

  >kernel: Invalid argument reading file caps for /bin/true

  I replicated this on Xenial using the HWE-edge kernel (4.13). The
  error does NOT occur on the HWE kernel (4.10).

  ---

  NOTE: I am aware that the result of changing files on the lowerdir of
  an Overlay union, per the documentation, is undefined — so this is
  probably not a 'bug' per se. However, i wasn't sure it was deliberate,
  either, and it seemed like maybe the previous undefined behaviour was
  nicer than the new undefined behaviour, so i thought i'd report it
  anyway.

  ---

  Config information:

  Ubuntu release: 16.04.3 (Xenial)
  Kernel package: linux-image-generic-hwe-16.04-edge 4.13.0.17.24
  Kernel version signature: Ubuntu 4.13.0-17.20~16.04.1-generic 4.13.8

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

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


[Kernel-packages] [Bug 1736947] Re: Very long boot time with Chelsio T320 10GBASE-R RNIC adapter

2017-12-07 Thread Joseph Salisbury
** Changed in: linux (Ubuntu)
   Status: Confirmed => Incomplete

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

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

Title:
  Very long boot time with Chelsio T320 10GBASE-R RNIC adapter

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I have a Chelsio T320 10GBASE-R RNIC in my machine apparently
  triggering a very long boot time.

  I initially thought about a USB problem as I wrote in ticket #1704614
  but new tests showed me otherwise.

  booting with this parameters yield some interesting things:
  GRUB_CMDLINE_LINUX_DEFAULT="--verbose nosplash debug"

  
  [4.772733] hid-generic 0003:046D:C22D.0009: input,hiddev0,hidraw8: USB 
HID v1.11 Device [Logitech G510 Gaming Keyboard] on 
usb-:00:1d.0-1.8.1.2.2/input1
  [4.877277] usb 2-1.8.1.3.4: New USB device found, idVendor=046d, 
idProduct=c069
  [4.877360] usb 2-1.8.1.3.4: New USB device strings: Mfr=1, Product=2, 
SerialNumber=0
  [4.877440] usb 2-1.8.1.3.4: Product: USB Laser Mouse
  [4.877504] usb 2-1.8.1.3.4: Manufacturer: Logitech
  [4.883052] input: Logitech USB Laser Mouse as 
/devices/pci:00/:00:1d.0/usb2/2-1/2-1.8/2-1.8.1/2-1.8.1.3/2-1.8.1.3.4/2-1.8.1.3.4:1.0/0003:046D:C069.000A/input/input12
  [4.883391] hid-generic 0003:046D:C069.000A: input,hidraw9: USB HID v1.10 
Mouse [Logitech USB Laser Mouse] on usb-:00:1d.0-1.8.1.3.4/input0
  [   62.501496] systemd-udevd[110]: seq 1103 
'/devices/pci:00/:00:01.1/:02:00.0/net/eth0' is taking a long time
  [   91.836493] systemd-udevd[131]: error changing net interface name 'eth0' 
to 'enp2s0': File exists
  [   91.836583] systemd-udevd[131]: could not rename interface '3' from 'eth0' 
to 'enp2s0': File exists
  [   91.908818] raid6: sse2x1   gen()  5176 MB/s
  [   91.976808] raid6: sse2x1   xor()  5202 MB/s
  [   92.044810] raid6: sse2x2   gen() 10397 MB/s
  [   92.112810] raid6: sse2x2   xor()  8718 MB/s
  [   92.180800] raid6: sse2x4   gen() 15554 MB/s
  [   92.248797] raid6: sse2x4   xor() 11584 MB/s
  [   92.248872] raid6: using algorithm sse2x4 gen() 15554 MB/s

  
  systemd-udevd seems to get stuck quite a long time here.

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

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


[Kernel-packages] [Bug 1314762] Re: CVE-2014-0196

2017-12-07 Thread Steve Beattie
** No longer affects: linux-mako (Ubuntu Precise)

** No longer affects: linux-lts-quantal (Ubuntu Vivid)

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

Title:
  CVE-2014-0196

Status in linux package in Ubuntu:
  Invalid
Status in linux-armadaxp package in Ubuntu:
  Invalid
Status in linux-ec2 package in Ubuntu:
  Invalid
Status in linux-flo package in Ubuntu:
  Invalid
Status in linux-fsl-imx51 package in Ubuntu:
  Invalid
Status in linux-goldfish package in Ubuntu:
  Invalid
Status in linux-lts-quantal package in Ubuntu:
  Invalid
Status in linux-lts-raring package in Ubuntu:
  Invalid
Status in linux-lts-saucy package in Ubuntu:
  Invalid
Status in linux-lts-trusty package in Ubuntu:
  Invalid
Status in linux-lts-utopic package in Ubuntu:
  Invalid
Status in linux-lts-vivid package in Ubuntu:
  Invalid
Status in linux-lts-wily package in Ubuntu:
  Invalid
Status in linux-lts-xenial package in Ubuntu:
  Invalid
Status in linux-mako package in Ubuntu:
  Invalid
Status in linux-manta package in Ubuntu:
  Invalid
Status in linux-mvl-dove package in Ubuntu:
  Invalid
Status in linux-raspi2 package in Ubuntu:
  Fix Committed
Status in linux-snapdragon package in Ubuntu:
  New
Status in linux-ti-omap4 package in Ubuntu:
  Invalid
Status in linux source package in Precise:
  Fix Released
Status in linux-armadaxp source package in Precise:
  Fix Released
Status in linux-ec2 source package in Precise:
  Invalid
Status in linux-flo source package in Precise:
  Invalid
Status in linux-fsl-imx51 source package in Precise:
  Invalid
Status in linux-goldfish source package in Precise:
  Invalid
Status in linux-lts-quantal source package in Precise:
  Fix Released
Status in linux-lts-raring source package in Precise:
  Fix Released
Status in linux-lts-saucy source package in Precise:
  Fix Released
Status in linux-lts-trusty source package in Precise:
  Fix Released
Status in linux-lts-utopic source package in Precise:
  Invalid
Status in linux-lts-vivid source package in Precise:
  Invalid
Status in linux-lts-wily source package in Precise:
  Invalid
Status in linux-lts-xenial source package in Precise:
  Invalid
Status in linux-manta source package in Precise:
  Invalid
Status in linux-mvl-dove source package in Precise:
  Invalid
Status in linux-raspi2 source package in Precise:
  Invalid
Status in linux-snapdragon source package in Precise:
  Invalid
Status in linux-ti-omap4 source package in Precise:
  Fix Released
Status in linux source package in Trusty:
  Fix Released
Status in linux-armadaxp source package in Trusty:
  Invalid
Status in linux-ec2 source package in Trusty:
  Invalid
Status in linux-flo source package in Trusty:
  Invalid
Status in linux-fsl-imx51 source package in Trusty:
  Invalid
Status in linux-goldfish source package in Trusty:
  Invalid
Status in linux-lts-quantal source package in Trusty:
  Invalid
Status in linux-lts-raring source package in Trusty:
  Invalid
Status in linux-lts-saucy source package in Trusty:
  Invalid
Status in linux-lts-trusty source package in Trusty:
  Invalid
Status in linux-lts-utopic source package in Trusty:
  Invalid
Status in linux-lts-vivid source package in Trusty:
  Fix Committed
Status in linux-lts-wily source package in Trusty:
  Invalid
Status in linux-lts-xenial source package in Trusty:
  Fix Committed
Status in linux-mako source package in Trusty:
  Invalid
Status in linux-manta source package in Trusty:
  Invalid
Status in linux-mvl-dove source package in Trusty:
  Invalid
Status in linux-raspi2 source package in Trusty:
  Invalid
Status in linux-snapdragon source package in Trusty:
  Invalid
Status in linux-ti-omap4 source package in Trusty:
  Invalid
Status in linux source package in Vivid:
  Invalid
Status in linux-armadaxp source package in Vivid:
  Invalid
Status in linux-ec2 source package in Vivid:
  Invalid
Status in linux-flo source package in Vivid:
  Invalid
Status in linux-fsl-imx51 source package in Vivid:
  Invalid
Status in linux-goldfish source package in Vivid:
  Invalid
Status in linux-lts-raring source package in Vivid:
  Invalid
Status in linux-lts-saucy source package in Vivid:
  Invalid
Status in linux-lts-trusty source package in Vivid:
  Invalid
Status in linux-lts-utopic source package in Vivid:
  Invalid
Status in linux-lts-vivid source package in Vivid:
  Invalid
Status in linux-lts-wily source package in Vivid:
  Invalid
Status in linux-lts-xenial source package in Vivid:
  New
Status in linux-mako source package in Vivid:
  Invalid
Status in linux-manta source package in Vivid:
  Invalid
Status in linux-mvl-dove source package in Vivid:
  Invalid
Status in linux-raspi2 source package in Vivid:
  Invalid
Status in linux-snapdragon source package in Vivid:
  New
Status in linux-ti-omap4 source package in Vivid:
  Invalid
Status in linux source package in Wily:
  Invalid
Status in linux-armadaxp 

[Kernel-packages] [Bug 1694485] Re: Ubuntu17.04: CAPI: call trace seen while error injection to the CAPI card.

2017-12-07 Thread Joseph Salisbury
SRU request submitted:
https://lists.ubuntu.com/archives/kernel-team/2017-December/088684.html

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

Title:
  Ubuntu17.04: CAPI: call trace seen while error injection to  the CAPI
  card.

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

Bug description:
  == Comment: #0 - SUDEESH JOHN  - 2017-03-18 13:55:03 ==
  ---Problem Description---
  call trace while injecting error to the CAPI card.

  " WARNING: CPU: 31 PID: 491 at 
/build/linux-VtwHOM/linux-4.10.0/drivers/misc/cxl/main.c:325 
cxl_adapter_context_unlock+0x68/0x90 [cxl] " 

  ---uname output---
  Linux freak 4.10.0-13-generic #15-Ubuntu SMP Thu Mar 9 20:27:28 UTC 2017 
ppc64le ppc64le ppc64le GNU/Linux
   
  Machine Type = PowerNV 8247-21L 

  ---Steps to Reproduce---
  1. echo 1 > /sys/kernel/debug/powerpc/eeh_max_freezes
  2. echo 1 > /sys/class/cxl/card0/perst_reloads_same_image
  3.  echo 0x8000 > 
/sys/kernel/debug/powerpc/PCI/err_injct_outbound
   
  ---The complete call trace ---

  Mar 18 14:39:09 freak kernel: [  289.675421] [ cut here 
]
  Mar 18 14:39:09 freak kernel: [  289.675431] WARNING: CPU: 5 PID: 491 at 
/build/linux-VtwHOM/linux-4.10.0/drivers/misc/cxl/main.c:325 
cxl_adapter_context_unlock+0x68/0x90 [cxl]
  Mar 18 14:39:09 freak kernel: [  289.675432] 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 kvm_hv kvm_pr kvm ebtable_filter 
ebtables ip6table_filter ip6_tables iptable_filter uio_pdrv_genirq uio 
ipmi_powernv ipmi_devintf ipmi_msghandler powernv_op_panel powernv_rng 
vmx_crypto ibmpowernv leds_powernv ib_iser rdma_cm iw_cm ib_cm ib_core configfs 
iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi ip_tables x_tables autofs4 
btrfs raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx 
xor raid6_pq raid1 raid0 multipath linear ses enclosure scsi_transport_sas 
bnx2x mlx5_core tg3 cxl mdio ipr libcrc32c devlink crc32c_vpmsum pnv_php
  Mar 18 14:39:09 freak kernel: [  289.675490] CPU: 5 PID: 491 Comm: eehd Not 
tainted 4.10.0-13-generic #15-Ubuntu
  Mar 18 14:39:09 freak kernel: [  289.675492] task: c003bfbfde00 
task.stack: c003bfc5c000
  Mar 18 14:39:09 freak kernel: [  289.675493] NIP: d5cc0ca0 LR: 
d5cc0c9c CTR: c0605aa0
  Mar 18 14:39:09 freak kernel: [  289.675495] REGS: c003bfc5f6a0 TRAP: 
0700   Not tainted  (4.10.0-13-generic)
  Mar 18 14:39:09 freak kernel: [  289.675496] MSR: 9282b033 

  Mar 18 14:39:09 freak kernel: [  289.675504]   CR: 28008282  XER: 2000
  Mar 18 14:39:09 freak kernel: [  289.675504] CFAR: c0b568dc SOFTE: 1
  Mar 18 14:39:09 freak kernel: [  289.675504] GPR00: d5cc0c9c 
c003bfc5f920 d5cf2d88 002f
  Mar 18 14:39:09 freak kernel: [  289.675504] GPR04: 0001 
03fd 63206576 
  Mar 18 14:39:09 freak kernel: [  289.675504] GPR08: c15dc700 
  0001
  Mar 18 14:39:09 freak kernel: [  289.675504] GPR12: 8800 
cfb82d00 c0108c88 c003c51f9f00
  Mar 18 14:39:09 freak kernel: [  289.675504] GPR16:  
  
  Mar 18 14:39:09 freak kernel: [  289.675504] GPR20:  
  c0d53990
  Mar 18 14:39:09 freak kernel: [  289.675504] GPR24: c0d53968 
c14a4330 c003ab8fa800 c003bd2c20c0
  Mar 18 14:39:09 freak kernel: [  289.675504] GPR28: c003c5051098 
 c003ab8fa800 
  Mar 18 14:39:09 freak kernel: [  289.675535] NIP [d5cc0ca0] 
cxl_adapter_context_unlock+0x68/0x90 [cxl]
  Mar 18 14:39:09 freak kernel: [  289.675540] LR [d5cc0c9c] 
cxl_adapter_context_unlock+0x64/0x90 [cxl]
  Mar 18 14:39:09 freak kernel: [  289.675541] Call Trace:
  Mar 18 14:39:09 freak kernel: [  289.675547] [c003bfc5f920] 
[d5cc0c9c] cxl_adapter_context_unlock+0x64/0x90 [cxl] (unreliable)
  Mar 18 14:39:09 freak kernel: [  289.675556] [c003bfc5f980] 
[d5cd022c] cxl_configure_adapter+0x954/0x990 [cxl]
  Mar 18 14:39:09 freak kernel: [  289.675563] [c003bfc5fa30] 
[d5cd02c0] cxl_pci_slot_reset+0x58/0x240 [cxl]
  Mar 18 14:39:09 freak kernel: [  289.675568] [c003bfc5fae0] 
[c003b0d4] eeh_report_reset+0x154/0x190
  Mar 18 14:39:09 freak kernel: [  289.675571] [c003bfc5fb20] 
[c0039428] eeh_pe_dev_traverse+0x98/0x170
  Mar 18 14:39:09 freak 

[Kernel-packages] [Bug 1736187] Re: linux-aws: 4.4.0-1043.52 -proposed tracker

2017-12-07 Thread Brad Figg
The package has been published and the bug is being set to Fix Released


** Changed in: kernel-sru-workflow/promote-to-updates
   Status: Fix Committed => 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: 1736181
  phase: Promoted to security
  proposed-announcement-sent: true
  proposed-testing-requested: true
+ kernel-stable-phase:Released
+ kernel-stable-phase-changed:Thursday, 07. December 2017 20:07 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: 1736181
- phase: Promoted to security
+ phase: Released
  proposed-announcement-sent: true
  proposed-testing-requested: true
- kernel-stable-phase:Released
- kernel-stable-phase-changed:Thursday, 07. December 2017 20:07 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-aws in Ubuntu.
https://bugs.launchpad.net/bugs/1736187

Title:
  linux-aws: 4.4.0-1043.52 -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 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 snap-release-to-beta series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-candidate series:
  Confirmed
Status in Kernel SRU Workflow snap-release-to-edge series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-stable series:
  Invalid
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux-aws package in Ubuntu:
  Invalid
Status in linux-aws source package in Xenial:
  Fix Released

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: 1736181
  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/1736187/+subscriptions

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


[Kernel-packages] [Bug 1736181] Re: linux: 4.4.0-103.126 -proposed tracker

2017-12-07 Thread Brad Figg
The package has been published and the bug is being set to Fix Released


** Changed in: kernel-sru-workflow/promote-to-updates
   Status: Fix Committed => 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: 1736182,1736183
  derivatives: 1736185,1736186,1736187,1736188,1736189,1736191
  -- swm properties --
  boot-testing-requested: true
  phase: Promoted to security
  proposed-announcement-sent: true
  proposed-testing-requested: true
+ kernel-stable-phase:Released
+ kernel-stable-phase-changed:Thursday, 07. December 2017 20:03 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
  
  backports: 1736182,1736183
  derivatives: 1736185,1736186,1736187,1736188,1736189,1736191
  -- swm properties --
  boot-testing-requested: true
- phase: Promoted to security
+ phase: Released
  proposed-announcement-sent: true
  proposed-testing-requested: true
- kernel-stable-phase:Released
- kernel-stable-phase-changed:Thursday, 07. December 2017 20:03 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 in Ubuntu.
https://bugs.launchpad.net/bugs/1736181

Title:
  linux: 4.4.0-103.126 -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:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow snap-certification-testing series:
  Confirmed
Status in Kernel SRU Workflow snap-release-to-beta series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-candidate series:
  New
Status in Kernel SRU Workflow snap-release-to-edge series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-stable series:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Fix Released

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: 1736182,1736183
  derivatives: 1736185,1736186,1736187,1736188,1736189,1736191
  -- 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/1736181/+subscriptions

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


[Kernel-packages] [Bug 1736194] Package Released!

2017-12-07 Thread Brad Figg
The package has been published and the bug is being set to 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: 1736195
  derivatives:
  -- swm properties --
  boot-testing-requested: true
  phase: Promoted to updates
  proposed-announcement-sent: true
  proposed-testing-requested: true
+ kernel-stable-phase:Released
+ kernel-stable-phase-changed:Thursday, 07. December 2017 20:01 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
  
  backports: 1736195
  derivatives:
  -- swm properties --
  boot-testing-requested: true
- phase: Promoted to updates
+ phase: Released
  proposed-announcement-sent: true
  proposed-testing-requested: true
- kernel-stable-phase:Released
- kernel-stable-phase-changed:Thursday, 07. December 2017 20:01 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 in Ubuntu.
https://bugs.launchpad.net/bugs/1736194

Title:
  linux: 3.13.0-137.186 -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:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Trusty:
  Fix Released

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: 1736195
  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/1736194/+subscriptions

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


[Kernel-packages] [Bug 1736182] Re: linux-aws: 4.4.0-1005.5 -proposed tracker

2017-12-07 Thread Brad Figg
The package has been published and the bug is being set to Fix Released


** Changed in: kernel-sru-workflow/promote-to-updates
   Status: Fix Committed => 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: 1736181
  phase: Promoted to security
  proposed-announcement-sent: true
  proposed-testing-requested: true
+ kernel-stable-phase:Released
+ kernel-stable-phase-changed:Thursday, 07. December 2017 20:04 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: 1736181
- phase: Promoted to security
+ phase: Released
  proposed-announcement-sent: true
  proposed-testing-requested: true
- kernel-stable-phase:Released
- kernel-stable-phase-changed:Thursday, 07. December 2017 20:04 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-aws in Ubuntu.
https://bugs.launchpad.net/bugs/1736182

Title:
  linux-aws: 4.4.0-1005.5 -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 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:
  New
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux-aws package in Ubuntu:
  Invalid
Status in linux-aws source package in Trusty:
  Fix Released

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: 1736181
  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/1736182/+subscriptions

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


[Kernel-packages] [Bug 1736194] Re: linux: 3.13.0-137.186 -proposed tracker

2017-12-07 Thread Brad Figg
The package has been published and the bug is being set to Fix Released


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

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

Title:
  linux: 3.13.0-137.186 -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:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Trusty:
  Fix Released

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: 1736195
  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/1736194/+subscriptions

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


[Kernel-packages] [Bug 1711407] Re: unregister_netdevice: waiting for lo to become free

2017-12-07 Thread Dan Streetman
simpler reproducer for this using LXD instead of Docker:

1. install/setup LXD
$ sudo apt install lxd
$ sudo lxd init

2. create two containers
$ lxc launch ubuntu:xenial server
$ lxc launch ubuntu:xenial client

3. make the client privileged (so it can mount smb/cifs)
$ lxc config set client security.privileged true
$ lxc stop client
$ lxc start client

4. set up samba server in container
$ lxc exec server apt update
$ lxc exec server apt install cifs-utils samba
$ lxc exec server mkdir /dummy
$ lxc exec server touch /dummy/emptyfile
$ lxc exec server vim /etc/samba/smb.conf

add this section at the end of the container's smb.conf:

[dummy]
  path = /dummy
  browseable = yes
  read only = yes
  guest ok = yes

$ lxc stop server
$ lxc start server

5. note server container's ip
$ lxc list server

e.g.
| server | RUNNING | 10.109.201.68 (eth0) 

6. setup client container
$ lxc exec client mkdir /dummy
$ lxc exec apt update
$ lxc exec apt install cifs-utils

7. stop client container
$ lxc stop client

8. full cycle of client container start through stop
$ lxc start client ; sleep 2 ; lxc exec client -- mount -o guest 
//10.109.201.68/dummy /dummy ; lxc exec client -- ls -l /dummy ; lxc exec 
client umount /dummy ; lxc stop -f client

9. repeat client cycle; it should hang due to this bug
$ lxc start client ; sleep 2 ; lxc exec client -- mount -o guest 
//10.109.201.68/dummy /dummy ; lxc exec client -- ls -l /dummy ; lxc exec 
client umount /dummy ; lxc stop -f client


Note this force-stops the container, instead of normally stopping it; if the 
container is allowed to exit normally, the problem isn't reproduced (with these 
steps, at least).  Also note the 'sleep 2' is there to give enough time for the 
client container network to come up, it may need to be increased if your client 
container takes longer to assign its ip address (you can edit the client 
container nw config to use a static address if you want, which should be 
faster).

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

Title:
  unregister_netdevice: waiting for lo to become free

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

Bug description:
  This is a "continuation" of bug 1403152, as that bug has been marked
  "fix released" and recent reports of failure may (or may not) be a new
  bug.  Any further reports of the problem should please be reported
  here instead of that bug.

  --

  [Impact]

  When shutting down and starting containers the container network
  namespace may experience a dst reference counting leak which results
  in this message repeated in the logs:

  unregister_netdevice: waiting for lo to become free. Usage count =
  1

  This can cause issues when trying to create net network namespace and
  thus block a user from creating new containers.

  [Test Case]

  See comment 16, reproducer provided at https://github.com/fho/docker-
  samba-loop

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

-- 
Mailing list: https://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 1729145] Re: /dev/bcache/by-uuid links not created after reboot

2017-12-07 Thread Ryan Harper
Confirmed bionic works as expected.

I suspect you can send that upstream with my SoB faster than I can.
Definitely interested in seeing if they'll take something like that.

On Thu, Dec 7, 2017 at 1:21 PM, Joseph Salisbury <
joseph.salisb...@canonical.com> wrote:

> Thanks for testing and the patch, Ryan.  I can submit and SRU request.
>
> We should also send this upstream for inclusion in the mainline kernel.
> Is that something you think you can do?  If not, I can do it for you.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1729145
>
> Title:
>   /dev/bcache/by-uuid links not created after reboot
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/
> 1729145/+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/1729145

Title:
  /dev/bcache/by-uuid links not created after reboot

Status in linux package in Ubuntu:
  Triaged
Status in systemd package in Ubuntu:
  New
Status in linux source package in Xenial:
  Triaged
Status in systemd source package in Xenial:
  New
Status in linux source package in Zesty:
  Triaged
Status in systemd source package in Zesty:
  New
Status in linux source package in Artful:
  Triaged
Status in systemd source package in Artful:
  New
Status in linux source package in Bionic:
  Triaged
Status in systemd source package in Bionic:
  New

Bug description:
  1. $ lsb_release -rd
  Description:  Ubuntu 17.10
  Release:  17.10

  2. $ apt-cache policy linux-image-`uname -r`
  linux-image-4.13.0-16-generic:
Installed: 4.13.0-16.19
Candidate: 4.13.0-16.19
Version table:
   *** 4.13.0-16.19 500
  500 http://nova.clouds.archive.ubuntu.com/ubuntu artful/main amd64 
Packages
  100 /var/lib/dpkg/status

  3. After creating some bcache devices and rebooting 
/dev/bcache/by-uuid/ -> ../../bcacheN
  symlinks point to the current bcache device which is caching the dev.uuid 
found after creating a backing device.

  4. /dev/bcache/by-uuid does not exist and there are not symlinks
  underneath

  
  It appears that since the initramfs loads the bcache module which probes and 
finds all of the cache devices and backing devices then once the rootfs is 
mounted and udev gets to run, the bcache kernel module does not emit the 
CACHED_UUID value into the environment if the underlying devices are already 
registered.

  In dmesg, one can see that prior to mounting the rootfs, we see bcache
  register events:

  [5.333973] bcache: register_bdev() registered backing device vdb2
  [5.354138] bcache: register_bdev() registered backing device vdb4
  [5.365665] bcache: register_bdev() registered backing device vdb3
  [5.397720] bcache: bch_journal_replay() journal replay done, 0 keys in 1 
entries, seq 1
  [5.428683] bcache: register_cache() registered cache device vdb1

  then rootfs ismounted and systemd starts systemd-udev

  [9.350889] systemd[1]: Listening on udev Kernel Socket.

  And then the coldplug replay of kernel events triggers 
/lib/udev/rules.d/69-bcache.rules
  which invokes /lib/udev/bcache-register which writes the device name 
(/dev/vdb1 or /dev/bcache0) into /sys/fs/bcache/register and results is the 
bcache kernel driver attempting to register the block device.  However, there 
is already a bcache device associated already and registration fails

  [   11.173141] bcache: register_bcache() error opening /dev/vdb2: device 
already registered
  [   11.184617] bcache: register_bcache() error opening /dev/vdb3: device 
already registered
  [   11.199130] bcache: register_bcache() error opening /dev/vdb1: device 
already registered
  [   11.271694] bcache: register_bcache() error opening /dev/vdb4: device 
already registered

  The problem then is that only a kernel call to bch_cached_dev_run()
  which happens like this:

  bcache_register()
register_bdev()
  bch_cached_dev_run()
kobject_uevent_env(_to_dev(d->disk)->kobj, KOBJ_CHANGE, env);

  where env includes: 
  "DRIVER=bcache",
  kasprintf(GFP_KERNEL, "CACHED_UUID=%pU", dc->sb.uuid),
  NULL,
  NULL,
  };

  Since that event is not emitted for any previously registered device,
  then the symlink will not be created.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-16-generic 4.13.0-16.19
  ProcVersionSignature: User Name 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Oct 31 22:09 seq
   crw-rw 1 root audio 116, 33 Oct 31 22:09 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  

[Kernel-packages] [Bug 1729145] Re: /dev/bcache/by-uuid links not created after reboot

2017-12-07 Thread Joseph Salisbury
Submitted SRU requests:
https://lists.ubuntu.com/archives/kernel-team/2017-December/088680.html
https://lists.ubuntu.com/archives/kernel-team/2017-December/088682.html

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

Title:
  /dev/bcache/by-uuid links not created after reboot

Status in linux package in Ubuntu:
  Triaged
Status in systemd package in Ubuntu:
  New
Status in linux source package in Xenial:
  Triaged
Status in systemd source package in Xenial:
  New
Status in linux source package in Zesty:
  Triaged
Status in systemd source package in Zesty:
  New
Status in linux source package in Artful:
  Triaged
Status in systemd source package in Artful:
  New
Status in linux source package in Bionic:
  Triaged
Status in systemd source package in Bionic:
  New

Bug description:
  1. $ lsb_release -rd
  Description:  Ubuntu 17.10
  Release:  17.10

  2. $ apt-cache policy linux-image-`uname -r`
  linux-image-4.13.0-16-generic:
Installed: 4.13.0-16.19
Candidate: 4.13.0-16.19
Version table:
   *** 4.13.0-16.19 500
  500 http://nova.clouds.archive.ubuntu.com/ubuntu artful/main amd64 
Packages
  100 /var/lib/dpkg/status

  3. After creating some bcache devices and rebooting 
/dev/bcache/by-uuid/ -> ../../bcacheN
  symlinks point to the current bcache device which is caching the dev.uuid 
found after creating a backing device.

  4. /dev/bcache/by-uuid does not exist and there are not symlinks
  underneath

  
  It appears that since the initramfs loads the bcache module which probes and 
finds all of the cache devices and backing devices then once the rootfs is 
mounted and udev gets to run, the bcache kernel module does not emit the 
CACHED_UUID value into the environment if the underlying devices are already 
registered.

  In dmesg, one can see that prior to mounting the rootfs, we see bcache
  register events:

  [5.333973] bcache: register_bdev() registered backing device vdb2
  [5.354138] bcache: register_bdev() registered backing device vdb4
  [5.365665] bcache: register_bdev() registered backing device vdb3
  [5.397720] bcache: bch_journal_replay() journal replay done, 0 keys in 1 
entries, seq 1
  [5.428683] bcache: register_cache() registered cache device vdb1

  then rootfs ismounted and systemd starts systemd-udev

  [9.350889] systemd[1]: Listening on udev Kernel Socket.

  And then the coldplug replay of kernel events triggers 
/lib/udev/rules.d/69-bcache.rules
  which invokes /lib/udev/bcache-register which writes the device name 
(/dev/vdb1 or /dev/bcache0) into /sys/fs/bcache/register and results is the 
bcache kernel driver attempting to register the block device.  However, there 
is already a bcache device associated already and registration fails

  [   11.173141] bcache: register_bcache() error opening /dev/vdb2: device 
already registered
  [   11.184617] bcache: register_bcache() error opening /dev/vdb3: device 
already registered
  [   11.199130] bcache: register_bcache() error opening /dev/vdb1: device 
already registered
  [   11.271694] bcache: register_bcache() error opening /dev/vdb4: device 
already registered

  The problem then is that only a kernel call to bch_cached_dev_run()
  which happens like this:

  bcache_register()
register_bdev()
  bch_cached_dev_run()
kobject_uevent_env(_to_dev(d->disk)->kobj, KOBJ_CHANGE, env);

  where env includes: 
  "DRIVER=bcache",
  kasprintf(GFP_KERNEL, "CACHED_UUID=%pU", dc->sb.uuid),
  NULL,
  NULL,
  };

  Since that event is not emitted for any previously registered device,
  then the symlink will not be created.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-16-generic 4.13.0-16.19
  ProcVersionSignature: User Name 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Oct 31 22:09 seq
   crw-rw 1 root audio 116, 33 Oct 31 22:09 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  Date: Wed Nov  1 01:39:01 2017
  Ec2AMI: ami-030b
  Ec2AMIManifest: FIXME
  Ec2AvailabilityZone: nova
  Ec2InstanceType: m1.small
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lsusb:
   Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: OpenStack Foundation OpenStack Nova
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   

[Kernel-packages] [Bug 1736187] Re: linux-aws: 4.4.0-1043.52 -proposed tracker

2017-12-07 Thread Brad Figg
** Changed in: kernel-sru-workflow/promote-to-security
   Status: Fix Committed => 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: 1736181
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true
+ kernel-stable-phase:Promoted to security
+ kernel-stable-phase-changed:Thursday, 07. December 2017 19:37 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: 1736181
- phase: Promoted to proposed
+ phase: Promoted to security
  proposed-announcement-sent: true
  proposed-testing-requested: true
- kernel-stable-phase:Promoted to security
- kernel-stable-phase-changed:Thursday, 07. December 2017 19:37 UTC

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

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

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

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: 1736181
  phase: Promoted to security
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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


[Kernel-packages] [Bug 1736168] Re: linux: 4.14.0-11.13 -proposed tracker

2017-12-07 Thread Brad Figg
** Changed in: kernel-development-workflow/automated-testing
   Status: Incomplete => Fix Released

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

Title:
  linux: 4.14.0-11.13 -proposed tracker

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

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

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

  -- swm properties --
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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


[Kernel-packages] [Bug 1736152] Package Released!

2017-12-07 Thread Brad Figg
The package has been published and the bug is being set to 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: 1736153,1736154
  derivatives: 1736155
  -- swm properties --
  boot-testing-requested: true
  phase: Promoted to updates
  proposed-announcement-sent: true
  proposed-testing-requested: true
+ kernel-stable-phase:Released
+ kernel-stable-phase-changed:Thursday, 07. December 2017 19: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
  
  backports: 1736153,1736154
  derivatives: 1736155
  -- swm properties --
  boot-testing-requested: true
- phase: Promoted to updates
+ phase: Released
  proposed-announcement-sent: true
  proposed-testing-requested: true
- kernel-stable-phase:Released
- kernel-stable-phase-changed:Thursday, 07. December 2017 19:32 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 in Ubuntu.
https://bugs.launchpad.net/bugs/1736152

Title:
  linux: 4.10.0-42.46 -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:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Zesty:
  Fix Released

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: 1736153,1736154
  derivatives: 1736155
  -- 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/1736152/+subscriptions

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


[Kernel-packages] [Bug 1736152] Re: linux: 4.10.0-42.46 -proposed tracker

2017-12-07 Thread Brad Figg
The package has been published and the bug is being set to Fix Released


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

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

Title:
  linux: 4.10.0-42.46 -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:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Zesty:
  Fix Released

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: 1736153,1736154
  derivatives: 1736155
  -- 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/1736152/+subscriptions

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


[Kernel-packages] [Bug 1736182] Re: linux-aws: 4.4.0-1005.5 -proposed tracker

2017-12-07 Thread Brad Figg
** Changed in: kernel-sru-workflow/promote-to-security
   Status: Fix Committed => 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: 1736181
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true
+ kernel-stable-phase:Promoted to security
+ kernel-stable-phase-changed:Thursday, 07. December 2017 19:34 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: 1736181
- phase: Promoted to proposed
+ phase: Promoted to security
  proposed-announcement-sent: true
  proposed-testing-requested: true
- kernel-stable-phase:Promoted to security
- kernel-stable-phase-changed:Thursday, 07. December 2017 19:34 UTC

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

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

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

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: 1736181
  phase: Promoted to security
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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


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

2017-12-07 Thread Brad Figg
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
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1736194
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true
+ kernel-stable-phase:Released
+ kernel-stable-phase-changed:Thursday, 07. December 2017 19:33 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: 1736194
- phase: Promoted to proposed
+ phase: Released
  proposed-announcement-sent: true
  proposed-testing-requested: true
- kernel-stable-phase:Released
- kernel-stable-phase-changed:Thursday, 07. December 2017 19:33 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/1736195

Title:
  linux-lts-trusty: 3.13.0-137.186~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: 1736194
  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/1736195/+subscriptions

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


[Kernel-packages] [Bug 1729145] Re: /dev/bcache/by-uuid links not created after reboot

2017-12-07 Thread Joseph Salisbury
Thanks for testing and the patch, Ryan.  I can submit and SRU request.

We should also send this upstream for inclusion in the mainline kernel.
Is that something you think you can do?  If not, I can do it for 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/1729145

Title:
  /dev/bcache/by-uuid links not created after reboot

Status in linux package in Ubuntu:
  Triaged
Status in systemd package in Ubuntu:
  New
Status in linux source package in Xenial:
  Triaged
Status in systemd source package in Xenial:
  New
Status in linux source package in Zesty:
  Triaged
Status in systemd source package in Zesty:
  New
Status in linux source package in Artful:
  Triaged
Status in systemd source package in Artful:
  New
Status in linux source package in Bionic:
  Triaged
Status in systemd source package in Bionic:
  New

Bug description:
  1. $ lsb_release -rd
  Description:  Ubuntu 17.10
  Release:  17.10

  2. $ apt-cache policy linux-image-`uname -r`
  linux-image-4.13.0-16-generic:
Installed: 4.13.0-16.19
Candidate: 4.13.0-16.19
Version table:
   *** 4.13.0-16.19 500
  500 http://nova.clouds.archive.ubuntu.com/ubuntu artful/main amd64 
Packages
  100 /var/lib/dpkg/status

  3. After creating some bcache devices and rebooting 
/dev/bcache/by-uuid/ -> ../../bcacheN
  symlinks point to the current bcache device which is caching the dev.uuid 
found after creating a backing device.

  4. /dev/bcache/by-uuid does not exist and there are not symlinks
  underneath

  
  It appears that since the initramfs loads the bcache module which probes and 
finds all of the cache devices and backing devices then once the rootfs is 
mounted and udev gets to run, the bcache kernel module does not emit the 
CACHED_UUID value into the environment if the underlying devices are already 
registered.

  In dmesg, one can see that prior to mounting the rootfs, we see bcache
  register events:

  [5.333973] bcache: register_bdev() registered backing device vdb2
  [5.354138] bcache: register_bdev() registered backing device vdb4
  [5.365665] bcache: register_bdev() registered backing device vdb3
  [5.397720] bcache: bch_journal_replay() journal replay done, 0 keys in 1 
entries, seq 1
  [5.428683] bcache: register_cache() registered cache device vdb1

  then rootfs ismounted and systemd starts systemd-udev

  [9.350889] systemd[1]: Listening on udev Kernel Socket.

  And then the coldplug replay of kernel events triggers 
/lib/udev/rules.d/69-bcache.rules
  which invokes /lib/udev/bcache-register which writes the device name 
(/dev/vdb1 or /dev/bcache0) into /sys/fs/bcache/register and results is the 
bcache kernel driver attempting to register the block device.  However, there 
is already a bcache device associated already and registration fails

  [   11.173141] bcache: register_bcache() error opening /dev/vdb2: device 
already registered
  [   11.184617] bcache: register_bcache() error opening /dev/vdb3: device 
already registered
  [   11.199130] bcache: register_bcache() error opening /dev/vdb1: device 
already registered
  [   11.271694] bcache: register_bcache() error opening /dev/vdb4: device 
already registered

  The problem then is that only a kernel call to bch_cached_dev_run()
  which happens like this:

  bcache_register()
register_bdev()
  bch_cached_dev_run()
kobject_uevent_env(_to_dev(d->disk)->kobj, KOBJ_CHANGE, env);

  where env includes: 
  "DRIVER=bcache",
  kasprintf(GFP_KERNEL, "CACHED_UUID=%pU", dc->sb.uuid),
  NULL,
  NULL,
  };

  Since that event is not emitted for any previously registered device,
  then the symlink will not be created.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-16-generic 4.13.0-16.19
  ProcVersionSignature: User Name 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Oct 31 22:09 seq
   crw-rw 1 root audio 116, 33 Oct 31 22:09 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  Date: Wed Nov  1 01:39:01 2017
  Ec2AMI: ami-030b
  Ec2AMIManifest: FIXME
  Ec2AvailabilityZone: nova
  Ec2InstanceType: m1.small
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lsusb:
   Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: OpenStack Foundation OpenStack Nova
  PciMultimedia:
   
  ProcEnviron:
   

[Kernel-packages] [Bug 1737005] Re: Mainline kernel 4.14 does not start apparmor

2017-12-07 Thread John Johansen
The Ubuntu mainline kernel build unfortunately currently does not have
apparmor set as the default LSM. This is due to some config changes done
when adding the LSM stacking patches (Ubuntu tries to keep the configs
as close as possible). Addressing this is wip and should land with the
next revision of the LSM stacking patches

until then you can enable apparmor by editing the grub kernel command line by 
adding
  security=apparmor

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

Title:
  Mainline kernel 4.14 does not start apparmor

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  With Ubuntu 16.04.3 LTS (Xenial Xerus), and Ubuntu mainline kernel
  4.14.3 or 4.14.4 systemd fails allways starting apparmor.service and
  ureadahead.service. Sometimes udisks2.service fails too.

  $ uname -a
  Linux lieselotte 4.14.4-041404-generic #201712050630 SMP Tue Dec 5 12:07:25 
UTC 2017 i686 i686 i686 GNU/Linux

  $ systemctl --failed
    UNIT   LOAD   ACTIVE SUBDESCRIPTION
  ● apparmor.service   loaded failed failed LSB: AppArmor initialization
  ● udisks2.serviceloaded failed failed Disk Manager
  ● ureadahead.service loaded failed failed Read required files in advance

  $ systemctl status apparmor.service
  ● apparmor.service - LSB: AppArmor initialization
     Loaded: loaded (/etc/init.d/apparmor; bad; vendor preset: enabled)
     Active: failed (Result: exit-code) since Do 2017-12-07 18:04:51 CET; 52min 
ago
   Docs: man:systemd-sysv-generator(8)
    Process: 689 ExecStart=/etc/init.d/apparmor start (code=exited, 
status=1/FAILURE)

  Dez 07 18:04:51 lieselotte systemd[1]: Starting LSB: AppArmor 
initialization...
  Dez 07 18:04:51 lieselotte apparmor[689]:  * Starting AppArmor profiles
  Dez 07 18:04:51 lieselotte apparmor[689]:  * AppArmor not available as kernel 
LSM.
  Dez 07 18:04:51 lieselotte apparmor[689]:...fail!
  Dez 07 18:04:51 lieselotte systemd[1]: apparmor.service: Control process 
exited, code=exited status=1
  Dez 07 18:04:51 lieselotte systemd[1]: Failed to start LSB: AppArmor 
initialization.
  Dez 07 18:04:51 lieselotte systemd[1]: apparmor.service: Unit entered failed 
state.
  Dez 07 18:04:51 lieselotte systemd[1]: apparmor.service: Failed with result 
'exit-code'.

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

-- 
Mailing list: https://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 1729145] Re: /dev/bcache/by-uuid links not created after reboot

2017-12-07 Thread Ryan Harper
Tested the xenial update.  I had one boot where the links didn't get
created, but I cannot recreate that issue now.

On Thu, Dec 7, 2017 at 9:56 AM, Ryan Harper <ryan.har...@canonical.com>
wrote:

> Here's the Zesty test; all looks good.
>
> ubuntu@ubuntu:~$ cat /etc/cloud/build.info
> build_name: server
> serial: 20171207
> ubuntu@ubuntu:~$ uname -a
> Linux ubuntu 4.10.0-40-generic #44~lp1729145 SMP Wed Dec 6 16:21:45 UTC
> 2017 x86_64 x86_64 x86_64 GNU/Linux
> ubuntu@ubuntu:~$ tree /dev/bcache
> /dev/bcache [error opening dir]
>
> 0 directories, 0 files
>
> $ sudo dpkg --install linux-image-4.10.0-40-generic_
> 4.10.0-40.44~lp1729145_amd64.deb
> dpkg: warning: downgrading linux-image-4.10.0-40-generic from 4.10.0-40.44
> to 4.10.0-40.44~lp1729145
> (Reading database ... 56846 files and directories currently installed.)
> Preparing to unpack linux-image-4.10.0-40-generic_
> 4.10.0-40.44~lp1729145_amd64.deb ...
> Done.
> Unpacking linux-image-4.10.0-40-generic (4.10.0-40.44~lp1729145) over
> (4.10.0-40.44) ...
> Examining /etc/kernel/postrm.d .
> run-parts: executing /etc/kernel/postrm.d/initramfs-tools
> 4.10.0-40-generic /boot/vmlinuz-4.10.0-40-generic
> run-parts: executing /etc/kernel/postrm.d/x-grub-legacy-ec2
> 4.10.0-40-generic /boot/vmlinuz-4.10.0-40-generic
> run-parts: executing /etc/kernel/postrm.d/zz-update-grub
> 4.10.0-40-generic /boot/vmlinuz-4.10.0-40-generic
> Setting up linux-image-4.10.0-40-generic (4.10.0-40.44~lp1729145) ...
> Running depmod.
> update-initramfs: deferring update (hook will be called later)
> Not updating initrd symbolic links since we are being updated/reinstalled
> (4.10.0-40.44 was configured last, according to dpkg)
> Not updating image symbolic links since we are being updated/reinstalled
> (4.10.0-40.44 was configured last, according to dpkg)
> Examining /etc/kernel/postinst.d.
> run-parts: executing /etc/kernel/postinst.d/apt-auto-removal
> 4.10.0-40-generic /boot/vmlinuz-4.10.0-40-generic
> run-parts: executing /etc/kernel/postinst.d/initramfs-tools
> 4.10.0-40-generic /boot/vmlinuz-4.10.0-40-generic
> update-initramfs: Generating /boot/initrd.img-4.10.0-40-generic
> W: mdadm: /etc/mdadm/mdadm.conf defines no arrays.
> run-parts: executing /etc/kernel/postinst.d/unattended-upgrades
> 4.10.0-40-generic /boot/vmlinuz-4.10.0-40-generic
> run-parts: executing /etc/kernel/postinst.d/update-notifier
> 4.10.0-40-generic /boot/vmlinuz-4.10.0-40-generic
> run-parts: executing /etc/kernel/postinst.d/x-grub-legacy-ec2
> 4.10.0-40-generic /boot/vmlinuz-4.10.0-40-generic
> Searching for GRUB installation directory ... found: /boot/grub
> Searching for default file ... found: /boot/grub/default
> Testing for an existing GRUB menu.lst file ... found: /boot/grub/menu.lst
> Searching for splash image ... none found, skipping ...
> Found kernel: /boot/vmlinuz-4.10.0-40-generic
> Found kernel: /boot/vmlinuz-4.10.0-40-generic
> Updating /boot/grub/menu.lst ... done
>
> run-parts: executing /etc/kernel/postinst.d/zz-update-grub
> 4.10.0-40-generic /boot/vmlinuz-4.10.0-40-generic
> Generating grub configuration file ...
> Found linux image: /boot/vmlinuz-4.10.0-40-generic
> Found initrd image: /boot/initrd.img-4.10.0-40-generic
> done
> ubuntu@ubuntu:~$ sudo reboot
> ...
>
> ubuntu@ubuntu:~$ dpkg --list | grep linux-image
> ii  linux-image-4.10.0-40-generic  4.10.0-40.44~lp1729145
>  amd64Linux kernel image for version 4.10.0 on 64
> bit x86 SMP
> ii  linux-image-virtual4.10.0.40.40
>  amd64Virtual Linux kernel image
> ubuntu@ubuntu:~$ sudo tree /dev/bcache
> /dev/bcache
> ├── by-label
> │   ├── backing0 -> ../../bcache2
> │   └── backing1 -> ../../bcache0
> └── by-uuid
> ├── 1375d23f-4780-46d7-9fca-c397f8333685 -> ../../bcache3
> ├── 57e009b1-6bf4-42ea-abe0-334b10941a0b -> ../../bcache0
> ├── 7ce7dc32-7da9-42a8-899a-5d21ed7ea714 -> ../../bcache1
> └── 92d882d8-38cd-4537-847b-6f9c40ba67b4 -> ../../bcache2
>
> 2 directories, 6 files
>
>
> On Wed, Dec 6, 2017 at 11:00 AM, Joseph Salisbury <
> joseph.salisb...@canonical.com> wrote:
>
>> I built Xenial, Zesty and Bionic test kernels with your patch.  They can
>> also be downloaded from:
>>
>> http://kernel.ubuntu.com/~jsalisbury/lp1729145/
>>
>> Can those that can reproduce this bug give this test kernel a try?
>>
>>
>> Zesty required upstream commit 4b758df21 as a prereq.  Zesty never got
>> it, since upstream 4.10 is EOL.  Zesty would be the more important test
>> kernel to try due to this difference.
>>
>> Thanks again.
>>
>> --
>> You re

[Kernel-packages] [Bug 1734327] Re: Kernel panic on a nfsroot system

2017-12-07 Thread Joseph Salisbury
I built one more test kernel.  This one only has commit 4ae2508
reverted.

The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1734327/revert-test

Can you test that kernel and report back if it has the bug or not?

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

Title:
  Kernel panic on a nfsroot system

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

Bug description:
  Summary:
  Kernel panic occurs after multiple TCP connection creations/closures to the 
localhost.
  The bug was found using STAF RPC calls, but is easily reproducible with SSH.
  The bug doesn't appear on an identical virtual machine booting from the disk.
  The bug is not reproducible on a similarly-prepared Ubuntu 16.04 machine.
  The bug is reproducible using an older 4.13.0-16-generic kernel
  Reproducible on multiple hardware types.
  Unable to create a kernel memory dump due to makedumpfile errors.
  apport-bug save attached.

  NFSRoot boot options:
  vmlinuz initrd=initrd.img boot=nfs root=/dev/nfs 
nfsroot=190.0.0.254:/diskless/host/u1616/Ubuntu/17.10 intel_iommu=on 
net.ifnames=0 biosdevname=0 apparmor=0 ip=:eth0:dhcp 
blacklist=i40e,ixgbe,fm10k crashkernel=384M-:768M rw

  Software:
  OS: Ubuntu 17.10
  Kernel: 4.13.0-17-generic x86_64

  Reproduction steps:
  1. Boot a system from a nfsroot
  2. Configure password-less localhost ssh access
  3. Run a loop: `while true; do ssh localhost 'uname -a'; done`
  4. Wait for system to crash

  Trace:
  4,1151,52372730,-;general protection fault:  [#1] SMP
  4,1152,52372771,-;Modules linked in: arc4 md4 rpcsec_gss_krb5 nls_utf8 
auth_rpcgss cifs nfsv4 ccm ipmi_ssif intel_rapl sb_edac x86_pkg_temp_thermal 
intel_powerclamp coretemp intel_cstate mei_me input_leds joydev intel_rapl_perf 
mei kvm_intel lpc_ich ioatdma kvm irqbypass ipmi_si ipmi_devintf 
ipmi_msghandler shpchp acpi_pad acpi_power_meter mac_hid ib_iser rdma_cm iw_cm 
ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi ip_tables 
x_tables autofs4 nfsv3 nfs_acl nfs lockd grace sunrpc fscache raid10 raid456 
async_raid6_recov async_memcpy async_pq async_xor async_tx xor hid_generic 
usbhid hid raid6_pq libcrc32c raid1 raid0 multipath linear uas usb_storage 
crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc ast ttm aesni_intel igb 
drm_kms_helper aes_x86_64 crypto_simd syscopyarea glue_helper
  4,1153,52373251,c; sysfillrect dca cryptd sysimgblt i2c_algo_bit fb_sys_fops 
ahci ptp drm libahci pps_core wmi
  4,1154,52373322,-;CPU: 11 PID: 1848 Comm: STAFProc Not tainted 
4.13.0-17-generic #20-Ubuntu
  4,1155,52373371,-;Hardware name: Supermicro Super Server/X10SRD-F, BIOS 2.0 
12/17/2015
  4,1156,52373418,-;task: 9d09267f5d00 task.stack: afddc3a7
  4,1157,52373461,-;RIP: 0010:kfree+0x53/0x160
  4,1158,52373486,-;RSP: 0018:9d092ecc3bc8 EFLAGS: 00010207
  4,1159,52373521,-;RAX:  RBX: 241c89490001 RCX: 
0004
  4,1160,52373566,-;RDX: 32d49081cc08 RSI: 00010080 RDI: 
62fac000
  4,1161,52373611,-;RBP: 9d092ecc3be0 R08: 0001f4c0 R09: 
943bb839
  4,1162,52373656,-;R10: 00904c789100 R11:  R12: 
9d09267ef000
  4,1163,52373701,-;R13: 93fa155e R14: 9d09267ef000 R15: 
9d09267ef000
  4,1164,52373746,-;FS:  7f3a53313700() GS:9d092ecc() 
knlGS:
  4,1165,52373797,-;CS:  0010 DS:  ES:  CR0: 80050033
  4,1166,52373834,-;CR2: 7fd5c9ffa780 CR3: 0004666d7000 CR4: 
003406e0
  4,1167,52373878,-;DR0:  DR1:  DR2: 

  4,1168,52373923,-;DR3:  DR6: fffe0ff0 DR7: 
0400
  4,1169,52373968,-;Call Trace:
  4,1170,52373987,-; 
  4,1171,52374009,-; security_sk_free+0x3e/0x50
  4,1172,52374042,-; __sk_destruct+0x108/0x190
  4,1173,52374070,-; sk_destruct+0x20/0x30
  4,1174,52374095,-; __sk_free+0x82/0xa0
  4,1175,52374120,-; sk_free+0x19/0x20
  4,1176,52374144,-; sock_put+0x14/0x20
  4,1177,52374168,-; tcp_v4_rcv+0x94d/0x9d0
  4,1178,52374195,-; ip_local_deliver_finish+0x5c/0x1f0
  4,1179,52374226,-; ip_local_deliver+0x6f/0xe0
  4,1180,52374254,-; ip_rcv_finish+0x120/0x410
  4,1181,52374281,-; ip_rcv+0x28c/0x3a0
  4,1182,52374305,-; ? update_load_avg+0x46d/0x590
  4,1183,52374335,-; __netif_receive_skb_core+0x39a/0xaa0
  4,1184,52374369,-; __netif_receive_skb+0x18/0x60
  4,1185,52374398,-; ? __netif_receive_skb+0x18/0x60
  4,1186,52374428,-; process_backlog+0x89/0x140
  4,1187,52374457,-; net_rx_action+0x13b/0x380
  4,1188,52374485,-; __do_softirq+0xde/0x2a5
  4,1189,52375837,-; do_softirq_own_stack+0x1c/0x30
  4,1190,52377188,-; 
  4,1191,52378538,-; do_softirq.part.17+0x4e/0x50
  4,1192,52379869,-; __local_bh_enable_ip+0x5a/0x60
  4,1193,52381174,-; 

[Kernel-packages] [Bug 1481347] Re: Power8 Nest PMU Instrumentation support

2017-12-07 Thread bugproxy
** Tags removed: verification-needed-artful
** Tags added: verification-done-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/1481347

Title:
  Power8 Nest PMU Instrumentation support

Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Artful:
  Fix Released

Bug description:
  This is a bug for Canonical awareness that we want to have the
  following patches included in 15.10.

  They are still under development/review:

  https://patchwork.ozlabs.org/patch/482968/
  https://patchwork.ozlabs.org/patch/482969/
  https://patchwork.ozlabs.org/patch/482970/
  https://patchwork.ozlabs.org/patch/482971/
  https://patchwork.ozlabs.org/patch/482972/
  https://patchwork.ozlabs.org/patch/482973/
  https://patchwork.ozlabs.org/patch/482974/

  Patches under review.

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

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


[Kernel-packages] [Bug 1711407] Re: unregister_netdevice: waiting for lo to become free

2017-12-07 Thread Dan Streetman
> In both of our reproducers, we added "ip route flush table all;

that won't help

> ifconfig down;

that's not a valid cmdline

> sleep 10" before existing from containers.

sleeping without closing existing open sockets doesn't help

what are you using for container mgmt?  docker?  lxc?  lxd?

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

Title:
  unregister_netdevice: waiting for lo to become free

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

Bug description:
  This is a "continuation" of bug 1403152, as that bug has been marked
  "fix released" and recent reports of failure may (or may not) be a new
  bug.  Any further reports of the problem should please be reported
  here instead of that bug.

  --

  [Impact]

  When shutting down and starting containers the container network
  namespace may experience a dst reference counting leak which results
  in this message repeated in the logs:

  unregister_netdevice: waiting for lo to become free. Usage count =
  1

  This can cause issues when trying to create net network namespace and
  thus block a user from creating new containers.

  [Test Case]

  See comment 16, reproducer provided at https://github.com/fho/docker-
  samba-loop

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

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


[Kernel-packages] [Bug 1728098] Re: [kernel] tty/hvc: Use opal irqchip interface if available

2017-12-07 Thread bugproxy
** 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/1728098

Title:
  [kernel] tty/hvc: Use opal irqchip interface if available

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

Bug description:

  == SRU Justification ==
  This bug is fixed by commit 00dab8187e18.  The commit updates the hvc
  driver to use the OPAL irqchip if made available by the running firmware.
  If it is not present, the driver falls back to the existing OPAL event 
number.   

  Commit 00dab8187e18 was added to mainline is v4.8-rc1, so it is not needed in 
  releases newer than Xenial.  The commit is a clean cherry pick in Xenial.

  
  == Fix ==
  commit 00dab8187e182da41122f66c207707b192509df4
  Author: Sam Mendoza-Jonas 
  Date:   Mon Jul 11 13:38:58 2016 +1000

  tty/hvc: Use opal irqchip interface if available

  
  == Regression Potential ==
  This change is specific to the hvc driver and has been in mainline since 
v4.8-rc1
  without any issues reported.

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

  
  ---Problem Description---
  Please backport console irq patch .

  commit 00dab8187e182da41122f66c207707b192509df4
  Author: Sam Mendoza-Jonas 
  Date:   Mon Jul 11 13:38:58 2016 +1000

  tty/hvc: Use opal irqchip interface if available

  Update the hvc driver to use the OPAL irqchip if made available by the
  running firmware. If it is not present, the driver falls back to the
  existing OPAL event number.

  Signed-off-by: Samuel Mendoza-Jonas 
  Signed-off-by: Michael Ellerman 

  ---uname output---
  Linux tul217p1 4.4.0-98-generic #121-Ubuntu SMP Tue Oct 10 14:23:01 UTC 2017 
ppc64le ppc64le ppc64le GNU/Linux

  Machine Type = FSP based PowerNV system

  Canonical,

  We need this patch in 16.04 GA 4.4 kernel. This fix will avoid the
  following error:

  Oct 19 22:15:07 tul217p1 kernel: sched: RT throttling activated
  Oct 19 22:15:49 tul217p1 kernel: INFO: rcu_sched self-detected stall on CPU
  Oct 19 22:15:49 tul217p1 kernel:21-...: (85 GPs behind) 
idle=d29/142/0 softirq=26316/26316 fqs=4417
  Oct 19 22:15:49 tul217p1 kernel: (t=5250 jiffies g=30019 c=30018 
q=20591)
  Oct 19 22:15:49 tul217p1 kernel: Call Trace:
  Oct 19 22:15:49 tul217p1 kernel: [c007f4d0f110] [c00fcbe0] 
sched_show_task+0xe0/0x180 (unreliable)
  Oct 19 22:15:49 tul217p1 kernel: [c007f4d0f180] [c013fcf4] 
rcu_dump_cpu_stacks+0xe4/0x150
  Oct 19 22:15:49 tul217p1 kernel: [c007f4d0f1d0] [c0145424] 
rcu_check_callbacks+0x6b4/0x9b0
  Oct 19 22:15:49 tul217p1 kernel: [c007f4d0f300] [c014d288] 
update_process_times+0x58/0xa0
  Oct 19 22:15:49 tul217p1 kernel: [c007f4d0f330] [c01649b8] 
tick_sched_handle.isra.6+0x48/0xe0
  Oct 19 22:15:49 tul217p1 kernel: [c007f4d0f370] [c0164ab4] 
tick_sched_timer+0x64/0xd0
  Oct 19 22:15:49 tul217p1 kernel: [c007f4d0f3b0] [c014dd54] 
__hrtimer_run_queues+0x124/0x450
  Oct 19 22:15:49 tul217p1 kernel: [c007f4d0f440] [c014ed7c] 
hrtimer_interrupt+0xec/0x2c0
  Oct 19 22:15:49 tul217p1 kernel: [c007f4d0f500] [c001f5fc] 
__timer_interrupt+0x8c/0x290
  Oct 19 22:15:49 tul217p1 kernel: [c007f4d0f550] [c001f9b0] 
timer_interrupt+0xa0/0xe0
  Oct 19 22:15:49 tul217p1 kernel: [c007f4d0f580] [c00099d8] 
restore_check_irq_replay+0x54/0x70
  Oct 19 22:15:49 tul217p1 kernel: --- interrupt: 901 at 
arch_local_irq_restore+0x74/0x90
   LR = arch_local_irq_restore+0x74/0x90
  Oct 19 22:15:49 tul217p1 kernel: [c007f4d0f870] [7fff] 
0x7fff (unreliable)
  Oct 19 22:15:49 tul217p1 kernel: [c007f4d0f890] [c00bf808] 
__do_softirq+0xd8/0x3e0
  Oct 19 22:15:49 tul217p1 kernel: [c007f4d0f980] [c00bfd88] 
irq_exit+0xc8/0x100
  Oct 19 22:15:49 tul217p1 kernel: [c007f4d0f9a0] [c001f9b4] 
timer_interrupt+0xa4/0xe0
  Oct 19 22:15:49 tul217p1 kernel: [c007f4d0f9d0] [c00099d8] 
restore_check_irq_replay+0x54/0x70
  Oct 19 22:15:49 tul217p1 kernel: --- interrupt: 901 at 
irq_work_queue+0x60/0xd0
   LR = irq_work_queue+0xa4/0xd0
  Oct 19 22:15:49 tul217p1 kernel: [c007f4d0fcc0] [c007f4d0fd00] 
0xc007f4d0fd00 (unreliable)
  Oct 19 22:15:49 tul217p1 kernel: [c007f4d0fcf0] [c0076a98] 
opal_handle_events+0x108/0x130
  Oct 19 22:15:49 tul217p1 kernel: [c007f4d0fd40] [c0070fc8] 

[Kernel-packages] [Bug 1735977] Re: Using asymmetric key for IMA appraisal crashes the system in Ubuntu 16.04

2017-12-07 Thread Joseph Salisbury
SRU request submitted:
https://lists.ubuntu.com/archives/kernel-team/2017-December/088677.html

** Description changed:

+ 
+ == SRU Justification ==
+ The bug reporter was trying to enable IMA appraisal with signatures for 
executable 
+ files on Xenial.  However, when enabling IMA appriasl the system would crash
+ and generate a trace.
+ 
+ This bug is happening because the following commit was applied to Xenial in 
bug 1569924:
+ db6c43bd2132 ("crypto: KEYS: convert public key and digsig asym to the 
akcipher api")
+ 
+ However, the following commit is also required or this bug happens:
+ eb5798f2e28f ("integrity: convert digsig to akcipher api")
+ 
+ 
+ == Fix ==
+ commit eb5798f2e28f3b43091cecc71c84c3f6fb35c7de
+ Author: Tadeusz Struk 
+ Date:   Tue Feb 2 10:08:58 2016 -0800
+ 
+ integrity: convert digsig to akcipher api
+ 
+ == Regression Potential ==
+ The requested commit is requred to fix an existing regression caused by bug 
1569924.
+ 
+ == Test Case ==
+ A test kernel was built with this patch and tested by the original bug 
reporter.
+ The bug reporter states the test kernel resolved the bug.
+ 
+ 
+ 
+ == Original Bug Description ==
  I'm trying to enable IMA appraisal with signatures for executable files on 
xenial with Linux 4.4. I took the following steps:
  * Downloaded ubuntu-xenial kernel sources
  * Run fakeroot debian/rules editconfigs to set CONFIG_SYSTEM_TRUSTED_KEYS to 
my key
  * Run fakeroot debian/rules binary-headers binary-generic binary-perarch to 
build the kernel deb packaes
  * Installed the kernel
  * Signed the filesystem with my key using 'evmctl sing'
  * Enabled IMA policy so that it will include the following line
-   appraise fowner=0 appraise_type=imasig
+   appraise fowner=0 appraise_type=imasig
  * From this point invocation of a signed binary cases a kernel BUG():
  
  [ 1395.036910] kernel BUG at 
/home/rapoport/git/ubuntu-xenial/crypto/asymmetric_keys/public_key.c:80!
- [ 1395.038963] invalid opcode:  [#1] SMP 
+ [ 1395.038963] invalid opcode:  [#1] SMP
  [ 1395.039973] Modules linked in: isofs ppdev kvm_intel kvm irqbypass joydev 
input_leds serio_raw parport_pc parport 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 libcrc32c raid1 raid0 multipath linear crct10dif_pclmul 
crc32_pclmul ghash_clmulni_intel aesni_intel aes_x86_64 lrw gf128mul 
glue_helper ablk_helper psmouse cryptd floppy
  [ 1395.050761] CPU: 6 PID: 31586 Comm: bash Not tainted 4.4.0-101-generic #124
  [ 1395.051909] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 
Ubuntu-1.8.2-1ubuntu1 04/01/2014
  [ 1395.053510] task: 8800bae9c600 ti: 88042c52c000 task.ti: 
88042c52c000
  [ 1395.054763] RIP: 0010:[]  [] 
public_key_verify_signature+0x46/0x50
  [ 1395.056406] RSP: 0018:88042c52fa98  EFLAGS: 00010246
  [ 1395.057307] RAX: 813bdb80 RBX: fff4 RCX: 
0001
  [ 1395.058518] RDX: 81ea73c0 RSI: 88042c52fac8 RDI: 
88042a107c10
  [ 1395.059709] RBP: 88042c52faa0 R08: 88042a849100 R09: 
0007
  [ 1395.061109] R10: 88042a0f9d00 R11: 88042c52fb07 R12: 
0080
  [ 1395.062289] R13: 88042abd9a80 R14: 0014 R15: 
88042a849ac4
  [ 1395.063404] FS:  7f5e21958700() GS:88043fd8() 
knlGS:
  [ 1395.064771] CS:  0010 DS:  ES:  CR0: 80050033
  [ 1395.065809] CR2: 7f5e20f5c3cc CR3: 00042cabc000 CR4: 
000406e0
  [ 1395.067058] Stack:
  [ 1395.067540]  813bdb95 88042c52fab0 813bdaec 
88042c52fb38
  [ 1395.068964]  813a759e 88042c52fac8  

  [ 1395.070417]  88042a849ac4 02000114 88042a849100 

  [ 1395.071973] Call Trace:
  [ 1395.072510]  [] ? public_key_verify_signature_2+0x15/0x20
  [ 1395.073605]  [] verify_signature+0x3c/0x50
  [ 1395.074526]  [] asymmetric_verify+0x17e/0x2a0
  [ 1395.075475]  [] integrity_digsig_verify+0x70/0x110
  [ 1395.076481]  [] ima_appraise_measurement+0x244/0x420
  [ 1395.077518]  [] process_measurement+0x3fa/0x480
  [ 1395.078479]  [] ima_file_check+0x18/0x20
  [ 1395.079381]  [] path_openat+0x1f3/0x1330
  [ 1395.080274]  [] ? __slab_free+0xcb/0x2c0
  [ 1395.081165]  [] do_filp_open+0x91/0x100
  [ 1395.082050]  [] ? apparmor_cred_prepare+0x2f/0x50
  [ 1395.083046]  [] ? security_prepare_creds+0x43/0x60
  [ 1395.084056]  [] do_open_execat+0x78/0x1d0
  [ 1395.084952]  [] do_execveat_common.isra.33+0x240/0x760
  [ 1395.086016]  [] SyS_execve+0x3a/0x50
  [ 1395.086877]  [] stub_execve+0x5/0x5
  [ 1395.087711]  [] ? entry_SYSCALL_64_fastpath+0x16/0x71
- [ 1395.088746] Code: 2a 0f b6 57 0c b8 bf ff ff ff 80 fa 01 77 14 48 8b 14 d5 
b0 05 a5 81 48 85 d2 74 07 55 48 89 e5 ff d2 5d f3 c3 0f 0b 0f 0b 0f 0b 

[Kernel-packages] [Bug 1736118] Re: linux: 4.13.0-19.22 -proposed tracker

2017-12-07 Thread Brad Figg
The package has been published and the bug is being set to Fix Released


** Changed in: kernel-sru-workflow/promote-to-updates
   Status: Fix Committed => 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: 1736120,1736121,1736123,1736124
  derivatives: 1736125
  -- swm properties --
  boot-testing-requested: true
  phase: Promoted to security
  proposed-announcement-sent: true
  proposed-testing-requested: true
+ kernel-stable-phase:Released
+ kernel-stable-phase-changed:Thursday, 07. December 2017 18:35 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
  
  backports: 1736120,1736121,1736123,1736124
  derivatives: 1736125
  -- swm properties --
  boot-testing-requested: true
- phase: Promoted to security
+ phase: Released
  proposed-announcement-sent: true
  proposed-testing-requested: true
- kernel-stable-phase:Released
- kernel-stable-phase-changed:Thursday, 07. December 2017 18:35 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 in Ubuntu.
https://bugs.launchpad.net/bugs/1736118

Title:
  linux: 4.13.0-19.22 -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:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Artful:
  Fix Released

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: 1736120,1736121,1736123,1736124
  derivatives: 1736125
  -- 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/1736118/+subscriptions

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


[Kernel-packages] [Bug 1730648] Re: Switch Vcs-Git: url to fully expanded form

2017-12-07 Thread Launchpad Bug Tracker
This bug was fixed in the package linux-meta-aws - 4.4.0.1005.5

---
linux-meta-aws (4.4.0.1005.5) trusty; urgency=medium

  * Bump ABI 4.4.0-1005

 -- Kamal Mostafa   Mon, 04 Dec 2017 12:20:48 -0800

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

Title:
  Switch Vcs-Git: url to fully expanded form

Status in linux-aws package in Ubuntu:
  Invalid
Status in linux-meta-aws package in Ubuntu:
  Invalid
Status in linux-aws source package in Trusty:
  Fix Released
Status in linux-meta-aws source package in Trusty:
  Fix Released
Status in linux-aws source package in Xenial:
  Fix Released
Status in linux-meta-aws source package in Xenial:
  Fix Released

Bug description:
  We have some URLs which are short form.  These are not clear and there
  is a risk of those changing later.  Where we have more than one series
  active they should be updated to point to the series repository.

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

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


[Kernel-packages] [Bug 1730648] Re: Switch Vcs-Git: url to fully expanded form

2017-12-07 Thread Launchpad Bug Tracker
This bug was fixed in the package linux-aws - 4.4.0-1005.5

---
linux-aws (4.4.0-1005.5) trusty; urgency=low

  * linux-aws: 4.4.0-1005.5 -proposed tracker (LP: #1736182)

  * Update config with NET_DSA=n as required by changes in
 upstream stable update to 4.4.98 (LP: #1732698)

  [ Ubuntu: 4.4.0-103.126 ]

  * linux: 4.4.0-103.126 -proposed tracker (LP: #1736181)
  * CVE-2017-1000405
- mm, thp: Do not make page table dirty unconditionally in touch_p[mu]d()
  * CVE-2017-16939
- netlink: add a start callback for starting a netlink dump
- ipsec: Fix aborted xfrm policy dump crash

  [ Ubuntu: 4.4.0-102.125 ]

  * linux: 4.4.0-102.125 -proposed tracker (LP: #1733541)
  * tar -x sometimes fails on overlayfs (LP: #1728489)
- ovl: check if all layers are on the same fs
- ovl: persistent inode number for directories
  * NVMe timeout is too short (LP: #1729119)
- nvme: update timeout module parameter type
  * Set PANIC_TIMEOUT=10 on Power Systems (LP: #1730660)
- [Config]: Set PANIC_TIMEOUT=10 on ppc64el
  * Cannot pair BLE remote devices when using combo BT SoC (LP: #1731467)
- Bluetooth: increase timeout for le auto connections
  * CIFS errors on 4.4.0-98, but not on 4.4.0-97 with same config (LP: #1729337)
- SMB3: Validate negotiate request must always be signed
  * Plantronics P610 does not support sample rate reading (LP: #1719853)
- ALSA: usb-audio: Add sample rate quirk for Plantronics P610
  * Invalid btree pointer causes the kernel NULL pointer dereference
(LP: #1729256)
- xfs: reinit btree pointer on attr tree inactivation walk
  * Samba mount/umount in docker container triggers kernel Oops (LP: #1729637)
- ipv6: only call ip6_route_dev_notify() once for NETDEV_UNREGISTER
- ipv6: fix NULL dereference in ip6_route_dev_notify()
  * [kernel] tty/hvc: Use opal irqchip interface if available (LP: #1728098)
- tty/hvc: Use opal irqchip interface if available
  * Device hotplugging with MPT SAS cannot work for VMWare ESXi (LP: #1730852)
- scsi: mptsas: Fixup device hotplug for VMWare ESXi
  * NMI watchdog: BUG: soft lockup on Guest upon boot (KVM) (LP: #1727331)
- KVM: PPC: Book3S: Treat VTB as a per-subcore register, not per-thread
  * Attempt to map rbd image from ceph jewel/luminous hangs (LP: #1728739)
- crush: ensure bucket id is valid before indexing buckets array
- crush: ensure take bucket value is valid
- crush: add chooseleaf_stable tunable
- crush: decode and initialize chooseleaf_stable
- libceph: advertise support for TUNABLES5
- libceph: MOSDOpReply v7 encoding
  * Xenial update to 4.4.98 stable release (LP: #1732698)
- adv7604: Initialize drive strength to default when using DT
- video: fbdev: pmag-ba-fb: Remove bad `__init' annotation
- PCI: mvebu: Handle changes to the bridge windows while enabled
- xen/netback: set default upper limit of tx/rx queues to 8
- drm: drm_minor_register(): Clean up debugfs on failure
- KVM: PPC: Book 3S: XICS: correct the real mode ICP rejecting counter
- iommu/arm-smmu-v3: Clear prior settings when updating STEs
- powerpc/corenet: explicitly disable the SDHC controller on kmcoge4
- ARM: omap2plus_defconfig: Fix probe errors on UARTs 5 and 6
- crypto: vmx - disable preemption to enable vsx in aes_ctr.c
- iio: trigger: free trigger resource correctly
- phy: increase size of MII_BUS_ID_SIZE and bus_id
- serial: sh-sci: Fix register offsets for the IRDA serial port
- usb: hcd: initialize hcd->flags to 0 when rm hcd
- netfilter: nft_meta: deal with PACKET_LOOPBACK in netdev family
- IPsec: do not ignore crypto err in ah4 input
- Input: mpr121 - handle multiple bits change of status register
- Input: mpr121 - set missing event capability
- IB/ipoib: Change list_del to list_del_init in the tx object
- s390/qeth: issue STARTLAN as first IPA command
- (config) Add NET_DSA=n
- net: dsa: select NET_SWITCHDEV
- platform/x86: hp-wmi: Fix detection for dock and tablet mode
- cdc_ncm: Set NTB format again after altsetting switch for Huawei devices
- KEYS: trusted: sanitize all key material
- KEYS: trusted: fix writing past end of buffer in trusted_read()
- platform/x86: hp-wmi: Fix error value for hp_wmi_tablet_state
- platform/x86: hp-wmi: Do not shadow error values
- x86/uaccess, sched/preempt: Verify access_ok() context
- workqueue: Fix NULL pointer dereference
- crypto: x86/sha1-mb - fix panic due to unaligned access
- KEYS: fix NULL pointer dereference during ASN.1 parsing [ver #2]
- ARM: 8720/1: ensure dump_instr() checks addr_limit
- ALSA: seq: Fix OSS sysex delivery in OSS emulation
- ALSA: seq: Avoid invalid lockdep class warning
- MIPS: microMIPS: Fix incorrect mask in insn_table_MM
- MIPS: Fix CM region target definitions
- MIPS: SMP: Use a completion event to signal CPU up
- MIPS: Fix race on setting and 

[Kernel-packages] [Bug 1736194] Re: linux: 3.13.0-137.186 -proposed tracker

2017-12-07 Thread Brad Figg
** Changed in: kernel-sru-workflow/promote-to-updates
   Status: Fix Committed => 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: 1736195
  derivatives:
  -- swm properties --
  boot-testing-requested: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true
+ kernel-stable-phase:Promoted to updates
+ kernel-stable-phase-changed:Thursday, 07. December 2017 18: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
  
  backports: 1736195
  derivatives:
  -- swm properties --
  boot-testing-requested: true
- phase: Promoted to proposed
+ phase: Promoted to updates
  proposed-announcement-sent: true
  proposed-testing-requested: true
- kernel-stable-phase:Promoted to updates
- kernel-stable-phase-changed:Thursday, 07. December 2017 18:31 UTC

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

Title:
  linux: 3.13.0-137.186 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  Fix Committed
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:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Trusty:
  Fix Released

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: 1736195
  derivatives:
  -- swm properties --
  boot-testing-requested: true
  phase: Promoted to updates
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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


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

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

apport-collect 1737005

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

Title:
  Mainline kernel 4.14 does not start apparmor

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  With Ubuntu 16.04.3 LTS (Xenial Xerus), and Ubuntu mainline kernel
  4.14.3 or 4.14.4 systemd fails allways starting apparmor.service and
  ureadahead.service. Sometimes udisks2.service fails too.

  $ uname -a
  Linux lieselotte 4.14.4-041404-generic #201712050630 SMP Tue Dec 5 12:07:25 
UTC 2017 i686 i686 i686 GNU/Linux

  $ systemctl --failed
    UNIT   LOAD   ACTIVE SUBDESCRIPTION
  ● apparmor.service   loaded failed failed LSB: AppArmor initialization
  ● udisks2.serviceloaded failed failed Disk Manager
  ● ureadahead.service loaded failed failed Read required files in advance

  $ systemctl status apparmor.service
  ● apparmor.service - LSB: AppArmor initialization
     Loaded: loaded (/etc/init.d/apparmor; bad; vendor preset: enabled)
     Active: failed (Result: exit-code) since Do 2017-12-07 18:04:51 CET; 52min 
ago
   Docs: man:systemd-sysv-generator(8)
    Process: 689 ExecStart=/etc/init.d/apparmor start (code=exited, 
status=1/FAILURE)

  Dez 07 18:04:51 lieselotte systemd[1]: Starting LSB: AppArmor 
initialization...
  Dez 07 18:04:51 lieselotte apparmor[689]:  * Starting AppArmor profiles
  Dez 07 18:04:51 lieselotte apparmor[689]:  * AppArmor not available as kernel 
LSM.
  Dez 07 18:04:51 lieselotte apparmor[689]:...fail!
  Dez 07 18:04:51 lieselotte systemd[1]: apparmor.service: Control process 
exited, code=exited status=1
  Dez 07 18:04:51 lieselotte systemd[1]: Failed to start LSB: AppArmor 
initialization.
  Dez 07 18:04:51 lieselotte systemd[1]: apparmor.service: Unit entered failed 
state.
  Dez 07 18:04:51 lieselotte systemd[1]: apparmor.service: Failed with result 
'exit-code'.

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

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


[Kernel-packages] [Bug 1733605] Re: elantech touchpad of Lenovo L480/580 failed to detect hw_version

2017-12-07 Thread Launchpad Bug Tracker
This bug was fixed in the package linux-oem - 4.13.0-1010.11

---
linux-oem (4.13.0-1010.11) xenial; urgency=low

  * linux-oem: 4.13.0-1010.11 -proposed tracker (LP: #1736124)

  [ Ubuntu: 4.13.0-19.22 ]

  * linux: 4.13.0-19.22 -proposed tracker (LP: #1736118)
  * CVE-2017-1000405
- mm, thp: Do not make page table dirty unconditionally in touch_p[mu]d()

linux-oem (4.13.0-1009.10) xenial; urgency=low

  * linux-oem: 4.13.0-1009.10 -proposed tracker (LP: #1733532)

  * Intel 9260/9462/9560 driver support (LP: #1734242)
- iwlwifi: refactor out paging code
- iwlwifi: refactor shared mem parsing
- iwlwifi: reorganize firmware API
- iwlwifi: mvm: support version 7 of the SCAN_REQ_UMAC FW command
- iwlwifi: fix PCI IDs and configuration mapping for 9000 series
- iwlwifi: fix firmware names for 9000 and A000 series hw

  * QCA Rome bluetooth connection cannot be established after S3  (LP: #1734020)
- Bluetooth: btusb: fix QCA Rome suspend/resume

  * elantech touchpad of Lenovo L480/580 failed to detect hw_version
(LP: #1733605)
- Input: elantech - add new icbody type 15

  * AQUANTIA AQC107 10G[1D6A:0001] & 2.5/5Gb [1D6A:D108] NIC (LP: #1730544)
- net: aquantia: Bad udp rate on default interrupt coalescing
- aquantia: Fix Tx queue hangups
- net: aquantia: Reset nic statistics on interface up/down
- net: aquantia: Enable coalescing management via ethtool interface
- net: aquantia: mmio unmap was not performed on driver removal
- net: aquantia: Limit number of MSIX irqs to the number of cpus
- net: aquantia: Fixed transient link up/down/up notification
- net: aquantia: Add queue restarts stats counter
- net: aquantia: Reset nic statistics on interface up/down

  * Miscellaneous Ubuntu changes
- Rebase to 4.13.0-18.21

  * Miscellaneous upstream changes
- Ubuntu: [Config] update configs following rebase to Ubuntu-4.13.0-18.21

  [ Ubuntu: 4.13.0-18.21 ]

  * linux: 4.13.0-18.21 -proposed tracker (LP: #1733530)
  * NVMe timeout is too short (LP: #1729119)
- nvme: update timeout module parameter type
  * CPU call trace on AMD Raven Ridge after S3 (LP: #1732894)
- x86/mce/AMD: Allow any CPU to initialize the smca_banks array
  * Set PANIC_TIMEOUT=10 on Power Systems (LP: #1730660)
- [Config]: Set PANIC_TIMEOUT=10 on ppc64el
  * Cannot pair BLE remote devices when using combo BT SoC (LP: #1731467)
- Bluetooth: increase timeout for le auto connections
  * enable CONFIG_SND_SOC_INTEL_BYT_CHT_NOCODEC_MACH easily confuse users
(LP: #1732627)
- [Config] CONFIG_SND_SOC_INTEL_BYT_CHT_NOCODEC_MACH=n
  * Plantronics P610 does not support sample rate reading (LP: #1719853)
- ALSA: usb-audio: Add sample rate quirk for Plantronics P610
  * Allow drivers to use Relaxed Ordering on capable root ports (LP: #1721365)
- Revert commit 1a8b6d76dc5b ("net:add one common config...")
- net: ixgbe: Use new PCI_DEV_FLAGS_NO_RELAXED_ORDERING flag
  * support GICv3 ITS save/restore & migration (LP: #1710019)
- KVM: arm/arm64: vgic-its: Fix return value for device table restore
  * Device hotplugging with MPT SAS cannot work for VMWare ESXi (LP: #1730852)
- scsi: mptsas: Fixup device hotplug for VMWare ESXi
  * Artful update to 4.13.13 stable release (LP: #1732726)
- netfilter: nat: Revert "netfilter: nat: convert nat bysrc hash to
  rhashtable"
- netfilter: nft_set_hash: disable fast_ops for 2-len keys
- workqueue: Fix NULL pointer dereference
- crypto: ccm - preserve the IV buffer
- crypto: x86/sha1-mb - fix panic due to unaligned access
- crypto: x86/sha256-mb - fix panic due to unaligned access
- KEYS: fix NULL pointer dereference during ASN.1 parsing [ver #2]
- ACPI / PM: Blacklist Low Power S0 Idle _DSM for Dell XPS13 9360
- ARM: 8720/1: ensure dump_instr() checks addr_limit
- ALSA: timer: Limit max instances per timer
- ALSA: usb-audio: support new Amanero Combo384 firmware version
- ALSA: hda - fix headset mic problem for Dell machines with alc274
- ALSA: seq: Fix OSS sysex delivery in OSS emulation
- ALSA: seq: Avoid invalid lockdep class warning
- MIPS: Fix CM region target definitions
- MIPS: BMIPS: Fix missing cbr address
- MIPS: AR7: Defer registration of GPIO
- MIPS: AR7: Ensure that serial ports are properly set up
- KVM: PPC: Book3S HV: Fix exclusion between HPT resizing and other HPT
  updates
- Input: elan_i2c - add ELAN060C to the ACPI table
- rbd: use GFP_NOIO for parent stat and data requests
- drm/vmwgfx: Fix Ubuntu 17.10 Wayland black screen issue
- Revert "x86: CPU: Fix up "cpu MHz" in /proc/cpuinfo"
- can: sun4i: handle overrun in RX FIFO
- can: peak: Add support for new PCIe/M2 CAN FD interfaces
- can: ifi: Fix transmitter delay calculation
- can: c_can: don't indicate triple sampling support for D_CAN
- x86/debug: Handle warnings before the notifier chain, to 

[Kernel-packages] [Bug 1732512] Re: xen hibernation support for linux-aws

2017-12-07 Thread Launchpad Bug Tracker
This bug was fixed in the package linux-aws - 4.4.0-1005.5

---
linux-aws (4.4.0-1005.5) trusty; urgency=low

  * linux-aws: 4.4.0-1005.5 -proposed tracker (LP: #1736182)

  * Update config with NET_DSA=n as required by changes in
 upstream stable update to 4.4.98 (LP: #1732698)

  [ Ubuntu: 4.4.0-103.126 ]

  * linux: 4.4.0-103.126 -proposed tracker (LP: #1736181)
  * CVE-2017-1000405
- mm, thp: Do not make page table dirty unconditionally in touch_p[mu]d()
  * CVE-2017-16939
- netlink: add a start callback for starting a netlink dump
- ipsec: Fix aborted xfrm policy dump crash

  [ Ubuntu: 4.4.0-102.125 ]

  * linux: 4.4.0-102.125 -proposed tracker (LP: #1733541)
  * tar -x sometimes fails on overlayfs (LP: #1728489)
- ovl: check if all layers are on the same fs
- ovl: persistent inode number for directories
  * NVMe timeout is too short (LP: #1729119)
- nvme: update timeout module parameter type
  * Set PANIC_TIMEOUT=10 on Power Systems (LP: #1730660)
- [Config]: Set PANIC_TIMEOUT=10 on ppc64el
  * Cannot pair BLE remote devices when using combo BT SoC (LP: #1731467)
- Bluetooth: increase timeout for le auto connections
  * CIFS errors on 4.4.0-98, but not on 4.4.0-97 with same config (LP: #1729337)
- SMB3: Validate negotiate request must always be signed
  * Plantronics P610 does not support sample rate reading (LP: #1719853)
- ALSA: usb-audio: Add sample rate quirk for Plantronics P610
  * Invalid btree pointer causes the kernel NULL pointer dereference
(LP: #1729256)
- xfs: reinit btree pointer on attr tree inactivation walk
  * Samba mount/umount in docker container triggers kernel Oops (LP: #1729637)
- ipv6: only call ip6_route_dev_notify() once for NETDEV_UNREGISTER
- ipv6: fix NULL dereference in ip6_route_dev_notify()
  * [kernel] tty/hvc: Use opal irqchip interface if available (LP: #1728098)
- tty/hvc: Use opal irqchip interface if available
  * Device hotplugging with MPT SAS cannot work for VMWare ESXi (LP: #1730852)
- scsi: mptsas: Fixup device hotplug for VMWare ESXi
  * NMI watchdog: BUG: soft lockup on Guest upon boot (KVM) (LP: #1727331)
- KVM: PPC: Book3S: Treat VTB as a per-subcore register, not per-thread
  * Attempt to map rbd image from ceph jewel/luminous hangs (LP: #1728739)
- crush: ensure bucket id is valid before indexing buckets array
- crush: ensure take bucket value is valid
- crush: add chooseleaf_stable tunable
- crush: decode and initialize chooseleaf_stable
- libceph: advertise support for TUNABLES5
- libceph: MOSDOpReply v7 encoding
  * Xenial update to 4.4.98 stable release (LP: #1732698)
- adv7604: Initialize drive strength to default when using DT
- video: fbdev: pmag-ba-fb: Remove bad `__init' annotation
- PCI: mvebu: Handle changes to the bridge windows while enabled
- xen/netback: set default upper limit of tx/rx queues to 8
- drm: drm_minor_register(): Clean up debugfs on failure
- KVM: PPC: Book 3S: XICS: correct the real mode ICP rejecting counter
- iommu/arm-smmu-v3: Clear prior settings when updating STEs
- powerpc/corenet: explicitly disable the SDHC controller on kmcoge4
- ARM: omap2plus_defconfig: Fix probe errors on UARTs 5 and 6
- crypto: vmx - disable preemption to enable vsx in aes_ctr.c
- iio: trigger: free trigger resource correctly
- phy: increase size of MII_BUS_ID_SIZE and bus_id
- serial: sh-sci: Fix register offsets for the IRDA serial port
- usb: hcd: initialize hcd->flags to 0 when rm hcd
- netfilter: nft_meta: deal with PACKET_LOOPBACK in netdev family
- IPsec: do not ignore crypto err in ah4 input
- Input: mpr121 - handle multiple bits change of status register
- Input: mpr121 - set missing event capability
- IB/ipoib: Change list_del to list_del_init in the tx object
- s390/qeth: issue STARTLAN as first IPA command
- (config) Add NET_DSA=n
- net: dsa: select NET_SWITCHDEV
- platform/x86: hp-wmi: Fix detection for dock and tablet mode
- cdc_ncm: Set NTB format again after altsetting switch for Huawei devices
- KEYS: trusted: sanitize all key material
- KEYS: trusted: fix writing past end of buffer in trusted_read()
- platform/x86: hp-wmi: Fix error value for hp_wmi_tablet_state
- platform/x86: hp-wmi: Do not shadow error values
- x86/uaccess, sched/preempt: Verify access_ok() context
- workqueue: Fix NULL pointer dereference
- crypto: x86/sha1-mb - fix panic due to unaligned access
- KEYS: fix NULL pointer dereference during ASN.1 parsing [ver #2]
- ARM: 8720/1: ensure dump_instr() checks addr_limit
- ALSA: seq: Fix OSS sysex delivery in OSS emulation
- ALSA: seq: Avoid invalid lockdep class warning
- MIPS: microMIPS: Fix incorrect mask in insn_table_MM
- MIPS: Fix CM region target definitions
- MIPS: SMP: Use a completion event to signal CPU up
- MIPS: Fix race on setting and 

[Kernel-packages] [Bug 1732774] Re: linux-aws: 4.4.0-1004.4 -proposed tracker

2017-12-07 Thread Launchpad Bug Tracker
This bug was fixed in the package linux-aws - 4.4.0-1005.5

---
linux-aws (4.4.0-1005.5) trusty; urgency=low

  * linux-aws: 4.4.0-1005.5 -proposed tracker (LP: #1736182)

  * Update config with NET_DSA=n as required by changes in
 upstream stable update to 4.4.98 (LP: #1732698)

  [ Ubuntu: 4.4.0-103.126 ]

  * linux: 4.4.0-103.126 -proposed tracker (LP: #1736181)
  * CVE-2017-1000405
- mm, thp: Do not make page table dirty unconditionally in touch_p[mu]d()
  * CVE-2017-16939
- netlink: add a start callback for starting a netlink dump
- ipsec: Fix aborted xfrm policy dump crash

  [ Ubuntu: 4.4.0-102.125 ]

  * linux: 4.4.0-102.125 -proposed tracker (LP: #1733541)
  * tar -x sometimes fails on overlayfs (LP: #1728489)
- ovl: check if all layers are on the same fs
- ovl: persistent inode number for directories
  * NVMe timeout is too short (LP: #1729119)
- nvme: update timeout module parameter type
  * Set PANIC_TIMEOUT=10 on Power Systems (LP: #1730660)
- [Config]: Set PANIC_TIMEOUT=10 on ppc64el
  * Cannot pair BLE remote devices when using combo BT SoC (LP: #1731467)
- Bluetooth: increase timeout for le auto connections
  * CIFS errors on 4.4.0-98, but not on 4.4.0-97 with same config (LP: #1729337)
- SMB3: Validate negotiate request must always be signed
  * Plantronics P610 does not support sample rate reading (LP: #1719853)
- ALSA: usb-audio: Add sample rate quirk for Plantronics P610
  * Invalid btree pointer causes the kernel NULL pointer dereference
(LP: #1729256)
- xfs: reinit btree pointer on attr tree inactivation walk
  * Samba mount/umount in docker container triggers kernel Oops (LP: #1729637)
- ipv6: only call ip6_route_dev_notify() once for NETDEV_UNREGISTER
- ipv6: fix NULL dereference in ip6_route_dev_notify()
  * [kernel] tty/hvc: Use opal irqchip interface if available (LP: #1728098)
- tty/hvc: Use opal irqchip interface if available
  * Device hotplugging with MPT SAS cannot work for VMWare ESXi (LP: #1730852)
- scsi: mptsas: Fixup device hotplug for VMWare ESXi
  * NMI watchdog: BUG: soft lockup on Guest upon boot (KVM) (LP: #1727331)
- KVM: PPC: Book3S: Treat VTB as a per-subcore register, not per-thread
  * Attempt to map rbd image from ceph jewel/luminous hangs (LP: #1728739)
- crush: ensure bucket id is valid before indexing buckets array
- crush: ensure take bucket value is valid
- crush: add chooseleaf_stable tunable
- crush: decode and initialize chooseleaf_stable
- libceph: advertise support for TUNABLES5
- libceph: MOSDOpReply v7 encoding
  * Xenial update to 4.4.98 stable release (LP: #1732698)
- adv7604: Initialize drive strength to default when using DT
- video: fbdev: pmag-ba-fb: Remove bad `__init' annotation
- PCI: mvebu: Handle changes to the bridge windows while enabled
- xen/netback: set default upper limit of tx/rx queues to 8
- drm: drm_minor_register(): Clean up debugfs on failure
- KVM: PPC: Book 3S: XICS: correct the real mode ICP rejecting counter
- iommu/arm-smmu-v3: Clear prior settings when updating STEs
- powerpc/corenet: explicitly disable the SDHC controller on kmcoge4
- ARM: omap2plus_defconfig: Fix probe errors on UARTs 5 and 6
- crypto: vmx - disable preemption to enable vsx in aes_ctr.c
- iio: trigger: free trigger resource correctly
- phy: increase size of MII_BUS_ID_SIZE and bus_id
- serial: sh-sci: Fix register offsets for the IRDA serial port
- usb: hcd: initialize hcd->flags to 0 when rm hcd
- netfilter: nft_meta: deal with PACKET_LOOPBACK in netdev family
- IPsec: do not ignore crypto err in ah4 input
- Input: mpr121 - handle multiple bits change of status register
- Input: mpr121 - set missing event capability
- IB/ipoib: Change list_del to list_del_init in the tx object
- s390/qeth: issue STARTLAN as first IPA command
- (config) Add NET_DSA=n
- net: dsa: select NET_SWITCHDEV
- platform/x86: hp-wmi: Fix detection for dock and tablet mode
- cdc_ncm: Set NTB format again after altsetting switch for Huawei devices
- KEYS: trusted: sanitize all key material
- KEYS: trusted: fix writing past end of buffer in trusted_read()
- platform/x86: hp-wmi: Fix error value for hp_wmi_tablet_state
- platform/x86: hp-wmi: Do not shadow error values
- x86/uaccess, sched/preempt: Verify access_ok() context
- workqueue: Fix NULL pointer dereference
- crypto: x86/sha1-mb - fix panic due to unaligned access
- KEYS: fix NULL pointer dereference during ASN.1 parsing [ver #2]
- ARM: 8720/1: ensure dump_instr() checks addr_limit
- ALSA: seq: Fix OSS sysex delivery in OSS emulation
- ALSA: seq: Avoid invalid lockdep class warning
- MIPS: microMIPS: Fix incorrect mask in insn_table_MM
- MIPS: Fix CM region target definitions
- MIPS: SMP: Use a completion event to signal CPU up
- MIPS: Fix race on setting and 

[Kernel-packages] [Bug 1729119] Re: NVMe timeout is too short

2017-12-07 Thread Launchpad Bug Tracker
This bug was fixed in the package linux-aws - 4.4.0-1005.5

---
linux-aws (4.4.0-1005.5) trusty; urgency=low

  * linux-aws: 4.4.0-1005.5 -proposed tracker (LP: #1736182)

  * Update config with NET_DSA=n as required by changes in
 upstream stable update to 4.4.98 (LP: #1732698)

  [ Ubuntu: 4.4.0-103.126 ]

  * linux: 4.4.0-103.126 -proposed tracker (LP: #1736181)
  * CVE-2017-1000405
- mm, thp: Do not make page table dirty unconditionally in touch_p[mu]d()
  * CVE-2017-16939
- netlink: add a start callback for starting a netlink dump
- ipsec: Fix aborted xfrm policy dump crash

  [ Ubuntu: 4.4.0-102.125 ]

  * linux: 4.4.0-102.125 -proposed tracker (LP: #1733541)
  * tar -x sometimes fails on overlayfs (LP: #1728489)
- ovl: check if all layers are on the same fs
- ovl: persistent inode number for directories
  * NVMe timeout is too short (LP: #1729119)
- nvme: update timeout module parameter type
  * Set PANIC_TIMEOUT=10 on Power Systems (LP: #1730660)
- [Config]: Set PANIC_TIMEOUT=10 on ppc64el
  * Cannot pair BLE remote devices when using combo BT SoC (LP: #1731467)
- Bluetooth: increase timeout for le auto connections
  * CIFS errors on 4.4.0-98, but not on 4.4.0-97 with same config (LP: #1729337)
- SMB3: Validate negotiate request must always be signed
  * Plantronics P610 does not support sample rate reading (LP: #1719853)
- ALSA: usb-audio: Add sample rate quirk for Plantronics P610
  * Invalid btree pointer causes the kernel NULL pointer dereference
(LP: #1729256)
- xfs: reinit btree pointer on attr tree inactivation walk
  * Samba mount/umount in docker container triggers kernel Oops (LP: #1729637)
- ipv6: only call ip6_route_dev_notify() once for NETDEV_UNREGISTER
- ipv6: fix NULL dereference in ip6_route_dev_notify()
  * [kernel] tty/hvc: Use opal irqchip interface if available (LP: #1728098)
- tty/hvc: Use opal irqchip interface if available
  * Device hotplugging with MPT SAS cannot work for VMWare ESXi (LP: #1730852)
- scsi: mptsas: Fixup device hotplug for VMWare ESXi
  * NMI watchdog: BUG: soft lockup on Guest upon boot (KVM) (LP: #1727331)
- KVM: PPC: Book3S: Treat VTB as a per-subcore register, not per-thread
  * Attempt to map rbd image from ceph jewel/luminous hangs (LP: #1728739)
- crush: ensure bucket id is valid before indexing buckets array
- crush: ensure take bucket value is valid
- crush: add chooseleaf_stable tunable
- crush: decode and initialize chooseleaf_stable
- libceph: advertise support for TUNABLES5
- libceph: MOSDOpReply v7 encoding
  * Xenial update to 4.4.98 stable release (LP: #1732698)
- adv7604: Initialize drive strength to default when using DT
- video: fbdev: pmag-ba-fb: Remove bad `__init' annotation
- PCI: mvebu: Handle changes to the bridge windows while enabled
- xen/netback: set default upper limit of tx/rx queues to 8
- drm: drm_minor_register(): Clean up debugfs on failure
- KVM: PPC: Book 3S: XICS: correct the real mode ICP rejecting counter
- iommu/arm-smmu-v3: Clear prior settings when updating STEs
- powerpc/corenet: explicitly disable the SDHC controller on kmcoge4
- ARM: omap2plus_defconfig: Fix probe errors on UARTs 5 and 6
- crypto: vmx - disable preemption to enable vsx in aes_ctr.c
- iio: trigger: free trigger resource correctly
- phy: increase size of MII_BUS_ID_SIZE and bus_id
- serial: sh-sci: Fix register offsets for the IRDA serial port
- usb: hcd: initialize hcd->flags to 0 when rm hcd
- netfilter: nft_meta: deal with PACKET_LOOPBACK in netdev family
- IPsec: do not ignore crypto err in ah4 input
- Input: mpr121 - handle multiple bits change of status register
- Input: mpr121 - set missing event capability
- IB/ipoib: Change list_del to list_del_init in the tx object
- s390/qeth: issue STARTLAN as first IPA command
- (config) Add NET_DSA=n
- net: dsa: select NET_SWITCHDEV
- platform/x86: hp-wmi: Fix detection for dock and tablet mode
- cdc_ncm: Set NTB format again after altsetting switch for Huawei devices
- KEYS: trusted: sanitize all key material
- KEYS: trusted: fix writing past end of buffer in trusted_read()
- platform/x86: hp-wmi: Fix error value for hp_wmi_tablet_state
- platform/x86: hp-wmi: Do not shadow error values
- x86/uaccess, sched/preempt: Verify access_ok() context
- workqueue: Fix NULL pointer dereference
- crypto: x86/sha1-mb - fix panic due to unaligned access
- KEYS: fix NULL pointer dereference during ASN.1 parsing [ver #2]
- ARM: 8720/1: ensure dump_instr() checks addr_limit
- ALSA: seq: Fix OSS sysex delivery in OSS emulation
- ALSA: seq: Avoid invalid lockdep class warning
- MIPS: microMIPS: Fix incorrect mask in insn_table_MM
- MIPS: Fix CM region target definitions
- MIPS: SMP: Use a completion event to signal CPU up
- MIPS: Fix race on setting and 

[Kernel-packages] [Bug 1733546] Re: linux-aws: 4.4.0-1042.51 -proposed tracker

2017-12-07 Thread Launchpad Bug Tracker
*** This bug is a duplicate of bug 1736187 ***
https://bugs.launchpad.net/bugs/1736187

This bug was fixed in the package linux-aws - 4.4.0-1043.52

---
linux-aws (4.4.0-1043.52) xenial; urgency=low

  * linux-aws: 4.4.0-1043.52 -proposed tracker (LP: #1736187)

  [ Ubuntu: 4.4.0-103.126 ]

  * linux: 4.4.0-103.126 -proposed tracker (LP: #1736181)
  * CVE-2017-1000405
- mm, thp: Do not make page table dirty unconditionally in touch_p[mu]d()
  * CVE-2017-16939
- netlink: add a start callback for starting a netlink dump
- ipsec: Fix aborted xfrm policy dump crash

linux-aws (4.4.0-1042.51) xenial; urgency=low

  * linux-aws: 4.4.0-1042.51 -proposed tracker (LP: #1733546)

  * Update config with NET_DSA=n as required by changes in
 upstream stable update to 4.4.98 (LP: #1732698)

  [ Ubuntu: 4.4.0-102.125 ]

  * linux: 4.4.0-102.125 -proposed tracker (LP: #1733541)
  * tar -x sometimes fails on overlayfs (LP: #1728489)
- ovl: check if all layers are on the same fs
- ovl: persistent inode number for directories
  * NVMe timeout is too short (LP: #1729119)
- nvme: update timeout module parameter type
  * Set PANIC_TIMEOUT=10 on Power Systems (LP: #1730660)
- [Config]: Set PANIC_TIMEOUT=10 on ppc64el
  * Cannot pair BLE remote devices when using combo BT SoC (LP: #1731467)
- Bluetooth: increase timeout for le auto connections
  * CIFS errors on 4.4.0-98, but not on 4.4.0-97 with same config (LP: #1729337)
- SMB3: Validate negotiate request must always be signed
  * Plantronics P610 does not support sample rate reading (LP: #1719853)
- ALSA: usb-audio: Add sample rate quirk for Plantronics P610
  * Invalid btree pointer causes the kernel NULL pointer dereference
(LP: #1729256)
- xfs: reinit btree pointer on attr tree inactivation walk
  * Samba mount/umount in docker container triggers kernel Oops (LP: #1729637)
- ipv6: only call ip6_route_dev_notify() once for NETDEV_UNREGISTER
- ipv6: fix NULL dereference in ip6_route_dev_notify()
  * [kernel] tty/hvc: Use opal irqchip interface if available (LP: #1728098)
- tty/hvc: Use opal irqchip interface if available
  * Device hotplugging with MPT SAS cannot work for VMWare ESXi (LP: #1730852)
- scsi: mptsas: Fixup device hotplug for VMWare ESXi
  * NMI watchdog: BUG: soft lockup on Guest upon boot (KVM) (LP: #1727331)
- KVM: PPC: Book3S: Treat VTB as a per-subcore register, not per-thread
  * Attempt to map rbd image from ceph jewel/luminous hangs (LP: #1728739)
- crush: ensure bucket id is valid before indexing buckets array
- crush: ensure take bucket value is valid
- crush: add chooseleaf_stable tunable
- crush: decode and initialize chooseleaf_stable
- libceph: advertise support for TUNABLES5
- libceph: MOSDOpReply v7 encoding
  * Xenial update to 4.4.98 stable release (LP: #1732698)
- adv7604: Initialize drive strength to default when using DT
- video: fbdev: pmag-ba-fb: Remove bad `__init' annotation
- PCI: mvebu: Handle changes to the bridge windows while enabled
- xen/netback: set default upper limit of tx/rx queues to 8
- drm: drm_minor_register(): Clean up debugfs on failure
- KVM: PPC: Book 3S: XICS: correct the real mode ICP rejecting counter
- iommu/arm-smmu-v3: Clear prior settings when updating STEs
- powerpc/corenet: explicitly disable the SDHC controller on kmcoge4
- ARM: omap2plus_defconfig: Fix probe errors on UARTs 5 and 6
- crypto: vmx - disable preemption to enable vsx in aes_ctr.c
- iio: trigger: free trigger resource correctly
- phy: increase size of MII_BUS_ID_SIZE and bus_id
- serial: sh-sci: Fix register offsets for the IRDA serial port
- usb: hcd: initialize hcd->flags to 0 when rm hcd
- netfilter: nft_meta: deal with PACKET_LOOPBACK in netdev family
- IPsec: do not ignore crypto err in ah4 input
- Input: mpr121 - handle multiple bits change of status register
- Input: mpr121 - set missing event capability
- IB/ipoib: Change list_del to list_del_init in the tx object
- s390/qeth: issue STARTLAN as first IPA command
- (config) Add NET_DSA=n
- net: dsa: select NET_SWITCHDEV
- platform/x86: hp-wmi: Fix detection for dock and tablet mode
- cdc_ncm: Set NTB format again after altsetting switch for Huawei devices
- KEYS: trusted: sanitize all key material
- KEYS: trusted: fix writing past end of buffer in trusted_read()
- platform/x86: hp-wmi: Fix error value for hp_wmi_tablet_state
- platform/x86: hp-wmi: Do not shadow error values
- x86/uaccess, sched/preempt: Verify access_ok() context
- workqueue: Fix NULL pointer dereference
- crypto: x86/sha1-mb - fix panic due to unaligned access
- KEYS: fix NULL pointer dereference during ASN.1 parsing [ver #2]
- ARM: 8720/1: ensure dump_instr() checks addr_limit
- ALSA: seq: Fix OSS sysex delivery in OSS emulation
- ALSA: seq: Avoid invalid lockdep class 

[Kernel-packages] [Bug 1729119] Re: NVMe timeout is too short

2017-12-07 Thread Launchpad Bug Tracker
This bug was fixed in the package linux-aws - 4.4.0-1005.5

---
linux-aws (4.4.0-1005.5) trusty; urgency=low

  * linux-aws: 4.4.0-1005.5 -proposed tracker (LP: #1736182)

  * Update config with NET_DSA=n as required by changes in
 upstream stable update to 4.4.98 (LP: #1732698)

  [ Ubuntu: 4.4.0-103.126 ]

  * linux: 4.4.0-103.126 -proposed tracker (LP: #1736181)
  * CVE-2017-1000405
- mm, thp: Do not make page table dirty unconditionally in touch_p[mu]d()
  * CVE-2017-16939
- netlink: add a start callback for starting a netlink dump
- ipsec: Fix aborted xfrm policy dump crash

  [ Ubuntu: 4.4.0-102.125 ]

  * linux: 4.4.0-102.125 -proposed tracker (LP: #1733541)
  * tar -x sometimes fails on overlayfs (LP: #1728489)
- ovl: check if all layers are on the same fs
- ovl: persistent inode number for directories
  * NVMe timeout is too short (LP: #1729119)
- nvme: update timeout module parameter type
  * Set PANIC_TIMEOUT=10 on Power Systems (LP: #1730660)
- [Config]: Set PANIC_TIMEOUT=10 on ppc64el
  * Cannot pair BLE remote devices when using combo BT SoC (LP: #1731467)
- Bluetooth: increase timeout for le auto connections
  * CIFS errors on 4.4.0-98, but not on 4.4.0-97 with same config (LP: #1729337)
- SMB3: Validate negotiate request must always be signed
  * Plantronics P610 does not support sample rate reading (LP: #1719853)
- ALSA: usb-audio: Add sample rate quirk for Plantronics P610
  * Invalid btree pointer causes the kernel NULL pointer dereference
(LP: #1729256)
- xfs: reinit btree pointer on attr tree inactivation walk
  * Samba mount/umount in docker container triggers kernel Oops (LP: #1729637)
- ipv6: only call ip6_route_dev_notify() once for NETDEV_UNREGISTER
- ipv6: fix NULL dereference in ip6_route_dev_notify()
  * [kernel] tty/hvc: Use opal irqchip interface if available (LP: #1728098)
- tty/hvc: Use opal irqchip interface if available
  * Device hotplugging with MPT SAS cannot work for VMWare ESXi (LP: #1730852)
- scsi: mptsas: Fixup device hotplug for VMWare ESXi
  * NMI watchdog: BUG: soft lockup on Guest upon boot (KVM) (LP: #1727331)
- KVM: PPC: Book3S: Treat VTB as a per-subcore register, not per-thread
  * Attempt to map rbd image from ceph jewel/luminous hangs (LP: #1728739)
- crush: ensure bucket id is valid before indexing buckets array
- crush: ensure take bucket value is valid
- crush: add chooseleaf_stable tunable
- crush: decode and initialize chooseleaf_stable
- libceph: advertise support for TUNABLES5
- libceph: MOSDOpReply v7 encoding
  * Xenial update to 4.4.98 stable release (LP: #1732698)
- adv7604: Initialize drive strength to default when using DT
- video: fbdev: pmag-ba-fb: Remove bad `__init' annotation
- PCI: mvebu: Handle changes to the bridge windows while enabled
- xen/netback: set default upper limit of tx/rx queues to 8
- drm: drm_minor_register(): Clean up debugfs on failure
- KVM: PPC: Book 3S: XICS: correct the real mode ICP rejecting counter
- iommu/arm-smmu-v3: Clear prior settings when updating STEs
- powerpc/corenet: explicitly disable the SDHC controller on kmcoge4
- ARM: omap2plus_defconfig: Fix probe errors on UARTs 5 and 6
- crypto: vmx - disable preemption to enable vsx in aes_ctr.c
- iio: trigger: free trigger resource correctly
- phy: increase size of MII_BUS_ID_SIZE and bus_id
- serial: sh-sci: Fix register offsets for the IRDA serial port
- usb: hcd: initialize hcd->flags to 0 when rm hcd
- netfilter: nft_meta: deal with PACKET_LOOPBACK in netdev family
- IPsec: do not ignore crypto err in ah4 input
- Input: mpr121 - handle multiple bits change of status register
- Input: mpr121 - set missing event capability
- IB/ipoib: Change list_del to list_del_init in the tx object
- s390/qeth: issue STARTLAN as first IPA command
- (config) Add NET_DSA=n
- net: dsa: select NET_SWITCHDEV
- platform/x86: hp-wmi: Fix detection for dock and tablet mode
- cdc_ncm: Set NTB format again after altsetting switch for Huawei devices
- KEYS: trusted: sanitize all key material
- KEYS: trusted: fix writing past end of buffer in trusted_read()
- platform/x86: hp-wmi: Fix error value for hp_wmi_tablet_state
- platform/x86: hp-wmi: Do not shadow error values
- x86/uaccess, sched/preempt: Verify access_ok() context
- workqueue: Fix NULL pointer dereference
- crypto: x86/sha1-mb - fix panic due to unaligned access
- KEYS: fix NULL pointer dereference during ASN.1 parsing [ver #2]
- ARM: 8720/1: ensure dump_instr() checks addr_limit
- ALSA: seq: Fix OSS sysex delivery in OSS emulation
- ALSA: seq: Avoid invalid lockdep class warning
- MIPS: microMIPS: Fix incorrect mask in insn_table_MM
- MIPS: Fix CM region target definitions
- MIPS: SMP: Use a completion event to signal CPU up
- MIPS: Fix race on setting and 

[Kernel-packages] [Bug 1730544] Re: AQUANTIA AQC107 10G[1D6A:0001] & 2.5/5Gb [1D6A:D108] NIC

2017-12-07 Thread Launchpad Bug Tracker
This bug was fixed in the package linux-oem - 4.13.0-1010.11

---
linux-oem (4.13.0-1010.11) xenial; urgency=low

  * linux-oem: 4.13.0-1010.11 -proposed tracker (LP: #1736124)

  [ Ubuntu: 4.13.0-19.22 ]

  * linux: 4.13.0-19.22 -proposed tracker (LP: #1736118)
  * CVE-2017-1000405
- mm, thp: Do not make page table dirty unconditionally in touch_p[mu]d()

linux-oem (4.13.0-1009.10) xenial; urgency=low

  * linux-oem: 4.13.0-1009.10 -proposed tracker (LP: #1733532)

  * Intel 9260/9462/9560 driver support (LP: #1734242)
- iwlwifi: refactor out paging code
- iwlwifi: refactor shared mem parsing
- iwlwifi: reorganize firmware API
- iwlwifi: mvm: support version 7 of the SCAN_REQ_UMAC FW command
- iwlwifi: fix PCI IDs and configuration mapping for 9000 series
- iwlwifi: fix firmware names for 9000 and A000 series hw

  * QCA Rome bluetooth connection cannot be established after S3  (LP: #1734020)
- Bluetooth: btusb: fix QCA Rome suspend/resume

  * elantech touchpad of Lenovo L480/580 failed to detect hw_version
(LP: #1733605)
- Input: elantech - add new icbody type 15

  * AQUANTIA AQC107 10G[1D6A:0001] & 2.5/5Gb [1D6A:D108] NIC (LP: #1730544)
- net: aquantia: Bad udp rate on default interrupt coalescing
- aquantia: Fix Tx queue hangups
- net: aquantia: Reset nic statistics on interface up/down
- net: aquantia: Enable coalescing management via ethtool interface
- net: aquantia: mmio unmap was not performed on driver removal
- net: aquantia: Limit number of MSIX irqs to the number of cpus
- net: aquantia: Fixed transient link up/down/up notification
- net: aquantia: Add queue restarts stats counter
- net: aquantia: Reset nic statistics on interface up/down

  * Miscellaneous Ubuntu changes
- Rebase to 4.13.0-18.21

  * Miscellaneous upstream changes
- Ubuntu: [Config] update configs following rebase to Ubuntu-4.13.0-18.21

  [ Ubuntu: 4.13.0-18.21 ]

  * linux: 4.13.0-18.21 -proposed tracker (LP: #1733530)
  * NVMe timeout is too short (LP: #1729119)
- nvme: update timeout module parameter type
  * CPU call trace on AMD Raven Ridge after S3 (LP: #1732894)
- x86/mce/AMD: Allow any CPU to initialize the smca_banks array
  * Set PANIC_TIMEOUT=10 on Power Systems (LP: #1730660)
- [Config]: Set PANIC_TIMEOUT=10 on ppc64el
  * Cannot pair BLE remote devices when using combo BT SoC (LP: #1731467)
- Bluetooth: increase timeout for le auto connections
  * enable CONFIG_SND_SOC_INTEL_BYT_CHT_NOCODEC_MACH easily confuse users
(LP: #1732627)
- [Config] CONFIG_SND_SOC_INTEL_BYT_CHT_NOCODEC_MACH=n
  * Plantronics P610 does not support sample rate reading (LP: #1719853)
- ALSA: usb-audio: Add sample rate quirk for Plantronics P610
  * Allow drivers to use Relaxed Ordering on capable root ports (LP: #1721365)
- Revert commit 1a8b6d76dc5b ("net:add one common config...")
- net: ixgbe: Use new PCI_DEV_FLAGS_NO_RELAXED_ORDERING flag
  * support GICv3 ITS save/restore & migration (LP: #1710019)
- KVM: arm/arm64: vgic-its: Fix return value for device table restore
  * Device hotplugging with MPT SAS cannot work for VMWare ESXi (LP: #1730852)
- scsi: mptsas: Fixup device hotplug for VMWare ESXi
  * Artful update to 4.13.13 stable release (LP: #1732726)
- netfilter: nat: Revert "netfilter: nat: convert nat bysrc hash to
  rhashtable"
- netfilter: nft_set_hash: disable fast_ops for 2-len keys
- workqueue: Fix NULL pointer dereference
- crypto: ccm - preserve the IV buffer
- crypto: x86/sha1-mb - fix panic due to unaligned access
- crypto: x86/sha256-mb - fix panic due to unaligned access
- KEYS: fix NULL pointer dereference during ASN.1 parsing [ver #2]
- ACPI / PM: Blacklist Low Power S0 Idle _DSM for Dell XPS13 9360
- ARM: 8720/1: ensure dump_instr() checks addr_limit
- ALSA: timer: Limit max instances per timer
- ALSA: usb-audio: support new Amanero Combo384 firmware version
- ALSA: hda - fix headset mic problem for Dell machines with alc274
- ALSA: seq: Fix OSS sysex delivery in OSS emulation
- ALSA: seq: Avoid invalid lockdep class warning
- MIPS: Fix CM region target definitions
- MIPS: BMIPS: Fix missing cbr address
- MIPS: AR7: Defer registration of GPIO
- MIPS: AR7: Ensure that serial ports are properly set up
- KVM: PPC: Book3S HV: Fix exclusion between HPT resizing and other HPT
  updates
- Input: elan_i2c - add ELAN060C to the ACPI table
- rbd: use GFP_NOIO for parent stat and data requests
- drm/vmwgfx: Fix Ubuntu 17.10 Wayland black screen issue
- Revert "x86: CPU: Fix up "cpu MHz" in /proc/cpuinfo"
- can: sun4i: handle overrun in RX FIFO
- can: peak: Add support for new PCIe/M2 CAN FD interfaces
- can: ifi: Fix transmitter delay calculation
- can: c_can: don't indicate triple sampling support for D_CAN
- x86/debug: Handle warnings before the notifier chain, to 

[Kernel-packages] [Bug 1734242] Re: Intel 9260/9462/9560 driver support

2017-12-07 Thread Launchpad Bug Tracker
This bug was fixed in the package linux-oem - 4.13.0-1010.11

---
linux-oem (4.13.0-1010.11) xenial; urgency=low

  * linux-oem: 4.13.0-1010.11 -proposed tracker (LP: #1736124)

  [ Ubuntu: 4.13.0-19.22 ]

  * linux: 4.13.0-19.22 -proposed tracker (LP: #1736118)
  * CVE-2017-1000405
- mm, thp: Do not make page table dirty unconditionally in touch_p[mu]d()

linux-oem (4.13.0-1009.10) xenial; urgency=low

  * linux-oem: 4.13.0-1009.10 -proposed tracker (LP: #1733532)

  * Intel 9260/9462/9560 driver support (LP: #1734242)
- iwlwifi: refactor out paging code
- iwlwifi: refactor shared mem parsing
- iwlwifi: reorganize firmware API
- iwlwifi: mvm: support version 7 of the SCAN_REQ_UMAC FW command
- iwlwifi: fix PCI IDs and configuration mapping for 9000 series
- iwlwifi: fix firmware names for 9000 and A000 series hw

  * QCA Rome bluetooth connection cannot be established after S3  (LP: #1734020)
- Bluetooth: btusb: fix QCA Rome suspend/resume

  * elantech touchpad of Lenovo L480/580 failed to detect hw_version
(LP: #1733605)
- Input: elantech - add new icbody type 15

  * AQUANTIA AQC107 10G[1D6A:0001] & 2.5/5Gb [1D6A:D108] NIC (LP: #1730544)
- net: aquantia: Bad udp rate on default interrupt coalescing
- aquantia: Fix Tx queue hangups
- net: aquantia: Reset nic statistics on interface up/down
- net: aquantia: Enable coalescing management via ethtool interface
- net: aquantia: mmio unmap was not performed on driver removal
- net: aquantia: Limit number of MSIX irqs to the number of cpus
- net: aquantia: Fixed transient link up/down/up notification
- net: aquantia: Add queue restarts stats counter
- net: aquantia: Reset nic statistics on interface up/down

  * Miscellaneous Ubuntu changes
- Rebase to 4.13.0-18.21

  * Miscellaneous upstream changes
- Ubuntu: [Config] update configs following rebase to Ubuntu-4.13.0-18.21

  [ Ubuntu: 4.13.0-18.21 ]

  * linux: 4.13.0-18.21 -proposed tracker (LP: #1733530)
  * NVMe timeout is too short (LP: #1729119)
- nvme: update timeout module parameter type
  * CPU call trace on AMD Raven Ridge after S3 (LP: #1732894)
- x86/mce/AMD: Allow any CPU to initialize the smca_banks array
  * Set PANIC_TIMEOUT=10 on Power Systems (LP: #1730660)
- [Config]: Set PANIC_TIMEOUT=10 on ppc64el
  * Cannot pair BLE remote devices when using combo BT SoC (LP: #1731467)
- Bluetooth: increase timeout for le auto connections
  * enable CONFIG_SND_SOC_INTEL_BYT_CHT_NOCODEC_MACH easily confuse users
(LP: #1732627)
- [Config] CONFIG_SND_SOC_INTEL_BYT_CHT_NOCODEC_MACH=n
  * Plantronics P610 does not support sample rate reading (LP: #1719853)
- ALSA: usb-audio: Add sample rate quirk for Plantronics P610
  * Allow drivers to use Relaxed Ordering on capable root ports (LP: #1721365)
- Revert commit 1a8b6d76dc5b ("net:add one common config...")
- net: ixgbe: Use new PCI_DEV_FLAGS_NO_RELAXED_ORDERING flag
  * support GICv3 ITS save/restore & migration (LP: #1710019)
- KVM: arm/arm64: vgic-its: Fix return value for device table restore
  * Device hotplugging with MPT SAS cannot work for VMWare ESXi (LP: #1730852)
- scsi: mptsas: Fixup device hotplug for VMWare ESXi
  * Artful update to 4.13.13 stable release (LP: #1732726)
- netfilter: nat: Revert "netfilter: nat: convert nat bysrc hash to
  rhashtable"
- netfilter: nft_set_hash: disable fast_ops for 2-len keys
- workqueue: Fix NULL pointer dereference
- crypto: ccm - preserve the IV buffer
- crypto: x86/sha1-mb - fix panic due to unaligned access
- crypto: x86/sha256-mb - fix panic due to unaligned access
- KEYS: fix NULL pointer dereference during ASN.1 parsing [ver #2]
- ACPI / PM: Blacklist Low Power S0 Idle _DSM for Dell XPS13 9360
- ARM: 8720/1: ensure dump_instr() checks addr_limit
- ALSA: timer: Limit max instances per timer
- ALSA: usb-audio: support new Amanero Combo384 firmware version
- ALSA: hda - fix headset mic problem for Dell machines with alc274
- ALSA: seq: Fix OSS sysex delivery in OSS emulation
- ALSA: seq: Avoid invalid lockdep class warning
- MIPS: Fix CM region target definitions
- MIPS: BMIPS: Fix missing cbr address
- MIPS: AR7: Defer registration of GPIO
- MIPS: AR7: Ensure that serial ports are properly set up
- KVM: PPC: Book3S HV: Fix exclusion between HPT resizing and other HPT
  updates
- Input: elan_i2c - add ELAN060C to the ACPI table
- rbd: use GFP_NOIO for parent stat and data requests
- drm/vmwgfx: Fix Ubuntu 17.10 Wayland black screen issue
- Revert "x86: CPU: Fix up "cpu MHz" in /proc/cpuinfo"
- can: sun4i: handle overrun in RX FIFO
- can: peak: Add support for new PCIe/M2 CAN FD interfaces
- can: ifi: Fix transmitter delay calculation
- can: c_can: don't indicate triple sampling support for D_CAN
- x86/debug: Handle warnings before the notifier chain, to 

[Kernel-packages] [Bug 1736182] Re: linux-aws: 4.4.0-1005.5 -proposed tracker

2017-12-07 Thread Launchpad Bug Tracker
This bug was fixed in the package linux-aws - 4.4.0-1005.5

---
linux-aws (4.4.0-1005.5) trusty; urgency=low

  * linux-aws: 4.4.0-1005.5 -proposed tracker (LP: #1736182)

  * Update config with NET_DSA=n as required by changes in
 upstream stable update to 4.4.98 (LP: #1732698)

  [ Ubuntu: 4.4.0-103.126 ]

  * linux: 4.4.0-103.126 -proposed tracker (LP: #1736181)
  * CVE-2017-1000405
- mm, thp: Do not make page table dirty unconditionally in touch_p[mu]d()
  * CVE-2017-16939
- netlink: add a start callback for starting a netlink dump
- ipsec: Fix aborted xfrm policy dump crash

  [ Ubuntu: 4.4.0-102.125 ]

  * linux: 4.4.0-102.125 -proposed tracker (LP: #1733541)
  * tar -x sometimes fails on overlayfs (LP: #1728489)
- ovl: check if all layers are on the same fs
- ovl: persistent inode number for directories
  * NVMe timeout is too short (LP: #1729119)
- nvme: update timeout module parameter type
  * Set PANIC_TIMEOUT=10 on Power Systems (LP: #1730660)
- [Config]: Set PANIC_TIMEOUT=10 on ppc64el
  * Cannot pair BLE remote devices when using combo BT SoC (LP: #1731467)
- Bluetooth: increase timeout for le auto connections
  * CIFS errors on 4.4.0-98, but not on 4.4.0-97 with same config (LP: #1729337)
- SMB3: Validate negotiate request must always be signed
  * Plantronics P610 does not support sample rate reading (LP: #1719853)
- ALSA: usb-audio: Add sample rate quirk for Plantronics P610
  * Invalid btree pointer causes the kernel NULL pointer dereference
(LP: #1729256)
- xfs: reinit btree pointer on attr tree inactivation walk
  * Samba mount/umount in docker container triggers kernel Oops (LP: #1729637)
- ipv6: only call ip6_route_dev_notify() once for NETDEV_UNREGISTER
- ipv6: fix NULL dereference in ip6_route_dev_notify()
  * [kernel] tty/hvc: Use opal irqchip interface if available (LP: #1728098)
- tty/hvc: Use opal irqchip interface if available
  * Device hotplugging with MPT SAS cannot work for VMWare ESXi (LP: #1730852)
- scsi: mptsas: Fixup device hotplug for VMWare ESXi
  * NMI watchdog: BUG: soft lockup on Guest upon boot (KVM) (LP: #1727331)
- KVM: PPC: Book3S: Treat VTB as a per-subcore register, not per-thread
  * Attempt to map rbd image from ceph jewel/luminous hangs (LP: #1728739)
- crush: ensure bucket id is valid before indexing buckets array
- crush: ensure take bucket value is valid
- crush: add chooseleaf_stable tunable
- crush: decode and initialize chooseleaf_stable
- libceph: advertise support for TUNABLES5
- libceph: MOSDOpReply v7 encoding
  * Xenial update to 4.4.98 stable release (LP: #1732698)
- adv7604: Initialize drive strength to default when using DT
- video: fbdev: pmag-ba-fb: Remove bad `__init' annotation
- PCI: mvebu: Handle changes to the bridge windows while enabled
- xen/netback: set default upper limit of tx/rx queues to 8
- drm: drm_minor_register(): Clean up debugfs on failure
- KVM: PPC: Book 3S: XICS: correct the real mode ICP rejecting counter
- iommu/arm-smmu-v3: Clear prior settings when updating STEs
- powerpc/corenet: explicitly disable the SDHC controller on kmcoge4
- ARM: omap2plus_defconfig: Fix probe errors on UARTs 5 and 6
- crypto: vmx - disable preemption to enable vsx in aes_ctr.c
- iio: trigger: free trigger resource correctly
- phy: increase size of MII_BUS_ID_SIZE and bus_id
- serial: sh-sci: Fix register offsets for the IRDA serial port
- usb: hcd: initialize hcd->flags to 0 when rm hcd
- netfilter: nft_meta: deal with PACKET_LOOPBACK in netdev family
- IPsec: do not ignore crypto err in ah4 input
- Input: mpr121 - handle multiple bits change of status register
- Input: mpr121 - set missing event capability
- IB/ipoib: Change list_del to list_del_init in the tx object
- s390/qeth: issue STARTLAN as first IPA command
- (config) Add NET_DSA=n
- net: dsa: select NET_SWITCHDEV
- platform/x86: hp-wmi: Fix detection for dock and tablet mode
- cdc_ncm: Set NTB format again after altsetting switch for Huawei devices
- KEYS: trusted: sanitize all key material
- KEYS: trusted: fix writing past end of buffer in trusted_read()
- platform/x86: hp-wmi: Fix error value for hp_wmi_tablet_state
- platform/x86: hp-wmi: Do not shadow error values
- x86/uaccess, sched/preempt: Verify access_ok() context
- workqueue: Fix NULL pointer dereference
- crypto: x86/sha1-mb - fix panic due to unaligned access
- KEYS: fix NULL pointer dereference during ASN.1 parsing [ver #2]
- ARM: 8720/1: ensure dump_instr() checks addr_limit
- ALSA: seq: Fix OSS sysex delivery in OSS emulation
- ALSA: seq: Avoid invalid lockdep class warning
- MIPS: microMIPS: Fix incorrect mask in insn_table_MM
- MIPS: Fix CM region target definitions
- MIPS: SMP: Use a completion event to signal CPU up
- MIPS: Fix race on setting and 

[Kernel-packages] [Bug 1736182] Re: linux-aws: 4.4.0-1005.5 -proposed tracker

2017-12-07 Thread Łukasz Zemczak
** Changed in: kernel-sru-workflow/promote-to-updates
   Status: Confirmed => Fix Committed

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

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

** Changed in: kernel-sru-workflow/promote-to-security
 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-aws in Ubuntu.
https://bugs.launchpad.net/bugs/1736182

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

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

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: 1736181
  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/1736182/+subscriptions

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


[Kernel-packages] [Bug 1736187] Re: linux-aws: 4.4.0-1043.52 -proposed tracker

2017-12-07 Thread Launchpad Bug Tracker
This bug was fixed in the package linux-aws - 4.4.0-1043.52

---
linux-aws (4.4.0-1043.52) xenial; urgency=low

  * linux-aws: 4.4.0-1043.52 -proposed tracker (LP: #1736187)

  [ Ubuntu: 4.4.0-103.126 ]

  * linux: 4.4.0-103.126 -proposed tracker (LP: #1736181)
  * CVE-2017-1000405
- mm, thp: Do not make page table dirty unconditionally in touch_p[mu]d()
  * CVE-2017-16939
- netlink: add a start callback for starting a netlink dump
- ipsec: Fix aborted xfrm policy dump crash

linux-aws (4.4.0-1042.51) xenial; urgency=low

  * linux-aws: 4.4.0-1042.51 -proposed tracker (LP: #1733546)

  * Update config with NET_DSA=n as required by changes in
 upstream stable update to 4.4.98 (LP: #1732698)

  [ Ubuntu: 4.4.0-102.125 ]

  * linux: 4.4.0-102.125 -proposed tracker (LP: #1733541)
  * tar -x sometimes fails on overlayfs (LP: #1728489)
- ovl: check if all layers are on the same fs
- ovl: persistent inode number for directories
  * NVMe timeout is too short (LP: #1729119)
- nvme: update timeout module parameter type
  * Set PANIC_TIMEOUT=10 on Power Systems (LP: #1730660)
- [Config]: Set PANIC_TIMEOUT=10 on ppc64el
  * Cannot pair BLE remote devices when using combo BT SoC (LP: #1731467)
- Bluetooth: increase timeout for le auto connections
  * CIFS errors on 4.4.0-98, but not on 4.4.0-97 with same config (LP: #1729337)
- SMB3: Validate negotiate request must always be signed
  * Plantronics P610 does not support sample rate reading (LP: #1719853)
- ALSA: usb-audio: Add sample rate quirk for Plantronics P610
  * Invalid btree pointer causes the kernel NULL pointer dereference
(LP: #1729256)
- xfs: reinit btree pointer on attr tree inactivation walk
  * Samba mount/umount in docker container triggers kernel Oops (LP: #1729637)
- ipv6: only call ip6_route_dev_notify() once for NETDEV_UNREGISTER
- ipv6: fix NULL dereference in ip6_route_dev_notify()
  * [kernel] tty/hvc: Use opal irqchip interface if available (LP: #1728098)
- tty/hvc: Use opal irqchip interface if available
  * Device hotplugging with MPT SAS cannot work for VMWare ESXi (LP: #1730852)
- scsi: mptsas: Fixup device hotplug for VMWare ESXi
  * NMI watchdog: BUG: soft lockup on Guest upon boot (KVM) (LP: #1727331)
- KVM: PPC: Book3S: Treat VTB as a per-subcore register, not per-thread
  * Attempt to map rbd image from ceph jewel/luminous hangs (LP: #1728739)
- crush: ensure bucket id is valid before indexing buckets array
- crush: ensure take bucket value is valid
- crush: add chooseleaf_stable tunable
- crush: decode and initialize chooseleaf_stable
- libceph: advertise support for TUNABLES5
- libceph: MOSDOpReply v7 encoding
  * Xenial update to 4.4.98 stable release (LP: #1732698)
- adv7604: Initialize drive strength to default when using DT
- video: fbdev: pmag-ba-fb: Remove bad `__init' annotation
- PCI: mvebu: Handle changes to the bridge windows while enabled
- xen/netback: set default upper limit of tx/rx queues to 8
- drm: drm_minor_register(): Clean up debugfs on failure
- KVM: PPC: Book 3S: XICS: correct the real mode ICP rejecting counter
- iommu/arm-smmu-v3: Clear prior settings when updating STEs
- powerpc/corenet: explicitly disable the SDHC controller on kmcoge4
- ARM: omap2plus_defconfig: Fix probe errors on UARTs 5 and 6
- crypto: vmx - disable preemption to enable vsx in aes_ctr.c
- iio: trigger: free trigger resource correctly
- phy: increase size of MII_BUS_ID_SIZE and bus_id
- serial: sh-sci: Fix register offsets for the IRDA serial port
- usb: hcd: initialize hcd->flags to 0 when rm hcd
- netfilter: nft_meta: deal with PACKET_LOOPBACK in netdev family
- IPsec: do not ignore crypto err in ah4 input
- Input: mpr121 - handle multiple bits change of status register
- Input: mpr121 - set missing event capability
- IB/ipoib: Change list_del to list_del_init in the tx object
- s390/qeth: issue STARTLAN as first IPA command
- (config) Add NET_DSA=n
- net: dsa: select NET_SWITCHDEV
- platform/x86: hp-wmi: Fix detection for dock and tablet mode
- cdc_ncm: Set NTB format again after altsetting switch for Huawei devices
- KEYS: trusted: sanitize all key material
- KEYS: trusted: fix writing past end of buffer in trusted_read()
- platform/x86: hp-wmi: Fix error value for hp_wmi_tablet_state
- platform/x86: hp-wmi: Do not shadow error values
- x86/uaccess, sched/preempt: Verify access_ok() context
- workqueue: Fix NULL pointer dereference
- crypto: x86/sha1-mb - fix panic due to unaligned access
- KEYS: fix NULL pointer dereference during ASN.1 parsing [ver #2]
- ARM: 8720/1: ensure dump_instr() checks addr_limit
- ALSA: seq: Fix OSS sysex delivery in OSS emulation
- ALSA: seq: Avoid invalid lockdep class warning
- MIPS: microMIPS: Fix incorrect mask in insn_table_MM
- MIPS: Fix CM region 

[Kernel-packages] [Bug 1736187] Re: linux-aws: 4.4.0-1043.52 -proposed tracker

2017-12-07 Thread Łukasz Zemczak
** Changed in: kernel-sru-workflow/promote-to-updates
   Status: Confirmed => Fix Committed

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

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

** Changed in: kernel-sru-workflow/promote-to-security
 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-aws in Ubuntu.
https://bugs.launchpad.net/bugs/1736187

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

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

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: 1736181
  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/1736187/+subscriptions

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


[Kernel-packages] [Bug 1733306] Re: FS-Cache: Assertion failed

2017-12-07 Thread DanielT
Hi,

Just to update that I've tried to install and boot mainline kernel 4.14.

Unfortunately boot always fails right after "Dec 08 00:17:39 g2
systemd[1]: dev-disk-
by\x2duuid-e9031178\x2d42d7\x2d46bf\x2db1b2\x2d979dc2b54c08.device: Job
dev-disk-
by\x2duuid-e9031178\x2d42d7\x2d46bf\x2db1b2\x2d979dc2b54c08.device/start
timed out." message. I tried adding "x-systemd.device-timeout=5min" to
the corresponding entries in fstab and disabled selinux but still no
luck... (Downgrading the kernel back to original 4.04 works immediately
though)

It'd be appreciated if there're some advices on getting it work :)

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

Title:
  FS-Cache: Assertion failed

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I'm encountering many random kernel panic after enabling fsc with NFS.
  Then I see a number of following err msgs right before it crashed.

  Nov 20 12:04:26 g2 kernel: [170689.549374] FS-Cache: 
  Nov 20 12:04:26 g2 kernel: [170689.549381] FS-Cache: Assertion failed
  Nov 20 12:04:26 g2 kernel: [170689.549384] FS-Cache: 6 == 5 is false
  Nov 20 12:04:26 g2 kernel: [170689.549439] [ cut here 
]
  Nov 20 12:04:26 g2 kernel: [170689.549490] kernel BUG at 
/build/linux-3phnTq/linux-4.4.0/fs/fscache/operation.c:494!
  Nov 20 12:04:26 g2 kernel: [170689.549557] invalid opcode:  [#1] SMP 
  Nov 20 12:04:26 g2 kernel: [170689.549598] Modules linked in: veth xt_nat 
xt_tcpudp ipt_MASQUERADE nf_nat_masquerade_ipv4 nf_conntrack_netlink nfnetlink 
xfrm_user xfrm_algo iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 
xt_addrtype iptable_filter ip_tables xt_conntrack x_tables nf_nat nf_conntrack 
br_netfilter bridge stp llc aufs cachefiles ipmi_devintf rpcsec_gss_krb5 
auth_rpcgss nfsv4 nfs lockd grace fscache snd_hda_codec_hdmi intel_rapl 
x86_pkg_temp_thermal intel_powerclamp kvm_intel kvm ipmi_ssif irqbypass 
serio_raw joydev input_leds snd_hda_intel snd_hda_codec snd_hda_core snd_hwdep 
snd_pcm nvidia_uvm(POE) sb_edac snd_seq_midi snd_seq_midi_event edac_core 
snd_rawmidi snd_seq snd_seq_device snd_timer snd soundcore mei_me lpc_ich mei 
shpchp wmi ipmi_si 8250_fintek ipmi_msghandler acpi_pad acpi_power_meter 
mac_hid sunrpc ib_iser rdma_cm iw_cm ib_cm ib_sa ib_mad ib_core ib_addr 
iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi nct6775 hwmon_vid coretemp 
bonding parport_pc ppdev lp parport autofs4 xfs btrfs raid10 raid456 
async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq 
libcrc32c raid1 raid0 multipath linear nvidia_drm(POE) nvidia_modeset(POE) 
hid_generic crct10dif_pclmul ast crc32_pclmul ghash_clmulni_intel aesni_intel 
aes_x86_64 lrw gf128mul nvidia(POE) glue_helper ttm ablk_helper igb cryptd 
drm_kms_helper psmouse syscopyarea dca sysfillrect ptp sysimgblt fb_sys_fops 
pps_core ahci i2c_algo_bit drm libahci fjes usbhid hid
  Nov 20 12:04:26 g2 kernel: [170689.550993] CPU: 22 PID: 6373 Comm: 
kworker/u98:1 Tainted: P   OE   4.4.0-98-generic #121-Ubuntu
  Nov 20 12:04:26 g2 kernel: [170689.551071] Hardware name: ASUSTeK COMPUTER 
INC. ESC8000 G3 Series/Z10PG-D24 Series, BIOS 3203 05/05/2016
  Nov 20 12:04:26 g2 kernel: [170689.551160] Workqueue: fscache_operation 
fscache_op_work_func [fscache]
  Nov 20 12:04:26 g2 kernel: [170689.551219] task: 882027887000 ti: 
881429ea4000 task.ti: 881429ea4000
  Nov 20 12:04:26 g2 kernel: [170689.551283] RIP: 0010:[]  
[] fscache_put_operation+0x1d6/0x210 [fscache]
  Nov 20 12:04:26 g2 kernel: [170689.551374] RSP: 0018:881429ea7de0  
EFLAGS: 00010282
  Nov 20 12:04:26 g2 kernel: [170689.551421] RAX: 0019 RBX: 
882037224300 RCX: 0006
  Nov 20 12:04:26 g2 kernel: [170689.551490] RDX:  RSI: 
0246 RDI: 88203f28dd50
  Nov 20 12:04:26 g2 kernel: [170689.551551] RBP: 881429ea7df8 R08: 
000a R09: 09c0
  Nov 20 12:04:26 g2 kernel: [170689.551611] R10: 88120db1b300 R11: 
09c0 R12: 882038bf8000
  Nov 20 12:04:26 g2 kernel: [170689.551672] R13: 88202ff08800 R14: 
0c40 R15: 882037224300
  Nov 20 12:04:26 g2 kernel: [170689.551733] FS:  () 
GS:88203f28() knlGS:
  Nov 20 12:04:26 g2 kernel: [170689.551801] CS:  0010 DS:  ES:  CR0: 
80050033
  Nov 20 12:04:26 g2 kernel: [170689.551850] CR2: 7f66b2887500 CR3: 
01e0a000 CR4: 003406e0
  Nov 20 12:04:26 g2 kernel: [170689.551912] DR0:  DR1: 
 DR2: 
  Nov 20 12:04:26 g2 kernel: [170689.551972] DR3:  DR6: 
fffe0ff0 DR7: 0400
  Nov 20 12:04:26 g2 kernel: [170689.552030] Stack:
  Nov 20 12:04:26 g2 kernel: [170689.552051]  882037224300 882038bf8000 
88202ff08800 881429ea7e10
  Nov 20 

[Kernel-packages] [Bug 1737005] [NEW] Mainline kernel 4.14 does not start apparmor

2017-12-07 Thread Klaus Bielke
Public bug reported:

With Ubuntu 16.04.3 LTS (Xenial Xerus), and Ubuntu mainline kernel
4.14.3 or 4.14.4 systemd fails allways starting apparmor.service and
ureadahead.service. Sometimes udisks2.service fails too.

$ uname -a
Linux lieselotte 4.14.4-041404-generic #201712050630 SMP Tue Dec 5 12:07:25 UTC 
2017 i686 i686 i686 GNU/Linux

$ systemctl --failed
  UNIT   LOAD   ACTIVE SUBDESCRIPTION
● apparmor.service   loaded failed failed LSB: AppArmor initialization
● udisks2.serviceloaded failed failed Disk Manager
● ureadahead.service loaded failed failed Read required files in advance

$ systemctl status apparmor.service
● apparmor.service - LSB: AppArmor initialization
   Loaded: loaded (/etc/init.d/apparmor; bad; vendor preset: enabled)
   Active: failed (Result: exit-code) since Do 2017-12-07 18:04:51 CET; 52min 
ago
 Docs: man:systemd-sysv-generator(8)
  Process: 689 ExecStart=/etc/init.d/apparmor start (code=exited, 
status=1/FAILURE)

Dez 07 18:04:51 lieselotte systemd[1]: Starting LSB: AppArmor initialization...
Dez 07 18:04:51 lieselotte apparmor[689]:  * Starting AppArmor profiles
Dez 07 18:04:51 lieselotte apparmor[689]:  * AppArmor not available as kernel 
LSM.
Dez 07 18:04:51 lieselotte apparmor[689]:...fail!
Dez 07 18:04:51 lieselotte systemd[1]: apparmor.service: Control process 
exited, code=exited status=1
Dez 07 18:04:51 lieselotte systemd[1]: Failed to start LSB: AppArmor 
initialization.
Dez 07 18:04:51 lieselotte systemd[1]: apparmor.service: Unit entered failed 
state.
Dez 07 18:04:51 lieselotte systemd[1]: apparmor.service: Failed with result 
'exit-code'.

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


** Tags: apparmor kernel-bug xenial

** Description changed:

- With Ubuntu 16.04.3 LTS (Xenial Xerus), and mainline kernel 4.14.3 or
- 4.14.4 systemd fails allways starting apparmor.service and
+ With Ubuntu 16.04.3 LTS (Xenial Xerus), and Ubuntu mainline kernel
+ 4.14.3 or 4.14.4 systemd fails allways starting apparmor.service and
  ureadahead.service. Sometimes udisks2.service failes too.
  
  $ systemctl --failed
-   UNIT   LOAD   ACTIVE SUBDESCRIPTION
+   UNIT   LOAD   ACTIVE SUBDESCRIPTION
  ● apparmor.service   loaded failed failed LSB: AppArmor initialization
  ● udisks2.serviceloaded failed failed Disk Manager
  ● ureadahead.service loaded failed failed Read required files in advance
  
- $ systemctl status apparmor.service 
+ $ systemctl status apparmor.service
  ● apparmor.service - LSB: AppArmor initialization
-Loaded: loaded (/etc/init.d/apparmor; bad; vendor preset: enabled)
-Active: failed (Result: exit-code) since Do 2017-12-07 18:04:51 CET; 52min 
ago
-  Docs: man:systemd-sysv-generator(8)
-   Process: 689 ExecStart=/etc/init.d/apparmor start (code=exited, 
status=1/FAILURE)
+    Loaded: loaded (/etc/init.d/apparmor; bad; vendor preset: enabled)
+    Active: failed (Result: exit-code) since Do 2017-12-07 18:04:51 CET; 52min 
ago
+  Docs: man:systemd-sysv-generator(8)
+   Process: 689 ExecStart=/etc/init.d/apparmor start (code=exited, 
status=1/FAILURE)
  
  Dez 07 18:04:51 lieselotte systemd[1]: Starting LSB: AppArmor 
initialization...
  Dez 07 18:04:51 lieselotte apparmor[689]:  * Starting AppArmor profiles
  Dez 07 18:04:51 lieselotte apparmor[689]:  * AppArmor not available as kernel 
LSM.
  Dez 07 18:04:51 lieselotte apparmor[689]:...fail!
  Dez 07 18:04:51 lieselotte systemd[1]: apparmor.service: Control process 
exited, code=exited status=1
  Dez 07 18:04:51 lieselotte systemd[1]: Failed to start LSB: AppArmor 
initialization.
  Dez 07 18:04:51 lieselotte systemd[1]: apparmor.service: Unit entered failed 
state.
  Dez 07 18:04:51 lieselotte systemd[1]: apparmor.service: Failed with result 
'exit-code'.

** Description changed:

  With Ubuntu 16.04.3 LTS (Xenial Xerus), and Ubuntu mainline kernel
  4.14.3 or 4.14.4 systemd fails allways starting apparmor.service and
- ureadahead.service. Sometimes udisks2.service failes too.
+ ureadahead.service. Sometimes udisks2.service fails too.
  
  $ systemctl --failed
    UNIT   LOAD   ACTIVE SUBDESCRIPTION
  ● apparmor.service   loaded failed failed LSB: AppArmor initialization
  ● udisks2.serviceloaded failed failed Disk Manager
  ● ureadahead.service loaded failed failed Read required files in advance
  
  $ systemctl status apparmor.service
  ● apparmor.service - LSB: AppArmor initialization
     Loaded: loaded (/etc/init.d/apparmor; bad; vendor preset: enabled)
     Active: failed (Result: exit-code) since Do 2017-12-07 18:04:51 CET; 52min 
ago
   Docs: man:systemd-sysv-generator(8)
    Process: 689 ExecStart=/etc/init.d/apparmor start (code=exited, 
status=1/FAILURE)
  
  Dez 07 18:04:51 lieselotte systemd[1]: Starting LSB: AppArmor 
initialization...
  Dez 07 18:04:51 lieselotte apparmor[689]:  * Starting AppArmor profiles
  Dez 07 18:04:51 lieselotte apparmor[689]:  * AppArmor 

[Kernel-packages] [Bug 1736118] Re: linux: 4.13.0-19.22 -proposed tracker

2017-12-07 Thread Brad Figg
** Changed in: kernel-sru-workflow/promote-to-security
   Status: Fix Committed => 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: 1736120,1736121,1736123,1736124
  derivatives: 1736125
  -- swm properties --
  boot-testing-requested: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true
+ kernel-stable-phase-changed:Thursday, 07. December 2017 18:04 UTC
+ kernel-stable-phase:Promoted to security

** 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: 1736120,1736121,1736123,1736124
  derivatives: 1736125
  -- swm properties --
  boot-testing-requested: true
- phase: Promoted to proposed
+ phase: Promoted to security
  proposed-announcement-sent: true
  proposed-testing-requested: true
- kernel-stable-phase-changed:Thursday, 07. December 2017 18:04 UTC
- kernel-stable-phase:Promoted to security

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

Title:
  linux: 4.13.0-19.22 -proposed tracker

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

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: 1736120,1736121,1736123,1736124
  derivatives: 1736125
  -- swm properties --
  boot-testing-requested: true
  phase: Promoted to security
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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


[Kernel-packages] [Bug 1736181] Re: linux: 4.4.0-103.126 -proposed tracker

2017-12-07 Thread Brad Figg
** Changed in: kernel-sru-workflow/promote-to-security
   Status: Fix Committed => 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: 1736182,1736183
  derivatives: 1736185,1736186,1736187,1736188,1736189,1736191
  -- swm properties --
  boot-testing-requested: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true
+ kernel-stable-phase-changed:Thursday, 07. December 2017 18:04 UTC
+ kernel-stable-phase:Promoted to security

** 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: 1736182,1736183
  derivatives: 1736185,1736186,1736187,1736188,1736189,1736191
  -- swm properties --
  boot-testing-requested: true
- phase: Promoted to proposed
+ phase: Promoted to security
  proposed-announcement-sent: true
  proposed-testing-requested: true
- kernel-stable-phase-changed:Thursday, 07. December 2017 18:04 UTC
- kernel-stable-phase:Promoted to security

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

Title:
  linux: 4.4.0-103.126 -proposed tracker

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

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: 1736182,1736183
  derivatives: 1736185,1736186,1736187,1736188,1736189,1736191
  -- swm properties --
  boot-testing-requested: true
  phase: Promoted to security
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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


[Kernel-packages] [Bug 1737005] [NEW] Mainline kernel 4.14 does not start apparmor

2017-12-07 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

With Ubuntu 16.04.3 LTS (Xenial Xerus), and Ubuntu mainline kernel
4.14.3 or 4.14.4 systemd fails allways starting apparmor.service and
ureadahead.service. Sometimes udisks2.service fails too.

$ systemctl --failed
  UNIT   LOAD   ACTIVE SUBDESCRIPTION
● apparmor.service   loaded failed failed LSB: AppArmor initialization
● udisks2.serviceloaded failed failed Disk Manager
● ureadahead.service loaded failed failed Read required files in advance

$ systemctl status apparmor.service
● apparmor.service - LSB: AppArmor initialization
   Loaded: loaded (/etc/init.d/apparmor; bad; vendor preset: enabled)
   Active: failed (Result: exit-code) since Do 2017-12-07 18:04:51 CET; 52min 
ago
 Docs: man:systemd-sysv-generator(8)
  Process: 689 ExecStart=/etc/init.d/apparmor start (code=exited, 
status=1/FAILURE)

Dez 07 18:04:51 lieselotte systemd[1]: Starting LSB: AppArmor initialization...
Dez 07 18:04:51 lieselotte apparmor[689]:  * Starting AppArmor profiles
Dez 07 18:04:51 lieselotte apparmor[689]:  * AppArmor not available as kernel 
LSM.
Dez 07 18:04:51 lieselotte apparmor[689]:...fail!
Dez 07 18:04:51 lieselotte systemd[1]: apparmor.service: Control process 
exited, code=exited status=1
Dez 07 18:04:51 lieselotte systemd[1]: Failed to start LSB: AppArmor 
initialization.
Dez 07 18:04:51 lieselotte systemd[1]: apparmor.service: Unit entered failed 
state.
Dez 07 18:04:51 lieselotte systemd[1]: apparmor.service: Failed with result 
'exit-code'.

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


** Tags: apparmor kernel-bug xenial
-- 
Mainline kernel 4.14 does not start apparmor
https://bugs.launchpad.net/bugs/1737005
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 1481347] Re: Power8 Nest PMU Instrumentation support

2017-12-07 Thread Launchpad Bug Tracker
This bug was fixed in the package linux - 4.13.0-19.22

---
linux (4.13.0-19.22) artful; urgency=low

  * linux: 4.13.0-19.22 -proposed tracker (LP: #1736118)

  * CVE-2017-1000405
- mm, thp: Do not make page table dirty unconditionally in touch_p[mu]d()

linux (4.13.0-18.21) artful; urgency=low

  * linux: 4.13.0-18.21 -proposed tracker (LP: #1733530)

  * NVMe timeout is too short (LP: #1729119)
- nvme: update timeout module parameter type

  * CPU call trace on AMD Raven Ridge after S3 (LP: #1732894)
- x86/mce/AMD: Allow any CPU to initialize the smca_banks array

  * Set PANIC_TIMEOUT=10 on Power Systems (LP: #1730660)
- [Config]: Set PANIC_TIMEOUT=10 on ppc64el

  * Cannot pair BLE remote devices when using combo BT SoC (LP: #1731467)
- Bluetooth: increase timeout for le auto connections

  * enable CONFIG_SND_SOC_INTEL_BYT_CHT_NOCODEC_MACH easily confuse users
(LP: #1732627)
- [Config] CONFIG_SND_SOC_INTEL_BYT_CHT_NOCODEC_MACH=n

  * Plantronics P610 does not support sample rate reading (LP: #1719853)
- ALSA: usb-audio: Add sample rate quirk for Plantronics P610

  * Allow drivers to use Relaxed Ordering on capable root ports (LP: #1721365)
- Revert commit 1a8b6d76dc5b ("net:add one common config...")
- net: ixgbe: Use new PCI_DEV_FLAGS_NO_RELAXED_ORDERING flag

  * support GICv3 ITS save/restore & migration (LP: #1710019)
- KVM: arm/arm64: vgic-its: Fix return value for device table restore

  * Device hotplugging with MPT SAS cannot work for VMWare ESXi (LP: #1730852)
- scsi: mptsas: Fixup device hotplug for VMWare ESXi

  * Artful update to 4.13.13 stable release (LP: #1732726)
- netfilter: nat: Revert "netfilter: nat: convert nat bysrc hash to
  rhashtable"
- netfilter: nft_set_hash: disable fast_ops for 2-len keys
- workqueue: Fix NULL pointer dereference
- crypto: ccm - preserve the IV buffer
- crypto: x86/sha1-mb - fix panic due to unaligned access
- crypto: x86/sha256-mb - fix panic due to unaligned access
- KEYS: fix NULL pointer dereference during ASN.1 parsing [ver #2]
- ACPI / PM: Blacklist Low Power S0 Idle _DSM for Dell XPS13 9360
- ARM: 8720/1: ensure dump_instr() checks addr_limit
- ALSA: timer: Limit max instances per timer
- ALSA: usb-audio: support new Amanero Combo384 firmware version
- ALSA: hda - fix headset mic problem for Dell machines with alc274
- ALSA: seq: Fix OSS sysex delivery in OSS emulation
- ALSA: seq: Avoid invalid lockdep class warning
- MIPS: Fix CM region target definitions
- MIPS: BMIPS: Fix missing cbr address
- MIPS: AR7: Defer registration of GPIO
- MIPS: AR7: Ensure that serial ports are properly set up
- KVM: PPC: Book3S HV: Fix exclusion between HPT resizing and other HPT
  updates
- Input: elan_i2c - add ELAN060C to the ACPI table
- rbd: use GFP_NOIO for parent stat and data requests
- drm/vmwgfx: Fix Ubuntu 17.10 Wayland black screen issue
- Revert "x86: CPU: Fix up "cpu MHz" in /proc/cpuinfo"
- can: sun4i: handle overrun in RX FIFO
- can: peak: Add support for new PCIe/M2 CAN FD interfaces
- can: ifi: Fix transmitter delay calculation
- can: c_can: don't indicate triple sampling support for D_CAN
- x86/debug: Handle warnings before the notifier chain, to fix KGDB crash
- x86/smpboot: Make optimization of delay calibration work correctly
- x86/oprofile/ppro: Do not use __this_cpu*() in preemptible context
- Linux 4.13.13

  * ELANTECH Touchpad is not detected in 'Lenovo Ideapad 320 14AST' after fresh
install (LP: #1727544)
- Input: elan_i2c - add ELAN060C to the ACPI table

  * Power8 Nest PMU Instrumentation support (LP: #1481347)
- powerpc/powernv: Add IMC OPAL APIs
- powerpc/powernv: Detect and create IMC device
- powerpc/perf: Add nest IMC PMU support
- powerpc/perf: Add core IMC PMU support
- powerpc/perf: Add thread IMC PMU support
- powerpc/perf: Fix double unlock in imc_common_cpuhp_mem_free()
- powerpc/perf/imc: Fix nest events on muti socket system
- powerpc/powernv: Fix build error in opal-imc.c when NUMA=n
- powerpc/perf: Fix usage of nest_imc_refc
- powerpc/perf: Fix for core/nest imc call trace on cpuhotplug
- powerpc/perf: Add ___GFP_NOWARN flag to alloc_pages_node()
- powerpc/perf: Fix IMC initialization crash

  * Artful update to 4.13.12 stable release (LP: #1731971)
- ALSA: timer: Add missing mutex lock for compat ioctls
- ALSA: seq: Fix nested rwsem annotation for lockdep splat
- cifs: check MaxPathNameComponentLength != 0 before using it
- KEYS: return full count in keyring_read() if buffer is too small
- KEYS: trusted: fix writing past end of buffer in trusted_read()
- KEYS: fix out-of-bounds read during ASN.1 parsing
- ASoC: adau17x1: Workaround for noise bug in ADC
- virtio_blk: Fix an SG_IO regression
- arm64: ensure __dump_instr() checks addr_limit
 

[Kernel-packages] [Bug 1731467] Re: Cannot pair BLE remote devices when using combo BT SoC

2017-12-07 Thread Launchpad Bug Tracker
This bug was fixed in the package linux - 4.13.0-19.22

---
linux (4.13.0-19.22) artful; urgency=low

  * linux: 4.13.0-19.22 -proposed tracker (LP: #1736118)

  * CVE-2017-1000405
- mm, thp: Do not make page table dirty unconditionally in touch_p[mu]d()

linux (4.13.0-18.21) artful; urgency=low

  * linux: 4.13.0-18.21 -proposed tracker (LP: #1733530)

  * NVMe timeout is too short (LP: #1729119)
- nvme: update timeout module parameter type

  * CPU call trace on AMD Raven Ridge after S3 (LP: #1732894)
- x86/mce/AMD: Allow any CPU to initialize the smca_banks array

  * Set PANIC_TIMEOUT=10 on Power Systems (LP: #1730660)
- [Config]: Set PANIC_TIMEOUT=10 on ppc64el

  * Cannot pair BLE remote devices when using combo BT SoC (LP: #1731467)
- Bluetooth: increase timeout for le auto connections

  * enable CONFIG_SND_SOC_INTEL_BYT_CHT_NOCODEC_MACH easily confuse users
(LP: #1732627)
- [Config] CONFIG_SND_SOC_INTEL_BYT_CHT_NOCODEC_MACH=n

  * Plantronics P610 does not support sample rate reading (LP: #1719853)
- ALSA: usb-audio: Add sample rate quirk for Plantronics P610

  * Allow drivers to use Relaxed Ordering on capable root ports (LP: #1721365)
- Revert commit 1a8b6d76dc5b ("net:add one common config...")
- net: ixgbe: Use new PCI_DEV_FLAGS_NO_RELAXED_ORDERING flag

  * support GICv3 ITS save/restore & migration (LP: #1710019)
- KVM: arm/arm64: vgic-its: Fix return value for device table restore

  * Device hotplugging with MPT SAS cannot work for VMWare ESXi (LP: #1730852)
- scsi: mptsas: Fixup device hotplug for VMWare ESXi

  * Artful update to 4.13.13 stable release (LP: #1732726)
- netfilter: nat: Revert "netfilter: nat: convert nat bysrc hash to
  rhashtable"
- netfilter: nft_set_hash: disable fast_ops for 2-len keys
- workqueue: Fix NULL pointer dereference
- crypto: ccm - preserve the IV buffer
- crypto: x86/sha1-mb - fix panic due to unaligned access
- crypto: x86/sha256-mb - fix panic due to unaligned access
- KEYS: fix NULL pointer dereference during ASN.1 parsing [ver #2]
- ACPI / PM: Blacklist Low Power S0 Idle _DSM for Dell XPS13 9360
- ARM: 8720/1: ensure dump_instr() checks addr_limit
- ALSA: timer: Limit max instances per timer
- ALSA: usb-audio: support new Amanero Combo384 firmware version
- ALSA: hda - fix headset mic problem for Dell machines with alc274
- ALSA: seq: Fix OSS sysex delivery in OSS emulation
- ALSA: seq: Avoid invalid lockdep class warning
- MIPS: Fix CM region target definitions
- MIPS: BMIPS: Fix missing cbr address
- MIPS: AR7: Defer registration of GPIO
- MIPS: AR7: Ensure that serial ports are properly set up
- KVM: PPC: Book3S HV: Fix exclusion between HPT resizing and other HPT
  updates
- Input: elan_i2c - add ELAN060C to the ACPI table
- rbd: use GFP_NOIO for parent stat and data requests
- drm/vmwgfx: Fix Ubuntu 17.10 Wayland black screen issue
- Revert "x86: CPU: Fix up "cpu MHz" in /proc/cpuinfo"
- can: sun4i: handle overrun in RX FIFO
- can: peak: Add support for new PCIe/M2 CAN FD interfaces
- can: ifi: Fix transmitter delay calculation
- can: c_can: don't indicate triple sampling support for D_CAN
- x86/debug: Handle warnings before the notifier chain, to fix KGDB crash
- x86/smpboot: Make optimization of delay calibration work correctly
- x86/oprofile/ppro: Do not use __this_cpu*() in preemptible context
- Linux 4.13.13

  * ELANTECH Touchpad is not detected in 'Lenovo Ideapad 320 14AST' after fresh
install (LP: #1727544)
- Input: elan_i2c - add ELAN060C to the ACPI table

  * Power8 Nest PMU Instrumentation support (LP: #1481347)
- powerpc/powernv: Add IMC OPAL APIs
- powerpc/powernv: Detect and create IMC device
- powerpc/perf: Add nest IMC PMU support
- powerpc/perf: Add core IMC PMU support
- powerpc/perf: Add thread IMC PMU support
- powerpc/perf: Fix double unlock in imc_common_cpuhp_mem_free()
- powerpc/perf/imc: Fix nest events on muti socket system
- powerpc/powernv: Fix build error in opal-imc.c when NUMA=n
- powerpc/perf: Fix usage of nest_imc_refc
- powerpc/perf: Fix for core/nest imc call trace on cpuhotplug
- powerpc/perf: Add ___GFP_NOWARN flag to alloc_pages_node()
- powerpc/perf: Fix IMC initialization crash

  * Artful update to 4.13.12 stable release (LP: #1731971)
- ALSA: timer: Add missing mutex lock for compat ioctls
- ALSA: seq: Fix nested rwsem annotation for lockdep splat
- cifs: check MaxPathNameComponentLength != 0 before using it
- KEYS: return full count in keyring_read() if buffer is too small
- KEYS: trusted: fix writing past end of buffer in trusted_read()
- KEYS: fix out-of-bounds read during ASN.1 parsing
- ASoC: adau17x1: Workaround for noise bug in ADC
- virtio_blk: Fix an SG_IO regression
- arm64: ensure __dump_instr() checks addr_limit
 

[Kernel-packages] [Bug 1729119] Re: NVMe timeout is too short

2017-12-07 Thread Launchpad Bug Tracker
This bug was fixed in the package linux - 4.13.0-19.22

---
linux (4.13.0-19.22) artful; urgency=low

  * linux: 4.13.0-19.22 -proposed tracker (LP: #1736118)

  * CVE-2017-1000405
- mm, thp: Do not make page table dirty unconditionally in touch_p[mu]d()

linux (4.13.0-18.21) artful; urgency=low

  * linux: 4.13.0-18.21 -proposed tracker (LP: #1733530)

  * NVMe timeout is too short (LP: #1729119)
- nvme: update timeout module parameter type

  * CPU call trace on AMD Raven Ridge after S3 (LP: #1732894)
- x86/mce/AMD: Allow any CPU to initialize the smca_banks array

  * Set PANIC_TIMEOUT=10 on Power Systems (LP: #1730660)
- [Config]: Set PANIC_TIMEOUT=10 on ppc64el

  * Cannot pair BLE remote devices when using combo BT SoC (LP: #1731467)
- Bluetooth: increase timeout for le auto connections

  * enable CONFIG_SND_SOC_INTEL_BYT_CHT_NOCODEC_MACH easily confuse users
(LP: #1732627)
- [Config] CONFIG_SND_SOC_INTEL_BYT_CHT_NOCODEC_MACH=n

  * Plantronics P610 does not support sample rate reading (LP: #1719853)
- ALSA: usb-audio: Add sample rate quirk for Plantronics P610

  * Allow drivers to use Relaxed Ordering on capable root ports (LP: #1721365)
- Revert commit 1a8b6d76dc5b ("net:add one common config...")
- net: ixgbe: Use new PCI_DEV_FLAGS_NO_RELAXED_ORDERING flag

  * support GICv3 ITS save/restore & migration (LP: #1710019)
- KVM: arm/arm64: vgic-its: Fix return value for device table restore

  * Device hotplugging with MPT SAS cannot work for VMWare ESXi (LP: #1730852)
- scsi: mptsas: Fixup device hotplug for VMWare ESXi

  * Artful update to 4.13.13 stable release (LP: #1732726)
- netfilter: nat: Revert "netfilter: nat: convert nat bysrc hash to
  rhashtable"
- netfilter: nft_set_hash: disable fast_ops for 2-len keys
- workqueue: Fix NULL pointer dereference
- crypto: ccm - preserve the IV buffer
- crypto: x86/sha1-mb - fix panic due to unaligned access
- crypto: x86/sha256-mb - fix panic due to unaligned access
- KEYS: fix NULL pointer dereference during ASN.1 parsing [ver #2]
- ACPI / PM: Blacklist Low Power S0 Idle _DSM for Dell XPS13 9360
- ARM: 8720/1: ensure dump_instr() checks addr_limit
- ALSA: timer: Limit max instances per timer
- ALSA: usb-audio: support new Amanero Combo384 firmware version
- ALSA: hda - fix headset mic problem for Dell machines with alc274
- ALSA: seq: Fix OSS sysex delivery in OSS emulation
- ALSA: seq: Avoid invalid lockdep class warning
- MIPS: Fix CM region target definitions
- MIPS: BMIPS: Fix missing cbr address
- MIPS: AR7: Defer registration of GPIO
- MIPS: AR7: Ensure that serial ports are properly set up
- KVM: PPC: Book3S HV: Fix exclusion between HPT resizing and other HPT
  updates
- Input: elan_i2c - add ELAN060C to the ACPI table
- rbd: use GFP_NOIO for parent stat and data requests
- drm/vmwgfx: Fix Ubuntu 17.10 Wayland black screen issue
- Revert "x86: CPU: Fix up "cpu MHz" in /proc/cpuinfo"
- can: sun4i: handle overrun in RX FIFO
- can: peak: Add support for new PCIe/M2 CAN FD interfaces
- can: ifi: Fix transmitter delay calculation
- can: c_can: don't indicate triple sampling support for D_CAN
- x86/debug: Handle warnings before the notifier chain, to fix KGDB crash
- x86/smpboot: Make optimization of delay calibration work correctly
- x86/oprofile/ppro: Do not use __this_cpu*() in preemptible context
- Linux 4.13.13

  * ELANTECH Touchpad is not detected in 'Lenovo Ideapad 320 14AST' after fresh
install (LP: #1727544)
- Input: elan_i2c - add ELAN060C to the ACPI table

  * Power8 Nest PMU Instrumentation support (LP: #1481347)
- powerpc/powernv: Add IMC OPAL APIs
- powerpc/powernv: Detect and create IMC device
- powerpc/perf: Add nest IMC PMU support
- powerpc/perf: Add core IMC PMU support
- powerpc/perf: Add thread IMC PMU support
- powerpc/perf: Fix double unlock in imc_common_cpuhp_mem_free()
- powerpc/perf/imc: Fix nest events on muti socket system
- powerpc/powernv: Fix build error in opal-imc.c when NUMA=n
- powerpc/perf: Fix usage of nest_imc_refc
- powerpc/perf: Fix for core/nest imc call trace on cpuhotplug
- powerpc/perf: Add ___GFP_NOWARN flag to alloc_pages_node()
- powerpc/perf: Fix IMC initialization crash

  * Artful update to 4.13.12 stable release (LP: #1731971)
- ALSA: timer: Add missing mutex lock for compat ioctls
- ALSA: seq: Fix nested rwsem annotation for lockdep splat
- cifs: check MaxPathNameComponentLength != 0 before using it
- KEYS: return full count in keyring_read() if buffer is too small
- KEYS: trusted: fix writing past end of buffer in trusted_read()
- KEYS: fix out-of-bounds read during ASN.1 parsing
- ASoC: adau17x1: Workaround for noise bug in ADC
- virtio_blk: Fix an SG_IO regression
- arm64: ensure __dump_instr() checks addr_limit
 

[Kernel-packages] [Bug 1481347] Re: Power8 Nest PMU Instrumentation support

2017-12-07 Thread Launchpad Bug Tracker
This bug was fixed in the package linux - 4.13.0-19.22

---
linux (4.13.0-19.22) artful; urgency=low

  * linux: 4.13.0-19.22 -proposed tracker (LP: #1736118)

  * CVE-2017-1000405
- mm, thp: Do not make page table dirty unconditionally in touch_p[mu]d()

linux (4.13.0-18.21) artful; urgency=low

  * linux: 4.13.0-18.21 -proposed tracker (LP: #1733530)

  * NVMe timeout is too short (LP: #1729119)
- nvme: update timeout module parameter type

  * CPU call trace on AMD Raven Ridge after S3 (LP: #1732894)
- x86/mce/AMD: Allow any CPU to initialize the smca_banks array

  * Set PANIC_TIMEOUT=10 on Power Systems (LP: #1730660)
- [Config]: Set PANIC_TIMEOUT=10 on ppc64el

  * Cannot pair BLE remote devices when using combo BT SoC (LP: #1731467)
- Bluetooth: increase timeout for le auto connections

  * enable CONFIG_SND_SOC_INTEL_BYT_CHT_NOCODEC_MACH easily confuse users
(LP: #1732627)
- [Config] CONFIG_SND_SOC_INTEL_BYT_CHT_NOCODEC_MACH=n

  * Plantronics P610 does not support sample rate reading (LP: #1719853)
- ALSA: usb-audio: Add sample rate quirk for Plantronics P610

  * Allow drivers to use Relaxed Ordering on capable root ports (LP: #1721365)
- Revert commit 1a8b6d76dc5b ("net:add one common config...")
- net: ixgbe: Use new PCI_DEV_FLAGS_NO_RELAXED_ORDERING flag

  * support GICv3 ITS save/restore & migration (LP: #1710019)
- KVM: arm/arm64: vgic-its: Fix return value for device table restore

  * Device hotplugging with MPT SAS cannot work for VMWare ESXi (LP: #1730852)
- scsi: mptsas: Fixup device hotplug for VMWare ESXi

  * Artful update to 4.13.13 stable release (LP: #1732726)
- netfilter: nat: Revert "netfilter: nat: convert nat bysrc hash to
  rhashtable"
- netfilter: nft_set_hash: disable fast_ops for 2-len keys
- workqueue: Fix NULL pointer dereference
- crypto: ccm - preserve the IV buffer
- crypto: x86/sha1-mb - fix panic due to unaligned access
- crypto: x86/sha256-mb - fix panic due to unaligned access
- KEYS: fix NULL pointer dereference during ASN.1 parsing [ver #2]
- ACPI / PM: Blacklist Low Power S0 Idle _DSM for Dell XPS13 9360
- ARM: 8720/1: ensure dump_instr() checks addr_limit
- ALSA: timer: Limit max instances per timer
- ALSA: usb-audio: support new Amanero Combo384 firmware version
- ALSA: hda - fix headset mic problem for Dell machines with alc274
- ALSA: seq: Fix OSS sysex delivery in OSS emulation
- ALSA: seq: Avoid invalid lockdep class warning
- MIPS: Fix CM region target definitions
- MIPS: BMIPS: Fix missing cbr address
- MIPS: AR7: Defer registration of GPIO
- MIPS: AR7: Ensure that serial ports are properly set up
- KVM: PPC: Book3S HV: Fix exclusion between HPT resizing and other HPT
  updates
- Input: elan_i2c - add ELAN060C to the ACPI table
- rbd: use GFP_NOIO for parent stat and data requests
- drm/vmwgfx: Fix Ubuntu 17.10 Wayland black screen issue
- Revert "x86: CPU: Fix up "cpu MHz" in /proc/cpuinfo"
- can: sun4i: handle overrun in RX FIFO
- can: peak: Add support for new PCIe/M2 CAN FD interfaces
- can: ifi: Fix transmitter delay calculation
- can: c_can: don't indicate triple sampling support for D_CAN
- x86/debug: Handle warnings before the notifier chain, to fix KGDB crash
- x86/smpboot: Make optimization of delay calibration work correctly
- x86/oprofile/ppro: Do not use __this_cpu*() in preemptible context
- Linux 4.13.13

  * ELANTECH Touchpad is not detected in 'Lenovo Ideapad 320 14AST' after fresh
install (LP: #1727544)
- Input: elan_i2c - add ELAN060C to the ACPI table

  * Power8 Nest PMU Instrumentation support (LP: #1481347)
- powerpc/powernv: Add IMC OPAL APIs
- powerpc/powernv: Detect and create IMC device
- powerpc/perf: Add nest IMC PMU support
- powerpc/perf: Add core IMC PMU support
- powerpc/perf: Add thread IMC PMU support
- powerpc/perf: Fix double unlock in imc_common_cpuhp_mem_free()
- powerpc/perf/imc: Fix nest events on muti socket system
- powerpc/powernv: Fix build error in opal-imc.c when NUMA=n
- powerpc/perf: Fix usage of nest_imc_refc
- powerpc/perf: Fix for core/nest imc call trace on cpuhotplug
- powerpc/perf: Add ___GFP_NOWARN flag to alloc_pages_node()
- powerpc/perf: Fix IMC initialization crash

  * Artful update to 4.13.12 stable release (LP: #1731971)
- ALSA: timer: Add missing mutex lock for compat ioctls
- ALSA: seq: Fix nested rwsem annotation for lockdep splat
- cifs: check MaxPathNameComponentLength != 0 before using it
- KEYS: return full count in keyring_read() if buffer is too small
- KEYS: trusted: fix writing past end of buffer in trusted_read()
- KEYS: fix out-of-bounds read during ASN.1 parsing
- ASoC: adau17x1: Workaround for noise bug in ADC
- virtio_blk: Fix an SG_IO regression
- arm64: ensure __dump_instr() checks addr_limit
 

[Kernel-packages] [Bug 1719697] Re: Boot/Installation crash of Ubuntu-16.04.3 HWE kernel on R940

2017-12-07 Thread Launchpad Bug Tracker
This bug was fixed in the package linux - 4.10.0-42.46

---
linux (4.10.0-42.46) zesty; urgency=low

  * linux: 4.10.0-42.46 -proposed tracker (LP: #1736152)

  * CVE-2017-1000405
- mm, thp: Do not make page table dirty unconditionally in touch_p[mu]d()

  * CVE-2017-16939
- ipsec: Fix aborted xfrm policy dump crash

linux (4.10.0-41.45) zesty; urgency=low

  * linux: 4.10.0-41.45 -proposed tracker (LP: #1733524)

  * tar -x sometimes fails on overlayfs (LP: #1728489)
- ovl: check if all layers are on the same fs
- ovl: persistent inode number for directories

  * CVE-2017-12146
- driver core: platform: fix race condition with driver_override

  * NVMe timeout is too short (LP: #1729119)
- nvme: update timeout module parameter type

  * Set PANIC_TIMEOUT=10 on Power Systems (LP: #1730660)
- [Config]: Set PANIC_TIMEOUT=10 on ppc64el

  * Cannot pair BLE remote devices when using combo BT SoC (LP: #1731467)
- Bluetooth: increase timeout for le auto connections

  * Plantronics P610 does not support sample rate reading (LP: #1719853)
- ALSA: usb-audio: Add sample rate quirk for Plantronics P610

  * Invalid btree pointer causes the kernel NULL pointer dereference
(LP: #1729256)
- xfs: reinit btree pointer on attr tree inactivation walk

  * Samba mount/umount in docker container triggers kernel Oops (LP: #1729637)
- ipv6: only call ip6_route_dev_notify() once for NETDEV_UNREGISTER
- ipv6: fix NULL dereference in ip6_route_dev_notify()

  * Device hotplugging with MPT SAS cannot work for VMWare ESXi (LP: #1730852)
- scsi: mptsas: Fixup device hotplug for VMWare ESXi

  * Boot/Installation crash of Ubuntu-16.04.3 HWE kernel on R940 (LP: #1719697)
- Revert "x86/acpi: Set persistent cpuid <-> nodeid mapping when booting"

 -- Stefan Bader   Mon, 04 Dec 2017 15:04:01
+0100

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

Title:
  Boot/Installation crash of Ubuntu-16.04.3 HWE kernel on R940

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

Bug description:

  == SRU Justification ==
  Kernel crashes when installation of Ubuntu-16.04.3 with HWE (ISO).
  Same observation while booting to 4.10.0-28 HWE kerenl of Ubuntu-16.04.3
  and 4.10.0-33 HWE as well.

  Seen only with 4.10 HWE kernels of Ubuntu-16.04.3.  4.4 kernels of
  Ubuntu-16.04.3 works fine. Daily builds of Ubuntu Server 17.10 works fine.

  Reducing the core count to <26 cores helps here. Boot & installation of
  HWE-kernel works fine.

  This bug was introduced by commit:
  dc6db24d2476 ("x86/acpi: Set persistent cpuid <-> nodeid mapping when 
booting")

  It is resolved by reverting commit dc6db24d2476, which was done in mainline 
by 
  commit c962cff17df as of v4.11-rc3.

  There are three additiona commits introduced by the same patch author when
  commit c962cff17df was submitted.  However, it was confirmed that only the 
single
  revert is needed to fix this particular bug.  Upstream thread:
   https://lkml.org/lkml/2017/2/20/66

  == Fix ==
  commit c962cff17dfa11f4a8227ac16de2b28aea3312e4
  Author: Dou Liyang 
  Date:   Fri Mar 3 16:02:23 2017 +0800

  Revert "x86/acpi: Set persistent cpuid <-> nodeid mapping when
  booting"

  == Regression Potential ==
  This is reverting a commit that introduced a bug.  This commit has also
  been reverted upstream.

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




  Setup:
  Dell PowerEdge R940 having 2 socket populated with 28 cores.

  Impact:
  This is a boot and installation failure for R940 users having 2 socket x 28 
cores.
  Requesting an SRU for the fix.

  Steps:
  1. Setup a Dell PowerEdge R940 with 28 cores CPUs on 2 sockets.
  2. Start installation of Ubuntu-16.04.3 with HWE kernel.
  3. Observe the screen remains blank. Console logs indicate kernel crash.

  Additional Info:
  * Seen only with 4.10 HWE kernels of Ubuntu-16.04.3.
    4.4 kernels of Ubuntu-16.04.3 works fine. Daily builds of Ubuntu Server 
17.10 works fine.

  * Reducing the core count to <26 cores helps here. Boot & installation
  of HWE-kernel works fine.

  * Attaching the console log and acpidump from the setup.

  * Patch causing this failure: 
https://github.com/torvalds/linux/commit/dc6db24d2476cd09c0ecf2b8d80313539f737a89
  x86/acpi: Set persistent cpuid <-> nodeid mapping when booting

  * Fix patch series: https://lkml.org/lkml/2017/2/20/66

  Revert "x86/acpi: Set persistent cpuid <-> nodeid mapping when booting"
  
https://github.com/torvalds/linux/commit/c962cff17dfa11f4a8227ac16de2b28aea3312e4#diff-6bd7ef719bca1a2a56b9ebf4bd0bd88d

  Revert"x86/acpi: Enable MADT APIs to 

[Kernel-packages] [Bug 1729256] Re: Invalid btree pointer causes the kernel NULL pointer dereference

2017-12-07 Thread Launchpad Bug Tracker
This bug was fixed in the package linux - 4.4.0-103.126

---
linux (4.4.0-103.126) xenial; urgency=low

  * linux: 4.4.0-103.126 -proposed tracker (LP: #1736181)

  * CVE-2017-1000405
- mm, thp: Do not make page table dirty unconditionally in touch_p[mu]d()

  * CVE-2017-16939
- netlink: add a start callback for starting a netlink dump
- ipsec: Fix aborted xfrm policy dump crash

linux (4.4.0-102.125) xenial; urgency=low

  * linux: 4.4.0-102.125 -proposed tracker (LP: #1733541)

  * tar -x sometimes fails on overlayfs (LP: #1728489)
- ovl: check if all layers are on the same fs
- ovl: persistent inode number for directories

  * NVMe timeout is too short (LP: #1729119)
- nvme: update timeout module parameter type

  * Set PANIC_TIMEOUT=10 on Power Systems (LP: #1730660)
- [Config]: Set PANIC_TIMEOUT=10 on ppc64el

  * Cannot pair BLE remote devices when using combo BT SoC (LP: #1731467)
- Bluetooth: increase timeout for le auto connections

  * CIFS errors on 4.4.0-98, but not on 4.4.0-97 with same config (LP: #1729337)
- SMB3: Validate negotiate request must always be signed

  * Plantronics P610 does not support sample rate reading (LP: #1719853)
- ALSA: usb-audio: Add sample rate quirk for Plantronics P610

  * Invalid btree pointer causes the kernel NULL pointer dereference
(LP: #1729256)
- xfs: reinit btree pointer on attr tree inactivation walk

  * Samba mount/umount in docker container triggers kernel Oops (LP: #1729637)
- ipv6: only call ip6_route_dev_notify() once for NETDEV_UNREGISTER
- ipv6: fix NULL dereference in ip6_route_dev_notify()

  * [kernel] tty/hvc: Use opal irqchip interface if available (LP: #1728098)
- tty/hvc: Use opal irqchip interface if available

  * Device hotplugging with MPT SAS cannot work for VMWare ESXi (LP: #1730852)
- scsi: mptsas: Fixup device hotplug for VMWare ESXi

  * NMI watchdog: BUG: soft lockup on Guest upon boot (KVM) (LP: #1727331)
- KVM: PPC: Book3S: Treat VTB as a per-subcore register, not per-thread

  * Attempt to map rbd image from ceph jewel/luminous hangs (LP: #1728739)
- crush: ensure bucket id is valid before indexing buckets array
- crush: ensure take bucket value is valid
- crush: add chooseleaf_stable tunable
- crush: decode and initialize chooseleaf_stable
- libceph: advertise support for TUNABLES5
- libceph: MOSDOpReply v7 encoding

  * Xenial update to 4.4.98 stable release (LP: #1732698)
- adv7604: Initialize drive strength to default when using DT
- video: fbdev: pmag-ba-fb: Remove bad `__init' annotation
- PCI: mvebu: Handle changes to the bridge windows while enabled
- xen/netback: set default upper limit of tx/rx queues to 8
- drm: drm_minor_register(): Clean up debugfs on failure
- KVM: PPC: Book 3S: XICS: correct the real mode ICP rejecting counter
- iommu/arm-smmu-v3: Clear prior settings when updating STEs
- powerpc/corenet: explicitly disable the SDHC controller on kmcoge4
- ARM: omap2plus_defconfig: Fix probe errors on UARTs 5 and 6
- crypto: vmx - disable preemption to enable vsx in aes_ctr.c
- iio: trigger: free trigger resource correctly
- phy: increase size of MII_BUS_ID_SIZE and bus_id
- serial: sh-sci: Fix register offsets for the IRDA serial port
- usb: hcd: initialize hcd->flags to 0 when rm hcd
- netfilter: nft_meta: deal with PACKET_LOOPBACK in netdev family
- IPsec: do not ignore crypto err in ah4 input
- Input: mpr121 - handle multiple bits change of status register
- Input: mpr121 - set missing event capability
- IB/ipoib: Change list_del to list_del_init in the tx object
- s390/qeth: issue STARTLAN as first IPA command
- (config) Add NET_DSA=n
- net: dsa: select NET_SWITCHDEV
- platform/x86: hp-wmi: Fix detection for dock and tablet mode
- cdc_ncm: Set NTB format again after altsetting switch for Huawei devices
- KEYS: trusted: sanitize all key material
- KEYS: trusted: fix writing past end of buffer in trusted_read()
- platform/x86: hp-wmi: Fix error value for hp_wmi_tablet_state
- platform/x86: hp-wmi: Do not shadow error values
- x86/uaccess, sched/preempt: Verify access_ok() context
- workqueue: Fix NULL pointer dereference
- crypto: x86/sha1-mb - fix panic due to unaligned access
- KEYS: fix NULL pointer dereference during ASN.1 parsing [ver #2]
- ARM: 8720/1: ensure dump_instr() checks addr_limit
- ALSA: seq: Fix OSS sysex delivery in OSS emulation
- ALSA: seq: Avoid invalid lockdep class warning
- MIPS: microMIPS: Fix incorrect mask in insn_table_MM
- MIPS: Fix CM region target definitions
- MIPS: SMP: Use a completion event to signal CPU up
- MIPS: Fix race on setting and getting cpu_online_mask
- MIPS: SMP: Fix deadlock & online race
- test: firmware_class: report errors properly on failure
- selftests: firmware: add empty string and async 

[Kernel-packages] [Bug 1729256] Re: Invalid btree pointer causes the kernel NULL pointer dereference

2017-12-07 Thread Launchpad Bug Tracker
This bug was fixed in the package linux - 4.10.0-42.46

---
linux (4.10.0-42.46) zesty; urgency=low

  * linux: 4.10.0-42.46 -proposed tracker (LP: #1736152)

  * CVE-2017-1000405
- mm, thp: Do not make page table dirty unconditionally in touch_p[mu]d()

  * CVE-2017-16939
- ipsec: Fix aborted xfrm policy dump crash

linux (4.10.0-41.45) zesty; urgency=low

  * linux: 4.10.0-41.45 -proposed tracker (LP: #1733524)

  * tar -x sometimes fails on overlayfs (LP: #1728489)
- ovl: check if all layers are on the same fs
- ovl: persistent inode number for directories

  * CVE-2017-12146
- driver core: platform: fix race condition with driver_override

  * NVMe timeout is too short (LP: #1729119)
- nvme: update timeout module parameter type

  * Set PANIC_TIMEOUT=10 on Power Systems (LP: #1730660)
- [Config]: Set PANIC_TIMEOUT=10 on ppc64el

  * Cannot pair BLE remote devices when using combo BT SoC (LP: #1731467)
- Bluetooth: increase timeout for le auto connections

  * Plantronics P610 does not support sample rate reading (LP: #1719853)
- ALSA: usb-audio: Add sample rate quirk for Plantronics P610

  * Invalid btree pointer causes the kernel NULL pointer dereference
(LP: #1729256)
- xfs: reinit btree pointer on attr tree inactivation walk

  * Samba mount/umount in docker container triggers kernel Oops (LP: #1729637)
- ipv6: only call ip6_route_dev_notify() once for NETDEV_UNREGISTER
- ipv6: fix NULL dereference in ip6_route_dev_notify()

  * Device hotplugging with MPT SAS cannot work for VMWare ESXi (LP: #1730852)
- scsi: mptsas: Fixup device hotplug for VMWare ESXi

  * Boot/Installation crash of Ubuntu-16.04.3 HWE kernel on R940 (LP: #1719697)
- Revert "x86/acpi: Set persistent cpuid <-> nodeid mapping when booting"

 -- Stefan Bader   Mon, 04 Dec 2017 15:04:01
+0100

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

** CVE added: https://cve.mitre.org/cgi-
bin/cvename.cgi?name=2017-1000405

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2017-12146

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2017-16939

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

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

Title:
  Invalid btree pointer causes the kernel NULL pointer dereference

Status in linux package in Ubuntu:
  Incomplete
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 Committed

Bug description:
  [Impact]
  The frequent kernel errors can be seen inside the XFS based OSD
  processes and it causes to crash and restart.

  BUG: unable to handle kernel NULL pointer dereference at 00a0
  IP: [] xfs_da3_node_read+0x30/0xb0 [xfs]
  CPU: 8 PID: 2855031 Comm: tp_fstore_op Not tainted 4.4.0-78-generic #99-Ubuntu
  Hardware name: HP ProLiant DL380 Gen9/ProLiant DL380 Gen9, BIOS P89 09/13/2016
  task: 880620f38e00 ti: 880678228000 task.ti: 880678228000
  RIP: 0010:[]  []
  xfs_da3_node_read+0x30/0xb0 [xfs]
  RSP: 0018:88067822bd00  EFLAGS: 00010286
  RAX:  RBX: 88078abff3f0 RCX: 0001
  RDX:  RSI:  RDI: 88067822bcb0
  RBP: 88067822bd20 R08: 0001 R09: fffe
  R10: ea001e2aff80 R11: 0001 R12: 88067822bd50
  R13: 8805a37f R14: 0001 R15: 8d180e3e
  FS:  7f7573c01700() GS:88103fa0()knlGS:
  CS:  0010 DS:  ES:  CR0: 80050033
  CR2: 00a0 CR3: 001686f3d000 CR4: 003406e0
  DR0:  DR1:  DR2: 
  DR3:  DR6: fffe0ff0 DR7: 0400
  Stack:
   c03cfb50 c03b0ecc 88067822bde0 0001
   88067822bd98 c038c8b3 00020008 88081cb06040
   0002d8723bf8 880fc142ae80  
  Call Trace:
   [] ? xfs_trans_roll+0x2c/0x50 [xfs]
   [] xfs_attr3_node_inactive+0x183/0x220 [xfs]
   [] xfs_attr3_root_inactive+0xac/0x100 [xfs]
   [] xfs_attr_inactive+0x14c/0x1a0 [xfs]
   [] xfs_inactive+0x85/0x120 [xfs]
   [] xfs_fs_evict_inode+0xa5/0x100 [xfs]
   [] evict+0xbe/0x190
   [] iput+0x1c1/0x240
   [] do_unlinkat+0x199/0x2d0
   [] SyS_unlink+0x16/0x20
   [] entry_SYSCALL_64_fastpath+0x16/0x71

  [Fix]
  commit e678a63e6c95f140befe6fcd81b49075ecb3c701
  Author: Brian Foster 
  Date:   Mon Oct 9 11:38:56 2017 -0700

  xfs: reinit btree pointer on attr tree inactivation walk

  xfs_attr3_root_inactive() walks the attr fork tree to invalidate the
  associated blocks. xfs_attr3_node_inactive() recursively descends from

[Kernel-packages] [Bug 1731882] Re: Xenial update to 4.4.96 stable release

2017-12-07 Thread Launchpad Bug Tracker
This bug was fixed in the package linux - 4.4.0-103.126

---
linux (4.4.0-103.126) xenial; urgency=low

  * linux: 4.4.0-103.126 -proposed tracker (LP: #1736181)

  * CVE-2017-1000405
- mm, thp: Do not make page table dirty unconditionally in touch_p[mu]d()

  * CVE-2017-16939
- netlink: add a start callback for starting a netlink dump
- ipsec: Fix aborted xfrm policy dump crash

linux (4.4.0-102.125) xenial; urgency=low

  * linux: 4.4.0-102.125 -proposed tracker (LP: #1733541)

  * tar -x sometimes fails on overlayfs (LP: #1728489)
- ovl: check if all layers are on the same fs
- ovl: persistent inode number for directories

  * NVMe timeout is too short (LP: #1729119)
- nvme: update timeout module parameter type

  * Set PANIC_TIMEOUT=10 on Power Systems (LP: #1730660)
- [Config]: Set PANIC_TIMEOUT=10 on ppc64el

  * Cannot pair BLE remote devices when using combo BT SoC (LP: #1731467)
- Bluetooth: increase timeout for le auto connections

  * CIFS errors on 4.4.0-98, but not on 4.4.0-97 with same config (LP: #1729337)
- SMB3: Validate negotiate request must always be signed

  * Plantronics P610 does not support sample rate reading (LP: #1719853)
- ALSA: usb-audio: Add sample rate quirk for Plantronics P610

  * Invalid btree pointer causes the kernel NULL pointer dereference
(LP: #1729256)
- xfs: reinit btree pointer on attr tree inactivation walk

  * Samba mount/umount in docker container triggers kernel Oops (LP: #1729637)
- ipv6: only call ip6_route_dev_notify() once for NETDEV_UNREGISTER
- ipv6: fix NULL dereference in ip6_route_dev_notify()

  * [kernel] tty/hvc: Use opal irqchip interface if available (LP: #1728098)
- tty/hvc: Use opal irqchip interface if available

  * Device hotplugging with MPT SAS cannot work for VMWare ESXi (LP: #1730852)
- scsi: mptsas: Fixup device hotplug for VMWare ESXi

  * NMI watchdog: BUG: soft lockup on Guest upon boot (KVM) (LP: #1727331)
- KVM: PPC: Book3S: Treat VTB as a per-subcore register, not per-thread

  * Attempt to map rbd image from ceph jewel/luminous hangs (LP: #1728739)
- crush: ensure bucket id is valid before indexing buckets array
- crush: ensure take bucket value is valid
- crush: add chooseleaf_stable tunable
- crush: decode and initialize chooseleaf_stable
- libceph: advertise support for TUNABLES5
- libceph: MOSDOpReply v7 encoding

  * Xenial update to 4.4.98 stable release (LP: #1732698)
- adv7604: Initialize drive strength to default when using DT
- video: fbdev: pmag-ba-fb: Remove bad `__init' annotation
- PCI: mvebu: Handle changes to the bridge windows while enabled
- xen/netback: set default upper limit of tx/rx queues to 8
- drm: drm_minor_register(): Clean up debugfs on failure
- KVM: PPC: Book 3S: XICS: correct the real mode ICP rejecting counter
- iommu/arm-smmu-v3: Clear prior settings when updating STEs
- powerpc/corenet: explicitly disable the SDHC controller on kmcoge4
- ARM: omap2plus_defconfig: Fix probe errors on UARTs 5 and 6
- crypto: vmx - disable preemption to enable vsx in aes_ctr.c
- iio: trigger: free trigger resource correctly
- phy: increase size of MII_BUS_ID_SIZE and bus_id
- serial: sh-sci: Fix register offsets for the IRDA serial port
- usb: hcd: initialize hcd->flags to 0 when rm hcd
- netfilter: nft_meta: deal with PACKET_LOOPBACK in netdev family
- IPsec: do not ignore crypto err in ah4 input
- Input: mpr121 - handle multiple bits change of status register
- Input: mpr121 - set missing event capability
- IB/ipoib: Change list_del to list_del_init in the tx object
- s390/qeth: issue STARTLAN as first IPA command
- (config) Add NET_DSA=n
- net: dsa: select NET_SWITCHDEV
- platform/x86: hp-wmi: Fix detection for dock and tablet mode
- cdc_ncm: Set NTB format again after altsetting switch for Huawei devices
- KEYS: trusted: sanitize all key material
- KEYS: trusted: fix writing past end of buffer in trusted_read()
- platform/x86: hp-wmi: Fix error value for hp_wmi_tablet_state
- platform/x86: hp-wmi: Do not shadow error values
- x86/uaccess, sched/preempt: Verify access_ok() context
- workqueue: Fix NULL pointer dereference
- crypto: x86/sha1-mb - fix panic due to unaligned access
- KEYS: fix NULL pointer dereference during ASN.1 parsing [ver #2]
- ARM: 8720/1: ensure dump_instr() checks addr_limit
- ALSA: seq: Fix OSS sysex delivery in OSS emulation
- ALSA: seq: Avoid invalid lockdep class warning
- MIPS: microMIPS: Fix incorrect mask in insn_table_MM
- MIPS: Fix CM region target definitions
- MIPS: SMP: Use a completion event to signal CPU up
- MIPS: Fix race on setting and getting cpu_online_mask
- MIPS: SMP: Fix deadlock & online race
- test: firmware_class: report errors properly on failure
- selftests: firmware: add empty string and async 

[Kernel-packages] [Bug 1710019] Re: support GICv3 ITS save/restore & migration

2017-12-07 Thread Launchpad Bug Tracker
This bug was fixed in the package linux - 4.13.0-19.22

---
linux (4.13.0-19.22) artful; urgency=low

  * linux: 4.13.0-19.22 -proposed tracker (LP: #1736118)

  * CVE-2017-1000405
- mm, thp: Do not make page table dirty unconditionally in touch_p[mu]d()

linux (4.13.0-18.21) artful; urgency=low

  * linux: 4.13.0-18.21 -proposed tracker (LP: #1733530)

  * NVMe timeout is too short (LP: #1729119)
- nvme: update timeout module parameter type

  * CPU call trace on AMD Raven Ridge after S3 (LP: #1732894)
- x86/mce/AMD: Allow any CPU to initialize the smca_banks array

  * Set PANIC_TIMEOUT=10 on Power Systems (LP: #1730660)
- [Config]: Set PANIC_TIMEOUT=10 on ppc64el

  * Cannot pair BLE remote devices when using combo BT SoC (LP: #1731467)
- Bluetooth: increase timeout for le auto connections

  * enable CONFIG_SND_SOC_INTEL_BYT_CHT_NOCODEC_MACH easily confuse users
(LP: #1732627)
- [Config] CONFIG_SND_SOC_INTEL_BYT_CHT_NOCODEC_MACH=n

  * Plantronics P610 does not support sample rate reading (LP: #1719853)
- ALSA: usb-audio: Add sample rate quirk for Plantronics P610

  * Allow drivers to use Relaxed Ordering on capable root ports (LP: #1721365)
- Revert commit 1a8b6d76dc5b ("net:add one common config...")
- net: ixgbe: Use new PCI_DEV_FLAGS_NO_RELAXED_ORDERING flag

  * support GICv3 ITS save/restore & migration (LP: #1710019)
- KVM: arm/arm64: vgic-its: Fix return value for device table restore

  * Device hotplugging with MPT SAS cannot work for VMWare ESXi (LP: #1730852)
- scsi: mptsas: Fixup device hotplug for VMWare ESXi

  * Artful update to 4.13.13 stable release (LP: #1732726)
- netfilter: nat: Revert "netfilter: nat: convert nat bysrc hash to
  rhashtable"
- netfilter: nft_set_hash: disable fast_ops for 2-len keys
- workqueue: Fix NULL pointer dereference
- crypto: ccm - preserve the IV buffer
- crypto: x86/sha1-mb - fix panic due to unaligned access
- crypto: x86/sha256-mb - fix panic due to unaligned access
- KEYS: fix NULL pointer dereference during ASN.1 parsing [ver #2]
- ACPI / PM: Blacklist Low Power S0 Idle _DSM for Dell XPS13 9360
- ARM: 8720/1: ensure dump_instr() checks addr_limit
- ALSA: timer: Limit max instances per timer
- ALSA: usb-audio: support new Amanero Combo384 firmware version
- ALSA: hda - fix headset mic problem for Dell machines with alc274
- ALSA: seq: Fix OSS sysex delivery in OSS emulation
- ALSA: seq: Avoid invalid lockdep class warning
- MIPS: Fix CM region target definitions
- MIPS: BMIPS: Fix missing cbr address
- MIPS: AR7: Defer registration of GPIO
- MIPS: AR7: Ensure that serial ports are properly set up
- KVM: PPC: Book3S HV: Fix exclusion between HPT resizing and other HPT
  updates
- Input: elan_i2c - add ELAN060C to the ACPI table
- rbd: use GFP_NOIO for parent stat and data requests
- drm/vmwgfx: Fix Ubuntu 17.10 Wayland black screen issue
- Revert "x86: CPU: Fix up "cpu MHz" in /proc/cpuinfo"
- can: sun4i: handle overrun in RX FIFO
- can: peak: Add support for new PCIe/M2 CAN FD interfaces
- can: ifi: Fix transmitter delay calculation
- can: c_can: don't indicate triple sampling support for D_CAN
- x86/debug: Handle warnings before the notifier chain, to fix KGDB crash
- x86/smpboot: Make optimization of delay calibration work correctly
- x86/oprofile/ppro: Do not use __this_cpu*() in preemptible context
- Linux 4.13.13

  * ELANTECH Touchpad is not detected in 'Lenovo Ideapad 320 14AST' after fresh
install (LP: #1727544)
- Input: elan_i2c - add ELAN060C to the ACPI table

  * Power8 Nest PMU Instrumentation support (LP: #1481347)
- powerpc/powernv: Add IMC OPAL APIs
- powerpc/powernv: Detect and create IMC device
- powerpc/perf: Add nest IMC PMU support
- powerpc/perf: Add core IMC PMU support
- powerpc/perf: Add thread IMC PMU support
- powerpc/perf: Fix double unlock in imc_common_cpuhp_mem_free()
- powerpc/perf/imc: Fix nest events on muti socket system
- powerpc/powernv: Fix build error in opal-imc.c when NUMA=n
- powerpc/perf: Fix usage of nest_imc_refc
- powerpc/perf: Fix for core/nest imc call trace on cpuhotplug
- powerpc/perf: Add ___GFP_NOWARN flag to alloc_pages_node()
- powerpc/perf: Fix IMC initialization crash

  * Artful update to 4.13.12 stable release (LP: #1731971)
- ALSA: timer: Add missing mutex lock for compat ioctls
- ALSA: seq: Fix nested rwsem annotation for lockdep splat
- cifs: check MaxPathNameComponentLength != 0 before using it
- KEYS: return full count in keyring_read() if buffer is too small
- KEYS: trusted: fix writing past end of buffer in trusted_read()
- KEYS: fix out-of-bounds read during ASN.1 parsing
- ASoC: adau17x1: Workaround for noise bug in ADC
- virtio_blk: Fix an SG_IO regression
- arm64: ensure __dump_instr() checks addr_limit
 

[Kernel-packages] [Bug 1729119] Re: NVMe timeout is too short

2017-12-07 Thread Launchpad Bug Tracker
This bug was fixed in the package linux - 4.10.0-42.46

---
linux (4.10.0-42.46) zesty; urgency=low

  * linux: 4.10.0-42.46 -proposed tracker (LP: #1736152)

  * CVE-2017-1000405
- mm, thp: Do not make page table dirty unconditionally in touch_p[mu]d()

  * CVE-2017-16939
- ipsec: Fix aborted xfrm policy dump crash

linux (4.10.0-41.45) zesty; urgency=low

  * linux: 4.10.0-41.45 -proposed tracker (LP: #1733524)

  * tar -x sometimes fails on overlayfs (LP: #1728489)
- ovl: check if all layers are on the same fs
- ovl: persistent inode number for directories

  * CVE-2017-12146
- driver core: platform: fix race condition with driver_override

  * NVMe timeout is too short (LP: #1729119)
- nvme: update timeout module parameter type

  * Set PANIC_TIMEOUT=10 on Power Systems (LP: #1730660)
- [Config]: Set PANIC_TIMEOUT=10 on ppc64el

  * Cannot pair BLE remote devices when using combo BT SoC (LP: #1731467)
- Bluetooth: increase timeout for le auto connections

  * Plantronics P610 does not support sample rate reading (LP: #1719853)
- ALSA: usb-audio: Add sample rate quirk for Plantronics P610

  * Invalid btree pointer causes the kernel NULL pointer dereference
(LP: #1729256)
- xfs: reinit btree pointer on attr tree inactivation walk

  * Samba mount/umount in docker container triggers kernel Oops (LP: #1729637)
- ipv6: only call ip6_route_dev_notify() once for NETDEV_UNREGISTER
- ipv6: fix NULL dereference in ip6_route_dev_notify()

  * Device hotplugging with MPT SAS cannot work for VMWare ESXi (LP: #1730852)
- scsi: mptsas: Fixup device hotplug for VMWare ESXi

  * Boot/Installation crash of Ubuntu-16.04.3 HWE kernel on R940 (LP: #1719697)
- Revert "x86/acpi: Set persistent cpuid <-> nodeid mapping when booting"

 -- Stefan Bader   Mon, 04 Dec 2017 15:04:01
+0100

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

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

Title:
  NVMe timeout is too short

Status in linux package in Ubuntu:
  Confirmed
Status in linux-aws package in Ubuntu:
  Fix Released
Status in linux source package in Trusty:
  Fix Released
Status in linux-aws source package in Trusty:
  New
Status in linux source package in Xenial:
  Fix Released
Status in linux-aws source package in Xenial:
  Fix Released
Status in linux source package in Zesty:
  Fix Released
Status in linux-aws source package in Zesty:
  Invalid
Status in linux source package in Artful:
  Fix Released
Status in linux-aws source package in Artful:
  Invalid

Bug description:
  [SRU Justification]

  [Impact]
  Some NVMe operations time out too quickly. The module parameters allow the 
timeouts to be extended, but only up to 255s, as the counters are bytes.

  [Fix]
  The underlying parameters are unsigned ints, so make the module parameters 
unsigned ints too, by picking patch 
http://lists.infradead.org/pipermail/linux-nvme/2017-September/012701.html

  (Trusty specific) This also requires picking the patch that converts
  the constant into a parameter, which is a clean cherry-pick.

  [Regression Potential]
  (X/Z/A) Very limited: only types of module parameters are changing, the patch 
is easily reviewable.

  (Trusty specific) Limited: a module parameter is added and its type is
  changed. The patches are easily reviewable.

  [Testing]
  (Trusty only) Boot tested on a c5.large instance on AWS which uses
  NVMe to boot. Verified that the system still boots with the patches,
  and that a timeout of 123456s is permitted.

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

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


  1   2   >