date:20170720

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

** Tags added: block-proposed

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  backports: 1704995
  derivatives:
  kernel-stable-phase:Uploaded
  kernel-stable-phase-changed:Thursday, 20. July 2017 17:31 UTC
  
  -- swm properties --
+ boot-testing-requested: true
  phase: Uploaded

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

Title:
  linux: 3.13.0-126.175 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Confirmed
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in 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: 1704995
  derivatives:
  kernel-stable-phase:Uploaded
  kernel-stable-phase-changed:Thursday, 20. July 2017 17:31 UTC

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

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

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

[Kernel-packages] [Bug 1705003] Re: linux: 3.19.0-89.97 -proposed tracker

2017-07-20 Thread Po-Hsu Lin

No bug was tagged with verification needed this time.

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

** Changed in: kernel-sru-workflow/verification-testing
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Po-Hsu Lin 
(cypressyew)

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

Title:
  linux: 3.19.0-89.97 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux package in Ubuntu:
  Confirmed
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: 1705004
  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/1705003/+subscriptions

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

[Kernel-packages] [Bug 305628] that's so great

2017-07-20 Thread mfranze

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


** Attachment added: "497E69E0CD999DB561DC613430544B38.jpg"
   
https://bugs.launchpad.net/bugs/305628/+attachment/4918509/+files/497E69E0CD999DB561DC613430544B38.jpg

** Attachment added: "497E69E0CD999DB561DC613430544B381.jpg"
   
https://bugs.launchpad.net/bugs/305628/+attachment/4918510/+files/497E69E0CD999DB561DC613430544B381.jpg

** Attachment added: "497E69E0CD999DB561DC613430544B382.jpg"
   
https://bugs.launchpad.net/bugs/305628/+attachment/4918511/+files/497E69E0CD999DB561DC613430544B382.jpg

** Attachment added: "497E69E0CD999DB561DC613430544B383.png"
   
https://bugs.launchpad.net/bugs/305628/+attachment/4918512/+files/497E69E0CD999DB561DC613430544B383.png

** Attachment added: "497E69E0CD999DB561DC613430544B384.png"
   
https://bugs.launchpad.net/bugs/305628/+attachment/4918513/+files/497E69E0CD999DB561DC613430544B384.png

** Attachment added: "497E69E0CD999DB561DC613430544B385.png"
   
https://bugs.launchpad.net/bugs/305628/+attachment/4918514/+files/497E69E0CD999DB561DC613430544B385.png

** Attachment added: "497E69E0CD999DB561DC613430544B386.png"
   
https://bugs.launchpad.net/bugs/305628/+attachment/4918515/+files/497E69E0CD999DB561DC613430544B386.png

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

Title:
  package linux-image-2.6.27-7-generic 2.6.27-7.14 failed to
  install/upgrade: impossibile creare il link per la copia di sicurezza
  di `./boot/vmlinuz-2.6.27-7-generic' prima di installarne la nuova
  versione: Funzione non permessa

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  It seems authorization missing to create a link

  ProblemType: Package
  Architecture: i386
  DistroRelease: Ubuntu 8.10
  ErrorMessage: impossibile creare il link per la copia di sicurezza di 
`./boot/vmlinuz-2.6.27-7-generic' prima di installarne la nuova versione: 
Funzione non permessa
  Package: linux-image-2.6.27-7-generic 2.6.27-7.14
  ProcCmdLine: User Name=UUID=420E-19E7 loop=/hostname/disks/home/username.disk 
ro ROOTFLAGS=sync quiet splash
  ProcVersionSignature: Ubuntu 2.6.27-7.14-generic
  SourcePackage: linux
  Title: package linux-image-2.6.27-7-generic 2.6.27-7.14 failed to 
install/upgrade: impossibile creare il link per la copia di sicurezza di 
`./boot/vmlinuz-2.6.27-7-generic' prima di installarne la nuova versione: 
Funzione non permessa

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

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

[Kernel-packages] [Bug 1705592] 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/1705592

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

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Several packages have failed installing lately. Should be checked
  better before they are made public.

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-28-generic (not installed)
  ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15
  Uname: Linux 4.10.0-22-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  rasmus 1996 F pulseaudio
  Date: Fri Jul 21 01:17:26 2017
  ErrorMessage: subprocess new pre-installation script returned error exit 
status 128
  HibernationDevice: RESUME=UUID=af7e72c8-6005-404a-bef3-9630b22b6bb6
  InstallationDate: Installed on 2016-06-24 (391 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 3570R/370R/470R/450R/510R/4450RV
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-22-generic.efi.signed 
root=UUID=53e647d1-9a1f-49e3-b64d-66c1cb9bfa34 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 N/A
  SourcePackage: linux
  Title: package linux-image-4.10.0-28-generic (not installed) failed to 
install/upgrade: subprocess new pre-installation script returned error exit 
status 128
  UpgradeStatus: Upgraded to zesty on 2017-05-05 (76 days ago)
  dmi.bios.date: 04/29/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P15RAN.208.140429.ZW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: NP370R5E-S08SE
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: SEC_SW_REVISION_1234567890ABCD
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP15RAN.208.140429.ZW:bd04/29/2014:svnSAMSUNGELECTRONICSCO.,LTD.:pn3570R/370R/470R/450R/510R/4450RV:pvrP15RAN:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP370R5E-S08SE:rvrSEC_SW_REVISION_1234567890ABCD:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvrN/A:
  dmi.product.name: 3570R/370R/470R/450R/510R/4450RV
  dmi.product.version: P15RAN
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

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

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

[Kernel-packages] [Bug 1705592] Re: package linux-image-4.10.0-28-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 128

2017-07-20 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/1705592

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

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Several packages have failed installing lately. Should be checked
  better before they are made public.

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-28-generic (not installed)
  ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15
  Uname: Linux 4.10.0-22-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  rasmus 1996 F pulseaudio
  Date: Fri Jul 21 01:17:26 2017
  ErrorMessage: subprocess new pre-installation script returned error exit 
status 128
  HibernationDevice: RESUME=UUID=af7e72c8-6005-404a-bef3-9630b22b6bb6
  InstallationDate: Installed on 2016-06-24 (391 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 3570R/370R/470R/450R/510R/4450RV
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-22-generic.efi.signed 
root=UUID=53e647d1-9a1f-49e3-b64d-66c1cb9bfa34 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 N/A
  SourcePackage: linux
  Title: package linux-image-4.10.0-28-generic (not installed) failed to 
install/upgrade: subprocess new pre-installation script returned error exit 
status 128
  UpgradeStatus: Upgraded to zesty on 2017-05-05 (76 days ago)
  dmi.bios.date: 04/29/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P15RAN.208.140429.ZW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: NP370R5E-S08SE
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: SEC_SW_REVISION_1234567890ABCD
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP15RAN.208.140429.ZW:bd04/29/2014:svnSAMSUNGELECTRONICSCO.,LTD.:pn3570R/370R/470R/450R/510R/4450RV:pvrP15RAN:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP370R5E-S08SE:rvrSEC_SW_REVISION_1234567890ABCD:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvrN/A:
  dmi.product.name: 3570R/370R/470R/450R/510R/4450RV
  dmi.product.version: P15RAN
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

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

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

[Kernel-packages] [Bug 1705592] [NEW] package linux-image-4.10.0-28-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 128

2017-07-20 Thread Rasmus Arild Djuve

Public bug reported:

Several packages have failed installing lately. Should be checked better
before they are made public.

ProblemType: Package
DistroRelease: Ubuntu 17.04
Package: linux-image-4.10.0-28-generic (not installed)
ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15
Uname: Linux 4.10.0-22-generic x86_64
ApportVersion: 2.20.4-0ubuntu4.5
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  rasmus 1996 F pulseaudio
Date: Fri Jul 21 01:17:26 2017
ErrorMessage: subprocess new pre-installation script returned error exit status 
128
HibernationDevice: RESUME=UUID=af7e72c8-6005-404a-bef3-9630b22b6bb6
InstallationDate: Installed on 2016-06-24 (391 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
MachineType: SAMSUNG ELECTRONICS CO., LTD. 3570R/370R/470R/450R/510R/4450RV
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-22-generic.efi.signed 
root=UUID=53e647d1-9a1f-49e3-b64d-66c1cb9bfa34 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 N/A
SourcePackage: linux
Title: package linux-image-4.10.0-28-generic (not installed) failed to 
install/upgrade: subprocess new pre-installation script returned error exit 
status 128
UpgradeStatus: Upgraded to zesty on 2017-05-05 (76 days ago)
dmi.bios.date: 04/29/2014
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P15RAN.208.140429.ZW
dmi.board.asset.tag: No Asset Tag
dmi.board.name: NP370R5E-S08SE
dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.board.version: SEC_SW_REVISION_1234567890ABCD
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 9
dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.chassis.version: N/A
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP15RAN.208.140429.ZW:bd04/29/2014:svnSAMSUNGELECTRONICSCO.,LTD.:pn3570R/370R/470R/450R/510R/4450RV:pvrP15RAN:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP370R5E-S08SE:rvrSEC_SW_REVISION_1234567890ABCD:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvrN/A:
dmi.product.name: 3570R/370R/470R/450R/510R/4450RV
dmi.product.version: P15RAN
dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

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


** Tags: amd64 apport-package zesty

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

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

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Several packages have failed installing lately. Should be checked
  better before they are made public.

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-28-generic (not installed)
  ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15
  Uname: Linux 4.10.0-22-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  rasmus 1996 F pulseaudio
  Date: Fri Jul 21 01:17:26 2017
  ErrorMessage: subprocess new pre-installation script returned error exit 
status 128
  HibernationDevice: RESUME=UUID=af7e72c8-6005-404a-bef3-9630b22b6bb6
  InstallationDate: Installed on 2016-06-24 (391 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 3570R/370R/470R/450R/510R/4450RV
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-22-generic.efi.signed 
root=UUID=53e647d1-9a1f-49e3-b64d-66c1cb9bfa34 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 N/A
  SourcePackage: linux
  Title: package linux-image-4.10.0-28-generic (not installed) failed to 
install/upgrade: subprocess new pre-installation script returned error exit 
status 128
  UpgradeStatus: Upgraded to zesty on 2017-05-05 (76 days ago)
  dmi.bios.date: 04/29/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P15RAN.208.140429.ZW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: NP370R5E-S08SE
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: SEC_SW_REVISION_1234567890ABCD
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP15RAN.208.140429.ZW:bd04/29/2014:svnSAMSUNGELECTRONICSCO.,LTD.:pn3570R/370R/470R/450R/510R/4450RV:pvrP15RAN:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP370R5E-S08SE:rvrSEC_SW_REVISION_1234567890ABCD:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvrN/A:

[Kernel-packages] [Bug 1705586] 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 1705586

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

Title:
  Mute key LED does not work on HP ProBook 440

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  this is probably a duplicate of
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1683277, but I
  was asked to file a new bug.

  The mute button on my laptop has a led that changes the color based on
  the status of the audio-master channel. At least it should.

  There is a slider for the LED in alsamixer but it doesn't change
  anything.

  Are there any tests I should run?

  cat /proc/version_signature > Ubuntu 4.10.0-28.32-generic 4.10.17

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

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

[Kernel-packages] [Bug 1705586] [NEW] Mute key LED does not work on HP ProBook 440

2017-07-20 Thread Benjamin Halbrock

Public bug reported:

this is probably a duplicate of
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1683277, but I was
asked to file a new bug.

The mute button on my laptop has a led that changes the color based on
the status of the audio-master channel. At least it should.

There is a slider for the LED in alsamixer but it doesn't change
anything.

Are there any tests I should run?

cat /proc/version_signature > Ubuntu 4.10.0-28.32-generic 4.10.17

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

** Attachment added: "lspci-vnvn.log"
   
https://bugs.launchpad.net/bugs/1705586/+attachment/4918479/+files/lspci-vnvn.log

** Description changed:

  this is probably a duplicate of
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1683277, but I was
  asked to file a new bug.
  
- The mute button on my laptop has a led, that changes the color based on
+ The mute button on my laptop has a led that changes the color based on
  the status of the audio-master channel. At least it should.
  
  There is a slider for the LED in alsamixer but it doesn't change
  anything.
  
  Are there any tests I should run?
  
- 
  cat /proc/version_signature > Ubuntu 4.10.0-28.32-generic 4.10.17

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

Title:
  Mute key LED does not work on HP ProBook 440

Status in linux package in Ubuntu:
  New

Bug description:
  this is probably a duplicate of
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1683277, but I
  was asked to file a new bug.

  The mute button on my laptop has a led that changes the color based on
  the status of the audio-master channel. At least it should.

  There is a slider for the LED in alsamixer but it doesn't change
  anything.

  Are there any tests I should run?

  cat /proc/version_signature > Ubuntu 4.10.0-28.32-generic 4.10.17

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

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

[Kernel-packages] [Bug 1705507] Re: linux-aws: 4.4.0-1026.35 -proposed tracker

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

** Tags added: block-proposed

** Description changed:

  This bug is for tracking the 4.4.0-1026.35 upload package. This bug will
  contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
+ boot-testing-requested: true
  phase: Uploaded

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

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

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

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

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

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

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

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

[Kernel-packages] [Bug 1698616] Re: 4.10.0-22 No longer suspends on Dell XPS 9560

2017-07-20 Thread David Kowis

> I guess it's pretty similar to LP: #1697556. Try blacklisting nouveau.

Good guess, it is indeed. Blacklisting nouveau and things suspend just
fine.

of note, I'm using the intel graphics adaptor exclusively, and don't
even have the nvidia drivers installed at the moment.

But this gets me to an up-to-date (at least with ubuntu) kernel! 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/1698616

Title:
  4.10.0-22 No longer suspends on Dell XPS 9560

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have to roll back to -21 to be able to suspend.

  Linux XPS 4.10.0-21-lowlatency #23~16.04.1-Ubuntu SMP PREEMPT Tue May
  2 14:25:44 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux

  With -22, it doesn't suspend, and has lots of trouble with it.

  I expect to be able to suspend when I close the laptop lid, or when I
  go to suspend from the power menu. Instead the OS acts like it
  suspends, but the laptop doesn't power down anything. The display
  remains on, the fans continue to spin. It acts like it has, because it
  takes a bit for the keyboard to respond, and the mouse to move again,
  and the wifi was disconnected. It's just that the hardware doesn't
  power down at all.

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

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

[Kernel-packages] [Bug 1702749] Re: arm64: fix crash reading /proc/kcore

2017-07-20 Thread dann frazier

Preemptive verification:

root@d05-3:~# cat /proc/version
Linux version 4.10.0-29-generic (buildd@bos01-arm64-012) (gcc version 6.3.0 
20170406 (Ubuntu/Linaro 6.3.0-12ubuntu2) ) #33-Ubuntu SMP Wed Jul 19 13:37:12 
UTC 2017
root@d05-3:~# cat /proc/kcore > /dev/null&
[1] 9206
root@d05-3:~# 

(/proc/kcore is 133T on this system, so it won't complete in any
reasonable time - but normally would've crashed by now).

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

Title:
  arm64: fix crash reading /proc/kcore

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

Bug description:
  [Impact]
  Reading /proc/kcore can lead to a crash on arm64 systems.
  This was found to cause crashes when, e.g. annotating symbols in a perf top 
session.

  [Test Case]
  # cat /proc/kcore > /dev/null

  [Regression Risk]
  2 upstream patches need to be cherry-picked to fix this. 

  The 1st patch is a simplification to the kcore driver that impacts all
  architectures. Instead of re-checking at read time for vmalloc/module
  addresses, it just checks for a flag that was set during kcore driver
  init. This looks correct to me but could of course have an unnoticed
  bug.

  The second patch is arm64-specific, and regression risk has been
  mitigated by testing on arm64 hardware.

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

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

[Kernel-packages] [Bug 1705507] Re: linux-aws: 4.4.0-1026.35 -proposed tracker

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

** Changed in: kernel-sru-workflow/prepare-package-meta
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Thadeu Lima de 
Souza Cascardo (cascardo)

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

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

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

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

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

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

[Kernel-packages] [Bug 1704146] Re: hns: under heavy load, NIC may fail and require reboot

2017-07-20 Thread dann frazier

Preemptive verification:

dannf@xps13:~$ ssh 10.XXX.XXX.XXX cat /proc/version
Warning: Permanently added '10.XXX.XXX.XXX' (ECDSA) to the list of known hosts.
Linux version 4.10.0-29-generic (buildd@bos01-arm64-012) (gcc version 6.3.0 
20170406 (Ubuntu/Linaro 6.3.0-12ubuntu2) ) #33-Ubuntu SMP Wed Jul 19 13:37:12 
UTC 2017

(The 10.XXX.XXX.XXX IP is on an hns NIC on a D05 system)

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

Title:
  hns: under heavy load, NIC may fail and require reboot

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

Bug description:
  [Impact]
  The onboard NIC on HiSilicon D05 boards can fail under heavy load, requiring 
a reboot to recover.

  [Test Case]
  There isn't a known reliable reproducer.

  [Regression Risk]
  This is a driver-specific fix, so regression risk is limited to devices that 
we can directly test.

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

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

[Kernel-packages] [Bug 1705584] Re: package bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu8 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before atte

2017-07-20 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 bcmwl in Ubuntu.
https://bugs.launchpad.net/bugs/1705584

Title:
  package bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu8 failed to
  install/upgrade: package is in a very bad inconsistent state; you
  should  reinstall it before attempting configuration

Status in bcmwl package in Ubuntu:
  New

Bug description:
  16.04

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu8
  ProcVersionSignature: Ubuntu 4.4.0-83.106-generic 4.4.70
  Uname: Linux 4.4.0-83-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  Date: Thu Jul 20 23:57:22 2017
  DuplicateSignature:
   package:bcmwl-kernel-source:6.30.223.248+bdcom-0ubuntu8
   Processing triggers for gconf2 (3.2.6-3ubuntu6) ...
   dpkg: error processing package bcmwl-kernel-source (--configure):
package is in a very bad inconsistent state; you should
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2016-08-31 (323 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: bcmwl
  Title: package bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu8 failed to 
install/upgrade: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  UpgradeStatus: Upgraded to xenial on 2016-09-02 (321 days ago)

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

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

[Kernel-packages] [Bug 1682410] Re: ecryptfs-utils not working properly with linux kernel 4.8.0-41-generic

2017-07-20 Thread Redsandro

Latest I tried was linux 4.10.0-26.30 through the hwe-edge package.
ecryptfs still didn't mount properly.

I switched back to 4.4.0. Ecryptfs works fine again.

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

Title:
  ecryptfs-utils not working properly with linux kernel 4.8.0-41-generic

Status in linux package in Ubuntu:
  Expired

Bug description:
  I have two systems that have a Dropbox folder synced. One of the
  subfolders contains sensitive data encrypted using ecryptfs. Both were
  running linux kernel 4.4.0-53-generic.

  I have since upgraded one system to use linux kernel 4.8.0-41-generic.
  Now, the decrypted directory can no longer see groups and owners or
  read files. All permissions are replaced by questionmarks.

  4.8.0-41-generic

  $ ll
  ls: cannot access 'Contracts': No such file or directory
  ls: cannot access 'Documents': No such file or directory
  ls: cannot access 'Work': No such file or directory
  total 12K
  drwxr-x--- 5 redsandro redsandro 4.0K Mar 31 15:54 ./
  drwxr-xr-x 7 redsandro redsandro 4.0K Apr 13 13:24 ../
  d? ? ?  ? ?? Contracts/
  d? ? ?  ? ?? Documents/
  d? ? ?  ? ?? Work/

  The other machine still works fine.

  4.4.0-53-generic:

  $ ll
  total 56K
  drwxr-x---  5 redsandro redsandro  12K Apr  4 16:11 ./
  drwxr-xr-x  8 redsandro redsandro 4.0K Oct 18 13:25 ../
  drwxr-xr-x  3 redsandro redsandro 4.0K Nov  2 18:50 Contracts/
  drwxr-xr-x 11 redsandro redsandro 4.0K Mar  9 17:03 Documents/
  drwxr-xr-x  3 redsandro redsandro 4.0K Mar  4  2013 Work/

  For both machines:
  $ apt version ecryptfs-utils 
  111-0ubuntu1.1

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

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

[Kernel-packages] [Bug 1705584] [NEW] package bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu8 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before at

2017-07-20 Thread Francisco Blazquez

Public bug reported:

16.04

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu8
ProcVersionSignature: Ubuntu 4.4.0-83.106-generic 4.4.70
Uname: Linux 4.4.0-83-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: amd64
Date: Thu Jul 20 23:57:22 2017
DuplicateSignature:
 package:bcmwl-kernel-source:6.30.223.248+bdcom-0ubuntu8
 Processing triggers for gconf2 (3.2.6-3ubuntu6) ...
 dpkg: error processing package bcmwl-kernel-source (--configure):
  package is in a very bad inconsistent state; you should
ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
InstallationDate: Installed on 2016-08-31 (323 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.2
 apt  1.2.20
SourcePackage: bcmwl
Title: package bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu8 failed to 
install/upgrade: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
UpgradeStatus: Upgraded to xenial on 2016-09-02 (321 days ago)

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


** Tags: amd64 apport-package xenial

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

Title:
  package bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu8 failed to
  install/upgrade: package is in a very bad inconsistent state; you
  should  reinstall it before attempting configuration

Status in bcmwl package in Ubuntu:
  New

Bug description:
  16.04

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu8
  ProcVersionSignature: Ubuntu 4.4.0-83.106-generic 4.4.70
  Uname: Linux 4.4.0-83-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  Date: Thu Jul 20 23:57:22 2017
  DuplicateSignature:
   package:bcmwl-kernel-source:6.30.223.248+bdcom-0ubuntu8
   Processing triggers for gconf2 (3.2.6-3ubuntu6) ...
   dpkg: error processing package bcmwl-kernel-source (--configure):
package is in a very bad inconsistent state; you should
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2016-08-31 (323 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: bcmwl
  Title: package bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu8 failed to 
install/upgrade: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  UpgradeStatus: Upgraded to xenial on 2016-09-02 (321 days ago)

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

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

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

--- Comment From drbr...@us.ibm.com 2017-07-20 17:52 EDT---
Canonical please clarify. I was on a call with Andrew Cloke earlier today. He 
said this could be done but not done in time for 17.10 GA in October. It would 
happen after 17.10 GA.

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

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

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

Bug description:
  Feature Description:

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

  
  Business Case: 

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

  Use Case:

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

  
  Test Case:

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

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

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

[Kernel-packages] [Bug 1679768] 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 1679768

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

Title:
  Docker build hangs on XFS with kernel 4.10

Status in docker.io package in Ubuntu:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I have my docker partition on XFS, and recently upgraded to Zesty Beta.
  Most of my `docker build.` processes hangs with a similar message in syslog:

  ```
  Apr  4 09:19:04 epuspdxn0004 kernel: [ 1330.171267] INFO: task 
kworker/1:3:5589 blocked for more than 120 seconds.
  Apr  4 09:19:04 epuspdxn0004 kernel: [ 1330.171275]   Tainted: P  
 O4.10.0-15-generic #17-Ubuntu
  Apr  4 09:19:04 epuspdxn0004 kernel: [ 1330.171278] "echo 0 > 
/proc/sys/kernel/hung_task_timeout_secs" disables this message.
  Apr  4 09:19:04 epuspdxn0004 kernel: [ 1330.171282] kworker/1:3 D0  
5589  2 0x
  Apr  4 09:19:04 epuspdxn0004 kernel: [ 1330.171310] Workqueue: aufsd wkq_func 
[aufs]
  Apr  4 09:19:04 epuspdxn0004 kernel: [ 1330.171313] Call Trace:
  Apr  4 09:19:04 epuspdxn0004 kernel: [ 1330.171323]  __schedule+0x233/0x6f0
  Apr  4 09:19:04 epuspdxn0004 kernel: [ 1330.171415]  ? 
kmem_zone_alloc+0x81/0x120 [xfs]
  Apr  4 09:19:04 epuspdxn0004 kernel: [ 1330.171419]  schedule+0x36/0x80
  Apr  4 09:19:04 epuspdxn0004 kernel: [ 1330.171423]  
rwsem_down_read_failed+0xfa/0x150
  Apr  4 09:19:04 epuspdxn0004 kernel: [ 1330.171491]  ? 
xfs_file_buffered_aio_read+0x3d/0xc0 [xfs]
  Apr  4 09:19:04 epuspdxn0004 kernel: [ 1330.171496]  
call_rwsem_down_read_failed+0x18/0x30
  Apr  4 09:19:04 epuspdxn0004 kernel: [ 1330.171500]  down_read+0x20/0x40
  Apr  4 09:19:04 epuspdxn0004 kernel: [ 1330.171567]  xfs_ilock+0xf5/0x110 
[xfs]
  Apr  4 09:19:04 epuspdxn0004 kernel: [ 1330.171628]  
xfs_file_buffered_aio_read+0x3d/0xc0 [xfs]
  Apr  4 09:19:04 epuspdxn0004 kernel: [ 1330.171686]  
xfs_file_read_iter+0x68/0xc0 [xfs]
  Apr  4 09:19:04 epuspdxn0004 kernel: [ 1330.171692]  new_sync_read+0xd2/0x120
  Apr  4 09:19:04 epuspdxn0004 kernel: [ 1330.171695]  __vfs_read+0x26/0x40
  Apr  4 09:19:04 epuspdxn0004 kernel: [ 1330.171697]  vfs_read+0x96/0x130
  Apr  4 09:19:04 epuspdxn0004 kernel: [ 1330.171715]  vfsub_read_u+0x14/0x30 
[aufs]
  Apr  4 09:19:04 epuspdxn0004 kernel: [ 1330.171729]  vfsub_read_k+0x2c/0x40 
[aufs]
  Apr  4 09:19:04 epuspdxn0004 kernel: [ 1330.171743]  au_copy_file+0x10c/0x370 
[aufs]
  Apr  4 09:19:04 epuspdxn0004 kernel: [ 1330.171756]  
au_cp_regular+0x11a/0x200 [aufs]
  Apr  4 09:19:04 epuspdxn0004 kernel: [ 1330.171767]  ? 
au_cp_regular+0x1ef/0x200 [aufs]
  Apr  4 09:19:04 epuspdxn0004 kernel: [ 1330.171777]  ? 
