date:20190214

[Expired for nftables (Ubuntu) because there has been no activity for 60
days.]

** Changed in: nftables (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  nft nat not working

Status in linux package in Ubuntu:
  Expired
Status in nftables package in Ubuntu:
  Expired

Bug description:
  Hi ,

  I have installed an ubuntu 15.10 beta machine and configured nftables
  firewalling.

  While the regular firewalling works (using the default settings that
  come with the package), I found that nat rules are silently ignored.
  I've added this to the /etc/nftables.conf and read it:

  table ip nat {

chain prerouting {
  type nat hook prerouting priority 0;
  ip daddr 1.2.3.4 tcp dport 80 redirect to 1234
  tcp dport 80 redirect to 1235
}

chain postrouting {
  type nat hook postrouting priority 0;
} 

  }

  
  following the example from 

  http://wiki.nftables.org/wiki-
  nftables/index.php/Performing_Network_Address_Translation_%28NAT%29#Redirect

  (1.2.3.4 is just a placeholder for the address actually used here, i
  do not want to reveal the address to the bug report). nft reads this
  without complaining, and

  nft list table ip nat

  gives exactly that output (except for replacing 80 with "http"), so
  the configuration is read correctly.


  But it simply does not work. Without having any daemon listening on
  ports 1234, 1235 , traffic to port 80 works as usual. As long as there
  is not process waiting on 1234/1235, connection should be refused.


  Which is dangerous and a security flaw, since this was meant (and used
  in a similar way with iptables and Ubuntu 14.04) to avoid revealing
  sensitive data over the internet (an application that is not able to
  use https should be tunneled). When firewall rules have been loaded
  and accepted without any warning, one would expect them to run.

  Ive tried to unload all iptables-related kernel packages and to load
  packages like nft_nat, nft_redir, nft_redir_ipv4, but the direct
  connection to port 80 still works although it shouldn't.

  No error warning, no message. It just allows outgoing port 80 although
  it shouldn't.

  Which is a problem, since this is security-relevant. If it doesn't
  work, it should spit out some error message.

  (FYI: It was implemented under Ubuntu 14.04 with

  iptables -t nat -I OUTPUT -d 1.2.3.4 -p tcp --dport 80 -j REDIRECT --to-port 
1234
  )

  
  My current guess: On that wiki page's bottem there's a hint that iptables and 
nft nat cannot be used at the same time. Unfortunately Ubuntu 15.10 still loads 
plenty of iptables stuff. Although I've tried to remove it all and it's kernel 
modules, I guess this could be a problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: nftables 0.4-7
  ProcVersionSignature: Ubuntu 4.2.0-14.16-generic 4.2.2
  Uname: Linux 4.2.0-14-generic x86_64
  ApportVersion: 2.19-0ubuntu1
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Wed Oct  7 15:21:36 2015
  InstallationDate: Installed on 2015-09-03 (33 days ago)
  InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150825)
  SourcePackage: nftables
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1503695] Re: nft nat not working

[Expired for linux (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  nft nat not working

Status in linux package in Ubuntu:
  Expired
Status in nftables package in Ubuntu:
  Expired

Bug description:
  Hi ,

  I have installed an ubuntu 15.10 beta machine and configured nftables
  firewalling.

  While the regular firewalling works (using the default settings that
  come with the package), I found that nat rules are silently ignored.
  I've added this to the /etc/nftables.conf and read it:

  table ip nat {

chain prerouting {
  type nat hook prerouting priority 0;
  ip daddr 1.2.3.4 tcp dport 80 redirect to 1234
  tcp dport 80 redirect to 1235
}

chain postrouting {
  type nat hook postrouting priority 0;
} 

  }

  
  following the example from 

  http://wiki.nftables.org/wiki-
  nftables/index.php/Performing_Network_Address_Translation_%28NAT%29#Redirect

  (1.2.3.4 is just a placeholder for the address actually used here, i
  do not want to reveal the address to the bug report). nft reads this
  without complaining, and

  nft list table ip nat

  gives exactly that output (except for replacing 80 with "http"), so
  the configuration is read correctly.


  But it simply does not work. Without having any daemon listening on
  ports 1234, 1235 , traffic to port 80 works as usual. As long as there
  is not process waiting on 1234/1235, connection should be refused.


  Which is dangerous and a security flaw, since this was meant (and used
  in a similar way with iptables and Ubuntu 14.04) to avoid revealing
  sensitive data over the internet (an application that is not able to
  use https should be tunneled). When firewall rules have been loaded
  and accepted without any warning, one would expect them to run.

  Ive tried to unload all iptables-related kernel packages and to load
  packages like nft_nat, nft_redir, nft_redir_ipv4, but the direct
  connection to port 80 still works although it shouldn't.

  No error warning, no message. It just allows outgoing port 80 although
  it shouldn't.

  Which is a problem, since this is security-relevant. If it doesn't
  work, it should spit out some error message.

  (FYI: It was implemented under Ubuntu 14.04 with

  iptables -t nat -I OUTPUT -d 1.2.3.4 -p tcp --dport 80 -j REDIRECT --to-port 
1234
  )

  
  My current guess: On that wiki page's bottem there's a hint that iptables and 
nft nat cannot be used at the same time. Unfortunately Ubuntu 15.10 still loads 
plenty of iptables stuff. Although I've tried to remove it all and it's kernel 
modules, I guess this could be a problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: nftables 0.4-7
  ProcVersionSignature: Ubuntu 4.2.0-14.16-generic 4.2.2
  Uname: Linux 4.2.0-14-generic x86_64
  ApportVersion: 2.19-0ubuntu1
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Wed Oct  7 15:21:36 2015
  InstallationDate: Installed on 2015-09-03 (33 days ago)
  InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150825)
  SourcePackage: nftables
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1808677] Re: apt hangs when updating to inux-headers-4.18.0-12-generic

[Expired for linux (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  apt hangs when updating to inux-headers-4.18.0-12-generic

Status in linux package in Ubuntu:
  Expired

Bug description:
  When updating only the kernel it hangs:

  apt install --only-upgrade linux-generic
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  The following additional packages will be installed:
linux-headers-4.18.0-12 linux-headers-4.18.0-12-generic 
linux-headers-generic linux-image-4.18.0-12-generic linux-image-generic 
linux-modules-4.18.0-12-generic
linux-modules-extra-4.18.0-12-generic
  Suggested packages:
fdutils linux-doc-4.18.0 | linux-source-4.18.0 linux-tools
  The following NEW packages will be installed:
linux-headers-4.18.0-12 linux-headers-4.18.0-12-generic 
linux-image-4.18.0-12-generic linux-modules-4.18.0-12-generic 
linux-modules-extra-4.18.0-12-generic
  The following packages will be upgraded:
linux-generic linux-headers-generic linux-image-generic
  3 upgraded, 5 newly installed, 0 to remove and 148 not upgraded.
  Need to get 0 B/66,0 MB of archives.
  After this operation, 330 MB of additional disk space will be used.
  Do you want to continue? [Y/n] Y
  Reading changelogs... Done
  Selecting previously unselected package linux-modules-4.18.0-12-generic.
  (Reading database ... 269826 files and directories currently installed.)
  Preparing to unpack 
.../0-linux-modules-4.18.0-12-generic_4.18.0-12.13_amd64.deb ...
  Unpacking linux-modules-4.18.0-12-generic (4.18.0-12.13) ...
  Selecting previously unselected package linux-image-4.18.0-12-generic.
  Preparing to unpack 
.../1-linux-image-4.18.0-12-generic_4.18.0-12.13_amd64.deb ...
  Unpacking linux-image-4.18.0-12-generic (4.18.0-12.13) ...
  Selecting previously unselected package linux-modules-extra-4.18.0-12-generic.
  Preparing to unpack 
.../2-linux-modules-extra-4.18.0-12-generic_4.18.0-12.13_amd64.deb ...
  Unpacking linux-modules-extra-4.18.0-12-generic (4.18.0-12.13) ...
  Preparing to unpack .../3-linux-generic_4.18.0.12.13_amd64.deb ...
  Unpacking linux-generic (4.18.0.12.13) over (4.18.0.11.12) ...
  Preparing to unpack .../4-linux-image-generic_4.18.0.12.13_amd64.deb ...
  Unpacking linux-image-generic (4.18.0.12.13) over (4.18.0.11.12) ...
  Selecting previously unselected package linux-headers-4.18.0-12.
  Preparing to unpack .../5-linux-headers-4.18.0-12_4.18.0-12.13_all.deb ...
  Unpacking linux-headers-4.18.0-12 (4.18.0-12.13) ...
  Selecting previously unselected package linux-headers-4.18.0-12-generic.
  Preparing to unpack 
.../6-linux-headers-4.18.0-12-generic_4.18.0-12.13_amd64.deb ...
  Unpacking linux-headers-4.18.0-12-generic (4.18.0-12.13) ...
  Preparing to unpack .../7-linux-headers-generic_4.18.0.12.13_amd64.deb ...
  Unpacking linux-headers-generic (4.18.0.12.13) over (4.18.0.11.12) ...
  Setting up linux-headers-4.18.0-12 (4.18.0-12.13) ...
  Setting up linux-modules-4.18.0-12-generic (4.18.0-12.13) ...
  Setting up linux-headers-4.18.0-12-generic (4.18.0-12.13) ...

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

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

[Kernel-packages] [Bug 1808635] Re: [nouveau] [Quadro FX 3800] no boot just red square on screen

[Expired for linux (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  [nouveau] [Quadro FX 3800] no boot just red square on screen

Status in linux package in Ubuntu:
  Expired

Bug description:
  no boot just red squar on screan

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.4.0-66.87-generic 4.4.44
  Uname: Linux 4.4.0-66-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CompositorRunning: None
  Date: Sat Dec 15 10:16:34 2018
  DistUpgraded: 2018-08-28 08:03:16,046 DEBUG icon theme changed, re-reading
  DistroCodename: bionic
  DistroVariant: ubuntu
  DpkgLog:
   
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard:
   NVIDIA Corporation GT200GL [Quadro FX 3800] [10de:05ff] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: NVIDIA Corporation GT200GL [Quadro FX 3800] [10de:0661]
  InstallationDate: Installed on 2016-09-30 (806 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: Hewlett-Packard HP Z400 Workstation
  ProcEnviron:
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-66-generic 
root=UUID=2aeb5d71-8879-4ee6-8084-763dda365c5a ro quiet splash vt.handoff=1
  Renderer: Software
  SourcePackage: xorg
  UpgradeStatus: Upgraded to bionic on 2018-08-28 (109 days ago)
  dmi.bios.date: 07/15/2013
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 786G3 v03.57
  dmi.board.asset.tag: 2UA935021D
  dmi.board.name: 0AE4h
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: C
  dmi.chassis.asset.tag: 2UA935021D
  dmi.chassis.type: 6
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr786G3v03.57:bd07/15/2013:svnHewlett-Packard:pnHPZ400Workstation:pvr:rvnHewlett-Packard:rn0AE4h:rvrC:cvnHewlett-Packard:ct6:cvr:
  dmi.product.name: HP Z400 Workstation
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
  xserver.bootTime: Tue Aug 28 22:26:33 2018
  xserver.configfile: default
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.19.6-1ubuntu4

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

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

[Kernel-packages] [Bug 1815857] Re: linux-firmware is missing ctefx-sbz.bin for snd_hda_codec_ca0132

2019-02-14 Thread Ben A

A recent driver contributor has made the blobs available here:

https://www.reddit.com/r/SoundBlasterOfficial/comments/9mm5ad/sound_blaster_r3dr3dizzxrae5_linux_driver/

No idea on the licensing situation.

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

Title:
  linux-firmware is missing ctefx-sbz.bin for snd_hda_codec_ca0132

Status in linux-firmware package in Ubuntu:
  Incomplete

Bug description:
  I'm not 100% sure what this firmware blob is actually used for, as the
  card is mostly functional without it and I'm not confident the broken
  bits aren't due to an incomplete driver, but it requests it for
  CA0132-based PCIe addin cards (Sound Blaster Recon3D, Z series, X
  AE-5).

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-firmware 1.173.3
  ProcVersionSignature: Ubuntu 4.18.0-15.16~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-15-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Feb 13 22:49:48 2019
  Dependencies:
   
  InstallationDate: Installed on 2018-09-12 (155 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-firmware
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1814733] Re: linux-azure: 4.18.0-1009.9~18.04.1 -proposed tracker

** Changed in: kernel-sru-workflow/automated-testing
   Status: Incomplete => In Progress

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  phase: Promote to Proposed
  phase-changed: Wednesday, 13. February 2019 14:03 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   automated-testing: Stalled -- testing FAILED
+   automated-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
snap-release-to-beta: Pending -- snap not in 18/beta channel
snap-release-to-edge: Pending -- snap not in 18/edge channel
stakeholder-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress

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

Title:
  linux-azure: 4.18.0-1009.9~18.04.1 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  In Progress
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow snap-release-to-beta series:
  Confirmed
Status in Kernel SRU Workflow snap-release-to-candidate series:
  New
Status in Kernel SRU Workflow snap-release-to-edge series:
  Confirmed
Status in Kernel SRU Workflow snap-release-to-stable series:
  Invalid
Status in Kernel SRU Workflow stakeholder-signoff series:
  Confirmed
Status in Kernel SRU Workflow upload-to-ppa-dnu series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-azure package in Ubuntu:
  Invalid
Status in linux-azure source package in Bionic:
  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
  phase: Promote to Proposed
  phase-changed: Wednesday, 13. February 2019 14:03 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
snap-release-to-beta: Pending -- snap not in 18/beta channel
snap-release-to-edge: Pending -- snap not in 18/edge channel
stakeholder-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress

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

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

[Kernel-packages] [Bug 1814733] Re: linux-azure: 4.18.0-1009.9~18.04.1 -proposed tracker

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  phase: Promote to Proposed
  phase-changed: Wednesday, 13. February 2019 14:03 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Stalled -- testing FAILED
-   regression-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
snap-release-to-beta: Pending -- snap not in 18/beta channel
snap-release-to-edge: Pending -- snap not in 18/edge channel
stakeholder-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress

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

Title:
  linux-azure: 4.18.0-1009.9~18.04.1 -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:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow snap-release-to-beta series:
  Confirmed
Status in Kernel SRU Workflow snap-release-to-candidate series:
  New
Status in Kernel SRU Workflow snap-release-to-edge series:
  Confirmed
Status in Kernel SRU Workflow snap-release-to-stable series:
  Invalid
Status in Kernel SRU Workflow stakeholder-signoff series:
  Confirmed
Status in Kernel SRU Workflow upload-to-ppa-dnu series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-azure package in Ubuntu:
  Invalid
Status in linux-azure source package in Bionic:
  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
  phase: Promote to Proposed
  phase-changed: Wednesday, 13. February 2019 14:03 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Stalled -- testing FAILED
security-signoff: Pending -- waiting for signoff
snap-release-to-beta: Pending -- snap not in 18/beta channel
snap-release-to-edge: Pending -- snap not in 18/edge channel
stakeholder-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress

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

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

[Kernel-packages] [Bug 1814733] Re: linux-azure: 4.18.0-1009.9~18.04.1 -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-azure in Ubuntu.
https://bugs.launchpad.net/bugs/1814733

Title:
  linux-azure: 4.18.0-1009.9~18.04.1 -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:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow snap-release-to-beta series:
  Confirmed
Status in Kernel SRU Workflow snap-release-to-candidate series:
  New
Status in Kernel SRU Workflow snap-release-to-edge series:
  Confirmed
Status in Kernel SRU Workflow snap-release-to-stable series:
  Invalid
Status in Kernel SRU Workflow stakeholder-signoff series:
  Confirmed
Status in Kernel SRU Workflow upload-to-ppa-dnu series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-azure package in Ubuntu:
  Invalid
Status in linux-azure source package in Bionic:
  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
  phase: Promote to Proposed
  phase-changed: Wednesday, 13. February 2019 14:03 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Stalled -- testing FAILED
security-signoff: Pending -- waiting for signoff
snap-release-to-beta: Pending -- snap not in 18/beta channel
snap-release-to-edge: Pending -- snap not in 18/edge channel
stakeholder-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress

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

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

[Kernel-packages] [Bug 1815579] Re: Broken dependencies with nvidia-driver-390 and xserver-xorg-hwe-18.04 in bionic

This bug was fixed in the package nvidia-graphics-drivers-390 -
390.77-0ubuntu0.18.04.2

---
nvidia-graphics-drivers-390 (390.77-0ubuntu0.18.04.2) bionic; urgency=medium

  * debian/rules.defs:
- Add support for xserver-xorg-core-hwe-18.04 (LP: #1815579).

 -- Alberto Milone   Thu, 14 Feb 2019
16:14:57 +0100

** Changed in: nvidia-graphics-drivers-390 (Ubuntu Bionic)
   Status: Fix Committed => Fix Released

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

Title:
  Broken dependencies with nvidia-driver-390 and xserver-xorg-hwe-18.04
  in bionic

Status in nvidia-graphics-drivers-340 package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-340 source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-390 source package in Bionic:
  Fix Released

Bug description:
  I am trying to test new HWE stack from 18.10 in my destkop Ubuntu
  18.04.1 (expected release 18.04.2 this week) and I have broken
  dependencies when installing `xserver-xorg-hwe-18.04` package with
  NVidia drivers:

  me@me-H110M-DS2:~$ sudo apt install xserver-xorg-hwe-18.04 
xserver-xorg-video-nvidia-390 
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  xserver-xorg-video-nvidia-390 is already the newest version 
(390.77-0ubuntu0.18.04.1).
  xserver-xorg-video-nvidia-390 set to manually installed.
  Some packages could not be installed. This may mean that you have
  requested an impossible situation or if you are using the unstable
  distribution that some required packages have not yet been created
  or been moved out of Incoming.
  The following information may help to resolve the situation:

  The following packages have unmet dependencies:
   xserver-xorg-hwe-18.04 : Depends: xserver-xorg-core-hwe-18.04 (>= 
2:1.17.2-2) but it is not going to be installed
Conflicts: xserver-xorg-core (>= 0~)
Recommends: xserver-xorg-video-all-hwe-18.04 but it 
is not going to be installed
  E: Unable to correct problems, you have held broken packages.

  
  Otherwise, if I try to install it without `xserver-xorg-video-nvidia-390` 
this happens:

  me@me-H110M-DS2:~$ sudo apt install xserver-xorg-hwe-18.04 
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  The following packages were automatically installed and are no longer 
required:
dkms libbsd0:i386 libdrm-amdgpu1:i386 libdrm-intel1:i386 
libdrm-nouveau2:i386 libdrm-radeon1:i386 libdrm2:i386 libedit2:i386 
libelf1:i386 libexpat1:i386 libffi6:i386 libgl1:i386 libgl1-mesa-dri:i386
libglapi-mesa:i386 libglvnd0:i386 libglx-mesa0:i386 libglx0:i386 
libllvm7:i386 libnvidia-cfg1-390 libnvidia-common-390 libnvidia-compute-390 
libnvidia-compute-390:i386 libnvidia-decode-390
libnvidia-decode-390:i386 libnvidia-encode-390 libnvidia-encode-390:i386 
libnvidia-fbc1-390 libnvidia-fbc1-390:i386 libnvidia-gl-390 
libnvidia-gl-390:i386 libnvidia-ifr1-390 libnvidia-ifr1-390:i386
libpciaccess0:i386 libsensors4:i386 libstdc++6:i386 libvdpau1 
libwayland-client0:i386 libwayland-server0:i386 libx11-6:i386 libx11-xcb1:i386 
libxau6:i386 libxcb-dri2-0:i386 libxcb-dri3-0:i386
libxcb-glx0:i386 libxcb-present0:i386 libxcb-sync1:i386 libxcb1:i386 
libxdamage1:i386 libxdmcp6:i386 libxext6:i386 libxfixes3:i386 libxnvctrl0 
libxshmfence1:i386 libxxf86vm1:i386 mesa-vdpau-drivers
nvidia-compute-utils-390 nvidia-dkms-390 nvidia-kernel-common-390 
nvidia-kernel-source-390 nvidia-prime nvidia-settings nvidia-utils-390 
pkg-config screen-resolution-extra vdpau-driver-all
  Use 'sudo apt autoremove' to remove them.
  The following additional packages will be installed:
xserver-xorg-core-hwe-18.04 xserver-xorg-input-all-hwe-18.04 
xserver-xorg-input-libinput-hwe-18.04 xserver-xorg-video-all-hwe-18.04 
xserver-xorg-video-amdgpu-hwe-18.04 xserver-xorg-video-ati-hwe-18.04
xserver-xorg-video-fbdev-hwe-18.04 xserver-xorg-video-intel-hwe-18.04 
xserver-xorg-video-nouveau-hwe-18.04 xserver-xorg-video-qxl-hwe-18.04 
xserver-xorg-video-radeon-hwe-18.04
xserver-xorg-video-vesa-hwe-18.04 xserver-xorg-video-vmware-hwe-18.04
  Suggested packages:
xfonts-100dpi | xfonts-75dpi firmware-amd-graphics xserver-xorg-video-r128 
xserver-xorg-video-mach64 firmware-misc-nonfree
  Recommended packages:
xserver-xorg-input-wacom-hwe-18.04
  The following packages will be REMOVED:
nvidia-driver-390 xserver-xorg xserver-xorg-core xserver-xorg-input-all 
xserver-xorg-input-libinput xserver-xorg-video-nvidia-390
  The following NEW packages will be installed:
xserver-xorg-core-hwe-18.04 xserver-xorg-hwe-18.04 
xserver-xorg-input-all-hwe-18.04 xserver-xorg-input-libinput-hwe-18.04

[Kernel-packages] [Bug 1815579] Re: Broken dependencies with nvidia-driver-390 and xserver-xorg-hwe-18.04 in bionic

This bug was fixed in the package nvidia-graphics-drivers-340 -
340.107-0ubuntu0.18.04.2

---
nvidia-graphics-drivers-340 (340.107-0ubuntu0.18.04.2) bionic; urgency=medium

  * Add support for xserver-xorg-core-hwe-18.04 (LP: #1815579).

 -- Alberto Milone   Thu, 14 Feb 2019
16:48:59 +0100

** Changed in: nvidia-graphics-drivers-340 (Ubuntu Bionic)
   Status: Fix Committed => Fix Released

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

Title:
  Broken dependencies with nvidia-driver-390 and xserver-xorg-hwe-18.04
  in bionic

Status in nvidia-graphics-drivers-340 package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-340 source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-390 source package in Bionic:
  Fix Released

Bug description:
  I am trying to test new HWE stack from 18.10 in my destkop Ubuntu
  18.04.1 (expected release 18.04.2 this week) and I have broken
  dependencies when installing `xserver-xorg-hwe-18.04` package with
  NVidia drivers:

  me@me-H110M-DS2:~$ sudo apt install xserver-xorg-hwe-18.04 
xserver-xorg-video-nvidia-390 
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  xserver-xorg-video-nvidia-390 is already the newest version 
(390.77-0ubuntu0.18.04.1).
  xserver-xorg-video-nvidia-390 set to manually installed.
  Some packages could not be installed. This may mean that you have
  requested an impossible situation or if you are using the unstable
  distribution that some required packages have not yet been created
  or been moved out of Incoming.
  The following information may help to resolve the situation:

  The following packages have unmet dependencies:
   xserver-xorg-hwe-18.04 : Depends: xserver-xorg-core-hwe-18.04 (>= 
2:1.17.2-2) but it is not going to be installed
Conflicts: xserver-xorg-core (>= 0~)
Recommends: xserver-xorg-video-all-hwe-18.04 but it 
is not going to be installed
  E: Unable to correct problems, you have held broken packages.

  
  Otherwise, if I try to install it without `xserver-xorg-video-nvidia-390` 
this happens:

  me@me-H110M-DS2:~$ sudo apt install xserver-xorg-hwe-18.04 
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  The following packages were automatically installed and are no longer 
required:
dkms libbsd0:i386 libdrm-amdgpu1:i386 libdrm-intel1:i386 
libdrm-nouveau2:i386 libdrm-radeon1:i386 libdrm2:i386 libedit2:i386 
libelf1:i386 libexpat1:i386 libffi6:i386 libgl1:i386 libgl1-mesa-dri:i386
libglapi-mesa:i386 libglvnd0:i386 libglx-mesa0:i386 libglx0:i386 
libllvm7:i386 libnvidia-cfg1-390 libnvidia-common-390 libnvidia-compute-390 
libnvidia-compute-390:i386 libnvidia-decode-390
libnvidia-decode-390:i386 libnvidia-encode-390 libnvidia-encode-390:i386 
libnvidia-fbc1-390 libnvidia-fbc1-390:i386 libnvidia-gl-390 
libnvidia-gl-390:i386 libnvidia-ifr1-390 libnvidia-ifr1-390:i386
libpciaccess0:i386 libsensors4:i386 libstdc++6:i386 libvdpau1 
libwayland-client0:i386 libwayland-server0:i386 libx11-6:i386 libx11-xcb1:i386 
libxau6:i386 libxcb-dri2-0:i386 libxcb-dri3-0:i386
libxcb-glx0:i386 libxcb-present0:i386 libxcb-sync1:i386 libxcb1:i386 
libxdamage1:i386 libxdmcp6:i386 libxext6:i386 libxfixes3:i386 libxnvctrl0 
libxshmfence1:i386 libxxf86vm1:i386 mesa-vdpau-drivers
nvidia-compute-utils-390 nvidia-dkms-390 nvidia-kernel-common-390 
nvidia-kernel-source-390 nvidia-prime nvidia-settings nvidia-utils-390 
pkg-config screen-resolution-extra vdpau-driver-all
  Use 'sudo apt autoremove' to remove them.
  The following additional packages will be installed:
xserver-xorg-core-hwe-18.04 xserver-xorg-input-all-hwe-18.04 
xserver-xorg-input-libinput-hwe-18.04 xserver-xorg-video-all-hwe-18.04 
xserver-xorg-video-amdgpu-hwe-18.04 xserver-xorg-video-ati-hwe-18.04
xserver-xorg-video-fbdev-hwe-18.04 xserver-xorg-video-intel-hwe-18.04 
xserver-xorg-video-nouveau-hwe-18.04 xserver-xorg-video-qxl-hwe-18.04 
xserver-xorg-video-radeon-hwe-18.04
xserver-xorg-video-vesa-hwe-18.04 xserver-xorg-video-vmware-hwe-18.04
  Suggested packages:
xfonts-100dpi | xfonts-75dpi firmware-amd-graphics xserver-xorg-video-r128 
xserver-xorg-video-mach64 firmware-misc-nonfree
  Recommended packages:
xserver-xorg-input-wacom-hwe-18.04
  The following packages will be REMOVED:
nvidia-driver-390 xserver-xorg xserver-xorg-core xserver-xorg-input-all 
xserver-xorg-input-libinput xserver-xorg-video-nvidia-390
  The following NEW packages will be installed:
xserver-xorg-core-hwe-18.04 xserver-xorg-hwe-18.04 
xserver-xorg-input-all-hwe-18.04 xserver-xorg-input-libinput-hwe-18.04 
xserver-xorg-video-all-hwe-18.04

[Kernel-packages] [Bug 1815579] Update Released

2019-02-14 Thread Adam Conrad

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

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

Title:
  Broken dependencies with nvidia-driver-390 and xserver-xorg-hwe-18.04
  in bionic

Status in nvidia-graphics-drivers-340 package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-340 source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-390 source package in Bionic:
  Fix Released

Bug description:
  I am trying to test new HWE stack from 18.10 in my destkop Ubuntu
  18.04.1 (expected release 18.04.2 this week) and I have broken
  dependencies when installing `xserver-xorg-hwe-18.04` package with
  NVidia drivers:

  me@me-H110M-DS2:~$ sudo apt install xserver-xorg-hwe-18.04 
xserver-xorg-video-nvidia-390 
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  xserver-xorg-video-nvidia-390 is already the newest version 
(390.77-0ubuntu0.18.04.1).
  xserver-xorg-video-nvidia-390 set to manually installed.
  Some packages could not be installed. This may mean that you have
  requested an impossible situation or if you are using the unstable
  distribution that some required packages have not yet been created
  or been moved out of Incoming.
  The following information may help to resolve the situation:

  The following packages have unmet dependencies:
   xserver-xorg-hwe-18.04 : Depends: xserver-xorg-core-hwe-18.04 (>= 
2:1.17.2-2) but it is not going to be installed
Conflicts: xserver-xorg-core (>= 0~)
Recommends: xserver-xorg-video-all-hwe-18.04 but it 
is not going to be installed
  E: Unable to correct problems, you have held broken packages.

  
  Otherwise, if I try to install it without `xserver-xorg-video-nvidia-390` 
this happens:

  me@me-H110M-DS2:~$ sudo apt install xserver-xorg-hwe-18.04 
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  The following packages were automatically installed and are no longer 
required:
dkms libbsd0:i386 libdrm-amdgpu1:i386 libdrm-intel1:i386 
libdrm-nouveau2:i386 libdrm-radeon1:i386 libdrm2:i386 libedit2:i386 
libelf1:i386 libexpat1:i386 libffi6:i386 libgl1:i386 libgl1-mesa-dri:i386
libglapi-mesa:i386 libglvnd0:i386 libglx-mesa0:i386 libglx0:i386 
libllvm7:i386 libnvidia-cfg1-390 libnvidia-common-390 libnvidia-compute-390 
libnvidia-compute-390:i386 libnvidia-decode-390
libnvidia-decode-390:i386 libnvidia-encode-390 libnvidia-encode-390:i386 
libnvidia-fbc1-390 libnvidia-fbc1-390:i386 libnvidia-gl-390 
libnvidia-gl-390:i386 libnvidia-ifr1-390 libnvidia-ifr1-390:i386
libpciaccess0:i386 libsensors4:i386 libstdc++6:i386 libvdpau1 
libwayland-client0:i386 libwayland-server0:i386 libx11-6:i386 libx11-xcb1:i386 
libxau6:i386 libxcb-dri2-0:i386 libxcb-dri3-0:i386
libxcb-glx0:i386 libxcb-present0:i386 libxcb-sync1:i386 libxcb1:i386 
libxdamage1:i386 libxdmcp6:i386 libxext6:i386 libxfixes3:i386 libxnvctrl0 
libxshmfence1:i386 libxxf86vm1:i386 mesa-vdpau-drivers
nvidia-compute-utils-390 nvidia-dkms-390 nvidia-kernel-common-390 
nvidia-kernel-source-390 nvidia-prime nvidia-settings nvidia-utils-390 
pkg-config screen-resolution-extra vdpau-driver-all
  Use 'sudo apt autoremove' to remove them.
  The following additional packages will be installed:
xserver-xorg-core-hwe-18.04 xserver-xorg-input-all-hwe-18.04 
xserver-xorg-input-libinput-hwe-18.04 xserver-xorg-video-all-hwe-18.04 
xserver-xorg-video-amdgpu-hwe-18.04 xserver-xorg-video-ati-hwe-18.04
xserver-xorg-video-fbdev-hwe-18.04 xserver-xorg-video-intel-hwe-18.04 
xserver-xorg-video-nouveau-hwe-18.04 xserver-xorg-video-qxl-hwe-18.04 
xserver-xorg-video-radeon-hwe-18.04
xserver-xorg-video-vesa-hwe-18.04 xserver-xorg-video-vmware-hwe-18.04
  Suggested packages:
xfonts-100dpi | xfonts-75dpi firmware-amd-graphics xserver-xorg-video-r128 
xserver-xorg-video-mach64 firmware-misc-nonfree
  Recommended packages:
xserver-xorg-input-wacom-hwe-18.04
  The following packages will be REMOVED:
nvidia-driver-390 xserver-xorg xserver-xorg-core xserver-xorg-input-all 
xserver-xorg-input-libinput xserver-xorg-video-nvidia-390
  The following NEW packages will be installed:
xserver-xorg-core-hwe-18.04 xserver-xorg-hwe-18.04 
xserver-xorg-input-all-hwe-18.04

Re: [Kernel-packages] [Bug 1734147] Re: corrupted BIOS due to Intel SPI bug in kernel

2019-02-14 Thread Steve Langasek

On Thu, Feb 14, 2019 at 10:44:34PM -, Marek Hák wrote:
> The output of 'efibootmgr -v' showed me where the EFI partition is, but
> I have no idea where it's mounted or how to get to it.

> Boot0004* ubuntuHD(2,GPT,83484852-541d-401e-
> 84e7-6e6e8549496a,0x1f4800,0x82000)/File(\EFI\ubuntu\shimx64.efi)

OK, this should be either sda2 or sdb2 depending on which order your disks
were detected. So you should be able to do sudo mount /dev/sda2 /boot/efi
to mount it (or /dev/sdb2, depending).

Then once you have replaced that grubx64.efi with the one that allows
booting unsigned kernels, you should run 'sudo umount /boot/efi' to make
sure the disk is cleanly unmounted. After this, you should have a
secureboot-enabled grub on the internal disk which allows you to boot to a
different unsigned kernel on the flash drive in order to reset the firmware
state.

> Thanks again for any help! I'd really love to sort this out :)

Sorry this is such a mess.

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

Title:
corrupted BIOS due to Intel SPI bug in kernel

Status in Linux:
Unknown
Status in linux package in Ubuntu:
Fix Released
Status in linux-hwe-edge source package in Xenial:
Fix Released
Status in linux-oem source package in Xenial:
Fix Released
Status in linux source package in Artful:
Fix Released

Bug description:
An update to linux kernel on Ubuntu 17.10 that enabled the Intel SPI
drivers results in a serial flash that is read only in Intel Broadwell
and Haswell machines with serial flashes with SPI_NOR_HAS_LOCK set.

Symptoms:
* BIOS settings cannot be saved
* USB Boot impossible
* EFI entries read-only.

---

Fix: The issue was fixed in kernel version 4.13.0-21 by configuring
the kernel so it is not compiled with Intel SPI support. But previous
affected machines still suffered from a broken BIOS.

Repair: If you still can boot into Ubuntu, you can recover your BIOS
with the following steps:

1. Boot into Ubuntu
2. Download
http://people.canonical.com/~ypwong/lp1734147/linux-image-4.15.0-041500rc6-generic_4.15.0-041500rc6.201712312330+20170103+1_amd64.deb
3. Install the downloaded package:
$ sudo dpkg -i
linux-image-4.15.0-041500rc6-generic_4.15.0-041500rc6.201712312330+20170103+1_amd64.deb
4. Make sure the kernel is installed without any error. Once installed,
reboot.
5. At grub, choose the newly installed kernel. You can choose the "recovery"
mode.
6. Reboot and go to BIOS settings to confirm your BIOS has been recovered.
7. In case your BIOS is not recovered, reboot to the new kernel, then reboot
*once again* to the new kernel, do not enter BIOS settings before the reboot.
After the second reboot, check BIOS.
8. If your BIOS issue remains, download another kernel from
http://people.canonical.com/~ypwong/lp1734147/linux-image-4.15.0-041500rc6-generic_4.15.0-041500rc6.201712312330+clear+debug_amd64.deb,
and use dpkg to install it, then repeat steps 4 to 6.

After your BIOS is fixed, the kernel packages you just installed are
no longer needed, you can remove it by running 'sudo dpkg -r linux-
image-4.15.0-041500rc6-generic'.

The patch used to build the linux v4.15 kernel in step 8 can be found
at https://goo.gl/xUKJFR.

If you have applied updates, and find that you can not boot the above fixed
kernel because of Secure Boot and that the kernel is unsigned, but can still
boot another kernel for your system; here's what you can do:

1) Download
http://archive.ubuntu.com/ubuntu/dists/xenial-updates/main/uefi/grub2-amd64/2.02~beta2-36ubuntu3.20/grubx64.efi.signed:
$ wget
http://archive.ubuntu.com/ubuntu/dists/xenial-updates/main/uefi/grub2-amd64/2.02~beta2-36ubuntu3.20/grubx64.efi.signed

2) Copy grubx64.efi.signed over /boot/efi/EFI/ubuntu/grubx64.efi:
$ sudo cp grubx64.efi.signed /boot/efi/EFI/ubuntu/grubx64.efi

3) Reboot; you should now be able to load the new unsigned kernel that
allows fixing firmware / SPI.

4) Once you're satisfied that things work; boot to Ubuntu with a
standard, signed kernel, and re-install the right GRUB version for
your system:

$ sudo grub-install

---

Test Case: Fix has been verified by our HWE team on affected hardware.

Regression Potential: Minimal, it's unlikely anyone is actually doing
anything which requires this driver.

---

Affected Machines:

Lenovo B40-70
Lenovo B50-70
Lenovo B50-80
Lenovo Flex-3
Lenovo Flex-10
Lenovo G40-30
Lenovo G50-30
Lenovo G50-70
Lenovo G50-80
Lenovo S20-30
Lenovo U31-70
Lenovo Y50-70
Lenovo Y70-70
Lenovo Yoga Thinkpad (20C0)
Lenovo Yoga 2 11" - 20332
Lenovo Yoga 3 11"
Lenovo Z50-70
Lenovo Z51-70
Lenovo ideapad 100-15IBY

Acer Aspire E5-771G
Acer Aspire ES1-111M-C1LE (fixed following your new instruction (thank you))
Acer TravelMate B113
Acer Swift SF314-52

[Kernel-packages] [Bug 1734147] Re: corrupted BIOS due to Intel SPI bug in kernel

2019-02-14 Thread Marek Hák

The output of 'efibootmgr -v' showed me where the EFI partition is, but
I have no idea where it's mounted or how to get to it.

Boot0004* ubuntuHD(2,GPT,83484852-541d-401e-
84e7-6e6e8549496a,0x1f4800,0x82000)/File(\EFI\ubuntu\shimx64.efi)

Some info that may help:

I do not have the current ubuntu installed on the hard drive itself,
it's installed on a flash drive. My old grub got corrupted or partially
deleted, so now I only have the minimal-bash editing grub. I boot from
the flash drive with:

set prefix=(hd0,msdos2)/boot/grub/
set root=(hd0,msdos2)
insmod normal
normal

After that, I get into a normal grub, that's probably located somewhere
on the flash drive.

The ubuntu on the flash drive was installed on another computer, and
just brought over to the laptop.

Thanks again for any help! I'd really love to sort this out :)

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

Title:
corrupted BIOS due to Intel SPI bug in kernel

Symptoms:
* BIOS settings cannot be saved
* USB Boot impossible
* EFI entries read-only.

---

Fix: The issue was fixed in kernel version 4.13.0-21 by configuring
the kernel so it is not compiled with Intel SPI support. But previous
affected machines still suffered from a broken BIOS.

Repair: If you still can boot into Ubuntu, you can recover your BIOS
with the following steps:

After your BIOS is fixed, the kernel packages you just installed are
no longer needed, you can remove it by running 'sudo dpkg -r linux-
image-4.15.0-041500rc6-generic'.

The patch used to build the linux v4.15 kernel in step 8 can be found
at https://goo.gl/xUKJFR.

2) Copy grubx64.efi.signed over /boot/efi/EFI/ubuntu/grubx64.efi:
$ sudo cp grubx64.efi.signed /boot/efi/EFI/ubuntu/grubx64.efi

3) Reboot; you should now be able to load the new unsigned kernel that
allows fixing firmware / SPI.

4) Once you're satisfied that things work; boot to Ubuntu with a
standard, signed kernel, and re-install the right GRUB version for
your system:

$ sudo grub-install

---

Test Case: Fix has been verified by our HWE team on affected hardware.

Regression Potential: Minimal, it's unlikely anyone is actually doing
anything which requires this driver.

---

Affected Machines:

[Kernel-packages] [Bug 1815952] Re: Mute key LED does not work on HP Pavilion x360

2019-02-14 Thread Bug Watch Updater

Launchpad has imported 2 comments from the remote bug at
https://bugzilla.kernel.org/show_bug.cgi?id=202581.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2019-02-14T19:24:52+00:00 romanescu.2019 wrote:

Open bug in launchpad.net:
https://bugs.launchpad.net/bugs/1815952

---

Description of problem:
The F6/mute key on the keyboard of HP notebooks often has a built in LED 
indicator to show if the sound is muted. The LED state is never toggled. It 
will just retain its state, even though the audio is succesfully muted/unmuted.

Tested with HP Pavilion x360 from 2018.

Version-Release number of selected component (if applicable):

How reproducible:
Always.

Steps to Reproduce:
1. Press mute key on HP laptop

Actual results:
Mute state in software toggles, LED in mute key does not.

Expected results:
Mute state in software and LED in mute key toggle.

Additional info:
This happens on kernel 4.20.8

Other similar errors:
* https://bugs.launchpad.net/bugs/1683277
* https://bugs.launchpad.net/bugs/1705586

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1815952/comments/2


On 2019-02-14T20:55:58+00:00 romanescu.2019 wrote:

Ok.

My first patch for the linux kernel:
https://github.com/caravena/linux/commit/c540283416a7756dedaa72aa66a00c897517b113#diff-f52b6863505adc3b972c64d4a22195cc

I would like to have credits for this patch (:

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1815952/comments/7


** Changed in: linux
   Status: Unknown => Confirmed

** Changed in: linux
   Importance: Unknown => 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/1815952

Title:
  Mute key LED does not work on HP Pavilion x360

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

Bug description:
  Description of problem:
  The F6/mute key on the keyboard of HP notebooks often has a built in LED 
indicator to show if the sound is muted. The LED state is never toggled. It 
will just retain its state, even though the audio is succesfully muted/unmuted.

  Tested with HP Pavilion x360 from 2018.

  Version-Release number of selected component (if applicable):

  How reproducible:
  Always.

  Steps to Reproduce:
  1. Press mute key on HP laptop

  Actual results:
  Mute state in software toggles, LED in mute key does not.

  Expected results:
  Mute state in software and LED in mute key toggle.

  Additional info:
  This happens on kernel 4.20.8

  Other similar errors:
  * https://bugs.launchpad.net/bugs/1683277
  * https://bugs.launchpad.net/bugs/1705586

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: linux-image-4.19.0-12-generic 4.19.0-12.13
  ProcVersionSignature: Ubuntu 4.19.0-12.13-generic 4.19.18
  Uname: Linux 4.19.0-12-generic x86_64
  ApportVersion: 2.20.10-0ubuntu20
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  caravena   2337 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Feb 14 15:56:54 2019
  HibernationDevice: RESUME=UUID=efcf081f-0bb0-4907-b78c-1299aa4aee57
  InstallationDate: Installed on 2018-12-02 (74 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: HP HP Pavilion x360 Convertible 14-cd0xxx
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.19.0-12-generic 
root=UUID=28bdadba-133c-4f5b-a5c9-b06993ea7ce2 ro rootflags=subvol=@ quiet 
splash vt.handoff=1
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Daemon 
not responding.
  RelatedPackageVersions:
   linux-restricted-modules-4.19.0-12-generic N/A
   linux-backports-modules-4.19.0-12-generic  N/A
   linux-firmware 1.177
  SourcePackage: linux
  UpgradeStatus: Upgraded to disco on 2018-12-02 (73 days ago)
  dmi.bios.date: 11/08/2018
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.32
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 8486
  dmi.board.vendor: HP
  dmi.board.version: 72.23
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.32:bd11/08/2018:svnHP:pnHPPavilionx360Convertible14-cd0xxx:pvrType1ProductConfigId:rvnHP:rn8486:rvr72.23:cvnHP:ct31:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Pavilion
  dmi.product.name: HP Pavilion x360 Convertible 14-cd0xxx
  dmi.product.sku: 3PX63LA#ABM
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP

To manage notifications about this bug go to:

[Kernel-packages] [Bug 1814393] Re: "make: write error: stdout" on parallel builds

2019-02-14 Thread Scott Kazimour

This happens for me with 18.04, kernel 4.15.0-45-generic.

It does not happen with 4.15.0-43-generic.

Running on xterm (as opposed to terminator) it still happens, but much
later in the build.

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

Title:
"make: write error: stdout" on parallel builds

Status in linux-signed package in Ubuntu:
Confirmed

Bug description:
- Release of Ubuntu: 18.04.1 LTS (Kubuntu).
- Package version: linux-image-4.15.0-44-generic,
linux-image-4.15.0-45-generic.
- Expected outcome: Large parallel make build completing properly.
- What happened instead: Build stops with "make: write error: stdout".

Full explanation:

Since the update to kernel 4.15.0-44 (linux-image-4.15.0-44-generic)
in Kubuntu Bionic I'm experiencing issues in my ThinkPad P52 laptop
during large parallel builds of source code (eg: a buildroot full
rebuild for a work project). Note that this reports isn't about kernel
builds, but about large project builds in general.

I don't think it's relevant, but I'm running those builds in an
schroot with the same Ubuntu Bionic distro I'm also using as main host
distro.

The specific error I get is this (in Spanish):

make[4]: error al escribir: stdout

I call Buildroot's make like this from KDE Konsole with "infinite
history buffer" enabled (uses a tmp file to store the logs):

V=1 make ...some stuff... 2>&1

However, the error is reproducible in Konsole even if I call make
without options and also if I use "limited (in-memory) history buffer"
as well as "no history buffer". Buildroot autoselects a
parallelization level (-j) automatically. In my case, I'm using a Xeon
E-2176 CPU with 12 threads.

Searching on the Internet I found a thread[1] where people from the
GNU Make project say that the error may be coming from the C runtime
library (and I suspect originating from the kernel).

I can NOT reproduce the issue on linux-image-4.15.0-43-generic
(selected from grub at boot), but I experience it with linux-
image-4.15.0-44-generic and linux-image-4.15.0-45-generic. That's why
I'm reporting this bug against the linux package.

Interestingly enough, I can NOT reproduce the issue on linux-
image-4.15.0-45-generic (haven't tried previous versions) when
building from xterm instead of Konsole. Unfortunately, this laptop has
a 4K screen and xterm isn't an option for me.

If I build redirecting stdout and stderr to different files to avoid
terminal output and then watching the stdout file with tail -f, the
tail command eventually finishes although the build continues and I
can keep watching it by running tail again. An infinite build loop
never finishes with this redirection (error not reproducible). Same
results with the 2>&1 redirection to a single file.

All this looks a bit like a poltergeist, but the only thing I'm sure
about is that it all started with the upgrade from 4.15.0-43 to -44
and it continues on -45.

Thank you.

[1]
http://gnu-make.2324884.n4.nabble.com/Spurious-quot-write-error-quot-on-parallel-builds-td15695.html

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

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

[Kernel-packages] [Bug 1802021] Re: [Hyper-V] srcu: Lock srcu_data structure in srcu_gp_start()

2019-02-14 Thread David Coronel

@lazamarius1: Just to clarify, the fix is scheduled to go in the 4.15
kernel in Bionic which is the same kernel as the Xenial HWE kernel. So
there's no need to add anything to the Affects section. You will see a
new linux-hwe 4.15 kernel in xenial-proposed once this is ready to test.
Thanks!

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

Title:
  [Hyper-V] srcu: Lock srcu_data structure in srcu_gp_start()

Status in linux package in Ubuntu:
  Confirmed
Status in linux-azure package in Ubuntu:
  Confirmed
Status in linux source package in Bionic:
  Confirmed
Status in linux-azure source package in Bionic:
  Fix Committed
Status in linux source package in Cosmic:
  Confirmed
Status in linux-azure source package in Cosmic:
  Fix Committed

Bug description:
  We had a customer seeing traces like the following:

  tack trace from kern.log:
  2018-10-10T04:43:08.542464+00:00 hbp2ann-2 kernel: INFO: task 
kworker/u16:0:16678 blocked for more than 120 seconds.
  2018-10-10T04:43:08.542503+00:00 hbp2ann-2 kernel: Not tainted 
4.15.0-1023-azure #24~16.04.1-Ubuntu
  2018-10-10T04:43:08.542513+00:00 hbp2ann-2 kernel: "echo 0 > 
/proc/sys/kernel/hung_task_timeout_secs" disables this message.
  2018-10-10T04:43:08.547366+00:00 hbp2ann-2 kernel: kworker/u16:0 D 0 16678 2 
0x8000
  2018-10-10T04:43:08.547386+00:00 hbp2ann-2 kernel: Workqueue: events_unbound 
fsnotify_mark_destroy_workfn
  2018-10-10T04:43:08.547395+00:00 hbp2ann-2 kernel: Call Trace:
  2018-10-10T04:43:08.547413+00:00 hbp2ann-2 kernel: __schedule+0x3d6/0x8b0
  2018-10-10T04:43:08.547422+00:00 hbp2ann-2 kernel: ? 
check_preempt_wakeup+0xfb/0x240
  2018-10-10T04:43:08.547431+00:00 hbp2ann-2 kernel: ? 
sched_clock_local+0x17/0x90
  2018-10-10T04:43:08.547440+00:00 hbp2ann-2 kernel: schedule+0x36/0x80
  2018-10-10T04:43:08.547448+00:00 hbp2ann-2 kernel: 
schedule_timeout+0x1db/0x370
  2018-10-10T04:43:08.547458+00:00 hbp2ann-2 kernel: ? 
__enqueue_entity+0x5c/0x60
  2018-10-10T04:43:08.547467+00:00 hbp2ann-2 kernel: ? 
enqueue_entity+0x112/0x670
  2018-10-10T04:43:08.547477+00:00 hbp2ann-2 kernel: 
wait_for_completion+0xb4/0x140
  2018-10-10T04:43:08.547486+00:00 hbp2ann-2 kernel: ? wake_up_q+0x70/0x70
  2018-10-10T04:43:08.547510+00:00 hbp2ann-2 kernel: 
__synchronize_srcu.part.13+0x85/0xb0
  2018-10-10T04:43:08.547535+00:00 hbp2ann-2 kernel: ? 
trace_raw_output_rcu_utilization+0x50/0x50
  2018-10-10T04:43:08.547560+00:00 hbp2ann-2 kernel: synchronize_srcu+0xd3/0xe0
  2018-10-10T04:43:08.547594+00:00 hbp2ann-2 kernel: ? 
synchronize_srcu+0xd3/0xe0
  2018-10-10T04:43:08.547604+00:00 hbp2ann-2 kernel: 
fsnotify_mark_destroy_workfn+0x7c/0xe0
  2018-10-10T04:43:08.547612+00:00 hbp2ann-2 kernel: 
process_one_work+0x14d/0x410
  2018-10-10T04:43:08.547620+00:00 hbp2ann-2 kernel: worker_thread+0x4b/0x460
  2018-10-10T04:43:08.547628+00:00 hbp2ann-2 kernel: kthread+0x105/0x140
  2018-10-10T04:43:08.547637+00:00 hbp2ann-2 kernel: ? 
process_one_work+0x410/0x410
  2018-10-10T04:43:08.547645+00:00 hbp2ann-2 kernel: ? 
kthread_destroy_worker+0x50/0x50
  2018-10-10T04:43:08.547654+00:00 hbp2ann-2 kernel: ? do_syscall_64+0x73/0x130
  2018-10-10T04:43:08.547677+00:00 hbp2ann-2 kernel: ? SyS_exit_group+0x14/0x20
  2018-10-10T04:43:08.547685+00:00 hbp2ann-2 kernel: ret_from_fork+0x35/0x40

  Error Code: INFO: task kworker/u16:0:16678 blocked for more than 120
  seconds.

  We are seeing more issue with fsnotify related callbacks. These are
  not a soft/hard lockup but seem to significantly degrade the
  responsiveness of systemd (and from there everything else).

  The following upstream commit may fix this issue, but it is in Paul's
  RCU tree and not in linux-next or upstream yet:

  https://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-
  rcu.git/commit/?h=dev=1a05c0cd2fee234a10362cc8f66057557cbb291f

  srcu: Lock srcu_data structure in srcu_gp_start()
  The srcu_gp_start() function is called with the srcu_struct structure's
  ->lock held, but not with the srcu_data structure's ->lock.  This is
  problematic because this function accesses and updates the srcu_data
  structure's ->srcu_cblist, which is protected by that lock.  Failing to
  hold this lock can result in corruption of the SRCU callback lists,
  which in turn can result in arbitrarily bad results.

  This commit therefore makes srcu_gp_start() acquire the srcu_data
  structure's ->lock across the calls to rcu_segcblist_advance() and
  rcu_segcblist_accelerate(), thus preventing this corruption.

  Please investigate this issue and evaluate the proposed fix.

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

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

[Kernel-packages] [Bug 1815952] Re: Mute key LED does not work on HP Pavilion x360

Ok.

My first patch for the linux kernel:
https://github.com/caravena/linux/commit/c540283416a7756dedaa72aa66a00c897517b113#diff-f52b6863505adc3b972c64d4a22195cc

I would like to have credits for this patch (:

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

Title:
  Mute key LED does not work on HP Pavilion x360

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

Bug description:
  Description of problem:
  The F6/mute key on the keyboard of HP notebooks often has a built in LED 
indicator to show if the sound is muted. The LED state is never toggled. It 
will just retain its state, even though the audio is succesfully muted/unmuted.

  Tested with HP Pavilion x360 from 2018.

  Version-Release number of selected component (if applicable):

  How reproducible:
  Always.

  Steps to Reproduce:
  1. Press mute key on HP laptop

  Actual results:
  Mute state in software toggles, LED in mute key does not.

  Expected results:
  Mute state in software and LED in mute key toggle.

  Additional info:
  This happens on kernel 4.20.8

  Other similar errors:
  * https://bugs.launchpad.net/bugs/1683277
  * https://bugs.launchpad.net/bugs/1705586

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: linux-image-4.19.0-12-generic 4.19.0-12.13
  ProcVersionSignature: Ubuntu 4.19.0-12.13-generic 4.19.18
  Uname: Linux 4.19.0-12-generic x86_64
  ApportVersion: 2.20.10-0ubuntu20
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  caravena   2337 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Feb 14 15:56:54 2019
  HibernationDevice: RESUME=UUID=efcf081f-0bb0-4907-b78c-1299aa4aee57
  InstallationDate: Installed on 2018-12-02 (74 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: HP HP Pavilion x360 Convertible 14-cd0xxx
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.19.0-12-generic 
root=UUID=28bdadba-133c-4f5b-a5c9-b06993ea7ce2 ro rootflags=subvol=@ quiet 
splash vt.handoff=1
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Daemon 
not responding.
  RelatedPackageVersions:
   linux-restricted-modules-4.19.0-12-generic N/A
   linux-backports-modules-4.19.0-12-generic  N/A
   linux-firmware 1.177
  SourcePackage: linux
  UpgradeStatus: Upgraded to disco on 2018-12-02 (73 days ago)
  dmi.bios.date: 11/08/2018
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.32
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 8486
  dmi.board.vendor: HP
  dmi.board.version: 72.23
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.32:bd11/08/2018:svnHP:pnHPPavilionx360Convertible14-cd0xxx:pvrType1ProductConfigId:rvnHP:rn8486:rvr72.23:cvnHP:ct31:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Pavilion
  dmi.product.name: HP Pavilion x360 Convertible 14-cd0xxx
  dmi.product.sku: 3PX63LA#ABM
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP

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

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

[Kernel-packages] [Bug 1814733] Re: linux-azure: 4.18.0-1009.9~18.04.1 -proposed tracker

2019-02-14 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-azure in Ubuntu.
https://bugs.launchpad.net/bugs/1814733

Title:
  linux-azure: 4.18.0-1009.9~18.04.1 -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:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow snap-release-to-beta series:
  Confirmed
Status in Kernel SRU Workflow snap-release-to-candidate series:
  New
Status in Kernel SRU Workflow snap-release-to-edge series:
  Confirmed
Status in Kernel SRU Workflow snap-release-to-stable series:
  Invalid
Status in Kernel SRU Workflow stakeholder-signoff series:
  Confirmed
Status in Kernel SRU Workflow upload-to-ppa-dnu series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-azure package in Ubuntu:
  Invalid
Status in linux-azure source package in Bionic:
  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
  phase: Promote to Proposed
  phase-changed: Wednesday, 13. February 2019 14:03 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Stalled -- testing FAILED
regression-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
snap-release-to-beta: Pending -- snap not in 18/beta channel
snap-release-to-edge: Pending -- snap not in 18/edge channel
stakeholder-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress

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

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

[Kernel-packages] [Bug 1815952] Re: Mute key LED does not work on HP Pavilion x360

$ lspci
-> Audio device [0403]: Intel Corporation Sunrise Point-LP HD Audio [8086:9d71] 
(rev 21)?

Add line(?):
+ SND_PCI_QUIRK(0x103c, 0x8086, "HP Pavilion x360", CXT_FIXUP_MUTE_LED_GPIO),

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

Title:
  Mute key LED does not work on HP Pavilion x360

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

Bug description:
  Description of problem:
  The F6/mute key on the keyboard of HP notebooks often has a built in LED 
indicator to show if the sound is muted. The LED state is never toggled. It 
will just retain its state, even though the audio is succesfully muted/unmuted.

  Tested with HP Pavilion x360 from 2018.

  Version-Release number of selected component (if applicable):

  How reproducible:
  Always.

  Steps to Reproduce:
  1. Press mute key on HP laptop

  Actual results:
  Mute state in software toggles, LED in mute key does not.

  Expected results:
  Mute state in software and LED in mute key toggle.

  Additional info:
  This happens on kernel 4.20.8

  Other similar errors:
  * https://bugs.launchpad.net/bugs/1683277
  * https://bugs.launchpad.net/bugs/1705586

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: linux-image-4.19.0-12-generic 4.19.0-12.13
  ProcVersionSignature: Ubuntu 4.19.0-12.13-generic 4.19.18
  Uname: Linux 4.19.0-12-generic x86_64
  ApportVersion: 2.20.10-0ubuntu20
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  caravena   2337 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Feb 14 15:56:54 2019
  HibernationDevice: RESUME=UUID=efcf081f-0bb0-4907-b78c-1299aa4aee57
  InstallationDate: Installed on 2018-12-02 (74 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: HP HP Pavilion x360 Convertible 14-cd0xxx
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.19.0-12-generic 
root=UUID=28bdadba-133c-4f5b-a5c9-b06993ea7ce2 ro rootflags=subvol=@ quiet 
splash vt.handoff=1
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Daemon 
not responding.
  RelatedPackageVersions:
   linux-restricted-modules-4.19.0-12-generic N/A
   linux-backports-modules-4.19.0-12-generic  N/A
   linux-firmware 1.177
  SourcePackage: linux
  UpgradeStatus: Upgraded to disco on 2018-12-02 (73 days ago)
  dmi.bios.date: 11/08/2018
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.32
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 8486
  dmi.board.vendor: HP
  dmi.board.version: 72.23
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.32:bd11/08/2018:svnHP:pnHPPavilionx360Convertible14-cd0xxx:pvrType1ProductConfigId:rvnHP:rn8486:rvr72.23:cvnHP:ct31:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Pavilion
  dmi.product.name: HP Pavilion x360 Convertible 14-cd0xxx
  dmi.product.sku: 3PX63LA#ABM
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP

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

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

[Kernel-packages] [Bug 1734147] Re: corrupted BIOS due to Intel SPI bug in kernel

2019-02-14 Thread Steve Langasek

Marek, Secure Boot is a UEFI feature. It is not possible for you to
have Secure Boot blocking a kernel boot if you do not have UEFI.

It is possible that your EFI System Partition is not mounted at
/boot/efi, if you have modified your /etc/fstab since installation. For
the system to boot at all under UEFI, you must have an EFI System
Partition. For you to have a grub that refuses to boot unsigned
kernels, you must have updated the contents on that EFI System Partition
rather recently.

The output of 'efibootmgr -v' may help you locate the partition so that
you can mount it.

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

Title:
corrupted BIOS due to Intel SPI bug in kernel

Symptoms:
* BIOS settings cannot be saved
* USB Boot impossible
* EFI entries read-only.

---

Fix: The issue was fixed in kernel version 4.13.0-21 by configuring
the kernel so it is not compiled with Intel SPI support. But previous
affected machines still suffered from a broken BIOS.

Repair: If you still can boot into Ubuntu, you can recover your BIOS
with the following steps:

After your BIOS is fixed, the kernel packages you just installed are
no longer needed, you can remove it by running 'sudo dpkg -r linux-
image-4.15.0-041500rc6-generic'.

The patch used to build the linux v4.15 kernel in step 8 can be found
at https://goo.gl/xUKJFR.

2) Copy grubx64.efi.signed over /boot/efi/EFI/ubuntu/grubx64.efi:
$ sudo cp grubx64.efi.signed /boot/efi/EFI/ubuntu/grubx64.efi

3) Reboot; you should now be able to load the new unsigned kernel that
allows fixing firmware / SPI.

4) Once you're satisfied that things work; boot to Ubuntu with a
standard, signed kernel, and re-install the right GRUB version for
your system:

$ sudo grub-install

---

Test Case: Fix has been verified by our HWE team on affected hardware.

Regression Potential: Minimal, it's unlikely anyone is actually doing
anything which requires this driver.

---

Affected Machines:

Acer Aspire E5-771G
Acer Aspire ES1-111M-C1LE (fixed following your new instruction (thank you))
Acer TravelMate B113
Acer Swift SF314-52 (Fixed by 4.14.9)
Toshiba Satellite S55T-B5233
Toshiba Satellite L50-B-1R7
Toshiba Satellite S50-B-13G
Toshiba Satellite L70-A-13M
Dell Inspiron 15-3531
Mediacom Smartbook 14 Ultra M-SB14UC (fixed with official fix)
Acer Aspire E3-111-C0UM
HP 14-r012la

---

Affected serial flash devices by manufacturer part number, JEDEC ID
(SPI_NOR_HAS_LOCK set in

[Kernel-packages] [Bug 1772950] Re: dkms key enrolled in mok, but dkms module fails to load

This bug was fixed in the package dkms - 2.2.0.3-2ubuntu11.6

---
dkms (2.2.0.3-2ubuntu11.6) xenial; urgency=medium

  * debian/patches/shim_secureboot_support.patch:
- Move to signing just after module build to ensure it correctly applies
  at kernel update times. (LP: #1772950)
- Generate a new MOK if there isn't one yet, and use that so sign
  newly-built kernel modules. (LP: #1748983)

 -- Mathieu Trudel-Lapierre   Mon, 28 Jan 2019
10:21:09 -0500

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

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

Title:
  dkms key enrolled in mok, but dkms module fails to load

Status in dkms package in Ubuntu:
  Fix Released
Status in dkms source package in Trusty:
  Fix Released
Status in dkms source package in Xenial:
  Fix Released
Status in dkms source package in Bionic:
  Fix Released

Bug description:
  [Impact]
  All Ubuntu users for whom Secure Boot is enabled.

  [Test cases]
  1) install dkms module (use virtualbox-dkms for example)
  2) Upgrade kernel (for example, install 4.15.0-22-generic on top of 
4.15.0-20-generic).
  3) Verify that the generated module for the new kernel (4.15.0-22-generic in 
this example) is built and signed by verifying that the file in 
/lib/modules/$kernel/updates/dkms/$module.ko ends in ~Module signature 
appended~:

  $ hexdump -Cv /lib/modules/4.15.0-22-generic/updates/dkms/vboxdrv.ko | tail 
-n 100
  [...]
  ~Module signature appended~

  4) Reboot
  5) modprobe -v the module.
  It should not respond "Required key not available", and should return with no 
error.
  6) Verify that dkms does not contain PKCS#7 errors.

  
  [Regression potential]
  Possible regressions involve failure to sign and/or be able to load modules 
