[Kernel-packages] [Bug 1320659] Re: [Lenovo ThinkPad Edge E430] "thinkpad unsupported brightness interface" message is showing while booting up

[chenjun]

I also havbe the problem.I am using Ubuntu 14.04 64 bit with a Thinkpad
E545."thinkpad unsupported brightness interface" message is showing
while booting up.I think this problem because of our computer'GPU is
AMD.

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

Title:
  [Lenovo ThinkPad Edge E430] "thinkpad unsupported brightness
  interface" message is showing while booting up

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  While I have no actual problem with adjusting the brightness, I've noticed a 
message that displays while booting up:
  "thinkpad unsupported brightness interface"

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-24-generic 3.13.0-24.47
  ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tarunp 2026 F pulseaudio
  CurrentDesktop: Unity
  Date: Sun May 18 21:18:35 2014
  HibernationDevice: RESUME=UUID=7769c1de-f761-42a1-841a-41dd723f7046
  InstallationDate: Installed on 2014-04-21 (26 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  MachineType: LENOVO 3254T1Q
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic 
root=UUID=5d9a6cf6-1023-43f0-82b8-7df33d90132e ro acpi_osi=Linux quiet splash 
acpi_backlight=vendor vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-24-generic N/A
   linux-backports-modules-3.13.0-24-generic  N/A
   linux-firmware 1.127
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/22/2012
  dmi.bios.vendor: LENOVO
  dmi.bios.version: H0ET72WW (2.06 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 3254T1Q
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrH0ET72WW(2.06):bd10/22/2012:svnLENOVO:pn3254T1Q:pvrThinkPadEdgeE430:rvnLENOVO:rn3254T1Q:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 3254T1Q
  dmi.product.version: ThinkPad Edge E430
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1572801] Re: Ubuntu 16.04 Unity desktop uses much more ram than Ubuntu 15.10

[Thiago Martins]

Right after booting my 16.04 (now 16.10), before even logging into
Unity, I go to text console and log there...

32G of RAM being used! htop shows nothing...

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

Title:
  Ubuntu 16.04 Unity desktop uses much more ram than Ubuntu 15.10

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

Bug description:
  Ubuntu 16.04 64bit ISO number 20160420.1
  unity version 7.4.0+16.04.20160415-0ubuntu1
  Ubuntu 16.04 64bit ram usage has increase dramatically over Ubuntu 15.10
  Ubuntu 16.04 ram roughly 1 GB Ubuntu15.10 can be tuned to 420, 450 MB
  Ubuntu 16.04 with unity uses 1GB whereas Kubuntu 16.04 is using 420MB live usb

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: unity 7.4.0+16.04.20160415-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CasperVersion: 1.376
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Thu Apr 21 01:44:22 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics 
Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Xeon E3-1200 v3/4th Gen Core Processor 
Integrated Graphics Controller [1043:8534]
  GsettingsChanges:
   b'org.compiz.core' b'outputs' b"['1920x1080+0+0']"
   b'org.compiz.core' b'active-plugins' b"['core', 'composite', 'opengl', 
'place', 'regex', 'resize', 'session', 'snap', 'vpswitch', 'wall', 'animation', 
'commands', 'compiztoolbox', 'copytex', 'fade', 'grid', 'imgpng', 'mousepoll', 
'move', 'scale', 'unitymtgrabhandles', 'workarounds', 'expo', 'ezoom', 
'unityshell']"
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
   b'org.gnome.desktop.interface' b'scaling-factor' b'uint32 1'
  LiveMediaBuild: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
  MachineType: ASUS All Series
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi 
file=/cdrom/preseed/username.seed boot=casper quiet splash --- 
cdrom-detect/try-usb=true noprompt
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/03/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2004
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z87-PLUS
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2004:bd06/03/2014:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ87-PLUS:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: All Series
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS
  version.compiz: compiz 1:0.9.12.2+16.04.20160415-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Thu Apr 21 01:37:17 2016
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.18.3-1ubuntu2

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

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

[Kernel-packages] [Bug 1578916] Re: Hibernate not working on Ubuntu 16.04 LTS

[Christopher M. Penalver]

Sergio Ventura, it will help immensely if you filed a new report with the 
Ubuntu repository kernel (not mainline/upstream) via a terminal:
ubuntu-bug linux

Please feel free to subscribe me to it.

For more on why this is helpful, please see
https://wiki.ubuntu.com/ReportingBugs.

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

Title:
  Hibernate not working on Ubuntu 16.04 LTS

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hibernate is not working on Ubuntu 16.04 LTS for my HP Pavilion g6
  laptop.

  Laptop Specs:
  Processor: Intel Core i5 3210
  Chipset: B75 Express
  Graphics : Intel HD4000m / AMD 7670m
  RAM: 8 GB

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-21-generic 4.4.0-21.37 [modified: 
boot/vmlinuz-4.4.0-21-generic]
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  swapnil1853 F pulseaudio
  CurrentDesktop: Unity
  Date: Fri May  6 10:51:59 2016
  HibernationDevice: RESUME=UUID=8309f535-564b-475c-b049-f76cb4408140
  InstallationDate: Installed on 2016-05-01 (4 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Hewlett-Packard HP Pavilion g6 Notebook PC
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic.efi.signed 
root=UUID=b2f9e75c-9600-49b6-a701-69d38d7b910b ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-21-generic N/A
   linux-backports-modules-4.4.0-21-generic  N/A
   linux-firmware1.157
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/29/2013
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.25
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 183E
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 56.32
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.25:bd05/29/2013:svnHewlett-Packard:pnHPPaviliong6NotebookPC:pvr08841138591610100:rvnHewlett-Packard:rn183E:rvr56.32:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.name: HP Pavilion g6 Notebook PC
  dmi.product.version: 08841138591610100
  dmi.sys.vendor: Hewlett-Packard

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

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

[Kernel-packages] [Bug 1625794] Re: linux-lts-vivid: 3.19.0-70.78~14.04.1 -proposed tracker

[Brad Figg]

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

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

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

Title:
  linux-lts-vivid: 3.19.0-70.78~14.04.1 -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:
  Fix Released
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:
  Confirmed
Status in Kernel SRU Workflow promote-to-updates series:
  Confirmed
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux-lts-vivid package in Ubuntu:
  Invalid
Status in linux-lts-vivid source package in Trusty:
  Confirmed

Bug description:
  This bug is for tracking the 3.19.0-70.78~14.04.1 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
  derivative-trackers-created: true
  kernel-stable-master-bug: 1625788
  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/1625794/+subscriptions

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

[Kernel-packages] [Bug 1625788] Re: linux: 3.19.0-70.78 -proposed tracker

[Brad Figg]

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

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

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

Title:
  linux: 3.19.0-70.78 -proposed tracker

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

Bug description:
  This bug is for tracking the 3.19.0-70.78 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 --
  derivative-trackers-created: 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/1625788/+subscriptions

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

[Kernel-packages] [Bug 1625788] Re: linux: 3.19.0-70.78 -proposed tracker

[Yung Shen]

Couldn't fully finished certification-testing for this cycle, since
packages for Vivid are missing build dependencies.

** Changed in: kernel-sru-workflow/certification-testing
   Status: In Progress => 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/1625788

Title:
  linux: 3.19.0-70.78 -proposed tracker

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

Bug description:
  This bug is for tracking the 3.19.0-70.78 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 --
  derivative-trackers-created: 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/1625788/+subscriptions

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

[Kernel-packages] [Bug 1628204] Re: linux: 4.4.0-41.61 -proposed tracker

[Brad Figg]

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

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

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

Title:
  linux: 4.4.0-41.61 -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:
  Fix Released
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:
  Confirmed
Status in Kernel SRU Workflow promote-to-updates series:
  Confirmed
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Confirmed

Bug description:
  This bug is for tracking the 4.4.0-41.61 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
  derivative-trackers-created: 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/1628204/+subscriptions

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

[Kernel-packages] [Bug 1628204] Re: linux: 4.4.0-41.61 -proposed tracker

[Yung Shen]

Hardware Certification have completed testing this -proposed kernel. No
regressions were observed, results are available here:
http://people.canonical.com/~hwcert/sru-testing/xenial/4.4.0-41.61
/xenial-proposed-frozen.html

** Tags added: certification-testing-passed

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

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

Title:
  linux: 4.4.0-41.61 -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:
  Fix Released
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:
  Confirmed
Status in Kernel SRU Workflow promote-to-updates series:
  Confirmed
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Confirmed

Bug description:
  This bug is for tracking the 4.4.0-41.61 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
  derivative-trackers-created: 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/1628204/+subscriptions

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

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

[Brad Figg]

This change was made by a bot.

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

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

Title:
  System freezes

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  My system frequently freezes.  The screen is still displayed but no
  input is accepted from mouse or keyboard.  The only action available
  is to switch off and re-start.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: compiz 1:0.9.12.2+15.10.20151015-0ubuntu1
  ProcVersionSignature: Ubuntu 4.2.0-25.30-generic 4.2.6
  Uname: Linux 4.2.0-25-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Thu Jan 21 16:47:04 2016
  DistUpgraded: 2015-10-28 10:41:28,942 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
"./xorg_fix_proprietary.py" (No such file or directory) (8))
  DistroCodename: wily
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation Atom Processor Z36xxx/Z37xxx Series Graphics & Display 
[8086:0f31] (rev 0e) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Device [17aa:368d]
  InstallationDate: Installed on 2015-06-21 (214 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: LENOVO 90BX0018UK
  PackageArchitecture: all
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-25-generic.efi.signed 
root=UUID=2e321d15-1961-4c45-b1ce-7662ab1eee40 ro quiet splash vt.handoff=7
  SourcePackage: compiz
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: Upgraded to wily on 2015-10-28 (85 days ago)
  dmi.bios.date: 08/29/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: O07KT44AUS
  dmi.board.name: Aptio CRB
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0F82993 WIN
  dmi.chassis.type: 3
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrO07KT44AUS:bd08/29/2014:svnLENOVO:pn90BX0018UK:pvrLenovoE50-00:rvnLENOVO:rnAptioCRB:rvrSDK0F82993WIN:cvnLENOVO:ct3:cvrNone:
  dmi.product.name: 90BX0018UK
  dmi.product.version: Lenovo E50-00
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.12.2+15.10.20151015-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.64-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.2-1ubuntu4
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.2-1ubuntu4
  version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu9.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:7.5.0+git20150819-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20150808-0ubuntu4
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu3
  xserver.bootTime: Thu Jan 21 16:19:27 2016
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id 780 
   vendor ACR
  xserver.version: 2:1.17.2-1ubuntu9.1

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

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

[Kernel-packages] [Bug 1630970] Re: crypto/vmx/p8_ghash memory corruption

[Tim Gardner]

** Changed in: linux (Ubuntu Xenial)
   Status: Confirmed => Fix Committed

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

Title:
  crypto/vmx/p8_ghash memory corruption

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

Bug description:
  That bug was reported on the linux-crypto mailing list by Jan Stancek.
  The bug is not easily reproduced on Xenial because the crypto API test
  manager is not enabled and the hash test that exorcises this bug is
  not present on the Xenial kernel.

  ---
  Hi,

  I'm chasing a memory corruption with 4.8-rc7 as I'm observing random Oopses
  on ppc BE/LE systems (lpars, KVM guests). About 30% of issues is that
  module list gets corrupted, and "cat /proc/modules" or "lsmod" triggers
  an Oops, for example:

  [   88.486041] Unable to handle kernel paging request for data at address 
0x0020
  ...
  [   88.487658] NIP [c020f820] m_show+0xa0/0x240
  [   88.487689] LR [c020f834] m_show+0xb4/0x240
  [   88.487719] Call Trace:
  [   88.487736] [c004b605bbb0] [c020f834] m_show+0xb4/0x240 
(unreliable)
  [   88.487796] [c004b605bc50] [c045e73c] seq_read+0x36c/0x520
  [   88.487843] [c004b605bcf0] [c04e1014] proc_reg_read+0x84/0x120
  [   88.487889] [c004b605bd30] [c040df88] vfs_read+0xf8/0x380
  [   88.487934] [c004b605bde0] [c040fd40] SyS_read+0x60/0x110
  [   88.487981] [c004b605be30] [c0009590] system_call+0x38/0xec

  0x20 offset is module_use->source, module_use is NULL because 
module.source_list
  gets corrupted.

  The source of corruption appears to originate from a 'ahash' test for
  p8_ghash:

  cryptomgr_test
   alg_test
alg_test_hash
 test_hash
  __test_hash
   ahash_partial_update
shash_async_export
 memcpy

  With some extra traces [1], I'm seeing that ahash_partial_update() allocates 
56 bytes
  for 'state', and then crypto_ahash_export() writes 76 bytes into it:

  [5.970887] __test_hash alg name p8_ghash, result: c4333ac0, key: 
c004b860a500, req: c004b860a380
  [5.970963] state: c4333f00, statesize: 56
  [5.970995] shash_default_export memcpy c4333f00 c004b860a3e0, 
len: 76

  This seems to directly correspond with:
p8_ghash_alg.descsize = sizeof(struct p8_ghash_desc_ctx) == 56
shash_tfm->descsize = sizeof(struct p8_ghash_desc_ctx) + 
crypto_shash_descsize(fallback) == 56 + 20
  where 20 is presumably coming from "ghash_alg.descsize".

  My gut feeling was that these 2 should match, but I'd love to hear
  what crypto people think.

  Thank you,
  Jan
  ---

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

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

[Kernel-packages] [Bug 1630038] Re: thunder nic: avoid link delays due to RX_PACKET_DIS

[dann frazier]

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

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

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

** Changed in: linux (Ubuntu Xenial)
 Assignee: (unassigned) => dann frazier (dannf)

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

Title:
  thunder nic: avoid link delays due to RX_PACKET_DIS

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

Bug description:
  [Impact]
  Link establishment is delayed during initialization, possibly resulting in 
remote fault conditions that may cause the interface to fail to come up.

  [Test Case]
  Put the system in a reboot loop and watch for a remote fault condition, or a 
failure to bring up the link that can only be resolved by reloading the module.

  [Regression Risk]
  Patch is to a specific driver that is only used on Cavium ThunderX systems. 
The patch is upstream, so will have upstream support for regressions.

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

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

[Kernel-packages] [Bug 1536721] Re: System freezes

[Tony Pursell]

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

** No longer affects: compiz (Ubuntu)

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

Title:
  System freezes

Status in linux package in Ubuntu:
  New

Bug description:
  My system frequently freezes.  The screen is still displayed but no
  input is accepted from mouse or keyboard.  The only action available
  is to switch off and re-start.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: compiz 1:0.9.12.2+15.10.20151015-0ubuntu1
  ProcVersionSignature: Ubuntu 4.2.0-25.30-generic 4.2.6
  Uname: Linux 4.2.0-25-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Thu Jan 21 16:47:04 2016
  DistUpgraded: 2015-10-28 10:41:28,942 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
"./xorg_fix_proprietary.py" (No such file or directory) (8))
  DistroCodename: wily
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation Atom Processor Z36xxx/Z37xxx Series Graphics & Display 
[8086:0f31] (rev 0e) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Device [17aa:368d]
  InstallationDate: Installed on 2015-06-21 (214 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: LENOVO 90BX0018UK
  PackageArchitecture: all
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-25-generic.efi.signed 
root=UUID=2e321d15-1961-4c45-b1ce-7662ab1eee40 ro quiet splash vt.handoff=7
  SourcePackage: compiz
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: Upgraded to wily on 2015-10-28 (85 days ago)
  dmi.bios.date: 08/29/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: O07KT44AUS
  dmi.board.name: Aptio CRB
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0F82993 WIN
  dmi.chassis.type: 3
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrO07KT44AUS:bd08/29/2014:svnLENOVO:pn90BX0018UK:pvrLenovoE50-00:rvnLENOVO:rnAptioCRB:rvrSDK0F82993WIN:cvnLENOVO:ct3:cvrNone:
  dmi.product.name: 90BX0018UK
  dmi.product.version: Lenovo E50-00
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.12.2+15.10.20151015-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.64-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.2-1ubuntu4
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.2-1ubuntu4
  version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu9.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:7.5.0+git20150819-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20150808-0ubuntu4
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu3
  xserver.bootTime: Thu Jan 21 16:19:27 2016
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id 780 
   vendor ACR
  xserver.version: 2:1.17.2-1ubuntu9.1

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

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

[Kernel-packages] [Bug 1630970] Re: crypto/vmx/p8_ghash memory corruption

[Tim Gardner]

** Changed in: linux (Ubuntu Yakkety)
   Status: Confirmed => Fix Committed

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

Title:
  crypto/vmx/p8_ghash memory corruption

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

Bug description:
  That bug was reported on the linux-crypto mailing list by Jan Stancek.
  The bug is not easily reproduced on Xenial because the crypto API test
  manager is not enabled and the hash test that exorcises this bug is
  not present on the Xenial kernel.

  ---
  Hi,

  I'm chasing a memory corruption with 4.8-rc7 as I'm observing random Oopses
  on ppc BE/LE systems (lpars, KVM guests). About 30% of issues is that
  module list gets corrupted, and "cat /proc/modules" or "lsmod" triggers
  an Oops, for example:

  [   88.486041] Unable to handle kernel paging request for data at address 
0x0020
  ...
  [   88.487658] NIP [c020f820] m_show+0xa0/0x240
  [   88.487689] LR [c020f834] m_show+0xb4/0x240
  [   88.487719] Call Trace:
  [   88.487736] [c004b605bbb0] [c020f834] m_show+0xb4/0x240 
(unreliable)
  [   88.487796] [c004b605bc50] [c045e73c] seq_read+0x36c/0x520
  [   88.487843] [c004b605bcf0] [c04e1014] proc_reg_read+0x84/0x120
  [   88.487889] [c004b605bd30] [c040df88] vfs_read+0xf8/0x380
  [   88.487934] [c004b605bde0] [c040fd40] SyS_read+0x60/0x110
  [   88.487981] [c004b605be30] [c0009590] system_call+0x38/0xec

  0x20 offset is module_use->source, module_use is NULL because 
module.source_list
  gets corrupted.

  The source of corruption appears to originate from a 'ahash' test for
  p8_ghash:

  cryptomgr_test
   alg_test
alg_test_hash
 test_hash
  __test_hash
   ahash_partial_update
shash_async_export
 memcpy

  With some extra traces [1], I'm seeing that ahash_partial_update() allocates 
56 bytes
  for 'state', and then crypto_ahash_export() writes 76 bytes into it:

  [5.970887] __test_hash alg name p8_ghash, result: c4333ac0, key: 
c004b860a500, req: c004b860a380
  [5.970963] state: c4333f00, statesize: 56
  [5.970995] shash_default_export memcpy c4333f00 c004b860a3e0, 
len: 76

  This seems to directly correspond with:
p8_ghash_alg.descsize = sizeof(struct p8_ghash_desc_ctx) == 56
shash_tfm->descsize = sizeof(struct p8_ghash_desc_ctx) + 
crypto_shash_descsize(fallback) == 56 + 20
  where 20 is presumably coming from "ghash_alg.descsize".

  My gut feeling was that these 2 should match, but I'd love to hear
  what crypto people think.

  Thank you,
  Jan
  ---

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

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

[Kernel-packages] [Bug 1606178] Re: Can't suspend to ram, since linux3.11 and more

[xzu]

I finally found some help from a friend and he explain me what you're
waiting for. I think I'll can do that (or we), but that will take time.
Can't tell when.

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

Title:
  Can't suspend to ram, since linux3.11 and more

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I can't suspend to ram since linux 3.11, with ubuntu12.04. Older version 
(3.8, 3.5 etc..) suspend perfectly.
  So, I can't suspend with ubuntu 14.04 and 16.04. :(
  Solutions from here (specially test newer kernels) don't work for me: 
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1566302
  ASRock N68C-S UCC, with phenomIIx4 processor.

  ~$ uname -a
  Linux DDX-STUDIO 4.4.0-28-generic #47-Ubuntu SMP Fri Jun 24 10:09:13 UTC 2016 
x86_64 x86_64 x86_64 GNU/Linux


  ~$ sudo dmidecode -t baseboard
  # dmidecode 2.11
  SMBIOS 2.4 present.

  Handle 0x0002, DMI type 2, 15 bytes
  Base Board Information
Manufacturer: ASRock
Product Name: N68C-S UCC
Version:   
Serial Number:   
Asset Tag:   
Features:
Board is a hosting board
Board is replaceable
Location In Chassis:   
Chassis Handle: 0x0003
Type: Motherboard
Contained Object Handles: 0

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-28-generic 4.4.0-28.47
  ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13
  Uname: Linux 4.4.0-28-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/hwC1D0', 
'/dev/snd/pcmC1D3p', '/dev/snd/controlC1', '/dev/snd/by-path', 
'/dev/snd/pcmC0D1c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', 
'/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
  CurrentDesktop: XFCE
  Date: Mon Jul 25 12:00:17 2016
  HibernationDevice: RESUME=UUID=3d14e312-ebd4-4129-9183-dcb17519893d
  IwConfig:
   lono wireless extensions.
   
   enp0s7no wireless extensions.
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 004: ID 0810:0001 Personal Communication Systems, Inc. Dual 
PSX Adaptor
   Bus 002 Device 003: ID 058f:9360 Alcor Micro Corp. 8-in-1 Media Card Reader
   Bus 002 Device 002: ID 056a:00b2 Wacom Co., Ltd Intuos3 9x12
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-28-generic 
root=UUID=7411581c-dc6e-4be3-85ba-bf5ae0c61bbc ro splash quiet vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-28-generic N/A
   linux-backports-modules-4.4.0-28-generic  N/A
   linux-firmware1.157.2
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/19/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.60
  dmi.board.name: N68C-S UCC
  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.60:bd09/19/2011:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnN68C-SUCC: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/1606178/+subscriptions

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

[Kernel-packages] [Bug 1627108] Re: X1Carbon comes to a crawl during high CPU usage tasks

[Omer Akram]

As notified on on IRC, that is a good kernel.

The issue is easy to reproduce on an X1 Carbon just run `stress -c 4`
and within a few seconds mouse starts to lag and everything becomes
slow.

** Description changed:

  My X1Carbon becomes quite laggy, the cursor hangs for a few seconds and
  then resumes while my system is compiling some code, or lets says
  PyCharm is indexing things or Android Studio is compiling some code. I
  was using 4.4 on Xenial a few days ago and everything was working just
  fine. Installed Yakkety and this issue happens.
+ 
+ TEST CASE:
+ `stress -c 4` <-- that results in system slowness.
+ 
  
  I will downgrade the kernel and see if that mitigates the issue.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: linux-image-4.8.0-15-generic 4.8.0-15.16
  ProcVersionSignature: Ubuntu 4.8.0-15.16-generic 4.8.0-rc7
  Uname: Linux 4.8.0-15-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
-  USERPID ACCESS COMMAND
-  /dev/snd/pcmC1D0p:   om26er 3390 F...m pulseaudio
-  /dev/snd/controlC1:  om26er 3390 F pulseaudio
-  /dev/snd/controlC0:  om26er 3390 F pulseaudio
+  USERPID ACCESS COMMAND
+  /dev/snd/pcmC1D0p:   om26er 3390 F...m pulseaudio
+  /dev/snd/controlC1:  om26er 3390 F pulseaudio
+  /dev/snd/controlC0:  om26er 3390 F pulseaudio
  CurrentDesktop: Unity
  Date: Fri Sep 23 21:40:34 2016
  HibernationDevice: RESUME=UUID=a92c85ab-cca3-4afc-abf1-3516f193129e
  InstallationDate: Installed on 2016-09-21 (1 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160921)
  MachineType: LENOVO 20BSCTO1WW
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-15-generic.efi.signed 
root=UUID=01b0a4a0-d791-46e8-a212-1f769cff3a4b ro quiet splash vt.handoff=7
  RelatedPackageVersions:
-  linux-restricted-modules-4.8.0-15-generic N/A
-  linux-backports-modules-4.8.0-15-generic  N/A
-  linux-firmware1.161
+  linux-restricted-modules-4.8.0-15-generic N/A
+  linux-backports-modules-4.8.0-15-generic  N/A
+  linux-firmware1.161
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/13/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N14ET32W (1.10 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20BSCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN14ET32W(1.10):bd08/13/2015:svnLENOVO:pn20BSCTO1WW:pvrThinkPadX1Carbon3rd:rvnLENOVO:rn20BSCTO1WW:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.name: 20BSCTO1WW
  dmi.product.version: ThinkPad X1 Carbon 3rd
  dmi.sys.vendor: LENOVO

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

Title:
  X1Carbon comes to a crawl during high CPU usage tasks

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

Bug description:
  My X1Carbon becomes quite laggy, the cursor hangs for a few seconds
  and then resumes while my system is compiling some code, or lets says
  PyCharm is indexing things or Android Studio is compiling some code. I
  was using 4.4 on Xenial a few days ago and everything was working just
  fine. Installed Yakkety and this issue happens.

  TEST CASE:
  `stress -c 4` <-- that results in system slowness.

  
  I will downgrade the kernel and see if that mitigates the issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: linux-image-4.8.0-15-generic 4.8.0-15.16
  ProcVersionSignature: Ubuntu 4.8.0-15.16-generic 4.8.0-rc7
  Uname: Linux 4.8.0-15-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC1D0p:   om26er 3390 F...m pulseaudio
   /dev/snd/controlC1:  om26er 3390 F pulseaudio
   /dev/snd/controlC0:  om26er 3390 F pulseaudio
  CurrentDesktop: Unity
  Date: Fri Sep 23 21:40:34 2016
  HibernationDevice: RESUME=UUID=a92c85ab-cca3-4afc-abf1-3516f193129e
  InstallationDate: Installed on 2016-09-21 (1 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160921)
  MachineType: LENOVO 20BSCTO1WW
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-15-generic.efi.signed 
root=UUID=01b0a4a0-d791-46e8-a212-1f769cff3a4b ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-15-generic N/A
   linux-backports-modules-4.8.0-15-generic  N/A
   linux-firmware1.161
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/13/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 

[Kernel-packages] [Bug 1627108] Re: X1Carbon comes to a crawl during high CPU usage tasks

[Joseph Salisbury]

I built a Yakkety test kernel with a revert of commit
3d30544f02120b884bba2a9466c87dba980e3be5.  The test kernel can be
downloaded from:

http://kernel.ubuntu.com/~jsalisbury/lp1627108/

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

Note with this kernel, you need to install both the linux-image and
linux-image-extra .deb packages.

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

Title:
  X1Carbon comes to a crawl during high CPU usage tasks

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

Bug description:
  My X1Carbon becomes quite laggy, the cursor hangs for a few seconds
  and then resumes while my system is compiling some code, or lets says
  PyCharm is indexing things or Android Studio is compiling some code. I
  was using 4.4 on Xenial a few days ago and everything was working just
  fine. Installed Yakkety and this issue happens.

  I will downgrade the kernel and see if that mitigates the issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: linux-image-4.8.0-15-generic 4.8.0-15.16
  ProcVersionSignature: Ubuntu 4.8.0-15.16-generic 4.8.0-rc7
  Uname: Linux 4.8.0-15-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC1D0p:   om26er 3390 F...m pulseaudio
   /dev/snd/controlC1:  om26er 3390 F pulseaudio
   /dev/snd/controlC0:  om26er 3390 F pulseaudio
  CurrentDesktop: Unity
  Date: Fri Sep 23 21:40:34 2016
  HibernationDevice: RESUME=UUID=a92c85ab-cca3-4afc-abf1-3516f193129e
  InstallationDate: Installed on 2016-09-21 (1 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160921)
  MachineType: LENOVO 20BSCTO1WW
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-15-generic.efi.signed 
root=UUID=01b0a4a0-d791-46e8-a212-1f769cff3a4b ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-15-generic N/A
   linux-backports-modules-4.8.0-15-generic  N/A
   linux-firmware1.161
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/13/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N14ET32W (1.10 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20BSCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN14ET32W(1.10):bd08/13/2015:svnLENOVO:pn20BSCTO1WW:pvrThinkPadX1Carbon3rd:rvnLENOVO:rn20BSCTO1WW:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.name: 20BSCTO1WW
  dmi.product.version: ThinkPad X1 Carbon 3rd
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1627108] Re: X1Carbon comes to a crawl during high CPU usage tasks

[Joseph Salisbury]

The bisect reported this as the first bad commit:

commit 3d30544f02120b884bba2a9466c87dba980e3be5
Author: Peter Zijlstra 
Date:   Tue Jun 21 14:27:50 2016 +0200

sched/fair: Apply more PELT fixes

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

Title:
  X1Carbon comes to a crawl during high CPU usage tasks

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

Bug description:
  My X1Carbon becomes quite laggy, the cursor hangs for a few seconds
  and then resumes while my system is compiling some code, or lets says
  PyCharm is indexing things or Android Studio is compiling some code. I
  was using 4.4 on Xenial a few days ago and everything was working just
  fine. Installed Yakkety and this issue happens.

  I will downgrade the kernel and see if that mitigates the issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: linux-image-4.8.0-15-generic 4.8.0-15.16
  ProcVersionSignature: Ubuntu 4.8.0-15.16-generic 4.8.0-rc7
  Uname: Linux 4.8.0-15-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC1D0p:   om26er 3390 F...m pulseaudio
   /dev/snd/controlC1:  om26er 3390 F pulseaudio
   /dev/snd/controlC0:  om26er 3390 F pulseaudio
  CurrentDesktop: Unity
  Date: Fri Sep 23 21:40:34 2016
  HibernationDevice: RESUME=UUID=a92c85ab-cca3-4afc-abf1-3516f193129e
  InstallationDate: Installed on 2016-09-21 (1 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160921)
  MachineType: LENOVO 20BSCTO1WW
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-15-generic.efi.signed 
root=UUID=01b0a4a0-d791-46e8-a212-1f769cff3a4b ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-15-generic N/A
   linux-backports-modules-4.8.0-15-generic  N/A
   linux-firmware1.161
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/13/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N14ET32W (1.10 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20BSCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN14ET32W(1.10):bd08/13/2015:svnLENOVO:pn20BSCTO1WW:pvrThinkPadX1Carbon3rd:rvnLENOVO:rn20BSCTO1WW:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.name: 20BSCTO1WW
  dmi.product.version: ThinkPad X1 Carbon 3rd
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1631406] Re: Wrong memory.stat values in container root cgroup

[hda_launchpad]

I didn't use apport ether apport uninstalled on all my machines. And as
I already said in bug I have this on different machines with totally
different hardware.

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

Title:
  Wrong memory.stat values in container root cgroup

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  1) Ubuntu 16.04.1 LTS

  2) linux-image-4.4.0-41-generic, bug happens and first tested on
  4.4.0-38, happens in all versions, including from 4.4.0-38 to 4.4.0-41
  and possibly. See this bug on totally different xenial lts machines

  3) What you expected to happen:
  cat /sys/fs/cgroup/memory/lxc/containername/memory.stat should display 