au_cp_regular+0x188/0x200 [aufs]
  Apr  4 09:19:04 epuspdxn0004 kernel: [ 1330.171788]  cpup_entry+0x538/0x5f0 
[aufs]
  Apr  4 09:19:04 epuspdxn0004 kernel: [ 1330.171802]  ? 
vfsub_lookup_one_len+0x31/0x70 [aufs]
  Apr  4 09:19:04 epuspdxn0004 kernel: [ 1330.171814]  
au_cpup_single.constprop.18+0x145/0x6a0 [aufs]
  Apr  4 09:19:04 epuspdxn0004 kernel: [ 1330.171820]  ? dput+0x40/0x270
  Apr  4 09:19:04 epuspdxn0004 kernel: [ 1330.171831]  au_cpup_simple+0x4d/0x80 
[aufs]
  Apr  4 09:19:04 epuspdxn0004 kernel: [ 1330.171842]  
au_call_cpup_simple+0x28/0x40 [aufs]
  Apr  4 09:19:04 epuspdxn0004 kernel: [ 1330.171855]  wkq_func+0x14/0x80 [aufs]
  Apr  4 09:19:04 epuspdxn0004 kernel: [ 1330.171861]  
process_one_work+0x1fc/0x4b0
  Apr  4 09:19:04 epuspdxn0004 kernel: [ 1330.171864]  worker_thread+0x4b/0x500
  Apr  4 09:19:04 epuspdxn0004 kernel: [ 1330.171870]  kthread+0x101/0x140
  Apr  4 09:19:04 epuspdxn0004 kernel: [ 1330.171873]  ? 
process_one_work+0x4b0/0x4b0
  Apr  4 09:19:04 epuspdxn0004 kernel: [ 1330.171878]  ? 
kthread_create_on_node+0x60/0x60
  Apr  4 09:19:04 epuspdxn0004 kernel: [ 1330.171883]  ? 
SyS_exit_group+0x14/0x20
  Apr  4 09:19:04 epuspdxn0004 kernel: [ 1330.171887]  ret_from_fork+0x2c/0x40
  Apr  4 09:19:04 epuspdxn0004 kernel: [ 1330.171895] INFO: task useradd:5758 
blocked for more than 120 seconds.
  Apr  4 09:19:04 epuspdxn0004 kernel: [ 1330.171899]   Tainted: P  
 O4.10.0-15-generic #17-Ubuntu
  ```

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1679768/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to :

[Kernel-packages] [Bug 1705507] Re: linux-aws: 4.4.0-1026.35 -proposed tracker

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

** Changed in: kernel-sru-workflow/prepare-package
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Thadeu Lima de 
Souza Cascardo (cascardo)

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

** Description changed:

  This bug is for tracking the 4.4.0-1026.35 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
  
- kernel-stable-phase-changed:Thursday, 20. July 2017 15:31 UTC
- kernel-stable-phase:Packaging
- 
  -- swm properties --
  phase: Packaging
+ kernel-stable-phase-changed:Thursday, 20. July 2017 22:00 UTC
+ kernel-stable-phase:Uploaded

** Description changed:

  This bug is for tracking the 4.4.0-1026.35 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: Packaging
- kernel-stable-phase-changed:Thursday, 20. July 2017 22:00 UTC
- kernel-stable-phase:Uploaded
+ phase: Uploaded

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

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

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

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

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

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

[Kernel-packages] [Bug 1705581] Re: Kernel Panic - using cgroups

2017-07-20 Thread John Fanjoy

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

** This bug has been marked a duplicate of bug 1702164
   Kernel panic - not syncing: Fatal exception in interrupt

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

Title:
  Kernel Panic - using cgroups

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Running the latest kernel at the time of this writing (4.4.0-83) we
  are experiencing frequent kernel panics across several hosts in our
  mesos cluster. At first glance this looks as though it may be related
  to a previous bug which was mentioned in 4.4.0-70 (LP #1687512).
  Another issue is currently open with high priority (LP #1702164) which
  seems to suggest that the kernel panics seen prior to the 4.4.0-79 may
  have resurfaced in the latest revision (4.4.0-83).

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-83-generic 4.4.0-83.106
  ProcVersionSignature: Ubuntu 4.4.0-83.106-generic 4.4.70
  Uname: Linux 4.4.0-83-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jul 19 01:31 seq
   crw-rw 1 root audio 116, 33 Jul 19 01:31 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Date: Wed Jul 19 17:31:08 2017
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  MachineType: Dell Inc. PowerEdge R430
  PciMultimedia:
   
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-83-generic 
root=/dev/mapper/vg01-root ro cgroup_enable=memory swapaccount=1 
crashkernel=384M-:128M
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-83-generic N/A
   linux-backports-modules-4.4.0-83-generic  N/A
   linux-firmware1.157.11
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/08/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.3.4
  dmi.board.name: 0CN7X8
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A04
  dmi.chassis.type: 23
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.3.4:bd11/08/2016:svnDellInc.:pnPowerEdgeR430:pvr:rvnDellInc.:rn0CN7X8:rvrA04:cvnDellInc.:ct23:cvr:
  dmi.product.name: PowerEdge R430
  dmi.sys.vendor: Dell Inc.

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

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

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

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

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

Title:
  Kernel Panic - using cgroups

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Running the latest kernel at the time of this writing (4.4.0-83) we
  are experiencing frequent kernel panics across several hosts in our
  mesos cluster. At first glance this looks as though it may be related
  to a previous bug which was mentioned in 4.4.0-70 (LP #1687512).
  Another issue is currently open with high priority (LP #1702164) which
  seems to suggest that the kernel panics seen prior to the 4.4.0-79 may
  have resurfaced in the latest revision (4.4.0-83).

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-83-generic 4.4.0-83.106
  ProcVersionSignature: Ubuntu 4.4.0-83.106-generic 4.4.70
  Uname: Linux 4.4.0-83-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jul 19 01:31 seq
   crw-rw 1 root audio 116, 33 Jul 19 01:31 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Date: Wed Jul 19 17:31:08 2017
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  MachineType: Dell Inc. PowerEdge R430
  PciMultimedia:
   
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-83-generic 
root=/dev/mapper/vg01-root ro cgroup_enable=memory swapaccount=1 
crashkernel=384M-:128M
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-83-generic N/A
   linux-backports-modules-4.4.0-83-generic  N/A
   linux-firmware1.157.11
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/08/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.3.4
  dmi.board.name: 0CN7X8
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A04
  dmi.chassis.type: 23
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.3.4:bd11/08/2016:svnDellInc.:pnPowerEdgeR430:pvr:rvnDellInc.:rn0CN7X8:rvrA04:cvnDellInc.:ct23:cvr:
  dmi.product.name: PowerEdge R430
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1705581] [NEW] Kernel Panic - using cgroups

2017-07-20 Thread John Fanjoy

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

Public bug reported:

Running the latest kernel at the time of this writing (4.4.0-83) we are
experiencing frequent kernel panics across several hosts in our mesos
cluster. At first glance this looks as though it may be related to a
previous bug which was mentioned in 4.4.0-70 (LP #1687512). Another
issue is currently open with high priority (LP #1702164) which seems to
suggest that the kernel panics seen prior to the 4.4.0-79 may have
resurfaced in the latest revision (4.4.0-83).

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-83-generic 4.4.0-83.106
ProcVersionSignature: Ubuntu 4.4.0-83.106-generic 4.4.70
Uname: Linux 4.4.0-83-generic x86_64
NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
AlsaDevices:
 total 0
 crw-rw 1 root audio 116,  1 Jul 19 01:31 seq
 crw-rw 1 root audio 116, 33 Jul 19 01:31 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
ApportVersion: 2.20.1-0ubuntu2.6
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
Date: Wed Jul 19 17:31:08 2017
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
MachineType: Dell Inc. PowerEdge R430
PciMultimedia:
 
ProcFB: 0 VESA VGA
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-83-generic 
root=/dev/mapper/vg01-root ro cgroup_enable=memory swapaccount=1 
crashkernel=384M-:128M
RelatedPackageVersions:
 linux-restricted-modules-4.4.0-83-generic N/A
 linux-backports-modules-4.4.0-83-generic  N/A
 linux-firmware1.157.11
RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/08/2016
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 2.3.4
dmi.board.name: 0CN7X8
dmi.board.vendor: Dell Inc.
dmi.board.version: A04
dmi.chassis.type: 23
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr2.3.4:bd11/08/2016:svnDellInc.:pnPowerEdgeR430:pvr:rvnDellInc.:rn0CN7X8:rvrA04:cvnDellInc.:ct23:cvr:
dmi.product.name: PowerEdge R430
dmi.sys.vendor: Dell Inc.

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


** Tags: amd64 apport-bug 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/1705581

Title:
  Kernel Panic - using cgroups

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Running the latest kernel at the time of this writing (4.4.0-83) we
  are experiencing frequent kernel panics across several hosts in our
  mesos cluster. At first glance this looks as though it may be related
  to a previous bug which was mentioned in 4.4.0-70 (LP #1687512).
  Another issue is currently open with high priority (LP #1702164) which
  seems to suggest that the kernel panics seen prior to the 4.4.0-79 may
  have resurfaced in the latest revision (4.4.0-83).

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-83-generic 4.4.0-83.106
  ProcVersionSignature: Ubuntu 4.4.0-83.106-generic 4.4.70
  Uname: Linux 4.4.0-83-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jul 19 01:31 seq
   crw-rw 1 root audio 116, 33 Jul 19 01:31 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Date: Wed Jul 19 17:31:08 2017
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  MachineType: Dell Inc. PowerEdge R430
  PciMultimedia:
   
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-83-generic 
root=/dev/mapper/vg01-root ro cgroup_enable=memory swapaccount=1 
crashkernel=384M-:128M
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-83-generic N/A
   linux-backports-modules-4.4.0-83-generic  N/A
   linux-firmware1.157.11
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/08/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.3.4
  dmi.board.name: 0CN7X8
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A04
  dmi.chassis.type: 23
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.3.4:bd11/08/2016:svnDellInc.:pnPowerEdgeR430:pvr:rvnDellInc.:rn0CN7X8:rvrA04:cvnDellInc.:ct23:cvr:
  dmi.product.name: PowerEdge R430
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:

[Kernel-packages] [Bug 1679768] Re: Docker build hangs on XFS with kernel 4.10

2017-07-20 Thread Brian Moyles

Seeing the same on Xenial when using linux-hwe-edge

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

Title:
  Docker build hangs on XFS with kernel 4.10

Status in docker.io package in Ubuntu:
  Incomplete
Status in linux package in Ubuntu:
  New

Bug description:
  I have my docker partition on XFS, and recently upgraded to Zesty Beta.
  Most of my `docker build.` processes hangs with a similar message in syslog:

  ```
  Apr  4 09:19:04 epuspdxn0004 kernel: [ 1330.171267] INFO: task 
kworker/1:3:5589 blocked for more than 120 seconds.
  Apr  4 09:19:04 epuspdxn0004 kernel: [ 1330.171275]   Tainted: P  
 O4.10.0-15-generic #17-Ubuntu
  Apr  4 09:19:04 epuspdxn0004 kernel: [ 1330.171278] "echo 0 > 
/proc/sys/kernel/hung_task_timeout_secs" disables this message.
  Apr  4 09:19:04 epuspdxn0004 kernel: [ 1330.171282] kworker/1:3 D0  
5589  2 0x
  Apr  4 09:19:04 epuspdxn0004 kernel: [ 1330.171310] Workqueue: aufsd wkq_func 
[aufs]
  Apr  4 09:19:04 epuspdxn0004 kernel: [ 1330.171313] Call Trace:
  Apr  4 09:19:04 epuspdxn0004 kernel: [ 1330.171323]  __schedule+0x233/0x6f0
  Apr  4 09:19:04 epuspdxn0004 kernel: [ 1330.171415]  ? 
kmem_zone_alloc+0x81/0x120 [xfs]
  Apr  4 09:19:04 epuspdxn0004 kernel: [ 1330.171419]  schedule+0x36/0x80
  Apr  4 09:19:04 epuspdxn0004 kernel: [ 1330.171423]  
rwsem_down_read_failed+0xfa/0x150
  Apr  4 09:19:04 epuspdxn0004 kernel: [ 1330.171491]  ? 
xfs_file_buffered_aio_read+0x3d/0xc0 [xfs]
  Apr  4 09:19:04 epuspdxn0004 kernel: [ 1330.171496]  
call_rwsem_down_read_failed+0x18/0x30
  Apr  4 09:19:04 epuspdxn0004 kernel: [ 1330.171500]  down_read+0x20/0x40
  Apr  4 09:19:04 epuspdxn0004 kernel: [ 1330.171567]  xfs_ilock+0xf5/0x110 
[xfs]
  Apr  4 09:19:04 epuspdxn0004 kernel: [ 1330.171628]  
xfs_file_buffered_aio_read+0x3d/0xc0 [xfs]
  Apr  4 09:19:04 epuspdxn0004 kernel: [ 1330.171686]  
xfs_file_read_iter+0x68/0xc0 [xfs]
  Apr  4 09:19:04 epuspdxn0004 kernel: [ 1330.171692]  new_sync_read+0xd2/0x120
  Apr  4 09:19:04 epuspdxn0004 kernel: [ 1330.171695]  __vfs_read+0x26/0x40
  Apr  4 09:19:04 epuspdxn0004 kernel: [ 1330.171697]  vfs_read+0x96/0x130
  Apr  4 09:19:04 epuspdxn0004 kernel: [ 1330.171715]  vfsub_read_u+0x14/0x30 
[aufs]
  Apr  4 09:19:04 epuspdxn0004 kernel: [ 1330.171729]  vfsub_read_k+0x2c/0x40 
[aufs]
  Apr  4 09:19:04 epuspdxn0004 kernel: [ 1330.171743]  au_copy_file+0x10c/0x370 
[aufs]
  Apr  4 09:19:04 epuspdxn0004 kernel: [ 1330.171756]  
au_cp_regular+0x11a/0x200 [aufs]
  Apr  4 09:19:04 epuspdxn0004 kernel: [ 1330.171767]  ? 
au_cp_regular+0x1ef/0x200 [aufs]
  Apr  4 09:19:04 epuspdxn0004 kernel: [ 1330.171777]  ? 
au_cp_regular+0x188/0x200 [aufs]
  Apr  4 09:19:04 epuspdxn0004 kernel: [ 1330.171788]  cpup_entry+0x538/0x5f0 
[aufs]
  Apr  4 09:19:04 epuspdxn0004 kernel: [ 1330.171802]  ? 
vfsub_lookup_one_len+0x31/0x70 [aufs]
  Apr  4 09:19:04 epuspdxn0004 kernel: [ 1330.171814]  
au_cpup_single.constprop.18+0x145/0x6a0 [aufs]
  Apr  4 09:19:04 epuspdxn0004 kernel: [ 1330.171820]  ? dput+0x40/0x270
  Apr  4 09:19:04 epuspdxn0004 kernel: [ 1330.171831]  au_cpup_simple+0x4d/0x80 
[aufs]
  Apr  4 09:19:04 epuspdxn0004 kernel: [ 1330.171842]  
au_call_cpup_simple+0x28/0x40 [aufs]
  Apr  4 09:19:04 epuspdxn0004 kernel: [ 1330.171855]  wkq_func+0x14/0x80 [aufs]
  Apr  4 09:19:04 epuspdxn0004 kernel: [ 1330.171861]  
process_one_work+0x1fc/0x4b0
  Apr  4 09:19:04 epuspdxn0004 kernel: [ 1330.171864]  worker_thread+0x4b/0x500
  Apr  4 09:19:04 epuspdxn0004 kernel: [ 1330.171870]  kthread+0x101/0x140
  Apr  4 09:19:04 epuspdxn0004 kernel: [ 1330.171873]  ? 
process_one_work+0x4b0/0x4b0
  Apr  4 09:19:04 epuspdxn0004 kernel: [ 1330.171878]  ? 
kthread_create_on_node+0x60/0x60
  Apr  4 09:19:04 epuspdxn0004 kernel: [ 1330.171883]  ? 
SyS_exit_group+0x14/0x20
  Apr  4 09:19:04 epuspdxn0004 kernel: [ 1330.171887]  ret_from_fork+0x2c/0x40
  Apr  4 09:19:04 epuspdxn0004 kernel: [ 1330.171895] INFO: task useradd:5758 
