Re: [Kernel-packages] [Bug 1842037] Re: Oops when Kerberos credentials are invalid

[Frank Burkhardt]

Hi Matthey,

- Ursprüngliche Mail -
> Von: "Matthew Ruffell" <1842...@bugs.launchpad.net>
> An: "burk" 
> Gesendet: Mittwoch, 11. September 2019 02:44:11
> Betreff: [Bug 1842037] Re: Oops when Kerberos credentials are invalid

> Hi Frank,
> 
> The test kernel has built, and I have tested it to ensure it boots, but
> I now need you to verify that the backported patches fix the issue that
> you are having.
> 
> Can you please install the test kernel onto a system which is having
> problems with NFS clients that are connecting with invalid kerberos
> credentials?
> 
> Please note this kernel is NOT SUPPORTED by Canonical, and is for
> TESTING PURPOSES ONLY. ONLY Install in a dedicated test environment.

thank you for the quick response. I'm deploying the kernel to
a test system right now.

Best regards,

Frank

-- 
Frank Burkhardt 
IT Dept., Max Planck Institute for Human Cognitive
and Brain Sciences, Leipzig, Germany

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

Title:
  Oops when Kerberos credentials are invalid

Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Disco:
  In Progress

Bug description:
  There's a bug in Linux Kernel 5.0 which is triggered by invalid
  credentials when the NFS clients is trying to aquire them via GSSD.
  This affects NFS-Shares that are protected by krb5* security. They
  become unusable until the system is re-booted. The problem is quite
  severe on terminal servers with multiple users - some of them not
  caring about refreshing their kerberos tickets.

  A fix is available here:

  


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

-- 
Mailing list: https://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 1839253] Re: Excessive screen tearing and flickering on Asus ZenBook S UX391UA

[Ethan Walker]

I'm uncertain if this channel is still open, but It seems that the problem
has returned. I'm not quite sure why, I think it might be that I didn't
properly update to boot parameters when I was testing kernel 5.3.0 - 994
but either way, it seems that the new kernel isn't a solution.

On Tue, Sep 3, 2019 at 10:02 PM Daniel van Vugt <
daniel.van.v...@canonical.com> wrote:

> ** Changed in: linux (Ubuntu)
>Status: Incomplete => New
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1839253
>
> Title:
>   Excessive screen tearing and flickering on Asus ZenBook S UX391UA
>
> Status in linux package in Ubuntu:
>   Confirmed
>
> Bug description:
>   I am experiencing a large amount of screen tearing flickering and
>   artifacting. I've tried the common fix that is suggested on
>   askubuntu.com which is editing the file /etc/X11/xorg.conf.d/20-intel-
>   graphics.conf and this has not changed anything.
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 19.04
>   Package: xorg 1:7.7+19ubuntu12
>   ProcVersionSignature: Ubuntu 5.0.0-23.24-generic 5.0.15
>   Uname: Linux 5.0.0-23-generic x86_64
>   ApportVersion: 2.20.10-0ubuntu27.1
>   Architecture: amd64
>   BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
>   CompositorRunning: None
>   CurrentDesktop: ubuntu:GNOME
>   Date: Wed Aug  7 02:06:01 2019
>   DistUpgraded: Fresh install
>   DistroCodename: disco
>   DistroVariant: ubuntu
>   ExtraDebuggingInterest: Yes
>   GraphicsCard:
>Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00
> [VGA controller])
>  Subsystem: ASUSTeK Computer Inc. UHD Graphics 620 [1043:10a1]
>   InstallationDate: Installed on 2019-08-06 (1 days ago)
>   InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
>   Lsusb:
>Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
>Bus 001 Device 004: ID 27c6:5201
>Bus 001 Device 003: ID 8087:0a2b Intel Corp.
>Bus 001 Device 002: ID 13d3:56b9 IMC Networks
>Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
>   MachineType: ASUSTeK COMPUTER INC. ZenBook S UX391UA
>   ProcEnviron:
>TERM=xterm-256color
>PATH=(custom, no user)
>XDG_RUNTIME_DIR=
>LANG=en_US.UTF-8
>SHELL=/bin/bash
>   ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-23-generic
> root=UUID=6c2ff7ef-a93b-47fe-ae85-a60f10a4201f ro quiet splash vt.handoff=1
>   SourcePackage: xorg
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   dmi.bios.date: 05/18/2018
>   dmi.bios.vendor: American Megatrends Inc.
>   dmi.bios.version: UX391UA.204
>   dmi.board.asset.tag: ATN12345678901234567
>   dmi.board.name: UX391UA
>   dmi.board.vendor: ASUSTeK COMPUTER INC.
>   dmi.board.version: 1.0
>   dmi.chassis.asset.tag: No Asset Tag
>   dmi.chassis.type: 10
>   dmi.chassis.vendor: ASUSTeK COMPUTER INC.
>   dmi.chassis.version: 1.0
>   dmi.modalias:
> dmi:bvnAmericanMegatrendsInc.:bvrUX391UA.204:bd05/18/2018:svnASUSTeKCOMPUTERINC.:pnZenBookSUX391UA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX391UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
>   dmi.product.family: ZenBook S
>   dmi.product.name: ZenBook S UX391UA
>   dmi.product.version: 1.0
>   dmi.sys.vendor: ASUSTeK COMPUTER INC.
>   version.compiz: compiz N/A
>   version.libdrm2: libdrm2 2.4.97-1ubuntu1
>   version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1.1
>   version.libgl1-mesa-glx: libgl1-mesa-glx 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/linux/+bug/1839253/+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/1839253

Title:
  Excessive screen tearing and flickering on Asus ZenBook S UX391UA

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I am experiencing a large amount of screen tearing flickering and
  artifacting. I've tried the common fix that is suggested on
  askubuntu.com which is editing the file /etc/X11/xorg.conf.d/20-intel-
  graphics.conf and this has not changed anything.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.0.0-23.24-generic 5.0.15
  Uname: Linux 5.0.0-23-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27.1
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Aug  7 02:06:01 2019
  DistUpgraded: Fresh install
  

[Kernel-packages] [Bug 1834047] Re: [Nvidia Quadro P1000] Xorg driver not loaded and external monitor not recognised

[Launchpad Bug Tracker]

[Expired for nvidia-graphics-drivers-418 (Ubuntu) because there has been
no activity for 60 days.]

** Changed in: nvidia-graphics-drivers-418 (Ubuntu)
   Status: Incomplete => Expired

-- 
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:
  Expired

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 1843323] Re: Kernel 4.15.0-59 (and onwards) breaks scroll wheel of USB mouse (A4Tech X5-50D)

[Ubuntu Foundations Team Bug Bot]

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

Title:
  Kernel 4.15.0-59 (and onwards) breaks scroll wheel of USB mouse
  (A4Tech X5-50D)

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

Bug description:
  The latest kernel upgrade makes it impossible to use the scroll wheel
  of one specific mouse.

   Affected Ubuntu release: 18.04.3
   Last working kernel version: 4.15.0-58
   Affected kernel versions: 4.15.0-59, 4.15.0-60, 4.15.0-62, …

  I've several X5-50D input devices, tested at three different systems,
  connected via USB2 and USB3. I can reproduce the issue at all machines
  at any time. All others mouses are working fine. When booting the old
  kernel the problem is gone.

  Please tell me what details are required to trace this issue down. I
  should be able to test custom patches and build packages, if required.

  > usb 3-11: new low-speed USB device number 5 using xhci_hcd
  > usb 3-11: New USB device found, idVendor=09da, idProduct=000a
  > usb 3-11: New USB device strings: Mfr=1, Product=2, SerialNumber=0
  > usb 3-11: Product: PS/2+USB Mouse
  > usb 3-11: Manufacturer: A4Tech
  > input: A4Tech PS/2+USB Mouse as 
/devices/pci:00/:00:14.0/usb3/3-11/3-11:1.0/0003:09DA:000A.0005/input/input21
  > a4tech 0003:09DA:000A.0005: input,hidraw4: USB HID v1.10 Mouse [A4Tech 
PS/2+USB Mouse] on usb-:00:14.0-11/input0

  > Bus 003 Device 004: ID 09da:000a A4Tech Co., Ltd. Optical Mouse Opto 510D / 
OP-620D
  > Device Descriptor:
  >   bLength18
  >   bDescriptorType 1
  >   bcdUSB   1.10
  >   bDeviceClass0 (Defined at Interface level)
  >   bDeviceSubClass 0
  >   bDeviceProtocol 0
  >   bMaxPacketSize0 8
  >   idVendor   0x09da A4Tech Co., Ltd.
  >   idProduct  0x000a Optical Mouse Opto 510D / OP-620D
  >   bcdDevice1.05
  >   iManufacturer   1 A4Tech
  >   iProduct2 USB Mouse
  >   iSerial 0
  >   bNumConfigurations  1
  >   Configuration Descriptor:
  > bLength 9
  > bDescriptorType 2
  > wTotalLength   34
  > bNumInterfaces  1
  > bConfigurationValue 1
  > iConfiguration  0
  > bmAttributes 0xa0
  >   (Bus Powered)
  >   Remote Wakeup
  > MaxPower  100mA
  > Interface Descriptor:
  >   bLength 9
  >   bDescriptorType 4
  >   bInterfaceNumber0
  >   bAlternateSetting   0
  >   bNumEndpoints   1
  >   bInterfaceClass 3 Human Interface Device
  >   bInterfaceSubClass  1 Boot Interface Subclass
  >   bInterfaceProtocol  2 Mouse
  >   iInterface  0
  > HID Device Descriptor:
  >   bLength 9
  >   bDescriptorType33
  >   bcdHID   1.10
  >   bCountryCode0 Not supported
  >   bNumDescriptors 1
  >   bDescriptorType34 Report
  >   wDescriptorLength  48
  >  Report Descriptors:
  >** UNAVAILABLE **
  >   Endpoint Descriptor:
  > bLength 7
  > bDescriptorType 5
  > bEndpointAddress 0x81  EP 1 IN
  > bmAttributes3
  >   Transfer TypeInterrupt
  >   Synch Type   None
  >   Usage Type   Data
  > wMaxPacketSize 0x0008  1x 8 bytes
  > bInterval  10
  > Device Status: 0x
  >   (Bus Powered)

  ---

  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=e505eab0-02d8-41dc-90f2-de6cd8658f6f
  InstallationDate: Installed on 2015-07-19 (1513 days ago)
  InstallationMedia: Xubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422.1)
  MachineType: MSI MS-7924
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-62-generic 
root=UUID=f8e0335a-11ac-48ca-90af-23784d1ed592 ro quiet splash
  ProcVersionSignature: Ubuntu 4.15.0-62.69-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-62-generic N/A
   linux-backports-modules-4.15.0-62-generic  N/A
   linux-firmware 1.173.10
  RfKill:

  Tags:  bionic
  Uname: Linux 4.15.0-62-generic x86_64
  UpgradeStatus: Upgraded to bionic on 2019-07-16 (55 days ago)
  UserGroups: adm cdrom dialout dip fax floppy fuse libvirt libvirtd lpadmin 
plugdev sambashare sudo tape vboxusers video wireshark
  _MarkForUpload: True

To manage notifications about this bug go to:

[Kernel-packages] [Bug 1835150] Re: Sometimes touchpad detected as mouse(i2c designware fails to get adapter number)

[Anthony Wong]

** Changed in: hwe-next
   Status: New => 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/1835150

Title:
  Sometimes touchpad detected as mouse(i2c designware fails to get
  adapter number)

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

Bug description:
  [Impact]
  I2C designware fails to get its adapter number, and this may lead to fail to 
access touchpad through I2C bus.
  [ 6.476367] WARNING: CPU: 9 PID: 567 at 
/build/linux-oem-osp1-bkWHJC/linux-oem-osp1-5.0.0/drivers/i2c/i2c-core-base.c:1322
 i2c_add_numbered_adapter+0x81/0x90

  [Fix]
  The 2 commits from v5.1-rc1 fix this issue.
     cd86d1403bb4 i2c: i2c-designware-platdrv: Always use a dynamic adapter 
number
     77f3381a83c2 i2c: i2c-designware-platdrv: Cleanup setting of the adapter 
number

  [Test]
  Verified on Dell machine which had this issue.

  [Regression Potential]
  Low, the 2 commits make it always use dynamic adapter-numbers which does not 
make any difference in most cases and in the one case where it does make a 
difference the behavior change is desirable because the old behavior caused an 
oops.

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

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

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

[Anthony Wong]

** Description changed:

  [Impact]
  Dell machines which uses goodix touchpad IC emit double click event
  while touching the touchpad if designware i2c adapter is in runtime
  suspend.
  
  Goodix re-assert the interrupt if host doesn't read the data within
  100ms and designware takes a longer time to wake up from runtime
  suspend. In the case, it got a second interrupt during resuming, so
  it thinks it's a double click.
  
  [Fix]
  There is no simple way to fix this, it's a firmware issue and goodix
  agrees to fix this in their firmware on next release, but this issue is
  still affects the machines that don't come with an updated firmware. So,
  add a quirk to mark those machines and avoid the designware from entering
  runtime suspend.
  
  [Regression Potential]
  Low, it only affects the listed machines, and prevent designware from
  entering runtime suspend impacts the power consumption little or none
  during short or long idle.
+ 
+ [MISC]
+ This patch contains on going product name, so set it as SAUCE patch,
+ will submit it to upstream and to Bionic kernel later.

** Changed in: hwe-next
   Status: New => Triaged

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

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

Title:
  Sometimes touchpad automatically trigger double click

Status in HWE Next:
  Triaged
Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem-osp1 package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  Triaged
Status in linux-oem-osp1 source package in Bionic:
  Fix Released
Status in linux source package in Disco:
  Fix Released
Status in linux-oem-osp1 source package in Disco:
  Fix Released

Bug description:
  [Impact]
  Dell machines which uses goodix touchpad IC emit double click event
  while touching the touchpad if designware i2c adapter is in runtime
  suspend.

  Goodix re-assert the interrupt if host doesn't read the data within
  100ms and designware takes a longer time to wake up from runtime
  suspend. In the case, it got a second interrupt during resuming, so
  it thinks it's a double click.

  [Fix]
  There is no simple way to fix this, it's a firmware issue and goodix
  agrees to fix this in their firmware on next release, but this issue is
  still affects the machines that don't come with an updated firmware. So,
  add a quirk to mark those machines and avoid the designware from entering
  runtime suspend.

  [Regression Potential]
  Low, it only affects the listed machines, and prevent designware from
  entering runtime suspend impacts the power consumption little or none
  during short or long idle.

  [MISC]
  This patch contains on going product name, so set it as SAUCE patch,
  will submit it to upstream and to Bionic kernel later.

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

-- 
Mailing list: https://launchpad.net/~kernel-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] Re: [Intel CyclonePeak] Can not turn on BT after turn off (via Hotkey)

[Anthony Wong]

** Changed in: hwe-next
   Status: New => Fix Released

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

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 1836020] Re: Sometimes touchpad(goodix) can't use tap function

[Anthony Wong]

** Changed in: hwe-next
   Status: New => 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/1836020

Title:
  Sometimes touchpad(goodix) can't use tap function

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

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 1842608] Re: xenial/linux: 4.4.0-162.190 -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 --
  packages:
main: linux
meta: linux-meta
signed: linux-signed
  phase: Holding before Promote to Proposed
  phase-changed: Wednesday, 04. September 2019 07:52 UTC
  reason:
promote-to-proposed: Pending -- builds not complete in ppa 
main:failed,meta:depwait
  trackers:
-   trusty/linux-aws: bug 1842793, bug 1842606
-   trusty/linux-lts-xenial: bug 1842607, bug 1842794
+   trusty/linux-aws: bug 1842606, bug 1842793
+   trusty/linux-lts-xenial: bug 1842794, bug 1842607
xenial/linux-aws: bug 1842597
xenial/linux-fips: bug 1842605
xenial/linux-kvm: bug 1842598
xenial/linux-raspi2: bug 1842600
xenial/linux-snapdragon: bug 1842603
xenial/linux/pc-kernel: bug 1842595
  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/1842608

Title:
  xenial/linux: 4.4.0-162.190 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  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 --
  packages:
main: linux
meta: linux-meta
signed: linux-signed
  phase: Holding before Promote to Proposed
  phase-changed: Wednesday, 04. September 2019 07:52 UTC
  reason:
promote-to-proposed: Pending -- builds not complete in ppa 
main:failed,meta:depwait
  trackers:
trusty/linux-aws: bug 1842606, bug 1842793
trusty/linux-lts-xenial: bug 1842794, bug 1842607
xenial/linux-aws: bug 1842597
xenial/linux-fips: bug 1842605
xenial/linux-kvm: bug 1842598
xenial/linux-raspi2: bug 1842600
xenial/linux-snapdragon: bug 1842603
xenial/linux/pc-kernel: bug 1842595
  variant: debs

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

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

[Anthony Wong]

** Changed in: hwe-next
   Status: New => Fix Released

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

Title:
  Intel ethernet I219 has slow RX speed

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

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 1842587] Re: xenial/linux-azure: 4.15.0-1057.62 -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: 1842828
  packages:
main: linux-azure
meta: linux-meta-azure
signed: linux-signed-azure
  phase: Ready for Testing
  phase-changed: Friday, 06. September 2019 05:48 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
regression-testing: Ongoing -- testing in progress
stakeholder-signoff: Stalled -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
-   trusty/linux-azure: bug 1842585, bug 1842819
+   trusty/linux-azure: bug 1842819, bug 1842585
xenial/linux-azure-edge: bug 1842584
xenial/linux-azure/azure-kernel: bug 1842583
  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/1842587

Title:
  xenial/linux-azure: 4.15.0-1057.62 -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:
  New
Status in Kernel SRU Workflow stakeholder-signoff series:
  Confirmed
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-azure package in Ubuntu:
  Invalid
Status in linux-azure source package in Xenial:
  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: 1842828
  packages:
main: linux-azure
meta: linux-meta-azure
signed: linux-signed-azure
  phase: Ready for Testing
  phase-changed: Friday, 06. September 2019 05:48 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
regression-testing: Ongoing -- testing in progress
stakeholder-signoff: Stalled -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
trusty/linux-azure: bug 1842819, bug 1842585
xenial/linux-azure-edge: bug 1842584
xenial/linux-azure/azure-kernel: bug 1842583
  variant: debs

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

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

[Anthony Wong]

** Changed in: hwe-next
   Status: New => Fix Released

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

Title:
  Intel ethernet I219 may wrongly detect connection speed as 10Mbps

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

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 1840882] Re: [SRU][B-OEM-OSP1/D/E] reduce s2idle power consumption when BIOS uses shared power resources

[Anthony Wong]

** Changed in: hwe-next
   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/1840882

Title:
  [SRU][B-OEM-OSP1/D/E] reduce s2idle power consumption when BIOS uses
  shared power resources

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

Bug description:
  SRU justification:

  [Impact]
  When system goes to suspend-to idle, it's power consumption is around 4+ w.

  [Fix]
  Some TBT and other ACPI devices share the same power resource, when system 
goes to s2idle.
  PME polling thread continue bringing up devices to D0 mode.
  Use cached ACPI device power state will avoid this issue.

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

  [Regression Potential]
  Medium, upstream patches cherry-picked.

  Since these hareware is only supported by 5.0+ kernel, I set B-OEM-
  OSP1 and disco+ kernel tag.

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

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

[Kernel-packages] [Bug 1836916] Re: alsa/hdmi: add icelake hdmi audio support for a Dell machine

[Anthony Wong]

** Changed in: hwe-next
   Status: New => 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/1836916

Title:
  alsa/hdmi: add icelake hdmi audio support for a Dell machine

Status in HWE Next:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem-osp1 package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  Won't Fix
Status in linux-oem-osp1 source package in Bionic:
  Fix Released
Status in linux source package in Disco:
  Fix Released
Status in linux-oem-osp1 source package in Disco:
  Fix Released

Bug description:
  [Impact]
  On a Dell icelake platform, the hdmi audio doesn't work at all, when users
  plug hdmi cable, they can't find hdmi audio from gnome-sound-setting.

  [Fix]
  add icl hdmi audio id and related support patch to alsa driver.

  [Test Case]
  after applying the patchset, we plug hdmi cable and the hdmi audio shows up
  in the sound-setting and works well, after unplugging the cable, the hdmi
  audio disappears as expected.

  [Regression Risk]
  Low. this patchset is specific to a icl hdmi audio codec.

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

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

[Kernel-packages] [Bug 1837963] Re: alsa/hda: neither mute led nor mic-mute led work on several Lenovo laptops

[Anthony Wong]

** Changed in: hwe-next
   Status: New => 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/1837963

Title:
  alsa/hda: neither mute led nor mic-mute led work on several Lenovo
  laptops

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

Bug description:
  
  [Impact]
  We have a couple of lenovo laptops which have conexant codec, the 
mute/mic-mute
  doesn't work on these machines.

  [Fix]
  Without this patch, the generic driver will be in use for this codec, generic
  driver doesn't apply any fixup for those machines, to let the led work, we 
need
  to apply fixup, so change the code to let patch_conexant.c drive hw.

  [Test Case]
  After booting up, please mute/mic-mute hotkeys, the led can turn on/off.

  [Regression Risk]
  Low. It is specific to the conexant codec with ID 1f86.

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

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

[Kernel-packages] [Bug 1840882] Re: [SRU][B-OEM-OSP1/D/E] reduce s2idle power consumption when BIOS uses shared power resources

[Anthony Wong]

** Changed in: hwe-next
   Status: In Progress => Invalid

** Changed in: hwe-next
   Status: Invalid => 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/1840882

Title:
  [SRU][B-OEM-OSP1/D/E] reduce s2idle power consumption when BIOS uses
  shared power resources

Status in HWE Next:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Disco:
  Fix Committed

Bug description:
  SRU justification:

  [Impact]
  When system goes to suspend-to idle, it's power consumption is around 4+ w.

  [Fix]
  Some TBT and other ACPI devices share the same power resource, when system 
goes to s2idle.
  PME polling thread continue bringing up devices to D0 mode.
  Use cached ACPI device power state will avoid this issue.

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

  [Regression Potential]
  Medium, upstream patches cherry-picked.

  Since these hareware is only supported by 5.0+ kernel, I set B-OEM-
  OSP1 and disco+ kernel tag.

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

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

[Kernel-packages] [Bug 1843018] Re: 5.0.0-27-generic: /proc//maps: Pathnames are '/' inside a container

[Marc Wittke]

confirmed to break on 5.0.0-1018-azure, last known good version is
5.0.0-1016-azure

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

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

Title:
  5.0.0-27-generic: /proc//maps: Pathnames are '/' inside a
  container

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

Bug description:
  Using kernel 5.0.0-27-generic on Ubuntu 18.04 in a container, every
  pathname in /proc//maps is / instead of the mapped file path.

  This appears to be a regression in 5.0.0-27-generic; it works on
  5.0.0-25-generic. The problem can be reproduced in various Ubuntu
  releases, e.g. 18.04 and 19.04.

  5.0.0-25-generic (working):

  $ sudo docker run ubuntu cat /proc/1/maps
  56324a3f5000-56324a3fd000 r-xp  fc:01 665673 
/bin/cat
  56324a5fc000-56324a5fd000 r--p 7000 fc:01 665673 
/bin/cat
  56324a5fd000-56324a5fe000 rw-p 8000 fc:01 665673 
/bin/cat
  56324a8eb000-56324a90c000 rw-p  00:00 0  
[heap]
  7f8ab5f91000-7f8ab6178000 r-xp  fc:01 666073 
/lib/x86_64-linux-gnu/libc-2.27.so
  7f8ab6178000-7f8ab6378000 ---p 001e7000 fc:01 666073 
/lib/x86_64-linux-gnu/libc-2.27.so
  7f8ab6378000-7f8ab637c000 r--p 001e7000 fc:01 666073 
/lib/x86_64-linux-gnu/libc-2.27.so
  7f8ab637c000-7f8ab637e000 rw-p 001eb000 fc:01 666073 
/lib/x86_64-linux-gnu/libc-2.27.so
  7f8ab637e000-7f8ab6382000 rw-p  00:00 0
  7f8ab6382000-7f8ab63a9000 r-xp  fc:01 666055 
/lib/x86_64-linux-gnu/ld-2.27.so
  7f8ab6583000-7f8ab65a7000 rw-p  00:00 0
  7f8ab65a9000-7f8ab65aa000 r--p 00027000 fc:01 666055 
/lib/x86_64-linux-gnu/ld-2.27.so
  7f8ab65aa000-7f8ab65ab000 rw-p 00028000 fc:01 666055 
/lib/x86_64-linux-gnu/ld-2.27.so
  7f8ab65ab000-7f8ab65ac000 rw-p  00:00 0
  7ffc25954000-7ffc25975000 rw-p  00:00 0  
[stack]
  7ffc259f1000-7ffc259f4000 r--p  00:00 0  
[vvar]
  7ffc259f4000-7ffc259f5000 r-xp  00:00 0  
[vdso]
  ff60-ff601000 r-xp  00:00 0  
[vsyscall]

  5.0.0-27-generic (broken):

  $ sudo docker run ubuntu cat /proc/1/maps
  55de0e052000-55de0e05a000 r-xp  fc:01 665673 /
  55de0e259000-55de0e25a000 r--p 7000 fc:01 665673 /
  55de0e25a000-55de0e25b000 rw-p 8000 fc:01 665673 /
  55de0fcb3000-55de0fcd4000 rw-p  00:00 0  
[heap]
  7f7a8d881000-7f7a8da68000 r-xp  fc:01 666073 /
  7f7a8da68000-7f7a8dc68000 ---p 001e7000 fc:01 666073 /
  7f7a8dc68000-7f7a8dc6c000 r--p 001e7000 fc:01 666073 /
  7f7a8dc6c000-7f7a8dc6e000 rw-p 001eb000 fc:01 666073 /
  7f7a8dc6e000-7f7a8dc72000 rw-p  00:00 0
  7f7a8dc72000-7f7a8dc99000 r-xp  fc:01 666055 /
  7f7a8de73000-7f7a8de97000 rw-p  00:00 0
  7f7a8de99000-7f7a8de9a000 r--p 00027000 fc:01 666055 /
  7f7a8de9a000-7f7a8de9b000 rw-p 00028000 fc:01 666055 /
  7f7a8de9b000-7f7a8de9c000 rw-p  00:00 0
  7ffc744bd000-7ffc744de000 rw-p  00:00 0  
[stack]
  7ffc7452d000-7ffc7453 r--p  00:00 0  
[vvar]
  7ffc7453-7ffc74531000 r-xp  00:00 0  
[vdso]

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

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

[Kernel-packages] [Bug 1818407] Re: Cant access emmc, error -84

