[Kernel-packages] [Bug 1802810] Re: SD card reader not working on Ubuntu 18.10

2019-05-31 Thread harrytonny
I have faced these common issues similar to https://errorcode0x.com/fix-
canon-printer-error-code-5b02/ that definitely sorted out by them. To
get an ultimate solution given by that will be helpful for them.

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

Title:
  SD card reader not working on Ubuntu 18.10

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  When I upgraded to Ubuntu 18.10 from Ubuntu 18.04, the SD card reader
  on my Macbook pro early 2015 13 inch stopped working. It won't show up
  when I do lspci. The SD card reader won't show up in gparted or gnome-
  disk-utility.

  My Kernel version is 4.18.0-10-generic

  Output of lspci

  00:00.0 Host bridge: Intel Corporation Broadwell-U Host Bridge -OPI (rev 09)
  00:02.0 VGA compatible controller: Intel Corporation Iris Graphics 6100 (rev 
09)
  00:03.0 Audio device: Intel Corporation Broadwell-U Audio Controller (rev 09)
  00:14.0 USB controller: Intel Corporation Wildcat Point-LP USB xHCI 
Controller (rev 03)
  00:15.0 DMA controller: Intel Corporation Wildcat Point-LP Serial IO DMA 
Controller (rev 03)
  00:15.4 Serial bus controller [0c80]: Intel Corporation Wildcat Point-LP 
Serial IO GSPI Controller #1 (rev 03)
  00:16.0 Communication controller: Intel Corporation Wildcat Point-LP MEI 
Controller #1 (rev 03)
  00:1b.0 Audio device: Intel Corporation Wildcat Point-LP High Definition 
Audio Controller (rev 03)
  00:1c.0 PCI bridge: Intel Corporation Wildcat Point-LP PCI Express Root Port 
#1 (rev e3)
  00:1c.1 PCI bridge: Intel Corporation Wildcat Point-LP PCI Express Root Port 
#2 (rev e3)
  00:1c.2 PCI bridge: Intel Corporation Wildcat Point-LP PCI Express Root Port 
#3 (rev e3)
  00:1c.4 PCI bridge: Intel Corporation Wildcat Point-LP PCI Express Root Port 
#5 (rev e3)
  00:1c.5 PCI bridge: Intel Corporation Wildcat Point-LP PCI Express Root Port 
#6 (rev e3)
  00:1f.0 ISA bridge: Intel Corporation Wildcat Point-LP LPC Controller (rev 03)
  00:1f.3 SMBus: Intel Corporation Wildcat Point-LP SMBus Controller (rev 03)
  00:1f.6 Signal processing controller: Intel Corporation Wildcat Point-LP 
Thermal Management Controller (rev 03)
  02:00.0 Multimedia controller: Broadcom Inc. and subsidiaries 720p FaceTime 
HD Camera
  03:00.0 Network controller: Broadcom Inc. and subsidiaries BCM43602 802.11ac 
Wireless LAN SoC (rev 01)
  04:00.0 SATA controller: Samsung Electronics Co Ltd Device a801 (rev 01)
  05:00.0 PCI bridge: Intel Corporation DSL5520 Thunderbolt 2 Bridge [Falcon 
Ridge 4C 2013]
  06:00.0 PCI bridge: Intel Corporation DSL5520 Thunderbolt 2 Bridge [Falcon 
Ridge 4C 2013]
  06:03.0 PCI bridge: Intel Corporation DSL5520 Thunderbolt 2 Bridge [Falcon 
Ridge 4C 2013]
  06:04.0 PCI bridge: Intel Corporation DSL5520 Thunderbolt 2 Bridge [Falcon 
Ridge 4C 2013]
  06:05.0 PCI bridge: Intel Corporation DSL5520 Thunderbolt 2 Bridge [Falcon 
Ridge 4C 2013]
  06:06.0 PCI bridge: Intel Corporation DSL5520 Thunderbolt 2 Bridge [Falcon 
Ridge 4C 2013]
  07:00.0 System peripheral: Intel Corporation DSL5520 Thunderbolt 2 NHI 
[Falcon Ridge 4C 2013]
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  monter 1583 F pulseaudio
   /dev/snd/controlC0:  monter 1583 F pulseaudio
  CurrentDesktop: Budgie:GNOME
  DistroRelease: Ubuntu 18.10
  InstallationDate: Installed on 2018-11-12 (0 days ago)
  InstallationMedia: Ubuntu-Budgie 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.2)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 05ac:0273 Apple, Inc. 
   Bus 001 Device 002: ID 05ac:8290 Apple, Inc. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Apple Inc. MacBookPro12,1
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-10-generic 
root=/dev/mapper/ubuntu--budgie--vg-root ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  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
  Tags:  cosmic
  Uname: Linux 4.18.0-10-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/17/2018
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: 180.0.0.0.0
  dmi.board.name: Mac-E43C1C25D4880AD6
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookPro12,1
  dmi.chassis.type: 9
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-E43C1C25D4880AD6
  dmi.modalias: 

[Kernel-packages] [Bug 1822665] Re: Brightness can't be changed from keyboard