blocked for more than 120 seconds.
  Apr  4 09:19:04 epuspdxn0004 kernel: [ 1330.171899]   Tainted: P  
 O4.10.0-15-generic #17-Ubuntu
  ```

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1679768/+subscriptions

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

[Kernel-packages] [Bug 1694859] Re: arm64 kernel crashdump support

2017-07-20 Thread dann frazier

dannf@d05-3:~$ sudo apt install kdump-tools
Reading package lists... Done
Building dependency tree   
Reading state information... Done
The following additional packages will be installed:
  crash kexec-tools makedumpfile
The following NEW packages will be installed:
  crash kdump-tools kexec-tools makedumpfile
0 upgraded, 4 newly installed, 0 to remove and 0 not upgraded.
Need to get 2,291 kB of archives.
After this operation, 7,092 kB of additional disk space will be used.
Do you want to continue? [Y/n] 
Get:1 http://us.ports.ubuntu.com/ubuntu-ports xenial-updates/main arm64 crash 
arm64 7.1.4-1ubuntu4.1 [2,096 kB]
Get:2 http://us.ports.ubuntu.com/ubuntu-ports xenial-proposed/main arm64 
makedumpfile arm64 1:1.5.9-5ubuntu0.5 [111 kB]
Get:3 http://us.ports.ubuntu.com/ubuntu-ports xenial-proposed/main arm64 
kexec-tools arm64 1:2.0.10-1ubuntu2.3 [63.3 kB]
Get:4 http://us.ports.ubuntu.com/ubuntu-ports xenial-proposed/main arm64 
kdump-tools all 1:1.5.9-5ubuntu0.5 [20.9 kB]
Fetched 2,291 kB in 0s (21.4 MB/s)  
Preconfiguring packages ...
Selecting previously unselected package crash.
(Reading database ... 93733 files and directories currently installed.)
Preparing to unpack .../crash_7.1.4-1ubuntu4.1_arm64.deb ...
Unpacking crash (7.1.4-1ubuntu4.1) ...
Selecting previously unselected package makedumpfile.
Preparing to unpack .../makedumpfile_1%3a1.5.9-5ubuntu0.5_arm64.deb ...
Unpacking makedumpfile (1:1.5.9-5ubuntu0.5) ...
Selecting previously unselected package kexec-tools.
Preparing to unpack .../kexec-tools_1%3a2.0.10-1ubuntu2.3_arm64.deb ...
Unpacking kexec-tools (1:2.0.10-1ubuntu2.3) ...
Selecting previously unselected package kdump-tools.
Preparing to unpack .../kdump-tools_1%3a1.5.9-5ubuntu0.5_all.deb ...
Unpacking kdump-tools (1:1.5.9-5ubuntu0.5) ...
Processing triggers for man-db (2.7.5-1) ...
Processing triggers for systemd (229-4ubuntu19) ...
Processing triggers for ureadahead (0.100.0-19) ...
ureadahead will be reprofiled on next reboot
Setting up crash (7.1.4-1ubuntu4.1) ...
Setting up makedumpfile (1:1.5.9-5ubuntu0.5) ...
Setting up kexec-tools (1:2.0.10-1ubuntu2.3) ...
Generating /etc/default/kexec...
Generating grub configuration file ...
File descriptor 3 (pipe:[70529]) leaked on vgs invocation. Parent PID 23506: 
/usr/sbin/grub-probe
File descriptor 3 (pipe:[70529]) leaked on vgs invocation. Parent PID 23506: 
/usr/sbin/grub-probe
File descriptor 3 (pipe:[70529]) leaked on vgs invocation. Parent PID 23555: 
/usr/sbin/grub-probe
File descriptor 3 (pipe:[70529]) leaked on vgs invocation. Parent PID 23555: 
/usr/sbin/grub-probe
File descriptor 3 (pipe:[70529]) leaked on vgs invocation. Parent PID 23598: 
/usr/sbin/grub-probe
File descriptor 3 (pipe:[70529]) leaked on vgs invocation. Parent PID 23598: 
/usr/sbin/grub-probe
File descriptor 3 (pipe:[70529]) leaked on vgs invocation. Parent PID 23675: 
/usr/sbin/grub-probe
File descriptor 3 (pipe:[70529]) leaked on vgs invocation. Parent PID 23675: 
/usr/sbin/grub-probe
File descriptor 3 (pipe:[70529]) leaked on vgs invocation. Parent PID 23823: 
/usr/sbin/grub-probe
File descriptor 3 (pipe:[70529]) leaked on vgs invocation. Parent PID 23823: 
/usr/sbin/grub-probe
Found linux image: /boot/vmlinuz-4.10.0-27-generic
Found initrd image: /boot/initrd.img-4.10.0-27-generic
File descriptor 3 (pipe:[70529]) leaked on vgs invocation. Parent PID 24161: 
/usr/sbin/grub-probe
File descriptor 3 (pipe:[70529]) leaked on vgs invocation. Parent PID 24161: 
/usr/sbin/grub-probe
File descriptor 3 (pipe:[70529]) leaked on lvs invocation. Parent PID 24390: 
/bin/sh
Found Ubuntu 17.04 (17.04) on /dev/sda2
Adding boot menu entry for EFI firmware configuration
done
Setting up kdump-tools (1:1.5.9-5ubuntu0.5) ...
Processing triggers for systemd (229-4ubuntu19) ...
Processing triggers for ureadahead (0.100.0-19) ...
dannf@d05-3:~$

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

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

Title:
  arm64 kernel crashdump support

Status in kexec-tools package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in makedumpfile package in Ubuntu:
  Fix Released
Status in kexec-tools source package in Xenial:
  Fix Committed
Status in linux source package in Xenial:
  Won't Fix
Status in makedumpfile source package in Xenial:
  Fix Committed
Status in kexec-tools source package in Yakkety:
  In Progress
Status in linux source package in Yakkety:
  Won't Fix
Status in makedumpfile source package in Yakkety:
  Won't Fix
Status in kexec-tools source package in Zesty:
  Fix Committed
Status in linux source package in Zesty:
  Fix Released
Status in makedumpfile source package in Zesty:
  Fix Released

Bug description:
  Note: Updates are being staged at ppa:dannf/arm64-kdump.

  [Impact]
  It is not possible

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

--- Comment From dougm...@us.ibm.com 2017-07-20 17:03 EDT---
*** Bug 156883 has been marked as a duplicate of this bug. ***

--- Comment From dougm...@us.ibm.com 2017-07-20 17:04 EDT---
We need to have this patch also pulled into 4.4 kernels.

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

Title:
  OpenPower: Some multipaths temporarily have only a single path

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

Bug description:
  [Impact]

   * The SES driver causes a long delay in disk discovery when
     a large number of disks is present in the disk enclosure,
     which increases with the number of disks attached.

   * This delays the addition and visibility of the disk devices
     to userspace, which among other things causes multipath not
     to have multiple paths, actually, until the disk discovery
     eventually/finally finishes.

   * The fix significantly shortens the time taken by the SES
     driver to handle disk discovery, causing no extra delays,
     by removing a superfluous SCSI command sent to enclosure.

  [Test Case]

   * Load the module to access the enclosure and its disks; e.g.,

     $ sudo modprobe mpt3sas

   * Notice the interval between the discovery of each disk; e.g., dmesg

     $ dmesg -T | grep 'Attached SCSI disk' | tail -n2
     [Thu Jun 1 14:18:30 2017] sd 17:0:100:0: [sdcr] Attached SCSI disk
     [Thu Jun 1 14:18:35 2017] sd 17:0:101:0: [sdcs] Attached SCSI disk

   * The interval should be in the same second or so range with the fix.

     $ dmesg -T | grep 'Attached SCSI disk' | tail -n2
     [Wed Jun  7 13:11:59 2017] sd 18:0:176:0: [sdly] Attached SCSI disk
     [Wed Jun  7 13:11:59 2017] sd 18:0:175:0: [sdlx] Attached SCSI disk

  [Regression Potential]

   * The power status of the disks in the enclosure is no longer
     checked during probe time.  However, the patch demonstrates that
     initial value was never used in any way.  So, little regression
     potential.

   * Nonetheless, users of SES enclosures which verify the power status
     of disks in the enclosure might _theoretically_ see a problem, iff
     the fix has a problem (which has not been found yet).

  [Other Info]

   * None at this time.

  
  Problem Description:
  

  This week, I went ahead and scaled up my test configuration to max
  configuration 2x5U84_Enclosures,_MaxCfg_168HDDs. This time, it hit a
  different issue. The issue is that some multipaths only have a single
  path and no redundancy. Others have multiple paths and redundancy.

  Checkpoint #1:
  ==
  - system reboot around 2pm (14:00)

  Checkpoint # 2:
  ===
  - It took several minutes for first disk to be detected.

  
  root@smb1p1:~# multipath -ll|grep dm |wc -l
  103

  root@smb1p1:~# dmesg -T | grep 'sd 1[78]:' |  grep 'Attached SCSI disk' | tail
  [Thu Jun  1 14:18:30 2017] sd 17:0:100:0: [sdcr] Attached SCSI disk
  [Thu Jun  1 14:18:35 2017] sd 17:0:101:0: [sdcs] Attached SCSI disk
  [Thu Jun  1 14:18:40 2017] sd 17:0:102:0: [sdct] Attached SCSI disk
  [Thu Jun  1 14:18:44 2017] sd 17:0:103:0: [sdcu] Attached SCSI disk
  [Thu Jun  1 14:18:54 2017] sd 17:0:105:0: [sdcv] Attached SCSI disk
  [Thu Jun  1 14:18:59 2017] sd 17:0:106:0: [sdcw] Attached SCSI disk
  [Thu Jun  1 14:19:04 2017] sd 17:0:107:0: [sdcx] Attached SCSI disk
  [Thu Jun  1 14:19:09 2017] sd 17:0:108:0: [sdcy] Attached SCSI disk
  [Thu Jun  1 14:19:14 2017] sd 17:0:109:0: [sdcz] Attached SCSI disk
  [Thu Jun  1 14:19:19 2017] sd 17:0:110:0: [sdda] Attached SCSI disk
  root@smb1p1:~#

  ...

  root@smb1p1:~# multipath -ll|grep dm |wc -l
  142
  root@smb1p1:~# dmesg -T | grep 'sd 1[78]:' |  grep 'Attached SCSI disk' | tail
  [Thu Jun  1 14:21:54 2017] sd 17:0:141:0: [sdee] Attached SCSI disk
  [Thu Jun  1 14:21:58 2017] sd 17:0:142:0: [sdef] Attached SCSI disk
  [Thu Jun  1 14:22:04 2017] sd 17:0:143:0: [sdeg] Attached SCSI disk
  [Thu Jun  1 14:22:08 2017] sd 17:0:144:0: [sdeh] Attached SCSI disk
  [Thu Jun  1 14:22:14 2017] sd 17:0:145:0: [sdei] Attached SCSI disk
  [Thu Jun  1 14:22:18 2017] sd 17:0:146:0: [sdej] Attached SCSI disk
  [Thu Jun  1 14:22:24 2017] sd 17:0:147:0: [sdek] Attached SCSI disk
  [Thu Jun  1 14:22:29 2017] sd 17:0:148:0: [sdel] Attached SCSI disk
  [Thu Jun  1 14:22:34 2017] sd 17:0:149:0: [sdem] Attached SCSI disk
  [Thu Jun  1 14:22:39 2017] sd 17:0:150:0: [sden] Attached SCSI disk
  root@smb1p1:~#

  
  ...

  - After 43  minutes, multipath -ll command shows some paths with only
  single path and no redundancy and some path with multiple paths and
  redundancy.

  root@smb1p1:~# date
  Thu Jun  1 14:43:00 CDT 2017
  root@smb1p1:~# multipath -ll | grep -c 'sd[a-z]\+'
  252

[Kernel-packages] [Bug 1700026] Re: [17.10 FEAT]: Update kernel .config for POWER8

Closing fix released since artful is now using 4.11 with the specified
setting.

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

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

Title:
  [17.10 FEAT]: Update kernel .config for POWER8

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

Bug description:
  == Comment: #0 - Breno Leitao  - 2017-06-19 13:06:06 ==
  Dear Canonical,

  Currently 17.10 kernel is built using POWER7 instructions. It is time
  to change for POWER8, could you please change CONFIG_POWER7_CPU=n and
  CONFIG_POWER8_CPU=y

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

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

[Kernel-packages] [Bug 1693369] Re: 5U84 - ses driver isn't binding right - cannot blink lights on 1 of the 2 5u84

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

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

Title:
  5U84 - ses driver isn't binding right - cannot blink lights on 1 of
  the 2 5u84

Status in The Ubuntu-power-systems project:
  New
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Xenial:
  In Progress
Status in linux source package in Yakkety:
  Won't Fix
Status in linux source package in Zesty:
  In Progress

Bug description:
  This is a request to add the following upstream commit to both Ubuntu
  16.04.1 and 16.04.2:

  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/scsi/ses.c?id=9373eba6cfae48911b977d14323032cd5d161aae

  Without this patch, the symlink in sysfs which binds a SAS device to
  an enclosure slot does not get created. This makes disk hotplug near
  impossible on large JBOD disk drawers.

  You should be able to do:

  ls /sys/block/sdb/device/ | grep enclosure

  and see something like:

  enclosure_device:1

  If you cd to this directory, you can then access the SES controls for
  that slot to flash the LED to assist in locating the disk to replace a
  failed disk.

  Currently with 16.04.1 and 16.04.2, these symlinks are not getting
  created.

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

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

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

--- Comment From dougm...@us.ibm.com 2017-07-20 16:05 EDT---
I tested this kernel and it works. There are some other fixes related to SES 
that are currently only in 4.8/4.10 kernels, so we need to determine whether 
anything else is required.

I am assuming that this fix will also be going into 4.8 and 4.10, right?

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

Title:
  5U84 - ses driver isn't binding right - cannot blink lights on 1 of
  the 2 5u84

Status in The Ubuntu-power-systems project:
  New
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Xenial:
  In Progress
Status in linux source package in Yakkety:
  Won't Fix

Bug description:
  This is a request to add the following upstream commit to both Ubuntu
  16.04.1 and 16.04.2:

  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/scsi/ses.c?id=9373eba6cfae48911b977d14323032cd5d161aae

  Without this patch, the symlink in sysfs which binds a SAS device to
  an enclosure slot does not get created. This makes disk hotplug near
  impossible on large JBOD disk drawers.

  You should be able to do:

  ls /sys/block/sdb/device/ | grep enclosure

  and see something like:

  enclosure_device:1

  If you cd to this directory, you can then access the SES controls for
  that slot to flash the LED to assist in locating the disk to replace a
  failed disk.

  Currently with 16.04.1 and 16.04.2, these symlinks are not getting
  created.

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

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

[Kernel-packages] [Bug 1704479] Re: Change CONFIG_IBMVETH to module

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

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

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

Title:
  Change CONFIG_IBMVETH to module

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

Bug description:
  == Comment: #0 - Breno Leitao  - 2017-07-14 15:07:47 ==
  Dear Canonical,

  Please change the CONFIG_IBMVETH=y to module on artful kernel.

  Thank you,
  Breno

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

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

[Kernel-packages] [Bug 1705169] Re: Hotkeys on new Thinkpad systems aren't working

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

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

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

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

Title:
  Hotkeys on new Thinkpad systems aren't working

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

Bug description:
  This includes mic-mute, bluetooth, video switch and wireless on/off

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

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

[Kernel-packages] [Bug 1696852] Re: [SRU][Zesty] arm64: Add support for handling memory corruption

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

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

Title:
  [SRU][Zesty] arm64: Add support for handling memory corruption

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

Bug description:
  [Impact]
  Enable memory corruption handling for arm64

  [Test]
  run mce-test mce-test/cases/function/hwpoison

  [Fix]
  [0] https://www.mail-archive.com/linux-kernel@vger.kernel.org/msg1376052.html
  [1] https://www.spinics.net/lists/arm-kernel/msg581657.html
  [1] https://lkml.org/lkml/2017/4/7/486
  [2] https://lkml.org/lkml/2017/4/5/402

  Jonathan (Zhixiong) Zhang (2):
    arm64: hwpoison: add VM_FAULT_HWPOISON[_LARGE] handling
    arm64: kconfig: allow support for memory failure handling

  Punit Agrawal (2):
    arm64: hugetlb: Fix huge_pte_offset to return poisoned page table
  entries
    arm64: mm: Update perf accounting to handle poison faults

   arch/arm64/Kconfig   |  1 +
   arch/arm64/include/asm/pgtable.h |  2 +-
   arch/arm64/mm/fault.c| 90 

   arch/arm64/mm/hugetlbpage.c  | 29 +
   4 files changed, 67 insertions(+), 55 deletions(-)

  [Regression Potential]
  Changes are confined to ARM64 architecture. Detailed test results are posted 
to this bug as comments.

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

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

[Kernel-packages] [Bug 1696570] Re: [SRU][Zesty] Add UEFI 2.6 and ACPI 6.1 updates for RAS on ARM64

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

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

Title:
  [SRU][Zesty] Add UEFI 2.6 and ACPI 6.1 updates for RAS on ARM64

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

Bug description:
  [Impact]
  Adds UEFI 2.6 and ACPI 6.1 updates for RAS on ARM64.

  [Test]
  Run mce-test for testing RAS features.

  [Fix]
  In maintainer (Will Deacon's) tree 
https://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git/log/?h=for-next/ras-apei

  [V17,01/11] acpi: apei: read ack upon ghes record consumption
  [V17,02/11] ras: acpi/apei: cper: add support for generic data v3 structure
  [V17,03/11] cper: add timestamp print to CPER status printing
  [V17,04/11] efi: parse ARM processor error
  [V17,05/11] arm64: exception: handle Synchronous External Abort
  [V17,06/11] acpi: apei: handle SEA notification type for ARMv8
  [V17,07/11] acpi: apei: panic OS with fatal error status block
  [V17,08/11] efi: print unrecognized CPER section
  [V17,09/11] ras: acpi / apei: generate trace event for unrecognized CPER 
section
  [V17,10/11] trace, ras: add ARM processor error trace event
  [V17,11/11] arm/arm64: KVM: add guest SEA support

  [Regression Potential]
  Patches deal with updates for RAS features on ARM64 with minor impact to 
generic code.Kernel was boot tested on ARM64, AMD64 and Power8 and no 
regressions were found.

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

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

[Kernel-packages] [Bug 1705447] Re: misleading kernel warning skb_warn_bad_offload during checksum calculation

2017-07-20 Thread malikons

Tested with your test kernel and I can confirm that the problem has been
resolved.

Thanks a lot!

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

Title:
  misleading kernel warning skb_warn_bad_offload during checksum
  calculation

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:
  Even when the packet says checksum calculation is unnecessary the
  kernel will still check the checksum and display a warning that the
  checksum is bad.

  This has been fixed upstream in Kernel 4.11 by commit id:
  b2504a5dbef3305ef41988ad270b0e8ec289331c

  We have reports of Ubuntu 16.04 virtual machines (with ip forward
  enabled) displaying these warnings:

  
  [10480.074664] [ cut here ]
  [10480.074667] WARNING: CPU: 1 PID: 0 at 
/build/linux-hwe-X3pKE5/linux-hwe-4.8.0/net/core/dev.c:2444 
skb_warn_bad_offload+0xd1/0x120
  [10480.074669] docker0: caps=(0x0400ffbb78e9, 0x) 
len=2962 data_len=2834 gso_size=1448 gso_type=5 ip_summed=1
  [10480.074670] Modules linked in: veth nfsv3 nfs_acl rpcsec_gss_krb5 
auth_rpcgss nfsv4 nfs lockd grace sunrpc fscache ipt_MASQUERADE 
nf_nat_masquerade_ipv4 xfrm_user xfrm_algo iptable_nat nf_conntrack_ipv4 
nf_defrag_ipv4 nf_nat_ipv4 xt_addrtype iptable_filter ip_tables xt_conntrack 
x_tables nf_nat nf_conntrack br_netfilter bridge stp llc aufs zfs(PO) 
zunicode(PO) zcommon(PO) znvpair(PO) spl(O) zavl(PO) crct10dif_pclmul 
crc32_pclmul ghash_clmulni_intel aesni_intel aes_x86_64 lrw glue_helper 
ablk_helper cryptd input_leds joydev serio_raw i2c_piix4 mac_hid parport_pc 
ppdev lp parport autofs4 hid_generic usbhid hid virtio_scsi psmouse virtio_net 
pata_acpi floppy
  [10480.074695] CPU: 1 PID: 0 Comm: swapper/1 Tainted: PW  O
4.8.0-52-generic #55~16.04.1-Ubuntu
  [10480.074696] Hardware name: Nutanix AHV, BIOS seabios-1.7.5-11.el6 
04/01/2014
  [10480.074697]  0286 ec176c2ae03bc036 8beef5643870 
b7a2e7b3
  [10480.074699]  8beef56438c0  8beef56438b0 
b768314b
  [10480.074702]  098cb84fba80 8bed61f82000 8bee9915c000 
0005
  [10480.074704] Call Trace:
  [10480.074704][] dump_stack+0x63/0x90
  [10480.074708]  [] __warn+0xcb/0xf0
  [10480.074710]  [] warn_slowpath_fmt+0x5f/0x80
  [10480.074713]  [] ? ___ratelimit+0xa2/0xf0
  [10480.074714]  [] skb_warn_bad_offload+0xd1/0x120
  [10480.074716]  [] __skb_gso_segment+0xd8/0x140
  [10480.074717]  [] validate_xmit_skb+0x14f/0x2a0
  [10480.074719]  [] __dev_queue_xmit+0x322/0x6d0
  [10480.074720]  [] ? nf_nat_ipv4_fn+0x1a6/0x230 
[nf_nat_ipv4]
  [10480.074723]  [] dev_queue_xmit+0x10/0x20
  [10480.074725]  [] ip_finish_output2+0x292/0x380
  [10480.074726]  [] ? ipv4_confirm+0x7d/0x100 
[nf_conntrack_ipv4]
  [10480.074728]  [] ip_finish_output+0x132/0x1d0
  [10480.074729]  [] ? nf_hook_slow+0x73/0xd0
  [10480.074731]  [] ip_output+0x6e/0xf0
  [10480.074733]  [] ? 
__ip_flush_pending_frames.isra.40+0x90/0x90
  [10480.074736]  [] ip_forward_finish+0x43/0x70
  [10480.074738]  [] ip_forward+0x384/0x480
  [10480.074739]  [] ? ip_frag_mem+0x50/0x50
  [10480.074741]  [] ip_rcv_finish+0x11b/0x400
  [10480.074743]  [] ip_rcv+0x28b/0x3c0
  [10480.074744]  [] ? inet_del_offload+0x40/0x40
  [10480.074746]  [] __netif_receive_skb_core+0x524/0xab0
  [10480.074747]  [] ? kmem_cache_alloc+0xd7/0x1b0
  [10480.074749]  [] ? __build_skb+0x2a/0xe0
  [10480.074751]  [] __netif_receive_skb+0x18/0x60
  [10480.074753]  [] netif_receive_skb_internal+0x32/0xa0
  [10480.074754]  [] napi_gro_receive+0xcd/0x120
  [10480.074756]  [] virtnet_receive+0x1c3/0x970 [virtio_net]
  [10480.074758]  [] ? update_cfs_rq_load_avg+0x1f9/0x4c0
  [10480.074760]  [] virtnet_poll+0x1d/0x80 [virtio_net]
  [10480.074762]  [] net_rx_action+0x238/0x380
  [10480.074764]  [] __do_softirq+0xf6/0x280
  [10480.074765]  [] irq_exit+0xa3/0xb0
  [10480.074766]  [] do_IRQ+0x54/0xd0
  [10480.074768]  [] common_interrupt+0x82/0x82
  [10480.074768][] ? native_safe_halt+0x6/0x10
  [10480.074772]  [] default_idle+0x1e/0xd0
  [10480.074774]  [] arch_cpu_idle+0xf/0x20
  [10480.074775]  [] default_idle_call+0x2a/0x40
  [10480.074776]  [] cpu_startup_entry+0x2ea/0x350
  [10480.074778]  [] start_secondary+0x151/0x190
  [10480.074781] ---[ end trace 3a9bd18de5564b05 ]---

  
  We have recompiled your latest 16.04.2 kernel with this patch and confirmed 
that this warning does not happen. Could you please consider including this fix 
in your next 16.04 LTS release?

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

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

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

I built Xenial, Zesty and Artful test kernels with commit 66aa0678efc2.
The test kernels can be downloaded from:

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

Can you test these kernels and see if they resolve 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/1692538

Title:
  Ubuntu 16.04.02: ibmveth: Support to enable LSO/CSO for Trunk VEA

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

Bug description:
  == 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 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 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 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   Increases performance greatly

  The patch has been accepted upstream: 
  https://patchwork.ozlabs.org/patch/764533/

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

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

[Kernel-packages] [Bug 1238110] Re: makedumpfile needs porting for AArch64

2017-07-20 Thread Brian Murray

Hello Matthias, or anyone else affected,

Accepted makedumpfile into xenial-proposed. The package will build now
and be available at
https://launchpad.net/ubuntu/+source/makedumpfile/1:1.5.9-5ubuntu0.5 in
a few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-xenial to verification-done-xenial. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-xenial. In either case, details of your
testing will help us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

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

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

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

Title:
  makedumpfile needs porting for AArch64

Status in Linaro AArch64 cross-distro work:
  New
Status in makedumpfile package in Ubuntu:
  Fix Released
Status in makedumpfile source package in Xenial:
  Fix Committed

Bug description:
  [Impact]
  kdump-tools is not installable on arm64 because it depends on makedumpfile, 
which is not currently built on arm64. Adding arm64 to the Architecture list in 
debian/control is all that is needed for it to build successfully.

  That said, xenial's version was too old to support filtering kdump-
  enabled xenial kernels (>= 4.10.0). So, this doesn't actually produce
  a *useful* makedumpfile, but does allow kdump-tools to be installed,
  which unblocks collection of (unfiltered) crash dump files.

  [Test Case]
  On an arm64 system:
   sudo apt install kdump-tools

  [Regression Risk]
  The only change here is to make a binary package available on arm64 that 
previously was not - regression risk to existing architectures should therefore 
be negligible.

  Note: Enabling a binary package for an architecture where it's known
  not to be useful - at last on it's own - is obviously non-ideal. I
  considered other options, but they all seem to add unnecessary
  regression risk:

  - Demoting the "Depends:" to a "Recommends:". I actually think we
  should do this going forward (https://bugs.debian.org/cgi-
  bin/bugreport.cgi?bug=865701), but this would be a change in behavior
  to people who may install kdump-tools w/ Recommends-disabled and
  expect to stil get makedumpfile.

  - Demoting only on arm64: This isn't possible unless we switch kdump-
  tools from Binary: any to Binary: all. I also think there are good
  reasons to do that in future releases (https://bugs.debian.org/cgi-
  bin/bugreport.cgi?bug=863858), but it seems overkill for just enabling
  arm64.

To manage notifications about this bug go to:
https://bugs.launchpad.net/linaro-aarch64/+bug/1238110/+subscriptions

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

[Kernel-packages] [Bug 1694859] Re: arm64 kernel crashdump support

2017-07-20 Thread Brian Murray

Hello dann, or anyone else affected,

Accepted makedumpfile into xenial-proposed. The package will build now
and be available at
https://launchpad.net/ubuntu/+source/makedumpfile/1:1.5.9-5ubuntu0.5 in
a few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-xenial to verification-done-xenial. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-xenial. In either case, details of your
testing will help us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Changed in: makedumpfile (Ubuntu)
   Status: Confirmed => Fix Released

** Changed in: makedumpfile (Ubuntu Zesty)
   Status: Confirmed => Fix Released

** Changed in: makedumpfile (Ubuntu Yakkety)
   Status: Confirmed => Won't Fix

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

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

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

Title:
  arm64 kernel crashdump support

Status in kexec-tools package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in makedumpfile package in Ubuntu:
  Fix Released
Status in kexec-tools source package in Xenial:
  Fix Committed
Status in linux source package in Xenial:
  Won't Fix
Status in makedumpfile source package in Xenial:
  Fix Committed
Status in kexec-tools source package in Yakkety:
  In Progress
Status in linux source package in Yakkety:
  Won't Fix
Status in makedumpfile source package in Yakkety:
  Won't Fix
Status in kexec-tools source package in Zesty:
  Fix Committed
Status in linux source package in Zesty:
  Fix Released
Status in makedumpfile source package in Zesty:
  Fix Released

Bug description:
  Note: Updates are being staged at ppa:dannf/arm64-kdump.

  [Impact]
  It is not possible to collect a kernel crash dump from a crashed arm64 server 
for later debugging.

  [Test Case]
  sudo apt install kdump-tools
  (reboot, so crashkernel= is added to the kernel commandline)
  echo c | sudo tee /proc/sysrq-trigger

  Crash dump should occur, with artifacts collected in /var/crash.

  If you want to verify that the dump is usable, install the
  corresponding linux-image--dbgsym package and run:

  sudo crash /usr/lib/debug/boot/vmlinux-
  /var/crash//dump.

  crash should successfully load, placing you at a "crash>" prompt. At that 
prompt, you can issue the 'bt' command to see a backtrace.
  Note: you need crash from zesty (7.1.8-1ubuntu1) or later.

  [Regression Risk]
  = Kernel =
  3 patches here touch code outside of arch/arm64/:

  memblock: add memblock_clear_nomap()
  This adds a new function with no callers, so regression risk is negligible.
  (A later patch adds a call to it under arch/arm64/).

  memblock: add memblock_cap_memory_range()
  This refactors some of the code in memblock_mem_limit_remove_map() into a new 
function. The only existing caller of memblock_mem_limit_remove_map() is under 
arch/arm64/, so the regression risk outside of arm64 is negligible.

  efi/libstub/arm*: Set default address and size cells values for an empty dtb
  Because this code is for EFI platforms that support device-tree, it is 
de-facto ARM-specific (as noted in the patch title).

  For arm64, we have mitigated the risk by explicit regression testing on 
several platforms:
   - Qualcomm QDF2400
   - Cavium ThunderX CRB1S
   - HP m400 (X-Gene)
   - HiSilicon D05 (Hi07)

  = kexec-tools =
  == zesty ==
  For zesty, 10 patches are required to add kdump support.

  0001-kexec-extend-the-semantics-of-kexec_iomem_for_each_l.patch:
  This modifies a function used on armhf & x86. The description explains the 
change, and why it does not impact those archs:

  -
  The current users of kexec_iomem_for_each_line(), arm, sh and x86, will not
  be affected by this change because
  * arm
    The callback function only returns -1 or 0, and the return value of
    kexec_iomem_for_each_line() will never be used.
  * sh, x86
    The callback function may return (-1 for sh,) 0 or 1, but always returns
    1 once we have reached the maximum number of entries allowed.
    Even so the current kexec_iomem_for_each_line() counts them up.
    This change actually fixes this bug.
  -

[Kernel-packages] [Bug 1705003] Re: linux: 3.19.0-89.97 -proposed tracker

2017-07-20 Thread Steve Beattie

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

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

Title:
  linux: 3.19.0-89.97 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
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: 1705004
  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/1705003/+subscriptions

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

[Kernel-packages] [Bug 1454450] Re: Bluetooth mouse laggy and erratic

2017-07-20 Thread Nicolas Jafelle

Having the same issue with Logitech m535 and dell xps 13 9350 with
broadcom bcm4350 card.

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

Title:
  Bluetooth mouse laggy and erratic

Status in bluez package in Ubuntu:
  Confirmed
Status in linux-firmware package in Ubuntu:
  Confirmed

Bug description:
  I installed Ubuntu 15.04 (64 bit) on a DELL XPS 13 (model 9343, bios
  A03) notebook. I use a DELL bluetooth mouse but sometimes it behaves
  erratically (laggy, jumpy). The problem happens after a few (sometimes
  one) suspend and resume. I am attaching below some info on my system.
  Thank you.

  cribari@darwin4:~$ uname -a; lspci -nnk | grep -iA2 net; lsusb; dmesg | grep 
-i bluetooth; dmesg | grep -i firmware; lsmod | grep bluetooth
  Linux darwin4 3.19.0-17-generic #17-Ubuntu SMP Wed May 6 16:46:12 UTC 2015 
x86_64 x86_64 x86_64 GNU/Linux
  02:00.0 Network controller [0280]: Broadcom Corporation BCM4352 802.11ac 
Wireless Network Adapter [14e4:43b1] (rev 03)
   Subsystem: Dell Device [1028:0019]
   Kernel driver in use: wl
  Bus 003 Device 002: ID 8087:8001 Intel Corp.
  Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 001 Device 004: ID 0c45:670c Microdia
  Bus 001 Device 003: ID 04f3:20d0 Elan Microelectronics Corp.
  Bus 001 Device 002: ID 0a5c:216f Broadcom Corp.
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  [2.174367] Bluetooth: Core ver 2.20
  [2.174669] Bluetooth: HCI device and connection manager initialized
  [2.174792] Bluetooth: HCI socket layer initialized
  [2.174795] Bluetooth: L2CAP socket layer initialized
  [2.175449] Bluetooth: SCO socket layer initialized
  [2.592936] Bluetooth: hci0: BCM: patching hci_ver=06 hci_rev=1624 
lmp_ver=06 lmp_subver=220e
  [3.203438] Bluetooth: hci0: BCM: firmware hci_ver=06 hci_rev=1624 
lmp_ver=06 lmp_subver=220e
  [3.542418] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
  [3.542421] Bluetooth: BNEP filters: protocol multicast
  [3.542425] Bluetooth: BNEP socket layer initialized
  [3.551641] Bluetooth: RFCOMM TTY layer initialized
  [3.551649] Bluetooth: RFCOMM socket layer initialized
  [3.551654] Bluetooth: RFCOMM ver 1.11
  [   26.569283] Bluetooth: HIDP (Human Interface Emulation) ver 1.2
  [   26.569287] Bluetooth: HIDP socket layer initialized
  [   26.576971] input: Dell Travel Mouse WM524 as 
/devices/pci:00/:00:14.0/usb1/1-3/1-3:1.0/bluetooth/hci0/hci0:11/0005:046D:B00E.0003/input/input15
  [   26.577172] hid-generic 0005:046D:B00E.0003: input,hidraw2: BLUETOOTH HID 
v8.00 Mouse [Dell Travel Mouse WM524] on ac:d1:b8:c0:6f:5c
  [   72.448281] input: Dell Travel Mouse WM524 as 
/devices/pci:00/:00:14.0/usb1/1-3/1-3:1.0/bluetooth/hci0/hci0:12/0005:046D:B00E.0004/input/input16
  [   72.448526] hid-generic 0005:046D:B00E.0004: input,hidraw2: BLUETOOTH HID 
v8.00 Mouse [Dell Travel Mouse WM524] on ac:d1:b8:c0:6f:5c
  [ 2994.842547] input: Dell Travel Mouse WM524 as 
/devices/pci:00/:00:14.0/usb1/1-3/1-3:1.0/bluetooth/hci0/hci0:13/0005:046D:B00E.0005/input/input17
  [ 2994.842810] hid-generic 0005:046D:B00E.0005: input,hidraw2: BLUETOOTH HID 
v8.00 Mouse [Dell Travel Mouse WM524] on ac:d1:b8:c0:6f:5c
  [ 3694.214037] Bluetooth: hci0: BCM: patching hci_ver=06 hci_rev=1000 
lmp_ver=06 lmp_subver=220e
  [ 3694.861578] Bluetooth: hci0: BCM: firmware hci_ver=06 hci_rev=1624 
lmp_ver=06 lmp_subver=220e
  [ 3811.777260] input: Dell Travel Mouse WM524 as 
/devices/pci:00/:00:14.0/usb1/1-3/1-3:1.0/bluetooth/hci0/hci0:11/0005:046D:B00E.0006/input/input20
  [ 3811.777571] hid-generic 0005:046D:B00E.0006: input,hidraw2: BLUETOOTH HID 
v8.00 Mouse [Dell Travel Mouse WM524] on ac:d1:b8:c0:6f:5c
  [ 5579.876192] Modules linked in: huawei_cdc_ncm cdc_wdm cdc_ncm option 
usb_wwan usbserial usbnet mii uas usb_storage hid_generic hidp nvram msr 
binfmt_misc rfcomm bnep nls_iso8859_1 intel_rapl iosf_mbi x86_pkg_temp_thermal 
dell_wmi sparse_keymap intel_powerclamp coretemp kvm_intel kvm crct10dif_pclmul 
dell_laptop dcdbas btusb crc32_pclmul bluetooth ghash_clmulni_intel 
hid_multitouch aesni_intel aes_x86_64 lrw uvcvideo gf128mul videobuf2_vmalloc 
glue_helper wl(POE) videobuf2_memops ablk_helper videobuf2_core cryptd 
v4l2_common videodev media joydev i915_bpo serio_raw i915 dell_led rtsx_pci_ms 
intel_ips memstick snd_hda_codec_realtek snd_soc_rt286 snd_hda_codec_generic 
cfg80211 snd_soc_core drm_kms_helper mei_me lpc_ich shpchp mei snd_compress 
snd_hda_intel snd_hda_controller drm snd_hda_codec i2c_algo_bit
  [ 5579.876223] Workqueue: hci0 hci_power_on [bluetooth]
  [ 5579.876261]  [] hci_dev_do_open+0xe1/0xa90 [bluetooth]
  [ 5579.876266]  [] hci_power_on+0x40/0x200 [bluetooth]
  [ 5579.876284] bluetooth hci0: firmware: brcm/BCM20702A0-0a5c-216f.hcd

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

--- Comment From drbr...@us.ibm.com 2017-07-20 14:16 EDT---
Canonical please clarify. I was on a call with Andrew Cloke earlier today. He 
said this could be done but not done in time for 17.10 GA in October. It would 
happen after 17.10 GA.

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

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

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

Bug description:
  Feature Description:

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

  
  Business Case: 

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

  Use Case:

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

  
  Test Case:

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

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

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

[Kernel-packages] [Bug 1704994] Re: linux: 3.13.0-126.175 -proposed tracker

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

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

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

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  backports: 1704995
  derivatives:
+ kernel-stable-phase:Uploaded
+ kernel-stable-phase-changed:Thursday, 20. July 2017 17:31 UTC

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  backports: 1704995
  derivatives:
  kernel-stable-phase:Uploaded
  kernel-stable-phase-changed:Thursday, 20. July 2017 17:31 UTC
+ 
+ -- swm properties --
+ phase: Uploaded

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

Title:
  linux: 3.13.0-126.175 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in 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: 1704995
  derivatives:
  kernel-stable-phase:Uploaded
  kernel-stable-phase-changed:Thursday, 20. July 2017 17:31 UTC

  -- swm properties --
  phase: Uploaded

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

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

[Kernel-packages] [Bug 1704995] Re: linux-lts-trusty: -proposed tracker

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

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  kernel-stable-master-bug: 1704994
+ kernel-stable-phase:Packaging
+ kernel-stable-phase-changed:Thursday, 20. July 2017 17:31 UTC

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  kernel-stable-master-bug: 1704994
- kernel-stable-phase:Packaging
- kernel-stable-phase-changed:Thursday, 20. July 2017 17:31 UTC
+ phase: Packaging

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

Title:
  linux-lts-trusty:  -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  Confirmed
Status in Kernel SRU Workflow prepare-package-meta series:
  New
Status in Kernel SRU Workflow prepare-package-signed series:
  New
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-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 --
  kernel-stable-master-bug: 1704994
  phase: Packaging

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

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

[Kernel-packages] [Bug 1705447] Re: misleading kernel warning skb_warn_bad_offload during checksum calculation

2017-07-20 Thread malikons

Brilliant! Testing it now.

Cheers,

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

Title:
  misleading kernel warning skb_warn_bad_offload during checksum
  calculation

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:
  Even when the packet says checksum calculation is unnecessary the
  kernel will still check the checksum and display a warning that the
  checksum is bad.

  This has been fixed upstream in Kernel 4.11 by commit id:
  b2504a5dbef3305ef41988ad270b0e8ec289331c

  We have reports of Ubuntu 16.04 virtual machines (with ip forward
  enabled) displaying these warnings:

  
  [10480.074664] [ cut here ]
  [10480.074667] WARNING: CPU: 1 PID: 0 at 
/build/linux-hwe-X3pKE5/linux-hwe-4.8.0/net/core/dev.c:2444 
skb_warn_bad_offload+0xd1/0x120
  [10480.074669] docker0: caps=(0x0400ffbb78e9, 0x) 
len=2962 data_len=2834 gso_size=1448 gso_type=5 ip_summed=1
  [10480.074670] Modules linked in: veth nfsv3 nfs_acl rpcsec_gss_krb5 
auth_rpcgss nfsv4 nfs lockd grace sunrpc fscache ipt_MASQUERADE 
nf_nat_masquerade_ipv4 xfrm_user xfrm_algo iptable_nat nf_conntrack_ipv4 
nf_defrag_ipv4 nf_nat_ipv4 xt_addrtype iptable_filter ip_tables xt_conntrack 
x_tables nf_nat nf_conntrack br_netfilter bridge stp llc aufs zfs(PO) 
zunicode(PO) zcommon(PO) znvpair(PO) spl(O) zavl(PO) crct10dif_pclmul 
crc32_pclmul ghash_clmulni_intel aesni_intel aes_x86_64 lrw glue_helper 
ablk_helper cryptd input_leds joydev serio_raw i2c_piix4 mac_hid parport_pc 
ppdev lp parport autofs4 hid_generic usbhid hid virtio_scsi psmouse virtio_net 
pata_acpi floppy
  [10480.074695] CPU: 1 PID: 0 Comm: swapper/1 Tainted: PW  O
4.8.0-52-generic #55~16.04.1-Ubuntu
  [10480.074696] Hardware name: Nutanix AHV, BIOS seabios-1.7.5-11.el6 
04/01/2014
  [10480.074697]  0286 ec176c2ae03bc036 8beef5643870 
b7a2e7b3
  [10480.074699]  8beef56438c0  8beef56438b0 
b768314b
  [10480.074702]  098cb84fba80 8bed61f82000 8bee9915c000 
0005
  [10480.074704] Call Trace:
  [10480.074704][] dump_stack+0x63/0x90
  [10480.074708]  [] __warn+0xcb/0xf0
  [10480.074710]  [] warn_slowpath_fmt+0x5f/0x80
  [10480.074713]  [] ? ___ratelimit+0xa2/0xf0
  [10480.074714]  [] skb_warn_bad_offload+0xd1/0x120
  [10480.074716]  [] __skb_gso_segment+0xd8/0x140
  [10480.074717]  [] validate_xmit_skb+0x14f/0x2a0
  [10480.074719]  [] __dev_queue_xmit+0x322/0x6d0
  [10480.074720]  [] ? nf_nat_ipv4_fn+0x1a6/0x230 
[nf_nat_ipv4]
  [10480.074723]  [] dev_queue_xmit+0x10/0x20
  [10480.074725]  [] ip_finish_output2+0x292/0x380
  [10480.074726]  [] ? ipv4_confirm+0x7d/0x100 
[nf_conntrack_ipv4]
  [10480.074728]  [] ip_finish_output+0x132/0x1d0
  [10480.074729]  [] ? nf_hook_slow+0x73/0xd0
  [10480.074731]  [] ip_output+0x6e/0xf0
  [10480.074733]  [] ? 
__ip_flush_pending_frames.isra.40+0x90/0x90
  [10480.074736]  [] ip_forward_finish+0x43/0x70
  [10480.074738]  [] ip_forward+0x384/0x480
  [10480.074739]  [] ? ip_frag_mem+0x50/0x50
  [10480.074741]  [] ip_rcv_finish+0x11b/0x400
  [10480.074743]  [] ip_rcv+0x28b/0x3c0
  [10480.074744]  [] ? inet_del_offload+0x40/0x40
  [10480.074746]  [] __netif_receive_skb_core+0x524/0xab0
  [10480.074747]  [] ? kmem_cache_alloc+0xd7/0x1b0
  [10480.074749]  [] ? __build_skb+0x2a/0xe0
  [10480.074751]  [] __netif_receive_skb+0x18/0x60
  [10480.074753]  [] netif_receive_skb_internal+0x32/0xa0
  [10480.074754]  [] napi_gro_receive+0xcd/0x120
  [10480.074756]  [] virtnet_receive+0x1c3/0x970 [virtio_net]
  [10480.074758]  [] ? update_cfs_rq_load_avg+0x1f9/0x4c0
  [10480.074760]  [] virtnet_poll+0x1d/0x80 [virtio_net]
  [10480.074762]  [] net_rx_action+0x238/0x380
  [10480.074764]  [] __do_softirq+0xf6/0x280
  [10480.074765]  [] irq_exit+0xa3/0xb0
  [10480.074766]  [] do_IRQ+0x54/0xd0
  [10480.074768]  [] common_interrupt+0x82/0x82
  [10480.074768][] ? native_safe_halt+0x6/0x10
  [10480.074772]  [] default_idle+0x1e/0xd0
  [10480.074774]  [] arch_cpu_idle+0xf/0x20
  [10480.074775]  [] default_idle_call+0x2a/0x40
  [10480.074776]  [] cpu_startup_entry+0x2ea/0x350
  [10480.074778]  [] start_secondary+0x151/0x190
  [10480.074781] ---[ end trace 3a9bd18de5564b05 ]---

  
  We have recompiled your latest 16.04.2 kernel with this patch and confirmed 
that this warning does not happen. Could you please consider including this fix 
in your next 16.04 LTS release?

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

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

[Kernel-packages] [Bug 1678184] Re: APST quirk needed for Samsung 512GB NVMe drive

2017-07-20 Thread Steve Roberts

Just landed here with similar issue on Samsung 960 EVO 500GB, system
crashes/hangs with disk inaccessible (?) but mostly after resume from
suspend, or latest 3 mins after cold boot...


Kernel 4.10.0-26-generic
M/B Asus Prime B350m-A

Seems it is either not fixed or I have another bug

e.g.
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  GB512   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
ps0 : mp:6.04W operational enlat:0 exlat:0 rrt:0 rrl:0
  rwt:0 rwl:0 idle_power:- active_power:-
ps1 : mp:5.09W operational enlat:0 exlat:0 rrt:1 rrl:1
  rwt:1 rwl:1 idle_power:- active_power:-
ps2 : mp:4.08W operational enlat:0 exlat:0 rrt:2 rrl:2
  rwt:2 rwl:2 idle_power:- active_power:-
ps3 : mp:0.0400W non-operational enlat:210 exlat:1500 rrt:3 rrl:3
  rwt:3 rwl:3 idle_power:- active_power:-
ps4 : mp:0.0050W non-operational enlat:2200 exlat:6000 rrt:4 rrl:4
  rwt:4 rwl:4 idle_power:- active_power:-

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

Title:
  APST quirk needed for Samsung 512GB NVMe drive

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

Bug description:
  APST support just landed in the latest Zesty kernel (4.10.0-14.16) as
  part of https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1664602.
  That patch has a quirk for certain 256GB Samsung drives found in Dell
  laptops that do not behave well when APST is enabled. I am
  experiencing the same symptoms with the same model laptop except with
  a 512GB Samsung. Prior to manually disabling APST the drive would die
  and system would go down in flames with I/O errors within 20 to 40
  minutes of boot.

  $ sudo nvme list
  Node SN   Model   
 Namespace Usage  Format   FW Rev  
    
 - -- 
 
  /dev/nvme0n1   ** PM951 NVMe SAMSUNG 512GB
 1 500.20  GB / 512.11  GB512   B +  0 B   BXV76D0Q

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-14-generic 4.10.0-14.16
  ProcVersionSignature: Ubuntu 4.10.0-14.16-generic 4.10.3
  Uname: Linux 4.10.0-14-generic x86_64
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ajclayton   3305 F pulseaudio
  CurrentDesktop: Unity:Unity7
  Date: Fri Mar 31 09:42:38 2017
  InstallationDate: Installed on 2012-09-08 (1665 days ago)
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
  MachineType: Dell Inc. XPS 15 9550
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-14-generic 
root=UUID=779e5929-5ffb-49b1-9786-1adcde824b7d ro rootflags=subvol=@ noprompt 
nouveau.modeset=0 log_buf_len=20M
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-14-generic N/A
   linux-backports-modules-4.10.0-14-generic  N/A
   linux-firmware 1.164
  SourcePackage: linux
  UpgradeStatus: Upgraded to zesty on 2017-03-07 (23 days ago)
  dmi.bios.date: 04/07/2016
  dmi.bios.vendor: Dell Inc.

[Kernel-packages] [Bug 1640200] Re: 16.10 hangs on shutdown

2017-07-20 Thread bigsicret

Solution ici : https://bbs.archlinux.org/viewtopic.php?id=148033

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

Title:
  16.10 hangs on shutdown

Status in linux package in Ubuntu:
  Expired

Bug description:
  This bug is about my Gateway M1629 not shutting down screen stops at reached 
. I can reproduce it every time. I also have a problem with booting up ( may be 
related) that has to do with the timing. If I click on ubunto LTS in grub 
screen it boots to a black screen. But if I make it wait by clicking on boot 
options and then back to ubuntu  it boots fine!
  The bug about hanging was reported so many times. I am not sure if is the 
kernel or the bios? too many answers but never one fix! can someone help please?
  Thanks,
  David
  --- 
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC1D0p:   david 22172 F...m pulseaudio
   /dev/snd/controlC1:  david 22172 F pulseaudio
   /dev/snd/controlC0:  david 22172 F pulseaudio
   /dev/snd/controlC2:  david 22172 F pulseaudio
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 16.10
  HibernationDevice: RESUME=UUID=7ede9358-a634-4d7a-ba7f-6f3ef9e433bb
  InstallationDate: Installed on 2016-11-03 (5 days ago)
  InstallationMedia: Ubuntu-Studio 16.10 "Yakkety Yak" - Release amd64 
(20161012.1)
  MachineType: Gateway M-1629
  Package: linux (not installed)
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-26-lowlatency 
root=UUID=60158545-3519-4bb6-8178-79f862ba7f87 ro recovery nomodeset
  ProcVersionSignature: Ubuntu 4.8.0-26.28-lowlatency 4.8.0
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-26-lowlatency N/A
   linux-backports-modules-4.8.0-26-lowlatency  N/A
   linux-firmware   1.161
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  Tags:  yakkety
  Uname: Linux 4.8.0-26-lowlatency x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/23/2008
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: 9D.05
  dmi.board.vendor: Gateway
  dmi.board.version: 9D.05
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 8
  dmi.chassis.vendor: Gateway
  dmi.chassis.version: Rev.1
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr9D.05:bd05/23/2008:svnGateway:pnM-1629:pvr3409925R:rvnGateway:rn:rvr9D.05:cvnGateway:ct8:cvrRev.1:
  dmi.product.name: M-1629
  dmi.product.version: 3409925R
  dmi.sys.vendor: Gateway

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

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

[Kernel-packages] [Bug 1624540] Re: please have lxd recommend zfs

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

** Changed in: zfs-linux (Ubuntu)
 Assignee: (unassigned) => Colin Ian King (colin-king)

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

Title:
  please have lxd recommend zfs

Status in lxd package in Ubuntu:
  Incomplete
Status in zfs-linux package in Ubuntu:
  In Progress

Bug description:
  Since ZFS is now in Main (Bug #1532198), LXD should recommend the ZFS
  userspace package, such that 'sudo lxd init' just works.

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

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

[Kernel-packages] [Bug 1685528] Re: ZFS initramfs mounts dataset explicitly set not to be mounted, causing boot process to fail

Hi Richard, I'll be happy to upload this fixes into the non-LTS releases
where this script is missing.

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

Title:
  ZFS initramfs mounts dataset explicitly set not to be mounted, causing
  boot process to fail

Status in zfs-linux package in Ubuntu:
  Confirmed

Bug description:
  Per https://github.com/zfsonlinux/pkg-zfs/issues/221: the initramfs
  zfs script might overrule canmount and mountpoint options for a
  dataset, causing other mount operations and with them the boot process
  to fail.

  Experienced this with Ubuntu Zesty. Xenial seems to ship with a
  different zfs script for the initrd.

  Work around when it happens: unmount the dataset that should not be
  mounted, and exit the initramfs rescue prompt to resume booting.

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

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

[Kernel-packages] [Bug 1567557] Re: Performance degradation of "zfs clone"

** Summary changed:

- Performance degradation of "zfs clone" when under load
+ Performance degradation of "zfs clone"

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

Title:
  Performance degradation of "zfs clone"

Status in Native ZFS for Linux:
  New
Status in lxd package in Ubuntu:
  Confirmed
Status in zfs-linux package in Ubuntu:
  Triaged

Bug description:
  I've been running some scale tests for LXD and what I've noticed is
  that "zfs clone" gets slower and slower as the zfs filesystem is
  getting busier.

  It feels like "zfs clone" requires some kind of pool-wide lock or
  something and so needs for all operations to complete before it can
  clone a new filesystem.

  A basic LXD scale test with btrfs vs zfs shows what I mean, see below
  for the reports.

  The test is run on a completely dedicated physical server with the
  pool on a dedicated SSD, the exact same machine and SSD was used for
  the btrfs test.

  The zfs filesystem is configured with those settings:
   - relatime=on
   - sync=disabled
   - xattr=sa

  So it shouldn't be related to pending sync() calls...

  The workload in this case is ultimately 1024 containers running busybox as 
their init system and udhcpc grabbing an IP.
  The problem gets significantly worse if spawning busier containers, say a 
full Ubuntu system.

  === zfs ===
  root@edfu:~# /home/ubuntu/lxd-benchmark spawn --count=1024 
--image=images:alpine/edge/amd64 --privileged=true
  Test environment:
Server backend: lxd
Server version: 2.0.0.rc8
Kernel: Linux
Kernel architecture: x86_64
Kernel version: 4.4.0-16-generic
Storage backend: zfs
Storage version: 5
Container backend: lxc
Container version: 2.0.0.rc15

  Test variables:
Container count: 1024
Container mode: privileged
Image: images:alpine/edge/amd64
Batches: 128
Batch size: 8
Remainder: 0

  [Apr  3 06:42:51.170] Importing image into local store: 
64192037277800298d8c19473c055868e0288b039349b1c6579971fe99fdbac7
  [Apr  3 06:42:52.657] Starting the test
  [Apr  3 06:42:53.994] Started 8 containers in 1.336s
  [Apr  3 06:42:55.521] Started 16 containers in 2.864s
  [Apr  3 06:42:58.632] Started 32 containers in 5.975s
  [Apr  3 06:43:05.399] Started 64 containers in 12.742s
  [Apr  3 06:43:20.343] Started 128 containers in 27.686s
  [Apr  3 06:43:57.269] Started 256 containers in 64.612s
  [Apr  3 06:46:09.112] Started 512 containers in 196.455s
  [Apr  3 06:58:19.309] Started 1024 containers in 926.652s
  [Apr  3 06:58:19.309] Test completed in 926.652s

  === btrfs ===
  Test environment:
Server backend: lxd
Server version: 2.0.0.rc8
Kernel: Linux
Kernel architecture: x86_64
Kernel version: 4.4.0-16-generic
Storage backend: btrfs
Storage version: 4.4
Container backend: lxc
Container version: 2.0.0.rc15

  Test variables:
Container count: 1024
Container mode: privileged
Image: images:alpine/edge/amd64
Batches: 128
Batch size: 8
Remainder: 0

  [Apr  3 07:42:12.053] Importing image into local store: 
64192037277800298d8c19473c055868e0288b039349b1c6579971fe99fdbac7
  [Apr  3 07:42:13.351] Starting the test
  [Apr  3 07:42:14.793] Started 8 containers in 1.442s
  [Apr  3 07:42:16.495] Started 16 containers in 3.144s
  [Apr  3 07:42:19.881] Started 32 containers in 6.530s
  [Apr  3 07:42:26.798] Started 64 containers in 13.447s
  [Apr  3 07:42:42.048] Started 128 containers in 28.697s
  [Apr  3 07:43:13.210] Started 256 containers in 59.859s
  [Apr  3 07:44:26.238] Started 512 containers in 132.887s
  [Apr  3 07:47:30.708] Started 1024 containers in 317.357s
  [Apr  3 07:47:30.708] Test completed in 317.357s

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

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

[Kernel-packages] [Bug 1705117] Re: ubuntu 17.04 : Boot failed with luks disk

2017-07-20 Thread Goacid

Thanks, the latest rc kernel is ok.

** Tags added: kernel-fixed-upstream

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

Title:
  ubuntu 17.04 : Boot failed with luks disk

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 17.04 with kernel  4.10.0-21-generic #23-Ubuntu boot successfully with 
my lucks partition. I enter the pass and it works.
  But all kernels after this one failed to boot. I enter the pass and then it 
freeze.
  I guess it is a kernel issue.

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

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

[Kernel-packages] [Bug 1696154] Re: [17.10 FEAT] Sign POWER host/NV kernels

2017-07-20 Thread Andrew Cloke

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

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

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

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

Bug description:
  Feature Description:

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

  
  Business Case: 

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

  Use Case:

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

  
  Test Case:

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

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

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

[Kernel-packages] [Bug 1596835] Re: libnvpair.so.1 should be in /lib/, not /usr/lib/

This is indeed fixed in 17.04 Zesty onwards.  I'll SRU this sometime in
the future for earlier releases

** Changed in: zfs-linux (Ubuntu Zesty)
   Status: New => Fix Released

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

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

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

** Changed in: zfs-linux (Ubuntu Xenial)
 Assignee: (unassigned) => Colin Ian King (colin-king)

** Changed in: zfs-linux (Ubuntu Artful)
   Status: New => Fix Committed

** Changed in: zfs-linux (Ubuntu Artful)
   Status: Fix Committed => Fix Released

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

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

Title:
  libnvpair.so.1 should be in /lib/, not /usr/lib/

Status in zfs-linux package in Ubuntu:
  Fix Released
Status in zfs-linux source package in Xenial:
  Triaged
Status in zfs-linux source package in Zesty:
  Fix Released
Status in zfs-linux source package in Artful:
  Fix Released

Bug description:
  Currently, in Ubuntu 16.04, the package libnvpair1linux puts
  libnvpair.so.1 in /usr/lib/, however, tools like zpool and zfs which
  are installed in /sbin/ need this library. According to the FHS this
  means the required libraries should be in /lib/ in order to allow the
  user to install /usr/ on a separate partition that is not immediately
  available after boot.

  This turns out to be a problem indeed. On one of my systems I had
  /usr/ on a ZFS filesystem (and /, /lib/, /sbin/, /bin/ on a separate
  ext4 partition). However, the system failed to boot: it hung while
  mounting the ZFS partitions which failed because zpool import didn't
  work as it couldn't find libnvpair.so.1.

  $ apt-cache policy libnvpair1linux 
  libnvpair1linux:
Installed: 0.6.5.6-0ubuntu9
Candidate: 0.6.5.6-0ubuntu9
Version table:
   *** 0.6.5.6-0ubuntu9 500
  500 http://nl.archive.ubuntu.com/ubuntu xenial-updates/universe amd64 
Packages
  100 /var/lib/dpkg/status
   0.6.5.6-0ubuntu8 500
  500 http://nl.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages

  $ apt-cache policy zfsutils-linux
  zfsutils-linux:
Installed: 0.6.5.6-0ubuntu9
Candidate: 0.6.5.6-0ubuntu9
Version table:
   *** 0.6.5.6-0ubuntu9 500
  500 http://nl.archive.ubuntu.com/ubuntu xenial-updates/universe amd64 
Packages
  100 /var/lib/dpkg/status
   0.6.5.6-0ubuntu8 500
  500 http://nl.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages

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

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

[Kernel-packages] [Bug 1640200] Re: 16.10 hangs on shutdown

2017-07-20 Thread bigsicret

Same problem with debian 9 "Stretch". I had no problem with debian 8.

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

Title:
  16.10 hangs on shutdown

Status in linux package in Ubuntu:
  Expired

Bug description:
  This bug is about my Gateway M1629 not shutting down screen stops at reached 
. I can reproduce it every time. I also have a problem with booting up ( may be 
related) that has to do with the timing. If I click on ubunto LTS in grub 
screen it boots to a black screen. But if I make it wait by clicking on boot 
options and then back to ubuntu  it boots fine!
  The bug about hanging was reported so many times. I am not sure if is the 
kernel or the bios? too many answers but never one fix! can someone help please?
  Thanks,
  David
  --- 
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC1D0p:   david 22172 F...m pulseaudio
   /dev/snd/controlC1:  david 22172 F pulseaudio
   /dev/snd/controlC0:  david 22172 F pulseaudio
   /dev/snd/controlC2:  david 22172 F pulseaudio
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 16.10
  HibernationDevice: RESUME=UUID=7ede9358-a634-4d7a-ba7f-6f3ef9e433bb
  InstallationDate: Installed on 2016-11-03 (5 days ago)
  InstallationMedia: Ubuntu-Studio 16.10 "Yakkety Yak" - Release amd64 
(20161012.1)
  MachineType: Gateway M-1629
  Package: linux (not installed)
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-26-lowlatency 
root=UUID=60158545-3519-4bb6-8178-79f862ba7f87 ro recovery nomodeset
  ProcVersionSignature: Ubuntu 4.8.0-26.28-lowlatency 4.8.0
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-26-lowlatency N/A
   linux-backports-modules-4.8.0-26-lowlatency  N/A
   linux-firmware   1.161
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  Tags:  yakkety
  Uname: Linux 4.8.0-26-lowlatency x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/23/2008
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: 9D.05
  dmi.board.vendor: Gateway
  dmi.board.version: 9D.05
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 8
  dmi.chassis.vendor: Gateway
  dmi.chassis.version: Rev.1
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr9D.05:bd05/23/2008:svnGateway:pnM-1629:pvr3409925R:rvnGateway:rn:rvr9D.05:cvnGateway:ct8:cvrRev.1:
  dmi.product.name: M-1629
  dmi.product.version: 3409925R
  dmi.sys.vendor: Gateway

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

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

[Kernel-packages] [Bug 1696154] Re: [17.10 FEAT] Sign POWER host/NV kernels

2017-07-20 Thread Manoj Iyer

apw is assigned this bug, kernel/foundations team will turn on the
signing on the kernel and push it to a PPA for your testing. As for
priority.. It is next on apw's list after he clears validations for the
point 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/1696154

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

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

Bug description:
  Feature Description:

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

  
  Business Case: 

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

  Use Case:

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

  
  Test Case:

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

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

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

[Kernel-packages] [Bug 1596835] Re: libnvpair.so.1 should be in /lib/, not /usr/lib/

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

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

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

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

Title:
  libnvpair.so.1 should be in /lib/, not /usr/lib/

Status in zfs-linux package in Ubuntu:
  Fix Released
Status in zfs-linux source package in Xenial:
  Triaged
Status in zfs-linux source package in Zesty:
  Fix Released
Status in zfs-linux source package in Artful:
  Fix Released

Bug description:
  Currently, in Ubuntu 16.04, the package libnvpair1linux puts
  libnvpair.so.1 in /usr/lib/, however, tools like zpool and zfs which
  are installed in /sbin/ need this library. According to the FHS this
  means the required libraries should be in /lib/ in order to allow the
  user to install /usr/ on a separate partition that is not immediately
  available after boot.

  This turns out to be a problem indeed. On one of my systems I had
  /usr/ on a ZFS filesystem (and /, /lib/, /sbin/, /bin/ on a separate
  ext4 partition). However, the system failed to boot: it hung while
  mounting the ZFS partitions which failed because zpool import didn't
  work as it couldn't find libnvpair.so.1.

  $ apt-cache policy libnvpair1linux 
  libnvpair1linux:
Installed: 0.6.5.6-0ubuntu9
Candidate: 0.6.5.6-0ubuntu9
Version table:
   *** 0.6.5.6-0ubuntu9 500
  500 http://nl.archive.ubuntu.com/ubuntu xenial-updates/universe amd64 
Packages
  100 /var/lib/dpkg/status
   0.6.5.6-0ubuntu8 500
  500 http://nl.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages

  $ apt-cache policy zfsutils-linux
  zfsutils-linux:
Installed: 0.6.5.6-0ubuntu9
Candidate: 0.6.5.6-0ubuntu9
Version table:
   *** 0.6.5.6-0ubuntu9 500
  500 http://nl.archive.ubuntu.com/ubuntu xenial-updates/universe amd64 
Packages
  100 /var/lib/dpkg/status
   0.6.5.6-0ubuntu8 500
  500 http://nl.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages

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

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

[Kernel-packages] [Bug 1635115] Re: grub fails zfs root filesystem detection due to failed checksum

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

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

Title:
  grub fails zfs root filesystem detection due to failed checksum

Status in grub2 package in Ubuntu:
  Confirmed
Status in zfs-linux package in Ubuntu:
  Won't Fix

Bug description:
  root@q-1-d.sv1:~# lsb_release -rd
  Description:  Ubuntu 16.04.1 LTS
  Release:  16.04

  root@q-1-d.sv1:~# apt-cache policy grub2-common
  grub2-common:
Installed: 2.02~beta2-36ubuntu3.2
Candidate: 2.02~beta2-36ubuntu3.2
Version table:
   *** 2.02~beta2-36ubuntu3.2 500
  500 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   2.02~beta2-36ubuntu3 500
  500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages

  
  I followed https://github.com/zfsonlinux/zfs/wiki/Ubuntu-16.04-Root-on-ZFS to 
make a ZFS native root disk system.  

  Installation went fine, systems works like a champ... but then, after
  a while, it's time to apt-get update ; apt-get upgrade to update my
  kernel.  That apt-get install fails because grub can't detect it's
  root file system:

  root@q-2-d.sv1:~# grub-probe /
  grub-probe: error: unknown filesystem.

  Strange, this use to work.  Add in a -vv and I see:

  grub-core/kern/fs.c:56: Detecting zfs...
  grub-core/osdep/hostdisk.c:415: opening the device `/dev/sda1' in 
