[Kernel-packages] [Bug 367688] Re: [424469.038129] ------------[ cut here ]------------

[Ubuntu QA Website]

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/367688

** Tags added: iso-testing

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

Title:
  [424469.038129] [ cut here ]

Status in linux package in Ubuntu:
  Invalid

Bug description:
  I'm not entirely sure what the oops did, as I'm by no means familiar
  with the kernel. First time this has happened, but since apport
  prompted me for a report I sent it through. If any further info is
  needed, I'll be glad to help and I will be keeping any eye out for any
  more problems along these lines.

  ProblemType: KernelOops
  Annotation: Your system might become unstable now and might need to be 
restarted.
  Architecture: i386
  DistroRelease: Ubuntu 9.04
  Failure: oops
  HibernationDevice: RESUME=UUID=9411d919-3750-47e2-bacd-fcffd1cb3273
  MachineType: EMACHINES T3604
  NonfreeKernelModules: nvidia
  Package: linux-image-2.6.28-11-generic 2.6.28-11.42
  ProcCmdLine: root=UUID=fe6b2c3e-6365-4730-a43c-673fe64457d6 ro quiet splash
  ProcVersionSignature: Ubuntu 2.6.28-11.42-generic
  SourcePackage: linux
  Tags: kernel-oops
  Title: [424469.038129] [ cut here ]

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

-- 
Mailing list: https://launchpad.net/~kernel-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)

[Kai-Heng Feng]

It's driven by intel graphics all the time. Nouveau is the part that has
more chance to hang the system.

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

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/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 1246670] ❤yahoo! a splendid dinner

[Piero Bonatti]

Hello friend,

We have recently had an outstanding dinner with my family in  a great
place, just take  a look  http://www.bio-
ecoplastic.com/master/Editor/plugins/link/as.php?UE8xMjQ2NjcwQGJ1Z3MubGF1bmNocGFkLm5ldA--

Good wishes, Piero Bonatti


From: Bug 1246670 [mailto:1246...@bugs.launchpad.net]
Sent: Tuesday, September 26, 2017 8:49 PM
To: pierobona...@libero.it
Subject: Tape a few ducks to it

Pass me a Kit Kat and give me a damn break. This is still a  huge market
with a decent roster  in need  of a leader. If a  coaching  prospect
doesn't want to come here  then they can go take the Raiders  job,
which the article itself says was  ranked below us along  with the Jets.
This is just Biggs blowing smoke.


Sent from Mail for Windows 10

** Attachment added: "3116F01ABCEF306F.jpg"
   
https://bugs.launchpad.net/bugs/1246670/+attachment/4957449/+files/3116F01ABCEF306F.jpg

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

Title:
  14e4:4727 [Dell Inspiron 10z (1120)] Ubuntu 12.04.3 LTS: can't connect
  to WIFI

Status in linux package in Ubuntu:
  Expired

Bug description:
  After the last updates I can't connect anymore to WIFI networks, including:
   - office wifi (WPA / WPA2 enterprise + PEAP)
   - public wifi from airport lounges, hotels, conferences.

  The notebook (dell inspiron) still detects the available newtorks. If
  they are protected, then additional data are requested (passwords and
  the like). So it seems that the wifi card is working well with the
  current driver (see below for further evidence). However, then the
  connection times out before getting any IP address.

  When I switch to Windows, I immediately get the connection (then the
  wifi network and the notebook's hardware are OK).  Sometimes, when I
  switch back to Ubuntu, the connection starts spontaneously and I can
  work normally (as if the problem were in the DHCP protocol execution,
  and the Windows connection "did some work" that Ubuntu currently can't
  do). (further evidence that the driver is OK).

  I'm using the proprietary driver proposed by Ubuntu:
  "This package contains Broadcom 802.11 Linux STA wireless driver for use with 
Broadcom's BCM4311-, BCM4312-, BCM4313-, BCM4321-, BCM4322-, BCM43224-, and 
BCM43225-, BCM43227- and BCM43228-based hardware."

  ---
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
  ApportVersion: 2.0.1-0ubuntu17.6
  Architecture: i386
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: SB [HDA ATI SB], device 0: ALC259 Analog [ALC259 Analog]
     Subdevices: 1/1
     Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  bonatti1690 F pulseaudio
   /dev/snd/controlC0:  bonatti1690 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'SB'/'HDA ATI SB at 0xd040 irq 16'
     Mixer name : 'Realtek ALC259'
     Components : 'HDA:10ec0269,10280470,00100100'
     Controls  : 18
     Simple ctrls  : 10
  Card1.Amixer.info:
   Card hw:1 'HDMI'/'HDA ATI HDMI at 0xd011 irq 19'
     Mixer name : 'ATI RS690/780 HDMI'
     Components : 'HDA:1002791a,00791a00,0010'
     Controls  : 4
     Simple ctrls  : 1
  Card1.Amixer.values:
   Simple mixer control 'IEC958',0
     Capabilities: pswitch pswitch-joined penum
     Playback channels: Mono
     Mono: Playback [on]
  DistroRelease: Ubuntu 12.04
  HibernationDevice: RESUME=UUID=8b9f8be8-b5ce-42d9-b311-de81faa160f6
  InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release i386 
(20120817.3)
  MachineType: Dell Inc. Inspiron 1120
  MarkForUpload: True
  NonfreeKernelModules: wl
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-55-generic-pae 
root=UUID=891059fc-57ca-484c-941a-e405cd31b74e ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.2.0-55.85-generic-pae 3.2.51
  RelatedPackageVersions:
   linux-restricted-modules-3.2.0-55-generic-pae N/A
   linux-backports-modules-3.2.0-55-generic-pae  N/A
   linux-firmware1.79.7
  Tags:  precise running-unity
  Uname: Linux 3.2.0-55-generic-pae i686
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lp lpadmin plugdev sambashare sudo
  dmi.bios.date: 07/26/2010
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A03
  dmi.board.asset.tag: 1234567890
  dmi.board.name: 090DNY
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A03
  dmi.chassis.asset.tag: 1234567890
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A03
  dmi.modalias: 
dmi:bvnDellInc.:bvrA03:bd07/26/2010:svnDellInc.:pnInspiron1120:pvrA03:rvnDellInc.:rn090DNY:rvrA03:cvnDellInc.:ct8:cvrA03:
  dmi.product.name: Inspiron 1120
  

[Kernel-packages] [Bug 1718871] Re: s4 get Error taking CPU down -34

[Zhanglei Mao]

Tested works well kernel are:
   kernel 3.13.0-24-generic of 14.04 
   Kernel 3.13.0-031300-generic on 14.04 from 
（http://kernel.ubuntu.com/~kernel-ppa/mainline/)

Tested was failed kernel are:


linux-image-4.4.0-93-generic of lasted 16.04.1
4.4.9-21-generic, 4.12.0-041200-generic,4.14.0-999-generic download from 
http://kernel.ubuntu.com/~kernel-ppa/mainline/) on 16.04

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

Title:
  s4 get Error taking CPU down -34

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

Bug description:
  When test S4 on Huawei 1288H V5 server as 
   #echo disk>/sys/power/state
  It show error of
Error taking CPU79 down: -34
Non-boot CPUs are not disabled 

  The echo command return with error of:
Write error: Numerical result out of range 

  From the dmesg it show error of:
CPU79 disable failed: CPU have 2 vectors assigned and there are only 1 
available 
Error taking CPU79 down: -34

  This server have been passed 16.04 certification
  (https://certification.ubuntu.com/hardware/201707-25617/).

  The test kernel is lasted 16.04.1 of linux-image-4.4.0-93-generic. It
  is also failed on 16.04 with kernel of 4.4.9-21-generic,
  4.12.0-041200-generic,4.14.0-999-generic which was download from
  （http://kernel.ubuntu.com/~kernel-ppa/mainline/). But it works on
  14.04 with kernel 3.13.0-24-generic and download kernel of
  3.13.0-031300-generic from above link.

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

-- 
Mailing list: https://launchpad.net/~kernel-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

[bugproxy]

--- Comment From hasri...@in.ibm.com 2017-09-26 21:24 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:

Can you build a ppc specific kernel?

Thanks,
Harish

-- 
You 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 159356] Re: System freeze on high memory usage

[insp]

Ubuntu 16.04.3, encrypted disk, 8GB RAM, 11GB swap file. Default
swapiness and cache_presure. System almost hang (feels like 1 frame per
5 seconds) with full RAM and 7.7/11GB swap used.

-- 
You 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 1713575] Re: Vlun resize request could fail with cxlflash driver

[bugproxy]

** Tags removed: targetmilestone-inin---
** Tags added: targetmilestone-inin16043

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

Title:
  Vlun resize request could fail with cxlflash driver

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

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

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

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

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

[Kernel-packages] [Bug 1650336] Re: NFS client : kernel 4.4.0-57 crash with nfsv4 enries in /etc/fstab

[Chris Mohler]

I'm getting this same issue in kernel 4.4.0-96 on Xenial. Any
suggestions?

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

Title:
  NFS client : kernel 4.4.0-57 crash with nfsv4 enries in /etc/fstab

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

Bug description:
  SRU Justification

  Impact: A commit from upstream 4.4 stable introduced a regression in
  refcounting auth_gss messages which can lead to an oops.

  Fix: Cherry pick upstream commit
  1cded9d2974fe4fe339fc0ccd6638b80d465ab2c "SUNRPC: fix refcounting
  problems with auth_gss messages."

  Regresssion Potential: Test results confirm that the commit fixes an
  existing regression. It's pretty straightforward and is already
  present in some upstream stable kernels, so I think the potential for
  regressions is minimal.

  ---

  On (K)ubuntu 16.04.01 (Xenial) Upgrading to kernel 4.4.0-57 the kernel
  crash on boot when in /etc/fstab a nfsv4 entry is active

  When comment the line or set to noauto the kernel boot with no error
  and mounting the nfs shares (after uncomment ) is also possible
  without error

  4.4.0-54 boots without this problem.

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

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

[Kernel-packages] [Bug 1713821] Re: arm64 arch_timer fixes

[dann frazier]

ubuntu@equal-beetle:~$ cat /proc/version
Linux version 4.10.0-36-generic (buildd@bos01-arm64-013) (gcc version 5.4.0 
20160609 (Ubuntu/Linaro 5.4.0-6ubuntu1~16.04.4) ) #40~16.04.1-Ubuntu SMP Tue 
Sep 19 15:20:18 UTC 2017
ubuntu@equal-beetle:~$ sudo dmesg | grep -i arch_timer
[0.00] arch_timer: Enabling global workaround for HiSilicon erratum 
161010101
[0.00] arch_timer: CPU0: Trapping CNTVCT access
[0.00] arch_timer: cp15 timer(s) running at 50.00MHz (phys).
[0.194148] arch_timer: CPU1: Trapping CNTVCT access
[0.197183] arch_timer: CPU2: Trapping CNTVCT access
[0.200193] arch_timer: CPU3: Trapping CNTVCT access
[0.203192] arch_timer: CPU4: Trapping CNTVCT access
[0.206199] arch_timer: CPU5: Trapping CNTVCT access
[0.209199] arch_timer: CPU6: Trapping CNTVCT access
[0.212197] arch_timer: CPU7: Trapping CNTVCT access
[0.215212] arch_timer: CPU8: Trapping CNTVCT access
[0.218234] arch_timer: CPU9: Trapping CNTVCT access
[0.221238] arch_timer: CPU10: Trapping CNTVCT access
[0.224244] arch_timer: CPU11: Trapping CNTVCT access
[0.227250] arch_timer: CPU12: Trapping CNTVCT access
[0.230271] arch_timer: CPU13: Trapping CNTVCT access
[0.233286] arch_timer: CPU14: Trapping CNTVCT access
[0.236293] arch_timer: CPU15: Trapping CNTVCT access
[0.239365] arch_timer: CPU16: Trapping CNTVCT access
[0.242482] arch_timer: CPU17: Trapping CNTVCT access
[0.245543] arch_timer: CPU18: Trapping CNTVCT access
[0.248601] arch_timer: CPU19: Trapping CNTVCT access
[0.251675] arch_timer: CPU20: Trapping CNTVCT access
[0.254747] arch_timer: CPU21: Trapping CNTVCT access
[0.257809] arch_timer: CPU22: Trapping CNTVCT access
[0.260874] arch_timer: CPU23: Trapping CNTVCT access
[0.263942] arch_timer: CPU24: Trapping CNTVCT access
[0.267019] arch_timer: CPU25: Trapping CNTVCT access
[0.270077] arch_timer: CPU26: Trapping CNTVCT access
[0.273181] arch_timer: CPU27: Trapping CNTVCT access
[0.276300] arch_timer: CPU28: Trapping CNTVCT access
[0.279418] arch_timer: CPU29: Trapping CNTVCT access
[0.282534] arch_timer: CPU30: Trapping CNTVCT access
[0.285632] arch_timer: CPU31: Trapping CNTVCT access
[0.289091] arch_timer: CPU32: Trapping CNTVCT access
[0.292688] arch_timer: CPU33: Trapping CNTVCT access
[0.296098] arch_timer: CPU34: Trapping CNTVCT access
[0.299505] arch_timer: CPU35: Trapping CNTVCT access
[0.302920] arch_timer: CPU36: Trapping CNTVCT access
[0.306333] arch_timer: CPU37: Trapping CNTVCT access
[0.309748] arch_timer: CPU38: Trapping CNTVCT access
[0.313156] arch_timer: CPU39: Trapping CNTVCT access
[0.316575] arch_timer: CPU40: Trapping CNTVCT access
[0.320010] arch_timer: CPU41: Trapping CNTVCT access
[0.323419] arch_timer: CPU42: Trapping CNTVCT access
[0.326831] arch_timer: CPU43: Trapping CNTVCT access
[0.330254] arch_timer: CPU44: Trapping CNTVCT access
[0.333679] arch_timer: CPU45: Trapping CNTVCT access
[0.337106] arch_timer: CPU46: Trapping CNTVCT access
[0.340505] arch_timer: CPU47: Trapping CNTVCT access
[0.343945] arch_timer: CPU48: Trapping CNTVCT access
[0.347462] arch_timer: CPU49: Trapping CNTVCT access
[0.350896] arch_timer: CPU50: Trapping CNTVCT access
[0.354329] arch_timer: CPU51: Trapping CNTVCT access
[0.357764] arch_timer: CPU52: Trapping CNTVCT access
[0.361200] arch_timer: CPU53: Trapping CNTVCT access
[0.364632] arch_timer: CPU54: Trapping CNTVCT access
[0.368067] arch_timer: CPU55: Trapping CNTVCT access
[0.371503] arch_timer: CPU56: Trapping CNTVCT access
[0.374955] arch_timer: CPU57: Trapping CNTVCT access
[0.378389] arch_timer: CPU58: Trapping CNTVCT access
[0.381850] arch_timer: CPU59: Trapping CNTVCT access
[0.385327] arch_timer: CPU60: Trapping CNTVCT access
[0.388814] arch_timer: CPU61: Trapping CNTVCT access
[0.392286] arch_timer: CPU62: Trapping CNTVCT access
[0.395757] arch_timer: CPU63: Trapping CNTVCT access

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

Title:
  arm64 arch_timer fixes

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

Bug description:
  [Impact]
  This bug captures a few issues with the ARM arch_timer driver:

  1) Some arm64 systems have hardware defects in their architected timer
  implementations that require errata, which we workaround in the
  kernel. However, it's possible that this workaround will not be
  applied if the timer was reset w/ the user access bit set.

  2) The Juno board fails to initialize a timer at boot:

    arch_timer: Unable to map frame @ 0x
    arch_timer: Frame missing phys irq.
    Failed 

[Kernel-packages] [Bug 1719731] Re: Suspending Lubuntu 16.04.3 results in network manager stops working

[Joseph Salisbury]

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

Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.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

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

Title:
  Suspending Lubuntu 16.04.3 results in network manager stops working

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hello, as per title I noticed that when I suspend Lubuntu 16.04.3 the
  network manager stops working or better it behaves weird. I noticed 4
  behaviors in different occasions:

  1) Enable networking and enable wifi are toggled but the connection I
  used before suspending is not shown (others are).

  2) Enable networking and enable wifi are toggled but no Wi-Fi
  connections are displayed.

  3) The icon changes to loading but it gets stuck, sometimes it just
  stays like that until I restart the network manager or sometimes it
  unstucks and connects, but instead of showing the "internet bars" for
  Wi-Fi it shows the icon as when you connect to a wired connection.

  3)The network manager menu is grey and you can't click anything (no
  connections are shown).

  The only way I have is either to restart nm-applet or restart Lubuntu.

  I have seen this behavior for maybe 3 days, therefore I am assuming
  one package was updated and the update messes up with the suspending
  system.

  The Network Manager I have is 1.2.6-0ubuntu0.16.04.1 and Xfce Power
  Manager is 1.4.4-4ubuntu2.

  Can someone investigate?
  Has anyone else experienced this? 
  If more info are needed I will try to do my best :)

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

-- 
Mailing list: https://launchpad.net/~kernel-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)

[Seth Forshee]

4.13.0-12.13 was promoted to artful-release today and has a fix for
overlayfs erroneously returning ESTALE, can you try this and see if it
fixes the issue?

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

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

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/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 1719733] Re: stale file handle when restarting ntp on overlayfs (maas)

[Joseph Salisbury]

** Tags added: kernel-key

** Also affects: linux (Ubuntu Artful)
   Importance: Critical
   Status: Confirmed

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

-- 
You 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:
  Triaged
Status in linux source package in Artful:
  Triaged

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 1719733] Re: stale file handle when restarting ntp on overlayfs (maas)

[Scott Moser]

Seems likely related to:
  https://github.com/coreos/bugs/issues/2152 

There are three overlayfs commits that add ESTALE returns in 4.13. Two of them 
only affect mount time, and the third is torvalds/linux@b9ac5c2. Other 4.13 
overlayfs changes may have introduced new calls to existing functions returning 
ESTALE, but I haven't checked.
aka, might be an issue *only* in 4.13 
https://patchwork.kernel.org/patch/9955803/

-- 
You 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:
  Confirmed

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 1719733] [NEW] stale file handle when restarting ntp on overlayfs (maas)

[Scott Moser]

Public bug reported:

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

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


** Tags: amd64 apport-bug artful ec2-images

** Attachment added: "install log showing this failure"
   
https://bugs.launchpad.net/bugs/1719733/+attachment/4957409/+files/witchita-install.log

** Bug watch added: github.com/coreos/bugs/issues #2152
   https://github.com/coreos/bugs/issues/2152

-- 
You 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:
  Confirmed

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 

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

[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 1719731

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

Title:
  Suspending Lubuntu 16.04.3 results in network manager stops working

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hello, as per title I noticed that when I suspend Lubuntu 16.04.3 the
  network manager stops working or better it behaves weird. I noticed 4
  behaviors in different occasions:

  1) Enable networking and enable wifi are toggled but the connection I
  used before suspending is not shown (others are).

  2) Enable networking and enable wifi are toggled but no Wi-Fi
  connections are displayed.

  3) The icon changes to loading but it gets stuck, sometimes it just
  stays like that until I restart the network manager or sometimes it
  unstucks and connects, but instead of showing the "internet bars" for
  Wi-Fi it shows the icon as when you connect to a wired connection.

  3)The network manager menu is grey and you can't click anything (no
  connections are shown).

  The only way I have is either to restart nm-applet or restart Lubuntu.

  I have seen this behavior for maybe 3 days, therefore I am assuming
  one package was updated and the update messes up with the suspending
  system.

  The Network Manager I have is 1.2.6-0ubuntu0.16.04.1 and Xfce Power
  Manager is 1.4.4-4ubuntu2.

  Can someone investigate?
  Has anyone else experienced this? 
  If more info are needed I will try to do my best :)

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

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

[Kernel-packages] [Bug 1719731] Re: Suspending Lubuntu 16.04.3 results in network manager stops working

[Mark]

The bug is Confirmed

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

Title:
  Suspending Lubuntu 16.04.3 results in network manager stops working

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hello, as per title I noticed that when I suspend Lubuntu 16.04.3 the
  network manager stops working or better it behaves weird. I noticed 4
  behaviors in different occasions:

  1) Enable networking and enable wifi are toggled but the connection I
  used before suspending is not shown (others are).

  2) Enable networking and enable wifi are toggled but no Wi-Fi
  connections are displayed.

  3) The icon changes to loading but it gets stuck, sometimes it just
  stays like that until I restart the network manager or sometimes it
  unstucks and connects, but instead of showing the "internet bars" for
  Wi-Fi it shows the icon as when you connect to a wired connection.

  3)The network manager menu is grey and you can't click anything (no
  connections are shown).

  The only way I have is either to restart nm-applet or restart Lubuntu.

  I have seen this behavior for maybe 3 days, therefore I am assuming
  one package was updated and the update messes up with the suspending
  system.

  The Network Manager I have is 1.2.6-0ubuntu0.16.04.1 and Xfce Power
  Manager is 1.4.4-4ubuntu2.

  Can someone investigate?
  Has anyone else experienced this? 
  If more info are needed I will try to do my best :)

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

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

[Kernel-packages] [Bug 1719731] [NEW] Suspending Lubuntu 16.04.3 results in network manager stops working

[Mark]

Public bug reported:

Hello, as per title I noticed that when I suspend Lubuntu 16.04.3 the
network manager stops working or better it behaves weird. I noticed 4
behaviors in different occasions:

1) Enable networking and enable wifi are toggled but the connection I
used before suspending is not shown (others are).

2) Enable networking and enable wifi are toggled but no Wi-Fi
connections are displayed.

3) The icon changes to loading but it gets stuck, sometimes it just
stays like that until I restart the network manager or sometimes it
unstucks and connects, but instead of showing the "internet bars" for
Wi-Fi it shows the icon as when you connect to a wired connection.

3)The network manager menu is grey and you can't click anything (no
connections are shown).

The only way I have is either to restart nm-applet or restart Lubuntu.

I have seen this behavior for maybe 3 days, therefore I am assuming one
package was updated and the update messes up with the suspending system.

The Network Manager I have is 1.2.6-0ubuntu0.16.04.1 and Xfce Power
Manager is 1.4.4-4ubuntu2.

Can someone investigate?
Has anyone else experienced this? 
If more info are needed I will try to do my best :)

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


** Tags: lubuntu manager network suspending suspension

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

Title:
  Suspending Lubuntu 16.04.3 results in network manager stops working

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hello, as per title I noticed that when I suspend Lubuntu 16.04.3 the
  network manager stops working or better it behaves weird. I noticed 4
  behaviors in different occasions:

  1) Enable networking and enable wifi are toggled but the connection I
  used before suspending is not shown (others are).

  2) Enable networking and enable wifi are toggled but no Wi-Fi
  connections are displayed.

  3) The icon changes to loading but it gets stuck, sometimes it just
  stays like that until I restart the network manager or sometimes it
  unstucks and connects, but instead of showing the "internet bars" for
  Wi-Fi it shows the icon as when you connect to a wired connection.

  3)The network manager menu is grey and you can't click anything (no
  connections are shown).

  The only way I have is either to restart nm-applet or restart Lubuntu.

  I have seen this behavior for maybe 3 days, therefore I am assuming
  one package was updated and the update messes up with the suspending
  system.

  The Network Manager I have is 1.2.6-0ubuntu0.16.04.1 and Xfce Power
  Manager is 1.4.4-4ubuntu2.

  Can someone investigate?
  Has anyone else experienced this? 
  If more info are needed I will try to do my best :)

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

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

[Kernel-packages] [Bug 1713553] Re: Intel i40e PF reset due to incorrect MDD detection

[Dan Streetman]

The original reporter to me verified that with the patch the problem
does not reoccur for several days, when previously they could reproduce
it within a day; unfortunately as this problem is hard to reproduce that
is the best verification possible from me currently.

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

Title:
  Intel i40e PF reset due to incorrect MDD detection

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

Bug description:
  [Impact]

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

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

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

  This was partially fixed by Xenial commit
  12f8cc59d5886b86372f45290166deca57a60d7a, however there is one
  additional upstream commit required to fully fix the issue:

  commit 841493a3f64395b60554afbcaa17f4350f90e764
  Author: Alexander Duyck 
  Date:   Tue Sep 6 18:05:04 2016 -0700

  i40e: Limit TX descriptor count in cases where frag size is
  greater than 16K

   This fix was never backported into the Xenial 4.4 kernel series, but
  is already present in the Xenial HWE (and Zesty) 4.10 kernel.

  [Testcase]

   In this case, the issue occurs at a customer site using i40e based
  Intel network cards with SR-IOV enabled. Under heavy load, the card will
  reset itself as described.

  [Regression Potential]

  As with any change to a network card driver, this may cause
  regressions with network I/O through i40e card(s).  However, this
  specific change only increases the likelyhood that any specific large
  TSO tx will need to be linearized, which will avoid the PF reset.
  Linearizing a TSO tx that did not need to be linearized will not cause
  any failures, it may only decrease performance slightly.  However this
  patch should only cause linearization when required to avoid the MDD
  detection and PF reset.

  [Other Info]

  The previous bug for this issue is bug 1700834.

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

-- 
Mailing list: https://launchpad.net/~kernel-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

[Daniel van Vugt]

That's great. But all we intended to fix was...
https://launchpad.net/ubuntu/+source/pulseaudio/1:8.0-0ubuntu3.4

-- 
You 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 1711358] Re: 20170817 - ISO hangs on boot on qemu with splash screen enabled and qxl graphics driver

[Jean-Baptiste Lallement]

4.14.0-0.1
from 
https://launchpad.net/~canonical-kernel-team/+archive/ubuntu/unstable/+sourcepub/8271798/+listing-archive-extra

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

Title:
  20170817 - ISO hangs on boot on qemu with splash screen enabled and
  qxl graphics driver

Status in linux package in Ubuntu:
  Confirmed
Status in plymouth package in Ubuntu:
  Confirmed
Status in ubiquity package in Ubuntu:
  Confirmed

Bug description:
  Test Case
  1. Boot artful desktop 20170817 under qemu with qxl
  2. Wait until ubiquity-dm is displayed

  Expected result
  It boots

  Actual result
  It hangs on the splash screen and the dots below the Ubuntu logo are not 
blinking. If the option 'splash' is removed from the boot command line it boots 
successfully.

  It also boots successfully with -vga std but in this case the splash
  screen is in text mode not graphical unlike with the qxl driver.

  - It started with kernel 4.12.
  - It is still happening with kernel 4.13.
  - It only happens when booting from an ISO and not on an installed system.
  - It works with cirrus/vga, but not qxl
  - It works if nosplash is set (or splash removed from the boot command line)
  - It works on Xenial but not on Artful

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

-- 
Mailing list: https://launchpad.net/~kernel-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

[Jason Gambrel]

Received pulseaudio update last night.  Appears to have resolved issue
so far for me, still need a bit of testing.  If it is resolved then MANY
thanks to those who squashed this annoying 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/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 1647036] [bcmwl/trusty] verification still needed

[Ubuntu Foundations Team Bug Bot]

The fix for this bug has been awaiting testing feedback in the -proposed
repository for trusty for more than 90 days.  Please test this fix and
update the bug appropriately with the results.  In the event that the
fix for this bug is still not verified 15 days from now, the package
will be removed from the -proposed repository.

** Tags added: removal-candidate

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

Title:
  Client does not ACK auth/assoc responses from Cisco AP3800

Status in bcmwl package in Ubuntu:
  Fix Released
Status in bcmwl source package in Trusty:
  Fix Committed
Status in bcmwl source package in Xenial:
  Fix Released
Status in bcmwl source package in Yakkety:
  Fix Released
Status in bcmwl source package in Zesty:
  Fix Released

Bug description:
  This client does not ACK Assoc Responses from a Cisco 3800.  Traces
  attached.

  - Model:Dell XPS13 9343
  - OS Version:Ubuntu 14.04.5 LTS
  - WNIC:Broadcom BCM4352 rev. 03 driver version 6.30.223.248
  - SSID:user.wifi (WPA2/dot1x )
  - MAC address:c4:8e:8f:f5:4a:7f
  -Cisco AP : 3800 (wave 2)

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

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

[Kernel-packages] [Bug 1711358] Re: 20170817 - ISO hangs on boot on qemu with splash screen enabled and qxl graphics driver

[Stefan Bader]

Hm, would be good if you noted down more exactly which version/ppa. I
assume it is the mainline builds and likely 4.14~rc2.

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

