[Kernel-packages] [Bug 1742722] Re: linux: 4.13.0-29.32 -proposed tracker

2018-01-12 Thread Steve Beattie
** Changed in: kernel-sru-workflow/security-signoff
   Status: Confirmed => In Progress

** Changed in: kernel-sru-workflow/security-signoff
 Assignee: Canonical Security Team (canonical-security) => Steve Beattie 
(sbeattie)

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

Title:
  linux: 4.13.0-29.32 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Confirmed
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 Artful:
  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: 1742723,1742725,1742726,1742727,1742728,1742928
  derivatives: 1742730
  -- 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/1742722/+subscriptions

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


[Kernel-packages] [Bug 1720557] Re: System freeze on attempt to suspend

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

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

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

Title:
  System freeze on attempt to suspend

Status in linux package in Ubuntu:
  Expired

Bug description:
  1. New install of 17.10 beta 2 on XPS 13 9350. Intel gpu and using wayland 
(enabled by default)
  2. Select top right menu, hold alt, select suspend button

  I expect the laptop to suspend. Instead the screen goes blank. The
  laptop remained on (power button is light, fans are on). The laptop is
  unresponsive until hard reboot (holding down power button). A
  suspended state is never reached.

  The laptop previously suspended fine on 17.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-12-generic 4.13.0-12.13 [modified: 
boot/vmlinuz-4.13.0-12-generic]
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   david  1388 F...m pulseaudio
   /dev/snd/controlC0:  david  1388 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Sep 30 12:18:05 2017
  InstallationDate: Installed on 2017-09-30 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  MachineType: Dell Inc. XPS 13 9350
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-12-generic.efi.signed 
root=UUID=a7e24755-5141-4ab1-a8d4-e4da5ebfe9ce ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-12-generic N/A
   linux-backports-modules-4.13.0-12-generic  N/A
   linux-firmware 1.168
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/18/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.5.1
  dmi.board.name: 09JHRY
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.5.1:bd08/18/2017:svnDellInc.:pnXPS139350:pvr:rvnDellInc.:rn09JHRY:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.family: NULL
  dmi.product.name: XPS 13 9350
  dmi.sys.vendor: Dell Inc.

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

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


[Kernel-packages] [Bug 1710877] Re: Fn Keys Not working Ubuntu 16.04 Asus FX553Vd

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

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

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

Title:
   Fn Keys Not working Ubuntu 16.04 Asus FX553Vd

Status in linux package in Ubuntu:
  Expired

Bug description:
  Hi,

  I have an ASUS FX553VD machne. Some of my Fn keys are not working. For 
example,
  Fn+F5/F6 to increase/decrease the brightness and Fn+F3/F4 to adjust the 
keyboard LED brightness and Fn+F2(Airplane Mode).

  sudo dmidecode -s bios-version
  GL553VD.302

  uname-a
  Linux mlp-GL553VD 4.4.0-91-generic #114-Ubuntu SMP Tue Aug 8 11:56:56 UTC 
2017 x86_64 x86_64 x86_64 GNU/Linux

  dmesg | grep -i asus

  [ 0.00] ACPI: RSDP 0x7AAA4000 24 (v02 _ASUS_)
  [ 0.00] ACPI: XSDT 0x7AAA40B8 F4 (v01 _ASUS_ Notebook 
01072009 AMI 00010013)
  [ 0.00] ACPI: FACP 0x7AAD3618 000114 (v06 _ASUS_ Notebook 
01072009 AMI 00010013)
  [ 0.00] ACPI: DSDT 0x7AAA4240 02F3D8 (v02 _ASUS_ Notebook 
01072009 INTL 20160422)
  [ 0.00] ACPI: APIC 0x7AAD3730 BC (v03 _ASUS_ Notebook 
01072009 AMI 00010013)
  [ 0.00] ACPI: FPDT 0x7AAD37F0 44 (v01 _ASUS_ Notebook 
01072009 AMI 00010013)
  [ 0.00] ACPI: MCFG 0x7AAD3838 3C (v01 _ASUS_ Notebook 
01072009 MSFT 0097)
  [ 0.00] ACPI: FIDT 0x7AAD3B70 9C (v01 _ASUS_ Notebook 
01072009 AMI 00010013)
  [ 0.00] ACPI: BGRT 0x7AADE938 38 (v01 _ASUS_ Notebook 
01072009 AMI 00010013)
  [ 0.046989] Hardware name: ASUSTeK COMPUTER INC. GL553VD/GL553VD, BIOS 
GL553VD.302 03/06/2017
  [ 3.113648] asus_wmi: ASUS WMI generic driver loaded
  [ 3.114634] asus_wmi: Initialization: 0x1
  [ 3.114680] asus_wmi: BIOS WMI version: 8.1
  [ 3.114732] asus_wmi: SFUN value: 0x4a0061
  [ 3.115047] input: Asus WMI hotkeys as 
/devices/platform/asus-nb-wmi/input/input9
  [ 3.115210] asus_wmi: Number of fans: 1

  sudo evtest
  No device specified, trying to scan all of /dev/input/event*
  Available devices:
  /dev/input/event0:Sleep Button
  /dev/input/event1:Power Button
  /dev/input/event2:Lid Switch
  /dev/input/event3:Power Button
  /dev/input/event4:AT Translated Set 2 keyboard
  /dev/input/event5:Video Bus
  /dev/input/event6:Video Bus
  /dev/input/event7:ITE Tech. Inc. ITE Device(8910)
  /dev/input/event8:Asus WMI hotkeys
  /dev/input/event9:USB2.0 UVC HD Webcam
  /dev/input/event10:   HDA Intel PCH Headphone
  /dev/input/event11:   HDA Intel PCH HDMI/DP,pcm=3
  /dev/input/event12:   HDA Intel PCH HDMI/DP,pcm=7
  /dev/input/event13:   HDA Intel PCH HDMI/DP,pcm=8
  /dev/input/event14:   ELAN1200:00 04F3:3045 Touchpad
  Select the device event number [0-14]:
  ---
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  mlp1552 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=2b0f4c5d-67b4-4f86-b6a4-1c8f92998187
  InstallationDate: Installed on 2017-08-14 (1 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2a Intel Corp.
   Bus 001 Device 002: ID 13d3:5654 IMC Networks
   Bus 001 Device 004: ID 0b05:1854 ASUSTek Computer, Inc.
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. GL553VD
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-91-generic.efi.signed 
root=UUID=40c41303-9bd9-4238-b4eb-8d1ec7845bfe ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-91.114-generic 4.4.76
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-91-generic N/A
   linux-backports-modules-4.4.0-91-generic  N/A
   linux-firmware1.157.11
  Tags:  xenial
  Uname: Linux 4.4.0-91-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 03/06/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: GL553VD.302
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: GL553VD
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No  Asset  Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrGL553VD.302:bd03/06/2017:svnASUSTeKCOMPUTERINC.:pnGL553VD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGL553VD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: GL553VD
  

[Kernel-packages] [Bug 1742998] Re: linux-aws: 4.4.0-1011.11 -proposed tracker

2018-01-12 Thread Brad Figg
** Changed in: kernel-sru-workflow/prepare-package
   Status: In Progress => Fix Released

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

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

** Tags added: block-proposed-trusty

** Tags added: block-proposed

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  kernel-stable-master-bug: 1742995
+ kernel-stable-phase:Uploaded
+ kernel-stable-phase-changed:Saturday, 13. January 2018 02:31 UTC

** Description changed:

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

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

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

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

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

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

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

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


[Kernel-packages] [Bug 1742995] Re: linux: 4.4.0-110.133 -proposed tracker

2018-01-12 Thread Brad Figg
** Changed in: kernel-sru-workflow/prepare-package
   Status: In Progress => Fix Released

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

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

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

** Tags added: block-proposed-xenial

** Tags added: block-proposed

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  backports: 1742996,1742998
  derivatives: 1742999,1743000,1743001,1743002,1743004,1743006
+ kernel-stable-phase:Uploaded
+ kernel-stable-phase-changed:Saturday, 13. January 2018 02:21 UTC

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  backports: 1742996,1742998
  derivatives: 1742999,1743000,1743001,1743002,1743004,1743006
  kernel-stable-phase:Uploaded
  kernel-stable-phase-changed:Saturday, 13. January 2018 02:21 UTC
+ 
+ -- swm properties --
+ boot-testing-requested: true
+ phase: Uploaded

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

Title:
  linux: 4.4.0-110.133 -proposed tracker

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

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

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

  backports: 1742996,1742998
  derivatives: 1742999,1743000,1743001,1743002,1743004,1743006
  kernel-stable-phase:Uploaded
  kernel-stable-phase-changed:Saturday, 13. January 2018 02:21 UTC

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

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

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


[Kernel-packages] [Bug 1743001] Re: linux-aws: 4.4.0-1049.58 -proposed tracker

2018-01-12 Thread Brad Figg
** Changed in: kernel-sru-workflow/prepare-package
   Status: In Progress => Fix Released

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

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

** Tags added: block-proposed-xenial

** Tags added: block-proposed

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  kernel-stable-master-bug: 1742995
+ kernel-stable-phase-changed:Saturday, 13. January 2018 02:22 UTC
+ kernel-stable-phase:Uploaded

** Description changed:

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

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

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

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

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

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

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

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


[Kernel-packages] [Bug 1743053] Re: libata: apply MAX_SEC_1024 to all LITEON EP1 series devices

2018-01-12 Thread Stephen A. Zarkos
No longs, this is an upstream fix from the vendor.

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

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

Title:
  libata: apply MAX_SEC_1024 to all LITEON EP1 series devices

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Some SSD drives made by LiteOn can crash the kernel due to bad
  drivers.  A fix for this issue has been submitted upstream:
  
https://git.kernel.org/pub/scm/linux/kernel/git/tj/libata.git/commit/?h=for-4.15-fixes

  LITEON EP1 has the same timeout issues as CX1 series devices.

  Revert max_sectors to the value of 1024.

  'e0edc8c54646 ("libata: apply MAX_SEC_1024 to all CX1-JB*-HP
  devices")'

  Signed-off-by: Xinyu Lin 
  Signed-off-by: Tejun Heo 
  Cc: sta...@vger.kernel.org

  
  At a high level the root cause of this problem is that the device only 
supports commands with a transfer size up to 512KB.  This worked fine with 
older versions of Linux but newer versions are attempting commands with a 
transfer size of 1280KB which is problematic for this device (LITEON EP1-KB480)

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

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


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

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

apport-collect 1743053

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

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

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

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

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

Title:
  libata: apply MAX_SEC_1024 to all LITEON EP1 series devices

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Some SSD drives made by LiteOn can crash the kernel due to bad
  drivers.  A fix for this issue has been submitted upstream:
  
https://git.kernel.org/pub/scm/linux/kernel/git/tj/libata.git/commit/?h=for-4.15-fixes

  LITEON EP1 has the same timeout issues as CX1 series devices.

  Revert max_sectors to the value of 1024.

  'e0edc8c54646 ("libata: apply MAX_SEC_1024 to all CX1-JB*-HP
  devices")'

  Signed-off-by: Xinyu Lin 
  Signed-off-by: Tejun Heo 
  Cc: sta...@vger.kernel.org

  
  At a high level the root cause of this problem is that the device only 
supports commands with a transfer size up to 512KB.  This worked fine with 
older versions of Linux but newer versions are attempting commands with a 
transfer size of 1280KB which is problematic for this device (LITEON EP1-KB480)

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

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


[Kernel-packages] [Bug 1743053] [NEW] libata: apply MAX_SEC_1024 to all LITEON EP1 series devices

2018-01-12 Thread Stephen A. Zarkos
Public bug reported:

Some SSD drives made by LiteOn can crash the kernel due to bad drivers.
A fix for this issue has been submitted upstream:
https://git.kernel.org/pub/scm/linux/kernel/git/tj/libata.git/commit/?h=for-4.15-fixes

LITEON EP1 has the same timeout issues as CX1 series devices.

Revert max_sectors to the value of 1024.

'e0edc8c54646 ("libata: apply MAX_SEC_1024 to all CX1-JB*-HP devices")'

Signed-off-by: Xinyu Lin 
Signed-off-by: Tejun Heo 
Cc: sta...@vger.kernel.org


At a high level the root cause of this problem is that the device only supports 
commands with a transfer size up to 512KB.  This worked fine with older 
versions of Linux but newer versions are attempting commands with a transfer 
size of 1280KB which is problematic for this device (LITEON EP1-KB480)

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

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

Title:
  libata: apply MAX_SEC_1024 to all LITEON EP1 series devices

Status in linux package in Ubuntu:
  New

Bug description:
  Some SSD drives made by LiteOn can crash the kernel due to bad
  drivers.  A fix for this issue has been submitted upstream:
  
https://git.kernel.org/pub/scm/linux/kernel/git/tj/libata.git/commit/?h=for-4.15-fixes

  LITEON EP1 has the same timeout issues as CX1 series devices.

  Revert max_sectors to the value of 1024.

  'e0edc8c54646 ("libata: apply MAX_SEC_1024 to all CX1-JB*-HP
  devices")'

  Signed-off-by: Xinyu Lin 
  Signed-off-by: Tejun Heo 
  Cc: sta...@vger.kernel.org

  
  At a high level the root cause of this problem is that the device only 
supports commands with a transfer size up to 512KB.  This worked fine with 
older versions of Linux but newer versions are attempting commands with a 
transfer size of 1280KB which is problematic for this device (LITEON EP1-KB480)

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

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


[Kernel-packages] [Bug 1742302] Re: Kernel 4.13.0-25 broke nvidia driver

2018-01-12 Thread Lastique
I have fixed the problem by installing nvidia driver 390.12.

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

Title:
  Kernel 4.13.0-25 broke nvidia driver

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After updating to linux-image-4.13.0-25-generic the binary nvidia
  driver 387.22 cannot be built. As a result the system does not boot
  into the desktop environment (in my case, KDE).

  I've attached the driver build log.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-25-generic 4.13.0-25.29
  ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13
  Uname: Linux 4.13.0-21-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  lastique   3049 F pulseaudio
   /dev/snd/controlC2:  lastique   3049 F pulseaudio
   /dev/snd/controlC3:  lastique   3049 F pulseaudio
   /dev/snd/controlC1:  lastique   3049 F pulseaudio
  CurrentDesktop: KDE
  Date: Wed Jan 10 02:00:46 2018
  InstallationDate: Installed on 2015-05-01 (984 days ago)
  InstallationMedia: Kubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: System manufacturer System Product Name
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-21-generic 
root=UUID=a03f1835-52f9-4409-9da7-fe45770637ae ro quiet splash nomdmonddf 
nomdmonisw
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-21-generic N/A
   linux-backports-modules-4.13.0-21-generic  N/A
   linux-firmware 1.169.1
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: Upgraded to artful on 2017-11-03 (67 days ago)
  dmi.bios.date: 11/09/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3603
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P8Z68-V PRO
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3603:bd11/09/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP8Z68-VPRO:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

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


[Kernel-packages] [Bug 1742722] Re: linux: 4.13.0-29.32 -proposed tracker

2018-01-12 Thread Brad Figg
** Changed in: kernel-sru-workflow/automated-testing
   Status: New => Confirmed

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

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

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

** Changed in: kernel-sru-workflow/security-signoff
   Status: New => Confirmed

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

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  backports: 1742723,1742725,1742726,1742727,1742728,1742928
  derivatives: 1742730
- kernel-stable-phase:Uploaded
- kernel-stable-phase-changed:Friday, 12. January 2018 18:30 UTC
- 
  -- swm properties --
  boot-testing-requested: true
  phase: Uploaded
+ kernel-stable-phase-changed:Friday, 12. January 2018 23:00 UTC
+ kernel-stable-phase:Promoted to proposed

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  backports: 1742723,1742725,1742726,1742727,1742728,1742928
  derivatives: 1742730
  -- swm properties --
  boot-testing-requested: true
- phase: Uploaded
- kernel-stable-phase-changed:Friday, 12. January 2018 23:00 UTC
- kernel-stable-phase:Promoted to proposed
+ phase: Promoted to proposed
+ proposed-announcement-sent: true
+ proposed-testing-requested: true

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

Title:
  linux: 4.13.0-29.32 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Confirmed
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:
  Confirmed
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 Artful:
  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: 1742723,1742725,1742726,1742727,1742728,1742928
  derivatives: 1742730
  -- 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/1742722/+subscriptions

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


[Kernel-packages] [Bug 1743001] Re: linux-aws: 4.4.0-1049.58 -proposed tracker

2018-01-12 Thread Brad Figg
** Changed in: kernel-sru-workflow/snap-release-to-stable
   Status: New => 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/1743001

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

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

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

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

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

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


[Kernel-packages] [Bug 1742998] Re: linux-aws: 4.4.0-1011.11 -proposed tracker

2018-01-12 Thread Kamal Mostafa
** Summary changed:

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

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

** Changed in: kernel-sru-workflow/prepare-package
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Kamal Mostafa 
(kamalmostafa)

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

** Changed in: kernel-sru-workflow/prepare-package-meta
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Kamal Mostafa 
(kamalmostafa)

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

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

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

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

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

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

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


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

2018-01-12 Thread Yuchen Fan
Hi,

I met the same bugs on kernel 4.10.0-38-generic

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

Title:
  FS-Cache: Assertion failed

Status in linux package in Ubuntu:
  Incomplete

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

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

[Kernel-packages] [Bug 1743001] Re: linux-aws: 4.4.0-1049.58 -proposed tracker

2018-01-12 Thread Kamal Mostafa
** Summary changed:

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

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

** Changed in: kernel-sru-workflow/prepare-package
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Kamal Mostafa 
(kamalmostafa)

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

** Changed in: kernel-sru-workflow/prepare-package-meta
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Kamal Mostafa 
(kamalmostafa)

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

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

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

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

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

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

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


[Kernel-packages] [Bug 1501884] Re: linux-image-extra-*-generic postrm script runs install actions

2018-01-12 Thread Jarno Suni
Cool, I was not aware of those variables.

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

Title:
  linux-image-extra-*-generic postrm script runs install actions

Status in linux package in Ubuntu:
  Confirmed
Status in linux-lts-trusty package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  The postrm maintainer script in the binary packages linux-image-
  extra-*-generic runs the scripts in /etc/kernel/postinst.d instead of
  those in /etc/kernel/postrm.d.

  This can have all sorts of undesirable consequences depending on what
  other packages add to those directories, but I noticed it because it
  caused /etc/kernel/postinst.d/apt-auto-removal to make the wrong
  decisions leaving my servers with only one installed kernel left.

  Cheers,
  Seb

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

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


[Kernel-packages] [Bug 1724863] Re: bcmwl 6.30.223.271+bdcom-0ubuntu1~1.1 ADT test failure with linux-hwe-edge 4.13.0-16.19~16.04.3

2018-01-12 Thread Bob Bowden
I tried to install the latest bcmwl-kernel-source and got the following
...

sudo apt install bcmwl-kernel-source
Reading package lists... Done
Building dependency tree   
Reading state information... Done
The following packages will be upgraded:
  bcmwl-kernel-source
1 upgraded, 0 newly installed, 0 to remove and 282 not upgraded.
Need to get 1,544 kB of archives.
After this operation, 5,120 B of additional disk space will be used.
Get:1 http://us.archive.ubuntu.com/ubuntu xenial-updates/restricted amd64 
bcmwl-kernel-source amd64 6.30.223.271+bdcom-0ubuntu1~1.2 [1,544 kB]
Fetched 1,544 kB in 0s (5,683 kB/s)   
(Reading database ... 177392 files and directories currently installed.)
Preparing to unpack 
.../bcmwl-kernel-source_6.30.223.271+bdcom-0ubuntu1~1.2_amd64.deb ...
Removing all DKMS Modules
Done.
Unpacking bcmwl-kernel-source (6.30.223.271+bdcom-0ubuntu1~1.2) over 
(6.30.223.271+bdcom-0ubuntu1~1.1) ...
Setting up bcmwl-kernel-source (6.30.223.271+bdcom-0ubuntu1~1.2) ...
Loading new bcmwl-6.30.223.271+bdcom DKMS files...
Building only for 4.13.0-26-generic
Building for architecture x86_64
Module build for the currently running kernel was skipped since the
kernel source for this kernel does not seem to be installed.
modprobe: ERROR: ../libkmod/libkmod.c:586 kmod_search_moddep() could not open 
moddep file '/lib/modules/4.13.0-26-generic/modules.dep.bin'
modprobe: FATAL: Module wl not found in directory /lib/modules/4.13.0-26-generic
update-initramfs: deferring update (trigger activated)
Processing triggers for initramfs-tools (0.122ubuntu8.8) ...
update-initramfs: Generating /boot/initrd.img-4.10.0-28-generic
W: Possible missing firmware /lib/firmware/i915/kbl_dmc_ver1_01.bin for module 
i915

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

Title:
  bcmwl 6.30.223.271+bdcom-0ubuntu1~1.1 ADT test failure with linux-hwe-
  edge 4.13.0-16.19~16.04.3

Status in bcmwl package in Ubuntu:
  In Progress
Status in bcmwl source package in Xenial:
  Fix Released

Bug description:
  [Impact]

  Currently the DKMS package bcmwl-kernel-source fails to install in
  supported custom kernels that are based on 4.11 or 4.13. That includes
  the current 4.11 hwe-edge and the upcoming 4.13 hwe-edge kernels and
  some of the custom and cloud kernels as well.

  [Test Case]

  Install the bcmwl-kernel-source package with the 4.13 hwe-edge kernel
  from -proposed. The package installation should proceed without any
  errors.

  [Regression Potential]

  Although new patches were added, the regression risk is very low since
  the new changes are conditionally compiled based on the kernel version.

  Besides that the new package was tested with the following kernels in an
  amd64 environment:

  - linux-generic 4.4
  - linux-hwe 4.10
  - linux-hwe-edge 4.11
  - linux-hwe-edge 4.13 (from xenial-proposed)
  - linux-azure 4.11
  - linux-azure-edge 4.13 (which is in process of getting promoted to
xenial-proposed)

  [Original Description]

  Testing failed on:
  amd64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/amd64/b/bcmwl/20171018_120646_2caa6@/log.gz
  i386: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/i386/b/bcmwl/20171018_120820_2caa6@/log.gz

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

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


[Kernel-packages] [Bug 1736390] Re: openvswitch: kernel oops destroying interfaces on i386

2018-01-12 Thread Joseph Salisbury
Thanks for the feedback, Christian!  This gives me enough to be able to
try and bisect this issue down now.  I'll post an update shortly.

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

Title:
  openvswitch: kernel oops destroying interfaces on i386

Status in linux package in Ubuntu:
  Fix Committed
Status in openvswitch package in Ubuntu:
  Confirmed
Status in linux source package in Artful:
  In Progress
Status in openvswitch source package in Artful:
  Confirmed
Status in linux source package in Bionic:
  Fix Committed
Status in openvswitch source package in Bionic:
  Confirmed

Bug description:
  Reproducable on bionic using the autopkgtest's from openvswitch on
  i386:

  [   41.420568] BUG: unable to handle kernel NULL pointer dereference at   
(null)
  [   41.421000] IP: igmp_group_dropped+0x21/0x220
  [   41.421246] *pdpt = 1d62c001 *pde =  

  [   41.421659] Oops:  [#1] SMP
  [   41.421852] Modules linked in: veth openvswitch nf_conntrack_ipv6 
nf_nat_ipv6 nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_defrag_ipv6 nf_nat 
nf_conntrack libcrc32c 9p fscache ppdev kvm_intel kvm 9pnet_virtio irqbypass 
input_leds joydev 9pnet parport_pc serio_raw parport i2c_piix4 qemu_fw_cfg 
mac_hid sch_fq_codel ip_tables x_tables autofs4 btrfs xor raid6_pq psmouse 
virtio_blk virtio_net pata_acpi floppy
  [   41.423855] CPU: 0 PID: 5 Comm: kworker/u2:0 Tainted: GW   
4.13.0-18-generic #21-Ubuntu
  [   41.424355] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 
1.10.2-1ubuntu1 04/01/2014
  [   41.424849] Workqueue: netns cleanup_net
  [   41.425071] task: db8fba80 task.stack: dba1
  [   41.425346] EIP: igmp_group_dropped+0x21/0x220
  [   41.425656] EFLAGS: 00010202 CPU: 0
  [   41.425864] EAX:  EBX: dd726360 ECX: dba11e6c EDX: 0002
  [   41.426335] ESI:  EDI: dd4db500 EBP: dba11dcc ESP: dba11d94
  [   41.426687]  DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068
  [   41.426990] CR0: 80050033 CR2:  CR3: 1e6d6d60 CR4: 06f0
  [   41.427340] Call Trace:
  [   41.427485]  ? __wake_up+0x36/0x40
  [   41.427680]  ip_mc_down+0x27/0x90
  [   41.427869]  inetdev_event+0x398/0x4e0
  [   41.428082]  ? skb_dequeue+0x5b/0x70
  [   41.428286]  ? wireless_nlevent_flush+0x4c/0x90
  [   41.428541]  notifier_call_chain+0x4e/0x70
  [   41.428772]  raw_notifier_call_chain+0x11/0x20
  [   41.429023]  call_netdevice_notifiers_info+0x2a/0x60
  [   41.429301]  dev_close_many+0x9d/0xe0
  [   41.429509]  rollback_registered_many+0xd7/0x380
  [   41.429768]  unregister_netdevice_many.part.102+0x10/0x80
  [   41.430075]  default_device_exit_batch+0x134/0x160
  [   41.430344]  ? do_wait_intr_irq+0x80/0x80
  [   41.430650]  ops_exit_list.isra.8+0x4d/0x60
  [   41.430886]  cleanup_net+0x18e/0x260
  [   41.431090]  process_one_work+0x1a0/0x390
  [   41.431317]  worker_thread+0x37/0x450
  [   41.431525]  kthread+0xf3/0x110
  [   41.431714]  ? process_one_work+0x390/0x390
  [   41.431941]  ? kthread_create_on_node+0x20/0x20
  [   41.432187]  ret_from_fork+0x19/0x24
  [   41.432382] Code: 90 90 90 90 90 90 90 90 90 90 3e 8d 74 26 00 55 89 e5 57 
56 53 89 c3 83 ec 2c 8b 33 65 a1 14 00 00 00 89 45 f0 31 c0 80 7b 4b 00 <8b> 06 
8b b8 20 03 00 00 8b 43 04 0f 85 5e 01 00 00 3d e0 00 00
  [   41.433405] EIP: igmp_group_dropped+0x21/0x220 SS:ESP: 0068:dba11d94
  [   41.433750] CR2: 
  [   41.433961] ---[ end trace 595db54cab84070c ]---

  
  system then becomes unresponsive; no further interfaces can be created.

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

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


[Kernel-packages] [Bug 1742995] Re: linux: 4.4.0-110.133 -proposed tracker

2018-01-12 Thread Kamal Mostafa
** Also affects: linux (Ubuntu Xenial)
   Importance: Undecided
   Status: New

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

Title:
  linux: 4.4.0-110.133 -proposed tracker

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

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

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

  backports: 1742996,1742998
  derivatives: 1742999,1743000,1743001,1743002,1743004,1743006

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

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


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

2018-01-12 Thread Kamal Mostafa
** Also affects: linux-aws (Ubuntu Trusty)
   Importance: Undecided
   Status: New

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

Title:
  linux-aws:  -proposed tracker

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

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

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

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

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


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

2018-01-12 Thread Kamal Mostafa
** Also affects: linux-aws (Ubuntu Xenial)
   Importance: Undecided
   Status: New

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

Title:
  linux-aws:  -proposed tracker

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

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

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

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

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


[Kernel-packages] [Bug 1743026] Re: qemu-nbd -c /dev/nbd0 fails to map partitions

2018-01-12 Thread Joseph Salisbury
** Changed in: linux (Ubuntu)
   Importance: Undecided => High

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

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

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

Title:
  qemu-nbd -c /dev/nbd0 fails to map partitions

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

Bug description:
  [impact]
  4.4.0-101+ (also 4.4.0-109) Ubuntu kernels no longer can use qemu-nbd to 
mount virtual disks onto a local filesystem (see test case for reproducer). 
4.4.0-98 works without issue.

  I was able to bisect the issue down to
  907196aba0d891c6d580abe69c36d3b4fd512dcc (a cherry-pick from
  37091fdd831f28a6509008542174ed324dd645bc). Reverting this from 4.4
  fixes the issue.

  Installing the mainline kernel shows mainline is _not_ affected by
  this bug.

  In addition this is also reported in debian here:
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=829532

  [test case]
  # given a vmdk disk with multiple partitions
  sudo modprobe nbd
  sudo qemu-nbd -d /dev/nbd0
  sudo qemu-nbd -r -c /dev/nbd0 disk.vmdk
  ls /dev/nbd0*
  # here you won't see multiple partition, nor be able to mount a partition 
locally

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

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


[Kernel-packages] [Bug 1742722] Re: linux: 4.13.0-29.32 -proposed tracker

2018-01-12 Thread Łukasz Zemczak
** Changed in: kernel-sru-workflow/promote-to-proposed
   Status: In Progress => Fix Committed

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

Title:
  linux: 4.13.0-29.32 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Committed
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Artful:
  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: 1742723,1742725,1742726,1742727,1742728,1742928
  derivatives: 1742730
  kernel-stable-phase:Uploaded
  kernel-stable-phase-changed:Friday, 12. January 2018 18:30 UTC

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

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

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


[Kernel-packages] [Bug 1743026] Re: qemu-nbd -c /dev/nbd0 fails to map partitions

2018-01-12 Thread Chris J Arges
This patch seems to fix the issue:
```
diff --git a/drivers/block/nbd.c b/drivers/block/nbd.c
index 5f807a6..b761971 100644
--- a/drivers/block/nbd.c
+++ b/drivers/block/nbd.c
@@ -98,11 +98,6 @@ static inline struct device *nbd_to_dev(struct nbd_device 
*nbd)
return disk_to_dev(nbd->disk);
 }
 
-static bool nbd_is_connected(struct nbd_device *nbd)
-{
-   return !!nbd->task_recv;
-}
-
 static const char *nbdcmd_to_ascii(int cmd)
 {
switch (cmd) {
@@ -126,9 +121,6 @@ static int nbd_size_clear(struct nbd_device *nbd, struct 
block_device *bdev)
 
 static void nbd_size_update(struct nbd_device *nbd, struct block_device *bdev)
 {
-   if (!nbd_is_connected(nbd))
-   return;
-
bdev->bd_inode->i_size = nbd->bytesize;
set_capacity(nbd->disk, nbd->bytesize >> 9);
kobject_uevent(_to_dev(nbd)->kobj, KOBJ_CHANGE);
```

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

Title:
  qemu-nbd -c /dev/nbd0 fails to map partitions

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

Bug description:
  [impact]
  4.4.0-101+ (also 4.4.0-109) Ubuntu kernels no longer can use qemu-nbd to 
mount virtual disks onto a local filesystem (see test case for reproducer). 
4.4.0-98 works without issue.

  I was able to bisect the issue down to
  907196aba0d891c6d580abe69c36d3b4fd512dcc (a cherry-pick from
  37091fdd831f28a6509008542174ed324dd645bc). Reverting this from 4.4
  fixes the issue.

  Installing the mainline kernel shows mainline is _not_ affected by
  this bug.

  In addition this is also reported in debian here:
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=829532

  [test case]
  # given a vmdk disk with multiple partitions
  sudo modprobe nbd
  sudo qemu-nbd -d /dev/nbd0
  sudo qemu-nbd -r -c /dev/nbd0 disk.vmdk
  ls /dev/nbd0*
  # here you won't see multiple partition, nor be able to mount a partition 
locally

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

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


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

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

apport-collect 1743026

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

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

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

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

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

Title:
  qemu-nbd -c /dev/nbd0 fails to map partitions

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

Bug description:
  [impact]
  4.4.0-101+ (also 4.4.0-109) Ubuntu kernels no longer can use qemu-nbd to 
mount virtual disks onto a local filesystem (see test case for reproducer). 
4.4.0-98 works without issue.

  I was able to bisect the issue down to
  907196aba0d891c6d580abe69c36d3b4fd512dcc (a cherry-pick from
  37091fdd831f28a6509008542174ed324dd645bc). Reverting this from 4.4
  fixes the issue.

  Installing the mainline kernel shows mainline is _not_ affected by
  this bug.

  In addition this is also reported in debian here:
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=829532

  [test case]
  # given a vmdk disk with multiple partitions
  sudo modprobe nbd
  sudo qemu-nbd -d /dev/nbd0
  sudo qemu-nbd -r -c /dev/nbd0 disk.vmdk
  ls /dev/nbd0*
  # here you won't see multiple partition, nor be able to mount a partition 
locally

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

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


[Kernel-packages] [Bug 1742722] Re: linux: 4.13.0-29.32 -proposed tracker

2018-01-12 Thread Łukasz Zemczak
** Changed in: kernel-sru-workflow/promote-to-proposed
   Status: Confirmed => In Progress

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

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

Title:
  linux: 4.13.0-29.32 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  In Progress
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Artful:
  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: 1742723,1742725,1742726,1742727,1742728,1742928
  derivatives: 1742730
  kernel-stable-phase:Uploaded
  kernel-stable-phase-changed:Friday, 12. January 2018 18:30 UTC

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

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

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


[Kernel-packages] [Bug 1743026] [NEW] qemu-nbd -c /dev/nbd0 fails to map partitions

2018-01-12 Thread Chris J Arges
Public bug reported:

[impact]
4.4.0-101+ (also 4.4.0-109) Ubuntu kernels no longer can use qemu-nbd to mount 
virtual disks onto a local filesystem (see test case for reproducer). 4.4.0-98 
works without issue.

I was able to bisect the issue down to
907196aba0d891c6d580abe69c36d3b4fd512dcc (a cherry-pick from
37091fdd831f28a6509008542174ed324dd645bc). Reverting this from 4.4 fixes
the issue.

Installing the mainline kernel shows mainline is _not_ affected by this
bug.

In addition this is also reported in debian here:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=829532

[test case]
# given a vmdk disk with multiple partitions
sudo modprobe nbd
sudo qemu-nbd -d /dev/nbd0
sudo qemu-nbd -r -c /dev/nbd0 disk.vmdk
ls /dev/nbd0*
# here you won't see multiple partition, nor be able to mount a partition 
locally

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

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

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

** Description changed:

  [impact]
  4.4.0-101+ (also 4.4.0-109) Ubuntu kernels no longer can use qemu-nbd to 
mount virtual disks onto a local filesystem (see test case for reproducer).
  
  I was able to bisect the issue down to
- 907196aba0d891c6d580abe69c36d3b4fd512dcc. Reverting this from 4.4 fixes
+ 907196aba0d891c6d580abe69c36d3b4fd512dcc (a cherry-pick from
+ 37091fdd831f28a6509008542174ed324dd645bc). Reverting this from 4.4 fixes
  the issue.
  
  In addition this is also reported in debian here:
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=829532
  
  [test case]
  # given a vmdk disk with multiple partitions
  sudo modprobe nbd
  sudo qemu-nbd -d /dev/nbd0
  sudo qemu-nbd -r -c /dev/nbd0 disk.vmdk
  ls /dev/nbd0*
  # here you won't see multiple partition, nor be able to mount a partition 
locally

** Description changed:

  [impact]
- 4.4.0-101+ (also 4.4.0-109) Ubuntu kernels no longer can use qemu-nbd to 
mount virtual disks onto a local filesystem (see test case for reproducer).
+ 4.4.0-101+ (also 4.4.0-109) Ubuntu kernels no longer can use qemu-nbd to 
mount virtual disks onto a local filesystem (see test case for reproducer). 
4.4.0-98 works without issue.
  
  I was able to bisect the issue down to
  907196aba0d891c6d580abe69c36d3b4fd512dcc (a cherry-pick from
  37091fdd831f28a6509008542174ed324dd645bc). Reverting this from 4.4 fixes
  the issue.
+ 
+ Installing the mainline kernel shows mainline is _not_ affected by this
+ bug.
  
  In addition this is also reported in debian here:
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=829532
  
  [test case]
  # given a vmdk disk with multiple partitions
  sudo modprobe nbd
  sudo qemu-nbd -d /dev/nbd0
  sudo qemu-nbd -r -c /dev/nbd0 disk.vmdk
  ls /dev/nbd0*
  # here you won't see multiple partition, nor be able to mount a partition 
locally

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

Title:
  qemu-nbd -c /dev/nbd0 fails to map partitions

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

Bug description:
  [impact]
  4.4.0-101+ (also 4.4.0-109) Ubuntu kernels no longer can use qemu-nbd to 
mount virtual disks onto a local filesystem (see test case for reproducer). 
4.4.0-98 works without issue.

  I was able to bisect the issue down to
  907196aba0d891c6d580abe69c36d3b4fd512dcc (a cherry-pick from
  37091fdd831f28a6509008542174ed324dd645bc). Reverting this from 4.4
  fixes the issue.

  Installing the mainline kernel shows mainline is _not_ affected by
  this bug.

  In addition this is also reported in debian here:
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=829532

  [test case]
  # given a vmdk disk with multiple partitions
  sudo modprobe nbd
  sudo qemu-nbd -d /dev/nbd0
  sudo qemu-nbd -r -c /dev/nbd0 disk.vmdk
  ls /dev/nbd0*
  # here you won't see multiple partition, nor be able to mount a partition 
locally

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

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


[Kernel-packages] [Bug 1742324] Re: Bionic kernel panics in the MAAS ephemeral environment

2018-01-12 Thread Lee Trager
** Changed in: maas
   Status: Triaged => 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/1742324

Title:
  Bionic kernel panics in the MAAS ephemeral environment

Status in MAAS:
  Won't Fix
Status in linux package in Ubuntu:
  Triaged

Bug description:
  Bionic kernel panics in the MAAS ephemeral environment. This does not
  always happen during commissioning or testing but does happen every
  time when trying to enter rescue mode. The test system is a KVM
  machine using all VirtIO drivers running on a Bionic host system. Both
  systems are using the 4.13.0-17-generic kernel.

  [   13.774332] BUG: unable to handle kernel paging request at f672c3075a20
  [   13.775203] IP: kfree+0x53/0x160
  [   13.775665] PGD 0 
  [   13.775666] P4D 0 
  [   13.775965] 
  [   13.776566] Oops:  [#1] SMP
  [   13.777004] Modules linked in: iscsi_tcp libiscsi_tcp libiscsi 
scsi_transport_iscsi overlay 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 crct10dif_pclmul crc32_pclmul 
ghash_clmulni_intel pcbc ttm drm_kms_helper aesni_intel syscopyarea sysfillrect 
aes_x86_64 crypto_simd glue_helper cryptd sysimgblt fb_sys_fops drm psmouse 
virtio_blk virtio_net pata_acpi floppy
  [   13.782468] CPU: 0 PID: 696 Comm: lxd Not tainted 4.13.0-17-generic 
#20-Ubuntu
  [   13.783169] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 
1.10.2-1ubuntu1 04/01/2014
  [   13.784028] task: 9afa30b62e80 task.stack: c07640a5
  [   13.784512] RIP: 0010:kfree+0x53/0x160
  [   13.784884] RSP: 0018:9afa3ca03a18 EFLAGS: 00010286
  [   13.785339] RAX:  RBX: f50a81d68280 RCX: 
0002
  [   13.785983] RDX: 457c0321e918 RSI: 00010080 RDI: 
6505c000
  [   13.786916] RBP: 9afa3ca03a30 R08: 0001f4c0 R09: 
94bbb839
  [   13.787877] R10: f672c3075a00 R11: e4e5cd01 R12: 
9afa3f794000
  [   13.788854] R13: 947a155e R14: 9afa3f794000 R15: 
9afa3f794000
  [   13.789882] FS:  7fc4a7938cc0() GS:9afa3ca0() 
knlGS:
  [   13.791134] CS:  0010 DS:  ES:  CR0: 80050033
  [   13.792003] CR2: f672c3075a20 CR3: 737f6000 CR4: 
001406f0
  [   13.793019] Call Trace:
  [   13.793462]  
  [   13.793886]  security_sk_free+0x3e/0x50
  [   13.794680]  __sk_destruct+0x108/0x190
  [   13.795465]  sk_destruct+0x20/0x30
  [   13.796193]  __sk_free+0x82/0xa0
  [   13.796899]  sk_free+0x19/0x20
  [   13.797537]  sock_put+0x14/0x20
  [   13.797926]  tcp_v4_rcv+0x94d/0x9d0
  [   13.798325]  ? ep_poll_callback+0x226/0x2b0
  [   13.798704]  ip_local_deliver_finish+0x5c/0x1f0
  [   13.799099]  ip_local_deliver+0x6f/0xe0
  [   13.799455]  ip_rcv_finish+0x120/0x410
  [   13.799868]  ip_rcv+0x28c/0x3a0
  [   13.800221]  ? csum_partial+0x11/0x20
  [   13.800649]  __netif_receive_skb_core+0x39a/0xaa0
  [   13.801295]  ? skb_checksum+0x35/0x50
  [   13.801742]  ? skb_append_datato_frags+0x200/0x200
  [   13.802164]  ? reqsk_fastopen_remove+0x140/0x140
  [   13.802576]  __netif_receive_skb+0x18/0x60
  [   13.803163]  ? __netif_receive_skb+0x18/0x60
  [   13.803798]  netif_receive_skb_internal+0x3f/0x3f0
  [   13.804538]  ? dev_gro_receive+0x2dc/0x480
  [   13.805210]  napi_gro_receive+0xc2/0xe0
  [   13.805851]  receive_buf+0x218/0xf70 [virtio_net]
  [   13.806591]  ? vring_unmap_one+0x1b/0x80
  [   13.807240]  virtnet_poll+0x173/0x268 [virtio_net]
  [   13.807998]  net_rx_action+0x13b/0x380
  [   13.808621]  ? skb_recv_done+0x30/0x40 [virtio_net]
  [   13.810159]  __do_softirq+0xde/0x2a5
  [   13.810673]  irq_exit+0xb6/0xc0
  [   13.811185]  do_IRQ+0x80/0xd0
  [   13.811881]  common_interrupt+0x89/0x89
  [   13.812668] RIP: 0010:filemap_fault+0xff/0x5e0
  [   13.819490] RSP: 0018:c07640a53cc8 EFLAGS: 0202 ORIG_RAX: 
ff8e
  [   13.820174] RAX: 0012e288 RBX: 9afa3f6e0800 RCX: 
0054
  [   13.820760] RDX:  RSI: 9afa30b64180 RDI: 
9afa3ca1c200
  [   13.821339] RBP: c07640a53d70 R08: 0310 R09: 
0001
  [   13.821917] R10: c076406ab738 R11: 00d2 R12: 
00ea
  [   13.822493] R13: 9afa3262e900 R14: f50a8174eec0 R15: 
c07640a53db8
  [   13.823075]  
  [   13.823327]  ? filemap_fault+0xb0/0x5e0
  [   13.823703]  ? filemap_map_pages+0x179/0x320
  [   13.824101]  __do_fault+0x1e/0xb0
  [   13.824434]  __handle_mm_fault+0xba7/0x1020
  [   13.824821]  handle_mm_fault+0xb1/0x200
  [   13.825189]  __do_page_fault+0x24d/0x4d0
  [   13.825560]  trace_do_page_fault+0x37/0xd0
  [   13.826051]  do_async_page_fault+0x51/0x80
  [   13.826652]  async_page_fault+0x28/0x30
  [   13.827246] RIP: 0033:0x7fc4a68e38a7
  [   13.827818] RSP: 002b:7ffea4ae47e8 

[Kernel-packages] [Bug 1742722] Re: linux: 4.13.0-29.32 -proposed tracker

2018-01-12 Thread Brad Figg
** Changed in: kernel-sru-workflow/prepare-package
   Status: In Progress => Fix Released

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

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

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

** Tags added: block-proposed-artful

** Tags added: block-proposed

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  backports: 1742723,1742725,1742726,1742727,1742728,1742928
  derivatives: 1742730
+ kernel-stable-phase:Uploaded
+ kernel-stable-phase-changed:Friday, 12. January 2018 18:30 UTC

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  backports: 1742723,1742725,1742726,1742727,1742728,1742928
  derivatives: 1742730
  kernel-stable-phase:Uploaded
  kernel-stable-phase-changed:Friday, 12. January 2018 18:30 UTC
+ 
+ -- swm properties --
+ boot-testing-requested: true
+ phase: Uploaded

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

Title:
  linux: 4.13.0-29.32 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Confirmed
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Artful:
  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: 1742723,1742725,1742726,1742727,1742728,1742928
  derivatives: 1742730
  kernel-stable-phase:Uploaded
  kernel-stable-phase-changed:Friday, 12. January 2018 18:30 UTC

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

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

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


[Kernel-packages] [Bug 1742772] Re: powerpc: flush L1D on return to use

2018-01-12 Thread Marcelo Cerri
** Changed in: linux (Ubuntu Xenial)
   Status: In Progress => Fix Committed

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

Title:
  powerpc: flush L1D on return to use

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

Bug description:
  powerpc: flush L1D on return to use

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

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


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

2018-01-12 Thread Marcelo Cerri
** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
+ 
+ backports: 1742996,1742998
+ derivatives: 1742999,1743000,1743001,1743002,1743004,1743006

** Summary changed:

- linux:  -proposed tracker
+ linux: 4.4.0-110.133 -proposed tracker

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

** Changed in: kernel-sru-workflow/prepare-package-signed
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Marcelo Cerri 
(mhcerri)

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

** Changed in: kernel-sru-workflow/prepare-package-meta
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Marcelo Cerri 
(mhcerri)

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

** Changed in: kernel-sru-workflow/prepare-package
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Marcelo Cerri 
(mhcerri)

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

Title:
  linux: 4.4.0-110.133 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  In Progress
Status in Kernel SRU Workflow prepare-package-meta series:
  In Progress
Status in Kernel SRU Workflow prepare-package-signed series:
  In Progress
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow snap-certification-testing series:
  New
Status in Kernel SRU Workflow snap-release-to-beta series:
  New
Status in Kernel SRU Workflow snap-release-to-candidate series:
  New
Status in Kernel SRU Workflow snap-release-to-edge series:
  New
Status in Kernel SRU Workflow snap-release-to-stable series:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux package in Ubuntu:
  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: 1742996,1742998
  derivatives: 1742999,1743000,1743001,1743002,1743004,1743006

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

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


[Kernel-packages] [Bug 1742771] Re: s390: add ppa to kernel entry/exit

2018-01-12 Thread Marcelo Cerri
** Changed in: linux (Ubuntu Xenial)
   Status: In Progress => Fix Committed

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

Title:
  s390: add ppa to kernel entry/exit

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

Bug description:
  s390: add ppa to kernel entry/exit

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

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


[Kernel-packages] [Bug 1720580] Re: RTL8723bs bug: ERROR sd_recv_rxfifo: alloc recvbuf FAIL!

2018-01-12 Thread mikewhatever
...been using kernel 4.14.11/12/13, and there are no errors and no
freezes. There is also nothing in changelogs about rtl8723bs fixes, and
yet, it works. I am looking forward to the 18.04 release.

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

Title:
  RTL8723bs bug: ERROR sd_recv_rxfifo: alloc recvbuf FAIL!

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Found a bunch of "RTL8723BS: ERROR sd_recv_rxfifo: alloc recvbuf
  FAIL!" messages in syslog after a complete freeze. Searching for this
  error only found one reference https://lkml.org/lkml/2017/6/12/504.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-12-generic 4.13.0-12.13 [modified: 
boot/vmlinuz-4.13.0-12-generic]
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  mele   1303 F pulseaudio
  CurrentDesktop: MATE
  Date: Sat Sep 30 23:45:09 2017
  HibernationDevice: RESUME=UUID=ab188fcc-c7b5-433e-8dc8-bf403e9888ec
  InstallationDate: Installed on 2017-09-29 (1 days ago)
  InstallationMedia: Ubuntu-MATE 17.10 "Artful Aardvark" - Alpha amd64 
(20170926)
  MachineType: MiPi PC Mini PC
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-12-generic.efi.signed 
root=UUID=f415201e-4ac6-4443-83b8-f40d3dc03403 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-12-generic N/A
   linux-backports-modules-4.13.0-12-generic  N/A
   linux-firmware 1.168
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  StagingDrivers: r8723bs
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/29/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5.6.5
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Mini PC
  dmi.board.vendor: Mini PC
  dmi.board.version: To be filled by O.E.M.
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Mini PC
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5.6.5:bd10/29/2015:svnMiPiPC:pnMiniPC:pvr2.80:rvnMiniPC:rnMiniPC:rvrTobefilledbyO.E.M.:cvnMiniPC:ct8:cvrToBeFilledByO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: Mini PC
  dmi.product.version: 2.80
  dmi.sys.vendor: MiPi PC

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

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


[Kernel-packages] [Bug 1742998] [NEW] linux-aws: -proposed tracker

2018-01-12 Thread Marcelo Cerri
Public bug reported:

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: 1742995

** Affects: kernel-sru-workflow
 Importance: Medium
 Status: In Progress

** Affects: kernel-sru-workflow/automated-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/certification-testing
 Importance: Medium
 Assignee: Canonical Hardware Certification (canonical-hw-cert)
 Status: New

** Affects: kernel-sru-workflow/prepare-package
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/prepare-package-meta
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/promote-to-proposed
 Importance: Medium
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru)
 Status: New

** Affects: kernel-sru-workflow/promote-to-security
 Importance: Medium
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru)
 Status: New