open_device()
  grub-core/fs/zfs/zfs.c:1192: label ok 0
  grub-core/osdep/hostdisk.c:394: reusing open device `/dev/sda1'
  grub-core/fs/zfs/zfs.c:1007: check 2 passed
  grub-core/fs/zfs/zfs.c:1018: check 3 passed
  grub-core/fs/zfs/zfs.c:1025: check 4 passed
  grub-core/fs/zfs/zfs.c:1035: check 6 passed
  grub-core/fs/zfs/zfs.c:1043: check 7 passed
  grub-core/fs/zfs/zfs.c:1054: check 8 passed
  grub-core/fs/zfs/zfs.c:1064: check 9 passed
  grub-core/fs/zfs/zfs.c:1086: check 11 passed
  grub-core/fs/zfs/zfs.c:1112: check 10 passed
  grub-core/fs/zfs/zfs.c:1128: str=com.delphix:hole_birth
  grub-core/fs/zfs/zfs.c:1128: str=com.delphix:embedded_data
  grub-core/fs/zfs/zfs.c:1137: check 12 passed (feature flags)
  grub-core/fs/zfs/zfs.c:1875: zio_read: E 0: size 2048/2048
  grub-core/fs/zfs/zfs.c:1898: endian = -1
  grub-core/fs/zfs/zfs.c:595: dva=8, b00258
  grub-core/osdep/hostdisk.c:394: reusing open device `/dev/sda1'
  grub-core/fs/zfs/zfs.c:442: checksum fletcher4 verification failed
  grub-core/fs/zfs/zfs.c:447: actual checksum 0059d95adad1 6322fba304b3 
