[Kernel-packages] [Bug 1788098] Re: Avoid migration issues with aligned 2MB THB

[Launchpad Bug Tracker]

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

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

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

Title:
  Avoid migration issues with aligned 2MB THB

Status in The Ubuntu-power-systems project:
  Incomplete
Status in linux package in Ubuntu:
  Expired
Status in qemu package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Expired
Status in linux source package in Cosmic:
  Invalid

Bug description:
  FYI: This blocks bug 1781526 - once this one here is resolved we can
  go on with SRU considerations for 1781526

  --- Comment From jhop...@us.ibm.com 2018-08-20 17:12 EDT---

  Hi, in some environments it was observed that this qemu patch to
  enable THP made it more likely to hit guest migration issues, however
  the following kernel patch resolves those migration issues:

  
https://git.kernel.org/pub/scm/linux/kernel/git/paulus/powerpc.git/commit/?h=kvm-ppc-next=c066fafc595eef5ae3c83ae3a8305956b8c3ef15
  KVM: PPC: Book3S HV: Use correct pagesize in kvm_unmap_radix()

  Once merged upstream, it would be good to include that change as well
  to avoid potential migration problems. Should I open a new bug for
  that or is it better to track here?

  Note Paelzer: I have not seen related migration issues myself, but it
  seems reasonable and confirmed by IBM.

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

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

[Kernel-packages] [Bug 1788098] Re: Avoid migration issues with aligned 2MB THB

[Launchpad Bug Tracker]

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

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

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

Title:
  Avoid migration issues with aligned 2MB THB

Status in The Ubuntu-power-systems project:
  Incomplete
Status in linux package in Ubuntu:
  Expired
Status in qemu package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Expired
Status in linux source package in Cosmic:
  Invalid

Bug description:
  FYI: This blocks bug 1781526 - once this one here is resolved we can
  go on with SRU considerations for 1781526

  --- Comment From jhop...@us.ibm.com 2018-08-20 17:12 EDT---

  Hi, in some environments it was observed that this qemu patch to
  enable THP made it more likely to hit guest migration issues, however
  the following kernel patch resolves those migration issues:

  
https://git.kernel.org/pub/scm/linux/kernel/git/paulus/powerpc.git/commit/?h=kvm-ppc-next=c066fafc595eef5ae3c83ae3a8305956b8c3ef15
  KVM: PPC: Book3S HV: Use correct pagesize in kvm_unmap_radix()

  Once merged upstream, it would be good to include that change as well
  to avoid potential migration problems. Should I open a new bug for
  that or is it better to track here?

  Note Paelzer: I have not seen related migration issues myself, but it
  seems reasonable and confirmed by IBM.

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

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

[Kernel-packages] [Bug 1816702] Re: Ubuntu 19.04 - tablet pc won't wake with pen or device buttons (unless keyboard attached)

[Chris Guiver]

Marking invalid - i cannot re-create on j3400 using released 19.04, nor
daily 19.10

I have now booted the released 19.04 with both keyboard-stand connected,
plus it as a 'tablet' only, and with power-blanking set to 1 minute (to
allow more testing in less time), I can use the pen to wake or unlock
device.  Whatever caused the initial problem on 19.04 daily has gone.

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

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

Title:
  Ubuntu 19.04 - tablet pc won't wake with pen or device buttons (unless
  keyboard attached)

Status in linux package in Ubuntu:
  Invalid

Bug description:
  Ubuntu 19.04 QA-TEST on tablet.pc (wacom pen)
  motion computing j3400 (c2d-u9400, 4gb, intel mobile 4 series)

  The test went really well, but I noticed I couldn't wake it if left
  alone and screen dims & thus locks using tablet buttons or pen (& its
  button).

  This is [most] likely device specific & is very MINOR.

  It woke perfectly when keyboard/stand was attached, but not with the
  device's arrow keys, button, or any on screen mouse movement (using
  pen, including pen button).  If the device dimmed screen with onscreen
  keyboard no longer visible, and I couldn't wake it.

  The result was you had to connect keyboard/stand in order to wake
  device...  The track-pad on the keyboard/stand woke machine too, but
  that required keyboard to be attached.

  
  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gnome-power-manager 3.30.0-2
  ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
  Uname: Linux 4.18.0-11-generic x86_64
  ApportVersion: 2.20.10-0ubuntu19
  Architecture: amd64
  CasperVersion: 1.402
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Feb 20 07:00:51 2019
  LiveMediaBuild: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190203)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-power-manager
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1828766] Re: network-manager ADT tests fail to run properly on bionic

[Launchpad Bug Tracker]

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

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

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

Title:
  network-manager ADT tests fail to run properly on bionic

Status in linux package in Ubuntu:
  Expired

Bug description:
  The network-manager ADT tests are now failing to run on bionic kernel
  4.15.0-49.53

  amd64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/amd64/n/network-manager/20190506_063857_d8103@/log.gz
  arm64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/arm64/n/network-manager/20190506_065519_d8103@/log.gz
  armhf: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/armhf/n/network-manager/20190506_063551_d8103@/log.gz
  i386: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/i386/n/network-manager/20190506_063938_d8103@/log.gz
  ppc64el: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/ppc64el/n/network-manager/20190506_064426_d8103@/log.gz
  s390x: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/s390x/n/network-manager/20190506_063740_d8103@/log.gz

  This is clearly a test problem but I haven't been able to figure out
  what's wrong.

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

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

[Kernel-packages] [Bug 1829737] Re: Bluetooth: hci0: request failed to create LE connection: status 0x0c (Intel 9462/9560)

[Warren Baird]

I believe I'm impacted by this same issue.  I have an ASUS ZenBook 14 - UX433FA 
- which based on this - 
https://www.notebookcheck.net/ASUS-ZenBook-14-UX433FA-Core-i5-8265U-SSD-FHD-Laptop-Review.403541.0.html
 - I believe has an Intel 9560 chipset (I am not sure how to independently 
verify this).
With kernels older than 4.20 I can successfully pair my bluetooth mouse 
(Logitech MX Master) - but with newer kernels I get "Bluetooth: hci0: request 
failed to create LE connection: status 0x0c" messages.

I'm running Linux Mint 19.1

I tried installing linux-firmware 1.173.8, and it didn't seem to help -
I also downloaded 1.173.9 proposed from here:
https://launchpad.net/ubuntu/bionic/amd64/linux-firmware/1.173.9 and
that also didn't seem to help.

Both after a cold reboot and a warm reboot I see 
[   14.724438] Bluetooth: hci0: Firmware revision 0.1 build 201 week 49 2017

in my dmesg output.

If it's better to open a new bug to track this, let me know...

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

Title:
  Bluetooth: hci0: request failed to create LE connection: status 0x0c
  (Intel 9462/9560)

Status in HWE Next:
  Fix Released
Status in linux-firmware package in Ubuntu:
  Fix Released
Status in linux-firmware source package in Bionic:
  Fix Released

Bug description:
  SRU Justification

  [Impact]
  The firmware blob for Intel Bluetooth 9560/9462 is versioned 20.30.0.1 is not 
compatible with kernel version >= 4.19 and will cause failure to pair BT 4.0 
devices.

  [Fix]
  29a536a02cad linux-firmware: Update firmware file for Intel Bluetooth 9560

  Above upstream change contains latest firmware file for Intel
  Bluetooth 9560 that fixes HID pairing in recent kernel versions.

  [Test Case]
  Copy ibt-17-16-1.sfi blob to /lib/firmware/intel and do a cold boot to reload 
firmware. One should find following message in dmesg:

Bluetooth: hci0: Bootloader revision 0.1 build 42 week 52 2015

  This indicates firmware reload has been activated. For further warm
  boots, kernel would dump updated revision:

Bluetooth: hci0: Firmware revision 0.1 build 184 week 15 2019

  And perform BT 4.0 device pairing for functional tests.

  Tested blob against following kernel versions:

  * 5.0.0-1004-oem-osp1
  * 5.0.0-15-generic
  * 4.18.0-20-generic
  * 4.15.0-1038-oem
  * 4.15.0-50-generic

  [Regression Risk]
  Low. This affects only Intel JeffersonPeak Bluetooth chip series, namely 
9461/9462/9560, which are the hardware variants to be fixed.

  ---

  For kernel version >= 4.19, it fails to pair with BT4.0 HID devices
  and leave error messages in syslog:

    Bluetooth: hci0: request failed to create LE connection: status 0x0c

  Which can be detailed by btmon:

    < HCI Command: LE Extended Create Connection (0x08|0x0043) plen 26 #800 
[hci0] 30.895622
  Filter policy: White list is not used (0x00)
  Own address type: Public (0x00)
  Peer address type: Random (0x01)
  Peer address: DB:DD:51:2D:1C:CC (Static)
  Initiating PHYs: 0x01
  Entry 0: LE 1M
    Scan interval: 60.000 msec (0x0060)
    Scan window: 60.000 msec (0x0060)
    Min connection interval: 30.00 msec (0x0018)
    Max connection interval: 50.00 msec (0x0028)
    Connection latency: 0 (0x)
    Supervision timeout: 420 msec (0x002a)
    Min connection length: 0.000 msec (0x)
    Max connection length: 0.000 msec (0x)
    > HCI Event: Command Status (0x0f) plen 4 #801 [hci0] 30.896453
    LE Extended Create Connection (0x08|0x0043) ncmd 1
  Status: Command Disallowed (0x0c)

  Indicating this is actually a firmware problem.

  Verified this has been fixed at least in upstream linux-firmware
  commit 29a536a02cadb75b84c6c0b5d7af22d34d278563, firmware release
  version 21.10.0.6. With that firmware blob placed under
  /lib/firmware/intel and a cold boot, dmesg gives updated revision and
  device pairing works as expected:

    Firmware revision 0.1 build 184 week 15 2019

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

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

[Kernel-packages] [Bug 1752194] Re: Intel GPU tools crash with "Couldn't map MMIO region"

[James]

I've hit this too on 18.04.
It may be related to kernel lockdown in UEFI secure boot.
https://bugs.freedesktop.org/show_bug.cgi?id=93199


** Bug watch added: freedesktop.org Bugzilla #93199
   https://bugs.freedesktop.org/show_bug.cgi?id=93199

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

Title:
  Intel GPU tools crash with "Couldn't map MMIO region"

Status in intel-gpu-tools package in Ubuntu:
  Confirmed

Bug description:
  Trying to run anything in intel-gpu-tools (tested intel_gpu_top, 
intel_gpu_time and intel_backlight) on my laptop (which has hybrid graphics, 
GTX 760m (proprietary nvidia driver not installed right now) + Intel 4th gen 
iGPU) as root yields the following output:
  (intel_gpu_top:23021) intel-mmio-CRITICAL: Test assertion failure function 
intel_mmio_use_pci_bar, file ../../lib/intel_mmio.c:145:
  (intel_gpu_top:23021) intel-mmio-CRITICAL: Failed assertion: !(error != 0)
  (intel_gpu_top:23021) intel-mmio-CRITICAL: Last errno: 1, Operation not 
permitted
  (intel_gpu_top:23021) intel-mmio-CRITICAL: Couldn't map MMIO region
  Stack trace:
    #0 [_init+0x1753f]
    #1 [_init+0xc978]
    #2 [_init+0x118d]
    #3 [__libc_start_main+0xf1]
    #4 [_init+0x1fba]
    #5 [+0x1fba]
  Test (null) failed.
   DEBUG 
  (intel_gpu_top:23021) intel-chipset-DEBUG: Test requirement passed: pci_dev
  (intel_gpu_top:23021) intel-mmio-CRITICAL: Test assertion failure function 
intel_mmio_use_pci_bar, file ../../lib/intel_mmio.c:145:
  (intel_gpu_top:23021) intel-mmio-CRITICAL: Failed assertion: !(error != 0)
  (intel_gpu_top:23021) intel-mmio-CRITICAL: Last errno: 1, Operation not 
permitted
  (intel_gpu_top:23021) intel-mmio-CRITICAL: Couldn't map MMIO region
  (intel_gpu_top:23021) igt-core-INFO: Stack trace:
  (intel_gpu_top:23021) igt-core-INFO:   #0 [_init+0x1753f]
  (intel_gpu_top:23021) igt-core-INFO:   #1 [_init+0xc978]
  (intel_gpu_top:23021) igt-core-INFO:   #2 [_init+0x118d]
  (intel_gpu_top:23021) igt-core-INFO:   #3 [__libc_start_main+0xf1]
  (intel_gpu_top:23021) igt-core-INFO:   #4 [_init+0x1fba]
  (intel_gpu_top:23021) igt-core-INFO:   #5 [+0x1fba]
    END  
  FAIL (-1.000s)

  Happens under bot Wayland and XOrg.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: intel-gpu-tools 1.20-1ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Feb 28 00:30:15 2018
  InstallationDate: Installed on 2015-11-25 (825 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  SourcePackage: intel-gpu-tools
  UpgradeStatus: Upgraded to artful on 2017-11-01 (118 days ago)

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

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

[Kernel-packages] [Bug 1836373] Re: Mainline builds for 5.1 and 5.2 failing for amd64 and i386

[El jinete sin cabeza]

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

** This bug has been marked a duplicate of bug 1830961
   Kernels & kernel drivers fail to build with gcc-9 [error: 
‘-mindirect-branch’ and ‘-fcf-protection’ are not compatible]

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

Title:
  Mainline builds for 5.1 and 5.2 failing for amd64 and i386

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.2/BUILD.LOG.amd64

  /home/kernel/COD/linux/include/linux/compiler.h: In function 
'__read_once_size':
  /home/kernel/COD/linux/include/linux/compiler.h:193:1: error: 
'-mindirect-branch' and '-fcf-protection' are not compatible

  The build has multiple errors saying '-mindirect-branch' and '-fcf-
  protection' are not compatible.  This currently affects the 5.2 kernel
  build and the 5.1.17 kernel build.

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

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

[Kernel-packages] [Bug 1752772] Re: r8169 ethernet card don't work after returning from suspension

[Aleksey]

The same problem in Xubuntu 18.04.2 with kernel 4.15.0-54. The fix is:

sudo modprobe -r r8169
sudo modprobe -i r8169

Please reopen the issue.

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

Title:
  r8169 ethernet card don't work after returning from suspension

Status in Linux:
  New
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  Fix Released

Bug description:
  ===SRU Justification===
  [Impact]
  Ethernet r8169 stops working after system resumed from suspend.

  [Test]
  User confirmed these patches fix the issue. r8169 continues to work
  after resume from suspend.

  [Regression Potential]
  Medium. The fix is limited to one device, all patches are in mainline.
  The WOL default change might cause regression for users that depend on
  BIOS settings. We can advice them to use userspace tool (systemd,
  ethtool, etc.) instead.

  ===Original Bug Report===
  I have noticed that the network stopped working on my desktop after I've 
suspended the system and woke it up. On dmesg there are messages like:

  [  150.877998] IPv6: ADDRCONF(NETDEV_UP): enp1s0: link is not ready
  [  150.944101] do_IRQ: 3.37 No irq handler for vector
  [  150.944105] r8169 :01:00.0 enp1s0: link down
  [  150.944180] IPv6: ADDRCONF(NETDEV_UP): enp1s0: link is not ready

  When using Xenial (from a different install), this problem is not
  happening. This is happening on Bionic.

  There are only two ways to restore connectivity:
  1) Reboot the system;
  2) Remove the r8169 module and reinsert it with modprobe.

  The motherboard is a AsRock H55M-LE and the Ethernet controller is:

  01:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd.
  RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 03)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-firmware 1.172
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: LXDE
  Date: Fri Mar  2 00:21:57 2018
  Dependencies:

  InstallationDate: Installed on 2018-02-26 (3 days ago)
  InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180226)
  PackageArchitecture: all
  SourcePackage: linux-firmware
  UpgradeStatus: No upgrade log present (probably fresh install)
  ---
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.15.0-10-generic.
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: MID [HDA Intel MID], device 0: VT1818S Analog [VT1818S Analog]
     Subdevices: 1/1
     Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  usuario1153 F pulseaudio
   /dev/snd/controlC1:  usuario1153 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'MID'/'HDA Intel MID at 0xfbdf8000 irq 26'
     Mixer name : 'VIA VT1818S'
     Components : 'HDA:11060440,18492818,0010'
     Controls  : 40
     Simple ctrls  : 17
  Card1.Amixer.info:
   Card hw:1 'HDMI'/'HDA ATI HDMI at 0xfbffc000 irq 27'
     Mixer name : 'ATI R6xx HDMI'
     Components : 'HDA:1002aa01,00aa0100,00100200'
     Controls  : 7
     Simple ctrls  : 1
  Card1.Amixer.values:
   Simple mixer control 'IEC958',0
     Capabilities: pswitch pswitch-joined
     Playback channels: Mono
     Mono: Playback [on]
  CurrentDesktop: LXDE
  Dependencies:

  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=edd83175-c707-4b31-90d2-ce2f5cebc73f
  InstallationDate: Installed on 2018-02-26 (3 days ago)
  InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180226)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Package: linux-firmware 1.172
  PackageArchitecture: all
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz 
root=UUID=0c4fc517-b7a0-49b0-bfcb-0485dfe6413b ro quiet
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-10-generic N/A
   linux-backports-modules-4.15.0-10-generic  N/A
   linux-firmware 1.172
  RfKill:

  Tags:  bionic
  Uname: Linux 4.15.0-10-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/20/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.80
  dmi.board.name: H55M-LE
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 

[Kernel-packages] [Bug 1836426] Re: Bionic update: upstream stable patchset 2019-07-12

[Kamal Mostafa]

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

** Changed in: linux (Ubuntu Bionic)
 Assignee: (unassigned) => Kamal Mostafa (kamalmostafa)

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

Title:
  Bionic update: upstream stable patchset 2019-07-12

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

Bug description:
  SRU Justification

  Impact:
     The upstream process for stable tree updates is quite similar
     in scope to the Ubuntu SRU process, e.g., each patch has to
     demonstrably fix a bug, and each patch is vetted by upstream
     by originating either directly from a mainline/stable Linux tree or
     a minimally backported form of that patch. The following upstream
     stable patches should be included in the Ubuntu kernel:

     upstream stable patchset 2019-07-12

 Ported from the following upstream stable releases:
  v4.14.75, v4.18.13,
  v4.14.76, v4.18.14,
  v4.14.77, v4.18.15

     from git://git.kernel.org/

  drm/amd/pp: initialize result to before or'ing in data
  drm/amdgpu: add another ATPX quirk for TOPAZ
  tools/power turbostat: fix possible sprintf buffer overflow
  mac80211: Run TXQ teardown code before de-registering interfaces
  mac80211_hwsim: require at least one channel
  btrfs: btrfs_shrink_device should call commit transaction at the end
  scsi: csiostor: add a check for NULL pointer after kmalloc()
  mac80211: correct use of IEEE80211_VHT_CAP_RXSTBC_X
  mac80211_hwsim: correct use of IEEE80211_VHT_CAP_RXSTBC_X
  gpio: adp5588: Fix sleep-in-atomic-context bug
  mac80211: mesh: fix HWMP sequence numbering to follow standard
  mac80211: avoid kernel panic when building AMSDU from non-linear SKB
  gpiolib: acpi: Switch to cansleep version of GPIO library call
  gpiolib-acpi: Register GpioInt ACPI event handlers from a late_initcall
  cfg80211: nl80211_update_ft_ies() to validate NL80211_ATTR_IE
  mac80211: do not convert to A-MSDU if frag/subframe limited
  mac80211: always account for A-MSDU header changes
  tools/kvm_stat: fix handling of invalid paths in debugfs provider
  gpio: Fix crash due to registration race
  ARC: atomics: unbork atomic_fetch_##op()
  md/raid5-cache: disable reshape completely
  RAID10 BUG_ON in raise_barrier when force is true and conf->barrier is 0
  i2c: uniphier: issue STOP only for last message or I2C_M_STOP
  i2c: uniphier-f: issue STOP only for last message or I2C_M_STOP
  net: cadence: Fix a sleep-in-atomic-context bug in macb_halt_tx()
  fs/cifs: don't translate SFM_SLASH (U+F026) to backslash
  mac80211: fix an off-by-one issue in A-MSDU max_subframe computation
  cfg80211: fix a type issue in ieee80211_chandef_to_operating_class()
  mac80211: fix a race between restart and CSA flows
  mac80211: Fix station bandwidth setting after channel switch
  mac80211: don't Tx a deauth frame if the AP forbade Tx
  mac80211: shorten the IBSS debug messages
  tools/vm/slabinfo.c: fix sign-compare warning
  tools/vm/page-types.c: fix "defined but not used" warning
  mm: madvise(MADV_DODUMP): allow hugetlbfs pages
  netfilter: xt_cluster: add dependency on conntrack module
  HID: add support for Apple Magic Keyboards
  usb: gadget: fotg210-udc: Fix memory leak of fotg210->ep[i]
  HID: hid-saitek: Add device ID for RAT 7 Contagion
  scsi: qedi: Add the CRC size within iSCSI NVM image
  perf evsel: Fix potential null pointer dereference in perf_evsel__new_idx()
  perf util: Fix bad memory access in trace info.
  perf probe powerpc: Ignore SyS symbols irrespective of endianness
  netfilter: nf_tables: release chain in flushing set
  Revert "iio: temperature: maxim_thermocouple: add MAX31856 part"
  RDMA/ucma: check fd type in ucma_migrate_id()
  HID: sensor-hub: Restore fixup for Lenovo ThinkPad Helix 2 sensor hub report
  USB: yurex: Check for truncation in yurex_read()
  nvmet-rdma: fix possible bogus dereference under heavy load
  net/mlx5: Consider PCI domain in search for next dev
  drm/nouveau/TBDdevinit: don't fail when PMU/PRE_OS is missing from VBIOS
  drm/nouveau/disp: fix DP disable race
  dm raid: fix rebuild of specific devices by updating superblock
  fs/cifs: suppress a string overflow warning
  perf/x86/intel: Add support/quirk for the MISPREDICT bit on Knights Landing 