after updates: failure to sign leading to a module being built but unsigned 
after a new kernel is installed or after a new DKMS module is installed, 
failure to load modules after reboot (usually caused by module being unsigned); 
failure to sign due to missing keys, signature key not being automatically 
slated for enrollment. All these potential regression scenarios present as 
failure to load a DKMS module after a reboot when it should be loaded 
successfully.

  ---

  At my last reboot, I was prompted to enable SecureBoot, so I did.

  When I booted, however, I noticed that the virtualbox service failed
  to start because it couldn't load its kernel module.  If I attempt the
  same thing, I see that there's an issue with keys:

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

  I do have keys enrolled; `mokutil --list-enrolled` produces
  http://paste.ubuntu.com/p/rntTQr5XJV/

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

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

[Kernel-packages] [Bug 1748983] Re: Generate per-machine MOK for dkms signing

This bug was fixed in the package dkms - 2.2.0.3-2ubuntu11.6

---
dkms (2.2.0.3-2ubuntu11.6) xenial; urgency=medium

  * debian/patches/shim_secureboot_support.patch:
- Move to signing just after module build to ensure it correctly applies
  at kernel update times. (LP: #1772950)
- Generate a new MOK if there isn't one yet, and use that so sign
  newly-built kernel modules. (LP: #1748983)

 -- Mathieu Trudel-Lapierre   Mon, 28 Jan 2019
10:21:09 -0500

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

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

Title:
  Generate per-machine MOK for dkms signing

Status in dkms package in Ubuntu:
  Fix Released
Status in shim-signed package in Ubuntu:
  Fix Released
Status in dkms source package in Trusty:
  Fix Released
Status in shim-signed source package in Trusty:
  Fix Released
Status in dkms source package in Xenial:
  Fix Released
Status in shim-signed source package in Xenial:
  Fix Released

Bug description:
  [SRU Justification]
  Move to using self-signed keys for signing DKMS modules, along with the 
wizard / guide to make this work properly, to let third-party modules be signed 
and loaded by enforcing kernels, rather than disabling Secure Boot altogether.

  [Test case]
  1) Install Ubuntu in UEFI mode.
  2) Install bbswitch-dkms (or another -dkms package if useful on your system).
  3) Follow the steps in the debconf prompts (enter a password, remember the 
password for next boot).
  4) Reboot; follow the steps in MokManagerL
  4a) Pick Enroll MOK: add the new key, enter the password when prompted to do 
so.
  4b) If a dkms package was previously installed on the system (so Secure Boot 
is currently disabled in shim), pick "Change Secure Boot state". Follow the 
prompts to enter password characters. The option will only show up if Secure 
Boot validation was found to be disabled.
  5) Pick "Reboot".
  6) Log in and verify that the dkms module is loaded, using "lsmod | grep 
".
  7) Run 'modprobe ' to validate that the module can be loaded 
explicilty.
  8) Validate that there are no errors from modprobe or errors in dmesg 
concerning signing keys.

  [Regression potential]
  If anything currently relies on Secure Boot validation being disabled in 
order to correctly run with an enforcing kernel, or grub is used in enforcing 
mode, custom / third-party kernels and modules may fail to load.

  ---

  shim-signed's update-secureboot-policy should allow creating a
  machine-owner key, and using this for signing kernel modules built via
  DKMS. Key generation and enrolling should be made as easy as possible
  for users.

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

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

[Kernel-packages] [Bug 1815952] Re: Mute key LED does not work on HP Pavilion x360

https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/sound/pci/hda/patch_conexant.c?id=v5.0-rc6#n934

SND_PCI_QUIRK(0x103c, 0x837f, "HP ProBook 470 G5",
CXT_FIXUP_MUTE_LED_GPIO),

What values are those that replace "0x837f"?
Where does that information come from?

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

Title:
  Mute key LED does not work on HP Pavilion x360

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

Bug description:
  Description of problem:
  The F6/mute key on the keyboard of HP notebooks often has a built in LED 
indicator to show if the sound is muted. The LED state is never toggled. It 
will just retain its state, even though the audio is succesfully muted/unmuted.

  Tested with HP Pavilion x360 from 2018.

  Version-Release number of selected component (if applicable):

  How reproducible:
  Always.

  Steps to Reproduce:
  1. Press mute key on HP laptop

  Actual results:
  Mute state in software toggles, LED in mute key does not.

  Expected results:
  Mute state in software and LED in mute key toggle.

  Additional info:
  This happens on kernel 4.20.8

  Other similar errors:
  * https://bugs.launchpad.net/bugs/1683277
  * https://bugs.launchpad.net/bugs/1705586

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: linux-image-4.19.0-12-generic 4.19.0-12.13
  ProcVersionSignature: Ubuntu 4.19.0-12.13-generic 4.19.18
  Uname: Linux 4.19.0-12-generic x86_64
  ApportVersion: 2.20.10-0ubuntu20
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  caravena   2337 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Feb 14 15:56:54 2019
  HibernationDevice: RESUME=UUID=efcf081f-0bb0-4907-b78c-1299aa4aee57
  InstallationDate: Installed on 2018-12-02 (74 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: HP HP Pavilion x360 Convertible 14-cd0xxx
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.19.0-12-generic 
root=UUID=28bdadba-133c-4f5b-a5c9-b06993ea7ce2 ro rootflags=subvol=@ quiet 
splash vt.handoff=1
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Daemon 
not responding.
  RelatedPackageVersions:
   linux-restricted-modules-4.19.0-12-generic N/A
   linux-backports-modules-4.19.0-12-generic  N/A
   linux-firmware 1.177
  SourcePackage: linux
  UpgradeStatus: Upgraded to disco on 2018-12-02 (73 days ago)
  dmi.bios.date: 11/08/2018
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.32
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 8486
  dmi.board.vendor: HP
  dmi.board.version: 72.23
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.32:bd11/08/2018:svnHP:pnHPPavilionx360Convertible14-cd0xxx:pvrType1ProductConfigId:rvnHP:rn8486:rvr72.23:cvnHP:ct31:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Pavilion
  dmi.product.name: HP Pavilion x360 Convertible 14-cd0xxx
  dmi.product.sku: 3PX63LA#ABM
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP

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

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

[Kernel-packages] [Bug 1594023] Re: Poweroff or reboot hangs. Laptop won't shutdown. 16.04

2019-02-14 Thread Keith

Sounds like broken record here, oh no broken shutdown here actually.
Bodhi Linux 4.2 on old hardare Aspire 5000 laptop, was wooring fine till a day 
or two ago.
Hangs at shutting down several things says all stopped down to hardware clock 
something or another.
can hit Esc a couple times and it progresses but still just stops.
Will boot fine with a Power Button Hold down and restart.

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

Title:
  Poweroff or reboot hangs. Laptop won't shutdown. 16.04

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This is about a fresh Ubuntu 16.04 install on a new laptop (asus
  x540sa). After pressing the shutdown button in the start menu; the
  shutdown procedure starts and in the final splash screen the system
  just hangs. Tried a second time by pressing Esc once the splash screen
  showed up and I saw that it reaches the line "Reached target shutdown"
  and just stops there, no matter how long I leave it there the machine
  won't turn off.

  I also tried a Kubuntu 16.04 fresh install on the same machine and it
  hanged too at the final splash screen where the pulsating logo
  stopped. Then I tried with Esc only to see the exact same line in the
  end.

  The issue seems to affect lately quite many users as shown by the
  google results of the past month / week or so.

  I have also tried shutting down from the console with shutdown -and
  all the parameters after that suggested online- and sudo poweroff but
  unfortunately they didn't do the trick. The exact same situation
  occurred.

  Unmounting the swap as suggested online doesn't work.

  Also rebooting the system is not working either due to the same issue.

  So right now the only way for me to poweroff the machine is to press
  the power button on the keyboard continuously.

  Reproducible: Always

  Steps to Reproduce:
  1.Install OS
  2.Do something, anything or nothing
  3.Try to shutdown or reboot

  Actual Results:
  The computer is not shutting down: "Reached target shutdown" and hangs there.

  Expected Results:
  Powering off the machine.

  For what it's worth, closing the lid won't suspend the system, but
  using the menu buttons for suspension will do it.

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

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

[Kernel-packages] [Bug 1734147] Re: corrupted BIOS due to Intel SPI bug in kernel

2019-02-14 Thread Marek Hák

Thanks for the help Mathieu, however, it sadly did not solve the issue.
There was no /efi direcory in my /boot. I still tried to create the
directories you told me to copy it into, but that didn't work. Is it
possible I have a non-UEFI version of ubuntu?

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

Title:
corrupted BIOS due to Intel SPI bug in kernel

Symptoms:
* BIOS settings cannot be saved
* USB Boot impossible
* EFI entries read-only.

---

Fix: The issue was fixed in kernel version 4.13.0-21 by configuring
the kernel so it is not compiled with Intel SPI support. But previous
affected machines still suffered from a broken BIOS.

Repair: If you still can boot into Ubuntu, you can recover your BIOS
with the following steps:

After your BIOS is fixed, the kernel packages you just installed are
no longer needed, you can remove it by running 'sudo dpkg -r linux-
image-4.15.0-041500rc6-generic'.

The patch used to build the linux v4.15 kernel in step 8 can be found
at https://goo.gl/xUKJFR.

2) Copy grubx64.efi.signed over /boot/efi/EFI/ubuntu/grubx64.efi:
$ sudo cp grubx64.efi.signed /boot/efi/EFI/ubuntu/grubx64.efi

3) Reboot; you should now be able to load the new unsigned kernel that
allows fixing firmware / SPI.

4) Once you're satisfied that things work; boot to Ubuntu with a
standard, signed kernel, and re-install the right GRUB version for
your system:

$ sudo grub-install

---

Test Case: Fix has been verified by our HWE team on affected hardware.

Regression Potential: Minimal, it's unlikely anyone is actually doing
anything which requires this driver.

---

Affected Machines:

---

Affected serial flash devices by manufacturer part number, JEDEC ID
(SPI_NOR_HAS_LOCK set in drivers/mtd/spi-nor/spi-nor.c)
/* ESMT */
f25l32pa, 0x8c2016
f25l32qa, 0x8c4116
f25l64qa, 0x8c4117
/* GigaDevice */
gd25q16, 0xc84015
gd25q32, 0xc84016
gd25lq32, 0xc86016
gd25q64, 0xc84017
gd25lq64c, 0xc86017
gd25q128, 0xc84018
gd25q256, 0xc84019
/* Winbond */
w25q16dw,

[Kernel-packages] [Bug 1815952] Re: Mute key LED does not work on HP Pavilion x360

This happens on kernel 5.0.0-05rc6-generic

** Tags added: kernel-bug-exists-upstream

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

Title:
  Mute key LED does not work on HP Pavilion x360

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

Bug description:
  Description of problem:
  The F6/mute key on the keyboard of HP notebooks often has a built in LED 
indicator to show if the sound is muted. The LED state is never toggled. It 
will just retain its state, even though the audio is succesfully muted/unmuted.

  Tested with HP Pavilion x360 from 2018.

  Version-Release number of selected component (if applicable):

  How reproducible:
  Always.

  Steps to Reproduce:
  1. Press mute key on HP laptop

  Actual results:
  Mute state in software toggles, LED in mute key does not.

  Expected results:
  Mute state in software and LED in mute key toggle.

  Additional info:
  This happens on kernel 4.20.8

  Other similar errors:
  * https://bugs.launchpad.net/bugs/1683277
  * https://bugs.launchpad.net/bugs/1705586

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: linux-image-4.19.0-12-generic 4.19.0-12.13
  ProcVersionSignature: Ubuntu 4.19.0-12.13-generic 4.19.18
  Uname: Linux 4.19.0-12-generic x86_64
  ApportVersion: 2.20.10-0ubuntu20
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  caravena   2337 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Feb 14 15:56:54 2019
  HibernationDevice: RESUME=UUID=efcf081f-0bb0-4907-b78c-1299aa4aee57
  InstallationDate: Installed on 2018-12-02 (74 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: HP HP Pavilion x360 Convertible 14-cd0xxx
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.19.0-12-generic 
root=UUID=28bdadba-133c-4f5b-a5c9-b06993ea7ce2 ro rootflags=subvol=@ quiet 
splash vt.handoff=1
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Daemon 
not responding.
  RelatedPackageVersions:
   linux-restricted-modules-4.19.0-12-generic N/A
   linux-backports-modules-4.19.0-12-generic  N/A
   linux-firmware 1.177
  SourcePackage: linux
  UpgradeStatus: Upgraded to disco on 2018-12-02 (73 days ago)
  dmi.bios.date: 11/08/2018
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.32
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 8486
  dmi.board.vendor: HP
  dmi.board.version: 72.23
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.32:bd11/08/2018:svnHP:pnHPPavilionx360Convertible14-cd0xxx:pvrType1ProductConfigId:rvnHP:rn8486:rvr72.23:cvnHP:ct31:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Pavilion
  dmi.product.name: HP Pavilion x360 Convertible 14-cd0xxx
  dmi.product.sku: 3PX63LA#ABM
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP

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

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

[Kernel-packages] [Bug 1795453] Re: [SRU] IO's are issued with incorrect Scatter Gather Buffer

2019-02-14 Thread Jerry Clement

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

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

Title:
  [SRU] IO's are issued with incorrect Scatter Gather Buffer

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Bionic:
  Fix Committed
Status in linux source package in Cosmic:
  Fix Committed

Bug description:
  [Impact]
  We have observed that OS is sending the IO's (SCSI Read/Write) with incorrect 
Scatter Gather Buffer address .

  i.e

   OS is sending the IO with 64 bit Scatter Gather Buffer address , such
  that if we add the length with buffer address then it causes the roll
  over .

  Here is the data we captured in our driver (Printed the SGE details
  which was sent by OS)

  sgl_ptr->Address = f000
  [14547.313240]
  sgl_ptr->Length = 1000
  [14547.313241]
  sge_count = 18
  [14547.313242]
  cmd->index = 9d9

  Note : This issue is observed only when virtualization is enabled

  Product : Broadcom (LSI) Megaraid H840 controller

  
  [Test Case]
  Steps found in comment #60
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1795453/comments/60

  
  [Regression Potential]

  The patches in Comment #59 have been accepted upstream.

  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1795453/comments/59


  [Other Info]

  Product : Broadcom (LSI) Megaraid H840 controller
  ---
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw+ 1 root audio 116,  1 Oct 12 16:35 seq
   crw-rw+ 1 root audio 116, 33 Oct 12 16:35 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 18.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  MachineType: Dell Inc. PowerEdge R7415
  Package: linux (not installed)
  PciMultimedia:

  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 mgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-8-generic 
root=UUID=43e89410-c7ff-11e8-9229-d094661013d8 ro
  ProcVersionSignature: Ubuntu 4.18.0-8.9~18.04.1-generic 4.18.7
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-8-generic N/A
   linux-backports-modules-4.18.0-8-generic  N/A
   linux-firmware1.173.1
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  Tags:  bionic uec-images
  Uname: Linux 4.18.0-8-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lxd plugdev sudo
  _MarkForUpload: True
  dmi.bios.date: 09/07/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.6.2
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 23
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.6.2:bd09/07/2018:svnDellInc.:pnPowerEdgeR7415:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct23:cvr:
  dmi.product.family: PowerEdge
  dmi.product.name: PowerEdge R7415
  dmi.product.sku: SKU=NotProvided;ModelName=PowerEdge R7415
  dmi.sys.vendor: Dell Inc.
  ---
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw+ 1 root audio 116,  1 Oct 12 16:35 seq
   crw-rw+ 1 root audio 116, 33 Oct 12 16:35 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 18.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  MachineType: Dell Inc. PowerEdge R7415
  Package: linux (not installed)
  PciMultimedia:

  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 mgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-8-generic 
root=UUID=43e89410-c7ff-11e8-9229-d094661013d8 ro
  ProcVersionSignature: Ubuntu 4.18.0-8.9~18.04.1-generic 4.18.7
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-8-generic N/A
   linux-backports-modules-4.18.0-8-generic  N/A
   linux-firmware1.173.1
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  Tags:  bionic uec-images
  Uname: Linux 4.18.0-8-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lxd plugdev sudo
  _MarkForUpload: True
  dmi.bios.date: 09/07/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version:

[Kernel-packages] [Bug 1815952] Re: Mute key LED does not work on HP Pavilion x360

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

** Also affects: linux via
   https://bugzilla.kernel.org/show_bug.cgi?id=202581
   Importance: Unknown
   Status: Unknown

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

Title:
  Mute key LED does not work on HP Pavilion x360

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

Bug description:
  Description of problem:
  The F6/mute key on the keyboard of HP notebooks often has a built in LED 
indicator to show if the sound is muted. The LED state is never toggled. It 
will just retain its state, even though the audio is succesfully muted/unmuted.

  Tested with HP Pavilion x360 from 2018.

  Version-Release number of selected component (if applicable):

  How reproducible:
  Always.

  Steps to Reproduce:
  1. Press mute key on HP laptop

  Actual results:
  Mute state in software toggles, LED in mute key does not.

  Expected results:
  Mute state in software and LED in mute key toggle.

  Additional info:
  This happens on kernel 4.20.8

  Other similar errors:
  * https://bugs.launchpad.net/bugs/1683277
  * https://bugs.launchpad.net/bugs/1705586

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: linux-image-4.19.0-12-generic 4.19.0-12.13
  ProcVersionSignature: Ubuntu 4.19.0-12.13-generic 4.19.18
  Uname: Linux 4.19.0-12-generic x86_64
  ApportVersion: 2.20.10-0ubuntu20
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  caravena   2337 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Feb 14 15:56:54 2019
  HibernationDevice: RESUME=UUID=efcf081f-0bb0-4907-b78c-1299aa4aee57
  InstallationDate: Installed on 2018-12-02 (74 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: HP HP Pavilion x360 Convertible 14-cd0xxx
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.19.0-12-generic 
root=UUID=28bdadba-133c-4f5b-a5c9-b06993ea7ce2 ro rootflags=subvol=@ quiet 
splash vt.handoff=1
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Daemon 
not responding.
  RelatedPackageVersions:
   linux-restricted-modules-4.19.0-12-generic N/A
   linux-backports-modules-4.19.0-12-generic  N/A
   linux-firmware 1.177
  SourcePackage: linux
  UpgradeStatus: Upgraded to disco on 2018-12-02 (73 days ago)
  dmi.bios.date: 11/08/2018
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.32
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 8486
  dmi.board.vendor: HP
  dmi.board.version: 72.23
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.32:bd11/08/2018:svnHP:pnHPPavilionx360Convertible14-cd0xxx:pvrType1ProductConfigId:rvnHP:rn8486:rvr72.23:cvnHP:ct31:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Pavilion
  dmi.product.name: HP Pavilion x360 Convertible 14-cd0xxx
  dmi.product.sku: 3PX63LA#ABM
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP

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

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

[Kernel-packages] [Bug 1815952] [NEW] Mute key LED does not work on HP Pavilion x360

Public bug reported:

Description of problem:
The F6/mute key on the keyboard of HP notebooks often has a built in LED 
indicator to show if the sound is muted. The LED state is never toggled. It 
will just retain its state, even though the audio is succesfully muted/unmuted.

Tested with HP Pavilion x360 from 2018.

Version-Release number of selected component (if applicable):

How reproducible:
Always.

Steps to Reproduce:
1. Press mute key on HP laptop

Actual results:
Mute state in software toggles, LED in mute key does not.

Expected results:
Mute state in software and LED in mute key toggle.

Additional info:
This happens on kernel 4.20.8

Other similar errors:
* https://bugs.launchpad.net/bugs/1683277
* https://bugs.launchpad.net/bugs/1705586

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: linux-image-4.19.0-12-generic 4.19.0-12.13
ProcVersionSignature: Ubuntu 4.19.0-12.13-generic 4.19.18
Uname: Linux 4.19.0-12-generic x86_64
ApportVersion: 2.20.10-0ubuntu20
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  caravena   2337 F pulseaudio
CurrentDesktop: ubuntu:GNOME
Date: Thu Feb 14 15:56:54 2019
HibernationDevice: RESUME=UUID=efcf081f-0bb0-4907-b78c-1299aa4aee57
InstallationDate: Installed on 2018-12-02 (74 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
MachineType: HP HP Pavilion x360 Convertible 14-cd0xxx
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.19.0-12-generic 
root=UUID=28bdadba-133c-4f5b-a5c9-b06993ea7ce2 ro rootflags=subvol=@ quiet 
splash vt.handoff=1
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Daemon not 
responding.
RelatedPackageVersions:
 linux-restricted-modules-4.19.0-12-generic N/A
 linux-backports-modules-4.19.0-12-generic  N/A
 linux-firmware 1.177
SourcePackage: linux
UpgradeStatus: Upgraded to disco on 2018-12-02 (73 days ago)
dmi.bios.date: 11/08/2018
dmi.bios.vendor: Insyde
dmi.bios.version: F.32
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: 8486
dmi.board.vendor: HP
dmi.board.version: 72.23
dmi.chassis.asset.tag: Chassis Asset Tag
dmi.chassis.type: 31
dmi.chassis.vendor: HP
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnInsyde:bvrF.32:bd11/08/2018:svnHP:pnHPPavilionx360Convertible14-cd0xxx:pvrType1ProductConfigId:rvnHP:rn8486:rvr72.23:cvnHP:ct31:cvrChassisVersion:
dmi.product.family: 103C_5335KV HP Pavilion
dmi.product.name: HP Pavilion x360 Convertible 14-cd0xxx
dmi.product.sku: 3PX63LA#ABM
dmi.product.version: Type1ProductConfigId
dmi.sys.vendor: HP

** Affects: linux
 Importance: Unknown
 Status: Unknown

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


** Tags: amd64 apport-bug disco wayland-session

** Description changed:

  Description of problem:
  The F6/mute key on the keyboard of HP notebooks often has a built in LED 
indicator to show if the sound is muted. The LED state is never toggled. It 
will just retain its state, even though the audio is succesfully muted/unmuted.
  
  Tested with HP Pavilion x360 from 2018.
  
  Version-Release number of selected component (if applicable):
  
  How reproducible:
  Always.
  
  Steps to Reproduce:
  1. Press mute key on HP laptop
  
  Actual results:
  Mute state in software toggles, LED in mute key does not.
  
  Expected results:
  Mute state in software and LED in mute key toggle.
  
  Additional info:
- 1.- This happens on kernel 4.20.8
- 2.- Attached image of the keys.
+ This happens on kernel 4.20.8
  
  Other similar errors:
  * https://bugs.launchpad.net/bugs/1683277
  * https://bugs.launchpad.net/bugs/1705586
  
  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: linux-image-4.19.0-12-generic 4.19.0-12.13
  ProcVersionSignature: Ubuntu 4.19.0-12.13-generic 4.19.18
  Uname: Linux 4.19.0-12-generic x86_64
  ApportVersion: 2.20.10-0ubuntu20
  Architecture: amd64
  AudioDevicesInUse:
-  USERPID ACCESS COMMAND
-  /dev/snd/controlC0:  caravena   2337 F pulseaudio
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC0:  caravena   2337 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Feb 14 15:56:54 2019
  HibernationDevice: RESUME=UUID=efcf081f-0bb0-4907-b78c-1299aa4aee57
  InstallationDate: Installed on 2018-12-02 (74 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: HP HP Pavilion x360 Convertible 14-cd0xxx
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.19.0-12-generic 
root=UUID=28bdadba-133c-4f5b-a5c9-b06993ea7ce2 ro rootflags=subvol=@ quiet 
splash vt.handoff=1
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Daemon 
not responding.
  RelatedPackageVersions:
-  linux-restricted-modules-4.19.0-12-generic N/A
-  linux-backports-modules-4.19.0-12-generic  N/A
-  linux-firmware 1.177
+

[Kernel-packages] [Bug 1734147] Re: corrupted BIOS due to Intel SPI bug in kernel

2019-02-14 Thread Mathieu Trudel-Lapierre

If you can still boot to Ubuntu with an older kernel (one that is
signed), here's what you can do:

1) Download http://archive.ubuntu.com/ubuntu/dists/xenial-
updates/main/uefi/grub2-amd64/2.02~beta2-36ubuntu3.20/grubx64.efi.signed.

2) Copy grubx64.efi.signed over /boot/efi/EFI/ubuntu/grubx64.efi:
sudo cp grubx64.efi.signed /boot/efi/EFI/ubuntu/grubx64.efi

3) Reboot; you should now be able to load the new unsigned kernel that
allows fixing firmware / SPI.

4) Once you're satisfied that things work; boot to Ubuntu with a
standard, signed kernel, and re-install the right GRUB version for your
system:

sudo grub-install

** Description changed:

An update to linux kernel on Ubuntu 17.10 that enabled the Intel SPI
drivers results in a serial flash that is read only in Intel Broadwell
and Haswell machines with serial flashes with SPI_NOR_HAS_LOCK set.

Symptoms:
* BIOS settings cannot be saved
* USB Boot impossible
* EFI entries read-only.

---

Fix: The issue was fixed in kernel version 4.13.0-21 by configuring the
kernel so it is not compiled with Intel SPI support. But previous
affected machines still suffered from a broken BIOS.

Repair: If you still can boot into Ubuntu, you can recover your BIOS
with the following steps:

After your BIOS is fixed, the kernel packages you just installed are no
longer needed, you can remove it by running 'sudo dpkg -r linux-
image-4.15.0-041500rc6-generic'.

The patch used to build the linux v4.15 kernel in step 8 can be found at
https://goo.gl/xUKJFR.
+
+
+ If you have applied updates, and find that you can not boot the above fixed
kernel because of Secure Boot and that the kernel is unsigned, but can still
boot another kernel for your system; here's what you can do:
+
+ 1) Download
http://archive.ubuntu.com/ubuntu/dists/xenial-updates/main/uefi/grub2-amd64/2.02~beta2-36ubuntu3.20/grubx64.efi.signed:
+ $ wget
http://archive.ubuntu.com/ubuntu/dists/xenial-updates/main/uefi/grub2-amd64/2.02~beta2-36ubuntu3.20/grubx64.efi.signed
+
+
+ 2) Copy grubx64.efi.signed over /boot/efi/EFI/ubuntu/grubx64.efi:
+ $ sudo cp grubx64.efi.signed /boot/efi/EFI/ubuntu/grubx64.efi
+
+ 3) Reboot; you should now be able to load the new unsigned kernel that
+ allows fixing firmware / SPI.
+
+ 4) Once you're satisfied that things work; boot to Ubuntu with a
+ standard, signed kernel, and re-install the right GRUB version for your
+ system:
+
+ $ sudo grub-install

---

Test Case: Fix has been verified by our HWE team on affected hardware.

Regression Potential: Minimal, it's unlikely anyone is actually doing
anything which requires this driver.

---

Affected Machines:

---

[Kernel-packages] [Bug 1815951] [NEW] Request backport of PBF features for next gen Intel proc.

Public bug reported:

SRU Justification:

Impact:

This feature is going to be a popular request for users of Intel's next gen 
CPUs. It
is enabled by two small commits that went into the upstream 4.20 kernel. 
Please
backport the two commits indicated in Fix: and investigate the effort to 
backport to
the 4.15 kernel.

Fix:

29523f095397637edca60c627bc3e5c25a02c40f
86d333a8cc7f66c2314ab1e147834a1cd95ec2de

Test:

Testing will need to be performed on the next gen CPU and on current gen 
CPUs to
verify there are no regressions.

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

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

Title:
  Request backport of PBF features for next gen Intel proc.

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  SRU Justification:

  Impact:

  This feature is going to be a popular request for users of Intel's next 
gen CPUs. It
  is enabled by two small commits that went into the upstream 4.20 kernel. 
Please
  backport the two commits indicated in Fix: and investigate the effort to 
backport to
  the 4.15 kernel.

  Fix:

  29523f095397637edca60c627bc3e5c25a02c40f
  86d333a8cc7f66c2314ab1e147834a1cd95ec2de

  Test:

  Testing will need to be performed on the next gen CPU and on current gen 
CPUs to
  verify there are no regressions.

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

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

[Kernel-packages] [Bug 1800566] Re: Make the reset_devices parameter default for kdump kernels

2019-02-14 Thread Heitor R. Alves de Siqueira

** Description changed:

- Kernel has the "reset_devices" parameter that drivers can opt-in, and
- perform special activity in case this parameter is parsed from command-
- line. For example, in kdump kernels it hints the drivers that they
- (maybe) are booting from a non-healthy condition and needs to issue some
- reset to the adapter. Users currently (kernel v4.19) are: hpsa, ipr,
- megaraid_sas, mpt3sas, smartpqi, xenbus.
+ [Impact]
+ Crash kernels do not advise some subsystems to perform a reset by default.
+ 
+ [Description]
+ Kernel has the "reset_devices" parameter that drivers can opt-in, and perform 
special activity in case this parameter is parsed from command-line. For 
example, in kdump kernels it hints the drivers that they (maybe) are booting 
from a non-healthy condition and needs to issue some reset to the adapter. 
Users currently (kernel v4.19) are: hpsa, ipr, megaraid_sas, mpt3sas, smartpqi, 
xenbus.
  
  This should be enabled by default in the kdump config file to be added
  in the kdump kernel command-line for all versions.
+ 
+ [Test Case]
+ 1) Deploy a Disco VM e.g. with uvt-kvm
+ 2) Install the kdump-tools package
+ 3) Run `kdump-config test`and check for the 'reset_devices' parameter:
+ 
+ $ kdump-config test
+ [...]
+ kexec command to be used:
+   /sbin/kexec -p --command-line="BOOT_IMAGE=/boot/vmlinuz-4.15.0-45-generic 
root=LABEL=cloudimg-rootfs ro console=tty1 console=ttyS0 nr_cpus=1 
systemd.unit=kdump-tools.service irqpoll nousb ata_piix.prefer_ms_hyperv=0" 
/var/lib/kdump/vmlinuz
+ 
+ [Regression Potential]
+ The regression potential is very low, since it doesn't need any changes in 
makedumpfile code and we're only adding a parameter on the crashkernel cmdline.
+ The fix will be tested with autopkgtests and normal kdump use-case scenarios.

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

Title:
  Make the reset_devices parameter default for kdump kernels

Status in makedumpfile package in Ubuntu:
  Confirmed
Status in makedumpfile source package in Trusty:
  Confirmed
Status in makedumpfile source package in Xenial:
  Confirmed
Status in makedumpfile source package in Bionic:
  Confirmed
Status in makedumpfile source package in Cosmic:
  Confirmed
Status in makedumpfile source package in Disco:
  Confirmed

Bug description:
  [Impact]
  Crash kernels do not advise some subsystems to perform a reset by default.

  [Description]
  Kernel has the "reset_devices" parameter that drivers can opt-in, and perform 
special activity in case this parameter is parsed from command-line. For 
example, in kdump kernels it hints the drivers that they (maybe) are booting 
from a non-healthy condition and needs to issue some reset to the adapter. 
Users currently (kernel v4.19) are: hpsa, ipr, megaraid_sas, mpt3sas, smartpqi, 
xenbus.

  This should be enabled by default in the kdump config file to be added
  in the kdump kernel command-line for all versions.

  [Test Case]
  1) Deploy a Disco VM e.g. with uvt-kvm
  2) Install the kdump-tools package
  3) Run `kdump-config test`and check for the 'reset_devices' parameter:

  $ kdump-config test
  [...]
  kexec command to be used:
/sbin/kexec -p --command-line="BOOT_IMAGE=/boot/vmlinuz-4.15.0-45-generic 
root=LABEL=cloudimg-rootfs ro console=tty1 console=ttyS0 nr_cpus=1 
systemd.unit=kdump-tools.service irqpoll nousb ata_piix.prefer_ms_hyperv=0" 
/var/lib/kdump/vmlinuz

  [Regression Potential]
  The regression potential is very low, since it doesn't need any changes in 
makedumpfile code and we're only adding a parameter on the crashkernel cmdline.
  The fix will be tested with autopkgtests and normal kdump use-case scenarios.

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

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

[Kernel-packages] [Bug 1814647] Re: linux: 4.4.0-143.169 -proposed tracker

** Changed in: kernel-sru-workflow/snap-release-to-candidate
   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
  
  backports: bug 1814648 (linux-aws), bug 1814649 (linux-lts-xenial)
  derivatives: bug 1814651 (linux-aws), bug 1814652 (linux-euclid), bug 1814654 
(linux-kvm), bug 1814655 (linux-raspi2), bug 1814657 (linux-snapdragon)
  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
  phase: Testing
  phase-changed: Thursday, 14. February 2019 16:33 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Stalled -- testing FAILED
certification-testing: Ongoing -- testing in progress
regression-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
-   snap-certification-testing: Ongoing -- testing in progress
+   snap-release-to-candidate: Pending -- snap not in candidate channel
verification-testing: Ongoing -- testing 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/1814647

Title:
  linux: 4.4.0-143.169 -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 snap-certification-testing series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-beta series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-candidate series:
  Confirmed
Status in Kernel SRU Workflow snap-release-to-edge series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-stable series:
  New
Status in Kernel SRU Workflow upload-to-ppa-dnu series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Confirmed

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

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

  backports: bug 1814648 (linux-aws), bug 1814649 (linux-lts-xenial)
  derivatives: bug 1814651 (linux-aws), bug 1814652 (linux-euclid), bug 1814654 
(linux-kvm), bug 1814655 (linux-raspi2), bug 1814657 (linux-snapdragon)
  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
  phase: Testing
  phase-changed: Thursday, 14. February 2019 16:33 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Stalled -- testing FAILED
certification-testing: Ongoing -- testing in progress
regression-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
snap-release-to-candidate: Pending -- snap not in candidate channel
verification-testing: Ongoing -- testing in progress

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

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

[Kernel-packages] [Bug 1814651] Re: linux-aws: 4.4.0-1076.86 -proposed tracker

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1814647
  phase: Promote to Proposed
  phase-changed: Thursday, 14. February 2019 12:34 UTC
  reason:
-   promote-to-proposed: Pending -- ready for review
+   promote-to-proposed: Ongoing -- review in progress

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

Title:
  linux-aws: 4.4.0-1076.86 -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:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  In Progress
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow snap-release-to-beta series:
  New
Status in Kernel SRU Workflow snap-release-to-candidate series:
  New
Status in Kernel SRU Workflow snap-release-to-edge series:
  New
Status in Kernel SRU Workflow snap-release-to-stable series:
  Invalid
Status in Kernel SRU Workflow upload-to-ppa-dnu series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-aws package in Ubuntu:
  Invalid
Status in linux-aws source package in Xenial:
  Confirmed

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1814647
  phase: Promote to Proposed
  phase-changed: Thursday, 14. February 2019 12:34 UTC
  reason:
promote-to-proposed: Ongoing -- review in progress

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

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

[Kernel-packages] [Bug 1779640] Re: [Hyper-V] KVP daemon crashes at startup

I wasn't able to reproduce it in hyper-v or in azure using the 4.15.0-45
generic kernel.

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

Title:
  [Hyper-V] KVP daemon crashes at startup

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Bionic:
  Confirmed
Status in linux source package in Disco:
  Confirmed

Bug description:
  While testing Bionic daily build with kernel 4.15.0-20-generic we saw
  the following issue with the KVP daemon:

  KVP daemon crashes after approximatively 2 minutes of uptime and it enters in 
a failed state. The daemon can be manually started and it enters back in active 
(running) state.
  The error messages from /var/log/syslog after the daemon enters the failed 
state are the following:

  Apr 25 04:28:46 bionicDaily KVP: read failed; error:9 Bad file descriptor
  Apr 25 04:28:46 bionicDaily systemd[1]: hv-kvp-daemon.service: Main process 
exited, code=exited, status=1/FAILURE
  Apr 25 04:28:46 bionicDaily systemd[1]: hv-kvp-daemon.service: Failed with 
result 'exit-code'.
  Apr 25 04:28:59 bionicDaily systemd[1]: Started Hyper-V KVP Protocol Daemon.

  Note: There was a simmilar issue discussed on this thread
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1664663, but the
  fixing commit seems to be inclued in this Bionic build.

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

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

[Kernel-packages] [Bug 1815579] Re: Broken dependencies with nvidia-driver-390 and xserver-xorg-hwe-18.04 in bionic

2019-02-14 Thread Alberto Milone

I can't reproduce the problem any more with 340 either:

~$ apt-cache policy nvidia-340
nvidia-340:
  Installed: 340.107-0ubuntu0.18.04.2
  Candidate: 340.107-0ubuntu0.18.04.2
  Version table:
 *** 340.107-0ubuntu0.18.04.2 400
400 http://archive.ubuntu.com/ubuntu bionic-proposed/restricted amd64 
Packages
100 /var/lib/dpkg/status
 340.107-0ubuntu0.18.04.1 500
500 http://archive.ubuntu.com/ubuntu bionic-updates/restricted amd64 
Packages
 340.106-0ubuntu3 500
500 http://archive.ubuntu.com/ubuntu bionic/restricted amd64 Packages


:~$ apt-cache policy xserver-xorg-hwe-18.04
xserver-xorg-hwe-18.04:
  Installed: 1:7.7+19ubuntu8~18.04.2
  Candidate: 1:7.7+19ubuntu8~18.04.2
  Version table:
 *** 1:7.7+19ubuntu8~18.04.2 500
500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages
100 /var/lib/dpkg/status

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

Title:
  Broken dependencies with nvidia-driver-390 and xserver-xorg-hwe-18.04
  in bionic

Status in nvidia-graphics-drivers-340 package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-340 source package in Bionic:
  Fix Committed
Status in nvidia-graphics-drivers-390 source package in Bionic:
  Fix Committed

Bug description:
  I am trying to test new HWE stack from 18.10 in my destkop Ubuntu
  18.04.1 (expected release 18.04.2 this week) and I have broken
  dependencies when installing `xserver-xorg-hwe-18.04` package with
  NVidia drivers:

  me@me-H110M-DS2:~$ sudo apt install xserver-xorg-hwe-18.04 
xserver-xorg-video-nvidia-390 
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  xserver-xorg-video-nvidia-390 is already the newest version 
(390.77-0ubuntu0.18.04.1).
  xserver-xorg-video-nvidia-390 set to manually installed.
  Some packages could not be installed. This may mean that you have
  requested an impossible situation or if you are using the unstable
  distribution that some required packages have not yet been created
  or been moved out of Incoming.
  The following information may help to resolve the situation:

  The following packages have unmet dependencies:
   xserver-xorg-hwe-18.04 : Depends: xserver-xorg-core-hwe-18.04 (>= 
2:1.17.2-2) but it is not going to be installed
Conflicts: xserver-xorg-core (>= 0~)
Recommends: xserver-xorg-video-all-hwe-18.04 but it 
is not going to be installed
  E: Unable to correct problems, you have held broken packages.

  
  Otherwise, if I try to install it without `xserver-xorg-video-nvidia-390` 
this happens:

  me@me-H110M-DS2:~$ sudo apt install xserver-xorg-hwe-18.04 
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  The following packages were automatically installed and are no longer 
required:
dkms libbsd0:i386 libdrm-amdgpu1:i386 libdrm-intel1:i386 
libdrm-nouveau2:i386 libdrm-radeon1:i386 libdrm2:i386 libedit2:i386 
libelf1:i386 libexpat1:i386 libffi6:i386 libgl1:i386 libgl1-mesa-dri:i386
libglapi-mesa:i386 libglvnd0:i386 libglx-mesa0:i386 libglx0:i386 
libllvm7:i386 libnvidia-cfg1-390 libnvidia-common-390 libnvidia-compute-390 
libnvidia-compute-390:i386 libnvidia-decode-390
libnvidia-decode-390:i386 libnvidia-encode-390 libnvidia-encode-390:i386 
libnvidia-fbc1-390 libnvidia-fbc1-390:i386 libnvidia-gl-390 
libnvidia-gl-390:i386 libnvidia-ifr1-390 libnvidia-ifr1-390:i386
libpciaccess0:i386 libsensors4:i386 libstdc++6:i386 libvdpau1 
libwayland-client0:i386 libwayland-server0:i386 libx11-6:i386 libx11-xcb1:i386 
libxau6:i386 libxcb-dri2-0:i386 libxcb-dri3-0:i386
libxcb-glx0:i386 libxcb-present0:i386 libxcb-sync1:i386 libxcb1:i386 
libxdamage1:i386 libxdmcp6:i386 libxext6:i386 libxfixes3:i386 libxnvctrl0 
libxshmfence1:i386 libxxf86vm1:i386 mesa-vdpau-drivers
nvidia-compute-utils-390 nvidia-dkms-390 nvidia-kernel-common-390 
nvidia-kernel-source-390 nvidia-prime nvidia-settings nvidia-utils-390 
pkg-config screen-resolution-extra vdpau-driver-all
  Use 'sudo apt autoremove' to remove them.
  The following additional packages will be installed:
xserver-xorg-core-hwe-18.04 xserver-xorg-input-all-hwe-18.04 
xserver-xorg-input-libinput-hwe-18.04 xserver-xorg-video-all-hwe-18.04 
xserver-xorg-video-amdgpu-hwe-18.04 xserver-xorg-video-ati-hwe-18.04
xserver-xorg-video-fbdev-hwe-18.04 xserver-xorg-video-intel-hwe-18.04 
xserver-xorg-video-nouveau-hwe-18.04 xserver-xorg-video-qxl-hwe-18.04 
xserver-xorg-video-radeon-hwe-18.04
xserver-xorg-video-vesa-hwe-18.04 xserver-xorg-video-vmware-hwe-18.04
  Suggested packages:
xfonts-100dpi | xfonts-75dpi firmware-amd-graphics xserver-xorg-video-r128 
xserver-xorg-video-mach64

[Kernel-packages] [Bug 1814655] Re: linux-raspi2: 4.4.0-1104.112 -proposed tracker

** Changed in: kernel-sru-workflow/snap-release-to-candidate
   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 --
  boot-testing-requested: true
  kernel-stable-master-bug: 1814647
  phase: Testing
  phase-changed: Thursday, 14. February 2019 17:11 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
certification-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
-   snap-certification-testing: Ongoing -- testing in progress
+   snap-release-to-candidate: Pending -- snap not in candidate channel
verification-testing: Ongoing -- testing in progress

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

Title:
  linux-raspi2: 4.4.0-1104.112 -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 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:
  Invalid
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow snap-certification-testing series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-beta series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-candidate series:
  Confirmed
Status in Kernel SRU Workflow snap-release-to-edge series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-stable series:
  New
Status in Kernel SRU Workflow upload-to-ppa-dnu series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-raspi2 package in Ubuntu:
  Invalid
Status in linux-raspi2 source package in Xenial:
  Confirmed

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1814647
  phase: Testing
  phase-changed: Thursday, 14. February 2019 17:11 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
certification-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
snap-release-to-candidate: Pending -- snap not in candidate channel
verification-testing: Ongoing -- testing in progress

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

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

[Kernel-packages] [Bug 1814647] Re: linux: 4.4.0-143.169 -proposed tracker

2019-02-14 Thread Canonical Certification Team

Snap beta testing complete, no regressions found. Ready for promotion.
Results here: https://trello.com/c/plDdBsnS/749-pc-kernel-440-143169-188

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

Title:
  linux: 4.4.0-143.169 -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 snap-certification-testing series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-beta series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-candidate series:
  New
Status in Kernel SRU Workflow snap-release-to-edge series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-stable series:
  New
Status in Kernel SRU Workflow upload-to-ppa-dnu series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Confirmed

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

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

  backports: bug 1814648 (linux-aws), bug 1814649 (linux-lts-xenial)
  derivatives: bug 1814651 (linux-aws), bug 1814652 (linux-euclid), bug 1814654 
(linux-kvm), bug 1814655 (linux-raspi2), bug 1814657 (linux-snapdragon)
  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
  phase: Testing
  phase-changed: Thursday, 14. February 2019 16:33 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Stalled -- testing FAILED
certification-testing: Ongoing -- testing in progress
regression-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
snap-certification-testing: Ongoing -- testing in progress
verification-testing: Ongoing -- testing in progress

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

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

[Kernel-packages] [Bug 1814655] Re: linux-raspi2: 4.4.0-1104.112 -proposed tracker

2019-02-14 Thread Canonical Certification Team

Snap beta testing complete, no regressions found. Ready for promotion.
Results here:
https://trello.com/c/rY5iUjvX/750-pi2-kernel-440-1104112-83

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

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

Title:
  linux-raspi2: 4.4.0-1104.112 -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 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:
  Invalid
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow snap-certification-testing series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-beta series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-candidate series:
  New
Status in Kernel SRU Workflow snap-release-to-edge series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-stable series:
  New
Status in Kernel SRU Workflow upload-to-ppa-dnu series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-raspi2 package in Ubuntu:
  Invalid
Status in linux-raspi2 source package in Xenial:
  Confirmed

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1814647
  phase: Testing
  phase-changed: Thursday, 14. February 2019 17:11 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
certification-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
snap-certification-testing: Ongoing -- testing in progress
verification-testing: Ongoing -- testing in progress

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

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

[Kernel-packages] [Bug 1808886] Re: Microcode SW error detected. Restarting 0x0.

2019-02-14 Thread jasd666

Still actual for me.
Please, can someone answer on the bug?

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

Title:
  Microcode SW error detected. Restarting 0x0.

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  intel-microcode:
Installed: 3.20180807a.0ubuntu0.18.04.1
Candidate: 3.20180807a.0ubuntu0.18.04.1
Version table:
   *** 3.20180807a.0ubuntu0.18.04.1 500
  500 http://ru.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   3.20180312.0~ubuntu18.04.1 500
  500 http://ru.archive.ubuntu.com/ubuntu bionic/main amd64 Packages

  
  Version:
  Ubuntu 4.15.0-42.45-generic 4.15.18

  Error:

  [ 3136.084499] rtsx_pci :06:00.0: VPD access failed.  This is likely a 
firmware bug on this device.  Contact the card vendor for a firmware update
  [ 3136.085614] r8169 :06:00.1: invalid short VPD tag 00 at offset 1
  [ 3136.085624] dpc :00:1d.0:pcie010: DPC containment event, status:0x1f00 
source:0x
  [ 3136.085662] pcieport :00:1d.0: AER: Multiple Corrected error received: 
id=00e8
  [ 3136.085683] pcieport :00:1d.0: PCIe Bus Error: severity=Corrected, 
type=Physical Layer, id=00e8(Transmitter ID)
  [ 3136.085694] pcieport :00:1d.0:   device [8086:a335] error 
status/mask=1101/2000
  [ 3136.085701] pcieport :00:1d.0:[ 0] Receiver Error (First)
  [ 3136.085722] pcieport :00:1d.0:[ 8] RELAY_NUM Rollover
  [ 3136.085741] pcieport :00:1d.0:[12] Replay Timer Timeout  
  [ 3166.625429] iwlwifi :00:14.3: Microcode SW error detected. Restarting 
0x0.
  [ 3166.625797] iwlwifi :00:14.3: Start IWL Error Log Dump:
  [ 3166.625805] iwlwifi :00:14.3: Status: 0x0100, count: 6
  [ 3166.625810] iwlwifi :00:14.3: Loaded firmware version: 34.0.0
  [ 3166.625817] iwlwifi :00:14.3: 0x1007 | ADVANCED_SYSASSERT  
  [ 3166.625823] iwlwifi :00:14.3: 0x0080A614 | trm_hw_status0
  [ 3166.625828] iwlwifi :00:14.3: 0x | trm_hw_status1
  [ 3166.625834] iwlwifi :00:14.3: 0x00456D06 | branchlink2
  [ 3166.625839] iwlwifi :00:14.3: 0x0046064A | interruptlink1
  [ 3166.625844] iwlwifi :00:14.3: 0x | interruptlink2
  [ 3166.625850] iwlwifi :00:14.3: 0x00030400 | data1
  [ 3166.625855] iwlwifi :00:14.3: 0x040B | data2
  [ 3166.625860] iwlwifi :00:14.3: 0x | data3
  [ 3166.625866] iwlwifi :00:14.3: 0xAD418817 | beacon time
  [ 3166.625871] iwlwifi :00:14.3: 0x6A2317EF | tsf low
  [ 3166.625876] iwlwifi :00:14.3: 0x0184 | tsf hi
  [ 3166.625881] iwlwifi :00:14.3: 0x | time gp1
  [ 3166.625887] iwlwifi :00:14.3: 0x0ADF380D | time gp2
  [ 3166.625892] iwlwifi :00:14.3: 0x0001 | uCode revision type
  [ 3166.625897] iwlwifi :00:14.3: 0x0022 | uCode version major
  [ 3166.625903] iwlwifi :00:14.3: 0x | uCode version minor
  [ 3166.625908] iwlwifi :00:14.3: 0x0312 | hw version
  [ 3166.625913] iwlwifi :00:14.3: 0x00C89008 | board version
  [ 3166.625918] iwlwifi :00:14.3: 0x0A9E001C | hcmd
  [ 3166.625924] iwlwifi :00:14.3: 0xA4022002 | isr0
  [ 3166.625929] iwlwifi :00:14.3: 0x0100 | isr1
  [ 3166.625934] iwlwifi :00:14.3: 0x08001802 | isr2
  [ 3166.625939] iwlwifi :00:14.3: 0x0041B8C5 | isr3
  [ 3166.625944] iwlwifi :00:14.3: 0x | isr4
  [ 3166.625950] iwlwifi :00:14.3: 0x00EC019C | last cmd Id
  [ 3166.625955] iwlwifi :00:14.3: 0x | wait_event
  [ 3166.625960] iwlwifi :00:14.3: 0x0080 | l2p_control
  [ 3166.625965] iwlwifi :00:14.3: 0x00012034 | l2p_duration
  [ 3166.625971] iwlwifi :00:14.3: 0x003F | l2p_mhvalid
  [ 3166.625976] iwlwifi :00:14.3: 0x00CE | l2p_addr_match
  [ 3166.625981] iwlwifi :00:14.3: 0x000F | lmpm_pmg_sel
  [ 3166.625987] iwlwifi :00:14.3: 0x12111721 | timestamp
  [ 3166.625992] iwlwifi :00:14.3: 0x9090 | flow_handler
  [ 3166.626141] iwlwifi :00:14.3: Start IWL Error Log Dump:
  [ 3166.626147] iwlwifi :00:14.3: Status: 0x0100, count: 7
  [ 3166.626152] iwlwifi :00:14.3: 0x0070 | ADVANCED_SYSASSERT
  [ 3166.626158] iwlwifi :00:14.3: 0x | umac branchlink1
  [ 3166.626163] iwlwifi :00:14.3: 0xC0087D08 | umac branchlink2
  [ 3166.626168] iwlwifi :00:14.3: 0xC0083A08 | umac interruptlink1
  [ 3166.626173] iwlwifi :00:14.3: 0xC0083A08 | umac interruptlink2
  [ 3166.626178] iwlwifi :00:14.3: 0x0800 | umac data1
  [ 3166.626184] iwlwifi :00:14.3: 0xC0083A08 | umac data2
  [ 3166.626189] iwlwifi :00:14.3: 0xDEADBEEF | umac data3
  [ 3166.626194] iwlwifi :00:14.3: 0x0022 | umac major
  [ 3166.626199] iwlwifi :00:14.3: 0x | umac minor