00430f321ad7f439 21e873b51c15e3bc
  grub-core/fs/zfs/zfs.c:452: expected checksum 00035ca143fb 
062fc3a48ff8 0005b49e0d96b07e 03841abf1fed586a
  grub-core/fs/zfs/zfs.c:1919: incorrect checksum
  grub-core/kern/fs.c:78: zfs detection failed.

  Now here's the fun part.  Rebooting the system will fix the checksum
  issue for a short amount of time.  Here is what it looks like
  immediately after a reboot:

  root@q-1-d.sv1:~# grub-probe /
  zfs

  grub-core/kern/fs.c:56: Detecting zfs...
  grub-core/osdep/hostdisk.c:415: opening the device `/dev/sda1' in 
open_device()
  grub-core/fs/zfs/zfs.c:1192: label ok 0
  grub-core/osdep/hostdisk.c:394: reusing open device `/dev/sda1'
  grub-core/fs/zfs/zfs.c:1007: check 2 passed
  grub-core/fs/zfs/zfs.c:1018: check 3 passed
  grub-core/fs/zfs/zfs.c:1025: check 4 passed
  grub-core/fs/zfs/zfs.c:1035: check 6 passed
  grub-core/fs/zfs/zfs.c:1043: check 7 passed
  grub-core/fs/zfs/zfs.c:1054: check 8 passed
  grub-core/fs/zfs/zfs.c:1064: check 9 passed
  grub-core/fs/zfs/zfs.c:1086: check 11 passed
  grub-core/fs/zfs/zfs.c:1112: check 10 passed
  grub-core/fs/zfs/zfs.c:1128: str=com.delphix:hole_birth
  grub-core/fs/zfs/zfs.c:1128: str=com.delphix:embedded_data
  grub-core/fs/zfs/zfs.c:1137: check 12 passed (feature flags)
  grub-core/fs/zfs/zfs.c:1875: zio_read: E 0: size 2048/2048
  grub-core/fs/zfs/zfs.c:1898: endian = -1
  grub-core/fs/zfs/zfs.c:595: dva=8, c001c0
  grub-core/osdep/hostdisk.c:394: reusing open device `/dev/sda1'
  grub-core/fs/zfs/zfs.c:2678: endian = -1, blkid=0
  grub-core/fs/zfs/zfs.c:2020: endian = -1
  grub-core/fs/zfs/zfs.c:2051: endian = -1
  grub-core/fs/zfs/zfs.c:1875: zio_read: E 0: size 16384/4096
  grub-core/fs/zfs/zfs.c:1898: endian = -1
  grub-core/fs/zfs/zfs.c:595: dva=8, c001b8
  grub-core/osdep/hostdisk.c:394: reusing open device `/dev/sda1'
  grub-core/fs/zfs/zfs.c:2020: endian = 1
  grub-core/fs/zfs/zfs.c:2046: endian = 1
  grub-core/fs/zfs/zfs.c:1875: zio_read: E 0: size 16384/4096
  grub-core/fs/zfs/zfs.c:1898: endian = 1
  grub-core/fs/zfs/zfs.c:595: dva=8, c001a0
  grub-core/fs/zfs/zfs.c:2682: alive
  grub-core/fs/zfs/zfs.c:2493: looking for 'features_for_read'
  grub-core/fs/zfs/zfs.c:2020: endian = 1
  grub-core/fs/zfs/zfs.c:2046: endian = 1
  grub-core/fs/zfs/zfs.c:1875: zio_read: E 0: size 16384/4096
  grub-core/fs/zfs/zfs.c:1898: endian

[Kernel-packages] [Bug 1704479] Re: Change CONFIG_IBMVETH to module

2017-07-20 Thread Manoj Iyer

CONFIG_IBMVETH=y is already set in Zesty (tag Ubuntu-4.10.0-29.33) and
also in artful tip of the tree.

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

Title:
  Change CONFIG_IBMVETH to module

Status in The Ubuntu-power-systems project:
  Triaged
Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Artful:
  Triaged

Bug description:
  == Comment: #0 - Breno Leitao  - 2017-07-14 15:07:47 ==
  Dear Canonical,

  Please change the CONFIG_IBMVETH=y to module on artful kernel.

  Thank you,
  Breno

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

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

[Kernel-packages] [Bug 1704994] Re: linux: 3.13.0-126.175 -proposed tracker

2017-07-20 Thread Kleber Sacilotto de Souza

** Summary changed:

- linux:  -proposed tracker
+ linux: 3.13.0-126.175 -proposed tracker

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

** Changed in: kernel-sru-workflow/prepare-package-signed
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Kleber 
Sacilotto de Souza (kleber-souza)

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

** Changed in: kernel-sru-workflow/prepare-package-meta
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Kleber 
Sacilotto de Souza (kleber-souza)

** Changed in: kernel-sru-workflow/prepare-package
 Assignee: Thadeu Lima de Souza Cascardo (cascardo) => Kleber Sacilotto de 
Souza (kleber-souza)

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

Title:
  linux: 3.13.0-126.175 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  In Progress
Status in Kernel SRU Workflow prepare-package-meta series:
  In Progress
Status in Kernel SRU Workflow prepare-package-signed series:
  In Progress
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in 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: 1704995
  derivatives:

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

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

[Kernel-packages] [Bug 1705447] Re: misleading kernel warning skb_warn_bad_offload during checksum calculation

I built Xenial and Zesty test kernels with commit b2504a5dbef.  The test
kernels can be downloaded from:

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

Can you test these kernels and see if they resolve this bug?

Thanks in advance!

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

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

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

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

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

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

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

Title:
  misleading kernel warning skb_warn_bad_offload during checksum
  calculation

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:
  Even when the packet says checksum calculation is unnecessary the
  kernel will still check the checksum and display a warning that the
  checksum is bad.

  This has been fixed upstream in Kernel 4.11 by commit id:
  b2504a5dbef3305ef41988ad270b0e8ec289331c

  We have reports of Ubuntu 16.04 virtual machines (with ip forward
  enabled) displaying these warnings:

  
  [10480.074664] [ cut here ]
  [10480.074667] WARNING: CPU: 1 PID: 0 at 
/build/linux-hwe-X3pKE5/linux-hwe-4.8.0/net/core/dev.c:2444 
skb_warn_bad_offload+0xd1/0x120
  [10480.074669] docker0: caps=(0x0400ffbb78e9, 0x) 
len=2962 data_len=2834 gso_size=1448 gso_type=5 ip_summed=1
  [10480.074670] Modules linked in: veth nfsv3 nfs_acl rpcsec_gss_krb5 
auth_rpcgss nfsv4 nfs lockd grace sunrpc fscache ipt_MASQUERADE 
nf_nat_masquerade_ipv4 xfrm_user xfrm_algo iptable_nat nf_conntrack_ipv4 
nf_defrag_ipv4 nf_nat_ipv4 xt_addrtype iptable_filter ip_tables xt_conntrack 
x_tables nf_nat nf_conntrack br_netfilter bridge stp llc aufs zfs(PO) 
zunicode(PO) zcommon(PO) znvpair(PO) spl(O) zavl(PO) crct10dif_pclmul 
crc32_pclmul ghash_clmulni_intel aesni_intel aes_x86_64 lrw glue_helper 
ablk_helper cryptd input_leds joydev serio_raw i2c_piix4 mac_hid parport_pc 
ppdev lp parport autofs4 hid_generic usbhid hid virtio_scsi psmouse virtio_net 
pata_acpi floppy
  [10480.074695] CPU: 1 PID: 0 Comm: swapper/1 Tainted: PW  O
4.8.0-52-generic #55~16.04.1-Ubuntu
  [10480.074696] Hardware name: Nutanix AHV, BIOS seabios-1.7.5-11.el6 
04/01/2014
  [10480.074697]  0286 ec176c2ae03bc036 8beef5643870 
b7a2e7b3
  [10480.074699]  8beef56438c0  8beef56438b0 
b768314b
  [10480.074702]  098cb84fba80 8bed61f82000 8bee9915c000 
0005
  [10480.074704] Call Trace:
  [10480.074704][] dump_stack+0x63/0x90
  [10480.074708]  [] __warn+0xcb/0xf0
  [10480.074710]  [] warn_slowpath_fmt+0x5f/0x80
  [10480.074713]  [] ? ___ratelimit+0xa2/0xf0
  [10480.074714]  [] skb_warn_bad_offload+0xd1/0x120
  [10480.074716]  [] __skb_gso_segment+0xd8/0x140
  [10480.074717]  [] validate_xmit_skb+0x14f/0x2a0
  [10480.074719]  [] __dev_queue_xmit+0x322/0x6d0
  [10480.074720]  [] ? nf_nat_ipv4_fn+0x1a6/0x230 
[nf_nat_ipv4]
  [10480.074723]  [] dev_queue_xmit+0x10/0x20
  [10480.074725]  [] ip_finish_output2+0x292/0x380
  [10480.074726]  [] ? ipv4_confirm+0x7d/0x100 
[nf_conntrack_ipv4]
  [10480.074728]  [] ip_finish_output+0x132/0x1d0
  [10480.074729]  [] ? nf_hook_slow+0x73/0xd0
  [10480.074731]  [] ip_output+0x6e/0xf0
  [10480.074733]  [] ? 
__ip_flush_pending_frames.isra.40+0x90/0x90
  [10480.074736]  [] ip_forward_finish+0x43/0x70
  [10480.074738]  [] ip_forward+0x384/0x480
  [10480.074739]  [] ? ip_frag_mem+0x50/0x50
  [10480.074741]  [] ip_rcv_finish+0x11b/0x400
  [10480.074743]  [] ip_rcv+0x28b/0x3c0
  [10480.074744]  [] ? inet_del_offload+0x40/0x40
  [10480.074746]  [] __netif_receive_skb_core+0x524/0xab0
  [10480.074747]  [] ? kmem_cache_alloc+0xd7/0x1b0
  [10480.074749]  [] ? __build_skb+0x2a/0xe0
  [10480.074751]  [] __netif_receive_skb+0x18/0x60
  [10480.074753]  [] netif_receive_skb_internal+0x32/0xa0
  [10480.074754]  [] napi_gro_receive+0xcd/0x120
  [10480.074756]  [] virtnet_receive+0x1c3/0x970 [virtio_net]
  [10480.074758]  [] ? update_cfs_rq_load_avg+0x1f9/0x4c0
  [10480.074760]  [] virtnet_poll+0x1d/0x80 [virtio_net]
  [10480.074762]  [] net_rx_action+0x238/0x380
  [10480.074764]  [] __do_softirq+0xf6/0x280
  [10480.074765]  [] irq_exit+0xa3/0xb0
  [10480.074766]  [] do_IRQ+0x54/0xd0
  [10480.074768]  [] common_interrupt+0x82/0x82
  [10480.074768][] ? native_safe_halt+0x6/0x10
  [10480.074772]  [] default_idle+0x1e/0xd0
  [10480.074774]  [] arch_cpu_idle+0xf/0x20
  [10480.074775]  []

[Kernel-packages] [Bug 1615405] Re: zfs share doesn't work

I've asked for an update on the status of this big in the zfs bug
tracker as it seems to have gone no where.

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

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

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

Title:
  zfs share doesn't work

Status in Native ZFS for Linux:
  Unknown
Status in zfs-linux package in Ubuntu:
  Triaged

Bug description:
  I'm testing on Ubuntu 16.04 with the included zol 0.6.5.

  I have also reported this bug here:
  https://github.com/zfsonlinux/zfs/issues/4999

  zfs share and zfs share -a just don't work. zfs set sharesmb=on
  pool/dataset works fine. I discovered that the shares are listed in
  /etc/dfs/sharetab but don't work. If I reboot or anything and try to
  share them again with zfs share, it will not work. net usershare list
  displays nothing. And of course because of this all shares are lost on
  every reboot.

  Despite a dataset having the sharesmb=on value set, it will not share
  with zfs share -a and if I use zfs share pool/dataset it says: cannot
  share 'pool/dataset': filesystem already shared, when net usershare
  list shows nothing**. Samba is running and the shares appear in
  /etc/dfs/sharetab, not that that is helping me.

  I've detailed a bunch of stuff at serverfault... if that's not good
  enough, I can bring some of it over here:

  http://serverfault.com/questions/797938/ubuntu-xenial-16-04-zfs-share-
  command-doesnt-work-for-smb-shares

  System/package informatiom

  zfsutils-linux:
Installed: 0.6.5.6-0ubuntu12
Candidate: 0.6.5.6-0ubuntu12
Version table:
   *** 0.6.5.6-0ubuntu12 500
  500 http://ca.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   0.6.5.6-0ubuntu8 500
  500 http://ca.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages

  Description:Ubuntu 16.04.1 LTS
  Release:16.04

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: zfsutils-linux 0.6.5.6-0ubuntu12
  ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15
  Uname: Linux 4.4.0-34-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Sun Aug 21 12:11:47 2016
  InstallationDate: Installed on 2016-05-26 (87 days ago)
  InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.3)
  SourcePackage: zfs-linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.default.zfs: [modified]
  mtime.conffile..etc.default.zfs: 2016-07-12T22:45:19.830513

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

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

[Kernel-packages] [Bug 1704961] Re: linux: 4.10.0-29.33 -proposed tracker

2017-07-20 Thread Steve Beattie

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

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

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

Title:
  linux: 4.10.0-29.33 -proposed tracker

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

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

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

  backports: 1704962,1704964
  derivatives: 1704966
  -- 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/1704961/+subscriptions

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

[Kernel-packages] [Bug 1697132] Re: CPU Cores Stalls/Lock

It maybe also worth stress testing your hardware with tools such as stress-ng 
to try and coerce issues like this out. See: 
http://kernel.ubuntu.com/~cking/stress-ng/
 

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

** Changed in: zfs-linux (Ubuntu)
 Assignee: (unassigned) => Colin Ian King (colin-king)

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

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

Title:
  CPU Cores Stalls/Lock

Status in linux package in Ubuntu:
  Confirmed
Status in zfs-linux package in Ubuntu:
  Triaged

Bug description:
  CPU Stalls or Locks up after a random period of time. Can not trace
  issue to high resources or heat. System will crash while sitting
  essentially idle. Sometimes system will crash after a few minutes some
  times it will take days. A large file transfer will usually force the
  crash though.

  I have been having similar issue since Ubuntu 14.04. I have upgrade to
  every version along the way to 17.04 with the same issue. I have
  replaced every piece of hardware except HDD. MB, Proc, power supply,
  memory, video card. With and without AMD micro code. This is a server
  so no GUI.

  I've tried upstream kernels but they don't support ZFS and I haven't
  had any luck shimming it in. Happy to try newer kernels if someone can
  provide one with ZFS support.

  
  Jun  9 18:54:57 TheSource kernel: [46465.931527] INFO: rcu_sched detected 
stalls on CPUs/tasks:
  Jun  9 18:54:57 TheSource kernel: [46465.931583]9-...: (12 GPs 
behind) idle=f03/1/0 softirq=261811/261811 fqs=6599
  Jun  9 18:54:57 TheSource kernel: [46465.931624](detected by 0, 
t=15002 jiffies, g=380049, c=380048, q=118270)
  Jun  9 18:54:57 TheSource kernel: [46465.931665] Task dump for CPU 9:
  Jun  9 18:54:57 TheSource kernel: [46465.931666] swapper/9   R  running 
task0 0  1 0x0008
  Jun  9 18:54:57 TheSource kernel: [46465.931670] Call Trace:
  Jun  9 18:54:57 TheSource kernel: [46465.931677]  ? 
cpuidle_enter_state+0x122/0x2c0
  Jun  9 18:54:57 TheSource kernel: [46465.931680]  ? 
cpuidle_enter_state+0x110/0x2c0
  Jun  9 18:54:57 TheSource kernel: [46465.931683]  ? cpuidle_enter+0x17/0x20
  Jun  9 18:54:57 TheSource kernel: [46465.931685]  ? call_cpuidle+0x23/0x40
  Jun  9 18:54:57 TheSource kernel: [46465.931688]  ? do_idle+0x189/0x200
  Jun  9 18:54:57 TheSource kernel: [46465.931690]  ? 
cpu_startup_entry+0x71/0x80
  Jun  9 18:54:57 TheSource kernel: [46465.931693]  ? 
start_secondary+0x154/0x190
  Jun  9 18:54:57 TheSource kernel: [46465.931696]  ? start_cpu+0x14/0x14

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-19-generic 4.10.0-19.21
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.10.0-19-generic.
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.4-0ubuntu4.1
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/hwC0D0', 
'/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/controlC0', 
'/dev/snd/by-path', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D2c', 
'/dev/snd/pcmC1D1p', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', 
'/dev/snd/controlC1', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer'
  Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer'
  Card1.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer'
  Card1.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer'
  Date: Fri Jun  9 20:17:45 2017
  InstallationDate: Installed on 2017-06-03 (6 days ago)
  InstallationMedia: Ubuntu-Server 17.04 "Zesty Zapus" - Release amd64 
(20170412)
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  MachineType: Micro-Star International Co., Ltd MS-7A32
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-19-generic 
root=UUID=bba67c63-3cd9-4475-bf3a-a0890087330d ro
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-19-generic N/A
   linux-backports-modules-4.10.0-19-generic  N/A
   linux-firmware 1.164.1
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/27/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.50
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: X370 GAMING PRO CARBON (MS-7A32)
  dmi.board.vendor:

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

2017-07-20 Thread Bib

Hi Joseph
I don't know how to do that as the need for nomodeset seems to be required from 
LiveUSB 14.04.5, i.e. my yet installed system is running 14.04.5 without 
nomodeset in /etc/default/grub.
Whatever I gave a try to 4.13-rc1 on my system and it could start when selected 
from grub menu without requiring nomodeset. Please feel free to set tags as you 
feel it's best, but this test doesn't say why LiveUSB XU16 and U17.04amd64 
failed... maybe I didn't hit ESC on them to get the usual menu so I couldn't 
have the idea to come back for nomodeset...
I'll try to see, redoing the stick.
Bye

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

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

Status in linux package in Ubuntu:
  Incomplete

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

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

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

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

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

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

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

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

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

2017-07-20 Thread Bib

Hi Joseph
I don't know how to do that as the need for nomodeset seems to be required from 
LiveUSB 14.04.5, i.e. my yet installed system is running 14.04.5 without 
nomodeset in /etc/default/grub.
Whatever I gave a try to 4.13-rc1 on my system and it could start when selected 
from grub menu without requiring nomodeset. Please feel free to set tags as you 
feel it's best, but this test doesn't say why LiveUSB XU16 and U17.04amd64 
failed... maybe I didn't hit ESC on them to get the usual menu so I could have 
the idea to come back for nomodeset...
I'll try to see, redoing the stick.
Bye

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

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

Status in linux package in Ubuntu:
  Incomplete

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

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

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

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

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

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

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

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

[Kernel-packages] [Bug 1704982] Re: linux: 4.4.0-87.110 -proposed tracker

** Changed in: kernel-sru-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/1704982

Title:
  linux: 4.4.0-87.110 -proposed tracker

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

Bug description:
  This bug is for tracking the  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: 1704985
  derivatives: 1704987,1704989,1704990,1704991
  -- 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/1704982/+subscriptions

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

[Kernel-packages] [Bug 1705507] Re: linux-aws: 4.4.0-1026.35 -proposed tracker

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

** Description changed:

  This bug is for tracking the 4.4.0-1026.35 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
+ 
+ kernel-stable-phase-changed:Thursday, 20. July 2017 15:31 UTC
+ kernel-stable-phase:Packaging

** Description changed:

  This bug is for tracking the 4.4.0-1026.35 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
  
  kernel-stable-phase-changed:Thursday, 20. July 2017 15:31 UTC
  kernel-stable-phase:Packaging
+ 
+ -- swm properties --
+ phase: Packaging

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

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

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

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

  kernel-stable-phase-changed:Thursday, 20. July 2017 15:31 UTC
  kernel-stable-phase:Packaging

  -- swm properties --
  phase: Packaging

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

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

[Kernel-packages] [Bug 1698363] Re: zfs-dkms 0.6.5.6-0ubuntu17: zfs kernel module failed to build

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

** This bug has been marked a duplicate of bug 1683340
   zfs-dkms 0.6.5.9-5ubuntu4: zfs kernel module failed to build [make: *** No 
targets specified and no makefile found. Stop.]

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

Title:
  zfs-dkms 0.6.5.6-0ubuntu17: zfs kernel module failed to build

Status in zfs-linux package in Ubuntu:
  Incomplete

Bug description:
  Performing system updates, not a user of zfs (at this point). Packages
  just failed to install.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: zfs-dkms 0.6.5.6-0ubuntu17
  ProcVersionSignature: Ubuntu 4.4.0-79.100-generic 4.4.67
  Uname: Linux 4.4.0-79-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  DKMSBuildLog:
   DKMS make.log for zfs-0.6.5.6 for kernel 4.4.0-79-generic (x86_64)
   Fri Jun 16 07:19:28 CDT 2017
   make: *** No targets specified and no makefile found.  Stop.
  DKMSKernelVersion: 4.4.0-79-generic
  Date: Fri Jun 16 07:19:32 2017
  InstallationDate: Installed on 2014-10-19 (971 days ago)
  InstallationMedia: Xubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140723)
  PackageVersion: 0.6.5.6-0ubuntu17
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: zfs-linux
  Title: zfs-dkms 0.6.5.6-0ubuntu17: zfs kernel module failed to build
  UpgradeStatus: Upgraded to xenial on 2016-04-22 (420 days ago)

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

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

