date:20190702

All tasks have been completed and the bug is being set to Fix Released


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

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

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

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

Status in Kernel SRU Workflow:
  Fix Released
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 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:
  Invalid
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:
  Invalid
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: 1833987
  phase: Complete
  phase-changed: Tuesday, 02. July 2019 06:32 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  variant: debs

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

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

[Kernel-packages] [Bug 1833405] Re: add firmware and topology file for sound sof driver [cml/cnl]

2019-07-02 Thread Hui Wang

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

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

Title:
  add firmware and topology file for sound sof driver [cml/cnl]

Status in HWE Next:
  New
Status in linux-firmware package in Ubuntu:
  Fix Released
Status in linux-firmware source package in Bionic:
  Fix Committed
Status in linux-firmware source package in Cosmic:
  Fix Committed
Status in linux-firmware source package in Disco:
  Fix Committed
Status in linux-firmware source package in Eoan:
  Fix Released

Bug description:
  [Impact]
  We have a couple dell and lenovo laptops which have dmic directly connected
  to PCH, this needs intel sof driver to work, and intel sof driver is merged
  oem-osp1-b kernel and it needs to load firmware and topology file to work.

  [Fix]
  Intel provides two binary files to us, one is firmware, the other is
  topology file, these two files are built from
  https://github.com/thesofproject/sof.git, and the license is BSD 3.

  [Test Case]
  put the firmware and topology to rootfs and boot with the oem-osp1-b
  kernel on those machines, the sof driver works well.

  [Regression Risk]
  Low. just adding two new binary files, no change to existing files.

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

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

[Kernel-packages] [Bug 1835001] [NEW] System does not auto detect disconnection of external monitor

2019-07-02 Thread Chih-Hsyuan Ho

Public bug reported:

Summary:
System does not auto detect disconnection of external monitor

Steps to reproduce:
1. install dell-bto-bionic-beaver-lancel-X84-20190507-42.iso and boot into OS
2. open "system settings > display settings"
3. connect laptop to an external HDMI monitor via HDMI port & cable
4. unplug the HDMI cable
5. check if "display settings" automatically detects the removal of the 
external monitor

Expected result:
display settings should automatically detect the removal of external monitor 
when unplugging the HDMI cable

Actual result:
System does not automatically detect the removal of the external monitor when 
HDMI cable is removed.
Sound setting also list HDMI audio in output tab after removal external monitor.

Failure rate:
2/10 to 1/10

** Affects: hwe-next/bionic
 Importance: Undecided
 Status: New

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

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

** Tags added: verification-needed-bionic

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

Title:
  System does not auto detect disconnection of external monitor

Status in HWE Next bionic series:
  New
Status in linux-oem package in Ubuntu:
  New

Bug description:
  Summary:
  System does not auto detect disconnection of external monitor

  Steps to reproduce:
  1. install dell-bto-bionic-beaver-lancel-X84-20190507-42.iso and boot into OS
  2. open "system settings > display settings"
  3. connect laptop to an external HDMI monitor via HDMI port & cable
  4. unplug the HDMI cable
  5. check if "display settings" automatically detects the removal of the 
external monitor

  Expected result:
  display settings should automatically detect the removal of external monitor 
when unplugging the HDMI cable

  Actual result:
  System does not automatically detect the removal of the external monitor when 
HDMI cable is removed.
  Sound setting also list HDMI audio in output tab after removal external 
monitor.

  Failure rate:
  2/10 to 1/10

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

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

[Kernel-packages] [Bug 1834114] Re: AX88772A USB to Ethernet dongle doesn't work

** Changed in: linux (Ubuntu Cosmic)
   Status: Fix Committed => Won't Fix

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

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

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

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

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

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

Title:
  AX88772A USB to Ethernet dongle doesn't work

Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Cosmic:
  Won't Fix
Status in linux source package in Disco:
  In Progress
Status in linux source package in Eoan:
  Triaged

Bug description:
  [Impact]
  There are 2 asix drivers in the kernel, they are drivers/net/usb/asix and 
drivers/net/phy/asix. It leads to the compilation race condition that one 
overwrites the other asix.mod in .tmp_version directory. This affects the USB 
dongle if the "phy" one wins.

  T:  Bus=01 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#=  7 Spd=480 MxCh= 0
  D:  Ver= 2.00 Cls=ff(vend.) Sub=ff Prot=00 MxPS=64 #Cfgs=  1
  P:  Vendor=0b95 ProdID=7720 Rev=00.01
  S:  Manufacturer=ASIX Elec. Corp.
  S:  Product=AX88772A
  S:  SerialNumber=000527
  C:  #Ifs= 1 Cfg#= 1 Atr=a0 MxPwr=250mA
  I:  If#= 0 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=ff Prot=00 Driver=asix

  [Fix]
  The same name asix has been introduced since v4.18-rc1 by this commit
 31dd83b96641 net-next: phy: new Asix Electronics PHY driver
  the new commit fix this issue by renaming it
 a9520543b123 net: phy: rename Asix Electronics PHY driver

  [Test]
  Verified on my own ASIX USB Ethernet dongle.

  [Regression Potential]
  Low, it only rename the module name, no code change.

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

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

[Kernel-packages] [Bug 1835001] Re: System does not auto detect disconnection of external monitor

2019-07-02 Thread You-Sheng Yang

** Description changed:

- [Impact]
- The affected systems do not always detect the unplug event of an HDMI cable 
and leave the desktop in an incorrect state. 
- 
- [Fix]
- Patchset from https://patchwork.freedesktop.org/series/62965/
- 
- [Test]
- Verified on multiple affected OEM platforms and HDMI cable removal can be 
reliably processed with the fix
- 
- [Regression Potential]
- TBD
- 
- == Original Bug Description ==
  Summary:
  System does not auto detect disconnection of external monitor
  
  Steps to reproduce:
  1. install dell-bto-bionic-beaver-lancel-X84-20190507-42.iso and boot into OS
  2. open "system settings > display settings"
  3. connect laptop to an external HDMI monitor via HDMI port & cable
  4. unplug the HDMI cable
  5. check if "display settings" automatically detects the removal of the 
external monitor
  
  Expected result:
  display settings should automatically detect the removal of external monitor 
when unplugging the HDMI cable
  
  Actual result:
  System does not automatically detect the removal of the external monitor when 
HDMI cable is removed.
  Sound setting also list HDMI audio in output tab after removal external 
monitor.
  
  Failure rate:
  2/10 to 1/10

** Also affects: hwe-next/bionic
   Importance: Undecided
   Status: New

** Tags removed: verification-needed-bionic

** No longer affects: hwe-next

** No longer affects: hwe-next/bionic

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

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

Title:
  System does not auto detect disconnection of external monitor

Status in linux-oem package in Ubuntu:
  New
Status in linux-oem source package in Bionic:
  New

Bug description:
  Summary:
  System does not auto detect disconnection of external monitor

  Steps to reproduce:
  1. install dell-bto-bionic-beaver-lancel-X84-20190507-42.iso and boot into OS
  2. open "system settings > display settings"
  3. connect laptop to an external HDMI monitor via HDMI port & cable
  4. unplug the HDMI cable
  5. check if "display settings" automatically detects the removal of the 
external monitor

  Expected result:
  display settings should automatically detect the removal of external monitor 
when unplugging the HDMI cable

  Actual result:
  System does not automatically detect the removal of the external monitor when 
HDMI cable is removed.
  Sound setting also list HDMI audio in output tab after removal external 
monitor.

  Failure rate:
  2/10 to 1/10

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

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

[Kernel-packages] [Bug 1834114] Re: AX88772A USB to Ethernet dongle doesn't work

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

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

Title:
  AX88772A USB to Ethernet dongle doesn't work

Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Cosmic:
  Won't Fix
Status in linux source package in Disco:
  Fix Committed
Status in linux source package in Eoan:
  Triaged

Bug description:
  [Impact]
  There are 2 asix drivers in the kernel, they are drivers/net/usb/asix and 
drivers/net/phy/asix. It leads to the compilation race condition that one 
overwrites the other asix.mod in .tmp_version directory. This affects the USB 
dongle if the "phy" one wins.

  T:  Bus=01 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#=  7 Spd=480 MxCh= 0
  D:  Ver= 2.00 Cls=ff(vend.) Sub=ff Prot=00 MxPS=64 #Cfgs=  1
  P:  Vendor=0b95 ProdID=7720 Rev=00.01
  S:  Manufacturer=ASIX Elec. Corp.
  S:  Product=AX88772A
  S:  SerialNumber=000527
  C:  #Ifs= 1 Cfg#= 1 Atr=a0 MxPwr=250mA
  I:  If#= 0 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=ff Prot=00 Driver=asix

  [Fix]
  The same name asix has been introduced since v4.18-rc1 by this commit
 31dd83b96641 net-next: phy: new Asix Electronics PHY driver
  the new commit fix this issue by renaming it
 a9520543b123 net: phy: rename Asix Electronics PHY driver

  [Test]
  Verified on my own ASIX USB Ethernet dongle.

  [Regression Potential]
  Low, it only rename the module name, no code change.

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

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

[Kernel-packages] [Bug 1832623] Re: [UBUNTU] kernel: Fix gcm-aes-s390 wrong scatter-gather list processing

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

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

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

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

Title:
  [UBUNTU] kernel: Fix gcm-aes-s390 wrong scatter-gather list processing

Status in Ubuntu on IBM z Systems:
  In Progress
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Bionic:
  Fix Committed
Status in linux source package in Cosmic:
  Fix Committed
Status in linux source package in Disco:
  Fix Committed

Bug description:
  SRU Justification:
  ==

  [Impact]

  * Wrong encryption/decryption with gcm-aes-s390 on z14.

  * gcm-aes-s390 does not process scatter-gather input and output lists
  correctly if list entries of sizes being not multiples of the
  blocksize (16 bytes) are used, which results in wrong calculations.

  [Fix]

  * bef9f0ba300a55d79a69aa172156072182176515 bef9f0b "s390/crypto: fix
  gcm-aes-s390 selftest failures"

  [Test Case]

  * z14 with kernel >= 5.1 needed

  * If disabled, enable the crypto self tests.

  * Monitor syslog during modprobe of the aes_s390 kernel module. As
  this module usually gets automatically inserted during system startup
  you may need to unload the aes_s390 kernel module before re-inserting
  it.

  * Without the fix a message like "kernel: alg: aead: gcm-aes-s390
  encryption test failed (wrong result) on test vector 1,..." will show
  up.

  * With the fix, all selftests will pass and nothing is reported in
  syslog.

  [Regression Potential]

  * The regression potential can be considered as low since this is
  purely s390x specific

  * affects one mode of the hardware crypto facility CPACF

  * and happens only on z14 (since z14 is the only model that currently
  supports the gcm-aes-s390 mode).

  * Applications using aes-gcm via the AF_ALG interface are not affected
  since this API ensures scatter/gather list entries with chunk sizes in
  multiples of 16 bytes.

  * Changes are limited to a single s390x crypto file
  /arch/s390/crypto/aes_s390.c

  [Other Info]

  * Problem was found during tests at IBM and is a so called 'preventive
  fix'

  * Since this affects z14 only, final test need to be done by IBM.

  * Applied cleanly for me on bionic master-next.
  __

  Description:   kernel: Fix gcm-aes-s390 wrong scatter-gather list processing
  Symptom:   gcm-aes-s390 wrong en/decryption processing
  Problem:   The current gcm aes s390 implementation does not process
     scatter-gather input and output lists correct when list
     entries with sizes not multiples of the blocksize of 16
     bytes are used. Result may be wrong calculated encrypted
     or decrypted data.
     This can only happen on z14 (this is the only machine
     which supports aes-gcm in hardware via CPACF). Please note
     that applications using aes-gcm via the AF_ALG interface are
     not affected as this API ensures scatter/gather list entries
     with chunk sizes in multiples of 16 bytes. However, all
     exploiters of aes-gcm within the kernel may be affected.
  Solution:  Rework of the scatter/gather walk within the aes_s390 kernel
     module implementation with the goal to support any list
     entry size.
  Reproduction:  With kernel 5.1 there has been an improvement on the crypto
     selftests. There are now tests run with fragmented
     scatter/gather lists. So:
     1. You need at least a z14 and kernel >= 5.1.
     2. If disabled, enable the crypto self tests.
     3. Watch for syslog entries during modprobe of the aes_s390
    kernel module. As this module usually gets automatically
    inserted during system startup you may need to unload the
    aes_s390 kernel module before re-inserting it.
     4. Without the fix something like
    "kernel: alg: aead: gcm-aes-s390 encryption test failed
    (wrong result) on test vector 1,..."
    will show up. With the fix, all selftests will pass and
    nothing is reported in syslog.

  Component: kernel
  Upstream-ID:   bef9f0ba300a55d79a69aa172156072182176515

  This request is targeted for 19.10, but should also be applied to
  18.04 and 19.04

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

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

[Kernel-packages] [Bug 1834840] Re: Laptop certified with a previous version of Ubuntu fails to boot 59% of the time

2019-07-02 Thread Pierre Equoy

** Description changed:

+ =[Edit July 2nd, 08:06UTC]=
+ 
+ Trying to boot from a 18.04.2 live USB or 19.04 live USB exhibits the
+ same kind of issue, no matter if Secure Boot is enabled or not in the
+ BIOS.
+ 
+ No matter Secure Boot is enabled or not in the BIOS, I briefly see
+ "Booting in insecure mode", then "error: file /boot/ not found" before
+ showing GRUB menu.
+ 
+ I tried the 16.04 OEM image and it works reliably. I can install it and
+ once installed, I can boot into the system 10 times out of 10.
+ 
+ =[Original Description]=
+ 
  Device: Dell Inspiron 7370
  BIOS: 1.2.0
  
  This device was certified with 16.04:
  https://certification.ubuntu.com/hardware/201704-25503/
  
  I installed Ubuntu 19.04 and although it installed properly, about 50%
  of the time, the device won't boot at all. I need to shut it down and
  restart it.
  
  Steps to reproduce
  --
  
  In the BIOS, make sure
  - SATA mode is set to AHCI
  - Secure Boot is enabled
  
  1. Install Ubuntu 19.04 stock. I selected the following options:
  - Erase disk and install Ubuntu
  - Full disk encryption
  - Minimal install
  - Install 3rd party drivers (this requires to enroll MOK key at the next 
reboot using a password)
  
  2. After installation, boot into Ubuntu.
  
  Expected results
  
  
  The device boots up Ubuntu reliably.
  
  Actual results
  --
  
  About 50% of the time, the screen remains dark purple and nohting moves.
  I have to manually shut it down and re-start it until it ends up booting
  Ubuntu.
  
  It looks like it stops at step:
  
  "Loading initial ramdisk..."
  
  Failure rate
  
  
  I booted 22 times. It failed to boot 13 times and booted up properly 9 times.
  -> failure rate = 59 %
  
  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: linux-image-5.0.0-20-generic 5.0.0-20.21
  ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8
  Uname: Linux 5.0.0-20-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