** Affects: kernel-sru-workflow/promote-to-updates
 Importance: Medium
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru)
 Status: New

** Affects: kernel-sru-workflow/regression-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/security-signoff
 Importance: Medium
 Assignee: Canonical Security Team (canonical-security)
 Status: New

** Affects: kernel-sru-workflow/upload-to-ppa
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/verification-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: linux-aws (Ubuntu)
 Importance: Undecided
 Status: Invalid


** Tags: kernel-release-tracking-bug kernel-release-tracking-bug-live 
kernel-sru-backport-of-1742995 kernel-sru-cycle-2017.11.20-8 trusty

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

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

** Tags added: trusty

** Also affects: kernel-sru-workflow/automated-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/certification-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/prepare-package
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/prepare-package-meta
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/promote-to-proposed
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/promote-to-security
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/promote-to-updates
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/regression-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/security-signoff
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/upload-to-ppa
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/verification-testing
   Importance: Undecided
   Status: New

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

** Changed in: kernel-sru-workflow
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/automated-testing
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/automated-testing
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-sru-workflow/certification-testing
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/certification-testing
 Assignee: (unassigned) => Canonical Hardware Certification 
(canonical-hw-cert)

** Changed in: kernel-sru-workflow/prepare-package
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/prepare-package
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-sru-workflow/prepare-package-meta
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/prepare-package-meta
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-sru-workflow/promote-to-proposed
   Importance: Undecided => Medium

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

** Changed in: kernel-sru-workflow/promote-to-security
   Importance: Undecided => Medium

** Changed in: 

[Kernel-packages] [Bug 1743001] [NEW] linux-aws: -proposed tracker

2018-01-12 Thread Marcelo Cerri
Public bug reported:

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: 1742995

** Affects: kernel-sru-workflow
 Importance: Medium
 Status: In Progress

** Affects: kernel-sru-workflow/automated-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/certification-testing
 Importance: Medium
 Assignee: Canonical Hardware Certification (canonical-hw-cert)
 Status: New

** Affects: kernel-sru-workflow/prepare-package
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/prepare-package-meta
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/promote-to-proposed
 Importance: Medium
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru)
 Status: New

** Affects: kernel-sru-workflow/promote-to-security
 Importance: Medium
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru)
 Status: New

** Affects: kernel-sru-workflow/promote-to-updates
 Importance: Medium
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru)
 Status: New

** Affects: kernel-sru-workflow/regression-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/security-signoff
 Importance: Medium
 Assignee: Canonical Security Team (canonical-security)
 Status: New

** Affects: kernel-sru-workflow/snap-release-to-beta
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/snap-release-to-candidate
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/snap-release-to-edge
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/snap-release-to-stable
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/upload-to-ppa
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/verification-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: linux-aws (Ubuntu)
 Importance: Undecided
 Status: Invalid


** Tags: kernel-release-tracking-bug kernel-release-tracking-bug-live 
kernel-sru-cycle-2017.11.20-8 kernel-sru-derivative-of-1742995 xenial

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

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

** Tags added: xenial

** Also affects: kernel-sru-workflow/automated-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/certification-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/prepare-package
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/prepare-package-meta
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/promote-to-proposed
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/promote-to-security
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/promote-to-updates
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/regression-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/security-signoff
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/snap-release-to-beta
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/snap-release-to-candidate
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/snap-release-to-edge
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/snap-release-to-stable
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/upload-to-ppa
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/verification-testing
   Importance: Undecided
   Status: New

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

** Changed in: kernel-sru-workflow
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/automated-testing
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/automated-testing
 Assignee: (unassigned) => Canonical Kernel 

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

2018-01-12 Thread Marcelo Cerri
** Changed in: kernel-sru-workflow
   Status: In Progress => Invalid

** Changed in: kernel-sru-workflow/automated-testing
   Status: New => Invalid

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

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

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

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

** Changed in: kernel-sru-workflow/promote-to-proposed
   Status: New => Invalid

** Changed in: kernel-sru-workflow/promote-to-security
   Status: New => Invalid

** Changed in: kernel-sru-workflow/promote-to-updates
   Status: New => Invalid

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

** Changed in: kernel-sru-workflow/security-signoff
   Status: New => Invalid

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

** Changed in: kernel-sru-workflow/snap-release-to-beta
   Status: New => Invalid

** Changed in: kernel-sru-workflow/snap-release-to-candidate
   Status: New => Invalid

** Changed in: kernel-sru-workflow/snap-release-to-edge
   Status: New => Invalid

** Changed in: kernel-sru-workflow/snap-release-to-stable
   Status: New => Invalid

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

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

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 snap-certification-testing series:
  Invalid
Status in Kernel SRU Workflow snap-release-to-beta series:
  Invalid
Status in Kernel SRU Workflow snap-release-to-candidate series:
  Invalid
Status in Kernel SRU Workflow snap-release-to-edge series:
  Invalid
Status in Kernel SRU Workflow snap-release-to-stable 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

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

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

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


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