correct information

  4) What happened instead
  cat /sys/fs/cgroup/memory/lxc/containername/memory.stat shows incorrect 
information
  cat /sys/fs/cgroup/memory/memory.stat in container shows different information
  lxc exec containername -- cat /sys/fs/cgroup/memory/memory.stat shows totally 
different information from two above. Meanwhile cat 
/sys/fs/cgroup/memory/lxc/containername/memory.usage_in_bytes is always correct.

  5) mount | grep cgroup output:
  tmpfs on /sys/fs/cgroup type tmpfs (rw,mode=755)
  cgroup on /sys/fs/cgroup/systemd type cgroup 
(rw,nosuid,nodev,noexec,relatime,xattr,release_agent=/lib/systemd/systemd-cgroups-agent,name=systemd)
  cgroup on /sys/fs/cgroup/cpu,cpuacct type cgroup 
(rw,nosuid,nodev,noexec,relatime,cpu,cpuacct)
  cgroup on /sys/fs/cgroup/perf_event type cgroup 
(rw,nosuid,nodev,noexec,relatime,perf_event,release_agent=/run/cgmanager/agents/cgm-release-agent.perf_event)
  cgroup on /sys/fs/cgroup/hugetlb type cgroup 
(rw,nosuid,nodev,noexec,relatime,hugetlb,release_agent=/run/cgmanager/agents/cgm-release-agent.hugetlb)
  cgroup on /sys/fs/cgroup/memory type cgroup 
(rw,nosuid,nodev,noexec,relatime,memory)
  cgroup on /sys/fs/cgroup/devices type cgroup 
(rw,nosuid,nodev,noexec,relatime,devices)
  cgroup on /sys/fs/cgroup/net_cls,net_prio type cgroup 
(rw,nosuid,nodev,noexec,relatime,net_cls,net_prio)
  cgroup on /sys/fs/cgroup/cpuset type cgroup 
(rw,nosuid,nodev,noexec,relatime,cpuset,clone_children)
  cgroup on /sys/fs/cgroup/freezer type cgroup 
(rw,nosuid,nodev,noexec,relatime,freezer)
  cgroup on /sys/fs/cgroup/pids type cgroup 
(rw,nosuid,nodev,noexec,relatime,pids,release_agent=/run/cgmanager/agents/cgm-release-agent.pids)
  cgroup on /sys/fs/cgroup/blkio type cgroup 
(rw,nosuid,nodev,noexec,relatime,blkio)

  6) I was able to reproduce the bug on another machine where memory.stat for 
container is correct  after removing this packages, but it makes no sense at 
all:
  mountall:amd64 plymouth-theme-ubuntu-text:amd64 plymouth:amd64 upstart:amd64
  Installing back didn't help.

  7) memory.stat information for programs running in containers is
  correct. Only memory.stat information for container root is incorrect.

  Bug graphical representation:
  
https://cloud.githubusercontent.com/assets/6484506/19012936/9f19ff7a-87b2-11e6-9e68-889659663249.png
  First chart is based on cat 
/sys/fs/cgroup/memory/lxc/containername/memory.usage_in_bytes and cat 
/sys/fs/cgroup/memory/lxc/containername/memsw_usage_in_bytes. Second chart 
based on incorrect cat /sys/fs/cgroup/memory/lxc/containername/memory.stat

  Possibly the same problems (bugs quite old):
  https://issues.apache.org/jira/browse/MESOS-758
  https://groups.google.com/forum/#!topic/linux.kernel/EwiYK53Itk8

  Bug original sources:
  https://github.com/firehol/netdata/issues/1019
  https://github.com/lxc/lxd/issues/2422

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

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

[Kernel-packages] [Bug 1631468] Re: Xenial update to v4.4.24 stable release

[Tim Gardner]

** Description changed:

+ SRU Justification
  
- SRU Justification
+ Impact:
+    The upstream process for stable tree updates is quite similar
+    in scope to the Ubuntu SRU process, e.g., each patch has to
+    demonstrably fix a bug, and each patch is vetted by upstream
+    by originating either directly from a mainline/stable Linux tree or
+    a minimally backported form of that patch. The v4.4.24 upstream stable
+    patch set is now available. It should be included in the Ubuntu
+    kernel as well.
  
- Impact:
-The upstream process for stable tree updates is quite similar
-in scope to the Ubuntu SRU process, e.g., each patch has to
-demonstrably fix a bug, and each patch is vetted by upstream
-by originating either directly from a mainline/stable Linux tree or
-a minimally backported form of that patch. The v4.4.24 upstream stable
-patch set is now available. It should be included in the Ubuntu
-kernel as well.
+    git://git.kernel.org/
  
-git://git.kernel.org/
+ TEST CASE: TBD
  
- TEST CASE: TBD
+    The following patches from the v4.4.24 stable release shall be
+ applied:
  
-The following patches from the v4.4.24 stable release shall be
- applied:
+ cpuset: handle race between CPU hotplug and cpuset_hotplug_work
+ mtd: nand: davinci: Reinitialize the HW ECC engine in 4bit hwctl
+ mm,ksm: fix endless looping in allocating memory when ksm enable
+ can: dev: fix deadlock reported after bus-off
+ x86/init: Fix cr4_init_shadow() on CR4-less machines
+ x86/boot: Initialize FPU and X86_FEATURE_ALWAYS even if we don't have CPUID
+ drm/nouveau/fifo/nv04: avoid ramht race against cookie insertion
+ drm/radeon/si/dpm: add workaround for for Jet parts
+ ARM: 8616/1: dt: Respect property size when parsing CPUs
+ ARM: 8617/1: dma: fix dma_max_pfn()
+ usb: musb: Fix DMA desired mode for Mentor DMA engine
+ usb: musb: fix DMA for host mode
+ iwlwifi: mvm: fix a few firmware capability checks
+ perf/core: Fix pmu::filter_match for SW-led groups
+ i40e: avoid null pointer dereference
+ pinctrl: uniphier: fix .pin_dbg_show() callback
+ pinctrl: Flag strict is a field in struct pinmux_ops
+ drivers/perf: arm_pmu: Fix leak in error path
+ mmc: pxamci: fix potential oops
+ tools/vm/slabinfo: fix an unintentional printf
+ ipvs: fix bind to link-local mcast IPv6 address in backup
+ nvmem: Declare nvmem_cell_read() consistently
+ hwmon: (adt7411) set bit 3 in CFG1 register
+ spi: sh-msiof: Avoid invalid clock generator parameters
+ iwlwifi: pcie: fix access to scratch buffer
+ iwlwifi: mvm: don't use ret when not initialised
+ ceph: fix race during filling readdir cache
+ usb: gadget: fsl_qe_udc: signedness bug in qe_get_frame()
+ gpio: sa1100: fix irq probing for ucb1x00
+ irqchip/gicv3: Silence noisy DEBUG_PER_CPU_MAPS warning
+ ARM: 8618/1: decompressor: reset ttbcr fields to use TTBR0 on ARMv7
+ arm64: debug: avoid resetting stepping state machine when TIF_SINGLESTEP
+ MIPS: uprobes: remove incorrect set_orig_insn
+ MIPS: fix uretprobe implementation
+ MIPS: Malta: Fix IOCU disable switch read for MIPS64
+ MIPS: uprobes: fix use of uninitialised variable
+ printk: fix parsing of "brl=" option
+ tpm: fix byte-order for the value read by tpm2_get_tpm_pt
+ regulator: qcom_spmi: Add support for S4 supply on pm8941
+ regulator: qcom_spmi: Add support for get_mode/set_mode on switches
+ regulator: qcom_spmi: Update mvs1/mvs2 switches on pm8941
+ regulator: qcom_smd: Fix voltage ranges for pm8x41
+ ARM: sun5i: Fix typo in trip point temperature
+ ARM: sa1100: register clocks early
+ ARM: sa1100: fix 3.6864MHz clock
+ ARM: sa1100: clear reset status prior to reboot
+ ARM: shmobile: fix regulator quirk for Gen2
+ ARM: sa: fix pcmcia suspend/resume
+ hwrng: omap - Fix assumption that runtime_get_sync will always succeed
+ blk-mq: actually hook up defer list when running requests
+ pstore: drop file opened reference count
+ tile: Define AT_VECTOR_SIZE_ARCH for ARCH_DLINFO
+ iwlmvm: mvm: set correct state in smart-fifo configuration
+ NFC: fdp: Detect errors from fdp_nci_create_conn()
+ em28xx-i2c: rt_mutex_trylock() returns zero on failure
+ gspca: avoid unused variable warnings
+ ath9k: Fix programming of minCCA power threshold
+ avr32: off by one in at32_init_pio()
+ fnic: pci_dma_mapping_error() doesn't return an error code
+ dmaengine: at_xdmac: fix debug string
+ svc: Avoid garbage replies when pc_func() returns rpc_drop_reply
+ NFS: Don't drop CB requests with invalid principals
+ pNFS/files: Fix layoutcommit after a commit to DS
+ pNFS/flexfiles: Fix layoutcommit after a commit to DS
+ ASoC: Intel: Skylake: Fix error return code in skl_probe()
+ brcmfmac: Fix glob_skb leak in brcmf_sdiod_recv_chain
+ brcmsmac: Free packet if dma_mapping_error() fails in dma_rxfill
+ brcmsmac: Initialize power in brcms_c_stf_ss_algo_channel_get()
+ powerpc/prom: Fix sub-processor option passed to 

[Kernel-packages] [Bug 1627108] Re: X1Carbon comes to a crawl during high CPU usage tasks

[Joseph Salisbury]

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

The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1627108/7dc603c9028ea5d4354e0e317e8481df99b06d7e

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

Title:
  X1Carbon comes to a crawl during high CPU usage tasks

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

Bug description:
  My X1Carbon becomes quite laggy, the cursor hangs for a few seconds
  and then resumes while my system is compiling some code, or lets says
  PyCharm is indexing things or Android Studio is compiling some code. I
  was using 4.4 on Xenial a few days ago and everything was working just
  fine. Installed Yakkety and this issue happens.

  I will downgrade the kernel and see if that mitigates the issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: linux-image-4.8.0-15-generic 4.8.0-15.16
  ProcVersionSignature: Ubuntu 4.8.0-15.16-generic 4.8.0-rc7
  Uname: Linux 4.8.0-15-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC1D0p:   om26er 3390 F...m pulseaudio
   /dev/snd/controlC1:  om26er 3390 F pulseaudio
   /dev/snd/controlC0:  om26er 3390 F pulseaudio
  CurrentDesktop: Unity
  Date: Fri Sep 23 21:40:34 2016
  HibernationDevice: RESUME=UUID=a92c85ab-cca3-4afc-abf1-3516f193129e
  InstallationDate: Installed on 2016-09-21 (1 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160921)
  MachineType: LENOVO 20BSCTO1WW
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-15-generic.efi.signed 
root=UUID=01b0a4a0-d791-46e8-a212-1f769cff3a4b ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-15-generic N/A
   linux-backports-modules-4.8.0-15-generic  N/A
   linux-firmware1.161
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/13/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N14ET32W (1.10 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20BSCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN14ET32W(1.10):bd08/13/2015:svnLENOVO:pn20BSCTO1WW:pvrThinkPadX1Carbon3rd:rvnLENOVO:rn20BSCTO1WW:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.name: 20BSCTO1WW
  dmi.product.version: ThinkPad X1 Carbon 3rd
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1631468] [NEW] Xenial update to v4.4.24 stable release

[Tim Gardner]

Public bug reported:


SRU Justification

Impact:
   The upstream process for stable tree updates is quite similar
   in scope to the Ubuntu SRU process, e.g., each patch has to
   demonstrably fix a bug, and each patch is vetted by upstream
   by originating either directly from a mainline/stable Linux tree or
   a minimally backported form of that patch. The v4.4.24 upstream stable
   patch set is now available. It should be included in the Ubuntu
   kernel as well.

   git://git.kernel.org/

TEST CASE: TBD

   The following patches from the v4.4.24 stable release shall be
applied:

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

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


** Tags: kernel-stable-tracking-bug

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

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

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

Title:
  Xenial update to v4.4.24 stable release

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