CPUs
  dm thin metadata: try to avoid ever aborting transactions
  arch/hexagon: fix kernel/dma.c build warning
  hexagon: modify ffs() and fls() to return int
  arm64: jump_label.h: use asm_volatile_goto macro instead of "asm goto"
  drm/amdgpu: fix error handling in amdgpu_cs_user_fence_chunk
  r8169: Clear RTL_FLAG_TASK_*_PENDING when clearing RTL_FLAG_TASK_ENABLED
  s390/qeth: don't dump past end of unknown HW header
  cifs: read overflow in is_valid_oplock_break()
  xen/manage: don't 

[Kernel-packages] [Bug 1836426] [NEW] Bionic update: upstream stable patchset 2019-07-12

[Kamal Mostafa]

Public bug reported:

SRU Justification

Impact:
   The upstream process for stable tree updates is quite similar
   in scope to the Ubuntu SRU process, e.g., each patch has to
   demonstrably fix a bug, and each patch is vetted by upstream
   by originating either directly from a mainline/stable Linux tree or
   a minimally backported form of that patch. The following upstream
   stable patches should be included in the Ubuntu kernel:

   upstream stable patchset 2019-07-12

   Ported from the following upstream stable releases:
v4.14.75, v4.18.13,
v4.14.76, v4.18.14,
v4.14.77, v4.18.15

   from git://git.kernel.org/

drm/amd/pp: initialize result to before or'ing in data
drm/amdgpu: add another ATPX quirk for TOPAZ
tools/power turbostat: fix possible sprintf buffer overflow
mac80211: Run TXQ teardown code before de-registering interfaces
mac80211_hwsim: require at least one channel
btrfs: btrfs_shrink_device should call commit transaction at the end
scsi: csiostor: add a check for NULL pointer after kmalloc()
mac80211: correct use of IEEE80211_VHT_CAP_RXSTBC_X
mac80211_hwsim: correct use of IEEE80211_VHT_CAP_RXSTBC_X
gpio: adp5588: Fix sleep-in-atomic-context bug
mac80211: mesh: fix HWMP sequence numbering to follow standard
mac80211: avoid kernel panic when building AMSDU from non-linear SKB
gpiolib: acpi: Switch to cansleep version of GPIO library call
gpiolib-acpi: Register GpioInt ACPI event handlers from a late_initcall
cfg80211: nl80211_update_ft_ies() to validate NL80211_ATTR_IE
mac80211: do not convert to A-MSDU if frag/subframe limited
mac80211: always account for A-MSDU header changes
tools/kvm_stat: fix handling of invalid paths in debugfs provider
gpio: Fix crash due to registration race
ARC: atomics: unbork atomic_fetch_##op()
md/raid5-cache: disable reshape completely
RAID10 BUG_ON in raise_barrier when force is true and conf->barrier is 0
i2c: uniphier: issue STOP only for last message or I2C_M_STOP
i2c: uniphier-f: issue STOP only for last message or I2C_M_STOP
net: cadence: Fix a sleep-in-atomic-context bug in macb_halt_tx()
fs/cifs: don't translate SFM_SLASH (U+F026) to backslash
mac80211: fix an off-by-one issue in A-MSDU max_subframe computation
cfg80211: fix a type issue in ieee80211_chandef_to_operating_class()
mac80211: fix a race between restart and CSA flows
mac80211: Fix station bandwidth setting after channel switch
mac80211: don't Tx a deauth frame if the AP forbade Tx
mac80211: shorten the IBSS debug messages
tools/vm/slabinfo.c: fix sign-compare warning
tools/vm/page-types.c: fix "defined but not used" warning
mm: madvise(MADV_DODUMP): allow hugetlbfs pages
netfilter: xt_cluster: add dependency on conntrack module
HID: add support for Apple Magic Keyboards
usb: gadget: fotg210-udc: Fix memory leak of fotg210->ep[i]
HID: hid-saitek: Add device ID for RAT 7 Contagion
scsi: qedi: Add the CRC size within iSCSI NVM image
perf evsel: Fix potential null pointer dereference in perf_evsel__new_idx()
perf util: Fix bad memory access in trace info.
perf probe powerpc: Ignore SyS symbols irrespective of endianness
netfilter: nf_tables: release chain in flushing set
Revert "iio: temperature: maxim_thermocouple: add MAX31856 part"
RDMA/ucma: check fd type in ucma_migrate_id()
HID: sensor-hub: Restore fixup for Lenovo ThinkPad Helix 2 sensor hub report
USB: yurex: Check for truncation in yurex_read()
nvmet-rdma: fix possible bogus dereference under heavy load
net/mlx5: Consider PCI domain in search for next dev
drm/nouveau/TBDdevinit: don't fail when PMU/PRE_OS is missing from VBIOS
drm/nouveau/disp: fix DP disable race
dm raid: fix rebuild of specific devices by updating superblock
fs/cifs: suppress a string overflow warning
perf/x86/intel: Add support/quirk for the MISPREDICT bit on Knights Landing CPUs
dm thin metadata: try to avoid ever aborting transactions
arch/hexagon: fix kernel/dma.c build warning
hexagon: modify ffs() and fls() to return int
arm64: jump_label.h: use asm_volatile_goto macro instead of "asm goto"
drm/amdgpu: fix error handling in amdgpu_cs_user_fence_chunk
r8169: Clear RTL_FLAG_TASK_*_PENDING when clearing RTL_FLAG_TASK_ENABLED
s390/qeth: don't dump past end of unknown HW header
cifs: read overflow in is_valid_oplock_break()
xen/manage: don't complain about an empty value in control/sysrq node
xen: avoid crash in disable_hotplug_cpu
xen: fix GCC warning and remove duplicate EVTCHN_ROW/EVTCHN_COL usage
ovl: fix access beyond unterminated strings
ovl: fix memory leak on unlink of indexed file
ovl: fix format of setxattr debug
sysfs: Do not return POSIX ACL xattrs via listxattr
smb2: fix missing files in root share directory listing
iommu/amd: Clear memory encryption mask from physical address
ALSA: hda/realtek - Cannot adjust speaker's volume on Dell XPS 27 7760
crypto: qat - Fix KASAN stack-out-of-bounds bug in adf_probe()
crypto: mxs-dcp - Fix wait logic on chan threads
crypto: caam/jr - 

[Kernel-packages] [Bug 1836373] Re: Mainline builds for 5.1 and 5.2 failing for amd64 and i386

[Doug Smythies]

This is duplicate with bug 1830961.

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

Title:
  Mainline builds for 5.1 and 5.2 failing for amd64 and i386

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.2/BUILD.LOG.amd64

  /home/kernel/COD/linux/include/linux/compiler.h: In function 
'__read_once_size':
  /home/kernel/COD/linux/include/linux/compiler.h:193:1: error: 
'-mindirect-branch' and '-fcf-protection' are not compatible

  The build has multiple errors saying '-mindirect-branch' and '-fcf-
  protection' are not compatible.  This currently affects the 5.2 kernel
  build and the 5.1.17 kernel build.

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

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

[Kernel-packages] [Bug 1835449] Please test proposed package

[Andy Whitcroft]

Hello Vincent, or anyone else affected,

Accepted linux-firmware into xenial-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/linux-
firmware/1.157.22 in a few hours, and then in the -proposed repository.

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

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

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

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

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

Title:
  Bluetooth: hci0: request failed to create LE connection: status 0x0c
  (Intel 9260)

Status in linux-firmware package in Ubuntu:
  In Progress
Status in linux-firmware source package in Xenial:
  Fix Committed
Status in linux-firmware source package in Bionic:
  Fix Committed

Bug description:
  [Impact]
  Intel Wireless-AC 9260 Bluetooth doesn't pair to Bluetooth 5.0 HID
  devices.

  [Fix]
  Bluetooth FW Build REL0329 or newer is known to have fixed this problem
  on Cosmic, and for Disco we have REL0420. On Bionic and Xenial it takes
  a firmware backport from upstream commit
  c2d8f1b7f820b31b6120d741c23db23340a72821. Original patch modified to fix
  conflicts in the WHENCE file.

  [Test Case]
  Verified on hardware platforms with Intel Wireless AC 9260 installed,
  e.g. Dell Precision 7530. Copied the two blobs to /lib/firmware/intel
  and power off the device completely to trigger firmware reload at the
  next boot.

  [Regression Risk]
  Low. Tried following kernels with REL0329 firmware blobs:

* 4.4.0-154-generic: Xenial, WiFi/Bluetooth doesn't work
* 4.8.0-58-generic: Xenial, even doesn't boot to console
* 4.10.0-42-generic: Xenial, WiFi/Bluetooth doesn't work
* 4.11.0-14-generic: Xenial, WiFi/Bluetooth doesn't work
* 4.13.0-45-generic: Xenial
* 4.15.0-54-generic: Xenial, Bionic
* 4.15.0-1043-oem: Xenial, Bionic

  For those WiFi/Bluetooth doesn't work versions, WiFi/Bluetooth doesn't
  work even with current firmware blobs shipped in Xenial's linux-firmware
  REL0186. So overall, these updated blobs are only loaded by hardware
  requires them, and they doesn't bring harm to known working
  configurations.

   Original Bug Description 

  Same problem exactly as encountered with Intel 9560 is also happening
  with Intel 9260.

  Update to linux-firmware 1.173.8 did not fix the problem.

  Everything is working fine when using 4.15 kernel, but not for 4.18+
  5.0+.

  Reference problem:
  https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1829737

  You-Sheng Yang advised to do this by email and it fixed my issue, so I
  think the 9260 driver would need to be updated in the bionic branch
  (it seems to be updated in newer branches).

  --
  Basically you should try copy the latest firmware (ibt-*) under
  
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/tree/intel
  , power off the device completely and power on, then have a check on
  bluetooth pairing.
  --

  Linux ideapad 5.0.0-20-generic #21~18.04.1-Ubuntu SMP Thu Jun 27
  04:04:37 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

  OS: Linux Mint 19.1 Tessa x86_64
  Host: 81JB Lenovo ideapad 730S-13IWL
  Wifi/Bluetooth card is Intel 9260

  @:/etc$ dmesg | egrep -i 'blue|firm'
  [0.099619] Spectre V2 : Enabling Restricted Speculation for firmware calls
  [0.173124] ACPI: [Firmware Bug]: BIOS _OSI(Linux) query ignored
  [2.379392] [Firmware Bug]: Invalid critical threshold (0)
  [2.699758] [drm] Finished loading DMC firmware i915/kbl_dmc_ver1_04.bin 
(v1.4)
  [6.259427] iwlwifi :73:00.0: loaded firmware version 43.95eb4e97.0 