Title:
  20170817 - ISO hangs on boot on qemu with splash screen enabled and
  qxl graphics driver

Status in linux package in Ubuntu:
  Confirmed
Status in plymouth package in Ubuntu:
  Confirmed
Status in ubiquity package in Ubuntu:
  Confirmed

Bug description:
  Test Case
  1. Boot artful desktop 20170817 under qemu with qxl
  2. Wait until ubiquity-dm is displayed

  Expected result
  It boots

  Actual result
  It hangs on the splash screen and the dots below the Ubuntu logo are not 
blinking. If the option 'splash' is removed from the boot command line it boots 
successfully.

  It also boots successfully with -vga std but in this case the splash
  screen is in text mode not graphical unlike with the qxl driver.

  - It started with kernel 4.12.
  - It is still happening with kernel 4.13.
  - It only happens when booting from an ISO and not on an installed system.
  - It works with cirrus/vga, but not qxl
  - It works if nosplash is set (or splash removed from the boot command line)
  - It works on Xenial but not on Artful

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

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

[Kernel-packages] [Bug 1718107] Re: task-size-overrun test will hang on IBM s390x zKVM / zVM

[Frank Heimes]

** Summary changed:

- brk_near_huge test will hang on IBM s390x zKVM / zVM
+ task-size-overrun test will hang on IBM s390x zKVM / zVM

-- 
You 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 1714966] Re: Backport documentation and help text rework

[Stefan Bader]

Verified new man page content with proposed version in zesty
(0.12.4~17.04.1).

** 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 ubuntu-fan in Ubuntu.
https://bugs.launchpad.net/bugs/1714966

Title:
  Backport documentation and help text rework

Status in ubuntu-fan package in Ubuntu:
  Fix Released
Status in ubuntu-fan source package in Xenial:
  In Progress
Status in ubuntu-fan source package in Zesty:
  Fix Committed

Bug description:
  SRU justification:

  Impact:
  After substantially enhancing all of the documentation (README and man pages) 
as well as the output of built-in help of fanatic, we should backport those 
changes to Zesty and Xenial.

  Fixes:
    * fanatic: recast advanced commands as non-interactive
    * fanatic: fix spelling in primary help
    * fanatic: fix references to fanatic manual page
    * fanatic: Fix typo in progress output
    * README: Refresh documentation
    * fanctl.8: Refresh documentation
    * fanatic.8: Refresh documentation
    * fanatic.8: Reword advanced to non-interactive usage

  Test case:
  Since all changes affect only documentation, there is no test case.

  Regression risk:
  Very low (documentation only)

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

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

[Kernel-packages] [Bug 1714969] Re: Backport remaining delta

[Stefan Bader]

Verification for this part was done by passing ADT testing before
hitting proposed. But also repeated the self-tests manually.

** 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 ubuntu-fan in Ubuntu.
https://bugs.launchpad.net/bugs/1714969

Title:
  Backport remaining delta

Status in ubuntu-fan package in Ubuntu:
  Fix Released
Status in ubuntu-fan source package in Xenial:
  In Progress
Status in ubuntu-fan source package in Zesty:
  Fix Committed

Bug description:
  SRU Justification:

  Impact: In order to lower maintenance burden we want to use the same
  code base of ubuntu-fan throughout all releases. Most of the code
  already is the same. The remaining delta could be split into two
  classes: documentation (for which there is a separate bug report and
  changes to build in and/or DEP8 testing (which this report is about).

  Fixes:
[ Xenial SRU only]
    * debian/control: fix use of obsolete > operator
  This only changes a package dependency. Not affecting use.
    * fanatic: fix local testing and improve docker test
  This fixes up the built-in test for docker and improves it
  (check for container start failure, potential clean up before
  start). Executed as part of DEP8 testing.
    * fanatic: Support nc -N option
  Strictly only needed in Artful but since the code was written
  to check for the new option and only use it if present, there
  is no visible change in previous releases. Covered by DEP8, too.
    * fanatic: Prevent error message without docker installed
  Without docker installed there is a message to stderr when
  disabling fan. This broke the LXD dep8 test. So again, verified
  by DEP8 as the LXD part gets added.
    * fanatic: Supply LXD storage if needed
  At some point the lxd-client started to require providing --storage
  when creating containers. The LXD dep8 test would break then. Fix
  checks for option being available and conditionally provides it.
  Again covered by DEP8 testing.
    * dep8: Add LXD auto-test
  Adds DEP8 testing for LXD (currently Xenial only tests docker).
[ Xenial and Zesty SRU ]
    * DEP8: lxd: Suppress stderr on profile list(*)
  Strictly only needed in Xenial but we want to make the code the
  same. In Xenial doing a lxc profile list is/was printing a hint
  about init to stderr even when lxd init was already done. This
  broke the LXD DEP8 test in Xenial. The fix is to ignore stderr
  for that call which again is verified by DEP8 passing.

  Test case:
  As stated for the individual fixes all the changes will be verified by the 
DEP8 tests passing. The only exception is the packaging fix and that has no 
impact on usage at all.

  Regression Risk:
  Since all is covered by DEP8, and only modifies tests, the overall risk of 
regression for normal operation should be very low.

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

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

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

[bugproxy]

--- Comment From geral...@de.ibm.com 2017-09-26 14:11 EDT---
(In reply to comment #20)
> According to #5: Please let us know when an updated fix becomes available
> and upstream accepted - thx.

Sure, I already posted a fix for this on the libhugetlbfs mailing list, but it 
doesn't look like there is very much traffic or attention on this (new) list:
https://groups.google.com/forum/?hl=en#!forum/libhugetlbfs

BTW, someone from Power apparently got triggered by my patch (or pure
coincidence) an posted a similar fix for Power, so I assume you would
see the same issue ("hanging" task-size-overrun) also on Power.

BTW2, the title of this bug is wrong, it is not "brk_near_huge" that
seems to be hanging, but rather "task-size-overrun".

-- 
You 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:
  brk_near_huge 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]

[Kernel-packages] [Bug 1707610] Re: fanctl does not stop setup on first match

[Stefan Bader]

Verified that upgrading to 0.12.4~17.04.1 allows to enable a Fan Bridge using 
an underlay of 192.168.122.0/24 (this failed with the current version).
Manually ran both docker and LXD self-test. The commented out debug echos are 
actually deliberate to be enabled if in need.

** 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 ubuntu-fan in Ubuntu.
https://bugs.launchpad.net/bugs/1707610

Title:
  fanctl does not stop setup on first match

Status in ubuntu-fan package in Ubuntu:
  Fix Released
Status in ubuntu-fan source package in Xenial:
  Triaged
Status in ubuntu-fan source package in Zesty:
  Fix Committed

Bug description:
  SRU Justification (Zesty/Xenial)

  Impact: When /etc/network/fan contains two entries for the same
  mapping (for example on mapping for the generic network mapping and
  one for a specific interface) it will try to set up the same Fan
  bridge twice.

  Fix: Modify fanctl to only bring up enabled networks in auto mode and
  to correctly apply the most specific local configuration.

  Testcase: If in an environment that uses one of the 192.168.0.0/16 subnets, 
and host has for example a 192.168.1.0/24 address. Then trying to use
   fanatic enable-fan -u 192.168.1.x/24 -o 250.0.0.0/8
  would show an error now and with the fix applied work ok.

  Regression Potential: We tested both cases of using an
  underlay/overlay combination which is in the template section and one
  that was using a subset for the underlay. The former was working
  before the latter not. For that reason we anticipate a low risk of
  regression.

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

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

[Kernel-packages] [Bug 1718397] Re: multipath -ll is not showing the disks which are actually multipath

[Frank Heimes]

** Changed in: ubuntu-power-systems
   Status: Triaged => 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/1718397

Title:
  multipath -ll is not showing the disks which are actually multipath

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

Bug description:
  [Impact]

   * The number of available AIO contexts is severely limited
 on systems with a large number of possible CPUs 
 (e.g., IBM POWER8 processors w/ 20ish cores * 8 threads/core,
 and other multithreaded server-class processors).

   * This prevents application such as multipath/directio checker
 to provide all of the available devices to the system.

   * Other applications which depend on AIO can be affected/limited.

   * The patch fixes how aio increments the number of active contexts
 (seen in /proc/sys/fs/aio-nr) and checks that against the global
 limit (seen in /proc/sys/fs/aio-max-nr).

  [Test Case]

   * A synthetic test-case is attached (io_setup_v2.c) and demonstrated
 (original/patched kernels) in comment #4.

   * Trying to perform multipath discovery in debug/verbose mode
 (i.e., "multipath -v3" command) with sufficient number of 
 individual paths using the "directio" path checker should
 demonstrate the problem/solution as well (i.e., presence or
 not of "io_setup failed" messages).

  [Regression Potential]

   * Note the fix is trivial and has been tested by several users,
 even caused the introduction of a new test-case in "libaio";
 (but that can never be a strong enough reason for no more errors).

   * Applications which use aio with small "nr_events" value as argument
 to "io_setup()" now have access to a much larger number of aio contexts;
 but hopefully those apps are already only requesting what they need,
 not trying to get more and more.

   * Applications which relied in the _incorrect_ behavior of 
'/proc/sys/fs/aio-nr'
 being possibly greater than '/proc/sys/fs/aio-max-nr' might have problems,
 but those apps should be fixed.


  Problem Description
  =
  I am facing this issue for Texan Flash storage 840 disks which are coming 
from coho and salfish adapter

  coho adapter with 840 storage  is 3G disks and salfish adapter with
  840 is 12G disks

  I am able to see those disks in lsblk o/p but not in multipath -ll
  comamnd

  0004:01:00.0 Coho: Saturn-X  U78C9.001.WZS0060-P1-C6 
0x1090fa2a51f8  host10  Online
  0004:01:00.1 Coho: Saturn-X  U78C9.001.WZS0060-P1-C6 
0x1090fa2a51f9  host11  Online

  0005:09:00.0 Sailfish: QLogic 8GBU78C9.001.WZS0060-P1-C9 
0x2124ff787778  host2   Online
  0005:09:00.1 Sailfish: QLogic 8GBU78C9.001.WZS0060-P1-C9 
0x2124ff787779  host4   Online

  root@luckyv1:/dev/disk# multipath -ll | grep "size=3.0G" -B 1
  root@luckyv1:/dev/disk# multipath -ll | grep "size=12G" -B 1
  root@luckyv1:/dev/disk#

  == Comment: #3 - Luciano Chavez  - 2016-09-20 20:22:20 ==
  I edited /etc/multipath.conf and added
  verbosity 6

  to crank up the output and ran multipath -ll and saved it off to a
  text file (attached). All the using the directio checker failed and
  those using the tur checker seem to work.

  Sep 20 20:07:36 | loading //lib/multipath/libcheckdirectio.so checker
  Sep 20 20:07:36 | loading //lib/multipath/libprioconst.so prioritizer
  Sep 20 20:07:36 | Discover device 
/sys/devices/pci:00/:00:00.0/:01:00.0/host3/rport-3:0-2/target3:0:0/3:0:0:0/block/sdai
  Sep 20 20:07:36 | sdai: udev property ID_WWN whitelisted
  Sep 20 20:07:36 | sdai: not found in pathvec
  Sep 20 20:07:36 | sdai: mask = 0x25
  Sep 20 20:07:36 | sdai: dev_t = 66:32
  Sep 20 20:07:36 | open 
'/sys/devices/pci:00/:00:00.0/:01:00.0/host3/rport-3:0-2/target3:0:0/3:0:0:0/block/sdai/size'
  Sep 20 20:07:36 | sdai: size = 20971520
  Sep 20 20:07:36 | sdai: vendor = IBM
  Sep 20 20:07:36 | sdai: product = FlashSystem-9840
  Sep 20 20:07:36 | sdai: rev = 1442
  Sep 20 20:07:36 | sdai: h:b:t:l = 3:0:0:0
  Sep 20 20:07:36 | SCSI target 3:0:0 -> FC rport 3:0-2
  Sep 20 20:07:36 | sdai: tgt_node_name = 0x500507605e839800
  Sep 20 20:07:36 | open 
'/sys/devices/pci:00/:00:00.0/:01:00.0/host3/rport-3:0-2/target3:0:0/3:0:0:0/state'
  Sep 20 20:07:36 | sdai: path state = running
  Sep 20 20:07:36 | sdai: get_state
  Sep 20 20:07:36 | sdai: path_checker = directio (internal default)
  Sep 20 20:07:36 | sdai: checker timeout = 30 ms (internal default)
  Sep 20 20:07:36 | io_setup failed

[Kernel-packages] [Bug 1718107] Re: brk_near_huge test will hang on IBM s390x zKVM / zVM

[Frank Heimes]

According to #5: Please let us know when an updated fix becomes
available and upstream accepted - thx.

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

** Changed in: ubuntu-z-systems
   Status: Triaged => 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/1718107

Title:
  brk_near_huge 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] 

[Kernel-packages] [Bug 1696102] Re: xfs/073 test fails with Metadata corruption detected on xfs file system (xfsprogs)

[Launchpad Bug Tracker]

This bug was fixed in the package xfsprogs - 4.3.0+nmu1ubuntu1.1

---
xfsprogs (4.3.0+nmu1ubuntu1.1) xenial; urgency=medium

  * xfs_copy: Fix meta UUID handling on multiple copies upstream fix