2018-01-12 Thread Marcelo Cerri
** Changed in: kernel-sru-workflow
   Status: In Progress => Invalid

** Changed in: kernel-sru-workflow/automated-testing
   Status: New => Invalid

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

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

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

** Changed in: kernel-sru-workflow/promote-to-proposed
   Status: New => Invalid

** Changed in: kernel-sru-workflow/promote-to-security
   Status: New => Invalid

** Changed in: kernel-sru-workflow/promote-to-updates
   Status: New => Invalid

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

** Changed in: kernel-sru-workflow/security-signoff
   Status: New => Invalid

** Changed in: kernel-sru-workflow/upload-to-ppa
   Status: New => Invalid

** Changed in: kernel-sru-workflow/verification-testing
   Status: New => 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/1742980

Title:
  linux-aws:  -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 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-aws package in Ubuntu:
  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: 1742979

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

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


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

2018-01-12 Thread Marcelo Cerri
** Changed in: kernel-sru-workflow
   Status: In Progress => Invalid

** Changed in: kernel-sru-workflow/automated-testing
   Status: New => Invalid

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

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

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

** Changed in: kernel-sru-workflow/promote-to-proposed
   Status: New => Invalid

** Changed in: kernel-sru-workflow/promote-to-security
   Status: New => Invalid

** Changed in: kernel-sru-workflow/promote-to-updates
   Status: New => Invalid

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

** Changed in: kernel-sru-workflow/security-signoff
   Status: New => Invalid

** Changed in: kernel-sru-workflow/snap-release-to-beta
   Status: New => Invalid

** Changed in: kernel-sru-workflow/snap-release-to-candidate
   Status: New => Invalid

** Changed in: kernel-sru-workflow/snap-release-to-edge
   Status: New => Invalid

** Changed in: kernel-sru-workflow/snap-release-to-stable
   Status: New => Invalid

** Changed in: kernel-sru-workflow/upload-to-ppa
   Status: New => Invalid

** Changed in: kernel-sru-workflow/verification-testing
   Status: New => 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/1742988

Title:
  linux-aws:  -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 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 snap-release-to-beta series:
  Invalid
Status in Kernel SRU Workflow snap-release-to-candidate series:
  Invalid
Status in Kernel SRU Workflow snap-release-to-edge series:
  Invalid
Status in Kernel SRU Workflow snap-release-to-stable series:
  Invalid
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Invalid
Status in linux-aws package in Ubuntu:
  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: 1742979

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

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


[Kernel-packages] [Bug 1742995] [NEW] linux: -proposed tracker

2018-01-12 Thread Marcelo Cerri
Public bug reported:

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

** Affects: kernel-sru-workflow
 Importance: Medium
 Status: In Progress

** Affects: kernel-sru-workflow/automated-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/certification-testing
 Importance: Medium
 Assignee: Canonical Hardware Certification (canonical-hw-cert)
 Status: New

** Affects: kernel-sru-workflow/prepare-package
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: Confirmed

** Affects: kernel-sru-workflow/prepare-package-meta
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/prepare-package-signed
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/promote-to-proposed
 Importance: Medium
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru)
 Status: New

** Affects: kernel-sru-workflow/promote-to-security
 Importance: Medium
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru)
 Status: New

** Affects: kernel-sru-workflow/promote-to-updates
 Importance: Medium
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru)
 Status: New

** Affects: kernel-sru-workflow/regression-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/security-signoff
 Importance: Medium
 Assignee: Canonical Security Team (canonical-security)
 Status: New

** Affects: kernel-sru-workflow/snap-certification-testing
 Importance: Medium
 Assignee: Canonical Hardware Certification (canonical-hw-cert)
 Status: New

** Affects: kernel-sru-workflow/snap-release-to-beta
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/snap-release-to-candidate
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/snap-release-to-edge
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/snap-release-to-stable
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/upload-to-ppa
 Importance: Medium
 Status: Invalid

** Affects: kernel-sru-workflow/verification-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

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


** Tags: kernel-release-tracking-bug kernel-release-tracking-bug-live 
kernel-sru-cycle-2017.11.20-8 kernel-sru-master-kernel xenial

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

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

** Tags added: xenial

** Also affects: kernel-sru-workflow/automated-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/certification-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/prepare-package
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/prepare-package-meta
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/prepare-package-signed
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/promote-to-proposed
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/promote-to-security
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/promote-to-updates
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/regression-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/security-signoff
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/snap-certification-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/snap-release-to-beta
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/snap-release-to-candidate
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/snap-release-to-edge
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/snap-release-to-stable
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/upload-to-ppa
   Importance: Undecided
   Status: New

** 

Re: [Kernel-packages] [Bug 1742789] Re: Xen PV Guest won't boot latest kernel- OSError: [Errno 28] No space left on device

2018-01-12 Thread Michael
Thanks for your help on this issue.  4.15-rc7 also fails to boot.


[Errno 28] No space left on device
Error writing temporary copy of ramdisk

libxl: error: libxl_bootloader.c:628:bootloader_finished: bootloader failed
- consult logfile /var/log/xen/bootloader.48.log
libxl: error: libxl_exec.c:118:libxl_report_child_exitstatus: bootloader
[-1] exited with error status 1
libxl: error: libxl_create.c:1024:domcreate_rebuild_done: cannot (re-)build
domain: -3



On Fri, Jan 12, 2018 at 9:43 AM, Joseph Salisbury <
joseph.salisb...@canonical.com> wrote:

> Thanks for testing.  That suggests this bug is not due to the PTI
> security patches.
>
> Can you next test the latest mainline kernel to see if this bug is
> already fixed upstream.  It can be downloaded from:
>
> http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.15-rc7
>
> ** Tags removed: pti
>
> ** Tags added: needs-bisect
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1742789
>
> Title:
>   Xen PV Guest won't boot latest kernel- OSError: [Errno 28] No space
>   left on device
>
> Status in linux package in Ubuntu:
>   Confirmed
>
> Bug description:
>   # lsb_release -rd
>   Description:  Ubuntu 16.04.3 LTS
>   Release:  16.04
>
>
>   This problem is related to the latest kernel for meltdown spectre
> patches for xen pv guest and pygrub.
>
>   This is the kernel that was attempting to be upgraded.
>   linux-image-4.4.0-109-generic   4.4.0-109.132
>
>
>   I tried to report this issue with the following command but it failed:
>
>   
>   ubuntu-bug linux
>
>
>
>   *** Collecting problem information
>
>
>
>   The collected information can be sent to the developers to improve the
>
>   application. This might take a few minutes.
>
>   ...
>
>
>
>   *** Problem in linux-image-4.4.0-15-generic
>
>
>
>   The problem cannot be reported:
>
>
>
>   This is not an official Ubuntu package. Please remove any third party
>   package and try again.
>
>
>
>   Press any key to continue...
>
>
>
>   No pending crash reports. Try --help for more information.
>
>   
>
>
>   I have an Ubuntu 14.04 running Xen and a VM running Ubuntu 16.04 LTS
>   that I'm having issues with it booting after upgrading the kernel for
>   meltdown and spectre vulnerability.
>
>   
>   sudo apt-get update
>   sudo apt-get upgrade
>   sudo apt-get dist-upgrade
>   
>
>   Ubuntu 14.04 xen host reboot failure log:
>   
>   $ tailf /var/log/xen/servername.log
>   Domain 24 needs to be cleaned up: destroying the domain
>   Done. Rebooting now
>   libxl: error: libxl_bootloader.c:628:bootloader_finished: bootloader
> failed - consult logfile /var/log/xen/bootloader.27.log
>   libxl: error: libxl_exec.c:118:libxl_report_child_exitstatus:
> bootloader [-1] exited with error status 1
>   libxl: error: libxl_create.c:1024:domcreate_rebuild_done: cannot
> (re-)build domain: -3
>   
>
>
>   
>   cat /var/log/xen/bootloader.27.log
>   Using  to parse /grub/grub.cfg
>   pyGRUB  version 0.6
>┌───
> ─┐
>│ Ubuntu
>  │
>│ Ubuntu, with Linux 4.4.0-109-generic
>  │
>│ Ubuntu, with Linux 4.4.0-109-generic (recovery mode)
>  │
>│ Ubuntu, with Linux 4.4.0-108-generic
>  │
>│ Ubuntu, with Linux 4.4.0-108-generic (recovery mode)
>  │
>│ Ubuntu, with Linux 4.4.0-104-generic
>  │
>│ Ubuntu, with Linux 4.4.0-104-generic (recovery mode)
>  │
>│ Ubuntu, with Linux 4.4.0-15-generic
>   │
>└───
> ─┘
>   Use the ^ and ┴ keys to select which entry is highlighted.
>   Press enter to boot the selected OS, 'e' to edit the
>   commands before booting, 'a' to modify the kernel arguments
>   before booting, or 'c' for a command line.
>
>   Traceback (most recent call last):
> File "/usr/lib/xen-4.4/bin/pygrub", line 905, in 
>   os.write(fd, ostring)
>   OSError: [Errno 28] No space left on device
>   
>
>   I was able to get the vm to boot only by rapidly attempt to access the
>   menu options and boot the old kernel (4.4.0-15-generic). Disk space
>   and inodes seems fine on the host Ubuntu 14.04LTS and Ubuntu 16.04LTS
>   Guest.
>
>   Ubuntu 14.04 Host:
>   
>   root@host:/var/log/xen# df -hFilesystem  Size  Used Avail Use%
> Mounted on
>   udev197M   12K  197M   1% /dev
>   tmpfs42M  1.1M   41M   3% /run
>   /dev/dm-0   104G   49G   50G  50% /
>   none4.0K 0  4.0K   0% /sys/fs/cgroup
>   none5.0M 0  5.0M   0% /run/lock
>   none208M 0  208M   0% /run/shm
>   none100M 0  100M   0% /run/user
>   /dev/sda1   236M   40M  184M  18% /boot
>   root@host:/var/log/xen# df -hi
>   Filesystem Inodes IUsed IFree IUse% Mounted on
>   udev  50K   721   49K2% /dev
>   tmpfs 52K   849   52K2% 

[Kernel-packages] [Bug 1742988] [NEW] linux-aws: -proposed tracker

2018-01-12 Thread Marcelo Cerri
Public bug reported:

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: 1742979

** Affects: kernel-sru-workflow
 Importance: Medium
 Status: Invalid

** Affects: kernel-sru-workflow/automated-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: Invalid

** Affects: kernel-sru-workflow/certification-testing
 Importance: Medium
 Assignee: Canonical Hardware Certification (canonical-hw-cert)
 Status: Invalid

** Affects: kernel-sru-workflow/prepare-package
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: Invalid

** Affects: kernel-sru-workflow/prepare-package-meta
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: Invalid

** Affects: kernel-sru-workflow/promote-to-proposed
 Importance: Medium
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru)
 Status: Invalid

** Affects: kernel-sru-workflow/promote-to-security
 Importance: Medium
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru)
 Status: Invalid

** Affects: kernel-sru-workflow/promote-to-updates
 Importance: Medium
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru)
 Status: Invalid

** Affects: kernel-sru-workflow/regression-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: Invalid

** Affects: kernel-sru-workflow/security-signoff
 Importance: Medium
 Assignee: Canonical Security Team (canonical-security)
 Status: Invalid

** Affects: kernel-sru-workflow/snap-release-to-beta
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: Invalid

** Affects: kernel-sru-workflow/snap-release-to-candidate
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: Invalid

** Affects: kernel-sru-workflow/snap-release-to-edge
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: Invalid

** Affects: kernel-sru-workflow/snap-release-to-stable
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: Invalid

** Affects: kernel-sru-workflow/upload-to-ppa
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: Invalid

** Affects: kernel-sru-workflow/verification-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: Invalid

** Affects: linux-aws (Ubuntu)
 Importance: Undecided
 Status: Invalid


** Tags: kernel-release-tracking-bug kernel-release-tracking-bug-live 
kernel-sru-cycle-2017.11.20-8 kernel-sru-derivative-of-1742979 xenial

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

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

** Tags added: xenial

** Also affects: kernel-sru-workflow/automated-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/certification-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/prepare-package
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/prepare-package-meta
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/promote-to-proposed
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/promote-to-security
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/promote-to-updates
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/regression-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/security-signoff
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/snap-release-to-beta
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/snap-release-to-candidate
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/snap-release-to-edge
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/snap-release-to-stable
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/upload-to-ppa
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/verification-testing
   Importance: Undecided
   Status: New

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

** Changed in: kernel-sru-workflow
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/automated-testing
   Importance: Undecided => Medium

** Changed in: 

[Kernel-packages] [Bug 1742979] [NEW] linux: -proposed tracker

2018-01-12 Thread Marcelo Cerri
Public bug reported:

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

** Affects: kernel-sru-workflow
 Importance: Medium
 Status: In Progress

** Affects: kernel-sru-workflow/automated-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/certification-testing
 Importance: Medium
 Assignee: Canonical Hardware Certification (canonical-hw-cert)
 Status: New

** Affects: kernel-sru-workflow/prepare-package
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: Confirmed

** Affects: kernel-sru-workflow/prepare-package-meta
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/prepare-package-signed
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/promote-to-proposed
 Importance: Medium
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru)
 Status: New

** Affects: kernel-sru-workflow/promote-to-security
 Importance: Medium
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru)
 Status: New

** Affects: kernel-sru-workflow/promote-to-updates
 Importance: Medium
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru)
 Status: New

** Affects: kernel-sru-workflow/regression-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/security-signoff
 Importance: Medium
 Assignee: Canonical Security Team (canonical-security)
 Status: New

** Affects: kernel-sru-workflow/snap-certification-testing
 Importance: Medium
 Assignee: Canonical Hardware Certification (canonical-hw-cert)
 Status: New

** Affects: kernel-sru-workflow/snap-release-to-beta
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/snap-release-to-candidate
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/snap-release-to-edge
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/snap-release-to-stable
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/upload-to-ppa
 Importance: Medium
 Status: Invalid

** Affects: kernel-sru-workflow/verification-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

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


** Tags: kernel-release-tracking-bug kernel-release-tracking-bug-live 
kernel-sru-cycle-2017.11.20-8 kernel-sru-master-kernel xenial

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

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

** Tags added: xenial

** Also affects: kernel-sru-workflow/automated-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/certification-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/prepare-package
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/prepare-package-meta
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/prepare-package-signed
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/promote-to-proposed
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/promote-to-security
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/promote-to-updates
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/regression-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/security-signoff
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/snap-certification-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/snap-release-to-beta
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/snap-release-to-candidate
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/snap-release-to-edge
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/snap-release-to-stable
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/upload-to-ppa
   Importance: Undecided
   Status: New

** 

[Kernel-packages] [Bug 1742980] [NEW] linux-aws: -proposed tracker

2018-01-12 Thread Marcelo Cerri
Public bug reported:

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: 1742979

** Affects: kernel-sru-workflow
 Importance: Medium
 Status: In Progress

** Affects: kernel-sru-workflow/automated-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/certification-testing
 Importance: Medium
 Assignee: Canonical Hardware Certification (canonical-hw-cert)
 Status: New

** Affects: kernel-sru-workflow/prepare-package
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/prepare-package-meta
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/promote-to-proposed
 Importance: Medium
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru)
 Status: New

** Affects: kernel-sru-workflow/promote-to-security
 Importance: Medium
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru)
 Status: New

** Affects: kernel-sru-workflow/promote-to-updates
 Importance: Medium
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru)
 Status: New

** Affects: kernel-sru-workflow/regression-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/security-signoff
 Importance: Medium
 Assignee: Canonical Security Team (canonical-security)
 Status: New

** Affects: kernel-sru-workflow/upload-to-ppa
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/verification-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: linux-aws (Ubuntu)
 Importance: Undecided
 Status: Invalid


** Tags: kernel-release-tracking-bug kernel-release-tracking-bug-live 
kernel-sru-backport-of-1742979 kernel-sru-cycle-2017.11.20-8 trusty

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

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

** Tags added: trusty

** Also affects: kernel-sru-workflow/automated-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/certification-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/prepare-package
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/prepare-package-meta
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/promote-to-proposed
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/promote-to-security
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/promote-to-updates
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/regression-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/security-signoff
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/upload-to-ppa
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/verification-testing
   Importance: Undecided
   Status: New

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

** Changed in: kernel-sru-workflow
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/automated-testing
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/automated-testing
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-sru-workflow/certification-testing
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/certification-testing
 Assignee: (unassigned) => Canonical Hardware Certification 
(canonical-hw-cert)

** Changed in: kernel-sru-workflow/prepare-package
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/prepare-package
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-sru-workflow/prepare-package-meta
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/prepare-package-meta
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-sru-workflow/promote-to-proposed
   Importance: Undecided => Medium

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

** Changed in: kernel-sru-workflow/promote-to-security
   Importance: Undecided => Medium

** Changed in: 

[Kernel-packages] [Bug 1733662] Re: System hang with Linux kernel due to mainline commit 24247aeeabe

2018-01-12 Thread Joseph Salisbury
Hi Vikas,

A kernel bug report was opened against Ubuntu [0].  After a kernel
bisect, it was found that reverting the following commit resolved this bug:

commit 24247aeeabe99eab13b798c2dec066dd6f07
Author: Vikas Shivappa 
Date:   Tue Aug 15 18:00:43 2017 -0700

    x86/intel_rdt/cqm: Improve limbo list processing


The regression was introduced as of v4.14-r1 and still exists with
current mainline.  The trace with v4.15-rc7 is in comment #44[1].

I was hoping to get your feedback, since you are the patch author.  Do
you think gathering any additional data will help diagnose this issue,
or would it be best to submit a revert request?


Thanks,

Joe
[0] http://pad.lv/1733662
[1]
https://bugs.launchpad.net/ubuntu/+source/linux-hwe/+bug/1733662/comments/44



** Summary changed:

- System hang with Linux kernel 4.13, not with 4.10
+ System hang with Linux kernel due to mainline commit 24247aeeabe

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

Title:
  System hang with Linux kernel due to mainline commit 24247aeeabe

Status in linux package in Ubuntu:
  In Progress
Status in linux-hwe package in Ubuntu:
  Confirmed
Status in linux source package in Artful:
  In Progress
Status in linux-hwe source package in Artful:
  Confirmed
Status in linux source package in Bionic:
  In Progress
Status in linux-hwe source package in Bionic:
  Confirmed

Bug description:
  In doing Ubuntu 17.10 regression testing, we've encountered one
  computer (boldore, a Cisco UCS C240 M4 [VIC]), that hangs about one in
  four times when running our cpu_offlining test. This test attempts to
  take all the CPU cores offline except one, then brings them back
  online again. This test ran successfully on boldore with previous
  releases, but with 17.10, the system sometimes (about one in four
  runs) hangs. Reverting to Ubuntu 16.04.3, I found no problems; but
  when I upgraded the 16.04.3 installation to linux-
  image-4.13.0-16-generic, the problem appeared again, so I'm confident
  this is a problem with the kernel. I'm attaching two files, dmesg-
  output-4.10.txt and dmesg-output-4.13.txt, which show the dmesg output
  that appears when running the cpu_offlining test with 4.10.0-38 and
  4.13.0-16 kernels, respectively; the system hung on the 4.13 run. (I
  was running "dmesg -w" in a second SSH login; the files are cut-and-
  pasted from that.)

  I initiated this bug report from an Ubuntu 16.04.3 installation
  running a 4.10 kernel; but as I said, this applies to the 4.13 kernel.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.10.0-38-generic 4.10.0-38.42~16.04.1
  ProcVersionSignature: User Name 4.10.0-38.42~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-38-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  Date: Tue Nov 21 17:36:06 2017
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-hwe
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Kernel-packages] [Bug 1742324] Re: Bionic kernel panics in the MAAS ephemeral environment

2018-01-12 Thread Joseph Salisbury
It might also be worthwhile to test the latest upstream 4.13 kernel:
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.13.16/

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

Title:
  Bionic kernel panics in the MAAS ephemeral environment

Status in MAAS:
  Triaged
Status in linux package in Ubuntu:
  Triaged

