date:20170825

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

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

** Tags removed: block-proposed-vivid

** Tags removed: block-proposed

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

Title:
  linux: 3.19.0-92.100 -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:
  Invalid
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Vivid:
  Confirmed

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

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

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

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

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

[Kernel-packages] [Bug 1713035] [NEW] Artful update to v4.12.9 stable release

2017-08-25 Thread Cristian Aravena Romero

Public bug reported:

Hello,

https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-
stable.git/commit/?h=linux-4.12.y

Regards,
--
Cristian

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: linux-image-4.12.0-11-generic 4.12.0-11.12
ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
Uname: Linux 4.12.0-11-generic x86_64
ApportVersion: 2.20.6-0ubuntu7
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  caravena   2546 F pulseaudio
CurrentDesktop: GNOME
Date: Fri Aug 25 08:29:07 2017
HibernationDevice: RESUME=UUID=360bd2d2-4f44-4311-86d6-4781ac81ee87
InstallationDate: Installed on 2017-07-05 (50 days ago)
InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.12.0-11-generic 
root=UUID=6b614287-8ce5-49c5-b66d-e92fa9568c2b ro rootflags=subvol=@ quiet 
splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-4.12.0-11-generic N/A
 linux-backports-modules-4.12.0-11-generic  N/A
 linux-firmware 1.167
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/15/2013
dmi.bios.vendor: Phoenix Technologies Ltd.
dmi.bios.version: P14AAJ
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: SAMSUNG_NP1234567890
dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.board.version: FAB1
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 9
dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.chassis.version: 0.1
dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvrP14AAJ:bd04/15/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1:
dmi.product.family: ChiefRiver System
dmi.product.name: 530U3C/530U4C
dmi.product.version: 0.1
dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

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


** Tags: amd64 apport-bug artful upgrade-software-version

** Summary changed:

- Artful update to v4.12.8 stable release
+ Artful update to v4.12.9 stable release

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

Title:
  Artful update to v4.12.9 stable release

Status in linux package in Ubuntu:
  New