[Kernel-packages] [Bug 1702164] Re: Kernel panic - not syncing: Fatal exception in interrupt

2017-07-20 Thread John Fanjoy

We are also seeing relatively frequent kernel panics using 4.4.0-83. We
run an Apache Mesos cluster using the docker containerizer. The
description of LP #1687512 appears to match quite nicely with our
configuration (cgroups enabled with small allocations). That issue
appears to have been addressed in 4.4.0-79, but perhaps this is related.

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

Title:
  Kernel panic - not syncing: Fatal exception in interrupt

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  we updated Kernel of Ubuntu 16.04 from 4.4.0-81-generic to
  generic_4.4.0-83.106 we had multiple reboots, and below appeared
  during the boot :

  [231489.162816] Kernel panic - not syncing: Fatal exception in interrupt
  [231490.197513] Shutting down cpus with NMI
  [231490.210772] Kernel Offset: disabled
  [0.00] Initializing cgroup subsys cpuset
  [0.00] Initializing cgroup subsys cpu
  [0.00] Initializing cgroup subsys cpuacct
  [0.00] Linux version 4.4.0-83-generic (buildd@lgw01-29) (gcc version 
5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.4) ) #106-Ubuntu SMP Mon Jun 26 
17:54:43 UTC 2017 (Ubuntu 4.4.0-83.106-generic 4.4.70)
  [0.00] Command line: BOOT_IMAGE=/boot/vmlinuz-4.4.0-83-generic 
root=UUID=e675b47c-3493-4ef8-8b6f-44acb3d1adb9 ro net.ifnames=0 biosdevname=0 
cgroup_enable=memory swapaccount=1 console=tty1 console=ttyS0
  [0.00] KERNEL supported cpus:
  [0.00]   Intel GenuineIntel
  [0.00]   AMD AuthenticAMD
  [0.00]   Centaur CentaurHauls
  [0.00] x86/fpu: xstate_offset[2]:  576, xstate_sizes[2]:  256
  [0.00] x86/fpu: Supporting XSAVE feature 0x01: 'x87 floating point 
registers'
  [0.00] x86/fpu: Supporting XSAVE feature 0x02: 'SSE registers'
  [0.00] x86/fpu: Supporting XSAVE feature 0x04: 'AVX registers'
  [0.00] x86/fpu: Enabled xstate features 0x7, context size is 832 
bytes, using 'standard' format.
  [0.00] x86/fpu: Using 'eager' FPU context switches.
  [0.00] e820: BIOS-provided physical RAM map:
  [0.00] BIOS-e820: [mem 0x-0x0009dfff] usable
  [0.00] BIOS-e820: [mem 0x0009e000-0x0009] reserved
  [0.00] BIOS-e820: [mem 0x000e-0x000f] reserved
  [0.00] BIOS-e820: [mem 0x0010-0x7fff] usable
  [0.00] BIOS-e820: [mem 0xfc00-0x] reserved
  [0.00] BIOS-e820: [mem 0x0001-0x00f47fff] usable
  [0.00] NX (Execute Disable) protection: active
  [0.00] SMBIOS 2.4 present.
  [0.00] Hypervisor detected: Xen
  [0.00] Xen version 4.2.
  [0.00] Netfront and the Xen platform PCI driver have been compiled 
for this kernel: unplug emulated NICs.
  [0.00] Blkfront and the Xen platform PCI driver have been compiled 
for this kernel: unplug emulated disks.
  [0.00] You might have to change the root device
  [0.00] from /dev/hd[a-d] to /dev/xvd[a-d]
  [0.00] in your root= kernel command line option
  [0.00] e820: last_pfn = 0xf48 max_arch_pfn = 0x4
  [0.00] x86/PAT: Configuration [0-7]: WB  WC  UC- UC  WB  WC  UC- WT  
  [0.00] e820: last_pfn = 0x8 max_arch_pfn = 0x4
  [0.00] found SMP MP-table at [mem 0x000fbc20-0x000fbc2f] mapped at 
[880fbc20]
  [0.00] Scanning 1 areas for low memory corruption
  [0.00] Using GB pages for direct mapping
  [0.00] RAMDISK: [mem 0x3612a000-0x3708cfff]
  [0.00] ACPI: Early table checksum verification disabled
  [0.00] ACPI: RSDP 0x000EA020 24 (v02 Xen   )
  [0.00] ACPI: XSDT 0xFC014140 5C (v01 XenHVM  
 HVML )
  [0.00] ACPI: FACP 0xFC0131A0 F4 (v04 XenHVM  
 HVML )
  [0.00] ACPI: DSDT 0xFC001CE0 011438 (v02 XenHVM  
 INTL 20090123)
  [0.00] ACPI: FACS 0xFC001CA0 40
  [0.00] ACPI: FACS 0xFC001CA0 40
  [0.00] ACPI: APIC 0xFC0132A0 000460 (v02 XenHVM  
 HVML )
  [0.00] ACPI: SRAT 0xFC013780 0008A8 (v01 XenHVM  
 HVML )
  [0.00] ACPI: HPET 0xFC014050 38 (v01 XenHVM  
 HVML )
  [0.00] ACPI: WAET 0xFC014090 28 (v01 XenHVM  
 HVML )
  [0.00] ACPI: SSDT 0xFC0140C0 31 (v02 XenHVM  
 INTL 20090123)
  [0.00] ACPI: SSDT 0xFC014100 31 (v02 XenHVM  
 INTL 20090123)
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jul  3 08:14 seq
   crw-rw 1 root

[Kernel-packages] [Bug 1705507] [NEW] linux-aws: 4.4.0-1026.35 -proposed tracker

2017-07-20 Thread Thadeu Lima de Souza Cascardo

Public bug reported:

This bug is for tracking the 4.4.0-1026.35 upload package. This bug will
contain status and testing results related to that upload.

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

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

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

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

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

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

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

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

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

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

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

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

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

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


** Tags: block-proposed-xenial kernel-release-tracking-bug 
kernel-release-tracking-bug-live kernel-sru-cycle-2017.06.28-5 xenial

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

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

** Tags added: block-proposed-xenial

** Tags added: xenial

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

** Changed in: kernel-sru-workflow/promote-to-security

[Kernel-packages] [Bug 1704982] Re: linux: 4.4.0-87.110 -proposed tracker

2017-07-20 Thread Kleber Sacilotto de Souza

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

Title:
  linux: 4.4.0-87.110 -proposed tracker

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

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

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

  backports: 1704985
  derivatives: 1704987,1704989,1704990,1704991
  -- 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/1704982/+subscriptions

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

[Kernel-packages] [Bug 1705493] Re: [4.4][backport] Multiple partitions are not supported on a bcache device

I built a Xenial test kernel with commit b8c0d911ac528.  The test kernel
can be downloaded from:

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

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

Thanks in advance!

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

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

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

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

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

Title:
  [4.4][backport] Multiple partitions are not supported on a bcache
  device

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

Bug description:
  Support for adding partitions on bcache devices only landed in 4.10:

  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=b8c0d911ac5285e6be8967713271a51bdc5a936a

  Although it is a small change, it is not backported to any of the
  xenial kernels and it only exists naturally in 4.10.

  ➜ ubuntu-xenial git:(master) git tag 
--contains=b8c0d911ac5285e6be8967713271a51bdc5a936a
  Ubuntu-hwe-4.10.0-13.15_16.04.2
  Ubuntu-hwe-4.10.0-14.16_16.04.1
  Ubuntu-hwe-4.10.0-19.21_16.04.1
  Ubuntu-hwe-4.10.0-20.22_16.04.1
  Ubuntu-hwe-4.10.0-21.23_16.04.1
  Ubuntu-hwe-4.10.0-22.24_16.04.1
  Ubuntu-hwe-4.10.0-25.29_16.04.1
  Ubuntu-hwe-4.10.0-26.30_16.04.1
  Ubuntu-hwe-4.10.0-28.32_16.04.1
  Ubuntu-hwe-edge-4.10.0-9.11_16.04.2
  Ubuntu-lts-4.10.0-10.12_16.04.1
  Ubuntu-lts-4.10.0-11.13_16.04.1
  Ubuntu-lts-4.10.0-12.14_16.04.1
  Ubuntu-lts-4.10.0-13.15_16.04.1
  Ubuntu-lts-4.10.0-7.9_16.04.1
  Ubuntu-lts-4.10.0-8.10_16.04.1
  Ubuntu-lts-4.10.0-9.11_16.04.1
  Ubuntu-lts-4.10.0-9.11_16.04.2

  This will prevent usage of multiple partitions on the same device
  which is the case when data and journal are collocated.

  Also, the lack of that feature prevents dmcrypt usage as multiple
  partitions are created on a device in this case.

  
  Could that be backported to the 4.4 kernel?

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

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

[Kernel-packages] [Bug 1683340] Re: zfs-dkms 0.6.5.9-5ubuntu4: zfs kernel module failed to build [make: *** No targets specified and no makefile found. Stop.]

OK, this looks like that a new ZFS in being installed against the old
kernel and this causes the initial old zfs dkms build to fail against
the older kernel headers, and then when the new headers of the new
kernel with the new zfs are installed this gets rectified. So as long as
ZFS is OK at the end of this, I believe this is nothing to get too
concerned about.

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

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

Title:
  zfs-dkms 0.6.5.9-5ubuntu4: zfs kernel module failed to build [make:
  *** No targets specified and no makefile found. Stop.]

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

Bug description:
  zfs-dkms 0.6.5.9-5ubuntu4: zfs kernel module failed to build

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: zfs-dkms 0.6.5.9-5ubuntu4
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair nvidia_drm 
nvidia_modeset nvidia
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  DKMSBuildLog:
   DKMS make.log for zfs-0.6.5.9 for kernel 4.10.0-19-generic (x86_64)
   luni 17 aprilie 2017, 14:43:07 +0300
   make: *** No targets specified and no makefile found.  Stop.
  DKMSKernelVersion: 4.10.0-19-generic
  Date: Mon Apr 17 14:43:08 2017
  InstallationDate: Installed on 2016-10-19 (180 days ago)
  InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  PackageArchitecture: all
  PackageVersion: 0.6.5.9-5ubuntu4
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  SourcePackage: zfs-linux
  Title: zfs-dkms 0.6.5.9-5ubuntu4: zfs kernel module failed to build
  UpgradeStatus: Upgraded to zesty on 2017-04-17 (0 days ago)

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

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

[Kernel-packages] [Bug 1704982] Re: linux: 4.4.0-87.110 -proposed tracker

2017-07-20 Thread Kleber Sacilotto de Souza

HW-certification tests completed this cycle with for xenial with 
linux-image-4.4.0-84-generic==4.4.0-84.107:
http://people.canonical.com/~hwcert/sru-testing/xenial/4.4.0-84.107/xenial-proposed.html

** Changed in: kernel-sru-workflow/certification-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/1704982

Title:
  linux: 4.4.0-87.110 -proposed tracker

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

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

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

  backports: 1704985
  derivatives: 1704987,1704989,1704990,1704991
  -- 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/1704982/+subscriptions

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

[Kernel-packages] [Bug 1705349] Re: tgtd blocked with hitting hung_task_timeout_secs

2017-07-20 Thread Bjoern Teipel

That issue did seem to be load induced, nothing has changed on the
system side since we did not update any packages. We will update the
kernel to the latest trusty first and if it still persists to either the
xenial kernel or newer

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

Title:
  tgtd blocked with hitting hung_task_timeout_secs

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  
  We see an issue where an IO thread of tgtd violates the hung task timeout and 
vmstat reports >20% wait on IO while we are not seeing a issue with the 
underlying hardware (iowait and svc time) inside IO stat. 

  We already limited the kernel parameters

  vm.dirty_background_ratio=5
  vm.dirty_ratio=10

  to reduce the impact of massive dirty blocks hitting the storage which
  is still based on spinning rust in a RAID 10 array.

  
  This is based on kernel 3.13.0-96-generic with the deadline IO scheduler and 
we got the following stack trace:

  
  [25300644.048029] INFO: task tgtd:27827 blocked for more than 300 seconds.
  [25300644.048065]   Not tainted 3.13.0-96-generic #143-Ubuntu
  [25300644.048100] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [25300644.048166] tgtdD 88103fc13180 0 27827  1 
0x0080
  [25300644.048168]  88019cc61c78 0086 880125791800 
00013180
  [25300644.048171]  88019cc61fd8 00013180 880125791800 
88103fc13a18
  [25300644.048173]  88207ffef6e8 88019cc61d00 0002 
81151e90
  [25300644.048176] Call Trace:
  [25300644.048178]  [] ? wait_on_page_read+0x60/0x60
  [25300644.048190]  [] io_schedule+0x9d/0x130
  [25300644.048192]  [] sleep_on_page+0xe/0x20
  [25300644.048194]  [] __wait_on_bit_lock+0x48/0xb0
  [25300644.048196]  [] __lock_page+0x6a/0x70
  [25300644.048198]  [] ? autoremove_wake_function+0x40/0x40
  [25300644.048200]  [] write_cache_pages+0x2f8/0x4b0
  [25300644.048202]  [] ? global_dirtyable_memory+0x50/0x50
  [25300644.048205]  [] ? get_futex_key+0x1d8/0x2c0
  [25300644.048207]  [] ? send_signal+0x3e/0x80
  [25300644.048209]  [] generic_writepages+0x40/0x60
  [25300644.048212]  [] do_writepages+0x1e/0x40
  [25300644.048213]  [] __filemap_fdatawrite_range+0x59/0x60
  [25300644.048215]  [] filemap_write_and_wait_range+0x2a/0x70
  [25300644.048217]  [] blkdev_fsync+0x1b/0x50
  [25300644.048219]  [] do_fsync+0x51/0x80
  [25300644.048221]  [] SyS_fdatasync+0x13/0x20
  [25300644.048223]  [] system_call_fastpath+0x1a/0x1f


  UPTIME report
   16:30:01 up 292 days, 22:34,  0 users,  load average: 9.89, 8.58, 5.33

  FREE report
   total   used   free sharedbuffers cached
  Mem: 131777272  116935780   14841492828  1106297401123368
  -/+ buffers/cache:5182672  126594600
  Swap:  7999484   90047990480

  VMSTAT report
  procs ---memory-- ---swap-- -io -system-- 
--cpu-
   r  b   swpd   free   buff  cache   si   sobibo   in   cs us sy id wa 
st
   0 10  8  14493 108036   109700 7   22700  0  0 100  
0  0
   0 10  8  14494 108036   109700 0 0  690 1149  0  0 78 22 
 0
   0 10  8  14494 108036   109700 0 8  736 1442  0  0 78 22 
 0

  IOSTAT report
  Linux 3.13.0-96-generic (cinder18)   07/19/2017  _x86_64_(32 
CPU)

  07/19/2017 04:30:03 PM
  avg-cpu:  %user   %nice %system %iowait  %steal   %idle
 0.350.000.080.070.00   99.50

  
  Device: rrqm/s   wrqm/s r/s w/srkB/swkB/s avgrq-sz 
avgqu-sz   await r_await w_await  svctm  %util
  sda   0.00 3.970.40   10.89 1.7563.1611.51
 0.000.160.130.16   0.01   0.01
  sdb  51.40   107.252.20   15.89   215.29  7198.82   819.79
 0.073.893.263.97   0.60   1.08
  sdc   0.00 0.000.000.00 0.00 0.00 8.00
 0.000.110.110.00   0.11   0.00
  dm-0  0.00 0.000.000.00 0.00 0.01 8.00
 0.00   11.760.66   14.98   0.17   0.00
  dm-1  0.00 0.000.01   14.86 0.1963.13 8.52
 0.000.153.100.15   0.00   0.01
  dm-2  0.00 0.000.000.00 0.03 0.0213.67
 0.001.071.660.69   0.47   0.00
  dm-18 0.00 0.000.000.00 0.00 0.00 8.00
 0.003.513.514.00   3.51   0.00
  dm-10 0.00 0.000.010.00 0.02 0.00 8.00
 0.001.761.760.00   0.41   0.00
  dm-28 0.00 0.000.000.02 0.00 0.06 8.00
 0.001.395.761.20   0.06   0.00
  dm-29 0.00 0.000.000.00 0.00

[Kernel-packages] [Bug 1566400] Re: Ubuntu 16.04 testing with PMC 12GB Series 8 adapter with MaxView RAID Migration deletes the RAID array.

2017-07-20 Thread Douglas Miller

The corresponding bug for this issue has been closed as unreproducible.
Unclear why that was not communicated here. This launchpad can also be
closed.

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

Title:
  Ubuntu 16.04 testing with PMC 12GB Series 8 adapter with MaxView RAID
  Migration deletes the RAID array.

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

Bug description:
   State: Open by: nauahmed on 17 March 2016 16:09:48 

  Hi,

  While using MaxView Storage Manager on Ubuntu 16.04 
  from 
https://w3-connections.ibm.com/communities/service/html/communitystart?communityUuid=7bb2d98d-64aa-437d-863e-db67dc1f50db
  
https://w3-connections.ibm.com/wikis/home?lang=en-us#!/wiki/W6ee916ce65bf_4973_a6c3_a0f025d8acc6/page/PMC%20Adapter%20Series%207%20and%20Series%208%20Code%20Deliveries

  PostGA_2.zip
  https://w3-connections.ibm.com/files/form/anonymous/api/library/c5f8d539
  -710e-4e26-9d2f-5073644c8c67/document/f9b22e38-4b5e-46ab-94ca-
  f5cb80b9e13d/media/PostGA_2.zip

  with Expand/Migrate Logical Drive option in web GUI menu.
  whole array is lost. 

  Steps:
  1> INITIALIZE ALL disks # arcconf task start 1 device all INITIALIZE noprompt

  Controllers found: 1
  Initializing Channel 0, Device 9.
  Initializing Channel 0, Device 12.
  Initializing Channel 0, Device 13.
  Initializing Channel 0, Device 14.
  4 device(s) initialized.

  Command completed successfully.

  2> Login to Web gui of MSM.. 
  clink on controller --> create logical device ---> custom mode -->RAID 1  
Mirroring; 2 drives required; redundant ---> select minimum two drives ---> 
next ---> finish. 

  3> Click on new logical raid1 device, click expand/migrate logical
  device

  RAID1
  Select a RAID level and click 'Next' to continue
Select raid Level
RAID Members
Set Attributes
Summary
RAID 1  Mirroring,2 drives required, redundant
RAID 5  Striping with parity,3 or more drives required, redundant
Simple Volume   A single drive segment,not redundant 

  Select RAID5, add additional drive, next, Finish,

  Existing RAID 1 logical device is lost.. there is no migration <-- ALL
  data lost...

  root@p7pran04:~# uname -a
  Linux p7pran04 4.4.0-12-generic #28-Ubuntu SMP Wed Mar 9 00:40:38 UTC 2016 
ppc64le ppc64le ppc64le GNU/Linux
  root@p7pran04:~# arcconf getversion
  Controllers found: 1
  Controller #1
  ==
  Firmware   : 7.8-0 (32968)
  Staged Firmware: 7.8-0 (32968)
  BIOS   : 7.8-0 (32968)
  Driver : 1.2-1 (41010)
  Boot Flash : 7.8-1 (32968)
  CPLD (Load version/ Flash version) : 5/ 10
  SEEPROM (Load version/ Flash version)  : 1/ 1
  root@p7pran04:~# modinfo aacraid
  filename:   
/lib/modules/4.4.0-12-generic/kernel/drivers/scsi/aacraid/aacraid.ko
  version:1.2-1[41010]-ms
  license:GPL
  description:Dell PERC2, 2/Si, 3/Si, 3/Di, Adaptec Advanced Raid Products, 
HP NetRAID-4M, IBM ServeRAID & ICP SCSI driver
  author: Red Hat Inc and Adaptec
  srcversion: FE59F41215F9D0437EA29CE
  alias:  pci:v9005d028Fsv*sd*bc*sc*i*
  alias:  pci:v9005d028Dsv*sd*bc*sc*i*
  alias:  pci:v9005d028Csv*sd*bc*sc*i*
  alias:  pci:v9005d028Bsv*sd*bc*sc*i*
  alias:  pci:v9005d0288sv*sd*bc*sc*i*
  alias:  pci:v9005d0286sv*sd*bc*sc*i*
  alias:  pci:v9005d0285sv*sd*bc*sc*i*
  alias:  pci:v9005d0285sv17AAsd*bc*sc*i*
  alias:  pci:v9005d0285sv1028sd*bc*sc*i*
  alias:  pci:v1011d0046sv103Csd10C2bc*sc*i*
  alias:  pci:v1011d0046sv9005sd1364bc*sc*i*
  alias:  pci:v1011d0046sv9005sd0364bc*sc*i*
  alias:  pci:v1011d0046sv9005sd0365bc*sc*i*
  alias:  pci:v9005d0285sv1028sd0287bc*sc*i*
  alias:  pci:v9005d0286sv9005sd02A2bc*sc*i*
  alias:  pci:v9005d0285sv9005sd029Abc*sc*i*
  alias:  pci:v9005d0285sv9005sd0299bc*sc*i*
  alias:  pci:v9005d0285sv9005sd0298bc*sc*i*
  alias:  pci:v9005d0286sv1014sd9540bc*sc*i*
  alias:  pci:v9005d0286sv1014sd9580bc*sc*i*
  alias:  pci:v9005d0285sv1014sd0312bc*sc*i*
  alias:  pci:v9005d0285sv1014sd02F2bc*sc*i*
  alias:  pci:v9005d0285sv9005sd0297bc*sc*i*
  alias:  pci:v9005d0285sv9005sd0296bc*sc*i*
  alias:  pci:v9005d0285sv103Csd3227bc*sc*i*
  alias:

[Kernel-packages] [Bug 1599599] Re: System beep broken (again) in Xenial Xerus

2017-07-20 Thread bam

Hi Anthony,
have you "echo -e '\a'" working in Ubuntu X11 Terminal?
The only way I could get beeper sound in X11 is 'beep' command.
But in virtual consoles, all the methods work.
So maybe it's too early to set this bug as Fixed?

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

Title:
System beep broken (again) in Xenial Xerus

Status in linux package in Ubuntu:
Fix Released

Bug description:
This is my first ever bug report, so bear with me if I make mistakes.

System bell (aka PC speaker beep) is not working upon installing
Ubuntu 16.04 Xenial Xerus.

The "beep" command has been installed and works, also "echo foo |
wall" works. But "echo -e '\a'" and "printf '\a'" make no sound, nor
does pressing the rubout or other keys in terminal and Gedit like it
usually does.

lsmod shows pcspkr is loaded

Note
The symptoms are exactly the same as in bug #486154
https://bugs.launchpad.net/ubuntu/+source/linux-lts-xenial/+bug/486154

Just for the record, rmmod and reloading the pcspkr module,
unblacklisting it, trying in vain to turn up the volume, and all the
other usual steps are no longer relevant at this point. We are way
beyond that here. Something very, very elusive in this 16.04 distro is
blocking the bell. I suspect something new in 16.04 runs after you
login which nullifies the standard error beep. Pressing down at the
end in Gedit and the terminal also used to make the beep, but
something is telling it not to anymore. The PC speaker works of
course, as the alternative beep command and "echo foo | wall" prove.

Interestingly, Ubuntu can and does produce the system beep in two other
instances:
1) Edit the grub menu at /etc/default /grub and remove the # hash at
GRUB_INIT_TUNE="480 440 1" and you will get a beep when grub loads.
2) Press Backspace without entering your password at login, and you will get
the error beep.

Description: Ubuntu 16.04 LTS
Release: 16.04

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-28-generic 4.4.0-28.47
ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13
Uname: Linux 4.4.0-28-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: dv430uuyn 1784 F pulseaudio
/dev/snd/controlC0: dv430uuyn 1784 F pulseaudio
CurrentDesktop: Unity
Date: Wed Jul 6 14:00:50 2016
HibernationDevice: RESUME=UUID=e8206eff-651f-4207-b0a8-9c5a06959711
InstallationDate: Installed on 2016-06-24 (12 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64
(20160420.1)
IwConfig:
enp2s0no wireless extensions.

lono wireless extensions.
MachineType: Dell Inc. Vostro 430
ProcFB: 0 nouveaufb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-28-generic
root=UUID=c3a8f971-548b-4666-b865-6bf917bef1c9 ro quiet splash vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-4.4.0-28-generic N/A
linux-backports-modules-4.4.0-28-generic N/A
linux-firmware1.157.2
RfKill:

SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/13/2011
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 2.4.0
dmi.board.name: 054KM3
dmi.board.vendor: Dell Inc.
dmi.board.version: A01
dmi.chassis.type: 3
dmi.chassis.vendor: Dell Inc.
dmi.modalias:
dmi:bvnDellInc.:bvr2.4.0:bd01/13/2011:svnDellInc.:pnVostro430:pvr00:rvnDellInc.:rn054KM3:rvrA01:cvnDellInc.:ct3:cvr:
dmi.product.name: Vostro 430
dmi.product.version: 00
dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1705466] Re: Kernel oopsed when booting

2017-07-20 Thread Will Cooke

So far it was a one off, if I can make it happen again I'll report back.

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

Title:
  Kernel oopsed when booting

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

Bug description:
  Spoke to Leann and she suggested that I log this.

  Artful running proposed.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.11.0-11-generic 4.11.0-11.16
  ProcVersionSignature: Ubuntu 4.11.0-11.16-generic 4.11.10
  Uname: Linux 4.11.0-11-generic x86_64
  ApportVersion: 2.20.5-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 1870 F pulseaudio
  CurrentDesktop: GNOME
  Date: Thu Jul 20 13:14:48 2017
  InstallationDate: Installed on 2017-07-10 (10 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170709)
  MachineType: Dell Inc. Inspiron 11-3168
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.11.0-11-generic.efi.signed 
root=UUID=02673bea-6091-48ee-8a1f-44d3ea4b71ce ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.11.0-11-generic N/A
   linux-backports-modules-4.11.0-11-generic  N/A
   linux-firmware 1.167
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/24/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.0.1
  dmi.board.name: 0XKKP9
  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.:bvr1.0.1:bd03/24/2016:svnDellInc.:pnInspiron11-3168:pvr1.0.1:rvnDellInc.:rn0XKKP9:rvrA00:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.name: Inspiron 11-3168
  dmi.product.version: 1.0.1
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1557751] Re: makedumpfile generates kernel version error