Bug description:
  
  SRU Justification

  Impact:
 The upstream process for stable tree updates is quite similar
 in scope to the Ubuntu SRU process, e.g., each patch has to
 demonstrably fix a bug, and each patch is vetted by upstream
 by originating either directly from a mainline/stable Linux tree or
 a minimally backported form of that patch. The v4.4.24 upstream stable
 patch set is now available. It should be included in the Ubuntu
 kernel as well.

 git://git.kernel.org/

  TEST CASE: TBD

 The following patches from the v4.4.24 stable release shall be
  applied:

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

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

[Kernel-packages] [Bug 1627108] Re: X1Carbon comes to a crawl during high CPU usage tasks

[Omer Akram]

As reported on IRC, that's a bad 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/1627108

Title:
  X1Carbon comes to a crawl during high CPU usage tasks

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

Bug description:
  My X1Carbon becomes quite laggy, the cursor hangs for a few seconds
  and then resumes while my system is compiling some code, or lets says
  PyCharm is indexing things or Android Studio is compiling some code. I
  was using 4.4 on Xenial a few days ago and everything was working just
  fine. Installed Yakkety and this issue happens.

  I will downgrade the kernel and see if that mitigates the issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: linux-image-4.8.0-15-generic 4.8.0-15.16
  ProcVersionSignature: Ubuntu 4.8.0-15.16-generic 4.8.0-rc7
  Uname: Linux 4.8.0-15-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC1D0p:   om26er 3390 F...m pulseaudio
   /dev/snd/controlC1:  om26er 3390 F pulseaudio
   /dev/snd/controlC0:  om26er 3390 F pulseaudio
  CurrentDesktop: Unity
  Date: Fri Sep 23 21:40:34 2016
  HibernationDevice: RESUME=UUID=a92c85ab-cca3-4afc-abf1-3516f193129e
  InstallationDate: Installed on 2016-09-21 (1 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160921)
  MachineType: LENOVO 20BSCTO1WW
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-15-generic.efi.signed 
root=UUID=01b0a4a0-d791-46e8-a212-1f769cff3a4b ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-15-generic N/A
   linux-backports-modules-4.8.0-15-generic  N/A
   linux-firmware1.161
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/13/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N14ET32W (1.10 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20BSCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN14ET32W(1.10):bd08/13/2015:svnLENOVO:pn20BSCTO1WW:pvrThinkPadX1Carbon3rd:rvnLENOVO:rn20BSCTO1WW:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.name: 20BSCTO1WW
  dmi.product.version: ThinkPad X1 Carbon 3rd
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1578916] Re: Hibernate not working on Ubuntu 16.04 LTS

[Sergio Ventura]

Hibernate does not work for me too on ubuntu 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/1578916

Title:
  Hibernate not working on Ubuntu 16.04 LTS

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hibernate is not working on Ubuntu 16.04 LTS for my HP Pavilion g6
  laptop.

  Laptop Specs:
  Processor: Intel Core i5 3210
  Chipset: B75 Express
  Graphics : Intel HD4000m / AMD 7670m
  RAM: 8 GB

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-21-generic 4.4.0-21.37 [modified: 
boot/vmlinuz-4.4.0-21-generic]
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  swapnil1853 F pulseaudio
  CurrentDesktop: Unity
  Date: Fri May  6 10:51:59 2016
  HibernationDevice: RESUME=UUID=8309f535-564b-475c-b049-f76cb4408140
  InstallationDate: Installed on 2016-05-01 (4 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Hewlett-Packard HP Pavilion g6 Notebook PC
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic.efi.signed 
root=UUID=b2f9e75c-9600-49b6-a701-69d38d7b910b ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-21-generic N/A
   linux-backports-modules-4.4.0-21-generic  N/A
   linux-firmware1.157
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/29/2013
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.25
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 183E
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 56.32
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.25:bd05/29/2013:svnHewlett-Packard:pnHPPaviliong6NotebookPC:pvr08841138591610100:rvnHewlett-Packard:rn183E:rvr56.32:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.name: HP Pavilion g6 Notebook PC
  dmi.product.version: 08841138591610100
  dmi.sys.vendor: Hewlett-Packard

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

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

[Kernel-packages] [Bug 1627108] Re: X1Carbon comes to a crawl during high CPU usage tasks

[Joseph Salisbury]

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

The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1627108/3d30544f02120b884bba2a9466c87dba980e3be5

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

Title:
  X1Carbon comes to a crawl during high CPU usage tasks

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

Bug description:
  My X1Carbon becomes quite laggy, the cursor hangs for a few seconds
  and then resumes while my system is compiling some code, or lets says
  PyCharm is indexing things or Android Studio is compiling some code. I
  was using 4.4 on Xenial a few days ago and everything was working just
  fine. Installed Yakkety and this issue happens.

  I will downgrade the kernel and see if that mitigates the issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: linux-image-4.8.0-15-generic 4.8.0-15.16
  ProcVersionSignature: Ubuntu 4.8.0-15.16-generic 4.8.0-rc7
  Uname: Linux 4.8.0-15-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC1D0p:   om26er 3390 F...m pulseaudio
   /dev/snd/controlC1:  om26er 3390 F pulseaudio
   /dev/snd/controlC0:  om26er 3390 F pulseaudio
  CurrentDesktop: Unity
  Date: Fri Sep 23 21:40:34 2016
  HibernationDevice: RESUME=UUID=a92c85ab-cca3-4afc-abf1-3516f193129e
  InstallationDate: Installed on 2016-09-21 (1 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160921)
  MachineType: LENOVO 20BSCTO1WW
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-15-generic.efi.signed 
root=UUID=01b0a4a0-d791-46e8-a212-1f769cff3a4b ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-15-generic N/A
   linux-backports-modules-4.8.0-15-generic  N/A
   linux-firmware1.161
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/13/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N14ET32W (1.10 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20BSCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN14ET32W(1.10):bd08/13/2015:svnLENOVO:pn20BSCTO1WW:pvrThinkPadX1Carbon3rd:rvnLENOVO:rn20BSCTO1WW:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.name: 20BSCTO1WW
  dmi.product.version: ThinkPad X1 Carbon 3rd
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1626436] Re: [4.8 regression] boot has become very slow

[Martin Pitt]

This could potentially be related to changes with cgroups -- creating
them did not cause any uevent in 4.4, but with 4.8 they do:

  sudo systemctl stop systemd-timesyncd
  udevadm monitor  -k  # in another terminal
  sudo systemctl start systemd-timesyncd

KERNEL[393.260769] add  
/kernel/slab/:atA-192/cgroup/dentry(1623:systemd-timesyncd.service) (cgroup)
KERNEL[393.261031] add  
/kernel/slab/inode_cache/cgroup/inode_cache(1623:systemd-timesyncd.service) 
(cgroup)
KERNEL[393.261850] add  
/kernel/slab/shmem_inode_cache/cgroup/shmem_inode_cache(1623:systemd-timesyncd.service)
 (cgroup)
KERNEL[393.262358] add  
/kernel/slab/:tA-192/cgroup/cred_jar(1623:systemd-timesyncd.service) 
(cgroup)
KERNEL[393.262636] add  
/kernel/slab/proc_inode_cache/cgroup/proc_inode_cache(1623:systemd-timesyncd.service)
 (cgroup)
KERNEL[393.452990] add  
/kernel/slab/:tA-0001024/cgroup/mm_struct(1623:systemd-timesyncd.service) 
(cgroup)
KERNEL[393.453082] add  
/kernel/slab/:tA-200/cgroup/vm_area_struct(1623:systemd-timesyncd.service) 
(cgroup)
KERNEL[393.453251] add  
/kernel/slab/:tA-064/cgroup/anon_vma_chain(1623:systemd-timesyncd.service) 
(cgroup)
KERNEL[393.453369] add  
/kernel/slab/anon_vma/cgroup/anon_vma(1623:systemd-timesyncd.service) (cgroup)
KERNEL[393.456909] add  
/kernel/slab/sock_inode_cache/cgroup/sock_inode_cache(1623:systemd-timesyncd.service)
 (cgroup)
KERNEL[393.457974] add  
/kernel/slab/:t-256/cgroup/kmalloc-256(1623:systemd-timesyncd.service) 
(cgroup)
KERNEL[393.458205] add  
/kernel/slab/:t-512/cgroup/kmalloc-512(1623:systemd-timesyncd.service) 
(cgroup)
KERNEL[393.460718] add  
/kernel/slab/:tA-0003648/cgroup/task_struct(1623:systemd-timesyncd.service) 
(cgroup)
KERNEL[393.462292] add  
/kernel/slab/:tA-128/cgroup/pid(1623:systemd-timesyncd.service) (cgroup)
KERNEL[393.465448] add  
/kernel/slab/:t-0001024/cgroup/kmalloc-1024(1623:systemd-timesyncd.service) 
(cgroup)

Which means that there will be a corresponding number of udev workers
running. At boot there is a *lot* of cgroup action due to lots of
services being started, while this is relatively quiet during runtime.
This is consistent with a slow boot but normal behaviour/feeling at
runtime.

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

Title:
  [4.8 regression] boot has become very slow

Status in linux package in Ubuntu:
  Triaged

Bug description:
  With yakkety's recent update from linux 4.4 to 4.8 booting has become
  a lot slower. It's not one service in particular, but without "quiet"
  and "splash" you can now easily read every single line instead of that
  whole wall of text zipping by. It now takes over 20s instead of ~10
  seconds to boot.

  This is even more dramatic when factoring out the recent boot hang of
  NetworkManager (bug 1622893) and disabling lightdm:

sudo systemctl mask NetworkManager NetworkManager-wait-online
  lightdm

  then booting with 4.4 takes 1.5s and with 4.8 19.5s (!).

  Some excerps from systemd-analyze blame:

  4.4:
 474ms postfix@-.service
 395ms lxd-containers.service
 305ms networking.service

  4.8:
4.578s postfix@-.service
7.300s lxd-containers.service
6.285s networking.service

  I attach the full outputs of critical-chain and analyze for 4.4 and
  4.8 for reference.

  
  This is much less noticeable in the running system. There is no immediate 
feeling of sluggishness (although my system is by and large idle).

  I compared the time of sbuilding colord under similar circumstances
  (-j4, building on tmpfs, thus no hard disk delays; running with fully
  pre-loaded apt-cacher-ng thus no random network delays), and with 4.4
  it takes 6.5 minutes and with 4.8 it takes 7.5. So that got a bit
  slower, but much less dramatically than during boot, so this is either
  happening when a lot of processes run in parallel, or is perhaps
  related to setting up cgroups.

  One thing I noticed that during sbuild in 4.8 "top" shows ridiculous
  loads (~ 250) under 4.8, while it's around 4 or 5 under 4.8. But that
  doesn't reflect in actual sluggishness, so this might be just an
  unrelated bug.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: linux-image-4.8.0-11-generic 4.8.0-11.12
  ProcVersionSignature: Ubuntu 4.8.0-11.12-generic 4.8.0-rc6
  Uname: Linux 4.8.0-11-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   martin 3049 F...m pulseaudio
   /dev/snd/pcmC0D0p:   martin 3049 F...m pulseaudio
   /dev/snd/controlC0:  martin 3049 F pulseaudio
  Date: Thu Sep 22 09:42:56 2016
  EcryptfsInUse: Yes
  MachineType: LENOVO 2324CTO
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   

[Kernel-packages] [Bug 1626436] Re: [4.8 regression] boot has become very slow

[Martin Pitt]

For the record, I tried Joseph's test bisect kernel in bug 1627108, and
this does not fix it, so this is not a duplicate of bug 1627108:

4.4.0-9136 (previous yakkety): 2.849s (kernel) + 4.639s (userspace)
4.8.0-19 (current yakkety): 5.145s (kernel) + 11.825s (userspace)
4.7.0-040700rc3 (from Joseph): 3.735s (kernel) + 14.810s (userspace)

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

Title:
  [4.8 regression] boot has become very slow

Status in linux package in Ubuntu:
  Triaged

Bug description:
  With yakkety's recent update from linux 4.4 to 4.8 booting has become
  a lot slower. It's not one service in particular, but without "quiet"
  and "splash" you can now easily read every single line instead of that
  whole wall of text zipping by. It now takes over 20s instead of ~10
  seconds to boot.

  This is even more dramatic when factoring out the recent boot hang of
  NetworkManager (bug 1622893) and disabling lightdm:

sudo systemctl mask NetworkManager NetworkManager-wait-online
  lightdm

  then booting with 4.4 takes 1.5s and with 4.8 19.5s (!).

  Some excerps from systemd-analyze blame:

  4.4:
 474ms postfix@-.service
 395ms lxd-containers.service
 305ms networking.service

  4.8:
4.578s postfix@-.service
7.300s lxd-containers.service
6.285s networking.service

  I attach the full outputs of critical-chain and analyze for 4.4 and
  4.8 for reference.

  
  This is much less noticeable in the running system. There is no immediate 
feeling of sluggishness (although my system is by and large idle).

  I compared the time of sbuilding colord under similar circumstances
  (-j4, building on tmpfs, thus no hard disk delays; running with fully
  pre-loaded apt-cacher-ng thus no random network delays), and with 4.4
  it takes 6.5 minutes and with 4.8 it takes 7.5. So that got a bit
  slower, but much less dramatically than during boot, so this is either
  happening when a lot of processes run in parallel, or is perhaps
  related to setting up cgroups.

  One thing I noticed that during sbuild in 4.8 "top" shows ridiculous
  loads (~ 250) under 4.8, while it's around 4 or 5 under 4.8. But that
  doesn't reflect in actual sluggishness, so this might be just an
  unrelated bug.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: linux-image-4.8.0-11-generic 4.8.0-11.12
  ProcVersionSignature: Ubuntu 4.8.0-11.12-generic 4.8.0-rc6
  Uname: Linux 4.8.0-11-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   martin 3049 F...m pulseaudio
   /dev/snd/pcmC0D0p:   martin 3049 F...m pulseaudio
   /dev/snd/controlC0:  martin 3049 F pulseaudio
  Date: Thu Sep 22 09:42:56 2016
  EcryptfsInUse: Yes
  MachineType: LENOVO 2324CTO
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.8.0-11-generic.efi.signed 
root=UUID=f86539b0-3a1b-4372-83b0-acdd029ade68 ro rootflags=subvol=@ 
systemd.debug-shell
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-11-generic N/A
   linux-backports-modules-4.8.0-11-generic  N/A
   linux-firmware1.161
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/09/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G2ET95WW (2.55 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2324CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: 0B98401 Pro
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG2ET95WW(2.55):bd07/09/2013:svnLENOVO:pn2324CTO:pvrThinkPadX230:rvnLENOVO:rn2324CTO:rvr0B98401Pro:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 2324CTO
  dmi.product.version: ThinkPad X230
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1627108] Re: X1Carbon comes to a crawl during high CPU usage tasks

[Martin Pitt]

FTR, I tested #29 which works for Omer, but not for me, so bug 1626436
is not a duplicate.

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

Title:
  X1Carbon comes to a crawl during high CPU usage tasks

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

Bug description:
  My X1Carbon becomes quite laggy, the cursor hangs for a few seconds
  and then resumes while my system is compiling some code, or lets says
  PyCharm is indexing things or Android Studio is compiling some code. I
  was using 4.4 on Xenial a few days ago and everything was working just
  fine. Installed Yakkety and this issue happens.

  I will downgrade the kernel and see if that mitigates the issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: linux-image-4.8.0-15-generic 4.8.0-15.16
  ProcVersionSignature: Ubuntu 4.8.0-15.16-generic 4.8.0-rc7
  Uname: Linux 4.8.0-15-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC1D0p:   om26er 3390 F...m pulseaudio
   /dev/snd/controlC1:  om26er 3390 F pulseaudio
   /dev/snd/controlC0:  om26er 3390 F pulseaudio
  CurrentDesktop: Unity
  Date: Fri Sep 23 21:40:34 2016
  HibernationDevice: RESUME=UUID=a92c85ab-cca3-4afc-abf1-3516f193129e
  InstallationDate: Installed on 2016-09-21 (1 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160921)
  MachineType: LENOVO 20BSCTO1WW
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-15-generic.efi.signed 
root=UUID=01b0a4a0-d791-46e8-a212-1f769cff3a4b ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-15-generic N/A
   linux-backports-modules-4.8.0-15-generic  N/A
   linux-firmware1.161
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/13/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N14ET32W (1.10 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20BSCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN14ET32W(1.10):bd08/13/2015:svnLENOVO:pn20BSCTO1WW:pvrThinkPadX1Carbon3rd:rvnLENOVO:rn20BSCTO1WW:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.name: 20BSCTO1WW
  dmi.product.version: ThinkPad X1 Carbon 3rd
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1530405] Re: NMI watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [kerneloops:814]

[asimsalam]

Like Frederick Astacio, I see this every time I shutdown the laptop. I am 
running elementary OS, which is a Ubuntu derivative.
Is there an ETA for the fix?

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

Title:
  NMI watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [kerneloops:814]

Status in linux package in Ubuntu:
  Triaged

Bug description:
  I'm using Ubuntu Xenial 16.04 and my computer (ASUS M32BF) will
  randomly freeze up, sometimes before the login screen, sometimes while
  I'm in the middle of using a program. This sometimes happens on the
  Wily 15.10 live cd as well, and on both kernel 4.3.0-2, and kernel
  4.2.0-22.

  Important part of log:

  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112129] NMI watchdog: BUG: soft 
lockup - CPU#0 stuck for 22s! [kerneloops:814]
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112134] Modules linked in: rfcomm 
bnep nls_iso8859_1 kvm_amd kvm eeepc_wmi asus_wmi crct10dif_pclmul 
sparse_keymap crc32_pclmul aesni_intel aes_x86_64 arc4 lrw gf128mul rtl8821ae 
glue_helper snd_hda_codec_realtek ablk_helper snd_hda_codec_generic 
snd_hda_codec_hdmi snd_hda_intel btcoexist snd_hda_codec rtl_pci snd_hda_core 
joydev input_leds snd_hwdep rtlwifi snd_pcm fam15h_power cryptd snd_seq_midi 
serio_raw snd_seq_midi_event snd_rawmidi mac80211 snd_seq snd_seq_device 
snd_timer cfg80211 btusb btrtl btbcm btintel bluetooth snd soundcore 
edac_mce_amd k10temp edac_core i2c_piix4 shpchp mac_hid parport_pc ppdev lp 
parport autofs4 hid_logitech_hidpp uas usb_storage hid_logitech_dj usbhid hid 
amdkfd amd_iommu_v2 radeon i2c_algo_bit ttm drm_kms_helper syscopyarea 
sysfillrect sysimgblt fb_sys_fops r8169 psmouse mii drm ahci libahci wmi fjes 
video
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112183] CPU: 0 PID: 814 Comm: 
kerneloops Not tainted 4.3.0-2-generic #11-Ubuntu
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112184] Hardware name: ASUSTeK 
COMPUTER INC. K30BF_M32BF_A_F_K31BF_6/K30BF_M32BF_A_F_K31BF_6, BIOS 0501 
07/09/2015
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112186] task: 88031146d400 
ti: 88030e838000 task.ti: 88030e838000
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112188] RIP: 
0010:[]  [] __do_softirq+0x76/0x250
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112194] RSP: 
0018:88031fc03f30  EFLAGS: 0202
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112196] RAX: 88030e83c000 
RBX:  RCX: 40400040
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112197] RDX:  
RSI: 613e RDI: 0380
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112198] RBP: 88031fc03f80 
R08: 0029f8fa1411 R09: 88031fc169f0
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112199] R10: 0020 
R11: 0004 R12: 88031fc169c0
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112201] R13: 88030df8e200 
R14:  R15: 0001
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112202] FS:  
7f6c266ac880() GS:88031fc0() knlGS:
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112203] CS:  0010 DS:  ES: 
 CR0: 80050033
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112205] CR2: 7ffef000bff8 
CR3: 00030f368000 CR4: 000406f0
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112206] Stack:
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112207]  404000401fc03f78 
88030e83c000 0121 8803000a
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112209]  00021fc0d640 
 88031fc169c0 88030df8e200
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112211]   
0001 88031fc03f90 81081d23
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112213] Call Trace:
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112215]   
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112219]  [] 
irq_exit+0xa3/0xb0
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.11]  [] 
smp_apic_timer_interrupt+0x42/0x50
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112225]  [] 
apic_timer_interrupt+0x82/0x90
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112226]   
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112230]  [] ? 
finish_task_switch+0x67/0x1c0
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112232]  [] 
__schedule+0x36c/0x980
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112234]  [] 
schedule+0x33/0x80
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112236]  [] 
do_nanosleep+0x6f/0xf0
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112239]  [] 
hrtimer_nanosleep+0xdc/0x1f0
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112241]  [] ? 
__hrtimer_init+0x90/0x90
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112243]  [] ? 
do_nanosleep+0x5a/0xf0
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112245]  [] 
SyS_nanosleep+0x7a/0x90
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112247]  

[Kernel-packages] [Bug 1627108] Re: X1Carbon comes to a crawl during high CPU usage tasks

[Joseph Salisbury]

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

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

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

Title:
  X1Carbon comes to a crawl during high CPU usage tasks

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

