date:20170901

@Piotr,
File a new bug, thanks!

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => Kai-Heng Feng (kaihengfeng)

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

Title:
  Kernel has troule recognizing Corsair Strafe RGB keyboard

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I recently bought a Corsair Strafe RGB keyboard, and while it works
  well when successfully recognized by Ubuntu at boot, that doesn't
  always happen.

  I see messages like this when booting my desktop up:

  [6.619510] usb 3-10: unable to read config index 0 descriptor/all
  [6.619543] usb 3-10: can't read configurations, error -110

  They sometimes repeat at 5-second intervals, culminating on a "can't
  set config #1" message or even "unable to enumerate USB device". This
  happens on the logic that deals with a new USB device being connected,
  so when it doesn't work it never gets to the HID drivers part of the
  code. When it does, hid-generic is quite able to control the keyboard,
  though this message appears on dmesg:

  [6.883811] usbhid 3-10:1.2: couldn't find an input interrupt
  endpoint

  
  From what I have been able to determine, the Corsair Strafe RGB has three 
inputs, with the last one being used as input/output and having something to do 
with the LEDs. It only has a single USB configuration, though I don't know why 
it times out.

  Searching on Google has a lot of people recommending this userspace
  drive to me: https://github.com/mattanger/ckb-next , and I've tried
  it, but it seems to be more about programming lighting effects into
  the keyboard than in controlling its basic operation, which is all I'm
  interested in. Its daemon was supposed to handle that part too, but it
  didn't fix those connection errors on boot.

  I have the following boot parameter set in my kernel, following advice
  from ckb-next's README, but it doesn't see to have an appreciable
  effect on my success rate:

  usbhid.quirks=0x1B1C:0x1B20:0x2448

  ckb-next recommended 0x2408, but I added the HID_QUIRK_MULTI_INPUT
  as well in an attempt to improve things, without success.

  GRUB is always able to correctly identify the keyboard and get it to
  work, too, which makes the fact that the full kernel can't always do
  it a little more frustrating.

  I would be happy to provide any extra information you require on this
  issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: linux-image-4.8.0-45-generic 4.8.0-45.48
  ProcVersionSignature: Ubuntu 4.8.0-45.48-generic 4.8.17
  Uname: Linux 4.8.0-45-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  bira   2322 F pulseaudio
   /dev/snd/controlC0:  bira   2322 F pulseaudio
  CurrentDesktop: i3
  Date: Sat Apr  1 10:23:52 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-02-24 (767 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  IwConfig:
   eth0  no wireless extensions.
   
   lono wireless extensions.
  MachineType: Gigabyte Technology Co., Ltd. Z97M-D3H
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-45-generic 
root=UUID=d1db423d-2a50-49ac-b4e7-fd50d73afaff ro quiet splash 
usbhid.quirks=0x1B1C:0x1B20:0x2448
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-45-generic N/A
   linux-backports-modules-4.8.0-45-generic  N/A
   linux-firmware1.161.1
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/30/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F5
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z97M-D3H
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF5:bd05/30/2014:svnGigabyteTechnologyCo.,Ltd.:pnZ97M-D3H:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ97M-D3H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: Z97M-D3H
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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

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

** Description changed:

+ SRU Justifications:
+ 
+ [Impact] 
+ Touchpad on Lenovo ideapad 320-14IKB does not work.
+ 
+ [Test Case]
+ After adding the ID to the elan_i2c driver, the touchpad works.
+ 
+ 
+ [Regression Potential]
+ Very low.
+ It only adds device ID to the driver, no functional changes.
+ 
+ ---
+ 
  The touchpad is not working in any linux distribution, but works in
  Windows. It is not getting detected. Seems like a kernel bug.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-30-generic 4.10.0-30.34
  ProcVersionSignature: Ubuntu 4.10.0-30.34-generic 4.10.17
  Uname: Linux 4.10.0-30-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  AudioDevicesInUse:
-  USERPID ACCESS COMMAND
-  /dev/snd/controlC0:  matheus1504 F pulseaudio
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC0:  matheus1504 F pulseaudio
  CurrentDesktop: GNOME
  Date: Sat Aug  5 12:58:21 2017
  InstallationDate: Installed on 2017-08-05 (0 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
  Lsusb:
-  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
-  Bus 001 Device 004: ID 5986:1127 Acer, Inc 
-  Bus 001 Device 003: ID 0cf3:e500 Atheros Communications, Inc. 
-  Bus 001 Device 002: ID 0101:0007  
-  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
+  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
+  Bus 001 Device 004: ID 5986:1127 Acer, Inc
+  Bus 001 Device 003: ID 0cf3:e500 Atheros Communications, Inc.
+  Bus 001 Device 002: ID 0101:0007
+  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 80YF
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-30-generic.efi.signed 
root=UUID=d7c89f65-c9a7-4e7f-9bce-ed58751f0619 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
-  linux-restricted-modules-4.10.0-30-generic N/A
-  linux-backports-modules-4.10.0-30-generic  N/A
-  linux-firmware 1.164.1
+  linux-restricted-modules-4.10.0-30-generic N/A
+  linux-backports-modules-4.10.0-30-generic  N/A
+  linux-firmware 1.164.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/22/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 4WCN16WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: Cairo 4A
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40679 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad 320-14IKB
  dmi.modalias: 
dmi:bvnLENOVO:bvr4WCN16WW:bd02/22/2017:svnLENOVO:pn80YF:pvrLenovoideapad320-14IKB:rvnLENOVO:rnCairo4A:rvrSDK0J40679WIN:cvnLENOVO:ct10:cvrLenovoideapad320-14IKB:
  dmi.product.name: 80YF
  dmi.product.version: Lenovo ideapad 320-14IKB
  dmi.sys.vendor: LENOVO

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

Title:
  Touchpad not detected

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  SRU Justifications:

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

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

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

  ---

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

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

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

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

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

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

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

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

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

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

[Kernel-packages] [Bug 1686019] Re: Ubuntu 16.04.3: Qemu fails on P9

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
zesty' to 'verification-done-zesty'. If the problem still exists, change
the tag 'verification-needed-zesty' to 'verification-failed-zesty'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-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/1686019

Title:
  Ubuntu 16.04.3: Qemu fails on P9

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

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

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

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

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

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

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

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

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

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

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
trusty' to 'verification-done-trusty'. If the problem still exists,
change the tag 'verification-needed-trusty' to 'verification-failed-
trusty'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!

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

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

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

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

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

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

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

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

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
xenial' to 'verification-done-xenial'. If the problem still exists,
change the tag 'verification-needed-xenial' to 'verification-failed-
xenial'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-trusty

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

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

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

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

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

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

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

[Kernel-packages] [Bug 1711098] Re: AMD RV platforms with SNPS 3.1 USB controller stop responding (S3 issue)

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
zesty' to 'verification-done-zesty'. If the problem still exists, change
the tag 'verification-needed-zesty' to 'verification-failed-zesty'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-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/1711098

Title:
  AMD RV platforms with SNPS 3.1 USB controller stop responding (S3
  issue)

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

Bug description:
  SRU Request:

  [Impact]
  AMD RV platforms with SNPS 3.1 USB controllers will stop responding because 
of an RTL bug.

  This workaround fixes S3 on RV platform with a USB keyboard

  [Test Case]
  1) Install the new kernel

  2) Run pm-suspend

  3) Press any key to wake up the system

  [Regression Potential]
  Low, the patch is very small, and it is already available upstream.

  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/usb/host
  /xhci-hub.c?h=v4.13-rc2&id=28a2369f7d72ece55089f33e7d7b9c1223673cc3

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

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

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

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
zesty' to 'verification-done-zesty'. If the problem still exists, change
the tag 'verification-needed-zesty' to 'verification-failed-zesty'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-zesty

** Tags added: verification-needed-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/1712345

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

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

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

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

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

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

[Kernel-packages] [Bug 1711182] Re: ACPI ID for Hip07/08 I2C controller has typo

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
zesty' to 'verification-done-zesty'. If the problem still exists, change
the tag 'verification-needed-zesty' to 'verification-failed-zesty'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-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/1711182

Title:
  ACPI ID for Hip07/08 I2C controller has typo

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

Bug description:
  [Impact]
  Due to a typo in the upstream fix for LP: #1708293, the i2c driver still does 
not recognize the ACPI IDs for the i2c devices on the Hip07/08 platforms, 
making these devices unusable.

  [Test Case]
