date:20170927

Tried it with a cp2102 usb->serial via usbip and its fine: on the kernel
4.14 so it looks like its probably usb-storage specific

[  108.613882] vhci_hcd vhci_hcd.0: pdev(0) rhport(0) sockfd(21)
[  108.613886] vhci_hcd vhci_hcd.0: devid(4) speed(2) speed_str(full-speed)
[  108.824764] vhci_hcd: vhci_device speed not set
[  108.885465] usb 3-1: new full-speed USB device number 2 using vhci_hcd
[  108.956844] vhci_hcd: vhci_device speed not set
[  109.016944] usb 3-1: SetAddress Request (2) to port 0
[  109.058931] usb 3-1: New USB device found, idVendor=10c4, idProduct=ea60
[  109.058934] usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[  109.058937] usb 3-1: Product: CP2102 USB to UART Bridge Controller
[  109.058939] usb 3-1: Manufacturer: Silicon Labs
[  109.058940] usb 3-1: SerialNumber: 0001
[  109.083878] usbcore: registered new interface driver usbserial
[  109.083895] usbcore: registered new interface driver usbserial_generic
[  109.083910] usbserial: USB Serial support registered for generic
[  109.087722] usbcore: registered new interface driver cp210x
[  109.087738] usbserial: USB Serial support registered for cp210x
[  109.087767] cp210x 3-1:1.0: cp210x converter detected
[  109.116156] usb 3-1: cp210x converter now attached to ttyUSB0

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

Title:
  kernel BUG at /build/linux-
  s_bACt/linux-4.13.0/drivers/usb/usbip/vhci_hcd.c:683!

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  When using a usb flash disk via usbip it crashes with this bug

  ProblemType: KernelOops
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-12-generic 4.13.0-12.13
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  Annotation: Your system might become unstable now and might need to be 
restarted.
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Date: Wed Sep 27 06:24:09 2017
  Failure: oops
  InstallationDate: Installed on 2017-09-27 (0 days ago)
  InstallationMedia: Xubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170829.1)
  IwConfig:
   ens33 no wireless extensions.
   
   lono wireless extensions.
  MachineType: VMware, Inc. VMware Virtual Platform
  ProcFB: 0 svgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-12-generic 
root=UUID=33763e28-10a5-4446-afbd-8cb727ae9363 ro find_preseed=/preseed.cfg 
auto noprompt priority=critical locale=en_US quiet
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: kerneloops-daemon N/A
  RfKill:
   
  SourcePackage: linux
  Title: kernel BUG at 
/build/linux-s_bACt/linux-4.13.0/drivers/usb/usbip/vhci_hcd.c:683!
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/02/2015
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: 6.00
  dmi.board.name: 440BX Desktop Reference Platform
  dmi.board.vendor: Intel Corporation
  dmi.board.version: None
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 1
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd07/02/2015:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
  dmi.product.name: VMware Virtual Platform
  dmi.product.version: None
  dmi.sys.vendor: VMware, Inc.

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

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

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

--- Comment From hasri...@in.ibm.com 2017-09-28 01:15 EDT---
(In reply to comment #50)
> I built the next test kernel, up to the following commit:
> d7fd24257aa60316bf81093f7f909dc9475ae974
>
> The test kernel can be downloaded from:
> http://kernel.ubuntu.com/~jsalisbury/lp1696049
>

Test passed with the given kernel.

Thanks,
Harish S

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

Title:
  xfstest sanity checks on seek operations fails

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

Bug description:
  == Comment: #0 - Harish Sriram 
  Issue:
  --
  xfstest fails with sanity checks on seek operations

  # uname -a
  Linux ltc-tuleta12 4.10.0-21-generic #23~16.04.1-Ubuntu SMP Tue May 2 
12:54:57 UTC 2017 ppc64le ppc64le ppc64le GNU/Linux

  Steps to reproduce:
  
  1. Create a loop device with xfs filesystem
  2. git clone git://git.kernel.org/pub/scm/fs/xfs/xfstests-dev.git; cd 
xfstests-dev
  3. make
  4. Create a local.config for running with created loop device
  5. Run xfstests-dev test  : ./check tests/generic/285 or ./check 
tests/generic/436

  The test 285 fails with following
  ...
  ...
  07. Test file with unwritten extents, only have dirty pages
  07.01 SEEK_HOLE expected 0 or 45056, got 0.   succ
  07.02 SEEK_HOLE expected 1 or 45056, got 1.   succ
  07.03 SEEK_DATA expected 40960 or 40960, got -1.  FAIL
  07.04 SEEK_DATA expected 40960 or 40960, got -1.  FAIL

  08. Test file with unwritten extents, only have unwritten pages
  08.01 SEEK_HOLE expected 0 or 45056, got 0.   succ
  08.02 SEEK_HOLE expected 1 or 45056, got 1.   succ
  08.03 SEEK_DATA expected 40960 or 40960, got -1.  FAIL
  08.04 SEEK_DATA expected 40960 or 40960, got -1.  FAIL

  The test 436 fails with 
  ...
  ...
  14. Test file with unwritten extents, small hole after pagevec dirty pages
  14.01 SEEK_HOLE expected 917504 or 4194304, got 3670016.  FAIL
  14.02 SEEK_HOLE expected 917504 or 4194304, got 3670016.  FAIL
  14.03 SEEK_HOLE expected 3670016 or 4194304, got 3670016. succ
  14.04 SEEK_DATA expected 0 or 0, got 0.   succ
  14.05 SEEK_DATA expected 1 or 1, got 1.   succ
  14.06 SEEK_DATA expected 2752512 or 2752512, got 2752512. succ

  seek sanity check failed!

  Full log is attached.

  == Comment: #6 - Harish Sriram

  commit 5375023ae1266553a7baa0845e82917d8803f48c
  Author: Jan Kara 
  Date:   Thu May 18 16:36:22 2017 -0700

  xfs: Fix missed holes in SEEK_HOLE implementation
  XFS SEEK_HOLE implementation could miss a hole in an unwritten extent as
  can be seen by the following command:
  
  xfs_io -c "falloc 0 256k" -c "pwrite 0 56k" -c "pwrite 128k 8k"
 -c "seek -h 0" file
  wrote 57344/57344 bytes at offset 0
  56 KiB, 14 ops; 0. sec (49.312 MiB/sec and 12623.9856 ops/sec)
  wrote 8192/8192 bytes at offset 131072
  8 KiB, 2 ops; 0. sec (70.383 MiB/sec and 18018.0180 ops/sec)
  Whence  Result
  HOLE139264
  
  Where we can see that hole at offset 56k was just ignored by SEEK_HOLE
  implementation. The bug is in xfs_find_get_desired_pgoff() which does
  not properly detect the case when pages are not contiguous.
  
  Fix the problem by properly detecting when found page has larger offset
  than expected.
  
  CC: sta...@vger.kernel.org
  Fixes: d126d43f631f996daeee5006714fed914be32368
  Signed-off-by: Jan Kara 
  Reviewed-by: Brian Foster 
  Reviewed-by: Darrick J. Wong 
  Signed-off-by: Darrick J. Wong 

  
  The above commit fixes the generic/436 test, but generic/285 still FAILS.

  The generic/285 failure is reproducible on most P8/P9 systems.

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

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

[Kernel-packages] [Bug 1717656] Re: Shadow memory range interleaves with an existing memory mapping. ASan cannot proceed correctly

2017-09-27 Thread Chamal De Silva

I can confirm this bug is resolved now.

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

Title:
  Shadow memory range interleaves with an existing memory mapping. ASan
  cannot proceed correctly

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

Bug description:
  Ubuntu 16.04
  Linux Kernel 4.4.0-93-generic

  Steps
  -
  1. Build chromium with address sanitizer
 https://www.chromium.org/developers/testing/addresssanitizer
  2. Received below mentioned error.
 ==6372==Shadow memory range interleaves with an existing memory mapping. 
ASan cannot proceed correctly. ABORTING.
 ==6372==ASan shadow was supposed to be located in the 
[0x7fff7000-0x10007fff7fff] range.

  This error occurs after a recent change to linux kernel. This bug is tracked 
in 
  https://bugzilla.kernel.org/show_bug.cgi?id=196537.

  Please provide an update for linux kernel for Ubuntu users.

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

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

[Kernel-packages] [Bug 1705299] Re: Ubuntu not compatible w MSI A88XM-E35 MoBo ?

2017-09-27 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/1705299

Title:
  Ubuntu not compatible w MSI A88XM-E35 MoBo ?

Status in linux package in Ubuntu:
  Expired

Bug description:
  Hi
  Needing to clone my IDE 14.04.5 boot drive to replace with a SSD I made a 
livestick which loop reboots.
  The Mother Board is MSI A88XM-E35 with APU A8-5600K. I updated the MoBo to 
latest BIOS V30.6 with no help.
  I get this :

  Missing parameter in configuration file. Keyword: path
  gfxboo.c32: not a COM32R image
  boot:
  TAB
  live live-install check memtest
  boot: live
  [0.024700] [firmware Bug]: AMD-Vi: IOAPIC[0] not in IVRS table
  [0.024778] [firmware Bug]: No southbridge IOAPIC found in IVRS table
  [0.024807] AMD-V i: Disabling interrupt remapping

  then the PC reboots
  ---
  ApportVersion: 2.14.1-0ubuntu3.25
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  fab2381 F pulseaudio
   /dev/snd/controlC0:  fab2381 F pulseaudio
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=66392631-7c4f-4773-8614-4c5ea0913890
  InstallationDate: Installed on 2014-07-26 (1089 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  IwConfig:
   eth1  no wireless extensions.

   lono wireless extensions.
  MachineType: MSI MS-7721
  Package: linux (not installed)
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-125-generic 
root=UUID=09ecdff0-44fe-437e-8063-deabc6feb00e ro rootdelay=30
  ProcVersionSignature: Ubuntu 3.13.0-125.174-generic 3.13.11-ckt39
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-125-generic N/A
   linux-backports-modules-3.13.0-125-generic  N/A
   linux-firmware  1.127.23
  RfKill:

  Tags:  trusty
  Uname: Linux 3.13.0-125-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

  _MarkForUpload: True
  dmi.bios.date: 12/15/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V30.6
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: A88XM-E35 (MS-7721)
  dmi.board.vendor: MSI
  dmi.board.version: 6.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 6.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV30.6:bd12/15/2014:svnMSI:pnMS-7721:pvr6.0:rvnMSI:rnA88XM-E35(MS-7721):rvr6.0:cvnMSI:ct3:cvr6.0:
  dmi.product.name: MS-7721
  dmi.product.version: 6.0
  dmi.sys.vendor: MSI

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

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

[Kernel-packages] [Bug 1646277] Re: Xenial server 16.04.x will have a black screen after PXE installation

2017-09-27 Thread NancyHsu

The bug didn't happened on test kernel 4.1.0-3.
commit: c6ff6112bd446505fb75a70690b953501bd4837f

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

Title:
  Xenial server 16.04.x will have a black screen after PXE installation

Status in debian-installer package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in debian-installer source package in Xenial:
  Confirmed
Status in linux source package in Xenial:
  Confirmed

Bug description:
  The display will keep black screen after install 16.04.x via PXE(need
  use "Ctrl+Alt+F1" to change to terminal 1, then can see text mode
  screen)

  Quanta team is installing Xenial server using PXE boot.   After the
  installation, the console will show a black screen.   Hitting ctl-
  alt-f1 displays the text mode screen OK.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1646277/+subscriptions

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

[Kernel-packages] [Bug 1589008] Re: Bluetooth freezing video playback In Ubuntu/Kubuntu 16.04

2017-09-27 Thread Kai-Heng Feng

Does your wifi connect to a 2.4G AP?
Do you use some other wireless input devices?

These might interfere Bluetooth.

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

Title:
  Bluetooth freezing video playback In Ubuntu/Kubuntu 16.04

Status in linux package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  In 16.04 when a bluetooth audio device is connected it freezes video
  playback and also no sound comes from online audio only streams. Issue
  does not exist with a wired headset.

  This issue does not exist with 15.10. All updates have been installed
  on 16.04 including backports but they have not fixed the issue.

  It is not browser specific and not website specific.

  It is not hardware specific as it affects my laptop with an intel 7260
  card and my pc with an intel 8260 card.

  The issue exists on both ubuntu and kubuntu 16.04.

  I have reported it on the ubuntu support forums and after
  investigation a moderator noticed changed in the kernel from 4.4 and
  4.2 that may becausing the issue and asked me to file a bug report.

  The ubuntu forum thread can be found here.
  http://ubuntuforums.org/showthread.php?t=2326672

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-23-generic 4.4.0-23.41
  ProcVersionSignature: Ubuntu 4.4.0-23.41-generic 4.4.10
  Uname: Linux 4.4.0-23-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  stephen1435 F pulseaudio
   /dev/snd/controlC0:  stephen1435 F pulseaudio
  CurrentDesktop: KDE
  Date: Fri Jun  3 23:50:00 2016
  HibernationDevice: RESUME=UUID=78e7aefc-d517-4c58-836f-a90f0b6017c6
  InstallationDate: Installed on 2016-05-06 (28 days ago)
  InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: MSI MS-7978
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-23-generic.efi.signed 
root=UUID=bccf2ca7-4e23-412a-ba10-7a3f915270dd ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-23-generic N/A
   linux-backports-modules-4.4.0-23-generic  N/A
   linux-firmware1.157
  SourcePackage: linux
  UpgradeStatus: Upgraded to xenial on 2016-06-03 (0 days ago)
  dmi.bios.date: 05/16/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: C.60
  dmi.board.asset.tag: Default string
  dmi.board.name: H170 GAMING M3 (MS-7978)
  dmi.board.vendor: MSI
  dmi.board.version: 2.0
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 2.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrC.60:bd05/16/2016:svnMSI:pnMS-7978:pvr2.0:rvnMSI:rnH170GAMINGM3(MS-7978):rvr2.0:cvnMSI:ct3:cvr2.0:
  dmi.product.name: MS-7978
  dmi.product.version: 2.0
  dmi.sys.vendor: MSI

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

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

[Kernel-packages] [Bug 1720042] Re: linux-aws: 4.4.0-1038.47 -proposed tracker

2017-09-27 Thread Brad Figg

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

** Description changed:

  This bug is for tracking the 4.4.0-1038.47 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: 1718149
+ kernel-stable-phase-changed:Thursday, 28. September 2017 03:03 UTC
+ kernel-stable-phase:Packaging

** Description changed:

  This bug is for tracking the 4.4.0-1038.47 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: 1718149
- kernel-stable-phase-changed:Thursday, 28. September 2017 03:03 UTC
- kernel-stable-phase:Packaging
+ phase: Packaging

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

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

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  Confirmed
Status in Kernel SRU Workflow prepare-package-meta series:
  New
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow snap-publish series:
  New
Status in Kernel SRU Workflow snap-qa-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:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-aws package in Ubuntu:
  Confirmed

Bug description:
  This bug is for tracking the 4.4.0-1038.47 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: 1718149
  phase: Packaging

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

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

[Kernel-packages] [Bug 1589008] Re: Bluetooth freezing video playback In Ubuntu/Kubuntu 16.04

2017-09-27 Thread Jason Gambrel

The other very strange part is that the longer I play audio through the
internal speakers, the longer bluetooth plays before the problem arises.
If I only play a few seconds through the internal speakers, I only get a
few minutes of bluetooth.  Longer through internal, longer through
bluetooth.  I hope this helps.

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

Title:
  Bluetooth freezing video playback In Ubuntu/Kubuntu 16.04

Status in linux package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  In 16.04 when a bluetooth audio device is connected it freezes video
  playback and also no sound comes from online audio only streams. Issue
  does not exist with a wired headset.

  This issue does not exist with 15.10. All updates have been installed
  on 16.04 including backports but they have not fixed the issue.

  It is not browser specific and not website specific.

  It is not hardware specific as it affects my laptop with an intel 7260
  card and my pc with an intel 8260 card.

  The issue exists on both ubuntu and kubuntu 16.04.

  I have reported it on the ubuntu support forums and after
  investigation a moderator noticed changed in the kernel from 4.4 and
  4.2 that may becausing the issue and asked me to file a bug report.

  The ubuntu forum thread can be found here.
  http://ubuntuforums.org/showthread.php?t=2326672

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-23-generic 4.4.0-23.41
  ProcVersionSignature: Ubuntu 4.4.0-23.41-generic 4.4.10
  Uname: Linux 4.4.0-23-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  stephen1435 F pulseaudio
   /dev/snd/controlC0:  stephen1435 F pulseaudio
  CurrentDesktop: KDE
  Date: Fri Jun  3 23:50:00 2016
  HibernationDevice: RESUME=UUID=78e7aefc-d517-4c58-836f-a90f0b6017c6
  InstallationDate: Installed on 2016-05-06 (28 days ago)
  InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: MSI MS-7978
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-23-generic.efi.signed 
root=UUID=bccf2ca7-4e23-412a-ba10-7a3f915270dd ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-23-generic N/A
   linux-backports-modules-4.4.0-23-generic  N/A
   linux-firmware1.157
  SourcePackage: linux
  UpgradeStatus: Upgraded to xenial on 2016-06-03 (0 days ago)
  dmi.bios.date: 05/16/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: C.60
  dmi.board.asset.tag: Default string
  dmi.board.name: H170 GAMING M3 (MS-7978)
  dmi.board.vendor: MSI
  dmi.board.version: 2.0
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 2.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrC.60:bd05/16/2016:svnMSI:pnMS-7978:pvr2.0:rvnMSI:rnH170GAMINGM3(MS-7978):rvr2.0:cvnMSI:ct3:cvr2.0:
  dmi.product.name: MS-7978
  dmi.product.version: 2.0
  dmi.sys.vendor: MSI

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

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

[Kernel-packages] [Bug 1719970] Re: linux-aws: 4.4.0-1037.46 -proposed tracker

2017-09-27 Thread Brad Figg

** Description changed:

  This bug is for tracking the 4.4.0-1037.46 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: 1716613

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

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

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

Bug description:
  This bug is for tracking the 4.4.0-1037.46 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: 1716613

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

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

[Kernel-packages] [Bug 1589008] Re: Bluetooth freezing video playback In Ubuntu/Kubuntu 16.04

2017-09-27 Thread Jason Gambrel

Sorry to report that bug still persists. Took longer to show up though.
Was able to watch video for about 15 min. Slowly started losing sync
between audio and video, then eventually video freezes. Unable to
resume normal playback even after reboot. Able to resume if I play
video through built in speakers for a time then switch back to
bluetooth. After about 15 minutes, problem resumes, again until I play
audio through built in speakers.

Hope this info helps.

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

Title:
Bluetooth freezing video playback In Ubuntu/Kubuntu 16.04

Status in linux package in Ubuntu:
Confirmed
Status in pulseaudio package in Ubuntu:
Confirmed

Bug description:
In 16.04 when a bluetooth audio device is connected it freezes video
playback and also no sound comes from online audio only streams. Issue
does not exist with a wired headset.

This issue does not exist with 15.10. All updates have been installed
on 16.04 including backports but they have not fixed the issue.

It is not browser specific and not website specific.

It is not hardware specific as it affects my laptop with an intel 7260
card and my pc with an intel 8260 card.

The issue exists on both ubuntu and kubuntu 16.04.

I have reported it on the ubuntu support forums and after
investigation a moderator noticed changed in the kernel from 4.4 and
4.2 that may becausing the issue and asked me to file a bug report.

The ubuntu forum thread can be found here.
http://ubuntuforums.org/showthread.php?t=2326672

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-23-generic 4.4.0-23.41
ProcVersionSignature: Ubuntu 4.4.0-23.41-generic 4.4.10
Uname: Linux 4.4.0-23-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: stephen1435 F pulseaudio
/dev/snd/controlC0: stephen1435 F pulseaudio
CurrentDesktop: KDE
Date: Fri Jun 3 23:50:00 2016
HibernationDevice: RESUME=UUID=78e7aefc-d517-4c58-836f-a90f0b6017c6
InstallationDate: Installed on 2016-05-06 (28 days ago)
InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
Lsusb:
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 003: ID 8087:0a2b Intel Corp.
Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: MSI MS-7978
ProcFB: 0 EFI VGA
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-23-generic.efi.signed
root=UUID=bccf2ca7-4e23-412a-ba10-7a3f915270dd ro quiet splash vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-4.4.0-23-generic N/A
linux-backports-modules-4.4.0-23-generic N/A
linux-firmware1.157
SourcePackage: linux
UpgradeStatus: Upgraded to xenial on 2016-06-03 (0 days ago)
dmi.bios.date: 05/16/2016
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: C.60
dmi.board.asset.tag: Default string
dmi.board.name: H170 GAMING M3 (MS-7978)
dmi.board.vendor: MSI
dmi.board.version: 2.0
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: MSI
dmi.chassis.version: 2.0
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvrC.60:bd05/16/2016:svnMSI:pnMS-7978:pvr2.0:rvnMSI:rnH170GAMINGM3(MS-7978):rvr2.0:cvnMSI:ct3:cvr2.0:
dmi.product.name: MS-7978
dmi.product.version: 2.0
dmi.sys.vendor: MSI

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

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

[Kernel-packages] [Bug 1720042] Re: linux-aws: 4.4.0-1038.47 -proposed tracker

** No longer affects: kernel-sru-workflow/snap-certification-testing

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

Title:
  linux-aws: 4.4.0-1038.47 -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-publish series:
  New
Status in Kernel SRU Workflow snap-qa-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:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-aws package in Ubuntu:
  Confirmed

Bug description:
  This bug is for tracking the 4.4.0-1038.47 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: 1718149

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

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

[Kernel-packages] [Bug 1718155] Re: linux-aws: 4.4.0-1036.45 -proposed tracker

*** This bug is a duplicate of bug 1720042 ***
https://bugs.launchpad.net/bugs/1720042

** This bug has been marked a duplicate of bug 1720042
   linux-aws: 4.4.0-1038.47 -proposed tracker

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

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

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

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

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

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

[Kernel-packages] [Bug 1719888] Re: kernel BUG at /build/linux-s_bACt/linux-4.13.0/drivers/usb/usbip/vhci_hcd.c:683!

Did the following:

1. install the latest daily build of artful 
(http://cdimage.ubuntu.com/daily-live/current/artful-desktop-amd64.iso) 26-sept
2. Install the latest mainline 4.14 from here 
linux-image-4.14.0-041400rc2-generic_4.14.0-041400rc2.201709242031_amd64 , 
headers all, generic)
3. It was a big issue to boot because apparmor seems to block most things like 
dhclient so its difficult to get an IP address. Needed to manually run dhclient 
after boot in terminal with this kernel

4. Ran my program (using xhost +) initially to get around a new sudo
restriction

5. Following bug occured (below)

Will keep investigating...

[  126.113573] [ cut here ]
[  126.113577] kernel BUG at 
/home/kernel/COD/linux/drivers/usb/usbip/vhci_hcd.c:683!
[  126.113584] invalid opcode:  [#1] SMP
[  126.113585] Modules linked in: uas usb_storage vhci_hcd usbip_core arc4 md4 
nls_utf8 cifs ccm fscache sb_edac coretemp crct10dif_pclmul crc32_pclmul 
ghash_clmulni_intel pcbc vmw_balloon aesni_intel aes_x86_64 crypto_simd 
glue_helper cryptd intel_rapl_perf joydev input_leds serio_raw shpchp i2c_piix4 
nfit mac_hid vmw_vsock_vmci_transport vsock vmw_vmci parport_pc ppdev lp 
parport ip_tables x_tables autofs4 hid_generic usbhid hid vmwgfx ttm 
drm_kms_helper mptspi mptscsih syscopyarea mptbase sysfillrect sysimgblt 
fb_sys_fops ahci psmouse libahci drm e1000 scsi_transport_spi pata_acpi
[  126.113622] CPU: 0 PID: 1802 Comm: usb-storage Not tainted 
4.14.0-041400rc2-generic #201709242031
[  126.113623] Hardware name: VMware, Inc. VMware Virtual Platform/440BX 
Desktop Reference Platform, BIOS 6.00 07/02/2015
[  126.113625] task: 8a863b28 task.stack: b44e81a74000
[  126.113632] RIP: 0010:vhci_urb_enqueue+0x2fa/0x4f0 [vhci_hcd]
[  126.113633] RSP: 0018:b44e81a77b60 EFLAGS: 00010206
[  126.113635] RAX: 0024 RBX: 8a8620e2e000 RCX: 8a85b235c098
[  126.113635] RDX: 0140 RSI: 8a85ec523e00 RDI: 8a8620e2e000
[  126.113636] RBP: b44e81a77bb8 R08: 0024 R09: 
[  126.113637] R10: b44e81a77cb8 R11: 1c40 R12: 0001
[  126.113638] R13: 8a85d1c82ce0 R14: 0001 R15: 8a85ec523e00
[  126.113639] FS:  () GS:8a868a20() 
knlGS:
[  126.113640] CS:  0010 DS:  ES:  CR0: 80050033
[  126.113641] CR2: 7fca70003ad0 CR3: 46d7d001 CR4: 003606f0
[  126.113698] DR0:  DR1:  DR2: 
[  126.113700] DR3:  DR6: fffe0ff0 DR7: 0400
[  126.113701] Call Trace:
[  126.113711]  usb_hcd_submit_urb+0xad/0xb70
[  126.113717]  ? schedule+0x2c/0x80
[  126.113719]  ? schedule_timeout+0x1f1/0x350
[  126.113724]  ? update_curr+0xf5/0x1b0
[  126.113726]  usb_submit_urb+0x22d/0x560
[  126.113728]  ? usb_alloc_urb+0x2a/0x30
[  126.113730]  usb_sg_wait+0xa0/0x190
[  126.113736]  usb_stor_bulk_transfer_sglist.part.1+0x67/0xc0 [usb_storage]
[  126.113748]  usb_stor_bulk_srb+0x4b/0x80 [usb_storage]
[  126.113753]  usb_stor_Bulk_transport+0x175/0x400 [usb_storage]
[  126.113755]  usb_stor_invoke_transport+0x3b/0x500 [usb_storage]
[  126.113758]  ? wait_for_completion_interruptible+0xb7/0x180
[  126.113761]  usb_stor_transparent_scsi_command+0xe/0x10 [usb_storage]
[  126.113763]  usb_stor_control_thread+0x1c7/0x280 [usb_storage]
[  126.113767]  kthread+0x125/0x140
[  126.113769]  ? usb_stor_disconnect+0xc0/0xc0 [usb_storage]
[  126.113770]  ? kthread_create_on_node+0x70/0x70
[  126.113772]  ret_from_fork+0x25/0x30
[  126.113773] Code: f1 48 89 fa 48 c7 c6 a0 6e 51 c0 48 c7 c7 20 8e 51 c0 e8 
ca 08 f9 de e9 5d fd ff ff 41 8b 87 88 00 00 00 85 c0 0f 84 67 fd ff ff <0f> 0b 
48 8b 7d d0 48 c7 c6 48 5d 51 c0 e8 c4 f3 0e df 4c 89 fe 
[  126.113791] RIP: vhci_urb_enqueue+0x2fa/0x4f0 [vhci_hcd] RSP: 
b44e81a77b60
[  126.113794] ---[ end trace 6e70660d8a09a8dd ]---
[  126.122875] audit: type=1400 audit(1506565321.693:181): apparmor="DENIED" 
operation=

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

Title:
  kernel BUG at /build/linux-
  s_bACt/linux-4.13.0/drivers/usb/usbip/vhci_hcd.c:683!

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  When using a usb flash disk via usbip it crashes with this bug

  ProblemType: KernelOops
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-12-generic 4.13.0-12.13
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  Annotation: Your system might become unstable now and might need to be 
restarted.
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Date: Wed Sep 27 06:24:09 2017
  Failure: oops
  InstallationDate: Installed on

[Kernel-packages] [Bug 1720042] Re: linux-aws: 4.4.0-1038.47 -proposed tracker

2017-09-27 Thread Launchpad Bug Tracker

Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  linux-aws: 4.4.0-1038.47 -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-certification-testing series:
  New
Status in Kernel SRU Workflow snap-publish series:
  New
Status in Kernel SRU Workflow snap-qa-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:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-aws package in Ubuntu:
  Confirmed

Bug description:
  This bug is for tracking the 4.4.0-1038.47 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: 1718149

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

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

[Kernel-packages] [Bug 1720042] Re: linux-aws: 4.4.0-1038.47 -proposed tracker

** Summary changed:

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

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

Title:
  linux-aws: 4.4.0-1038.47 -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-certification-testing series:
  New
Status in Kernel SRU Workflow snap-publish series:
  New
Status in Kernel SRU Workflow snap-qa-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:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-aws package in Ubuntu:
  Confirmed

Bug description:
  This bug is for tracking the 4.4.0-1038.47 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: 1718149

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

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

[Kernel-packages] [Bug 1720042] [NEW] linux-aws: 4.4.0-1038.47 -proposed tracker

Public bug reported:

This bug is for tracking the 4.4.0-1038.47 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: 1718149

** 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-certification-testing
 Importance: Medium
 Status: New

** Affects: kernel-sru-workflow/snap-publish
 Importance: Undecided
 Status: New

** Affects: kernel-sru-workflow/snap-qa-testing
 Importance: Undecided
 Status: New

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

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

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

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

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

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

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


** Tags: kernel-release-tracking-bug kernel-release-tracking-bug-live 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-certification-testing
   Importance: Undecided
   Status: New

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

** Also affects: kernel-sru-workflow/snap-qa-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

** 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 =>

[Kernel-packages] [Bug 1715271] Re: Middle button of trackpoint doesn't work

** Changed in: linux (Ubuntu Artful)
   Status: Fix Committed => In Progress

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

Title:
  Middle button of trackpoint doesn't work

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

Bug description:
  Middle button doesn't work on several Thinkpad laptops like E570,
  E475, E470, E575 and X1Carbon.

  When middle button fails to work, logs show:
  psmouse serio2: trackpoint: failed to get extended button data

  It fails to read out ext button info via PS2 command.
  Almost all the Thinkpad have 3 buttons, so set it to 3 button when it fails 
to read button info.

  And on Lenovo X1, there is a new version of trackpoint, add this ID
  for this new device.

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

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

[Kernel-packages] [Bug 1720041] Re: Add GuC firmware for Kabylake v9.14

2017-09-27 Thread AceLan Kao

commit d7fe1272a38777a41ce9d1df80f58ace2d9e3d27
Author: Anusha Srivatsa 
Date:   Tue Feb 7 09:52:56 2017 -0800

linux-firmware/i915: GuC firmware for Kabylake v9.14

This update includes (since v8.12):
 1. Sub-feature level control for power management features.
 2. Clean-up for power management interface.
 3. Bug Fix for multi context scheduler flag.

8.12 contained since v 5.1:
 1. Add per engine preemption support to scheduler
 2. Minor bug fixes
 3. Add support to log media reset count

Cc: Rodrigo Vivi 
Signed-off-by: Anusha Srivatsa 

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

Title:
  Add GuC firmware for Kabylake v9.14

Status in linux-firmware package in Ubuntu:
  In Progress

Bug description:
  SRU Justification

  Impact:
  On new platform, new firmwares are required.
  [3.647168] i915_bpo :00:02.0: Direct firmware load for 
i915/kbl_dmc_ver1.bin failed with error -2
  [3.647171] i915_bpo :00:02.0: Failed to load DMC firmware 
[https://01.org/linuxgraphics/intel-linux-graphics-firmwares], disabling 
runtime power management.

  Fix:
  Add new firmware files.

  Test case:
  Test with affected hw and with a kernel which has the driver update.

  Regression potential:
  These are new files, so no regressions are possible outside of that driver.

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

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

[Kernel-packages] [Bug 1720041] [NEW] Add GuC firmware for Kabylake v9.14

2017-09-27 Thread AceLan Kao

Public bug reported:

SRU Justification

Impact:
On new platform, new firmwares are required.
[3.647168] i915_bpo :00:02.0: Direct firmware load for 
i915/kbl_dmc_ver1.bin failed with error -2
[3.647171] i915_bpo :00:02.0: Failed to load DMC firmware 
[https://01.org/linuxgraphics/intel-linux-graphics-firmwares], disabling 
runtime power management.

Fix:
Add new firmware files.

Test case:
Test with affected hw and with a kernel which has the driver update.

Regression potential:
These are new files, so no regressions are possible outside of that driver.

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

** Changed in: linux-firmware (Ubuntu)
 Assignee: (unassigned) => AceLan Kao (acelankao)

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

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

Title:
  Add GuC firmware for Kabylake v9.14

Status in linux-firmware package in Ubuntu:
  In Progress

Bug description:
  SRU Justification

  Impact:
  On new platform, new firmwares are required.
  [3.647168] i915_bpo :00:02.0: Direct firmware load for 
i915/kbl_dmc_ver1.bin failed with error -2
  [3.647171] i915_bpo :00:02.0: Failed to load DMC firmware 
[https://01.org/linuxgraphics/intel-linux-graphics-firmwares], disabling 
runtime power management.

  Fix:
  Add new firmware files.

  Test case:
  Test with affected hw and with a kernel which has the driver update.

  Regression potential:
  These are new files, so no regressions are possible outside of that driver.

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

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

[Kernel-packages] [Bug 1719888] Re: kernel BUG at /build/linux-s_bACt/linux-4.13.0/drivers/usb/usbip/vhci_hcd.c:683!

It works fine with this build:

Linux ubuntu 4.12.0-11-generic #12-Ubuntu SMP Fri Aug 11 12:26:42 UTC
2017 x86_64 x86_64 x86_64 GNU/Linux

 
It might be a 4.13 thing as a lot of code was changed in usbip for that 
verison. Ill do more testing on 4.13 and let you know what i find..

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

Title:
  kernel BUG at /build/linux-
  s_bACt/linux-4.13.0/drivers/usb/usbip/vhci_hcd.c:683!

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  When using a usb flash disk via usbip it crashes with this bug

  ProblemType: KernelOops
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-12-generic 4.13.0-12.13
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  Annotation: Your system might become unstable now and might need to be 
restarted.
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Date: Wed Sep 27 06:24:09 2017
  Failure: oops
  InstallationDate: Installed on 2017-09-27 (0 days ago)
  InstallationMedia: Xubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170829.1)
  IwConfig:
   ens33 no wireless extensions.
   
   lono wireless extensions.
  MachineType: VMware, Inc. VMware Virtual Platform
  ProcFB: 0 svgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-12-generic 
root=UUID=33763e28-10a5-4446-afbd-8cb727ae9363 ro find_preseed=/preseed.cfg 
auto noprompt priority=critical locale=en_US quiet
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: kerneloops-daemon N/A
  RfKill:
   
  SourcePackage: linux
  Title: kernel BUG at 
/build/linux-s_bACt/linux-4.13.0/drivers/usb/usbip/vhci_hcd.c:683!
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/02/2015
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: 6.00
  dmi.board.name: 440BX Desktop Reference Platform
  dmi.board.vendor: Intel Corporation
  dmi.board.version: None
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 1
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd07/02/2015:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
  dmi.product.name: VMware Virtual Platform
  dmi.product.version: None
  dmi.sys.vendor: VMware, Inc.

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

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

[Kernel-packages] [Bug 1718936] Re: Can't boot Artful 17.10 live images on XPS 15 (9560)

2017-09-27 Thread Anmar Oueja

This bug shouldn't be fixed-released. Nothing got fixed. The live image
doesn't boot without the nouveau modeset kernel boot option. It
shouldn't be fixed until the live image boots without any tinkering.

** Changed in: linux (Ubuntu)
   Status: Fix Released => 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/1718936

Title:
  Can't boot Artful 17.10 live images on XPS 15 (9560)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I usually test Ubuntu beta releases. With Artful, I haven't been able
  to boot the image on my XPS 15 (9560) Dell laptop because the boot
  process stops half way.

  The boot proceeds properly if I pass the "nomodeset" kernel boot
  option but that won't work because there is no more hiDPI support and
  dual display doesn't work.

  This has been ongoing for several weeks, around the 4.12 kernel.
  Please fix it. It would be a shame for this product not to boot Artful
  out of the box.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-11-generic 4.13.0-11.12
  ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1
  Uname: Linux 4.13.0-11-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 1701 F pulseaudio
  CasperVersion: 1.384
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep 22 12:38:09 2017
  LiveMediaBuild: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170921)
  MachineType: Dell Inc. XPS 15 9560
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi 
file=/cdrom/preseed/username.seed boot=casper quiet splash --- nomodeset
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-11-generic N/A
   linux-backports-modules-4.13.0-11-generic  N/A
   linux-firmware 1.168
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/30/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.5.0
  dmi.board.name: 0JHP5H
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.5.0:bd08/30/2017:svnDellInc.:pnXPS159560:pvr:rvnDellInc.:rn0JHP5H:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 15 9560
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1715812] Re: Neighbour confirmation broken, breaks ARP cache aging

2017-09-27 Thread Daniel Axtens

Verified on Xenial and Zesty.

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

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

Title:
  Neighbour confirmation broken, breaks ARP cache aging

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

Bug description:
  [SRU Justification]

  [Impact]
  A host can lose access to another host whose MAC address changes if they have 
active connections to other hosts that share a route. The ARP cache does not 
time out as expected - instead the old MAC address is continuously reconfirmed.

  [Fix]
  Apply series [1], which changes the algorithm for neighbour confirmation.
  That is, from upstream:
  51ce8bd4d17a net: pending_confirm is not used anymore 
  0dec879f636f net: use dst_confirm_neigh for UDP, RAW, ICMP, L2TP 
  63fca65d0863 net: add confirm_neigh method to dst_ops 
  c3a2e8370534 tcp: replace dst_confirm with sk_dst_confirm 
  c86a773c7802 sctp: add dst_pending_confirm flag 
  4ff0620354f2 net: add dst_pending_confirm flag to skbuff 
  9b8805a32559 sock: add sk_dst_pending_confirm flag 

  [Test case]
  Create 3 real or virtual systems, all hooked up to a switch.
  One system needs an active-backup bond with fail_over_mac=1 num_grat_arp=0.

  Put all the systems in the same subnet, e.g. 192.168.200.0/24

  Call the system with the bond A, and the other two systems B and C.

  On B, run in 3 shells:
   - netperf -t TCP_RR to C
   - ping -f A
   - watch 'ip -s neigh show 192.168.200.0/24'

  On A, cause the bond to fail over.

  Observe that:

   - without the patches, B intermittently fails to notice the change in
  A's MAC address. This presents as the ping failing and not recovering,
  and the arp table showing the old mac address never timing out and
  never being replace with a new mac address.

   - with the patches, the arp cache times out and B sends another mac
  probe and detects A's new address.

  It helps to use taskset to put ping and netperf on the same CPU, or
  use single-CPU vms.

  See [2] for more details.

  [References]
  [2] Original report: 
https://www.mail-archive.com/netdev@vger.kernel.org/msg138762.html
  [1]: https://www.spinics.net/lists/linux-rdma/msg45907.html

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

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

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

--- Comment From cclau...@br.ibm.com 2017-09-27 16:47 EDT---
(In reply to comment #30)
> Attached is the ESL db update for Canonical's POWER SecureBoot signing key.
> It is signed with Canonical's KEK key, which will be provided to IBM out of
> band to ensure integrity of the delivery channel.

Thanks Andy and Vorlon for the attached files. The kernel appended
signature verified successfully.

We didn't test the Canonical-POWER-SB-20170926.esl.signed file yet.

Questions:

1) The certificate provided contains a 4096-bit key and it was signed
using sha512WithRSAEncryption. We had no problem to use it to verify the
kernel appended signature - the kernel crypto API supports 4096-bit RSA
keys. However, we don't have much space in our keystore and that's why
we prefer to use 2048-bit RSA keys, same as UEFI SecureBoot. Could the
Canonical-POWER-SB-20170926.esl.signed file be regenerated to contain a
certificate that contains a 2048-bit RSA key instead? The certificate
would be signed using sha256WithRSAEncryption.

2) We will need to put in the KEK a certificate that can be used to verify the 
signed ESL db updates provided by Canonical. How does Canonical have provided 
that for UEFI SecureBoot? certificate, ESL (not signed, since PK is not 
provided by Canonical)?
Currently, we are working on the code that will validate/process the 
authenticated variable updates. We will probably start testing it by the end of 
this year.

Thanks,
Claudio

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

Title:
  [17.10 FEAT] Sign POWER host/NV kernels

Status in Launchpad itself:
  Fix Committed
Status in The Ubuntu-power-systems project:
  In Progress
Status in linux package in Ubuntu:
  In Progress
Status in linux-signed package in Ubuntu:
  In Progress

Bug description:
  Feature Description:

  Sign POWER host and NV kernels with sign-file in anticipation of POWER
  secure boot.  Provide the  associated certificate.  Ideally it would
  be possible to reuse the UEFI shim private key and certificate used to
  sign and verify x86_64 kernels.  More details to follow.  Guest
  kernels will be addressed in a future separate feature request.

  
  Business Case: 

  As a system administrator I want to verify the integrity of my kernels
  so that I can prevent malicious kernels from being executed.

  Use Case:

  Signed POWER kernels will be validated by OPAL as OpenPOWER systems
  boot when keys are properly installed and the system is booted in
  secure mode.

  
  Test Case:

  Sign and install a POWER kernel on an OpenPOWER machine with a
  firmware level that supports secure boot.  Install a PK, distro KEK
  certificat, and distro DB certificate.  Boot the system and verify
  that it will boot the kernel.  Negative tests:  Separately remove the
  signature, install an usigned kernel, and modify the kernel image and
  test that the kernel will not boot.

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

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

[Kernel-packages] [Bug 1718936] Re: Can't boot Artful 17.10 live images on XPS 15 (9560)

2017-09-27 Thread Anmar Oueja

I just tested the "blacklist=nouveau modprobe.blacklist=nouveau" and the
"nouveau.modeset=0" separately and both of them the machine booted off
the USB stick. I had a live image running 4.12 kernel so I will test
today's images (with 4.13 kernel) and report back.

Here is  my dmidecode just in case anybody wants to confirm the type of
machine I am testing on especially that some of you couldn't boot it
with the above modeset mods to the kernel boot prompt.

# dmidecode 3.0
Getting SMBIOS data from sysfs.
SMBIOS 3.0.0 present.
Table at 0x000E.

Handle 0x, DMI type 0, 24 bytes
BIOS Information
Vendor: Dell Inc.
Version: 1.5.0
Release Date: 08/30/2017
Address: 0xF
Runtime Size: 64 kB
ROM Size: 16384 kB
Characteristics:
PCI is supported
PNP is supported
BIOS is upgradeable
BIOS shadowing is allowed
Boot from CD is supported
Selectable boot is supported
EDD is supported
Japanese floppy for NEC 9800 1.2 MB is supported (int 13h)
5.25"/1.2 MB floppy services are supported (int 13h)

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

Title:
  Can't boot Artful 17.10 live images on XPS 15 (9560)

Status in linux package in Ubuntu:
  Fix Released

Bug description:
  I usually test Ubuntu beta releases. With Artful, I haven't been able
  to boot the image on my XPS 15 (9560) Dell laptop because the boot
  process stops half way.

  The boot proceeds properly if I pass the "nomodeset" kernel boot
  option but that won't work because there is no more hiDPI support and
  dual display doesn't work.

  This has been ongoing for several weeks, around the 4.12 kernel.
  Please fix it. It would be a shame for this product not to boot Artful
  out of the box.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-11-generic 4.13.0-11.12
  ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1
  Uname: Linux 4.13.0-11-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 1701 F pulseaudio
  CasperVersion: 1.384
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep 22 12:38:09 2017
  LiveMediaBuild: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170921)
  MachineType: Dell Inc. XPS 15 9560
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi 
file=/cdrom/preseed/username.seed boot=casper quiet splash --- nomodeset
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-11-generic N/A
   linux-backports-modules-4.13.0-11-generic  N/A
   linux-firmware 1.168
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/30/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.5.0
  dmi.board.name: 0JHP5H
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.5.0:bd08/30/2017:svnDellInc.:pnXPS159560:pvr:rvnDellInc.:rn0JHP5H:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 15 9560
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 362875] Re: rt2x00usb_vendor_request: Error - Vendor Request 0x07 failed for offset