cbca895541facb. (LP: #1696102)

 -- Brian Murray   Tue, 05 Sep 2017 09:59:09 -0700

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

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

Title:
  xfs/073 test fails with Metadata corruption detected on xfs file
  system (xfsprogs)

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

Bug description:
  Impact
  ==
  When making multiple copies of a V5 filesystem with xfs_copy those copies 
will be corrupt due to incorrect UUIDs.

  Test Case
  =
  See the detailed steps to create the test environment in comment #20.

  Regression Potential
  
  From the patch "Most of this patch is changing comments and re-ordering tests 
to match; the functional change is to simply use the *sb rather than the 
*ag_hdr to identify the proper metadata UUID." So this seems pretty 
straightforward and given that copy process is currently broken, because the 
copies are corrupt, this will be an improvement.

  Original Description
  

  Problem Description
  
  xfs/073 test fails with Metadata corruption detected on xfs file system. Test 
fails with _check_xfs_filesystem: filesystem on /mnt/test/84004.image2 is 
inconsistent.

  # diff -u tests/xfs/073.out /root/xfstests-dev/results//xfs/073.out.bad
  --- tests/xfs/073.out 2017-03-23 12:13:05.288877197 +0530
  +++ /root/xfstests-dev/results//xfs/073.out.bad   2017-03-27 
11:11:43.023059702 +0530
  @@ -59,8 +59,7 @@
   comparing new image geometry to old
   unmounting and removing new image
   checking new image
  -mounting new image on loopback
  -comparing new image files to old
  -comparing new image directories to old
  -comparing new image geometry to old
  -unmounting and removing new image
  +_check_xfs_filesystem: filesystem on /mnt/test/15413.image2 is inconsistent 
(c)
  +(see /root/xfstests-dev/results//xfs/073.full for details)
  +_check_xfs_filesystem: filesystem on /mnt/test/15413.image2 is inconsistent 
(r)
  +(see /root/xfstests-dev/results//xfs/073.full for details)

  Metadata corruption detected at xfs_agf block 0x1/0x200

  # 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.conf for running with created loop device
  5.. Run xfstests-dev test  : ./check tests/xfs/073

  Full log is attached.

  == Comment: #2 - Harish Sriram  - 2017-05-31 01:22:11 ==
  (In reply to comment #1)
  > Hi Harish,
  > Can you share the steps used in creating the loop device with xfs filesystem
  > ?
  >
  > Thank you.

  Create loop device:
  # mkdir /mnt/loop-device /mnt/test /mnt/scratch

  # for i in $(seq 0 1); do fallocate -o 0 -l 5GiB 
/mnt/loop-device/file-$i.img; done
  # for i in $(seq 0 1); do losetup /dev/loop$i /mnt/loop-device/file-$i.img; 
done

  Create File system:
  # for i in $(seq 0 1); do mkfs.ext4 -F /dev/loop$i; done

  # cat local.config
  export TEST_DEV=/dev/loop0
  export TEST_DIR=/mnt/test
  export SCRATCH_DEV=/dev/loop1
  export SCRATCH_MNT=/mnt/scratch

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

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

[Kernel-packages] [Bug 1696102] Update Released

[Brian Murray]

The verification of the Stable Release Update for xfsprogs has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  xfs/073 test fails with Metadata corruption detected on xfs file
  system (xfsprogs)

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

Bug description:
  Impact
  ==
  When making multiple copies of a V5 filesystem with xfs_copy those copies 
will be corrupt due to incorrect UUIDs.

  Test Case
  =
  See the detailed steps to create the test environment in comment #20.

  Regression Potential
  
  From the patch "Most of this patch is changing comments and re-ordering tests 
to match; the functional change is to simply use the *sb rather than the 
*ag_hdr to identify the proper metadata UUID." So this seems pretty 
straightforward and given that copy process is currently broken, because the 
copies are corrupt, this will be an improvement.

  Original Description
  

  Problem Description
  
  xfs/073 test fails with Metadata corruption detected on xfs file system. Test 
fails with _check_xfs_filesystem: filesystem on /mnt/test/84004.image2 is 
inconsistent.

  # diff -u tests/xfs/073.out /root/xfstests-dev/results//xfs/073.out.bad
  --- tests/xfs/073.out 2017-03-23 12:13:05.288877197 +0530
  +++ /root/xfstests-dev/results//xfs/073.out.bad   2017-03-27 
11:11:43.023059702 +0530
  @@ -59,8 +59,7 @@
   comparing new image geometry to old
   unmounting and removing new image
   checking new image
  -mounting new image on loopback
  -comparing new image files to old
  -comparing new image directories to old
  -comparing new image geometry to old
  -unmounting and removing new image
  +_check_xfs_filesystem: filesystem on /mnt/test/15413.image2 is inconsistent 
(c)
  +(see /root/xfstests-dev/results//xfs/073.full for details)
  +_check_xfs_filesystem: filesystem on /mnt/test/15413.image2 is inconsistent 
(r)
  +(see /root/xfstests-dev/results//xfs/073.full for details)

  Metadata corruption detected at xfs_agf block 0x1/0x200

  # 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.conf for running with created loop device
  5.. Run xfstests-dev test  : ./check tests/xfs/073

  Full log is attached.

  == Comment: #2 - Harish Sriram  - 2017-05-31 01:22:11 ==
  (In reply to comment #1)
  > Hi Harish,
  > Can you share the steps used in creating the loop device with xfs filesystem
  > ?
  >
  > Thank you.

  Create loop device:
  # mkdir /mnt/loop-device /mnt/test /mnt/scratch

  # for i in $(seq 0 1); do fallocate -o 0 -l 5GiB 
/mnt/loop-device/file-$i.img; done
  # for i in $(seq 0 1); do losetup /dev/loop$i /mnt/loop-device/file-$i.img; 
done

  Create File system:
  # for i in $(seq 0 1); do mkfs.ext4 -F /dev/loop$i; done

  # cat local.config
  export TEST_DEV=/dev/loop0
  export TEST_DIR=/mnt/test
  export SCRATCH_DEV=/dev/loop1
  export SCRATCH_MNT=/mnt/scratch

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

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

[Kernel-packages] [Bug 1718980] Re: linux: 4.13.0-12.13 -proposed tracker

[Brad Figg]

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


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

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

** Description changed:

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

** Description changed:

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

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

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

Title:
  linux: 4.13.0-12.13 -proposed tracker

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

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

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

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

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

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

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

[Brad Figg]

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

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

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

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

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

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

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

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1718159
  phase: Uploaded
+ kernel-stable-phase-changed:Tuesday, 26. September 2017 17:34 UTC
+ kernel-stable-phase:Promoted to proposed

** Description changed:

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

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-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:
  Confirmed
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  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

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

[Anmar Oueja]

I did that with yesterday's Ubuntu 17.10 live image and it did boot.

Q: Does that mean the acceleration is done by the Intel board instead?

On Tue, Sep 26, 2017 at 8:56 AM, Hlini Melsteð Jóngeirsson
 wrote:
> I just tried adding "blacklist=nouveau modprobe.blacklist=nouveau" but
> it will not boot.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> 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:
>   Incomplete
>
> 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

-- 
You 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:
  Incomplete

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: 

[Kernel-packages] [Bug 1591813] Re: [Feature] SKX: Support crystall ridge / far / near memory indication in PEBS

[Launchpad Bug Tracker]

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

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

  * linux: 4.13.0-12.13 -proposed tracker (LP: #1718980)

  * [Feature] SKX: Support crystall ridge / far / near memory indication in PEBS
(LP: #1591813)
- perf/x86: Move Nehalem PEBS code to flag
- perf/x86: Fix data source decoding for Skylake

  * Upgrade to 4.13.0-11.12 in artful amd64 VM breaks display on wayland
(LP: #1718679)
- [Config] CONFIG_DRM_VBOXVIDEO=n

  * ipmmu-vmsa driver breaks arm64 boots (LP: #1718734)
- [Config] Disable CONFIG_IPMMU_VMSA on arm64

  * Vlun resize request could fail with cxlflash driver (LP: #1713575)
- scsi: cxlflash: Fix vlun resize failure in the shrink path

  * multipath -ll is not showing the disks which are actually multipath
(LP: #1718397)
- fs: aio: fix the increment of aio-nr and counting against aio-max-nr

  * [Feature] Crystal Ridge - BTT - Rework error clearing (LP: #1704350)
- libnvdimm, btt: fix a missed NVDIMM_IO_ATOMIC case in the write path
- libnvdimm, btt: refactor map entry operations with macros
- libnvdimm, btt: ensure that flags were also unchanged during a map_read
- libnvdimm, btt: cache sector_size in arena_info
- libnvdimm: fix potential deadlock while clearing errors
- libnvdimm, btt: rework error clearing

  * [Feature] Crystal Ridge - have 4k DAX faults use a common zero page
(LP: #1704439)
- mm: add vm_insert_mixed_mkwrite()
- dax: relocate some dax functions
- dax: use common 4k zero page for dax mmap reads
- dax: remove DAX code from page_cache_tree_insert()
- dax: move all DAX radix tree defs to fs/dax.c

  * [bug] 17.10: CDP test fail on platform of Purley-2S/4S/Neoncity,BDW-
de/ep/ex, (LP: #1716843)
- SAUCE: (no-up) x86/intel_rdt: Fix cdp info directory files issue

  * [featue] GPIO support for Denverton (LP: #1591829)
- pinctrl: intel: Add Intel Denverton pin controller support

  * ETPS/2 Elantech Touchpad inconsistently detected (Gigabyte P57W laptop)
(LP: #1594214)
- Input: i8042 - add Gigabyte P57 to the keyboard reset table

  * autopkgtest profile fails to build on armhf (LP: #1717920)
- [Packaging] autopkgtest -- disable d-i when dropping flavours

  * Artful update to v4.13.3 stable release (LP: #1718412)
- Revert "net: use lib/percpu_counter API for fragmentation mem accounting"
- Revert "net: fix percpu memory leaks"
- gianfar: Fix Tx flow control deactivation
- vhost_net: correctly check tx avail during rx busy polling
- ip6_gre: update mtu properly in ip6gre_err
- udp: drop head states only when all skb references are gone
- ipv6: fix memory leak with multiple tables during netns destruction
- ipv6: fix typo in fib6_net_exit()
- sctp: fix missing wake ups in some situations
- tcp: fix a request socket leak
- ip_tunnel: fix setting ttl and tos value in collect_md mode
- f2fs: let fill_super handle roll-forward errors
- f2fs: check hot_data for roll-forward recovery
- x86/fsgsbase/64: Fully initialize FS and GS state in start_thread_common
- x86/fsgsbase/64: Report FSBASE and GSBASE correctly in core dumps
- x86/switch_to/64: Rewrite FS/GS switching yet again to fix AMD CPUs
- x86/mm, mm/hwpoison: Clear PRESENT bit for kernel 1:1 mappings of poison
  pages
- ovl: fix false positive ESTALE on lookup
- fuse: allow server to run in different pid_ns
- idr: remove WARN_ON_ONCE() when trying to replace negative ID
- libnvdimm, btt: check memory allocation failure
- libnvdimm: fix integer overflow static analysis warning
- xfs: write unmount record for ro mounts
- xfs: toggle readonly state around xfs_log_mount_finish
- xfs: Add infrastructure needed for error propagation during buffer IO
  failure
- xfs: Properly retry failed inode items in case of error during buffer
  writeback
- xfs: fix recovery failure when log record header wraps log end
- xfs: always verify the log tail during recovery
- xfs: fix log recovery corruption error due to tail overwrite
- xfs: handle -EFSCORRUPTED during head/tail verification
- xfs: stop searching for free slots in an inode chunk when there are none
- xfs: evict all inodes involved with log redo item
- xfs: check for race with xfs_reclaim_inode() in xfs_ifree_cluster()
- xfs: open-code xfs_buf_item_dirty()
- xfs: remove unnecessary dirty bli format check for ordered bufs
- xfs: ordered buffer log items are never formatted
- xfs: refactor buffer logging into buffer dirtying helper
- xfs: don't log dirty ranges for ordered buffers
- xfs: skip bmbt block ino validation during owner change
- xfs: move bmbt owner change to last step of extent swap
- xfs: disallow marking previously dirty buffers as ordered
- xfs: relog dirty buffers during swapext bmbt owner change
- xfs: disable per-inode DAX 

[Kernel-packages] [Bug 1594214] Re: ETPS/2 Elantech Touchpad inconsistently detected (Gigabyte P57W laptop)

[Launchpad Bug Tracker]

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

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

  * linux: 4.13.0-12.13 -proposed tracker (LP: #1718980)

  * [Feature] SKX: Support crystall ridge / far / near memory indication in PEBS
(LP: #1591813)
- perf/x86: Move Nehalem PEBS code to flag
- perf/x86: Fix data source decoding for Skylake

  * Upgrade to 4.13.0-11.12 in artful amd64 VM breaks display on wayland
(LP: #1718679)
- [Config] CONFIG_DRM_VBOXVIDEO=n

  * ipmmu-vmsa driver breaks arm64 boots (LP: #1718734)
- [Config] Disable CONFIG_IPMMU_VMSA on arm64

  * Vlun resize request could fail with cxlflash driver (LP: #1713575)
- scsi: cxlflash: Fix vlun resize failure in the shrink path

  * multipath -ll is not showing the disks which are actually multipath
(LP: #1718397)
- fs: aio: fix the increment of aio-nr and counting against aio-max-nr

  * [Feature] Crystal Ridge - BTT - Rework error clearing (LP: #1704350)
- libnvdimm, btt: fix a missed NVDIMM_IO_ATOMIC case in the write path
- libnvdimm, btt: refactor map entry operations with macros
- libnvdimm, btt: ensure that flags were also unchanged during a map_read
- libnvdimm, btt: cache sector_size in arena_info
- libnvdimm: fix potential deadlock while clearing errors
- libnvdimm, btt: rework error clearing

  * [Feature] Crystal Ridge - have 4k DAX faults use a common zero page
(LP: #1704439)
- mm: add vm_insert_mixed_mkwrite()
- dax: relocate some dax functions
- dax: use common 4k zero page for dax mmap reads
- dax: remove DAX code from page_cache_tree_insert()
- dax: move all DAX radix tree defs to fs/dax.c

  * [bug] 17.10: CDP test fail on platform of Purley-2S/4S/Neoncity,BDW-
de/ep/ex, (LP: #1716843)
- SAUCE: (no-up) x86/intel_rdt: Fix cdp info directory files issue

  * [featue] GPIO support for Denverton (LP: #1591829)
- pinctrl: intel: Add Intel Denverton pin controller support

  * ETPS/2 Elantech Touchpad inconsistently detected (Gigabyte P57W laptop)
(LP: #1594214)
- Input: i8042 - add Gigabyte P57 to the keyboard reset table

  * autopkgtest profile fails to build on armhf (LP: #1717920)
- [Packaging] autopkgtest -- disable d-i when dropping flavours

  * Artful update to v4.13.3 stable release (LP: #1718412)
- Revert "net: use lib/percpu_counter API for fragmentation mem accounting"
- Revert "net: fix percpu memory leaks"
- gianfar: Fix Tx flow control deactivation
- vhost_net: correctly check tx avail during rx busy polling
- ip6_gre: update mtu properly in ip6gre_err
- udp: drop head states only when all skb references are gone
- ipv6: fix memory leak with multiple tables during netns destruction
- ipv6: fix typo in fib6_net_exit()
- sctp: fix missing wake ups in some situations
- tcp: fix a request socket leak
- ip_tunnel: fix setting ttl and tos value in collect_md mode
- f2fs: let fill_super handle roll-forward errors
- f2fs: check hot_data for roll-forward recovery
- x86/fsgsbase/64: Fully initialize FS and GS state in start_thread_common
- x86/fsgsbase/64: Report FSBASE and GSBASE correctly in core dumps
- x86/switch_to/64: Rewrite FS/GS switching yet again to fix AMD CPUs
- x86/mm, mm/hwpoison: Clear PRESENT bit for kernel 1:1 mappings of poison
  pages
- ovl: fix false positive ESTALE on lookup
- fuse: allow server to run in different pid_ns
- idr: remove WARN_ON_ONCE() when trying to replace negative ID
- libnvdimm, btt: check memory allocation failure
- libnvdimm: fix integer overflow static analysis warning
- xfs: write unmount record for ro mounts
- xfs: toggle readonly state around xfs_log_mount_finish
- xfs: Add infrastructure needed for error propagation during buffer IO
  failure
- xfs: Properly retry failed inode items in case of error during buffer
  writeback
- xfs: fix recovery failure when log record header wraps log end
- xfs: always verify the log tail during recovery
- xfs: fix log recovery corruption error due to tail overwrite
- xfs: handle -EFSCORRUPTED during head/tail verification
- xfs: stop searching for free slots in an inode chunk when there are none
- xfs: evict all inodes involved with log redo item
- xfs: check for race with xfs_reclaim_inode() in xfs_ifree_cluster()
- xfs: open-code xfs_buf_item_dirty()
- xfs: remove unnecessary dirty bli format check for ordered bufs
- xfs: ordered buffer log items are never formatted
- xfs: refactor buffer logging into buffer dirtying helper
- xfs: don't log dirty ranges for ordered buffers
- xfs: skip bmbt block ino validation during owner change
- xfs: move bmbt owner change to last step of extent swap
- xfs: disallow marking previously dirty buffers as ordered
- xfs: relog dirty buffers during swapext bmbt owner change
- xfs: disable per-inode DAX 

[Kernel-packages] [Bug 1591829] Re: [featue] GPIO support for Denverton

[Launchpad Bug Tracker]

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

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

  * linux: 4.13.0-12.13 -proposed tracker (LP: #1718980)

  * [Feature] SKX: Support crystall ridge / far / near memory indication in PEBS
(LP: #1591813)
- perf/x86: Move Nehalem PEBS code to flag
- perf/x86: Fix data source decoding for Skylake

  * Upgrade to 4.13.0-11.12 in artful amd64 VM breaks display on wayland
(LP: #1718679)
- [Config] CONFIG_DRM_VBOXVIDEO=n

  * ipmmu-vmsa driver breaks arm64 boots (LP: #1718734)
- [Config] Disable CONFIG_IPMMU_VMSA on arm64

  * Vlun resize request could fail with cxlflash driver (LP: #1713575)
- scsi: cxlflash: Fix vlun resize failure in the shrink path

  * multipath -ll is not showing the disks which are actually multipath
(LP: #1718397)
- fs: aio: fix the increment of aio-nr and counting against aio-max-nr

  * [Feature] Crystal Ridge - BTT - Rework error clearing (LP: #1704350)
- libnvdimm, btt: fix a missed NVDIMM_IO_ATOMIC case in the write path
- libnvdimm, btt: refactor map entry operations with macros
- libnvdimm, btt: ensure that flags were also unchanged during a map_read
- libnvdimm, btt: cache sector_size in arena_info
- libnvdimm: fix potential deadlock while clearing errors
- libnvdimm, btt: rework error clearing

  * [Feature] Crystal Ridge - have 4k DAX faults use a common zero page
(LP: #1704439)
- mm: add vm_insert_mixed_mkwrite()
- dax: relocate some dax functions
- dax: use common 4k zero page for dax mmap reads
- dax: remove DAX code from page_cache_tree_insert()
- dax: move all DAX radix tree defs to fs/dax.c

  * [bug] 17.10: CDP test fail on platform of Purley-2S/4S/Neoncity,BDW-
de/ep/ex, (LP: #1716843)
- SAUCE: (no-up) x86/intel_rdt: Fix cdp info directory files issue

  * [featue] GPIO support for Denverton (LP: #1591829)
- pinctrl: intel: Add Intel Denverton pin controller support

  * ETPS/2 Elantech Touchpad inconsistently detected (Gigabyte P57W laptop)
(LP: #1594214)
- Input: i8042 - add Gigabyte P57 to the keyboard reset table

  * autopkgtest profile fails to build on armhf (LP: #1717920)
- [Packaging] autopkgtest -- disable d-i when dropping flavours

  * Artful update to v4.13.3 stable release (LP: #1718412)
- Revert "net: use lib/percpu_counter API for fragmentation mem accounting"
- Revert "net: fix percpu memory leaks"
- gianfar: Fix Tx flow control deactivation
- vhost_net: correctly check tx avail during rx busy polling
- ip6_gre: update mtu properly in ip6gre_err
- udp: drop head states only when all skb references are gone
- ipv6: fix memory leak with multiple tables during netns destruction
- ipv6: fix typo in fib6_net_exit()
- sctp: fix missing wake ups in some situations
- tcp: fix a request socket leak
- ip_tunnel: fix setting ttl and tos value in collect_md mode
- f2fs: let fill_super handle roll-forward errors
- f2fs: check hot_data for roll-forward recovery
- x86/fsgsbase/64: Fully initialize FS and GS state in start_thread_common
- x86/fsgsbase/64: Report FSBASE and GSBASE correctly in core dumps
- x86/switch_to/64: Rewrite FS/GS switching yet again to fix AMD CPUs
- x86/mm, mm/hwpoison: Clear PRESENT bit for kernel 1:1 mappings of poison
  pages
- ovl: fix false positive ESTALE on lookup
- fuse: allow server to run in different pid_ns
- idr: remove WARN_ON_ONCE() when trying to replace negative ID
- libnvdimm, btt: check memory allocation failure
- libnvdimm: fix integer overflow static analysis warning
- xfs: write unmount record for ro mounts
- xfs: toggle readonly state around xfs_log_mount_finish
- xfs: Add infrastructure needed for error propagation during buffer IO
  failure
- xfs: Properly retry failed inode items in case of error during buffer
  writeback
- xfs: fix recovery failure when log record header wraps log end
- xfs: always verify the log tail during recovery
- xfs: fix log recovery corruption error due to tail overwrite
- xfs: handle -EFSCORRUPTED during head/tail verification
- xfs: stop searching for free slots in an inode chunk when there are none
- xfs: evict all inodes involved with log redo item
- xfs: check for race with xfs_reclaim_inode() in xfs_ifree_cluster()
- xfs: open-code xfs_buf_item_dirty()
- xfs: remove unnecessary dirty bli format check for ordered bufs
- xfs: ordered buffer log items are never formatted
- xfs: refactor buffer logging into buffer dirtying helper
- xfs: don't log dirty ranges for ordered buffers
- xfs: skip bmbt block ino validation during owner change
- xfs: move bmbt owner change to last step of extent swap
- xfs: disallow marking previously dirty buffers as ordered
- xfs: relog dirty buffers during swapext bmbt owner change
- xfs: disable per-inode DAX 

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

[Launchpad Bug Tracker]

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

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

  * linux: 4.13.0-12.13 -proposed tracker (LP: #1718980)

  * [Feature] SKX: Support crystall ridge / far / near memory indication in PEBS
(LP: #1591813)
- perf/x86: Move Nehalem PEBS code to flag
- perf/x86: Fix data source decoding for Skylake

  * Upgrade to 4.13.0-11.12 in artful amd64 VM breaks display on wayland
(LP: #1718679)
- [Config] CONFIG_DRM_VBOXVIDEO=n

  * ipmmu-vmsa driver breaks arm64 boots (LP: #1718734)
- [Config] Disable CONFIG_IPMMU_VMSA on arm64

  * Vlun resize request could fail with cxlflash driver (LP: #1713575)
- scsi: cxlflash: Fix vlun resize failure in the shrink path

  * multipath -ll is not showing the disks which are actually multipath
(LP: #1718397)
- fs: aio: fix the increment of aio-nr and counting against aio-max-nr

  * [Feature] Crystal Ridge - BTT - Rework error clearing (LP: #1704350)
- libnvdimm, btt: fix a missed NVDIMM_IO_ATOMIC case in the write path
- libnvdimm, btt: refactor map entry operations with macros
- libnvdimm, btt: ensure that flags were also unchanged during a map_read
- libnvdimm, btt: cache sector_size in arena_info
- libnvdimm: fix potential deadlock while clearing errors
- libnvdimm, btt: rework error clearing

  * [Feature] Crystal Ridge - have 4k DAX faults use a common zero page
(LP: #1704439)
- mm: add vm_insert_mixed_mkwrite()
- dax: relocate some dax functions
- dax: use common 4k zero page for dax mmap reads
- dax: remove DAX code from page_cache_tree_insert()
- dax: move all DAX radix tree defs to fs/dax.c

  * [bug] 17.10: CDP test fail on platform of Purley-2S/4S/Neoncity,BDW-
de/ep/ex, (LP: #1716843)
- SAUCE: (no-up) x86/intel_rdt: Fix cdp info directory files issue

  * [featue] GPIO support for Denverton (LP: #1591829)
- pinctrl: intel: Add Intel Denverton pin controller support

  * ETPS/2 Elantech Touchpad inconsistently detected (Gigabyte P57W laptop)
(LP: #1594214)
- Input: i8042 - add Gigabyte P57 to the keyboard reset table

  * autopkgtest profile fails to build on armhf (LP: #1717920)
- [Packaging] autopkgtest -- disable d-i when dropping flavours

  * Artful update to v4.13.3 stable release (LP: #1718412)
- Revert "net: use lib/percpu_counter API for fragmentation mem accounting"
- Revert "net: fix percpu memory leaks"
- gianfar: Fix Tx flow control deactivation
- vhost_net: correctly check tx avail during rx busy polling
- ip6_gre: update mtu properly in ip6gre_err
- udp: drop head states only when all skb references are gone
- ipv6: fix memory leak with multiple tables during netns destruction
- ipv6: fix typo in fib6_net_exit()
- sctp: fix missing wake ups in some situations
- tcp: fix a request socket leak
- ip_tunnel: fix setting ttl and tos value in collect_md mode
- f2fs: let fill_super handle roll-forward errors
- f2fs: check hot_data for roll-forward recovery
- x86/fsgsbase/64: Fully initialize FS and GS state in start_thread_common
- x86/fsgsbase/64: Report FSBASE and GSBASE correctly in core dumps
- x86/switch_to/64: Rewrite FS/GS switching yet again to fix AMD CPUs
- x86/mm, mm/hwpoison: Clear PRESENT bit for kernel 1:1 mappings of poison
  pages
- ovl: fix false positive ESTALE on lookup
- fuse: allow server to run in different pid_ns
- idr: remove WARN_ON_ONCE() when trying to replace negative ID
- libnvdimm, btt: check memory allocation failure
- libnvdimm: fix integer overflow static analysis warning
- xfs: write unmount record for ro mounts
- xfs: toggle readonly state around xfs_log_mount_finish
- xfs: Add infrastructure needed for error propagation during buffer IO
  failure
- xfs: Properly retry failed inode items in case of error during buffer
  writeback
- xfs: fix recovery failure when log record header wraps log end
- xfs: always verify the log tail during recovery
- xfs: fix log recovery corruption error due to tail overwrite
- xfs: handle -EFSCORRUPTED during head/tail verification
- xfs: stop searching for free slots in an inode chunk when there are none
- xfs: evict all inodes involved with log redo item
- xfs: check for race with xfs_reclaim_inode() in xfs_ifree_cluster()
- xfs: open-code xfs_buf_item_dirty()
- xfs: remove unnecessary dirty bli format check for ordered bufs
- xfs: ordered buffer log items are never formatted
- xfs: refactor buffer logging into buffer dirtying helper
- xfs: don't log dirty ranges for ordered buffers
- xfs: skip bmbt block ino validation during owner change
- xfs: move bmbt owner change to last step of extent swap
- xfs: disallow marking previously dirty buffers as ordered
- xfs: relog dirty buffers during swapext bmbt owner change
- xfs: disable per-inode DAX 

[Kernel-packages] [Bug 1716843] Re: [bug] 17.10: CDP test fail on platform of Purley-2S/4S/Neoncity, BDW-de/ep/ex,

[Launchpad Bug Tracker]

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

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

  * linux: 4.13.0-12.13 -proposed tracker (LP: #1718980)

  * [Feature] SKX: Support crystall ridge / far / near memory indication in PEBS
(LP: #1591813)
- perf/x86: Move Nehalem PEBS code to flag
- perf/x86: Fix data source decoding for Skylake

  * Upgrade to 4.13.0-11.12 in artful amd64 VM breaks display on wayland
(LP: #1718679)
- [Config] CONFIG_DRM_VBOXVIDEO=n

  * ipmmu-vmsa driver breaks arm64 boots (LP: #1718734)
- [Config] Disable CONFIG_IPMMU_VMSA on arm64

  * Vlun resize request could fail with cxlflash driver (LP: #1713575)
- scsi: cxlflash: Fix vlun resize failure in the shrink path

  * multipath -ll is not showing the disks which are actually multipath
(LP: #1718397)
- fs: aio: fix the increment of aio-nr and counting against aio-max-nr

  * [Feature] Crystal Ridge - BTT - Rework error clearing (LP: #1704350)
- libnvdimm, btt: fix a missed NVDIMM_IO_ATOMIC case in the write path
- libnvdimm, btt: refactor map entry operations with macros
- libnvdimm, btt: ensure that flags were also unchanged during a map_read
- libnvdimm, btt: cache sector_size in arena_info
- libnvdimm: fix potential deadlock while clearing errors
- libnvdimm, btt: rework error clearing

  * [Feature] Crystal Ridge - have 4k DAX faults use a common zero page
(LP: #1704439)
- mm: add vm_insert_mixed_mkwrite()
- dax: relocate some dax functions
- dax: use common 4k zero page for dax mmap reads
- dax: remove DAX code from page_cache_tree_insert()
- dax: move all DAX radix tree defs to fs/dax.c

  * [bug] 17.10: CDP test fail on platform of Purley-2S/4S/Neoncity,BDW-
de/ep/ex, (LP: #1716843)
- SAUCE: (no-up) x86/intel_rdt: Fix cdp info directory files issue

  * [featue] GPIO support for Denverton (LP: #1591829)
- pinctrl: intel: Add Intel Denverton pin controller support

  * ETPS/2 Elantech Touchpad inconsistently detected (Gigabyte P57W laptop)
(LP: #1594214)
- Input: i8042 - add Gigabyte P57 to the keyboard reset table

  * autopkgtest profile fails to build on armhf (LP: #1717920)
- [Packaging] autopkgtest -- disable d-i when dropping flavours

  * Artful update to v4.13.3 stable release (LP: #1718412)
- Revert "net: use lib/percpu_counter API for fragmentation mem accounting"
- Revert "net: fix percpu memory leaks"
- gianfar: Fix Tx flow control deactivation
- vhost_net: correctly check tx avail during rx busy polling
- ip6_gre: update mtu properly in ip6gre_err
- udp: drop head states only when all skb references are gone
- ipv6: fix memory leak with multiple tables during netns destruction
- ipv6: fix typo in fib6_net_exit()
- sctp: fix missing wake ups in some situations
- tcp: fix a request socket leak
- ip_tunnel: fix setting ttl and tos value in collect_md mode
- f2fs: let fill_super handle roll-forward errors
- f2fs: check hot_data for roll-forward recovery
- x86/fsgsbase/64: Fully initialize FS and GS state in start_thread_common
- x86/fsgsbase/64: Report FSBASE and GSBASE correctly in core dumps
- x86/switch_to/64: Rewrite FS/GS switching yet again to fix AMD CPUs
- x86/mm, mm/hwpoison: Clear PRESENT bit for kernel 1:1 mappings of poison
  pages
- ovl: fix false positive ESTALE on lookup
- fuse: allow server to run in different pid_ns
- idr: remove WARN_ON_ONCE() when trying to replace negative ID
- libnvdimm, btt: check memory allocation failure
- libnvdimm: fix integer overflow static analysis warning
- xfs: write unmount record for ro mounts
- xfs: toggle readonly state around xfs_log_mount_finish
- xfs: Add infrastructure needed for error propagation during buffer IO
  failure
- xfs: Properly retry failed inode items in case of error during buffer
  writeback
- xfs: fix recovery failure when log record header wraps log end
- xfs: always verify the log tail during recovery
- xfs: fix log recovery corruption error due to tail overwrite
- xfs: handle -EFSCORRUPTED during head/tail verification
- xfs: stop searching for free slots in an inode chunk when there are none
- xfs: evict all inodes involved with log redo item
- xfs: check for race with xfs_reclaim_inode() in xfs_ifree_cluster()
- xfs: open-code xfs_buf_item_dirty()
- xfs: remove unnecessary dirty bli format check for ordered bufs
- xfs: ordered buffer log items are never formatted
- xfs: refactor buffer logging into buffer dirtying helper
- xfs: don't log dirty ranges for ordered buffers
- xfs: skip bmbt block ino validation during owner change
- xfs: move bmbt owner change to last step of extent swap
- xfs: disallow marking previously dirty buffers as ordered
- xfs: relog dirty buffers during swapext bmbt owner change
- xfs: disable per-inode DAX 

[Kernel-packages] [Bug 1704350] Re: [Feature] Crystal Ridge - BTT - Rework error clearing

[Launchpad Bug Tracker]

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

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

  * linux: 4.13.0-12.13 -proposed tracker (LP: #1718980)

  * [Feature] SKX: Support crystall ridge / far / near memory indication in PEBS
(LP: #1591813)
- perf/x86: Move Nehalem PEBS code to flag
- perf/x86: Fix data source decoding for Skylake

  * Upgrade to 4.13.0-11.12 in artful amd64 VM breaks display on wayland
(LP: #1718679)
- [Config] CONFIG_DRM_VBOXVIDEO=n

  * ipmmu-vmsa driver breaks arm64 boots (LP: #1718734)
- [Config] Disable CONFIG_IPMMU_VMSA on arm64

  * Vlun resize request could fail with cxlflash driver (LP: #1713575)
- scsi: cxlflash: Fix vlun resize failure in the shrink path

  * multipath -ll is not showing the disks which are actually multipath
(LP: #1718397)
- fs: aio: fix the increment of aio-nr and counting against aio-max-nr

  * [Feature] Crystal Ridge - BTT - Rework error clearing (LP: #1704350)
- libnvdimm, btt: fix a missed NVDIMM_IO_ATOMIC case in the write path
- libnvdimm, btt: refactor map entry operations with macros
- libnvdimm, btt: ensure that flags were also unchanged during a map_read
- libnvdimm, btt: cache sector_size in arena_info
- libnvdimm: fix potential deadlock while clearing errors
- libnvdimm, btt: rework error clearing

  * [Feature] Crystal Ridge - have 4k DAX faults use a common zero page
(LP: #1704439)
- mm: add vm_insert_mixed_mkwrite()
- dax: relocate some dax functions
- dax: use common 4k zero page for dax mmap reads
- dax: remove DAX code from page_cache_tree_insert()
- dax: move all DAX radix tree defs to fs/dax.c

  * [bug] 17.10: CDP test fail on platform of Purley-2S/4S/Neoncity,BDW-
de/ep/ex, (LP: #1716843)
- SAUCE: (no-up) x86/intel_rdt: Fix cdp info directory files issue

  * [featue] GPIO support for Denverton (LP: #1591829)
- pinctrl: intel: Add Intel Denverton pin controller support

  * ETPS/2 Elantech Touchpad inconsistently detected (Gigabyte P57W laptop)
(LP: #1594214)
- Input: i8042 - add Gigabyte P57 to the keyboard reset table

  * autopkgtest profile fails to build on armhf (LP: #1717920)
- [Packaging] autopkgtest -- disable d-i when dropping flavours

  * Artful update to v4.13.3 stable release (LP: #1718412)
- Revert "net: use lib/percpu_counter API for fragmentation mem accounting"
- Revert "net: fix percpu memory leaks"
- gianfar: Fix Tx flow control deactivation
- vhost_net: correctly check tx avail during rx busy polling
- ip6_gre: update mtu properly in ip6gre_err
- udp: drop head states only when all skb references are gone
- ipv6: fix memory leak with multiple tables during netns destruction
- ipv6: fix typo in fib6_net_exit()
- sctp: fix missing wake ups in some situations
- tcp: fix a request socket leak
- ip_tunnel: fix setting ttl and tos value in collect_md mode
- f2fs: let fill_super handle roll-forward errors
- f2fs: check hot_data for roll-forward recovery
- x86/fsgsbase/64: Fully initialize FS and GS state in start_thread_common
- x86/fsgsbase/64: Report FSBASE and GSBASE correctly in core dumps
- x86/switch_to/64: Rewrite FS/GS switching yet again to fix AMD CPUs
- x86/mm, mm/hwpoison: Clear PRESENT bit for kernel 1:1 mappings of poison
  pages
- ovl: fix false positive ESTALE on lookup
- fuse: allow server to run in different pid_ns
- idr: remove WARN_ON_ONCE() when trying to replace negative ID
- libnvdimm, btt: check memory allocation failure
- libnvdimm: fix integer overflow static analysis warning
- xfs: write unmount record for ro mounts
- xfs: toggle readonly state around xfs_log_mount_finish
- xfs: Add infrastructure needed for error propagation during buffer IO
  failure
- xfs: Properly retry failed inode items in case of error during buffer
  writeback
- xfs: fix recovery failure when log record header wraps log end
- xfs: always verify the log tail during recovery
- xfs: fix log recovery corruption error due to tail overwrite
- xfs: handle -EFSCORRUPTED during head/tail verification
- xfs: stop searching for free slots in an inode chunk when there are none
- xfs: evict all inodes involved with log redo item
- xfs: check for race with xfs_reclaim_inode() in xfs_ifree_cluster()
- xfs: open-code xfs_buf_item_dirty()
- xfs: remove unnecessary dirty bli format check for ordered bufs
- xfs: ordered buffer log items are never formatted
- xfs: refactor buffer logging into buffer dirtying helper
- xfs: don't log dirty ranges for ordered buffers
- xfs: skip bmbt block ino validation during owner change
- xfs: move bmbt owner change to last step of extent swap
- xfs: disallow marking previously dirty buffers as ordered
- xfs: relog dirty buffers during swapext bmbt owner change
- xfs: disable per-inode DAX 

[Kernel-packages] [Bug 1704439] Re: [Feature] Crystal Ridge - have 4k DAX faults use a common zero page

[Launchpad Bug Tracker]

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

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

  * linux: 4.13.0-12.13 -proposed tracker (LP: #1718980)

  * [Feature] SKX: Support crystall ridge / far / near memory indication in PEBS
(LP: #1591813)
- perf/x86: Move Nehalem PEBS code to flag
- perf/x86: Fix data source decoding for Skylake

  * Upgrade to 4.13.0-11.12 in artful amd64 VM breaks display on wayland
(LP: #1718679)
- [Config] CONFIG_DRM_VBOXVIDEO=n

  * ipmmu-vmsa driver breaks arm64 boots (LP: #1718734)
- [Config] Disable CONFIG_IPMMU_VMSA on arm64

  * Vlun resize request could fail with cxlflash driver (LP: #1713575)
- scsi: cxlflash: Fix vlun resize failure in the shrink path

  * multipath -ll is not showing the disks which are actually multipath
(LP: #1718397)
- fs: aio: fix the increment of aio-nr and counting against aio-max-nr

  * [Feature] Crystal Ridge - BTT - Rework error clearing (LP: #1704350)
- libnvdimm, btt: fix a missed NVDIMM_IO_ATOMIC case in the write path
- libnvdimm, btt: refactor map entry operations with macros
- libnvdimm, btt: ensure that flags were also unchanged during a map_read
- libnvdimm, btt: cache sector_size in arena_info
- libnvdimm: fix potential deadlock while clearing errors
- libnvdimm, btt: rework error clearing

  * [Feature] Crystal Ridge - have 4k DAX faults use a common zero page
(LP: #1704439)
- mm: add vm_insert_mixed_mkwrite()
- dax: relocate some dax functions
- dax: use common 4k zero page for dax mmap reads
- dax: remove DAX code from page_cache_tree_insert()
- dax: move all DAX radix tree defs to fs/dax.c

  * [bug] 17.10: CDP test fail on platform of Purley-2S/4S/Neoncity,BDW-
de/ep/ex, (LP: #1716843)
- SAUCE: (no-up) x86/intel_rdt: Fix cdp info directory files issue

  * [featue] GPIO support for Denverton (LP: #1591829)
- pinctrl: intel: Add Intel Denverton pin controller support

  * ETPS/2 Elantech Touchpad inconsistently detected (Gigabyte P57W laptop)
(LP: #1594214)
- Input: i8042 - add Gigabyte P57 to the keyboard reset table

  * autopkgtest profile fails to build on armhf (LP: #1717920)
- [Packaging] autopkgtest -- disable d-i when dropping flavours

  * Artful update to v4.13.3 stable release (LP: #1718412)
- Revert "net: use lib/percpu_counter API for fragmentation mem accounting"
- Revert "net: fix percpu memory leaks"
- gianfar: Fix Tx flow control deactivation
- vhost_net: correctly check tx avail during rx busy polling
- ip6_gre: update mtu properly in ip6gre_err
- udp: drop head states only when all skb references are gone
- ipv6: fix memory leak with multiple tables during netns destruction
- ipv6: fix typo in fib6_net_exit()
- sctp: fix missing wake ups in some situations
- tcp: fix a request socket leak
- ip_tunnel: fix setting ttl and tos value in collect_md mode
- f2fs: let fill_super handle roll-forward errors
- f2fs: check hot_data for roll-forward recovery
- x86/fsgsbase/64: Fully initialize FS and GS state in start_thread_common
- x86/fsgsbase/64: Report FSBASE and GSBASE correctly in core dumps
- x86/switch_to/64: Rewrite FS/GS switching yet again to fix AMD CPUs
- x86/mm, mm/hwpoison: Clear PRESENT bit for kernel 1:1 mappings of poison
  pages
- ovl: fix false positive ESTALE on lookup
- fuse: allow server to run in different pid_ns
- idr: remove WARN_ON_ONCE() when trying to replace negative ID
- libnvdimm, btt: check memory allocation failure
- libnvdimm: fix integer overflow static analysis warning
- xfs: write unmount record for ro mounts
- xfs: toggle readonly state around xfs_log_mount_finish
- xfs: Add infrastructure needed for error propagation during buffer IO
  failure
- xfs: Properly retry failed inode items in case of error during buffer
  writeback
- xfs: fix recovery failure when log record header wraps log end
- xfs: always verify the log tail during recovery
- xfs: fix log recovery corruption error due to tail overwrite
- xfs: handle -EFSCORRUPTED during head/tail verification
- xfs: stop searching for free slots in an inode chunk when there are none
- xfs: evict all inodes involved with log redo item
- xfs: check for race with xfs_reclaim_inode() in xfs_ifree_cluster()
- xfs: open-code xfs_buf_item_dirty()
- xfs: remove unnecessary dirty bli format check for ordered bufs
- xfs: ordered buffer log items are never formatted
- xfs: refactor buffer logging into buffer dirtying helper
- xfs: don't log dirty ranges for ordered buffers
- xfs: skip bmbt block ino validation during owner change
- xfs: move bmbt owner change to last step of extent swap
- xfs: disallow marking previously dirty buffers as ordered
- xfs: relog dirty buffers during swapext bmbt owner change
- xfs: disable per-inode DAX 

[Kernel-packages] [Bug 1717430] Re: [Bug] Thunderbolt-patches: Related to the way the key for secure connection is handled

[Launchpad Bug Tracker]

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

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

  * linux: 4.13.0-12.13 -proposed tracker (LP: #1718980)

  * [Feature] SKX: Support crystall ridge / far / near memory indication in PEBS
(LP: #1591813)
- perf/x86: Move Nehalem PEBS code to flag
- perf/x86: Fix data source decoding for Skylake

  * Upgrade to 4.13.0-11.12 in artful amd64 VM breaks display on wayland
(LP: #1718679)
- [Config] CONFIG_DRM_VBOXVIDEO=n

  * ipmmu-vmsa driver breaks arm64 boots (LP: #1718734)
- [Config] Disable CONFIG_IPMMU_VMSA on arm64

  * Vlun resize request could fail with cxlflash driver (LP: #1713575)
- scsi: cxlflash: Fix vlun resize failure in the shrink path

  * multipath -ll is not showing the disks which are actually multipath
(LP: #1718397)
- fs: aio: fix the increment of aio-nr and counting against aio-max-nr

  * [Feature] Crystal Ridge - BTT - Rework error clearing (LP: #1704350)
- libnvdimm, btt: fix a missed NVDIMM_IO_ATOMIC case in the write path
- libnvdimm, btt: refactor map entry operations with macros
- libnvdimm, btt: ensure that flags were also unchanged during a map_read
- libnvdimm, btt: cache sector_size in arena_info
- libnvdimm: fix potential deadlock while clearing errors
- libnvdimm, btt: rework error clearing

  * [Feature] Crystal Ridge - have 4k DAX faults use a common zero page
(LP: #1704439)
- mm: add vm_insert_mixed_mkwrite()
- dax: relocate some dax functions
- dax: use common 4k zero page for dax mmap reads
- dax: remove DAX code from page_cache_tree_insert()
- dax: move all DAX radix tree defs to fs/dax.c

  * [bug] 17.10: CDP test fail on platform of Purley-2S/4S/Neoncity,BDW-
de/ep/ex, (LP: #1716843)
- SAUCE: (no-up) x86/intel_rdt: Fix cdp info directory files issue

  * [featue] GPIO support for Denverton (LP: #1591829)
- pinctrl: intel: Add Intel Denverton pin controller support

  * ETPS/2 Elantech Touchpad inconsistently detected (Gigabyte P57W laptop)
(LP: #1594214)
- Input: i8042 - add Gigabyte P57 to the keyboard reset table

  * autopkgtest profile fails to build on armhf (LP: #1717920)
- [Packaging] autopkgtest -- disable d-i when dropping flavours

  * Artful update to v4.13.3 stable release (LP: #1718412)
- Revert "net: use lib/percpu_counter API for fragmentation mem accounting"
- Revert "net: fix percpu memory leaks"
- gianfar: Fix Tx flow control deactivation
- vhost_net: correctly check tx avail during rx busy polling
- ip6_gre: update mtu properly in ip6gre_err
- udp: drop head states only when all skb references are gone
- ipv6: fix memory leak with multiple tables during netns destruction
- ipv6: fix typo in fib6_net_exit()
- sctp: fix missing wake ups in some situations
- tcp: fix a request socket leak
- ip_tunnel: fix setting ttl and tos value in collect_md mode
- f2fs: let fill_super handle roll-forward errors
- f2fs: check hot_data for roll-forward recovery
- x86/fsgsbase/64: Fully initialize FS and GS state in start_thread_common
- x86/fsgsbase/64: Report FSBASE and GSBASE correctly in core dumps
- x86/switch_to/64: Rewrite FS/GS switching yet again to fix AMD CPUs
- x86/mm, mm/hwpoison: Clear PRESENT bit for kernel 1:1 mappings of poison
  pages
- ovl: fix false positive ESTALE on lookup
- fuse: allow server to run in different pid_ns
- idr: remove WARN_ON_ONCE() when trying to replace negative ID
- libnvdimm, btt: check memory allocation failure
- libnvdimm: fix integer overflow static analysis warning
- xfs: write unmount record for ro mounts
- xfs: toggle readonly state around xfs_log_mount_finish
- xfs: Add infrastructure needed for error propagation during buffer IO
  failure
- xfs: Properly retry failed inode items in case of error during buffer
  writeback
- xfs: fix recovery failure when log record header wraps log end
- xfs: always verify the log tail during recovery
- xfs: fix log recovery corruption error due to tail overwrite
- xfs: handle -EFSCORRUPTED during head/tail verification
- xfs: stop searching for free slots in an inode chunk when there are none
- xfs: evict all inodes involved with log redo item
- xfs: check for race with xfs_reclaim_inode() in xfs_ifree_cluster()
- xfs: open-code xfs_buf_item_dirty()
- xfs: remove unnecessary dirty bli format check for ordered bufs
- xfs: ordered buffer log items are never formatted
- xfs: refactor buffer logging into buffer dirtying helper
- xfs: don't log dirty ranges for ordered buffers
- xfs: skip bmbt block ino validation during owner change
- xfs: move bmbt owner change to last step of extent swap
- xfs: disallow marking previously dirty buffers as ordered
- xfs: relog dirty buffers during swapext bmbt owner change
- xfs: disable per-inode DAX 

[Kernel-packages] [Bug 1717920] Re: autopkgtest profile fails to build on armhf

[Launchpad Bug Tracker]

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

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

  * linux: 4.13.0-12.13 -proposed tracker (LP: #1718980)

  * [Feature] SKX: Support crystall ridge / far / near memory indication in PEBS
(LP: #1591813)
- perf/x86: Move Nehalem PEBS code to flag
- perf/x86: Fix data source decoding for Skylake

  * Upgrade to 4.13.0-11.12 in artful amd64 VM breaks display on wayland
(LP: #1718679)
- [Config] CONFIG_DRM_VBOXVIDEO=n

  * ipmmu-vmsa driver breaks arm64 boots (LP: #1718734)
- [Config] Disable CONFIG_IPMMU_VMSA on arm64

  * Vlun resize request could fail with cxlflash driver (LP: #1713575)
- scsi: cxlflash: Fix vlun resize failure in the shrink path

  * multipath -ll is not showing the disks which are actually multipath
(LP: #1718397)
- fs: aio: fix the increment of aio-nr and counting against aio-max-nr

  * [Feature] Crystal Ridge - BTT - Rework error clearing (LP: #1704350)
- libnvdimm, btt: fix a missed NVDIMM_IO_ATOMIC case in the write path
- libnvdimm, btt: refactor map entry operations with macros
- libnvdimm, btt: ensure that flags were also unchanged during a map_read
- libnvdimm, btt: cache sector_size in arena_info
- libnvdimm: fix potential deadlock while clearing errors
- libnvdimm, btt: rework error clearing

  * [Feature] Crystal Ridge - have 4k DAX faults use a common zero page
(LP: #1704439)
- mm: add vm_insert_mixed_mkwrite()
- dax: relocate some dax functions
- dax: use common 4k zero page for dax mmap reads
- dax: remove DAX code from page_cache_tree_insert()
- dax: move all DAX radix tree defs to fs/dax.c

  * [bug] 17.10: CDP test fail on platform of Purley-2S/4S/Neoncity,BDW-
de/ep/ex, (LP: #1716843)
- SAUCE: (no-up) x86/intel_rdt: Fix cdp info directory files issue

  * [featue] GPIO support for Denverton (LP: #1591829)
- pinctrl: intel: Add Intel Denverton pin controller support

  * ETPS/2 Elantech Touchpad inconsistently detected (Gigabyte P57W laptop)
(LP: #1594214)
- Input: i8042 - add Gigabyte P57 to the keyboard reset table

  * autopkgtest profile fails to build on armhf (LP: #1717920)
- [Packaging] autopkgtest -- disable d-i when dropping flavours

  * Artful update to v4.13.3 stable release (LP: #1718412)
- Revert "net: use lib/percpu_counter API for fragmentation mem accounting"
- Revert "net: fix percpu memory leaks"
- gianfar: Fix Tx flow control deactivation
- vhost_net: correctly check tx avail during rx busy polling
- ip6_gre: update mtu properly in ip6gre_err
- udp: drop head states only when all skb references are gone
- ipv6: fix memory leak with multiple tables during netns destruction
- ipv6: fix typo in fib6_net_exit()
- sctp: fix missing wake ups in some situations
- tcp: fix a request socket leak
- ip_tunnel: fix setting ttl and tos value in collect_md mode
- f2fs: let fill_super handle roll-forward errors
- f2fs: check hot_data for roll-forward recovery
- x86/fsgsbase/64: Fully initialize FS and GS state in start_thread_common
- x86/fsgsbase/64: Report FSBASE and GSBASE correctly in core dumps
- x86/switch_to/64: Rewrite FS/GS switching yet again to fix AMD CPUs
- x86/mm, mm/hwpoison: Clear PRESENT bit for kernel 1:1 mappings of poison
  pages
- ovl: fix false positive ESTALE on lookup
- fuse: allow server to run in different pid_ns
- idr: remove WARN_ON_ONCE() when trying to replace negative ID
- libnvdimm, btt: check memory allocation failure
- libnvdimm: fix integer overflow static analysis warning
- xfs: write unmount record for ro mounts
- xfs: toggle readonly state around xfs_log_mount_finish
- xfs: Add infrastructure needed for error propagation during buffer IO
  failure
- xfs: Properly retry failed inode items in case of error during buffer
  writeback
- xfs: fix recovery failure when log record header wraps log end
- xfs: always verify the log tail during recovery
- xfs: fix log recovery corruption error due to tail overwrite
- xfs: handle -EFSCORRUPTED during head/tail verification
- xfs: stop searching for free slots in an inode chunk when there are none
- xfs: evict all inodes involved with log redo item
- xfs: check for race with xfs_reclaim_inode() in xfs_ifree_cluster()
- xfs: open-code xfs_buf_item_dirty()
- xfs: remove unnecessary dirty bli format check for ordered bufs
- xfs: ordered buffer log items are never formatted
- xfs: refactor buffer logging into buffer dirtying helper
- xfs: don't log dirty ranges for ordered buffers
- xfs: skip bmbt block ino validation during owner change
- xfs: move bmbt owner change to last step of extent swap
- xfs: disallow marking previously dirty buffers as ordered
- xfs: relog dirty buffers during swapext bmbt owner change
- xfs: disable per-inode DAX 

[Kernel-packages] [Bug 1718734] Re: ipmmu-vmsa driver breaks arm64 boots

[Launchpad Bug Tracker]

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

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

  * linux: 4.13.0-12.13 -proposed tracker (LP: #1718980)

  * [Feature] SKX: Support crystall ridge / far / near memory indication in PEBS
(LP: #1591813)
- perf/x86: Move Nehalem PEBS code to flag
- perf/x86: Fix data source decoding for Skylake

  * Upgrade to 4.13.0-11.12 in artful amd64 VM breaks display on wayland
(LP: #1718679)
- [Config] CONFIG_DRM_VBOXVIDEO=n

  * ipmmu-vmsa driver breaks arm64 boots (LP: #1718734)
- [Config] Disable CONFIG_IPMMU_VMSA on arm64

  * Vlun resize request could fail with cxlflash driver (LP: #1713575)
- scsi: cxlflash: Fix vlun resize failure in the shrink path

  * multipath -ll is not showing the disks which are actually multipath
(LP: #1718397)
- fs: aio: fix the increment of aio-nr and counting against aio-max-nr

  * [Feature] Crystal Ridge - BTT - Rework error clearing (LP: #1704350)
- libnvdimm, btt: fix a missed NVDIMM_IO_ATOMIC case in the write path
- libnvdimm, btt: refactor map entry operations with macros
- libnvdimm, btt: ensure that flags were also unchanged during a map_read
- libnvdimm, btt: cache sector_size in arena_info
- libnvdimm: fix potential deadlock while clearing errors
- libnvdimm, btt: rework error clearing

  * [Feature] Crystal Ridge - have 4k DAX faults use a common zero page
(LP: #1704439)
- mm: add vm_insert_mixed_mkwrite()
- dax: relocate some dax functions
- dax: use common 4k zero page for dax mmap reads
- dax: remove DAX code from page_cache_tree_insert()
- dax: move all DAX radix tree defs to fs/dax.c

  * [bug] 17.10: CDP test fail on platform of Purley-2S/4S/Neoncity,BDW-
de/ep/ex, (LP: #1716843)
- SAUCE: (no-up) x86/intel_rdt: Fix cdp info directory files issue

  * [featue] GPIO support for Denverton (LP: #1591829)
- pinctrl: intel: Add Intel Denverton pin controller support

  * ETPS/2 Elantech Touchpad inconsistently detected (Gigabyte P57W laptop)
(LP: #1594214)
- Input: i8042 - add Gigabyte P57 to the keyboard reset table

  * autopkgtest profile fails to build on armhf (LP: #1717920)
- [Packaging] autopkgtest -- disable d-i when dropping flavours

  * Artful update to v4.13.3 stable release (LP: #1718412)
- Revert "net: use lib/percpu_counter API for fragmentation mem accounting"
- Revert "net: fix percpu memory leaks"
- gianfar: Fix Tx flow control deactivation
- vhost_net: correctly check tx avail during rx busy polling
- ip6_gre: update mtu properly in ip6gre_err
- udp: drop head states only when all skb references are gone
- ipv6: fix memory leak with multiple tables during netns destruction
- ipv6: fix typo in fib6_net_exit()
- sctp: fix missing wake ups in some situations
- tcp: fix a request socket leak
- ip_tunnel: fix setting ttl and tos value in collect_md mode
- f2fs: let fill_super handle roll-forward errors
- f2fs: check hot_data for roll-forward recovery
- x86/fsgsbase/64: Fully initialize FS and GS state in start_thread_common
- x86/fsgsbase/64: Report FSBASE and GSBASE correctly in core dumps
- x86/switch_to/64: Rewrite FS/GS switching yet again to fix AMD CPUs
- x86/mm, mm/hwpoison: Clear PRESENT bit for kernel 1:1 mappings of poison
  pages
- ovl: fix false positive ESTALE on lookup
- fuse: allow server to run in different pid_ns
- idr: remove WARN_ON_ONCE() when trying to replace negative ID
- libnvdimm, btt: check memory allocation failure
- libnvdimm: fix integer overflow static analysis warning
- xfs: write unmount record for ro mounts
- xfs: toggle readonly state around xfs_log_mount_finish
- xfs: Add infrastructure needed for error propagation during buffer IO
  failure
- xfs: Properly retry failed inode items in case of error during buffer
  writeback
- xfs: fix recovery failure when log record header wraps log end
- xfs: always verify the log tail during recovery
- xfs: fix log recovery corruption error due to tail overwrite
- xfs: handle -EFSCORRUPTED during head/tail verification
- xfs: stop searching for free slots in an inode chunk when there are none
- xfs: evict all inodes involved with log redo item
- xfs: check for race with xfs_reclaim_inode() in xfs_ifree_cluster()
- xfs: open-code xfs_buf_item_dirty()
- xfs: remove unnecessary dirty bli format check for ordered bufs
- xfs: ordered buffer log items are never formatted
- xfs: refactor buffer logging into buffer dirtying helper
- xfs: don't log dirty ranges for ordered buffers
- xfs: skip bmbt block ino validation during owner change
- xfs: move bmbt owner change to last step of extent swap
- xfs: disallow marking previously dirty buffers as ordered
- xfs: relog dirty buffers during swapext bmbt owner change
- xfs: disable per-inode DAX 

[Kernel-packages] [Bug 1717431] Re: [Bug] Thunderbolt-patches: Fixes the issue regarding the order of ACPI calls w.r.t. PCI enumeration

[Launchpad Bug Tracker]

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

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

  * linux: 4.13.0-12.13 -proposed tracker (LP: #1718980)

  * [Feature] SKX: Support crystall ridge / far / near memory indication in PEBS
(LP: #1591813)
- perf/x86: Move Nehalem PEBS code to flag
- perf/x86: Fix data source decoding for Skylake

  * Upgrade to 4.13.0-11.12 in artful amd64 VM breaks display on wayland
(LP: #1718679)
- [Config] CONFIG_DRM_VBOXVIDEO=n

  * ipmmu-vmsa driver breaks arm64 boots (LP: #1718734)
- [Config] Disable CONFIG_IPMMU_VMSA on arm64

  * Vlun resize request could fail with cxlflash driver (LP: #1713575)
- scsi: cxlflash: Fix vlun resize failure in the shrink path

  * multipath -ll is not showing the disks which are actually multipath
(LP: #1718397)
- fs: aio: fix the increment of aio-nr and counting against aio-max-nr

  * [Feature] Crystal Ridge - BTT - Rework error clearing (LP: #1704350)
- libnvdimm, btt: fix a missed NVDIMM_IO_ATOMIC case in the write path
- libnvdimm, btt: refactor map entry operations with macros
- libnvdimm, btt: ensure that flags were also unchanged during a map_read
- libnvdimm, btt: cache sector_size in arena_info
- libnvdimm: fix potential deadlock while clearing errors
- libnvdimm, btt: rework error clearing

  * [Feature] Crystal Ridge - have 4k DAX faults use a common zero page
(LP: #1704439)
- mm: add vm_insert_mixed_mkwrite()
- dax: relocate some dax functions
- dax: use common 4k zero page for dax mmap reads
- dax: remove DAX code from page_cache_tree_insert()
- dax: move all DAX radix tree defs to fs/dax.c

  * [bug] 17.10: CDP test fail on platform of Purley-2S/4S/Neoncity,BDW-
de/ep/ex, (LP: #1716843)
- SAUCE: (no-up) x86/intel_rdt: Fix cdp info directory files issue

  * [featue] GPIO support for Denverton (LP: #1591829)
- pinctrl: intel: Add Intel Denverton pin controller support

  * ETPS/2 Elantech Touchpad inconsistently detected (Gigabyte P57W laptop)
(LP: #1594214)
- Input: i8042 - add Gigabyte P57 to the keyboard reset table

  * autopkgtest profile fails to build on armhf (LP: #1717920)
- [Packaging] autopkgtest -- disable d-i when dropping flavours

  * Artful update to v4.13.3 stable release (LP: #1718412)
- Revert "net: use lib/percpu_counter API for fragmentation mem accounting"
- Revert "net: fix percpu memory leaks"
- gianfar: Fix Tx flow control deactivation
- vhost_net: correctly check tx avail during rx busy polling
- ip6_gre: update mtu properly in ip6gre_err
- udp: drop head states only when all skb references are gone
- ipv6: fix memory leak with multiple tables during netns destruction
- ipv6: fix typo in fib6_net_exit()
- sctp: fix missing wake ups in some situations
- tcp: fix a request socket leak
- ip_tunnel: fix setting ttl and tos value in collect_md mode
- f2fs: let fill_super handle roll-forward errors
- f2fs: check hot_data for roll-forward recovery
- x86/fsgsbase/64: Fully initialize FS and GS state in start_thread_common
- x86/fsgsbase/64: Report FSBASE and GSBASE correctly in core dumps
- x86/switch_to/64: Rewrite FS/GS switching yet again to fix AMD CPUs
- x86/mm, mm/hwpoison: Clear PRESENT bit for kernel 1:1 mappings of poison
  pages
- ovl: fix false positive ESTALE on lookup
- fuse: allow server to run in different pid_ns
- idr: remove WARN_ON_ONCE() when trying to replace negative ID
- libnvdimm, btt: check memory allocation failure
- libnvdimm: fix integer overflow static analysis warning
- xfs: write unmount record for ro mounts
- xfs: toggle readonly state around xfs_log_mount_finish
- xfs: Add infrastructure needed for error propagation during buffer IO
  failure
- xfs: Properly retry failed inode items in case of error during buffer
  writeback
- xfs: fix recovery failure when log record header wraps log end
- xfs: always verify the log tail during recovery
- xfs: fix log recovery corruption error due to tail overwrite
- xfs: handle -EFSCORRUPTED during head/tail verification
- xfs: stop searching for free slots in an inode chunk when there are none
- xfs: evict all inodes involved with log redo item
- xfs: check for race with xfs_reclaim_inode() in xfs_ifree_cluster()
- xfs: open-code xfs_buf_item_dirty()
- xfs: remove unnecessary dirty bli format check for ordered bufs
- xfs: ordered buffer log items are never formatted
- xfs: refactor buffer logging into buffer dirtying helper
- xfs: don't log dirty ranges for ordered buffers
- xfs: skip bmbt block ino validation during owner change
- xfs: move bmbt owner change to last step of extent swap
- xfs: disallow marking previously dirty buffers as ordered
- xfs: relog dirty buffers during swapext bmbt owner change
- xfs: disable per-inode DAX 

[Kernel-packages] [Bug 1718679] Re: Upgrade to 4.13.0-11.12 in artful amd64 VM breaks display on wayland

[Launchpad Bug Tracker]

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

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

  * linux: 4.13.0-12.13 -proposed tracker (LP: #1718980)

  * [Feature] SKX: Support crystall ridge / far / near memory indication in PEBS
(LP: #1591813)
- perf/x86: Move Nehalem PEBS code to flag
- perf/x86: Fix data source decoding for Skylake

  * Upgrade to 4.13.0-11.12 in artful amd64 VM breaks display on wayland
(LP: #1718679)
- [Config] CONFIG_DRM_VBOXVIDEO=n

  * ipmmu-vmsa driver breaks arm64 boots (LP: #1718734)
- [Config] Disable CONFIG_IPMMU_VMSA on arm64

  * Vlun resize request could fail with cxlflash driver (LP: #1713575)
- scsi: cxlflash: Fix vlun resize failure in the shrink path

  * multipath -ll is not showing the disks which are actually multipath
(LP: #1718397)
- fs: aio: fix the increment of aio-nr and counting against aio-max-nr

  * [Feature] Crystal Ridge - BTT - Rework error clearing (LP: #1704350)
- libnvdimm, btt: fix a missed NVDIMM_IO_ATOMIC case in the write path
- libnvdimm, btt: refactor map entry operations with macros
- libnvdimm, btt: ensure that flags were also unchanged during a map_read
- libnvdimm, btt: cache sector_size in arena_info
- libnvdimm: fix potential deadlock while clearing errors
- libnvdimm, btt: rework error clearing

  * [Feature] Crystal Ridge - have 4k DAX faults use a common zero page
(LP: #1704439)
- mm: add vm_insert_mixed_mkwrite()
- dax: relocate some dax functions
- dax: use common 4k zero page for dax mmap reads
- dax: remove DAX code from page_cache_tree_insert()
- dax: move all DAX radix tree defs to fs/dax.c

  * [bug] 17.10: CDP test fail on platform of Purley-2S/4S/Neoncity,BDW-
de/ep/ex, (LP: #1716843)
- SAUCE: (no-up) x86/intel_rdt: Fix cdp info directory files issue

  * [featue] GPIO support for Denverton (LP: #1591829)
- pinctrl: intel: Add Intel Denverton pin controller support

  * ETPS/2 Elantech Touchpad inconsistently detected (Gigabyte P57W laptop)
(LP: #1594214)
- Input: i8042 - add Gigabyte P57 to the keyboard reset table

  * autopkgtest profile fails to build on armhf (LP: #1717920)
- [Packaging] autopkgtest -- disable d-i when dropping flavours

  * Artful update to v4.13.3 stable release (LP: #1718412)
- Revert "net: use lib/percpu_counter API for fragmentation mem accounting"
- Revert "net: fix percpu memory leaks"
- gianfar: Fix Tx flow control deactivation
- vhost_net: correctly check tx avail during rx busy polling
- ip6_gre: update mtu properly in ip6gre_err
- udp: drop head states only when all skb references are gone
- ipv6: fix memory leak with multiple tables during netns destruction
- ipv6: fix typo in fib6_net_exit()
- sctp: fix missing wake ups in some situations
- tcp: fix a request socket leak
- ip_tunnel: fix setting ttl and tos value in collect_md mode
- f2fs: let fill_super handle roll-forward errors
- f2fs: check hot_data for roll-forward recovery
- x86/fsgsbase/64: Fully initialize FS and GS state in start_thread_common
- x86/fsgsbase/64: Report FSBASE and GSBASE correctly in core dumps
- x86/switch_to/64: Rewrite FS/GS switching yet again to fix AMD CPUs
- x86/mm, mm/hwpoison: Clear PRESENT bit for kernel 1:1 mappings of poison
  pages
- ovl: fix false positive ESTALE on lookup
- fuse: allow server to run in different pid_ns
- idr: remove WARN_ON_ONCE() when trying to replace negative ID
- libnvdimm, btt: check memory allocation failure
- libnvdimm: fix integer overflow static analysis warning
- xfs: write unmount record for ro mounts
- xfs: toggle readonly state around xfs_log_mount_finish
- xfs: Add infrastructure needed for error propagation during buffer IO
  failure
- xfs: Properly retry failed inode items in case of error during buffer
  writeback
- xfs: fix recovery failure when log record header wraps log end
- xfs: always verify the log tail during recovery
- xfs: fix log recovery corruption error due to tail overwrite
- xfs: handle -EFSCORRUPTED during head/tail verification
- xfs: stop searching for free slots in an inode chunk when there are none
- xfs: evict all inodes involved with log redo item
- xfs: check for race with xfs_reclaim_inode() in xfs_ifree_cluster()
- xfs: open-code xfs_buf_item_dirty()
- xfs: remove unnecessary dirty bli format check for ordered bufs
- xfs: ordered buffer log items are never formatted
- xfs: refactor buffer logging into buffer dirtying helper
- xfs: don't log dirty ranges for ordered buffers
- xfs: skip bmbt block ino validation during owner change
- xfs: move bmbt owner change to last step of extent swap
- xfs: disallow marking previously dirty buffers as ordered
- xfs: relog dirty buffers during swapext bmbt owner change
- xfs: disable per-inode DAX 

[Kernel-packages] [Bug 1718397] Re: multipath -ll is not showing the disks which are actually multipath

[Launchpad Bug Tracker]

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

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

  * linux: 4.13.0-12.13 -proposed tracker (LP: #1718980)

  * [Feature] SKX: Support crystall ridge / far / near memory indication in PEBS
(LP: #1591813)
- perf/x86: Move Nehalem PEBS code to flag
- perf/x86: Fix data source decoding for Skylake

  * Upgrade to 4.13.0-11.12 in artful amd64 VM breaks display on wayland
(LP: #1718679)
- [Config] CONFIG_DRM_VBOXVIDEO=n

  * ipmmu-vmsa driver breaks arm64 boots (LP: #1718734)
- [Config] Disable CONFIG_IPMMU_VMSA on arm64

  * Vlun resize request could fail with cxlflash driver (LP: #1713575)
- scsi: cxlflash: Fix vlun resize failure in the shrink path

  * multipath -ll is not showing the disks which are actually multipath
(LP: #1718397)
- fs: aio: fix the increment of aio-nr and counting against aio-max-nr

  * [Feature] Crystal Ridge - BTT - Rework error clearing (LP: #1704350)
- libnvdimm, btt: fix a missed NVDIMM_IO_ATOMIC case in the write path
- libnvdimm, btt: refactor map entry operations with macros
- libnvdimm, btt: ensure that flags were also unchanged during a map_read
- libnvdimm, btt: cache sector_size in arena_info
- libnvdimm: fix potential deadlock while clearing errors
- libnvdimm, btt: rework error clearing

  * [Feature] Crystal Ridge - have 4k DAX faults use a common zero page
(LP: #1704439)
- mm: add vm_insert_mixed_mkwrite()
- dax: relocate some dax functions
- dax: use common 4k zero page for dax mmap reads
- dax: remove DAX code from page_cache_tree_insert()
- dax: move all DAX radix tree defs to fs/dax.c

  * [bug] 17.10: CDP test fail on platform of Purley-2S/4S/Neoncity,BDW-
de/ep/ex, (LP: #1716843)
- SAUCE: (no-up) x86/intel_rdt: Fix cdp info directory files issue

  * [featue] GPIO support for Denverton (LP: #1591829)
- pinctrl: intel: Add Intel Denverton pin controller support

  * ETPS/2 Elantech Touchpad inconsistently detected (Gigabyte P57W laptop)
(LP: #1594214)
- Input: i8042 - add Gigabyte P57 to the keyboard reset table

  * autopkgtest profile fails to build on armhf (LP: #1717920)
- [Packaging] autopkgtest -- disable d-i when dropping flavours

  * Artful update to v4.13.3 stable release (LP: #1718412)
- Revert "net: use lib/percpu_counter API for fragmentation mem accounting"
- Revert "net: fix percpu memory leaks"
- gianfar: Fix Tx flow control deactivation
- vhost_net: correctly check tx avail during rx busy polling
- ip6_gre: update mtu properly in ip6gre_err
- udp: drop head states only when all skb references are gone
- ipv6: fix memory leak with multiple tables during netns destruction
- ipv6: fix typo in fib6_net_exit()
- sctp: fix missing wake ups in some situations
- tcp: fix a request socket leak
- ip_tunnel: fix setting ttl and tos value in collect_md mode
- f2fs: let fill_super handle roll-forward errors
- f2fs: check hot_data for roll-forward recovery
- x86/fsgsbase/64: Fully initialize FS and GS state in start_thread_common
- x86/fsgsbase/64: Report FSBASE and GSBASE correctly in core dumps
- x86/switch_to/64: Rewrite FS/GS switching yet again to fix AMD CPUs
- x86/mm, mm/hwpoison: Clear PRESENT bit for kernel 1:1 mappings of poison
  pages
- ovl: fix false positive ESTALE on lookup
- fuse: allow server to run in different pid_ns
- idr: remove WARN_ON_ONCE() when trying to replace negative ID
- libnvdimm, btt: check memory allocation failure
- libnvdimm: fix integer overflow static analysis warning
- xfs: write unmount record for ro mounts
- xfs: toggle readonly state around xfs_log_mount_finish
- xfs: Add infrastructure needed for error propagation during buffer IO
  failure
- xfs: Properly retry failed inode items in case of error during buffer
  writeback
- xfs: fix recovery failure when log record header wraps log end
- xfs: always verify the log tail during recovery
- xfs: fix log recovery corruption error due to tail overwrite
- xfs: handle -EFSCORRUPTED during head/tail verification
- xfs: stop searching for free slots in an inode chunk when there are none
- xfs: evict all inodes involved with log redo item
- xfs: check for race with xfs_reclaim_inode() in xfs_ifree_cluster()
- xfs: open-code xfs_buf_item_dirty()
- xfs: remove unnecessary dirty bli format check for ordered bufs
- xfs: ordered buffer log items are never formatted
- xfs: refactor buffer logging into buffer dirtying helper
- xfs: don't log dirty ranges for ordered buffers
- xfs: skip bmbt block ino validation during owner change
- xfs: move bmbt owner change to last step of extent swap
- xfs: disallow marking previously dirty buffers as ordered
- xfs: relog dirty buffers during swapext bmbt owner change
- xfs: disable per-inode DAX 

[Kernel-packages] [Bug 1717549] Re: Artful update to v4.13.2 stable release

[Launchpad Bug Tracker]

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

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

  * linux: 4.13.0-12.13 -proposed tracker (LP: #1718980)

  * [Feature] SKX: Support crystall ridge / far / near memory indication in PEBS
(LP: #1591813)
- perf/x86: Move Nehalem PEBS code to flag
- perf/x86: Fix data source decoding for Skylake

  * Upgrade to 4.13.0-11.12 in artful amd64 VM breaks display on wayland
(LP: #1718679)
- [Config] CONFIG_DRM_VBOXVIDEO=n

  * ipmmu-vmsa driver breaks arm64 boots (LP: #1718734)
- [Config] Disable CONFIG_IPMMU_VMSA on arm64

  * Vlun resize request could fail with cxlflash driver (LP: #1713575)
- scsi: cxlflash: Fix vlun resize failure in the shrink path

  * multipath -ll is not showing the disks which are actually multipath
(LP: #1718397)
- fs: aio: fix the increment of aio-nr and counting against aio-max-nr

  * [Feature] Crystal Ridge - BTT - Rework error clearing (LP: #1704350)
- libnvdimm, btt: fix a missed NVDIMM_IO_ATOMIC case in the write path
- libnvdimm, btt: refactor map entry operations with macros
- libnvdimm, btt: ensure that flags were also unchanged during a map_read
- libnvdimm, btt: cache sector_size in arena_info
- libnvdimm: fix potential deadlock while clearing errors
- libnvdimm, btt: rework error clearing

  * [Feature] Crystal Ridge - have 4k DAX faults use a common zero page
(LP: #1704439)
- mm: add vm_insert_mixed_mkwrite()
- dax: relocate some dax functions
- dax: use common 4k zero page for dax mmap reads
- dax: remove DAX code from page_cache_tree_insert()
- dax: move all DAX radix tree defs to fs/dax.c

  * [bug] 17.10: CDP test fail on platform of Purley-2S/4S/Neoncity,BDW-
de/ep/ex, (LP: #1716843)
- SAUCE: (no-up) x86/intel_rdt: Fix cdp info directory files issue

  * [featue] GPIO support for Denverton (LP: #1591829)
- pinctrl: intel: Add Intel Denverton pin controller support

  * ETPS/2 Elantech Touchpad inconsistently detected (Gigabyte P57W laptop)
(LP: #1594214)
- Input: i8042 - add Gigabyte P57 to the keyboard reset table

  * autopkgtest profile fails to build on armhf (LP: #1717920)
- [Packaging] autopkgtest -- disable d-i when dropping flavours

  * Artful update to v4.13.3 stable release (LP: #1718412)
- Revert "net: use lib/percpu_counter API for fragmentation mem accounting"
- Revert "net: fix percpu memory leaks"
- gianfar: Fix Tx flow control deactivation
- vhost_net: correctly check tx avail during rx busy polling
- ip6_gre: update mtu properly in ip6gre_err
- udp: drop head states only when all skb references are gone
- ipv6: fix memory leak with multiple tables during netns destruction
- ipv6: fix typo in fib6_net_exit()
- sctp: fix missing wake ups in some situations
- tcp: fix a request socket leak
- ip_tunnel: fix setting ttl and tos value in collect_md mode
- f2fs: let fill_super handle roll-forward errors
- f2fs: check hot_data for roll-forward recovery
- x86/fsgsbase/64: Fully initialize FS and GS state in start_thread_common
- x86/fsgsbase/64: Report FSBASE and GSBASE correctly in core dumps
- x86/switch_to/64: Rewrite FS/GS switching yet again to fix AMD CPUs
- x86/mm, mm/hwpoison: Clear PRESENT bit for kernel 1:1 mappings of poison
  pages
- ovl: fix false positive ESTALE on lookup
- fuse: allow server to run in different pid_ns
- idr: remove WARN_ON_ONCE() when trying to replace negative ID
- libnvdimm, btt: check memory allocation failure
- libnvdimm: fix integer overflow static analysis warning
- xfs: write unmount record for ro mounts
- xfs: toggle readonly state around xfs_log_mount_finish
- xfs: Add infrastructure needed for error propagation during buffer IO
  failure
- xfs: Properly retry failed inode items in case of error during buffer
  writeback
- xfs: fix recovery failure when log record header wraps log end
- xfs: always verify the log tail during recovery
- xfs: fix log recovery corruption error due to tail overwrite
- xfs: handle -EFSCORRUPTED during head/tail verification
- xfs: stop searching for free slots in an inode chunk when there are none
- xfs: evict all inodes involved with log redo item
- xfs: check for race with xfs_reclaim_inode() in xfs_ifree_cluster()
- xfs: open-code xfs_buf_item_dirty()
- xfs: remove unnecessary dirty bli format check for ordered bufs
- xfs: ordered buffer log items are never formatted
- xfs: refactor buffer logging into buffer dirtying helper
- xfs: don't log dirty ranges for ordered buffers
- xfs: skip bmbt block ino validation during owner change
- xfs: move bmbt owner change to last step of extent swap
- xfs: disallow marking previously dirty buffers as ordered
- xfs: relog dirty buffers during swapext bmbt owner change
- xfs: disable per-inode DAX 

[Kernel-packages] [Bug 1718980] Re: linux: 4.13.0-12.13 -proposed tracker

[Launchpad Bug Tracker]

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

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

  * linux: 4.13.0-12.13 -proposed tracker (LP: #1718980)

  * [Feature] SKX: Support crystall ridge / far / near memory indication in PEBS
(LP: #1591813)
- perf/x86: Move Nehalem PEBS code to flag
- perf/x86: Fix data source decoding for Skylake

  * Upgrade to 4.13.0-11.12 in artful amd64 VM breaks display on wayland
(LP: #1718679)
- [Config] CONFIG_DRM_VBOXVIDEO=n

  * ipmmu-vmsa driver breaks arm64 boots (LP: #1718734)
- [Config] Disable CONFIG_IPMMU_VMSA on arm64

  * Vlun resize request could fail with cxlflash driver (LP: #1713575)
- scsi: cxlflash: Fix vlun resize failure in the shrink path

  * multipath -ll is not showing the disks which are actually multipath
(LP: #1718397)
- fs: aio: fix the increment of aio-nr and counting against aio-max-nr

  * [Feature] Crystal Ridge - BTT - Rework error clearing (LP: #1704350)
- libnvdimm, btt: fix a missed NVDIMM_IO_ATOMIC case in the write path
- libnvdimm, btt: refactor map entry operations with macros
- libnvdimm, btt: ensure that flags were also unchanged during a map_read
- libnvdimm, btt: cache sector_size in arena_info
- libnvdimm: fix potential deadlock while clearing errors
- libnvdimm, btt: rework error clearing

  * [Feature] Crystal Ridge - have 4k DAX faults use a common zero page
(LP: #1704439)
- mm: add vm_insert_mixed_mkwrite()
- dax: relocate some dax functions
- dax: use common 4k zero page for dax mmap reads
- dax: remove DAX code from page_cache_tree_insert()
- dax: move all DAX radix tree defs to fs/dax.c

  * [bug] 17.10: CDP test fail on platform of Purley-2S/4S/Neoncity,BDW-
de/ep/ex, (LP: #1716843)
- SAUCE: (no-up) x86/intel_rdt: Fix cdp info directory files issue

  * [featue] GPIO support for Denverton (LP: #1591829)
- pinctrl: intel: Add Intel Denverton pin controller support

  * ETPS/2 Elantech Touchpad inconsistently detected (Gigabyte P57W laptop)
(LP: #1594214)
- Input: i8042 - add Gigabyte P57 to the keyboard reset table

  * autopkgtest profile fails to build on armhf (LP: #1717920)
- [Packaging] autopkgtest -- disable d-i when dropping flavours

  * Artful update to v4.13.3 stable release (LP: #1718412)
- Revert "net: use lib/percpu_counter API for fragmentation mem accounting"
- Revert "net: fix percpu memory leaks"
- gianfar: Fix Tx flow control deactivation
- vhost_net: correctly check tx avail during rx busy polling
- ip6_gre: update mtu properly in ip6gre_err
- udp: drop head states only when all skb references are gone
- ipv6: fix memory leak with multiple tables during netns destruction
- ipv6: fix typo in fib6_net_exit()
- sctp: fix missing wake ups in some situations
- tcp: fix a request socket leak
- ip_tunnel: fix setting ttl and tos value in collect_md mode
- f2fs: let fill_super handle roll-forward errors
- f2fs: check hot_data for roll-forward recovery
- x86/fsgsbase/64: Fully initialize FS and GS state in start_thread_common
- x86/fsgsbase/64: Report FSBASE and GSBASE correctly in core dumps
- x86/switch_to/64: Rewrite FS/GS switching yet again to fix AMD CPUs
- x86/mm, mm/hwpoison: Clear PRESENT bit for kernel 1:1 mappings of poison
  pages
- ovl: fix false positive ESTALE on lookup
- fuse: allow server to run in different pid_ns
- idr: remove WARN_ON_ONCE() when trying to replace negative ID
- libnvdimm, btt: check memory allocation failure
- libnvdimm: fix integer overflow static analysis warning
- xfs: write unmount record for ro mounts
- xfs: toggle readonly state around xfs_log_mount_finish
- xfs: Add infrastructure needed for error propagation during buffer IO
  failure
- xfs: Properly retry failed inode items in case of error during buffer
  writeback
- xfs: fix recovery failure when log record header wraps log end
- xfs: always verify the log tail during recovery
- xfs: fix log recovery corruption error due to tail overwrite
- xfs: handle -EFSCORRUPTED during head/tail verification
- xfs: stop searching for free slots in an inode chunk when there are none
- xfs: evict all inodes involved with log redo item
- xfs: check for race with xfs_reclaim_inode() in xfs_ifree_cluster()
- xfs: open-code xfs_buf_item_dirty()
- xfs: remove unnecessary dirty bli format check for ordered bufs
- xfs: ordered buffer log items are never formatted
- xfs: refactor buffer logging into buffer dirtying helper
- xfs: don't log dirty ranges for ordered buffers
- xfs: skip bmbt block ino validation during owner change
- xfs: move bmbt owner change to last step of extent swap
- xfs: disallow marking previously dirty buffers as ordered
- xfs: relog dirty buffers during swapext bmbt owner change
- xfs: disable per-inode DAX 

[Kernel-packages] [Bug 1718412] Re: Artful update to v4.13.3 stable release

[Launchpad Bug Tracker]

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

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

  * linux: 4.13.0-12.13 -proposed tracker (LP: #1718980)

  * [Feature] SKX: Support crystall ridge / far / near memory indication in PEBS
(LP: #1591813)
- perf/x86: Move Nehalem PEBS code to flag
- perf/x86: Fix data source decoding for Skylake

  * Upgrade to 4.13.0-11.12 in artful amd64 VM breaks display on wayland
(LP: #1718679)
- [Config] CONFIG_DRM_VBOXVIDEO=n

  * ipmmu-vmsa driver breaks arm64 boots (LP: #1718734)
- [Config] Disable CONFIG_IPMMU_VMSA on arm64

  * Vlun resize request could fail with cxlflash driver (LP: #1713575)
- scsi: cxlflash: Fix vlun resize failure in the shrink path

  * multipath -ll is not showing the disks which are actually multipath
(LP: #1718397)
- fs: aio: fix the increment of aio-nr and counting against aio-max-nr

  * [Feature] Crystal Ridge - BTT - Rework error clearing (LP: #1704350)
- libnvdimm, btt: fix a missed NVDIMM_IO_ATOMIC case in the write path
- libnvdimm, btt: refactor map entry operations with macros
- libnvdimm, btt: ensure that flags were also unchanged during a map_read
- libnvdimm, btt: cache sector_size in arena_info
- libnvdimm: fix potential deadlock while clearing errors
- libnvdimm, btt: rework error clearing

  * [Feature] Crystal Ridge - have 4k DAX faults use a common zero page
(LP: #1704439)
- mm: add vm_insert_mixed_mkwrite()
- dax: relocate some dax functions
- dax: use common 4k zero page for dax mmap reads
- dax: remove DAX code from page_cache_tree_insert()
- dax: move all DAX radix tree defs to fs/dax.c

  * [bug] 17.10: CDP test fail on platform of Purley-2S/4S/Neoncity,BDW-
de/ep/ex, (LP: #1716843)
- SAUCE: (no-up) x86/intel_rdt: Fix cdp info directory files issue

  * [featue] GPIO support for Denverton (LP: #1591829)
- pinctrl: intel: Add Intel Denverton pin controller support

  * ETPS/2 Elantech Touchpad inconsistently detected (Gigabyte P57W laptop)
(LP: #1594214)
- Input: i8042 - add Gigabyte P57 to the keyboard reset table

  * autopkgtest profile fails to build on armhf (LP: #1717920)
- [Packaging] autopkgtest -- disable d-i when dropping flavours

  * Artful update to v4.13.3 stable release (LP: #1718412)
- Revert "net: use lib/percpu_counter API for fragmentation mem accounting"
- Revert "net: fix percpu memory leaks"
- gianfar: Fix Tx flow control deactivation
- vhost_net: correctly check tx avail during rx busy polling
- ip6_gre: update mtu properly in ip6gre_err
- udp: drop head states only when all skb references are gone
- ipv6: fix memory leak with multiple tables during netns destruction
- ipv6: fix typo in fib6_net_exit()
- sctp: fix missing wake ups in some situations
- tcp: fix a request socket leak
- ip_tunnel: fix setting ttl and tos value in collect_md mode
- f2fs: let fill_super handle roll-forward errors
- f2fs: check hot_data for roll-forward recovery
- x86/fsgsbase/64: Fully initialize FS and GS state in start_thread_common
- x86/fsgsbase/64: Report FSBASE and GSBASE correctly in core dumps
- x86/switch_to/64: Rewrite FS/GS switching yet again to fix AMD CPUs
- x86/mm, mm/hwpoison: Clear PRESENT bit for kernel 1:1 mappings of poison
  pages
- ovl: fix false positive ESTALE on lookup
- fuse: allow server to run in different pid_ns
- idr: remove WARN_ON_ONCE() when trying to replace negative ID
- libnvdimm, btt: check memory allocation failure
- libnvdimm: fix integer overflow static analysis warning
- xfs: write unmount record for ro mounts
- xfs: toggle readonly state around xfs_log_mount_finish
- xfs: Add infrastructure needed for error propagation during buffer IO
  failure
- xfs: Properly retry failed inode items in case of error during buffer
  writeback
- xfs: fix recovery failure when log record header wraps log end
- xfs: always verify the log tail during recovery
- xfs: fix log recovery corruption error due to tail overwrite
- xfs: handle -EFSCORRUPTED during head/tail verification
- xfs: stop searching for free slots in an inode chunk when there are none
- xfs: evict all inodes involved with log redo item
- xfs: check for race with xfs_reclaim_inode() in xfs_ifree_cluster()
- xfs: open-code xfs_buf_item_dirty()
- xfs: remove unnecessary dirty bli format check for ordered bufs
- xfs: ordered buffer log items are never formatted
- xfs: refactor buffer logging into buffer dirtying helper
- xfs: don't log dirty ranges for ordered buffers
- xfs: skip bmbt block ino validation during owner change
- xfs: move bmbt owner change to last step of extent swap
- xfs: disallow marking previously dirty buffers as ordered
- xfs: relog dirty buffers during swapext bmbt owner change
- xfs: disable per-inode DAX 

[Kernel-packages] [Bug 1718871] Re: s4 get Error taking CPU down -34

[Joseph Salisbury]

Did this issue start happening after an update/upgrade? Was there a
kernel version where you were not having this particular problem? This
will help determine if the problem you are seeing is the result of a
regression, and when this regression was introduced.   If this is a
regression, we can perform a kernel bisect to identify the commit that
introduced the problem.


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

** Also affects: linux (Ubuntu Artful)
   Importance: Medium
   Status: Triaged

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

Title:
  s4 get Error taking CPU down -34

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

Bug description:
  When test S4 on Huawei 1288H V5 server as 
   #echo disk>/sys/power/state
  It show error of
Error taking CPU79 down: -34
Non-boot CPUs are not disabled 

  The echo command return with error of:
Write error: Numerical result out of range 

  From the dmesg it show error of:
CPU79 disable failed: CPU have 2 vectors assigned and there are only 1 
available 
Error taking CPU79 down: -34

  This server have been passed 16.04 certification
  (https://certification.ubuntu.com/hardware/201707-25617/).

  The test kernel is lasted 16.04.1 of linux-image-4.4.0-93-generic. It
  is also failed on 16.04 with kernel of 4.4.9-21-generic,
  4.12.0-041200-generic,4.14.0-999-generic which was download from
  （http://kernel.ubuntu.com/~kernel-ppa/mainline/). But it works on
  14.04 with kernel 3.13.0-24-generic and download kernel of
  3.13.0-031300-generic from above link.

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

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

[Kernel-packages] [Bug 1719545] Re: [LTCTest][Opal][FW910] cpupower monitor shows multiple stop Idle_Stats

[Joseph Salisbury]

Can you post a comment in this bug report once the patch gets accepted
upstream?

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

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

Title:
  [LTCTest][Opal][FW910] cpupower monitor shows multiple stop Idle_Stats

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

Bug description:
  == Comment: #0 - PAVAMAN SUBRAMANIYAM  - 2017-06-29 
02:30:22 ==
  ---Problem Description---
  cpupower monitor shows multiple stop Idle_Stats
   

   
  ---uname output---
  Linux zz376p1 4.10.0-26-generic #30~16.04.1-Ubuntu SMP Tue Jun 27 09:38:48 
UTC 2017 ppc64le ppc64le ppc64le GNU/Linux
   
  Machine Type = P9 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
  Install a P9 8375-42A Hardware with Ubuntu 16.04.3 OS.
  Then execute the cpupower monitor command to fetch all the Idle_Stats values.

  root@zz376p1:~# cpupower monitor
|Idle_Stats
  PKG |CORE|CPU | snoo | stop | stop
 0|   8|   0|  0.00|  0.00|  2.79
 0|   8|   1|  0.00|  0.00| 70.68
 0|   8|   2|  0.00|  0.00| 99.87
 0|   8|   3|  0.00|  0.00| 67.28
 0|  12|   4|  0.00|  0.00|  5.17
 0|  12|   5|  0.00|  0.00| 12.50
 0|  12|   6|  0.00|  0.00| 99.74
 0|  12|   7|  0.00|  0.00|  0.00
 8|2048|   8|  0.00|  0.00| 22.14
 8|2048|   9|  0.00|  0.00| 102.3
 8|2048|  10|  0.00|  0.00|  0.00
 8|2048|  11|  0.00|  0.00| 99.97
 8|2052|  12|  0.00|  0.00| 99.70
 8|2052|  13|  0.00|  0.00| 23.86
 8|2052|  14|  0.00|  0.00| 113.1
 8|2052|  15|  0.00|  0.00|  0.00

  As can be seen it shows 2 columns for stop.

  root@zz376p1:~# uname -a
  Linux zz376p1 4.10.0-26-generic #30~16.04.1-Ubuntu SMP Tue Jun 27 09:38:48 
UTC 2017 ppc64le ppc64le ppc64le GNU/Linux

  root@zz376p1:~# cat /etc/os-release
  NAME="Ubuntu"
  VERSION="16.04.2 LTS (Xenial Xerus)"
  ID=ubuntu
  ID_LIKE=debian
  PRETTY_NAME="Ubuntu 16.04.2 LTS"
  VERSION_ID="16.04"
  HOME_URL="http://www.ubuntu.com/;
  SUPPORT_URL="http://help.ubuntu.com/;
  BUG_REPORT_URL="http://bugs.launchpad.net/ubuntu/;
  VERSION_CODENAME=xenial
  UBUNTU_CODENAME=xenial

  root@zz376p1:~# cat /proc/cpuinfo | tail
  processor   : 15
  cpu : POWER9 (raw), altivec supported
  clock   : 2600.00MHz
  revision: 1.0 (pvr 004e 0100)

  timebase: 51200
  platform: PowerNV
  model   : 8375-42A
  machine : PowerNV 8375-42A
  firmware: OPAL
   
  Userspace tool common name: /usr/bin/cpupower 
   
  The userspace tool has the following bit modes: 64-bit 

  Userspace rpm: linux-tools-common

  Userspace tool obtained from project website:  na 
   
  *Additional Instructions for pavsu...@in.ibm.com: 
  -Post a private note with access information to the machine that the bug is 
occuring on.
  -Attach ltrace and strace of userspace application.

  
  .
  There are 3 idle_stats (3 states) in this system. 

  root@zz376p1:/sys/devices/system/cpu/cpu0/cpuidle/state2# cpupower monitor -l
  Monitor "Idle_Stats" (3 states) - Might overflow after 4294967295 s
  snoo  [T] -> snooze
  stop  [T] -> stop0_lite
  stop  [T] -> stop1_lite

  root@zz376p1:/sys/devices/system/cpu/cpu0/cpuidle/state2# cpupower idle-info
  CPUidle driver: powernv_idle
  CPUidle governor: menu
  analyzing CPU 0:

  Number of idle states: 3
  Available idle states: snooze stop0_lite stop1_lite
  snooze:
  Flags/Description: snooze
  Latency: 0
  Usage: 224
  Duration: 423
  stop0_lite:
  Flags/Description: stop0_lite
  Latency: 0
  Usage: 1685
  Duration: 530522
  stop1_lite:
  Flags/Description: stop1_lite
  Latency: 4
  Usage: 12693
  Duration: 5405898106

  root@zz376p1:/sys/devices/system/cpu/cpu0/cpuidle/state2# cpupower monitor -l
  Monitor "Idle_Stats" (3 states) - Might overflow after 4294967295 s
  snoo  [T] -> snooze
  stop  [T] -> stop0_lite
  stop  [T] -> stop1_lite
  root@zz376p1:/sys/devices/system/cpu/cpu0/cpuidle/state2# cpupower idle-info
  CPUidle driver: powernv_idle
  CPUidle governor: menu
  analyzing CPU 0:

  Number of idle states: 3
  Available idle states: snooze stop0_lite stop1_lite
  snooze:
  Flags/Description: snooze
  Latency: 0
  Usage: 272
  Duration: 905
  stop0_lite:
  Flags/Description: stop0_lite
  Latency: 0
  Usage: 2141
  Duration: 536399
  stop1_lite:
  Flags/Description: stop1_lite
  Latency: 4
  Usage: 15396
  Duration: 6625668881

  
  cpu monitor will print the results of all the 3 available idle_stats .

  The first stop -> stop0_lite stats
  and
  The second stop -> stop1_lite stats.

  cpupower monitor header prints the header list by getting the name of
  the idle stats.

  name  (name description)
  snoo   [T] -> snooze
  stop   [T] -> stop0_lite
  stop   [T] -> stop1_lite

[Kernel-packages] [Bug 1698470] Re: [Zesty][Yakkety] rtl8192e bug fixes

[Joseph Salisbury]

** Description changed:

- The following commits needed to be added to 4.10 and 4.8 kernels for
- stable operation of r8192e_pci driver. They are already in 4.11 and in
- 4.4.
+ == SRU Justification ==
+ The following commits needed to be added to the 4.10 and 4.4 kernels
+ for stable operation of r8192e_pci driver. They are already in Xenial because 
+ they came in with upstream stable updates.  However, upstream v4.10 is EOL so 
+ these commits are being submitted via SRU request.
+ 
+ All four commits are in mainline as of v4.12-rc2.
+ 
+ == Fixes ==
+ baabd567f87b ("staging: rtl8192e: rtl92e_fill_tx_desc fix write to mapped out 
memory.")
+ 867510bde14e ("staging: rtl8192e: fix 2 byte alignment of register BSSIDR.")
+ 90be652c9f15 ("staging: rtl8192e: rtl92e_get_eeprom_size Fix read size of 
EPROM_CMD.")
+ 95d93e271d92 ("staging: rtl8192e: GetTs Fix invalid TID 7 warning.")
+ 
+ == Regression Potential ==
+ These commits were also cc'd to stable and accepted, so additional upstream 
review
+ was performed.
+ 
+ == Test Case ==
+ A test kernel was built with these patches and tested by the original bug 
reporter.
+ The bug reporter states the test kernel resolved the bug.
+ 
+ 
+ 
+ The following commits needed to be added to 4.10 and 4.8 kernels for stable 
operation of r8192e_pci driver. They are already in 4.11 and in 4.4.
  
  commit baabd567f87be05330faa5140f72a91960e7405a upstream
  staging: rtl8192e: rtl92e_fill_tx_desc fix write to mapped out memory.
  
  commit 867510bde14e7b7fc6dd0f50b48f6753cfbd227a upstream.
  staging: rtl8192e: fix 2 byte alignment of register BSSIDR.
  
  commit 90be652c9f157d44b9c2803f902a8839796c090d upstream.
  staging: rtl8192e: rtl92e_get_eeprom_size Fix read size of EPROM_CMD.
  
  commit 95d93e271d920dfda369d4740b1cc1061d41fe7f upstream.
  staging: rtl8192e: GetTs Fix invalid TID 7 warning.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-22-generic 4.10.0-22.24
  ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15
  Uname: Linux 4.10.0-22-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.1
  Architecture: amd64
  AudioDevicesInUse:
-  USERPID ACCESS COMMAND
-  /dev/snd/controlC1:  canaries-64   2006 F pulseaudio
-  /dev/snd/controlC0:  canaries-64   2006 F pulseaudio
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC1:  canaries-64   2006 F pulseaudio
+  /dev/snd/controlC0:  canaries-64   2006 F pulseaudio
  CurrentDesktop: Unity:Unity7
  Date: Fri Jun 16 23:11:13 2017
  HibernationDevice: RESUME=UUID=f23ec6f5-7e6a-4559-a7f1-af640124e970
  InstallationDate: Installed on 2015-10-31 (594 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151027)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-22-generic 
root=UUID=48898cca-fae3-4cdc-9785-fc0b97f4cbd9 ro quiet splash
  RelatedPackageVersions:
-  linux-restricted-modules-4.10.0-22-generic N/A
-  linux-backports-modules-4.10.0-22-generic  N/A
-  linux-firmware 1.164.1
+  linux-restricted-modules-4.10.0-22-generic N/A
+  linux-backports-modules-4.10.0-22-generic  N/A
+  linux-firmware 1.164.1
  RfKill:
-  0: phy1: Wireless LAN
-   Soft blocked: no
-   Hard blocked: no
+  0: phy1: Wireless LAN
+   Soft blocked: no
+   Hard blocked: no
  SourcePackage: linux
  StagingDrivers: rtllib r8192e_pci
  UpgradeStatus: Upgraded to zesty on 2016-10-23 (236 days ago)
  dmi.bios.date: 04/18/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.70
  dmi.board.name: N3700-ITX
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.70:bd04/18/2016:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnN3700-ITX:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

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

Title:
  [Zesty][Yakkety] rtl8192e bug fixes

Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Yakkety:
  Won't Fix
Status in linux source package in Zesty:
  In Progress

Bug description:
  == SRU Justification ==
  The following commits needed to be added to the 4.10 and 4.4 kernels
  for stable operation of r8192e_pci driver. They are already in Xenial because 
  they came in with upstream stable updates.  However, upstream v4.10 is EOL so 
  these commits are being submitted via SRU request.

  All four commits are in mainline as of v4.12-rc2.

  == Fixes ==
  baabd567f87b ("staging: 

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

[Hlini Melsteð Jóngeirsson]

I just tried adding "blacklist=nouveau modprobe.blacklist=nouveau" but
it will not boot.

-- 
You 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:
  Incomplete

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 1594214] Re: ETPS/2 Elantech Touchpad inconsistently detected (Gigabyte P57W laptop)

[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/1594214

Title:
  ETPS/2 Elantech Touchpad inconsistently detected (Gigabyte P57W
  laptop)

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

Bug description:
  SRU Justification

  [Impact]
  Touchpad on Gigabyte P57W laptop does not gets detected reliably.

  [Test Case]
  Touchpad not does not gets detected reliably.
  With the patch, it can get detected reliably.

  [Regression Potential]
  Minimal. The change limits to a single specific laptop.
  ---

  On my Gigabyte P57W laptop the ETPS/2 Elantech touchpad is
  inconsistently detected at boot. Trying mainline 4.6 kernel did not
  help.

  WORKAROUND: Add kernel boot parameter:
  i8042.kbdreset=1

  The device is id=17 on xinput below:
  $ xinput

  ⎡ Virtual core pointerid=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ Kingsis Peripherals  Evoluent VerticalMouse 3   id=12   [slave  pointer 
 (2)]
  ⎜   ↳ Sunrex/JME Ghost Key Elimiantion Keyboard   id=14   [slave  pointer 
 (2)]
  ⎜   ↳ ETPS/2 Elantech Touchpadid=17   [slave  pointer 
 (2)]
  ⎣ Virtual core keyboard   id=3[master keyboard (2)]
  ↳ Virtual core XTEST keyboard id=5[slave  
keyboard (3)]
  ↳ Power Buttonid=6[slave  
keyboard (3)]
  ↳ Video Bus   id=7[slave  
keyboard (3)]
  ↳ Video Bus   id=8[slave  
keyboard (3)]
  ↳ Sleep Buttonid=9[slave  
keyboard (3)]
  ↳ Power Buttonid=10   [slave  
keyboard (3)]
  ↳ Sleep Buttonid=11   [slave  
keyboard (3)]
  ↳ Sunrex/JME Ghost Key Elimiantion Keyboard   id=13   [slave  
keyboard (3)]
  ↳ Chicony USB 2.0 Camera  id=15   [slave  
keyboard (3)]
  ↳ AT Translated Set 2 keyboardid=16   [slave  
keyboard (3)]

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-4.4.0-24-generic 4.4.0-24.43~14.04.1
  ProcVersionSignature: Ubuntu 4.4.0-24.43~14.04.1-generic 4.4.10
  Uname: Linux 4.4.0-24-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: amd64
  Date: Mon Jun 20 10:56:33 2016
  InstallationDate: Installed on 2014-05-20 (761 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  SourcePackage: linux-lts-xenial
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1698470] Re: [Zesty][Yakkety] rtl8192e bug fixes

[Joseph Salisbury]

** Changed in: linux (Ubuntu Zesty)
   Status: Triaged => In Progress

** Changed in: linux (Ubuntu Zesty)
 Assignee: (unassigned) => Joseph Salisbury (jsalisbury)

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

Title:
  [Zesty][Yakkety] rtl8192e bug fixes

Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Yakkety:
  Won't Fix
Status in linux source package in Zesty:
  In Progress

Bug description:
  The following commits needed to be added to 4.10 and 4.8 kernels for
  stable operation of r8192e_pci driver. They are already in 4.11 and in
  4.4.

  commit baabd567f87be05330faa5140f72a91960e7405a upstream
  staging: rtl8192e: rtl92e_fill_tx_desc fix write to mapped out memory.

  commit 867510bde14e7b7fc6dd0f50b48f6753cfbd227a upstream.
  staging: rtl8192e: fix 2 byte alignment of register BSSIDR.

  commit 90be652c9f157d44b9c2803f902a8839796c090d upstream.
  staging: rtl8192e: rtl92e_get_eeprom_size Fix read size of EPROM_CMD.

  commit 95d93e271d920dfda369d4740b1cc1061d41fe7f upstream.
  staging: rtl8192e: GetTs Fix invalid TID 7 warning.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-22-generic 4.10.0-22.24
  ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15
  Uname: Linux 4.10.0-22-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  canaries-64   2006 F pulseaudio
   /dev/snd/controlC0:  canaries-64   2006 F pulseaudio
  CurrentDesktop: Unity:Unity7
  Date: Fri Jun 16 23:11:13 2017
  HibernationDevice: RESUME=UUID=f23ec6f5-7e6a-4559-a7f1-af640124e970
  InstallationDate: Installed on 2015-10-31 (594 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151027)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-22-generic 
root=UUID=48898cca-fae3-4cdc-9785-fc0b97f4cbd9 ro quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-22-generic N/A
   linux-backports-modules-4.10.0-22-generic  N/A
   linux-firmware 1.164.1
  RfKill:
   0: phy1: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  StagingDrivers: rtllib r8192e_pci
  UpgradeStatus: Upgraded to zesty on 2016-10-23 (236 days ago)
  dmi.bios.date: 04/18/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.70
  dmi.board.name: N3700-ITX
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.70:bd04/18/2016:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnN3700-ITX:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

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

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

[Kernel-packages] [Bug 1706243] Re: Stranded with ENODEV after mdadm --readonly

[Joseph Salisbury]

** Description changed:

+ == SRU Justification ==
+ The bug reporter was trying to turn on the RAID journal.  One of the steps
+ is to set the device readonly.  This did not work as planned, or indeed at
+ all. After the first --readonly, all requests for the device report
+ "No such device or address" until a reboot, though /proc/mdstat says the
+ device is still there.
+ 
+ This bug is fixed by mainline commit 065e519e71b2c1f41936cce75b46b5ab34adb588,
+ which is in mainline as of 4.12-rc1.  The commit was also cc'd to stable, but 
+ upstream 4.10 is EOL, so that is the reason for the SRU request.
+ 
+ 
  Please backport upstream fix.
  
  
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git/commit/?h=v4.12.3=065e519e71b2c1f41936cce75b46b5ab34adb588
- --- 
+ ---
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  AudioDevicesInUse:
-  USERPID ACCESS COMMAND
-  /dev/snd/pcmC0D0c:   trent 10668 F...m pulseaudio
-  /dev/snd/pcmC0D0p:   trent 10668 F...m pulseaudio
-  /dev/snd/controlC0:  trent 10668 F pulseaudio
+  USERPID ACCESS COMMAND
+  /dev/snd/pcmC0D0c:   trent 10668 F...m pulseaudio
+  /dev/snd/pcmC0D0p:   trent 10668 F...m pulseaudio
+  /dev/snd/controlC0:  trent 10668 F pulseaudio
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=848108cd-a607-494c-a6ea-626267ed0a12
  InstallationDate: Installed on 2014-12-23 (944 days ago)
  InstallationMedia: Ubuntu-Server 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.3)
  IwConfig:
-  p11p1 no wireless extensions.
-  
-  lono wireless extensions.
+  p11p1 no wireless extensions.
+ 
+  lono wireless extensions.
  Lsusb:
-  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
-  Bus 001 Device 003: ID 046d:c52b Logitech, Inc. Unifying Receiver
-  Bus 001 Device 002: ID 1307:0163 Transcend Information, Inc. 256MB/512MB/1GB 
Flash Drive
-  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
+  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
+  Bus 001 Device 003: ID 046d:c52b Logitech, Inc. Unifying Receiver
+  Bus 001 Device 002: ID 1307:0163 Transcend Information, Inc. 256MB/512MB/1GB 
Flash Drive
+  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: System manufacturer System Product Name
  Package: linux (not installed)
  ProcEnviron:
-  TERM=xterm-256color
-  PATH=(custom, no user)
-  XDG_RUNTIME_DIR=
-  LANG=en_US.UTF-8
-  SHELL=/bin/bash
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=en_US.UTF-8
+  SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-26-generic 
root=UUID=7afb765b-b26b-44cc-ace1-654320cd85b2 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.10.0-26.30~16.04.1-generic 4.10.17
  RelatedPackageVersions:
-  linux-restricted-modules-4.10.0-26-generic N/A
-  linux-backports-modules-4.10.0-26-generic  N/A
-  linux-firmware 1.157.11
+  linux-restricted-modules-4.10.0-26-generic N/A
+  linux-backports-modules-4.10.0-26-generic  N/A
+  linux-firmware 1.157.11
  RfKill:
-  
+ 
  Tags:  xenial xenial
  Uname: Linux 4.10.0-26-generic x86_64
  UnreportableReason: The report belongs to a package that is not installed.
  UpgradeStatus: Upgraded to xenial on 2017-07-01 (24 days ago)
  UserGroups: adm audio cdrom dip glftpd lpadmin plugdev sambashare sudo
  _MarkForUpload: False
  dmi.bios.date: 06/16/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0808
  dmi.board.asset.tag: Default string
  dmi.board.name: PRIME B250M-A
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0808:bd06/16/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEB250M-A:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

** Description changed:

  == SRU Justification ==
  The bug reporter was trying to turn on the RAID journal.  One of the steps
  is to set the device readonly.  This did not work as planned, or indeed at
  all. After the first --readonly, all requests for the device report
  "No such device or address" until a reboot, though /proc/mdstat says the
  device is still there.
  
  This bug is fixed by mainline commit 065e519e71b2c1f41936cce75b46b5ab34adb588,
- which is in mainline as of 4.12-rc1.  The commit was also cc'd to stable, but 
+ which is in mainline as of 4.12-rc1.  The commit was also cc'd to stable, but
  upstream 4.10 is EOL, so that is the reason for the SRU request.
+ 
+ == Fix ==
+ commit 065e519e71b2c1f41936cce75b46b5ab34adb588
+ Author: NeilBrown 

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

[bugproxy]

--- Comment From cls...@us.ibm.com 2017-09-26 11:17 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:
  brk_near_huge test will hang on IBM s390x zKVM / zVM

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

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 1626984] Re: kernel BUG at /build/linux-lts-xenial-_hWfOZ/linux-lts-xenial-4.4.0/security/apparmor/include/context.h:69!

[Eric Desrochers]

I have tested with 4.4.0-97 and I can't reproduce the above behavior
now.

# uname -r
4.4.0-97-generic

# cat /sys/module/apparmor/parameters/audit
cat: /sys/module/apparmor/parameters/audit: Invalid argument

- Eric

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

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

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

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

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

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

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

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

[Kernel-packages] [Bug 1718713] Re: upon reboot monitor came up with flickerty screen

[ventrical]

Here is vid of one flickerty session.

It is itermittent. Some boots will be fine. Othes will be full scree
flickering of verbose code. In this vid it is one small flash and
several cursor flashes between plymouth and gdm login screen.

https://www.youtube.com/watch?v=7UlXdWneUw8=youtu.be

-- 
You 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 1706243] Re: Stranded with ENODEV after mdadm --readonly

[Joseph Salisbury]

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => Joseph Salisbury (jsalisbury)

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

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

** Changed in: linux (Ubuntu Zesty)
 Assignee: (unassigned) => Joseph Salisbury (jsalisbury)

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

** Changed in: linux (Ubuntu Zesty)
   Status: New => 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/1706243

Title:
  Stranded with ENODEV after mdadm --readonly

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

Bug description:
  Please backport upstream fix.

  
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git/commit/?h=v4.12.3=065e519e71b2c1f41936cce75b46b5ab34adb588
  --- 
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   trent 10668 F...m pulseaudio
   /dev/snd/pcmC0D0p:   trent 10668 F...m pulseaudio
   /dev/snd/controlC0:  trent 10668 F pulseaudio
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=848108cd-a607-494c-a6ea-626267ed0a12
  InstallationDate: Installed on 2014-12-23 (944 days ago)
  InstallationMedia: Ubuntu-Server 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.3)
  IwConfig:
   p11p1 no wireless extensions.
   
   lono wireless extensions.
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 046d:c52b Logitech, Inc. Unifying Receiver
   Bus 001 Device 002: ID 1307:0163 Transcend Information, Inc. 256MB/512MB/1GB 
Flash Drive
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: System manufacturer System Product Name
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-26-generic 
root=UUID=7afb765b-b26b-44cc-ace1-654320cd85b2 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.10.0-26.30~16.04.1-generic 4.10.17
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-26-generic N/A
   linux-backports-modules-4.10.0-26-generic  N/A
   linux-firmware 1.157.11
  RfKill:
   
  Tags:  xenial xenial
  Uname: Linux 4.10.0-26-generic x86_64
  UnreportableReason: The report belongs to a package that is not installed.
  UpgradeStatus: Upgraded to xenial on 2017-07-01 (24 days ago)
  UserGroups: adm audio cdrom dip glftpd lpadmin plugdev sambashare sudo
  _MarkForUpload: False
  dmi.bios.date: 06/16/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0808
  dmi.board.asset.tag: Default string
  dmi.board.name: PRIME B250M-A
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0808:bd06/16/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEB250M-A:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

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

[Kernel-packages] [Bug 1718980] Re: linux: 4.13.0-12.13 -proposed tracker

[Brad Figg]

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

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

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

** Tags removed: block-proposed-artful

** Tags removed: block-proposed

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

Title:
  linux: 4.13.0-12.13 -proposed tracker

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

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

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

  -- swm properties --
  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-development-workflow/+bug/1718980/+subscriptions

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

[Kernel-packages] [Bug 1718980] Re: linux: 4.13.0-12.13 -proposed tracker

[Seth Forshee]

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

Title:
  linux: 4.13.0-12.13 -proposed tracker

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

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

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

  -- swm properties --
  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-development-workflow/+bug/1718980/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-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

[Brad Figg]

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

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-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:
  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:
  Confirmed
Status in linux-aws package in Ubuntu:
  Invalid
Status in linux-aws source package in Xenial:
  Confirmed

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 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 1719644] [NEW] fanctl does not exit with an error when an up step fails

[Stefan Bader]

Public bug reported:

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

** Affects: ubuntu-fan (Ubuntu)
 Importance: Medium
 Assignee: Stefan Bader (smb)
 Status: Triaged

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

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 1696049] Re: xfstest sanity checks on seek operations fails

[Joseph Salisbury]

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

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/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 1646277] Re: Xenial server 16.04.x will have a black screen after PXE installation

[Joseph Salisbury]

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

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 1685892] Re: CVE-2017-7477: macsec: avoid heap overflow in skb_to_sgvec

[Steve Beattie]

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

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

Title:
  CVE-2017-7477: macsec: avoid heap overflow in skb_to_sgvec

Status in linux package in Ubuntu:
  Fix Released
Status in linux-hwe package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Invalid
Status in linux-hwe source package in Xenial:
  Fix Released
Status in linux source package in Yakkety:
  Fix Released
Status in linux-hwe source package in Yakkety:
  Invalid
Status in linux source package in Zesty:
  Fix Released
Status in linux-hwe source package in Zesty:
  Invalid

Bug description:
  Please apply
  
https://git.kernel.org/pub/scm/linux/kernel/git/davem/net.git/commit/?id=4d6fa57b4dab0d77f4d8e9d9c73d1e63f6fe8fee

  (See also http://www.openwall.com/lists/oss-security/2017/04/24/4 )

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

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

[Kernel-packages] [Bug 1718864] Re: BUG: unable to handle kernel NULL pointer dereference at 0000000000000020

[Colin Brash]

'kernel-bug-exists-upstream'

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

Title:
  BUG: unable to handle kernel NULL pointer dereference at
  0020

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu Artful Aardvark (development branch)
  Release:  17.10
  Bluez 5.46

  ProblemType: KernelOops
  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
  Annotation: Your system might become unstable now and might need to be 
restarted.
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  Date: Fri Sep 22 15:11:53 2017
  DuplicateSignature: BUG: unable to handle kernel NULL pointer dereference at 
location RIP: klist_next+0x16/0xb0 RSP: abf7c40f3c70
  Failure: oops
  InstallationDate: Installed on 2017-09-21 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170914)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-11-generic.efi.signed 
root=UUID=23f296e8-85c6-49c5-8040-17830fef017b ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: kerneloops-daemon N/A
  SourcePackage: linux
  Title: BUG: unable to handle kernel NULL pointer dereference at 
0020
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/03/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: KYSKLi70.86A.0037.2016.0603.1032
  dmi.board.name: NUC6i7KYB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: H90766-405
  dmi.chassis.type: 3
  dmi.chassis.vendor: Intel Corporation
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrKYSKLi70.86A.0037.2016.0603.1032:bd06/03/2016:svn:pn:pvr:rvnIntelCorporation:rnNUC6i7KYB:rvrH90766-405:cvnIntelCorporation:ct3:cvr1.0:

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

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

[Kernel-packages] [Bug 1718679] Re: Upgrade to 4.13.0-11.12 in artful amd64 VM breaks display on wayland

[Ubuntu QA Website]

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1718679

** Tags added: iso-testing

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

Title:
  Upgrade to 4.13.0-11.12 in artful amd64 VM breaks display on wayland

Status in linux package in Ubuntu:
  Fix Committed

Bug description:
  I have a virtualbox VM running artful which I upgrade every day. Today
  when upgrading from kernel  4.12.0-12.13 to 4.13.0-11.12, after a
  reboot gdm3 failed to display the login screen. All I got was a black
  screen, but I could access a virtual terminal.

  Downgrading the kernel back to 4.12.0-12.13 fixed the issue.

  jibel suggested to trying disabling wayland in gdm (by uncommenting
  #WaylandEnable=false in /etc/gdm3/custom.conf), and that did the trick
  too, but only X11 sessions were available of course.

  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/pcmC0D0c:   ubuntu 1726 F...m pulseaudio
   /dev/snd/pcmC0D0p:   ubuntu 1726 F...m pulseaudio
   /dev/snd/controlC0:  ubuntu 1726 F pulseaudio
   /dev/snd/timer:  ubuntu 1726 f pulseaudio
  Date: Thu Sep 21 15:40:40 2017
  InstallationDate: Installed on 2017-06-07 (106 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170606.1)
  IwConfig:
   enp0s3no wireless extensions.
   
   lono wireless extensions.
  Lsusb:
   Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet
   Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: innotek GmbH VirtualBox
  ProcFB: 0 vboxdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-11-generic 
root=UUID=e23963bd-97af-4402-b681-376a6fcaae62 ro quiet splash
  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
  StagingDrivers: vboxvideo
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
  dmi.product.family: Virtual Machine
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH

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

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

[Kernel-packages] [Bug 1719545] Re: [LTCTest][Opal][FW910] cpupower monitor shows multiple stop Idle_Stats

[Frank Heimes]

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

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

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

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

Title:
  [LTCTest][Opal][FW910] cpupower monitor shows multiple stop Idle_Stats

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

Bug description:
  == Comment: #0 - PAVAMAN SUBRAMANIYAM  - 2017-06-29 
02:30:22 ==
  ---Problem Description---
  cpupower monitor shows multiple stop Idle_Stats
   

   
  ---uname output---
  Linux zz376p1 4.10.0-26-generic #30~16.04.1-Ubuntu SMP Tue Jun 27 09:38:48 
UTC 2017 ppc64le ppc64le ppc64le GNU/Linux
   
  Machine Type = P9 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
  Install a P9 8375-42A Hardware with Ubuntu 16.04.3 OS.
  Then execute the cpupower monitor command to fetch all the Idle_Stats values.

  root@zz376p1:~# cpupower monitor
|Idle_Stats
  PKG |CORE|CPU | snoo | stop | stop
 0|   8|   0|  0.00|  0.00|  2.79
 0|   8|   1|  0.00|  0.00| 70.68
 0|   8|   2|  0.00|  0.00| 99.87
 0|   8|   3|  0.00|  0.00| 67.28
 0|  12|   4|  0.00|  0.00|  5.17
 0|  12|   5|  0.00|  0.00| 12.50
 0|  12|   6|  0.00|  0.00| 99.74
 0|  12|   7|  0.00|  0.00|  0.00
 8|2048|   8|  0.00|  0.00| 22.14
 8|2048|   9|  0.00|  0.00| 102.3
 8|2048|  10|  0.00|  0.00|  0.00
 8|2048|  11|  0.00|  0.00| 99.97
 8|2052|  12|  0.00|  0.00| 99.70
 8|2052|  13|  0.00|  0.00| 23.86
 8|2052|  14|  0.00|  0.00| 113.1
 8|2052|  15|  0.00|  0.00|  0.00

  As can be seen it shows 2 columns for stop.

  root@zz376p1:~# uname -a
  Linux zz376p1 4.10.0-26-generic #30~16.04.1-Ubuntu SMP Tue Jun 27 09:38:48 
UTC 2017 ppc64le ppc64le ppc64le GNU/Linux

  root@zz376p1:~# cat /etc/os-release
  NAME="Ubuntu"
  VERSION="16.04.2 LTS (Xenial Xerus)"
  ID=ubuntu
  ID_LIKE=debian
  PRETTY_NAME="Ubuntu 16.04.2 LTS"
  VERSION_ID="16.04"
  HOME_URL="http://www.ubuntu.com/;
  SUPPORT_URL="http://help.ubuntu.com/;
  BUG_REPORT_URL="http://bugs.launchpad.net/ubuntu/;
  VERSION_CODENAME=xenial
  UBUNTU_CODENAME=xenial

  root@zz376p1:~# cat /proc/cpuinfo | tail
  processor   : 15
  cpu : POWER9 (raw), altivec supported
  clock   : 2600.00MHz
  revision: 1.0 (pvr 004e 0100)

  timebase: 51200
  platform: PowerNV
  model   : 8375-42A
  machine : PowerNV 8375-42A
  firmware: OPAL
   
  Userspace tool common name: /usr/bin/cpupower 
   
  The userspace tool has the following bit modes: 64-bit 

  Userspace rpm: linux-tools-common

  Userspace tool obtained from project website:  na 
   
  *Additional Instructions for pavsu...@in.ibm.com: 
  -Post a private note with access information to the machine that the bug is 
occuring on.
  -Attach ltrace and strace of userspace application.

  
  .
  There are 3 idle_stats (3 states) in this system. 

  root@zz376p1:/sys/devices/system/cpu/cpu0/cpuidle/state2# cpupower monitor -l
  Monitor "Idle_Stats" (3 states) - Might overflow after 4294967295 s
  snoo  [T] -> snooze
  stop  [T] -> stop0_lite
  stop  [T] -> stop1_lite

  root@zz376p1:/sys/devices/system/cpu/cpu0/cpuidle/state2# cpupower idle-info
  CPUidle driver: powernv_idle
  CPUidle governor: menu
  analyzing CPU 0:

  Number of idle states: 3
  Available idle states: snooze stop0_lite stop1_lite
  snooze:
  Flags/Description: snooze
  Latency: 0
  Usage: 224
  Duration: 423
  stop0_lite:
  Flags/Description: stop0_lite
  Latency: 0
  Usage: 1685
  Duration: 530522
  stop1_lite:
  Flags/Description: stop1_lite
  Latency: 4
  Usage: 12693
  Duration: 5405898106

  root@zz376p1:/sys/devices/system/cpu/cpu0/cpuidle/state2# cpupower monitor -l
  Monitor "Idle_Stats" (3 states) - Might overflow after 4294967295 s
  snoo  [T] -> snooze
  stop  [T] -> stop0_lite
  stop  [T] -> stop1_lite
  root@zz376p1:/sys/devices/system/cpu/cpu0/cpuidle/state2# cpupower idle-info
  CPUidle driver: powernv_idle
  CPUidle governor: menu
  analyzing CPU 0:

  Number of idle states: 3
  Available idle states: snooze stop0_lite stop1_lite
  snooze:
  Flags/Description: snooze
  Latency: 0
  Usage: 272
  Duration: 905
  stop0_lite:
  Flags/Description: stop0_lite
  Latency: 0
  Usage: 2141
  Duration: 536399
  stop1_lite:
  Flags/Description: stop1_lite
  Latency: 4
  Usage: 15396
  Duration: 6625668881

  
  cpu monitor will print the results of all the 3 available idle_stats .

  The first stop -> stop0_lite stats
  and
  The second stop -> stop1_lite stats.

  cpupower monitor header prints the header list by getting the name of
  the idle stats.

  name  (name 

[Kernel-packages] [Bug 1718149] Re: linux: 4.4.0-97.120 -proposed tracker

[Taihsiang Ho]

Hardware Certification have begun testing this -proposed kernel.

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

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

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

Title:
  linux: 4.4.0-97.120 -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:
  In Progress
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:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Confirmed

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

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

  backports: 1718150,1718151
  derivatives: 1718153,1718154,1718155,1718156,1718157
  -- 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/1718149/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-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

[Hagen Kuehn]

** Attachment added: "Kernel 4.11.12 log when using blacklist nouveau arguments"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1697556/+attachment/4957292/+files/kernel.log.4.11.12.blacklist.nouveau.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 1697556] Re: Computer freezes after login - 4.10.0-22-generic

[Hagen Kuehn]

** Attachment added: "Kernel 4.11.12 log using default kernel arguments"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1697556/+attachment/4957290/+files/kernel.log.4.11.12.WithDefaultKernelArguments.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 1697556] Re: Computer freezes after login - 4.10.0-22-generic

[Hagen Kuehn]

** Attachment added: "Kernel 4.11.12 log using nomodeset argument"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1697556/+attachment/4957291/+files/kernel.log.4.11.12.nomodeset.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.
  dmi.board.version: A00
  

[Kernel-packages] [Bug 1697556] Re: Computer freezes after login - 4.10.0-22-generic

[Hagen Kuehn]

@Kai-Heng

In answer to your question "Can you confirm v4.11 freezes but v4.12-rc1
doesn't?", I can confirm that 4.11.12 freezes. Kernel log shows "NMI
watchdog: BUG: soft lockup - CPU#3 stuck for 23s! [kworker/3:1:70]".

Below are the test details along with the corresponding kernel log
output.

Kernel version used during this test:
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.11.12/
linux-headers-4.11.12-041112_4.11.12-041112.201707210350_all.deb
linux-headers-4.11.12-041112-generic_4.11.12-041112.201707210350_amd64.deb
linux-image-4.11.12-041112-generic_4.11.12-041112.201707210350_amd64.deb

Detailed answer:
v4.11.12 -> default kernel settings -> Progress icon rotates endlessly. When 
toggling to the ttl output I see "NMI watchdog: BUG: soft lockup - CPU#3 stuck 
for 23s! [kworker/3:1:70]" and many more.
-> See attached file kernel.log.4.11.12.WithDefaultKernelArguments.log

v4.11.12 -> NOMODESET -> Progress icon was displayed and rotated for a while 
but then the entire computer turned off. -> Not frozen but dead.
-> See attached file kernel.log.4.11.12.nomodeset.log

v4.11.12 -> "blacklist=nouveau modprobe.blacklist=nouveau" -> I could login 
without problems and the desktop appears to be displayed and working as I would 
expect.
-> See attached file kernel.log.4.11.12.blacklist.nouveau.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 

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

[bugproxy]

--- Comment From jac...@de.ibm.com 2017-09-26 07:41 EDT---
Ok, just checked kernel 4.4.0-97 ... that looks much better:

root@x:~# uname -a
Linux mclint 4.4.0-97-generic #120-Ubuntu SMP Tue Sep 19 17:27:01 UTC 2017 
s390x s390x s390x GNU/Linux
root@x:~# systool -v -m scsi_mod
Module = "scsi_mod"

Attributes:
uevent  = 

Parameters:
default_dev_flags   = "0"
eh_deadline = "-1"
inq_timeout = "20"
max_luns= "512"
scan= "async"
scsi_logging_level  = "0"
use_blk_mq  = "N"
root@x:~# systool -v -m dm_mod
Module = "dm_mod"

Attributes:
uevent  = 

Parameters:
reserved_bio_based_ios= "16"
reserved_rq_based_ios= "256"
stats_current_allocated_bytes= "0"
use_blk_mq  = "N"

blk_mq() is now turned off by default and that was our main concern! On
top, I also started two "big" pdebuild processes (firefox) that so far
had the potential to drive the system right into the hang scenario that
was the origin cause to write this ticket. The build did not succeed,
but the point is that the system did not run into the typical hang -> so
I think you can consider this problem being solved!

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

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

Status in Ubuntu on IBM z Systems:
  Fix Committed
Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Xenial:
  Fix Committed

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

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

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

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

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

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

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

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

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

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

  [ 5281.179428] INFO: task xfsaild/dm-11:1604 blocked for more than 120 
seconds.
  [ 5281.179437]   Not tainted 4.4.0-65-generic #86-Ubuntu
  [ 5281.179438] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [ 

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

[bugproxy]

--- Comment From michael.holz...@de.ibm.com 2017-09-26 07:23 EDT---
(In reply to comment #7)
> I just did a brief check on an Artful install based on the daily image from
> the 22nd and it looks like it's indeed already enabled:
>
> ubuntu@s1lp11:/$ lsb_release -a
> No LSB modules are available.
> Distributor ID:   Ubuntu
> Description:  Ubuntu Artful Aardvark (development branch)
> Release:  17.10
> Codename: artful
> ubuntu@s1lp11:/$ uname -r
> 4.13.0-11-generic
> ubuntu@s1lp11:/$ grep CONFIG_DEBUG_FS /boot/config-4.13.0-11-generic
> CONFIG_DEBUG_FS=y

For zfcpdump we have a special kernel package "zfcpdump-kernel".
Have you also checked the config for that 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/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 linux 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

Re: [Kernel-packages] [Bug 1528684] Re: Error parsing PCC subspaces from PCCT

[Piotr Miszczak]

I had to reinstall the system, still have an error, but it works at
least

2017-09-26 8:58 GMT+02:00 PrPom.cz :

> Same problem on Thinkpad L440, cannot even run Ubuntu, it crashes with
> this message on screen. Totally lost, have no clue, this discussion does
> not give a clear guide, what to do.
> Problem appeared all of a sudden, no new install, no dual boot.
> Please help!!!
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1528684
>
> Title:
>   Error parsing PCC subspaces from PCCT
>
> Status in linux package in Ubuntu:
>   Confirmed
>
> Bug description:
>   On my Thinkpad laptop I am seeing this error every time after the boot
>   in the dmesg output:
>
>   "Error parsing PCC subspaces from PCCT" (Portable C Compiler)
>
>   The attached log files should reveal more. I have no idea what it
>   means but seems serious. Hope you can solve this for once and all?
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 15.10
>   Package: linux-image-4.2.0-22-generic 4.2.0-22.27
>   ProcVersionSignature: Ubuntu 4.2.0-22.27-generic 4.2.6
>   Uname: Linux 4.2.0-22-generic x86_64
>   ApportVersion: 2.19.1-0ubuntu5
>   Architecture: amd64
>   AudioDevicesInUse:
>USERPID ACCESS COMMAND
>/dev/snd/controlC0:  michael-heuberger   2972 F pulseaudio
>/dev/snd/controlC1:  michael-heuberger   2972 F pulseaudio
>   Date: Wed Dec 23 09:36:44 2015
>   HibernationDevice: RESUME=UUID=bb8b6759-8fdb-4e4b-879b-7701cb217d2a
>   InstallationDate: Installed on 2015-05-22 (214 days ago)
>   InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
>   MachineType: LENOVO 20A7006KAU
>   ProcFB: 0 inteldrmfb
>   ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-22-generic
> root=UUID=b2f035dd-f14c-4a64-8834-5116d2df7864 ro cgroup_enable=memory
> swapaccount=1
>   PulseList:
>Error: command ['pacmd', 'list'] failed with exit code 1: Home
> directory not accessible: Permission denied
>No PulseAudio daemon running, or not running as session daemon.
>   RelatedPackageVersions:
>linux-restricted-modules-4.2.0-22-generic N/A
>linux-backports-modules-4.2.0-22-generic  N/A
>linux-firmware1.149.3
>   SourcePackage: linux
>   UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
>   UpgradeStatus: Upgraded to wily on 2015-11-15 (36 days ago)
>   dmi.bios.date: 11/20/2014
>   dmi.bios.vendor: LENOVO
>   dmi.bios.version: GRET42WW (1.19 )
>   dmi.board.asset.tag: Not Available
>   dmi.board.name: 20A7006KAU
>   dmi.board.vendor: LENOVO
>   dmi.board.version: 0B98417 WIN
>   dmi.chassis.asset.tag: No Asset Information
>   dmi.chassis.type: 10
>   dmi.chassis.vendor: LENOVO
>   dmi.chassis.version: Not Available
>   dmi.modalias: dmi:bvnLENOVO:bvrGRET42WW(1.19):bd11/20/2014:svnLENOVO:
> pn20A7006KAU:pvrThinkPadX1Carbon2nd:rvnLENOVO:rn20A7006KAU:
> rvr0B98417WIN:cvnLENOVO:ct10:cvrNotAvailable:
>   dmi.product.name: 20A7006KAU
>   dmi.product.version: ThinkPad X1 Carbon 2nd
>   dmi.sys.vendor: LENOVO
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/
> 1528684/+subscriptions
>


-- 
Piotr Miszczak

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

Title:
  Error parsing PCC subspaces from PCCT

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  On my Thinkpad laptop I am seeing this error every time after the boot
  in the dmesg output:

  "Error parsing PCC subspaces from PCCT" (Portable C Compiler)

  The attached log files should reveal more. I have no idea what it
  means but seems serious. Hope you can solve this for once and all?

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: linux-image-4.2.0-22-generic 4.2.0-22.27
  ProcVersionSignature: Ubuntu 4.2.0-22.27-generic 4.2.6
  Uname: Linux 4.2.0-22-generic x86_64
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  michael-heuberger   2972 F pulseaudio
   /dev/snd/controlC1:  michael-heuberger   2972 F pulseaudio
  Date: Wed Dec 23 09:36:44 2015
  HibernationDevice: RESUME=UUID=bb8b6759-8fdb-4e4b-879b-7701cb217d2a
  InstallationDate: Installed on 2015-05-22 (214 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: LENOVO 20A7006KAU
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-22-generic 
root=UUID=b2f035dd-f14c-4a64-8834-5116d2df7864 ro cgroup_enable=memory 
swapaccount=1
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-22-generic N/A
   

[Kernel-packages] [Bug 1653456] Re: ASUS G752VS: Touchpad and Fn keys not working (Ubuntu 16.04.1/16.10/17.04)

[aljosa]

Today I sent the following email to ASUS support:

26 September 2017

Quite a long time ago it's been reported that there's a serious issue with the 
ASUS G752VS laptop equipped with ELAN touchpad - regardless of which operating 
system is in use.
Problem is still unsolved: while in Linux the ELAN touchpad starts functioning 
only after resume from suspend, in Windows the opposite happens - ELAN touchpad 
stops functioning after resume from suspend!

The good news is that some smart people created a glorious fix for ASUS
G752VS touchpad issue. It's been reported that the mentioned fix works
both in Windows and Linux:

=
Patch:
http://www.share-online.biz/dl/E5NEO8QOUVO

Windows:
https://rog.asus.com/forum/showthread.php?93405-G-752-VS-Touchpad-Gesture-Fix

Linux (comments #130 and 134) :
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1653456
=

The bad news is that it is not an official ASUS fix, and that the patch
eventually contains a virus.

As an owner of G752VS laptop for which I paid the not so small amount of
2400 euro, I'm very interested to know if ASUS intents to officially fix
the long standing issue with ELAN touchpad in the foreseeable future?

Thanks in advance for any replies,
worried Customer.

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

Title:
  ASUS G752VS: Touchpad and Fn keys not working (Ubuntu
  16.04.1/16.10/17.04)

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Fix Released

Bug description:
  Non-Optimus laptop ASUS G752VS-GC063D-CST256.
  17.3" FHD LED 1920x1080, Intel Core i7-6700HQ (3.50Ghz), 16GB DDR4, 256GB M.2 
NVMe SSD + 1TB HDD 7200rpm, DVDRW-DL, Nvidia GTX1070 8GB GDDR5, Wifi 
802.11ac+Bluetooth 4.1 (Dual band) 2*2, Gb LAN, HDMI, mDP, Intel WiDi, USB3.0 
x4, USB3.1-Type C(Gen2) with Thunderbolt, HD webcam, Illuminated KB, no OS.

  Hello, after experimenting few days ago with Ubuntu 16.04.1, 16.10 and
  17.04, among other problems I found that touchpad and Fn keys (all
  except volume control) doesn't work on my brand new ASUS G752VS.

  It is very hard even to try Ubuntu 16.10 and 17.04 because of the
  missing mouse pointer. This problem must be related to a video driver
  because if after installing one is capable to install Nvidia drivers -
  problem is solved. This problem doesn't exist both while trying and
  installing Ubuntu 16.04.1!

  I'm currently on Windows 10, and this bug report is made from Ubuntu
  16.04.1 LiveCD.

  
  dmesg | grep -i elan
  [  101.082929] input: ELAN1203:00 04F3:3043 Touchpad as 
/devices/pci:00/:00:15.1/i2c_designware.1/i2c-1/i2c-ELAN1203:00/0018:04F3:3043.0007/input/input11
  [  101.082998] hid-multitouch 0018:04F3:3043.0007: input,hidraw6: I2C HID 
v1.00 Mouse [ELAN1203:00 04F3:3043] on i2c-ELAN1203:00

  
  xinput list
  ⎡ Virtual core pointerid=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ G-SPY USB Gaming Mouse  id=10   [slave  pointer 
 (2)]
  ⎜   ↳ ASASTeK COMPUTER INC. ROG MacroKey  id=13   [slave  pointer 
 (2)]
  ⎜   ↳ ASASTeK COMPUTER INC. ROG MacroKey  id=14   [slave  pointer 
 (2)]
  ⎜   ↳ ELAN1203:00 04F3:3043 Touchpad  id=15   [slave  pointer 
 (2)]
  ⎣ Virtual core keyboard   id=3[master keyboard (2)]
  ↳ Virtual core XTEST keyboard id=5[slave  
keyboard (3)]
  ↳ Power Buttonid=6[slave  
keyboard (3)]
  ↳ Video Bus   id=7[slave  
keyboard (3)]
  ↳ Sleep Buttonid=8[slave  
keyboard (3)]
  ↳ G-SPY USB Gaming Mouse  id=9[slave  
keyboard (3)]
  ↳ USB2.0 HD UVC WebCamid=11   [slave  
keyboard (3)]
  ↳ ASASTeK COMPUTER INC. ROG MacroKey  id=12   [slave  
keyboard (3)]
  ↳ Asus WMI hotkeysid=16   [slave  
keyboard (3)]
  ↳ AT Translated Set 2 keyboardid=17   [slave  
keyboard (3)]

  cat /proc/bus/input/devices
  I: Bus=0019 Vendor= Product=0005 Version=
  N: Name="Lid Switch"
  P: Phys=PNP0C0D/button/input0
  S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0D:00/input/input0
  U: Uniq=
  H: Handlers=event0 
  B: PROP=0
  B: EV=21
  B: SW=1

  I: Bus=0019 Vendor= Product=0003 Version=
  N: Name="Sleep Button"
  P: Phys=PNP0C0E/button/input0
  S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0E:00/input/input1
  U: Uniq=
  H: Handlers=kbd event1 
  B: PROP=0
  B: EV=3
  B: KEY=4000 0 0

  I: Bus=0019 Vendor= Product=0001 Version=
  N: Name="Power Button"
  P: Phys=LNXPWRBN/button/input0
  S: Sysfs=/devices/LNXSYSTM:00/LNXPWRBN:00/input/input2
  U: Uniq=
  H: 

[Kernel-packages] [Bug 1719553] Re: sysdig-smoke-test failed on ppc64le with Zesty kernel

[Colin Ian King]

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

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

Title:
  sysdig-smoke-test failed on ppc64le with Zesty kernel

Status in linux package in Ubuntu:
  In Progress

Bug description:
  Traceback (most recent call last):
  File "/home/ubuntu/autotest/client/shared/test.py", line 411, in _exec
  _call_test_function(self.execute, *p_args, **p_dargs)
  File "/home/ubuntu/autotest/client/shared/test.py", line 823, in 
_call_test_function
  return func(*args, **dargs)
  File "/home/ubuntu/autotest/client/shared/test.py", line 291, in execute
  postprocess_profiled_run, args, dargs)
  File "/home/ubuntu/autotest/client/shared/test.py", line 212, in 
_call_run_once
  self.run_once(*args, **dargs)
  File 
"/home/ubuntu/autotest/client/tests/ubuntu_sysdig_smoke_test/ubuntu_sysdig_smoke_test.py",
 line 22, in run_once
  self.results = utils.system_output(cmd, retain_output=True)
  File "/home/ubuntu/autotest/client/shared/utils.py", line 1267, in 
system_output
  verbose=verbose, args=args).stdout
  File "/home/ubuntu/autotest/client/shared/utils.py", line 918, in run
  "Command returned non-zero exit status")
  CmdError: Command failed, rc=1, Command returned non-zero exit status
  * Command:
  /home/ubuntu/autotest/client/tests/ubuntu_sysdig_smoke_test/ubuntu_sysdig
  _smoke_test.sh
  Exit status: 1
  Duration: 46.2219159603

  stdout:
  == sysdig smoke test to trace dd, cat, read and writes ==
  Limiting raw capture file to 16384 blocks
  Try 1 of 10
  Sysdig capture started after 2 seconds wait
  Raw capture file is 16 Mbytes
  Converted events file is 21 Mbytes
  Try 2 of 10
  Sysdig capture started after 2 seconds wait
  Raw capture file is 16 Mbytes
  Converted events file is 21 Mbytes
  Try 3 of 10
  Sysdig capture started after 2 seconds wait
  Raw capture file is 16 Mbytes
  Converted events file is 21 Mbytes
  Try 4 of 10
  Sysdig capture started after 2 seconds wait
  Raw capture file is 16 Mbytes
  Converted events file is 21 Mbytes
  Try 5 of 10
  Sysdig capture started after 2 seconds wait
  Raw capture file is 16 Mbytes
  Converted events file is 21 Mbytes
  Try 6 of 10
  Sysdig capture started after 2 seconds wait
  Raw capture file is 16 Mbytes
  Converted events file is 21 Mbytes
  Try 7 of 10
  Sysdig capture started after 2 seconds wait
  Raw capture file is 16 Mbytes
  Converted events file is 21 Mbytes
  Try 8 of 10
  Sysdig capture started after 2 seconds wait
  Raw capture file is 16 Mbytes
  Converted events file is 21 Mbytes
  Try 9 of 10
  Sysdig capture started after 2 seconds wait
  Raw capture file is 16 Mbytes
  Converted events file is 21 Mbytes
  Try 10 of 10
  Sysdig capture started after 2 seconds wait
  Raw capture file is 16 Mbytes
  Converted events file is 21 Mbytes
  Found:
  185201 sysdig events
  0 dd context switches
  0 cat context switches
  0 reads from /dev/zero by dd
  0 writes to /dev/null by dd
  FAILED (trace at least 25 context switches involving dd)
  FAILED (trace at least 25 context switches involving cat)
  FAILED (trace at least 25 reads of /dev/zero by dd)
  FAILED (trace at least 25 writes to /dev/null by dd)

  Summary: 0 passed, 4 failed

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

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

[Kernel-packages] [Bug 1719553] [NEW] sysdig-smoke-test failed on ppc64le with Zesty kernel

[Po-Hsu Lin]

Public bug reported:

Traceback (most recent call last):
File "/home/ubuntu/autotest/client/shared/test.py", line 411, in _exec
_call_test_function(self.execute, *p_args, **p_dargs)
File "/home/ubuntu/autotest/client/shared/test.py", line 823, in 
_call_test_function
return func(*args, **dargs)
File "/home/ubuntu/autotest/client/shared/test.py", line 291, in execute
postprocess_profiled_run, args, dargs)
File "/home/ubuntu/autotest/client/shared/test.py", line 212, in _call_run_once
self.run_once(*args, **dargs)
File 
"/home/ubuntu/autotest/client/tests/ubuntu_sysdig_smoke_test/ubuntu_sysdig_smoke_test.py",
 line 22, in run_once
self.results = utils.system_output(cmd, retain_output=True)
File "/home/ubuntu/autotest/client/shared/utils.py", line 1267, in system_output
verbose=verbose, args=args).stdout
File "/home/ubuntu/autotest/client/shared/utils.py", line 918, in run
"Command returned non-zero exit status")
CmdError: Command failed, rc=1, Command returned non-zero exit status
* Command:
/home/ubuntu/autotest/client/tests/ubuntu_sysdig_smoke_test/ubuntu_sysdig
_smoke_test.sh
Exit status: 1
Duration: 46.2219159603

stdout:
== sysdig smoke test to trace dd, cat, read and writes ==
Limiting raw capture file to 16384 blocks
Try 1 of 10
Sysdig capture started after 2 seconds wait
Raw capture file is 16 Mbytes
Converted events file is 21 Mbytes
Try 2 of 10
Sysdig capture started after 2 seconds wait
Raw capture file is 16 Mbytes
Converted events file is 21 Mbytes
Try 3 of 10
Sysdig capture started after 2 seconds wait
Raw capture file is 16 Mbytes
Converted events file is 21 Mbytes
Try 4 of 10
Sysdig capture started after 2 seconds wait
Raw capture file is 16 Mbytes
Converted events file is 21 Mbytes
Try 5 of 10
Sysdig capture started after 2 seconds wait
Raw capture file is 16 Mbytes
Converted events file is 21 Mbytes
Try 6 of 10
Sysdig capture started after 2 seconds wait
Raw capture file is 16 Mbytes
Converted events file is 21 Mbytes
Try 7 of 10
Sysdig capture started after 2 seconds wait
Raw capture file is 16 Mbytes
Converted events file is 21 Mbytes
Try 8 of 10
Sysdig capture started after 2 seconds wait
Raw capture file is 16 Mbytes
Converted events file is 21 Mbytes
Try 9 of 10
Sysdig capture started after 2 seconds wait
Raw capture file is 16 Mbytes
Converted events file is 21 Mbytes
Try 10 of 10
Sysdig capture started after 2 seconds wait
Raw capture file is 16 Mbytes
Converted events file is 21 Mbytes
Found:
185201 sysdig events
0 dd context switches
0 cat context switches
0 reads from /dev/zero by dd
0 writes to /dev/null by dd
FAILED (trace at least 25 context switches involving dd)
FAILED (trace at least 25 context switches involving cat)
FAILED (trace at least 25 reads of /dev/zero by dd)
FAILED (trace at least 25 writes to /dev/null by dd)

Summary: 0 passed, 4 failed

** Affects: linux (Ubuntu)
 Importance: Medium
 Assignee: Colin Ian King (colin-king)
 Status: In Progress


** Tags: zesty

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => Colin Ian King (colin-king)

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

Title:
  sysdig-smoke-test failed on ppc64le with Zesty kernel

Status in linux package in Ubuntu:
  In Progress

Bug description:
  Traceback (most recent call last):
  File "/home/ubuntu/autotest/client/shared/test.py", line 411, in _exec
  _call_test_function(self.execute, *p_args, **p_dargs)
  File "/home/ubuntu/autotest/client/shared/test.py", line 823, in 
_call_test_function
  return func(*args, **dargs)
  File "/home/ubuntu/autotest/client/shared/test.py", line 291, in execute
  postprocess_profiled_run, args, dargs)
  File "/home/ubuntu/autotest/client/shared/test.py", line 212, in 
_call_run_once
  self.run_once(*args, **dargs)
  File 
"/home/ubuntu/autotest/client/tests/ubuntu_sysdig_smoke_test/ubuntu_sysdig_smoke_test.py",
 line 22, in run_once
  self.results = utils.system_output(cmd, retain_output=True)
  File "/home/ubuntu/autotest/client/shared/utils.py", line 1267, in 
system_output
  verbose=verbose, args=args).stdout
  File "/home/ubuntu/autotest/client/shared/utils.py", line 918, in run
  "Command returned non-zero exit status")
  CmdError: Command failed, rc=1, Command returned non-zero exit status
  * Command:
  /home/ubuntu/autotest/client/tests/ubuntu_sysdig_smoke_test/ubuntu_sysdig
  _smoke_test.sh
  Exit status: 1
  Duration: 46.2219159603

  stdout:
  == sysdig smoke test to trace dd, cat, read and writes ==
  Limiting raw capture file to 16384 blocks
  Try 1 of 10
  Sysdig capture started after 2 seconds wait
  Raw capture file is 16 Mbytes
  Converted events file is 21 Mbytes
  Try 2 of 10
  Sysdig capture started after 2 seconds wait
  Raw capture file is 16 Mbytes
  Converted events file is 21 Mbytes
  Try 3 of 10
  Sysdig capture started after 2 seconds wait
  Raw capture file is 16 Mbytes
  Converted events 

[Kernel-packages] [Bug 1719545] [NEW] [LTCTest][Opal][FW910] cpupower monitor shows multiple stop Idle_Stats

[bugproxy]

Public bug reported:

== Comment: #0 - PAVAMAN SUBRAMANIYAM  - 2017-06-29 
02:30:22 ==
---Problem Description---
cpupower monitor shows multiple stop Idle_Stats
 

 
---uname output---
Linux zz376p1 4.10.0-26-generic #30~16.04.1-Ubuntu SMP Tue Jun 27 09:38:48 UTC 
2017 ppc64le ppc64le ppc64le GNU/Linux
 
Machine Type = P9 
 
---Debugger---
A debugger is not configured
 
---Steps to Reproduce---
Install a P9 8375-42A Hardware with Ubuntu 16.04.3 OS.
Then execute the cpupower monitor command to fetch all the Idle_Stats values.

root@zz376p1:~# cpupower monitor
  |Idle_Stats
PKG |CORE|CPU | snoo | stop | stop
   0|   8|   0|  0.00|  0.00|  2.79
   0|   8|   1|  0.00|  0.00| 70.68
   0|   8|   2|  0.00|  0.00| 99.87
   0|   8|   3|  0.00|  0.00| 67.28
   0|  12|   4|  0.00|  0.00|  5.17
   0|  12|   5|  0.00|  0.00| 12.50
   0|  12|   6|  0.00|  0.00| 99.74
   0|  12|   7|  0.00|  0.00|  0.00
   8|2048|   8|  0.00|  0.00| 22.14
   8|2048|   9|  0.00|  0.00| 102.3
   8|2048|  10|  0.00|  0.00|  0.00
   8|2048|  11|  0.00|  0.00| 99.97
   8|2052|  12|  0.00|  0.00| 99.70
   8|2052|  13|  0.00|  0.00| 23.86
   8|2052|  14|  0.00|  0.00| 113.1
   8|2052|  15|  0.00|  0.00|  0.00

As can be seen it shows 2 columns for stop.

root@zz376p1:~# uname -a
Linux zz376p1 4.10.0-26-generic #30~16.04.1-Ubuntu SMP Tue Jun 27 09:38:48 UTC 
2017 ppc64le ppc64le ppc64le GNU/Linux

root@zz376p1:~# cat /etc/os-release
NAME="Ubuntu"
VERSION="16.04.2 LTS (Xenial Xerus)"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu 16.04.2 LTS"
VERSION_ID="16.04"
HOME_URL="http://www.ubuntu.com/;
SUPPORT_URL="http://help.ubuntu.com/;
BUG_REPORT_URL="http://bugs.launchpad.net/ubuntu/;
VERSION_CODENAME=xenial
UBUNTU_CODENAME=xenial

root@zz376p1:~# cat /proc/cpuinfo | tail
processor   : 15
cpu : POWER9 (raw), altivec supported
clock   : 2600.00MHz
revision: 1.0 (pvr 004e 0100)

timebase: 51200
platform: PowerNV
model   : 8375-42A
machine : PowerNV 8375-42A
firmware: OPAL
 
Userspace tool common name: /usr/bin/cpupower 
 
The userspace tool has the following bit modes: 64-bit 

Userspace rpm: linux-tools-common

Userspace tool obtained from project website:  na 
 
*Additional Instructions for pavsu...@in.ibm.com: 
-Post a private note with access information to the machine that the bug is 
occuring on.
-Attach ltrace and strace of userspace application.


.
There are 3 idle_stats (3 states) in this system. 

root@zz376p1:/sys/devices/system/cpu/cpu0/cpuidle/state2# cpupower monitor -l
Monitor "Idle_Stats" (3 states) - Might overflow after 4294967295 s
snoo[T] -> snooze
stop[T] -> stop0_lite
stop[T] -> stop1_lite

root@zz376p1:/sys/devices/system/cpu/cpu0/cpuidle/state2# cpupower idle-info
CPUidle driver: powernv_idle
CPUidle governor: menu
analyzing CPU 0:

Number of idle states: 3
Available idle states: snooze stop0_lite stop1_lite
snooze:
Flags/Description: snooze
Latency: 0
Usage: 224
Duration: 423
stop0_lite:
Flags/Description: stop0_lite
Latency: 0
Usage: 1685
Duration: 530522
stop1_lite:
Flags/Description: stop1_lite
Latency: 4
Usage: 12693
Duration: 5405898106

root@zz376p1:/sys/devices/system/cpu/cpu0/cpuidle/state2# cpupower monitor -l
Monitor "Idle_Stats" (3 states) - Might overflow after 4294967295 s
snoo[T] -> snooze
stop[T] -> stop0_lite
stop[T] -> stop1_lite
root@zz376p1:/sys/devices/system/cpu/cpu0/cpuidle/state2# cpupower idle-info
CPUidle driver: powernv_idle
CPUidle governor: menu
analyzing CPU 0:

Number of idle states: 3
Available idle states: snooze stop0_lite stop1_lite
snooze:
Flags/Description: snooze
Latency: 0
Usage: 272
Duration: 905
stop0_lite:
Flags/Description: stop0_lite
Latency: 0
Usage: 2141
Duration: 536399
stop1_lite:
Flags/Description: stop1_lite
Latency: 4
Usage: 15396
Duration: 6625668881


cpu monitor will print the results of all the 3 available idle_stats .

The first stop -> stop0_lite stats
and
The second stop -> stop1_lite stats.

cpupower monitor header prints the header list by getting the name of
the idle stats.

name  (name description)
snoo [T] -> snooze
stop [T] -> stop0_lite
stop [T] -> stop1_lite

We can change the header to be more meaningful so user won't interpret
it as 2 columns for stop.

May be we need to change the code to print the header to use name description 
instead of name.
.
I will work on the patch and get it resolve.


== Comment: #8 - PAVAMAN SUBRAMANIYAM  - 2017-06-30 
03:42:01 ==
I have executed the command again with the fixed cpupower utility.


Submitted patch upstream and awaiting response. 

https://lkml.org/lkml/2017/7/31/177

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


** Tags: architecture-ppc64le bugnameltc-156226 severity-medium 
targetmilestone-inin16043

** Tags added: 

[Kernel-packages] [Bug 1718871] Re: s4 get Error taking CPU down -34

[Zhanglei Mao]

For the newest upstream kernel of http://kernel.ubuntu.com/~kernel-
ppa/mainline/v4.14-rc2/linux-
image-4.14.0-041400rc2-generic_4.14.0-041400rc2.201709242031_amd64.deb.
The S4 test is same error.

tags:kernel-bug-exists-upstream

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

Title:
  s4 get Error taking CPU down -34

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  When test S4 on Huawei 1288H V5 server as 
   #echo disk>/sys/power/state
  It show error of
Error taking CPU79 down: -34
Non-boot CPUs are not disabled 

  The echo command return with error of:
Write error: Numerical result out of range 

  From the dmesg it show error of:
CPU79 disable failed: CPU have 2 vectors assigned and there are only 1 
available 
Error taking CPU79 down: -34

  This server have been passed 16.04 certification
  (https://certification.ubuntu.com/hardware/201707-25617/).

  The test kernel is lasted 16.04.1 of linux-image-4.4.0-93-generic. It
  is also failed on 16.04 with kernel of 4.4.9-21-generic,
  4.12.0-041200-generic,4.14.0-999-generic which was download from
  （http://kernel.ubuntu.com/~kernel-ppa/mainline/). But it works on
  14.04 with kernel 3.13.0-24-generic and download kernel of
  3.13.0-031300-generic from above link.

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

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

[Kernel-packages] [Bug 1719545] [NEW] [LTCTest][Opal][FW910] cpupower monitor shows multiple stop Idle_Stats

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

== Comment: #0 - PAVAMAN SUBRAMANIYAM  - 2017-06-29 
02:30:22 ==
---Problem Description---
cpupower monitor shows multiple stop Idle_Stats
 

 
---uname output---
Linux zz376p1 4.10.0-26-generic #30~16.04.1-Ubuntu SMP Tue Jun 27 09:38:48 UTC 
2017 ppc64le ppc64le ppc64le GNU/Linux
 
Machine Type = P9 
 
---Debugger---
A debugger is not configured
 
---Steps to Reproduce---
Install a P9 8375-42A Hardware with Ubuntu 16.04.3 OS.
Then execute the cpupower monitor command to fetch all the Idle_Stats values.

root@zz376p1:~# cpupower monitor
  |Idle_Stats
PKG |CORE|CPU | snoo | stop | stop
   0|   8|   0|  0.00|  0.00|  2.79
   0|   8|   1|  0.00|  0.00| 70.68
   0|   8|   2|  0.00|  0.00| 99.87
   0|   8|   3|  0.00|  0.00| 67.28
   0|  12|   4|  0.00|  0.00|  5.17
   0|  12|   5|  0.00|  0.00| 12.50
   0|  12|   6|  0.00|  0.00| 99.74
   0|  12|   7|  0.00|  0.00|  0.00
   8|2048|   8|  0.00|  0.00| 22.14
   8|2048|   9|  0.00|  0.00| 102.3
   8|2048|  10|  0.00|  0.00|  0.00
   8|2048|  11|  0.00|  0.00| 99.97
   8|2052|  12|  0.00|  0.00| 99.70
   8|2052|  13|  0.00|  0.00| 23.86
   8|2052|  14|  0.00|  0.00| 113.1
   8|2052|  15|  0.00|  0.00|  0.00

As can be seen it shows 2 columns for stop.

root@zz376p1:~# uname -a
Linux zz376p1 4.10.0-26-generic #30~16.04.1-Ubuntu SMP Tue Jun 27 09:38:48 UTC 
2017 ppc64le ppc64le ppc64le GNU/Linux

root@zz376p1:~# cat /etc/os-release
NAME="Ubuntu"
VERSION="16.04.2 LTS (Xenial Xerus)"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu 16.04.2 LTS"
VERSION_ID="16.04"
HOME_URL="http://www.ubuntu.com/;
SUPPORT_URL="http://help.ubuntu.com/;
BUG_REPORT_URL="http://bugs.launchpad.net/ubuntu/;
VERSION_CODENAME=xenial
UBUNTU_CODENAME=xenial

root@zz376p1:~# cat /proc/cpuinfo | tail
processor   : 15
cpu : POWER9 (raw), altivec supported
clock   : 2600.00MHz
revision: 1.0 (pvr 004e 0100)

timebase: 51200
platform: PowerNV
model   : 8375-42A
machine : PowerNV 8375-42A
firmware: OPAL
 
Userspace tool common name: /usr/bin/cpupower 
 
The userspace tool has the following bit modes: 64-bit 

Userspace rpm: linux-tools-common

Userspace tool obtained from project website:  na 
 
*Additional Instructions for pavsu...@in.ibm.com: 
-Post a private note with access information to the machine that the bug is 
occuring on.
-Attach ltrace and strace of userspace application.


.
There are 3 idle_stats (3 states) in this system. 

root@zz376p1:/sys/devices/system/cpu/cpu0/cpuidle/state2# cpupower monitor -l
Monitor "Idle_Stats" (3 states) - Might overflow after 4294967295 s
snoo[T] -> snooze
stop[T] -> stop0_lite
stop[T] -> stop1_lite

root@zz376p1:/sys/devices/system/cpu/cpu0/cpuidle/state2# cpupower idle-info
CPUidle driver: powernv_idle
CPUidle governor: menu
analyzing CPU 0:

Number of idle states: 3
Available idle states: snooze stop0_lite stop1_lite
snooze:
Flags/Description: snooze
Latency: 0
Usage: 224
Duration: 423
stop0_lite:
Flags/Description: stop0_lite
Latency: 0
Usage: 1685
Duration: 530522
stop1_lite:
Flags/Description: stop1_lite
Latency: 4
Usage: 12693
Duration: 5405898106

root@zz376p1:/sys/devices/system/cpu/cpu0/cpuidle/state2# cpupower monitor -l
Monitor "Idle_Stats" (3 states) - Might overflow after 4294967295 s
snoo[T] -> snooze
stop[T] -> stop0_lite
stop[T] -> stop1_lite
root@zz376p1:/sys/devices/system/cpu/cpu0/cpuidle/state2# cpupower idle-info
CPUidle driver: powernv_idle
CPUidle governor: menu
analyzing CPU 0:

Number of idle states: 3
Available idle states: snooze stop0_lite stop1_lite
snooze:
Flags/Description: snooze
Latency: 0
Usage: 272
Duration: 905
stop0_lite:
Flags/Description: stop0_lite
Latency: 0
Usage: 2141
Duration: 536399
stop1_lite:
Flags/Description: stop1_lite
Latency: 4
Usage: 15396
Duration: 6625668881


cpu monitor will print the results of all the 3 available idle_stats .

The first stop -> stop0_lite stats
and
The second stop -> stop1_lite stats.

cpupower monitor header prints the header list by getting the name of
the idle stats.

name  (name description)
snoo [T] -> snooze
stop [T] -> stop0_lite
stop [T] -> stop1_lite

We can change the header to be more meaningful so user won't interpret
it as 2 columns for stop.

May be we need to change the code to print the header to use name description 
instead of name.
.
I will work on the patch and get it resolve.


== Comment: #8 - PAVAMAN SUBRAMANIYAM  - 2017-06-30 
03:42:01 ==
I have executed the command again with the fixed cpupower utility.


Submitted patch upstream and awaiting response. 

https://lkml.org/lkml/2017/7/31/177

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


** Tags: architecture-ppc64le bugnameltc-156226 severity-medium 
targetmilestone-inin16043
-- 

[Kernel-packages] [Bug 1716301] Re: wifi driver: mt7601u not work on 16.04

[chenzero]

I just fell a little strange that is , why some info log in mt7801u is not 
printed, 
e.g: in 09-26.2.txt, no any log about mt7601u. however, in mt7801u code, it 
printed those info

[  127.095245] mt7601u 1-1.4:1.0: ASIC revision: 76010001 MAC revision: 76010500
[  127.146876] mt7601u 1-1.4:1.0: Firmware Version: 0.1.00 Build: 7640 Build 
time: 201302052146

and I sometimes still can see on kernel 4.13 or  4.4.0-91
  Vendor request failed with -110.   

what's the differences between replying on system to automatically switch mode 
and I manually eject the disk , or if I run command 
sudo usb_modeswitch -v 148f -p 2878 -V 148f -P 7601 -K 

Thanks !

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/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 

[Kernel-packages] [Bug 1716301] Re: wifi driver: mt7601u not work on 16.04

[chenzero]

I tried kernel 4.13. however, no much diff with kernel 4.4.0-91.
I must mention that in both kernel, no ALAWAYS the adapter is automatically 
recoginized as 148f:7601, sometimes, it still mounted as 148f:2878, sometimes, 
it's 7601. ( I found the pattern is: unplug the adapter, wait a relative long 
time, e.g: 1 or 2 minutes, plug the adapter, then it's 7601. if immediately 
plug in the adapter, say just wait 10 seconds, mostly, it's mounted as usb 
stroage disk and will not change to 7601).

I can use following command to switch mode, with errors, but mode
changed to 7601.

chenzero@chenzero:/usr/share/usb_modeswitch$ sudo usb_modeswitch -v 148f -p 
2878 -V 148f -P 7601 -K
Look for target devices ...
 No devices in target mode or class found
Look for default devices ...
   product ID matched
 Found devices in default mode (1)
Access device 016 on bus 001
Current configuration number is 1
Use interface number 0
Use endpoints 0x08 (out) and 0x84 (in)
Error: could not get description string "manufacturer"
Error: could not get description string "product"

USB description data (for identification)
-
Manufacturer: 
 Product: 
  Serial No.: not provided
-
Sending standard EJECT sequence
Looking for active driver ...
 OK, driver detached
Set up interface 0
Use endpoint 0x08 for message sending ...
Trying to send message 1 to endpoint 0x08 ...
 OK, message successfully sent
Read the response to message 1 (CSW) ...
 Response successfully read (13 bytes).
Trying to send message 2 to endpoint 0x08 ...
 OK, message successfully sent
Read the response to message 2 (CSW) ...
 Response reading failed (error -1)
 Device is gone, skip any further commands
-> Run lsusb to note any changes. Bye!


Please see the attached 09-26.2.txt

Thanks!


** Attachment added: "09-26.2.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1716301/+attachment/4957218/+files/09-26.2.txt

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/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 

[Kernel-packages] [Bug 1718159] Re: linux: 3.13.0-133.182 -proposed tracker

[Po-Hsu Lin]

** 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) => Po-Hsu Lin 
(cypressyew)

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

Title:
  linux: 3.13.0-133.182 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Trusty:
  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: 1718161
  derivatives:
  -- swm properties --
  boot-testing-requested: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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

[Kernel-packages] [Bug 1521173] Re: AER: Corrected error received: id=00e0

[jon anoter]

I just wanted to report that I am on Asus X550V (Skylake  i7-7700HQ Cpu
with Nividia GeForce GTX 950M) and your workaround in first paragraph
worked:

"Note: Current workaround is to add pci=noaer to your kernel command
line:

1) edit /etc/default/grub and and add pci=noaer to the line starting with 
GRUB_CMDLINE_LINUX_DEFAULT. It will look like this:
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash pci=noaer"
2) run "sudo update-grub"
3) reboot"
`
That fixed my problem. No more `PCIe Bus Error` and `AER error` messages now. 

(I also used `sudo find /var/log -type f -name "*.gz" -delete` to remove
old log files and enabled  `logrotate` , because I had over 100Gb (!) in
those thousands of spam `pcie error` log messages.)

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

Title:
  AER: Corrected error received: id=00e0

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Xenial:
  Triaged

Bug description:
  Note: Current workaround is to add pci=noaer to your kernel command
  line:

  1) edit /etc/default/grub and and add pci=noaer to the line starting with 
GRUB_CMDLINE_LINUX_DEFAULT. It will look like this: 
  GRUB_CMDLINE_LINUX_DEFAULT="quiet splash pci=noaer"
  2) run "sudo update-grub"
  3) reboot

  

  My dmesg gets completely spammed with the following messages appearing
  over and over again. It stops after one s3 cycle; it only happens
  after reboot.

  [ 5315.986588] pcieport :00:1c.0: AER: Corrected error received: id=00e0
  [ 5315.987249] pcieport :00:1c.0: can't find device of ID00e0
  [ 5315.995632] pcieport :00:1c.0: AER: Corrected error received: id=00e0
  [ 5315.995664] pcieport :00:1c.0: PCIe Bus Error: severity=Corrected, 
type=Physical Layer, id=00e0(Receiver ID)
  [ 5315.995674] pcieport :00:1c.0:   device [8086:9d14] error 
status/mask=0001/2000
  [ 5315.995683] pcieport :00:1c.0:[ 0] Receiver Error
  [ 5316.002772] pcieport :00:1c.0: AER: Corrected error received: id=00e0
  [ 5316.002811] pcieport :00:1c.0: PCIe Bus Error: severity=Corrected, 
type=Physical Layer, id=00e0(Receiver ID)
  [ 5316.002826] pcieport :00:1c.0:   device [8086:9d14] error 
status/mask=0001/2000
  [ 5316.002838] pcieport :00:1c.0:[ 0] Receiver Error
  [ 5316.009926] pcieport :00:1c.0: AER: Corrected error received: id=00e0
  [ 5316.009964] pcieport :00:1c.0: PCIe Bus Error: severity=Corrected, 
type=Physical Layer, id=00e0(Receiver ID)
  [ 5316.009979] pcieport :00:1c.0:   device [8086:9d14] error 
status/mask=0001/2000
  [ 5316.009991] pcieport :00:1c.0:[ 0] Receiver Error

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.2.0-19-generic 4.2.0-19.23 [modified: 
boot/vmlinuz-4.2.0-19-generic]
  ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6
  Uname: Linux 4.2.0-19-generic x86_64
  ApportVersion: 2.19.2-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   david  1502 F...m pulseaudio
   /dev/snd/controlC0:  david  1502 F pulseaudio
  CurrentDesktop: Unity
  Date: Mon Nov 30 13:19:00 2015
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=fe528b90-b4eb-4a20-82bd-6a03b79cfb14
  InstallationDate: Installed on 2015-11-28 (2 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151127)
  MachineType: Dell Inc. Inspiron 13-7359
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-19-generic.efi.signed 
root=UUID=94d54f88-5d18-4e2b-960a-8717d6e618bb ro noprompt persistent quiet 
splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-19-generic N/A
   linux-backports-modules-4.2.0-19-generic  N/A
   linux-firmware1.153
  SourcePackage: linux
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/07/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 01.00.00
  dmi.board.name: 0NT3WX
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr01.00.00:bd08/07/2015:svnDellInc.:pnInspiron13-7359:pvr:rvnDellInc.:rn0NT3WX:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Inspiron 13-7359
  dmi.sys.vendor: Dell Inc.

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

-- 
Mailing list: https://launchpad.net/~kernel-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

[Kai-Heng Feng]

Let's focus on the freeze (nouveau) first. We can solve the docking
output (i915) later.

Can you confirm v4.11 freezes but v4.12-rc1 doesn't?

-- 
You 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 

[Kernel-packages] [Bug 1701499] Re: System often freezes or panics if I log in with Dell Dock WD15 connected

[Piotr Kołaczkowski]

No, after disabling apparmor for dhclient, I'm successfully running v4.14-rc2.
However, it looks like exactly the same problems exist with this kernel as with 
v4.14-rc2:

1. NetworkManager fails to connect automatically at startup, but
connects fine after manual intervention.

2. System fails to resume if it was disconnected from the dock while
suspended.

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

Title:
  System often freezes or panics if I log in with Dell Dock WD15
  connected

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I'm using Dell Precision 5520 with Ubuntu 17.04.

  If I first start a Unity session and then connect Dell WD15 USB-C dock
  with an external diplay plugged in, the system detects it properly and
  all the things work flawlessly (ethernet, external keyboard, external
  display, external storage connected to USB on the dock). I can plug-in
  and plug-out the dock multiple times and it just works.

  However if I boot the laptop with the dock already plugged in, first I
  get to the login screen and initially all is ok. Both screens are
  activated, and I can log in using the keyboard connected to the dock.

  When I hit "Enter", both screens go blank for a while, then they turn
  back on and I can see the desktop. A second or maybe two seconds later
  things start falling apart. When I move the mouse pointer a second
  after logging, it is kinda "jumpy", the movement is not smooth. The
  move freezes for a few times. I observed this behaviour only when
  moving the wireless mouse connected to the USB of the laptop. The
  builtin touchpad works smoothly.

  If it was the only issue, this would be a very minor annoyance.
  Sometimes, after a few short mouse pointer freezes the system starts
  working smoothly and all is rock stable from that point. However quite
  often I noticed much worse things happen:

  1. The mouse pointer and everything freezes totally after a few
  seconds from displaying the desktop. It is not possible to switch to
  the console with Ctrl-Alt-F1. This happens in >50% of logins.

  2. Kernel panic.

  I observed this behavior with stable Ubuntu kernel 4.10.0-20, as well
  as 4.11.0 - 4.11.8 (which I'm using now, because 4.11.x seems more
  stable than 4.10.0-x) and also 4.12.rc5 which I tried once.

  Even if everything goes fine, I noticed the following errors printed
  in syslog. I'm not sure if they are related, but they look very iffy
  to me:

  Jun 30 10:46:23 p5520 kernel: [   38.391971] DMAR: DRHD: handling fault 
status reg 2
  Jun 30 10:46:23 p5520 kernel: [   38.391977] DMAR: [INTR-REMAP] Request 
device [3e:00.0] fault index 1e [fault reason 38] Blocked an interrupt request 
due to source-id verification failure
  Jun 30 10:46:23 p5520 kernel: [   38.472490] xhci_hcd :0a:00.0: remove, 
state 1
  Jun 30 10:46:23 p5520 kernel: [   38.472496] usb usb4: USB disconnect, device 
number 1
  Jun 30 10:46:23 p5520 kernel: [   38.472497] usb 4-1: USB disconnect, device 
number 2
  Jun 30 10:46:23 p5520 kernel: [   38.472498] usb 4-1.2: USB disconnect, 
device number 3
  Jun 30 10:46:23 p5520 NetworkManager[1129]:   [1498812383.7510] device 
(eth0): state change: disconnected -> unmanaged (reason 'removed') [30 10 36]
  Jun 30 10:46:23 p5520 ModemManager[1076]:   (net/eth0): released by 
modem 
/sys/devices/pci:00/:00:1d.6/:06:00.0/:07:02.0/:0a:00.0/usb4/4-1/4-1.2
  Jun 30 10:46:23 p5520 NetworkManager[1129]:   [1498812383.7537] devices 
removed (path: 
/sys/devices/pci:00/:00:1d.6/:06:00.0/:07:02.0/:0a:00.0/usb4/4-1/4-1.2/4-1.2:1.0/net/eth0,
 iface: eth0)
  Jun 30 10:46:23 p5520 kernel: [   38.552718] xhci_hcd :0a:00.0: Host halt 
failed, -19
  Jun 30 10:46:23 p5520 kernel: [   38.552721] xhci_hcd :0a:00.0: Host not 
accessible, reset failed.
  Jun 30 10:46:23 p5520 kernel: [   38.552722] xhci_hcd :0a:00.0: USB bus 4 
deregistered
  Jun 30 10:46:23 p5520 kernel: [   38.552728] xhci_hcd :0a:00.0: remove, 
state 1
  Jun 30 10:46:23 p5520 kernel: [   38.552731] usb usb3: USB disconnect, device 
number 1
  Jun 30 10:46:23 p5520 kernel: [   38.552732] usb 3-1: USB disconnect, device 
number 2
  Jun 30 10:46:23 p5520 kernel: [   38.552732] usb 3-1.5: USB disconnect, 
device number 3
  Jun 30 10:46:23 p5520 kernel: [   38.553322] usb 3-1.7: USB disconnect, 
device number 4
  Jun 30 10:46:23 p5520 kernel: [   38.556064] BUG: unable to handle kernel 
paging request at 002018387ad8
  Jun 30 10:46:23 p5520 kernel: [   38.556173] IP: __radix_tree_lookup+0x10/0xf0
  Jun 30 10:46:23 p5520 kernel: [   38.556230] PGD 0 
  Jun 30 10:46:23 p5520 kernel: [   38.556232] 
  Jun 30 10:46:24 p5520 kernel: [   38.556280] Oops:  [#1] SMP
  Jun 30 10:46:24 p5520 kernel: [   38.556320] Modules linked in: ccm rfcomm 
cdc_ether usbnet snd_usb_audio snd_usbmidi_lib r8152 mii 

[Kernel-packages] [Bug 1716626] Re: linux: 3.19.0-93.101 -proposed tracker

[Po-Hsu Lin]

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

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

Title:
  linux: 3.19.0-93.101 -proposed tracker

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

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

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

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

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

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

[Kernel-packages] [Bug 1528684] Re: Error parsing PCC subspaces from PCCT

[PrPom.cz]

Same problem on Thinkpad L440, cannot even run Ubuntu, it crashes with this 
message on screen. Totally lost, have no clue, this discussion does not give a 
clear guide, what to do. 
Problem appeared all of a sudden, no new install, no dual boot.
Please help!!!

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

Title:
  Error parsing PCC subspaces from PCCT

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  On my Thinkpad laptop I am seeing this error every time after the boot
  in the dmesg output:

  "Error parsing PCC subspaces from PCCT" (Portable C Compiler)

  The attached log files should reveal more. I have no idea what it
  means but seems serious. Hope you can solve this for once and all?

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: linux-image-4.2.0-22-generic 4.2.0-22.27
  ProcVersionSignature: Ubuntu 4.2.0-22.27-generic 4.2.6
  Uname: Linux 4.2.0-22-generic x86_64
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  michael-heuberger   2972 F pulseaudio
   /dev/snd/controlC1:  michael-heuberger   2972 F pulseaudio
  Date: Wed Dec 23 09:36:44 2015
  HibernationDevice: RESUME=UUID=bb8b6759-8fdb-4e4b-879b-7701cb217d2a
  InstallationDate: Installed on 2015-05-22 (214 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: LENOVO 20A7006KAU
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-22-generic 
root=UUID=b2f035dd-f14c-4a64-8834-5116d2df7864 ro cgroup_enable=memory 
swapaccount=1
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-22-generic N/A
   linux-backports-modules-4.2.0-22-generic  N/A
   linux-firmware1.149.3
  SourcePackage: linux
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: Upgraded to wily on 2015-11-15 (36 days ago)
  dmi.bios.date: 11/20/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GRET42WW (1.19 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20A7006KAU
  dmi.board.vendor: LENOVO
  dmi.board.version: 0B98417 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrGRET42WW(1.19):bd11/20/2014:svnLENOVO:pn20A7006KAU:pvrThinkPadX1Carbon2nd:rvnLENOVO:rn20A7006KAU:rvr0B98417WIN:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 20A7006KAU
  dmi.product.version: ThinkPad X1 Carbon 2nd
  dmi.sys.vendor: LENOVO

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

-- 
Mailing list: https://launchpad.net/~kernel-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

[Kai-Heng Feng]

Now please go back to comment #3 to test kernel itself (again).

-- 
You 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) 

[Kernel-packages] [Bug 1701499] Re: System often freezes or panics if I log in with Dell Dock WD15 connected

[Kai-Heng Feng]

That's probably some AppArmor regression introduced in v4.14-rc2.

Do you still see "Severely broken stuffs" on v4.14-rc2?

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

Title:
  System often freezes or panics if I log in with Dell Dock WD15
  connected

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I'm using Dell Precision 5520 with Ubuntu 17.04.

  If I first start a Unity session and then connect Dell WD15 USB-C dock
  with an external diplay plugged in, the system detects it properly and
  all the things work flawlessly (ethernet, external keyboard, external
  display, external storage connected to USB on the dock). I can plug-in
  and plug-out the dock multiple times and it just works.

  However if I boot the laptop with the dock already plugged in, first I
  get to the login screen and initially all is ok. Both screens are
  activated, and I can log in using the keyboard connected to the dock.

  When I hit "Enter", both screens go blank for a while, then they turn
  back on and I can see the desktop. A second or maybe two seconds later
  things start falling apart. When I move the mouse pointer a second
  after logging, it is kinda "jumpy", the movement is not smooth. The
  move freezes for a few times. I observed this behaviour only when
  moving the wireless mouse connected to the USB of the laptop. The
  builtin touchpad works smoothly.

  If it was the only issue, this would be a very minor annoyance.
  Sometimes, after a few short mouse pointer freezes the system starts
  working smoothly and all is rock stable from that point. However quite
  often I noticed much worse things happen:

  1. The mouse pointer and everything freezes totally after a few
  seconds from displaying the desktop. It is not possible to switch to
  the console with Ctrl-Alt-F1. This happens in >50% of logins.

  2. Kernel panic.

  I observed this behavior with stable Ubuntu kernel 4.10.0-20, as well
  as 4.11.0 - 4.11.8 (which I'm using now, because 4.11.x seems more
  stable than 4.10.0-x) and also 4.12.rc5 which I tried once.

  Even if everything goes fine, I noticed the following errors printed
  in syslog. I'm not sure if they are related, but they look very iffy
  to me:

  Jun 30 10:46:23 p5520 kernel: [   38.391971] DMAR: DRHD: handling fault 
status reg 2
  Jun 30 10:46:23 p5520 kernel: [   38.391977] DMAR: [INTR-REMAP] Request 
device [3e:00.0] fault index 1e [fault reason 38] Blocked an interrupt request 
due to source-id verification failure
  Jun 30 10:46:23 p5520 kernel: [   38.472490] xhci_hcd :0a:00.0: remove, 
state 1
  Jun 30 10:46:23 p5520 kernel: [   38.472496] usb usb4: USB disconnect, device 
number 1
  Jun 30 10:46:23 p5520 kernel: [   38.472497] usb 4-1: USB disconnect, device 
number 2
  Jun 30 10:46:23 p5520 kernel: [   38.472498] usb 4-1.2: USB disconnect, 
device number 3
  Jun 30 10:46:23 p5520 NetworkManager[1129]:   [1498812383.7510] device 
(eth0): state change: disconnected -> unmanaged (reason 'removed') [30 10 36]
  Jun 30 10:46:23 p5520 ModemManager[1076]:   (net/eth0): released by 
modem 
/sys/devices/pci:00/:00:1d.6/:06:00.0/:07:02.0/:0a:00.0/usb4/4-1/4-1.2
  Jun 30 10:46:23 p5520 NetworkManager[1129]:   [1498812383.7537] devices 
removed (path: 
/sys/devices/pci:00/:00:1d.6/:06:00.0/:07:02.0/:0a:00.0/usb4/4-1/4-1.2/4-1.2:1.0/net/eth0,
 iface: eth0)
  Jun 30 10:46:23 p5520 kernel: [   38.552718] xhci_hcd :0a:00.0: Host halt 
failed, -19
  Jun 30 10:46:23 p5520 kernel: [   38.552721] xhci_hcd :0a:00.0: Host not 
accessible, reset failed.
  Jun 30 10:46:23 p5520 kernel: [   38.552722] xhci_hcd :0a:00.0: USB bus 4 
deregistered
  Jun 30 10:46:23 p5520 kernel: [   38.552728] xhci_hcd :0a:00.0: remove, 
state 1
  Jun 30 10:46:23 p5520 kernel: [   38.552731] usb usb3: USB disconnect, device 
number 1
  Jun 30 10:46:23 p5520 kernel: [   38.552732] usb 3-1: USB disconnect, device 
number 2
  Jun 30 10:46:23 p5520 kernel: [   38.552732] usb 3-1.5: USB disconnect, 
device number 3
  Jun 30 10:46:23 p5520 kernel: [   38.553322] usb 3-1.7: USB disconnect, 
device number 4
  Jun 30 10:46:23 p5520 kernel: [   38.556064] BUG: unable to handle kernel 
paging request at 002018387ad8
  Jun 30 10:46:23 p5520 kernel: [   38.556173] IP: __radix_tree_lookup+0x10/0xf0
  Jun 30 10:46:23 p5520 kernel: [   38.556230] PGD 0 
  Jun 30 10:46:23 p5520 kernel: [   38.556232] 
  Jun 30 10:46:24 p5520 kernel: [   38.556280] Oops:  [#1] SMP
  Jun 30 10:46:24 p5520 kernel: [   38.556320] Modules linked in: ccm rfcomm 
cdc_ether usbnet snd_usb_audio snd_usbmidi_lib r8152 mii snd_hda_codec_hdmi 
cmac msr uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 
videobuf2_core videodev media btusb btrtl joydev hid_multitouch ipmi_devintf 
ipmi_msghandler bnep nls_iso8859_1 arc4 dell_led snd_hda_codec_realtek 

[Kernel-packages] [Bug 1716301] Re: wifi driver: mt7601u not work on 16.04

[chenzero]

This time, the adapter is first recognized as 148f:7601.
and the dmesg output is some different. 

Although still can not find any interface by "ifconfig -a", and can not
select wifi in the "Network Manager", it's promosing to let the adapter
work, at least the GMS modem work now.

Please see the attached 17-09-26.txt

Thanks!


** Attachment added: "17-09-26.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1716301/+attachment/4957126/+files/17-09-26.txt

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/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]