-  USERPID ACCESS COMMAND
-  /dev/snd/controlC0:  pieq   1846 F pulseaudio
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC0:  pieq   1846 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jul  1 17:38:59 2019
  InstallationDate: Installed on 2019-07-01 (0 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  Lsusb:
-  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
-  Bus 001 Device 003: ID 8087:0a2a Intel Corp. 
-  Bus 001 Device 002: ID 0bda:58f5 Realtek Semiconductor Corp. 
-  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
+  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
+  Bus 001 Device 003: ID 8087:0a2a Intel Corp.
+  Bus 001 Device 002: ID 0bda:58f5 Realtek Semiconductor Corp.
+  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 7370
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-20-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash
  RelatedPackageVersions:
-  linux-restricted-modules-5.0.0-20-generic N/A
-  linux-backports-modules-5.0.0-20-generic  N/A
-  linux-firmware1.178.1
+  linux-restricted-modules-5.0.0-20-generic N/A
+  linux-backports-modules-5.0.0-20-generic  N/A
+  linux-firmware1.178.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/31/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.0
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.0:bd08/31/2017:svnDellInc.:pnInspiron7370:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 7370
  dmi.product.sku: 07E9
  dmi.sys.vendor: Dell Inc.

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

Title:
  Laptop certified with a previous version of Ubuntu fails to boot 59%
  of the time

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  =[Edit July 2nd, 08:06UTC]=

  Trying to boot from a 18.04.2 live USB or 19.04 live USB exhibits the
  same kind of issue, no matter if Secure Boot is enabled or not in the
  BIOS.

  No matter Secure Boot is enabled or not in the BIOS, I briefly see
  "Booting in insecure mode", then "error: file /boot/ not found" before
  showing GRUB menu.

  I tried the 16.04 OEM image and it works reliably. I can install it
  and once installed, I can boot into the system 10 times out of 10.

  =[Original Description]=

  Device: Dell Inspiron 7370
  BIOS: 1.2.0

  This device was certified with 16.04:
  https://certification.ubuntu.com/hardware/201704-25503/

  I installed Ubuntu 19.04 and although it installed p

[Kernel-packages] [Bug 1831751] Re: rtlwifi: aggressive memory leak

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

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

Title:
  rtlwifi: aggressive memory leak

Status in Linux:
  Fix Released
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Cosmic:
  Fix Committed

Bug description:
  [Impact]

   * Upstream commit 0a9f8f0a1ba9 "rtlwifi: fix btmpinfo timeout while
  processing C2H_BT_INFO" fixed a timeout message by adding a fast path
  which allowed commands to skip the queue to be processed immediately.
  However, the fast path doesn't free the sk_buff when it completes;
  this results in a memory leak when commands are fast-tracked.

  [Test Case]

   * This was tested in the bug report on a RTL8723BE card. As the
  system is running, a memory leak is observed until it gets to the
  point where a reboot is necessary.

   * The following patch was applied and the ever-increasing memory
  consumption no longer experienced.

  [Regression Potential]

   * This was fixed in Linux 4.20 and participants in both the LP bug
  and the Github issue reports [1] have reported positive test results
  with just this patch applied.

  [1] https://github.com/lwfinger/rtlwifi_new/issues/401

  
  Original bug description follows:
  ---

  Hey, i got a memory leak on Ubuntu 18.04.2 even in console mode (no X/GUI) 
the memory usage grows slowly to take all the available RAM when i let the 
computer running over the night (with just top and irssi), and i have to reboot 
to get things back to normal. I didn't have this problem on Ubuntu 17.10 but i 
was still flooded with message about pci aer taking lots of disk space in the 
logs, but pci=noaer fixed this problem and i had no memory leak.
  The computer is a common laptop: HP Pavilion.

  ---
  Kernel log gets spammed with AERs so owner uses "pci=noaer"; that was briefly 
disabled to capture the AERs.

  Memory seems to be consumed (~6 GB of 8GB) just by leaving PC
  overnight booted just to console (systemd.unit=multi-user.target).

  The memory leak doesn't affect Windows but owner is going to check
  Windows Event Log for signs of AERs being logged.

  ---

  Original suspect of AER is not guilty.

  This turns out to be a bug in the rtlwifi driver where in some rare
  circumstances it fails to free an sk_buf.

  Reporter has been testing a DKMS build of rtlwfi with the fix applied
  and confirms it solves the issue.

  Upstream has the commit. Can we get this cherry-picked into all
  releases?

  commit 8cfa272b0d321160ebb5b45073e39ef0a6ad73f2
  Author: Larry Finger 
  Date:   Sat Nov 17 20:55:03 2018 -0600

  rtlwifi: Fix leak of skb when processing C2H_BT_INFO

  With commit 0a9f8f0a1ba9 ("rtlwifi: fix btmpinfo timeout while processing
  C2H_BT_INFO"), calling rtl_c2hcmd_enqueue() with rtl_c2h_fast_cmd() true,
  the routine returns without freeing that skb, thereby leaking it.

  This issue has been discussed at 
https://github.com/lwfinger/rtlwifi_new/issues/401
  and the fix tested there.

  Fixes: 0a9f8f0a1ba9 ("rtlwifi: fix btmpinfo timeout while processing 
C2H_BT_INFO")
  Reported-and-tested-by: Francisco Machado Magalhães Neto 

  Cc: Francisco Machado Magalhães Neto 
  Cc: Ping-Ke Shih 
  Cc: Stable  # 4.18+
  Signed-off-by: Larry Finger 
  Signed-off-by: Kalle Valo 

  diff --git a/drivers/net/wireless/realtek/rtlwifi/base.c 
b/drivers/net/wireless/realtek/rtlwifi/base.c
  index f4122c8fdd97..ef9b502ce576 100644
  --- a/drivers/net/wireless/realtek/rtlwifi/base.c
  +++ b/drivers/net/wireless/realtek/rtlwifi/base.c
  @@ -2289,6 +2289,7 @@ void rtl_c2hcmd_enqueue(struct ieee80211_hw *hw, struct 
sk_buff *skb)

  if (rtl_c2h_fast_cmd(hw, skb)) {
  rtl_c2h_content_parsing(hw, skb);
  +   kfree_skb(skb);
  return;
  }

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

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

[Kernel-packages] [Bug 1832625] Re: [UBUNTU] pkey: Indicate old mkvp only if old and curr. mkvp are different

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

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

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

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

Title:
  [UBUNTU] pkey: Indicate old mkvp only if old and curr. mkvp are
  different

Status in Ubuntu on IBM z Systems:
  In Progress
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Bionic:
  Fix Committed
Status in linux source package in Cosmic:
  Fix Committed
Status in linux source package in Disco:
  Fix Committed

Bug description:
  SRU Justification:
  ==

  [Impact]

  * 'zkey validate' shows wrong information about master key registers

  * this might lead to unsuccessful usage of pkeys, although the master
  key and the derived keys are correct

  [Fix]

  * ebb7c695d3bc7a4986b92edc8d9ef43491be183e ebb7c69 "pkey: Indicate old
  mkvp only if old and current mkvp are different"

  [Test Case]

  * set a CCA master key

  * generate a pkey

  * 'change' (or better set) the current CCA master key to the exact
  same master key again which is currently in use

  * execute a 'zkey validate'

  [Regression Potential]

  * The regression potential can be considered as very low since this is
  purely s390x specific

  * changes are limited to a single file
  (drivers/s390/crypto/pkey_api.c)

  * patch changes only one line (actually expands an if stmt)

  * and all this happens only in a very specific situation (in case a
  new master key was set, using the same key as before)

  [Other Info]

  * Problem was found during tests at IBM and is a so called 'preventive
  fix'

  __

  Description:   pkey: Indicate old mkvp only if old and curr. mkvp are
  different

  Symptom:   zkey validate shows wrong information about master key
  registers

  Problem:   When the CCA master key is set twice with the same master key,
     then the old and the current master key are the same and thus
     the verification patterns are the same, too. The check to 
report
     if a secure key is currently wrapped by the old master key
     erroneously reports old mkvp in this case.

  Solution:  Fix this by checking current and old mkvp and report OLD only 
if
     current and old mkvp are different.

  Reproduction:  Change the CCA master key but set the exact same master
  key that is already used. Then do a 'zkey validate' command on a
  secure key

  Component: kernel 5.1 rc1
  Upstream-ID:   ebb7c695d3bc7a4986b92edc8d9ef43491be183e

  This fix will be provided with kernel >=5.1 , will be integrate in 19.10 by 
default.
  But should also be applied to 18.04 and 19.04

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

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

[Kernel-packages] [Bug 1821625] Re: systemd 237-3ubuntu10.14 ADT test failure on Bionic ppc64el (test-seccomp)

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

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

Title:
  systemd 237-3ubuntu10.14 ADT test failure on Bionic ppc64el (test-
  seccomp)

Status in libseccomp package in Ubuntu:
  Incomplete
Status in linux package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Invalid
Status in libseccomp source package in Bionic:
  Incomplete
Status in linux source package in Bionic:
  Fix Committed
Status in systemd source package in Bionic:
  Invalid

Bug description:
  Starting with systemd 237-3ubuntu10.14, the testcase test-seccomp is
  failing on Bionic on ppc64el with the error messages:

  Operating on architecture: ppc
  Failed to add n/a() rule for architecture ppc, skipping: Bad address
  Operating on architecture: ppc64
  Failed to add n/a() rule for architecture ppc64, skipping: Bad address
  Operating on architecture: ppc64-le
  Failed to add n/a() rule for architecture ppc64-le, skipping: Numerical 
argument out of domain
  Assertion 'p == MAP_FAILED' failed at ../src/test/test-seccomp.c:413, 
function test_memory_deny_write_execute_mmap(). Aborting.
  memoryseccomp-mmap terminated by signal ABRT.
  Assertion 'wait_for_terminate_and_check("memoryseccomp-mmap", pid, WAIT_LOG) 
== EXIT_SUCCESS' failed at ../src/test/test-seccomp.c:427, function 
test_memory_deny_write_execute_mmap(). Aborting.
  Aborted (core dumped)
  FAIL: test-seccomp (code: 134)

  Full logs at:
  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/ppc64el/s/systemd/20190302_025135_d0e38@/log.gz

  The testcase passed with systemd version 237-3ubuntu10.13 running on the same 
4.15.0-45 kernel on ppc64el:
  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/ppc64el/s/systemd/20190228_154406_6b12f@/log.gz

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

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

[Kernel-packages] [Bug 1832625] Re: [UBUNTU] pkey: Indicate old mkvp only if old and curr. mkvp are different

2019-07-02 Thread Frank Heimes

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

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

Title:
  [UBUNTU] pkey: Indicate old mkvp only if old and curr. mkvp are
  different

Status in Ubuntu on IBM z Systems:
  Fix Committed
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Bionic:
  Fix Committed
Status in linux source package in Cosmic:
  Fix Committed
Status in linux source package in Disco:
  Fix Committed

Bug description:
  SRU Justification:
  ==

  [Impact]

  * 'zkey validate' shows wrong information about master key registers

  * this might lead to unsuccessful usage of pkeys, although the master
  key and the derived keys are correct

  [Fix]

  * ebb7c695d3bc7a4986b92edc8d9ef43491be183e ebb7c69 "pkey: Indicate old
  mkvp only if old and current mkvp are different"

  [Test Case]

  * set a CCA master key

  * generate a pkey

  * 'change' (or better set) the current CCA master key to the exact
  same master key again which is currently in use

  * execute a 'zkey validate'

  [Regression Potential]

  * The regression potential can be considered as very low since this is
  purely s390x specific

  * changes are limited to a single file
  (drivers/s390/crypto/pkey_api.c)

  * patch changes only one line (actually expands an if stmt)

  * and all this happens only in a very specific situation (in case a
  new master key was set, using the same key as before)

  [Other Info]

  * Problem was found during tests at IBM and is a so called 'preventive
  fix'

  __

  Description:   pkey: Indicate old mkvp only if old and curr. mkvp are
  different

  Symptom:   zkey validate shows wrong information about master key
  registers

  Problem:   When the CCA master key is set twice with the same master key,
     then the old and the current master key are the same and thus
     the verification patterns are the same, too. The check to 
report
     if a secure key is currently wrapped by the old master key
     erroneously reports old mkvp in this case.

  Solution:  Fix this by checking current and old mkvp and report OLD only 
if
     current and old mkvp are different.

  Reproduction:  Change the CCA master key but set the exact same master
  key that is already used. Then do a 'zkey validate' command on a
  secure key

  Component: kernel 5.1 rc1
  Upstream-ID:   ebb7c695d3bc7a4986b92edc8d9ef43491be183e

  This fix will be provided with kernel >=5.1 , will be integrate in 19.10 by 
default.
  But should also be applied to 18.04 and 19.04

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

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

[Kernel-packages] [Bug 1833132] Re: net: hns: Fix loopback test failed at copper ports

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

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

Title:
  net: hns: Fix loopback test failed at copper ports

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

Bug description:
  [Impact]
  The ethtool offline test always fails on HNS devices w/ copper ports.

  [Test Case]
  sudo ethtool -t enahisic2i1 offline

  [Fix]
  2e1f164861e50 net: hns: Fix loopback test failed at copper ports

  [Regression Risk]
  Fix is restricted to the hns driver, which is the driver for the nics on the 
Hi1616 SoC. Regressions would therefore be limited to platforms using this SoC, 
such as the HiSilicon D05 board.

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

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

[Kernel-packages] [Bug 1833140] Re: hns: fix ICMP6 neighbor solicitation messages discard problem

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

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

Title:
  hns: fix ICMP6 neighbor solicitation messages discard problem

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

Bug description:
  [Impact]
  ICMP6 neighbor solicitation messages are discarded.

  [Test Case]
  Regression tested only

  [Fix]
  ea401685a20b5 net: hns: fix unsigned comparison to less than zero
  f058e46855dcb net: hns: fix ICMP6 neighbor solicitation messages discard 
problem

  [Regression Risk]
  Fix is restricted to the hns driver, which is the driver for the nics on the 
Hi1616 SoC. Regressions would therefore be limited to platforms using this SoC, 
such as the HiSilicon D05 board.

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

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

[Kernel-packages] [Bug 1833147] Re: hns: attempt to restart autoneg when disabled should report error

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

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

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

Title:
  hns: attempt to restart autoneg when disabled should report error

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]
  Asking the driver to restart autonegotiation silently fails when 
autonegotation has been disabled. It should report an error.

  [Test Case]
  sudo ethtool -s ethX autoneg off
  sudo ethtool -r ethX

  [Fix]
  ed29ca8b95925 net: hns: Restart autoneg need return failed when autoneg off

  [Regression Risk]
  Fix is restricted to the hns driver, which is the driver for the nics on the 
Hi1616 SoC. Regressions would therefore be limited to platforms using this SoC, 
such as the HiSilicon D05 board.

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

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

[Kernel-packages] [Bug 1831482] Re: VIMC module not available (CONFIG_VIDEO_VIMC not set)

2019-07-02 Thread Kieran Bingham

for reference, CONFIG_VIDEO_VIMC was added in
v4.11-rc5-253-gf2fe89061d79, which made it into Linux v4.12

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

Title:
  VIMC module not available (CONFIG_VIDEO_VIMC not set)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The Multimedia VIMC module provides a test interface for the linux-
  media media controller framework.

  This is useful for automated tests, and development of multimedia frameworks.
  Other components similar to this such as VIVID (CONFIG_VIDEO_VIVID=m) are 
enabled, but VIMC is missing from the linux-modules packages:

  $ grep VIMC /boot/config-*
  /boot/config-4.15.0-32-generic:# CONFIG_VIDEO_VIMC is not set
  /boot/config-4.17.9-041709-generic:# CONFIG_VIDEO_VIMC is not set
  /boot/config-4.18.4-041804-generic:# CONFIG_VIDEO_VIMC is not set
  /boot/config-4.18.7-041807-generic:# CONFIG_VIDEO_VIMC is not set
  /boot/config-5.0.0-13-generic:# CONFIG_VIDEO_VIMC is not set
  /boot/config-5.0.0-15-generic:# CONFIG_VIDEO_VIMC is not set

  
  Could this be enabled in future releases as a module please?

  I'm running Ubuntu 19.04, with Ubuntu 5.0.0-13.14-generic 5.0.6,
  however I believe this issue affects all current Ubuntu kernel
  releases.

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

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

[Kernel-packages] [Bug 1833138] Re: Fix occasional boot time crash in hns driver

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

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

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

Title:
  Fix occasional boot time crash in hns driver

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

Bug description:
  [Impact]
  On rare occasions, the hns driver will oops on start-up

  [Test Case]
  Reboot, watch for oops

  [Fix]
  c0b0984426814 net: hns: Fix probabilistic memory overwrite when HNS driver 
initialized

  [Regression Risk]
  Fix is restricted to the hns driver, which is the driver for the nics on the 
Hi1616 SoC. Regressions would therefore be limited to platforms using this SoC, 
such as the HiSilicon D05 board

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

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

[Kernel-packages] [Bug 1833140] Re: hns: fix ICMP6 neighbor solicitation messages discard problem

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

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

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

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

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

Title:
  hns: fix ICMP6 neighbor solicitation messages discard problem

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

Bug description:
  [Impact]
  ICMP6 neighbor solicitation messages are discarded.

  [Test Case]
  Regression tested only

  [Fix]
  ea401685a20b5 net: hns: fix unsigned comparison to less than zero
  f058e46855dcb net: hns: fix ICMP6 neighbor solicitation messages discard 
problem

  [Regression Risk]
  Fix is restricted to the hns driver, which is the driver for the nics on the 
Hi1616 SoC. Regressions would therefore be limited to platforms using this SoC, 
such as the HiSilicon D05 board.

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

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

[Kernel-packages] [Bug 1833136] Re: use-after-free in hns_nic_net_xmit_hw

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

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

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

Title:
   use-after-free in hns_nic_net_xmit_hw

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

Bug description:
  [Impact]
  KASAN detected a use-after-free condition, which could lead to memory 
corruption or a crash.

  [Test Case]
  Rebuild kernel w/ CONFIG_KASAN=y, look for errors in dmesg.

  [Fix]
  3a39a12ad364a net: hns: fix KASAN: use-after-free in hns_nic_net_xmit_hw()

  [Regression Risk]
  Fix is restricted to the hns driver, which is the driver for the nics on the 
Hi1616 SoC. Regressions would therefore be limited to platforms using this SoC, 
such as the HiSilicon D05 board.

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

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

[Kernel-packages] [Bug 1835001] Re: System does not auto detect disconnection of external monitor

2019-07-02 Thread Timo Aaltonen

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

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

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

Title:
  System does not auto detect disconnection of external monitor

Status in linux package in Ubuntu:
  Confirmed
Status in linux-oem package in Ubuntu:
  New
Status in linux-oem-osp1 package in Ubuntu:
  New
Status in linux source package in Bionic:
  Won't Fix
Status in linux-oem source package in Bionic:
  New
Status in linux-oem-osp1 source package in Bionic:
  New

Bug description:
  Summary:
  System does not auto detect disconnection of external monitor

  Steps to reproduce:
  1. install dell-bto-bionic-beaver-lancel-X84-20190507-42.iso and boot into OS
  2. open "system settings > display settings"
  3. connect laptop to an external HDMI monitor via HDMI port & cable
  4. unplug the HDMI cable
  5. check if "display settings" automatically detects the removal of the 
external monitor

  Expected result:
  display settings should automatically detect the removal of external monitor 
when unplugging the HDMI cable

  Actual result:
  System does not automatically detect the removal of the external monitor when 
HDMI cable is removed.
  Sound setting also list HDMI audio in output tab after removal external 
monitor.

  Failure rate:
  2/10 to 1/10

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

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

[Kernel-packages] [Bug 1832909] Re: Cache line contention prevents scaling of 100Gbps performance

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

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

Title:
  Cache line contention prevents scaling of 100Gbps performance

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Disco:
  Fix Committed
Status in linux source package in Eoan:
  In Progress

Bug description:
  [Impact]
  100Gbps network performance, as measured on an hns3 controller, doesn't scale 
as queue size goes up.

  [Test Case]
  Use a traffic generator instrument to generate load, using the SUT as an IP 
forwarder.

  19.04 today:

  8 queue 12 queue 16 queue 24 queue
  37G 45G 38G 33G

  With the patch applied:
  8 queue 12 queue 16 queue 24 queue
  37G 50G 47G 47G

  [Fix]
  14bd9a607f908 iommu/iova: Separate atomic variables to improve performance

  [Regression Risk]
  The patch makes no functional change, just reorders members of a structure. 
However, it is possible that this has unforeseen negative performance impacts 
on some platform.

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

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

[Kernel-packages] [Bug 1832623] Re: [UBUNTU] kernel: Fix gcm-aes-s390 wrong scatter-gather list processing

2019-07-02 Thread Frank Heimes

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

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

Title:
  [UBUNTU] kernel: Fix gcm-aes-s390 wrong scatter-gather list processing

Status in Ubuntu on IBM z Systems:
  Fix Committed
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Bionic:
  Fix Committed
Status in linux source package in Cosmic:
  Fix Committed
Status in linux source package in Disco:
  Fix Committed

Bug description:
  SRU Justification:
  ==

  [Impact]

  * Wrong encryption/decryption with gcm-aes-s390 on z14.

  * gcm-aes-s390 does not process scatter-gather input and output lists
  correctly if list entries of sizes being not multiples of the
  blocksize (16 bytes) are used, which results in wrong calculations.

  [Fix]

  * bef9f0ba300a55d79a69aa172156072182176515 bef9f0b "s390/crypto: fix
  gcm-aes-s390 selftest failures"

  [Test Case]

  * z14 with kernel >= 5.1 needed

  * If disabled, enable the crypto self tests.

  * Monitor syslog during modprobe of the aes_s390 kernel module. As
  this module usually gets automatically inserted during system startup
  you may need to unload the aes_s390 kernel module before re-inserting
  it.

  * Without the fix a message like "kernel: alg: aead: gcm-aes-s390
  encryption test failed (wrong result) on test vector 1,..." will show
  up.

  * With the fix, all selftests will pass and nothing is reported in
  syslog.

  [Regression Potential]

  * The regression potential can be considered as low since this is
  purely s390x specific

  * affects one mode of the hardware crypto facility CPACF

  * and happens only on z14 (since z14 is the only model that currently
  supports the gcm-aes-s390 mode).

  * Applications using aes-gcm via the AF_ALG interface are not affected
  since this API ensures scatter/gather list entries with chunk sizes in
  multiples of 16 bytes.

  * Changes are limited to a single s390x crypto file
  /arch/s390/crypto/aes_s390.c

  [Other Info]

  * Problem was found during tests at IBM and is a so called 'preventive
  fix'

  * Since this affects z14 only, final test need to be done by IBM.

  * Applied cleanly for me on bionic master-next.
  __

  Description:   kernel: Fix gcm-aes-s390 wrong scatter-gather list processing
  Symptom:   gcm-aes-s390 wrong en/decryption processing
  Problem:   The current gcm aes s390 implementation does not process
     scatter-gather input and output lists correct when list
     entries with sizes not multiples of the blocksize of 16
     bytes are used. Result may be wrong calculated encrypted
     or decrypted data.
     This can only happen on z14 (this is the only machine
     which supports aes-gcm in hardware via CPACF). Please note
     that applications using aes-gcm via the AF_ALG interface are
     not affected as this API ensures scatter/gather list entries
     with chunk sizes in multiples of 16 bytes. However, all
     exploiters of aes-gcm within the kernel may be affected.
  Solution:  Rework of the scatter/gather walk within the aes_s390 kernel
     module implementation with the goal to support any list
     entry size.
  Reproduction:  With kernel 5.1 there has been an improvement on the crypto
     selftests. There are now tests run with fragmented
     scatter/gather lists. So:
     1. You need at least a z14 and kernel >= 5.1.
     2. If disabled, enable the crypto self tests.
     3. Watch for syslog entries during modprobe of the aes_s390
    kernel module. As this module usually gets automatically
    inserted during system startup you may need to unload the
    aes_s390 kernel module before re-inserting it.
     4. Without the fix something like
    "kernel: alg: aead: gcm-aes-s390 encryption test failed
    (wrong result) on test vector 1,..."
    will show up. With the fix, all selftests will pass and
    nothing is reported in syslog.

  Component: kernel
  Upstream-ID:   bef9f0ba300a55d79a69aa172156072182176515

  This request is targeted for 19.10, but should also be applied to
  18.04 and 19.04

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

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

[Kernel-packages] [Bug 1832624] Re: [UBUNTU] kernel: Fix wrong dispatching for control domain CPRBs

2019-07-02 Thread Frank Heimes

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

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

Title:
  [UBUNTU] kernel: Fix wrong dispatching for control domain CPRBs

Status in Ubuntu on IBM z Systems:
  Fix Committed
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Bionic:
  Fix Committed
Status in linux source package in Disco:
  Fix Committed

Bug description:
  SRU Justification:
  ==

  [Impact]

  * Unable to maintain control-only crypto domains

  * The communication to control-only domains does not work in any way.

  * And depending on the setup (lowest numerical domain is control-only)
  the TKE does not see the crypto card at all.

  [Fix]

  * 7379e652797c0b9b5f6caea1576f2dff9ce6a708 7379e65 "s390/zcrypt: Fix
  wrong dispatching for control domain CPRBs"

  * Backport:
  
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1832624/+attachment/5271392/+files/s390
  -zcrypt-Fix-wrong-dispatching-for-control-domain.patch

  [Test Case]

  * Configure a control-only domain to the activation profile of LPAR A

  * Configure a control-and-usage domain to the activation profile of
  LPAR B

  * Try to communicate to LPAR A with the control-only domain (e.g.
  trying to read or set master key)

  [Regression Potential]

  * The regression potential can be considered as moderate since this is
  purely s390x specific

  * and again limited to CryptoExpress adapter cards.

  * It only occurs if crypto domains are configured as control-only or
  better control-only in combination with control-and-usage.

  * The majority of configurations is control-and-usage, since this
  offers more flexibility and covers more use cases.

  [Other Info]

  * Problem was found during tests at IBM and is a so called 'preventive
  fix'

  * The given patch is supposed to fix this issue and became upstream
  accepted with kernel 5.2-rc3.

  * It applies cleanly to disco master-next while cherry-picking, but
  needs the the backport (from comment #3) for bionic's master-next
  kernel 4.15.

  * Once target kernel 5.2 has landed in Eoan, it will be in Eoan, too.

  __

  Description:   kernel: Fix wrong dispatching for control domain CPRBs

  Symptom:   Unable to maintain control-only crypto domains

  Problem:   LPARs may have control-only crypto domains assigned.
     Such a domain can be controlled (for example master keys can
     be set) but can't be used for regualar crypto load (usage).
     A crypto domain may be assigned for control-and-usage to
     only one active LPAR. But the very same domain may be
     assigned for control-only to one or more other LPARs.
     However, trying to communicate in any way with a
     control-only crypto domain did not work. So a simple query
     for the state of the master keys on a control-only domain
     failed and the TKE does not even show this domain. Even
     worse, when the lowest domain (in a numerically sense) is a
     control-only domain, the TKE does not even see the crypto
     cards at all.

  Solution:  This fix introduces some code which checks if an CCA CPRB is
     addressing a control-only domain. If that's the case and
     there is a default control-and-usage domain available the
     CPRB is send to this other domain instead. The target domain
     field within the CPRB is untouched and the crypto card
     firmware code detects this working-as-designed mismatch and
     does the right job and addresses the control domain.

  Reproduction:  1. Add a control-only domain to the crypto configuration of
    an LPAR and re-activate the LPAR.
     2. Connect the TKE the LPAR and try to visit the master key
    verification patterns of this control-only domain.
     3. Will fail without the fix, will succeed with the fix.

  Component: kernel
  Upstream-ID:   7379e652797c0b9b5f6caea1576f2dff9ce6a708

  This fix is requested for 19.10 but should also be applied to 18.04
  and 19.04

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

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

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

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

apport-collect 1835001

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

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

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

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

** Tags added: 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/1835001

Title:
  System does not auto detect disconnection of external monitor

Status in linux package in Ubuntu:
  Confirmed
Status in linux-oem package in Ubuntu:
  New
Status in linux-oem-osp1 package in Ubuntu:
  New
Status in linux source package in Bionic:
  Won't Fix
Status in linux-oem source package in Bionic:
  New
Status in linux-oem-osp1 source package in Bionic:
  New

Bug description:
  Summary:
  System does not auto detect disconnection of external monitor

  Steps to reproduce:
  1. install dell-bto-bionic-beaver-lancel-X84-20190507-42.iso and boot into OS
  2. open "system settings > display settings"
  3. connect laptop to an external HDMI monitor via HDMI port & cable
  4. unplug the HDMI cable
  5. check if "display settings" automatically detects the removal of the 
external monitor

  Expected result:
  display settings should automatically detect the removal of external monitor 
when unplugging the HDMI cable

  Actual result:
  System does not automatically detect the removal of the external monitor when 
HDMI cable is removed.
  Sound setting also list HDMI audio in output tab after removal external 
monitor.

  Failure rate:
  2/10 to 1/10

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

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

[Kernel-packages] [Bug 1835001] Re: System does not auto detect disconnection of external monitor

2019-07-02 Thread Timo Aaltonen

this is an old bug, and there have been several attempts to fix it in
the past, but this series finally seems to make it upstream:

https://patchwork.freedesktop.org/series/62965/

let's fix it in eoan at least, besides oem/osp1

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

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => Timo Aaltonen (tjaalton)

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

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

Title:
  System does not auto detect disconnection of external monitor

Status in linux package in Ubuntu:
  Confirmed
Status in linux-oem package in Ubuntu:
  New
Status in linux-oem-osp1 package in Ubuntu:
  New
Status in linux source package in Bionic:
  Won't Fix
Status in linux-oem source package in Bionic:
  New
Status in linux-oem-osp1 source package in Bionic:
  New

Bug description:
  Summary:
  System does not auto detect disconnection of external monitor

  Steps to reproduce:
  1. install dell-bto-bionic-beaver-lancel-X84-20190507-42.iso and boot into OS
  2. open "system settings > display settings"
  3. connect laptop to an external HDMI monitor via HDMI port & cable
  4. unplug the HDMI cable
  5. check if "display settings" automatically detects the removal of the 
external monitor

  Expected result:
  display settings should automatically detect the removal of external monitor 
when unplugging the HDMI cable

  Actual result:
  System does not automatically detect the removal of the external monitor when 
HDMI cable is removed.
  Sound setting also list HDMI audio in output tab after removal external 
monitor.

  Failure rate:
  2/10 to 1/10

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

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

[Kernel-packages] [Bug 1832012] Re: Initial support for Qualcomm Snapdragon 820 chipset

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

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

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

Title:
  Initial support for Qualcomm Snapdragon 820 chipset

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

Bug description:
  Impact:

  Although the Bionic/snapdragon kernel contains the BSP from the
  Qualcomm landing tree kernel[1], it didn't work on Snapdragon 820
  based board (e.g.  Qualcomm DB820C APQ8096).

  Fix:

  Import the necessary patches to make it boot on such a board (and
  clones).

  How to test:

  1) put the board in fastboot mode (see [2])
  2) generate a compatible boot.img:

  $ cat linux/arch/arm64/boot/Image.gz 
linux/arch/arm64/boot/dts/qcom/apq8096-db820c.dtb > Image.gz+dtb
  $ touch ramdisk
  $ python android/system/core/mkbootimg/mkbootimg.py --kernel Image.gz+dtb 
--ramdisk ramdisk --pagesize 4096 --base 0x8000 --kernel_offset 0x8000 
--ramdisk_offset 0x100 --tags_offset 0x100 --cmdline 
'console=ttyMSM0,115200n8 root=/dev/sda1 net.ifnames=0 
init=/lib/systemd/systemd ro rootwait rng_core.default_quality=700 panic=-1 
fixrtc earlyprintk earlycon=msm_serial_dm,0x75b' --output 
bionic-snapdragon-db820c-boot.img

  3) boot the board using the generated boot.img:

  $ fastboot boot bionic-snapdragon-db820c-boot.img

  Regression potential:

  With new code there's always a degree of regression potential, but all
  patches (but one) came from Linus's upstream tree, and the only
  external one, came direclty from the qcom-lt 4.14 tree.

  1: 
https://git.linaro.org/landing-teams/working/qualcomm/kernel.git/log/?h=release/qcomlt-4.14
  2: 
https://www.96boards.org/documentation/consumer/dragonboard/dragonboard820c/installation/board-recovery.md.html

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

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

[Kernel-packages] [Bug 1757218] Re: QCA9377 isn't being recognized sometimes

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

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

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

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

Title:
  QCA9377 isn't being recognized sometimes

Status in linux package in Ubuntu:
  Fix Committed
Status in linux-oem package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  Fix Committed
Status in linux-oem source package in Bionic:
  Fix Released
Status in linux source package in Cosmic:
  Fix Committed
Status in linux-oem source package in Cosmic:
  Invalid
Status in linux source package in Disco:
  Fix Committed
Status in linux-oem source package in Disco:
  Invalid

Bug description:
  === SRU Justification ===
  [Impact]
  Qualcomm WiFi/Bluetooth may disappear after boot. 

  [Fix]
  Disable USB2 LPM at shutdown phase, to prevent it from lingering in LPM
  L1. Pull back the device to full power before shutdown imitates the
  behavior on Windows.

  [Test] 
  The affected user confimed it fixes the issue.
  I can also confirm that
  a) The power drain in S5 is much lower,
  b) Both WiFi and Bluetooth are always present during reboot stress test.

  [Regression Potential]
  Low. Only a limited number of USB2 devices that support LPM.

  === Original Bug Report ===
  Sometimes, the Wireless Network Card QCA9377 is not recognized on boot. This 
caused, on prior versions, a kernel panic at boot. With Bionic, the system 
boots but is unable to use wireless network. On dmesg there are messages like:

  [2.680590] usb 1-7: new full-speed USB device number 7 using xhci_hcd
  [2.808640] usb 1-7: device descriptor read/64, error -71
  [3.044337] usb 1-7: device descriptor read/64, error -71
  [3.280064] usb 1-7: new full-speed USB device number 8 using xhci_hcd
  [3.408245] usb 1-7: device descriptor read/64, error -71
  [3.644244] usb 1-7: device descriptor read/64, error -71
  [3.752193] usb usb1-port7: attempt power cycle
  [4.404591] usb 1-7: new full-speed USB device number 9 using xhci_hcd
  [4.404904] usb 1-7: Device not responding to setup address.
  [4.612478] usb 1-7: Device not responding to setup address.
  [4.820588] usb 1-7: device not accepting address 9, error -71
  [4.948591] usb 1-7: new full-speed USB device number 10 using xhci_hcd
  [4.949109] usb 1-7: Device not responding to setup address.
  [5.156893] usb 1-7: Device not responding to setup address.
  [5.364589] usb 1-7: device not accepting address 10, error -71
  [5.364655] usb usb1-port7: unable to enumerate USB device

  And lspci and lsusb don't show the wireless network card. The
  alternative is to turn the system off. Reboot don't work and reboot to
  Windows 10 also don't. The system must be powered off to restore
  functionality. Then, on the next boot, it works properly.

  However, after the system is turned off, it may cause the issue again.
  This is not 100% consistent, but mostly it cycles between powering off
  and powering on the notebook as:

  Work -> Don't work -> Work -> Don't work

  On Windows 10 this doesn't happen but when happens on Ubuntu, it's
  possible to reboot and see the status on Windows 10 too: on Device
  Manager it's shown a unidentified USB device at 1-7. Sometimes, on
  Windows 10's Network Devices it's shown, instead of the QCA9377, from
  four to six different devices with generic names and Bluetooth and/or
  Wireless don't work.

  When turning Ubuntu off, there are messages that appears a few
  instants before the system is turned off:

  Mar 18 18:27:26 usuario-Lenovo-ideapad-310-14ISK kernel: [14146.403388] 