Bug description:
  Hello,

  https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-
  stable.git/commit/?h=linux-4.12.y

  Regards,
  --
  Cristian

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.12.0-11-generic 4.12.0-11.12
  ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
  Uname: Linux 4.12.0-11-generic x86_64
  ApportVersion: 2.20.6-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  caravena   2546 F pulseaudio
  CurrentDesktop: GNOME
  Date: Fri Aug 25 08:29:07 2017
  HibernationDevice: RESUME=UUID=360bd2d2-4f44-4311-86d6-4781ac81ee87
  InstallationDate: Installed on 2017-07-05 (50 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.12.0-11-generic 
root=UUID=6b614287-8ce5-49c5-b66d-e92fa9568c2b ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.12.0-11-generic N/A
   linux-backports-modules-4.12.0-11-generic  N/A
   linux-firmware 1.167
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/15/2013
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: P14AAJ
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: SAMSUNG_NP1234567890
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: FAB1
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvrP14AAJ:bd04/15/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1:
  dmi.product.family: ChiefRiver System
  dmi.product.name: 530U3C/530U4C
  dmi.product.version: 0.1
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

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

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

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

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

Title:
  Artful update to v4.12.9 stable release

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hello,

  https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-
  stable.git/commit/?h=linux-4.12.y

  Regards,
  --
  Cristian

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.12.0-11-generic 4.12.0-11.12
  ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
  Uname: Linux 4.12.0-11-generic x86_64
  ApportVersion: 2.20.6-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  caravena   2546 F pulseaudio
  CurrentDesktop: GNOME
  Date: Fri Aug 25 08:29:07 2017
  HibernationDevice: RESUME=UUID=360bd2d2-4f44-4311-86d6-4781ac81ee87
  InstallationDate: Installed on 2017-07-05 (50 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.12.0-11-generic 
root=UUID=6b614287-8ce5-49c5-b66d-e92fa9568c2b ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.12.0-11-generic N/A
   linux-backports-modules-4.12.0-11-generic  N/A
   linux-firmware 1.167
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/15/2013
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: P14AAJ
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: SAMSUNG_NP1234567890
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: FAB1
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvrP14AAJ:bd04/15/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1:
  dmi.product.family: ChiefRiver System
  dmi.product.name: 530U3C/530U4C
  dmi.product.version: 0.1
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

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

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

[Kernel-packages] [Bug 1712804] Re: 4.12.0-11-generic rejects kernel modules signed with enrolled key

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

** This bug has been marked a duplicate of bug 1712168
   Linux 4.12 refuses to load self-signed modules under Secure Boot with 
properly enrolled keys

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

Title:
  4.12.0-11-generic rejects kernel modules signed with enrolled key

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hi,

  I've been signing my DKMS modules manually for some time and it was
  working just fine with 17.04 but since I upgraded to 17.10 and signing
  the modules again the kernel rejects them.

  Version: Ubuntu 4.12.0-11.12-generic 4.12.5

  ```
  $ sudo mokutil --import MOK.der 
  SKIP: MOK.der is already enrolled

  $ sudo /usr/src/linux-headers-4.12.0-11-generic/scripts/sign-file
  sha512 MOK.priv MOK.der
  /lib/modules/4.12.0-11-generic/updates/dkms/vboxdrv.ko

  $ sudo hexdump -C /lib/modules/4.12.0-11-generic/updates/dkms/vboxdrv.ko | 
tail
  00085530  73 59 c9 38 05 53 a3 95  df df c6 ca 93 ef ad 87  |sY.8.S..|
  00085540  38 52 a4 41 4b b6 79 e7  1f 02 49 d7 ba 7c 60 21  |8R.AK.y...I..|`!|
  00085550  94 9a b8 c2 d2 73 68 91  fc e8 12 c1 e9 68 21 eb  |.sh..h!.|
  00085560  55 d1 0b 6f 4e 04 ee b2  e7 a7 47 42 07 bb 0e 3b  |U..oN.GB...;|
  00085570  8a fa 9c d0 7f 1e d5 af  92 8a a3 db 13 32 6d f1  |.2m.|
  00085580  c0 c7 6a 31 c6 39 39 14  0d ec 19 73 7e 14 1b e6  |..j1.99s~...|
  00085590  8d 1b 5c 7a 0c 26 00 00  02 00 00 00 00 00 00 00  |..\z.&..|
  000855a0  01 8b 7e 4d 6f 64 75 6c  65 20 73 69 67 6e 61 74  |..~Module signat|
  000855b0  75 72 65 20 61 70 70 65  6e 64 65 64 7e 0a|ure appended~.|
  000855be

  $ sudo modprobe vboxdrv
  modprobe: ERROR: could not insert 'vboxdrv': Required key not available
  ```

  dmesg shows:
  ```
  [260594.834844] PKCS#7 signature not signed with a trusted key
  ```

  It also seems like modinfo doesn't recognize/shows the signing
  details:

  ```
  $ sudo modinfo /lib/modules/4.12.0-11-generic/updates/dkms/vboxdrv.ko
  filename:   /lib/modules/4.12.0-11-generic/updates/dkms/vboxdrv.ko
  version:5.1.26_Ubuntu r117224 (0x002a)
  license:GPL
  description:Oracle VM VirtualBox Support Driver
  author: Oracle Corporation
  srcversion: 135FF31DCB56FAD62FFCD36
  depends:
  vermagic:   4.12.0-11-generic SMP mod_unload 
  signat: PKCS#7
  signer: 
  sig_key:
  sig_hashalgo:   md4
  parm:   force_async_tsc:force the asynchronous TSC mode (int)
  ```

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

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

[Kernel-packages] [Bug 1713051] [NEW] package linux-image-4.4.0-92-generic 4.4.0-92.115 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

2017-08-25 Thread KVG Rao

Public bug reported:

oracle java

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-92-generic 4.4.0-92.115
ProcVersionSignature: Ubuntu 4.4.0-62.83-generic 4.4.40
Uname: Linux 4.4.0-62-generic i686
ApportVersion: 2.14.1-0ubuntu3.25
Architecture: i386
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  kvg1933 F pulseaudio
Date: Fri Aug 25 16:36:37 2017
DuplicateSignature: 
package:linux-image-4.4.0-92-generic:4.4.0-92.115:subprocess installed 
post-installation script returned error exit status 1
ErrorMessage: subprocess installed post-installation script returned error exit 
status 1
InstallationDate: Installed on 2016-02-13 (559 days ago)
InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta i386 (20150805)
MachineType: Acer Aspire 4738Z
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-62-generic 
root=UUID=f110cdde-d212-475b-b683-1e305b54 ro quiet splash
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
 dpkg 1.17.5ubuntu5.7
 apt  1.0.1ubuntu2.17
SourcePackage: linux
Title: package linux-image-4.4.0-92-generic 4.4.0-92.115 failed to 
install/upgrade: subprocess installed post-installation script returned error 
exit status 1
UpgradeStatus: Upgraded to xenial on 2017-08-25 (0 days ago)
dmi.bios.date: 09/10/2010
dmi.bios.vendor: INSYDE
dmi.bios.version: V1.06
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: JE41_CP
dmi.board.vendor: Acer
dmi.board.version: Base Board Version
dmi.chassis.type: 10
dmi.chassis.vendor: Chassis Manufacturer
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnINSYDE:bvrV1.06:bd09/10/2010:svnAcer:pnAspire4738Z:pvrV1.06:rvnAcer:rnJE41_CP:rvrBaseBoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion:
dmi.product.name: Aspire 4738Z
dmi.product.version: V1.06
dmi.sys.vendor: Acer

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


** Tags: apport-package i386 need-duplicate-check third-party-packages xenial

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

Title:
  package linux-image-4.4.0-92-generic 4.4.0-92.115 failed to
  install/upgrade: subprocess installed post-installation script
  returned error exit status 1

Status in linux package in Ubuntu:
  New

Bug description:
  oracle java

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-92-generic 4.4.0-92.115
  ProcVersionSignature: Ubuntu 4.4.0-62.83-generic 4.4.40
  Uname: Linux 4.4.0-62-generic i686
  ApportVersion: 2.14.1-0ubuntu3.25
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  kvg1933 F pulseaudio
  Date: Fri Aug 25 16:36:37 2017
  DuplicateSignature: 
package:linux-image-4.4.0-92-generic:4.4.0-92.115:subprocess installed 
post-installation script returned error exit status 1
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2016-02-13 (559 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta i386 (20150805)
  MachineType: Acer Aspire 4738Z
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-62-generic 
root=UUID=f110cdde-d212-475b-b683-1e305b54 ro quiet splash
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   dpkg 1.17.5ubuntu5.7
   apt  1.0.1ubuntu2.17
  SourcePackage: linux
  Title: package linux-image-4.4.0-92-generic 4.4.0-92.115 failed to 
install/upgrade: subprocess installed post-installation script returned error 
exit status 1
  UpgradeStatus: Upgraded to xenial on 2017-08-25 (0 days ago)
  dmi.bios.date: 09/10/2010
  dmi.bios.vendor: INSYDE
  dmi.bios.version: V1.06
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: JE41_CP
  dmi.board.vendor: Acer
  dmi.board.version: Base Board Version
  dmi.chassis.type: 10
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnINSYDE:bvrV1.06:bd09/10/2010:svnAcer:pnAspire4738Z:pvrV1.06:rvnAcer:rnJE41_CP:rvrBaseBoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion:
  dmi.product.name: Aspire 4738Z
  dmi.product.version: V1.06
  dmi.sys.vendor: Acer

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

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

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

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

Title:
  package linux-image-4.4.0-92-generic 4.4.0-92.115 failed to
  install/upgrade: subprocess installed post-installation script
  returned error exit status 1

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  oracle java

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-92-generic 4.4.0-92.115
  ProcVersionSignature: Ubuntu 4.4.0-62.83-generic 4.4.40
  Uname: Linux 4.4.0-62-generic i686
  ApportVersion: 2.14.1-0ubuntu3.25
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  kvg1933 F pulseaudio
  Date: Fri Aug 25 16:36:37 2017
  DuplicateSignature: 
package:linux-image-4.4.0-92-generic:4.4.0-92.115:subprocess installed 
post-installation script returned error exit status 1
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2016-02-13 (559 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta i386 (20150805)
  MachineType: Acer Aspire 4738Z
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-62-generic 
root=UUID=f110cdde-d212-475b-b683-1e305b54 ro quiet splash
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   dpkg 1.17.5ubuntu5.7
   apt  1.0.1ubuntu2.17
  SourcePackage: linux
  Title: package linux-image-4.4.0-92-generic 4.4.0-92.115 failed to 
install/upgrade: subprocess installed post-installation script returned error 
exit status 1
  UpgradeStatus: Upgraded to xenial on 2017-08-25 (0 days ago)
  dmi.bios.date: 09/10/2010
  dmi.bios.vendor: INSYDE
  dmi.bios.version: V1.06
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: JE41_CP
  dmi.board.vendor: Acer
  dmi.board.version: Base Board Version
  dmi.chassis.type: 10
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnINSYDE:bvrV1.06:bd09/10/2010:svnAcer:pnAspire4738Z:pvrV1.06:rvnAcer:rnJE41_CP:rvrBaseBoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion:
  dmi.product.name: Aspire 4738Z
  dmi.product.version: V1.06
  dmi.sys.vendor: Acer

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

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

[Kernel-packages] [Bug 1713051] Re: package linux-image-4.4.0-92-generic 4.4.0-92.115 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

2017-08-25 Thread Apport retracing service

** Tags removed: need-duplicate-check

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

Title:
  package linux-image-4.4.0-92-generic 4.4.0-92.115 failed to
  install/upgrade: subprocess installed post-installation script
  returned error exit status 1

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  oracle java

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-92-generic 4.4.0-92.115
  ProcVersionSignature: Ubuntu 4.4.0-62.83-generic 4.4.40
  Uname: Linux 4.4.0-62-generic i686
  ApportVersion: 2.14.1-0ubuntu3.25
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  kvg1933 F pulseaudio
  Date: Fri Aug 25 16:36:37 2017
  DuplicateSignature: 
package:linux-image-4.4.0-92-generic:4.4.0-92.115:subprocess installed 
post-installation script returned error exit status 1
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2016-02-13 (559 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta i386 (20150805)
  MachineType: Acer Aspire 4738Z
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-62-generic 
root=UUID=f110cdde-d212-475b-b683-1e305b54 ro quiet splash
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   dpkg 1.17.5ubuntu5.7
   apt  1.0.1ubuntu2.17
  SourcePackage: linux
  Title: package linux-image-4.4.0-92-generic 4.4.0-92.115 failed to 
install/upgrade: subprocess installed post-installation script returned error 
exit status 1
  UpgradeStatus: Upgraded to xenial on 2017-08-25 (0 days ago)
  dmi.bios.date: 09/10/2010
  dmi.bios.vendor: INSYDE
  dmi.bios.version: V1.06
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: JE41_CP
  dmi.board.vendor: Acer
  dmi.board.version: Base Board Version
  dmi.chassis.type: 10
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnINSYDE:bvrV1.06:bd09/10/2010:svnAcer:pnAspire4738Z:pvrV1.06:rvnAcer:rnJE41_CP:rvrBaseBoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion:
  dmi.product.name: Aspire 4738Z
  dmi.product.version: V1.06
  dmi.sys.vendor: Acer

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

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

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

** Tags added: regression-testing-passed

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

Title:
  linux: 4.12.0-12.13 -proposed tracker

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

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

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

  -- swm properties --
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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

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

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

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

Title:
  linux: 4.12.0-12.13 -proposed tracker

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

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

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

  -- swm properties --
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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

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

2017-08-25 Thread Kleber Sacilotto de Souza

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

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

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

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

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

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

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

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

[Kernel-packages] [Bug 1574341] Re: [Asus T300 CHI] Synaptics Touch Digitizer V04 - no multitouch

this bug affects my asus t300 chi. Tried a bunch of things to no avail.
I'll try to add the normally requested attachments. Any help
appreciated.

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

Title:
  [Asus T300 CHI] Synaptics Touch Digitizer V04 - no multitouch

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Triaged
Status in xinput package in Ubuntu:
  Triaged

Bug description:
  This is a related but separate issue to bug #1480673  "Asus T300 CHI
  bluetooth Touchpad is recognized incorrectly".

  Affecting this digitizer is also bug #1574028 "Asus T300 CHI:
  touchscreen digitiser missing at boot".

  Using 16.04 amd64 Ubuntu (unity).

  In this case the USB-attached "Synaptics Touch Digitizer V04" fails to
  provide any multitouch functionality.

  'evtest' shows multitouch events happening.

  $ lsusb
  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 001 Device 007: ID 06cb:11ef Synaptics, Inc.
  Bus 001 Device 005: ID 04f2:b3d5 Chicony Electronics Co., Ltd
  Bus 001 Device 003: ID 8087:0a2a Intel Corp.
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

  ~$ xinput --list
  ⎡ Virtual core pointer  id=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointerid=4[slave  pointer  (2)]
  ⎜   ↳ ASUS T300CHI DOCKING  id=9[slave  pointer  (2)]
  ⎜   ↳ SYNAPTICS Synaptics Touch Digitizer V04   id=11   [slave  pointer  (2)]
  ⎜   ↳ SYNAPTICS Synaptics Touch Digitizer V04 Pen   id=12   [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)]
  ↳ Sleep Button  id=8[slave  keyboard (3)]
  ↳ USB2.0 HD UVC WebCam  id=10   [slave  keyboard (3)]
  ↳ Asus WMI hotkeys  id=13   [slave  keyboard (3)]
  ↳ AT Translated Set 2 keyboard  id=14   [slave  keyboard (3)]
  ↳ ASUS T300CHI DOCKING  id=15   [slave  keyboard (3)]

  $ ll /sys/bus/hid/drivers/hid-multitouch/
  total 0
  drwxr-xr-x 2 root root0 Apr 24 18:12 ./
  drwxr-xr-x 4 root root0 Apr 24 18:12 ../
  lrwxrwxrwx 1 root root0 Apr 24 18:12 0003:06CB:11EF.0003 -> 
../../../../devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/0003:06CB:11EF.0003/
  --w--- 1 root root 4096 Apr 24 18:12 bind
  lrwxrwxrwx 1 root root0 Apr 24 18:12 module -> 
../../../../module/hid_multitouch/
  --w--- 1 root root 4096 Apr 24 18:12 new_id
  --w--- 1 root root 4096 Apr 24 18:12 uevent
  --w--- 1 root root 4096 Apr 24 18:12 unbind

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

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

[Kernel-packages] [Bug 1574341] Re: [Asus T300 CHI] Synaptics Touch Digitizer V04 - no multitouch

** Attachment added: "devices"
   
https://bugs.launchpad.net/ubuntu/+source/xinput/+bug/1574341/+attachment/4938667/+files/devices

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

Title:
  [Asus T300 CHI] Synaptics Touch Digitizer V04 - no multitouch

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Triaged
Status in xinput package in Ubuntu:
  Triaged

Bug description:
  This is a related but separate issue to bug #1480673  "Asus T300 CHI
  bluetooth Touchpad is recognized incorrectly".

  Affecting this digitizer is also bug #1574028 "Asus T300 CHI:
  touchscreen digitiser missing at boot".

  Using 16.04 amd64 Ubuntu (unity).

  In this case the USB-attached "Synaptics Touch Digitizer V04" fails to
  provide any multitouch functionality.

  'evtest' shows multitouch events happening.

  $ lsusb
  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 001 Device 007: ID 06cb:11ef Synaptics, Inc.
  Bus 001 Device 005: ID 04f2:b3d5 Chicony Electronics Co., Ltd
  Bus 001 Device 003: ID 8087:0a2a Intel Corp.
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

  ~$ xinput --list
  ⎡ Virtual core pointer  id=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointerid=4[slave  pointer  (2)]
  ⎜   ↳ ASUS T300CHI DOCKING  id=9[slave  pointer  (2)]
  ⎜   ↳ SYNAPTICS Synaptics Touch Digitizer V04   id=11   [slave  pointer  (2)]
  ⎜   ↳ SYNAPTICS Synaptics Touch Digitizer V04 Pen   id=12   [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)]
  ↳ Sleep Button  id=8[slave  keyboard (3)]
  ↳ USB2.0 HD UVC WebCam  id=10   [slave  keyboard (3)]
  ↳ Asus WMI hotkeys  id=13   [slave  keyboard (3)]
  ↳ AT Translated Set 2 keyboard  id=14   [slave  keyboard (3)]
  ↳ ASUS T300CHI DOCKING  id=15   [slave  keyboard (3)]

  $ ll /sys/bus/hid/drivers/hid-multitouch/
  total 0
  drwxr-xr-x 2 root root0 Apr 24 18:12 ./
  drwxr-xr-x 4 root root0 Apr 24 18:12 ../
  lrwxrwxrwx 1 root root0 Apr 24 18:12 0003:06CB:11EF.0003 -> 
../../../../devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/0003:06CB:11EF.0003/
  --w--- 1 root root 4096 Apr 24 18:12 bind
  lrwxrwxrwx 1 root root0 Apr 24 18:12 module -> 
../../../../module/hid_multitouch/
  --w--- 1 root root 4096 Apr 24 18:12 new_id
  --w--- 1 root root 4096 Apr 24 18:12 uevent
  --w--- 1 root root 4096 Apr 24 18:12 unbind

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

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

[Kernel-packages] [Bug 1574341] Re: [Asus T300 CHI] Synaptics Touch Digitizer V04 - no multitouch

** Attachment added: "Xorg.0.log"
   
https://bugs.launchpad.net/ubuntu/+source/xinput/+bug/1574341/+attachment/4938669/+files/Xorg.0.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/1574341

Title:
  [Asus T300 CHI] Synaptics Touch Digitizer V04 - no multitouch

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Triaged
Status in xinput package in Ubuntu:
  Triaged

Bug description:
  This is a related but separate issue to bug #1480673  "Asus T300 CHI
  bluetooth Touchpad is recognized incorrectly".

  Affecting this digitizer is also bug #1574028 "Asus T300 CHI:
  touchscreen digitiser missing at boot".

  Using 16.04 amd64 Ubuntu (unity).

  In this case the USB-attached "Synaptics Touch Digitizer V04" fails to
  provide any multitouch functionality.

  'evtest' shows multitouch events happening.

  $ lsusb
  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 001 Device 007: ID 06cb:11ef Synaptics, Inc.
  Bus 001 Device 005: ID 04f2:b3d5 Chicony Electronics Co., Ltd
  Bus 001 Device 003: ID 8087:0a2a Intel Corp.
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

  ~$ xinput --list
  ⎡ Virtual core pointer  id=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointerid=4[slave  pointer  (2)]
  ⎜   ↳ ASUS T300CHI DOCKING  id=9[slave  pointer  (2)]
  ⎜   ↳ SYNAPTICS Synaptics Touch Digitizer V04   id=11   [slave  pointer  (2)]
  ⎜   ↳ SYNAPTICS Synaptics Touch Digitizer V04 Pen   id=12   [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)]
  ↳ Sleep Button  id=8[slave  keyboard (3)]
  ↳ USB2.0 HD UVC WebCam  id=10   [slave  keyboard (3)]
  ↳ Asus WMI hotkeys  id=13   [slave  keyboard (3)]
  ↳ AT Translated Set 2 keyboard  id=14   [slave  keyboard (3)]
  ↳ ASUS T300CHI DOCKING  id=15   [slave  keyboard (3)]

  $ ll /sys/bus/hid/drivers/hid-multitouch/
  total 0
  drwxr-xr-x 2 root root0 Apr 24 18:12 ./
  drwxr-xr-x 4 root root0 Apr 24 18:12 ../
  lrwxrwxrwx 1 root root0 Apr 24 18:12 0003:06CB:11EF.0003 -> 
../../../../devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/0003:06CB:11EF.0003/
  --w--- 1 root root 4096 Apr 24 18:12 bind
  lrwxrwxrwx 1 root root0 Apr 24 18:12 module -> 
../../../../module/hid_multitouch/
  --w--- 1 root root 4096 Apr 24 18:12 new_id
  --w--- 1 root root 4096 Apr 24 18:12 uevent
  --w--- 1 root root 4096 Apr 24 18:12 unbind

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

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

[Kernel-packages] [Bug 1574341] Re: [Asus T300 CHI] Synaptics Touch Digitizer V04 - no multitouch

** Attachment added: "uname"
   
https://bugs.launchpad.net/ubuntu/+source/xinput/+bug/1574341/+attachment/4938670/+files/uname

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

Title:
  [Asus T300 CHI] Synaptics Touch Digitizer V04 - no multitouch

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Triaged
Status in xinput package in Ubuntu:
  Triaged

Bug description:
  This is a related but separate issue to bug #1480673  "Asus T300 CHI
  bluetooth Touchpad is recognized incorrectly".

  Affecting this digitizer is also bug #1574028 "Asus T300 CHI:
  touchscreen digitiser missing at boot".

  Using 16.04 amd64 Ubuntu (unity).

  In this case the USB-attached "Synaptics Touch Digitizer V04" fails to
  provide any multitouch functionality.

  'evtest' shows multitouch events happening.

  $ lsusb
  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 001 Device 007: ID 06cb:11ef Synaptics, Inc.
  Bus 001 Device 005: ID 04f2:b3d5 Chicony Electronics Co., Ltd
  Bus 001 Device 003: ID 8087:0a2a Intel Corp.
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

  ~$ xinput --list
  ⎡ Virtual core pointer  id=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointerid=4[slave  pointer  (2)]
  ⎜   ↳ ASUS T300CHI DOCKING  id=9[slave  pointer  (2)]
  ⎜   ↳ SYNAPTICS Synaptics Touch Digitizer V04   id=11   [slave  pointer  (2)]
  ⎜   ↳ SYNAPTICS Synaptics Touch Digitizer V04 Pen   id=12   [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)]
  ↳ Sleep Button  id=8[slave  keyboard (3)]
  ↳ USB2.0 HD UVC WebCam  id=10   [slave  keyboard (3)]
  ↳ Asus WMI hotkeys  id=13   [slave  keyboard (3)]
  ↳ AT Translated Set 2 keyboard  id=14   [slave  keyboard (3)]
  ↳ ASUS T300CHI DOCKING  id=15   [slave  keyboard (3)]

  $ ll /sys/bus/hid/drivers/hid-multitouch/
  total 0
  drwxr-xr-x 2 root root0 Apr 24 18:12 ./
  drwxr-xr-x 4 root root0 Apr 24 18:12 ../
  lrwxrwxrwx 1 root root0 Apr 24 18:12 0003:06CB:11EF.0003 -> 
../../../../devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/0003:06CB:11EF.0003/
  --w--- 1 root root 4096 Apr 24 18:12 bind
  lrwxrwxrwx 1 root root0 Apr 24 18:12 module -> 
../../../../module/hid_multitouch/
  --w--- 1 root root 4096 Apr 24 18:12 new_id
  --w--- 1 root root 4096 Apr 24 18:12 uevent
  --w--- 1 root root 4096 Apr 24 18:12 unbind

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

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

[Kernel-packages] [Bug 1574341] Re: [Asus T300 CHI] Synaptics Touch Digitizer V04 - no multitouch

** Attachment added: "xinput"
   
https://bugs.launchpad.net/ubuntu/+source/xinput/+bug/1574341/+attachment/4938668/+files/xinput

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

Title:
  [Asus T300 CHI] Synaptics Touch Digitizer V04 - no multitouch

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Triaged
Status in xinput package in Ubuntu:
  Triaged

Bug description:
  This is a related but separate issue to bug #1480673  "Asus T300 CHI
  bluetooth Touchpad is recognized incorrectly".

  Affecting this digitizer is also bug #1574028 "Asus T300 CHI:
  touchscreen digitiser missing at boot".

  Using 16.04 amd64 Ubuntu (unity).

  In this case the USB-attached "Synaptics Touch Digitizer V04" fails to
  provide any multitouch functionality.

  'evtest' shows multitouch events happening.

  $ lsusb
  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 001 Device 007: ID 06cb:11ef Synaptics, Inc.
  Bus 001 Device 005: ID 04f2:b3d5 Chicony Electronics Co., Ltd
  Bus 001 Device 003: ID 8087:0a2a Intel Corp.
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

  ~$ xinput --list
  ⎡ Virtual core pointer  id=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointerid=4[slave  pointer  (2)]
  ⎜   ↳ ASUS T300CHI DOCKING  id=9[slave  pointer  (2)]
  ⎜   ↳ SYNAPTICS Synaptics Touch Digitizer V04   id=11   [slave  pointer  (2)]
  ⎜   ↳ SYNAPTICS Synaptics Touch Digitizer V04 Pen   id=12   [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)]
  ↳ Sleep Button  id=8[slave  keyboard (3)]
  ↳ USB2.0 HD UVC WebCam  id=10   [slave  keyboard (3)]
  ↳ Asus WMI hotkeys  id=13   [slave  keyboard (3)]
  ↳ AT Translated Set 2 keyboard  id=14   [slave  keyboard (3)]
  ↳ ASUS T300CHI DOCKING  id=15   [slave  keyboard (3)]

  $ ll /sys/bus/hid/drivers/hid-multitouch/
  total 0
  drwxr-xr-x 2 root root0 Apr 24 18:12 ./
  drwxr-xr-x 4 root root0 Apr 24 18:12 ../
  lrwxrwxrwx 1 root root0 Apr 24 18:12 0003:06CB:11EF.0003 -> 
../../../../devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/0003:06CB:11EF.0003/
  --w--- 1 root root 4096 Apr 24 18:12 bind
  lrwxrwxrwx 1 root root0 Apr 24 18:12 module -> 
../../../../module/hid_multitouch/
  --w--- 1 root root 4096 Apr 24 18:12 new_id
  --w--- 1 root root 4096 Apr 24 18:12 uevent
  --w--- 1 root root 4096 Apr 24 18:12 unbind

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

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

[Kernel-packages] [Bug 1713035] Re: Artful update to v4.12.9 stable release

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

Title:
  Artful update to v4.12.9 stable release

Status in linux package in Ubuntu:
  Invalid

Bug description:
  Hello,

  https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-
  stable.git/commit/?h=linux-4.12.y

  Regards,
  --
  Cristian

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.12.0-11-generic 4.12.0-11.12
  ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
  Uname: Linux 4.12.0-11-generic x86_64
  ApportVersion: 2.20.6-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  caravena   2546 F pulseaudio
  CurrentDesktop: GNOME
  Date: Fri Aug 25 08:29:07 2017
  HibernationDevice: RESUME=UUID=360bd2d2-4f44-4311-86d6-4781ac81ee87
  InstallationDate: Installed on 2017-07-05 (50 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.12.0-11-generic 
root=UUID=6b614287-8ce5-49c5-b66d-e92fa9568c2b ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.12.0-11-generic N/A
   linux-backports-modules-4.12.0-11-generic  N/A
   linux-firmware 1.167
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/15/2013
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: P14AAJ
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: SAMSUNG_NP1234567890
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: FAB1
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvrP14AAJ:bd04/15/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1:
  dmi.product.family: ChiefRiver System
  dmi.product.name: 530U3C/530U4C
  dmi.product.version: 0.1
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

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

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

[Kernel-packages] [Bug 1712508] Re: Disappearing screen and flickering after upgrade to 16.04

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

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

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

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

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.13-rc6

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

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

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

Title:
Disappearing screen and flickering after upgrade to 16.04

Status in linux package in Ubuntu:
Incomplete

Bug description:
I have two Lenovo T410s that I upgraded from 14.04 to 16.04.
Since then, one is working fine while the other shows mainly an ever
disappearing screen and flickering.

I have asked here:
https://askubuntu.com/questions/947233/i-upgraded-from-kubuntu-14-04-lts-to-16-04-lts-and-now-my-screen-shows-up-and-di?noredirect=1#comment1506995_947233
I also found I am not the only one:
https://askubuntu.com/questions/927407/flickering-screen-with-intel-graphics-on-ubuntu-17-04?noredirect=1#comment1507937_927407
The latter has tried pretty much that could be tried already, to no avail.

I think that I can help with this problem, since my two T410s are
identical in hard- and software, including BIOS, except that one is a
type 2924 (with NVIDIA-card, though disabled in the BIOS), and the
other one is a 2904 (without NVIDIA card).

I have checked for differences at boot time and found DMAR as major
difference:
T410s, 2924: [ 0.335616] DMAR: Disabling batched IOTLB flush on Ironlake
T410s, 2904: [ 0.355681] DMAR: BIOS has allocated no shadow GTT; disabling
IOMMU for graphics

Should this be initially at the root of the problem, I'd consider the
kernel package as responsible, therefore I marked it as above.

The outputs of lspci -k | grep -EA3 'VGA|3D|Display' are identical to
the point.

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

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

[Kernel-packages] [Bug 1709179] Re: Drop GPL from of_node_to_nid() export to match other arches

** Changed in: linux (Ubuntu)
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Joseph 
Salisbury (jsalisbury)

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

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

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

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

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

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

Title:
  Drop GPL from of_node_to_nid() export to match other arches

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

Bug description:
  == Comment: #0 - Reza A. Arbab  - 2017-08-07 15:34:04 ==
  We need to backport mainline commit be9ba9ff93cc ("Drop GPL from 
of_node_to_nid() export to match other arches") to the Ubuntu 4.10 kernel.

  This exposes functionality needed by the Nvidia device driver on
  POWER9.

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

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

[Kernel-packages] [Bug 1712427] Re: No audio output to Speakers when HDMI cable removed

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

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

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

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

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


Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.13-rc6

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

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

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

Title:
  No audio output to Speakers when HDMI cable removed

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  The Sound Settings dialog in Unity allows to switch between various
  audio outputs.

  If HDMI is selected and the cable removed the dialog shows that Speakers are 
selected. But there is no audio. To actually output audio to speakers one needs 
to click some other output ("Simultaneous output ...") and then again on 
Speakers.
  The expected behaviour would be to actually play audio on the speakers 
without the need to switch forth and back.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  brain  2435 F pulseaudio
   /dev/snd/controlC1:  brain  2435 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=5165b586-2b44-4e4b-be49-177090e3b609
  InstallationDate: Installed on 2015-05-26 (819 days ago)
  InstallationMedia: Kubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: ASUSTeK COMPUTER INC. N501JW
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-33-generic 
root=UUID=299cfed8-e49e-40d4-a8dd-fd66089e6d8a ro quiet splash 
iwlwifi.power_save=1 iwlwifi.power_level=5 acpi_osi= acpi_backlight=vendor 
acpi_enforce_resources=lax acpi=force nmi_watchdog=0 drm.vblankoffdelay=1 
i915.semaphores=1 i915.enable_rc6=7 i915.lvds_downclock=1 
rcutree.rcu_idle_gp_delay=1 pcie_aspm=force i915.enable_psr=1 i915.enable_fbc=1 
i915.disable_power_well=1 vt.handoff=7
  ProcVersionSignature: Ubuntu 4.10.0-33.37~16.04.1-generic 4.10.17
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-33-generic N/A
   linux-backports-modules-4.10.0-33-generic  N/A
   linux-firmware 1.157.12
  Tags:  xenial
  Uname: Linux 4.10.0-33-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm bumblebee cdrom dialout dip disk lp lpadmin opt plugdev 
sambashare sudo vboxusers wireshark
  _MarkForUpload: True
  dmi.bios.date: 08/03/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: N501JW.210
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: N501JW
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrN501JW.210:bd08/03/2015:svnASUSTeKCOMPUTERINC.:pnN501JW:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnN501JW:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: N501JW
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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

[Kernel-packages] [Bug 1333294] Re: 32-bit kernel HDD slow write speed

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

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

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

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


Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.13-rc6

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

** No longer affects: linux-meta-lts-trusty (Ubuntu)

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

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

Title:
  32-bit kernel HDD slow write speed

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Summary

  After upgrading my Ubuntu 32-bit from 12.04 to 14.04 the write
  performance is painfully slow (less than 4.6MB/s) of both my SSD
  drives. The read speed is still fine. I've tested with the latest
  version of System Rescue CD (4.2.0 at this time) to see if was a
  hardware problem. However the performance of my drives was even better
  better than using Ubuntu 12.04.

  I've also tried to make a fresh installation of Ubuntu 14.04 on a
  spare SSD drive of mine to see if its because I upgraded from 12.04.
  But after waiting 4 hours for it to install, I finally lost patience,
  and stopped the installation.

  I'm using the deadline scheduler, but it doesn't matter which one I
  use. I'm also using the lowlatency kernel, but using the generic
  kernel doesn't have any effect.

  I've tested with mechanical hard drives, and the problem also occurs
  there.

  I've also tried to update to the proposed updates, and updated to
  kernel 3.13.0-30.54, but problem still exists there.

  The only think that helps is telling the kernel only to address 8GB
  RAM using the "mem=8GB" kernel option, but that is obviously not a
  solution when I need to utilize all the 32GB RAM that I have .

  The reason that I use a 32-bit OS  is because most of the applications
  I use on my laptop are propriety software that only exists in 32-bit
  versions.


  Details

  Kernel version
  root@ubuntu:~# uname -a
  Linux fk20563 3.13.0-29-lowlatency #53-Ubuntu SMP PREEMPT Wed Jun 4 21:20:42 
UTC 2014 i686 i686 i686 GNU/Linux

  List hardware
  lshw > lshw.txt

  Timings of devices (which is also 4x slower than normal)
  root@ubuntu:~# hdparm -t /dev/sda && hdparm -t /dev/sda && hdparm -t /dev/sda
  /dev/sda:
   Timing buffered disk reads: 470 MB in  3.01 seconds = 156.33 MB/sec

  /dev/sda:
   Timing buffered disk reads: 530 MB in  3.03 seconds = 174.86 MB/sec

  /dev/sda:
   Timing buffered disk reads: 500 MB in  3.01 seconds = 166.36 MB/sec

  root@ubuntu:~# hdparm -t /dev/sdb && hdparm -t /dev/sdb && hdparm -t /dev/sdb
  /dev/sdb:
   Timing buffered disk reads: 500 MB in  3.32 seconds = 150.61 MB/sec

  /dev/sdb:
   Timing buffered disk reads: 508 MB in  3.03 seconds = 167.49 MB/sec

  /dev/sdb:
   Timing buffered disk reads: 500 MB in  3.21 seconds = 155.81 MB/sec

  SSD partition alignment check
  root@ubuntu:~# fdisk -l

  Disk /dev/sda: 256.1 GB, 256060514304 bytes
  255 heads, 63 sectors/track, 31130 cylinders, total 500118192 sectors
  Units = sectors of 1 * 512 = 512 bytes
  Sector size (logical/physical): 512 bytes / 512 bytes
  I/O size (minimum/optimal): 512 bytes / 512 bytes
  Disk identifier: 0xd162fc6d

  Device Boot Start End Blocks Id System
  /dev/sda1 2048 483332095 241665024 83 Linux
  /dev/sda2 483332096 500117503 8392704 5 Extended
  /dev/sda5 483334144 500117503 8391680 82 Linux swap / Solaris

  Disk /dev/sdb: 480.1 GB, 480103981056 bytes
  255 heads, 63 sectors/track, 58369 cylinders, total 937703088 sectors
  Units = sectors of 1 * 512 = 512 bytes
  Sector size (logical/physical): 512 bytes / 512 bytes
  I/O size (minimum/optimal): 512 bytes / 512 bytes
  Disk identifier: 0x

  Device Boot Start End Blocks Id System
  /dev/sdb1 2048 937703087 468850520 83 Linux
  root@ubuntu:~# parted 
  GNU Parted 2.3
  Using /dev/sda
  Welcome to GNU Parted! Type 'help' to view a list of commands.
  (parted) select /dev/sda
  Using /dev/sda
  (parted) align-check opt 1 
  1 aligned
  (parted) select /dev/sdb
  Using /dev/sdb
  (parted) align-check opt 1 
  1 aligned
  (parted) quit 

  Scheduler:
  root@ubuntu:~# cat /sys/block/sd{a,b}/queue/scheduler
  noop [deadline] cfq 
  noop [deadline] cfq 

  Mount options:
  root@fk20563:~# mount | grep sda
  /dev/sda1 on / type ext4 (rw,noatime,nodiratime,errors=remount-ro,discard)
  root@fk20563:~# mount | grep sdb
  /dev/sdb1 on /media/vmware type xfs 
(rw,noatime,nodiratime,logbsize=256k,discard)

  FS read/write check of /dev/sda1 on Ubuntu
  root@fk20563:~# dd if=/dev/zero of=/

[Kernel-packages] [Bug 1713051] Re: package linux-image-4.4.0-92-generic 4.4.0-92.115 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

You may need to run the following from a terminal:

sudo apt-get install -f
sudo apt-get clean
sudo apt-get update

Then re-install the package or updates.

If that does not resolve your issue, please mark the bug as "Confirmed"

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

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

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

Title:
  package linux-image-4.4.0-92-generic 4.4.0-92.115 failed to
  install/upgrade: subprocess installed post-installation script
  returned error exit status 1

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  oracle java

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-92-generic 4.4.0-92.115
  ProcVersionSignature: Ubuntu 4.4.0-62.83-generic 4.4.40
  Uname: Linux 4.4.0-62-generic i686
  ApportVersion: 2.14.1-0ubuntu3.25
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  kvg1933 F pulseaudio
  Date: Fri Aug 25 16:36:37 2017
  DuplicateSignature: 
package:linux-image-4.4.0-92-generic:4.4.0-92.115:subprocess installed 
post-installation script returned error exit status 1
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2016-02-13 (559 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta i386 (20150805)
  MachineType: Acer Aspire 4738Z
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-62-generic 
root=UUID=f110cdde-d212-475b-b683-1e305b54 ro quiet splash
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   dpkg 1.17.5ubuntu5.7
   apt  1.0.1ubuntu2.17
  SourcePackage: linux
  Title: package linux-image-4.4.0-92-generic 4.4.0-92.115 failed to 
install/upgrade: subprocess installed post-installation script returned error 
exit status 1
  UpgradeStatus: Upgraded to xenial on 2017-08-25 (0 days ago)
  dmi.bios.date: 09/10/2010
  dmi.bios.vendor: INSYDE
  dmi.bios.version: V1.06
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: JE41_CP
  dmi.board.vendor: Acer
  dmi.board.version: Base Board Version
  dmi.chassis.type: 10
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnINSYDE:bvrV1.06:bd09/10/2010:svnAcer:pnAspire4738Z:pvrV1.06:rvnAcer:rnJE41_CP:rvrBaseBoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion:
  dmi.product.name: Aspire 4738Z
  dmi.product.version: V1.06
  dmi.sys.vendor: Acer

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

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

[Kernel-packages] [Bug 1712724] Re: s390 zKVM complains about "illegal operation" to s390/mm/pgalloc.c

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

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

** Tags added: kernel-da-key

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

Title:
  s390 zKVM complains about "illegal operation" to s390/mm/pgalloc.c

Status in linux package in Ubuntu:
  Triaged

Bug description:
  [  543.516708] kernel BUG at 
/build/linux-a7axPg/linux-4.12.0/arch/s390/mm/pgalloc.c:84!
  [  543.516783] illegal operation: 0001 ilc:1 [#1] SMP 
  [  543.516785] Modules linked in: xt_CHECKSUM iptable_mangle ipt_MASQUERADE 
nf_nat_masquerade_ipv4 iptable_nat xt_tcpudp bridge stp llc iptable_filter 
openvswitch nf_conntrack_ipv6 nf_nat_ipv6 nf_conntrack_ipv4 nf_defrag_ipv4 
nf_nat_ipv4 nf_defrag_ipv6 nf_nat nf_conntrack binfmt_misc zfs(PO) zunicode(PO) 
zavl(PO) zcommon(PO) znvpair(PO) spl(O) vfio_ccw vfio_mdev mdev 
vfio_iommu_type1 vfio ib_iser rdma_cm iw_cm ib_cm ib_core nfsd iscsi_tcp 
auth_rpcgss nfs_acl lockd grace libiscsi_tcp libiscsi sunrpc 
scsi_transport_iscsi ip_tables x_tables btrfs zlib_deflate raid10 raid456 
async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq 
libcrc32c raid1 raid0 linear ghash_s390 prng aes_s390 des_s390 des_generic 
sha512_s390 sha256_s390 virtio_net sha1_s390 sha_common virtio_blk virtio_scsi
  [  543.516828] CPU: 0 PID: 10024 Comm: task-size-overr Tainted: P   O 
   4.12.0-12-generic #13-Ubuntu
  [  543.516829] Hardware name: IBM 2964 N63 400 (KVM/Linux)
  [  543.516830] task: 0cdb9e00 task.stack: 099e8000
  [  543.516831] Krnl PSW : 0704d0018000 001274ec 
(crst_table_upgrade+0x124/0x130)
  [  543.516841]R:0 T:1 IO:1 EX:1 Key:0 M:1 W:0 P:0 AS:3 CC:1 PM:0 
RI:0 EA:3
  [  543.516842] Krnl GPRS: 0001 0400 243d7800 
0020
  [  543.516843]1000  0032 

  [  543.516844]8000 0020  
1000
  [  543.516845]0020 243d7800 001239f6 
099ebbe0
  [  543.516853] Krnl Code: 001274de: c0e5002446c1  brasl   
%r14,5b0260
  [  543.516853]001274e4: a7f4ffb8  brc 
15,127454
  [  543.516853]   #001274e8: a7f40001  brc 
15,1274ea
  [  543.516853]   >001274ec: a728fff4  lhi %r2,-12
  [  543.516853]001274f0: a7f4ffee  brc 
15,1274cc
  [  543.516853]001274f4: 0707  bcr 0,%r7
  [  543.516853]001274f6: 0707  bcr 0,%r7
  [  543.516853]001274f8: c004  brcl0,1274f8
  [  543.516862] Call Trace:
  [  543.516864] ([<085d8578>] 0x85d8578)
  [  543.516868]  [<002f529a>] get_unmapped_area+0x72/0x120 
  [  543.516870]  [<002f931a>] do_mmap+0xfa/0x3e0 
  [  543.516873]  [<002d6292>] vm_mmap_pgoff+0xca/0x120 
  [  543.516874]  [<002f6962>] SyS_mmap_pgoff+0x10a/0x2a0 
  [  543.516875]  [<002f6b72>] SyS_old_mmap+0x7a/0xa8 
  [  543.516880]  [<00864c1c>] system_call+0xc4/0x27c 
  [  543.516881] Last Breaking-Event-Address:
  [  543.516882]  [<001274e8>] crst_table_upgrade+0x120/0x130
  [  543.516883]  
  [  543.516883] ---[ end trace 036f94bf79a83905 ]---

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.12.0-12-generic 4.12.0-12.13
  ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8
  Uname: Linux 4.12.0-12-generic s390x
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 
2: ls: cannot access '/dev/snd/': No such file or directory
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.6-0ubuntu6
  Architecture: s390x
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  Date: Thu Aug 24 05:01:08 2017
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lspci:
   
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  PciMultimedia:
   
  ProcEnviron:
   TERM=vt220
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C
   SHELL=/bin/bash
  ProcFB: Error: [Errno 2] No such file or directory: '/proc/fb'
  ProcKernelCmdLine: root=UUID=d86dc8de-6ac8-4e4b-aba8-92872a209a8c 
crashkernel=196M
  RelatedPackageVersions:
   linux-restricted-modules-4.12.0-12-generic N/A
   linux-backports-modules-4.12.0-12-generic  N/A
   linux-firmware 1.167
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probabl

[Kernel-packages] [Bug 1712765] Re: reboot instead of shutdown

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

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

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

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

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


Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.13-rc6

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

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

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

Title:
  reboot instead of shutdown

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I have a Acer Aspire v5 571g laptop which initially had Windows
  installed. After I installed Ubuntu (and overwrote Windows) the
  computer shuts down when a restart is requested. Windows did not
  exhibit this problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-32-generic 4.10.0-32.36
  ProcVersionSignature: Ubuntu 4.10.0-32.36-generic 4.10.17
  Uname: Linux 4.10.0-32-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   felix  1929 F...m pulseaudio
   /dev/snd/controlC0:  felix  1929 F pulseaudio
  CurrentDesktop: Unity:Unity7
  Date: Thu Aug 24 10:24:56 2017
  HibernationDevice: RESUME=UUID=9aa9aa29-eb16-473f-b28d-5d6c340eac81
  InstallationDate: Installed on 2017-06-14 (70 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: Acer Aspire V5-571G
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-32-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-32-generic N/A
   linux-backports-modules-4.10.0-32-generic  N/A
   linux-firmware 1.164.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/12/2012
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: V1.12
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Aspire V5-571G
  dmi.board.vendor: Acer
  dmi.board.version: V1.12
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.12
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvrV1.12:bd06/12/2012:svnAcer:pnAspireV5-571G:pvrV1.12:rvnAcer:rnAspireV5-571G:rvrV1.12:cvnAcer:ct9:cvrV1.12:
  dmi.product.name: Aspire V5-571G
  dmi.product.version: V1.12
  dmi.sys.vendor: Acer

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

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

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

You may need to run the following from a terminal:

sudo apt-get install -f
sudo apt-get clean
sudo apt-get update

Then re-install the package or updates.

If that does not resolve your issue, please mark the bug as "Confirmed"


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

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

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

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

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  This was a distro provided on a magazine. A few years ago. I am trying to 
start using Linux but had to put this machine away for some time. Now I have 
come back to it to find this error. I have attempted to obtain updates and 
upgrades to no avail. I may try a different version of Linux if this does not 
work. Admittedly, it is an old portable computer but I did not like the idea of 
working equipment being sent for scrap or recycling.
  All the best. Ian

  ProblemType: Package
  DistroRelease: Ubuntu 15.04
  Package: linux-image-3.19.0-84-generic (not installed)
  ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3
  Uname: Linux 3.19.0-15-generic i686
  ApportVersion: 2.17.2-0ubuntu1.3
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ian 997 F pulseaudio
  Date: Thu Aug 24 12:35:12 2017
  DuplicateSignature: package:linux-image-3.19.0-84-generic:(not 
installed):subprocess new pre-installation script returned error exit status 1
  ErrorMessage: subprocess new pre-installation script returned error exit 
status 1
  HibernationDevice: RESUME=UUID=4e3df44a-93e5-40f0-a2d5-e09806eb9d50
  InstallationDate: Installed on 2015-08-29 (725 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release i386 (20150422)
  IwConfig:
   irda0 no wireless extensions.
   
   lono wireless extensions.
   
   eth0  no wireless extensions.
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: Hewlett-Packard HP Compaq nc6000 (DP894A#ABU)
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-15-generic 
root=UUID=23e721d5-1b3f-418c-bcab-e03f284d2e71 ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc 2.02~beta2-22ubuntu1.1
  RfKill:
   
  SourcePackage: linux
  Title: package linux-image-3.19.0-84-generic (not installed) failed to 
install/upgrade: subprocess new pre-installation script returned error exit 
status 1
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/23/2004
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68BDD Ver. F.0F
  dmi.board.name: 0890
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 8051 Version 1A.19
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68BDDVer.F.0F:bd07/23/2004:svnHewlett-Packard:pnHPCompaqnc6000(DP894A#ABU):pvrF.0F:rvnHewlett-Packard:rn0890:rvr8051Version1A.19:cvnHewlett-Packard:ct10:cvr:
  dmi.product.name: HP Compaq nc6000 (DP894A#ABU)
  dmi.product.version: F.0F
  dmi.sys.vendor: Hewlett-Packard

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

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

[Kernel-packages] [Bug 1712831] Re: 4.12.0-11-generic - crashing in infrastructure on i386 openvswitch tests

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

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

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

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


Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.13-rc6


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

** Tags added: kernel-da-key

** Tags removed: kernel-da-key
** Tags added: kernel-key

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

Title:
  4.12.0-11-generic - crashing in infrastructure on i386 openvswitch
  tests

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hi,
  this seems to me to be a kernel crash of some sorts.
  Somewhat in the spirit of older bugs:
  - bug 1630940
  - bug 1630578

  Xnox asked me to look into a hang on openvswitch dep8 tests.
  What I found initially was in the log just
"ERROR: Removing temporary files on testbed timed out"
  That message brought me to the two bugs above.

  But in there I read that this was the infra running dep8 crashing.
  So for a better bug report I tried to reproduce locally and that actually 
seems to work very reliable.

  To reproduce do:
  $ autopkgtest-buildvm-ubuntu-cloud -a i386 -r artful -s 10G
  $ pull-lp-source openvswitch
  $ autopkgtest --apt-upgrade --shell --no-built-binaries 
openvswitch_2.8.0~git20170809.7aa47a19d-0ubuntu1.dsc -- qemu 
~/work/autopkgtest-artful-i386.img
  # This guest currently will crash after a while of testing

  
  But with that running you can attach to the console and monitor of that guest.
  For example:
  $ sudo nc -U /tmp/autopkgtest-virt-qemu.*/ttyS0

  That gave me a crash on the hang which kind of matches the older bugs, here 
the console:
  [   54.256253] BUG: unable to handle kernel NULL pointer dereference at   
(null)
  [   54.257156] IP: add_grec+0x28/0x440
  [   54.257553] *pdpt = 1a869001 *pde =  
  [   54.257555] 
  [   54.258338] Oops:  [#1] SMP
  [   54.258638] Modules linked in: veth openvswitch nf_conntrack_ipv6 
nf_nat_ipv6 nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_defrag_ipv6 nf_nat 
nf_conntrack libcrc32c 9p fscache ppdev kvm_intel kvm irqbypass joydev 
input_leds serio_raw 9pnet_virtio parport_pc 9pnet parport qemu_fw_cfg 
i2c_piix4 mac_hid ip_tables x_tables autofs4 btrfs xor raid6_pq psmouse 
virtio_blk virtio_net floppy pata_acpi
  [   54.261891] CPU: 0 PID: 0 Comm: swapper/0 Tainted: GW   
4.12.0-11-generic #12-Ubuntu
  [   54.262715] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 
1.10.1-1ubuntu1~cloud0 04/01/2014
  [   54.263610] task: c7b622c0 task.stack: c7b5a000
  [   54.264039] EIP: add_grec+0x28/0x440
  [   54.264378] EFLAGS: 00010202 CPU: 0
  [   54.264711] EAX:  EBX: dd062540 ECX: 0006 EDX: dd062540
  [   54.265308] ESI: dd1e6e00 EDI: dd1e6e00 EBP: dbcc5f30 ESP: dbcc5ef0
  [   54.265793]  DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068
  [   54.266297] CR0: 80050033 CR2:  CR3: 1e930d80 CR4: 06f0
  [   54.266885] Call Trace:
  [   54.267120]  
  [   54.267349]  mld_ifc_timer_expire+0xfe/0x250
  [   54.267754]  ? mld_dad_timer_expire+0x50/0x50
  [   54.268173]  call_timer_fn+0x30/0x120
  [   54.268524]  ? mld_dad_timer_expire+0x50/0x50
  [   54.268942]  ? mld_dad_timer_expire+0x50/0x50
  [   54.269364]  run_timer_softirq+0x3c5/0x420
  [   54.269760]  ? __softirqentry_text_start+0x8/0x8
  [   54.270198]  __do_softirq+0xa9/0x245
  [   54.270539]  ? __softirqentry_text_start+0x8/0x8
  [   54.270976]  do_softirq_own_stack+0x24/0x30
  [   54.271373]  
  [   54.271611]  irq_exit+0xad/0xb0
  [   54.271913]  smp_apic_timer_interrupt+0x38/0x50
  [   54.272344]  apic_timer_interrupt+0x39/0x40
  [   54.272745] EIP: native_safe_halt+0x5/0x10
  [   54.273139] EFLAGS: 0246 CPU: 0
  [   54.273624] EAX:  EBX:  ECX: 0001 EDX: 
  [   54.274000] ESI:  EDI: c7b622c0 EBP: c7b5bf10 ESP: c7b5bf10
  [   54.274361]  DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068
  [   54.274687]  default_idle+0x1c/0xf0
  [   54.274896]  arch_cpu_idle+0xe/0x10
  [   54.275286]  default_idle_call+0x1e/0x30
  [   54.275787]  do_idle+0x145/0x1c0
  [   54.276092]  cpu_startup_entry+0x65/0x70
  [   54.276441]  rest_init+0x62/0x70
  [   54.276718]  start_kernel+0x3be/0x3d7
  [   54.276974]  i386_start_kernel+0x9d/0xa1
  [   54.277260]  startup_32_smp+0x16b/0x16d
  [   54.277509] Code: 00 00 00 3e 8d 74 26 00 55 89 e5 57 56 53 89 c6 83 ec 34 
89 4d e8 65 a1 14 00 00 00 89 45 f0 31 c0 8b 42 10 f6 42 48 08 89 45 cc <8b> 00 
c7 45 ec 00 00 00 00 89 45 c8 89 f0 0f 85 b4 02 00 00 8b
  [   54.279314]

[Kernel-packages] [Bug 1712626] Re: Cannot launch virtual instance on nova host after upgrading to kernel 4.4.0.92- works with 4.4.0.83

Can you test the kernel posted in comment #7 of bug 1709784 ?

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

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

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

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

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

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

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

Title:
  Cannot launch virtual instance on nova host after upgrading to kernel
  4.4.0.92- works with 4.4.0.83

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

Bug description:
  Host -- IBM Power 8  822L
  OS- Ubuntu 14.04 ppc64el
  previous kernel 3.19.0.68
  Nova Compute host using kvm - Openstack Liberty

  HWE was out of date so needed to update

  Steps:

  sudo apt-get install linux-generic-lts-xenial linux-image-generic-lts-xenial
  sudo init 6
  sudo apt update
  sudo apt upgrade
  sudo init 6

  afterwards - system seemed ok - kernel 4.4.0.92 installed

  However, launching a Ubuntu VM failed

  Aug 23 11:38:25 rcsnode03 kernel: [ 3270.246360] Facility 'TM' unavailable, 
exception at 0xd000189f85a0, MSR=90009033
  Aug 23 11:38:25 rcsnode03 kernel: [ 3270.246374] Oops: Unexpected facility 
unavailable exception, sig: 6 [#1]
  Aug 23 11:38:25 rcsnode03 kernel: [ 3270.246379] SMP NR_CPUS=2048 NUMA PowerNV
  Aug 23 11:38:25 rcsnode03 kernel: [ 3270.246385] Modules linked in: vhost_net 
vhost macvtap macvlan xt_REDIRECT nf_nat_redirect xt_mark xt_nat ip6table_raw 
nf_conntrack_ipv6
   xt_CT xt_mac xt_comment xt_physdev br_netfilter iptable_raw veth xt_CHECKSUM 
iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_nat_ipv4 
nf_nat nf_conntrac
  k_ipv4 nf_defrag_ipv4 xt_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp 
ebtable_filter ebtables ip6table_filter ip6_tables iptable_filter ip_tables 
x_tables vport_gre ip_gre 
  ip_tunnel gre nbd kvm_hv kvm ib_iser rdma_cm iw_cm ib_cm ib_sa ib_mad ib_core 
ib_addr iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi openvswitch 
nf_defrag_ipv6 nf_conn
  track dm_crypt bridge stp llc dm_multipath uio_pdrv_genirq ipmi_powernv 
ipmi_msghandler uio ibmpowernv powernv_rng vmx_crypto leds_powernv ses 
enclosure bnx2x vxlan ip6_udp_
  tunnel udp_tunnel mdio libcrc32c ipr
  Aug 23 11:38:25 rcsnode03 kernel: [ 3270.246500] CPU: 96 PID: 52779 Comm: 
qemu-system-ppc Not tainted 4.4.0-92-generic #115~14.04.1-Ubuntu
  Aug 23 11:38:25 rcsnode03 kernel: [ 3270.246506] task: c01e228dcf60 ti: 
c01e229f4000 task.ti: c01e229f4000
  Aug 23 11:38:25 rcsnode03 kernel: [ 3270.246511] NIP: d000189f85a0 LR: 
d000188a2584 CTR: d000189f84f0
  Aug 23 11:38:25 rcsnode03 kernel: [ 3270.246516] REGS: c01e229f7840 TRAP: 
0f60   Not tainted  (4.4.0-92-generic)
  Aug 23 11:38:25 rcsnode03 kernel: [ 3270.246519] MSR: 90009033 
  CR: 28022448  XER: 
  Aug 23 11:38:25 rcsnode03 kernel: [ 3270.246534] CFAR: d000189f8534 
SOFTE: 1 
  Aug 23 11:38:25 rcsnode03 kernel: [ 3270.246534] GPR00: d000188a2584 
c01e229f7ac0 d00018a0c7f8 c01c4c68 
  Aug 23 11:38:25 rcsnode03 kernel: [ 3270.246534] GPR04: c01c5308 
c01e229f7bc0  0004 
  Aug 23 11:38:25 rcsnode03 kernel: [ 3270.246534] GPR08: 0001 
c01e228dcf60  d000188a7518 
  Aug 23 11:38:25 rcsnode03 kernel: [ 3270.246534] GPR12: d000189f84f0 
cfb79000 3fff7d74ed40 3fff7d74f3d0 
  Aug 23 11:38:25 rcsnode03 kernel: [ 3270.246534] GPR16: 3fff7cf5 
 0003 3fff7d750010 
  Aug 23 11:38:25 rcsnode03 kernel: [ 3270.246534] GPR20: 100c0570 
01000f6ebba0 0080 3fff85644330 
  Aug 23 11:38:25 rcsnode03 kernel: [ 3270.246534] GPR24:  
3fff7cf30028 d4f6d401 0010 
  Aug 23 11:38:25 rcsnode03 kernel: [ 3270.246534] GPR28:  
c01c4c68 c01c4c68 c01c5308 
  Aug 23 11:38:25 rcsnode03 kernel: [ 3270.246594] NIP [d000189f85a0] 
kvmppc_vcpu_run_hv+0xb0/0x610 [kvm_hv]
  Aug 23 11:38:25 rcsnode03 kernel: [ 3270.246606] LR [d000188a2584] 
kvmppc_vcpu_run+0x44/0x60 [kvm]
  Aug 23 11:38:25 rcsnode03 kernel: [ 3270.246610] Call Trace:
  Aug 23 11:38:25 rcsnode03 kernel: [ 3270.246617] [c01e229f7ac0] 
[c00ca294] recalc_sigpending+0x24/0x90 (unreliable)
  Aug 23 11:38:25 rcsnode03 kernel: [ 3270.246630] [c01e229f7b70] 
[d000188a2584] kvmppc_vcpu_run+0x44/0x60 [kvm]
  Aug 23 11:38:25 rcsnode03 kernel: [ 3270.246642] [c01e229f7ba0] 
[d0001889f274] kvm_arch_vcpu_ioctl_run+0x64/0x1

[Kernel-packages] [Bug 1712803] Re: spapr_hcall from ubuntu_kvm_unit_test failed on ppc64el with Z-hwe kernel

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

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

** Tags added: kernel-da-key

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

Title:
  spapr_hcall from ubuntu_kvm_unit_test failed on ppc64el with Z-hwe
  kernel

Status in linux package in Ubuntu:
  Triaged

Bug description:
  kernel: 4.10.0-33.37~16.04.1

  I think this issue was introduced by the old qemu version (similar
  issue was spotted on Xenial before), will need to investigate this
  further.

  
  qemu-system-ppc64 -machine pseries,accel=kvm -bios powerpc/boot_rom.bin 
-display none -serial stdio -kernel powerpc/spapr_hcall.elf -smp 1
  FAIL: hypercall: h_set_sprg0: sprg0 = 0xcafebabedeadbeef
  FAIL: hypercall: h_set_sprg0: sprg0 = 0x
  FAIL: hypercall: h_set_sprg0: sprg0 = 0x41a588
  FAIL: hypercall: h_page_init: h_zero_page
  FAIL: hypercall: h_page_init: h_copy_page
  FAIL: hypercall: h_page_init: h_copy_page+h_zero_page
  FAIL: hypercall: h_page_init: h_zero_page unaligned dst
  FAIL: hypercall: h_page_init: h_copy_page unaligned src
  XFAIL: hypercall: h_random: h-call available

  SUMMARY: 9 tests, 8 unexpected failures, 1 expected failures

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

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

[Kernel-packages] [Bug 1712688] Re: The computer don't recognize my cellphone device.

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

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

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

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

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


Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.13-rc6

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

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

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

Title:
  The computer don't recognize my cellphone device.

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  When I connect my cellphone to the USB port, my cellphone recognize it
  and show me options of connection, but the computer don't show me
  anything.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-121-generic 3.13.0-121.170
  ProcVersionSignature: Ubuntu 3.13.0-121.170-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-121-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.24
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  vinicius   2282 F pulseaudio
  CurrentDesktop: Unity
  Date: Wed Aug 23 18:01:35 2017
  GvfsMonitorLog: Monitoring events. Press Ctrl+C to quit.
  HibernationDevice: RESUME=UUID=d02a4916-1c22-45b2-bfb1-c8761de14e8e
  HotplugNewDevices:
   
  HotplugNewMounts:
   
  InstallationDate: Installed on 2014-02-20 (1280 days ago)
  InstallationMedia: Ubuntu 12.04.4 LTS "Precise Pangolin" - Release amd64 
(20140204)
  MachineType: Dell Inc. Inspiron N4050
  ProcEnviron:
   LANGUAGE=pt_BR:pt:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pt_BR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-121-generic 
root=UUID=252638a5-b37d-45ae-8a1f-02a56ee91c75 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-121-generic N/A
   linux-backports-modules-3.13.0-121-generic  N/A
   linux-firmware  1.127.23
  SourcePackage: linux
  Symptom: storage
  UdisksMonitorLog:
   Monitoring the udisks daemon. Press Ctrl+C to exit.
   18:02:09.163: The udisks-daemon is running (name-owner :1.80).
  UpgradeStatus: Upgraded to trusty on 2015-03-18 (889 days ago)
  dmi.bios.date: 11/14/2011
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A06
  dmi.board.name: 0X0DC1
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A06
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvrA06:bd11/14/2011:svnDellInc.:pnInspironN4050:pvrNotSpecified:rvnDellInc.:rn0X0DC1:rvrA06:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.name: Inspiron N4050
  dmi.product.version: Not Specified
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1697892] Re: linux >= 4.2: bonding 802.3ad does not work with 5G, 25G and 50G link speeds

2017-08-25 Thread Julien Floret

Hello @kleber-souza,

Nicolas is currently out of office. The fix is ok for us.

Thanks!

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

Title:
  linux >= 4.2: bonding 802.3ad does not work with 5G, 25G and 50G link
  speeds

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Fix Committed
Status in linux source package in Yakkety:
  Won't Fix
Status in linux source package in Zesty:
  Fix Committed
Status in linux source package in Artful:
  Fix Released

Bug description:
  These upstream patches are needed to correctly handle 5G, 25G and 50G
  speeds in 802.3ad:

  19ddde1eeca1 bonding: add 802.3ad support for 25G speeds
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=19ddde1eeca1e

  c7c550670afd bonding: fix 802.3ad support for 5G and 50G speeds
  
https://git.kernel.org/pub/scm/linux/kernel/git/davem/net.git/commit/?id=c7c550670af

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

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

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

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

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

** Tags removed: block-proposed-artful

** Tags removed: block-proposed

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

Title:
  linux: 4.12.0-12.13 -proposed tracker

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

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

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

  -- swm properties --
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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

[Kernel-packages] [Bug 1712031] Re: [Feature] PXE boot with Intel Omni-Path

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

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

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

Title:
  [Feature] PXE boot with Intel Omni-Path

Status in intel:
  New
Status in linux package in Ubuntu:
  New
Status in linux-firmware package in Ubuntu:
  New

Bug description:
  Description:

  This is about ability to PXE boot over Intel Fabric.
  Netboot initrd is missing infiniband kernel stack along with hfi1.ko (for 1st 
generation of Intel Omni-Path cards). In addition some firmware files required 
to load modules are also missing in initrd. This firmware came from existing 
linux-firmware package, but is not included in netboot initrd image.

  Add Intel Omni-Path Architecture (OPA) Firmware to initrd.gz

  The initrd.gz supplied on Ubuntu 17.04 is missing
  the following firmware listed below in the /lib/firmware directory.
  As a result, PXE boot over fabric fails.

  hfi1_dc8051.fw
  hfi1_fabric.fw
  hfi1_pcie.fw
  hfi1_sbus.fw

  Target Release: 18.04

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

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

[Kernel-packages] [Bug 1711251] Re: vhost guest network randomly drops under stress (kvm)

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

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

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

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

Title:
  vhost guest network randomly drops under stress (kvm)

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

Bug description:
  == SRU Justification ==

  A vhost performance patch was introduced in the 4.10 kernel upstream,
  and is currently included in the Zesty 4.10 kernel:

  commit 809ecb9bca6a9424ccd392d67e368160f8b76c92
  Author: Jason Wang 
  Date:   Mon Dec 12 14:46:49 2016 +0800

  vhost: cache used event for better performance

  --

  However I recently hit a functional issue linked to this patch which
  would cause random guests to lose their network connection under
  stress.  This is not architecture specific and more likely to be hit
  with high network stress (i.e. lots of uperf instances).

  The patch author has now reverted this patch upstream:
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/vhost?id=8d65843c44269c21e95c98090d9bb4848d473853

  which reads:
  "
  Revert "vhost: cache used event for better performance"
  This reverts commit 809ecb9bca6a9424ccd392d67e368160f8b76c92. Since it
  was reported to break vhost_net. We want to cache used event and use
  it to check for notification. The assumption was that guest won't move
  the event idx back, but this could happen in fact when 16 bit index
  wraps around after 64K entries.

  Signed-off-by: Jason Wang 
  Acked-by: Michael S. Tsirkin 
  Signed-off-by: David S. Miller 
  "

  I am requesting this patch to revert the problematic one be pulled
  into Ubuntu Zesty (anything 4.10+).

  ---uname output---
  Linux p82qvirt 4.10.0-32-generic #36~16.04.1-Ubuntu SMP Wed Aug 9 09:19:19 
UTC 2017 ppc64le ppc64le ppc64le GNU/Linux

  Machine Type = 8247-22L

  ---Steps to Reproduce---
   I can recreate the scenario with the following setup:
   - on a 20core host, start 20 1core VMs
   - I have a single linux bridge assigned to all guests using virtio
   - start a uperf benchmark between each guest pair (10 total) using a high 
number of uperf nprocs (32)

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

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

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

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

apport-collect 1712031

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-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/1712031

Title:
  [Feature] PXE boot with Intel Omni-Path

Status in intel:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in linux-firmware package in Ubuntu:
  New

Bug description:
  Description:

  This is about ability to PXE boot over Intel Fabric.
  Netboot initrd is missing infiniband kernel stack along with hfi1.ko (for 1st 
generation of Intel Omni-Path cards). In addition some firmware files required 
to load modules are also missing in initrd. This firmware came from existing 
linux-firmware package, but is not included in netboot initrd image.

  Add Intel Omni-Path Architecture (OPA) Firmware to initrd.gz

  The initrd.gz supplied on Ubuntu 17.04 is missing
  the following firmware listed below in the /lib/firmware directory.
  As a result, PXE boot over fabric fails.

  hfi1_dc8051.fw
  hfi1_fabric.fw
  hfi1_pcie.fw
  hfi1_sbus.fw

  Target Release: 18.04

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

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

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

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

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

** Tags removed: block-proposed-precise

** Tags removed: block-proposed

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

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

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Invalid
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  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:
  New
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux-lts-trusty package in Ubuntu:
  Invalid
Status in linux-lts-trusty source package in Precise:
  Confirmed

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

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

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

[Kernel-packages] [Bug 1709292] Re: linux: 3.13.0-129.178 -proposed tracker

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

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

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

** Tags removed: block-proposed-trusty

** Tags removed: block-proposed

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

Title:
  linux: 3.13.0-129.178 -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 Trusty:
  Confirmed

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

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

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

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

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

[Kernel-packages] [Bug 1711251] Re: vhost guest network randomly drops under stress (kvm)

** Description changed:

- ---Problem Description---
- A vhost performance patch was introduced in the 4.10 kernel upstream, and is 
currently included in the Zesty 4.10 kernel:
+ == SRU Justification ==
+ 
+ A vhost performance patch was introduced in the 4.10 kernel upstream,
+ and is currently included in the Zesty 4.10 kernel:
  
  commit 809ecb9bca6a9424ccd392d67e368160f8b76c92
  Author: Jason Wang 
  Date:   Mon Dec 12 14:46:49 2016 +0800
  
- vhost: cache used event for better performance
+ vhost: cache used event for better performance
  
  --
  
  However I recently hit a functional issue linked to this patch which
  would cause random guests to lose their network connection under stress.
  This is not architecture specific and more likely to be hit with high
  network stress (i.e. lots of uperf instances).
  
  The patch author has now reverted this patch upstream:
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/vhost?id=8d65843c44269c21e95c98090d9bb4848d473853
  
  which reads:
- " 
+ "
  Revert "vhost: cache used event for better performance"
  This reverts commit 809ecb9bca6a9424ccd392d67e368160f8b76c92. Since it
  was reported to break vhost_net. We want to cache used event and use
  it to check for notification. The assumption was that guest won't move
  the event idx back, but this could happen in fact when 16 bit index
  wraps around after 64K entries.
  
  Signed-off-by: Jason Wang 
  Acked-by: Michael S. Tsirkin 
  Signed-off-by: David S. Miller 
  "
  
- I am requesting this patch to revert the problematic one be pulled into 
Ubuntu Zesty (anything 4.10+).
-  
+ I am requesting this patch to revert the problematic one be pulled into
+ Ubuntu Zesty (anything 4.10+).
+ 
  ---uname output---
  Linux p82qvirt 4.10.0-32-generic #36~16.04.1-Ubuntu SMP Wed Aug 9 09:19:19 
UTC 2017 ppc64le ppc64le ppc64le GNU/Linux
-  
- Machine Type = 8247-22L 
-  
+ 
+ Machine Type = 8247-22L
+ 
  ---Steps to Reproduce---
-  I can recreate the scenario with the following setup:
-  - on a 20core host, start 20 1core VMs
-  - I have a single linux bridge assigned to all guests using virtio
-  - start a uperf benchmark between each guest pair (10 total) using a high 
number of uperf nprocs (32)
+  I can recreate the scenario with the following setup:
+  - on a 20core host, start 20 1core VMs
+  - I have a single linux bridge assigned to all guests using virtio
+  - start a uperf benchmark between each guest pair (10 total) using a high 
number of uperf nprocs (32)

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

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

Title:
  vhost guest network randomly drops under stress (kvm)

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

Bug description:
  == SRU Justification ==

  A vhost performance patch was introduced in the 4.10 kernel upstream,
  and is currently included in the Zesty 4.10 kernel:

  commit 809ecb9bca6a9424ccd392d67e368160f8b76c92
  Author: Jason Wang 
  Date:   Mon Dec 12 14:46:49 2016 +0800

  vhost: cache used event for better performance

  --

  However I recently hit a functional issue linked to this patch which
  would cause random guests to lose their network connection under
  stress.  This is not architecture specific and more likely to be hit
  with high network stress (i.e. lots of uperf instances).

  The patch author has now reverted this patch upstream:
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/vhost?id=8d65843c44269c21e95c98090d9bb4848d473853

  which reads:
  "
  Revert "vhost: cache used event for better performance"
  This reverts commit 809ecb9bca6a9424ccd392d67e368160f8b76c92. Since it
  was reported to break vhost_net. We want to cache used event and use
  it to check for notification. The assumption was that guest won't move
  the event idx back, but this could happen in fact when 16 bit index
  wraps around after 64K entries.

  Signed-off-by: Jason Wang 
  Acked-by: Michael S. Tsirkin 
  Signed-off-by: David S. Miller 
  "

  I am requesting this patch to revert the problematic one be pulled
  into Ubuntu Zesty (anything 4.10+).

  ---uname output---
  Linux p82qvirt 4.10.0-32-generic #36~16.04.1-Ubuntu SMP Wed Aug 9 09:19:19 
UTC 2017 ppc64le ppc64le ppc64le GNU/Linux

  Machine Type = 8247-22L

  ---Steps to Reproduce---
   I can recreate the scenario with the following setup:
   - on a 20core host, start 20 1core VMs
   - I have a single linux bridge assigned to all guests using virtio
   - start a uperf benchmark between each guest pair (10 total) using a high 
number of uperf nprocs (32)

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

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

** Description changed:

+ == SRU Justification ==
+ Ubuntu 16.04.03: perf tool does not count pm_run_inst_cmpl with rcode on 
POWER9 DD2.0.
+ 
+ This is a regression introduced by mainline commit 8d911904f3ce.  This 
regression
+ is resolved by commit 8c218578fcbbbdb10416c8614658bf32e3bf1655.
+ 
+ Commit 8c218578fc is available in mailine as of 4.12-rc5.
+ 
+ 
+ 
  ---Problem Description---
  Unable to count pm_run_inst_cmpl using perf tool on boston dd2.0
  
  root@isvbos3:~# perf stat -e r500fa,r600f4 -a  sleep 1
  
-  Performance counter stats for 'system wide':
+  Performance counter stats for 'system wide':
  
-  r500fa   
-  8,162,912  r600f4
  
+      r500fa
+  8,162,912  r600f4
  
-1.001562716 seconds time elapsed
-  
+    1.001562716 seconds time elapsed
+ 
  ---uname output---
  Linux isvbos3 4.10.0-29-generic #33~16.04.1-Ubuntu SMP Tue Jul 25 18:17:06 
UTC 2017 ppc64le ppc64le ppc64le GNU/Linux
-  
- Machine Type = p9 dd2.0 
-   
+ 
+ Machine Type = p9 dd2.0
+ 
  ---Steps to Reproduce---
-  root@isvbos3:~# perf stat -e r500fa,r600f4 -a  sleep 1
+  root@isvbos3:~# perf stat -e r500fa,r600f4 -a  sleep 1
  
-  Performance counter stats for 'system wide':
+  Performance counter stats for 'system wide':
  
-  r500fa   
-  8,162,912  r600f4
  
+      r500fa
+  8,162,912  r600f4
  
-1.001562716 seconds time elapsed
+    1.001562716 seconds time elapsed
  
-  
  > Also we need this upstream fix 8c218578fcbbbdb10416c8614658bf32e3bf1655 in
  > the distro.
  
  $ git log 8c218578fcbbbdb10416c8614658 -1
  commit 8c218578fcbbbdb10416c8614658bf32e3bf1655
  Author: Madhavan Srinivasan 
  Date:   Fri May 26 13:38:27 2017 +0530
  
- powerpc/perf: Fix Power9 test_adder fields
- 
- Commit 8d911904f3ce4 ('powerpc/perf: Add restrictions to PMC5 in power9 
DD1')
- was added to restrict the use of PMC5 in Power9 DD1. Intention was to 
disable
- the use of PMC5 using raw event code. But instead of updating the
- power9_isa207_pmu structure (used on DD1), the commit incorrectly updated 
the
- power9_pmu structure. Fix it.
- 
- Fixes: 8d911904f3ce ("powerpc/perf: Add restrictions to PMC5 in power9 
DD1")
- Reported-by: Shriya 
- Signed-off-by: Madhavan Srinivasan 
- Tested-by: Shriya 
- Signed-off-by: Michael Ellerman 
+ powerpc/perf: Fix Power9 test_adder fields
+ 
+ Commit 8d911904f3ce4 ('powerpc/perf: Add restrictions to PMC5 in power9 
DD1')
+ was added to restrict the use of PMC5 in Power9 DD1. Intention was to 
disable
+ the use of PMC5 using raw event code. But instead of updating the
+ power9_isa207_pmu structure (used on DD1), the commit incorrectly updated 
the
+ power9_pmu structure. Fix it.
+ 
+ Fixes: 8d911904f3ce ("powerpc/perf: Add restrictions to PMC5 in power9 
DD1")
+ Reported-by: Shriya 
+ Signed-off-by: Madhavan Srinivasan 
+ Tested-by: Shriya 
+ Signed-off-by: Michael Ellerman 
  
  $ git describe --contains 8c218578fcbbbdb
  v4.12-rc7~9^2~13
- $ 
+ $
  
  Commit 8c218578fc is available with kernel 4.12-rc7 afterwards.
  
  I don't see this fix in the Ubuntu 16.04.3 Zesty tree (the P9 hwe
  kernel, 4.10 based).
  
  Need to mirror to Canonical to request they pull in:
  8c218578fcbbbdb10416c8614658bf32e3bf1655

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

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

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

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

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

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



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

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

   Performance counter stats for 'system wide':

       r500fa
   8,162,912  r600f4

     1.001562716 seconds time elapsed

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

  Machine Type = p9 dd2.0

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

   Performance counter stats for 'system wide':

       r500fa
   8,162,912  r600f4

     1.001562716 seconds time elapsed

  > Also we need this

[Kernel-packages] [Bug 1713051] Re: package linux-image-4.4.0-92-generic 4.4.0-92.115 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

2017-08-25 Thread Ubuntu Foundations Team Bug Bot

Thank you for taking the time to report this bug and helping to make
Ubuntu better.  Reviewing your dmesg attachment in this bug report it
seems that there is a problem with your hardware.  I recommend
performing a back up and then investigating the situation.  Measures you
might take include checking cable connections and using software tools
to investigate the health of your hardware.  In the event that is is not
in fact an error with your hardware please set the bug's status back to
New.  Thanks and good luck!

[This is an automated message.  I apologize if it reached you
inappropriately; please just reply to this message indicating so.]

** Tags added: hardware-error

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

Title:
  package linux-image-4.4.0-92-generic 4.4.0-92.115 failed to
  install/upgrade: subprocess installed post-installation script
  returned error exit status 1

Status in linux package in Ubuntu:
  Invalid

Bug description:
  oracle java

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-92-generic 4.4.0-92.115
  ProcVersionSignature: Ubuntu 4.4.0-62.83-generic 4.4.40
  Uname: Linux 4.4.0-62-generic i686
  ApportVersion: 2.14.1-0ubuntu3.25
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  kvg1933 F pulseaudio
  Date: Fri Aug 25 16:36:37 2017
  DuplicateSignature: 
package:linux-image-4.4.0-92-generic:4.4.0-92.115:subprocess installed 
post-installation script returned error exit status 1
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2016-02-13 (559 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta i386 (20150805)
  MachineType: Acer Aspire 4738Z
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-62-generic 
root=UUID=f110cdde-d212-475b-b683-1e305b54 ro quiet splash
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   dpkg 1.17.5ubuntu5.7
   apt  1.0.1ubuntu2.17
  SourcePackage: linux
  Title: package linux-image-4.4.0-92-generic 4.4.0-92.115 failed to 
install/upgrade: subprocess installed post-installation script returned error 
exit status 1
  UpgradeStatus: Upgraded to xenial on 2017-08-25 (0 days ago)
  dmi.bios.date: 09/10/2010
  dmi.bios.vendor: INSYDE
  dmi.bios.version: V1.06
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: JE41_CP
  dmi.board.vendor: Acer
  dmi.board.version: Base Board Version
  dmi.chassis.type: 10
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnINSYDE:bvrV1.06:bd09/10/2010:svnAcer:pnAspire4738Z:pvrV1.06:rvnAcer:rnJE41_CP:rvrBaseBoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion:
  dmi.product.name: Aspire 4738Z
  dmi.product.version: V1.06
  dmi.sys.vendor: Acer

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

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

[Kernel-packages] [Bug 1692538] Re: Ubuntu 16.04.02: ibmveth: Support to enable LSO/CSO for Trunk VEA

** Description changed:

+ 
+ == SRU Justification ==
+ Commit 66aa0678ef is request to fix four issues with the ibmveth driver.
+ The issues are as follows:
+ - Issue 1: ibmveth doesn't support largesend and checksum offload features 
when configured as "Trunk".
+ - Issue 2: SYN packet drops seen at destination VM. When the packet
+ originates, it has CHECKSUM_PARTIAL flag set and as it gets delivered to IO
+ server's inbound Trunk ibmveth, on validating "checksum good" bits in ibmveth
+ receive routine, SKB's ip_summed field is set with CHECKSUM_UNNECESSARY flag.
+ - Issue 3: First packet of a TCP connection will be dropped, if there is
+ no OVS flow cached in datapath.
+ - Issue 4: ibmveth driver doesn't have support for SKB's with frag_list.
+ 
+ The details for the fixes to these issues are described in the commits
+ git log.
+ 
+ 
+ 
  == Comment: #0 - BRYANT G. LY  - 2017-05-22 08:40:16 ==
  ---Problem Description---
  
-  - Issue 1: ibmveth doesn't support largesend and checksum offload features
-when configured as "Trunk". Driver has explicit checks to prevent
-enabling these offloads.
+  - Issue 1: ibmveth doesn't support largesend and checksum offload features
+    when configured as "Trunk". Driver has explicit checks to prevent
+    enabling these offloads.
  
-  - Issue 2: SYN packet drops seen at destination VM. When the packet
-originates, it has CHECKSUM_PARTIAL flag set and as it gets delivered to
-IO server's inbound Trunk ibmveth, on validating "checksum good" bits
-in ibmveth receive routine, SKB's ip_summed field is set with
-CHECKSUM_UNNECESSARY flag. This packet is then bridged by OVS (or Linux
-Bridge) and delivered to outbound Trunk ibmveth. At this point the
-outbound ibmveth transmit routine will not set "no checksum" and
-"checksum good" bits in transmit buffer descriptor, as it does so only
-when the ip_summed field is CHECKSUM_PARTIAL. When this packet gets
-delivered to destination VM, TCP layer receives the packet with checksum
-value of 0 and with no checksum related flags in ip_summed field. This
-leads to packet drops. So, TCP connections never goes through fine.
+  - Issue 2: SYN packet drops seen at destination VM. When the packet
+    originates, it has CHECKSUM_PARTIAL flag set and as it gets delivered to
+    IO server's inbound Trunk ibmveth, on validating "checksum good" bits
+    in ibmveth receive routine, SKB's ip_summed field is set with
+    CHECKSUM_UNNECESSARY flag. This packet is then bridged by OVS (or Linux
+    Bridge) and delivered to outbound Trunk ibmveth. At this point the
+    outbound ibmveth transmit routine will not set "no checksum" and
+    "checksum good" bits in transmit buffer descriptor, as it does so only
+    when the ip_summed field is CHECKSUM_PARTIAL. When this packet gets
+    delivered to destination VM, TCP layer receives the packet with checksum
+    value of 0 and with no checksum related flags in ip_summed field. This
+    leads to packet drops. So, TCP connections never goes through fine.
  
-  - Issue 3: First packet of a TCP connection will be dropped, if there is
-no OVS flow cached in datapath. OVS while trying to identify the flow,
-computes the checksum. The computed checksum will be invalid at the
-receiving end, as ibmveth transmit routine zeroes out the pseudo
-checksum value in the packet. This leads to packet drop.
+  - Issue 3: First packet of a TCP connection will be dropped, if there is
+    no OVS flow cached in datapath. OVS while trying to identify the flow,
+    computes the checksum. The computed checksum will be invalid at the
+    receiving end, as ibmveth transmit routine zeroes out the pseudo
+    checksum value in the packet. This leads to packet drop.
  
-  - Issue 4: ibmveth driver doesn't have support for SKB's with frag_list.
-When Physical NIC has GRO enabled and when OVS bridges these packets,
-OVS vport send code will end up calling dev_queue_xmit, which in turn
-calls validate_xmit_skb.
-In validate_xmit_skb routine, the larger packets will get segmented into
-MSS sized segments, if SKB has a frag_list and if the driver to which
-they are delivered to doesn't support NETIF_F_FRAGLIST feature.
-  
- Contact Information = Bryant G. Ly/b...@us.ibm.com 
-  
+  - Issue 4: ibmveth driver doesn't have support for SKB's with frag_list.
+    When Physical NIC has GRO enabled and when OVS bridges these packets,
+    OVS vport send code will end up calling dev_queue_xmit, which in turn
+    calls validate_xmit_skb.
+    In validate_xmit_skb routine, the larger packets will get segmented into
+    MSS sized segments, if SKB has a frag_list and if the driver to which
+    they are delivered to doesn't support NETIF_F_FRAGLIST feature.
+ 
+ Contact Information = Bryant G. Ly/b...@us.ibm.com
+ 
  ---uname output---
  4.8.0-51.54
-  
- Machine Type = p8 
-  
+ 
+ Machine Type = p8
+ 
  ---Debugger---
  A debugger is not c

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

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

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

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

Thanks in advance

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

Title:
  [Hyper-V] LIS daemons fail to start after disable/re-enable VM
  integration services

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

Bug description:
  Issue description: Hyper-V daemons fail to start after disable/re-
  enable VM integration services.

  Platform: host independent
  Affected daemons - KVP, FCOPY and VSS.

  Distribution name and release: Ubuntu 16.04, Ubuntu 17.04
  Kernel version: 4.11.0-rc7-next-20170421 (for Ubuntu 16.04), 
4.10.0-19-generic (for Ubuntu 17.04)

  Repro rate: 100%

  Steps to reproduce:
  1.Start VM with Guest Services enabled (FCopy daemon starts automatically)
  2.Go to File > Settings > Integration Services, uncheck Guest Services 
and apply (FCopy daemon will stop at this point)
  3.Re-enable Guest Services from VM Settings (Fcopy daemon is not running).
  This is the issue. systemd monitors for the service and if we have the hook 
for the Guest Service, it tries to start the daemon again.
  systemd attempt to start any of the LIS daemons will fail, but manually 
executing the daemon binary, it will start the daemon.

  Additional Info:
  - the steps above can be repro'd with KVP / Data Exchange integration service 
as well.
  - Manually starting hv_fcopy_daemon works fine.
  - other distros (RHEL) does not have this behavior, the LIS daemons are 
started automatically by systemd once we re-enable the integration service.

  On the upstream kernel and the upstream hv daemons, these messages are 
recorded in syslog, once we re-enable the Guest service:
  HV_FCOPY: pread failed: Bad file descriptor
  systemd[1]: hv-fcopy-daemon.service: Main process exited, code=exited, 
status=1/FAILURE
  systemd[1]: hv-fcopy-daemon.service: Unit entered failed state.
  systemd[1]: hv-fcopy-daemon.service: Failed with result 'exit-code'.

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

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

[Kernel-packages] [Bug 1713106] [NEW] Artful update to v4.12.9 stable release

2017-08-25 Thread Andy Whitcroft

Public bug reported:

Artful update to v4.12.8 stable release

** Affects: linux (Ubuntu)
 Importance: High
 Assignee: Andy Whitcroft (apw)
 Status: Triaged

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

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

Title:
  Artful update to v4.12.9 stable release

Status in linux package in Ubuntu:
  Triaged

Bug description:
  Artful update to v4.12.8 stable release

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

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

[Kernel-packages] [Bug 1709179] Re: Drop GPL from of_node_to_nid() export to match other arches

I built a Zesty test kernel with a pick of commit be9ba9ff93cc.  The
test kernel can be downloaded from:

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

Can you test this kernel and see if it resolves this bug?

Thanks in advance!

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

Title:
  Drop GPL from of_node_to_nid() export to match other arches

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

Bug description:
  == Comment: #0 - Reza A. Arbab  - 2017-08-07 15:34:04 ==
  We need to backport mainline commit be9ba9ff93cc ("Drop GPL from 
of_node_to_nid() export to match other arches") to the Ubuntu 4.10 kernel.

  This exposes functionality needed by the Nvidia device driver on
  POWER9.

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

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

[Kernel-packages] [Bug 1708399] Re: kernel panic -not syncing: Fatal exception: panic_on_oops

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

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

** No longer affects: ubuntu-power-systems

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

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

Title:
  kernel panic -not syncing: Fatal exception: panic_on_oops

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

Bug description:
  == Comment: #0 - QI YE  - 2017-08-02 04:11:25 ==
  ---Problem Description---
  Ubuntu got kernel panic

  ---uname output---
  #110-Ubuntu SMP Tue Jul 18 12:56:43 UTC 2017 s390x s390x s390x GNU/Linux
   
  ---Debugger Data---
  PID: 10991  TASK: 19872a0e8 CPU: 2   COMMAND: "hyperkube"
   LOWCORE INFO:
-psw  : 0x0004c0018000 0x00115fa6
-function : pcpu_delegate at 115fa6
-prefix   : 0x7fe42000
-cpu timer: 0x7ffab2827828aa50
-clock cmp: 0xd2eb8b31445e4200
-general registers:
   0x0004e001 0x001283b6
   0xc001 0x8380fcb8
   0x00115f9e 0x0056f6e2
   0x0004 0x00cf9070
   0x0001f3bfc000 0x00112fd8
   0x0001c72bb400 0x0002
   0x7fffc000 0x007c9ef0
   0x00115f9e 0x8380fc18
-access registers:
   0x03ff 0x7910 00 00
   00 00 00 00
   00 00 00 00
   00 00 00 00
-control registers:
   0x14066a12 0x7e6d81c7
   0x00011140 00
   0x2aef 0x0400
   0x5000 0x7e6d81c7
   00 00
   00 00
   00 0x00cfc007
   0xdb00 0x00011280
-floating point registers:
   0x409c7e258000 0x401de4e0
   00 0x3fd24407ab0e073a
   0x3ff0 0x3fee
   0x3fef218f8a7a41a0 0x3fee
   0x0080 00
   0x03ff7f80 0x02aa4940e9e0
   0xd401 0x03ffe81fe110
   00 0x03fff2cfe638

   #0 [8380fc78] smp_find_processor_id at 1160f8
   #1 [8380fc90] machine_kexec at 1135d4
   #2 [8380fcb8] crash_kexec at 1fbb8a
   #3 [8380fd88] panic at 27d0e0
   #4 [8380fe28] die at 1142cc
   #5 [8380fe90] do_low_address at 12215e
   #6 [8380fea8] pgm_check_handler at 7c2ab4
   PSW:  070520018000 02aa267e0e42 (user space)
   GPRS:   02aa2c4fd690 0001
 02aa2c4fd690 03ff7fffee38  0002
 00029c0f 00c42001ea00 0001 0001
 00c42001c5c8 00c42082c1a0 02aa2666325e 03ff7fffed90 
   
  Contact Information = Chee Ye / y...@cn.ibm.com 
   
  Stack trace output:
   no
   
  Oops output:
   [43200.761465] docker0: port 10(vethb9132e9) entered forwarding state
  [50008.560926] hrtimer: interrupt took 1698076 ns
  [123483.768984] systemd[1]: apt-daily.timer: Adding 7h 34min 22.582204s 
random time.
  [123483.930058] systemd[1]: apt-daily.timer: Adding 2h 18min 14.857162s 
random time.
  [123484.064879] systemd[1]: apt-daily.timer: Adding 10h 46min 2.301756s 
random time.
  [123484.824760] systemd[1]: apt-daily.timer: Adding 6h 16min 22.178655s 
random time.
  [153113.703126] conntrack: generic helper won't handle protocol 47. Please 
consider loading the specific helper module.
  [477085.704538] Low-address protection: 0004 ilc:2 [#1] SMP
  [477085.704551] Modules linked in: xt_physdev veth xt_recent xt_comment 
xt_mark xt_nat ipt_MASQUERADE nf_nat_masquerade_ipv4 xfrm_user xfrm_algo 
iptable_nat nf_nat_ipv4 xt_addrtype nf_nat br_netfilter bridge stp llc aufs 
ipt_REJECT nf_reject_ipv4 xt_tcpudp nf_conntrack_ipv4 nf_defrag_ipv4 
xt_conntrack nf_conntrack iptable_filter ip_tables x_tables ghash_s390 prng 
aes_s390 des_s390 des_generic sha512_s390 qeth_l2 sha256_s390 qeth sha1_s390 
qdio sha_common ccwgroup vmur dasd_eckd_mod dasd_mod
  [477085.705522] CPU: 2 PID: 10991 Comm: hyperkube Not tainted 
4.4.0-87-generic #110-Ubuntu
  [477085.705525] task: 00019872a0e8 ti: 8380c000 task.ti: 
8380c000
  [477085.705529] User PSW : 070520018000 02aa267e0e42
  [477085.705532]R:0 T:1 IO:1 EX:1 Key:0 M:1 W:0 P:1 AS:0 CC:2 PM:0 
EA:3
  User GPRS:   02aa2c4fd690 
0001
  [477085.705539]02aa2c4fd690 03ff7fffee38  
0002
  [477085.705553]

[Kernel-packages] [Bug 1713103] [NEW] snapd 2.27.3+17.10 ADT test failure with linux 4.13.0-6.7

You have been subscribed to a public bug:

Testing failed on:
amd64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-artful-canonical-kernel-team-unstable/artful/amd64/s/snapd/20170825_154928_33cfc@/log.gz
i386: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-artful-canonical-kernel-team-unstable/artful/i386/s/snapd/20170825_150258_33cfc@/log.gz
ppc64el: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-artful-canonical-kernel-team-unstable/artful/ppc64el/s/snapd/20170825_141201_33cfc@/log.gz

** Affects: linux (Ubuntu)
 Importance: High
 Assignee: John Johansen (jjohansen)
 Status: Triaged


** Tags: kernel-adt-failure
-- 
snapd 2.27.3+17.10 ADT test failure with linux 4.13.0-6.7
https://bugs.launchpad.net/bugs/1713103
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to linux in Ubuntu.

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

[Kernel-packages] [Bug 1713103] Re: snapd 2.27.3+17.10 ADT test failure with linux 4.13.0-6.7

The apparmorfs kernel query interface file has more restrictive file
permissions in the upstream kernel versus what we've had in the Ubuntu
sauce patches.

In Artful (Ubuntu 4.11.0-13.19-generic 4.11.12):
$ ls -al /sys/kernel/security/apparmor/.access 
-rw-rw-rw- 1 root root 0 Aug 15 17:38 /sys/kernel/security/apparmor/.access

In linux-next (4.13.0-rc6-next-20170824):
$ ls -al /sys/kernel/security/apparmor/.access
-rw-r- 1 root root 0 Aug 24 21:26 /sys/kernel/security/apparmor/.access

This means that the D-Bus session bus cannot perform AppArmor policy
queries because it can't open the .access file.

** Package changed: snapd (Ubuntu) => linux (Ubuntu)

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

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

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => John Johansen (jjohansen)

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

Title:
  snapd 2.27.3+17.10 ADT test failure with linux 4.13.0-6.7

Status in linux package in Ubuntu:
  Triaged

Bug description:
  Testing failed on:
  amd64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-artful-canonical-kernel-team-unstable/artful/amd64/s/snapd/20170825_154928_33cfc@/log.gz
  i386: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-artful-canonical-kernel-team-unstable/artful/i386/s/snapd/20170825_150258_33cfc@/log.gz
  ppc64el: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-artful-canonical-kernel-team-unstable/artful/ppc64el/s/snapd/20170825_141201_33cfc@/log.gz

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

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

[Kernel-packages] [Bug 1712232] Re: [Feature] KNM: KNM NIs Enabling

It appears the kernel commit listed here has already landed in upstream
4.10 and thus also available in the Artful kernel.  Marking the linux
task Fix Released.  I have added a task for qemu to confirm those
commits are integrated already as well.

commit 4504b5c9414c55da37f26b1faf49c09a2acbf255
Author: Luwei Kang 
Date:   Mon Nov 7 14:03:20 2016 +0800

kvm: x86: Add AVX512_4VNNIW and AVX512_4FMAPS support

** Information type changed from Proprietary to Public

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

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

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

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

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

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

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

** Changed in: qemu (Ubuntu Artful)
 Assignee: (unassigned) => ChristianEhrhardt (paelzer)

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

Title:
  [Feature] KNM: KNM NIs Enabling

Status in intel:
  New
Status in linux package in Ubuntu:
  Fix Released
Status in qemu package in Ubuntu:
  Triaged
Status in linux source package in Artful:
  Fix Released
Status in qemu source package in Artful:
  Triaged

Bug description:
  KNM NIs Enabling, including avx512 4vnniw, 4fmaps, vpopcntdq

  
  AVX512_4VNNIW and AVX512_4FMAPS

  Linux kernel commit id: 4504b5c9414c55da37f26b1faf49c09a2acbf255

  QEMU commit id: 95ea69fb46266aaa46d0c8b7f0ba8c4903dbe4e3

  AVX512_VPOPCNTDQ
  QEMU commit id: f77543772dcd38fa438470d9b80bafbd3a3ebbd7

  This feature should have been merged to 17.10 beta1.  Create it for
  track.

  Target Release: 17.10

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

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

[Kernel-packages] [Bug 1713106] Re: Artful update to v4.12.9 stable release

2017-08-25 Thread Andy Whitcroft

audit: Fix use after free in audit_remove_watch_rule()
parisc: pci memory bar assignment fails with 64bit kernels on dino/cujo
crypto: ixp4xx - Fix error handling path in 'aead_perform()'
crypto: x86/sha1 - Fix reads beyond the number of blocks passed
drm/i915: Perform an invalidate prior to executing golden renderstate
drm/amdgpu: save list length when fence is signaled
Input: elan_i2c - add ELAN0608 to the ACPI table
Input: elan_i2c - Add antoher Lenovo ACPI ID for upcoming Lenovo NB
md: fix test in md_write_start()
md: always clear ->safemode when md_check_recovery gets the mddev lock.
MD: not clear ->safemode for external metadata array
ALSA: seq: 2nd attempt at fixing race creating a queue
ALSA: usb-audio: Apply sample rate quirk to Sennheiser headset
ALSA: usb-audio: Add mute TLV for playback volumes on C-Media devices
ALSA: usb-audio: add DSD support for new Amanero PID
mm: discard memblock data later
slub: fix per memcg cache leak on css offline
mm: fix double mmap_sem unlock on MMF_UNSTABLE enforced SIGBUS
mm/cma_debug.c: fix stack corruption due to sprintf usage
mm/mempolicy: fix use after free when calling get_mempolicy
mm/vmalloc.c: don't unconditonally use __GFP_HIGHMEM
mm: revert x86_64 and arm64 ELF_ET_DYN_BASE base changes
xen: fix bio vec merging
ARM: dts: imx6qdl-nitrogen6_som2: fix PCIe reset
blk-mq-pci: add a fallback when pci_irq_get_affinity returns NULL
powerpc: Fix VSX enabling/flushing to also test MSR_FP and MSR_VEC
xen-blkfront: use a right index when checking requests
perf/x86: Fix RDPMC vs. mm_struct tracking
x86/asm/64: Clear AC on NMI entries
x86: Fix norandmaps/ADDR_NO_RANDOMIZE
x86/elf: Remove the unnecessary ADDR_NO_RANDOMIZE checks
irqchip/atmel-aic: Fix unbalanced of_node_put() in aic_common_irq_fixup()
irqchip/atmel-aic: Fix unbalanced refcount in aic_common_rtc_irq_fixup()
genirq: Restore trigger settings in irq_modify_status()
genirq/ipi: Fixup checks against nr_cpu_ids
kernel/watchdog: Prevent false positives with turbo modes
Sanitize 'move_pages()' permission checks
pids: make task_tgid_nr_ns() safe
debug: Fix WARN_ON_ONCE() for modules
usb: optimize acpi companion search for usb port devices
usb: qmi_wwan: add D-Link DWM-222 device ID
Linux 4.12.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/1713106

Title:
  Artful update to v4.12.9 stable release

Status in linux package in Ubuntu:
  Triaged

Bug description:
  Artful update to v4.12.8 stable release

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

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

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

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

apport-collect 1712249

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

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

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

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

** Tags added: artful

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

Title:
  [Bug] Crystal Ridge: Fix device-dax sysfs duplicate name warning /
  failure

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

Bug description:
  Fix warnings of the form...
  WARNING: CPU: 10 PID: 4983 at fs/sysfs/dir.c:31 sysfs_warn_dup+0x62/0x80
  sysfs: cannot create duplicate filename '/class/dax/dax12.0'
  Call Trace:
  dump_stack+0x63/0x86
  __warn+0xcb/0xf0
  warn_slowpath_fmt+0x5a/0x80
  ? kernfs_path_from_node+0x4f/0x60
  sysfs_warn_dup+0x62/0x80
  sysfs_do_create_link_sd.isra.2+0x97/0xb0
  sysfs_create_link+0x25/0x40
  device_add+0x266/0x630
  devm_create_dax_dev+0x2cf/0x340 [dax]
  dax_pmem_probe+0x1f5/0x26e [dax_pmem]
  nvdimm_bus_probe+0x71/0x120
  ...by reusing the namespace id for the device-dax instance name.
  Now that we have decided that there will never by more than one
  device-dax instance per libnvdimm-namespace parent device [1], we can
  directly reuse the namepace ids. There are some possible follow-on
  cleanups, but those are saved for a later patch to simplify the -stable
  backport.
  [1]: https://lists.01.org/pipermail/linux-nvdimm/2016-December/008266.html
  Fixes: 98a29c39dc68 ("libnvdimm, namespace: allow creation of multiple 
pmem...")
  Cc: Jeff Moyer 
  Cc: 
  Reported-by: Dariusz Dokupil 
  Signed-off-by: Dan Williams 

  
  Target Release: 17.10
  Target Kernel: 4.13

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

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

[Kernel-packages] [Bug 1712249] Re: [Bug] Crystal Ridge: Fix device-dax sysfs duplicate name warning / failure

** Information type changed from Proprietary to Public

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

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

Title:
  [Bug] Crystal Ridge: Fix device-dax sysfs duplicate name warning /
  failure

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

Bug description:
  Fix warnings of the form...
  WARNING: CPU: 10 PID: 4983 at fs/sysfs/dir.c:31 sysfs_warn_dup+0x62/0x80
  sysfs: cannot create duplicate filename '/class/dax/dax12.0'
  Call Trace:
  dump_stack+0x63/0x86
  __warn+0xcb/0xf0
  warn_slowpath_fmt+0x5a/0x80
  ? kernfs_path_from_node+0x4f/0x60
  sysfs_warn_dup+0x62/0x80
  sysfs_do_create_link_sd.isra.2+0x97/0xb0
  sysfs_create_link+0x25/0x40
  device_add+0x266/0x630
  devm_create_dax_dev+0x2cf/0x340 [dax]
  dax_pmem_probe+0x1f5/0x26e [dax_pmem]
  nvdimm_bus_probe+0x71/0x120
  ...by reusing the namespace id for the device-dax instance name.
  Now that we have decided that there will never by more than one
  device-dax instance per libnvdimm-namespace parent device [1], we can
  directly reuse the namepace ids. There are some possible follow-on
  cleanups, but those are saved for a later patch to simplify the -stable
  backport.
  [1]: https://lists.01.org/pipermail/linux-nvdimm/2016-December/008266.html
  Fixes: 98a29c39dc68 ("libnvdimm, namespace: allow creation of multiple 
pmem...")
  Cc: Jeff Moyer 
  Cc: 
  Reported-by: Dariusz Dokupil 
  Signed-off-by: Dan Williams 

  
  Target Release: 17.10
  Target Kernel: 4.13

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

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

[Kernel-packages] [Bug 1469829] Re: ppc64el should use 'deadline' as default io scheduler

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

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

Title:
  ppc64el should use 'deadline' as default io scheduler

Status in The Ubuntu-power-systems project:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Trusty:
  Fix Released
Status in linux-lts-utopic source package in Trusty:
  Fix Released
Status in linux source package in Utopic:
  Won't Fix
Status in linux source package in Vivid:
  Fix Released

Bug description:
  [Impact]
  Using cfq instead of deadline as the default io scheduler starves certain 
workloads and causes performance issues. In addition every other arch we build 
uses deadline as the default scheduler.

  [Fix]
  Change the configuration to the following for ppc64el:
  CONFIG_DEFAULT_DEADLINE=y
  CONFIG_DEFAULT_IOSCHED="deadline"

  [Test Case]
  Boot and cat /sys/block/*/queue/scheduler to see if deadline is being used.

  --

  -- Problem Description --

  Firestone system given to DASD group failed HTX overnight test with 
miscompare error.
  HTX mdt.hdbuster was running on secondary drive and failed about 12 hours 
into test

  HTX miscompare analysis:
  -==

  Device under test: /dev/sdb
  Stanza running: rule_3
  miscompare offset: 0x40
  Transfer size: Random Size
  LBA number: 0x70fc
  miscompare length: all the blocks in the transfer size

  *- STANZA 3: Creates number of threads twice the queue depth. Each thread  -*
  *- doing 2 num_oper with RC operation with xfer size between 1 block   -*
  *- to 256K.-*

  This miscompare shows read operation is unable to get the expected
  data from the disk. The re-read buffer also shows the same data as the
  first read operation. Since the first read and next re-read shows same
  data, there could be a write operation (of previous rule stanza to
  initialize disk with pattern 007 ) failure on the disk. The same
  miscompare behavior shows for all the blocks in the transfer size.

  /dev/sdb  Jun  2 02:29:43 2015 err=03b6 sev=2 hxestorage  
<<===  device name (/dev/sdb)
  rule_3_13  numopers= 2  loop=   767  blk=0x70fc len=89088
   min_blkno=0 max_blkno=0x74706daf, RANDOM access
  Seed Values= 37303, 290, 23235
  Data Pattern Seed Values = 37303, 291, 23235
  BWRC LBA fencepost Detail:
  th_nummin_lba  max_lba  status
   0 01c9be3ffR
   1  1d1c1b6c3a3836d7F
   2  3a3836d857545243F
   3  5754524474706dafF
  Miscompare at buffer offset 64 (0x40) <<===   
miscompare offset (0x40)
  (Flags: badsig=0; cksum=0x6)  Maximum LBA = 0x74706daf
  wbuf (baseaddr 0x3ffe1c0e6600) b0ff
  rbuf (baseaddr 0x3ffe1c0fc400) 850100fc700200fd700300fe700400ff7005
  Write buffer saved in /tmp/htxsdb.wbuf1
  Read buffer saved in /tmp/htxsdb.rbuf1
  Re-read fails compare at offset64; buffer saved in /tmp/htxsdb.rerd1
  errno: 950(Unknown error 950)

  Asghar reproduced that HTX hang he is seeing. Looking in the kernel
  logs I see some messages from the kernel that there are user threads
  blocked on getting reads serviced. So likely HTX is seeing the same
  thing. I've asked Asghar to try using the deadline I/O scheduler
  rather than CFQ to see if that makes any difference. If that does not
  make any difference, the next thing to try is reducing the queue depth
  of the device. Right now its 31, which I think is pretty high.

  Step 1:

  echo deadline > /sys/block/sda/queue/scheduler
  echo deadline > /sys/block/sdb/queue/scheduler

  If that reproduces the issue, go to step 2:

  echo cfq > /sys/block/sda/queue/scheduler
  echo cfq > /sys/block/sdb/queue/scheduler
  echo 8 > /sys/block/sda/device/queue_depth
  echo 8 > /sys/block/sdb/device/queue_depth

  Breno - it looks like the default I/O scheduler + default queue depth
  for the SATA disks in Firestone is not optimal, in that when running a
  heavy I/O workload, we see read starvation occurring, which is making
  the system nearly unusable.

  Once we changed the I/O scheduler from cfq to deadline, all the issues
  went away and the system is able to run the same workload yet still be
  responsive. Suggest we either encourage Canonical to change the
  default I/O scheduler to deadline or at the very least provide
  documentation to encourage our customers to make this change
  themselves.

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

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

[Kernel-packages] [Bug 1713103] Re: snapd 2.27.3+17.10 ADT test failure with linux 4.13.0-6.7

@jjohansen are the more restrictive file permissions intentional? I see
quite a few apparmorfs permissions changes between xenial and upstream:

-static struct aa_fs_entry aa_fs_entry_apparmor[] = {
-   AA_FS_FILE_FOPS(".access", 0666, &aa_fs_access),
-   AA_FS_FILE_FOPS(".stacked", 0666, &aa_fs_stacked),
-   AA_FS_FILE_FOPS(".ns_stacked", 0666, &aa_fs_ns_stacked),
-   AA_FS_FILE_FOPS(".ns_level", 0666, &aa_fs_ns_level),
-   AA_FS_FILE_FOPS(".ns_name", 0666, &aa_fs_ns_name),
-   AA_FS_FILE_FOPS("profiles", 0444, &aa_fs_profiles_fops),
-   AA_FS_DIR("features", aa_fs_entry_features),
+static struct aa_sfs_entry aa_sfs_entry_apparmor[] = {
+   AA_SFS_FILE_FOPS(".access", 0640, &aa_sfs_access),
+   AA_SFS_FILE_FOPS(".stacked", 0444, &seq_ns_stacked_fops),
+   AA_SFS_FILE_FOPS(".ns_stacked", 0444, &seq_ns_nsstacked_fops),
+   AA_SFS_FILE_FOPS(".ns_level", 0666, &seq_ns_level_fops),
+   AA_SFS_FILE_FOPS(".ns_name", 0640, &seq_ns_name_fops),
+   AA_SFS_FILE_FOPS("profiles", 0440, &aa_sfs_profiles_fops),
+   AA_SFS_DIR("features", aa_sfs_entry_features),
{ }
 };

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

Title:
  snapd 2.27.3+17.10 ADT test failure with linux 4.13.0-6.7

Status in linux package in Ubuntu:
  Triaged

Bug description:
  Testing failed on:
  amd64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-artful-canonical-kernel-team-unstable/artful/amd64/s/snapd/20170825_154928_33cfc@/log.gz
  i386: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-artful-canonical-kernel-team-unstable/artful/i386/s/snapd/20170825_150258_33cfc@/log.gz
  ppc64el: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-artful-canonical-kernel-team-unstable/artful/ppc64el/s/snapd/20170825_141201_33cfc@/log.gz

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

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

[Kernel-packages] [Bug 1712709] Re: [Feature] KBL:Enable Suspend to Idle on Dell 9360 and Dell 9365.

Marking this In Progress as we move to a 4.13 based kernel for Artful.

0ce3fcaff92908c370334ce3b9111aeea71159d6 PCI / PM: Restore PME Enable after 
config space restoration
v4.13-rc1~17^2~2^2~1
33e4f80ee69b5168badf37edbfed796eb48434b9 ACPI / PM: Ignore spurious SCI wakeups 
from suspend-to-idle
v4.13-rc1~17^2~2^2~11
76380636280b46541a9d2fe5aac497475bfbcde8 ACPI / EC: Add parameter to force 
disable the GPE on suspend
v4.13-rc3~19^2~2^2
8110dd281e155e5010ffd657bba4742ebef7a93f ACPI / sleep: EC-based wakeup from 
suspend-to-idle on recent systems
v4.13-rc1~17^2~2^2~7
880a66275ef4d1e08e5d4dcf4cec768de18c68ef ACPI / PM / EC: Flush all EC work in 
acpi_freeze_sync()
v4.13-rc3~19^2~1
c7b5a4e6e8fbef8fdf2c529f953000d24c561339 PCI / PM: Fix native PME handling 
during system suspend/resume
v4.13-rc1~17^2~2^2
eed4d47efe9508b855b09754cf6de4325d8a2f0d ACPI / sleep: Ignore spurious SCI 
wakeups from suspend-to-idle
v4.12-rc3~29^2^2~3
f3b7eaae1b35eb8077610eb7c7db042c9b0645e1 Revert "ACPI / sleep: Ignore spurious 
SCI wakeups from suspend-to-idle"
v4.12-rc5~29^2^3


** Information type changed from Proprietary to Public

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

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

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

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

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

Title:
  [Feature] KBL:Enable Suspend to Idle on Dell 9360 and Dell 9365.

Status in intel:
  New
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Artful:
  In Progress

Bug description:
  This jira is to track the commits for making suspend to idle function
  on Dell 9360 and Dell 9365.

  0ce3fcaff92908c370334ce3b9111aeea71159d6
  33e4f80ee69b5168badf37edbfed796eb48434b9
  76380636280b46541a9d2fe5aac497475bfbcde8
  8110dd281e155e5010ffd657bba4742ebef7a93f
  880a66275ef4d1e08e5d4dcf4cec768de18c68ef
  c7b5a4e6e8fbef8fdf2c529f953000d24c561339
  eed4d47efe9508b855b09754cf6de4325d8a2f0d
  f3b7eaae1b35eb8077610eb7c7db042c9b0645e1

  Target Kernel: 4.13

  Target Release: 17.10

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

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

[Kernel-packages] [Bug 1712031] Re: [Feature] PXE boot with Intel Omni-Path

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

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

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

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

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

Title:
  [Feature] PXE boot with Intel Omni-Path

Status in intel:
  New
Status in linux package in Ubuntu:
  Triaged
Status in linux-firmware package in Ubuntu:
  Triaged

Bug description:
  Description:

  This is about ability to PXE boot over Intel Fabric.
  Netboot initrd is missing infiniband kernel stack along with hfi1.ko (for 1st 
generation of Intel Omni-Path cards). In addition some firmware files required 
to load modules are also missing in initrd. This firmware came from existing 
linux-firmware package, but is not included in netboot initrd image.

  Add Intel Omni-Path Architecture (OPA) Firmware to initrd.gz

  The initrd.gz supplied on Ubuntu 17.04 is missing
  the following firmware listed below in the /lib/firmware directory.
  As a result, PXE boot over fabric fails.

  hfi1_dc8051.fw
  hfi1_fabric.fw
  hfi1_pcie.fw
  hfi1_sbus.fw

  Target Release: 18.04

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

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

[Kernel-packages] [Bug 1709257] Re: [Bug] Harrisonville: pnd2_edac always fail to load on B1 stepping Harrisonville SDP

bc8f10babcc2 "EDAC, pnd2: Properly toggle hidden state for P2SB PCI
device" doesn't apply cleanly without 3e5d2bd19138 "EDAC, pnd2: Build in
a minimal sideband driver for Apollo Lake". The backport is not
straightforward, and I'm not sure how to validate if I did attempt a
backport. Can you please advise if we should also take that commit, or
else provide us with a tested backport of bc8f10babcc2 to 4.13? Thanks!

For future reference, this appears to be the extra patch which was
requested - https://patchwork.ozlabs.org/patch/801447/.

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

** Information type changed from Private to Public

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

Title:
  [Bug] Harrisonville: pnd2_edac always fail to load on B1 stepping
  Harrisonville SDP

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

Bug description:
  Description:
  During our EDAC validation on Wind River Linux 9, we found pnd2_edac manually 
load always fails on B1 stepping Harrisonville SDP.
  Error info as below:
  root@intel-x86-64:~# uname -r
  4.8.20-WR9.0.0.5_standard
  root@intel-x86-64:~# dmesg |grep -i edac
  [   11.949838] EDAC MC: Ver: 3.0.0
  [   11.954312] EDAC DEBUG: edac_mc_sysfs_init: device mc created
  [   12.060157] EDAC DEBUG: pnd2_init:
  [   12.060160] EDAC DEBUG: pnd2_probe:
  [   12.060167] EDAC DEBUG: dnv_rd_reg: Read b_cr_tolud_pci=_8000
  [   12.060169] EDAC DEBUG: dnv_rd_reg: Read 
b_cr_touud_lo_pci=_8000
  [   12.060172] EDAC DEBUG: dnv_rd_reg: Read 
b_cr_touud_hi_pci=_0004
  [   12.060228] EDAC DEBUG: dnv_rd_reg: Read 
b_cr_asym_mem_region0_mchbar=_
  [   12.060239] EDAC DEBUG: dnv_rd_reg: Read 
b_cr_asym_mem_region1_mchbar=_
  [   12.060247] EDAC DEBUG: dnv_rd_reg: Read 
b_cr_mot_out_base_mchbar=_
  [   12.060255] EDAC DEBUG: dnv_rd_reg: Read 
b_cr_mot_out_mask_mchbar=_
  [   12.078301] Modules linked in: pnd2_edac(+) edac_core x86_pkg_temp_thermal 
i2c_i801 intel_powerclamp matroxfb_base matroxfb_g450 matroxfb_accel 
matroxfb_DAC1064 g450_pll matroxfb_misc i2c_ismt i2c_smbus coretemp 
crct10dif_pclmul crct10dif_common aesni_intel aes_x86_64 glue_helper lrw 
gf128mul ablk_helper cryptd efi_pstore efivars acpi_cpufreq tpm_tis 
tpm_tis_core softdog efivarfs
  [   12.143390]  [] ? dnv_rd_reg+0x128/0x220 [pnd2_edac]
  [   12.148890]  [] dnv_rd_reg+0x128/0x220 [pnd2_edac]
  [   12.148896]  [] pnd2_init+0x22b/0x809 [pnd2_edac]
  [   12.148961] EDAC pnd2: Failed to register device with error -19.
  [   12.180813] EDAC DEBUG: pnd2_init:
  [   12.180814] EDAC DEBUG: pnd2_probe:
  [   12.180841] EDAC DEBUG: dnv_rd_reg: Read b_cr_tolud_pci=_8000
  [   12.180937] EDAC DEBUG: dnv_rd_reg: Read 
b_cr_touud_lo_pci=_8000
  [   12.180969] EDAC DEBUG: dnv_rd_reg: Read 
b_cr_touud_hi_pci=_0004
  [   12.181129] EDAC DEBUG: dnv_rd_reg: Read 
b_cr_asym_mem_region0_mchbar=_
  [   12.181299] EDAC DEBUG: dnv_rd_reg: Read 
b_cr_asym_mem_region1_mchbar=_
  [   12.181425] EDAC DEBUG: dnv_rd_reg: Read 
b_cr_mot_out_base_mchbar=_
  [   12.181671] EDAC DEBUG: dnv_rd_reg: Read 
b_cr_mot_out_mask_mchbar=_
  [   12.181810] EDAC pnd2: Failed to register device with error -19.
  root@intel-x86-64:~# dmesg -c > dmesg.clear_14.D91.log
  root@intel-x86-64:~# modprobe edac_core
  root@intel-x86-64:~# modprobe pnd2_edac
  modprobe: ERROR: could not insert 'pnd2_edac': No such device
  root@intel-x86-64:~# dmesg
  [  194.524122] EDAC DEBUG: pnd2_init:
  [  194.524126] EDAC DEBUG: pnd2_probe:
  [  194.524135] EDAC DEBUG: dnv_rd_reg: Read b_cr_tolud_pci=_8000
  [  194.524139] EDAC DEBUG: dnv_rd_reg: Read 
b_cr_touud_lo_pci=_8000
  [  194.524143] EDAC DEBUG: dnv_rd_reg: Read 
b_cr_touud_hi_pci=_0004
  [  194.524211] EDAC DEBUG: dnv_rd_reg: Read 
b_cr_asym_mem_region0_mchbar=_
  [  194.524226] EDAC DEBUG: dnv_rd_reg: Read 
b_cr_asym_mem_region1_mchbar=_
  [  194.524239] EDAC DEBUG: dnv_rd_reg: Read 
b_cr_mot_out_base_mchbar=_
  [  194.524252] EDAC DEBUG: dnv_rd_reg: Read 
b_cr_mot_out_mask_mchbar=_
  [  194.524264] EDAC pnd2: Failed to register device with error -19.
  root@intel-x86-64:~# dmidecode -t bios | grep Version
  Version: HAVLCRB1.X64.0014.D91.1704200405

  Target Kernel: 4.14
  Target Release: 18.04
  if 17.10, it will need back porting

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

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

[Kernel-packages] [Bug 1712249] Re: [Bug] Crystal Ridge: Fix device-dax sysfs duplicate name warning / failure

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

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

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

Title:
  [Bug] Crystal Ridge: Fix device-dax sysfs duplicate name warning /
  failure

Status in intel:
  New
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Artful:
  In Progress

Bug description:
  Fix warnings of the form...
  WARNING: CPU: 10 PID: 4983 at fs/sysfs/dir.c:31 sysfs_warn_dup+0x62/0x80
  sysfs: cannot create duplicate filename '/class/dax/dax12.0'
  Call Trace:
  dump_stack+0x63/0x86
  __warn+0xcb/0xf0
  warn_slowpath_fmt+0x5a/0x80
  ? kernfs_path_from_node+0x4f/0x60
  sysfs_warn_dup+0x62/0x80
  sysfs_do_create_link_sd.isra.2+0x97/0xb0
  sysfs_create_link+0x25/0x40
  device_add+0x266/0x630
  devm_create_dax_dev+0x2cf/0x340 [dax]
  dax_pmem_probe+0x1f5/0x26e [dax_pmem]
  nvdimm_bus_probe+0x71/0x120
  ...by reusing the namespace id for the device-dax instance name.
  Now that we have decided that there will never by more than one
  device-dax instance per libnvdimm-namespace parent device [1], we can
  directly reuse the namepace ids. There are some possible follow-on
  cleanups, but those are saved for a later patch to simplify the -stable
  backport.
  [1]: https://lists.01.org/pipermail/linux-nvdimm/2016-December/008266.html
  Fixes: 98a29c39dc68 ("libnvdimm, namespace: allow creation of multiple 
pmem...")
  Cc: Jeff Moyer 
  Cc: 
  Reported-by: Dariusz Dokupil 
  Signed-off-by: Dan Williams 

  
  Target Release: 17.10
  Target Kernel: 4.13

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

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

[Kernel-packages] [Bug 1700834] Re: Intel i40e PF reset under load

2017-08-25 Thread Björn Zettergren

I'm running Xenial with kernel 4.4.0-92.115 on a Dell R330 with intel X710 NIC.
Under load it fails with message: "TX driver issue detected, PF reset issued" 
as original report says.

To me it looks like this issue isn't completely solved since I'm running
a more recent kernel than the "fix" was commited to.

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

Title:
  Intel i40e PF reset under load

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

Bug description:
  SRU Justification:

  Impact:

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

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

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

In this case, these errors arise from a bug in the i40e device
  driver introduced by commit:

  commit 584a837e26408c66e87df87a022faa6a54c2b020
  Author: Alexander Duyck 
  Date:   Wed Feb 17 11:02:50 2016 -0800

  i40e/i40evf: Rewrite logic for 8 descriptor per packet check

This patch was added to the Xenial kernel beginning with version
  4.4.0-8.23.  This bug does not manifest on any other Ubuntu kernel series.

  
  Fix:

  This error is resolved upstream by:

  commit 3f3f7cb875c0f621485644d4fd7453b0d37f00e4
  Author: Alexander Duyck 
  Date:   Wed Mar 30 16:15:37 2016 -0700

  i40e/i40evf: Limit TSO to 7 descriptors for payload instead of 8 per 
packet
  
This fix was never backported into the Xenial 4.4 kernel series.
  

  Testcase:

In this case, the issue occurs at a customer site using i40e based
  Intel network cards with SR-IOV enabled.  Under heavy load, the card will
  reset itself as described.  The customer has tested the 3f3f7cb875c patch
  in their environment and confirmed that it resolves the issue.

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

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

[Kernel-packages] [Bug 1712626] Re: Cannot launch virtual instance on nova host after upgrading to kernel 4.4.0.92- works with 4.4.0.83

2017-08-25 Thread Blake Henderson

I will look into testing it on our nova host.
I tested it on a vm just to ensure it booted ok- no issues.  I will try it on 
the nova host as soon as i can and see if i am able to launch a virtual 
instance.

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

Title:
  Cannot launch virtual instance on nova host after upgrading to kernel
  4.4.0.92- works with 4.4.0.83

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

Bug description:
  Host -- IBM Power 8  822L
  OS- Ubuntu 14.04 ppc64el
  previous kernel 3.19.0.68
  Nova Compute host using kvm - Openstack Liberty

  HWE was out of date so needed to update

  Steps:

  sudo apt-get install linux-generic-lts-xenial linux-image-generic-lts-xenial
  sudo init 6
  sudo apt update
  sudo apt upgrade
  sudo init 6

  afterwards - system seemed ok - kernel 4.4.0.92 installed

  However, launching a Ubuntu VM failed

  Aug 23 11:38:25 rcsnode03 kernel: [ 3270.246360] Facility 'TM' unavailable, 
exception at 0xd000189f85a0, MSR=90009033
  Aug 23 11:38:25 rcsnode03 kernel: [ 3270.246374] Oops: Unexpected facility 
unavailable exception, sig: 6 [#1]
  Aug 23 11:38:25 rcsnode03 kernel: [ 3270.246379] SMP NR_CPUS=2048 NUMA PowerNV
  Aug 23 11:38:25 rcsnode03 kernel: [ 3270.246385] Modules linked in: vhost_net 
vhost macvtap macvlan xt_REDIRECT nf_nat_redirect xt_mark xt_nat ip6table_raw 
nf_conntrack_ipv6
   xt_CT xt_mac xt_comment xt_physdev br_netfilter iptable_raw veth xt_CHECKSUM 
iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_nat_ipv4 
nf_nat nf_conntrac
  k_ipv4 nf_defrag_ipv4 xt_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp 
ebtable_filter ebtables ip6table_filter ip6_tables iptable_filter ip_tables 
x_tables vport_gre ip_gre 
  ip_tunnel gre nbd kvm_hv kvm ib_iser rdma_cm iw_cm ib_cm ib_sa ib_mad ib_core 
ib_addr iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi openvswitch 
nf_defrag_ipv6 nf_conn
  track dm_crypt bridge stp llc dm_multipath uio_pdrv_genirq ipmi_powernv 
ipmi_msghandler uio ibmpowernv powernv_rng vmx_crypto leds_powernv ses 
enclosure bnx2x vxlan ip6_udp_
  tunnel udp_tunnel mdio libcrc32c ipr
  Aug 23 11:38:25 rcsnode03 kernel: [ 3270.246500] CPU: 96 PID: 52779 Comm: 
qemu-system-ppc Not tainted 4.4.0-92-generic #115~14.04.1-Ubuntu
  Aug 23 11:38:25 rcsnode03 kernel: [ 3270.246506] task: c01e228dcf60 ti: 
c01e229f4000 task.ti: c01e229f4000
  Aug 23 11:38:25 rcsnode03 kernel: [ 3270.246511] NIP: d000189f85a0 LR: 
d000188a2584 CTR: d000189f84f0
  Aug 23 11:38:25 rcsnode03 kernel: [ 3270.246516] REGS: c01e229f7840 TRAP: 
0f60   Not tainted  (4.4.0-92-generic)
  Aug 23 11:38:25 rcsnode03 kernel: [ 3270.246519] MSR: 90009033 
  CR: 28022448  XER: 
  Aug 23 11:38:25 rcsnode03 kernel: [ 3270.246534] CFAR: d000189f8534 
SOFTE: 1 
  Aug 23 11:38:25 rcsnode03 kernel: [ 3270.246534] GPR00: d000188a2584 
c01e229f7ac0 d00018a0c7f8 c01c4c68 
  Aug 23 11:38:25 rcsnode03 kernel: [ 3270.246534] GPR04: c01c5308 
c01e229f7bc0  0004 
  Aug 23 11:38:25 rcsnode03 kernel: [ 3270.246534] GPR08: 0001 
c01e228dcf60  d000188a7518 
  Aug 23 11:38:25 rcsnode03 kernel: [ 3270.246534] GPR12: d000189f84f0 
cfb79000 3fff7d74ed40 3fff7d74f3d0 
  Aug 23 11:38:25 rcsnode03 kernel: [ 3270.246534] GPR16: 3fff7cf5 
 0003 3fff7d750010 
  Aug 23 11:38:25 rcsnode03 kernel: [ 3270.246534] GPR20: 100c0570 
01000f6ebba0 0080 3fff85644330 
  Aug 23 11:38:25 rcsnode03 kernel: [ 3270.246534] GPR24:  
3fff7cf30028 d4f6d401 0010 
  Aug 23 11:38:25 rcsnode03 kernel: [ 3270.246534] GPR28:  
c01c4c68 c01c4c68 c01c5308 
  Aug 23 11:38:25 rcsnode03 kernel: [ 3270.246594] NIP [d000189f85a0] 
kvmppc_vcpu_run_hv+0xb0/0x610 [kvm_hv]
  Aug 23 11:38:25 rcsnode03 kernel: [ 3270.246606] LR [d000188a2584] 
kvmppc_vcpu_run+0x44/0x60 [kvm]
  Aug 23 11:38:25 rcsnode03 kernel: [ 3270.246610] Call Trace:
  Aug 23 11:38:25 rcsnode03 kernel: [ 3270.246617] [c01e229f7ac0] 
[c00ca294] recalc_sigpending+0x24/0x90 (unreliable)
  Aug 23 11:38:25 rcsnode03 kernel: [ 3270.246630] [c01e229f7b70] 
[d000188a2584] kvmppc_vcpu_run+0x44/0x60 [kvm]
  Aug 23 11:38:25 rcsnode03 kernel: [ 3270.246642] [c01e229f7ba0] 
[d0001889f274] kvm_arch_vcpu_ioctl_run+0x64/0x180 [kvm]
  Aug 23 11:38:25 rcsnode03 kernel: [ 3270.246653] [c01e229f7be0] 
[d00018893898] kvm_vcpu_ioctl+0x5e8/0x7c0 [kvm]
  Aug 23 11:38:25 rcsnode03 kernel: [ 3270.246661] [c01e229f7d40] 
[c02ef7d0] do_vfs_ioctl+0x4d0/0x7e0
  Aug 23 11:38:25 rcsnode03 kernel: [ 3270.246667] [c01e229f7de0] 
[c02efbb4]

[Kernel-packages] [Bug 1712626] Re: Cannot launch virtual instance on nova host after upgrading to kernel 4.4.0.92- works with 4.4.0.83

2017-08-25 Thread Blake Henderson

Added kernel 4.4.0-94-117 to the nova node
I am now able to create VMs on it. 

Fix is successful

ubuntu@rcsnode03:~$ uname -a
Linux rcsnode03 4.4.0-94-generic #117~lp1709784 SMP Wed Aug 23 20:28:29 UTC 
2017 ppc64le ppc64le ppc64le GNU/Linux

ubuntu@rcsnode03:~$ virsh list
 IdName   State

 2 instance-0269  running

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

Title:
  Cannot launch virtual instance on nova host after upgrading to kernel
  4.4.0.92- works with 4.4.0.83

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

Bug description:
  Host -- IBM Power 8  822L
  OS- Ubuntu 14.04 ppc64el
  previous kernel 3.19.0.68
  Nova Compute host using kvm - Openstack Liberty

  HWE was out of date so needed to update

  Steps:

  sudo apt-get install linux-generic-lts-xenial linux-image-generic-lts-xenial
  sudo init 6
  sudo apt update
  sudo apt upgrade
  sudo init 6

  afterwards - system seemed ok - kernel 4.4.0.92 installed

  However, launching a Ubuntu VM failed

  Aug 23 11:38:25 rcsnode03 kernel: [ 3270.246360] Facility 'TM' unavailable, 
exception at 0xd000189f85a0, MSR=90009033
  Aug 23 11:38:25 rcsnode03 kernel: [ 3270.246374] Oops: Unexpected facility 
unavailable exception, sig: 6 [#1]
  Aug 23 11:38:25 rcsnode03 kernel: [ 3270.246379] SMP NR_CPUS=2048 NUMA PowerNV
  Aug 23 11:38:25 rcsnode03 kernel: [ 3270.246385] Modules linked in: vhost_net 
vhost macvtap macvlan xt_REDIRECT nf_nat_redirect xt_mark xt_nat ip6table_raw 
nf_conntrack_ipv6
   xt_CT xt_mac xt_comment xt_physdev br_netfilter iptable_raw veth xt_CHECKSUM 
iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_nat_ipv4 
nf_nat nf_conntrac
  k_ipv4 nf_defrag_ipv4 xt_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp 
ebtable_filter ebtables ip6table_filter ip6_tables iptable_filter ip_tables 
x_tables vport_gre ip_gre 
  ip_tunnel gre nbd kvm_hv kvm ib_iser rdma_cm iw_cm ib_cm ib_sa ib_mad ib_core 
ib_addr iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi openvswitch 
nf_defrag_ipv6 nf_conn
  track dm_crypt bridge stp llc dm_multipath uio_pdrv_genirq ipmi_powernv 
ipmi_msghandler uio ibmpowernv powernv_rng vmx_crypto leds_powernv ses 
enclosure bnx2x vxlan ip6_udp_
  tunnel udp_tunnel mdio libcrc32c ipr
  Aug 23 11:38:25 rcsnode03 kernel: [ 3270.246500] CPU: 96 PID: 52779 Comm: 
qemu-system-ppc Not tainted 4.4.0-92-generic #115~14.04.1-Ubuntu
  Aug 23 11:38:25 rcsnode03 kernel: [ 3270.246506] task: c01e228dcf60 ti: 
c01e229f4000 task.ti: c01e229f4000
  Aug 23 11:38:25 rcsnode03 kernel: [ 3270.246511] NIP: d000189f85a0 LR: 
d000188a2584 CTR: d000189f84f0
  Aug 23 11:38:25 rcsnode03 kernel: [ 3270.246516] REGS: c01e229f7840 TRAP: 
0f60   Not tainted  (4.4.0-92-generic)
  Aug 23 11:38:25 rcsnode03 kernel: [ 3270.246519] MSR: 90009033 
  CR: 28022448  XER: 
  Aug 23 11:38:25 rcsnode03 kernel: [ 3270.246534] CFAR: d000189f8534 
SOFTE: 1 
  Aug 23 11:38:25 rcsnode03 kernel: [ 3270.246534] GPR00: d000188a2584 
c01e229f7ac0 d00018a0c7f8 c01c4c68 
  Aug 23 11:38:25 rcsnode03 kernel: [ 3270.246534] GPR04: c01c5308 
c01e229f7bc0  0004 
  Aug 23 11:38:25 rcsnode03 kernel: [ 3270.246534] GPR08: 0001 
c01e228dcf60  d000188a7518 
  Aug 23 11:38:25 rcsnode03 kernel: [ 3270.246534] GPR12: d000189f84f0 
cfb79000 3fff7d74ed40 3fff7d74f3d0 
  Aug 23 11:38:25 rcsnode03 kernel: [ 3270.246534] GPR16: 3fff7cf5 
 0003 3fff7d750010 
  Aug 23 11:38:25 rcsnode03 kernel: [ 3270.246534] GPR20: 100c0570 
01000f6ebba0 0080 3fff85644330 
  Aug 23 11:38:25 rcsnode03 kernel: [ 3270.246534] GPR24:  
3fff7cf30028 d4f6d401 0010 
  Aug 23 11:38:25 rcsnode03 kernel: [ 3270.246534] GPR28:  
c01c4c68 c01c4c68 c01c5308 
  Aug 23 11:38:25 rcsnode03 kernel: [ 3270.246594] NIP [d000189f85a0] 
kvmppc_vcpu_run_hv+0xb0/0x610 [kvm_hv]
  Aug 23 11:38:25 rcsnode03 kernel: [ 3270.246606] LR [d000188a2584] 
kvmppc_vcpu_run+0x44/0x60 [kvm]
  Aug 23 11:38:25 rcsnode03 kernel: [ 3270.246610] Call Trace:
  Aug 23 11:38:25 rcsnode03 kernel: [ 3270.246617] [c01e229f7ac0] 
[c00ca294] recalc_sigpending+0x24/0x90 (unreliable)
  Aug 23 11:38:25 rcsnode03 kernel: [ 3270.246630] [c01e229f7b70] 
[d000188a2584] kvmppc_vcpu_run+0x44/0x60 [kvm]
  Aug 23 11:38:25 rcsnode03 kernel: [ 3270.246642] [c01e229f7ba0] 
[d0001889f274] kvm_arch_vcpu_ioctl_run+0x64/0x180 [kvm]
  Aug 23 11:38:25 rcsnode03 kernel: [ 3270.246653] [c01e229f7be0] 
[d00018893898] kvm_vcpu_ioctl+0x5e8/0x7c0

[Kernel-packages] [Bug 1713134] [NEW] linux 4.13.0-6.7 ADT test failure with linux 4.13.0-6.7

Public bug reported:

Testing failed on:
amd64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-artful-canonical-kernel-team-unstable/artful/amd64/l/linux/20170825_162923_61ef2@/log.gz
i386: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-artful-canonical-kernel-team-unstable/artful/i386/l/linux/20170825_175003_61ef2@/log.gz
ppc64el: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-artful-canonical-kernel-team-unstable/artful/ppc64el/l/linux/20170825_155346_61ef2@/log.gz

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


** Tags: kernel-adt-failure

** Tags added: kernel-adt-failure

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

Title:
  linux 4.13.0-6.7 ADT test failure with linux 4.13.0-6.7

Status in linux package in Ubuntu:
  New

Bug description:
  Testing failed on:
  amd64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-artful-canonical-kernel-team-unstable/artful/amd64/l/linux/20170825_162923_61ef2@/log.gz
  i386: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-artful-canonical-kernel-team-unstable/artful/i386/l/linux/20170825_175003_61ef2@/log.gz
  ppc64el: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-artful-canonical-kernel-team-unstable/artful/ppc64el/l/linux/20170825_155346_61ef2@/log.gz

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

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

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

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

apport-collect 1713134

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

Title:
  linux 4.13.0-6.7 ADT test failure with linux 4.13.0-6.7

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Testing failed on:
  amd64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-artful-canonical-kernel-team-unstable/artful/amd64/l/linux/20170825_162923_61ef2@/log.gz
  i386: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-artful-canonical-kernel-team-unstable/artful/i386/l/linux/20170825_175003_61ef2@/log.gz
  ppc64el: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-artful-canonical-kernel-team-unstable/artful/ppc64el/l/linux/20170825_155346_61ef2@/log.gz

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

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

[Kernel-packages] [Bug 1713103] Re: snapd 2.27.3+17.10 ADT test failure with linux 4.13.0-6.7

2017-08-25 Thread John Johansen

sort of. The code was broken into patches and upstreamed piece meal, so
the tighter restrictions when a give patch went it made sense. They also
better reflect some of the internal permissions that were being
enforced, ie. while profiles was  you needed cap mac admin to actual
see it. It looks like opening some of those back up dropped of the todo
queue.

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

Title:
  snapd 2.27.3+17.10 ADT test failure with linux 4.13.0-6.7

Status in linux package in Ubuntu:
  Triaged

Bug description:
  Testing failed on:
  amd64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-artful-canonical-kernel-team-unstable/artful/amd64/s/snapd/20170825_154928_33cfc@/log.gz
  i386: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-artful-canonical-kernel-team-unstable/artful/i386/s/snapd/20170825_150258_33cfc@/log.gz
  ppc64el: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-artful-canonical-kernel-team-unstable/artful/ppc64el/s/snapd/20170825_141201_33cfc@/log.gz

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

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

[Kernel-packages] [Bug 1713134] Re: linux 4.13.0-6.7 ADT test failure with linux 4.13.0-6.7

All three arches have apparmor failures, jjohansen says these are
needing test updates which haven't yet been pushed out.

i386 additionally has a stress-ng clone test failure.

ppc64el has a kernel selftests build failure which is already tracked in
bug 1710904.

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

Title:
  linux 4.13.0-6.7 ADT test failure with linux 4.13.0-6.7

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Testing failed on:
  amd64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-artful-canonical-kernel-team-unstable/artful/amd64/l/linux/20170825_162923_61ef2@/log.gz
  i386: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-artful-canonical-kernel-team-unstable/artful/i386/l/linux/20170825_175003_61ef2@/log.gz
  ppc64el: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-artful-canonical-kernel-team-unstable/artful/ppc64el/l/linux/20170825_155346_61ef2@/log.gz

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

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

[Kernel-packages] [Bug 1709179] Re: Drop GPL from of_node_to_nid() export to match other arches

** Changed in: ubuntu-power-systems
   Status: New => In Progress

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

Title:
  Drop GPL from of_node_to_nid() export to match other arches

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

Bug description:
  == Comment: #0 - Reza A. Arbab  - 2017-08-07 15:34:04 ==
  We need to backport mainline commit be9ba9ff93cc ("Drop GPL from 
of_node_to_nid() export to match other arches") to the Ubuntu 4.10 kernel.

  This exposes functionality needed by the Nvidia device driver on
  POWER9.

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

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

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

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

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

Title:
  Disable CONFIG_MEMORY_HOTPLUG_DEFAULT_ONLINE

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

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

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

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

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

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

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

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

Title:
  Ubuntu17.10 - perf: Update Power9 PMU event JSON files

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

Bug description:
  == Comment: #0 - Sukadev Bhattiprolu  - 2017-08-03 20:36:26 
==
  +++ This bug was initially created as a clone of Bug #157304 +++

  ---Problem Description---
  BZ 150738 added  Power9 PMU event lists to the Linux kernel tree.
  We need to update the event lists to include several more events
  as well as clean up the event descriptions of some events.

  The patches for these updates were posted to LKML 
   https://lkml.org/lkml/2017/8/2/699
  with:
  Subject: Re: [GIT PULL] Please pull JSON files for Power9 PMU events

  and were merged into Arnaldo's "perf-core" tree as git commits:

  
https://git.kernel.org/pub/scm/linux/kernel/git/acme/linux.git/commit/?h=perf/core&id=864c572433dedfb5c36db79c4ceb6dfb80b3344b
  ("perf vendor events powerpc: remove suffix in mapfile")

  and

  
https://git.kernel.org/pub/scm/linux/kernel/git/acme/linux.git/commit/?h=perf/core&id=b547e94b919c84de22052935a77de9c8a97d3418
  ("perf vendor events powerpc: Update POWER9 events")

  We will need to include those updates into
   
  Contact Information = s...@us.ibm.com 
   
  ---uname output---
  na
   
  Machine Type = Powre9 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   'perf list pmu' , 'perf stat' and 'perf record' are unable to list/use some 
Power9 PMU events as they are missing from the kernel source tree.
   
  Stack trace output:
   no
   
  Oops output:
   no
   
  Userspace tool common name: perf 

  Userspace rpm: linux-tools 
   
  The userspace tool has the following bit modes: 64-bit 
   
  System Dump Info:
The system is not configured to capture a system dump.

  Userspace tool obtained from project website:  na 
   
  *Additional Instructions for s...@us.ibm.com: 
  -Attach sysctl -a output output to the bug.
  -Attach ltrace and strace of userspace application.

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

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

[Kernel-packages] [Bug 1710904] Re: linux 4.12.0-11.12 ADT test failure with linux 4.12.0-11.12

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

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

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

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

Title:
  linux 4.12.0-11.12 ADT test failure with linux 4.12.0-11.12

Status in linux package in Ubuntu:
  Fix Committed

Bug description:
  Testing failed on:
  ppc64el: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-artful/artful/ppc64el/l/linux/20170815_145827_31c05@/log.gz

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

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

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

** Tags added: kernel-key

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

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

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

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

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

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

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

[Kernel-packages] [Bug 1673564] Re: ThunderX: soft lockup on 4.8+ kernels when running qemu-efi with vhost=on

2017-08-25 Thread dann frazier

I've been able to backport the fixes back as far as 4.7. 4.7 was when
the new vgic reimplementation was merged, and the upstream patchset
would need significant surgery to apply. To fix Ubuntu 16.04's GA kernel
(4.4-based), we'd probably need to develop a new (hopefully simpler)
solution. In the meantime, I recommend anyone using ThunderX w/ 16.04
stick with the HWE (currently 4.10-based).

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

Title:
  ThunderX: soft lockup on 4.8+ kernels when running qemu-efi with
  vhost=on

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Confirmed
Status in linux source package in Yakkety:
  Won't Fix
Status in linux source package in Zesty:
  Fix Committed

Bug description:
  [Impact]
  VMs can cause interrupts to be disabled on the host CPU, resulting in hangs.

  [Test Case]
  Download the attached vm-start-stop.tar.gz and unpack it. Run the start.sh 
script within. This will start 30 parallel loops where a VM is defined, 
started, allowed 60s to run, then destroyed. If the bug exists, within 10 
minutes you'll see qemu processes start to hang, along with soft lockup 
messages on the console. Note that this script is compatible with xenial 
libvirt syntax - it likely needs tweaks to run in newer Ubuntu releases, just 
due to QEMU/libvirt changes.

  [Regression Risk]
  The code changes are restricted to ARM - but there are a lot of them. While 
we've attempted to stress test the proposed changes on both impacted and 
non-impacted (non-ThunderX) systems, it is possible that there are issues that 
our test isn't finding, which would likely surface as KVM guest crashes/hangs.

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

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

[Kernel-packages] [Bug 1611078] Re: Support snaps inside of lxd containers

2017-08-25 Thread Stéphane Graber

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

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

Title:
  Support snaps inside of lxd containers

Status in Snappy:
  Fix Released
Status in apparmor package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in lxd package in Ubuntu:
  Fix Released
Status in apparmor source package in Xenial:
  Fix Released
Status in linux source package in Xenial:
  Fix Released
Status in lxd source package in Xenial:
  Fix Released
Status in apparmor source package in Yakkety:
  Fix Released
Status in linux source package in Yakkety:
  Fix Released
Status in lxd source package in Yakkety:
  Fix Released

Bug description:
  I tried following the instructions on snapcraft.io and got a failure.
  See the output below.  I've also attached the relevant output from
  running "journalctl -xe".

  uname: Linux 3.19.0-65-generic x86_64
  release: Ubuntu 16.04
  package: snapd 2.11+0.16.04

  Notably, I'm running this in an LXD container (version: 2.0.0.rc9).

  -

  $ sudo snap install hello-world
  64.75 MB / 64.75 MB 
[==]
 100.00 % 2.85 MB/s 

  error: cannot perform the following tasks:
  - Mount snap "ubuntu-core" (122) ([start snap-ubuntu\x2dcore-122.mount] 
failed with exit status 1: Job for snap-ubuntu\x2dcore-122.mount failed. See 
"systemctl status "snap-ubuntu\\x2dcore-122.mount"" and "journalctl -xe" for 
details.
  )
  $ ls -la /snap
  total 4K
  drwxr-xr-x 3 root root 4096 Aug  8 17:49 ubuntu-core
  $ ls -la /snap/ubuntu-core/
  total 4K
  drwxr-xr-x 2 root root 4096 Aug  8 17:49 122
  $ ls -la /snap/ubuntu-core/122/
  total 0K
  $ systemctl status "snap-ubuntu\\x2dcore-122.mount"
  ● snap-ubuntu\x2dcore-122.mount - Mount unit for ubuntu-core
 Loaded: loaded (/etc/systemd/system/snap-ubuntu\x2dcore-122.mount; 
enabled; vendor preset: enabled)
 Active: failed (Result: exit-code) since Mon 2016-08-08 17:49:36 UTC; 6min 
ago
  Where: /snap/ubuntu-core/122
   What: /var/lib/snapd/snaps/ubuntu-core_122.snap
Process: 31781 ExecMount=/bin/mount 
/var/lib/snapd/snaps/ubuntu-core_122.snap /snap/ubuntu-core/122 -t squashfs 
(code=exited, status=32)

  Aug 08 17:49:35 my-host systemd[1]: Mounting Mount unit for ubuntu-core...
  Aug 08 17:49:35 my-host mount[31781]: mount: /snap/ubuntu-core/122: mount 
failed: Unknown error -1
  Aug 08 17:49:36 my-host systemd[1]: snap-ubuntu\x2dcore-122.mount: Mount 
process exited, code=exited status=32
  Aug 08 17:49:36 my-host systemd[1]: Failed to mount Mount unit for 
ubuntu-core.
  Aug 08 17:49:36 my-host systemd[1]: snap-ubuntu\x2dcore-122.mount: Unit 
entered failed state.

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

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

[Kernel-packages] [Bug 1567597] Re: implement 'complain mode' in seccomp for developer mode with snaps

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

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

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => Tyler Hicks (tyhicks)

** Changed in: libseccomp (Ubuntu)
 Assignee: (unassigned) => Tyler Hicks (tyhicks)

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

Title:
  implement 'complain mode' in seccomp for developer mode with snaps

Status in Snappy:
  In Progress
Status in libseccomp package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  In Progress

Bug description:
  A requirement for snappy is that a snap may be placed in developer
  mode which will put the security sandbox in complain mode such that
  violations against policy are logged, but permitted. In this manner
  learning tools can be written to parse the logs, etc and make
  developing on snappy easier.

  Unfortunately with seccomp only SCMP_ACT_KILL logs to dmesg and while
  we can set complain mode to permit all calls, they are not logged at
  this time. I've discussed this with upstream and we are working
  together on the approach. This may require a kernel patch and an
  update to libseccomp, to filing this bug for now as a placeholder and
  we'll add other tasks as necessary.

  UPDATE: ubuntu-core-launcher now supports the '@complain' directive
  that is a synonym for '@unrestricted' so people can at least turn on
  developer mode and not be blocked by seccomp. Proper complain mode for
  seccomp needs to still be implemented (this bug).

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

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

[Kernel-packages] [Bug 1567597] Re: implement 'complain mode' in seccomp for developer mode with snaps

A status update is in order. We settled on a design that meets
everyone's kernel needs. Those patches have been accepted into linux-
next and they're on their way into 4.14.

  https://lkml.kernel.org/r/%3C20170815220319.GA63342@beast%3E

I've submitted Artful backports to the kernel team:

  https://lists.ubuntu.com/archives/kernel-team/2017-August/086691.html

I've reached out to the libseccomp maintainer to discuss some design
aspects that needed to be sorted out and now I've proposed a PR for
libseccomp:

  https://github.com/seccomp/libseccomp/pull/92

I'll have a little more work to do on libseccomp-golang once the
libseccomp PR is reviewed. Then I can start the SRUs. The snap-seccomp
/snap-confine changes are straightforward and small so they shouldn't be
a problem.

Everything is finally coming together but there have been a lot of
moving pieces (and people) involved in landing all the changes.

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

Title:
  implement 'complain mode' in seccomp for developer mode with snaps

Status in Snappy:
  In Progress
Status in libseccomp package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  In Progress

Bug description:
  A requirement for snappy is that a snap may be placed in developer
  mode which will put the security sandbox in complain mode such that
  violations against policy are logged, but permitted. In this manner
  learning tools can be written to parse the logs, etc and make
  developing on snappy easier.

  Unfortunately with seccomp only SCMP_ACT_KILL logs to dmesg and while
  we can set complain mode to permit all calls, they are not logged at
  this time. I've discussed this with upstream and we are working
  together on the approach. This may require a kernel patch and an
  update to libseccomp, to filing this bug for now as a placeholder and
  we'll add other tasks as necessary.

  UPDATE: ubuntu-core-launcher now supports the '@complain' directive
  that is a synonym for '@unrestricted' so people can at least turn on
  developer mode and not be blocked by seccomp. Proper complain mode for
  seccomp needs to still be implemented (this bug).

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

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

[Kernel-packages] [Bug 1705748] Re: Samsung SSD 960 EVO 500GB refused to change power state

2017-08-25 Thread Steve Roberts

Using  http://people.canonical.com/~khfeng/lp1705748-sleep/

with "nvme_core.default_ps_max_latency_us=1500", to disable deepest
power state

Been through several suspend/resume cycles so far and seems to be ok.

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

Title:
  Samsung SSD 960 EVO 500GB refused to change power state

Status in linux package in Ubuntu:
  In Progress

Bug description:
  Originally thought my issue was same as this:
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678184
  but requested to report as separate bug

  System becomes unusable at seemingly random times but especially after
  resume from suspend due to disk 'disappearing' becoming inaccessible,
  with hundreds of I/O errors logged.

  After viewing the above bug report yesterday as a quick temporary fix I added 
kernel param, updated grub, etc with:
  GRUB_CMDLINE_LINUX_DEFAULT="nvme_core.default_ps_max_latency_us=0"

  System appears to have been stable for the last day, but is presumably
  using more power than it should.

  System, drive details below:

  M2 nvme drive: Samsung SSD 960 EVO 500GB

  Ubuntu 4.10.0-26.30~16.04.1-generic 4.10.17

  M/B Asus Prime B350m-A
  Ryzen 1600 cpu

  Jul 20 16:32:59 phs08 kernel: [ 190.893571] INVALID_DEVICE_REQUEST 
device=00:00.0 address=0xfffdf800 flags=0x0a00]
  Jul 20 16:33:05 phs08 kernel: [ 197.010928] nvme :01:00.0: controller is 
down; will reset: CSTS=0x, PCI_STATUS=0x
  Jul 20 16:33:05 phs08 kernel: [ 197.046980] pci_raw_set_power_state: 4 
callbacks suppressed
  Jul 20 16:33:05 phs08 kernel: [ 197.046985] nvme :01:00.0: Refused to 
change power state, currently in D3
  Jul 20 16:33:05 phs08 kernel: [ 197.047163] nvme nvme0: Removing after probe 
failure status: -19
  Jul 20 16:33:05 phs08 kernel: [ 197.047182] nvme0n1: detected capacity change 
from 500107862016 to 0
  Jul 20 16:33:05 phs08 kernel: [ 197.047793] blk_update_request: I/O error, 
dev nvme0n1, sector 0

  
  nvme list

  /dev/nvme0n1 S3EUNX0J305518L Samsung SSD 960 EVO 500GB 1.2 1 125.20 GB
  / 500.11 GB 512 B + 0 B 2B7QCXE7

  sudo nvme id-ctrl /dev/nvme0

  NVME Identify Controller:
  vid : 0x144d
  ssvid : 0x144d
  sn : S3EUNX0J305518L
  mn : Samsung SSD 960 EVO 500GB
  fr : 2B7QCXE7
  rab : 2
  ieee : 002538
  cmic : 0
  mdts : 9
  cntlid : 2
  ver : 10200
  rtd3r : 7a120
  rtd3e : 4c4b40
  oaes : 0
  oacs : 0x7
  acl : 7
  aerl : 3
  frmw : 0x16
  lpa : 0x3
  elpe : 63
  npss : 4
  avscc : 0x1
  apsta : 0x1
  wctemp : 350
  cctemp : 352
  mtfa : 0
  hmpre : 0
  hmmin : 0
  tnvmcap : 500107862016
  unvmcap : 0
  rpmbs : 0
  sqes : 0x66
  cqes : 0x44
  nn : 1
  oncs : 0x1f
  fuses : 0
  fna : 0x5
  vwc : 0x1
  awun : 255
  awupf : 0
  nvscc : 1
  acwu : 0
  sgls : 0
  ps 0 : mp:6.04W operational enlat:0 exlat:0 rrt:0 rrl:0
rwt:0 rwl:0 idle_power:- active_power:-
  ps 1 : mp:5.09W operational enlat:0 exlat:0 rrt:1 rrl:1
rwt:1 rwl:1 idle_power:- active_power:-
  ps 2 : mp:4.08W operational enlat:0 exlat:0 rrt:2 rrl:2
rwt:2 rwl:2 idle_power:- active_power:-
  ps 3 : mp:0.0400W non-operational enlat:210 exlat:1500 rrt:3 rrl:3
rwt:3 rwl:3 idle_power:- active_power:-
  ps 4 : mp:0.0050W non-operational enlat:2200 exlat:6000 rrt:4 rrl:4
rwt:4 rwl:4 idle_power:- active_power:-
  --- 
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  drgrumpy   2192 F pulseaudio
   /dev/snd/pcmC1D0p:   drgrumpy   2192 F...m pulseaudio
   /dev/snd/controlC1:  drgrumpy   2192 F pulseaudio
  DistroRelease: Linux 18.2
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=a6896cdd-6bac-4e7f-9e13-55460859c3ec
  InstallationDate: Installed on 2017-07-06 (15 days ago)
  InstallationMedia: Linux Mint 18.2 "Sonya" - Release amd64 20170628
  IwConfig:
   lono wireless extensions.
   
   enp37s0   no wireless extensions.
  MachineType: System manufacturer System Product Name
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=en_GB:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-26-generic 
root=UUID=f7ae652b-cbf6-48b8-bc6a-d3963957ab57 ro 
nvme_core.default_ps_max_latency_us=0
  ProcVersionSignature: Ubuntu 4.10.0-26.30~16.04.1-generic 4.10.17
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-26-generic N/A
   linux-backports-modules-4.10.0-26-generic  N/A
   linux-firmware 1.157.11
  RfKill:
   
  Tags:  sonya
  Uname: Linux 4.10.0-26-generic x86_64
  UpgradeStatus: No upgrade log present (probably

[Kernel-packages] [Bug 441169] [NEW] CPU Scaling no longer supported on Single core 1.7Ghz Centrino

You have been subscribed to a public bug:

Binary package hint: libcpufreq0

Hi, I've noticed slow performance. My details are similar to the forum
post "Single core 1.7Ghz Centrino stuck at 600MHz?" from 12th May 2009.
The post has no answer or further reference so I raised a bug here and
I'll cross reference it on the Forum. My processor is stuck at 798MHz
and on adding the cpufreq-applet I was treated to an error, "Warning CPU
Frequency Scaling not supported". I have a Dell Inspiron 9300. Regards,
Richard

Here is the original post:



I'm been experiencing quite a slow performance on Ubuntu, specially on
flash videos, and finally I discovered the it was not xorg or firefox or
the ati driver but rather the cpu is stuck at 600MHz according to
/proc/cpuinfo.

model name : Intel(R) Pentium(R) M processor 1.70GHz
stepping : 6
cpu MHz : 600.012


I had been experiencing sudden burst in performance for a while, and now I'm 
guessing that all of a sudden the cpu just "breaks free" and goes to full power 
for absolutely no reason, without my intervention. I'm waiting for this to 
happen again, but I'm pretty sure this is the problem.

I've been trying to fix it for a while but it's been quite difficult. I
installed powernowd (success was reported here
http://ubuntuforums.org/showthread.php?t=1134657), and running it says

Please make sure that:
- 
- That you have sysfs mounted /sys
- That you have the core cpufreq and cpufreq-userspace
modules loaded into your kernel

Which I don't by checking lsmod | grep cpu, and no wonder, because
according to something I read the new ubuntu kernel has the cpufreq
modules built-in. But something is indeed failing because running ls
/sys/devices/system/cpu/cpu0 reveals

cpuidle crash_notes topology

The frequency part is missing.

Any input? Can I refer to any log for further info?

Thx in advance, I would really like to fix this thing... O_o
Last edited by Cenoforums; May 12th, 2009 at 04:14 PM.. Reason: reference post

ProblemType: Bug
Architecture: i386
DistroRelease: Ubuntu 9.04
ExecutablePath: /usr/lib/gnome-applets/cpufreq-applet
Package: gnome-applets 2.26.1-0ubuntu1
ProcEnviron:
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
SourcePackage: gnome-applets
Uname: Linux 2.6.28-6-386 i686

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


** Tags: apport-bug i386
-- 
CPU Scaling no longer supported on Single core 1.7Ghz Centrino
https://bugs.launchpad.net/bugs/441169
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to linux in Ubuntu.

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

[Kernel-packages] [Bug 1567597] Re: implement 'complain mode' in seccomp for developer mode with snaps

2017-08-25 Thread Kyle Fazzari

Thanks for the update, Tyler. I know this has been a long road, but the
cumulative effect of everyone's hard work on this particular front will
be huge. I'm very much looking forward to this.

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

Title:
  implement 'complain mode' in seccomp for developer mode with snaps

Status in Snappy:
  In Progress
Status in libseccomp package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  In Progress

Bug description:
  A requirement for snappy is that a snap may be placed in developer
  mode which will put the security sandbox in complain mode such that
  violations against policy are logged, but permitted. In this manner
  learning tools can be written to parse the logs, etc and make
  developing on snappy easier.

  Unfortunately with seccomp only SCMP_ACT_KILL logs to dmesg and while
  we can set complain mode to permit all calls, they are not logged at
  this time. I've discussed this with upstream and we are working
  together on the approach. This may require a kernel patch and an
  update to libseccomp, to filing this bug for now as a placeholder and
  we'll add other tasks as necessary.

  UPDATE: ubuntu-core-launcher now supports the '@complain' directive
  that is a synonym for '@unrestricted' so people can at least turn on
  developer mode and not be blocked by seccomp. Proper complain mode for
  seccomp needs to still be implemented (this bug).

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

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

[Kernel-packages] [Bug 441169] Re: CPU Scaling no longer supported on Single core 1.7Ghz Centrino

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

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

Title:
  CPU Scaling no longer supported on Single core 1.7Ghz Centrino

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Binary package hint: libcpufreq0

  Hi, I've noticed slow performance. My details are similar to the forum
  post "Single core 1.7Ghz Centrino stuck at 600MHz?" from 12th May
  2009. The post has no answer or further reference so I raised a bug
  here and I'll cross reference it on the Forum. My processor is stuck
  at 798MHz and on adding the cpufreq-applet I was treated to an error,
  "Warning CPU Frequency Scaling not supported". I have a Dell Inspiron
  9300. Regards, Richard

  Here is the original post:

  

  I'm been experiencing quite a slow performance on Ubuntu, specially on
  flash videos, and finally I discovered the it was not xorg or firefox
  or the ati driver but rather the cpu is stuck at 600MHz according to
  /proc/cpuinfo.

  model name : Intel(R) Pentium(R) M processor 1.70GHz
  stepping : 6
  cpu MHz : 600.012

  
  I had been experiencing sudden burst in performance for a while, and now I'm 
guessing that all of a sudden the cpu just "breaks free" and goes to full power 
for absolutely no reason, without my intervention. I'm waiting for this to 
happen again, but I'm pretty sure this is the problem.

  I've been trying to fix it for a while but it's been quite difficult.
  I installed powernowd (success was reported here
  http://ubuntuforums.org/showthread.php?t=1134657), and running it says

  Please make sure that:
  - 
  - That you have sysfs mounted /sys
  - That you have the core cpufreq and cpufreq-userspace
  modules loaded into your kernel

  Which I don't by checking lsmod | grep cpu, and no wonder, because
  according to something I read the new ubuntu kernel has the cpufreq
  modules built-in. But something is indeed failing because running ls
  /sys/devices/system/cpu/cpu0 reveals

  cpuidle crash_notes topology

  The frequency part is missing.

  Any input? Can I refer to any log for further info?

  Thx in advance, I would really like to fix this thing... O_o
  Last edited by Cenoforums; May 12th, 2009 at 04:14 PM.. Reason: reference post

  ProblemType: Bug
  Architecture: i386
  DistroRelease: Ubuntu 9.04
  ExecutablePath: /usr/lib/gnome-applets/cpufreq-applet
  Package: gnome-applets 2.26.1-0ubuntu1
  ProcEnviron:
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-applets
  Uname: Linux 2.6.28-6-386 i686

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

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

[Kernel-packages] [Bug 441169] Re: CPU Scaling no longer supported on Single core 1.7Ghz Centrino

2017-08-25 Thread Connor Imes

If you (or anybody else) still have this hardware, is scaling working
properly these days?

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

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

Title:
  CPU Scaling no longer supported on Single core 1.7Ghz Centrino

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Binary package hint: libcpufreq0

  Hi, I've noticed slow performance. My details are similar to the forum
  post "Single core 1.7Ghz Centrino stuck at 600MHz?" from 12th May
  2009. The post has no answer or further reference so I raised a bug
  here and I'll cross reference it on the Forum. My processor is stuck
  at 798MHz and on adding the cpufreq-applet I was treated to an error,
  "Warning CPU Frequency Scaling not supported". I have a Dell Inspiron
  9300. Regards, Richard

  Here is the original post:

  

  I'm been experiencing quite a slow performance on Ubuntu, specially on
  flash videos, and finally I discovered the it was not xorg or firefox
  or the ati driver but rather the cpu is stuck at 600MHz according to
  /proc/cpuinfo.

  model name : Intel(R) Pentium(R) M processor 1.70GHz
  stepping : 6
  cpu MHz : 600.012

  
  I had been experiencing sudden burst in performance for a while, and now I'm 
guessing that all of a sudden the cpu just "breaks free" and goes to full power 
for absolutely no reason, without my intervention. I'm waiting for this to 
happen again, but I'm pretty sure this is the problem.

  I've been trying to fix it for a while but it's been quite difficult.
  I installed powernowd (success was reported here
  http://ubuntuforums.org/showthread.php?t=1134657), and running it says

  Please make sure that:
  - 
  - That you have sysfs mounted /sys
  - That you have the core cpufreq and cpufreq-userspace
  modules loaded into your kernel

  Which I don't by checking lsmod | grep cpu, and no wonder, because
  according to something I read the new ubuntu kernel has the cpufreq
  modules built-in. But something is indeed failing because running ls
  /sys/devices/system/cpu/cpu0 reveals

  cpuidle crash_notes topology

  The frequency part is missing.

  Any input? Can I refer to any log for further info?

  Thx in advance, I would really like to fix this thing... O_o
  Last edited by Cenoforums; May 12th, 2009 at 04:14 PM.. Reason: reference post

  ProblemType: Bug
  Architecture: i386
  DistroRelease: Ubuntu 9.04
  ExecutablePath: /usr/lib/gnome-applets/cpufreq-applet
  Package: gnome-applets 2.26.1-0ubuntu1
  ProcEnviron:
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-applets
  Uname: Linux 2.6.28-6-386 i686

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

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

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

2017-08-25 Thread Connor Imes

** Package changed: cpufrequtils (Ubuntu) => cpufreqd (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/933443

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

Status in cpufreqd package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Invalid

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

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

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

[Kernel-packages] [Bug 1713195] [NEW] Backlight Won't Adjust, Xorg Failures

Public bug reported:

Previously had Ubuntu 16.04 installed on this machine, but I installed
Xubuntu over it including formatting my partitions. I did not have
issues with adjusting the brightness, getting the screen to show, or
Xorg crashes prior to the second install (ie the Ubuntu worked fine).

This bug falls under "Backlight control does not work and there are no
entries in /sys/class/backlight" category. I also experience the Blank
Screen at Startup issue, which is only remedied by adding nomodeset to
the grub boot options.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-92-generic 4.4.0-92.115
ProcVersionSignature: Ubuntu 4.4.0-92.115-generic 4.4.76
Uname: Linux 4.4.0-92-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  sebastian   6377 F pulseaudio
CurrentDesktop: XFCE
Date: Fri Aug 25 22:42:52 2017
HibernationDevice: RESUME=UUID=14b7bd47-d085-4964-8823-eedc74c0391d
InstallationDate: Installed on 2017-08-20 (6 days ago)
InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
MachineType: Dell Inc. Inspiron 15-3552
ProcFB:
 
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-92-generic.efi.signed 
root=UUID=fe7fca66-0701-4ee1-bdfe-baf9f4bffcab ro nomodeset
RelatedPackageVersions:
 linux-restricted-modules-4.4.0-92-generic N/A
 linux-backports-modules-4.4.0-92-generic  N/A
 linux-firmware1.157.11
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/26/2016
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 4.0.7
dmi.board.name: 0787MR
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: Not Specified
dmi.modalias: 
dmi:bvnDellInc.:bvr4.0.7:bd04/26/2016:svnDellInc.:pnInspiron15-3552:pvr4.0.7:rvnDellInc.:rn0787MR:rvrA00:cvnDellInc.:ct8:cvrNotSpecified:
dmi.product.name: Inspiron 15-3552
dmi.product.version: 4.0.7
dmi.sys.vendor: Dell Inc.

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


** Tags: amd64 apport-bug xenial

** Attachment added: "acpi"
   https://bugs.launchpad.net/bugs/1713195/+attachment/4939012/+files/acpi

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

Title:
  Backlight Won't Adjust, Xorg Failures

Status in linux package in Ubuntu:
  New

Bug description:
  Previously had Ubuntu 16.04 installed on this machine, but I installed
  Xubuntu over it including formatting my partitions. I did not have
  issues with adjusting the brightness, getting the screen to show, or
  Xorg crashes prior to the second install (ie the Ubuntu worked fine).

  This bug falls under "Backlight control does not work and there are no
  entries in /sys/class/backlight" category. I also experience the Blank
  Screen at Startup issue, which is only remedied by adding nomodeset to
  the grub boot options.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-92-generic 4.4.0-92.115
  ProcVersionSignature: Ubuntu 4.4.0-92.115-generic 4.4.76
  Uname: Linux 4.4.0-92-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  sebastian   6377 F pulseaudio
  CurrentDesktop: XFCE
  Date: Fri Aug 25 22:42:52 2017
  HibernationDevice: RESUME=UUID=14b7bd47-d085-4964-8823-eedc74c0391d
  InstallationDate: Installed on 2017-08-20 (6 days ago)
  InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: Dell Inc. Inspiron 15-3552
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-92-generic.efi.signed 
root=UUID=fe7fca66-0701-4ee1-bdfe-baf9f4bffcab ro nomodeset
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-92-generic N/A
   linux-backports-modules-4.4.0-92-generic  N/A
   linux-firmware1.157.11
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/26/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 4.0.7
  dmi.board.name: 0787MR
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvr4.0.7:bd04/26/2016:svnDellInc.:pnInspiron15-3552:pvr4.0.7:rvnDellInc.:rn0787MR:rvrA00:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.name: Inspiron 15-3552
  dmi.product.version: 4.0.7
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1713195] Re: Backlight Won't Adjust, Xorg Failures

** Attachment added: "acpidump.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1713195/+attachment/4939030/+files/acpidump.txt

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

Title:
  Backlight Won't Adjust, Xorg Failures

Status in linux package in Ubuntu:
  New

Bug description:
  Previously had Ubuntu 16.04 installed on this machine, but I installed
  Xubuntu over it including formatting my partitions. I did not have
  issues with adjusting the brightness, getting the screen to show, or
  Xorg crashes prior to the second install (ie the Ubuntu worked fine).

  This bug falls under "Backlight control does not work and there are no
  entries in /sys/class/backlight" category. I also experience the Blank
  Screen at Startup issue, which is only remedied by adding nomodeset to
  the grub boot options.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-92-generic 4.4.0-92.115
  ProcVersionSignature: Ubuntu 4.4.0-92.115-generic 4.4.76
  Uname: Linux 4.4.0-92-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  sebastian   6377 F pulseaudio
  CurrentDesktop: XFCE
  Date: Fri Aug 25 22:42:52 2017
  HibernationDevice: RESUME=UUID=14b7bd47-d085-4964-8823-eedc74c0391d
  InstallationDate: Installed on 2017-08-20 (6 days ago)
  InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: Dell Inc. Inspiron 15-3552
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-92-generic.efi.signed 
root=UUID=fe7fca66-0701-4ee1-bdfe-baf9f4bffcab ro nomodeset
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-92-generic N/A
   linux-backports-modules-4.4.0-92-generic  N/A
   linux-firmware1.157.11
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/26/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 4.0.7
  dmi.board.name: 0787MR
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvr4.0.7:bd04/26/2016:svnDellInc.:pnInspiron15-3552:pvr4.0.7:rvnDellInc.:rn0787MR:rvrA00:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.name: Inspiron 15-3552
  dmi.product.version: 4.0.7
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1713195] Re: Backlight Won't Adjust, Xorg Failures

** Attachment added: "dmidecode.log"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1713195/+attachment/4939031/+files/dmidecode.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/1713195

Title:
  Backlight Won't Adjust, Xorg Failures

Status in linux package in Ubuntu:
  New

Bug description:
  Previously had Ubuntu 16.04 installed on this machine, but I installed
  Xubuntu over it including formatting my partitions. I did not have
  issues with adjusting the brightness, getting the screen to show, or
  Xorg crashes prior to the second install (ie the Ubuntu worked fine).

  This bug falls under "Backlight control does not work and there are no
  entries in /sys/class/backlight" category. I also experience the Blank
  Screen at Startup issue, which is only remedied by adding nomodeset to
  the grub boot options.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-92-generic 4.4.0-92.115
  ProcVersionSignature: Ubuntu 4.4.0-92.115-generic 4.4.76
  Uname: Linux 4.4.0-92-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  sebastian   6377 F pulseaudio
  CurrentDesktop: XFCE
  Date: Fri Aug 25 22:42:52 2017
  HibernationDevice: RESUME=UUID=14b7bd47-d085-4964-8823-eedc74c0391d
  InstallationDate: Installed on 2017-08-20 (6 days ago)
  InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: Dell Inc. Inspiron 15-3552
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-92-generic.efi.signed 
root=UUID=fe7fca66-0701-4ee1-bdfe-baf9f4bffcab ro nomodeset
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-92-generic N/A
   linux-backports-modules-4.4.0-92-generic  N/A
   linux-firmware1.157.11
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/26/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 4.0.7
  dmi.board.name: 0787MR
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvr4.0.7:bd04/26/2016:svnDellInc.:pnInspiron15-3552:pvr4.0.7:rvnDellInc.:rn0787MR:rvrA00:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.name: Inspiron 15-3552
  dmi.product.version: 4.0.7
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1713195] Re: Backlight Won't Adjust, Xorg Failures

** Attachment added: "fwts_method"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1713195/+attachment/4939033/+files/fwts_method

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

Title:
  Backlight Won't Adjust, Xorg Failures

Status in linux package in Ubuntu:
  New

Bug description:
  Previously had Ubuntu 16.04 installed on this machine, but I installed
  Xubuntu over it including formatting my partitions. I did not have
  issues with adjusting the brightness, getting the screen to show, or
  Xorg crashes prior to the second install (ie the Ubuntu worked fine).

  This bug falls under "Backlight control does not work and there are no
  entries in /sys/class/backlight" category. I also experience the Blank
  Screen at Startup issue, which is only remedied by adding nomodeset to
  the grub boot options.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-92-generic 4.4.0-92.115
  ProcVersionSignature: Ubuntu 4.4.0-92.115-generic 4.4.76
  Uname: Linux 4.4.0-92-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  sebastian   6377 F pulseaudio
  CurrentDesktop: XFCE
  Date: Fri Aug 25 22:42:52 2017
  HibernationDevice: RESUME=UUID=14b7bd47-d085-4964-8823-eedc74c0391d
  InstallationDate: Installed on 2017-08-20 (6 days ago)
  InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: Dell Inc. Inspiron 15-3552
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-92-generic.efi.signed 
root=UUID=fe7fca66-0701-4ee1-bdfe-baf9f4bffcab ro nomodeset
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-92-generic N/A
   linux-backports-modules-4.4.0-92-generic  N/A
   linux-firmware1.157.11
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/26/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 4.0.7
  dmi.board.name: 0787MR
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvr4.0.7:bd04/26/2016:svnDellInc.:pnInspiron15-3552:pvr4.0.7:rvnDellInc.:rn0787MR:rvrA00:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.name: Inspiron 15-3552
  dmi.product.version: 4.0.7
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1713195] Re: Backlight Won't Adjust, Xorg Failures

** Attachment added: "fwts"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1713195/+attachment/4939032/+files/fwts

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

Title:
  Backlight Won't Adjust, Xorg Failures

Status in linux package in Ubuntu:
  New

Bug description:
  Previously had Ubuntu 16.04 installed on this machine, but I installed
  Xubuntu over it including formatting my partitions. I did not have
  issues with adjusting the brightness, getting the screen to show, or
  Xorg crashes prior to the second install (ie the Ubuntu worked fine).

  This bug falls under "Backlight control does not work and there are no
  entries in /sys/class/backlight" category. I also experience the Blank
  Screen at Startup issue, which is only remedied by adding nomodeset to
  the grub boot options.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-92-generic 4.4.0-92.115
  ProcVersionSignature: Ubuntu 4.4.0-92.115-generic 4.4.76
  Uname: Linux 4.4.0-92-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  sebastian   6377 F pulseaudio
  CurrentDesktop: XFCE
  Date: Fri Aug 25 22:42:52 2017
  HibernationDevice: RESUME=UUID=14b7bd47-d085-4964-8823-eedc74c0391d
  InstallationDate: Installed on 2017-08-20 (6 days ago)
  InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: Dell Inc. Inspiron 15-3552
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-92-generic.efi.signed 
root=UUID=fe7fca66-0701-4ee1-bdfe-baf9f4bffcab ro nomodeset
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-92-generic N/A
   linux-backports-modules-4.4.0-92-generic  N/A
   linux-firmware1.157.11
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/26/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 4.0.7
  dmi.board.name: 0787MR
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvr4.0.7:bd04/26/2016:svnDellInc.:pnInspiron15-3552:pvr4.0.7:rvnDellInc.:rn0787MR:rvrA00:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.name: Inspiron 15-3552
  dmi.product.version: 4.0.7
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1713195] Re: Backlight Won't Adjust, Xorg Failures

** Attachment added: "results.log"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1713195/+attachment/4939034/+files/results.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/1713195

Title:
  Backlight Won't Adjust, Xorg Failures

Status in linux package in Ubuntu:
  New

Bug description:
  Previously had Ubuntu 16.04 installed on this machine, but I installed
  Xubuntu over it including formatting my partitions. I did not have
  issues with adjusting the brightness, getting the screen to show, or
  Xorg crashes prior to the second install (ie the Ubuntu worked fine).

  This bug falls under "Backlight control does not work and there are no
  entries in /sys/class/backlight" category. I also experience the Blank
  Screen at Startup issue, which is only remedied by adding nomodeset to
  the grub boot options.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-92-generic 4.4.0-92.115
  ProcVersionSignature: Ubuntu 4.4.0-92.115-generic 4.4.76
  Uname: Linux 4.4.0-92-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  sebastian   6377 F pulseaudio
  CurrentDesktop: XFCE
  Date: Fri Aug 25 22:42:52 2017
  HibernationDevice: RESUME=UUID=14b7bd47-d085-4964-8823-eedc74c0391d
  InstallationDate: Installed on 2017-08-20 (6 days ago)
  InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: Dell Inc. Inspiron 15-3552
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-92-generic.efi.signed 
root=UUID=fe7fca66-0701-4ee1-bdfe-baf9f4bffcab ro nomodeset
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-92-generic N/A
   linux-backports-modules-4.4.0-92-generic  N/A
   linux-firmware1.157.11
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/26/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 4.0.7
  dmi.board.name: 0787MR
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvr4.0.7:bd04/26/2016:svnDellInc.:pnInspiron15-3552:pvr4.0.7:rvnDellInc.:rn0787MR:rvrA00:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.name: Inspiron 15-3552
  dmi.product.version: 4.0.7
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1700618] Re: Internet connection not working while torrenting

[Expired for linux (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  Internet connection not working while torrenting

Status in linux package in Ubuntu:
  Expired

Bug description:
  Hello, 
  I am using KDE Neon (Ubuntu 16.04). 
  My Internet connection drops suddenly while I am using any torrent client 
(tested with qbittorrent, ktorrent). The wifi does not disconnect in the 
process, signal strength remains full, just there is not internet. 
  As a temporary solution, disabling and enabling the wifi through dedicated 
wifi key works.

  Another point, if I am just using a torrent client (qbittorrent) and
  no other application is using internet (chrome, firefox, telegram),
  then connection behaves normally.

  I don't know which application is responsible for the issue or is it a KDE 
Neon thing.
  Please let me know of any other info that I can provide.

  Thank you.

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

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

[Kernel-packages] [Bug 1695829] Re: IP Subnet to internet routing fails 5x/day after latest 16.04 LTS updates

[Expired for linux (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  IP Subnet to internet routing fails 5x/day after latest 16.04 LTS
  updates

Status in linux package in Ubuntu:
  Expired

Bug description:
  Since updating Ubuntu 16.04.02 LTS with all latest patches on 6/2, my
  subnet internet routing is failing 5x+/day for my Windows 10 machine.
  Unfortunately, Windows 10 is also a moving target, which also updated
  6/2, about when this problem started. Bug report also filed with MS.

  Why I think it's Ubuntu... When Windows 10 based web pages stop
  loading, email stops transmitting, and internet-based CAD licensing
  stops working, I can get everything working like new again by typing
  "firehol start", which refreshes iptables entries.  So I suspect the
  issue might be related to either the Linux kernel or iptables.

  I also see another bug dated 2-Jun-2017 for IP subnet routing, but
  that one is running on an ARM processor.  Mine is AMD FX-8120, Ubuntu
  16.04.2 LTS x64. The reported problem sounds similar.

  I performed an IP Tables dump during "operating" and "not routing"
  states.  I can't see any difference between the two dumps, but running
  firehol start clears the problem.

  While in the "problem state", my Ubuntu server does have internet 
connectivity.  i.e. Loading web pages on Firefox on the Server/router does 
work.  On the "routed" Windows 10 machine, what doesn't work are; ping 
(internet), Firefox (internet), Thunderbird (internet)...  From the Windows 10 
machine what does work are; ping (server), Firefox (server apache web pages), 
Thunderbird (server imaps accounts).  So the Windows 10 machine still has full 
server access over gigabit ethernet, but can't see any internet based services, 
where IP routing is required to succeed.  "firehol start" restores routing 
until for a brief time when the Windows machine is busy accessing the internet. 
 Routing stayed up all night when there was no Windows 10 internet routing 
activity.  Resuming activity in the morning caused a quick routing failure.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  craig  7726 F pulseaudio
   /dev/snd/controlC0:  craig  7726 F pulseaudio
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=5967ff24-0a8c-4a29-bd33-408fc996d7a5
  InstallationDate: Installed on 2016-06-13 (357 days ago)
  InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.3)
  MachineType: To be filled by O.E.M. To be filled by O.E.M.
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-78-generic 
root=UUID=5764c9d8-e512-48d9-8496-58db180684ac ro
  ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62
  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-78-generic N/A
   linux-backports-modules-4.4.0-78-generic  N/A
   linux-firmware1.157.10
  RfKill:
   
  Tags:  xenial
  Uname: Linux 4.4.0-78-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 11/24/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0901
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: SABERTOOTH 990FX
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  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.:bvr0901:bd11/24/2011:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnSABERTOOTH990FX:rvrRev1.xx: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/1695829/+subscriptions

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

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