Bug description:
  Bionic kernel panics in the MAAS ephemeral environment. This does not
  always happen during commissioning or testing but does happen every
  time when trying to enter rescue mode. The test system is a KVM
  machine using all VirtIO drivers running on a Bionic host system. Both
  systems are using the 4.13.0-17-generic kernel.

  [   13.774332] BUG: unable to handle kernel paging request at f672c3075a20
  [   13.775203] IP: kfree+0x53/0x160
  [   13.775665] PGD 0 
  [   13.775666] P4D 0 
  [   13.775965] 
  [   13.776566] Oops:  [#1] SMP
  [   13.777004] Modules linked in: iscsi_tcp libiscsi_tcp libiscsi 
scsi_transport_iscsi overlay 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 crct10dif_pclmul crc32_pclmul 
ghash_clmulni_intel pcbc ttm drm_kms_helper aesni_intel syscopyarea sysfillrect 
aes_x86_64 crypto_simd glue_helper cryptd sysimgblt fb_sys_fops drm psmouse 
virtio_blk virtio_net pata_acpi floppy
  [   13.782468] CPU: 0 PID: 696 Comm: lxd Not tainted 4.13.0-17-generic 
#20-Ubuntu
  [   13.783169] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 
1.10.2-1ubuntu1 04/01/2014
  [   13.784028] task: 9afa30b62e80 task.stack: c07640a5
  [   13.784512] RIP: 0010:kfree+0x53/0x160
  [   13.784884] RSP: 0018:9afa3ca03a18 EFLAGS: 00010286
  [   13.785339] RAX:  RBX: f50a81d68280 RCX: 
0002
  [   13.785983] RDX: 457c0321e918 RSI: 00010080 RDI: 
6505c000
  [   13.786916] RBP: 9afa3ca03a30 R08: 0001f4c0 R09: 
94bbb839
  [   13.787877] R10: f672c3075a00 R11: e4e5cd01 R12: 
9afa3f794000
  [   13.788854] R13: 947a155e R14: 9afa3f794000 R15: 
9afa3f794000
  [   13.789882] FS:  7fc4a7938cc0() GS:9afa3ca0() 
knlGS:
  [   13.791134] CS:  0010 DS:  ES:  CR0: 80050033
  [   13.792003] CR2: f672c3075a20 CR3: 737f6000 CR4: 
001406f0
  [   13.793019] Call Trace:
  [   13.793462]  
  [   13.793886]  security_sk_free+0x3e/0x50
  [   13.794680]  __sk_destruct+0x108/0x190
  [   13.795465]  sk_destruct+0x20/0x30
  [   13.796193]  __sk_free+0x82/0xa0
  [   13.796899]  sk_free+0x19/0x20
  [   13.797537]  sock_put+0x14/0x20
  [   13.797926]  tcp_v4_rcv+0x94d/0x9d0
  [   13.798325]  ? ep_poll_callback+0x226/0x2b0
  [   13.798704]  ip_local_deliver_finish+0x5c/0x1f0
  [   13.799099]  ip_local_deliver+0x6f/0xe0
  [   13.799455]  ip_rcv_finish+0x120/0x410
  [   13.799868]  ip_rcv+0x28c/0x3a0
  [   13.800221]  ? csum_partial+0x11/0x20
  [   13.800649]  __netif_receive_skb_core+0x39a/0xaa0
  [   13.801295]  ? skb_checksum+0x35/0x50
  [   13.801742]  ? skb_append_datato_frags+0x200/0x200
  [   13.802164]  ? reqsk_fastopen_remove+0x140/0x140
  [   13.802576]  __netif_receive_skb+0x18/0x60
  [   13.803163]  ? __netif_receive_skb+0x18/0x60
  [   13.803798]  netif_receive_skb_internal+0x3f/0x3f0
  [   13.804538]  ? dev_gro_receive+0x2dc/0x480
  [   13.805210]  napi_gro_receive+0xc2/0xe0
  [   13.805851]  receive_buf+0x218/0xf70 [virtio_net]
  [   13.806591]  ? vring_unmap_one+0x1b/0x80
  [   13.807240]  virtnet_poll+0x173/0x268 [virtio_net]
  [   13.807998]  net_rx_action+0x13b/0x380
  [   13.808621]  ? skb_recv_done+0x30/0x40 [virtio_net]
  [   13.810159]  __do_softirq+0xde/0x2a5
  [   13.810673]  irq_exit+0xb6/0xc0
  [   13.811185]  do_IRQ+0x80/0xd0
  [   13.811881]  common_interrupt+0x89/0x89
  [   13.812668] RIP: 0010:filemap_fault+0xff/0x5e0
  [   13.819490] RSP: 0018:c07640a53cc8 EFLAGS: 0202 ORIG_RAX: 
ff8e
  [   13.820174] RAX: 0012e288 RBX: 9afa3f6e0800 RCX: 
0054
  [   13.820760] RDX:  RSI: 9afa30b64180 RDI: 
9afa3ca1c200
  [   13.821339] RBP: c07640a53d70 R08: 0310 R09: 
0001
  [   13.821917] R10: c076406ab738 R11: 00d2 R12: 
00ea
  [   13.822493] R13: 9afa3262e900 R14: f50a8174eec0 R15: 
c07640a53db8
  [   13.823075]  
  [   13.823327]  ? filemap_fault+0xb0/0x5e0
  [   13.823703]  ? filemap_map_pages+0x179/0x320
  [   13.824101]  __do_fault+0x1e/0xb0
  [   13.824434]  __handle_mm_fault+0xba7/0x1020
  [   13.824821]  handle_mm_fault+0xb1/0x200
  [   13.825189]  __do_page_fault+0x24d/0x4d0
  [   13.825560]  trace_do_page_fault+0x37/0xd0
  [   13.826051]  do_async_page_fault+0x51/0x80
  [   13.826652]  async_page_fault+0x28/0x30
  [   13.827246] 

[Kernel-packages] [Bug 1742324] Re: Bionic kernel panics in the MAAS ephemeral environment

2018-01-12 Thread Joseph Salisbury
Thanks for the update.  We can perform a "Reverse" bisect to identify
the commit that fixes this bug in mainline.  We would first need to
identify the last kernel version that had the bug and the first version
that did not have the bug.  We now know that v4.15-rc7 is fixed.  Can
you next test v4.15-rc1?  It can be downloaded from:

 http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.15-rc1

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

Title:
  Bionic kernel panics in the MAAS ephemeral environment

Status in MAAS:
  Triaged
Status in linux package in Ubuntu:
  Triaged

Bug description:
  Bionic kernel panics in the MAAS ephemeral environment. This does not
  always happen during commissioning or testing but does happen every
  time when trying to enter rescue mode. The test system is a KVM
  machine using all VirtIO drivers running on a Bionic host system. Both
  systems are using the 4.13.0-17-generic kernel.

  [   13.774332] BUG: unable to handle kernel paging request at f672c3075a20
  [   13.775203] IP: kfree+0x53/0x160
  [   13.775665] PGD 0 
  [   13.775666] P4D 0 
  [   13.775965] 
  [   13.776566] Oops:  [#1] SMP
  [   13.777004] Modules linked in: iscsi_tcp libiscsi_tcp libiscsi 
scsi_transport_iscsi overlay 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 crct10dif_pclmul crc32_pclmul 
ghash_clmulni_intel pcbc ttm drm_kms_helper aesni_intel syscopyarea sysfillrect 
aes_x86_64 crypto_simd glue_helper cryptd sysimgblt fb_sys_fops drm psmouse 
virtio_blk virtio_net pata_acpi floppy
  [   13.782468] CPU: 0 PID: 696 Comm: lxd Not tainted 4.13.0-17-generic 
#20-Ubuntu
  [   13.783169] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 
1.10.2-1ubuntu1 04/01/2014
  [   13.784028] task: 9afa30b62e80 task.stack: c07640a5
  [   13.784512] RIP: 0010:kfree+0x53/0x160
  [   13.784884] RSP: 0018:9afa3ca03a18 EFLAGS: 00010286
  [   13.785339] RAX:  RBX: f50a81d68280 RCX: 
0002
  [   13.785983] RDX: 457c0321e918 RSI: 00010080 RDI: 
6505c000
  [   13.786916] RBP: 9afa3ca03a30 R08: 0001f4c0 R09: 
94bbb839
  [   13.787877] R10: f672c3075a00 R11: e4e5cd01 R12: 
9afa3f794000
  [   13.788854] R13: 947a155e R14: 9afa3f794000 R15: 
9afa3f794000
  [   13.789882] FS:  7fc4a7938cc0() GS:9afa3ca0() 
knlGS:
  [   13.791134] CS:  0010 DS:  ES:  CR0: 80050033
  [   13.792003] CR2: f672c3075a20 CR3: 737f6000 CR4: 
001406f0
  [   13.793019] Call Trace:
  [   13.793462]  
  [   13.793886]  security_sk_free+0x3e/0x50
  [   13.794680]  __sk_destruct+0x108/0x190
  [   13.795465]  sk_destruct+0x20/0x30
  [   13.796193]  __sk_free+0x82/0xa0
  [   13.796899]  sk_free+0x19/0x20
  [   13.797537]  sock_put+0x14/0x20
  [   13.797926]  tcp_v4_rcv+0x94d/0x9d0
  [   13.798325]  ? ep_poll_callback+0x226/0x2b0
  [   13.798704]  ip_local_deliver_finish+0x5c/0x1f0
  [   13.799099]  ip_local_deliver+0x6f/0xe0
  [   13.799455]  ip_rcv_finish+0x120/0x410
  [   13.799868]  ip_rcv+0x28c/0x3a0
  [   13.800221]  ? csum_partial+0x11/0x20
  [   13.800649]  __netif_receive_skb_core+0x39a/0xaa0
  [   13.801295]  ? skb_checksum+0x35/0x50
  [   13.801742]  ? skb_append_datato_frags+0x200/0x200
  [   13.802164]  ? reqsk_fastopen_remove+0x140/0x140
  [   13.802576]  __netif_receive_skb+0x18/0x60
  [   13.803163]  ? __netif_receive_skb+0x18/0x60
  [   13.803798]  netif_receive_skb_internal+0x3f/0x3f0
  [   13.804538]  ? dev_gro_receive+0x2dc/0x480
  [   13.805210]  napi_gro_receive+0xc2/0xe0
  [   13.805851]  receive_buf+0x218/0xf70 [virtio_net]
  [   13.806591]  ? vring_unmap_one+0x1b/0x80
  [   13.807240]  virtnet_poll+0x173/0x268 [virtio_net]
  [   13.807998]  net_rx_action+0x13b/0x380
  [   13.808621]  ? skb_recv_done+0x30/0x40 [virtio_net]
  [   13.810159]  __do_softirq+0xde/0x2a5
  [   13.810673]  irq_exit+0xb6/0xc0
  [   13.811185]  do_IRQ+0x80/0xd0
  [   13.811881]  common_interrupt+0x89/0x89
  [   13.812668] RIP: 0010:filemap_fault+0xff/0x5e0
  [   13.819490] RSP: 0018:c07640a53cc8 EFLAGS: 0202 ORIG_RAX: 
ff8e
  [   13.820174] RAX: 0012e288 RBX: 9afa3f6e0800 RCX: 
0054
  [   13.820760] RDX:  RSI: 9afa30b64180 RDI: 
9afa3ca1c200
  [   13.821339] RBP: c07640a53d70 R08: 0310 R09: 
0001
  [   13.821917] R10: c076406ab738 R11: 00d2 R12: 
00ea
  [   13.822493] R13: 9afa3262e900 R14: f50a8174eec0 R15: 
c07640a53db8
  [   13.823075]  
  [   13.823327]  ? filemap_fault+0xb0/0x5e0
  [   13.823703]  ? filemap_map_pages+0x179/0x320
  [   13.824101]  __do_fault+0x1e/0xb0
  [   13.824434]  

[Kernel-packages] [Bug 1742789] Re: Xen PV Guest won't boot latest kernel- OSError: [Errno 28] No space left on device

2018-01-12 Thread Joseph Salisbury
Thanks for testing.  That suggests this bug is not due to the PTI
security patches.

Can you next test the latest mainline kernel to see if this bug is
already fixed upstream.  It can be downloaded from:

http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.15-rc7

** Tags removed: pti

** Tags added: needs-bisect

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

Title:
  Xen PV Guest won't boot latest kernel- OSError: [Errno 28] No space
  left on device

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  # lsb_release -rd
  Description:  Ubuntu 16.04.3 LTS
  Release:  16.04

  
  This problem is related to the latest kernel for meltdown spectre patches for 
xen pv guest and pygrub.

  This is the kernel that was attempting to be upgraded.
  linux-image-4.4.0-109-generic   4.4.0-109.132 

  
  I tried to report this issue with the following command but it failed:

  
  ubuntu-bug linux



  *** Collecting problem information



  The collected information can be sent to the developers to improve the

  application. This might take a few minutes.

  ...



  *** Problem in linux-image-4.4.0-15-generic



  The problem cannot be reported:



  This is not an official Ubuntu package. Please remove any third party
  package and try again.



  Press any key to continue...



  No pending crash reports. Try --help for more information.

  


  I have an Ubuntu 14.04 running Xen and a VM running Ubuntu 16.04 LTS
  that I'm having issues with it booting after upgrading the kernel for
  meltdown and spectre vulnerability.

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

  Ubuntu 14.04 xen host reboot failure log:
  
  $ tailf /var/log/xen/servername.log
  Domain 24 needs to be cleaned up: destroying the domain
  Done. Rebooting now
  libxl: error: libxl_bootloader.c:628:bootloader_finished: bootloader failed - 
consult logfile /var/log/xen/bootloader.27.log
  libxl: error: libxl_exec.c:118:libxl_report_child_exitstatus: bootloader [-1] 
exited with error status 1
  libxl: error: libxl_create.c:1024:domcreate_rebuild_done: cannot (re-)build 
domain: -3
  

  
  
  cat /var/log/xen/bootloader.27.log
  Using  to parse /grub/grub.cfg
pyGRUB  version 0.6
   ┌┐
   │ Ubuntu │
   │ Ubuntu, with Linux 4.4.0-109-generic   │
   │ Ubuntu, with Linux 4.4.0-109-generic (recovery mode)   │
   │ Ubuntu, with Linux 4.4.0-108-generic   │
   │ Ubuntu, with Linux 4.4.0-108-generic (recovery mode)   │
   │ Ubuntu, with Linux 4.4.0-104-generic   │
   │ Ubuntu, with Linux 4.4.0-104-generic (recovery mode)   │
   │ Ubuntu, with Linux 4.4.0-15-generic│
   └┘
  Use the ^ and ┴ keys to select which entry is highlighted.
  Press enter to boot the selected OS, 'e' to edit the
  commands before booting, 'a' to modify the kernel arguments
  before booting, or 'c' for a command line.

  Traceback (most recent call last):
File "/usr/lib/xen-4.4/bin/pygrub", line 905, in 
  os.write(fd, ostring)
  OSError: [Errno 28] No space left on device
  

  I was able to get the vm to boot only by rapidly attempt to access the
  menu options and boot the old kernel (4.4.0-15-generic). Disk space
  and inodes seems fine on the host Ubuntu 14.04LTS and Ubuntu 16.04LTS
  Guest.

  Ubuntu 14.04 Host:
  
  root@host:/var/log/xen# df -hFilesystem  Size  Used Avail Use% Mounted on
  udev197M   12K  197M   1% /dev
  tmpfs42M  1.1M   41M   3% /run
  /dev/dm-0   104G   49G   50G  50% /
  none4.0K 0  4.0K   0% /sys/fs/cgroup
  none5.0M 0  5.0M   0% /run/lock
  none208M 0  208M   0% /run/shm
  none100M 0  100M   0% /run/user
  /dev/sda1   236M   40M  184M  18% /boot
  root@host:/var/log/xen# df -hi
  Filesystem Inodes IUsed IFree IUse% Mounted on
  udev  50K   721   49K2% /dev
  tmpfs 52K   849   52K2% /run
  /dev/dm-06.6M   86K  6.5M2% /
  none  52K 2   52K1% /sys/fs/cgroup
  none  52K 5   52K1% /run/lock
  none  52K 1   52K1% /run/shm
  none  52K 2   52K1% /run/user
  /dev/sda1 61K   298   61K1% /boot
  root@host:/var/log/xen#
  

  Ubuntu 16.04 PV Guest:
  
  root@guest:~# df -hFilesystemSize  Used Avail 
Use% Mounted on
  udev  950M 0  950M   0% /dev
  

[Kernel-packages] [Bug 1742572] Re: System Hangs and General Protection Fault Occurs following NFS Access

2018-01-12 Thread Joseph Salisbury
*** This bug is a duplicate of bug 1734327 ***
https://bugs.launchpad.net/bugs/1734327

A SRU request has been submitted to have the problematic commit reverted
until the permanent fix comes down from upstream.

I'll mark this bug as a duplicate of bug 1734327

** This bug has been marked a duplicate of bug 1734327
   Kernel panic on a nfsroot system

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

Title:
  System Hangs and General Protection Fault Occurs following NFS Access

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

Bug description:
  Last night, in an attempt to secure my system against
  Meltdown/Spectre, I upgraded from Zesty to Artful. Upon booting into
  the latest kernel, my system would immediately hang and fail to
  respond (including to SysRq commands).

  Both this (my primary) system and an Intel NUC (which were both
  upgraded from Zesty to Artful at the same time) export NFS shares to
  one other. The NUC appears to be error-free, but my primary system
  seems to crash whenever I attempt to access the NFS share of NUC.

  As I have not tried any other kernel releases in either system other
  than 4.13.0-25.29, it's impossible for me to say if this is an issue
  regarding the recent security patch, or if it is some other issue.

  Attached is the console log (obtained via netconsole) which includes
  the kernel trace of the error.

  Please let me know if further information is required or if I can help
  further in troubleshooting.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-25-generic 4.13.0-25.29
  ProcVersionSignature: Ubuntu 4.10.0-42.46-generic 4.10.17
  Uname: Linux 4.10.0-42-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  mvastola   4661 F pulseaudio
   /dev/snd/controlC1:  mvastola   4661 F pulseaudio
  CurrentDesktop: KDE
  Date: Wed Jan 10 18:18:52 2018
  InstallationDate: Installed on 2012-01-06 (2196 days ago)
  InstallationMedia: Kubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111011)
  IwConfig:
   lono wireless extensions.

   mike  no wireless extensions.

   docker0   no wireless extensions.
  MachineType: Gigabyte Technology Co., Ltd. GA-990XA-UD3
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-42-generic 
root=/dev/mapper/VastDesk-RootOS ro apparmor=0 
netconsole=@10.12.1.55/mike,@10.12.1.1/8c:ae:4c:f4:83:1a 
crashkernel=384M-:128M crashkernel=384M-:128M
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-42-generic N/A
   linux-backports-modules-4.10.0-42-generic  N/A
   linux-firmware 1.169.1
  RfKill:
   0: hci0: Bluetooth
    Soft blocked: no
    Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: Upgraded to artful on 2014-12-03 (1134 days ago)
  dmi.bios.date: 09/09/2014
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F14e
  dmi.board.name: GA-990XA-UD3
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF14e:bd09/09/2014:svnGigabyteTechnologyCo.,Ltd.:pnGA-990XA-UD3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-990XA-UD3:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: GA-990XA-UD3
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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


[Kernel-packages] [Bug 1734686] Re: BUG: unable to handle kernel paging request at ffffdf3cd60001a0

2018-01-12 Thread Joseph Salisbury
*** This bug is a duplicate of bug 1734327 ***
https://bugs.launchpad.net/bugs/1734327

** This bug has been marked a duplicate of bug 1734327
   Kernel panic on a nfsroot system

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

Title:
  BUG: unable to handle kernel paging request at df3cd60001a0

Status in linux package in Ubuntu:
  Triaged

Bug description:
  I can consistently reproduce this with the Ubuntu 17.10 kernel.  It
  never happens with a mainline 4.13.11 kernel built from source.

  To reproduce:

  1. clone https://github.com/nodejs/node (currently at commit 4ca4db0d4c)
  2. ./configure && make -j8
  3. ./out/Release/cctest

  cctest is sometimes killed, sometimes locks up the computer.  When the
  computer is still usable, the following message is logged:

  [36488.886799] BUG: unable to handle kernel paging request at df3cd60001a0
  [36488.886824] IP: kfree+0x53/0x190
  [36488.886831] PGD 0 
  [36488.886831] P4D 0 

  [36488.886844] Oops:  [#2] PREEMPT SMP
  [36488.886851] Modules linked in: xt_tcpudp iptable_filter cfg80211 
binfmt_misc snd_hda_codec_hdmi intel_rapl x86_pkg_temp_thermal intel_powerclamp 
coretemp kvm_intel kvm irqbypass crct10dif_pclmul crc32_pclmul 
ghash_clmulni_intel pcbc aesni_intel aes_x86_64 crypto_simd glue_helper cryptd 
snd_hda_codec_realtek snd_hda_codec_generic intel_cstate r8712u(C) 
intel_rapl_perf snd_seq_midi snd_seq_midi_event input_leds snd_hda_intel 
snd_rawmidi snd_hda_codec snd_hda_core snd_seq snd_hwdep snd_pcm snd_seq_device 
snd_timer snd ie31200_edac soundcore mei_me shpchp mei lpc_ich mac_hid cuse 
parport_pc ppdev lp parport ip_tables x_tables autofs4 nouveau mxm_wmi wmi 
i2c_algo_bit ttm drm_kms_helper syscopyarea sysfillrect hid_generic sysimgblt 
uas ahci fb_sys_fops usbhid usb_storage r8169 drm libahci hid mii video
  [36488.886940] CPU: 6 PID: 21882 Comm: cctest Tainted: G  D  C  
4.13.0-17-lowlatency #20-Ubuntu
  [36488.886947] Hardware name: MEDION H77H2-EM/H77H2-EM, BIOS EM0411-M8 
04/11/2012
  [36488.886951] task: 8ebd7c18a640 task.stack: a003ce10c000
  [36488.886957] RIP: 0010:kfree+0x53/0x190
  [36488.886961] RSP: 0018:a003ce10fd30 EFLAGS: 00010282
  [36488.886965] RAX:  RBX: 6fa8 RCX: 
0002
  [36488.886970] RDX: 314521002bc0 RSI: 00010080 RDI: 
7145
  [36488.888247] RBP: a003ce10fd48 R08: 0001f640 R09: 
a27c7979
  [36488.890131] R10: df3cd6000180 R11: 0100 R12: 
8ebe84406900
  [36488.892024] R13: a23aa5ee R14:  R15: 
8ebe8c611820
  [36488.901718] FS:  7f7666764b80() GS:8ebe9ed8() 
knlGS:
  [36488.906872] CS:  0010 DS:  ES:  CR0: 80050033
  [36488.908816] CR2: df3cd60001a0 CR3: 0002fc3c5000 CR4: 
001406e0
  [36488.910711] Call Trace:
  [36488.912512]  security_sk_free+0x3e/0x50
  [36488.914232]  __sk_destruct+0x108/0x190
  [36488.915872]  sk_destruct+0x20/0x30
  [36488.917483]  __sk_free+0x82/0xa0
  [36488.919064]  sk_free+0x19/0x20
  [36488.920626]  tcp_close+0x230/0x3f0
  [36488.922183]  inet_release+0x3c/0x60
  [36488.923714]  inet6_release+0x30/0x40
  [36488.925242]  sock_release+0x1f/0x80
  [36488.926785]  sock_close+0x12/0x20
  [36488.932837]  __fput+0xe1/0x220
  [36488.937778]  fput+0xe/0x10
  [36488.942441]  task_work_run+0x76/0x90
  [36488.943956]  exit_to_usermode_loop+0xc4/0xd0
  [36488.945467]  syscall_return_slowpath+0x59/0x60
  [36488.946973]  entry_SYSCALL_64_fastpath+0xa7/0xa9
  [36488.948468] RIP: 0033:0x7f7666376df0
  [36488.949967] RSP: 002b:7ffe98391250 EFLAGS: 0293 ORIG_RAX: 
0003
  [36488.951522] RAX:  RBX: 000c RCX: 
7f7666376df0
  [36488.953073] RDX:  RSI: 0002 RDI: 
000c
  [36488.954639] RBP: 000c R08: 55a301618920 R09: 
000a
  [36488.956208] R10: 7ffe9839126c R11: 0293 R12: 
0011
  [36488.957774] R13: 0020 R14: 0001 R15: 
7ffe983916ec
  [36488.959354] Code: 00 80 49 01 da 0f 82 47 01 00 00 48 c7 c7 00 00 00 80 48 
2b 3d ef 98 c1 00 49 01 fa 49 c1 ea 0c 49 c1 e2 06 4c 03 15 cd 98 c1 00 <49> 8b 
42 20 48 8d 50 ff a8 01 4c 0f 45 d2 49 8b 52 20 48 8d 42 
  [36488.961040] RIP: kfree+0x53/0x190 RSP: a003ce10fd30
  [36488.962714] CR2: df3cd60001a0
  [36488.964377] ---[ end trace 46732cc399d66b31 ]---

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-17-lowlatency 4.13.0-17.20
  ProcVersionSignature: Ubuntu 4.13.0-17.20-lowlatency 4.13.8
  Uname: Linux 4.13.0-17-lowlatency x86_64
  ApportVersion: 2.20.7-0ubuntu3.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  bnoordhuis   1664 F pulseaudio
   

[Kernel-packages] [Bug 1742572] Re: System Hangs and General Protection Fault Occurs following NFS Access

2018-01-12 Thread Joseph Salisbury
*** This bug is a duplicate of bug 1734327 ***
https://bugs.launchpad.net/bugs/1734327

** Tags removed: pti

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

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

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

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

** Also affects: linux (Ubuntu Bionic)
   Importance: High
   Status: Triaged

** Tags added: bionic

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

Title:
  System Hangs and General Protection Fault Occurs following NFS Access

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

Bug description:
  Last night, in an attempt to secure my system against
  Meltdown/Spectre, I upgraded from Zesty to Artful. Upon booting into
  the latest kernel, my system would immediately hang and fail to
  respond (including to SysRq commands).

  Both this (my primary) system and an Intel NUC (which were both
  upgraded from Zesty to Artful at the same time) export NFS shares to
  one other. The NUC appears to be error-free, but my primary system
  seems to crash whenever I attempt to access the NFS share of NUC.

  As I have not tried any other kernel releases in either system other
  than 4.13.0-25.29, it's impossible for me to say if this is an issue
  regarding the recent security patch, or if it is some other issue.

  Attached is the console log (obtained via netconsole) which includes
  the kernel trace of the error.

  Please let me know if further information is required or if I can help
  further in troubleshooting.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-25-generic 4.13.0-25.29
  ProcVersionSignature: Ubuntu 4.10.0-42.46-generic 4.10.17
  Uname: Linux 4.10.0-42-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  mvastola   4661 F pulseaudio
   /dev/snd/controlC1:  mvastola   4661 F pulseaudio
  CurrentDesktop: KDE
  Date: Wed Jan 10 18:18:52 2018
  InstallationDate: Installed on 2012-01-06 (2196 days ago)
  InstallationMedia: Kubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111011)
  IwConfig:
   lono wireless extensions.

   mike  no wireless extensions.

   docker0   no wireless extensions.
  MachineType: Gigabyte Technology Co., Ltd. GA-990XA-UD3
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-42-generic 
root=/dev/mapper/VastDesk-RootOS ro apparmor=0 
netconsole=@10.12.1.55/mike,@10.12.1.1/8c:ae:4c:f4:83:1a 
crashkernel=384M-:128M crashkernel=384M-:128M
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-42-generic N/A
   linux-backports-modules-4.10.0-42-generic  N/A
   linux-firmware 1.169.1
  RfKill:
   0: hci0: Bluetooth
    Soft blocked: no
    Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: Upgraded to artful on 2014-12-03 (1134 days ago)
  dmi.bios.date: 09/09/2014
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F14e
  dmi.board.name: GA-990XA-UD3
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF14e:bd09/09/2014:svnGigabyteTechnologyCo.,Ltd.:pnGA-990XA-UD3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-990XA-UD3:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: GA-990XA-UD3
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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


[Kernel-packages] [Bug 1732056] Re: Touchpad stops working after a few seconds in Lenovo ideapad 320

2018-01-12 Thread Kleber Sacilotto de Souza
** Changed in: linux-oem (Ubuntu Xenial)
   Status: New => Fix Committed

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

Title:
  Touchpad stops working after a few seconds in Lenovo ideapad 320

Status in HWE Next:
  Triaged
Status in linux package in Ubuntu:
  Triaged
Status in linux-oem package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Invalid
Status in linux-oem source package in Xenial:
  Fix Committed

Bug description:
  === SRU Justifications ===

  [Impact]
  Touchpad freezes after a brief usage.

  [Fix]
  Quote from the commit log:
  "The stale cached value written at the final stage undoes the masking.
  Fix this by re-reading the register before clearing the interrupt.

  I also spotted that the interrupt-clearing code can race against
  amd_gpio_irq_mask() / amd_gpio_irq_unmask(), so add locking there.
  Presumably this race was leading to the loss of interrupts."

  [Test Case]
  Touchpad no longer freezes on ideapad 320-15ABR, a new Dell Latitude and
  a new Dell Inspiron.

  [Regression Potential]
  Low. It limits to AMD laptops

  === Original Bug Report ===

  I have installed ubuntu bionic on a Lenovo ideapad 320. The touchpad
  stops working a few seconds after I log in.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.13.0-16-generic 4.13.0-16.19
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  rebeca 1440 F pulseaudio
   /dev/snd/controlC0:  rebeca 1440 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Nov 13 20:03:41 2017
  InstallationDate: Installed on 2017-09-22 (53 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170918)
  MachineType: LENOVO 80XS
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic.efi.signed 
root=UUID=1e55f665-bd98-4113-9ae8-ec766bfc424f ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-16-generic N/A
   linux-backports-modules-4.13.0-16-generic  N/A
   linux-firmware 1.169
  SourcePackage: linux
  UpgradeStatus: Upgraded to bionic on 2017-11-14 (0 days ago)
  dmi.bios.date: 05/22/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 5QCN16WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40700WIN
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad 320-15ABR
  dmi.modalias: 
dmi:bvnLENOVO:bvr5QCN16WW:bd05/22/2017:svnLENOVO:pn80XS:pvrLenovoideapad320-15ABR:rvnLENOVO:rnLNVNB161216:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrLenovoideapad320-15ABR:
  dmi.product.family: ideapad 320-15ABR
  dmi.product.name: 80XS
  dmi.product.version: Lenovo ideapad 320-15ABR
  dmi.sys.vendor: LENOVO

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

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


[Kernel-packages] [Bug 1736393] Re: [Artful][Wyse 3040] System hang when trying to enable an offlined CPU core

2018-01-12 Thread Kleber Sacilotto de Souza
** Changed in: linux-oem (Ubuntu Xenial)
   Status: New => Fix Committed

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

Title:
  [Artful][Wyse 3040] System hang when trying to enable an offlined CPU
  core

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  In Progress
Status in linux-oem package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Invalid
Status in linux-oem source package in Xenial:
  Fix Committed

Bug description:
  1. disable cpu[1-3] $ echo 0 > /sys/devices/system/cpu/cpu[1-3]/online
  2. enable cpu[1-3] $ echo 1 > /sys/devices/system/cpu/cpu[1-3]/online

  System will hang on step 2.

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

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


[Kernel-packages] [Bug 1738523] Re: External HDMI monitor failed to show screen on Lenovo X1 series

2018-01-12 Thread Kleber Sacilotto de Souza
** Changed in: linux-oem (Ubuntu Xenial)
   Status: New => Fix Committed

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

Title:
  External HDMI monitor failed to show screen on Lenovo X1 series

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Fix Committed
Status in linux-oem package in Ubuntu:
  New
Status in linux source package in Xenial:
  New
Status in linux-oem source package in Xenial:
  Fix Committed

Bug description:
  Thinkpad X1 yoga:
  CPU: Intel(R) Core(TM) i7-8550U CPU @ 1.80GHz (family: 0x6, model: 0x8e, 
stepping: 0xa)
  GPU: Intel Corporation Device [8086:5917] (rev 07) (prog-if 00 [VGA 
controller])

  Steps:
  1, Connect an external monitor
  2, Try to switch display modes in mirrored, extended, displayed on external 
or internal.

  [Impact]
  External HDMI monitor failed to show screen on Lenovo X1 yoga/carbon

  [Fix]
  Add a workaround to bypass this TMDS_OE writing on identified laptop models.

  [Test Case]
  Tested on ThinkPad X1 yoga 2nd/3rd and Carbon 6th, external HDMI output
  OK.

  [Regression Potential]
  Low, it limits to ThinkPad specific laptops.

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

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


[Kernel-packages] [Bug 1737890] Re: QCA Rome bluetooth can not wakeup after USB runtime suspended.

2018-01-12 Thread Kleber Sacilotto de Souza
** Changed in: linux-oem (Ubuntu Xenial)
   Status: New => Fix Committed

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

Title:
  QCA Rome bluetooth can not wakeup after USB runtime suspended.

Status in linux package in Ubuntu:
  Incomplete
Status in linux-oem package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Invalid
Status in linux-oem source package in Xenial:
  Fix Committed

Bug description:
  == SRU Justification ==
  [Impact]
  Some QCA ROME bluetooth devices does not work after runtime suspended.

  [Fix]
  Latest mainline does not have this issue. The bisected commit is 
a0085f2510e8976614ad8f766b209448b385492f "Bluetooth: btusb: driver to enable 
the usb-wakeup feature".
  With this commit, the BT device now can wake host controller up.

  [Test]
  Cherry-picked the commit into Artful/OEM kernel and the issue is fixed.

  [Regression Potential]
  Low. usb-wakeup support shouldn't affect the driver's function.

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

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


[Kernel-packages] [Bug 1738523] Re: External HDMI monitor failed to show screen on Lenovo X1 series

2018-01-12 Thread Timo Aaltonen
** Also affects: linux (Ubuntu Xenial)
   Importance: Undecided
   Status: New

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

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

Title:
  External HDMI monitor failed to show screen on Lenovo X1 series

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Fix Committed
Status in linux-oem package in Ubuntu:
  New
Status in linux source package in Xenial:
  New
Status in linux-oem source package in Xenial:
  Fix Committed

Bug description:
  Thinkpad X1 yoga:
  CPU: Intel(R) Core(TM) i7-8550U CPU @ 1.80GHz (family: 0x6, model: 0x8e, 
stepping: 0xa)
  GPU: Intel Corporation Device [8086:5917] (rev 07) (prog-if 00 [VGA 
controller])

  Steps:
  1, Connect an external monitor
  2, Try to switch display modes in mirrored, extended, displayed on external 
or internal.

  [Impact]
  External HDMI monitor failed to show screen on Lenovo X1 yoga/carbon

  [Fix]
  Add a workaround to bypass this TMDS_OE writing on identified laptop models.

  [Test Case]
  Tested on ThinkPad X1 yoga 2nd/3rd and Carbon 6th, external HDMI output
  OK.

  [Regression Potential]
  Low, it limits to ThinkPad specific laptops.

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

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


[Kernel-packages] [Bug 1736639] Re: Intel 9260/9462/9560 can't connect to 5GHz AP

2018-01-12 Thread Kleber Sacilotto de Souza
** Changed in: linux-oem (Ubuntu Xenial)
   Status: New => Fix Committed

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

Title:
  Intel 9260/9462/9560 can't connect to 5GHz AP

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

Bug description:
  With 1009 oem(v4.13) kernel and latest linux-firmware[1], it connect to 
2.4GHz APs without any issues.
  But it fails to connect 5GHz APs.

  It stucks when I select a 5GHz network AP, and after timeout it
  connects to another configured 2.4GHz AP.
  [ 512.404139] wlp0s20f3: authenticate with 2c:36:f8:fa:ec:00
  [ 512.410781] wlp0s20f3: send auth to 2c:36:f8:fa:ec:00 (try 1/3)
  [ 512.449561] wlp0s20f3: authenticated
  [ 512.450625] wlp0s20f3: associate with 2c:36:f8:fa:ec:00 (try 1/3)
  [ 512.452010] wlp0s20f3: RX AssocResp from 2c:36:f8:fa:ec:00
  (capab=0x111 status=0 aid=8)
  [ 512.454501] wlp0s20f3: associated
  [ 512.542439] wlp0s20f3: Limiting TX power to 27 (30 - 3) dBm as
  advertised by 2c:36:f8:fa:ec:00
  [ 557.685247] wlp0s20f3: deauthenticating from 2c:36:f8:fa:ec:00 by
  local choice (Reason: 3=DEAUTH_LEAVING)
  [ 557.695875] wlp0s20f3: failed to remove key (1, ff:ff:ff:ff:ff:ff)
  from hardware (-22)

  1. c4276b6 (tag: refs/tags/iwlwifi-fw-2017-11-03) iwlwifi: add
  firmware version 33 for new 9000 series

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

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


[Kernel-packages] [Bug 1738911] Re: Support realtek new codec alc257 in the alsa hda driver

2018-01-12 Thread Kleber Sacilotto de Souza
** Changed in: linux-oem (Ubuntu Xenial)
   Status: New => Fix Committed

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

Title:
  Support realtek new codec alc257 in the alsa hda driver

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in linux-oem package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Invalid
Status in linux-oem source package in Xenial:
  Fix Committed

Bug description:
  Otherwise, the kernel will load generic codec driver, this will
  introduce lots of problem like mute/micmute hotkey can't work.

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

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


[Kernel-packages] [Bug 1742721] Re: linux-image-4.13.0-26-generic / linux-image-extra-4.13.0-26-generic fail to boot

2018-01-12 Thread Dawei wang
My kernel version is linux-image-4.13.0-26-generic, reboot to old kernel
linux-headers-4.10.0-42-generic works.

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

Title:
  linux-image-4.13.0-26-generic / linux-image-extra-4.13.0-26-generic
  fail to boot

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

Bug description:
  I've updated the machine to the linux-hwe kernels, and experienced an
  almost instant crash when booting.  Nothing is shown on the VGA
  output, so no stack traces are available.

  I've tried booting a few kernels with the following results:

  - linux-image-4.8.0-56-generic + linux-image-extra-4.8.0-56-generic: boots up 
fine
  - linux-image-4.13.0-26-generic + linux-image-extra-4.13.0-26-generic:  fails 
to boot
  - linux-image-4.13.0-21-generic: boots up, but since no r8169, no networking
  - linux-image-4.13.0-21-generic + linux-image-extra-4.13.0-21-generic:  fails 
to boot
  - linux-image-4.10.0-42-generic + linux-image-extra-4.10.0-42-generic:  boots 
up fine

  After that I've tried some mainline kernels from
  http://kernel.ubuntu.com/~kernel-ppa/mainline to check if the problem
  is the upstream or ubuntu patches:

  - linux-image-4.14.13-041413-generic_4.14.13-041413.201801101001_amd64.deb: 
boots up fine
  - linux-image-4.13.13-041313-generic_4.13.13-041313.201711150531_amd64.deb: 
fails to boot
  - linux-image-4.13.16-041316-generic_4.13.16-041316.201711240901_amd64.deb: 
boots up fine
  - linux-image-4.13.14-041314-generic_4.13.14-041314.201711180632_amd64.deb: 
fails to boot
  - linux-image-4.13.15-041315-generic_4.13.15-041315.201711211030_amd64.deb: 
boots up fine

  So, it seems, the problem is fixed either in patches between 4.13.14
  and 4.13.15 upstream, or ubuntu configs/patches applied to mainline
  kernels.

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

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


[Kernel-packages] [Bug 1734147] Re: corrupted BIOS due to Intel SPI bug in kernel

2018-01-12 Thread Danny
hi.
i don't know if this question has been answered but here it goes.
my laptop suffers with the intel-spi problem cant save bios settings, cant boot 
by any form.
at the time i only could boot to ubuntu (i had dual boot with win10) and i used 
one key recovery and i recovered windows but made boot impossible to ubuntu 
cause it erased grub so i deleted ubuntu partition. one day i wanted to install 
again ubuntu and i couldnt it was when i noticed that i couldnt made any 
changes in bios.
so please help me how can i fix this issue from windows? lenovo didnt put 
another bios update on their website.my computer is Lenovo IdeaPad G50-80

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

Title:
  corrupted BIOS due to Intel SPI bug in kernel

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Fix Released
Status in linux-hwe-edge source package in Xenial:
  Fix Released
Status in linux-oem source package in Xenial:
  Fix Released
Status in linux source package in Artful:
  Fix Released

Bug description:
  An update to linux kernel on Ubuntu 17.10 that enabled the Intel SPI
  drivers results in a serial flash that is read only in Intel Broadwell
  and Haswell machines with serial flashes with SPI_NOR_HAS_LOCK set.

  Symptoms:
   * BIOS settings cannot be saved
   * USB Boot impossible
   * EFI entries read-only.

  ---

  Fix: The issue was fixed in kernel version 4.13.0-21 by configuring
  the kernel so it is not compiled with Intel SPI support. But previous
  affected machines still suffered from a broken BIOS.

  Repair: If you still can boot into Ubuntu, you can recover your BIOS
  with the following steps:

  1. Boot into Ubuntu
  2. Download 
http://people.canonical.com/~ypwong/lp1734147/linux-image-4.15.0-041500rc6-generic_4.15.0-041500rc6.201712312330+20170103+1_amd64.deb
  3. Install the downloaded package:
    $ sudo dpkg -i 
linux-image-4.15.0-041500rc6-generic_4.15.0-041500rc6.201712312330+20170103+1_amd64.deb
  4. Make sure the kernel is installed without any error. Once installed, 
reboot.
  5. At grub, choose the newly installed kernel. You can choose the "recovery" 
mode.
  6. Reboot and go to BIOS settings to confirm your BIOS has been recovered.
  7. In case your BIOS is not recovered, reboot to the new kernel, then reboot 
*once again* to the new kernel, do not enter BIOS settings before the reboot. 
After the second reboot, check BIOS.
  8. If your BIOS issue remains, download another kernel from 
http://people.canonical.com/~ypwong/lp1734147/linux-image-4.15.0-041500rc6-generic_4.15.0-041500rc6.201712312330+clear+debug_amd64.deb,
 and use dpkg to install it, then repeat steps 4 to 6.

  After your BIOS is fixed, the kernel packages you just installed are
  no longer needed, you can remove it by running 'sudo dpkg -r linux-
  image-4.15.0-041500rc6-generic'.

  The patch used to build the linux v4.15 kernel in step 8 can be found
  at https://goo.gl/xUKJFR.

  ---

  Test Case: Fix has been verified by our HWE team on affected hardware.

  Regression Potential: Minimal, it's unlikely anyone is actually doing
  anything which requires this driver.

  ---

  Affected Machines:

  Lenovo B40-70
  Lenovo B50-70
  Lenovo B50-80
  Lenovo Flex-3
  Lenovo Flex-10
  Lenovo G40-30
  Lenovo G50-30
  Lenovo G50-70
  Lenovo G50-80
  Lenovo S20-30
  Lenovo U31-70
  Lenovo Y50-70
  Lenovo Y70-70
  Lenovo Yoga Thinkpad (20C0)
  Lenovo Yoga 2 11" - 20332
  Lenovo Yoga 3 11"
  Lenovo Z50-70
  Lenovo Z51-70
  Lenovo ideapad 100-15IBY

  Acer Aspire E5-771G
  Acer Aspire ES1-111M-C1LE (fixed following your new instruction (thank you))
  Acer TravelMate B113
  Acer Swift SF314-52 (Fixed by 4.14.9)
  Toshiba Satellite S55T-B5233
  Toshiba Satellite L50-B-1R7
  Toshiba Satellite S50-B-13G
  Dell Inspiron 15-3531
  Mediacom Smartbook 14 Ultra M-SB14UC
  Acer Aspire E3-111-C0UM
  HP 14-r012la

  ---

  Affected serial flash devices by manufacturer part number, JEDEC ID 
(SPI_NOR_HAS_LOCK set in drivers/mtd/spi-nor/spi-nor.c)
  /* ESMT */
     f25l32pa, 0x8c2016
     f25l32qa, 0x8c4116
     f25l64qa, 0x8c4117
  /* GigaDevice */
     gd25q16, 0xc84015
     gd25q32, 0xc84016
     gd25lq32, 0xc86016
     gd25q64, 0xc84017
     gd25lq64c, 0xc86017
     gd25q128, 0xc84018
     gd25q256, 0xc84019
  /* Winbond */
     w25q16dw, 0xef6015
     w25q32dw, 0xef6016
     w25q64dw, 0xef6017
     w25q128fw, 0xef6018

  ---

  Original Description:

  Basically on Lenovo Y50-70 after installing Ubuntu 17.10, many users
  reported a corrupted BIOS.

  It's not possible to save new settings in BIOS anymore and after
  rebooting, the system starts with the old settings.

  Moreover (and most important) USB booting is not possible anymore
  since USB is not recognized. It's very serious, since our machines do
  not have a CDROM.

  Lenovo forums at the moment are full of topics regading this issue.

  Thank 

[Kernel-packages] [Bug 1742721] Re: linux-image-4.13.0-26-generic / linux-image-extra-4.13.0-26-generic fail to boot

2018-01-12 Thread Dawei wang
I got similar issue, the kernel encountered NULL dereference to null
error.

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

Title:
  linux-image-4.13.0-26-generic / linux-image-extra-4.13.0-26-generic
  fail to boot

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

Bug description:
  I've updated the machine to the linux-hwe kernels, and experienced an
  almost instant crash when booting.  Nothing is shown on the VGA
  output, so no stack traces are available.

  I've tried booting a few kernels with the following results:

  - linux-image-4.8.0-56-generic + linux-image-extra-4.8.0-56-generic: boots up 
fine
  - linux-image-4.13.0-26-generic + linux-image-extra-4.13.0-26-generic:  fails 
to boot
  - linux-image-4.13.0-21-generic: boots up, but since no r8169, no networking
  - linux-image-4.13.0-21-generic + linux-image-extra-4.13.0-21-generic:  fails 
to boot
  - linux-image-4.10.0-42-generic + linux-image-extra-4.10.0-42-generic:  boots 
up fine

  After that I've tried some mainline kernels from
  http://kernel.ubuntu.com/~kernel-ppa/mainline to check if the problem
  is the upstream or ubuntu patches:

  - linux-image-4.14.13-041413-generic_4.14.13-041413.201801101001_amd64.deb: 
boots up fine
  - linux-image-4.13.13-041313-generic_4.13.13-041313.201711150531_amd64.deb: 
fails to boot
  - linux-image-4.13.16-041316-generic_4.13.16-041316.201711240901_amd64.deb: 
boots up fine
  - linux-image-4.13.14-041314-generic_4.13.14-041314.201711180632_amd64.deb: 
fails to boot
  - linux-image-4.13.15-041315-generic_4.13.15-041315.201711211030_amd64.deb: 
boots up fine

  So, it seems, the problem is fixed either in patches between 4.13.14
  and 4.13.15 upstream, or ubuntu configs/patches applied to mainline
  kernels.

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

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


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

2018-01-12 Thread bugproxy
--- Comment From frede...@fr.ibm.com 2018-01-12 08:59 EDT---
Hi,

Aneesh, right, I missed the 2 other ones. I rebuilt a kernel with the 3 
patches, thanks for having thought of this, because that fixes the issue. Some 
details now :
actually this issue happens only when disabling RPT ("disable_radix") which is 
not the default in Artful.
Also I could have it on Witherspoon systems but not on Boston (having an other 
issue, which may hide this one... FYI the kernel loops infinitly displaying :
[0.00]   Allocated bitmap for 2040 MSIs (base IRQ 0x1fd000)
[0.00] Initializing IODA2 PHB (/pciex@620c3c030)
[0.00] PCI host bridge /pciex@620c3c030  ranges:
[0.[   89.349426896,3] opalmsg: No available node in the free list, 
allocating
[   89.352371632,3] opalmsg: No available node in the free list, allocating
00]  M[   89.355953552,3] opalmsg: No available node in the free list, 
allocating
[   89.359518752,3] opalmsg: No available node in the free list, allocating
[   89.363009568,3] opalmsg: No available node in the free list, allocating
[   89.366608224,3] opalmsg: No available node in the free list, allocating
[   89.370155632,3] opalmsg: No available node in the free list, allocating
[   89.373689632,3] opalmsg: No available node in the free list, allocating
[   89.376579088,3] opalmsg: No available node in the free list, allocating
[   89.380134464,3] opalmsg: No available node in the free list, allocating
[   89.383665744,3] opalmsg: No available node in the free list, allocating
[   89.387155088,3] opalmsg: No available node in the free list, allocating
[   89.390741040,3] opalmsg: No available node in the free list, allocating
[   89.393600592,3] opalmsg: No available node in the free list, allocating
[   89.397146720,3] opalmsg: No available node in the free list, allocating
[   89.400687600,3] opalmsg: No available node in the free list, allocating
[   89.404226032,3] opalmsg: No available node in the free list, allocating
[   89.407772816,3] opalmsg: No available node in the free list, allocating
[   89.410644096,3] opalmsg: No available node in the free list, allocating

).

So it seems those commits help :
---
commit 21a0e8c14bf61472723d2acc83f98ab35ff321b4
Author: Michael Ellerman 
Date:   Tue Aug 1 20:29:24 2017 +1000

powerpc/mm/hash64: Make vmalloc 56T on hash

commit b5048de04b32104140e5b251005404c3e0d03ccd
Author: Michael Ellerman 
Date:   Tue Aug 1 20:29:23 2017 +1000

powerpc/mm/slb: Move comment next to the code it's referring to

commit 63ee9b2ff9d306efaa61b04b8710fafe339ae441
Author: Michael Ellerman 
Date:   Tue Aug 1 20:29:22 2017 +1000

powerpc/mm/book3s64: Make KERN_IO_START a variable

---

F.

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

Title:
  Ubuntu 17.10 crashes on vmalloc.c

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

Bug description:
  == Comment: #0 - Breno Leitao - 2017-12-19 09:48:10 ==
  When running Ubuntu 17.10 on POWER9, I got the following error:

  [409038.118908] WARNING: CPU: 47 PID: 294 at 
/build/linux-LIHoWc/linux-4.13.0/mm/vmalloc.c:2527 pcpu_get_vm_areas+0x62c/0x660
  [409038.118909] 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 libcrc32c ipt_REJECT nf_reject_ipv4 
xt_tcpudp bridge stp llc ebtable_filter ebtables ip6table_filter ip6_tables 
iptable_filter kvm_hv kvm at24 ofpart ipmi_powernv ipmi_devintf ipmi_msghandler 
cmdlinepart powernv_flash uio_pdrv_genirq uio mtd vmx_crypto ibmpowernv 
crct10dif_vpmsum opal_prd binfmt_misc ip_tables x_tables autofs4 crc32c_vpmsum 
ast i2c_algo_bit drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops 
ttm drm tg3 ahci libahci
  [409038.118933] CPU: 47 PID: 294 Comm: kworker/47:0 Tainted: GW   
4.13.0-12-generic #13-Ubuntu
  [409038.118934] Workqueue: events pcpu_balance_workfn
  [409038.118936] task: c03fe3cdcc00 task.stack: c03fe3be
  [409038.118937] NIP: c032c1fc LR: c02f5fd4 CTR: 

  [409038.118937] REGS: c03fe3be3810 TRAP: 0700   Tainted: GW   
 (4.13.0-12-generic)
  [409038.118938] MSR: 9282b033 
  [409038.118944]   CR: 24024828  XER: 2004
  [409038.118944] CFAR: c032bdb8 SOFTE: 1
  GPR00: 2df0 c03fe3be3a90 c15e3000 
c000203fff6b6880
  GPR04: c000203fff223608 0008 c000203fff6b6888 

  GPR08: 2df0 0800 0160 
c000203fff6b6888
  GPR12: 0002 cfaded80 c0f6c050 
c03fe3be3bc0
   

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

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

apport-collect 1742953

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

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

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

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

** Tags added: artful

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

Title:
  When starting Virtualbox system freeze

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Still new to linux and not good in English...

  After installing the new kernel 4.10.0-42 ---> 4.13.0-26
  When I try to start VirtualBox the system freezes.
  It was working fine (everything was working fine for the last 6 months) until 
this update.
  So my guest is this kernel...

  Other than this I have no problem.

  Thank you for all the work you have been done.

  
  ubuntu-bug linux

  won't work so I am putting this sumary from hardinfo

  Computer
  Processor 4x Intel(R) Core(TM) i3-3120M CPU @ 2.50GHz
  Memory5983MB (2932MB used)
  Operating System  Linux Mint 18.3 Sylvia
  Date/Time Fri 12 Jan 2018 11:07:41 PM JST
  Display
  Resolution2646x1024 pixels
  OpenGL Renderer   Mesa DRI Intel(R) Ivybridge Mobile
  X11 VendorThe X.Org Foundation
  Multimedia
  Audio Adapter HDA-Intel - HDA Intel PCH
  Audio Adapter USB-Audio - USB Audio
  Input Devices
  Power Button  
  Lid Switch
  Power Button  
  AT Translated Set 2 keyboard  
  Video Bus 
  AlpsPS/2 ALPS GlidePoint  
  Logitech USB Receiver 
  Logitech USB Receiver 
  Extended USB Keypad   
  Extended USB Keypad   
  HDA Intel PCH Mic 
  HDA Intel PCH Headphone   
  Printers (CUPS)
  MFCJ860DN 
  SCSI Disks
  ATA WDC WD3200BPVT-2  
  MATSHITA DVD-ROM UJ8A0AC  
  SanDisk Cruzer Fit
  Operating System
  Version
  KernelLinux 4.13.0-26-generic (x86_64)
  Compiled  #29~16.04.2-Ubuntu SMP Tue Jan 9 22:00:44 UTC 2018
  C Library Unknown
  Default C CompilerGNU C Compiler version 5.4.0 20160609 (Ubuntu 
5.4.0-6ubuntu1~16.04.5)
  Distribution  Linux Mint 18.3 Sylvia
  Current Session
  Computer Name k-PC-VK25LAZCG
  Desktop Environment   XFCE 4
  Misc
  Uptime3 hours, 1 minute
  Load Average  1.83, 1.17, 1.07
  Kernel Modules
  Loaded Modules
  pci_stub  
  vboxpci   Oracle VM VirtualBox PCI access Driver
  vboxnetadpOracle VM VirtualBox Network Adapter Driver
  vboxnetfltOracle VM VirtualBox Network Filter Driver
  vboxdrv   Oracle VM VirtualBox Support Driver
  intel_raplDriver for Intel RAPL (Running Average Power Limit)
  x86_pkg_temp_thermal  X86 PKG TEMP Thermal Driver
  intel_powerclamp  Package Level C-state Idle Injection for Intel CPUs
  snd_hda_codec_realtek Realtek HD-audio codec
  snd_hda_codec_generic Generic HD-audio codec parser
  coretemp  Intel Core temperature monitor
  ip6t_REJECT   Xtables: packet "rejection" target for IPv6
  nf_reject_ipv6
  snd_hda_intel Intel HDA driver
  nf_log_ipv6   Netfilter IPv6 packet logging
  snd_hda_codec HDA codec core
  snd_usb_audio USB Audio
  snd_hda_core  HD-audio bus
  kvm_intel 
  kvm   
  snd_usbmidi_lib   USB Audio/MIDI helper module
  snd_hwdep Hardware dependent layer
  irqbypass IRQ bypass manager utility module
  snd_seq_midi  Advanced Linux Sound Architecture sequencer MIDI synth.
  crct10dif_pclmul  T10 DIF CRC calculation accelerated with PCLMULQDQ.
  snd_seq_midi_eventMIDI byte <-> sequencer event coder
  crc32_pclmul  
  snd_rawmidi   Midlevel RawMidi code for ALSA.
  snd_pcm   Midlevel PCM code for ALSA.
  snd_seq   Advanced Linux Sound Architecture sequencer.
  arc4  ARC4 Cipher Algorithm
  xt_hl Xtables: Hoplimit/TTL field match
  ghash_clmulni_intel   GHASH Message Digest Algorithm, acclerated by 
PCLMULQDQ-NI
  snd_seq_deviceALSA sequencer device management
  ip6t_rt   Xtables: IPv6 Routing Header match
  iwldvmIntel(R) Wireless WiFi Link AGN driver for Linux
  mac80211  IEEE 802.11 subsystem
  iwlwifi   Intel(R) Wireless WiFi driver for Linux
  snd_timer ALSA timer interface
  nf_conntrack_ipv6 
  cryptdSoftware async crypto daemon
  nf_defrag_ipv6
  pcmciaPCMCIA Driver Services
  snd   Advanced Linux Sound Architecture driver for soundcards.
  intel_cstate  
  ipt_REJECTXtables: packet "rejection" target for IPv4
  intel_rapl_perf   
  nf_reject_ipv4
  joydevJoystick device interfaces
  input_ledsInput -> LEDs Bridge
  serio_raw 

[Kernel-packages] [Bug 1742953] [NEW] When starting Virtualbox system freeze

2018-01-12 Thread kek
Public bug reported:

Still new to linux and not good in English...

After installing the new kernel 4.10.0-42 ---> 4.13.0-26
When I try to start VirtualBox the system freezes.
It was working fine (everything was working fine for the last 6 months) until 
this update.
So my guest is this kernel...

Other than this I have no problem.

Thank you for all the work you have been done.


ubuntu-bug linux

won't work so I am putting this sumary from hardinfo

Computer
Processor   4x Intel(R) Core(TM) i3-3120M CPU @ 2.50GHz
Memory  5983MB (2932MB used)
Operating SystemLinux Mint 18.3 Sylvia
Date/Time   Fri 12 Jan 2018 11:07:41 PM JST
Display
Resolution  2646x1024 pixels
OpenGL Renderer Mesa DRI Intel(R) Ivybridge Mobile
X11 Vendor  The X.Org Foundation
Multimedia
Audio Adapter   HDA-Intel - HDA Intel PCH
Audio Adapter   USB-Audio - USB Audio
Input Devices
Power Button
Lid Switch  
Power Button
AT Translated Set 2 keyboard
Video Bus   
AlpsPS/2 ALPS GlidePoint
Logitech USB Receiver   
Logitech USB Receiver   
Extended USB Keypad 
Extended USB Keypad 
HDA Intel PCH Mic   
HDA Intel PCH Headphone 
Printers (CUPS)
MFCJ860DN   
SCSI Disks
ATA WDC WD3200BPVT-2
MATSHITA DVD-ROM UJ8A0AC
SanDisk Cruzer Fit  
Operating System
Version
Kernel  Linux 4.13.0-26-generic (x86_64)
Compiled#29~16.04.2-Ubuntu SMP Tue Jan 9 22:00:44 UTC 2018
C Library   Unknown
Default C Compiler  GNU C Compiler version 5.4.0 20160609 (Ubuntu 
5.4.0-6ubuntu1~16.04.5)
DistributionLinux Mint 18.3 Sylvia
Current Session
Computer Name   k-PC-VK25LAZCG
Desktop Environment XFCE 4
Misc
Uptime  3 hours, 1 minute
Load Average1.83, 1.17, 1.07
Kernel Modules
Loaded Modules
pci_stub
vboxpci Oracle VM VirtualBox PCI access Driver
vboxnetadp  Oracle VM VirtualBox Network Adapter Driver
vboxnetflt  Oracle VM VirtualBox Network Filter Driver
vboxdrv Oracle VM VirtualBox Support Driver
intel_rapl  Driver for Intel RAPL (Running Average Power Limit)
x86_pkg_temp_thermalX86 PKG TEMP Thermal Driver
intel_powerclampPackage Level C-state Idle Injection for Intel CPUs
snd_hda_codec_realtek   Realtek HD-audio codec
snd_hda_codec_generic   Generic HD-audio codec parser
coretempIntel Core temperature monitor
ip6t_REJECT Xtables: packet "rejection" target for IPv6
nf_reject_ipv6  
snd_hda_intel   Intel HDA driver
nf_log_ipv6 Netfilter IPv6 packet logging
snd_hda_codec   HDA codec core
snd_usb_audio   USB Audio
snd_hda_coreHD-audio bus
kvm_intel   
kvm 
snd_usbmidi_lib USB Audio/MIDI helper module
snd_hwdep   Hardware dependent layer
irqbypass   IRQ bypass manager utility module
snd_seq_midiAdvanced Linux Sound Architecture sequencer MIDI synth.
crct10dif_pclmulT10 DIF CRC calculation accelerated with PCLMULQDQ.
snd_seq_midi_event  MIDI byte <-> sequencer event coder
crc32_pclmul
snd_rawmidi Midlevel RawMidi code for ALSA.
snd_pcm Midlevel PCM code for ALSA.
snd_seq Advanced Linux Sound Architecture sequencer.
arc4ARC4 Cipher Algorithm
xt_hl   Xtables: Hoplimit/TTL field match
ghash_clmulni_intel GHASH Message Digest Algorithm, acclerated by 
PCLMULQDQ-NI
snd_seq_device  ALSA sequencer device management
ip6t_rt Xtables: IPv6 Routing Header match
iwldvm  Intel(R) Wireless WiFi Link AGN driver for Linux
mac80211IEEE 802.11 subsystem
iwlwifi Intel(R) Wireless WiFi driver for Linux
snd_timer   ALSA timer interface
nf_conntrack_ipv6   
cryptd  Software async crypto daemon
nf_defrag_ipv6  
pcmcia  PCMCIA Driver Services
snd Advanced Linux Sound Architecture driver for soundcards.
intel_cstate
ipt_REJECT  Xtables: packet "rejection" target for IPv4
intel_rapl_perf 
nf_reject_ipv4  
joydev  Joystick device interfaces
input_leds  Input -> LEDs Bridge
serio_raw   Raw serio driver
soundcore   Core sound module
cfg80211wireless configuration support
nf_log_ipv4 Netfilter IPv4 packet logging
shpchp  Standard Hot Plug PCI Controller Driver
yenta_socket
mei_me  Intel(R) Management Engine Interface
nf_log_common   
binfmt_misc 
mac_hid 
pcmcia_rsrc 
pcmcia_core Linux Kernel Card Services
xt_LOG  Xtables: IPv4/IPv6 packet logging
mei Intel(R) Management Engine Interface
lpc_ich LPC interface for Intel ICH
xt_limitXtables: rate-limit match
xt_tcpudp   Xtables: TCP, UDP and UDP-Lite match
xt_addrtype Xtables: address type match
nf_conntrack_ipv4   
nf_defrag_ipv4  
xt_conntrackXtables: connection tracking state match
ip6table_filter ip6tables filter table
ip6_tables  IPv6 packet filter
nf_conntrack_netbios_ns NetBIOS name service broadcast connection tracking 
helper
nf_conntrack_broadcast  
nf_nat_ftp  ftp NAT helper
nf_nat  
parport_pc  PC-style parallel port driver
nf_conntrack_ftpftp connection tracking helper
nf_conntrack
libcrc32c   CRC32c (Castagnoli) 

[Kernel-packages] [Bug 1607325] Re: Ubuntu 16.04 running on z13 hardware is unable to configure blue ridge

2018-01-12 Thread Frank Heimes
got fixed with an updated release

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

** Changed in: ubuntu-z-systems
   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/1607325

Title:
  Ubuntu 16.04 running on z13 hardware is unable to configure blue ridge

Status in Ubuntu on IBM z Systems:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released

Bug description:
  Problem Description
  ===
  system Z Ubuntu 16.04 LTS can not correctly configured DS8870 2107 LUNs.
   
  ---uname output---
  Linux ilabg3 4.4.0-33-generic #52-Ubuntu SMP Fri Jul 22 19:17:00 UTC 2016 
s390x s390x s390x GNU/Linux
   
  ---Additional Hardware Info---
  Z13 system using 16G FCP adapters to attach to FC fabric and IBM Blue ridge

   Machine Type = Z13 S390

  Steps to Reproduce
  
  The initial kernel is 4.4.0-24-generic and all blue ridge devices can be 
configured normally.
  After we upgrade kernel to 4.4.0-33 and reload BR code all BR devices can not 
be detect.

  System log show:
  [ 2645.893763] scsi 0:0:7:0: RAID  IBM  2810XIV-LUN-0 
PQ: 0 ANSI: 5
  [ 2645.895269] sysfs: cannot create duplicate filename 
'/bus/scsi/devices/0:0:7:0'
  [ 2645.895310] [ cut here ]
  [ 2645.895311] WARNING: at /build/linux-o03cxz/linux-4.4.0/fs/sysfs/dir.c:31
  [ 2645.895312] Modules linked in: rpcsec_gss_krb5 auth_rpcgss nfsv4 nfs lockd 
grace fscache qeth_l3 qeth ccwgroup vmur ib_iser rdma_cm iw_cm ib_cm ib_sa 
ib_mad ib_core sunrpc ib_addr iscsi_tcp libiscsi_tcp libiscsi 
scsi_transport_iscsi btrfs zlib_deflate raid10 raid456 async_memcpy 
async_raid6_recov async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 
raid0 linear dm_round_robin ghash_s390 prng aes_s390 des_s390 des_generic 
sha512_s390 sha256_s390 sha1_s390 sha_common zfcp dasd_eckd_mod qdio 
scsi_transport_fc dasd_fba_mod dasd_mod scsi_dh_emc scsi_dh_rdac scsi_dh_alua 
dm_multipath
  [ 2645.895338] CPU: 1 PID: 4008 Comm: sh Tainted: GW   
4.4.0-33-generic #52-Ubuntu
  [ 2645.895339] task: dfe436b0 ti: 7b97c000 task.ti: 
7b97c000
  [ 2645.895340] Krnl PSW : 0704d0018000 003a361c 
(sysfs_warn_dup+0x7c/0x98)
  [ 2645.895350]R:0 T:1 IO:1 EX:1 Key:0 M:1 W:0 P:0 AS:3 CC:1 PM:0 
EA:3
 Krnl GPRS: 00cf7039 00cd9f3c 0043 
ef4d18a0
  [ 2645.895351]003a3618  7a49a000 
707b9178
  [ 2645.895352]00c1d0e0 ee71a780 0001 
ee71a780
  [ 2645.895353]e9554b60 7ebdf000 003a3618 
7b97f9b8
  [ 2645.895361] Krnl Code: 003a360c: c020002f33e7  larl
%r2,989dda
003a3612: c0e5fff6befb  brasl   
%r14,27b408
   #003a3618: a7f40001  brc 
15,3a361a
   >003a361c: b904002d  lgr %r2,%r13
003a3620: ebbff0a4  lmg 
%r11,%r15,160(%r15)
003a3626: c0f4fffa5995  brcl
15,2ee950
003a362c: a739  lghi%r3,0
003a3630: a7f4ffec  brc 
15,3a3608
  [ 2645.895370] Call Trace:
  [ 2645.895372] ([<003a3618>] sysfs_warn_dup+0x78/0x98)
  [ 2645.895374]  [<003a3b30>] sysfs_do_create_link_sd.isra.0+0xf8/0x108
  [ 2645.895378]  [<005c4044>] bus_add_device+0x13c/0x230
  [ 2645.895379]  [<005c1758>] device_add+0x398/0x680
  [ 2645.895385]  [<005f7a34>] scsi_sysfs_add_sdev+0xcc/0x2a8
  [ 2645.895386]  [<005f4210>] scsi_probe_and_add_lun+0xcc0/0xe18
  [ 2645.895387]  [<005f4c5a>] __scsi_scan_target+0xba/0x268
  [ 2645.895389]  [<005f4f0a>] scsi_scan_target+0x102/0x120
  [ 2645.895401]  [<03ff801095f6>] zfcp_unit_scsi_scan+0x7e/0x90 [zfcp]
  [ 2645.895404]  [<03ff80109948>] zfcp_unit_add+0x168/0x1f0 [zfcp]
  [ 2645.895407]  [<03ff80108564>] zfcp_sysfs_unit_add_store+0x54/0x70 
[zfcp]
  [ 2645.895408]  [<003a1d9a>] kernfs_fop_write+0x13a/0x190
  [ 2645.895413]  [<0030fcac>] vfs_write+0x94/0x1a0
  [ 2645.895414]  [<003109be>] SyS_write+0x66/0xd8
  [ 2645.895417]  [<007b86c6>] system_call+0xd6/0x264
  [ 2645.895418]  [<03ffb10df6e8>] 0x3ffb10df6e8
  [ 2645.895419] Last Breaking-Event-Address:
  [ 2645.895420]  [<003a3618>] sysfs_warn_dup+0x78/0x98
  [ 2645.895421] ---[ end trace a9b757385c995a64 ]---
  [ 2645.895535] scsi 0:0:7:0: failed to add device: -17

  == Comment: #1 - XIANG ZHANG  - 2016-07-26 02:34:39 ==
  I know the Bug 139096, not sure the 

[Kernel-packages] [Bug 1739341] Re: unshare test in ubuntu_stress_smoke_test cause OOM on Ubuntu on LPAR (Xenial)

2018-01-12 Thread Colin Ian King
** Changed in: linux (Ubuntu)
   Status: In Progress => Fix Released

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

Title:
  unshare test in ubuntu_stress_smoke_test cause OOM on Ubuntu on LPAR
  (Xenial)

Status in linux package in Ubuntu:
  Fix Released

Bug description:
  Output from jenkins:
  22:22:50 DEBUG| [stdout] udp RETURNED 0
  22:22:50 DEBUG| [stdout] udp PASSED
  22:22:50 DEBUG| [stdout] udp-flood STARTING
  22:22:55 DEBUG| [stdout] udp-flood RETURNED 0
  22:22:55 DEBUG| [stdout] udp-flood PASSED
  22:22:55 DEBUG| [stdout] unshare STARTING
  Connection to s2lp3 closed by remote host.

  This test will cause OOM on this node. The job will be killed and I
  will need to reset the system via IBM HMC.

  Re-tested and it's reproducible (2 out of 2)

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-105-generic 4.4.0-105.128
  ProcVersionSignature: Ubuntu 4.4.0-105.128-generic 4.4.98
  Uname: Linux 4.4.0-105-generic s390x
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 
2: ls: cannot access '/dev/snd/': No such file or directory
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.1-0ubuntu2.14
  Architecture: s390x
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  Date: Tue Dec 19 22:09:03 2017
  HibernationDevice: RESUME=UUID=f578fa27-1d57-41c9-bb1d-7ff64c1c9345
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: Error: [Errno 2] No such file or directory: '/proc/fb'
  ProcKernelCmdLine: root=UUID=f26894a2-496d-4891-aa9a-f66344c9 
crashkernel=196M BOOT_IMAGE=0
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-105-generic N/A
   linux-backports-modules-4.4.0-105-generic  N/A
   linux-firmware 1.157.15
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Kernel-packages] [Bug 1742939] Re: MLX: Set network offload for ppc64el