[Kernel-packages] [Bug 1814651] Re: linux-aws: 4.4.0-1076.86 -proposed tracker

2019-02-14 Thread Łukasz Zemczak

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

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

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

Title:
  linux-aws: 4.4.0-1076.86 -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:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  In Progress
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow snap-release-to-beta series:
  New
Status in Kernel SRU Workflow snap-release-to-candidate series:
  New
Status in Kernel SRU Workflow snap-release-to-edge series:
  New
Status in Kernel SRU Workflow snap-release-to-stable series:
  Invalid
Status in Kernel SRU Workflow upload-to-ppa-dnu series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-aws package in Ubuntu:
  Invalid
Status in linux-aws source package in Xenial:
  Confirmed

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1814647
  phase: Promote to Proposed
  phase-changed: Thursday, 14. February 2019 12:34 UTC
  reason:
promote-to-proposed: Pending -- ready for review

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

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

[Kernel-packages] [Bug 1815172]

2019-02-14 Thread Alkis Georgopoulos

Just correcting a wrong comment (#2) I made:
> It happens on both 32bit and 64bit installations.

I asked the school that reported the issue on 64bit to check again, and
they said they have a 32bit installation after all.

So the problem has only been reported in 32bit installations; I don't
know if it happened on 64bit. And btw everything is fixed now, thanks
again to all. :)

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

Title:
  Black screen on skylake after 18.0 => 18.2 update

Status in Mesa:
  Fix Released
Status in linux package in Ubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  New
Status in linux source package in Bionic:
  New
Status in mesa source package in Bionic:
  Fix Committed
Status in linux source package in Cosmic:
  New
Status in mesa source package in Cosmic:
  Fix Committed

Bug description:
  Several schools reported black screens after normally updating their
  Ubuntu boxes from 18.0.5-0ubuntu0~18.04.1 to 18.2.2-0ubuntu1~18.04.1.

  Downgrading mesa fixes the problem.

  lspci: 00:02.0 VGA compatible controller [0300]: Intel Corporation HD
  Graphics 530 [8086:1912] (rev 06) Subsystem: ASUSTeK Computer
  Inc. HD Graphics 530 [1043:8694]Kernel modules: i915

  Unfortunately I can't find a lot of useful information, here are some bits:
   * systemctl --failed says "gpu-manager" and "lightdm" have failed
   * Xorg.log is clean: https://termbin.com/6l2b
   * dmesg too: https://termbin.com/ip4e
   * It happens on lightdm/MATE, I don't know about Ubuntu GNOME.
   * If one runs `xinit` from ssh, it fails with:
  i965: Failed to submit batchbuffer: Invalid argument

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

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

[Kernel-packages] [Bug 1814655] Re: linux-raspi2: 4.4.0-1104.112 -proposed tracker

** Changed in: kernel-sru-workflow/snap-release-to-beta
   Status: Confirmed => Fix Released

** Changed in: kernel-sru-workflow/snap-release-to-edge
   Status: Confirmed => Fix Released

** Changed in: kernel-sru-workflow/snap-certification-testing
   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 --
  boot-testing-requested: true
  kernel-stable-master-bug: 1814647
- phase: Promote to Proposed
- phase-changed: Friday, 08. February 2019 21:34 UTC
+ phase: Testing
+ phase-changed: Thursday, 14. February 2019 17:11 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
certification-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
-   snap-release-to-beta: Pending -- snap not in beta channel
-   snap-release-to-edge: Pending -- snap not in edge channel
+   snap-certification-testing: Ongoing -- testing in progress
verification-testing: Ongoing -- testing in progress

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

Title:
  linux-raspi2: 4.4.0-1104.112 -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 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:
  Invalid
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow snap-certification-testing series:
  Confirmed
Status in Kernel SRU Workflow snap-release-to-beta series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-candidate series:
  New
Status in Kernel SRU Workflow snap-release-to-edge series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-stable series:
  New
Status in Kernel SRU Workflow upload-to-ppa-dnu series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-raspi2 package in Ubuntu:
  Invalid
Status in linux-raspi2 source package in Xenial:
  Confirmed

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1814647
  phase: Testing
  phase-changed: Thursday, 14. February 2019 17:11 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
certification-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
snap-certification-testing: Ongoing -- testing in progress
verification-testing: Ongoing -- testing in progress

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

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

[Kernel-packages] [Bug 1779640] Re: [Hyper-V] KVP daemon crashes at startup

Does it also happen with the lastest generic bionic kernel (4.15.0-45)?

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

Title:
  [Hyper-V] KVP daemon crashes at startup

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Bionic:
  Confirmed
Status in linux source package in Disco:
  Confirmed

Bug description:
  While testing Bionic daily build with kernel 4.15.0-20-generic we saw
  the following issue with the KVP daemon:

  KVP daemon crashes after approximatively 2 minutes of uptime and it enters in 
a failed state. The daemon can be manually started and it enters back in active 
(running) state.
  The error messages from /var/log/syslog after the daemon enters the failed 
state are the following:

  Apr 25 04:28:46 bionicDaily KVP: read failed; error:9 Bad file descriptor
  Apr 25 04:28:46 bionicDaily systemd[1]: hv-kvp-daemon.service: Main process 
exited, code=exited, status=1/FAILURE
  Apr 25 04:28:46 bionicDaily systemd[1]: hv-kvp-daemon.service: Failed with 
result 'exit-code'.
  Apr 25 04:28:59 bionicDaily systemd[1]: Started Hyper-V KVP Protocol Daemon.

  Note: There was a simmilar issue discussed on this thread
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1664663, but the
  fixing commit seems to be inclued in this Bionic build.

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

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

[Kernel-packages] [Bug 1815579] Re: Broken dependencies with nvidia-driver-390 and xserver-xorg-hwe-18.04 in bionic

2019-02-14 Thread Leopoldo

Tested `sudo apt install xserver-xorg-hwe-18.04` after activating
proposed in the affected machine. Now working as intended. Rebooted,
checked Xorg version with `sudo X -version` (X.Org X Server 1.20.1) and
run `nvidia-smi` showing driver 390.77 version and installed cards
without any issues.

So, this specific bug is fixed (I didn't test any further).

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

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

Title:
  Broken dependencies with nvidia-driver-390 and xserver-xorg-hwe-18.04
  in bionic

Status in nvidia-graphics-drivers-340 package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-340 source package in Bionic:
  Fix Committed
Status in nvidia-graphics-drivers-390 source package in Bionic:
  Fix Committed

Bug description:
  I am trying to test new HWE stack from 18.10 in my destkop Ubuntu
  18.04.1 (expected release 18.04.2 this week) and I have broken
  dependencies when installing `xserver-xorg-hwe-18.04` package with
  NVidia drivers:

  me@me-H110M-DS2:~$ sudo apt install xserver-xorg-hwe-18.04 
xserver-xorg-video-nvidia-390 
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  xserver-xorg-video-nvidia-390 is already the newest version 
(390.77-0ubuntu0.18.04.1).
  xserver-xorg-video-nvidia-390 set to manually installed.
  Some packages could not be installed. This may mean that you have
  requested an impossible situation or if you are using the unstable
  distribution that some required packages have not yet been created
  or been moved out of Incoming.
  The following information may help to resolve the situation:

  The following packages have unmet dependencies:
   xserver-xorg-hwe-18.04 : Depends: xserver-xorg-core-hwe-18.04 (>= 
2:1.17.2-2) but it is not going to be installed
Conflicts: xserver-xorg-core (>= 0~)
Recommends: xserver-xorg-video-all-hwe-18.04 but it 
is not going to be installed
  E: Unable to correct problems, you have held broken packages.

  
  Otherwise, if I try to install it without `xserver-xorg-video-nvidia-390` 
this happens:

  me@me-H110M-DS2:~$ sudo apt install xserver-xorg-hwe-18.04 
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  The following packages were automatically installed and are no longer 
required:
dkms libbsd0:i386 libdrm-amdgpu1:i386 libdrm-intel1:i386 
libdrm-nouveau2:i386 libdrm-radeon1:i386 libdrm2:i386 libedit2:i386 
libelf1:i386 libexpat1:i386 libffi6:i386 libgl1:i386 libgl1-mesa-dri:i386
libglapi-mesa:i386 libglvnd0:i386 libglx-mesa0:i386 libglx0:i386 
libllvm7:i386 libnvidia-cfg1-390 libnvidia-common-390 libnvidia-compute-390 
libnvidia-compute-390:i386 libnvidia-decode-390
libnvidia-decode-390:i386 libnvidia-encode-390 libnvidia-encode-390:i386 
libnvidia-fbc1-390 libnvidia-fbc1-390:i386 libnvidia-gl-390 
libnvidia-gl-390:i386 libnvidia-ifr1-390 libnvidia-ifr1-390:i386
libpciaccess0:i386 libsensors4:i386 libstdc++6:i386 libvdpau1 
libwayland-client0:i386 libwayland-server0:i386 libx11-6:i386 libx11-xcb1:i386 
libxau6:i386 libxcb-dri2-0:i386 libxcb-dri3-0:i386
libxcb-glx0:i386 libxcb-present0:i386 libxcb-sync1:i386 libxcb1:i386 
libxdamage1:i386 libxdmcp6:i386 libxext6:i386 libxfixes3:i386 libxnvctrl0 
libxshmfence1:i386 libxxf86vm1:i386 mesa-vdpau-drivers
nvidia-compute-utils-390 nvidia-dkms-390 nvidia-kernel-common-390 
nvidia-kernel-source-390 nvidia-prime nvidia-settings nvidia-utils-390 
pkg-config screen-resolution-extra vdpau-driver-all
  Use 'sudo apt autoremove' to remove them.
  The following additional packages will be installed:
xserver-xorg-core-hwe-18.04 xserver-xorg-input-all-hwe-18.04 
xserver-xorg-input-libinput-hwe-18.04 xserver-xorg-video-all-hwe-18.04 
xserver-xorg-video-amdgpu-hwe-18.04 xserver-xorg-video-ati-hwe-18.04
xserver-xorg-video-fbdev-hwe-18.04 xserver-xorg-video-intel-hwe-18.04 
xserver-xorg-video-nouveau-hwe-18.04 xserver-xorg-video-qxl-hwe-18.04 
xserver-xorg-video-radeon-hwe-18.04
xserver-xorg-video-vesa-hwe-18.04 xserver-xorg-video-vmware-hwe-18.04
  Suggested packages:
xfonts-100dpi | xfonts-75dpi firmware-amd-graphics xserver-xorg-video-r128 
xserver-xorg-video-mach64 firmware-misc-nonfree
  Recommended packages:
xserver-xorg-input-wacom-hwe-18.04
  The following packages will be REMOVED:
nvidia-driver-390 xserver-xorg xserver-xorg-core xserver-xorg-input-all 
xserver-xorg-input-libinput xserver-xorg-video-nvidia-390
  The following NEW packages will be installed:
xserver-xorg-core-hwe-18.04 xserver-xorg-hwe-18.04 
xserver-xorg-input-all-hwe-18.04 xserver-xorg-input-libinput-hwe-18.04

[Kernel-packages] [Bug 1813211] Re: Allow I/O schedulers to be loaded with modprobe in linux-azure

That's the expected result. Only multiqueue io schedulers will be
available for multiqueue block devices.

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

Title:
  Allow I/O schedulers to be loaded with modprobe in linux-azure

Status in linux-azure package in Ubuntu:
  Invalid
Status in linux-azure source package in Bionic:
  Fix Committed
Status in linux-azure source package in Cosmic:
  Fix Committed

Bug description:
  There was a previous request in bug
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1671203 to limit
  the IO scheduler to NOOP in linux-azure. The other schedulers were
  turned off and NOOP was made the default.

  However with new upstream releases, new schedulers where added and
  linux-azure inherited the default config value for them from the
  master kernel. That's why there are some IO schedulers built as
  modules in the extra package (mq-deadline and kyber-iosched). In order
  to use those two modules, one needs to install the -extra package and
  modprobe the modules first:

  # tail /sys/block/sd*/queue/scheduler
  ==> /sys/block/sda/queue/scheduler <==
  [none] 

  ==> /sys/block/sdb/queue/scheduler <==
  [none] 

  # apt install linux-modules-extra-4.15.0-1036-azure

  # modprobe kyber-iosched
  # tail /sys/block/sd*/queue/scheduler
  ==> /sys/block/sda/queue/scheduler <==
  [none] kyber 

  ==> /sys/block/sdb/queue/scheduler <==
  [none] kyber 

  # modprobe mq-deadline
  # tail /sys/block/sd*/queue/scheduler
  ==> /sys/block/sda/queue/scheduler <==
  [none] kyber mq-deadline 

  ==> /sys/block/sdb/queue/scheduler <==
  [none] kyber mq-deadline 

  
  The schedulers cfq and deadline have been completely disabled in LP bug 
#1671203 so they cannot be added with modprobe.

  This is a request to move back the cfq and deadline schedulers along
  with the mq-deadline and kyber-iosched schedulers to the main linux-
  azure package (in other words, not in the -extra package) and allow
  the users to be able to modprobe the schedulers when needed.

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

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

[Kernel-packages] [Bug 1748983] Re: Generate per-machine MOK for dkms signing

This bug was fixed in the package shim-signed - 1.33.1~14.04.4

---
shim-signed (1.33.1~14.04.4) trusty; urgency=medium

  * update-secureboot-policy: (LP: #1748983)
- Backport update-secureboot-policy changes to generate a MOK and guide
  users through re-enabling validation and automatically signing DKMS
  modules.
  * debian/shim-signed.postinst:
- When triggered, explicitly try to enroll the available MOK.
  * debian/shim-signed.install, openssl.cnf: Install some default configuration
for creating our self-signed key.
  * debian/shim-signed.dirs: make sure we have a directory where to put a MOK.
  * debian/templates: update templates for update-secureboot-policy changes.
  * debian/control: Breaks dkms (<< 2.2.0.3-1.1ubuntu5.14.04.10~) since we're
changing the behavior of update-secureboot-policy.

 -- Mathieu Trudel-Lapierre   Mon, 28 Jan 2019
11:02:00 -0500

** Changed in: shim-signed (Ubuntu Trusty)
   Status: Fix Committed => Fix Released

** Changed in: dkms (Ubuntu Trusty)
   Status: Fix Committed => Fix Released

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

Title:
  Generate per-machine MOK for dkms signing

Status in dkms package in Ubuntu:
  Fix Released
Status in shim-signed package in Ubuntu:
  Fix Released
Status in dkms source package in Trusty:
  Fix Released
Status in shim-signed source package in Trusty:
  Fix Released
Status in dkms source package in Xenial:
  Fix Committed
Status in shim-signed source package in Xenial:
  Fix Released

Bug description:
  [SRU Justification]
  Move to using self-signed keys for signing DKMS modules, along with the 
wizard / guide to make this work properly, to let third-party modules be signed 
and loaded by enforcing kernels, rather than disabling Secure Boot altogether.

  [Test case]
  1) Install Ubuntu in UEFI mode.
  2) Install bbswitch-dkms (or another -dkms package if useful on your system).
  3) Follow the steps in the debconf prompts (enter a password, remember the 
password for next boot).
  4) Reboot; follow the steps in MokManagerL
  4a) Pick Enroll MOK: add the new key, enter the password when prompted to do 
so.
  4b) If a dkms package was previously installed on the system (so Secure Boot 
is currently disabled in shim), pick "Change Secure Boot state". Follow the 
prompts to enter password characters. The option will only show up if Secure 
Boot validation was found to be disabled.
  5) Pick "Reboot".
  6) Log in and verify that the dkms module is loaded, using "lsmod | grep 
".
  7) Run 'modprobe ' to validate that the module can be loaded 
explicilty.
  8) Validate that there are no errors from modprobe or errors in dmesg 
concerning signing keys.

  [Regression potential]
  If anything currently relies on Secure Boot validation being disabled in 
order to correctly run with an enforcing kernel, or grub is used in enforcing 
mode, custom / third-party kernels and modules may fail to load.

  ---

  shim-signed's update-secureboot-policy should allow creating a
  machine-owner key, and using this for signing kernel modules built via
  DKMS. Key generation and enrolling should be made as easy as possible
  for users.

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

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

[Kernel-packages] [Bug 1777029] Re: fscache: Fix hanging wait on page discarded by writeback

This bug was erroneously marked for verification in bionic; verification
is not required and verification-needed-bionic is being removed.

** Tags removed: verification-needed-bionic
** Tags added: kernel-fixup-verification-needed-bionic verification-done-bionic

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

Title:
  fscache: Fix hanging wait on page discarded by writeback

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Trusty:
  Fix Released
Status in linux source package in Xenial:
  Fix Released
Status in linux source package in Artful:
  Won't Fix
Status in linux source package in Bionic:
  Fix Released

Bug description:
  == SRU Justification ==

  [Impact]
  Under heavy NFS + FSCache load, a user sometimes observes a hang in 
__fscache_wait_on_page_write+0x5f/0xa0.

  Example traces:
  [] __fscache_wait_on_page_write+0x5f/0xa0 [fscache]
  [] __fscache_uncache_all_inode_pages+0xba/0x120 [fscache]
  [] nfs_fscache_open_file+0x4e/0xc0 [nfs]

  [] __fscache_wait_on_page_write+0x5f/0xa0 [fscache]
  [] __nfs_fscache_invalidate_page+0x2c/0x80 [nfs]
  [] nfs_invalidate_page+0x63/0x90 [nfs]
  [] truncate_inode_page+0x80/0x90

  [Fix]
  Cherry-pick 2c98425720233ae3e135add0c7e869b32913502f from upstream, which is 
a patch from the FSCache maintainer.

  [Testcase]
  The user has run a NFS stress-test with a similar home-grown patch, and will 
run a stress test on the proposed kernel.

  [Regression Potential]
  Patch is limited to FSCache, so regression potential is limited.

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

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

[Kernel-packages] [Bug 1811660] Re: [SRU] Unable to modify/create-namespace over NVDIMM-N

This bug was erroneously marked for verification in bionic; verification
is not required and verification-needed-bionic is being removed.

** Tags removed: verification-needed-bionic
** Tags added: kernel-fixup-verification-needed-bionic verification-done-bionic

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

Title:
  [SRU] Unable to modify/create-namespace over NVDIMM-N

Status in The Dell-poweredge project:
  New
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  [Impact]
  Users are unable to modify or create namespaces over NVDIMM-N

  [Test Case]

  Steps to Reproduce:
  1. Setup a Dell EMC 14G server R740xd server with NVDIMM-N, update BIOS & 
NVDIMM firmware to latest available to customers.
  2. Install and boot to Ubuntu 18.04
  3. Notice that no pmems are enumerated.
  4. Try #ndctl create-namespace -> Failure with device or resource busy.

  Actual results:
  No pmems are enumerated, cannot create namespaces.
  If pmems are already present, then cannot modify the namespaces.

  Expected results:
  namespace creation should be possible

  
  [Regression Potential] 

  The Regression Risk is low, Intel not impacted but Dell is.

  
  [Other Info]
  Additional Info:
  * Seen with upstream linux-4.20.2 also.

  * Upstream bug report -
  https://github.com/pmem/ndctl/issues/78

  * Upstream kernel patch:
  https://lists.01.org/pipermail/linux-nvdimm/2019-January/019435.html

  Request you to incorporate it in bionic and xenial kernels.

To manage notifications about this bug go to:
https://bugs.launchpad.net/dell-poweredge/+bug/1811660/+subscriptions

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

[Kernel-packages] [Bug 1748983] Re: Generate per-machine MOK for dkms signing

This bug was fixed in the package dkms - 2.2.0.3-1.1ubuntu5.14.04.10

---
dkms (2.2.0.3-1.1ubuntu5.14.04.10) trusty; urgency=medium

  * debian/patches/shim_secureboot_support.patch:
- Move to signing just after module build to ensure it correctly applies
  at kernel update times. (LP: #1772950)
- Generate a new MOK if there isn't one yet, and use that so sign
  newly-built kernel modules. (LP: #1748983)
  * debian/control: Breaks: shim-signed (<< 1.33.1~14.04.4) to ensure both
are updated in lock-step since the changes above require a new version of
update-secureboot-policy to correctly generate the new MOK and enroll it
in firmware.

 -- Mathieu Trudel-Lapierre   Mon, 28 Jan 2019
11:05:49 -0500

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

Title:
  Generate per-machine MOK for dkms signing

Status in dkms package in Ubuntu:
  Fix Released
Status in shim-signed package in Ubuntu:
  Fix Released
Status in dkms source package in Trusty:
  Fix Released
Status in shim-signed source package in Trusty:
  Fix Released
Status in dkms source package in Xenial:
  Fix Committed
Status in shim-signed source package in Xenial:
  Fix Released

Bug description:
  [SRU Justification]
  Move to using self-signed keys for signing DKMS modules, along with the 
wizard / guide to make this work properly, to let third-party modules be signed 
and loaded by enforcing kernels, rather than disabling Secure Boot altogether.

  [Test case]
  1) Install Ubuntu in UEFI mode.
  2) Install bbswitch-dkms (or another -dkms package if useful on your system).
  3) Follow the steps in the debconf prompts (enter a password, remember the 
password for next boot).
  4) Reboot; follow the steps in MokManagerL
  4a) Pick Enroll MOK: add the new key, enter the password when prompted to do 
so.
  4b) If a dkms package was previously installed on the system (so Secure Boot 
is currently disabled in shim), pick "Change Secure Boot state". Follow the 
prompts to enter password characters. The option will only show up if Secure 
Boot validation was found to be disabled.
  5) Pick "Reboot".
  6) Log in and verify that the dkms module is loaded, using "lsmod | grep 
".
  7) Run 'modprobe ' to validate that the module can be loaded 
explicilty.
  8) Validate that there are no errors from modprobe or errors in dmesg 
concerning signing keys.

  [Regression potential]
  If anything currently relies on Secure Boot validation being disabled in 
order to correctly run with an enforcing kernel, or grub is used in enforcing 
mode, custom / third-party kernels and modules may fail to load.

  ---

  shim-signed's update-secureboot-policy should allow creating a
  machine-owner key, and using this for signing kernel modules built via
  DKMS. Key generation and enrolling should be made as easy as possible
  for users.

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

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

[Kernel-packages] [Bug 1786013] Re: Packaging resync

This bug was erroneously marked for verification in bionic; verification
is not required and verification-needed-bionic is being removed.

** Tags removed: verification-needed-bionic
** Tags added: kernel-fixup-verification-needed-bionic verification-done-bionic

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

Title:
  Packaging resync

Status in linux package in Ubuntu:
  Fix Released
Status in linux-azure package in Ubuntu:
  Fix Released
Status in linux-azure-edge package in Ubuntu:
  New
Status in linux source package in Precise:
  Fix Committed
Status in linux-azure source package in Precise:
  Invalid
Status in linux-azure-edge source package in Precise:
  Invalid
Status in linux source package in Trusty:
  Fix Released
Status in linux-azure source package in Trusty:
  Fix Released
Status in linux-azure-edge source package in Trusty:
  Invalid
Status in linux source package in Xenial:
  Fix Released
Status in linux-azure source package in Xenial:
  Fix Released
Status in linux-azure-edge source package in Xenial:
  Fix Released
Status in linux source package in Bionic:
  Fix Released
Status in linux-azure source package in Bionic:
  Fix Released
Status in linux-azure-edge source package in Bionic:
  Fix Released
Status in linux source package in Cosmic:
  Fix Released
Status in linux-azure source package in Cosmic:
  Fix Released
Status in linux-azure-edge source package in Cosmic:
  New
Status in linux source package in Disco:
  Fix Released
Status in linux-azure source package in Disco:
  Fix Released
Status in linux-azure-edge source package in Disco:
  New

Bug description:
  Ongoing packing resyncs.

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

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

[Kernel-packages] [Bug 1789924] Re: Missing Intel GPU pci-id's

This bug was erroneously marked for verification in bionic; verification
is not required and verification-needed-bionic is being removed.

** Tags removed: verification-needed-bionic
** Tags added: kernel-fixup-verification-needed-bionic verification-done-bionic

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

Title:
  Missing Intel GPU pci-id's

Status in libdrm package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in mesa package in Ubuntu:
  Fix Released
Status in xorg-server package in Ubuntu:
  Fix Released
Status in libdrm source package in Bionic:
  Fix Released
Status in linux source package in Bionic:
  Fix Released
Status in mesa source package in Bionic:
  Fix Committed
Status in xorg-server source package in Bionic:
  Fix Released
Status in libdrm source package in Cosmic:
  Fix Released
Status in linux source package in Cosmic:
  Fix Released
Status in mesa source package in Cosmic:
  Fix Committed
Status in xorg-server source package in Cosmic:
  Fix Released

Bug description:
  [Impact]
  There are some new Intel GPU pci-id's that need to be added to several places:

  0x3E98
  0x87C0

  and to make future additions easier, add platform definitions for
  Whiskey Lake and Amber Lake too.

  [Test case]
  Check that the user session uses the proper driver on these systems.

  [Regression potential]
  none, these just add pci-id's and platform definitions

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

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

[Kernel-packages] [Bug 1767180] Re: Bluetooth of the Asus Maximus X Hero Wifi AC motherboard doesnt work using the Realtek 8822BE driver

This bug was erroneously marked for verification in bionic; verification
is not required and verification-needed-bionic is being removed.

** Tags removed: verification-needed-bionic
** Tags added: kernel-fixup-verification-needed-bionic verification-done-bionic

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

Title:
  Bluetooth of the Asus Maximus X Hero Wifi AC motherboard doesnt work
  using the Realtek 8822BE driver

Status in linux package in Ubuntu:
  Fix Committed

Bug description:
  What you expected to happen
  For the Asus Maximus X Hero Wifi AC motherboards' bluetooth to work

  What happened instead
  Bluetooth does not work

  lsb_release -rd
  Description:  Ubuntu Bionic Beaver (development branch)
  Release:  18.04

  My custom computer uses an Asus Maximus X Hero Wifi AC motherboard,
  which uses the Realtek 8822BE driver to cotrol wifi and bluetooth.
  Support for this driver was added on kernel 4.14, however only wifi
  works. Bluetooth appears as disabled on the Bluetooth adapters
  program, but on rfkill it is not blocked, and it is not disabled on
  the motherboards' settings.

  This was tested on an Ubuntu-Mate 18.04 Beta 2, Ubuntu 16.04LTS and Ubuntu 
17.10 using kernel 4.15. Tried 4.16 just in case, but it didn't work.
  --- 
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  azul   1431 F pulseaudio
   /dev/snd/controlC0:  azul   1431 F pulseaudio
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-04-08 (18 days ago)
  InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Beta amd64 