Bug description:
  My X1Carbon becomes quite laggy, the cursor hangs for a few seconds
  and then resumes while my system is compiling some code, or lets says
  PyCharm is indexing things or Android Studio is compiling some code. I
  was using 4.4 on Xenial a few days ago and everything was working just
  fine. Installed Yakkety and this issue happens.

  I will downgrade the kernel and see if that mitigates the issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: linux-image-4.8.0-15-generic 4.8.0-15.16
  ProcVersionSignature: Ubuntu 4.8.0-15.16-generic 4.8.0-rc7
  Uname: Linux 4.8.0-15-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC1D0p:   om26er 3390 F...m pulseaudio
   /dev/snd/controlC1:  om26er 3390 F pulseaudio
   /dev/snd/controlC0:  om26er 3390 F pulseaudio
  CurrentDesktop: Unity
  Date: Fri Sep 23 21:40:34 2016
  HibernationDevice: RESUME=UUID=a92c85ab-cca3-4afc-abf1-3516f193129e
  InstallationDate: Installed on 2016-09-21 (1 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160921)
  MachineType: LENOVO 20BSCTO1WW
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-15-generic.efi.signed 
root=UUID=01b0a4a0-d791-46e8-a212-1f769cff3a4b ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-15-generic N/A
   linux-backports-modules-4.8.0-15-generic  N/A
   linux-firmware1.161
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/13/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N14ET32W (1.10 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20BSCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN14ET32W(1.10):bd08/13/2015:svnLENOVO:pn20BSCTO1WW:pvrThinkPadX1Carbon3rd:rvnLENOVO:rn20BSCTO1WW:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.name: 20BSCTO1WW
  dmi.product.version: ThinkPad X1 Carbon 3rd
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1559194] linux-image-4.4.0-33.52+_4.4.0-33.52+-6_s390x.deb

[bugproxy]

--- Comment on attachment From geral...@de.ibm.com 2016-09-06 10:25 
EDT---


Debian kernel package with genwqe-bad-page.patch applied.

** Attachment added: "linux-image-4.4.0-33.52+_4.4.0-33.52+-6_s390x.deb"
   
https://bugs.launchpad.net/bugs/1559194/+attachment/4756818/+files/linux-image-4.4.0-33.52+_4.4.0-33.52+-6_s390x.deb

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

Title:
  Bad page state in process genwqe_gunzip pfn:3c275 in the genwqe device
  driver

Status in Release Notes for Ubuntu:
  Fix Released
Status in Ubuntu on IBM z Systems:
  Fix Released
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Xenial:
  In Progress
Status in linux source package in Yakkety:
  In Progress

Bug description:
  == Comment: #0 - Dmitry Gorbachev  - 2016-03-17 
08:52:41 ==
  An error occurs when running zEDC compression/decompression and hotplugging 
PCI devices.
  There was 1G of memory, 2 pci functions and 50 threads of gunzipping enabled.

  Mar 14 23:59:01 s8330018 kernel: [ 4972.486883] BUG: Bad page state in 
process genwqe_gunzip  pfn:3c275
  Mar 14 23:59:01 s8330018 kernel: [ 4972.486888] page:03d100f09d40 
count:-1 mapcount:0 mapping:  (null) index:0x0
  Mar 14 23:59:01 s8330018 kernel: [ 4972.486891] flags: 0x0()
  Mar 14 23:59:01 s8330018 kernel: [ 4972.486895] page dumped because: nonzero 
_count
  Mar 14 23:59:01 s8330018 kernel: [ 4972.486897] Modules linked in: 
xt_CHECKSUM(E) iptable_mangle(E) ipt_MASQUERADE(E) nf_nat_masquerade_ipv4(E) 
iptable_nat(E) nf_conntrack_ipv4(E) nf_defrag_ipv4(E) nf_nat_ipv4(E) nf_nat(E) 
nf_conntrack(E) xt_tcpudp(E) bridge(E) stp(E) llc(E) iptable_filter(E) 
ip_tables(E) x_tables(E) genwqe_card(E) crc_itu_t(E) qeth_l2(E) qeth(E) vmur(E) 
ccwgroup(E) dm_multipath(E) ib_iser(E) rdma_cm(E) iw_cm(E) ib_cm(E) ib_sa(E) 
ib_mad(E) ib_core(E) ib_addr(E) iscsi_tcp(E) libiscsi_tcp(E) libiscsi(E) 
scsi_transport_iscsi(E) btrfs(E) zlib_deflate(E) raid10(E) raid456(E) 
async_memcpy(E) async_raid6_recov(E) async_pq(E) async_xor(E) async_tx(E) 
xor(E) raid6_pq(E) libcrc32c(E) raid1(E) raid0(E) linear(E) ghash_s390(E) 
prng(E) aes_s390(E) des_s390(E) des_generic(E) sha512_s390(E) sha256_s390(E) 
sha1_s390(E) sha_common(E) zfcp(E) qdio(E) scsi_transport_fc(E) 
dasd_eckd_mod(E) dasd_mod(E)
  Mar 14 23:59:01 s8330018 kernel: [ 4972.486916] CPU: 0 PID: 37867 Comm: 
genwqe_gunzip Tainted: GW   E   4.4.0-8-generic #23-Ubuntu
  Mar 14 23:59:01 s8330018 kernel: [ 4972.486916]209176f8 
20917788 0002 
  Mar 14 23:59:01 s8330018 kernel: [ 4972.486916]20917828 
209177a0 209177a0 00114182
  Mar 14 23:59:01 s8330018 kernel: [ 4972.486916]0011 
0092345a 03d1000a 000a
  Mar 14 23:59:01 s8330018 kernel: [ 4972.486916]209177e8 
20917788  20914000
  Mar 14 23:59:01 s8330018 kernel: [ 4972.486916] 
00114182 20917788 209177e8
  Mar 14 23:59:01 s8330018 kernel: [ 4972.486922] Call Trace:
  Mar 14 23:59:01 s8330018 kernel: [ 4972.486927] ([<0011406e>] 
show_trace+0xf6/0x148)
  Mar 14 23:59:01 s8330018 kernel: [ 4972.486929]  [<00114136>] 
show_stack+0x76/0xe8
  Mar 14 23:59:01 s8330018 kernel: [ 4972.486934]  [<00518c26>] 
dump_stack+0x6e/0x90
  Mar 14 23:59:01 s8330018 kernel: [ 4972.486937]  [<0027c376>] 
bad_page+0xe6/0x148
  Mar 14 23:59:01 s8330018 kernel: [ 4972.486938]  [<00280516>] 
get_page_from_freelist+0x49e/0xba8
  Mar 14 23:59:01 s8330018 kernel: [ 4972.486940]  [<00280ede>] 
__alloc_pages_nodemask+0x166/0xb00
  Mar 14 23:59:01 s8330018 kernel: [ 4972.486941]  [<0015635a>] 
s390_dma_alloc+0x82/0x1a0
  Mar 14 23:59:01 s8330018 kernel: [ 4972.486944]  [<03ff805ea142>] 
__genwqe_alloc_consistent+0x7a/0x90 [genwqe_card]
  Mar 14 23:59:01 s8330018 kernel: [ 4972.486947]  [<03ff805ea344>] 
genwqe_alloc_sync_sgl+0x17c/0x2e0 [genwqe_card]
  Mar 14 23:59:01 s8330018 kernel: [ 4972.486950]  [<03ff805e52da>] 
do_execute_ddcb+0x1da/0x348 [genwqe_card]
  Mar 14 23:59:01 s8330018 kernel: [ 4972.486952]  [<03ff805e5964>] 
genwqe_ioctl+0x51c/0xc20 [genwqe_card]
  Mar 14 23:59:01 s8330018 kernel: [ 4972.486953]  [<003145ee>] 
do_vfs_ioctl+0x3b6/0x518
  Mar 14 23:59:01 s8330018 kernel: [ 4972.486955]  [<003147f4>] 
SyS_ioctl+0xa4/0xb8
  Mar 14 23:59:01 s8330018 kernel: [ 4972.486956]  [<007ad1be>] 
system_call+0xd6/0x264
  Mar 14 23:59:01 s8330018 kernel: [ 4972.486957]  [<03ffa9df2492>] 
0x3ffa9df2492

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-release-notes/+bug/1559194/+subscriptions

-- 
Mailing list: 

[Kernel-packages] [Bug 1559194] linux-image-4.4.0-33.52+_4.4.0-33.52+-6_s390x.deb

[bugproxy]

Default Comment by Bridge

** Attachment added: "linux-image-4.4.0-33.52+_4.4.0-33.52+-6_s390x.deb"
   
https://bugs.launchpad.net/bugs/1559194/+attachment/4756819/+files/linux-image-4.4.0-33.52__4.4.0-33.52_-6_s390x.deb

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

Title:
  Bad page state in process genwqe_gunzip pfn:3c275 in the genwqe device
  driver

Status in Release Notes for Ubuntu:
  Fix Released
Status in Ubuntu on IBM z Systems:
  Fix Released
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Xenial:
  In Progress
Status in linux source package in Yakkety:
  In Progress

Bug description:
  == Comment: #0 - Dmitry Gorbachev  - 2016-03-17 
08:52:41 ==
  An error occurs when running zEDC compression/decompression and hotplugging 
PCI devices.
  There was 1G of memory, 2 pci functions and 50 threads of gunzipping enabled.

  Mar 14 23:59:01 s8330018 kernel: [ 4972.486883] BUG: Bad page state in 
process genwqe_gunzip  pfn:3c275
  Mar 14 23:59:01 s8330018 kernel: [ 4972.486888] page:03d100f09d40 
count:-1 mapcount:0 mapping:  (null) index:0x0
  Mar 14 23:59:01 s8330018 kernel: [ 4972.486891] flags: 0x0()
  Mar 14 23:59:01 s8330018 kernel: [ 4972.486895] page dumped because: nonzero 
_count
  Mar 14 23:59:01 s8330018 kernel: [ 4972.486897] Modules linked in: 
xt_CHECKSUM(E) iptable_mangle(E) ipt_MASQUERADE(E) nf_nat_masquerade_ipv4(E) 
iptable_nat(E) nf_conntrack_ipv4(E) nf_defrag_ipv4(E) nf_nat_ipv4(E) nf_nat(E) 
nf_conntrack(E) xt_tcpudp(E) bridge(E) stp(E) llc(E) iptable_filter(E) 
ip_tables(E) x_tables(E) genwqe_card(E) crc_itu_t(E) qeth_l2(E) qeth(E) vmur(E) 
ccwgroup(E) dm_multipath(E) ib_iser(E) rdma_cm(E) iw_cm(E) ib_cm(E) ib_sa(E) 
ib_mad(E) ib_core(E) ib_addr(E) iscsi_tcp(E) libiscsi_tcp(E) libiscsi(E) 
scsi_transport_iscsi(E) btrfs(E) zlib_deflate(E) raid10(E) raid456(E) 
async_memcpy(E) async_raid6_recov(E) async_pq(E) async_xor(E) async_tx(E) 
xor(E) raid6_pq(E) libcrc32c(E) raid1(E) raid0(E) linear(E) ghash_s390(E) 
prng(E) aes_s390(E) des_s390(E) des_generic(E) sha512_s390(E) sha256_s390(E) 
sha1_s390(E) sha_common(E) zfcp(E) qdio(E) scsi_transport_fc(E) 
dasd_eckd_mod(E) dasd_mod(E)
  Mar 14 23:59:01 s8330018 kernel: [ 4972.486916] CPU: 0 PID: 37867 Comm: 
genwqe_gunzip Tainted: GW   E   4.4.0-8-generic #23-Ubuntu
  Mar 14 23:59:01 s8330018 kernel: [ 4972.486916]209176f8 
20917788 0002 
  Mar 14 23:59:01 s8330018 kernel: [ 4972.486916]20917828 
209177a0 209177a0 00114182
  Mar 14 23:59:01 s8330018 kernel: [ 4972.486916]0011 
0092345a 03d1000a 000a
  Mar 14 23:59:01 s8330018 kernel: [ 4972.486916]209177e8 
20917788  20914000
  Mar 14 23:59:01 s8330018 kernel: [ 4972.486916] 
00114182 20917788 209177e8
  Mar 14 23:59:01 s8330018 kernel: [ 4972.486922] Call Trace:
  Mar 14 23:59:01 s8330018 kernel: [ 4972.486927] ([<0011406e>] 
show_trace+0xf6/0x148)
  Mar 14 23:59:01 s8330018 kernel: [ 4972.486929]  [<00114136>] 
show_stack+0x76/0xe8
  Mar 14 23:59:01 s8330018 kernel: [ 4972.486934]  [<00518c26>] 
dump_stack+0x6e/0x90
  Mar 14 23:59:01 s8330018 kernel: [ 4972.486937]  [<0027c376>] 
bad_page+0xe6/0x148
  Mar 14 23:59:01 s8330018 kernel: [ 4972.486938]  [<00280516>] 
get_page_from_freelist+0x49e/0xba8
  Mar 14 23:59:01 s8330018 kernel: [ 4972.486940]  [<00280ede>] 
__alloc_pages_nodemask+0x166/0xb00
  Mar 14 23:59:01 s8330018 kernel: [ 4972.486941]  [<0015635a>] 
s390_dma_alloc+0x82/0x1a0
  Mar 14 23:59:01 s8330018 kernel: [ 4972.486944]  [<03ff805ea142>] 
__genwqe_alloc_consistent+0x7a/0x90 [genwqe_card]
  Mar 14 23:59:01 s8330018 kernel: [ 4972.486947]  [<03ff805ea344>] 
genwqe_alloc_sync_sgl+0x17c/0x2e0 [genwqe_card]
  Mar 14 23:59:01 s8330018 kernel: [ 4972.486950]  [<03ff805e52da>] 
do_execute_ddcb+0x1da/0x348 [genwqe_card]
  Mar 14 23:59:01 s8330018 kernel: [ 4972.486952]  [<03ff805e5964>] 
genwqe_ioctl+0x51c/0xc20 [genwqe_card]
  Mar 14 23:59:01 s8330018 kernel: [ 4972.486953]  [<003145ee>] 
do_vfs_ioctl+0x3b6/0x518
  Mar 14 23:59:01 s8330018 kernel: [ 4972.486955]  [<003147f4>] 
SyS_ioctl+0xa4/0xb8
  Mar 14 23:59:01 s8330018 kernel: [ 4972.486956]  [<007ad1be>] 
system_call+0xd6/0x264
  Mar 14 23:59:01 s8330018 kernel: [ 4972.486957]  [<03ffa9df2492>] 
0x3ffa9df2492

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-release-notes/+bug/1559194/+subscriptions

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

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

[Brad Figg]

This bug is missing log files that will aid in diagnosing the problem.
>From a terminal window please run:

apport-collect 1631406

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

Title:
  Wrong memory.stat values in container root cgroup

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  1) Ubuntu 16.04.1 LTS

  2) linux-image-4.4.0-41-generic, bug happens and first tested on
  4.4.0-38, happens in all versions, including from 4.4.0-38 to 4.4.0-41
  and possibly. See this bug on totally different xenial lts machines

  3) What you expected to happen:
  cat /sys/fs/cgroup/memory/lxc/containername/memory.stat should display 
correct information

  4) What happened instead
  cat /sys/fs/cgroup/memory/lxc/containername/memory.stat shows incorrect 
information
  cat /sys/fs/cgroup/memory/memory.stat in container shows different information
  lxc exec containername -- cat /sys/fs/cgroup/memory/memory.stat shows totally 
different information from two above. Meanwhile cat 
/sys/fs/cgroup/memory/lxc/containername/memory.usage_in_bytes is always correct.

  5) mount | grep cgroup output:
  tmpfs on /sys/fs/cgroup type tmpfs (rw,mode=755)
  cgroup on /sys/fs/cgroup/systemd type cgroup 
(rw,nosuid,nodev,noexec,relatime,xattr,release_agent=/lib/systemd/systemd-cgroups-agent,name=systemd)
  cgroup on /sys/fs/cgroup/cpu,cpuacct type cgroup 
(rw,nosuid,nodev,noexec,relatime,cpu,cpuacct)
  cgroup on /sys/fs/cgroup/perf_event type cgroup 
(rw,nosuid,nodev,noexec,relatime,perf_event,release_agent=/run/cgmanager/agents/cgm-release-agent.perf_event)
  cgroup on /sys/fs/cgroup/hugetlb type cgroup 
(rw,nosuid,nodev,noexec,relatime,hugetlb,release_agent=/run/cgmanager/agents/cgm-release-agent.hugetlb)
  cgroup on /sys/fs/cgroup/memory type cgroup 
(rw,nosuid,nodev,noexec,relatime,memory)
  cgroup on /sys/fs/cgroup/devices type cgroup 
(rw,nosuid,nodev,noexec,relatime,devices)
  cgroup on /sys/fs/cgroup/net_cls,net_prio type cgroup 
(rw,nosuid,nodev,noexec,relatime,net_cls,net_prio)
  cgroup on /sys/fs/cgroup/cpuset type cgroup 
(rw,nosuid,nodev,noexec,relatime,cpuset,clone_children)
  cgroup on /sys/fs/cgroup/freezer type cgroup 
(rw,nosuid,nodev,noexec,relatime,freezer)
  cgroup on /sys/fs/cgroup/pids type cgroup 
(rw,nosuid,nodev,noexec,relatime,pids,release_agent=/run/cgmanager/agents/cgm-release-agent.pids)
  cgroup on /sys/fs/cgroup/blkio type cgroup 
(rw,nosuid,nodev,noexec,relatime,blkio)

  6) I was able to reproduce the bug on another machine where memory.stat for 
container is correct  after removing this packages, but it makes no sense at 
all:
  mountall:amd64 plymouth-theme-ubuntu-text:amd64 plymouth:amd64 upstart:amd64
  Installing back didn't help.

  7) memory.stat information for programs running in containers is
  correct. Only memory.stat information for container root is incorrect.

  Bug graphical representation:
  
https://cloud.githubusercontent.com/assets/6484506/19012936/9f19ff7a-87b2-11e6-9e68-889659663249.png
  First chart is based on cat 
/sys/fs/cgroup/memory/lxc/containername/memory.usage_in_bytes and cat 
/sys/fs/cgroup/memory/lxc/containername/memsw_usage_in_bytes. Second chart 
based on incorrect cat /sys/fs/cgroup/memory/lxc/containername/memory.stat

  Possibly the same problems (bugs quite old):
  https://issues.apache.org/jira/browse/MESOS-758
  https://groups.google.com/forum/#!topic/linux.kernel/EwiYK53Itk8

  Bug original sources:
  https://github.com/firehol/netdata/issues/1019
  https://github.com/lxc/lxd/issues/2422

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

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

[Kernel-packages] [Bug 1631406] [NEW] Wrong memory.stat values in container root cgroup

[hda_launchpad]

Public bug reported:

1) Ubuntu 16.04.1 LTS

2) linux-image-4.4.0-41-generic, bug happens and first tested on
4.4.0-38, happens in all versions, including from 4.4.0-38 to 4.4.0-41
and possibly. See this bug on totally different xenial lts machines

3) What you expected to happen:
cat /sys/fs/cgroup/memory/lxc/containername/memory.stat should display correct 
information

4) What happened instead
cat /sys/fs/cgroup/memory/lxc/containername/memory.stat shows incorrect 
information
cat /sys/fs/cgroup/memory/memory.stat in container shows different information
lxc exec containername -- cat /sys/fs/cgroup/memory/memory.stat shows totally 
different information from two above. Meanwhile cat 
/sys/fs/cgroup/memory/lxc/containername/memory.usage_in_bytes is always correct.

5) mount | grep cgroup output:
tmpfs on /sys/fs/cgroup type tmpfs (rw,mode=755)
cgroup on /sys/fs/cgroup/systemd type cgroup 
(rw,nosuid,nodev,noexec,relatime,xattr,release_agent=/lib/systemd/systemd-cgroups-agent,name=systemd)
cgroup on /sys/fs/cgroup/cpu,cpuacct type cgroup 
(rw,nosuid,nodev,noexec,relatime,cpu,cpuacct)
cgroup on /sys/fs/cgroup/perf_event type cgroup 
(rw,nosuid,nodev,noexec,relatime,perf_event,release_agent=/run/cgmanager/agents/cgm-release-agent.perf_event)
cgroup on /sys/fs/cgroup/hugetlb type cgroup 
(rw,nosuid,nodev,noexec,relatime,hugetlb,release_agent=/run/cgmanager/agents/cgm-release-agent.hugetlb)
cgroup on /sys/fs/cgroup/memory type cgroup 
(rw,nosuid,nodev,noexec,relatime,memory)
cgroup on /sys/fs/cgroup/devices type cgroup 
(rw,nosuid,nodev,noexec,relatime,devices)
cgroup on /sys/fs/cgroup/net_cls,net_prio type cgroup 
(rw,nosuid,nodev,noexec,relatime,net_cls,net_prio)
cgroup on /sys/fs/cgroup/cpuset type cgroup 
(rw,nosuid,nodev,noexec,relatime,cpuset,clone_children)
cgroup on /sys/fs/cgroup/freezer type cgroup 
(rw,nosuid,nodev,noexec,relatime,freezer)
cgroup on /sys/fs/cgroup/pids type cgroup 
(rw,nosuid,nodev,noexec,relatime,pids,release_agent=/run/cgmanager/agents/cgm-release-agent.pids)
cgroup on /sys/fs/cgroup/blkio type cgroup 
(rw,nosuid,nodev,noexec,relatime,blkio)

6) I was able to reproduce the bug on another machine where memory.stat for 
container is correct  after removing this packages, but it makes no sense at 
all:
mountall:amd64 plymouth-theme-ubuntu-text:amd64 plymouth:amd64 upstart:amd64
Installing back didn't help.

7) memory.stat information for programs running in containers is
correct. Only memory.stat information for container root is incorrect.