op_mode iwlmvm
  [6.337749] Bluetooth: Core ver 2.22
  [6.337767] Bluetooth: HCI device and connection manager initialized
  [6.337770] Bluetooth: HCI socket layer initialized
  [6.337773] Bluetooth: L2CAP socket layer initialized
  [6.33] Bluetooth: SCO socket layer initialized
  [6.368073] Bluetooth: hci0: Firmware revision 0.1 build 201 week 49 2017
  [7.309936] Bluetooth: BNEP (Ethernet 

[Kernel-packages] [Bug 1836372] Re: Update firmware in nic-firmware udeb for 5.0 hwe kernel

[Andy Whitcroft]

Hello Seth, or anyone else affected,

Accepted linux-firmware into bionic-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/linux-
firmware/1.173.9 in a few hours, and then in the -proposed repository.

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

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-bionic to verification-done-bionic. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-bionic. In either case, without details of
your testing we will not be able to proceed.

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

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: linux-firmware (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-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/1836372

Title:
  Update firmware in nic-firmware udeb for 5.0 hwe kernel

Status in linux-firmware package in Ubuntu:
  Fix Committed
Status in linux-firmware source package in Bionic:
  Fix Committed

Bug description:
  SRU Justification

  Impact: Recent updates to linux-firmware means that there are new and
  updated firmware files relevant to the 5.0 hwe kernel from disco.
  Adding these files to give a better install experience for the 18.04.3
  release.

  Fix: Add the new firmware files to the nic-firmware udeb.

  Test Case: Confirm that the new files are present in the nic-firmware
  udeb.

  Regression Potential: New firmware versions could contain regressions.
  These versions have already been released into bionic with no reported
  regressions though, and are known to fix actual problems, so the
  benefit seems to outweigh the potential risk.

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

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

[Kernel-packages] [Bug 1835449] Please test proposed package

[Andy Whitcroft]

Hello Vincent, or anyone else affected,

Accepted linux-firmware into bionic-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/linux-
firmware/1.173.9 in a few hours, and then in the -proposed repository.

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

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-bionic to verification-done-bionic. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-bionic. In either case, without details of
your testing we will not be able to proceed.

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

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

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

Title:
  Bluetooth: hci0: request failed to create LE connection: status 0x0c
  (Intel 9260)

Status in linux-firmware package in Ubuntu:
  In Progress
Status in linux-firmware source package in Xenial:
  Fix Committed
Status in linux-firmware source package in Bionic:
  Fix Committed

Bug description:
  [Impact]
  Intel Wireless-AC 9260 Bluetooth doesn't pair to Bluetooth 5.0 HID
  devices.

  [Fix]
  Bluetooth FW Build REL0329 or newer is known to have fixed this problem
  on Cosmic, and for Disco we have REL0420. On Bionic and Xenial it takes
  a firmware backport from upstream commit
  c2d8f1b7f820b31b6120d741c23db23340a72821. Original patch modified to fix
  conflicts in the WHENCE file.

  [Test Case]
  Verified on hardware platforms with Intel Wireless AC 9260 installed,
  e.g. Dell Precision 7530. Copied the two blobs to /lib/firmware/intel
  and power off the device completely to trigger firmware reload at the
  next boot.

  [Regression Risk]
  Low. Tried following kernels with REL0329 firmware blobs:

* 4.4.0-154-generic: Xenial, WiFi/Bluetooth doesn't work
* 4.8.0-58-generic: Xenial, even doesn't boot to console
* 4.10.0-42-generic: Xenial, WiFi/Bluetooth doesn't work
* 4.11.0-14-generic: Xenial, WiFi/Bluetooth doesn't work
* 4.13.0-45-generic: Xenial
* 4.15.0-54-generic: Xenial, Bionic
* 4.15.0-1043-oem: Xenial, Bionic

  For those WiFi/Bluetooth doesn't work versions, WiFi/Bluetooth doesn't
  work even with current firmware blobs shipped in Xenial's linux-firmware
  REL0186. So overall, these updated blobs are only loaded by hardware
  requires them, and they doesn't bring harm to known working
  configurations.

   Original Bug Description 

  Same problem exactly as encountered with Intel 9560 is also happening
  with Intel 9260.

  Update to linux-firmware 1.173.8 did not fix the problem.

  Everything is working fine when using 4.15 kernel, but not for 4.18+
  5.0+.

  Reference problem:
  https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1829737

  You-Sheng Yang advised to do this by email and it fixed my issue, so I
  think the 9260 driver would need to be updated in the bionic branch
  (it seems to be updated in newer branches).

  --
  Basically you should try copy the latest firmware (ibt-*) under
  
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/tree/intel
  , power off the device completely and power on, then have a check on
  bluetooth pairing.
  --

  Linux ideapad 5.0.0-20-generic #21~18.04.1-Ubuntu SMP Thu Jun 27
  04:04:37 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

  OS: Linux Mint 19.1 Tessa x86_64
  Host: 81JB Lenovo ideapad 730S-13IWL
  Wifi/Bluetooth card is Intel 9260

  @:/etc$ dmesg | egrep -i 'blue|firm'
  [0.099619] Spectre V2 : Enabling Restricted Speculation for firmware calls
  [0.173124] ACPI: [Firmware Bug]: BIOS _OSI(Linux) query ignored
  [2.379392] [Firmware Bug]: Invalid critical threshold (0)
  [2.699758] [drm] Finished loading DMC firmware i915/kbl_dmc_ver1_04.bin 
(v1.4)
  [6.259427] iwlwifi :73:00.0: loaded firmware version 43.95eb4e97.0 
op_mode iwlmvm
  [6.337749] Bluetooth: Core ver 2.22
  [6.337767] Bluetooth: HCI device and connection manager initialized
  [6.337770] Bluetooth: HCI socket layer initialized
  [6.337773] Bluetooth: L2CAP socket layer initialized
  [6.33] Bluetooth: SCO socket layer initialized
  [6.368073] Bluetooth: hci0: Firmware revision 0.1 build 201 week 49 2017
  [7.309936] Bluetooth: BNEP (Ethernet 

[Kernel-packages] [Bug 1835345] Please test proposed package

[Andy Whitcroft]

Hello AceLan, or anyone else affected,

Accepted linux-firmware into bionic-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/linux-
firmware/1.173.9 in a few hours, and then in the -proposed repository.

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

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-bionic to verification-done-bionic. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-bionic. In either case, without details of
your testing we will not be able to proceed.

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

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

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

Title:
  [Intel CyclonePeak] Can not turn on BT after turn off (via Hotkey)

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 Disco:
  Fix Committed

Bug description:
  [Impact]
  BT fails to enable again after disabled it by hotkey with the following 
message
     Bus 001 Device 004: ID 8087:0029 Intel Corp.
  [248987.643125] usb 1-10: device descriptor read/64, error -110
  [249003.247721] usb 1-10: device descriptor read/64, error -110
  [249003.483611] usb 1-10: reset full-speed USB device number 4 using xhci_hcd
  [249018.855466] usb 1-10: device descriptor read/64, error -110
  [249034.467589] usb 1-10: device descriptor read/64, error -110
  [249034.703574] usb 1-10: reset full-speed USB device number 4 using xhci_hcd
  [249045.299399] usb 1-10: device not accepting address 4, error -62
  [249045.427510] usb 1-10: reset full-speed USB device number 4 using xhci_hcd
  [249050.675715] usb 1-10: Device not responding to setup address.
  [249050.883541] usb 1-10: device not accepting address 4, error -71

  [Fix]
  Found the updated firmware fixes the issue

  [Test]
  Verify on the machine couple days, and can't duplicate the issue anymore.

  [Regression Potential]
  Low, the system keeps running for 5 days, and pass s3 tests 30 times, 
everything works well.

  [Misc]
  The firmware for the wifi/bt card is intel/ibt-20-0-3.*, but 
intel/ibt-20-0-4.* have identical md5sum. To avoid the following new cards 
require the new fw_revision, so SRU both of them.

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

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

[Kernel-packages] [Bug 1834464] Please test proposed package

[Andy Whitcroft]

Hello You-Sheng, or anyone else affected,

Accepted linux-firmware into bionic-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/linux-
firmware/1.173.9 in a few hours, and then in the -proposed repository.

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

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-bionic to verification-done-bionic. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-bionic. In either case, without details of
your testing we will not be able to proceed.

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

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

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

Title:
  Missing bluetooth firmware for Intel Wireless-AC 9462/9560

Status in HWE Next:
  New
Status in linux-firmware package in Ubuntu:
  In Progress
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:
  In Progress

Bug description:
  [Impact]
  Bluetooth on Intel Wireless-AC 9462/9560 requires new firmware blobs to
  be enabled.

  [Fix]
  Backport newly released firmware blobs from linux-firmware. This will
  also requires minor change to the WHENCE file to resolve cherry-pick
  conflicts. B/C/D would requires this explicitly and Eoan should be
  rebased onto linux-firmware master branch HEAD as usual.

  [Test Case]
  Verified with hardware platforms with corresponding devices. Completely
  power off and power on to trigger firmware reload, check from dmesg to
  see if Bluetooth firmware has been correctly loaded.

  [Regression Risk]
  Low. This adds new binary firmware blobs that are only loaded by
  targeting hardware.

  == original bug description ==

  On systems with Intel Wireless-AC 9462/9560 cards, following failed-
  to-load-firmware kernel messages found:

    bluetooth hci0: Direct firmware load for intel/ibt-19-32-1.sfi
  failed with error -2

  See also Bug #1833065 for wireless firmware & driver fix.

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

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

[Kernel-packages] [Bug 1835345] Please test proposed package

[Andy Whitcroft]

Hello AceLan, or anyone else affected,

Accepted linux-firmware into disco-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/linux-
firmware/1.178.3 in a few hours, and then in the -proposed repository.

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

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-disco to verification-done-disco. If it does not fix
the bug for you, please add a comment stating that, and change the tag
to verification-failed-disco. In either case, without details of your
testing we will not be able to proceed.

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

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

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

Title:
  [Intel CyclonePeak] Can not turn on BT after turn off (via Hotkey)

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 Disco:
  Fix Committed

Bug description:
  [Impact]
  BT fails to enable again after disabled it by hotkey with the following 
message
     Bus 001 Device 004: ID 8087:0029 Intel Corp.
  [248987.643125] usb 1-10: device descriptor read/64, error -110
  [249003.247721] usb 1-10: device descriptor read/64, error -110
  [249003.483611] usb 1-10: reset full-speed USB device number 4 using xhci_hcd
  [249018.855466] usb 1-10: device descriptor read/64, error -110
  [249034.467589] usb 1-10: device descriptor read/64, error -110
  [249034.703574] usb 1-10: reset full-speed USB device number 4 using xhci_hcd
  [249045.299399] usb 1-10: device not accepting address 4, error -62
  [249045.427510] usb 1-10: reset full-speed USB device number 4 using xhci_hcd
  [249050.675715] usb 1-10: Device not responding to setup address.
  [249050.883541] usb 1-10: device not accepting address 4, error -71

  [Fix]
  Found the updated firmware fixes the issue

  [Test]
  Verify on the machine couple days, and can't duplicate the issue anymore.

  [Regression Potential]
  Low, the system keeps running for 5 days, and pass s3 tests 30 times, 
everything works well.

  [Misc]
  The firmware for the wifi/bt card is intel/ibt-20-0-3.*, but 
intel/ibt-20-0-4.* have identical md5sum. To avoid the following new cards 
require the new fw_revision, so SRU both of them.

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

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

[Kernel-packages] [Bug 1834464] Please test proposed package

[Andy Whitcroft]

Hello You-Sheng, or anyone else affected,

Accepted linux-firmware into disco-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/linux-
firmware/1.178.3 in a few hours, and then in the -proposed repository.

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

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-disco to verification-done-disco. If it does not fix
the bug for you, please add a comment stating that, and change the tag
to verification-failed-disco. In either case, without details of your
testing we will not be able to proceed.

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

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

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

Title:
  Missing bluetooth firmware for Intel Wireless-AC 9462/9560

Status in HWE Next:
  New
Status in linux-firmware package in Ubuntu:
  In Progress
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:
  In Progress

Bug description:
  [Impact]
  Bluetooth on Intel Wireless-AC 9462/9560 requires new firmware blobs to
  be enabled.

  [Fix]
  Backport newly released firmware blobs from linux-firmware. This will
  also requires minor change to the WHENCE file to resolve cherry-pick
  conflicts. B/C/D would requires this explicitly and Eoan should be
  rebased onto linux-firmware master branch HEAD as usual.

  [Test Case]
  Verified with hardware platforms with corresponding devices. Completely
  power off and power on to trigger firmware reload, check from dmesg to
  see if Bluetooth firmware has been correctly loaded.

  [Regression Risk]
  Low. This adds new binary firmware blobs that are only loaded by
  targeting hardware.

  == original bug description ==

  On systems with Intel Wireless-AC 9462/9560 cards, following failed-
  to-load-firmware kernel messages found:

    bluetooth hci0: Direct firmware load for intel/ibt-19-32-1.sfi
  failed with error -2

  See also Bug #1833065 for wireless firmware & driver fix.

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

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

[Kernel-packages] [Bug 1830961] Re: Kernels & kernel drivers fail to build with gcc-9 [error: ‘-mindirect-branch’ and ‘-fcf-protection’ are not compatible]

[Maarten Fonville]

Can the patch that was applied to the kernel in
https://launchpad.net/ubuntu/+source/linux/5.2.0-8.9 please also be
applied to the daily mainline builds? (possible duplicate bug:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1836373 )

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

Title:
  Kernels & kernel drivers fail to build with gcc-9 [error: ‘-mindirect-
  branch’ and ‘-fcf-protection’ are not compatible]

Status in gcc-9 package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-430 package in Ubuntu:
  Fix Released
Status in virtualbox package in Ubuntu:
  Confirmed
Status in xtables-addons package in Ubuntu:
  Confirmed

Bug description:
  Compiling kernels & kernel modules fails due to these errors:

  ./include/linux/compiler.h:193:1: error: ‘-mindirect-branch’ and
  ‘-fcf-protection’ are not compatible

  (This happens with any kernel modules.)

  This appears to be due to the changes in 9.1.0-3ubuntu1 enabling -fcf-
  protection by default on 19.10's gcc-9.

  Switching to gcc-8 allows compilation to proceed.

  WORKAROUND:

  sudo ln -fs gcc-8 /usr/bin/gcc

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gcc-9/+bug/1830961/+subscriptions

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

[Kernel-packages] [Bug 1835434] Re: linux-azure: 5.0.0-1012.12 -proposed tracker

[Ubuntu Kernel Bot]

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
    https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  backports: bug 1835882 (bionic/linux-azure-edge)
  
  -- swm properties --
  kernel-stable-master-bug: 1834902
  phase: Ready for Testing
  phase-changed: Wednesday, 10. July 2019 23:36 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
regression-testing: Ongoing -- testing in progress
-   stakeholder-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  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/1835434

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

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

  backports: bug 1835882 (bionic/linux-azure-edge)

  -- swm properties --
  kernel-stable-master-bug: 1834902
  phase: Ready for Testing
  phase-changed: Wednesday, 10. July 2019 23:36 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
regression-testing: Ongoing -- testing in progress
verification-testing: Ongoing -- testing in progress
  variant: debs

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

-- 
Mailing list: https://launchpad.net/~kernel-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

[Ubuntu Kernel Bot]

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

** 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 1835388 (bionic/linux-hwe), bug 1836161 (bionic/linux-oem-osp1)
  derivatives: bug 1834884 (linux-raspi2), bug 1834886 (linux-aws), bug 1834891 
(linux-gcp), bug 1834892 (linux-kvm), bug 1834894 (linux-snapdragon), bug 
1835434 (linux-azure)
  
  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
- phase: Ready for Testing
- phase-changed: Friday, 12. July 2019 17:10 UTC
+ phase: Testing
+ phase-changed: Friday, 12. July 2019 20:00 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   automated-testing: Ongoing -- testing in progress
+   automated-testing: Stalled -- testing FAILED
certification-testing: Ongoing -- testing in progress
regression-testing: Ongoing -- testing in progress
verification-testing: Ongoing -- testing in progress
  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:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-lrm series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
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 1835388 (bionic/linux-hwe), bug 1836161 (bionic/linux-oem-osp1)
  derivatives: bug 1834884 (linux-raspi2), bug 1834886 (linux-aws), bug 1834891 
(linux-gcp), bug 1834892 (linux-kvm), bug 1834894 (linux-snapdragon), bug 
1835434 (linux-azure)

  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
  phase: Testing
  phase-changed: Friday, 12. July 2019 20:00 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Stalled -- testing FAILED
certification-testing: Ongoing -- testing in progress
regression-testing: Ongoing -- testing in progress
verification-testing: Ongoing -- testing in progress
  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 1834904] Re: linux: 4.18.0-26.27 -proposed tracker

[Ubuntu Kernel Bot]

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

** 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 1834880 (linux-raspi2), bug 1834883 (linux-aws), bug
  1834899 (linux-gcp), bug 1834901 (linux-kvm), bug 1835438 (linux-azure)
  
  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
- phase: Ready for Testing
- phase-changed: Friday, 12. July 2019 17:16 UTC
+ phase: Testing
+ phase-changed: Friday, 12. July 2019 20:01 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   automated-testing: Ongoing -- testing in progress
+   automated-testing: Stalled -- testing FAILED
  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:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  Fix Released
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Invalid
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  Invalid
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

  derivatives: bug 1834880 (linux-raspi2), bug 1834883 (linux-aws), bug
  1834899 (linux-gcp), bug 1834901 (linux-kvm), bug 1835438 (linux-
  azure)

  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
  phase: Testing
  phase-changed: Friday, 12. July 2019 20:01 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Stalled -- testing FAILED
  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 1834918] Re: linux: 4.4.0-155.182 -proposed tracker

[Ubuntu Kernel Bot]

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

** 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 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 --
  boot-testing-requested: true
  bugs-spammed: true
- phase: Ready for Testing
- phase-changed: Friday, 12. July 2019 17:21 UTC
+ phase: Testing
+ phase-changed: Friday, 12. July 2019 20:01 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   automated-testing: Ongoing -- testing in progress
+   automated-testing: Stalled -- testing FAILED
certification-testing: Ongoing -- testing in progress
verification-testing: Ongoing -- testing in progress
  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:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  New

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

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

  backports: bug 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 --
  boot-testing-requested: true
  bugs-spammed: true
  phase: Testing
  phase-changed: Friday, 12. July 2019 20:01 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Stalled -- testing FAILED
certification-testing: Ongoing -- testing in progress
verification-testing: Ongoing -- testing in progress
  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 1834950] Re: linux-azure: 4.15.0-1051.56 -proposed tracker

[Ubuntu Kernel Bot]

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  backports: bug 1834948 (trusty/linux-azure)
  derivatives: bug 1834945 (azure-kernel), bug 1834946 (linux-azure-edge)
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1834954
  phase: Ready for Testing
  phase-changed: Wednesday, 10. July 2019 23:42 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
regression-testing: Ongoing -- testing in progress
-   stakeholder-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  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: 4.15.0-1051.56 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow stakeholder-signoff series:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
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 --
  boot-testing-requested: true
  kernel-stable-master-bug: 1834954
  phase: Ready for Testing
  phase-changed: Wednesday, 10. July 2019 23:42 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
regression-testing: Ongoing -- testing in progress
verification-testing: Ongoing -- testing in progress
  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 1831268] Re: Ubuntu 19.04: Random SR-IOV issues

[Joshua R. Poulson]

Actually, it looks like that patch has been applied to this tree.

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

Title:
  Ubuntu 19.04: Random SR-IOV issues

Status in linux-azure package in Ubuntu:
  New

Bug description:
  No VFs inside the VM.

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

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

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

  mlx4_en: rename9: Link Up

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

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

[Kernel-packages] [Bug 1834948] Re: linux-azure: 4.15.0-1051.56~14.04.1 -proposed tracker

[Ubuntu Kernel Bot]

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1834950
  phase: Ready for Testing
  phase-changed: Wednesday, 10. July 2019 23:45 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
regression-testing: Ongoing -- testing in progress
-   stakeholder-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  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/1834948

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

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

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

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

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1834950
  phase: Ready for Testing
  phase-changed: Wednesday, 10. July 2019 23:45 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
regression-testing: Ongoing -- testing in progress
verification-testing: Ongoing -- testing in progress
  variant: debs

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

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

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

[Ubuntu Kernel Bot]

This change was made by a bot.

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

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