(20180404)
  MachineType: System manufacturer System Product Name
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic 
root=UUID=d3f1f2d4-b9ff-4e28-b840-fe563d5df18d ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-20-generic N/A
   linux-backports-modules-4.15.0-20-generic  N/A
   linux-firmware 1.173
  StagingDrivers: r8822be
  Tags:  bionic staging
  Uname: Linux 4.15.0-20-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/09/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1301
  dmi.board.asset.tag: Default string
  dmi.board.name: ROG MAXIMUS X HERO (WI-FI AC)
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1301:bd04/09/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGMAXIMUSXHERO(WI-FIAC):rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  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/1767180/+subscriptions

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

[Kernel-packages] [Bug 1779827] Re: failure to boot with linux-image-4.15.0-24-generic

This bug was erroneously marked for verification in bionic; verification
is not required and verification-needed-bionic is being removed.

** Tags removed: verification-needed-bionic
** Tags added: kernel-fixup-verification-needed-bionic verification-done-bionic

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

Title:
  failure to boot with linux-image-4.15.0-24-generic

Status in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in The Bionic Beaver:
  Confirmed
Status in linux source package in Bionic:
  Fix Released

Bug description:
  This was the last OK then my 18.04 hangs after an update this morning.
  07:00 AM CEST

  Last Ok in boot was Started gnome display manager. dispatcher service
  .. tem changes.pp link was shut down

  Tried install lightdm from command line and the  response was lastest
  already installed.

  Probably it is what is coming after the lastest OK which is to be the
  error. And here I have lots of guesses..

  Any Ideas ? I need to do some work and I may not be waiting long.

  Search and browsed and now close to give up. Yeah it is a Lenovo.

  Guys: turn of auto update it is a machine killer.

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

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

[Kernel-packages] [Bug 1785171] Re: Intel I219-V Ethernet Interface on Ubuntu Linux Using e1000e Driver keeps Dropping Internet Connection

2019-02-14 Thread carlos

Hello:

I'm an ex-Ubuntu user and thought I'd add some information which may be
useful.

I came across this thread while looking for answers to problems posed by
the e1000e driver for my Sun Microsystems Ultra 24 on-board ethernet
controller.

It's an Intel Corporation 82566DM-2 Gigabit Network Controller (rev 02),
using the latest available driver for Linux (v.3.4.2.1 - 8/26/2018)
provided by Intel under Devuan ASCII, 4.9.0-8-amd64 #1 SMP Debian
4.9.130-2 (2018-10-27) x86_64 GNU/Linux.

This driver is also used for many other Inter ethernet cards under
Linux.

[quote=Tj]
[i]The solution was always to disable the power-management options via
Windows.[/i]
[/quote]

Indeed ...
If only that *were* possible under Linux.

At least in *my* case (Devuan ASCII, v.3.4.2.1 e1000e driver and ethtool
v.4.19), this has not been possible. It seems that as the driver is
loaded as a module, ethtool cannot access the controller EEE settings.

ie:

[code]
# ethtool --show-eee eth0
Cannot get EEE settings: Operation not supported
#
# ethtool --set-eee eth0 eee off
Cannot get EEE settings: Operation not supported
#
[/code]

I have no doubt that the issues this e1000e driver has are originated in
the power savings features which *do not* work properly.

Unfortunately, my attempts to get answers from Intel and Sourceforge
with respect to this were non-productive.

See:
https://forums.intel.com/s/question/0D50P4A4QxySAF/disabling-eee-on-82566dm2-gbe-controller?language=en_US

and

https://sourceforge.net/p/e1000/bugs/635/

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

Title:
Intel I219-V Ethernet Interface on Ubuntu Linux Using e1000e Driver
keeps Dropping Internet Connection

Status in linux package in Ubuntu:
Confirmed
Status in linux source package in Bionic:
Confirmed

Bug description:
I've turned up many, many new server and workstation systems over the
years on both Linux and Windows. Never seen anything like this
behaviour I'm witnessing on Ubuntu Server 18.04 before where I simply
lose Internet connectivity while using a browser. Ethernet interfaces
usually either work or they don't work.

I've configured the Intel I219-V Ethernet interface (wired Ethernet
connection, there is no wifi on this system) using the e1000e driver
for Ubuntu. The Ethernet connection is configured to use
NetworkManager via Netplan on Ubuntu 18.04 LTS Server version. ASRock
Z370m Pro4 motherboard.

The Ethernet interface will drop the Internet connectivity when I'm
using either the Firefox or Chrome browser. It usually happens when
I'm using the search features of the browser. I can't figure out what
would cause this type of behaviour. When the Internet connection
drops, the only way to get back Internet connectivity is to disconnect
the wired connection using the Ubuntu features and then re-connect
(this restarts the NetworkManager service I notice).

In the NetworkManager logs I do notice an "auth" error about a file or
directory not found. I've never seen that before.

Note: The auth error does not coincide with the loss of Internet
connectivity, but it does proceed it. Often there can be many hours
between the auth error and the actual loss of Internet connectivity.

After I reconnect the connection (via re-starting the NetworkManager
service) all will be fine for up to a day or so, but then I stress
test it with a bunch of searches using the browser and usually I can
get the Internet connectivity to drop again. Repeat the disconnect
and reconnect process again (aka re-start NetworkManager) and the
Internet connectivity will be fine again. The longest I've seen it go
without an "Internet connectivity drop" issue is about 36 hours.

I notice that the e1000e driver does not list the I219-V as a
supported Ethernet interface in the Intel documentation for the Linux
version of the driver. I'm not sure why that is. The I219-V is
supposed to used another driver, but it's not clear there's a Linux
version for of the driver for the I219-V.

I'm really disappointed that I've run into this issue with Ubuntu
Server LTS 18.04 on this motherboard. I had CentOS Server 7.4 (my
standard server OS, a great Linux distro) on this same motherboard for
a week with no issues, so I know the motherboard and the I219-V
Ethernet interface are 100% good hardware wise and can work properly.
CentOS 7.4 uses NetworkManager as the default for managing the
Ethernet interface.

The only reason I'm using Ubuntu Server 18.04 on this motherboard is
because of a specific package that Ubuntu has a newer packaged version
than CentOS. CentOS is extremely stable when it comes to basic server
functionality.

Hopefully, this bug with the I219-V Ethernet interface using the
e1000e drive for Linux can be verified and a fix rolled out.

[Kernel-packages] [Bug 1772950] Re: dkms key enrolled in mok, but dkms module fails to load

This bug was fixed in the package dkms - 2.2.0.3-1.1ubuntu5.14.04.10

---
dkms (2.2.0.3-1.1ubuntu5.14.04.10) trusty; urgency=medium

  * debian/patches/shim_secureboot_support.patch:
- Move to signing just after module build to ensure it correctly applies
  at kernel update times. (LP: #1772950)
- Generate a new MOK if there isn't one yet, and use that so sign
  newly-built kernel modules. (LP: #1748983)
  * debian/control: Breaks: shim-signed (<< 1.33.1~14.04.4) to ensure both
are updated in lock-step since the changes above require a new version of
update-secureboot-policy to correctly generate the new MOK and enroll it
in firmware.

 -- Mathieu Trudel-Lapierre   Mon, 28 Jan 2019
11:05:49 -0500

** Changed in: dkms (Ubuntu Trusty)
   Status: Fix Committed => Fix Released

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

Title:
  dkms key enrolled in mok, but dkms module fails to load

Status in dkms package in Ubuntu:
  Fix Released
Status in dkms source package in Trusty:
  Fix Released
Status in dkms source package in Xenial:
  Fix Committed
Status in dkms source package in Bionic:
  Fix Released

Bug description:
  [Impact]
  All Ubuntu users for whom Secure Boot is enabled.

  [Test cases]
  1) install dkms module (use virtualbox-dkms for example)
  2) Upgrade kernel (for example, install 4.15.0-22-generic on top of 
4.15.0-20-generic).
  3) Verify that the generated module for the new kernel (4.15.0-22-generic in 
this example) is built and signed by verifying that the file in 
/lib/modules/$kernel/updates/dkms/$module.ko ends in ~Module signature 
appended~:

  $ hexdump -Cv /lib/modules/4.15.0-22-generic/updates/dkms/vboxdrv.ko | tail 
-n 100
  [...]
  ~Module signature appended~

  4) Reboot
  5) modprobe -v the module.
  It should not respond "Required key not available", and should return with no 
error.
  6) Verify that dkms does not contain PKCS#7 errors.

  
  [Regression potential]
  Possible regressions involve failure to sign and/or be able to load modules 
after updates: failure to sign leading to a module being built but unsigned 
after a new kernel is installed or after a new DKMS module is installed, 
failure to load modules after reboot (usually caused by module being unsigned); 
failure to sign due to missing keys, signature key not being automatically 
slated for enrollment. All these potential regression scenarios present as 
failure to load a DKMS module after a reboot when it should be loaded 
successfully.

  ---

  At my last reboot, I was prompted to enable SecureBoot, so I did.

  When I booted, however, I noticed that the virtualbox service failed
  to start because it couldn't load its kernel module.  If I attempt the
  same thing, I see that there's an issue with keys:

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

  I do have keys enrolled; `mokutil --list-enrolled` produces
  http://paste.ubuntu.com/p/rntTQr5XJV/

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

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

[Kernel-packages] [Bug 1796647] Re: Shared folders cannot be mounted in ubuntu/cosmic64 due to missing vbox modules

This bug was erroneously marked for verification in bionic; verification
is not required and verification-needed-bionic is being removed.

** Tags removed: verification-needed-bionic
** Tags added: kernel-fixup-verification-needed-bionic verification-done-bionic

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

Title:
  Shared folders cannot be mounted in ubuntu/cosmic64 due to missing
  vbox modules

Status in cloud-images:
  Fix Released
Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Cosmic:
  Fix Committed

Bug description:
  SRU Justification

  Impact: Vagrant environments are no longer able to use virtualbox
  feartures like shared folders. This is due to Ubuntu Cosmic kernels
  currently shipping the upstream vboxguest module and not importing
  modules from the virtualbox-guest-dkms package.

  Fix: One solution would be to use the dkms modules for Vagrant, but
  this is not ideal. At this late stage the simplest solution is to go
  back to importing the out-of-tree modules.

  Regression Potential: Minimal. Will have no impact outside of
  virtualbox environments, and the drivers being imported come from the
  virtualbox-guest-dkms package in cosmic and are thus expected to work
  well.

  ---

  In bionic, the vboxsf module was included in linux-
  modules-...-generic:

  $ dpkg -c linux-modules-4.15.0-36-generic_4.15.0-36.39_amd64.deb | grep 
vboxsf.ko
  -rw-r--r-- root/root 63238 2018-09-24 10:08 
./lib/modules/4.15.0-36-generic/kernel/ubuntu/vbox/vboxsf/vboxsf.ko

  In cosmic, it isn't:

  $ dpkg -c ~/Downloads/linux-
  modules-4.18.0-9-generic_4.18.0-9.10_amd64.deb | grep vboxsf.ko

  This results in shared folders no longer being mountable in Ubuntu
  Vagrant boxes (and, as the other vbox modules are also missing,
  probably has other effects that haven't yet been reported).

  [Original Report]

  Just tried to test out the new cosmic64 vagrant box and get the
  following error;

  ```
  Vagrant was unable to mount VirtualBox shared folders. This is usually
  because the filesystem "vboxsf" is not available. This filesystem is
  made available via the VirtualBox Guest Additions and kernel module.
  Please verify that these guest additions are properly installed in the
  guest. This is not a bug in Vagrant and is usually caused by a faulty
  Vagrant box. For context, the command attempted was:

  mount -t vboxsf -o uid=1000,gid=1000 vagrant /vagrant

  The error output from the command was:

  /sbin/mount.vboxsf: mounting failed with the error: No such device
  ```

  I tried with ubuntu/bionic64 and it worked fine.

  I've got;
  $ vagrant version
  Installed Version: 2.1.5
  Latest Version: 2.1.5

  You're running an up-to-date version of Vagrant!
  $ VBoxManage --version
  5.2.18r124319
  $

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-images/+bug/1796647/+subscriptions

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

[Kernel-packages] [Bug 1706991] Re: ubuntu/rsi driver downlink wifi throughput drops to 5-6 Mbps when BT keyboard is connected

This bug was erroneously marked for verification in bionic; verification
is not required and verification-needed-bionic is being removed.

** Tags removed: verification-needed-bionic
** Tags added: kernel-fixup-verification-needed-bionic verification-done-bionic

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

Title:
  ubuntu/rsi driver downlink wifi throughput drops to 5-6 Mbps when BT
  keyboard is connected

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

Bug description:
  SRU Justification
  =

  [Impact]
  wifi throughput numbers are good when device is running in WLAN only mode.

  In STA+BT+BLE mode, we get expected wifi throughput numbers when BT
  device is not connected. However downlink throughput drops to 5-6 Mbps
  from 35+Mbps as soon as bluetooth keyboard is connected.

  [Fix]
  Enable UAPSD mode with some optimized parameters, so that wifi station can 
get Rx packets buffered by AP efficiently even if radio is shared with bluetooth

  [Test Case]
  Conducted throughput tests and confirmed throughput gets dropped by 60% to 
65% as expected(not more than that) when bluetooth keyboard connected.

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

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

[Kernel-packages] [Bug 1763040] Re: Merge the linux-snapdragon kernel into bionic master/snapdragon

This bug was erroneously marked for verification in bionic; verification
is not required and verification-needed-bionic is being removed.

** Tags removed: verification-needed-bionic
** Tags added: kernel-fixup-verification-needed-bionic verification-done-bionic

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

Title:
  Merge the linux-snapdragon kernel into bionic master/snapdragon

Status in linux package in Ubuntu:
  Fix Released
Status in linux-meta package in Ubuntu:
  In Progress
Status in linux source package in Bionic:
  Fix Released
Status in linux-meta source package in Bionic:
  Fix Released
Status in linux source package in Cosmic:
  Fix Released
Status in linux-meta source package in Cosmic:
  In Progress

Bug description:
  Merge the linux-snapdragon arm64 kernel into a new arm64 bionic master
  flavour called -snapdragon:

  * all the enablement patches came from the qcomlt-4.14 branch [1] and were 
merged in master
  * a new master flavour called -snapdragon was created to accomodate the 
custom config and the 
resulting kernel Image (contrary to the Image.gz kernel file generated by 
generic arm64)

  
  1: http://git.linaro.org/landing-teams/working/qualcomm/kernel.git 
release/qcomlt-4.14

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

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

[Kernel-packages] [Bug 1786110] Re: SMB3: Fix regression in server reconnect detection

This bug was erroneously marked for verification in bionic; verification
is not required and verification-needed-bionic is being removed.

** Tags removed: verification-needed-bionic
** Tags added: kernel-fixup-verification-needed-bionic verification-done-bionic

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

Title:
  SMB3: Fix regression in server reconnect detection

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

Bug description:
  Request to pull this patch from upstream into the next 4.15 kernel
  update:

  
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=b2adf22fdfba85a6701c481faccdbbb3a418ccfc

  This fixes a regression in SMB 2/3 reconnect detection. The fix has
  been backported to stable updates for 4.9.x, 4.14.x, 4.16.x and
  4.17.x. But EOL kernels 4.10.x, 4.11.x, 4.12.x, 4.13.x and 4.15.x are
  also impacted.

  Highest priority is fixing linux-azure but would recommend cherry-
  picking this patch for all affected kernels.

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

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

[Kernel-packages] [Bug 1776967] Re: glibc pkeys test fail on powerpc

This bug was erroneously marked for verification in bionic; verification
is not required and verification-needed-bionic is being removed.

** Tags removed: verification-needed-bionic
** Tags added: kernel-fixup-verification-needed-bionic verification-done-bionic

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

Title:
  glibc pkeys test fail on powerpc

Status in glibc package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Fix Released
Status in glibc source package in Bionic:
  New
Status in linux source package in Bionic:
  Invalid
Status in glibc source package in Cosmic:
  Confirmed
Status in linux source package in Cosmic:
  Fix Released

Bug description:
  powerpc introduced protection keys support, now present on 4.17
  kernel.

  glibc has a tst-pkey that fails on powerpc, and that needs further
  investigation.

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

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

[Kernel-packages] [Bug 1798863] Re: 18.10 kernel does not appear to validate kernel module signatures correctly

This bug was erroneously marked for verification in bionic; verification
is not required and verification-needed-bionic is being removed.

** Tags removed: verification-needed-bionic
** Tags added: kernel-fixup-verification-needed-bionic verification-done-bionic

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

Title:
  18.10 kernel does not appear to validate kernel module signatures
  correctly

Status in linux package in Ubuntu:
  In Progress
Status in shim package in Ubuntu:
  Invalid
Status in linux source package in Cosmic:
  Fix Released
Status in shim source package in Cosmic:
  Invalid

Bug description:
  SRU Justification

  Impact: An bug in the secure boot lockdown patches in the 18.10 kernel
  causes the results of module signature verification to be ignored,
  allowing modules with no signature or an invalid signature to be
  loaded. A second bug results in the MOK not being trusted for signing
  modules, but this bug has been masked by the first bug.

  Fix: These bugs should be fixed together to avoid regressions in dkms
  module loading under secure boot. First, fix the latter bug by
  trusting keys in the kernel's secondary keyring for module signing.
  Then fix the former bug by removing code related to trusting IMA
  signatures for loading modules under kernel lockdown.

  Test Case: Confirm the following behavior under kernel lockdown:

1) Unsigned modules cannot be loaded.

2) Modules signed with an untrusted key cannot be loaded.

3) Modules signed with the kernel's ephemeral build-time key can be
  loaded.

4) Modules signed with a MOK which has been enrolled with shim can
  be loaded.

  I have tested to verify these conditions with the proposed fixes.

  Regression Potential: This restores the behavior from previous Ubuntu
  releases, so no regressions are expected wrt those releases. In some
  cases modules that were loading under lockdown might no longer load,
  but this is the intended behavior.

  ---

  On a system with Ubuntu 18.10, with secure boot enabled, and a key
  enrolled in the MOK database, I am observing the following peculiar
  behaviors:

  * Signature verification appears to be disabled, and cannot be enabled again. 
It appeared to be enabled previously, as loading of unsigned modules was 
failing, and `mokutil --enable-validation` runs without incident; however, upon 
the next boot when attempting to confirm the change, MokManager prints an error 
message "Unable to delete Secure Boot state" after completing the password 
challenge.
  * As a result of signature verification being disabled, modules signed with 
untrusted keys taint the kernel instead of failing to load outright.
  * Regardless of signature verification being enabled or not, it seems that 
the key enrolled in the MOK is not being used for validating kernel module 
signatures. Modules signed with the key still fail the signature verification 
test and taint the kernel, even though the key is visible in the output of 
`mokutil --list-enrolled`, and testing the key with `mokutil --test-key` shows 
that it's enrolled. Also, a message acknowledging the key appears in dmesg: 
Loaded UEFI:MokListRT cert 'nvidia-installer generated signing key: 
90c957eb56dfb04d8734d54fb614ef5af6c69318' linked to secondary sys keyring
  * Also, somewhat strangely, in this state with module signature verification 
not being enforced, attempting to load a completely unsigned kernel module 
suceeds, and doesn't even log a kernel message about a missing/invalid 
signature, or taint the kernel.

  Apport report attached, which includes dmesg log showing the kernel
  acknowledging the key enrolled in the MOK database, and a signature
  verification failure and subsequent successful loading of a module
  signed with that key:

   [4.234093] Loaded UEFI:MokListRT cert 'nvidia-installer generated 
signing key: 90c957eb56dfb04d8734d54fb614ef5af6c69318' linked to secondary sys 
keyring
  ...
   [6.628452] nvidia: module verification failed: signature and/or required 
key missing - tainting kernel
  ...
   [6.637252] nvidia-nvlink: Nvlink Core is being initialized, major device 
number 238
   [6.637507] nvidia :01:00.0: enabling device (0006 -> 0007)
   [6.637620] nvidia :01:00.0: vgaarb: changed VGA decodes: 
olddecodes=io+mem,decodes=none:owns=none
   [6.737216] NVRM: loading NVIDIA UNIX x86_64 Kernel Module  410.66  Wed 
Oct 10 12:01:53 CDT 2018 (using threaded interrupts)

  This system dual-boots Ubuntu 18.04 and Ubuntu 18.10: when booted into Ubuntu 
18.04, signatures made with the same key are recognized as valid. Hence, I 
suspect that something changed in the Ubuntu 18.10 kernel which is causing 
signature verification to function in an unexpected way.
  ---
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  AudioDevicesInUse:
   USER

[Kernel-packages] [Bug 1782540] Re: Allow Raven Ridge's audio controller to be runtime suspended

This bug was erroneously marked for verification in bionic; verification
is not required and verification-needed-bionic is being removed.

** Tags removed: verification-needed-bionic
** Tags added: kernel-fixup-verification-needed-bionic verification-done-bionic

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

Title:
  Allow Raven Ridge's audio controller to be runtime suspended

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  Fix Released

Bug description:
  ===SRU Justification===
  [Impact]
  AMD Raven Ridge's audio controller doesn't get runtime suspended. It consumes 
unnecessary power.

  [Test]
  With the patch, it can get runtime suspended and save ~1W for the system.
  It can also get runtime resumed correctly when doing audio input/output.

  [Fix]
  Add AZX_DCAPS_PM_RUNTIME flag to let sound subsystem know it supports runtime 
PM.

  [Regression Potential]
  Low. This change limits to Raven Ridge's audio controller.

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

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

[Kernel-packages] [Bug 1779823] Re: xhci_hcd 0000:00:14.0: Root hub is not suspended

This bug was erroneously marked for verification in bionic; verification
is not required and verification-needed-bionic is being removed.

** Tags removed: verification-needed-bionic
** Tags added: kernel-fixup-verification-needed-bionic verification-done-bionic

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

Title:
  xhci_hcd :00:14.0: Root hub is not suspended

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  Fix Released
Status in linux-oem source package in Bionic:
  Fix Released

Bug description:
  ===SRU Justification===
  [Impact]
  Runtime suspended xHC keeps spewing out this message:
  xhci_hcd :00:14.0: Root hub is not suspended

  [Test]
  With the fix, the message stops.

  [Fix]
  Only decrement PM counter when DBC was started.

  [Regression Potential]
  Low. It fixes the overlooked logic.

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

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

[Kernel-packages] [Bug 1736393] Re: [Artful][Wyse 3040] System hang when trying to enable an offlined CPU core

This bug was erroneously marked for verification in bionic; verification
is not required and verification-needed-bionic is being removed.

** Tags removed: verification-needed-bionic
** Tags added: kernel-fixup-verification-needed-bionic verification-done-bionic

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

Title:
  [Artful][Wyse 3040] System hang when trying to enable an offlined CPU
  core

Status in HWE Next:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Invalid
Status in linux-oem source package in Xenial:
  Fix Released
Status in linux source package in Artful:
  Fix Released
Status in linux-oem source package in Artful:
  Invalid
Status in linux source package in Bionic:
  Fix Released
Status in linux-oem source package in Bionic:
  Invalid

Bug description:
  1. disable cpu[1-3] $ echo 0 > /sys/devices/system/cpu/cpu[1-3]/online
  2. enable cpu[1-3] $ echo 1 > /sys/devices/system/cpu/cpu[1-3]/online

  System will hang on step 2.

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

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

[Kernel-packages] [Bug 1764690] Re: SRU: bionic: apply 50 ZFS upstream bugfixes

This bug was erroneously marked for verification in bionic; verification
is not required and verification-needed-bionic is being removed.

** Tags removed: verification-needed-bionic
** Tags added: kernel-fixup-verification-needed-bionic verification-done-bionic

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

Title:
  SRU: bionic: apply 50 ZFS upstream bugfixes

Status in linux package in Ubuntu:
  Fix Released
Status in zfs-linux package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  Fix Released
Status in zfs-linux source package in Bionic:
  Invalid

Bug description:
  SRU Justification, bionic

  Apply the first round of SRU bugfixes for ZFS from 0.7.5 onwards from
  upstream ZFS repository. This round fixes the following ZFS bugs:

  - OpenZFS 8373 - TXG_WAIT in ZIL commit path
    Closes zfsonlinux #6403
  - zfs promote|rename .../%recv should be an error
    Closes zfsonlinux #4843, #6339
  - Fix parsable 'zfs get' for compressratios
    Closes zfsonlinux #6436, #6449
  - Fix zpool events scripted mode tab separator
    Closes zfsonlinux #6444, #6445
  - zv_suspend_lock in zvol_open()/zvol_release()
    Closes zfsonlinux #6342
  - Allow longer SPA names in stats, allows bigger pool names
    Closes zfsonlinux #6481
  - vdev_mirror: load balancing fixes
    Closes zfsonlinux #6461
  - Fix zfs_ioc_pool_sync should not use fnvlist
    Closes zfsonlinux #6529
  - OpenZFS 8375 - Kernel memory leak in nvpair code
    Closes zfsonlinux #6578
  - OpenZFS 7261 - nvlist code should enforce name length limit
    Closes zfsonlinux #6579
  - OpenZFS 5778 - nvpair_type_is_array() does not recognize
    DATA_TYPE_INT8_ARRAY
    Closes zfsonlinux #6580
  - dmu_objset: release bonus buffer in failure path
    Closes zfsonlinux #6575
  - Fix false config_cache_write events
    Closes zfsonlinux #6617
  - Fix printk() calls missing log level
    Closes zfsonlinux #6672
  - Fix abdstats kstat on 32-bit systems
    Closes zfsonlinux #6721
  - Relax ASSERT for #6526
    Closes zfsonlinux #6526
  - Fix coverity defects: 147480, 147584 (Logically dead code)
    Closes zfsonlinux #6745
  - Fix coverity defects: CID 161388 (Resource Leak)
    Closes zfsonlinux #6755
  - Use ashift=12 by default on SSDSC2BW48 disks
    Closes zfsonlinux #6774
  - OpenZFS 8558, 8602 - lwp_create() returns EAGAIN
    Closes zfsonlinux #6779
  - ZFS send fails to dump objects larger than 128PiB
    Closes zfsonlinux #6760
  - Sort output of tunables in arc_summary.py
    Closes zfsonlinux #6828
  - Fix data on evict_skips in arc_summary.py
    Closes zfsonlinux #6882, #6883
  - Fix segfault in zpool iostat when adding VDEVs
    Closes zfsonlinux #6748, #6872
  - ZTS: Fix create-o_ashift test case
    Closes zfsonlinux #6924, #6877
  - Handle invalid options in arc_summary
    Closes zfsonlinux #6983
  - Call commit callbacks from the tail of the list
    Closes zfsonlinux #6986
  - Fix 'zpool add' handling of nested interior VDEVs
    Closes zfsonlinux #6678, #6996
  - Fix -fsanitize=address memory leak
    kmem_alloc(0, ...) in userspace returns a leakable pointer.
    Closes zfsonlinux #6941
  - Revert raidz_map and _col structure types
    Closes zfsonlinux #6981, #7023
  - Use zap_count instead of cached z_size for unlink
    Closes zfsonlinux #7019
  - OpenZFS 8897 - zpool online -e fails assertion when run on non-leaf
    vdevs
    Closes zfsonlinux #7030
  - OpenZFS 8898 - creating fs with checksum=skein on the boot pools
    fails ungracefully
    Closes zfsonlinux #7031
  - Emit an error message before MMP suspends pool
    Closes zfsonlinux #7048
  - OpenZFS 8641 - "zpool clear" and "zinject" don't work on "spare"
    or "replacing" vdevs
    Closes zfsonlinux #7060
  - OpenZFS 8835 - Speculative prefetch in ZFS not working for
    misaligned reads
    Closes zfsonlinux #7062
  - OpenZFS 8972 - zfs holds: In scripted mode, do not pad columns with
    spaces
    Closes zfsonlinux #7063
  - Revert "Remove wrong ASSERT in annotate_ecksum"
    Closes zfsonlinux #7079
  - OpenZFS 8731 - ASSERT3U(nui64s, <=, UINT16_MAX) fails for large
    blocks
    Closes zfsonlinux #7079
  - Prevent zdb(8) from occasionally hanging on I/O
    Closes zfsonlinux #6999
  - Fix 'zfs receive -o' when used with '-e|-d'
    Closes zfsonlinux #7088
  - Change movaps to movups in AES-NI code
    Closes zfsonlinux #7065, #7108
  - tx_waited -> tx_dirty_delayed in trace_dmu.h
    Closes zfsonlinux #7096
  - OpenZFS 8966 - Source file zfs_acl.c,