Bug graphical representation:
https://cloud.githubusercontent.com/assets/6484506/19012936/9f19ff7a-87b2-11e6-9e68-889659663249.png
First chart is based on cat 
/sys/fs/cgroup/memory/lxc/containername/memory.usage_in_bytes and cat 
/sys/fs/cgroup/memory/lxc/containername/memsw_usage_in_bytes. Second chart 
based on incorrect cat /sys/fs/cgroup/memory/lxc/containername/memory.stat

Possibly the same problems (bugs quite old):
https://issues.apache.org/jira/browse/MESOS-758
https://groups.google.com/forum/#!topic/linux.kernel/EwiYK53Itk8

Bug original sources:
https://github.com/firehol/netdata/issues/1019
https://github.com/lxc/lxd/issues/2422

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

** Description changed:

  1) Ubuntu 16.04.1 LTS
- 2) linux-image-4.4.0-41-generic, bug happens and first tested on 4.4.0-38, 
happens in all versions, including from 4.4.0-38 to 4.4.0-41 and possibly. See 
this bug on totally different xenial lts machines
+ 
+ 2) linux-image-4.4.0-41-generic, bug happens and first tested on
+ 4.4.0-38, happens in all versions, including from 4.4.0-38 to 4.4.0-41
+ and possibly. See this bug on totally different xenial lts machines
+ 
  3) What you expected to happen:
  cat /sys/fs/cgroup/memory/lxc/containername/memory.stat should display 
correct information
+ 
  4) What happened instead
  cat /sys/fs/cgroup/memory/lxc/containername/memory.stat shows incorrect 
information
  cat /sys/fs/cgroup/memory/memory.stat in container shows different information
  lxc exec containername -- cat /sys/fs/cgroup/memory/memory.stat shows totally 
different information from two above. Meanwhile cat 
/sys/fs/cgroup/memory/lxc/containername/memory.usage_in_bytes is always correct.
+ 
  5) mount | grep cgroup output:
  tmpfs on /sys/fs/cgroup type tmpfs (rw,mode=755)
  cgroup on /sys/fs/cgroup/systemd type cgroup 
(rw,nosuid,nodev,noexec,relatime,xattr,release_agent=/lib/systemd/systemd-cgroups-agent,name=systemd)
  cgroup on /sys/fs/cgroup/cpu,cpuacct type cgroup 
(rw,nosuid,nodev,noexec,relatime,cpu,cpuacct)
  cgroup on /sys/fs/cgroup/perf_event type cgroup 
(rw,nosuid,nodev,noexec,relatime,perf_event,release_agent=/run/cgmanager/agents/cgm-release-agent.perf_event)
  cgroup on /sys/fs/cgroup/hugetlb type cgroup 
(rw,nosuid,nodev,noexec,relatime,hugetlb,release_agent=/run/cgmanager/agents/cgm-release-agent.hugetlb)
  cgroup on /sys/fs/cgroup/memory type cgroup 
(rw,nosuid,nodev,noexec,relatime,memory)
  

[Kernel-packages] [Bug 1559194] linux-image-4.4.0-33.52+_4.4.0-33.52+-6_s390x.deb

[bugproxy]

--- Comment on attachment From geral...@de.ibm.com 2016-09-06 10:25 
EDT---


Debian kernel package with genwqe-bad-page.patch applied.

** Attachment added: "linux-image-4.4.0-33.52+_4.4.0-33.52+-6_s390x.deb"
   
https://bugs.launchpad.net/bugs/1559194/+attachment/4756788/+files/linux-image-4.4.0-33.52+_4.4.0-33.52+-6_s390x.deb

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

Title:
  Bad page state in process genwqe_gunzip pfn:3c275 in the genwqe device
  driver

Status in Release Notes for Ubuntu:
  Fix Released
Status in Ubuntu on IBM z Systems:
  Fix Released
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Xenial:
  In Progress
Status in linux source package in Yakkety:
  In Progress

Bug description:
  == Comment: #0 - Dmitry Gorbachev  - 2016-03-17 
08:52:41 ==
  An error occurs when running zEDC compression/decompression and hotplugging 
PCI devices.
  There was 1G of memory, 2 pci functions and 50 threads of gunzipping enabled.

  Mar 14 23:59:01 s8330018 kernel: [ 4972.486883] BUG: Bad page state in 
process genwqe_gunzip  pfn:3c275
  Mar 14 23:59:01 s8330018 kernel: [ 4972.486888] page:03d100f09d40 
count:-1 mapcount:0 mapping:  (null) index:0x0
  Mar 14 23:59:01 s8330018 kernel: [ 4972.486891] flags: 0x0()
  Mar 14 23:59:01 s8330018 kernel: [ 4972.486895] page dumped because: nonzero 
_count
  Mar 14 23:59:01 s8330018 kernel: [ 4972.486897] Modules linked in: 
xt_CHECKSUM(E) iptable_mangle(E) ipt_MASQUERADE(E) nf_nat_masquerade_ipv4(E) 
iptable_nat(E) nf_conntrack_ipv4(E) nf_defrag_ipv4(E) nf_nat_ipv4(E) nf_nat(E) 
nf_conntrack(E) xt_tcpudp(E) bridge(E) stp(E) llc(E) iptable_filter(E) 
ip_tables(E) x_tables(E) genwqe_card(E) crc_itu_t(E) qeth_l2(E) qeth(E) vmur(E) 
ccwgroup(E) dm_multipath(E) ib_iser(E) rdma_cm(E) iw_cm(E) ib_cm(E) ib_sa(E) 
ib_mad(E) ib_core(E) ib_addr(E) iscsi_tcp(E) libiscsi_tcp(E) libiscsi(E) 
scsi_transport_iscsi(E) btrfs(E) zlib_deflate(E) raid10(E) raid456(E) 
async_memcpy(E) async_raid6_recov(E) async_pq(E) async_xor(E) async_tx(E) 
xor(E) raid6_pq(E) libcrc32c(E) raid1(E) raid0(E) linear(E) ghash_s390(E) 
prng(E) aes_s390(E) des_s390(E) des_generic(E) sha512_s390(E) sha256_s390(E) 
sha1_s390(E) sha_common(E) zfcp(E) qdio(E) scsi_transport_fc(E) 
dasd_eckd_mod(E) dasd_mod(E)
  Mar 14 23:59:01 s8330018 kernel: [ 4972.486916] CPU: 0 PID: 37867 Comm: 
genwqe_gunzip Tainted: GW   E   4.4.0-8-generic #23-Ubuntu
  Mar 14 23:59:01 s8330018 kernel: [ 4972.486916]209176f8 
20917788 0002 
  Mar 14 23:59:01 s8330018 kernel: [ 4972.486916]20917828 
209177a0 209177a0 00114182
  Mar 14 23:59:01 s8330018 kernel: [ 4972.486916]0011 
0092345a 03d1000a 000a
  Mar 14 23:59:01 s8330018 kernel: [ 4972.486916]209177e8 
20917788  20914000
  Mar 14 23:59:01 s8330018 kernel: [ 4972.486916] 
00114182 20917788 209177e8
  Mar 14 23:59:01 s8330018 kernel: [ 4972.486922] Call Trace:
  Mar 14 23:59:01 s8330018 kernel: [ 4972.486927] ([<0011406e>] 
show_trace+0xf6/0x148)
  Mar 14 23:59:01 s8330018 kernel: [ 4972.486929]  [<00114136>] 
show_stack+0x76/0xe8
  Mar 14 23:59:01 s8330018 kernel: [ 4972.486934]  [<00518c26>] 
dump_stack+0x6e/0x90
  Mar 14 23:59:01 s8330018 kernel: [ 4972.486937]  [<0027c376>] 
bad_page+0xe6/0x148
  Mar 14 23:59:01 s8330018 kernel: [ 4972.486938]  [<00280516>] 
get_page_from_freelist+0x49e/0xba8
  Mar 14 23:59:01 s8330018 kernel: [ 4972.486940]  [<00280ede>] 
__alloc_pages_nodemask+0x166/0xb00
  Mar 14 23:59:01 s8330018 kernel: [ 4972.486941]  [<0015635a>] 
s390_dma_alloc+0x82/0x1a0
  Mar 14 23:59:01 s8330018 kernel: [ 4972.486944]  [<03ff805ea142>] 
__genwqe_alloc_consistent+0x7a/0x90 [genwqe_card]
  Mar 14 23:59:01 s8330018 kernel: [ 4972.486947]  [<03ff805ea344>] 
genwqe_alloc_sync_sgl+0x17c/0x2e0 [genwqe_card]
  Mar 14 23:59:01 s8330018 kernel: [ 4972.486950]  [<03ff805e52da>] 
do_execute_ddcb+0x1da/0x348 [genwqe_card]
  Mar 14 23:59:01 s8330018 kernel: [ 4972.486952]  [<03ff805e5964>] 
genwqe_ioctl+0x51c/0xc20 [genwqe_card]
  Mar 14 23:59:01 s8330018 kernel: [ 4972.486953]  [<003145ee>] 
do_vfs_ioctl+0x3b6/0x518
  Mar 14 23:59:01 s8330018 kernel: [ 4972.486955]  [<003147f4>] 
SyS_ioctl+0xa4/0xb8
  Mar 14 23:59:01 s8330018 kernel: [ 4972.486956]  [<007ad1be>] 
system_call+0xd6/0x264
  Mar 14 23:59:01 s8330018 kernel: [ 4972.486957]  [<03ffa9df2492>] 
0x3ffa9df2492

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-release-notes/+bug/1559194/+subscriptions

-- 
Mailing list: 

[Kernel-packages] [Bug 1559194] linux-image-4.4.0-33.52+_4.4.0-33.52+-6_s390x.deb

[bugproxy]

--- Comment on attachment From geral...@de.ibm.com 2016-09-06 10:25 
EDT---


Debian kernel package with genwqe-bad-page.patch applied.

** Attachment added: "linux-image-4.4.0-33.52+_4.4.0-33.52+-6_s390x.deb"
   
https://bugs.launchpad.net/bugs/1559194/+attachment/4756768/+files/linux-image-4.4.0-33.52+_4.4.0-33.52+-6_s390x.deb

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

Title:
  Bad page state in process genwqe_gunzip pfn:3c275 in the genwqe device
  driver

Status in Release Notes for Ubuntu:
  Fix Released
Status in Ubuntu on IBM z Systems:
  Fix Released
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Xenial:
  In Progress
Status in linux source package in Yakkety:
  In Progress

Bug description:
  == Comment: #0 - Dmitry Gorbachev  - 2016-03-17 
08:52:41 ==
  An error occurs when running zEDC compression/decompression and hotplugging 
PCI devices.
  There was 1G of memory, 2 pci functions and 50 threads of gunzipping enabled.

  Mar 14 23:59:01 s8330018 kernel: [ 4972.486883] BUG: Bad page state in 
process genwqe_gunzip  pfn:3c275
  Mar 14 23:59:01 s8330018 kernel: [ 4972.486888] page:03d100f09d40 
count:-1 mapcount:0 mapping:  (null) index:0x0
  Mar 14 23:59:01 s8330018 kernel: [ 4972.486891] flags: 0x0()
  Mar 14 23:59:01 s8330018 kernel: [ 4972.486895] page dumped because: nonzero 
_count
  Mar 14 23:59:01 s8330018 kernel: [ 4972.486897] Modules linked in: 
xt_CHECKSUM(E) iptable_mangle(E) ipt_MASQUERADE(E) nf_nat_masquerade_ipv4(E) 
iptable_nat(E) nf_conntrack_ipv4(E) nf_defrag_ipv4(E) nf_nat_ipv4(E) nf_nat(E) 
nf_conntrack(E) xt_tcpudp(E) bridge(E) stp(E) llc(E) iptable_filter(E) 
ip_tables(E) x_tables(E) genwqe_card(E) crc_itu_t(E) qeth_l2(E) qeth(E) vmur(E) 
ccwgroup(E) dm_multipath(E) ib_iser(E) rdma_cm(E) iw_cm(E) ib_cm(E) ib_sa(E) 
ib_mad(E) ib_core(E) ib_addr(E) iscsi_tcp(E) libiscsi_tcp(E) libiscsi(E) 
scsi_transport_iscsi(E) btrfs(E) zlib_deflate(E) raid10(E) raid456(E) 
async_memcpy(E) async_raid6_recov(E) async_pq(E) async_xor(E) async_tx(E) 
xor(E) raid6_pq(E) libcrc32c(E) raid1(E) raid0(E) linear(E) ghash_s390(E) 
prng(E) aes_s390(E) des_s390(E) des_generic(E) sha512_s390(E) sha256_s390(E) 
sha1_s390(E) sha_common(E) zfcp(E) qdio(E) scsi_transport_fc(E) 
dasd_eckd_mod(E) dasd_mod(E)
  Mar 14 23:59:01 s8330018 kernel: [ 4972.486916] CPU: 0 PID: 37867 Comm: 
genwqe_gunzip Tainted: GW   E   4.4.0-8-generic #23-Ubuntu
  Mar 14 23:59:01 s8330018 kernel: [ 4972.486916]209176f8 
20917788 0002 
  Mar 14 23:59:01 s8330018 kernel: [ 4972.486916]20917828 
209177a0 209177a0 00114182
  Mar 14 23:59:01 s8330018 kernel: [ 4972.486916]0011 
0092345a 03d1000a 000a
  Mar 14 23:59:01 s8330018 kernel: [ 4972.486916]209177e8 
20917788  20914000
  Mar 14 23:59:01 s8330018 kernel: [ 4972.486916] 
00114182 20917788 209177e8
  Mar 14 23:59:01 s8330018 kernel: [ 4972.486922] Call Trace:
  Mar 14 23:59:01 s8330018 kernel: [ 4972.486927] ([<0011406e>] 
show_trace+0xf6/0x148)
  Mar 14 23:59:01 s8330018 kernel: [ 4972.486929]  [<00114136>] 
show_stack+0x76/0xe8
  Mar 14 23:59:01 s8330018 kernel: [ 4972.486934]  [<00518c26>] 
dump_stack+0x6e/0x90
  Mar 14 23:59:01 s8330018 kernel: [ 4972.486937]  [<0027c376>] 
bad_page+0xe6/0x148
  Mar 14 23:59:01 s8330018 kernel: [ 4972.486938]  [<00280516>] 
get_page_from_freelist+0x49e/0xba8
  Mar 14 23:59:01 s8330018 kernel: [ 4972.486940]  [<00280ede>] 
__alloc_pages_nodemask+0x166/0xb00
  Mar 14 23:59:01 s8330018 kernel: [ 4972.486941]  [<0015635a>] 
s390_dma_alloc+0x82/0x1a0
  Mar 14 23:59:01 s8330018 kernel: [ 4972.486944]  [<03ff805ea142>] 
__genwqe_alloc_consistent+0x7a/0x90 [genwqe_card]
  Mar 14 23:59:01 s8330018 kernel: [ 4972.486947]  [<03ff805ea344>] 
genwqe_alloc_sync_sgl+0x17c/0x2e0 [genwqe_card]
  Mar 14 23:59:01 s8330018 kernel: [ 4972.486950]  [<03ff805e52da>] 
do_execute_ddcb+0x1da/0x348 [genwqe_card]
  Mar 14 23:59:01 s8330018 kernel: [ 4972.486952]  [<03ff805e5964>] 
genwqe_ioctl+0x51c/0xc20 [genwqe_card]
  Mar 14 23:59:01 s8330018 kernel: [ 4972.486953]  [<003145ee>] 
do_vfs_ioctl+0x3b6/0x518
  Mar 14 23:59:01 s8330018 kernel: [ 4972.486955]  [<003147f4>] 
SyS_ioctl+0xa4/0xb8
  Mar 14 23:59:01 s8330018 kernel: [ 4972.486956]  [<007ad1be>] 
system_call+0xd6/0x264
  Mar 14 23:59:01 s8330018 kernel: [ 4972.486957]  [<03ffa9df2492>] 
0x3ffa9df2492

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-release-notes/+bug/1559194/+subscriptions

-- 
Mailing list: 

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

[bugproxy]

--- Comment From bren...@br.ibm.com 2016-10-07 10:18 EDT---
I saw that the crash package is already included in the -proposed archive. Can 
you test with it?

$ apt-cache madison crash
crash | 7.1.5-1ubuntu2 | http://us.ports.ubuntu.com/ubuntu-ports 
yakkety-proposed/main ppc64el Packages

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

Title:
  ISST-LTE:pVM:roselp2:ubuntu 16.10: crash failed to check vmcore of 4.8
  kernel

Status in crash package in Ubuntu:
  In Progress

Bug description:
  == Comment: #0 - Ping Tian Han  - 2016-09-22 03:05:36 ==
  ---Problem Description---
  crash cannot check vmcore of 4.8 kernel. 

  Then when trying to check the core with crash:

  % sudo crash /usr/lib/debug/boot/vmlinux-4.8.0-14-generic
  /var/crash/201609212349/vmcore.201609212349

  crash 7.1.5
  Copyright (C) 2002-2016  Red Hat, Inc.
  Copyright (C) 2004, 2005, 2006, 2010  IBM Corporation
  Copyright (C) 1999-2006  Hewlett-Packard Co
  Copyright (C) 2005, 2006, 2011, 2012  Fujitsu Limited
  Copyright (C) 2006, 2007  VA Linux Systems Japan K.K.
  Copyright (C) 2005, 2011  NEC Corporation
  Copyright (C) 1999, 2002, 2007  Silicon Graphics, Inc.
  Copyright (C) 1999, 2000, 2001, 2002  Mission Critical Linux, Inc.
  This program is free software, covered by the GNU General Public License,
  and you are welcome to change it and/or distribute copies of it under
  certain conditions.  Enter "help copying" to see the conditions.
  This program has absolutely no warranty.  Enter "help warranty" for details.

  GNU gdb (GDB) 7.6
  Copyright (C) 2013 Free Software Foundation, Inc.
  License GPLv3+: GNU GPL version 3 or later 
  This is free software: you are free to change and redistribute it.
  There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
  and "show warranty" for details.
  This GDB was configured as "powerpc64le-unknown-linux-gnu"...

  please wait... (gathering kmem slab cache data)
  crash: invalid kernel virtual address: 7aa9fe0100  type: "pmd page"

   
  ---uname output---
  Linux roselp2 4.8.0-14-generic #15-Ubuntu SMP Tue Sep 20 21:59:33 UTC 2016 
ppc64le ppc64le ppc64le GNU/Linux
   
  Machine Type = IBM,8286-42A, lpar 
   
  ---Steps to Reproduce---
   1. install 4.8 kernel
  2. trigger kdump to get vmcore
  3. check the vmcore with crash

  
  == Comment: #8 - Hari Krishna Bathini  - 2016-09-24 14:12:23 ==
  The below commit is needed for vtop address translation to succeed

commit 182914debbb9a2671ef644027fedd339aa9c80e0
Author: Dave Anderson 
Date:   Fri Sep 23 09:09:15 2016 -0400

  With the introduction of radix MMU in Power ISA 3.0, there are
  changes in kernel page table management accommodating it.  This patch
  series makes appropriate changes here to work for such kernels.
  Also, this series fixes a few bugs along the way:
  
ppc64: fix vtop page translation for 4K pages
ppc64: Use kernel terminology for each level in 4-level page table
ppc64/book3s: address changes in kernel v4.5
ppc64/book3s: address change in page flags for PowerISA v3.0
ppc64: use physical addresses and unfold pud for 64K page size
ppc64/book3s: support big endian Linux page tables
  
  The patches are needed for Linux v4.5 and later kernels on all
  ppc64 hardware.
  (hbath...@linux.vnet.ibm.com)
  --

  Also, the below commit is needed

commit 8ceb1ac628bf6a0a7f0bbfff030ec93081bca4cd
Author: Dave Anderson 
Date:   Mon May 23 11:23:01 2016 -0400

  Fix for Linux commit 0139aa7b7fa12ceef095d99dc36606a5b10ab83a, which
  renamed the page._count member to page._refcount.  Without the patch,
  certain "kmem" commands fail with the "kmem: invalid structure member
  offset: page_count".
  (ander...@redhat.com)

  Thanks
  Hari

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

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

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

[bugproxy]

--- Comment From cha...@us.ibm.com 2016-10-07 09:49 EDT---
*** Bug 146293 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/1624961

Title:
  Ubuntu 16.10 KVM: kernel 4.8 can not enable SRIOV for power systems

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

Bug description:
  ---Problem Description---
  Using Ubuntu mainline kernel 
  http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.8-rc6/
  if we try to enable SRIOV in Mellanox CX4 card it will fail. 

  # uname -r
  4.8.0-040800rc6-generic
  root@c158f2u09os:~# echo 7 > /sys/class/net/enP5p1s0f0/device/sriov_numvfs
  -bash: echo: write error: Cannot allocate memory

  logs show:
  Sep 16 00:52:46 c158f2u09os kernel: [ 1419.778118] mlx5_core 0005:01:00.0: 
not enough MMIO resources for SR-IOV
  Sep 16 00:52:46 c158f2u09os kernel: [ 1419.778238] mlx5_core 0005:01:00.0: 
enable sriov failed -12
  Sep 16 00:52:46 c158f2u09os kernel: [ 1419.778604] mlx5_core 0005:01:00.0: 
mlx5_core_sriov_enable failed -12

  ---uname output---
  4.8.0-040800rc6-generic
   
  ---Additional Hardware Info---
  To recreate this you need power system and a Mellanox card that can be used 