Title:
  ACPI: Invalid passive threshold

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  dmesg:
  [0.830997] ACPI: Invalid passive threshold

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: linux-image-5.2.0-8-generic 5.2.0-8.9
  ProcVersionSignature: Ubuntu 5.2.0-8.9-generic 5.2.0
  Uname: Linux 5.2.0-8-generic x86_64
  ApportVersion: 2.20.11-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  caravena   2036 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jul 12 15:10:00 2019
  HibernationDevice: RESUME=UUID=efcf081f-0bb0-4907-b78c-1299aa4aee57
  InstallationDate: Installed on 2018-12-02 (222 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: HP HP Pavilion x360 Convertible 14-cd0xxx
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.2.0-8-generic 
root=UUID=28bdadba-133c-4f5b-a5c9-b06993ea7ce2 ro rootflags=subvol=@ quiet 
splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-5.2.0-8-generic N/A
   linux-backports-modules-5.2.0-8-generic  N/A
   linux-firmware   1.180
  SourcePackage: linux
  UpgradeStatus: Upgraded to eoan on 2018-12-02 (221 days ago)
  dmi.bios.date: 11/08/2018
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.32
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 8486
  dmi.board.vendor: HP
  dmi.board.version: 72.23
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.32:bd11/08/2018:svnHP:pnHPPavilionx360Convertible14-cd0xxx:pvrType1ProductConfigId:rvnHP:rn8486:rvr72.23:cvnHP:ct31:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Pavilion
  dmi.product.name: HP Pavilion x360 Convertible 14-cd0xxx
  dmi.product.sku: 3PX63LA#ABM
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP

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

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

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

[Ubuntu Kernel Bot]

This change was made by a bot.

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

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

Title:
  Bluetooth: hci0: inquiry failed: status 0x0c

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  dmesg:
  [   64.142848] Bluetooth: hci0: inquiry failed: status 0x0c

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: linux-image-5.2.0-8-generic 5.2.0-8.9
  ProcVersionSignature: Ubuntu 5.2.0-8.9-generic 5.2.0
  Uname: Linux 5.2.0-8-generic x86_64
  ApportVersion: 2.20.11-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  caravena   2036 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jul 12 15:03:07 2019
  HibernationDevice: RESUME=UUID=efcf081f-0bb0-4907-b78c-1299aa4aee57
  InstallationDate: Installed on 2018-12-02 (222 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: HP HP Pavilion x360 Convertible 14-cd0xxx
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.2.0-8-generic 
root=UUID=28bdadba-133c-4f5b-a5c9-b06993ea7ce2 ro rootflags=subvol=@ quiet 
splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-5.2.0-8-generic N/A
   linux-backports-modules-5.2.0-8-generic  N/A
   linux-firmware   1.180
  SourcePackage: linux
  UpgradeStatus: Upgraded to eoan on 2018-12-02 (221 days ago)
  dmi.bios.date: 11/08/2018
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.32
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 8486
  dmi.board.vendor: HP
  dmi.board.version: 72.23
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.32:bd11/08/2018:svnHP:pnHPPavilionx360Convertible14-cd0xxx:pvrType1ProductConfigId:rvnHP:rn8486:rvr72.23:cvnHP:ct31:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Pavilion
  dmi.product.name: HP Pavilion x360 Convertible 14-cd0xxx
  dmi.product.sku: 3PX63LA#ABM
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP

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

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

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

[Ubuntu Kernel Bot]

This change was made by a bot.

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

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

Title:
  lis3lv02d: unknown sensor type 0x0

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  dmesg:
  [4.135296] lis3lv02d: unknown sensor type 0x0

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: linux-image-5.2.0-8-generic 5.2.0-8.9
  ProcVersionSignature: Ubuntu 5.2.0-8.9-generic 5.2.0
  Uname: Linux 5.2.0-8-generic x86_64
  ApportVersion: 2.20.11-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  caravena   2036 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jul 12 14:53:45 2019
  HibernationDevice: RESUME=UUID=efcf081f-0bb0-4907-b78c-1299aa4aee57
  InstallationDate: Installed on 2018-12-02 (222 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: HP HP Pavilion x360 Convertible 14-cd0xxx
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.2.0-8-generic 
root=UUID=28bdadba-133c-4f5b-a5c9-b06993ea7ce2 ro rootflags=subvol=@ quiet 
splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-5.2.0-8-generic N/A
   linux-backports-modules-5.2.0-8-generic  N/A
   linux-firmware   1.180
  SourcePackage: linux
  UpgradeStatus: Upgraded to eoan on 2018-12-02 (221 days ago)
  dmi.bios.date: 11/08/2018
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.32
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 8486
  dmi.board.vendor: HP
  dmi.board.version: 72.23
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.32:bd11/08/2018:svnHP:pnHPPavilionx360Convertible14-cd0xxx:pvrType1ProductConfigId:rvnHP:rn8486:rvr72.23:cvnHP:ct31:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Pavilion
  dmi.product.name: HP Pavilion x360 Convertible 14-cd0xxx
  dmi.product.sku: 3PX63LA#ABM
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP

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

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

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

[Joshua R. Poulson]

I'm wondering if the upstream change "Fix locking in SRIOV mode of mlx4
driver, from Jack Morgenstein" might fix this issue. It's part of this
merge to Dave Miller's tree, and later to 5.1:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/net/ethernet/mellanox?h=v5.2=f3ca4c55a6581c46e9f4a592dd698a7c67a713dd

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

Title:
  Ubuntu 19.04: Random SR-IOV issues

Status in linux-azure package in Ubuntu:
  New

Bug description:
  No VFs inside the VM.

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

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

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

  mlx4_en: rename9: Link Up

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

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

[Kernel-packages] [Bug 1836414] [NEW] Wireless 8265 / 8275 crashing

[Florian Klug]

Public bug reported:

The Intel 8265 / 8275 Wireless in my Lenovo ThinkPad X1 Yoga (Gen 3)
keeps constantly crashing with

Jun 28 21:09:46 thinkflurl wpa_supplicant[882]: TDLS: Creating peer entry for 
1c:23:2c:6e:90:09
Jun 28 21:09:46 thinkflurl wpa_supplicant[882]: TDLS: Dialog Token in TPK M1 1
Jun 28 21:09:46 thinkflurl kernel: iwlwifi :02:00.0: Microcode SW error 
detected.  Restarting 0x8200.

I'm reporting this against the linux-firmware package because I found
this bug report https://bugzilla.kernel.org/show_bug.cgi?id=203055 and
the firmware posted in comment 1 fixed the crashes. But the thing is, on
Jun 28 21:09:46 this crash happend the first time after months of
trouble free wifi. And in dpkg.log I don't see any updates to this
package before the crash. So I have no clue, what caused this.

What I expected to happen:
I expected a stable wifi connection

What happens:
Wifi keeps crashing

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: linux-firmware 1.178.2 [modified: lib/firmware/iwlwifi-8000C-36.ucode 
lib/firmware/iwlwifi-8265-36.ucode]
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
CurrentDesktop: XFCE
Date: Fri Jul 12 20:46:10 2019
Dependencies:
 
InstallationDate: Installed on 2019-04-06 (97 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190326.2)
PackageArchitecture: all
SourcePackage: linux-firmware
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug disco

** Attachment added: "dpkg.log.1"
   https://bugs.launchpad.net/bugs/1836414/+attachment/5276817/+files/dpkg.log.1

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

Title:
  Wireless 8265 / 8275 crashing

Status in linux-firmware package in Ubuntu:
  New

Bug description:
  The Intel 8265 / 8275 Wireless in my Lenovo ThinkPad X1 Yoga (Gen 3)
  keeps constantly crashing with

  Jun 28 21:09:46 thinkflurl wpa_supplicant[882]: TDLS: Creating peer entry for 
1c:23:2c:6e:90:09
  Jun 28 21:09:46 thinkflurl wpa_supplicant[882]: TDLS: Dialog Token in TPK M1 1
  Jun 28 21:09:46 thinkflurl kernel: iwlwifi :02:00.0: Microcode SW error 
detected.  Restarting 0x8200.

  I'm reporting this against the linux-firmware package because I found
  this bug report https://bugzilla.kernel.org/show_bug.cgi?id=203055 and
  the firmware posted in comment 1 fixed the crashes. But the thing is,
  on Jun 28 21:09:46 this crash happend the first time after months of
  trouble free wifi. And in dpkg.log I don't see any updates to this
  package before the crash. So I have no clue, what caused this.

  What I expected to happen:
  I expected a stable wifi connection

  What happens:
  Wifi keeps crashing

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: linux-firmware 1.178.2 [modified: 
lib/firmware/iwlwifi-8000C-36.ucode lib/firmware/iwlwifi-8265-36.ucode]
  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
  CurrentDesktop: XFCE
  Date: Fri Jul 12 20:46:10 2019
  Dependencies:
   
  InstallationDate: Installed on 2019-04-06 (97 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190326.2)
  PackageArchitecture: all
  SourcePackage: linux-firmware
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1836372] Re: Update firmware in nic-firmware udeb for 5.0 hwe kernel

[Seth Forshee]

** Changed in: linux-firmware (Ubuntu)
   Status: Invalid => Fix Committed

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

Title:
  Update firmware in nic-firmware udeb for 5.0 hwe kernel

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

Bug description:
  SRU Justification

  Impact: Recent updates to linux-firmware means that there are new and
  updated firmware files relevant to the 5.0 hwe kernel from disco.
  Adding these files to give a better install experience for the 18.04.3
  release.

  Fix: Add the new firmware files to the nic-firmware udeb.

  Test Case: Confirm that the new files are present in the nic-firmware
  udeb.

  Regression Potential: New firmware versions could contain regressions.
  These versions have already been released into bionic with no reported
  regressions though, and are known to fix actual problems, so the
  benefit seems to outweigh the potential risk.

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

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

[Kernel-packages] [Bug 1836412] [NEW] ACPI: Invalid passive threshold

[El jinete sin cabeza]

Public bug reported:

dmesg:
[0.830997] ACPI: Invalid passive threshold

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: linux-image-5.2.0-8-generic 5.2.0-8.9
ProcVersionSignature: Ubuntu 5.2.0-8.9-generic 5.2.0
Uname: Linux 5.2.0-8-generic x86_64
ApportVersion: 2.20.11-0ubuntu3
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  caravena   2036 F pulseaudio
CurrentDesktop: ubuntu:GNOME
Date: Fri Jul 12 15:10:00 2019
HibernationDevice: RESUME=UUID=efcf081f-0bb0-4907-b78c-1299aa4aee57
InstallationDate: Installed on 2018-12-02 (222 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
MachineType: HP HP Pavilion x360 Convertible 14-cd0xxx
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.2.0-8-generic 
root=UUID=28bdadba-133c-4f5b-a5c9-b06993ea7ce2 ro rootflags=subvol=@ quiet 
splash vt.handoff=1
RelatedPackageVersions:
 linux-restricted-modules-5.2.0-8-generic N/A
 linux-backports-modules-5.2.0-8-generic  N/A
 linux-firmware   1.180
SourcePackage: linux
UpgradeStatus: Upgraded to eoan on 2018-12-02 (221 days ago)
dmi.bios.date: 11/08/2018
dmi.bios.vendor: Insyde
dmi.bios.version: F.32
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: 8486
dmi.board.vendor: HP
dmi.board.version: 72.23
dmi.chassis.asset.tag: Chassis Asset Tag
dmi.chassis.type: 31
dmi.chassis.vendor: HP
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnInsyde:bvrF.32:bd11/08/2018:svnHP:pnHPPavilionx360Convertible14-cd0xxx:pvrType1ProductConfigId:rvnHP:rn8486:rvr72.23:cvnHP:ct31:cvrChassisVersion:
dmi.product.family: 103C_5335KV HP Pavilion
dmi.product.name: HP Pavilion x360 Convertible 14-cd0xxx
dmi.product.sku: 3PX63LA#ABM
dmi.product.version: Type1ProductConfigId
dmi.sys.vendor: HP

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


** Tags: amd64 apport-bug eoan package-from-proposed

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

Title:
  ACPI: Invalid passive threshold

Status in linux package in Ubuntu:
  New

Bug description:
  dmesg:
  [0.830997] ACPI: Invalid passive threshold

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: linux-image-5.2.0-8-generic 5.2.0-8.9
  ProcVersionSignature: Ubuntu 5.2.0-8.9-generic 5.2.0
  Uname: Linux 5.2.0-8-generic x86_64
  ApportVersion: 2.20.11-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  caravena   2036 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jul 12 15:10:00 2019
  HibernationDevice: RESUME=UUID=efcf081f-0bb0-4907-b78c-1299aa4aee57
  InstallationDate: Installed on 2018-12-02 (222 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: HP HP Pavilion x360 Convertible 14-cd0xxx
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.2.0-8-generic 
root=UUID=28bdadba-133c-4f5b-a5c9-b06993ea7ce2 ro rootflags=subvol=@ quiet 
splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-5.2.0-8-generic N/A
   linux-backports-modules-5.2.0-8-generic  N/A
   linux-firmware   1.180
  SourcePackage: linux
  UpgradeStatus: Upgraded to eoan on 2018-12-02 (221 days ago)
  dmi.bios.date: 11/08/2018
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.32
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 8486
  dmi.board.vendor: HP
  dmi.board.version: 72.23
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.32:bd11/08/2018:svnHP:pnHPPavilionx360Convertible14-cd0xxx:pvrType1ProductConfigId:rvnHP:rn8486:rvr72.23:cvnHP:ct31:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Pavilion
  dmi.product.name: HP Pavilion x360 Convertible 14-cd0xxx
  dmi.product.sku: 3PX63LA#ABM
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP

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

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

[Kernel-packages] [Bug 1836411] [NEW] Bluetooth: hci0: inquiry failed: status 0x0c

[El jinete sin cabeza]

Public bug reported:

dmesg:
[   64.142848] Bluetooth: hci0: inquiry failed: status 0x0c

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: linux-image-5.2.0-8-generic 5.2.0-8.9
ProcVersionSignature: Ubuntu 5.2.0-8.9-generic 5.2.0
Uname: Linux 5.2.0-8-generic x86_64
ApportVersion: 2.20.11-0ubuntu3
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  caravena   2036 F pulseaudio
CurrentDesktop: ubuntu:GNOME
Date: Fri Jul 12 15:03:07 2019
HibernationDevice: RESUME=UUID=efcf081f-0bb0-4907-b78c-1299aa4aee57
InstallationDate: Installed on 2018-12-02 (222 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
MachineType: HP HP Pavilion x360 Convertible 14-cd0xxx
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.2.0-8-generic 
root=UUID=28bdadba-133c-4f5b-a5c9-b06993ea7ce2 ro rootflags=subvol=@ quiet 
splash vt.handoff=1
RelatedPackageVersions:
 linux-restricted-modules-5.2.0-8-generic N/A
 linux-backports-modules-5.2.0-8-generic  N/A
 linux-firmware   1.180
SourcePackage: linux
UpgradeStatus: Upgraded to eoan on 2018-12-02 (221 days ago)
dmi.bios.date: 11/08/2018
dmi.bios.vendor: Insyde
dmi.bios.version: F.32
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: 8486
dmi.board.vendor: HP
dmi.board.version: 72.23
dmi.chassis.asset.tag: Chassis Asset Tag
dmi.chassis.type: 31
dmi.chassis.vendor: HP
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnInsyde:bvrF.32:bd11/08/2018:svnHP:pnHPPavilionx360Convertible14-cd0xxx:pvrType1ProductConfigId:rvnHP:rn8486:rvr72.23:cvnHP:ct31:cvrChassisVersion:
dmi.product.family: 103C_5335KV HP Pavilion
dmi.product.name: HP Pavilion x360 Convertible 14-cd0xxx
dmi.product.sku: 3PX63LA#ABM
dmi.product.version: Type1ProductConfigId
dmi.sys.vendor: HP

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


** Tags: amd64 apport-bug eoan package-from-proposed

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

Title:
  Bluetooth: hci0: inquiry failed: status 0x0c

Status in linux package in Ubuntu:
  New

Bug description:
  dmesg:
  [   64.142848] Bluetooth: hci0: inquiry failed: status 0x0c

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: linux-image-5.2.0-8-generic 5.2.0-8.9
  ProcVersionSignature: Ubuntu 5.2.0-8.9-generic 5.2.0
  Uname: Linux 5.2.0-8-generic x86_64
  ApportVersion: 2.20.11-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  caravena   2036 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jul 12 15:03:07 2019
  HibernationDevice: RESUME=UUID=efcf081f-0bb0-4907-b78c-1299aa4aee57
  InstallationDate: Installed on 2018-12-02 (222 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: HP HP Pavilion x360 Convertible 14-cd0xxx
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.2.0-8-generic 
root=UUID=28bdadba-133c-4f5b-a5c9-b06993ea7ce2 ro rootflags=subvol=@ quiet 
splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-5.2.0-8-generic N/A
   linux-backports-modules-5.2.0-8-generic  N/A
   linux-firmware   1.180
  SourcePackage: linux
  UpgradeStatus: Upgraded to eoan on 2018-12-02 (221 days ago)
  dmi.bios.date: 11/08/2018
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.32
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 8486
  dmi.board.vendor: HP
  dmi.board.version: 72.23
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.32:bd11/08/2018:svnHP:pnHPPavilionx360Convertible14-cd0xxx:pvrType1ProductConfigId:rvnHP:rn8486:rvr72.23:cvnHP:ct31:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Pavilion
  dmi.product.name: HP Pavilion x360 Convertible 14-cd0xxx
  dmi.product.sku: 3PX63LA#ABM
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP

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

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

[Kernel-packages] [Bug 1836410] [NEW] lis3lv02d: unknown sensor type 0x0

[El jinete sin cabeza]

Public bug reported:

dmesg:
[4.135296] lis3lv02d: unknown sensor type 0x0

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: linux-image-5.2.0-8-generic 5.2.0-8.9
ProcVersionSignature: Ubuntu 5.2.0-8.9-generic 5.2.0
Uname: Linux 5.2.0-8-generic x86_64
ApportVersion: 2.20.11-0ubuntu3
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  caravena   2036 F pulseaudio
CurrentDesktop: ubuntu:GNOME
Date: Fri Jul 12 14:53:45 2019
HibernationDevice: RESUME=UUID=efcf081f-0bb0-4907-b78c-1299aa4aee57
InstallationDate: Installed on 2018-12-02 (222 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
MachineType: HP HP Pavilion x360 Convertible 14-cd0xxx
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.2.0-8-generic 
root=UUID=28bdadba-133c-4f5b-a5c9-b06993ea7ce2 ro rootflags=subvol=@ quiet 
splash vt.handoff=1
RelatedPackageVersions:
 linux-restricted-modules-5.2.0-8-generic N/A
 linux-backports-modules-5.2.0-8-generic  N/A
 linux-firmware   1.180
SourcePackage: linux
UpgradeStatus: Upgraded to eoan on 2018-12-02 (221 days ago)
dmi.bios.date: 11/08/2018
dmi.bios.vendor: Insyde
dmi.bios.version: F.32
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: 8486
dmi.board.vendor: HP
dmi.board.version: 72.23
dmi.chassis.asset.tag: Chassis Asset Tag
dmi.chassis.type: 31
dmi.chassis.vendor: HP
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnInsyde:bvrF.32:bd11/08/2018:svnHP:pnHPPavilionx360Convertible14-cd0xxx:pvrType1ProductConfigId:rvnHP:rn8486:rvr72.23:cvnHP:ct31:cvrChassisVersion:
dmi.product.family: 103C_5335KV HP Pavilion
dmi.product.name: HP Pavilion x360 Convertible 14-cd0xxx
dmi.product.sku: 3PX63LA#ABM
dmi.product.version: Type1ProductConfigId
dmi.sys.vendor: HP

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


** Tags: amd64 apport-bug eoan package-from-proposed

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

Title:
  lis3lv02d: unknown sensor type 0x0

Status in linux package in Ubuntu:
  New

Bug description:
  dmesg:
  [4.135296] lis3lv02d: unknown sensor type 0x0

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: linux-image-5.2.0-8-generic 5.2.0-8.9
  ProcVersionSignature: Ubuntu 5.2.0-8.9-generic 5.2.0
  Uname: Linux 5.2.0-8-generic x86_64
  ApportVersion: 2.20.11-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  caravena   2036 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jul 12 14:53:45 2019
  HibernationDevice: RESUME=UUID=efcf081f-0bb0-4907-b78c-1299aa4aee57
  InstallationDate: Installed on 2018-12-02 (222 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: HP HP Pavilion x360 Convertible 14-cd0xxx
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.2.0-8-generic 
root=UUID=28bdadba-133c-4f5b-a5c9-b06993ea7ce2 ro rootflags=subvol=@ quiet 
splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-5.2.0-8-generic N/A
   linux-backports-modules-5.2.0-8-generic  N/A
   linux-firmware   1.180
  SourcePackage: linux
  UpgradeStatus: Upgraded to eoan on 2018-12-02 (221 days ago)
  dmi.bios.date: 11/08/2018
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.32
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 8486
  dmi.board.vendor: HP
  dmi.board.version: 72.23
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.32:bd11/08/2018:svnHP:pnHPPavilionx360Convertible14-cd0xxx:pvrType1ProductConfigId:rvnHP:rn8486:rvr72.23:cvnHP:ct31:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Pavilion
  dmi.product.name: HP Pavilion x360 Convertible 14-cd0xxx
  dmi.product.sku: 3PX63LA#ABM
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP

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

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

[Kernel-packages] [Bug 1835434] Re: linux-azure: 5.0.0-1012.12 -proposed tracker

[Joshua R. Poulson]

** Changed in: kernel-sru-workflow/stakeholder-signoff
   Status: Confirmed => Fix Released

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

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

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

  backports: bug 1835882 (bionic/linux-azure-edge)

  -- swm properties --
  kernel-stable-master-bug: 1834902
  phase: Ready for Testing
  phase-changed: Wednesday, 10. July 2019 23:36 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
regression-testing: Ongoing -- testing in progress
stakeholder-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  variant: debs

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

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

[Kernel-packages] [Bug 1834950] Re: linux-azure: 4.15.0-1051.56 -proposed tracker

[Joshua R. Poulson]

** Changed in: kernel-sru-workflow/stakeholder-signoff
   Status: Confirmed => Fix Released

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

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

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow stakeholder-signoff series:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
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 --
  boot-testing-requested: true
  kernel-stable-master-bug: 1834954
  phase: Ready for Testing
  phase-changed: Wednesday, 10. July 2019 23:42 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
regression-testing: Ongoing -- testing in progress
stakeholder-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  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 1834948] Re: linux-azure: 4.15.0-1051.56~14.04.1 -proposed tracker

[Joshua R. Poulson]

** Changed in: kernel-sru-workflow/stakeholder-signoff
   Status: Confirmed => Fix Released

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

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

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

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

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

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1834950
  phase: Ready for Testing
  phase-changed: Wednesday, 10. July 2019 23:45 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
regression-testing: Ongoing -- testing in progress
stakeholder-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  variant: debs

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

-- 
Mailing list: https://launchpad.net/~kernel-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.60 -proposed tracker

[Ubuntu Kernel Bot]

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

** 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 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), bug 1836172 (linux-oem)
  
  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
  phase: Testing
- phase-changed: Wednesday, 03. July 2019 13:05 UTC
+ phase-changed: Friday, 12. July 2019 17:33 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Stalled -- testing FAILED
certification-testing: Ongoing -- testing in progress
regression-testing: Ongoing -- testing in progress
verification-testing: Ongoing -- testing in progress
  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.60 -proposed tracker

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

  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 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), bug 1836172 (linux-oem)

  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
  phase: Testing
  phase-changed: Friday, 12. July 2019 17:33 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Stalled -- testing FAILED
certification-testing: Ongoing -- testing in progress
regression-testing: Ongoing -- testing in progress
verification-testing: Ongoing -- testing in progress
  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 1834918] Re: linux: 4.4.0-155.182 -proposed tracker

[Ubuntu Kernel Bot]

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  backports: bug 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 --
  boot-testing-requested: true
  bugs-spammed: true
- phase: Testing
- phase-changed: Wednesday, 03. July 2019 11:05 UTC
+ phase: Ready for Testing
+ phase-changed: Friday, 12. July 2019 17:21 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   automated-testing: Stalled -- testing FAILED
+   automated-testing: Ongoing -- testing in progress
certification-testing: Ongoing -- testing in progress
verification-testing: Ongoing -- testing in progress
  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:
  Confirmed
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  New

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

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

  backports: bug 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 --
  boot-testing-requested: true
  bugs-spammed: true
  phase: Ready for Testing
  phase-changed: Friday, 12. July 2019 17:21 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Ongoing -- testing in progress
certification-testing: Ongoing -- testing in progress
verification-testing: Ongoing -- testing in progress
  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 1834954] Re: linux: 4.15.0-55.60 -proposed tracker

[Ubuntu Kernel Bot]

** Changed in: kernel-sru-workflow/automated-testing
   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/1834954

Title:
  linux: 4.15.0-55.60 -proposed tracker

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

  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 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), bug 1836172 (linux-oem)

  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
  phase: Testing
  phase-changed: Friday, 12. July 2019 17:33 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Stalled -- testing FAILED
certification-testing: Ongoing -- testing in progress
regression-testing: Ongoing -- testing in progress
verification-testing: Ongoing -- testing in progress
  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 1834904] Re: linux: 4.18.0-26.27 -proposed tracker

[Ubuntu Kernel Bot]

** Changed in: kernel-sru-workflow/automated-testing
   Status: Incomplete => 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 1834880 (linux-raspi2), bug 1834883 (linux-aws), bug
  1834899 (linux-gcp), bug 1834901 (linux-kvm), bug 1835438 (linux-azure)
  
  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
- phase: Testing
- phase-changed: Wednesday, 03. July 2019 13:02 UTC
+ phase: Ready for Testing
+ phase-changed: Friday, 12. July 2019 17:16 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   automated-testing: Stalled -- testing FAILED
+   automated-testing: Ongoing -- testing in progress
  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:
  Confirmed
Status in Kernel SRU Workflow certification-testing series:
  Fix Released
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Invalid
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  Invalid
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

  derivatives: bug 1834880 (linux-raspi2), bug 1834883 (linux-aws), bug
  1834899 (linux-gcp), bug 1834901 (linux-kvm), bug 1835438 (linux-
  azure)

  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
  phase: Ready for Testing
  phase-changed: Friday, 12. July 2019 17:16 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Ongoing -- testing in progress
  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 1834918] Re: linux: 4.4.0-155.182 -proposed tracker

[Ubuntu Kernel Bot]

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

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

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

  backports: bug 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 --
  boot-testing-requested: true
  bugs-spammed: true
  phase: Ready for Testing
  phase-changed: Friday, 12. July 2019 17:21 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Ongoing -- testing in progress
certification-testing: Ongoing -- testing in progress
verification-testing: Ongoing -- testing in progress
  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

[Ubuntu Kernel Bot]

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  backports: bug 1835388 (bionic/linux-hwe), bug 1836161 (bionic/linux-oem-osp1)
  derivatives: bug 1834884 (linux-raspi2), bug 1834886 (linux-aws), bug 1834891 
(linux-gcp), bug 1834892 (linux-kvm), bug 1834894 (linux-snapdragon), bug 
1835434 (linux-azure)
  
  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
- phase: Testing
- phase-changed: Wednesday, 03. July 2019 11:01 UTC
+ phase: Ready for Testing
+ phase-changed: Friday, 12. July 2019 17:10 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   automated-testing: Stalled -- testing FAILED
+   automated-testing: Ongoing -- testing in progress
certification-testing: Ongoing -- testing in progress
regression-testing: Ongoing -- testing in progress
verification-testing: Ongoing -- testing in progress
  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:
  Confirmed
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-lrm series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
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 1835388 (bionic/linux-hwe), bug 1836161 (bionic/linux-oem-osp1)
  derivatives: bug 1834884 (linux-raspi2), bug 1834886 (linux-aws), bug 1834891 
(linux-gcp), bug 1834892 (linux-kvm), bug 1834894 (linux-snapdragon), bug 
1835434 (linux-azure)

  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
  phase: Ready for Testing
  phase-changed: Friday, 12. July 2019 17:10 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Ongoing -- testing in progress
certification-testing: Ongoing -- testing in progress
regression-testing: Ongoing -- testing in progress
verification-testing: Ongoing -- testing in progress
  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

Re: [Kernel-packages] [Bug 1832087] Re: Intel WIRELESS-AC 9260 (2526:0010) Wi-Fi doesn't work on kernel > 5.0.0-16

[Philippe]

I would like to test the kernel v. 5.2 stable, but the amd64.deb files is
not disponible ?? :

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

Regards

Le mar. 9 juil. 2019 à 19:20, You-Sheng Yang <1832...@bugs.launchpad.net> a
écrit :

> Error in comment #50 should has been FIX COMMITTED but not yet released.
> A new release pending in https://code.launchpad.net/~canonical-hwe-
> team/+git/backport-iwlwifi-dkms/+merge/369867
> 
> already, so you can get it
> from https://code.launchpad.net/~vicamo/+archive/ubuntu/ci-test-only .
> Sorry for the inconvenience.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1832087
>
> Title:
>   Intel WIRELESS-AC 9260 (2526:0010) Wi-Fi doesn't work on kernel >
>   5.0.0-16
>
> Status in linux package in Ubuntu:
>   Confirmed
>
> Bug description:
>   Kernel 5.0.0-16 > Bluetooth on INTEL WIRELESS-AC 9260 NOT WORK !!??
>
>   I can not use my mouse, my keyboard and external speakers that all
>   need bluetooth.
>
>   My laptop has few usb ports, I am dependent on bluetooth with him...
>
>   Unsolved problem from Kernel 5.0.0-15
>
>   https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1829497
>   ---
>   ProblemType: Bug
>   ApportVersion: 2.20.9-0ubuntu7.6
>   Architecture: amd64
>   AudioDevicesInUse:
>USERPID ACCESS COMMAND
>/dev/snd/controlC0:  philippe   1646 F pulseaudio
>   CurrentDesktop: X-Cinnamon
>   DistroRelease: Linux Mint 19.1
>   InstallationDate: Installed on 2018-11-13 (206 days ago)
>   InstallationMedia: Linux Mint 19 "Tara" - Release amd64 20180717
>   Lsusb:
>Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
>Bus 001 Device 003: ID 27c6:5395
>Bus 001 Device 002: ID 8087:0025 Intel Corp.
>Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
>   MachineType: Dell Inc. XPS 15 9570
>   Package: linux (not installed)
>   ProcFB: 0 inteldrmfb
>   ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-16-generic
> root=UUID=1c90898a-7750-4a75-967f-b653a0db22aa ro quiet splash vt.handoff=1
>   ProcVersionSignature: Ubuntu 5.0.0-16.17~18.04.1-generic 5.0.8
>   RelatedPackageVersions:
>linux-restricted-modules-5.0.0-16-generic N/A
>linux-backports-modules-5.0.0-16-generic  N/A
>linux-firmware1.173.6
>   Tags:  tessa
>   Uname: Linux 5.0.0-16-generic x86_64
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
>   _MarkForUpload: True
>   dmi.bios.date: 04/26/2019
>   dmi.bios.vendor: Dell Inc.
>   dmi.bios.version: 1.10.1
>   dmi.board.name: 0D0T05
>   dmi.board.vendor: Dell Inc.
>   dmi.board.version: A00
>   dmi.chassis.type: 10
>   dmi.chassis.vendor: Dell Inc.
>   dmi.modalias:
> dmi:bvnDellInc.:bvr1.10.1:bd04/26/2019:svnDellInc.:pnXPS159570:pvr:rvnDellInc.:rn0D0T05:rvrA00:cvnDellInc.:ct10:cvr:
>   dmi.product.family: XPS
>   dmi.product.name: XPS 15 9570
>   dmi.product.sku: 087C
>   dmi.sys.vendor: Dell Inc.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832087/+subscriptions
>

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