ath10k_pci :02:00.0: failed to install key for vdev 0 peer 
xx:xx:xx:xx:xx:xx: -110
  Mar 18 18:27:26 usuario-Lenovo-ideapad-310-14ISK kernel: [14146.403399] 
wlp2s0: failed to remove key (0, xx:xx:xx:xx:xx:xx) from hardware (-110)

  Generally, only the second message appears (but both are recorded on
  kern.log). The MAC adress is the one from the router, not from the
  wireless card.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-12-generic 4.15.0-12.13
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  Uname: Linux 4.15.0-12-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  usuario1364 F pulseaudio
   /dev/snd/seq:usuario1258 F timidity
  CurrentDesktop: XFCE
  Date: Tue Mar 20 14:43:42 2018
  HibernationDevice: RESUME=UUID=9f36068f-c6d6-4fd6-87d5-46f1f5247563
  InstallationDate: Installed on 2017-06-13 (279 days ago)
  InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: LENOVO 80UG
  ProcFB: 0 inteldrmfb
  Pro

[Kernel-packages] [Bug 1832012] Re: Initial support for Qualcomm Snapdragon 820 chipset

** Changed in: linux-snapdragon (Ubuntu Bionic)
   Status: New => Fix Committed

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

Title:
  Initial support for Qualcomm Snapdragon 820 chipset

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

Bug description:
  Impact:

  Although the Bionic/snapdragon kernel contains the BSP from the
  Qualcomm landing tree kernel[1], it didn't work on Snapdragon 820
  based board (e.g.  Qualcomm DB820C APQ8096).

  Fix:

  Import the necessary patches to make it boot on such a board (and
  clones).

  How to test:

  1) put the board in fastboot mode (see [2])
  2) generate a compatible boot.img:

  $ cat linux/arch/arm64/boot/Image.gz 
linux/arch/arm64/boot/dts/qcom/apq8096-db820c.dtb > Image.gz+dtb
  $ touch ramdisk
  $ python android/system/core/mkbootimg/mkbootimg.py --kernel Image.gz+dtb 
--ramdisk ramdisk --pagesize 4096 --base 0x8000 --kernel_offset 0x8000 
--ramdisk_offset 0x100 --tags_offset 0x100 --cmdline 
'console=ttyMSM0,115200n8 root=/dev/sda1 net.ifnames=0 
init=/lib/systemd/systemd ro rootwait rng_core.default_quality=700 panic=-1 
fixrtc earlyprintk earlycon=msm_serial_dm,0x75b' --output 
bionic-snapdragon-db820c-boot.img

  3) boot the board using the generated boot.img:

  $ fastboot boot bionic-snapdragon-db820c-boot.img

  Regression potential:

  With new code there's always a degree of regression potential, but all
  patches (but one) came from Linus's upstream tree, and the only
  external one, came direclty from the qcom-lt 4.14 tree.

  1: 
https://git.linaro.org/landing-teams/working/qualcomm/kernel.git/log/?h=release/qcomlt-4.14
  2: 
https://www.96boards.org/documentation/consumer/dragonboard/dragonboard820c/installation/board-recovery.md.html

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

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

[Kernel-packages] [Bug 1825940] Re: [graphics] Enable ICL

2019-07-02 Thread Timo Aaltonen

thanks

These lists also have entries for EHL, but it's beyond our scope to
support ICL, unless there are common commits needed for both.

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

Title:
  [graphics] Enable ICL

Status in intel:
  Fix Committed
Status in linux package in Ubuntu:
  Confirmed
Status in linux-oem-osp1 package in Ubuntu:
  New
Status in mesa package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  Invalid
Status in linux-oem-osp1 source package in Bionic:
  Fix Committed
Status in mesa source package in Bionic:
  New

Bug description:
  [Impact]
  Ice Lake (ICL) graphics needs to be enabled for OEM OSP1 image which is based 
on 18.04.3 graphics stack with linux-oem-osp1 kernel.

  
  [Test case]
  The usual desktop usage, graphics tests etc.

  
  [Regression potential]
  Linux-oem-osp1 kernel is a new kernel used only on new OEM enablements, and 
it can't regress any currently running system.

  Mesa backports are limited to ICL, so they shouldn't regress earlier
  generations either.

  --

  Original description:

  ICL graphics is not enabled in 19.04.
  if you want to use 19.04 on ICL platform, you need do like this

  Add kernel option
  i915.alpha_support=1

  Target Release:19.10
  Target Kernel: 5.2
  Target Mesa: 19.1

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

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

[Kernel-packages] [Bug 1834840] Re: Laptop certified with a previous version of Ubuntu fails to boot 59% of the time

2019-07-02 Thread Pierre Equoy

** Description changed:

+ =[Edit July 2nd, 09:33UTC]=
+
+ Found that I was not using the latest BIOS (fwupdmgr in 16.04 OEM image
+ is not working anymore and it was impossible to boot into 19.04 to run
+ it...). Finally got my hands on BIOS v1.14 published in May 2019 and it
+ seems it addresses an issue with Linux booting:
+
+ - Fixed a potential issue with binary image measurement using the Linux UEFI
shim boot loader. (from v1.11 changelog:
https://www.dell.com/support/home/tw/en/twdhs1/drivers/driversdetails?driverid=h3n5f&oscode=biosa&productcode=inspiron-13-7370-laptop)
+ - Fixed an issue with Secure Boot Option ROM signature verification. (from
v1.13.1 changelog:
https://www.dell.com/support/home/tw/en/twdhs1/drivers/driversdetails?driverid=my4n2&oscode=biosa&productcode=inspiron-13-7370-laptop)
+
=[Edit July 2nd, 08:06UTC]=

Trying to boot from a 18.04.2 live USB or 19.04 live USB exhibits the
same kind of issue, no matter if Secure Boot is enabled or not in the
BIOS.

No matter Secure Boot is enabled or not in the BIOS, I briefly see
"Booting in insecure mode", then "error: file /boot/ not found" before
showing GRUB menu.

I tried the 16.04 OEM image and it works reliably. I can install it and
once installed, I can boot into the system 10 times out of 10.

=[Original Description]=

Device: Dell Inspiron 7370
BIOS: 1.2.0

This device was certified with 16.04:
https://certification.ubuntu.com/hardware/201704-25503/

I installed Ubuntu 19.04 and although it installed properly, about 50%
of the time, the device won't boot at all. I need to shut it down and
restart it.

Steps to reproduce
--

In the BIOS, make sure
- SATA mode is set to AHCI
- Secure Boot is enabled

1. Install Ubuntu 19.04 stock. I selected the following options:
- Erase disk and install Ubuntu
- Full disk encryption
- Minimal install
- Install 3rd party drivers (this requires to enroll MOK key at the next
reboot using a password)

2. After installation, boot into Ubuntu.

Expected results

The device boots up Ubuntu reliably.

Actual results
--

About 50% of the time, the screen remains dark purple and nohting moves.
I have to manually shut it down and re-start it until it ends up booting
Ubuntu.

It looks like it stops at step:

"Loading initial ramdisk..."

Failure rate

I booted 22 times. It failed to boot 13 times and booted up properly 9 times.
-> failure rate = 59 %

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: linux-image-5.0.0-20-generic 5.0.0-20.21
ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8
Uname: Linux 5.0.0-20-generic x86_64
ApportVersion: 2.20.10-0ubuntu27
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: pieq 1846 F pulseaudio
CurrentDesktop: ubuntu:GNOME
Date: Mon Jul 1 17:38:59 2019
InstallationDate: Installed on 2019-07-01 (0 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
Lsusb:
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 003: ID 8087:0a2a Intel Corp.
Bus 001 Device 002: ID 0bda:58f5 Realtek Semiconductor Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Dell Inc. Inspiron 7370
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-20-generic
root=/dev/mapper/ubuntu--vg-root ro quiet splash
RelatedPackageVersions:
linux-restricted-modules-5.0.0-20-generic N/A
linux-backports-modules-5.0.0-20-generic N/A
linux-firmware1.178.1
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/31/2017
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.2.0
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias:
dmi:bvnDellInc.:bvr1.2.0:bd08/31/2017:svnDellInc.:pnInspiron7370:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:
dmi.product.family: Inspiron
dmi.product.name: Inspiron 7370
dmi.product.sku: 07E9
dmi.sys.vendor: Dell Inc.

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

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

Title:
Laptop certified with a previous version of Ubuntu fails to boot 59%
of the time

Status in linux package in Ubuntu:
Invalid

Bug description:
=[Edit July 2nd, 09:33UTC]=

Found that I was not using the latest BIOS (fwupdmgr in 16.04 OEM
image is not working anymore and it was impossible to boot into 19.04
to run it...). Finally got my hands on BIOS v1.14 published in May
2019 and it seems it addresses an issue with Linux booting:

- Fixed a potential issue with

[Kernel-packages] [Bug 1834954] Re: linux: 4.15.0-55.59 -proposed tracker

** Summary changed:

- linux:  -proposed tracker
+ linux: 4.15.0-55.59 -proposed tracker

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

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

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

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

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

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

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

Title:
  linux: 4.15.0-55.59 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  In Progress
Status in Kernel SRU Workflow prepare-package-meta series:
  In Progress
Status in Kernel SRU Workflow prepare-package-signed series:
  In Progress
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
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 1834950 (xenial/linux-azure), bug 1834953 (xenial/linux-hwe)
  derivatives: bug 1834919 (pc-kernel), bug 1834921 (pc-lowlatency-kernel), bug 
1834923 (linux-raspi2), bug 1834925 (linux-snapdragon), bug 1834926 
(linux-oem), bug 1834930 (linux-aws), bug 1834936 (linux-gcp), bug 1834939 
(linux-gke-4.15), bug 1834940 (linux-kvm), bug 1834941 (linux-ibm-gt), bug 
1834943 (linux-oracle), bug 1834944 (linux-fips)

  -- swm properties --
  phase: Ready for Packaging
  phase-changed: Monday, 01. July 2019 17:11 UTC
  reason:
prepare-package: Pending -- version not specified
  variant: debs

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

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

[Kernel-packages] [Bug 1834771] Re: No HDMI-audio after kernel 4.15.-0.50

2019-07-02 Thread Hui Wang

According to #19, the 4.15.0-50 can work that is because the driver doesn't 
check the ELD status, that is not correct. The hdmi audio is valid/plugged only 
if both monitor_present and eld_valid are true, but that is the log from 
4.15.0-50:
 monitor_present1
 eld_valid  0

We did introduce a new patch to check ELD from the 4.15.0-51, because of
this patch, the hdmi audio will not be regarded as plugged since
eld_valid is 0.

The root cause of this problem is the graphic driver amdgpu, so could
you please test the latest mainline kernel if it can make both
monitor_present and eld_valid true.

https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.2-rc6/

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

Title:
  No HDMI-audio after kernel 4.15.-0.50

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I've got no HDMI-audio. Latest kernel with working HDMI-audio is 4.15.-0.50. 
In pavucontrol HDMI-audio shows unplugged. And also internal audio shows 
unplugged, but it still works. I'm on linux mint 18.3.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jouni  1859 F pulseaudio
   /dev/snd/controlC1:  jouni  1859 F pulseaudio
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux 18.3
  HibernationDevice: RESUME=UUID=9e8d7bf3-dc5f-4c72-b875-6dbe81a36c36
  InstallationDate: Installed on 2017-01-28 (883 days ago)
  InstallationMedia: Linux Mint 18.1 "Serena" - Release amd64 20161213
  IwConfig:
   lono wireless extensions.
   
   enp3s0no wireless extensions.
  MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-54-generic 
root=UUID=f167a2b0-3b30-4a5a-907f-6b97c95b7a91 ro quiet iommu=soft splash 
vt.handoff=7
  ProcVersionSignature: Ubuntu 4.15.0-54.58~16.04.1-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-54-generic N/A
   linux-backports-modules-4.15.0-54-generic  N/A
   linux-firmware 1.157.21
  RfKill:
   
  Tags:  sylvia
  Uname: Linux 4.15.0-54-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo video
  _MarkForUpload: True
  dmi.bios.date: 02/26/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: FC
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: 970A-UD3P
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrFC:bd02/26/2016:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rn970A-UD3P:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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

[Kernel-packages] [Bug 1834902] Re: linux: 5.0.0-21.22 -proposed tracker

** Summary changed:

- linux:  -proposed tracker
+ linux: 5.0.0-21.22 -proposed tracker

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

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

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

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

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

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

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

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

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

Title:
  linux: 5.0.0-21.22 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  In Progress
Status in Kernel SRU Workflow prepare-package-lrm series:
  In Progress
Status in Kernel SRU Workflow prepare-package-meta series:
  In Progress
Status in Kernel SRU Workflow prepare-package-signed series:
  In Progress
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
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 1834898 (bionic/linux-hwe-edge), bug 1834900 
(bionic/linux-oem-osp1)
  derivatives: bug 1834884 (linux-raspi2), bug 1834886 (linux-aws), bug 1834888 
(linux-azure), bug 1834891 (linux-gcp), bug 1834892 (linux-kvm), bug 1834894 
(linux-snapdragon)

  -- swm properties --
  phase: Ready for Packaging
  phase-changed: Monday, 01. July 2019 16:06 UTC
  reason:
prepare-package: Pending -- version not specified
  variant: debs

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

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

[Kernel-packages] [Bug 1831828] Re: [SRU][B/B-OEM/C/D/OEM-OSP1] Add RTL8822 wifi driver rtw88

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

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

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

Title:
  [SRU][B/B-OEM/C/D/OEM-OSP1] Add RTL8822 wifi driver rtw88

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

Bug description:
  SRU justification:

  [Impact]
  RTL8822BE/RTL8822CE need new driver rtw88 supports.

  [Fix]
  This is a new mac80211 driver for Realtek 802.11ac wireless network chips.
  And it needs new firmware too.

  [Test]
  Verified on hardware. Tests result are good.

  [Regression Potential]
  Low, it introducs the new driver to enable new wifi chips supports.
  2 more upstream commits are introduced:
  e7d4a95da bitfield: fix *_encode_bits()
  00b0c9b82 Add primitives for manipulating bitfields both in host- and 
fixed-endian.
  These 2 commits add "le32p_replace_bits" functions that rtw88 uses.
  They introduced new operator of bitfields since 4.16 kernel, don't change 
exsit funtions.
  C/D/OEM-OSP-1 don't need these 2 patches.

  These firmwares are already in disco.

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

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

[Kernel-packages] [Bug 1784485] Re: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all

The kernel fix is not released to updates, we just have it committed to
git.

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

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

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

Title:
  [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all

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

Bug description:
  Internal speaker - not sound at all
  Cable Headphonse - realy quiet disorted sound
  Bluetooth headphones - sound works fine

  On Windows 10 everything works fine.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18
  Uname: Linux 4.15.0-29-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pmichalski   7964 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jul 30 22:32:10 2018
  InstallationDate: Installed on 2018-07-17 (12 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pl_PL.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed
  Symptom_Card: Wbudowany dźwięk - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm2988 F pulseaudio
pmichalski   7964 F pulseaudio
  Symptom_Jack: Mic, Internal
  Symptom_Type: No sound at all
  Title: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/18/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX391UA.204
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX391UA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX391UA.204:bd05/18/2018:svnASUSTeKCOMPUTERINC.:pnZenBookSUX391UA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX391UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: ZenBook S
  dmi.product.name: ZenBook S UX391UA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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

[Kernel-packages] [Bug 1834954] Re: linux: 4.15.0-55.59 -proposed tracker

** 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 1834950 (xenial/linux-azure), bug 1834953 (xenial/linux-hwe)
  derivatives: bug 1834919 (pc-kernel), bug 1834921 (pc-lowlatency-kernel), bug 
1834923 (linux-raspi2), bug 1834925 (linux-snapdragon), bug 1834926 
(linux-oem), bug 1834930 (linux-aws), bug 1834936 (linux-gcp), bug 1834939 
(linux-gke-4.15), bug 1834940 (linux-kvm), bug 1834941 (linux-ibm-gt), bug 
1834943 (linux-oracle), bug 1834944 (linux-fips)
  
  -- swm properties --
- phase: Ready for Packaging
- phase-changed: Monday, 01. July 2019 17:11 UTC
+ phase: Packaging
+ phase-changed: Tuesday, 02. July 2019 10:31 UTC
  reason:
-   prepare-package: Pending -- version not specified
+   prepare-package: Pending -- package not yet uploaded
+   prepare-package-meta: Pending -- package not yet uploaded
+   prepare-package-signed: Pending -- package not yet uploaded
  variant: debs

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

Title:
  linux: 4.15.0-55.59 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  In Progress
Status in Kernel SRU Workflow prepare-package-meta series:
  In Progress
Status in Kernel SRU Workflow prepare-package-signed series:
  In Progress
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
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 1834950 (xenial/linux-azure), bug 1834953 (xenial/linux-hwe)
  derivatives: bug 1834919 (pc-kernel), bug 1834921 (pc-lowlatency-kernel), bug 
1834923 (linux-raspi2), bug 1834925 (linux-snapdragon), bug 1834926 
(linux-oem), bug 1834930 (linux-aws), bug 1834936 (linux-gcp), bug 1834939 
(linux-gke-4.15), bug 1834940 (linux-kvm), bug 1834941 (linux-ibm-gt), bug 
1834943 (linux-oracle), bug 1834944 (linux-fips)

  -- swm properties --
  phase: Packaging
  phase-changed: Tuesday, 02. July 2019 10:31 UTC
  reason:
prepare-package: Pending -- package not yet uploaded
prepare-package-meta: Pending -- package not yet uploaded
prepare-package-signed: Pending -- package not yet uploaded
  variant: debs

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

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

[Kernel-packages] [Bug 1834902] Re: linux: 5.0.0-21.22 -proposed tracker

** 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 1834898 (bionic/linux-hwe-edge), bug 1834900 
(bionic/linux-oem-osp1)
  derivatives: bug 1834884 (linux-raspi2), bug 1834886 (linux-aws), bug 1834888 
(linux-azure), bug 1834891 (linux-gcp), bug 1834892 (linux-kvm), bug 1834894 
(linux-snapdragon)
  
  -- swm properties --
- phase: Ready for Packaging
- phase-changed: Monday, 01. July 2019 16:06 UTC
+ phase: Packaging
+ phase-changed: Tuesday, 02. July 2019 10:31 UTC
  reason:
-   prepare-package: Pending -- version not specified
+   prepare-package: Pending -- package not yet uploaded
+   prepare-package-lrm: Pending -- package not yet uploaded
+   prepare-package-meta: Pending -- package not yet uploaded
+   prepare-package-signed: Pending -- package not yet uploaded
  variant: debs

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

Title:
  linux: 5.0.0-21.22 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  In Progress
Status in Kernel SRU Workflow prepare-package-lrm series:
  In Progress
Status in Kernel SRU Workflow prepare-package-meta series:
  In Progress
Status in Kernel SRU Workflow prepare-package-signed series:
  In Progress
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
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 1834898 (bionic/linux-hwe-edge), bug 1834900 
(bionic/linux-oem-osp1)
  derivatives: bug 1834884 (linux-raspi2), bug 1834886 (linux-aws), bug 1834888 
(linux-azure), bug 1834891 (linux-gcp), bug 1834892 (linux-kvm), bug 1834894 
(linux-snapdragon)

  -- swm properties --
  phase: Packaging
  phase-changed: Tuesday, 02. July 2019 10:31 UTC
  reason:
prepare-package: Pending -- package not yet uploaded
prepare-package-lrm: Pending -- package not yet uploaded
prepare-package-meta: Pending -- package not yet uploaded
prepare-package-signed: Pending -- package not yet uploaded
  variant: debs

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

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

[Kernel-packages] [Bug 1835040] [NEW] Touchpd not working properly on Linux

2019-07-02 Thread Arnab Satapathi

Public bug reported:

Installed Ubuntu 19.04 on a laptop, the touch pad is behaving abnormally.
It's detected, but nothing seems to work, however working very normal with 
Windows 10.

Laptop model - iBall CompBook M500

It's somewhat similar to this bug, probably using the same touchpad hardware 
too.
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1757435

Attached some logs, with `i2c-hid.debug=1 hid.debug=1` the boot time
kernel parameters added.

Thanks.

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


** Tags: kernel-bug

** Attachment added: "dmesg.log"
   https://bugs.launchpad.net/bugs/1835040/+attachment/5274624/+files/dmesg.log

** Description changed:

  Installed Ubuntu 19.04 on a laptop, the touch pad is behaving abnormally.
  It's detected, but nothing seems to work, however working very normal with 
Windows 10.
  
  It's somewhat similar to this bug, probably using the same touchpad hardware 
too.
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1757435
  
  Attached some logs, with `i2c-hid.debug=1 hid.debug=1` the boot time
  kernel parameters added.
+ 
+ Thanks.

** Description changed:

  Installed Ubuntu 19.04 on a laptop, the touch pad is behaving abnormally.
  It's detected, but nothing seems to work, however working very normal with 
Windows 10.
+ 
+ Laptop model - iBall CompBook M500
  
  It's somewhat similar to this bug, probably using the same touchpad hardware 
too.
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1757435
  
  Attached some logs, with `i2c-hid.debug=1 hid.debug=1` the boot time
  kernel parameters added.
  
  Thanks.

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

Title:
  Touchpd not working properly on Linux

Status in linux package in Ubuntu:
  New

Bug description:
  Installed Ubuntu 19.04 on a laptop, the touch pad is behaving abnormally.
  It's detected, but nothing seems to work, however working very normal with 
Windows 10.

  Laptop model - iBall CompBook M500

  It's somewhat similar to this bug, probably using the same touchpad hardware 
too.
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1757435

  Attached some logs, with `i2c-hid.debug=1 hid.debug=1` the boot time
  kernel parameters added.

  Thanks.

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

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

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

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

apport-collect 1835040

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

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

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

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

** Tags added: 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/1835040

Title:
  Touchpd not working properly on Linux

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Installed Ubuntu 19.04 on a laptop, the touch pad is behaving abnormally.
  It's detected, but nothing seems to work, however working very normal with 
Windows 10.

  Laptop model - iBall CompBook M500

  It's somewhat similar to this bug, probably using the same touchpad hardware 
too.
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1757435

  Attached some logs, with `i2c-hid.debug=1 hid.debug=1` the boot time
  kernel parameters added.

  Thanks.

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

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

[Kernel-packages] [Bug 1835040] Re: Touchpd not working properly on Linux

2019-07-02 Thread Arnab Satapathi

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

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

Title:
  Touchpd not working properly on Linux

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Installed Ubuntu 19.04 on a laptop, the touch pad is behaving abnormally.
  It's detected, but nothing seems to work, however working very normal with 
Windows 10.

  Laptop model - iBall CompBook M500

  It's somewhat similar to this bug, probably using the same touchpad hardware 
too.
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1757435

  Attached some logs, with `i2c-hid.debug=1 hid.debug=1` the boot time
  kernel parameters added.

  Thanks.

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

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

[Kernel-packages] [Bug 1834918] Re: linux: 4.4.0-155.182 -proposed tracker

** Summary changed:

- linux:  -proposed tracker
+ linux: 4.4.0-155.182 -proposed tracker

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

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

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

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

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

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

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

Title:
  linux: 4.4.0-155.182 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  In Progress
Status in Kernel SRU Workflow prepare-package-meta series:
  In Progress
Status in Kernel SRU Workflow prepare-package-signed series:
  In Progress
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
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 1834916 (trusty/linux-aws), bug 1834917 
(trusty/linux-lts-xenial)
  derivatives: bug 1834906 (pc-kernel), bug 1834908 (linux-aws), bug 1834909 
(linux-kvm), bug 1834911 (linux-raspi2), bug 1834913 (linux-snapdragon), bug 
1834915 (linux-fips)

  -- swm properties --
  phase: Ready for Packaging
  phase-changed: Monday, 01. July 2019 16:37 UTC
  reason:
prepare-package: Pending -- version not specified
  variant: debs

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

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

[Kernel-packages] [Bug 1834918] Re: linux: 4.4.0-155.182 -proposed tracker

** 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 1834916 (trusty/linux-aws), bug 1834917 
(trusty/linux-lts-xenial)
  derivatives: bug 1834906 (pc-kernel), bug 1834908 (linux-aws), bug 1834909 
(linux-kvm), bug 1834911 (linux-raspi2), bug 1834913 (linux-snapdragon), bug 
1834915 (linux-fips)
  
  -- swm properties --
- phase: Ready for Packaging
- phase-changed: Monday, 01. July 2019 16:37 UTC
+ phase: Packaging
+ phase-changed: Tuesday, 02. July 2019 12:00 UTC
  reason:
-   prepare-package: Pending -- version not specified
+   prepare-package: Pending -- package not yet uploaded
+   prepare-package-meta: Pending -- package not yet uploaded
+   prepare-package-signed: Pending -- package not yet uploaded
  variant: debs

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

Title:
  linux: 4.4.0-155.182 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  In Progress
Status in Kernel SRU Workflow prepare-package-meta series:
  In Progress
Status in Kernel SRU Workflow prepare-package-signed series:
  In Progress
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
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 1834916 (trusty/linux-aws), bug 1834917 
(trusty/linux-lts-xenial)
  derivatives: bug 1834906 (pc-kernel), bug 1834908 (linux-aws), bug 1834909 
(linux-kvm), bug 1834911 (linux-raspi2), bug 1834913 (linux-snapdragon), bug 
1834915 (linux-fips)

  -- swm properties --
  phase: Packaging
  phase-changed: Tuesday, 02. July 2019 12:00 UTC
  reason:
prepare-package: Pending -- package not yet uploaded
prepare-package-meta: Pending -- package not yet uploaded
prepare-package-signed: Pending -- package not yet uploaded
  variant: debs

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

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

[Kernel-packages] [Bug 1807259] Re: sky2 ethernet card doesn't work after returning from suspend

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

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

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

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

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

Title:
  sky2 ethernet card doesn't work after returning from suspend

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

Bug description:
  I am on "Linux Mint 18.2 Sonya".

  Upgrading to Kernel 4.15.0-39.42~16.04.1 leaves the ethernet adapter
  inactive after resume from suspend. I reverted to a 4.13 kernel for
  this reason for which it works.

  the bug seems to be similar to
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1798921.

  $ lshw -class network
  WARNUNG: Sie sollten dieses Programm mit Systemverwalterrechten (root) 
ausführen.
*-network DEAKTIVIERT
 Beschreibung: Kabellose Verbindung
 Produkt: BCM4312 802.11b/g LP-PHY
 Hersteller: Broadcom Corporation
 Physische ID: 0
 Bus-Informationen: pci@:0c:00.0
 Logischer Name: wlp12s0
 Version: 01
 Seriennummer: 00:26:5e:33:a9:6d
 Breite: 64 bits
 Takt: 33MHz
 Fähigkeiten: bus_master cap_list ethernet physical wireless
 Konfiguration: broadcast=yes driver=wl0 driverversion=6.30.223.271 
(r587334) latency=0 multicast=yes wireless=IEEE 802.11
 Ressourcen: irq:17 memory:f69fc000-f69f
*-network
 Beschreibung: Ethernet interface
 Produkt: 88E8040 PCI-E Fast Ethernet Controller
 Hersteller: Marvell Technology Group Ltd.
 Physische ID: 0
 Bus-Informationen: pci@:09:00.0
 Logischer Name: enp9s0
 Version: 13
 Seriennummer: 00:25:64:4a:26:00
 Größe: 100Mbit/s
 Kapazität: 100Mbit/s
 Breite: 64 bits
 Takt: 33MHz
 Fähigkeiten: bus_master cap_list ethernet physical tp 10bt 10bt-fd 
100bt 100bt-fd autonegotiation
 Konfiguration: autonegotiation=on broadcast=yes driver=sky2 
driverversion=1.30 duplex=full ip=192.168.1.7 latency=0 link=yes multicast=yes 
port=twisted pair speed=100Mbit/s
 Ressourcen: irq:24 memory:f68fc000-f68f ioport:de00(Größe=256)

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

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

[Kernel-packages] [Bug 1035645] Re: kernel panic after rebooting ARM Quantal installation

2019-07-02 Thread Bruce Hank

Excellent and nice post. This is such a great resource that you are
providing and you give it away for free. I love seeing that understands
the value. I'm glad to have found this post as its such an interesting
one! I have also something very interesting for you. Visit our blog
post-http://www.applesupport247.com/blog/how-to-fix-mac-error-43/

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

Title:
  kernel panic after rebooting ARM Quantal installation

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I was carrying out this test: 
http://iso.qa.ubuntu.com/qatracker/milestones/219/builds/20826/testcases/1300/results/
 on this image: 
http://cdimage.ubuntu.com/daily-live/20120811.1/quantal-desktop-armhf+omap4.img 
on a pandaboard with a 16 GB Kingston USB key.
  After the installation finished and I rebooted got the message you can see in 
attached picture.
  Not sure if it's a capser o kernel problem.

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

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

[Kernel-packages] [Bug 1791312] Re: ubuntu 18.04 flickering screen with Radeon X1600

Hi Werner,

The fix for this bug hasn't been released yet, so kernel 4.15.0-54 is
expected to still have the issue. A new kernel version containing the
fix is planned to be published to -proposed this week and an automated
comment will be added when the new version is available for testing.
Meanwhile please keep the tasks as 'Fix Committed' to correct reflect
their current status.

Thank you.

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

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

Title:
  ubuntu 18.04 flickering screen with Radeon X1600

Status in Linux:
  Fix Released
Status in linux package in Ubuntu:
  Confirmed
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 ===
  [Impact]
  Screen flickers when using radeon.ko.
  It's a regression, it didn't happen on Trusty.

  [Fix]
  Quote the original commit log:
  "Instead of the closest reference divider prefer the lowest".

  [Test]
  Affected user confirms it fixes the issue.

  [Regression Potential]
  Low. Only affect radeaon, and it's in upstream stable tree.

  === Original Bug Report ===
  my laptop: HP Compaq nx9420
  my grafic card:
  01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] 
RV530/M56-P [Mobility Radeon X1600] (prog-if 00 [VGA controller])

  attachment:
  the bug-apport-file

  Description:
  I start ubuntu 18.04 LTS (Kernel 4.15.0.33) in textmode;
  -> as soon as the kernel-module radeon.ko is loaded the screen starts 
flickering
  when starting the grafic-mode the flickering continues; so the screen is 
unusable.

  when setting the option "radeon.modeset=0" (thus: not use radeon drivers) the 
screen does not flicker
  but the resolution is limited to 1400x1050 (instead of natural 1680x1050)
  so I can not use this as work-around

  when using the old ubuntu 14.04.05 LTS (Kernel 3.13.0-157)
  the screen is o.k. NO flickering in textmode, nice grafic, NO flickering
  xrandr tells: 1680x1050 60.1

  so I must stay on old ubuntu 14.04.05 ???

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

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

[Kernel-packages] [Bug 1809856] Re: [XPS 13 9370, Realtek ALC3271, Headphone Out, Right] Static/Electric background noise when volume is not muted

2019-07-02 Thread Chris

Hi Hui Wang, sorry it has taken me so long to test this. I installed
your patch and noticed the following things:

1. I **think** the noise is less than before although still present.
2. The commands in your test instructions now make no difference 
(https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1809856/comments/12)

Please let me know if you need any further detail.

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

Title:
  [XPS 13 9370, Realtek ALC3271, Headphone Out, Right] Static/Electric
  background noise when volume is not muted

Status in alsa-driver package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Whenever I plug in my Sennheiser HD1 Wired headphones with mic, I start 
hearing a static/electric (some internal?) sound if the volume isn't muted. 
Something similar occurs with my other earbuds with mic, just much quieter and 
less noticable. It works fine on Windows 10 running on the same machine, and on 
my Android phone. I don't notice is when something is playing, but the 
frequency of the sound changes when I play something, then pause it, the 
background noise will sound slightly different.
  This is from an installed Ubuntu 18.10. I have tried booting 18.10 Live USB 
and 18.04.1 LTS Live USB, and the issue still occurs. I have tried playing with 
alsamixer and pavucontrol settings, and nothing fixed this background noise.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17
  Uname: Linux 4.18.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  davidkoplik   1891 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Dec 26 20:17:59 2018
  InstallationDate: Installed on 2018-12-26 (0 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Black Headphone Out, Right
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: High background noise, or volume is too low
  Title: [XPS 13 9370, Realtek ALC3271, Black Headphone Out, Right] Background 
noise or low volume
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/04/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.6.3
  dmi.board.name: 0F6P3V
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.6.3:bd11/04/2018:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0F6P3V:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9370
  dmi.product.sku: 07E6
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1809856/+subscriptions

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

[Kernel-packages] [Bug 1563110]

2019-07-02 Thread ric-82

> I hope these efforts can be merged into mainline Linux and ALSA.

Me too: I lack the know-how to fix the kernel myself, unfortunately...

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

Title:
  No sound on Asus e200ha, intel sst with cx2072x codec

Status in ALSA driver:
  Confirmed
Status in alsa-driver package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released

Bug description:
  I've recently bought an Asus e200ha.
  Sound in this laptop doesn't work.
  The sound card is an intel sst with codec conexant cx2072x

  aplay -l:
  aplay: device_list:268: no soundcard found...
  in the sound setting there is a "Dummy output"
  --- 
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=7b77dc46-7d5b-4869-83dd-739980736c3a
  InstallationDate: Installed on 2016-03-28 (0 days ago)
  InstallationMedia: Linux Mint 17.3 "Rosa" - Release amd64 20160105
  Lsusb:
   Bus 002 Device 002: ID 0781:5583 SanDisk Corp. 
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 13d3:3496 IMC Networks 
   Bus 001 Device 002: ID 04f2:b54b Chicony Electronics Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. E200HA
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-32-generic 
root=UUID=50fb13c0-a8cd-441d-a38b-c0295c1b9a15 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.19.0-32.37~14.04.1-generic 3.19.8-ckt7
  RelatedPackageVersions:
   linux-restricted-modules-3.19.0-32-generic N/A
   linux-backports-modules-3.19.0-32-generic  N/A
   linux-firmware 1.127.16
  Tags:  rosa
  Uname: Linux 3.19.0-32-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/26/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E200HA.203
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: E200HA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrE200HA.203:bd11/26/2015:svnASUSTeKCOMPUTERINC.:pnE200HA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnE200HA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: E200HA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/alsa-driver/+bug/1563110/+subscriptions

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

[Kernel-packages] [Bug 1835054] [NEW] Missing NIC driver for Armada 8040 (Macchiatobin)

2019-07-02 Thread Paweł Moll

Public bug reported:

At least in Ubuntu 19.04, the arm64 kernel (linux-image-5.0.0) is not
building CONFIG_MVPP2 (depends on CONFIG_ARCH_MVEBU) -  a driver for
network controllers(s) in Marvell SOCs, particularly Armada 8040 -
neither as a model or a built-in:

$ uname -m
aarch64
$ grep MVPP2 /boot/config-5.0.0-20-generic 
$

It makes very hard (and impossible for non-advanced users) to install
and use Ubuntu on the Macchiatobin board (http://macchiatobin.net/) - a
reasonably priced and performant server/mini-desktop platform.

Could it be added, please, and the installer image re-generated.

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


** Tags: 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/1835054

Title:
  Missing NIC driver for Armada 8040 (Macchiatobin)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  At least in Ubuntu 19.04, the arm64 kernel (linux-image-5.0.0) is not
  building CONFIG_MVPP2 (depends on CONFIG_ARCH_MVEBU) -  a driver for
  network controllers(s) in Marvell SOCs, particularly Armada 8040 -
  neither as a model or a built-in:

  $ uname -m
  aarch64
  $ grep MVPP2 /boot/config-5.0.0-20-generic 
  $

  It makes very hard (and impossible for non-advanced users) to install
  and use Ubuntu on the Macchiatobin board (http://macchiatobin.net/) -
  a reasonably priced and performant server/mini-desktop platform.

  Could it be added, please, and the installer image re-generated.

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

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

[Kernel-packages] [Bug 1563110]

2019-07-02 Thread mirh

https://mailman.alsa-project.org/pipermail/alsa-
devel/2019-May/149706.html

CX2072X is landing in 5.3.

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

Title:
  No sound on Asus e200ha, intel sst with cx2072x codec

Status in ALSA driver:
  Confirmed
Status in alsa-driver package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released

Bug description:
  I've recently bought an Asus e200ha.
  Sound in this laptop doesn't work.
  The sound card is an intel sst with codec conexant cx2072x

  aplay -l:
  aplay: device_list:268: no soundcard found...
  in the sound setting there is a "Dummy output"
  --- 
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=7b77dc46-7d5b-4869-83dd-739980736c3a
  InstallationDate: Installed on 2016-03-28 (0 days ago)
  InstallationMedia: Linux Mint 17.3 "Rosa" - Release amd64 20160105
  Lsusb:
   Bus 002 Device 002: ID 0781:5583 SanDisk Corp. 
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 13d3:3496 IMC Networks 
   Bus 001 Device 002: ID 04f2:b54b Chicony Electronics Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. E200HA
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-32-generic 
root=UUID=50fb13c0-a8cd-441d-a38b-c0295c1b9a15 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.19.0-32.37~14.04.1-generic 3.19.8-ckt7
  RelatedPackageVersions:
   linux-restricted-modules-3.19.0-32-generic N/A
   linux-backports-modules-3.19.0-32-generic  N/A
   linux-firmware 1.127.16
  Tags:  rosa
  Uname: Linux 3.19.0-32-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/26/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E200HA.203
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: E200HA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrE200HA.203:bd11/26/2015:svnASUSTeKCOMPUTERINC.:pnE200HA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnE200HA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: E200HA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/alsa-driver/+bug/1563110/+subscriptions

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

[Kernel-packages] [Bug 1809206]

2019-07-02 Thread luya

Follow-up,
The current ACPI status still remain unresolved to this date. The dmesg is 
located on https://linux-hardware.org/index.php?probe=ce83006200

Is there someone from HP willing to take a look?

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

Title:
  Amd ACPI Error

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

Bug description:
  Hi
  Hp Laptop
  Amd A10 9600p

  Ubuntu 18.10 
  Kernel: all kernel acpi error

  mesg | grep Error
  [3.546921] RAS: Correctable Errors collector initialized.
  [9.979321] ACPI Error: Field [D128] at bit offset/length 128/1024 exceeds 
size of target Buffer (160 bits) (20180531/dsopcode-201)
  [9.979438] ACPI Error: Method parse/execution failed \HWMC, 
AE_AML_BUFFER_LIMIT (20180531/psparse-516)
  [9.979484] ACPI Error: Method parse/execution failed \_SB.WMID.WMAA, 
AE_AML_BUFFER_LIMIT (20180531/psparse-516)
  [9.979764] ACPI Error: Field [D128] at bit offset/length 128/1024 exceeds 
size of target Buffer (160 bits) (20180531/dsopcode-201)
  [9.979872] ACPI Error: Method parse/execution failed \HWMC, 
AE_AML_BUFFER_LIMIT (20180531/psparse-516)
  [9.988903] ACPI Error: Method parse/execution failed \_SB.WMID.WMAA, 
AE_AML_BUFFER_LIMIT (20180531/psparse-516)
  [9.989220] ACPI Error: Field [D128] at bit offset/length 128/1024 exceeds 
size of target Buffer (160 bits) (20180531/dsopcode-201)
  [9.989318] ACPI Error: Method parse/execution failed \HWMC, 
AE_AML_BUFFER_LIMIT (20180531/psparse-516)
  [9.989358] ACPI Error: Method parse/execution failed \_SB.WMID.WMAA, 
AE_AML_BUFFER_LIMIT (20180531/psparse-516)
  [9.990180] ACPI Error: Field [D128] at bit offset/length 128/1024 exceeds 
size of target Buffer (160 bits) (20180531/dsopcode-201)
  [9.990274] ACPI Error: Method parse/execution failed \HWMC, 
AE_AML_BUFFER_LIMIT (20180531/psparse-516)
  [9.990312] ACPI Error: Method parse/execution failed \_SB.WMID.WMAA, 
AE_AML_BUFFER_LIMIT (20180531/psparse-516)
  [9.990557] ACPI Error: Field [D128] at bit offset/length 128/1024 exceeds 
size of target Buffer (160 bits) (20180531/dsopcode-201)
  [9.990646] ACPI Error: Method parse/execution failed \HWMC, 
AE_AML_BUFFER_LIMIT (20180531/psparse-516)
  [9.990682] ACPI Error: Method parse/execution failed \_SB.WMID.WMAA, 
AE_AML_BUFFER_LIMIT (20180531/psparse-516)

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

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

[Kernel-packages] [Bug 1809206]

2019-07-02 Thread serdar2005

Hp is a complete Linux enemy

Hp Computer:

[serdar@archlinux Desktop]$ uname -a
Linux archlinux 5.1.12-arch1-1-ARCH #1 SMP PREEMPT Wed Jun 19 09:16:00 UTC 2019 
x86_64 GNU/Linux

[serdar@archlinux Desktop]$ dmesg | grep Error
[1.813390] RAS: Correctable Errors collector initialized.
[4.818789] ACPI BIOS Error (bug): AE_AML_BUFFER_LIMIT, Field [D128] at bit 
offset/length 128/1024 exceeds size of target Buffer (160 bits) 
(20190215/dsopcode-198)
[4.818801] ACPI Error: Aborting method \HWMC due to previous error 
(AE_AML_BUFFER_LIMIT) (20190215/psparse-529)
[4.818813] ACPI Error: Aborting method \_SB.WMID.WMAA due to previous error 
(AE_AML_BUFFER_LIMIT) (20190215/psparse-529)
[4.820585] ACPI BIOS Error (bug): AE_AML_BUFFER_LIMIT, Field [D128] at bit 
offset/length 128/1024 exceeds size of target Buffer (160 bits) 
(20190215/dsopcode-198)
[4.820592] ACPI Error: Aborting method \HWMC due to previous error 
(AE_AML_BUFFER_LIMIT) (20190215/psparse-529)
[4.820601] ACPI Error: Aborting method \_SB.WMID.WMAA due to previous error 
(AE_AML_BUFFER_LIMIT) (20190215/psparse-529)
[4.821508] ACPI BIOS Error (bug): AE_AML_BUFFER_LIMIT, Field [D128] at bit 
offset/length 128/1024 exceeds size of target Buffer (160 bits) 
(20190215/dsopcode-198)
[4.821514] ACPI Error: Aborting method \HWMC due to previous error 
(AE_AML_BUFFER_LIMIT) (20190215/psparse-529)
[4.821522] ACPI Error: Aborting method \_SB.WMID.WMAA due to previous error 
(AE_AML_BUFFER_LIMIT) (20190215/psparse-529)
[4.824655] ACPI BIOS Error (bug): AE_AML_BUFFER_LIMIT, Field [D128] at bit 
offset/length 128/1024 exceeds size of target Buffer (160 bits) 
(20190215/dsopcode-198)
[4.824667] ACPI Error: Aborting method \HWMC due to previous error 
(AE_AML_BUFFER_LIMIT) (20190215/psparse-529)
[4.824679] ACPI Error: Aborting method \_SB.WMID.WMAA due to previous error 
(AE_AML_BUFFER_LIMIT) (20190215/psparse-529)
[4.824756] ACPI BIOS Error (bug): AE_AML_BUFFER_LIMIT, Field [D128] at bit 
offset/length 128/1024 exceeds size of target Buffer (160 bits) 
(20190215/dsopcode-198)
[4.824762] ACPI Error: Aborting method \HWMC due to previous error 
(AE_AML_BUFFER_LIMIT) (20190215/psparse-529)
[4.824771] ACPI Error: Aborting method \_SB.WMID.WMAA due to previous error 
(AE_AML_BUFFER_LIMIT) (20190215/psparse-529)

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

Title:
  Amd ACPI Error

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

Bug description:
  Hi
  Hp Laptop
  Amd A10 9600p

  Ubuntu 18.10 
  Kernel: all kernel acpi error

  mesg | grep Error
  [3.546921] RAS: Correctable Errors collector initialized.
  [9.979321] ACPI Error: Field [D128] at bit offset/length 128/1024 exceeds 
size of target Buffer (160 bits) (20180531/dsopcode-201)
  [9.979438] ACPI Error: Method parse/execution failed \HWMC, 
AE_AML_BUFFER_LIMIT (20180531/psparse-516)
  [9.979484] ACPI Error: Method parse/execution failed \_SB.WMID.WMAA, 
AE_AML_BUFFER_LIMIT (20180531/psparse-516)
  [9.979764] ACPI Error: Field [D128] at bit offset/length 128/1024 exceeds 
size of target Buffer (160 bits) (20180531/dsopcode-201)
  [9.979872] ACPI Error: Method parse/execution failed \HWMC, 
AE_AML_BUFFER_LIMIT (20180531/psparse-516)
  [9.988903] ACPI Error: Method parse/execution failed \_SB.WMID.WMAA, 
AE_AML_BUFFER_LIMIT (20180531/psparse-516)
  [9.989220] ACPI Error: Field [D128] at bit offset/length 128/1024 exceeds 
size of target Buffer (160 bits) (20180531/dsopcode-201)
  [9.989318] ACPI Error: Method parse/execution failed \HWMC, 
AE_AML_BUFFER_LIMIT (20180531/psparse-516)
  [9.989358] ACPI Error: Method parse/execution failed \_SB.WMID.WMAA, 
AE_AML_BUFFER_LIMIT (20180531/psparse-516)
  [9.990180] ACPI Error: Field [D128] at bit offset/length 128/1024 exceeds 
size of target Buffer (160 bits) (20180531/dsopcode-201)
  [9.990274] ACPI Error: Method parse/execution failed \HWMC, 
AE_AML_BUFFER_LIMIT (20180531/psparse-516)
  [9.990312] ACPI Error: Method parse/execution failed \_SB.WMID.WMAA, 
AE_AML_BUFFER_LIMIT (20180531/psparse-516)
  [9.990557] ACPI Error: Field [D128] at bit offset/length 128/1024 exceeds 
size of target Buffer (160 bits) (20180531/dsopcode-201)
  [9.990646] ACPI Error: Method parse/execution failed \HWMC, 
AE_AML_BUFFER_LIMIT (20180531/psparse-516)
  [9.990682] ACPI Error: Method parse/execution failed \_SB.WMID.WMAA, 
AE_AML_BUFFER_LIMIT (20180531/psparse-516)

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

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

[Kernel-packages] [Bug 1834904] Re: linux: 4.18.0-26.27 -proposed tracker

** Summary changed:

- linux:  -proposed tracker
+ linux: 4.18.0-26.27 -proposed tracker

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

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

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

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

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

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

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

Title:
  linux: 4.18.0-26.27 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  In Progress
Status in Kernel SRU Workflow prepare-package-meta series:
  In Progress
Status in Kernel SRU Workflow prepare-package-signed series:
  In Progress
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Cosmic:
  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 1834903 (bionic/linux-hwe)
  derivatives: bug 1834880 (linux-raspi2), bug 1834883 (linux-aws), bug 1834893 
(linux-azure), bug 1834899 (linux-gcp), bug 1834901 (linux-kvm)

  -- swm properties --
  phase: Ready for Packaging
  phase-changed: Monday, 01. July 2019 16:07 UTC
  reason:
prepare-package: Pending -- version not specified
  variant: debs

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

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

[Kernel-packages] [Bug 1563110]

2019-07-02 Thread ric-82

(In reply to mirh from comment #113)
> https://mailman.alsa-project.org/pipermail/alsa-devel/2019-May/149706.html
> 
> CX2072X is landing in 5.3.

That's good news! I'll look forward to it, thanks :)

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

Title:
  No sound on Asus e200ha, intel sst with cx2072x codec

Status in ALSA driver:
  Confirmed
Status in alsa-driver package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released

Bug description:
  I've recently bought an Asus e200ha.
  Sound in this laptop doesn't work.
  The sound card is an intel sst with codec conexant cx2072x

  aplay -l:
  aplay: device_list:268: no soundcard found...
  in the sound setting there is a "Dummy output"
  --- 
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=7b77dc46-7d5b-4869-83dd-739980736c3a
  InstallationDate: Installed on 2016-03-28 (0 days ago)
  InstallationMedia: Linux Mint 17.3 "Rosa" - Release amd64 20160105
  Lsusb:
   Bus 002 Device 002: ID 0781:5583 SanDisk Corp. 
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 13d3:3496 IMC Networks 
   Bus 001 Device 002: ID 04f2:b54b Chicony Electronics Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. E200HA
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-32-generic 
root=UUID=50fb13c0-a8cd-441d-a38b-c0295c1b9a15 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.19.0-32.37~14.04.1-generic 3.19.8-ckt7
  RelatedPackageVersions:
   linux-restricted-modules-3.19.0-32-generic N/A
   linux-backports-modules-3.19.0-32-generic  N/A
   linux-firmware 1.127.16
  Tags:  rosa
  Uname: Linux 3.19.0-32-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/26/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E200HA.203
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: E200HA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrE200HA.203:bd11/26/2015:svnASUSTeKCOMPUTERINC.:pnE200HA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnE200HA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: E200HA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/alsa-driver/+bug/1563110/+subscriptions

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

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

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

apport-collect 1835054

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

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

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

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

** Tags added: 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/1835054

Title:
  Missing NIC driver for Armada 8040 (Macchiatobin)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  At least in Ubuntu 19.04, the arm64 kernel (linux-image-5.0.0) is not
  building CONFIG_MVPP2 (depends on CONFIG_ARCH_MVEBU) -  a driver for
  network controllers(s) in Marvell SOCs, particularly Armada 8040 -
  neither as a model or a built-in:

  $ uname -m
  aarch64
  $ grep MVPP2 /boot/config-5.0.0-20-generic 
  $

  It makes very hard (and impossible for non-advanced users) to install
  and use Ubuntu on the Macchiatobin board (http://macchiatobin.net/) -
  a reasonably priced and performant server/mini-desktop platform.

  Could it be added, please, and the installer image re-generated.

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

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

[Kernel-packages] [Bug 1834904] Re: linux: 4.18.0-26.27 -proposed tracker

** 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 1834903 (bionic/linux-hwe)
  derivatives: bug 1834880 (linux-raspi2), bug 1834883 (linux-aws), bug 1834893 
(linux-azure), bug 1834899 (linux-gcp), bug 1834901 (linux-kvm)
  
  -- swm properties --
- phase: Ready for Packaging
- phase-changed: Monday, 01. July 2019 16:07 UTC
+ phase: Packaging
+ phase-changed: Tuesday, 02. July 2019 13:30 UTC
  reason:
-   prepare-package: Pending -- version not specified
+   prepare-package: Pending -- package not yet uploaded
+   prepare-package-meta: Pending -- package not yet uploaded
+   prepare-package-signed: Pending -- package not yet uploaded
  variant: debs

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

Title:
  linux: 4.18.0-26.27 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  In Progress
Status in Kernel SRU Workflow prepare-package-meta series:
  In Progress
Status in Kernel SRU Workflow prepare-package-signed series:
  In Progress
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Cosmic:
  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 1834903 (bionic/linux-hwe)
  derivatives: bug 1834880 (linux-raspi2), bug 1834883 (linux-aws), bug 1834893 
(linux-azure), bug 1834899 (linux-gcp), bug 1834901 (linux-kvm)

  -- swm properties --
  phase: Packaging
  phase-changed: Tuesday, 02. July 2019 13:30 UTC
  reason:
prepare-package: Pending -- package not yet uploaded
prepare-package-meta: Pending -- package not yet uploaded
prepare-package-signed: Pending -- package not yet uploaded
  variant: debs

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

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

[Kernel-packages] [Bug 1835054] Re: Missing NIC driver for Armada 8040 (Macchiatobin)

2019-07-02 Thread Paweł Moll

Can't really provide logs here... One thing I figured out in the
meantime is that the source package seems to be building it for armhf:

debian.master/config/config.common.ubuntu:CONFIG_MVPP2=m
debian.master/config/annotations:CONFIG_MVPP2   
 policy<{'armhf': 'm'}>

so perhaps all is needed is adding a policy for arm64.

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

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

Title:
  Missing NIC driver for Armada 8040 (Macchiatobin)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  At least in Ubuntu 19.04, the arm64 kernel (linux-image-5.0.0) is not
  building CONFIG_MVPP2 (depends on CONFIG_ARCH_MVEBU) -  a driver for
  network controllers(s) in Marvell SOCs, particularly Armada 8040 -
  neither as a model or a built-in:

  $ uname -m
  aarch64
  $ grep MVPP2 /boot/config-5.0.0-20-generic 
  $

  It makes very hard (and impossible for non-advanced users) to install
  and use Ubuntu on the Macchiatobin board (http://macchiatobin.net/) -
  a reasonably priced and performant server/mini-desktop platform.

  Could it be added, please, and the installer image re-generated.

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

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

Re: [Kernel-packages] [Bug 1831710] Re: Touchpad not working (Lenevo Ideapad 330 series)

2019-07-02 Thread Sumneet Kaur Bamrah

Hi,
Want to share an update. The following kernels are available. It is
becoming impractical to manually load the earliest version while booting
everytime.
Please guide as to how to proceed.

On Fri, Jun 28, 2019, 9:26 PM Sumneet Kaur Bamrah 
wrote:

> Hi,
> Tried loading/booting. Keep getting the same error. Please help, unable to
> boot normally.
>
>
> On Thu, Jun 27, 2019, 11:52 AM Sumneet Kaur Bamrah <
> sumneetbam...@gmail.com> wrote:
>
>> Thank you for being so patient! I managed to execute the command - `sudo
>> apt install linux-generic-hwe-18.04-edge`.
>>
>>
>> On Thu, Jun 27, 2019 at 11:11 AM Kai-Heng Feng <
>> kai.heng.f...@canonical.com> wrote:
>>
>>> Press ESC in GRUB, then use down arrow to pick an older kernel.
>>>
>>> --
>>> You received this bug notification because you are subscribed to the bug
>>> report.
>>> https://bugs.launchpad.net/bugs/1831710
>>>
>>> Title:
>>>   Touchpad not working (Lenevo Ideapad 330 series)
>>>
>>> Status in linux package in Ubuntu:
>>>   Confirmed
>>>
>>> Bug description:
>>>   The touch pad has not been used since the purchase of the product.
>>>
>>>   ProblemType: Bug
>>>   DistroRelease: Ubuntu 18.04
>>>   Package: linux-image-4.18.0-21-generic 4.18.0-21.22~18.04.1
>>>   ProcVersionSignature: Ubuntu 4.18.0-21.22~18.04.1-generic 4.18.20
>>>   Uname: Linux 4.18.0-21-generic x86_64
>>>   ApportVersion: 2.20.9-0ubuntu7.6
>>>   Architecture: amd64
>>>   CurrentDesktop: ubuntu:GNOME
>>>   Date: Wed Jun  5 13:41:22 2019
>>>   InstallationDate: Installed on 2019-06-05 (0 days ago)
>>>   InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64
>>> (20190210)
>>>   SourcePackage: linux-signed-hwe
>>>   UpgradeStatus: No upgrade log present (probably fresh install)
>>>   ---
>>>   ProblemType: Bug
>>>   ApportVersion: 2.20.9-0ubuntu7.6
>>>   Architecture: amd64
>>>   AudioDevicesInUse:
>>>USERPID ACCESS COMMAND
>>>/dev/snd/controlC1:  athena 1232 F pulseaudio
>>>/dev/snd/pcmC1D0p:   athena 1232 F...m pulseaudio
>>>/dev/snd/controlC0:  athena 1232 F pulseaudio
>>>   CurrentDesktop: ubuntu:GNOME
>>>   DistroRelease: Ubuntu 18.04
>>>   InstallationDate: Installed on 2019-06-05 (1 days ago)
>>>   InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64
>>> (20190210)
>>>   MachineType: LENOVO 81D2
>>>   Package: linux (not installed)
>>>   ProcFB: 0 amdgpudrmfb
>>>   ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-21-generic
>>> root=UUID=29a08da7-0f52-4ee8-8424-f2b37885999f ro quiet splash vt.handoff=1
>>>   ProcVersionSignature: Ubuntu 4.18.0-21.22~18.04.1-generic 4.18.20
>>>   RelatedPackageVersions:
>>>linux-restricted-modules-4.18.0-21-generic N/A
>>>linux-backports-modules-4.18.0-21-generic  N/A
>>>linux-firmware 1.173.6
>>>   Tags:  bionic
>>>   Uname: Linux 4.18.0-21-generic x86_64
>>>   UpgradeStatus: No upgrade log present (probably fresh install)
>>>   UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
>>>   _MarkForUpload: True
>>>   dmi.bios.date: 12/10/2018
>>>   dmi.bios.vendor: LENOVO
>>>   dmi.bios.version: 7VCN46WW
>>>   dmi.board.asset.tag: NO Asset Tag
>>>   dmi.board.name: LNVNB161216
>>>   dmi.board.vendor: LENOVO
>>>   dmi.board.version: NO DPK
>>>   dmi.chassis.asset.tag: NO Asset Tag
>>>   dmi.chassis.type: 10
>>>   dmi.chassis.vendor: LENOVO
>>>   dmi.chassis.version: Lenovo ideapad 330-15ARR
>>>   dmi.modalias:
>>> dmi:bvnLENOVO:bvr7VCN46WW:bd12/10/2018:svnLENOVO:pn81D2:pvrLenovoideapad330-15ARR:rvnLENOVO:rnLNVNB161216:rvrNODPK:cvnLENOVO:ct10:cvrLenovoideapad330-15ARR:
>>>   dmi.product.family: ideapad 330-15ARR
>>>   dmi.product.name: 81D2
>>>   dmi.product.sku: LENOVO_MT_81D2_BU_idea_FM_ideapad 330-15ARR
>>>   dmi.product.version: Lenovo ideapad 330-15ARR
>>>   dmi.sys.vendor: LENOVO
>>>
>>> To manage notifications about this bug go to:
>>>
>>> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1831710/+subscriptions
>>>
>>
>>
>> --
>> Thanks and Regards,
>> Sumneet Kaur Bamrah
>>
>>


** Attachment added: "P_20190702_191548_001.jpg"
   
https://bugs.launchpad.net/bugs/1831710/+attachment/5274679/+files/P_20190702_191548_001.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/1831710

Title:
  Touchpad not working (Lenevo Ideapad 330 series)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The touch pad has not been used since the purchase of the product.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.18.0-21-generic 4.18.0-21.22~18.04.1
  ProcVersionSignature: Ubuntu 4.18.0-21.22~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-21-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jun  5 13:41:22 2019
  InstallationDate: Installed on 2019-06-05 (0 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beave

[Kernel-packages] [Bug 1834902] Re: linux: 5.0.0-21.22 -proposed tracker

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

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

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

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

** Description changed:

  This bug 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 1834898 (bionic/linux-hwe-edge), bug 1834900 
(bionic/linux-oem-osp1)
  derivatives: bug 1834884 (linux-raspi2), bug 1834886 (linux-aws), bug 1834888 
(linux-azure), bug 1834891 (linux-gcp), bug 1834892 (linux-kvm), bug 1834894 
(linux-snapdragon)
  
  -- swm properties --
- phase: Packaging
- phase-changed: Tuesday, 02. July 2019 10:31 UTC
+ phase: Holding before Promote to Proposed
+ phase-changed: Tuesday, 02. July 2019 14:00 UTC
  reason:
-   prepare-package: Pending -- package not yet uploaded
-   prepare-package-lrm: Pending -- package not yet uploaded
-   prepare-package-meta: Pending -- package not yet uploaded
-   prepare-package-signed: Pending -- package not yet uploaded
+   promote-to-proposed: Ongoing -- builds not complete in ppa 
main:building,meta:building,signed:building,lrm:building
  variant: debs

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

Title:
  linux: 5.0.0-21.22 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-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:
  New
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
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 1834898 (bionic/linux-hwe-edge), bug 1834900 
(bionic/linux-oem-osp1)
  derivatives: bug 1834884 (linux-raspi2), bug 1834886 (linux-aws), bug 1834888 
(linux-azure), bug 1834891 (linux-gcp), bug 1834892 (linux-kvm), bug 1834894 
(linux-snapdragon)

  -- swm properties --
  phase: Holding before Promote to Proposed
  phase-changed: Tuesday, 02. July 2019 14:00 UTC
  reason:
promote-to-proposed: Ongoing -- builds not complete in ppa 
main:building,meta:building,signed:building,lrm:building
  variant: debs

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

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

[Kernel-packages] [Bug 1834894] Re: linux-snapdragon: -proposed tracker

** Changed in: kernel-sru-workflow/prepare-package
   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 --
  kernel-stable-master-bug: 1834902
- phase: Holding before Packaging
- phase-changed: Monday, 01. July 2019 16:05 UTC
+ phase: Ready for Packaging
+ phase-changed: Tuesday, 02. July 2019 14:03 UTC
  reason:
-   prepare-package: Stalled -- waiting for master bug
+   prepare-package: Pending -- version not specified
  variant: debs

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

Title:
  linux-snapdragon:  -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  Confirmed
Status in Kernel SRU Workflow prepare-package-meta series:
  New
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Invalid
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
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 --
  kernel-stable-master-bug: 1834902
  phase: Ready for Packaging
  phase-changed: Tuesday, 02. July 2019 14:03 UTC
  reason:
prepare-package: Pending -- version not specified
  variant: debs

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

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

[Kernel-packages] [Bug 1834888] Re: linux-azure: -proposed tracker

** Changed in: kernel-sru-workflow/prepare-package
   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 --
  kernel-stable-master-bug: 1834902
- phase: Holding before Packaging
- phase-changed: Monday, 01. July 2019 16:05 UTC
+ phase: Ready for Packaging
+ phase-changed: Tuesday, 02. July 2019 14:03 UTC
  reason:
-   prepare-package: Stalled -- waiting for master bug
+   prepare-package: Pending -- version not specified
  variant: debs

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

Title:
  linux-azure:  -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Confirmed
Status in Kernel SRU Workflow prepare-package-meta series:
  New
Status in Kernel SRU Workflow prepare-package-signed series:
  New
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow stakeholder-signoff series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
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 --
  kernel-stable-master-bug: 1834902
  phase: Ready for Packaging
  phase-changed: Tuesday, 02. July 2019 14:03 UTC
  reason:
prepare-package: Pending -- version not specified
  variant: debs

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

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

[Kernel-packages] [Bug 1834891] Re: linux-gcp: -proposed tracker

** Changed in: kernel-sru-workflow/prepare-package
   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 --
  kernel-stable-master-bug: 1834902
- phase: Holding before Packaging
- phase-changed: Monday, 01. July 2019 16:05 UTC
+ phase: Ready for Packaging
+ phase-changed: Tuesday, 02. July 2019 14:03 UTC
  reason:
-   prepare-package: Stalled -- waiting for master bug
+   prepare-package: Pending -- version not specified
  variant: debs

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

Title:
  linux-gcp:  -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Confirmed
Status in Kernel SRU Workflow prepare-package-meta series:
  New
Status in Kernel SRU Workflow prepare-package-signed series:
  New
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
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 --
  kernel-stable-master-bug: 1834902
  phase: Ready for Packaging
  phase-changed: Tuesday, 02. July 2019 14:03 UTC
  reason:
prepare-package: Pending -- version not specified
  variant: debs

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

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

[Kernel-packages] [Bug 1808957] Re: Dell XPS 13 (9370) defaults to s2idle sleep/suspend instead of deep, NVMe drains lots of power under s2idle

This bug was fixed in the package linux-oem-osp1 - 5.0.0-1012.13

---
linux-oem-osp1 (5.0.0-1012.13) bionic; urgency=medium

  * linux-oem-osp1: 5.0.0-1012.13 -proposed tracker (LP: #1833932)

  * Add DMIC support to oem-kernel (LP: #1826181)
- ASoC: SOF: Intel: hda: reduce ifdef usage for hda
- ASoC: SOF: Intel: hda: Enable jack detection in sof hda driver
- Revert "ASoC: SOF: Intel: hda: switch to use legacy IRQ mode"
- ASoC: SOF: Intel: hda: modify stream interrupt handler
- ASoC: SOF: Intel: fix warning for unused variable in non-HDA builds
- ASoC: hdac_hdmi: report codec link up/down status to bus
- ASoC: SOF: add runtime idle callback
- ASoC: SOF: Intel: implement runtime idle for CNL/APL
- ASoC: SOF: dont wake dsp up in kcontrol IO
- ASoC: codec: hdac_hdmi: fix pin connections at cvt enable
- ALSA: hda: fix headphone detection failed

  * [SRU][B/B-OEM/B-OEM-OSP-1/C/D/E] Add trackpoint middle button support of 2
new thinpads (LP: #1833637)
- Input: elantech - enable middle button support on 2 ThinkPads

  * [graphics] Enable ICL (LP: #1825940)
- drm/i915/icl: Add WaDisableBankHangMode
- drm/i915/icl: Adding few more device IDs for Ice Lake
- drm/i915/cfl: Adding another PCI Device ID.
- drm/i915: Accept alloc_size == blocks
- drm/i915: Don't pass plane state to skl_compute_plane_wm()
- drm/i915: Extract skl_compute_wm_params()
- drm/i915: Allocate enough DDB for the cursor
- drm/i915: Make sure cursor has enough ddb for the selected wm level
- drm/i915: Keep plane watermarks enabled more aggressively
- drm/i915: Move some variables to tighter scope
- drm/i915: Don't pass pipe_wm around so much
- drm/i915: Inline skl_update_pipe_wm() into its only caller
- drm/i915: Fix PSR2 selective update corruption after PSR1 setup
- drm/i915: Populate pipe_offsets[] & co. accurately
- drm/i915: Extract ilk_lut_10()
- drm/i915: Don't use split gamma when we don't have to
- drm/i915: Implement split/10bit gamma for ivb/hsw
- drm/i915: Add 10bit LUT for ilk/snb
- drm/i915: Add "10.6" LUT mode for i965+
- drm/i915: Expose the legacy LUT via the GAMMA_LUT/GAMMA_LUT_SIZE props on
  gen2/3
- drm/i915: Expose full 1024 LUT entries on ivb+
- drm/i915: Introduce struct class_instance for engines across the uAPI
- drm/i915: Fix skl+ max plane width
- drm/i915: Rename skl_wa_clkgating to the actual WA
- drm/i915: Fix the inconsistent RMW in WA 827
- drm/i915/icl: Fix clockgating issue when using scalers
- drm/i915: Always try to reset the GPU on takeover
- drm/i915: Add Wa_1409120013:icl,ehl
- drm/i915/icl: use ranges for voltage level lookup
- drm/i915/cnl: use ranges for voltage level lookup
- drm/i915/skl: use ranges for voltage level lookup

  * Sometimes touchpad automatically trigger double click (LP: #1833484)
- SAUCE: i2c: designware: Add disable runtime pm quirk

  * Add pointstick support on HP ZBook 17 G5 (LP: #1833387)
- Revert "HID: multitouch: Support ALPS PTP stick with pid 0x120A"
- SAUCE: HID: multitouch: Add pointstick support for ALPS Touchpad

  * Dell XPS 13 (9370) defaults to s2idle sleep/suspend instead of deep, NVMe
drains lots of power under s2idle (LP: #1808957)
- Revert "UBUNTU: SAUCE: pci/nvme: prevent WDC PC SN720 NVMe from entering 
D3
  and being disabled"
- Revert "UBUNTU: SAUCE: nvme: add quirk to not call disable function when
  suspending"
- Revert "UBUTU: SAUCE: pci: prevent Intel NVMe SSDPEKKF from entering D3"
- Revert "UBUNTU: SAUCE: nvme: add quirk to not call disable function when
  suspending"
- Revert "UBUNTU: SAUCE: pci: prevent sk hynix nvme from entering D3"
- PCI: PM: Avoid possible suspend-to-idle issue
- SAUCE: PCI: PM: Skip devices in D0 for suspend-to-idle
- nvme-pci: Sync queues on reset
- nvme: Export get and set features
- nvme-pci: Use host managed power state for suspend

  * Intel WiFi (CNVi) module has no function on Comet Lake [8086:02f0]
(LP: #1833065)
- iwlwifi: add support for 6-7 GHz channels
- iwlwifi: support new NVM response API
- iwlwifi: for AX210 device support radio GF4
- iwlwifi: bump FW API to 47 for 22000 series
- iwlwifi: remove unused 0x40C0 PCI device IDs
- iwlwifi: bump FW API to 48 for 22000 series
- iwlwifi: bump FW API to 49 for 22000 series
- iwlwifi: add new cards for 22000 and fix struct name
- iwlwifi: bump FW API to 50 for 22000 series
- iwlwifi: add new cards for 22000 and change wrong structs
- iwlwifi: change 0x02F0 fw from qu to quz

  [ Ubuntu: 5.0.0-20.21 ]

  * linux: 5.0.0-20.21 -proposed tracker (LP: #1833934)
  * CVE-2019-11479
- SAUCE: tcp: add tcp_min_snd_mss sysctl
- SAUCE: tcp: enforce tcp_min_snd_mss in tcp_mtu_probing()
  * Remote denial of service (resource exhaustion) caused by TCP SACK scoreboard
manipulatio

[Kernel-packages] [Bug 1833387] Re: Add pointstick support on HP ZBook 17 G5

This bug was fixed in the package linux-oem-osp1 - 5.0.0-1012.13

---
linux-oem-osp1 (5.0.0-1012.13) bionic; urgency=medium

  * linux-oem-osp1: 5.0.0-1012.13 -proposed tracker (LP: #1833932)

  * Add DMIC support to oem-kernel (LP: #1826181)
- ASoC: SOF: Intel: hda: reduce ifdef usage for hda
- ASoC: SOF: Intel: hda: Enable jack detection in sof hda driver
- Revert "ASoC: SOF: Intel: hda: switch to use legacy IRQ mode"
- ASoC: SOF: Intel: hda: modify stream interrupt handler
- ASoC: SOF: Intel: fix warning for unused variable in non-HDA builds
- ASoC: hdac_hdmi: report codec link up/down status to bus
- ASoC: SOF: add runtime idle callback
- ASoC: SOF: Intel: implement runtime idle for CNL/APL
- ASoC: SOF: dont wake dsp up in kcontrol IO
- ASoC: codec: hdac_hdmi: fix pin connections at cvt enable
- ALSA: hda: fix headphone detection failed

  * [SRU][B/B-OEM/B-OEM-OSP-1/C/D/E] Add trackpoint middle button support of 2
new thinpads (LP: #1833637)
- Input: elantech - enable middle button support on 2 ThinkPads

  * [graphics] Enable ICL (LP: #1825940)
- drm/i915/icl: Add WaDisableBankHangMode
- drm/i915/icl: Adding few more device IDs for Ice Lake
- drm/i915/cfl: Adding another PCI Device ID.
- drm/i915: Accept alloc_size == blocks
- drm/i915: Don't pass plane state to skl_compute_plane_wm()
- drm/i915: Extract skl_compute_wm_params()
- drm/i915: Allocate enough DDB for the cursor
- drm/i915: Make sure cursor has enough ddb for the selected wm level
- drm/i915: Keep plane watermarks enabled more aggressively
- drm/i915: Move some variables to tighter scope
- drm/i915: Don't pass pipe_wm around so much
- drm/i915: Inline skl_update_pipe_wm() into its only caller
- drm/i915: Fix PSR2 selective update corruption after PSR1 setup
- drm/i915: Populate pipe_offsets[] & co. accurately
- drm/i915: Extract ilk_lut_10()
- drm/i915: Don't use split gamma when we don't have to
- drm/i915: Implement split/10bit gamma for ivb/hsw
- drm/i915: Add 10bit LUT for ilk/snb
- drm/i915: Add "10.6" LUT mode for i965+
- drm/i915: Expose the legacy LUT via the GAMMA_LUT/GAMMA_LUT_SIZE props on
  gen2/3
- drm/i915: Expose full 1024 LUT entries on ivb+
- drm/i915: Introduce struct class_instance for engines across the uAPI
- drm/i915: Fix skl+ max plane width
- drm/i915: Rename skl_wa_clkgating to the actual WA
- drm/i915: Fix the inconsistent RMW in WA 827
- drm/i915/icl: Fix clockgating issue when using scalers
- drm/i915: Always try to reset the GPU on takeover
- drm/i915: Add Wa_1409120013:icl,ehl
- drm/i915/icl: use ranges for voltage level lookup
- drm/i915/cnl: use ranges for voltage level lookup
- drm/i915/skl: use ranges for voltage level lookup

  * Sometimes touchpad automatically trigger double click (LP: #1833484)
- SAUCE: i2c: designware: Add disable runtime pm quirk

  * Add pointstick support on HP ZBook 17 G5 (LP: #1833387)
- Revert "HID: multitouch: Support ALPS PTP stick with pid 0x120A"
- SAUCE: HID: multitouch: Add pointstick support for ALPS Touchpad

  * Dell XPS 13 (9370) defaults to s2idle sleep/suspend instead of deep, NVMe
drains lots of power under s2idle (LP: #1808957)
- Revert "UBUNTU: SAUCE: pci/nvme: prevent WDC PC SN720 NVMe from entering 
D3
  and being disabled"
- Revert "UBUNTU: SAUCE: nvme: add quirk to not call disable function when
  suspending"
- Revert "UBUTU: SAUCE: pci: prevent Intel NVMe SSDPEKKF from entering D3"
- Revert "UBUNTU: SAUCE: nvme: add quirk to not call disable function when
  suspending"
- Revert "UBUNTU: SAUCE: pci: prevent sk hynix nvme from entering D3"
- PCI: PM: Avoid possible suspend-to-idle issue
- SAUCE: PCI: PM: Skip devices in D0 for suspend-to-idle
- nvme-pci: Sync queues on reset
- nvme: Export get and set features
- nvme-pci: Use host managed power state for suspend

  * Intel WiFi (CNVi) module has no function on Comet Lake [8086:02f0]
(LP: #1833065)
- iwlwifi: add support for 6-7 GHz channels
- iwlwifi: support new NVM response API
- iwlwifi: for AX210 device support radio GF4
- iwlwifi: bump FW API to 47 for 22000 series
- iwlwifi: remove unused 0x40C0 PCI device IDs
- iwlwifi: bump FW API to 48 for 22000 series
- iwlwifi: bump FW API to 49 for 22000 series
- iwlwifi: add new cards for 22000 and fix struct name
- iwlwifi: bump FW API to 50 for 22000 series
- iwlwifi: add new cards for 22000 and change wrong structs
- iwlwifi: change 0x02F0 fw from qu to quz

  [ Ubuntu: 5.0.0-20.21 ]

  * linux: 5.0.0-20.21 -proposed tracker (LP: #1833934)
  * CVE-2019-11479
- SAUCE: tcp: add tcp_min_snd_mss sysctl
- SAUCE: tcp: enforce tcp_min_snd_mss in tcp_mtu_probing()
  * Remote denial of service (resource exhaustion) caused by TCP SACK scoreboard
manipulatio

[Kernel-packages] [Bug 1833065] Re: Intel WiFi (CNVi) module has no function on Comet Lake [8086:02f0]

This bug was fixed in the package linux-oem-osp1 - 5.0.0-1012.13

---
linux-oem-osp1 (5.0.0-1012.13) bionic; urgency=medium

  * linux-oem-osp1: 5.0.0-1012.13 -proposed tracker (LP: #1833932)

  * Add DMIC support to oem-kernel (LP: #1826181)
- ASoC: SOF: Intel: hda: reduce ifdef usage for hda
- ASoC: SOF: Intel: hda: Enable jack detection in sof hda driver
- Revert "ASoC: SOF: Intel: hda: switch to use legacy IRQ mode"
- ASoC: SOF: Intel: hda: modify stream interrupt handler
- ASoC: SOF: Intel: fix warning for unused variable in non-HDA builds
- ASoC: hdac_hdmi: report codec link up/down status to bus
- ASoC: SOF: add runtime idle callback
- ASoC: SOF: Intel: implement runtime idle for CNL/APL
- ASoC: SOF: dont wake dsp up in kcontrol IO
- ASoC: codec: hdac_hdmi: fix pin connections at cvt enable
- ALSA: hda: fix headphone detection failed

  * [SRU][B/B-OEM/B-OEM-OSP-1/C/D/E] Add trackpoint middle button support of 2
new thinpads (LP: #1833637)
- Input: elantech - enable middle button support on 2 ThinkPads

  * [graphics] Enable ICL (LP: #1825940)
- drm/i915/icl: Add WaDisableBankHangMode
- drm/i915/icl: Adding few more device IDs for Ice Lake
- drm/i915/cfl: Adding another PCI Device ID.
- drm/i915: Accept alloc_size == blocks
- drm/i915: Don't pass plane state to skl_compute_plane_wm()
- drm/i915: Extract skl_compute_wm_params()
- drm/i915: Allocate enough DDB for the cursor
- drm/i915: Make sure cursor has enough ddb for the selected wm level
- drm/i915: Keep plane watermarks enabled more aggressively
- drm/i915: Move some variables to tighter scope
- drm/i915: Don't pass pipe_wm around so much
- drm/i915: Inline skl_update_pipe_wm() into its only caller
- drm/i915: Fix PSR2 selective update corruption after PSR1 setup
- drm/i915: Populate pipe_offsets[] & co. accurately
- drm/i915: Extract ilk_lut_10()
- drm/i915: Don't use split gamma when we don't have to
- drm/i915: Implement split/10bit gamma for ivb/hsw
- drm/i915: Add 10bit LUT for ilk/snb
- drm/i915: Add "10.6" LUT mode for i965+
- drm/i915: Expose the legacy LUT via the GAMMA_LUT/GAMMA_LUT_SIZE props on
  gen2/3
- drm/i915: Expose full 1024 LUT entries on ivb+
- drm/i915: Introduce struct class_instance for engines across the uAPI
- drm/i915: Fix skl+ max plane width
- drm/i915: Rename skl_wa_clkgating to the actual WA
- drm/i915: Fix the inconsistent RMW in WA 827
- drm/i915/icl: Fix clockgating issue when using scalers
- drm/i915: Always try to reset the GPU on takeover
- drm/i915: Add Wa_1409120013:icl,ehl
- drm/i915/icl: use ranges for voltage level lookup
- drm/i915/cnl: use ranges for voltage level lookup
- drm/i915/skl: use ranges for voltage level lookup

  * Sometimes touchpad automatically trigger double click (LP: #1833484)
- SAUCE: i2c: designware: Add disable runtime pm quirk

  * Add pointstick support on HP ZBook 17 G5 (LP: #1833387)
- Revert "HID: multitouch: Support ALPS PTP stick with pid 0x120A"
- SAUCE: HID: multitouch: Add pointstick support for ALPS Touchpad

  * Dell XPS 13 (9370) defaults to s2idle sleep/suspend instead of deep, NVMe
drains lots of power under s2idle (LP: #1808957)
- Revert "UBUNTU: SAUCE: pci/nvme: prevent WDC PC SN720 NVMe from entering 
D3
  and being disabled"
- Revert "UBUNTU: SAUCE: nvme: add quirk to not call disable function when
  suspending"
- Revert "UBUTU: SAUCE: pci: prevent Intel NVMe SSDPEKKF from entering D3"
- Revert "UBUNTU: SAUCE: nvme: add quirk to not call disable function when
  suspending"
- Revert "UBUNTU: SAUCE: pci: prevent sk hynix nvme from entering D3"
- PCI: PM: Avoid possible suspend-to-idle issue
- SAUCE: PCI: PM: Skip devices in D0 for suspend-to-idle
- nvme-pci: Sync queues on reset
- nvme: Export get and set features
- nvme-pci: Use host managed power state for suspend

  * Intel WiFi (CNVi) module has no function on Comet Lake [8086:02f0]
(LP: #1833065)
- iwlwifi: add support for 6-7 GHz channels
- iwlwifi: support new NVM response API
- iwlwifi: for AX210 device support radio GF4
- iwlwifi: bump FW API to 47 for 22000 series
- iwlwifi: remove unused 0x40C0 PCI device IDs
- iwlwifi: bump FW API to 48 for 22000 series
- iwlwifi: bump FW API to 49 for 22000 series
- iwlwifi: add new cards for 22000 and fix struct name
- iwlwifi: bump FW API to 50 for 22000 series
- iwlwifi: add new cards for 22000 and change wrong structs
- iwlwifi: change 0x02F0 fw from qu to quz

  [ Ubuntu: 5.0.0-20.21 ]

  * linux: 5.0.0-20.21 -proposed tracker (LP: #1833934)
  * CVE-2019-11479
- SAUCE: tcp: add tcp_min_snd_mss sysctl
- SAUCE: tcp: enforce tcp_min_snd_mss in tcp_mtu_probing()
  * Remote denial of service (resource exhaustion) caused by TCP SACK scoreboard
manipulatio

[Kernel-packages] [Bug 1833484] Re: Sometimes touchpad automatically trigger double click

This bug was fixed in the package linux-oem-osp1 - 5.0.0-1012.13

---
linux-oem-osp1 (5.0.0-1012.13) bionic; urgency=medium

  * linux-oem-osp1: 5.0.0-1012.13 -proposed tracker (LP: #1833932)

  * Add DMIC support to oem-kernel (LP: #1826181)
- ASoC: SOF: Intel: hda: reduce ifdef usage for hda
- ASoC: SOF: Intel: hda: Enable jack detection in sof hda driver
- Revert "ASoC: SOF: Intel: hda: switch to use legacy IRQ mode"
- ASoC: SOF: Intel: hda: modify stream interrupt handler
- ASoC: SOF: Intel: fix warning for unused variable in non-HDA builds
- ASoC: hdac_hdmi: report codec link up/down status to bus
- ASoC: SOF: add runtime idle callback
- ASoC: SOF: Intel: implement runtime idle for CNL/APL
- ASoC: SOF: dont wake dsp up in kcontrol IO
- ASoC: codec: hdac_hdmi: fix pin connections at cvt enable
- ALSA: hda: fix headphone detection failed

  * [SRU][B/B-OEM/B-OEM-OSP-1/C/D/E] Add trackpoint middle button support of 2
new thinpads (LP: #1833637)
- Input: elantech - enable middle button support on 2 ThinkPads

  * [graphics] Enable ICL (LP: #1825940)
- drm/i915/icl: Add WaDisableBankHangMode
- drm/i915/icl: Adding few more device IDs for Ice Lake
- drm/i915/cfl: Adding another PCI Device ID.
- drm/i915: Accept alloc_size == blocks
- drm/i915: Don't pass plane state to skl_compute_plane_wm()
- drm/i915: Extract skl_compute_wm_params()
- drm/i915: Allocate enough DDB for the cursor
- drm/i915: Make sure cursor has enough ddb for the selected wm level
- drm/i915: Keep plane watermarks enabled more aggressively
- drm/i915: Move some variables to tighter scope
- drm/i915: Don't pass pipe_wm around so much
- drm/i915: Inline skl_update_pipe_wm() into its only caller
- drm/i915: Fix PSR2 selective update corruption after PSR1 setup
- drm/i915: Populate pipe_offsets[] & co. accurately
- drm/i915: Extract ilk_lut_10()
- drm/i915: Don't use split gamma when we don't have to
- drm/i915: Implement split/10bit gamma for ivb/hsw
- drm/i915: Add 10bit LUT for ilk/snb
- drm/i915: Add "10.6" LUT mode for i965+
- drm/i915: Expose the legacy LUT via the GAMMA_LUT/GAMMA_LUT_SIZE props on
  gen2/3
- drm/i915: Expose full 1024 LUT entries on ivb+
- drm/i915: Introduce struct class_instance for engines across the uAPI
- drm/i915: Fix skl+ max plane width
- drm/i915: Rename skl_wa_clkgating to the actual WA
- drm/i915: Fix the inconsistent RMW in WA 827
- drm/i915/icl: Fix clockgating issue when using scalers
- drm/i915: Always try to reset the GPU on takeover
- drm/i915: Add Wa_1409120013:icl,ehl
- drm/i915/icl: use ranges for voltage level lookup
- drm/i915/cnl: use ranges for voltage level lookup
- drm/i915/skl: use ranges for voltage level lookup

  * Sometimes touchpad automatically trigger double click (LP: #1833484)
- SAUCE: i2c: designware: Add disable runtime pm quirk

  * Add pointstick support on HP ZBook 17 G5 (LP: #1833387)
- Revert "HID: multitouch: Support ALPS PTP stick with pid 0x120A"
- SAUCE: HID: multitouch: Add pointstick support for ALPS Touchpad

  * Dell XPS 13 (9370) defaults to s2idle sleep/suspend instead of deep, NVMe
drains lots of power under s2idle (LP: #1808957)
- Revert "UBUNTU: SAUCE: pci/nvme: prevent WDC PC SN720 NVMe from entering 
D3
  and being disabled"
- Revert "UBUNTU: SAUCE: nvme: add quirk to not call disable function when
  suspending"
- Revert "UBUTU: SAUCE: pci: prevent Intel NVMe SSDPEKKF from entering D3"
- Revert "UBUNTU: SAUCE: nvme: add quirk to not call disable function when
  suspending"
- Revert "UBUNTU: SAUCE: pci: prevent sk hynix nvme from entering D3"
- PCI: PM: Avoid possible suspend-to-idle issue
- SAUCE: PCI: PM: Skip devices in D0 for suspend-to-idle
- nvme-pci: Sync queues on reset
- nvme: Export get and set features
- nvme-pci: Use host managed power state for suspend

  * Intel WiFi (CNVi) module has no function on Comet Lake [8086:02f0]
(LP: #1833065)
- iwlwifi: add support for 6-7 GHz channels
- iwlwifi: support new NVM response API
- iwlwifi: for AX210 device support radio GF4
- iwlwifi: bump FW API to 47 for 22000 series
- iwlwifi: remove unused 0x40C0 PCI device IDs
- iwlwifi: bump FW API to 48 for 22000 series
- iwlwifi: bump FW API to 49 for 22000 series
- iwlwifi: add new cards for 22000 and fix struct name
- iwlwifi: bump FW API to 50 for 22000 series
- iwlwifi: add new cards for 22000 and change wrong structs
- iwlwifi: change 0x02F0 fw from qu to quz

  [ Ubuntu: 5.0.0-20.21 ]

  * linux: 5.0.0-20.21 -proposed tracker (LP: #1833934)
  * CVE-2019-11479
- SAUCE: tcp: add tcp_min_snd_mss sysctl
- SAUCE: tcp: enforce tcp_min_snd_mss in tcp_mtu_probing()
  * Remote denial of service (resource exhaustion) caused by TCP SACK scoreboard
manipulatio

[Kernel-packages] [Bug 1834892] Re: linux-kvm: -proposed tracker

** Changed in: kernel-sru-workflow/prepare-package
   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 --
  kernel-stable-master-bug: 1834902
- phase: Holding before Packaging
- phase-changed: Monday, 01. July 2019 16:05 UTC
+ phase: Ready for Packaging
+ phase-changed: Tuesday, 02. July 2019 14:03 UTC
  reason:
-   prepare-package: Stalled -- waiting for master bug
+   prepare-package: Pending -- version not specified
  variant: debs

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

Title:
  linux-kvm:  -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Confirmed
Status in Kernel SRU Workflow prepare-package-meta series:
  New
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
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 --
  kernel-stable-master-bug: 1834902
  phase: Ready for Packaging
  phase-changed: Tuesday, 02. July 2019 14:03 UTC
  reason:
prepare-package: Pending -- version not specified
  variant: debs

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

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

[Kernel-packages] [Bug 1825940] Re: [graphics] Enable ICL

This bug was fixed in the package linux-oem-osp1 - 5.0.0-1012.13

---
linux-oem-osp1 (5.0.0-1012.13) bionic; urgency=medium

  * linux-oem-osp1: 5.0.0-1012.13 -proposed tracker (LP: #1833932)

  * Add DMIC support to oem-kernel (LP: #1826181)
- ASoC: SOF: Intel: hda: reduce ifdef usage for hda
- ASoC: SOF: Intel: hda: Enable jack detection in sof hda driver
- Revert "ASoC: SOF: Intel: hda: switch to use legacy IRQ mode"
- ASoC: SOF: Intel: hda: modify stream interrupt handler
- ASoC: SOF: Intel: fix warning for unused variable in non-HDA builds
- ASoC: hdac_hdmi: report codec link up/down status to bus
- ASoC: SOF: add runtime idle callback
- ASoC: SOF: Intel: implement runtime idle for CNL/APL
- ASoC: SOF: dont wake dsp up in kcontrol IO
- ASoC: codec: hdac_hdmi: fix pin connections at cvt enable
- ALSA: hda: fix headphone detection failed

  * [SRU][B/B-OEM/B-OEM-OSP-1/C/D/E] Add trackpoint middle button support of 2
new thinpads (LP: #1833637)
- Input: elantech - enable middle button support on 2 ThinkPads

  * [graphics] Enable ICL (LP: #1825940)
- drm/i915/icl: Add WaDisableBankHangMode
- drm/i915/icl: Adding few more device IDs for Ice Lake
- drm/i915/cfl: Adding another PCI Device ID.
- drm/i915: Accept alloc_size == blocks
- drm/i915: Don't pass plane state to skl_compute_plane_wm()
- drm/i915: Extract skl_compute_wm_params()
- drm/i915: Allocate enough DDB for the cursor
- drm/i915: Make sure cursor has enough ddb for the selected wm level
- drm/i915: Keep plane watermarks enabled more aggressively
- drm/i915: Move some variables to tighter scope
- drm/i915: Don't pass pipe_wm around so much
- drm/i915: Inline skl_update_pipe_wm() into its only caller
- drm/i915: Fix PSR2 selective update corruption after PSR1 setup
- drm/i915: Populate pipe_offsets[] & co. accurately
- drm/i915: Extract ilk_lut_10()
- drm/i915: Don't use split gamma when we don't have to
- drm/i915: Implement split/10bit gamma for ivb/hsw
- drm/i915: Add 10bit LUT for ilk/snb
- drm/i915: Add "10.6" LUT mode for i965+
- drm/i915: Expose the legacy LUT via the GAMMA_LUT/GAMMA_LUT_SIZE props on
  gen2/3
- drm/i915: Expose full 1024 LUT entries on ivb+
- drm/i915: Introduce struct class_instance for engines across the uAPI
- drm/i915: Fix skl+ max plane width
- drm/i915: Rename skl_wa_clkgating to the actual WA
- drm/i915: Fix the inconsistent RMW in WA 827
- drm/i915/icl: Fix clockgating issue when using scalers
- drm/i915: Always try to reset the GPU on takeover
- drm/i915: Add Wa_1409120013:icl,ehl
- drm/i915/icl: use ranges for voltage level lookup
- drm/i915/cnl: use ranges for voltage level lookup
- drm/i915/skl: use ranges for voltage level lookup

  * Sometimes touchpad automatically trigger double click (LP: #1833484)
- SAUCE: i2c: designware: Add disable runtime pm quirk

  * Add pointstick support on HP ZBook 17 G5 (LP: #1833387)
- Revert "HID: multitouch: Support ALPS PTP stick with pid 0x120A"
- SAUCE: HID: multitouch: Add pointstick support for ALPS Touchpad

  * Dell XPS 13 (9370) defaults to s2idle sleep/suspend instead of deep, NVMe
drains lots of power under s2idle (LP: #1808957)
- Revert "UBUNTU: SAUCE: pci/nvme: prevent WDC PC SN720 NVMe from entering 
D3
  and being disabled"
- Revert "UBUNTU: SAUCE: nvme: add quirk to not call disable function when
  suspending"
- Revert "UBUTU: SAUCE: pci: prevent Intel NVMe SSDPEKKF from entering D3"
- Revert "UBUNTU: SAUCE: nvme: add quirk to not call disable function when
  suspending"
- Revert "UBUNTU: SAUCE: pci: prevent sk hynix nvme from entering D3"
- PCI: PM: Avoid possible suspend-to-idle issue
- SAUCE: PCI: PM: Skip devices in D0 for suspend-to-idle
- nvme-pci: Sync queues on reset
- nvme: Export get and set features
- nvme-pci: Use host managed power state for suspend

  * Intel WiFi (CNVi) module has no function on Comet Lake [8086:02f0]
(LP: #1833065)
- iwlwifi: add support for 6-7 GHz channels
- iwlwifi: support new NVM response API
- iwlwifi: for AX210 device support radio GF4
- iwlwifi: bump FW API to 47 for 22000 series
- iwlwifi: remove unused 0x40C0 PCI device IDs
- iwlwifi: bump FW API to 48 for 22000 series
- iwlwifi: bump FW API to 49 for 22000 series
- iwlwifi: add new cards for 22000 and fix struct name
- iwlwifi: bump FW API to 50 for 22000 series
- iwlwifi: add new cards for 22000 and change wrong structs
- iwlwifi: change 0x02F0 fw from qu to quz

  [ Ubuntu: 5.0.0-20.21 ]

  * linux: 5.0.0-20.21 -proposed tracker (LP: #1833934)
  * CVE-2019-11479
- SAUCE: tcp: add tcp_min_snd_mss sysctl
- SAUCE: tcp: enforce tcp_min_snd_mss in tcp_mtu_probing()
  * Remote denial of service (resource exhaustion) caused by TCP SACK scoreboard
manipulatio

[Kernel-packages] [Bug 1834884] Re: linux-raspi2: -proposed tracker

** Changed in: kernel-sru-workflow/prepare-package
   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 --
  kernel-stable-master-bug: 1834902
- phase: Holding before Packaging
- phase-changed: Monday, 01. July 2019 16:04 UTC
+ phase: Ready for Packaging
+ phase-changed: Tuesday, 02. July 2019 14:02 UTC
  reason:
-   prepare-package: Stalled -- waiting for master bug
+   prepare-package: Pending -- version not specified
  variant: debs

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

Title:
  linux-raspi2:  -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  Confirmed
Status in Kernel SRU Workflow prepare-package-meta series:
  New
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Invalid
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
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 --
  kernel-stable-master-bug: 1834902
  phase: Ready for Packaging
  phase-changed: Tuesday, 02. July 2019 14:02 UTC
  reason:
prepare-package: Pending -- version not specified
  variant: debs

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

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

[Kernel-packages] [Bug 1834886] Re: linux-aws: -proposed tracker

** Changed in: kernel-sru-workflow/prepare-package
   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 --
  kernel-stable-master-bug: 1834902
- phase: Holding before Packaging
- phase-changed: Monday, 01. July 2019 16:04 UTC
+ phase: Ready for Packaging
+ phase-changed: Tuesday, 02. July 2019 14:03 UTC
  reason:
-   prepare-package: Stalled -- waiting for master bug
+   prepare-package: Pending -- version not specified
  variant: debs

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

Title:
  linux-aws:  -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Confirmed
Status in Kernel SRU Workflow prepare-package-meta series:
  New
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
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 --
  kernel-stable-master-bug: 1834902
  phase: Ready for Packaging
  phase-changed: Tuesday, 02. July 2019 14:03 UTC
  reason:
prepare-package: Pending -- version not specified
  variant: debs

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

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

Re: [Kernel-packages] [Bug 1447664] Re: 14e4:1687 broadcom tg3 network driver disconnects under high load

2019-07-02 Thread Paulo Abadie Guedes

Thank you, Kai-Heng Feng. Really appreciate it.

Currently I'm under a lot of pressure at work. But I will try this in the
next days, to see if it fixes the problem for us. My network still have the
same condition and my previous kernel versions are still breaking. So, it
should be easy to reproduce.
Will write back reporting as soon as I can.

Thank you again,
Paulo


On Tue, Jul 2, 2019, 03:15 Kai-Heng Feng 
wrote:

> Latest kernels in Xenial, Bionic, Cosmic and Disco have the following
> commit:
> commit 3a498606bb04af603a46ebde8296040b2de350d1
> Author: Sanjeev Bansal 
> Date:   Mon Jul 16 11:13:32 2018 +0530
>
> tg3: Add higher cpu clock for 5762.
>
> This patch has fix for TX timeout while running bi-directional
> traffic with 100 Mbps using 5762.
>
> Signed-off-by: Sanjeev Bansal 
> Signed-off-by: Siva Reddy Kallam 
> Reviewed-by: Michael Chan 
> Signed-off-by: David S. Miller 
>
> ** Changed in: linux (Ubuntu)
>Status: Triaged => Fix Released
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1447664
>
> Title:
>   14e4:1687 broadcom tg3 network driver disconnects under high load
>
> Status in linux package in Ubuntu:
>   Fix Released
> Status in linux package in Debian:
>   New
>
> Bug description:
>   The tg3 broadcom network driver that binds with chipset 5762 goes
> offline and unable to recover (even with tg3 watchdog timeout) when network
> transmit is under high load.  Call trace:
>   https://launchpadlibrarian.net/204185480/dmesg
>
>   When this happens, only a reboot would be able to fix it.  Sometimes,
>   however, bringing the interface offline and online (via ifconfig)
>   would recover networking.  I've also tested with the latest tg3 driver
>   (dec 2014 version) and networking is still problematic.  I have also
>   disabled TSO, GSO etc... with ethtool and the bug still surfaces.
>   This bug may be related to the integrated Firmware.
>
>   Here is the procedure to replicate the issue because it is hard to
>   replicate it under moderate network load.
>
>   1. Bootup a machine with a broadcom 5762 NIC (ie. HP DeskElite 705)
> using a Ubuntu/Kubunu Live CD 14.04-15.04.
>   2. from another machine: start 5 sessions, repetitively copy (scp with
> public key authentication) a 70 meg file back and forth to the tg3 machine
> in each session. (not sure if this is necessary)
>   3. create a 1GB file on the tg3 machine, with something like dd
> if=/dev/urandom of=/my/test/file bs=1024 count=$((1024*1000))
>   4. from another machine: repetitively scp copy that 1GB file from the
> tg3 machine. This can be done with something like:
>
>   while [ 0 ]; do
>  scp -i /my/scp/private.key u...@ip.of.tg3:/my/test/file /tmp
>   done;
>
>   Networking will mostly goes offline in about 10-30 minutes.
>
>   WORKAROUND: Add udev rule to make the changes permanent in
> /etc/udev/rules.d/80-tg3-fix.rules :
>   ACTION=="add", SUBSYSTEM=="net", ATTRS{vendor}=="0x14e4",
> ATTRS{device}=="0x1687", RUN+="/sbin/ethtool -K %k highdma off"
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 15.04
>   Package: linux-image-3.19.0-15-generic 3.19.0-15.15
>   ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3
>   Uname: Linux 3.19.0-15-generic x86_64
>   ApportVersion: 2.17.2-0ubuntu1
>   Architecture: amd64
>   AudioDevicesInUse:
>USERPID ACCESS COMMAND
>/dev/snd/controlC1:  kubuntu3748 F pulseaudio
>/dev/snd/controlC0:  kubuntu3748 F pulseaudio
>   CasperVersion: 1.360
>   Date: Thu Apr 23 11:16:24 2015
>   IwConfig:
>eth0  no wireless extensions.
>
>lono wireless extensions.
>   LiveMediaBuild: Kubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
>   MachineType: Hewlett-Packard HP EliteDesk 705 G1 MT
>   ProcEnviron:
>LANGUAGE=
>TERM=xterm
>PATH=(custom, no user)
>LANG=en_US.UTF-8
>SHELL=/bin/bash
>   ProcFB: 0 radeondrmfb
>   ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi
> file=/cdrom/preseed/hostname.seed boot=casper maybe-ubiquity quiet splash
> ---
>   PulseList:
>Error: command ['pacmd', 'list'] failed with exit code 1: Home
> directory not accessible: Permission denied
>No PulseAudio daemon running, or not running as session daemon.
>   RelatedPackageVersions:
>linux-restricted-modules-3.19.0-15-generic N/A
>linux-backports-modules-3.19.0-15-generic  N/A
>linux-firmware 1.143
>   RfKill:
>
>   SourcePackage: linux
>   UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   dmi.bios.date: 10/22/2014
>   dmi.bios.vendor: Hewlett-Packard
>   dmi.bios.version: L06 v02.15
>   dmi.board.asset.tag: 2UA5041TG4
>   dmi.board.name: 2215
>   dmi.board.vendor: Hewlett-Packard
>   dmi.chassis.asset.tag: 2UA5041TG4
>   dmi.chassis.type: 6
>   dmi.chassis.vendor: Hewlett-Packard
>   dmi.modalias:
>

[Kernel-packages] [Bug 1832138] Re: Login screen never appears on vmwgfx using bionic kernel 4.15

2019-07-02 Thread Eric Desrochers

The testing phase where the kernel will land in bionic-proposed pocket is due 
around :
08-Jul - 19-Jul Bug verification & Regression testing

This is where I'll need you guys to test the proposed kernel and confirm
it still work as expected for you.

- Eric

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

Title:
  Login screen never appears on vmwgfx using bionic kernel 4.15

Status in linux package in Ubuntu:
  Invalid
Status in linux-hwe package in Ubuntu:
  Invalid
Status in mutter package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Fix Committed
Status in linux-hwe source package in Bionic:
  Fix Released
Status in mutter source package in Bionic:
  Won't Fix
Status in linux source package in Disco:
  Fix Released
Status in linux-hwe source package in Disco:
  Invalid
Status in mutter source package in Disco:
  Invalid
Status in linux source package in Eoan:
  Invalid
Status in linux-hwe source package in Eoan:
  Invalid
Status in mutter source package in Eoan:
  Invalid

Bug description:
  [Impact]

  With most recent version of mutter installed.
  If running kernel is in the 4.15 serie (using the vmwgfx video kernel driver) 
and if the login screen uses wayland, then the login prompt doesn't appears. 
All we see is the purple background with ubuntu in white at the bottom, nothing 
else.

  The vmwgfx driver in kernels prior to 4.17 reported bogus timestamps using 
the wrong clock. This would lead us to wait forever (or at least 49 years)
  before rendering the next frame. There's no decisive way to know this kernel 
bug is going to happen before it does so just detect timestamps which are 
obviously going to cause freezes and ignore them.

  [Test case]

  1) Use Virtualbox or VMware ESxi (if you have the infra)
   1.1) [virtualbox] Make sure in the VM setting that the display uses 'VMSVGA' 
which will force the OS to pick 'vmwgfx' video kernel driver. You can confirm 
with 'lspci -nnvv' command.
  2) Deploy a VM with Ubuntu 18.04.1 (which come w/ 4.15)
  4) apt-get dist-upgrade
  5) Reboot

  with 4.15 it will fails
  with hwe kernel 4.18 it will work as expected. # workaround

  [Potential regression]

  Low, it should fix vmwgfx and stop using the wrong clock.

  A test kernel (pre-sru) has been made available to impact users for
  them to test and conclude it works. It does work as expected, and no
  regression has been found during the pre-sru testing phase.

  As per commit description:

  "
  This should be transparent to to user space, as long as it doesn't
  compare the time against the result of gettimeofday().
  "

  [Other informations]

  upstream fix:
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?h=v5.2-rc5&id=37efe80ce85f

  [Original description]

  I'm running Ubuntu 18.04.2 desktop in a virtual machine under VMWare
  Fusion Pro V11.1.0 on MacOS Mojave 10.14.5, all on a 15inch 2018
  Macbook Pro.

  I've been running this Ubuntu 18.04.2 VM without problem for many months 
without problem.
  Yesterday, I did 'sudo apt update; sudo apt upgrade'.  Upon rebooting, the 
system hangs immediately after displaying the splash screen.  I never see a 
login screen.  And I can't use Ctrl+Alt+F2 to navigate to a console/tty login.

  I can SSH into the system however.

  I've found that I can work around the hang/freeze if I uncomment the 
following line in /etc/gdm3/custom.conf;
  #WaylandEnable=false

  After uncommenting the WaylandEnable=false line and rebooting, then I
  see the login prompt as expected and I can then log in and use the
  system normally again.

  After the 'apt upgrade' my system is running linux kernel 4.15.0-51,
  as shown in this 'uname -a' output;

  Linux ubuntuvm1 4.15.0-51-generic #55-Ubuntu SMP Wed May 15 14:27:21
  UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

  lsb_release -a output;

  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 18.04.2 LTS
  Release:  18.04
  Codename: bionic

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-51.55-generic 4.15.18
  Uname: Linux 4.15.0-51-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CompositorRunning: None
  Date: Sun Jun  9 12:38:37 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: This is the first time
  GraphicsCard:
   VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller])
     Subsystem: VMware SVGA II Adapter [15ad:0405]
  InstallationDate: Installed on 2018-05-06 (399 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: VMware, Inc. VMware Virtual Platform
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKerne

[Kernel-packages] [Bug 1834950] Re: linux-azure: -proposed tracker

** Changed in: kernel-sru-workflow/prepare-package
   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 1834948 (trusty/linux-azure)
  derivatives: bug 1834945 (azure-kernel), bug 1834946 (linux-azure-edge)
  
  -- swm properties --
  kernel-stable-master-bug: 1834954
- phase: Holding before Packaging
- phase-changed: Monday, 01. July 2019 17:10 UTC
+ phase: Ready for Packaging
+ phase-changed: Tuesday, 02. July 2019 14:37 UTC
  reason:
-   prepare-package: Stalled -- waiting for master bug
+   prepare-package: Pending -- version not specified
  variant: debs

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

Title:
  linux-azure:  -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Confirmed
Status in Kernel SRU Workflow prepare-package-meta series:
  New
Status in Kernel SRU Workflow prepare-package-signed series:
  New
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow stakeholder-signoff series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
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 1834948 (trusty/linux-azure)
  derivatives: bug 1834945 (azure-kernel), bug 1834946 (linux-azure-edge)

  -- swm properties --
  kernel-stable-master-bug: 1834954
  phase: Ready for Packaging
  phase-changed: Tuesday, 02. July 2019 14:37 UTC
  reason:
prepare-package: Pending -- version not specified
  variant: debs

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

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

[Kernel-packages] [Bug 1834954] Re: linux: 4.15.0-55.59 -proposed tracker

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

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

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

** Description changed:

  This bug 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 1834950 (xenial/linux-azure), bug 1834953 (xenial/linux-hwe)
  derivatives: bug 1834919 (pc-kernel), bug 1834921 (pc-lowlatency-kernel), bug 
1834923 (linux-raspi2), bug 1834925 (linux-snapdragon), bug 1834926 
(linux-oem), bug 1834930 (linux-aws), bug 1834936 (linux-gcp), bug 1834939 
(linux-gke-4.15), bug 1834940 (linux-kvm), bug 1834941 (linux-ibm-gt), bug 
1834943 (linux-oracle), bug 1834944 (linux-fips)
  
  -- swm properties --
- phase: Packaging
- phase-changed: Tuesday, 02. July 2019 10:31 UTC
+ phase: Holding before Promote to Proposed
+ phase-changed: Tuesday, 02. July 2019 14:31 UTC
  reason:
-   prepare-package: Pending -- package not yet uploaded
-   prepare-package-meta: Pending -- package not yet uploaded
-   prepare-package-signed: Pending -- package not yet uploaded
+   promote-to-proposed: Ongoing -- builds not complete in ppa 
meta:building,signed:building,main:building
  variant: debs

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

Title:
  linux: 4.15.0-55.59 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
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 1834950 (xenial/linux-azure), bug 1834953 (xenial/linux-hwe)
  derivatives: bug 1834919 (pc-kernel), bug 1834921 (pc-lowlatency-kernel), bug 
1834923 (linux-raspi2), bug 1834925 (linux-snapdragon), bug 1834926 
(linux-oem), bug 1834930 (linux-aws), bug 1834936 (linux-gcp), bug 1834939 
(linux-gke-4.15), bug 1834940 (linux-kvm), bug 1834941 (linux-ibm-gt), bug 
1834943 (linux-oracle), bug 1834944 (linux-fips)

  -- swm properties --
  phase: Holding before Promote to Proposed
  phase-changed: Tuesday, 02. July 2019 14:31 UTC
  reason:
promote-to-proposed: Ongoing -- builds not complete in ppa 
meta:building,signed:building,main:building
  variant: debs

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

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

[Kernel-packages] [Bug 1834902] Re: linux: 5.0.0-21.22 -proposed tracker

** 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 1834898 (bionic/linux-hwe-edge), bug 1834900 
(bionic/linux-oem-osp1)
  derivatives: bug 1834884 (linux-raspi2), bug 1834886 (linux-aws), bug 1834888 
(linux-azure), bug 1834891 (linux-gcp), bug 1834892 (linux-kvm), bug 1834894 
(linux-snapdragon)
  
  -- swm properties --
  phase: Holding before Promote to Proposed
  phase-changed: Tuesday, 02. July 2019 14:00 UTC
  reason:
-   promote-to-proposed: Ongoing -- builds not complete in ppa 
main:building,meta:building,signed:building,lrm:building
+   promote-to-proposed: Ongoing -- builds not complete in ppa 
meta:building,signed:building,lrm:building,main:building
  variant: debs

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

Title:
  linux: 5.0.0-21.22 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-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:
  New
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
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 1834898 (bionic/linux-hwe-edge), bug 1834900 
(bionic/linux-oem-osp1)
  derivatives: bug 1834884 (linux-raspi2), bug 1834886 (linux-aws), bug 1834888 
(linux-azure), bug 1834891 (linux-gcp), bug 1834892 (linux-kvm), bug 1834894 
(linux-snapdragon)

  -- swm properties --
  phase: Holding before Promote to Proposed
  phase-changed: Tuesday, 02. July 2019 14:00 UTC
  reason:
promote-to-proposed: Ongoing -- builds not complete in ppa 
meta:building,signed:building,lrm:building,main:building
  variant: debs

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

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

[Kernel-packages] [Bug 1834943] Re: linux-oracle: -proposed tracker

** Changed in: kernel-sru-workflow/prepare-package
   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 1834942 (xenial/linux-oracle)
  
  -- swm properties --
  kernel-stable-master-bug: 1834954
- phase: Holding before Packaging
- phase-changed: Monday, 01. July 2019 17:09 UTC
+ phase: Ready for Packaging
+ phase-changed: Tuesday, 02. July 2019 14:37 UTC
  reason:
-   prepare-package: Stalled -- waiting for master bug
+   prepare-package: Pending -- version not specified
  variant: debs

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

Title:
  linux-oracle:  -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Confirmed
Status in Kernel SRU Workflow prepare-package-meta series:
  New
Status in Kernel SRU Workflow prepare-package-signed series:
  New
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
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 1834942 (xenial/linux-oracle)

  -- swm properties --
  kernel-stable-master-bug: 1834954
  phase: Ready for Packaging
  phase-changed: Tuesday, 02. July 2019 14:37 UTC
  reason:
prepare-package: Pending -- version not specified
  variant: debs

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

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

[Kernel-packages] [Bug 1834944] Re: linux-fips: -proposed tracker

** Changed in: kernel-sru-workflow/prepare-package
   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 --
  kernel-stable-master-bug: 1834954
- phase: Holding before Packaging
- phase-changed: Monday, 01. July 2019 17:10 UTC
+ phase: Ready for Packaging
+ phase-changed: Tuesday, 02. July 2019 14:37 UTC
  reason:
-   prepare-package: Stalled -- waiting for master bug
+   prepare-package: Pending -- version not specified
  variant: debs

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

Title:
  linux-fips:  -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Confirmed
Status in Kernel SRU Workflow prepare-package-meta series:
  New
Status in Kernel SRU Workflow prepare-package-signed series:
  New
Status in Kernel SRU Workflow promote-signing-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
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 --
  kernel-stable-master-bug: 1834954
  phase: Ready for Packaging
  phase-changed: Tuesday, 02. July 2019 14:37 UTC
  reason:
prepare-package: Pending -- version not specified
  variant: debs

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

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

[Kernel-packages] [Bug 1834936] Re: linux-gcp: -proposed tracker

** Changed in: kernel-sru-workflow/prepare-package
   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 1834935 (xenial/linux-gcp)
  derivatives: bug 1834931 (gcp-kernel)
  
  -- swm properties --
  kernel-stable-master-bug: 1834954
- phase: Holding before Packaging
- phase-changed: Monday, 01. July 2019 17:09 UTC
+ phase: Ready for Packaging
+ phase-changed: Tuesday, 02. July 2019 14:36 UTC
  reason:
-   prepare-package: Stalled -- waiting for master bug
+   prepare-package: Pending -- version not specified
  variant: debs

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

Title:
  linux-gcp:  -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Confirmed
Status in Kernel SRU Workflow prepare-package-meta series:
  New
Status in Kernel SRU Workflow prepare-package-signed series:
  New
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
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 1834935 (xenial/linux-gcp)
  derivatives: bug 1834931 (gcp-kernel)

  -- swm properties --
  kernel-stable-master-bug: 1834954
  phase: Ready for Packaging
  phase-changed: Tuesday, 02. July 2019 14:36 UTC
  reason:
prepare-package: Pending -- version not specified
  variant: debs

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

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

[Kernel-packages] [Bug 1834923] Re: linux-raspi2: -proposed tracker

** Changed in: kernel-sru-workflow/prepare-package
   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
  
  derivatives: bug 1834922 (pi-kernel)
  
  -- swm properties --
  kernel-stable-master-bug: 1834954
- phase: Holding before Packaging
- phase-changed: Monday, 01. July 2019 17:07 UTC
+ phase: Ready for Packaging
+ phase-changed: Tuesday, 02. July 2019 14:35 UTC
  reason:
-   prepare-package: Stalled -- waiting for master bug
+   prepare-package: Pending -- version not specified
  variant: debs

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

Title:
  linux-raspi2:  -proposed tracker

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

  derivatives: bug 1834922 (pi-kernel)

  -- swm properties --
  kernel-stable-master-bug: 1834954
  phase: Ready for Packaging
  phase-changed: Tuesday, 02. July 2019 14:35 UTC
  reason:
prepare-package: Pending -- version not specified
  variant: debs

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

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

[Kernel-packages] [Bug 1834666] Re: Intel GPU present but i915 not loaded. Stuck in low resolution.

2019-07-02 Thread juan david linares santana

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

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

Title:
  Intel GPU present but i915 not loaded. Stuck in low resolution.

Status in linux package in Ubuntu:
  Fix Released

Bug description:
  Your system is providing 3D via software rendering rather than
  hardware rendering.  This is a compatibility mode which should display
  3D graphics properly but the performance may be very poor.  If the
  problem you're reporting is related to graphics performance, your real
  question may be why X didn't use hardware acceleration for your
  system.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg (not installed)
  ProcVersionSignature: Ubuntu 4.15.0-50.54-generic 4.15.18
  Uname: Linux 4.15.0-50-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: KDE
  Date: Fri Jun 28 16:28:41 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard:
   Intel Corporation Device [8086:3e92] (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Device [1043:8694]
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-50-generic 
root=UUID=4e297ab3-b0cc-4dcf-ac56-953597c77fa0 ro
  Renderer: Software
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/23/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0602
  dmi.board.asset.tag: Default string
  dmi.board.name: TUF B360-PLUS GAMING
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0602:bd03/23/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnTUFB360-PLUSGAMING:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.95-1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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

[Kernel-packages] [Bug 1834940] Re: linux-kvm: -proposed tracker

** Changed in: kernel-sru-workflow/prepare-package
   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 --
  kernel-stable-master-bug: 1834954
- phase: Holding before Packaging
- phase-changed: Monday, 01. July 2019 17:09 UTC
+ phase: Ready for Packaging
+ phase-changed: Tuesday, 02. July 2019 14:36 UTC
  reason:
-   prepare-package: Stalled -- waiting for master bug
+   prepare-package: Pending -- version not specified
  variant: debs

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

Title:
  linux-kvm:  -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Confirmed
Status in Kernel SRU Workflow prepare-package-meta series:
  New
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
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 --
  kernel-stable-master-bug: 1834954
  phase: Ready for Packaging
  phase-changed: Tuesday, 02. July 2019 14:36 UTC
  reason:
prepare-package: Pending -- version not specified
  variant: debs

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

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

[Kernel-packages] [Bug 1834930] Re: linux-aws: -proposed tracker

** Changed in: kernel-sru-workflow/prepare-package
   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 1834929 (xenial/linux-aws-hwe)
  derivatives: bug 1834927 (aws-kernel)
  
  -- swm properties --
  kernel-stable-master-bug: 1834954
- phase: Holding before Packaging
- phase-changed: Monday, 01. July 2019 17:08 UTC
+ phase: Ready for Packaging
+ phase-changed: Tuesday, 02. July 2019 14:36 UTC
  reason:
-   prepare-package: Stalled -- waiting for master bug
+   prepare-package: Pending -- version not specified
  variant: debs

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

Title:
  linux-aws:  -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Confirmed
Status in Kernel SRU Workflow prepare-package-meta series:
  New
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
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 1834929 (xenial/linux-aws-hwe)
  derivatives: bug 1834927 (aws-kernel)

  -- swm properties --
  kernel-stable-master-bug: 1834954
  phase: Ready for Packaging
  phase-changed: Tuesday, 02. July 2019 14:36 UTC
  reason:
prepare-package: Pending -- version not specified
  variant: debs

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

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

[Kernel-packages] [Bug 1834925] Re: linux-snapdragon: -proposed tracker

** Changed in: kernel-sru-workflow/prepare-package
   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
  
  derivatives: bug 1834924 (dragonboard-kernel)
  
  -- swm properties --
  kernel-stable-master-bug: 1834954
- phase: Holding before Packaging
- phase-changed: Monday, 01. July 2019 17:07 UTC
+ phase: Ready for Packaging
+ phase-changed: Tuesday, 02. July 2019 14:36 UTC
  reason:
-   prepare-package: Stalled -- waiting for master bug
+   prepare-package: Pending -- version not specified
  variant: debs

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

Title:
  linux-snapdragon:  -proposed tracker

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

  derivatives: bug 1834924 (dragonboard-kernel)

  -- swm properties --
  kernel-stable-master-bug: 1834954
  phase: Ready for Packaging
  phase-changed: Tuesday, 02. July 2019 14:36 UTC
  reason:
prepare-package: Pending -- version not specified
  variant: debs

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

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

[Kernel-packages] [Bug 1834926] Re: linux-oem: -proposed tracker

** Changed in: kernel-sru-workflow/prepare-package
   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 --
  kernel-stable-master-bug: 1834954
- phase: Holding before Packaging
- phase-changed: Monday, 01. July 2019 17:08 UTC
+ phase: Ready for Packaging
+ phase-changed: Tuesday, 02. July 2019 14:36 UTC
  reason:
-   prepare-package: Stalled -- waiting for master bug
+   prepare-package: Pending -- version not specified
  variant: debs

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

Title:
  linux-oem:  -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  Confirmed
Status in Kernel SRU Workflow prepare-package-meta series:
  New
Status in Kernel SRU Workflow prepare-package-signed series:
  New
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
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 --
  kernel-stable-master-bug: 1834954
  phase: Ready for Packaging
  phase-changed: Tuesday, 02. July 2019 14:36 UTC
  reason:
prepare-package: Pending -- version not specified
  variant: debs

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

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

[Kernel-packages] [Bug 1834941] Re: linux-ibm-gt: -proposed tracker

** Changed in: kernel-sru-workflow/prepare-package
   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 --
  kernel-stable-master-bug: 1834954
- phase: Holding before Packaging
- phase-changed: Monday, 01. July 2019 17:09 UTC
+ phase: Ready for Packaging
+ phase-changed: Tuesday, 02. July 2019 14:37 UTC
  reason:
-   prepare-package: Stalled -- waiting for master bug
+   prepare-package: Pending -- version not specified
  variant: debs

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

Title:
  linux-ibm-gt:  -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Confirmed
Status in Kernel SRU Workflow prepare-package-meta series:
  New
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
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 --
  kernel-stable-master-bug: 1834954
  phase: Ready for Packaging
  phase-changed: Tuesday, 02. July 2019 14:37 UTC
  reason:
prepare-package: Pending -- version not specified
  variant: debs

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

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

Re: [Kernel-packages] [Bug 1833018] Re: After Installing Updates, system fails to boot on first try

2019-07-02 Thread Aere Greenway

On 6/27/19 10:46 PM, Kai-Heng Feng wrote:
> Ah, please try kernel parameter "nopti".
>
As I indicated in my earlier feedback, I tried that, and it didn't 
affect the problem.

-- 
Sincerely,
Aere

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

Title:
  After Installing Updates, system fails to boot on first try

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I installed Lubuntu 18.04 LTS on an i386 machine (Dell GX-270).  After
  installation, it rebooted with no problems.

  I installed all updates, and on rebooting it failed to boot.  The
  screen had unreadable graphics in the top third of it.

  On rebooting again, it booted okay, saying it recovered the journal.

  Sometimes, it takes 3 tries to get it to boot.  Often, it gets most of
  the way into the boot process, then suddenly goes into the GRUB menu.

  I installed this system because my primary partition on the same
  machine started failing to boot much of the time.  This failure
  started happening after applying updates.  I was thinking something in
  the system files might be corrupted.  But the newly-installed system
  has the same symptoms.

  After applying updates, I expected the system to boot successfully
  every time.

  Instead, it always crashes during the boot, or hangs, on the first try
  to boot.  On the 2nd or 3rd try, it will boot.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-51-generic 4.15.0-51.55
  ProcVersionSignature: Ubuntu 4.15.0-51.55-generic 4.15.18
  Uname: Linux 4.15.0-51-generic i686
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.15.0-51-generic.
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC3:  aere805 F pulseaudio
   /dev/snd/controlC0:  aere805 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'Live'/'SB Live! 5.1 (rev.7, serial:0x80641102) at 0xdf20, irq 18'
 Mixer name : 'SigmaTel STAC9708,11'
 Components : 'AC97a:83847608'
 Controls  : 225
 Simple ctrls  : 45
  Card1.Amixer.info:
   Card hw:1 'MPD218'/'Akai MPD218 at usb-:00:1d.0-2, full speed'
 Mixer name : 'USB Mixer'
 Components : 'USB09e8:0034'
 Controls  : 0
 Simple ctrls  : 0
  Card1.Amixer.values:

  Card2.Amixer.info:
   Card hw:2 'Interface'/'M-Audio USB Uno MIDI Interface at usb-:00:1d.2-2, 
full speed'
 Mixer name : 'USB Mixer'
 Components : 'USB0763:0150'
 Controls  : 0
 Simple ctrls  : 0
  Card2.Amixer.values:

  Card3.Amixer.info:
   Card hw:3 'ICH5'/'Intel ICH5 with AD1981B at irq 17'
 Mixer name : 'Analog Devices AD1981B'
 Components : 'AC97a:41445374'
 Controls  : 27
 Simple ctrls  : 19
  CurrentDesktop: LXDE
  Date: Sun Jun 16 18:09:10 2019
  HibernationDevice: RESUME=UUID=254efefa-b824-4c7b-ae5c-dcf19ed85430
  InstallationDate: Installed on 2019-06-16 (0 days ago)
  InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Release i386 (20180426)
  MachineType: Dell Computer Corporation OptiPlex GX270
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-51-generic 
root=UUID=01278e7e-143f-479d-8842-aa15ad6ff5a8 ro quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-51-generic N/A
   linux-backports-modules-4.15.0-51-generic  N/A
   linux-firmware 1.173.6
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/26/2006
  dmi.bios.vendor: Dell Computer Corporation
  dmi.bios.version: A07
  dmi.board.name: 0U1325
  dmi.board.vendor: Dell Computer Corp.
  dmi.chassis.type: 6
  dmi.chassis.vendor: Dell Computer Corporation
  dmi.modalias: 
dmi:bvnDellComputerCorporation:bvrA07:bd06/26/2006:svnDellComputerCorporation:pnOptiPlexGX270:pvr:rvnDellComputerCorp.:rn0U1325:rvr:cvnDellComputerCorporation:ct6:cvr:
  dmi.product.name: OptiPlex GX270
  dmi.sys.vendor: Dell Computer Corporation

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

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

[Kernel-packages] [Bug 1834886] Re: linux-aws: 5.0.0-1011.12 -proposed tracker

** Summary changed:

- linux-aws:  -proposed tracker
+ linux-aws: 5.0.0-1011.12 -proposed tracker

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

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

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

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

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

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

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  In Progress
Status in Kernel SRU Workflow prepare-package-meta series:
  In Progress
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
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 --
  kernel-stable-master-bug: 1834902
  phase: Ready for Packaging
  phase-changed: Tuesday, 02. July 2019 14:03 UTC
  reason:
prepare-package: Pending -- version not specified
  variant: debs

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

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

[Kernel-packages] [Bug 1828596] Re: kdump fails when crash is triggered after DLPAR cpu add operation

2019-07-02 Thread Thadeu Lima de Souza Cascardo

** Patch added: "backport for disco"
   
https://bugs.launchpad.net/ubuntu/+source/kexec-tools/+bug/1828596/+attachment/5274690/+files/makedumpfile_1.6.5-1ubuntu2~19.04.1.debdiff

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

Title:
  kdump fails when crash is triggered after DLPAR cpu add operation

Status in The Ubuntu-power-systems project:
  Confirmed
Status in kexec-tools package in Ubuntu:
  Invalid
Status in makedumpfile package in Ubuntu:
  Fix Released
Status in kexec-tools source package in Xenial:
  New
Status in makedumpfile source package in Xenial:
  New
Status in kexec-tools source package in Bionic:
  New
Status in makedumpfile source package in Bionic:
  New
Status in kexec-tools source package in Cosmic:
  New
Status in makedumpfile source package in Cosmic:
  New
Status in kexec-tools source package in Disco:
  New
Status in makedumpfile source package in Disco:
  New
Status in kexec-tools source package in Eoan:
  Invalid
Status in makedumpfile source package in Eoan:
  Fix Released

Bug description:
  == Comment: #0 - Hari Krishna Bathini - 2019-05-10 05:55:40 ==
  ---Problem Description---
  kdump fails when crash is triggered after CPU add operation.
   
  Machine Type = na 
   
  ---System Hang---
   Crashed in early boot process of kdump kernel after crash

  Had to issue system reset from HMC to reclaim
   
  ---Steps to Reproduce---
   1. Configure kdump.
  2. Add cpu from HMC.
  3. Trigger crash.
  4. Machine hangs after crash as below:

  ---
  [169250.213166] IPI complete
  [169250.234331] kexec: Starting switchover sequence.
  I'm in purgatory
   --- STRUCK HERE ---
   
  ---uname output---
  na
   
  ---Debugger---
  A debugger is not configured

  == Comment: #1 - Hari Krishna Bathini  - 2019-05-10 05:56:46 ==
  The problem is, kexec udev rule to restart kdump-tools service - when a core 
is added,
  is not being triggered. The old DT created by kexec (before the core is added)
  is being used by KDump Kernel. So, when system crashes on a thread from
  the added core(s), KDump kernel is failing to get the 'boot_cpuid' and
  eventually failing to boot..

  == Comment: #2 - Hari Krishna Bathini - 2019-05-10 06:02:27 ==
  The udev rule when CPU is added is not triggered because ppc64 does not
  eject add/remove event when a CPU is hot added/removed. It only ejects
  online/offline event to user space when CPU is hot added/removed.

  So, the below udev rules are never triggered when needed:

  SUBSYSTEM=="cpu", ACTION=="add", PROGRAM="/bin/systemctl try-restart 
kdump-tools.service"
  SUBSYSTEM=="cpu", ACTION=="remove", PROGRAM="/bin/systemctl try-restart 
kdump-tools.service"

  Also, with how CPU hot add & remove are handled in ppc64, a udev trigger
  to reload kdump after CPU is hot removed is NOT necessary. So, fix the CPU
  hot add case by updating the udev rule and drop the udev rule meant for CPU
  hot remove in the kdump udev rules file:

  
  SUBSYSTEM=="cpu", ACTION=="online", PROGRAM="/bin/systemctl try-restart 
kdump-tools.service"

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

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

[Kernel-packages] [Bug 1828596] Re: kdump fails when crash is triggered after DLPAR cpu add operation

2019-07-02 Thread Thadeu Lima de Souza Cascardo

** Patch added: "backport for bionic"
   
https://bugs.launchpad.net/ubuntu/+source/kexec-tools/+bug/1828596/+attachment/5274692/+files/makedumpfile_1.6.5-1ubuntu2~18.04.1.debdiff

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

Title:
  kdump fails when crash is triggered after DLPAR cpu add operation

Status in The Ubuntu-power-systems project:
  Confirmed
Status in kexec-tools package in Ubuntu:
  Invalid
Status in makedumpfile package in Ubuntu:
  Fix Released
Status in kexec-tools source package in Xenial:
  New
Status in makedumpfile source package in Xenial:
  New
Status in kexec-tools source package in Bionic:
  New
Status in makedumpfile source package in Bionic:
  New
Status in kexec-tools source package in Cosmic:
  New
Status in makedumpfile source package in Cosmic:
  New
Status in kexec-tools source package in Disco:
  New
Status in makedumpfile source package in Disco:
  New
Status in kexec-tools source package in Eoan:
  Invalid
Status in makedumpfile source package in Eoan:
  Fix Released

Bug description:
  == Comment: #0 - Hari Krishna Bathini - 2019-05-10 05:55:40 ==
  ---Problem Description---
  kdump fails when crash is triggered after CPU add operation.
   
  Machine Type = na 
   
  ---System Hang---
   Crashed in early boot process of kdump kernel after crash

  Had to issue system reset from HMC to reclaim
   
  ---Steps to Reproduce---
   1. Configure kdump.
  2. Add cpu from HMC.
  3. Trigger crash.
  4. Machine hangs after crash as below:

  ---
  [169250.213166] IPI complete
  [169250.234331] kexec: Starting switchover sequence.
  I'm in purgatory
   --- STRUCK HERE ---
   
  ---uname output---
  na
   
  ---Debugger---
  A debugger is not configured

  == Comment: #1 - Hari Krishna Bathini  - 2019-05-10 05:56:46 ==
  The problem is, kexec udev rule to restart kdump-tools service - when a core 
is added,
  is not being triggered. The old DT created by kexec (before the core is added)
  is being used by KDump Kernel. So, when system crashes on a thread from
  the added core(s), KDump kernel is failing to get the 'boot_cpuid' and
  eventually failing to boot..

  == Comment: #2 - Hari Krishna Bathini - 2019-05-10 06:02:27 ==
  The udev rule when CPU is added is not triggered because ppc64 does not
  eject add/remove event when a CPU is hot added/removed. It only ejects
  online/offline event to user space when CPU is hot added/removed.

  So, the below udev rules are never triggered when needed:

  SUBSYSTEM=="cpu", ACTION=="add", PROGRAM="/bin/systemctl try-restart 
kdump-tools.service"
  SUBSYSTEM=="cpu", ACTION=="remove", PROGRAM="/bin/systemctl try-restart 
kdump-tools.service"

  Also, with how CPU hot add & remove are handled in ppc64, a udev trigger
  to reload kdump after CPU is hot removed is NOT necessary. So, fix the CPU
  hot add case by updating the udev rule and drop the udev rule meant for CPU
  hot remove in the kdump udev rules file:

  
  SUBSYSTEM=="cpu", ACTION=="online", PROGRAM="/bin/systemctl try-restart 
kdump-tools.service"

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

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

[Kernel-packages] [Bug 1828596] Re: kdump fails when crash is triggered after DLPAR cpu add operation

2019-07-02 Thread Thadeu Lima de Souza Cascardo

** Patch added: "backport for cosmic"
   
https://bugs.launchpad.net/ubuntu/+source/kexec-tools/+bug/1828596/+attachment/5274691/+files/makedumpfile_1.6.5-1ubuntu2~18.10.1.debdiff

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

Title:
  kdump fails when crash is triggered after DLPAR cpu add operation

Status in The Ubuntu-power-systems project:
  Confirmed
Status in kexec-tools package in Ubuntu:
  Invalid
Status in makedumpfile package in Ubuntu:
  Fix Released
Status in kexec-tools source package in Xenial:
  New
Status in makedumpfile source package in Xenial:
  New
Status in kexec-tools source package in Bionic:
  New
Status in makedumpfile source package in Bionic:
  New
Status in kexec-tools source package in Cosmic:
  New
Status in makedumpfile source package in Cosmic:
  New
Status in kexec-tools source package in Disco:
  New
Status in makedumpfile source package in Disco:
  New
Status in kexec-tools source package in Eoan:
  Invalid
Status in makedumpfile source package in Eoan:
  Fix Released

Bug description:
  == Comment: #0 - Hari Krishna Bathini - 2019-05-10 05:55:40 ==
  ---Problem Description---
  kdump fails when crash is triggered after CPU add operation.
   
  Machine Type = na 
   
  ---System Hang---
   Crashed in early boot process of kdump kernel after crash

  Had to issue system reset from HMC to reclaim
   
  ---Steps to Reproduce---
   1. Configure kdump.
  2. Add cpu from HMC.
  3. Trigger crash.
  4. Machine hangs after crash as below:

  ---
  [169250.213166] IPI complete
  [169250.234331] kexec: Starting switchover sequence.
  I'm in purgatory
   --- STRUCK HERE ---
   
  ---uname output---
  na
   
  ---Debugger---
  A debugger is not configured

  == Comment: #1 - Hari Krishna Bathini  - 2019-05-10 05:56:46 ==
  The problem is, kexec udev rule to restart kdump-tools service - when a core 
is added,
  is not being triggered. The old DT created by kexec (before the core is added)
  is being used by KDump Kernel. So, when system crashes on a thread from
  the added core(s), KDump kernel is failing to get the 'boot_cpuid' and
  eventually failing to boot..

  == Comment: #2 - Hari Krishna Bathini - 2019-05-10 06:02:27 ==
  The udev rule when CPU is added is not triggered because ppc64 does not
  eject add/remove event when a CPU is hot added/removed. It only ejects
  online/offline event to user space when CPU is hot added/removed.

  So, the below udev rules are never triggered when needed:

  SUBSYSTEM=="cpu", ACTION=="add", PROGRAM="/bin/systemctl try-restart 
kdump-tools.service"
  SUBSYSTEM=="cpu", ACTION=="remove", PROGRAM="/bin/systemctl try-restart 
kdump-tools.service"

  Also, with how CPU hot add & remove are handled in ppc64, a udev trigger
  to reload kdump after CPU is hot removed is NOT necessary. So, fix the CPU
  hot add case by updating the udev rule and drop the udev rule meant for CPU
  hot remove in the kdump udev rules file:

  
  SUBSYSTEM=="cpu", ACTION=="online", PROGRAM="/bin/systemctl try-restart 
kdump-tools.service"

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

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

[Kernel-packages] [Bug 1834954] Re: linux: 4.15.0-55.59 -proposed tracker

** 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 1834950 (xenial/linux-azure), bug 1834953 (xenial/linux-hwe)
  derivatives: bug 1834919 (pc-kernel), bug 1834921 (pc-lowlatency-kernel), bug 
1834923 (linux-raspi2), bug 1834925 (linux-snapdragon), bug 1834926 
(linux-oem), bug 1834930 (linux-aws), bug 1834936 (linux-gcp), bug 1834939 
(linux-gke-4.15), bug 1834940 (linux-kvm), bug 1834941 (linux-ibm-gt), bug 
1834943 (linux-oracle), bug 1834944 (linux-fips)
  
  -- swm properties --
  phase: Holding before Promote to Proposed
  phase-changed: Tuesday, 02. July 2019 14:31 UTC
  reason:
-   promote-to-proposed: Ongoing -- builds not complete in ppa 
meta:building,signed:building,main:building
+   promote-to-proposed: Ongoing -- builds not complete in ppa 
main:building,meta:building,signed:building
  variant: debs

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

Title:
  linux: 4.15.0-55.59 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
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 1834950 (xenial/linux-azure), bug 1834953 (xenial/linux-hwe)
  derivatives: bug 1834919 (pc-kernel), bug 1834921 (pc-lowlatency-kernel), bug 
1834923 (linux-raspi2), bug 1834925 (linux-snapdragon), bug 1834926 
(linux-oem), bug 1834930 (linux-aws), bug 1834936 (linux-gcp), bug 1834939 
(linux-gke-4.15), bug 1834940 (linux-kvm), bug 1834941 (linux-ibm-gt), bug 
1834943 (linux-oracle), bug 1834944 (linux-fips)

  -- swm properties --
  phase: Holding before Promote to Proposed
  phase-changed: Tuesday, 02. July 2019 14:31 UTC
  reason:
promote-to-proposed: Ongoing -- builds not complete in ppa 
main:building,meta:building,signed:building
  variant: debs

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

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

[Kernel-packages] [Bug 1834902] Re: linux: 5.0.0-21.22 -proposed tracker

** 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 1834898 (bionic/linux-hwe-edge), bug 1834900 
(bionic/linux-oem-osp1)
  derivatives: bug 1834884 (linux-raspi2), bug 1834886 (linux-aws), bug 1834888 
(linux-azure), bug 1834891 (linux-gcp), bug 1834892 (linux-kvm), bug 1834894 
(linux-snapdragon)
  
  -- swm properties --
  phase: Holding before Promote to Proposed
  phase-changed: Tuesday, 02. July 2019 14:00 UTC
  reason:
-   promote-to-proposed: Ongoing -- builds not complete in ppa 
meta:building,signed:building,lrm:building,main:building
+   promote-to-proposed: Ongoing -- builds not complete in ppa 
main:building,meta:building,signed:building,lrm:building
  variant: debs

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

Title:
  linux: 5.0.0-21.22 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-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:
  New
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
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 1834898 (bionic/linux-hwe-edge), bug 1834900 
(bionic/linux-oem-osp1)
  derivatives: bug 1834884 (linux-raspi2), bug 1834886 (linux-aws), bug 1834888 
(linux-azure), bug 1834891 (linux-gcp), bug 1834892 (linux-kvm), bug 1834894 
(linux-snapdragon)

  -- swm properties --
  phase: Holding before Promote to Proposed
  phase-changed: Tuesday, 02. July 2019 14:00 UTC
  reason:
promote-to-proposed: Ongoing -- builds not complete in ppa 
main:building,meta:building,signed:building,lrm:building
  variant: debs

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

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

[Kernel-packages] [Bug 1834886] Re: linux-aws: 5.0.0-1011.12 -proposed tracker

** 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 --
  kernel-stable-master-bug: 1834902
- phase: Ready for Packaging
- phase-changed: Tuesday, 02. July 2019 14:03 UTC
+ phase: Packaging
+ phase-changed: Tuesday, 02. July 2019 15:02 UTC
  reason:
-   prepare-package: Pending -- version not specified
+   prepare-package: Pending -- package not yet uploaded
+   prepare-package-meta: Pending -- package not yet uploaded
  variant: debs

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

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

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  In Progress
Status in Kernel SRU Workflow prepare-package-meta series:
  In Progress
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
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 --
  kernel-stable-master-bug: 1834902
  phase: Packaging
  phase-changed: Tuesday, 02. July 2019 15:02 UTC
  reason:
prepare-package: Pending -- package not yet uploaded
prepare-package-meta: Pending -- package not yet uploaded
  variant: debs

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

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

[Kernel-packages] [Bug 1833922] Re: linux-aws: 5.0.0-1010.11 -proposed tracker

This bug was fixed in the package linux-aws - 5.0.0-1010.11

---
linux-aws (5.0.0-1010.11) disco; urgency=medium

  * linux-aws: 5.0.0-1010.11 -proposed tracker (LP: #1833922)

  [ Ubuntu: 5.0.0-20.21 ]

  * linux: 5.0.0-20.21 -proposed tracker (LP: #1833934)
  * CVE-2019-11479
- SAUCE: tcp: add tcp_min_snd_mss sysctl
- SAUCE: tcp: enforce tcp_min_snd_mss in tcp_mtu_probing()
  * Remote denial of service (resource exhaustion) caused by TCP SACK scoreboard
manipulation (LP: #1831638) // CVE-2019-11478
- tcp: refine memory limit test in tcp_fragment()

  [ Ubuntu: 5.0.0-19.20 ]

  * CVE-2019-12817
- SAUCE: powerpc/mm/64s/hash: Reallocate context ids on fork

 -- Kleber Sacilotto de Souza   Tue, 25 Jun
2019 14:31:54 +0200

** Changed in: linux-aws (Ubuntu)
   Status: Invalid => Fix Released

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

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

Status in Kernel SRU Workflow:
  Fix Released
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:
  Fix Released
Status in Kernel SRU Workflow promote-to-updates series:
  Fix Released
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:
  Invalid
Status in linux-aws package in Ubuntu:
  Fix Released
Status in linux-aws source package in Disco:
  Fix Released

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: 1833934
  phase: Complete
  phase-changed: Friday, 28. June 2019 17:05 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  variant: debs

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

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

[Kernel-packages] [Bug 1833929] Re: linux-snapdragon: 5.0.0-1016.17 -proposed tracker

This bug was fixed in the package linux-snapdragon - 5.0.0-1016.17

---
linux-snapdragon (5.0.0-1016.17) disco; urgency=medium

  * linux-snapdragon: 5.0.0-1016.17 -proposed tracker (LP: #1833929)

  [ Ubuntu: 5.0.0-20.21 ]

  * linux: 5.0.0-20.21 -proposed tracker (LP: #1833934)
  * CVE-2019-11479
- SAUCE: tcp: add tcp_min_snd_mss sysctl
- SAUCE: tcp: enforce tcp_min_snd_mss in tcp_mtu_probing()
  * Remote denial of service (resource exhaustion) caused by TCP SACK scoreboard
manipulation (LP: #1831638) // CVE-2019-11478
- tcp: refine memory limit test in tcp_fragment()

  [ Ubuntu: 5.0.0-19.20 ]

  * CVE-2019-12817
- SAUCE: powerpc/mm/64s/hash: Reallocate context ids on fork

 -- Stefan Bader   Tue, 25 Jun 2019 14:59:37
+0200

** Changed in: linux-snapdragon (Ubuntu)
   Status: Invalid => Fix Released

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

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

Status in Kernel SRU Workflow:
  Fix Released
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:
  Fix Released
Status in Kernel SRU Workflow promote-to-updates series:
  Fix Released
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:
  Invalid
Status in linux-snapdragon package in Ubuntu:
  Fix Released
Status in linux-snapdragon source package in Disco:
  Fix Released

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: 1833934
  phase: Complete
  phase-changed: Friday, 28. June 2019 17:06 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  variant: debs

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

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

[Kernel-packages] [Bug 1834916] Re: linux-aws: -proposed tracker

** Changed in: kernel-sru-workflow/prepare-package
   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 --
  kernel-stable-master-bug: 1834918
- phase: Holding before Packaging
- phase-changed: Monday, 01. July 2019 16:37 UTC
+ phase: Ready for Packaging
+ phase-changed: Tuesday, 02. July 2019 15:35 UTC
  reason:
-   prepare-package: Stalled -- waiting for master bug
+   prepare-package: Pending -- version not specified
  variant: debs

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

Title:
  linux-aws:  -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:
  Confirmed
Status in Kernel SRU Workflow prepare-package-meta series:
  New
Status in Kernel SRU Workflow promote-signing-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-aws package in Ubuntu:
  Invalid
Status in linux-aws 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 --
  kernel-stable-master-bug: 1834918
  phase: Ready for Packaging
  phase-changed: Tuesday, 02. July 2019 15:35 UTC
  reason:
prepare-package: Pending -- version not specified
  variant: debs

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

-- 
Mailing list: https://launchpad.net/~kernel-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-07-02 Thread Fred Schnittke

Hello, we are also running in to this same issue. I see that the bug
appears to be fixed as of June 24th, but how would an end user like
myself be able to get a hold of this? It appears the Ubuntu Server
minimal iso is still an old version that does not contain the fix?

regards

-- 
You 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:
  Fix Released
Status in hw-detect source package in Bionic:
  Fix Released
Status in linux source package in Bionic:
  Fix Released
Status in partman-iscsi source package in Bionic:
  Fix Released
Status in debian-installer source package in Cosmic:
  Fix Released
Status in hw-detect source package in Cosmic:
  Fix Released
Status in linux source package in Cosmic:
  Fix Released
Status in partman-iscsi source package in Cosmic:
  Fix Released
Status in debian-installer source package in Disco:
  Fix Released
Status in hw-detect source package in Disco:
  Fix Released
Status in linux source package in Disco:
  Fix Released
Status in partman-iscsi source package in Disco:
  Fix Released
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 1834918] Re: linux: 4.4.0-155.182 -proposed tracker

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

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

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

** Description changed:

  This bug 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 1834916 (trusty/linux-aws), bug 1834917 
(trusty/linux-lts-xenial)
  derivatives: bug 1834906 (pc-kernel), bug 1834908 (linux-aws), bug 1834909 
(linux-kvm), bug 1834911 (linux-raspi2), bug 1834913 (linux-snapdragon), bug 
1834915 (linux-fips)
  
  -- swm properties --
- phase: Packaging
- phase-changed: Tuesday, 02. July 2019 12:00 UTC
+ phase: Holding before Promote to Proposed
+ phase-changed: Tuesday, 02. July 2019 15:31 UTC
  reason:
-   prepare-package: Pending -- package not yet uploaded
-   prepare-package-meta: Pending -- package not yet uploaded
-   prepare-package-signed: Pending -- package not yet uploaded
+   promote-to-proposed: Ongoing -- builds not complete in ppa 
signed:building,main:building,meta:building
  variant: debs

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

Title:
  linux: 4.4.0-155.182 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
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 1834916 (trusty/linux-aws), bug 1834917 
(trusty/linux-lts-xenial)
  derivatives: bug 1834906 (pc-kernel), bug 1834908 (linux-aws), bug 1834909 
(linux-kvm), bug 1834911 (linux-raspi2), bug 1834913 (linux-snapdragon), bug 
1834915 (linux-fips)

  -- swm properties --
  phase: Holding before Promote to Proposed
  phase-changed: Tuesday, 02. July 2019 15:31 UTC
  reason:
promote-to-proposed: Ongoing -- builds not complete in ppa 
signed:building,main:building,meta:building
  variant: debs

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

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

[Kernel-packages] [Bug 1834902] Re: linux: 5.0.0-21.22 -proposed tracker

** 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 1834898 (bionic/linux-hwe-edge), bug 1834900 
(bionic/linux-oem-osp1)
  derivatives: bug 1834884 (linux-raspi2), bug 1834886 (linux-aws), bug 1834888 
(linux-azure), bug 1834891 (linux-gcp), bug 1834892 (linux-kvm), bug 1834894 
(linux-snapdragon)
  
  -- swm properties --
  phase: Holding before Promote to Proposed
  phase-changed: Tuesday, 02. July 2019 14:00 UTC
  reason:
-   promote-to-proposed: Ongoing -- builds not complete in ppa 
main:building,meta:building,signed:building,lrm:building
+   promote-to-proposed: Ongoing -- builds not complete in ppa 
signed:building,main:building,lrm:building,meta:building
  variant: debs

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

Title:
  linux: 5.0.0-21.22 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-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:
  New
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
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 1834898 (bionic/linux-hwe-edge), bug 1834900 
(bionic/linux-oem-osp1)
  derivatives: bug 1834884 (linux-raspi2), bug 1834886 (linux-aws), bug 1834888 
(linux-azure), bug 1834891 (linux-gcp), bug 1834892 (linux-kvm), bug 1834894 
(linux-snapdragon)

  -- swm properties --
  phase: Holding before Promote to Proposed
  phase-changed: Tuesday, 02. July 2019 14:00 UTC
  reason:
promote-to-proposed: Ongoing -- builds not complete in ppa 
signed:building,main:building,lrm:building,meta:building
  variant: debs

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

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

[Kernel-packages] [Bug 1834911] Re: linux-raspi2: -proposed tracker