for SRIOV.  

   
  Machine Type = P8 
   
  ---Steps to Reproduce---
   with a Mellanox card like CX4 with SRIOV enabled.
  just do this echo to the PF interface in this case was enP5p1s0f0.
  echo 1 > /sys/class/net/enP5p1s0f0/device

  If I take kernel 4.8 and I revert the following patch I can get it to
  work again:

  
http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/patch/arch/powerpc/platforms/powernv
  /pci-ioda.c?id=5958d19a143eb229e9ece20bd4c781ad41cb7d24

   From 5958d19a143eb229e9ece20bd4c781ad41cb7d24 Mon Sep 17 00:00:00 2001
   From: Benjamin Herrenschmidt 
   Date: Fri, 8 Jul 2016 15:55:43 +1000
   Subject: powerpc/pnv/pci: Fix incorrect PE reservation attempt on some 
64-bit BARs

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

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

[Kernel-packages] [Bug 1627108] Re: X1Carbon comes to a crawl during high CPU usage tasks

[Omer Akram]

Ok, the one is comment 28 is bad, while the one in #29 is Good.

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

Title:
  X1Carbon comes to a crawl during high CPU usage tasks

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

Bug description:
  My X1Carbon becomes quite laggy, the cursor hangs for a few seconds
  and then resumes while my system is compiling some code, or lets says
  PyCharm is indexing things or Android Studio is compiling some code. I
  was using 4.4 on Xenial a few days ago and everything was working just
  fine. Installed Yakkety and this issue happens.

  I will downgrade the kernel and see if that mitigates the issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: linux-image-4.8.0-15-generic 4.8.0-15.16
  ProcVersionSignature: Ubuntu 4.8.0-15.16-generic 4.8.0-rc7
  Uname: Linux 4.8.0-15-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC1D0p:   om26er 3390 F...m pulseaudio
   /dev/snd/controlC1:  om26er 3390 F pulseaudio
   /dev/snd/controlC0:  om26er 3390 F pulseaudio
  CurrentDesktop: Unity
  Date: Fri Sep 23 21:40:34 2016
  HibernationDevice: RESUME=UUID=a92c85ab-cca3-4afc-abf1-3516f193129e
  InstallationDate: Installed on 2016-09-21 (1 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160921)
  MachineType: LENOVO 20BSCTO1WW
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-15-generic.efi.signed 
root=UUID=01b0a4a0-d791-46e8-a212-1f769cff3a4b ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-15-generic N/A
   linux-backports-modules-4.8.0-15-generic  N/A
   linux-firmware1.161
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/13/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N14ET32W (1.10 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20BSCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN14ET32W(1.10):bd08/13/2015:svnLENOVO:pn20BSCTO1WW:pvrThinkPadX1Carbon3rd:rvnLENOVO:rn20BSCTO1WW:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.name: 20BSCTO1WW
  dmi.product.version: ThinkPad X1 Carbon 3rd
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1629204] Re: Autofs parameter substitution broken in kernel 4.4.0-38 and 4.4.0-40

[Seth Forshee]

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

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

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

Title:
  Autofs parameter substitution broken in kernel 4.4.0-38 and 4.4.0-40

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

Bug description:
  SRU Justification

  Impact: ca6fe3344554 "fs: Call d_automount with the filesystems creds"
  causes a regression in the requester uid and gid passed to userspace
  during automount, as the current credentials during automount are
  those of root and not the user who requested the mount.

  Fix: Use current->real_cred instead of current->cred for getting the
  requester's uid and gid.

  Regression Potential: Minimal. current->cred and current->real_cred
  are the same except when credentials are overridden, thus
  current->real_cred contains the same credentials that autofs had been
  using prior to the change which overrides the credentials during
  automount.

  ---

  Hello,

  I have run into a bug relating autofs's parameter substitution (e.g.
  UID, GID, etc) with kernel versions 4.4.0-38 and proposed 4.4.0-40.
  Kernel version 4.4.0-28 does things correctly but testing intermediate
  kernel versions is hard due to earlier bugs related with fs's.
  Incorrect parameter substitution makes CIFS mounting with variable
  credentials impossible.

  Wat was expected:
  $UID in autofs map are substituted by the uid of the user that starts the 
auto-mounting process.

  What actually happens:
  Root's uid (0) is substituted instead.

  This ill parameter substitution likely caused by recent fixes
  resolving permissions problems for nfs/cifs mounts and dfs referrals
  (#1626112 and #1612135). And possibly the fix 'fs: Call d_automount
  with the filesystems creds' but that is a wild guess.

  Furthermore; playing with the force_standard_program_map_env settings
  in autofs.conf and prefixing variables with 'AUTOFS_' does not solve
  anything.

  Yours kindly,

  Chris

   Additional info 

    lsb_release -rd
  Description:Ubuntu 16.04.1 LTS
  Release:16.04
  ---
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  run1   3015 F pulseaudio
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=f2a2c5c4-2f41-482a-80b4-968a87131214
  InstallationDate: Installed on 2016-09-19 (10 days ago)
  InstallationMedia: Kubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  IwConfig:
   enp0s8no wireless extensions.

   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
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 vboxdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-40-generic root=/dev/sda1 
ro quiet splash
  ProcVersionSignature: Ubuntu 4.4.0-40.60-generic 4.4.21
  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.4.0-40-generic N/A
   linux-backports-modules-4.4.0-40-generic  N/A
   linux-firmware1.157.3
  RfKill:

  Tags:  xenial
  Uname: Linux 4.4.0-40-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

  _MarkForUpload: True
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH

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

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

[Kernel-packages] [Bug 1629205] Re: regression: with linux-image-4.4.0-38-generic autofs tries to acess folders as root instead of the user

[Robert Euhus]

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

This bug seems like a duplicate of this one filed moments beforem mine:
http://bugs.launchpad.net/bugs/1629204

The came to the same conclusion.

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

Title:
  regression: with linux-image-4.4.0-38-generic autofs tries to acess
  folders as root instead of the user

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Running with linux-image-4.4.0-38-generic autofs is not working
  properly anymore: when I try to access a autofs-monitored folder as
  normal user "joe" the environment variable $AUTOFS_USER inside the
  auto mounter map script is set to "root" instead of the user "joe".

  A little background information: in our setup the autofs master map
  /etc/auto.master contains a line:

  /mnt/cifs   /etc/auto.cifs-shares --timeout=300 --verbose

  The script /etc/auto.cifs-shares contains for debugging purposes the
  lines:

  DEBUG=true
  $DEBUG && logger -p debug -- "$0: running 'env|grep AUTOFS':"
  $DEBUG && logger -p debug -- "$(env|grep AUTOFS)"

  and

  if test "$1" = "$AUTOFS_USER" ; then
  ## First generate automount map
  [..]
  else
  logger -p debug -- "$0: Error: User '$AUTOFS_USER' tried to access 
wrong directory '$1'"
  fi

  
  Which yields to the following errors in the logs:

  Sep 29 17:03:20 pcXX root[7613]: AUTOFS_SHOST=pc203re3
   AUTOFS_HOME=/root
   AUTOFS_GID=0
   AUTOFS_UID=0
   AUTOFS_GROUP=root
   AUTOFS_USER=root
  Sep 29 17:03:20 pcXX root[7614]: /etc/auto.cifs-shares: Error: User 
'root' tried to access wrong directory 'joe'
  Sep 29 17:03:20 pcXX automount[7557]: lookup(program): lookup for joe 
failed
  Sep 29 17:03:20 pcXX automount[7557]: failed to mount /mnt/cifs/joe

  
  So for some reason autofs with this kernel gets the environment variables 
wrong.
  Running an older Kernel like linux-image-4.4.0-36-generic does not show this 
problem and the cifs shares work as expected.

  other Info:
  lsb_release -rd
  Description:Ubuntu 16.04.1 LTS
  Release:16.04

  uname -r
  4.4.0-38-generic

  If you need any further info or testing, please let me know.

  Thanks,
  Robert Euhus

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-38-generic 4.4.0-38.57
  ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
  Uname: Linux 4.4.0-38-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  euhus  1711 F pulseaudio
  CurrentDesktop: GNOME
  Date: Fri Sep 30 09:36:31 2016
  HibernationDevice: RESUME=UUID=1aae5293-ed3d-4dae-a8b5-54d831262f4a
  IwConfig:
   lono wireless extensions.
   
   enp0s31f6  no wireless extensions.
  MachineType: Dell Inc. OptiPlex 5040
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-38-generic 
root=UUID=adae86bf-dc79-4962-aa5f-41a1a037c8ec ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-38-generic N/A
   linux-backports-modules-4.4.0-38-generic  N/A
   linux-firmware1.157.3
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/15/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.7
  dmi.board.name: 0R790T
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 3
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.7:bd01/15/2016:svnDellInc.:pnOptiPlex5040:pvr:rvnDellInc.:rn0R790T:rvrA00:cvnDellInc.:ct3:cvr:
  dmi.product.name: OptiPlex 5040
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1629205] Re: regression: with linux-image-4.4.0-38-generic autofs tries to acess folders as root instead of the user

[Seth Forshee]

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

** This bug has been marked a duplicate of bug 1629204
   Autofs parameter substitution broken in kernel 4.4.0-38 and 4.4.0-40

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

Title:
  regression: with linux-image-4.4.0-38-generic autofs tries to acess
  folders as root instead of the user

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Running with linux-image-4.4.0-38-generic autofs is not working
  properly anymore: when I try to access a autofs-monitored folder as
  normal user "joe" the environment variable $AUTOFS_USER inside the
  auto mounter map script is set to "root" instead of the user "joe".

  A little background information: in our setup the autofs master map
  /etc/auto.master contains a line:

  /mnt/cifs   /etc/auto.cifs-shares --timeout=300 --verbose

  The script /etc/auto.cifs-shares contains for debugging purposes the
  lines:

  DEBUG=true
  $DEBUG && logger -p debug -- "$0: running 'env|grep AUTOFS':"
  $DEBUG && logger -p debug -- "$(env|grep AUTOFS)"

  and

  if test "$1" = "$AUTOFS_USER" ; then
  ## First generate automount map
  [..]
  else
  logger -p debug -- "$0: Error: User '$AUTOFS_USER' tried to access 
wrong directory '$1'"
  fi

  
  Which yields to the following errors in the logs:

  Sep 29 17:03:20 pcXX root[7613]: AUTOFS_SHOST=pc203re3
   AUTOFS_HOME=/root
   AUTOFS_GID=0
   AUTOFS_UID=0
   AUTOFS_GROUP=root
   AUTOFS_USER=root
  Sep 29 17:03:20 pcXX root[7614]: /etc/auto.cifs-shares: Error: User 
'root' tried to access wrong directory 'joe'
  Sep 29 17:03:20 pcXX automount[7557]: lookup(program): lookup for joe 
failed
  Sep 29 17:03:20 pcXX automount[7557]: failed to mount /mnt/cifs/joe

  
  So for some reason autofs with this kernel gets the environment variables 
wrong.
  Running an older Kernel like linux-image-4.4.0-36-generic does not show this 
problem and the cifs shares work as expected.

  other Info:
  lsb_release -rd
  Description:Ubuntu 16.04.1 LTS
  Release:16.04

  uname -r
  4.4.0-38-generic

  If you need any further info or testing, please let me know.

  Thanks,
  Robert Euhus

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-38-generic 4.4.0-38.57
  ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
  Uname: Linux 4.4.0-38-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  euhus  1711 F pulseaudio
  CurrentDesktop: GNOME
  Date: Fri Sep 30 09:36:31 2016
  HibernationDevice: RESUME=UUID=1aae5293-ed3d-4dae-a8b5-54d831262f4a
  IwConfig:
   lono wireless extensions.
   
   enp0s31f6  no wireless extensions.
  MachineType: Dell Inc. OptiPlex 5040
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-38-generic 
root=UUID=adae86bf-dc79-4962-aa5f-41a1a037c8ec ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-38-generic N/A
   linux-backports-modules-4.4.0-38-generic  N/A
   linux-firmware1.157.3
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/15/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.7
  dmi.board.name: 0R790T
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 3
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.7:bd01/15/2016:svnDellInc.:pnOptiPlex5040:pvr:rvnDellInc.:rn0R790T:rvrA00:cvnDellInc.:ct3:cvr:
  dmi.product.name: OptiPlex 5040
  dmi.sys.vendor: Dell Inc.

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

-- 
Mailing list: https://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 1590590] Re: Touchpad not recognized on Dell Latitude E7470 Ultrabook

[A. Richard Miller]

See attached.

--Dick Miller, Partner, MMS >