2017-09-27 Thread Ubuntu Foundations Team Bug Bot

The attachment "rt2x00usb.pat" seems to be a patch.  If it isn't, please
remove the "patch" flag from the attachment, remove the "patch" tag, and
if you are a member of the ~ubuntu-reviewers, unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by
~brian-murray, for any issues please contact him.]

** Tags added: patch

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

Title:
  rt2x00usb_vendor_request: Error - Vendor Request 0x07 failed for
  offset

Status in linux package in Ubuntu:
  Confirmed
Status in rt2x00 package in Ubuntu:
  Confirmed

Bug description:
  Binary package hint: linux-firmware

  Dear friends,

  [24225.012753] phy2 -> rt2x00usb_vendor_request: Error - Vendor Request 0x07 
failed for offset 0x308c with error -71.
  [24225.017901] phy2 -> rt2x00usb_vendor_request: Error - Vendor Request 0x06 
failed for offset 0x308c with error -71.
  [24225.022279] phy2 -> rt2x00usb_vendor_request: Error - Vendor Request 0x07 
failed for offset 0x308c with error -71.
  [24226.005773] phy2 -> rt2x00usb_vendor_request: Error - Vendor Request 0x07 
failed for offset 0x30c0 with error -71.
  [24226.011307] phy2 -> rt2x00usb_vendor_request: Error - Vendor Request 0x07 
failed for offset 0x30c4 with error -71.
  [24226.015147] phy2 -> rt2x00usb_vendor_request: Error - Vendor Request 0x07 
failed for offset 0x308c with error -71.
  [24226.020486] phy2 -> rt2x00usb_vendor_request: Error - Vendor Request 0x06 
failed for offset 0x308c with error -71.
  [24226.024151] phy2 -> rt2x00usb_vendor_request: Error - Vendor Request 0x07 
failed for offset 0x308c with error -71.
  [24227.003532] phy2 -> rt2x00usb_vendor_request: Error - Vendor Request 0x07 
failed for offset 0x30c0 with error -71.
  [24227.007269] phy2 -> rt2x00usb_vendor_request: Error - Vendor Request 0x07 
failed for offset 0x30c4 with error -71.
  [24227.020153] phy2 -> rt2x00usb_vendor_request: Error - Vendor Request 0x07 
failed for offset 0x308c with error -71.
  [24227.023895] phy2 -> rt2x00usb_vendor_request: Error - Vendor Request 0x06 
failed for offset 0x308c with error -71.
  [24227.027645] phy2 -> rt2x00usb_vendor_request: Error - Vendor Request 0x07 
failed for offset 0x308c with error -71.

  This is an example of the message I'm continually getting.

  ID 148f:2671 Ralink Technology, Corp. RT2601USB Wireless Adapter

  Many blessings.

  ProblemType: Bug
  Architecture: i386
  Dependencies:
   
  DistroRelease: Ubuntu 8.10
  Package: linux-restricted-modules None [modified: 
/var/lib/dpkg/info/linux-restricted-modules.list]
  ProcEnviron:
   SHELL=/bin/bash
   
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/X11R6/bin
   LANG=en_US.UTF-8
  SourcePackage: linux-meta
  Uname: Linux 2.6.27-7-generic i686

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

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

[Kernel-packages] [Bug 1685899] Re: [Ubuntu 17.04] - JFS related call traces and system enters xmon when rebooted after installation

2017-09-27 Thread Juerg Haefliger

*** This bug is a duplicate of bug 1708096 ***
https://bugs.launchpad.net/bugs/1708096

** This bug has been marked a duplicate of bug 1708096
   Ubuntu16.04.3 Installation fails for JFS file 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/1685899

Title:
  [Ubuntu 17.04] - JFS related call traces and system enters xmon when
  rebooted after installation

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

Bug description:
  Issue:
  
  JFS related call traces and system enters xmon when rebooted after 
installation 

  Steps to reproduce:
  -
  1 - Install Ubuntu 17.04 the system with 
   - prepboot
  - /root [JFS filesystem]
  - swap space

  2 -After installation when rebooted it gives out call traces like as
  below:

  [3.895246] Unable to handle kernel paging request for data at address 