[Kernel-packages] [Bug 1789934] Re: [18.10 FEAT] Add kernel config options for SMC-R/D

This bug was erroneously marked for verification in bionic; verification
is not required and verification-needed-bionic is being removed.

** Tags removed: verification-needed-bionic
** Tags added: kernel-fixup-verification-needed-bionic verification-done-bionic

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

Title:
  [18.10 FEAT] Add kernel config options for SMC-R/D

Status in Ubuntu on IBM z Systems:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  Invalid

Bug description:
  Add folliowing options for SMC-R/D

  CONFIG_SMC=m
  CONFIG_SMC_DIAG=m
  CONFIG_ISM=m

  
  Already provided 
  CONFIG_HAVE_PNETID with bugzilla 
  https://bugzilla.linux.ibm.com/show_bug.cgi?id=167251
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786902

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

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

[Kernel-packages] [Bug 1728244] Re: Touchpad stops working after reboot on Apollo Lake

This bug was erroneously marked for verification in bionic; verification
is not required and verification-needed-bionic is being removed.

** Tags removed: verification-needed-bionic
** Tags added: kernel-fixup-verification-needed-bionic verification-done-bionic

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

Title:
  Touchpad stops working after reboot on Apollo Lake

Status in Linux:
  Confirmed
Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Bionic:
  Fix Released

Bug description:
  ===SRU Justification===
  Hantick touchpad stops working after reboot.

  [Fix]
  Disable runtime power management for the touchpad.

  [Test]
  User confirmed it fixed the issue.
  Some users reported it doesn't work for them, I'll ask them to file new
  bugs for different touchpads.

  [Regression Potential]
  Low. Disable runtime power management doesn't affect devivce's
  funtionality. In general desktop usage the graphical session opens the
  touchpad HID device so the touchpad never get runtime suspended, so it
  won't hurt power in this case.

  ===Original Bug Report===
  On the Jumper EZBook 3 Pro (V4) laptop, using an Apollo Lake N3450 processor, 
if you install Ubuntu 17.10 (or less) with isorespin and use rEFInd as 
bootloader (this is the only way to get linux booting on this laptop) 
everything works out of the box, but after a reboot or two the touchpad stops 
working. Both in Ubuntu and Windows 10. The only way to restore functionality 
is to boot from usb key ubuntu 17.10 respined, or disassemble laptop and 
detach-reattach battery cable. This is mesg | grep i2c_hid:

  [ 2056.460636] i2c_hid i2c-SYNA3602:00: i2c_hid_get_input: incomplete report 
(27/34)
  [ 3077.604699] i2c_hid i2c-SYNA3602:00: failed to reset device.
  [ 3077.605473] dpm_run_callback(): i2c_hid_resume+0x0/0xe0 [i2c_hid] returns 
-61
  [ 3080.468156] i2c_hid i2c-SYNA3602:00: i2c_hid_get_input: incomplete report 
(27/34)

  uname -rvps
  Linux 4.10.0-32-generic #36~16.04.1-Ubuntu SMP Wed Aug 9 09:19:02 UTC 2017 
x86_64

  There has to be a bug in the kernel. Any way to avoid this?

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

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

[Kernel-packages] [Bug 1754584] Re: zfs system process hung on container stop/delete

This bug was erroneously marked for verification in bionic; verification
is not required and verification-needed-bionic is being removed.

** Tags removed: verification-needed-bionic
** Tags added: kernel-fixup-verification-needed-bionic verification-done-bionic

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

Title:
  zfs system process hung on container stop/delete

Status in Native ZFS for Linux:
  New
Status in linux package in Ubuntu:
  Fix Released
Status in zfs-linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Fix Released
Status in zfs-linux source package in Xenial:
  Fix Released
Status in linux source package in Artful:
  Fix Released
Status in zfs-linux source package in Artful:
  Fix Released
Status in linux source package in Bionic:
  Fix Released
Status in zfs-linux source package in Bionic:
  Fix Released

Bug description:
  == SRU Request [Xenial][Artful] ==

  == Justification ==

  It is possible to hang zfs asynchronous reads if a read to a page that
  is mmap'd onto the the file being read is the same offset in the
  mapping as in the file. This is caused by two lock operations on the
  page.

  == Fix ==

  Upstream ZFS fix to ensure the page is not double-locked during async
  I/O of one or more pages.

  == Testing ==

  Create a zfs pool + zfs file system, run the reproducer program in
  comment #28 on the zfs filesystem.  Without the fix this can lock up,
  with the fix this runs to completion.

  == Regression Potential ==

  Minimal, the locking fix addresses a fundamental bug in the locking
  and this should not affect ZFS read/write I/O with this fix.

  --

  Summary:
  On a Bionic system running 4.15.0-10-generic, after attempting to build 
libaio in a Bionic daily container I cannot stop or delete the container. dmesg 
shows a variety of hung tasks

  Steps to Reproduce:
  Use the following script and watch for the the hang. At that point attempt to 
stop or delete the container: http://paste.ubuntu.com/p/SxfgbxM8v7/

  Originally filed against LXD: https://github.com/lxc/lxd/issues/4314

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-10-generic 4.15.0-10.11
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  powersj2414 F pulseaudio
   /dev/snd/controlC0:  powersj2414 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar  9 09:19:11 2018
  HibernationDevice: RESUME=UUID=40a4eb28-4454-44f0-a377-ea611ce685bb
  InstallationDate: Installed on 2018-02-19 (17 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180214)
  Lsusb:
   Bus 001 Device 002: ID 8087:8001 Intel Corp.
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 002 Device 002: ID 04f2:b45d Chicony Electronics Co., Ltd
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 20BSCTO1WW
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-10-generic 
root=/dev/mapper/ubuntu--vg-root ro
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-10-generic N/A
   linux-backports-modules-4.15.0-10-generic  N/A
   linux-firmware 1.172
  RfKill:
   0: phy0: Wireless LAN
    Soft blocked: no
    Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/13/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N14ET42W (1.20 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20BSCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50512 STD
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN14ET42W(1.20):bd09/13/2017:svnLENOVO:pn20BSCTO1WW:pvrThinkPadX1Carbon3rd:rvnLENOVO:rn20BSCTO1WW:rvrSDK0E50512STD:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Carbon 3rd
  dmi.product.name: 20BSCTO1WW
  dmi.product.version: ThinkPad X1 Carbon 3rd
  dmi.sys.vendor: LENOVO
  ---
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  powersj1878 F pulseaudio
   /dev/snd/controlC0:  powersj1878 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=40a4eb28-4454-44f0-a377-ea611ce685bb
  InstallationDate: Installed on

[Kernel-packages] [Bug 1798583] Re: the new Steam Controller driver breaks it on Steam

This bug was erroneously marked for verification in bionic; verification
is not required and verification-needed-bionic is being removed.

** Tags removed: verification-needed-bionic
** Tags added: kernel-fixup-verification-needed-bionic verification-done-bionic

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

Title:
  the new Steam Controller driver breaks it on Steam

Status in Linux:
  Confirmed
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Cosmic:
  Fix Released
Status in linux source package in Disco:
  Fix Released

Bug description:
  ===SRU Justification===
  [Impact]
  New steam-hid driver breaks Unity games.

  [Fix]
  Quote from the commit message:
  "With this commit, when a HID client starts, the input device is removed;
  when the HID client ends the input device is recreated."

  [Test]
  A guy from Valve comfirms the backport works.

  [Regression Potential]
  Low. This fix is specific to hid-steam, which is a new driver introduced
  in v4.18.

  ===Original Bug Report===
  The new hid_steam driver in kernel 4.18 breaks the use of it within Steam.

  Games either:
  - Crash
  - Don't detect it at all
  - Only pick it up as player 2

  To get it working as normal, it needs blacklisting currently.

  See here: https://www.gamingonlinux.com/articles/the-steam-controller-
  on-ubuntu-1810-and-other-distributions-using-linux-kernel-418-needs-
  quick-a-fix.12775

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.18.0-10-generic 4.18.0-10.11
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  Uname: Linux 4.18.0-10-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  liam   2492 F pulseaudio
   /dev/snd/controlC0:  liam   2492 F pulseaudio
   /dev/snd/controlC1:  liam   2492 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 18 12:49:44 2018
  InstallationDate: Installed on 2017-10-18 (364 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171017.1)
  IwConfig:
   lono wireless extensions.

   enp5s0no wireless extensions.

   eno1  no wireless extensions.
  MachineType: ASUS All Series
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic 
root=UUID=2a8676f3-0045-4e66-9cd1-186ffc6a8c2a ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-10-generic N/A
   linux-backports-modules-4.18.0-10-generic  N/A
   linux-firmware 1.175
  RfKill:

  SourcePackage: linux
  UpgradeStatus: Upgraded to cosmic on 2018-10-18 (0 days ago)
  dmi.bios.date: 08/10/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1901
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: SABERTOOTH X99
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: PCS
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1901:bd08/10/2015:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnSABERTOOTHX99:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: ASUS MB
  dmi.product.name: All Series
  dmi.product.sku: All
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS

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

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

[Kernel-packages] [Bug 1767133] Re: linux-image-4.15.0-20-generic install after upgrade from xenial breaks

This bug was erroneously marked for verification in bionic; verification
is not required and verification-needed-bionic is being removed.

** Tags removed: verification-needed-bionic
** Tags added: kernel-fixup-verification-needed-bionic verification-done-bionic

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

Title:
  linux-image-4.15.0-20-generic install after upgrade from xenial breaks

Status in linux package in Ubuntu:
  Fix Released
Status in linux-hwe-edge package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Invalid
Status in linux-hwe-edge source package in Xenial:
  Fix Released
Status in linux source package in Bionic:
  Fix Released
Status in linux-hwe-edge source package in Bionic:
  Invalid

Bug description:
  [Impact]
  Some upgrades from xenial to bionic break.

  [Test Case]
  Change sources.list from xenial to bionic, then apt install 
linux-image-4.15.0-20-generic.

  [Regression Potential]
  The kernel may be uninstallable if there is no linux-base with the 
appropriate version in the archive.

  

  When installing the linux-image-4.15.0-20-generic kernel from bionic
  on xenial breaks because of the unversioned Depends on linux-base.

  /var/lib/dpkg/info/linux-image-4.15.0-20-generic.postinst: 50: 
/var/lib/dpkg/info/linux-image-4.15.0-20-generic.postinst: 
linux-update-symlinks: not found
  dpkg: error processing package linux-image-4.15.0-20-generic (--configure):
   subprocess installed post-installation script returned error exit status 127
  Errors were encountered while processing:
   linux-image-4.15.0-20-generic
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  If the trigger is called, when some meta packages are installed, it
  won't happen. If all packages are upgraded, it's possible linux-base
  is going to be upgraded first, so the problem won't happen either.

  So, not all upgrades will be affected.

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

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

[Kernel-packages] [Bug 1800562] Re: Replace "nousb" option in kdump command-line for the newer "usbcore.nousb"

2019-02-14 Thread Heitor R. Alves de Siqueira

** Description changed:

- Since kernel v4.5, the correct parameter to disable USB subsystem
- initialization is "usbcore.nousb" always (instead of "nousb" in case the
- subsystem is built-in). This was changed by commit 097a9ea0e48 ("usb:
- make "nousb" a clear module parameter").
+ [Impact]
+ Crash kernels come up with the usb subsystem enabled, even when it should be 
disabled by default.
+ 
+ 
+ [Description]
+ Since kernel v4.5, the correct parameter to disable USB subsystem 
initialization is "usbcore.nousb" always (instead of "nousb" in case the 
subsystem is built-in). This was changed by commit 097a9ea0e48 ("usb: make 
"nousb" a clear module parameter").
  
  We need to take this into account in kdump-tools, or else we may boot
  with USB in kdump even the command-line saying the opposite.
+ 
+ This affects Xenial onwards, since the system may be running an HWE or
+ other supported v4.5+ kernel.
+ 
+ [Test Case]
+ 1) Deploy a Disco VM e.g. with uvt-kvm
+ 2) Install the kdump-tools package
+ 3) Run `kdump-config test`and check for the 'usbcore.nousb' parameter:
+ 
+ $ kdump-config test
+ [...]
+ kexec command to be used:
+   /sbin/kexec -p --command-line="BOOT_IMAGE=/boot/vmlinuz-4.15.0-45-generic 
root=LABEL=cloudimg-rootfs ro console=tty1 console=ttyS0 nr_cpus=1 
systemd.unit=kdump-tools.service irqpoll nousb ata_piix.prefer_ms_hyperv=0" 
/var/lib/kdump/vmlinuz
+ 
+ [Regression Potential]
+ The regression potential is very low, since it doesn't need any changes in 
makedumpfile and we're only adding a parameter on the crashkernel cmdline.
+ According to kernel documentation [0], unknown parameters will be ignored if 
they contain a dot (usbcore.nousb), so this change should have no impact on 
v4.4 and earlier kernels.
+ Nonetheless, the fix will be tested with autopkgtests and normal kdump 
use-case scenarios.

** Description changed:

  [Impact]
  Crash kernels come up with the usb subsystem enabled, even when it should be 
disabled by default.
- 
  
  [Description]
  Since kernel v4.5, the correct parameter to disable USB subsystem 
initialization is "usbcore.nousb" always (instead of "nousb" in case the 
subsystem is built-in). This was changed by commit 097a9ea0e48 ("usb: make 
"nousb" a clear module parameter").
  
  We need to take this into account in kdump-tools, or else we may boot
  with USB in kdump even the command-line saying the opposite.
  
  This affects Xenial onwards, since the system may be running an HWE or
  other supported v4.5+ kernel.
  
  [Test Case]
  1) Deploy a Disco VM e.g. with uvt-kvm
  2) Install the kdump-tools package
  3) Run `kdump-config test`and check for the 'usbcore.nousb' parameter:
  
  $ kdump-config test
  [...]
  kexec command to be used:
-   /sbin/kexec -p --command-line="BOOT_IMAGE=/boot/vmlinuz-4.15.0-45-generic 
root=LABEL=cloudimg-rootfs ro console=tty1 console=ttyS0 nr_cpus=1 
systemd.unit=kdump-tools.service irqpoll nousb ata_piix.prefer_ms_hyperv=0" 
/var/lib/kdump/vmlinuz
+   /sbin/kexec -p --command-line="BOOT_IMAGE=/boot/vmlinuz-4.15.0-45-generic 
root=LABEL=cloudimg-rootfs ro console=tty1 console=ttyS0 nr_cpus=1 
systemd.unit=kdump-tools.service irqpoll nousb ata_piix.prefer_ms_hyperv=0" 
/var/lib/kdump/vmlinuz
  
  [Regression Potential]
  The regression potential is very low, since it doesn't need any changes in 
makedumpfile and we're only adding a parameter on the crashkernel cmdline.
  According to kernel documentation [0], unknown parameters will be ignored if 
they contain a dot (usbcore.nousb), so this change should have no impact on 
v4.4 and earlier kernels.
  Nonetheless, the fix will be tested with autopkgtests and normal kdump 
use-case scenarios.
+ 
+ [0] https://www.kernel.org/doc/Documentation/admin-guide/kernel-
+ parameters.rst

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

Title:
  Replace "nousb" option in kdump command-line for the newer
  "usbcore.nousb"

Status in makedumpfile package in Ubuntu:
  Confirmed
Status in makedumpfile source package in Xenial:
  Confirmed
Status in makedumpfile source package in Bionic:
  Confirmed
Status in makedumpfile source package in Cosmic:
  Confirmed
Status in makedumpfile source package in Disco:
  Confirmed

Bug description:
  [Impact]
  Crash kernels come up with the usb subsystem enabled, even when it should be 
disabled by default.

  [Description]
  Since kernel v4.5, the correct parameter to disable USB subsystem 
initialization is "usbcore.nousb" always (instead of "nousb" in case the 
subsystem is built-in). This was changed by commit 097a9ea0e48 ("usb: make 
"nousb" a clear module parameter").

  We need to take this into account in kdump-tools, or else we may boot
  with USB in kdump even the command-line saying the opposite.

  This affects Xenial onwards, since the system may be running an HWE or
  other supported v4.5+ kernel.

  [Test Case]

[Kernel-packages] [Bug 1765564] Re: fsnotify: Fix fsnotify_mark_connector race

This bug was erroneously marked for verification in bionic; verification
is not required and verification-needed-bionic is being removed.

** Tags removed: verification-needed-bionic
** Tags added: kernel-fixup-verification-needed-bionic verification-done-bionic

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

Title:
  fsnotify: Fix fsnotify_mark_connector race

Status in Linux:
  Incomplete
Status in linux package in Ubuntu:
  Fix Released
Status in linux-azure package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Invalid
Status in linux-azure source package in Xenial:
  Fix Released
Status in linux source package in Artful:
  Fix Released
Status in linux-azure source package in Artful:
  Invalid
Status in linux source package in Bionic:
  Fix Released
Status in linux-azure source package in Bionic:
  Fix Released

Bug description:
  On Azure we have had sporadic cases of soft lockups in fsnotify that
  may very well be mitigated by the following fix. The LKML thread is
  "kernel panics with 4.14.X".

  This should be applied to 4.13 and 4.15 versions of the linux-azure
  kernel, and possibly the 4.15 generic kernel in bionic as well.

  -

  fsnotify() acquires a reference to a fsnotify_mark_connector through
  the SRCU-protected pointer to_tell->i_fsnotify_marks. However, it
  appears that no precautions are taken in fsnotify_put_mark() to
  ensure that fsnotify() drops its reference to this
  fsnotify_mark_connector before assigning a value to its 'destroy_next'
  field. This can result in fsnotify_put_mark() assigning a value
  to a connector's 'destroy_next' field right before fsnotify() tries to
  traverse the linked list referenced by the connector's 'list' field.
  Since these two fields are members of the same union, this behavior
  results in a kernel panic.

  This issue is resolved by moving the connector's 'destroy_next' field
  into the object pointer union. This should work since the object pointer
  access is protected by both a spinlock and the value of the 'flags'
  field, and the 'flags' field is cleared while holding the spinlock in
  fsnotify_put_mark() before 'destroy_next' is updated. It shouldn't be
  possible for another thread to accidentally read from the object pointer
  after the 'destroy_next' field is updated.

  The offending behavior here is extremely unlikely; since
  fsnotify_put_mark() removes references to a connector (specifically,
  it ensures that the connector is unreachable from the inode it was
  formerly attached to) before updating its 'destroy_next' field, a
  sizeable chunk of code in fsnotify_put_mark() has to execute in the
  short window between when fsnotify() acquires the connector reference
  and saves the value of its 'list' field. On the HEAD kernel, I've only
  been able to reproduce this by inserting a udelay(1) in fsnotify().
  However, I've been able to reproduce this issue without inserting a
  udelay(1) anywhere on older unmodified release kernels, so I believe
  it's worth fixing at HEAD.

  References: https://bugzilla.kernel.org/show_bug.cgi?id=199437
  Fixes: 08991e83b7286635167bab40927665a90fb00d81
  CC: sta...@vger.kernel.org
  Signed-off-by: Robert Kolchmeyer 
  Signed-off-by: Jan Kara 

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

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

[Kernel-packages] [Bug 1808318] Re: powerpc test in ubuntu_kernel_selftest failed on Cosmic P8/P9

This bug was erroneously marked for verification in bionic; verification
is not required and verification-needed-bionic is being removed.

** Tags removed: verification-needed-bionic
** Tags added: kernel-fixup-verification-needed-bionic verification-done-bionic

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

Title:
  powerpc test in ubuntu_kernel_selftest failed on Cosmic P8/P9

Status in ubuntu-kernel-tests:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Cosmic:
  Fix Released

Bug description:
  == Justification ==
  Commit b2d35fa5fc80 ("selftests: add headers_install to lib.mk")
  introduced a requirement that Makefiles more than one level below the
  selftests directory need to define top_srcdir, but it didn't update
  any of the powerpc Makefiles.

  This broke building all the powerpc selftests with eg:

    make[1]: Entering directory '/src/linux/tools/testing/selftests/powerpc'
    BUILD_TARGET=/src/linux/tools/testing/selftests/powerpc/alignment; mkdir -p 
$BUILD_TARGET; make OUTPUT=$BUILD_TARGET -k -C alignment all
    make[2]: Entering directory 
'/src/linux/tools/testing/selftests/powerpc/alignment'
    ../../lib.mk:20: ../../../../scripts/subarch.include: No such file or 
directory
    make[2]: *** No rule to make target '../../../../scripts/subarch.include'.
    make[2]: Failed to remake makefile '../../../../scripts/subarch.include'.
    Makefile:38: recipe for target 'alignment' failed

  == Fix ==
  7e0cf1c983b5 (selftests/powerpc: Fix Makefiles for headers_install change)
  It can be cherry-picked for Cosmic. And it's already landed in Disco.

  == Regression Potential ==
  None, this just fixes the broken build issue for the test. Nothing else will 
be affected.

  
  ===
  This test passed with 4.18.0-12 on the last cycle [1]
  But failed with the proposed 4.18.0-13 this time.

  Test failed to build because of a missing include file:
  50.   ../../lib.mk:20: ../../../../scripts/subarch.include: No such file or 
directory

  Tried to reproduce this cycle with 4.18.0-12 first and this can be
  reproduced as well.

  39.   make: Entering directory 
'/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/powerpc'
  40.   
BUILD_TARGET=/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/powerpc/alignment;
 mkdir -p $BUILD_TARGET; make OUTPUT=$BUILD_TARGET -k -C alignment all
  41.   make[1]: Entering directory 
'/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/powerpc/alignment'
  42.   gcc -std=gnu99 -O2 -Wall -Werror 
-DGIT_VERSION='"Ubuntu-4.18.0-12.13-0-g3d21f8e15-dirty"' 
-I/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/powerpc/include
 copy_unaligned.c ../harness.c ../utils.c copy_paste_unaligned_common.c -o 
/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/powerpc/alignment/copy_unaligned
  43.   gcc -std=gnu99 -O2 -Wall -Werror 
-DGIT_VERSION='"Ubuntu-4.18.0-12.13-0-g3d21f8e15-dirty"' 
-I/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/powerpc/include
 copy_first_unaligned.c ../harness.c ../utils.c copy_paste_unaligned_common.c 
-o 
/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/powerpc/alignment/copy_first_unaligned
  44.   gcc -std=gnu99 -O2 -Wall -Werror 
-DGIT_VERSION='"Ubuntu-4.18.0-12.13-0-g3d21f8e15-dirty"' 
-I/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/powerpc/include
 paste_unaligned.c ../harness.c ../utils.c copy_paste_unaligned_common.c -o 
/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/powerpc/alignment/paste_unaligned
  45.   gcc -std=gnu99 -O2 -Wall -Werror 
-DGIT_VERSION='"Ubuntu-4.18.0-12.13-0-g3d21f8e15-dirty"' 
-I/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/powerpc/include
 paste_last_unaligned.c ../harness.c ../utils.c copy_paste_unaligned_common.c 
-o 
/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/powerpc/alignment/paste_last_unaligned
  46.   gcc -std=gnu99 -O2 -Wall -Werror 
-DGIT_VERSION='"Ubuntu-4.18.0-12.13-0-g3d21f8e15-dirty"' 
-I/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/powerpc/include
 alignment_handler.c ../harness.c ../utils.c copy_paste_unaligned_common.c -o 
/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/powerpc/alignment/alignment_handler
  47.   make[1]: Leaving directory 
'/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/powerpc/alignment'
  48.   make: Leaving directory

[Kernel-packages] [Bug 1794477] Re: Accelerated networking (SR-IOV VF) broken in 18.10 daily

This bug was erroneously marked for verification in bionic; verification
is not required and verification-needed-bionic is being removed.

** Tags removed: verification-needed-bionic
** Tags added: kernel-fixup-verification-needed-bionic verification-done-bionic

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

Title:
  Accelerated networking (SR-IOV VF) broken in 18.10 daily

Status in linux package in Ubuntu:
  Invalid
Status in linux-azure package in Ubuntu:
  Fix Released
Status in linux source package in Cosmic:
  Invalid
Status in linux-azure source package in Cosmic:
  Fix Released

Bug description:
  While testing Ubuntu 18.10 daily from cloud-images repo, on Azure, we 
discovered that accelerated networking wasn’t working inside the VM.
  No VF shows up inside the VM and lspci didn’t show any Mellanox drivers in 
use.
  We tested the daily build on Hyper-V also, but there the Mellanox VF is 
functional, with the same mlx4 drivers.

  To give more details about this:
  • No mellanox logs are showing up in dmesg or syslog.
  • Modinfo mlx4_core/mlx4_en finds the module, but lsmod doesn’t show it as 
loaded, although Accelerated Networking is enabled for the Azure VM, so this 
should happen transparently.
  • Modprobe  -r mlx4_core && modprobe mlx4_core is giving 0 exit code, but 
nothing really happens. And no Mellanox messages are logged in dmesg/syslog.
  - There are no entries in the logs to show anything about the drivers or 
netvsc/pci-hyperv that might relate to this issue.

  Kernel: 4.18.0-7-generic

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

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

[Kernel-packages] [Bug 1748983] Re: Generate per-machine MOK for dkms signing

This bug was fixed in the package shim-signed - 1.33.1~16.04.4

---
shim-signed (1.33.1~16.04.4) xenial; urgency=medium

  * update-secureboot-policy: (LP: #1748983)
- Backport update-secureboot-policy changes to generate a MOK and guide
  users through re-enabling validation and automatically signing DKMS
  modules.
  * debian/shim-signed.postinst:
- When triggered, explicitly try to enroll the available MOK.
  * debian/shim-signed.install, openssl.cnf: Install some default configuration
for creating our self-signed key.
  * debian/shim-signed.dirs: make sure we have a directory where to put a MOK.
  * debian/templates: update templates for update-secureboot-policy changes.
  * debian/control: Breaks dkms (<< 2.2.0.3-2ubuntu11.5~) since we're changing
the behavior of update-secureboot-policy.

 -- Mathieu Trudel-Lapierre   Mon, 28 Jan 2019
10:22:31 -0500

** Changed in: shim-signed (Ubuntu Xenial)
   Status: Fix Committed => Fix Released

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

Title:
  Generate per-machine MOK for dkms signing

Status in dkms package in Ubuntu:
  Fix Released
Status in shim-signed package in Ubuntu:
  Fix Released
Status in dkms source package in Trusty:
  Fix Released
Status in shim-signed source package in Trusty:
  Fix Released
Status in dkms source package in Xenial:
  Fix Committed
Status in shim-signed source package in Xenial:
  Fix Released

Bug description:
  [SRU Justification]
  Move to using self-signed keys for signing DKMS modules, along with the 
wizard / guide to make this work properly, to let third-party modules be signed 
and loaded by enforcing kernels, rather than disabling Secure Boot altogether.

  [Test case]
  1) Install Ubuntu in UEFI mode.
  2) Install bbswitch-dkms (or another -dkms package if useful on your system).
  3) Follow the steps in the debconf prompts (enter a password, remember the 
password for next boot).
  4) Reboot; follow the steps in MokManagerL
  4a) Pick Enroll MOK: add the new key, enter the password when prompted to do 
so.
  4b) If a dkms package was previously installed on the system (so Secure Boot 
is currently disabled in shim), pick "Change Secure Boot state". Follow the 
prompts to enter password characters. The option will only show up if Secure 
Boot validation was found to be disabled.
  5) Pick "Reboot".
  6) Log in and verify that the dkms module is loaded, using "lsmod | grep 
".
  7) Run 'modprobe ' to validate that the module can be loaded 
explicilty.
  8) Validate that there are no errors from modprobe or errors in dmesg 
concerning signing keys.

  [Regression potential]
  If anything currently relies on Secure Boot validation being disabled in 
order to correctly run with an enforcing kernel, or grub is used in enforcing 
mode, custom / third-party kernels and modules may fail to load.

  ---

  shim-signed's update-secureboot-policy should allow creating a
  machine-owner key, and using this for signing kernel modules built via
  DKMS. Key generation and enrolling should be made as easy as possible
  for users.

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

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

[Kernel-packages] [Bug 1785780] Re: TB 16 issue on Dell Lattitude 7490 with large amount of data

This bug was erroneously marked for verification in bionic; verification
is not required and verification-needed-bionic is being removed.

** Tags removed: verification-needed-bionic
** Tags added: kernel-fixup-verification-needed-bionic verification-done-bionic

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

Title:
  TB 16 issue on Dell Lattitude 7490 with large amount of data