[Óvári]

Tried with the latest "generic" kernel, i.e. 5.2.11.

Once you reproduced it, reboot setting eMMC Max Speed to HS200, and run:
   journalctl -kb -1 | nc termbin.com 
to post your kernel log from the last but one (-1) boot (the one where
the eMMC failed) to termbin.com. Then send along the termbin.com URL
that was returned on the terminal and update your bug report with your
new findings (affected mainline kernel version).

It doesn't seem to show the failed boot. Perhaps this is due to not
being able to access the eMMC?

Attaching photos of the display.

Attached is 2 of 2.

** Attachment added: "hs400_2.jpg"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818407/+attachment/5287922/+files/hs400_2.jpg

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

Title:
  Cant access emmc, error -84

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Greetings!

  I just got my new convertible(Asus TP202NAS, brand new) and wanted to install 
kubuntu 18.10 onto the internal storage, only to find that it cant see it. In 
dmesg i only got these two error:
  mc0: mmc_select_hs400 failed, error -84
  mc0: error -84 whilst initializing mmc card

  Tried to google around for a solution but i didnt found any solution
  to this, also tried the kubuntu IRC channel but didnt got any luck
  there too

  
  /EDIT
  Submitted from a live session.

  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: ubuntu-release-upgrader-core 1:18.10.11
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  Uname: Linux 4.18.0-10-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  CasperVersion: 1.399
  CrashDB: ubuntu
  Date: Sun Mar  3 13:59:13 2019
  LiveMediaBuild: Kubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.2)
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubuntu-release-upgrader
  Symptom: ubuntu-release-upgrader
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  kubuntu3661 F pulseaudio
  CasperVersion: 1.394
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 18.04
  LiveMediaBuild: Kubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210)
  Lsusb:
   Bus 002 Device 003: ID 0781:5581 SanDisk Corp. Ultra
   Bus 002 Device 002: ID 05e3:0747 Genesys Logic, Inc. 
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 13d3:3501 IMC Networks 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. TP202NAS
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz 
file=/cdrom/preseed/username.seed boot=casper maybe-ubiquity quiet splash ---
  ProcVersionSignature: Ubuntu 4.18.0-15.16~18.04.1-generic 4.18.20
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-15-generic N/A
   linux-backports-modules-4.18.0-15-generic  N/A
   linux-firmware 1.173.3
  Tags:  bionic
  Uname: Linux 4.18.0-15-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/19/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: TP202NAS.209
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: TP202NAS
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No  Asset  Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrTP202NAS.209:bd07/19/2018:svnASUSTeKCOMPUTERINC.:pnTP202NAS:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnTP202NAS:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct31:cvr1.0:
  dmi.product.family: VivoBook Flip
  dmi.product.name: TP202NAS
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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

[Kernel-packages] [Bug 1818407] Re: Cant access emmc, error -84

[Óvári]

Tried with the latest "generic" kernel, i.e. 5.2.11.

Once you reproduced it, reboot setting eMMC Max Speed to HS200, and run:
   journalctl -kb -1 | nc termbin.com 
to post your kernel log from the last but one (-1) boot (the one where
the eMMC failed) to termbin.com. Then send along the termbin.com URL
that was returned on the terminal and update your bug report with your
new findings (affected mainline kernel version).

It doesn't seem to show the failed boot. Perhaps this is due to not
being able to access the eMMC?

Attaching photos of the display.

Attached is 1 of 2.

** Attachment added: "hs400_1.jpg"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818407/+attachment/5287921/+files/hs400_1.jpg

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

Title:
  Cant access emmc, error -84

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Greetings!

  I just got my new convertible(Asus TP202NAS, brand new) and wanted to install 
kubuntu 18.10 onto the internal storage, only to find that it cant see it. In 
dmesg i only got these two error:
  mc0: mmc_select_hs400 failed, error -84
  mc0: error -84 whilst initializing mmc card

  Tried to google around for a solution but i didnt found any solution
  to this, also tried the kubuntu IRC channel but didnt got any luck
  there too

  
  /EDIT
  Submitted from a live session.

  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: ubuntu-release-upgrader-core 1:18.10.11
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  Uname: Linux 4.18.0-10-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  CasperVersion: 1.399
  CrashDB: ubuntu
  Date: Sun Mar  3 13:59:13 2019
  LiveMediaBuild: Kubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.2)
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubuntu-release-upgrader
  Symptom: ubuntu-release-upgrader
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  kubuntu3661 F pulseaudio
  CasperVersion: 1.394
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 18.04
  LiveMediaBuild: Kubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210)
  Lsusb:
   Bus 002 Device 003: ID 0781:5581 SanDisk Corp. Ultra
   Bus 002 Device 002: ID 05e3:0747 Genesys Logic, Inc. 
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 13d3:3501 IMC Networks 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. TP202NAS
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz 
file=/cdrom/preseed/username.seed boot=casper maybe-ubiquity quiet splash ---
  ProcVersionSignature: Ubuntu 4.18.0-15.16~18.04.1-generic 4.18.20
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-15-generic N/A
   linux-backports-modules-4.18.0-15-generic  N/A
   linux-firmware 1.173.3
  Tags:  bionic
  Uname: Linux 4.18.0-15-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/19/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: TP202NAS.209
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: TP202NAS
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No  Asset  Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrTP202NAS.209:bd07/19/2018:svnASUSTeKCOMPUTERINC.:pnTP202NAS:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnTP202NAS:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct31:cvr1.0:
  dmi.product.family: VivoBook Flip
  dmi.product.name: TP202NAS
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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

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

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

Title:
  Oops when Kerberos credentials are invalid

Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Disco:
  In Progress

Bug description:
  There's a bug in Linux Kernel 5.0 which is triggered by invalid
  credentials when the NFS clients is trying to aquire them via GSSD.
  This affects NFS-Shares that are protected by krb5* security. They
  become unusable until the system is re-booted. The problem is quite
  severe on terminal servers with multiple users - some of them not
  caring about refreshing their kerberos tickets.

  A fix is available here:

  


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

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

[Kernel-packages] [Bug 1842037] Re: Oops when Kerberos credentials are invalid

[Matthew Ruffell]

Hi Frank,

The test kernel has built, and I have tested it to ensure it boots, but
I now need you to verify that the backported patches fix the issue that
you are having.

Can you please install the test kernel onto a system which is having
problems with NFS clients that are connecting with invalid kerberos
credentials?

Please note this kernel is NOT SUPPORTED by Canonical, and is for
TESTING PURPOSES ONLY. ONLY Install in a dedicated test environment.

Instructions to install (on a bionic system):

1) sudo add-apt-repository ppa:mruffell/sf241068-test
2) sudo apt-get update
3) sudo apt install linux-image-unsigned-5.0.0-27-generic 
linux-headers-5.0.0-27-generic linux-headers-5.0.0-27 
linux-modules-5.0.0-27-generic linux-modules-extra-5.0.0-27-generic
4) reboot
5) uname -rv
5.0.0-27-generic #28~18.04.1+hf241068v20190910b2-Ubuntu SMP Tue Sep 10 06:53:53 
U

If you get output different from above then you need to edit grub
configuration to boot the correct kernel. If you are asked to abort the
kernel install due to removing the running kernel, say no.

This kernel contains the below patches you requested:

https://paste.ubuntu.com/p/BPD3PzmZ97/
https://paste.ubuntu.com/p/74n7nq5Wfj/

Please test the kernel and let me know if it fixes your problem. If you
could also provide a stack trace or sosreport of the original issue,
that would be good as well.

Let me know if you have any questions,

Thanks,
Matthew

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

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

** Also affects: linux-meta-hwe (Ubuntu Disco)
   Importance: Undecided
   Status: New

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

** Changed in: linux-meta-hwe (Ubuntu Disco)
   Status: New => Invalid

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

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

** Changed in: linux (Ubuntu Disco)
 Assignee: (unassigned) => Matthew Ruffell (mruffell)

** No longer affects: linux-meta-hwe (Ubuntu)

** No longer affects: linux-meta-hwe (Ubuntu Disco)

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

Title:
  Oops when Kerberos credentials are invalid

Status in linux package in Ubuntu:
  New
Status in linux source package in Disco:
  In Progress

Bug description:
  There's a bug in Linux Kernel 5.0 which is triggered by invalid
  credentials when the NFS clients is trying to aquire them via GSSD.
  This affects NFS-Shares that are protected by krb5* security. They
  become unusable until the system is re-booted. The problem is quite
  severe on terminal servers with multiple users - some of them not
  caring about refreshing their kerberos tickets.

  A fix is available here:

  


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

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

[Kernel-packages] [Bug 1843296] Re: ZFS auto scrub after upgrade to Xubuntu 19.10

[BertN45]

I have two datapools one in the begin of the HDD for the Host OSes and
Virtual Machines and one at the end for data, music, family videos and
relatively large old archives. The throughput at the begin of the HDD is
often twice the throughput at the end of the HDD, so I have a very good
reason to put the Host OSes and Virtual Machines at the begin of a HDD.

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

Title:
  ZFS auto scrub after upgrade to Xubuntu 19.10

Status in zfs-linux package in Ubuntu:
  New

Bug description:
  I have upgraded my dual boot laptop (Xubuntu 19.04 on ZFS) to 19.10, I
  only had a minor problem:

  The system on boot did start scrub of all datapools automatically, that 
was unexpected and it took a couple of minutes before I realized, why the 
system was that effing slow. There is a small chance that the monthly 
auto-scrub was due. If it is part of the upgrade do not do it without at least 
a notification and a confirmation of the user. Never start it during the boot 
process, please wait a few minutes. The same remarks are valid for the monthly 
default auto-scrub. 
  Even not Microsoft is allowed to monopolize my system for a long time without 
telling and without my permission, that is partly why I moved to Linux :) :)

  I detected it relatively fast on my conky display, but else?? 
  Of course I stopped the scrub of the two datapools on the same SSHD and 
restarted it one by one. 
  I'm more happy with the SSHD using ZFS and LZ4 compression.

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

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

[Kernel-packages] [Bug 1842587] Re: xenial/linux-azure: 4.15.0-1057.62 -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: 1842828
  packages:
main: linux-azure
meta: linux-meta-azure
signed: linux-signed-azure
  phase: Ready for Testing
  phase-changed: Friday, 06. September 2019 05:48 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
regression-testing: Ongoing -- testing in progress
stakeholder-signoff: Stalled -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
-   trusty/linux-azure: bug 1842819, bug 1842585
+   trusty/linux-azure: bug 1842585, bug 1842819
xenial/linux-azure-edge: bug 1842584
xenial/linux-azure/azure-kernel: bug 1842583
  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/1842587

Title:
  xenial/linux-azure: 4.15.0-1057.62 -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:
  New
Status in Kernel SRU Workflow stakeholder-signoff series:
  Confirmed
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-azure package in Ubuntu:
  Invalid
Status in linux-azure source package in Xenial:
  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: 1842828
  packages:
main: linux-azure
meta: linux-meta-azure
signed: linux-signed-azure
  phase: Ready for Testing
  phase-changed: Friday, 06. September 2019 05:48 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
regression-testing: Ongoing -- testing in progress
stakeholder-signoff: Stalled -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
trusty/linux-azure: bug 1842585, bug 1842819
xenial/linux-azure-edge: bug 1842584
xenial/linux-azure/azure-kernel: bug 1842583
  variant: debs

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

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

[Kernel-packages] [Bug 1842608] Re: xenial/linux: 4.4.0-162.190 -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 --
  packages:
main: linux
meta: linux-meta
signed: linux-signed
  phase: Holding before Promote to Proposed
  phase-changed: Wednesday, 04. September 2019 07:52 UTC
  reason:
promote-to-proposed: Pending -- builds not complete in ppa 
main:failed,meta:depwait
  trackers:
trusty/linux-aws: bug 1842793, bug 1842606
-   trusty/linux-lts-xenial: bug 1842794, bug 1842607
+   trusty/linux-lts-xenial: bug 1842607, bug 1842794
xenial/linux-aws: bug 1842597
xenial/linux-fips: bug 1842605
xenial/linux-kvm: bug 1842598
xenial/linux-raspi2: bug 1842600
xenial/linux-snapdragon: bug 1842603
xenial/linux/pc-kernel: bug 1842595
  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/1842608

Title:
  xenial/linux: 4.4.0-162.190 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  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 --
  packages:
main: linux
meta: linux-meta
signed: linux-signed
  phase: Holding before Promote to Proposed
  phase-changed: Wednesday, 04. September 2019 07:52 UTC
  reason:
promote-to-proposed: Pending -- builds not complete in ppa 
main:failed,meta:depwait
  trackers:
trusty/linux-aws: bug 1842793, bug 1842606
trusty/linux-lts-xenial: bug 1842607, bug 1842794
xenial/linux-aws: bug 1842597
xenial/linux-fips: bug 1842605
xenial/linux-kvm: bug 1842598
xenial/linux-raspi2: bug 1842600
xenial/linux-snapdragon: bug 1842603
xenial/linux/pc-kernel: bug 1842595
  variant: debs

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

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

[Kernel-packages] [Bug 1843296] Re: ZFS auto scrub after upgrade to Xubuntu 19.10

[Richard Laager]

I’m not aware of anything new starting scrubs. Scrubs are throttled and
usually the complaint is that they are throttled too much, not too
little. Having two pools on the same disk is likely the issue. That
should be avoided, with the exception of a small boot pool on the same
disk as the root pool for root on ZFS setups. Is that your multiple
pools situation, or are you doing something else?

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

Title:
  ZFS auto scrub after upgrade to Xubuntu 19.10

Status in zfs-linux package in Ubuntu:
  New

Bug description:
  I have upgraded my dual boot laptop (Xubuntu 19.04 on ZFS) to 19.10, I
  only had a minor problem:

  The system on boot did start scrub of all datapools automatically, that 
was unexpected and it took a couple of minutes before I realized, why the 
system was that effing slow. There is a small chance that the monthly 
auto-scrub was due. If it is part of the upgrade do not do it without at least 
a notification and a confirmation of the user. Never start it during the boot 
process, please wait a few minutes. The same remarks are valid for the monthly 
default auto-scrub. 
  Even not Microsoft is allowed to monopolize my system for a long time without 
telling and without my permission, that is partly why I moved to Linux :) :)

  I detected it relatively fast on my conky display, but else?? 
  Of course I stopped the scrub of the two datapools on the same SSHD and 
restarted it one by one. 
  I'm more happy with the SSHD using ZFS and LZ4 compression.

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

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

[Kernel-packages] [Bug 1843298] Re: Upgrade of datapool to ZFS 0.8 creates a problem if dual booting

[Richard Laager]

This is a known issue which will hopefully be improved by 20.04 or so.

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

Title:
  Upgrade of datapool to ZFS 0.8 creates a problem if dual booting

Status in zfs-linux package in Ubuntu:
  New

Bug description:
  I have upgraded my dual boot laptop (Xubuntu 19.04 on ZFS) to 19.10, I
  only had a minor problems:

  The system started scrubbing the exisisting datapools.
  In the scrub I have been notified, that my datapool did not support all new 
features and that I had to upgrade the datapool. Of course I followed that 
advice enthusiastically and now the second 18.04.3 OS does not recognize the 
upgraded datapool anymore. I found out I can’t disable the culprit features.

  I think there should be a more specific warning in the "zpool upgrade"
  for stupids like me. Only upgrade the datapool, if all OSes on the PC
  have been upgraded to zfs 0.8.

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

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

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

Title:
  i915 enable_rc6=0 not respected

Status in linux package in Ubuntu:
  Confirmed

Bug description:
   i915 enable_rc6=0 is not respected.  I want to disable rc6 power savings 
because it is a tower
  machine with a kilowatt supply and lots of fan so I don't give a rip about 
power consumption, I do not
  want my display interrupted while I'm watching a movie or video and when 
monitoring things I want to
  be able to walk by the monitor and see what is going on without having to go 
up and wiggle the mouse
  and wait for it to wake up and my monitor to sync.

   I have an i7-9700k on an Asus Z390A Prime motherboard.  I have
  enable RC6 disabled in the BIOS so BIOS isn't enabling it, in
  /etc/modprobe.d/i915.conf I have:

   options i915 enable_guc=3 enable_dc=0 enable_rc6=0

   In /etc/default/grub I have:

   GRUB_CMDLINE_LINUX_DEFAULT="quiet splash xdg.force_integrated=1
  modprobe.blacklist=nouveau i915.i915_enable_rc6=0"

   I have done update-grub2 and update-initramfs -u -k all and
  rebooted, but still:

  cat /sys/class/drm/card0/power/rc6_enable
  1

   The kernel totally ignores my instructions and enables the damned
  thing anyway.  ARRGGH!

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: linux-lowlatency 5.0.0.28.29
  ProcVersionSignature: Ubuntu 5.0.0-28.30-lowlatency 5.0.21
  Uname: Linux 5.0.0-28-lowlatency x86_64
  ApportVersion: 2.20.10-0ubuntu27.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nanook 4342 F pulseaudio
  CurrentDesktop: MATE
  Date: Tue Sep 10 16:14:06 2019
  MachineType: System manufacturer System Product Name
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-28-lowlatency 
root=UUID=718970be-1c9c-4b4e-8940-1e26324e158b ro console=tty1 console=ttyS0 
panic=-1
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-28-lowlatency N/A
   linux-backports-modules-5.0.0-28-lowlatency  N/A
   linux-firmware   1.178.4
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/06/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1105
  dmi.board.asset.tag: Default string
  dmi.board.name: PRIME Z390-A
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1105:bd06/06/2019:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEZ390-A:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: ASUS_MB_CNL
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

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

[Kernel-packages] [Bug 1843511] [NEW] i915 enable_rc6=0 not respected

[Robert Dinse]

Public bug reported:

 i915 enable_rc6=0 is not respected.  I want to disable rc6 power savings 
because it is a tower
machine with a kilowatt supply and lots of fan so I don't give a rip about 
power consumption, I do not
want my display interrupted while I'm watching a movie or video and when 
monitoring things I want to
be able to walk by the monitor and see what is going on without having to go up 
and wiggle the mouse
and wait for it to wake up and my monitor to sync.

 I have an i7-9700k on an Asus Z390A Prime motherboard.  I have
enable RC6 disabled in the BIOS so BIOS isn't enabling it, in
/etc/modprobe.d/i915.conf I have:

 options i915 enable_guc=3 enable_dc=0 enable_rc6=0

 In /etc/default/grub I have:

 GRUB_CMDLINE_LINUX_DEFAULT="quiet splash xdg.force_integrated=1
modprobe.blacklist=nouveau i915.i915_enable_rc6=0"

 I have done update-grub2 and update-initramfs -u -k all and
rebooted, but still:

cat /sys/class/drm/card0/power/rc6_enable
1

 The kernel totally ignores my instructions and enables the damned
thing anyway.  ARRGGH!

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: linux-lowlatency 5.0.0.28.29
ProcVersionSignature: Ubuntu 5.0.0-28.30-lowlatency 5.0.21
Uname: Linux 5.0.0-28-lowlatency x86_64
ApportVersion: 2.20.10-0ubuntu27.1
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  nanook 4342 F pulseaudio
CurrentDesktop: MATE
Date: Tue Sep 10 16:14:06 2019
MachineType: System manufacturer System Product Name
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-28-lowlatency 
root=UUID=718970be-1c9c-4b4e-8940-1e26324e158b ro console=tty1 console=ttyS0 
panic=-1
RelatedPackageVersions:
 linux-restricted-modules-5.0.0-28-lowlatency N/A
 linux-backports-modules-5.0.0-28-lowlatency  N/A
 linux-firmware   1.178.4
RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/06/2019
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1105
dmi.board.asset.tag: Default string
dmi.board.name: PRIME Z390-A
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1105:bd06/06/2019:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEZ390-A:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: System Product Name
dmi.product.sku: ASUS_MB_CNL
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer

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


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

Title:
  i915 enable_rc6=0 not respected

Status in linux package in Ubuntu:
  Confirmed

Bug description:
   i915 enable_rc6=0 is not respected.  I want to disable rc6 power savings 
because it is a tower
  machine with a kilowatt supply and lots of fan so I don't give a rip about 
power consumption, I do not
  want my display interrupted while I'm watching a movie or video and when 
monitoring things I want to
  be able to walk by the monitor and see what is going on without having to go 
up and wiggle the mouse
  and wait for it to wake up and my monitor to sync.

   I have an i7-9700k on an Asus Z390A Prime motherboard.  I have
  enable RC6 disabled in the BIOS so BIOS isn't enabling it, in
  /etc/modprobe.d/i915.conf I have:

   options i915 enable_guc=3 enable_dc=0 enable_rc6=0

   In /etc/default/grub I have:

   GRUB_CMDLINE_LINUX_DEFAULT="quiet splash xdg.force_integrated=1
  modprobe.blacklist=nouveau i915.i915_enable_rc6=0"

   I have done update-grub2 and update-initramfs -u -k all and
  rebooted, but still:

  cat /sys/class/drm/card0/power/rc6_enable
  1

   The kernel totally ignores my instructions and enables the damned
  thing anyway.  ARRGGH!

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: linux-lowlatency 5.0.0.28.29
  ProcVersionSignature: Ubuntu 5.0.0-28.30-lowlatency 5.0.21
  Uname: Linux 5.0.0-28-lowlatency x86_64
  ApportVersion: 2.20.10-0ubuntu27.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nanook 4342 F pulseaudio
  CurrentDesktop: MATE
  Date: Tue Sep 10 16:14:06 2019
  MachineType: System manufacturer System Product Name
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-28-lowlatency 
root=UUID=718970be-1c9c-4b4e-8940-1e26324e158b ro console=tty1 console=ttyS0 
panic=-1
  RelatedPackageVersions:
   

[Kernel-packages] [Bug 1759836] Re: systemd-udevd consumes 100% of CPU due to hid2hci udev rule from bluez

[Launchpad Bug Tracker]

This bug was fixed in the package bluez - 5.50-0ubuntu4

---
bluez (5.50-0ubuntu4) eoan; urgency=medium

  * d/p/lp1759836.patch: avoid endless udev events from new bind uevents
(LP: #1759836)

 -- Dan Streetman   Tue, 10 Sep 2019 17:22:37
-0400

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

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

Title:
  systemd-udevd consumes 100% of CPU due to hid2hci udev rule from bluez

Status in linux:
  Confirmed
Status in The Ubuntu Power Consumption Project:
  New
Status in bluez package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Invalid
Status in bluez source package in Bionic:
  In Progress
Status in linux source package in Bionic:
  Invalid
Status in systemd source package in Bionic:
  Invalid
Status in bluez source package in Disco:
  In Progress
Status in linux source package in Disco:
  Invalid
Status in systemd source package in Disco:
  Invalid
Status in bluez source package in Eoan:
  Fix Released
Status in linux source package in Eoan:
  Invalid
Status in systemd source package in Eoan:
  Invalid
Status in bluez package in Debian:
  New

Bug description:
  The systemd-udevd proccess consumes 100% of a thread everytime, but
  i'm not noticing any difference in my computer.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: systemd 237-3ubuntu6
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Mar 29 08:52:54 2018
  InstallationDate: Installed on 2018-03-05 (23 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180304)
  MachineType: Dell Inc. Inspiron N5010
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic 
root=UUID=3c29e292-f1ae-45e1-a0ed-a82524278ce1 ro quiet splash vt.handoff=1
  SourcePackage: systemd
  SystemdDelta:
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /lib/systemd/system/user@.service → 
/lib/systemd/system/user@.service.d/timeout.conf

   2 overridden configuration files found.
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/25/2011
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A12
  dmi.board.name: 08R0GW
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A12
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A12
  dmi.modalias: 
dmi:bvnDellInc.:bvrA12:bd01/25/2011:svnDellInc.:pnInspironN5010:pvrA12:rvnDellInc.:rn08R0GW:rvrA12:cvnDellInc.:ct8:cvrA12:
  dmi.product.name: Inspiron N5010
  dmi.product.version: A12
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1842714] Re: bionic/linux-oem: 4.15.0-1054.63 -proposed tracker

[Ubuntu Kernel Bot]

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

** Changed in: kernel-sru-workflow/certification-testing
   Status: New => Confirmed

** Changed in: kernel-sru-workflow/promote-to-proposed
   Status: Fix Committed => Fix Released

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

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

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

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

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

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1842746
  packages:
lrm: linux-restricted-modules-oem
main: linux-oem
meta: linux-meta-oem
signed: linux-signed-oem
- phase: Promote to Proposed
- phase-changed: Tuesday, 10. September 2019 20:35 UTC
+ phase: Testing
+ phase-changed: Tuesday, 10. September 2019 22:51 UTC
+ proposed-announcement-sent: true
+ proposed-testing-requested: true
  reason:
-   promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror 
sync
+   automated-testing: Ongoing -- testing in progress
+   certification-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-oem in Ubuntu.
https://bugs.launchpad.net/bugs/1842714

Title:
  bionic/linux-oem: 4.15.0-1054.63 -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-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:
  Fix Released
Status in linux-oem package in Ubuntu:
  Invalid
Status in linux-oem 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: 1842746
  packages:
lrm: linux-restricted-modules-oem
main: linux-oem
meta: linux-meta-oem
signed: linux-signed-oem
  phase: Testing
  phase-changed: Tuesday, 10. September 2019 22:51 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
  variant: debs

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

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

[Kernel-packages] [Bug 1843323] Re: Kernel 4.15.0-59 (and onwards) breaks scroll wheel of USB mouse (A4Tech X5-50D)

[Bug Watch Updater]

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

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


On 2019-07-14T17:53:17+00:00 morfikov wrote:

Created attachment 283689
lsusb

I have the following mouse:

$ lsusb
...
Bus 002 Device 005: ID 09da:000a A4Tech Co., Ltd. Optical Mouse Opto 510D / 
OP-620D

It was working well till the kernel 5.1.16. I upgraded the kernel to
5.1.18 and the mouse scroll doesn't work any more. The same issue is
with the kernel 5.2.0 and 5.2.1 . I haven't tested it with the 5.1.17
version.

When I compare the kernel .config file from 5.1.16 and 5.1.18, they're
pretty much the same.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1843323/comments/0


On 2019-07-15T15:30:36+00:00 k-kern-bugzilla wrote:

(In reply to Mikhail Morfikov from comment #0)
> Created attachment 283689 [details]
> lsusb
> 
> I have the following mouse:
> 
> $ lsusb
> ...
> Bus 002 Device 005: ID 09da:000a A4Tech Co., Ltd. Optical Mouse Opto 510D /
> OP-620D
> 
> It was working well till the kernel 5.1.16. I upgraded the kernel to 5.1.18
> and the mouse scroll doesn't work any more. The same issue is with the
> kernel 5.2.0 and 5.2.1 . I haven't tested it with the 5.1.17 version. 
> 
> When I compare the kernel .config file from 5.1.16 and 5.1.18, they're
> pretty much the same.

I can confirm same issue. Fedora 30, 5.1.17-300.fc30.x86_64 kernel, the
same mouse :

$ lsusb
...
Bus 003 Device 002: ID 09da:000a A4Tech Co., Ltd. Optical Mouse Opto 510D 
/OP-620D

First time I supposed that my mouse is gone, but then I rebooted into
older 5.1.16 kernel - and everything works fine there.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1843323/comments/1


On 2019-07-17T14:22:24+00:00 k-kern-bugzilla wrote:

I've been upgraded (F30) into the 5.1.18-300.fc30.x86_64 kernel before a
while, problem still remains. So it has to be something (which occurs)
between 5.1.16 and 5.1.17 and it's not solved yet.

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


On 2019-07-17T18:26:17+00:00 igorkuo wrote:

Applying the following patch may fix this bug: 
https://www.spinics.net/lists/linux-input/msg61859.html.
See also https://bugzilla.kernel.org/show_bug.cgi?id=203369#c7.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1843323/comments/3


On 2019-07-18T15:19:31+00:00 k-kern-bugzilla wrote:

Yes, this patch is working well, as I tested before a while and
confirmed also in RedHat bugzilla there :

https://bugzilla.redhat.com/show_bug.cgi?id=1730762

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1843323/comments/4


On 2019-07-18T17:42:32+00:00 morfikov wrote:

I also can confirm the patch fixes the scroll issue (tested with the
kernel 5.2.1).

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1843323/comments/5


On 2019-07-18T22:55:09+00:00 dithpri wrote:

I can also confirm the patch works, tested on kernel 5.2.0.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1843323/comments/6


On 2019-07-23T19:01:47+00:00 ikalvachev wrote:

This patch fixes the scroll issue for me too.

I'm with fairly old A4Tech X6-005D 
a4tech 0003:09DA:000A.0001: input,hidraw0: USB HID v1.10 Mouse [A4Tech PS/2+USB 
Mouse]

I've tested it on 5.2.1 and 5.2.2.

I hope the patch will make it into 5.2.3.

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


On 2019-07-28T10:09:17+00:00 k-kern-bugzilla wrote:

Could anybody confirm, if this patch is (or isn't yet) included in the
fresh 5.2.4 kernel, please ?

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1843323/comments/8


On 2019-07-28T10:20:32+00:00 igorkuo wrote:

Probably not. You can search for "a4tech" in kernel patch change logs
here: https://cdn.kernel.org/pub/linux/kernel/v5.x/ChangeLog-5.2.4
(replace the version number at the end of this URL to check out other
versions).

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1843323/comments/9

[Kernel-packages] [Bug 1822363] Re: Booting hangs when USB 3.0 Etron EJ168 PCI card is detected

[Mike]

New Ubuntu 18.04 LTS supported kernel 4.15.0-60-generic is again
bootable and USB 3.0 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/1822363

Title:
  Booting hangs when USB 3.0 Etron EJ168 PCI card is detected

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have installed Etron EJ168 PCI USB 3.0 [1B6F:7023] which briliantly works 
in any Windows OS (I use multiboot PC) on my Conroe865PE AGP/PCI Intel 
Kentsfield QX6800 system with classic BIOS (non UEFI).
  There are no devices connected to PCI USB card during boot.

  The desktop Ubuntu 18.04 kernel 4.15.0-46-generic freezes with this
  card during boot (see attached "photo log" with boot and grub
  options). I can't access/login Ubuntu or console. It was checked and
  confirmed on ubuntu-18.04.1-desktop-amd64.iso LIVE CD desktop (with
  acpi=off option too).

  Previously I was used and removed USB 3.0 NEC Renesas upd720200 PCI card 
[1033:0194], which was partially workable under my installation of Ubuntu 18.04 
and Windows. It had problems from time to time with FW load from card on start 
and not detecting USB devices connected even if FW present.
  I tried and also removed USB 3.0 NEC Renesas upd720202 PCI card [1912:0015] 
which also was partially workable in the same way (other card bios and newer 
NEC chip). System was fully bootable with NEC cards.

  The Etron EJ168 works superb on Windows OS's with directly or with hub 
connections with USB devices.
  I can assist in any way to solve this bug as IT Professional.

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

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

[Kernel-packages] [Bug 1843222] Re: Old Linux version booted after upgrade to Ubuntu 19.10

[BertN45]

I did add an entry with two /boot/grub/grub.cfg files and one did
include my 40_custom file. That file did include "This" but in the first
comment line as shown below:

### BEGIN /etc/grub.d/40_custom ###
# This file provides an easy way to add custom menu entries.  Simply type the
# menu entries you want to add after this comment.  Be careful not to change
# the 'exec tail' line above.
menuentry 'Xubuntu 18.04' --class ubuntu --class gnu-linux --class gnu --class 
os $menuentry_id_option 'gnulinux-simple-93b2f0baee676e9a' {

I scanned /boot/grub/grub.cfg on "This" and it only occurs in comment
lines. The grub.cfg.new completely misses those text-includes from
40_custom, as I would expect. But it did include booting from Linux 5.2.

I had the same problem, when upgrading the last of my three Ubuntus,
that one also booted from Linux 5.0. The first upgrade went OK without
problems. Maybe it started to go wrong after I upgraded one of the two
datapools. That datapool could not be mounted or imported anymore. The
second and third upgrade went wrong, any relation?

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

Title:
  Old Linux version booted after upgrade to Ubuntu 19.10

Status in zfs-linux package in Ubuntu:
  New

Bug description:
  I have a triple boot with the following systems:
  - Xubuntu 19.10 from zfs 0.8.1
  - Ubuntu Mate 18.04.3 from zfs 0.7.12
  - Ubuntu 19.10 from ext4

  Upgrading the first system Xubuntu to 19.10 worked fine and I was very happy 
with the almost perfect result and the nice grub-menu.
  Upgrading to Ubuntu 19.10 created the following problems:
  - That system booted after the upgrade to Ubuntu 19.10 in Linux 5.0 with zfs 
0.7.12
  - All grub entries with the ZFS systems disappeared and the whole nice 
grub-menu was gone.

  Running update-grub and grub install; I did see the Linux 5.2 version
  appear, but it still booted from 5.0.

  There were some error messages about mounting/importing during the zfs
  part of the upgrade, but they were the same as the ones during the
  Xubuntu upgrade and that upgrade worked perfectly.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: zfsutils-linux 0.8.1-1ubuntu11
  ProcVersionSignature: Ubuntu 5.0.0-27.28-generic 5.0.21
  Uname: Linux 5.0.0-27-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Sep  9 01:37:21 2019
  InstallationDate: Installed on 2019-03-10 (183 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  SourcePackage: zfs-linux
  UpgradeStatus: Upgraded to eoan on 2019-09-09 (0 days ago)
  modified.conffile..etc.sudoers.d.zfs: [inaccessible: [Errno 13] Permission 
denied: '/etc/sudoers.d/zfs']

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

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

[Kernel-packages] [Bug 1759836] Re: systemd-udevd consumes 100% of CPU due to hid2hci udev rule from bluez

[Dan Streetman]

** Also affects: linux (Ubuntu Eoan)
   Importance: Low
   Status: Invalid

** Also affects: bluez (Ubuntu Eoan)
   Importance: Medium
 Assignee: Dan Streetman (ddstreet)
   Status: In Progress

** Also affects: systemd (Ubuntu Eoan)
   Importance: Undecided
   Status: Invalid

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

** Also affects: bluez (Ubuntu Disco)
   Importance: Undecided
   Status: New

** Also affects: systemd (Ubuntu Disco)
   Importance: Undecided
   Status: New

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

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

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

** Changed in: systemd (Ubuntu Disco)
   Status: New => Invalid

** Changed in: systemd (Ubuntu Bionic)
   Status: New => Invalid

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

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

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

** Changed in: bluez (Ubuntu Disco)
   Status: New => In Progress

** Changed in: bluez (Ubuntu Disco)
 Assignee: (unassigned) => Dan Streetman (ddstreet)

** Changed in: bluez (Ubuntu Bionic)
   Importance: Undecided => Medium

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

** Changed in: bluez (Ubuntu Bionic)
 Assignee: (unassigned) => Dan Streetman (ddstreet)

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

Title:
  systemd-udevd consumes 100% of CPU due to hid2hci udev rule from bluez

Status in linux:
  Confirmed
Status in The Ubuntu Power Consumption Project:
  New
Status in bluez package in Ubuntu:
  In Progress
Status in linux package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Invalid
Status in bluez source package in Bionic:
  In Progress
Status in linux source package in Bionic:
  Invalid
Status in systemd source package in Bionic:
  Invalid
Status in bluez source package in Disco:
  In Progress
Status in linux source package in Disco:
  Invalid
Status in systemd source package in Disco:
  Invalid
Status in bluez source package in Eoan:
  In Progress
Status in linux source package in Eoan:
  Invalid
Status in systemd source package in Eoan:
  Invalid
Status in bluez package in Debian:
  New

Bug description:
  The systemd-udevd proccess consumes 100% of a thread everytime, but
  i'm not noticing any difference in my computer.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: systemd 237-3ubuntu6
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Mar 29 08:52:54 2018
  InstallationDate: Installed on 2018-03-05 (23 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180304)
  MachineType: Dell Inc. Inspiron N5010
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic 
root=UUID=3c29e292-f1ae-45e1-a0ed-a82524278ce1 ro quiet splash vt.handoff=1
  SourcePackage: systemd
  SystemdDelta:
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /lib/systemd/system/user@.service → 
/lib/systemd/system/user@.service.d/timeout.conf

   2 overridden configuration files found.
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/25/2011
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A12
  dmi.board.name: 08R0GW
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A12
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A12
  dmi.modalias: 
dmi:bvnDellInc.:bvrA12:bd01/25/2011:svnDellInc.:pnInspironN5010:pvrA12:rvnDellInc.:rn08R0GW:rvrA12:cvnDellInc.:ct8:cvrA12:
  dmi.product.name: Inspiron N5010
  dmi.product.version: A12
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1839966] Re: bionic/linux-oracle-edge: -proposed tracker

[Andy Whitcroft]

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

** This bug is no longer a duplicate of bug 1840826
   bionic/linux-oracle-edge: 5.0.0-1001.2~18.04.1 -proposed tracker
** This bug has been marked a duplicate of bug 1842843
   bionic/linux-oracle-edge:  -proposed tracker

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

Title:
  bionic/linux-oracle-edge:  -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:
  New
Status in Kernel SRU Workflow prepare-package-meta series:
  New
Status in Kernel SRU Workflow prepare-package-signed series:
  New
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Invalid

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 --
  packages:
main: linux-oracle-edge
meta: linux-meta-oracle-edge
signed: linux-signed-oracle-edge
  phase: Holding before Packaging
  phase-changed: Tuesday, 13. August 2019 10:12 UTC
  reason:
prepare-package: Holding -- waiting for master bug
  variant: debs

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

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

[Kernel-packages] [Bug 1840826] Re: bionic/linux-oracle-edge: 5.0.0-1001.2~18.04.1 -proposed tracker

[Andy Whitcroft]

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

** This bug has been marked a duplicate of bug 1842843
   bionic/linux-oracle-edge:  -proposed tracker

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

Title:
  bionic/linux-oracle-edge: 5.0.0-1001.2~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:
  Incomplete
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:
  Invalid

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: 1842155
  packages:
main: linux-oracle-edge
meta: linux-meta-oracle-edge
signed: linux-signed-oracle-edge
  phase: Promote to Proposed
  phase-changed: Thursday, 05. September 2019 21:21 UTC
  reason:
promote-to-proposed: Alert -- packages no longer available
  variant: debs

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

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

[Kernel-packages] [Bug 1842714] Re: bionic/linux-oem: 4.15.0-1054.63 -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: 1842746
  packages:
lrm: linux-restricted-modules-oem
main: linux-oem
meta: linux-meta-oem
signed: linux-signed-oem
  phase: Promote to Proposed
  phase-changed: Tuesday, 10. September 2019 20:35 UTC
  reason:
-   promote-to-proposed: Ongoing -- package copied to Proposed signed:building
+   promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror 
sync
  variant: debs

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

Title:
  bionic/linux-oem: 4.15.0-1054.63 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-lrm series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Committed
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-oem package in Ubuntu:
  Invalid
Status in linux-oem source package in Bionic:
  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: 1842746
  packages:
lrm: linux-restricted-modules-oem
main: linux-oem
meta: linux-meta-oem
signed: linux-signed-oem
  phase: Promote to Proposed
  phase-changed: Tuesday, 10. September 2019 20:35 UTC
  reason:
promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror 
sync
  variant: debs

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

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

[Kernel-packages] [Bug 1842772] Re: xenial/linux-oracle: 4.15.0-1023.26~16.04.1 -proposed tracker

[Ubuntu Kernel Bot]

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


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

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

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

Title:
  xenial/linux-oracle: 4.15.0-1023.26~16.04.1 -proposed tracker

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

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

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

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1842773
  packages:
main: linux-oracle
meta: linux-meta-oracle
signed: linux-signed-oracle
  phase: Complete
  phase-changed: Tuesday, 10. September 2019 20:16 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  replaces: bug 1842724
  variant: debs

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

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

[Kernel-packages] [Bug 1843118] Re: bionic/linux-gcp: 4.15.0-1042.45 -proposed tracker

[Ubuntu Kernel Bot]

** Changed in: kernel-sru-workflow/promote-to-updates
   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 --
  boot-testing-requested: true
  kernel-stable-master-bug: 1842746
  packages:
main: linux-gcp
meta: linux-meta-gcp
signed: linux-signed-gcp
- phase: Promote to Updates
- phase-changed: Tuesday, 10. September 2019 21:05 UTC
+ phase: Holding before Promote to Security
+ phase-changed: Tuesday, 10. September 2019 21:16 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
- reason:
-   promote-to-updates: Ongoing -- packages not yet published
  replaces: bug 1840806
  trackers:
bionic/linux-gcp-edge: bug 1840824
bionic/linux-gcp/gcp-kernel: bug 1843117
  variant: debs

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

Title:
  bionic/linux-gcp: 4.15.0-1042.45 -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-lrm series:
  Invalid
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:
  Fix Released
Status in Kernel SRU Workflow regression-testing series:
  Invalid
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux-gcp package in Ubuntu:
  Invalid
Status in linux-gcp source package in Bionic:
  Fix Released

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

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

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1842746
  packages:
main: linux-gcp
meta: linux-meta-gcp
signed: linux-signed-gcp
  phase: Holding before Promote to Security
  phase-changed: Tuesday, 10. September 2019 21:16 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  replaces: bug 1840806
  trackers:
bionic/linux-gcp-edge: bug 1840824
bionic/linux-gcp/gcp-kernel: bug 1843117
  variant: debs

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

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

[Kernel-packages] [Bug 1843323] Re: Kernel 4.15.0-59 (and onwards) breaks scroll wheel of USB mouse (A4Tech X5-50D)

[Christian Schrötter]

** Attachment removed: "CurrentDmesg.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1843323/+attachment/5287557/+files/CurrentDmesg.txt

** Attachment removed: "UdevDb.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1843323/+attachment/5287567/+files/UdevDb.txt

** Attachment removed: "Lsusb.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1843323/+attachment/5287560/+files/Lsusb.txt

** Attachment removed: "Lspci.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1843323/+attachment/5287559/+files/Lspci.txt

** Attachment removed: "ProcCpuinfo.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1843323/+attachment/5287561/+files/ProcCpuinfo.txt

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

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

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

Title:
  Kernel 4.15.0-59 (and onwards) breaks scroll wheel of USB mouse
  (A4Tech X5-50D)

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

Bug description:
  The latest kernel upgrade makes it impossible to use the scroll wheel
  of one specific mouse.

   Affected Ubuntu release: 18.04.3
   Last working kernel version: 4.15.0-58
   Affected kernel versions: 4.15.0-59, 4.15.0-60, 4.15.0-62, …

  I've several X5-50D input devices, tested at three different systems,
  connected via USB2 and USB3. I can reproduce the issue at all machines
  at any time. All others mouses are working fine. When booting the old
  kernel the problem is gone.

  Please tell me what details are required to trace this issue down. I
  should be able to test custom patches and build packages, if required.

  > usb 3-11: new low-speed USB device number 5 using xhci_hcd
  > usb 3-11: New USB device found, idVendor=09da, idProduct=000a
  > usb 3-11: New USB device strings: Mfr=1, Product=2, SerialNumber=0
  > usb 3-11: Product: PS/2+USB Mouse
  > usb 3-11: Manufacturer: A4Tech
  > input: A4Tech PS/2+USB Mouse as 
/devices/pci:00/:00:14.0/usb3/3-11/3-11:1.0/0003:09DA:000A.0005/input/input21
  > a4tech 0003:09DA:000A.0005: input,hidraw4: USB HID v1.10 Mouse [A4Tech 
PS/2+USB Mouse] on usb-:00:14.0-11/input0

  > Bus 003 Device 004: ID 09da:000a A4Tech Co., Ltd. Optical Mouse Opto 510D / 
OP-620D
  > Device Descriptor:
  >   bLength18
  >   bDescriptorType 1
  >   bcdUSB   1.10
  >   bDeviceClass0 (Defined at Interface level)
  >   bDeviceSubClass 0
  >   bDeviceProtocol 0
  >   bMaxPacketSize0 8
  >   idVendor   0x09da A4Tech Co., Ltd.
  >   idProduct  0x000a Optical Mouse Opto 510D / OP-620D
  >   bcdDevice1.05
  >   iManufacturer   1 A4Tech
  >   iProduct2 USB Mouse
  >   iSerial 0
  >   bNumConfigurations  1
  >   Configuration Descriptor:
  > bLength 9
  > bDescriptorType 2
  > wTotalLength   34
  > bNumInterfaces  1
  > bConfigurationValue 1
  > iConfiguration  0
  > bmAttributes 0xa0
  >   (Bus Powered)
  >   Remote Wakeup
  > MaxPower  100mA
  > Interface Descriptor:
  >   bLength 9
  >   bDescriptorType 4
  >   bInterfaceNumber0
  >   bAlternateSetting   0
  >   bNumEndpoints   1
  >   bInterfaceClass 3 Human Interface Device
  >   bInterfaceSubClass  1 Boot Interface Subclass
  >   bInterfaceProtocol  2 Mouse
  >   iInterface  0
  > HID Device Descriptor:
  >   bLength 9
  >   bDescriptorType33
  >   bcdHID   1.10
  >   bCountryCode0 Not supported
  >   bNumDescriptors 1
  >   bDescriptorType34 Report
  >   wDescriptorLength  48
  >  Report Descriptors:
  >** UNAVAILABLE **
  >   Endpoint Descriptor:
  > bLength 7
  > bDescriptorType 5
  > bEndpointAddress 0x81  EP 1 IN
  > bmAttributes3
  >   Transfer TypeInterrupt
  >   Synch Type   None
  >   Usage Type   Data
  > wMaxPacketSize 0x0008  1x 8 bytes
  > bInterval  10
  > Device Status: 0x
  >   (Bus Powered)

  ---

  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=e505eab0-02d8-41dc-90f2-de6cd8658f6f
  InstallationDate: Installed on 2015-07-19 

[Kernel-packages] [Bug 1842714] Re: bionic/linux-oem: 4.15.0-1054.63 -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: 1842746
  packages:
lrm: linux-restricted-modules-oem
main: linux-oem
meta: linux-meta-oem
signed: linux-signed-oem
  phase: Promote to Proposed
  phase-changed: Tuesday, 10. September 2019 20:35 UTC
  reason:
-   promote-to-proposed: Ongoing -- package copied to Proposed signed:depwait
+   promote-to-proposed: Ongoing -- package copied to Proposed signed:building
  variant: debs

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

Title:
  bionic/linux-oem: 4.15.0-1054.63 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-lrm series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Committed
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-oem package in Ubuntu:
  Invalid
Status in linux-oem source package in Bionic:
  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: 1842746
  packages:
lrm: linux-restricted-modules-oem
main: linux-oem
meta: linux-meta-oem
signed: linux-signed-oem
  phase: Promote to Proposed
  phase-changed: Tuesday, 10. September 2019 20:35 UTC
  reason:
promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror 
sync
  variant: debs

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

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

[Kernel-packages] [Bug 1842773] Re: bionic/linux-oracle: 4.15.0-1023.26 -proposed tracker

[Ubuntu Kernel Bot]

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


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

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

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

Title:
  bionic/linux-oracle: 4.15.0-1023.26 -proposed tracker

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

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

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

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1842746
  packages:
lrm: linux-restricted-modules-oracle
main: linux-oracle
meta: linux-meta-oracle
signed: linux-signed-oracle
  phase: Complete
  phase-changed: Tuesday, 10. September 2019 20:10 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  trackers:
xenial/linux-oracle: bug 1842772
  variant: debs

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

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

[Kernel-packages] [Bug 1843118] Re: bionic/linux-gcp: 4.15.0-1042.45 -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: 1842746
  packages:
main: linux-gcp
meta: linux-meta-gcp
signed: linux-signed-gcp
- phase: Ready for Promote to Updates
- phase-changed: Tuesday, 10. September 2019 21:02 UTC
+ phase: Promote to Updates
+ phase-changed: Tuesday, 10. September 2019 21:05 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   promote-to-updates: Pending -- ready to copy
+   promote-to-updates: Ongoing -- packages not yet published
  replaces: bug 1840806
  trackers:
bionic/linux-gcp-edge: bug 1840824
bionic/linux-gcp/gcp-kernel: bug 1843117
  variant: debs

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

Title:
  bionic/linux-gcp: 4.15.0-1042.45 -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-lrm series:
  Invalid
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:
  Fix Released
Status in Kernel SRU Workflow regression-testing series:
  Invalid
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux-gcp package in Ubuntu:
  Invalid
Status in linux-gcp source package in Bionic:
  Fix Released

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

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

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1842746
  packages:
main: linux-gcp
meta: linux-meta-gcp
signed: linux-signed-gcp
  phase: Holding before Promote to Security
  phase-changed: Tuesday, 10. September 2019 21:16 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  replaces: bug 1840806
  trackers:
bionic/linux-gcp-edge: bug 1840824
bionic/linux-gcp/gcp-kernel: bug 1843117
  variant: debs

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

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

[Kernel-packages] [Bug 1842714] Re: bionic/linux-oem: 4.15.0-1054.63 -proposed tracker

[Ubuntu Kernel Bot]

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

** 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: 1842746
  packages:
lrm: linux-restricted-modules-oem
main: linux-oem
meta: linux-meta-oem
signed: linux-signed-oem
  phase: Promote to Proposed
  phase-changed: Tuesday, 10. September 2019 20:35 UTC
  reason:
-   promote-to-proposed: Ongoing -- review in progress
+   promote-to-proposed: Ongoing -- package copied to Proposed signed:depwait
  variant: debs

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

Title:
  bionic/linux-oem: 4.15.0-1054.63 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-lrm series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Committed
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-oem package in Ubuntu:
  Invalid
Status in linux-oem source package in Bionic:
  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: 1842746
  packages:
lrm: linux-restricted-modules-oem
main: linux-oem
meta: linux-meta-oem
signed: linux-signed-oem
  phase: Promote to Proposed
  phase-changed: Tuesday, 10. September 2019 20:35 UTC
  reason:
promote-to-proposed: Ongoing -- package copied to Proposed signed:building
  variant: debs

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

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

[Kernel-packages] [Bug 1843118] Re: bionic/linux-gcp: 4.15.0-1042.45 -proposed tracker

[Ubuntu Kernel Bot]

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

** Tags removed: block-proposed-bionic

** Tags removed: 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: 1842746
  packages:
main: linux-gcp
meta: linux-meta-gcp
signed: linux-signed-gcp
- phase: Ready for Testing
- phase-changed: Tuesday, 10. September 2019 10:21 UTC
+ phase: Ready for Promote to Updates
+ phase-changed: Tuesday, 10. September 2019 21:02 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   automated-testing: Ongoing -- testing in progress
-   regression-testing: Ongoing -- testing in progress
+   promote-to-updates: Pending -- ready to copy
  replaces: bug 1840806
  trackers:
bionic/linux-gcp-edge: bug 1840824
bionic/linux-gcp/gcp-kernel: bug 1843117
  variant: debs

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

Title:
  bionic/linux-gcp: 4.15.0-1042.45 -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-lrm series:
  Invalid
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:
  In Progress
Status in Kernel SRU Workflow regression-testing series:
  Invalid
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux-gcp package in Ubuntu:
  Invalid
Status in linux-gcp source package in Bionic:
  Fix Released

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

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

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1842746
  packages:
main: linux-gcp
meta: linux-meta-gcp
signed: linux-signed-gcp
  phase: Promote to Updates
  phase-changed: Tuesday, 10. September 2019 21:05 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
promote-to-updates: Ongoing -- packages not yet published
  replaces: bug 1840806
  trackers:
bionic/linux-gcp-edge: bug 1840824
bionic/linux-gcp/gcp-kernel: bug 1843117
  variant: debs

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

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

[Kernel-packages] [Bug 1843118] Re: bionic/linux-gcp: 4.15.0-1042.45 -proposed tracker

[Andy Whitcroft]

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

** Changed in: kernel-sru-workflow/promote-to-updates
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Andy 
Whitcroft (apw)

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

Title:
  bionic/linux-gcp: 4.15.0-1042.45 -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-lrm series:
  Invalid
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:
  In Progress
Status in Kernel SRU Workflow regression-testing series:
  Invalid
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux-gcp package in Ubuntu:
  Invalid
Status in linux-gcp source package in Bionic:
  Fix Released

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

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

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1842746
  packages:
main: linux-gcp
meta: linux-meta-gcp
signed: linux-signed-gcp
  phase: Promote to Updates
  phase-changed: Tuesday, 10. September 2019 21:05 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
promote-to-updates: Ongoing -- packages not yet published
  replaces: bug 1840806
  trackers:
bionic/linux-gcp-edge: bug 1840824
bionic/linux-gcp/gcp-kernel: bug 1843117
  variant: debs

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

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

[Kernel-packages] [Bug 1843118] Re: bionic/linux-gcp: 4.15.0-1042.45 -proposed tracker

[Andy Whitcroft]

Testing up to now is reported good.  Google has signed off on this
kernel for release.

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

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

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

Title:
  bionic/linux-gcp: 4.15.0-1042.45 -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-lrm series:
  Invalid
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:
  In Progress
Status in Kernel SRU Workflow regression-testing series:
  Invalid
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux-gcp package in Ubuntu:
  Invalid
Status in linux-gcp source package in Bionic:
  Fix Released

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

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

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1842746
  packages:
main: linux-gcp
meta: linux-meta-gcp
signed: linux-signed-gcp
  phase: Promote to Updates
  phase-changed: Tuesday, 10. September 2019 21:05 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
promote-to-updates: Ongoing -- packages not yet published
  replaces: bug 1840806
  trackers:
bionic/linux-gcp-edge: bug 1840824
bionic/linux-gcp/gcp-kernel: bug 1843117
  variant: debs

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

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

[Kernel-packages] [Bug 1842742] Re: xenial/linux-deeplens: 4.15.0-1007.7 -proposed tracker

[Ubuntu Kernel Bot]

** Changed in: kernel-sru-workflow/certification-testing
   Status: New => Confirmed

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

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

** Changed in: kernel-sru-workflow/promote-to-proposed
   Status: Fix Committed => Fix Released

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

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1842744
  packages:
main: linux-deeplens
meta: linux-meta-deeplens
- phase: Promote to Proposed
- phase-changed: Tuesday, 10. September 2019 20:21 UTC
+ phase: Ready for Testing
+ phase-changed: Tuesday, 10. September 2019 20:46 UTC
+ proposed-announcement-sent: true
+ proposed-testing-requested: true
  reason:
-   promote-to-proposed: Stalled -- review in progress
+   certification-testing: Ongoing -- testing in progress
  replaces: bug 1840004
  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/1842742

Title:
  xenial/linux-deeplens: 4.15.0-1007.7 -proposed tracker

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

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: 1842744
  packages:
main: linux-deeplens
meta: linux-meta-deeplens
  phase: Ready for Testing
  phase-changed: Tuesday, 10. September 2019 20:46 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
certification-testing: Ongoing -- testing in progress
  replaces: bug 1840004
  variant: debs

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

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

[Kernel-packages] [Bug 1842714] Re: bionic/linux-oem: 4.15.0-1054.63 -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: 1842746
  packages:
lrm: linux-restricted-modules-oem
main: linux-oem
meta: linux-meta-oem
signed: linux-signed-oem
- phase: Ready for Promote to Proposed
- phase-changed: Tuesday, 10. September 2019 19:06 UTC
+ phase: Promote to Proposed
+ phase-changed: Tuesday, 10. September 2019 20:35 UTC
  reason:
-   promote-to-proposed: Pending -- ready for review
+   promote-to-proposed: Ongoing -- review in progress
  variant: debs

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

Title:
  bionic/linux-oem: 4.15.0-1054.63 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-lrm series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  In Progress
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-oem package in Ubuntu:
  Invalid
Status in linux-oem 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: 1842746
  packages:
lrm: linux-restricted-modules-oem
main: linux-oem
meta: linux-meta-oem
signed: linux-signed-oem
  phase: Promote to Proposed
  phase-changed: Tuesday, 10. September 2019 20:35 UTC
  reason:
promote-to-proposed: Ongoing -- review in progress
  variant: debs

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

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

[Kernel-packages] [Bug 1843323] Re: Kernel 4.15.0-59 (and onwards) breaks scroll wheel of USB mouse (A4Tech X5-50D)

[vlad]

** Patch added: "1c703b53e5bfb5c2205c30f0fb157ce271fd42fb.patch"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1843323/+attachment/5287864/+files/1c703b53e5bfb5c2205c30f0fb157ce271fd42fb.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/1843323

Title:
  Kernel 4.15.0-59 (and onwards) breaks scroll wheel of USB mouse
  (A4Tech X5-50D)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The latest kernel upgrade makes it impossible to use the scroll wheel
  of one specific mouse.

   Affected Ubuntu release: 18.04.3
   Last working kernel version: 4.15.0-58
   Affected kernel versions: 4.15.0-59, 4.15.0-60, 4.15.0-62, …

  I've several X5-50D input devices, tested at three different systems,
  connected via USB2 and USB3. I can reproduce the issue at all machines
  at any time. All others mouses are working fine. When booting the old
  kernel the problem is gone.

  Please tell me what details are required to trace this issue down. I
  should be able to test custom patches and build packages, if required.

  > usb 3-11: new low-speed USB device number 5 using xhci_hcd
  > usb 3-11: New USB device found, idVendor=09da, idProduct=000a
  > usb 3-11: New USB device strings: Mfr=1, Product=2, SerialNumber=0
  > usb 3-11: Product: PS/2+USB Mouse
  > usb 3-11: Manufacturer: A4Tech
  > input: A4Tech PS/2+USB Mouse as 
/devices/pci:00/:00:14.0/usb3/3-11/3-11:1.0/0003:09DA:000A.0005/input/input21
  > a4tech 0003:09DA:000A.0005: input,hidraw4: USB HID v1.10 Mouse [A4Tech 
PS/2+USB Mouse] on usb-:00:14.0-11/input0

  > Bus 003 Device 004: ID 09da:000a A4Tech Co., Ltd. Optical Mouse Opto 510D / 
OP-620D
  > Device Descriptor:
  >   bLength18
  >   bDescriptorType 1
  >   bcdUSB   1.10
  >   bDeviceClass0 (Defined at Interface level)
  >   bDeviceSubClass 0
  >   bDeviceProtocol 0
  >   bMaxPacketSize0 8
  >   idVendor   0x09da A4Tech Co., Ltd.
  >   idProduct  0x000a Optical Mouse Opto 510D / OP-620D
  >   bcdDevice1.05
  >   iManufacturer   1 A4Tech
  >   iProduct2 USB Mouse
  >   iSerial 0
  >   bNumConfigurations  1
  >   Configuration Descriptor:
  > bLength 9
  > bDescriptorType 2
  > wTotalLength   34
  > bNumInterfaces  1
  > bConfigurationValue 1
  > iConfiguration  0
  > bmAttributes 0xa0
  >   (Bus Powered)
  >   Remote Wakeup
  > MaxPower  100mA
  > Interface Descriptor:
  >   bLength 9
  >   bDescriptorType 4
  >   bInterfaceNumber0
  >   bAlternateSetting   0
  >   bNumEndpoints   1
  >   bInterfaceClass 3 Human Interface Device
  >   bInterfaceSubClass  1 Boot Interface Subclass
  >   bInterfaceProtocol  2 Mouse
  >   iInterface  0
  > HID Device Descriptor:
  >   bLength 9
  >   bDescriptorType33
  >   bcdHID   1.10
  >   bCountryCode0 Not supported
  >   bNumDescriptors 1
  >   bDescriptorType34 Report
  >   wDescriptorLength  48
  >  Report Descriptors:
  >** UNAVAILABLE **
  >   Endpoint Descriptor:
  > bLength 7
  > bDescriptorType 5
  > bEndpointAddress 0x81  EP 1 IN
  > bmAttributes3
  >   Transfer TypeInterrupt
  >   Synch Type   None
  >   Usage Type   Data
  > wMaxPacketSize 0x0008  1x 8 bytes
  > bInterval  10
  > Device Status: 0x
  >   (Bus Powered)

  ---

  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=e505eab0-02d8-41dc-90f2-de6cd8658f6f
  InstallationDate: Installed on 2015-07-19 (1513 days ago)
  InstallationMedia: Xubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422.1)
  MachineType: MSI MS-7924
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-62-generic 
root=UUID=f8e0335a-11ac-48ca-90af-23784d1ed592 ro quiet splash
  ProcVersionSignature: Ubuntu 4.15.0-62.69-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-62-generic N/A
   linux-backports-modules-4.15.0-62-generic  N/A
   linux-firmware 1.173.10
  RfKill:

  Tags:  bionic
  Uname: Linux 4.15.0-62-generic x86_64
  UpgradeStatus: Upgraded to bionic on 2019-07-16 (55 days ago)
  UserGroups: adm cdrom dialout dip fax floppy fuse libvirt libvirtd lpadmin 
plugdev sambashare sudo 

[Kernel-packages] [Bug 1842714] Re: bionic/linux-oem: 4.15.0-1054.63 -proposed tracker

[Andy Whitcroft]

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

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

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

Title:
  bionic/linux-oem: 4.15.0-1054.63 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-lrm series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  In Progress
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-oem package in Ubuntu:
  Invalid
Status in linux-oem 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: 1842746
  packages:
lrm: linux-restricted-modules-oem
main: linux-oem
meta: linux-meta-oem
signed: linux-signed-oem
  phase: Promote to Proposed
  phase-changed: Tuesday, 10. September 2019 20:35 UTC
  reason:
promote-to-proposed: Ongoing -- review in progress
  variant: debs

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

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

[Kernel-packages] [Bug 1842772] Re: xenial/linux-oracle: 4.15.0-1023.26~16.04.1 -proposed tracker

[Ubuntu Kernel Bot]

** Changed in: kernel-sru-workflow/promote-to-security
   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 --
  boot-testing-requested: true
  kernel-stable-master-bug: 1842773
  packages:
main: linux-oracle
meta: linux-meta-oracle
signed: linux-signed-oracle
- phase: Ready for Promote to Security
- phase-changed: Tuesday, 10. September 2019 12:47 UTC
+ phase: Complete
+ phase-changed: Tuesday, 10. September 2019 20:16 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
- reason:
-   promote-to-security: Pending -- ready to copy
  replaces: bug 1842724
  variant: debs

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

Title:
  xenial/linux-oracle: 4.15.0-1023.26~16.04.1 -proposed tracker

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

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

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

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1842773
  packages:
main: linux-oracle
meta: linux-meta-oracle
signed: linux-signed-oracle
  phase: Complete
  phase-changed: Tuesday, 10. September 2019 20:16 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  replaces: bug 1842724
  variant: debs

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

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

[Kernel-packages] [Bug 1759836] Re: systemd-udevd consumes 100% of CPU due to hid2hci udev rule from bluez

[Dan Streetman]

> Sorry for the late reply. Here comes the output:
> KERNEL[90619.640204] remove /module/nvidia (module)
> KERNEL[90619.696504] add /module/nvidia (module)

ok, your problem is that something is constantly adding and removing the
nvidia module (and, doing other related device processing).  That has
nothing to do with this bug's problem, which is ONLY for udev looping
due to rules in the bluez package's hid2hci rules file.  I updated the
bug subject to clarify that (scanning back through all the comments, I
think most if not all of the discussion focuses on this specific package
and rule).

You do seem to be having some other problem, which probably is with the
nvidia-persistenced.service, provided by the nvidia-compute-utils-NNN
package (with NNN being a number).  Check:

$ dpkg -l | grep nvidia

to see the specific package name/version on your system.  I don't really
know what the problem is there, but you could try removing the package
(if you don't need it), or searching for and/or opening a new bug for
the problem.

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

Title:
  systemd-udevd consumes 100% of CPU due to hid2hci udev rule from bluez

Status in linux:
  Confirmed
Status in The Ubuntu Power Consumption Project:
  New
Status in bluez package in Ubuntu:
  In Progress
Status in linux package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Invalid
Status in bluez package in Debian:
  New

Bug description:
  The systemd-udevd proccess consumes 100% of a thread everytime, but
  i'm not noticing any difference in my computer.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: systemd 237-3ubuntu6
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Mar 29 08:52:54 2018
  InstallationDate: Installed on 2018-03-05 (23 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180304)
  MachineType: Dell Inc. Inspiron N5010
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic 
root=UUID=3c29e292-f1ae-45e1-a0ed-a82524278ce1 ro quiet splash vt.handoff=1
  SourcePackage: systemd
  SystemdDelta:
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /lib/systemd/system/user@.service → 
/lib/systemd/system/user@.service.d/timeout.conf

   2 overridden configuration files found.
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/25/2011
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A12
  dmi.board.name: 08R0GW
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A12
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A12
  dmi.modalias: 
dmi:bvnDellInc.:bvrA12:bd01/25/2011:svnDellInc.:pnInspironN5010:pvrA12:rvnDellInc.:rn08R0GW:rvrA12:cvnDellInc.:ct8:cvrA12:
  dmi.product.name: Inspiron N5010
  dmi.product.version: A12
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1842742] Re: xenial/linux-deeplens: 4.15.0-1007.7 -proposed tracker

[Andy Whitcroft]

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

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

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

Title:
  xenial/linux-deeplens: 4.15.0-1007.7 -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:
  New
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  In Progress
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:
  Invalid
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:
  Invalid

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: 1842744
  packages:
main: linux-deeplens
meta: linux-meta-deeplens
  phase: Promote to Proposed
  phase-changed: Tuesday, 10. September 2019 20:21 UTC
  reason:
promote-to-proposed: Stalled -- review in progress
  replaces: bug 1840004
  variant: debs

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

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

[Kernel-packages] [Bug 1842742] Re: xenial/linux-deeplens: 4.15.0-1007.7 -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: 1842744
  packages:
main: linux-deeplens
meta: linux-meta-deeplens
- phase: Ready for Promote to Proposed
- phase-changed: Tuesday, 10. September 2019 12:31 UTC
+ phase: Promote to Proposed
+ phase-changed: Tuesday, 10. September 2019 20:21 UTC
  reason:
-   promote-to-proposed: Pending -- ready for review
+   promote-to-proposed: Stalled -- review in progress
  replaces: bug 1840004
  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/1842742

Title:
  xenial/linux-deeplens: 4.15.0-1007.7 -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:
  New
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  In Progress
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:
  Invalid
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:
  Invalid

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: 1842744
  packages:
main: linux-deeplens
meta: linux-meta-deeplens
  phase: Promote to Proposed
  phase-changed: Tuesday, 10. September 2019 20:21 UTC
  reason:
promote-to-proposed: Stalled -- review in progress
  replaces: bug 1840004
  variant: debs

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

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

[Kernel-packages] [Bug 1843323] Re: Kernel 4.15.0-59 (and onwards) breaks scroll wheel of USB mouse (A4Tech X5-50D)

[vlad]

This commit fixes the bug:
https://github.com/torvalds/linux/commit/1c703b53e5bfb5c2205c30f0fb157ce271fd42fb
Backport, please.

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

Title:
  Kernel 4.15.0-59 (and onwards) breaks scroll wheel of USB mouse
  (A4Tech X5-50D)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The latest kernel upgrade makes it impossible to use the scroll wheel
  of one specific mouse.

   Affected Ubuntu release: 18.04.3
   Last working kernel version: 4.15.0-58
   Affected kernel versions: 4.15.0-59, 4.15.0-60, 4.15.0-62, …

  I've several X5-50D input devices, tested at three different systems,
  connected via USB2 and USB3. I can reproduce the issue at all machines
  at any time. All others mouses are working fine. When booting the old
  kernel the problem is gone.

  Please tell me what details are required to trace this issue down. I
  should be able to test custom patches and build packages, if required.

  > usb 3-11: new low-speed USB device number 5 using xhci_hcd
  > usb 3-11: New USB device found, idVendor=09da, idProduct=000a
  > usb 3-11: New USB device strings: Mfr=1, Product=2, SerialNumber=0
  > usb 3-11: Product: PS/2+USB Mouse
  > usb 3-11: Manufacturer: A4Tech
  > input: A4Tech PS/2+USB Mouse as 
/devices/pci:00/:00:14.0/usb3/3-11/3-11:1.0/0003:09DA:000A.0005/input/input21
  > a4tech 0003:09DA:000A.0005: input,hidraw4: USB HID v1.10 Mouse [A4Tech 
PS/2+USB Mouse] on usb-:00:14.0-11/input0

  > Bus 003 Device 004: ID 09da:000a A4Tech Co., Ltd. Optical Mouse Opto 510D / 
OP-620D
  > Device Descriptor:
  >   bLength18
  >   bDescriptorType 1
  >   bcdUSB   1.10
  >   bDeviceClass0 (Defined at Interface level)
  >   bDeviceSubClass 0
  >   bDeviceProtocol 0
  >   bMaxPacketSize0 8
  >   idVendor   0x09da A4Tech Co., Ltd.
  >   idProduct  0x000a Optical Mouse Opto 510D / OP-620D
  >   bcdDevice1.05
  >   iManufacturer   1 A4Tech
  >   iProduct2 USB Mouse
  >   iSerial 0
  >   bNumConfigurations  1
  >   Configuration Descriptor:
  > bLength 9
  > bDescriptorType 2
  > wTotalLength   34
  > bNumInterfaces  1
  > bConfigurationValue 1
  > iConfiguration  0
  > bmAttributes 0xa0
  >   (Bus Powered)
  >   Remote Wakeup
  > MaxPower  100mA
  > Interface Descriptor:
  >   bLength 9
  >   bDescriptorType 4
  >   bInterfaceNumber0
  >   bAlternateSetting   0
  >   bNumEndpoints   1
  >   bInterfaceClass 3 Human Interface Device
  >   bInterfaceSubClass  1 Boot Interface Subclass
  >   bInterfaceProtocol  2 Mouse
  >   iInterface  0
  > HID Device Descriptor:
  >   bLength 9
  >   bDescriptorType33
  >   bcdHID   1.10
  >   bCountryCode0 Not supported
  >   bNumDescriptors 1
  >   bDescriptorType34 Report
  >   wDescriptorLength  48
  >  Report Descriptors:
  >** UNAVAILABLE **
  >   Endpoint Descriptor:
  > bLength 7
  > bDescriptorType 5
  > bEndpointAddress 0x81  EP 1 IN
  > bmAttributes3
  >   Transfer TypeInterrupt
  >   Synch Type   None
  >   Usage Type   Data
  > wMaxPacketSize 0x0008  1x 8 bytes
  > bInterval  10
  > Device Status: 0x
  >   (Bus Powered)

  ---

  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=e505eab0-02d8-41dc-90f2-de6cd8658f6f
  InstallationDate: Installed on 2015-07-19 (1513 days ago)
  InstallationMedia: Xubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422.1)
  MachineType: MSI MS-7924
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-62-generic 
root=UUID=f8e0335a-11ac-48ca-90af-23784d1ed592 ro quiet splash
  ProcVersionSignature: Ubuntu 4.15.0-62.69-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-62-generic N/A
   linux-backports-modules-4.15.0-62-generic  N/A
   linux-firmware 1.173.10
  RfKill:

  Tags:  bionic
  Uname: Linux 4.15.0-62-generic x86_64
  UpgradeStatus: Upgraded to bionic on 2019-07-16 (55 days ago)
  UserGroups: adm cdrom dialout dip fax floppy fuse libvirt libvirtd lpadmin 
plugdev sambashare sudo tape vboxusers video wireshark
  _MarkForUpload: True

To manage 

[Kernel-packages] [Bug 1842772] Re: xenial/linux-oracle: 4.15.0-1023.26~16.04.1 -proposed tracker

[Andy Whitcroft]

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

** Changed in: kernel-sru-workflow/promote-to-security
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Andy 
Whitcroft (apw)

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

Title:
  xenial/linux-oracle: 4.15.0-1023.26~16.04.1 -proposed tracker

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

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

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

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1842773
  packages:
main: linux-oracle
meta: linux-meta-oracle
signed: linux-signed-oracle
  phase: Complete
  phase-changed: Tuesday, 10. September 2019 20:16 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  replaces: bug 1842724
  variant: debs

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

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

[Kernel-packages] [Bug 1842773] Re: bionic/linux-oracle: 4.15.0-1023.26 -proposed tracker

[Ubuntu Kernel Bot]

** Changed in: kernel-sru-workflow/promote-to-security
   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 --
  boot-testing-requested: true
  kernel-stable-master-bug: 1842746
  packages:
lrm: linux-restricted-modules-oracle
main: linux-oracle
meta: linux-meta-oracle
signed: linux-signed-oracle
- phase: Ready for Promote to Security
- phase-changed: Tuesday, 10. September 2019 12:41 UTC
+ phase: Complete
+ phase-changed: Tuesday, 10. September 2019 20:10 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
- reason:
-   promote-to-security: Pending -- ready to copy
  trackers:
xenial/linux-oracle: bug 1842772
  variant: debs

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

Title:
  bionic/linux-oracle: 4.15.0-1023.26 -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-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:
  Fix Released
Status in Kernel SRU Workflow promote-to-updates series:
  Fix Released
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux-oracle package in Ubuntu:
  Fix Released
Status in linux-oracle source package in Bionic:
  Fix Released

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

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

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1842746
  packages:
lrm: linux-restricted-modules-oracle
main: linux-oracle
meta: linux-meta-oracle
signed: linux-signed-oracle
  phase: Complete
  phase-changed: Tuesday, 10. September 2019 20:10 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  trackers:
xenial/linux-oracle: bug 1842772
  variant: debs

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

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

[Kernel-packages] [Bug 1842587] Re: xenial/linux-azure: 4.15.0-1057.62 -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: 1842828
  packages:
main: linux-azure
meta: linux-meta-azure
signed: linux-signed-azure
  phase: Ready for Testing
  phase-changed: Friday, 06. September 2019 05:48 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
regression-testing: Ongoing -- testing in progress
stakeholder-signoff: Stalled -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
-   trusty/linux-azure: bug 1842585, bug 1842819
+   trusty/linux-azure: bug 1842819, bug 1842585
xenial/linux-azure-edge: bug 1842584
xenial/linux-azure/azure-kernel: bug 1842583
  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/1842587

Title:
  xenial/linux-azure: 4.15.0-1057.62 -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:
  New
Status in Kernel SRU Workflow stakeholder-signoff series:
  Confirmed
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-azure package in Ubuntu:
  Invalid
Status in linux-azure source package in Xenial:
  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: 1842828
  packages:
main: linux-azure
meta: linux-meta-azure
signed: linux-signed-azure
  phase: Ready for Testing
  phase-changed: Friday, 06. September 2019 05:48 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
regression-testing: Ongoing -- testing in progress
stakeholder-signoff: Stalled -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
trusty/linux-azure: bug 1842819, bug 1842585
xenial/linux-azure-edge: bug 1842584
xenial/linux-azure/azure-kernel: bug 1842583
  variant: debs

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

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

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

[Antoine Jacob]

Hello !

I've been following this thread for a solution while not updating my ubuntu 
18.04 fresh install.
Seeing that updating the BIOS was a possible fix, i flashed version 302 of my 
ASUS BIOS (I own a UX450FD-BE014T) and updated everything.
When time came to reboot, I was stuck on the plain purple screen without the 
ability to get to the OS...
Being tired of all that waiting I'll try another solution. But how easy will it 
be to revert to normal when (if) the bug is fixed ?

Thanks a lot to everyone for their involvment in this cause !

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

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

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

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

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

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

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

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

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

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

  EDIT:

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

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

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

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

  WORKAROUND 3: upgrade BIOS
  Asus has released updated BIOSes, which probably include the newest 
microcode. After upgrading workarounds 1,2 are not needed. 
  Please NOTE, unlike workarounds 1,2, BIOS upgrade is permanent and cannot be 
(easily) reverted. 

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

[Kernel-packages] [Bug 1759836] Re: systemd-udevd consumes 100% of CPU due to hid2hci udev rule from bluez

[Dan Streetman]

** Summary changed:

- systemd-udevd consumes 100% of CPU
+ systemd-udevd consumes 100% of CPU due to hid2hci udev rule from bluez

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

Title:
  systemd-udevd consumes 100% of CPU due to hid2hci udev rule from bluez

Status in linux:
  Confirmed
Status in The Ubuntu Power Consumption Project:
  New
Status in bluez package in Ubuntu:
  In Progress
Status in linux package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Invalid
Status in bluez package in Debian:
  New

Bug description:
  The systemd-udevd proccess consumes 100% of a thread everytime, but
  i'm not noticing any difference in my computer.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: systemd 237-3ubuntu6
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Mar 29 08:52:54 2018
  InstallationDate: Installed on 2018-03-05 (23 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180304)
  MachineType: Dell Inc. Inspiron N5010
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic 
root=UUID=3c29e292-f1ae-45e1-a0ed-a82524278ce1 ro quiet splash vt.handoff=1
  SourcePackage: systemd
  SystemdDelta:
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /lib/systemd/system/user@.service → 
/lib/systemd/system/user@.service.d/timeout.conf

   2 overridden configuration files found.
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/25/2011
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A12
  dmi.board.name: 08R0GW
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A12
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A12
  dmi.modalias: 
dmi:bvnDellInc.:bvrA12:bd01/25/2011:svnDellInc.:pnInspironN5010:pvrA12:rvnDellInc.:rn08R0GW:rvrA12:cvnDellInc.:ct8:cvrA12:
  dmi.product.name: Inspiron N5010
  dmi.product.version: A12
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1843323] Re: Kernel 4.15.0-59 (and onwards) breaks scroll wheel of USB mouse (A4Tech X5-50D)

