[Kernel-packages] [Bug 1854550] Re: [scsi-1130]scsi: scsi_transport_sas: Fix memory leak when removing devices

[Fred Kimmy]

if this patch merge into this linus 5.5 version, whether we can backport
ubuntu 18.04.4 update version or not?

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

Title:
  [scsi-1130]scsi: scsi_transport_sas: Fix memory leak when removing
  devices

Status in kunpeng920:
  Triaged
Status in kunpeng920 ubuntu-18.04 series:
  Invalid
Status in kunpeng920 ubuntu-18.04-hwe series:
  Triaged
Status in kunpeng920 ubuntu-19.04 series:
  Won't Fix
Status in kunpeng920 ubuntu-19.10 series:
  Won't Fix
Status in kunpeng920 ubuntu-20.04 series:
  Triaged
Status in kunpeng920 upstream-kernel series:
  Fix Committed
Status in linux package in Ubuntu:
  Triaged

Bug description:
  "[Steps to reproduce]
  Enable memleak, and do as follows:
  root@(none)$ echo 0 > 
/sys/devices/platform/HISI0162:01/host0/port-0:0/expander-0:0/port-0:0:10/phy-0:0:10/sas_phy/phy-0:0:10/enable
  [   79.857888] hisi_sas_v2_hw HISI0162:01: dev[7:1] is gone
  root@(none)$ echo scan > /sys/kernel/debug/kmemleak
  [  131.656603] kmemleak: 3 new suspected memory leaks (see 
/sys/kernel/debug/kmemleak)
  root@(none)$ more /sys/kernel/debug/kmemleak
  unreferenced object 0x041da5c66000 (size 256):
comm ""kworker/u128:1"", pid 549, jiffies 4294898543 (age 113.728s)
hex dump (first 32 bytes):
  00 5e c6 a5 1d 04 ff ff 01 00 00 00 00 00 00 00  .^..
  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  
backtrace:
  [<(ptrval)>] kmem_cache_alloc+0x188/0x260
  [<(ptrval)>] bsg_setup_queue+0x48/0x1a8
  [<(ptrval)>] sas_rphy_add+0x108/0x2d0
  [<(ptrval)>] sas_probe_devices+0x168/0x208
  [<(ptrval)>] sas_discover_domain+0x660/0x9c8
  [<(ptrval)>] process_one_work+0x3f8/0x690
  [<(ptrval)>] worker_thread+0x70/0x6a0
  [<(ptrval)>] kthread+0x1b8/0x1c0
  [<(ptrval)>] ret_from_fork+0x10/0x18
  unreferenced object 0x041d8c075400 (size 128):
comm ""kworker/u128:1"", pid 549, jiffies 4294898543 (age 113.728s)
hex dump (first 32 bytes):
  00 40 25 97 1d 00 ff ff 00 00 00 00 00 00 00 00  .@%.
  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  
backtrace:
  [<(ptrval)>] __kmalloc_node+0x1a8/0x2c8
  [<(ptrval)>] blk_mq_realloc_tag_set_tags.part.70+0x48/0xd8
  [<(ptrval)>] blk_mq_alloc_tag_set+0x1dc/0x530
  [<(ptrval)>] bsg_setup_queue+0xe8/0x1a8
  [<(ptrval)>] sas_rphy_add+0x108/0x2d0
  [<(ptrval)>] sas_probe_devices+0x168/0x208
  [<(ptrval)>] sas_discover_domain+0x660/0x9c8
  [<(ptrval)>] process_one_work+0x3f8/0x690
  [<(ptrval)>] worker_thread+0x70/0x6a0
  [<(ptrval)>] kthread+0x1b8/0x1c0
  [<(ptrval)>] ret_from_fork+0x10/0x18
  unreferenced object 0x041da5c65e00 (size 256):
comm ""kworker/u128:1"", pid 549, jiffies 4294898543 (age 113.728s)
hex dump (first 32 bytes):
  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  
  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  
backtrace:
  [<(ptrval)>] __kmalloc_node+0x1a8/0x2c8
  [<(ptrval)>] blk_mq_alloc_tag_set+0x254/0x530
  [<(ptrval)>] bsg_setup_queue+0xe8/0x1a8
  [<(ptrval)>] sas_rphy_add+0x108/0x2d0
  [<(ptrval)>] sas_probe_devices+0x168/0x208
  [<(ptrval)>] sas_discover_domain+0x660/0x9c8
  [<(ptrval)>] process_one_work+0x3f8/0x690
  [<(ptrval)>] worker_thread+0x70/0x6a0
  [<(ptrval)>] kthread+0x1b8/0x1c0
  [<(ptrval)>] ret_from_fork+0x10/0x18
  root@(none)$

  [solution]
  Fix by doing the queue removal in one place - in sas_rphy_remove() -
  instead of unregistering the queue in sas_rphy_remove() and finally
  cleaning up the queue in calling blk_cleanup_queue() from
  sas_end_device_release() or sas_expander_release().

  Function bsg_remove_queue() can handle a NULL pointer q, so remove the
  precheck in sas_rphy_remove().
  "
  scsi: scsi_transport_sas: Fix memory leak when removing devices

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

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

[Kernel-packages] [Bug 1856387] Re: Freezing on boot since kernel 4.15.0-72-generic release

[You-Sheng Yang]

Is it possible for you to perform kernel bisecting between -70 and -72?

* 
https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/bionic/tag/?h=Ubuntu-4.15.0-70.79
* 
https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/bionic/tag/?h=Ubuntu-4.15.0-72.81

See https://wiki.ubuntu.com/Kernel/KernelBisection for detailed steps.

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

Title:
  Freezing on boot since kernel 4.15.0-72-generic release

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After the update to install kernel 4.15.0-72-generic (a bit over a week ago) 
my computer will not boot. On boot, all I see is the purple screen with:
  Loading Linux 4.15.0-72-generic ...
  Loading initial ramdisk ...
  and nothing happens. Just sits there. I've waited about 5-10 minutes on 