Title:
  Intel WIRELESS-AC 9260 (2526:0010) Wi-Fi doesn't work on kernel >
  5.0.0-16

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Kernel 5.0.0-16 > Bluetooth on INTEL WIRELESS-AC 9260 NOT WORK !!??

  I can not use my mouse, my keyboard and external speakers that all
  need bluetooth.

  My laptop has few usb ports, I am dependent on bluetooth with him...

  Unsolved problem from Kernel 5.0.0-15

  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1829497
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  philippe   1646 F pulseaudio
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 19.1
  InstallationDate: Installed on 2018-11-13 (206 days ago)
  InstallationMedia: Linux Mint 19 "Tara" - Release amd64 20180717
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 27c6:5395  
   Bus 001 Device 002: ID 8087:0025 Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 15 9570
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-16-generic 
root=UUID=1c90898a-7750-4a75-967f-b653a0db22aa ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.0.0-16.17~18.04.1-generic 5.0.8
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-16-generic N/A
   linux-backports-modules-5.0.0-16-generic  N/A
   linux-firmware 

[Kernel-packages] [Bug 1832087] Re: Intel WIRELESS-AC 9260 (2526:0010) Wi-Fi doesn't work on kernel > 5.0.0-16

[Philippe]

I would like to test directly the kernel v. 5.2 stable, but the
amd64.deb files is not disponible ?? :

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

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

Title:
  Intel WIRELESS-AC 9260 (2526:0010) Wi-Fi doesn't work on kernel >
  5.0.0-16

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Kernel 5.0.0-16 > Bluetooth on INTEL WIRELESS-AC 9260 NOT WORK !!??

  I can not use my mouse, my keyboard and external speakers that all
  need bluetooth.

  My laptop has few usb ports, I am dependent on bluetooth with him...

  Unsolved problem from Kernel 5.0.0-15

  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1829497
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  philippe   1646 F pulseaudio
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 19.1
  InstallationDate: Installed on 2018-11-13 (206 days ago)
  InstallationMedia: Linux Mint 19 "Tara" - Release amd64 20180717
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 27c6:5395  
   Bus 001 Device 002: ID 8087:0025 Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 15 9570
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-16-generic 
root=UUID=1c90898a-7750-4a75-967f-b653a0db22aa ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.0.0-16.17~18.04.1-generic 5.0.8
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-16-generic N/A
   linux-backports-modules-5.0.0-16-generic  N/A
   linux-firmware1.173.6
  Tags:  tessa
  Uname: Linux 5.0.0-16-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/26/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.10.1
  dmi.board.name: 0D0T05
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.10.1:bd04/26/2019:svnDellInc.:pnXPS159570:pvr:rvnDellInc.:rn0D0T05:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 15 9570
  dmi.product.sku: 087C
  dmi.sys.vendor: Dell Inc.

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

-- 
Mailing list: https://launchpad.net/~kernel-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

[Ubuntu Kernel Bot]

** Changed in: kernel-sru-workflow/automated-testing
   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/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:
  Confirmed
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-lrm series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
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 1835388 (bionic/linux-hwe), bug 1836161 (bionic/linux-oem-osp1)
  derivatives: bug 1834884 (linux-raspi2), bug 1834886 (linux-aws), bug 1834891 
(linux-gcp), bug 1834892 (linux-kvm), bug 1834894 (linux-snapdragon), bug 
1835434 (linux-azure)

  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
  phase: Ready for Testing
  phase-changed: Friday, 12. July 2019 17:10 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Ongoing -- testing in progress
certification-testing: Ongoing -- testing in progress
regression-testing: Ongoing -- testing in progress
verification-testing: Ongoing -- testing in progress
  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 1685937] Re: HID 1018:1006 Touchpad does not work

[Ondřej Žára]

It looks like I am currently hit by the very same issue: bought a
chinese tablet, its keyboard+touchpad is detected as 1018:1006 and the
touchpad is not working (only sending garbage on 3-finger gestures).

May I ask about the status of the discussed patch?

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

Title:
  HID 1018:1006 Touchpad does not work

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The touchpad does not work. hid_multitouch interprets gestures as weird stuff 
-> opens search, types letters. If I didnt overlook anything the touchpad 
position does not show in any of the /dev/input files.. Any help would be 
appreciated.
  edit:  its on a trekstor surfbook w2.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-19-generic 4.10.0-19.21 [modified: 
boot/vmlinuz-4.10.0-19-generic]
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: Unity:Unity7
  Date: Mon Apr 24 23:05:18 2017
  MachineType: TrekStor SurfBook W2
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-19-generic.efi.signed 
root=UUID=78342794-9ef5-4a63-9b1e-040a63fd644b ro i8042.nopnp quiet splash 
vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-19-generic N/A
   linux-backports-modules-4.10.0-19-generic  N/A
   linux-firmware 1.164
  RfKill:

  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/22/2016
  dmi.bios.version: SB14464-2_BIOS_V2.1.1
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: CherryTrail CR
  dmi.board.vendor: TS_I-Net
  dmi.board.version: Type2 - Board Version
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvn:bvrSB14464-2_BIOS_V2.1.1:bd11/22/2016:svnTrekStor:pnSurfBookW2:pvrType1-TBDbyOEM:rvnTS_I-Net:rnCherryTrailCR:rvrType2-BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion:
  dmi.product.name: SurfBook W2
  dmi.product.version: Type1 - TBD by OEM
  dmi.sys.vendor: TrekStor

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

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

[Kernel-packages] [Bug 1834915] Re: linux-fips: 4.4.0-1014.18 -proposed tracker

[Ubuntu Kernel Bot]

** 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
  
  -- swm properties --
  kernel-stable-master-bug: 1834918
- phase: Packaging
- phase-changed: Wednesday, 10. July 2019 13:09 UTC
+ phase: Holding before Promote to Proposed
+ phase-changed: Friday, 12. July 2019 16:09 UTC
  reason:
-   prepare-package: Pending -- package tag not yet published
-   prepare-package-meta: Pending -- package tag not yet published
-   prepare-package-signed: Pending -- package tag not yet published
promote-to-proposed: Pending -- builds not complete in ppa 
main:failed,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/1834915

Title:
  linux-fips: 4.4.0-1014.18 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
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:
  Invalid
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:
  Invalid
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

  -- swm properties --
  kernel-stable-master-bug: 1834918
  phase: Holding before Promote to Proposed
  phase-changed: Friday, 12. July 2019 16:09 UTC
  reason:
promote-to-proposed: Pending -- builds not complete in ppa 
main:failed,meta:building,signed:building
  variant: debs

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

-- 
Mailing list: https://launchpad.net/~kernel-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: 4.15.0-1012.13 -proposed tracker

[Ubuntu Kernel Bot]

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

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

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

** Tags added: block-proposed-bionic

** Tags added: block-proposed

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
+ boot-testing-requested: true
  kernel-stable-master-bug: 1834954
- phase: Packaging
- phase-changed: Tuesday, 09. July 2019 15:42 UTC
+ phase: Ready for Promote to Proposed
+ phase-changed: Friday, 12. July 2019 16:12 UTC
  reason:
-   prepare-package: Pending -- package tag not yet published
-   prepare-package-signed: Pending -- package tag not yet published
-   promote-to-proposed: Pending -- source package tags missing
+   promote-to-proposed: Pending -- ready for review
  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: 4.15.0-1012.13 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-signing-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-proposed series:
  Confirmed
Status in Kernel SRU Workflow promote-to-security series:
  Invalid
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  Invalid
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 --
  boot-testing-requested: true
  kernel-stable-master-bug: 1834954
  phase: Ready for Promote to Proposed
  phase-changed: Friday, 12. July 2019 16:12 UTC
  reason:
promote-to-proposed: Pending -- ready for review
  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 1835185] Re: High write iops after kernel upgrade

[Igor Naumov]

Tested 4.15.0-56-generic #60~lp1835185 - everything is good

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

Title:
  High write iops after kernel upgrade

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu server 18.04.2
  There is a problem with the latest system updates (kernel version 
4.15.0-54-generic # 58-Ubuntu SMP).
  After upgrading from version 4.15.0-36-generic # 39-Ubuntu SMP
  we observe at the same software configuration an increased load on the disk 
(write) - MySQL previously loaded the disk at 20-50 mB/s, after the update it 
started loading at 150-250 mB/s. On the server we have cronjobs with PHP 
writing stuff to the DB.
  MySQL configuration and package version was not changed, the load profile is 
the same and does not depend on external users (OLAP DB)

  If we boot into the old kernel version (4.15.0-36), the problem disappears. 
Also tested kernels:
  4.15.0-52 - problem persists
  4.18.0-25 (hwe) - problem persists, load became more 200-250 mB/s

  Attaching list of updated packages (apt/history.log) and other info.

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

-- 
Mailing list: https://launchpad.net/~kernel-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: 4.15.0-1012.13 -proposed tracker

[Ubuntu Kernel Bot]

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  kernel-stable-master-bug: 1834954
  phase: Packaging
  phase-changed: Tuesday, 09. July 2019 15:42 UTC
  reason:
prepare-package: Pending -- package tag not yet published
prepare-package-signed: Pending -- package tag not yet published
-   promote-to-proposed: Pending -- builds not complete in ppa 
meta:queued,signed:queued
+   promote-to-proposed: Pending -- source package tags missing
  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: 4.15.0-1012.13 -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:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  In Progress
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:
  Invalid
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:
  Invalid
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: Packaging
  phase-changed: Tuesday, 09. July 2019 15:42 UTC
  reason:
prepare-package: Pending -- package tag not yet published
prepare-package-signed: Pending -- package tag not yet published
promote-to-proposed: Pending -- source package tags missing
  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 1836373] Re: Mainline builds for 5.1 and 5.2 failing for amd64 and i386

[Chris Plummer]

** Attachment added: "5.2 Build Log"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1836373/+attachment/5276696/+files/BUILD.LOG.amd64

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

Title:
  Mainline builds for 5.1 and 5.2 failing for amd64 and i386

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.2/BUILD.LOG.amd64

  /home/kernel/COD/linux/include/linux/compiler.h: In function 
'__read_once_size':
  /home/kernel/COD/linux/include/linux/compiler.h:193:1: error: 
'-mindirect-branch' and '-fcf-protection' are not compatible

  The build has multiple errors saying '-mindirect-branch' and '-fcf-
  protection' are not compatible.  This currently affects the 5.2 kernel
  build and the 5.1.17 kernel build.

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

-- 
Mailing list: https://launchpad.net/~kernel-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: 4.15.0-1012.13 -proposed tracker

[Ubuntu Kernel Bot]

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  kernel-stable-master-bug: 1834954
  phase: Packaging
  phase-changed: Tuesday, 09. July 2019 15:42 UTC
  reason:
prepare-package: Pending -- package tag not yet published
prepare-package-signed: Pending -- package tag not yet published
-   promote-to-proposed: Pending -- builds not complete in ppa 
meta:failed,signed:retry-needed
+   promote-to-proposed: Pending -- builds not complete in ppa 
meta:queued,signed:queued
  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: 4.15.0-1012.13 -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:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  In Progress
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:
  Invalid
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:
  Invalid
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: Packaging
  phase-changed: Tuesday, 09. July 2019 15:42 UTC
  reason:
prepare-package: Pending -- package tag not yet published
prepare-package-signed: Pending -- package tag not yet published
promote-to-proposed: Pending -- builds not complete in ppa 
meta:queued,signed:queued
  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 1835112] Re: linux-fips: 4.15.0-1011.12 -proposed tracker

[Ubuntu Kernel Bot]

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

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
    https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1833987
  phase: Ready for Testing
  phase-changed: Monday, 08. July 2019 10:04 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Ongoing -- testing in progress
-   regression-testing: Ongoing -- testing in progress
  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/1835112

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

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Confirmed
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-signing-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  Invalid
Status in Kernel SRU Workflow promote-to-updates series:
  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: Ready for Testing
  phase-changed: Monday, 08. July 2019 10:04 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Ongoing -- testing in progress
  variant: debs

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

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

[Kernel-packages] [Bug 1835112] Re: linux-fips: 4.15.0-1011.12 -proposed tracker

[Sean Feole]

** Tags added: regression-testing-passed

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

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

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Confirmed
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-signing-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  Invalid
Status in Kernel SRU Workflow promote-to-updates series:
  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: Ready for Testing
  phase-changed: Monday, 08. July 2019 10:04 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Ongoing -- testing in progress
  variant: debs

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

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

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

[Ubuntu Kernel Bot]

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

apport-collect 1836373

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

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

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

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

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

Title:
  Mainline builds for 5.1 and 5.2 failing for amd64 and i386

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.2/BUILD.LOG.amd64

  /home/kernel/COD/linux/include/linux/compiler.h: In function 
'__read_once_size':
  /home/kernel/COD/linux/include/linux/compiler.h:193:1: error: 
'-mindirect-branch' and '-fcf-protection' are not compatible

  The build has multiple errors saying '-mindirect-branch' and '-fcf-
  protection' are not compatible.  This currently affects the 5.2 kernel
  build and the 5.1.17 kernel build.

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

-- 
Mailing list: https://launchpad.net/~kernel-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: 4.15.0-1012.13 -proposed tracker

[Ubuntu Kernel Bot]

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  kernel-stable-master-bug: 1834954
  phase: Packaging
  phase-changed: Tuesday, 09. July 2019 15:42 UTC
  reason:
prepare-package: Pending -- package tag not yet published
prepare-package-signed: Pending -- package tag not yet published
-   promote-to-proposed: Pending -- builds not complete in ppa 
meta:failed,signed:building
+   promote-to-proposed: Pending -- builds not complete in ppa 
meta:failed,signed:retry-needed
  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: 4.15.0-1012.13 -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:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  In Progress
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:
  Invalid
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:
  Invalid
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: Packaging
  phase-changed: Tuesday, 09. July 2019 15:42 UTC
  reason:
prepare-package: Pending -- package tag not yet published
prepare-package-signed: Pending -- package tag not yet published
promote-to-proposed: Pending -- builds not complete in ppa 
meta:failed,signed:retry-needed
  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 1836372] Re: Update firmware in nic-firmware udeb for 5.0 hwe kernel

[Seth Forshee]

** Description changed:

  SRU Justification
  
  Impact: Recent updates to linux-firmware means that there are new and
  updated firmware files relevant to the 5.0 hwe kernel from disco. Adding
- these files may give a better install experience for the 18.04.3
- release.
+ these files to give a better install experience for the 18.04.3 release.
  
  Fix: Add the new firmware files to the nic-firmware udeb.
  
  Test Case: Confirm that the new files are present in the nic-firmware
  udeb.
  
  Regression Potential: New firmware versions could contain regressions.
  These versions have already been released into bionic with no reported
  regressions though, and are known to fix actual problems, so the benefit
  seems to outweigh the potential risk.

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

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

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

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

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

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

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

Title:
  Update firmware in nic-firmware udeb for 5.0 hwe kernel

Status in linux-firmware package in Ubuntu:
  Invalid
Status in linux-firmware source package in Bionic:
  In Progress

Bug description:
  SRU Justification

  Impact: Recent updates to linux-firmware means that there are new and
  updated firmware files relevant to the 5.0 hwe kernel from disco.
  Adding these files to give a better install experience for the 18.04.3
  release.

  Fix: Add the new firmware files to the nic-firmware udeb.

  Test Case: Confirm that the new files are present in the nic-firmware
  udeb.

  Regression Potential: New firmware versions could contain regressions.
  These versions have already been released into bionic with no reported
  regressions though, and are known to fix actual problems, so the
  benefit seems to outweigh the potential risk.

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

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

[Kernel-packages] [Bug 1836202] Re: bionic/linux-gke-5.0: 5.0.0-1011.11~18.04.1 -proposed tracker

[Ubuntu Kernel Bot]

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

** Tags added: block-proposed-bionic

** Tags added: block-proposed

** 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 1836201 (gke-kernel)
  
  -- swm properties --
+ boot-testing-requested: true
  kernel-stable-master-bug: 1834891
- phase: Holding before Promote to Proposed
- phase-changed: Friday, 12. July 2019 13:54 UTC
+ phase: Ready for Promote to Proposed
+ phase-changed: Friday, 12. July 2019 14:13 UTC
  reason:
-   promote-to-proposed: Ongoing -- builds not complete in ppa meta:building
+   promote-to-proposed: Pending -- ready for review
  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/1836202

Title:
  bionic/linux-gke-5.0: 5.0.0-1011.11~18.04.1 -proposed tracker

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

  derivatives: bug 1836201 (gke-kernel)

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1834891
  phase: Ready for Promote to Proposed
  phase-changed: Friday, 12. July 2019 14:13 UTC
  reason:
promote-to-proposed: Pending -- ready for review
  variant: debs

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

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

[Kernel-packages] [Bug 1836373] [NEW] Mainline builds for 5.1 and 5.2 failing for amd64 and i386

[Chris Plummer]

Public bug reported:

https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.2/BUILD.LOG.amd64

/home/kernel/COD/linux/include/linux/compiler.h: In function '__read_once_size':
/home/kernel/COD/linux/include/linux/compiler.h:193:1: error: 
'-mindirect-branch' and '-fcf-protection' are not compatible

The build has multiple errors saying '-mindirect-branch' and '-fcf-
protection' are not compatible.  This currently affects the 5.2 kernel
build and the 5.1.17 kernel build.

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

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

Title:
  Mainline builds for 5.1 and 5.2 failing for amd64 and i386

Status in linux package in Ubuntu:
  New

Bug description:
  https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.2/BUILD.LOG.amd64

  /home/kernel/COD/linux/include/linux/compiler.h: In function 
'__read_once_size':
  /home/kernel/COD/linux/include/linux/compiler.h:193:1: error: 
'-mindirect-branch' and '-fcf-protection' are not compatible

  The build has multiple errors saying '-mindirect-branch' and '-fcf-
  protection' are not compatible.  This currently affects the 5.2 kernel
  build and the 5.1.17 kernel build.

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

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

[Kernel-packages] [Bug 1836372] [NEW] Update firmware in nic-firmware udeb for 5.0 hwe kernel

[Seth Forshee]

Public bug reported:

SRU Justification

Impact: Recent updates to linux-firmware means that there are new and
updated firmware files relevant to the 5.0 hwe kernel from disco. Adding
these files to give a better install experience for the 18.04.3 release.

Fix: Add the new firmware files to the nic-firmware udeb.

Test Case: Confirm that the new files are present in the nic-firmware
udeb.

Regression Potential: New firmware versions could contain regressions.
These versions have already been released into bionic with no reported
regressions though, and are known to fix actual problems, so the benefit
seems to outweigh the potential risk.

** Affects: linux-firmware (Ubuntu)
 Importance: Medium
 Assignee: Seth Forshee (sforshee)
 Status: In Progress

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

Title:
  Update firmware in nic-firmware udeb for 5.0 hwe kernel

Status in linux-firmware package in Ubuntu:
  In Progress

Bug description:
  SRU Justification

  Impact: Recent updates to linux-firmware means that there are new and
  updated firmware files relevant to the 5.0 hwe kernel from disco.
  Adding these files to give a better install experience for the 18.04.3
  release.

  Fix: Add the new firmware files to the nic-firmware udeb.

  Test Case: Confirm that the new files are present in the nic-firmware
  udeb.

  Regression Potential: New firmware versions could contain regressions.
  These versions have already been released into bionic with no reported
  regressions though, and are known to fix actual problems, so the
  benefit seems to outweigh the potential risk.

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

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