On 10/07/2016 04:02 AM, bagl0312 wrote:
> I found a workaround to invert the two finger scrolling behavior.
> It is enough to add a file .Xmodmap in the home dir with the following 
> content:
>
> $ cat .Xmodmap
> pointer = 2 3 5 4 6 7 8 9 10
>
> (note that the forth and fifth numbers are swapped)
>
> This invert the two finger scrolling direction, but unfortunately also
> the direction of scrolling of the wheel of an external mouse, if used...
>
> Anyway, for those using only the touchpad I think it is a good,
> temporary compromise :)
> -- You received this bug notification because you are subscribed to 
> xserver-xorg-input-synaptics in Ubuntu. Matching subscriptions: A. 
> Richard Miller https://bugs.launchpad.net/bugs/1590590 Title: Touchpad 
> not recognized on Dell Latitude E7470 Ultrabook Status in linux 
> package in Ubuntu: Triaged Status in xserver-xorg-input-synaptics 
> package in Ubuntu: Confirmed Bug description: Expected: Touchpad 
> settings available in Mouse & Touchpad Settings dialog Actual result: 
> Touchpad settings missing entirely Details: The touchpad on my Dell 
> Ultrabook (Latitude E7470) functions mostly. The settings for the 
> touchpad are not available at all in the Mouse and Touchpad settings 
> (see http://i.imgur.com/YRGiOrj.png). Two-finger scrolling works as 
> expected except it's using "Natural Scrolling" by default and there is 
> no way to change it. xinput list does not display a touchpad at all: ⎡ 
> Virtual core pointer id=2 [master pointer (3)] ⎜ ↳ Virtual core XTEST 
> pointer id=4 [slave pointer (2)] ⎜ ↳ ELAN Touchscreen id=11 [slave 
> pointer (2)] ⎜ ↳ ImPS/2 Generic Wheel Mouse id=13 [slave pointer (2)] 
> ⎣ Virtual core keyboard id=3 [master keyboard (2)] ↳ Virtual core 
> XTEST keyboard id=5 [slave keyboard (3)] ↳ Power Button id=6 [slave 
> keyboard (3)] ↳ Video Bus id=7 [slave keyboard (3)] ↳ Power Button 
> id=8 [slave keyboard (3)] ↳ Sleep Button id=9 [slave keyboard (3)] ↳ 
> Integrated_Webcam_FHD id=10 [slave keyboard (3)] ↳ AT Translated Set 2 
> keyboard id=12 [slave keyboard (3)] ↳ Dell WMI hotkeys id=14 [slave 
> keyboard (3)] ↳ DELL Wireless hotkeys id=15 [slave keyboard (3)] 
> /proc/bus/input/devices lists the device as a "Generic Wheel Mouse" 
> Output of `lsb_release -rd`: Description: Ubuntu 16.04 LTS Release: 
> 16.04 xserver-xorg-input-synaptics version information: 
> xserver-xorg-input-synaptics: Installed: 1.8.2-1ubuntu3 Candidate: 
> 1.8.2-1ubuntu3 Version table: *** 1.8.2-1ubuntu3 500 500 
> http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages 100 
> /var/lib/dpkg/status To manage notifications about this bug go to: 
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1590590/+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/1590590

Title:
  Touchpad not recognized on Dell Latitude E7470 Ultrabook

Status in linux package in Ubuntu:
  Triaged
Status in xserver-xorg-input-synaptics package in Ubuntu:
  Confirmed

Bug description:
  Expected: Touchpad settings available in Mouse & Touchpad Settings
  dialog

  Actual result: Touchpad settings missing entirely

  
  Details:
  The touchpad on my Dell Ultrabook (Latitude E7470) functions mostly. 

  The settings for the touchpad are not available at all in the Mouse
  and Touchpad settings (see http://i.imgur.com/YRGiOrj.png).

  Two-finger scrolling works as expected except it's using "Natural
  Scrolling" by default and there is no way to change it.

  xinput list does not display a touchpad at all:

  ⎡ Virtual core pointerid=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ ELAN Touchscreenid=11   [slave  pointer 
 (2)]
  ⎜   ↳ ImPS/2 Generic Wheel Mouse  id=13   [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)]
  ↳ Power Buttonid=8[slave  
keyboard (3)]
  ↳ Sleep Buttonid=9[slave  
keyboard (3)]
  ↳ Integrated_Webcam_FHD   id=10   [slave  
keyboard (3)]
  ↳ AT Translated Set 2 keyboardid=12   [slave  
keyboard (3)]
  ↳ Dell WMI hotkeysid=14   [slave  
keyboard (3)]
  ↳ DELL Wireless hotkeys   id=15   [slave  
keyboard (3)]

  
  /proc/bus/input/devices lists the device as a "Generic 

[Kernel-packages] [Bug 1244737] Re: Test Bug Report

[Seth Forshee]

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

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

Title:
  Test Bug Report

Status in linux-firmware package in Ubuntu:
  Invalid

Bug description:
  A test of the kernel team bug bots for the linux-firmware package.

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

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

[Kernel-packages] [Bug 1630906] Re: QML segfault on arm64 due to builder kernel change

[Timo Jyrinki]

xenial and yakkety needed symbol updates but now they have compiled and
work at least on desktop, and the arm64 build finished so it's likely
the arm64 build issue would be solved now. I've asked QA to look into
it.

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

Title:
  QML segfault on arm64 due to builder kernel change

Status in linux package in Ubuntu:
  Confirmed
Status in online-accounts-api package in Ubuntu:
  New
Status in qmenumodel package in Ubuntu:
  New
Status in qtdeclarative-opensource-src package in Ubuntu:
  New
Status in ubuntu-push-qml package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  New
Status in webbrowser-app package in Ubuntu:
  New

Bug description:
  Builders were changed from wily to xenial (4.4) kernel for arm64, and
  likely due to this the following kind of errors started happening:

  https://launchpadlibrarian.net/288487533/buildlog_ubuntu-yakkety-arm64
  .ubuntu-push-qml_0.1+15.10.20150826.1-0ubuntu2_BUILDING.txt.gz

  They happen when executing QML code.

  I've ruled out that reverting to previous qtbase and qtdeclarative
  versions don't affect this, so it's not coming from a Qt change. I've
  also verified there's no problem eg on our Bq tablet running the same
  tests on xenial+overlay. There are currently no found changes at least
  in Qt upstream to backport arm64 related fixes.

  Cause is unknown. But the same problem is there on vivid, xenial and yakkety 
builds:
  
https://launchpadlibrarian.net/288516465/buildlog_ubuntu-yakkety-arm64.online-accounts-api_0.1+16.10.20161006.1-0ubuntu1_BUILDING.txt.gz
  
https://launchpadlibrarian.net/288515705/buildlog_ubuntu-xenial-arm64.online-accounts-api_0.1+16.04.20161006.1-0ubuntu1_BUILDING.txt.gz
  
https://launchpadlibrarian.net/288515510/buildlog_ubuntu-vivid-arm64.online-accounts-api_0.1+15.04.20161006.1-0ubuntu1_BUILDING.txt.gz

  This means it does not matter if it's Qt 5.4 or 5.6, GCC 4.9, 5 or 6,
  or glibc 2.21, 2.23 or 2.24.

  More logs from affected packages:
  
https://launchpadlibrarian.net/288493058/buildlog_ubuntu-yakkety-arm64.qtdeclarative-opensource-src_5.6.1-7ubuntu3~1_BUILDING.txt.gz
  
https://launchpadlibrarian.net/288347391/buildlog_ubuntu-xenial-arm64.webbrowser-app_0.23+16.04.20161005.1-0ubuntu1_BUILDING.txt.gz
  
https://launchpadlibrarian.net/288385063/buildlog_ubuntu-vivid-arm64.qmenumodel_0.2.10+15.04.20161005.1-0ubuntu1_BUILDING.txt.gz

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

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

[Kernel-packages] [Bug 1602051] Re: 5Ghz link no longer works on 16.04 - iwlwifi

[Seth Forshee]

Closing as reporter has switched to a different card.

** Changed in: linux-firmware (Ubuntu)
   Status: Incomplete => Won't Fix

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

Title:
  5Ghz link no longer works on 16.04 - iwlwifi

Status in linux-firmware package in Ubuntu:
  Won't Fix

Bug description:
  Gone from 15.04 to 15.10 on a media PC, constantly streaming movies on
  the 5Ghz since some get choppy on 2.4Ghz. Has worked beautifully for
  well over a year now on both 15.x releases.

  Decided to take the plunge to 16.04, and things were good at first,
  but I believe there was a firmware update that broke 5Ghz support.

  After a update (then a reboot), I could (grudgingly) connect to my
  5Ghz network, but throughput would drop like a rock even on an apt
  update/upgrade, to the point where it would stop responding entirely.

  Had a thought regarding firmware, and decided to force an older rev,
  so I copied the newest from /lib/firmware/ (iwlwifi-3160-16.ucode) to
  a backup location and removed it from /lib/firmware/ which forced use
  of the next newest firmware, iwlwifi-3160-16.ucode, to be loaded.

  After a reboot, the difference is night and day - no problem
  connecting to my 5Ghz network again, and throughput is as expected for
  a solid 5Ghz connection.

  This is the AC version of this card (first one listed here):
  https://wikidevi.com/wiki/Intel#abgn.2Bac

  ```
  ~:$ lspci -nn | grep -i intel
  02:00.0 Network controller [0280]: Intel Corporation Wireless 3160 
[8086:08b3] (rev 83)
  ```

  This is an up to date 16.04, running kernel 4.4.0-28-generic, linux-
  firmware version 1.158 (although this occurred on 1.157 as well).

  I'm happy to output more info if needed.

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

-- 
Mailing list: https://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 1627274] Re: kernek 4.4.0-39-generic crash my xps 13 dev.ed I had to return to the 38

[jacopo.tolja]

Thank you Joseph
I did install the latest
jaki@jaki-XPS-13-9350:~$ uname -r
4.4.23-040423-generic
It boot up nicely and it work fine but I don't know where should I report
fixed upstream as you suggested.

I log into the bug report site and changed the status to "released"
But I don't know where to say Upstream!

Sorry but I am new to all this and just wish to help so I am learning.

As I say in the first report the bug related to the audio jack persist and
since last report I had dell change the motherboard where the jack is hard
installed and the problem persist

Should I make another report? and what type of information should I file to
make sure all the relative data is available to technician

Kind Regard and thank you for the wonderful work you do with Ubuntu


On Tue, Oct 4, 2016 at 3:09 PM, Joseph Salisbury <
joseph.salisb...@canonical.com> wrote:

> You really don't need to install the -headers package.  Just the
> linux-image package:
> linux-image-4.4.23-040423-generic_4.4.23-040423.201609300709_amd64.deb
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1627274
>
> Title:
>   kernek 4.4.0-39-generic crash my xps 13 dev.ed I had to return to the
>   38
>
> Status in linux package in Ubuntu:
>   Incomplete
> Status in linux source package in Xenial:
>   Incomplete
>
> Bug description:
>   Hi there, the system does not boot and goes into initransf black screen
>   I am not an experienced user and I just deleted the 4.4.0-39-generic and
> use the 4.4.0-38-generic that seem to work very good apart two small issues.
>   The touch screen does not work after a sleep  and to make it to work I
> have to close the lid and open the lid again and it work!
>   The sound jack does not give output
>   Kind Regard
>   Jacopo
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/
> 1627274/+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/1627274

Title:
  kernek 4.4.0-39-generic crash my xps 13 dev.ed I had to return to the
  38

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

Bug description:
  Hi there, the system does not boot and goes into initransf black screen
  I am not an experienced user and I just deleted the 4.4.0-39-generic and use 
the 4.4.0-38-generic that seem to work very good apart two small issues.
  The touch screen does not work after a sleep  and to make it to work I have 
to close the lid and open the lid again and it work!
  The sound jack does not give output
  Kind Regard
  Jacopo

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

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

[Kernel-packages] [Bug 1627274] Re: kernek 4.4.0-39-generic crash my xps 13 dev.ed I had to return to the 38

[jacopo.tolja]

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

Title:
  kernek 4.4.0-39-generic crash my xps 13 dev.ed I had to return to the
  38

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

Bug description:
  Hi there, the system does not boot and goes into initransf black screen
  I am not an experienced user and I just deleted the 4.4.0-39-generic and use 
the 4.4.0-38-generic that seem to work very good apart two small issues.
  The touch screen does not work after a sleep  and to make it to work I have 
to close the lid and open the lid again and it work!
  The sound jack does not give output
  Kind Regard
  Jacopo

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

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

[Kernel-packages] [Bug 1626517] Re: Access to some folders hangs and in dmesg see kernel BUG report

[Vadim Shalts]

Unfortunately I don't monitor precisely kernel version and updates. Hard
to say in what state was system prior to current one.

And I don't have strong scenario to reproduce this issue. But it hit me
be several times. I know cases in with it looks like appear. Switched to
upstream kernel. So far so good. Will continue to monitoring. If I will
not be able to reproduce this issue during next week then I will mark
bug with 'kernel-fixed-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/1626517

Title:
  Access to some folders hangs and in dmesg see kernel BUG report

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Probably freeze during access to folder caused by 
  kernel BUG at /build/linux-BvkamA/linux-4.4.0/fs/namei.c:2562!

  Also segfault during collecting information with 'ubuntu-bug linux', but not 
sure it is related:
  [80059.937844] apport-kde[22602]: segfault at 7fdb0f1d4b00 ip 
7fdb44cd40f5 sp 7ffd35400828 error 4 in 
QtCore.cpython-35m-x86_64-linux-gnu.so[7fdb44ae4000+268000]
  [80099.437691] Qt bearer threa[23986]: segfault at 7f23b89942e9 ip 
7f23b3d41ccb sp 7f239fffce50 error 4 in 
libgcc_s.so.1[7f23b3d33000+16000]
  It is looks like separate issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-28-generic 4.4.0-28.47
  ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13
  Uname: Linux 4.4.0-28-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  vadim  4045 F pulseaudio
   /dev/snd/controlC0:  vadim  4045 F pulseaudio
  Date: Thu Sep 22 13:52:19 2016
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=4ff5857a-eca8-4968-9e7d-16cb2b146f60
  InstallationDate: Installed on 2015-04-28 (512 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: ASUS All Series
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-28-generic 
root=UUID=f0d3e2ee-9f79-431c-9d8a-1079d7638279 ro quiet splash vt.handoff=7
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-28-generic N/A
   linux-backports-modules-4.4.0-28-generic  N/A
   linux-firmware1.157.3
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: Upgraded to xenial on 2016-04-22 (152 days ago)
  dmi.bios.date: 08/12/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1002
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H81M-K
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1002:bd08/12/2014:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH81M-K:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: All Series
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS

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

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

[Kernel-packages] [Bug 1589905] Re: Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter [168c:003e] is not supported

[Seth Forshee]

** Tags added: verification-done

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

Title:
  Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter [168c:003e]
  is not supported

Status in HWE Next:
  Triaged
Status in linux-firmware package in Ubuntu:
  Fix Released
Status in linux-firmware source package in Xenial:
  Fix Committed
Status in linux-firmware source package in Yakkety:
  Fix Released

Bug description:
  Firmware for this card isn't in the current linux-firmware package.
  Latest upstream firmware is also tested but doesn't work either.

  The only working firmware is extracted from Windows driver. By
  comparing the md5sum, the only different file is
  ath10k/QCA6174/hw3.0/board.bin (upstream is cb37c6, and Windows is
  df5ba1), we need Qualcomm to upstream the file to fix this issue.

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

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

[Kernel-packages] [Bug 1629661] Re: Hissing sound in headphones

[LGB [Gábor Lénárt]]

Sorry about my English, so I meant that I didn't own the machine itself,
so I have no experience just since I use that PC, and it's only two
weeks or so. Also, I've just discovered that the annoying sound is there
even right after switching the machine on, without any OS loaded too.

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

Title:
  Hissing sound in headphones

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 16.04 on 64 bit produces hissing sound (just by my - far from
  being 'musical' - ear, it sounds like a sinus wave with frequency
  about 1KHz or so) on headphones. Interestingly, after boot this does
  not happen and usually can be hear only after the first application
  which makes any sound (but not always, sometimes it starts later). But
  if any time it starts, it remains, whatever I do, exiting the
  application (which makes the sound) even by killing pulseaudio
  process, etc. I've read a lot on this issue but usually - it seems -
  always notebook problems mentioned, however it's a desktop machine
  (Asrock FM2A88M extreme4+ motherboard, AMD A6-6400K CPU, integrated
  audio). It seems it uses snd_hda_intel kernel module though. I've
  tried advices mentioned by various resources throughout the net,
  disabling powersave problems, using hdajackretask from alsa-tools-gui,
  etc, but they didn't help.

  Ubuntu 4.4.0-36.55-generic 4.4.16

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-41-generic 4.4.0-41.61
  ProcVersionSignature: Ubuntu 4.4.0-41.61-generic 4.4.21
  Uname: Linux 4.4.0-41-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  lgb2128 F pulseaudio
   /dev/snd/controlC0:  lgb2128 F pulseaudio
  CurrentDesktop: Unity
  Date: Sun Oct  2 14:24:21 2016
  HibernationDevice: RESUME=UUID=c92777cb-b700-4a8e-b937-1ed4983fecb1
  InstallationDate: Installed on 2015-07-10 (449 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release i386 (20150422)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-41-generic 
root=UUID=d203063e-78c0-425a-bee2-0e3ecb4ea74c ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-41-generic N/A
   linux-backports-modules-4.4.0-41-generic  N/A
   linux-firmware1.157.4
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/17/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P2.00
  dmi.board.name: FM2A88M Extreme4+
  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.:bvrP2.00:bd01/17/2014:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnFM2A88MExtreme4+: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/1629661/+subscriptions

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

[Kernel-packages] [Bug 1500242] Re: Bluetooth devices (Jabra BT250, Audi A3 car kit) can not be connected with BQ Aquaris 4.5

[asier urbina]

Hello all,

I am getting the same problem.
I use BQ Aquaris E4.5 and my car is Seat Altea XL 2010 version.
The phone finds the car bluetooth, I can connect to it, I get the PIN request, 
and the device gets paired. Even the bluetooth icon changes its colour to white.
But when i try to make a call, or to access the contacts, the connection goes 
down.

I would like to tell that for me it is really frustrating to see how the 
problems with the bluetooth system are going from one OTA to the following, or 
worse in this case that it is being redirected to backlog, without being solved.
In my case it is very important to connect the phone with the car, as i haveto 
drive long distances and need to make or recieve calls for work purposes.

Thank you for your support and work.
Best regards.

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

Title:
  Bluetooth devices (Jabra BT250, Audi A3 car kit) can not be connected
  with BQ Aquaris 4.5

Status in Canonical System Image:
  In Progress
Status in bluez package in Ubuntu:
  Confirmed
Status in ofono package in Ubuntu:
  Incomplete

Bug description:
  STEPS:
  Requirements: Aquaris E4.5, Jabra BT250 blue tooth handset device (rather old 
one supports blue tooth 1.1 and therefore I thought should be no issue) or Audi 
car kit (A3 2012 model)

  1. Put Jabra BT250 into receiving mode
  2. Phone searches automatically every 15 - 30 seconds for a new blue tooth 
device
  3. Phone finds Jabra BT250 and asks for pairing code
  4. Enter code into phone
  5. Jabra BT250 automatically exits the pairing mode (which is a sign that 
pairing should have worked)
  6. Phone looses connection to Jabra BT250
  7. Manual reconnection via phone works (shows Jabra BT250 as being connected) 
but ignores the device

  Same behaviour with Audi car kit (Audi A3, 2012 model)

  EXPECTED:
  I expect that the blue tooth kits work similar to my Seat Alhambra (also 2012 
model) where the blue tooth pairing etc. works great (except some bugs which 
are already filed).

  ACTUAL:
  No connection to the blue tooth device

  VERSIONS:
  OS-Build-Number: 25
  Ubuntu-Image: 20150825.1

  POSSIBLE ROOT CAUSE:
  Is this issue also solved as soon as bluez5 is implemented? When will this be?

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1500242/+subscriptions

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

[Kernel-packages] [Bug 1629205] Re: regression: with linux-image-4.4.0-38-generic autofs tries to acess folders as root instead of the user

[Robert Euhus]

Tim - thanks for that advice!

Now I'm finally there:

git bisect good
ca6fe3344554d31ac9c0f7e2e6be490c2d5d501f is the first bad commit
commit ca6fe3344554d31ac9c0f7e2e6be490c2d5d501f
Author: Eric W. Biederman 
Date:   Tue Sep 6 09:32:01 2016 -0500

fs: Call d_automount with the filesystems creds

BugLink: http://bugs.launchpad.net/bugs/1612135

Seth Forshee reported a mount regression in nfs autmounts
with "fs: Add user namespace member to struct super_block".

It turns out that the assumption that current->cred is something
reasonable during mount while necessary to improve support of
unprivileged mounts is wrong in the automount path.

To fix the existing filesystems override current->cred with the
init_cred before calling d_automount and restore current->cred after
d_automount completes.

To support unprivileged mounts would require a more nuanced cred
selection, so fail on unprivileged mounts for the time being.  As none
of the filesystems that currently set FS_USERNS_MOUNT implement
d_automount this check is only good for preventing future problems.

Fixes: 6e4eab577a0c ("fs: Add user namespace member to struct super_block")
Tested-by: Seth Forshee 
Signed-off-by: "Eric W. Biederman" 
(backported from commit aeaa4a79ff6a5ed912b7362f206cf8576fca538b)
Signed-off-by: Seth Forshee 
Acked-by: Stefan Bader 
Acked-by: Colin King 
Acked-by: Brad Figg 
Signed-off-by: Tim Gardner 

:04 04 3b16a342088c0cfead081f63bc7fe9bed93bcf00
2634a48c59a1c6b313be2d8406644fd9d0e18a60 M  fs


** Attachment added: "Git bisect log showing leading to the first bad commit."
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1629205/+attachment/4756633/+files/git_bisect_log_final

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

Title:
  regression: with linux-image-4.4.0-38-generic autofs tries to acess
  folders as root instead of the user

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Running with linux-image-4.4.0-38-generic autofs is not working
  properly anymore: when I try to access a autofs-monitored folder as
  normal user "joe" the environment variable $AUTOFS_USER inside the
  auto mounter map script is set to "root" instead of the user "joe".

  A little background information: in our setup the autofs master map
  /etc/auto.master contains a line:

  /mnt/cifs   /etc/auto.cifs-shares --timeout=300 --verbose

  The script /etc/auto.cifs-shares contains for debugging purposes the
  lines:

  DEBUG=true
  $DEBUG && logger -p debug -- "$0: running 'env|grep AUTOFS':"
  $DEBUG && logger -p debug -- "$(env|grep AUTOFS)"

  and

  if test "$1" = "$AUTOFS_USER" ; then
  ## First generate automount map
  [..]
  else
  logger -p debug -- "$0: Error: User '$AUTOFS_USER' tried to access 
wrong directory '$1'"
  fi

  
  Which yields to the following errors in the logs:

  Sep 29 17:03:20 pcXX root[7613]: AUTOFS_SHOST=pc203re3
   AUTOFS_HOME=/root
   AUTOFS_GID=0
   AUTOFS_UID=0
   AUTOFS_GROUP=root
   AUTOFS_USER=root
  Sep 29 17:03:20 pcXX root[7614]: /etc/auto.cifs-shares: Error: User 
'root' tried to access wrong directory 'joe'
  Sep 29 17:03:20 pcXX automount[7557]: lookup(program): lookup for joe 
failed
  Sep 29 17:03:20 pcXX automount[7557]: failed to mount /mnt/cifs/joe

  
  So for some reason autofs with this kernel gets the environment variables 
wrong.
  Running an older Kernel like linux-image-4.4.0-36-generic does not show this 
problem and the cifs shares work as expected.

  other Info:
  lsb_release -rd
  Description:Ubuntu 16.04.1 LTS
  Release:16.04

  uname -r
  4.4.0-38-generic

  If you need any further info or testing, please let me know.

  Thanks,
  Robert Euhus

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-38-generic 4.4.0-38.57
  ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
  Uname: Linux 4.4.0-38-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  euhus  1711 F pulseaudio
  CurrentDesktop: GNOME
  Date: Fri Sep 30 09:36:31 2016
  HibernationDevice: RESUME=UUID=1aae5293-ed3d-4dae-a8b5-54d831262f4a
  IwConfig:
   lono wireless extensions.
   
   enp0s31f6  no wireless extensions.
  MachineType: Dell Inc. OptiPlex 5040
  ProcFB: 0 inteldrmfb
  

[Kernel-packages] [Bug 1631298] Re: lts-yakkety 4.8 cannot mount lvm raid1

[Andy Whitcroft]

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

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

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => Andy Whitcroft (apw)

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

Title:
  lts-yakkety 4.8 cannot mount lvm raid1

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  linux-lts-yakkety 4.8.0-20 from the dev ppa cannot mount my lvm raid1
  volumes, the linear volumes where / and /boot are mounted do work
  fine.

  device-mapper: raid: Loading target version 1.9.0
  [   21.128262] device-mapper: table: 252:7: raid: Unable to assemble array: 
Unknown flag(s) in compatible feature flags

  attached the dmesg and lvdisplay -m

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

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

[Kernel-packages] [Bug 1622005] Re: [Asus ZenBook UX501VW] Touchpad doesn't have multitouch support

[Christopher M. Penalver]

David DIDIER, no problem on my end. Sometimes you just have to rant it
out to move forward. :D

All joking aside, yahoo has been compromised for years, so it may not be
a bad idea to move off the platform going forward to better preserve
your security.

Despite this, while you didn't get a great outcome in that there is no
support, and one would have to wait until a developer works on it and
simultaneously nag the vendor to do it, at least you got the scoop on
your hardware.

Unfortunately, I'm not able to help further given the above, other than
reinforce what was advised by Dmitry.

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

Title:
  [Asus ZenBook UX501VW] Touchpad doesn't have multitouch support

Status in linux package in Ubuntu:
  Triaged

Bug description:
  The touchpad isn't recognized as such so there is no multitouch
  support. xinput displays "FTE1001:00 0B05:0101" instead.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  Uname: Linux 4.7.3-040703-generic x86_64
  NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] est un dossier: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  367.44  Wed Aug 17 22:24:07 
PDT 2016
   GCC version:  gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.2)
  .tmp.unity_support_test.0:

  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Fri Sep  9 22:27:19 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Skylake Integrated Graphics [8086:191b] (rev 06) (prog-if 
00 [VGA controller])
     Subsystem: ASUSTeK Computer Inc. Skylake Integrated Graphics [1043:1080]
     Subsystem: ASUSTeK Computer Inc. GM107M [GeForce GTX 960M] [1043:1080]
  InstallationDate: Installed on 2016-06-01 (100 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0a2a Intel Corp.
   Bus 001 Device 003: ID 046d:c069 Logitech, Inc. M-U0007 [Corded Mouse M500]
   Bus 001 Device 002: ID 04f2:b3fd Chicony Electronics Co., Ltd
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. N501VW
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.7.3-040703-generic 
root=UUID=ad612961-a4ae-4950-9d5a-20dcf8e56681 ro quiet splash acpi_osi= 
acpi_backlight=native nouveau.modeset=0 nvidia.nomodeset=0 i915.nomodeset=0 
vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/09/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: N501VW.300
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: N501VW
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrN501VW.300:bd05/09/2016:svnASUSTeKCOMPUTERINC.:pnN501VW:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnN501VW:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: N501VW
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz 1:0.9.12.2+16.04.20160714-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Fri Sep  9 22:26:55 2016
  xserver.configfile: default
  xserver.errors:
   Failed to load module "nvidia" (module does not exist, 0)
   Failed to load module "nvidia" (module does not exist, 0)
   [drm] Failed to open DRM device for (null): -22
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   12876
   vendor SDC
  

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

[Brad Figg]

This bug is missing log files that will aid in diagnosing the problem.
>From a terminal window please run:

apport-collect 1631298

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

Title:
  lts-yakkety 4.8 cannot mount lvm raid1

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  linux-lts-yakkety 4.8.0-20 from the dev ppa cannot mount my lvm raid1
  volumes, the linear volumes where / and /boot are mounted do work
  fine.

  device-mapper: raid: Loading target version 1.9.0
  [   21.128262] device-mapper: table: 252:7: raid: Unable to assemble array: 
Unknown flag(s) in compatible feature flags

  attached the dmesg and lvdisplay -m

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

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

[Kernel-packages] [Bug 1622005] Re: [Asus ZenBook UX501VW] Touchpad doesn't have multitouch support

[David DIDIER]

Christopher, I'm sorry, I didn't mean to upset you with my rant that
wasn't directed at you. But that was really annoying. So I finally sent
it successfully to the linux-input mailing list. After one week without
answer, I retried, and after another week, I directly emailed Dmitry
Torokhov.

Who informed me that the kernel list is to submit a patch or information
about recent kernel regression" and that I simply have some hardware
that is currently unsupported by the kernel. Then I can try to contact
the manufacturer to see if they will be willing to release a driver or I
can try to figure out the device and protocol myself. And he gave me a
pointer to this issue :
https://bugzilla.kernel.org/show_bug.cgi?id=120181.

As the manufacturer is still unclear and I'm not able to reverse
engineer the protocol, that settle it I guess... So for anyone willing
to buy a ZenBook ux501 and use it with Linux: just don't!

** Bug watch added: Linux Kernel Bug Tracker #120181
   http://bugzilla.kernel.org/show_bug.cgi?id=120181

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

Title:
  [Asus ZenBook UX501VW] Touchpad doesn't have multitouch support

Status in linux package in Ubuntu:
  Triaged

Bug description:
  The touchpad isn't recognized as such so there is no multitouch
  support. xinput displays "FTE1001:00 0B05:0101" instead.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  Uname: Linux 4.7.3-040703-generic x86_64
  NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] est un dossier: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  367.44  Wed Aug 17 22:24:07 
PDT 2016
   GCC version:  gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.2)
  .tmp.unity_support_test.0:

  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Fri Sep  9 22:27:19 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Skylake Integrated Graphics [8086:191b] (rev 06) (prog-if 
00 [VGA controller])
     Subsystem: ASUSTeK Computer Inc. Skylake Integrated Graphics [1043:1080]
     Subsystem: ASUSTeK Computer Inc. GM107M [GeForce GTX 960M] [1043:1080]
  InstallationDate: Installed on 2016-06-01 (100 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0a2a Intel Corp.
   Bus 001 Device 003: ID 046d:c069 Logitech, Inc. M-U0007 [Corded Mouse M500]
   Bus 001 Device 002: ID 04f2:b3fd Chicony Electronics Co., Ltd
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. N501VW
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.7.3-040703-generic 
root=UUID=ad612961-a4ae-4950-9d5a-20dcf8e56681 ro quiet splash acpi_osi= 
acpi_backlight=native nouveau.modeset=0 nvidia.nomodeset=0 i915.nomodeset=0 
vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/09/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: N501VW.300
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: N501VW
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrN501VW.300:bd05/09/2016:svnASUSTeKCOMPUTERINC.:pnN501VW:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnN501VW:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: N501VW
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz 1:0.9.12.2+16.04.20160714-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 

[Kernel-packages] [Bug 1623172] Re: [Asus ZenBook UX501VW] Function keys to change keyboard brightness don't work

[David DIDIER]

See
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1622005/comments/9

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

Title:
  [Asus ZenBook UX501VW] Function keys to change keyboard brightness
  don't work

Status in linux package in Ubuntu:
  Triaged

Bug description:
  On Ubuntu Ubuntu 16.04.1 LTS with all the latest kernels installed
  from http://kernel.ubuntu.com/~kernel-ppa/mainline/ : 4.4.19, 4.5.7,
  4.6.7, 4.7.3 nor 4.8-rc6.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  Uname: Linux 4.8.0-040800rc6-generic x86_64
  NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] est un dossier: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  367.44  Wed Aug 17 22:24:07 