occasion but to no avail.
  I've checked a number of logs in /var/log but not found anything.

  If I go into the advanced options and select kernel
  4.15.0-70-generic, the computer boots normally.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-72-generic 4.15.0-72.81
  ProcVersionSignature: Ubuntu 4.15.0-70.79-generic 4.15.18
  Uname: Linux 4.15.0-70-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tony   1977 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Dec 14 21:53:14 2019
  HibernationDevice: RESUME=UUID=5475ce25-e091-45e2-9811-9b5cddc08dd1
  InstallationDate: Installed on 2018-09-16 (454 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 04f2:b59e Chicony Electronics Co., Ltd 
   Bus 001 Device 002: ID 046d:c063 Logitech, Inc. DELL Laser Mouse
   Bus 001 Device 004: ID 8087:0aaa Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: GIGABYTE Sabre 17WV8
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-70-generic 
root=UUID=9455257c-d3b7-4d61-853d-ab0b0ee40013 ro acpi=off
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-70-generic N/A
   linux-backports-modules-4.15.0-70-generic  N/A
   linux-firmware 1.173.13
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/22/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F05
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: Sabre 17WV8
  dmi.board.vendor: GIGABYTE
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: GIGABYTE
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF05:bd05/22/2018:svnGIGABYTE:pnSabre17WV8:pvrNotApplicable:rvnGIGABYTE:rnSabre17WV8:rvrNotApplicable:cvnGIGABYTE:ct10:cvrN/A:
  dmi.product.family: Sabre
  dmi.product.name: Sabre 17WV8
  dmi.product.version: Not Applicable
  dmi.sys.vendor: GIGABYTE

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

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

[Kernel-packages] [Bug 1856308] Re: [Realtek Audio Codec ALC294] [ASUS R542UF] Since Linux 4.20 and newer no sound at all

[Kai-Heng Feng]

Please test latest mainline kernel:
https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.5-rc2/

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

Title:
  [Realtek Audio Codec ALC294] [ASUS R542UF] Since Linux 4.20 and newer
  no sound at all

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Similar issue https://bugs.launchpad.net/ubuntu/+source/alsa-
  driver/+bug/1784485

  tl;dr

  I have sound only under 4.19.x series. 
  I have NOT sound at all under newer kernel series. 

  HW Details:
  ```
  kubuntu@kubuntu:~$ sudo hwinfo --sound
  20: PCI 1f.3: 0403 Audio device 
[Created at pci.386]
Unique ID: nS1_.b28td23g3aB
SysFS ID: /devices/pci:00/:00:1f.3
SysFS BusID: :00:1f.3
Hardware Class: sound
Model: "Intel Sunrise Point-LP HD Audio"
Vendor: pci 0x8086 "Intel Corporation"
Device: pci 0x9d71 "Sunrise Point-LP HD Audio"
SubVendor: pci 0x1043 "ASUSTeK Computer Inc."
SubDevice: pci 0x1a00 
Revision: 0x21
Driver: "snd_hda_intel"
Driver Modules: "snd_hda_intel"
Memory Range: 0xef528000-0xef52bfff (rw,non-prefetchable)
Memory Range: 0xef50-0xef50 (rw,non-prefetchable)
IRQ: 132 (1577 events)
Module Alias: "pci:v8086d9D71sv1043sd1A00bc04sc03i00"
Driver Info #0:
  Driver Status: snd_hda_intel is active
  Driver Activation Cmd: "modprobe snd_hda_intel"
Driver Info #1:
  Driver Status: snd_soc_skl is active
  Driver Activation Cmd: "modprobe snd_soc_skl"
Config Status: cfg=new, avail=yes, need=no, active=unknown
  ```
  ```
   Linux version 5.3.0-24-generic (buildd@lgw01-amd64-035) (gcc version 9.2.1 
20191008 (Ubuntu 9.2.1-9ubuntu2)) #26-Ubuntu SMP Thu Nov 14 01:33:18 UTC 2019 
(Ubuntu 5.3.0-24.26-generic 5.3.10)
  ```
  ```
  [0.00] efi: EFI v2.60 by American Megatrends
  [0.00] efi:  TPMFinalLog=0x8adf  ACPI 2.0=0x8a98d000  
ACPI=0x8a98d000  SMBIOS=0x8b214000  SMBIOS 3.0=0x8b213000  ESRT=0x884d4e98  
MEMATTR=0x8739a018 
  [0.00] secureboot: Secure boot could not be determined (mode 0)
  [0.00] SMBIOS 3.0.0 present.
  [0.00] DMI: ASUSTeK COMPUTER INC. VivoBook 15_ASUS Laptop 
X542UF/X542UF, BIOS X542UF.307 06/13/2019
  [0.00] tsc: Detected 1800.000 MHz processor
  [0.00] [Firmware Bug]: TSC ADJUST: CPU0: -214721515 force to 0
  ```
  ```
  kubuntu@kubuntu:~$ lspci
  00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v6/7th Gen Core Processor 
Host Bridge/DRAM Registers (rev 08)
  00:02.0 VGA compatible controller: Intel Corporation UHD Graphics 620 (rev 07)
  00:04.0 Signal processing controller: Intel Corporation Xeon E3-1200 
v5/E3-1500 v5/6th Gen Core Processor Thermal Subsystem (rev 08)
  00:14.0 USB controller: Intel Corporation Sunrise Point-LP USB 3.0 xHCI 
Controller (rev 21)
  00:14.2 Signal processing controller: Intel Corporation Sunrise Point-LP 
Thermal subsystem (rev 21)
  00:15.0 Signal processing controller: Intel Corporation Sunrise Point-LP 
Serial IO I2C Controller #0 (rev 21)
  00:15.1 Signal processing controller: Intel Corporation Sunrise Point-LP 
Serial IO I2C Controller #1 (rev 21)
  00:16.0 Communication controller: Intel Corporation Sunrise Point-LP CSME 
HECI #1 (rev 21)
  00:17.0 SATA controller: Intel Corporation Sunrise Point-LP SATA Controller 
[AHCI mode] (rev 21)
  00:1c.0 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port 
#1 (rev f1)
  00:1c.4 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port 
#5 (rev f1)
  00:1c.5 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port 
#6 (rev f1)
  00:1e.0 Signal processing controller: Intel Corporation Sunrise Point-LP 
Serial IO UART Controller #0 (rev 21)
  00:1e.2 Signal processing controller: Intel Corporation Sunrise Point-LP 
Serial IO SPI Controller #0 (rev 21)
  00:1f.0 ISA bridge: Intel Corporation Sunrise Point LPC Controller/eSPI 
Controller (rev 21)
  00:1f.2 Memory controller: Intel Corporation Sunrise Point-LP PMC (rev 21)
  00:1f.3 Audio device: Intel Corporation Sunrise Point-LP HD Audio (rev 21)
  00:1f.4 SMBus: Intel Corporation Sunrise Point-LP SMBus (rev 21)
  01:00.0 3D controller: NVIDIA Corporation GM108M [GeForce MX130] (rev a2)
  02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. 
RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 15)
  03:00.0 Network controller: Qualcomm Atheros QCA9377 802.11ac Wireless 
Network Adapter (rev 31)
  ```
  ```
  kubuntu@kubuntu:~$ aplay -l
   List of PLAYBACK Hardware Devices 
  card 0: PCH [HDA Intel PCH], device 0: ALC294 Analog [ALC294 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 3: HDMI 0 [HDMI 0]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 7: HDMI 1 

[Kernel-packages] [Bug 1856440] Re: cpufreq: no or unknown cpufreq driver

[Erich Eickmeyer]

It did definitely work in 19.04, but cannot find a CPU governor on 19.10
or Focal.

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

Title:
  cpufreq: no or unknown cpufreq driver

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Not sure where this goes, but no cpufreq driver is available in 19.10
  or 20.04 on AMD CPUs. I'm not sure why this is happening, but no
  cpufreq driver gets loaded.

  Output of cpufreq-info
  cpufrequtils 008: cpufreq-info (C) Dominik Brodowski 2004-2009
  Report errors and bugs to cpuf...@vger.kernel.org, please.
  analyzing CPU 0:
no or unknown cpufreq driver is active on this CPU
maximum transition latency: 4294.55 ms.
  analyzing CPU 1:
no or unknown cpufreq driver is active on this CPU
maximum transition latency: 4294.55 ms.
  analyzing CPU 2:
no or unknown cpufreq driver is active on this CPU
maximum transition latency: 4294.55 ms.
  analyzing CPU 3:
no or unknown cpufreq driver is active on this CPU
maximum transition latency: 4294.55 ms.

  Output of cpupower frequency-info
  analyzing CPU 0:
no or unknown cpufreq driver is active on this CPU
CPUs which run at the same hardware frequency: Not Available
CPUs which need to have their frequency coordinated by software: Not 
Available
maximum transition latency:  Cannot determine or is not supported.
  Not Available
available cpufreq governors: Not Available
Unable to determine current policy
current CPU frequency: Unable to call hardware
current CPU frequency:  Unable to call to kernel
boost state support:
  Supported: yes
  Active: yes
  Boost States: 3
  Total States: 8
  Pstate-Pb0: 3300MHz (boost state)
  Pstate-Pb1: 3100MHz (boost state)
  Pstate-Pb2: 2800MHz (boost state)
  Pstate-P0:  2600MHz
  Pstate-P1:  2200MHz
  Pstate-P2:  1800MHz
  Pstate-P3:  1400MHz
  Pstate-P4:  1200MHz

  Issue is present in 19.10. Upgraded to 20.04 to see if issue persists
  and it does.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.3.0-24-lowlatency 5.3.0-24.26
  ProcVersionSignature: Ubuntu 5.3.0-24.26-lowlatency 5.3.10
  Uname: Linux 5.3.0-24-lowlatency x86_64
  ApportVersion: 2.20.11-0ubuntu13
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  erich  3958 F pulseaudio
   /dev/snd/controlC3:  erich  3958 F pulseaudio
   /dev/snd/controlC1:  erich  3958 F pulseaudio
   /dev/snd/controlC0:  erich  3958 F pulseaudio
  CurrentDesktop: GNOME
  Date: Sat Dec 14 20:59:10 2019
  InstallationDate: Installed on 2019-02-12 (306 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190203)
  MachineType: Dell Inc. Inspiron 5576
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-lowlatency 
root=UUID=cbf0a967-a34d-43b1-a42e-993daa70b8f7 ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-24-lowlatency N/A
   linux-backports-modules-5.3.0-24-lowlatency  N/A
   linux-firmware   1.184
  SourcePackage: linux
  UpgradeStatus: Upgraded to focal on 2019-12-15 (0 days ago)
  dmi.bios.date: 01/29/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.0.7
  dmi.board.name: 0HJ6MY
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.0.7:bd01/29/2018:svnDellInc.:pnInspiron5576:pvr1.0.7:rvnDellInc.:rn0HJ6MY:rvrA00:cvnDellInc.:ct10:cvrNotSpecified:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 5576
  dmi.product.sku: 07E2
  dmi.product.version: 1.0.7
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1852493] Re: Freeze on suspend (Acer SF314-57)

[Kai-Heng Feng]

s2idle should work. Can you please give v5.5-rc1 a try?

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

Title:
  Freeze on suspend (Acer SF314-57)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I freshly installed Ubuntu Budgie 19.10 today after receiving my new
  notebook. However, when putting the system to suspend (or hibernate),
  the screen goes off and the system freezes. The fan keeps running,
  keyboard backlight and power led are on. Sometimes, when pressing a
  button, I can get the screen to turn back on, but its frozen as well
  (no mouse movement, clock stuck etc.)

  So far I tried increasing the swap file size, however this did not
  help. I also livebooted Ubuntu 19.10 and tried suspend, but I had the
  same issue.

  Could this be a problem of my fairly new chipset (Intel i7 1065G7)?
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  norbert1508 F pulseaudio
   /dev/snd/pcmC0D0p:   norbert1508 F...m pulseaudio
  CurrentDesktop: Budgie:GNOME
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2019-11-13 (1 days ago)
  InstallationMedia: Ubuntu-Budgie 19.10 "Eoan Ermine" - Release amd64 
(20191017)
  MachineType: Acer Swift SF314-57
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-23-generic 
root=/dev/mapper/vgubuntu--budgie-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-23-generic N/A
   linux-backports-modules-5.3.0-23-generic  N/A
   linux-firmware1.183.2
  Tags:  eoan
  Uname: Linux 5.3.0-23-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/05/2019
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.07
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Floris_IL
  dmi.board.vendor: IL
  dmi.board.version: V1.07
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.07:bd09/05/2019:svnAcer:pnSwiftSF314-57:pvrV1.07:rvnIL:rnFloris_IL:rvrV1.07:cvnAcer:ct10:cvrChassisVersion:
  dmi.product.family: Swift 3
  dmi.product.name: Swift SF314-57
  dmi.product.sku: 
  dmi.product.version: V1.07
  dmi.sys.vendor: Acer

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

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

[Kernel-packages] [Bug 1856440] Re: cpufreq: no or unknown cpufreq driver

[Kai-Heng Feng]

Did it work on Disco i.e. Linux kernel v5.0?

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

Title:
  cpufreq: no or unknown cpufreq driver

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Not sure where this goes, but no cpufreq driver is available in 19.10
  or 20.04 on AMD CPUs. I'm not sure why this is happening, but no
  cpufreq driver gets loaded.

  Output of cpufreq-info
  cpufrequtils 008: cpufreq-info (C) Dominik Brodowski 2004-2009
  Report errors and bugs to cpuf...@vger.kernel.org, please.
  analyzing CPU 0:
no or unknown cpufreq driver is active on this CPU
maximum transition latency: 4294.55 ms.
  analyzing CPU 1:
no or unknown cpufreq driver is active on this CPU
maximum transition latency: 4294.55 ms.
  analyzing CPU 2:
no or unknown cpufreq driver is active on this CPU
maximum transition latency: 4294.55 ms.
  analyzing CPU 3:
no or unknown cpufreq driver is active on this CPU
maximum transition latency: 4294.55 ms.

  Output of cpupower frequency-info
  analyzing CPU 0:
no or unknown cpufreq driver is active on this CPU
CPUs which run at the same hardware frequency: Not Available
CPUs which need to have their frequency coordinated by software: Not 
Available
maximum transition latency:  Cannot determine or is not supported.
  Not Available
available cpufreq governors: Not Available
Unable to determine current policy
current CPU frequency: Unable to call hardware
current CPU frequency:  Unable to call to kernel
boost state support:
  Supported: yes
  Active: yes
  Boost States: 3
  Total States: 8
  Pstate-Pb0: 3300MHz (boost state)
  Pstate-Pb1: 3100MHz (boost state)
  Pstate-Pb2: 2800MHz (boost state)
  Pstate-P0:  2600MHz
  Pstate-P1:  2200MHz
  Pstate-P2:  1800MHz
  Pstate-P3:  1400MHz
  Pstate-P4:  1200MHz

  Issue is present in 19.10. Upgraded to 20.04 to see if issue persists
  and it does.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.3.0-24-lowlatency 5.3.0-24.26
  ProcVersionSignature: Ubuntu 5.3.0-24.26-lowlatency 5.3.10
  Uname: Linux 5.3.0-24-lowlatency x86_64
  ApportVersion: 2.20.11-0ubuntu13
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  erich  3958 F pulseaudio
   /dev/snd/controlC3:  erich  3958 F pulseaudio
   /dev/snd/controlC1:  erich  3958 F pulseaudio
   /dev/snd/controlC0:  erich  3958 F pulseaudio
  CurrentDesktop: GNOME
  Date: Sat Dec 14 20:59:10 2019
  InstallationDate: Installed on 2019-02-12 (306 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190203)
  MachineType: Dell Inc. Inspiron 5576
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-lowlatency 
root=UUID=cbf0a967-a34d-43b1-a42e-993daa70b8f7 ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-24-lowlatency N/A
   linux-backports-modules-5.3.0-24-lowlatency  N/A
   linux-firmware   1.184
  SourcePackage: linux
  UpgradeStatus: Upgraded to focal on 2019-12-15 (0 days ago)
  dmi.bios.date: 01/29/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.0.7
  dmi.board.name: 0HJ6MY
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.0.7:bd01/29/2018:svnDellInc.:pnInspiron5576:pvr1.0.7:rvnDellInc.:rn0HJ6MY:rvrA00:cvnDellInc.:ct10:cvrNotSpecified:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 5576
  dmi.product.sku: 07E2
  dmi.product.version: 1.0.7
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1853197] Re: Memory leak in net/xfrm/xfrm_state.c - 8 pages per ipsec connection

[Bernd Schütte]

Tested 5.3.0-25-generic on Eoan and it fixes the memory leak there as
well.

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

Title:
  Memory leak in net/xfrm/xfrm_state.c - 8 pages per ipsec connection

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

Bug description:
  [SRU Justification]

  == Impact ==

  An upstream change in v4.11 made xfrm loose memory (8 pages per ipsec 
connection). This was fixed in v5.4 by:
commit 86c6739eda7d "xfrm: Fix memleak on xfrm state destroy"

  == Fix ==

  Pick the upstream fix into all affected series.

  == Testcase ==

  see below

  == Risk of Regression ==

  Low, the change adds a single memory release case in one driver. The
  effect can be verified.

  ---

  Ubuntu linux distro, 4.15.0-62 kernel, server platform.
  This OS is used as an IPSec VPN gateway.  It serves up to several hundred 
concurrent connections

  In an attempt to upgrade from the 4.4 kernel to 4.15, the team noticed
  that VPN gateway VMs were running out of physical memory after 12-48
  hours, depending on load.

  Attachments from a server machine in this state in attached leakinfo.txt
  output of free -t
  output of /proc/meminfo in out of memory condition
  output of /slabtop -o -sc
  /sys/kernel/debug/page_owner sorted and aggregated after server ran for 12 
hrs and ran out of memory
  Patches for 4.15 and 5.4

  Highlight from page_owner, we can see the leak is a buffer associated
  with the ipsec impelementation.  Each connection leaks 32k of memory
  via alloc_page with order=3

  100960 times:
  Page allocated via order 3, mask 
0x1085220(GFP_ATOMIC|__GFP_NOWARN|__GFP_NORETRY|__GFP_COMP)
   get_page_from_freelist+0xd64/0x1250
   __alloc_pages_nodemask+0x11c/0x2e0
   alloc_pages_current+0x6a/0xe0
   skb_page_frag_refill+0x71/0x100
   esp_output_head+0x265/0x3e0 [esp4]
   esp_output+0xbc/0x180 [esp4]
   xfrm_output_resume+0x179/0x530
   xfrm_output+0x8e/0x230
   xfrm4_output_finish+0x2b/0x30
   __xfrm4_output+0x3a/0x50
   xfrm4_output+0x43/0xc0
   ip_forward_finish+0x51/0x80
   ip_forward+0x38a/0x480
   ip_rcv_finish+0x122/0x410
   ip_rcv+0x292/0x360
   __netif_receive_skb_core+0x815/0xbd0

  Patch to fix this issue in 4.15 (tested and verified on same server 
exhibiting above leak):
  diff --git a/net/xfrm/xfrm_state.c b/net/xfrm/xfrm_state.c
  index 728272f..7842f83 100644
  --- a/net/xfrm/xfrm_state.c
  +++ b/net/xfrm/xfrm_state.c
  @@ -451,6 +451,10 @@ static void xfrm_state_gc_destroy(struct xfrm_state *x)
  }
  xfrm_dev_state_free(x);
  security_xfrm_state_free(x);
  +
  +   if(x->xfrag.page)
  +   put_page(x->xfrag.page);
  +
  kfree(x);
  }

  Patch for master branch (5.4 I believe) from Paul Wouters
  (p...@nohats.ca)

  diff --git a/net/xfrm/xfrm_state.c b/net/xfrm/xfrm_state.c
  index c6f3c4a1bd99..f3423562d933 100644
  --- a/net/xfrm/xfrm_state.c
  +++ b/net/xfrm/xfrm_state.c
  @@ -495,6 +495,8 @@ static void ___xfrm_state_destroy(struct xfrm_state *x)
  x->type->destructor(x);
  xfrm_put_type(x->type);
  }
  + if (x->xfrag.page)
  + put_page(x->xfrag.page);
  xfrm_dev_state_free(x);
  security_xfrm_state_free(x);
  xfrm_state_free(x);

  Severity:  Critical - we are unable to use any kernel later than 4.11,
  and are sticking with 4.4 in production.

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

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

[Kernel-packages] [Bug 1856370] Re: GPU has fallen off the bus

[Kai-Heng Feng]

Can you please attach dmesg so I can see why sound doesn't work?

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

Title:
  GPU has fallen off the bus

Status in linux package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-435 package in Ubuntu:
  New

Bug description:
  Every time I suspend my laptop, after I resume it, a black screen
  shows with the error message

  - GPU has fallen off the bus

  It's a plain vanilla Ubunbtu 19.10 installation on an Dell XPS 15 7590
  with NVIDIA(R) GeForce(R) GTX 1650 4GB GDDR5

  Description:  Ubuntu 19.10
  Release:  19.10
  nvidia driver 435

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  Uname: Linux 5.3.0-24-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  435.21  Sun Aug 25 08:17:57 
CDT 2019
   GCC version:  gcc version 9.2.1 20191008 (Ubuntu 9.2.1-9ubuntu2)
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Dec 13 16:31:58 2019
  DistUpgraded: Fresh install
  DistroCodename: eoan
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 435.21, 5.3.0-18-generic, x86_64: installed
   nvidia, 435.21, 5.3.0-24-generic, x86_64: installed
   virtualbox, 6.0.14, 5.3.0-24-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (prog-if 00 [VGA 
controller])
 Subsystem: Dell UHD Graphics 630 (Mobile) [1028:0905]
 Subsystem: Dell Device [1028:0905]
  InstallationDate: Installed on 2019-12-13 (0 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: Dell Inc. XPS 15 7590
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic 
root=UUID=0b1a4be3-b095-45fc-ae1b-4b6fb7845eb2 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/25/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.3.3
  dmi.board.name: 0VYV0G
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.3.3:bd09/25/2019:svnDellInc.:pnXPS157590:pvr:rvnDellInc.:rn0VYV0G:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 15 7590
  dmi.product.sku: 0905
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.1-1ubuntu1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  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/1856370/+subscriptions

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

[Kernel-packages] [Bug 1856557] Re: Touchpad not found

[Kai-Heng Feng]

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

** This bug has been marked a duplicate of bug 1854798
   Synaptics s3203 touchpad not working after update to kernel 4.15.0-72-generic

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

Title:
  Touchpad not found

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  My laptop was shutdown from low battery and when turn on, my touchpad
  was not working

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-72-generic 4.15.0-72.81
  ProcVersionSignature: Ubuntu 4.15.0-72.81-generic 4.15.18
  Uname: Linux 4.15.0-72-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  luan   4220 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Dec 16 09:45:12 2019
  InstallationDate: Installed on 2018-11-07 (403 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 13d3:5a02 IMC Networks 
   Bus 001 Device 002: ID 0cf3:e500 Atheros Communications, Inc. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 80YH
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-72-generic 
root=UUID=a12740a1-d4e7-4532-b3cb-551c3932b684 ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-72-generic N/A
   linux-backports-modules-4.15.0-72-generic  N/A
   linux-firmware 1.173.12
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/04/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 4WCN37WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40679 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad 320-15IKB
  dmi.modalias: 
dmi:bvnLENOVO:bvr4WCN37WW:bd12/04/2017:svnLENOVO:pn80YH:pvrLenovoideapad320-15IKB:rvnLENOVO:rnLNVNB161216:rvrSDK0J40679WIN:cvnLENOVO:ct10:cvrLenovoideapad320-15IKB:
  dmi.product.family: ideapad 320-15IKB
  dmi.product.name: 80YH
  dmi.product.version: Lenovo ideapad 320-15IKB
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1856653] Re: CVE-2019-0154 caused major power problem, pls backport maintainers fix

[Tim Richardson]

logs not applicable

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

** Summary changed:

- CVE-2019-0154 caused major power problem, pls backport maintainers fix
+ CVE-2019-0154 caused major power problem, pls backport maintainer's fix

** Summary changed:

- CVE-2019-0154 caused major power problem, pls backport maintainer's fix
+ CVE-2019-0154 caused major power problem, pls backport upstream's fix

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

Title:
  CVE-2019-0154 caused major power problem, pls backport upstream's fix

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  https://gitlab.freedesktop.org/drm/intel/issues/614
  the fix released as CVE-2019-0154 increases idle power consumption on intel 
i915 6th gen and later.
  That's because the GPU does not enter RC6 any more.

  For example, my Thinkpad P50 (6th gen) idles at 9w with current 5.3 kernels. 
Previously, it idled at 5W.
  Effects on a T480 (8th gen) are less dramatic but still significant.

  5.5RC1 has the maintainer's second pass at this, which restores RC6
  idling

  The maintainer's patch for 5.3 is here:
   https://gitlab.freedesktop.org/drm/intel/issues/614#note_366057

  I have applied this to tag Ubuntu-hwe-5.3.0-25.27~18.04.2 and it
  builds. I am testing it now.

  I think it would be very helpful to backport this if you can.

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

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

[Kernel-packages] [Bug 1853044] Re: 5.3.0-23-generic causes fans to spin when idle

[Kai-Heng Feng]

Seems like LP: #1856653 is the same issue.

The solution from Chris Wilson:
https://gitlab.freedesktop.org/drm/intel/issues/614#note_366057

** Bug watch added: gitlab.freedesktop.org/drm/intel/issues #614
   https://gitlab.freedesktop.org/drm/intel/issues/614

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

Title:
  5.3.0-23-generic causes fans to spin when idle

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After upgrading to 5.3.0-23-generic the fans in my machine don't stop
  running. They always sound like something is utilizing CPU - even with
  no applications running after boot.

  If I boot back to 5.3.0-19-generic it's fine.

  My microcode version is reported as 0xd4 and iucode-tool reports:

  iucode-tool: system has processor(s) with signature 0x000506e3

  Let me know if you need anything else.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: linux-image-5.3.0-23-generic 5.3.0-23.25
  ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7
  Uname: Linux 5.3.0-23-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  dean   2898 F pulseaudio
   /dev/snd/pcmC2D0p:   dean   2898 F...m pulseaudio
   /dev/snd/controlC0:  dean   2898 F pulseaudio
   /dev/snd/controlC1:  dean   2898 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Nov 18 13:03:34 2019
  HibernationDevice: RESUME=UUID=55a42c82-50bf-4e75-a133-dbd3aa93611b
  InstallationDate: Installed on 2018-07-24 (482 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180724)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-23-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-23-generic N/A
   linux-backports-modules-5.3.0-23-generic  N/A
   linux-firmware1.183.2
  SourcePackage: linux
  UpgradeStatus: Upgraded to eoan on 2019-07-19 (121 days ago)
  dmi.bios.date: 05/16/2018
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: KYSKLi70.86A.0055.2018.0516.1629
  dmi.board.name: NUC6i7KYB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: H90766-406
  dmi.chassis.type: 3
  dmi.chassis.vendor: Intel Corporation
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrKYSKLi70.86A.0055.2018.0516.1629:bd05/16/2018:svn:pn:pvr:rvnIntelCorporation:rnNUC6i7KYB:rvrH90766-406:cvnIntelCorporation:ct3:cvr1.0:

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

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

[Kernel-packages] [Bug 1856653] Re: CVE-2019-0154 caused major power problem, pls backport maintainers fix

[Tim Richardson]

** Description changed:

  https://gitlab.freedesktop.org/drm/intel/issues/614
  the fix released as CVE-2019-0154 increases idle power consumption on intel 
i915 6th gen and later.
- That's because the GPU does not enter RC6 any more. 
+ That's because the GPU does not enter RC6 any more.
  
- For example, my Thinkpad P50 (6th gen) idles at 9w with current 5.3 kernels. 
Previously, it idled at 5W. 
- Effects on a T480 (8th gen) are less dramatic but still significant. 
+ For example, my Thinkpad P50 (6th gen) idles at 9w with current 5.3 kernels. 
Previously, it idled at 5W.
+ Effects on a T480 (8th gen) are less dramatic but still significant.
  
+ 5.5RC1 has the maintainer's second pass at this, which restores RC6
+ idling
  
- 5.5RC1 has the maintainers second pass at this, which restores RC6 idling
- 
- The maintainers patch for 5.3 is here:
-  https://gitlab.freedesktop.org/drm/intel/issues/614#note_366057
+ The maintainer's patch for 5.3 is here:
+  https://gitlab.freedesktop.org/drm/intel/issues/614#note_366057
  
  I have applied this to tag Ubuntu-hwe-5.3.0-25.27~18.04.2 and it builds.
  I am testing it now.
  
  I think it would be very helpful to backport this if you can.

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

Title:
  CVE-2019-0154 caused major power problem, pls backport maintainers fix

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  https://gitlab.freedesktop.org/drm/intel/issues/614
  the fix released as CVE-2019-0154 increases idle power consumption on intel 
i915 6th gen and later.
  That's because the GPU does not enter RC6 any more.

  For example, my Thinkpad P50 (6th gen) idles at 9w with current 5.3 kernels. 
Previously, it idled at 5W.
  Effects on a T480 (8th gen) are less dramatic but still significant.

  5.5RC1 has the maintainer's second pass at this, which restores RC6
  idling

  The maintainer's patch for 5.3 is here:
   https://gitlab.freedesktop.org/drm/intel/issues/614#note_366057

  I have applied this to tag Ubuntu-hwe-5.3.0-25.27~18.04.2 and it
  builds. I am testing it now.

  I think it would be very helpful to backport this if you can.

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

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

[Kernel-packages] [Bug 1856653] [NEW] CVE-2019-0154 caused major power problem, pls backport maintainers fix

[Tim Richardson]

Public bug reported:

https://gitlab.freedesktop.org/drm/intel/issues/614
the fix released as CVE-2019-0154 increases idle power consumption on intel 
i915 6th gen and later.
That's because the GPU does not enter RC6 any more.

For example, my Thinkpad P50 (6th gen) idles at 9w with current 5.3 kernels. 
Previously, it idled at 5W.
Effects on a T480 (8th gen) are less dramatic but still significant.

5.5RC1 has the maintainer's second pass at this, which restores RC6
idling

The maintainer's patch for 5.3 is here:
 https://gitlab.freedesktop.org/drm/intel/issues/614#note_366057

I have applied this to tag Ubuntu-hwe-5.3.0-25.27~18.04.2 and it builds.
I am testing it now.

I think it would be very helpful to backport this if you can.

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: 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/1856653

Title:
  CVE-2019-0154 caused major power problem, pls backport maintainers fix

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  https://gitlab.freedesktop.org/drm/intel/issues/614
  the fix released as CVE-2019-0154 increases idle power consumption on intel 
i915 6th gen and later.
  That's because the GPU does not enter RC6 any more.

  For example, my Thinkpad P50 (6th gen) idles at 9w with current 5.3 kernels. 
Previously, it idled at 5W.
  Effects on a T480 (8th gen) are less dramatic but still significant.

  5.5RC1 has the maintainer's second pass at this, which restores RC6
  idling

  The maintainer's patch for 5.3 is here:
   https://gitlab.freedesktop.org/drm/intel/issues/614#note_366057

  I have applied this to tag Ubuntu-hwe-5.3.0-25.27~18.04.2 and it
  builds. I am testing it now.

  I think it would be very helpful to backport this if you can.

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

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

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

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

Title:
  CVE-2019-0154 caused major power problem, pls backport maintainers fix

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  https://gitlab.freedesktop.org/drm/intel/issues/614
  the fix released as CVE-2019-0154 increases idle power consumption on intel 
i915 6th gen and later.
  That's because the GPU does not enter RC6 any more.

  For example, my Thinkpad P50 (6th gen) idles at 9w with current 5.3 kernels. 
Previously, it idled at 5W.
  Effects on a T480 (8th gen) are less dramatic but still significant.

  5.5RC1 has the maintainer's second pass at this, which restores RC6
  idling

  The maintainer's patch for 5.3 is here:
   https://gitlab.freedesktop.org/drm/intel/issues/614#note_366057

  I have applied this to tag Ubuntu-hwe-5.3.0-25.27~18.04.2 and it
  builds. I am testing it now.

  I think it would be very helpful to backport this if you can.

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

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

[Kernel-packages] [Bug 1856642] Re: Add new PCH ID for the Intel Comet Lake -H variant

[You-Sheng Yang]

** Description changed:

+ [SRU Justification]
+ 
+ [Impact]
+ DesignWare USB3 not enabled on certain Comet Lake platforms.
+ 
+ [Fix]
+ Commit 3c3caae4cd6e ("usb: dwc3: pci: add ID for the Intel Comet Lake -H 
variant")
+ 
+ [Test Case]
+ Find following line in dmesg:
+ 
+   dwc3-pci :00:16.0: enabling device ...
+ 
+ [Regression Potential]
+ Low. Add new ID for a new device.
+ 
+ == original bug description ==
+ 
  New ID available in
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=3c3caae4cd6e122472efcf64759ff6392fb6bce2

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

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

** Changed in: linux (Ubuntu Eoan)
   Status: New => 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/1856642

Title:
  Add new PCH ID for the Intel Comet Lake -H variant

Status in linux package in Ubuntu:
  In Progress
Status in linux-oem-osp1 package in Ubuntu:
  Confirmed
Status in linux source package in Bionic:
  Won't Fix
Status in linux-oem-osp1 source package in Bionic:
  In Progress
Status in linux source package in Eoan:
  In Progress
Status in linux-oem-osp1 source package in Eoan:
  Confirmed
Status in linux source package in Focal:
  In Progress
Status in linux-oem-osp1 source package in Focal:
  Confirmed

Bug description:
  [SRU Justification]

  [Impact]
  DesignWare USB3 not enabled on certain Comet Lake platforms.

  [Fix]
  Commit 3c3caae4cd6e ("usb: dwc3: pci: add ID for the Intel Comet Lake -H 
variant")

  [Test Case]
  Find following line in dmesg:

dwc3-pci :00:16.0: enabling device ...

  [Regression Potential]
  Low. Add new ID for a new device.

  == original bug description ==

  New ID available in
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=3c3caae4cd6e122472efcf64759ff6392fb6bce2

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

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

[Kernel-packages] [Bug 1856642] Re: Add new PCH ID for the Intel Comet Lake -H variant

[You-Sheng Yang]

https://lists.ubuntu.com/archives/kernel-team/2019-December/106418.html

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

Title:
  Add new PCH ID for the Intel Comet Lake -H variant

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

Bug description:
  New ID available in
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=3c3caae4cd6e122472efcf64759ff6392fb6bce2

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

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

[Kernel-packages] [Bug 1848340] Re: Lenovo ThinkPad e580 touchpad and trackpoint stopped working lately

[Kai-Heng Feng]

Is this issue still present?

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

Title:
  Lenovo ThinkPad e580 touchpad and trackpoint stopped working lately

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The device isn't listed in xinput nor devices list from
  /proc/bus/input/devices. External mouse works as intended.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: linux-image-5.0.0-32-generic 5.0.0-32.34
  ProcVersionSignature: Ubuntu 5.0.0-32.34-generic 5.0.21
  Uname: Linux 5.0.0-32-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  spurlos3258 F pulseaudio
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Wed Oct 16 15:50:52 2019
  InstallationDate: Installed on 2018-09-20 (390 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: LENOVO 20KS001QRT
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-32-generic 
root=UUID=a98572ba-317f-4569-b9cf-49ae45dd9308 ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-32-generic N/A
   linux-backports-modules-5.0.0-32-generic  N/A
   linux-firmware1.178.3
  SourcePackage: linux
  UpgradeStatus: Upgraded to disco on 2019-04-19 (180 days ago)
  dmi.bios.date: 06/14/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R0PET42W (1.19 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20KS001QRT
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrR0PET42W(1.19):bd06/14/2018:svnLENOVO:pn20KS001QRT:pvrThinkPadE580:rvnLENOVO:rn20KS001QRT:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad E580
  dmi.product.name: 20KS001QRT
  dmi.product.sku: LENOVO_MT_20KS_BU_Think_FM_ThinkPad E580
  dmi.product.version: ThinkPad E580
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1849830] Re: usb_set_interface failed (-110) when connecting a videoconference peripheral

[Kai-Heng Feng]

Can you please attach dmesg when it's work on laptop?

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

Title:
  usb_set_interface failed (-110) when connecting a videoconference
  peripheral

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The VideConference peripheral is a LogiGroup with camera, micro and
  audio. Camera works fine, but micro and audio fails. The LogiGroup
  system is connected using a single USB port. In other Linux laptop, it
  works fine

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: linux-image-5.3.0-19-generic 5.3.0-19.20
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC1D0p:   carlos 1859 F...m pulseaudio
   /dev/snd/controlC0:  carlos 1859 F pulseaudio
  CurrentDesktop: KDE
  Date: Fri Oct 25 15:01:12 2019
  InstallationDate: Installed on 2019-10-24 (0 days ago)
  InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: Dell Inc. XPS 13 7390
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-19-generic 
root=/dev/mapper/vgkubuntu-root ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Daemon 
not responding.
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-19-generic N/A
   linux-backports-modules-5.3.0-19-generic  N/A
   linux-firmware1.183.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/23/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.1.3
  dmi.board.name: 0G2D0W
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.1.3:bd08/23/2019:svnDellInc.:pnXPS137390:pvr:rvnDellInc.:rn0G2D0W:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 7390
  dmi.product.sku: 0962
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1854432] Re: Fix MST support on Ice Lake

[Kai-Heng Feng]

** Changed in: linux (Ubuntu Focal)
   Status: In Progress => Fix Released

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

Title:
  Fix MST support on Ice Lake

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem-osp1 package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Won't Fix
Status in linux-oem-osp1 source package in Bionic:
  Fix Committed
Status in linux source package in Eoan:
  Fix Committed
Status in linux-oem-osp1 source package in Eoan:
  Won't Fix
Status in linux source package in Focal:
  Fix Released
Status in linux-oem-osp1 source package in Focal:
  Invalid

Bug description:
  [Impact]
  Some HDMI and DP doesn't count as external monitor on ICL MST.

  [Fix]
  Fix external port MST check on Ice Lake.

  [Test]
  DP and HDMI ports can only mirror display.
  After applying this patch bot DP and HDMI ports can drive its own external 
display.

  [Regression Potential]
  Low. This fix targets Gen 11 and Gen 12 Intel graphics, older systems are 
unaffected.

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

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

[Kernel-packages] [Bug 1856507] Re: [nvidia] Login screen doesn't show up after installing the Nvidia driver, on a desktop with only an Nvidia GPU

[Daniel van Vugt]

Here's an idea:

Please reinstall the Nvidia driver, reproduce the bug, then revert to
nouveau again.

Assuming the problem with the Nvidia driver was the _previous_ boot:

  journalctl -b-1 > prevboot.txt

and then attach the file prevboot.txt


** Summary changed:

- [nvidia] Login screen doesn't show up after installing the Nvidia driver
+ [nvidia] Login screen doesn't show up after installing the Nvidia driver, on 
a desktop with only an Nvidia GPU

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

Title:
  [nvidia] Login screen doesn't show up after installing the Nvidia
  driver, on a desktop with only an Nvidia GPU

Status in gdm3 package in Ubuntu:
  Incomplete
Status in nvidia-graphics-drivers-435 package in Ubuntu:
  Incomplete

Bug description:
  Attempting to boot after installing nvidia-driver-435, the login
  screen does not show up.

  I tried editing /etc/gdm3/custom.conf and uncommenting the line:

#WaylandEnable=false

  And then rebooting. No apparent change. Still no login screen.

  Screenshot attached.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: nvidia-driver-435 435.21-0ubuntu2
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  Uname: Linux 5.3.0-24-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Dec 16 10:46:58 2019
  InstallationDate: Installed on 2010-10-12 (3351 days ago)
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
  SourcePackage: nvidia-graphics-drivers-435
  UpgradeStatus: Upgraded to eoan on 2019-10-23 (53 days ago)

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

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

[Kernel-packages] [Bug 1848108] Re: [amdgpu] Screen Glitching & Kernel Panic

[Kai-Heng Feng]

Please file an upstream bug to let AMDGPU maintainers know.

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

Title:
  [amdgpu] Screen Glitching & Kernel Panic

Status in linux package in Ubuntu:
  Confirmed
Status in xserver-xorg-video-amdgpu package in Ubuntu:
  New

Bug description:
  I've recently updated to Eoan, but it seems like some nasty bugs came
  with it, particularly from the amdgpu package.

  It started with visual glitches but it would occasionally freeze the
  screen with whatever playing in the background and require me to hard-
  shutdown to escape. Attached is an abridged `journalctl -b -1` showing
  the lines were the kernal panic occurred. I'll probably attach more as
  they occur and if it's not redundant.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
  Uname: Linux 5.3.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  CompositorRunning: None
  Date: Mon Oct 14 21:27:34 2019
  DistUpgraded: 2019-10-13 05:03:20,327 DEBUG entry '# deb 
http://linux.teamviewer.com/deb stable main # disabled on upgrade to eoan' was 
disabled (unknown mirror)
  DistroCodename: eoan
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: Very infrequently
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / 
Radeon Vega Mobile Series] [1002:15dd] (rev c3) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Raven Ridge [Radeon Vega Series / Radeon Vega Mobile 
Series] [17aa:506f]
  InstallationDate: Installed on 2019-03-22 (206 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  Lsusb:
   Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 003 Device 003: ID 13d3:56a6 IMC Networks Integrated Camera
   Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 20KVCTO1WW
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-18-generic 
root=/dev/mapper/ubuntu--vg-root ro DEFAULT quiet splash ivrs_ioapic[32]=00:14.0
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: Upgraded to eoan on 2019-10-13 (1 days ago)
  dmi.bios.date: 12/07/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R0UET68W (1.48 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20KVCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrR0UET68W(1.48):bd12/07/2018:svnLENOVO:pn20KVCTO1WW:pvrThinkPadE585:rvnLENOVO:rn20KVCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad E585
  dmi.product.name: 20KVCTO1WW
  dmi.product.sku: LENOVO_MT_20KV_BU_Think_FM_ThinkPad E585
  dmi.product.version: ThinkPad E585
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.1-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  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/1848108/+subscriptions

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

[Kernel-packages] [Bug 1822394] Re: [Dell BIOSes dated 27 Mar 2019, XPS 9575, Precision 5530 2-in-1] laptop keyboard & touchpad not working at gdm screen after boot

[Kai-Heng Feng]

Mark,

If possible, please do a kernel bisect.

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

Title:
  [Dell BIOSes dated 27 Mar 2019, XPS 9575, Precision 5530 2-in-1]
  laptop keyboard & touchpad not working at gdm screen after boot

Status in libinput package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  On a dell XPS 15 2-in-1 with the latest 1.4.0 bios, my touchpad and keyboard 
are unresponsive at the gdm login screen.  Keyboard works to unlock encrypted 
harddrive before that though.  If I plug in a USB keyboard or activate my 
bluetooth mouse, I can use those to log in, and then after logging in the 
laptop touchpad and keyboard work again.  Logging out of the desktop results
  in the laptop touchpad and keyboard working on the gdm screen.  Did not see
  this behavior before upgrading from 1.2.0 bios to 1.4.0 bios, but also had
  not rebooted in a while, so not sure if bios or package upgrades triggered
  this behavior.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gdm3 3.32.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1
  Uname: Linux 5.0.0-8-generic x86_64
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Mar 29 17:51:00 2019
  InstallationDate: Installed on 2018-09-26 (184 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: gdm3
  UpgradeStatus: Upgraded to disco on 2019-03-11 (18 days ago)

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

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

[Kernel-packages] [Bug 1856642] Re: Add new PCH ID for the Intel Comet Lake -H variant

[You-Sheng Yang]

WIP branches:
* 
https://code.launchpad.net/~vicamo/+git/ubuntu-kernel/+ref/bug-1856642/new-id-06ee-for-cml-pch/disco
* 
https://code.launchpad.net/~vicamo/+git/ubuntu-kernel/+ref/bug-1856642/new-id-06ee-for-cml-pch/eoan
* 
https://code.launchpad.net/~vicamo/+git/ubuntu-kernel/+ref/bug-1856642/new-id-06ee-for-cml-pch/focal
* 
https://code.launchpad.net/~vicamo/+git/ubuntu-kernel/+ref/bug-1856642/new-id-06ee-for-cml-pch/unstable
* 
https://code.launchpad.net/~vicamo/+git/ubuntu-kernel/+ref/bug-1856642/new-id-06ee-for-cml-pch/oem-osp1-bionic

PPA: https://launchpad.net/~vicamo/+archive/ubuntu/ppa-1856642

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

Title:
  Add new PCH ID for the Intel Comet Lake -H variant

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

Bug description:
  New ID available in
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=3c3caae4cd6e122472efcf64759ff6392fb6bce2

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

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

[Kernel-packages] [Bug 1854896] Re: Synaptics TM3336-004 Touchpad Stopped working after update to the latest kernel 4.15.0-72 generic

[ayush]

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

Same issue happening in my laptop after kernel update 4.15.0-72 i have
dell 3542 , i am sure problem in kernel i move to linux mint cause i
face touchpad not working in ubuntu 16.4.6 after updating kernel and now
same happens to linux mint

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

Title:
  Synaptics TM3336-004 Touchpad Stopped working after update to the
  latest kernel 4.15.0-72 generic

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Please see to it, my touchpad all of a sudden stopped working after reboot.
  it happened after updating to the latest kernel 4.15.0-72, i am using linux 
mint 19.2.

  Pointer version: Synaptics TM3336-004

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

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

[Kernel-packages] [Bug 1856507] Re: [nvidia] Login screen doesn't show up after installing the Nvidia driver

[Shahar Or]

Thank you, Daniel. Here it is.

** Attachment added: "lspci -k"
   
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-435/+bug/1856507/+attachment/5313153/+files/lspcik.txt

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

Title:
  [nvidia] Login screen doesn't show up after installing the Nvidia
  driver

Status in gdm3 package in Ubuntu:
  Incomplete
Status in nvidia-graphics-drivers-435 package in Ubuntu:
  Incomplete

Bug description:
  Attempting to boot after installing nvidia-driver-435, the login
  screen does not show up.

  I tried editing /etc/gdm3/custom.conf and uncommenting the line:

#WaylandEnable=false

  And then rebooting. No apparent change. Still no login screen.

  Screenshot attached.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: nvidia-driver-435 435.21-0ubuntu2
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  Uname: Linux 5.3.0-24-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Dec 16 10:46:58 2019
  InstallationDate: Installed on 2010-10-12 (3351 days ago)
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
  SourcePackage: nvidia-graphics-drivers-435
  UpgradeStatus: Upgraded to eoan on 2019-10-23 (53 days ago)

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

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

[Kernel-packages] [Bug 1843774] Re: [CML] New device IDs for CML-U

[You-Sheng Yang]

7ae622c978db has been included in oem-osp1 in bug 1830934, 3c3caae4cd6e
to be cherry-picked in newly created bug 1856642.

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

Title:
  [CML] New device IDs for CML-U

Status in intel:
  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:
  Description
  This task is to identify what new device IDs are required for CML.

  CML PCH-LP: CML-U
  CML PCH-V:

  ControllerKernel Version  Commit  Approved to be
  published Comments
  USB device/xDCI   0x02ee 0x06ee(0x02ee) v5.1-rc3
  (0x06ee) v5.5-rc2 7ae622c978db 3c3caae4cd6e
https://lore.kernel.org/r/20191212093713.60614-1-heikki.kroge...@linux.intel.com

  SMBus 0x02a3  v5.1-rc35cd1c56c42be
  SPI   0x02aa 0x02ab 0x02fbv5.2dd6629073a97 41a918026407
  GPIO  INT34BB It seems the same as for CNL. 
Does it have same IDs? According to dump from Wendy the ID is INT34BB which is 
CNL-LP. Nothing needs to be done here. 
Chap03_CMP-H_Pins_Chap18_GPIO_Automation_v3 1.0.xlsx is in use
  UFS   Is there a CML design with UFS 
this has been only POR for IoTG?
  AHCI  Not Needed supported by Class 
ID.
  XHCI  Not needed supported by Class 
ID.
  eMMC  0x02c4  v5.2-rc1765c59675ab5
  SD Card   0x02f5  v5.2-rc1765c59675ab5

  is in oem (4.15) and up:
  NPK   0x02a6  v5.2e60e9a4b231a
  I²C   0x02c5 0x02c6 0x02e8 0x02e9 0x02ea 0x02eb   v5.2
dd6629073a97https://lkml.org/lkml/2019/4/9/548
  HS-UART   0x02a8 0x02a9 0x02c7v5.2dd6629073a97
https://lkml.org/lkml/2019/4/9/548

  not in oem (4.15) or oem-osp1 (5.0):
  SPI Flash Controller  0x02a4  v5.2e43f53c22a93

  Target Kernel: 5.2
  Target Release: 19.10

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

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

[Kernel-packages] [Bug 1856642] Re: Add new PCH ID for the Intel Comet Lake -H variant

[You-Sheng Yang]

** Also affects: linux (Ubuntu Focal)
   Importance: Undecided
 Assignee: You-Sheng Yang (vicamo)
   Status: Incomplete

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

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

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

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

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

** Changed in: linux-oem-osp1 (Ubuntu Eoan)
   Status: New => Confirmed

** Changed in: linux-oem-osp1 (Ubuntu Focal)
   Status: New => Confirmed

** Changed in: linux (Ubuntu Focal)
   Status: Incomplete => 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/1856642

Title:
  Add new PCH ID for the Intel Comet Lake -H variant

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

Bug description:
  New ID available in
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=3c3caae4cd6e122472efcf64759ff6392fb6bce2

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

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

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

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

Title:
  Add new PCH ID for the Intel Comet Lake -H variant

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

Bug description:
  New ID available in
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=3c3caae4cd6e122472efcf64759ff6392fb6bce2

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

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

[Kernel-packages] [Bug 1856642] [NEW] Add new PCH ID for the Intel Comet Lake -H variant

[You-Sheng Yang]

Public bug reported:

New ID available in
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=3c3caae4cd6e122472efcf64759ff6392fb6bce2

** Affects: linux (Ubuntu)
 Importance: Undecided
 Assignee: You-Sheng Yang (vicamo)
 Status: Triaged

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

** Affects: linux (Ubuntu Bionic)
 Importance: Undecided
 Status: Won't Fix

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

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

** Affects: linux-oem-osp1 (Ubuntu Eoan)
 Importance: Undecided
 Status: Confirmed

** Affects: linux (Ubuntu Focal)
 Importance: Undecided
 Assignee: You-Sheng Yang (vicamo)
 Status: Triaged

** Affects: linux-oem-osp1 (Ubuntu Focal)
 Importance: Undecided
 Status: 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/1856642

Title:
  Add new PCH ID for the Intel Comet Lake -H variant

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

Bug description:
  New ID available in
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=3c3caae4cd6e122472efcf64759ff6392fb6bce2

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

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

[Kernel-packages] [Bug 1843774] Re: [CML] New device IDs for CML-U

[quanxian]

USB device/xDCI 0x02ee 0x06ee(0x02ee) v5.1-rc3
(0x06ee) v5.5-rc2   7ae622c978db 3c3caae4cd6e
https://lore.kernel.org/r/20191212093713.60614-1-heikki.kroge...@linux.intel.com

Make sure this two patches has been cherry picked.

** Description changed:

  Description
  This task is to identify what new device IDs are required for CML.
  
  CML PCH-LP: CML-U
  CML PCH-V:
  
  ControllerKernel Version  Commit  Approved to be
  published Comments
+ USB device/xDCI   0x02ee 0x06ee(0x02ee) v5.1-rc3
+ (0x06ee) v5.5-rc2 7ae622c978db 3c3caae4cd6e
https://lore.kernel.org/r/20191212093713.60614-1-heikki.kroge...@linux.intel.com
+ 
  SMBus 0x02a3  v5.1-rc35cd1c56c42be
  SPI   0x02aa 0x02ab 0x02fbv5.2dd6629073a97 41a918026407
  GPIO  INT34BB It seems the same as for CNL. 
Does it have same IDs? According to dump from Wendy the ID is INT34BB which is 
CNL-LP. Nothing needs to be done here. 
Chap03_CMP-H_Pins_Chap18_GPIO_Automation_v3 1.0.xlsx is in use
  UFS   Is there a CML design with UFS 
this has been only POR for IoTG?
  AHCI  Not Needed supported by Class 
ID.
  XHCI  Not needed supported by Class 
ID.
  eMMC  0x02c4  v5.2-rc1765c59675ab5
  SD Card   0x02f5  v5.2-rc1765c59675ab5
  
  is in oem (4.15) and up:
  NPK   0x02a6  v5.2e60e9a4b231a
  I²C   0x02c5 0x02c6 0x02e8 0x02e9 0x02ea 0x02eb   v5.2
dd6629073a97https://lkml.org/lkml/2019/4/9/548
  HS-UART   0x02a8 0x02a9 0x02c7v5.2dd6629073a97
https://lkml.org/lkml/2019/4/9/548
  
  not in oem (4.15) or oem-osp1 (5.0):
  SPI Flash Controller  0x02a4  v5.2e43f53c22a93
  
  Target Kernel: 5.2
  Target Release: 19.10

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

Title:
  [CML] New device IDs for CML-U

Status in intel:
  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:
  Description
  This task is to identify what new device IDs are required for CML.

  CML PCH-LP: CML-U
  CML PCH-V:

  ControllerKernel Version  Commit  Approved to be
  published Comments
  USB device/xDCI   0x02ee 0x06ee(0x02ee) v5.1-rc3
  (0x06ee) v5.5-rc2 7ae622c978db 3c3caae4cd6e
https://lore.kernel.org/r/20191212093713.60614-1-heikki.kroge...@linux.intel.com

  SMBus 0x02a3  v5.1-rc35cd1c56c42be
  SPI   0x02aa 0x02ab 0x02fbv5.2dd6629073a97 41a918026407
  GPIO  INT34BB It seems the same as for CNL. 
Does it have same IDs? According to dump from Wendy the ID is INT34BB which is 
CNL-LP. Nothing needs to be done here. 
Chap03_CMP-H_Pins_Chap18_GPIO_Automation_v3 1.0.xlsx is in use
  UFS   Is there a CML design with UFS 
this has been only POR for IoTG?
  AHCI  Not Needed supported by Class 
ID.
  XHCI  Not needed supported by Class 
ID.
  eMMC  0x02c4  v5.2-rc1765c59675ab5
  SD Card   0x02f5  v5.2-rc1765c59675ab5

  is in oem (4.15) and up:
  NPK   0x02a6  v5.2e60e9a4b231a
  I²C   0x02c5 0x02c6 0x02e8 0x02e9 0x02ea 0x02eb   v5.2
dd6629073a97https://lkml.org/lkml/2019/4/9/548
  HS-UART   0x02a8 0x02a9 0x02c7v5.2dd6629073a97
https://lkml.org/lkml/2019/4/9/548

  not in oem (4.15) or oem-osp1 (5.0):
  SPI Flash Controller  0x02a4  v5.2e43f53c22a93

  Target Kernel: 5.2
  Target Release: 19.10

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

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

[Kernel-packages] [Bug 1853378] Re: [amdgpu] ryzen 2500u random Xorg freeze

[njklim]

Currently using kernel version 5.4.3 with lightdm as display manager.I
also installed amdgpu pro drivers. I've added idle=nomwait and
iommu=soft to grub. Everything is stable so far.

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

Title:
  [amdgpu] ryzen 2500u random Xorg freeze

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Currently using a Dell Inspiron 3835 with a ryzen 2500u with 8gb of
  ram on a pcie nvme ssd. PC randomly freezes at times. This actually
  occurs on asus x505za also running 2500u.

  I checked the log files and there was this error.
  [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process 
gnome-shell pid 10648 thread gnome-shel:cs0 pid 10654
  [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process 
gnome-shell pid 10648 thread gnome-shel:cs0 pid 10654

  I think it may be a problem with gnome since I was running lubuntu
  before and there's no hang whatsoever when using that.

  Ubuntu 18.04.3 LTS
  Release 18.04

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  Uname: Linux 5.3.12-050312-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Nov 21 07:04:57 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  GpuHangFrequency: Several times a week
  GpuHangReproducibility: Seems to happen randomly
  GpuHangStarted: Since a couple weeks or more
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / 
Radeon Vega Mobile Series] [1002:15dd] (rev c4) (prog-if 00 [VGA controller])
 Subsystem: Dell Vega [Radeon Vega 8 Mobile] [1028:08d7]
  InstallationDate: Installed on 2019-11-19 (1 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  MachineType: Dell Inc. Inspiron 3585
  ProcEnviron:
   LANGUAGE=en_PH:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_PH.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.12-050312-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash idle=nomwait iommu=soft 
pci=nomsi vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/29/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.4.0
  dmi.board.asset.tag: not specified
  dmi.board.name: 0TY9XW
  dmi.board.vendor: Dell Inc.
  dmi.board.version: X01
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 1.4.0
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.4.0:bd05/29/2019:svnDellInc.:pnInspiron3585:pvr1.4.0:rvnDellInc.:rn0TY9XW:rvrX01:cvnDellInc.:ct10:cvr1.4.0:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 3585
  dmi.product.sku: 08D7
  dmi.product.version: 1.4.0
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.100+git1911150630.a39c34~oibaf~b
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0~git1911201930.bcfc9c~oibaf~b
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.0~git1911201930.bcfc9c~oibaf~b
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

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

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

[Kernel-packages] [Bug 1856103] Re: [CML] New device IDs for CMP-V

[quanxian]

** Description changed:

  new device IDs are required for CMP-V, whether they are published or
  not. Once that is clarified, documentations and device drivers need to
  update accordingly.
  
  ControllerIn intel-next   Kernel Version  Commit  Approved to be
  published Comments
- SPI NOR   0xa3a4   
- NPK   0xa3a6   
- HS UART   0xa3a7 0xa3a8 0xa3e6 
- SPI   0xa3a9 0xa3aa
- I²C   0xa3e0 0xa3e1 0xa3e2 0xa3e3  
- SMBus 0xa3a3   
+ GPIO  
+ SPI NOR   0xa3a4
+ NPK   0xa3a6
+ HS UART   0xa3a7 0xa3a8 0xa3e6
+ SPI   0xa3a9 0xa3aa
+ I²C   0xa3e0 0xa3e1 0xa3e2 0xa3e3
+ SMBus 0xa3a3
  
  Target Kernel: 5.5
  Target Release: 20.04

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

Title:
  [CML] New device IDs for CMP-V

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

Bug description:
  new device IDs are required for CMP-V, whether they are published or
  not. Once that is clarified, documentations and device drivers need to
  update accordingly.

  ControllerIn intel-next   Kernel Version  Commit  Approved to be
  published Comments
  GPIO  
  SPI NOR   0xa3a4
  NPK   0xa3a6
  HS UART   0xa3a7 0xa3a8 0xa3e6
  SPI   0xa3a9 0xa3aa
  I²C   0xa3e0 0xa3e1 0xa3e2 0xa3e3
  SMBus 0xa3a3

  Target Kernel: 5.5
  Target Release: 20.04

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

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

[Kernel-packages] [Bug 1856633] Re: My touchpad stop working

[You-Sheng Yang]

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

This duplicates bug 1856499, which has also Synpatics TM2985. The root
cause is probably still bug 1854798.

** This bug has been marked a duplicate of bug 1856499
   Touchpad is not detected after the latest kernel update

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

Title:
  My touchpad stop working

Status in linux package in Ubuntu:
  New

Bug description:
  I followed this

  In case your Touchpad doesn't work at all (No response from the
  Touchpad)

  This is generally a case of a kernel (linux) or xorg bug.

  Execute at a terminal:

  cat /proc/bus/input/devices

  One should see a touchpad device, like:

  I: Bus=0011 Vendor=0002 Product=0007 Version=01b1
  N: Name="SynPS/2 Synaptics TouchPad"
  P: Phys=isa0060/serio2/input0
  S: Sysfs=/devices/platform/i8042/serio2/input/input8
  U: Uniq=
  H: Handlers=mouse2 event8
  B: EV=b
  B: KEY=420 0 7 0 0 0 0 0 0 0 0
  B: ABS=1103 

  If you do not find something like this, then the bug is in the
  linux kernel. Please follow these steps:

  File the bug against the linux package by running ubuntu-bug
  linux.

  Provide the general information.

  Enter the following commands in a terminal:

  cat /proc/bus/input/devices > ~/devices

  Attach ~/devices as separate attachments to your bug report.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-72-generic 4.15.0-72.81
  ProcVersionSignature: Ubuntu 4.15.0-72.81-generic 4.15.18
  Uname: Linux 4.15.0-72-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  efalabrini   1968 F pulseaudio
  CurrentDesktop: MATE
  Date: Mon Dec 16 22:59:30 2019
  HibernationDevice: RESUME=UUID=78dee4f0-4177-42a3-9e3a-18c5562142a9
  InstallationDate: Installed on 2016-08-11 (1222 days ago)
  InstallationMedia: Ubuntu-MATE 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: Dell Inc. Inspiron 11-3157
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-72-generic 
root=UUID=695e60b3-8b9c-4d3c-8646-9f5dbd9323fb ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-72-generic N/A
   linux-backports-modules-4.15.0-72-generic  N/A
   linux-firmware 1.173.13
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/29/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.1.13
  dmi.board.name: 0C9N4H
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.1.13:bd07/29/2015:svnDellInc.:pnInspiron11-3157:pvr1.1.13:rvnDellInc.:rn0C9N4H:rvrA00:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: Inspiron 11-3157
  dmi.product.version: 1.1.13
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1856633] [NEW] My touchpad stop working

[Emiliano Falabrini]

Public bug reported:

I followed this

In case your Touchpad doesn't work at all (No response from the
Touchpad)

This is generally a case of a kernel (linux) or xorg bug.

Execute at a terminal:

cat /proc/bus/input/devices

One should see a touchpad device, like:

I: Bus=0011 Vendor=0002 Product=0007 Version=01b1
N: Name="SynPS/2 Synaptics TouchPad"
P: Phys=isa0060/serio2/input0
S: Sysfs=/devices/platform/i8042/serio2/input/input8
U: Uniq=
H: Handlers=mouse2 event8
B: EV=b
B: KEY=420 0 7 0 0 0 0 0 0 0 0
B: ABS=1103 

If you do not find something like this, then the bug is in the linux
kernel. Please follow these steps:

File the bug against the linux package by running ubuntu-bug
linux.

Provide the general information.

Enter the following commands in a terminal:

cat /proc/bus/input/devices > ~/devices

Attach ~/devices as separate attachments to your bug report.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-72-generic 4.15.0-72.81
ProcVersionSignature: Ubuntu 4.15.0-72.81-generic 4.15.18
Uname: Linux 4.15.0-72-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.9
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  efalabrini   1968 F pulseaudio
CurrentDesktop: MATE
Date: Mon Dec 16 22:59:30 2019
HibernationDevice: RESUME=UUID=78dee4f0-4177-42a3-9e3a-18c5562142a9
InstallationDate: Installed on 2016-08-11 (1222 days ago)
InstallationMedia: Ubuntu-MATE 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
MachineType: Dell Inc. Inspiron 11-3157
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-72-generic 
root=UUID=695e60b3-8b9c-4d3c-8646-9f5dbd9323fb ro quiet splash vt.handoff=1
RelatedPackageVersions:
 linux-restricted-modules-4.15.0-72-generic N/A
 linux-backports-modules-4.15.0-72-generic  N/A
 linux-firmware 1.173.13
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/29/2015
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.1.13
dmi.board.name: 0C9N4H
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: Not Specified
dmi.modalias: 
dmi:bvnDellInc.:bvr1.1.13:bd07/29/2015:svnDellInc.:pnInspiron11-3157:pvr1.1.13:rvnDellInc.:rn0C9N4H:rvrA00:cvnDellInc.:ct8:cvrNotSpecified:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: Inspiron 11-3157
dmi.product.version: 1.1.13
dmi.sys.vendor: Dell Inc.

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


** Tags: amd64 apport-bug bionic

** Attachment added: "devices"
   https://bugs.launchpad.net/bugs/1856633/+attachment/5313113/+files/devices

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

Title:
  My touchpad stop working

Status in linux package in Ubuntu:
  New

Bug description:
  I followed this

  In case your Touchpad doesn't work at all (No response from the
  Touchpad)

  This is generally a case of a kernel (linux) or xorg bug.

  Execute at a terminal:

  cat /proc/bus/input/devices

  One should see a touchpad device, like:

  I: Bus=0011 Vendor=0002 Product=0007 Version=01b1
  N: Name="SynPS/2 Synaptics TouchPad"
  P: Phys=isa0060/serio2/input0
  S: Sysfs=/devices/platform/i8042/serio2/input/input8
  U: Uniq=
  H: Handlers=mouse2 event8
  B: EV=b
  B: KEY=420 0 7 0 0 0 0 0 0 0 0
  B: ABS=1103 

  If you do not find something like this, then the bug is in the
  linux kernel. Please follow these steps:

  File the bug against the linux package by running ubuntu-bug
  linux.

  Provide the general information.

  Enter the following commands in a terminal:

  cat /proc/bus/input/devices > ~/devices

  Attach ~/devices as separate attachments to your bug report.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-72-generic 4.15.0-72.81
  ProcVersionSignature: Ubuntu 4.15.0-72.81-generic 4.15.18
  Uname: Linux 4.15.0-72-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  efalabrini   1968 F pulseaudio
  CurrentDesktop: MATE
  Date: Mon Dec 16 22:59:30 2019
  HibernationDevice: RESUME=UUID=78dee4f0-4177-42a3-9e3a-18c5562142a9
  InstallationDate: Installed on 2016-08-11 (1222 days ago)
  InstallationMedia: Ubuntu-MATE 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: Dell Inc. Inspiron 11-3157
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-72-generic 
root=UUID=695e60b3-8b9c-4d3c-8646-9f5dbd9323fb ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-72-generic N/A
 

[Kernel-packages] [Bug 1853044] Re: 5.3.0-23-generic causes fans to spin when idle

[Dean Henrichsmeyer]

Just to close the loop on this, I used the test kernels and the problem
went away.

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

Title:
  5.3.0-23-generic causes fans to spin when idle

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After upgrading to 5.3.0-23-generic the fans in my machine don't stop
  running. They always sound like something is utilizing CPU - even with
  no applications running after boot.

  If I boot back to 5.3.0-19-generic it's fine.

  My microcode version is reported as 0xd4 and iucode-tool reports:

  iucode-tool: system has processor(s) with signature 0x000506e3

  Let me know if you need anything else.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: linux-image-5.3.0-23-generic 5.3.0-23.25
  ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7
  Uname: Linux 5.3.0-23-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  dean   2898 F pulseaudio
   /dev/snd/pcmC2D0p:   dean   2898 F...m pulseaudio
   /dev/snd/controlC0:  dean   2898 F pulseaudio
   /dev/snd/controlC1:  dean   2898 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Nov 18 13:03:34 2019
  HibernationDevice: RESUME=UUID=55a42c82-50bf-4e75-a133-dbd3aa93611b
  InstallationDate: Installed on 2018-07-24 (482 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180724)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-23-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-23-generic N/A
   linux-backports-modules-5.3.0-23-generic  N/A
   linux-firmware1.183.2
  SourcePackage: linux
  UpgradeStatus: Upgraded to eoan on 2019-07-19 (121 days ago)
  dmi.bios.date: 05/16/2018
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: KYSKLi70.86A.0055.2018.0516.1629
  dmi.board.name: NUC6i7KYB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: H90766-406
  dmi.chassis.type: 3
  dmi.chassis.vendor: Intel Corporation
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrKYSKLi70.86A.0055.2018.0516.1629:bd05/16/2018:svn:pn:pvr:rvnIntelCorporation:rnNUC6i7KYB:rvrH90766-406:cvnIntelCorporation:ct3:cvr1.0:

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

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

[Kernel-packages] [Bug 1853567] Re: Bluetooth keyboard after upgrade consumes rapidly battery

[Daniel van Vugt]

You *might* find details of your Bluetooth battery in the app "Power
Statistics".

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

Title:
  Bluetooth keyboard after upgrade consumes rapidly battery

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  After upgrading from ubuntu 19.04 to 19.10 the bluetooth keyboard Logitech 
K810 is consuming faster the battery. Now it needs recharging almost every 
week, while with 19.04 it was every couple of months.
  My impression is that either the kernel or the bluez is pinging more often 
the keyboard and doesn't let it sleep when not in use.

  There was a similar problem some years ago and with an updated kernel
  it was fixed.

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

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

[Kernel-packages] [Bug 1854796] Re: bionic/linux-snapdragon: 4.15.0-1070.77 -proposed tracker

[Ubuntu Kernel Bot]

** Changed in: kernel-sru-workflow/automated-testing
   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: 1854819
  packages:
main: linux-snapdragon
meta: linux-meta-snapdragon
  phase: Testing
  phase-changed: Wednesday, 04. December 2019 15:11 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   automated-testing: Ongoing -- testing in progress
certification-testing: Ongoing -- testing in progress
security-signoff: Stalled -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
bionic/linux-snapdragon/dragonboard-kernel: bug 1854795
  variant: debs

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

Title:
  bionic/linux-snapdragon: 4.15.0-1070.77 -proposed tracker

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

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

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

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1854819
  packages:
main: linux-snapdragon
meta: linux-meta-snapdragon
  phase: Testing
  phase-changed: Wednesday, 04. December 2019 15:11 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
certification-testing: Ongoing -- testing in progress
security-signoff: Stalled -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
bionic/linux-snapdragon/dragonboard-kernel: bug 1854795
  variant: debs

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

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

[Kernel-packages] [Bug 1854824] Re: xenial/linux-aws: 4.4.0-1100.111 -proposed tracker

[Ubuntu Kernel Bot]

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

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1854835
  packages:
main: linux-aws
meta: linux-meta-aws
  phase: Testing
  phase-changed: Wednesday, 04. December 2019 16:11 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   automated-testing: Stalled -- testing FAILED
regression-testing: Ongoing -- testing in progress
security-signoff: Stalled -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
xenial/linux-aws/aws-kernel: bug 1854823
  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/1854824

Title:
  xenial/linux-aws: 4.4.0-1100.111 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  In Progress
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow verification-testing series:
  In Progress
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 --
  boot-testing-requested: true
  kernel-stable-master-bug: 1854835
  packages:
main: linux-aws
meta: linux-meta-aws
  phase: Testing
  phase-changed: Wednesday, 04. December 2019 16:11 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
regression-testing: Ongoing -- testing in progress
security-signoff: Stalled -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
xenial/linux-aws/aws-kernel: bug 1854823
  variant: debs

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

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

[Kernel-packages] [Bug 1856605] Re: [linux-azure] Ubuntu 16.04 + INFINIBAND-OPEN-MPI-2VM

[Launchpad Bug Tracker]

Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  [linux-azure] Ubuntu 16.04 + INFINIBAND-OPEN-MPI-2VM

Status in linux-azure package in Ubuntu:
  Confirmed

Bug description:
  We ran an RDMA test case against gallery image Ubuntu 16.04 (with
  proposed kernel), and found the below issue.  The kernel prior to
  proposed does not exhibit this bug, so it is a regression:

  The issue is when ibv_devinfo is run, we get the below info:

  ibv_devinfo
  libibverbs: Warning: no userspace device-specific driver found for 
/sys/class/infiniband_verbs/uverbs0
  No IB devices found
   
  ibv_devices
  libibverbs: Warning: no userspace device-specific driver found for 
/sys/class/infiniband_verbs/uverbs0
  device node GUID
  --  
   
  Ibstat works as expected
  CA 'mlx5_0'
  CA type: MT4120
  Number of ports: 1
  Firmware version: 16.23.1020
  Hardware version: 0
  Node GUID: 0x00155dfffe33ff49
  System image GUID: 0x506b4b0300f521ec
  Port 1:
  State: Active
  Physical state: LinkUp
  Rate: 100
  Base lid: 713
  LMC: 0
  SM lid: 16
  Capability mask: 0x2651ec48
  Port GUID: 0x00155dfffd33ff49
  Link layer: InfiniBand


  This Family exhibits the bug, with a subsystem of MT28800:
  lspci -v|egrep 'Mel|mlx'
  0002:00:02.0 Infiniband controller: Mellanox Technologies MT27800 Family 
[ConnectX-5 Virtual Function]
  Subsystem: Mellanox Technologies MT28800 Family [ConnectX-5 Virtual 
Function]
  Kernel driver in use: mlx5_core
  Kernel modules: mlx5_core

   
  This issue does not occur with Ubuntu 18.04, which has a different 
Subsystem(MT27800):
  lspci -v|egrep 'Mel|mlx'
  0002:00:02.0 Infiniband controller: Mellanox Technologies MT27800 Family 
[ConnectX-5 Virtual Function]
  Subsystem: Mellanox Technologies MT27800 Family [ConnectX-5 Virtual 
Function]
  Kernel driver in use: mlx5_core
  Kernel modules: mlx5_core

  If we could, we would like to move to rmda-core to version 22 or
  higher.

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

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

[Kernel-packages] [Bug 1854774] Re: bionic/linux-gcp: 5.0.0-1027.28~18.04.1 -proposed tracker

[Ubuntu Kernel Bot]

** Changed in: kernel-sru-workflow/regression-testing
   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: 1854777
  packages:
lrm: linux-restricted-modules-gcp
main: linux-gcp
meta: linux-meta-gcp
signed: linux-signed-gcp
  phase: Testing
  phase-changed: Thursday, 05. December 2019 12:52 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Stalled -- testing FAILED
-   regression-testing: Ongoing -- testing in progress
security-signoff: Stalled -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
bionic/linux-gcp/gcp-kernel: bug 1854773
  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/1854774

Title:
  bionic/linux-gcp: 5.0.0-1027.28~18.04.1 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-lrm series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow verification-testing series:
  In Progress
Status in linux-gcp package in Ubuntu:
  Invalid
Status in linux-gcp 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: 1854777
  packages:
lrm: linux-restricted-modules-gcp
main: linux-gcp
meta: linux-meta-gcp
signed: linux-signed-gcp
  phase: Testing
  phase-changed: Thursday, 05. December 2019 12:52 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Stalled -- testing FAILED
security-signoff: Stalled -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
bionic/linux-gcp/gcp-kernel: bug 1854773
  variant: debs

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

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

[Kernel-packages] [Bug 1854774] Re: bionic/linux-gcp: 5.0.0-1027.28~18.04.1 -proposed tracker

[Sean Feole]

** Tags added: regression-testing-passed

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

Title:
  bionic/linux-gcp: 5.0.0-1027.28~18.04.1 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-lrm series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow verification-testing series:
  In Progress
Status in linux-gcp package in Ubuntu:
  Invalid
Status in linux-gcp 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: 1854777
  packages:
lrm: linux-restricted-modules-gcp
main: linux-gcp
meta: linux-meta-gcp
signed: linux-signed-gcp
  phase: Testing
  phase-changed: Thursday, 05. December 2019 12:52 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Stalled -- testing FAILED
security-signoff: Stalled -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
bionic/linux-gcp/gcp-kernel: bug 1854773
  variant: debs

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

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

[Kernel-packages] [Bug 1854788] Re: disco/linux: 5.0.0-38.41 -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
  bugs-spammed: true
  packages:
lrm: linux-restricted-modules
main: linux
meta: linux-meta
signed: linux-signed
  phase: Testing
  phase-changed: Tuesday, 03. December 2019 15:42 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
security-signoff: Stalled -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
bionic/linux-bluefield: bug 1854787
bionic/linux-hwe: bug 1854785
-   bionic/linux-oem-osp1: bug 1854786, bug 1856522
+   bionic/linux-oem-osp1: bug 1856522
disco/linux-aws: bug 1854768
disco/linux-azure: bug 1854771
disco/linux-gcp: bug 1854777
disco/linux-kvm: bug 1854778
disco/linux-oracle: bug 1854781
disco/linux-raspi2: bug 1854766
disco/linux-snapdragon: bug 1854784
unknown/unknown: bug 1854781
  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/1854788

Title:
  disco/linux: 5.0.0-38.41 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Fix Released
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-lrm series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow verification-testing series:
  In Progress
Status in linux package in Ubuntu:
  Invalid
Status in linux 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
  bugs-spammed: true
  packages:
lrm: linux-restricted-modules
main: linux
meta: linux-meta
signed: linux-signed
  phase: Testing
  phase-changed: Tuesday, 03. December 2019 15:42 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
security-signoff: Stalled -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
bionic/linux-bluefield: bug 1854787
bionic/linux-hwe: bug 1854785
bionic/linux-oem-osp1: bug 1856522
disco/linux-aws: bug 1854768
disco/linux-azure: bug 1854771
disco/linux-gcp: bug 1854777
disco/linux-kvm: bug 1854778
disco/linux-oracle: bug 1854781
disco/linux-raspi2: bug 1854766
disco/linux-snapdragon: bug 1854784
unknown/unknown: bug 1854781
  variant: debs

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

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

[Kernel-packages] [Bug 1856407] Re: nvidia-435 is in eoan, linux-restricted-modules only builds against 430, ubiquity gives me the self-signed modules experience instead of using the Canonical-signed

[Launchpad Bug Tracker]

Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: ubuntu-drivers-common (Ubuntu Eoan)
   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/1856407

Title:
  nvidia-435 is in eoan, linux-restricted-modules only builds against
  430, ubiquity gives me the self-signed modules experience instead of
  using the Canonical-signed modules

Status in linux package in Ubuntu:
  Invalid
Status in linux-restricted-modules package in Ubuntu:
  Invalid
Status in nvidia-graphics-drivers-435 package in Ubuntu:
  Confirmed
Status in ubuntu-drivers-common package in Ubuntu:
  Confirmed
Status in linux source package in Eoan:
  In Progress
Status in linux-restricted-modules source package in Eoan:
  In Progress
Status in nvidia-graphics-drivers-435 source package in Eoan:
  Confirmed
Status in ubuntu-drivers-common source package in Eoan:
  Confirmed

Bug description:
  The linux-restricted-modules package exists so that users who install
  the nvidia drivers can get known-good, signed modules instead of
  having to locally self-sign and enroll a signing key through MOK.  But
  lrm in eoan is only building driver packages for nvidia 390 and 430,
  and nvidia 435 is present in eoan.

  So on a new Ubuntu 19.10 install, ubuntu-drivers is picking 435 as the
  newest driver instead of using the signed 430 driver.

  We should never allow the archive to get into this situation.  We
  should be enforcing that any version of the nvidia driver that we
  expect ubuntu-drivers to install by default on any hardware is
  integrated into linux-restricted-modules, and we should ensure that
  ubuntu-drivers always prefers the signed drivers over other options.

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

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

[Kernel-packages] [Bug 1856407] Re: nvidia-435 is in eoan, linux-restricted-modules only builds against 430, ubiquity gives me the self-signed modules experience instead of using the Canonical-signed

[Launchpad Bug Tracker]

Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: nvidia-graphics-drivers-435 (Ubuntu Eoan)
   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/1856407

Title:
  nvidia-435 is in eoan, linux-restricted-modules only builds against
  430, ubiquity gives me the self-signed modules experience instead of
  using the Canonical-signed modules

Status in linux package in Ubuntu:
  Invalid
Status in linux-restricted-modules package in Ubuntu:
  Invalid
Status in nvidia-graphics-drivers-435 package in Ubuntu:
  Confirmed
Status in ubuntu-drivers-common package in Ubuntu:
  Confirmed
Status in linux source package in Eoan:
  In Progress
Status in linux-restricted-modules source package in Eoan:
  In Progress
Status in nvidia-graphics-drivers-435 source package in Eoan:
  Confirmed
Status in ubuntu-drivers-common source package in Eoan:
  Confirmed

Bug description:
  The linux-restricted-modules package exists so that users who install
  the nvidia drivers can get known-good, signed modules instead of
  having to locally self-sign and enroll a signing key through MOK.  But
  lrm in eoan is only building driver packages for nvidia 390 and 430,
  and nvidia 435 is present in eoan.

  So on a new Ubuntu 19.10 install, ubuntu-drivers is picking 435 as the
  newest driver instead of using the signed 430 driver.

  We should never allow the archive to get into this situation.  We
  should be enforcing that any version of the nvidia driver that we
  expect ubuntu-drivers to install by default on any hardware is
  integrated into linux-restricted-modules, and we should ensure that
  ubuntu-drivers always prefers the signed drivers over other options.

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

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

[Kernel-packages] [Bug 1856407] Re: nvidia-435 is in eoan, linux-restricted-modules only builds against 430, ubiquity gives me the self-signed modules experience instead of using the Canonical-signed

[Launchpad Bug Tracker]

Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: nvidia-graphics-drivers-435 (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/1856407

Title:
  nvidia-435 is in eoan, linux-restricted-modules only builds against
  430, ubiquity gives me the self-signed modules experience instead of
  using the Canonical-signed modules

Status in linux package in Ubuntu:
  Invalid
Status in linux-restricted-modules package in Ubuntu:
  Invalid
Status in nvidia-graphics-drivers-435 package in Ubuntu:
  Confirmed
Status in ubuntu-drivers-common package in Ubuntu:
  Confirmed
Status in linux source package in Eoan:
  In Progress
Status in linux-restricted-modules source package in Eoan:
  In Progress
Status in nvidia-graphics-drivers-435 source package in Eoan:
  Confirmed
Status in ubuntu-drivers-common source package in Eoan:
  Confirmed

Bug description:
  The linux-restricted-modules package exists so that users who install
  the nvidia drivers can get known-good, signed modules instead of
  having to locally self-sign and enroll a signing key through MOK.  But
  lrm in eoan is only building driver packages for nvidia 390 and 430,
  and nvidia 435 is present in eoan.

  So on a new Ubuntu 19.10 install, ubuntu-drivers is picking 435 as the
  newest driver instead of using the signed 430 driver.

  We should never allow the archive to get into this situation.  We
  should be enforcing that any version of the nvidia driver that we
  expect ubuntu-drivers to install by default on any hardware is
  integrated into linux-restricted-modules, and we should ensure that
  ubuntu-drivers always prefers the signed drivers over other options.

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

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

[Kernel-packages] [Bug 1856407] Re: nvidia-435 is in eoan, linux-restricted-modules only builds against 430, ubiquity gives me the self-signed modules experience instead of using the Canonical-signed

[Launchpad Bug Tracker]

Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: ubuntu-drivers-common (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/1856407

Title:
  nvidia-435 is in eoan, linux-restricted-modules only builds against
  430, ubiquity gives me the self-signed modules experience instead of
  using the Canonical-signed modules

Status in linux package in Ubuntu:
  Invalid
Status in linux-restricted-modules package in Ubuntu:
  Invalid
Status in nvidia-graphics-drivers-435 package in Ubuntu:
  Confirmed
Status in ubuntu-drivers-common package in Ubuntu:
  Confirmed
Status in linux source package in Eoan:
  In Progress
Status in linux-restricted-modules source package in Eoan:
  In Progress
Status in nvidia-graphics-drivers-435 source package in Eoan:
  Confirmed
Status in ubuntu-drivers-common source package in Eoan:
  Confirmed

Bug description:
  The linux-restricted-modules package exists so that users who install
  the nvidia drivers can get known-good, signed modules instead of
  having to locally self-sign and enroll a signing key through MOK.  But
  lrm in eoan is only building driver packages for nvidia 390 and 430,
  and nvidia 435 is present in eoan.

  So on a new Ubuntu 19.10 install, ubuntu-drivers is picking 435 as the
  newest driver instead of using the signed 430 driver.

  We should never allow the archive to get into this situation.  We
  should be enforcing that any version of the nvidia driver that we
  expect ubuntu-drivers to install by default on any hardware is
  integrated into linux-restricted-modules, and we should ensure that
  ubuntu-drivers always prefers the signed drivers over other options.

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

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

[Kernel-packages] [Bug 1783881] Re: ltp-syscalls: msgstress03 fails because systemd limits number of processes

[Sean Feole]

** Tags added: azure

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

** No longer affects: linux (Ubuntu Cosmic)

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

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

** Also affects: linux-azure (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/1783881

Title:
  ltp-syscalls: msgstress03 fails because systemd limits number of
  processes

Status in ubuntu-kernel-tests:
  Triaged
Status in linux package in Ubuntu:
  Incomplete
Status in linux-azure package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  Incomplete
Status in linux source package in Xenial:
  New
Status in linux-azure source package in Xenial:
  New
Status in systemd source package in Xenial:
  New
Status in linux source package in Bionic:
  New
Status in linux-azure source package in Bionic:
  New
Status in systemd source package in Bionic:
  New

Bug description:
  As systemd limits the number of processes, this test will fail because
  it can't fork enough processes. That is limited to when the test is
  run after logging as user 1000, then running sudo. I guess that
  logging as root may not cause this to happen.

  # ./testcases/bin/msgstress03 
  Fork failed (may be OK if under stress)
  Fork failed (may be OK if under stress)
  msgstress031  TFAIL  :  msgstress03.c:157:  Fork failed (may be OK if 
under stress)
  #

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

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

[Kernel-packages] [Bug 1830360] Re: cpuset_load_balance from controller test suite in LTP failed

[Sean Feole]

** Changed in: ubuntu-kernel-tests
   Status: New => Triaged

** Tags added: azure

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

Title:
  cpuset_load_balance from controller test suite in LTP failed

Status in ubuntu-kernel-tests:
  Triaged
Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Bionic:
  New
Status in linux source package in Disco:
  New

Bug description:
  Issue found on Disco with node glameow:
   startup='Fri May 24 10:24:55 2019'
   cpuset_load_balance 1 TINFO: general group load balance test
   cpuset_load_balance 1 TINFO: root group info:
   cpuset_load_balance 1 TINFO:  sched load balance: 0
   cpuset_load_balance 1 TINFO: general group info:
   cpuset_load_balance 1 TINFO:  cpus: -
   cpuset_load_balance 1 TINFO:  sched load balance: 1
   cpuset_load_balance 1 TFAIL: load balance test failed.
   cpuset_load_balance 3 TINFO: general group load balance test
   cpuset_load_balance 3 TINFO: root group info:
   cpuset_load_balance 3 TINFO:  sched load balance: 0
   cpuset_load_balance 3 TINFO: general group info:
   cpuset_load_balance 3 TINFO:  cpus: 1
   cpuset_load_balance 3 TINFO:  sched load balance: 0
   cpuset_load_balance 3 TFAIL: load balance test failed.
   cpuset_load_balance 5 TINFO: general group load balance test
   cpuset_load_balance 5 TINFO: root group info:
   cpuset_load_balance 5 TINFO:  sched load balance: 1
   cpuset_load_balance 5 TINFO: general group info:
   cpuset_load_balance 5 TINFO:  cpus: -
   cpuset_load_balance 5 TINFO:  sched load balance: 1
   cpuset_load_balance 5 TFAIL: load balance test failed.
   cpuset_load_balance 7 TINFO: general group load balance test
   cpuset_load_balance 7 TINFO: root group info:
   cpuset_load_balance 7 TINFO:  sched load balance: 1
   cpuset_load_balance 7 TINFO: general group info:
   cpuset_load_balance 7 TINFO:  cpus: 1
   cpuset_load_balance 7 TINFO:  sched load balance: 1
   cpuset_load_balance 7 TFAIL: load balance test failed.
   cpuset_load_balance 9 TINFO: general group load balance test
   cpuset_load_balance 9 TINFO: root group info:
   cpuset_load_balance 9 TINFO:  sched load balance: 0
   cpuset_load_balance 9 TINFO: general group info:
   cpuset_load_balance 9 TINFO:  cpus: 1,2
   cpuset_load_balance 9 TINFO:  sched load balance: 0
   cpuset_load_balance 9 TFAIL: load balance test failed.
   cpuset_load_balance 11 TINFO: general group load balance test
   cpuset_load_balance 11 TINFO: root group info:
   cpuset_load_balance 11 TINFO:  sched load balance: 0
   cpuset_load_balance 11 TINFO: general group info:
   cpuset_load_balance 11 TINFO:  cpus: 1,2
   cpuset_load_balance 11 TINFO:  sched load balance: 1
   cpuset_load_balance 11 TFAIL: load balance test failed.
   cpuset_load_balance 13 TINFO: general group load balance test
   cpuset_load_balance 13 TINFO: root group info:
   cpuset_load_balance 13 TINFO:  sched load balance: 0
   cpuset_load_balance 13 TINFO: general group info:
   cpuset_load_balance 13 TINFO:  cpus: 
0,1,2,3,4,5,6,7,8,9,10,11,12,13,14,15,16,17,18,19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39
   cpuset_load_balance 13 TINFO:  sched load balance: 1
   cpuset_load_balance 13 TFAIL: load balance test failed.
   cpuset_load_balance 15 TINFO: general group load balance test
   cpuset_load_balance 15 TINFO: root group info:
   cpuset_load_balance 15 TINFO:  sched load balance: 0
   cpuset_load_balance 15 TINFO: general group1 info:
   cpuset_load_balance 15 TINFO:  cpus: 1
   cpuset_load_balance 15 TINFO:  sched load balance: 1
   cpuset_load_balance 15 TINFO: general group2 info:
   cpuset_load_balance 15 TINFO:  cpus: 0
   cpuset_load_balance 15 TINFO:  sched load balance: 1
   cpuset_load_balance 15 TINFO: CPU hotplug: none
   cpuset_load_balance 15 TFAIL: load balance test failed.
   cpuset_load_balance 17 TINFO: general group load balance test
   cpuset_load_balance 17 TINFO: root group info:
   cpuset_load_balance 17 TINFO:  sched load balance: 0
   cpuset_load_balance 17 TINFO: general group1 info:
   cpuset_load_balance 17 TINFO:  cpus: 1,2
   cpuset_load_balance 17 TINFO:  sched load balance: 1
   cpuset_load_balance 17 TINFO: general group2 info:
   cpuset_load_balance 17 TINFO:  cpus: 0-3
   cpuset_load_balance 17 TINFO:  sched load balance: 0
   cpuset_load_balance 17 TINFO: CPU hotplug: none
   cpuset_load_balance 17 TFAIL: load balance test failed.
   cpuset_load_balance 19 TINFO: general group load balance test
   cpuset_load_balance 19 TINFO: root group info:
   cpuset_load_balance 19 TINFO:  sched load balance: 0
   cpuset_load_balance 19 TINFO: general group1 info:
   cpuset_load_balance 19 TINFO:  cpus: 1,2
   cpuset_load_balance 19 TINFO:  sched load balance: 1
   

[Kernel-packages] [Bug 1830359] Re: cpuset_base_ops from controller test suite in LTP failed

[Sean Feole]

** Tags added: azure bionic

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

Title:
  cpuset_base_ops from controller test suite in LTP failed

Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in linux-azure package in Ubuntu:
  New
Status in linux source package in Bionic:
  New
Status in linux-azure source package in Bionic:
  New
Status in linux source package in Disco:
  New
Status in linux-azure source package in Disco:
  New

Bug description:
  Issue found on Disco with node glameow:
   startup='Fri May 24 10:23:44 2019'
   cpuset_base_ops 1 TPASS: cpuset.cpus(READONLY): Get the expected string
   cpuset_base_ops 3 TPASS: cpuset.mems(READONLY): Get the expected string
   cpuset_base_ops 5 TPASS: cpuset.memory_pressure(READONLY): Get the expected 
string
   cpuset_base_ops 7 TPASS: cpuset.cpus: Get the expected string
   cpuset_base_ops 9 TPASS: cpuset.cpus: Get the expected string
   cpuset_base_ops 11 TPASS: cpuset.cpus: Get the expected string
   cpuset_base_ops 13 TPASS: cpuset.cpus: Get the expected string
   cpuset_base_ops 15 TPASS: cpuset.cpus: Get the expected string
   cpuset_base_ops 17 TPASS: cpuset.cpus: Get the expected string
   cpuset_base_ops 19 TPASS: cpuset.cpus: Get the expected string
   cpuset_base_ops 21 TPASS: cpuset.cpus: Get the expected string
   cpuset_base_ops 23 TPASS: cpuset.cpus: Get the expected string
   cpuset_base_ops 25 TPASS: cpuset.cpus: Get the expected string
   cpuset_base_ops 27 TPASS: cpuset.cpus: Get the expected string
   cpuset_base_ops 29 TPASS: cpuset.cpus: Get the expected string
   cpuset_base_ops 31 TPASS: cpuset.cpus: Get the expected string
   cpuset_base_ops 33 TPASS: cpuset.cpus: Get the expected string
   cpuset_base_ops 35 TPASS: cpuset.cpus: Get the expected string
   cpuset_base_ops 37 TFAIL: cpuset.cpus: Test result -  Expected string - "0"
   cpuset_base_ops 39 TPASS: cpuset.mems: Get the expected string
   cpuset_base_ops 41 TPASS: cpuset.mems: Get the expected string
   cpuset_base_ops 43 TPASS: cpuset.mems: Get the expected string
   cpuset_base_ops 45 TPASS: cpuset.mems: Get the expected string
   cpuset_base_ops 47 TPASS: cpuset.mems: Get the expected string
   cpuset_base_ops 49 TPASS: cpuset.mems: Get the expected string
   cpuset_base_ops 51 TPASS: cpuset.mems: Get the expected string
   cpuset_base_ops 53 TPASS: cpuset.mems: Get the expected string
   cpuset_base_ops 55 TPASS: cpuset.mems: Get the expected string
   cpuset_base_ops 57 TPASS: cpuset.mems: Get the expected string
   cpuset_base_ops 59 TPASS: cpuset.mems: Get the expected string
   cpuset_base_ops 61 TPASS: cpuset.mems: Get the expected string
   cpuset_base_ops 63 TPASS: cpuset.mems: Get the expected string
   cpuset_base_ops 65 TFAIL: cpuset.mems: Test result -  Expected string - "0"
   cpuset_base_ops 67 TPASS: cpuset.cpu_exclusive: Get the expected string
   cpuset_base_ops 69 TPASS: cpuset.cpu_exclusive: Get the expected string
   cpuset_base_ops 71 TPASS: cpuset.cpu_exclusive: Get the expected string
   cpuset_base_ops 73 TPASS: cpuset.cpu_exclusive: Get the expected string
   cpuset_base_ops 75 TPASS: cpuset.cpu_exclusive: Get the expected string
   cpuset_base_ops 77 TPASS: cpuset.mem_exclusive: Get the expected string
   cpuset_base_ops 79 TPASS: cpuset.mem_exclusive: Get the expected string
   cpuset_base_ops 81 TPASS: cpuset.mem_exclusive: Get the expected string
   cpuset_base_ops 83 TPASS: cpuset.mem_exclusive: Get the expected string
   cpuset_base_ops 85 TPASS: cpuset.mem_exclusive: Get the expected string
   cpuset_base_ops 87 TPASS: cpuset.mem_hardwall: Get the expected string
   cpuset_base_ops 89 TPASS: cpuset.mem_hardwall: Get the expected string
   cpuset_base_ops 91 TPASS: cpuset.mem_hardwall: Get the expected string
   cpuset_base_ops 93 TPASS: cpuset.mem_hardwall: Get the expected string
   cpuset_base_ops 95 TPASS: cpuset.mem_hardwall: Get the expected string
   cpuset_base_ops 97 TPASS: cpuset.memory_migrate: Get the expected string
   cpuset_base_ops 99 TPASS: cpuset.memory_migrate: Get the expected string
   cpuset_base_ops 101 TPASS: cpuset.memory_migrate: Get the expected string
   cpuset_base_ops 103 TPASS: cpuset.memory_migrate: Get the expected string
   cpuset_base_ops 105 TPASS: cpuset.memory_migrate: Get the expected string
   cpuset_base_ops 107 TPASS: cpuset.memory_spread_page: Get the expected string
   cpuset_base_ops 109 TPASS: cpuset.memory_spread_page: Get the expected string
   cpuset_base_ops 111 TPASS: cpuset.memory_spread_page: Get the expected string
   cpuset_base_ops 113 TPASS: cpuset.memory_spread_page: Get the expected string
   cpuset_base_ops 115 TPASS: cpuset.memory_spread_page: Get the expected string
   cpuset_base_ops 117 TPASS: cpuset.memory_spread_slab: Get the expected 

[Kernel-packages] [Bug 1854802] Re: bionic/linux-aws: 4.15.0-1057.59 -proposed tracker

[Ubuntu Kernel Bot]

** Changed in: kernel-sru-workflow/automated-testing
   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: 1854819
  packages:
lrm: linux-restricted-modules-aws
main: linux-aws
meta: linux-meta-aws
  phase: Testing
  phase-changed: Wednesday, 04. December 2019 23:21 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   automated-testing: Ongoing -- testing in progress
security-signoff: Stalled -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
bionic/linux-aws-fips: bug 1854800
bionic/linux-aws/aws-kernel: bug 1854799
xenial/linux-aws-hwe: bug 1854801
  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/1854802

Title:
  bionic/linux-aws: 4.15.0-1057.59 -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 promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow verification-testing series:
  In Progress
Status in linux-aws package in Ubuntu:
  Invalid
Status in linux-aws 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: 1854819
  packages:
lrm: linux-restricted-modules-aws
main: linux-aws
meta: linux-meta-aws
  phase: Testing
  phase-changed: Wednesday, 04. December 2019 23:21 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
security-signoff: Stalled -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
bionic/linux-aws-fips: bug 1854800
bionic/linux-aws/aws-kernel: bug 1854799
xenial/linux-aws-hwe: bug 1854801
  variant: debs

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

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

[Kernel-packages] [Bug 1856407] Re: nvidia-435 is in eoan, linux-restricted-modules only builds against 430, ubiquity gives me the self-signed modules experience instead of using the Canonical-signed

[Seth Forshee]

I've got patches to add nvidia-435 to linux/l-r-m for eoan, will need to
upload to a ppa for testing. They should be ready tormorrow.

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

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

** Also affects: linux-restricted-modules (Ubuntu Eoan)
   Importance: Undecided
   Status: New

** Also affects: ubuntu-drivers-common (Ubuntu Eoan)
   Importance: Undecided
   Status: New

** Also affects: nvidia-graphics-drivers-435 (Ubuntu Eoan)
   Importance: Undecided
   Status: New

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

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

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

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

** Changed in: linux (Ubuntu Eoan)
 Assignee: (unassigned) => Seth Forshee (sforshee)

** Changed in: linux-restricted-modules (Ubuntu Eoan)
   Importance: Undecided => High

** Changed in: linux-restricted-modules (Ubuntu Eoan)
   Status: New => In Progress

** Changed in: linux-restricted-modules (Ubuntu Eoan)
 Assignee: (unassigned) => Seth Forshee (sforshee)

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

Title:
  nvidia-435 is in eoan, linux-restricted-modules only builds against
  430, ubiquity gives me the self-signed modules experience instead of
  using the Canonical-signed modules

Status in linux package in Ubuntu:
  Invalid
Status in linux-restricted-modules package in Ubuntu:
  Invalid
Status in nvidia-graphics-drivers-435 package in Ubuntu:
  New
Status in ubuntu-drivers-common package in Ubuntu:
  New
Status in linux source package in Eoan:
  In Progress
Status in linux-restricted-modules source package in Eoan:
  In Progress
Status in nvidia-graphics-drivers-435 source package in Eoan:
  New
Status in ubuntu-drivers-common source package in Eoan:
  New

Bug description:
  The linux-restricted-modules package exists so that users who install
  the nvidia drivers can get known-good, signed modules instead of
  having to locally self-sign and enroll a signing key through MOK.  But
  lrm in eoan is only building driver packages for nvidia 390 and 430,
  and nvidia 435 is present in eoan.

  So on a new Ubuntu 19.10 install, ubuntu-drivers is picking 435 as the
  newest driver instead of using the signed 430 driver.

  We should never allow the archive to get into this situation.  We
  should be enforcing that any version of the nvidia driver that we
  expect ubuntu-drivers to install by default on any hardware is
  integrated into linux-restricted-modules, and we should ensure that
  ubuntu-drivers always prefers the signed drivers over other options.

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

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

[Kernel-packages] [Bug 1822394] Re: [Dell BIOSes dated 27 Mar 2019, XPS 9575, Precision 5530 2-in-1] laptop keyboard & touchpad not working at gdm screen after boot

[Mark Haiman]

On a new XPS 15 9575 2-in-1 with BIOS 1.8.1, the symptoms are similar to
comment #24.  At the gdm login screen, the keyboard doesn't work at
first but is OK after 20-30 seconds. The touchpad is not affected.  The
Linux 4.15 kernel is not affected but later ones are.  I tried it with
4.18, 5.0 and 5.3 kernels.  I am running Mint 19.2, which uses the
Ubuntu kernels.

If I boot in recovery mode, the keyboard works on the recovery mode menu.  If I 
then exit to normal boot, the unresponsive keyboard recurs.  However, the 
elapsed time until it starts working
again is from the initial boot.  That is, if I wait 30 seconds in recovery mode 
before exiting to normal boot, the keyboard will then be working at the gdm 
screen.

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

Title:
  [Dell BIOSes dated 27 Mar 2019, XPS 9575, Precision 5530 2-in-1]
  laptop keyboard & touchpad not working at gdm screen after boot

Status in libinput package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  On a dell XPS 15 2-in-1 with the latest 1.4.0 bios, my touchpad and keyboard 
are unresponsive at the gdm login screen.  Keyboard works to unlock encrypted 
harddrive before that though.  If I plug in a USB keyboard or activate my 
bluetooth mouse, I can use those to log in, and then after logging in the 
laptop touchpad and keyboard work again.  Logging out of the desktop results
  in the laptop touchpad and keyboard working on the gdm screen.  Did not see
  this behavior before upgrading from 1.2.0 bios to 1.4.0 bios, but also had
  not rebooted in a while, so not sure if bios or package upgrades triggered
  this behavior.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gdm3 3.32.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1
  Uname: Linux 5.0.0-8-generic x86_64
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Mar 29 17:51:00 2019
  InstallationDate: Installed on 2018-09-26 (184 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: gdm3
  UpgradeStatus: Upgraded to disco on 2019-03-11 (18 days ago)

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

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

[Kernel-packages] [Bug 1848108] Re: [amdgpu] Screen Glitching & Kernel Panic

[Jarrod Farrell]

@kaihengfeng

Sorry about the delay. Life being distracting.

But it seems like the issue is /mostly/ fixed in the provided 2019-12-16
build and so far hasn't required me to hard shutdown which is good. What
isn't particularly good is the occasional "freeze" where everything on
screen stops for a few moments. Occasionally during these freezes, items
that were occluded by something appeared in front of it instead, like
desktop icons in front of Firefox with mild graphical glitching on a
terminal window (tiling parts of a window somewhere else). It seems like
the issue occurs when something even mildly graphically intensive
(searching through a large webpage, alt-tabbing, etc.) will cause one of
these freezes. I've even had it happen several times in a row before it
finally recovered.

I did open journalctl -f and noted this:

Dec 16 16:12:29 DarkBolt kernel: [drm:amdgpu_dm_commit_planes.constprop.0 
[amdgpu]] *ERROR* Waiting for fences timed out!
Dec 16 16:12:29 DarkBolt kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* 
ring gfx timeout, but soft recovered
Dec 16 16:12:39 DarkBolt kernel: [drm:amdgpu_dm_commit_planes.constprop.0 
[amdgpu]] *ERROR* Waiting for fences timed out!
Dec 16 16:12:39 DarkBolt kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* 
ring gfx timeout, but soft recovered

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

Title:
  [amdgpu] Screen Glitching & Kernel Panic

Status in linux package in Ubuntu:
  Confirmed
Status in xserver-xorg-video-amdgpu package in Ubuntu:
  New

Bug description:
  I've recently updated to Eoan, but it seems like some nasty bugs came
  with it, particularly from the amdgpu package.

  It started with visual glitches but it would occasionally freeze the
  screen with whatever playing in the background and require me to hard-
  shutdown to escape. Attached is an abridged `journalctl -b -1` showing
  the lines were the kernal panic occurred. I'll probably attach more as
  they occur and if it's not redundant.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
  Uname: Linux 5.3.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  CompositorRunning: None
  Date: Mon Oct 14 21:27:34 2019
  DistUpgraded: 2019-10-13 05:03:20,327 DEBUG entry '# deb 
http://linux.teamviewer.com/deb stable main # disabled on upgrade to eoan' was 
disabled (unknown mirror)
  DistroCodename: eoan
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: Very infrequently
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / 
Radeon Vega Mobile Series] [1002:15dd] (rev c3) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Raven Ridge [Radeon Vega Series / Radeon Vega Mobile 
Series] [17aa:506f]
  InstallationDate: Installed on 2019-03-22 (206 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  Lsusb:
   Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 003 Device 003: ID 13d3:56a6 IMC Networks Integrated Camera
   Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 20KVCTO1WW
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-18-generic 
root=/dev/mapper/ubuntu--vg-root ro DEFAULT quiet splash ivrs_ioapic[32]=00:14.0
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: Upgraded to eoan on 2019-10-13 (1 days ago)
  dmi.bios.date: 12/07/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R0UET68W (1.48 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20KVCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrR0UET68W(1.48):bd12/07/2018:svnLENOVO:pn20KVCTO1WW:pvrThinkPadE585:rvnLENOVO:rn20KVCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad E585
  dmi.product.name: 20KVCTO1WW
  dmi.product.sku: LENOVO_MT_20KV_BU_Think_FM_ThinkPad E585
  dmi.product.version: ThinkPad E585
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.1-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 

[Kernel-packages] [Bug 1856413] Re: Asus UX580 touchpad stops working

[Pavel Deg]

Attached dmesg.

** Attachment added: "dmesg out"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1856413/+attachment/5313068/+files/dmesg.out

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

Title:
  Asus UX580 touchpad stops working

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Periodically after restart touchpad on my UX580 laptop stops working 
completely. 
  Closing the lid and letting the laptop to suspend, and then re-opening the 
lid activates the touchpad.
  Attached xinput list output.

  This is Ubuntu 19.10, latest kernel.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pavel  2048 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2019-10-29 (47 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 13d3:5755 IMC Networks USB2.0 VGA UVC WebCam
   Bus 001 Device 004: ID 8087:0aaa Intel Corp. 
   Bus 001 Device 003: ID 04f3:2706 Elan Microelectronics Corp. Touchscreen
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. ZenBook Pro 15 UX550GDX_UX580GD
  NonfreeKernelModules: nvidia_modeset nvidia
  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 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic 
root=UUID=9909f5be-7ef4-4a37-b5c1-c07caf97ff8f ro quiet splash 
resume=UUID=cc044a08-3549-4c51-9964-c4e396792368 vt.handoff=7
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-24-generic N/A
   linux-backports-modules-5.3.0-24-generic  N/A
   linux-firmware1.183.2
  Tags:  eoan
  Uname: Linux 5.3.0-24-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/11/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX550GDX.308
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX550GDX
  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.:bvrUX550GDX.308:bd07/11/2019:svnASUSTeKCOMPUTERINC.:pnZenBookPro15UX550GDX_UX580GD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX550GDX:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: ZenBook Pro
  dmi.product.name: ZenBook Pro 15 UX550GDX_UX580GD
  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/1856413/+subscriptions

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

[Kernel-packages] [Bug 1854752] Re: eoan/linux-kvm: 5.3.0-1009.10 -proposed tracker

[Ubuntu Kernel Bot]

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

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1854762
  packages:
main: linux-kvm
meta: linux-meta-kvm
  phase: Testing
  phase-changed: Thursday, 05. December 2019 10:41 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   automated-testing: Stalled -- testing FAILED
security-signoff: Stalled -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  variant: debs

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

Title:
  eoan/linux-kvm: 5.3.0-1009.10 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow verification-testing series:
  In Progress
Status in linux-kvm package in Ubuntu:
  Invalid
Status in linux-kvm 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 --
  boot-testing-requested: true
  kernel-stable-master-bug: 1854762
  packages:
main: linux-kvm
meta: linux-meta-kvm
  phase: Testing
  phase-changed: Thursday, 05. December 2019 10:41 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
security-signoff: Stalled -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  variant: debs

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

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

[Kernel-packages] [Bug 1854749] Re: eoan/linux-azure: 5.3.0-1009.10 -proposed tracker

[Ubuntu Kernel Bot]

** Changed in: kernel-sru-workflow/automated-testing
   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: 1854762
  packages:
lrm: linux-restricted-modules-azure
main: linux-azure
meta: linux-meta-azure
signed: linux-signed-azure
  phase: Testing
  phase-changed: Friday, 06. December 2019 22:26 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   automated-testing: Ongoing -- testing in progress
security-signoff: Stalled -- waiting for signoff
stakeholder-signoff: Stalled -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
bionic/linux-azure-5.3: bug 1854747
  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/1854749

Title:
  eoan/linux-azure: 5.3.0-1009.10 -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:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow stakeholder-signoff series:
  Confirmed
Status in Kernel SRU Workflow verification-testing series:
  In Progress
Status in linux-azure package in Ubuntu:
  Invalid
Status in linux-azure 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 --
  boot-testing-requested: true
  kernel-stable-master-bug: 1854762
  packages:
lrm: linux-restricted-modules-azure
main: linux-azure
meta: linux-meta-azure
signed: linux-signed-azure
  phase: Testing
  phase-changed: Friday, 06. December 2019 22:26 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
security-signoff: Stalled -- waiting for signoff
stakeholder-signoff: Stalled -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
bionic/linux-azure-5.3: bug 1854747
  variant: debs

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

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

[Kernel-packages] [Bug 1854751] Re: eoan/linux-gcp: 5.3.0-1010.11 -proposed tracker

[Ubuntu Kernel Bot]

** Changed in: kernel-sru-workflow/automated-testing
   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: 1854762
  packages:
lrm: linux-restricted-modules-gcp
main: linux-gcp
meta: linux-meta-gcp
signed: linux-signed-gcp
  phase: Testing
  phase-changed: Thursday, 05. December 2019 12:51 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   automated-testing: Ongoing -- testing in progress
security-signoff: Stalled -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
bionic/linux-gcp-5.3: bug 1854750
  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/1854751

Title:
  eoan/linux-gcp: 5.3.0-1010.11 -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:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow verification-testing series:
  In Progress
Status in linux-gcp package in Ubuntu:
  Invalid
Status in linux-gcp 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 --
  boot-testing-requested: true
  kernel-stable-master-bug: 1854762
  packages:
lrm: linux-restricted-modules-gcp
main: linux-gcp
meta: linux-meta-gcp
signed: linux-signed-gcp
  phase: Testing
  phase-changed: Thursday, 05. December 2019 12:51 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
security-signoff: Stalled -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
bionic/linux-gcp-5.3: bug 1854750
  variant: debs

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

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

[Kernel-packages] [Bug 1854746] Re: eoan/linux-aws: 5.3.0-1009.10 -proposed tracker

[Ubuntu Kernel Bot]

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

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1854762
  packages:
lrm: linux-restricted-modules-aws
main: linux-aws
meta: linux-meta-aws
  phase: Testing
  phase-changed: Thursday, 05. December 2019 11:36 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   automated-testing: Stalled -- testing FAILED
security-signoff: Stalled -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
bionic/linux-aws-5.3: bug 1854745
  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/1854746

Title:
  eoan/linux-aws: 5.3.0-1009.10 -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 promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow verification-testing series:
  In Progress
Status in linux-aws package in Ubuntu:
  Invalid
Status in linux-aws 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 --
  boot-testing-requested: true
  kernel-stable-master-bug: 1854762
  packages:
lrm: linux-restricted-modules-aws
main: linux-aws
meta: linux-meta-aws
  phase: Testing
  phase-changed: Thursday, 05. December 2019 11:36 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
security-signoff: Stalled -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
bionic/linux-aws-5.3: bug 1854745
  variant: debs

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

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

[Kernel-packages] [Bug 1856408] Re: zfs-initramfs needs to set FRAMEBUFFER=y

[Launchpad Bug Tracker]

This bug was fixed in the package zfs-linux - 0.8.2-3ubuntu4

---
zfs-linux (0.8.2-3ubuntu4) focal; urgency=medium

  * debian/patches/initramfs-setup-keymapping-and-video-for-
prompts.patch: initramfs: setup keymapping and video for prompts.
Thanks to Richard Laager .  Closes LP: #1856408.

 -- Steve Langasek   Mon, 16 Dec 2019
09:42:52 -0800

** Changed in: zfs-linux (Ubuntu)
   Status: New => Fix Released

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

Title:
  zfs-initramfs needs to set FRAMEBUFFER=y

Status in zfs-linux package in Ubuntu:
  Fix Released

Bug description:
  The poorly-named 'FRAMEBUFFER' option in initramfs-tools controls
  whether the console_setup and plymouth scripts are included and used
  in the initramfs.  These are required for any initramfs which will be
  prompting for user input: console_setup because without it the user's
  configured keymap will not be set up, and plymouth because you are not
  guaranteed to have working video output in the initramfs without it
  (e.g. some nvidia+UEFI configurations with the default GRUB behavior).

  The zfs initramfs script may need to prompt the user for passphrases
  for encrypted zfs datasets, and we don't know definitively whether
  this is the case or not at the time the initramfs is constructed (and
  it's difficult to dynamically populate initramfs config variables
  anyway), therefore the zfs-initramfs package should just set
  FRAMEBUFFER=yes in a conf snippet the same way that the cryptsetup-
  initramfs package does (/usr/share/initramfs-tools/conf-
  hooks.d/cryptsetup).

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

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

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

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

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

** Changed in: linux (Ubuntu Eoan)
   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/1856608

Title:
  [Regression] usb usb2-port2: Cannot enable. Maybe the USB cable is
  bad?

Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Bionic:
  Triaged
Status in linux source package in Disco:
  Incomplete
Status in linux source package in Eoan:
  Incomplete
Status in linux source package in Focal:
  Incomplete

Bug description:
  This appears to be a regression between 4.15.0-70.79 and 4.15.0-72.81.

  [Impact]
  USB port unusable and boot time takes ~5 minutes longer to complete.

  [Test Case]
  dmesg | grep "Cannot enable"

  [Fix]
  [Regression Risk]

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

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

[Kernel-packages] [Bug 1856608] Re: [Regression] usb usb2-port2: Cannot enable. Maybe the USB cable is bad?

[dann frazier]

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

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

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => dann frazier (dannf)

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

** Also affects: linux (Ubuntu Focal)
   Importance: Undecided
 Assignee: dann frazier (dannf)
   Status: Triaged

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

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

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

** Changed in: linux (Ubuntu Focal)
   Status: Triaged => 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/1856608

Title:
  [Regression] usb usb2-port2: Cannot enable. Maybe the USB cable is
  bad?

Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Bionic:
  Triaged
Status in linux source package in Disco:
  Incomplete
Status in linux source package in Eoan:
  Incomplete
Status in linux source package in Focal:
  Incomplete

Bug description:
  This appears to be a regression between 4.15.0-70.79 and 4.15.0-72.81.

  [Impact]
  USB port unusable and boot time takes ~5 minutes longer to complete.

  [Test Case]
  dmesg | grep "Cannot enable"

  [Fix]
  [Regression Risk]

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

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

[Kernel-packages] [Bug 1848883] Re: (Lenovo S130-11IGM) emmc not working in 19.04

[Jim]

Hi Adrian... that worked !! Is this just a temporary fix or something
that would be in future releases ? Thanks

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

Title:
  (Lenovo S130-11IGM) emmc not working in 19.04

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  
  I don't think this is the same issue as ;
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818407
  although I have read a lot of issues with emmc disks.

  Booting from lubuntu CD1 19.04 takes about an hour before I get to the
  desktop. The installer runs through to the partitioning sections and
  is able to see the disk, but it fails to create the partitions. The
  laptop has a 32gb emmc disk. There is some kind of timeout during boot
  on the dhpci probe. The only OS/kernel match I have got to work on
  this device is Lubuntu/18.04 4.15.0-20 (every single function works).
  After installing 18.04 there is an auto update to 4.15.0-65 but the
  touchpad stops working so I defaulted grub back to -20 (this failure
  is not caused by libinput or synaptics drivers). Neither kernels have
  a working wifi module but rtl8821ce install fixes this so not an issue
  for me.

  Attaching as many logs as I can grab.. please let me know and I'll 
happily get any other requested logging.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  lubuntu1434 F pulseaudio
  CasperVersion: 1.405
  DistroRelease: Ubuntu 19.04
  IwConfig:
   enp0s21f0u1  no wireless extensions.
   
   lono wireless extensions.
  LiveMediaBuild: Lubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  MachineType: LENOVO 81J1
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz 
file=/cdrom/preseed/hostname.seed boot=casper quiet splash ---
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-13-generic N/A
   linux-backports-modules-5.0.0-13-generic  N/A
   linux-firmware1.178
  Tags:  disco
  Uname: Linux 5.0.0-13-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 09/05/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 9HCN27WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0R32802WIN
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad S130-11IGM
  dmi.modalias: 
dmi:bvnLENOVO:bvr9HCN27WW:bd09/05/2019:svnLENOVO:pn81J1:pvrLenovoideapadS130-11IGM:rvnLENOVO:rnLNVNB161216:rvrSDK0R32802WIN:cvnLENOVO:ct10:cvrLenovoideapadS130-11IGM:
  dmi.product.family: ideapad S130-11IGM
  dmi.product.name: 81J1
  dmi.product.sku: LENOVO_MT_81J1_BU_idea_FM_ideapad S130-11IGM
  dmi.product.version: Lenovo ideapad S130-11IGM
  dmi.sys.vendor: LENOVO

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

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

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

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

Title:
  [Regression] usb usb2-port2: Cannot enable. Maybe the USB cable is
  bad?

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  This appears to be a regression between 4.15.0-70.79 and 4.15.0-72.81.

  [Impact]
  USB port unusable and boot time takes ~5 minutes longer to complete.

  [Test Case]
  dmesg | grep "Cannot enable"

  [Fix]
  [Regression Risk]

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

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

[Kernel-packages] [Bug 1856084] Re: Livelock between ZFS evict and writeback threads

[Colin Ian King]

I've tested zfs from the -proposed pockets with the ubuntu ZFS autotest
regression tests:

ubuntu_zfs_fstest
ubuntu_zfs_smoke_test
ubuntu_zfs_stress
ubuntu_zfs_xfs_generic

All the following passed the regression testing.

bionic: 0.7.5-1ubuntu16.7 
disco:  0.7.12-1ubuntu5.1 
eoan:   0.8.1-1ubuntu14.3

I was unable to trip and lockups, so as far as I'm concerned I'm happy
for these updates to be released.

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

Title:
  Livelock between ZFS evict and writeback threads

Status in zfs-linux package in Ubuntu:
  Fix Released
Status in zfs-linux source package in Bionic:
  Fix Committed
Status in zfs-linux source package in Disco:
  Fix Committed
Status in zfs-linux source package in Eoan:
  Fix Committed
Status in zfs-linux source package in Focal:
  Fix Released
Status in zfs-linux package in Debian:
  Unknown

Bug description:
  Livelock between ZFS evict and writeback threads

  [Impact]
  ZIO pipeline stalls, causing ZFS workloads to hang indefinitely

  [Description]
  For certain ZFS workloads, we start seeing hung task timeouts in the kernel 
logs due to zil_commit() stalling. This is due to zfs_zget() not detecting 
whether a znode has been marked for deletion before attempting to access it, 
causing a constant "retry loop" in zfs_get_data() if that znode has been 
unlinked already. An example of the stack traces follows:

  [72742.051703] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [72742.070429] mysqld  D0  5713   2881 0x0320
  [72742.073220] Call Trace:
  [72742.075305]  __schedule+0x24e/0x880
  [72742.090436]  schedule+0x2c/0x80
  [72742.090438]  schedule_preempt_disabled+0xe/0x10
  [72742.090441]  __mutex_lock.isra.5+0x276/0x4e0
  [72742.090547]  ? dmu_tx_destroy+0x105/0x130 [zfs]
  [72742.090555]  __mutex_lock_slowpath+0x13/0x20
  [72742.115374]  ? __mutex_lock_slowpath+0x13/0x20
  [72742.132266]  mutex_lock+0x2f/0x40
  [72742.134207]  zil_commit_impl+0x1b0/0x1b30 [zfs]
  [72742.150428]  ? spl_kmem_alloc+0x115/0x180 [spl]
  [72742.152622]  ? mutex_lock+0x12/0x40
  [72742.154819]  ? zfs_refcount_add_many+0x9a/0x100 [zfs]
  [72742.171450]  zil_commit+0xde/0x150 [zfs]
  [72742.173687]  zfs_fsync+0x77/0xe0 [zfs]
  [72742.175044]  zpl_fsync+0x80/0x110 [zfs]
  [72742.191690]  vfs_fsync_range+0x51/0xb0
  [72742.193876]  do_fsync+0x3d/0x70
  [72742.195126]  SyS_fsync+0x10/0x20
  [72742.211059]  do_syscall_64+0x73/0x130
  [72742.214078]  entry_SYSCALL_64_after_hwframe+0x3d/0xa2

  It's possible to hit this issue due to a race between the ZFS evict
  and writeback threads. If the z_iput task is trying to evict a znode
  that's currently sitting in the writeback thread, both will "livelock"
  each other and stall the ZIO pipeline, causing other ZFS operations
  (such as zil_commit) to hang indefinitely.

  This has been documented and fixed upstream in PR#9583 [0]. We need to
  pull two fixes from upstream: the first one fixes the zfs_zget() issue
  in the writeback thread, while the second fixes a regression on
  O_TMPFILE descriptors caused by the first one.

  Upstream patches:
   - Break out of zfs_zget early if unlinked znode (41e1aa2a06f8)
   - Check for unlinked znodes after igrab() (0c46813805f4)

  [Test Case]
  Being a race condition, this issue has been hard to reproduce consistently. 
The racing window between evict() and the ZFS writeback thread is quite strict, 
but users have reported this to show up after some hours of running 
LXD-containerized mySQL workloads.

  [Regression Potential]
  These patches have been tested both in the ZFS test suite and in production 
environments, so the potential for further regressions should be low.
  Additional regressions would likely cause issues with the ZFS 
writeback/commit and IO pipeline, so they should be spotted fairly quickly.

  [0] https://github.com/zfsonlinux/zfs/pull/9583
  [1] https://github.com/zfsonlinux/zfs/commit/41e1aa2a06f8
  [2] https://github.com/zfsonlinux/zfs/commit/0c46813805f4

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

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

[Kernel-packages] [Bug 1856084] Re: Livelock between ZFS evict and writeback threads

[Colin Ian King]

*I was unable to trip any lockups

** Tags added: verification-done-bionic verification-done-disco
verification-done-eoan

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

Title:
  Livelock between ZFS evict and writeback threads

Status in zfs-linux package in Ubuntu:
  Fix Released
Status in zfs-linux source package in Bionic:
  Fix Committed
Status in zfs-linux source package in Disco:
  Fix Committed
Status in zfs-linux source package in Eoan:
  Fix Committed
Status in zfs-linux source package in Focal:
  Fix Released
Status in zfs-linux package in Debian:
  Unknown

Bug description:
  Livelock between ZFS evict and writeback threads

  [Impact]
  ZIO pipeline stalls, causing ZFS workloads to hang indefinitely

  [Description]
  For certain ZFS workloads, we start seeing hung task timeouts in the kernel 
logs due to zil_commit() stalling. This is due to zfs_zget() not detecting 
whether a znode has been marked for deletion before attempting to access it, 
causing a constant "retry loop" in zfs_get_data() if that znode has been 
unlinked already. An example of the stack traces follows:

  [72742.051703] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [72742.070429] mysqld  D0  5713   2881 0x0320
  [72742.073220] Call Trace:
  [72742.075305]  __schedule+0x24e/0x880
  [72742.090436]  schedule+0x2c/0x80
  [72742.090438]  schedule_preempt_disabled+0xe/0x10
  [72742.090441]  __mutex_lock.isra.5+0x276/0x4e0
  [72742.090547]  ? dmu_tx_destroy+0x105/0x130 [zfs]
  [72742.090555]  __mutex_lock_slowpath+0x13/0x20
  [72742.115374]  ? __mutex_lock_slowpath+0x13/0x20
  [72742.132266]  mutex_lock+0x2f/0x40
  [72742.134207]  zil_commit_impl+0x1b0/0x1b30 [zfs]
  [72742.150428]  ? spl_kmem_alloc+0x115/0x180 [spl]
  [72742.152622]  ? mutex_lock+0x12/0x40
  [72742.154819]  ? zfs_refcount_add_many+0x9a/0x100 [zfs]
  [72742.171450]  zil_commit+0xde/0x150 [zfs]
  [72742.173687]  zfs_fsync+0x77/0xe0 [zfs]
  [72742.175044]  zpl_fsync+0x80/0x110 [zfs]
  [72742.191690]  vfs_fsync_range+0x51/0xb0
  [72742.193876]  do_fsync+0x3d/0x70
  [72742.195126]  SyS_fsync+0x10/0x20
  [72742.211059]  do_syscall_64+0x73/0x130
  [72742.214078]  entry_SYSCALL_64_after_hwframe+0x3d/0xa2

  It's possible to hit this issue due to a race between the ZFS evict
  and writeback threads. If the z_iput task is trying to evict a znode
  that's currently sitting in the writeback thread, both will "livelock"
  each other and stall the ZIO pipeline, causing other ZFS operations
  (such as zil_commit) to hang indefinitely.

  This has been documented and fixed upstream in PR#9583 [0]. We need to
  pull two fixes from upstream: the first one fixes the zfs_zget() issue
  in the writeback thread, while the second fixes a regression on
  O_TMPFILE descriptors caused by the first one.

  Upstream patches:
   - Break out of zfs_zget early if unlinked znode (41e1aa2a06f8)
   - Check for unlinked znodes after igrab() (0c46813805f4)

  [Test Case]
  Being a race condition, this issue has been hard to reproduce consistently. 
The racing window between evict() and the ZFS writeback thread is quite strict, 
but users have reported this to show up after some hours of running 
LXD-containerized mySQL workloads.

  [Regression Potential]
  These patches have been tested both in the ZFS test suite and in production 
environments, so the potential for further regressions should be low.
  Additional regressions would likely cause issues with the ZFS 
writeback/commit and IO pipeline, so they should be spotted fairly quickly.

  [0] https://github.com/zfsonlinux/zfs/pull/9583
  [1] https://github.com/zfsonlinux/zfs/commit/41e1aa2a06f8
  [2] https://github.com/zfsonlinux/zfs/commit/0c46813805f4

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

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

[Kernel-packages] [Bug 1856608] [NEW] [Regression] usb usb2-port2: Cannot enable. Maybe the USB cable is bad?

[dann frazier]

Public bug reported:

This appears to be a regression between 4.15.0-70.79 and 4.15.0-72.81.

[Impact]
USB port unusable and boot time takes ~5 minutes longer to complete.

[Test Case]
dmesg | grep "Cannot enable"

[Fix]
[Regression Risk]

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

Title:
  [Regression] usb usb2-port2: Cannot enable. Maybe the USB cable is
  bad?

Status in linux package in Ubuntu:
  New

Bug description:
  This appears to be a regression between 4.15.0-70.79 and 4.15.0-72.81.

  [Impact]
  USB port unusable and boot time takes ~5 minutes longer to complete.

  [Test Case]
  dmesg | grep "Cannot enable"

  [Fix]
  [Regression Risk]

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

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

[Kernel-packages] [Bug 1853440] Re: Volume either 0 or 100% on Lenovo X1 Carbon G7

[Jan]

Perfect, this kernel version resolves this bug! Thanks for your help!

Should I close this issue now, or should I wait until the fix gets
merged into the normal kernel?

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

Title:
  Volume either 0 or 100% on Lenovo X1 Carbon G7

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Volume increasing or decreasing doesn't work. 
  I can only toggle sound on (= 100%) and off (= 0%).

  What I found out is that the Master channel seems to have no effect
  for volume adjustments, but the PCM channel does. If the sound is
  muted, PCM is set to 0 and therefore the sound is toggled off, but
  when I increase the sound a bit, PCM jumps straight to 100, causing
  the speakers to be very load.

  I have attached alsa-info output.

  System environment:
  Pop!_OS 19.10
  Release: 19.10

  Alsa-Version:
  alsa-base: 1.0.25

  Sound Card:
  HDA-Intel
  Codec: Realtek ALC285
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: pop:GNOME
  DisplayManager: gdm3
  DistroRelease: Pop!_OS 19.10
  Package: linux
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 
5.3.0-22.24+system76~1573659475~19.10~26b2022-generic 5.3.7
  RelatedPackageVersions: mutter-common 
3.34.1+git20191107-1ubuntu1~19.10.1pop0~1573683812~19.10~50e928a
  Tags: third-party-packages eoan
  Uname: Linux 5.3.0-22-generic x86_64
  UnreportableReason: This is not an official Pop!_OS package. Please remove 
any third party package and try again.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm sudo
  _MarkForUpload: True

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

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

[Kernel-packages] [Bug 1783881] Re: ltp-syscalls: msgstress03 fails because systemd limits number of processes

[Sean Feole]

This failure occurs in the cloud, on amazon aws, it can be reproduced on
c4/c5.large abd c5.metal

where it passes on c5n.xlarge / i3.metal m3.large m4.large.

I will try the suggested steps above on one of the affected flavor types
and see if we can get to the bottom of this.

** Changed in: ubuntu-kernel-tests
 Assignee: (unassigned) => Sean Feole (sfeole)

** Tags added: sqa

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

Title:
  ltp-syscalls: msgstress03 fails because systemd limits number of
  processes

Status in ubuntu-kernel-tests:
  Triaged
Status in linux package in Ubuntu:
  Incomplete
Status in systemd package in Ubuntu:
  Incomplete
Status in linux source package in Xenial:
  New
Status in systemd source package in Xenial:
  New
Status in linux source package in Cosmic:
  Incomplete

Bug description:
  As systemd limits the number of processes, this test will fail because
  it can't fork enough processes. That is limited to when the test is
  run after logging as user 1000, then running sudo. I guess that
  logging as root may not cause this to happen.

  # ./testcases/bin/msgstress03 
  Fork failed (may be OK if under stress)
  Fork failed (may be OK if under stress)
  msgstress031  TFAIL  :  msgstress03.c:157:  Fork failed (may be OK if 
under stress)
  #

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

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

[Kernel-packages] [Bug 1856605] [NEW] [linux-azure] Ubuntu 16.04 + INFINIBAND-OPEN-MPI-2VM

[Joseph Salisbury]

Public bug reported:

We ran an RDMA test case against gallery image Ubuntu 16.04 (with
proposed kernel), and found the below issue.  The kernel prior to
proposed does not exhibit this bug, so it is a regression:

The issue is when ibv_devinfo is run, we get the below info:

ibv_devinfo
libibverbs: Warning: no userspace device-specific driver found for 
/sys/class/infiniband_verbs/uverbs0
No IB devices found
 
ibv_devices
libibverbs: Warning: no userspace device-specific driver found for 
/sys/class/infiniband_verbs/uverbs0
device node GUID
--  
 
Ibstat works as expected
CA 'mlx5_0'
CA type: MT4120
Number of ports: 1
Firmware version: 16.23.1020
Hardware version: 0
Node GUID: 0x00155dfffe33ff49
System image GUID: 0x506b4b0300f521ec
Port 1:
State: Active
Physical state: LinkUp
Rate: 100
Base lid: 713
LMC: 0
SM lid: 16
Capability mask: 0x2651ec48
Port GUID: 0x00155dfffd33ff49
Link layer: InfiniBand


This Family exhibits the bug, with a subsystem of MT28800:
lspci -v|egrep 'Mel|mlx'
0002:00:02.0 Infiniband controller: Mellanox Technologies MT27800 Family 
[ConnectX-5 Virtual Function]
Subsystem: Mellanox Technologies MT28800 Family [ConnectX-5 Virtual 
Function]
Kernel driver in use: mlx5_core
Kernel modules: mlx5_core

 
This issue does not occur with Ubuntu 18.04, which has a different 
Subsystem(MT27800):
lspci -v|egrep 'Mel|mlx'
0002:00:02.0 Infiniband controller: Mellanox Technologies MT27800 Family 
[ConnectX-5 Virtual Function]
Subsystem: Mellanox Technologies MT27800 Family [ConnectX-5 Virtual 
Function]
Kernel driver in use: mlx5_core
Kernel modules: mlx5_core

If we could, we would like to move to rmda-core to version 22 or higher.

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

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

Title:
  [linux-azure] Ubuntu 16.04 + INFINIBAND-OPEN-MPI-2VM

Status in linux-azure package in Ubuntu:
  New

Bug description:
  We ran an RDMA test case against gallery image Ubuntu 16.04 (with
  proposed kernel), and found the below issue.  The kernel prior to
  proposed does not exhibit this bug, so it is a regression:

  The issue is when ibv_devinfo is run, we get the below info:

  ibv_devinfo
  libibverbs: Warning: no userspace device-specific driver found for 
/sys/class/infiniband_verbs/uverbs0
  No IB devices found
   
  ibv_devices
  libibverbs: Warning: no userspace device-specific driver found for 
/sys/class/infiniband_verbs/uverbs0
  device node GUID
  --  
   
  Ibstat works as expected
  CA 'mlx5_0'
  CA type: MT4120
  Number of ports: 1
  Firmware version: 16.23.1020
  Hardware version: 0
  Node GUID: 0x00155dfffe33ff49
  System image GUID: 0x506b4b0300f521ec
  Port 1:
  State: Active
  Physical state: LinkUp
  Rate: 100
  Base lid: 713
  LMC: 0
  SM lid: 16
  Capability mask: 0x2651ec48
  Port GUID: 0x00155dfffd33ff49
  Link layer: InfiniBand


  This Family exhibits the bug, with a subsystem of MT28800:
  lspci -v|egrep 'Mel|mlx'
  0002:00:02.0 Infiniband controller: Mellanox Technologies MT27800 Family 
[ConnectX-5 Virtual Function]
  Subsystem: Mellanox Technologies MT28800 Family [ConnectX-5 Virtual 
Function]
  Kernel driver in use: mlx5_core
  Kernel modules: mlx5_core

   
  This issue does not occur with Ubuntu 18.04, which has a different 
Subsystem(MT27800):
  lspci -v|egrep 'Mel|mlx'
  0002:00:02.0 Infiniband controller: Mellanox Technologies MT27800 Family 
[ConnectX-5 Virtual Function]
  Subsystem: Mellanox Technologies MT27800 Family [ConnectX-5 Virtual 
Function]
  Kernel driver in use: mlx5_core
  Kernel modules: mlx5_core

  If we could, we would like to move to rmda-core to version 22 or
  higher.

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

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

[Kernel-packages] [Bug 1854722] Re: mtest06 from mm in ubuntu_ltp failed on B-AWS-5.0

[Sean Feole]

** Changed in: ubuntu-kernel-tests
   Status: New => Triaged

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

Title:
  mtest06 from mm in ubuntu_ltp failed on B-AWS-5.0

Status in ubuntu-kernel-tests:
  Triaged
Status in linux-aws package in Ubuntu:
  New

Bug description:
  Kernel: 5.0.0-1022.25~18.04.1

  Issue found on instance t2.small
  The test failed with ENOMEM

  
   startup='Wed Nov 20 10:40:07 2019'
   tst_test.c:1217: INFO: Timeout per run is 0h 05m 00s
   mmap1.c:205: BROK: mmap((nil),2147483648,3,34,-1,0) failed: ENOMEM (12)

   Summary:
   passed 0
   failed 0
   skipped 0
   warnings 0
   tag=mtest06 stime=1574246407 dur=0 exit=exited stat=2 core=no cu=0 cs=0

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

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

[Kernel-packages] [Bug 1829849] Re: proc01 in fs from ubuntu_ltp failed with D/B/E

[Sean Feole]

** Tags added: sqa-check

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

Title:
  proc01 in fs from ubuntu_ltp failed with D/B/E

Status in ubuntu-kernel-tests:
  Triaged
Status in linux package in Ubuntu:
  Incomplete
Status in linux-aws package in Ubuntu:
  New

Bug description:
   proc01  0  TINFO  :  /proc/sys/fs/binfmt_misc/register: is write-only.
   proc01  0  TINFO  :  /proc/sys/net/ipv6/conf/all/stable_secret: known 
issue: errno=EIO(5): Input/output error
   proc01  0  TINFO  :  /proc/sys/net/ipv6/conf/default/stable_secret: 
known issue: errno=EIO(5): Input/output error
   proc01  0  TINFO  :  /proc/sys/net/ipv6/conf/ens6/stable_secret: known 
issue: errno=EIO(5): Input/output error
   proc01  0  TINFO  :  /proc/sys/net/ipv6/conf/lo/stable_secret: known 
issue: errno=EIO(5): Input/output error
   proc01  0  TINFO  :  /proc/kmsg: known issue: 
errno=EAGAIN/EWOULDBLOCK(11): Resource temporarily unavailable
   proc01  0  TINFO  :  /proc/sysrq-trigger: is write-only.
   proc01  0  TINFO  :  /proc/self/task/8782/mem: known issue: 
errno=EIO(5): Input/output error
   proc01  0  TINFO  :  /proc/self/task/8782/clear_refs: is write-only.
   proc01  0  TINFO  :  /proc/self/task/8782/pagemap: reached maxmbytes (-m)
   proc01  0  TINFO  :  /proc/self/task/8782/attr/prev: known issue: 
errno=EINVAL(22): Invalid argument
   proc01  0  TINFO  :  /proc/self/task/8782/attr/exec: known issue: 
errno=EINVAL(22): Invalid argument
   proc01  0  TINFO  :  /proc/self/task/8782/attr/fscreate: known issue: 
errno=EINVAL(22): Invalid argument
   proc01  0  TINFO  :  /proc/self/task/8782/attr/keycreate: known issue: 
errno=EINVAL(22): Invalid argument
   proc01  0  TINFO  :  /proc/self/task/8782/attr/sockcreate: known issue: 
errno=EINVAL(22): Invalid argument
   proc01  1  TFAIL  :  proc01.c:397: read failed: 
/proc/self/task/8782/attr/selinux/current: errno=EINVAL(22): Invalid argument
   proc01  2  TFAIL  :  proc01.c:397: read failed: 
/proc/self/task/8782/attr/selinux/prev: errno=EINVAL(22): Invalid argument
   proc01  3  TFAIL  :  proc01.c:397: read failed: 
/proc/self/task/8782/attr/selinux/exec: errno=EINVAL(22): Invalid argument
   proc01  4  TFAIL  :  proc01.c:397: read failed: 
/proc/self/task/8782/attr/selinux/fscreate: errno=EINVAL(22): Invalid argument
   proc01  5  TFAIL  :  proc01.c:397: read failed: 
/proc/self/task/8782/attr/selinux/keycreate: errno=EINVAL(22): Invalid argument
   proc01  6  TFAIL  :  proc01.c:397: read failed: 
/proc/self/task/8782/attr/selinux/sockcreate: errno=EINVAL(22): Invalid argument
   proc01  7  TFAIL  :  proc01.c:397: read failed: 
/proc/self/task/8782/attr/smack/current: errno=EINVAL(22): Invalid argument
   proc01  8  TFAIL  :  proc01.c:397: read failed: 
/proc/self/task/8782/attr/apparmor/prev: errno=EINVAL(22): Invalid argument
   proc01  9  TFAIL  :  proc01.c:397: read failed: 
/proc/self/task/8782/attr/apparmor/exec: errno=EINVAL(22): Invalid argument
   proc01  0  TINFO  :  /proc/self/mem: known issue: errno=EIO(5): 
Input/output error
   proc01  0  TINFO  :  /proc/self/clear_refs: is write-only.
   proc01  0  TINFO  :  /proc/self/pagemap: reached maxmbytes (-m)
   proc01  0  TINFO  :  /proc/self/attr/prev: known issue: 
errno=EINVAL(22): Invalid argument
   proc01  0  TINFO  :  /proc/self/attr/exec: known issue: 
errno=EINVAL(22): Invalid argument
   proc01  0  TINFO  :  /proc/self/attr/fscreate: known issue: 
errno=EINVAL(22): Invalid argument
   proc01  0  TINFO  :  /proc/self/attr/keycreate: known issue: 
errno=EINVAL(22): Invalid argument
   proc01  0  TINFO  :  /proc/self/attr/sockcreate: known issue: 
errno=EINVAL(22): Invalid argument
   proc01 10  TFAIL  :  proc01.c:397: read failed: 
/proc/self/attr/selinux/current: errno=EINVAL(22): Invalid argument
   proc01 11  TFAIL  :  proc01.c:397: read failed: 
/proc/self/attr/selinux/prev: errno=EINVAL(22): Invalid argument
   proc01 12  TFAIL  :  proc01.c:397: read failed: 
/proc/self/attr/selinux/exec: errno=EINVAL(22): Invalid argument
   proc01 13  TFAIL  :  proc01.c:397: read failed: 
/proc/self/attr/selinux/fscreate: errno=EINVAL(22): Invalid argument
   proc01 14  TFAIL  :  proc01.c:397: read failed: 
/proc/self/attr/selinux/keycreate: errno=EINVAL(22): Invalid argument
   proc01 15  TFAIL  :  proc01.c:397: read failed: 
/proc/self/attr/selinux/sockcreate: errno=EINVAL(22): Invalid argument
   proc01 16  TFAIL  :  proc01.c:397: read failed: 
/proc/self/attr/smack/current: errno=EINVAL(22): Invalid argument
   proc01 17  TFAIL  :  proc01.c:397: read failed: 
/proc/self/attr/apparmor/prev: errno=EINVAL(22): Invalid argument
   proc01 18  TFAIL  :  proc01.c:397: read failed: 
/proc/self/attr/apparmor/exec: errno=EINVAL(22): Invalid 

[Kernel-packages] [Bug 1848193] Re: Fixup tlbie vs store ordering issue on POWER9

[Frank Heimes]

Cool, many thx Manoj!

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

Title:
  Fixup tlbie vs store ordering issue on POWER9

Status in The Ubuntu-power-systems project:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Eoan:
  Fix Released

Bug description:
  == Comment: #0 - Michael Ranweiler  - 2019-10-07 01:52:38 ==
  On POWER9, under some circumstances, a broadcast TLB invalidation will fail 
to invalidate the ERAT cache on some threads when there are parallel 
mtpidr/mtlpidr happening on other threads of the same core.  This can cause 
stores to continue to go to a page after it's unmapped.

  The workaround is to force an ERAT flush using PID=0 or LPID=0 tlbie
  flush. This additional TLB flush will cause the ERAT cache
  invalidation. Since we are using PID=0 or LPID=0, we don't get
  filtered out by the TLB snoop filtering logic.

  We need to still follow this up with another tlbie to take care of
  store vs tlbie ordering issue explained in commit: a5d4b5891c2f
  ("powerpc/mm: Fixup tlbie vs store ordering issue on POWER9"). The
  presence of ERAT cache implies we can still get new stores and they
  may miss store queue marking flush.

  The upstream git commits to resolve the problem:

  
https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git/commit/?h=fixes=677733e296b5c7a37c47da391fc70a43dc40bd67

  
https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git/commit/?h=fixes=09ce98cacd51fcd0fa0af2f79d1e1d3192f4cbb0

  
https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git/commit/?h=fixes=047e6575aec71d75b765c22111820c4776cd1c43

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

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

[Kernel-packages] [Bug 1854802] Re: bionic/linux-aws: 4.15.0-1057.59 -proposed tracker

[Ubuntu Kernel Bot]

** Changed in: kernel-sru-workflow/regression-testing
   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: 1854819
  packages:
lrm: linux-restricted-modules-aws
main: linux-aws
meta: linux-meta-aws
  phase: Testing
  phase-changed: Wednesday, 04. December 2019 23:21 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Ongoing -- testing in progress
-   regression-testing: Ongoing -- testing in progress
security-signoff: Stalled -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
bionic/linux-aws-fips: bug 1854800
bionic/linux-aws/aws-kernel: bug 1854799
xenial/linux-aws-hwe: bug 1854801
  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/1854802

Title:
  bionic/linux-aws: 4.15.0-1057.59 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  In Progress
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-lrm series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow verification-testing series:
  In Progress
Status in linux-aws package in Ubuntu:
  Invalid
Status in linux-aws 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: 1854819
  packages:
lrm: linux-restricted-modules-aws
main: linux-aws
meta: linux-meta-aws
  phase: Testing
  phase-changed: Wednesday, 04. December 2019 23:21 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Ongoing -- testing in progress
security-signoff: Stalled -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
bionic/linux-aws-fips: bug 1854800
bionic/linux-aws/aws-kernel: bug 1854799
xenial/linux-aws-hwe: bug 1854801
  variant: debs

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

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

[Kernel-packages] [Bug 1837543] Re: crypto_user02 in crypto from ubuntu_ltp failed

[Sean Feole]

linux-aws 4.15.0-1057.59

05 10:32:55 DEBUG| utils:0153| [stdout] crypto_user02.c:59: INFO: Starting 
crypto_user larval deletion test.  May crash buggy kernels.
12/05 10:32:55 DEBUG| utils:0153| [stdout] crypto_user02.c:91: BROK: 
unexpected error from tst_crypto_del_alg(): EBUSY (16)

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

Title:
  crypto_user02 in crypto from ubuntu_ltp failed

Status in ubuntu-kernel-tests:
  Triaged
Status in linux package in Ubuntu:
  Confirmed
Status in linux-aws package in Ubuntu:
  New
Status in linux source package in Bionic:
  New
Status in linux-aws source package in Bionic:
  Confirmed
Status in linux source package in Disco:
  Confirmed
Status in linux-aws source package in Disco:
  New
Status in linux source package in Eoan:
  Confirmed
Status in linux-aws source package in Eoan:
  New

Bug description:
  This is a new test, test will fail with:

  <<>>
  tag=crypto_user02 stime=1563881396
  cmdline="crypto_user02"
  contacts=""
  analysis=exit
  <<>>
  incrementing stop
  tst_test.c:1100: INFO: Timeout per run is 0h 05m 00s
  crypto_user02.c:59: INFO: Starting crypto_user larval deletion test.  May 
crash buggy kernels.
  crypto_user02.c:91: BROK: unexpected error from tst_crypto_del_alg(): EBUSY

  Summary:
  passed   0
  failed   0
  skipped  0
  warnings 0
  <<>>
  initiation_status="ok"
  duration=0 termination_type=exited termination_id=2 corefile=no
  cutime=0 cstime=0
  <<>>

  
  Nothing interesting in syslog:
  Jul 23 11:29:20 amaura systemd[1]: Started Session 1 of user ubuntu.
  Jul 23 11:29:56 amaura kernel: [  619.646330] LTP: starting crypto_user02
  Jul 23 11:30:23 amaura kernel: [  646.554403] cfg80211: Loading compiled-in 
X.509 certificates for regulatory database

  
  Steps to run this test:
git clone --depth=1 https://github.com/linux-test-project/ltp.git
cd ltp; make autotools; ./configure; make; sudo make install
echo "crypto_user02 crypto_user02" > /tmp/jobs
sudo /opt/ltp/runltp -f /tmp/jobs

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: linux-image-5.0.0-21-generic 5.0.0-21.22
  ProcVersionSignature: User Name 5.0.0-21.22-generic 5.0.15
  Uname: Linux 5.0.0-21-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jul 23 11:19 seq
   crw-rw 1 root audio 116, 33 Jul 23 11:19 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.10-0ubuntu27.1
  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:
  Date: Tue Jul 23 11:30:15 2019
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  MachineType: Intel Corporation S1200RP
  PciMultimedia:
   
  ProcFB: 0 mgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-21-generic 
root=UUID=b0d2ae4e-12dd-423e-acea-272ee8b2a893 ro
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-21-generic N/A
   linux-backports-modules-5.0.0-21-generic  N/A
   linux-firmware1.178.3
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/01/2015
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: S1200RP.86B.03.02.0003.070120151022
  dmi.board.asset.tag: 
  dmi.board.name: S1200RP
  dmi.board.vendor: Intel Corporation
  dmi.board.version: G62254-407
  dmi.chassis.asset.tag: 
  dmi.chassis.type: 17
  dmi.chassis.vendor: ..
  dmi.chassis.version: ..
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrS1200RP.86B.03.02.0003.070120151022:bd07/01/2015:svnIntelCorporation:pnS1200RP:pvr:rvnIntelCorporation:rnS1200RP:rvrG62254-407:cvn..:ct17:cvr..:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: S1200RP
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: 
  dmi.sys.vendor: Intel Corporation

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

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

[Kernel-packages] [Bug 1854802] Re: bionic/linux-aws: 4.15.0-1057.59 -proposed tracker

[Sean Feole]

** Tags added: regression-testing-passed

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

Title:
  bionic/linux-aws: 4.15.0-1057.59 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  In Progress
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-lrm series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow verification-testing series:
  In Progress
Status in linux-aws package in Ubuntu:
  Invalid
Status in linux-aws 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: 1854819
  packages:
lrm: linux-restricted-modules-aws
main: linux-aws
meta: linux-meta-aws
  phase: Testing
  phase-changed: Wednesday, 04. December 2019 23:21 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Ongoing -- testing in progress
security-signoff: Stalled -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
bionic/linux-aws-fips: bug 1854800
bionic/linux-aws/aws-kernel: bug 1854799
xenial/linux-aws-hwe: bug 1854801
  variant: debs

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

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

[Kernel-packages] [Bug 1829989] Re: memcg_use_hierarchy from controllers test suite in LTP failed

[Sean Feole]

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

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

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

Title:
  memcg_use_hierarchy from controllers test suite in LTP failed

Status in ubuntu-kernel-tests:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in linux-aws package in Ubuntu:
  Triaged
Status in linux source package in Bionic:
  Confirmed
Status in linux-aws source package in Bionic:
  New
Status in linux source package in Cosmic:
  Confirmed
Status in linux-aws source package in Cosmic:
  New

Bug description:
  startup='Wed May 22 05:59:07 2019'
  memcg_use_hierarchy_test 1 TINFO: Starting test 1
  sh: echo: I/O error
  memcg_use_hierarchy_test 1 TINFO: set /dev/memcg/memory.use_hierarchy to 0 
failed
  memcg_use_hierarchy_test 1 TPASS: process 31577 is killed
  memcg_use_hierarchy_test 2 TINFO: Starting test 2
  sh: echo: I/O error
  memcg_use_hierarchy_test 2 TINFO: set /dev/memcg/memory.use_hierarchy to 0 
failed
  memcg_use_hierarchy_test 2 TFAIL: echo 1 > memory.use_hierarchy passed 
unexpectedly
  memcg_use_hierarchy_test 3 TINFO: Starting test 3
  sh: echo: I/O error
  memcg_use_hierarchy_test 3 TINFO: set /dev/memcg/memory.use_hierarchy to 0 
failed
  memcg_use_hierarchy_test 3 TPASS: echo 0 > subgroup/memory.use_hierarchy 
failed as expected
  tag=memcg_use_hierarchy stime=1558504747 dur=1 exit=exited stat=1 core=no 
cu=5 cs=5

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-50-generic 4.15.0-50.54
  ProcVersionSignature: User Name 4.15.0-50.54-generic 4.15.18
  Uname: Linux 4.15.0-50-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 May 22 02:57 seq
   crw-rw 1 root audio 116, 33 May 22 02:57 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.6
  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:
  CurrentDmesg:
   [14538.862950] cfg80211: Loading compiled-in X.509 certificates for 
regulatory database
   [14538.874559] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7'
  Date: Wed May 22 07:33:33 2019
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
  PciMultimedia:
   
  ProcFB: 0 cirrusdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-50-generic 
root=UUID=57e8-9e7f-40ee-934e-f1dce18323e5 ro
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-50-generic N/A
   linux-backports-modules-4.15.0-50-generic  N/A
   linux-firmware 1.173.6
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/01/2014
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: Ubuntu-1.8.2-1ubuntu1
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-i440fx-xenial
  dmi.modalias: 
dmi:bvnSeaBIOS:bvrUbuntu-1.8.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-xenial:cvnQEMU:ct1:cvrpc-i440fx-xenial:
  dmi.product.name: Standard PC (i440FX + PIIX, 1996)
  dmi.product.version: pc-i440fx-xenial
  dmi.sys.vendor: QEMU

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

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

[Kernel-packages] [Bug 1834006] Re: cpuset_hotplug from controllers in ubuntu_ltp failed

[Sean Feole]

This bug is also found in linux-aws on Bionic,4.15.0-1057.59-aws

266.12/05 10:33:23 DEBUG| utils:0153| [stdout] startup='Thu Dec 5 10:28:50 
2019'
99267.  12/05 10:33:23 DEBUG| utils:0153| [stdout] cpuset_hotplug 1 TFAIL: 
task's allowed list isn't expected.(Result: 0-14, Expect: 0-1)
99268.  12/05 10:33:23 DEBUG| utils:0153| [stdout] cpuset_hotplug 3 TFAIL: 
task's allowed list isn't expected.(Result: 0-14, Expect: 0-1)
99269.  12/05 10:33:23 DEBUG| utils:0153| [stdout] cpuset_hotplug 5 TPASS: 
Cpuset vs CPU hotplug test succeeded.
99270.  12/05 10:33:23 DEBUG| utils:0153| [stdout] cpuset_hotplug 7 TFAIL: 
task's cpu allowed list isn't expected(Result: 0-14, Expect: 0-1).
99271.  12/05 10:33:23 DEBUG| utils:0153| [stdout] cpuset_hotplug 9 TPASS: 
Cpuset vs CPU hotplug test succeeded.
99272.  12/05 10:33:23 DEBUG| utils:0153| [stdout] cpuset_hotplug 11 TPASS: 
Cpuset vs CPU hotplug test succeeded.
99273.  12/05 10:33:23 DEBUG| utils:0153| [stdout] tag=cpuset_hotplug 
stime=1575541730 dur=1 exit=exited stat=1 core=no cu=17 cs=33
99274.  12/05 10:33:23 DEBUG| utils:0153| [stdout] startup='Thu Dec 5 10:28:52 
2019'

** Summary changed:

- cpuset_hotplug from controllers in ubuntu_ltp failed on D with node amaura
+ cpuset_hotplug from controllers in ubuntu_ltp failed

** Tags added: bionic

** Tags added: sru-20191202

** Tags added: 4.15

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

** No longer affects: linux (Ubuntu Cosmic)

** No longer affects: linux-aws (Ubuntu Cosmic)

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

** Also affects: linux-aws (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/1834006

Title:
  cpuset_hotplug from controllers in ubuntu_ltp failed

Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in linux-aws package in Ubuntu:
  New
Status in linux source package in Bionic:
  New
Status in linux-aws source package in Bionic:
  New
Status in linux source package in Disco:
  New
Status in linux-aws source package in Disco:
  New

Bug description:
  Issue found on node amaura:
  <<>>
  tag=cpuset_hotplug stime=1561372131
  cmdline="cpuset_hotplug_test.sh"
  contacts=""
  analysis=exit
  <<>>
  incrementing stop
  cpuset_hotplug 1 TFAIL: task's allowed list isn't expected.(Result: 0-15, 
Expect: 0-7)
  cpuset_hotplug 3 TFAIL: task's allowed list isn't expected.(Result: 0-15, 
Expect: 0-7)
  cpuset_hotplug 5 TPASS: Cpuset vs CPU hotplug test succeeded.
  cpuset_hotplug 7 TFAIL: task's cpu allowed list isn't expected(Result: 0-15, 
Expect: 0-7).
  cpuset_hotplug 9 TPASS: Cpuset vs CPU hotplug test succeeded.
  cpuset_hotplug 11 TPASS: Cpuset vs CPU hotplug test succeeded.
  <<>>
  initiation_status="ok"
  duration=1 termination_type=exited termination_id=1 corefile=no
  cutime=19 cstime=81
  <<>>

  Test script:
  
https://github.com/linux-test-project/ltp/blob/master/testcases/kernel/controllers/cpuset/cpuset_hotplug_test/cpuset_hotplug_test.sh

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.18.0-22-generic 4.18.0-22.23
  ProcVersionSignature: User Name 4.18.0-22.23-generic 4.18.20
  Uname: Linux 4.18.0-22-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jun 24 10:25 seq
   crw-rw 1 root audio 116, 33 Jun 24 10:25 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.10-0ubuntu13.3
  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:
  Date: Mon Jun 24 10:30:59 2019
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  MachineType: Intel Corporation S1200RP
  PciMultimedia:
   
  ProcFB: 0 mgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-22-generic 
root=UUID=b0d2ae4e-12dd-423e-acea-272ee8b2a893 ro
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-22-generic N/A
   linux-backports-modules-4.18.0-22-generic  N/A
   linux-firmware 1.175.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: 07/01/2015
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: S1200RP.86B.03.02.0003.070120151022
  dmi.board.asset.tag: 
  dmi.board.name: S1200RP
  dmi.board.vendor: Intel Corporation
  dmi.board.version: G62254-407
  dmi.chassis.asset.tag: 
  dmi.chassis.type: 17
  dmi.chassis.vendor: ..
  dmi.chassis.version: ..
  dmi.modalias: 

[Kernel-packages] [Bug 1829849] Re: proc01 in fs from ubuntu_ltp failed with D/B/E

[Sean Feole]

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

** Tags added: sru-20191202

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

Title:
  proc01 in fs from ubuntu_ltp failed with D/B/E

Status in ubuntu-kernel-tests:
  Triaged
Status in linux package in Ubuntu:
  Incomplete
Status in linux-aws package in Ubuntu:
  New

Bug description:
   proc01  0  TINFO  :  /proc/sys/fs/binfmt_misc/register: is write-only.
   proc01  0  TINFO  :  /proc/sys/net/ipv6/conf/all/stable_secret: known 
issue: errno=EIO(5): Input/output error
   proc01  0  TINFO  :  /proc/sys/net/ipv6/conf/default/stable_secret: 
known issue: errno=EIO(5): Input/output error
   proc01  0  TINFO  :  /proc/sys/net/ipv6/conf/ens6/stable_secret: known 
issue: errno=EIO(5): Input/output error
   proc01  0  TINFO  :  /proc/sys/net/ipv6/conf/lo/stable_secret: known 
issue: errno=EIO(5): Input/output error
   proc01  0  TINFO  :  /proc/kmsg: known issue: 
errno=EAGAIN/EWOULDBLOCK(11): Resource temporarily unavailable
   proc01  0  TINFO  :  /proc/sysrq-trigger: is write-only.
   proc01  0  TINFO  :  /proc/self/task/8782/mem: known issue: 
errno=EIO(5): Input/output error
   proc01  0  TINFO  :  /proc/self/task/8782/clear_refs: is write-only.
   proc01  0  TINFO  :  /proc/self/task/8782/pagemap: reached maxmbytes (-m)
   proc01  0  TINFO  :  /proc/self/task/8782/attr/prev: known issue: 
errno=EINVAL(22): Invalid argument
   proc01  0  TINFO  :  /proc/self/task/8782/attr/exec: known issue: 
errno=EINVAL(22): Invalid argument
   proc01  0  TINFO  :  /proc/self/task/8782/attr/fscreate: known issue: 
errno=EINVAL(22): Invalid argument
   proc01  0  TINFO  :  /proc/self/task/8782/attr/keycreate: known issue: 
errno=EINVAL(22): Invalid argument
   proc01  0  TINFO  :  /proc/self/task/8782/attr/sockcreate: known issue: 
errno=EINVAL(22): Invalid argument
   proc01  1  TFAIL  :  proc01.c:397: read failed: 
/proc/self/task/8782/attr/selinux/current: errno=EINVAL(22): Invalid argument
   proc01  2  TFAIL  :  proc01.c:397: read failed: 
/proc/self/task/8782/attr/selinux/prev: errno=EINVAL(22): Invalid argument
   proc01  3  TFAIL  :  proc01.c:397: read failed: 
/proc/self/task/8782/attr/selinux/exec: errno=EINVAL(22): Invalid argument
   proc01  4  TFAIL  :  proc01.c:397: read failed: 
/proc/self/task/8782/attr/selinux/fscreate: errno=EINVAL(22): Invalid argument
   proc01  5  TFAIL  :  proc01.c:397: read failed: 
/proc/self/task/8782/attr/selinux/keycreate: errno=EINVAL(22): Invalid argument
   proc01  6  TFAIL  :  proc01.c:397: read failed: 
/proc/self/task/8782/attr/selinux/sockcreate: errno=EINVAL(22): Invalid argument
   proc01  7  TFAIL  :  proc01.c:397: read failed: 
/proc/self/task/8782/attr/smack/current: errno=EINVAL(22): Invalid argument
   proc01  8  TFAIL  :  proc01.c:397: read failed: 
/proc/self/task/8782/attr/apparmor/prev: errno=EINVAL(22): Invalid argument
   proc01  9  TFAIL  :  proc01.c:397: read failed: 
/proc/self/task/8782/attr/apparmor/exec: errno=EINVAL(22): Invalid argument
   proc01  0  TINFO  :  /proc/self/mem: known issue: errno=EIO(5): 
Input/output error
   proc01  0  TINFO  :  /proc/self/clear_refs: is write-only.
   proc01  0  TINFO  :  /proc/self/pagemap: reached maxmbytes (-m)
   proc01  0  TINFO  :  /proc/self/attr/prev: known issue: 
errno=EINVAL(22): Invalid argument
   proc01  0  TINFO  :  /proc/self/attr/exec: known issue: 
errno=EINVAL(22): Invalid argument
   proc01  0  TINFO  :  /proc/self/attr/fscreate: known issue: 
errno=EINVAL(22): Invalid argument
   proc01  0  TINFO  :  /proc/self/attr/keycreate: known issue: 
errno=EINVAL(22): Invalid argument
   proc01  0  TINFO  :  /proc/self/attr/sockcreate: known issue: 
errno=EINVAL(22): Invalid argument
   proc01 10  TFAIL  :  proc01.c:397: read failed: 
/proc/self/attr/selinux/current: errno=EINVAL(22): Invalid argument
   proc01 11  TFAIL  :  proc01.c:397: read failed: 
/proc/self/attr/selinux/prev: errno=EINVAL(22): Invalid argument
   proc01 12  TFAIL  :  proc01.c:397: read failed: 
/proc/self/attr/selinux/exec: errno=EINVAL(22): Invalid argument
   proc01 13  TFAIL  :  proc01.c:397: read failed: 
/proc/self/attr/selinux/fscreate: errno=EINVAL(22): Invalid argument
   proc01 14  TFAIL  :  proc01.c:397: read failed: 
/proc/self/attr/selinux/keycreate: errno=EINVAL(22): Invalid argument
   proc01 15  TFAIL  :  proc01.c:397: read failed: 
/proc/self/attr/selinux/sockcreate: errno=EINVAL(22): Invalid argument
   proc01 16  TFAIL  :  proc01.c:397: read failed: 
/proc/self/attr/smack/current: errno=EINVAL(22): Invalid argument
   proc01 17  TFAIL  :  proc01.c:397: read failed: 
/proc/self/attr/apparmor/prev: errno=EINVAL(22): Invalid argument
   proc01 18  TFAIL  :  

[Kernel-packages] [Bug 1856370] Re: GPU has fallen off the bus

[Stuardo -StR- Rodríguez]

... but then sound didn't work... weird.. So, what does it meant it
works with your custom kernel?

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

Title:
  GPU has fallen off the bus

Status in linux package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-435 package in Ubuntu:
  New

Bug description:
  Every time I suspend my laptop, after I resume it, a black screen
  shows with the error message

  - GPU has fallen off the bus

  It's a plain vanilla Ubunbtu 19.10 installation on an Dell XPS 15 7590
  with NVIDIA(R) GeForce(R) GTX 1650 4GB GDDR5

  Description:  Ubuntu 19.10
  Release:  19.10
  nvidia driver 435

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  Uname: Linux 5.3.0-24-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  435.21  Sun Aug 25 08:17:57 
CDT 2019
   GCC version:  gcc version 9.2.1 20191008 (Ubuntu 9.2.1-9ubuntu2)
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Dec 13 16:31:58 2019
  DistUpgraded: Fresh install
  DistroCodename: eoan
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 435.21, 5.3.0-18-generic, x86_64: installed
   nvidia, 435.21, 5.3.0-24-generic, x86_64: installed
   virtualbox, 6.0.14, 5.3.0-24-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (prog-if 00 [VGA 
controller])
 Subsystem: Dell UHD Graphics 630 (Mobile) [1028:0905]
 Subsystem: Dell Device [1028:0905]
  InstallationDate: Installed on 2019-12-13 (0 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: Dell Inc. XPS 15 7590
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic 
root=UUID=0b1a4be3-b095-45fc-ae1b-4b6fb7845eb2 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/25/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.3.3
  dmi.board.name: 0VYV0G
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.3.3:bd09/25/2019:svnDellInc.:pnXPS157590:pvr:rvnDellInc.:rn0VYV0G:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 15 7590
  dmi.product.sku: 0905
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.1-1ubuntu1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  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/1856370/+subscriptions

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

[Kernel-packages] [Bug 1856460] PulseList.txt

[soulsacrifire]

apport information

** Attachment added: "PulseList.txt"
   
https://bugs.launchpad.net/bugs/1856460/+attachment/5313051/+files/PulseList.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/1856460

Title:
  [ZenBook UX334FL_UX334FL, Realtek ALC294, Mic, Internal] Microphone
  doesn't work

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

Bug description:
  I have a dual boot system with windows 10.
  In windows I don't find any problem but on Ubuntu the microphone doesn't seem 
to work or be recognized.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: pulseaudio 1:13.0-1ubuntu1
  Uname: Linux 5.3.16-050316-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nesar  2260 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Dec 15 15:04:59 2019
  InstallationDate: Installed on 2019-11-26 (19 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH successful
  Symptom_Card: Audio interno - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nesar  2260 F pulseaudio
  Symptom_Jack: Mic, Internal
  Symptom_PulseAudioRecordingTest: PulseAudio recording test through plughw:PCH 
failed
  Symptom_Type: No sound at all
  Title: [ZenBook UX334FL_UX334FL, Realtek ALC294, Mic, Internal] No sound at 
all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/16/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX334FL.302
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX334FL
  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.:bvrUX334FL.302:bd10/16/2019:svnASUSTeKCOMPUTERINC.:pnZenBookUX334FL_UX334FL:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX334FL:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: ZenBook
  dmi.product.name: ZenBook UX334FL_UX334FL
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nesar  2298 F pulseaudio
   /dev/snd/pcmC0D0p:   nesar  2298 F...m pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2019-11-26 (20 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  Tags:  eoan
  Uname: Linux 5.3.16-050316-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/16/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX334FL.302
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX334FL
  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.:bvrUX334FL.302:bd10/16/2019:svnASUSTeKCOMPUTERINC.:pnZenBookUX334FL_UX334FL:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX334FL:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: ZenBook
  dmi.product.name: ZenBook UX334FL_UX334FL
  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/alsa-driver/+bug/1856460/+subscriptions

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

[Kernel-packages] [Bug 1854819] Re: bionic/linux: 4.15.0-73.82 -proposed tracker

[Sean Feole]

SRU regression testing done, Existing bugs found here:
https://bugs.launchpad.net/ubuntu-kernel-
tests/+bugs?field.tag=sru-20191202

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

Title:
  bionic/linux: 4.15.0-73.82 -proposed tracker

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

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

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

  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
  packages:
lrm: linux-restricted-modules
main: linux
meta: linux-meta
signed: linux-signed
  phase: Testing
  phase-changed: Tuesday, 03. December 2019 15:44 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
regression-testing: Ongoing -- testing in progress
security-signoff: Stalled -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
bionic/linux-aws: bug 1854802
bionic/linux-fips: bug 1854809
bionic/linux-gke-4.15: bug 1854804
bionic/linux-ibm-gt: bug 1854806
bionic/linux-kvm: bug 1854805
bionic/linux-oem: bug 1854797
bionic/linux-oracle: bug 1854808
bionic/linux-raspi2: bug 1854793
bionic/linux-snapdragon: bug 1854796
bionic/linux/pc-kernel: bug 1854790
bionic/linux/pc-lowlatency-kernel: bug 1854791
unknown/unknown: bug 1854806, bug 1854809, bug 1854818, bug 1854808, bug 
1854790,
  bug 1854816, bug 1854791, bug 1854793
xenial/linux-azure: bug 1856203
xenial/linux-gcp: bug 1854816
xenial/linux-hwe: bug 1854818
  variant: debs

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

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

[Kernel-packages] [Bug 1856460] CurrentDmesg.txt

[soulsacrifire]

apport information

** Attachment added: "CurrentDmesg.txt"
   
https://bugs.launchpad.net/bugs/1856460/+attachment/5313049/+files/CurrentDmesg.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/1856460

Title:
  [ZenBook UX334FL_UX334FL, Realtek ALC294, Mic, Internal] Microphone
  doesn't work

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

Bug description:
  I have a dual boot system with windows 10.
  In windows I don't find any problem but on Ubuntu the microphone doesn't seem 
to work or be recognized.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: pulseaudio 1:13.0-1ubuntu1
  Uname: Linux 5.3.16-050316-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nesar  2260 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Dec 15 15:04:59 2019
  InstallationDate: Installed on 2019-11-26 (19 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH successful
  Symptom_Card: Audio interno - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nesar  2260 F pulseaudio
  Symptom_Jack: Mic, Internal
  Symptom_PulseAudioRecordingTest: PulseAudio recording test through plughw:PCH 
failed
  Symptom_Type: No sound at all
  Title: [ZenBook UX334FL_UX334FL, Realtek ALC294, Mic, Internal] No sound at 
all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/16/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX334FL.302
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX334FL
  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.:bvrUX334FL.302:bd10/16/2019:svnASUSTeKCOMPUTERINC.:pnZenBookUX334FL_UX334FL:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX334FL:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: ZenBook
  dmi.product.name: ZenBook UX334FL_UX334FL
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nesar  2298 F pulseaudio
   /dev/snd/pcmC0D0p:   nesar  2298 F...m pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2019-11-26 (20 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  Tags:  eoan
  Uname: Linux 5.3.16-050316-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/16/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX334FL.302
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX334FL
  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.:bvrUX334FL.302:bd10/16/2019:svnASUSTeKCOMPUTERINC.:pnZenBookUX334FL_UX334FL:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX334FL:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: ZenBook
  dmi.product.name: ZenBook UX334FL_UX334FL
  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/alsa-driver/+bug/1856460/+subscriptions

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

[Kernel-packages] [Bug 1856460] AlsaInfo.txt

[soulsacrifire]

apport information

** Attachment added: "AlsaInfo.txt"
   
https://bugs.launchpad.net/bugs/1856460/+attachment/5313048/+files/AlsaInfo.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/1856460

Title:
  [ZenBook UX334FL_UX334FL, Realtek ALC294, Mic, Internal] Microphone
  doesn't work

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

Bug description:
  I have a dual boot system with windows 10.
  In windows I don't find any problem but on Ubuntu the microphone doesn't seem 
to work or be recognized.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: pulseaudio 1:13.0-1ubuntu1
  Uname: Linux 5.3.16-050316-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nesar  2260 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Dec 15 15:04:59 2019
  InstallationDate: Installed on 2019-11-26 (19 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH successful
  Symptom_Card: Audio interno - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nesar  2260 F pulseaudio
  Symptom_Jack: Mic, Internal
  Symptom_PulseAudioRecordingTest: PulseAudio recording test through plughw:PCH 
failed
  Symptom_Type: No sound at all
  Title: [ZenBook UX334FL_UX334FL, Realtek ALC294, Mic, Internal] No sound at 
all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/16/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX334FL.302
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX334FL
  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.:bvrUX334FL.302:bd10/16/2019:svnASUSTeKCOMPUTERINC.:pnZenBookUX334FL_UX334FL:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX334FL:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: ZenBook
  dmi.product.name: ZenBook UX334FL_UX334FL
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nesar  2298 F pulseaudio
   /dev/snd/pcmC0D0p:   nesar  2298 F...m pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2019-11-26 (20 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  Tags:  eoan
  Uname: Linux 5.3.16-050316-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/16/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX334FL.302
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX334FL
  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.:bvrUX334FL.302:bd10/16/2019:svnASUSTeKCOMPUTERINC.:pnZenBookUX334FL_UX334FL:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX334FL:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: ZenBook
  dmi.product.name: ZenBook UX334FL_UX334FL
  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/alsa-driver/+bug/1856460/+subscriptions

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

[Kernel-packages] [Bug 1854824] Re: xenial/linux-aws: 4.4.0-1100.111 -proposed tracker

[Ubuntu Kernel Bot]

** Changed in: kernel-sru-workflow/automated-testing
   Status: In Progress => 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 --
  boot-testing-requested: true
  kernel-stable-master-bug: 1854835
  packages:
main: linux-aws
meta: linux-meta-aws
  phase: Testing
  phase-changed: Wednesday, 04. December 2019 16:11 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   automated-testing: Ongoing -- testing in progress
+   automated-testing: Stalled -- testing FAILED
regression-testing: Ongoing -- testing in progress
security-signoff: Stalled -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
xenial/linux-aws/aws-kernel: bug 1854823
  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/1854824

Title:
  xenial/linux-aws: 4.4.0-1100.111 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow 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:
  In Progress
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow verification-testing series:
  In Progress
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 --
  boot-testing-requested: true
  kernel-stable-master-bug: 1854835
  packages:
main: linux-aws
meta: linux-meta-aws
  phase: Testing
  phase-changed: Wednesday, 04. December 2019 16:11 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Stalled -- testing FAILED
regression-testing: Ongoing -- testing in progress
security-signoff: Stalled -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
xenial/linux-aws/aws-kernel: bug 1854823
  variant: debs

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

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

[Kernel-packages] [Bug 1856460] ProcCpuinfoMinimal.txt

[soulsacrifire]

apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1856460/+attachment/5313050/+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/1856460

Title:
  [ZenBook UX334FL_UX334FL, Realtek ALC294, Mic, Internal] Microphone
  doesn't work

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

Bug description:
  I have a dual boot system with windows 10.
  In windows I don't find any problem but on Ubuntu the microphone doesn't seem 
to work or be recognized.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: pulseaudio 1:13.0-1ubuntu1
  Uname: Linux 5.3.16-050316-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nesar  2260 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Dec 15 15:04:59 2019
  InstallationDate: Installed on 2019-11-26 (19 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH successful
  Symptom_Card: Audio interno - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nesar  2260 F pulseaudio
  Symptom_Jack: Mic, Internal
  Symptom_PulseAudioRecordingTest: PulseAudio recording test through plughw:PCH 
failed
  Symptom_Type: No sound at all
  Title: [ZenBook UX334FL_UX334FL, Realtek ALC294, Mic, Internal] No sound at 
all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/16/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX334FL.302
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX334FL
  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.:bvrUX334FL.302:bd10/16/2019:svnASUSTeKCOMPUTERINC.:pnZenBookUX334FL_UX334FL:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX334FL:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: ZenBook
  dmi.product.name: ZenBook UX334FL_UX334FL
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nesar  2298 F pulseaudio
   /dev/snd/pcmC0D0p:   nesar  2298 F...m pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2019-11-26 (20 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  Tags:  eoan
  Uname: Linux 5.3.16-050316-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/16/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX334FL.302
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX334FL
  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.:bvrUX334FL.302:bd10/16/2019:svnASUSTeKCOMPUTERINC.:pnZenBookUX334FL_UX334FL:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX334FL:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: ZenBook
  dmi.product.name: ZenBook UX334FL_UX334FL
  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/alsa-driver/+bug/1856460/+subscriptions

-- 
Mailing list: https://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 1856460] Re: [ZenBook UX334FL_UX334FL, Realtek ALC294, Mic, Internal] Microphone doesn't work

[soulsacrifire]

Hi Hui,

the problem is regarding the internal mic.

I've tried different versions of kernel, reloaded the alsa drivers but
nothing to do.. This afternnon I tried to remove the nvidia driver and
reinstall the 5.3.16 kernel and now it works fine.

Regards.


Il giorno lun 16 dic 2019 alle ore 08:21 Hui Wang 
ha scritto:

> "the microphone doesn't seem to work or be recognized", do you mean the
> internal mic? it is not recognized? I checked the log in the #1, the
> internal mic is defined, you should be able to see/find the internal mic
> from the gnome-control-center sound-setting.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1856460
>
> Title:
>   [ZenBook UX334FL_UX334FL, Realtek ALC294, Mic, Internal] Microphone
>   doesn't work
>
> Status in alsa-driver package in Ubuntu:
>   New
> Status in linux package in Ubuntu:
>   Incomplete
>
> Bug description:
>   I have a dual boot system with windows 10.
>   In windows I don't find any problem but on Ubuntu the microphone doesn't
> seem to work or be recognized.
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 19.10
>   Package: pulseaudio 1:13.0-1ubuntu1
>   Uname: Linux 5.3.16-050316-generic x86_64
>   ApportVersion: 2.20.11-0ubuntu8.2
>   Architecture: amd64
>   AudioDevicesInUse:
>USERPID ACCESS COMMAND
>/dev/snd/controlC0:  nesar  2260 F pulseaudio
>   CurrentDesktop: ubuntu:GNOME
>   Date: Sun Dec 15 15:04:59 2019
>   InstallationDate: Installed on 2019-11-26 (19 days ago)
>   InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
>   ProcEnviron:
>PATH=(custom, no user)
>XDG_RUNTIME_DIR=
>LANG=it_IT.UTF-8
>SHELL=/bin/bash
>   SourcePackage: pulseaudio
>   Symptom: audio
>   Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH
> successful
>   Symptom_Card: Audio interno - HDA Intel PCH
>   Symptom_DevicesInUse:
>USERPID ACCESS COMMAND
>/dev/snd/controlC0:  nesar  2260 F pulseaudio
>   Symptom_Jack: Mic, Internal
>   Symptom_PulseAudioRecordingTest: PulseAudio recording test through
> plughw:PCH failed
>   Symptom_Type: No sound at all
>   Title: [ZenBook UX334FL_UX334FL, Realtek ALC294, Mic, Internal] No sound
> at all
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   dmi.bios.date: 10/16/2019
>   dmi.bios.vendor: American Megatrends Inc.
>   dmi.bios.version: UX334FL.302
>   dmi.board.asset.tag: ATN12345678901234567
>   dmi.board.name: UX334FL
>   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.:bvrUX334FL.302:bd10/16/2019:svnASUSTeKCOMPUTERINC.:pnZenBookUX334FL_UX334FL:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX334FL:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
>   dmi.product.family: ZenBook
>   dmi.product.name: ZenBook UX334FL_UX334FL
>   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/alsa-driver/+bug/1856460/+subscriptions
>


** Tags added: apport-collected

** Description changed:

  I have a dual boot system with windows 10.
  In windows I don't find any problem but on Ubuntu the microphone doesn't seem 
to work or be recognized.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: pulseaudio 1:13.0-1ubuntu1
  Uname: Linux 5.3.16-050316-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nesar  2260 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Dec 15 15:04:59 2019
  InstallationDate: Installed on 2019-11-26 (19 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH successful
  Symptom_Card: Audio interno - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nesar  2260 F pulseaudio
  Symptom_Jack: Mic, Internal
  Symptom_PulseAudioRecordingTest: PulseAudio recording test through plughw:PCH 
failed
  Symptom_Type: No sound at all
  Title: [ZenBook UX334FL_UX334FL, Realtek ALC294, Mic, Internal] No sound at 
all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/16/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX334FL.302
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX334FL
  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.
  

[Kernel-packages] [Bug 1848193] Re: Fixup tlbie vs store ordering issue on POWER9

[Manoj Iyer]

Fixed by https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1848039

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

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

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

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

** Changed in: ubuntu-power-systems
   Status: Triaged => 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/1848193

Title:
  Fixup tlbie vs store ordering issue on POWER9

Status in The Ubuntu-power-systems project:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Eoan:
  Fix Released

Bug description:
  == Comment: #0 - Michael Ranweiler  - 2019-10-07 01:52:38 ==
  On POWER9, under some circumstances, a broadcast TLB invalidation will fail 
to invalidate the ERAT cache on some threads when there are parallel 
mtpidr/mtlpidr happening on other threads of the same core.  This can cause 
stores to continue to go to a page after it's unmapped.

  The workaround is to force an ERAT flush using PID=0 or LPID=0 tlbie
  flush. This additional TLB flush will cause the ERAT cache
  invalidation. Since we are using PID=0 or LPID=0, we don't get
  filtered out by the TLB snoop filtering logic.

  We need to still follow this up with another tlbie to take care of
  store vs tlbie ordering issue explained in commit: a5d4b5891c2f
  ("powerpc/mm: Fixup tlbie vs store ordering issue on POWER9"). The
  presence of ERAT cache implies we can still get new stores and they
  may miss store queue marking flush.

  The upstream git commits to resolve the problem:

  
https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git/commit/?h=fixes=677733e296b5c7a37c47da391fc70a43dc40bd67

  
https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git/commit/?h=fixes=09ce98cacd51fcd0fa0af2f79d1e1d3192f4cbb0

  
https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git/commit/?h=fixes=047e6575aec71d75b765c22111820c4776cd1c43

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

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

[Kernel-packages] [Bug 1848193] Re: Fixup tlbie vs store ordering issue on POWER9

[Manoj Iyer]

$ uname -a 
Linux bobone 5.3.0-24-generic #26-Ubuntu SMP Thu Nov 14 01:12:58 UTC 2019 
ppc64le ppc64le ppc64le GNU/Linux

$ sudo ./tlbie_test 
start_cpu list:0
number of worker threads:4 + 1 snapshot thread
Allocated address:0x75e53581 + secondary map:0x75e53557
logdir at : /tmp/logdir-26561
Timeout: 1200 seconds
=
 Starting Test
 Mon Dec 16 16:59:06 2019
=

$

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

Title:
  Fixup tlbie vs store ordering issue on POWER9

Status in The Ubuntu-power-systems project:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Eoan:
  Fix Released

Bug description:
  == Comment: #0 - Michael Ranweiler  - 2019-10-07 01:52:38 ==
  On POWER9, under some circumstances, a broadcast TLB invalidation will fail 
to invalidate the ERAT cache on some threads when there are parallel 
mtpidr/mtlpidr happening on other threads of the same core.  This can cause 
stores to continue to go to a page after it's unmapped.

  The workaround is to force an ERAT flush using PID=0 or LPID=0 tlbie
  flush. This additional TLB flush will cause the ERAT cache
  invalidation. Since we are using PID=0 or LPID=0, we don't get
  filtered out by the TLB snoop filtering logic.

  We need to still follow this up with another tlbie to take care of
  store vs tlbie ordering issue explained in commit: a5d4b5891c2f
  ("powerpc/mm: Fixup tlbie vs store ordering issue on POWER9"). The
  presence of ERAT cache implies we can still get new stores and they
  may miss store queue marking flush.

  The upstream git commits to resolve the problem:

  
https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git/commit/?h=fixes=677733e296b5c7a37c47da391fc70a43dc40bd67

  
https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git/commit/?h=fixes=09ce98cacd51fcd0fa0af2f79d1e1d3192f4cbb0

  
https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git/commit/?h=fixes=047e6575aec71d75b765c22111820c4776cd1c43

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

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

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

[Ubuntu Kernel Bot]

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

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1854808
  packages:
main: linux-oracle
meta: linux-meta-oracle
signed: linux-signed-oracle
  phase: Testing
  phase-changed: Thursday, 05. December 2019 22:51 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   automated-testing: Stalled -- testing FAILED
regression-testing: Ongoing -- testing in progress
security-signoff: Stalled -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  variant: debs

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

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

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  In Progress
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow verification-testing series:
  In Progress
Status in linux-oracle package in Ubuntu:
  Invalid
Status in linux-oracle 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: 1854808
  packages:
main: linux-oracle
meta: linux-meta-oracle
signed: linux-signed-oracle
  phase: Testing
  phase-changed: Thursday, 05. December 2019 22:51 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
regression-testing: Ongoing -- testing in progress
security-signoff: Stalled -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  variant: debs

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

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

[Kernel-packages] [Bug 1829995] Re: getaddrinfo_01 from ipv6_lib test suite in LTP failed

[Sean Feole]

affects arm64 Bionic , 4.15.0-73.82-generic/

** Tags added: sru-20191202

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

Title:
  getaddrinfo_01 from ipv6_lib test suite in LTP failed

Status in ubuntu-kernel-tests:
  Triaged
Status in linux package in Ubuntu:
  Incomplete
Status in linux-aws package in Ubuntu:
  New
Status in linux source package in Bionic:
  Incomplete
Status in linux-aws source package in Bionic:
  New
Status in linux source package in Disco:
  New
Status in linux-aws source package in Disco:
  New
Status in linux source package in Eoan:
  New
Status in linux-aws source package in Eoan:
  New

Bug description:
  startup='Wed May 22 08:02:52 2019'
  getaddrinfo_011  TPASS  :  getaddrinfo IPv4 basic lookup
  getaddrinfo_012  TFAIL  :  getaddrinfo_01.c:140: getaddrinfo IPv4 
canonical name ("curly.maas") doesn't match hostname ("curly")
  getaddrinfo_013  TFAIL  :  getaddrinfo_01.c:578: getaddrinfo IPv6 basic 
lookup ("curly") returns -5 ("No address associated with hostname")
  tag=getaddrinfo_01 stime=1558512172 dur=1 exit=exited stat=1 core=no cu=0 cs=0

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-50-generic 4.15.0-50.54
  ProcVersionSignature: User Name 4.15.0-50.54-generic 4.15.18
  Uname: Linux 4.15.0-50-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 May 22 02:57 seq
   crw-rw 1 root audio 116, 33 May 22 02:57 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.6
  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:
  CurrentDmesg:
   
  Date: Wed May 22 08:04:30 2019
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
  PciMultimedia:
   
  ProcFB: 0 cirrusdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-50-generic 
root=UUID=57e8-9e7f-40ee-934e-f1dce18323e5 ro
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-50-generic N/A
   linux-backports-modules-4.15.0-50-generic  N/A
   linux-firmware 1.173.6
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/01/2014
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: Ubuntu-1.8.2-1ubuntu1
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-i440fx-xenial
  dmi.modalias: 
dmi:bvnSeaBIOS:bvrUbuntu-1.8.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-xenial:cvnQEMU:ct1:cvrpc-i440fx-xenial:
  dmi.product.name: Standard PC (i440FX + PIIX, 1996)
  dmi.product.version: pc-i440fx-xenial
  dmi.sys.vendor: QEMU

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

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

[Kernel-packages] [Bug 1748103] Re: apic test in kvm-unit-test failed

[Sean Feole]

In general this test fails usually across all clouds/metals Should be a
higher priority to get this fixed,

12/03 21:30:32 DEBUG| utils:0116| Running 'kvm-ok'
12/03 21:30:32 DEBUG| utils:0153| [stdout] INFO: /dev/kvm exists
12/03 21:30:32 DEBUG| utils:0153| [stdout] KVM acceleration can be used
12/03 21:30:32 DEBUG| utils:0116| Running 
'/home/ubuntu/autotest/client/tmp/ubuntu_kvm_unit_tests/src/kvm-unit-tests/tests/apic'
12/03 21:30:32 DEBUG| utils:0153| [stdout] BUILD_HEAD=e2c275c4
12/03 21:30:33 DEBUG| utils:0153| [stdout] timeout -k 1s --foreground 30 
/usr/bin/qemu-system-x86_64 -nodefaults -device pc-testdev -device 
isa-debug-exit,iobase=0xf4,iosize=0x4 -vnc none -serial stdio -device 
pci-testdev -machine accel=kvm -kernel /tmp/tmp.l8jZuQAnJV -smp 2 -cpu 
qemu64,+x2apic,+tsc-deadline # -initrd /tmp/tmp.97foJOgQOp
12/03 21:30:33 DEBUG| utils:0153| [stderr] qemu-system-x86_64: warning: 
host doesn't support requested feature: CPUID.8001H:ECX.svm [bit 2]
12/03 21:30:33 DEBUG| utils:0153| [stderr] qemu-system-x86_64: warning: 
host doesn't support requested feature: CPUID.8001H:ECX.svm [bit 2]
12/03 21:30:33 DEBUG| utils:0153| [stdout] enabling apic
12/03 21:30:33 DEBUG| utils:0153| [stdout] enabling apic
12/03 21:30:33 DEBUG| utils:0153| [stdout] paging enabled
12/03 21:30:33 DEBUG| utils:0153| [stdout] cr0 = 80010011
12/03 21:30:33 DEBUG| utils:0153| [stdout] cr3 = 45a000
12/03 21:30:33 DEBUG| utils:0153| [stdout] cr4 = 20
12/03 21:30:33 DEBUG| utils:0153| [stdout] apic version: 50014
12/03 21:30:33 DEBUG| utils:0153| [stdout] PASS: apic existence
12/03 21:30:33 DEBUG| utils:0153| [stdout] PASS: xapic id matches cpuid
12/03 21:30:33 DEBUG| utils:0153| [stdout] PASS: writeable xapic id
12/03 21:30:33 DEBUG| utils:0153| [stdout] PASS: non-writeable x2apic id
12/03 21:30:33 DEBUG| utils:0153| [stdout] PASS: sane x2apic id
12/03 21:30:33 DEBUG| utils:0153| [stdout] PASS: x2apic id matches cpuid
12/03 21:30:33 DEBUG| utils:0153| [stdout] PASS: correct xapic id after 
reset
12/03 21:30:33 DEBUG| utils:0153| [stdout] PASS: apic_disable: Local apic 
disabled
12/03 21:30:33 DEBUG| utils:0153| [stdout] PASS: apic_disable: 
CPUID.1H:EDX.APIC[bit 9] is clear
12/03 21:30:33 DEBUG| utils:0153| [stdout] PASS: apic_disable: *0xfee00030: 

12/03 21:30:33 DEBUG| utils:0153| [stdout] PASS: apic_disable: CR8: 0
12/03 21:30:33 DEBUG| utils:0153| [stdout] PASS: apic_disable: CR8: f
12/03 21:30:33 DEBUG| utils:0153| [stdout] PASS: apic_disable: *0xfee00080: 

12/03 21:30:33 DEBUG| utils:0153| [stdout] PASS: apic_disable: Local apic 
enabled in xAPIC mode
12/03 21:30:33 DEBUG| utils:0153| [stdout] PASS: apic_disable: 
CPUID.1H:EDX.APIC[bit 9] is set
12/03 21:30:33 DEBUG| utils:0153| [stdout] PASS: apic_disable: *0xfee00030: 
50014
12/03 21:30:33 DEBUG| utils:0153| [stdout] PASS: apic_disable: *0xfee00080: 0
12/03 21:30:33 DEBUG| utils:0153| [stdout] PASS: apic_disable: *0xfee00080: 
f0
12/03 21:30:33 DEBUG| utils:0153| [stdout] PASS: apic_disable: Local apic 
enabled in x2APIC mode
12/03 21:30:33 DEBUG| utils:0153| [stdout] PASS: apic_disable: 
CPUID.1H:EDX.APIC[bit 9] is set
12/03 21:30:33 DEBUG| utils:0153| [stdout] PASS: apic_disable: *0xfee00030: 

12/03 21:30:33 DEBUG| utils:0153| [stdout] PASS: apic_disable: CR8: 0
12/03 21:30:33 DEBUG| utils:0153| [stdout] PASS: apic_disable: CR8: f
12/03 21:30:33 DEBUG| utils:0153| [stdout] PASS: apic_disable: *0xfee00080: 

12/03 21:30:33 DEBUG| utils:0153| [stdout] x2apic enabled
12/03 21:30:33 DEBUG| utils:0153| [stdout] PASS: x2apic enabled to invalid 
state
12/03 21:30:33 DEBUG| utils:0153| [stdout] PASS: x2apic enabled to apic 
enabled
12/03 21:30:33 DEBUG| utils:0153| [stdout] PASS: x2apic enabled to disabled 
state
12/03 21:30:33 DEBUG| utils:0153| [stdout] PASS: disabled to invalid state
12/03 21:30:33 DEBUG| utils:0153| [stdout] PASS: disabled to x2apic enabled
12/03 21:30:33 DEBUG| utils:0153| [stdout] PASS: apic enabled to invalid 
state
12/03 21:30:33 DEBUG| utils:0153| [stdout] PASS: apicbase: relocate apic
12/03 21:30:33 DEBUG| utils:0153| [stdout] PASS: apicbase: reserved 
physaddr bits
12/03 21:30:33 DEBUG| utils:0153| [stdout] PASS: apicbase: reserved low bits
12/03 21:30:33 DEBUG| utils:0153| [stdout] PASS: self ipi
12/03 21:30:33 DEBUG| utils:0153| [stdout] starting broadcast (x2apic)
12/03 21:30:33 DEBUG| utils:0153| [stdout] PASS: APIC physical broadcast 
address
12/03 21:30:33 DEBUG| utils:0153| [stdout] PASS: APIC physical broadcast 
shorthand
12/03 21:30:33 DEBUG| utils:0153| [stdout] FAIL: PV IPIs testing
12/03 21:30:33 DEBUG| utils:0153| [stdout] PASS: nmi-after-sti
12/03 21:30:49 DEBUG| utils:0153| [stdout] PASS: multiple nmi
12/03 21:30:49 DEBUG| utils:0153| [stdout] PASS: APIC LVT timer 

[Kernel-packages] [Bug 1856370] Re: GPU has fallen off the bus

[Stuardo -StR- Rodríguez]

@kaihengfeng it worked with that kernel. I had to disable secure-boot to
test the custom kernel, but it worked!!

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

Title:
  GPU has fallen off the bus

Status in linux package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-435 package in Ubuntu:
  New

Bug description:
  Every time I suspend my laptop, after I resume it, a black screen
  shows with the error message

  - GPU has fallen off the bus

  It's a plain vanilla Ubunbtu 19.10 installation on an Dell XPS 15 7590
  with NVIDIA(R) GeForce(R) GTX 1650 4GB GDDR5

  Description:  Ubuntu 19.10
  Release:  19.10
  nvidia driver 435

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  Uname: Linux 5.3.0-24-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  435.21  Sun Aug 25 08:17:57 
CDT 2019
   GCC version:  gcc version 9.2.1 20191008 (Ubuntu 9.2.1-9ubuntu2)
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Dec 13 16:31:58 2019
  DistUpgraded: Fresh install
  DistroCodename: eoan
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 435.21, 5.3.0-18-generic, x86_64: installed
   nvidia, 435.21, 5.3.0-24-generic, x86_64: installed
   virtualbox, 6.0.14, 5.3.0-24-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (prog-if 00 [VGA 
controller])
 Subsystem: Dell UHD Graphics 630 (Mobile) [1028:0905]
 Subsystem: Dell Device [1028:0905]
  InstallationDate: Installed on 2019-12-13 (0 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: Dell Inc. XPS 15 7590
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic 
root=UUID=0b1a4be3-b095-45fc-ae1b-4b6fb7845eb2 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/25/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.3.3
  dmi.board.name: 0VYV0G
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.3.3:bd09/25/2019:svnDellInc.:pnXPS157590:pvr:rvnDellInc.:rn0VYV0G:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 15 7590
  dmi.product.sku: 0905
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.1-1ubuntu1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  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/1856370/+subscriptions

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

[Kernel-packages] [Bug 1831043] Re: move_pages12 test from ubuntu_ltp_syscalls failed on X/B/D

[Sean Feole]

Can be found on Bionic ARM64 - 4.15.0-73.82-generic console output above
in previous comment

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

Title:
  move_pages12 test from ubuntu_ltp_syscalls failed on X/B/D

Status in ubuntu-kernel-tests:
  Triaged
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Xenial:
  New
Status in linux source package in Bionic:
  Confirmed
Status in linux source package in Disco:
  New

Bug description:
  This is a new test case landed 8 days ago, but we already have the patch in 
B, and it looks like this is not failing across all the nodes:
  move_pages12.c:114: FAIL: move_pages failed: ENOMEM


  <<>>
  tag=move_pages12 stime=1559209337
  cmdline="move_pages12"
  contacts=""
  analysis=exit
  <<>>
  incrementing stop
  tst_test.c:1096: INFO: Timeout per run is 0h 05m 00s
  move_pages12.c:235: INFO: Free RAM 31883452 kB
  move_pages12.c:253: INFO: Increasing 2048kB hugepages pool on node 0 to 4
  move_pages12.c:263: INFO: Increasing 2048kB hugepages pool on node 1 to 4
  move_pages12.c:179: INFO: Allocating and freeing 4 hugepages on node 0
  move_pages12.c:179: INFO: Allocating and freeing 4 hugepages on node 1
  move_pages12.c:169: PASS: Bug not reproduced
  move_pages12.c:114: FAIL: move_pages failed: ENOMEM
  move_pages12.c:81: FAIL: madvise failed: SUCCESS
  move_pages12.c:81: FAIL: madvise failed: SUCCESS
  
  move_pages12.c:81: FAIL: madvise failed: SUCCESS
  move_pages12.c:81: FAIL: madvise failed: SUCCESS

  Summary:
  passed   1
  failed   998
  skipped  0
  warnings 0
  <<>>
  initiation_status="ok"
  duration=4 termination_type=exited termination_id=1 corefile=no
  cutime=93 cstime=474
  <<>>

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-50-generic 4.15.0-50.54
  ProcVersionSignature: User Name 4.15.0-50.54-generic 4.15.18
  Uname: Linux 4.15.0-50-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 May 30 09:29 seq
   crw-rw 1 root audio 116, 33 May 30 09:29 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.6
  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:
  Date: Thu May 30 09:42:46 2019
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  MachineType: HP ProLiant DL360 Gen9
  PciMultimedia:

  ProcFB: 0 mgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-50-generic 
root=UUID=6422cfdd-2a69-4c0b-9784-6809a77ab980 ro
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-50-generic N/A
   linux-backports-modules-4.15.0-50-generic  N/A
   linux-firmware 1.173.6
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/25/2017
  dmi.bios.vendor: HP
  dmi.bios.version: P89
  dmi.board.name: ProLiant DL360 Gen9
  dmi.board.vendor: HP
  dmi.chassis.type: 23
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrP89:bd04/25/2017:svnHP:pnProLiantDL360Gen9:pvr:rvnHP:rnProLiantDL360Gen9:rvr:cvnHP:ct23:cvr:
  dmi.product.family: ProLiant
  dmi.product.name: ProLiant DL360 Gen9
  dmi.sys.vendor: HP

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

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

[Kernel-packages] [Bug 1831043] Re: move_pages12 test from ubuntu_ltp_syscalls failed on X/B/D

[Sean Feole]

12/09 20:34:48 DEBUG| utils:0153| [stdout] move_pages12.c:263: INFO: Free 
RAM 260417808 kB
12/09 20:34:48 DEBUG| utils:0153| [stdout] move_pages12.c:281: INFO: 
Increasing 2048kB hugepages pool on node 0 to 4
12/09 20:34:48 DEBUG| utils:0153| [stdout] move_pages12.c:291: INFO: 
Increasing 2048kB hugepages pool on node 1 to 4
12/09 20:34:48 DEBUG| utils:0153| [stdout] move_pages12.c:207: INFO: 
Allocating and freeing 4 hugepages on node 0
12/09 20:34:48 DEBUG| utils:0153| [stdout] move_pages12.c:207: INFO: 
Allocating and freeing 4 hugepages on node 1
12/09 20:34:48 DEBUG| utils:0153| [stdout] move_pages12.c:197: PASS: Bug 
not reproduced
12/09 20:34:48 DEBUG| utils:0153| [stdout] move_pages12.c:95: FAIL: madvise 
failed: EIO (5)
12/09 20:34:48 DEBUG| utils:0153| [stdout] move_pages12.c:95: FAIL: madvise 
failed: EIO (5)
12/09 20:34:48 DEBUG| utils:0153| [stdout] move_pages12.c:95: FAIL: madvise 
failed: EIO (5)
12/09 20:34:48 DEBUG| utils:0153| [stdout] move_pages12.c:95: FAIL: madvise 
failed: EIO (5)
12/09 20:34:48 DEBUG| utils:0153| [stdout] move_pages12.c:95: FAIL: madvise 
failed: EIO (5)
12/09 20:34:48 DEBUG| utils:0153| [stdout] move_pages12.c:95: FAIL: madvise 
failed: EIO (5)
12/09 20:34:48 DEBUG| utils:0153| [stdout] move_pages12.c:95: FAIL: madvise 
failed: EIO (5)
12/09 20:34:48 DEBUG| utils:0153| [stdout] move_pages12.c:95: FAIL: madvise 
failed: EIO (5)
12/09 20:34:48 DEBUG| utils:0153| [stdout] move_pages12.c:95: FAIL: madvise 
failed: EIO (5)
12/09 20:34:48 DEBUG| utils:0153| [stdout] move_pages12.c:95: FAIL: madvise 
failed: EIO (5)
12/09 20:34:48 DEBUG| utils:0153| [stdout] move_pages12.c:95: FAIL: madvise 
failed: EIO (5)
12/09 20:34:48 DEBUG| utils:0153| [stdout] move_pages12.c:95: FAIL: madvise 
failed: EIO (5)
12/09 20:34:48 DEBUG| utils:0153| [stdout] move_pages12.c:95: FAIL: madvise 
failed: EIO (5)
12/09 20:34:48 DEBUG| utils:0153| [stdout] move_pages12.c:95: FAIL: madvise 
failed: EIO (5)
12/09 20:34:48 DEBUG| utils:0153| [stdout] move_pages12.c:95: FAIL: madvise 
failed: EIO (5)

** Changed in: ubuntu-kernel-tests
   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/1831043

Title:
  move_pages12 test from ubuntu_ltp_syscalls failed on X/B/D

Status in ubuntu-kernel-tests:
  Triaged
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Xenial:
  New
Status in linux source package in Bionic:
  Confirmed
Status in linux source package in Disco:
  New

Bug description:
  This is a new test case landed 8 days ago, but we already have the patch in 
B, and it looks like this is not failing across all the nodes:
  move_pages12.c:114: FAIL: move_pages failed: ENOMEM


  <<>>
  tag=move_pages12 stime=1559209337
  cmdline="move_pages12"
  contacts=""
  analysis=exit
  <<>>
  incrementing stop
  tst_test.c:1096: INFO: Timeout per run is 0h 05m 00s
  move_pages12.c:235: INFO: Free RAM 31883452 kB
  move_pages12.c:253: INFO: Increasing 2048kB hugepages pool on node 0 to 4
  move_pages12.c:263: INFO: Increasing 2048kB hugepages pool on node 1 to 4
  move_pages12.c:179: INFO: Allocating and freeing 4 hugepages on node 0
  move_pages12.c:179: INFO: Allocating and freeing 4 hugepages on node 1
  move_pages12.c:169: PASS: Bug not reproduced
  move_pages12.c:114: FAIL: move_pages failed: ENOMEM
  move_pages12.c:81: FAIL: madvise failed: SUCCESS
  move_pages12.c:81: FAIL: madvise failed: SUCCESS
  
  move_pages12.c:81: FAIL: madvise failed: SUCCESS
  move_pages12.c:81: FAIL: madvise failed: SUCCESS

  Summary:
  passed   1
  failed   998
  skipped  0
  warnings 0
  <<>>
  initiation_status="ok"
  duration=4 termination_type=exited termination_id=1 corefile=no
  cutime=93 cstime=474
  <<>>

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-50-generic 4.15.0-50.54
  ProcVersionSignature: User Name 4.15.0-50.54-generic 4.15.18
  Uname: Linux 4.15.0-50-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 May 30 09:29 seq
   crw-rw 1 root audio 116, 33 May 30 09:29 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.6
  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:
  Date: Thu May 30 09:42:46 2019
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  MachineType: HP ProLiant DL360 Gen9
  PciMultimedia:

  ProcFB: 0 mgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-50-generic 
root=UUID=6422cfdd-2a69-4c0b-9784-6809a77ab980 ro
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-50-generic N/A
   

[Kernel-packages] [Bug 1856408] Re: zfs-initramfs needs to set FRAMEBUFFER=y

[Sebastien Bacher]

** Tags added: zfs

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

Title:
  zfs-initramfs needs to set FRAMEBUFFER=y

Status in zfs-linux package in Ubuntu:
  New

Bug description:
  The poorly-named 'FRAMEBUFFER' option in initramfs-tools controls
  whether the console_setup and plymouth scripts are included and used
  in the initramfs.  These are required for any initramfs which will be
  prompting for user input: console_setup because without it the user's
  configured keymap will not be set up, and plymouth because you are not
  guaranteed to have working video output in the initramfs without it
  (e.g. some nvidia+UEFI configurations with the default GRUB behavior).

  The zfs initramfs script may need to prompt the user for passphrases
  for encrypted zfs datasets, and we don't know definitively whether
  this is the case or not at the time the initramfs is constructed (and
  it's difficult to dynamically populate initramfs config variables
  anyway), therefore the zfs-initramfs package should just set
  FRAMEBUFFER=yes in a conf snippet the same way that the cryptsetup-
  initramfs package does (/usr/share/initramfs-tools/conf-
  hooks.d/cryptsetup).

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

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

[Kernel-packages] [Bug 1839857] Re: apic tests fail to run (5 unexpected failures)

[Sean Feole]

** Tags added: sru-20191202

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

Title:
  apic tests fail to run (5 unexpected failures)

Status in ubuntu-kernel-tests:
  New
Status in linux-oracle package in Ubuntu:
  New
Status in linux-oracle source package in Xenial:
  New

Bug description:
  Originally Affected: linux-oracle
  Version: 4.15.0-1021.23~16.04.1
  Series: Xenial

  Apic tests appear to fail to run , with a series of test failures
  itself.

  08/09 20:46:23 DEBUG| utils:0153| [stdout] starting broadcast (x2apic)
  08/09 20:46:23 DEBUG| utils:0153| [stdout] PASS: APIC physical broadcast 
address
  08/09 20:46:23 DEBUG| utils:0153| [stdout] PASS: APIC physical broadcast 
shorthand
  08/09 20:46:23 DEBUG| utils:0153| [stdout] FAIL: PV IPIs testing
  08/09 20:46:23 DEBUG| utils:0153| [stdout] PASS: nmi-after-sti
  08/09 20:46:28 DEBUG| utils:0153| [stdout] PASS: multiple nmi
  08/09 20:46:28 DEBUG| utils:0153| [stdout] PASS: APIC LVT timer one shot
  08/09 20:46:28 DEBUG| utils:0153| [stdout] starting apic change mode
  08/09 20:46:28 DEBUG| utils:0153| [stdout] PASS: TMICT value reset
  08/09 20:46:28 DEBUG| utils:0153| [stdout] PASS: TMCCT should have a 
non-zero value
  08/09 20:46:28 DEBUG| utils:0153| [stdout] PASS: TMCCT should have 
reached 0
  08/09 20:46:28 DEBUG| utils:0153| [stdout] PASS: TMCCT should have a 
non-zero value
  08/09 20:46:28 DEBUG| utils:0153| [stdout] PASS: TMCCT should not be 
reset to TMICT value
  08/09 20:46:28 DEBUG| utils:0153| [stdout] PASS: TMCCT should be reset to 
the initial-count
  08/09 20:46:28 DEBUG| utils:0153| [stdout] PASS: TMCCT should not be 
reset to init
  08/09 20:46:28 DEBUG| utils:0153| [stdout] PASS: TMCCT should have reach 
zero
  08/09 20:46:28 DEBUG| utils:0153| [stdout] PASS: TMCCT should stay at zero
  08/09 20:46:28 DEBUG| utils:0153| [stdout] PASS: tsc deadline timer
  08/09 20:46:28 DEBUG| utils:0153| [stdout] PASS: tsc deadline timer 
clearing
  08/09 20:46:28 DEBUG| utils:0153| [stdout] SUMMARY: 51 tests, 5 
unexpected failures
  08/09 20:46:28 DEBUG| utils:0153| [stdout] FAIL apic (51 tests, 5 
unexpected failures)
  08/09 20:46:28 ERROR|  test:0414| Exception escaping from test:
  Traceback (most recent call last):
File "/home/ubuntu/autotest/client/shared/test.py", line 411, in _exec
  _call_test_function(self.execute, *p_args, **p_dargs)
File "/home/ubuntu/autotest/client/shared/test.py", line 823, in 
_call_test_function
  return func(*args, **dargs)
File "/home/ubuntu/autotest/client/shared/test.py", line 291, in execute
  postprocess_profiled_run, args, dargs)
File "/home/ubuntu/autotest/client/shared/test.py", line 212, in 
_call_run_once
  self.run_once(*args, **dargs)
File 
"/home/ubuntu/autotest/client/tests/ubuntu_kvm_unit_tests/ubuntu_kvm_unit_tests.py",
 line 88, in run_once
  raise error.TestError("Test failed for {}".format(test_name))
  TestError: Test failed for apic

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

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

[Kernel-packages] [Bug 1854771] Re: disco/linux-azure: 5.0.0-1028.30 -proposed tracker

[Ubuntu Kernel Bot]

** Changed in: kernel-sru-workflow/regression-testing
   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: 1854788
  packages:
main: linux-azure
meta: linux-meta-azure
signed: linux-signed-azure
  phase: Testing
  phase-changed: Thursday, 05. December 2019 12:52 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   regression-testing: Ongoing -- testing in progress
security-signoff: Stalled -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
bionic/linux-azure: bug 1854770
  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/1854771

Title:
  disco/linux-azure: 5.0.0-1028.30 -proposed tracker

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

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

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

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1854788
  packages:
main: linux-azure
meta: linux-meta-azure
signed: linux-signed-azure
  phase: Testing
  phase-changed: Thursday, 05. December 2019 12:52 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
security-signoff: Stalled -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
bionic/linux-azure: bug 1854770
  variant: debs

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

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

[Kernel-packages] [Bug 1854771] Re: disco/linux-azure: 5.0.0-1028.30 -proposed tracker

[Sean Feole]

** Tags added: regression-testing-passed

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

Title:
  disco/linux-azure: 5.0.0-1028.30 -proposed tracker

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

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

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

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1854788
  packages:
main: linux-azure
meta: linux-meta-azure
signed: linux-signed-azure
  phase: Testing
  phase-changed: Thursday, 05. December 2019 12:52 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
security-signoff: Stalled -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
bionic/linux-azure: bug 1854770
  variant: debs

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

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

[Kernel-packages] [Bug 1799788] Re: linux-kvm image package is missing /boot/config-$abi

[Paolo Pisati]

Ok, disregard my previous comment: config file was  part of linux-image
until kernel signing was implemented - nonetheless, nowadays linux-image
generic doesn't ship the config file anymore - any reason why you don't
install linux-modules? Is this issue still relevant?

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

Title:
  linux-kvm image package is missing /boot/config-$abi

Status in linux-kvm package in Ubuntu:
  New

Bug description:
  $ dpkg -c linux-image-4.18.0-1003-kvm_4.18.0-1003.3_amd64.deb  | grep boot
  drwxr-xr-x root/root 0 2018-10-05 14:30 ./boot/
  -rw--- root/root   4665392 2018-10-05 14:30 ./boot/vmlinuz-4.18.0-1003-kvm
  $

  The linux-kvm package should ship a copy of the kernel config in
  /boot, the same as the other kernel flavors (cf generic).

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

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

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

Title:
  Issue with mousepad

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Recently i had updated my softwares in linux system,after restarting
  the system mousepad stops working. I don't know what is the issue is.

  cat /proc/bus/input/devices

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-72-generic 4.15.0-72.81
  ProcVersionSignature: Ubuntu 4.15.0-72.81-generic 4.15.18
  Uname: Linux 4.15.0-72-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  arthik 1604 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Dec 16 20:51:03 2019
  InstallationDate: Installed on 2018-10-06 (435 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: Dell Inc. Inspiron 15-3567
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-72-generic 
root=UUID=3e8fe954-5e78-409f-9f2a-4b1f5bc42f1f ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-72-generic N/A
   linux-backports-modules-4.15.0-72-generic  N/A
   linux-firmware 1.173.12
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/06/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.3.0
  dmi.board.name: 0FGN4M
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.3.0:bd02/06/2018:svnDellInc.:pnInspiron15-3567:pvr:rvnDellInc.:rn0FGN4M:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 15-3567
  dmi.sys.vendor: Dell Inc.

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

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