2017-07-20 Thread Manoj Iyer

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

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

Title:
  makedumpfile generates kernel version error

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

Bug description:
  == Comment: #7 - Vaishnavi Bhat  - 2016-03-15 06:16:53 ==
  The following warning is generated by makedumpfile 
  * running makedumpfile --dump-dmesg /proc/vmcore 
/mnt/201602030129/dmesg.201602030129
  The kernel version is not supported.
  The created dumpfile may be incomplete.

  The makedumpfile version on your machine is 
  # makedumpfile -v
  makedumpfile: version 1.5.5 (released on 18 Dec 2013)

  I did a #sudo apt-get source makedumpfile and checked for the sources. 
  In the makedumpfile.h ,  the LATEST_VERSION is set to
  #define OLDEST_VERSION  KERNEL_VERSION(2, 6, 15)/* linux-2.6.15 */
  #define LATEST_VERSION  KERNEL_VERSION(4, 1, 0)/* linux-4.1.0 */
  where as kernel version on the machine is 
  # uname -r
  4.2.0-27-generic

  Hence we see this mismatch and message as "The kernel version is not
  supported."

  We need canonical to change the value of LATEST_VERSION  so that we do
  not see this message.

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

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

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

--- Comment From dougm...@us.ibm.com 2017-07-20 10:20 EDT---
Sorry for the confusion, something must not be mirroring status properly. This 
bug has been CLOSED UNREPRODUCIBLE.

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

Title:
  Ubuntu 16.04 testing with PMC 12GB Series 8 adapter with MaxView RAID
  Migration deletes the RAID array.

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

Bug description:
   State: Open by: nauahmed on 17 March 2016 16:09:48 

  Hi,

  While using MaxView Storage Manager on Ubuntu 16.04 
  from 
https://w3-connections.ibm.com/communities/service/html/communitystart?communityUuid=7bb2d98d-64aa-437d-863e-db67dc1f50db
  
https://w3-connections.ibm.com/wikis/home?lang=en-us#!/wiki/W6ee916ce65bf_4973_a6c3_a0f025d8acc6/page/PMC%20Adapter%20Series%207%20and%20Series%208%20Code%20Deliveries

  PostGA_2.zip
  https://w3-connections.ibm.com/files/form/anonymous/api/library/c5f8d539
  -710e-4e26-9d2f-5073644c8c67/document/f9b22e38-4b5e-46ab-94ca-
  f5cb80b9e13d/media/PostGA_2.zip

  with Expand/Migrate Logical Drive option in web GUI menu.
  whole array is lost. 

  Steps:
  1> INITIALIZE ALL disks # arcconf task start 1 device all INITIALIZE noprompt

  Controllers found: 1
  Initializing Channel 0, Device 9.
  Initializing Channel 0, Device 12.
  Initializing Channel 0, Device 13.
  Initializing Channel 0, Device 14.
  4 device(s) initialized.

  Command completed successfully.

  2> Login to Web gui of MSM.. 
  clink on controller --> create logical device ---> custom mode -->RAID 1  
Mirroring; 2 drives required; redundant ---> select minimum two drives ---> 
next ---> finish. 

  3> Click on new logical raid1 device, click expand/migrate logical
  device

  RAID1
  Select a RAID level and click 'Next' to continue
Select raid Level
RAID Members
Set Attributes
Summary
RAID 1  Mirroring,2 drives required, redundant
RAID 5  Striping with parity,3 or more drives required, redundant
Simple Volume   A single drive segment,not redundant 

  Select RAID5, add additional drive, next, Finish,

  Existing RAID 1 logical device is lost.. there is no migration <-- ALL
  data lost...

  root@p7pran04:~# uname -a
  Linux p7pran04 4.4.0-12-generic #28-Ubuntu SMP Wed Mar 9 00:40:38 UTC 2016 
ppc64le ppc64le ppc64le GNU/Linux
  root@p7pran04:~# arcconf getversion
  Controllers found: 1
  Controller #1
  ==
  Firmware   : 7.8-0 (32968)
  Staged Firmware: 7.8-0 (32968)
  BIOS   : 7.8-0 (32968)
  Driver : 1.2-1 (41010)
  Boot Flash : 7.8-1 (32968)
  CPLD (Load version/ Flash version) : 5/ 10
  SEEPROM (Load version/ Flash version)  : 1/ 1
  root@p7pran04:~# modinfo aacraid
  filename:   
/lib/modules/4.4.0-12-generic/kernel/drivers/scsi/aacraid/aacraid.ko
  version:1.2-1[41010]-ms
  license:GPL
  description:Dell PERC2, 2/Si, 3/Si, 3/Di, Adaptec Advanced Raid Products, 
HP NetRAID-4M, IBM ServeRAID & ICP SCSI driver
  author: Red Hat Inc and Adaptec
  srcversion: FE59F41215F9D0437EA29CE
  alias:  pci:v9005d028Fsv*sd*bc*sc*i*
  alias:  pci:v9005d028Dsv*sd*bc*sc*i*
  alias:  pci:v9005d028Csv*sd*bc*sc*i*
  alias:  pci:v9005d028Bsv*sd*bc*sc*i*
  alias:  pci:v9005d0288sv*sd*bc*sc*i*
  alias:  pci:v9005d0286sv*sd*bc*sc*i*
  alias:  pci:v9005d0285sv*sd*bc*sc*i*
  alias:  pci:v9005d0285sv17AAsd*bc*sc*i*
  alias:  pci:v9005d0285sv1028sd*bc*sc*i*
  alias:  pci:v1011d0046sv103Csd10C2bc*sc*i*
  alias:  pci:v1011d0046sv9005sd1364bc*sc*i*
  alias:  pci:v1011d0046sv9005sd0364bc*sc*i*
  alias:  pci:v1011d0046sv9005sd0365bc*sc*i*
  alias:  pci:v9005d0285sv1028sd0287bc*sc*i*
  alias:  pci:v9005d0286sv9005sd02A2bc*sc*i*
  alias:  pci:v9005d0285sv9005sd029Abc*sc*i*
  alias:  pci:v9005d0285sv9005sd0299bc*sc*i*
  alias:  pci:v9005d0285sv9005sd0298bc*sc*i*
  alias:  pci:v9005d0286sv1014sd9540bc*sc*i*
  alias:  pci:v9005d0286sv1014sd9580bc*sc*i*
  alias:  pci:v9005d0285sv1014sd0312bc*sc*i*
  alias:  pci:v9005d0285sv1014sd02F2bc*sc*i*
  alias:  pci:v9005d0285sv9005sd0297bc*sc*i*
  alias:  pci:v9005d0285sv9005sd0296bc*sc*i*
  alias:

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

2017-07-20 Thread Po-Hsu Lin

3.13.0-125.174~precise1 - generic
Regression test CMPL.
http://kernel.ubuntu.com/testing/tracker-index.html

Issue to note in amd64:
  aio_dio_bugs - test for CVE-2016-10044, expected

Issue to note in i386:
  aio_dio_bugs - test for CVE-2016-10044, expected

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2016-10044

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

** Changed in: kernel-sru-workflow/regression-testing
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Po-Hsu Lin 
(cypressyew)

** Tags added: regression-testing-passed

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

Title:
  linux-lts-trusty: 3.13.0-125.174~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:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow upload-to-ppa series:
  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: 1703396
  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/1703397/+subscriptions

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

[Kernel-packages] [Bug 1705466] Re: Kernel oopsed when booting

Can you reproduce the oops, or was it a one time event?

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

** Tags added: kernel-da-key

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

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

Title:
  Kernel oopsed when booting

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

Bug description:
  Spoke to Leann and she suggested that I log this.

  Artful running proposed.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.11.0-11-generic 4.11.0-11.16
  ProcVersionSignature: Ubuntu 4.11.0-11.16-generic 4.11.10
  Uname: Linux 4.11.0-11-generic x86_64
  ApportVersion: 2.20.5-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 1870 F pulseaudio
  CurrentDesktop: GNOME
  Date: Thu Jul 20 13:14:48 2017
  InstallationDate: Installed on 2017-07-10 (10 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170709)
  MachineType: Dell Inc. Inspiron 11-3168
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.11.0-11-generic.efi.signed 
root=UUID=02673bea-6091-48ee-8a1f-44d3ea4b71ce ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.11.0-11-generic N/A
   linux-backports-modules-4.11.0-11-generic  N/A
   linux-firmware 1.167
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/24/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.0.1
  dmi.board.name: 0XKKP9
  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.:bvr1.0.1:bd03/24/2016:svnDellInc.:pnInspiron11-3168:pvr1.0.1:rvnDellInc.:rn0XKKP9:rvrA00:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.name: Inspiron 11-3168
  dmi.product.version: 1.0.1
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1705493] Re: [4.4][backport] Multiple partitions are not supported on a bcache device

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

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

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

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

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

** Tags added: kernel-da-key

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

Title:
  [4.4][backport] Multiple partitions are not supported on a bcache
  device

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

Bug description:
  Support for adding partitions on bcache devices only landed in 4.10:

  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=b8c0d911ac5285e6be8967713271a51bdc5a936a

  Although it is a small change, it is not backported to any of the
  xenial kernels and it only exists naturally in 4.10.

  ➜ ubuntu-xenial git:(master) git tag 
--contains=b8c0d911ac5285e6be8967713271a51bdc5a936a
  Ubuntu-hwe-4.10.0-13.15_16.04.2
  Ubuntu-hwe-4.10.0-14.16_16.04.1
  Ubuntu-hwe-4.10.0-19.21_16.04.1
  Ubuntu-hwe-4.10.0-20.22_16.04.1
  Ubuntu-hwe-4.10.0-21.23_16.04.1
  Ubuntu-hwe-4.10.0-22.24_16.04.1
  Ubuntu-hwe-4.10.0-25.29_16.04.1
  Ubuntu-hwe-4.10.0-26.30_16.04.1
  Ubuntu-hwe-4.10.0-28.32_16.04.1
  Ubuntu-hwe-edge-4.10.0-9.11_16.04.2
  Ubuntu-lts-4.10.0-10.12_16.04.1
  Ubuntu-lts-4.10.0-11.13_16.04.1
  Ubuntu-lts-4.10.0-12.14_16.04.1
  Ubuntu-lts-4.10.0-13.15_16.04.1
  Ubuntu-lts-4.10.0-7.9_16.04.1
  Ubuntu-lts-4.10.0-8.10_16.04.1
  Ubuntu-lts-4.10.0-9.11_16.04.1
  Ubuntu-lts-4.10.0-9.11_16.04.2

  This will prevent usage of multiple partitions on the same device
  which is the case when data and journal are collocated.

  Also, the lack of that feature prevents dmcrypt usage as multiple
  partitions are created on a device in this case.

  
  Could that be backported to the 4.4 kernel?

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

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

[Kernel-packages] [Bug 1705349] Re: tgtd blocked with hitting hung_task_timeout_secs

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


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

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

** Tags added: kernel-da-key

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

Title:
  tgtd blocked with hitting hung_task_timeout_secs

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  
  We see an issue where an IO thread of tgtd violates the hung task timeout and 
vmstat reports >20% wait on IO while we are not seeing a issue with the 
underlying hardware (iowait and svc time) inside IO stat. 

  We already limited the kernel parameters

  vm.dirty_background_ratio=5
  vm.dirty_ratio=10

  to reduce the impact of massive dirty blocks hitting the storage which
  is still based on spinning rust in a RAID 10 array.

  
  This is based on kernel 3.13.0-96-generic with the deadline IO scheduler and 
we got the following stack trace:

  
  [25300644.048029] INFO: task tgtd:27827 blocked for more than 300 seconds.
  [25300644.048065]   Not tainted 3.13.0-96-generic #143-Ubuntu
  [25300644.048100] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [25300644.048166] tgtdD 88103fc13180 0 27827  1 
0x0080
  [25300644.048168]  88019cc61c78 0086 880125791800 
00013180
  [25300644.048171]  88019cc61fd8 00013180 880125791800 
88103fc13a18
  [25300644.048173]  88207ffef6e8 88019cc61d00 0002 
81151e90
  [25300644.048176] Call Trace:
  [25300644.048178]  [] ? wait_on_page_read+0x60/0x60
  [25300644.048190]  [] io_schedule+0x9d/0x130
  [25300644.048192]  [] sleep_on_page+0xe/0x20
  [25300644.048194]  [] __wait_on_bit_lock+0x48/0xb0
  [25300644.048196]  [] __lock_page+0x6a/0x70
  [25300644.048198]  [] ? autoremove_wake_function+0x40/0x40
  [25300644.048200]  [] write_cache_pages+0x2f8/0x4b0
  [25300644.048202]  [] ? global_dirtyable_memory+0x50/0x50
  [25300644.048205]  [] ? get_futex_key+0x1d8/0x2c0
  [25300644.048207]  [] ? send_signal+0x3e/0x80
  [25300644.048209]  [] generic_writepages+0x40/0x60
  [25300644.048212]  [] do_writepages+0x1e/0x40
  [25300644.048213]  [] __filemap_fdatawrite_range+0x59/0x60
  [25300644.048215]  [] filemap_write_and_wait_range+0x2a/0x70
  [25300644.048217]  [] blkdev_fsync+0x1b/0x50
  [25300644.048219]  [] do_fsync+0x51/0x80
  [25300644.048221]  [] SyS_fdatasync+0x13/0x20
  [25300644.048223]  [] system_call_fastpath+0x1a/0x1f


  UPTIME report
   16:30:01 up 292 days, 22:34,  0 users,  load average: 9.89, 8.58, 5.33

  FREE report
   total   used   free sharedbuffers cached
  Mem: 131777272  116935780   14841492828  1106297401123368
  -/+ buffers/cache:5182672  126594600
  Swap:  7999484   90047990480

  VMSTAT report
  procs ---memory-- ---swap-- -io -system-- 
--cpu-
   r  b   swpd   free   buff  cache   si   sobibo   in   cs us sy id wa 
st
   0 10  8  14493 108036   109700 7   22700  0  0 100  
0  0
   0 10  8  14494 108036   109700 0 0  690 1149  0  0 78 22 
 0
   0 10  8  14494 108036   109700 0 8  736 1442  0  0 78 22 
 0

  IOSTAT report
  Linux 3.13.0-96-generic (cinder18)   07/19/2017  _x86_64_(32 
CPU)

  07/19/2017 04:30:03 PM
  avg-cpu:  %user   %nice %system %iowait  %steal   %idle
 0.350.000.080.070.00   99.50

  
  Device: rrqm/s   wrqm/s r/s w/srkB/swkB/s avgrq-sz 
avgqu-sz   await r_await w_await  svctm  %util
  sda   0.00 3.970.40   10.89 1.7563.1611.51
 0.000.160.130.16   0.01   0.01
  sdb  51.40   107.252.20   15.89   215.29  7198.82   819.79
 0.073.893.263.97   0.60   1.08
  sdc   0.00 0.000.000.00 0.00 0.00 8.00
 0.000.110.110.00   0.11   0.00
  dm-0  0.00 0.000.000.00 0.00 0.01 8.00
 0.00   11.760.66   14.98   0.17   0.00
  dm-1  0.00 0.000.01   14.86 0.1963.13 8.52

[Kernel-packages] [Bug 1705447] Re: misleading kernel warning skb_warn_bad_offload during checksum calculation

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

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

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

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

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

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

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

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

** Tags added: kernel-da-key xenial zesty

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

Title:
  misleading kernel warning skb_warn_bad_offload during checksum
  calculation

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

Bug description:
  Even when the packet says checksum calculation is unnecessary the
  kernel will still check the checksum and display a warning that the
  checksum is bad.

  This has been fixed upstream in Kernel 4.11 by commit id:
  b2504a5dbef3305ef41988ad270b0e8ec289331c

  We have reports of Ubuntu 16.04 virtual machines (with ip forward
  enabled) displaying these warnings:

  
  [10480.074664] [ cut here ]
  [10480.074667] WARNING: CPU: 1 PID: 0 at 
/build/linux-hwe-X3pKE5/linux-hwe-4.8.0/net/core/dev.c:2444 
skb_warn_bad_offload+0xd1/0x120
  [10480.074669] docker0: caps=(0x0400ffbb78e9, 0x) 
len=2962 data_len=2834 gso_size=1448 gso_type=5 ip_summed=1
  [10480.074670] Modules linked in: veth nfsv3 nfs_acl rpcsec_gss_krb5 
auth_rpcgss nfsv4 nfs lockd grace sunrpc fscache ipt_MASQUERADE 
nf_nat_masquerade_ipv4 xfrm_user xfrm_algo iptable_nat nf_conntrack_ipv4 
nf_defrag_ipv4 nf_nat_ipv4 xt_addrtype iptable_filter ip_tables xt_conntrack 
x_tables nf_nat nf_conntrack br_netfilter bridge stp llc aufs zfs(PO) 
zunicode(PO) zcommon(PO) znvpair(PO) spl(O) zavl(PO) crct10dif_pclmul 
crc32_pclmul ghash_clmulni_intel aesni_intel aes_x86_64 lrw glue_helper 
ablk_helper cryptd input_leds joydev serio_raw i2c_piix4 mac_hid parport_pc 
ppdev lp parport autofs4 hid_generic usbhid hid virtio_scsi psmouse virtio_net 
pata_acpi floppy
  [10480.074695] CPU: 1 PID: 0 Comm: swapper/1 Tainted: PW  O
4.8.0-52-generic #55~16.04.1-Ubuntu
  [10480.074696] Hardware name: Nutanix AHV, BIOS seabios-1.7.5-11.el6 
04/01/2014
  [10480.074697]  0286 ec176c2ae03bc036 8beef5643870 
b7a2e7b3
  [10480.074699]  8beef56438c0  8beef56438b0 
b768314b
  [10480.074702]  098cb84fba80 8bed61f82000 8bee9915c000 
0005
  [10480.074704] Call Trace:
  [10480.074704][] dump_stack+0x63/0x90
  [10480.074708]  [] __warn+0xcb/0xf0
  [10480.074710]  [] warn_slowpath_fmt+0x5f/0x80
  [10480.074713]  [] ? ___ratelimit+0xa2/0xf0
  [10480.074714]  [] skb_warn_bad_offload+0xd1/0x120
  [10480.074716]  [] __skb_gso_segment+0xd8/0x140
  [10480.074717]  [] validate_xmit_skb+0x14f/0x2a0
  [10480.074719]  [] __dev_queue_xmit+0x322/0x6d0
  [10480.074720]  [] ? nf_nat_ipv4_fn+0x1a6/0x230 
[nf_nat_ipv4]
  [10480.074723]  [] dev_queue_xmit+0x10/0x20
  [10480.074725]  [] ip_finish_output2+0x292/0x380
  [10480.074726]  [] ? ipv4_confirm+0x7d/0x100 
[nf_conntrack_ipv4]
  [10480.074728]  [] ip_finish_output+0x132/0x1d0
  [10480.074729]  [] ? nf_hook_slow+0x73/0xd0
  [10480.074731]  [] ip_output+0x6e/0xf0
  [10480.074733]  [] ? 
__ip_flush_pending_frames.isra.40+0x90/0x90
  [10480.074736]  [] ip_forward_finish+0x43/0x70
  [10480.074738]  [] ip_forward+0x384/0x480
  [10480.074739]  [] ? ip_frag_mem+0x50/0x50
  [10480.074741]  [] ip_rcv_finish+0x11b/0x400
  [10480.074743]  [] ip_rcv+0x28b/0x3c0
  [10480.074744]  [] ? inet_del_offload+0x40/0x40
  [10480.074746]  [] __netif_receive_skb_core+0x524/0xab0
  [10480.074747]  [] ? kmem_cache_alloc+0xd7/0x1b0
  [10480.074749]  [] ? __build_skb+0x2a/0xe0
  [10480.074751]  [] __netif_receive_skb+0x18/0x60
  [10480.074753]  [] netif_receive_skb_internal+0x32/0xa0
  [10480.074754]  [] napi_gro_receive+0xcd/0x120
  [10480.074756]  [] virtnet_receive+0x1c3/0x970 [virtio_net]
  [10480.074758]  [] ? update_cfs_rq_load_avg+0x1f9/0x4c0
  [10480.074760]  [] virtnet_poll+0x1d/0x80 [virtio_net]
  [10480.074762]  [] net_rx_action+0x238/0x380
  [10480.074764]  [] __do_softirq+0xf6/0x280
  [10480.074765]  [] irq_exit+0xa3/0xb0
  [10480.074766]  [] do_IRQ+0x54/0xd0
  [10480.074768]  [] common_interrupt+0x82/0x82
  [10480.074768][] ? native_safe_halt+0x6/0x10
  [10480.074772]  [] default_idle+0x1e/0xd0
  [10480.074774]  [] arch_cpu_idle+0xf/0x20
  [10480.074775]  [] default_idle_call+0x2a/0x40
  [10480.074776]  [] cpu_startup_entry+0x2ea/0x350
  [10480.074778]  [] start_secondary+0x151/0x190

[Kernel-packages] [Bug 1705493] 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 1705493

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

Title:
  [4.4][backport] Multiple partitions are not supported on a bcache
  device

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

Bug description:
  Support for adding partitions on bcache devices only landed in 4.10:

  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=b8c0d911ac5285e6be8967713271a51bdc5a936a

  Although it is a small change, it is not backported to any of the
  xenial kernels and it only exists naturally in 4.10.

  ➜ ubuntu-xenial git:(master) git tag 
--contains=b8c0d911ac5285e6be8967713271a51bdc5a936a
  Ubuntu-hwe-4.10.0-13.15_16.04.2
  Ubuntu-hwe-4.10.0-14.16_16.04.1
  Ubuntu-hwe-4.10.0-19.21_16.04.1
  Ubuntu-hwe-4.10.0-20.22_16.04.1
  Ubuntu-hwe-4.10.0-21.23_16.04.1
  Ubuntu-hwe-4.10.0-22.24_16.04.1
  Ubuntu-hwe-4.10.0-25.29_16.04.1
  Ubuntu-hwe-4.10.0-26.30_16.04.1
  Ubuntu-hwe-4.10.0-28.32_16.04.1
  Ubuntu-hwe-edge-4.10.0-9.11_16.04.2
  Ubuntu-lts-4.10.0-10.12_16.04.1
  Ubuntu-lts-4.10.0-11.13_16.04.1
  Ubuntu-lts-4.10.0-12.14_16.04.1
  Ubuntu-lts-4.10.0-13.15_16.04.1
  Ubuntu-lts-4.10.0-7.9_16.04.1
  Ubuntu-lts-4.10.0-8.10_16.04.1
  Ubuntu-lts-4.10.0-9.11_16.04.1
  Ubuntu-lts-4.10.0-9.11_16.04.2

  This will prevent usage of multiple partitions on the same device
  which is the case when data and journal are collocated.

  Also, the lack of that feature prevents dmcrypt usage as multiple
  partitions are created on a device in this case.

  
  Could that be backported to the 4.4 kernel?

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

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

[Kernel-packages] [Bug 1705495] 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 1705495

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

Title:
  Adt tests of src:linux time out often on armhf lxc containers

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  http://autopkgtest.ubuntu.com/packages/linux/artful/armhf

  quite often the tests time out on armhf. Maybe this is due to running
  inside a lxc container, rather than in a full VM.

  Could you please consider disabling rebuild test on armhf? Or for
  example lowering its parallelism during adt tests.

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

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

[Kernel-packages] [Bug 1705495] [NEW] Adt tests of src:linux time out often on armhf lxc containers

2017-07-20 Thread Dimitri John Ledkov

Public bug reported:

http://autopkgtest.ubuntu.com/packages/linux/artful/armhf

quite often the tests time out on armhf. Maybe this is due to running
inside a lxc container, rather than in a full VM.

Could you please consider disabling rebuild test on armhf? Or for
example lowering its parallelism during adt tests.

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


** Tags: adt-fail

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

Title:
  Adt tests of src:linux time out often on armhf lxc containers

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  http://autopkgtest.ubuntu.com/packages/linux/artful/armhf

  quite often the tests time out on armhf. Maybe this is due to running
  inside a lxc container, rather than in a full VM.

  Could you please consider disabling rebuild test on armhf? Or for
  example lowering its parallelism during adt tests.

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

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

[Kernel-packages] [Bug 1678745] Re: Ubuntu17.04 KVM: Guest crashed @ xfs_perag_get_tag+0x6c

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

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

Title:
  Ubuntu17.04 KVM: Guest crashed @ xfs_perag_get_tag+0x6c

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

Bug description:
  == Comment: #0 - Lata Kuntal  - 2017-03-30 09:44:23 ==
  Ubuntu 17.04 KVM guest gusg8 was having ubuntu 16.04.2 and was running stress 