0x
  [3.895278] Faulting instruction address: 0xd4c5df1c
  [3.895284] Oops: Kernel access of bad area, sig: 11 [#1]
  [3.895287] SMP NR_CPUS=2048 [3.895288] NUMA 
  [3.895290] pSeries
  [3.895292] Modules linked in: ip_tables x_tables autofs4 jfs ibmvscsi 
crc32c_vpmsum
  [3.895301] CPU: 30 PID: 923 Comm: ureadahead Not tainted 4.9.0-15-generic 
#16-Ubuntu
  [3.895304] task: c00381d3c800 task.stack: c00381fd
  [3.895307] NIP: d4c5df1c LR: d4c5deb0 CTR: 
c01279d0
  [3.895310] REGS: c00381fd3500 TRAP: 0300   Not tainted  
(4.9.0-15-generic)
  [3.895313] MSR: 8280b033 [
3.895322]   CR: 48008804  XER: 0001
  [3.895324] CFAR: c0008a60 DAR:  DSISR: 4000 
SOFTE: 1 
  GPR00: d4c5deb0 c00381fd3780 d4c78c28 c003802f40f0 
  GPR04: d4c6f6f0 d4c72b58 0563 d4c78c28 
  GPR08:  00180e97  d4c6a608 
  GPR12: c01279d0 cfb90e00   
  GPR16:     
  GPR20:     
  GPR24:  1000  d4c72b38 
  GPR28: 00180e97 f0e1d5c0 c003812af240 c003802f40b0 
  NIP [d4c5df1c] __get_metapage+0x204/0x6f0 [jfs]
  [3.895372] LR [d4c5deb0] __get_metapage+0x198/0x6f0 [jfs]
  [3.895374] Call Trace:
  [3.895378] [c00381fd3780] [d4c5de6c] 
__get_metapage+0x154/0x6f0 [jfs] (unreliable)
  [3.895384] [c00381fd3870] [d4c4c368] diRead+0x130/0x260 [jfs]
  [3.895388] [c00381fd3920] [d4c424f4] jfs_iget+0x6c/0x1e0 [jfs]
  [3.895393] [c00381fd3950] [d4c43adc] jfs_lookup+0xe4/0x100 
[jfs]
  [3.895398] [c00381fd3a80] [c032a120] lookup_slow+0xe0/0x240
  [3.895402] [c00381fd3b00] [c032e8a8] 
walk_component+0x2d8/0x3f0
  [3.895406] [c00381fd3b70] [c032eb94] 
link_path_walk+0x1d4/0x600
  [3.895409] [c00381fd3c00] [c0330c1c] path_openat+0xbc/0x480
  [3.895413] [c00381fd3c80] [c03328ac] do_filp_open+0xec/0x160
  [3.895417] [c00381fd3db0] [c031863c] do_sys_open+0x1cc/0x380
  [3.895421] [c00381fd3e30] [c000bd84] system_call+0x38/0xe0
  [3.895424] Instruction dump:
  [3.895426] 7909f00e 7fc9f214 3921 f93f0028 fbdf0030 e93d 71280800 
41820460 
  [3.895433] ebdd0030 41920034 e91d0008 e93f0038  811e 
80e70090 39080001 
  [3.895441] ---[ end trace c2aa9ba09ea05eac ]---
  [3.895443] 
  [4.088560] systemd-journald[925]: Received request to flush runtime 
journal from PID 1
  [4.362062] crypto_register_alg 'aes' = 0
  [4.362112] crypto_register_alg 'cbc(aes)' = 0
  [4.362150] crypto_register_alg 'ctr(aes)' = 0
  [4.362191] crypto_register_alg 'xts(aes)' = 0
  [4.366949] pseries_rng: Registering IBM pSeries RNG driver

  When I first connected to the LPAR, it was unresponsive so I restarted
  it from the HMC and surprisingly it came up to the login prompt and I
  logged into the shell. I proceeded to install the matching linux-
  image-4.10.0-15-generic-dbgsym_4.10.0-15.17_ppc64el.ddeb. However, the
  installation of the matching dbgsym wasn't as helpful as I wanted it
  to be. objdump, crash tool, or addr2line wouldn't give me the source
  line correspond to the NIP address.

  I then restarted the LPAR with xmon enabled and it would drop to xmon
  immediately after attempting to remount / and at the same location as
  before at __get_metapage+0x204/0x6f0 [jfs] and again with a
  dereference of 0x0 as the cause of the data exception

  0xd649df54 <__get_metapage+508>:ld  r8,8(r29)

[Kernel-packages] [Bug 1719970] Re: linux-aws: 4.4.0-1037.46 -proposed tracker

2017-09-27 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

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

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

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

Bug description:
  This bug is for tracking the 4.4.0-1037.46 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: 1716613

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

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

[Kernel-packages] [Bug 1706033] Re: [P9, Power NV][ WSP][Ubuntu 16.04.03] : perf hw breakpoint command results in call traces and system goes for reboot.

2017-09-27 Thread Stefan Bader

** Also affects: linux (Ubuntu Zesty)
   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/1706033

Title:
  [P9, Power NV][ WSP][Ubuntu 16.04.03] : perf hw breakpoint command
  results in call traces and system goes for reboot.

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

Bug description:
  == Comment: #0 - Shriya R. Kulkarni <> - 2017-06-14 04:38:16 ==
  Problem Description :
  =
   
  While running perftool - testsuite, the perf hw breakpoint fails and it 
result in call traces , hence system goes for reboot .

  Machine details :
  ==
  System : P9 , WSP , Bare metal.
  OS : Ubuntu 16.04.03
  uname -a : Linux ltc-wspoon3 4.10.0-23-generic #25~16.04.1-Ubuntu SMP Fri Jun 
9 10:43:34 UTC 2017 ppc64le ppc64le ppc64le GNU/Linux

  Steps to reproduce:
  
  1. Install perf.
  2. git clone perftool-testsuite.
  https://github.com/rfmvh/perftool-testsuite
  3. Do make.
  4. Test fails at step : -- [ FAIL ] -- perf_stat :: test_hw_breakpoints :: 
kspace address execution mem:0xc035c020:x (command exitcode + output 
regexp parsing
  and call trace is seen as system goes for reboot.

  Call traces :
  ===

  ubuntu@ltc-wspoon3:~$ [1602513.518414] Unable to handle kernel paging request 
for data at address 0xc135d3b8
  [1602513.518553] Faulting instruction address: 0xc02869bc
  [1602513.518694] Oops: Kernel access of bad area, sig: 11 [#1]
  [1602513.518782] SMP NR_CPUS=2048 
  [1602513.518784] NUMA 
  [1602513.518842] PowerNV
  [1602513.518922] Modules linked in: vmx_crypto ofpart ipmi_powernv 
cmdlinepart ipmi_devintf powernv_flash ipmi_msghandler ibmpowernv opal_prd mtd 
at24 nvmem_core uio_pdrv_genirq uio autofs4 ast i2c_algo_bit drm_kms_helper 
syscopyarea sysfillrect sysimgblt fb_sys_fops crc32c_vpmsum ttm drm tg3 ahci 
libahci
  [1602513.519399] CPU: 27 PID: 4069 Comm: sysctl Not tainted 4.10.0-22-generic 
#24
  [1602513.519524] task: c000203968c42c00 task.stack: c00020396571
  [1602513.519624] NIP: c02869bc LR: c03f7348 CTR: 
c0286990
  [1602513.519747] REGS: c000203965713a40 TRAP: 0300   Not tainted  
(4.10.0-22-generic)
  [1602513.519876] MSR: 90009033 
  [1602513.519889]   CR: 22002448  XER: 
  [1602513.520058] CFAR: c03f7344 DAR: c135d3b8 DSISR: 0040 
SOFTE: 1 
  [1602513.520058] GPR00: c03f7348 c000203965713cc0 c145d100 
c134af00 
  [1602513.520058] GPR04:  4ee50300 c000203965713d20 
c000203965713e00 
  [1602513.520058] GPR08:  c135d100  
c0b71020 
  [1602513.520058] GPR12: c0286990 c7b4f300  
 
  [1602513.520058] GPR16:    
 
  [1602513.520058] GPR20:    
0001 
  [1602513.520058] GPR24: 3fffc542f5a0 0400 c000203965713e00 
4ee50300 
  [1602513.520058] GPR28: c134af00  c03fee038800 
 
  [1602513.521280] NIP [c02869bc] dirty_ratio_handler+0x2c/0x90
  [1602513.521374] LR [c03f7348] proc_sys_call_handler+0x138/0x1c0
  [1602513.521481] Call Trace:
  [1602513.521526] [c000203965713cc0] [c000203965713d00] 0xc000203965713d00 
(unreliable)
  [1602513.521655] [c000203965713d00] [c03f7348] 
proc_sys_call_handler+0x138/0x1c0
  [1602513.521797] [c000203965713d70] [c03436ec] __vfs_read+0x3c/0x70
  [1602513.521907] [c000203965713d90] [c034516c] vfs_read+0xbc/0x1b0
  [1602513.522016] [c000203965713de0] [c0346dd8] SyS_read+0x68/0x110
  [1602513.522112] [c000203965713e30] [c000b184] system_call+0x38/0xe0
  [1602513.522243] Instruction dump:
  [1602513.522303] 6042 3c4c011d 38426770 7c0802a6 6000 7c0802a6 
fbc1fff0 fbe1fff8 
  [1602513.522445] f8010010 f821ffc1 3d22fff0 7c9f2378  4be66da9 
6000 3d22fff0 
  [1602513.522564] ---[ end trace 17c76e13e641d3c6 ]---
  [1602513.522657] 

  It goes for reboot :

  After booting to Ubuntu , I see series of call traces.

  Ubuntu 16.04.2 LTS ltc-wspoon3 hvc0

  ltc-wspoon3 login: [ 3476.626263] Unable to handle kernel paging request for 
data at address 0xc13ad438
  [ 3476.626422] Faulting instruction address: 0xc029a140
  [ 3476.626537] Oops: Kernel access of bad area, sig: 11 [#1]
  [ 3476.626615] SMP NR_CPUS=2048 
  [ 3476.626616] NUMA 
  [ 3476.626673] PowerNV
  [ 3476.626746] Modules linked in: ipmi_powernv at24 ipmi_devintf nvmem_core 
ipmi_msghandler ofpart cmdlinepart powernv_flash mtd opal_prd vmx_crypto 
ibmpowernv uio_pdrv_genirq uio autofs4 ast

[Kernel-packages] [Bug 933443] Re: [Kbuntu 11.10] Poor boot performance after installing cpufrequtils!

2017-09-27 Thread Phillip Susi

11.10 reached end of life long ago and is no longer supported.  Are you
still having this issue on a current release?


** Package changed: cpufreqd (Ubuntu) => cpufrequtils (Ubuntu)

** Changed in: cpufrequtils (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/933443

Title:
  [Kbuntu 11.10] Poor boot performance after installing cpufrequtils!

Status in cpufrequtils package in Ubuntu:
  Incomplete
Status in linux package in Ubuntu:
  Invalid

Bug description:
  After installing cpufrequtils I noticed some error message. Does error 
message also occurs in /var/log/boot.log:
  FATAL: Error inserting p4_clockmod 
(/lib/modules/3.0.0-16-generic/kernel/drivers/cpufreq/p4-clockmod.ko): No such 
device
   * Stopping Failsafe Boot Delay 
  FATAL: Error inserting pcc_cpufreq 
(/lib/modules/3.0.0-16-generic/kernel/drivers/cpufreq/pcc-cpufreq.ko): No such 
device
   * Stopping anac(h)ronistic cron
  FATAL: Error inserting e_powersaver 
(/lib/modules/3.0.0-16-generic/kernel/drivers/cpufreq/e_powersaver.ko): No such 
device
   * Starting CPU interrupts balancing daemon 

  I noticed after installing cpufrequtils it also effected the
  bootspeed/time when I restarted the laptop. In a bad way.

  cpufreq-info
  cpufrequtils 007: cpufreq-info (C) Dominik Brodowski 2004-2009
  Report errors and bugs to cpuf...@vger.kernel.org, please.
  analyzing CPU 0:
driver: powernow-k8
CPUs which run at the same hardware frequency: 0 1
CPUs which need to have their frequency coordinated by software: 0 1
maximum transition latency: 107 us.
hardware limits: 800 MHz - 1.60 GHz
available frequency steps: 1.60 GHz, 800 MHz
available cpufreq governors: conservative, ondemand, userspace, powersave, 
performance
current policy: frequency should be within 800 MHz and 1.60 GHz.
The governor "ondemand" may decide which speed to use
within this range.
current CPU frequency is 800 MHz.
cpufreq stats: 1.60 GHz:16,63%, 800 MHz:83,37%  (697)
  analyzing CPU 1:
driver: powernow-k8
CPUs which run at the same hardware frequency: 0 1
CPUs which need to have their frequency coordinated by software: 0 1
maximum transition latency: 107 us.
hardware limits: 800 MHz - 1.60 GHz
available frequency steps: 1.60 GHz, 800 MHz
available cpufreq governors: conservative, ondemand, userspace, powersave, 
performance
current policy: frequency should be within 800 MHz and 1.60 GHz.
The governor "ondemand" may decide which speed to use
within this range.
current CPU frequency is 800 MHz.
cpufreq stats: 1.60 GHz:16,63%, 800 MHz:83,37%  (697)
  --- 
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
  ApportVersion: 1.23-0ubuntu4
  Architecture: i386
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: NVidia [HDA NVidia], device 0: ALC883 Analog [ALC883 Analog]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  hem1676 F pulseaudio
  CRDA: Error: [Errno 2] Filen eller katalogen finns inte
  Card0.Amixer.info:
   Card hw:0 'NVidia'/'HDA NVidia at 0xc000 irq 19'
 Mixer name : 'Realtek ALC883'
 Components : 'HDA:10ec0883,17348205,0012 
HDA:14f12bfa,14f10001,0009'
 Controls  : 26
 Simple ctrls  : 15
  DistroRelease: Ubuntu 11.10
  HibernationDevice: RESUME=UUID=0b9d0972-c5e3-488a-96a9-ff235052bd5a
  InstallationMedia: Kubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111012)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 002 Device 002: ID 093a:2510 Pixart Imaging, Inc. Optical Mouse
  MachineType: FUJITSU SIEMENS AMILO Pa 1538
  NonfreeKernelModules: nvidia
  Package: linux (not installed)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.0.0-16-generic 
root=UUID=aee60c94-7ae7-4989-9342-7f31dca60d6c ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.0.0-16.28-generic 3.0.17
  RelatedPackageVersions:
   linux-restricted-modules-3.0.0-16-generic N/A
   linux-backports-modules-3.0.0-16-generic  N/A
   linux-firmware1.60
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  Tags:  oneiric
  Uname: Linux 3.0.0-16-generic i686
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
  dmi.bios.date: 10/24/08
  dmi.bios.vendor: Phoenix
  dmi.bios.version: 1.1Q-5821-8A20
  dmi.board.name: PTB50
  dmi.board.vendor: FUJITSU SIEMENS
  dmi.board.version: 0.6
  dmi.chassis.asset.tag: Tag 12345
  dmi.chassis.type: 10
  dmi.chassis.vendor: FUJITSU SIEMENS
  dmi.chassis.version:

[Kernel-packages] [Bug 1719297] Re: [17.10 FEAT] KVM: CPU Model z14

2017-09-27 Thread Frank Heimes

** Changed in: ubuntu-z-systems
   Status: In Progress => Fix Committed

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

Title:
  [17.10 FEAT] KVM: CPU Model z14

Status in Ubuntu on IBM z Systems:
  Fix Committed
Status in linux package in Ubuntu:
  Fix Committed
Status in qemu package in Ubuntu:
  Fix Released

Bug description:
  Kernel team, could you please consider cherrypicking the below commit
  into the linux kernel for Artful?

  commit b697e435aeee99b7f5b2d8f8dbb51f791be99b16
  Author: Jason J. Herne 
  Date:   Fri Feb 24 10:01:30 2017 -0500

  KVM: s390: Support Configuration z/Architecture Mode

  
  This is related to the following feature:
  Enable non transparent hardware functions for KVM guests  (crypto CPACF 
functions)
  Commit-ID will follow

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

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

[Kernel-packages] [Bug 1718578] Re: Support setting I2C_TIMEOUT via ioctl for i2c-designware

2017-09-27 Thread Stefan Bader

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

Title:
  Support setting I2C_TIMEOUT via ioctl for i2c-designware

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Xenial:
  New

Bug description:
  SRU Justification

  [Impact]
  The timeout value in i2c-designware is hardcoded. Userspace tool may want to 
change the timeout value via ioctl I2C_TIMEOUT, but it doesn't work for 
i2c-designware.

  [Test Case]
  Change the timeout value via ioctl I2C_TIMEOUT. Nothing happened.
  With the patch, timeout value for i2c-designware will be updated correctly.

  [Regression Potential]
  Minimal. The change only applies to a specific driver, i2c-designware. Also, 
it has minimal code change.

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

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

[Kernel-packages] [Bug 1719970] Re: linux-aws: 4.4.0-1037.46 -proposed tracker

** 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) => Thadeu Lima de 
Souza Cascardo (cascardo)

** 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) => Thadeu Lima de 
Souza Cascardo (cascardo)

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

Title:
  linux-aws: 4.4.0-1037.46 -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-certification-testing series:
  New
Status in Kernel SRU Workflow snap-publish series:
  New
Status in Kernel SRU Workflow snap-qa-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:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-aws package in Ubuntu:
  New
Status in linux-aws source package in Xenial:
  New

Bug description:
  This bug is for tracking the 4.4.0-1037.46 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: 1716613

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

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

[Kernel-packages] [Bug 1719970] Re: linux-aws: 4.4.0-1037.46 -proposed tracker

2017-09-27 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/1719970

Title:
  linux-aws: 4.4.0-1037.46 -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-certification-testing series:
  New
Status in Kernel SRU Workflow snap-publish series:
  New
Status in Kernel SRU Workflow snap-qa-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:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-aws package in Ubuntu:
  New
Status in linux-aws source package in Xenial:
  New

Bug description:
  This bug is for tracking the 4.4.0-1037.46 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: 1716613

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

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

[Kernel-packages] [Bug 1719733] Re: stale file handle when restarting ntp on overlayfs (maas)

2017-09-27 Thread Witold Krecicki

I hit the same problem with current
(http://images.maas.io/ephemeral-v3/daily/artful/amd64/20170926/)
version.

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

Title:
  stale file handle when restarting ntp on overlayfs (maas)

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

Bug description:
  MAAS is currently failing to deploy artful.

  [0.00] Kernel command line: nomodeset
  iscsi_target_name=iqn.2004-05.com.ubuntu:maas:ephemeral-ubuntu-
  ppc64el-ga-17.10-artful-daily iscsi_target_ip=10.245.71.3
  iscsi_target_port=3260 iscsi_initiator=wichita ip=wichita:BOOTIF
  ip6=off ro root=/dev/disk/by-path/ip-10.245.71.3:3260-iscsi-
  iqn.2004-05.com.ubuntu:maas:ephemeral-ubuntu-ppc64el-ga-17.10-artful-
  daily-lun-1 overlayroot=tmpfs overlayroot_cfgdisk=disabled
  cc:{'datasource_list': ['MAAS']}end_cc cloud-config-
  url=http://10.245.71.3:5240/MAAS/metadata/latest/by-id/node-45f9009a-
  0bc4-11e6-9882-00163e5b6994/?op=get_preseed apparmor=0
  log_host=10.245.71.3 log_port=514 --- console=hvc0 BOOTIF=01-6c-ae-
  8b-01-e9-00^M

  ...

  [   60.064994] cloud-init[4805]: ERROR: ld.so: object 'libeatmydata.so' from 
LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.^M
  [   60.216965] cloud-init[4805]: Created symlink 
/etc/systemd/system/multi-user.target.wants/ntp.service → 
/lib/systemd/system/ntp.service.^M
  [   60.837682] cloud-init[4805]: Processing triggers for libc-bin 
(2.26-0ubuntu1) ...^M
  [   60.851733] cloud-init[4805]: Processing triggers for ureadahead 
(0.100.0-20) ...^M
  [   61.003403] cloud-init[4805]: Processing triggers for systemd 
(234-2ubuntu10) ...^M
  [   61.183944] cloud-init[4805]: dpkg: error: error removing old backup file 
'/var/lib/dpkg/status-old': Stale file handle^M
  [   62.202113] cloud-init[4805]: E: Sub-process /usr/bin/dpkg returned an 
error code (2)^M
  @

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-11-generic 4.13.0-11.12
  ProcVersionSignature: User Name 4.13.0-11.12-generic 4.13.1
  Uname: Linux 4.13.0-11-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Sep 26 20:32 seq
   crw-rw 1 root audio 116, 33 Sep 26 20:32 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  Date: Tue Sep 26 20:33:41 2017
  Ec2AMI: ami-0181
  Ec2AMIManifest: FIXME
  Ec2AvailabilityZone: nova
  Ec2InstanceType: m1.small
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lsusb:
   Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: OpenStack Foundation OpenStack Nova
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-11-generic 
root=LABEL=cloudimg-rootfs ro console=tty1 console=ttyS0
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-11-generic N/A
   linux-backports-modules-4.13.0-11-generic  N/A
   linux-firmware N/A
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/01/2014
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: 1.10.1-1ubuntu1~cloud0
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-i440fx-zesty
  dmi.modalias: 
dmi:bvnSeaBIOS:bvr1.10.1-1ubuntu1~cloud0:bd04/01/2014:svnOpenStackFoundation:pnOpenStackNova:pvr15.0.2:cvnQEMU:ct1:cvrpc-i440fx-zesty:
  dmi.product.family: Virtual Machine
  dmi.product.name: OpenStack Nova
  dmi.product.version: 15.0.2
  dmi.sys.vendor: OpenStack Foundation

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

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

[Kernel-packages] [Bug 1718388] Re: Fix OpenNSL GPL bugs found by CoverityScan static analysis

2017-09-27 Thread Stefan Bader

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

Title:
  Fix OpenNSL GPL bugs found by CoverityScan static analysis

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

Bug description:
  Static analysis on the ubuntu/opennsl drivers in Xenial have picked up
  various bugs. These need fixing.

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

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

[Kernel-packages] [Bug 1719970] [NEW] linux-aws: 4.4.0-1037.46 -proposed tracker

Public bug reported:

This bug is for tracking the 4.4.0-1037.46 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: 1716613

** 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: Thadeu Lima de Souza Cascardo (cascardo)
 Status: In Progress

** Affects: kernel-sru-workflow/prepare-package-meta
 Importance: Medium
 Assignee: Thadeu Lima de Souza Cascardo (cascardo)
 Status: In Progress

** 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
 Status: New

** Affects: kernel-sru-workflow/snap-publish
 Importance: Undecided
 Status: New

** Affects: kernel-sru-workflow/snap-qa-testing
 Importance: Undecided
 Status: New

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

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

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

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

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

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

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

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


** Tags: kernel-release-tracking-bug kernel-release-tracking-bug-live 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-certification-testing
   Importance: Undecided
   Status: New

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

** Also affects: kernel-sru-workflow/snap-qa-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

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

** Changed in: kernel-sru-workflow

[Kernel-packages] [Bug 1719297] Re: [17.10 FEAT] KVM: CPU Model z14

2017-09-27 Thread Seth Forshee

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

Title:
  [17.10 FEAT] KVM: CPU Model z14

Status in Ubuntu on IBM z Systems:
  In Progress
Status in linux package in Ubuntu:
  Fix Committed
Status in qemu package in Ubuntu:
  Fix Released

Bug description:
  Kernel team, could you please consider cherrypicking the below commit
  into the linux kernel for Artful?

  commit b697e435aeee99b7f5b2d8f8dbb51f791be99b16
  Author: Jason J. Herne 
  Date:   Fri Feb 24 10:01:30 2017 -0500

  KVM: s390: Support Configuration z/Architecture Mode

  
  This is related to the following feature:
  Enable non transparent hardware functions for KVM guests  (crypto CPACF 
functions)
  Commit-ID will follow

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

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

[Kernel-packages] [Bug 1719297] Re: [17.10 FEAT] KVM: CPU Model z14

2017-09-27 Thread Seth Forshee

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

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

** Changed in: linux (Ubuntu)
 Assignee: Ubuntu Kernel Team (ubuntu-kernel-team) => Seth Forshee 
(sforshee)

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

Title:
  [17.10 FEAT] KVM: CPU Model z14

Status in Ubuntu on IBM z Systems:
  In Progress
Status in linux package in Ubuntu:
  Triaged
Status in qemu package in Ubuntu:
  Fix Released

Bug description:
  Kernel team, could you please consider cherrypicking the below commit
  into the linux kernel for Artful?

  commit b697e435aeee99b7f5b2d8f8dbb51f791be99b16
  Author: Jason J. Herne 
  Date:   Fri Feb 24 10:01:30 2017 -0500

  KVM: s390: Support Configuration z/Architecture Mode

  
  This is related to the following feature:
  Enable non transparent hardware functions for KVM guests  (crypto CPACF 
functions)
  Commit-ID will follow

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

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

[Kernel-packages] [Bug 1719297] Re: [17.10 FEAT] KVM: CPU Model z14

** Description changed:

- Enable non transparent hardware functions for KVM guests  (crypto CPACF
- functions)
+ Kernel team, could you please consider cherrypicking the below commit
+ into the linux kernel for Artful?
  
+ commit b697e435aeee99b7f5b2d8f8dbb51f791be99b16
+ Author: Jason J. Herne 
+ Date:   Fri Feb 24 10:01:30 2017 -0500
+ 
+ KVM: s390: Support Configuration z/Architecture Mode
+ 
+ 
+ This is related to the following feature:
+ Enable non transparent hardware functions for KVM guests  (crypto CPACF 
functions)
  Commit-ID will follow

** Information type changed from Private to Public

** Changed in: linux (Ubuntu)
 Assignee: Skipper Bug Screeners (skipper-screen-team) => Ubuntu Kernel 
Team (ubuntu-kernel-team)

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

Title:
  [17.10 FEAT] KVM: CPU Model z14

Status in Ubuntu on IBM z Systems:
  In Progress
Status in linux package in Ubuntu:
  New
Status in qemu package in Ubuntu:
  Fix Released

Bug description:
  Kernel team, could you please consider cherrypicking the below commit
  into the linux kernel for Artful?

  commit b697e435aeee99b7f5b2d8f8dbb51f791be99b16
  Author: Jason J. Herne 
  Date:   Fri Feb 24 10:01:30 2017 -0500

  KVM: s390: Support Configuration z/Architecture Mode

  
  This is related to the following feature:
  Enable non transparent hardware functions for KVM guests  (crypto CPACF 
functions)
  Commit-ID will follow

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

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

[Kernel-packages] [Bug 1704929] Re: Repeating "can't open /dev/ttyX: No such device or address" messages during installation

2017-09-27 Thread Frank Heimes

** Changed in: ubuntu-z-systems
   Importance: Undecided => Medium

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

Title:
  Repeating "can't open /dev/ttyX: No such device or address" messages
  during installation

Status in Ubuntu on IBM z Systems:
  Confirmed
Status in console-setup package in Ubuntu:
  Incomplete
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  [Impact]

  console-setup continuously tries to open /dev/tty[1-6] on s390x, when
  such consoles do not exist on s390x.

  This can be seen on boot in the output from the initramfs, and during
  the installer.

  [Cuase]

  It seems to me that the postinst of the console-setup is incorrect for
  s390, since on s390 Linux tty[1-6] do not exist in any modes (LPAR,
  z/VM, KVM)

  [Solution]
  I do not know what ACTIVE_CONSOLES should be set as, my guess is to set it 
to... "guess". Usually it should be slcp, but that depends on which consoles 
are configured/activated in the given KVM.

  [Testcase]
  On boot, scroll all the messages and makesure there are no error messages 
about inability to open /dev/tty*

  [Original Bug Report]

  During the installation (z/VM guest and KVM virtual machine) of Ubuntu
  Server 16.04.1 (and 16.04.2) repeating messages of the form:

  "
  Select and install software ... 10% can't open /dev/tty4: No such device or 
address
  can't open /dev/tty2: No such device or address
  can't open /dev/tty3: No such device or address
  can't open /dev/tty4: No such device or address
  can't open /dev/tty2: No such device or address
  can't open /dev/tty3: No such device or address
  can't open /dev/tty2: No such device or address
  can't open /dev/tty4: No such device or address
  can't open /dev/tty4: No such device or address
  can't open /dev/tty3: No such device or address
  can't open /dev/tty2: No such device or address
  can't open /dev/tty2: No such device or address
  can't open /dev/tty3: No such device or address
  ... 20% can't open /dev/tty4: No such device or address
  can't open /dev/tty2: No such device or address
  can't open /dev/tty3: No such device or address
  ... 30%... 40% can't open /dev/tty3: No such device or address
  can't open /dev/tty4: No such device or address
  can't open /dev/tty2: No such device or address
  ... 50% can't open /dev/tty3: No such device or address
  can't open /dev/tty4: No such device or address
  can't open /dev/tty2: No such device or address
  ... 60% can't open /dev/tty2: No such device or address
  can't open /dev/tty3: No such device or address
  can't open /dev/tty4: No such device or address
  can't open /dev/tty2: No such device or address
  ...
  Finishing the installation ... 13%... 22%... 31% can't open /dev/tty3: No 
such device or address
  can't open /dev/tty2: No such device or address
  can't open /dev/tty4: No such device or address
  ... 40%... 50%... 63%... 72%... 81% can't open /dev/tty4: No such device or 
address
  can't open /dev/tty2: No such device or address
  can't open /dev/tty3: No such device or address
  ... 90% The system is going down NOW
   Sent SIGTERM to all processes
   Sent SIGKILL to all processes
   Requesting system reboot
  01: HCPGSP2629I The virtual machine is placed in CP mode due to a SIGP stop 
CPU 00.
  02: HCPGSP2629I The virtual machine is placed in CP mode due to a SIGP stop 
CPU 00.
  03: HCPGSP2629I The virtual machine is placed in CP mode due to a SIGP stop 
CPU 00.
  00 Storage cleared - system reset.
  00 zIPL ..
  "

  They start to occur when the software gets installed:

  "Select and install software ... 10% can't open /dev/tty4: No such
  device or address"

  And only stop with the final system reboot at the end of the
  installation.

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

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

[Kernel-packages] [Bug 1719844] Re: kernel BUG at /build/linux-Fk60NP/linux-4.10.0/include/linux/swapops.h:129!

2017-09-27 Thread Richard

This was a fresh install on a machine that I have just acquired - so I
have no previous kernel version that I can say worked.

Happy to try the latest upstream kernel.

I'll get it set up and report back.

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

Title:
  kernel BUG at /build/linux-
  Fk60NP/linux-4.10.0/include/linux/swapops.h:129!

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Full system freeze under almost no load.

  Running google-chrome and Pycharm.

  Traceback in syslog:
  Sep 27 11:06:36 toto kernel: [66558.227374] [ cut here 
]
  Sep 27 11:06:36 toto kernel: [66558.227450] kernel BUG at 
/build/linux-Fk60NP/linux-4.10.0/include/linux/swapops.h:129!
  Sep 27 11:06:36 toto kernel: [66558.227472] invalid opcode:  [#1] SMP
  Sep 27 11:06:36 toto kernel: [66558.227483] Modules linked in: btrfs xor 
raid6_pq ufs qnx4 hfsplus hfs minix ntfs msdos jfs xfs libcrc32c cpuid joydev 
hid_logitech_hidpp hid_logitech_dj intel_rapl x86_pkg_temp_thermal 
intel_powerclamp coretemp snd_hda_codec_realtek snd_hda_codec_generic kvm_intel 
kvm snd_hda_intel irqbypass snd_hda_codec crct10dif_pclmul snd_hda_core 
snd_hwdep cr
  c32_pclmul snd_pcm ghash_clmulni_intel snd_seq_midi pcbc snd_seq_midi_event 
snd_rawmidi snd_seq aesni_intel aes_x86_64 snd_seq_device snd_timer dcdbas 
crypto_simd glue_helper cryptd intel_cstate intel_rapl_perf serio_raw 
input_leds snd lpc_ich soundcore shpchp mac_hid mei_me mei parport_pc ppdev lp 
parport ip_tables x_tables autofs4 hid_generic usbhid hid amdkfd amd_iommu_v2 
rade
  on i2c_algo_bit ttm drm_kms_helper syscopyarea sysfillrect psmouse sysimgblt
  Sep 27 11:06:36 toto kernel: [66558.227676]  fb_sys_fops e1000e ahci e1000 
drm libahci ptp pps_core fjes video
  Sep 27 11:06:36 toto kernel: [66558.227699] CPU: 2 PID: 26031 Comm: chrome 
Not tainted 4.10.0-19-generic #21-Ubuntu
  Sep 27 11:06:36 toto kernel: [66558.227718] Hardware name: Dell Inc. OptiPlex 
990/06D7TR, BIOS A03 04/11/2011
  Sep 27 11:06:36 toto kernel: [66558.227737] task: 9afc1ae52d00 
task.stack: c1ebc808
  Sep 27 11:06:36 toto kernel: [66558.227756] RIP: 
0010:__migration_entry_wait+0x16a/0x180
  Sep 27 11:06:36 toto kernel: [66558.227770] RSP: :c1ebc8083d68 
EFLAGS: 00010246
  Sep 27 11:06:36 toto kernel: [66558.227784] RAX: 000fc0048078 RBX: 
f50cc31604b0 RCX: f50cc31604b0
  Sep 27 11:06:36 toto kernel: [66558.227803] RDX: 0001 RSI: 
9afcc58120a0 RDI: f50cc18f0500
  Sep 27 11:06:36 toto kernel: [66558.227821] RBP: c1ebc8083d80 R08: 
9afd233ab640 R09: 9afd233ab640
  Sep 27 11:06:36 toto kernel: [66558.227839] R10: 0008 R11: 
7f7d4d3403b0 R12: f50cc18f0500
  Sep 27 11:06:36 toto kernel: [66558.227857] R13: 3e063c14 R14: 
c1ebc8083e30 R15: 9afc274e24b0
  Sep 27 11:06:36 toto kernel: [66558.227876] FS:  7f7d4d8e5b00() 
GS:9afd2928() knlGS:
  Sep 27 11:06:36 toto kernel: [66558.227897] CS:  0010 DS:  ES:  CR0: 
80050033
  Sep 27 11:06:36 toto kernel: [66558.227912] CR2: 2e6ce3c146e8 CR3: 
27486000 CR4: 000406e0
  Sep 27 11:06:36 toto kernel: [66558.227930] Call Trace:
  Sep 27 11:06:36 toto kernel: [66558.227939]  migration_entry_wait+0x74/0x80
  Sep 27 11:06:36 toto kernel: [66558.227953]  do_swap_page+0x5b3/0x770
  Sep 27 11:06:36 toto kernel: [66558.227963]  ? do_swap_page+0xb/0x770
  Sep 27 11:06:36 toto kernel: [66558.227974]  handle_mm_fault+0x873/0x1360
  Sep 27 11:06:36 toto kernel: [66558.227987]  __do_page_fault+0x23e/0x4e0
  Sep 27 11:06:36 toto kernel: [66558.227998]  do_page_fault+0x22/0x30
  Sep 27 11:06:36 toto kernel: [66558.228010]  page_fault+0x28/0x30
  Sep 27 11:06:36 toto kernel: [66558.228020] RIP: 0033:0x5596fffb1b95
  Sep 27 11:06:36 toto kernel: [66558.228030] RSP: 002b:7ffc942f4f20 
EFLAGS: 00010283
  Sep 27 11:06:36 toto kernel: [66558.228044] RAX: 001e RBX: 
0002acb7ffd8 RCX: 0007
  Sep 27 11:06:36 toto kernel: [66558.228062] RDX:  RSI: 
000a RDI: 00a0
  Sep 27 11:06:36 toto kernel: [66558.228081] RBP: 2e6ce3c146e0 R08: 
c3ff R09: 0002
  Sep 27 11:06:36 toto kernel: [66558.228099] R10: 0008 R11: 
7f7d4d3403b0 R12: 00a0
  Sep 27 11:06:36 toto kernel: [66558.228118] R13: 7ffc942f5580 R14: 
2e6ce329e128 R15: 2e6ce367cdc0
  Sep 27 11:06:36 toto kernel: [66558.228136] Code: ff ff ff 4c 89 e7 e8 96 a2 
f8 ff e9 3c ff ff ff 85 d2 0f 84 2a ff ff ff 8d 4a 01 89 d0 f0 41 0f b1 4d 00 
39 d0 74 81 89 c2 eb e5 <0f> 0b 4c 89 e7 e8 0c fb f9 ff eb b8 4c 8d 60 ff 4c 8d 
68 1b eb 
  Sep 27 11:06:36 toto kernel: [66558.228199] RIP: 
__migration_entry_wait+0x16a/0x180 RSP: c1ebc8083d68
  Sep 27 11:06:36 toto kernel:

[Kernel-packages] [Bug 362875] Re: rt2x00usb_vendor_request: Error - Vendor Request 0x07 failed for offset

2017-09-27 Thread Jay Foster

I have experienced this bug on a non Ubuntu system for some time. I
spent some time comparing the SparkLAN DPO driver source with the main
line kernel driver source and tried a couple of changes.

1) There were some places missing a lock (this change did not affect this bug,
however).
2) The DPO driver performed the 32-bit register writes as two 16-bit single
write commands instead of one four byte multi-write command. I suspected that
this might lead to race conditions setting the registers (not atomic) which was
causing the Wi-Fi chip to hang. I thought it possible that the Wi-Fi chip
firmware might buffer the two 16-bit single writes and then perform a single
32-bit write to the register, thus making it atomic. I asked SparkLAN about
this, but received no reply. Note that the DPO driver performs the 32-bit
register reads as a single four byte multi-read, just like the main line kernel
driver does.

I tested the following patch and the problem went away, either because
it fixes the issue or it changes the timing to cover it up. Perhaps a
distinction without a difference.

** Attachment added: "rt2x00usb.pat"

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/362875/+attachment/4957754/+files/rt2x00usb.pat

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

Title:
rt2x00usb_vendor_request: Error - Vendor Request 0x07 failed for
offset

Status in linux package in Ubuntu:
Confirmed
Status in rt2x00 package in Ubuntu:
Confirmed

Bug description:
Binary package hint: linux-firmware

Dear friends,

[24225.012753] phy2 -> rt2x00usb_vendor_request: Error - Vendor Request 0x07
failed for offset 0x308c with error -71.
[24225.017901] phy2 -> rt2x00usb_vendor_request: Error - Vendor Request 0x06
failed for offset 0x308c with error -71.
[24225.022279] phy2 -> rt2x00usb_vendor_request: Error - Vendor Request 0x07
failed for offset 0x308c with error -71.
[24226.005773] phy2 -> rt2x00usb_vendor_request: Error - Vendor Request 0x07
failed for offset 0x30c0 with error -71.
[24226.011307] phy2 -> rt2x00usb_vendor_request: Error - Vendor Request 0x07
failed for offset 0x30c4 with error -71.
[24226.015147] phy2 -> rt2x00usb_vendor_request: Error - Vendor Request 0x07
failed for offset 0x308c with error -71.
[24226.020486] phy2 -> rt2x00usb_vendor_request: Error - Vendor Request 0x06
failed for offset 0x308c with error -71.
[24226.024151] phy2 -> rt2x00usb_vendor_request: Error - Vendor Request 0x07
failed for offset 0x308c with error -71.
[24227.003532] phy2 -> rt2x00usb_vendor_request: Error - Vendor Request 0x07
failed for offset 0x30c0 with error -71.
[24227.007269] phy2 -> rt2x00usb_vendor_request: Error - Vendor Request 0x07
failed for offset 0x30c4 with error -71.
[24227.020153] phy2 -> rt2x00usb_vendor_request: Error - Vendor Request 0x07
failed for offset 0x308c with error -71.
[24227.023895] phy2 -> rt2x00usb_vendor_request: Error - Vendor Request 0x06
failed for offset 0x308c with error -71.
[24227.027645] phy2 -> rt2x00usb_vendor_request: Error - Vendor Request 0x07
failed for offset 0x308c with error -71.

This is an example of the message I'm continually getting.

ID 148f:2671 Ralink Technology, Corp. RT2601USB Wireless Adapter

Many blessings.

ProblemType: Bug
Architecture: i386
Dependencies:

DistroRelease: Ubuntu 8.10
Package: linux-restricted-modules None [modified:
/var/lib/dpkg/info/linux-restricted-modules.list]
ProcEnviron:
SHELL=/bin/bash

PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/X11R6/bin
LANG=en_US.UTF-8
SourcePackage: linux-meta
Uname: Linux 2.6.27-7-generic i686

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

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

--- Comment From cls...@us.ibm.com 2017-09-27 12:27 EDT---
*** Bug 159257 has been marked as a duplicate of 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/1718107

Title:
  task-size-overrun test will hang on IBM s390x zKVM / zVM

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

Bug description:
  This issue does not exist on other amd64 / i386 / arm64 boxes.

  Steps:
  1. Clone git://kernel.ubuntu.com/ubuntu/autotest-client-tests
  2. Untar libhugetlbfs/libhugetlbfs-2.20.tar.gz
  3. Run `sudo BUILDTYPE=NATIVEONLY make check` in the extracted 
libhugetlbfs-2.20 directory
  4. Hit Ctrl + C to terminate it

  From the output you will see it get stuck:
  truncate_above_4GB (1024K: 64):   PASS
  brk_near_huge (1024K: 64):brk_near_huge: malloc.c:2427: sysmalloc: 
Assertion `(old_top == initial_top (av) && old_size == 0) || ((unsigned long) 
(old_size) >= MINSIZE && prev_inuse (old_top) && ((unsigned long) old_end & 
(pagesize - 1)) == 0)' failed.

  task-size-overrun (1024K: 64):

  From the syslog you can see brk_near_huge has crashed:
  Sep 19 07:28:25 s2lp6g004 rsyslogd-2007: action 'action 10' suspended, next 
retry is Tue Sep 19 07:29:55 2017 [v8.16.0 try http://www.rsyslog.com/e/2007 ]
  Sep 19 07:28:36 s2lp6g004 AutotestCrashHandler: Application brk_near_huge, 
PID 10474 crashed
  Sep 19 07:28:36 s2lp6g004 AutotestCrashHandler: Writing core files to 
['/home/ubuntu/autotest/client/results/default/libhugetlbfs/debug/crash.brk_near_huge.10474']
  Sep 19 07:28:36 s2lp6g004 AutotestCrashHandler: Could not determine from 
which application core file 
/home/ubuntu/autotest/client/results/default/libhugetlbfs/debug/crash.brk_near_huge.10474/core
 is from

  After hitting Ctrl + C to interrupt, kernel trace could be found in syslog:
  Sep 19 07:30:02 s2lp6g004 kernel: [11224.325504] report_user_fault: 35 
callbacks suppressed
  Sep 19 07:30:02 s2lp6g004 kernel: [11224.325507] User process fault: 
interruption code 0010 ilc:3 in stack_grow_into_huge[12f88+4000]
  Sep 19 07:30:02 s2lp6g004 kernel: [11224.325520] Failing address: 
03ffe72fe000 TEID: 03ffe72fe400
  Sep 19 07:30:02 s2lp6g004 kernel: [11224.325521] Fault in primary space mode 
while using user ASCE.
  Sep 19 07:30:02 s2lp6g004 kernel: [11224.325523] AS:551701c7 
R3:48d88007 S:0020
  Sep 19 07:30:02 s2lp6g004 kernel: [11224.325527] CPU: 0 PID: 10481 Comm: 
stack_grow_into Tainted: P  DO4.13.0-11-generic #12-Ubuntu
  Sep 19 07:30:02 s2lp6g004 kernel: [11224.325527] Hardware name: IBM 2964 N63 
400 (KVM/Linux)
  Sep 19 07:30:02 s2lp6g004 kernel: [11224.325528] task: 6245 
task.stack: 62b3c000
  Sep 19 07:30:02 s2lp6g004 kernel: [11224.325529] User PSW : 070530018000 
00012f8819a8
  Sep 19 07:30:02 s2lp6g004 kernel: [11224.325530]R:0 T:1 IO:1 EX:1 
Key:0 M:1 W:0 P:1 AS:0 CC:3 PM:0 RI:0 EA:3
  Sep 19 07:30:02 s2lp6g004 kernel: [11224.325531] User GPRS: 02001c51e2f8 
f000  0004
  Sep 19 07:30:02 s2lp6g004 kernel: [11224.325531]03fff72fe5c0 
 0003 000157806000
  Sep 19 07:30:02 s2lp6g004 kernel: [11224.325532]fff0 
0010 03fff700 03fff72fe520
  Sep 19 07:30:02 s2lp6g004 kernel: [11224.325532]02001c426000 
0003 00012f8819a2 03ffe72fe518
  Sep 19 07:30:02 s2lp6g004 kernel: [11224.325540] User Code: 00012f881996: 
e548b0a80001mvghi   168(%r11),1
  Sep 19 07:30:02 s2lp6g004 kernel: [11224.325540]00012f88199c: 
c0e5fc86brasl   %r14,12f8812a8
  Sep 19 07:30:02 s2lp6g004 kernel: [11224.325540]   #00012f8819a2: 
c2f41008slgfi   %r15,268435464
  Sep 19 07:30:02 s2lp6g004 kernel: [11224.325540]   >00012f8819a8: 
e54cf0a1mvhi160(%r15),1
  Sep 19 07:30:02 s2lp6g004 kernel: [11224.325540]00012f8819ae: 
4110f0a0la  %r1,160(%r15)
  Sep 19 07:30:02 s2lp6g004 kernel: [11224.325540]00012f8819b2: 
ec1afff8a065clgrj   %r1,%r10,10,12f8819a2
  Sep 19 07:30:02 s2lp6g004 kernel: [11224.325540]00012f8819b8: 
b24f0010ear %r1,%a0
  Sep 19 07:30:02 s2lp6g004 kernel: [11224.325540]00012f8819bc: 
eb11002dsllg%r1,%r1,32
  Sep 19 07:30:02 s2lp6g004 kernel: [11224.325549] Last Breaking-Event-Address:
  Sep 19 07:30:02 s2lp6g004 kernel: [11224.325552]  [<02001c7f26e8>] 
0x2001c7f26e8
  Sep 19 07:30:02 s2lp6g004 kernel: [11224.325562] Process 
10481(stack_grow_into) has RLIMIT_CORE set to 1
  Sep 19 07:30:02 s2lp6g004 kernel: [11224.325563] Aborting core

  Please find attachment for a more detailed syslog and core dump file.

  ProblemType: Bug

[Kernel-packages] [Bug 1704929] Re: Repeating "can't open /dev/ttyX: No such device or address" messages during installation

--- Comment From heinz-werner_se...@de.ibm.com 2017-09-27 12:20 EDT---
Will be covered by original Launchpad bug

** Tags added: architecture-s39064 bugnameltc-159373 severity-high
targetmilestone-inin1710

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

Title:
  Repeating "can't open /dev/ttyX: No such device or address" messages
  during installation

Status in Ubuntu on IBM z Systems:
  Confirmed
Status in console-setup package in Ubuntu:
  Incomplete
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  [Impact]

  console-setup continuously tries to open /dev/tty[1-6] on s390x, when
  such consoles do not exist on s390x.

  This can be seen on boot in the output from the initramfs, and during
  the installer.

  [Cuase]

  It seems to me that the postinst of the console-setup is incorrect for
  s390, since on s390 Linux tty[1-6] do not exist in any modes (LPAR,
  z/VM, KVM)

  [Solution]
  I do not know what ACTIVE_CONSOLES should be set as, my guess is to set it 
to... "guess". Usually it should be slcp, but that depends on which consoles 
are configured/activated in the given KVM.

  [Testcase]
  On boot, scroll all the messages and makesure there are no error messages 
about inability to open /dev/tty*

  [Original Bug Report]

  During the installation (z/VM guest and KVM virtual machine) of Ubuntu
  Server 16.04.1 (and 16.04.2) repeating messages of the form:

  "
  Select and install software ... 10% can't open /dev/tty4: No such device or 
address
  can't open /dev/tty2: No such device or address
  can't open /dev/tty3: No such device or address
  can't open /dev/tty4: No such device or address
  can't open /dev/tty2: No such device or address
  can't open /dev/tty3: No such device or address
  can't open /dev/tty2: No such device or address
  can't open /dev/tty4: No such device or address
  can't open /dev/tty4: No such device or address
  can't open /dev/tty3: No such device or address
  can't open /dev/tty2: No such device or address
  can't open /dev/tty2: No such device or address
  can't open /dev/tty3: No such device or address
  ... 20% can't open /dev/tty4: No such device or address
  can't open /dev/tty2: No such device or address
  can't open /dev/tty3: No such device or address
  ... 30%... 40% can't open /dev/tty3: No such device or address
  can't open /dev/tty4: No such device or address
  can't open /dev/tty2: No such device or address
  ... 50% can't open /dev/tty3: No such device or address
  can't open /dev/tty4: No such device or address
  can't open /dev/tty2: No such device or address
  ... 60% can't open /dev/tty2: No such device or address
  can't open /dev/tty3: No such device or address
  can't open /dev/tty4: No such device or address
  can't open /dev/tty2: No such device or address
  ...
  Finishing the installation ... 13%... 22%... 31% can't open /dev/tty3: No 
such device or address
  can't open /dev/tty2: No such device or address
  can't open /dev/tty4: No such device or address
  ... 40%... 50%... 63%... 72%... 81% can't open /dev/tty4: No such device or 
address
  can't open /dev/tty2: No such device or address
  can't open /dev/tty3: No such device or address
  ... 90% The system is going down NOW
   Sent SIGTERM to all processes
   Sent SIGKILL to all processes
   Requesting system reboot
  01: HCPGSP2629I The virtual machine is placed in CP mode due to a SIGP stop 
CPU 00.
  02: HCPGSP2629I The virtual machine is placed in CP mode due to a SIGP stop 
CPU 00.
  03: HCPGSP2629I The virtual machine is placed in CP mode due to a SIGP stop 
CPU 00.
  00 Storage cleared - system reset.
  00 zIPL ..
  "

  They start to occur when the software gets installed:

  "Select and install software ... 10% can't open /dev/tty4: No such
  device or address"

  And only stop with the final system reboot at the end of the
  installation.

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

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

[Kernel-packages] [Bug 1719844] Re: kernel BUG at /build/linux-Fk60NP/linux-4.10.0/include/linux/swapops.h:129!

Did this issue start happening after an update/upgrade?  Was there a
prior kernel version where you were not having this particular problem?

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

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

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

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


Thanks in advance.

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

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

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

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

Title:
  kernel BUG at /build/linux-
  Fk60NP/linux-4.10.0/include/linux/swapops.h:129!

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Full system freeze under almost no load.

  Running google-chrome and Pycharm.

  Traceback in syslog:
  Sep 27 11:06:36 toto kernel: [66558.227374] [ cut here 
]
  Sep 27 11:06:36 toto kernel: [66558.227450] kernel BUG at 
/build/linux-Fk60NP/linux-4.10.0/include/linux/swapops.h:129!
  Sep 27 11:06:36 toto kernel: [66558.227472] invalid opcode:  [#1] SMP
  Sep 27 11:06:36 toto kernel: [66558.227483] Modules linked in: btrfs xor 
raid6_pq ufs qnx4 hfsplus hfs minix ntfs msdos jfs xfs libcrc32c cpuid joydev 
hid_logitech_hidpp hid_logitech_dj intel_rapl x86_pkg_temp_thermal 
intel_powerclamp coretemp snd_hda_codec_realtek snd_hda_codec_generic kvm_intel 
kvm snd_hda_intel irqbypass snd_hda_codec crct10dif_pclmul snd_hda_core 
snd_hwdep cr
  c32_pclmul snd_pcm ghash_clmulni_intel snd_seq_midi pcbc snd_seq_midi_event 
snd_rawmidi snd_seq aesni_intel aes_x86_64 snd_seq_device snd_timer dcdbas 
crypto_simd glue_helper cryptd intel_cstate intel_rapl_perf serio_raw 
input_leds snd lpc_ich soundcore shpchp mac_hid mei_me mei parport_pc ppdev lp 
parport ip_tables x_tables autofs4 hid_generic usbhid hid amdkfd amd_iommu_v2 
rade
  on i2c_algo_bit ttm drm_kms_helper syscopyarea sysfillrect psmouse sysimgblt
  Sep 27 11:06:36 toto kernel: [66558.227676]  fb_sys_fops e1000e ahci e1000 
drm libahci ptp pps_core fjes video
  Sep 27 11:06:36 toto kernel: [66558.227699] CPU: 2 PID: 26031 Comm: chrome 
Not tainted 4.10.0-19-generic #21-Ubuntu
  Sep 27 11:06:36 toto kernel: [66558.227718] Hardware name: Dell Inc. OptiPlex 
990/06D7TR, BIOS A03 04/11/2011
  Sep 27 11:06:36 toto kernel: [66558.227737] task: 9afc1ae52d00 
task.stack: c1ebc808
  Sep 27 11:06:36 toto kernel: [66558.227756] RIP: 
0010:__migration_entry_wait+0x16a/0x180
  Sep 27 11:06:36 toto kernel: [66558.227770] RSP: :c1ebc8083d68 
EFLAGS: 00010246
  Sep 27 11:06:36 toto kernel: [66558.227784] RAX: 000fc0048078 RBX: 
f50cc31604b0 RCX: f50cc31604b0
  Sep 27 11:06:36 toto kernel: [66558.227803] RDX: 0001 RSI: 
9afcc58120a0 RDI: f50cc18f0500
  Sep 27 11:06:36 toto kernel: [66558.227821] RBP: c1ebc8083d80 R08: 
9afd233ab640 R09: 9afd233ab640
  Sep 27 11:06:36 toto kernel: [66558.227839] R10: 0008 R11: 
7f7d4d3403b0 R12: f50cc18f0500
  Sep 27 11:06:36 toto kernel: [66558.227857] R13: 3e063c14 R14: 
c1ebc8083e30 R15: 9afc274e24b0
  Sep 27 11:06:36 toto kernel: [66558.227876] FS:  7f7d4d8e5b00() 
GS:9afd2928() knlGS:
  Sep 27 11:06:36 toto kernel: [66558.227897] CS:  0010 DS:  ES:  CR0: 
80050033
  Sep 27 11:06:36 toto kernel: [66558.227912] CR2: 2e6ce3c146e8 CR3: 
27486000 CR4: 000406e0
  Sep 27 11:06:36 toto kernel: [66558.227930] Call Trace:
  Sep 27 11:06:36 toto kernel: [66558.227939]  migration_entry_wait+0x74/0x80
  Sep 27 11:06:36 toto kernel: [66558.227953]  do_swap_page+0x5b3/0x770
  Sep 27 11:06:36 toto kernel: [66558.227963]  ? do_swap_page+0xb/0x770
  Sep 27 11:06:36 toto kernel: [66558.227974]  handle_mm_fault+0x873/0x1360
  Sep 27 11:06:36 toto kernel: [66558.227987]  __do_page_fault+0x23e/0x4e0
  Sep 27 11:06:36 toto kernel: [66558.227998]  do_page_fault+0x22/0x30
  Sep 27 11:06:36 toto kernel: [66558.228010]  page_fault+0x28/0x30
  Sep 27 11:06:36 toto kernel: [66558.228020] RIP: 0033:0x5596fffb1b95
  Sep 27 11:06:36 toto kernel: [66558.228030] RSP: 002b:7ffc942f4f20 
EFLAGS: 00010283
  Sep 27 11:06:36 toto kernel: [66558.228044] RAX: 001e RBX: 
0002acb7ffd8 RCX: 0007
  Sep 27 11:06:36 toto kernel: [66558.228062] RDX:  RSI: 
000a RDI: 00a0
  Sep 27 11:06:36 toto kernel: [66558.228081] RBP: 2e6ce3c146e0 R08: 
c3ff R09:

[Kernel-packages] [Bug 1719795] Re: Dell 7140 avarage power consumption in idle increased by 1.3-1.5 times due to events by INT3432

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

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

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

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


Thanks in advance.

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

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

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

Title:
  Dell 7140 avarage power consumption in idle increased by 1.3-1.5 times
  due to events by INT3432

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  New

Bug description:
  On Dell Venue 11 Pro 7140 average power consumption in idle increased
  by 1.3-1.5 times due to events coming from INT343A. According to
  powertop since Linux 4.10 INT3432:00 generate around two hundred
  events on average, in /sys/devices/pci:00/INT3432:00/i2c-6 there
  is two devices: INT343A and SMO91D0. AFAIK INT343A is rt286.

  With Linux 4.9.0-4.9.45, Linux 4.11.0-4.11.12 in idle there is around 100 
wakeups per second in sum, battery discharge rate around 3-3.5 Watts per second.
  But with Linux 4.9.46-4.9.51, Linux 4.10.0-4.10.17, Linux 4.12.0rc1-4.13.3 - 
around 300 wakeups per second on average, due to events coming from INT3432:00. 
With Linux 4.13.3 battery discharge rate around 4.5 Watts per second.
  Probably some commit was backported to Linux 4.9 between .45 and .46 releases.
  I have no idea why issue is not reproducible on any Linux 4.11 release I 
tried.

  Sometimes INT3432 events rate fall from two hundred to one hundred for
  shorts period of time (for example I observe this right now on Linux
  4.10.0 while removing/installing packages).

  Message like this sometimes appear in dmesg:
  [  731.226730] i2c_hid i2c-SMO91D0:00: i2c_hid_get_input: incomplete report 
(53/13568)

  Complete dmesg with Linux 4.13.3 is attached.

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

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

[Kernel-packages] [Bug 1719853] Re: Plantronics P610 does not support sample rate reading

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

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

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

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


Thanks in advance.

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

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

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

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

Title:
  Plantronics P610 does not support sample rate reading

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  As per
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1622763/comments/29
  and https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1709282 , I
  believe the USB ID 0x047F 0xC02F needs to be added to quirks.c in
  order for me to use my Plantronics P610. Thanks!

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

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

[Kernel-packages] [Bug 1715368] Re: Broadcom NXE controller Cumulus devices ID's are missing in 16.04.03 'kernel-fixed-upstream'

We don't generally pull in a new version of a driver to fix a bug.
There is a document that describes the SRU process[0].


For this bug, what we would want to do is find the specific commit in the newer 
driver that fixes the bug, then SRU it to the 16.04.03 kernel.

To identify the commit that fixes this, we would need to perform a
"Reverse" kernel bisect[1], which is why I asked for the testing of
various kernel versions in comment #6.

It looks like you tested those kernels per comment #9.  Is it correct
that the 4.5 kernel with  version: 1.0.0 does not have the bug?  If that
is the case, we can bisect between 4.4 and 4.5.


[0] https://wiki.ubuntu.com/StableReleaseUpdates

[1] https://wiki.ubuntu.com/Kernel/KernelBisection

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

Title:
  Broadcom NXE controller Cumulus devices ID's are missing in 16.04.03
  'kernel-fixed-upstream'

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

Bug description:
  Broadcom NXE controller Cumulus devices ID's are missing in 16.04.03.
  CuW B1 device IDs are missing with Ubuntu 16.04.03 inbox bnxt_en 
driver(0.1.24) 

  Below is the modinfo output of Ubuntu 16.04.03 inbox bnxt_en driver.

  root@ubuntu160403:~# modinfo bnxt_en 
  filename: 
/lib/modules/4.4.0-87-generic/kernel/drivers/net/ethernet/broadcom/bnxt/bnxt_en.ko
 
  version: 0.1.24 
  description: Broadcom BCM573xx network driver 
  license: GPL 
  srcversion: 0110469E9118262B301CA46 
  alias: pci:v14E4d16D3sv*sd*bc*sc*i* 
  alias: pci:v14E4d16CBsv*sd*bc*sc*i* 
  alias: pci:v14E4d16D2sv*sd*bc*sc*i* 
  alias: pci:v14E4d16D1sv*sd*bc*sc*i* 
  alias: pci:v14E4d16CAsv*sd*bc*sc*i* 
  alias: pci:v14E4d16C9sv*sd*bc*sc*i* 
  depends: vxlan 
  intree: Y 
  vermagic: 4.4.0-87-generic SMP mod_unload modversions 

  OS Details: 
  root@ubuntu160403:~# cat /etc/issue 
  Ubuntu 16.04.3 LTS \n \l 

  root@ubuntu160403:~# uname -a 
  Linux ubuntu160403 4.4.0-87-generic #110-Ubuntu SMP Tue Jul 18 12:55:35 UTC 
2017 x86_64 x86_64 x86_64 GNU/Linux

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

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

[Kernel-packages] [Bug 1719888] Re: kernel BUG at /build/linux-s_bACt/linux-4.13.0/drivers/usb/usbip/vhci_hcd.c:683!

Did this issue start happening after an update/upgrade?  Was there a
prior kernel version where you were not having this particular problem?

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

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

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

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


Thanks in advance.

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

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

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

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

Title:
  kernel BUG at /build/linux-
  s_bACt/linux-4.13.0/drivers/usb/usbip/vhci_hcd.c:683!

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  When using a usb flash disk via usbip it crashes with this bug

  ProblemType: KernelOops
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-12-generic 4.13.0-12.13
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  Annotation: Your system might become unstable now and might need to be 
restarted.
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Date: Wed Sep 27 06:24:09 2017
  Failure: oops
  InstallationDate: Installed on 2017-09-27 (0 days ago)
  InstallationMedia: Xubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170829.1)
  IwConfig:
   ens33 no wireless extensions.
   
   lono wireless extensions.
  MachineType: VMware, Inc. VMware Virtual Platform
  ProcFB: 0 svgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-12-generic 
root=UUID=33763e28-10a5-4446-afbd-8cb727ae9363 ro find_preseed=/preseed.cfg 
auto noprompt priority=critical locale=en_US quiet
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: kerneloops-daemon N/A
  RfKill:
   
  SourcePackage: linux
  Title: kernel BUG at 
/build/linux-s_bACt/linux-4.13.0/drivers/usb/usbip/vhci_hcd.c:683!
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/02/2015
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: 6.00
  dmi.board.name: 440BX Desktop Reference Platform
  dmi.board.vendor: Intel Corporation
  dmi.board.version: None
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 1
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd07/02/2015:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
  dmi.product.name: VMware Virtual Platform
  dmi.product.version: None
  dmi.sys.vendor: VMware, Inc.

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

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

[Kernel-packages] [Bug 1718155] Re: linux-aws: 4.4.0-1036.45 -proposed tracker

2017-09-27 Thread Kamal Mostafa

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

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

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

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

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

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

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

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

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

[Kernel-packages] [Bug 1704929] Re: Repeating "can't open /dev/ttyX: No such device or address" messages during installation

2017-09-27 Thread Frank Heimes

Reverse proxy initiated ...

** Changed in: ubuntu-z-systems
 Assignee: (unassigned) => bugproxy (bugproxy)

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

Title:
  Repeating "can't open /dev/ttyX: No such device or address" messages
  during installation

Status in Ubuntu on IBM z Systems:
  Confirmed
Status in console-setup package in Ubuntu:
  Incomplete
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  [Impact]

  console-setup continuously tries to open /dev/tty[1-6] on s390x, when
  such consoles do not exist on s390x.

  This can be seen on boot in the output from the initramfs, and during
  the installer.

  [Cuase]

  It seems to me that the postinst of the console-setup is incorrect for
  s390, since on s390 Linux tty[1-6] do not exist in any modes (LPAR,
  z/VM, KVM)

  [Solution]
  I do not know what ACTIVE_CONSOLES should be set as, my guess is to set it 
to... "guess". Usually it should be slcp, but that depends on which consoles 
are configured/activated in the given KVM.

  [Testcase]
  On boot, scroll all the messages and makesure there are no error messages 
about inability to open /dev/tty*

  [Original Bug Report]

  During the installation (z/VM guest and KVM virtual machine) of Ubuntu
  Server 16.04.1 (and 16.04.2) repeating messages of the form:

  "
  Select and install software ... 10% can't open /dev/tty4: No such device or 
address
  can't open /dev/tty2: No such device or address
  can't open /dev/tty3: No such device or address
  can't open /dev/tty4: No such device or address
  can't open /dev/tty2: No such device or address
  can't open /dev/tty3: No such device or address
  can't open /dev/tty2: No such device or address
  can't open /dev/tty4: No such device or address
  can't open /dev/tty4: No such device or address
  can't open /dev/tty3: No such device or address
  can't open /dev/tty2: No such device or address
  can't open /dev/tty2: No such device or address
  can't open /dev/tty3: No such device or address
  ... 20% can't open /dev/tty4: No such device or address
  can't open /dev/tty2: No such device or address
  can't open /dev/tty3: No such device or address
  ... 30%... 40% can't open /dev/tty3: No such device or address
  can't open /dev/tty4: No such device or address
  can't open /dev/tty2: No such device or address
  ... 50% can't open /dev/tty3: No such device or address
  can't open /dev/tty4: No such device or address
  can't open /dev/tty2: No such device or address
  ... 60% can't open /dev/tty2: No such device or address
  can't open /dev/tty3: No such device or address
  can't open /dev/tty4: No such device or address
  can't open /dev/tty2: No such device or address
  ...
  Finishing the installation ... 13%... 22%... 31% can't open /dev/tty3: No 
such device or address
  can't open /dev/tty2: No such device or address
  can't open /dev/tty4: No such device or address
  ... 40%... 50%... 63%... 72%... 81% can't open /dev/tty4: No such device or 
address
  can't open /dev/tty2: No such device or address
  can't open /dev/tty3: No such device or address
  ... 90% The system is going down NOW
   Sent SIGTERM to all processes
   Sent SIGKILL to all processes
   Requesting system reboot
  01: HCPGSP2629I The virtual machine is placed in CP mode due to a SIGP stop 
CPU 00.
  02: HCPGSP2629I The virtual machine is placed in CP mode due to a SIGP stop 
CPU 00.
  03: HCPGSP2629I The virtual machine is placed in CP mode due to a SIGP stop 
CPU 00.
  00 Storage cleared - system reset.
  00 zIPL ..
  "

  They start to occur when the software gets installed:

  "Select and install software ... 10% can't open /dev/tty4: No such
  device or address"

  And only stop with the final system reboot at the end of the
  installation.

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

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

[Kernel-packages] [Bug 1719644] Re: fanctl does not exit with an error when an up step fails

2017-09-27 Thread Andy Whitcroft

** Also affects: ubuntu-fan (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Also affects: ubuntu-fan (Ubuntu Zesty)
   Importance: Undecided
   Status: New

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

Title:
  fanctl does not exit with an error when an up step fails

Status in ubuntu-fan package in Ubuntu:
  Triaged
Status in ubuntu-fan source package in Xenial:
  New
Status in ubuntu-fan source package in Zesty:
  New

Bug description:
  SRU Justification:

  Impact:
  When running cmd_up there are a few failure points which call fail_up to 
unwind but then do not exit with failure. This also has effect on running 
"fanatic enable-fan" which itself runs fanctl.

  Fix:
  Force the fail_up function to do a hard stop by adding an "exit 1" statement.

  Testcase: TBD

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

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

[Kernel-packages] [Bug 1704929] Re: Repeating "can't open /dev/ttyX: No such device or address" messages during installation

/dev/tty1 file exists on s390x ubuntu, however, one cannot open that
file doing that results in ENXIO.

console-setup is an architecture independent package which tries to
detect and configure all consoles. Ideally, I do not want to encode if
`uname -p` is s390x or some such to filter-out and skip tty[0-9].

Imho, if /dev/tty[0-9] devices do not exist, why does kernel create such
files? Can it be escalated to IBM linux team to not have those files at
all? E.g. make a upstream kernel patch to not create these devices.
Maybe I am crazy, I don't understand things - e.g. is it possible to
somehow get a working /dev/tty1?

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

Title:
  Repeating "can't open /dev/ttyX: No such device or address" messages
  during installation

Status in Ubuntu on IBM z Systems:
  Confirmed
Status in console-setup package in Ubuntu:
  Incomplete
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  [Impact]

  console-setup continuously tries to open /dev/tty[1-6] on s390x, when
  such consoles do not exist on s390x.

  This can be seen on boot in the output from the initramfs, and during
  the installer.

  [Cuase]

  It seems to me that the postinst of the console-setup is incorrect for
  s390, since on s390 Linux tty[1-6] do not exist in any modes (LPAR,
  z/VM, KVM)

  [Solution]
  I do not know what ACTIVE_CONSOLES should be set as, my guess is to set it 
to... "guess". Usually it should be slcp, but that depends on which consoles 
are configured/activated in the given KVM.

  [Testcase]
  On boot, scroll all the messages and makesure there are no error messages 
about inability to open /dev/tty*

  [Original Bug Report]

  During the installation (z/VM guest and KVM virtual machine) of Ubuntu
  Server 16.04.1 (and 16.04.2) repeating messages of the form:

  "
  Select and install software ... 10% can't open /dev/tty4: No such device or 
address
  can't open /dev/tty2: No such device or address
  can't open /dev/tty3: No such device or address
  can't open /dev/tty4: No such device or address
  can't open /dev/tty2: No such device or address
  can't open /dev/tty3: No such device or address
  can't open /dev/tty2: No such device or address
  can't open /dev/tty4: No such device or address
  can't open /dev/tty4: No such device or address
  can't open /dev/tty3: No such device or address
  can't open /dev/tty2: No such device or address
  can't open /dev/tty2: No such device or address
  can't open /dev/tty3: No such device or address
  ... 20% can't open /dev/tty4: No such device or address
  can't open /dev/tty2: No such device or address
  can't open /dev/tty3: No such device or address
  ... 30%... 40% can't open /dev/tty3: No such device or address
  can't open /dev/tty4: No such device or address
  can't open /dev/tty2: No such device or address
  ... 50% can't open /dev/tty3: No such device or address
  can't open /dev/tty4: No such device or address
  can't open /dev/tty2: No such device or address
  ... 60% can't open /dev/tty2: No such device or address
  can't open /dev/tty3: No such device or address
  can't open /dev/tty4: No such device or address
  can't open /dev/tty2: No such device or address
  ...
  Finishing the installation ... 13%... 22%... 31% can't open /dev/tty3: No 
such device or address
  can't open /dev/tty2: No such device or address
  can't open /dev/tty4: No such device or address
  ... 40%... 50%... 63%... 72%... 81% can't open /dev/tty4: No such device or 
address
  can't open /dev/tty2: No such device or address
  can't open /dev/tty3: No such device or address
  ... 90% The system is going down NOW
   Sent SIGTERM to all processes
   Sent SIGKILL to all processes
   Requesting system reboot
  01: HCPGSP2629I The virtual machine is placed in CP mode due to a SIGP stop 
CPU 00.
  02: HCPGSP2629I The virtual machine is placed in CP mode due to a SIGP stop 
CPU 00.
  03: HCPGSP2629I The virtual machine is placed in CP mode due to a SIGP stop 
CPU 00.
  00 Storage cleared - system reset.
  00 zIPL ..
  "

  They start to occur when the software gets installed:

  "Select and install software ... 10% can't open /dev/tty4: No such
  device or address"

  And only stop with the final system reboot at the end of the
  installation.

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

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

[Kernel-packages] [Bug 1719945] [NEW] Silently fails in Wayland session

2017-09-27 Thread Chris Halse Rogers

Public bug reported:

I've got an nvidia/intel hybrid laptop. In a Wayland session nvidia-
settings fails silently when started from the shell. When started from a
terminal, it prints:

ERROR: Unable to load info from any available system

and then quits.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: nvidia-settings 367.35-0ubuntu1
ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1
Uname: Linux 4.13.0-11-generic x86_64
NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
ApportVersion: 2.20.7-0ubuntu1
Architecture: amd64
CurrentDesktop: GNOME
Date: Wed Sep 27 11:49:57 2017
InstallationDate: Installed on 2017-09-20 (7 days ago)
InstallationMedia: Ubuntu-GNOME 17.10 "Artful Aardvark" - Alpha amd64 (20170919)
SourcePackage: nvidia-settings
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: nvidia-settings (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 nvidia-settings in Ubuntu.
https://bugs.launchpad.net/bugs/1719945

Title:
  Silently fails in Wayland session

Status in nvidia-settings package in Ubuntu:
  New

Bug description:
  I've got an nvidia/intel hybrid laptop. In a Wayland session nvidia-
  settings fails silently when started from the shell. When started from
  a terminal, it prints:

  ERROR: Unable to load info from any available system

  and then quits.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: nvidia-settings 367.35-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1
  Uname: Linux 4.13.0-11-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Wed Sep 27 11:49:57 2017
  InstallationDate: Installed on 2017-09-20 (7 days ago)
  InstallationMedia: Ubuntu-GNOME 17.10 "Artful Aardvark" - Alpha amd64 
(20170919)
  SourcePackage: nvidia-settings
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-settings/+bug/1719945/+subscriptions

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

[Kernel-packages] [Bug 1704929] Re: Repeating "can't open /dev/ttyX: No such device or address" messages during installation

** No longer affects: console-setup (Ubuntu Xenial)

** No longer affects: console-setup (Ubuntu Zesty)

** No longer affects: console-setup (Ubuntu Artful)

** Changed in: console-setup (Ubuntu)
   Status: Confirmed => Incomplete

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

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

Title:
  Repeating "can't open /dev/ttyX: No such device or address" messages
  during installation

Status in Ubuntu on IBM z Systems:
  Confirmed
Status in console-setup package in Ubuntu:
  Incomplete
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  [Impact]

  console-setup continuously tries to open /dev/tty[1-6] on s390x, when
  such consoles do not exist on s390x.

  This can be seen on boot in the output from the initramfs, and during
  the installer.

  [Cuase]

  It seems to me that the postinst of the console-setup is incorrect for
  s390, since on s390 Linux tty[1-6] do not exist in any modes (LPAR,
  z/VM, KVM)

  [Solution]
  I do not know what ACTIVE_CONSOLES should be set as, my guess is to set it 
to... "guess". Usually it should be slcp, but that depends on which consoles 
are configured/activated in the given KVM.

  [Testcase]
  On boot, scroll all the messages and makesure there are no error messages 
about inability to open /dev/tty*

  [Original Bug Report]

  During the installation (z/VM guest and KVM virtual machine) of Ubuntu
  Server 16.04.1 (and 16.04.2) repeating messages of the form:

  "
  Select and install software ... 10% can't open /dev/tty4: No such device or 
address
  can't open /dev/tty2: No such device or address
  can't open /dev/tty3: No such device or address
  can't open /dev/tty4: No such device or address
  can't open /dev/tty2: No such device or address
  can't open /dev/tty3: No such device or address
  can't open /dev/tty2: No such device or address
  can't open /dev/tty4: No such device or address
  can't open /dev/tty4: No such device or address
  can't open /dev/tty3: No such device or address
  can't open /dev/tty2: No such device or address
  can't open /dev/tty2: No such device or address
  can't open /dev/tty3: No such device or address
  ... 20% can't open /dev/tty4: No such device or address
  can't open /dev/tty2: No such device or address
  can't open /dev/tty3: No such device or address
  ... 30%... 40% can't open /dev/tty3: No such device or address
  can't open /dev/tty4: No such device or address
  can't open /dev/tty2: No such device or address
  ... 50% can't open /dev/tty3: No such device or address
  can't open /dev/tty4: No such device or address
  can't open /dev/tty2: No such device or address
  ... 60% can't open /dev/tty2: No such device or address
  can't open /dev/tty3: No such device or address
  can't open /dev/tty4: No such device or address
  can't open /dev/tty2: No such device or address
  ...
  Finishing the installation ... 13%... 22%... 31% can't open /dev/tty3: No 
such device or address
  can't open /dev/tty2: No such device or address
  can't open /dev/tty4: No such device or address
  ... 40%... 50%... 63%... 72%... 81% can't open /dev/tty4: No such device or 
address
  can't open /dev/tty2: No such device or address
  can't open /dev/tty3: No such device or address
  ... 90% The system is going down NOW
   Sent SIGTERM to all processes
   Sent SIGKILL to all processes
   Requesting system reboot
  01: HCPGSP2629I The virtual machine is placed in CP mode due to a SIGP stop 
CPU 00.
  02: HCPGSP2629I The virtual machine is placed in CP mode due to a SIGP stop 
CPU 00.
  03: HCPGSP2629I The virtual machine is placed in CP mode due to a SIGP stop 
CPU 00.
  00 Storage cleared - system reset.
  00 zIPL ..
  "

  They start to occur when the software gets installed:

  "Select and install software ... 10% can't open /dev/tty4: No such
  device or address"

  And only stop with the final system reboot at the end of the
  installation.

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

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

[Kernel-packages] [Bug 1646277] Re: Xenial server 16.04.x will have a black screen after PXE installation

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

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

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

Thanks in advance

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

Title:
  Xenial server 16.04.x will have a black screen after PXE installation

Status in debian-installer package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in debian-installer source package in Xenial:
  Confirmed
Status in linux source package in Xenial:
  Confirmed

Bug description:
  The display will keep black screen after install 16.04.x via PXE(need
  use "Ctrl+Alt+F1" to change to terminal 1, then can see text mode
  screen)

  Quanta team is installing Xenial server using PXE boot.   After the
  installation, the console will show a black screen.   Hitting ctl-
  alt-f1 displays the text mode screen OK.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1646277/+subscriptions

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

[Kernel-packages] [Bug 1711075] Re: [Power 9, Power NV][WSP/Boston]Ubuntu 16.04.03 : perf test is hung at Breakpoint overflow signal handler

*** This bug is a duplicate of bug 1706033 ***
https://bugs.launchpad.net/bugs/1706033

Commit d89ba5353f301 was SRU'd for bug 1706033, so I'll mark this bug as
a duplicate of that bug.

** This bug has been marked a duplicate of bug 1706033
   [P9, Power NV][ WSP][Ubuntu 16.04.03] : perf hw breakpoint command results 
in call traces and system goes for reboot.

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

Title:
  [Power 9, Power NV][WSP/Boston]Ubuntu 16.04.03 : perf test is hung at
  Breakpoint overflow signal handler

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

Bug description:
  == Comment: # - Shriya R. Kulkarni <> - 2017-06-14 01:11:02 ==
  Problem Description :
  =
  perf test is hung at Breakpoint overflow signal handler.

  Machine details :
  ==
  System : WSP , P9 baremetal.
  OS : Ubuntu 16.04.03
  uname -a : Linux ltc-wspoon3 4.10.0-23-generic #25~16.04.1-Ubuntu SMP Fri Jun 
9 10:43:34 UTC 2017 ppc64le ppc64le ppc64le GNU/Linux

  Testing:
  
  root@ltc-wspoon3:~# perf test
   1: vmlinux symtab matches kallsyms: Skip
   2: Detect openat syscall event: Ok
   3: Detect openat syscall event on all cpus: Ok
   4: Read samples using the mmap interface  : Ok
   5: Parse event definition strings : Ok
   6: PERF_RECORD_* events & perf_sample fields  : Ok
   7: Parse perf pmu format  : Ok
   8: DSO data read  : Ok
   9: DSO data cache : Ok
  10: DSO data reopen: Ok
  11: Roundtrip evsel->name  : Ok
  12: Parse sched tracepoints fields : Ok
  13: syscalls:sys_enter_openat event fields : Ok
  14: Setup struct perf_event_attr   : Skip
  15: Match and link multiple hists  : Ok
  16: 'import perf' in python: Ok
  17: Breakpoint overflow signal handler :^C

  root@ltc-wspoon3:~# perf test -v 17
  17: Breakpoint overflow signal handler :
  --- start ---
  test child forked, pid 3802
  failed opening event 0
  failed opening event 0

  Attach : strace output.

  Steps to reproduce :
  
  1. Install perf. 
  2. Run perf test.
  3. When system hangs , exit it by : ^c.

  == Comment: # - Ravikumar B. Bangoria <> - 2017-07-13 04:44:29 ==
  Shriya,

  Can you please check after applying:
  
https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git/commit/?id=d89ba5353f301971dd7d2f9fdf25c4432728f38e

  == Comment: # - Shriya R. Kulkarni <> - 2017-07-19 06:28:13 ==
  Verified and Tested on Ubuntu 16.04.03:
  =
  uname -a : 4.10.0-27-generic
  System : Boston

  Testing without patch using distro perf:
  
  root@ltc-boston27:~# perf test
   1: vmlinux symtab matches kallsyms: Skip
   2: Detect openat syscall event: Ok
   3: Detect openat syscall event on all cpus: Ok
   4: Read samples using the mmap interface  : Ok
   5: Parse event definition strings : Ok
   6: PERF_RECORD_* events & perf_sample fields  : Ok
   7: Parse perf pmu format  : Ok
   8: DSO data read  : Ok
   9: DSO data cache : Ok
  10: DSO data reopen: Ok
  11: Roundtrip evsel->name  : Ok
  12: Parse sched tracepoints fields : Ok
  13: syscalls:sys_enter_openat event fields : Ok
  14: Setup struct perf_event_attr   : Skip
  15: Match and link multiple hists  : Ok
  16: 'import perf' in python: Ok
  17: Breakpoint overflow signal handler :^C
  root@ltc-boston27:~# 

  
  Testing with Patch using distro perf :
  ==
  root@ltc-boston27:~/linux-hwe-4.10.0/tools/perf# ./perf test
   1: vmlinux symtab matches kallsyms: Ok
   2: Detect openat syscall event: Ok
   3: Detect openat syscall event on all cpus: Ok
   4: Read samples using the mmap interface  : Ok
   5: Parse event definition strings : Ok
   6: PERF_RECORD_* events & perf_sample fields  : Ok
   7: Parse perf pmu format  : Ok
   8: DSO data read  : Ok
   9: DSO data cache : Ok
  10: DSO data reopen: Ok
  11: Roundtrip evsel->name  : Ok
  12: Parse sched tracepoints fields : Ok
  13: syscalls:sys_enter_openat event fields : Ok
  14: Setup struct perf_event_attr   : Ok
  15: Match and link multiple hists  : Ok
  16: 'import perf' in python: Ok
  17: Breakpoint overflow signal handler : FAILED!

[Kernel-packages] [Bug 1715725] Re: linux-aws needs drbd.ko

2017-09-27 Thread Kamal Mostafa

** Tags added: verification-done-xenial

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

Title:
  linux-aws needs drbd.ko

Status in linux-aws package in Ubuntu:
  Fix Committed
Status in linux-aws source package in Xenial:
  Fix Committed

Bug description:
  Please distribute drbd.ko in main linux-image package.

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

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

[Kernel-packages] [Bug 1719290] Re: CONFIG_DEBUG_FS is not enabled by "make zfcpdump_defconfig" with Ubuntu 17.10 (kernel 4.13)

zfcpdump kernel is escalated to the kernel team.

** Also affects: zfcpdump-kernel (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: zfcpdump-kernel (Ubuntu Artful)
   Status: New => Triaged

** Changed in: zfcpdump-kernel (Ubuntu Artful)
   Importance: Undecided => High

** Changed in: zfcpdump-kernel (Ubuntu Artful)
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

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

Title:
  CONFIG_DEBUG_FS is not enabled by "make zfcpdump_defconfig" with
  Ubuntu 17.10 (kernel 4.13)

Status in Ubuntu on IBM z Systems:
  Triaged
Status in linux package in Ubuntu:
  Triaged
Status in zfcpdump-kernel package in Ubuntu:
  Triaged
Status in linux source package in Artful:
  Triaged
Status in zfcpdump-kernel source package in Artful:
  Triaged

Bug description:
  Ubuntu 17.10 uses kernel 4.13.

  We just found out that on this kernel version CONFIG_DEBUG_FS is not
  enabled by "make zfcpdump_defconfig".

  This makes zfcpdump fail with the following error message:

  ERROR: Unable to mount debugfs 
  No such file or directory

  Patch solving this problem is attached

  As reference following bugzilla
  As reference h
  IBM bugzilla for enabling zfcpdump: 
https://bugzilla.linux.ibm.com/show_bug.cgi?id=139974

  or Launchpad 
  https://bugs.launchpad.net/ubuntu/+source/s390-tools/+bug/1565841

  == Comment: #1 - Heinz-Werner Seeck  -
  2017-09-25 06:00:23 ==

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

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

[Kernel-packages] [Bug 1706033] Re: [P9, Power NV][ WSP][Ubuntu 16.04.03] : perf hw breakpoint command results in call traces and system goes for reboot.

I submitted a Z SRU request.

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

Title:
  [P9, Power NV][ WSP][Ubuntu 16.04.03] : perf hw breakpoint command
  results in call traces and system goes for reboot.

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

Bug description:
  == Comment: #0 - Shriya R. Kulkarni <> - 2017-06-14 04:38:16 ==
  Problem Description :
  =
   
  While running perftool - testsuite, the perf hw breakpoint fails and it 
result in call traces , hence system goes for reboot .

  Machine details :
  ==
  System : P9 , WSP , Bare metal.
  OS : Ubuntu 16.04.03
  uname -a : Linux ltc-wspoon3 4.10.0-23-generic #25~16.04.1-Ubuntu SMP Fri Jun 
9 10:43:34 UTC 2017 ppc64le ppc64le ppc64le GNU/Linux

  Steps to reproduce:
  
  1. Install perf.
  2. git clone perftool-testsuite.
  https://github.com/rfmvh/perftool-testsuite
  3. Do make.
  4. Test fails at step : -- [ FAIL ] -- perf_stat :: test_hw_breakpoints :: 
kspace address execution mem:0xc035c020:x (command exitcode + output 
regexp parsing
  and call trace is seen as system goes for reboot.

  Call traces :
  ===

  ubuntu@ltc-wspoon3:~$ [1602513.518414] Unable to handle kernel paging request 
for data at address 0xc135d3b8
  [1602513.518553] Faulting instruction address: 0xc02869bc
  [1602513.518694] Oops: Kernel access of bad area, sig: 11 [#1]
  [1602513.518782] SMP NR_CPUS=2048 
  [1602513.518784] NUMA 
  [1602513.518842] PowerNV
  [1602513.518922] Modules linked in: vmx_crypto ofpart ipmi_powernv 
cmdlinepart ipmi_devintf powernv_flash ipmi_msghandler ibmpowernv opal_prd mtd 
at24 nvmem_core uio_pdrv_genirq uio autofs4 ast i2c_algo_bit drm_kms_helper 
syscopyarea sysfillrect sysimgblt fb_sys_fops crc32c_vpmsum ttm drm tg3 ahci 
libahci
  [1602513.519399] CPU: 27 PID: 4069 Comm: sysctl Not tainted 4.10.0-22-generic 
#24
  [1602513.519524] task: c000203968c42c00 task.stack: c00020396571
  [1602513.519624] NIP: c02869bc LR: c03f7348 CTR: 
c0286990
  [1602513.519747] REGS: c000203965713a40 TRAP: 0300   Not tainted  
(4.10.0-22-generic)
  [1602513.519876] MSR: 90009033 
  [1602513.519889]   CR: 22002448  XER: 
  [1602513.520058] CFAR: c03f7344 DAR: c135d3b8 DSISR: 0040 
SOFTE: 1 
  [1602513.520058] GPR00: c03f7348 c000203965713cc0 c145d100 
c134af00 
  [1602513.520058] GPR04:  4ee50300 c000203965713d20 
c000203965713e00 
  [1602513.520058] GPR08:  c135d100  
c0b71020 
  [1602513.520058] GPR12: c0286990 c7b4f300  
 
  [1602513.520058] GPR16:    
 
  [1602513.520058] GPR20:    
0001 
  [1602513.520058] GPR24: 3fffc542f5a0 0400 c000203965713e00 
4ee50300 
  [1602513.520058] GPR28: c134af00  c03fee038800 
 
  [1602513.521280] NIP [c02869bc] dirty_ratio_handler+0x2c/0x90
  [1602513.521374] LR [c03f7348] proc_sys_call_handler+0x138/0x1c0
  [1602513.521481] Call Trace:
  [1602513.521526] [c000203965713cc0] [c000203965713d00] 0xc000203965713d00 
(unreliable)
  [1602513.521655] [c000203965713d00] [c03f7348] 
proc_sys_call_handler+0x138/0x1c0
  [1602513.521797] [c000203965713d70] [c03436ec] __vfs_read+0x3c/0x70
  [1602513.521907] [c000203965713d90] [c034516c] vfs_read+0xbc/0x1b0
  [1602513.522016] [c000203965713de0] [c0346dd8] SyS_read+0x68/0x110
  [1602513.522112] [c000203965713e30] [c000b184] system_call+0x38/0xe0
  [1602513.522243] Instruction dump:
  [1602513.522303] 6042 3c4c011d 38426770 7c0802a6 6000 7c0802a6 
fbc1fff0 fbe1fff8 
  [1602513.522445] f8010010 f821ffc1 3d22fff0 7c9f2378  4be66da9 
6000 3d22fff0 
  [1602513.522564] ---[ end trace 17c76e13e641d3c6 ]---
  [1602513.522657] 

  It goes for reboot :

  After booting to Ubuntu , I see series of call traces.

  Ubuntu 16.04.2 LTS ltc-wspoon3 hvc0

  ltc-wspoon3 login: [ 3476.626263] Unable to handle kernel paging request for 
data at address 0xc13ad438
  [ 3476.626422] Faulting instruction address: 0xc029a140
  [ 3476.626537] Oops: Kernel access of bad area, sig: 11 [#1]
  [ 3476.626615] SMP NR_CPUS=2048 
  [ 3476.626616] NUMA 
  [ 3476.626673] PowerNV
  [ 3476.626746] Modules linked in: ipmi_powernv at24 ipmi_devintf nvmem_core 
ipmi_msghandler ofpart cmdlinepart powernv_flash mtd opal_prd vmx_crypto 
ibmpowernv uio_pdrv_genirq uio autofs4 ast i2c_algo_bit ttm crc32c_vpmsum 
drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops tg3 drm ahci

[Kernel-packages] [Bug 1718936] Re: Can't boot Artful 17.10 live images on XPS 15 (9560)

2017-09-27 Thread garyx

Someone suggested noveau.modeset=0 however for me that does not boot for
me either. The only setting that will is nomodeset as mentioned here in
the first entry.

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

Title:
  Can't boot Artful 17.10 live images on XPS 15 (9560)

Status in linux package in Ubuntu:
  Fix Released

Bug description:
  I usually test Ubuntu beta releases. With Artful, I haven't been able
  to boot the image on my XPS 15 (9560) Dell laptop because the boot
  process stops half way.

  The boot proceeds properly if I pass the "nomodeset" kernel boot
  option but that won't work because there is no more hiDPI support and
  dual display doesn't work.

  This has been ongoing for several weeks, around the 4.12 kernel.
  Please fix it. It would be a shame for this product not to boot Artful
  out of the box.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-11-generic 4.13.0-11.12
  ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1
  Uname: Linux 4.13.0-11-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 1701 F pulseaudio
  CasperVersion: 1.384
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep 22 12:38:09 2017
  LiveMediaBuild: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170921)
  MachineType: Dell Inc. XPS 15 9560
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi 
file=/cdrom/preseed/username.seed boot=casper quiet splash --- nomodeset
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-11-generic N/A
   linux-backports-modules-4.13.0-11-generic  N/A
   linux-firmware 1.168
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/30/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.5.0
  dmi.board.name: 0JHP5H
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.5.0:bd08/30/2017:svnDellInc.:pnXPS159560:pvr:rvnDellInc.:rn0JHP5H:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 15 9560
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1635597] Re: Ubuntu16.10:talclp1: Kdump failed with multipath disk

By "recreated the issue", do you mean it fixes the issue? Cause in the
previous message, you mentioned you could create the crash files? Was
that using the proposed package from louis ppa? Can you clarify?

Thank you very much.
Cascardo.

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

Title:
  Ubuntu16.10:talclp1: Kdump failed with multipath disk

Status in The Ubuntu-power-systems project:
  Confirmed
Status in linux package in Ubuntu:
  New
Status in makedumpfile package in Ubuntu:
  Fix Released
Status in linux source package in Trusty:
  New
Status in makedumpfile source package in Trusty:
  Confirmed
Status in linux source package in Xenial:
  New
Status in makedumpfile source package in Xenial:
  Confirmed
Status in linux source package in Zesty:
  New
Status in makedumpfile source package in Zesty:
  Confirmed

Bug description:
  Problem  Description
  ==
  On talclp1, I enabled kdump. But kdump failed and it drop to BusyBox.

  root@talclp1:~# echo c> /proc/sysrq-trigger
  [  132.643690] sysrq: SysRq : Trigger a crash
  [  132.643739] Unable to handle kernel paging request for data at address 
0x
  [  132.643745] Faulting instruction address: 0xc05c28f4
  [  132.643749] Oops: Kernel access of bad area, sig: 11 [#1]
  [  132.643753] SMP NR_CPUS=2048 NUMA pSeries
  [  132.643758] Modules linked in: fuse ufs qnx4 hfsplus hfs minix ntfs msdos 
jfs rpadlpar_io rpaphp rpcsec_gss_krb5 nfsv4 dccp_diag cifs nfs dns_resolver 
dccp tcp_diag fscache udp_diag inet_diag unix_diag af_packet_diag netlink_diag 
binfmt_misc xfs libcrc32c pseries_rng rng_core ghash_generic gf128mul 
vmx_crypto sg nfsd auth_rpcgss nfs_acl lockd grace sunrpc ip_tables x_tables 
autofs4 ext4 crc16 jbd2 fscrypto mbcache crc32c_generic btrfs xor raid6_pq 
dm_round_robin sr_mod sd_mod cdrom ses enclosure scsi_transport_sas ibmveth 
crc32c_vpmsum ipr scsi_dh_emc scsi_dh_rdac scsi_dh_alua dm_multipath dm_mod
  [  132.643819] CPU: 49 PID: 10174 Comm: bash Not tainted 4.8.0-15-generic 
#16-Ubuntu
  [  132.643824] task: c00111767080 task.stack: c000d82e
  [  132.643828] NIP: c05c28f4 LR: c05c39d8 CTR: 
c05c28c0
  [  132.643832] REGS: c000d82e3990 TRAP: 0300   Not tainted  
(4.8.0-15-generic)
  [  132.643836] MSR: 80009033   CR: 28242422  
XER: 0001
  [  132.643848] CFAR: c00087d0 DAR:  DSISR: 4200 
SOFTE: 1
  GPR00: c05c39d8 c000d82e3c10 c0f67b00 0063
  GPR04: c0011d04a9b8 c0011d05f7e0 c0047fb0 00015998
  GPR08: 0007 0001  0001
  GPR12: c05c28c0 c7b4b900  2200
  GPR16: 10170dc8 01002b566368 10140f58 100c7570
  GPR20:  1017dd58 10153618 1017b608
  GPR24: 3e87a294 0001 c0ebff60 0004
  GPR28: c0ec0320 0063 c0e72a90 
  [  132.643906] NIP [c05c28f4] sysrq_handle_crash+0x34/0x50
  [  132.643911] LR [c05c39d8] __handle_sysrq+0xe8/0x280
  [  132.643914] Call Trace:
  [  132.643917] [c000d82e3c10] [c0a245e8] 0xc0a245e8 
(unreliable)
  [  132.643923] [c000d82e3c30] [c05c39d8] __handle_sysrq+0xe8/0x280
  [  132.643928] [c000d82e3cd0] [c05c4188] 
write_sysrq_trigger+0x78/0xa0
  [  132.643935] [c000d82e3d00] [c03ad770] proc_reg_write+0xb0/0x110
  [  132.643941] [c000d82e3d50] [c030fc3c] __vfs_write+0x6c/0xe0
  [  132.643946] [c000d82e3d90] [c0311144] vfs_write+0xd4/0x240
  [  132.643950] [c000d82e3de0] [c0312e5c] SyS_write+0x6c/0x110
  [  132.643957] [c000d82e3e30] [c00095e0] system_call+0x38/0x108
  [  132.643961] Instruction dump:
  [  132.643963] 38425240 7c0802a6 f8010010 f821ffe1 6000 6000 3d220019 
3949ba60
  [  132.643972] 3921 912a 7c0004ac 3940 <992a> 38210020 
e8010010 7c0803a6
  [  132.643981] ---[ end trace eed6bbcd2c3bdfdf ]---
  [  132.646105]
  [  132.646176] Sending IPI to other CPUs
  [  132.647490] IPI complete
  I'm in purgatory
   -> smp_release_cpus()
  spinning_secondaries = 104
   <- smp_release_cpus()
  [2.011346] alg: hash: Test 1 failed for crc32c-vpmsum
  [2.729254] sd 0:2:0:0: [sda] Assuming drive cache: write through
  [2.731554] sd 1:2:5:0: [sdn] Assuming drive cache: write through
  [2.739087] sd 1:2:4:0: [sdm] Assuming drive cache: write through
  [2.739089] sd 1:2:6:0: [sdo] Assuming drive cache: write through
  [2.739110] sd 1:2:7:0: [sdp] Assuming drive cache: write through
  [2.739115] sd 1:2:0:0: [sdi] Assuming drive cache: write through
  [2.739122] sd 1:2:3:0: [sdl] Assuming drive

[Kernel-packages] [Bug 1696049] Re: xfstest sanity checks on seek operations fails

Sorry, ppc kernels are there now.

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

Title:
  xfstest sanity checks on seek operations fails

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

Bug description:
  == Comment: #0 - Harish Sriram 
  Issue:
  --
  xfstest fails with sanity checks on seek operations

  # uname -a
  Linux ltc-tuleta12 4.10.0-21-generic #23~16.04.1-Ubuntu SMP Tue May 2 
12:54:57 UTC 2017 ppc64le ppc64le ppc64le GNU/Linux

  Steps to reproduce:
  
  1. Create a loop device with xfs filesystem
  2. git clone git://git.kernel.org/pub/scm/fs/xfs/xfstests-dev.git; cd 
xfstests-dev
  3. make
  4. Create a local.config for running with created loop device
  5. Run xfstests-dev test  : ./check tests/generic/285 or ./check 
tests/generic/436

  The test 285 fails with following
  ...
  ...
  07. Test file with unwritten extents, only have dirty pages
  07.01 SEEK_HOLE expected 0 or 45056, got 0.   succ
  07.02 SEEK_HOLE expected 1 or 45056, got 1.   succ
  07.03 SEEK_DATA expected 40960 or 40960, got -1.  FAIL
  07.04 SEEK_DATA expected 40960 or 40960, got -1.  FAIL

  08. Test file with unwritten extents, only have unwritten pages
  08.01 SEEK_HOLE expected 0 or 45056, got 0.   succ
  08.02 SEEK_HOLE expected 1 or 45056, got 1.   succ
  08.03 SEEK_DATA expected 40960 or 40960, got -1.  FAIL
  08.04 SEEK_DATA expected 40960 or 40960, got -1.  FAIL

  The test 436 fails with 
  ...
  ...
  14. Test file with unwritten extents, small hole after pagevec dirty pages
  14.01 SEEK_HOLE expected 917504 or 4194304, got 3670016.  FAIL
  14.02 SEEK_HOLE expected 917504 or 4194304, got 3670016.  FAIL
  14.03 SEEK_HOLE expected 3670016 or 4194304, got 3670016. succ
  14.04 SEEK_DATA expected 0 or 0, got 0.   succ
  14.05 SEEK_DATA expected 1 or 1, got 1.   succ
  14.06 SEEK_DATA expected 2752512 or 2752512, got 2752512. succ

  seek sanity check failed!

  Full log is attached.

  == Comment: #6 - Harish Sriram

  commit 5375023ae1266553a7baa0845e82917d8803f48c
  Author: Jan Kara 
  Date:   Thu May 18 16:36:22 2017 -0700

  xfs: Fix missed holes in SEEK_HOLE implementation
  XFS SEEK_HOLE implementation could miss a hole in an unwritten extent as
  can be seen by the following command:
  
  xfs_io -c "falloc 0 256k" -c "pwrite 0 56k" -c "pwrite 128k 8k"
 -c "seek -h 0" file
  wrote 57344/57344 bytes at offset 0
  56 KiB, 14 ops; 0. sec (49.312 MiB/sec and 12623.9856 ops/sec)
  wrote 8192/8192 bytes at offset 131072
  8 KiB, 2 ops; 0. sec (70.383 MiB/sec and 18018.0180 ops/sec)
  Whence  Result
  HOLE139264
  
  Where we can see that hole at offset 56k was just ignored by SEEK_HOLE
  implementation. The bug is in xfs_find_get_desired_pgoff() which does
  not properly detect the case when pages are not contiguous.
  
  Fix the problem by properly detecting when found page has larger offset
  than expected.
  
  CC: sta...@vger.kernel.org
  Fixes: d126d43f631f996daeee5006714fed914be32368
  Signed-off-by: Jan Kara 
  Reviewed-by: Brian Foster 
  Reviewed-by: Darrick J. Wong 
  Signed-off-by: Darrick J. Wong 

  
  The above commit fixes the generic/436 test, but generic/285 still FAILS.

  The generic/285 failure is reproducible on most P8/P9 systems.

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

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

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

Well, it shouldn't be empty, unless there is a bug on XFS. Can you
verify what is the content of the file right before rebooting?

Thank you very much.
Cascardo.

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

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

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

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

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

  ---Steps to Reproduce---

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

  Machine hangs after below log. Attaching console log.

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

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

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

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

[Kernel-packages] [Bug 1715812] Re: Neighbour confirmation broken, breaks ARP cache aging

2017-09-27 Thread Fabio Bardella

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

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

Title:
  Neighbour confirmation broken, breaks ARP cache aging

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

Bug description:
  [SRU Justification]

  [Impact]
  A host can lose access to another host whose MAC address changes if they have 
active connections to other hosts that share a route. The ARP cache does not 
time out as expected - instead the old MAC address is continuously reconfirmed.

  [Fix]
  Apply series [1], which changes the algorithm for neighbour confirmation.
  That is, from upstream:
  51ce8bd4d17a net: pending_confirm is not used anymore 
  0dec879f636f net: use dst_confirm_neigh for UDP, RAW, ICMP, L2TP 
  63fca65d0863 net: add confirm_neigh method to dst_ops 
  c3a2e8370534 tcp: replace dst_confirm with sk_dst_confirm 
  c86a773c7802 sctp: add dst_pending_confirm flag 
  4ff0620354f2 net: add dst_pending_confirm flag to skbuff 
  9b8805a32559 sock: add sk_dst_pending_confirm flag 

  [Test case]
  Create 3 real or virtual systems, all hooked up to a switch.
  One system needs an active-backup bond with fail_over_mac=1 num_grat_arp=0.

  Put all the systems in the same subnet, e.g. 192.168.200.0/24

  Call the system with the bond A, and the other two systems B and C.

  On B, run in 3 shells:
   - netperf -t TCP_RR to C
   - ping -f A
   - watch 'ip -s neigh show 192.168.200.0/24'

  On A, cause the bond to fail over.

  Observe that:

   - without the patches, B intermittently fails to notice the change in
  A's MAC address. This presents as the ping failing and not recovering,
  and the arp table showing the old mac address never timing out and
  never being replace with a new mac address.

   - with the patches, the arp cache times out and B sends another mac
  probe and detects A's new address.

  It helps to use taskset to put ping and netperf on the same CPU, or
  use single-CPU vms.

  See [2] for more details.

  [References]
  [2] Original report: 
https://www.mail-archive.com/netdev@vger.kernel.org/msg138762.html
  [1]: https://www.spinics.net/lists/linux-rdma/msg45907.html

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

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

[Kernel-packages] [Bug 1663400] Re: kexec: arm64: Increase the upper limit for RAM segments

2017-09-27 Thread Bug Watch Updater

** Changed in: kexec-tools (Debian)
   Status: New => Fix Released

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

Title:
  kexec: arm64: Increase the upper limit for RAM segments

Status in kexec-tools package in Ubuntu:
  Fix Released
Status in kexec-tools source package in Xenial:
  Fix Committed
Status in kexec-tools source package in Yakkety:
  Fix Committed
Status in kexec-tools package in Debian:
  Fix Released

Bug description:
  [Impact]
  Currently kexec is unable to see all the "System RAM" recorded in /proc/iomem.

  On a newer UEFI based Qualcomm target the number of system ram regions
  retrieved from /proc/iomem  are ~40. Currently KEXEC_SEGMENT_MAX is
  set to 16, which represents the kexec segments passed to kexec_load
  syscall, like kernel image, initrd image etc. The patch increases the
  value to 64. This enables kexec to see all the "System RAM" as
  recorded in /proc/iomem.

  [Test Case]
  == System RAM reported by /proc/iomem ==
  ubuntu@ubuntu:~$ sudo cat /proc/iomem | grep "System RAM"
  0020-0020 : System RAM
  0082-0307 : System RAM
  0308-0308 : System RAM
  0309-031f : System RAM
  0320-033f : System RAM
  0341-0589 : System RAM
  058a-058a : System RAM
  058b-058b : System RAM
  058c-0597 : System RAM
  0598-05987fff : System RAM
  05988000-0598bfff : System RAM
  0598c000-05a0 : System RAM
  05a1-05aa : System RAM
  05ab-05ca0fff : System RAM
  05ca1000-08ca : System RAM
  08cb-08cf : System RAM
  08d0-08ed : System RAM
  08ee-08ee0fff : System RAM
  08ee1000-08ee3fff : System RAM
  08ee4000-08ee : System RAM
  08ef-092a : System RAM
  092b-092d : System RAM
  092e-09422fff : System RAM
  09423000-0949 : System RAM
  094a-0957 : System RAM
  0958-0958cfff : System RAM
  0958d000-098c : System RAM
  098d-098d0fff : System RAM
  098d1000-098dbfff : System RAM
  098dc000-0e8b : System RAM
  0e8c-0e8e : System RAM
  0e8f-0fff : System RAM
  1080-17fe : System RAM
  1c02-1c7f : System RAM
  1c80-1c80 : System RAM
  1c81-7efb : System RAM
  7efc-7efd : System RAM
  7efe-7efe : System RAM
  7eff-7eff : System RAM
  7f00-17 : System RAM
  ubuntu@ubuntu:~$

  == BEFORE PATCH: System RAM reported by kexec ==
  ubuntu@ubuntu:~$ sudo kexec -d -l /boot/vmlinuz-4.7.0-2-generic --reuse-cmd 
--initrd=/boot/initrd.img-4.7.0-2-generic | grep "System RAM"
  get_memory_ranges_iomem_cb: 0020 - 0020 : System RAM
  get_memory_ranges_iomem_cb: 0082 - 0307 : System RAM
  get_memory_ranges_iomem_cb: 0308 - 0308 : System RAM
  get_memory_ranges_iomem_cb: 0309 - 031f : System RAM
  get_memory_ranges_iomem_cb: 0320 - 033f : System RAM
  get_memory_ranges_iomem_cb: 0341 - 0589 : System RAM
  get_memory_ranges_iomem_cb: 058a - 058a : System RAM
  get_memory_ranges_iomem_cb: 058b - 058b : System RAM
  get_memory_ranges_iomem_cb: 058c - 0597 : System RAM
  get_memory_ranges_iomem_cb: 0598 - 05987fff : System RAM
  get_memory_ranges_iomem_cb: 05988000 - 0598bfff : System RAM
  get_memory_ranges_iomem_cb: 0598c000 - 05a0 : System RAM
  get_memory_ranges_iomem_cb: 05a1 - 05aa : System RAM
  get_memory_ranges_iomem_cb: 05ab - 05ca0fff : System RAM
  get_memory_ranges_iomem_cb: 05ca1000 - 08ca : System RAM
  get_memory_ranges_iomem_cb: 08cb - 08cf : System RAM

  ==AFTER PATCH: System RAM reported by kexec ==
  ubuntu@ubuntu:~$ sudo kexec -d -l /boot/vmlinuz-4.7.0-2-generic --reuse-cmd 
--initrd=/boot/initrd.img-4.7.0-2-generic | grep "System RAM"
  get_memory_ranges_iomem_cb: 0020 - 0020 : System RAM
  get_memory_ranges_iomem_cb: 0082 - 0307 : System RAM
  get_memory_ranges_iomem_cb: 0308 - 0308 : System RAM
  get_memory_ranges_iomem_cb: 0309 - 031f : System RAM
  get_memory_ranges_iomem_cb: 0320 - 033f : System RAM
  get_memory_ranges_iomem_cb: 0341 - 0589 : System RAM
  get_memory_ranges_iomem_cb: 058a - 058a : System RAM
  get_memory_ranges_iomem_cb: 058b - 058b : System RAM
  get_memory_ranges_iomem_cb: 058c - 0597 : System RAM
  get_memory_ranges_iomem_cb: 0598 - 05987fff : System RAM
  get_memory_ranges_iomem_cb: 05988000 -

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

2017-09-27 Thread Kleber Sacilotto de Souza

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

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

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

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

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

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

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

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

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

2017-09-27 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/1719888

Title:
  kernel BUG at /build/linux-
  s_bACt/linux-4.13.0/drivers/usb/usbip/vhci_hcd.c:683!

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  When using a usb flash disk via usbip it crashes with this bug

  ProblemType: KernelOops
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-12-generic 4.13.0-12.13
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  Annotation: Your system might become unstable now and might need to be 
restarted.
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Date: Wed Sep 27 06:24:09 2017
  Failure: oops
  InstallationDate: Installed on 2017-09-27 (0 days ago)
  InstallationMedia: Xubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170829.1)
  IwConfig:
   ens33 no wireless extensions.
   
   lono wireless extensions.
  MachineType: VMware, Inc. VMware Virtual Platform
  ProcFB: 0 svgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-12-generic 
root=UUID=33763e28-10a5-4446-afbd-8cb727ae9363 ro find_preseed=/preseed.cfg 
auto noprompt priority=critical locale=en_US quiet
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: kerneloops-daemon N/A
  RfKill:
   
  SourcePackage: linux
  Title: kernel BUG at 
/build/linux-s_bACt/linux-4.13.0/drivers/usb/usbip/vhci_hcd.c:683!
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/02/2015
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: 6.00
  dmi.board.name: 440BX Desktop Reference Platform
  dmi.board.vendor: Intel Corporation
  dmi.board.version: None
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 1
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd07/02/2015:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
  dmi.product.name: VMware Virtual Platform
  dmi.product.version: None
  dmi.sys.vendor: VMware, Inc.

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

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

[Kernel-packages] [Bug 1708409] Re: kdump service does not start after configure/reboot

** Tags removed: severity-high
** Tags added: severity-medium

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

Title:
  kdump service does not start after configure/reboot

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

Bug description:
  == Comment: #0 - Harish Sriram  - 2017-08-02 01:45:01 ==
  kdump service does not start after configure/reboot

  --Problem Description---
  kdump service does not start after configure/reboot. It has to be 
started/loaded manually, everytime after reboot.

  # kdump-config status
  current state   : Not ready to kdump

  
  ---uname output---
  Linux ltc-test-ci2 4.11.0-10-generic #15-Ubuntu SMP Thu Jun 29 15:02:54 UTC 
2017 ppc64le ppc64le ppc64le GNU/Linux 
   
  Machine Type/Model = Power 8/8247-22L 

  Additional Info-
  # cat /proc/cmdline
  root=UUID=974df602-c0e4-4e67-8853-78ad15884c59 ro console=tty0 
console=ttyS0,115200 quiet splash cgroup_enable=memory swapaccount=1 
crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M
   
  ---Steps to Reproduce---
  1. installed linux-crashdump
  2. edited the kdump-tools.cfg crashkernel cmdline to above
  3. update-grub
  4. reboot

  Expected:
  kdump-config to be loaded by default after reboot

  # kdump-config status
  current state   : Not ready to kdump

  # service kdump-tools status
  * kdump-tools.service - Kernel crash dump capture service
 Loaded: loaded (/lib/systemd/system/kdump-tools.service; enabled; vendor 
pres
 Active: inactive (dead)

  ...
  https://github.com/systemd/systemd/issues/6334

  systemd in artful is not properly picking up the unit files in 
  /etc/systemd/system/default.target.wants

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

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

[Kernel-packages] [Bug 1719853] Re: Plantronics P610 does not support sample rate reading

2017-09-27 Thread Tim De Pauw

Pasting logs from
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1622763/comments/29
:

[ 93.738138] usb 3-2: USB disconnect, device number 5
[ 103.950487] usb 3-4: new full-speed USB device number 6 using xhci_hcd
[ 104.228308] usb 3-4: New USB device found, idVendor=047f, idProduct=c02f
[ 104.228312] usb 3-4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 104.228314] usb 3-4: Product: Plantronics P610
[ 104.228316] usb 3-4: Manufacturer: Plantronics
[ 104.228317] usb 3-4: SerialNumber: D21FA3D2B38C144D91AF207D0A9A030D
[ 104.368289] input: Plantronics Plantronics P610 as 
/devices/pci:00/:00:14.0/usb3/3-4/3-4:1.3/0003:047F:C02F.0002/input/input18
[ 104.422797] plantronics 0003:047F:C02F.0002: input,hiddev0,hidraw0: USB HID 
v1.11 Device [Plantronics Plantronics P610] on usb-:00:14.0-4/input3
[ 104.955080] usb 3-4: 1:1: cannot get freq at ep 0x81
[ 104.955294] usb 3-4: 1:1: cannot get freq at ep 0x81
[ 104.958747] usb 3-4: 2:1: cannot get freq at ep 0x1
[ 104.958841] usb 3-4: 2:1: cannot set freq 44100 to ep 0x1
[ 104.969429] usb 3-4: 2:1: cannot get freq at ep 0x1
[ 104.969543] usb 3-4: 2:1: cannot set freq 44100 to ep 0x1
[ 104.973338] usb 3-4: 2:1: cannot get freq at ep 0x1
[ 104.973430] usb 3-4: 2:1: cannot set freq 44100 to ep 0x1
[ 104.977360] usb 3-4: 2:1: cannot get freq at ep 0x1
[ 104.977461] usb 3-4: 2:1: cannot set freq 44100 to ep 0x1
[ 104.981966] usb 3-4: 2:1: cannot get freq at ep 0x1
[ 104.982055] usb 3-4: 2:1: cannot set freq 44100 to ep 0x1
[ 104.985335] usb 3-4: 2:1: cannot get freq at ep 0x1
[ 104.985434] usb 3-4: 2:1: cannot set freq 44100 to ep 0x1
[ 104.989361] usb 3-4: 2:1: cannot get freq at ep 0x1
[ 104.989471] usb 3-4: 2:1: cannot set freq 44100 to ep 0x1
[ 104.993311] usb 3-4: 2:1: cannot get freq at ep 0x1
[ 104.993397] usb 3-4: 2:1: cannot set freq 44100 to ep 0x1
[ 104.997442] usb 3-4: 1:1: cannot get freq at ep 0x81
[ 104.997589] usb 3-4: 1:1: cannot set freq 44100 to ep 0x81
[ 104.999399] usb 3-4: 1:1: cannot get freq at ep 0x81
[ 104.999504] usb 3-4: 1:1: cannot set freq 44100 to ep 0x81
[ 105.001310] usb 3-4: 1:1: cannot get freq at ep 0x81
[ 105.001379] usb 3-4: 1:1: cannot set freq 44100 to ep 0x81
[ 105.003233] usb 3-4: 1:1: cannot get freq at ep 0x81
[ 105.003339] usb 3-4: 1:1: cannot set freq 44100 to ep 0x81

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

Title:
  Plantronics P610 does not support sample rate reading

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  As per
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1622763/comments/29
  and https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1709282 , I
  believe the USB ID 0x047F 0xC02F needs to be added to quirks.c in
  order for me to use my Plantronics P610. Thanks!

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

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

[Kernel-packages] [Bug 1718936] Re: Can't boot Artful 17.10 live images on XPS 15 (9560)

2017-09-27 Thread Hlini Melsteð Jóngeirsson

I was going to add that it should run on Intel by default. I updated the
image to the latest on the USB and tried again and it still hangs even
with the kernel parameters. "blacklist=nouveau
modprobe.blacklist=nouveau" It worked for you Anmar?

Cause I cannot get that to work here. Also this issue is set to "Fix
Released" What fix is that?

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

Title:
  Can't boot Artful 17.10 live images on XPS 15 (9560)

Status in linux package in Ubuntu:
  Fix Released

Bug description:
  I usually test Ubuntu beta releases. With Artful, I haven't been able
  to boot the image on my XPS 15 (9560) Dell laptop because the boot
  process stops half way.

  The boot proceeds properly if I pass the "nomodeset" kernel boot
  option but that won't work because there is no more hiDPI support and
  dual display doesn't work.

  This has been ongoing for several weeks, around the 4.12 kernel.
  Please fix it. It would be a shame for this product not to boot Artful
  out of the box.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-11-generic 4.13.0-11.12
  ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1
  Uname: Linux 4.13.0-11-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 1701 F pulseaudio
  CasperVersion: 1.384
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep 22 12:38:09 2017
  LiveMediaBuild: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170921)
  MachineType: Dell Inc. XPS 15 9560
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi 
file=/cdrom/preseed/username.seed boot=casper quiet splash --- nomodeset
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-11-generic N/A
   linux-backports-modules-4.13.0-11-generic  N/A
   linux-firmware 1.168
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/30/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.5.0
  dmi.board.name: 0JHP5H
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.5.0:bd08/30/2017:svnDellInc.:pnXPS159560:pvr:rvnDellInc.:rn0JHP5H:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 15 9560
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1719888] [NEW] kernel BUG at /build/linux-s_bACt/linux-4.13.0/drivers/usb/usbip/vhci_hcd.c:683!

Public bug reported:

When using a usb flash disk via usbip it crashes with this bug

ProblemType: KernelOops
DistroRelease: Ubuntu 17.10
Package: linux-image-4.13.0-12-generic 4.13.0-12.13
ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
Uname: Linux 4.13.0-12-generic x86_64
Annotation: Your system might become unstable now and might need to be 
restarted.
ApportVersion: 2.20.7-0ubuntu1
Architecture: amd64
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
Date: Wed Sep 27 06:24:09 2017
Failure: oops
InstallationDate: Installed on 2017-09-27 (0 days ago)
InstallationMedia: Xubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170829.1)
IwConfig:
 ens33 no wireless extensions.
 
 lono wireless extensions.
MachineType: VMware, Inc. VMware Virtual Platform
ProcFB: 0 svgadrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-12-generic 
root=UUID=33763e28-10a5-4446-afbd-8cb727ae9363 ro find_preseed=/preseed.cfg 
auto noprompt priority=critical locale=en_US quiet
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions: kerneloops-daemon N/A
RfKill:
 
SourcePackage: linux
Title: kernel BUG at 
/build/linux-s_bACt/linux-4.13.0/drivers/usb/usbip/vhci_hcd.c:683!
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/02/2015
dmi.bios.vendor: Phoenix Technologies LTD
dmi.bios.version: 6.00
dmi.board.name: 440BX Desktop Reference Platform
dmi.board.vendor: Intel Corporation
dmi.board.version: None
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 1
dmi.chassis.vendor: No Enclosure
dmi.chassis.version: N/A
dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd07/02/2015:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
dmi.product.name: VMware Virtual Platform
dmi.product.version: None
dmi.sys.vendor: VMware, Inc.

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


** Tags: amd64 apport-kerneloops artful kernel-driver-vhci.hcd kernel-oops

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

Title:
  kernel BUG at /build/linux-
  s_bACt/linux-4.13.0/drivers/usb/usbip/vhci_hcd.c:683!

Status in linux package in Ubuntu:
  New

Bug description:
  When using a usb flash disk via usbip it crashes with this bug

  ProblemType: KernelOops
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-12-generic 4.13.0-12.13
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  Annotation: Your system might become unstable now and might need to be 
restarted.
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Date: Wed Sep 27 06:24:09 2017
  Failure: oops
  InstallationDate: Installed on 2017-09-27 (0 days ago)
  InstallationMedia: Xubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170829.1)
  IwConfig:
   ens33 no wireless extensions.
   
   lono wireless extensions.
  MachineType: VMware, Inc. VMware Virtual Platform
  ProcFB: 0 svgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-12-generic 
root=UUID=33763e28-10a5-4446-afbd-8cb727ae9363 ro find_preseed=/preseed.cfg 
auto noprompt priority=critical locale=en_US quiet
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: kerneloops-daemon N/A
  RfKill:
   
  SourcePackage: linux
  Title: kernel BUG at 
/build/linux-s_bACt/linux-4.13.0/drivers/usb/usbip/vhci_hcd.c:683!
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/02/2015
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: 6.00
  dmi.board.name: 440BX Desktop Reference Platform
  dmi.board.vendor: Intel Corporation
  dmi.board.version: None
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 1
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd07/02/2015:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
  dmi.product.name: VMware Virtual Platform
  dmi.product.version: None
  dmi.sys.vendor: VMware, Inc.

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

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

[Kernel-packages] [Bug 1696154] Re: [17.10 FEAT] Sign POWER host/NV kernels

2017-09-27 Thread Steve Langasek

Attached is the ESL db update for Canonical's POWER SecureBoot signing
key.  It is signed with Canonical's KEK key, which will be provided to
IBM out of band to ensure integrity of the delivery channel.

** Attachment added: "Canonical-POWER-SB-20170926.esl.signed"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1696154/+attachment/4957646/+files/Canonical-POWER-SB-20170926.esl.signed

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

Title:
  [17.10 FEAT] Sign POWER host/NV kernels

Status in Launchpad itself:
  Fix Committed
Status in The Ubuntu-power-systems project:
  In Progress
Status in linux package in Ubuntu:
  In Progress
Status in linux-signed package in Ubuntu:
  In Progress

Bug description:
  Feature Description:

  Sign POWER host and NV kernels with sign-file in anticipation of POWER
  secure boot.  Provide the  associated certificate.  Ideally it would
  be possible to reuse the UEFI shim private key and certificate used to
  sign and verify x86_64 kernels.  More details to follow.  Guest
  kernels will be addressed in a future separate feature request.

  
  Business Case: 

  As a system administrator I want to verify the integrity of my kernels
  so that I can prevent malicious kernels from being executed.

  Use Case:

  Signed POWER kernels will be validated by OPAL as OpenPOWER systems
  boot when keys are properly installed and the system is booted in
  secure mode.

  
  Test Case:

  Sign and install a POWER kernel on an OpenPOWER machine with a
  firmware level that supports secure boot.  Install a PK, distro KEK
  certificat, and distro DB certificate.  Boot the system and verify
  that it will boot the kernel.  Negative tests:  Separately remove the
  signature, install an usigned kernel, and modify the kernel image and
  test that the kernel will not boot.

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

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

[Kernel-packages] [Bug 1716301] Re: wifi driver: mt7601u not work on 16.04

2017-09-27 Thread chenzero

What do you mean "Artful live image" ? 
do you mean boot computer with the latest release ISO ?
Ubuntu 17.04 ISO on the page: https://www.ubuntu.com/download/desktop

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

Title:
  wifi driver: mt7601u not work on 16.04

Status in linux package in Ubuntu:
  Confirmed
Status in usb-modeswitch-data package in Ubuntu:
  New

Bug description:
  In the beginning, when the adapter is pluged in, it's mounted as a disk 
including driver files for Windows, and
  $> lsusb
  Bus 003 Device 010: ID 148f:2878 Ralink Technology, Corp.

  after eject the disk,
  $> lsusb
  Bus 003 Device 011: ID 148f:7601 Ralink Technology, Corp. MT7601U Wireless 
Adapter

  I tried following 3 drivers:
  1) the default mt7601u included in the kernel: 4.4.0-91-generic
  after eject the disk,
  $> lsmod|grep mt
  mt7601u 102400 0
  mac80211 737280 1 mt7601u
  cfg80211 565248 2 mac80211,mt7601u
  binfmt_misc 20480 1
  $> modinfo mt7601u
  filename: 
/lib/modules/4.4.0-91-generic/kernel/drivers/net/wireless/mediatek/mt7601u/mt7601u.ko
  srcversion: E8B632D369E0C2A9F1CF7D8
  alias: usb:v7392p7710d*dc*dsc*dp*ic*isc*ip*in*
  ..
  depends: mac80211,cfg80211
  intree: Y
  vermagic: 4.4.0-91-generic SMP mod_unload modversions

  $> dmesg
  // begin
  [ 4581.094119] usb 3-4: USB disconnect, device number 6
  [ 4584.872751] usb 3-4: new high-speed USB device number 7 using xhci_hcd
  [ 4585.001408] usb 3-4: New USB device found, idVendor=148f, idProduct=2878
  [ 4585.001413] usb 3-4: New USB device strings: Mfr=1, Product=2, 
SerialNumber=0
  [ 4585.001416] usb 3-4: Product: Љ
  [ 4585.001418] usb 3-4: Manufacturer: Љ
  [ 4585.001753] usb-storage 3-4:1.0: USB Mass Storage device detected
  [ 4585.001873] scsi host6: usb-storage 3-4:1.0
  [ 4586.001122] scsi 6:0:0:0: CD-ROM MediaTek Flash autorun 0.01 PQ: 0 ANSI: 0 
CCS
  [ 4586.001978] sr 6:0:0:0: [sr0] scsi3-mmc drive: 52x/52x cd/rw xa/form2 cdda 
tray
  [ 4586.002529] sr 6:0:0:0: Attached scsi CD-ROM sr0
  [ 4586.002716] sr 6:0:0:0: Attached scsi generic sg1 type 5
  [ 4619.658385] ISO 9660 Extensions: Microsoft Joliet Level 3
  [ 4619.691737] ISOFS: changing to secondary root
  [ 4691.563347] usb 3-4: USB disconnect, device number 7
  [ 4693.638315] usb 3-4: new high-speed USB device number 8 using xhci_hcd
  [ 4693.766896] usb 3-4: New USB device found, idVendor=148f, idProduct=2878
  [ 4693.766901] usb 3-4: New USB device strings: Mfr=1, Product=2, 
SerialNumber=0
  [ 4693.766903] usb 3-4: Product: Љ
  [ 4693.766905] usb 3-4: Manufacturer: Љ
  [ 4693.767338] usb-storage 3-4:1.0: USB Mass Storage device detected
  [ 4693.768063] scsi host7: usb-storage 3-4:1.0
  [ 4694.766737] scsi 7:0:0:0: CD-ROM MediaTek Flash autorun 0.01 PQ: 0 ANSI: 0 
CCS
  [ 4694.767423] sr 7:0:0:0: [sr0] scsi3-mmc drive: 52x/52x cd/rw xa/form2 cdda 
tray
  [ 4694.767908] sr 7:0:0:0: Attached scsi CD-ROM sr0
  [ 4694.768147] sr 7:0:0:0: Attached scsi generic sg1 type 5
  [ 4728.418255] ISO 9660 Extensions: Microsoft Joliet Level 3
  [ 4728.427856] ISOFS: changing to secondary root
  [ 4733.824182] sr 7:0:0:0: [sr0] tag#0 FAILED Result: hostbyte=DID_ERROR 
driverbyte=DRIVER_OK
  [ 4733.824190] sr 7:0:0:0: [sr0] tag#0 CDB: Start/Stop Unit 1b 00 00 00 02 00
  [ 4733.824218] usb 3-4: USB disconnect, device number 8
  [ 4733.824281] sr 7:0:0:0: [sr0] tag#0 FAILED Result: hostbyte=DID_ERROR 
driverbyte=DRIVER_OK
  [ 4733.824291] sr 7:0:0:0: [sr0] tag#0 CDB: Prevent/Allow Medium Removal 1e 
00 00 00 00 00
  [ 4734.099901] usb 3-4: new high-speed USB device number 9 using xhci_hcd
  [ 4734.238749] usb 3-4: New USB device found, idVendor=148f, idProduct=7601
  [ 4734.238754] usb 3-4: New USB device strings: Mfr=1, Product=2, 
SerialNumber=3
  [ 4734.238757] usb 3-4: Product: 802.11 n WLAN
  [ 4734.238772] usb 3-4: Manufacturer: MediaTek
  [ 4734.238775] usb 3-4: SerialNumber: 1.0
  [ 4735.432096] usb 3-4: reset high-speed USB device number 9 using xhci_hcd
  [ 4735.562543] mt7601u 3-4:1.0: ASIC revision: 76010001 MAC revision: 76010500
  [ 4735.563089] mt7601u 3-4:1.0: Firmware Version: 0.1.00 Build: 7640 Build 
time: 201302052146
  [ 4739.011624] mt7601u 3-4:1.0: Vendor request req:07 off:09a8 failed:-110
  [ 4742.131399] mt7601u 3-4:1.0: Vendor request req:02 off:09a8 failed:-110
  [ 4745.251254] mt7601u 3-4:1.0: Vendor request req:07 off:0734 failed:-110
  [ 4748.371056] mt7601u 3-4:1.0: Vendor request req:42 off:0230 failed:-110
  [ 4751.490880] mt7601u 3-4:1.0: Vendor request req:07 off:0080 failed:-110
  [ 4754.610694] mt7601u 3-4:1.0: Vendor request req:02 off:0080 failed:-110
  [ 4757.730501] mt7601u 3-4:1.0: Vendor request req:02 off:0080 failed:-110
  [ 4757.730548] mt7601u: probe of 3-4:1.0 failed with error -110
  [ 4757.730870] usbcore: registered new interface driver mt7601u
  // end

[Kernel-packages] [Bug 1646277] Re: Xenial server 16.04.x will have a black screen after PXE installation

2017-09-27 Thread NancyHsu

The bug didn't happened on test kernel 4.1.0-1.
commit: d9e5b220f962910fb37133bde7e857ce478daf3e

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

Title:
  Xenial server 16.04.x will have a black screen after PXE installation

Status in debian-installer package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in debian-installer source package in Xenial:
  Confirmed
Status in linux source package in Xenial:
  Confirmed

Bug description:
  The display will keep black screen after install 16.04.x via PXE(need
  use "Ctrl+Alt+F1" to change to terminal 1, then can see text mode
  screen)

  Quanta team is installing Xenial server using PXE boot.   After the
  installation, the console will show a black screen.   Hitting ctl-
  alt-f1 displays the text mode screen OK.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1646277/+subscriptions

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

[Kernel-packages] [Bug 1719733] Re: stale file handle when restarting ntp on overlayfs (maas)

2017-09-27 Thread Po-Hsu Lin

I can still see this error while deploying ARM64 Artful today

[  121.632228] cloud-init[2022]: ERROR: ld.so: object 'libeatmydata.so' from 
LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.
[  122.172457] cloud-init[2022]: Created symlink 
/etc/systemd/system/multi-user.target.wants/ntp.service → 
/lib/systemd/system/ntp.service.
[  123.362260] cloud-init[2022]: Processing triggers for libc-bin 
(2.26-0ubuntu1) ...
[  123.396725] cloud-init[2022]: Processing triggers for ureadahead 
(0.100.0-20) ...
[  123.929345] cloud-init[2022]: Processing triggers for systemd 
(234-2ubuntu10) ...
[  124.235965] cloud-init[2022]: dpkg: error: error removing old backup file 
'/var/lib/dpkg/status-old': Stale file handle
[  128.358899] cloud-init[2022]: E: Sub-process /usr/bin/dpkg returned an error 
code (2)

The interesting thing is that this issue seem to be only affecting the
ARM64 nodes, as I can deploy it on a amd64/i386 node (affecting arm64
image maybe?)

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

Title:
  stale file handle when restarting ntp on overlayfs (maas)

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

Bug description:
  MAAS is currently failing to deploy artful.

  [0.00] Kernel command line: nomodeset
  iscsi_target_name=iqn.2004-05.com.ubuntu:maas:ephemeral-ubuntu-
  ppc64el-ga-17.10-artful-daily iscsi_target_ip=10.245.71.3
  iscsi_target_port=3260 iscsi_initiator=wichita ip=wichita:BOOTIF
  ip6=off ro root=/dev/disk/by-path/ip-10.245.71.3:3260-iscsi-
  iqn.2004-05.com.ubuntu:maas:ephemeral-ubuntu-ppc64el-ga-17.10-artful-
  daily-lun-1 overlayroot=tmpfs overlayroot_cfgdisk=disabled
  cc:{'datasource_list': ['MAAS']}end_cc cloud-config-
  url=http://10.245.71.3:5240/MAAS/metadata/latest/by-id/node-45f9009a-
  0bc4-11e6-9882-00163e5b6994/?op=get_preseed apparmor=0
  log_host=10.245.71.3 log_port=514 --- console=hvc0 BOOTIF=01-6c-ae-
  8b-01-e9-00^M

  ...

  [   60.064994] cloud-init[4805]: ERROR: ld.so: object 'libeatmydata.so' from 
LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.^M
  [   60.216965] cloud-init[4805]: Created symlink 
/etc/systemd/system/multi-user.target.wants/ntp.service → 
/lib/systemd/system/ntp.service.^M
  [   60.837682] cloud-init[4805]: Processing triggers for libc-bin 
(2.26-0ubuntu1) ...^M
  [   60.851733] cloud-init[4805]: Processing triggers for ureadahead 
(0.100.0-20) ...^M
  [   61.003403] cloud-init[4805]: Processing triggers for systemd 
(234-2ubuntu10) ...^M
  [   61.183944] cloud-init[4805]: dpkg: error: error removing old backup file 
'/var/lib/dpkg/status-old': Stale file handle^M
  [   62.202113] cloud-init[4805]: E: Sub-process /usr/bin/dpkg returned an 
error code (2)^M
  @

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-11-generic 4.13.0-11.12
  ProcVersionSignature: User Name 4.13.0-11.12-generic 4.13.1
  Uname: Linux 4.13.0-11-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Sep 26 20:32 seq
   crw-rw 1 root audio 116, 33 Sep 26 20:32 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  Date: Tue Sep 26 20:33:41 2017
  Ec2AMI: ami-0181
  Ec2AMIManifest: FIXME
  Ec2AvailabilityZone: nova
  Ec2InstanceType: m1.small
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lsusb:
   Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: OpenStack Foundation OpenStack Nova
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-11-generic 
root=LABEL=cloudimg-rootfs ro console=tty1 console=ttyS0
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-11-generic N/A
   linux-backports-modules-4.13.0-11-generic  N/A
   linux-firmware N/A
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/01/2014
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: 1.10.1-1ubuntu1~cloud0
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-i440fx-zesty
  dmi.modalias: 
dmi:bvnSeaBIOS:bvr1.10.1-1ubuntu1~cloud0:bd04/01/2014:svnOpenStackFoundation:pnOpenStackNova:pvr15.0.2:cvnQEMU:ct1:cvrpc-i440fx-zesty:

[Kernel-packages] [Bug 1719853] [NEW] Plantronics P610 does not support sample rate reading

2017-09-27 Thread Tim De Pauw

Public bug reported:

As per
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1622763/comments/29
and https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1709282 , I
believe the USB ID 0x047F 0xC02F needs to be added to quirks.c in order
for me to use my Plantronics P610. Thanks!

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: 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/1719853

Title:
  Plantronics P610 does not support sample rate reading

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  As per
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1622763/comments/29
  and https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1709282 , I
  believe the USB ID 0x047F 0xC02F needs to be added to quirks.c in
  order for me to use my Plantronics P610. Thanks!

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

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

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

2017-09-27 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 1719853

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

Title:
  Plantronics P610 does not support sample rate reading

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  As per
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1622763/comments/29
  and https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1709282 , I
  believe the USB ID 0x047F 0xC02F needs to be added to quirks.c in
  order for me to use my Plantronics P610. Thanks!

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

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

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

2017-09-27 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/1719844

Title:
  kernel BUG at /build/linux-
  Fk60NP/linux-4.10.0/include/linux/swapops.h:129!

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Full system freeze under almost no load.

  Running google-chrome and Pycharm.

  Traceback in syslog:
  Sep 27 11:06:36 toto kernel: [66558.227374] [ cut here 
]
  Sep 27 11:06:36 toto kernel: [66558.227450] kernel BUG at 
/build/linux-Fk60NP/linux-4.10.0/include/linux/swapops.h:129!
  Sep 27 11:06:36 toto kernel: [66558.227472] invalid opcode:  [#1] SMP
  Sep 27 11:06:36 toto kernel: [66558.227483] Modules linked in: btrfs xor 
raid6_pq ufs qnx4 hfsplus hfs minix ntfs msdos jfs xfs libcrc32c cpuid joydev 
hid_logitech_hidpp hid_logitech_dj intel_rapl x86_pkg_temp_thermal 
intel_powerclamp coretemp snd_hda_codec_realtek snd_hda_codec_generic kvm_intel 
kvm snd_hda_intel irqbypass snd_hda_codec crct10dif_pclmul snd_hda_core 
snd_hwdep cr
  c32_pclmul snd_pcm ghash_clmulni_intel snd_seq_midi pcbc snd_seq_midi_event 
snd_rawmidi snd_seq aesni_intel aes_x86_64 snd_seq_device snd_timer dcdbas 
crypto_simd glue_helper cryptd intel_cstate intel_rapl_perf serio_raw 
input_leds snd lpc_ich soundcore shpchp mac_hid mei_me mei parport_pc ppdev lp 
parport ip_tables x_tables autofs4 hid_generic usbhid hid amdkfd amd_iommu_v2 
rade
  on i2c_algo_bit ttm drm_kms_helper syscopyarea sysfillrect psmouse sysimgblt
  Sep 27 11:06:36 toto kernel: [66558.227676]  fb_sys_fops e1000e ahci e1000 
drm libahci ptp pps_core fjes video
  Sep 27 11:06:36 toto kernel: [66558.227699] CPU: 2 PID: 26031 Comm: chrome 
Not tainted 4.10.0-19-generic #21-Ubuntu
  Sep 27 11:06:36 toto kernel: [66558.227718] Hardware name: Dell Inc. OptiPlex 
990/06D7TR, BIOS A03 04/11/2011
  Sep 27 11:06:36 toto kernel: [66558.227737] task: 9afc1ae52d00 
task.stack: c1ebc808
  Sep 27 11:06:36 toto kernel: [66558.227756] RIP: 
0010:__migration_entry_wait+0x16a/0x180
  Sep 27 11:06:36 toto kernel: [66558.227770] RSP: :c1ebc8083d68 
EFLAGS: 00010246
  Sep 27 11:06:36 toto kernel: [66558.227784] RAX: 000fc0048078 RBX: 
f50cc31604b0 RCX: f50cc31604b0
  Sep 27 11:06:36 toto kernel: [66558.227803] RDX: 0001 RSI: 
9afcc58120a0 RDI: f50cc18f0500
  Sep 27 11:06:36 toto kernel: [66558.227821] RBP: c1ebc8083d80 R08: 
9afd233ab640 R09: 9afd233ab640
  Sep 27 11:06:36 toto kernel: [66558.227839] R10: 0008 R11: 
7f7d4d3403b0 R12: f50cc18f0500
  Sep 27 11:06:36 toto kernel: [66558.227857] R13: 3e063c14 R14: 
c1ebc8083e30 R15: 9afc274e24b0
  Sep 27 11:06:36 toto kernel: [66558.227876] FS:  7f7d4d8e5b00() 
GS:9afd2928() knlGS:
  Sep 27 11:06:36 toto kernel: [66558.227897] CS:  0010 DS:  ES:  CR0: 
80050033
  Sep 27 11:06:36 toto kernel: [66558.227912] CR2: 2e6ce3c146e8 CR3: 
27486000 CR4: 000406e0
  Sep 27 11:06:36 toto kernel: [66558.227930] Call Trace:
  Sep 27 11:06:36 toto kernel: [66558.227939]  migration_entry_wait+0x74/0x80
  Sep 27 11:06:36 toto kernel: [66558.227953]  do_swap_page+0x5b3/0x770
  Sep 27 11:06:36 toto kernel: [66558.227963]  ? do_swap_page+0xb/0x770
  Sep 27 11:06:36 toto kernel: [66558.227974]  handle_mm_fault+0x873/0x1360
  Sep 27 11:06:36 toto kernel: [66558.227987]  __do_page_fault+0x23e/0x4e0
  Sep 27 11:06:36 toto kernel: [66558.227998]  do_page_fault+0x22/0x30
  Sep 27 11:06:36 toto kernel: [66558.228010]  page_fault+0x28/0x30
  Sep 27 11:06:36 toto kernel: [66558.228020] RIP: 0033:0x5596fffb1b95
  Sep 27 11:06:36 toto kernel: [66558.228030] RSP: 002b:7ffc942f4f20 
EFLAGS: 00010283
  Sep 27 11:06:36 toto kernel: [66558.228044] RAX: 001e RBX: 
0002acb7ffd8 RCX: 0007
  Sep 27 11:06:36 toto kernel: [66558.228062] RDX:  RSI: 
000a RDI: 00a0
  Sep 27 11:06:36 toto kernel: [66558.228081] RBP: 2e6ce3c146e0 R08: 
c3ff R09: 0002
  Sep 27 11:06:36 toto kernel: [66558.228099] R10: 0008 R11: 
7f7d4d3403b0 R12: 00a0
  Sep 27 11:06:36 toto kernel: [66558.228118] R13: 7ffc942f5580 R14: 
2e6ce329e128 R15: 2e6ce367cdc0
  Sep 27 11:06:36 toto kernel: [66558.228136] Code: ff ff ff 4c 89 e7 e8 96 a2 
f8 ff e9 3c ff ff ff 85 d2 0f 84 2a ff ff ff 8d 4a 01 89 d0 f0 41 0f b1 4d 00 
39 d0 74 81 89 c2 eb e5 <0f> 0b 4c 89 e7 e8 0c fb f9 ff eb b8 4c 8d 60 ff 4c 8d 
68 1b eb 
  Sep 27 11:06:36 toto kernel: [66558.228199] RIP: 
__migration_entry_wait+0x16a/0x180 RSP: c1ebc8083d68
  Sep 27 11:06:36 toto kernel: [66558.234716] ---[ end trace e96bebf99e91814f 
]---


  Description:  Ubuntu 17.04
  Release:  17.04

  Looks like it

[Kernel-packages] [Bug 1719844] [NEW] kernel BUG at /build/linux-Fk60NP/linux-4.10.0/include/linux/swapops.h:129!

2017-09-27 Thread Richard

Public bug reported:

Full system freeze under almost no load.

Running google-chrome and Pycharm.

Traceback in syslog:
Sep 27 11:06:36 toto kernel: [66558.227374] [ cut here ]
Sep 27 11:06:36 toto kernel: [66558.227450] kernel BUG at 
/build/linux-Fk60NP/linux-4.10.0/include/linux/swapops.h:129!
Sep 27 11:06:36 toto kernel: [66558.227472] invalid opcode:  [#1] SMP
Sep 27 11:06:36 toto kernel: [66558.227483] Modules linked in: btrfs xor 
raid6_pq ufs qnx4 hfsplus hfs minix ntfs msdos jfs xfs libcrc32c cpuid joydev 
hid_logitech_hidpp hid_logitech_dj intel_rapl x86_pkg_temp_thermal 
intel_powerclamp coretemp snd_hda_codec_realtek snd_hda_codec_generic kvm_intel 
kvm snd_hda_intel irqbypass snd_hda_codec crct10dif_pclmul snd_hda_core 
snd_hwdep cr
c32_pclmul snd_pcm ghash_clmulni_intel snd_seq_midi pcbc snd_seq_midi_event 
snd_rawmidi snd_seq aesni_intel aes_x86_64 snd_seq_device snd_timer dcdbas 
crypto_simd glue_helper cryptd intel_cstate intel_rapl_perf serio_raw 
input_leds snd lpc_ich soundcore shpchp mac_hid mei_me mei parport_pc ppdev lp 
parport ip_tables x_tables autofs4 hid_generic usbhid hid amdkfd amd_iommu_v2 
rade
on i2c_algo_bit ttm drm_kms_helper syscopyarea sysfillrect psmouse sysimgblt
Sep 27 11:06:36 toto kernel: [66558.227676]  fb_sys_fops e1000e ahci e1000 drm 
libahci ptp pps_core fjes video
Sep 27 11:06:36 toto kernel: [66558.227699] CPU: 2 PID: 26031 Comm: chrome Not 
tainted 4.10.0-19-generic #21-Ubuntu
Sep 27 11:06:36 toto kernel: [66558.227718] Hardware name: Dell Inc. OptiPlex 
990/06D7TR, BIOS A03 04/11/2011
Sep 27 11:06:36 toto kernel: [66558.227737] task: 9afc1ae52d00 task.stack: 
c1ebc808
Sep 27 11:06:36 toto kernel: [66558.227756] RIP: 
0010:__migration_entry_wait+0x16a/0x180
Sep 27 11:06:36 toto kernel: [66558.227770] RSP: :c1ebc8083d68 EFLAGS: 
00010246
Sep 27 11:06:36 toto kernel: [66558.227784] RAX: 000fc0048078 RBX: 
f50cc31604b0 RCX: f50cc31604b0
Sep 27 11:06:36 toto kernel: [66558.227803] RDX: 0001 RSI: 
9afcc58120a0 RDI: f50cc18f0500
Sep 27 11:06:36 toto kernel: [66558.227821] RBP: c1ebc8083d80 R08: 
9afd233ab640 R09: 9afd233ab640
Sep 27 11:06:36 toto kernel: [66558.227839] R10: 0008 R11: 
7f7d4d3403b0 R12: f50cc18f0500
Sep 27 11:06:36 toto kernel: [66558.227857] R13: 3e063c14 R14: 
c1ebc8083e30 R15: 9afc274e24b0
Sep 27 11:06:36 toto kernel: [66558.227876] FS:  7f7d4d8e5b00() 
GS:9afd2928() knlGS:
Sep 27 11:06:36 toto kernel: [66558.227897] CS:  0010 DS:  ES:  CR0: 
80050033
Sep 27 11:06:36 toto kernel: [66558.227912] CR2: 2e6ce3c146e8 CR3: 
27486000 CR4: 000406e0
Sep 27 11:06:36 toto kernel: [66558.227930] Call Trace:
Sep 27 11:06:36 toto kernel: [66558.227939]  migration_entry_wait+0x74/0x80
Sep 27 11:06:36 toto kernel: [66558.227953]  do_swap_page+0x5b3/0x770
Sep 27 11:06:36 toto kernel: [66558.227963]  ? do_swap_page+0xb/0x770
Sep 27 11:06:36 toto kernel: [66558.227974]  handle_mm_fault+0x873/0x1360
Sep 27 11:06:36 toto kernel: [66558.227987]  __do_page_fault+0x23e/0x4e0
Sep 27 11:06:36 toto kernel: [66558.227998]  do_page_fault+0x22/0x30
Sep 27 11:06:36 toto kernel: [66558.228010]  page_fault+0x28/0x30
Sep 27 11:06:36 toto kernel: [66558.228020] RIP: 0033:0x5596fffb1b95
Sep 27 11:06:36 toto kernel: [66558.228030] RSP: 002b:7ffc942f4f20 EFLAGS: 
00010283
Sep 27 11:06:36 toto kernel: [66558.228044] RAX: 001e RBX: 
0002acb7ffd8 RCX: 0007
Sep 27 11:06:36 toto kernel: [66558.228062] RDX:  RSI: 
000a RDI: 00a0
Sep 27 11:06:36 toto kernel: [66558.228081] RBP: 2e6ce3c146e0 R08: 
c3ff R09: 0002
Sep 27 11:06:36 toto kernel: [66558.228099] R10: 0008 R11: 
7f7d4d3403b0 R12: 00a0
Sep 27 11:06:36 toto kernel: [66558.228118] R13: 7ffc942f5580 R14: 
2e6ce329e128 R15: 2e6ce367cdc0
Sep 27 11:06:36 toto kernel: [66558.228136] Code: ff ff ff 4c 89 e7 e8 96 a2 f8 
ff e9 3c ff ff ff 85 d2 0f 84 2a ff ff ff 8d 4a 01 89 d0 f0 41 0f b1 4d 00 39 
d0 74 81 89 c2 eb e5 <0f> 0b 4c 89 e7 e8 0c fb f9 ff eb b8 4c 8d 60 ff 4c 8d 68 
1b eb 
Sep 27 11:06:36 toto kernel: [66558.228199] RIP: 
__migration_entry_wait+0x16a/0x180 RSP: c1ebc8083d68
Sep 27 11:06:36 toto kernel: [66558.234716] ---[ end trace e96bebf99e91814f ]---


Description:Ubuntu 17.04
Release:17.04

Looks like it might be a regression of:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1674838

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: linux-image-4.10.0-35-generic 4.10.0-35.39
ProcVersionSignature: Ubuntu 4.10.0-35.39-generic 4.10.17
Uname: Linux 4.10.0-35-generic x86_64
ApportVersion: 2.20.4-0ubuntu4.5
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  rjt1809 F pulseaudio
CurrentDesktop: Unity:Unity7
Date: Wed

[Kernel-packages] [Bug 1705493] Re: [4.4][backport] Multiple partitions are not supported on a bcache device

2017-09-27 Thread Ante Karamatić

** Tags removed: cpec
** Tags added: cpe-onsite

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

Title:
  [4.4][backport] Multiple partitions are not supported on a bcache
  device

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

Bug description:
  Support for adding partitions on bcache devices only landed in 4.10:

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

  Although it is a small change, it is not backported to any of the
  xenial kernels and it only exists naturally in 4.10.

  ➜ ubuntu-xenial git:(master) git tag 
--contains=b8c0d911ac5285e6be8967713271a51bdc5a936a
  Ubuntu-hwe-4.10.0-13.15_16.04.2
  Ubuntu-hwe-4.10.0-14.16_16.04.1
  Ubuntu-hwe-4.10.0-19.21_16.04.1
  Ubuntu-hwe-4.10.0-20.22_16.04.1
  Ubuntu-hwe-4.10.0-21.23_16.04.1
  Ubuntu-hwe-4.10.0-22.24_16.04.1
  Ubuntu-hwe-4.10.0-25.29_16.04.1
  Ubuntu-hwe-4.10.0-26.30_16.04.1
  Ubuntu-hwe-4.10.0-28.32_16.04.1
  Ubuntu-hwe-edge-4.10.0-9.11_16.04.2
  Ubuntu-lts-4.10.0-10.12_16.04.1
  Ubuntu-lts-4.10.0-11.13_16.04.1
  Ubuntu-lts-4.10.0-12.14_16.04.1
  Ubuntu-lts-4.10.0-13.15_16.04.1
  Ubuntu-lts-4.10.0-7.9_16.04.1
  Ubuntu-lts-4.10.0-8.10_16.04.1
  Ubuntu-lts-4.10.0-9.11_16.04.1
  Ubuntu-lts-4.10.0-9.11_16.04.2

  This will prevent usage of multiple partitions on the same device
  which is the case when data and journal are collocated.

  Also, the lack of that feature prevents dmcrypt usage as multiple
  partitions are created on a device in this case.

  
  Could that be backported to the 4.4 kernel?

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

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

[Kernel-packages] [Bug 1718713] Re: upon reboot monitor came up with flickerty screen

2017-09-27 Thread BertN45

Forgot to mention the other Ubuntu Betas (L-, X- and Mate) have no
problem and work normally.

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

Title:
  upon reboot monitor came up with flickerty screen

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After the  upgrade of kernel and reboot the VT went black with one
  line of verbose code  then started to flash  with full screen of code
  at least 6 times , top down, bottom up. Then gdm screen and was able
  to logon.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-11-generic 4.13.0-11.12
  ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1
  Uname: Linux 4.13.0-11-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  ventrical   1935 F pulseaudio
   /dev/snd/controlC0:  ventrical   1935 F pulseaudio
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Thu Sep 21 11:26:13 2017
  HibernationDevice: RESUME=UUID=73906ed5-985c-4166-9fc2-13fb389012cf
  InstallationDate: Installed on 2017-09-05 (16 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170820)
  IwConfig:
   lono wireless extensions.
   
   enp4s0no wireless extensions.
  MachineType: Dell Inc. Precision WorkStation T3400
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-11-generic 
root=UUID=cdef7dd2-7ccb-446a-a39a-df77fea13ef0 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-11-generic N/A
   linux-backports-modules-4.13.0-11-generic  N/A
   linux-firmware 1.168
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/31/2008
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A03
  dmi.board.name: 0TP412
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 7
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA03:bd01/31/2008:svnDellInc.:pnPrecisionWorkStationT3400:pvr:rvnDellInc.:rn0TP412:rvr:cvnDellInc.:ct7:cvr:
  dmi.product.name: Precision WorkStation T3400
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1718713] Re: upon reboot monitor came up with flickerty screen

2017-09-27 Thread BertN45

I have the same problem running the Ubuntu Beta in Virtualbox with as far as I
remember 4.13.0.11. All other Ubuntu Betas (L-, X- and Mate) did use that Linux
version too. I tried a fresh install from the latest second daily build of 26-9
with the same result. The symptom is a VM-screen that switches from size 4-6
times and disk and network lights of Vbox status bar died out and we are left
with a black screen.
The host is Ubuntu 16.04 and Vbox is 5.1.28.
I can't create a memory dump, since CTR + ALT + Fn is catched by the Host
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/1718713

Title:
upon reboot monitor came up with flickerty screen

Status in linux package in Ubuntu:
Confirmed

Bug description:
After the upgrade of kernel and reboot the VT went black with one
line of verbose code then started to flash with full screen of code
at least 6 times , top down, bottom up. Then gdm screen and was able
to logon.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: linux-image-4.13.0-11-generic 4.13.0-11.12
ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1
Uname: Linux 4.13.0-11-generic x86_64
ApportVersion: 2.20.7-0ubuntu1
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: ventrical 1935 F pulseaudio
/dev/snd/controlC0: ventrical 1935 F pulseaudio
CurrentDesktop: Unity:Unity7:ubuntu
Date: Thu Sep 21 11:26:13 2017
HibernationDevice: RESUME=UUID=73906ed5-985c-4166-9fc2-13fb389012cf
InstallationDate: Installed on 2017-09-05 (16 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170820)
IwConfig:
lono wireless extensions.

enp4s0no wireless extensions.
MachineType: Dell Inc. Precision WorkStation T3400
ProcFB: 0 nouveaufb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-11-generic
root=UUID=cdef7dd2-7ccb-446a-a39a-df77fea13ef0 ro quiet splash vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-4.13.0-11-generic N/A
linux-backports-modules-4.13.0-11-generic N/A
linux-firmware 1.168
RfKill:

SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/31/2008
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A03
dmi.board.name: 0TP412
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 7
dmi.chassis.vendor: Dell Inc.
dmi.modalias:
dmi:bvnDellInc.:bvrA03:bd01/31/2008:svnDellInc.:pnPrecisionWorkStationT3400:pvr:rvnDellInc.:rn0TP412:rvr:cvnDellInc.:ct7:cvr:
dmi.product.name: Precision WorkStation T3400
dmi.sys.vendor: Dell Inc.

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

[Kernel-packages] [Bug 1697556] Re: Computer freezes after login - 4.10.0-22-generic

2017-09-27 Thread Hagen Kuehn

Your question:
"so what's the result on v4.12-rc1, without "nomodeset"?"

Short answer: It does not freeze.

Detailed answer:
With v4.12-rc1, by using the default kernel arguments (i.e. without 
"nomodeset"), it does not freeze. It shows the login screen on the closed 
laptop, which you pointed out is related to i915.

The kern.log shows following nouveau related output.

Sep 27 09:37:15 computername kernel: [3.239682] nouveau: detected PR 
support, will not use DSM
Sep 27 09:37:15 computername kernel: [3.239698] nouveau :01:00.0: 
enabling device (0006 -> 0007)
Sep 27 09:37:15 computername kernel: [3.239831] nouveau :01:00.0: 
NVIDIA GP107 (137000a1)
Sep 27 09:37:15 computername kernel: [3.245638] i915 :00:02.0: vgaarb: 
changed VGA decodes: olddecodes=io+mem,decodes=io+mem:owns=io+mem
Sep 27 09:37:15 computername kernel: [3.248707] [drm] Finished loading DMC 
firmware i915/kbl_dmc_ver1_01.bin (v1.1)
Sep 27 09:37:15 computername kernel: [3.269575] nouveau :01:00.0: bios: 
version 86.07.3e.00.1c
Sep 27 09:37:15 computername kernel: [3.269993] nouveau :01:00.0: 
Direct firmware load for nvidia/gp107/gr/sw_nonctx.bin failed with error -2
Sep 27 09:37:15 computername kernel: [3.269995] nouveau :01:00.0: gr: 
failed to load gr/sw_nonctx
Sep 27 09:37:15 computername kernel: [3.26] nouveau :01:00.0: gr 
ctor failed, -2
Sep 27 09:37:15 computername kernel: [3.270003] nouveau: probe of 
:01:00.0 failed with error -2

Please see attached "kernel.log.4.12-rc1WithDefaultKernelArguments.log"
for details.

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

Title:
  Computer freezes after login - 4.10.0-22-generic

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have got a new Ubuntu 17.04 install on a Dell XPS 15 (Intel(R)
  Core(TM) i7-7700HQ CPU @ 2.80GHz) that was installed a couple of days
  ago. Login worked fine too.

  A couple of days later I installed the suggested kernel update
  "4.10.0-22-generic". With kernel 4.10.0-22-generic, the computer
  freezes right after login (i.e. after pressing enter, the background
  image with the mouse is shown, no responses to any key strokes).

  Syslog excerpt:

  Jun 12 22:12:48 computername kernel: [   47.603358] NMI watchdog: BUG: soft 
lockup - CPU#1 stuck for 23s! [Xorg.wrap:1672]
  Jun 12 22:12:48 computername kernel: [   47.603360] Modules linked in: ccm 
msr arc4 cmac rfcomm uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 
videobuf2_core videodev media btusb btrtl bnep hid_multitouch nls_iso8859_1 
i2c_designware_platform i2c_designware_core snd_hda_codec_hdmi dell_wmi 
dell_led dell_smbios snd_hda_codec_realtek snd_hda_codec_generic snd_hda_intel 
dcdbas ath10k_pci snd_hda_codec ath10k_core intel_rapl snd_hda_core ath 
x86_pkg_temp_thermal snd_hwdep intel_powerclamp mac80211 snd_pcm coretemp 
snd_seq_midi snd_seq_midi_event cfg80211 snd_rawmidi rtsx_pci_ms kvm_intel 
memstick kvm irqbypass crct10dif_pclmul joydev crc32_pclmul snd_seq 
ghash_clmulni_intel snd_seq_device input_leds snd_timer serio_raw snd soundcore 
idma64 virt_dma mei_me mei shpchp processor_thermal_device intel_soc_dts_iosf 
intel_lpss_pci intel_pch_thermal
  Jun 12 22:12:48 computername kernel: [   47.603422]  hci_uart btbcm btqca 
btintel bluetooth dell_smo8800 intel_hid intel_lpss_acpi sparse_keymap 
intel_lpss tpm_crb int3403_thermal int3400_thermal acpi_als 
int340x_thermal_zone acpi_thermal_rel acpi_pad kfifo_buf industrialio mac_hid 
pcbc aesni_intel crypto_simd glue_helper cryptd aes_x86_64 dm_crypt parport_pc 
ppdev lp parport ip_tables x_tables autofs4 nouveau rtsx_pci_sdmmc i915 ttm 
i2c_algo_bit drm_kms_helper syscopyarea mxm_wmi sysfillrect psmouse sysimgblt 
fb_sys_fops nvme drm nvme_core rtsx_pci ahci libahci i2c_hid hid 
pinctrl_sunrisepoint video wmi pinctrl_intel fjes
  Jun 12 22:12:48 computername kernel: [   47.603453] CPU: 1 PID: 1672 Comm: 
Xorg.wrap Not tainted 4.10.0-22-generic #24-Ubuntu
  Jun 12 22:12:48 computername kernel: [   47.603453] Hardware name: Dell Inc. 
XPS 15 9560/05FFDN, BIOS 1.3.3 05/08/2017

  
  Note, this problem is observed with kernel 4.10.0-22-generic whereas it's not 
observed with 4.10.0-21-generic. As I was not able to login to my computer I am 
writing this bug report while it runs on kernel 4.10.0-21-generic. Therefore 
the information attached through the "ubuntu-bug linux" command here, are 
referring to the kernel that is actually working. I decided to nonetheless 
include that information as it might contain other kernel unrelated information 
that would help you troubleshooting.

  Please see attached file "syslog-4.10.0-22-generic-freeze-after-
  login.log" for the full syslog.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-21-generic 4.10.0-21.23
  ProcVersionSignature: Ubuntu

[Kernel-packages] [Bug 1697556] Re: Computer freezes after login - 4.10.0-22-generic

2017-09-27 Thread Hagen Kuehn

** Attachment added: "Kernel 4.12-rc1 log using default kernel argument"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1697556/+attachment/4957550/+files/kernel.log.4.12-rc1WithDefaultKernelArguments.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/1697556

Title:
  Computer freezes after login - 4.10.0-22-generic

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have got a new Ubuntu 17.04 install on a Dell XPS 15 (Intel(R)
  Core(TM) i7-7700HQ CPU @ 2.80GHz) that was installed a couple of days
  ago. Login worked fine too.

  A couple of days later I installed the suggested kernel update
  "4.10.0-22-generic". With kernel 4.10.0-22-generic, the computer
  freezes right after login (i.e. after pressing enter, the background
  image with the mouse is shown, no responses to any key strokes).

  Syslog excerpt:

  Jun 12 22:12:48 computername kernel: [   47.603358] NMI watchdog: BUG: soft 
lockup - CPU#1 stuck for 23s! [Xorg.wrap:1672]
  Jun 12 22:12:48 computername kernel: [   47.603360] Modules linked in: ccm 
msr arc4 cmac rfcomm uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 
videobuf2_core videodev media btusb btrtl bnep hid_multitouch nls_iso8859_1 
i2c_designware_platform i2c_designware_core snd_hda_codec_hdmi dell_wmi 
dell_led dell_smbios snd_hda_codec_realtek snd_hda_codec_generic snd_hda_intel 
dcdbas ath10k_pci snd_hda_codec ath10k_core intel_rapl snd_hda_core ath 
x86_pkg_temp_thermal snd_hwdep intel_powerclamp mac80211 snd_pcm coretemp 
snd_seq_midi snd_seq_midi_event cfg80211 snd_rawmidi rtsx_pci_ms kvm_intel 
memstick kvm irqbypass crct10dif_pclmul joydev crc32_pclmul snd_seq 
ghash_clmulni_intel snd_seq_device input_leds snd_timer serio_raw snd soundcore 
idma64 virt_dma mei_me mei shpchp processor_thermal_device intel_soc_dts_iosf 
intel_lpss_pci intel_pch_thermal
  Jun 12 22:12:48 computername kernel: [   47.603422]  hci_uart btbcm btqca 
btintel bluetooth dell_smo8800 intel_hid intel_lpss_acpi sparse_keymap 
intel_lpss tpm_crb int3403_thermal int3400_thermal acpi_als 
int340x_thermal_zone acpi_thermal_rel acpi_pad kfifo_buf industrialio mac_hid 
pcbc aesni_intel crypto_simd glue_helper cryptd aes_x86_64 dm_crypt parport_pc 
ppdev lp parport ip_tables x_tables autofs4 nouveau rtsx_pci_sdmmc i915 ttm 
i2c_algo_bit drm_kms_helper syscopyarea mxm_wmi sysfillrect psmouse sysimgblt 
fb_sys_fops nvme drm nvme_core rtsx_pci ahci libahci i2c_hid hid 
pinctrl_sunrisepoint video wmi pinctrl_intel fjes
  Jun 12 22:12:48 computername kernel: [   47.603453] CPU: 1 PID: 1672 Comm: 
Xorg.wrap Not tainted 4.10.0-22-generic #24-Ubuntu
  Jun 12 22:12:48 computername kernel: [   47.603453] Hardware name: Dell Inc. 
XPS 15 9560/05FFDN, BIOS 1.3.3 05/08/2017

  
  Note, this problem is observed with kernel 4.10.0-22-generic whereas it's not 
observed with 4.10.0-21-generic. As I was not able to login to my computer I am 
writing this bug report while it runs on kernel 4.10.0-21-generic. Therefore 
the information attached through the "ubuntu-bug linux" command here, are 
referring to the kernel that is actually working. I decided to nonetheless 
include that information as it might contain other kernel unrelated information 
that would help you troubleshooting.

  Please see attached file "syslog-4.10.0-22-generic-freeze-after-
  login.log" for the full syslog.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-21-generic 4.10.0-21.23
  ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11
  Uname: Linux 4.10.0-21-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  hkuehn 1796 F pulseaudio
  CurrentDesktop: GNOME
  Date: Mon Jun 12 23:17:08 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-05-30 (13 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 138a:0091 Validity Sensors, Inc. 
   Bus 001 Device 002: ID 0cf3:e300 Atheros Communications, Inc. 
   Bus 001 Device 004: ID 0c45:6713 Microdia 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 15 9560
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-21-generic.efi.signed 
root=UUID=e0800d30-3eff-46ac-a6af-38e3bcf99b58 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-21-generic N/A
   linux-backports-modules-4.10.0-21-generic  N/A
   linux-firmware 1.164.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/08/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.3.3
  dmi.board.name: 05FFDN
  dmi.board.vendor: Dell Inc.

[Kernel-packages] [Bug 1718143] Re: linux: 4.10.0-36.40 -proposed tracker

2017-09-27 Thread Po-Hsu Lin

4.10.0-36.40 - generic
Regression test CMPL.
http://kernel.ubuntu.com/testing/tracker-index.html

Issue to note in amd64:
  hwclock - failed on lodygin only, bug 1714229
  monotonic_time - gtod failed on fozzie, rizzo. tsc failed on lodygin
  ubuntu_kvm_unit_tests - 57 failed on lodygin, 28 failed on rizzo, 15 failed 
on hainzel
  ubuntu_lxc - Failed to start networking in ubuntu-cloud container
  ubuntu_zfs_fstest - dpkg issued, passed on amaura after re-test
  xfstests - btrfs, xfs failed, bug 1718925

Issue to note in arm64:
  rtc - Update IRQs not supported on node wright
  hwclock - failed to change time on Moonshot system, bug 1716603
  ubuntu_bpf - failed to build, bug 1675395
  ubuntu_fan_smoke_test - network issue
  ubuntu_kernel_selftests - breakpoint test failed to build, bug 1680507
  ubuntu_kvm_unit_tests - gicv2-ipi, gicv2-active failed on 
ms10-35-mcdivittB0-kernel, passed on wright
  ubuntu_lxc - failed to fetch GPG key, network issue
  ubuntu_stress_smoke_test - failed to fetch cking's repo, network issue
  ubuntu_zfs_xfs_generic - test 079, 317 failed

Issue to note in i386:
  ubuntu_bpf - test_maps bpf test crashed, bug 1711512
  xfstests - btrfs, xfs failed, bug 1718925

Issue to note in ppc64le:
  libhugetlbfs - 4 failed, 7 killed by signal (small_const / small_data is not 
hugepage)
  rtc - Update IRQs not supported.
  ubuntu_kvm_unit_tests - sprs failed
  ubuntu_sysdig_smoke_test - passed after applying cking's patch, bug 1719553
  xfstests - btrfs, xfs failed, bug 1718925

Issue to note in s390x (zKVM):
  aio_dio_bugs - event res -22, not regression
  libhugetlbfs - 10 failed, 7 killed by signal, 1 bad config
  scrashme - failed to build bug 1689240
  ubuntu_bpf - failed to build, bug 1711299
  ubuntu_ecryptfs - miscdev-bad-count.sh.xfs ~ namelen.sh failed (28 failed)

Issue to note in s390x (zVM):
  aio_dio_bugs - event res -22, not regression
  libhugetlbfs - IOError: [Errno 95] Operation not supported
  scrashme - failed to build bug 1689240
  ubuntu_bpf - failed to build, bug 1711299
  ubuntu_ecryptfs - miscdev-bad-count.sh.xfs ~ namelen.sh failed (28 failed)

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

** Changed in: kernel-sru-workflow/regression-testing
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Po-Hsu Lin 
(cypressyew)

** Tags added: regression-testing-passed

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

Title:
  linux: 4.10.0-36.40 -proposed tracker

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

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

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

  backports: 1718145,1718146
  derivatives: 1718147
  -- 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/1718143/+subscriptions

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

[Kernel-packages] [Bug 1715271] Re: Middle button of trackpoint doesn't work

Ubuntu Artful needs the 2nd patch in comment #3 too.
Please apply it on artful kernel 4.13

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

Title:
  Middle button of trackpoint doesn't work

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

Bug description:
  Middle button doesn't work on several Thinkpad laptops like E570,
  E475, E470, E575 and X1Carbon.

  When middle button fails to work, logs show:
  psmouse serio2: trackpoint: failed to get extended button data

  It fails to read out ext button info via PS2 command.
  Almost all the Thinkpad have 3 buttons, so set it to 3 button when it fails 
to read button info.

  And on Lenovo X1, there is a new version of trackpoint, add this ID
  for this new device.

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

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

[Kernel-packages] [Bug 1715271] Re: Middle button of trackpoint doesn't work

The first patch in #1 is still missing in Zesty kernel.
I will send it to zesty kernel.

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

Title:
  Middle button of trackpoint doesn't work

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

Bug description:
  Middle button doesn't work on several Thinkpad laptops like E570,
  E475, E470, E575 and X1Carbon.

  When middle button fails to work, logs show:
  psmouse serio2: trackpoint: failed to get extended button data

  It fails to read out ext button info via PS2 command.
  Almost all the Thinkpad have 3 buttons, so set it to 3 button when it fails 
to read button info.

  And on Lenovo X1, there is a new version of trackpoint, add this ID
  for this new device.

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

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

[Kernel-packages] [Bug 159356] Re: System freeze on high memory usage

2017-09-27 Thread yas

Hi to the new updaters, :-)

I found this to happen with several instances of chrome, or with file 
operations over big files in combination. I've filed a bug report that was 
confirmed a couple of years ago:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1504914

One thing that helped me to avoid some hang if I manage to do it
promptly was to go su and use the drop_caches

$ sudo su
$ free -h  && sync && echo 3 > /proc/sys/vm/drop_caches && free -h

But this works temporarily and as long as I don't keep with many instances or 
big files accesses.
HTH

PS:
Ubuntu 16.04.03, encrypted home, 16GB RAM, 16Gb swap file. Default swapiness, 
cache_pressure and min_free_kbytes
uname -a
Linux big 4.4.0-96-generic #119-Ubuntu SMP Tue Sep 12 14:59:54 UTC 2017 x86_64 
x86_64 x86_64 GNU/Linux

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

Title:
  System freeze on high memory usage

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I run a batch matlab job server here at my lab, running Dapper 6.06 (for the 
LTS). One of the users has submitted a very memory-consuming job, which 
successfully crashes the server. Upon closer inspection, the crash happens like 
this:
  1. I run matlab with the given file (as an ordinary, unpriveleged user)
  2. RAM usage quickly fills up
  3. Once the RAM meter hits 100%, the system freezes: All SSH connections 
freeze up, and while switching VTs directly on the machine works, no new 
processes run - so one can't log in, or do anything if he is logged in. 
(Sometimes typing doesn't work at all)

  Note that the swap - while 7 gigs of it are available - is never used.
  (The machine has 7 gigs of RAM as well)

  I've tried the same on my Gutsy 32-bit box, and there was no system
  freezeup - matlab simply notified that the system was out of memory.
  However, it did this once memory was 100% in use - and still, swap
  didn't get used at all! (Though it is mounted correctly and shows up
  in "top" and "free").

  So first thing's first - I'd like to eliminate the crash issue. I
  suppose I could switch the server to 32-bit, but I think that would be
  a performance loss, considering that it does a lot of heavy
  computation. There is no reason, however, that this should happen on a
  64-bit machine anyway. Why does it?

  WORKAROUND: Enabling DMA in the BIOS

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

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

[Kernel-packages] [Bug 1715271] Re: Middle button of trackpoint doesn't work

Tested on E470 with Xenial 4.4.0.97-120 kernel, works fine.

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

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

Title:
  Middle button of trackpoint doesn't work

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

Bug description:
  Middle button doesn't work on several Thinkpad laptops like E570,
  E475, E470, E575 and X1Carbon.

  When middle button fails to work, logs show:
  psmouse serio2: trackpoint: failed to get extended button data

  It fails to read out ext button info via PS2 command.
  Almost all the Thinkpad have 3 buttons, so set it to 3 button when it fails 
to read button info.

  And on Lenovo X1, there is a new version of trackpoint, add this ID
  for this new device.

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

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

[Kernel-packages] [Bug 1697556] Re: Computer freezes after login - 4.10.0-22-generic

2017-09-27 Thread Kai-Heng Feng

Sorry to ask again - so what's the result on v4.12-rc1, without
"nomodeset"?

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

Title:
  Computer freezes after login - 4.10.0-22-generic

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have got a new Ubuntu 17.04 install on a Dell XPS 15 (Intel(R)
  Core(TM) i7-7700HQ CPU @ 2.80GHz) that was installed a couple of days
  ago. Login worked fine too.

  A couple of days later I installed the suggested kernel update
  "4.10.0-22-generic". With kernel 4.10.0-22-generic, the computer
  freezes right after login (i.e. after pressing enter, the background
  image with the mouse is shown, no responses to any key strokes).

  Syslog excerpt:

  Jun 12 22:12:48 computername kernel: [   47.603358] NMI watchdog: BUG: soft 
lockup - CPU#1 stuck for 23s! [Xorg.wrap:1672]
  Jun 12 22:12:48 computername kernel: [   47.603360] Modules linked in: ccm 
msr arc4 cmac rfcomm uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 
videobuf2_core videodev media btusb btrtl bnep hid_multitouch nls_iso8859_1 
i2c_designware_platform i2c_designware_core snd_hda_codec_hdmi dell_wmi 
dell_led dell_smbios snd_hda_codec_realtek snd_hda_codec_generic snd_hda_intel 
dcdbas ath10k_pci snd_hda_codec ath10k_core intel_rapl snd_hda_core ath 
x86_pkg_temp_thermal snd_hwdep intel_powerclamp mac80211 snd_pcm coretemp 
snd_seq_midi snd_seq_midi_event cfg80211 snd_rawmidi rtsx_pci_ms kvm_intel 
memstick kvm irqbypass crct10dif_pclmul joydev crc32_pclmul snd_seq 
ghash_clmulni_intel snd_seq_device input_leds snd_timer serio_raw snd soundcore 
idma64 virt_dma mei_me mei shpchp processor_thermal_device intel_soc_dts_iosf 
intel_lpss_pci intel_pch_thermal
  Jun 12 22:12:48 computername kernel: [   47.603422]  hci_uart btbcm btqca 
btintel bluetooth dell_smo8800 intel_hid intel_lpss_acpi sparse_keymap 
intel_lpss tpm_crb int3403_thermal int3400_thermal acpi_als 
int340x_thermal_zone acpi_thermal_rel acpi_pad kfifo_buf industrialio mac_hid 
pcbc aesni_intel crypto_simd glue_helper cryptd aes_x86_64 dm_crypt parport_pc 
ppdev lp parport ip_tables x_tables autofs4 nouveau rtsx_pci_sdmmc i915 ttm 
i2c_algo_bit drm_kms_helper syscopyarea mxm_wmi sysfillrect psmouse sysimgblt 
fb_sys_fops nvme drm nvme_core rtsx_pci ahci libahci i2c_hid hid 
pinctrl_sunrisepoint video wmi pinctrl_intel fjes
  Jun 12 22:12:48 computername kernel: [   47.603453] CPU: 1 PID: 1672 Comm: 
Xorg.wrap Not tainted 4.10.0-22-generic #24-Ubuntu
  Jun 12 22:12:48 computername kernel: [   47.603453] Hardware name: Dell Inc. 
XPS 15 9560/05FFDN, BIOS 1.3.3 05/08/2017

  
  Note, this problem is observed with kernel 4.10.0-22-generic whereas it's not 
observed with 4.10.0-21-generic. As I was not able to login to my computer I am 
writing this bug report while it runs on kernel 4.10.0-21-generic. Therefore 
the information attached through the "ubuntu-bug linux" command here, are 
referring to the kernel that is actually working. I decided to nonetheless 
include that information as it might contain other kernel unrelated information 
that would help you troubleshooting.

  Please see attached file "syslog-4.10.0-22-generic-freeze-after-
  login.log" for the full syslog.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-21-generic 4.10.0-21.23
  ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11
  Uname: Linux 4.10.0-21-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  hkuehn 1796 F pulseaudio
  CurrentDesktop: GNOME
  Date: Mon Jun 12 23:17:08 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-05-30 (13 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 138a:0091 Validity Sensors, Inc. 
   Bus 001 Device 002: ID 0cf3:e300 Atheros Communications, Inc. 
   Bus 001 Device 004: ID 0c45:6713 Microdia 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 15 9560
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-21-generic.efi.signed 
root=UUID=e0800d30-3eff-46ac-a6af-38e3bcf99b58 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-21-generic N/A
   linux-backports-modules-4.10.0-21-generic  N/A
   linux-firmware 1.164.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/08/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.3.3
  dmi.board.name: 05FFDN
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias:

[Kernel-packages] [Bug 1716301] Re: wifi driver: mt7601u not work on 16.04

2017-09-27 Thread Kai-Heng Feng

Weird. Can you try Artful live image?

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

Title:
  wifi driver: mt7601u not work on 16.04

Status in linux package in Ubuntu:
  Confirmed
Status in usb-modeswitch-data package in Ubuntu:
  New

Bug description:
  In the beginning, when the adapter is pluged in, it's mounted as a disk 
including driver files for Windows, and
  $> lsusb
  Bus 003 Device 010: ID 148f:2878 Ralink Technology, Corp.

  after eject the disk,
  $> lsusb
  Bus 003 Device 011: ID 148f:7601 Ralink Technology, Corp. MT7601U Wireless 
Adapter

  I tried following 3 drivers:
  1) the default mt7601u included in the kernel: 4.4.0-91-generic
  after eject the disk,
  $> lsmod|grep mt
  mt7601u 102400 0
  mac80211 737280 1 mt7601u
  cfg80211 565248 2 mac80211,mt7601u
  binfmt_misc 20480 1
  $> modinfo mt7601u
  filename: 
/lib/modules/4.4.0-91-generic/kernel/drivers/net/wireless/mediatek/mt7601u/mt7601u.ko
  srcversion: E8B632D369E0C2A9F1CF7D8
  alias: usb:v7392p7710d*dc*dsc*dp*ic*isc*ip*in*
  ..
  depends: mac80211,cfg80211
  intree: Y
  vermagic: 4.4.0-91-generic SMP mod_unload modversions

  $> dmesg
  // begin
  [ 4581.094119] usb 3-4: USB disconnect, device number 6
  [ 4584.872751] usb 3-4: new high-speed USB device number 7 using xhci_hcd
  [ 4585.001408] usb 3-4: New USB device found, idVendor=148f, idProduct=2878
  [ 4585.001413] usb 3-4: New USB device strings: Mfr=1, Product=2, 
SerialNumber=0
  [ 4585.001416] usb 3-4: Product: Љ
  [ 4585.001418] usb 3-4: Manufacturer: Љ
  [ 4585.001753] usb-storage 3-4:1.0: USB Mass Storage device detected
  [ 4585.001873] scsi host6: usb-storage 3-4:1.0
  [ 4586.001122] scsi 6:0:0:0: CD-ROM MediaTek Flash autorun 0.01 PQ: 0 ANSI: 0 
CCS
  [ 4586.001978] sr 6:0:0:0: [sr0] scsi3-mmc drive: 52x/52x cd/rw xa/form2 cdda 
tray
  [ 4586.002529] sr 6:0:0:0: Attached scsi CD-ROM sr0
  [ 4586.002716] sr 6:0:0:0: Attached scsi generic sg1 type 5
  [ 4619.658385] ISO 9660 Extensions: Microsoft Joliet Level 3
  [ 4619.691737] ISOFS: changing to secondary root
  [ 4691.563347] usb 3-4: USB disconnect, device number 7
  [ 4693.638315] usb 3-4: new high-speed USB device number 8 using xhci_hcd
  [ 4693.766896] usb 3-4: New USB device found, idVendor=148f, idProduct=2878
  [ 4693.766901] usb 3-4: New USB device strings: Mfr=1, Product=2, 
SerialNumber=0
  [ 4693.766903] usb 3-4: Product: Љ
  [ 4693.766905] usb 3-4: Manufacturer: Љ
  [ 4693.767338] usb-storage 3-4:1.0: USB Mass Storage device detected
  [ 4693.768063] scsi host7: usb-storage 3-4:1.0
  [ 4694.766737] scsi 7:0:0:0: CD-ROM MediaTek Flash autorun 0.01 PQ: 0 ANSI: 0 
CCS
  [ 4694.767423] sr 7:0:0:0: [sr0] scsi3-mmc drive: 52x/52x cd/rw xa/form2 cdda 
tray
  [ 4694.767908] sr 7:0:0:0: Attached scsi CD-ROM sr0
  [ 4694.768147] sr 7:0:0:0: Attached scsi generic sg1 type 5
  [ 4728.418255] ISO 9660 Extensions: Microsoft Joliet Level 3
  [ 4728.427856] ISOFS: changing to secondary root
  [ 4733.824182] sr 7:0:0:0: [sr0] tag#0 FAILED Result: hostbyte=DID_ERROR 
driverbyte=DRIVER_OK
  [ 4733.824190] sr 7:0:0:0: [sr0] tag#0 CDB: Start/Stop Unit 1b 00 00 00 02 00
  [ 4733.824218] usb 3-4: USB disconnect, device number 8
  [ 4733.824281] sr 7:0:0:0: [sr0] tag#0 FAILED Result: hostbyte=DID_ERROR 
driverbyte=DRIVER_OK
  [ 4733.824291] sr 7:0:0:0: [sr0] tag#0 CDB: Prevent/Allow Medium Removal 1e 
00 00 00 00 00
  [ 4734.099901] usb 3-4: new high-speed USB device number 9 using xhci_hcd
  [ 4734.238749] usb 3-4: New USB device found, idVendor=148f, idProduct=7601
  [ 4734.238754] usb 3-4: New USB device strings: Mfr=1, Product=2, 
SerialNumber=3
  [ 4734.238757] usb 3-4: Product: 802.11 n WLAN
  [ 4734.238772] usb 3-4: Manufacturer: MediaTek
  [ 4734.238775] usb 3-4: SerialNumber: 1.0
  [ 4735.432096] usb 3-4: reset high-speed USB device number 9 using xhci_hcd
  [ 4735.562543] mt7601u 3-4:1.0: ASIC revision: 76010001 MAC revision: 76010500
  [ 4735.563089] mt7601u 3-4:1.0: Firmware Version: 0.1.00 Build: 7640 Build 
time: 201302052146
  [ 4739.011624] mt7601u 3-4:1.0: Vendor request req:07 off:09a8 failed:-110
  [ 4742.131399] mt7601u 3-4:1.0: Vendor request req:02 off:09a8 failed:-110
  [ 4745.251254] mt7601u 3-4:1.0: Vendor request req:07 off:0734 failed:-110
  [ 4748.371056] mt7601u 3-4:1.0: Vendor request req:42 off:0230 failed:-110
  [ 4751.490880] mt7601u 3-4:1.0: Vendor request req:07 off:0080 failed:-110
  [ 4754.610694] mt7601u 3-4:1.0: Vendor request req:02 off:0080 failed:-110
  [ 4757.730501] mt7601u 3-4:1.0: Vendor request req:02 off:0080 failed:-110
  [ 4757.730548] mt7601u: probe of 3-4:1.0 failed with error -110
  [ 4757.730870] usbcore: registered new interface driver mt7601u
  // end 

  $> sudo ifconfig -a // do not list any new interface

  2) DPO_MT7601U_LinuxSTA_3.0.0.4_20130913.tar.bz2
  this

[Kernel-packages] [Bug 1719795] [NEW] Dell 7140 avarage power consumption in idle increased by 1.3-1.5 times due to events by INT3432

2017-09-27 Thread RussianNeuroMancer

Public bug reported:

On Dell Venue 11 Pro 7140 average power consumption in idle increased by
1.3-1.5 times due to events coming from INT343A. According to powertop
since Linux 4.10 INT3432:00 generate around two hundred events on
average, in /sys/devices/pci:00/INT3432:00/i2c-6 there is two
devices: INT343A and SMO91D0. AFAIK INT343A is rt286.

With Linux 4.9.0-4.9.45, Linux 4.11.0-4.11.12 in idle there is around 100 
wakeups per second in sum, battery discharge rate around 3-3.5 Watts per second.
But with Linux 4.9.46-4.9.51, Linux 4.10.0-4.10.17, Linux 4.12.0rc1-4.13.3 - 
around 300 wakeups per second on average, due to events coming from INT3432:00. 
With Linux 4.13.3 battery discharge rate around 4.5 Watts per second.
Probably some commit was backported to Linux 4.9 between .45 and .46 releases.
I have no idea why issue is not reproducible on any Linux 4.11 release I tried.

Sometimes INT3432 events rate fall from two hundred to one hundred for
shorts period of time (for example I observe this right now on Linux
4.10.0 while removing/installing packages).

Message like this sometimes appear in dmesg:
[  731.226730] i2c_hid i2c-SMO91D0:00: i2c_hid_get_input: incomplete report 
(53/13568)

Complete dmesg with Linux 4.13.3 is attached.

** Affects: linux
 Importance: Unknown
 Status: Unknown

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

** Attachment added: "dmesg"
   https://bugs.launchpad.net/bugs/1719795/+attachment/4957514/+files/dmesg

** Bug watch added: Linux Kernel Bug Tracker #197047
   https://bugzilla.kernel.org/show_bug.cgi?id=197047

** Also affects: linux via
   https://bugzilla.kernel.org/show_bug.cgi?id=197047
   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/1719795

Title:
  Dell 7140 avarage power consumption in idle increased by 1.3-1.5 times
  due to events by INT3432

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  New

Bug description:
  On Dell Venue 11 Pro 7140 average power consumption in idle increased
  by 1.3-1.5 times due to events coming from INT343A. According to
  powertop since Linux 4.10 INT3432:00 generate around two hundred
  events on average, in /sys/devices/pci:00/INT3432:00/i2c-6 there
  is two devices: INT343A and SMO91D0. AFAIK INT343A is rt286.

  With Linux 4.9.0-4.9.45, Linux 4.11.0-4.11.12 in idle there is around 100 
wakeups per second in sum, battery discharge rate around 3-3.5 Watts per second.
  But with Linux 4.9.46-4.9.51, Linux 4.10.0-4.10.17, Linux 4.12.0rc1-4.13.3 - 
around 300 wakeups per second on average, due to events coming from INT3432:00. 
With Linux 4.13.3 battery discharge rate around 4.5 Watts per second.
  Probably some commit was backported to Linux 4.9 between .45 and .46 releases.
  I have no idea why issue is not reproducible on any Linux 4.11 release I 
tried.

  Sometimes INT3432 events rate fall from two hundred to one hundred for
  shorts period of time (for example I observe this right now on Linux
  4.10.0 while removing/installing packages).

  Message like this sometimes appear in dmesg:
  [  731.226730] i2c_hid i2c-SMO91D0:00: i2c_hid_get_input: incomplete report 
(53/13568)

  Complete dmesg with Linux 4.13.3 is attached.

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

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

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

--- Comment From shriy...@in.ibm.com 2017-09-27 03:26 EDT---
Verified on the kernel : http://kernel.ubuntu.com/~jsalisbury/lp1711075/

System : Witherspoon + DD1.0
uname -a : Linux ltc-wspoon3 4.10.0-32-generic #36~lp1711075 SMP Wed Aug 16 
14:09:56 UTC 2017 ppc64le ppc64le ppc64le GNU/Linux

root@ltc-wspoon3:/usr/lib/linux-tools/4.10.0-36-generic# ./perf test
1: vmlinux symtab matches kallsyms: Skip
2: Detect openat syscall event: Ok
3: Detect openat syscall event on all cpus: Ok
4: Read samples using the mmap interface  : Ok
5: Parse event definition strings : Ok
6: PERF_RECORD_* events & perf_sample fields  : Ok
7: Parse perf pmu format  : Ok
8: DSO data read  : Ok
9: DSO data cache : Ok
10: DSO data reopen: Ok
11: Roundtrip evsel->name  : Ok
12: Parse sched tracepoints fields : Ok
13: syscalls:sys_enter_openat event fields : Ok
14: Setup struct perf_event_attr   : Skip
15: Match and link multiple hists  : Ok
16: 'import perf' in python: Ok
17: Breakpoint overflow signal handler : FAILED!
18: Breakpoint overflow sampling   : FAILED!
19: Number of exit events of a simple workload : Ok
20: Software clock events period values: Ok
21: Object code reading: FAILED!
22: Sample parsing : Ok
23: Use a dummy software event to keep tracking: Ok
24: Parse with no sample_id_all bit set: Ok
25: Filter hist entries: Ok
26: Lookup mmap thread : Ok
27: Share thread mg: Ok
28: Sort output of hist entries: Ok
29: Cumulate child hist entries: Ok
30: Track with sched_switch: Ok
31: Filter fds with revents mask in a fdarray  : Ok
32: Add fd to a fdarray, making it autogrow: Ok
33: kmod_path__parse   : Ok
34: Thread map : Ok
35: LLVM search and compile:
35.1: Basic BPF llvm compile: Skip
35.2: kbuild searching  : Skip
35.3: Compile source for BPF prologue generation: Skip
35.4: Compile source for BPF relocation : Skip
36: Session topology   : Ok
37: BPF filter :
37.1: Basic BPF filtering  : Skip
37.2: BPF prologue generation  : Skip
37.3: BPF relocation checker   : Skip
38: Synthesize thread map  : Ok
39: Remove thread map  : Ok
40: Synthesize cpu map : Ok
41: Synthesize stat config : Ok
42: Synthesize stat: Ok
43: Synthesize stat round  : Ok
44: Synthesize attr update : Ok
45: Event times: Ok
46: Read backward ring buffer  : Ok
47: Print cpu map  : Ok
48: Probe SDT events   : Skip
49: is_printable_array : Ok
50: Print bitmap   : Ok
51: perf hooks : Ok
52: builtin clang support  : Skip (not compiled in)
53: Test dwarf unwind  : FAILED!

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

Title:
  [Power 9, Power NV][WSP/Boston]Ubuntu 16.04.03 : perf test is hung at
  Breakpoint overflow signal handler

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

Bug description:
  == Comment: # - Shriya R. Kulkarni <> - 2017-06-14 01:11:02 ==
  Problem Description :
  =
  perf test is hung at Breakpoint overflow signal handler.

  Machine details :
  ==
  System : WSP , P9 baremetal.
  OS : Ubuntu 16.04.03
  uname -a : Linux ltc-wspoon3 4.10.0-23-generic #25~16.04.1-Ubuntu SMP Fri Jun 
9 10:43:34 UTC 2017 ppc64le ppc64le ppc64le GNU/Linux

  Testing:
  
  root@ltc-wspoon3:~# perf test
   1: vmlinux symtab matches kallsyms: Skip
   2: Detect openat syscall event: Ok
   3: Detect openat syscall event on all cpus: Ok
   4: Read samples using the mmap interface  : Ok
   5: Parse event definition strings : Ok
   6: PERF_RECORD_* events & perf_sample fields  : Ok
   7: Parse perf pmu format  : Ok
   8: DSO data read  : Ok
   9: DSO data cache : Ok
  10: DSO data reopen: Ok
  11: Roundtrip evsel->name  : Ok
  12: Parse sched

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