2018-01-12 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)

** Tags added: triage-g

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

Title:
  MLX: Set network offload for ppc64el

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

Bug description:
  == Comment: #0 - Breno Leitao  - 2018-01-12 07:01:25 ==
  Hi Canonical,

  
  We've been looking at an adapter from Mellanox and we need to do some kernel 
config changes. 

  This adapter is essentially an ethernet adapter with accelerators ,
  capable of doing some interesting network offloads, such as offload of
  IPsec. There was some kernel support that went upstream fairly
  recently that is needed to support it.

   The kernel config options are:
   
  CONFIG_XFRM_OFFLOAD
  CONFIG_INET_ESP_OFFLOAD
  CONFIG_INET6_ESP_OFFLOAD
  CONFIG_MLX5_ACCEL
  CONFIG_MLX5_EN_IPSEC

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

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


[Kernel-packages] [Bug 1742934] Re: Double swapon message

2018-01-12 Thread Cristian Aravena Romero
** Bug watch added: Linux Kernel Bug Tracker #198459
   https://bugzilla.kernel.org/show_bug.cgi?id=198459

** Also affects: linux via
   https://bugzilla.kernel.org/show_bug.cgi?id=198459
   Importance: Unknown
   Status: Unknown

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

Title:
  Double swapon message

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hello,

  dmesg:
  [4.086945] swapon: swapfile has holes
  [5.507148] swapon: swapfile has holes

  Regards,
  --
  Cristian

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.13.0-25-generic 4.13.0-25.29
  ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
  Uname: Linux 4.13.0-25-generic x86_64
  ApportVersion: 2.20.8-0ubuntu6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   caravena   1664 F...m pulseaudio
   /dev/snd/controlC0:  caravena   1664 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jan 12 09:50:39 2018
  InstallationDate: Installed on 2017-10-13 (90 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.13.0-25-generic 
root=UUID=707d0f89-4b1d-4432-9d50-6058dc4c1ee9 ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-25-generic N/A
   linux-backports-modules-4.13.0-25-generic  N/A
   linux-firmware 1.170
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/15/2013
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: P14AAJ
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: SAMSUNG_NP1234567890
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: FAB1
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvrP14AAJ:bd04/15/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1:
  dmi.product.family: ChiefRiver System
  dmi.product.name: 530U3C/530U4C
  dmi.product.version: 0.1
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

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

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


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

2018-01-12 Thread bugproxy
--- Comment From heinz-werner_se...@de.ibm.com 2018-01-12 07:57 EDT---
IBM External Status-> closed, Verified

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

Title:
  Ubuntu 16.04 running on z13 hardware is unable to configure blue ridge

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

Bug description:
  Problem Description
  ===
  system Z Ubuntu 16.04 LTS can not correctly configured DS8870 2107 LUNs.
   
  ---uname output---
  Linux ilabg3 4.4.0-33-generic #52-Ubuntu SMP Fri Jul 22 19:17:00 UTC 2016 
s390x s390x s390x GNU/Linux
   
  ---Additional Hardware Info---
  Z13 system using 16G FCP adapters to attach to FC fabric and IBM Blue ridge

   Machine Type = Z13 S390

  Steps to Reproduce
  
  The initial kernel is 4.4.0-24-generic and all blue ridge devices can be 
configured normally.
  After we upgrade kernel to 4.4.0-33 and reload BR code all BR devices can not 
be detect.

  System log show:
  [ 2645.893763] scsi 0:0:7:0: RAID  IBM  2810XIV-LUN-0 
PQ: 0 ANSI: 5
  [ 2645.895269] sysfs: cannot create duplicate filename 
'/bus/scsi/devices/0:0:7:0'
  [ 2645.895310] [ cut here ]
  [ 2645.895311] WARNING: at /build/linux-o03cxz/linux-4.4.0/fs/sysfs/dir.c:31
  [ 2645.895312] Modules linked in: rpcsec_gss_krb5 auth_rpcgss nfsv4 nfs lockd 
grace fscache qeth_l3 qeth ccwgroup vmur ib_iser rdma_cm iw_cm ib_cm ib_sa 
ib_mad ib_core sunrpc ib_addr iscsi_tcp libiscsi_tcp libiscsi 
scsi_transport_iscsi btrfs zlib_deflate raid10 raid456 async_memcpy 
async_raid6_recov async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 
raid0 linear dm_round_robin ghash_s390 prng aes_s390 des_s390 des_generic 
sha512_s390 sha256_s390 sha1_s390 sha_common zfcp dasd_eckd_mod qdio 
scsi_transport_fc dasd_fba_mod dasd_mod scsi_dh_emc scsi_dh_rdac scsi_dh_alua 
dm_multipath
  [ 2645.895338] CPU: 1 PID: 4008 Comm: sh Tainted: GW   
4.4.0-33-generic #52-Ubuntu
  [ 2645.895339] task: dfe436b0 ti: 7b97c000 task.ti: 
7b97c000
  [ 2645.895340] Krnl PSW : 0704d0018000 003a361c 
(sysfs_warn_dup+0x7c/0x98)
  [ 2645.895350]R:0 T:1 IO:1 EX:1 Key:0 M:1 W:0 P:0 AS:3 CC:1 PM:0 
EA:3
 Krnl GPRS: 00cf7039 00cd9f3c 0043 
ef4d18a0
  [ 2645.895351]003a3618  7a49a000 
707b9178
  [ 2645.895352]00c1d0e0 ee71a780 0001 
ee71a780
  [ 2645.895353]e9554b60 7ebdf000 003a3618 
7b97f9b8
  [ 2645.895361] Krnl Code: 003a360c: c020002f33e7  larl
%r2,989dda
003a3612: c0e5fff6befb  brasl   
%r14,27b408
   #003a3618: a7f40001  brc 
15,3a361a
   >003a361c: b904002d  lgr %r2,%r13
003a3620: ebbff0a4  lmg 
%r11,%r15,160(%r15)
003a3626: c0f4fffa5995  brcl
15,2ee950
003a362c: a739  lghi%r3,0
003a3630: a7f4ffec  brc 
15,3a3608
  [ 2645.895370] Call Trace:
  [ 2645.895372] ([<003a3618>] sysfs_warn_dup+0x78/0x98)
  [ 2645.895374]  [<003a3b30>] sysfs_do_create_link_sd.isra.0+0xf8/0x108
  [ 2645.895378]  [<005c4044>] bus_add_device+0x13c/0x230
  [ 2645.895379]  [<005c1758>] device_add+0x398/0x680
  [ 2645.895385]  [<005f7a34>] scsi_sysfs_add_sdev+0xcc/0x2a8
  [ 2645.895386]  [<005f4210>] scsi_probe_and_add_lun+0xcc0/0xe18
  [ 2645.895387]  [<005f4c5a>] __scsi_scan_target+0xba/0x268
  [ 2645.895389]  [<005f4f0a>] scsi_scan_target+0x102/0x120
  [ 2645.895401]  [<03ff801095f6>] zfcp_unit_scsi_scan+0x7e/0x90 [zfcp]
  [ 2645.895404]  [<03ff80109948>] zfcp_unit_add+0x168/0x1f0 [zfcp]
  [ 2645.895407]  [<03ff80108564>] zfcp_sysfs_unit_add_store+0x54/0x70 
[zfcp]
  [ 2645.895408]  [<003a1d9a>] kernfs_fop_write+0x13a/0x190
  [ 2645.895413]  [<0030fcac>] vfs_write+0x94/0x1a0
  [ 2645.895414]  [<003109be>] SyS_write+0x66/0xd8
  [ 2645.895417]  [<007b86c6>] system_call+0xd6/0x264
  [ 2645.895418]  [<03ffb10df6e8>] 0x3ffb10df6e8
  [ 2645.895419] Last Breaking-Event-Address:
  [ 2645.895420]  [<003a3618>] sysfs_warn_dup+0x78/0x98
  [ 2645.895421] ---[ end trace a9b757385c995a64 ]---
  [ 2645.895535] scsi 0:0:7:0: failed to add device: -17

  == Comment: #1 - XIANG ZHANG  - 2016-07-26 02:34:39 ==
  I know the Bug 139096, not sure the same symptom

To manage notifications about this bug go to:

[Kernel-packages] [Bug 1742939] [NEW] MLX: Set network offload for ppc64el

2018-01-12 Thread bugproxy
Public bug reported:

== Comment: #0 - Breno Leitao  - 2018-01-12 07:01:25 ==
Hi Canonical,


We've been looking at an adapter from Mellanox and we need to do some kernel 
config changes. 

This adapter is essentially an ethernet adapter with accelerators ,
capable of doing some interesting network offloads, such as offload of
IPsec. There was some kernel support that went upstream fairly recently
that is needed to support it.

 The kernel config options are:
 
CONFIG_XFRM_OFFLOAD
CONFIG_INET_ESP_OFFLOAD
CONFIG_INET6_ESP_OFFLOAD
CONFIG_MLX5_ACCEL
CONFIG_MLX5_EN_IPSEC

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


** Tags: architecture-ppc64le bugnameltc-163544 severity-high 
targetmilestone-inin1804

** Tags added: architecture-ppc64le bugnameltc-163544 severity-high
targetmilestone-inin1804

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

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

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

Title:
  MLX: Set network offload for ppc64el

Status in linux package in Ubuntu:
  New

Bug description:
  == Comment: #0 - Breno Leitao  - 2018-01-12 07:01:25 ==
  Hi Canonical,

  
  We've been looking at an adapter from Mellanox and we need to do some kernel 
config changes. 

  This adapter is essentially an ethernet adapter with accelerators ,
  capable of doing some interesting network offloads, such as offload of
  IPsec. There was some kernel support that went upstream fairly
  recently that is needed to support it.

   The kernel config options are:
   
  CONFIG_XFRM_OFFLOAD
  CONFIG_INET_ESP_OFFLOAD
  CONFIG_INET6_ESP_OFFLOAD
  CONFIG_MLX5_ACCEL
  CONFIG_MLX5_EN_IPSEC

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

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


[Kernel-packages] [Bug 1742939] [NEW] MLX: Set network offload for ppc64el

2018-01-12 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

== Comment: #0 - Breno Leitao  - 2018-01-12 07:01:25 ==
Hi Canonical,


We've been looking at an adapter from Mellanox and we need to do some kernel 
config changes. 

This adapter is essentially an ethernet adapter with accelerators ,
capable of doing some interesting network offloads, such as offload of
IPsec. There was some kernel support that went upstream fairly recently
that is needed to support it.

 The kernel config options are:
 
CONFIG_XFRM_OFFLOAD
CONFIG_INET_ESP_OFFLOAD
CONFIG_INET6_ESP_OFFLOAD
CONFIG_MLX5_ACCEL
CONFIG_MLX5_EN_IPSEC

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


** Tags: architecture-ppc64le bugnameltc-163544 severity-high 
targetmilestone-inin1804
-- 
MLX: Set network offload for ppc64el
https://bugs.launchpad.net/bugs/1742939
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 1742753] Re: Error after shutdown and reboot