2019-05-31 Thread Launchpad Bug Tracker
[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/1822665

Title:
  Brightness can't be changed from keyboard

Status in linux package in Ubuntu:
  Expired

Bug description:
  Brightness level can't be changed from keyboard with the Fn key and
  the corresponding designated key. Other functions like changing
  volumes involving the Fn key work perfectly. The only way I can change
  brightness is from the status bar.

  Current OS: Ubuntu 19.04 Disco Dingo (development branch)
  Package version: gnome-shell 3.32.0-1ubuntu1

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gnome-shell 3.32.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0
  Uname: Linux 5.0.0-7-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr  1 20:46:39 2019
  DisplayManager: gdm3
  InstallationDate: Installed on 2018-12-31 (91 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to disco on 2019-03-29 (3 days ago)

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

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


[Kernel-packages] [Bug 1831301] Re: sound doesn't works in both kernel. no one cards is recognize by system-

2019-05-31 Thread Tom Reynolds
OP had also tested this with linux-image-generic-hwe-18.04 / linux-
image-4.18.0-20-generic, where dmesg looked very similar to that of this
hwe-18.04-edge kernel.


Gabriele:

(1) Please do as discussed in comment 2.

(2) Please also re-run alsa-info as discussed at
https://wiki.ubuntu.com/Audio/AlsaInfo and attach the output as a file
to this bug report.

(3) These commands (3 lines total) would create an ALSA profile for your
hardware, and may provide audio after rebooting:

sudo mkdir -p /usr/share/alsa/ucm/bytcr-rt5651 && \
wget -qO- 
'https://git.alsa-project.org/?p=alsa-lib.git;a=blob_plain;f=src/conf/ucm/bytcr-rt5651/bytcr-rt5651.conf'
 | sudo tee /usr/share/alsa/ucm/bytcr-rt5651/bytcr-rt5651.conf >/dev/null && \
wget -qO- 
https://git.alsa-project.org/?p=alsa-lib.git;a=blob_plain;f=src/conf/ucm/bytcr-rt5651/HiFi.conf
 | sudo tee /usr/share/alsa/ucm/bytcr-rt5651/HiFi.conf >/dev/null

To undo these changes, please run this command:
sudo rm -r /usr/share/alsa/ucm/bytcr-rt5651

Please report back whether this helped. If so, please repeat (1) and
(2).

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

Title:
  sound doesn't works in both kernel. no one cards is recognize by
  system-

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  .

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base (not installed)
  ProcVersionSignature: Ubuntu 5.0.0-15.16~18.04.1-generic 5.0.6
  Uname: Linux 5.0.0-15-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  Date: Sat Jun  1 04:26:10 2019
  InstallationDate: Installed on 2019-04-03 (58 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.modprobe.d.alsa-base.conf: 2019-05-31T22:19:11.232515

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

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


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

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

apport-collect 1831301

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

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

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

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

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

Title:
  sound doesn't works in both kernel. no one cards is recognize by
  system-

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  .

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base (not installed)
  ProcVersionSignature: Ubuntu 5.0.0-15.16~18.04.1-generic 5.0.6
  Uname: Linux 5.0.0-15-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  Date: Sat Jun  1 04:26:10 2019
  InstallationDate: Installed on 2019-04-03 (58 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.modprobe.d.alsa-base.conf: 2019-05-31T22:19:11.232515

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

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


[Kernel-packages] [Bug 1831301] Re: sound doesn't works in both kernel. no one cards is recognize by system-

2019-05-31 Thread Tom Reynolds
Thank you for taking the time to report this bug and helping to make Ubuntu 
better. Please execute the following command only once, as it will 
automatically gather debugging information, in a terminal:
   apport-collect 1831301

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

Title:
  sound doesn't works in both kernel. no one cards is recognize by
  system-

Status in linux package in Ubuntu:
  New

Bug description:
  .

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base (not installed)
  ProcVersionSignature: Ubuntu 5.0.0-15.16~18.04.1-generic 5.0.6
  Uname: Linux 5.0.0-15-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  Date: Sat Jun  1 04:26:10 2019
  InstallationDate: Installed on 2019-04-03 (58 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.modprobe.d.alsa-base.conf: 2019-05-31T22:19:11.232515

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

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


[Kernel-packages] [Bug 1831301] Re: sound doesn't works in both kernel. no one cards is recognize by system-

2019-05-31 Thread Seth Arnold
** Package changed: alsa-driver (Ubuntu) => linux (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/1831301

Title:
  sound doesn't works in both kernel. no one cards is recognize by
  system-

Status in linux package in Ubuntu:
  New

Bug description:
  .

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base (not installed)
  ProcVersionSignature: Ubuntu 5.0.0-15.16~18.04.1-generic 5.0.6
  Uname: Linux 5.0.0-15-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  Date: Sat Jun  1 04:26:10 2019
  InstallationDate: Installed on 2019-04-03 (58 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.modprobe.d.alsa-base.conf: 2019-05-31T22:19:11.232515

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

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


[Kernel-packages] [Bug 1831301] [NEW] sound doesn't works in both kernel. no one cards is recognize by system-

2019-05-31 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: alsa-base (not installed)
ProcVersionSignature: Ubuntu 5.0.0-15.16~18.04.1-generic 5.0.6
Uname: Linux 5.0.0-15-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.6
Architecture: amd64
Date: Sat Jun  1 04:26:10 2019
InstallationDate: Installed on 2019-04-03 (58 days ago)
InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 LANG=it_IT.UTF-8
 SHELL=/bin/bash
SourcePackage: alsa-driver
UpgradeStatus: No upgrade log present (probably fresh install)
mtime.conffile..etc.modprobe.d.alsa-base.conf: 2019-05-31T22:19:11.232515

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


** Tags: amd64 apport-bug bionic
-- 
sound doesn't works in both kernel. no one cards is recognize by system-
https://bugs.launchpad.net/bugs/1831301
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to linux in Ubuntu.

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


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

2019-05-31 Thread bugproxy
--- Comment From s...@us.ibm.com 2019-05-31 18:35 EDT---
No response to repeated requests. Rejecting.

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

Title:
  ISST-LTE:pVM:roselp4:ubuntu16.04.2: number of numa_miss and
  numa_foreign wrong in numastat

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

Bug description:
  == Comment: #0 - Ping Tian Han  - 2016-12-07 19:14:40 ==
  +++ This bug was initially created as a clone of Bug #148750 +++

  On roselp4, we got numastat as this:

  % sudo numastat  
 node0   node1
  numa_hit   0   0
  numa_miss  0  292054
  numa_foreign   0  292054
  interleave_hit 04100
  local_node 0   0
  other_node 0   0
  % uname -a   
  Linux roselp4 4.8.0-30-generic #32~16.04.1-Ubuntu SMP Fri Dec 2 03:43:52 UTC 
2016 ppc64le ppc64le ppc64le GNU/Linux
  % 

  
  The number of numa_miss and numa_foreign looks wrong, because the manual says 
that "Each numa_miss has a numa_foreign on another node." and "Each 
numa_foreign has a numa_miss on another node." But the numbers of node0 are all 
zeros.

  
  == Comment: #18 - JIA HE  - 2017-02-20 00:24:26 ==
  hi, Ping Tian Han
  Please see the test result, is it what you expected?
  before the patches
  root@seedlp1:~# numastat
 node0   node2   node3
  numa_hit   0   0   0
  numa_miss  0  3525215466
  numa_foreign   0  3525215466
  interleave_hit 056285402
  local_node 0   0   0
  other_node 0   0   0
  root@seedlp1:~# 

  after the patches
  xinhui locking
  root@seedlp1:/boot# numastat
 node0   node2   node3
  numa_hit   0  2387664837
  numa_miss  0   0   0
  numa_foreign   0   0   0
  interleave_hit 048884777
  local_node 0   0   0
  other_node 0  2387664837

  == Comment: #19 - JIA HE  - 2017-02-20 00:28:14 ==
  New kernel is at 
http://kernel.stglabs.ibm.com/~hejianet/bug149763/linux-image-4.8.0-37-generic_4.8.0-37.39_ppc64el.deb

  md5: f3a57af05f0945f10b9d2841844f0fe4  linux-
  image-4.8.0-37-generic_4.8.0-37.39bug149763_ppc64el.deb

  == Comment: #20 - Ping Tian Han  - 2017-02-20 00:57:30 ==
  (In reply to comment #18)
  > hi, Ping Tian Han
  > Please see the test result, is it what you expected?
  > before the patches
  > root@seedlp1:~# numastat
  >node0   node2   node3
  > numa_hit   0   0   0
  > numa_miss  0  3525215466
  > numa_foreign   0  3525215466
  > interleave_hit 056285402
  > local_node 0   0   0
  > other_node 0   0   0
  > root@seedlp1:~# 
  > 
  > after the patches
  > xinhui locking
  > root@seedlp1:/boot# numastat
  >node0   node2   node3
  > numa_hit   0  2387664837
  > numa_miss  0   0   0
  > numa_foreign   0   0   0
  > interleave_hit 048884777
  > local_node 0   0   0
  > other_node 0  2387664837

  This looks good to me. Thanks.

  Please cherry pick the  patches below

  
  
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=2df26639e708a88dcc22171949da638a9998f3bc

  
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=41b6167e8f746b475668f1da78599fc4284f18db

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

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


[Kernel-packages] [Bug 1817321] Re: installer does not support iSCSI iBFT

2019-05-31 Thread Dan Streetman
** Tags added: sts-sponsor-ddstreet

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

Title:
  installer does not support iSCSI iBFT

Status in debian-installer package in Ubuntu:
  Fix Released
Status in hw-detect package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in partman-iscsi package in Ubuntu:
  Fix Released
Status in debian-installer source package in Bionic:
  Confirmed
Status in hw-detect source package in Bionic:
  Confirmed
Status in linux source package in Bionic:
  Fix Released
Status in partman-iscsi source package in Bionic:
  Confirmed
Status in debian-installer source package in Cosmic:
  Confirmed
Status in hw-detect source package in Cosmic:
  Confirmed
Status in linux source package in Cosmic:
  Fix Released
Status in partman-iscsi source package in Cosmic:
  Confirmed
Status in debian-installer source package in Disco:
  Confirmed
Status in hw-detect source package in Disco:
  Confirmed
Status in linux source package in Disco:
  Fix Released
Status in partman-iscsi source package in Disco:
  Confirmed
Status in debian-installer source package in Eoan:
  Fix Released
Status in hw-detect source package in Eoan:
  Fix Released
Status in linux source package in Eoan:
  Fix Released
Status in partman-iscsi source package in Eoan:
  Fix Released

Bug description:
  [Impact]

   * It's not possible to access iBFT (iSCSI Boot Firmware Table) information
     (settings for network interface, initiator, and target) in the installer
     because the 'iscsi_ibft' module is not present in udeb packages.

   * Even if it was, the installer does not handle iBFT information at all,
     thus any settings are ignored, and iSCSI-related configuration has to
     be done manually or with workarounds.

   * This impacts user-experience and automatic installation on systems and
     deployments which actually do provide the iBFT feature and information,
     but cannot use it practically.

   * With proper iBFT support in the installer (kernel module in udeb package
     and automatic iSCSI-related configuration) users will be able to rely on
     iBFT to install/deploy Ubuntu on their servers and datacenters.

   * These fixes add the 'iscsi_ibft' kernel module in the scsi-modules udeb,
     and configure network/iSCSI according to iBFT information in disk-detect.

     This is done in disk-detect so that the iSCSI LUNs are detected as disks
     (useful in case of no other disks in the system so the installer doesn't
     complain nor wait too long) and that any partman-related preseed options
     are not required and may be still available for the user.

  [Test Case]

   * linux package / kernel module in udeb:

     $ dpkg-deb -c scsi-modules_*.udeb | grep iscsi_ibft.ko

     Check the module loads in the installer environment.
     See comment with example for disco.

   * d-i/hw-detect/partman-iscsi package:
     See comments 11, 12, 13.

  [Regression Potential]

   * linux package: low, the kernel module is not loaded by default,
     and only checks whether iBFT information is present in firmware,
     then exposes that in sysfs in read-only mode.

   * d-i/hw-detect/partman-iscsi:
     - d-i: kernel version update to include iscsi_ibft module,
    based on kernel released to -updates plus one week
    monitoring bug reports -- it should be OK.
    Tested on amd64/i386/arm64/ppc64el on QEMU, plus amd64
    on baremetal -- see comment 11.
     - hw-detect: low, the changes are enabled by a preseed option.
  see comment 12.
     - partman-iscsi: low, simple changes, plus one fix that has
  been tested in detail, and falls back to
  previous behavior if it fails.
  see comment 13.

  [Other Info]

   * This has been verified both by the developer with a simple iSCSI
     iBFT environment (2 VMs: iSCSI target & initiator with UEFI+iPXE)
     and by an user with system/firmware that supports iBFT for iSCSI.

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

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


[Kernel-packages] [Bug 1826461] Re: Suspend fails on Ubuntu 18.04 when mobile network connected and no WiFi connection.

2019-05-31 Thread Jan
** Package changed: linux (Ubuntu) => modem-manager-gui (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/1826461

Title:
  Suspend fails on Ubuntu 18.04 when mobile network connected and no
  WiFi connection.

Status in modem-manager-gui package in Ubuntu:
  Confirmed

Bug description:
  Suspend fails on Ubuntu 18.04 when mobile network connected and no
  WiFi connection.

  Ubuntu 18.04, Thinkpad X240, Sierra modem
  Reproduced on 4.15 and 4.18 kernel. 
  The bug is triggered only when there is no WiFi connection. After waking 
laptop from suspend ModemManager stops working and after that I cannot suspend 
anymore. When it happens mmcli -L gives:

  Found 1 modems:
  /org/freedesktop/ModemManager1/Modem/9 [Sierra] MBIM [1199:A001]

  And mmcli -m 9:

Status   |   lock: 'none'
 | unlock retries: 'sim-pin (3)'
 |  state: 'registered'
 |power state: 'on'
 |access tech: 'gprs, lte'
 | signal quality: '0' (cached)

  After a few attempts to restart ModemManager and suspend it starts
  working. But only for one suspend. After one suspend I need to do the
  whole procedure again.

  Similar to:
  
https://askubuntu.com/questions/1084698/ubuntu-18-04-em7455-works-only-after-suspend
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1774950?comments=all
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1801743

  On Ubuntu 16.04 suspend and ModemManager used to work flawlessly.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jan2384 F pulseaudio
   /dev/snd/controlC1:  jan2384 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=2e1ab569-7004-4df3-b9f0-445fd74a1998
  InstallationDate: Installed on 2016-10-22 (915 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: LENOVO 20ALA0ARHH
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pl_PL.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-18-generic 
root=UUID=88a770a0-dfd0-42f5-91bb-960353d1f1f6 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.18.0-18.19~18.04.1-generic 4.18.20
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-18-generic N/A
   linux-backports-modules-4.18.0-18-generic  N/A
   linux-firmware 1.173.5
  Tags:  bionic
  Uname: Linux 4.18.0-18-generic x86_64
  UpgradeStatus: Upgraded to bionic on 2018-08-14 (254 days ago)
  UserGroups: adm audio cdrom dip input lp lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/20/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GIET94WW (2.44 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20ALA0ARHH
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 PRO
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrGIET94WW(2.44):bd09/20/2018:svnLENOVO:pn20ALA0ARHH:pvrThinkPadX240:rvnLENOVO:rn20ALA0ARHH:rvrSDK0E50510PRO:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad X240
  dmi.product.name: 20ALA0ARHH
  dmi.product.sku: LENOVO_MT_20AL_BU_Think_FM_ThinkPad X240
  dmi.product.version: ThinkPad X240
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/modem-manager-gui/+bug/1826461/+subscriptions

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


[Kernel-packages] [Bug 1798961] Re: Random unrecoverable freezes on Ubuntu 18.10

2019-05-31 Thread Warren
Sorry I thought this was a thread about Brave Browser and freezing, not
just Ubuntu in general.  Well touch wood I only get freezes with Braze
meaning I'll have to ditch Brave Browser.

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

Title:
  Random unrecoverable freezes on Ubuntu 18.10

Status in Linux:
  New
Status in linux package in Ubuntu:
  Triaged
Status in xserver-xorg-video-intel package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Triaged
Status in xserver-xorg-video-intel source package in Bionic:
  Invalid
Status in linux source package in Cosmic:
  Triaged
Status in xserver-xorg-video-intel source package in Cosmic:
  Invalid
Status in linux source package in Disco:
  Triaged
Status in xserver-xorg-video-intel source package in Disco:
  Invalid

Bug description:
  First thing I notice is that the mouse cursor freezes as I'm using it,
  then I hit the CAPS LOCK key and the LED indicator doesn't respond.
  Then I try the "REISUB" command, but it doesn't do anything either.
  Only a hard reset works, pressing down the power button for a few
  seconds.

  How to reproduce?
  I couldn't figure out a consistent method. It is still random to me.

  Version: Ubuntu 4.18.0-10.11-generic 4.18.12
  System information attached.

  Also happens under Arch Linux and Fedora.
  I've talked to another user on IRC who seems to be having the same freezes.

  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
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  dsilva 1213 F pulseaudio
   /dev/snd/controlC0:  dsilva 1213 F pulseaudio
  CurrentDesktop: XFCE
  Date: Sat Oct 20 09:54:50 2018
  InstallationDate: Installed on 2018-10-20 (0 days ago)
  InstallationMedia: Xubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.2)
  MachineType: Dell Inc. Inspiron 5458
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-10-generic 
root=/dev/mapper/xubuntu--vg-root 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:
   0: phy0: Wireless LAN
    Soft blocked: no
    Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/02/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A15
  dmi.board.name: 09WGNT
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA15:bd02/02/2018:svnDellInc.:pnInspiron5458:pvr01:rvnDellInc.:rn09WGNT:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Inspiron 5458
  dmi.product.sku: Inspiron 5458
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

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

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


[Kernel-packages] [Bug 1798961] Re: Random unrecoverable freezes on Ubuntu 18.10

2019-05-31 Thread Warren
Hi All.

I am getting system freezes on a dual boot base unit with Ryzen 1700 and
a R9 380 graphics card.  I'm running Kubuntu 19.04.  The whole system
locks up and I have to hard power down with the power button.  This is
happening at least once a day.  I don't think its worth trying fixes #43
and #58 because this is not a laptop and my graphics card is not Intel.

This is annoying as I have just migrated over to Brave but now I have
gone back to FF (if this doesn't get fixed) for good.

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

Title:
  Random unrecoverable freezes on Ubuntu 18.10

Status in Linux:
  New
Status in linux package in Ubuntu:
  Triaged
Status in xserver-xorg-video-intel package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Triaged
Status in xserver-xorg-video-intel source package in Bionic:
  Invalid
Status in linux source package in Cosmic:
  Triaged
Status in xserver-xorg-video-intel source package in Cosmic:
  Invalid
Status in linux source package in Disco:
  Triaged
Status in xserver-xorg-video-intel source package in Disco:
  Invalid

Bug description:
  First thing I notice is that the mouse cursor freezes as I'm using it,
  then I hit the CAPS LOCK key and the LED indicator doesn't respond.
  Then I try the "REISUB" command, but it doesn't do anything either.
  Only a hard reset works, pressing down the power button for a few
  seconds.

  How to reproduce?
  I couldn't figure out a consistent method. It is still random to me.

  Version: Ubuntu 4.18.0-10.11-generic 4.18.12
  System information attached.

  Also happens under Arch Linux and Fedora.
  I've talked to another user on IRC who seems to be having the same freezes.

  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
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  dsilva 1213 F pulseaudio
   /dev/snd/controlC0:  dsilva 1213 F pulseaudio
  CurrentDesktop: XFCE
  Date: Sat Oct 20 09:54:50 2018
  InstallationDate: Installed on 2018-10-20 (0 days ago)
  InstallationMedia: Xubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.2)
  MachineType: Dell Inc. Inspiron 5458
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-10-generic 
root=/dev/mapper/xubuntu--vg-root 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:
   0: phy0: Wireless LAN
    Soft blocked: no
    Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/02/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A15
  dmi.board.name: 09WGNT
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA15:bd02/02/2018:svnDellInc.:pnInspiron5458:pvr01:rvnDellInc.:rn09WGNT:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Inspiron 5458
  dmi.product.sku: Inspiron 5458
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

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

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


[Kernel-packages] [Bug 1814373] Re: storage / luks / dmsetup regressed (or got better) on ppc64le

2019-05-31 Thread Bug Watch Updater
** Changed in: systemd (Debian)
   Status: Unknown => New

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

Title:
  storage / luks / dmsetup regressed (or got better) on ppc64le

Status in linux package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Fix Committed
Status in udisks2 package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  New
Status in systemd source package in Bionic:
  Fix Committed
Status in udisks2 source package in Bionic:
  Invalid
Status in linux source package in Cosmic:
  New
Status in systemd source package in Cosmic:
  Fix Committed
Status in udisks2 source package in Cosmic:
  Invalid
Status in linux source package in Disco:
  New
Status in systemd source package in Disco:
  Fix Committed
Status in udisks2 source package in Disco:
  Invalid
Status in linux source package in Eoan:
  Confirmed
Status in systemd source package in Eoan:
  Fix Committed
Status in udisks2 source package in Eoan:
  Invalid
Status in systemd package in Debian:
  New

Bug description:
  in disco proposed with new systemd and v4.19 kernel it appears that
  dmsetup / cryptsetup storage either got better or worse.

  Devices take very long to activate, and sometimes remain in use during
  test clean up.

  This leads to udisks autopkgtest failing on ppc64le and systemd's
  "storage" autopkgtest is also failing.

  I've tried to make ppc64le test more resilient, but it's still odd
  that it became unstable in disco, and used to be rock solid on
  ppc64le.

  --
  sru template for systemd upload:

  [impact]
  buffer overflow can cause memory corruption; this is seen in failed 
autopkgtests

  [test case]
  see comment 6

  [regression potential]
  the patch is minimal and clearly correct; however the regression potential is 
around invalid/corrupted keys read from the keyring.

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

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


[Kernel-packages] [Bug 1830941] Re: linux: 4.4.0-150.176 -proposed tracker

2019-05-31 Thread Steve Beattie
** Changed in: kernel-sru-workflow/security-signoff
   Status: In Progress => Fix Released

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

Title:
  linux: 4.4.0-150.176 -proposed tracker

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

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

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

  backports: bug 1829205 (trusty/linux-aws), bug 1830947 
(trusty/linux-lts-xenial)
  derivatives: bug 1829193 (linux-aws), bug 1829195 (linux-kvm), bug 1829198 
(linux-raspi2), bug 1829201 (linux-snapdragon), bug 1829203 (linux-fips)

  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
  phase: Signoff
  phase-changed: Friday, 31. May 2019 13:31 UTC
  reason:
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/1830941/+subscriptions

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


[Kernel-packages] [Bug 1830941] Re: linux: 4.4.0-150.176 -proposed tracker

2019-05-31 Thread Ubuntu Kernel Bot
** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  backports: bug 1829205 (trusty/linux-aws), bug 1830947 
(trusty/linux-lts-xenial)
  derivatives: bug 1829193 (linux-aws), bug 1829195 (linux-kvm), bug 1829198 
(linux-raspi2), bug 1829201 (linux-snapdragon), bug 1829203 (linux-fips)
  
  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
- phase: Signoff
- phase-changed: Friday, 31. May 2019 13:31 UTC
+ phase: Ready for Testing
+ phase-changed: Friday, 31. May 2019 20:32 UTC
  reason:
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

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

Title:
  linux: 4.4.0-150.176 -proposed tracker

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

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

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

  backports: bug 1829205 (trusty/linux-aws), bug 1830947 
(trusty/linux-lts-xenial)
  derivatives: bug 1829193 (linux-aws), bug 1829195 (linux-kvm), bug 1829198 
(linux-raspi2), bug 1829201 (linux-snapdragon), bug 1829203 (linux-fips)

  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
  phase: Ready for Testing
  phase-changed: Friday, 31. May 2019 20:32 UTC
  reason:
regression-testing: Ongoing -- testing in progress
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/1830941/+subscriptions

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


[Kernel-packages] [Bug 1811723] Re: Samba client freeze during write when using higher than vers=1.0

2019-05-31 Thread zorlax
I have tried the 4.18 kernel (see comment 3) and while it seems to fix
this samba issue it was no good for my system, unless I of course
installed it wrong.  Is there a definitive guide on how to install and
choose different kernels for 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/1811723

Title:
  Samba client freeze during write when using higher than vers=1.0

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hello,
   My issue is that whenever I try to write new files (copy or move) to my file 
server something in the samba client freezes and I can't do anything samba 
until the system is rebooted. 

  To get write access I mount with uid ie "sudo mount //server/share
  /mountpoint -o user=write,uid=1000". Using this command the server and
  client negotiates smb protocol version 3.02.

  When this happens the server is still happily serving files to other machines.
  If I just read files everything works fine.
  If I connect from a windows client there is no issue.
  If I add "vers=1.0" everything works but transfers are really slow. 
Specifying version 3 produces a fail.
  Trying the same operation (different hw) with Mint 18 Mate produces the same 
fault.
  Trying the same operation (with "vers=3.0" set) using SuSE Leap 15.0 KDE live 
everything works as expected.

  Both client and server are running fully updated, as of posting,
  bionic.

  Using 'dmesg -w' too see what's going on I can see that there is a
  general protection fault somehow related to cifsd. I am however unable
  to tell if it is relevant to my issue, from kern.log:

  Jan  9 21:03:49 ubnu kernel: [  410.357213] general protection fault:  
[#1] SMP PTI
  Jan  9 21:03:49 ubnu kernel: [  410.357224] Modules linked in: cmac arc4 md4 
nls_utf8 cifs ccm fscache rfcomm pci_stub vboxpci(OE) vboxnetadp(OE) 
vboxnetflt(OE) vboxdrv(OE) thunderbolt bnep binfmt_misc nls_iso8859_1 
snd_hda_codec_hdmi snd_soc_skl snd_soc_skl_ipc snd_hda_ext_core snd_soc_sst_dsp 
snd_soc_sst_ipc snd_hda_codec_realtek snd_soc_acpi snd_hda_codec_generic 
snd_soc_core snd_compress ac97_bus snd_pcm_dmaengine snd_hda_intel intel_rapl 
btusb x86_pkg_temp_thermal intel_powerclamp btrtl coretemp joydev btbcm 
snd_hda_codec kvm_intel input_leds kvm irqbypass btintel crct10dif_pclmul 
crc32_pclmul snd_hda_core ghash_clmulni_intel pcbc snd_hwdep snd_pcm bluetooth 
ecdh_generic snd_seq_midi snd_seq_midi_event aesni_intel snd_rawmidi aes_x86_64 
crypto_simd glue_helper cryptd intel_cstate intel_rapl_perf snd_seq rtsx_pci_ms 
snd_seq_device
  Jan  9 21:03:49 ubnu kernel: [  410.357357]  wmi_bmof snd_timer memstick 
intel_wmi_thunderbolt snd shpchp soundcore mei_me mei intel_pch_thermal 
acpi_pad mac_hid sch_fq_codel parport_pc ppdev lp parport ip_tables x_tables 
autofs4 xfs libcrc32c hid_generic usbhid hid rtsx_pci_sdmmc i915 e1000e 
i2c_algo_bit drm_kms_helper ptp syscopyarea pps_core i2c_i801 sysfillrect 
sysimgblt rtsx_pci fb_sys_fops drm ahci libahci wmi video
  Jan  9 21:03:49 ubnu kernel: [  410.357447] CPU: 2 PID: 1822 Comm: cifsd 
Tainted: G   OE4.15.0-43-generic #46-Ubuntu
  Jan  9 21:03:49 ubnu kernel: [  410.357453] Hardware name:  /NUC7i3BNB, BIOS 
BNKBL357.86A.0069.2018.0920.1250 09/20/2018
  Jan  9 21:03:49 ubnu kernel: [  410.357468] RIP: 
0010:prefetch_freepointer+0x15/0x30
  Jan  9 21:03:49 ubnu kernel: [  410.357474] RSP: 0018:b16201ae3da0 
EFLAGS: 00010282
  Jan  9 21:03:49 ubnu kernel: [  410.357482] RAX:  RBX: 
e90527c744fff71a RCX: 3ea9
  Jan  9 21:03:49 ubnu kernel: [  410.357488] RDX: 3ea8 RSI: 
e90527c744fff71a RDI: 9d7079255080
  Jan  9 21:03:49 ubnu kernel: [  410.357494] RBP: b16201ae3da0 R08: 
9d707ed2b650 R09: b16201ae3db0
  Jan  9 21:03:49 ubnu kernel: [  410.357499] R10: b16201ae3de8 R11: 
 R12: 01011200
  Jan  9 21:03:49 ubnu kernel: [  410.357505] R13: 9d7079255080 R14: 
9d7016478c40 R15: 9d7079255080
  Jan  9 21:03:49 ubnu kernel: [  410.357512] FS:  () 
GS:9d707ed0() knlGS:
  Jan  9 21:03:49 ubnu kernel: [  410.357519] CS:  0010 DS:  ES:  CR0: 
80050033
  Jan  9 21:03:49 ubnu kernel: [  410.357525] CR2: 7f0a2802d028 CR3: 
3760a006 CR4: 003606e0
  Jan  9 21:03:49 ubnu kernel: [  410.357530] Call Trace:
  Jan  9 21:03:49 ubnu kernel: [  410.357545]  kmem_cache_alloc+0xa2/0x1b0
  Jan  9 21:03:49 ubnu kernel: [  410.357558]  ? mempool_alloc_slab+0x15/0x20
  Jan  9 21:03:49 ubnu kernel: [  410.357570]  ? wait_woken+0x80/0x80
  Jan  9 21:03:49 ubnu kernel: [  410.357580]  mempool_alloc_slab+0x15/0x20
  Jan  9 21:03:49 ubnu kernel: [  410.357590]  mempool_alloc+0x71/0x190
  Jan  9 21:03:49 ubnu kernel: [  410.357660]  ? smb2_add_credits+0xb0/0x250 
[cifs]
  Jan  9 21:03:49 ubnu kernel: [  410.357709]  

[Kernel-packages] [Bug 1830905] Re: Nvidia RTX 2060 USB bus timeouts cause ~30s delay in boot

2019-05-31 Thread Dan Watkins
I will do, thank you!  Can you direct me towards the appropriate Nvidia
forum to use?  And is there any way I could configure my system to
perform that blacklisting in the meantime?


Thanks again!

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

Title:
  Nvidia RTX 2060 USB bus timeouts cause ~30s delay in boot

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  From dmesg:

  [0.132667] kernel: pci :07:00.1: Linked as a consumer to :07:00.0
  [5.882727] kernel: pci :07:00.2: xHCI HW not ready after 5 sec (HC 
bug?) status = 0x801
  [5.882781] kernel: pci :07:00.2: quirk_usb_early_handoff+0x0/0x6a6 
took 5615333 usecs

  

  [9.984204] kernel: usb 1-7: new full-speed USB device number 4 using 
xhci_hcd
  [   10.308689] kernel: usb 1-7: New USB device found, idVendor=8087, 
idProduct=0a2b, bcdDevice= 0.10
  [   10.308690] kernel: usb 1-7: New USB device strings: Mfr=0, Product=0, 
SerialNumber=0
  [   34.654721] kernel: xhci_hcd :07:00.2: can't setup: -110
  [   34.654730] kernel: xhci_hcd :07:00.2: USB bus 3 deregistered
  [   34.654769] kernel: xhci_hcd :07:00.2: init :07:00.2 fail, -110
  [   34.654771] kernel: xhci_hcd: probe of :07:00.2 failed with error -110

  $ lspci -k -s :07:00
  07:00.0 VGA compatible controller: NVIDIA Corporation TU106 [GeForce RTX 2060 
Rev. A] (rev a1)
Subsystem: Gigabyte Technology Co., Ltd TU106
Kernel driver in use: nvidia
Kernel modules: nvidiafb, nouveau, nvidia_drm, nvidia
  07:00.1 Audio device: NVIDIA Corporation TU106 High Definition Audio 
Controller (rev a1)
Subsystem: Gigabyte Technology Co., Ltd TU106 High Definition Audio 
Controller
Kernel driver in use: snd_hda_intel
Kernel modules: snd_hda_intel
  07:00.2 USB controller: NVIDIA Corporation TU106 USB 3.1 Host Controller (rev 
a1)
Subsystem: Gigabyte Technology Co., Ltd TU106 USB 3.1 Host Controller
  07:00.3 Serial bus controller [0c80]: NVIDIA Corporation TU106 USB Type-C 
Port Policy Controller (rev a1)
Subsystem: Gigabyte Technology Co., Ltd TU106 USB Type-C Port Policy 
Controller
Kernel driver in use: nvidia-gpu
Kernel modules: i2c_nvidia_gpu

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: linux-image-5.0.0-15-generic 5.0.0-15.16
  ProcVersionSignature: Ubuntu 5.0.0-15.16-generic 5.0.6
  Uname: Linux 5.0.0-15-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  daniel 4470 F pulseaudio
   /dev/snd/controlC1:  daniel 4470 F pulseaudio
   /dev/snd/controlC2:  daniel 4470 F pulseaudio
  CurrentDesktop: i3
  Date: Wed May 29 09:36:51 2019
  InstallationDate: Installed on 2019-05-07 (21 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  MachineType: Gigabyte Technology Co., Ltd. B450M DS3H
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-15-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash 
resume=UUID=73909634-a75d-42c9-8f66-a69138690756 vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-15-generic N/A
   linux-backports-modules-5.0.0-15-generic  N/A
   linux-firmware1.179
  SourcePackage: linux
  UpgradeStatus: Upgraded to eoan on 2019-05-08 (20 days ago)
  dmi.bios.date: 01/25/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F4
  dmi.board.asset.tag: Default string
  dmi.board.name: B450M DS3H-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF4:bd01/25/2019:svnGigabyteTechnologyCo.,Ltd.:pnB450MDS3H:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB450MDS3H-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: B450M DS3H
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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


[Kernel-packages] [Bug 1829620] Re: intel-microcode on ASUS makes kernel stuck during loading initramfs on bionic-updates, bionic-security

2019-05-31 Thread aditya lele
Hi,

I think the discussions already confirm this. Just wanted to reiterate:
I have ASUS-FX533FD Zenbook laptop with i7-8565U CPU. I also faced the
same problem as mentioned in the bug description. I can confirm that it
was fixed with "WORKAROUND 2: downgrade (and hold) intel-microcode to
older version from bionic/main".

Thanks for your help.

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

Title:
  intel-microcode on ASUS makes kernel stuck during loading initramfs on
  bionic-updates, bionic-security

Status in intel-microcode package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in linux-hwe package in Ubuntu:
  Confirmed
Status in linux-hwe-edge package in Ubuntu:
  Confirmed

Bug description:
  Description:
  - my system gets stuck at "Booting, Loading initramfs" (the first 2 lines of 
booting, after grub)
  - does not even show the enter cryptsetup passphrase
  - affected kernels:
  # apt list --installed |grep linux-signed
  WARNING: apt does not have a stable CLI interface. Use with caution in 
scripts.
  linux-signed-generic/bionic-security,bionic-updates,now 4.15.0.50.52 amd64 
[installed]
  linux-signed-generic-hwe-18.04/bionic-security,bionic-updates,now 
4.18.0.20.70 amd64 [installed]
  linux-signed-generic-hwe-18.04-edge/bionic-security,bionic-updates,now 
5.0.0.15.71 amd64 [installed]

  - the setup is not new, has been working perfectly before (about 7
  days since my last restart?)

  System:
  - HW: ASUS Zenbook 14 UX433FN
  - Ubuntu 18.04, runing latest HWE, fully updated
  - grub(-pc), cryptsetup (crypttab entries for custom encrypted LUKS setup),

  Suspected/possible cause?:
  - recent intel-microcode package update
  - recent kernel package updates

  Steps taken:
  - tried to remove "splash quiet" from grub/kernel cmd line (also tried adding 
nosplash, noplymouth)
  - completely removed nvidia drivers (apt purge *nvidia*)
  - completely purged and reinstalled grub (grup-pc)
  - completely purged and reinstalled all kernels (headers, modules, image, ..)
  - toggle BIOS "fastboot" (now using OFF)
  - toggle UEFI SecureBoot (now using ON)
  - remove plymouth (apt remove *plymouth* , but the workaround is working with 
plymouth installed)

  Workaround:
  - so far, I'm only able to boot with non-Ubuntu kernel! 
(linux-image-liquorix-amd64)
  - which needs "splash" option ON
  - reinstall cryptsetup & update-grub (as suggested in 
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1829620/comments/10 )

  I am not sure how to get you more debug info, as this setup has been
  working before, and it's a very eary boot-process bug, so I can't even
  access dmesg etc.

  EDIT:

  Hypothesis:
  Only affects ASUS with i7-8565U Whiskey Lake Intel CPU

  Upstream Bug Report:
  https://github.com/intel/Intel-Linux-Processor-Microcode-Data-Files/issues/1

  WORKAROUND 1: disable intel microcode updates during boot
  From this bug: 
https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1759920
  1/ add the boot parameter: dis_ucode_ldr to /etc/default/grub
  2/ update-grub

  WORKAROUND 2: downgrade (and hold) intel-microcode to older version from 
bionic/main
  apt install --reinstall intel-microcode=3.20180312.0~ubuntu18.04.1

  ---
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CurrentDesktop: KDE
  DistroRelease: KDE neon 18.04
  InstallationDate: Installed on 2012-12-23 (2337 days ago)
  InstallationMedia: Kubuntu 12.10 "Quantal Quetzal" - Release amd64 
(20121017.1)
  Package: linux-hwe-edge (not installed)
  Tags:  bionic wayland-session
  Uname: Linux 5.0.0-17.1-liquorix-amd64 x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm libvirtd lpadmin netdev plugdev sudo vboxusers video
  _MarkForUpload: True
  ---
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CurrentDesktop: KDE
  DistroRelease: KDE neon 18.04
  InstallationDate: Installed on 2012-12-23 (2339 days ago)
  InstallationMedia: Kubuntu 12.10 "Quantal Quetzal" - Release amd64 
(20121017.1)
  Package: linux-hwe-edge
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.0.0-15.16~18.04.1-generic 5.0.6
  Tags: third-party-packages bionic wayland-session
  Uname: Linux 5.0.0-15-generic x86_64
  UnreportableReason: Toto není oficiální KDE balík. Prosíme odstraňte všechny 
balíky třetích stran a zkuste to znovu.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm libvirtd lpadmin netdev plugdev sudo video
  _MarkForUpload: True

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

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

[Kernel-packages] [Bug 1830905] Re: Nvidia RTX 2060 USB bus timeouts cause ~30s delay in boot

2019-05-31 Thread Kai-Heng Feng
We can add Gigabyte subsystem id to blacklist so xhci_pci and
i2c_nvidia_gpu won't load for those PCI functions. But before doing
that, please raise the issue to Nvidia forum, they may have better
solution.

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

Title:
  Nvidia RTX 2060 USB bus timeouts cause ~30s delay in boot

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  From dmesg:

  [0.132667] kernel: pci :07:00.1: Linked as a consumer to :07:00.0
  [5.882727] kernel: pci :07:00.2: xHCI HW not ready after 5 sec (HC 
bug?) status = 0x801
  [5.882781] kernel: pci :07:00.2: quirk_usb_early_handoff+0x0/0x6a6 
took 5615333 usecs

  

  [9.984204] kernel: usb 1-7: new full-speed USB device number 4 using 
xhci_hcd
  [   10.308689] kernel: usb 1-7: New USB device found, idVendor=8087, 
idProduct=0a2b, bcdDevice= 0.10
  [   10.308690] kernel: usb 1-7: New USB device strings: Mfr=0, Product=0, 
SerialNumber=0
  [   34.654721] kernel: xhci_hcd :07:00.2: can't setup: -110
  [   34.654730] kernel: xhci_hcd :07:00.2: USB bus 3 deregistered
  [   34.654769] kernel: xhci_hcd :07:00.2: init :07:00.2 fail, -110
  [   34.654771] kernel: xhci_hcd: probe of :07:00.2 failed with error -110

  $ lspci -k -s :07:00
  07:00.0 VGA compatible controller: NVIDIA Corporation TU106 [GeForce RTX 2060 
Rev. A] (rev a1)
Subsystem: Gigabyte Technology Co., Ltd TU106
Kernel driver in use: nvidia
Kernel modules: nvidiafb, nouveau, nvidia_drm, nvidia
  07:00.1 Audio device: NVIDIA Corporation TU106 High Definition Audio 
Controller (rev a1)
Subsystem: Gigabyte Technology Co., Ltd TU106 High Definition Audio 
Controller
Kernel driver in use: snd_hda_intel
Kernel modules: snd_hda_intel
  07:00.2 USB controller: NVIDIA Corporation TU106 USB 3.1 Host Controller (rev 
a1)
Subsystem: Gigabyte Technology Co., Ltd TU106 USB 3.1 Host Controller
  07:00.3 Serial bus controller [0c80]: NVIDIA Corporation TU106 USB Type-C 
Port Policy Controller (rev a1)
Subsystem: Gigabyte Technology Co., Ltd TU106 USB Type-C Port Policy 
Controller
Kernel driver in use: nvidia-gpu
Kernel modules: i2c_nvidia_gpu

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: linux-image-5.0.0-15-generic 5.0.0-15.16
  ProcVersionSignature: Ubuntu 5.0.0-15.16-generic 5.0.6
  Uname: Linux 5.0.0-15-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  daniel 4470 F pulseaudio
   /dev/snd/controlC1:  daniel 4470 F pulseaudio
   /dev/snd/controlC2:  daniel 4470 F pulseaudio
  CurrentDesktop: i3
  Date: Wed May 29 09:36:51 2019
  InstallationDate: Installed on 2019-05-07 (21 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  MachineType: Gigabyte Technology Co., Ltd. B450M DS3H
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-15-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash 
resume=UUID=73909634-a75d-42c9-8f66-a69138690756 vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-15-generic N/A
   linux-backports-modules-5.0.0-15-generic  N/A
   linux-firmware1.179
  SourcePackage: linux
  UpgradeStatus: Upgraded to eoan on 2019-05-08 (20 days ago)
  dmi.bios.date: 01/25/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F4
  dmi.board.asset.tag: Default string
  dmi.board.name: B450M DS3H-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF4:bd01/25/2019:svnGigabyteTechnologyCo.,Ltd.:pnB450MDS3H:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB450MDS3H-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: B450M DS3H
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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


[Kernel-packages] [Bug 1820075] Re: [Packaging] Improve config annotations check on custom kernels

2019-05-31 Thread Marcelo Cerri
** Also affects: linux-azure (Ubuntu Xenial)
   Importance: Undecided
   Status: New

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

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

** Changed in: linux-azure (Ubuntu Bionic)
   Status: In Progress => Invalid

** Changed in: linux-azure (Ubuntu Xenial)
 Assignee: (unassigned) => Marcelo Cerri (mhcerri)

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

Title:
  [Packaging] Improve config annotations check on custom kernels

Status in linux-azure package in Ubuntu:
  New
Status in linux-gcp package in Ubuntu:
  New
Status in linux-azure source package in Xenial:
  In Progress
Status in linux-gcp source package in Xenial:
  New
Status in linux-azure source package in Bionic:
  Invalid
Status in linux-gcp source package in Bionic:
  New
Status in linux-azure source package in Cosmic:
  In Progress
Status in linux-gcp source package in Cosmic:
  Fix Released
Status in linux-azure source package in Disco:
  In Progress
Status in linux-gcp source package in Disco:
  New

Bug description:
  [Impact]

  Currently for custom kernels, it's necessary to keep a separate
  annotations file that often gets out of sync with the corresponding
  file in debian.master/.

  The "debian/scripts/config-check" script can be changed to allow
  additional annotations files to act as overlays over the original
  annotations file, allowing custom kernels to override the policies
  just for the relevant configs.

  The proposal is to add support for an include directive in the
  annotations file so custom kernels can include the annotations file
  from its base kernel and override policies on a config basis.

  [Test Case]

  A kernel build should complete successfully after the change.

  
  [Regression Potential] 

  Low regression potential since that's a change on the build process
  that doesn't affect the final kernel that is built.

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

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


[Kernel-packages] [Bug 1831276] Re: Gnome wayland hangs with nvidia driver on video load/changing tabs

2019-05-31 Thread lotuspsychje
Thank you for reporting your bug to make Ubuntu better.

Please in the future use ubuntu-bug affectedpackage so relevant info and logs
are automaticly added to your bug and developers can debug a better way.

You can still use apport-collect BUGID in this stage to pull add your
info.

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

Title:
  Gnome wayland hangs with nvidia driver on video load/changing tabs

Status in nvidia-graphics-drivers-418 package in Ubuntu:
  New

Bug description:
  This is on nvidia 430, which is only packages in PPAs so far.

  I've reproduced this by just playing a Youtube video (Not using
  wayland enabled Firefox, but Beta snappy version) or by switching tabs
  while on a google hangout meet.

  The video or hangout continues but the screen is fully locked up.
  Switch to other VTs does not work.

  Only error reported is:
  May 28 21:30:06 desktop kernel: [drm:nv_drm_atomic_commit [nvidia_drm]] 
*ERROR* [nvidia-drm] [GPU ID 0x1c00] Flip event timeout on head 0

  Ubuntu 19.04
  nvidia-driver-430 430.14-0ubuntu0~gpu19.04.1
  snap firefox 68.0b5-1 2019-05-28 (221)
  gnome-shell3.32.0+git20190410-1ubuntu1
  mutter 3.32.0+git20190410-1ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-418/+bug/1831276/+subscriptions

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


[Kernel-packages] [Bug 1831276] [NEW] Gnome wayland hangs with nvidia driver on video load/changing tabs

2019-05-31 Thread Bryan Quigley
Public bug reported:

This is on nvidia 430, which is only packages in PPAs so far.

I've reproduced this by just playing a Youtube video (Not using wayland
enabled Firefox, but Beta snappy version) or by switching tabs while on
a google hangout meet.

The video or hangout continues but the screen is fully locked up. Switch
to other VTs does not work.

Only error reported is:
May 28 21:30:06 desktop kernel: [drm:nv_drm_atomic_commit [nvidia_drm]] *ERROR* 
[nvidia-drm] [GPU ID 0x1c00] Flip event timeout on head 0

Ubuntu 19.04
nvidia-driver-430 430.14-0ubuntu0~gpu19.04.1
snap firefox 68.0b5-1 2019-05-28 (221)
gnome-shell3.32.0+git20190410-1ubuntu1
mutter 3.32.0+git20190410-1ubuntu1

** Affects: nvidia-graphics-drivers-418 (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  Gnome wayland hangs with nvidia driver on video load/changing tabs

Status in nvidia-graphics-drivers-418 package in Ubuntu:
  New

Bug description:
  This is on nvidia 430, which is only packages in PPAs so far.

  I've reproduced this by just playing a Youtube video (Not using
  wayland enabled Firefox, but Beta snappy version) or by switching tabs
  while on a google hangout meet.

  The video or hangout continues but the screen is fully locked up.
  Switch to other VTs does not work.

  Only error reported is:
  May 28 21:30:06 desktop kernel: [drm:nv_drm_atomic_commit [nvidia_drm]] 
*ERROR* [nvidia-drm] [GPU ID 0x1c00] Flip event timeout on head 0

  Ubuntu 19.04
  nvidia-driver-430 430.14-0ubuntu0~gpu19.04.1
  snap firefox 68.0b5-1 2019-05-28 (221)
  gnome-shell3.32.0+git20190410-1ubuntu1
  mutter 3.32.0+git20190410-1ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-418/+bug/1831276/+subscriptions

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


[Kernel-packages] [Bug 1830905] Re: Nvidia RTX 2060 USB bus timeouts cause ~30s delay in boot

2019-05-31 Thread Dan Watkins
OK, this improves things slightly; the first timeout is gone:

[0.12] kernel: pci :07:00.1: Linked as a consumer to :07:00.0
[0.124592] kernel: PCI: CLS 64 bytes, default 64
[0.124621] kernel: Unpacking initramfs...

But the second (longer) timeout is still there, and now has a trace:

[4.601812] kernel: usb 1-7: New USB device strings: Mfr=0, Product=0, 
SerialNumber=0
[   28.016007] kernel: watchdog: BUG: soft lockup - CPU#4 stuck for 23s! 
[swapper/0:1]
[   28.016007] kernel: Modules linked in:
[   28.016007] kernel: CPU: 4 PID: 1 Comm: swapper/0 Not tainted 
5.0.0-16-generic #17~lp1830905+2
[   28.016007] kernel: Hardware name: Gigabyte Technology Co., Ltd. B450M 
DS3H/B450M DS3H-CF, BIOS F4 01/25/2019
[   28.016007] kernel: RIP: 0010:xhci_reset+0x7f/0x1a0
[   28.016007] kernel: Code: 00 00 00 4d 8b 6c 24 18 bb 80 96 98 00 eb 17 a8 02 
74 43 bf c7 10 00 00 e8 4e 30 25 00 83 eb 01 0f 84 e9 00 00 00 41 8b 45 00 <83> 
f8 ff 75 e0 b8 ed ff ff ff 5b 41 5c 41 5d 5d c3 48 8b 07 48 c7
[   28.016007] kernel: RSP: 0018:acb30004bad0 EFLAGS: 0202 ORIG_RAX: 
ff13
[   28.016007] kernel: RAX: 0002 RBX: 00050ef2 RCX: 
0002
[   28.016007] kernel: RDX: 13d4 RSI: 0024d0b051d8 RDI: 
0ded
[   28.016007] kernel: RBP: acb30004bae8 R08:  R09: 

[   28.016007] kernel: R10: 0002 R11: 000f R12: 
89803bf62230
[   28.016007] kernel: R13: acb302480020 R14: 8bbddee0 R15: 
89803bf62230
[   28.016007] kernel: FS:  () GS:89804eb0() 
knlGS:
[   28.016007] kernel: CS:  0010 DS:  ES:  CR0: 80050033
[   28.016007] kernel: CR2: 7f3995075e04 CR3: 0001ec00e000 CR4: 
003406e0
[   28.016007] kernel: Call Trace:
[   28.016007] kernel:  xhci_gen_setup+0x224/0x3e0
[   28.016007] kernel:  ? pci_bus_read_config_byte+0x40/0x60
[   28.016007] kernel:  xhci_pci_setup+0x56/0x120
[   28.016007] kernel:  usb_add_hcd+0x2cb/0x8a0
[   28.016007] kernel:  usb_hcd_pci_probe+0x283/0x480
[   28.016007] kernel:  xhci_pci_probe+0x30/0x230
[   28.016007] kernel:  local_pci_probe+0x47/0xa0
[   28.016007] kernel:  pci_device_probe+0x145/0x1b0
[   28.016007] kernel:  really_probe+0xfe/0x3f0
[   28.016007] kernel:  ? set_debug_rodata+0x17/0x17
[   28.016007] kernel:  driver_probe_device+0x11a/0x130
[   28.016007] kernel:  __driver_attach+0xe3/0x110
[   28.016007] kernel:  ? driver_probe_device+0x130/0x130
[   28.016007] kernel:  ? driver_probe_device+0x130/0x130
[   28.016007] kernel:  bus_for_each_dev+0x74/0xb0
[   28.016007] kernel:  ? kmem_cache_alloc_trace+0x1a6/0x1c0
[   28.016007] kernel:  driver_attach+0x1e/0x20
[   28.016007] kernel:  bus_add_driver+0x167/0x260
[   28.016007] kernel:  ? xhci_debugfs_create_root+0x25/0x25
[   28.016007] kernel:  driver_register+0x60/0x100
[   28.016007] kernel:  ? xhci_debugfs_create_root+0x25/0x25
[   28.016007] kernel:  __pci_register_driver+0x5a/0x60
[   28.016007] kernel:  xhci_pci_init+0x47/0x49
[   28.016007] kernel:  do_one_initcall+0x4a/0x1c9
[   28.016007] kernel:  kernel_init_freeable+0x1cb/0x272
[   28.016007] kernel:  ? rest_init+0xb0/0xb0
[   28.016007] kernel:  kernel_init+0xe/0x110
[   28.016007] kernel:  ret_from_fork+0x22/0x40
[   28.874267] kernel: xhci_hcd :07:00.2: can't setup: -110
[   28.874275] kernel: xhci_hcd :07:00.2: USB bus 3 deregistered
[   28.874312] kernel: xhci_hcd :07:00.2: init :07:00.2 fail, -110
[   28.874314] kernel: xhci_hcd: probe of :07:00.2 failed with error -110

I've done a bit of digging regarding the USB bus; I believe it's present
to support a USB-C port which some RTX 2060 cards do have, but my
specific model _does not_ have.

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

Title:
  Nvidia RTX 2060 USB bus timeouts cause ~30s delay in boot

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  From dmesg:

  [0.132667] kernel: pci :07:00.1: Linked as a consumer to :07:00.0
  [5.882727] kernel: pci :07:00.2: xHCI HW not ready after 5 sec (HC 
bug?) status = 0x801
  [5.882781] kernel: pci :07:00.2: quirk_usb_early_handoff+0x0/0x6a6 
took 5615333 usecs

  

  [9.984204] kernel: usb 1-7: new full-speed USB device number 4 using 
xhci_hcd
  [   10.308689] kernel: usb 1-7: New USB device found, idVendor=8087, 
idProduct=0a2b, bcdDevice= 0.10
  [   10.308690] kernel: usb 1-7: New USB device strings: Mfr=0, Product=0, 
SerialNumber=0
  [   34.654721] kernel: xhci_hcd :07:00.2: can't setup: -110
  [   34.654730] kernel: xhci_hcd :07:00.2: USB bus 3 deregistered
  [   34.654769] kernel: xhci_hcd :07:00.2: init :07:00.2 fail, -110
  [   34.654771] kernel: xhci_hcd: probe of :07:00.2 failed with error -110

  $ lspci -k -s 

[Kernel-packages] [Bug 1830941] Re: linux: 4.4.0-150.176 -proposed tracker

2019-05-31 Thread Ubuntu Kernel Bot
** 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 will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  backports: bug 1829205 (trusty/linux-aws), bug 1830947 
(trusty/linux-lts-xenial)
  derivatives: bug 1829193 (linux-aws), bug 1829195 (linux-kvm), bug 1829198 
(linux-raspi2), bug 1829201 (linux-snapdragon), bug 1829203 (linux-fips)
  
  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
  phase: Signoff
  phase-changed: Friday, 31. May 2019 13:31 UTC
  reason:
regression-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
-   snap-release-to-beta: 'Pending -- snap pc-kernel not in expected 
channel(s): arch=amd64:channel=latest/beta
- arch=i386:channel=latest/beta'
-   snap-release-to-edge: 'Pending -- snap pc-kernel not in expected 
channel(s): arch=amd64:channel=latest/edge
- arch=i386:channel=latest/edge'
+   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/1830941

Title:
  linux: 4.4.0-150.176 -proposed tracker

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

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

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

  backports: bug 1829205 (trusty/linux-aws), bug 1830947 
(trusty/linux-lts-xenial)
  derivatives: bug 1829193 (linux-aws), bug 1829195 (linux-kvm), bug 1829198 
(linux-raspi2), bug 1829201 (linux-snapdragon), bug 1829203 (linux-fips)

  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
  phase: Signoff
  phase-changed: Friday, 31. May 2019 13:31 UTC
  reason:
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/1830941/+subscriptions

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


[Kernel-packages] [Bug 1801359] Re: Notebook lid blank after booting with lid closed

2019-05-31 Thread Kai-Heng Feng
I'll see if this also happens to the Precision 5520 in our lab.

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => Kai-Heng Feng (kaihengfeng)

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

Title:
  Notebook lid blank after booting with lid closed

Status in linux package in Ubuntu:
  Triaged

Bug description:
  When using a external monitor on a Dell Precision 5520 Notebook and
  booting with lid closed ...

  1. the lid stays blank when later opening it (happens on Ubuntu 18.10
  and 18.04)

  2. and login using a Xorg is not possible (a login-loop happens on
  Ubuntu 18.10)

  Digging in sysfs I saw that /sys/class/backlight/intel_backlight/bl_power 
  0 (and manually changable) when booted with lid open
  but 4 (and unchangable) when booted with lid closed. 

  Other (eg. power) entires under /sys/class/backlight/intel_backlight
  can't be changed or don't help and changing
  /sys/class/backlight/intel_backlight/brightness don't help as well.

  There is neither a difference in dmesg output (except some additional
  "enabling Extended Tags" when booting with lid open) nor any
  difference in modules loaded.

  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
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  mm 1720 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Nov  2 13:38:44 2018
  InstallationDate: Installed on 2018-10-19 (13 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 04f3:24a1 Elan Microelectronics Corp. 
   Bus 001 Device 005: ID 0c45:6713 Microdia 
   Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Precision 5520
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/vmlinuz 
root=UUID=31b59337-0e21-48d0-bede-155475fc0c7b ro rootflags=subvol=@ rootwait 
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
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/02/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.12.1
  dmi.board.name: 0R6JFH
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.12.1:bd10/02/2018:svnDellInc.:pnPrecision5520:pvr:rvnDellInc.:rn0R6JFH:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Precision
  dmi.product.name: Precision 5520
  dmi.product.sku: 07BF
  dmi.sys.vendor: Dell Inc.

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

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


[Kernel-packages] [Bug 1830905] Re: Nvidia RTX 2060 USB bus timeouts cause ~30s delay in boot

2019-05-31 Thread Kai-Heng Feng
One possibility is that it doesn't need to do xhci handoff, please test:
https://people.canonical.com/~khfeng/lp1830905-2/

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

Title:
  Nvidia RTX 2060 USB bus timeouts cause ~30s delay in boot

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  From dmesg:

  [0.132667] kernel: pci :07:00.1: Linked as a consumer to :07:00.0
  [5.882727] kernel: pci :07:00.2: xHCI HW not ready after 5 sec (HC 
bug?) status = 0x801
  [5.882781] kernel: pci :07:00.2: quirk_usb_early_handoff+0x0/0x6a6 
took 5615333 usecs

  

  [9.984204] kernel: usb 1-7: new full-speed USB device number 4 using 
xhci_hcd
  [   10.308689] kernel: usb 1-7: New USB device found, idVendor=8087, 
idProduct=0a2b, bcdDevice= 0.10
  [   10.308690] kernel: usb 1-7: New USB device strings: Mfr=0, Product=0, 
SerialNumber=0
  [   34.654721] kernel: xhci_hcd :07:00.2: can't setup: -110
  [   34.654730] kernel: xhci_hcd :07:00.2: USB bus 3 deregistered
  [   34.654769] kernel: xhci_hcd :07:00.2: init :07:00.2 fail, -110
  [   34.654771] kernel: xhci_hcd: probe of :07:00.2 failed with error -110

  $ lspci -k -s :07:00
  07:00.0 VGA compatible controller: NVIDIA Corporation TU106 [GeForce RTX 2060 
Rev. A] (rev a1)
Subsystem: Gigabyte Technology Co., Ltd TU106
Kernel driver in use: nvidia
Kernel modules: nvidiafb, nouveau, nvidia_drm, nvidia
  07:00.1 Audio device: NVIDIA Corporation TU106 High Definition Audio 
Controller (rev a1)
Subsystem: Gigabyte Technology Co., Ltd TU106 High Definition Audio 
Controller
Kernel driver in use: snd_hda_intel
Kernel modules: snd_hda_intel
  07:00.2 USB controller: NVIDIA Corporation TU106 USB 3.1 Host Controller (rev 
a1)
Subsystem: Gigabyte Technology Co., Ltd TU106 USB 3.1 Host Controller
  07:00.3 Serial bus controller [0c80]: NVIDIA Corporation TU106 USB Type-C 
Port Policy Controller (rev a1)
Subsystem: Gigabyte Technology Co., Ltd TU106 USB Type-C Port Policy 
Controller
Kernel driver in use: nvidia-gpu
Kernel modules: i2c_nvidia_gpu

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: linux-image-5.0.0-15-generic 5.0.0-15.16
  ProcVersionSignature: Ubuntu 5.0.0-15.16-generic 5.0.6
  Uname: Linux 5.0.0-15-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  daniel 4470 F pulseaudio
   /dev/snd/controlC1:  daniel 4470 F pulseaudio
   /dev/snd/controlC2:  daniel 4470 F pulseaudio
  CurrentDesktop: i3
  Date: Wed May 29 09:36:51 2019
  InstallationDate: Installed on 2019-05-07 (21 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  MachineType: Gigabyte Technology Co., Ltd. B450M DS3H
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-15-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash 
resume=UUID=73909634-a75d-42c9-8f66-a69138690756 vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-15-generic N/A
   linux-backports-modules-5.0.0-15-generic  N/A
   linux-firmware1.179
  SourcePackage: linux
  UpgradeStatus: Upgraded to eoan on 2019-05-08 (20 days ago)
  dmi.bios.date: 01/25/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F4
  dmi.board.asset.tag: Default string
  dmi.board.name: B450M DS3H-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF4:bd01/25/2019:svnGigabyteTechnologyCo.,Ltd.:pnB450MDS3H:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB450MDS3H-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: B450M DS3H
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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


[Kernel-packages] [Bug 1831268] [NEW] Ubuntu 19.04: Random SR-IOV issues

2019-05-31 Thread Joseph Salisbury
Public bug reported:

No VFs inside the VM.

Unfortunately this issue doesn’t have a 100% repro. Sometimes all the
VFs are missing, other times a few are available and the rest are
missing.

The best test case to catch this issue is VERIFY-ENABLE-DISABLE-SRIOV-
ON-EXISTING-VM.

Comparing the logs between working/not working VMs, the only difference was 
that these 2 messages were missing from the broken VMs:
mlx4_en: rename9: Steering Mode 2

mlx4_en: rename9: Link Up

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

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

Title:
  Ubuntu 19.04: Random SR-IOV issues

Status in linux-azure package in Ubuntu:
  New

Bug description:
  No VFs inside the VM.

  Unfortunately this issue doesn’t have a 100% repro. Sometimes all the
  VFs are missing, other times a few are available and the rest are
  missing.

  The best test case to catch this issue is VERIFY-ENABLE-DISABLE-SRIOV-
  ON-EXISTING-VM.

  Comparing the logs between working/not working VMs, the only difference was 
that these 2 messages were missing from the broken VMs:
  mlx4_en: rename9: Steering Mode 2

  mlx4_en: rename9: Link Up

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

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


[Kernel-packages] [Bug 1829198] Re: linux-raspi2: 4.4.0-1110.118 -proposed tracker

2019-05-31 Thread Ubuntu Kernel Bot
** Changed in: kernel-sru-workflow/snap-release-to-candidate
   Status: New => Confirmed

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  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: 1830941
  phase: Ready for Testing
  phase-changed: Wednesday, 29. May 2019 07:36 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   snap-certification-testing: Ongoing -- testing in progress
+   snap-release-to-candidate: 'Pending -- snap pi2-kernel not in expected 
channel(s):
+ arch=armhf:channel=latest/candidate:rev=89'
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/1829198

Title:
  linux-raspi2: 4.4.0-1110.118 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Fix Released
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow 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:
  Fix Released
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 verification-testing series:
  Confirmed
Status in linux-raspi2 package in Ubuntu:
  Invalid
Status in linux-raspi2 source package in Xenial:
  New

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  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: 1830941
  phase: Ready for Testing
  phase-changed: Wednesday, 29. May 2019 07:36 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
snap-release-to-candidate: 'Pending -- snap pi2-kernel not in expected 
channel(s):
  arch=armhf:channel=latest/candidate:rev=89'
verification-testing: Ongoing -- testing in progress

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

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


[Kernel-packages] [Bug 1830175] Re: Add support to Comet Lake LPSS

2019-05-31 Thread Kai-Heng Feng
** 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/1830175

Title:
  Add support to Comet Lake LPSS

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in linux-oem-osp1 package in Ubuntu:
  New
Status in linux source package in Bionic:
  Fix Committed
Status in linux-oem-osp1 source package in Bionic:
  Fix Committed
Status in linux source package in Cosmic:
  Fix Committed
Status in linux-oem-osp1 source package in Cosmic:
  Invalid
Status in linux source package in Disco:
  Fix Committed
Status in linux-oem-osp1 source package in Disco:
  Invalid

Bug description:
  [Impact]
  I2C touchpad doesn't work when it's connected to Comet Lake LPSS, which isn't 
supported.

  [Fix]
  Add CML LPSS PCI IDs to intel-lpss module.

  [Test]
  The I2C touchpad connected to CML LPSS works after applying the patch.

  [Regression Potential]
  None. It's a new device enablement.

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

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


[Kernel-packages] [Bug 1829198] Re: linux-raspi2: 4.4.0-1110.118 -proposed tracker

2019-05-31 Thread Taihsiang Ho
** 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/1829198

Title:
  linux-raspi2: 4.4.0-1110.118 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Fix Released
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow 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:
  Fix Released
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 verification-testing series:
  Confirmed
Status in linux-raspi2 package in Ubuntu:
  Invalid
Status in linux-raspi2 source package in Xenial:
  New

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  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: 1830941
  phase: Ready for Testing
  phase-changed: Wednesday, 29. May 2019 07:36 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
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/1829198/+subscriptions

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


[Kernel-packages] [Bug 1831232] Re: Ubuntu 18.04 won't boot - failed to connect to lvmetad

2019-05-31 Thread Kai-Heng Feng
** Also affects: lvm2 (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  Ubuntu 18.04 won't boot - failed to connect to lvmetad

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

Bug description:
  This bug report relates to a machine running 18.04, not the one I am
  submitting the report from.

  On 30 May The Software Updater prompted me to update. Included in the
  update were initramfs components. I now cannot boot the machine.

  After decrypting the root file system, instead of being prompted for
  the pass-phrase to decrypt the swap, I get the message "cannot connect
  to lvmetad: falling back to device scanning". This repeats for a while
  until I am dropped into a recovery shell of some sort from which I
  cannot access the root disk.

  Blocker. My machine is unusable.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-generic 4.15.0.48.50
  ProcVersionSignature: Ubuntu 4.15.0-48.51-generic 4.15.18
  Uname: Linux 4.15.0-48-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  gdm2433 F pulseaudio
raph   8920 F pulseaudio
   /dev/snd/controlC0:  gdm2433 F pulseaudio
  Date: Fri May 31 12:08:33 2019
  HibernationDevice: RESUME=UUID=2538baa4-d43e-4876-8d94-dd3221894bac
  InstallationDate: Installed on 2018-02-09 (475 days ago)
  InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: LENOVO 20CJS0UU00
  ProcEnviron:
   LANGUAGE=en_GB:en
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-48-generic 
root=/dev/mapper/xubuntu--vg-root ro quiet splash vt.handoff=1
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-48-generic N/A
   linux-backports-modules-4.15.0-48-generic  N/A
   linux-firmware 1.173.5
  SourcePackage: linux
  UpgradeStatus: Upgraded to bionic on 2018-09-12 (260 days ago)
  dmi.bios.date: 09/13/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N11ET42W (1.18 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20CJS0UU00
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 WIN
  dmi.chassis.asset.tag: R90G3N7R
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN11ET42W(1.18):bd09/13/2017:svnLENOVO:pn20CJS0UU00:pvrThinkPadT550:rvnLENOVO:rn20CJS0UU00:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T550
  dmi.product.name: 20CJS0UU00
  dmi.product.version: ThinkPad T550
  dmi.sys.vendor: LENOVO

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

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


[Kernel-packages] [Bug 1827437] Re: potential memory corruption on arm64 on dev release

2019-05-31 Thread dann frazier
(initramfs) modprobe -r hisi_sas_v3_hw
[   70.546285] hisi_sas_v3_hw :74:02.0: dev[4:1] is gone
[   70.552479] sd 3:0:1:0: [sdc] Synchronizing SCSI cache
[   70.561963] sd 3:0:1:0: [sdc] Stopping disk
[   71.161605] hisi_sas_v3_hw :74:02.0: dev[3:5] is gone
[   71.168193] sd 3:0:0:0: [sdb] Synchronizing SCSI cache
[   71.180633] sd 3:0:0:0: [sdb] Stopping disk
[   71.785586] hisi_sas_v3_hw :74:02.0: dev[2:5] is gone
[   71.794376] hisi_sas_v3_hw :74:02.0: dev[1:2] is gone
(initramfs) cat /proc/version
Linux version 4.18.0-21-generic (buildd@bos02-arm64-052) (gcc version 8.2.0 
(Ubuntu 8.2.0-7ubuntu1)) #22-Ubuntu SMP Wed May 15 13:14:00 UTC 2019
(initramfs) 


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

Title:
  potential memory corruption on arm64 on dev release

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  Fix Committed
Status in linux source package in Cosmic:
  Fix Committed

Bug description:
  [Impact]
  Potential memory corruption.

  [Test Case]
  I've not seen a failure in practice (well, it's easy to crash 5.0 but, as the 
commit message notes, that's because it includes an additional patch that 
happens to "tickle" this. But to regression test, I boot a HiSilicon D06 to a 
ramdisk and remove the hisi_sas_v3_hw module, which allocates memory as 
described in the commit message.

  [Fix]
  376991db4b646 driver core: Postpone DMA tear-down until after devres release

  [Regression Risk]
  From the stable tree, so in theory would be applied eventually anyway.

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

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


[Kernel-packages] [Bug 1829166] Re: linux-azure: 5.0.0-1007.7 -proposed tracker

2019-05-31 Thread Ubuntu Kernel Bot
** Changed in: kernel-sru-workflow/verification-testing
   Status: Confirmed => Fix Released

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  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: 1829173
- phase: Ready for Testing
- phase-changed: Tuesday, 28. May 2019 21:33 UTC
+ phase: Ready for Signoff
+ phase-changed: Friday, 31. May 2019 16:03 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
+   promote-to-updates: Holding -- stakeholder signoff not verified
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/1829166

Title:
  linux-azure: 5.0.0-1007.7 -proposed tracker

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

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  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: 1829173
  phase: Ready for Signoff
  phase-changed: Friday, 31. May 2019 16:03 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
promote-to-updates: Holding -- stakeholder signoff not verified
stakeholder-signoff: Pending -- waiting for signoff

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

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


[Kernel-packages] [Bug 1829164] Re: linux-raspi2: 5.0.0-1009.9 -proposed tracker

2019-05-31 Thread Ubuntu Kernel Bot
** Changed in: kernel-sru-workflow/verification-testing
   Status: Confirmed => Fix Released

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  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: 1829173
- phase: Ready for Testing
- phase-changed: Wednesday, 29. May 2019 07:32 UTC
+ phase: Holding before Release
+ phase-changed: Friday, 31. May 2019 16:03 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   verification-testing: Ongoing -- testing in progress
+   promote-to-updates: Holding -- cycle not ready to release

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

Title:
  linux-raspi2: 5.0.0-1009.9 -proposed tracker

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

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  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: 1829173
  phase: Holding before Release
  phase-changed: Friday, 31. May 2019 16:03 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
promote-to-updates: Holding -- cycle not ready to release

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

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


[Kernel-packages] [Bug 1829169] Re: linux-kvm: 5.0.0-1007.7 -proposed tracker

2019-05-31 Thread Ubuntu Kernel Bot
** Changed in: kernel-sru-workflow/verification-testing
   Status: Confirmed => Fix Released

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  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: 1829173
  phase: Ready for Testing
  phase-changed: Tuesday, 28. May 2019 21:34 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
regression-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-kvm in Ubuntu.
https://bugs.launchpad.net/bugs/1829169

Title:
  linux-kvm: 5.0.0-1007.7 -proposed tracker

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

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  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: 1829173
  phase: Ready for Testing
  phase-changed: Tuesday, 28. May 2019 21:34 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
regression-testing: Ongoing -- testing in progress

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

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


[Kernel-packages] [Bug 1829168] Re: linux-gcp: 5.0.0-1007.7 -proposed tracker

2019-05-31 Thread Ubuntu Kernel Bot
** Changed in: kernel-sru-workflow/verification-testing
   Status: Confirmed => Fix Released

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  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: 1829173
- phase: Ready for Testing
- phase-changed: Tuesday, 28. May 2019 21:34 UTC
+ phase: Holding before Release
+ phase-changed: Friday, 31. May 2019 16:04 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   verification-testing: Ongoing -- testing in progress
+   promote-to-updates: Holding -- cycle not ready to release

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

Title:
  linux-gcp: 5.0.0-1007.7 -proposed tracker

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

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  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: 1829173
  phase: Holding before Release
  phase-changed: Friday, 31. May 2019 16:04 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
promote-to-updates: Holding -- cycle not ready to release

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

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


[Kernel-packages] [Bug 1829170] Re: linux-snapdragon: 5.0.0-1013.13 -proposed tracker

2019-05-31 Thread Ubuntu Kernel Bot
** Changed in: kernel-sru-workflow/verification-testing
   Status: Confirmed => Fix Released

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  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: 1829173
- phase: Ready for Testing
- phase-changed: Wednesday, 29. May 2019 07:33 UTC
+ phase: Holding before Release
+ phase-changed: Friday, 31. May 2019 16:04 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   verification-testing: Ongoing -- testing in progress
+   promote-to-updates: Holding -- cycle not ready to release

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

Title:
  linux-snapdragon: 5.0.0-1013.13 -proposed tracker

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

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  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: 1829173
  phase: Holding before Release
  phase-changed: Friday, 31. May 2019 16:04 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
promote-to-updates: Holding -- cycle not ready to release

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

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


[Kernel-packages] [Bug 1829165] Re: linux-aws: 5.0.0-1007.7 -proposed tracker

2019-05-31 Thread Ubuntu Kernel Bot
** Changed in: kernel-sru-workflow/verification-testing
   Status: Confirmed => Fix Released

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  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: 1829173
- phase: Ready for Testing
- phase-changed: Tuesday, 28. May 2019 21:33 UTC
+ phase: Holding before Release
+ phase-changed: Friday, 31. May 2019 16:03 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   verification-testing: Ongoing -- testing in progress
+   promote-to-updates: Holding -- cycle not ready to release

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

Title:
  linux-aws: 5.0.0-1007.7 -proposed tracker

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

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  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: 1829173
  phase: Holding before Release
  phase-changed: Friday, 31. May 2019 16:03 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
promote-to-updates: Holding -- cycle not ready to release

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

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


[Kernel-packages] [Bug 1829173] Re: linux: 5.0.0-16.17 -proposed tracker

2019-05-31 Thread Ubuntu Kernel Bot
** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  backports: bug 1829171 (bionic/linux-hwe-edge), bug 1830840 
(bionic/linux-oem-osp1)
  derivatives: bug 1829164 (linux-raspi2), bug 1829165 (linux-aws), bug 1829166 
(linux-azure), bug 1829168 (linux-gcp), bug 1829169 (linux-kvm), bug 1829170 
(linux-snapdragon)
  
  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
- phase: Ready for Testing
- phase-changed: Tuesday, 28. May 2019 21:30 UTC
+ phase: Holding before Release
+ phase-changed: Friday, 31. May 2019 16:00 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   verification-testing: Ongoing -- testing in progress
+   promote-to-updates: Holding -- cycle not ready to release

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

Title:
  linux: 5.0.0-16.17 -proposed tracker

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

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

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

  backports: bug 1829171 (bionic/linux-hwe-edge), bug 1830840 
(bionic/linux-oem-osp1)
  derivatives: bug 1829164 (linux-raspi2), bug 1829165 (linux-aws), bug 1829166 
(linux-azure), bug 1829168 (linux-gcp), bug 1829169 (linux-kvm), bug 1829170 
(linux-snapdragon)

  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
  phase: Holding before Release
  phase-changed: Friday, 31. May 2019 16:00 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
promote-to-updates: Holding -- cycle not ready to release

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

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


[Kernel-packages] [Bug 1830910] Re: Kernel traces in ieee80211 after "Hardware restart was requested"

2019-05-31 Thread Kai-Heng Feng
Maybe try the latest firmware without the mainline 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/1830910

Title:
  Kernel traces in ieee80211 after "Hardware restart was requested"

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  When using my desktop normally, I experienced a hard lock-up.  On
  reboot, I was able to examine the journal to find a whole bunch of
  traces (attached in journal-traces).

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: linux-image-5.0.0-15-generic 5.0.0-15.16
  ProcVersionSignature: Ubuntu 5.0.0-15.16-generic 5.0.6
  Uname: Linux 5.0.0-15-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  daniel 4111 F pulseaudio
   /dev/snd/controlC1:  daniel 4111 F pulseaudio
   /dev/snd/controlC2:  daniel 4111 F pulseaudio
  CurrentDesktop: i3
  Date: Wed May 29 10:12:40 2019
  InstallationDate: Installed on 2019-05-07 (21 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  MachineType: Gigabyte Technology Co., Ltd. B450M DS3H
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-15-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash 
resume=UUID=73909634-a75d-42c9-8f66-a69138690756 vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-15-generic N/A
   linux-backports-modules-5.0.0-15-generic  N/A
   linux-firmware1.179
  SourcePackage: linux
  UpgradeStatus: Upgraded to eoan on 2019-05-08 (20 days ago)
  dmi.bios.date: 01/25/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F4
  dmi.board.asset.tag: Default string
  dmi.board.name: B450M DS3H-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF4:bd01/25/2019:svnGigabyteTechnologyCo.,Ltd.:pnB450MDS3H:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB450MDS3H-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: B450M DS3H
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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


[Kernel-packages] [Bug 1824879] Re: linux-azure: Add the Catapult FPGA Driver

2019-05-31 Thread Marcelo Cerri
Disco: https://lists.ubuntu.com/archives/kernel-
team/2019-May/101028.html

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

Title:
  linux-azure: Add the Catapult FPGA Driver

Status in linux-azure package in Ubuntu:
  Fix Released
Status in linux-azure source package in Xenial:
  Fix Released
Status in linux-azure source package in Cosmic:
  Fix Released
Status in linux-azure source package in Disco:
  In Progress

Bug description:
  [Impact]

  Add the Catapult FPGA Driver to the custom linux-azure kernel while a
  version is not available upstream.

  [Test Case]

  The catapult driver must be present as a module in the linux-modules
  package (not in the linux-modules-extra).

  [Regression Potential]

  Low risk of regression since that's a new driver.

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

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


[Kernel-packages] [Bug 1825777] Re: False positive test result in run_netsocktests from net in ubuntu_kernel_selftest

2019-05-31 Thread Kleber Sacilotto de Souza
On disco the ubuntu_kernel_selftest.net testcase is failing to compile
(bug 1829812), so we are not able to verify 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/1825777

Title:
  False positive test result in run_netsocktests from net in
  ubuntu_kernel_selftest

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

Bug description:
  == SRU Justification ==

  The run_netsocktests from net in ubuntu_kernel_selftest will be marked
  as passed regardless the actual test result from the ./socket:

  selftests: net: run_netsocktests
  
  
  running socket test
  
  [FAIL]
  ok 1..6 selftests: net: run_netsocktests [PASS]

  This is because the test script itself has been successfully executed,
  and make it return 0.

  == Fix ==
  30c04d79 (selftests/net: correct the return value for run_netsocktests)

  This can be cherry-picked into all of our kernels.

  == Test ==
  Patch tested and submitted to the upstream.

  == Regression Potential ==
  Changes limit to the testing tool, and it's is expected to see failures
  from this test in the future.

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

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


[Kernel-packages] [Bug 1829173] Re: linux: 5.0.0-16.17 -proposed tracker

2019-05-31 Thread Kleber Sacilotto de Souza
Verification tests completed successfully, with exception of:
- bug 1825777

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

Title:
  linux: 5.0.0-16.17 -proposed tracker

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

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

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

  backports: bug 1829171 (bionic/linux-hwe-edge), bug 1830840 
(bionic/linux-oem-osp1)
  derivatives: bug 1829164 (linux-raspi2), bug 1829165 (linux-aws), bug 1829166 
(linux-azure), bug 1829168 (linux-gcp), bug 1829169 (linux-kvm), bug 1829170 
(linux-snapdragon)

  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
  phase: Holding before Release
  phase-changed: Friday, 31. May 2019 16:00 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
promote-to-updates: Holding -- cycle not ready to release

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

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


[Kernel-packages] [Bug 1829179] Re: linux-azure: 4.18.0-1019.19~18.04.1 -proposed tracker

2019-05-31 Thread Sean Feole
Known Bugs:
amd64:

monotonic:(1829179): clock test in monotonic_time will fail on Azure Instances
kvm_unit_tests: 1824228: ept test fails in kvm_unit_tests , 1821394: vmx tests 
fail in kvm_unit_tests , 1821152:
ubuntu_lxc:(1821152): lxc-test-no-new-privs failed with Temporary failure 
resolving 'archive.ubuntu.com'
ubuntu_unionmount_overlayfs_suite:(1727290): ubuntu_unionmount_overlayfs_suite 
failed on Azure

** Tags added: regression-testing-passed

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

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

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-beta series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-candidate series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-edge series:
  Fix Released
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 verification-testing series:
  Confirmed
Status in linux-azure package in Ubuntu:
  Invalid
Status in linux-azure source package in Bionic:
  New

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

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

  derivatives: bug 1829178 (linux-azure-edge)

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1829180
  phase: Ready for Testing
  phase-changed: Tuesday, 28. May 2019 22:14 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
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/1829179/+subscriptions

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


[Kernel-packages] [Bug 1829179] Re: linux-azure: 4.18.0-1019.19~18.04.1 -proposed tracker

2019-05-31 Thread Ubuntu Kernel Bot
** Changed in: kernel-sru-workflow/regression-testing
   Status: Confirmed => Fix Released

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  derivatives: bug 1829178 (linux-azure-edge)
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1829180
  phase: Ready for Testing
  phase-changed: Tuesday, 28. May 2019 22:14 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   regression-testing: Ongoing -- testing in progress
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/1829179

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

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-beta series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-candidate series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-edge series:
  Fix Released
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 verification-testing series:
  Confirmed
Status in linux-azure package in Ubuntu:
  Invalid
Status in linux-azure source package in Bionic:
  New

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

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

  derivatives: bug 1829178 (linux-azure-edge)

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1829180
  phase: Ready for Testing
  phase-changed: Tuesday, 28. May 2019 22:14 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
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/1829179/+subscriptions

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


[Kernel-packages] [Bug 1796443] Re: HP EliteBook 745 G5 (Ryzen 2500U) fails to boot unless `mce=off` is set on command line

2019-05-31 Thread Jon Grimm
Just ran across this bug in LP.

Note: 60c8144afc28 is only masking what the real issue is; it's a real
bug, but the reason it's getting hit at all in this specific instance is
because of an AMD CPU erratum which is causing spurious MCEs early
enough to hit the bug this commit fixes.

However, while the crash is fixed, the thresholding interrupts are still
going to be coming in fast and furious, better to disable them on
affected CPUs as fixed by the following:

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

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

If the above 2 commits are in place, 60c8144afc28 becomes less critical,
as you should no longer hit that condition.

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

Title:
  HP EliteBook 745 G5 (Ryzen 2500U) fails to boot unless `mce=off` is
  set on command line

Status in Linux:
  Fix Released
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  My new Elitebook, with the latest bios 1.03.01, refuses to boot any
  kernel later than 4.10 unless mce=off is appended to the kernel
  command line.  As in, there are no kernel messages at all after grub
  (yes, quiet and splash were removed from the command line).  Perhaps
  it crashes before the efifb kicks in?

  System operates fine if mce=off is added to the kernel command line
  (and iommu=soft, but that's a separate issue, and fails with kernel
  output in that case).

  I opened upstream bug here :
  https://bugzilla.kernel.org/show_bug.cgi?id=201291

  I bisected the problem down to this commit (and the few before it,
  which also added extra MCE output, but didn't actually crash):

  18807ddb7f88d4ac3797302bafb18143d573e66f is the first bad commit
  commit 18807ddb7f88d4ac3797302bafb18143d573e66f
  Author: Yazen Ghannam 
  Date:   Tue Nov 15 15:13:53 2016 -0600

  x86/mce/AMD: Reset Threshold Limit after logging error

  The error count field in MCA_MISC does not get reset by hardware when the
  threshold has been reached. Software is expected to reset it. Currently,
  the threshold limit only gets reset during init or when a user writes to
  sysfs.

  If the user is not monitoring threshold interrupts and resetting
  the limit then the user will only see 1 interrupt when the limit is first
  hit. So if, for example, the limit is set to 10 then only 1 interrupt will
  be recorded after 10 errors even if 100 errors have occurred. The user may
  then assume that only 10 errors have occurred.

  There are threads online about this being related to the latest bios.
  The upstream bug has acpidump attached.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.18.0-8-generic 4.18.0-8.9
  ProcVersionSignature: Ubuntu 4.18.0-8.9-generic 4.18.7
  Uname: Linux 4.18.0-8-generic x86_64
  ApportVersion: 2.20.10-0ubuntu11
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  john   2015 F pulseaudio
   /dev/snd/pcmC1D0p:   john   2015 F...m pulseaudio
   /dev/snd/controlC0:  john   2015 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Oct  5 23:24:45 2018
  InstallationDate: Installed on 2018-09-30 (5 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Beta amd64 (20180927)
  Lsusb:
   Bus 005 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 004 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 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP EliteBook 745 G5
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-8-generic 
root=UUID=5cf73665-d2a3-4203-80fd-659faf1afea4 ro quiet splash iommu=soft 
mce=off
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-8-generic N/A
   linux-backports-modules-4.18.0-8-generic  N/A
   linux-firmware1.175
  RfKill:
   1: phy0: Wireless LAN
    Soft blocked: no
    Hard blocked: no
  SourcePackage: linux
  StagingDrivers: r8822be
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/26/2018
  dmi.bios.vendor: HP
  dmi.bios.version: Q81 Ver. 01.03.01
  dmi.board.name: 83D5
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 08.47.00
  dmi.chassis.asset.tag: 5CG838305Y
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.modalias: 

[Kernel-packages] [Bug 1806380] Re: linux-buildinfo: pull out ABI information into its own package

2019-05-31 Thread Kleber Sacilotto de Souza
Changed working as expected on the re-used BugLink applied to Disco.

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

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

Title:
  linux-buildinfo: pull out ABI information into its own package

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 Bionic:
  Fix Released
Status in linux source package in Cosmic:
  Fix Released
Status in linux source package in Disco:
  Fix Released

Bug description:
  We have an increasing amount of ABI information which is currently
  exposed via the primary binary packages.  Little to none of this is
  relevant to the end-user and does not deserve to use up space on their
  system.  Also the kernel developer who needs to update this data does
  not want to downloads 10s of Megabytes of binary packages to extract
  this information.  Pull it all out and generate all data that would
  require the actual binaries at kernel build time, package all of this
  information into a new linux-buildinfo package for consumption.  This
  package is not installed by default.

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

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


[Kernel-packages] [Bug 1829196] Re: linux-gcp: 4.15.0-1033.35~16.04.1 -proposed tracker

2019-05-31 Thread Ubuntu Kernel Bot
** Changed in: kernel-sru-workflow/verification-testing
   Status: Confirmed => Fix Released

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  derivatives: bug 1829847 (linux-gcp)
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1829200
- phase: Ready for Testing
- phase-changed: Tuesday, 28. May 2019 23:45 UTC
+ phase: Holding before Release
+ phase-changed: Friday, 31. May 2019 15:43 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
promote-to-updates: Pending -- Nvidia object not found -- 
current-driver-4.15.0-1033-gcp-amd64
-   verification-testing: Ongoing -- testing in progress

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

Title:
  linux-gcp: 4.15.0-1033.35~16.04.1 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-beta series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-candidate series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-edge series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-stable series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux-gcp package in Ubuntu:
  Invalid
Status in linux-gcp source package in Xenial:
  New

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

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

  derivatives: bug 1829847 (linux-gcp)

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1829200
  phase: Holding before Release
  phase-changed: Friday, 31. May 2019 15:43 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
promote-to-updates: Pending -- Nvidia object not found -- 
current-driver-4.15.0-1033-gcp-amd64

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

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


[Kernel-packages] [Bug 1829208] Re: linux-oracle: 4.15.0-1014.16~16.04.1 -proposed tracker

2019-05-31 Thread Ubuntu Kernel Bot
** Changed in: kernel-sru-workflow/verification-testing
   Status: Confirmed => Fix Released

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  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: 1829210
  phase: Ready for Testing
  phase-changed: Tuesday, 28. May 2019 23:46 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
regression-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-oracle in Ubuntu.
https://bugs.launchpad.net/bugs/1829208

Title:
  linux-oracle: 4.15.0-1014.16~16.04.1 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  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:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux-oracle package in Ubuntu:
  Invalid
Status in linux-oracle source package in Xenial:
  New

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  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: 1829210
  phase: Ready for Testing
  phase-changed: Tuesday, 28. May 2019 23:46 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
regression-testing: Ongoing -- testing in progress

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

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


[Kernel-packages] [Bug 1829213] Re: linux-azure: 4.15.0-1046.50~14.04.1 -proposed tracker

2019-05-31 Thread Ubuntu Kernel Bot
** Changed in: kernel-sru-workflow/verification-testing
   Status: Confirmed => Fix Released

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  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: 1829214
  phase: Ready for Testing
  phase-changed: Tuesday, 28. May 2019 23:46 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
regression-testing: Ongoing -- testing in progress
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/1829213

Title:
  linux-azure: 4.15.0-1046.50~14.04.1 -proposed tracker

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

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  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: 1829214
  phase: Ready for Testing
  phase-changed: Tuesday, 28. May 2019 23:46 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
regression-testing: Ongoing -- testing in progress
stakeholder-signoff: Pending -- waiting for signoff

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

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


[Kernel-packages] [Bug 1829200] Re: linux-gcp: 4.15.0-1033.35 -proposed tracker

2019-05-31 Thread Ubuntu Kernel Bot
** Changed in: kernel-sru-workflow/verification-testing
   Status: Confirmed => Fix Released

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  backports: bug 1829196 (xenial/linux-gcp)
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1829219
- phase: Ready for Testing
- phase-changed: Wednesday, 29. May 2019 09:39 UTC
+ phase: Holding before Release
+ phase-changed: Friday, 31. May 2019 15:37 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   verification-testing: Ongoing -- testing in progress
+   promote-to-updates: Holding -- cycle not ready to release

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

Title:
  linux-gcp: 4.15.0-1033.35 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-beta series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-candidate series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-edge series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-stable series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux-gcp package in Ubuntu:
  Invalid
Status in linux-gcp source package in Bionic:
  New

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

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

  backports: bug 1829196 (xenial/linux-gcp)

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1829219
  phase: Holding before Release
  phase-changed: Friday, 31. May 2019 15:37 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
promote-to-updates: Holding -- cycle not ready to release

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

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


[Kernel-packages] [Bug 1829194] Re: linux-aws: 4.15.0-1040.42 -proposed tracker

2019-05-31 Thread Ubuntu Kernel Bot
** Changed in: kernel-sru-workflow/verification-testing
   Status: Confirmed => Fix Released

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  backports: bug 1829192 (xenial/linux-aws-hwe)
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1829219
- phase: Ready for Testing
- phase-changed: Tuesday, 28. May 2019 23:40 UTC
+ phase: Holding before Release
+ phase-changed: Friday, 31. May 2019 15:37 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   verification-testing: Ongoing -- testing in progress
+   promote-to-updates: Holding -- cycle not ready to release

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

Title:
  linux-aws: 4.15.0-1040.42 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff 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:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-edge series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-stable series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux-aws package in Ubuntu:
  Invalid
Status in linux-aws source package in Bionic:
  New

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

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

  backports: bug 1829192 (xenial/linux-aws-hwe)

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1829219
  phase: Holding before Release
  phase-changed: Friday, 31. May 2019 15:37 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
promote-to-updates: Holding -- cycle not ready to release

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

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


[Kernel-packages] [Bug 1829189] Re: linux-snapdragon: 4.15.0-1054.58 -proposed tracker

2019-05-31 Thread Ubuntu Kernel Bot
** Changed in: kernel-sru-workflow/verification-testing
   Status: Confirmed => Fix Released

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  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: 1829219
- phase: Ready for Testing
- phase-changed: Wednesday, 29. May 2019 14:09 UTC
+ phase: Holding before Release
+ phase-changed: Friday, 31. May 2019 15:36 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   verification-testing: Ongoing -- testing in progress
+   promote-to-updates: Holding -- cycle not ready to release

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

Title:
  linux-snapdragon: 4.15.0-1054.58 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Fix Released
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow 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:
  Fix Released
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:
  Fix Released
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 verification-testing series:
  Fix Released
Status in linux-snapdragon package in Ubuntu:
  Invalid
Status in linux-snapdragon source package in Bionic:
  New

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  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: 1829219
  phase: Holding before Release
  phase-changed: Friday, 31. May 2019 15:36 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
promote-to-updates: Holding -- cycle not ready to release

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

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


[Kernel-packages] [Bug 1829187] Re: linux-raspi2: 4.15.0-1037.39 -proposed tracker

2019-05-31 Thread Ubuntu Kernel Bot
** Changed in: kernel-sru-workflow/verification-testing
   Status: Confirmed => Fix Released

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  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: 1829219
  phase: Ready for Testing
  phase-changed: Wednesday, 29. May 2019 07:39 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
+   promote-to-updates: Holding -- cycle not ready to release
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/1829187

Title:
  linux-raspi2: 4.15.0-1037.39 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Fix Released
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow 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:
  Fix Released
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 verification-testing series:
  Fix Released
Status in linux-raspi2 package in Ubuntu:
  Invalid
Status in linux-raspi2 source package in Bionic:
  New

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  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: 1829219
  phase: Ready for Testing
  phase-changed: Wednesday, 29. May 2019 07:39 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
promote-to-updates: Holding -- cycle not ready to release
snap-certification-testing: Ongoing -- testing in progress

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

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


[Kernel-packages] [Bug 1829204] Re: linux-kvm: 4.15.0-1035.35 -proposed tracker

2019-05-31 Thread Ubuntu Kernel Bot
** Changed in: kernel-sru-workflow/verification-testing
   Status: Confirmed => Fix Released

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  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: 1829219
- phase: Ready for Testing
- phase-changed: Tuesday, 28. May 2019 23:40 UTC
+ phase: Holding before Release
+ phase-changed: Friday, 31. May 2019 15:38 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   verification-testing: Ongoing -- testing in progress
+   promote-to-updates: Holding -- cycle not ready to release

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

Title:
  linux-kvm: 4.15.0-1035.35 -proposed tracker

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

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  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: 1829219
  phase: Holding before Release
  phase-changed: Friday, 31. May 2019 15:38 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
promote-to-updates: Holding -- cycle not ready to release

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

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


[Kernel-packages] [Bug 1829191] Re: linux-oem: 4.15.0-1039.44 -proposed tracker

2019-05-31 Thread Ubuntu Kernel Bot
** Changed in: kernel-sru-workflow/verification-testing
   Status: Confirmed => Fix Released

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  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: 1829219
- phase: Ready for Testing
- phase-changed: Friday, 31. May 2019 11:36 UTC
+ phase: Holding before Release
+ phase-changed: Friday, 31. May 2019 15:37 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   verification-testing: Ongoing -- testing in progress
+   promote-to-updates: Holding -- cycle not ready to release

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

Title:
  linux-oem: 4.15.0-1039.44 -proposed tracker

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

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  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: 1829219
  phase: Holding before Release
  phase-changed: Friday, 31. May 2019 15:37 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
promote-to-updates: Holding -- cycle not ready to release

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

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


[Kernel-packages] [Bug 1829211] Re: linux-fips: 4.15.0-1008.9 -proposed tracker

2019-05-31 Thread Ubuntu Kernel Bot
** Changed in: kernel-sru-workflow/verification-testing
   Status: Confirmed => Fix Released

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  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: 1829219
  phase: Ready for Testing
  phase-changed: Thursday, 23. May 2019 20:11 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-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/1829211

Title:
  linux-fips: 4.15.0-1008.9 -proposed tracker

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

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  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: 1829219
  phase: Ready for Testing
  phase-changed: Thursday, 23. May 2019 20:11 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Ongoing -- testing in progress

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

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


[Kernel-packages] [Bug 1829206] Re: linux-ibm-gt: 4.15.0-1022.24 -proposed tracker

2019-05-31 Thread Ubuntu Kernel Bot
** Changed in: kernel-sru-workflow/verification-testing
   Status: Confirmed => Fix Released

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  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: 1829219
  phase: Ready for Testing
  phase-changed: Tuesday, 28. May 2019 23:41 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Ongoing -- testing in progress
regression-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/1829206

Title:
  linux-ibm-gt: 4.15.0-1022.24 -proposed tracker

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

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  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: 1829219
  phase: Ready for Testing
  phase-changed: Tuesday, 28. May 2019 23:41 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Ongoing -- testing in progress
regression-testing: Ongoing -- testing in progress

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

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


[Kernel-packages] [Bug 1829210] Re: linux-oracle: 4.15.0-1014.16 -proposed tracker

2019-05-31 Thread Ubuntu Kernel Bot
** Changed in: kernel-sru-workflow/verification-testing
   Status: Confirmed => Fix Released

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  backports: bug 1829208 (xenial/linux-oracle)
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1829219
  phase: Ready for Testing
  phase-changed: Tuesday, 28. May 2019 23:41 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
regression-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-oracle in Ubuntu.
https://bugs.launchpad.net/bugs/1829210

Title:
  linux-oracle: 4.15.0-1014.16 -proposed tracker

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

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

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

  backports: bug 1829208 (xenial/linux-oracle)

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1829219
  phase: Ready for Testing
  phase-changed: Tuesday, 28. May 2019 23:41 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
regression-testing: Ongoing -- testing in progress

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

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


[Kernel-packages] [Bug 1829214] Re: linux-azure: 4.15.0-1046.50 -proposed tracker

2019-05-31 Thread Ubuntu Kernel Bot
** Changed in: kernel-sru-workflow/verification-testing
   Status: Confirmed => Fix Released

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  backports: bug 1829213 (trusty/linux-azure)
  derivatives: bug 1829212 (linux-azure-edge)
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1829219
  phase: Ready for Testing
  phase-changed: Tuesday, 28. May 2019 23:42 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
regression-testing: Ongoing -- testing in progress
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/1829214

Title:
  linux-azure: 4.15.0-1046.50 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff 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:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-edge series:
  Fix Released
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 verification-testing series:
  Fix Released
Status in linux-azure package in Ubuntu:
  Invalid
Status in linux-azure source package in Xenial:
  New

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

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

  backports: bug 1829213 (trusty/linux-azure)
  derivatives: bug 1829212 (linux-azure-edge)

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1829219
  phase: Ready for Testing
  phase-changed: Tuesday, 28. May 2019 23:42 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
regression-testing: Ongoing -- testing in progress
stakeholder-signoff: Pending -- waiting for signoff

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

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


[Kernel-packages] [Bug 1829219] Re: linux: 4.15.0-51.55 -proposed tracker

2019-05-31 Thread Ubuntu Kernel Bot
** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  backports: bug 1829214 (xenial/linux-azure), bug 1829216 (xenial/linux-hwe)
  derivatives: bug 1829187 (linux-raspi2), bug 1829189 (linux-snapdragon), bug 
1829191 (linux-oem), bug 1829194 (linux-aws), bug 1829200 (linux-gcp), bug 
1829202 (linux-gke-4.15), bug 1829204 (linux-kvm), bug 1829206 (linux-ibm-gt), 
bug 1829210 (linux-oracle), bug 1829211 (linux-fips), bug 1829846 (linux)
  
  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
- phase: Ready for Testing
- phase-changed: Friday, 31. May 2019 14:31 UTC
+ phase: Holding before Release
+ phase-changed: Friday, 31. May 2019 15:31 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   verification-testing: Ongoing -- testing in progress
+   promote-to-updates: Holding -- cycle not ready to release

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

Title:
  linux: 4.15.0-51.55 -proposed tracker

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

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

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

  backports: bug 1829214 (xenial/linux-azure), bug 1829216 (xenial/linux-hwe)
  derivatives: bug 1829187 (linux-raspi2), bug 1829189 (linux-snapdragon), bug 
1829191 (linux-oem), bug 1829194 (linux-aws), bug 1829200 (linux-gcp), bug 
1829202 (linux-gke-4.15), bug 1829204 (linux-kvm), bug 1829206 (linux-ibm-gt), 
bug 1829210 (linux-oracle), bug 1829211 (linux-fips), bug 1829846 (linux)

  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
  phase: Holding before Release
  phase-changed: Friday, 31. May 2019 15:31 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
promote-to-updates: Holding -- cycle not ready to release

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

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


[Kernel-packages] [Bug 1827880] Re: bionic/linux: completely remove snapdragon files from sources

2019-05-31 Thread Kleber Sacilotto de Souza
** 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/1827880

Title:
  bionic/linux: completely remove snapdragon files from sources

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Fix Committed

Bug description:
  [Impact]

  As requested by bug 1820868, we have split bionic/linux-snapdragon to
  its own source package and own git branch for better maintainability.
  Functionally that split was complete, however some leftover files
  where not removed from the sources leaving some dead files on the
  tree.

  [Fix]

  Sauce patch to remove all the files that were previously used to
  produce the snapdragon binaries from the linux master source.

  [Test Case]

  Compile test bionic/linux source and verify that nothing breaks.

  [Regression potential]

  Minimum. The fix is to remove files that are not being used anymore.

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

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


[Kernel-packages] [Bug 1829219] Re: linux: 4.15.0-51.55 -proposed tracker

2019-05-31 Thread Kleber Sacilotto de Souza
Verification tests completed successfully, with exception of:
- bug 1787775

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

Title:
  linux: 4.15.0-51.55 -proposed tracker

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

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

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

  backports: bug 1829214 (xenial/linux-azure), bug 1829216 (xenial/linux-hwe)
  derivatives: bug 1829187 (linux-raspi2), bug 1829189 (linux-snapdragon), bug 
1829191 (linux-oem), bug 1829194 (linux-aws), bug 1829200 (linux-gcp), bug 
1829202 (linux-gke-4.15), bug 1829204 (linux-kvm), bug 1829206 (linux-ibm-gt), 
bug 1829210 (linux-oracle), bug 1829211 (linux-fips), bug 1829846 (linux)

  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
  phase: Holding before Release
  phase-changed: Friday, 31. May 2019 15:31 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
promote-to-updates: Holding -- cycle not ready to release

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

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


[Kernel-packages] [Bug 1831232] Re: Ubuntu 18.04 won't boot - failed to connect to lvmetad

2019-05-31 Thread Raphael Mankin
** Attachment added: "Photo of my screen during the boot."
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1831232/+attachment/5268075/+files/IMG_20190531_161254.jpg

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

Title:
  Ubuntu 18.04 won't boot - failed to connect to lvmetad

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This bug report relates to a machine running 18.04, not the one I am
  submitting the report from.

  On 30 May The Software Updater prompted me to update. Included in the
  update were initramfs components. I now cannot boot the machine.

  After decrypting the root file system, instead of being prompted for
  the pass-phrase to decrypt the swap, I get the message "cannot connect
  to lvmetad: falling back to device scanning". This repeats for a while
  until I am dropped into a recovery shell of some sort from which I
  cannot access the root disk.

  Blocker. My machine is unusable.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-generic 4.15.0.48.50
  ProcVersionSignature: Ubuntu 4.15.0-48.51-generic 4.15.18
  Uname: Linux 4.15.0-48-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  gdm2433 F pulseaudio
raph   8920 F pulseaudio
   /dev/snd/controlC0:  gdm2433 F pulseaudio
  Date: Fri May 31 12:08:33 2019
  HibernationDevice: RESUME=UUID=2538baa4-d43e-4876-8d94-dd3221894bac
  InstallationDate: Installed on 2018-02-09 (475 days ago)
  InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: LENOVO 20CJS0UU00
  ProcEnviron:
   LANGUAGE=en_GB:en
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-48-generic 
root=/dev/mapper/xubuntu--vg-root ro quiet splash vt.handoff=1
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-48-generic N/A
   linux-backports-modules-4.15.0-48-generic  N/A
   linux-firmware 1.173.5
  SourcePackage: linux
  UpgradeStatus: Upgraded to bionic on 2018-09-12 (260 days ago)
  dmi.bios.date: 09/13/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N11ET42W (1.18 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20CJS0UU00
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 WIN
  dmi.chassis.asset.tag: R90G3N7R
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN11ET42W(1.18):bd09/13/2017:svnLENOVO:pn20CJS0UU00:pvrThinkPadT550:rvnLENOVO:rn20CJS0UU00:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T550
  dmi.product.name: 20CJS0UU00
  dmi.product.version: ThinkPad T550
  dmi.sys.vendor: LENOVO

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

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


[Kernel-packages] [Bug 1831254] [NEW] [linux-azure] XDP generic fixes

2019-05-31 Thread Joseph Salisbury
Public bug reported:

These two commits were needed to to get XDP working on Azure.

This set of patches came about while investigating and XDP generic issue
on Azure. The split brain nature of the accelerated networking exposed
issues with the stack device model.

The following two commits are currently in linux-next and were tested to
resolve this issue:

996ed04741467 ("netvsc: unshare skb in VF rx handler")
458bf2f224f04 ("net: core: support XDP generic on stacked devices.")

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

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

Title:
  [linux-azure] XDP generic fixes

Status in linux-azure package in Ubuntu:
  New

Bug description:
  These two commits were needed to to get XDP working on Azure.

  This set of patches came about while investigating and XDP generic
  issue on Azure. The split brain nature of the accelerated networking
  exposed issues with the stack device model.

  The following two commits are currently in linux-next and were tested
  to resolve this issue:

  996ed04741467 ("netvsc: unshare skb in VF rx handler")
  458bf2f224f04 ("net: core: support XDP generic on stacked devices.")

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

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


[Kernel-packages] [Bug 1830890] Re: glibc 2.23-0ubuntu11 ADT test failure with linux 4.4.0-149.175

2019-05-31 Thread Kleber Sacilotto de Souza
ADT glibc testcases are now successful:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/i386/g/glibc/20190530_100415_f7174@/log.gz

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

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

Title:
  glibc 2.23-0ubuntu11 ADT test failure with linux 4.4.0-149.175

Status in glibc package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Invalid
Status in glibc source package in Xenial:
  Invalid
Status in linux source package in Xenial:
  Fix Committed

Bug description:
  [Impact]
  Some glibc testcases are regressing on i386 after the following commit was 
applied to xenial/linux as part of upstream stable update 4.4.179:

  commit 379d98ddf41344273d9718556f761420f4dc80b3
  Author: Alistair Strachan 
  Date: Fri Aug 3 10:39:31 2018 -0700

  x86: vdso: Use $LD instead of $CC to link

  which accidentally broke unwinding from userspace, because ld would
  strip the .eh_frame sections when linking.

  Test logs:
  i386: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/i386/g/glibc/20190528_085308_d03ca@/log.gz

  [Fix]
  The following commit fixes the issue:

  commit cd01544a268ad8ee5b1dfe42c4393f1095f86879
  Author: Alistair Strachan 
  Date: Fri Dec 14 14:36:37 2018 -0800

  x86/vdso: Pass --eh-frame-hdr to the linker

  It was applied to 4.4.180, but we need to apply it before otherwise
  xenial/linux will be released with a regression.

  [Test]
  ADT tests for glibc.

  [Regression Potential]
  Low. One line patch to Makefile which fixes a known regression.

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

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


[Kernel-packages] [Bug 1829219] Re: linux: 4.15.0-51.55 -proposed tracker

2019-05-31 Thread Ubuntu Kernel Bot
** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  backports: bug 1829214 (xenial/linux-azure), bug 1829216 (xenial/linux-hwe)
  derivatives: bug 1829187 (linux-raspi2), bug 1829189 (linux-snapdragon), bug 
1829191 (linux-oem), bug 1829194 (linux-aws), bug 1829200 (linux-gcp), bug 
1829202 (linux-gke-4.15), bug 1829204 (linux-kvm), bug 1829206 (linux-ibm-gt), 
bug 1829210 (linux-oracle), bug 1829211 (linux-fips), bug 1829846 (linux)
  
  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
- phase: Testing
- phase-changed: Thursday, 16. May 2019 15:03 UTC
+ phase: Ready for Testing
+ phase-changed: Friday, 31. May 2019 14:31 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   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/1829219

Title:
  linux: 4.15.0-51.55 -proposed tracker

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

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

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

  backports: bug 1829214 (xenial/linux-azure), bug 1829216 (xenial/linux-hwe)
  derivatives: bug 1829187 (linux-raspi2), bug 1829189 (linux-snapdragon), bug 
1829191 (linux-oem), bug 1829194 (linux-aws), bug 1829200 (linux-gcp), bug 
1829202 (linux-gke-4.15), bug 1829204 (linux-kvm), bug 1829206 (linux-ibm-gt), 
bug 1829210 (linux-oracle), bug 1829211 (linux-fips), bug 1829846 (linux)

  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
  phase: Ready for Testing
  phase-changed: Friday, 31. May 2019 14:31 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
verification-testing: Ongoing -- testing in progress

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

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


[Kernel-packages] [Bug 1829219] Re: linux: 4.15.0-51.55 -proposed tracker

2019-05-31 Thread Taihsiang Ho
Hardware Certification have completed testing this -proposed kernel. No
regressions were observed, results are available here:
http://people.canonical.com/~hwcert/sru-testing/bionic/4.15.0-51.55
/bionic-proposed-published.html

** Tags added: certification-testing-passed

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

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

Title:
  linux: 4.15.0-51.55 -proposed tracker

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

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

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

  backports: bug 1829214 (xenial/linux-azure), bug 1829216 (xenial/linux-hwe)
  derivatives: bug 1829187 (linux-raspi2), bug 1829189 (linux-snapdragon), bug 
1829191 (linux-oem), bug 1829194 (linux-aws), bug 1829200 (linux-gcp), bug 
1829202 (linux-gke-4.15), bug 1829204 (linux-kvm), bug 1829206 (linux-ibm-gt), 
bug 1829210 (linux-oracle), bug 1829211 (linux-fips), bug 1829846 (linux)

  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
  phase: Ready for Testing
  phase-changed: Friday, 31. May 2019 14:31 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
verification-testing: Ongoing -- testing in progress

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

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


[Kernel-packages] [Bug 1830905] Re: Nvidia RTX 2060 USB bus timeouts cause ~30s delay in boot

2019-05-31 Thread Dan Watkins
Hi Kai-Heng,

As an extra data point, when I attempted to boot the latest mainline
kernel for bug 1830910, it didn't fully boot but it did get far enough
to display the "kernel: xhci_hcd :07:00.2: can't setup: -110"
messages.  So the mainline kernel doesn't address this issue either.


Thanks!

Dan

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

Title:
  Nvidia RTX 2060 USB bus timeouts cause ~30s delay in boot

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  From dmesg:

  [0.132667] kernel: pci :07:00.1: Linked as a consumer to :07:00.0
  [5.882727] kernel: pci :07:00.2: xHCI HW not ready after 5 sec (HC 
bug?) status = 0x801
  [5.882781] kernel: pci :07:00.2: quirk_usb_early_handoff+0x0/0x6a6 
took 5615333 usecs

  

  [9.984204] kernel: usb 1-7: new full-speed USB device number 4 using 
xhci_hcd
  [   10.308689] kernel: usb 1-7: New USB device found, idVendor=8087, 
idProduct=0a2b, bcdDevice= 0.10
  [   10.308690] kernel: usb 1-7: New USB device strings: Mfr=0, Product=0, 
SerialNumber=0
  [   34.654721] kernel: xhci_hcd :07:00.2: can't setup: -110
  [   34.654730] kernel: xhci_hcd :07:00.2: USB bus 3 deregistered
  [   34.654769] kernel: xhci_hcd :07:00.2: init :07:00.2 fail, -110
  [   34.654771] kernel: xhci_hcd: probe of :07:00.2 failed with error -110

  $ lspci -k -s :07:00
  07:00.0 VGA compatible controller: NVIDIA Corporation TU106 [GeForce RTX 2060 
Rev. A] (rev a1)
Subsystem: Gigabyte Technology Co., Ltd TU106
Kernel driver in use: nvidia
Kernel modules: nvidiafb, nouveau, nvidia_drm, nvidia
  07:00.1 Audio device: NVIDIA Corporation TU106 High Definition Audio 
Controller (rev a1)
Subsystem: Gigabyte Technology Co., Ltd TU106 High Definition Audio 
Controller
Kernel driver in use: snd_hda_intel
Kernel modules: snd_hda_intel
  07:00.2 USB controller: NVIDIA Corporation TU106 USB 3.1 Host Controller (rev 
a1)
Subsystem: Gigabyte Technology Co., Ltd TU106 USB 3.1 Host Controller
  07:00.3 Serial bus controller [0c80]: NVIDIA Corporation TU106 USB Type-C 
Port Policy Controller (rev a1)
Subsystem: Gigabyte Technology Co., Ltd TU106 USB Type-C Port Policy 
Controller
Kernel driver in use: nvidia-gpu
Kernel modules: i2c_nvidia_gpu

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: linux-image-5.0.0-15-generic 5.0.0-15.16
  ProcVersionSignature: Ubuntu 5.0.0-15.16-generic 5.0.6
  Uname: Linux 5.0.0-15-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  daniel 4470 F pulseaudio
   /dev/snd/controlC1:  daniel 4470 F pulseaudio
   /dev/snd/controlC2:  daniel 4470 F pulseaudio
  CurrentDesktop: i3
  Date: Wed May 29 09:36:51 2019
  InstallationDate: Installed on 2019-05-07 (21 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  MachineType: Gigabyte Technology Co., Ltd. B450M DS3H
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-15-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash 
resume=UUID=73909634-a75d-42c9-8f66-a69138690756 vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-15-generic N/A
   linux-backports-modules-5.0.0-15-generic  N/A
   linux-firmware1.179
  SourcePackage: linux
  UpgradeStatus: Upgraded to eoan on 2019-05-08 (20 days ago)
  dmi.bios.date: 01/25/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F4
  dmi.board.asset.tag: Default string
  dmi.board.name: B450M DS3H-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF4:bd01/25/2019:svnGigabyteTechnologyCo.,Ltd.:pnB450MDS3H:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB450MDS3H-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: B450M DS3H
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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


[Kernel-packages] [Bug 1830910] Re: Kernel traces in ieee80211 after "Hardware restart was requested"

2019-05-31 Thread Dan Watkins
Hi Kai-Heng,

Thanks for the next steps!  I've just installed the latest mainline
kernel and it failed to boot.  I _didn't_ attempt the new firmware at
the same time, would that have made a difference?


Thanks,

Dan

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

Title:
  Kernel traces in ieee80211 after "Hardware restart was requested"

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  When using my desktop normally, I experienced a hard lock-up.  On
  reboot, I was able to examine the journal to find a whole bunch of
  traces (attached in journal-traces).

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: linux-image-5.0.0-15-generic 5.0.0-15.16
  ProcVersionSignature: Ubuntu 5.0.0-15.16-generic 5.0.6
  Uname: Linux 5.0.0-15-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  daniel 4111 F pulseaudio
   /dev/snd/controlC1:  daniel 4111 F pulseaudio
   /dev/snd/controlC2:  daniel 4111 F pulseaudio
  CurrentDesktop: i3
  Date: Wed May 29 10:12:40 2019
  InstallationDate: Installed on 2019-05-07 (21 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  MachineType: Gigabyte Technology Co., Ltd. B450M DS3H
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-15-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash 
resume=UUID=73909634-a75d-42c9-8f66-a69138690756 vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-15-generic N/A
   linux-backports-modules-5.0.0-15-generic  N/A
   linux-firmware1.179
  SourcePackage: linux
  UpgradeStatus: Upgraded to eoan on 2019-05-08 (20 days ago)
  dmi.bios.date: 01/25/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F4
  dmi.board.asset.tag: Default string
  dmi.board.name: B450M DS3H-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF4:bd01/25/2019:svnGigabyteTechnologyCo.,Ltd.:pnB450MDS3H:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB450MDS3H-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: B450M DS3H
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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


[Kernel-packages] [Bug 1830350] Re: System freezes repeatedly for several seconds; wifi driver related errors

2019-05-31 Thread Frank van Wensveen
Sorry, previous post was repeated following a browser crash / session
restore. My bad.

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

Title:
  System freezes repeatedly for several seconds; wifi driver related
  errors

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

Bug description:
  I updated my system about a month ago (Fri 26 April 2019). This was
  the first update in several weeks and installed fresh versions of a
  whole truck load of applications including a kernel update. Since this
  latest bunch of updates the system freezes for a few seconds at
  regular intervals. Not fatal, but very annoying.

  Output from "journalctl -f" shows the following errors occurring at
  the same time as these freezes:

  May 24 10:31:18 dellfvw wpa_supplicant[1078]: wlp3s0: CTRL-EVENT-SCAN-FAILED 
ret=-110
  May 24 10:31:18 dellfvw kernel: ath10k_pci :03:00.0: failed to receive 
scan abortion completion: timed out
  May 24 10:31:18 dellfvw kernel: ath10k_pci :03:00.0: failed to stop scan: 
-110
  May 24 10:31:18 dellfvw kernel: ath10k_pci :03:00.0: failed to start hw 
scan: -110

  Corresponding lines in /var/log/syslog:

  May 24 10:29:16 dellfvw avahi-daemon[1053]: Registering new address record 
for fe80::424:c75b:2a2d:52e2 on wlp3s0.*.
  May 24 10:29:55 dellfvw avahi-daemon[1053]: Withdrawing address record for 
fe80::424:c75b:2a2d:52e2 on wlp3s0.
  May 24 10:31:18 dellfvw wpa_supplicant[1078]: wlp3s0: CTRL-EVENT-SCAN-FAILED 
ret=-110
  May 24 10:31:18 dellfvw kernel: [45569.661175] ath10k_pci :03:00.0: 
failed to receive scan abortion completion: timed out
  May 24 10:31:18 dellfvw kernel: [45569.661183] ath10k_pci :03:00.0: 
failed to stop scan: -110
  May 24 10:31:18 dellfvw kernel: [45569.661187] ath10k_pci :03:00.0: 
failed to start hw scan: -110

  I do note the interval between the avahi-daemon entry and the
  subsequent errors related to the wireless network interface, but the
  former precede the latter consistently in syslog, suggesting they may
  be related, which is why I'm including it in this report.

  The freezes last a few seconds. Keyboard input is preserved at this
  time and typed input appears after the freeze is resolved. Mouse
  cursor continues to move during freezes but mouse clicks are only
  processed after the freeze is resolved, i.e. the result of the mouse
  click is suspended (e.g. buffered) until the system becomes responsive
  again. For example, clicking on a window during the freeze will focus
  that window after the freeze has been resolved.

  The system is a Dell Inspiron 15 3576. Relevant output of lspci -nnk:

  03:00.0 Network controller [0280]: Qualcomm Atheros QCA9377 802.11ac
  Wireless Network Adapter [168c:0042] (rev 31)

  Output of lsb_release -rd:
  Description:  Ubuntu 18.04.2 LTS
  Release:  18.04

  Output of uname -a:
  Linux dellfvw 4.15.0-50-generic #54-Ubuntu SMP Mon May 6 18:46:08 UTC 2019 
x86_64 x86_64 x86_64 GNU/Linux

  As already said, this is a new issue that has began occurring only
  after the recent batch of updates that included a kernel update. I
  reported the bug (maybe in the wrong place) but so far I have received
  no response. I've lived with this for a month or so hoping that
  further updates would fix the problem but it still persists.
  Installing the latest firmware update (14 Mar 2019) has no effect. No
  other changes were made to either hardware or OS configuration.

  Logfile snippets attached.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  frankvw1989 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 18.04
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=7d4169aa-136e-4eac-bb87-bb1b63b0bb27
  InstallationDate: Installed on 2018-05-10 (379 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: Dell Inc. Inspiron 3576
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-50-generic 
root=UUID=0ce4cd7e-e0fd-4fe0-83fc-9f845405ab62 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-50.54-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-50-generic N/A
   linux-backports-modules-4.15.0-50-generic  N/A
   linux-firmware 1.173.6
  Tags:  bionic
  Uname: Linux 4.15.0-50-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip disk lpadmin plugdev sambashare sudo users vboxusers
  _MarkForUpload: True
  dmi.bios.date: 01/16/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.7.0
  dmi.board.name: 0K83NX
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  

[Kernel-packages] [Bug 1830350] Re: System freezes repeatedly for several seconds; wifi driver related errors

2019-05-31 Thread Frank van Wensveen
@Kai-Heng Feng: I will do that.

However, I'm deadlined right now and this is my production machine, so
it'll have to wait for the paying job to be dealt with (probably this
weekend). Two questions, though:

1. The latest linux-firmware that you directed me to (linux-
firmware-20190514.tar.gz) is obviously intended for those who know what
they're doing. It is just a matter of "make install"? Because pretty
much all that does is copy the contents of the tarball to /lib/firmware
and I don't think that's enough.

2. Can I simply install:
linux-image-unsigned-5.2.0-050200rc2-generic_5.2.0-050200rc2.201905262130_amd64.deb
linux-modules-5.2.0-050200rc2-generic_5.2.0-050200rc2.201905262130_amd64.deb
linux-headers-5.2.0-050200rc2-generic_5.2.0-050200rc2.201905262130_amd64.deb
or are there other dependencies as well that I need to be aware of / deal with?

(As you will probably have understood by now I've little or no
experience with nightly builds, interim development releases and/or
other Linux development related issues.)

Please advise. Thank you!

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

Title:
  System freezes repeatedly for several seconds; wifi driver related
  errors

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

Bug description:
  I updated my system about a month ago (Fri 26 April 2019). This was
  the first update in several weeks and installed fresh versions of a
  whole truck load of applications including a kernel update. Since this
  latest bunch of updates the system freezes for a few seconds at
  regular intervals. Not fatal, but very annoying.

  Output from "journalctl -f" shows the following errors occurring at
  the same time as these freezes:

  May 24 10:31:18 dellfvw wpa_supplicant[1078]: wlp3s0: CTRL-EVENT-SCAN-FAILED 
ret=-110
  May 24 10:31:18 dellfvw kernel: ath10k_pci :03:00.0: failed to receive 
scan abortion completion: timed out
  May 24 10:31:18 dellfvw kernel: ath10k_pci :03:00.0: failed to stop scan: 
-110
  May 24 10:31:18 dellfvw kernel: ath10k_pci :03:00.0: failed to start hw 
scan: -110

  Corresponding lines in /var/log/syslog:

  May 24 10:29:16 dellfvw avahi-daemon[1053]: Registering new address record 
for fe80::424:c75b:2a2d:52e2 on wlp3s0.*.
  May 24 10:29:55 dellfvw avahi-daemon[1053]: Withdrawing address record for 
fe80::424:c75b:2a2d:52e2 on wlp3s0.
  May 24 10:31:18 dellfvw wpa_supplicant[1078]: wlp3s0: CTRL-EVENT-SCAN-FAILED 
ret=-110
  May 24 10:31:18 dellfvw kernel: [45569.661175] ath10k_pci :03:00.0: 
failed to receive scan abortion completion: timed out
  May 24 10:31:18 dellfvw kernel: [45569.661183] ath10k_pci :03:00.0: 
failed to stop scan: -110
  May 24 10:31:18 dellfvw kernel: [45569.661187] ath10k_pci :03:00.0: 
failed to start hw scan: -110

  I do note the interval between the avahi-daemon entry and the
  subsequent errors related to the wireless network interface, but the
  former precede the latter consistently in syslog, suggesting they may
  be related, which is why I'm including it in this report.

  The freezes last a few seconds. Keyboard input is preserved at this
  time and typed input appears after the freeze is resolved. Mouse
  cursor continues to move during freezes but mouse clicks are only
  processed after the freeze is resolved, i.e. the result of the mouse
  click is suspended (e.g. buffered) until the system becomes responsive
  again. For example, clicking on a window during the freeze will focus
  that window after the freeze has been resolved.

  The system is a Dell Inspiron 15 3576. Relevant output of lspci -nnk:

  03:00.0 Network controller [0280]: Qualcomm Atheros QCA9377 802.11ac
  Wireless Network Adapter [168c:0042] (rev 31)

  Output of lsb_release -rd:
  Description:  Ubuntu 18.04.2 LTS
  Release:  18.04

  Output of uname -a:
  Linux dellfvw 4.15.0-50-generic #54-Ubuntu SMP Mon May 6 18:46:08 UTC 2019 
x86_64 x86_64 x86_64 GNU/Linux

  As already said, this is a new issue that has began occurring only
  after the recent batch of updates that included a kernel update. I
  reported the bug (maybe in the wrong place) but so far I have received
  no response. I've lived with this for a month or so hoping that
  further updates would fix the problem but it still persists.
  Installing the latest firmware update (14 Mar 2019) has no effect. No
  other changes were made to either hardware or OS configuration.

  Logfile snippets attached.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  frankvw1989 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 18.04
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=7d4169aa-136e-4eac-bb87-bb1b63b0bb27
  InstallationDate: Installed on 2018-05-10 

[Kernel-packages] [Bug 1830905] Re: Nvidia RTX 2060 USB bus timeouts cause ~30s delay in boot

2019-05-31 Thread Dan Watkins
Hi Kai-Heng,

Thanks for the test kernel!  Unfortunately, it doesn't appear to have
changed the behaviour. :(

```
$ uname -a
Linux surprise 5.0.0-16-generic #17~lp1830905 SMP Fri May 31 13:39:26 CST 2019 
x86_64 x86_64 x86_64 GNU/Linux

$ grep :07:00.2 /var/log/dmesg
[0.086533] kernel: pci :07:00.2: [10de:1ada] type 00 class 0x0c0330
[0.086556] kernel: pci :07:00.2: reg 0x10: [mem 0xf200-0xf203 
64bit pref]
[0.086576] kernel: pci :07:00.2: reg 0x1c: [mem 0xf204-0xf204 
64bit pref]
[0.086639] kernel: pci :07:00.2: PME# supported from D0 D3hot
[5.878588] kernel: pci :07:00.2: xHCI HW not ready after 5 sec (HC 
bug?) status = 0x801
[5.878636] kernel: pci :07:00.2: quirk_usb_early_handoff+0x0/0x6a0 took 
5611519 usecs
[6.542191] kernel: iommu: Adding device :07:00.2 to group 15
[8.682608] kernel: xhci_hcd :07:00.2: xHCI Host Controller
[8.682611] kernel: xhci_hcd :07:00.2: new USB bus registered, assigned 
bus number 3
[   34.483186] kernel: xhci_hcd :07:00.2: can't setup: -110
[   34.483204] kernel: xhci_hcd :07:00.2: USB bus 3 deregistered
[   34.483250] kernel: xhci_hcd :07:00.2: init :07:00.2 fail, -110
[   34.483253] kernel: xhci_hcd: probe of :07:00.2 failed with error -110
```


Cheers,

Dan

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

Title:
  Nvidia RTX 2060 USB bus timeouts cause ~30s delay in boot

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  From dmesg:

  [0.132667] kernel: pci :07:00.1: Linked as a consumer to :07:00.0
  [5.882727] kernel: pci :07:00.2: xHCI HW not ready after 5 sec (HC 
bug?) status = 0x801
  [5.882781] kernel: pci :07:00.2: quirk_usb_early_handoff+0x0/0x6a6 
took 5615333 usecs

  

  [9.984204] kernel: usb 1-7: new full-speed USB device number 4 using 
xhci_hcd
  [   10.308689] kernel: usb 1-7: New USB device found, idVendor=8087, 
idProduct=0a2b, bcdDevice= 0.10
  [   10.308690] kernel: usb 1-7: New USB device strings: Mfr=0, Product=0, 
SerialNumber=0
  [   34.654721] kernel: xhci_hcd :07:00.2: can't setup: -110
  [   34.654730] kernel: xhci_hcd :07:00.2: USB bus 3 deregistered
  [   34.654769] kernel: xhci_hcd :07:00.2: init :07:00.2 fail, -110
  [   34.654771] kernel: xhci_hcd: probe of :07:00.2 failed with error -110

  $ lspci -k -s :07:00
  07:00.0 VGA compatible controller: NVIDIA Corporation TU106 [GeForce RTX 2060 
Rev. A] (rev a1)
Subsystem: Gigabyte Technology Co., Ltd TU106
Kernel driver in use: nvidia
Kernel modules: nvidiafb, nouveau, nvidia_drm, nvidia
  07:00.1 Audio device: NVIDIA Corporation TU106 High Definition Audio 
Controller (rev a1)
Subsystem: Gigabyte Technology Co., Ltd TU106 High Definition Audio 
Controller
Kernel driver in use: snd_hda_intel
Kernel modules: snd_hda_intel
  07:00.2 USB controller: NVIDIA Corporation TU106 USB 3.1 Host Controller (rev 
a1)
Subsystem: Gigabyte Technology Co., Ltd TU106 USB 3.1 Host Controller
  07:00.3 Serial bus controller [0c80]: NVIDIA Corporation TU106 USB Type-C 
Port Policy Controller (rev a1)
Subsystem: Gigabyte Technology Co., Ltd TU106 USB Type-C Port Policy 
Controller
Kernel driver in use: nvidia-gpu
Kernel modules: i2c_nvidia_gpu

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: linux-image-5.0.0-15-generic 5.0.0-15.16
  ProcVersionSignature: Ubuntu 5.0.0-15.16-generic 5.0.6
  Uname: Linux 5.0.0-15-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  daniel 4470 F pulseaudio
   /dev/snd/controlC1:  daniel 4470 F pulseaudio
   /dev/snd/controlC2:  daniel 4470 F pulseaudio
  CurrentDesktop: i3
  Date: Wed May 29 09:36:51 2019
  InstallationDate: Installed on 2019-05-07 (21 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  MachineType: Gigabyte Technology Co., Ltd. B450M DS3H
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-15-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash 
resume=UUID=73909634-a75d-42c9-8f66-a69138690756 vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-15-generic N/A
   linux-backports-modules-5.0.0-15-generic  N/A
   linux-firmware1.179
  SourcePackage: linux
  UpgradeStatus: Upgraded to eoan on 2019-05-08 (20 days ago)
  dmi.bios.date: 01/25/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F4
  dmi.board.asset.tag: Default string
  dmi.board.name: B450M DS3H-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  

[Kernel-packages] [Bug 1814373] Re: storage / luks / dmsetup regressed (or got better) on ppc64le

2019-05-31 Thread Timo Aaltonen
Hello Dimitri, or anyone else affected,

Accepted systemd into bionic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/systemd/237-3ubuntu10.22 in a few
hours, and then in the -proposed repository.

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

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-bionic to verification-done-bionic. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-bionic. In either case, without details of
your testing we will not be able to proceed.

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

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: systemd (Ubuntu Bionic)
   Status: In Progress => Fix Committed

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

Title:
  storage / luks / dmsetup regressed (or got better) on ppc64le

Status in linux package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Fix Committed
Status in udisks2 package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  New
Status in systemd source package in Bionic:
  Fix Committed
Status in udisks2 source package in Bionic:
  Invalid
Status in linux source package in Cosmic:
  New
Status in systemd source package in Cosmic:
  Fix Committed
Status in udisks2 source package in Cosmic:
  Invalid
Status in linux source package in Disco:
  New
Status in systemd source package in Disco:
  Fix Committed
Status in udisks2 source package in Disco:
  Invalid
Status in linux source package in Eoan:
  Confirmed
Status in systemd source package in Eoan:
  Fix Committed
Status in udisks2 source package in Eoan:
  Invalid
Status in systemd package in Debian:
  Unknown

Bug description:
  in disco proposed with new systemd and v4.19 kernel it appears that
  dmsetup / cryptsetup storage either got better or worse.

  Devices take very long to activate, and sometimes remain in use during
  test clean up.

  This leads to udisks autopkgtest failing on ppc64le and systemd's
  "storage" autopkgtest is also failing.

  I've tried to make ppc64le test more resilient, but it's still odd
  that it became unstable in disco, and used to be rock solid on
  ppc64le.

  --
  sru template for systemd upload:

  [impact]
  buffer overflow can cause memory corruption; this is seen in failed 
autopkgtests

  [test case]
  see comment 6

  [regression potential]
  the patch is minimal and clearly correct; however the regression potential is 
around invalid/corrupted keys read from the keyring.

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

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


[Kernel-packages] [Bug 1814373] Please test proposed package

2019-05-31 Thread Timo Aaltonen
Hello Dimitri, or anyone else affected,

Accepted systemd into cosmic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/systemd/239-7ubuntu10.14 in a few
hours, and then in the -proposed repository.

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

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-cosmic to verification-done-cosmic. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-cosmic. In either case, without details of
your testing we will not be able to proceed.

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

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

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

Title:
  storage / luks / dmsetup regressed (or got better) on ppc64le

Status in linux package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Fix Committed
Status in udisks2 package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  New
Status in systemd source package in Bionic:
  In Progress
Status in udisks2 source package in Bionic:
  Invalid
Status in linux source package in Cosmic:
  New
Status in systemd source package in Cosmic:
  Fix Committed
Status in udisks2 source package in Cosmic:
  Invalid
Status in linux source package in Disco:
  New
Status in systemd source package in Disco:
  Fix Committed
Status in udisks2 source package in Disco:
  Invalid
Status in linux source package in Eoan:
  Confirmed
Status in systemd source package in Eoan:
  Fix Committed
Status in udisks2 source package in Eoan:
  Invalid
Status in systemd package in Debian:
  Unknown

Bug description:
  in disco proposed with new systemd and v4.19 kernel it appears that
  dmsetup / cryptsetup storage either got better or worse.

  Devices take very long to activate, and sometimes remain in use during
  test clean up.

  This leads to udisks autopkgtest failing on ppc64le and systemd's
  "storage" autopkgtest is also failing.

  I've tried to make ppc64le test more resilient, but it's still odd
  that it became unstable in disco, and used to be rock solid on
  ppc64le.

  --
  sru template for systemd upload:

  [impact]
  buffer overflow can cause memory corruption; this is seen in failed 
autopkgtests

  [test case]
  see comment 6

  [regression potential]
  the patch is minimal and clearly correct; however the regression potential is 
around invalid/corrupted keys read from the keyring.

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

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


[Kernel-packages] [Bug 1830941] Re: linux: 4.4.0-150.176 -proposed tracker

2019-05-31 Thread Ubuntu Kernel Bot
** Changed in: kernel-sru-workflow/automated-testing
   Status: Incomplete => Fix Released

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  backports: bug 1829205 (trusty/linux-aws), bug 1830947 
(trusty/linux-lts-xenial)
  derivatives: bug 1829193 (linux-aws), bug 1829195 (linux-kvm), bug 1829198 
(linux-raspi2), bug 1829201 (linux-snapdragon), bug 1829203 (linux-fips)
  
  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
- phase: Testing
- phase-changed: Thursday, 30. May 2019 11:31 UTC
+ phase: Signoff
+ phase-changed: Friday, 31. May 2019 13:31 UTC
  reason:
-   automated-testing: Stalled -- testing FAILED
regression-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
snap-release-to-beta: 'Pending -- snap pc-kernel not in expected 
channel(s): arch=amd64:channel=latest/beta
  arch=i386:channel=latest/beta'
snap-release-to-edge: 'Pending -- snap pc-kernel not in expected 
channel(s): arch=amd64:channel=latest/edge
  arch=i386:channel=latest/edge'
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/1830941

Title:
  linux: 4.4.0-150.176 -proposed tracker

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

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

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

  backports: bug 1829205 (trusty/linux-aws), bug 1830947 
(trusty/linux-lts-xenial)
  derivatives: bug 1829193 (linux-aws), bug 1829195 (linux-kvm), bug 1829198 
(linux-raspi2), bug 1829201 (linux-snapdragon), bug 1829203 (linux-fips)

  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
  phase: Signoff
  phase-changed: Friday, 31. May 2019 13:31 UTC
  reason:
regression-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
snap-release-to-beta: 'Pending -- snap pc-kernel not in expected 
channel(s): arch=amd64:channel=latest/beta
  arch=i386:channel=latest/beta'
snap-release-to-edge: 'Pending -- snap pc-kernel not in expected 
channel(s): arch=amd64:channel=latest/edge
  arch=i386:channel=latest/edge'
verification-testing: Ongoing -- testing in progress

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

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


[Kernel-packages] [Bug 1814373] Re: storage / luks / dmsetup regressed (or got better) on ppc64le

2019-05-31 Thread Timo Aaltonen
Hello Dimitri, or anyone else affected,

Accepted systemd into disco-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/systemd/240-6ubuntu5.1
in a few hours, and then in the -proposed repository.

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

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-disco to verification-done-disco. If it does not fix
the bug for you, please add a comment stating that, and change the tag
to verification-failed-disco. In either case, without details of your
testing we will not be able to proceed.

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

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: systemd (Ubuntu Disco)
   Status: In Progress => Fix Committed

** Tags added: verification-needed verification-needed-disco

** Changed in: systemd (Ubuntu Cosmic)
   Status: In Progress => Fix Committed

** Tags added: verification-needed-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/1814373

Title:
  storage / luks / dmsetup regressed (or got better) on ppc64le

Status in linux package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Fix Committed
Status in udisks2 package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  New
Status in systemd source package in Bionic:
  In Progress
Status in udisks2 source package in Bionic:
  Invalid
Status in linux source package in Cosmic:
  New
Status in systemd source package in Cosmic:
  Fix Committed
Status in udisks2 source package in Cosmic:
  Invalid
Status in linux source package in Disco:
  New
Status in systemd source package in Disco:
  Fix Committed
Status in udisks2 source package in Disco:
  Invalid
Status in linux source package in Eoan:
  Confirmed
Status in systemd source package in Eoan:
  Fix Committed
Status in udisks2 source package in Eoan:
  Invalid
Status in systemd package in Debian:
  Unknown

Bug description:
  in disco proposed with new systemd and v4.19 kernel it appears that
  dmsetup / cryptsetup storage either got better or worse.

  Devices take very long to activate, and sometimes remain in use during
  test clean up.

  This leads to udisks autopkgtest failing on ppc64le and systemd's
  "storage" autopkgtest is also failing.

  I've tried to make ppc64le test more resilient, but it's still odd
  that it became unstable in disco, and used to be rock solid on
  ppc64le.

  --
  sru template for systemd upload:

  [impact]
  buffer overflow can cause memory corruption; this is seen in failed 
autopkgtests

  [test case]
  see comment 6

  [regression potential]
  the patch is minimal and clearly correct; however the regression potential is 
around invalid/corrupted keys read from the keyring.

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

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


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

2019-05-31 Thread Marcelo Cerri
** Also affects: linux-azure (Ubuntu Disco)
   Importance: Undecided
   Status: New

-- 
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:
  Fix Released
Status in linux-azure source package in Xenial:
  Fix Released
Status in linux-azure source package in Bionic:
  Fix Released
Status in linux-azure source package in Cosmic:
  Fix Released
Status in linux-azure source package in Disco:
  New

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 1824879] Re: linux-azure: Add the Catapult FPGA Driver

2019-05-31 Thread Marcelo Cerri
** Also affects: linux-azure (Ubuntu Disco)
   Importance: Undecided
   Status: New

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

** Changed in: linux-azure (Ubuntu Disco)
 Assignee: (unassigned) => Marcelo Cerri (mhcerri)

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

Title:
  linux-azure: Add the Catapult FPGA Driver

Status in linux-azure package in Ubuntu:
  Fix Released
Status in linux-azure source package in Xenial:
  Fix Released
Status in linux-azure source package in Cosmic:
  Fix Released
Status in linux-azure source package in Disco:
  In Progress

Bug description:
  [Impact]

  Add the Catapult FPGA Driver to the custom linux-azure kernel while a
  version is not available upstream.

  [Test Case]

  The catapult driver must be present as a module in the linux-modules
  package (not in the linux-modules-extra).

  [Regression Potential]

  Low risk of regression since that's a new driver.

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

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


[Kernel-packages] [Bug 1830883] Re: iwlwifi Intel 8265 firmware crashing in powersave mode

2019-05-31 Thread Seth Forshee
That does appear to be the latest firmware. There's some information
about debugging and reporting bugs here:

https://wireless.wiki.kernel.org/en/users/drivers/iwlwifi/debugging

There are some things there to try, but given that this appears to be a
firmware crash I don't know that they will be of much help. Your best
bet is to follow the instructions there to report a bug for the
developers at Intel to look at.

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

Title:
   iwlwifi Intel 8265 firmware crashing in powersave mode

Status in linux-firmware package in Ubuntu:
  Incomplete

Bug description:
  When I disconnect my AC adapter or run `sudo tlp bat` to switch to
  battery mode my wifi stops working. Reconnecting the AC adapter or
  running `sudo tlp ac` returns the wifi adapter to a functioning state.

  I use the default TLP configuration without modifications and at first
  I was thinking that this is a bug in TLP. The FAQs already have an
  entry about this and state that this is due to the "kernel driver does
  not implement power saving properly" [1]. This is why I'm reporting
  the issue here.

  I'm using Ubuntu Disco and I remember this working in previous Ubuntu
  versions / kernels. This happened on kernel 5.0.0-15-generic but also
  on the 5.1.5-050105-generic mainline kernel.

  Below is a snippet of /var/log/syslog at the moment of switching TLP
  to battery mode. Battery mode was activated at 11:25 and AC mode was
  re-activated around 11:27.

  Please let me know if this is actually the right place to submit this
  bug report and whether I can provide more information.

  ---

  May 29 11:23:40 x1cbn systemd-resolved[1037]: message repeated 3 times: [ 
Server returned error NXDOMAIN, mitigating potential DNS violation 
DVE-2018-0001, retrying transaction with reduced feature level UDP.]
  May 29 11:23:41 x1cbn colord[1285]: failed to get session [pid 1158]: Keine 
Daten verfügbar
  May 29 11:25:37 x1cbn wpa_supplicant[1144]: wlp2s0: CTRL-EVENT-SCAN-FAILED 
ret=-110
  May 29 11:25:37 x1cbn geoclue[1741]: WiFi scan failed
  May 29 11:25:37 x1cbn kernel: [ 4645.773659] iwlwifi :02:00.0: Error 
sending SCAN_REQ_UMAC: time out after 2000ms.
  May 29 11:25:37 x1cbn kernel: [ 4645.773670] iwlwifi :02:00.0: Current 
CMD queue read_ptr 229 write_ptr 230
  May 29 11:25:37 x1cbn kernel: [ 4645.775119] iwlwifi :02:00.0: Start IWL 
Error Log Dump:
  May 29 11:25:37 x1cbn kernel: [ 4645.775125] iwlwifi :02:00.0: Status: 
0x0100, count: 6
  May 29 11:25:37 x1cbn kernel: [ 4645.775130] iwlwifi :02:00.0: Loaded 
firmware version: 36.9f0a2d68.0
  May 29 11:25:37 x1cbn kernel: [ 4645.775137] iwlwifi :02:00.0: 0x0084 
| NMI_INTERRUPT_UNKNOWN   
  May 29 11:25:37 x1cbn kernel: [ 4645.775142] iwlwifi :02:00.0: 0x0200 
| trm_hw_status0
  May 29 11:25:37 x1cbn kernel: [ 4645.775147] iwlwifi :02:00.0: 0x 
| trm_hw_status1
  May 29 11:25:37 x1cbn kernel: [ 4645.775152] iwlwifi :02:00.0: 0x0002485C 
| branchlink2
  May 29 11:25:37 x1cbn kernel: [ 4645.775157] iwlwifi :02:00.0: 0x0003A7CA 
| interruptlink1
  May 29 11:25:37 x1cbn kernel: [ 4645.775161] iwlwifi :02:00.0: 0x5D56 
| interruptlink2
  May 29 11:25:37 x1cbn kernel: [ 4645.775166] iwlwifi :02:00.0: 0x 
| data1
  May 29 11:25:37 x1cbn kernel: [ 4645.775171] iwlwifi :02:00.0: 0x0080 
| data2
  May 29 11:25:37 x1cbn kernel: [ 4645.775175] iwlwifi :02:00.0: 0x07A3 
| data3
  May 29 11:25:37 x1cbn kernel: [ 4645.775180] iwlwifi :02:00.0: 0xBBC109E2 
| beacon time
  May 29 11:25:37 x1cbn kernel: [ 4645.775185] iwlwifi :02:00.0: 0x10C87621 
| tsf low
  May 29 11:25:37 x1cbn kernel: [ 4645.775190] iwlwifi :02:00.0: 0x019F 
| tsf hi
  May 29 11:25:37 x1cbn kernel: [ 4645.775194] iwlwifi :02:00.0: 0x 
| time gp1
  May 29 11:25:37 x1cbn kernel: [ 4645.775199] iwlwifi :02:00.0: 0xCC95B750 
| time gp2
  May 29 11:25:37 x1cbn kernel: [ 4645.775204] iwlwifi :02:00.0: 0x0001 
| uCode revision type
  May 29 11:25:37 x1cbn kernel: [ 4645.775209] iwlwifi :02:00.0: 0x0024 
| uCode version major
  May 29 11:25:37 x1cbn kernel: [ 4645.775214] iwlwifi :02:00.0: 0x9F0A2D68 
| uCode version minor
  May 29 11:25:37 x1cbn kernel: [ 4645.775219] iwlwifi :02:00.0: 0x0230 
| hw version
  May 29 11:25:37 x1cbn kernel: [ 4645.775224] iwlwifi :02:00.0: 0x0008 
| board version
  May 29 11:25:37 x1cbn kernel: [ 4645.775228] iwlwifi :02:00.0: 0x001C 
| hcmd
  May 29 11:25:37 x1cbn kernel: [ 4645.775233] iwlwifi :02:00.0: 0x24022000 
| isr0
  May 29 11:25:37 x1cbn kernel: [ 4645.775238] iwlwifi :02:00.0: 0x0180 
| isr1
  May 29 11:25:37 x1cbn kernel: [ 4645.775242] iwlwifi :02:00.0: 0x0800180A 
| isr2
  May 29 11:25:37 x1cbn kernel: [ 4645.775247] iwlwifi :02:00.0: 

Re: [Kernel-packages] [Bug 1830350] Re: System freezes repeatedly for several seconds; wifi driver related errors

2019-05-31 Thread Seth Forshee
On Fri, May 31, 2019 at 10:41:17AM -, Frank van Wensveen wrote:
> 1. The latest linux-firmware that you directed me to (linux-
> firmware-20190514.tar.gz) is obviously intended for those who know what
> they're doing. It is just a matter of "make install" or is there more to
> installing this version? I'm a little concerned about hosing my system,
> seeing as it's my production machine.

I think you would be better off making backup copies of the specific
files the driver uses, then replace the original files with the versions
from the link. Running "modinfo -F firmware /lib/modules/$(uname
-r)/kernel/drivers/net/wireless/ath/ath10k/ath10k_pci.ko" in a terminal
will give you a list of the firmware files the driver may be using. Note
that the paths it prints need to have /lib/firmware/ prepended.

> 2. Can I simply install:
> linux-image-unsigned-5.2.0-050200rc2-generic_5.2.0-050200rc2.201905262130_amd64.deb
> linux-modules-5.2.0-050200rc2-generic_5.2.0-050200rc2.201905262130_amd64.deb
> linux-headers-5.2.0-050200rc2-generic_5.2.0-050200rc2.201905262130_amd64.deb
> or are there other dependencies as well?

You might also need the linux-headers-*_all.deb package. You probably
only need the headers packages if you are using dkms modules, but if the
*_amd64 package without the *_all package won't do you much good. If
you're unsure whether you need them just go ahead and install them; they
won't hurt anything.

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

Title:
  System freezes repeatedly for several seconds; wifi driver related
  errors

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

Bug description:
  I updated my system about a month ago (Fri 26 April 2019). This was
  the first update in several weeks and installed fresh versions of a
  whole truck load of applications including a kernel update. Since this
  latest bunch of updates the system freezes for a few seconds at
  regular intervals. Not fatal, but very annoying.

  Output from "journalctl -f" shows the following errors occurring at
  the same time as these freezes:

  May 24 10:31:18 dellfvw wpa_supplicant[1078]: wlp3s0: CTRL-EVENT-SCAN-FAILED 
ret=-110
  May 24 10:31:18 dellfvw kernel: ath10k_pci :03:00.0: failed to receive 
scan abortion completion: timed out
  May 24 10:31:18 dellfvw kernel: ath10k_pci :03:00.0: failed to stop scan: 
-110
  May 24 10:31:18 dellfvw kernel: ath10k_pci :03:00.0: failed to start hw 
scan: -110

  Corresponding lines in /var/log/syslog:

  May 24 10:29:16 dellfvw avahi-daemon[1053]: Registering new address record 
for fe80::424:c75b:2a2d:52e2 on wlp3s0.*.
  May 24 10:29:55 dellfvw avahi-daemon[1053]: Withdrawing address record for 
fe80::424:c75b:2a2d:52e2 on wlp3s0.
  May 24 10:31:18 dellfvw wpa_supplicant[1078]: wlp3s0: CTRL-EVENT-SCAN-FAILED 
ret=-110
  May 24 10:31:18 dellfvw kernel: [45569.661175] ath10k_pci :03:00.0: 
failed to receive scan abortion completion: timed out
  May 24 10:31:18 dellfvw kernel: [45569.661183] ath10k_pci :03:00.0: 
failed to stop scan: -110
  May 24 10:31:18 dellfvw kernel: [45569.661187] ath10k_pci :03:00.0: 
failed to start hw scan: -110

  I do note the interval between the avahi-daemon entry and the
  subsequent errors related to the wireless network interface, but the
  former precede the latter consistently in syslog, suggesting they may
  be related, which is why I'm including it in this report.

  The freezes last a few seconds. Keyboard input is preserved at this
  time and typed input appears after the freeze is resolved. Mouse
  cursor continues to move during freezes but mouse clicks are only
  processed after the freeze is resolved, i.e. the result of the mouse
  click is suspended (e.g. buffered) until the system becomes responsive
  again. For example, clicking on a window during the freeze will focus
  that window after the freeze has been resolved.

  The system is a Dell Inspiron 15 3576. Relevant output of lspci -nnk:

  03:00.0 Network controller [0280]: Qualcomm Atheros QCA9377 802.11ac
  Wireless Network Adapter [168c:0042] (rev 31)

  Output of lsb_release -rd:
  Description:  Ubuntu 18.04.2 LTS
  Release:  18.04

  Output of uname -a:
  Linux dellfvw 4.15.0-50-generic #54-Ubuntu SMP Mon May 6 18:46:08 UTC 2019 
x86_64 x86_64 x86_64 GNU/Linux

  As already said, this is a new issue that has began occurring only
  after the recent batch of updates that included a kernel update. I
  reported the bug (maybe in the wrong place) but so far I have received
  no response. I've lived with this for a month or so hoping that
  further updates would fix the problem but it still persists.
  Installing the latest firmware update (14 Mar 2019) has no effect. No
  other changes were made to either hardware or OS configuration.

  Logfile snippets attached.
  --- 
  

[Kernel-packages] [Bug 1829195] Re: linux-kvm: 4.4.0-1047.53 -proposed tracker

2019-05-31 Thread Ubuntu Kernel Bot
** Changed in: kernel-sru-workflow/automated-testing
   Status: Incomplete => Fix Released

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  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: 1830941
- phase: Testing
- phase-changed: Monday, 20. May 2019 11:54 UTC
+ phase: Ready for Testing
+ phase-changed: Friday, 31. May 2019 12:39 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   automated-testing: Stalled -- testing FAILED
verification-testing: Ongoing -- testing in progress

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

Title:
  linux-kvm: 4.4.0-1047.53 -proposed tracker

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

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  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: 1830941
  phase: Ready for Testing
  phase-changed: Friday, 31. May 2019 12:39 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
verification-testing: Ongoing -- testing in progress

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

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


[Kernel-packages] [Bug 1830050] Re: nvidia-graphics-drivers-390 390.116-0ubuntu1 ADT test failure with linux 5.2.0-0.1

2019-05-31 Thread Seth Forshee
** Attachment added: "make.log"
   
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1830050/+attachment/5268059/+files/make.log

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

Title:
  nvidia-graphics-drivers-390 390.116-0ubuntu1 ADT test failure with
  linux 5.2.0-0.1

Status in nvidia-graphics-drivers-390 package in Ubuntu:
  New

Bug description:
  Testing failed on:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1830050/+subscriptions

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


[Kernel-packages] [Bug 1830050] Re: nvidia-graphics-drivers-390 390.116-0ubuntu1 ADT test failure with linux 5.2.0-0.1

2019-05-31 Thread Alberto Milone
** Changed in: nvidia-graphics-drivers-390 (Ubuntu)
   Importance: Undecided => Medium

** Changed in: nvidia-graphics-drivers-390 (Ubuntu)
 Assignee: (unassigned) => Alberto Milone (albertomilone)

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

Title:
  nvidia-graphics-drivers-390 390.116-0ubuntu1 ADT test failure with
  linux 5.2.0-0.1

Status in nvidia-graphics-drivers-390 package in Ubuntu:
  New

Bug description:
  Testing failed on:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1830050/+subscriptions

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


[Kernel-packages] [Bug 1830053] Re: nvidia-graphics-drivers-418 418.74-0ubuntu1 ADT test failure with linux 5.2.0-0.1

2019-05-31 Thread Alberto Milone
** Changed in: nvidia-graphics-drivers-418 (Ubuntu)
 Assignee: (unassigned) => Alberto Milone (albertomilone)

** Changed in: nvidia-graphics-drivers-418 (Ubuntu)
   Importance: Undecided => Medium

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

Title:
  nvidia-graphics-drivers-418 418.74-0ubuntu1 ADT test failure with
  linux 5.2.0-0.1

Status in nvidia-graphics-drivers-418 package in Ubuntu:
  Confirmed

Bug description:
  Testing failed on:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-418/+bug/1830053/+subscriptions

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


[Kernel-packages] [Bug 1830053] Re: nvidia-graphics-drivers-418 418.74-0ubuntu1 ADT test failure with linux 5.2.0-0.1

2019-05-31 Thread Seth Forshee
** Attachment added: "make.log"
   
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-418/+bug/1830053/+attachment/5268058/+files/make.log

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

Title:
  nvidia-graphics-drivers-418 418.74-0ubuntu1 ADT test failure with
  linux 5.2.0-0.1

Status in nvidia-graphics-drivers-418 package in Ubuntu:
  Confirmed

Bug description:
  Testing failed on:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-418/+bug/1830053/+subscriptions

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


[Kernel-packages] [Bug 1831229] Re: getrandom02 from ubuntu_ltp_syscalls failed with timeout multiplier = 3 on D-KVM

2019-05-31 Thread Colin Ian King
..or network too.

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

Title:
  getrandom02 from ubuntu_ltp_syscalls failed with timeout multiplier =
  3 on D-KVM

Status in ubuntu-kernel-tests:
  New
Status in linux-kvm package in Ubuntu:
  New

Bug description:
  Even with the timeout multiplier set to 3, the test is still failing:

   Waiting for pid 1892 for 21600 seconds
   Checking virt-what to see if we need to set LTP_TIMEOUT_MUL...
   Running in VM, set timeout multiplier LTP_TIMEOUT_MUL=3 (lp:1797327)
   == Test Suite Summary ==
   7 test cases failed
   0 test cases blacklisted
   Failed test cases : acct01 getrandom02 msgstress03 quotactl01 quotactl02 
quotactl03 sync_file_range02 

  startup='Thu May 30 21:36:06 2019'
  tst_test.c:1096: INFO: Timeout per run is 0h 15m 00s
  getrandom02.c:72: PASS: getrandom returned 256
  Test timeouted, sending SIGKILL!
  tst_test.c:1136: INFO: If you are running on slow machine, try exporting 
LTP_TIMEOUT_MUL > 1
  tst_test.c:1137: BROK: Test killed! (timeout?)

  Summary:
  passed   1
  failed   0
  skipped  0
  warnings 0
  tag=getrandom02 stime=1559252166 dur=900 exit=exited stat=2 core=no cu=0 cs=0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1831229/+subscriptions

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


[Kernel-packages] [Bug 1824687] Re: 4.4.0-145-generic Kernel Panic ip6_expire_frag_queue

2019-05-31 Thread Heikki Hannikainen
Thanks, I deployed the v4 debs on one server which was particularly
unstable, and it's still up after 1 day and 8 hours now. I'll deploy
more widely on Monday and Tuesday.

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

Title:
  4.4.0-145-generic Kernel Panic  ip6_expire_frag_queue

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

Bug description:
  Description:  Ubuntu 16.04.6 LTS
  Release:  16.04

  
  After upgrading our server to this Kernel we experience frequent Kernel 
panics (Attachment).
  Every 3 hours. 
  Our machine has a throuput of about 600 Mbits/s 
  The Panics are around the area of ip6_expire_frag_queue.

__pskb_pull_tail
ip6_dst_lookup_tail
_decode_session6
__xfrm_decode_session
icmpv6_route_lookup
icmp6_send

  
  It seems similar to Bug Report in Debian.
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=922488

  According to the bug finder of above bug it also occurred after using a 
Kernel with the change of
  rewrite ip6_expire_frag_queue()

  Intermediate solution. We disabled IPv6 on this machine to avoid further 
Panics.
  Please let me know what information is missing. The ubuntu-bug linux was 
send. And I hope it is attached to this report.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-145-generic 4.4.0-145.171
  ProcVersionSignature: Ubuntu 4.4.0-145.171-generic 4.4.176
  Uname: Linux 4.4.0-145-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  Date: Sun Apr 14 11:40:11 2019
  InstallationDate: Installed on 2018-03-18 (391 days ago)
  InstallationMedia: Ubuntu-Server 16.04.4 LTS "Xenial Xerus" - Release amd64 
(20180228)
  ProcEnviron:
   LANGUAGE=en_GB:en
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-signed
  UpgradeStatus: Upgraded to xenial on 2018-10-21 (174 days ago)
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Apr 12 21:04 seq
   crw-rw 1 root audio 116, 33 Apr 12 21:04 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=/dev/mapper/tor3--vg-swap_1
  InstallationDate: Installed on 2018-03-18 (393 days ago)
  InstallationMedia: Ubuntu-Server 16.04.4 LTS "Xenial Xerus" - Release amd64 
(20180228)
  IwConfig: Error: [Errno 2] No such file or directory
  Lsusb:
   Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 003: ID 0557:2221 ATEN International Co., Ltd Winbond Hermon
   Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Supermicro X9SRE/X9SRE-3F/X9SRi/X9SRi-3F
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   LANGUAGE=en_GB:en
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-145-generic 
root=/dev/mapper/hostname--vg-root ro
  ProcVersionSignature: Ubuntu 4.4.0-145.171-generic 4.4.176
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-145-generic N/A
   linux-backports-modules-4.4.0-145-generic  N/A
   linux-firmware 1.157.21
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  xenial xenial
  Uname: Linux 4.4.0-145-generic x86_64
  UpgradeStatus: Upgraded to xenial on 2018-10-21 (176 days ago)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 10/08/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.0c
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: X9SRE/X9SRE-3F/X9SRi/X9SRi-3F
  dmi.board.vendor: Supermicro
  dmi.board.version: 1.2
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Supermicro
  dmi.chassis.version: 0123456789
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.0c:bd10/08/2012:svnSupermicro:pnX9SRE/X9SRE-3F/X9SRi/X9SRi-3F:pvr0123456789:rvnSupermicro:rnX9SRE/X9SRE-3F/X9SRi/X9SRi-3F:rvr1.2:cvnSupermicro:ct3:cvr0123456789:
  dmi.product.name: X9SRE/X9SRE-3F/X9SRi/X9SRi-3F
  dmi.product.version: 0123456789
  dmi.sys.vendor: Supermicro

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

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

[Kernel-packages] [Bug 1831229] Re: getrandom02 from ubuntu_ltp_syscalls failed with timeout multiplier = 3 on D-KVM

2019-05-31 Thread Colin Ian King
Maybe exercising the disc(s) may help, this generates interrupts that
get used to add entropy to the entropy pool.

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

Title:
  getrandom02 from ubuntu_ltp_syscalls failed with timeout multiplier =
  3 on D-KVM

Status in ubuntu-kernel-tests:
  New
Status in linux-kvm package in Ubuntu:
  New

Bug description:
  Even with the timeout multiplier set to 3, the test is still failing:

   Waiting for pid 1892 for 21600 seconds
   Checking virt-what to see if we need to set LTP_TIMEOUT_MUL...
   Running in VM, set timeout multiplier LTP_TIMEOUT_MUL=3 (lp:1797327)
   == Test Suite Summary ==
   7 test cases failed
   0 test cases blacklisted
   Failed test cases : acct01 getrandom02 msgstress03 quotactl01 quotactl02 
quotactl03 sync_file_range02 

  startup='Thu May 30 21:36:06 2019'
  tst_test.c:1096: INFO: Timeout per run is 0h 15m 00s
  getrandom02.c:72: PASS: getrandom returned 256
  Test timeouted, sending SIGKILL!
  tst_test.c:1136: INFO: If you are running on slow machine, try exporting 
LTP_TIMEOUT_MUL > 1
  tst_test.c:1137: BROK: Test killed! (timeout?)

  Summary:
  passed   1
  failed   0
  skipped  0
  warnings 0
  tag=getrandom02 stime=1559252166 dur=900 exit=exited stat=2 core=no cu=0 cs=0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1831229/+subscriptions

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


[Kernel-packages] [Bug 1817321] Re: installer does not support iSCSI iBFT

2019-05-31 Thread Dan Streetman
** Tags added: sts-sponsor

** Tags added: sts-sponsor-ddstreet

** Tags removed: sts-sponsor-ddstreet

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

Title:
  installer does not support iSCSI iBFT

Status in debian-installer package in Ubuntu:
  Fix Released
Status in hw-detect package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in partman-iscsi package in Ubuntu:
  Fix Released
Status in debian-installer source package in Bionic:
  Confirmed
Status in hw-detect source package in Bionic:
  Confirmed
Status in linux source package in Bionic:
  Fix Released
Status in partman-iscsi source package in Bionic:
  Confirmed
Status in debian-installer source package in Cosmic:
  Confirmed
Status in hw-detect source package in Cosmic:
  Confirmed
Status in linux source package in Cosmic:
  Fix Released
Status in partman-iscsi source package in Cosmic:
  Confirmed
Status in debian-installer source package in Disco:
  Confirmed
Status in hw-detect source package in Disco:
  Confirmed
Status in linux source package in Disco:
  Fix Released
Status in partman-iscsi source package in Disco:
  Confirmed
Status in debian-installer source package in Eoan:
  Fix Released
Status in hw-detect source package in Eoan:
  Fix Released
Status in linux source package in Eoan:
  Fix Released
Status in partman-iscsi source package in Eoan:
  Fix Released

Bug description:
  [Impact]

   * It's not possible to access iBFT (iSCSI Boot Firmware Table) information
     (settings for network interface, initiator, and target) in the installer
     because the 'iscsi_ibft' module is not present in udeb packages.

   * Even if it was, the installer does not handle iBFT information at all,
     thus any settings are ignored, and iSCSI-related configuration has to
     be done manually or with workarounds.

   * This impacts user-experience and automatic installation on systems and
     deployments which actually do provide the iBFT feature and information,
     but cannot use it practically.

   * With proper iBFT support in the installer (kernel module in udeb package
     and automatic iSCSI-related configuration) users will be able to rely on
     iBFT to install/deploy Ubuntu on their servers and datacenters.

   * These fixes add the 'iscsi_ibft' kernel module in the scsi-modules udeb,
     and configure network/iSCSI according to iBFT information in disk-detect.

     This is done in disk-detect so that the iSCSI LUNs are detected as disks
     (useful in case of no other disks in the system so the installer doesn't
     complain nor wait too long) and that any partman-related preseed options
     are not required and may be still available for the user.

  [Test Case]

   * linux package / kernel module in udeb:

     $ dpkg-deb -c scsi-modules_*.udeb | grep iscsi_ibft.ko

     Check the module loads in the installer environment.
     See comment with example for disco.

   * d-i/hw-detect/partman-iscsi package:
     See comments 11, 12, 13.

  [Regression Potential]

   * linux package: low, the kernel module is not loaded by default,
     and only checks whether iBFT information is present in firmware,
     then exposes that in sysfs in read-only mode.

   * d-i/hw-detect/partman-iscsi:
     - d-i: kernel version update to include iscsi_ibft module,
    based on kernel released to -updates plus one week
    monitoring bug reports -- it should be OK.
    Tested on amd64/i386/arm64/ppc64el on QEMU, plus amd64
    on baremetal -- see comment 11.
     - hw-detect: low, the changes are enabled by a preseed option.
  see comment 12.
     - partman-iscsi: low, simple changes, plus one fix that has
  been tested in detail, and falls back to
  previous behavior if it fails.
  see comment 13.

  [Other Info]

   * This has been verified both by the developer with a simple iSCSI
     iBFT environment (2 VMs: iSCSI target & initiator with UEFI+iPXE)
     and by an user with system/firmware that supports iBFT for iSCSI.

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

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


[Kernel-packages] [Bug 1829191] Re: linux-oem: 4.15.0-1039.44 -proposed tracker

2019-05-31 Thread Ubuntu Kernel Bot
** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  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: 1829219
- phase: Testing
- phase-changed: Friday, 24. May 2019 18:10 UTC
+ phase: Ready for Testing
+ phase-changed: Friday, 31. May 2019 11:36 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   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-oem in Ubuntu.
https://bugs.launchpad.net/bugs/1829191

Title:
  linux-oem: 4.15.0-1039.44 -proposed tracker

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

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  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: 1829219
  phase: Ready for Testing
  phase-changed: Friday, 31. May 2019 11:36 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
verification-testing: Ongoing -- testing in progress

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

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


[Kernel-packages] [Bug 1829191] Re: linux-oem: 4.15.0-1039.44 -proposed tracker

2019-05-31 Thread Taihsiang Ho
Hardware Certification have completed testing this -proposed kernel. No
regressions were observed, results are available here:
http://people.canonical.com/~hwcert/sru-
testing/oem/4.15.0-1039.44/oem-4.15-proposed-published.html

** Tags added: certification-testing-passed

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

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

Title:
  linux-oem: 4.15.0-1039.44 -proposed tracker

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

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  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: 1829219
  phase: Ready for Testing
  phase-changed: Friday, 31. May 2019 11:36 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
verification-testing: Ongoing -- testing in progress

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

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


[Kernel-packages] [Bug 1830941] Re: linux: 4.4.0-150.176 -proposed tracker

2019-05-31 Thread Ubuntu Kernel Bot
** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  backports: bug 1829205 (trusty/linux-aws), bug 1830947 
(trusty/linux-lts-xenial)
  derivatives: bug 1829193 (linux-aws), bug 1829195 (linux-kvm), bug 1829198 
(linux-raspi2), bug 1829201 (linux-snapdragon), bug 1829203 (linux-fips)
  
  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
  phase: Testing
  phase-changed: Thursday, 30. May 2019 11:31 UTC
  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 pc-kernel not in expected 
channel(s): arch=amd64:channel=latest/beta
  arch=i386:channel=latest/beta'
snap-release-to-edge: 'Pending -- snap pc-kernel not in expected 
channel(s): arch=amd64:channel=latest/edge
  arch=i386:channel=latest/edge'
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/1830941

Title:
  linux: 4.4.0-150.176 -proposed tracker

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

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

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

  backports: bug 1829205 (trusty/linux-aws), bug 1830947 
(trusty/linux-lts-xenial)
  derivatives: bug 1829193 (linux-aws), bug 1829195 (linux-kvm), bug 1829198 
(linux-raspi2), bug 1829201 (linux-snapdragon), bug 1829203 (linux-fips)

  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
  phase: Testing
  phase-changed: Thursday, 30. May 2019 11:31 UTC
  reason:
automated-testing: Stalled -- testing FAILED
regression-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
snap-release-to-beta: 'Pending -- snap pc-kernel not in expected 
channel(s): arch=amd64:channel=latest/beta
  arch=i386:channel=latest/beta'
snap-release-to-edge: 'Pending -- snap pc-kernel not in expected 
channel(s): arch=amd64:channel=latest/edge
  arch=i386:channel=latest/edge'
verification-testing: Ongoing -- testing in progress

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

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


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

2019-05-31 Thread Ubuntu Kernel Bot
This change was made by a bot.

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

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

Title:
  Ubuntu 18.04 won't boot - failed to connect to lvmetad

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This bug report relates to a machine running 18.04, not the one I am
  submitting the report from.

  On 30 May The Software Updater prompted me to update. Included in the
  update were initramfs components. I now cannot boot the machine.

  After decrypting the root file system, instead of being prompted for
  the pass-phrase to decrypt the swap, I get the message "cannot connect
  to lvmetad: falling back to device scanning". This repeats for a while
  until I am dropped into a recovery shell of some sort from which I
  cannot access the root disk.

  Blocker. My machine is unusable.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-generic 4.15.0.48.50
  ProcVersionSignature: Ubuntu 4.15.0-48.51-generic 4.15.18
  Uname: Linux 4.15.0-48-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  gdm2433 F pulseaudio
raph   8920 F pulseaudio
   /dev/snd/controlC0:  gdm2433 F pulseaudio
  Date: Fri May 31 12:08:33 2019
  HibernationDevice: RESUME=UUID=2538baa4-d43e-4876-8d94-dd3221894bac
  InstallationDate: Installed on 2018-02-09 (475 days ago)
  InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: LENOVO 20CJS0UU00
  ProcEnviron:
   LANGUAGE=en_GB:en
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-48-generic 
root=/dev/mapper/xubuntu--vg-root ro quiet splash vt.handoff=1
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-48-generic N/A
   linux-backports-modules-4.15.0-48-generic  N/A
   linux-firmware 1.173.5
  SourcePackage: linux
  UpgradeStatus: Upgraded to bionic on 2018-09-12 (260 days ago)
  dmi.bios.date: 09/13/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N11ET42W (1.18 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20CJS0UU00
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 WIN
  dmi.chassis.asset.tag: R90G3N7R
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN11ET42W(1.18):bd09/13/2017:svnLENOVO:pn20CJS0UU00:pvrThinkPadT550:rvnLENOVO:rn20CJS0UU00:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T550
  dmi.product.name: 20CJS0UU00
  dmi.product.version: ThinkPad T550
  dmi.sys.vendor: LENOVO

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

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


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

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

apport-collect 1830151

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

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

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

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

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

Title:
  ebb: cycles_test in powerpc from ubuntu_kernel_selftests failed on
  B-hwe P9

Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  This test has passed with Cosmic kernel on the same node ("baltar"),
  but not with the 4.18 kernel on Bionic.

   selftests: ebb: cycles_test
   
   test: cycles
   tags: git_version:unknown
   EBB Handler is at 0x10004170
   ebb_state:
   ebb_count = 10
   spurious = 0
   negative = 0
   no_overflow = 0
   pmc[1] count = 0x2843f
   pmc[2] count = 0x0
   pmc[3] count = 0x0
   pmc[4] count = 0x0
   pmc[5] count = 0x0
   pmc[6] count = 0x0
   HW state:
   MMCR0 0x8400 FC PMAE
   MMCR2 0x
   EBBHR 0x10004170
   BESCR 0x8000 GE
   PMC1 0x4000
   PMC2 0x
   PMC3 0x
   PMC4 0x
   PMC5 0x00028b3f
   PMC6 0x0002ac80
   SIAR 0x100035d4
   Trace buffer dump:
   address 0x71a628a2
   tail 0x71a628a201f6
   size 1048576
   overflow false
   Content:
   [0]: counter = 1
   [1]: register SPRN_MMCR0 = 0x8080
   [2]: register SPRN_PMC1 = 0x8004
   [3]: counter = 2
   [4]: register SPRN_MMCR0 = 0x8080
   [5]: register SPRN_PMC1 = 0x8004
   [6]: counter = 3
   [7]: register SPRN_MMCR0 = 0x8080
   [8]: register SPRN_PMC1 = 0x8004
   [FAIL] Test FAILED on line 52
   [9]: counter = 4
   [10]: register SPRN_MMCR0 = 0x8080
   [11]: register SPRN_PMC1 = 0x8004
   [12]: counter = 5
   [13]: register SPRN_MMCR0 = 0x8080
   [14]: register SPRN_PMC1 = 0x8004
   [15]: counter = 6
   [16]: register SPRN_MMCR0 = 0x8080
   [17]: register SPRN_PMC1 = 0x8004
   [18]: counter = 7
   [19]: register SPRN_MMCR0 = 0x8080
   [20]: register SPRN_PMC1 = 0x8004
   [21]: counter = 8
   [22]: register SPRN_MMCR0 = 0x8080
   [23]: register SPRN_PMC1 = 0x8004
   [24]: counter = 9
   [25]: register SPRN_MMCR0 = 0x8080
   [26]: register SPRN_PMC1 = 0x8004
   [27]: counter = 10
   [28]: register SPRN_MMCR0 = 0x8080
   [29]: register SPRN_PMC1 = 0x8004
   [30]: register SPRN_PMC1 = 0x4417
   PMC1 count (0x2843f) above upper limit 0x283e8 (+0x57)
   failure: cycles
   not ok 1..3 selftests: ebb: cycles_test [FAIL]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1830151/+subscriptions

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


[Kernel-packages] [Bug 1831229] Re: getrandom02 from ubuntu_ltp_syscalls failed with timeout multiplier = 3 on D-KVM

2019-05-31 Thread Po-Hsu Lin
Will try to increase the timeout multiplier.
Or install the haveged to see if it helps.

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

Title:
  getrandom02 from ubuntu_ltp_syscalls failed with timeout multiplier =
  3 on D-KVM

Status in ubuntu-kernel-tests:
  New
Status in linux-kvm package in Ubuntu:
  New

Bug description:
  Even with the timeout multiplier set to 3, the test is still failing:

   Waiting for pid 1892 for 21600 seconds
   Checking virt-what to see if we need to set LTP_TIMEOUT_MUL...
   Running in VM, set timeout multiplier LTP_TIMEOUT_MUL=3 (lp:1797327)
   == Test Suite Summary ==
   7 test cases failed
   0 test cases blacklisted
   Failed test cases : acct01 getrandom02 msgstress03 quotactl01 quotactl02 
quotactl03 sync_file_range02 

  startup='Thu May 30 21:36:06 2019'
  tst_test.c:1096: INFO: Timeout per run is 0h 15m 00s
  getrandom02.c:72: PASS: getrandom returned 256
  Test timeouted, sending SIGKILL!
  tst_test.c:1136: INFO: If you are running on slow machine, try exporting 
LTP_TIMEOUT_MUL > 1
  tst_test.c:1137: BROK: Test killed! (timeout?)

  Summary:
  passed   1
  failed   0
  skipped  0
  warnings 0
  tag=getrandom02 stime=1559252166 dur=900 exit=exited stat=2 core=no cu=0 cs=0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1831229/+subscriptions

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


[Kernel-packages] [Bug 1830941] Re: linux: 4.4.0-150.176 -proposed tracker

2019-05-31 Thread Taihsiang Ho
Hardware Certification have completed testing this -proposed kernel. No
regressions were observed, results are available here:
http://people.canonical.com/~hwcert/sru-testing/xenial/4.4.0-150.176
/xenial-proposed-published.html

** Tags added: certification-testing-passed

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

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

Title:
  linux: 4.4.0-150.176 -proposed tracker

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

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

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

  backports: bug 1829205 (trusty/linux-aws), bug 1830947 
(trusty/linux-lts-xenial)
  derivatives: bug 1829193 (linux-aws), bug 1829195 (linux-kvm), bug 1829198 
(linux-raspi2), bug 1829201 (linux-snapdragon), bug 1829203 (linux-fips)

  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
  phase: Testing
  phase-changed: Thursday, 30. May 2019 11:31 UTC
  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 pc-kernel not in expected 
channel(s): arch=amd64:channel=latest/beta
  arch=i386:channel=latest/beta'
snap-release-to-edge: 'Pending -- snap pc-kernel not in expected 
channel(s): arch=amd64:channel=latest/edge
  arch=i386:channel=latest/edge'
verification-testing: Ongoing -- testing in progress

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

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


[Kernel-packages] [Bug 1831229] Re: getrandom02 from ubuntu_ltp_syscalls failed with timeout multiplier = 3 on D-KVM

2019-05-31 Thread Colin Ian King
I suspect this is due to lack of entropy on the machine.

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

Title:
  getrandom02 from ubuntu_ltp_syscalls failed with timeout multiplier =
  3 on D-KVM

Status in ubuntu-kernel-tests:
  New
Status in linux-kvm package in Ubuntu:
  New

Bug description:
  Even with the timeout multiplier set to 3, the test is still failing:

   Waiting for pid 1892 for 21600 seconds
   Checking virt-what to see if we need to set LTP_TIMEOUT_MUL...
   Running in VM, set timeout multiplier LTP_TIMEOUT_MUL=3 (lp:1797327)
   == Test Suite Summary ==
   7 test cases failed
   0 test cases blacklisted
   Failed test cases : acct01 getrandom02 msgstress03 quotactl01 quotactl02 
quotactl03 sync_file_range02 

  startup='Thu May 30 21:36:06 2019'
  tst_test.c:1096: INFO: Timeout per run is 0h 15m 00s
  getrandom02.c:72: PASS: getrandom returned 256
  Test timeouted, sending SIGKILL!
  tst_test.c:1136: INFO: If you are running on slow machine, try exporting 
LTP_TIMEOUT_MUL > 1
  tst_test.c:1137: BROK: Test killed! (timeout?)

  Summary:
  passed   1
  failed   0
  skipped  0
  warnings 0
  tag=getrandom02 stime=1559252166 dur=900 exit=exited stat=2 core=no cu=0 cs=0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1831229/+subscriptions

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


[Kernel-packages] [Bug 1831232] [NEW] Ubuntu 18.04 won't boot - failed to connect to lvmetad

2019-05-31 Thread Raphael Mankin
Public bug reported:

This bug report relates to a machine running 18.04, not the one I am
submitting the report from.

On 30 May The Software Updater prompted me to update. Included in the
update were initramfs components. I now cannot boot the machine.

After decrypting the root file system, instead of being prompted for the
pass-phrase to decrypt the swap, I get the message "cannot connect to
lvmetad: falling back to device scanning". This repeats for a while
until I am dropped into a recovery shell of some sort from which I
cannot access the root disk.

Blocker. My machine is unusable.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-generic 4.15.0.48.50
ProcVersionSignature: Ubuntu 4.15.0-48.51-generic 4.15.18
Uname: Linux 4.15.0-48-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.6
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  gdm2433 F pulseaudio
  raph   8920 F pulseaudio
 /dev/snd/controlC0:  gdm2433 F pulseaudio
Date: Fri May 31 12:08:33 2019
HibernationDevice: RESUME=UUID=2538baa4-d43e-4876-8d94-dd3221894bac
InstallationDate: Installed on 2018-02-09 (475 days ago)
InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
MachineType: LENOVO 20CJS0UU00
ProcEnviron:
 LANGUAGE=en_GB:en
 TERM=xterm-256color
 PATH=(custom, no user)
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-48-generic 
root=/dev/mapper/xubuntu--vg-root ro quiet splash vt.handoff=1
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
 linux-restricted-modules-4.15.0-48-generic N/A
 linux-backports-modules-4.15.0-48-generic  N/A
 linux-firmware 1.173.5
SourcePackage: linux
UpgradeStatus: Upgraded to bionic on 2018-09-12 (260 days ago)
dmi.bios.date: 09/13/2017
dmi.bios.vendor: LENOVO
dmi.bios.version: N11ET42W (1.18 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20CJS0UU00
dmi.board.vendor: LENOVO
dmi.board.version: SDK0E50510 WIN
dmi.chassis.asset.tag: R90G3N7R
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias: 
dmi:bvnLENOVO:bvrN11ET42W(1.18):bd09/13/2017:svnLENOVO:pn20CJS0UU00:pvrThinkPadT550:rvnLENOVO:rn20CJS0UU00:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone:
dmi.product.family: ThinkPad T550
dmi.product.name: 20CJS0UU00
dmi.product.version: ThinkPad T550
dmi.sys.vendor: LENOVO

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


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

Title:
  Ubuntu 18.04 won't boot - failed to connect to lvmetad

Status in linux package in Ubuntu:
  New

Bug description:
  This bug report relates to a machine running 18.04, not the one I am
  submitting the report from.

  On 30 May The Software Updater prompted me to update. Included in the
  update were initramfs components. I now cannot boot the machine.

  After decrypting the root file system, instead of being prompted for
  the pass-phrase to decrypt the swap, I get the message "cannot connect
  to lvmetad: falling back to device scanning". This repeats for a while
  until I am dropped into a recovery shell of some sort from which I
  cannot access the root disk.

  Blocker. My machine is unusable.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-generic 4.15.0.48.50
  ProcVersionSignature: Ubuntu 4.15.0-48.51-generic 4.15.18
  Uname: Linux 4.15.0-48-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  gdm2433 F pulseaudio
raph   8920 F pulseaudio
   /dev/snd/controlC0:  gdm2433 F pulseaudio
  Date: Fri May 31 12:08:33 2019
  HibernationDevice: RESUME=UUID=2538baa4-d43e-4876-8d94-dd3221894bac
  InstallationDate: Installed on 2018-02-09 (475 days ago)
  InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: LENOVO 20CJS0UU00
  ProcEnviron:
   LANGUAGE=en_GB:en
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-48-generic 
root=/dev/mapper/xubuntu--vg-root ro quiet splash vt.handoff=1
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-48-generic N/A
   linux-backports-modules-4.15.0-48-generic  N/A
   linux-firmware 1.173.5
  SourcePackage: linux
  UpgradeStatus: Upgraded to bionic on 2018-09-12 (260 days ago)
  dmi.bios.date: 

[Kernel-packages] [Bug 1830151] Re: ebb: cycles_test in powerpc from ubuntu_kernel_selftests failed on B-hwe P9

2019-05-31 Thread Po-Hsu Lin
This test should be run exclusively on Power8:
https://github.com/torvalds/linux/commit/39fcfb911c3862f1366ef84efbea10aff59421c2

** Changed in: ubuntu-kernel-tests
 Assignee: (unassigned) => Po-Hsu Lin (cypressyew)

** Changed in: ubuntu-kernel-tests
   Status: New => In Progress

** Package changed: linux-hwe (Ubuntu) => linux (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/1830151

Title:
  ebb: cycles_test in powerpc from ubuntu_kernel_selftests failed on
  B-hwe P9

Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  New

Bug description:
  This test has passed with Cosmic kernel on the same node ("baltar"),
  but not with the 4.18 kernel on Bionic.

   selftests: ebb: cycles_test
   
   test: cycles
   tags: git_version:unknown
   EBB Handler is at 0x10004170
   ebb_state:
   ebb_count = 10
   spurious = 0
   negative = 0
   no_overflow = 0
   pmc[1] count = 0x2843f
   pmc[2] count = 0x0
   pmc[3] count = 0x0
   pmc[4] count = 0x0
   pmc[5] count = 0x0
   pmc[6] count = 0x0
   HW state:
   MMCR0 0x8400 FC PMAE
   MMCR2 0x
   EBBHR 0x10004170
   BESCR 0x8000 GE
   PMC1 0x4000
   PMC2 0x
   PMC3 0x
   PMC4 0x
   PMC5 0x00028b3f
   PMC6 0x0002ac80
   SIAR 0x100035d4
   Trace buffer dump:
   address 0x71a628a2
   tail 0x71a628a201f6
   size 1048576
   overflow false
   Content:
   [0]: counter = 1
   [1]: register SPRN_MMCR0 = 0x8080
   [2]: register SPRN_PMC1 = 0x8004
   [3]: counter = 2
   [4]: register SPRN_MMCR0 = 0x8080
   [5]: register SPRN_PMC1 = 0x8004
   [6]: counter = 3
   [7]: register SPRN_MMCR0 = 0x8080
   [8]: register SPRN_PMC1 = 0x8004
   [FAIL] Test FAILED on line 52
   [9]: counter = 4
   [10]: register SPRN_MMCR0 = 0x8080
   [11]: register SPRN_PMC1 = 0x8004
   [12]: counter = 5
   [13]: register SPRN_MMCR0 = 0x8080
   [14]: register SPRN_PMC1 = 0x8004
   [15]: counter = 6
   [16]: register SPRN_MMCR0 = 0x8080
   [17]: register SPRN_PMC1 = 0x8004
   [18]: counter = 7
   [19]: register SPRN_MMCR0 = 0x8080
   [20]: register SPRN_PMC1 = 0x8004
   [21]: counter = 8
   [22]: register SPRN_MMCR0 = 0x8080
   [23]: register SPRN_PMC1 = 0x8004
   [24]: counter = 9
   [25]: register SPRN_MMCR0 = 0x8080
   [26]: register SPRN_PMC1 = 0x8004
   [27]: counter = 10
   [28]: register SPRN_MMCR0 = 0x8080
   [29]: register SPRN_PMC1 = 0x8004
   [30]: register SPRN_PMC1 = 0x4417
   PMC1 count (0x2843f) above upper limit 0x283e8 (+0x57)
   failure: cycles
   not ok 1..3 selftests: ebb: cycles_test [FAIL]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1830151/+subscriptions

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


  1   2   >