[Kernel-packages] [Bug 1826125] Re: Dell XPS 13 9380 flickering (Whiskey Lake)

[Bug Watch Updater]

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

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

Title:
  Dell XPS 13 9380 flickering  (Whiskey Lake)

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

Bug description:
  A brand new Dell XPS 13 9380 preinstalled with Ubuntu 18.04 flickers
  to the point of being totally unusable.

  I have upgraded since to 18.10 and 19.04 with no changes. I have tried
  several combinations of the i915 parameters fastboot, enable_rc6 and
  enable_fbc to no avail.

  Examples of flickering are here:
  https://photos.app.goo.gl/1PkL2HrjMBP41aML9
  https://photos.app.goo.gl/CMzmMwrCPH5wh8aw6
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm1430 F pulseaudio
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-bionic-amd64-20180608-47+italia-whl+X31
  DistroRelease: Ubuntu 19.04
  InstallationDate: Installed on 2019-04-13 (10 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20180608-09:38
  MachineType: Dell Inc. XPS 13 9380
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-1035-oem 
root=UUID=252898e9-6e96-4705-a709-2db930b7c4c7 ro quiet splash i915.fastboot=1 
i915.enable_rc6=0 vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-1035.40-oem 4.15.18
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-1035-oem N/A
   linux-backports-modules-4.15.0-1035-oem  N/A
   linux-firmware   1.178
  Tags:  disco
  Uname: Linux 4.15.0-1035-oem x86_64
  UpgradeStatus: Upgraded to disco on 2019-04-24 (0 days ago)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 02/14/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.1
  dmi.board.name: 0KTW76
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.1:bd02/14/2019:svnDellInc.:pnXPS139380:pvr:rvnDellInc.:rn0KTW76:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9380
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1836202] Re: bionic/linux-gke-5.0: 5.0.0-1011.11~18.04.1 -proposed tracker

[Ubuntu Kernel Bot]

** 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
  
  derivatives: bug 1836201 (gke-kernel)
  
  -- swm properties --
  kernel-stable-master-bug: 1834891
- phase: Packaging
- phase-changed: Thursday, 11. July 2019 14:43 UTC
+ phase: Holding before Promote to Proposed
+ phase-changed: Friday, 12. July 2019 13:54 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
  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/1836202

Title:
  bionic/linux-gke-5.0: 5.0.0-1011.11~18.04.1 -proposed tracker

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

  derivatives: bug 1836201 (gke-kernel)

  -- swm properties --
  kernel-stable-master-bug: 1834891
  phase: Holding before Promote to Proposed
  phase-changed: Friday, 12. July 2019 13:54 UTC
  reason:
promote-to-proposed: Ongoing -- builds not complete in ppa meta:building
  variant: debs

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

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

[Kernel-packages] [Bug 1826125]

[Ville-syrjala-e]

Created attachment 144765
[PATCH] drm/i915: Try to use fast+narrow link on eDP again and fall  back to 
the old max strategy on failure

Here's an attempt at fixing this without horribly breaking a bunch of
other eDP panels. Would appreciate if people can test this.

Also available here in git form:
git://github.com/vsyrjala/linux.git dp_retry_max_vs_optim

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

Title:
  Dell XPS 13 9380 flickering  (Whiskey Lake)

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

Bug description:
  A brand new Dell XPS 13 9380 preinstalled with Ubuntu 18.04 flickers
  to the point of being totally unusable.

  I have upgraded since to 18.10 and 19.04 with no changes. I have tried
  several combinations of the i915 parameters fastboot, enable_rc6 and
  enable_fbc to no avail.

  Examples of flickering are here:
  https://photos.app.goo.gl/1PkL2HrjMBP41aML9
  https://photos.app.goo.gl/CMzmMwrCPH5wh8aw6
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm1430 F pulseaudio
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-bionic-amd64-20180608-47+italia-whl+X31
  DistroRelease: Ubuntu 19.04
  InstallationDate: Installed on 2019-04-13 (10 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20180608-09:38
  MachineType: Dell Inc. XPS 13 9380
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-1035-oem 
root=UUID=252898e9-6e96-4705-a709-2db930b7c4c7 ro quiet splash i915.fastboot=1 
i915.enable_rc6=0 vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-1035.40-oem 4.15.18
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-1035-oem N/A
   linux-backports-modules-4.15.0-1035-oem  N/A
   linux-firmware   1.178
  Tags:  disco
  Uname: Linux 4.15.0-1035-oem x86_64
  UpgradeStatus: Upgraded to disco on 2019-04-24 (0 days ago)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 02/14/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.1
  dmi.board.name: 0KTW76
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.1:bd02/14/2019:svnDellInc.:pnXPS139380:pvr:rvnDellInc.:rn0KTW76:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9380
  dmi.sys.vendor: Dell Inc.

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

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

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

[Ubuntu Kernel Bot]

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

apport-collect 1816702

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

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

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

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

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

Title:
  Ubuntu 19.04 - tablet pc won't wake with pen or device buttons (unless
  keyboard attached)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 19.04 QA-TEST on tablet.pc (wacom pen)
  motion computing j3400 (c2d-u9400, 4gb, intel mobile 4 series)

  The test went really well, but I noticed I couldn't wake it if left
  alone and screen dims & thus locks using tablet buttons or pen (& its
  button).

  This is [most] likely device specific & is very MINOR.

  It woke perfectly when keyboard/stand was attached, but not with the
  device's arrow keys, button, or any on screen mouse movement (using
  pen, including pen button).  If the device dimmed screen with onscreen
  keyboard no longer visible, and I couldn't wake it.

  The result was you had to connect keyboard/stand in order to wake
  device...  The track-pad on the keyboard/stand woke machine too, but
  that required keyboard to be attached.

  
  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gnome-power-manager 3.30.0-2
  ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
  Uname: Linux 4.18.0-11-generic x86_64
  ApportVersion: 2.20.10-0ubuntu19
  Architecture: amd64
  CasperVersion: 1.402
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Feb 20 07:00:51 2019
  LiveMediaBuild: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190203)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-power-manager
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1816702] Re: Ubuntu 19.04 - tablet pc won't wake with pen or device buttons (unless keyboard attached)

[Chris Guiver]

Ubuntu 19.10 QA-test
motion computing j3400 (c2d-u9400, 4gb, intel mobile 4 series)
-- notes from qa-test comments
screensaver has kicked in four times now, and both times I could stroke-up with 
pen & session resumed (not requiring keyboard).
--
I don't think I can change status to "fix-released" or "invalid" as bug was for 
19.04 (it'd require me to download & test 19.04).  It's not an issue in 19.10 
anyway.

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

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

Title:
  Ubuntu 19.04 - tablet pc won't wake with pen or device buttons (unless
  keyboard attached)

Status in linux package in Ubuntu:
  New

Bug description:
  Ubuntu 19.04 QA-TEST on tablet.pc (wacom pen)
  motion computing j3400 (c2d-u9400, 4gb, intel mobile 4 series)

  The test went really well, but I noticed I couldn't wake it if left
  alone and screen dims & thus locks using tablet buttons or pen (& its
  button).

  This is [most] likely device specific & is very MINOR.

  It woke perfectly when keyboard/stand was attached, but not with the
  device's arrow keys, button, or any on screen mouse movement (using
  pen, including pen button).  If the device dimmed screen with onscreen
  keyboard no longer visible, and I couldn't wake it.

  The result was you had to connect keyboard/stand in order to wake
  device...  The track-pad on the keyboard/stand woke machine too, but
  that required keyboard to be attached.

  
  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gnome-power-manager 3.30.0-2
  ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
  Uname: Linux 4.18.0-11-generic x86_64
  ApportVersion: 2.20.10-0ubuntu19
  Architecture: amd64
  CasperVersion: 1.402
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Feb 20 07:00:51 2019
  LiveMediaBuild: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190203)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-power-manager
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1836064] Re: glibc needs an update for linux-5.2 kernel headers (alpha)

[Francis Ginther]

** Tags added: id-5d275685e33375453e26b14b

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

Title:
  glibc needs an update for linux-5.2 kernel headers (alpha)

Status in glibc package in Ubuntu:
  Triaged
Status in linux package in Ubuntu:
  Fix Released
Status in glibc source package in Eoan:
  Triaged
Status in linux source package in Eoan:
  Fix Released

Bug description:
  as seen in 
  
https://launchpad.net/ubuntu/+source/cross-toolchain-base-ports/30ubuntu2/+build/17249410

  the c-t-b-ports package ftbfs:

  /bin/bash ../scripts/move-if-change 
/<>/glibc-2.29/build-tree/alpha-libc/gnu/lib-names.T 
/<>/glibc-2.29/build-tree/alpha-libc/gnu/lib-names.h
  touch /<>/glibc-2.29/build-tree/alpha-libc/gnu/lib-names.stmp
  if test -r 
/<>/glibc-2.29/build-tree/alpha-libc/csu/abi-tag.h.new; then mv -f 
/<>/glibc-2.29/build-tree/alpha-libc/csu/abi-tag.h.new 
/<>/glibc-2.29/build-tree/alpha-libc/csu/abi-tag.h; \
  else echo >&2 'This configuration not matched in ../abi-tags'; exit 1; fi
  In file included from :1:
  ../sysdeps/unix/sysv/linux/alpha/sysdep.h:54: error: "__NR_osf_shmat" 
redefined [-Werror]
   #define __NR_osf_shmat  209
   
  In file included from ../sysdeps/unix/sysv/linux/sys/syscall.h:24,
   from ../sysdeps/unix/sysdep.h:20,
   from ../sysdeps/unix/alpha/sysdep.h:19,
   from ../sysdeps/unix/sysv/linux/alpha/sysdep.h:29,
   from :1:
  /<>/glibc-2.29/debian/include/asm/unistd.h:8: note: this is the 
location of the previous definition
   #define __NR_osf_shmat __NR_shmat
   
  cc1: all warnings being treated as errors
  Traceback (most recent call last):
File "../scripts/gen-as-const.py", line 120, in 
  main()
File "../scripts/gen-as-const.py", line 116, in main
  consts = glibcextract.compute_c_consts(sym_data, args.cc)
File "/<>/glibc-2.29/scripts/glibcextract.py", line 62, in 
compute_c_consts
  subprocess.check_call(cmd, shell=True)
File "/usr/lib/python3.7/subprocess.py", line 347, in check_call
  raise CalledProcessError(retcode, cmd)
  subprocess.CalledProcessError: Command 'alpha-linux-gnu-gcc-8 -no-pie 
-fno-PIE -std=gnu11 -fgnu89-inline  -pipe -O2 -g -Wall -Wwrite-strings -Wundef 
-Werror -fmerge-all-constants -frounding-math -fno-stack-protector 
-Wstrict-prototypes -Wold-style-definition -fmath-errno -mlong-double-128 
-mieee -mfp-rounding-mode=d-ftls-model=initial-exec   -U_FORTIFY_SOURCE 
-isystem /<>/glibc-2.29/debian/include  -I../include 
-I/<>/glibc-2.29/build-tree/alpha-libc/csu  
-I/<>/glibc-2.29/build-tree/alpha-libc  
-I../sysdeps/unix/sysv/linux/alpha/alpha  
-I../sysdeps/unix/sysv/linux/alpha/fpu  -I../sysdeps/alpha/fpu  
-I../sysdeps/unix/sysv/linux/alpha  -I../sysdeps/alpha/nptl  
-I../sysdeps/unix/sysv/linux/wordsize-64  -I../sysdeps/ieee754/ldbl-64-128  
-I../sysdeps/ieee754/ldbl-opt  -I../sysdeps/unix/sysv/linux/include 
-I../sysdeps/unix/sysv/linux  -I../sysdeps/nptl  -I../sysdeps/pthread  
-I../sysdeps/gnu  -I../sysdeps/unix/inet  -I../sysdeps/unix/sysv  
-I../sysdeps/unix/alpha  -I../sysdeps/unix  -I../sysdeps/posix  
-I../sysdeps/alpha  -I../sysdeps/wordsize-64  -I../sysdeps/ieee754/ldbl-128  
-I../sysdeps/ieee754/dbl-64/wordsize-64  -I../sysdeps/ieee754/dbl-64  
-I../sysdeps/ieee754/flt-32  -I../sysdeps/ieee754  -I../sysdeps/generic  -I.. 
-I../libio -I. -nostdinc -isystem 
/<>/debian/tmp.alpha/usr/bin/../lib/gcc-cross/alpha-linux-gnu/8/include
 -isystem 
/<>/debian/tmp.alpha/usr/bin/../lib/gcc-cross/alpha-linux-gnu/8/include-fixed
 -isystem /<>/glibc-2.29/debian/include  -D_LIBC_REENTRANT 
-include /<>/glibc-2.29/build-tree/alpha-libc/libc-modules.h 
-DMODULE_NAME=libc -include ../include/libc-symbols.h   
-DTOP_NAMESPACE=glibc -DGEN_AS_CONST_HEADERS-MD -MP -MF 
/<>/glibc-2.29/build-tree/alpha-libc/tcb-offsets.h.dT  
-MT '/<>/glibc-2.29/build-tree/alpha-libc/tcb-offsets.h.d 
/<>/glibc-2.29/build-tree/alpha-libc/tcb-offsets.h' -S -o 
/tmp/tmpq06grbcg/test.s -x c - < /tmp/tmpq06grbcg/test.c' returned non-zero 
exit status 1.
  make[4]: *** [../Makerules:271: 
/<>/glibc-2.29/build-tree/alpha-libc/tcb-offsets.h] Error 1
  make[4]: Leaving directory '/<>/glibc-2.29/csu'
  make[3]: *** [Makefile:275: csu/subdir_lib] Error 2

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

-- 
Mailing list: https://launchpad.net/~kernel-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: 4.15.0-1012.13 -proposed tracker

[Ubuntu Kernel Bot]

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  kernel-stable-master-bug: 1834954
  phase: Packaging
  phase-changed: Tuesday, 09. July 2019 15:42 UTC
  reason:
prepare-package: Pending -- package tag not yet published
prepare-package-signed: Pending -- package tag not yet published
-   promote-to-proposed: Pending -- builds not complete in ppa 
main:queued,meta:building,signed:building
+   promote-to-proposed: Pending -- builds not complete in ppa 
meta:failed,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/1834944

Title:
  linux-fips: 4.15.0-1012.13 -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:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  In Progress
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:
  Invalid
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:
  Invalid
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: Packaging
  phase-changed: Tuesday, 09. July 2019 15:42 UTC
  reason:
prepare-package: Pending -- package tag not yet published
prepare-package-signed: Pending -- package tag not yet published
promote-to-proposed: Pending -- builds not complete in ppa 
meta:failed,signed:building
  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 1836188] Re: cpuset_exclusive in controllers from ubuntu_ltp failed on C P9

[Po-Hsu Lin]

http://lists.linux.it/pipermail/ltp/2019-July/012741.html

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

Title:
  cpuset_exclusive in controllers from ubuntu_ltp failed on C P9

Status in ubuntu-kernel-tests:
  In Progress
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Cosmic:
  Invalid

Bug description:
  This issue was only spotted on node Baltar (P9)

  This is caused by the return value in:
    $ cat /sys/devices/system/node/has_normal_memory
    0,8

  The test was trying to use do arithmetic operation with it, but didn't
  expect to get a return value with a comma in it.

  <<>>
  tag=cpuset_exclusive stime=1562844139
  cmdline="   cpuset_exclusive_test.sh"
  contacts=""
  analysis=exit
  <<>>
  incrementing stop
  /opt/ltp/testcases/bin/cpuset_exclusive_test.sh: 36: 
/opt/ltp/testcases/bin/cpuset_funcs.sh: arithmetic expression: expecting EOF: 
"0,8 + 1"
  <<>>
  initiation_status="ok"
  duration=0 termination_type=exited termination_id=2 corefile=no
  cutime=0 cstime=0
  <<>>

  Not sure if this is a test case issue, or if we should see a comma in
  /sys/devices/system/node/has_normal_memory

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.18.0-25-generic 4.18.0-25.26
  ProcVersionSignature: Ubuntu 4.18.0-25.26-generic 4.18.20
  Uname: Linux 4.18.0-25-generic ppc64le
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jul 11 10:56 seq
   crw-rw 1 root audio 116, 33 Jul 11 10:56 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.10-0ubuntu13.4
  Architecture: ppc64el
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Date: Thu Jul 11 11:25:40 2019
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0451:80ff Texas Instruments, Inc.
   Bus 001 Device 004: ID 0557:2419 ATEN International Co., Ltd
   Bus 001 Device 002: ID 0557:7000 ATEN International Co., Ltd Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  PciMultimedia:

  ProcFB: 0 astdrmfb
  ProcKernelCmdLine: root=UUID=acd1a0d7-f6fc-4130-928c-c8b11ad6e4be ro 
console=hvc0
  ProcLoadAvg: 0.74 1.52 0.74 1/1338 6264
  ProcLocks:
   1: POSIX  ADVISORY  WRITE 1805 00:17:364 0 EOF
   2: POSIX  ADVISORY  WRITE 3956 00:17:504 0 EOF
   3: FLOCK  ADVISORY  WRITE 3915 00:17:566 0 EOF
  ProcSwaps:
   Filename TypeSizeUsedPriority
   /swap.img   file 8388544 0   -2
  ProcVersion: Linux version 4.18.0-25-generic (buildd@bos02-ppc64el-009) (gcc 
version 8.3.0 (Ubuntu 8.3.0-6ubuntu1~18.10.1)) #26-Ubuntu SMP Mon Jun 24 
09:32:46 UTC 2019
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-25-generic N/A
   linux-backports-modules-4.18.0-25-generic  N/A
   linux-firmware 1.175.6
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  VarLogDump_list: total 0
  cpu_cores: Number of cores present = 40
  cpu_coreson: Number of cores online = 39
  cpu_dscr: DSCR is 16
  cpu_freq:
   min: 2.862 GHz (cpu 79)
   max: 2.945 GHz (cpu 83)
   avg: 2.903 GHz
  cpu_runmode:
   Could not retrieve current diagnostics mode,
   No kernel interface to firmware
  cpu_smt: SMT=4

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1836188/+subscriptions

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

[Kernel-packages] [Bug 1812796] Re: TRACE_syscall.ptrace_syscall_dropped in seccomp from ubuntu_kernel_selftests failed on B/C PowerPC

[Po-Hsu Lin]

** Changed in: ubuntu-kernel-tests
   Status: In Progress => Fix Released

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

Title:
  TRACE_syscall.ptrace_syscall_dropped in seccomp from
  ubuntu_kernel_selftests failed on B/C PowerPC

Status in ubuntu-kernel-tests:
  Fix Released
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:
  == SRU Justification ==
  The TRACE_syscall.ptrace_syscall_dropped test in seccomp from 
ubuntu_kernel_selftests will fail on a Power8 node with B/C kernel.

  [ RUN  ] TRACE_syscall.ptrace_syscall_dropped
  seccomp_bpf.c:1808:TRACE_syscall.ptrace_syscall_dropped:Expected 1 (1) == 
syscall(286) (18446744073709551615)
  TRACE_syscall.ptrace_syscall_dropped: Test failed at step #13
  [ FAIL ] TRACE_syscall.ptrace_syscall_dropped

  == Fix ==
  * ed5f1326 (selftests/seccomp: Enhance per-arch ptrace syscall skip tests)

  This patch can be cherry-picked into B/C, and it's already in Disco.
  The ptrace_syscall_dropped will be changed into ptrace_syscall_faked, and a 
new ptrace_syscall_errno test will be added.

  == Test ==
  Patch tested with different arch (amd64 / power8 / arm64 / i386), the new 
test will pass on them except for PowerPC.

  Although the faked (bug 1829363) and errno (bug 1829359) test will
  fail on PowerPC, it's actually helping us to nail down a real issue in
  our kernel.

  == Regression Potential ==
  Low, changes limited to the testing tool in the kernel.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-43-generic 4.15.0-43.46
  ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
  Uname: Linux 4.15.0-43-generic ppc64le
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jan 22 04:30 seq
   crw-rw 1 root audio 116, 33 Jan 22 04:30 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: ppc64el
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Date: Tue Jan 22 06:09:34 2019
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lsusb:
   Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  PciMultimedia:

  ProcFB:

  ProcKernelCmdLine: root=/dev/mapper/mpath0-part2 ro console=hvc0
  ProcLoadAvg: 0.13 0.34 0.23 1/1487 35882
  ProcSwaps:
   Filename TypeSizeUsedPriority
   /swap.img   file 8388544 0   -2
  ProcVersion: Linux version 4.15.0-43-generic (buildd@bos02-ppc64el-020) (gcc 
version 7.3.0 (Ubuntu 7.3.0-16ubuntu3)) #46-Ubuntu SMP Thu Dec 6 14:43:28 UTC 
2018
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-43-generic N/A
   linux-backports-modules-4.15.0-43-generic  N/A
   linux-firmware 1.173.3
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  VarLogDump_list: total 0
  cpu_cores: Number of cores present = 20
  cpu_coreson: Number of cores online = 20
  cpu_dscr: DSCR is 0
  cpu_freq:
   min: 3.694 GHz (cpu 152)
   max: 3.694 GHz (cpu 1)
   avg: 3.694 GHz
  cpu_runmode:
   Could not retrieve current diagnostics mode,
   No kernel interface to firmware
  cpu_smt: SMT=8

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1812796/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-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: 4.15.0-1012.13 -proposed tracker