[vlad]

I've tested latest mainline kernel.
This bug is fixed in mainline. I'm using A4tech X6-90D and both wheels are 
working fine in mainline.

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

Title:
  Kernel 4.15.0-59 (and onwards) breaks scroll wheel of USB mouse
  (A4Tech X5-50D)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The latest kernel upgrade makes it impossible to use the scroll wheel
  of one specific mouse.

   Affected Ubuntu release: 18.04.3
   Last working kernel version: 4.15.0-58
   Affected kernel versions: 4.15.0-59, 4.15.0-60, 4.15.0-62, …

  I've several X5-50D input devices, tested at three different systems,
  connected via USB2 and USB3. I can reproduce the issue at all machines
  at any time. All others mouses are working fine. When booting the old
  kernel the problem is gone.

  Please tell me what details are required to trace this issue down. I
  should be able to test custom patches and build packages, if required.

  > usb 3-11: new low-speed USB device number 5 using xhci_hcd
  > usb 3-11: New USB device found, idVendor=09da, idProduct=000a
  > usb 3-11: New USB device strings: Mfr=1, Product=2, SerialNumber=0
  > usb 3-11: Product: PS/2+USB Mouse
  > usb 3-11: Manufacturer: A4Tech
  > input: A4Tech PS/2+USB Mouse as 
/devices/pci:00/:00:14.0/usb3/3-11/3-11:1.0/0003:09DA:000A.0005/input/input21
  > a4tech 0003:09DA:000A.0005: input,hidraw4: USB HID v1.10 Mouse [A4Tech 
PS/2+USB Mouse] on usb-:00:14.0-11/input0

  > Bus 003 Device 004: ID 09da:000a A4Tech Co., Ltd. Optical Mouse Opto 510D / 