Status in Dell Sputnik:
  New
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  Fix Released
Status in linux source package in Cosmic:
  Fix Released

Bug description:
  ===SRU Justification===
  [Impact]
  Packets are silently corrupted on Dell TB16's ethernet.

  [Fix]
  Disable RX aggregation on new Dell TB16 dock.

  [Test]
  User confirms the patch fixes the issue.

  [Regression Potential]
  Low. The workaround already works, we just add a new USB serial to let
  new TB16 dock also uses this workaround.

  ===Original Bug Report===
  Hi.

  Large amount of data gets corrupted when using the TB16 ethernet port.
  (rsync synchronization, etc... )

  We can confirm this issue on this kernel. Creating new issue as stated
  in this bug (#1729674)

  Linux E7490 4.15.0-29-generic #31-Ubuntu SMP Tue Jul 17 15:39:52 UTC
  2018 x86_64 x86_64 x86_64 GNU/Linux

  On my Fedora is this still an issue even with announced bugfix (link copied 
from this discussion #78.
  Linux username-localdomain 4.17.9-200.fc28.x86_64 #1 SMP Mon Jul 23 21:41:29 
UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

  It's fixed by turning the checksum offload off (tested on the Fedora .
  sudo ethtool --offload enp11s0u1u2 rx off

  https://bugs.launchpad.net/dell-sputnik/+bug/1729674

  related in bugzilla:
  ---
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 1955 F pulseaudio
  CasperVersion: 1.394
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  LiveMediaBuild: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
  MachineType: Dell Inc. Latitude 7490
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz 
file=/cdrom/preseed/username.seed boot=casper quiet splash ---
  ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-29-generic N/A
   linux-backports-modules-4.15.0-29-generic  N/A
   linux-firmware 1.173.1
  Tags:  bionic
  Uname: Linux 4.15.0-29-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 06/07/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.4.1
  dmi.board.name: 0KP0FT
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.4.1:bd06/07/2018:svnDellInc.:pnLatitude7490:pvr:rvnDellInc.:rn0KP0FT:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Latitude
  dmi.product.name: Latitude 7490
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/dell-sputnik/+bug/1785780/+subscriptions

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

[Kernel-packages] [Bug 1748345] Re: QCA9377 requires more IRAM banks for its new firmware

This bug was erroneously marked for verification in bionic; verification
is not required and verification-needed-bionic is being removed.

** Tags removed: verification-needed-bionic
** Tags added: kernel-fixup-verification-needed-bionic verification-done-bionic

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

Title:
  QCA9377 requires more IRAM banks for its new firmware

Status in HWE Next:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Fix Released
Status in linux-oem source package in Xenial:
  Fix Released

Bug description:
  [Impact]
  The new firmware for QCA9377 supports Qualcomm's RED(Radio Equipment 
Directive) compliance and requires more IRAM banks. The origin 4 banks doesn't 
fit the new BDF and firmware.

  [Fix]
  Change the bank number from 4 to 9.

  [Regression Potential]
  Low, increasing the number of IRAM banks should be no harm.

  [Misc]
  Currently, both driver patch and new firmware do not upstream yet. For the 
sake of avoiding dkms package, we can change t
  he IRAM bank number before their patch is ready.

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

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

[Kernel-packages] [Bug 1748983] Update Released

2019-02-14 Thread Łukasz Zemczak

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

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

Title:
  Generate per-machine MOK for dkms signing

Status in dkms package in Ubuntu:
  Fix Released
Status in shim-signed package in Ubuntu:
  Fix Released
Status in dkms source package in Trusty:
  Fix Committed
Status in shim-signed source package in Trusty:
  Fix Committed
Status in dkms source package in Xenial:
  Fix Committed
Status in shim-signed source package in Xenial:
  Fix Committed

Bug description:
  [SRU Justification]
  Move to using self-signed keys for signing DKMS modules, along with the 
wizard / guide to make this work properly, to let third-party modules be signed 
and loaded by enforcing kernels, rather than disabling Secure Boot altogether.

  [Test case]
  1) Install Ubuntu in UEFI mode.
  2) Install bbswitch-dkms (or another -dkms package if useful on your system).
  3) Follow the steps in the debconf prompts (enter a password, remember the 
password for next boot).
  4) Reboot; follow the steps in MokManagerL
  4a) Pick Enroll MOK: add the new key, enter the password when prompted to do 
so.
  4b) If a dkms package was previously installed on the system (so Secure Boot 
is currently disabled in shim), pick "Change Secure Boot state". Follow the 
prompts to enter password characters. The option will only show up if Secure 
Boot validation was found to be disabled.
  5) Pick "Reboot".
  6) Log in and verify that the dkms module is loaded, using "lsmod | grep 
".
  7) Run 'modprobe ' to validate that the module can be loaded 
explicilty.
  8) Validate that there are no errors from modprobe or errors in dmesg 
concerning signing keys.

  [Regression potential]
  If anything currently relies on Secure Boot validation being disabled in 
order to correctly run with an enforcing kernel, or grub is used in enforcing 
mode, custom / third-party kernels and modules may fail to load.

  ---

  shim-signed's update-secureboot-policy should allow creating a
  machine-owner key, and using this for signing kernel modules built via
  DKMS. Key generation and enrolling should be made as easy as possible
  for users.

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

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

[Kernel-packages] [Bug 1775217] Re: bluetooth controller fail after suspend with USB autosuspend on XPS 13 9360

** Tags removed: verification-needed-bionic
** Tags added: kernel-fixup-verification-needed-bionic

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

Title:
  bluetooth controller fail after suspend with USB autosuspend on XPS 13
  9360

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

Bug description:
  == SRU Justification ==
  This is a regression introduced in v4.15 and Bionic.  The bluetooth
  controller fails after suspend with USB autosuspend on an XPS 13 9360.

  This regression is fixed by mainline commit 596b07a9a226.  This commit
  was also cc'd to upstream stable, but it has not landed in Bionic via
  stable updates as of yet.

  == Fix ==
  596b07a9a226 ("Bluetooth: btusb: Add Dell XPS 13 9360 to 
btusb_needs_reset_resume_table")

  == Regression Potential ==
  Low.  This patch has also been cc'd to upstream stable, so it recieved
  additonal upstream review.

  == Test Case ==
  A test kernel was built with this patch and tested by the original bug 
reporter.
  The bug reporter states the test kernel resolved the bug.


  
  More information here: https://bugzilla.redhat.com/show_bug.cgi?id=1514836

  Patch:
  
https://git.kernel.org/pub/scm/linux/kernel/git/bluetooth/bluetooth.git/commit/?id=596b07a9a22656493726edf1739569102bd3e136

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-generic 4.15.0.22.23
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  guilhem2319 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jun  5 18:19:20 2018
  HibernationDevice: RESUME=UUID=bfa874ab-9c2f-4228-9fd1-51267b4ea3c3
  InstallationDate: Installed on 2018-02-26 (99 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180225)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0c45:670c Microdia
   Bus 001 Device 002: ID 0cf3:e300 Atheros Communications, Inc.
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 13 9360
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-22-generic 
root=UUID=287736d3-3b35-4262-a175-3254aa366f41 ro rootflags=subvol=@ quiet 
splash i915.enable_rc6=1 i915.enable_psr=2 i915.enable_guc_loading=1 
i915.enable_guc_submission=1 i915.semaphores=1 i915.disable_power_well=0 
vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-22-generic N/A
   linux-backports-modules-4.15.0-22-generic  N/A
   linux-firmware 1.173.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/26/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.6.2
  dmi.board.name: 02PG84
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.6.2:bd02/26/2018:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn02PG84:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9360
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1755857] Re: devpts: handle bind-mounts

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
bionic' to 'verification-done-bionic'. If the problem still exists,
change the tag 'verification-needed-bionic' to 'verification-failed-
bionic'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!

** Tags added: verification-needed-bionic

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

Title:
devpts: handle bind-mounts

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

Bug description:
Hey everyone,

I sent a few patches to fix a regression caused by wrong behavior in
the devpts filesystem when used with the TIOCGPTPEER ioctl() we
implemented a while back. The context and reproducer can be taken from
my following commit message. The required patches are in Greg's tree
and are:

1.
https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/tty.git/commit/?h=tty-testing=7d71109df186d630a41280670c8d71d0cf9b0da9
2.
https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/tty.git/commit/?h=tty-testing=a319b01d9095da6f6c54bd20c1f1300762506255
3.
https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/tty.git/commit/?h=tty-testing=4e15f760a43c7cb88e2b7ad6882501ccab5de29f
4.
https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/tty.git/commit/?h=tty-testing=ce290a19609d5ecd4a240a4750e0ed9a476cf015

devpts: resolve devpts bind-mounts
Most libcs will still look at /dev/ptmx when opening the master fd of a pty
device. When /dev/ptmx is a bind-mount of /dev/pts/ptmx and the TIOCGPTPEER
ioctl() is used to safely retrieve a file descriptor for the slave side of
the pty based on the master fd, the /proc/self/fd/{0,1,2} symlinks will
point to /. A very simply reproducer for this issue presupposing a libc
that uses TIOCGPTPEER in its openpty() implementation is:

unshare --mount
mount --bind /dev/pts/ptmx /dev/ptmx
chmod 666 /dev/ptmx
script
ls -al /proc/self/fd/0

Having bind-mounts of /dev/pts/ptmx to /dev/ptmx not working correctly is a
regression. In addition, it is also a fairly common scenario in containers
employing user namespaces.

The reason for the current failure is that the kernel tries to verify the
useability of the devpts filesystem without resolving the /dev/ptmx
bind-mount first. This will lead it to detect that the dentry is escaping
its bind-mount. The reason is that while the devpts filesystem mounted at
/dev/pts has the devtmpfs mounted at /dev as its parent mount:

21 -- -- / /dev
-- 21 -- / /dev/pts

devtmpfs and devpts are on different devices

-- -- 0:6 / /dev
-- -- 0:20 / /dev/pts

This has the consequence that the pathname of the parent directory of the
devpts filesystem mount at /dev/pts is /. So if /dev/ptmx is a bind-mount
of /dev/pts/ptmx then the /dev/ptmx bind-mount and the devpts mount at
/dev/pts will end up being located on the same device which is recorded in
the superblock of their vfsmount. This means the parent directory of the
/dev/ptmx bind-mount will be /ptmx:

-- -- /ptmx /dev/ptmx

Without the bind-mount resolution patch the kernel will now perform the
bind-mount escape check directly on /dev/ptmx. The function responsible for
this is devpts_ptmx_path() which calls pts_path() which in turn calls
path_parent_directory(). Based on the above explanation,
path_parent_directory() will yield / as the parent directory for the
/dev/ptmx bind-mount and not the expected /dev. Thus, the kernel detects
that /dev/ptmx is escaping its bind-mount and will set /proc//fd/
to /.

This patch changes the logic to first resolve any bind-mounts. After the
bind-mounts have been resolved (i.e. we have traced it back to the
associated devpts mount) devpts_ptmx_path() can be called. In order to
guarantee correct path generation for the slave file descriptor the kernel
now requires that a pts directory is found in the parent directory of the
ptmx bind-mount. This implies that when doing bind-mounts the ptmx
bind-mount and the devpts mount should have a common parent directory. A
valid example is:

mount -t devpts devpts /dev/pts
mount --bind /dev/pts/ptmx /dev/ptmx

an invalid example is:

mount -t devpts devpts /dev/pts
mount --bind /dev/pts/ptmx /ptmx

This allows us to support:
- calling open on ptmx devices located inside non-standard devpts mounts:
mount -t devpts devpts /mnt
master = open("/mnt/ptmx", ...);
slave = ioctl(master, TIOCGPTPEER, ...);
- calling open on ptmx devices

[Kernel-packages] [Bug 1752655] Re: retpoline: ignore %cs:0xNNN constant indirections

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
bionic' to 'verification-done-bionic'. If the problem still exists,
change the tag 'verification-needed-bionic' to 'verification-failed-
bionic'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-bionic

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

Title:
  retpoline: ignore %cs:0xNNN constant indirections

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

Bug description:
  These are paravirt style indirections and can be ignored.

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

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

[Kernel-packages] [Bug 1761534] Re: "ip a" command on a guest VM shows UNKNOWN status

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
bionic' to 'verification-done-bionic'. If the problem still exists,
change the tag 'verification-needed-bionic' to 'verification-failed-
bionic'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-bionic

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

Title:
  "ip a" command on a guest VM shows UNKNOWN status

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Trusty:
  Fix Released
Status in linux source package in Xenial:
  Fix Released
Status in linux source package in Artful:
  Fix Released
Status in linux source package in Bionic:
  Fix Released

Bug description:
  
  [Impact] 

  "ip a" command on a guest VM shows UNKNOWN status.

  [Test Case]

  * Environment : Running a guest VM with a virtio-net adaptor interface, 
running on DPDK.
  * Perform "ip a" inside the guest VM shows state "UNKNOWN" as follow example:

  2: eth0:  mtu 1500 qdisc pfifo_fast state 
UNKNOWN group default qlen 1000
  .

  [Regression Potential]

   * Regression is low, the patch fix the operstate logic for virtio when no 
VIRTIO_NET_F_STATUS.[1]
   * The patch has been first accepted in net-next, then move into Linus's git.

  [1] - VIRTIO_NET_F_STATUS
  Allow the host to inform us that the link is down by adding a 
VIRTIO_NET_F_STATUS which indicates that device status is available in 
virtio_net config.

  [Other Info]
   
   * Linus: 
https://github.com/torvalds/linux/commit/bda7fab54828bbef2164bb23c0f6b1a7d05cc718

   * Net-next:
  
https://git.kernel.org/pub/scm/linux/kernel/git/davem/net-next.git/commit/?id=bda7fab54828bbe
 

  [Original Description]
  It has been brought to our attention the following bug :

  
  Environment: The guest VM is using a canonical ubuntu image, and the eth0 is 
a virtio-net adaptor, running on DPDK.

  Background: "ip a" command relies on the operstate variable of the
  net_device structure maintained by the kernel. This is based on the
  operational state as defined in the IF MIB (RFC 2863). Device drivers
  are expected to update this member. But many older drivers don’t seem
  to be using this. So in general, IF_OPER_UP and IF_OPER_UNKNOWN are
  treated as equal, in some sense, to maintain backward compatibility.
  Even if we look at https://elixir.free-
  electrons.com/linux/v4.15-rc2/source/include/linux/netdevice.h#L3468,
  the function to check if interface is up, is written as follows, which
  says that OPER_UNKNOWN is not something to be alarmed about, and just
  reflective of a state that some drivers don’t care to update about.

  static inline bool netif_oper_up(const struct net_device *dev)
  {
  return (dev->operstate == IF_OPER_UP ||
  dev->operstate == IF_OPER_UNKNOWN /* backward compat */);
  }

  Code Ref:

  1. 
https://elixir.free-electrons.com/linux/v4.15-rc2/source/include/linux/netdevice.h#L1739
  2. 
https://elixir.free-electrons.com/linux/v4.15-rc2/source/include/linux/netdevice.h#L3468
  3. https://www.kernel.org/doc/Documentation/networking/operstates.txt

  Now, for traditional kernel mode network adapter drivers, this state is 
supposed to be manipulated by the driver. And we can safely assume that most 
current kernel model drivers do keep this updated.
  

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

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

[Kernel-packages] [Bug 1756094] Re: [Bionic][ARM64] PCI and SAS driver patches for hip08 SoCs

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
bionic' to 'verification-done-bionic'. If the problem still exists,
change the tag 'verification-needed-bionic' to 'verification-failed-
bionic'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-bionic

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

Title:
  [Bionic][ARM64] PCI and SAS driver patches for hip08 SoCs

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

Bug description:
  Following patches are required to boot and install Bionic on hip08 soc
  based server reference board.

  Bjorn Helgaas (4):
PCI/ASPM: Calculate LTR_L1.2_THRESHOLD from device characteristics
PCI/ASPM: Enable Latency Tolerance Reporting when supported
PCI/ASPM: Unexport internal ASPM interfaces
PCI: Make PCI_SCAN_ALL_PCIE_DEVS work for Root as well as Downstream 
Ports

  Keith Busch (2):
PCI/AER: Return error if AER is not supported
PCI/DPC: Enable DPC only if AER is available

  Rafael J. Wysocki (2):
PM / core: Add LEAVE_SUSPENDED driver flag
PCI / PM: Support for LEAVE_SUSPENDED driver flag

  Tyler Baicar (1):
PCI/AER: Skip recovery callbacks for correctable errors from ACPI APEI

  Wei Yongjun (1):
scsi: hisi_sas: make local symbol host_attrs static

  Xiang Chen (8):
scsi: hisi_sas: fix dma_unmap_sg() parameter
scsi: hisi_sas: modify hisi_sas_dev_gone() for reset
scsi: hisi_sas: change ncq process for v3 hw
scsi: hisi_sas: add some print to enhance debugging
scsi: hisi_sas: fix SAS_QUEUE_FULL problem while running IO
scsi: hisi_sas: re-add the lldd_port_deformed()
scsi: hisi_sas: add v3 hw suspend and resume
scsi: hisi_sas: fix a bug in hisi_sas_dev_gone()

  Xiaofei Tan (11):
scsi: hisi_sas: relocate clearing ITCT and freeing device
scsi: hisi_sas: optimise port id refresh function
scsi: hisi_sas: some optimizations of host controller reset
scsi: hisi_sas: add an mechanism to do reset work synchronously
scsi: hisi_sas: add RAS feature for v3 hw
scsi: hisi_sas: improve int_chnl_int_v2_hw() consistency with v3 hw
scsi: hisi_sas: add v2 hw port AXI error handling support
scsi: hisi_sas: use an general way to delay PHY work
scsi: hisi_sas: do link reset for some CHL_INT2 ints
scsi: hisi_sas: judge result of internal abort
scsi: hisi_sas: add internal abort dev in some places
  chenxiang (4):
scsi: ata: enhance the definition of SET MAX feature field value
scsi: hisi_sas: Change frame type for SET MAX commands
UBUNTU: SAUCE: scsi: hisi_sas: config for hip08 ES
UBUNTU: SAUCE: scsi: hisi_sas: export device table of v3 hw to userspace

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

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

[Kernel-packages] [Bug 1805248] Re: Regression: hinic performance degrades over time

This bug was erroneously marked for verification in bionic; verification
is not required and verification-needed-bionic is being removed.

** Tags removed: verification-needed-bionic

** Tags added: verification-done-bionic

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

Title:
  Regression: hinic performance degrades over time

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Cosmic:
  Fix Released
Status in linux source package in Disco:
  Fix Released

Bug description:
  [Impact]
  Bug 1800664 introduced checksum offload and TSO support for HiNIC adapters. 
While that did improve performance in short iperf runs, longer runs were later 
found to show a significant regression in performance:
    https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1800664/comments/3

  [Test Case]
  iperf -c 192.168.99.1 -P5

  [Fix]
  Revert the offending patch.

  [Regression Risk]
  This is reverting a patch, returning the driver to 18.10 GA behavior.

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

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

[Kernel-packages] [Bug 1790652] Re: Oracle cosmic image does not find broadcom network device in Shape VMStandard2.1

This bug was erroneously marked for verification in bionic; verification
is not required and verification-needed-bionic is being removed.

** Tags removed: verification-needed-bionic

** Tags added: verification-done-bionic

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

Title:
  Oracle cosmic image does not find broadcom network device in Shape
  VMStandard2.1

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

Bug description:
  I tried to register and boot a cosmic image to verify new changes in it and 
in cloud-init.
  The image failed to bring up networking in the initramfs, and thus failed to 
find iscsi root.
  this could be user error.

  Here is what I did to publish the image.

   - use oci build tool [1].
 following
 
https://docs.cloud.oracle.com/iaas/Content/Compute/Tasks/imageimportexport.htm#ImportinganImage
   - Download a livefs build from cloudware
 https://launchpad.net/~cloudware/+livefs/ubuntu/cosmic/cpc/
 example: livecd.ubuntu-cpc.oracle_bare_metal.img
 My image had version 20180821.1

   - oci os bucket create --name=smoser-devel
   - oci os object put \
--parallel-upload-count=4 \
--part-size=10 \
--bucket-name=smoser-devel \
--file=/tmp/livecd.ubuntu-cpc.oracle_bare_metal.img \
--name=cosmic-20180821.1.img

   - import the object
  $ oci compute image import from-object \
  --display-name=smoser-cosmic-20180821.1.img \
  --launch-mode=NATIVE \
  --namespace=intcanonical \
  --bucket-name=smoser-devel \
  --name=cosmic-20180821.1.img \
  --source-image-type=QCOW2

  Then I launched from the web UI a VM.Standard2.1.

  --
   https://docs.cloud.oracle.com/iaas/Content/API/Concepts/cliconcepts.htm

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

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

[Kernel-packages] [Bug 1620762] Re: Support AverMedia DVD EZMaker 7 USB video capture dongle

This bug was erroneously marked for verification in bionic; verification
is not required and verification-needed-bionic is being removed.

** Tags removed: verification-needed-bionic

** Tags added: verification-done-bionic

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

Title:
  Support AverMedia DVD EZMaker 7 USB video capture dongle

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

Bug description:
  Linux doesn't support this capture.
  Link to patch 
https://www.linuxtv.org/wiki/index.php/AVerMedia_DVD_EZMaker_7_(C039). 
  I tested it on Ubuntu 16.04 - OK.
  It will be great if this patch is built-in to kernel.

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

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

[Kernel-packages] [Bug 1751021] Re: retpoline abi files are empty on i386

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
bionic' to 'verification-done-bionic'. If the problem still exists,
change the tag 'verification-needed-bionic' to 'verification-failed-
bionic'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-bionic

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

Title:
  retpoline abi files are empty on i386

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

Bug description:
  The .retpoline files in the current abi are actually blank.
  This is due to incorrect handling in retpoline-extract.

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

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

[Kernel-packages] [Bug 1814647] Re: linux: 4.4.0-143.169 -proposed tracker

** Changed in: kernel-sru-workflow/snap-release-to-beta
   Status: Confirmed => Fix Released

** Changed in: kernel-sru-workflow/snap-release-to-edge
   Status: Confirmed => Fix Released

** Changed in: kernel-sru-workflow/snap-certification-testing
   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
  
  backports: bug 1814648 (linux-aws), bug 1814649 (linux-lts-xenial)
  derivatives: bug 1814651 (linux-aws), bug 1814652 (linux-euclid), bug 1814654 
(linux-kvm), bug 1814655 (linux-raspi2), bug 1814657 (linux-snapdragon)
  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
- phase: Promote to Proposed
- phase-changed: Monday, 11. February 2019 15:40 UTC
+ phase: Testing
+ phase-changed: Thursday, 14. February 2019 16:33 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Stalled -- testing FAILED
certification-testing: Ongoing -- testing in progress
regression-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
-   snap-release-to-beta: Pending -- snap not in beta channel
-   snap-release-to-edge: Pending -- snap not in edge channel
+   snap-certification-testing: Ongoing -- testing in progress
verification-testing: Ongoing -- testing 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/1814647

Title:
  linux: 4.4.0-143.169 -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 snap-certification-testing series:
  Confirmed
Status in Kernel SRU Workflow snap-release-to-beta series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-candidate series:
  New
Status in Kernel SRU Workflow snap-release-to-edge series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-stable series:
  New
Status in Kernel SRU Workflow upload-to-ppa-dnu series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Confirmed

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

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

  backports: bug 1814648 (linux-aws), bug 1814649 (linux-lts-xenial)
  derivatives: bug 1814651 (linux-aws), bug 1814652 (linux-euclid), bug 1814654 
(linux-kvm), bug 1814655 (linux-raspi2), bug 1814657 (linux-snapdragon)
  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
  phase: Testing
  phase-changed: Thursday, 14. February 2019 16:33 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Stalled -- testing FAILED
certification-testing: Ongoing -- testing in progress
regression-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
snap-certification-testing: Ongoing -- testing in progress
verification-testing: Ongoing -- testing in progress

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

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

[Kernel-packages] [Bug 1766052] Re: Incorrect blacklist of bcm2835_wdt

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
bionic' to 'verification-done-bionic'. If the problem still exists,
change the tag 'verification-needed-bionic' to 'verification-failed-
bionic'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-bionic

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

Title:
  Incorrect blacklist of bcm2835_wdt

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Artful:
  Won't Fix
Status in linux source package in Bionic:
  Fix Released

Bug description:
  Without bcm2835_wdt loaded, Raspberry Pi systems cannot reboot or shut
  down. This needs to be removed from the automatic blacklist generated
  by the kernel build that ends up in
  /lib/modprobe.d/blacklist_linux_$(uname -r).conf

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

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

[Kernel-packages] [Bug 1779640] Re: [Hyper-V] KVP daemon crashes at startup

Sorry for the delay. That might be a dependency problem on the KVP
systemd service. I will run some tests locally. Can you confirm if the
problem also happens with the linux-azure kernel?

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

Title:
  [Hyper-V] KVP daemon crashes at startup

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Bionic:
  Confirmed
Status in linux source package in Disco:
  Confirmed

Bug description:
  While testing Bionic daily build with kernel 4.15.0-20-generic we saw
  the following issue with the KVP daemon:

  KVP daemon crashes after approximatively 2 minutes of uptime and it enters in 
a failed state. The daemon can be manually started and it enters back in active 
(running) state.
  The error messages from /var/log/syslog after the daemon enters the failed 
state are the following:

  Apr 25 04:28:46 bionicDaily KVP: read failed; error:9 Bad file descriptor
  Apr 25 04:28:46 bionicDaily systemd[1]: hv-kvp-daemon.service: Main process 
exited, code=exited, status=1/FAILURE
  Apr 25 04:28:46 bionicDaily systemd[1]: hv-kvp-daemon.service: Failed with 
result 'exit-code'.
  Apr 25 04:28:59 bionicDaily systemd[1]: Started Hyper-V KVP Protocol Daemon.

  Note: There was a simmilar issue discussed on this thread
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1664663, but the
  fixing commit seems to be inclued in this Bionic build.

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

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

[Kernel-packages] [Bug 1759511] Re: Fix an issue that when system in S3, USB keyboard can't wake up the system.

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
bionic' to 'verification-done-bionic'. If the problem still exists,
change the tag 'verification-needed-bionic' to 'verification-failed-
bionic'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-bionic

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

Title:
  Fix an issue that when system in S3, USB keyboard can't wake up the
  system.

Status in HWE Next:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Invalid
Status in linux-oem source package in Xenial:
  Fix Released
Status in linux source package in Artful:
  Fix Released
Status in linux-oem source package in Artful:
  Invalid

Bug description:
  ===SRU Justification===
  [Impact]
  xHC stays at D0 when system is in S3. Unfortunately D0 can't generate PME# 
wakeup event, so USB device can't wake the system.

  [Test]
  Intel NUC can't be waken up by USB keyboard when the system is in S3.
  With the patch, USB keyboard can wake up the system.

  [Regression Potential]
  Low.
  The issue starts appearing from Gemini Lake, older generation hardware 
shouldn't get affected.

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

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

[Kernel-packages] [Bug 1783964] Re: Please make CONFIG_PWM_LPSS_PCI and CONFIG_PWM_LPSS_PLATFORM built in to make brightness adjustment working on various BayTrail/CherryTrail-based devices

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
bionic' to 'verification-done-bionic'. If the problem still exists,
change the tag 'verification-needed-bionic' to 'verification-failed-
bionic'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-bionic

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

Title:
  Please make CONFIG_PWM_LPSS_PCI and CONFIG_PWM_LPSS_PLATFORM built in
  to make brightness adjustment working on various BayTrail/CherryTrail-
  based devices

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

Bug description:
  Hello!

  Building kernel with following option should make brightness
  adjustment working on various Intel BayTrail and CherryTrail-based
  devices such as HP Stream 7 Tablet, Microsoft Surface 3, and quite a
  few tablets from ASUS, and many no-name Chinese companies.

  CONFIG_PWM_LPSS=y
  CONFIG_PWM_LPSS_PCI=y
  CONFIG_PWM_LPSS_PLATFORM=y

  I tested this change on HP Stream 7, by installing Linux 4.18rc6 from
  http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.18-rc6/ and then
  installing same kernel, but with built in CONFIG_PWM_LPSS modules
  listed above.

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

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

[Kernel-packages] [Bug 1759848] Re: Allow multiple mounts of zfs datasets