[Ubuntu Kernel Bot]

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  kernel-stable-master-bug: 1834954
  phase: Packaging
  phase-changed: Tuesday, 09. July 2019 15:42 UTC
  reason:
prepare-package: Pending -- package tag not yet published
prepare-package-signed: Pending -- package tag not yet published
-   promote-to-proposed: Ongoing -- builds not complete in ppa 
main:building,meta:building,signed:building
+   promote-to-proposed: Pending -- builds not complete in ppa 
main:queued,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/1834944

Title:
  linux-fips: 4.15.0-1012.13 -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:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  In Progress
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:
  Invalid
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:
  Invalid
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: Packaging
  phase-changed: Tuesday, 09. July 2019 15:42 UTC
  reason:
prepare-package: Pending -- package tag not yet published
prepare-package-signed: Pending -- package tag not yet published
promote-to-proposed: Pending -- builds not complete in ppa 
main:queued,meta:building,signed:building
  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 1829258] Re: package linux-image-3.13.0-46-generic 3.13.0-46.79 failed to install/upgrade: subprocess installed post-installation script returned error exit status 17

[Apport retracing service]

** Tags removed: need-duplicate-check

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

Title:
  package linux-image-3.13.0-46-generic 3.13.0-46.79 failed to
  install/upgrade: subprocess installed post-installation script
  returned error exit status 17

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  was upgrading from version 12.04 to version 14.04 when problem
  occurred.

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-46-generic 3.13.0-46.79
  ProcVersionSignature: Ubuntu 3.13.0-170.220-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-170-generic i686
  ApportVersion: 2.14.1-0ubuntu3.29
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  james  3054 F pulseaudio
  Date: Wed May 15 06:39:53 2019
  DuplicateSignature: 
package:linux-image-3.13.0-46-generic:3.13.0-46.79:subprocess installed 
post-installation script returned error exit status 17
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 17
  HibernationDevice: RESUME=UUID=a46e9566-b234-42c1-8190-cf2faf38ac18
  InstallationDate: Installed on 2014-04-08 (1863 days ago)
  InstallationMedia: Ubuntu 12.04.4 LTS "Precise Pangolin" - Release i386 
(20140204)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: Dell Inc. Latitude D610
  PccardctlIdent:
   Socket 0:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-170-generic 
root=UUID=0af89630-e623-4dfc-82a4-e14418a93f26 ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc 2.02~beta2-9ubuntu1.17
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  Title: package linux-image-3.13.0-46-generic 3.13.0-46.79 failed to 
install/upgrade: subprocess installed post-installation script returned error 
exit status 17
  UpgradeStatus: Upgraded to trusty on 2019-05-15 (0 days ago)
  dmi.bios.date: 10/02/2005
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A06
  dmi.board.name: 0U8082
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA06:bd10/02/2005:svnDellInc.:pnLatitudeD610:pvr:rvnDellInc.:rn0U8082:rvr:cvnDellInc.:ct8:cvr:
  dmi.product.name: Latitude D610
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1833630] Re: Lenovo Yoga C930 ideapad_laptop driver rfkill switch

[Kai-Heng Feng]

Please test kernels here:
https://people.canonical.com/~khfeng/lp1833630/

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

Title:
  Lenovo Yoga C930 ideapad_laptop driver rfkill switch

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Leonvo Yoga C930 has similar issues with ideapad_laptop and rfkill switches 
to the following bugs:
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1519900
  https://bugs.launchpad.net/ubuntu/+source/linux-lts-utopic/+bug/1397021

  System info:
  sudo dmidecode | grep 'System Information' -A8
  Manufacturer: LENOVO
  Product Name: 81C4
  Version: Lenovo YOGA C930-13IKB

  Wake-up Type: Power Switch
  SKU Number: LENOVO_MT_81C4_BU_idea_FM_YOGA C930-13IKB
  Family: YOGA C930-13IKB

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

-- 
Mailing list: https://launchpad.net/~kernel-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: 4.15.0-1012.13 -proposed tracker

[Andy Whitcroft]

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

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

Title:
  linux-fips: 4.15.0-1012.13 -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:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  In Progress
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:
  Invalid
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:
  Invalid
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: Packaging
  phase-changed: Tuesday, 09. July 2019 15:42 UTC
  reason:
prepare-package: Pending -- package tag not yet published
prepare-package-signed: Pending -- package tag not yet published
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/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 1834944] Re: linux-fips: 4.15.0-1012.13 -proposed tracker

[Ubuntu Kernel Bot]

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

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

Title:
  linux-fips: 4.15.0-1012.13 -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:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  In Progress
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:
  Invalid
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:
  Invalid
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: Packaging
  phase-changed: Tuesday, 09. July 2019 15:42 UTC
  reason:
prepare-package: Pending -- package tag not yet published
prepare-package-signed: Pending -- package tag not yet published
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/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 1812796] Re: TRACE_syscall.ptrace_syscall_dropped in seccomp from ubuntu_kernel_selftests failed on B/C PowerPC

[Po-Hsu Lin]

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

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

Title:
  TRACE_syscall.ptrace_syscall_dropped in seccomp from
  ubuntu_kernel_selftests failed on B/C PowerPC

Status in ubuntu-kernel-tests:
  In Progress
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:
  == SRU Justification ==
  The TRACE_syscall.ptrace_syscall_dropped test in seccomp from 
ubuntu_kernel_selftests will fail on a Power8 node with B/C kernel.

  [ RUN  ] TRACE_syscall.ptrace_syscall_dropped
  seccomp_bpf.c:1808:TRACE_syscall.ptrace_syscall_dropped:Expected 1 (1) == 
syscall(286) (18446744073709551615)
  TRACE_syscall.ptrace_syscall_dropped: Test failed at step #13
  [ FAIL ] TRACE_syscall.ptrace_syscall_dropped

  == Fix ==
  * ed5f1326 (selftests/seccomp: Enhance per-arch ptrace syscall skip tests)

  This patch can be cherry-picked into B/C, and it's already in Disco.
  The ptrace_syscall_dropped will be changed into ptrace_syscall_faked, and a 
new ptrace_syscall_errno test will be added.

  == Test ==
  Patch tested with different arch (amd64 / power8 / arm64 / i386), the new 
test will pass on them except for PowerPC.

  Although the faked (bug 1829363) and errno (bug 1829359) test will
  fail on PowerPC, it's actually helping us to nail down a real issue in
  our kernel.

  == Regression Potential ==
  Low, changes limited to the testing tool in the kernel.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-43-generic 4.15.0-43.46
  ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
  Uname: Linux 4.15.0-43-generic ppc64le
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jan 22 04:30 seq
   crw-rw 1 root audio 116, 33 Jan 22 04:30 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: ppc64el
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Date: Tue Jan 22 06:09:34 2019
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lsusb:
   Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  PciMultimedia:

  ProcFB:

  ProcKernelCmdLine: root=/dev/mapper/mpath0-part2 ro console=hvc0
  ProcLoadAvg: 0.13 0.34 0.23 1/1487 35882
  ProcSwaps:
   Filename TypeSizeUsedPriority
   /swap.img   file 8388544 0   -2
  ProcVersion: Linux version 4.15.0-43-generic (buildd@bos02-ppc64el-020) (gcc 
version 7.3.0 (Ubuntu 7.3.0-16ubuntu3)) #46-Ubuntu SMP Thu Dec 6 14:43:28 UTC 
2018
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-43-generic N/A
   linux-backports-modules-4.15.0-43-generic  N/A
   linux-firmware 1.173.3
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  VarLogDump_list: total 0
  cpu_cores: Number of cores present = 20
  cpu_coreson: Number of cores online = 20
  cpu_dscr: DSCR is 0
  cpu_freq:
   min: 3.694 GHz (cpu 152)
   max: 3.694 GHz (cpu 1)
   avg: 3.694 GHz
  cpu_runmode:
   Could not retrieve current diagnostics mode,
   No kernel interface to firmware
  cpu_smt: SMT=8

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1812796/+subscriptions

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

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

[Ubuntu Kernel Bot]

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

apport-collect 1816702

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

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

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

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

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

Title:
  Ubuntu 19.04 - tablet pc won't wake with pen or device buttons (unless
  keyboard attached)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 19.04 QA-TEST on tablet.pc (wacom pen)
  motion computing j3400 (c2d-u9400, 4gb, intel mobile 4 series)

  The test went really well, but I noticed I couldn't wake it if left
  alone and screen dims & thus locks using tablet buttons or pen (& its
  button).

  This is [most] likely device specific & is very MINOR.

  It woke perfectly when keyboard/stand was attached, but not with the
  device's arrow keys, button, or any on screen mouse movement (using
  pen, including pen button).  If the device dimmed screen with onscreen
  keyboard no longer visible, and I couldn't wake it.

  The result was you had to connect keyboard/stand in order to wake
  device...  The track-pad on the keyboard/stand woke machine too, but
  that required keyboard to be attached.

  
  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gnome-power-manager 3.30.0-2
  ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
  Uname: Linux 4.18.0-11-generic x86_64
  ApportVersion: 2.20.10-0ubuntu19
  Architecture: amd64
  CasperVersion: 1.402
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Feb 20 07:00:51 2019
  LiveMediaBuild: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190203)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-power-manager
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1834915] Re: linux-fips: 4.4.0-1014.18 -proposed tracker

[Ubuntu Kernel Bot]

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  kernel-stable-master-bug: 1834918
  phase: Packaging
  phase-changed: Wednesday, 10. July 2019 13:09 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
+   prepare-package: Pending -- package tag not yet published
+   prepare-package-meta: Pending -- package tag not yet published
+   prepare-package-signed: Pending -- package tag not yet published
+   promote-to-proposed: Pending -- builds not complete in ppa 
main:failed,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/1834915

Title:
  linux-fips: 4.4.0-1014.18 -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 prepare-package-signed series:
  In Progress
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:
  Invalid
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:
  Invalid
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

  -- swm properties --
  kernel-stable-master-bug: 1834918
  phase: Packaging
  phase-changed: Wednesday, 10. July 2019 13:09 UTC
  reason:
prepare-package: Pending -- package tag not yet published
prepare-package-meta: Pending -- package tag not yet published
prepare-package-signed: Pending -- package tag not yet published
promote-to-proposed: Pending -- builds not complete in ppa 
main:failed,meta:building,signed:building
  variant: debs

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

-- 
Mailing list: https://launchpad.net/~kernel-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: 4.15.0-1012.13 -proposed tracker

[Ubuntu Kernel Bot]

** Changed in: kernel-sru-workflow/prepare-package-meta
   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
  
  -- swm properties --
  kernel-stable-master-bug: 1834954
  phase: Packaging
  phase-changed: Tuesday, 09. July 2019 15:42 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
+   prepare-package: Pending -- package tag not yet published
+   prepare-package-signed: Pending -- package tag not yet published
+   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/1834944

Title:
  linux-fips: 4.15.0-1012.13 -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:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  In Progress
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:
  Invalid
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:
  Invalid
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: Packaging
  phase-changed: Tuesday, 09. July 2019 15:42 UTC
  reason:
prepare-package: Pending -- package tag not yet published
prepare-package-signed: Pending -- package tag not yet published
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/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 1816702] Re: Ubuntu 19.04 - tablet pc won't wake with pen or device buttons (unless keyboard attached)

[Chris Guiver]

My comment #3 is in error, on the QA-test I wrote

"...suspended system, waited, woke with power button, screensaver was
visible which I could wake with wacom pen & streaming news continued
(with sound)."

I misread this report which is not about wake-from-suspend; thus comment #3 is 
invalid.
Sorry for my mistake.  (I've already started 19.10 Ubuntu zsync, and will test 
for this function using the 19.10 Lubuntu again).

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

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

Title:
  Ubuntu 19.04 - tablet pc won't wake with pen or device buttons (unless
  keyboard attached)

Status in linux package in Ubuntu:
  New

Bug description:
  Ubuntu 19.04 QA-TEST on tablet.pc (wacom pen)
  motion computing j3400 (c2d-u9400, 4gb, intel mobile 4 series)

  The test went really well, but I noticed I couldn't wake it if left
  alone and screen dims & thus locks using tablet buttons or pen (& its
  button).

  This is [most] likely device specific & is very MINOR.

  It woke perfectly when keyboard/stand was attached, but not with the
  device's arrow keys, button, or any on screen mouse movement (using
  pen, including pen button).  If the device dimmed screen with onscreen
  keyboard no longer visible, and I couldn't wake it.

  The result was you had to connect keyboard/stand in order to wake
  device...  The track-pad on the keyboard/stand woke machine too, but
  that required keyboard to be attached.

  
  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gnome-power-manager 3.30.0-2
  ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
  Uname: Linux 4.18.0-11-generic x86_64
  ApportVersion: 2.20.10-0ubuntu19
  Architecture: amd64
  CasperVersion: 1.402
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Feb 20 07:00:51 2019
  LiveMediaBuild: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190203)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-power-manager
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://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 1834047] Re: [Nvidia Quadro P1000] Xorg driver not loaded and external monitor not recognised

[Daniel Martinek]

Cannot update. Newest version 19.4

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

Title:
  [Nvidia Quadro P1000] Xorg driver not loaded and external monitor not
  recognised

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

Bug description:
  I have BenQ i do not know what number, but it is connected by HDMI to DVI 
cable.
   nvidia-driver-418 is version 418.56-0ubuntu1

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.0.0-17.18-generic 5.0.8
  Uname: Linux 5.0.0-17-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] je adresářem: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  418.56  Fri Mar 15 12:59:26 
CDT 2019
   GCC version:  gcc version 8.3.0 (Ubuntu 8.3.0-6ubuntu1)
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Operace zamítnuta: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jun 24 16:20:03 2019
  DistUpgraded: Fresh install
  DistroCodename: disco
  DistroVariant: ubuntu
  DkmsStatus:
   als, master, 5.0.0-16-generic, x86_64: installed
   als, master, 5.0.0-17-generic, x86_64: installed
   nvidia, 418.56, 5.0.0-16-generic, x86_64: installed
   nvidia, 418.56, 5.0.0-17-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   NVIDIA Corporation GP107GLM [Quadro P1000 Mobile] [10de:1cbb] (rev a1) 
(prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company GP107GLM [Quadro P1000 Mobile] (P1000 
[Zbook 17 G5 mobile workstation]) [103c:842f]
  MachineType: HP HP ZBook 17 G5
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=cs_CZ.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-17-generic 
root=UUID=d3c1a21c-bf79-43cc-9eb9-83748dbaf57d ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/15/2019
  dmi.bios.vendor: HP
  dmi.bios.version: Q70 Ver. 01.07.00
  dmi.board.name: 842D
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 15.37.00
  dmi.chassis.asset.tag: 5CD8501DGX
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrQ70Ver.01.07.00:bd04/15/2019:svnHP:pnHPZBook17G5:pvr:rvnHP:rn842D:rvrKBCVersion15.37.00:cvnHP:ct10:cvr:
  dmi.product.family: 103C_5336AN HP ZBook 17
  dmi.product.name: HP ZBook 17 G5
  dmi.product.sku: 4QH25EA#BCM
  dmi.sys.vendor: HP
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20180925-2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Kernel-packages] [Bug 1836340] Re: [19.10 FEAT] Export CPU-MF counter sets as auxtrace data for perf

[Frank Heimes]

Based on this information:
$ rmadison --arch=s390x linux-generic | grep eoan-proposed
 linux-generic | 5.2.0.8.9 | eoan-proposed   | s390x
$ git tag --contains 8dabe9c43af7aa78b16ce0d61bc595eca20c7a70
Ubuntu-5.2.0-8.9
v5.2
$ git tag --contains fe5908bccc565f85cab025695627678cf257f91e
Ubuntu-5.2.0-8.9
v5.2
$ git tag --contains b6ffdf27f3d4f1e9af56effe6f86989170d71e95
Ubuntu-5.2.0-8.9
v5.2
$ git tag --contains 1c410fd6a561af452aba282b1cd3cabef2080d72
Ubuntu-5.2.0-8.9
v5.2
I'm setting the status of this ticket to Fix Committed.

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

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

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

** Changed in: ubuntu-z-systems
   Importance: Undecided => High

** Changed in: ubuntu-z-systems
 Assignee: (unassigned) => Frank Heimes (frank-heimes)

** Changed in: linux (Ubuntu)
 Assignee: Skipper Bug Screeners (skipper-screen-team) => Frank Heimes 
(frank-heimes)

** Information type changed from Private to Public

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

Title:
  [19.10 FEAT] Export CPU-MF counter sets as auxtrace data for perf

Status in Ubuntu on IBM z Systems:
  Fix Committed
Status in linux package in Ubuntu:
  Fix Committed

Bug description:
  Available with kernel 5.1 
  https://github.com/torvalds/linux/commit/fe5908bccc

  The feature has the following commit IDs

  commit 8dabe9c43af7aa78b16ce0d61bc595eca20c7a70
perf report: Dump s390 counter set data to file
  commit fe5908bccc565f85cab025695627678cf257f91e
  s390/cpum_cf_diag: Add support for s390 counter facility diagnostic trace
  commit b6ffdf27f3d4f1e9af56effe6f86989170d71e95
s390/cpumf: Fix warning from check_processor_id
  commit 1c410fd6a561af452aba282b1cd3cabef2080d72 
s390/cpum_cf_diag: Add support for CPU-MF SVN 6

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

-- 
Mailing list: https://launchpad.net/~kernel-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: 4.15.0-1058.64 -proposed tracker

[Andy Whitcroft]

** Tags added: kernel-fake-testing-done

-- 
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: 4.15.0-1058.64 -proposed tracker

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

  derivatives: bug 1834924 (dragonboard-kernel)

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1834954
  phase: Testing
  phase-changed: Thursday, 11. July 2019 13:10 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Ongoing -- testing in progress
certification-testing: Ongoing -- testing in progress
verification-testing: Ongoing -- testing in progress
  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 1747463] Re: kernel crashes during boot unless IOMMU is disabled on Ryzen 1800X

[Peridot]

No, only pci=noats works

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

Title:
  kernel crashes during boot unless IOMMU is disabled on Ryzen 1800X

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

Bug description:
  I'm on a Ryzen 1800X and Biostar B350GT5 on bionic kubuntu.

  There are lots of AMD-Vi logged events and I get irq crashes or acpi
  hangups with a 'normal' boot. I got it to boot by disabling IOMMU in
  the BIOS and adding "iommu=soft" to the kernel booting options in
  grub.

  linux can then detect everything properly (all cores) and I've had
  zero crashes. The only issue is that it's using software IOMMU which
  could have a performance penalty because it has to copy all the data
  of some PCI devices to sub 4G regions.

  Alternatively it boots with the kernel option "acpi=off" but only
  detects a single core/thread.

  I attached a kernel log.

  I believe(d) this might be related to 
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1671360
  and https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1690085
  ---
  ApportVersion: 2.20.8-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  fixme  1487 F pulseaudio
   /dev/snd/controlC0:  fixme  1487 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=bc971fcc-8e63-4fa5-a149-af4af6c8eece
  InstallationDate: Installed on 2018-01-31 (4 days ago)
  InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180131)
  IwConfig:
   lono wireless extensions.

   enp3s0no wireless extensions.
  MachineType: BIOSTAR Group B350GT5
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic.efi.signed 
root=/dev/mapper/kubuntu--vg-root ro iommu=soft quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-32-generic N/A
   linux-backports-modules-4.13.0-32-generic  N/A
   linux-firmware 1.170
  RfKill:

  Tags:  bionic
  Uname: Linux 4.13.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/30/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5.13
  dmi.board.asset.tag: None
  dmi.board.name: B350GT5
  dmi.board.vendor: BIOSTAR Group
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5.13:bd11/30/2017:svnBIOSTARGroup:pnB350GT5:pvr:rvnBIOSTARGroup:rnB350GT5:rvr:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: None
  dmi.product.name: B350GT5
  dmi.sys.vendor: BIOSTAR Group

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

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

[Kernel-packages] [Bug 1835185] Re: High write iops after kernel upgrade

[Kai-Heng Feng]

Please test this kernel:
https://people.canonical.com/~khfeng/lp1835185/

It reverts the only BTRFS commit between -45 and -46:
commit 1d81a0bf4208926150baa26ccfc85926282c1f36
Author: Filipe Manana 
Date:   Wed May 9 16:01:46 2018 +0100

Btrfs: fix duplicate extents after fsync of file with prealloc
extents

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