OP-620D
  > Device Descriptor:
  >   bLength18
  >   bDescriptorType 1
  >   bcdUSB   1.10
  >   bDeviceClass0 (Defined at Interface level)
  >   bDeviceSubClass 0
  >   bDeviceProtocol 0
  >   bMaxPacketSize0 8
  >   idVendor   0x09da A4Tech Co., Ltd.
  >   idProduct  0x000a Optical Mouse Opto 510D / OP-620D
  >   bcdDevice1.05
  >   iManufacturer   1 A4Tech
  >   iProduct2 USB Mouse
  >   iSerial 0
  >   bNumConfigurations  1
  >   Configuration Descriptor:
  > bLength 9
  > bDescriptorType 2
  > wTotalLength   34
  > bNumInterfaces  1
  > bConfigurationValue 1
  > iConfiguration  0
  > bmAttributes 0xa0
  >   (Bus Powered)
  >   Remote Wakeup
  > MaxPower  100mA
  > Interface Descriptor:
  >   bLength 9
  >   bDescriptorType 4
  >   bInterfaceNumber0
  >   bAlternateSetting   0
  >   bNumEndpoints   1
  >   bInterfaceClass 3 Human Interface Device
  >   bInterfaceSubClass  1 Boot Interface Subclass
  >   bInterfaceProtocol  2 Mouse
  >   iInterface  0
  > HID Device Descriptor:
  >   bLength 9
  >   bDescriptorType33
  >   bcdHID   1.10
  >   bCountryCode0 Not supported
  >   bNumDescriptors 1
  >   bDescriptorType34 Report
  >   wDescriptorLength  48
  >  Report Descriptors:
  >** UNAVAILABLE **
  >   Endpoint Descriptor:
  > bLength 7
  > bDescriptorType 5
  > bEndpointAddress 0x81  EP 1 IN
  > bmAttributes3
  >   Transfer TypeInterrupt
  >   Synch Type   None
  >   Usage Type   Data
  > wMaxPacketSize 0x0008  1x 8 bytes
  > bInterval  10
  > Device Status: 0x
  >   (Bus Powered)

  ---

  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=e505eab0-02d8-41dc-90f2-de6cd8658f6f
  InstallationDate: Installed on 2015-07-19 (1513 days ago)
  InstallationMedia: Xubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422.1)
  MachineType: MSI MS-7924
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-62-generic 
root=UUID=f8e0335a-11ac-48ca-90af-23784d1ed592 ro quiet splash
  ProcVersionSignature: Ubuntu 4.15.0-62.69-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-62-generic N/A
   linux-backports-modules-4.15.0-62-generic  N/A
   linux-firmware 1.173.10
  RfKill:

  Tags:  bionic
  Uname: Linux 4.15.0-62-generic x86_64
  UpgradeStatus: Upgraded to bionic on 2019-07-16 (55 days ago)
  UserGroups: adm cdrom dialout dip fax floppy fuse libvirt libvirtd lpadmin 
plugdev sambashare sudo tape vboxusers video wireshark
  _MarkForUpload: True

To manage 

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

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

Title:
  IOMMU SVM requires PRQ_DRAIN function implemented.

Status in intel:
  New
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Description
  Under terminal conditions when drivers require to reset their devices, they 
need to ensure that page request processing is flushed and restarted after the 
device is completed processing the reset.

  Drivers need a mechanism to stop page requests, and start page request
  processing.

  Need 2 new interfaces:
  intel_svm_suspend_prs_processing() - it can take some flags to indicate if 
this indicates all PASID's for this device? or just a specific PASID. Any Page 
Request that comes will be dropped and not processed by IOMMU SVM code.

  Consider having any stats on per device or per pasid to indicate how many 
were dropped during this period. and facility to clear stats?
  intel_svm_drain_prs_processing() This call will block, until a drain desc is 
complete, also should ensure that any request that have been pushed to the page 
queue should be dropped before returning back to caller.

  Target Release: 20.04
  Target Kernel: TBD

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

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

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

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

Title:
  Audit IOMMU capabilities and disable if there are some incompatible
  IOMMU's in the platform

Status in intel:
  New
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Description
  Audit the capabilities and extended capabilities and disable IOMMU if there 
is incompatibility between them.

  For e.g. cap.first_level_1G_page support=0, and kernel has enabled 1G
  pages, we should disable SVM on that IOMMU.

  Audit code for any other anomalies like this, for e.g. difference in
  address bits supported, HAW, AGAW etc we should disable IOMMU for the
  whole system if these differences can lead to improper behavior.

  Target Release: 20.04
  Target Kernel: TBD

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

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

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

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

Title:
  UIO: mutex used in interrupt handler causes crash

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Running:
  Bionic Beaver
  Ubuntu 4.15.0-62.69-generic 4.15.18

  In commit 725bbc87 on 2/13/2019 in uio.c a mutex_lock was added to
  uio_interrupt.  This results in a "scheduling while atomic" error if
  someone else owns the mutex at the time it is invoked.

  [ 1941.409212] BUG: scheduling while atomic: fcasm-test/3937/0x0001
  [ 1941.409216] Modules linked in: cdc_ether usbnet r8152 mii rfcomm ccm bnep 
arc4 nls_iso8859_1 snd_hda_codec_hdmi hid_multitouch dell_laptop 
intel_wmi_thunderbolt dell_wmi wmi_bmof dell_smbios dcdbas dell_wmi_descriptor 
snd_soc_skl snd_hda_codec_realtek snd_soc_skl_ipc snd_hda_codec_generic 
snd_hda_ext_core snd_soc_sst_dsp snd_soc_sst_ipc snd_soc_acpi snd_soc_core 
snd_compress ac97_bus snd_pcm_dmaengine intel_rapl ath10k_pci 
x86_pkg_temp_thermal intel_powerclamp ath10k_core coretemp kvm_intel ath kvm 
mac80211 irqbypass crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc 
cfg80211 aesni_intel rtsx_pci_ms aes_x86_64 memstick crypto_simd glue_helper 
cryptd intel_cstate intel_rapl_perf snd_hda_intel snd_hda_codec snd_hda_core 
snd_hwdep snd_pcm snd_seq_midi snd_seq_midi_event snd_rawmidi snd_seq joydev
  [ 1941.409247]  input_leds serio_raw snd_seq_device snd_timer idma64 snd 
virt_dma soundcore i915 mei_me mei shpchp uvcvideo btusb drm_kms_helper btrtl 
videobuf2_vmalloc btbcm intel_lpss_pci videobuf2_memops btintel intel_lpss drm 
videobuf2_v4l2 bluetooth videobuf2_core intel_pch_thermal i2c_algo_bit videodev 
fb_sys_fops syscopyarea processor_thermal_device sysfillrect media ecdh_generic 
sysimgblt intel_soc_dts_iosf wmi intel_hid int3400_thermal int3403_thermal 
int340x_thermal_zone acpi_thermal_rel sparse_keymap mac_hid acpi_pad video 
sch_fq_codel nfsd uio_nwdv(OE) auth_rpcgss nfs_acl uio lockd grace parport_pc 
ppdev sunrpc lp parport ip_tables x_tables autofs4 nvme rtsx_pci_sdmmc psmouse 
nvme_core thunderbolt rtsx_pci i2c_hid hid pinctrl_sunrisepoint
  [ 1941.409281] CPU: 3 PID: 3937 Comm: fcasm-test Tainted: G   OE
4.15.0-62-generic #69-Ubuntu
  [ 1941.409282] Hardware name: Dell Inc. XPS 13 9370/0F6P3V, BIOS 1.10.0 
04/18/2019
  [ 1941.409282] Call Trace:
  [ 1941.409284]  
  [ 1941.409290]  dump_stack+0x63/0x8b
  [ 1941.409293]  __schedule_bug+0x55/0x70
  [ 1941.409295]  __schedule+0x658/0x880
  [ 1941.409297]  ? default_wake_function+0x12/0x20
  [ 1941.409298]  ? pollwake+0x73/0x90
  [ 1941.409300]  schedule+0x2c/0x80
  [ 1941.409302]  schedule_preempt_disabled+0xe/0x10
  [ 1941.409303]  __mutex_lock.isra.5+0x478/0x4e0
  [ 1941.409304]  __mutex_lock_slowpath+0x13/0x20
  [ 1941.409305]  ? __mutex_lock_slowpath+0x13/0x20
  [ 1941.409306]  mutex_lock+0x2f/0x40
  [ 1941.409309]  uio_interrupt+0x23/0x70 [uio]
  [ 1941.409311]  __handle_irq_event_percpu+0x44/0x1a0
  [ 1941.409313]  handle_irq_event_percpu+0x32/0x80
  [ 1941.409315]  handle_irq_event+0x3b/0x60
  [ 1941.409316]  handle_fasteoi_irq+0x7c/0x130
  [ 1941.409318]  handle_irq+0x20/0x30
  [ 1941.409319]  do_IRQ+0x50/0xe0
  [ 1941.409321]  common_interrupt+0x8c/0x8c
  [ 1941.409322]  
  [ 1941.409323] RIP: 0010:mutex_lock+0x22/0x40
  [ 1941.409324] RSP: 0018:b68681b9b950 EFLAGS: 0246 ORIG_RAX: 
ffdc
  [ 1941.409325] RAX:  RBX: 8ae612f8af10 RCX: 

  [ 1941.409326] RDX: 8ae51b319740 RSI: b68681b9ba70 RDI: 
8ae612f8af10
  [ 1941.409327] RBP: b68681b9b958 R08: 8ae4ffa35200 R09: 
c04c7120
  [ 1941.409327] R10: 0001 R11: 0389cc0215b7 R12: 
8ae612f8af10
  [ 1941.409328] R13: 8ae512de6bb0 R14: 8ae4ffa35200 R15: 
b68681b9ba70
  [ 1941.409330]  ? uio_interrupt+0x70/0x70 [uio]
  [ 1941.409331]  uio_poll+0x32/0xb0 [uio]
  [ 1941.409333]  do_select+0x384/0x7e0
  [ 1941.409335]  ? compat_poll_select_copy_remaining+0x130/0x130
  [ 1941.409338]  ? __update_load_avg_se.isra.37+0x1c0/0x1d0
  [ 1941.409339]  ? __update_load_avg_se.isra.37+0x1c0/0x1d0
  [ 1941.409341]  ? find_next_bit+0xb/0x10
  [ 1941.409342]  ? update_load_avg+0x3b0/0x6e0
  [ 1941.409343]  ? update_curr+0x7a/0x1d0
  [ 1941.409344]  ? 

[Kernel-packages] [Bug 1842608] Re: xenial/linux: 4.4.0-162.190 -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 --
  packages:
main: linux
meta: linux-meta
signed: linux-signed
  phase: Holding before Promote to Proposed
  phase-changed: Wednesday, 04. September 2019 07:52 UTC
  reason:
promote-to-proposed: Pending -- builds not complete in ppa 
main:failed,meta:depwait
  trackers:
-   trusty/linux-aws: bug 1842606, bug 1842793
+   trusty/linux-aws: bug 1842793, bug 1842606
trusty/linux-lts-xenial: bug 1842794, bug 1842607
xenial/linux-aws: bug 1842597
xenial/linux-fips: bug 1842605
xenial/linux-kvm: bug 1842598
xenial/linux-raspi2: bug 1842600
xenial/linux-snapdragon: bug 1842603
xenial/linux/pc-kernel: bug 1842595
  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/1842608

Title:
  xenial/linux: 4.4.0-162.190 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  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 --
  packages:
main: linux
meta: linux-meta
signed: linux-signed
  phase: Holding before Promote to Proposed
  phase-changed: Wednesday, 04. September 2019 07:52 UTC
  reason:
promote-to-proposed: Pending -- builds not complete in ppa 
main:failed,meta:depwait
  trackers:
trusty/linux-aws: bug 1842793, bug 1842606
trusty/linux-lts-xenial: bug 1842794, bug 1842607
xenial/linux-aws: bug 1842597
xenial/linux-fips: bug 1842605
xenial/linux-kvm: bug 1842598
xenial/linux-raspi2: bug 1842600
xenial/linux-snapdragon: bug 1842603
xenial/linux/pc-kernel: bug 1842595
  variant: debs

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

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

[Kernel-packages] [Bug 1842773] Re: bionic/linux-oracle: 4.15.0-1023.26 -proposed tracker

[Andy Whitcroft]

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

** Changed in: kernel-sru-workflow/promote-to-security
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Andy 
Whitcroft (apw)

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

Title:
  bionic/linux-oracle: 4.15.0-1023.26 -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-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:
  Fix Released
Status in Kernel SRU Workflow promote-to-updates series:
  Fix Released
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux-oracle package in Ubuntu:
  Fix Released
Status in linux-oracle source package in Bionic:
  Fix Released

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

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

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1842746
  packages:
lrm: linux-restricted-modules-oracle
main: linux-oracle
meta: linux-meta-oracle
signed: linux-signed-oracle
  phase: Complete
  phase-changed: Tuesday, 10. September 2019 20:10 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  trackers:
xenial/linux-oracle: bug 1842772
  variant: debs

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

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

[Kernel-packages] [Bug 1843491] [NEW] IOMMU SVM requires PRQ_DRAIN function implemented.

[quanxian]

Public bug reported:

Description
Under terminal conditions when drivers require to reset their devices, they 
need to ensure that page request processing is flushed and restarted after the 
device is completed processing the reset.

Drivers need a mechanism to stop page requests, and start page request
processing.

Need 2 new interfaces:
intel_svm_suspend_prs_processing() - it can take some flags to indicate if this 
indicates all PASID's for this device? or just a specific PASID. Any Page 
Request that comes will be dropped and not processed by IOMMU SVM code.

Consider having any stats on per device or per pasid to indicate how many were 
dropped during this period. and facility to clear stats?
intel_svm_drain_prs_processing() This call will block, until a drain desc is 
complete, also should ensure that any request that have been pushed to the page 
queue should be dropped before returning back to caller.

Target Release: 20.04
Target Kernel: TBD

** Affects: intel
 Importance: Undecided
 Status: New

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


** Tags: intel-kernel-20.04

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

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

Title:
  IOMMU SVM requires PRQ_DRAIN function implemented.

Status in intel:
  New
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Description
  Under terminal conditions when drivers require to reset their devices, they 
need to ensure that page request processing is flushed and restarted after the 
device is completed processing the reset.

  Drivers need a mechanism to stop page requests, and start page request
  processing.

  Need 2 new interfaces:
  intel_svm_suspend_prs_processing() - it can take some flags to indicate if 
this indicates all PASID's for this device? or just a specific PASID. Any Page 
Request that comes will be dropped and not processed by IOMMU SVM code.

  Consider having any stats on per device or per pasid to indicate how many 
were dropped during this period. and facility to clear stats?
  intel_svm_drain_prs_processing() This call will block, until a drain desc is 
complete, also should ensure that any request that have been pushed to the page 
queue should be dropped before returning back to caller.

  Target Release: 20.04
  Target Kernel: TBD

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

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

[Kernel-packages] [Bug 1843487] Re: UIO: mutex used in interrupt handler causes crash

[Tom Brezinski]

** Tags added: bionic

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

Title:
  UIO: mutex used in interrupt handler causes crash

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Running:
  Bionic Beaver
  Ubuntu 4.15.0-62.69-generic 4.15.18

  In commit 725bbc87 on 2/13/2019 in uio.c a mutex_lock was added to
  uio_interrupt.  This results in a "scheduling while atomic" error if
  someone else owns the mutex at the time it is invoked.

  [ 1941.409212] BUG: scheduling while atomic: fcasm-test/3937/0x0001
  [ 1941.409216] Modules linked in: cdc_ether usbnet r8152 mii rfcomm ccm bnep 
arc4 nls_iso8859_1 snd_hda_codec_hdmi hid_multitouch dell_laptop 
intel_wmi_thunderbolt dell_wmi wmi_bmof dell_smbios dcdbas dell_wmi_descriptor 
snd_soc_skl snd_hda_codec_realtek snd_soc_skl_ipc snd_hda_codec_generic 
snd_hda_ext_core snd_soc_sst_dsp snd_soc_sst_ipc snd_soc_acpi snd_soc_core 
snd_compress ac97_bus snd_pcm_dmaengine intel_rapl ath10k_pci 
x86_pkg_temp_thermal intel_powerclamp ath10k_core coretemp kvm_intel ath kvm 
mac80211 irqbypass crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc 
cfg80211 aesni_intel rtsx_pci_ms aes_x86_64 memstick crypto_simd glue_helper 
cryptd intel_cstate intel_rapl_perf snd_hda_intel snd_hda_codec snd_hda_core 
snd_hwdep snd_pcm snd_seq_midi snd_seq_midi_event snd_rawmidi snd_seq joydev
  [ 1941.409247]  input_leds serio_raw snd_seq_device snd_timer idma64 snd 
virt_dma soundcore i915 mei_me mei shpchp uvcvideo btusb drm_kms_helper btrtl 
videobuf2_vmalloc btbcm intel_lpss_pci videobuf2_memops btintel intel_lpss drm 
videobuf2_v4l2 bluetooth videobuf2_core intel_pch_thermal i2c_algo_bit videodev 
fb_sys_fops syscopyarea processor_thermal_device sysfillrect media ecdh_generic 
sysimgblt intel_soc_dts_iosf wmi intel_hid int3400_thermal int3403_thermal 
int340x_thermal_zone acpi_thermal_rel sparse_keymap mac_hid acpi_pad video 
sch_fq_codel nfsd uio_nwdv(OE) auth_rpcgss nfs_acl uio lockd grace parport_pc 
ppdev sunrpc lp parport ip_tables x_tables autofs4 nvme rtsx_pci_sdmmc psmouse 
nvme_core thunderbolt rtsx_pci i2c_hid hid pinctrl_sunrisepoint
  [ 1941.409281] CPU: 3 PID: 3937 Comm: fcasm-test Tainted: G   OE
4.15.0-62-generic #69-Ubuntu
  [ 1941.409282] Hardware name: Dell Inc. XPS 13 9370/0F6P3V, BIOS 1.10.0 
04/18/2019
  [ 1941.409282] Call Trace:
  [ 1941.409284]  
  [ 1941.409290]  dump_stack+0x63/0x8b
  [ 1941.409293]  __schedule_bug+0x55/0x70
  [ 1941.409295]  __schedule+0x658/0x880
  [ 1941.409297]  ? default_wake_function+0x12/0x20
  [ 1941.409298]  ? pollwake+0x73/0x90
  [ 1941.409300]  schedule+0x2c/0x80
  [ 1941.409302]  schedule_preempt_disabled+0xe/0x10
  [ 1941.409303]  __mutex_lock.isra.5+0x478/0x4e0
  [ 1941.409304]  __mutex_lock_slowpath+0x13/0x20
  [ 1941.409305]  ? __mutex_lock_slowpath+0x13/0x20
  [ 1941.409306]  mutex_lock+0x2f/0x40
  [ 1941.409309]  uio_interrupt+0x23/0x70 [uio]
  [ 1941.409311]  __handle_irq_event_percpu+0x44/0x1a0
  [ 1941.409313]  handle_irq_event_percpu+0x32/0x80
  [ 1941.409315]  handle_irq_event+0x3b/0x60
  [ 1941.409316]  handle_fasteoi_irq+0x7c/0x130
  [ 1941.409318]  handle_irq+0x20/0x30
  [ 1941.409319]  do_IRQ+0x50/0xe0
  [ 1941.409321]  common_interrupt+0x8c/0x8c
  [ 1941.409322]  
  [ 1941.409323] RIP: 0010:mutex_lock+0x22/0x40
  [ 1941.409324] RSP: 0018:b68681b9b950 EFLAGS: 0246 ORIG_RAX: 
ffdc
  [ 1941.409325] RAX:  RBX: 8ae612f8af10 RCX: 

  [ 1941.409326] RDX: 8ae51b319740 RSI: b68681b9ba70 RDI: 
8ae612f8af10
  [ 1941.409327] RBP: b68681b9b958 R08: 8ae4ffa35200 R09: 
c04c7120
  [ 1941.409327] R10: 0001 R11: 0389cc0215b7 R12: 
8ae612f8af10
  [ 1941.409328] R13: 8ae512de6bb0 R14: 8ae4ffa35200 R15: 
b68681b9ba70
  [ 1941.409330]  ? uio_interrupt+0x70/0x70 [uio]
  [ 1941.409331]  uio_poll+0x32/0xb0 [uio]
  [ 1941.409333]  do_select+0x384/0x7e0
  [ 1941.409335]  ? compat_poll_select_copy_remaining+0x130/0x130
  [ 1941.409338]  ? __update_load_avg_se.isra.37+0x1c0/0x1d0
  [ 1941.409339]  ? __update_load_avg_se.isra.37+0x1c0/0x1d0
  [ 1941.409341]  ? find_next_bit+0xb/0x10
  [ 1941.409342]  ? update_load_avg+0x3b0/0x6e0
  [ 1941.409343]  ? update_curr+0x7a/0x1d0
  [ 1941.409344]  ? reweight_entity+0x155/0x1a0
  [ 1941.409345]  ? check_preempt_wakeup+0x10e/0x240
  [ 1941.409347]  ? check_preempt_curr+0x2d/0x90
  [ 1941.409348]  ? ttwu_do_wakeup+0x1e/0x140
  [ 1941.409349]  core_sys_select+0x1d9/0x320
  [ 1941.409350]  ? core_sys_select+0x1d9/0x320
  [ 1941.409353]  ? ktime_get_ts64+0x51/0xf0
  [ 1941.409354]  SyS_select+0xb7/0x110
  [ 1941.409357]  do_syscall_64+0x73/0x130
  [ 1941.409358]  entry_SYSCALL_64_after_hwframe+0x3d/0xa2
  [ 1941.409359] RIP: 0033:0x7f8a46a4803f
  [ 1941.409360] RSP: 002b:7f8a45d91db0 EFLAGS: 0293 ORIG_RAX: 