test IO, Base,TCP and NFS.The guest is having XFS as rootFS and after running 
few hours of regression test it dropped at xmon.

  Console logs :
  
  root@guskvm:~# virsh console gusg8 --force
  Connected to domain gusg8
  Escape character is ^]

  
  1:mon> r
  R00 = d288edf4   R16 = 024200ca
  R01 = c000378cb1f0   R17 = 
  R02 = d2936080   R18 = 0020
  R03 = 0001   R19 = c002734d1800
  R04 = c000378cb190   R20 = 
  R05 =    R21 = 
  R06 = 3c00d03fe056   R22 = c0027e26ccf0
  R07 =    R23 = 
  R08 = c48492d0   R24 = 
  R09 = 3c00d03fe056   R25 = 
  R10 = 3c00d03fe062   R26 = 00024df4cd49
  R11 = d28fa360   R27 = 
  R12 =    R28 = d28ac7b0
  R13 = cfb80900   R29 = c4849000
  R14 =    R30 = 
  R15 = c137ad08   R31 = 
  pc  = d288ee0c xfs_perag_get_tag+0x6c/0x170 [xfs]
  cfar= c096a494 perf_trace_mmc_request_start+0x104/0x440
  lr  = d288edf4 xfs_perag_get_tag+0x54/0x170 [xfs]
  msr = 80010280b033   cr  = 82428424
  ctr = c05e4950   xer = 2000   trap =  300
  dar = 3c00d03fe062   dsisr = 4000
  1:mon> t
  [c000378cb250] d28ac7b0 xfs_reclaim_inodes_count+0x70/0xa0 [xfs]
  [c000378cb290] d28c0ea8 xfs_fs_nr_cached_objects+0x28/0x40 [xfs]
  [c000378cb2b0] c03292d8 super_cache_count+0x68/0x120
  [c000378cb2f0] c0271530 shrink_slab.part.14+0x150/0x4f0
  [c000378cb430] c0276db8 shrink_node+0x158/0x3f0
  [c000378cb4f0] c0277178 do_try_to_free_pages+0x128/0x460
  [c000378cb590] c02775ac try_to_free_pages+0xfc/0x280
  [c000378cb620] c0260158 __alloc_pages_nodemask+0x758/0xe30
  [c000378cb7e0] c02dbb98 alloc_pages_vma+0x108/0x360
  [c000378cb880] c029d080 wp_page_copy+0xf0/0x9d0
  [c000378cb920] c02a0770 do_wp_page+0x210/0xb20
  [c000378cb9b0] c02a656c handle_mm_fault+0x9cc/0x14c0
  [c000378cba60] c0b511a0 do_page_fault+0x260/0x7d0
  [c000378cbb10] c0008948 handle_page_fault+0x10/0x30
  --- Exception: 301 (Data Access) at c010aec4 schedule_tail+0x84/0xb0
  [c000378cbe30] c0009844 ret_from_fork+0x4/0x54
  --- Exception: c00 (System Call) at 3fffa2b5bf44
  1:mon> d
      ||
  1:mon> c
  cpus stopped: 0x0-0x3
  1:mon>

  Kernel host build
  =
  root@guskvm:~# uname -r
  4.10.0-13-generic
  root@guskvm:~#

  
  == Comment: #1 - Luciano Chavez  - 2017-03-30 10:42:15 ==
  At first glance, based on the following assembly from around the failure 
point:

  d288edd4  38c1  li  r6,1
  d288edd8  7f8802a6  mflrr28
  d288eddc  78a70020  clrldi  r7,r5,32
  d288ede0  7c7d1b78  mr  r29,r3
  d288ede4  7c852378  mr  r5,r4
  d288ede8  386302c8  addir3,r3,712
  d288edec  38810020  addir4,r1,32
  d288edf0  4806b571  bl  d28fa360# 
exit_xfs_fs+0x180c/0xfd44 [xfs]
  d288edf4  e8410018  ld  r2,24(r1)
  d288edf8  2f83  cmpwi   cr7,r3,0
  d288edfc  409d0104  ble cr7,d288ef00# 
xfs_perag_get_tag+0x160/0x170 [xfs]
  d288ee00  7c0004ac  sync
  d288ee04  e9210020  ld  r9,32(r1)
  d288ee08  3949000c  addir10,r9,12
  d288ee0c  7fc05028  lwarx   r30,0,r10
  d288ee10  33de0001  addic   r30,r30,1
  d288ee14  7fc0512d  stwcx.  r30,0,r10

  I believe the

[Kernel-packages] [Bug 1656123] Re: Dualshock 4 (ps4 controller) prevents Ubuntu from booting

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

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

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

Title:
  Dualshock 4 (ps4 controller) prevents Ubuntu from booting

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  If my Dualshock 4 controller is plugged in via usb before booting the
  system boot hangs before it gets the login window and I cannot
  activate a seperate tty session for debugging.

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

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

[Kernel-packages] [Bug 1705117] Re: ubuntu 17.04 : Boot failed with luks disk

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


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

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

Title:
  ubuntu 17.04 : Boot failed with luks disk

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 17.04 with kernel  4.10.0-21-generic #23-Ubuntu boot successfully with 
my lucks partition. I enter the pass and it works.
  But all kernels after this one failed to boot. I enter the pass and then it 
freeze.
  I guess it is a kernel issue.

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

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

[Kernel-packages] [Bug 1705054] Re: Trusty kexec-tools suffer from upstream code regression. Fix not included.

2017-07-20 Thread Łukasz Zemczak

Hello Rafael, or anyone else affected,

Accepted kexec-tools into trusty-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/kexec-
tools/1:2.0.6-0ubuntu2.3 in a few hours, and then in the -proposed
repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-trusty to verification-done-trusty. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-trusty. In either case, details of your
testing will help us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Changed in: kexec-tools (Ubuntu Trusty)
   Status: In Progress => Fix Committed

** Tags added: verification-needed verification-needed-trusty

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

Title:
  Trusty kexec-tools suffer from upstream code regression. Fix not
  included.

Status in kexec-tools package in Ubuntu:
  Fix Released
Status in kexec-tools source package in Trusty:
  Fix Committed

Bug description:
  [Impact]

   * kdump doesn't work on non-efi systems
   * a kernel dump can't be generated

  [Test Case]

   * install kdump-tools
   * configure kdump-tools (/etc/default/kdump-tools)
   * try to start kdump-tools service (kdump-config start)
   * while executing kexec, you will get:
 "efi memory descriptor version 0 is not supported!"

  [Regression Potential]

   * in theory it could brake kdump for efi systems
   * in practice, its based on upstream regression fix (not included in Trusty)
   * it has also been tested in 3 different setups and it worked

  [Other Info]

  Based on upstream code commit explanation:

  """
  On non-EFI systems, efi_info section of boot_params is zero filled resulting
  in an erroneous message from kexec regarding "efi memory descriptor" version.

  Caused by commit: e1ffc9e9a0769e1f54185003102e9bec428b84e8 "Passing efi 
related
  data via setup_data"

  # od -j 448 -N 32 -v -x /sys/kernel/boot_params/data
  700        
  720        
  740

  # kexec -l --reuse-cmdline --initrd=/boot/initrd-`uname -r` 
/boot/vmlinuz-`uname -r`
  efi memory descriptor version 0 is not supported!
  """

  It was brought to my attention to some of our users are facing this:

  
  ## TRUSTY with kernel 4.4.0-83-generic

  # /usr/sbin/kdump-config load
  efi memory descriptor version 0 is not supported!
  * loaded kdump kernel

  /var/log/syslog:

  Jul 18 13:37:06  kdump-config: /sbin/kexec -p 
--command-line="BOOT_IMAGE=/boot/vmlinuz-4.4.0-83-generic 
root=UUID=-20e4-4325-ad92-7aef2af0beac ro KDUMP_CMDLINE_APPEND=irqpoll 
maxcpus=1 nousb irqpoll maxcpus=1 nousb" 
--initrd=/boot/initrd.img-4.4.0-83-generic /boot/vmlinuz-4.4.0-83-generic
  Jul 18 13:37:06  kdump-config: loaded kdump kernel
  

  Despite the message of kdump being loaded, it doesn't look that it is
  operational. Dump files could be generated using Xenial kdump-tools,
  but not Trusty's.

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

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

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

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

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

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

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

Status in linux package in Ubuntu:
  Incomplete

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

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

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

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

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

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

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

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

[Kernel-packages] [Bug 1705493] [NEW] [4.4][backport] Multiple partitions are not supported on a bcache device

2017-07-20 Thread Dmitrii Shcherbakov

Public bug reported:

Support for adding partitions on bcache devices only landed in 4.10:

https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=b8c0d911ac5285e6be8967713271a51bdc5a936a

Although it is a small change, it is not backported to any of the xenial
kernels and it only exists naturally in 4.10.

➜ ubuntu-xenial git:(master) git tag 
--contains=b8c0d911ac5285e6be8967713271a51bdc5a936a
Ubuntu-hwe-4.10.0-13.15_16.04.2
Ubuntu-hwe-4.10.0-14.16_16.04.1
Ubuntu-hwe-4.10.0-19.21_16.04.1
Ubuntu-hwe-4.10.0-20.22_16.04.1
Ubuntu-hwe-4.10.0-21.23_16.04.1
Ubuntu-hwe-4.10.0-22.24_16.04.1
Ubuntu-hwe-4.10.0-25.29_16.04.1
Ubuntu-hwe-4.10.0-26.30_16.04.1
Ubuntu-hwe-4.10.0-28.32_16.04.1
Ubuntu-hwe-edge-4.10.0-9.11_16.04.2
Ubuntu-lts-4.10.0-10.12_16.04.1
Ubuntu-lts-4.10.0-11.13_16.04.1
Ubuntu-lts-4.10.0-12.14_16.04.1
Ubuntu-lts-4.10.0-13.15_16.04.1
Ubuntu-lts-4.10.0-7.9_16.04.1
Ubuntu-lts-4.10.0-8.10_16.04.1
Ubuntu-lts-4.10.0-9.11_16.04.1
Ubuntu-lts-4.10.0-9.11_16.04.2

This will prevent usage of multiple partitions on the same device which
is the case when data and journal are collocated.

Also, the lack of that feature prevents dmcrypt usage as multiple
partitions are created on a device in this case.


Could that be backported to the 4.4 kernel?

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


** Tags: canonical-bootstack cpec

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

Title:
  [4.4][backport] Multiple partitions are not supported on a bcache
  device

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Support for adding partitions on bcache devices only landed in 4.10:

  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=b8c0d911ac5285e6be8967713271a51bdc5a936a

  Although it is a small change, it is not backported to any of the
  xenial kernels and it only exists naturally in 4.10.

  ➜ ubuntu-xenial git:(master) git tag 
--contains=b8c0d911ac5285e6be8967713271a51bdc5a936a
  Ubuntu-hwe-4.10.0-13.15_16.04.2
  Ubuntu-hwe-4.10.0-14.16_16.04.1
  Ubuntu-hwe-4.10.0-19.21_16.04.1
  Ubuntu-hwe-4.10.0-20.22_16.04.1
  Ubuntu-hwe-4.10.0-21.23_16.04.1
  Ubuntu-hwe-4.10.0-22.24_16.04.1
  Ubuntu-hwe-4.10.0-25.29_16.04.1
  Ubuntu-hwe-4.10.0-26.30_16.04.1
  Ubuntu-hwe-4.10.0-28.32_16.04.1
  Ubuntu-hwe-edge-4.10.0-9.11_16.04.2
  Ubuntu-lts-4.10.0-10.12_16.04.1
  Ubuntu-lts-4.10.0-11.13_16.04.1
  Ubuntu-lts-4.10.0-12.14_16.04.1
  Ubuntu-lts-4.10.0-13.15_16.04.1
  Ubuntu-lts-4.10.0-7.9_16.04.1
  Ubuntu-lts-4.10.0-8.10_16.04.1
  Ubuntu-lts-4.10.0-9.11_16.04.1
  Ubuntu-lts-4.10.0-9.11_16.04.2

  This will prevent usage of multiple partitions on the same device
  which is the case when data and journal are collocated.

  Also, the lack of that feature prevents dmcrypt usage as multiple
  partitions are created on a device in this case.

  
  Could that be backported to the 4.4 kernel?

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

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

[Kernel-packages] [Bug 1566400] Re: Ubuntu 16.04 testing with PMC 12GB Series 8 adapter with MaxView RAID Migration deletes the RAID array.

Are there patches available yet to address this issue?

** Tags added: kernel-da-key

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

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

Title:
  Ubuntu 16.04 testing with PMC 12GB Series 8 adapter with MaxView RAID
  Migration deletes the RAID array.

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

Bug description:
   State: Open by: nauahmed on 17 March 2016 16:09:48 

  Hi,

  While using MaxView Storage Manager on Ubuntu 16.04 
  from 
https://w3-connections.ibm.com/communities/service/html/communitystart?communityUuid=7bb2d98d-64aa-437d-863e-db67dc1f50db
  
https://w3-connections.ibm.com/wikis/home?lang=en-us#!/wiki/W6ee916ce65bf_4973_a6c3_a0f025d8acc6/page/PMC%20Adapter%20Series%207%20and%20Series%208%20Code%20Deliveries

  PostGA_2.zip
  https://w3-connections.ibm.com/files/form/anonymous/api/library/c5f8d539
  -710e-4e26-9d2f-5073644c8c67/document/f9b22e38-4b5e-46ab-94ca-
  f5cb80b9e13d/media/PostGA_2.zip

  with Expand/Migrate Logical Drive option in web GUI menu.
  whole array is lost. 

  Steps:
  1> INITIALIZE ALL disks # arcconf task start 1 device all INITIALIZE noprompt

  Controllers found: 1
  Initializing Channel 0, Device 9.
  Initializing Channel 0, Device 12.
  Initializing Channel 0, Device 13.
  Initializing Channel 0, Device 14.
  4 device(s) initialized.

  Command completed successfully.

  2> Login to Web gui of MSM.. 
  clink on controller --> create logical device ---> custom mode -->RAID 1  
Mirroring; 2 drives required; redundant ---> select minimum two drives ---> 
next ---> finish. 

  3> Click on new logical raid1 device, click expand/migrate logical
  device

  RAID1
  Select a RAID level and click 'Next' to continue
Select raid Level
RAID Members
Set Attributes
Summary
RAID 1  Mirroring,2 drives required, redundant
RAID 5  Striping with parity,3 or more drives required, redundant
Simple Volume   A single drive segment,not redundant 

  Select RAID5, add additional drive, next, Finish,

  Existing RAID 1 logical device is lost.. there is no migration <-- ALL
  data lost...

  root@p7pran04:~# uname -a
  Linux p7pran04 4.4.0-12-generic #28-Ubuntu SMP Wed Mar 9 00:40:38 UTC 2016 
ppc64le ppc64le ppc64le GNU/Linux
  root@p7pran04:~# arcconf getversion
  Controllers found: 1
  Controller #1
  ==
  Firmware   : 7.8-0 (32968)
  Staged Firmware: 7.8-0 (32968)
  BIOS   : 7.8-0 (32968)
  Driver : 1.2-1 (41010)
  Boot Flash : 7.8-1 (32968)
  CPLD (Load version/ Flash version) : 5/ 10
  SEEPROM (Load version/ Flash version)  : 1/ 1
  root@p7pran04:~# modinfo aacraid
  filename:   
/lib/modules/4.4.0-12-generic/kernel/drivers/scsi/aacraid/aacraid.ko
  version:1.2-1[41010]-ms
  license:GPL
  description:Dell PERC2, 2/Si, 3/Si, 3/Di, Adaptec Advanced Raid Products, 
HP NetRAID-4M, IBM ServeRAID & ICP SCSI driver
  author: Red Hat Inc and Adaptec
  srcversion: FE59F41215F9D0437EA29CE
  alias:  pci:v9005d028Fsv*sd*bc*sc*i*
  alias:  pci:v9005d028Dsv*sd*bc*sc*i*
  alias:  pci:v9005d028Csv*sd*bc*sc*i*
  alias:  pci:v9005d028Bsv*sd*bc*sc*i*
  alias:  pci:v9005d0288sv*sd*bc*sc*i*
  alias:  pci:v9005d0286sv*sd*bc*sc*i*
  alias:  pci:v9005d0285sv*sd*bc*sc*i*
  alias:  pci:v9005d0285sv17AAsd*bc*sc*i*
  alias:  pci:v9005d0285sv1028sd*bc*sc*i*
  alias:  pci:v1011d0046sv103Csd10C2bc*sc*i*
  alias:  pci:v1011d0046sv9005sd1364bc*sc*i*
  alias:  pci:v1011d0046sv9005sd0364bc*sc*i*
  alias:  pci:v1011d0046sv9005sd0365bc*sc*i*
  alias:  pci:v9005d0285sv1028sd0287bc*sc*i*
  alias:  pci:v9005d0286sv9005sd02A2bc*sc*i*
  alias:  pci:v9005d0285sv9005sd029Abc*sc*i*
  alias:  pci:v9005d0285sv9005sd0299bc*sc*i*
  alias:  pci:v9005d0285sv9005sd0298bc*sc*i*
  alias:  pci:v9005d0286sv1014sd9540bc*sc*i*
  alias:  pci:v9005d0286sv1014sd9580bc*sc*i*
  alias:  pci:v9005d0285sv1014sd0312bc*sc*i*
  alias:  pci:v9005d0285sv1014sd02F2bc*sc*i*
  alias:  pci:v9005d0285sv9005sd0297bc*sc*i*
  alias:  pci:v9005d0285sv9005sd0296bc*sc*i*
  alias:  pci:v9005d0285sv103Csd3227bc*sc*i*
  alias:

[Kernel-packages] [Bug 1687779] Re: Ubuntu 16.04.2: kdump is not working in 4.8.0-46 kernel

2017-07-20 Thread goldyfruit

@Joseph, I don't know, we are just using the Ubuntu LTS versions.
You point is valid, maybe it's better to check if Zesty has this issue.

Thanks for the follow up!

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

Title:
  Ubuntu 16.04.2: kdump is not working in 4.8.0-46 kernel

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

Bug description:
  I'm not able to take a crashdump on Ubuntu Xenial 16.04.2 in 4.8.0-46 kernel.
  This issue seems to be fixed mainstream: https://lkml.org/lkml/2017/1/9/77

  
  kdump-tools 1:1.5.9-5ubuntu0.4
  makedumpfile1:1.5.9-5ubuntu0.4
  linux-image-4.8.0-46-generic4.8.0-46.49~16.04.1

  # kdump-config show

  DUMP_MODE:kdump
  USE_KDUMP:1
  KDUMP_SYSCTL: kernel.panic_on_oops=1
  KDUMP_COREDIR:/var/crash
  crashkernel addr: 0x2b00
     /var/lib/kdump/vmlinuz: symbolic link to /boot/vmlinuz-4.8.0-46-generic
  kdump initrd:
     /var/lib/kdump/initrd.img: symbolic link to 
/var/lib/kdump/initrd.img-4.8.0-46-generic
  current state:ready to kdump

  kexec command:
    /sbin/kexec -p --command-line="BOOT_IMAGE=/boot/vmlinuz-4.8.0-46-generic 
root=LABEL=cloudimg-rootfs ro nmi_watchdog=0 elevator=deadline net.ifnames=1 
cgroup_enable=memory swapaccount=1 console=ttyS0,115200 console=tty1 irqpoll 
nr_cpus=1 nousb systemd.unit=kdump-tools.service" 
--initrd=/var/lib/kdump/initrd.img /var/lib/kdump/vmlinuz

  The kernel trace

  [   10.738064] BUG: unable to handle kernel NULL pointer dereference at 
0088
  [   10.740946] IP: [] hswep_uncore_cpu_init+0x52/0xa0
  [   10.743571] PGD 0
  [   10.744482] Oops:  [#1] SMP
  [   10.745615] Modules linked in:
  [   10.747000] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 4.8.0-46-generic 
#49~16.04.1-Ubuntu
  [   10.750255] Hardware name: HP ProLiant BL460c Gen9, BIOS I36 02/17/2017
  [   10.752574] task: 8f16b2938ec0 task.stack: 8f16b294
  [   10.754892] RIP: 0010:[]  [] 
hswep_uncore_cpu_init+0x52/0xa0
  [   10.758371] RSP: 0018:8f16b2943e40  EFLAGS: 00010206
  [   10.760337] RAX: 0050 RBX:  RCX: 
238a
  [   10.762787] RDX: 8f16b01f47e0 RSI: 8f16b2c1c700 RDI: 

  [   10.765289] RBP: 8f16b2943e50 R08: 0001c700 R09: 
89231a97
  [   10.767968] R10: eac07000 R11:  R12: 
89c1a030
  [   10.770399] R13: 89ea7760 R14: 89c0daf8 R15: 
8f16b2c19300
  [   10.772894] FS:  () GS:8f16b2c0() 
knlGS:
  [   10.775945] CS:  0010 DS:  ES:  CR0: 80050033
  [   10.777935] CR2: 0088 CR3: 2d806000 CR4: 
001406f0
  [   10.780398] Stack:
  [   10.781154]  8f16b2943e50 df388e 8f16b2943e88 
89d8b292
  [   10.884602]   0105 89d8b196 
89c0daf8
  [   10.887394]  8f16b2c19300 8f16b2943f08 88e02190 
88ea377f
  [   10.890699] Call Trace:
  [   10.891596]  [] intel_uncore_init+0xfc/0x2d6
  [   10.893587]  [ 70 
38 48 8b 78 10 48 8d 4d f4 ba 94 00 00 00 e8 49 e2 45 00
  [   11.422367] RIP  [] hswep_uncore_cpu_init+0x52/0xa0
  [   11.425174]  RSP 
  [   11.426588] CR2: 0088
  [   11.427978] ---[ end trace d8adbfe4355f5160 ]---
  [   11.430006] Kernel panic - not syncing: Attempted to kill init! 
exitcode=0x0009
  [   11.430006]
  [   11.433354] ---[ end Kernel panic - not syncing: Attempted to kill init! 
exitcode=0x0009
  [   11.433354]

  Please find the full kernel trace

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

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

[Kernel-packages] [Bug 1704614] Re: very long kernel boot time with some KVM switch

** Attachment added: "demsg-mainline41110.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1704614/+attachment/4918157/+files/demsg-mainline41110.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/1704614

Title:
  very long kernel boot time with some KVM switch

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I am using a Aten KVM switch CS1794 hooked on my computer.
  It allows the switching for USB, HDMI, and audio.
  
http://www.aten.com/global/en/products/kvm/desktop-kvm-switches/cs1794/#.WWrnguk9iUk

  I run a Ubuntu 17.04 system.

  I experience a very long boot time, having done an analysis it appears
  that the main problem is the kernel boot time and more specifically
  the time it takes to start its USB subsystem.

  when you look at the dsmg output you can clearly see a gap between 4-78s and 
79-91s, all in the USB sub-process.
  --- 
  ApportVersion: 2.20.4-0ubuntu4.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  stranche   3670 F pulseaudio
   /dev/snd/controlC1:  stranche   3670 F pulseaudio
   /dev/snd/controlC0:  stranche   3670 F pulseaudio
  DistroRelease: Ubuntu 17.04
  HibernationDevice: RESUME=UUID=28d4f703-2b20-4dd3-ba8b-aa363ad5141d
  InstallationDate: Installed on 2017-07-14 (2 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: System manufacturer System Product Name
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-26-generic.efi.signed 
root=UUID=4fde9883-6d7f-4954-90d6-779f37bbdc93 ro console=tty 
console=ttyUSB0,57600 noplymouth debug
  ProcVersionSignature: Ubuntu 4.10.0-26.30-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.164.1
  RfKill:
   
  Tags:  zesty
  Uname: Linux 4.10.0-26-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 08/13/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2104
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: SABERTOOTH Z77
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2104:bd08/13/2013:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnSABERTOOTHZ77:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

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

[Kernel-packages] [Bug 1704614] Re: very long kernel boot time with some KVM switch

** Attachment added: "journalctl-mainline41110.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1704614/+attachment/4918158/+files/journalctl-mainline41110.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/1704614

Title:
  very long kernel boot time with some KVM switch

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I am using a Aten KVM switch CS1794 hooked on my computer.
  It allows the switching for USB, HDMI, and audio.
  
http://www.aten.com/global/en/products/kvm/desktop-kvm-switches/cs1794/#.WWrnguk9iUk

  I run a Ubuntu 17.04 system.

  I experience a very long boot time, having done an analysis it appears
  that the main problem is the kernel boot time and more specifically
  the time it takes to start its USB subsystem.

  when you look at the dsmg output you can clearly see a gap between 4-78s and 
79-91s, all in the USB sub-process.
  --- 
  ApportVersion: 2.20.4-0ubuntu4.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  stranche   3670 F pulseaudio
   /dev/snd/controlC1:  stranche   3670 F pulseaudio
   /dev/snd/controlC0:  stranche   3670 F pulseaudio
  DistroRelease: Ubuntu 17.04
  HibernationDevice: RESUME=UUID=28d4f703-2b20-4dd3-ba8b-aa363ad5141d
  InstallationDate: Installed on 2017-07-14 (2 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: System manufacturer System Product Name
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-26-generic.efi.signed 
root=UUID=4fde9883-6d7f-4954-90d6-779f37bbdc93 ro console=tty 
console=ttyUSB0,57600 noplymouth debug
  ProcVersionSignature: Ubuntu 4.10.0-26.30-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.164.1
  RfKill:
   
  Tags:  zesty
  Uname: Linux 4.10.0-26-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 08/13/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2104
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: SABERTOOTH Z77
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2104:bd08/13/2013:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnSABERTOOTHZ77:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

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

[Kernel-packages] [Bug 1704614] Re: very long kernel boot time with some KVM switch

** Attachment added: "lsusb-mainline41110.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1704614/+attachment/4918159/+files/lsusb-mainline41110.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/1704614

Title:
  very long kernel boot time with some KVM switch

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I am using a Aten KVM switch CS1794 hooked on my computer.
  It allows the switching for USB, HDMI, and audio.
  
http://www.aten.com/global/en/products/kvm/desktop-kvm-switches/cs1794/#.WWrnguk9iUk

  I run a Ubuntu 17.04 system.

  I experience a very long boot time, having done an analysis it appears
  that the main problem is the kernel boot time and more specifically
  the time it takes to start its USB subsystem.

  when you look at the dsmg output you can clearly see a gap between 4-78s and 
79-91s, all in the USB sub-process.
  --- 
  ApportVersion: 2.20.4-0ubuntu4.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  stranche   3670 F pulseaudio
   /dev/snd/controlC1:  stranche   3670 F pulseaudio
   /dev/snd/controlC0:  stranche   3670 F pulseaudio
  DistroRelease: Ubuntu 17.04
  HibernationDevice: RESUME=UUID=28d4f703-2b20-4dd3-ba8b-aa363ad5141d
  InstallationDate: Installed on 2017-07-14 (2 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: System manufacturer System Product Name
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-26-generic.efi.signed 
root=UUID=4fde9883-6d7f-4954-90d6-779f37bbdc93 ro console=tty 
console=ttyUSB0,57600 noplymouth debug
  ProcVersionSignature: Ubuntu 4.10.0-26.30-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.164.1
  RfKill:
   
  Tags:  zesty
  Uname: Linux 4.10.0-26-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 08/13/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2104
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: SABERTOOTH Z77
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2104:bd08/13/2013:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnSABERTOOTHZ77:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

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

[Kernel-packages] [Bug 1704614] Re: very long kernel boot time with some KVM switch