2018-01-12 Thread Joseph Salisbury
*** This bug is a duplicate of bug 1741934 ***
https://bugs.launchpad.net/bugs/1741934

** This bug has been marked a duplicate of bug 1741934
   Kernel trace with xenial 4.4  (4.4.0-108.131, Candidate kernels for PTI 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/1742753

Title:
  Error after shutdown and reboot

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Distributor ID:   Ubuntu
  Description:  Ubuntu 16.04.3 LTS
  Release:  16.04
  Codename: xenial
  4.4.0-108-generic
  Linux version 4.4.0-108-generic (buildd@lgw01-amd64-003) (gcc version 5.4.0 
20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.5) ) #131-Ubuntu SMP Sun Jan 7 14:34:49 
UTC 2018

  Jan 12 00:21:18 gerasimchuk-dv-m kernel: [   11.133795] [ cut 
here ]
  Jan 12 00:21:18 gerasimchuk-dv-m kernel: [   11.133809] kernel BUG at 
/build/linux-J4_1pC/linux-4.4.0/mm/slub.c:3627!
  Jan 12 00:21:18 gerasimchuk-dv-m kernel: [   11.133823] invalid opcode:  
[#1] SMP
  Jan 12 00:21:18 gerasimchuk-dv-m kernel: [   11.133833] Modules linked in: 
nvram msr 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 uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 videobuf2_core 
v4l2_common videodev media bnep btusb joydev btrtl hid_alps binfmt_misc arc4 
snd_hda_codec_hdmi(OE) i2c_designware_platform i2c_designware_core dell_wmi 
dell_led intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel 
kvm snd_hda_codec_realtek(OE) irqbypass snd_hda_codec_generic(OE) iwlmvm(OE) 
mac80211(OE) crct10dif_pclmul dell_rbtn crc32_pclmul ghash_clmulni_intel 
dell_laptop dcdbas aesni_intel dell_smm_hwmon aes_x86_64 lrw snd_hda_intel(OE) 
gf128mul iwlwifi(OE) snd_hda_codec(OE) glue_helper ablk_helper rtsx_pci_ms 
snd_hda_core(OE) cryptd snd_hwdep memstick cfg80211(OE) snd_pcm snd_seq_midi 
compat(OE) snd_seq_midi_event snd_rawmidi input_leds snd_seq serio_raw 
snd_seq_device snd_timer idma64 snd virt_dma soundcore mei_me shpchp mei 
intel_lpss_pci processor_thermal_device intel_soc_dts_iosf hci_uart btbcm btqca 
btintel bluetooth intel_lpss_acpi intel_lpss int3400_thermal acpi_thermal_rel 
dell_smo8800 int3403_thermal int340x_thermal_zone acpi_pad acpi_als 
intel_hid(OE) mac_hid kfifo_buf sparse_keymap industrialio parport_pc ppdev lp 
parport autofs4 btrfs xor raid6_pq hid_generic usbhid rtsx_pci_sdmmc i915_bpo 
intel_ips i2c_algo_bit drm_kms_helper syscopyarea e1000e(OE) ptp sysfillrect 
sysimgblt pps_core fb_sys_fops rtsx_pci ahci drm libahci wmi i2c_hid hid 
pinctrl_sunrisepoint video pinctrl_intel fjes
  Jan 12 00:21:18 gerasimchuk-dv-m kernel: [   11.134217] CPU: 3 PID: 21 Comm: 
watchdog/3 Tainted: G   OE   4.4.0-108-generic #131-Ubuntu
  Jan 12 00:21:18 gerasimchuk-dv-m kernel: [   11.134234] Hardware name: Dell 
Inc. Latitude 5580/0DTP1F, BIOS 1.5.3 08/07/2017
  Jan 12 00:21:18 gerasimchuk-dv-m kernel: [   11.134248] task: 
880224016900 ti: 8802240f4000 task.ti: 8802240f4000
  Jan 12 00:21:18 gerasimchuk-dv-m kernel: [   11.134262] RIP: 
0010:[]  [] kfree+0x147/0x150
  Jan 12 00:21:18 gerasimchuk-dv-m kernel: [   11.134279] RSP: 
0018:8802240f7d58  EFLAGS: 00010246
  Jan 12 00:21:18 gerasimchuk-dv-m kernel: [   11.134289] RAX: ea0008b90120 
RBX: 88022e404840 RCX: 88022e7f9220
  Jan 12 00:21:18 gerasimchuk-dv-m kernel: [   11.134302] RDX: ea0008900c20 
RSI: ea0008901020 RDI: ea0008b90100
  Jan 12 00:21:18 gerasimchuk-dv-m kernel: [   11.134315] RBP: 8802240f7d70 
R08: 0009 R09: ff80003f
  Jan 12 00:21:18 gerasimchuk-dv-m kernel: [   11.134329] R10: ea0008b90100 
R11: 0001 R12: 
  Jan 12 00:21:18 gerasimchuk-dv-m kernel: [   11.134342] R13: 810104ff 
R14: 81f3c840 R15: 
  Jan 12 00:21:18 gerasimchuk-dv-m kernel: [   11.134355] FS:  
() GS:88022e58() knlGS:
  Jan 12 00:21:18 gerasimchuk-dv-m kernel: [   11.134390] CS:  0010 DS:  
ES:  CR0: 80050033
  Jan 12 00:21:18 gerasimchuk-dv-m kernel: [   11.134402] CR2: 009c5ec8 
CR3: 01e0a000 CR4: 00360670
  Jan 12 00:21:18 gerasimchuk-dv-m kernel: [   11.134430] DR0:  
DR1:  DR2: 
  Jan 12 00:21:18 gerasimchuk-dv-m kernel: [   11.134455] DR3:  
DR6: fffe0ff0 DR7: 0400
  Jan 12 00:21:18 gerasimchuk-dv-m kernel: [   11.134468] Stack:
  Jan 12 00:21:18 gerasimchuk-dv-m kernel: [   11.134473]   
 d440 8802240f7da0
  Jan 12 00:21:18 gerasimchuk-dv-m kernel: [   11.134489]  810104ff 
0008 

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

2018-01-12 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/1742934

Title:
  Double swapon message

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hello,

  dmesg:
  [4.086945] swapon: swapfile has holes
  [5.507148] swapon: swapfile has holes

  Regards,
  --
  Cristian

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.13.0-25-generic 4.13.0-25.29
  ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
  Uname: Linux 4.13.0-25-generic x86_64
  ApportVersion: 2.20.8-0ubuntu6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   caravena   1664 F...m pulseaudio
   /dev/snd/controlC0:  caravena   1664 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jan 12 09:50:39 2018
  InstallationDate: Installed on 2017-10-13 (90 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.13.0-25-generic 
root=UUID=707d0f89-4b1d-4432-9d50-6058dc4c1ee9 ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-25-generic N/A
   linux-backports-modules-4.13.0-25-generic  N/A
   linux-firmware 1.170
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/15/2013
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: P14AAJ
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: SAMSUNG_NP1234567890
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: FAB1
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvrP14AAJ:bd04/15/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1:
  dmi.product.family: ChiefRiver System
  dmi.product.name: 530U3C/530U4C
  dmi.product.version: 0.1
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

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

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


[Kernel-packages] [Bug 1742934] [NEW] Double swapon message

2018-01-12 Thread Cristian Aravena Romero
Public bug reported:

Hello,

dmesg:
[4.086945] swapon: swapfile has holes
[5.507148] swapon: swapfile has holes

Regards,
--
Cristian

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-image-4.13.0-25-generic 4.13.0-25.29
ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
Uname: Linux 4.13.0-25-generic x86_64
ApportVersion: 2.20.8-0ubuntu6
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/pcmC0D0p:   caravena   1664 F...m pulseaudio
 /dev/snd/controlC0:  caravena   1664 F pulseaudio
CurrentDesktop: ubuntu:GNOME
Date: Fri Jan 12 09:50:39 2018
InstallationDate: Installed on 2017-10-13 (90 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.13.0-25-generic 
root=UUID=707d0f89-4b1d-4432-9d50-6058dc4c1ee9 ro rootflags=subvol=@ quiet 
splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-4.13.0-25-generic N/A
 linux-backports-modules-4.13.0-25-generic  N/A
 linux-firmware 1.170
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/15/2013
dmi.bios.vendor: Phoenix Technologies Ltd.
dmi.bios.version: P14AAJ
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: SAMSUNG_NP1234567890
dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.board.version: FAB1
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 9
dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.chassis.version: 0.1
dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvrP14AAJ:bd04/15/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1:
dmi.product.family: ChiefRiver System
dmi.product.name: 530U3C/530U4C
dmi.product.version: 0.1
dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

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


** Tags: amd64 apport-bug bionic

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

Title:
  Double swapon message

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hello,

  dmesg:
  [4.086945] swapon: swapfile has holes
  [5.507148] swapon: swapfile has holes

  Regards,
  --
  Cristian

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.13.0-25-generic 4.13.0-25.29
  ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
  Uname: Linux 4.13.0-25-generic x86_64
  ApportVersion: 2.20.8-0ubuntu6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   caravena   1664 F...m pulseaudio
   /dev/snd/controlC0:  caravena   1664 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jan 12 09:50:39 2018
  InstallationDate: Installed on 2017-10-13 (90 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.13.0-25-generic 
root=UUID=707d0f89-4b1d-4432-9d50-6058dc4c1ee9 ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-25-generic N/A
   linux-backports-modules-4.13.0-25-generic  N/A
   linux-firmware 1.170
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/15/2013
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: P14AAJ
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: SAMSUNG_NP1234567890
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: FAB1
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvrP14AAJ:bd04/15/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1:
  dmi.product.family: ChiefRiver System
  dmi.product.name: 530U3C/530U4C
  dmi.product.version: 0.1
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

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

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


[Kernel-packages] [Bug 1734147] Re: corrupted BIOS due to Intel SPI bug in kernel

2018-01-12 Thread Ads20000
Sorry if this question has already been dealt with (in which case, may
be nice to have it in the bug description) but has there been an update
released which automatically fixes the issue for people affected? I'm
sure there are many who wouldn't realize that their BIOS is broken for a
while (or have already realized) and then wouldn't know to come here to
find a 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/1734147

Title:
  corrupted BIOS due to Intel SPI bug in kernel

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Fix Released
Status in linux-hwe-edge source package in Xenial:
  Fix Released
Status in linux-oem source package in Xenial:
  Fix Released
Status in linux source package in Artful:
  Fix Released

Bug description:
  An update to linux kernel on Ubuntu 17.10 that enabled the Intel SPI
  drivers results in a serial flash that is read only in Intel Broadwell
  and Haswell machines with serial flashes with SPI_NOR_HAS_LOCK set.

  Symptoms:
   * BIOS settings cannot be saved
   * USB Boot impossible
   * EFI entries read-only.

  ---

  Fix: The issue was fixed in kernel version 4.13.0-21 by configuring
  the kernel so it is not compiled with Intel SPI support. But previous
  affected machines still suffered from a broken BIOS.

  Repair: If you still can boot into Ubuntu, you can recover your BIOS
  with the following steps:

  1. Boot into Ubuntu
  2. Download 
http://people.canonical.com/~ypwong/lp1734147/linux-image-4.15.0-041500rc6-generic_4.15.0-041500rc6.201712312330+20170103+1_amd64.deb
  3. Install the downloaded package:
    $ sudo dpkg -i 
linux-image-4.15.0-041500rc6-generic_4.15.0-041500rc6.201712312330+20170103+1_amd64.deb
  4. Make sure the kernel is installed without any error. Once installed, 
reboot.
  5. At grub, choose the newly installed kernel. You can choose the "recovery" 
mode.
  6. Reboot and go to BIOS settings to confirm your BIOS has been recovered.
  7. In case your BIOS is not recovered, reboot to the new kernel, then reboot 
*once again* to the new kernel, do not enter BIOS settings before the reboot. 
After the second reboot, check BIOS.
  8. If your BIOS issue remains, download another kernel from 
http://people.canonical.com/~ypwong/lp1734147/linux-image-4.15.0-041500rc6-generic_4.15.0-041500rc6.201712312330+clear+debug_amd64.deb,
 and use dpkg to install it, then repeat steps 4 to 6.

  After your BIOS is fixed, the kernel packages you just installed are
  no longer needed, you can remove it by running 'sudo dpkg -r linux-
  image-4.15.0-041500rc6-generic'.

  The patch used to build the linux v4.15 kernel in step 8 can be found
  at https://goo.gl/xUKJFR.

  ---

  Test Case: Fix has been verified by our HWE team on affected hardware.

  Regression Potential: Minimal, it's unlikely anyone is actually doing
  anything which requires this driver.

  ---

  Affected Machines:

  Lenovo B40-70
  Lenovo B50-70
  Lenovo B50-80
  Lenovo Flex-3
  Lenovo Flex-10
  Lenovo G40-30
  Lenovo G50-30
  Lenovo G50-70
  Lenovo G50-80
  Lenovo S20-30
  Lenovo U31-70
  Lenovo Y50-70
  Lenovo Y70-70
  Lenovo Yoga Thinkpad (20C0)
  Lenovo Yoga 2 11" - 20332
  Lenovo Yoga 3 11"
  Lenovo Z50-70
  Lenovo Z51-70
  Lenovo ideapad 100-15IBY

  Acer Aspire E5-771G
  Acer Aspire ES1-111M-C1LE (fixed following your new instruction (thank you))
  Acer TravelMate B113
  Acer Swift SF314-52 (Fixed by 4.14.9)
  Toshiba Satellite S55T-B5233
  Toshiba Satellite L50-B-1R7
  Toshiba Satellite S50-B-13G
  Dell Inspiron 15-3531
  Mediacom Smartbook 14 Ultra M-SB14UC
  Acer Aspire E3-111-C0UM
  HP 14-r012la

  ---

  Affected serial flash devices by manufacturer part number, JEDEC ID 
(SPI_NOR_HAS_LOCK set in drivers/mtd/spi-nor/spi-nor.c)
  /* ESMT */
     f25l32pa, 0x8c2016
     f25l32qa, 0x8c4116
     f25l64qa, 0x8c4117
  /* GigaDevice */
     gd25q16, 0xc84015
     gd25q32, 0xc84016
     gd25lq32, 0xc86016
     gd25q64, 0xc84017
     gd25lq64c, 0xc86017
     gd25q128, 0xc84018
     gd25q256, 0xc84019
  /* Winbond */
     w25q16dw, 0xef6015
     w25q32dw, 0xef6016
     w25q64dw, 0xef6017
     w25q128fw, 0xef6018

  ---

  Original Description:

  Basically on Lenovo Y50-70 after installing Ubuntu 17.10, many users
  reported a corrupted BIOS.

  It's not possible to save new settings in BIOS anymore and after
  rebooting, the system starts with the old settings.

  Moreover (and most important) USB booting is not possible anymore
  since USB is not recognized. It's very serious, since our machines do
  not have a CDROM.

  Lenovo forums at the moment are full of topics regading this issue.

  Thank you!!

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

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

[Kernel-packages] [Bug 1726519] Re: Unable to handle kernel NULL pointer dereference at isci_task_abort_task

2018-01-12 Thread Joseph Salisbury
This bug and bug 1742630 are probably duplicates.

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

Title:
  Unable to handle kernel NULL pointer dereference at
  isci_task_abort_task

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

Bug description:
  So I just upgrade from zesty zapus to artful aardvark. At boot, right
  after I enter my drive encryption password, it kernel panics with the
  above message.

  It doesn't even get far enough along in the boot process for syslog to
  log this panic, so the only info I have is a photo of the panic.

  In short, I can't boot using the latest artful aardvark kernel, and I
  have to boot with the latest zesty zapus kernel.

  :~$ lsb_release -rd
  Description:  Ubuntu 17.10
  Release:  17.10

  linux-image-4.13.0-16-generic

  I expect this isn't normal and I should be able to boot with the new
  kernel, which I can't.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-16-generic 4.13.0-16.19
  ProcVersionSignature: Ubuntu 4.10.0-37.41-generic 4.10.17
  Uname: Linux 4.10.0-37-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  lost   2071 F pulseaudio
   /dev/snd/controlC2:  lost   2071 F pulseaudio
   /dev/snd/controlC0:  lost   2071 F pulseaudio
  CurrentDesktop: XFCE
  Date: Mon Oct 23 12:52:20 2017
  HibernationDevice: RESUME=UUID=cf59c168-54d0-45b9-b633-240bd76bbaa6
  InstallationDate: Installed on 2016-11-01 (355 days ago)
  InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: LENOVO 11361Q0
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-37-generic 
root=/dev/mapper/xubuntu--vg-root ro quiet
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-37-generic N/A
   linux-backports-modules-4.10.0-37-generic  N/A
   linux-firmware 1.169
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: Upgraded to artful on 2017-10-23 (0 days ago)
  dmi.bios.date: 09/29/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: A3KT57AUS
  dmi.board.name: LENOVO
  dmi.board.vendor: LENOVO
  dmi.board.version: NO DPK
  dmi.chassis.asset.tag: 573921
  dmi.chassis.type: 7
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: NONE
  dmi.modalias: 
dmi:bvnLENOVO:bvrA3KT57AUS:bd09/29/2016:svnLENOVO:pn11361Q0:pvrThinkStationC30:rvnLENOVO:rnLENOVO:rvrNODPK:cvnLENOVO:ct7:cvrNONE:
  dmi.product.name: 11361Q0
  dmi.product.version: ThinkStation C30
  dmi.sys.vendor: LENOVO

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

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


[Kernel-packages] [Bug 1726519] Re: Unable to handle kernel NULL pointer dereference at isci_task_abort_task

2018-01-12 Thread Joseph Salisbury
I built a test kernel with the patch posted here:
https://marc.info/?l=linux-scsi=151557324907914

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

Can you test this kernel and see if it resolves this bug?

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

Title:
  Unable to handle kernel NULL pointer dereference at
  isci_task_abort_task

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

Bug description:
  So I just upgrade from zesty zapus to artful aardvark. At boot, right
  after I enter my drive encryption password, it kernel panics with the
  above message.

  It doesn't even get far enough along in the boot process for syslog to
  log this panic, so the only info I have is a photo of the panic.

  In short, I can't boot using the latest artful aardvark kernel, and I
  have to boot with the latest zesty zapus kernel.

  :~$ lsb_release -rd
  Description:  Ubuntu 17.10
  Release:  17.10

  linux-image-4.13.0-16-generic

  I expect this isn't normal and I should be able to boot with the new
  kernel, which I can't.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-16-generic 4.13.0-16.19
  ProcVersionSignature: Ubuntu 4.10.0-37.41-generic 4.10.17
  Uname: Linux 4.10.0-37-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  lost   2071 F pulseaudio
   /dev/snd/controlC2:  lost   2071 F pulseaudio
   /dev/snd/controlC0:  lost   2071 F pulseaudio
  CurrentDesktop: XFCE
  Date: Mon Oct 23 12:52:20 2017
  HibernationDevice: RESUME=UUID=cf59c168-54d0-45b9-b633-240bd76bbaa6
  InstallationDate: Installed on 2016-11-01 (355 days ago)
  InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: LENOVO 11361Q0
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-37-generic 
root=/dev/mapper/xubuntu--vg-root ro quiet
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-37-generic N/A
   linux-backports-modules-4.10.0-37-generic  N/A
   linux-firmware 1.169
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: Upgraded to artful on 2017-10-23 (0 days ago)
  dmi.bios.date: 09/29/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: A3KT57AUS
  dmi.board.name: LENOVO
  dmi.board.vendor: LENOVO
  dmi.board.version: NO DPK
  dmi.chassis.asset.tag: 573921
  dmi.chassis.type: 7
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: NONE
  dmi.modalias: 
dmi:bvnLENOVO:bvrA3KT57AUS:bd09/29/2016:svnLENOVO:pn11361Q0:pvrThinkStationC30:rvnLENOVO:rnLENOVO:rvrNODPK:cvnLENOVO:ct7:cvrNONE:
  dmi.product.name: 11361Q0
  dmi.product.version: ThinkStation C30
  dmi.sys.vendor: LENOVO

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

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


[Kernel-packages] [Bug 1742630] Re: Booting from 4.13 leads to Oops: NULL pointer dereference - RIP: isci_task_abort_task+0x30/0x3e0 [isci]

2018-01-12 Thread Joseph Salisbury
This bug and bug 1726519 are probably duplicates.

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

Title:
  Booting from 4.13 leads to Oops: NULL pointer dereference - RIP:
  isci_task_abort_task+0x30/0x3e0 [isci]

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

Bug description:
  I cannot boot from 4.13.0-21-generic

  Oops: NULL pointer dereference - RIP: isci_task_abort_task+0x30/0x3e0
  [isci]

  This Kernel bug was already fixed in Debian:
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=882414

  Relevant discussion:
  https://marc.info/?l=linux-scsi=151523964725984=2

  Ubuntu needs to fix this, because otherwise _many_ people will
  complain about crashes when they upgrade from 4.9 (or 4.4) to 4.13,
  which Ubuntu defined as their new “HWE” kernel.

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

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


[Kernel-packages] [Bug 1742722] Re: linux: 4.13.0-29.32 -proposed tracker

2018-01-12 Thread Kleber Sacilotto de Souza
** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
- backports: 1742723,1742725,1742726,1742727,1742728
+ backports: 1742723,1742725,1742726,1742727,1742728,1742928
  derivatives: 1742730

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

Title:
  linux: 4.13.0-29.32 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  In Progress
Status in Kernel SRU Workflow prepare-package-meta series:
  In Progress
Status in Kernel SRU Workflow prepare-package-signed series:
  In Progress
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Artful:
  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: 1742723,1742725,1742726,1742727,1742728,1742928
  derivatives: 1742730

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

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


[Kernel-packages] [Bug 1742630] Re: Booting from 4.13 leads to Oops: NULL pointer dereference - RIP: isci_task_abort_task+0x30/0x3e0 [isci]

2018-01-12 Thread Saverio Proto
I have the kernel running and I confirm that it resolved the bug

Linux s0008 4.13.0-25-generic #29~lp1742630 SMP Thu Jan 11 18:42:42 UTC
2018 x86_64 x86_64 x86_64 GNU/Linux

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

Title:
  Booting from 4.13 leads to Oops: NULL pointer dereference - RIP:
  isci_task_abort_task+0x30/0x3e0 [isci]

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

Bug description:
  I cannot boot from 4.13.0-21-generic

  Oops: NULL pointer dereference - RIP: isci_task_abort_task+0x30/0x3e0
  [isci]

  This Kernel bug was already fixed in Debian:
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=882414

  Relevant discussion:
  https://marc.info/?l=linux-scsi=151523964725984=2

  Ubuntu needs to fix this, because otherwise _many_ people will
  complain about crashes when they upgrade from 4.9 (or 4.4) to 4.13,
  which Ubuntu defined as their new “HWE” kernel.

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

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


[Kernel-packages] [Bug 1742696] Re: Commit d9018976cdb6 missing in Kernels <4.14.x preventing lasting fix of Intel SPI bug on certain serial flash

2018-01-12 Thread Christian List
So how are we going on with this?
As it seems I am the only one so far in this unique combination. Hence it might 
be too much asked to cherry pick the 4.13 kernels just for me?

I could try to build by current kernel (4.13.0-26) with patches and then stay 
on that one until 4.14 gets available? (never done that but would be worth a 
try?)
If more people show up here with the issue the cherry pick is still an option.

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

Title:
  Commit d9018976cdb6 missing in Kernels <4.14.x preventing lasting fix
  of Intel SPI bug on certain serial flash

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  New bug forked out of Bug #1734147 "corrupted BIOS due to Intel SPI
  bug in kernel Edit"

  When trying to apply the proposed fix in Bug #1734147 to a Lenovo Yoga
  with Serial Flash s25fl064k, the actual fix works, however reverting
  back to original available Kernel <4.14.x again locks the BIOS for
  write.

  How to identify chip: Using the Fix Kernel from Bug #1734147 the kernel log 
will show intel-spi entries.
  In lower part serial is shown as below:

  intel-spi intel-spi: s25fl064k (8192 Kbytes)

  Additional Information:
  Lenovo Yoga running Linux Mint 18.3 (based on Xenial 16.04)
  Bug #1734147 occured when trying Ubuntu 17.10

  
  Explanation by Mika Westerberg (Bug #1734147, Comment #524)
  "commit d9018976cdb6 is missing with this particular BIOS/system because 
every time you boot the system, the BIOS resets to default when it finds BCR 
register is changed. This is different issue than the CMP=1 issue most of the 
users have reported. This one also is not permanent so everything is fine as 
long as you don't touch that BCR register. In this case you either need to 
always boot to a kernel where that fix (d9018976cdb6) is included or blacklist 
lpc_ich.ko. Ubuntu v4.14.x kernels have that fix included so you might want to 
take one of them or build your own."

  New bug requested to discuss this separate from main Bug #1734147
  Anthony Wong (Bug #1734147, Comment #525)
  "Looks like we need to cherry-pick it to 4.13 after all.
  Christian, do you mind opening a new bug for your issue? We should continue 
the discussion and fix over there."

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

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


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

2018-01-12 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/1742920

Title:
  hang

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  just hangig our system

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-25-generic 4.13.0-25.29
  ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
  Uname: Linux 4.13.0-25-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  devvorld   1567 F pulseaudio
   /dev/snd/controlC0:  devvorld   1567 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jan 12 17:15:12 2018
  InstallationDate: Installed on 2018-01-02 (9 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: HP HP Notebook
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-25-generic 
root=UUID=677e5094-ae84-489f-9293-4cf58e0beebd ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-25-generic N/A
   linux-backports-modules-4.13.0-25-generic  N/A
   linux-firmware 1.169.1
  SourcePackage: linux
  UpgradeStatus: Upgraded to artful on 2018-01-02 (9 days ago)
  dmi.bios.date: 04/14/2016
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.04
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 81EF
  dmi.board.vendor: HP
  dmi.board.version: 63.25
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.04:bd04/14/2016:svnHP:pnHPNotebook:pvrType1ProductConfigId:rvnHP:rn81EF:rvr63.25:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP
  dmi.product.name: HP Notebook
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP

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

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


[Kernel-packages] [Bug 1742920] [NEW] hang

2018-01-12 Thread preety
Public bug reported:

just hangig our system

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: linux-image-4.13.0-25-generic 4.13.0-25.29
ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
Uname: Linux 4.13.0-25-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.7-0ubuntu3.7
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  devvorld   1567 F pulseaudio
 /dev/snd/controlC0:  devvorld   1567 F pulseaudio
CurrentDesktop: ubuntu:GNOME
Date: Fri Jan 12 17:15:12 2018
InstallationDate: Installed on 2018-01-02 (9 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
MachineType: HP HP Notebook
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-25-generic 
root=UUID=677e5094-ae84-489f-9293-4cf58e0beebd ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-4.13.0-25-generic N/A
 linux-backports-modules-4.13.0-25-generic  N/A
 linux-firmware 1.169.1
SourcePackage: linux
UpgradeStatus: Upgraded to artful on 2018-01-02 (9 days ago)
dmi.bios.date: 04/14/2016
dmi.bios.vendor: Insyde
dmi.bios.version: F.04
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: 81EF
dmi.board.vendor: HP
dmi.board.version: 63.25
dmi.chassis.asset.tag: Chassis Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: HP
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnInsyde:bvrF.04:bd04/14/2016:svnHP:pnHPNotebook:pvrType1ProductConfigId:rvnHP:rn81EF:rvr63.25:cvnHP:ct10:cvrChassisVersion:
dmi.product.family: 103C_5335KV G=N L=CON B=HP
dmi.product.name: HP Notebook
dmi.product.version: Type1ProductConfigId
dmi.sys.vendor: HP

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


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

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

Title:
  hang

Status in linux package in Ubuntu:
  New

Bug description:
  just hangig our system

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-25-generic 4.13.0-25.29
  ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
  Uname: Linux 4.13.0-25-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  devvorld   1567 F pulseaudio
   /dev/snd/controlC0:  devvorld   1567 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jan 12 17:15:12 2018
  InstallationDate: Installed on 2018-01-02 (9 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: HP HP Notebook
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-25-generic 
root=UUID=677e5094-ae84-489f-9293-4cf58e0beebd ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-25-generic N/A
   linux-backports-modules-4.13.0-25-generic  N/A
   linux-firmware 1.169.1
  SourcePackage: linux
  UpgradeStatus: Upgraded to artful on 2018-01-02 (9 days ago)
  dmi.bios.date: 04/14/2016
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.04
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 81EF
  dmi.board.vendor: HP
  dmi.board.version: 63.25
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.04:bd04/14/2016:svnHP:pnHPNotebook:pvrType1ProductConfigId:rvnHP:rn81EF:rvr63.25:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP
  dmi.product.name: HP Notebook
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP

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

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


[Kernel-packages] [Bug 1739341] Re: unshare test in ubuntu_stress_smoke_test cause OOM on Ubuntu on LPAR (Xenial)

2018-01-12 Thread Colin Ian King
Resolved issue, pushed a fix to http://kernel.ubuntu.com/git/cking
/stress-ng.git/commit/?id=1181d5c0913df0786e27ce10134a146deda261a6

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

Title:
  unshare test in ubuntu_stress_smoke_test cause OOM on Ubuntu on LPAR
  (Xenial)

Status in linux package in Ubuntu:
  In Progress

Bug description:
  Output from jenkins:
  22:22:50 DEBUG| [stdout] udp RETURNED 0
  22:22:50 DEBUG| [stdout] udp PASSED
  22:22:50 DEBUG| [stdout] udp-flood STARTING
  22:22:55 DEBUG| [stdout] udp-flood RETURNED 0
  22:22:55 DEBUG| [stdout] udp-flood PASSED
  22:22:55 DEBUG| [stdout] unshare STARTING
  Connection to s2lp3 closed by remote host.

  This test will cause OOM on this node. The job will be killed and I
  will need to reset the system via IBM HMC.

  Re-tested and it's reproducible (2 out of 2)

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-105-generic 4.4.0-105.128
  ProcVersionSignature: Ubuntu 4.4.0-105.128-generic 4.4.98
  Uname: Linux 4.4.0-105-generic s390x
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 
2: ls: cannot access '/dev/snd/': No such file or directory
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.1-0ubuntu2.14
  Architecture: s390x
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  Date: Tue Dec 19 22:09:03 2017
  HibernationDevice: RESUME=UUID=f578fa27-1d57-41c9-bb1d-7ff64c1c9345
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: Error: [Errno 2] No such file or directory: '/proc/fb'
  ProcKernelCmdLine: root=UUID=f26894a2-496d-4891-aa9a-f66344c9 
crashkernel=196M BOOT_IMAGE=0
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-105-generic N/A
   linux-backports-modules-4.4.0-105-generic  N/A
   linux-firmware 1.157.15
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Kernel-packages] [Bug 1661876] Re: [Asus UX360UA] battery status in unity-panel is not changing when battery is being charged

2018-01-12 Thread tjiagoM
Yes, that last command makes the icon appear, writing "100%", and with
the charging symbol! Shouldn't the icon-policy be set to present by
default (I guess this would solve the issue)?

However, that strange thing about the battery being at 98% (or even 95%
sometimes) and recognising it as full, continues to happen. I have to
explore more to see whether it is a problem with the battery or with
ubuntu.

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

Title:
  [Asus UX360UA] battery status in unity-panel is not changing when
  battery is being charged

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I've just installed Ubuntu 16.04.1 in dualboot on top of an Asus
  UX360UA, alongside with Windows 10. I've already installed the updates
  meanwhile.

  When I start charging my computer the battery icon on the unity-panel
  is not changing (it stays in the 98% complete).

  This is strange because this is a fresh installation so I didn't change any 
configuration yet. Also, when I tried this ubuntu in the live pen, I noticed 
that the icon changed when I started charging the laptop. That's why I think it 
is a bug.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tjiagom1806 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=0eaf9255-c29a-41b7-8449-1eb52f637933
  InstallationDate: Installed on 2017-02-04 (0 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 04f2:b56b Chicony Electronics Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. UX360UA
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-62-generic.efi.signed 
root=UUID=6ca1f963-632a-401d-80db-610ef37f1f26 ro quiet splash
  ProcVersionSignature: Ubuntu 4.4.0-62.83-generic 4.4.40
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-62-generic N/A
   linux-backports-modules-4.4.0-62-generic  N/A
   linux-firmware1.157.6
  Tags:  xenial
  Uname: Linux 4.4.0-62-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 06/17/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX360UA.300
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX360UA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX360UA.300:bd06/17/2016:svnASUSTeKCOMPUTERINC.:pnUX360UA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX360UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: UX360UA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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


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

2018-01-12 Thread Kleber Sacilotto de Souza
** Summary changed:

- linux: 4.13.0-28.31 -proposed tracker
+ linux:  -proposed tracker

** Summary changed:

- linux:  -proposed tracker
+ linux: 4.13.0-29.32 -proposed tracker

** Changed in: kernel-sru-workflow/prepare-package
 Assignee: Marcelo Cerri (mhcerri) => Kleber Sacilotto de Souza 
(kleber-souza)

** Changed in: kernel-sru-workflow/prepare-package-meta
 Assignee: Marcelo Cerri (mhcerri) => Kleber Sacilotto de Souza 
(kleber-souza)

** Changed in: kernel-sru-workflow/prepare-package-signed
 Assignee: Marcelo Cerri (mhcerri) => Kleber Sacilotto de Souza 
(kleber-souza)

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

Title:
  linux: 4.13.0-29.32 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  In Progress
Status in Kernel SRU Workflow prepare-package-meta series:
  In Progress
Status in Kernel SRU Workflow prepare-package-signed series:
  In Progress
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Artful:
  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: 1742723,1742725,1742726,1742727,1742728
  derivatives: 1742730

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

-- 
Mailing list: https://launchpad.net/~kernel-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: Add support for 16g huge pages on Ubuntu 16.04.2 PowerNV

2018-01-12 Thread bugproxy
--- Comment From sthou...@in.ibm.com 2018-01-12 06:04 EDT---
(In reply to comment #29)
> I built a Zesty test kernel with the following six patches:
>
> a525108cf1cc14651602d678da38fa627a76a724
> e1073d1e7920946ac4776a619cc40668b9e1401b
> 40692eb5eea209c2dd55857f44b4e1d7206e91d6
> e24a1307ba1f99fc62a0bd61d5e87fcfb6d5503d
> 79cc38ded1e1ac86e69c90f604efadd50b0b3762
> 4ae279c2c96ab38a78b954d218790a8f6db714e5
>
> The test kernel can be downloaded from:
>
> http://kernel.ubuntu.com/~jsalisbury/lp1706247/zesty
>
> Can you test this kernel and see if it resolves this bug?

https://bugzilla.linux.ibm.com/show_bug.cgi?id=156931#c25

Praveen K. Pandey 2017-12-14 02:49:52 CST

Hi ,

I verified this on kernel available on
http://kernel.ubuntu.com/~jsalisbury/lp1706247/artful/  and able to
allocate 16GB huge pages number .

** Bug watch added: bugzilla.linux.ibm.com/ #156931
   https://bugzilla.linux.ibm.com/show_bug.cgi?id=156931

-- 
You 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:
  Add support for 16g huge pages on Ubuntu 16.04.2 PowerNV

Status in The Ubuntu-power-systems project:
  Incomplete
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
Status in linux source package in Artful:
  In Progress

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 1742753] Re: Error after shutdown and reboot

2018-01-12 Thread MASSIMILIANO CANNATA
I have the same issue.
yes 4.4.0-109 and 4.14.13 solved both this issue then after upgrade wifi and 
other devices cannt be found anymore...

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

Title:
  Error after shutdown and reboot

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Distributor ID:   Ubuntu
  Description:  Ubuntu 16.04.3 LTS
  Release:  16.04
  Codename: xenial
  4.4.0-108-generic
  Linux version 4.4.0-108-generic (buildd@lgw01-amd64-003) (gcc version 5.4.0 
20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.5) ) #131-Ubuntu SMP Sun Jan 7 14:34:49 
UTC 2018

  Jan 12 00:21:18 gerasimchuk-dv-m kernel: [   11.133795] [ cut 
here ]
  Jan 12 00:21:18 gerasimchuk-dv-m kernel: [   11.133809] kernel BUG at 
/build/linux-J4_1pC/linux-4.4.0/mm/slub.c:3627!
  Jan 12 00:21:18 gerasimchuk-dv-m kernel: [   11.133823] invalid opcode:  
[#1] SMP
  Jan 12 00:21:18 gerasimchuk-dv-m kernel: [   11.133833] Modules linked in: 
nvram msr 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 uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 videobuf2_core 
v4l2_common videodev media bnep btusb joydev btrtl hid_alps binfmt_misc arc4 
snd_hda_codec_hdmi(OE) i2c_designware_platform i2c_designware_core dell_wmi 
dell_led intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel 
kvm snd_hda_codec_realtek(OE) irqbypass snd_hda_codec_generic(OE) iwlmvm(OE) 
mac80211(OE) crct10dif_pclmul dell_rbtn crc32_pclmul ghash_clmulni_intel 
dell_laptop dcdbas aesni_intel dell_smm_hwmon aes_x86_64 lrw snd_hda_intel(OE) 
gf128mul iwlwifi(OE) snd_hda_codec(OE) glue_helper ablk_helper rtsx_pci_ms 
snd_hda_core(OE) cryptd snd_hwdep memstick cfg80211(OE) snd_pcm snd_seq_midi 
compat(OE) snd_seq_midi_event snd_rawmidi input_leds snd_seq serio_raw 
snd_seq_device snd_timer idma64 snd virt_dma soundcore mei_me shpchp mei 
intel_lpss_pci processor_thermal_device intel_soc_dts_iosf hci_uart btbcm btqca 
btintel bluetooth intel_lpss_acpi intel_lpss int3400_thermal acpi_thermal_rel 
dell_smo8800 int3403_thermal int340x_thermal_zone acpi_pad acpi_als 
intel_hid(OE) mac_hid kfifo_buf sparse_keymap industrialio parport_pc ppdev lp 
parport autofs4 btrfs xor raid6_pq hid_generic usbhid rtsx_pci_sdmmc i915_bpo 
intel_ips i2c_algo_bit drm_kms_helper syscopyarea e1000e(OE) ptp sysfillrect 
sysimgblt pps_core fb_sys_fops rtsx_pci ahci drm libahci wmi i2c_hid hid 
pinctrl_sunrisepoint video pinctrl_intel fjes
  Jan 12 00:21:18 gerasimchuk-dv-m kernel: [   11.134217] CPU: 3 PID: 21 Comm: 
watchdog/3 Tainted: G   OE   4.4.0-108-generic #131-Ubuntu
  Jan 12 00:21:18 gerasimchuk-dv-m kernel: [   11.134234] Hardware name: Dell 
Inc. Latitude 5580/0DTP1F, BIOS 1.5.3 08/07/2017
  Jan 12 00:21:18 gerasimchuk-dv-m kernel: [   11.134248] task: 
880224016900 ti: 8802240f4000 task.ti: 8802240f4000
  Jan 12 00:21:18 gerasimchuk-dv-m kernel: [   11.134262] RIP: 
0010:[]  [] kfree+0x147/0x150
  Jan 12 00:21:18 gerasimchuk-dv-m kernel: [   11.134279] RSP: 
0018:8802240f7d58  EFLAGS: 00010246
  Jan 12 00:21:18 gerasimchuk-dv-m kernel: [   11.134289] RAX: ea0008b90120 
RBX: 88022e404840 RCX: 88022e7f9220
  Jan 12 00:21:18 gerasimchuk-dv-m kernel: [   11.134302] RDX: ea0008900c20 
RSI: ea0008901020 RDI: ea0008b90100
  Jan 12 00:21:18 gerasimchuk-dv-m kernel: [   11.134315] RBP: 8802240f7d70 
R08: 0009 R09: ff80003f
  Jan 12 00:21:18 gerasimchuk-dv-m kernel: [   11.134329] R10: ea0008b90100 
R11: 0001 R12: 
  Jan 12 00:21:18 gerasimchuk-dv-m kernel: [   11.134342] R13: 810104ff 
R14: 81f3c840 R15: 
  Jan 12 00:21:18 gerasimchuk-dv-m kernel: [   11.134355] FS:  
() GS:88022e58() knlGS:
  Jan 12 00:21:18 gerasimchuk-dv-m kernel: [   11.134390] CS:  0010 DS:  
ES:  CR0: 80050033
  Jan 12 00:21:18 gerasimchuk-dv-m kernel: [   11.134402] CR2: 009c5ec8 
CR3: 01e0a000 CR4: 00360670
  Jan 12 00:21:18 gerasimchuk-dv-m kernel: [   11.134430] DR0:  
DR1:  DR2: 
  Jan 12 00:21:18 gerasimchuk-dv-m kernel: [   11.134455] DR3:  
DR6: fffe0ff0 DR7: 0400
  Jan 12 00:21:18 gerasimchuk-dv-m kernel: [   11.134468] Stack:
  Jan 12 00:21:18 gerasimchuk-dv-m kernel: [   11.134473]   
 d440 8802240f7da0
  Jan 12 00:21:18 gerasimchuk-dv-m kernel: [   11.134489]  810104ff 
0008 0186 0003
  Jan 12 00:21:18 gerasimchuk-dv-m kernel: [   11.134505]  

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

2018-01-12 Thread bugproxy
--- Comment From heinz-werner_se...@de.ibm.com 2018-01-12 05:26 EDT---
IBM bugzilla status-> closed; now Fix Released within Artful/Bionic

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

Title:
  s390/mm: fix write access check in gup_huge_pmd()

Status in Ubuntu on IBM z Systems:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Fix Released
Status in linux source package in Zesty:
  Fix Released
Status in linux source package in Artful:
  Fix Released
Status in linux source package in Bionic:
  Fix Released

Bug description:
  == SRU Justification ==
  The check for the _SEGMENT_ENTRY_PROTECT bit in gup_huge_pmd() is the
  wrong way around. It must not be set for write==1, and not be checked for
  write==0. Fix this similar to how it was fixed for ptes long time ago in
  commit 25591b0 ("[S390] fix get_user_pages_fast").

  One impact of this bug would be unnecessarily using the gup slow path for
  write==0 on r/w mappings. A potentially more severe impact would be that
  gup_huge_pmd() will succeed for write==1 on r/o mappings.

  This bug is fixed by mainline commit ba385c0594, which is in mainline
  as of v4.14-rc2.  It was also cc'd to upstream stable.  It has already
  been accepted in upstream v4.13.y, so Artful and Bionic have the fix
  via the 4.13.5 stable updates.

  == Fix ==
  commit ba385c0594e723d41790ecfb12c610e6f90c7785
  Author: Gerald Schaefer 
  Date:   Mon Sep 18 16:51:51 2017 +0200

  s390/mm: fix write access check in gup_huge_pmd()

  
  == Regression Potential ==
  This patch is specific to s390.  It has also been accepted by upstream 
stable, so additional upstream review has been done.


  
  Addl information

  Problem: The check for the _SEGMENT_ENTRY_PROTECT bit in
    gup_huge_pmd() is the wrong way around. It must not be set
    for write==1, and not be checked for write==0. Allowing
    write==1 with protection bit set, instead of breaking out
    to the slow path, will result in a missing faultin_page()
    to clear the protection bit (for valid writable mappings),
    and the async I/O write operation will fail to write to
    such a mapping.
  Solution: Fix it by correctly checking the protection bit like it is
    also done in gup_pte_range() and gup_huge_pud().
  Reproduction: Async I/O workload on buffers that are mapped as transparent
    hugepages.
  Upstream-ID:  ba385c0594e723d41790ecfb12c610e6f90c7785

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

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


[Kernel-packages] [Bug 1742095] Re: kernel 4.13.0-24 not working with nvidia drivers, monitor flickering

2018-01-12 Thread Maraschin
I can confirm that upgrading nvidia to 387.34 does the trick!

PPA is available here:
https://launchpad.net/~graphics-drivers/+archive/ubuntu/ppa

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

Title:
  kernel 4.13.0-24 not working with nvidia drivers, monitor flickering

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  After update to kernel 4.13.0-24 gnome will not start and the monitors will 
be flickering...
  It is impossible to see were it stops on the startup since the flickering is 
too fast (I may have to film it and pause to check)

  Running:
  Ubuntu 17.10, 64 bit OS
  HP ZBooks G2 15" with latest bios update
  Processor: Intel® Xeon(R) CPU E3-1505M v5 @ 2.80GHz × 8 
  Memory: 15.6 GB
  GNOME: 3.26.2 vanilla with nvidia-387 drivers

  System is working fine if I keep using kernel 4.13.0-22
  --- 
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  carlo  4669 F pulseaudio
   /dev/snd/controlC2:  carlo  4669 F pulseaudio
   /dev/snd/controlC0:  carlo  4669 F pulseaudio
  DistroRelease: Ubuntu 17.10
  HibernationDevice: RESUME=/dev/mapper/vg-swap
  InstallationDate: Installed on 2016-04-25 (624 days ago)
  InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.3)
  MachineType: HP HP ZBook Studio G3
  Package: linux (not installed)
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-24-generic 
root=/dev/mapper/vg-data ro
  ProcVersionSignature: Ubuntu 4.13.0-24.28-generic 4.13.13
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-24-generic N/A
   linux-backports-modules-4.13.0-24-generic  N/A
   linux-firmware 1.169.2
  Tags:  artful
  Uname: Linux 4.13.0-24-generic x86_64
  UpgradeStatus: Upgraded to artful on 2017-10-20 (81 days ago)
  UserGroups: adm cdrom dip docker libvirt libvirtd lpadmin lxd plugdev 
sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/26/2017
  dmi.bios.vendor: HP
  dmi.bios.version: N82 Ver. 01.19
  dmi.board.name: 80D4
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 11.6F
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrN82Ver.01.19:bd09/26/2017:svnHP:pnHPZBookStudioG3:pvr:rvnHP:rn80D4:rvrKBCVersion11.6F:cvnHP:ct10:cvr:
  dmi.product.family: 103C_5336AN
  dmi.product.name: HP ZBook Studio G3
  dmi.sys.vendor: HP

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

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


[Kernel-packages] [Bug 1742302] Re: Kernel 4.13.0-25 broke nvidia driver

2018-01-12 Thread fgr1986
The same happens with driver 340 and 384. Older kernels work fine.
For now I have disabled nvidia's driver, and the open-sourced driver works.

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

Title:
  Kernel 4.13.0-25 broke nvidia driver

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After updating to linux-image-4.13.0-25-generic the binary nvidia
  driver 387.22 cannot be built. As a result the system does not boot
  into the desktop environment (in my case, KDE).

  I've attached the driver build log.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-25-generic 4.13.0-25.29
  ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13
  Uname: Linux 4.13.0-21-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  lastique   3049 F pulseaudio
   /dev/snd/controlC2:  lastique   3049 F pulseaudio
   /dev/snd/controlC3:  lastique   3049 F pulseaudio
   /dev/snd/controlC1:  lastique   3049 F pulseaudio
  CurrentDesktop: KDE
  Date: Wed Jan 10 02:00:46 2018
  InstallationDate: Installed on 2015-05-01 (984 days ago)
  InstallationMedia: Kubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: System manufacturer System Product Name
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-21-generic 
root=UUID=a03f1835-52f9-4409-9da7-fe45770637ae ro quiet splash nomdmonddf 
nomdmonisw
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-21-generic N/A
   linux-backports-modules-4.13.0-21-generic  N/A
   linux-firmware 1.169.1
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: Upgraded to artful on 2017-11-03 (67 days ago)
  dmi.bios.date: 11/09/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3603
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P8Z68-V PRO
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3603:bd11/09/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP8Z68-VPRO:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

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


[Kernel-packages] [Bug 1741409] Re: stress smoke test hang with dev test on AWS Xenial kernel

2018-01-12 Thread Po-Hsu Lin
Tested with 4.4.0-109 lowlatency kernel, this dev test can pass now.

I will leave this bug open as discussed on the IRC.

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

Title:
  stress smoke test hang with dev test on AWS Xenial kernel

Status in linux-aws package in Ubuntu:
  In Progress

Bug description:
  The test will hang on dev STARTING, and get killed by the timeout
  setting.

  DEBUG| [stdout] dccp PASSED
  DEBUG| [stdout] dentry STARTING
  DEBUG| [stdout] dentry RETURNED 0
  DEBUG| [stdout] dentry PASSED
  DEBUG| [stdout] dev STARTING

  No interesting output in dmesg:
  [8.281861] random: nonblocking pool is initialized
  [8.338335] ppdev: user-space parallel port driver
  [   11.662848] cgroup: new mount options do not match the existing 
superblock, will be ignored
  [   12.272168] systemd[1]: Started ACPI event daemon.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-1045-aws 4.4.0-1045.54
  ProcVersionSignature: User Name 4.4.0-1045.54-aws 4.4.98
  Uname: Linux 4.4.0-1045-aws x86_64
  ApportVersion: 2.20.1-0ubuntu2.14
  Architecture: amd64
  Date: Fri Jan  5 06:47:45 2018
  Ec2AMI: ami-a2e544da
  Ec2AMIManifest: (unknown)
  Ec2AvailabilityZone: us-west-2b
  Ec2InstanceType: t2.nano
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-aws
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Kernel-packages] [Bug 1738491] Re: touchpad not working

2018-01-12 Thread David Franko
** Attachment added: "libinput-devices"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1738491/+attachment/5035736/+files/libinput-devices

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

Title:
  touchpad not working

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  chuwi Lapbook Air touch pad not working

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

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


[Kernel-packages] [Bug 1738491] Re: touchpad not working

2018-01-12 Thread David Franko
** Attachment added: "Xorg.0.log"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1738491/+attachment/5035739/+files/Xorg.0.log

** Attachment removed: "proc_bus_input_devices"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1738491/+attachment/5035737/+files/proc_bus_input_devices

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

Title:
  touchpad not working

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  chuwi Lapbook Air touch pad not working

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

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


[Kernel-packages] [Bug 1738491] Re: touchpad not working

2018-01-12 Thread David Franko
** Attachment added: "evtest.log"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1738491/+attachment/5035735/+files/evtest.log

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

Title:
  touchpad not working

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  chuwi Lapbook Air touch pad not working

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

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


[Kernel-packages] [Bug 1738491] Re: touchpad not working

2018-01-12 Thread David Franko
Maybe, the device is similar to ours, but they were able to get some
movement from the touchpad and we dont.

I collected some logs (sorry, i dont have ubuntu now, i tried again with
mainline kernel).


** Attachment added: "dmesg"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1738491/+attachment/5035734/+files/dmesg

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

Title:
  touchpad not working

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  chuwi Lapbook Air touch pad not working

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

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


[Kernel-packages] [Bug 1738491] Re: touchpad not working

2018-01-12 Thread David Franko
** Attachment added: "proc_bus_input_devices"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1738491/+attachment/5035738/+files/proc_bus_input_devices

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

Title:
  touchpad not working

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  chuwi Lapbook Air touch pad not working

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

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


[Kernel-packages] [Bug 1738491] Re: touchpad not working

2018-01-12 Thread David Franko
** Attachment added: "proc_bus_input_devices"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1738491/+attachment/5035737/+files/proc_bus_input_devices

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

Title:
  touchpad not working

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  chuwi Lapbook Air touch pad not working

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

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


[Kernel-packages] [Bug 1742095] Re: kernel 4.13.0-24 not working with nvidia drivers, monitor flickering

2018-01-12 Thread Harish Ranganathan
I've just fixed this by purging the nvidia drivers and installing
nvidia-387.34

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

Title:
  kernel 4.13.0-24 not working with nvidia drivers, monitor flickering

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  After update to kernel 4.13.0-24 gnome will not start and the monitors will 
be flickering...
  It is impossible to see were it stops on the startup since the flickering is 
too fast (I may have to film it and pause to check)

  Running:
  Ubuntu 17.10, 64 bit OS
  HP ZBooks G2 15" with latest bios update
  Processor: Intel® Xeon(R) CPU E3-1505M v5 @ 2.80GHz × 8 
  Memory: 15.6 GB
  GNOME: 3.26.2 vanilla with nvidia-387 drivers

  System is working fine if I keep using kernel 4.13.0-22
  --- 
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  carlo  4669 F pulseaudio
   /dev/snd/controlC2:  carlo  4669 F pulseaudio
   /dev/snd/controlC0:  carlo  4669 F pulseaudio
  DistroRelease: Ubuntu 17.10
  HibernationDevice: RESUME=/dev/mapper/vg-swap
  InstallationDate: Installed on 2016-04-25 (624 days ago)
  InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.3)
  MachineType: HP HP ZBook Studio G3
  Package: linux (not installed)
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-24-generic 
root=/dev/mapper/vg-data ro
  ProcVersionSignature: Ubuntu 4.13.0-24.28-generic 4.13.13
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-24-generic N/A
   linux-backports-modules-4.13.0-24-generic  N/A
   linux-firmware 1.169.2
  Tags:  artful
  Uname: Linux 4.13.0-24-generic x86_64
  UpgradeStatus: Upgraded to artful on 2017-10-20 (81 days ago)
  UserGroups: adm cdrom dip docker libvirt libvirtd lpadmin lxd plugdev 
sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/26/2017
  dmi.bios.vendor: HP
  dmi.bios.version: N82 Ver. 01.19
  dmi.board.name: 80D4
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 11.6F
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrN82Ver.01.19:bd09/26/2017:svnHP:pnHPZBookStudioG3:pvr:rvnHP:rn80D4:rvrKBCVersion11.6F:cvnHP:ct10:cvr:
  dmi.product.family: 103C_5336AN
  dmi.product.name: HP ZBook Studio G3
  dmi.sys.vendor: HP

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

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


[Kernel-packages] [Bug 1726519] Re: Unable to handle kernel NULL pointer dereference at isci_task_abort_task

2018-01-12 Thread Fabian Grünbichler
the following upstream patch seems like a likely fix:

https://patchwork.kernel.org/patch/10154587/

otherwise, reverting the buggy commit seems to solve the issue as well
as a temporary measure.

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

Title:
  Unable to handle kernel NULL pointer dereference at
  isci_task_abort_task

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

Bug description:
  So I just upgrade from zesty zapus to artful aardvark. At boot, right
  after I enter my drive encryption password, it kernel panics with the
  above message.

  It doesn't even get far enough along in the boot process for syslog to
  log this panic, so the only info I have is a photo of the panic.

  In short, I can't boot using the latest artful aardvark kernel, and I
  have to boot with the latest zesty zapus kernel.

  :~$ lsb_release -rd
  Description:  Ubuntu 17.10
  Release:  17.10

  linux-image-4.13.0-16-generic

  I expect this isn't normal and I should be able to boot with the new
  kernel, which I can't.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-16-generic 4.13.0-16.19
  ProcVersionSignature: Ubuntu 4.10.0-37.41-generic 4.10.17
  Uname: Linux 4.10.0-37-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  lost   2071 F pulseaudio
   /dev/snd/controlC2:  lost   2071 F pulseaudio
   /dev/snd/controlC0:  lost   2071 F pulseaudio
  CurrentDesktop: XFCE
  Date: Mon Oct 23 12:52:20 2017
  HibernationDevice: RESUME=UUID=cf59c168-54d0-45b9-b633-240bd76bbaa6
  InstallationDate: Installed on 2016-11-01 (355 days ago)
  InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: LENOVO 11361Q0
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-37-generic 
root=/dev/mapper/xubuntu--vg-root ro quiet
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-37-generic N/A
   linux-backports-modules-4.10.0-37-generic  N/A
   linux-firmware 1.169
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: Upgraded to artful on 2017-10-23 (0 days ago)
  dmi.bios.date: 09/29/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: A3KT57AUS
  dmi.board.name: LENOVO
  dmi.board.vendor: LENOVO
  dmi.board.version: NO DPK
  dmi.chassis.asset.tag: 573921
  dmi.chassis.type: 7
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: NONE
  dmi.modalias: 
dmi:bvnLENOVO:bvrA3KT57AUS:bd09/29/2016:svnLENOVO:pn11361Q0:pvrThinkStationC30:rvnLENOVO:rnLENOVO:rvrNODPK:cvnLENOVO:ct7:cvrNONE:
  dmi.product.name: 11361Q0
  dmi.product.version: ThinkStation C30
  dmi.sys.vendor: LENOVO

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

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


[Kernel-packages] [Bug 1734147] Re: corrupted BIOS due to Intel SPI bug in kernel

2018-01-12 Thread farid
Ubuntu 17.10.1 (Artful Aardvark)


http://releases.ubuntu.com/17.10.1/

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

Title:
  corrupted BIOS due to Intel SPI bug in kernel

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Fix Released
Status in linux-hwe-edge source package in Xenial:
  Fix Released
Status in linux-oem source package in Xenial:
  Fix Released
Status in linux source package in Artful:
  Fix Released

Bug description:
  An update to linux kernel on Ubuntu 17.10 that enabled the Intel SPI
  drivers results in a serial flash that is read only in Intel Broadwell
  and Haswell machines with serial flashes with SPI_NOR_HAS_LOCK set.

  Symptoms:
   * BIOS settings cannot be saved
   * USB Boot impossible
   * EFI entries read-only.

  ---

  Fix: The issue was fixed in kernel version 4.13.0-21 by configuring
  the kernel so it is not compiled with Intel SPI support. But previous
  affected machines still suffered from a broken BIOS.

  Repair: If you still can boot into Ubuntu, you can recover your BIOS
  with the following steps:

  1. Boot into Ubuntu
  2. Download 
http://people.canonical.com/~ypwong/lp1734147/linux-image-4.15.0-041500rc6-generic_4.15.0-041500rc6.201712312330+20170103+1_amd64.deb
  3. Install the downloaded package:
    $ sudo dpkg -i 
linux-image-4.15.0-041500rc6-generic_4.15.0-041500rc6.201712312330+20170103+1_amd64.deb
  4. Make sure the kernel is installed without any error. Once installed, 
reboot.
  5. At grub, choose the newly installed kernel. You can choose the "recovery" 
mode.
  6. Reboot and go to BIOS settings to confirm your BIOS has been recovered.
  7. In case your BIOS is not recovered, reboot to the new kernel, then reboot 
*once again* to the new kernel, do not enter BIOS settings before the reboot. 
After the second reboot, check BIOS.
  8. If your BIOS issue remains, download another kernel from 
http://people.canonical.com/~ypwong/lp1734147/linux-image-4.15.0-041500rc6-generic_4.15.0-041500rc6.201712312330+clear+debug_amd64.deb,
 and use dpkg to install it, then repeat steps 4 to 6.

  After your BIOS is fixed, the kernel packages you just installed are
  no longer needed, you can remove it by running 'sudo dpkg -r linux-
  image-4.15.0-041500rc6-generic'.

  The patch used to build the linux v4.15 kernel in step 8 can be found
  at https://goo.gl/xUKJFR.

  ---

  Test Case: Fix has been verified by our HWE team on affected hardware.

  Regression Potential: Minimal, it's unlikely anyone is actually doing
  anything which requires this driver.

  ---

  Affected Machines:

  Lenovo B40-70
  Lenovo B50-70
  Lenovo B50-80
  Lenovo Flex-3
  Lenovo Flex-10
  Lenovo G40-30
  Lenovo G50-30
  Lenovo G50-70
  Lenovo G50-80
  Lenovo S20-30
  Lenovo U31-70
  Lenovo Y50-70
  Lenovo Y70-70
  Lenovo Yoga Thinkpad (20C0)
  Lenovo Yoga 2 11" - 20332
  Lenovo Yoga 3 11"
  Lenovo Z50-70
  Lenovo Z51-70
  Lenovo ideapad 100-15IBY

  Acer Aspire E5-771G
  Acer Aspire ES1-111M-C1LE (fixed following your new instruction (thank you))
  Acer TravelMate B113
  Acer Swift SF314-52 (Fixed by 4.14.9)
  Toshiba Satellite S55T-B5233
  Toshiba Satellite L50-B-1R7
  Toshiba Satellite S50-B-13G
  Dell Inspiron 15-3531
  Mediacom Smartbook 14 Ultra M-SB14UC
  Acer Aspire E3-111-C0UM
  HP 14-r012la

  ---

  Affected serial flash devices by manufacturer part number, JEDEC ID 
(SPI_NOR_HAS_LOCK set in drivers/mtd/spi-nor/spi-nor.c)
  /* ESMT */
     f25l32pa, 0x8c2016
     f25l32qa, 0x8c4116
     f25l64qa, 0x8c4117
  /* GigaDevice */
     gd25q16, 0xc84015
     gd25q32, 0xc84016
     gd25lq32, 0xc86016
     gd25q64, 0xc84017
     gd25lq64c, 0xc86017
     gd25q128, 0xc84018
     gd25q256, 0xc84019
  /* Winbond */
     w25q16dw, 0xef6015
     w25q32dw, 0xef6016
     w25q64dw, 0xef6017
     w25q128fw, 0xef6018

  ---

  Original Description:

  Basically on Lenovo Y50-70 after installing Ubuntu 17.10, many users
  reported a corrupted BIOS.

  It's not possible to save new settings in BIOS anymore and after
  rebooting, the system starts with the old settings.

  Moreover (and most important) USB booting is not possible anymore
  since USB is not recognized. It's very serious, since our machines do
  not have a CDROM.

  Lenovo forums at the moment are full of topics regading this issue.

  Thank you!!

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

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


  1   2   >