Title:
  High write iops after kernel upgrade

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu server 18.04.2
  There is a problem with the latest system updates (kernel version 
4.15.0-54-generic # 58-Ubuntu SMP).
  After upgrading from version 4.15.0-36-generic # 39-Ubuntu SMP
  we observe at the same software configuration an increased load on the disk 
(write) - MySQL previously loaded the disk at 20-50 mB/s, after the update it 
started loading at 150-250 mB/s. On the server we have cronjobs with PHP 
writing stuff to the DB.
  MySQL configuration and package version was not changed, the load profile is 
the same and does not depend on external users (OLAP DB)

  If we boot into the old kernel version (4.15.0-36), the problem disappears. 
Also tested kernels:
  4.15.0-52 - problem persists
  4.18.0-25 (hwe) - problem persists, load became more 200-250 mB/s

  Attaching list of updated packages (apt/history.log) and other info.

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

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

[Kernel-packages] [Bug 1818974] Re: Ubuntu 18.04 Kernel 4.18 - Standby wakeup user session crash

[Kai-Heng Feng]

Please test latest mainline kernel:
https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.2-rc7/

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

Title:
  Ubuntu 18.04 Kernel 4.18 - Standby wakeup user session crash

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I'm using Ubuntu 18.04 (Linux Mint 19.1 Tessa) with HWE.
  Since kernel 4.18 sometimes while waking up from standby my user session 
crash.
  I assume that my attached external USB to SATA HDD could be cause this kernel 
bug.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  martin27966 F pulseaudio
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 19.1
  HibernationDevice: RESUME=UUID=4a747812-cab0-438b-ace1-a46b73f00d4a
  InstallationDate: Installed on 2018-07-21 (228 days ago)
  InstallationMedia: Linux Mint 19 "Tara" - Release amd64 20180626
  MachineType: LENOVO 20FXS05500
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-16-generic 
root=UUID=8ffc268d-6911-42c4-9bc3-a290376cb41b ro quiet splash 
nvidia-drm.modeset=1 nopti spectre_v2=off spectre_v2_user=off nospec noibrs 
noibpb l1tf=off vt.handoff=1
  ProcVersionSignature: Ubuntu 4.18.0-16.17~18.04.1-generic 4.18.20
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-16-generic N/A
   linux-backports-modules-4.18.0-16-generic  N/A
   linux-firmware 1.173.3
  Tags:  tessa
  Uname: Linux 4.18.0-16-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom davfs2 dip lpadmin plugdev sambashare scanner sudo
  _MarkForUpload: True
  dmi.bios.date: 09/27/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R07ET87W (2.27 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20FXS05500
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrR07ET87W(2.27):bd09/27/2018:svnLENOVO:pn20FXS05500:pvrThinkPadT460p:rvnLENOVO:rn20FXS05500:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T460p
  dmi.product.name: 20FXS05500
  dmi.product.sku: LENOVO_MT_20FX_BU_Think_FM_ThinkPad T460p
  dmi.product.version: ThinkPad T460p
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1816702] Re: Ubuntu 19.04 - tablet pc won't wake with pen or device buttons (unless keyboard attached)

[Kai-Heng Feng]

Is this a regression?

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

Title:
  Ubuntu 19.04 - tablet pc won't wake with pen or device buttons (unless
  keyboard attached)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 19.04 QA-TEST on tablet.pc (wacom pen)
  motion computing j3400 (c2d-u9400, 4gb, intel mobile 4 series)

  The test went really well, but I noticed I couldn't wake it if left
  alone and screen dims & thus locks using tablet buttons or pen (& its
  button).

  This is [most] likely device specific & is very MINOR.

  It woke perfectly when keyboard/stand was attached, but not with the
  device's arrow keys, button, or any on screen mouse movement (using
  pen, including pen button).  If the device dimmed screen with onscreen
  keyboard no longer visible, and I couldn't wake it.

  The result was you had to connect keyboard/stand in order to wake
  device...  The track-pad on the keyboard/stand woke machine too, but
  that required keyboard to be attached.

  
  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gnome-power-manager 3.30.0-2
  ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
  Uname: Linux 4.18.0-11-generic x86_64
  ApportVersion: 2.20.10-0ubuntu19
  Architecture: amd64
  CasperVersion: 1.402
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Feb 20 07:00:51 2019
  LiveMediaBuild: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190203)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-power-manager
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1816702] Re: Ubuntu 19.04 - tablet pc won't wake with pen or device buttons (unless keyboard attached)

[Chris Guiver]

> 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'.
It was a 'live' QA-test (19.04 daily) so I cannot add information on that run. 

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

Title:
  Ubuntu 19.04 - tablet pc won't wake with pen or device buttons (unless
  keyboard attached)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 19.04 QA-TEST on tablet.pc (wacom pen)
  motion computing j3400 (c2d-u9400, 4gb, intel mobile 4 series)

  The test went really well, but I noticed I couldn't wake it if left
  alone and screen dims & thus locks using tablet buttons or pen (& its
  button).

  This is [most] likely device specific & is very MINOR.

  It woke perfectly when keyboard/stand was attached, but not with the
  device's arrow keys, button, or any on screen mouse movement (using
  pen, including pen button).  If the device dimmed screen with onscreen
  keyboard no longer visible, and I couldn't wake it.

  The result was you had to connect keyboard/stand in order to wake
  device...  The track-pad on the keyboard/stand woke machine too, but
  that required keyboard to be attached.

  
  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gnome-power-manager 3.30.0-2
  ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
  Uname: Linux 4.18.0-11-generic x86_64
  ApportVersion: 2.20.10-0ubuntu19
  Architecture: amd64
  CasperVersion: 1.402
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Feb 20 07:00:51 2019
  LiveMediaBuild: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190203)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-power-manager
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1836132] Re: headphone-mic doesn't work on a couple of dell machines (alsa/realtek)

[Timo Aaltonen]

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

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

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

** Changed in: linux-oem-osp1 (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/1836132

Title:
  headphone-mic doesn't work on a couple of dell machines (alsa/realtek)

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

Bug description:
  We need to add support for a pure Mic device plugged into the audio
  jack.

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

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

[Kernel-packages] [Bug 1836152] Re: Intel ethernet I219 has slow RX speed

[Timo Aaltonen]

** Changed in: linux-oem-osp1 (Ubuntu Bionic)
   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/1836152

Title:
  Intel ethernet I219 has slow RX speed

Status in HWE Next:
  New
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:
  Confirmed
Status in linux-oem source package in Bionic:
  New
Status in linux-oem-osp1 source package in Bionic:
  Fix Committed
Status in linux source package in Disco:
  Confirmed
Status in linux-oem source package in Disco:
  Invalid
Status in linux-oem-osp1 source package in Disco:
  Invalid

Bug description:
  [Impact]
  RX speed on Intel ethernet I219 v6 is extremely slow due to multiple RX
  CRC errors.

  [Fix]
  Disable e1000e K1 feature to make I219 and PCH operate at higher speed
  to avoid the issue.
   
  [Test]
  Before applying the patch, the RX is slower than 150Kbps. After applying
  the fix the RX speed can achive gigabits.

  [Regression Potential]
  Low. This only applies to recent I219 generations.
  I've also test several other systems with e1000e and I don't see any
  regression.

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

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

[Kernel-packages] [Bug 1836177] Re: Intel ethernet I219 may wrongly detect connection speed as 10Mbps

[Timo Aaltonen]

** Changed in: linux-oem-osp1 (Ubuntu Bionic)
   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/1836177

Title:
  Intel ethernet I219 may wrongly detect connection speed as 10Mbps

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

Bug description:
  [Impact]
  Intel I219 ethernet may wrongly detect 1Gbps network as 10Mbps after
  ethernet cable hotplugging.

  [Fix]
  Use delayed work before deciding the network speed.
  This essentially workarounds unreliable reading on MII_BMSR register.

  [Test]
  Before the patch the network operates at 10Mbps after cable gets
  plugged.
  With the fix, network always operates in 1Gbps.

  [Regression Potential]
  Low. It changes the watchdog task from timer to delayed work, the logic
  is essentially the same.

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

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

[Kernel-packages] [Bug 1816702] Re: Ubuntu 19.04 - tablet pc won't wake with pen or device buttons (unless keyboard attached)

[Sebastien Bacher]

The waking up is probably lower level, gnome-power-manager also isn't a
service but just an UI showing power usage statistics nowadays

** Package changed: gnome-power-manager (Ubuntu) => linux (Ubuntu)

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

Title:
  Ubuntu 19.04 - tablet pc won't wake with pen or device buttons (unless
  keyboard attached)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 19.04 QA-TEST on tablet.pc (wacom pen)
  motion computing j3400 (c2d-u9400, 4gb, intel mobile 4 series)

  The test went really well, but I noticed I couldn't wake it if left
  alone and screen dims & thus locks using tablet buttons or pen (& its
  button).

  This is [most] likely device specific & is very MINOR.

  It woke perfectly when keyboard/stand was attached, but not with the
  device's arrow keys, button, or any on screen mouse movement (using
  pen, including pen button).  If the device dimmed screen with onscreen
  keyboard no longer visible, and I couldn't wake it.

  The result was you had to connect keyboard/stand in order to wake
  device...  The track-pad on the keyboard/stand woke machine too, but
  that required keyboard to be attached.

  
  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gnome-power-manager 3.30.0-2
  ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
  Uname: Linux 4.18.0-11-generic x86_64
  ApportVersion: 2.20.10-0ubuntu19
  Architecture: amd64
  CasperVersion: 1.402
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Feb 20 07:00:51 2019
  LiveMediaBuild: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190203)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-power-manager
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

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

[Ubuntu Kernel Bot]

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

apport-collect 1816702

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

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

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

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

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

Title:
  Ubuntu 19.04 - tablet pc won't wake with pen or device buttons (unless
  keyboard attached)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 19.04 QA-TEST on tablet.pc (wacom pen)
  motion computing j3400 (c2d-u9400, 4gb, intel mobile 4 series)

  The test went really well, but I noticed I couldn't wake it if left
  alone and screen dims & thus locks using tablet buttons or pen (& its
  button).

  This is [most] likely device specific & is very MINOR.

  It woke perfectly when keyboard/stand was attached, but not with the
  device's arrow keys, button, or any on screen mouse movement (using
  pen, including pen button).  If the device dimmed screen with onscreen
  keyboard no longer visible, and I couldn't wake it.

  The result was you had to connect keyboard/stand in order to wake
  device...  The track-pad on the keyboard/stand woke machine too, but
  that required keyboard to be attached.

  
  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gnome-power-manager 3.30.0-2
  ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
  Uname: Linux 4.18.0-11-generic x86_64
  ApportVersion: 2.20.10-0ubuntu19
  Architecture: amd64
  CasperVersion: 1.402
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Feb 20 07:00:51 2019
  LiveMediaBuild: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190203)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-power-manager
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1816702] [NEW] Ubuntu 19.04 - tablet pc won't wake with pen or device buttons (unless keyboard attached)

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

Ubuntu 19.04 QA-TEST on tablet.pc (wacom pen)
motion computing j3400 (c2d-u9400, 4gb, intel mobile 4 series)

The test went really well, but I noticed I couldn't wake it if left
alone and screen dims & thus locks using tablet buttons or pen (& its
button).

This is [most] likely device specific & is very MINOR.

It woke perfectly when keyboard/stand was attached, but not with the
device's arrow keys, button, or any on screen mouse movement (using pen,
including pen button).  If the device dimmed screen with onscreen
keyboard no longer visible, and I couldn't wake it.

The result was you had to connect keyboard/stand in order to wake
device...  The track-pad on the keyboard/stand woke machine too, but
that required keyboard to be attached.


ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: gnome-power-manager 3.30.0-2
ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
Uname: Linux 4.18.0-11-generic x86_64
ApportVersion: 2.20.10-0ubuntu19
Architecture: amd64
CasperVersion: 1.402
CurrentDesktop: ubuntu:GNOME
Date: Wed Feb 20 07:00:51 2019
LiveMediaBuild: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190203)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: gnome-power-manager
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug disco iso-testing
-- 
Ubuntu 19.04 - tablet pc won't wake with pen or device buttons (unless keyboard 
attached)
https://bugs.launchpad.net/bugs/1816702
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to linux in Ubuntu.

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

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

[Ubuntu Kernel Bot]

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

apport-collect 1836020

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

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

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

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

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

Title:
  Sometimes touchpad(goodix) can't use tap function

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

Bug description:
  [Impact]
  Wake up from runtime suspend, Goodix doesn't report correct Tap event by 
tapping it the first time, so if you double tap the touchpad, the system only 
got one tap.

  [Fix]
  Adding the platforms which uses Goodix touchpad IC to the i2c designware 
quirk list.

  [Test]
  Verified on the buggy machines.

  [Regression Potential]
  Low, this quirk doesn't hurt anything and do little or none to power 
consumption.

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

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

[Kernel-packages] [Bug 1836287] Re: Bionic update: upstream stable patchset 2019-07-11

[Khaled El Mously]

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

Title:
  Bionic update: upstream stable patchset 2019-07-11

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

Bug description:
  SRU Justification

  Impact:
     The upstream process for stable tree updates is quite similar
     in scope to the Ubuntu SRU process, e.g., each patch has to
     demonstrably fix a bug, and each patch is vetted by upstream
     by originating either directly from a mainline/stable Linux tree or
     a minimally backported form of that patch. The following upstream
     stable patches should be included in the Ubuntu kernel:

     upstream stable patchset 2019-07-11

 Ported from the following upstream stable releases:
  v4.14.73, v4.18.11,
  v4.14.74, v4.18.12

     from git://git.kernel.org/

  perf tools: Fix undefined symbol scnprintf in libperf-jvmti.so
  gso_segment: Reset skb->mac_len after modifying network header
  ipv6: fix possible use-after-free in ip6_xmit()
  net/appletalk: fix minor pointer leak to userspace in SIOCFINDIPDDPRT
  net: hp100: fix always-true check for link up state
  pppoe: fix reception of frames with no mac header
  qmi_wwan: set DTR for modems in forced USB2 mode
  udp4: fix IP_CMSG_CHECKSUM for connected sockets
  neighbour: confirm neigh entries when ARP packet is received
  udp6: add missing checks on edumux packet processing
  net/sched: act_sample: fix NULL dereference in the data path
  tls: don't copy the key out of tls12_crypto_info_aes_gcm_128
  tls: zero the crypto information from tls_context before freeing
  tls: clear key material from kernel memory when do_tls_setsockopt_conf fails
  NFC: Fix possible memory corruption when handling SHDLC I-Frame commands
  NFC: Fix the number of pipes
  ASoC: cs4265: fix MMTLR Data switch control
  ASoC: rsnd: fixup not to call clk_get/set under non-atomic
  ALSA: bebob: fix memory leak for M-Audio FW1814 and ProjectMix I/O at error 
path
  ALSA: bebob: use address returned by kmalloc() instead of kernel stack for 
streaming DMA mapping
  ALSA: emu10k1: fix possible info leak to userspace on SNDRV_EMU10K1_IOCTL_INFO
  ALSA: fireface: fix memory leak in ff400_switch_fetching_mode()
  ALSA: firewire-digi00x: fix memory leak of private data
  ALSA: firewire-tascam: fix memory leak of private data
  ALSA: fireworks: fix memory leak of response buffer at error path
  ALSA: oxfw: fix memory leak for model-dependent data at error path
  ALSA: oxfw: fix memory leak of discovered stream formats at error path
  ALSA: oxfw: fix memory leak of private data
  platform/x86: alienware-wmi: Correct a memory leak
  xen/netfront: don't bug in case of too many frags
  xen/x86/vpmu: Zero struct pt_regs before calling into sample handling code
  spi: fix IDR collision on systems with both fixed and dynamic SPI bus numbers
  ring-buffer: Allow for rescheduling when removing pages
  mm: shmem.c: Correctly annotate new inodes for lockdep
  scsi: target: iscsi: Use bin2hex instead of a re-implementation
  ocfs2: fix ocfs2 read block panic
  drm/nouveau: Fix deadlocks in nouveau_connector_detect()
  drm/nouveau/drm/nouveau: Don't forget to cancel hpd_work on suspend/unload
  drm/nouveau/drm/nouveau: Fix bogus drm_kms_helper_poll_enable() placement
  drm/nouveau/drm/nouveau: Use pm_runtime_get_noresume() in connector_detect()
  drm/nouveau/drm/nouveau: Prevent handling ACPI HPD events too early
  drm/vc4: Fix the "no scaling" case on multi-planar YUV formats
  drm: udl: Destroy framebuffer only if it was initialized
  drm/amdgpu: add new polaris pci id
  ext4: check to make sure the rename(2)'s destination is not freed
  ext4: avoid divide by zero fault when deleting corrupted inline directories
  ext4: avoid arithemetic overflow that can trigger a BUG
  ext4: recalucate superblock checksum after updating free blocks/inodes
  ext4: fix online resize's handling of a too-small final block group
  ext4: fix online resizing for bigalloc file systems with a 1k block size
  ext4: don't mark mmp buffer head dirty
  ext4: show test_dummy_encryption mount option in /proc/mounts
  sched/fair: Fix vruntime_normalized() for remote non-migration wakeup
  PCI: aardvark: Size bridges before resources allocation
  vmw_balloon: include asm/io.h
  iw_cxgb4: only allow 1 flush on user qps
  tick/nohz: Prevent bogus softirq pending warning
  spi: Fix double IDR allocation with DT aliases
  hv_netvsc: fix schedule in RCU context
  bnxt_en: Fix VF mac address regression.
  net: rtnl_configure_link: fix dev flags changes arg to __dev_notify_flags
  mtd: rawnand: denali: fix a race condition when DMA is kicked
  platform/x86: dell-smbios-wmi: Correct a memory leak
  spi: fix IDR 

[Kernel-packages] [Bug 1829378] Re: Kernel 4.15.0-50 or newer wont boot as Xen-DomU with PVH

[Khaled El Mously]

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

Title:
  Kernel 4.15.0-50 or newer wont boot as Xen-DomU with PVH

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

Bug description:
  === SRU Justification ===
  [Impact]
  NULL pointer dereference in acpi_quirk_matches_bios_ids() renders kernel
  unbootable.

  [Fix]
  It's a regression caused by commit abd273f52766 ("UBUNTU: SAUCE: ACPI /
  bus: Add some Lenovo laptops in list of acpi table term list").

  When both bios_vendor and bios_ver are NULL then a NULL string is passed
  to strncmp() and the issue occurs.

  VMs may not provides string bios_vendor or bios_ver, so bail out early
  when either bios_vendor or bios_ver is NULL.

  [Test]
  User reported the test kernel with proposed fix solves the issue.

  [Regression Potenial]
  Low. It's quite trivial so I don't think it'll regress anything.

  === Original Bug Report ===
  After upgrading HWE-16.04-kernel from 4.15.0-48 to 4.15.0-50 the kernel 
crashes while booting as PVH-Guest with Xen 4.12 (booting as PV works).
  Kernel 4.15.0-48 and prior did boot without any problems as PVH.

  We have the same problem for Ubuntu 18.04 with Kernel 4.15.0-50.
  Ubunutu 18.04 with HWE-Kernel 4.18.0-20 boots without problems as PVH-
  DomU.

  See also https://lists.xenproject.org/archives/html/xen-
  users/2019-05/msg00010.html

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

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

[Kernel-packages] [Bug 1836308] Re: Unhide Nvidia HDA audio controller

[Kai-Heng Feng]

** Tags added: oem-priority originate-from-1799870 stella

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

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

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

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

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

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

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

** Changed in: linux-oem-osp1 (Ubuntu Disco)
   Status: New => Invalid

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

Title:
  Unhide Nvidia HDA audio controller

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

Bug description:
  [Impact]
  Nvidia HDA audio controller comes with Nvidia graphics cannot be found
  by PCI subsystem.

  [Fix]
  Write bit 25 at graphics' config space offset 0x488 to enable the HDA
  controller.

  [Test]
  Nvidia HDA controller is not listed under lspci.
  After applying the fix lspci can find Nvidia HDA controller.

  [Regression Potential]
  Low. This fix doesn't bring any functional change other then exposing
  HDA controller at hardware level.

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

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

[Kernel-packages] [Bug 1827314] Re: Ubuntu 19.04 Background and lockscreen image turns into white noise after sleep and wakeup

[Launchpad Bug Tracker]

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

Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: gnome-desktop (Ubuntu)
   Status: New => Confirmed

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

Title:
  Ubuntu 19.04 Background and lockscreen image turns into white noise
  after sleep and wakeup

Status in gnome-desktop package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 19.04 Background and lockscreen image turns into white noise after 
sleep and wakeup
  the lock screen is Disco Dingo default image and bg is custom but both turn 
into a noisy broken image
  my laptop is MSI CX627QL
  Core i5 7th gen
  Ram 12 gb

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-desktop/+bug/1827314/+subscriptions

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