0017
  [ 

[Kernel-packages] [Bug 1843489] [NEW] Audit IOMMU capabilities and disable if there are some incompatible IOMMU's in the platform

[quanxian]

Public bug reported:

Description
Audit the capabilities and extended capabilities and disable IOMMU if there is 
incompatibility between them.

For e.g. cap.first_level_1G_page support=0, and kernel has enabled 1G
pages, we should disable SVM on that IOMMU.

Audit code for any other anomalies like this, for e.g. difference in
address bits supported, HAW, AGAW etc we should disable IOMMU for the
whole system if these differences can lead to improper behavior.

Target Release: 20.04
Target Kernel: TBD

** Affects: intel
 Importance: Undecided
 Status: New

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


** Tags: intel-kernel-20.04

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

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

Title:
  Audit IOMMU capabilities and disable if there are some incompatible
  IOMMU's in the platform

Status in intel:
  New
Status in linux package in Ubuntu:
  New

Bug description:
  Description
  Audit the capabilities and extended capabilities and disable IOMMU if there 
is incompatibility between them.

  For e.g. cap.first_level_1G_page support=0, and kernel has enabled 1G
  pages, we should disable SVM on that IOMMU.

  Audit code for any other anomalies like this, for e.g. difference in
  address bits supported, HAW, AGAW etc we should disable IOMMU for the
  whole system if these differences can lead to improper behavior.

  Target Release: 20.04
  Target Kernel: TBD

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

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

[Kernel-packages] [Bug 1759836] Re: systemd-udevd consumes 100% of CPU

[Jón Bjarni Bjarnason]

Sorry for the late reply. Here comes the output:
KERNEL[90619.640204] remove   /module/nvidia (module)
UDEV  [90619.659490] add  /kernel/slab/:0012288 (slab)
KERNEL[90619.696504] add  /module/nvidia (module)
KERNEL[90619.697757] add  /kernel/slab/:0012288 (slab)
KERNEL[90619.697792] add  /bus/pci/drivers/nvidia-nvswitch (drivers)
KERNEL[90619.698144] remove   /bus/pci/drivers/nvidia-nvswitch (drivers)
UDEV  [90619.734780] add  /bus/pci/drivers/nvidia-nvswitch (drivers)
KERNEL[90619.760125] remove   /kernel/slab/:0012288 (slab)
KERNEL[90619.780134] remove   /module/nvidia (module)
UDEV  [90619.799634] add  /module/nvidia (module)
UDEV  [90619.863581] remove   /module/nvidia (module)
UDEV  [90619.914399] remove   /bus/pci/drivers/nvidia-nvswitch (drivers)
UDEV  [90619.980993] remove   /kernel/slab/:0012288 (slab)
KERNEL[90619.987727] add  
/kernel/slab/:A-256/cgroup/filp(351529:nvidia-persistenced.service) (cgroup)
KERNEL[90619.987765] add  
/kernel/slab/dentry/cgroup/dentry(351529:nvidia-persistenced.service) (cgroup)
KERNEL[90619.987787] add  
/kernel/slab/inode_cache/cgroup/inode_cache(351529:nvidia-persistenced.service) 
(cgroup)
KERNEL[90619.987807] add  
/kernel/slab/:A-128/cgroup/pid(351529:nvidia-persistenced.service) (cgroup)
KERNEL[90619.987827] add  
/kernel/slab/sock_inode_cache/cgroup/sock_inode_cache(351529:nvidia-persistenced.service)
 (cgroup)
KERNEL[90619.987846] add  
/kernel/slab/:A-0001024/cgroup/UNIX(351529:nvidia-persistenced.service) (cgroup)
KERNEL[90619.987873] add  
/kernel/slab/skbuff_head_cache/cgroup/skbuff_head_cache(351529:nvidia-persistenced.service)
 (cgroup)
KERNEL[90619.987893] add  
/kernel/slab/kmalloc-512/cgroup/kmalloc-512(351529:nvidia-persistenced.service) 
(cgroup)
KERNEL[90619.987918] add  
/kernel/slab/:A-192/cgroup/cred_jar(351529:nvidia-persistenced.service) 
(cgroup)
KERNEL[90619.987938] add  
/kernel/slab/mm_struct/cgroup/mm_struct(351529:nvidia-persistenced.service) 
(cgroup)
KERNEL[90619.987956] add  
/kernel/slab/:A-208/cgroup/vm_area_struct(351529:nvidia-persistenced.service)
 (cgroup)
KERNEL[90619.988007] add  
/kernel/slab/:A-064/cgroup/anon_vma_chain(351529:nvidia-persistenced.service)
 (cgroup)
KERNEL[90619.988029] add  
/kernel/slab/anon_vma/cgroup/anon_vma(351529:nvidia-persistenced.service) 
(cgroup)
KERNEL[90619.988058] add  
/kernel/slab/kmalloc-192/cgroup/kmalloc-192(351529:nvidia-persistenced.service) 
(cgroup)
KERNEL[90619.988076] add  
/kernel/slab/kmalloc-1k/cgroup/kmalloc-1k(351529:nvidia-persistenced.service) 
(cgroup)
KERNEL[90619.988094] add  
/kernel/slab/task_struct/cgroup/task_struct(351529:nvidia-persistenced.service) 
(cgroup)
KERNEL[90619.988113] add  
/kernel/slab/:A-080/cgroup/task_delay_info(351529:nvidia-persistenced.service)
 (cgroup)
KERNEL[90619.988128] add  
/kernel/slab/:A-704/cgroup/files_cache(351529:nvidia-persistenced.service) 
(cgroup)
KERNEL[90619.988144] add  
/kernel/slab/sighand_cache/cgroup/sighand_cache(351529:nvidia-persistenced.service)
 (cgroup)
KERNEL[90619.988159] add  
/kernel/slab/:A-0001088/cgroup/signal_cache(351529:nvidia-persistenced.service) 
(cgroup)
KERNEL[90619.989100] add  
/kernel/slab/shmem_inode_cache/cgroup/shmem_inode_cache(351529:nvidia-persistenced.service)
 (cgroup)
KERNEL[90619.989133] add  
/kernel/slab/:A-040/cgroup/pde_opener(351529:nvidia-persistenced.service) 
(cgroup)
KERNEL[90619.989163] add  
/kernel/slab/kmalloc-4k/cgroup/kmalloc-4k(351529:nvidia-persistenced.service) 
(cgroup)
KERNEL[90620.018974] add  /module/nvidia (module)
KERNEL[90620.019912] add  /kernel/slab/:0012288 (slab)
KERNEL[90620.019938] add  /bus/pci/drivers/nvidia-nvswitch (drivers)
KERNEL[90620.020631] remove   /bus/pci/drivers/nvidia-nvswitch (drivers)
KERNEL[90620.080127] remove   /kernel/slab/:0012288 (slab)
KERNEL[90620.104154] remove   /module/nvidia (module)
KERNEL[90620.137366] add  /module/nvidia (module)
KERNEL[90620.138144] add  /kernel/slab/:0012288 (slab)
KERNEL[90620.138175] add  /bus/pci/drivers/nvidia-nvswitch (drivers)
KERNEL[90620.138657] remove   /bus/pci/drivers/nvidia-nvswitch (drivers)


** Attachment added: "longer log"
   
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1759836/+attachment/5287861/+files/udevd.log

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

Title:
  systemd-udevd consumes 100% of CPU

Status in linux:
  Confirmed
Status in The Ubuntu Power Consumption Project:
  New
Status in bluez package in Ubuntu:
  In Progress
Status in linux package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Invalid
Status in bluez package in Debian:
  New

Bug description:
  The systemd-udevd proccess consumes 100% of a thread everytime, but
  i'm not noticing any difference in my 

[Kernel-packages] [Bug 1843487] Re: UIO: mutex used in interrupt handler causes crash

[Tom Brezinski]

** Description changed:

+ Running:
+ Bionic Beaver
  Ubuntu 4.15.0-62.69-generic 4.15.18
  
  In commit 725bbc87 on 2/13/2019 in uio.c a mutex_lock was added to
  uio_interrupt.  This results in a "scheduling while atomic" error if
  someone else owns the mutex at the time it is invoked.
  
  [ 1941.409212] BUG: scheduling while atomic: fcasm-test/3937/0x0001
  [ 1941.409216] Modules linked in: cdc_ether usbnet r8152 mii rfcomm ccm bnep 
arc4 nls_iso8859_1 snd_hda_codec_hdmi hid_multitouch dell_laptop 
intel_wmi_thunderbolt dell_wmi wmi_bmof dell_smbios dcdbas dell_wmi_descriptor 
snd_soc_skl snd_hda_codec_realtek snd_soc_skl_ipc snd_hda_codec_generic 
snd_hda_ext_core snd_soc_sst_dsp snd_soc_sst_ipc snd_soc_acpi snd_soc_core 
snd_compress ac97_bus snd_pcm_dmaengine intel_rapl ath10k_pci 
x86_pkg_temp_thermal intel_powerclamp ath10k_core coretemp kvm_intel ath kvm 
mac80211 irqbypass crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc 
cfg80211 aesni_intel rtsx_pci_ms aes_x86_64 memstick crypto_simd glue_helper 
cryptd intel_cstate intel_rapl_perf snd_hda_intel snd_hda_codec snd_hda_core 
snd_hwdep snd_pcm snd_seq_midi snd_seq_midi_event snd_rawmidi snd_seq joydev
  [ 1941.409247]  input_leds serio_raw snd_seq_device snd_timer idma64 snd 
virt_dma soundcore i915 mei_me mei shpchp uvcvideo btusb drm_kms_helper btrtl 
videobuf2_vmalloc btbcm intel_lpss_pci videobuf2_memops btintel intel_lpss drm 
videobuf2_v4l2 bluetooth videobuf2_core intel_pch_thermal i2c_algo_bit videodev 
fb_sys_fops syscopyarea processor_thermal_device sysfillrect media ecdh_generic 
sysimgblt intel_soc_dts_iosf wmi intel_hid int3400_thermal int3403_thermal 
int340x_thermal_zone acpi_thermal_rel sparse_keymap mac_hid acpi_pad video 
sch_fq_codel nfsd uio_nwdv(OE) auth_rpcgss nfs_acl uio lockd grace parport_pc 
ppdev sunrpc lp parport ip_tables x_tables autofs4 nvme rtsx_pci_sdmmc psmouse 
nvme_core thunderbolt rtsx_pci i2c_hid hid pinctrl_sunrisepoint
  [ 1941.409281] CPU: 3 PID: 3937 Comm: fcasm-test Tainted: G   OE
4.15.0-62-generic #69-Ubuntu
  [ 1941.409282] Hardware name: Dell Inc. XPS 13 9370/0F6P3V, BIOS 1.10.0 
04/18/2019
  [ 1941.409282] Call Trace:
  [ 1941.409284]  
  [ 1941.409290]  dump_stack+0x63/0x8b
  [ 1941.409293]  __schedule_bug+0x55/0x70
  [ 1941.409295]  __schedule+0x658/0x880
  [ 1941.409297]  ? default_wake_function+0x12/0x20
  [ 1941.409298]  ? pollwake+0x73/0x90
  [ 1941.409300]  schedule+0x2c/0x80
  [ 1941.409302]  schedule_preempt_disabled+0xe/0x10
  [ 1941.409303]  __mutex_lock.isra.5+0x478/0x4e0
  [ 1941.409304]  __mutex_lock_slowpath+0x13/0x20
  [ 1941.409305]  ? __mutex_lock_slowpath+0x13/0x20
  [ 1941.409306]  mutex_lock+0x2f/0x40
  [ 1941.409309]  uio_interrupt+0x23/0x70 [uio]
  [ 1941.409311]  __handle_irq_event_percpu+0x44/0x1a0
  [ 1941.409313]  handle_irq_event_percpu+0x32/0x80
  [ 1941.409315]  handle_irq_event+0x3b/0x60
  [ 1941.409316]  handle_fasteoi_irq+0x7c/0x130
  [ 1941.409318]  handle_irq+0x20/0x30
  [ 1941.409319]  do_IRQ+0x50/0xe0
  [ 1941.409321]  common_interrupt+0x8c/0x8c
  [ 1941.409322]  
  [ 1941.409323] RIP: 0010:mutex_lock+0x22/0x40
  [ 1941.409324] RSP: 0018:b68681b9b950 EFLAGS: 0246 ORIG_RAX: 
ffdc
  [ 1941.409325] RAX:  RBX: 8ae612f8af10 RCX: 

  [ 1941.409326] RDX: 8ae51b319740 RSI: b68681b9ba70 RDI: 
8ae612f8af10
  [ 1941.409327] RBP: b68681b9b958 R08: 8ae4ffa35200 R09: 
c04c7120
  [ 1941.409327] R10: 0001 R11: 0389cc0215b7 R12: 
8ae612f8af10
  [ 1941.409328] R13: 8ae512de6bb0 R14: 8ae4ffa35200 R15: 
b68681b9ba70
  [ 1941.409330]  ? uio_interrupt+0x70/0x70 [uio]
  [ 1941.409331]  uio_poll+0x32/0xb0 [uio]
  [ 1941.409333]  do_select+0x384/0x7e0
  [ 1941.409335]  ? compat_poll_select_copy_remaining+0x130/0x130
  [ 1941.409338]  ? __update_load_avg_se.isra.37+0x1c0/0x1d0
  [ 1941.409339]  ? __update_load_avg_se.isra.37+0x1c0/0x1d0
  [ 1941.409341]  ? find_next_bit+0xb/0x10
  [ 1941.409342]  ? update_load_avg+0x3b0/0x6e0
  [ 1941.409343]  ? update_curr+0x7a/0x1d0
  [ 1941.409344]  ? reweight_entity+0x155/0x1a0
  [ 1941.409345]  ? check_preempt_wakeup+0x10e/0x240
  [ 1941.409347]  ? check_preempt_curr+0x2d/0x90
  [ 1941.409348]  ? ttwu_do_wakeup+0x1e/0x140
  [ 1941.409349]  core_sys_select+0x1d9/0x320
  [ 1941.409350]  ? core_sys_select+0x1d9/0x320
  [ 1941.409353]  ? ktime_get_ts64+0x51/0xf0
  [ 1941.409354]  SyS_select+0xb7/0x110
  [ 1941.409357]  do_syscall_64+0x73/0x130
  [ 1941.409358]  entry_SYSCALL_64_after_hwframe+0x3d/0xa2
  [ 1941.409359] RIP: 0033:0x7f8a46a4803f
  [ 1941.409360] RSP: 002b:7f8a45d91db0 EFLAGS: 0293 ORIG_RAX: 
0017
  [ 1941.409361] RAX: ffda RBX: 0400 RCX: 
7f8a46a4803f
  [ 1941.409362] RDX:  RSI: 7f8a45d91e30 RDI: 
0400
  [ 1941.409362] RBP: 7f8a45d91e30 R08: 7f8a45d91e20 R09: 

  [ 1941.409363] R10:  

[Kernel-packages] [Bug 1843487] [NEW] UIO: mutex used in interrupt handler causes crash

[Tom Brezinski]

Public bug reported:

Ubuntu 4.15.0-62.69-generic 4.15.18

In commit 725bbc87 on 2/13/2019 in uio.c a mutex_lock was added to
uio_interrupt.  This results in a "scheduling while atomic" error if
someone else owns the mutex at the time it is invoked.

[ 1941.409212] BUG: scheduling while atomic: fcasm-test/3937/0x0001
[ 1941.409216] Modules linked in: cdc_ether usbnet r8152 mii rfcomm ccm bnep 
arc4 nls_iso8859_1 snd_hda_codec_hdmi hid_multitouch dell_laptop 
intel_wmi_thunderbolt dell_wmi wmi_bmof dell_smbios dcdbas dell_wmi_descriptor 
snd_soc_skl snd_hda_codec_realtek snd_soc_skl_ipc snd_hda_codec_generic 
snd_hda_ext_core snd_soc_sst_dsp snd_soc_sst_ipc snd_soc_acpi snd_soc_core 
snd_compress ac97_bus snd_pcm_dmaengine intel_rapl ath10k_pci 
x86_pkg_temp_thermal intel_powerclamp ath10k_core coretemp kvm_intel ath kvm 
mac80211 irqbypass crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc 
cfg80211 aesni_intel rtsx_pci_ms aes_x86_64 memstick crypto_simd glue_helper 
cryptd intel_cstate intel_rapl_perf snd_hda_intel snd_hda_codec snd_hda_core 
snd_hwdep snd_pcm snd_seq_midi snd_seq_midi_event snd_rawmidi snd_seq joydev
[ 1941.409247]  input_leds serio_raw snd_seq_device snd_timer idma64 snd 
virt_dma soundcore i915 mei_me mei shpchp uvcvideo btusb drm_kms_helper btrtl 
videobuf2_vmalloc btbcm intel_lpss_pci videobuf2_memops btintel intel_lpss drm 
videobuf2_v4l2 bluetooth videobuf2_core intel_pch_thermal i2c_algo_bit videodev 
fb_sys_fops syscopyarea processor_thermal_device sysfillrect media ecdh_generic 
sysimgblt intel_soc_dts_iosf wmi intel_hid int3400_thermal int3403_thermal 
int340x_thermal_zone acpi_thermal_rel sparse_keymap mac_hid acpi_pad video 
sch_fq_codel nfsd uio_nwdv(OE) auth_rpcgss nfs_acl uio lockd grace parport_pc 
ppdev sunrpc lp parport ip_tables x_tables autofs4 nvme rtsx_pci_sdmmc psmouse 
nvme_core thunderbolt rtsx_pci i2c_hid hid pinctrl_sunrisepoint
[ 1941.409281] CPU: 3 PID: 3937 Comm: fcasm-test Tainted: G   OE
4.15.0-62-generic #69-Ubuntu
[ 1941.409282] Hardware name: Dell Inc. XPS 13 9370/0F6P3V, BIOS 1.10.0 
04/18/2019
[ 1941.409282] Call Trace:
[ 1941.409284]  
[ 1941.409290]  dump_stack+0x63/0x8b
[ 1941.409293]  __schedule_bug+0x55/0x70
[ 1941.409295]  __schedule+0x658/0x880
[ 1941.409297]  ? default_wake_function+0x12/0x20
[ 1941.409298]  ? pollwake+0x73/0x90
[ 1941.409300]  schedule+0x2c/0x80
[ 1941.409302]  schedule_preempt_disabled+0xe/0x10
[ 1941.409303]  __mutex_lock.isra.5+0x478/0x4e0
[ 1941.409304]  __mutex_lock_slowpath+0x13/0x20
[ 1941.409305]  ? __mutex_lock_slowpath+0x13/0x20
[ 1941.409306]  mutex_lock+0x2f/0x40
[ 1941.409309]  uio_interrupt+0x23/0x70 [uio]
[ 1941.409311]  __handle_irq_event_percpu+0x44/0x1a0
[ 1941.409313]  handle_irq_event_percpu+0x32/0x80
[ 1941.409315]  handle_irq_event+0x3b/0x60
[ 1941.409316]  handle_fasteoi_irq+0x7c/0x130
[ 1941.409318]  handle_irq+0x20/0x30
[ 1941.409319]  do_IRQ+0x50/0xe0
[ 1941.409321]  common_interrupt+0x8c/0x8c
[ 1941.409322]  
[ 1941.409323] RIP: 0010:mutex_lock+0x22/0x40
[ 1941.409324] RSP: 0018:b68681b9b950 EFLAGS: 0246 ORIG_RAX: 
ffdc
[ 1941.409325] RAX:  RBX: 8ae612f8af10 RCX: 
[ 1941.409326] RDX: 8ae51b319740 RSI: b68681b9ba70 RDI: 8ae612f8af10
[ 1941.409327] RBP: b68681b9b958 R08: 8ae4ffa35200 R09: c04c7120
[ 1941.409327] R10: 0001 R11: 0389cc0215b7 R12: 8ae612f8af10
[ 1941.409328] R13: 8ae512de6bb0 R14: 8ae4ffa35200 R15: b68681b9ba70
[ 1941.409330]  ? uio_interrupt+0x70/0x70 [uio]
[ 1941.409331]  uio_poll+0x32/0xb0 [uio]
[ 1941.409333]  do_select+0x384/0x7e0
[ 1941.409335]  ? compat_poll_select_copy_remaining+0x130/0x130
[ 1941.409338]  ? __update_load_avg_se.isra.37+0x1c0/0x1d0
[ 1941.409339]  ? __update_load_avg_se.isra.37+0x1c0/0x1d0
[ 1941.409341]  ? find_next_bit+0xb/0x10
[ 1941.409342]  ? update_load_avg+0x3b0/0x6e0
[ 1941.409343]  ? update_curr+0x7a/0x1d0
[ 1941.409344]  ? reweight_entity+0x155/0x1a0
[ 1941.409345]  ? check_preempt_wakeup+0x10e/0x240
[ 1941.409347]  ? check_preempt_curr+0x2d/0x90
[ 1941.409348]  ? ttwu_do_wakeup+0x1e/0x140
[ 1941.409349]  core_sys_select+0x1d9/0x320
[ 1941.409350]  ? core_sys_select+0x1d9/0x320
[ 1941.409353]  ? ktime_get_ts64+0x51/0xf0
[ 1941.409354]  SyS_select+0xb7/0x110
[ 1941.409357]  do_syscall_64+0x73/0x130
[ 1941.409358]  entry_SYSCALL_64_after_hwframe+0x3d/0xa2
[ 1941.409359] RIP: 0033:0x7f8a46a4803f
[ 1941.409360] RSP: 002b:7f8a45d91db0 EFLAGS: 0293 ORIG_RAX: 
0017
[ 1941.409361] RAX: ffda RBX: 0400 RCX: 7f8a46a4803f
[ 1941.409362] RDX:  RSI: 7f8a45d91e30 RDI: 0400
[ 1941.409362] RBP: 7f8a45d91e30 R08: 7f8a45d91e20 R09: 
[ 1941.409363] R10:  R11: 0293 R12: 
[ 1941.409364] R13:  R14: 7f8a45d91e20 R15: 55d1091c0180

** Affects: linux (Ubuntu)
 Importance: 

[Kernel-packages] [Bug 1842714] Re: bionic/linux-oem: 4.15.0-1054.63 -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
  
  -- swm properties --
+ boot-testing-requested: true
  kernel-stable-master-bug: 1842746
  packages:
lrm: linux-restricted-modules-oem
main: linux-oem
meta: linux-meta-oem
signed: linux-signed-oem
- phase: Holding before Promote to Proposed
- phase-changed: Tuesday, 10. September 2019 13:12 UTC
+ phase: Ready for Promote to Proposed
+ phase-changed: Tuesday, 10. September 2019 19:06 UTC
  reason:
-   promote-to-proposed: Pending -- builds not complete in ppa lrm:queued
- replaces: bug 1842418
+   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-oem in Ubuntu.
https://bugs.launchpad.net/bugs/1842714

Title:
  bionic/linux-oem: 4.15.0-1054.63 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-lrm series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  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-oem package in Ubuntu:
  Invalid
Status in linux-oem 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: 1842746
  packages:
lrm: linux-restricted-modules-oem
main: linux-oem
meta: linux-meta-oem
signed: linux-signed-oem
  phase: Ready for Promote to Proposed
  phase-changed: Tuesday, 10. September 2019 19:06 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/1842714/+subscriptions

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

[Kernel-packages] [Bug 1842714] Re: bionic/linux-oem: 4.15.0-1054.63 -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: 1842746
  packages:
lrm: linux-restricted-modules-oem
main: linux-oem
meta: linux-meta-oem
signed: linux-signed-oem
  phase: Holding before Promote to Proposed
  phase-changed: Tuesday, 10. September 2019 13:12 UTC
  reason:
-   promote-to-proposed: Ongoing -- builds not complete in ppa 
lrm:depwait,meta:depwait,signed:depwait
+   promote-to-proposed: Pending -- builds not complete in ppa lrm:queued
  replaces: bug 1842418
  variant: debs

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

Title:
  bionic/linux-oem: 4.15.0-1054.63 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-lrm series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-oem package in Ubuntu:
  Invalid
Status in linux-oem 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 --
  kernel-stable-master-bug: 1842746
  packages:
lrm: linux-restricted-modules-oem
main: linux-oem
meta: linux-meta-oem
signed: linux-signed-oem
  phase: Holding before Promote to Proposed
  phase-changed: Tuesday, 10. September 2019 13:12 UTC
  reason:
promote-to-proposed: Pending -- builds not complete in ppa lrm:queued
  replaces: bug 1842418
  variant: debs

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

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

[Kernel-packages] [Bug 1843463] Re: Bionic update: upstream stable patchset 2019-09-10

[Kamal Mostafa]

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

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

** Description changed:

+ SRU Justification
  
- 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:
  
- 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-09-10
  
-upstream stable patchset 2019-09-10
-from git://git.kernel.org/
+   Ported from the following upstream stable releases:
+   v4.14.143, v4.19.72
+ 
+    from git://git.kernel.org/

** Description changed:

  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-09-10
  
-   Ported from the following upstream stable releases:
-   v4.14.143, v4.19.72
+   Ported from the following upstream stable releases:
+    v4.14.143, v4.19.72
  
     from git://git.kernel.org/
+ 
+ net: tundra: tsi108: use spin_lock_irqsave instead of spin_lock_irq in IRQ 
context
+ hv_netvsc: Fix a warning of suspicious RCU usage
+ net: tc35815: Explicitly check NET_IP_ALIGN is not zero in tc35815_rx
+ Bluetooth: btqca: Add a short delay before downloading the NVM
+ ibmveth: Convert multicast list size for little-endian system
+ gpio: Fix build error of function redefinition
+ drm/mediatek: use correct device to import PRIME buffers
+ drm/mediatek: set DMA max segment size
+ cxgb4: fix a memory leak bug
+ liquidio: add cleanup in octeon_setup_iq()
+ net: myri10ge: fix memory leaks
+ lan78xx: Fix memory leaks
+ vfs: fix page locking deadlocks when deduping files
+ cx82310_eth: fix a memory leak bug
+ net: kalmia: fix memory leaks
+ wimax/i2400m: fix a memory leak bug
+ ravb: Fix use-after-free ravb_tstamp_skb
+ kprobes: Fix potential deadlock in kprobe_optimizer()
+ HID: cp2112: prevent sleeping function called from invalid context
+ Input: hyperv-keyboard: Use in-place iterator API in the channel callback
+ Tools: hv: kvp: eliminate 'may be used uninitialized' warning
+ IB/mlx4: Fix memory leaks
+ ceph: fix buffer free while holding i_ceph_lock in __ceph_setxattr()
+ ceph: fix buffer free while holding i_ceph_lock in __ceph_build_xattrs_blob()
+ ceph: fix buffer free while holding i_ceph_lock in fill_inode()
+ KVM: arm/arm64: Only skip MMIO insn once
+ libceph: allow ceph_buffer_put() to receive a NULL ceph_buffer
+ spi: bcm2835aux: unifying code between polling and interrupt driven code
+ spi: bcm2835aux: remove dangerous uncontrolled read of fifo
+ spi: bcm2835aux: fix corruptions for longer spi transfers
+ net: fix skb use after free in netpoll
+ net_sched: fix a NULL pointer deref in ipt action
+ net: stmmac: dwmac-rk: Don't fail if phy regulator is absent
+ tcp: inherit timestamp on mtu probe
+ tcp: remove empty skb from write queue in error cases
+ net: sched: act_sample: fix psample group handling on overwrite
+ mld: fix memory leak in mld_del_delrec()
+ x86/boot: Preserve boot_params.secure_boot from sanitizing
+ tools: bpftool: fix error message (prog -> object)
+ scsi: qla2xxx: Fix gnl.l memory leak on adapter init failure
+ afs: Fix leak in afs_lookup_cell_rcu()
+ UBUNTU: upstream stable to v4.14.143, v4.19.72

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

Title:
  Bionic update: upstream stable patchset 2019-09-10

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 

[Kernel-packages] [Bug 1836739] Re: [19.10 FEAT] Enhanced CPU-MF hardware counters fix

[Frank Heimes]

I quickly checked the kernel commit and it's incl. in Eoan's master-next
tree that contains 5.3-rc8

workstation:~/ubuntu-eoan-master-next/ubuntu-eoan$ git log --oneline --grep 
"s390/cpumf: Add extended counter set definitions for model 8561 and 8562"
aabfea8 Merge tag 's390-5.3-2' of 
git://git.kernel.org/pub/scm/linux/kernel/git/s390/linux
820bace s390/cpumf: Add extended counter set definitions for model 8561 and 8562
workstation:~/ubuntu-eoan-master-next/ubuntu-eoan$ git describe --tags 
--contains 820bace
v5.3-rc8~365^2~6

(the kernel based on that is also available from proposed:
 linux-generic | 5.3.0.10.11 | eoan-proposed | s390x)

Hence changing this ticket to Fix Committed.


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

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

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

Title:
  [19.10 FEAT] Enhanced CPU-MF hardware counters fix

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

Bug description:
  Feature request to add a fix need to be applied on top of kernel 5.2-.

  Already Fix Released feature:
  LP: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1834201

  Require git commit from kernel 5.3 :
  https://github.com/torvalds/linux/commit/820bace73472

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

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

[Kernel-packages] [Bug 1830731] Re: [19.10 FEAT] Thin provisioning base support (kernel+390tools)

[Frank Heimes]

I quickly double checked the kernel commits, almost all got upstream accepted 
with 5.3-rc2, hence all are incl. in Eoan's master-next tree that contains 
5.3-rc8
(that's available from proposed:
 linux-generic | 5.3.0.10.11   | eoan-proposed   | s390x)
Hence changing the kernel entry here to Fix Committed.

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

** Changed in: ubuntu-z-systems
   Status: Incomplete => 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/1830731

Title:
  [19.10 FEAT] Thin provisioning base support (kernel+390tools)

Status in Ubuntu on IBM z Systems:
  In Progress
Status in linux package in Ubuntu:
  Fix Committed
Status in s390-tools package in Ubuntu:
  Incomplete

Bug description:
  Enable use of thin provisioned ECKD volumes.
  Efficient use of storage resources and reduced deployment time for ECKD 
volumes .

  Tentative Target is kernel 5.3 + s390tools
  Assumption from crystal balls
  merge window closes on Sunday, 2019-07-28 and release on Sunday, 2019-09-15

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

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

[Kernel-packages] [Bug 1843463] [NEW] Bionic update: upstream stable patchset 2019-09-10

[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-09-10
   from git://git.kernel.org/

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

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


** Tags: kernel-stable-tracking-bug

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

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

** Also affects: linux (Ubuntu Bionic)
   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/1843463

Title:
  Bionic update: upstream stable patchset 2019-09-10

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

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-09-10
 from git://git.kernel.org/

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

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

[Kernel-packages] [Bug 1842542] Re: disco/linux-aws: 5.0.0-1015.17 -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: 1842561
  packages:
main: linux-aws
meta: linux-meta-aws
  phase: Ready for Promote to Proposed
  phase-changed: Tuesday, 10. September 2019 04:40 UTC
  reason:
-   promote-to-proposed: Pending -- ready for review
+   promote-to-proposed: Stalled -- ready for review
  trackers:
bionic/linux-aws-edge: bug 1842830
  variant: debs

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

Title:
  disco/linux-aws: 5.0.0-1015.17 -proposed tracker

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

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1842561
  packages:
main: linux-aws
meta: linux-meta-aws
  phase: Ready for Promote to Proposed
  phase-changed: Tuesday, 10. September 2019 04:40 UTC
  reason:
promote-to-proposed: Stalled -- ready for review
  trackers:
bionic/linux-aws-edge: bug 1842830
  variant: debs

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

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

[Kernel-packages] [Bug 1842834] Re: bionic/linux-azure: 5.0.0-1019.20~18.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 --
  kernel-stable-master-bug: 1842546
  packages:
lrm: linux-restricted-modules-azure
main: linux-azure
meta: linux-meta-azure
signed: linux-signed-azure
- phase: Ready for Packaging
- phase-changed: Monday, 09. September 2019 10:43 UTC
+ phase: Packaging
+ phase-changed: Tuesday, 10. September 2019 16:16 UTC
  reason:
-   prepare-package: Pending -- version not specified
+   prepare-package: Pending -- package not yet uploaded
+   prepare-package-lrm: Pending -- package not yet uploaded
+   prepare-package-meta: Pending -- package not yet uploaded
+   prepare-package-signed: Pending -- package not yet uploaded
  replaces: bug 1842545
  trackers:
bionic/linux-azure-edge: bug 1842833
bionic/linux-azure/azure-kernel: bug 1842832
  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/1842834

Title:
  bionic/linux-azure: 5.0.0-1019.20~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:
  In Progress
Status in Kernel SRU Workflow prepare-package-lrm series:
  In Progress
Status in Kernel SRU Workflow prepare-package-meta series:
  In Progress
Status in Kernel SRU Workflow prepare-package-signed series:
  In Progress
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow stakeholder-signoff series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-azure package in Ubuntu:
  Invalid
Status in linux-azure source package in 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 --
  kernel-stable-master-bug: 1842546
  packages:
lrm: linux-restricted-modules-azure
main: linux-azure
meta: linux-meta-azure
signed: linux-signed-azure
  phase: Packaging
  phase-changed: Tuesday, 10. September 2019 16:16 UTC
  reason:
prepare-package: Pending -- package not yet uploaded
prepare-package-lrm: Pending -- package not yet uploaded
prepare-package-meta: Pending -- package not yet uploaded
prepare-package-signed: Pending -- package not yet uploaded
  replaces: bug 1842545
  trackers:
bionic/linux-azure-edge: bug 1842833
bionic/linux-azure/azure-kernel: bug 1842832
  variant: debs

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

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

[Kernel-packages] [Bug 1842834] Re: bionic/linux-azure: 5.0.0-1019.20~18.04.1 -proposed tracker

[Sultan Alsawaf]

** Summary changed:

- bionic/linux-azure:  -proposed tracker
+ bionic/linux-azure: 5.0.0-1019.20~18.04.1 -proposed tracker

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

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

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

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

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

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

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

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

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

Title:
  bionic/linux-azure: 5.0.0-1019.20~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:
  In Progress
Status in Kernel SRU Workflow prepare-package-lrm series:
  In Progress
Status in Kernel SRU Workflow prepare-package-meta series:
  In Progress
Status in Kernel SRU Workflow prepare-package-signed series:
  In Progress
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow stakeholder-signoff series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-azure package in Ubuntu:
  Invalid
Status in linux-azure source package in 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 --
  kernel-stable-master-bug: 1842546
  packages:
lrm: linux-restricted-modules-azure
main: linux-azure
meta: linux-meta-azure
signed: linux-signed-azure
  phase: Packaging
  phase-changed: Tuesday, 10. September 2019 16:16 UTC
  reason:
prepare-package: Pending -- package not yet uploaded
prepare-package-lrm: Pending -- package not yet uploaded
prepare-package-meta: Pending -- package not yet uploaded
prepare-package-signed: Pending -- package not yet uploaded
  replaces: bug 1842545
  trackers:
bionic/linux-azure-edge: bug 1842833
bionic/linux-azure/azure-kernel: bug 1842832
  variant: debs

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

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

[Kernel-packages] [Bug 1842587] Re: xenial/linux-azure: 4.15.0-1057.62 -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: 1842828
  packages:
main: linux-azure
meta: linux-meta-azure
signed: linux-signed-azure
  phase: Ready for Testing
  phase-changed: Friday, 06. September 2019 05:48 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
regression-testing: Ongoing -- testing in progress
stakeholder-signoff: Stalled -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
-   trusty/linux-azure: bug 1842819, bug 1842585
+   trusty/linux-azure: bug 1842585, bug 1842819
xenial/linux-azure-edge: bug 1842584
xenial/linux-azure/azure-kernel: bug 1842583
  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/1842587

Title:
  xenial/linux-azure: 4.15.0-1057.62 -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:
  New
Status in Kernel SRU Workflow stakeholder-signoff series:
  Confirmed
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-azure package in Ubuntu:
  Invalid
Status in linux-azure source package in Xenial:
  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: 1842828
  packages:
main: linux-azure
meta: linux-meta-azure
signed: linux-signed-azure
  phase: Ready for Testing
  phase-changed: Friday, 06. September 2019 05:48 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
regression-testing: Ongoing -- testing in progress
stakeholder-signoff: Stalled -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
trusty/linux-azure: bug 1842585, bug 1842819
xenial/linux-azure-edge: bug 1842584
xenial/linux-azure/azure-kernel: bug 1842583
  variant: debs

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

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

[Kernel-packages] [Bug 1842608] Re: xenial/linux: 4.4.0-162.190 -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 --
  packages:
main: linux
meta: linux-meta
signed: linux-signed
  phase: Holding before Promote to Proposed
  phase-changed: Wednesday, 04. September 2019 07:52 UTC
  reason:
promote-to-proposed: Pending -- builds not complete in ppa 
main:failed,meta:depwait
  trackers:
trusty/linux-aws: bug 1842606, bug 1842793
-   trusty/linux-lts-xenial: bug 1842607, bug 1842794
+   trusty/linux-lts-xenial: bug 1842794, bug 1842607
xenial/linux-aws: bug 1842597
xenial/linux-fips: bug 1842605
xenial/linux-kvm: bug 1842598
xenial/linux-raspi2: bug 1842600
xenial/linux-snapdragon: bug 1842603
xenial/linux/pc-kernel: bug 1842595
  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/1842608

Title:
  xenial/linux: 4.4.0-162.190 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  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 --
  packages:
main: linux
meta: linux-meta
signed: linux-signed
  phase: Holding before Promote to Proposed
  phase-changed: Wednesday, 04. September 2019 07:52 UTC
  reason:
promote-to-proposed: Pending -- builds not complete in ppa 
main:failed,meta:depwait
  trackers:
trusty/linux-aws: bug 1842606, bug 1842793
trusty/linux-lts-xenial: bug 1842794, bug 1842607
xenial/linux-aws: bug 1842597
xenial/linux-fips: bug 1842605
xenial/linux-kvm: bug 1842598
xenial/linux-raspi2: bug 1842600
xenial/linux-snapdragon: bug 1842603
xenial/linux/pc-kernel: bug 1842595
  variant: debs

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

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

[Kernel-packages] [Bug 1842540] Re: disco/linux-raspi2: 5.0.0-1016.16 -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: 1842561
  packages:
main: linux-raspi2
meta: linux-meta-raspi2
  phase: Ready for Promote to Proposed
  phase-changed: Tuesday, 10. September 2019 03:35 UTC
  reason:
-   promote-to-proposed: Pending -- ready for review
+   promote-to-proposed: Stalled -- ready for review
  variant: debs

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

Title:
  disco/linux-raspi2: 5.0.0-1016.16 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Confirmed
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Invalid
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-raspi2 package in Ubuntu:
  Invalid
Status in linux-raspi2 source package in Disco:
  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: 1842561
  packages:
main: linux-raspi2
meta: linux-meta-raspi2
  phase: Ready for Promote to Proposed
  phase-changed: Tuesday, 10. September 2019 03:35 UTC
  reason:
promote-to-proposed: Stalled -- ready for review
  variant: debs

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

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

[Kernel-packages] [Bug 1830731] Re: [19.10 FEAT] Thin provisioning base support (kernel+390tools)

[Dimitri John Ledkov]

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

Title:
  [19.10 FEAT] Thin provisioning base support (kernel+390tools)

Status in Ubuntu on IBM z Systems:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete
Status in s390-tools package in Ubuntu:
  Incomplete

Bug description:
  Enable use of thin provisioned ECKD volumes.
  Efficient use of storage resources and reduced deployment time for ECKD 
volumes .

  Tentative Target is kernel 5.3 + s390tools
  Assumption from crystal balls
  merge window closes on Sunday, 2019-07-28 and release on Sunday, 2019-09-15

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

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

[Kernel-packages] [Bug 1842714] Re: bionic/linux-oem: 4.15.0-1054.63 -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: 1842746
  packages:
lrm: linux-restricted-modules-oem
main: linux-oem
meta: linux-meta-oem
signed: linux-signed-oem
  phase: Holding before Promote to Proposed
  phase-changed: Tuesday, 10. September 2019 13:12 UTC
  reason:
-   promote-to-proposed: Ongoing -- builds not complete in ppa 
lrm:depwait,main:building,meta:depwait,signed:depwait
+   promote-to-proposed: Ongoing -- builds not complete in ppa 
lrm:depwait,meta:depwait,signed:depwait
  replaces: bug 1842418
  variant: debs

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

Title:
  bionic/linux-oem: 4.15.0-1054.63 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-lrm series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-oem package in Ubuntu:
  Invalid
Status in linux-oem 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 --
  kernel-stable-master-bug: 1842746
  packages:
lrm: linux-restricted-modules-oem
main: linux-oem
meta: linux-meta-oem
signed: linux-signed-oem
  phase: Holding before Promote to Proposed
  phase-changed: Tuesday, 10. September 2019 13:12 UTC
  reason:
promote-to-proposed: Ongoing -- builds not complete in ppa 
lrm:depwait,meta:depwait,signed:depwait
  replaces: bug 1842418
  variant: debs

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

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

[Kernel-packages] [Bug 1843444] ProcModules.txt

[faleiros]

apport information

** Attachment added: "ProcModules.txt"
   
https://bugs.launchpad.net/bugs/1843444/+attachment/5287818/+files/ProcModules.txt

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

Title:
  Guests paused/crash during live-migration

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  after update my hosts (OpenStack Queens) to current packages (I'm
  using 18.04, kernel 4.15.0-62)  live-migration is intermittently
  failing pausing my vms with the following error (this problem doesn't
  occur before upgrade the hosts):

  KVM: entry failed, hardware error 0x8021

  If you're running a guest on an Intel machine without unrestricted mode
  support, the failure can be most likely due to the guest entering an invalid
  state for Intel VT. For example, the guest maybe running in big real mode
  which is not supported on less recent Intel processors.

  RAX=997bdc50 RBX=0003 RCX= 
RDX=
  RSI= RDI= RBP=b8d940387e78 
RSP=b8d940387e78
  R8 =0004 R9 =9dc43fd9d220 R10= 
R11=00cfc7d0f8fb
  R12=0003 R13=9dc43c8e8000 R14= 
R15=
  RIP=997bdfc2 RFL=00010246 [---Z-P-] CPL=0 II=0 A20=1 SMM=0 HLT=0
  ES =   
  CS =0010   00a09b00 DPL=0 CS64 [-RA]
  SS =0018   00c09300 DPL=0 DS   [-WA]
  DS =   
  FS =   
  GS = 9dc43fd8  
  LDT=  000f 
  TR =0040 fe087000 206f 8b00 DPL=0 TSS64-busy
  GDT= fe085000 007f
  IDT= fe00 0fff
  CR0=80050033 CR2= CR3=52e0a003 CR4=00760ee0
  DR0= DR1= DR2= 
DR3= 
  DR6=fffe0ff0 DR7=0400
  EFER=0d01
  Code=90 90 55 48 89 e5 e9 07 00 00 00 0f 00 2d f0 bc 44 00 fb f4 <5d> c3 66 
90 66 2e 0f 1f 84 00 00 00 00 00 55 48 89 e5 e9 07 00 00 00 0f 00 2d d0 bc 44 00
  KVM: entry failed, hardware error 0x8021

  If you're running a guest on an Intel machine without unrestricted mode
  support, the failure can be most likely due to the guest entering an invalid
  state for Intel VT. For example, the guest maybe running in big real mode
  which is not supported on less recent Intel processors.

  RAX=997bdc50 RBX=0002 RCX= 
RDX=
  RSI= RDI= RBP=b8d94037fe78 
RSP=b8d94037fe78
  R8 =0004 R9 =9dc43fd1d220 R10= 
R11=00cfcef806fb
  R12=0002 R13=9dc43c8ebb80 R14= 
R15=
  RIP=997bdfc2 RFL=00010246 [---Z-P-] CPL=0 II=0 A20=1 SMM=0 HLT=0
  ES =   
  CS =0010   00a09b00 DPL=0 CS64 [-RA]
  SS =0018   00c09300 DPL=0 DS   [-WA]
  DS =   
  FS =   
  GS = 9dc43fd0  
  LDT=   
  TR =0040 fe05b000 206f 8b00 DPL=0 TSS64-busy
  GDT= fe059000 007f
  IDT= fe00 0fff
  CR0=80050033 CR2= CR3=52e0a003 CR4=00760ee0
  DR0= DR1= DR2= 
DR3= 
  DR6=fffe0ff0 DR7=0400
  EFER=0d01
  Code=90 90 55 48 89 e5 e9 07 00 00 00 0f 00 2d f0 bc 44 00 fb f4 <5d> c3 66 
90 66 2e 0f 1f 84 00 00 00 00 00 55 48 89 e5 e9 07 00 00 00 0f 00 2d d0 bc 44 00
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0K
   crw-rw 1 root audio 116,  1 Sep  9 13:56 seq
   crw-rw 1 root audio 116, 33 Sep  9 13:56 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  DistroRelease: Ubuntu 18.04
  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 004: ID 1604:10c0 Tascam 
   Bus 001 Device 003: ID 1604:10c0 Tascam 
   Bus 001 Device 002: ID 1604:10c0 Tascam 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. PowerEdge R640
  Package: linux (not installed)
  PciMultimedia:
 

[Kernel-packages] [Bug 1843444] WifiSyslog.txt

[faleiros]

apport information

** Attachment added: "WifiSyslog.txt"
   
https://bugs.launchpad.net/bugs/1843444/+attachment/5287820/+files/WifiSyslog.txt

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

Title:
  Guests paused/crash during live-migration

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  after update my hosts (OpenStack Queens) to current packages (I'm
  using 18.04, kernel 4.15.0-62)  live-migration is intermittently
  failing pausing my vms with the following error (this problem doesn't
  occur before upgrade the hosts):

  KVM: entry failed, hardware error 0x8021

  If you're running a guest on an Intel machine without unrestricted mode
  support, the failure can be most likely due to the guest entering an invalid
  state for Intel VT. For example, the guest maybe running in big real mode
  which is not supported on less recent Intel processors.

  RAX=997bdc50 RBX=0003 RCX= 
RDX=
  RSI= RDI= RBP=b8d940387e78 
RSP=b8d940387e78
  R8 =0004 R9 =9dc43fd9d220 R10= 
R11=00cfc7d0f8fb
  R12=0003 R13=9dc43c8e8000 R14= 
R15=
  RIP=997bdfc2 RFL=00010246 [---Z-P-] CPL=0 II=0 A20=1 SMM=0 HLT=0
  ES =   
  CS =0010   00a09b00 DPL=0 CS64 [-RA]
  SS =0018   00c09300 DPL=0 DS   [-WA]
  DS =   
  FS =   
  GS = 9dc43fd8  
  LDT=  000f 
  TR =0040 fe087000 206f 8b00 DPL=0 TSS64-busy
  GDT= fe085000 007f
  IDT= fe00 0fff
  CR0=80050033 CR2= CR3=52e0a003 CR4=00760ee0
  DR0= DR1= DR2= 
DR3= 
  DR6=fffe0ff0 DR7=0400
  EFER=0d01
  Code=90 90 55 48 89 e5 e9 07 00 00 00 0f 00 2d f0 bc 44 00 fb f4 <5d> c3 66 
90 66 2e 0f 1f 84 00 00 00 00 00 55 48 89 e5 e9 07 00 00 00 0f 00 2d d0 bc 44 00
  KVM: entry failed, hardware error 0x8021

  If you're running a guest on an Intel machine without unrestricted mode
  support, the failure can be most likely due to the guest entering an invalid
  state for Intel VT. For example, the guest maybe running in big real mode
  which is not supported on less recent Intel processors.

  RAX=997bdc50 RBX=0002 RCX= 
RDX=
  RSI= RDI= RBP=b8d94037fe78 
RSP=b8d94037fe78
  R8 =0004 R9 =9dc43fd1d220 R10= 
R11=00cfcef806fb
  R12=0002 R13=9dc43c8ebb80 R14= 
R15=
  RIP=997bdfc2 RFL=00010246 [---Z-P-] CPL=0 II=0 A20=1 SMM=0 HLT=0
  ES =   
  CS =0010   00a09b00 DPL=0 CS64 [-RA]
  SS =0018   00c09300 DPL=0 DS   [-WA]
  DS =   
  FS =   
  GS = 9dc43fd0  
  LDT=   
  TR =0040 fe05b000 206f 8b00 DPL=0 TSS64-busy
  GDT= fe059000 007f
  IDT= fe00 0fff
  CR0=80050033 CR2= CR3=52e0a003 CR4=00760ee0
  DR0= DR1= DR2= 
DR3= 
  DR6=fffe0ff0 DR7=0400
  EFER=0d01
  Code=90 90 55 48 89 e5 e9 07 00 00 00 0f 00 2d f0 bc 44 00 fb f4 <5d> c3 66 
90 66 2e 0f 1f 84 00 00 00 00 00 55 48 89 e5 e9 07 00 00 00 0f 00 2d d0 bc 44 00
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0K
   crw-rw 1 root audio 116,  1 Sep  9 13:56 seq
   crw-rw 1 root audio 116, 33 Sep  9 13:56 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  DistroRelease: Ubuntu 18.04
  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 004: ID 1604:10c0 Tascam 
   Bus 001 Device 003: ID 1604:10c0 Tascam 
   Bus 001 Device 002: ID 1604:10c0 Tascam 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell 

[Kernel-packages] [Bug 1843444] ProcInterrupts.txt

[faleiros]

apport information

** Attachment added: "ProcInterrupts.txt"
   
https://bugs.launchpad.net/bugs/1843444/+attachment/5287817/+files/ProcInterrupts.txt

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

Title:
  Guests paused/crash during live-migration

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  after update my hosts (OpenStack Queens) to current packages (I'm
  using 18.04, kernel 4.15.0-62)  live-migration is intermittently
  failing pausing my vms with the following error (this problem doesn't
  occur before upgrade the hosts):

  KVM: entry failed, hardware error 0x8021

  If you're running a guest on an Intel machine without unrestricted mode
  support, the failure can be most likely due to the guest entering an invalid
  state for Intel VT. For example, the guest maybe running in big real mode
  which is not supported on less recent Intel processors.

  RAX=997bdc50 RBX=0003 RCX= 
RDX=
  RSI= RDI= RBP=b8d940387e78 
RSP=b8d940387e78
  R8 =0004 R9 =9dc43fd9d220 R10= 
R11=00cfc7d0f8fb
  R12=0003 R13=9dc43c8e8000 R14= 
R15=
  RIP=997bdfc2 RFL=00010246 [---Z-P-] CPL=0 II=0 A20=1 SMM=0 HLT=0
  ES =   
  CS =0010   00a09b00 DPL=0 CS64 [-RA]
  SS =0018   00c09300 DPL=0 DS   [-WA]
  DS =   
  FS =   
  GS = 9dc43fd8  
  LDT=  000f 
  TR =0040 fe087000 206f 8b00 DPL=0 TSS64-busy
  GDT= fe085000 007f
  IDT= fe00 0fff
  CR0=80050033 CR2= CR3=52e0a003 CR4=00760ee0
  DR0= DR1= DR2= 
DR3= 
  DR6=fffe0ff0 DR7=0400
  EFER=0d01
  Code=90 90 55 48 89 e5 e9 07 00 00 00 0f 00 2d f0 bc 44 00 fb f4 <5d> c3 66 
90 66 2e 0f 1f 84 00 00 00 00 00 55 48 89 e5 e9 07 00 00 00 0f 00 2d d0 bc 44 00
  KVM: entry failed, hardware error 0x8021

  If you're running a guest on an Intel machine without unrestricted mode
  support, the failure can be most likely due to the guest entering an invalid
  state for Intel VT. For example, the guest maybe running in big real mode
  which is not supported on less recent Intel processors.

  RAX=997bdc50 RBX=0002 RCX= 
RDX=
  RSI= RDI= RBP=b8d94037fe78 
RSP=b8d94037fe78
  R8 =0004 R9 =9dc43fd1d220 R10= 
R11=00cfcef806fb
  R12=0002 R13=9dc43c8ebb80 R14= 
R15=
  RIP=997bdfc2 RFL=00010246 [---Z-P-] CPL=0 II=0 A20=1 SMM=0 HLT=0
  ES =   
  CS =0010   00a09b00 DPL=0 CS64 [-RA]
  SS =0018   00c09300 DPL=0 DS   [-WA]
  DS =   
  FS =   
  GS = 9dc43fd0  
  LDT=   
  TR =0040 fe05b000 206f 8b00 DPL=0 TSS64-busy
  GDT= fe059000 007f
  IDT= fe00 0fff
  CR0=80050033 CR2= CR3=52e0a003 CR4=00760ee0
  DR0= DR1= DR2= 
DR3= 
  DR6=fffe0ff0 DR7=0400
  EFER=0d01
  Code=90 90 55 48 89 e5 e9 07 00 00 00 0f 00 2d f0 bc 44 00 fb f4 <5d> c3 66 
90 66 2e 0f 1f 84 00 00 00 00 00 55 48 89 e5 e9 07 00 00 00 0f 00 2d d0 bc 44 00
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0K
   crw-rw 1 root audio 116,  1 Sep  9 13:56 seq
   crw-rw 1 root audio 116, 33 Sep  9 13:56 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  DistroRelease: Ubuntu 18.04
  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 004: ID 1604:10c0 Tascam 
   Bus 001 Device 003: ID 1604:10c0 Tascam 
   Bus 001 Device 002: ID 1604:10c0 Tascam 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. PowerEdge R640
  Package: linux (not installed)
  

[Kernel-packages] [Bug 1843444] Lspci.txt

[faleiros]

apport information

** Attachment added: "Lspci.txt"
   https://bugs.launchpad.net/bugs/1843444/+attachment/5287814/+files/Lspci.txt

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

Title:
  Guests paused/crash during live-migration

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  after update my hosts (OpenStack Queens) to current packages (I'm
  using 18.04, kernel 4.15.0-62)  live-migration is intermittently
  failing pausing my vms with the following error (this problem doesn't
  occur before upgrade the hosts):

  KVM: entry failed, hardware error 0x8021

  If you're running a guest on an Intel machine without unrestricted mode
  support, the failure can be most likely due to the guest entering an invalid
  state for Intel VT. For example, the guest maybe running in big real mode
  which is not supported on less recent Intel processors.

  RAX=997bdc50 RBX=0003 RCX= 
RDX=
  RSI= RDI= RBP=b8d940387e78 
RSP=b8d940387e78
  R8 =0004 R9 =9dc43fd9d220 R10= 
R11=00cfc7d0f8fb
  R12=0003 R13=9dc43c8e8000 R14= 
R15=
  RIP=997bdfc2 RFL=00010246 [---Z-P-] CPL=0 II=0 A20=1 SMM=0 HLT=0
  ES =   
  CS =0010   00a09b00 DPL=0 CS64 [-RA]
  SS =0018   00c09300 DPL=0 DS   [-WA]
  DS =   
  FS =   
  GS = 9dc43fd8  
  LDT=  000f 
  TR =0040 fe087000 206f 8b00 DPL=0 TSS64-busy
  GDT= fe085000 007f
  IDT= fe00 0fff
  CR0=80050033 CR2= CR3=52e0a003 CR4=00760ee0
  DR0= DR1= DR2= 
DR3= 
  DR6=fffe0ff0 DR7=0400
  EFER=0d01
  Code=90 90 55 48 89 e5 e9 07 00 00 00 0f 00 2d f0 bc 44 00 fb f4 <5d> c3 66 
90 66 2e 0f 1f 84 00 00 00 00 00 55 48 89 e5 e9 07 00 00 00 0f 00 2d d0 bc 44 00
  KVM: entry failed, hardware error 0x8021

  If you're running a guest on an Intel machine without unrestricted mode
  support, the failure can be most likely due to the guest entering an invalid
  state for Intel VT. For example, the guest maybe running in big real mode
  which is not supported on less recent Intel processors.

  RAX=997bdc50 RBX=0002 RCX= 
RDX=
  RSI= RDI= RBP=b8d94037fe78 
RSP=b8d94037fe78
  R8 =0004 R9 =9dc43fd1d220 R10= 
R11=00cfcef806fb
  R12=0002 R13=9dc43c8ebb80 R14= 
R15=
  RIP=997bdfc2 RFL=00010246 [---Z-P-] CPL=0 II=0 A20=1 SMM=0 HLT=0
  ES =   
  CS =0010   00a09b00 DPL=0 CS64 [-RA]
  SS =0018   00c09300 DPL=0 DS   [-WA]
  DS =   
  FS =   
  GS = 9dc43fd0  
  LDT=   
  TR =0040 fe05b000 206f 8b00 DPL=0 TSS64-busy
  GDT= fe059000 007f
  IDT= fe00 0fff
  CR0=80050033 CR2= CR3=52e0a003 CR4=00760ee0
  DR0= DR1= DR2= 
DR3= 
  DR6=fffe0ff0 DR7=0400
  EFER=0d01
  Code=90 90 55 48 89 e5 e9 07 00 00 00 0f 00 2d f0 bc 44 00 fb f4 <5d> c3 66 
90 66 2e 0f 1f 84 00 00 00 00 00 55 48 89 e5 e9 07 00 00 00 0f 00 2d d0 bc 44 00
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0K
   crw-rw 1 root audio 116,  1 Sep  9 13:56 seq
   crw-rw 1 root audio 116, 33 Sep  9 13:56 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  DistroRelease: Ubuntu 18.04
  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 004: ID 1604:10c0 Tascam 
   Bus 001 Device 003: ID 1604:10c0 Tascam 
   Bus 001 Device 002: ID 1604:10c0 Tascam 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. PowerEdge R640
  Package: linux (not installed)
  PciMultimedia:
   
  

[Kernel-packages] [Bug 1843444] UdevDb.txt

[faleiros]

apport information

** Attachment added: "UdevDb.txt"
   https://bugs.launchpad.net/bugs/1843444/+attachment/5287819/+files/UdevDb.txt

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

Title:
  Guests paused/crash during live-migration

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  after update my hosts (OpenStack Queens) to current packages (I'm
  using 18.04, kernel 4.15.0-62)  live-migration is intermittently
  failing pausing my vms with the following error (this problem doesn't
  occur before upgrade the hosts):

  KVM: entry failed, hardware error 0x8021

  If you're running a guest on an Intel machine without unrestricted mode
  support, the failure can be most likely due to the guest entering an invalid
  state for Intel VT. For example, the guest maybe running in big real mode
  which is not supported on less recent Intel processors.

  RAX=997bdc50 RBX=0003 RCX= 
RDX=
  RSI= RDI= RBP=b8d940387e78 
RSP=b8d940387e78
  R8 =0004 R9 =9dc43fd9d220 R10= 
R11=00cfc7d0f8fb
  R12=0003 R13=9dc43c8e8000 R14= 
R15=
  RIP=997bdfc2 RFL=00010246 [---Z-P-] CPL=0 II=0 A20=1 SMM=0 HLT=0
  ES =   
  CS =0010   00a09b00 DPL=0 CS64 [-RA]
  SS =0018   00c09300 DPL=0 DS   [-WA]
  DS =   
  FS =   
  GS = 9dc43fd8  
  LDT=  000f 
  TR =0040 fe087000 206f 8b00 DPL=0 TSS64-busy
  GDT= fe085000 007f
  IDT= fe00 0fff
  CR0=80050033 CR2= CR3=52e0a003 CR4=00760ee0
  DR0= DR1= DR2= 
DR3= 
  DR6=fffe0ff0 DR7=0400
  EFER=0d01
  Code=90 90 55 48 89 e5 e9 07 00 00 00 0f 00 2d f0 bc 44 00 fb f4 <5d> c3 66 
90 66 2e 0f 1f 84 00 00 00 00 00 55 48 89 e5 e9 07 00 00 00 0f 00 2d d0 bc 44 00
  KVM: entry failed, hardware error 0x8021

  If you're running a guest on an Intel machine without unrestricted mode
  support, the failure can be most likely due to the guest entering an invalid
  state for Intel VT. For example, the guest maybe running in big real mode
  which is not supported on less recent Intel processors.

  RAX=997bdc50 RBX=0002 RCX= 
RDX=
  RSI= RDI= RBP=b8d94037fe78 
RSP=b8d94037fe78
  R8 =0004 R9 =9dc43fd1d220 R10= 
R11=00cfcef806fb
  R12=0002 R13=9dc43c8ebb80 R14= 
R15=
  RIP=997bdfc2 RFL=00010246 [---Z-P-] CPL=0 II=0 A20=1 SMM=0 HLT=0
  ES =   
  CS =0010   00a09b00 DPL=0 CS64 [-RA]
  SS =0018   00c09300 DPL=0 DS   [-WA]
  DS =   
  FS =   
  GS = 9dc43fd0  
  LDT=   
  TR =0040 fe05b000 206f 8b00 DPL=0 TSS64-busy
  GDT= fe059000 007f
  IDT= fe00 0fff
  CR0=80050033 CR2= CR3=52e0a003 CR4=00760ee0
  DR0= DR1= DR2= 
DR3= 
  DR6=fffe0ff0 DR7=0400
  EFER=0d01
  Code=90 90 55 48 89 e5 e9 07 00 00 00 0f 00 2d f0 bc 44 00 fb f4 <5d> c3 66 
90 66 2e 0f 1f 84 00 00 00 00 00 55 48 89 e5 e9 07 00 00 00 0f 00 2d d0 bc 44 00
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0K
   crw-rw 1 root audio 116,  1 Sep  9 13:56 seq
   crw-rw 1 root audio 116, 33 Sep  9 13:56 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  DistroRelease: Ubuntu 18.04
  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 004: ID 1604:10c0 Tascam 
   Bus 001 Device 003: ID 1604:10c0 Tascam 
   Bus 001 Device 002: ID 1604:10c0 Tascam 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. PowerEdge R640
  Package: linux (not installed)
  PciMultimedia:
   
  

[Kernel-packages] [Bug 1843444] ProcCpuinfoMinimal.txt

[faleiros]

apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1843444/+attachment/5287816/+files/ProcCpuinfoMinimal.txt

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

Title:
  Guests paused/crash during live-migration

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  after update my hosts (OpenStack Queens) to current packages (I'm
  using 18.04, kernel 4.15.0-62)  live-migration is intermittently
  failing pausing my vms with the following error (this problem doesn't
  occur before upgrade the hosts):

  KVM: entry failed, hardware error 0x8021

  If you're running a guest on an Intel machine without unrestricted mode
  support, the failure can be most likely due to the guest entering an invalid
  state for Intel VT. For example, the guest maybe running in big real mode
  which is not supported on less recent Intel processors.

  RAX=997bdc50 RBX=0003 RCX= 
RDX=
  RSI= RDI= RBP=b8d940387e78 
RSP=b8d940387e78
  R8 =0004 R9 =9dc43fd9d220 R10= 
R11=00cfc7d0f8fb
  R12=0003 R13=9dc43c8e8000 R14= 
R15=
  RIP=997bdfc2 RFL=00010246 [---Z-P-] CPL=0 II=0 A20=1 SMM=0 HLT=0
  ES =   
  CS =0010   00a09b00 DPL=0 CS64 [-RA]
  SS =0018   00c09300 DPL=0 DS   [-WA]
  DS =   
  FS =   
  GS = 9dc43fd8  
  LDT=  000f 
  TR =0040 fe087000 206f 8b00 DPL=0 TSS64-busy
  GDT= fe085000 007f
  IDT= fe00 0fff
  CR0=80050033 CR2= CR3=52e0a003 CR4=00760ee0
  DR0= DR1= DR2= 
DR3= 
  DR6=fffe0ff0 DR7=0400
  EFER=0d01
  Code=90 90 55 48 89 e5 e9 07 00 00 00 0f 00 2d f0 bc 44 00 fb f4 <5d> c3 66 
90 66 2e 0f 1f 84 00 00 00 00 00 55 48 89 e5 e9 07 00 00 00 0f 00 2d d0 bc 44 00
  KVM: entry failed, hardware error 0x8021

  If you're running a guest on an Intel machine without unrestricted mode
  support, the failure can be most likely due to the guest entering an invalid
  state for Intel VT. For example, the guest maybe running in big real mode
  which is not supported on less recent Intel processors.

  RAX=997bdc50 RBX=0002 RCX= 
RDX=
  RSI= RDI= RBP=b8d94037fe78 
RSP=b8d94037fe78
  R8 =0004 R9 =9dc43fd1d220 R10= 
R11=00cfcef806fb
  R12=0002 R13=9dc43c8ebb80 R14= 
R15=
  RIP=997bdfc2 RFL=00010246 [---Z-P-] CPL=0 II=0 A20=1 SMM=0 HLT=0
  ES =   
  CS =0010   00a09b00 DPL=0 CS64 [-RA]
  SS =0018   00c09300 DPL=0 DS   [-WA]
  DS =   
  FS =   
  GS = 9dc43fd0  
  LDT=   
  TR =0040 fe05b000 206f 8b00 DPL=0 TSS64-busy
  GDT= fe059000 007f
  IDT= fe00 0fff
  CR0=80050033 CR2= CR3=52e0a003 CR4=00760ee0
  DR0= DR1= DR2= 
DR3= 
  DR6=fffe0ff0 DR7=0400
  EFER=0d01
  Code=90 90 55 48 89 e5 e9 07 00 00 00 0f 00 2d f0 bc 44 00 fb f4 <5d> c3 66 
90 66 2e 0f 1f 84 00 00 00 00 00 55 48 89 e5 e9 07 00 00 00 0f 00 2d d0 bc 44 00
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0K
   crw-rw 1 root audio 116,  1 Sep  9 13:56 seq
   crw-rw 1 root audio 116, 33 Sep  9 13:56 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  DistroRelease: Ubuntu 18.04
  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 004: ID 1604:10c0 Tascam 
   Bus 001 Device 003: ID 1604:10c0 Tascam 
   Bus 001 Device 002: ID 1604:10c0 Tascam 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. PowerEdge R640
  Package: linux (not installed)
  

[Kernel-packages] [Bug 1843444] ProcCpuinfo.txt

[faleiros]

apport information

** Attachment added: "ProcCpuinfo.txt"
   
https://bugs.launchpad.net/bugs/1843444/+attachment/5287815/+files/ProcCpuinfo.txt

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

Title:
  Guests paused/crash during live-migration

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  after update my hosts (OpenStack Queens) to current packages (I'm
  using 18.04, kernel 4.15.0-62)  live-migration is intermittently
  failing pausing my vms with the following error (this problem doesn't
  occur before upgrade the hosts):

  KVM: entry failed, hardware error 0x8021

  If you're running a guest on an Intel machine without unrestricted mode
  support, the failure can be most likely due to the guest entering an invalid
  state for Intel VT. For example, the guest maybe running in big real mode
  which is not supported on less recent Intel processors.

  RAX=997bdc50 RBX=0003 RCX= 
RDX=
  RSI= RDI= RBP=b8d940387e78 
RSP=b8d940387e78
  R8 =0004 R9 =9dc43fd9d220 R10= 
R11=00cfc7d0f8fb
  R12=0003 R13=9dc43c8e8000 R14= 
R15=
  RIP=997bdfc2 RFL=00010246 [---Z-P-] CPL=0 II=0 A20=1 SMM=0 HLT=0
  ES =   
  CS =0010   00a09b00 DPL=0 CS64 [-RA]
  SS =0018   00c09300 DPL=0 DS   [-WA]
  DS =   
  FS =   
  GS = 9dc43fd8  
  LDT=  000f 
  TR =0040 fe087000 206f 8b00 DPL=0 TSS64-busy
  GDT= fe085000 007f
  IDT= fe00 0fff
  CR0=80050033 CR2= CR3=52e0a003 CR4=00760ee0
  DR0= DR1= DR2= 
DR3= 
  DR6=fffe0ff0 DR7=0400
  EFER=0d01
  Code=90 90 55 48 89 e5 e9 07 00 00 00 0f 00 2d f0 bc 44 00 fb f4 <5d> c3 66 
90 66 2e 0f 1f 84 00 00 00 00 00 55 48 89 e5 e9 07 00 00 00 0f 00 2d d0 bc 44 00
  KVM: entry failed, hardware error 0x8021

  If you're running a guest on an Intel machine without unrestricted mode
  support, the failure can be most likely due to the guest entering an invalid
  state for Intel VT. For example, the guest maybe running in big real mode
  which is not supported on less recent Intel processors.

  RAX=997bdc50 RBX=0002 RCX= 
RDX=
  RSI= RDI= RBP=b8d94037fe78 
RSP=b8d94037fe78
  R8 =0004 R9 =9dc43fd1d220 R10= 
R11=00cfcef806fb
  R12=0002 R13=9dc43c8ebb80 R14= 
R15=
  RIP=997bdfc2 RFL=00010246 [---Z-P-] CPL=0 II=0 A20=1 SMM=0 HLT=0
  ES =   
  CS =0010   00a09b00 DPL=0 CS64 [-RA]
  SS =0018   00c09300 DPL=0 DS   [-WA]
  DS =   
  FS =   
  GS = 9dc43fd0  
  LDT=   
  TR =0040 fe05b000 206f 8b00 DPL=0 TSS64-busy
  GDT= fe059000 007f
  IDT= fe00 0fff
  CR0=80050033 CR2= CR3=52e0a003 CR4=00760ee0
  DR0= DR1= DR2= 
DR3= 
  DR6=fffe0ff0 DR7=0400
  EFER=0d01
  Code=90 90 55 48 89 e5 e9 07 00 00 00 0f 00 2d f0 bc 44 00 fb f4 <5d> c3 66 
90 66 2e 0f 1f 84 00 00 00 00 00 55 48 89 e5 e9 07 00 00 00 0f 00 2d d0 bc 44 00
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0K
   crw-rw 1 root audio 116,  1 Sep  9 13:56 seq
   crw-rw 1 root audio 116, 33 Sep  9 13:56 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  DistroRelease: Ubuntu 18.04
  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 004: ID 1604:10c0 Tascam 
   Bus 001 Device 003: ID 1604:10c0 Tascam 
   Bus 001 Device 002: ID 1604:10c0 Tascam 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. PowerEdge R640
  Package: linux (not installed)
  PciMultimedia:
 

[Kernel-packages] [Bug 1843444] Re: Guests paused/crash during live-migration

[faleiros]

apport information

** Tags added: apport-collected bionic

** Description changed:

  after update my hosts (OpenStack Queens) to current packages (I'm using
  18.04, kernel 4.15.0-62)  live-migration is intermittently failing
  pausing my vms with the following error (this problem doesn't occur
  before upgrade the hosts):
  
  KVM: entry failed, hardware error 0x8021
  
  If you're running a guest on an Intel machine without unrestricted mode
  support, the failure can be most likely due to the guest entering an invalid
  state for Intel VT. For example, the guest maybe running in big real mode
  which is not supported on less recent Intel processors.
  
  RAX=997bdc50 RBX=0003 RCX= 
RDX=
  RSI= RDI= RBP=b8d940387e78 
RSP=b8d940387e78
  R8 =0004 R9 =9dc43fd9d220 R10= 
R11=00cfc7d0f8fb
  R12=0003 R13=9dc43c8e8000 R14= 
R15=
  RIP=997bdfc2 RFL=00010246 [---Z-P-] CPL=0 II=0 A20=1 SMM=0 HLT=0
  ES =   
  CS =0010   00a09b00 DPL=0 CS64 [-RA]
  SS =0018   00c09300 DPL=0 DS   [-WA]
  DS =   
  FS =   
  GS = 9dc43fd8  
  LDT=  000f 
  TR =0040 fe087000 206f 8b00 DPL=0 TSS64-busy
  GDT= fe085000 007f
  IDT= fe00 0fff
  CR0=80050033 CR2= CR3=52e0a003 CR4=00760ee0
  DR0= DR1= DR2= 
DR3= 
  DR6=fffe0ff0 DR7=0400
  EFER=0d01
  Code=90 90 55 48 89 e5 e9 07 00 00 00 0f 00 2d f0 bc 44 00 fb f4 <5d> c3 66 
90 66 2e 0f 1f 84 00 00 00 00 00 55 48 89 e5 e9 07 00 00 00 0f 00 2d d0 bc 44 00
  KVM: entry failed, hardware error 0x8021
  
  If you're running a guest on an Intel machine without unrestricted mode
  support, the failure can be most likely due to the guest entering an invalid
  state for Intel VT. For example, the guest maybe running in big real mode
  which is not supported on less recent Intel processors.
  
  RAX=997bdc50 RBX=0002 RCX= 
RDX=
  RSI= RDI= RBP=b8d94037fe78 
RSP=b8d94037fe78
  R8 =0004 R9 =9dc43fd1d220 R10= 
R11=00cfcef806fb
  R12=0002 R13=9dc43c8ebb80 R14= 
R15=
  RIP=997bdfc2 RFL=00010246 [---Z-P-] CPL=0 II=0 A20=1 SMM=0 HLT=0
  ES =   
  CS =0010   00a09b00 DPL=0 CS64 [-RA]
  SS =0018   00c09300 DPL=0 DS   [-WA]
  DS =   
  FS =   
  GS = 9dc43fd0  
  LDT=   
  TR =0040 fe05b000 206f 8b00 DPL=0 TSS64-busy
  GDT= fe059000 007f
  IDT= fe00 0fff
  CR0=80050033 CR2= CR3=52e0a003 CR4=00760ee0
  DR0= DR1= DR2= 
DR3= 
  DR6=fffe0ff0 DR7=0400
  EFER=0d01
  Code=90 90 55 48 89 e5 e9 07 00 00 00 0f 00 2d f0 bc 44 00 fb f4 <5d> c3 66 
90 66 2e 0f 1f 84 00 00 00 00 00 55 48 89 e5 e9 07 00 00 00 0f 00 2d d0 bc 44 00
+ --- 
+ ProblemType: Bug
+ AlsaDevices:
+  total 0K
+  crw-rw 1 root audio 116,  1 Sep  9 13:56 seq
+  crw-rw 1 root audio 116, 33 Sep  9 13:56 timer
+ AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
+ ApportVersion: 2.20.9-0ubuntu7.7
+ Architecture: amd64
+ ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
+ AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
+ CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
+ DistroRelease: Ubuntu 18.04
+ 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 004: ID 1604:10c0 Tascam 
+  Bus 001 Device 003: ID 1604:10c0 Tascam 
+  Bus 001 Device 002: ID 1604:10c0 Tascam 
+  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
+ MachineType: Dell Inc. PowerEdge R640
+ Package: linux (not installed)
+ PciMultimedia:
+  
+ ProcEnviron:
+  LC_TIME=en_US.UTF-8
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  LANG=en_US.UTF-8
+  SHELL=/bin/csh
+ ProcFB: 0 EFI VGA
+ ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-58-generic 
root=UUID=931f084f-0c66-44fc-b270-8f8f4357aa3c ro apparmor=1 security=apparmor
+ ProcVersionSignature: Ubuntu 

[Kernel-packages] [Bug 1842965] Re: Unable to boot kernel 4.15 on MacPro5, 1 (mid 2012)

[Scott Talbert]

OK, so I bisected the kernel versions by using the mainline builds.  The
first kernel where this breaks is v4.8-rc1 (v4.7.x works fine).

I think did a git bisection and found that this commit is the bad one:
27b79027bc112a63ad4004eb83c6acacae08a0de

This seems a bit strange to me, though, as this is a merge commit and
both of the two parent commits work.  Investigating further.

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

Title:
  Unable to boot kernel 4.15 on MacPro5,1 (mid 2012)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  System: Mac Pro 5,1 (mid-2012).

  I'm unable to boot the Ubuntu 18.04 installer ISO on this system (tried both 
18.04.0 and 18.04.3).  I was able to boot the 16.04.1 ISO (but NOT 16.04.6) and 
installed 16.04 successfully.  Then, I upgraded to 18.04.  However, when trying 
to boot the new kernel (4.15.0-60), it just locks up at the purple screen.  
Booting back to 4.4.0-161 works.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  stalbert   2072 F pulseaudio
   /dev/snd/controlC1:  stalbert   2072 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=9c6c2f5f-9303-4f65-955d-30f5db341801
  InstallationDate: Installed on 2019-09-05 (0 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  IwConfig:
   enp10s0   no wireless extensions.
   
   lono wireless extensions.
   
   enp9s0no wireless extensions.
  MachineType: Apple Inc. MacPro5,1
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-161-generic 
root=UUID=c7c8d4ce-3f44-41cd-8ce0-2e835c8d5547 ro quiet splash
  ProcVersionSignature: Ubuntu 4.4.0-161.189-generic 4.4.186
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-161-generic N/A
   linux-backports-modules-4.4.0-161-generic  N/A
   linux-firmware 1.173.9
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  Tags:  bionic
  Uname: Linux 4.4.0-161-generic x86_64
  UpgradeStatus: Upgraded to bionic on 2019-09-05 (0 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/08/17
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MP51.88Z.0084.B00.1708080528
  dmi.board.asset.tag: 0
  dmi.board.name: Mac-F221BEC8
  dmi.board.vendor: Apple Inc.
  dmi.chassis.type: 7
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-F221BEC8
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMP51.88Z.0084.B00.1708080528:bd08/08/17:svnAppleInc.:pnMacPro5,1:pvr0.0:rvnAppleInc.:rnMac-F221BEC8:rvr:cvnAppleInc.:ct7:cvrMac-F221BEC8:
  dmi.product.name: MacPro5,1
  dmi.product.version: 0.0
  dmi.sys.vendor: Apple Inc.

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

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

[Kernel-packages] [Bug 1842597] Re: xenial/linux-aws: 4.4.0-1093.104 -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: 1842608
  packages:
main: linux-aws
meta: linux-meta-aws
- phase: Ready for Packaging
- phase-changed: Friday, 06. September 2019 05:33 UTC
+ phase: Packaging
+ phase-changed: Tuesday, 10. September 2019 14:40 UTC
  reason:
-   prepare-package: Pending -- version not specified
+   prepare-package: Pending -- package not yet uploaded
+   prepare-package-meta: Pending -- package not yet uploaded
  trackers:
xenial/linux-aws/aws-kernel: bug 1842596
  variant: debs

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

Title:
  xenial/linux-aws: 4.4.0-1093.104 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  In Progress
Status in Kernel SRU Workflow prepare-package-meta series:
  In Progress
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-aws package in Ubuntu:
  Invalid
Status in linux-aws source package in Xenial:
  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 --
  kernel-stable-master-bug: 1842608
  packages:
main: linux-aws
meta: linux-meta-aws
  phase: Packaging
  phase-changed: Tuesday, 10. September 2019 14:40 UTC
  reason:
prepare-package: Pending -- package not yet uploaded
prepare-package-meta: Pending -- package not yet uploaded
  trackers:
xenial/linux-aws/aws-kernel: bug 1842596
  variant: debs

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

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

[Kernel-packages] [Bug 1842597] Re: xenial/linux-aws: 4.4.0-1093.104 -proposed tracker

[Paolo Pisati]

** Summary changed:

- xenial/linux-aws:  -proposed tracker
+ xenial/linux-aws: 4.4.0-1093.104 -proposed tracker

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

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

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

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

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

Title:
  xenial/linux-aws: 4.4.0-1093.104 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  In Progress
Status in Kernel SRU Workflow prepare-package-meta series:
  In Progress
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-aws package in Ubuntu:
  Invalid
Status in linux-aws source package in Xenial:
  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 --
  kernel-stable-master-bug: 1842608
  packages:
main: linux-aws
meta: linux-meta-aws
  phase: Packaging
  phase-changed: Tuesday, 10. September 2019 14:40 UTC
  reason:
prepare-package: Pending -- package not yet uploaded
prepare-package-meta: Pending -- package not yet uploaded
  trackers:
xenial/linux-aws/aws-kernel: bug 1842596
  variant: debs

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

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

[Kernel-packages] [Bug 1843232] Re: eoan/linux: 5.3.0-10.11 -proposed tracker

[Ubuntu Kernel Bot]

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

** Changed in: kernel-sru-workflow/promote-to-proposed
   Status: Fix Committed => Fix Released

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

** 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
  
  -- swm properties --
  packages:
lrm: linux-restricted-modules
main: linux
meta: linux-meta
signed: linux-signed
- phase: Promote to Proposed
- phase-changed: Tuesday, 10. September 2019 10:31 UTC
+ phase: Testing
+ phase-changed: Tuesday, 10. September 2019 14:36 UTC
+ proposed-announcement-sent: true
+ proposed-testing-requested: true
  reason:
-   promote-to-proposed: Pending -- package copied to Proposed signed:queued
+   automated-testing: Stalled -- testing FAILED
+   regression-testing: Ongoing -- testing in progress
  trackers:
bionic/linux-hwe-edge: bug 1843231
  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/1843232

Title:
  eoan/linux: 5.3.0-10.11 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
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-release series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Eoan:
  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 --
  packages:
lrm: linux-restricted-modules
main: linux
meta: linux-meta
signed: linux-signed
  phase: Testing
  phase-changed: Tuesday, 10. September 2019 14:36 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Stalled -- testing FAILED
regression-testing: Ongoing -- testing in progress
  trackers:
bionic/linux-hwe-edge: bug 1843231
  variant: debs

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

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

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

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

Title:
  Guests paused/crash during live-migration

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  after update my hosts (OpenStack Queens) to current packages (I'm
  using 18.04, kernel 4.15.0-62)  live-migration is intermittently
  failing pausing my vms with the following error (this problem doesn't
  occur before upgrade the hosts):

  KVM: entry failed, hardware error 0x8021

  If you're running a guest on an Intel machine without unrestricted mode
  support, the failure can be most likely due to the guest entering an invalid
  state for Intel VT. For example, the guest maybe running in big real mode
  which is not supported on less recent Intel processors.

  RAX=997bdc50 RBX=0003 RCX= 
RDX=
  RSI= RDI= RBP=b8d940387e78 
RSP=b8d940387e78
  R8 =0004 R9 =9dc43fd9d220 R10= 
R11=00cfc7d0f8fb
  R12=0003 R13=9dc43c8e8000 R14= 
R15=
  RIP=997bdfc2 RFL=00010246 [---Z-P-] CPL=0 II=0 A20=1 SMM=0 HLT=0
  ES =   
  CS =0010   00a09b00 DPL=0 CS64 [-RA]
  SS =0018   00c09300 DPL=0 DS   [-WA]
  DS =   
  FS =   
  GS = 9dc43fd8  
  LDT=  000f 
  TR =0040 fe087000 206f 8b00 DPL=0 TSS64-busy
  GDT= fe085000 007f
  IDT= fe00 0fff
  CR0=80050033 CR2= CR3=52e0a003 CR4=00760ee0
  DR0= DR1= DR2= 
DR3= 
  DR6=fffe0ff0 DR7=0400
  EFER=0d01
  Code=90 90 55 48 89 e5 e9 07 00 00 00 0f 00 2d f0 bc 44 00 fb f4 <5d> c3 66 
90 66 2e 0f 1f 84 00 00 00 00 00 55 48 89 e5 e9 07 00 00 00 0f 00 2d d0 bc 44 00
  KVM: entry failed, hardware error 0x8021

  If you're running a guest on an Intel machine without unrestricted mode
  support, the failure can be most likely due to the guest entering an invalid
  state for Intel VT. For example, the guest maybe running in big real mode
  which is not supported on less recent Intel processors.

  RAX=997bdc50 RBX=0002 RCX= 
RDX=
  RSI= RDI= RBP=b8d94037fe78 
RSP=b8d94037fe78
  R8 =0004 R9 =9dc43fd1d220 R10= 
R11=00cfcef806fb
  R12=0002 R13=9dc43c8ebb80 R14= 
R15=
  RIP=997bdfc2 RFL=00010246 [---Z-P-] CPL=0 II=0 A20=1 SMM=0 HLT=0
  ES =   
  CS =0010   00a09b00 DPL=0 CS64 [-RA]
  SS =0018   00c09300 DPL=0 DS   [-WA]
  DS =   
  FS =   
  GS = 9dc43fd0  
  LDT=   
  TR =0040 fe05b000 206f 8b00 DPL=0 TSS64-busy
  GDT= fe059000 007f
  IDT= fe00 0fff
  CR0=80050033 CR2= CR3=52e0a003 CR4=00760ee0
  DR0= DR1= DR2= 
DR3= 
  DR6=fffe0ff0 DR7=0400
  EFER=0d01
  Code=90 90 55 48 89 e5 e9 07 00 00 00 0f 00 2d f0 bc 44 00 fb f4 <5d> c3 66 
90 66 2e 0f 1f 84 00 00 00 00 00 55 48 89 e5 e9 07 00 00 00 0f 00 2d d0 bc 44 00

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

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