ls -l /sys/class/i2c-dev/*/device/firmware_node | grep HISI

  [Regression Risk]
  This adds an ID/config for previously unsupported ACPI IDs.

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

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

[Kernel-packages] [Bug 1710868] Re: memory-hotplug test needs to be fixed

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
xenial' to 'verification-done-xenial'. If the problem still exists,
change the tag 'verification-needed-xenial' to 'verification-failed-
xenial'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!

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

Title:
  memory-hotplug test needs to be fixed

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

Bug description:
  SRU Justification:

  Impact: 
  The memory-hotplug test in the kernel tree 
(tools/testing/selftests/memory-hotplug/) needs to be fixed:
  1. The test will pass even the memory blocks are failed to be offlined [1].
  2. It's using a random number generator to decide if each memory block needs 
to be offlined, which is not ideal for testing as the block it tries to unplug 
might be different between two runs.
  3. The "-r" flag, percent-of-memory-to-offline, does not match what is says. 
It's being used as the percentage to get a memory block offlined instead.

  Fix: 
  Apply the following patch from upstream can fix these issues:
  593f9278 - selftests: typo correction for memory-hotplug test
  a34b28c9 - selftests: check hot-pluggagble memory for memory-hotplug test
  72441ea5 - selftests: check percentage range for memory-hotplug test
  02d8f075 - selftests: add missing test name in memory-hotplug test
  5ff0c60b - selftests: fix memory-hotplug test

  Testcase:
  Run the script directly, it will fail when all memory blocks are busy. And it 
will try to unplug memory blocks in a fixed order.

  Regression Potential:
  Negligible, it's just affecting this specific test case among those testing 
tools.

  [1] https://paste.ubuntu.com/25318445/

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

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

[Kernel-packages] [Bug 1711096] Re: dma-buf: performance issue when looking up the fence status

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
zesty' to 'verification-done-zesty'. If the problem still exists, change
the tag 'verification-needed-zesty' to 'verification-failed-zesty'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!

** Tags added: verification-needed-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/1711096

Title:
dma-buf: performance issue when looking up the fence status

Status in linux package in Ubuntu:
Triaged
Status in linux source package in Zesty:
Fix Committed

Bug description:
SRU Request:

[Impact]
When a timeout of zero is specified, the caller is only interested in
the fence status.

In the current implementation, dma_fence_default_wait will always call
schedule_timeout() at least once for an unsignaled fence. This adds a
significant overhead to a fence status query.

Avoid this overhead by returning early if a zero timeout is specified.

[Test Case]
1) Install the new kernel

2) Download amdgpu-pro-17.30-465504.tar.xz from http://support.amd.com
/en-us/kb-articles/Pages/AMDGPU-PRO-Driver-for-Linux-Release-
Notes.aspx, and follow the install guide to install the driver on
Ubuntu 16.04.3

3) Install Unigine Heaven to get performance score

4) Rmeove DKMS, remove this patch

http://git.amd.com:8080/gitweb?p=brahma/ec/linux.git;a=commit;h=8586edda6677b90f3971919f3c6babbbec4b5b8c
from DKMS source code, and install DKMS

5) re-run the benchmark, and check if there's any obvious performance
drop.

[Regression Potential]
Low, the patch is very small, and it is already available upstream.

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

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

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

[Kernel-packages] [Bug 1712024] Re: igb: Support using Broadcom 54616 as PHY

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
xenial' to 'verification-done-xenial'. If the problem still exists,
change the tag 'verification-needed-xenial' to 'verification-failed-
xenial'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!

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

Title:
  igb: Support using Broadcom 54616 as PHY

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

Bug description:
  The igb driver fails to work when using Broadcom 54616 as PHY.

  00:14.0 Ethernet controller: Intel Corporation Ethernet Connection I354 (rev 
03)
  00:14.1 Ethernet controller: Intel Corporation Ethernet Connection I354 (rev 
03)
  00:14.2 Ethernet controller: Intel Corporation Ethernet Connection I354 (rev 
03)

  $ dmesg | grep igb
  [3.472655] igb: Intel(R) Gigabit Ethernet Network Driver - version 5.3.0-k
  [3.480475] igb: Copyright (c) 2007-2014 Intel Corporation.
  [3.584768] igb: probe of :00:14.0 failed with error -2
  [3.965971] igb :00:14.1: added PHC on eth0
  [3.971066] igb :00:14.1: Intel(R) Gigabit Ethernet Network Connection
  [4.010706] igb :00:14.1: eth0: PBA No: 002000-000
  [4.016458] igb :00:14.1: Using MSI-X interrupts. 4 rx queue(s), 4 tx 
queue(s)
  [4.399662] igb :00:14.2: added PHC on eth1
  [4.404738] igb :00:14.2: Intel(R) Gigabit Ethernet Network Connection
  [4.412489] igb :00:14.2: eth1: PBA No: 002000-000
  [4.418235] igb :00:14.2: Using MSI-X interrupts. 4 rx queue(s), 4 tx 
queue(s)
  [4.428206] igb :00:14.1 enp0s20f1: renamed from eth0
  [4.465744] igb :00:14.2 enp0s20f2: renamed from eth1

  A patch can be found in OpenNetworkLinux:
  
https://github.com/opencomputeproject/OpenNetworkLinux/blob/master/packages/base/any/kernels/3.18.25/patches
  /driver-support-intel-igb-bcm54616-phy.patch

  It should be safe to include this in an SRU release since the new code
  is only functioning when certain ID is found.

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

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

[Kernel-packages] [Bug 1711401] Re: accessing /dev/hvc1 with stress-ng on Ubuntu xenial causes crash

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
xenial' to 'verification-done-xenial'. If the problem still exists,
change the tag 'verification-needed-xenial' to 'verification-failed-
xenial'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-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/1711401

Title:
  accessing /dev/hvc1 with stress-ng on Ubuntu xenial causes crash

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

Bug description:
  [SRU REQUEST][XENIAL]

  When running stress-ng --dev stressor accessing /dev/hvc1 causes the
  stressor to lock up and never terminal.

  [FIX]
  Upstream commmit:From bbc3dfe8805de86874b1a1b1429a002e8670043e Mon Sep 17 
00:00:00 2001
  From: Sam Mendoza-Jonas 
  Date: Mon, 11 Jul 2016 13:38:57 +1000
  Subject: [PATCH] tty/hvc: Use IRQF_SHARED for OPAL hvc consoles

  [TESTING]
  Without the fix, stress-ng --dev run as root hangs, and one gets an irq 
failed error and an oops:

  [ 2096.476610] hvc_open: request_irq failed with rc -16.
  [ 2096.476634] Unable to handle kernel paging request for data at address 
0x00a8
  [ 2096.476641] Faulting instruction address: 0xc0b0d8a4
  [ 2096.476647] Oops: Kernel access of bad area, sig: 11 [#1]
  [ 2096.476650] SMP NR_CPUS=2048 NUMA PowerNV

  With the fix, the stressor runs w/o any issues

  [REGRESSION POTENTIAL]
  This is specific to one driver for ppc64el, so the risk potential is limited. 
The fix has limited regression potential as it essentially marks a flag to 
allow interrupt to be shared and fundamentally this is a very minor change to  
the interrupt handling functionality in the driver.

  ---

  stress-ng run as root, --dev stressor, accessing /dev/hvc1:

  [ 2096.476610] hvc_open: request_irq failed with rc -16.
  [ 2096.476634] Unable to handle kernel paging request for data at address 
0x00a8
  [ 2096.476641] Faulting instruction address: 0xc0b0d8a4
  [ 2096.476647] Oops: Kernel access of bad area, sig: 11 [#1]
  [ 2096.476650] SMP NR_CPUS=2048 NUMA PowerNV
  [ 2096.476657] Modules linked in: kvm_hv kvm_pr kvm cuse userio hci_vhci 
bluetooth uhid hid vhost_net vhost macvtap macvlan snd_seq snd_seq_device 
snd_timer snd soundcore ipmi_powernv ipmi_msghandler vmx_crypto leds_powernv 
uio_pdrv_genirq uio powernv_rng ibmpowernv 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 dm_round_robin ses 
enclosure ipr scsi_dh_emc scsi_dh_rdac scsi_dh_alua dm_multipath
  [ 2096.476718] CPU: 74 PID: 23074 Comm: stress-ng-dev Not tainted 
4.4.0-92-generic #115-Ubuntu
  [ 2096.476724] task: c00fe8499030 ti: c00f0fa0c000 task.ti: 
c00f0fa0c000
  [ 2096.476728] NIP: c0b0d8a4 LR: c069648c CTR: 
c0696450
  [ 2096.476732] REGS: c00f0fa0f6b0 TRAP: 0300   Not tainted  
(4.4.0-92-generic)
  [ 2096.476736] MSR: 90009033   CR: 2248  
XER: 
  [ 2096.476749] CFAR: c0008468 DAR: 00a8 DSISR: 4000 
SOFTE: 0
     GPR00: c069648c c00f0fa0f930 c15f8000 
00a8
     GPR04: c00ff0082400 0002 001ffe7d 
0036
     GPR08: c3236b90  804a 
c01e4e568880
     GPR12: c0696450 cfb6bf00 000f 
010023d22660
     GPR16: 3fff9ca5 0080 c01e43dde100 
c00fe459c800
     GPR20:  0001 0e51 
00010004
     GPR24: 00010800  f000 
c1892448
     GPR28: c00fef98da28 c00fe459c800 0001 
00a8
  [ 2096.476805] NIP [c0b0d8a4] _raw_spin_lock_irqsave+0x44/0x130
  [ 2096.476812] LR [c069648c] hvc_open+0x3c/0x1a0
  [ 2096.476815] Call Trace:
  [ 2096.476818] [c00f0fa0f930] [c00f0fa0f970] 0xc00f0fa0f970 
(unreliable)
  [ 2096.476824] [c00f0fa0f970] [c069648c] hvc_open+0x3c/0x1a0
  [ 2096.476829] [c00f0fa0f9f0] [c066c514] tty_open+0x194/0x7c0
  [ 2096.476836] [c00f0fa0fa90] [c02ec234] chrdev_open+0x114/0x270
  [ 2096.476841] [c00f0fa0faf0] [c00

[Kernel-packages] [Bug 1712481] Re: HID: multitouch: Support ALPS PTP Stick and Touchpad devices

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
xenial' to 'verification-done-xenial'. If the problem still exists,
change the tag 'verification-needed-xenial' to 'verification-failed-
xenial'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!

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

Title:
  HID: multitouch: Support ALPS PTP Stick and Touchpad devices

Status in HWE Next:
  In Progress
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Xenial:
  Fix Committed
Status in linux source package in Zesty:
  Fix Committed

Bug description:
  [Impact]
  Support to ALPS PTP Stick and Touchpad devices found on latest Dell Latitude 
systems.

  [Fix]
  This fix in two parts:
  1. Requires cherry-pick of patch submitted by ALPS in upstream kernel 4.13
  See: 
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?h=v4.13-rc6&id=504c932c7c47a6b4c572302a13873f7d83af1ff3

  2. Additional sauce patch adds the device-id of the new PTP stick. This
  patch is already submitted to linux-input and is pending review.
  See: http://marc.info/?l=linux-input&m=150235885218076&w=2

  [Test Case]
  Verified on the systems affected with this issue and confirmed that this 
solution works.

  [Regression Potential]
  The patch adds new device ids to hid multi-touch driver. With strict 
conditional filtering based on these device-ids, regression potential is 
minimal.

  This bug is used for tracking purposes, please do not triage.

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

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

[Kernel-packages] [Bug 1712024] Re: igb: Support using Broadcom 54616 as PHY

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
zesty' to 'verification-done-zesty'. If the problem still exists, change
the tag 'verification-needed-zesty' to 'verification-failed-zesty'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-zesty

** Tags added: verification-needed-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/1712024

Title:
  igb: Support using Broadcom 54616 as PHY

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

Bug description:
  The igb driver fails to work when using Broadcom 54616 as PHY.

  00:14.0 Ethernet controller: Intel Corporation Ethernet Connection I354 (rev 
03)
  00:14.1 Ethernet controller: Intel Corporation Ethernet Connection I354 (rev 
03)
  00:14.2 Ethernet controller: Intel Corporation Ethernet Connection I354 (rev 
03)

  $ dmesg | grep igb
  [3.472655] igb: Intel(R) Gigabit Ethernet Network Driver - version 5.3.0-k
  [3.480475] igb: Copyright (c) 2007-2014 Intel Corporation.
  [3.584768] igb: probe of :00:14.0 failed with error -2
  [3.965971] igb :00:14.1: added PHC on eth0
  [3.971066] igb :00:14.1: Intel(R) Gigabit Ethernet Network Connection
  [4.010706] igb :00:14.1: eth0: PBA No: 002000-000
  [4.016458] igb :00:14.1: Using MSI-X interrupts. 4 rx queue(s), 4 tx 
queue(s)
  [4.399662] igb :00:14.2: added PHC on eth1
  [4.404738] igb :00:14.2: Intel(R) Gigabit Ethernet Network Connection
  [4.412489] igb :00:14.2: eth1: PBA No: 002000-000
  [4.418235] igb :00:14.2: Using MSI-X interrupts. 4 rx queue(s), 4 tx 
queue(s)
  [4.428206] igb :00:14.1 enp0s20f1: renamed from eth0
  [4.465744] igb :00:14.2 enp0s20f2: renamed from eth1

  A patch can be found in OpenNetworkLinux:
  
https://github.com/opencomputeproject/OpenNetworkLinux/blob/master/packages/base/any/kernels/3.18.25/patches
  /driver-support-intel-igb-bcm54616-phy.patch

  It should be safe to include this in an SRU release since the new code
  is only functioning when certain ID is found.

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

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

[Kernel-packages] [Bug 1712481] Re: HID: multitouch: Support ALPS PTP Stick and Touchpad devices

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
zesty' to 'verification-done-zesty'. If the problem still exists, change
the tag 'verification-needed-zesty' to 'verification-failed-zesty'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-zesty

** Tags added: verification-needed-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/1712481

Title:
  HID: multitouch: Support ALPS PTP Stick and Touchpad devices

Status in HWE Next:
  In Progress
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Xenial:
  Fix Committed
Status in linux source package in Zesty:
  Fix Committed

Bug description:
  [Impact]
  Support to ALPS PTP Stick and Touchpad devices found on latest Dell Latitude 
systems.

  [Fix]
  This fix in two parts:
  1. Requires cherry-pick of patch submitted by ALPS in upstream kernel 4.13
  See: 
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?h=v4.13-rc6&id=504c932c7c47a6b4c572302a13873f7d83af1ff3

  2. Additional sauce patch adds the device-id of the new PTP stick. This
  patch is already submitted to linux-input and is pending review.
  See: http://marc.info/?l=linux-input&m=150235885218076&w=2

  [Test Case]
  Verified on the systems affected with this issue and confirmed that this 
solution works.

  [Regression Potential]
  The patch adds new device ids to hid multi-touch driver. With strict 
conditional filtering based on these device-ids, regression potential is 
minimal.

  This bug is used for tracking purposes, please do not triage.

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

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

[Kernel-packages] [Bug 1712746] Re: mwifiex causes kernel oops when AP mode is enabled

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
xenial' to 'verification-done-xenial'. If the problem still exists,
change the tag 'verification-needed-xenial' to 'verification-failed-
xenial'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-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/1712746

Title:
  mwifiex causes kernel oops when AP mode is enabled

Status in HWE Next:
  In Progress
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Xenial:
  Fix Committed

Bug description:
  When it's in AP mode, there's quite a chance to find kernel oops
  during reboot.

  This is caused by the wiphy may be NULL for some reason. It's likely a
  bug in mwifiex. We've already pinged Marvell and Murata. Before
  there's a real fix available, we should check wiphy before accessing
  it.

  I've tried a 4.13-rc6 kernel. Though it has oops for NULL pointer
  deference too, it happens in a different function in mwifiex. Thus the
  workaround for Xenial may or may not help for other series. Will need
  to reproduce this issue with Zesty and then we can decide whether this
  workaround should be applied to Zesty.

  [   30.701441] BUG: unable to handle kernel NULL pointer dereference at 
00f0
  [   30.709511] IP: [] mwifiex_get_cfp+0x49/0x150 [mwifiex]
  [   30.716494] PGD 0
  [   30.718575] Oops:  [#1] SMP
  [   30.721918] Modules linked in: ipt_MASQUERADE nf_nat_masquerade_ipv4 
iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conni
  [   30.836915] CPU: 1 PID: 679 Comm: kworker/u5:0 Not tainted 
4.4.0-57-generic #78-Ubuntu
  [   30.845018] Hardware name: Dell Inc. Edge Gateway 5000/  , BIOS 
01.05.00 10/18/2016
  [   30.853218] Workqueue: MWIFIEX_WORK_QUEUE mwifiex_main_work_queue [mwifiex]
  [   30.860362] task: 880077c11980 ti: 880075e48000 task.ti: 
880075e48000
  [   30.868018] RIP: 0010:[]  [] 
mwifiex_get_cfp+0x49/0x150 [mwifiex]
  [   30.877484] RSP: 0018:880075e4bbf8  EFLAGS: 00010202
  [   30.882920] RAX:  RBX: 0004 RCX: 
0004
  [   30.890221] RDX: 001000110010 RSI: 0004 RDI: 
0004
  [   30.897520] RBP: 880075e4bc28 R08: 0003 R09: 
0001
  [   30.904821] R10: 0001 R11: 02ff R12: 
0095
  [   30.912123] R13:  R14: 880075e4 R15: 
0095
  [   30.919425] FS:  () GS:88007130() 
knlGS:
  [   30.927701] CS:  0010 DS:  ES:  CR0: 8005003b
  [   30.933581] CR2: 00f0 CR3: 01e0a000 CR4: 
001006e0
  [   30.940882] Stack:
  [   30.942944]  0118 880075e4 8800750c4000 
880075e3ed59
  [   30.950592]  0095 880075e3ee01 880075e4bcd0 
c05846fc
  [   30.958232]   880075e4bc50 8140bcb5 
880075e4bc70
  [   30.965873] Call Trace:
  [   30.968397]  [] 
mwifiex_parse_single_response_buf+0x1fc/0x560 [mwifiex]
  [   30.976772]  [] ? find_next_bit+0x15/0x20
  [   30.982490]  [] 
mwifiex_handle_event_ext_scan_report+0x15c/0x340 [mwifiex]
  [   30.991139]  [] mwifiex_process_sta_event+0x276/0xb40 
[mwifiex]
  [   30.998806]  [] mwifiex_process_event+0x102/0x1c0 
[mwifiex]
  [   31.006120]  [] mwifiex_main_process+0x5de/0x8d0 
[mwifiex]
  [   31.013346]  [] mwifiex_main_work_queue+0x1f/0x30 
[mwifiex]
  [   31.020650]  [] process_one_work+0x165/0x480
  [   31.026624]  [] worker_thread+0x4b/0x4c0
  [   31.032240]  [] ? process_one_work+0x480/0x480
  [   31.038387]  [] kthread+0xd8/0xf0
  [   31.043384]  [] ? kthread_create_on_node+0x1e0/0x1e0
  [   31.050071]  [] ret_from_fork+0x3f/0x70
  [   31.055596]  [] ? kthread_create_on_node+0x1e0/0x1e0
  [   31.062276] Code: 85 c9 0f 84 ef 00 00 00 40 0f b6 de 49 89 fe 41 89 cd 89 
df 41 89 d4 e8 46 f1 00 00 84 c0 49 8b 86 e0 13 00 00 0f 84 98 00
  [   31.082756] RIP  [] mwifiex_get_cfp+0x49/0x150 [mwifiex]
  [   31.089820]  RSP 
  [   31.093392] CR2: 00f0
  [   31.096787] ---[ end trace f3a762be5787f138 ]---

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

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

[Kernel-packages] [Bug 1711056] Re: Backport more recent Broadcom bnxt_en driver

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
xenial' to 'verification-done-xenial'. If the problem still exists,
change the tag 'verification-needed-xenial' to 'verification-failed-
xenial'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-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/1711056

Title:
  Backport more recent Broadcom bnxt_en driver

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

Bug description:
  [Impact]

  The current Xenial bnxt_en driver only supports a limited (old) set of
  Broadcom NICs. We want to support newer NICs in Xenial without adding
  risk for existing users.

  The plan is to provide a separate driver called bnxt_en_bpo which is a
  backported driver from Broadcom. This driver will be modified to only
  support the new NICs that the current kernel driver does not support
  so that they both can co-exist.

  In other words, NICs that used to be supported by Xenial will still be
  managed by the current (unmodified) bnxt_en driver. Newer NICs will be
  managed by the new bnxt_en_bpo driver.

  [Test Case]

  Due to the unavailability of Broadcom HW, the only test that was run
  was to manually load both the bnxt_en and bnxt_en_bpo module to ensure
  that they can co-exist.

  [Regression Potential]

  There should be no regression potential, since the current driver is
  not modified and the new driver only loads for NICs that are not
  handled by the current driver.

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

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

[Kernel-packages] [Bug 1709171] Re: Disable CONFIG_MEMORY_HOTPLUG_DEFAULT_ONLINE

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
zesty' to 'verification-done-zesty'. If the problem still exists, change
the tag 'verification-needed-zesty' to 'verification-failed-zesty'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-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/1709171

Title:
  Disable CONFIG_MEMORY_HOTPLUG_DEFAULT_ONLINE

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

Bug description:
  == SRU Justification ==
  IBM is requesting that we disable CONFIG_MEMORY_HOTPLUG_DEFAULT_ONLINE in 
  the current ppc64el kernels up to 16.04.3.

  This was requested originally in LP#1706380, but it was not integrated
  in that bug.

  This chanage has already been made in Artful(Commit 8f189e08c9a), so that 
  is where I cherry picked the patch from.

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

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

[Kernel-packages] [Bug 1707643] Re: HP lt4132 LTE/HSPA+ 4G Module (03f0:a31d) does not work

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
xenial' to 'verification-done-xenial'. If the problem still exists,
change the tag 'verification-needed-xenial' to 'verification-failed-
xenial'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-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/1707643

Title:
  HP lt4132 LTE/HSPA+ 4G Module (03f0:a31d) does not work

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

Bug description:
  HP lt4132 LTE/HSPA+ 4G Module (03f0:a31d) modem does not work without this 
patch:
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?h=v4.13-rc3&id=a68491f895a937778bb25b0795830797239de31f

  Modem connects, but does not receive any packets.
  ifconfig shows;
  wwp0s20f0u10c3 Link encap:Ethernet  HWaddr 9e:63:76:8e:c0:91  
inet addr:10.137.74.102  Bcast:10.137.74.103  Mask:255.255.255.252
UP BROADCAST RUNNING NOARP MULTICAST  MTU:1500  Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:50 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000 
RX bytes:0 (0.0 B)  TX bytes:3465 (3.4 KB)

  Booting to http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.13-rc3/
  fixes the problem. Modem works as expected.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-generic 4.4.0.83.89
  ProcVersionSignature: Ubuntu 4.4.0-83.106-generic 4.4.70
  Uname: Linux 4.4.0-83-generic i686
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  it 1334 F pulseaudio
  CurrentDesktop: XFCE
  Date: Mon Jul 31 15:40:55 2017
  HibernationDevice: RESUME=UUID=9e656f3b-ee00-4e30-83e9-43a15bd0a6d1
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 002: ID 04f2:b595 Chicony Electronics Co., Ltd 
   Bus 001 Device 004: ID 03f0:a31d Hewlett-Packard 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP ProBook 430 G4
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-83-generic 
root=UUID=b7cbc0e4-b6dd-4df5-ac7a-7a3b513743d9 ro splash quiet vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-83-generic N/A
   linux-backports-modules-4.4.0-83-generic  N/A
   linux-firmware1.157.11
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/12/2017
  dmi.bios.vendor: HP
  dmi.bios.version: P85 Ver. 01.04
  dmi.board.name: 822C
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 42.65
  dmi.chassis.asset.tag: 5CD7274GN2
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrP85Ver.01.04:bd04/12/2017:svnHP:pnHPProBook430G4:pvr:rvnHP:rn822C:rvrKBCVersion42.65:cvnHP:ct10:cvr:
  dmi.product.name: HP ProBook 430 G4
  dmi.sys.vendor: HP

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

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

[Kernel-packages] [Bug 1709220] Re: RPT related fixes missing in Ubuntu 16.04.3

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
zesty' to 'verification-done-zesty'. If the problem still exists, change
the tag 'verification-needed-zesty' to 'verification-failed-zesty'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-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/1709220

Title:
  RPT related fixes missing in Ubuntu 16.04.3

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

Bug description:
  == SRU Justification ==
  These four commits are Radix performance patches specific to powerpc.  

  The patches are reported to help anywhere from 40% up to 3.5X on
  unixbench fork/exec testcases.

  The first patch was included in mainlne as of 4.12-rc1.  The last three 
patches are
  still in linux-next.


  ---Problem Description---

  The following patches are missing in the ubuntu 16.04.3 kernel

  https://lists.ozlabs.org/pipermail/linuxppc-dev/2017-April/156104.html

  https://lists.ozlabs.org/pipermail/linuxppc-dev/2017-April/156105.html

  https://lists.ozlabs.org/pipermail/linuxppc-dev/2017-April/157130.html

  ---uname output---

  4.10.0-29-generic #33~16.04.1-Ubuntu SMP Tue Jul 25 18:17:06 UTC 2017
  ppc64le ppc64le ppc64le GNU/Linux

  Machine Type = power9

  ---Steps to Reproduce---

  Did a fork and exec benchmark to look at the performance and they
  pointed to radix routines.

  Upstream commits mentioned:

  commit  f7327e0ba3805470cced2acfa053e795362ee41d

  powerpc/mm/radix: Remove unnecessary ptesync

  commit  f6b0df55cad252fedd60aa2ba75a0207d0006283

  powerpc/mm/radix: Don't do page walk cache flush when doing full mm
  flush

  commit  a5998fcb92552a18713b6aa5c146aa400e4d75ee

  powerpc/mm/radix: Optimise tlbiel flush all case

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

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

[Kernel-packages] [Bug 1709964] Re: Ubuntu 16.04.03: perf tool does not count pm_run_inst_cmpl with rcode on POWER9 DD2.0

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
zesty' to 'verification-done-zesty'. If the problem still exists, change
the tag 'verification-needed-zesty' to 'verification-failed-zesty'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-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/1709964

Title:
  Ubuntu 16.04.03: perf tool does not count pm_run_inst_cmpl with rcode
  on POWER9 DD2.0

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

Bug description:
  == SRU Justification ==
  Ubuntu 16.04.03: perf tool does not count pm_run_inst_cmpl with rcode on 
POWER9 DD2.0.

  This is a regression introduced by mainline commit 8d911904f3ce.  This 
regression
  is resolved by commit 8c218578fcbbbdb10416c8614658bf32e3bf1655.

  Commit 8c218578fc is available in mailine as of 4.12-rc5.



  ---Problem Description---
  Unable to count pm_run_inst_cmpl using perf tool on boston dd2.0

  root@isvbos3:~# perf stat -e r500fa,r600f4 -a  sleep 1

   Performance counter stats for 'system wide':

       r500fa
   8,162,912  r600f4

     1.001562716 seconds time elapsed

  ---uname output---
  Linux isvbos3 4.10.0-29-generic #33~16.04.1-Ubuntu SMP Tue Jul 25 18:17:06 
UTC 2017 ppc64le ppc64le ppc64le GNU/Linux

  Machine Type = p9 dd2.0

  ---Steps to Reproduce---
   root@isvbos3:~# perf stat -e r500fa,r600f4 -a  sleep 1

   Performance counter stats for 'system wide':

       r500fa
   8,162,912  r600f4

     1.001562716 seconds time elapsed

  > Also we need this upstream fix 8c218578fcbbbdb10416c8614658bf32e3bf1655 in
  > the distro.

  $ git log 8c218578fcbbbdb10416c8614658 -1
  commit 8c218578fcbbbdb10416c8614658bf32e3bf1655
  Author: Madhavan Srinivasan 
  Date:   Fri May 26 13:38:27 2017 +0530

  powerpc/perf: Fix Power9 test_adder fields

  Commit 8d911904f3ce4 ('powerpc/perf: Add restrictions to PMC5 in power9 
DD1')
  was added to restrict the use of PMC5 in Power9 DD1. Intention was to 
disable
  the use of PMC5 using raw event code. But instead of updating the
  power9_isa207_pmu structure (used on DD1), the commit incorrectly updated 
the
  power9_pmu structure. Fix it.

  Fixes: 8d911904f3ce ("powerpc/perf: Add restrictions to PMC5 in power9 
DD1")
  Reported-by: Shriya 
  Signed-off-by: Madhavan Srinivasan 
  Tested-by: Shriya 
  Signed-off-by: Michael Ellerman 

  $ git describe --contains 8c218578fcbbbdb
  v4.12-rc7~9^2~13
  $

  Commit 8c218578fc is available with kernel 4.12-rc7 afterwards.

  I don't see this fix in the Ubuntu 16.04.3 Zesty tree (the P9 hwe
  kernel, 4.10 based).

  Need to mirror to Canonical to request they pull in:
  8c218578fcbbbdb10416c8614658bf32e3bf1655

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

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

[Kernel-packages] [Bug 1709073] Re: [SRU][ZESTY]kernel BUG at /build/linux-H5UzH8/linux-4.10.0/drivers/nvme/host/pci.c:567!

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
zesty' to 'verification-done-zesty'. If the problem still exists, change
the tag 'verification-needed-zesty' to 'verification-failed-zesty'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-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/1709073

Title:
  [SRU][ZESTY]kernel BUG at /build/linux-
  H5UzH8/linux-4.10.0/drivers/nvme/host/pci.c:567!

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

Bug description:
  SRU Justification:

  Impact: reliably reproducible kernel BUG_ON leading to complete system hang
  Fix: cherry-pick upstream followup commit
  Testcase: mkfs.btrfs on Samsung SM/PM961 no longer triggers the BUG_ON

  Detailed description:

  the fix for http://bugs.launchpad.net/bugs/1657539 which cherry-picked

  729204ef49ec00b788ce23deb9eb922a5769f55d block: relax check on sg gap

  is missing a follow-up fix commit

  5a8d75a1b8c99bdc926ba69b7b7dbe4fae81a5af block: fix bio_will_gap() for
  first bvec with offset

  without, the following BUG_ON is triggered using a mkfs.btrfs
  /dev/nvme0n1 on a Samsung SM961/PM961 M.2 device:

  Aug 07 09:19:09 ubuntu kernel: kernel BUG at 
/build/linux-H5UzH8/linux-4.10.0/drivers/nvme/host/pci.c:567!
  Aug 07 09:19:09 ubuntu kernel: invalid opcode:  [#1] SMP
  Aug 07 09:19:09 ubuntu kernel: Modules linked in: nls_iso8859_1 ppdev 
snd_hda_intel snd_hda_codec snd_hda_core joydev snd_hwdep snd_pcm snd_ti
  Aug 07 09:19:09 ubuntu kernel: CPU: 0 PID: 2071 Comm: mkfs.btrfs Not tainted 
4.10.0-30-generic #34-Ubuntu
  Aug 07 09:19:09 ubuntu kernel: Hardware name: QEMU Standard PC (Q35 + ICH9, 
2009), BIOS 0.0.0 02/06/2015
  Aug 07 09:19:09 ubuntu kernel: task: 8e537417bfc0 task.stack: 
b580c1698000
  Aug 07 09:19:09 ubuntu kernel: RIP: 0010:nvme_queue_rq+0x746/0x8e0 [nvme]
  Aug 07 09:19:09 ubuntu kernel: RSP: 0018:b580c169b950 EFLAGS: 00010286
  Aug 07 09:19:09 ubuntu kernel: RAX: 0078 RBX: fa00 
RCX: 1000
  Aug 07 09:19:09 ubuntu kernel: RDX: 0010 RSI: 0200 
RDI: 0246
  Aug 07 09:19:09 ubuntu kernel: RBP: b580c169ba28 R08: 8e53733cb000 
R09: fa00
  Aug 07 09:19:09 ubuntu kernel: R10: 1000 R11: 8e53733d 
R12: 000273a8a000
  Aug 07 09:19:09 ubuntu kernel: R13: 0002fc00 R14: 8e53733cb000 
R15: 0200
  Aug 07 09:19:09 ubuntu kernel: FS:  7f92511ba080() 
GS:8e537fc0() knlGS:
  Aug 07 09:19:09 ubuntu kernel: CS:  0010 DS:  ES:  CR0: 
80050033
  Aug 07 09:19:09 ubuntu kernel: CR2: 7ffeecdc9000 CR3: 000274323000 
CR4: 06f0
  Aug 07 09:19:09 ubuntu kernel: DR0:  DR1:  
DR2: 
  Aug 07 09:19:09 ubuntu kernel: DR3:  DR6: fffe0ff0 
DR7: 0400
  Aug 07 09:19:09 ubuntu kernel: Call Trace:
  Aug 07 09:19:09 ubuntu kernel:  blk_mq_try_issue_directly+0x7e/0x100
  Aug 07 09:19:09 ubuntu kernel:  blk_mq_make_request+0x3cf/0x4e0
  Aug 07 09:19:09 ubuntu kernel:  generic_make_request+0x110/0x2d0
  Aug 07 09:19:09 ubuntu kernel:  submit_bio+0x73/0x150
  Aug 07 09:19:09 ubuntu kernel:  ? __percpu_counter_add+0x4f/0x60
  Aug 07 09:19:09 ubuntu kernel:  submit_bh_wbc+0x152/0x180
  Aug 07 09:19:09 ubuntu kernel:  __block_write_full_page+0x176/0x360
  Aug 07 09:19:09 ubuntu kernel:  ? I_BDEV+0x20/0x20
  Aug 07 09:19:09 ubuntu kernel:  ? I_BDEV+0x20/0x20
  Aug 07 09:19:09 ubuntu kernel:  block_write_full_page+0x13b/0x160
  Aug 07 09:19:09 ubuntu kernel:  blkdev_writepage+0x18/0x20
  Aug 07 09:19:09 ubuntu kernel:  __writepage+0x13/0x30
  Aug 07 09:19:09 ubuntu kernel:  write_cache_pages+0x205/0x530
  Aug 07 09:19:09 ubuntu kernel:  ? wb_position_ratio+0x1f0/0x1f0
  Aug 07 09:19:09 ubuntu kernel:  generic_writepages+0x56/0x90
  Aug 07 09:19:09 ubuntu kernel:  blkdev_writepages+0x2f/0x40
  Aug 07 09:19:09 ubuntu kernel:  do_writepages+0x1e/0x30
  Aug 07 09:19:09 ubuntu kernel:  __filemap_fdatawrite_range+0xc6/0x100
  Aug 07 09:19:09 ubuntu kernel:  SyS_fadvise64+0x25e/0x290
  Aug 07 09:19:09 ubuntu kernel:  entry_SYSCALL_64_fastpath+0x1e/0xad
  Aug 07 09:19:09 ubuntu kernel: RIP: 0033:0x7f925066debd
  Aug 07 09:19:09 ubuntu kernel: RSP: 002b:7ffeecd46a38 EFLAGS: 0246 
ORIG_RAX: 00dd
  Aug 07 09:19:09 ubuntu kernel: RAX: ffda RBX: 7ffeecd45a30 
RCX: 000

[Kernel-packages] [Bug 1709123] Re: [SRU][Zesty] [QDF2400] pl011 E44 erratum patch needed for 2.0 firmware and 1.1 silicon

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
zesty' to 'verification-done-zesty'. If the problem still exists, change
the tag 'verification-needed-zesty' to 'verification-failed-zesty'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-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/1709123

Title:
  [SRU][Zesty] [QDF2400] pl011 E44 erratum patch needed for 2.0 firmware
  and 1.1 silicon

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

Bug description:
  [Impact]
  Another bug was found in the pl011/spcr code that implements the work-around 
for erratum E44. This erratum affects QDF2400 v1.1 silicon. The software bug is 
only exposed when using Firmware 2.0 or later (estimated release October 2017).

  To ensure compatibility with future firmware, the Ubuntu kernel should
  apply the aforementioned patch. Without this patch, customers using
  the 2.0 firmware and 1.1 silicon might not have a functional UART
  console, either sometimes or always.

  It is expected that this problem does not occur with 2.0 or later
  silicon.

  [Test Case]
  Upgrade firmware to v2.0 on a QDF2400 server with 1.1 silicon, and the kernel 
should fail to boot, with the patch applied, we should see no boot failure.

  [Fix]
  Following patch in linux-next fixes this issue:
  37ef38f3f838 tty: pl011: fix initialization order of QDF2400 E44

  [Regression Potential]
  This is a bug fix to tty driver and limited to qdf2400. Low risk.

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

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

[Kernel-packages] [Bug 1709749] Re: Docker hangs with xfs using aufs storage driver

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
zesty' to 'verification-done-zesty'. If the problem still exists, change
the tag 'verification-needed-zesty' to 'verification-failed-zesty'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-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/1709749

Title:
  Docker hangs with xfs using aufs storage driver

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

Bug description:
  SRU Justification

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

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

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

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

  ---

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

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

  3) What you expected to happen

  Docker with AUFS on XFS works.

  4) What happened instead

  It hangs up

  ---

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

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

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

[Kernel-packages] [Bug 1700972] Re: Please only recommend or suggest initramfs-tools | linux-initramfs-tool for kernels able to boot without initramfs

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
xenial' to 'verification-done-xenial'. If the problem still exists,
change the tag 'verification-needed-xenial' to 'verification-failed-
xenial'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-trusty

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

Title:
  Please only recommend or suggest initramfs-tools | linux-initramfs-
  tool for kernels able to boot without initramfs

Status in linux package in Ubuntu:
  Fix Released
Status in linux-aws package in Ubuntu:
  Fix Committed
Status in linux-azure package in Ubuntu:
  Fix Committed
Status in linux-gke package in Ubuntu:
  Fix Committed
Status in linux source package in Trusty:
  Fix Committed
Status in linux source package in Xenial:
  Fix Committed
Status in linux-aws source package in Xenial:
  Fix Committed
Status in linux-azure source package in Xenial:
  Fix Committed
Status in linux-gke source package in Xenial:
  Fix Committed
Status in linux source package in Zesty:
  Fix Committed
Status in linux source package in Artful:
  Fix Released

Bug description:
  Linux kernel packages depend on initramfs-tools | linux-initramfs-
  tool, even when systems using the kernel can be booted without it.

  Demoting the dependency to Recommends: or Suggests: would allow
  creating smaller images without initramfs-tools installed and fully
  skipping initramfs updates upon kernel updates saving time.

  Please consider changing the Depends: to Recommends: or Suggests: for
  kernels capable of booting without initramfs.

  initramfs-tools is still a dependency of ubuntu-minimal thus
  accidental removal of initramfs-tools resulting an unbootable system
  would still be unlikely.

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

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

[Kernel-packages] [Bug 1710868] Re: memory-hotplug test needs to be fixed

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
zesty' to 'verification-done-zesty'. If the problem still exists, change
the tag 'verification-needed-zesty' to 'verification-failed-zesty'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-zesty

** Tags added: verification-needed-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/1710868

Title:
  memory-hotplug test needs to be fixed

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

Bug description:
  SRU Justification:

  Impact: 
  The memory-hotplug test in the kernel tree 
(tools/testing/selftests/memory-hotplug/) needs to be fixed:
  1. The test will pass even the memory blocks are failed to be offlined [1].
  2. It's using a random number generator to decide if each memory block needs 
to be offlined, which is not ideal for testing as the block it tries to unplug 
might be different between two runs.
  3. The "-r" flag, percent-of-memory-to-offline, does not match what is says. 
It's being used as the percentage to get a memory block offlined instead.

  Fix: 
  Apply the following patch from upstream can fix these issues:
  593f9278 - selftests: typo correction for memory-hotplug test
  a34b28c9 - selftests: check hot-pluggagble memory for memory-hotplug test
  72441ea5 - selftests: check percentage range for memory-hotplug test
  02d8f075 - selftests: add missing test name in memory-hotplug test
  5ff0c60b - selftests: fix memory-hotplug test

  Testcase:
  Run the script directly, it will fail when all memory blocks are busy. And it 
will try to unplug memory blocks in a fixed order.

  Regression Potential:
  Negligible, it's just affecting this specific test case among those testing 
tools.

  [1] https://paste.ubuntu.com/25318445/

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

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

[Kernel-packages] [Bug 1709352] Re: Avoid spurious PMU interrupts after idle

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
zesty' to 'verification-done-zesty'. If the problem still exists, change
the tag 'verification-needed-zesty' to 'verification-failed-zesty'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-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/1709352

Title:
  Avoid spurious PMU interrupts after idle

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

Bug description:
  Hello Canonical,

  For POWER9 enablement, we need to backport the following commit ID up
  to Zesty.

  101dd590a7fa ("powerpc/perf: Avoid spurious PMU interrupts after
  idle")

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

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

[Kernel-packages] [Bug 1682644] Re: IPR driver causes multipath to fail paths/stuck IO on Medium Errors

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
xenial' to 'verification-done-xenial'. If the problem still exists,
change the tag 'verification-needed-xenial' to 'verification-failed-
xenial'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!

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

Title:
IPR driver causes multipath to fail paths/stuck IO on Medium Errors

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

Bug description:
SRU Justification:

Impact: stuck I/O to multipath disks with medium errors (on IPR controllers)
Fix: upstream commit for IPR driver to allow SCSI layer to handle the error
Testcase: perform I/O to a failing disk which is multipathed (on IPR
controller), which returns SCSI Medium Errors (without the fix,
the I/O gets stuck).
the commit message describes a test-case w/ sg_dd.

---Problem Description---
IPR driver causes multipath to fail paths/stuck IO on Medium Errors

This problem is resolved with this upstream accepted patch, scheduled for
4.11.
The detailed problem description and resolution are described in the commit
message.

> scsi: ipr: do not set DID_PASSTHROUGH on CHECK CONDITION
>
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=785a470496d8e0a32e3d39f376984eb2c98ca5b3

Please apply to 17.04 (target 16.04.3 HWE kernel) and 16.04 (GA kernel).
Patch already applied to 17.10.

The business justification for the SRU is:

Clients with a dual-controller multipathed IPR configuration that
eventually runs into failing disk/sectors, will experience an I/O hang
once the drive reports a Medium Error, which can hang an application
or even the root filesystem (whatever is doing I/O to the failing
drive), potentially hanging the system.

Thanks.

---Additional Hardware Info---
Dual (IPR) controller setup, multipath enabled

---Steps to Reproduce---
1) Use a disk with bad sectors (or force such condition, via internal/special
tools)
2) Multipath that disk
3) Run IO to the multipath device on the bad sectors
4) Both paths will be failed, and IO is stuck due to queue_if_no_path
(enabled by default for IPR)

The detailed problem description and resolution are described in the
commit message.

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

[Kernel-packages] [Bug 1680513] Re: Migrating KSM page causes the VM lock up as the KSM page merging list is too large

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
xenial' to 'verification-done-xenial'. If the problem still exists,
change the tag 'verification-needed-xenial' to 'verification-failed-
xenial'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-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/1680513

Title:
  Migrating KSM page causes the VM lock up as the KSM page merging list
  is too large

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

Bug description:
  [Impact]
  After numad is enabled and there are several VMs running on the same
  host machine(host kernel version: 4.4.0-72-generic #93), the
  softlockup messages can be observed inside the VMs' dmesg.

  First, the crashdump was captured when the symptom was observed. At
  the first glance, it looks like an IPI lost issue. The numad process
  initiates a migration of memory, and as part of this, needs to flush
  the TLB cache of another CPU. When the crash dump was taken, that
  other CPU has the TLB flush pending, but not executed. 

  The numad kernel task is holding a semaphore lock mmap_sem(for the
  VM's memory) to do the migration, and the tasks that actually end up
  being blocked are other virtual CPUs for the same VM. These tasks need
  to access or make changes to the memory map for the VM because of the
  VM page fault, but cannot acquire the semaphore lock.

  However, the original thoughts on the root cause (unhandled IPI or csd
  lock issue) are incorrect.

  We originally suspected an issue with a lost IPI (inter processor
  interrupt) that performs remote CPU cache flushes during page
  migration, or a known issue with the "csd" lock used to synchronize
  the remote CPU cache flush.  A lost IPI would be a function of the
  system firmware or chipset (it is not a CPU issue), but the known csd
  issue is hardware independent. 

  Gavin created the hotfix kernel with changes in the csd_lock_wait
  function that would time out if the unlock never happens (the end
  result of either cause), and print messages to the console when that
  timeout occurred. The messages look like: 

  csd_lock_wait called %d times

  csd: Detected non-responsive CSD lock (#%d) on CPU#%02d, waiting
  %Ld.%03Ld secs for CPU#%02d

  However, the VMs are still experiencing the hangs, but the
  csd_lock_wait timeout is not happening. This suggests that the csd
  lock / lost IPI is not the actual cause.

  In the crash dump, the numad task has induced a migration, and the
  stack is as follows: 

  #1 [885f8fb4fb78] smp_call_function_many 
  #2 [885f8fb4fbc0] native_flush_tlb_others 
  #3 [885f8fb4fc08] flush_tlb_page 
  #4 [885f8fb4fc30] ptep_clear_flush 
  #5 [885f8fb4fc60] try_to_unmap_one 
  #6 [885f8fb4fcd0] rmap_walk_ksm 
  #7 [885f8fb4fd28] rmap_walk 
  #8 [885f8fb4fd80] try_to_unmap 
  #9 [885f8fb4fdc8] migrate_pages 
  #10 [885f8fb4fe80] do_migrate_pages 

  
  The frame #1 is actually in the csd_lock_wait function mentioned
  above, but the compiler has optimized that call and it does not appear
  in the stack. 

  What happens here is that do_migrate_pages (frame #10) acquires the
  semaphore that everything else is waiting for (and that eventually
  produce the hang warnings), and it holds that semaphore for the
  duration of the page migration.  This strongly suggests that this
  single do_migrate_pages call is taking in excess of 10 seconds, and if
  the csd lock is not stuck, then something else within its call path is
  not functioning correctly. 

  We originally suspected that the lost IPI/csd lock hang was
  responsible for the hung task timeouts, but in the absence of the csd
  warning messages, the cause presumably lies elsewhere. 

  A KSM function appears in frame #6; this is the function that will
  search out the merged pages to handle them for the migration. 

  Gavin have tried to disassemble the code and finally find the 
  stable_node->hlist is as long as 2306920 entries:

  rmap_item list(stable_node->hlist): 
  stable_node: 0x881f836ba000 stable_node->hlist->first = 
0x883f3e5746b0 

  struct hlist_head { 
  [0] struct hlist_node *first; 
  } 
  struct hlist_node { 
  [0] struct hlist_node *next; 
  [8] struct hlist_node **pprev; 
  } 

  crash> list hlist_node.next 0x883f3e5746b0 > rmap_item.lst

  $ wc -l rmap_item.lst 
  2306920 rmap_item.lst

  This is roughly 9 G

[Kernel-packages] [Bug 1682644] Re: IPR driver causes multipath to fail paths/stuck IO on Medium Errors

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
zesty' to 'verification-done-zesty'. If the problem still exists, change
the tag 'verification-needed-zesty' to 'verification-failed-zesty'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-zesty

** Tags added: verification-needed-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/1682644

Title:
  IPR driver causes multipath to fail paths/stuck IO on Medium Errors

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

Bug description:
  SRU Justification:

  Impact: stuck I/O to multipath disks with medium errors (on IPR controllers)
  Fix: upstream commit for IPR driver to allow SCSI layer to handle the error
  Testcase: perform I/O to a failing disk which is multipathed (on IPR
controller), which returns SCSI Medium Errors (without the fix,
the I/O gets stuck). 
the commit message describes a test-case w/ sg_dd.

  
  ---Problem Description---
  IPR driver causes multipath to fail paths/stuck IO on Medium Errors

  This problem is resolved with this upstream accepted patch, scheduled for 
4.11.
  The detailed problem description and resolution are described in the commit 
message.

  > scsi: ipr: do not set DID_PASSTHROUGH on CHECK CONDITION
  > 
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=785a470496d8e0a32e3d39f376984eb2c98ca5b3

  Please apply to 17.04 (target 16.04.3 HWE kernel) and 16.04 (GA kernel).
  Patch already applied to 17.10.

  The business justification for the SRU is:

  Clients with a dual-controller multipathed IPR configuration that
  eventually runs into failing disk/sectors, will experience an I/O hang
  once the drive reports a Medium Error, which can hang an application
  or even the root filesystem (whatever is doing I/O to the failing
  drive), potentially hanging the system.

  Thanks.

  ---Additional Hardware Info---
  Dual (IPR) controller setup, multipath enabled

  ---Steps to Reproduce---
  1) Use a disk with bad sectors (or force such condition, via internal/special 
tools)
  2) Multipath that disk
  3) Run IO to the multipath device on the bad sectors
  4) Both paths will be failed, and IO is stuck due to queue_if_no_path 
(enabled by default for IPR)

  The detailed problem description and resolution are described in the
  commit message.

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

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

[Kernel-packages] [Bug 1700972] Re: Please only recommend or suggest initramfs-tools | linux-initramfs-tool for kernels able to boot without initramfs

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
zesty' to 'verification-done-zesty'. If the problem still exists, change
the tag 'verification-needed-zesty' to 'verification-failed-zesty'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-zesty

** Tags added: verification-needed-xenial

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

Title:
  Please only recommend or suggest initramfs-tools | linux-initramfs-
  tool for kernels able to boot without initramfs

Status in linux package in Ubuntu:
  Fix Released
Status in linux-aws package in Ubuntu:
  Fix Committed
Status in linux-azure package in Ubuntu:
  Fix Committed
Status in linux-gke package in Ubuntu:
  Fix Committed
Status in linux source package in Trusty:
  Fix Committed
Status in linux source package in Xenial:
  Fix Committed
Status in linux-aws source package in Xenial:
  Fix Committed
Status in linux-azure source package in Xenial:
  Fix Committed
Status in linux-gke source package in Xenial:
  Fix Committed
Status in linux source package in Zesty:
  Fix Committed
Status in linux source package in Artful:
  Fix Released

Bug description:
  Linux kernel packages depend on initramfs-tools | linux-initramfs-
  tool, even when systems using the kernel can be booted without it.

  Demoting the dependency to Recommends: or Suggests: would allow
  creating smaller images without initramfs-tools installed and fully
  skipping initramfs updates upon kernel updates saving time.

  Please consider changing the Depends: to Recommends: or Suggests: for
  kernels capable of booting without initramfs.

  initramfs-tools is still a dependency of ubuntu-minimal thus
  accidental removal of initramfs-tools resulting an unbootable system
  would still be unlikely.

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

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

[Kernel-packages] [Bug 1665783] Re: Include Broadcom GPL modules in Xenial Kernel

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
xenial' to 'verification-done-xenial'. If the problem still exists,
change the tag 'verification-needed-xenial' to 'verification-failed-
xenial'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-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/1665783

Title:
  Include Broadcom GPL modules in Xenial Kernel

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

Bug description:
  Please include the OpenNSL GPL modules with the Kernel.
  These modules are located at https://github.com/Broadcom-Switch/OpenNSL.
  The latest SDK version is 6.5.6. 
  We would like to have the kernel modules included with the LTS Xenial kernel 
so that we can provide these modules to network vendors so that they don't have 
to compile them and taint our working kernel. 
  We would want to manage these modules so that we can perform updates and 
security fixes to the kernel and even use kernel-livepatch with these devices. 
  Currently, Network vendors compile and build these against older kernel's and 
then they cannot be patched or updated leaving network devices vulnerable to 
security threats that normally would be patched by our systems. By having us 
manage these modules, we can maintain security and compatibility with the 
kernel and the network vendors can use our native kernel with their software.

  The three modules that get built are linux-kernel-bde.ko, linux-user-
  bde,ko and linux-bcm-knet.ko.

  If you have any other questions, please don't hesitate to contact me.

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

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

[Kernel-packages] [Bug 1700972] Re: Please only recommend or suggest initramfs-tools | linux-initramfs-tool for kernels able to boot without initramfs

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
trusty' to 'verification-done-trusty'. If the problem still exists,
change the tag 'verification-needed-trusty' to 'verification-failed-
trusty'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!

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

Title:
  Please only recommend or suggest initramfs-tools | linux-initramfs-
  tool for kernels able to boot without initramfs

Status in linux package in Ubuntu:
  Fix Released
Status in linux-aws package in Ubuntu:
  Fix Committed
Status in linux-azure package in Ubuntu:
  Fix Committed
Status in linux-gke package in Ubuntu:
  Fix Committed
Status in linux source package in Trusty:
  Fix Committed
Status in linux source package in Xenial:
  Fix Committed
Status in linux-aws source package in Xenial:
  Fix Committed
Status in linux-azure source package in Xenial:
  Fix Committed
Status in linux-gke source package in Xenial:
  Fix Committed
Status in linux source package in Zesty:
  Fix Committed
Status in linux source package in Artful:
  Fix Released

Bug description:
  Linux kernel packages depend on initramfs-tools | linux-initramfs-
  tool, even when systems using the kernel can be booted without it.

  Demoting the dependency to Recommends: or Suggests: would allow
  creating smaller images without initramfs-tools installed and fully
  skipping initramfs updates upon kernel updates saving time.

  Please consider changing the Depends: to Recommends: or Suggests: for
  kernels capable of booting without initramfs.

  initramfs-tools is still a dependency of ubuntu-minimal thus
  accidental removal of initramfs-tools resulting an unbootable system
  would still be unlikely.

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

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

[Kernel-packages] [Bug 1709073] Re: [SRU][ZESTY]kernel BUG at /build/linux-H5UzH8/linux-4.10.0/drivers/nvme/host/pci.c:567!

2017-09-01 Thread Fabian Grünbichler

no longer have the test hardware to verify the kernel in -proposed, but
I did verify that the commit in question fixes the problem (hence my
report ;)).

** Tags removed: verification-needed-zesty
** Tags added: verification-done-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/1709073

Title:
  [SRU][ZESTY]kernel BUG at /build/linux-
  H5UzH8/linux-4.10.0/drivers/nvme/host/pci.c:567!

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

Bug description:
  SRU Justification:

  Impact: reliably reproducible kernel BUG_ON leading to complete system hang
  Fix: cherry-pick upstream followup commit
  Testcase: mkfs.btrfs on Samsung SM/PM961 no longer triggers the BUG_ON

  Detailed description:

  the fix for http://bugs.launchpad.net/bugs/1657539 which cherry-picked

  729204ef49ec00b788ce23deb9eb922a5769f55d block: relax check on sg gap

  is missing a follow-up fix commit

  5a8d75a1b8c99bdc926ba69b7b7dbe4fae81a5af block: fix bio_will_gap() for
  first bvec with offset

  without, the following BUG_ON is triggered using a mkfs.btrfs
  /dev/nvme0n1 on a Samsung SM961/PM961 M.2 device:

  Aug 07 09:19:09 ubuntu kernel: kernel BUG at 
/build/linux-H5UzH8/linux-4.10.0/drivers/nvme/host/pci.c:567!
  Aug 07 09:19:09 ubuntu kernel: invalid opcode:  [#1] SMP
  Aug 07 09:19:09 ubuntu kernel: Modules linked in: nls_iso8859_1 ppdev 
snd_hda_intel snd_hda_codec snd_hda_core joydev snd_hwdep snd_pcm snd_ti
  Aug 07 09:19:09 ubuntu kernel: CPU: 0 PID: 2071 Comm: mkfs.btrfs Not tainted 
4.10.0-30-generic #34-Ubuntu
  Aug 07 09:19:09 ubuntu kernel: Hardware name: QEMU Standard PC (Q35 + ICH9, 
2009), BIOS 0.0.0 02/06/2015
  Aug 07 09:19:09 ubuntu kernel: task: 8e537417bfc0 task.stack: 
b580c1698000
  Aug 07 09:19:09 ubuntu kernel: RIP: 0010:nvme_queue_rq+0x746/0x8e0 [nvme]
  Aug 07 09:19:09 ubuntu kernel: RSP: 0018:b580c169b950 EFLAGS: 00010286
  Aug 07 09:19:09 ubuntu kernel: RAX: 0078 RBX: fa00 
RCX: 1000
  Aug 07 09:19:09 ubuntu kernel: RDX: 0010 RSI: 0200 
RDI: 0246
  Aug 07 09:19:09 ubuntu kernel: RBP: b580c169ba28 R08: 8e53733cb000 
R09: fa00
  Aug 07 09:19:09 ubuntu kernel: R10: 1000 R11: 8e53733d 
R12: 000273a8a000
  Aug 07 09:19:09 ubuntu kernel: R13: 0002fc00 R14: 8e53733cb000 
R15: 0200
  Aug 07 09:19:09 ubuntu kernel: FS:  7f92511ba080() 
GS:8e537fc0() knlGS:
  Aug 07 09:19:09 ubuntu kernel: CS:  0010 DS:  ES:  CR0: 
80050033
  Aug 07 09:19:09 ubuntu kernel: CR2: 7ffeecdc9000 CR3: 000274323000 
CR4: 06f0
  Aug 07 09:19:09 ubuntu kernel: DR0:  DR1:  
DR2: 
  Aug 07 09:19:09 ubuntu kernel: DR3:  DR6: fffe0ff0 
DR7: 0400
  Aug 07 09:19:09 ubuntu kernel: Call Trace:
  Aug 07 09:19:09 ubuntu kernel:  blk_mq_try_issue_directly+0x7e/0x100
  Aug 07 09:19:09 ubuntu kernel:  blk_mq_make_request+0x3cf/0x4e0
  Aug 07 09:19:09 ubuntu kernel:  generic_make_request+0x110/0x2d0
  Aug 07 09:19:09 ubuntu kernel:  submit_bio+0x73/0x150
  Aug 07 09:19:09 ubuntu kernel:  ? __percpu_counter_add+0x4f/0x60
  Aug 07 09:19:09 ubuntu kernel:  submit_bh_wbc+0x152/0x180
  Aug 07 09:19:09 ubuntu kernel:  __block_write_full_page+0x176/0x360
  Aug 07 09:19:09 ubuntu kernel:  ? I_BDEV+0x20/0x20
  Aug 07 09:19:09 ubuntu kernel:  ? I_BDEV+0x20/0x20
  Aug 07 09:19:09 ubuntu kernel:  block_write_full_page+0x13b/0x160
  Aug 07 09:19:09 ubuntu kernel:  blkdev_writepage+0x18/0x20
  Aug 07 09:19:09 ubuntu kernel:  __writepage+0x13/0x30
  Aug 07 09:19:09 ubuntu kernel:  write_cache_pages+0x205/0x530
  Aug 07 09:19:09 ubuntu kernel:  ? wb_position_ratio+0x1f0/0x1f0
  Aug 07 09:19:09 ubuntu kernel:  generic_writepages+0x56/0x90
  Aug 07 09:19:09 ubuntu kernel:  blkdev_writepages+0x2f/0x40
  Aug 07 09:19:09 ubuntu kernel:  do_writepages+0x1e/0x30
  Aug 07 09:19:09 ubuntu kernel:  __filemap_fdatawrite_range+0xc6/0x100
  Aug 07 09:19:09 ubuntu kernel:  SyS_fadvise64+0x25e/0x290
  Aug 07 09:19:09 ubuntu kernel:  entry_SYSCALL_64_fastpath+0x1e/0xad
  Aug 07 09:19:09 ubuntu kernel: RIP: 0033:0x7f925066debd
  Aug 07 09:19:09 ubuntu kernel: RSP: 002b:7ffeecd46a38 EFLAGS: 0246 
ORIG_RAX: 00dd
  Aug 07 09:19:09 ubuntu kernel: RAX: ffda RBX: 7ffeecd45a30 
RCX: 7f925066debd
  Aug 07 09:19:09 ubuntu kernel: RDX:  RSI:  
RDI: 0004
  Aug 07 09:19:09 ubuntu kernel: RBP:  R08:  
R09: 1001
  Aug 07 09:19:09 ubuntu kernel: R10: 0004 R11: 0246 
R12: 0010
  Aug 07 09:19:09 ubuntu kernel: R13: 7ffeecd45a40 R14: 0004 
R15: 000

[Kernel-packages] [Bug 1581711] Re: 024C:B723 Need support for Realtek Wifi card rtl8723bs

It's enabled since v4.12, so it will work out of the box on v4.13.

Backport to v4.4 is no easy task and I doubt anyone really need this on
Xenial.

** Changed in: hwe-next/xenial
   Status: New => Won't Fix

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

Title:
  024C:B723 Need support for Realtek Wifi card rtl8723bs

Status in HWE Next:
  Won't Fix
Status in HWE Next xenial series:
  Won't Fix
Status in linux package in Ubuntu:
  Fix Released

Bug description:
  This device is appearing in some OEM machines.

  WORKAROUND: sudo apt-get install build-essential linux-headers-generic git
  git clone https://github.com/hadess/rtl8723as.git
  cd rtl8723as
  make
  sudo make install
  sudo depmod -a
  sudo modprobe r8723bs

  cat /sys/bus/sdio/devices/mmc1:0001:1/*
  0x07
  0xb723
  cat: '/sys/bus/sdio/devices/mmc1:0001:1/firmware_node': Is a directory
  sdio:c07v024CdB723
  cat: '/sys/bus/sdio/devices/mmc1:0001:1/power': Is a directory
  cat: '/sys/bus/sdio/devices/mmc1:0001:1/subsystem': Is a directory
  SDIO_CLASS=07
  SDIO_ID=024C:B723
  MODALIAS=sdio:c07v024CdB723
  0x024c

  WORKAROUND 2: Install this DKMS driver package:
  
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1581711/+attachment/4732838/+files
  /rtl8723bs-dkms_4.4.1+17245.20160325.2_all.deb

  ---
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=e59c3a84-25cb-4931-887e-13ab29829963
  InstallationDate: Installed on 2016-05-14 (0 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Release amd64 
(20160421)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 06cb:73f4 Synaptics, Inc.
   Bus 001 Device 002: ID 05e3:0608 Genesys Logic, Inc. Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Acer One S1002
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-22-generic.efi.signed 
root=/dev/mmcblk0p2 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-22-generic N/A
   linux-backports-modules-4.4.0-22-generic  N/A
   linux-firmware1.157
  RfKill:
   0: phy0: Wireless LAN
    Soft blocked: no
    Hard blocked: no
  Tags:  xenial
  Uname: Linux 4.4.0-22-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/20/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.10
  dmi.board.name: Popcorn
  dmi.board.vendor: Acer
  dmi.board.version: To be filled by O.E.M.
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.10:bd10/20/2015:svnAcer:pnOneS1002:pvr1.10:rvnAcer:rnPopcorn:rvrTobefilledbyO.E.M.:cvnAcer:ct10:cvrToBeFilledByO.E.M.:
  dmi.product.name: One S1002
  dmi.product.version: 1.10
  dmi.sys.vendor: Acer

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

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

[Kernel-packages] [Bug 1579748] Re: rtsx_usb module for Realtek Semiconductor Corp. RTS5129 Card Reader Controller: mmc errors and read data corruption

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

** Changed in: linux (Ubuntu)
 Assignee: Kai-Heng Feng (kaihengfeng) => (unassigned)

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

Title:
  rtsx_usb module for Realtek Semiconductor Corp. RTS5129 Card Reader
  Controller: mmc errors and read data corruption

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  RTS5129 Card Reader has issues with rtsx_usb module on kernels >=3.16
  (since kmod-staging rts5129 module replaced with rtsx).

  Copying files from FAT32 SDHC memory card produces error messages in syslog:
  May  9 05:39:15 dev-laptop kernel: [  134.762713] mmcblk0: error -110 sending 
stop command, original cmd response 0x900, card status 0x900
  May  9 05:39:15 dev-laptop kernel: [  135.427035] mmcblk0: error -110 sending 
stop command, original cmd response 0x900, card status 0x900
  May  9 05:39:16 dev-laptop kernel: [  136.030041] mmcblk0: error -110 sending 
stop command, original cmd response 0x900, card status 0x900

  Also these errors indicate that copied files are corrupted - md5sum
  shows different checksums for copied file after each "insert card/copy
  file/check md5sum/eject card" cycle (actually you can skip "copy file"
  step and run "check md5sum" step directly with file on mounted memory
  card filesystem).

  Running sudo badblocks -n /dev/mmcblk0 produces same error messages
  and prints a lot of random block numbers.

  Hardware:
   - dell inspiron 7720 laptop (a few different RAM modules and HDD drives used 
for testing);
   - Realtek Semiconductor Corp. RTS5129 Card Reader (ID 0bda:0129);
   - Transcend 32Gb SDHC Memory card Class 10 UHS-I.

  Bug exists in latest xenial 4.4.0-22.39 kernel and xenial mainline
  4.4.9-040409_4.4.9-040409.201605041832.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-22-generic 4.4.0-22.39
  ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dev1692 F pulseaudio
  CurrentDesktop: Unity
  Date: Mon May  9 08:38:14 2016
  HibernationDevice: RESUME=UUID=cf073128-d53a-4214-96bc-3acdf0516900
  InstallationDate: Installed on 2016-05-08 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Dell Inc. Inspiron 7720
  ProcFB:
   0 inteldrmfb
   1 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-22-generic 
root=UUID=2e4e4944-669a-4f1b-a080-87971c644984 ro quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-22-generic N/A
   linux-backports-modules-4.4.0-22-generic  N/A
   linux-firmware1.157
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: yes
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/23/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A16
  dmi.board.name: 04M3YM
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnDellInc.:bvrA16:bd08/23/2013:svnDellInc.:pnInspiron7720:pvr:rvnDellInc.:rn04M3YM:rvrA00:cvnDellInc.:ct8:cvr0.1:
  dmi.product.name: Inspiron 7720
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1581711] Re: 024C:B723 Need support for Realtek Wifi card rtl8723bs

** Changed in: hwe-next
   Status: New => Won't Fix

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

Title:
  024C:B723 Need support for Realtek Wifi card rtl8723bs

Status in HWE Next:
  Won't Fix
Status in HWE Next xenial series:
  Won't Fix
Status in linux package in Ubuntu:
  Fix Released

Bug description:
  This device is appearing in some OEM machines.

  WORKAROUND: sudo apt-get install build-essential linux-headers-generic git
  git clone https://github.com/hadess/rtl8723as.git
  cd rtl8723as
  make
  sudo make install
  sudo depmod -a
  sudo modprobe r8723bs

  cat /sys/bus/sdio/devices/mmc1:0001:1/*
  0x07
  0xb723
  cat: '/sys/bus/sdio/devices/mmc1:0001:1/firmware_node': Is a directory
  sdio:c07v024CdB723
  cat: '/sys/bus/sdio/devices/mmc1:0001:1/power': Is a directory
  cat: '/sys/bus/sdio/devices/mmc1:0001:1/subsystem': Is a directory
  SDIO_CLASS=07
  SDIO_ID=024C:B723
  MODALIAS=sdio:c07v024CdB723
  0x024c

  WORKAROUND 2: Install this DKMS driver package:
  
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1581711/+attachment/4732838/+files
  /rtl8723bs-dkms_4.4.1+17245.20160325.2_all.deb

  ---
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=e59c3a84-25cb-4931-887e-13ab29829963
  InstallationDate: Installed on 2016-05-14 (0 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Release amd64 
(20160421)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 06cb:73f4 Synaptics, Inc.
   Bus 001 Device 002: ID 05e3:0608 Genesys Logic, Inc. Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Acer One S1002
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-22-generic.efi.signed 
root=/dev/mmcblk0p2 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-22-generic N/A
   linux-backports-modules-4.4.0-22-generic  N/A
   linux-firmware1.157
  RfKill:
   0: phy0: Wireless LAN
    Soft blocked: no
    Hard blocked: no
  Tags:  xenial
  Uname: Linux 4.4.0-22-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/20/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.10
  dmi.board.name: Popcorn
  dmi.board.vendor: Acer
  dmi.board.version: To be filled by O.E.M.
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.10:bd10/20/2015:svnAcer:pnOneS1002:pvr1.10:rvnAcer:rnPopcorn:rvrTobefilledbyO.E.M.:cvnAcer:ct10:cvrToBeFilledByO.E.M.:
  dmi.product.name: One S1002
  dmi.product.version: 1.10
  dmi.sys.vendor: Acer

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

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

[Kernel-packages] [Bug 1714262] [NEW] mysql socket no longer accessible during overlayroot

You have been subscribed to a public bug:

Running on a Ubuntu 16.04.2 LTS
install mysql through apt-get
successfully run 'mysql' and connect
add "tmpfs" to /etc/overlayroot.conf
reboot the system to engage overlay
attempt 'mysql' command and get a fail to connect to socket error
this is repeatable by added and removing the overlay

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


** Tags: mysql overlay overlayroot socket
-- 
mysql socket no longer accessible during overlayroot
https://bugs.launchpad.net/bugs/1714262
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 1714262] Re: mysql socket no longer accessible during overlayroot

2017-09-01 Thread ChristianEhrhardt

Hi Cody,
that would be a bug (feature request) against (upstream) overlayfs then right?

I wonder this being against "cloud-initramfs-tools (Ubuntu)".
Lets retarget the bug at overlayfs for now to discuss in that context (which is 
the kernel package).

Or OTOH you meant to want us to consider picking [1] somewhere into
mysql packaging so adding a task for that as well.

Please help to clarify further.

** Package changed: cloud-initramfs-tools (Ubuntu) => linux (Ubuntu)

** Also affects: mysql-5.7 (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: mysql-5.7 (Ubuntu)
   Status: New => Incomplete

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

Title:
  mysql socket no longer accessible during overlayroot

Status in linux package in Ubuntu:
  Incomplete
Status in mysql-5.7 package in Ubuntu:
  Incomplete

Bug description:
  Running on a Ubuntu 16.04.2 LTS
  install mysql through apt-get
  successfully run 'mysql' and connect
  add "tmpfs" to /etc/overlayroot.conf
  reboot the system to engage overlay
  attempt 'mysql' command and get a fail to connect to socket error
  this is repeatable by added and removing the overlay

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

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

[Kernel-packages] [Bug 1714262] Re: mysql socket no longer accessible during overlayroot

2017-09-01 Thread ChristianEhrhardt

I thank you for your report and your help to make Ubuntu better.
But for now I'll mark it incomplete until it is clear what the requested action 
shall be.

Please feel free to set back to new when the clarification is provided.

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

Title:
  mysql socket no longer accessible during overlayroot

Status in linux package in Ubuntu:
  Incomplete
Status in mysql-5.7 package in Ubuntu:
  Incomplete

Bug description:
  Running on a Ubuntu 16.04.2 LTS
  install mysql through apt-get
  successfully run 'mysql' and connect
  add "tmpfs" to /etc/overlayroot.conf
  reboot the system to engage overlay
  attempt 'mysql' command and get a fail to connect to socket error
  this is repeatable by added and removing the overlay

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

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

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

2017-09-01 Thread Krzysztof Bytnerowicz

Public bug reported:

Software updater

ProblemType: Package
DistroRelease: Ubuntu 17.04
Package: linux-image-4.10.0-33-generic (not installed)
ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
Uname: Linux 4.10.0-19-generic i686
AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.10.0-19-generic.
ApportVersion: 2.20.4-0ubuntu4.5
Architecture: i386
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  krzysztof   1439 F pulseaudio
Card0.Amixer.info:
 Card hw:0 'I82801DBICH4'/'Intel 82801DB-ICH4 with AD1981B at irq 11'
   Mixer name   : 'Analog Devices AD1981B'
   Components   : 'AC97a:41445374'
   Controls  : 27
   Simple ctrls  : 18
Card29.Amixer.info:
 Card hw:29 'ThinkPadEC'/'ThinkPad Console Audio Control at EC reg 0x30, fw 
1RHT71WW-3.04'
   Mixer name   : 'ThinkPad EC 1RHT71WW-3.04'
   Components   : ''
   Controls  : 2
   Simple ctrls  : 1
Card29.Amixer.values:
 Simple mixer control 'Console',0
   Capabilities: pvolume pvolume-joined pswitch pswitch-joined
   Playback channels: Mono
   Limits: Playback 0 - 14
   Mono: Playback 6 [43%] [on]
Date: Fri Sep  1 19:45:12 2017
DuplicateSignature:
 package:linux-image-4.10.0-33-generic:(not installed)
 Preparing to unpack .../70-linux-image-4.10.0-33-generic_4.10.0-33.37_i386.deb 
...
 This kernel does not support a non-PAE CPU.
 dpkg: error processing archive 
/tmp/apt-dpkg-install-ak6tb9/70-linux-image-4.10.0-33-generic_4.10.0-33.37_i386.deb
 (--unpack):
  subprocess new pre-installation script returned error exit status 1
ErrorMessage: subprocess new pre-installation script returned error exit status 
1
HibernationDevice: RESUME=UUID=510d28f0-e291-49b2-aeeb-59d71d93eaad
InstallationDate: Installed on 2017-09-01 (0 days ago)
InstallationMedia: Lubuntu 17.04 "Zesty Zapus" - Release i386 (20170412)
MachineType: IBM 2373BM0
PccardctlIdent:
 Socket 0:
   no product info available
 Socket 1:
   no product info available
PccardctlStatus:
 Socket 0:
   no card
 Socket 1:
   no card
ProcFB: 0 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-19-generic 
root=UUID=2a98691a-5408-497e-a398-f808b0cedbed ro quiet splash vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions: grub-pc 2.02~beta3-4ubuntu2.2
RfKill:
 0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
SourcePackage: linux
Title: package linux-image-4.10.0-33-generic (not installed) failed to 
install/upgrade: subprocess new pre-installation script returned error exit 
status 1
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/18/2007
dmi.bios.vendor: IBM
dmi.bios.version: 1RETDRWW (3.23 )
dmi.board.name: 2373BM0
dmi.board.vendor: IBM
dmi.board.version: Not Available
dmi.chassis.asset.tag: N8206
dmi.chassis.type: 10
dmi.chassis.vendor: IBM
dmi.chassis.version: Not Available
dmi.modalias: 
dmi:bvnIBM:bvr1RETDRWW(3.23):bd06/18/2007:svnIBM:pn2373BM0:pvrThinkPadT41:rvnIBM:rn2373BM0:rvrNotAvailable:cvnIBM:ct10:cvrNotAvailable:
dmi.product.name: 2373BM0
dmi.product.version: ThinkPad T41
dmi.sys.vendor: IBM

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


** Tags: apport-package i386 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/1714464

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

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Software updater

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-33-generic (not installed)
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic i686
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.10.0-19-generic.
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  krzysztof   1439 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'I82801DBICH4'/'Intel 82801DB-ICH4 with AD1981B at irq 11'
 Mixer name : 'Analog Devices AD1981B'
 Components : 'AC97a:41445374'
 Controls  : 27
 Simple ctrls  : 18
  Card29.Amixer.info:
   Card hw:29 'ThinkPadEC'/'ThinkPad Console Audio Control at EC reg 0x30, fw 
1RHT71WW-3.04'
 Mixer name : 'ThinkPad EC 1RHT71WW-3.04'
 Components : ''
 Controls  : 2
 Simple ctrls  : 1
  Card29.Amixer.values:
   Simple mixer control 'Console',0
 Capabilities: pvolume pvolume-joined pswitch pswitch-joined
 Playback channels: Mono
 Limits: Playback 0 - 14
 Mono: Playback 6 [43%] [on]
  Date: Fri Sep  1 19:45:12 2017
  DuplicateSignature:
   package:linux-image-4.10.0-33-generic:(not installed)
   Preparing to unpack 
.../70-linux-image-4

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

2017-09-01 Thread Ubuntu Kernel Bot

This change was made by a bot.

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

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

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

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Software updater

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-33-generic (not installed)
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic i686
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.10.0-19-generic.
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  krzysztof   1439 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'I82801DBICH4'/'Intel 82801DB-ICH4 with AD1981B at irq 11'
 Mixer name : 'Analog Devices AD1981B'
 Components : 'AC97a:41445374'
 Controls  : 27
 Simple ctrls  : 18
  Card29.Amixer.info:
   Card hw:29 'ThinkPadEC'/'ThinkPad Console Audio Control at EC reg 0x30, fw 
1RHT71WW-3.04'
 Mixer name : 'ThinkPad EC 1RHT71WW-3.04'
 Components : ''
 Controls  : 2
 Simple ctrls  : 1
  Card29.Amixer.values:
   Simple mixer control 'Console',0
 Capabilities: pvolume pvolume-joined pswitch pswitch-joined
 Playback channels: Mono
 Limits: Playback 0 - 14
 Mono: Playback 6 [43%] [on]
  Date: Fri Sep  1 19:45:12 2017
  DuplicateSignature:
   package:linux-image-4.10.0-33-generic:(not installed)
   Preparing to unpack 
.../70-linux-image-4.10.0-33-generic_4.10.0-33.37_i386.deb ...
   This kernel does not support a non-PAE CPU.
   dpkg: error processing archive 
/tmp/apt-dpkg-install-ak6tb9/70-linux-image-4.10.0-33-generic_4.10.0-33.37_i386.deb
 (--unpack):
subprocess new pre-installation script returned error exit status 1
  ErrorMessage: subprocess new pre-installation script returned error exit 
status 1
  HibernationDevice: RESUME=UUID=510d28f0-e291-49b2-aeeb-59d71d93eaad
  InstallationDate: Installed on 2017-09-01 (0 days ago)
  InstallationMedia: Lubuntu 17.04 "Zesty Zapus" - Release i386 (20170412)
  MachineType: IBM 2373BM0
  PccardctlIdent:
   Socket 0:
 no product info available
   Socket 1:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
   Socket 1:
 no card
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-19-generic 
root=UUID=2a98691a-5408-497e-a398-f808b0cedbed ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc 2.02~beta3-4ubuntu2.2
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  Title: package linux-image-4.10.0-33-generic (not installed) failed to 
install/upgrade: subprocess new pre-installation script returned error exit 
status 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/18/2007
  dmi.bios.vendor: IBM
  dmi.bios.version: 1RETDRWW (3.23 )
  dmi.board.name: 2373BM0
  dmi.board.vendor: IBM
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: N8206
  dmi.chassis.type: 10
  dmi.chassis.vendor: IBM
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnIBM:bvr1RETDRWW(3.23):bd06/18/2007:svnIBM:pn2373BM0:pvrThinkPadT41:rvnIBM:rn2373BM0:rvrNotAvailable:cvnIBM:ct10:cvrNotAvailable:
  dmi.product.name: 2373BM0
  dmi.product.version: ThinkPad T41
  dmi.sys.vendor: IBM

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

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

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

2017-09-01 Thread Apport retracing service

** Tags removed: need-duplicate-check

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

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

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Software updater

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-33-generic (not installed)
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic i686
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.10.0-19-generic.
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  krzysztof   1439 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'I82801DBICH4'/'Intel 82801DB-ICH4 with AD1981B at irq 11'
 Mixer name : 'Analog Devices AD1981B'
 Components : 'AC97a:41445374'
 Controls  : 27
 Simple ctrls  : 18
  Card29.Amixer.info:
   Card hw:29 'ThinkPadEC'/'ThinkPad Console Audio Control at EC reg 0x30, fw 
1RHT71WW-3.04'
 Mixer name : 'ThinkPad EC 1RHT71WW-3.04'
 Components : ''
 Controls  : 2
 Simple ctrls  : 1
  Card29.Amixer.values:
   Simple mixer control 'Console',0
 Capabilities: pvolume pvolume-joined pswitch pswitch-joined
 Playback channels: Mono
 Limits: Playback 0 - 14
 Mono: Playback 6 [43%] [on]
  Date: Fri Sep  1 19:45:12 2017
  DuplicateSignature:
   package:linux-image-4.10.0-33-generic:(not installed)
   Preparing to unpack 
.../70-linux-image-4.10.0-33-generic_4.10.0-33.37_i386.deb ...
   This kernel does not support a non-PAE CPU.
   dpkg: error processing archive 
/tmp/apt-dpkg-install-ak6tb9/70-linux-image-4.10.0-33-generic_4.10.0-33.37_i386.deb
 (--unpack):
subprocess new pre-installation script returned error exit status 1
  ErrorMessage: subprocess new pre-installation script returned error exit 
status 1
  HibernationDevice: RESUME=UUID=510d28f0-e291-49b2-aeeb-59d71d93eaad
  InstallationDate: Installed on 2017-09-01 (0 days ago)
  InstallationMedia: Lubuntu 17.04 "Zesty Zapus" - Release i386 (20170412)
  MachineType: IBM 2373BM0
  PccardctlIdent:
   Socket 0:
 no product info available
   Socket 1:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
   Socket 1:
 no card
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-19-generic 
root=UUID=2a98691a-5408-497e-a398-f808b0cedbed ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc 2.02~beta3-4ubuntu2.2
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  Title: package linux-image-4.10.0-33-generic (not installed) failed to 
install/upgrade: subprocess new pre-installation script returned error exit 
status 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/18/2007
  dmi.bios.vendor: IBM
  dmi.bios.version: 1RETDRWW (3.23 )
  dmi.board.name: 2373BM0
  dmi.board.vendor: IBM
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: N8206
  dmi.chassis.type: 10
  dmi.chassis.vendor: IBM
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnIBM:bvr1RETDRWW(3.23):bd06/18/2007:svnIBM:pn2373BM0:pvrThinkPadT41:rvnIBM:rn2373BM0:rvrNotAvailable:cvnIBM:ct10:cvrNotAvailable:
  dmi.product.name: 2373BM0
  dmi.product.version: ThinkPad T41
  dmi.sys.vendor: IBM

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

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

[Kernel-packages] [Bug 1703339] Re: Unable to install Ubuntu on the NVMe disk under VMD PCI domain

2017-09-01 Thread Tomasz Majchrzak

Has the change been applied to Ubuntu Server? It still doesn't seem to
be working there.

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

Title:
  Unable to install Ubuntu on the NVMe disk under VMD PCI domain

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

Bug description:
  It is not possible to install Ubuntu on the NVMe disk under VMD
  (Volume Management Device) PCI domain. The disk is not visible in the
  installer because VMD module is not available at this stage.

  I'm raising it against kernel package as I have impression VMD module
  must be included in linux-image dpkg package, not linux-image-extra.

  Please also assure VMD module gets included in initramfs by installer
  (if necessary).

  For more information about VMD please see bug 1591806.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-generic 4.10.0.26.28
  ProcVersionSignature: Ubuntu 4.10.0-26.30-generic 4.10.17
  Uname: Linux 4.10.0-26-generic x86_64
  ApportVersion: 2.20.5-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   tomasz 1659 F...m pulseaudio
   /dev/snd/controlC0:  tomasz 1659 F pulseaudio
   /dev/snd/timer:  tomasz 1659 f pulseaudio
  CurrentDesktop: GNOME
  Date: Mon Jul 10 10:40:20 2017
  HibernationDevice: RESUME=/dev/mapper/ubuntu--vg-swap_1
  InstallationDate: Installed on 2017-07-06 (3 days ago)
  InstallationMedia: Ubuntu-Server 17.10 "Artful Aardvark" - Alpha amd64 
(20170702)
  IwConfig:
   lono wireless extensions.
   
   enp0s3no wireless extensions.
  Lsusb:
   Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet
   Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: innotek GmbH VirtualBox
  ProcFB: 0 vboxdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-26-generic 
root=/dev/mapper/hostname--vg-root ro
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-26-generic N/A
   linux-backports-modules-4.10.0-26-generic  N/A
   linux-firmware 1.167
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH

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

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

[Kernel-packages] [Bug 1686099] Re: connection flood to port 445 on mounting cifs volume under kernel

2017-09-01 Thread Marat Khalili

Hello, is it going to appear in 4.4? I'm getting tired of running
4.4.0-66 (jk works ok but still would prefer to update).

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

Title:
  connection flood to port 445 on mounting cifs volume under kernel

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

Bug description:
  This is identical to the bug reported on the Debian kernel list, only
  I'm running 4.4.0, not 4.[89].0

  After about 15 mintues, the cifsd daemon starts flooding echo requests
  on port 445 to the windows server causing a constant 1MB/s load
  (around 10,000 packets per second) that eventually leads to system
  instability that forces a reboot to correct.  This is repeatable and
  as far as I know started about a week ago (possibly with the
  installation of 4.4.0-75).

  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=856843

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

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

[Kernel-packages] [Bug 1714485] [NEW] Ubuntu 16.04.03: kdump fails with error "kdump-tools[1532]: /etc/init.d/kdump-tools: 26: [: -ne: unexpected operator" when / file system is xfs.

You have been subscribed to a public bug:

== Comment: #0 - PAVITHRA R. PRAKASH <> - 2017-08-31 00:33:37 ==
---Problem Description---

Ubuntu 16.04.03: kdump fails with error "kdump-tools[1532]: /etc/init.d
/kdump-tools: 26: [: -ne: unexpected operator" when / file system is
xfs.

---Steps to Reproduce---

1. Install Ubuntu 16.04.03 with / as xfs.
2. Configure kdump.
3. trigger crash.

Machine hangs after below log. Attaching console log.

[  OK  ] Reached target Network is Online.
 Starting Kernel crash dump capture service...
 Starting iSCSI initiator daemon (iscsid)...
[   12.263089] kdump-tools[1205]: /etc/init.d/kdump-tools: 26: [: -ne: 
unexpected operator
[  OK  ] Started Kernel crash dump capture service.
[  OK  ] Started iSCSI initiator daemon (iscsid).
 Starting Login to default iSCSI targets...
[  OK  ] Started Login to default iSCSI targets.
[  OK  ] Reached target Remote File Systems (Pre).


4. After manual reboot  /etc/default/kdump-tools is empty.

** Affects: makedumpfile (Ubuntu)
 Importance: Undecided
 Assignee: Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage)
 Status: New


** Tags: architecture-ppc64le bugnameltc-158164 severity-high 
targetmilestone-inin---
-- 
Ubuntu 16.04.03: kdump fails with error "kdump-tools[1532]: 
/etc/init.d/kdump-tools: 26: [: -ne: unexpected operator" when / file system is 
xfs.
https://bugs.launchpad.net/bugs/1714485
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to makedumpfile 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 1714485] sosreport

Default Comment by Bridge

** Attachment added: "sosreport"
   
https://bugs.launchpad.net/bugs/1714485/+attachment/4942321/+files/sosreport-120450-20170901054352.tar.xz

** Changed in: ubuntu
 Assignee: (unassigned) => Ubuntu on IBM Power Systems Bug Triage 
(ubuntu-power-triage)

** Package changed: ubuntu => makedumpfile (Ubuntu)

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

Title:
  Ubuntu 16.04.03: kdump fails with error "kdump-tools[1532]:
  /etc/init.d/kdump-tools: 26: [: -ne: unexpected operator" when / file
  system is xfs.

Status in makedumpfile package in Ubuntu:
  New

Bug description:
  == Comment: #0 - PAVITHRA R. PRAKASH <> - 2017-08-31 00:33:37 ==
  ---Problem Description---

  Ubuntu 16.04.03: kdump fails with error "kdump-tools[1532]:
  /etc/init.d/kdump-tools: 26: [: -ne: unexpected operator" when / file
  system is xfs.

  ---Steps to Reproduce---

  1. Install Ubuntu 16.04.03 with / as xfs.
  2. Configure kdump.
  3. trigger crash.

  Machine hangs after below log. Attaching console log.

  [  OK  ] Reached target Network is Online.
   Starting Kernel crash dump capture service...
   Starting iSCSI initiator daemon (iscsid)...
  [   12.263089] kdump-tools[1205]: /etc/init.d/kdump-tools: 26: [: -ne: 
unexpected operator
  [  OK  ] Started Kernel crash dump capture service.
  [  OK  ] Started iSCSI initiator daemon (iscsid).
   Starting Login to default iSCSI targets...
  [  OK  ] Started Login to default iSCSI targets.
  [  OK  ] Reached target Remote File Systems (Pre).

  
  4. After manual reboot  /etc/default/kdump-tools is empty.

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

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

[Kernel-packages] [Bug 1714485] Re: Ubuntu 16.04.03: kdump fails with error "kdump-tools[1532]: /etc/init.d/kdump-tools: 26: [: -ne: unexpected operator" when / file system is xfs.

2017-09-01 Thread Andrew Cloke

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

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

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

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

Title:
  Ubuntu 16.04.03: kdump fails with error "kdump-tools[1532]:
  /etc/init.d/kdump-tools: 26: [: -ne: unexpected operator" when / file
  system is xfs.

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

Bug description:
  == Comment: #0 - PAVITHRA R. PRAKASH <> - 2017-08-31 00:33:37 ==
  ---Problem Description---

  Ubuntu 16.04.03: kdump fails with error "kdump-tools[1532]:
  /etc/init.d/kdump-tools: 26: [: -ne: unexpected operator" when / file
  system is xfs.

  ---Steps to Reproduce---

  1. Install Ubuntu 16.04.03 with / as xfs.
  2. Configure kdump.
  3. trigger crash.

  Machine hangs after below log. Attaching console log.

  [  OK  ] Reached target Network is Online.
   Starting Kernel crash dump capture service...
   Starting iSCSI initiator daemon (iscsid)...
  [   12.263089] kdump-tools[1205]: /etc/init.d/kdump-tools: 26: [: -ne: 
unexpected operator
  [  OK  ] Started Kernel crash dump capture service.
  [  OK  ] Started iSCSI initiator daemon (iscsid).
   Starting Login to default iSCSI targets...
  [  OK  ] Started Login to default iSCSI targets.
  [  OK  ] Reached target Remote File Systems (Pre).

  
  4. After manual reboot  /etc/default/kdump-tools is empty.

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

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

[Kernel-packages] [Bug 1703339] Re: Unable to install Ubuntu on the NVMe disk under VMD PCI domain

2017-09-01 Thread Seth Forshee

Are you testing artful? I just confirmed that vmd.ko is included in the
main kernel package in 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/1703339

Title:
  Unable to install Ubuntu on the NVMe disk under VMD PCI domain

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

Bug description:
  It is not possible to install Ubuntu on the NVMe disk under VMD
  (Volume Management Device) PCI domain. The disk is not visible in the
  installer because VMD module is not available at this stage.

  I'm raising it against kernel package as I have impression VMD module
  must be included in linux-image dpkg package, not linux-image-extra.

  Please also assure VMD module gets included in initramfs by installer
  (if necessary).

  For more information about VMD please see bug 1591806.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-generic 4.10.0.26.28
  ProcVersionSignature: Ubuntu 4.10.0-26.30-generic 4.10.17
  Uname: Linux 4.10.0-26-generic x86_64
  ApportVersion: 2.20.5-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   tomasz 1659 F...m pulseaudio
   /dev/snd/controlC0:  tomasz 1659 F pulseaudio
   /dev/snd/timer:  tomasz 1659 f pulseaudio
  CurrentDesktop: GNOME
  Date: Mon Jul 10 10:40:20 2017
  HibernationDevice: RESUME=/dev/mapper/ubuntu--vg-swap_1
  InstallationDate: Installed on 2017-07-06 (3 days ago)
  InstallationMedia: Ubuntu-Server 17.10 "Artful Aardvark" - Alpha amd64 
(20170702)
  IwConfig:
   lono wireless extensions.
   
   enp0s3no wireless extensions.
  Lsusb:
   Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet
   Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: innotek GmbH VirtualBox
  ProcFB: 0 vboxdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-26-generic 
root=/dev/mapper/hostname--vg-root ro
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-26-generic N/A
   linux-backports-modules-4.10.0-26-generic  N/A
   linux-firmware 1.167
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH

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

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

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

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

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

Title:
  linux: 4.10.0-34.38 -proposed tracker

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

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

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

  backports: 1713471,1713472
  derivatives: 1713473
  -- swm properties --
  boot-testing-requested: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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

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

** 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-vivid in Ubuntu.
https://bugs.launchpad.net/bugs/1713461

Title:
  linux-lts-vivid:  -proposed tracker

Status in Kernel SRU Workflow:
  Invalid
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:
  Invalid
Status in Kernel SRU Workflow prepare-package-meta series:
  Invalid
Status in Kernel SRU Workflow prepare-package-signed series:
  Invalid
Status in Kernel SRU Workflow promote-to-proposed series:
  Invalid
Status in Kernel SRU Workflow promote-to-security series:
  Invalid
Status in Kernel SRU Workflow promote-to-updates series:
  Invalid
Status in Kernel SRU Workflow regression-testing series:
  Invalid
Status in Kernel SRU Workflow security-signoff series:
  Invalid
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Invalid
Status in linux-lts-vivid package in Ubuntu:
  Invalid
Status in linux-lts-vivid source package in Trusty:
  Invalid

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

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

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

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

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

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

Title:
  linux:  -proposed tracker

Status in Kernel SRU Workflow:
  Invalid
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:
  Invalid
Status in Kernel SRU Workflow prepare-package-meta series:
  Invalid
Status in Kernel SRU Workflow prepare-package-signed series:
  Invalid
Status in Kernel SRU Workflow promote-to-proposed series:
  Invalid
Status in Kernel SRU Workflow promote-to-security series:
  Invalid
Status in Kernel SRU Workflow promote-to-updates series:
  Invalid
Status in Kernel SRU Workflow regression-testing series:
  Invalid
Status in Kernel SRU Workflow security-signoff series:
  Invalid
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Invalid
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Vivid:
  Invalid

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

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

  backports: 1713461
  derivatives:

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

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

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

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

Title:
  linux:  -proposed tracker

Status in Kernel SRU Workflow:
  Invalid
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:
  Invalid
Status in Kernel SRU Workflow prepare-package-lbm series:
  Invalid
Status in Kernel SRU Workflow prepare-package-meta series:
  Invalid
Status in Kernel SRU Workflow promote-to-proposed series:
  Invalid
Status in Kernel SRU Workflow promote-to-security series:
  Invalid
Status in Kernel SRU Workflow promote-to-updates series:
  Invalid
Status in Kernel SRU Workflow regression-testing series:
  Invalid
Status in Kernel SRU Workflow security-signoff series:
  Invalid
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Invalid
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Precise:
  Invalid

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

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

  backports: 
  derivatives:

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

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

[Kernel-packages] [Bug 1700972] Re: Please only recommend or suggest initramfs-tools | linux-initramfs-tool for kernels able to boot without initramfs

2017-09-01 Thread Marcelo Cerri

** Tags removed: verification-needed-trusty verification-needed-xenial 
verification-needed-zesty
** Tags added: verification-done-trusty verification-done-xenial 
verification-done-zesty

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

Title:
  Please only recommend or suggest initramfs-tools | linux-initramfs-
  tool for kernels able to boot without initramfs

Status in linux package in Ubuntu:
  Fix Released
Status in linux-aws package in Ubuntu:
  Fix Committed
Status in linux-azure package in Ubuntu:
  Fix Committed
Status in linux-gke package in Ubuntu:
  Fix Committed
Status in linux source package in Trusty:
  Fix Committed
Status in linux source package in Xenial:
  Fix Committed
Status in linux-aws source package in Xenial:
  Fix Committed
Status in linux-azure source package in Xenial:
  Fix Committed
Status in linux-gke source package in Xenial:
  Fix Committed
Status in linux source package in Zesty:
  Fix Committed
Status in linux source package in Artful:
  Fix Released

Bug description:
  Linux kernel packages depend on initramfs-tools | linux-initramfs-
  tool, even when systems using the kernel can be booted without it.

  Demoting the dependency to Recommends: or Suggests: would allow
  creating smaller images without initramfs-tools installed and fully
  skipping initramfs updates upon kernel updates saving time.

  Please consider changing the Depends: to Recommends: or Suggests: for
  kernels capable of booting without initramfs.

  initramfs-tools is still a dependency of ubuntu-minimal thus
  accidental removal of initramfs-tools resulting an unbootable system
  would still be unlikely.

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

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

[Kernel-packages] [Bug 1653597] Re: libhugetlbfs test suite failed with brk_near_huge test on GCE with 4.8.0-34.36

2017-09-01 Thread Marcelo Cerri

** Also affects: linux-azure (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/1653597

Title:
  libhugetlbfs test suite failed with brk_near_huge test on GCE with
  4.8.0-34.36

Status in linux package in Ubuntu:
  Confirmed
Status in linux-azure package in Ubuntu:
  New

Bug description:
  Kernel: 4.8.0-34.36

  The libhugetlbfs failed with the brk_near_huge test on x86_64(gce)

  12/24 04:59:42 DEBUG| utils:0153| [stdout] truncate_above_4GB (2M: 64): PASS
  12/24 04:59:42 ERROR| utils:0153| [stderr] brk_near_huge: malloc.c:2403: 
sysmalloc: Assertion `(old_top == initial_top (av) && old_size == 0) || 
((unsigned long) (old_size) >= MINSIZE && prev_inuse (old_top) && ((unsigned 
long) old_end & (pagesize - 1)) == 0)' failed.
  12/24 04:59:42 DEBUG| utils:0153| [stdout] brk_near_huge (2M: 64):
  12/24 04:59:42 DEBUG| utils:0153| [stdout] task-size-overrun (2M: 64): PASS

  Full log: http://pastebin.ubuntu.com/23732201/

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

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

[Kernel-packages] [Bug 1711368] Re: Artful update to v4.12.8 stable release

This bug was fixed in the package linux - 4.12.0-12.13

---
linux (4.12.0-12.13) artful; urgency=low

  * Artful update to v4.12.8 stable release (LP: #1711368)
- mm: ratelimit PFNs busy info message
- mm: fix list corruptions on shmem shrinklist
- futex: Remove unnecessary warning from get_futex_key
- xtensa: fix cache aliasing handling code for WT cache
- xtensa: mm/cache: add missing EXPORT_SYMBOLs
- xtensa: don't limit csum_partial export by CONFIG_NET
- xfs: Fix leak of discard bio
- pinctrl: armada-37xx: Fix number of pin in south bridge
- mtd: nand: atmel: Fix DT backward compatibility in pmecc.c
- mtd: nand: Fix timing setup for NANDs that do not support SET FEATURES
- mtd: nand: Declare tBERS, tR and tPROG as u64 to avoid integer overflow
- iscsi-target: fix memory leak in iscsit_setup_text_cmd()
- iscsi-target: Fix iscsi_np reset hung task during parallel delete
- usb-storage: fix deadlock involving host lock and scsi_done
- target: Fix node_acl demo-mode + uncached dynamic shutdown regression
- fuse: initialize the flock flag in fuse_file on allocation
- i2c: designware: Some broken DSTDs use 1MiHz instead of 1MHz
- nand: fix wrong default oob layout for small pages using soft ecc
- mmc: mmc: correct the logic for setting HS400ES signal voltage
- nfs/flexfiles: fix leak of nfs4_ff_ds_version arrays
- drm/bridge: tc358767: fix probe without attached output node
- drm/etnaviv: Fix off-by-one error in reloc checking
- drm/i915: Fix out-of-bounds array access in bdw_load_gamma_lut
- USB: serial: option: add D-Link DWM-222 device ID
- USB: serial: cp210x: add support for Qivicon USB ZigBee dongle
- USB: serial: pl2303: add new ATEN device id
- usb: musb: fix tx fifo flush handling again
- USB: hcd: Mark secondary HCD as dead if the primary one died
- staging:iio:resolver:ad2s1210 fix negative IIO_ANGL_VEL read
- iio: aspeed-adc: wait for initial sequence.
- iio: accel: st_accel: add SPI-3wire support
- iio: accel: bmc150: Always restore device to normal mode after suspend-
  resume
- iio: pressure: st_pressure_core: disable multiread by default for LPS22HB
- iio: light: tsl2563: use correct event code
- iio: adc: Revert "axp288: Drop bogus AXP288_ADC_TS_PIN_CTRL register
  modifications"
- staging: comedi: comedi_fops: do not call blocking ops when !TASK_RUNNING
- uas: Add US_FL_IGNORE_RESIDUE for Initio Corporation INIC-3069
- firmware: fix batched requests - wake all waiters
- firmware: fix batched requests - send wake up on failure on direct lookups
- firmware: avoid invalid fallback aborts by using killable wait
- block: Make blk_mq_delay_kick_requeue_list() rerun the queue at a quiet 
time
- usb: gadget: udc: renesas_usb3: Fix usb_gadget_giveback_request() calling
- usb: renesas_usbhs: Fix UGCTRL2 value for R-Car Gen3
- USB: Check for dropped connection before switching to full speed
- usb: core: unlink urbs from the tail of the endpoint's urb_list
- usb: quirks: Add no-lpm quirk for Moshi USB to Ethernet Adapter
- usb:xhci:Add quirk for Certain failing HP keyboard on reset after resume
- PCI: Protect pci_error_handlers->reset_notify() usage with device_lock()
- PCI: Remove __pci_dev_reset() and pci_dev_reset()
- PCI: Add pci_reset_function_locked()
- xhci: Reset Renesas uPD72020x USB controller for 32-bit DMA issue
- iio: adc: vf610_adc: Fix VALT selection value for REFSEL bits
- pnfs/blocklayout: require 64-bit sector_t
- pinctrl: cherryview: Add Setzer models to the Chromebook DMI quirk
- pinctrl: sunxi: add a missing function of A10/A20 pinctrl driver
- pinctrl: intel: merrifield: Correct UART pin lists
- pinctrl: uniphier: fix WARN_ON() of pingroups dump on LD11
- pinctrl: uniphier: fix WARN_ON() of pingroups dump on LD20
- pinctrl: samsung: Remove bogus irq_[un]mask from resource management
- pinctrl: meson-gxbb: Add missing GPIODV_18 pin entry
- pinctrl: meson-gxl: Add missing GPIODV_18 pin entry
- MIPS: DEC: Fix an int-handler.S CPU_DADDI_WORKAROUNDS regression
- Revert "MIPS: Don't unnecessarily include kmalloc.h into ."
- MIPS: Octeon: Fix broken EDAC driver.
- Linux 4.12.8

  * Artful: 4.12.0-11.12: Boot panic in vlv2_plat_configure_clock+0x3b/0xa0
(LP: #1711298)
- [Config] CONFIG_INTEL_ATOMISP=n

  * ACPI ID for Hip07/08 I2C controller has typo (LP: #1711182)
- ACPI: APD: Fix HID for Hisilicon Hip07/08

  * Ubuntu17.10 - perf: Update Power9 PMU event JSON files (LP: #1708630)
- perf pmu-events: Support additional POWER8+ PVR in mapfile
- perf vendor events: Add POWER9 PMU events
- perf vendor events: Add POWER9 PVRs to mapfile
- SAUCE: perf vendor events powerpc: remove suffix in mapfile
- SAUCE: perf vendor events powerpc: Update POWER9 events

  * Disable CONFIG_MEMORY_HOTPLU

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

This bug was fixed in the package linux - 4.12.0-12.13

---
linux (4.12.0-12.13) artful; urgency=low

  * Artful update to v4.12.8 stable release (LP: #1711368)
- mm: ratelimit PFNs busy info message
- mm: fix list corruptions on shmem shrinklist
- futex: Remove unnecessary warning from get_futex_key
- xtensa: fix cache aliasing handling code for WT cache
- xtensa: mm/cache: add missing EXPORT_SYMBOLs
- xtensa: don't limit csum_partial export by CONFIG_NET
- xfs: Fix leak of discard bio
- pinctrl: armada-37xx: Fix number of pin in south bridge
- mtd: nand: atmel: Fix DT backward compatibility in pmecc.c
- mtd: nand: Fix timing setup for NANDs that do not support SET FEATURES
- mtd: nand: Declare tBERS, tR and tPROG as u64 to avoid integer overflow
- iscsi-target: fix memory leak in iscsit_setup_text_cmd()
- iscsi-target: Fix iscsi_np reset hung task during parallel delete
- usb-storage: fix deadlock involving host lock and scsi_done
- target: Fix node_acl demo-mode + uncached dynamic shutdown regression
- fuse: initialize the flock flag in fuse_file on allocation
- i2c: designware: Some broken DSTDs use 1MiHz instead of 1MHz
- nand: fix wrong default oob layout for small pages using soft ecc
- mmc: mmc: correct the logic for setting HS400ES signal voltage
- nfs/flexfiles: fix leak of nfs4_ff_ds_version arrays
- drm/bridge: tc358767: fix probe without attached output node
- drm/etnaviv: Fix off-by-one error in reloc checking
- drm/i915: Fix out-of-bounds array access in bdw_load_gamma_lut
- USB: serial: option: add D-Link DWM-222 device ID
- USB: serial: cp210x: add support for Qivicon USB ZigBee dongle
- USB: serial: pl2303: add new ATEN device id
- usb: musb: fix tx fifo flush handling again
- USB: hcd: Mark secondary HCD as dead if the primary one died
- staging:iio:resolver:ad2s1210 fix negative IIO_ANGL_VEL read
- iio: aspeed-adc: wait for initial sequence.
- iio: accel: st_accel: add SPI-3wire support
- iio: accel: bmc150: Always restore device to normal mode after suspend-
  resume
- iio: pressure: st_pressure_core: disable multiread by default for LPS22HB
- iio: light: tsl2563: use correct event code
- iio: adc: Revert "axp288: Drop bogus AXP288_ADC_TS_PIN_CTRL register
  modifications"
- staging: comedi: comedi_fops: do not call blocking ops when !TASK_RUNNING
- uas: Add US_FL_IGNORE_RESIDUE for Initio Corporation INIC-3069
- firmware: fix batched requests - wake all waiters
- firmware: fix batched requests - send wake up on failure on direct lookups
- firmware: avoid invalid fallback aborts by using killable wait
- block: Make blk_mq_delay_kick_requeue_list() rerun the queue at a quiet 
time
- usb: gadget: udc: renesas_usb3: Fix usb_gadget_giveback_request() calling
- usb: renesas_usbhs: Fix UGCTRL2 value for R-Car Gen3
- USB: Check for dropped connection before switching to full speed
- usb: core: unlink urbs from the tail of the endpoint's urb_list
- usb: quirks: Add no-lpm quirk for Moshi USB to Ethernet Adapter
- usb:xhci:Add quirk for Certain failing HP keyboard on reset after resume
- PCI: Protect pci_error_handlers->reset_notify() usage with device_lock()
- PCI: Remove __pci_dev_reset() and pci_dev_reset()
- PCI: Add pci_reset_function_locked()
- xhci: Reset Renesas uPD72020x USB controller for 32-bit DMA issue
- iio: adc: vf610_adc: Fix VALT selection value for REFSEL bits
- pnfs/blocklayout: require 64-bit sector_t
- pinctrl: cherryview: Add Setzer models to the Chromebook DMI quirk
- pinctrl: sunxi: add a missing function of A10/A20 pinctrl driver
- pinctrl: intel: merrifield: Correct UART pin lists
- pinctrl: uniphier: fix WARN_ON() of pingroups dump on LD11
- pinctrl: uniphier: fix WARN_ON() of pingroups dump on LD20
- pinctrl: samsung: Remove bogus irq_[un]mask from resource management
- pinctrl: meson-gxbb: Add missing GPIODV_18 pin entry
- pinctrl: meson-gxl: Add missing GPIODV_18 pin entry
- MIPS: DEC: Fix an int-handler.S CPU_DADDI_WORKAROUNDS regression
- Revert "MIPS: Don't unnecessarily include kmalloc.h into ."
- MIPS: Octeon: Fix broken EDAC driver.
- Linux 4.12.8

  * Artful: 4.12.0-11.12: Boot panic in vlv2_plat_configure_clock+0x3b/0xa0
(LP: #1711298)
- [Config] CONFIG_INTEL_ATOMISP=n

  * ACPI ID for Hip07/08 I2C controller has typo (LP: #1711182)
- ACPI: APD: Fix HID for Hisilicon Hip07/08

  * Ubuntu17.10 - perf: Update Power9 PMU event JSON files (LP: #1708630)
- perf pmu-events: Support additional POWER8+ PVR in mapfile
- perf vendor events: Add POWER9 PMU events
- perf vendor events: Add POWER9 PVRs to mapfile
- SAUCE: perf vendor events powerpc: remove suffix in mapfile
- SAUCE: perf vendor events powerpc: Update POWER9 events

  * Disable CONFIG_MEMORY_HOTPLU

[Kernel-packages] [Bug 1710648] Re: Artful update to v4.12.6 stable release

This bug was fixed in the package linux - 4.12.0-12.13

---
linux (4.12.0-12.13) artful; urgency=low

  * Artful update to v4.12.8 stable release (LP: #1711368)
- mm: ratelimit PFNs busy info message
- mm: fix list corruptions on shmem shrinklist
- futex: Remove unnecessary warning from get_futex_key
- xtensa: fix cache aliasing handling code for WT cache
- xtensa: mm/cache: add missing EXPORT_SYMBOLs
- xtensa: don't limit csum_partial export by CONFIG_NET
- xfs: Fix leak of discard bio
- pinctrl: armada-37xx: Fix number of pin in south bridge
- mtd: nand: atmel: Fix DT backward compatibility in pmecc.c
- mtd: nand: Fix timing setup for NANDs that do not support SET FEATURES
- mtd: nand: Declare tBERS, tR and tPROG as u64 to avoid integer overflow
- iscsi-target: fix memory leak in iscsit_setup_text_cmd()
- iscsi-target: Fix iscsi_np reset hung task during parallel delete
- usb-storage: fix deadlock involving host lock and scsi_done
- target: Fix node_acl demo-mode + uncached dynamic shutdown regression
- fuse: initialize the flock flag in fuse_file on allocation
- i2c: designware: Some broken DSTDs use 1MiHz instead of 1MHz
- nand: fix wrong default oob layout for small pages using soft ecc
- mmc: mmc: correct the logic for setting HS400ES signal voltage
- nfs/flexfiles: fix leak of nfs4_ff_ds_version arrays
- drm/bridge: tc358767: fix probe without attached output node
- drm/etnaviv: Fix off-by-one error in reloc checking
- drm/i915: Fix out-of-bounds array access in bdw_load_gamma_lut
- USB: serial: option: add D-Link DWM-222 device ID
- USB: serial: cp210x: add support for Qivicon USB ZigBee dongle
- USB: serial: pl2303: add new ATEN device id
- usb: musb: fix tx fifo flush handling again
- USB: hcd: Mark secondary HCD as dead if the primary one died
- staging:iio:resolver:ad2s1210 fix negative IIO_ANGL_VEL read
- iio: aspeed-adc: wait for initial sequence.
- iio: accel: st_accel: add SPI-3wire support
- iio: accel: bmc150: Always restore device to normal mode after suspend-
  resume
- iio: pressure: st_pressure_core: disable multiread by default for LPS22HB
- iio: light: tsl2563: use correct event code
- iio: adc: Revert "axp288: Drop bogus AXP288_ADC_TS_PIN_CTRL register
  modifications"
- staging: comedi: comedi_fops: do not call blocking ops when !TASK_RUNNING
- uas: Add US_FL_IGNORE_RESIDUE for Initio Corporation INIC-3069
- firmware: fix batched requests - wake all waiters
- firmware: fix batched requests - send wake up on failure on direct lookups
- firmware: avoid invalid fallback aborts by using killable wait
- block: Make blk_mq_delay_kick_requeue_list() rerun the queue at a quiet 
time
- usb: gadget: udc: renesas_usb3: Fix usb_gadget_giveback_request() calling
- usb: renesas_usbhs: Fix UGCTRL2 value for R-Car Gen3
- USB: Check for dropped connection before switching to full speed
- usb: core: unlink urbs from the tail of the endpoint's urb_list
- usb: quirks: Add no-lpm quirk for Moshi USB to Ethernet Adapter
- usb:xhci:Add quirk for Certain failing HP keyboard on reset after resume
- PCI: Protect pci_error_handlers->reset_notify() usage with device_lock()
- PCI: Remove __pci_dev_reset() and pci_dev_reset()
- PCI: Add pci_reset_function_locked()
- xhci: Reset Renesas uPD72020x USB controller for 32-bit DMA issue
- iio: adc: vf610_adc: Fix VALT selection value for REFSEL bits
- pnfs/blocklayout: require 64-bit sector_t
- pinctrl: cherryview: Add Setzer models to the Chromebook DMI quirk
- pinctrl: sunxi: add a missing function of A10/A20 pinctrl driver
- pinctrl: intel: merrifield: Correct UART pin lists
- pinctrl: uniphier: fix WARN_ON() of pingroups dump on LD11
- pinctrl: uniphier: fix WARN_ON() of pingroups dump on LD20
- pinctrl: samsung: Remove bogus irq_[un]mask from resource management
- pinctrl: meson-gxbb: Add missing GPIODV_18 pin entry
- pinctrl: meson-gxl: Add missing GPIODV_18 pin entry
- MIPS: DEC: Fix an int-handler.S CPU_DADDI_WORKAROUNDS regression
- Revert "MIPS: Don't unnecessarily include kmalloc.h into ."
- MIPS: Octeon: Fix broken EDAC driver.
- Linux 4.12.8

  * Artful: 4.12.0-11.12: Boot panic in vlv2_plat_configure_clock+0x3b/0xa0
(LP: #1711298)
- [Config] CONFIG_INTEL_ATOMISP=n

  * ACPI ID for Hip07/08 I2C controller has typo (LP: #1711182)
- ACPI: APD: Fix HID for Hisilicon Hip07/08

  * Ubuntu17.10 - perf: Update Power9 PMU event JSON files (LP: #1708630)
- perf pmu-events: Support additional POWER8+ PVR in mapfile
- perf vendor events: Add POWER9 PMU events
- perf vendor events: Add POWER9 PVRs to mapfile
- SAUCE: perf vendor events powerpc: remove suffix in mapfile
- SAUCE: perf vendor events powerpc: Update POWER9 events

  * Disable CONFIG_MEMORY_HOTPLU

[Kernel-packages] [Bug 1709171] Re: Disable CONFIG_MEMORY_HOTPLUG_DEFAULT_ONLINE

This bug was fixed in the package linux - 4.12.0-12.13

---
linux (4.12.0-12.13) artful; urgency=low

  * Artful update to v4.12.8 stable release (LP: #1711368)
- mm: ratelimit PFNs busy info message
- mm: fix list corruptions on shmem shrinklist
- futex: Remove unnecessary warning from get_futex_key
- xtensa: fix cache aliasing handling code for WT cache
- xtensa: mm/cache: add missing EXPORT_SYMBOLs
- xtensa: don't limit csum_partial export by CONFIG_NET
- xfs: Fix leak of discard bio
- pinctrl: armada-37xx: Fix number of pin in south bridge
- mtd: nand: atmel: Fix DT backward compatibility in pmecc.c
- mtd: nand: Fix timing setup for NANDs that do not support SET FEATURES
- mtd: nand: Declare tBERS, tR and tPROG as u64 to avoid integer overflow
- iscsi-target: fix memory leak in iscsit_setup_text_cmd()
- iscsi-target: Fix iscsi_np reset hung task during parallel delete
- usb-storage: fix deadlock involving host lock and scsi_done
- target: Fix node_acl demo-mode + uncached dynamic shutdown regression
- fuse: initialize the flock flag in fuse_file on allocation
- i2c: designware: Some broken DSTDs use 1MiHz instead of 1MHz
- nand: fix wrong default oob layout for small pages using soft ecc
- mmc: mmc: correct the logic for setting HS400ES signal voltage
- nfs/flexfiles: fix leak of nfs4_ff_ds_version arrays
- drm/bridge: tc358767: fix probe without attached output node
- drm/etnaviv: Fix off-by-one error in reloc checking
- drm/i915: Fix out-of-bounds array access in bdw_load_gamma_lut
- USB: serial: option: add D-Link DWM-222 device ID
- USB: serial: cp210x: add support for Qivicon USB ZigBee dongle
- USB: serial: pl2303: add new ATEN device id
- usb: musb: fix tx fifo flush handling again
- USB: hcd: Mark secondary HCD as dead if the primary one died
- staging:iio:resolver:ad2s1210 fix negative IIO_ANGL_VEL read
- iio: aspeed-adc: wait for initial sequence.
- iio: accel: st_accel: add SPI-3wire support
- iio: accel: bmc150: Always restore device to normal mode after suspend-
  resume
- iio: pressure: st_pressure_core: disable multiread by default for LPS22HB
- iio: light: tsl2563: use correct event code
- iio: adc: Revert "axp288: Drop bogus AXP288_ADC_TS_PIN_CTRL register
  modifications"
- staging: comedi: comedi_fops: do not call blocking ops when !TASK_RUNNING
- uas: Add US_FL_IGNORE_RESIDUE for Initio Corporation INIC-3069
- firmware: fix batched requests - wake all waiters
- firmware: fix batched requests - send wake up on failure on direct lookups
- firmware: avoid invalid fallback aborts by using killable wait
- block: Make blk_mq_delay_kick_requeue_list() rerun the queue at a quiet 
time
- usb: gadget: udc: renesas_usb3: Fix usb_gadget_giveback_request() calling
- usb: renesas_usbhs: Fix UGCTRL2 value for R-Car Gen3
- USB: Check for dropped connection before switching to full speed
- usb: core: unlink urbs from the tail of the endpoint's urb_list
- usb: quirks: Add no-lpm quirk for Moshi USB to Ethernet Adapter
- usb:xhci:Add quirk for Certain failing HP keyboard on reset after resume
- PCI: Protect pci_error_handlers->reset_notify() usage with device_lock()
- PCI: Remove __pci_dev_reset() and pci_dev_reset()
- PCI: Add pci_reset_function_locked()
- xhci: Reset Renesas uPD72020x USB controller for 32-bit DMA issue
- iio: adc: vf610_adc: Fix VALT selection value for REFSEL bits
- pnfs/blocklayout: require 64-bit sector_t
- pinctrl: cherryview: Add Setzer models to the Chromebook DMI quirk
- pinctrl: sunxi: add a missing function of A10/A20 pinctrl driver
- pinctrl: intel: merrifield: Correct UART pin lists
- pinctrl: uniphier: fix WARN_ON() of pingroups dump on LD11
- pinctrl: uniphier: fix WARN_ON() of pingroups dump on LD20
- pinctrl: samsung: Remove bogus irq_[un]mask from resource management
- pinctrl: meson-gxbb: Add missing GPIODV_18 pin entry
- pinctrl: meson-gxl: Add missing GPIODV_18 pin entry
- MIPS: DEC: Fix an int-handler.S CPU_DADDI_WORKAROUNDS regression
- Revert "MIPS: Don't unnecessarily include kmalloc.h into ."
- MIPS: Octeon: Fix broken EDAC driver.
- Linux 4.12.8

  * Artful: 4.12.0-11.12: Boot panic in vlv2_plat_configure_clock+0x3b/0xa0
(LP: #1711298)
- [Config] CONFIG_INTEL_ATOMISP=n

  * ACPI ID for Hip07/08 I2C controller has typo (LP: #1711182)
- ACPI: APD: Fix HID for Hisilicon Hip07/08

  * Ubuntu17.10 - perf: Update Power9 PMU event JSON files (LP: #1708630)
- perf pmu-events: Support additional POWER8+ PVR in mapfile
- perf vendor events: Add POWER9 PMU events
- perf vendor events: Add POWER9 PVRs to mapfile
- SAUCE: perf vendor events powerpc: remove suffix in mapfile
- SAUCE: perf vendor events powerpc: Update POWER9 events

  * Disable CONFIG_MEMORY_HOTPLU

[Kernel-packages] [Bug 1709352] Re: Avoid spurious PMU interrupts after idle

This bug was fixed in the package linux - 4.12.0-12.13

---
linux (4.12.0-12.13) artful; urgency=low

  * Artful update to v4.12.8 stable release (LP: #1711368)
- mm: ratelimit PFNs busy info message
- mm: fix list corruptions on shmem shrinklist
- futex: Remove unnecessary warning from get_futex_key
- xtensa: fix cache aliasing handling code for WT cache
- xtensa: mm/cache: add missing EXPORT_SYMBOLs
- xtensa: don't limit csum_partial export by CONFIG_NET
- xfs: Fix leak of discard bio
- pinctrl: armada-37xx: Fix number of pin in south bridge
- mtd: nand: atmel: Fix DT backward compatibility in pmecc.c
- mtd: nand: Fix timing setup for NANDs that do not support SET FEATURES
- mtd: nand: Declare tBERS, tR and tPROG as u64 to avoid integer overflow
- iscsi-target: fix memory leak in iscsit_setup_text_cmd()
- iscsi-target: Fix iscsi_np reset hung task during parallel delete
- usb-storage: fix deadlock involving host lock and scsi_done
- target: Fix node_acl demo-mode + uncached dynamic shutdown regression
- fuse: initialize the flock flag in fuse_file on allocation
- i2c: designware: Some broken DSTDs use 1MiHz instead of 1MHz
- nand: fix wrong default oob layout for small pages using soft ecc
- mmc: mmc: correct the logic for setting HS400ES signal voltage
- nfs/flexfiles: fix leak of nfs4_ff_ds_version arrays
- drm/bridge: tc358767: fix probe without attached output node
- drm/etnaviv: Fix off-by-one error in reloc checking
- drm/i915: Fix out-of-bounds array access in bdw_load_gamma_lut
- USB: serial: option: add D-Link DWM-222 device ID
- USB: serial: cp210x: add support for Qivicon USB ZigBee dongle
- USB: serial: pl2303: add new ATEN device id
- usb: musb: fix tx fifo flush handling again
- USB: hcd: Mark secondary HCD as dead if the primary one died
- staging:iio:resolver:ad2s1210 fix negative IIO_ANGL_VEL read
- iio: aspeed-adc: wait for initial sequence.
- iio: accel: st_accel: add SPI-3wire support
- iio: accel: bmc150: Always restore device to normal mode after suspend-
  resume
- iio: pressure: st_pressure_core: disable multiread by default for LPS22HB
- iio: light: tsl2563: use correct event code
- iio: adc: Revert "axp288: Drop bogus AXP288_ADC_TS_PIN_CTRL register
  modifications"
- staging: comedi: comedi_fops: do not call blocking ops when !TASK_RUNNING
- uas: Add US_FL_IGNORE_RESIDUE for Initio Corporation INIC-3069
- firmware: fix batched requests - wake all waiters
- firmware: fix batched requests - send wake up on failure on direct lookups
- firmware: avoid invalid fallback aborts by using killable wait
- block: Make blk_mq_delay_kick_requeue_list() rerun the queue at a quiet 
time
- usb: gadget: udc: renesas_usb3: Fix usb_gadget_giveback_request() calling
- usb: renesas_usbhs: Fix UGCTRL2 value for R-Car Gen3
- USB: Check for dropped connection before switching to full speed
- usb: core: unlink urbs from the tail of the endpoint's urb_list
- usb: quirks: Add no-lpm quirk for Moshi USB to Ethernet Adapter
- usb:xhci:Add quirk for Certain failing HP keyboard on reset after resume
- PCI: Protect pci_error_handlers->reset_notify() usage with device_lock()
- PCI: Remove __pci_dev_reset() and pci_dev_reset()
- PCI: Add pci_reset_function_locked()
- xhci: Reset Renesas uPD72020x USB controller for 32-bit DMA issue
- iio: adc: vf610_adc: Fix VALT selection value for REFSEL bits
- pnfs/blocklayout: require 64-bit sector_t
- pinctrl: cherryview: Add Setzer models to the Chromebook DMI quirk
- pinctrl: sunxi: add a missing function of A10/A20 pinctrl driver
- pinctrl: intel: merrifield: Correct UART pin lists
- pinctrl: uniphier: fix WARN_ON() of pingroups dump on LD11
- pinctrl: uniphier: fix WARN_ON() of pingroups dump on LD20
- pinctrl: samsung: Remove bogus irq_[un]mask from resource management
- pinctrl: meson-gxbb: Add missing GPIODV_18 pin entry
- pinctrl: meson-gxl: Add missing GPIODV_18 pin entry
- MIPS: DEC: Fix an int-handler.S CPU_DADDI_WORKAROUNDS regression
- Revert "MIPS: Don't unnecessarily include kmalloc.h into ."
- MIPS: Octeon: Fix broken EDAC driver.
- Linux 4.12.8

  * Artful: 4.12.0-11.12: Boot panic in vlv2_plat_configure_clock+0x3b/0xa0
(LP: #1711298)
- [Config] CONFIG_INTEL_ATOMISP=n

  * ACPI ID for Hip07/08 I2C controller has typo (LP: #1711182)
- ACPI: APD: Fix HID for Hisilicon Hip07/08

  * Ubuntu17.10 - perf: Update Power9 PMU event JSON files (LP: #1708630)
- perf pmu-events: Support additional POWER8+ PVR in mapfile
- perf vendor events: Add POWER9 PMU events
- perf vendor events: Add POWER9 PVRs to mapfile
- SAUCE: perf vendor events powerpc: remove suffix in mapfile
- SAUCE: perf vendor events powerpc: Update POWER9 events

  * Disable CONFIG_MEMORY_HOTPLU

[Kernel-packages] [Bug 1711182] Re: ACPI ID for Hip07/08 I2C controller has typo

This bug was fixed in the package linux - 4.12.0-12.13

---
linux (4.12.0-12.13) artful; urgency=low

  * Artful update to v4.12.8 stable release (LP: #1711368)
- mm: ratelimit PFNs busy info message
- mm: fix list corruptions on shmem shrinklist
- futex: Remove unnecessary warning from get_futex_key
- xtensa: fix cache aliasing handling code for WT cache
- xtensa: mm/cache: add missing EXPORT_SYMBOLs
- xtensa: don't limit csum_partial export by CONFIG_NET
- xfs: Fix leak of discard bio
- pinctrl: armada-37xx: Fix number of pin in south bridge
- mtd: nand: atmel: Fix DT backward compatibility in pmecc.c
- mtd: nand: Fix timing setup for NANDs that do not support SET FEATURES
- mtd: nand: Declare tBERS, tR and tPROG as u64 to avoid integer overflow
- iscsi-target: fix memory leak in iscsit_setup_text_cmd()
- iscsi-target: Fix iscsi_np reset hung task during parallel delete
- usb-storage: fix deadlock involving host lock and scsi_done
- target: Fix node_acl demo-mode + uncached dynamic shutdown regression
- fuse: initialize the flock flag in fuse_file on allocation
- i2c: designware: Some broken DSTDs use 1MiHz instead of 1MHz
- nand: fix wrong default oob layout for small pages using soft ecc
- mmc: mmc: correct the logic for setting HS400ES signal voltage
- nfs/flexfiles: fix leak of nfs4_ff_ds_version arrays
- drm/bridge: tc358767: fix probe without attached output node
- drm/etnaviv: Fix off-by-one error in reloc checking
- drm/i915: Fix out-of-bounds array access in bdw_load_gamma_lut
- USB: serial: option: add D-Link DWM-222 device ID
- USB: serial: cp210x: add support for Qivicon USB ZigBee dongle
- USB: serial: pl2303: add new ATEN device id
- usb: musb: fix tx fifo flush handling again
- USB: hcd: Mark secondary HCD as dead if the primary one died
- staging:iio:resolver:ad2s1210 fix negative IIO_ANGL_VEL read
- iio: aspeed-adc: wait for initial sequence.
- iio: accel: st_accel: add SPI-3wire support
- iio: accel: bmc150: Always restore device to normal mode after suspend-
  resume
- iio: pressure: st_pressure_core: disable multiread by default for LPS22HB
- iio: light: tsl2563: use correct event code
- iio: adc: Revert "axp288: Drop bogus AXP288_ADC_TS_PIN_CTRL register
  modifications"
- staging: comedi: comedi_fops: do not call blocking ops when !TASK_RUNNING
- uas: Add US_FL_IGNORE_RESIDUE for Initio Corporation INIC-3069
- firmware: fix batched requests - wake all waiters
- firmware: fix batched requests - send wake up on failure on direct lookups
- firmware: avoid invalid fallback aborts by using killable wait
- block: Make blk_mq_delay_kick_requeue_list() rerun the queue at a quiet 
time
- usb: gadget: udc: renesas_usb3: Fix usb_gadget_giveback_request() calling
- usb: renesas_usbhs: Fix UGCTRL2 value for R-Car Gen3
- USB: Check for dropped connection before switching to full speed
- usb: core: unlink urbs from the tail of the endpoint's urb_list
- usb: quirks: Add no-lpm quirk for Moshi USB to Ethernet Adapter
- usb:xhci:Add quirk for Certain failing HP keyboard on reset after resume
- PCI: Protect pci_error_handlers->reset_notify() usage with device_lock()
- PCI: Remove __pci_dev_reset() and pci_dev_reset()
- PCI: Add pci_reset_function_locked()
- xhci: Reset Renesas uPD72020x USB controller for 32-bit DMA issue
- iio: adc: vf610_adc: Fix VALT selection value for REFSEL bits
- pnfs/blocklayout: require 64-bit sector_t
- pinctrl: cherryview: Add Setzer models to the Chromebook DMI quirk
- pinctrl: sunxi: add a missing function of A10/A20 pinctrl driver
- pinctrl: intel: merrifield: Correct UART pin lists
- pinctrl: uniphier: fix WARN_ON() of pingroups dump on LD11
- pinctrl: uniphier: fix WARN_ON() of pingroups dump on LD20
- pinctrl: samsung: Remove bogus irq_[un]mask from resource management
- pinctrl: meson-gxbb: Add missing GPIODV_18 pin entry
- pinctrl: meson-gxl: Add missing GPIODV_18 pin entry
- MIPS: DEC: Fix an int-handler.S CPU_DADDI_WORKAROUNDS regression
- Revert "MIPS: Don't unnecessarily include kmalloc.h into ."
- MIPS: Octeon: Fix broken EDAC driver.
- Linux 4.12.8

  * Artful: 4.12.0-11.12: Boot panic in vlv2_plat_configure_clock+0x3b/0xa0
(LP: #1711298)
- [Config] CONFIG_INTEL_ATOMISP=n

  * ACPI ID for Hip07/08 I2C controller has typo (LP: #1711182)
- ACPI: APD: Fix HID for Hisilicon Hip07/08

  * Ubuntu17.10 - perf: Update Power9 PMU event JSON files (LP: #1708630)
- perf pmu-events: Support additional POWER8+ PVR in mapfile
- perf vendor events: Add POWER9 PMU events
- perf vendor events: Add POWER9 PVRs to mapfile
- SAUCE: perf vendor events powerpc: remove suffix in mapfile
- SAUCE: perf vendor events powerpc: Update POWER9 events

  * Disable CONFIG_MEMORY_HOTPLU

[Kernel-packages] [Bug 1711298] Re: Artful: 4.12.0-11.12: Boot panic in vlv2_plat_configure_clock+0x3b/0xa0

This bug was fixed in the package linux - 4.12.0-12.13

---
linux (4.12.0-12.13) artful; urgency=low

  * Artful update to v4.12.8 stable release (LP: #1711368)
- mm: ratelimit PFNs busy info message
- mm: fix list corruptions on shmem shrinklist
- futex: Remove unnecessary warning from get_futex_key
- xtensa: fix cache aliasing handling code for WT cache
- xtensa: mm/cache: add missing EXPORT_SYMBOLs
- xtensa: don't limit csum_partial export by CONFIG_NET
- xfs: Fix leak of discard bio
- pinctrl: armada-37xx: Fix number of pin in south bridge
- mtd: nand: atmel: Fix DT backward compatibility in pmecc.c
- mtd: nand: Fix timing setup for NANDs that do not support SET FEATURES
- mtd: nand: Declare tBERS, tR and tPROG as u64 to avoid integer overflow
- iscsi-target: fix memory leak in iscsit_setup_text_cmd()
- iscsi-target: Fix iscsi_np reset hung task during parallel delete
- usb-storage: fix deadlock involving host lock and scsi_done
- target: Fix node_acl demo-mode + uncached dynamic shutdown regression
- fuse: initialize the flock flag in fuse_file on allocation
- i2c: designware: Some broken DSTDs use 1MiHz instead of 1MHz
- nand: fix wrong default oob layout for small pages using soft ecc
- mmc: mmc: correct the logic for setting HS400ES signal voltage
- nfs/flexfiles: fix leak of nfs4_ff_ds_version arrays
- drm/bridge: tc358767: fix probe without attached output node
- drm/etnaviv: Fix off-by-one error in reloc checking
- drm/i915: Fix out-of-bounds array access in bdw_load_gamma_lut
- USB: serial: option: add D-Link DWM-222 device ID
- USB: serial: cp210x: add support for Qivicon USB ZigBee dongle
- USB: serial: pl2303: add new ATEN device id
- usb: musb: fix tx fifo flush handling again
- USB: hcd: Mark secondary HCD as dead if the primary one died
- staging:iio:resolver:ad2s1210 fix negative IIO_ANGL_VEL read
- iio: aspeed-adc: wait for initial sequence.
- iio: accel: st_accel: add SPI-3wire support
- iio: accel: bmc150: Always restore device to normal mode after suspend-
  resume
- iio: pressure: st_pressure_core: disable multiread by default for LPS22HB
- iio: light: tsl2563: use correct event code
- iio: adc: Revert "axp288: Drop bogus AXP288_ADC_TS_PIN_CTRL register
  modifications"
- staging: comedi: comedi_fops: do not call blocking ops when !TASK_RUNNING
- uas: Add US_FL_IGNORE_RESIDUE for Initio Corporation INIC-3069
- firmware: fix batched requests - wake all waiters
- firmware: fix batched requests - send wake up on failure on direct lookups
- firmware: avoid invalid fallback aborts by using killable wait
- block: Make blk_mq_delay_kick_requeue_list() rerun the queue at a quiet 
time
- usb: gadget: udc: renesas_usb3: Fix usb_gadget_giveback_request() calling
- usb: renesas_usbhs: Fix UGCTRL2 value for R-Car Gen3
- USB: Check for dropped connection before switching to full speed
- usb: core: unlink urbs from the tail of the endpoint's urb_list
- usb: quirks: Add no-lpm quirk for Moshi USB to Ethernet Adapter
- usb:xhci:Add quirk for Certain failing HP keyboard on reset after resume
- PCI: Protect pci_error_handlers->reset_notify() usage with device_lock()
- PCI: Remove __pci_dev_reset() and pci_dev_reset()
- PCI: Add pci_reset_function_locked()
- xhci: Reset Renesas uPD72020x USB controller for 32-bit DMA issue
- iio: adc: vf610_adc: Fix VALT selection value for REFSEL bits
- pnfs/blocklayout: require 64-bit sector_t
- pinctrl: cherryview: Add Setzer models to the Chromebook DMI quirk
- pinctrl: sunxi: add a missing function of A10/A20 pinctrl driver
- pinctrl: intel: merrifield: Correct UART pin lists
- pinctrl: uniphier: fix WARN_ON() of pingroups dump on LD11
- pinctrl: uniphier: fix WARN_ON() of pingroups dump on LD20
- pinctrl: samsung: Remove bogus irq_[un]mask from resource management
- pinctrl: meson-gxbb: Add missing GPIODV_18 pin entry
- pinctrl: meson-gxl: Add missing GPIODV_18 pin entry
- MIPS: DEC: Fix an int-handler.S CPU_DADDI_WORKAROUNDS regression
- Revert "MIPS: Don't unnecessarily include kmalloc.h into ."
- MIPS: Octeon: Fix broken EDAC driver.
- Linux 4.12.8

  * Artful: 4.12.0-11.12: Boot panic in vlv2_plat_configure_clock+0x3b/0xa0
(LP: #1711298)
- [Config] CONFIG_INTEL_ATOMISP=n

  * ACPI ID for Hip07/08 I2C controller has typo (LP: #1711182)
- ACPI: APD: Fix HID for Hisilicon Hip07/08

  * Ubuntu17.10 - perf: Update Power9 PMU event JSON files (LP: #1708630)
- perf pmu-events: Support additional POWER8+ PVR in mapfile
- perf vendor events: Add POWER9 PMU events
- perf vendor events: Add POWER9 PVRs to mapfile
- SAUCE: perf vendor events powerpc: remove suffix in mapfile
- SAUCE: perf vendor events powerpc: Update POWER9 events

  * Disable CONFIG_MEMORY_HOTPLU

[Kernel-packages] [Bug 1709123] Re: [SRU][Zesty] [QDF2400] pl011 E44 erratum patch needed for 2.0 firmware and 1.1 silicon

This bug was fixed in the package linux - 4.12.0-12.13

---
linux (4.12.0-12.13) artful; urgency=low

  * Artful update to v4.12.8 stable release (LP: #1711368)
- mm: ratelimit PFNs busy info message
- mm: fix list corruptions on shmem shrinklist
- futex: Remove unnecessary warning from get_futex_key
- xtensa: fix cache aliasing handling code for WT cache
- xtensa: mm/cache: add missing EXPORT_SYMBOLs
- xtensa: don't limit csum_partial export by CONFIG_NET
- xfs: Fix leak of discard bio
- pinctrl: armada-37xx: Fix number of pin in south bridge
- mtd: nand: atmel: Fix DT backward compatibility in pmecc.c
- mtd: nand: Fix timing setup for NANDs that do not support SET FEATURES
- mtd: nand: Declare tBERS, tR and tPROG as u64 to avoid integer overflow
- iscsi-target: fix memory leak in iscsit_setup_text_cmd()
- iscsi-target: Fix iscsi_np reset hung task during parallel delete
- usb-storage: fix deadlock involving host lock and scsi_done
- target: Fix node_acl demo-mode + uncached dynamic shutdown regression
- fuse: initialize the flock flag in fuse_file on allocation
- i2c: designware: Some broken DSTDs use 1MiHz instead of 1MHz
- nand: fix wrong default oob layout for small pages using soft ecc
- mmc: mmc: correct the logic for setting HS400ES signal voltage
- nfs/flexfiles: fix leak of nfs4_ff_ds_version arrays
- drm/bridge: tc358767: fix probe without attached output node
- drm/etnaviv: Fix off-by-one error in reloc checking
- drm/i915: Fix out-of-bounds array access in bdw_load_gamma_lut
- USB: serial: option: add D-Link DWM-222 device ID
- USB: serial: cp210x: add support for Qivicon USB ZigBee dongle
- USB: serial: pl2303: add new ATEN device id
- usb: musb: fix tx fifo flush handling again
- USB: hcd: Mark secondary HCD as dead if the primary one died
- staging:iio:resolver:ad2s1210 fix negative IIO_ANGL_VEL read
- iio: aspeed-adc: wait for initial sequence.
- iio: accel: st_accel: add SPI-3wire support
- iio: accel: bmc150: Always restore device to normal mode after suspend-
  resume
- iio: pressure: st_pressure_core: disable multiread by default for LPS22HB
- iio: light: tsl2563: use correct event code
- iio: adc: Revert "axp288: Drop bogus AXP288_ADC_TS_PIN_CTRL register
  modifications"
- staging: comedi: comedi_fops: do not call blocking ops when !TASK_RUNNING
- uas: Add US_FL_IGNORE_RESIDUE for Initio Corporation INIC-3069
- firmware: fix batched requests - wake all waiters
- firmware: fix batched requests - send wake up on failure on direct lookups
- firmware: avoid invalid fallback aborts by using killable wait
- block: Make blk_mq_delay_kick_requeue_list() rerun the queue at a quiet 
time
- usb: gadget: udc: renesas_usb3: Fix usb_gadget_giveback_request() calling
- usb: renesas_usbhs: Fix UGCTRL2 value for R-Car Gen3
- USB: Check for dropped connection before switching to full speed
- usb: core: unlink urbs from the tail of the endpoint's urb_list
- usb: quirks: Add no-lpm quirk for Moshi USB to Ethernet Adapter
- usb:xhci:Add quirk for Certain failing HP keyboard on reset after resume
- PCI: Protect pci_error_handlers->reset_notify() usage with device_lock()
- PCI: Remove __pci_dev_reset() and pci_dev_reset()
- PCI: Add pci_reset_function_locked()
- xhci: Reset Renesas uPD72020x USB controller for 32-bit DMA issue
- iio: adc: vf610_adc: Fix VALT selection value for REFSEL bits
- pnfs/blocklayout: require 64-bit sector_t
- pinctrl: cherryview: Add Setzer models to the Chromebook DMI quirk
- pinctrl: sunxi: add a missing function of A10/A20 pinctrl driver
- pinctrl: intel: merrifield: Correct UART pin lists
- pinctrl: uniphier: fix WARN_ON() of pingroups dump on LD11
- pinctrl: uniphier: fix WARN_ON() of pingroups dump on LD20
- pinctrl: samsung: Remove bogus irq_[un]mask from resource management
- pinctrl: meson-gxbb: Add missing GPIODV_18 pin entry
- pinctrl: meson-gxl: Add missing GPIODV_18 pin entry
- MIPS: DEC: Fix an int-handler.S CPU_DADDI_WORKAROUNDS regression
- Revert "MIPS: Don't unnecessarily include kmalloc.h into ."
- MIPS: Octeon: Fix broken EDAC driver.
- Linux 4.12.8

  * Artful: 4.12.0-11.12: Boot panic in vlv2_plat_configure_clock+0x3b/0xa0
(LP: #1711298)
- [Config] CONFIG_INTEL_ATOMISP=n

  * ACPI ID for Hip07/08 I2C controller has typo (LP: #1711182)
- ACPI: APD: Fix HID for Hisilicon Hip07/08

  * Ubuntu17.10 - perf: Update Power9 PMU event JSON files (LP: #1708630)
- perf pmu-events: Support additional POWER8+ PVR in mapfile
- perf vendor events: Add POWER9 PMU events
- perf vendor events: Add POWER9 PVRs to mapfile
- SAUCE: perf vendor events powerpc: remove suffix in mapfile
- SAUCE: perf vendor events powerpc: Update POWER9 events

  * Disable CONFIG_MEMORY_HOTPLU

[Kernel-packages] [Bug 1708630] Re: Ubuntu17.10 - perf: Update Power9 PMU event JSON files

This bug was fixed in the package linux - 4.12.0-12.13

---
linux (4.12.0-12.13) artful; urgency=low

  * Artful update to v4.12.8 stable release (LP: #1711368)
- mm: ratelimit PFNs busy info message
- mm: fix list corruptions on shmem shrinklist
- futex: Remove unnecessary warning from get_futex_key
- xtensa: fix cache aliasing handling code for WT cache
- xtensa: mm/cache: add missing EXPORT_SYMBOLs
- xtensa: don't limit csum_partial export by CONFIG_NET
- xfs: Fix leak of discard bio
- pinctrl: armada-37xx: Fix number of pin in south bridge
- mtd: nand: atmel: Fix DT backward compatibility in pmecc.c
- mtd: nand: Fix timing setup for NANDs that do not support SET FEATURES
- mtd: nand: Declare tBERS, tR and tPROG as u64 to avoid integer overflow
- iscsi-target: fix memory leak in iscsit_setup_text_cmd()
- iscsi-target: Fix iscsi_np reset hung task during parallel delete
- usb-storage: fix deadlock involving host lock and scsi_done
- target: Fix node_acl demo-mode + uncached dynamic shutdown regression
- fuse: initialize the flock flag in fuse_file on allocation
- i2c: designware: Some broken DSTDs use 1MiHz instead of 1MHz
- nand: fix wrong default oob layout for small pages using soft ecc
- mmc: mmc: correct the logic for setting HS400ES signal voltage
- nfs/flexfiles: fix leak of nfs4_ff_ds_version arrays
- drm/bridge: tc358767: fix probe without attached output node
- drm/etnaviv: Fix off-by-one error in reloc checking
- drm/i915: Fix out-of-bounds array access in bdw_load_gamma_lut
- USB: serial: option: add D-Link DWM-222 device ID
- USB: serial: cp210x: add support for Qivicon USB ZigBee dongle
- USB: serial: pl2303: add new ATEN device id
- usb: musb: fix tx fifo flush handling again
- USB: hcd: Mark secondary HCD as dead if the primary one died
- staging:iio:resolver:ad2s1210 fix negative IIO_ANGL_VEL read
- iio: aspeed-adc: wait for initial sequence.
- iio: accel: st_accel: add SPI-3wire support
- iio: accel: bmc150: Always restore device to normal mode after suspend-
  resume
- iio: pressure: st_pressure_core: disable multiread by default for LPS22HB
- iio: light: tsl2563: use correct event code
- iio: adc: Revert "axp288: Drop bogus AXP288_ADC_TS_PIN_CTRL register
  modifications"
- staging: comedi: comedi_fops: do not call blocking ops when !TASK_RUNNING
- uas: Add US_FL_IGNORE_RESIDUE for Initio Corporation INIC-3069
- firmware: fix batched requests - wake all waiters
- firmware: fix batched requests - send wake up on failure on direct lookups
- firmware: avoid invalid fallback aborts by using killable wait
- block: Make blk_mq_delay_kick_requeue_list() rerun the queue at a quiet 
time
- usb: gadget: udc: renesas_usb3: Fix usb_gadget_giveback_request() calling
- usb: renesas_usbhs: Fix UGCTRL2 value for R-Car Gen3
- USB: Check for dropped connection before switching to full speed
- usb: core: unlink urbs from the tail of the endpoint's urb_list
- usb: quirks: Add no-lpm quirk for Moshi USB to Ethernet Adapter
- usb:xhci:Add quirk for Certain failing HP keyboard on reset after resume
- PCI: Protect pci_error_handlers->reset_notify() usage with device_lock()
- PCI: Remove __pci_dev_reset() and pci_dev_reset()
- PCI: Add pci_reset_function_locked()
- xhci: Reset Renesas uPD72020x USB controller for 32-bit DMA issue
- iio: adc: vf610_adc: Fix VALT selection value for REFSEL bits
- pnfs/blocklayout: require 64-bit sector_t
- pinctrl: cherryview: Add Setzer models to the Chromebook DMI quirk
- pinctrl: sunxi: add a missing function of A10/A20 pinctrl driver
- pinctrl: intel: merrifield: Correct UART pin lists
- pinctrl: uniphier: fix WARN_ON() of pingroups dump on LD11
- pinctrl: uniphier: fix WARN_ON() of pingroups dump on LD20
- pinctrl: samsung: Remove bogus irq_[un]mask from resource management
- pinctrl: meson-gxbb: Add missing GPIODV_18 pin entry
- pinctrl: meson-gxl: Add missing GPIODV_18 pin entry
- MIPS: DEC: Fix an int-handler.S CPU_DADDI_WORKAROUNDS regression
- Revert "MIPS: Don't unnecessarily include kmalloc.h into ."
- MIPS: Octeon: Fix broken EDAC driver.
- Linux 4.12.8

  * Artful: 4.12.0-11.12: Boot panic in vlv2_plat_configure_clock+0x3b/0xa0
(LP: #1711298)
- [Config] CONFIG_INTEL_ATOMISP=n

  * ACPI ID for Hip07/08 I2C controller has typo (LP: #1711182)
- ACPI: APD: Fix HID for Hisilicon Hip07/08

  * Ubuntu17.10 - perf: Update Power9 PMU event JSON files (LP: #1708630)
- perf pmu-events: Support additional POWER8+ PVR in mapfile
- perf vendor events: Add POWER9 PMU events
- perf vendor events: Add POWER9 PVRs to mapfile
- SAUCE: perf vendor events powerpc: remove suffix in mapfile
- SAUCE: perf vendor events powerpc: Update POWER9 events

  * Disable CONFIG_MEMORY_HOTPLU

[Kernel-packages] [Bug 1626984] Re: kernel BUG at /build/linux-lts-xenial-_hWfOZ/linux-lts-xenial-4.4.0/security/apparmor/include/context.h:69!

2017-09-01 Thread Eric Desrochers

A patch[1] has been submitted to Kernel team ML, it is now waiting for
kernel folks ACK and will then fall under the next kernel cycle.

[1] - Email subject : 
[PATCH][Xenial][Zesty] UBUNTU: SAUCE: fix oops when disabled and module 
parameters, are accessed

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

Title:
  kernel BUG at /build/linux-lts-xenial-_hWfOZ/linux-lts-
  xenial-4.4.0/security/apparmor/include/context.h:69!

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I am runing sosreport on ubuntu 14.04.4 LTS which has upgrade the kernel to 
4.4.0-38-generic, it get oops while copying 
/sys/module/apparmor/parameters/audit. and it also can be triggered with
  cat /sys/module/apparmor/parameters/audit.

  [  213.174092] [ cut here ]
  [  213.174130] kernel BUG at 
/build/linux-lts-xenial-_hWfOZ/linux-lts-xenial-4.4.0/security/apparmor/include/context.h:69!
  [  213.174187] invalid opcode:  [#1] SMP 
  [  213.174215] Modules linked in: ppdev lp joydev serio_raw parport_pc 
parport psmouse virtio_scsi floppy
  [  213.174283] CPU: 0 PID: 2246 Comm: cat Not tainted 4.4.0-38-generic 
#57~14.04.1-Ubuntu
  [  213.174324] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 
rel-1.8.2-0-g33fbe13 by qemu-project.org 04/01/2014
  [  213.174380] task: 880037b15780 ti: 8800399c4000 task.ti: 
8800399c4000
  [  213.174419] RIP: 0010:[]  [] 
aa_current_raw_label.part.6+0x4/0x6
  [  213.174478] RSP: 0018:8800399c7d60  EFLAGS: 00010246
  [  213.174506] RAX:  RBX: 88003a426000 RCX: 
88003e3802a0
  [  213.174542] RDX: 88003a426000 RSI: 81ddc0d8 RDI: 
88003a426000
  [  213.174578] RBP: 8800399c7d60 R08: 88003e3802a0 R09: 

  [  213.174614] R10: 1000 R11: 0246 R12: 
81e44ae0
  [  213.174658] R13: 88003e3802a0 R14: 81e4c220 R15: 
88003c2b2e40
  [  213.174702] FS:  7f7bea106740() GS:88003fc0() 
knlGS:
  [  213.174743] CS:  0010 DS:  ES:  CR0: 80050033
  [  213.174781] CR2: 00a40038 CR3: 3cdfa000 CR4: 
06f0
  [  213.174819] Stack:
  [  213.174832]  8800399c7d88 8136d58a 88003a426000 
88003a426000
  [  213.174885]  88003e3802a0 8800399c7da0 8136fda2 
88003e39c5f0
  [  213.174928]  8800399c7dd0 8109a7e4 88003c2b2e40 
81a170c0
  [  213.174971] Call Trace:
  [  213.174996]  [] policy_view_capable+0x1ba/0x220
  [  213.175030]  [] param_get_audit+0x12/0x50
  [  213.175062]  [] param_attr_show+0x54/0xa0
  [  213.175092]  [] module_attr_show+0x1d/0x30
  [  213.175130]  [] sysfs_kf_seq_show+0xc2/0x1a0
  [  213.175162]  [] kernfs_seq_show+0x23/0x30
  [  213.175199]  [] seq_read+0xe5/0x350
  [  213.175227]  [] kernfs_fop_read+0x10d/0x170
  [  213.176170]  [] __vfs_read+0x18/0x40
  [  213.177101]  [] vfs_read+0x7f/0x130
  [  213.178016]  [] SyS_read+0x46/0xa0
  [  213.178932]  [] entry_SYSCALL_64_fastpath+0x16/0x75
  [  213.179814] Code: 80 3d 1a 7f b8 00 00 75 1d 55 be 2e 00 00 00 48 c7 c7 f0 
2f cb 81 48 89 e5 e8 7c 50 cf ff 5d c6 05 fb 7e b8 00 01 c3 55 48 89 e5 <0f> 0b 
b8 01 00 00 00 3e 0f c1 07 ff c0 ff c8 7f 26 80 3d df 7e 
  [  213.182634] RIP  [] aa_current_raw_label.part.6+0x4/0x6
  [  213.183528]  RSP 

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

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

[Kernel-packages] [Bug 1703339] Re: Unable to install Ubuntu on the NVMe disk under VMD PCI domain

2017-09-01 Thread Tomasz Majchrzak

Yes, I tested it today with artful.

It works fine for Ubuntu 17.10 (Artful Aardvark) Daily Build (vmd.ko
present)

It doesn't work for Ubuntu Server 17.10 (Artful Aardvark) Daily Build
(no vmd.ko). I see it has a kernel 4.12.0-11-generic. Does text
installer come with a different kernel?

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

Title:
  Unable to install Ubuntu on the NVMe disk under VMD PCI domain

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

Bug description:
  It is not possible to install Ubuntu on the NVMe disk under VMD
  (Volume Management Device) PCI domain. The disk is not visible in the
  installer because VMD module is not available at this stage.

  I'm raising it against kernel package as I have impression VMD module
  must be included in linux-image dpkg package, not linux-image-extra.

  Please also assure VMD module gets included in initramfs by installer
  (if necessary).

  For more information about VMD please see bug 1591806.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-generic 4.10.0.26.28
  ProcVersionSignature: Ubuntu 4.10.0-26.30-generic 4.10.17
  Uname: Linux 4.10.0-26-generic x86_64
  ApportVersion: 2.20.5-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   tomasz 1659 F...m pulseaudio
   /dev/snd/controlC0:  tomasz 1659 F pulseaudio
   /dev/snd/timer:  tomasz 1659 f pulseaudio
  CurrentDesktop: GNOME
  Date: Mon Jul 10 10:40:20 2017
  HibernationDevice: RESUME=/dev/mapper/ubuntu--vg-swap_1
  InstallationDate: Installed on 2017-07-06 (3 days ago)
  InstallationMedia: Ubuntu-Server 17.10 "Artful Aardvark" - Alpha amd64 
(20170702)
  IwConfig:
   lono wireless extensions.
   
   enp0s3no wireless extensions.
  Lsusb:
   Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet
   Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: innotek GmbH VirtualBox
  ProcFB: 0 vboxdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-26-generic 
root=/dev/mapper/hostname--vg-root ro
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-26-generic N/A
   linux-backports-modules-4.10.0-26-generic  N/A
   linux-firmware 1.167
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH

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

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

[Kernel-packages] [Bug 1705447] Re: misleading kernel warning skb_warn_bad_offload during checksum calculation

2017-09-01 Thread manojav

I am still seeing this issue with

Linux ___ 4.4.0-93-generic #116-Ubuntu SMP Fri Aug 11 21:17:51 UTC 2017
x86_64 x86_64 x86_64 GNU/Linux


[214343.266228] [ cut here ]
[214343.266235] WARNING: CPU: 1 PID: 10743 at 
/build/linux-YyUNAI/linux-4.4.0/net/core/dev.c:2445 
skb_warn_bad_offload+0xd1/0x120()
[214343.266239] tg3: caps=(0x000401b2, 0x) len=1444 
data_len=1402 gso_size=1376 gso_type=2 ip_summed=0
[214343.266241] Modules linked in: nf_conntrack_netlink nfnetlink binfmt_misc 
rpcsec_gss_krb5 auth_rpcgss nfsv4 nfs lockd grace fscache veth ipt_MASQUERADE 
nf_nat_masquerade_ipv4 xfrm_user xfrm_algo xt_addrtype iptable_filter 
xt_conntrack br_netfilter bridge stp llc aufs xt_nat xt_tcpudp iptable_nat 
nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack ip_tables 
x_tables hp_wmi gpio_ich sparse_keymap ppdev intel_powerclamp coretemp 
kvm_intel snd_hda_codec_realtek kvm snd_hda_codec_generic snd_hda_intel 
irqbypass snd_hda_codec snd_hda_core snd_hwdep snd_pcm snd_timer pl2303 snd 
usbserial soundcore input_leds serio_raw lpc_ich i7core_edac shpchp edac_core 
8250_fintek parport_pc tpm_infineon parport mac_hid ib_iser rdma_cm iw_cm ib_cm 
ib_sa ib_mad ib_core ib_addr iscsi_tcp libiscsi_tcp libiscsi
[214343.266302]  scsi_transport_iscsi sunrpc autofs4 btrfs raid10 raid456 
async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq 
libcrc32c raid1 raid0 multipath linear hid_generic usbhid hid nouveau 
crct10dif_pclmul crc32_pclmul ghash_clmulni_intel aesni_intel mxm_wmi video 
aes_x86_64 i2c_algo_bit lrw ttm gf128mul glue_helper ablk_helper drm_kms_helper 
syscopyarea cryptd firewire_ohci sysfillrect tg3 psmouse sysimgblt fb_sys_fops 
firewire_core ahci ptp libahci drm crc_itu_t pps_core wmi floppy fjes
[214343.266347] CPU: 1 PID: 10743 Comm: transmission-da Tainted: GW I   
  4.4.0-93-generic #116-Ubuntu
[214343.266349] Hardware name: Hewlett-Packard HP Z600 Workstation/0B54h, BIOS 
786G4 v03.13 10/13/2010
[214343.266351]  0286 4281c02c793d7594 880313a434c8 
813f9f83
[214343.266355]  880313a43510 81d6f780 880313a43500 
810812f2
[214343.266358]  88030f710300 8803114c 0002 
880310cbd6ac
[214343.266361] Call Trace:
[214343.266363][] dump_stack+0x63/0x90
[214343.266373]  [] warn_slowpath_common+0x82/0xc0
[214343.266376]  [] warn_slowpath_fmt+0x5c/0x80
[214343.266381]  [] ? ___ratelimit+0xa2/0xe0
[214343.266385]  [] skb_warn_bad_offload+0xd1/0x120
[214343.266388]  [] __skb_gso_segment+0xfd/0x110
[214343.266391]  [] 
validate_xmit_skb.isra.97.part.98+0x10d/0x2b0
[214343.266394]  [] validate_xmit_skb_list+0x3b/0x60
[214343.266399]  [] sch_direct_xmit+0x16a/0x220
[214343.266402]  [] __dev_queue_xmit+0x23d/0x590
[214343.266405]  [] dev_queue_xmit+0x10/0x20
[214343.266410]  [] neigh_resolve_output+0x118/0x1c0
[214343.266415]  [] ip_finish_output2+0x146/0x380
[214343.266420]  [] ? ipv4_confirm+0x7d/0x100 
[nf_conntrack_ipv4]
[214343.266424]  [] ip_finish_output+0x136/0x1f0
[214343.266428]  [] ? nf_hook_slow+0x73/0xd0
[214343.266431]  [] ip_output+0x6e/0xe0
[214343.266435]  [] ? 
__ip_flush_pending_frames.isra.41+0x90/0x90
[214343.266438]  [] ip_forward_finish+0x43/0x70
[214343.266441]  [] ip_forward+0x399/0x480
[214343.266444]  [] ? ip_frag_mem+0x50/0x50
[214343.266447]  [] ip_rcv_finish+0x92/0x320
[214343.266450]  [] ip_rcv+0x291/0x3a0
[214343.266453]  [] ? inet_del_offload+0x40/0x40
[214343.266456]  [] __netif_receive_skb_core+0x704/0xa60
[214343.266467]  [] ? nf_conntrack_tuple_taken+0x1b0/0x1d0 
[nf_conntrack]
[214343.266474]  [] ? get_unique_tuple+0x147/0x630 [nf_nat]
[214343.266476]  [] __netif_receive_skb+0x18/0x60
[214343.266479]  [] netif_receive_skb_internal+0x32/0xa0
[214343.266482]  [] netif_receive_skb+0x1c/0x70
[214343.266491]  [] br_netif_receive_skb+0x34/0x50 [bridge]
[214343.266498]  [] br_handle_frame_finish+0x2bb/0x620 
[bridge]
[214343.266505]  [] ? __nf_ct_refresh_acct+0xab/0xc0 
[nf_conntrack]
[214343.266513]  [] ? br_handle_local_finish+0xa0/0xa0 
[bridge]
[214343.266520]  [] ? br_handle_local_finish+0xa0/0xa0 
[bridge]
[214343.266524]  [] NF_HOOK_THRESH+0x57/0xb0 [br_netfilter]
[214343.266531]  [] ? br_handle_local_finish+0xa0/0xa0 
[bridge]
[214343.266535]  [] br_nf_pre_routing_finish+0x1a9/0x350 
[br_netfilter]
[214343.266542]  [] ? br_handle_local_finish+0xa0/0xa0 
[bridge]
[214343.266545]  [] ? nf_iterate+0x62/0x80
[214343.266549]  [] br_nf_pre_routing+0x2e1/0x440 
[br_netfilter]
[214343.266553]  [] ? br_nf_forward_ip+0x480/0x480 
[br_netfilter]
[214343.266556]  [] nf_iterate+0x62/0x80
[214343.266560]  [] nf_hook_slow+0x73/0xd0
[214343.266567]  [] br_handle_frame+0x1da/0x2b0 [bridge]
[214343.266573]  [] ? can_migrate_task+0x287/0x2b0
[214343.266580]  [] ? br_handle_local_finish+0xa0/0xa0 
[bridge]
[214343.266583]  [] __netif_receive_skb_core+0x364/0xa60
[214343.266586]  [] ? sched_clock_cpu+0x8f/0xa0
[214343.266590]  [] ? check_pr

[Kernel-packages] [Bug 1705447] Re: misleading kernel warning skb_warn_bad_offload during checksum calculation

2017-09-01 Thread manojav

** Attachment added: "appport from crash"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1705447/+attachment/4942420/+files/apport.linux-image-4.4.0-93-generic.36d989m1.apport

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

Title:
  misleading kernel warning skb_warn_bad_offload during checksum
  calculation

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

Bug description:
  Even when the packet says checksum calculation is unnecessary the
  kernel will still check the checksum and display a warning that the
  checksum is bad.

  This has been fixed upstream in Kernel 4.11 by commit id:
  b2504a5dbef3305ef41988ad270b0e8ec289331c

  We have reports of Ubuntu 16.04 virtual machines (with ip forward
  enabled) displaying these warnings:

  
  [10480.074664] [ cut here ]
  [10480.074667] WARNING: CPU: 1 PID: 0 at 
/build/linux-hwe-X3pKE5/linux-hwe-4.8.0/net/core/dev.c:2444 
skb_warn_bad_offload+0xd1/0x120
  [10480.074669] docker0: caps=(0x0400ffbb78e9, 0x) 
len=2962 data_len=2834 gso_size=1448 gso_type=5 ip_summed=1
  [10480.074670] Modules linked in: veth nfsv3 nfs_acl rpcsec_gss_krb5 
auth_rpcgss nfsv4 nfs lockd grace sunrpc fscache ipt_MASQUERADE 
nf_nat_masquerade_ipv4 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 zfs(PO) 
zunicode(PO) zcommon(PO) znvpair(PO) spl(O) zavl(PO) crct10dif_pclmul 
crc32_pclmul ghash_clmulni_intel aesni_intel aes_x86_64 lrw glue_helper 
ablk_helper cryptd input_leds joydev serio_raw i2c_piix4 mac_hid parport_pc 
ppdev lp parport autofs4 hid_generic usbhid hid virtio_scsi psmouse virtio_net 
pata_acpi floppy
  [10480.074695] CPU: 1 PID: 0 Comm: swapper/1 Tainted: PW  O
4.8.0-52-generic #55~16.04.1-Ubuntu
  [10480.074696] Hardware name: Nutanix AHV, BIOS seabios-1.7.5-11.el6 
04/01/2014
  [10480.074697]  0286 ec176c2ae03bc036 8beef5643870 
b7a2e7b3
  [10480.074699]  8beef56438c0  8beef56438b0 
b768314b
  [10480.074702]  098cb84fba80 8bed61f82000 8bee9915c000 
0005
  [10480.074704] Call Trace:
  [10480.074704][] dump_stack+0x63/0x90
  [10480.074708]  [] __warn+0xcb/0xf0
  [10480.074710]  [] warn_slowpath_fmt+0x5f/0x80
  [10480.074713]  [] ? ___ratelimit+0xa2/0xf0
  [10480.074714]  [] skb_warn_bad_offload+0xd1/0x120
  [10480.074716]  [] __skb_gso_segment+0xd8/0x140
  [10480.074717]  [] validate_xmit_skb+0x14f/0x2a0
  [10480.074719]  [] __dev_queue_xmit+0x322/0x6d0
  [10480.074720]  [] ? nf_nat_ipv4_fn+0x1a6/0x230 
[nf_nat_ipv4]
  [10480.074723]  [] dev_queue_xmit+0x10/0x20
  [10480.074725]  [] ip_finish_output2+0x292/0x380
  [10480.074726]  [] ? ipv4_confirm+0x7d/0x100 
[nf_conntrack_ipv4]
  [10480.074728]  [] ip_finish_output+0x132/0x1d0
  [10480.074729]  [] ? nf_hook_slow+0x73/0xd0
  [10480.074731]  [] ip_output+0x6e/0xf0
  [10480.074733]  [] ? 
__ip_flush_pending_frames.isra.40+0x90/0x90
  [10480.074736]  [] ip_forward_finish+0x43/0x70
  [10480.074738]  [] ip_forward+0x384/0x480
  [10480.074739]  [] ? ip_frag_mem+0x50/0x50
  [10480.074741]  [] ip_rcv_finish+0x11b/0x400
  [10480.074743]  [] ip_rcv+0x28b/0x3c0
  [10480.074744]  [] ? inet_del_offload+0x40/0x40
  [10480.074746]  [] __netif_receive_skb_core+0x524/0xab0
  [10480.074747]  [] ? kmem_cache_alloc+0xd7/0x1b0
  [10480.074749]  [] ? __build_skb+0x2a/0xe0
  [10480.074751]  [] __netif_receive_skb+0x18/0x60
  [10480.074753]  [] netif_receive_skb_internal+0x32/0xa0
  [10480.074754]  [] napi_gro_receive+0xcd/0x120
  [10480.074756]  [] virtnet_receive+0x1c3/0x970 [virtio_net]
  [10480.074758]  [] ? update_cfs_rq_load_avg+0x1f9/0x4c0
  [10480.074760]  [] virtnet_poll+0x1d/0x80 [virtio_net]
  [10480.074762]  [] net_rx_action+0x238/0x380
  [10480.074764]  [] __do_softirq+0xf6/0x280
  [10480.074765]  [] irq_exit+0xa3/0xb0
  [10480.074766]  [] do_IRQ+0x54/0xd0
  [10480.074768]  [] common_interrupt+0x82/0x82
  [10480.074768][] ? native_safe_halt+0x6/0x10
  [10480.074772]  [] default_idle+0x1e/0xd0
  [10480.074774]  [] arch_cpu_idle+0xf/0x20
  [10480.074775]  [] default_idle_call+0x2a/0x40
  [10480.074776]  [] cpu_startup_entry+0x2ea/0x350
  [10480.074778]  [] start_secondary+0x151/0x190
  [10480.074781] ---[ end trace 3a9bd18de5564b05 ]---

  
  We have recompiled your latest 16.04.2 kernel with this patch and confirmed 
that this warning does not happen. Could you please consider including this fix 
in your next 16.04 LTS release?

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

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

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

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

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

Title:
  linux: 3.13.0-130.179 -proposed tracker

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

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

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

  backports: 1713458
  derivatives:
  -- swm properties --
  boot-testing-requested: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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

[Kernel-packages] [Bug 1711571] Re: linux: 4.12.0-12.13 -proposed tracker

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


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

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

** Description changed:

  This bug is for tracking the 4.12.0-12.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
+ kernel-phase-changed:Friday, 01. September 2017 14:01 UTC
+ kernel-phase:Released

** Description changed:

  This bug is for tracking the 4.12.0-12.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
+ phase: Released
  proposed-announcement-sent: true
  proposed-testing-requested: true
- kernel-phase-changed:Friday, 01. September 2017 14:01 UTC
- kernel-phase:Released

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

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

Title:
  linux: 4.12.0-12.13 -proposed tracker

Status in Kernel Development Workflow:
  Fix Released
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:
  Fix Released
Status in Kernel Development Workflow regression-testing series:
  Fix Released
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Artful:
  Confirmed

Bug description:
  This bug is for tracking the 4.12.0-12.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: Released
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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

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

I built the next test kernel, up to the following commit:
49594cb78e0decefdd60bf462a25d7f50e8d5239

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

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

Thanks in advance

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

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

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

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

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

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

  Repro rate: 100%

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

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

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

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

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

[Kernel-packages] [Bug 1714525] [NEW] Artful update to v4.12.10 stable release

Public bug reported:

Artful update to v4.12.10 stable release

** Affects: linux (Ubuntu)
 Importance: High
 Assignee: Andy Whitcroft (apw)
 Status: In Progress

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

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

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

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

Title:
  Artful update to v4.12.10 stable release

Status in linux package in Ubuntu:
  In Progress

Bug description:
  Artful update to v4.12.10 stable release

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

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

[Kernel-packages] [Bug 1706247] Re: It should not be possible to turn on 16g huge pages on Ubuntu 16.04.2 PowerNV

Do you happen to know if there is a boot or sysctl option that can be
used to disable 16G Huge Pages?

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

Title:
  It should not be possible to turn on 16g huge pages on Ubuntu 16.04.2
  PowerNV

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

Bug description:
  16G Huge Pages are not supported on PowerNV (bare metal) installations. 
Ubuntu 16.04.2 still allows 16G huge pages to be turned on.
   
  Contact Information = Mike Hollinger (mchol...@us.ibm.com) 
   
  ---uname output---
  Linux aprilmin4 4.4.0-83-generic #106-Ubuntu SMP Mon Jun 26 17:53:54 UTC 2017 
ppc64le ppc64le ppc64le GNU/Linux
   
  Machine Type = 8335-GTB 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   1. Add the following to the kernel boot args (either via editing the 
petitboot boot option manually, or updating /boot/grub/grub.cfg:

  default_hugepagesz=16G hugepagesz=16G hugepages=4

  2. Boot Linux
  3. Observe that the kernel believes 16G huge pages are available:
  ubuntu@aprilmin7:~$ cat /proc/meminfo | grep -i huge
  AnonHugePages:475136 kB
  HugePages_Total:   0
  HugePages_Free:0
  HugePages_Rsvd:0
  HugePages_Surp:0
  Hugepagesize:   16777216 kB
  ubuntu@aprilmin7:~$ ls /sys/devices/system/node/node0/hugepages
  hugepages-1024kB  hugepages-16384kB  hugepages-16777216kB

   
  Stack trace output:
   no
   
  Oops output:
   no
   
  System Dump Info:
The system is not configured to capture a system dump.
   
  *Additional Instructions for Mike Hollinger (mchol...@us.ibm.com): 
  -Post a private note with access information to the machine that the bug is 
occuring on. 
  -Attach sysctl -a output output to the bug.

  
  This may be recreated on any bare metal POWER8 server with Ubuntu 16.04.2; I 
haven't checked other versions of Ubuntu.

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

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

[Kernel-packages] [Bug 1664545] Re: In Ubuntu17.04 as Kvm guest : While trigger kdump console hung having call traces

bug 1655280 may be related.

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

Title:
  In Ubuntu17.04 as Kvm guest  : While trigger kdump console hung having
  call traces

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

Bug description:
  In ubuntu17.04 as KVM guest on ubuntu KVM Host and trying kdump on
  guest while kdump process  console got hung having call traces

  
  Reproducible Step:

  1- Install Ubuntu17.04 as kvm guest  on ubuntu kvm host 
  2- configure kdump 
  3- trigger kdump 

  Expected Result :

  Kdump should capture

  Actual Result :

  Kdump console hung having continuous call traces

  LOG:

  [0.488534] Freeing unused kernel memory: 4416K (c8e8 - 
c92d)
  [0.488725] This architecture does not have kernel memory protection.
  Loading, please wait...
  starting version 232
  [0.501616] random: udevadm: uninitialized urandom read (16 bytes read)
  [0.501830] random: udevadm: uninitialized urandom read (16 bytes read)
  [0.501981] random: udevadm: uninitialized urandom read (16 bytes read)
  [0.502162] random: udevadm: uninitialized urandom read (16 bytes read)
  [0.502254] random: udevadm: uninitialized urandom read (16 bytes read)
  [0.502433] random: udevadm: uninitialized urandom read (16 bytes read)
  [0.503188] random: udevadm: uninitialized urandom read (16 bytes read)
  [0.503270] random: udevadm: uninitialized urandom read (16 bytes read)
  [0.503978] random: systemd-udevd: uninitialized urandom read (16 bytes 
read)
  [0.504218] random: systemd-udevd: uninitialized urandom read (16 bytes 
read)
  [  242.663388] INFO: task systemd-udevd:151 blocked for more than 120 seconds.
  [  242.663514]   Not tainted 4.9.0-15-generic #16-Ubuntu
  [  242.663553] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [  242.663755] systemd-udevd   D0   151145 0x00040002
  [  242.663795] Call Trace:
  [  242.663868] [c0001fe4ecd0] [c801c3a0] __switch_to+0x2e0/0x4c0
  [  242.663964] [c0001fe4ed30] [c8b19398] __schedule+0x2f8/0x990
  [  242.664076] [c0001fe4ee10] [c8b19a78] schedule+0x48/0xc0
  [  242.664179] [c0001fe4ee40] [c8b1de54] 
schedule_timeout+0x274/0x470
  [  242.664334] [c0001fe4ef30] [c8b19010] 
io_schedule_timeout+0xd0/0x160
  [  242.664502] [c0001fe4ef80] [c8b1a720] bit_wait_io+0x30/0x90
  [  242.664618] [c0001fe4efb0] [c8b1a168] __wait_on_bit+0xf8/0x170
  [  242.664754] [c0001fe4f000] [c824b238] 
wait_on_page_bit+0x98/0xb0
  [  242.664847] [c0001fe4f060] [c824d60c] 
do_read_cache_page+0x21c/0x4e0
  [  242.665008] [c0001fe4f0d0] [c859be78] 
read_dev_sector+0xb8/0x140
  [  242.665126] [c0001fe4f100] [c85a5d88] 
read_lba.isra.0+0x148/0x250
  [  242.665259] [c0001fe4f170] [c85a652c] efi_partition+0x12c/0x830
  [  242.665363] [c0001fe4f2e0] [c859e768] 
check_partition+0x158/0x2d0
  [  242.665469] [c0001fe4f360] [c859c760] 
rescan_partitions+0xe0/0x390
  [  242.665552] [c0001fe4f430] [c8371828] __blkdev_get+0x358/0x490
  [  242.665669] [c0001fe4f4a0] [c8372b50] blkdev_get+0x1a0/0x4a0
  [  242.665784] [c0001fe4f550] [c8599538] 
device_add_disk+0x4a8/0x500
  [  242.665894] [c0001fe4f600] [d0511cc8] 
virtblk_probe+0x560/0x928 [virtio_blk]
  [  242.665983] [c0001fe4f6c0] [c8687700] 
virtio_dev_probe+0x1d0/0x350
  [  242.666050] [c0001fe4f700] [c8716f30] 
driver_probe_device+0x240/0x540
  [  242.666116] [c0001fe4f790] [c871738c] 
__driver_attach+0x15c/0x160
  [  242.666174] [c0001fe4f810] [c87138ec] 
bus_for_each_dev+0x8c/0xf0
  [  242.666232] [c0001fe4f860] [c87162e4] driver_attach+0x34/0x50
  [  242.666289] [c0001fe4f880] [c8715a78] 
bus_add_driver+0x238/0x380
  [  242.666345] [c0001fe4f910] [c871829c] 
driver_register+0x9c/0x180
  [  242.666403] [c0001fe4f980] [c8686abc] 
register_virtio_driver+0x4c/0x60
  [  242.666470] [c0001fe4f9a0] [d0512114] init+0x84/0xd4 
[virtio_blk]
  [  242.666527] [c0001fe4fa10] [c800dde8] 
do_one_initcall+0x68/0x1d0
  [  242.666584] [c0001fe4fad0] [c8b28e00] do_init_module+0x90/0x244
  [  242.43] [c0001fe4fb60] [c8184794] load_module+0x1614/0x17a0
  [  242.666701] [c0001fe4fd30] [c8184c60] 
SyS_finit_module+0xf0/0x170
  [  242.666759] [c0001fe4fe30] [c800bd84] system_call+0x38/0xe0

[Kernel-packages] [Bug 1655280] Re: ISST-LTE:pVM:roselp4:ubuntu 16.04.2: cp: error reading '/proc/vmcore': Bad address when trying to dump vmcore

bug 1664545 may be related.

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

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

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

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

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

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

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

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

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

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

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

[Kernel-packages] [Bug 1714065] Re: ZFS NULL pointer dereference

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

** Tags added: kernel-da-key

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

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

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

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

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

Title:
  ZFS NULL pointer dereference

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

Bug description:
  I am using a file-backed ZFS pool for LXD containers.  I have a few
  running and I got a few ZFS null pointer dereferences that make the
  system unusable.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-33-generic 4.10.0-33.37
  ProcVersionSignature: Ubuntu 4.10.0-33.37-generic 4.10.17
  Uname: Linux 4.10.0-33-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  Date: Wed Aug 30 13:00:37 2017
  InstallationDate: Installed on 2017-04-21 (130 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Beta amd64 (20170404)
  MachineType: Micro-Star International Co., Ltd MS-7A34
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-33-generic.efi.signed 
root=UUID=1bf886cb-50ea-4487-a660-07d91bbb51fc ro quiet splash vt.handoff=7
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-33-generic N/A
   linux-backports-modules-4.10.0-33-generic  N/A
   linux-firmware 1.164.1
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/22/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.60
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: B350 TOMAHAWK (MS-7A34)
  dmi.board.vendor: Micro-Star International Co., Ltd
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Micro-Star International Co., Ltd
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.60:bd06/22/2017:svnMicro-StarInternationalCo.,Ltd:pnMS-7A34:pvr1.0:rvnMicro-StarInternationalCo.,Ltd:rnB350TOMAHAWK(MS-7A34):rvr1.0:cvnMicro-StarInternationalCo.,Ltd:ct3:cvr1.0:
  dmi.product.name: MS-7A34
  dmi.product.version: 1.0
  dmi.sys.vendor: Micro-Star International Co., Ltd

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

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

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

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

Title:
  linux: 4.4.0-94.117 -proposed tracker

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

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

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

  backports: 1713463
  derivatives: 1713464,1713465,1713467,1713468,1713469
  -- swm properties --
  boot-testing-requested: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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

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

You may need to run the following from a terminal:

sudo apt-get install -f
sudo apt-get clean
sudo apt-get update

Then re-install the package or updates.

If that does not resolve your issue, please mark the bug as "Confirmed"


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

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

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

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Software updater

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-33-generic (not installed)
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic i686
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.10.0-19-generic.
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  krzysztof   1439 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'I82801DBICH4'/'Intel 82801DB-ICH4 with AD1981B at irq 11'
 Mixer name : 'Analog Devices AD1981B'
 Components : 'AC97a:41445374'
 Controls  : 27
 Simple ctrls  : 18
  Card29.Amixer.info:
   Card hw:29 'ThinkPadEC'/'ThinkPad Console Audio Control at EC reg 0x30, fw 
1RHT71WW-3.04'
 Mixer name : 'ThinkPad EC 1RHT71WW-3.04'
 Components : ''
 Controls  : 2
 Simple ctrls  : 1
  Card29.Amixer.values:
   Simple mixer control 'Console',0
 Capabilities: pvolume pvolume-joined pswitch pswitch-joined
 Playback channels: Mono
 Limits: Playback 0 - 14
 Mono: Playback 6 [43%] [on]
  Date: Fri Sep  1 19:45:12 2017
  DuplicateSignature:
   package:linux-image-4.10.0-33-generic:(not installed)
   Preparing to unpack 
.../70-linux-image-4.10.0-33-generic_4.10.0-33.37_i386.deb ...
   This kernel does not support a non-PAE CPU.
   dpkg: error processing archive 
/tmp/apt-dpkg-install-ak6tb9/70-linux-image-4.10.0-33-generic_4.10.0-33.37_i386.deb
 (--unpack):
subprocess new pre-installation script returned error exit status 1
  ErrorMessage: subprocess new pre-installation script returned error exit 
status 1
  HibernationDevice: RESUME=UUID=510d28f0-e291-49b2-aeeb-59d71d93eaad
  InstallationDate: Installed on 2017-09-01 (0 days ago)
  InstallationMedia: Lubuntu 17.04 "Zesty Zapus" - Release i386 (20170412)
  MachineType: IBM 2373BM0
  PccardctlIdent:
   Socket 0:
 no product info available
   Socket 1:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
   Socket 1:
 no card
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-19-generic 
root=UUID=2a98691a-5408-497e-a398-f808b0cedbed ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc 2.02~beta3-4ubuntu2.2
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  Title: package linux-image-4.10.0-33-generic (not installed) failed to 
install/upgrade: subprocess new pre-installation script returned error exit 
status 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/18/2007
  dmi.bios.vendor: IBM
  dmi.bios.version: 1RETDRWW (3.23 )
  dmi.board.name: 2373BM0
  dmi.board.vendor: IBM
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: N8206
  dmi.chassis.type: 10
  dmi.chassis.vendor: IBM
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnIBM:bvr1RETDRWW(3.23):bd06/18/2007:svnIBM:pn2373BM0:pvrThinkPadT41:rvnIBM:rn2373BM0:rvrNotAvailable:cvnIBM:ct10:cvrNotAvailable:
  dmi.product.name: 2373BM0
  dmi.product.version: ThinkPad T41
  dmi.sys.vendor: IBM

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

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

[Kernel-packages] [Bug 1714485] Re: Ubuntu 16.04.03: kdump fails with error "kdump-tools[1532]: /etc/init.d/kdump-tools: 26: [: -ne: unexpected operator" when / file system is xfs.

** Tags added: kernel-da-key

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

Title:
  Ubuntu 16.04.03: kdump fails with error "kdump-tools[1532]:
  /etc/init.d/kdump-tools: 26: [: -ne: unexpected operator" when / file
  system is xfs.

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

Bug description:
  == Comment: #0 - PAVITHRA R. PRAKASH <> - 2017-08-31 00:33:37 ==
  ---Problem Description---

  Ubuntu 16.04.03: kdump fails with error "kdump-tools[1532]:
  /etc/init.d/kdump-tools: 26: [: -ne: unexpected operator" when / file
  system is xfs.

  ---Steps to Reproduce---

  1. Install Ubuntu 16.04.03 with / as xfs.
  2. Configure kdump.
  3. trigger crash.

  Machine hangs after below log. Attaching console log.

  [  OK  ] Reached target Network is Online.
   Starting Kernel crash dump capture service...
   Starting iSCSI initiator daemon (iscsid)...
  [   12.263089] kdump-tools[1205]: /etc/init.d/kdump-tools: 26: [: -ne: 
unexpected operator
  [  OK  ] Started Kernel crash dump capture service.
  [  OK  ] Started iSCSI initiator daemon (iscsid).
   Starting Login to default iSCSI targets...
  [  OK  ] Started Login to default iSCSI targets.
  [  OK  ] Reached target Remote File Systems (Pre).

  
  4. After manual reboot  /etc/default/kdump-tools is empty.

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

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

[Kernel-packages] [Bug 1714262] Re: mysql socket no longer accessible during overlayroot

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

Title:
  mysql socket no longer accessible during overlayroot

Status in linux package in Ubuntu:
  Incomplete
Status in mysql-5.7 package in Ubuntu:
  Incomplete

Bug description:
  Running on a Ubuntu 16.04.2 LTS
  install mysql through apt-get
  successfully run 'mysql' and connect
  add "tmpfs" to /etc/overlayroot.conf
  reboot the system to engage overlay
  attempt 'mysql' command and get a fail to connect to socket error
  this is repeatable by added and removing the overlay

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

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

[Kernel-packages] [Bug 1714229] Re: hwclock will set the date to 2/2/2080 with given 2/2/80

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

Title:
  hwclock will set the date to 2/2/2080 with given 2/2/80

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  On node lodygin, run:
  sudo /sbin/hwclock --set --date "2/2/80 03:04:00"

  Will set the date to 2/2/2080. Thus it failed the hwclock test, which
  expect the output of 1980

  This only happen on lodygin, other testing nodes (hainzel, rumford,
  rizzo, fozzie) are good.

  This issue has been tested on Xenial and Zesty, they will all behave
  in the same way.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-93-generic 4.4.0-93.116
  ProcVersionSignature: User Name 4.4.0-93.116-generic 4.4.79
  Uname: Linux 4.4.0-93-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Aug 31 11:27 seq
   crw-rw 1 root audio 116, 33 Aug 31 11:27 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Date: Thu Aug 31 11:36:37 2017
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  MachineType: AMD Corporation Speedway
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 astdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-93-generic 
root=UUID=e54320fc-c0c6-4801-843e-13288cad433e ro
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-93-generic N/A
   linux-backports-modules-4.4.0-93-generic  N/A
   linux-firmware1.157.11
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/24/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: RSW1001E
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Speedway
  dmi.board.vendor: AMD Corporation
  dmi.board.version: To be filled by O.E.M.
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 17
  dmi.chassis.vendor: To be filled by O.E.M.
  dmi.chassis.version: To be filled by O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrRSW1001E:bd07/24/2017:svnAMDCorporation:pnSpeedway:pvrTobefilledbyO.E.M.:rvnAMDCorporation:rnSpeedway:rvrTobefilledbyO.E.M.:cvnTobefilledbyO.E.M.:ct17:cvrTobefilledbyO.E.M.:
  dmi.product.name: Speedway
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: AMD Corporation

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

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

[Kernel-packages] [Bug 1664545] Re: In Ubuntu17.04 as Kvm guest : While trigger kdump console hung having call traces

2017-09-01 Thread Thadeu Lima de Souza Cascardo

If you add the following line to /etc/default/kdump-tools:

KDUMP_CMDLINE_APPEND="noirqdistrib irqpoll nr_cpus=1 nousb systemd.unit
=kdump-tools.service ata_piix.prefer_ms_hyperv=0"

and run:

kdump-config unload ; kdump-config load

does it fix it?

Cascardo.

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

Title:
  In Ubuntu17.04 as Kvm guest  : While trigger kdump console hung having
  call traces

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

Bug description:
  In ubuntu17.04 as KVM guest on ubuntu KVM Host and trying kdump on
  guest while kdump process  console got hung having call traces

  
  Reproducible Step:

  1- Install Ubuntu17.04 as kvm guest  on ubuntu kvm host 
  2- configure kdump 
  3- trigger kdump 

  Expected Result :

  Kdump should capture

  Actual Result :

  Kdump console hung having continuous call traces

  LOG:

  [0.488534] Freeing unused kernel memory: 4416K (c8e8 - 
c92d)
  [0.488725] This architecture does not have kernel memory protection.
  Loading, please wait...
  starting version 232
  [0.501616] random: udevadm: uninitialized urandom read (16 bytes read)
  [0.501830] random: udevadm: uninitialized urandom read (16 bytes read)
  [0.501981] random: udevadm: uninitialized urandom read (16 bytes read)
  [0.502162] random: udevadm: uninitialized urandom read (16 bytes read)
  [0.502254] random: udevadm: uninitialized urandom read (16 bytes read)
  [0.502433] random: udevadm: uninitialized urandom read (16 bytes read)
  [0.503188] random: udevadm: uninitialized urandom read (16 bytes read)
  [0.503270] random: udevadm: uninitialized urandom read (16 bytes read)
  [0.503978] random: systemd-udevd: uninitialized urandom read (16 bytes 
read)
  [0.504218] random: systemd-udevd: uninitialized urandom read (16 bytes 
read)
  [  242.663388] INFO: task systemd-udevd:151 blocked for more than 120 seconds.
  [  242.663514]   Not tainted 4.9.0-15-generic #16-Ubuntu
  [  242.663553] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [  242.663755] systemd-udevd   D0   151145 0x00040002
  [  242.663795] Call Trace:
  [  242.663868] [c0001fe4ecd0] [c801c3a0] __switch_to+0x2e0/0x4c0
  [  242.663964] [c0001fe4ed30] [c8b19398] __schedule+0x2f8/0x990
  [  242.664076] [c0001fe4ee10] [c8b19a78] schedule+0x48/0xc0
  [  242.664179] [c0001fe4ee40] [c8b1de54] 
schedule_timeout+0x274/0x470
  [  242.664334] [c0001fe4ef30] [c8b19010] 
io_schedule_timeout+0xd0/0x160
  [  242.664502] [c0001fe4ef80] [c8b1a720] bit_wait_io+0x30/0x90
  [  242.664618] [c0001fe4efb0] [c8b1a168] __wait_on_bit+0xf8/0x170
  [  242.664754] [c0001fe4f000] [c824b238] 
wait_on_page_bit+0x98/0xb0
  [  242.664847] [c0001fe4f060] [c824d60c] 
do_read_cache_page+0x21c/0x4e0
  [  242.665008] [c0001fe4f0d0] [c859be78] 
read_dev_sector+0xb8/0x140
  [  242.665126] [c0001fe4f100] [c85a5d88] 
read_lba.isra.0+0x148/0x250
  [  242.665259] [c0001fe4f170] [c85a652c] efi_partition+0x12c/0x830
  [  242.665363] [c0001fe4f2e0] [c859e768] 
check_partition+0x158/0x2d0
  [  242.665469] [c0001fe4f360] [c859c760] 
rescan_partitions+0xe0/0x390
  [  242.665552] [c0001fe4f430] [c8371828] __blkdev_get+0x358/0x490
  [  242.665669] [c0001fe4f4a0] [c8372b50] blkdev_get+0x1a0/0x4a0
  [  242.665784] [c0001fe4f550] [c8599538] 
device_add_disk+0x4a8/0x500
  [  242.665894] [c0001fe4f600] [d0511cc8] 
virtblk_probe+0x560/0x928 [virtio_blk]
  [  242.665983] [c0001fe4f6c0] [c8687700] 
virtio_dev_probe+0x1d0/0x350
  [  242.666050] [c0001fe4f700] [c8716f30] 
driver_probe_device+0x240/0x540
  [  242.666116] [c0001fe4f790] [c871738c] 
__driver_attach+0x15c/0x160
  [  242.666174] [c0001fe4f810] [c87138ec] 
bus_for_each_dev+0x8c/0xf0
  [  242.666232] [c0001fe4f860] [c87162e4] driver_attach+0x34/0x50
  [  242.666289] [c0001fe4f880] [c8715a78] 
bus_add_driver+0x238/0x380
  [  242.666345] [c0001fe4f910] [c871829c] 
driver_register+0x9c/0x180
  [  242.666403] [c0001fe4f980] [c8686abc] 
register_virtio_driver+0x4c/0x60
  [  242.666470] [c0001fe4f9a0] [d0512114] init+0x84/0xd4 
[virtio_blk]
  [  242.666527] [c0001fe4fa10] [c800dde8] 
do_one_initcall+0x68/0x1d0
  [  242.666584] [c0001fe4fad0] [c8b28e00] do_init_module+0x90/0x244
  [  242.43] [c0001fe4fb60] [c8184794] load_module+0x1614/0x17a0
  [  242.666701] [c0001fe4fd30] [c8184c60] 
SyS_finit_module+0xf0/0x170
  [  242.666759] [c0001

[Kernel-packages] [Bug 1714485] Re: Ubuntu 16.04.03: kdump fails with error "kdump-tools[1532]: /etc/init.d/kdump-tools: 26: [: -ne: unexpected operator" when / file system is xfs.

2017-09-01 Thread Thadeu Lima de Souza Cascardo

What is the content of /etc/default/kdump-tools ? It seems it doesn't
have USE_KDUMP set at all.

Cascardo.

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

Title:
  Ubuntu 16.04.03: kdump fails with error "kdump-tools[1532]:
  /etc/init.d/kdump-tools: 26: [: -ne: unexpected operator" when / file
  system is xfs.

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

Bug description:
  == Comment: #0 - PAVITHRA R. PRAKASH <> - 2017-08-31 00:33:37 ==
  ---Problem Description---

  Ubuntu 16.04.03: kdump fails with error "kdump-tools[1532]:
  /etc/init.d/kdump-tools: 26: [: -ne: unexpected operator" when / file
  system is xfs.

  ---Steps to Reproduce---

  1. Install Ubuntu 16.04.03 with / as xfs.
  2. Configure kdump.
  3. trigger crash.

  Machine hangs after below log. Attaching console log.

  [  OK  ] Reached target Network is Online.
   Starting Kernel crash dump capture service...
   Starting iSCSI initiator daemon (iscsid)...
  [   12.263089] kdump-tools[1205]: /etc/init.d/kdump-tools: 26: [: -ne: 
unexpected operator
  [  OK  ] Started Kernel crash dump capture service.
  [  OK  ] Started iSCSI initiator daemon (iscsid).
   Starting Login to default iSCSI targets...
  [  OK  ] Started Login to default iSCSI targets.
  [  OK  ] Reached target Remote File Systems (Pre).

  
  4. After manual reboot  /etc/default/kdump-tools is empty.

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

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

[Kernel-packages] [Bug 1714112] Re: EDAC sbridge: Failed to register device with error -22.

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

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

** Also affects: linux (Ubuntu Artful)
   Importance: Medium
   Status: Triaged

** Tags added: kernel-da-key

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

Title:
  EDAC sbridge: Failed to register device with error -22.

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

Bug description:
  These kernel error messages appear with artful kernel
  4.12.0-11-generic.

  EDAC sbridge: Couldn't find mci handler
  EDAC sbridge: Couldn't find mci handler
  EDAC sbridge: Failed to register device with error -22.

  EDAC_GHES is enable in 4.12.0-11-generic, but according to
  https://lkml.org/lkml/2017/7/9/258 it should be disabled.

  $ grep CONFIG_EDAC /boot/config-4.12.0-11-generic 
  CONFIG_EDAC_ATOMIC_SCRUB=y
  CONFIG_EDAC_SUPPORT=y
  CONFIG_EDAC=y
  # CONFIG_EDAC_LEGACY_SYSFS is not set
  # CONFIG_EDAC_DEBUG is not set
  CONFIG_EDAC_DECODE_MCE=m
  CONFIG_EDAC_GHES=y
  CONFIG_EDAC_AMD64=m
  # CONFIG_EDAC_AMD64_ERROR_INJECTION is not set
  CONFIG_EDAC_E752X=m
  CONFIG_EDAC_I82975X=m
  CONFIG_EDAC_I3000=m
  CONFIG_EDAC_I3200=m
  CONFIG_EDAC_IE31200=m
  CONFIG_EDAC_X38=m
  CONFIG_EDAC_I5400=m
  CONFIG_EDAC_I7CORE=m
  CONFIG_EDAC_I5000=m
  CONFIG_EDAC_I5100=m
  CONFIG_EDAC_I7300=m
  CONFIG_EDAC_SBRIDGE=m
  CONFIG_EDAC_SKX=m
  CONFIG_EDAC_PND2=m

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

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

[Kernel-packages] [Bug 1714229] Re: hwclock will set the date to 2/2/2080 with given 2/2/80

** Tags added: kernel-da-key

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

Title:
  hwclock will set the date to 2/2/2080 with given 2/2/80

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  On node lodygin, run:
  sudo /sbin/hwclock --set --date "2/2/80 03:04:00"

  Will set the date to 2/2/2080. Thus it failed the hwclock test, which
  expect the output of 1980

  This only happen on lodygin, other testing nodes (hainzel, rumford,
  rizzo, fozzie) are good.

  This issue has been tested on Xenial and Zesty, they will all behave
  in the same way.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-93-generic 4.4.0-93.116
  ProcVersionSignature: User Name 4.4.0-93.116-generic 4.4.79
  Uname: Linux 4.4.0-93-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Aug 31 11:27 seq
   crw-rw 1 root audio 116, 33 Aug 31 11:27 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Date: Thu Aug 31 11:36:37 2017
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  MachineType: AMD Corporation Speedway
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 astdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-93-generic 
root=UUID=e54320fc-c0c6-4801-843e-13288cad433e ro
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-93-generic N/A
   linux-backports-modules-4.4.0-93-generic  N/A
   linux-firmware1.157.11
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/24/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: RSW1001E
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Speedway
  dmi.board.vendor: AMD Corporation
  dmi.board.version: To be filled by O.E.M.
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 17
  dmi.chassis.vendor: To be filled by O.E.M.
  dmi.chassis.version: To be filled by O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrRSW1001E:bd07/24/2017:svnAMDCorporation:pnSpeedway:pvrTobefilledbyO.E.M.:rvnAMDCorporation:rnSpeedway:rvrTobefilledbyO.E.M.:cvnTobefilledbyO.E.M.:ct17:cvrTobefilledbyO.E.M.:
  dmi.product.name: Speedway
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: AMD Corporation

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

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

[Kernel-packages] [Bug 1714112] Re: EDAC sbridge: Failed to register device with error -22.

2017-09-01 Thread Seth Forshee

Funny, the Kconfig help text says it should be enabled. They need to
make up their minds :-P

I found a branch which I think has the fixes, but it looks to me like
they are still testing it. So for now I'll disable that option.

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

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

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

Title:
  EDAC sbridge: Failed to register device with error -22.

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

Bug description:
  These kernel error messages appear with artful kernel
  4.12.0-11-generic.

  EDAC sbridge: Couldn't find mci handler
  EDAC sbridge: Couldn't find mci handler
  EDAC sbridge: Failed to register device with error -22.

  EDAC_GHES is enable in 4.12.0-11-generic, but according to
  https://lkml.org/lkml/2017/7/9/258 it should be disabled.

  $ grep CONFIG_EDAC /boot/config-4.12.0-11-generic 
  CONFIG_EDAC_ATOMIC_SCRUB=y
  CONFIG_EDAC_SUPPORT=y
  CONFIG_EDAC=y
  # CONFIG_EDAC_LEGACY_SYSFS is not set
  # CONFIG_EDAC_DEBUG is not set
  CONFIG_EDAC_DECODE_MCE=m
  CONFIG_EDAC_GHES=y
  CONFIG_EDAC_AMD64=m
  # CONFIG_EDAC_AMD64_ERROR_INJECTION is not set
  CONFIG_EDAC_E752X=m
  CONFIG_EDAC_I82975X=m
  CONFIG_EDAC_I3000=m
  CONFIG_EDAC_I3200=m
  CONFIG_EDAC_IE31200=m
  CONFIG_EDAC_X38=m
  CONFIG_EDAC_I5400=m
  CONFIG_EDAC_I7CORE=m
  CONFIG_EDAC_I5000=m
  CONFIG_EDAC_I5100=m
  CONFIG_EDAC_I7300=m
  CONFIG_EDAC_SBRIDGE=m
  CONFIG_EDAC_SKX=m
  CONFIG_EDAC_PND2=m

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

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

[Kernel-packages] [Bug 1705447] Re: misleading kernel warning skb_warn_bad_offload during checksum calculation

@manojav, since the original bug reporter, mailkons, says this bug is
now fixed, you may want to open a new separate bug to track your issue.

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

Title:
  misleading kernel warning skb_warn_bad_offload during checksum
  calculation

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

Bug description:
  Even when the packet says checksum calculation is unnecessary the
  kernel will still check the checksum and display a warning that the
  checksum is bad.

  This has been fixed upstream in Kernel 4.11 by commit id:
  b2504a5dbef3305ef41988ad270b0e8ec289331c

  We have reports of Ubuntu 16.04 virtual machines (with ip forward
  enabled) displaying these warnings:

  
  [10480.074664] [ cut here ]
  [10480.074667] WARNING: CPU: 1 PID: 0 at 
/build/linux-hwe-X3pKE5/linux-hwe-4.8.0/net/core/dev.c:2444 
skb_warn_bad_offload+0xd1/0x120
  [10480.074669] docker0: caps=(0x0400ffbb78e9, 0x) 
len=2962 data_len=2834 gso_size=1448 gso_type=5 ip_summed=1
  [10480.074670] Modules linked in: veth nfsv3 nfs_acl rpcsec_gss_krb5 
auth_rpcgss nfsv4 nfs lockd grace sunrpc fscache ipt_MASQUERADE 
nf_nat_masquerade_ipv4 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 zfs(PO) 
zunicode(PO) zcommon(PO) znvpair(PO) spl(O) zavl(PO) crct10dif_pclmul 
crc32_pclmul ghash_clmulni_intel aesni_intel aes_x86_64 lrw glue_helper 
ablk_helper cryptd input_leds joydev serio_raw i2c_piix4 mac_hid parport_pc 
ppdev lp parport autofs4 hid_generic usbhid hid virtio_scsi psmouse virtio_net 
pata_acpi floppy
  [10480.074695] CPU: 1 PID: 0 Comm: swapper/1 Tainted: PW  O
4.8.0-52-generic #55~16.04.1-Ubuntu
  [10480.074696] Hardware name: Nutanix AHV, BIOS seabios-1.7.5-11.el6 
04/01/2014
  [10480.074697]  0286 ec176c2ae03bc036 8beef5643870 
b7a2e7b3
  [10480.074699]  8beef56438c0  8beef56438b0 
b768314b
  [10480.074702]  098cb84fba80 8bed61f82000 8bee9915c000 
0005
  [10480.074704] Call Trace:
  [10480.074704][] dump_stack+0x63/0x90
  [10480.074708]  [] __warn+0xcb/0xf0
  [10480.074710]  [] warn_slowpath_fmt+0x5f/0x80
  [10480.074713]  [] ? ___ratelimit+0xa2/0xf0
  [10480.074714]  [] skb_warn_bad_offload+0xd1/0x120
  [10480.074716]  [] __skb_gso_segment+0xd8/0x140
  [10480.074717]  [] validate_xmit_skb+0x14f/0x2a0
  [10480.074719]  [] __dev_queue_xmit+0x322/0x6d0
  [10480.074720]  [] ? nf_nat_ipv4_fn+0x1a6/0x230 
[nf_nat_ipv4]
  [10480.074723]  [] dev_queue_xmit+0x10/0x20
  [10480.074725]  [] ip_finish_output2+0x292/0x380
  [10480.074726]  [] ? ipv4_confirm+0x7d/0x100 
[nf_conntrack_ipv4]
  [10480.074728]  [] ip_finish_output+0x132/0x1d0
  [10480.074729]  [] ? nf_hook_slow+0x73/0xd0
  [10480.074731]  [] ip_output+0x6e/0xf0
  [10480.074733]  [] ? 
__ip_flush_pending_frames.isra.40+0x90/0x90
  [10480.074736]  [] ip_forward_finish+0x43/0x70
  [10480.074738]  [] ip_forward+0x384/0x480
  [10480.074739]  [] ? ip_frag_mem+0x50/0x50
  [10480.074741]  [] ip_rcv_finish+0x11b/0x400
  [10480.074743]  [] ip_rcv+0x28b/0x3c0
  [10480.074744]  [] ? inet_del_offload+0x40/0x40
  [10480.074746]  [] __netif_receive_skb_core+0x524/0xab0
  [10480.074747]  [] ? kmem_cache_alloc+0xd7/0x1b0
  [10480.074749]  [] ? __build_skb+0x2a/0xe0
  [10480.074751]  [] __netif_receive_skb+0x18/0x60
  [10480.074753]  [] netif_receive_skb_internal+0x32/0xa0
  [10480.074754]  [] napi_gro_receive+0xcd/0x120
  [10480.074756]  [] virtnet_receive+0x1c3/0x970 [virtio_net]
  [10480.074758]  [] ? update_cfs_rq_load_avg+0x1f9/0x4c0
  [10480.074760]  [] virtnet_poll+0x1d/0x80 [virtio_net]
  [10480.074762]  [] net_rx_action+0x238/0x380
  [10480.074764]  [] __do_softirq+0xf6/0x280
  [10480.074765]  [] irq_exit+0xa3/0xb0
  [10480.074766]  [] do_IRQ+0x54/0xd0
  [10480.074768]  [] common_interrupt+0x82/0x82
  [10480.074768][] ? native_safe_halt+0x6/0x10
  [10480.074772]  [] default_idle+0x1e/0xd0
  [10480.074774]  [] arch_cpu_idle+0xf/0x20
  [10480.074775]  [] default_idle_call+0x2a/0x40
  [10480.074776]  [] cpu_startup_entry+0x2ea/0x350
  [10480.074778]  [] start_secondary+0x151/0x190
  [10480.074781] ---[ end trace 3a9bd18de5564b05 ]---

  
  We have recompiled your latest 16.04.2 kernel with this patch and confirmed 
that this warning does not happen. Could you please consider including this fix 
in your next 16.04 LTS release?

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

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

[Kernel-packages] [Bug 1714112] Re: EDAC sbridge: Failed to register device with error -22.

2017-09-01 Thread Seth Forshee

** Changed in: linux (Ubuntu Artful)
   Status: In Progress => Fix Committed

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

Title:
  EDAC sbridge: Failed to register device with error -22.

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

Bug description:
  These kernel error messages appear with artful kernel
  4.12.0-11-generic.

  EDAC sbridge: Couldn't find mci handler
  EDAC sbridge: Couldn't find mci handler
  EDAC sbridge: Failed to register device with error -22.

  EDAC_GHES is enable in 4.12.0-11-generic, but according to
  https://lkml.org/lkml/2017/7/9/258 it should be disabled.

  $ grep CONFIG_EDAC /boot/config-4.12.0-11-generic 
  CONFIG_EDAC_ATOMIC_SCRUB=y
  CONFIG_EDAC_SUPPORT=y
  CONFIG_EDAC=y
  # CONFIG_EDAC_LEGACY_SYSFS is not set
  # CONFIG_EDAC_DEBUG is not set
  CONFIG_EDAC_DECODE_MCE=m
  CONFIG_EDAC_GHES=y
  CONFIG_EDAC_AMD64=m
  # CONFIG_EDAC_AMD64_ERROR_INJECTION is not set
  CONFIG_EDAC_E752X=m
  CONFIG_EDAC_I82975X=m
  CONFIG_EDAC_I3000=m
  CONFIG_EDAC_I3200=m
  CONFIG_EDAC_IE31200=m
  CONFIG_EDAC_X38=m
  CONFIG_EDAC_I5400=m
  CONFIG_EDAC_I7CORE=m
  CONFIG_EDAC_I5000=m
  CONFIG_EDAC_I5100=m
  CONFIG_EDAC_I7300=m
  CONFIG_EDAC_SBRIDGE=m
  CONFIG_EDAC_SKX=m
  CONFIG_EDAC_PND2=m

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

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

[Kernel-packages] [Bug 1712867] Re: [Hyper-V] 16.04 kexec-tools doesn't match linux-azure

2017-09-01 Thread Steve Langasek

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

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

Title:
  [Hyper-V] 16.04 kexec-tools doesn't match linux-azure

Status in linux-azure package in Ubuntu:
  In Progress
Status in makedumpfile package in Ubuntu:
  New
Status in linux-azure source package in Xenial:
  In Progress
Status in makedumpfile source package in Xenial:
  New

Bug description:
  Because the linux-azure kernel is based on 4.11, kexec on 16.04 gives the 
following error:
  kdump-tools[1436]: ELF core (kcore) parse failed

  Perhaps the artful kexec-tools should be backported?

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

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

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

@furmanek, The fix is in the Ubuntu-4.4.0-94 kernel, which is the
current -proposed kernel.

Would it be possible for you to test the proposed kernel and post back if it 
resolves this bug?
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to 
enable and use -proposed. 

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

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

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

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

Title:
  KVM on 16.04.3 throws an error

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

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

  install KVM like:

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

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

  then run my spawn script

  $ cat spawn.sh
  #!/bin/bash

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

  with a freshly downloaded ubuntu cloud image

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

  And I get nothing on the output.

  and errors in dmesg

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

[Kernel-packages] [Bug 1696049] Re: xfstest sanity checks on seek operations fails

I'd like to perform a reverse bisect to figure out which commit upstream fixes 
this regression.  We need to figure out  the last kernel that had this issue 
and the first kernel that did not.
Can you test the following kernels and report back? We are looking for the last 
kernel version that has the bug and the first that does not:

v4.11-rc1: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.11-rc1/
v4.11-rc4: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.11-rc4/
v4.11-rc7: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.11-rc8/

You don't have to test every kernel, just up until the first kernel that
does not have this bug.

Thanks in advance!

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

Title:
  xfstest sanity checks on seek operations fails

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

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

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

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

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

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

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

  seek sanity check failed!

  Full log is attached.

  == Comment: #6 - Harish Sriram

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

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

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

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

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

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

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

--- Comment From hbath...@in.ibm.com 2017-09-01 11:37 EDT---
(In reply to comment #8)
> == Comment: #0 - PAVITHRA R. PRAKASH <> - 2017-08-31 00:33:37 ==
> ---Problem Description---
>
> Ubuntu 16.04.03: kdump fails with error "kdump-tools[1532]:
> /etc/init.d/kdump-tools: 26: [: -ne: unexpected operator" when / file system
> is xfs.
> 4. After manual reboot  /etc/default/kdump-tools is empty.
>

Hello Cascardo,

The file is ending up empty..

Thanks
Hari

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

Title:
  Ubuntu 16.04.03: kdump fails with error "kdump-tools[1532]:
  /etc/init.d/kdump-tools: 26: [: -ne: unexpected operator" when / file
  system is xfs.

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

Bug description:
  == Comment: #0 - PAVITHRA R. PRAKASH <> - 2017-08-31 00:33:37 ==
  ---Problem Description---

  Ubuntu 16.04.03: kdump fails with error "kdump-tools[1532]:
  /etc/init.d/kdump-tools: 26: [: -ne: unexpected operator" when / file
  system is xfs.

  ---Steps to Reproduce---

  1. Install Ubuntu 16.04.03 with / as xfs.
  2. Configure kdump.
  3. trigger crash.

  Machine hangs after below log. Attaching console log.

  [  OK  ] Reached target Network is Online.
   Starting Kernel crash dump capture service...
   Starting iSCSI initiator daemon (iscsid)...
  [   12.263089] kdump-tools[1205]: /etc/init.d/kdump-tools: 26: [: -ne: 
unexpected operator
  [  OK  ] Started Kernel crash dump capture service.
  [  OK  ] Started iSCSI initiator daemon (iscsid).
   Starting Login to default iSCSI targets...
  [  OK  ] Started Login to default iSCSI targets.
  [  OK  ] Reached target Remote File Systems (Pre).

  
  4. After manual reboot  /etc/default/kdump-tools is empty.

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

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

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

--- Comment From hbath...@in.ibm.com 2017-09-01 11:38 EDT---
(In reply to comment #25)
> bug 1655280 may be related.
>
> If you add the following line to /etc/default/kdump-tools:
>
> KDUMP_CMDLINE_APPEND="noirqdistrib irqpoll nr_cpus=1 nousb
> systemd.unit=kdump-tools.service ata_piix.prefer_ms_hyperv=0"
>
> and run:
>
> kdump-config unload ; kdump-config load
>
> does it fix it?
>

Hello Cascardo, passing "noirqdistrib" helps..

Thanks
Hari

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

Title:
  In Ubuntu17.04 as Kvm guest  : While trigger kdump console hung having
  call traces

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

Bug description:
  In ubuntu17.04 as KVM guest on ubuntu KVM Host and trying kdump on
  guest while kdump process  console got hung having call traces

  
  Reproducible Step:

  1- Install Ubuntu17.04 as kvm guest  on ubuntu kvm host 
  2- configure kdump 
  3- trigger kdump 

  Expected Result :

  Kdump should capture

  Actual Result :

  Kdump console hung having continuous call traces

  LOG:

  [0.488534] Freeing unused kernel memory: 4416K (c8e8 - 
c92d)
  [0.488725] This architecture does not have kernel memory protection.
  Loading, please wait...
  starting version 232
  [0.501616] random: udevadm: uninitialized urandom read (16 bytes read)
  [0.501830] random: udevadm: uninitialized urandom read (16 bytes read)
  [0.501981] random: udevadm: uninitialized urandom read (16 bytes read)
  [0.502162] random: udevadm: uninitialized urandom read (16 bytes read)
  [0.502254] random: udevadm: uninitialized urandom read (16 bytes read)
  [0.502433] random: udevadm: uninitialized urandom read (16 bytes read)
  [0.503188] random: udevadm: uninitialized urandom read (16 bytes read)
  [0.503270] random: udevadm: uninitialized urandom read (16 bytes read)
  [0.503978] random: systemd-udevd: uninitialized urandom read (16 bytes 
read)
  [0.504218] random: systemd-udevd: uninitialized urandom read (16 bytes 
read)
  [  242.663388] INFO: task systemd-udevd:151 blocked for more than 120 seconds.
  [  242.663514]   Not tainted 4.9.0-15-generic #16-Ubuntu
  [  242.663553] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [  242.663755] systemd-udevd   D0   151145 0x00040002
  [  242.663795] Call Trace:
  [  242.663868] [c0001fe4ecd0] [c801c3a0] __switch_to+0x2e0/0x4c0
  [  242.663964] [c0001fe4ed30] [c8b19398] __schedule+0x2f8/0x990
  [  242.664076] [c0001fe4ee10] [c8b19a78] schedule+0x48/0xc0
  [  242.664179] [c0001fe4ee40] [c8b1de54] 
schedule_timeout+0x274/0x470
  [  242.664334] [c0001fe4ef30] [c8b19010] 
io_schedule_timeout+0xd0/0x160
  [  242.664502] [c0001fe4ef80] [c8b1a720] bit_wait_io+0x30/0x90
  [  242.664618] [c0001fe4efb0] [c8b1a168] __wait_on_bit+0xf8/0x170
  [  242.664754] [c0001fe4f000] [c824b238] 
wait_on_page_bit+0x98/0xb0
  [  242.664847] [c0001fe4f060] [c824d60c] 
do_read_cache_page+0x21c/0x4e0
  [  242.665008] [c0001fe4f0d0] [c859be78] 
read_dev_sector+0xb8/0x140
  [  242.665126] [c0001fe4f100] [c85a5d88] 
read_lba.isra.0+0x148/0x250
  [  242.665259] [c0001fe4f170] [c85a652c] efi_partition+0x12c/0x830
  [  242.665363] [c0001fe4f2e0] [c859e768] 
check_partition+0x158/0x2d0
  [  242.665469] [c0001fe4f360] [c859c760] 
rescan_partitions+0xe0/0x390
  [  242.665552] [c0001fe4f430] [c8371828] __blkdev_get+0x358/0x490
  [  242.665669] [c0001fe4f4a0] [c8372b50] blkdev_get+0x1a0/0x4a0
  [  242.665784] [c0001fe4f550] [c8599538] 
device_add_disk+0x4a8/0x500
  [  242.665894] [c0001fe4f600] [d0511cc8] 
virtblk_probe+0x560/0x928 [virtio_blk]
  [  242.665983] [c0001fe4f6c0] [c8687700] 
virtio_dev_probe+0x1d0/0x350
  [  242.666050] [c0001fe4f700] [c8716f30] 
driver_probe_device+0x240/0x540
  [  242.666116] [c0001fe4f790] [c871738c] 
__driver_attach+0x15c/0x160
  [  242.666174] [c0001fe4f810] [c87138ec] 
bus_for_each_dev+0x8c/0xf0
  [  242.666232] [c0001fe4f860] [c87162e4] driver_attach+0x34/0x50
  [  242.666289] [c0001fe4f880] [c8715a78] 
bus_add_driver+0x238/0x380
  [  242.666345] [c0001fe4f910] [c871829c] 
driver_register+0x9c/0x180
  [  242.666403] [c0001fe4f980] [c8686abc] 
register_virtio_driver+0x4c/0x60
  [  242.666470] [c0001fe4f9a0] [d0512114] init+0x84/0xd4 
[virtio_blk]
  [  242.666527] [c0001fe4fa10] [c800dde8] 
do_one_initcall+0x68/0x1d0
  [  242.666584] [c0001fe4fad0] [c8b28e00] do_init_module+0x90/0x24

[Kernel-packages] [Bug 1709171] Re: Disable CONFIG_MEMORY_HOTPLUG_DEFAULT_ONLINE

--- Comment From ar...@us.ibm.com 2017-09-01 11:59 EDT---
> This bug is awaiting verification that the kernel in -proposed solves the
> problem. Please test the kernel and update this bug with the results. If the
> problem is solved, change the tag 'verification-needed-zesty' to
> 'verification-done-zesty'.

I verified that linux-image-4.10.0-34-generic/zesty-proposed is fixed.

** Tags removed: verification-needed-zesty
** Tags added: verification-done-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/1709171

Title:
  Disable CONFIG_MEMORY_HOTPLUG_DEFAULT_ONLINE

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

Bug description:
  == SRU Justification ==
  IBM is requesting that we disable CONFIG_MEMORY_HOTPLUG_DEFAULT_ONLINE in 
  the current ppc64el kernels up to 16.04.3.

  This was requested originally in LP#1706380, but it was not integrated
  in that bug.

  This chanage has already been made in Artful(Commit 8f189e08c9a), so that 
  is where I cherry picked the patch from.

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

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

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