PDT 2016
   GCC version:  gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.2)
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  BootLog:
   
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Tue Sep 13 21:44:06 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Skylake Integrated Graphics [8086:191b] (rev 06) (prog-if 
00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Skylake Integrated Graphics [1043:1080]
 Subsystem: ASUSTeK Computer Inc. GM107M [GeForce GTX 960M] [1043:1080]
  InstallationDate: Installed on 2016-06-01 (104 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 003: ID 046d:c069 Logitech, Inc. M-U0007 [Corded Mouse M500]
   Bus 001 Device 002: ID 04f2:b3fd Chicony Electronics Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. N501VW
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-040800rc6-generic 
root=UUID=ad612961-a4ae-4950-9d5a-20dcf8e56681 ro quiet splash acpi_osi= 
acpi_backlight=native nouveau.modeset=0 nvidia.nomodeset=0 i915.nomodeset=0 
vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/09/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: N501VW.300
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: N501VW
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrN501VW.300:bd05/09/2016:svnASUSTeKCOMPUTERINC.:pnN501VW:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnN501VW:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: N501VW
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.2
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Tue Sep 13 21:14:29 2016
  xserver.configfile: default
  xserver.errors:
   Failed to load module "nvidia" (module does not exist, 0)
   Failed to load module "nvidia" (module does not exist, 0)
   [drm] Failed to open DRM device for (null): -22
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   12876 
   vendor SDC
  xserver.version: 2:1.18.3-1ubuntu2.3

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

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

[Kernel-packages] [Bug 1631298] Re: lts-yakkety 4.8 cannot mount lvm raid1

[Julian Taylor]

attached lvdisplay -m /dev/lvm/linux-data and steam are the raid1
volumes

** Attachment added: "lvmsetup"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1631298/+attachment/4756581/+files/lvmsetup

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

Title:
  lts-yakkety 4.8 cannot mount lvm raid1

Status in linux package in Ubuntu:
  New

Bug description:
  linux-lts-yakkety 4.8.0-20 from the dev ppa cannot mount my lvm raid1
  volumes, the linear volumes where / and /boot are mounted do work
  fine.

  device-mapper: raid: Loading target version 1.9.0
  [   21.128262] device-mapper: table: 252:7: raid: Unable to assemble array: 
Unknown flag(s) in compatible feature flags

  attached the dmesg and lvdisplay -m

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

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

[Kernel-packages] [Bug 1631298] [NEW] lts-yakkety 4.8 cannot mount lvm raid1

[Julian Taylor]

Public bug reported:

linux-lts-yakkety 4.8.0-20 from the dev ppa cannot mount my lvm raid1
volumes, the linear volumes where / and /boot are mounted do work fine.

device-mapper: raid: Loading target version 1.9.0
[   21.128262] device-mapper: table: 252:7: raid: Unable to assemble array: 
Unknown flag(s) in compatible feature flags

attached the dmesg and lvdisplay -m

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

** Attachment added: "dmesg log"
   https://bugs.launchpad.net/bugs/1631298/+attachment/4756579/+files/raid.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/1631298

Title:
  lts-yakkety 4.8 cannot mount lvm raid1

Status in linux package in Ubuntu:
  New

Bug description:
  linux-lts-yakkety 4.8.0-20 from the dev ppa cannot mount my lvm raid1
  volumes, the linear volumes where / and /boot are mounted do work
  fine.

  device-mapper: raid: Loading target version 1.9.0
  [   21.128262] device-mapper: table: 252:7: raid: Unable to assemble array: 
Unknown flag(s) in compatible feature flags

  attached the dmesg and lvdisplay -m

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

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

[Kernel-packages] [Bug 1470250] Re: [Hyper-V] Ubuntu 14.04.2 LTS Generation 2 SCSI Errors on VSS Based Backups

[Emsi]

Thank you for the update. I'm staying tuned :)

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

Title:
  [Hyper-V] Ubuntu 14.04.2 LTS Generation 2 SCSI Errors on VSS Based
  Backups

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Trusty:
  In Progress
Status in linux source package in Vivid:
  In Progress
Status in linux source package in Wily:
  In Progress
Status in linux source package in Xenial:
  In Progress
Status in linux source package in Yakkety:
  In Progress

Bug description:
  Customers have reported running various versions of Ubuntu 14.04.2 LTS
  on Generation 2 Hyper-V Hosts.On a random Basis, the file system
  will be mounted Read-Only due to a "disk error" (which really isn't
  the case here).As a result, they must reboot the Ubuntu guest to
  get the file system to mount RW again.

  The Error seen are the following:
  Apr 30 00:02:01 balticnetworkstraining kernel: [640153.968142] storvsc: Sense 
Key : Unit Attention [current] 
  Apr 30 00:02:01 balticnetworkstraining kernel: [640153.968145] storvsc: Add. 
Sense: Changed operating definition
  Apr 30 00:02:01 balticnetworkstraining kernel: [640153.968161] sd 0:0:0:0: 
Warning! Received an indication that the operating parameters on this target 
have changed. The Linux SCSI layer does not automatically adjust these 
parameters.
  Apr 30 01:23:26 balticnetworkstraining kernel: [645039.584164] hv_storvsc 
vmbus_0_4: cmd 0x2a scsi status 0x2 srb status 0x82
  Apr 30 01:23:26 balticnetworkstraining kernel: [645039.584178] hv_storvsc 
vmbus_0_4: stor pkt 88006eb6c700 autosense data valid - len 18
  Apr 30 01:23:26 balticnetworkstraining kernel: [645039.584180] storvsc: Sense 
Key : Unit Attention [current] 
  Apr 30 01:23:26 balticnetworkstraining kernel: [645039.584183] storvsc: Add. 
Sense: Changed operating definition
  Apr 30 01:23:26 balticnetworkstraining kernel: [645039.584198] sd 0:0:0:0: 
Warning! Received an indication that the operating parameters on this target 
have changed.  The Linux SCSI layer does not automatically adjust these 
parameters.

  This relates to the VSS "Windows Server Backup" process that kicks off at 
midnight on the host and finishes an hour and half later.   
  Yes, we do have hv_vss_daemon and hv_kvp_daemon running for the correct 
kernel version we have.   We're currently running kernel version 
3.13.0-49-generic #83 on one system and 3.16.0-34-generic #37 on the other. -- 
We see the same errors on both.
  As a result, we've been hesitant to drop any more ubuntu guests on our 2012R2 
hyper-v system because of this.   We can stop the backup process and all is 
good, but we need nightly backups to image all of our VM's.   All the windows 
guests have no issues of course.   We also have some CentOS based guests 
running without issues from what we've seen.

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

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

[Kernel-packages] [Bug 1590590] Re: Touchpad not recognized on Dell Latitude E7470 Ultrabook

[bagl0312]

I found a workaround to invert the two finger scrolling behavior.
It is enough to add a file .Xmodmap in the home dir with the following content:

$ cat .Xmodmap 
pointer = 1 2 3 5 4 6 7 8 9 10

(note that the forth and fifth numbers are swapped)

This invert the two finger scrolling direction, but unfortunately also
the direction of scrolling of the wheel of an external mouse, if used...

Anyway, for those using only the touchpad I think it is a good,
temporary compromise :)

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

Title:
  Touchpad not recognized on Dell Latitude E7470 Ultrabook

Status in linux package in Ubuntu:
  Triaged
Status in xserver-xorg-input-synaptics package in Ubuntu:
  Confirmed

Bug description:
  Expected: Touchpad settings available in Mouse & Touchpad Settings
  dialog

  Actual result: Touchpad settings missing entirely

  
  Details:
  The touchpad on my Dell Ultrabook (Latitude E7470) functions mostly. 

  The settings for the touchpad are not available at all in the Mouse
  and Touchpad settings (see http://i.imgur.com/YRGiOrj.png).

  Two-finger scrolling works as expected except it's using "Natural
  Scrolling" by default and there is no way to change it.

  xinput list does not display a touchpad at all:

  ⎡ Virtual core pointerid=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ ELAN Touchscreenid=11   [slave  pointer 
 (2)]
  ⎜   ↳ ImPS/2 Generic Wheel Mouse  id=13   [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)]
  ↳ Power Buttonid=8[slave  
keyboard (3)]
  ↳ Sleep Buttonid=9[slave  
keyboard (3)]
  ↳ Integrated_Webcam_FHD   id=10   [slave  
keyboard (3)]
  ↳ AT Translated Set 2 keyboardid=12   [slave  
keyboard (3)]
  ↳ Dell WMI hotkeysid=14   [slave  
keyboard (3)]
  ↳ DELL Wireless hotkeys   id=15   [slave  
keyboard (3)]

  
  /proc/bus/input/devices lists the device as a "Generic Wheel Mouse"

  Output of `lsb_release -rd`:
  Description:  Ubuntu 16.04 LTS
  Release:  16.04

  xserver-xorg-input-synaptics version information:
  xserver-xorg-input-synaptics:
Installed: 1.8.2-1ubuntu3
Candidate: 1.8.2-1ubuntu3
Version table:
   *** 1.8.2-1ubuntu3 500
  500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status

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

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

[Kernel-packages] [Bug 1630549] Re: Traffic Shaping under kernel 4.4

[David Nix]

Hi Brad,

Can you please explain what sort of logs are you missing?

I am not able to run this command unfortunately.


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

Title:
  Traffic Shaping under kernel 4.4

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hi All,

  I am seeking information whether anyone come across this issue before.
  Basically traffic shaping stopped working as I started to use kernel
  4.4.19 The rules seem to be in place but packets do not get queued at
  all.

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

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

[Kernel-packages] [Bug 1629784] Re: Ubuntu16.04 installation failed on IBM LE server

[christy]

We have tried installing image(yakkety-server-ppc64el) downloaded from
this location  http://cdimage.ubuntu.com/ubuntu-server/daily/current/.
But installation failed with below error.

 GNU GRUB  version 2.02~beta2-36ubuntu11

 ++
 |*Install|
 | Rescue mode|
 ||
 ||
 ||
 ||
 ||
 ||
 ||
 ||
 ||
 ||
 ++

  Use the ^ and v keys to select which entry is highlighted.
  Press enter to boot the selected OS, `e' to edit the commands
  before booting or `c' for a command-line.


OF stdout device is: /vdevice/vty@3000
Preparing to boot Linux version 4.8.0-19-generic (buildd@bos01-ppc64el-030) 
(gcc version 6.2.0 20160914 (Ubuntu 6.2.0-3ubuntu15) ) #21-Ubuntu SMP Thu Sep 
29 19:43:27 UTC 2016 (Ubuntu 4.8.0-19.21-generic 4.8.0-rc8)
Detected machine type: 0101
Max number of cores passed to firmware: 256 (NR_CPUS = 2048)
Calling ibm,client-architecture-support... done
command line: BOOT_IMAGE=/install/vmlinux tasks=standard 
pkgsel/language-pack-patterns= pkgsel/install-language-support=false --- quiet
memory layout at init:
  memory_limit :  (16 MB aligned)
  alloc_bottom : 0ada
  alloc_top: 2000
  alloc_top_hi : 2000
  rmo_top  : 2000
  ram_top  : 2000
instantiating rtas at 0x1eb8... done
prom_hold_cpus: skipped
copying OF device tree...
Building dt strings...
Building dt structure...
Device tree strings 0x0adb -> 0x0adb1988
Device tree struct  0x0adc -> 0x0ae1
 -> smp_release_cpus()
spinning_secondaries = 191
 <- smp_release_cpus()
[1.297245] pci 001b:50:00.0: of_irq_parse_pci() failed with rc=-22
[1.506318] pci 001e:80:00.0: of_irq_parse_pci() failed with rc=-22
[3.671042] genirq: Flags mismatch irq 16. 0001 (hvc_console) vs. 
0001 (hvsi)
[3.671069] hvc_open: request_irq failed with rc -16.
[3.671144] Warning: unable to open an initial console.
Starting system log daemon: syslogd, klogd.

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

Title:
  Ubuntu16.04 installation failed on IBM LE server

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu OS installation is getting failed on IBM LE server. Please let
  us know whether this is System/OS specific issue.,

  Also please include "christy.rajku...@broadcom.com" in bug_list for
  any further information regarding bug.

  We tried installation with the image("ubuntu-16.04-server-ppc64el") that is 
available 
  under link: http://cdimage.ubuntu.com/releases/16.04.1/release/

  
  Please find the error message below.
   
   
   
   GNU GRUB  version 2.02~beta2-36ubuntu3
   
   
++
   |*Install
|
   | Rescue mode
|
   |
|
   |
|
   |
|
   |
|
   |
|
   |
|
   |
|
   |
|
   |
|
   |
|
   

[Kernel-packages] [Bug 1590590] Re: Touchpad not recognized on Dell Latitude E7470 Ultrabook

[bagl0312]

Indeed, if a workaround to invert the "natural scrolling" behavior will
be found we could survive until a real support is enabled

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

Title:
  Touchpad not recognized on Dell Latitude E7470 Ultrabook

Status in linux package in Ubuntu:
  Triaged
Status in xserver-xorg-input-synaptics package in Ubuntu:
  Confirmed

Bug description:
  Expected: Touchpad settings available in Mouse & Touchpad Settings
  dialog

  Actual result: Touchpad settings missing entirely

  
  Details:
  The touchpad on my Dell Ultrabook (Latitude E7470) functions mostly. 

  The settings for the touchpad are not available at all in the Mouse
  and Touchpad settings (see http://i.imgur.com/YRGiOrj.png).

  Two-finger scrolling works as expected except it's using "Natural
  Scrolling" by default and there is no way to change it.

  xinput list does not display a touchpad at all:

  ⎡ Virtual core pointerid=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ ELAN Touchscreenid=11   [slave  pointer 
 (2)]
  ⎜   ↳ ImPS/2 Generic Wheel Mouse  id=13   [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)]
  ↳ Power Buttonid=8[slave  
keyboard (3)]
  ↳ Sleep Buttonid=9[slave  
keyboard (3)]
  ↳ Integrated_Webcam_FHD   id=10   [slave  
keyboard (3)]
  ↳ AT Translated Set 2 keyboardid=12   [slave  
keyboard (3)]
  ↳ Dell WMI hotkeysid=14   [slave  
keyboard (3)]
  ↳ DELL Wireless hotkeys   id=15   [slave  
keyboard (3)]

  
  /proc/bus/input/devices lists the device as a "Generic Wheel Mouse"

  Output of `lsb_release -rd`:
  Description:  Ubuntu 16.04 LTS
  Release:  16.04

  xserver-xorg-input-synaptics version information:
  xserver-xorg-input-synaptics:
Installed: 1.8.2-1ubuntu3
Candidate: 1.8.2-1ubuntu3
Version table:
   *** 1.8.2-1ubuntu3 500
  500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status

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

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

[Kernel-packages] [Bug 1085766] Re: /var/log/upstart/ureadahead.log contains garbage

[Dominic Raferd]

I have this too with Xenial. Looking at yesterday's syslog:

$ sudo grep -c "Ignored relative path" /var/log/syslog.1
19728

and here are the first few lines:

$ sudo grep -m30 ureadahead /var/log/syslog.1
Oct  6 08:00:20 dl1 systemd[1]: Stopped Stop ureadahead data collection 45s 
after completed startup.
Oct  6 08:01:02 dl1 systemd[1]: Started Stop ureadahead data collection 45s 
after completed startup.
Oct  6 08:01:47 dl1 systemd[1]: Starting Stop ureadahead data collection...
Oct  6 08:01:47 dl1 systemd[1]: Started Stop ureadahead data collection.
Oct  6 08:01:47 dl1 ureadahead[222]: ureadahead:events/fs/open_exec/enable: 
Ignored relative path
Oct  6 08:01:47 dl1 ureadahead[222]: ureadahead:buffer_size_kb: Ignored 
relative path
Oct  6 08:01:47 dl1 ureadahead[222]: ureadahead:tracing_on: Ignored relative 
path
Oct  6 08:01:47 dl1 ureadahead[222]: ureadahead:binfmt_misc: Ignored relative 
path
Oct  6 08:01:47 dl1 ureadahead[222]: ureadahead:size: Ignored relative path
Oct  6 08:01:47 dl1 ureadahead[222]: ureadahead:start: Ignored relative path
Oct  6 08:01:47 dl1 ureadahead[222]: ureadahead:size: Ignored relative path
Oct  6 08:01:47 dl1 ureadahead[222]: ureadahead:start: Ignored relative path
Oct  6 08:01:47 dl1 ureadahead[222]: ureadahead:size: Ignored relative path
Oct  6 08:01:47 dl1 ureadahead[222]: ureadahead:start: Ignored relative path
Oct  6 08:01:47 dl1 ureadahead[222]: ureadahead:size: Ignored relative path
Oct  6 08:01:47 dl1 ureadahead[222]: ureadahead:start: Ignored relative path
Oct  6 08:01:47 dl1 ureadahead[222]: ureadahead:size: Ignored relative path
Oct  6 08:01:47 dl1 ureadahead[222]: ureadahead:start: Ignored relative path
Oct  6 08:01:47 dl1 ureadahead[222]: ureadahead:dm/uuid: Ignored relative path
Oct  6 08:01:47 dl1 ureadahead[222]: message repeated 11 times: [ 
ureadahead:dm/uuid: Ignored relative path]
Oct  6 08:01:47 dl1 ureadahead[222]: ureadahead:.: Ignored relative path
Oct  6 08:01:47 dl1 ureadahead[222]: ureadahead:1/stat: Ignored relative path
Oct  6 08:01:47 dl1 ureadahead[222]: ureadahead:1/cmdline: Ignored relative path

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

Title:
  /var/log/upstart/ureadahead.log contains garbage

Status in linux package in Ubuntu:
  Fix Released
Status in ureadahead package in Ubuntu:
  Fix Released

Bug description:
  After an upgrade to Raring (as of today) from Quantal I'm seeing tons
  of these in /var/log/upstart/ureadahead.log:

  Counted 8 CPUs

  ureadahead:  ��&a��w: Ignored relative path
  ureadahead:  : Ignored relative path
  ureadahead:  �=%���n�T9: Ignored relative path
  ureadahead:  �=%v9T9: Ignored relative path
  ureadahead:  �=%���U�Ek�: Ignored relative path
  ureadahead:  �=%���`�a: Ignored relative path

  
  (the boot was wonderfully fast - not sure if that's because ureadahead was 
working well or if it's because it didn't do anything).

  Dave

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: ureadahead 0.100.0-12build1
  ProcVersionSignature: Ubuntu 3.7.0-4.12-generic 3.7.0-rc7
  Uname: Linux 3.7.0-4-generic x86_64
  ApportVersion: 2.6.3-0ubuntu2
  Architecture: amd64
  Date: Mon Dec  3 02:06:14 2012
  InstallationDate: Installed on 2012-07-17 (138 days ago)
  InstallationMedia: Kubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120717)
  MarkForUpload: True
  ProcEnviron:
   LANGUAGE=en_GB:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: ureadahead
  UpgradeStatus: Upgraded to raring on 2012-12-02 (0 days ago)

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

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

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

[Brad Figg]

This change was made by a bot.

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

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

Title:
  [Yakkety] suspend fail and reboot while resuming

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Using 16.04 daily image: 20160919(downloading date)
  With testing package for 4.8 kernel: ppa:canonical-kernel-team/unstable

  Suspend by closing lid or setting menu, both randomly(2 out of 3
  times) cause system reboot after suspend.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: systemd 231-6git1
  ProcVersionSignature: Ubuntu 4.8.0-14.15-generic 4.8.0-rc7
  Uname: Linux 4.8.0-14-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Sep 22 18:07:09 2016
  InstallationDate: Installed on 2016-09-22 (0 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160918)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0bda:5682 Realtek Semiconductor Corp. 
   Bus 001 Device 003: ID 04f3:20d0 Elan Microelectronics Corp. 
   Bus 001 Device 002: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 13 9350
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-14-generic.efi.signed 
root=UUID=5ce90c47-3ebd-4119-9522-ad3d23f95ce3 ro quiet splash vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/14/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.4.4
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.4.4:bd06/14/2016:svnDellInc.:pnXPS139350:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 13 9350
  dmi.sys.vendor: Dell Inc.

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

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