[Kernel-packages] [Bug 1859730] Re: [comet lake] Gnome freezes, icons missing, graphics corruption
Comet Lake is a gen9 gpu like Skylake etc, it only needed pci-id's to
gain support. I have the upcoming desktop version ('CML-S') running
without issues, and don't recall seeing issues with the mobile version
either ('CML-U').
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1859730
Title:
[comet lake] Gnome freezes, icons missing, graphics corruption
Status in linux package in Ubuntu:
Confirmed
Status in mesa package in Ubuntu:
New
Status in mutter package in Ubuntu:
New
Bug description:
ack please..
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
Uname: Linux 5.4.11-050411-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.9
Architecture: amd64
CompositorRunning: None
Date: Tue Jan 14 20:17:26 2020
DistUpgraded: Fresh install
DistributionChannelDescriptor:
# This is the distribution channel descriptor for the OEM CDs
# For more information see
http://wiki.ubuntu.com/DistributionChannelDescriptor
canonical-oem-somerville-bionic-amd64-20180608-47+beaver-three-eyed-raven+X92
DistroCodename: bionic
DistroVariant: ubuntu
DkmsStatus:
backport-iwlwifi, 8286, 4.15.0-1042-oem, x86_64: installed
backport-iwlwifi, 8286, 4.15.0-1066-oem, x86_64: installed
ExtraDebuggingInterest: Yes
GpuHangFrequency: Very infrequently
GraphicsCard:
Intel Corporation Device [8086:9bca] (rev 04) (prog-if 00 [VGA controller])
Subsystem: Dell Device [1028:0962]
InstallationDate: Installed on 2020-01-13 (1 days ago)
InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary
20180608-09:38
Lsusb:
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 002: ID 8087:0029 Intel Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Dell Inc. XPS 13 7390
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
LANG=es_CL.UTF-8
SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.11-050411-generic
root=UUID=8fd25548-00af-4395-92f0-5d7d27a54deb ro quiet splash vt.handoff=1
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/25/2019
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.4.0
dmi.board.name: 0377MH
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias:
dmi:bvnDellInc.:bvr1.4.0:bd11/25/2019:svnDellInc.:pnXPS137390:pvr:rvnDellInc.:rn0377MH:rvrA00:cvnDellInc.:ct10:cvr:
dmi.product.family: XPS
dmi.product.name: XPS 13 7390
dmi.product.sku: 0962
dmi.sys.vendor: Dell Inc.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~18.04.3
version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~18.04.3
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel
2:2.99.917+git20171229-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1859730/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1860483] Re: [nouveau] screen background overlaid with scan type artifact in red
and can skip the headers too, if there are no dkms modules that need those -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1860483 Title: [nouveau] screen background overlaid with scan type artifact in red Status in linux package in Ubuntu: Incomplete Status in mesa package in Ubuntu: Incomplete Bug description: My desktop has both it's usual items in place; toolbar on left and desktop icons distributed around the screen. Then there's what appears to be a bunch of scan line, raster line artifacts, in red, laid over my normal background, which is a star field photo on what is ordinarily a black field. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-74.84-generic 4.15.18 Uname: Linux 4.15.0-74-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Jan 21 13:04:20 2020 DistUpgraded: 2018-10-03 14:38:19,863 DEBUG icon theme changed, re-reading DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation G72 [GeForce 7300 LE] [10de:01d1] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell G72 [GeForce 7300 LE] [1028:0405] InstallationDate: Installed on 2016-08-19 (1249 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: Dell Inc. Inspiron 531 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-74-generic root=UUID=08d8f7c1-e351-4abe-8ebe-443d6a751497 ro plymouth:debug=1 quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to bionic on 2018-10-03 (474 days ago) dmi.bios.date: 11/09/2007 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.7 dmi.board.name: 0RY206 dmi.board.vendor: Dell Inc. dmi.board.version: ��� dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnDellInc.:bvr1.0.7:bd11/09/2007:svnDellInc.:pnInspiron531:pvr00:rvnDellInc.:rn0RY206:rvr:cvnDellInc.:ct3:cvrChassisVersion: dmi.product.name: Inspiron 531 dmi.product.version: 00 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.1-1ubuntu1~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Wed Oct 3 10:41:28 2018 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputDell Dell USB Keyboard KEYBOARD, id 8 inputLogitech USB Trackball MOUSE, id 9 xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-0ubuntu0.8 xserver.video_driver: nouveau To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860483/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1860483] Re: [nouveau] screen background overlaid with scan type artifact in red
I know, this is a common question and we should do better to make it clear. You only need the non-lowlatency packages: https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.5-rc7/linux- headers-5.5.0-050500rc7_5.5.0-050500rc7.202001192030_all.deb https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.5-rc7/linux- headers-5.5.0-050500rc7-generic_5.5.0-050500rc7.202001192030_amd64.deb https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.5-rc7/linux-image- unsigned-5.5.0-050500rc7-generic_5.5.0-050500rc7.202001192030_amd64.deb https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.5-rc7/linux- modules-5.5.0-050500rc7-generic_5.5.0-050500rc7.202001192030_amd64.deb -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1860483 Title: [nouveau] screen background overlaid with scan type artifact in red Status in linux package in Ubuntu: Incomplete Status in mesa package in Ubuntu: Incomplete Bug description: My desktop has both it's usual items in place; toolbar on left and desktop icons distributed around the screen. Then there's what appears to be a bunch of scan line, raster line artifacts, in red, laid over my normal background, which is a star field photo on what is ordinarily a black field. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-74.84-generic 4.15.18 Uname: Linux 4.15.0-74-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Jan 21 13:04:20 2020 DistUpgraded: 2018-10-03 14:38:19,863 DEBUG icon theme changed, re-reading DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation G72 [GeForce 7300 LE] [10de:01d1] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell G72 [GeForce 7300 LE] [1028:0405] InstallationDate: Installed on 2016-08-19 (1249 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: Dell Inc. Inspiron 531 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-74-generic root=UUID=08d8f7c1-e351-4abe-8ebe-443d6a751497 ro plymouth:debug=1 quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to bionic on 2018-10-03 (474 days ago) dmi.bios.date: 11/09/2007 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.7 dmi.board.name: 0RY206 dmi.board.vendor: Dell Inc. dmi.board.version: ��� dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnDellInc.:bvr1.0.7:bd11/09/2007:svnDellInc.:pnInspiron531:pvr00:rvnDellInc.:rn0RY206:rvr:cvnDellInc.:ct3:cvrChassisVersion: dmi.product.name: Inspiron 531 dmi.product.version: 00 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.1-1ubuntu1~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Wed Oct 3 10:41:28 2018 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputDell Dell USB Keyboard KEYBOARD, id 8 inputLogitech USB Trackball MOUSE, id 9 xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-0ubuntu0.8 xserver.video_driver: nouveau To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860483/+subscriptions -- Mailing list: https://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 1860483] Re: [nouveau] screen background overlaid with scan type artifact in red
Should I try all the amd64 packages, i.e. headers, images, and modules in both generic and low latency flavors, or is there a specific package? I've pulled down the entire amd64 set, and the headers-all as well. On 1/22/20 6:55 PM, Daniel van Vugt wrote: > Thanks. This is starting to sound like general problems with the nouveau > kernel driver, or maybe GPU memory corruption, since multiple desktop > environments are broken. > > Next please try the latest kernel packages from > https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.5-rc7/ > > ** No longer affects: mutter (Ubuntu) > -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1860483 Title: [nouveau] screen background overlaid with scan type artifact in red Status in linux package in Ubuntu: Incomplete Status in mesa package in Ubuntu: Incomplete Bug description: My desktop has both it's usual items in place; toolbar on left and desktop icons distributed around the screen. Then there's what appears to be a bunch of scan line, raster line artifacts, in red, laid over my normal background, which is a star field photo on what is ordinarily a black field. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-74.84-generic 4.15.18 Uname: Linux 4.15.0-74-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Jan 21 13:04:20 2020 DistUpgraded: 2018-10-03 14:38:19,863 DEBUG icon theme changed, re-reading DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation G72 [GeForce 7300 LE] [10de:01d1] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell G72 [GeForce 7300 LE] [1028:0405] InstallationDate: Installed on 2016-08-19 (1249 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: Dell Inc. Inspiron 531 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-74-generic root=UUID=08d8f7c1-e351-4abe-8ebe-443d6a751497 ro plymouth:debug=1 quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to bionic on 2018-10-03 (474 days ago) dmi.bios.date: 11/09/2007 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.7 dmi.board.name: 0RY206 dmi.board.vendor: Dell Inc. dmi.board.version: ��� dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnDellInc.:bvr1.0.7:bd11/09/2007:svnDellInc.:pnInspiron531:pvr00:rvnDellInc.:rn0RY206:rvr:cvnDellInc.:ct3:cvrChassisVersion: dmi.product.name: Inspiron 531 dmi.product.version: 00 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.1-1ubuntu1~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Wed Oct 3 10:41:28 2018 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputDell Dell USB Keyboard KEYBOARD, id 8 inputLogitech USB Trackball MOUSE, id 9 xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-0ubuntu0.8 xserver.video_driver: nouveau To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860483/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1860559] Re: [18.04.4] System fails to reboot after installation
** Description changed: bionic desktop 20190122 Since bionic 20191211 the system doesn't reboot after installation. After pressing enter to reboot, the system hangs. There is this message printed in a loop on the console: [sdb] tag#0 access beyond end of device 20191211 includes a new kernel and a new gcc This is similar to bug 1840122 in 19.10 which started with the upgrade from kernel 5.0 to kernel 5.2. Although the error message displayed on - the console was different. + the console was different on baremetal, it is identical in a VM. Installing finalrd helps to work around the issue. However in Bionic, finalrd is in universe. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubiquity (not installed) ProcVersionSignature: Ubuntu 5.3.0-28.30~18.04.1-generic 5.3.13 Uname: Linux 5.3.0-28-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.10 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Jan 22 15:17:58 2020 InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper initrd=/casper/initrd quiet splash --- maybe-ubiquity InstallationDate: Installed on 2020-01-22 (0 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Beta amd64 (20200122) SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1860559 Title: [18.04.4] System fails to reboot after installation Status in casper package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in casper source package in Bionic: Confirmed Status in linux source package in Bionic: Confirmed Bug description: bionic desktop 20190122 Since bionic 20191211 the system doesn't reboot after installation. After pressing enter to reboot, the system hangs. There is this message printed in a loop on the console: [sdb] tag#0 access beyond end of device 20191211 includes a new kernel and a new gcc This is similar to bug 1840122 in 19.10 which started with the upgrade from kernel 5.0 to kernel 5.2. Although the error message displayed on the console was different on baremetal, it is identical in a VM. Installing finalrd helps to work around the issue. However in Bionic, finalrd is in universe. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubiquity (not installed) ProcVersionSignature: Ubuntu 5.3.0-28.30~18.04.1-generic 5.3.13 Uname: Linux 5.3.0-28-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.10 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Jan 22 15:17:58 2020 InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper initrd=/casper/initrd quiet splash --- maybe-ubiquity InstallationDate: Installed on 2020-01-22 (0 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Beta amd64 (20200122) SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1860559/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1860559] Re: [18.04.4] System fails to reboot after installation
** Description changed: bionic desktop 20190122 Since bionic 20191211 the system doesn't reboot after installation. After pressing enter to reboot, the system hangs. There is this message printed in a loop on the console: [sdb] tag#0 access beyond end of device 20191211 includes a new kernel and a new gcc This is similar to bug 1840122 in 19.10 which started with the upgrade from kernel 5.0 to kernel 5.2. Although the error message displayed on the console was different. + Installing finalrd helps to work around the issue. However in Bionic, + finalrd is in universe. + ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubiquity (not installed) ProcVersionSignature: Ubuntu 5.3.0-28.30~18.04.1-generic 5.3.13 Uname: Linux 5.3.0-28-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.10 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Jan 22 15:17:58 2020 InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper initrd=/casper/initrd quiet splash --- maybe-ubiquity InstallationDate: Installed on 2020-01-22 (0 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Beta amd64 (20200122) SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) ** Changed in: casper (Ubuntu) Importance: Undecided => Critical ** Changed in: casper (Ubuntu Bionic) Importance: Undecided => Critical ** Changed in: casper (Ubuntu) Status: New => Fix Released ** Changed in: casper (Ubuntu Bionic) Status: New => Confirmed ** Changed in: linux (Ubuntu Bionic) 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/1860559 Title: [18.04.4] System fails to reboot after installation Status in casper package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in casper source package in Bionic: Confirmed Status in linux source package in Bionic: Confirmed Bug description: bionic desktop 20190122 Since bionic 20191211 the system doesn't reboot after installation. After pressing enter to reboot, the system hangs. There is this message printed in a loop on the console: [sdb] tag#0 access beyond end of device 20191211 includes a new kernel and a new gcc This is similar to bug 1840122 in 19.10 which started with the upgrade from kernel 5.0 to kernel 5.2. Although the error message displayed on the console was different. Installing finalrd helps to work around the issue. However in Bionic, finalrd is in universe. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubiquity (not installed) ProcVersionSignature: Ubuntu 5.3.0-28.30~18.04.1-generic 5.3.13 Uname: Linux 5.3.0-28-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.10 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Jan 22 15:17:58 2020 InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper initrd=/casper/initrd quiet splash --- maybe-ubiquity InstallationDate: Installed on 2020-01-22 (0 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Beta amd64 (20200122) SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1860559/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1860559] Re: [18.04.4] System fails to reboot after installation
** Also affects: casper (Ubuntu) Importance: Undecided Status: New ** Description changed: bionic desktop 20190122 Since bionic 20191211 the system doesn't reboot after installation. After pressing enter to reboot, the system hangs. There is this message printed in a loop on the console: [sdb] tag#0 access beyond end of device 20191211 includes a new kernel and a new gcc + + This is similar to bug 1840122 in 19.10 which started with the upgrade + from kernel 5.0 to kernel 5.2. Although the error message displayed on + the console was different. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubiquity (not installed) ProcVersionSignature: Ubuntu 5.3.0-28.30~18.04.1-generic 5.3.13 Uname: Linux 5.3.0-28-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.10 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Jan 22 15:17:58 2020 InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper initrd=/casper/initrd quiet splash --- maybe-ubiquity InstallationDate: Installed on 2020-01-22 (0 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Beta amd64 (20200122) SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1860559 Title: [18.04.4] System fails to reboot after installation Status in casper package in Ubuntu: New Status in linux package in Ubuntu: Fix Released Status in casper source package in Bionic: New Status in linux source package in Bionic: New Bug description: bionic desktop 20190122 Since bionic 20191211 the system doesn't reboot after installation. After pressing enter to reboot, the system hangs. There is this message printed in a loop on the console: [sdb] tag#0 access beyond end of device 20191211 includes a new kernel and a new gcc This is similar to bug 1840122 in 19.10 which started with the upgrade from kernel 5.0 to kernel 5.2. Although the error message displayed on the console was different. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubiquity (not installed) ProcVersionSignature: Ubuntu 5.3.0-28.30~18.04.1-generic 5.3.13 Uname: Linux 5.3.0-28-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.10 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Jan 22 15:17:58 2020 InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper initrd=/casper/initrd quiet splash --- maybe-ubiquity InstallationDate: Installed on 2020-01-22 (0 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Beta amd64 (20200122) SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1860559/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1854842] Re: mlx5_core reports hardware checksum error for padded packets on Mellanox NICs
Hi Mohammad, I have some bad news. The patches are not present in the current SRU cycle and have been delayed until the next SRU cycle. This is not unique to us and this LP bug, everyone has had the same thing happen to them. The reason is that the kernel team are currently spinning kernels for the Ubuntu 18.04.4 ISO image release, which is due in the coming weeks, and wished for a quiet SRU cycle, so it appears that they only applied reverts to known regressions (1x USB regression) and one CVE (a CVE related to intel 915 graphics drivers) to ensure things go smoothly with no regressions for the 18.04.4 release. The problem with this, is that it has delayed all queued up patches for the bionic and the bionic 5.3 HWE kernel, and has delayed fixes being delivered for another 3 weeks. I know that this is frustrating, and I sincerely apologise for the delay. I am also annoyed, since I only found out recently when I manually examined the commits present in the current SRU cycle, and only found 4, when there would normally be several hundred or so. I believe things will go back to normal for the next SRU cycle, and all queued up patches will be incorporated then. As for the timeframe, if we look at: https://kernel.ubuntu.com/, we see a kernel update being built by the kernel team to happen sometime next week, and the update placed into -proposed for us to test between the 3rd and 14th of February. This would put a release around the 17th of February, given no more delays. Again, I apologise for the delay, and I will make sure to let you know when the next 4.15 bionic kernel with the patches is ready to test in -proposed. Thanks, Matthew -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1854842 Title: mlx5_core reports hardware checksum error for padded packets on Mellanox NICs Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Committed Bug description: BugLink: https://bugs.launchpad.net/bugs/1854842 [Impact] On machines equipped with Mellanox NIC's, in this particular case, Mellanox 5 series NICs using the mlx5_core driver, there is a kernel splat when sending large IP packets which have padding at the end. enp6s0f0: hw csum failure CPU: 19 PID: 0 Comm: swapper/19 Not tainted 4.15.0-72-generic Call Trace: dump_stack+0x63/0x8e netdev_rx_csum_fault+0x38/0x40 __skb_checksum_complete+0xbc/0xd0 nf_ip_checksum+0xc3/0xf0 icmp_error+0x27d/0x310 [nf_conntrack_ipv4] nf_conntrack_in+0x15a/0x510 [nf_conntrack] ? __skb_checksum+0x68/0x330 ipv4_conntrack_in+0x1c/0x20 [nf_conntrack_ipv4] nf_hook_slow+0x48/0xc0 ? skb_send_sock+0x50/0x50 ip_rcv+0x301/0x360 ? inet_del_offload+0x40/0x40 __netif_receive_skb_core+0x432/0xb80 __netif_receive_skb+0x18/0x60 ? __netif_receive_skb+0x18/0x60 netif_receive_skb_internal+0x45/0xe0 napi_gro_receive+0xc5/0xf0 mlx5e_handle_rx_cqe+0x48d/0x5e0 [mlx5_core] ? enqueue_task_rt+0x1b4/0x2e0 mlx5e_poll_rx_cq+0xd1/0x8c0 [mlx5_core] mlx5e_napi_poll+0x9d/0x290 [mlx5_core] net_rx_action+0x140/0x3a0 __do_softirq+0xe4/0x2d4 irq_exit+0xc5/0xd0 do_IRQ+0x86/0xe0 common_interrupt+0x8c/0x8c This bug is a further attempt to fix these splats, as there has been previous fixes in LP #1840854 and a series of commits which landed in 4.15.0-67 (LP #1847155) as a part of upstream -stable patches. This bug will also fix the same problems on the new Mellanox CX6 and Bluefield hardware, which has been enabled already via previous upstream -stable patches which landed in LP #1847155. [Fix] This particular issue was fixed for Mellanox series 5 drivers in the following commits: commit 0aa1d18615c163f92935b806dcaff9157645233a Author: Saeed Mahameed Date: Tue Mar 12 00:24:52 2019 -0700 Subject: net/mlx5e: Rx, Fixup skb checksum for packets with tail padding This commit required a minor backport. This commit was selected for upstream -stable in 4.19.76 and 5.0.10. This commit appears to be omitted from "Bionic update: upstream stable patchset 2019-10-07", which is LP #1847155, probably due to requiring a backport. commit db849faa9bef993a1379dc510623f750a72fa7ce Author: Saeed Mahameed Date: Fri May 3 13:14:59 2019 -0700 Subject: net/mlx5e: Rx, Fix checksum calculation for new hardware This commit required a minor backport. This commit was selected for upstream -stable in 5.1.21 and 5.2.4. This commit has already been applied to the disco kernel, as part of stable updates. [Testcase] The following scapy script will reproduce this issue. Run from the machine with the Mellanox series 5 NIC: 1)
[Kernel-packages] [Bug 1858624] Re: precise/linux-lts-trusty: -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: New => Confirmed ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1858625 packages: main: linux-lts-trusty meta: linux-meta-lts-trusty signed: linux-signed-lts-trusty - phase: Holding before Packaging - phase-changed: Tuesday, 07. January 2020 10:16 UTC + phase: Ready for Packaging + phase-changed: Thursday, 23. January 2020 05:21 UTC reason: - prepare-package: Holding -- waiting for master bug + prepare-package: Pending -- version not specified variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lts-trusty in Ubuntu. https://bugs.launchpad.net/bugs/1858624 Title: precise/linux-lts-trusty: -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Confirmed Status in Kernel SRU Workflow prepare-package-meta series: New Status in Kernel SRU Workflow prepare-package-signed series: New Status in Kernel SRU Workflow promote-signing-to-proposed series: New Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-trusty source package in Precise: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1858625 packages: main: linux-lts-trusty meta: linux-meta-lts-trusty signed: linux-signed-lts-trusty phase: Ready for Packaging phase-changed: Thursday, 23. January 2020 05:21 UTC reason: prepare-package: Pending -- version not specified variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1858624/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1858625] Re: trusty/linux: 3.13.0-176.227 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package
Status: Fix Committed => Fix Released
** Changed in: kernel-sru-workflow/promote-to-proposed
Status: New => Confirmed
** Tags added: block-proposed-trusty
** Tags added: block-proposed
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
+ boot-testing-requested: true
packages:
main: linux
meta: linux-meta
signed: linux-signed
- phase: Packaging
- phase-changed: Wednesday, 22. January 2020 18:25 UTC
+ phase: Ready for Promote to Proposed
+ phase-changed: Thursday, 23. January 2020 05:21 UTC
reason:
- prepare-package: Ongoing -- {} package not yet fully built
- promote-to-proposed: Ongoing -- builds not complete in ppa main:building
+ promote-to-proposed: Pending -- ready for review
trackers:
precise/linux-lts-trusty: bug 1858624
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/1858625
Title:
trusty/linux: 3.13.0-176.227 -proposed tracker
Status in Kernel SRU Workflow:
In Progress
Status in Kernel SRU Workflow automated-testing series:
Invalid
Status in Kernel SRU Workflow certification-testing series:
Invalid
Status in Kernel SRU Workflow prepare-package series:
Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
Fix Released
Status in Kernel SRU Workflow promote-signing-to-proposed series:
New
Status in Kernel SRU Workflow promote-to-proposed series:
Confirmed
Status in Kernel SRU Workflow promote-to-security series:
Invalid
Status in Kernel SRU Workflow promote-to-updates series:
New
Status in Kernel SRU Workflow regression-testing series:
New
Status in Kernel SRU Workflow security-signoff series:
Invalid
Status in Kernel SRU Workflow verification-testing series:
New
Status in linux package in Ubuntu:
Invalid
Status in linux source package in Trusty:
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
packages:
main: linux
meta: linux-meta
signed: linux-signed
phase: Ready for Promote to Proposed
phase-changed: Thursday, 23. January 2020 05:21 UTC
reason:
promote-to-proposed: Pending -- ready for review
trackers:
precise/linux-lts-trusty: bug 1858624
variant: debs
To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1858625/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1859730] Re: [comet lake] Gnome freezes, icons missing, graphics corruption
Is this the kernel that ships with the machine? 5.4.11-050411-generic Also is Mesa 19.0 expected to support Comet Lake fully? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1859730 Title: [comet lake] Gnome freezes, icons missing, graphics corruption Status in linux package in Ubuntu: Confirmed Status in mesa package in Ubuntu: New Status in mutter package in Ubuntu: New Bug description: ack please.. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 Uname: Linux 5.4.11-050411-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CompositorRunning: None Date: Tue Jan 14 20:17:26 2020 DistUpgraded: Fresh install DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20180608-47+beaver-three-eyed-raven+X92 DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: backport-iwlwifi, 8286, 4.15.0-1042-oem, x86_64: installed backport-iwlwifi, 8286, 4.15.0-1066-oem, x86_64: installed ExtraDebuggingInterest: Yes GpuHangFrequency: Very infrequently GraphicsCard: Intel Corporation Device [8086:9bca] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0962] InstallationDate: Installed on 2020-01-13 (1 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 Lsusb: Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 8087:0029 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 13 7390 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=es_CL.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.11-050411-generic root=UUID=8fd25548-00af-4395-92f0-5d7d27a54deb ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/25/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.4.0 dmi.board.name: 0377MH dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.4.0:bd11/25/2019:svnDellInc.:pnXPS137390:pvr:rvnDellInc.:rn0377MH:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 7390 dmi.product.sku: 0962 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~18.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~18.04.3 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1859730/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1859730] Re: [comet lake] Gnome freezes, icons missing, graphics corruption
SSD or FS corruption doesn't seem to appear in the original kernel log attached to this bug. I suspect that's a new issue and not the cause of this bug, but it might be... -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1859730 Title: [comet lake] Gnome freezes, icons missing, graphics corruption Status in linux package in Ubuntu: Confirmed Status in mesa package in Ubuntu: New Status in mutter package in Ubuntu: New Bug description: ack please.. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 Uname: Linux 5.4.11-050411-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CompositorRunning: None Date: Tue Jan 14 20:17:26 2020 DistUpgraded: Fresh install DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20180608-47+beaver-three-eyed-raven+X92 DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: backport-iwlwifi, 8286, 4.15.0-1042-oem, x86_64: installed backport-iwlwifi, 8286, 4.15.0-1066-oem, x86_64: installed ExtraDebuggingInterest: Yes GpuHangFrequency: Very infrequently GraphicsCard: Intel Corporation Device [8086:9bca] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0962] InstallationDate: Installed on 2020-01-13 (1 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 Lsusb: Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 8087:0029 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 13 7390 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=es_CL.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.11-050411-generic root=UUID=8fd25548-00af-4395-92f0-5d7d27a54deb ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/25/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.4.0 dmi.board.name: 0377MH dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.4.0:bd11/25/2019:svnDellInc.:pnXPS137390:pvr:rvnDellInc.:rn0377MH:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 7390 dmi.product.sku: 0962 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~18.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~18.04.3 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1859730/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1859730] Re: [comet lake] Gnome freezes, icons missing, graphics corruption
yep, best to get it serviced -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1859730 Title: [comet lake] Gnome freezes, icons missing, graphics corruption Status in linux package in Ubuntu: Confirmed Status in mesa package in Ubuntu: New Status in mutter package in Ubuntu: New Bug description: ack please.. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 Uname: Linux 5.4.11-050411-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CompositorRunning: None Date: Tue Jan 14 20:17:26 2020 DistUpgraded: Fresh install DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20180608-47+beaver-three-eyed-raven+X92 DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: backport-iwlwifi, 8286, 4.15.0-1042-oem, x86_64: installed backport-iwlwifi, 8286, 4.15.0-1066-oem, x86_64: installed ExtraDebuggingInterest: Yes GpuHangFrequency: Very infrequently GraphicsCard: Intel Corporation Device [8086:9bca] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0962] InstallationDate: Installed on 2020-01-13 (1 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 Lsusb: Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 8087:0029 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 13 7390 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=es_CL.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.11-050411-generic root=UUID=8fd25548-00af-4395-92f0-5d7d27a54deb ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/25/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.4.0 dmi.board.name: 0377MH dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.4.0:bd11/25/2019:svnDellInc.:pnXPS137390:pvr:rvnDellInc.:rn0377MH:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 7390 dmi.product.sku: 0962 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~18.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~18.04.3 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1859730/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1859730] Re: [comet lake] Gnome freezes, icons missing, graphics corruption
Hello, 7 days ago I received the notebook and the bios was version 1.2 and automatically updated to 1.4. dell support doesn't respond yet but since I tried 3 OS (ubuntu 18, fedora 31 and ubuntu 20.04) and all three failed in the same way, it could point to a problem of Hw that can be the Ssd. I attach new photos ... ** Attachment added: "WhatsApp Image 2020-01-23 at 01.30.27(2).jpeg" https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1859730/+attachment/5322278/+files/WhatsApp%20Image%202020-01-23%20at%2001.30.27%282%29.jpeg -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1859730 Title: [comet lake] Gnome freezes, icons missing, graphics corruption Status in linux package in Ubuntu: Confirmed Status in mesa package in Ubuntu: New Status in mutter package in Ubuntu: New Bug description: ack please.. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 Uname: Linux 5.4.11-050411-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CompositorRunning: None Date: Tue Jan 14 20:17:26 2020 DistUpgraded: Fresh install DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20180608-47+beaver-three-eyed-raven+X92 DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: backport-iwlwifi, 8286, 4.15.0-1042-oem, x86_64: installed backport-iwlwifi, 8286, 4.15.0-1066-oem, x86_64: installed ExtraDebuggingInterest: Yes GpuHangFrequency: Very infrequently GraphicsCard: Intel Corporation Device [8086:9bca] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0962] InstallationDate: Installed on 2020-01-13 (1 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 Lsusb: Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 8087:0029 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 13 7390 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=es_CL.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.11-050411-generic root=UUID=8fd25548-00af-4395-92f0-5d7d27a54deb ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/25/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.4.0 dmi.board.name: 0377MH dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.4.0:bd11/25/2019:svnDellInc.:pnXPS137390:pvr:rvnDellInc.:rn0377MH:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 7390 dmi.product.sku: 0962 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~18.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~18.04.3 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1859730/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1854887] Re: cifs: DFS Caching feature causing problems traversing multi-tier DFS setups
Verification for disco. I went and installed 5.0.0-40-generic from -proposed to a disco box: $ uname -rv 5.0.0-40-generic #44-Ubuntu SMP Wed Jan 15 02:03:45 UTC 2020 I do not have access to a multi tier cifs mount, so I will try and connect to a known one with a bad username / password to ensure that the server forwarding and caching works as expected, since that occurs before authentication. I enabled tracing with: # modprobe cifs # echo 'module cifs +p' > /sys/kernel/debug/dynamic_debug/control # echo 'file fs/cifs/* +p' > /sys/kernel/debug/dynamic_debug/control # echo 7 > /proc/fs/cifs/cifsFYI To mount a cifs share, you need cifs-utils: $ sudo apt install cifs-utils >From there I accessed the multi tier cifs server: $ sudo mount -v -t cifs / -o defaults,user=aaa /mnt/share Checking dmesg we get: Status code returned 0xc257 STATUS_PATH_NOT_COVERED fs/cifs/smb2maperror.c: Mapping SMB2 status code 0xc257 to POSIX err -66 fs/cifs/connect.c: build_unc_path_to_root: full_path=\\\Root\Country\ fs/cifs/connect.c: build_unc_path_to_root: full_path=\\\Root\Country\ fs/cifs/dfs_cache.c: do_dfs_cache_find: search path: \\Root\Country\ fs/cifs/dfs_cache.c: do_dfs_cache_find: cache miss fs/cifs/dfs_cache.c: do_dfs_cache_find: DFS referral request for \\Root\Country\ fs/cifs/smb2ops.c: smb2_get_dfs_refer path <\\Root\Country\> fs/cifs/misc.c: num_referrals: 1 dfs flags: 0x2 ... fs/cifs/dns_resolve.c: dns_resolve_server_name_to_ip: resolved: to fs/cifs/connect.c: Username: aaa This is in line with what is expected, since it resolves the next tier file server instead of failing and going back up the tree. I had also previously supplied the customer with a test build based on the previous bionic hwe kernel, 5.0.0-37-generic #40~18.04.1, with the commit applied, and all was tested and working. With my verification of disco kernel from -proposed the customer's prior test kernel, I am happy to mark this as verified. Next, I just need this patch to land in eoan, and then into a bionic HWE kernel to get this fixed for the customer. ** Tags removed: verification-needed-disco ** Tags added: verification-done-disco -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1854887 Title: cifs: DFS Caching feature causing problems traversing multi-tier DFS setups Status in linux package in Ubuntu: Fix Released Status in linux source package in Disco: Fix Committed Status in linux source package in Eoan: Fix Committed Status in linux source package in Focal: Fix Released Bug description: BugLink: https://bugs.launchpad.net/bugs/1854887 [Impact] There is a problem where kernels 5.0-rc1 and onwards cannot mount a multi tier cifs DFS setup, while kernels 4.20 and below can mount the share fine. The DFS tiering structure looks like this: Domain virtual DFS (i.e. \\company.com\folders\share) |-- Domain controller DFS (i.e. \\regional-dc.company.com\folders\share) |-- Regional DFS Server (i.e. \\regional-dfs.company.com\folders\share) |-- Actual file server (i.e. \\regional-svr.company.com\share) On the 5.x series kernels, after getting the DFS referrals list through to the Regional DFS Server, which responds with the correct server/share, instead of going to the Actual file server, the kernel backtracks from the Regional DFS Server back to the Domain controller and requests the share there. Of course, this share does not exist on the Domain controller, as it only exists on the Actual file server, and the connection dies. We have collected a packet capture, and the flow looks like this: Legend: -- DC = Domain Controller / Domain DFS Root RDC = Regional Domain Controller / Domain DFS Root RDS = Regional DFS Server AFS = Actual File Server 4.18.0-21-generic Ubuntu kernel - Good Host: request/response DC: company.com\folders DC: Referral List RDC:start convo RDC:\Folders\Country\ referral RDC:\Folders\Country\ referral RDS:start convo RDS:\Root\Country\ RDS:STATUS_PATH_NOT_COVERED RDS:request referrals RDS:Referral List AFS:convo started AFS:\ AFS:Good response 5.0.0-26-generic Ubuntu kernel - Bad Host: request/response DC: company.com\folders RDC:start convo RDC:\Folders\Country\ RDC:STATUS_PATH_NOT_COVERED RDS:start convo RDS:\Root\Country\ RDS:STATUS_PATH_NOT_COVERED RDC:\Root\Country\ RDC:STATUS_PATH_NOT_COVERED From there the debugging output was more or less the same between the two kernel versions, until the problematic area: Linux 4.18: Full log: https://paste.ubuntu.com/p/D9XwBbvTXc/
[Kernel-packages] [Bug 1859730] Re: [comet lake] Gnome freezes, icons missing, graphics corruption
The platform has gone through extensive testing when it was certified by us, so I wonder if the hw is faulty somehow, or if there's a BIOS update available that might help? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1859730 Title: [comet lake] Gnome freezes, icons missing, graphics corruption Status in linux package in Ubuntu: Confirmed Status in mesa package in Ubuntu: New Status in mutter package in Ubuntu: New Bug description: ack please.. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 Uname: Linux 5.4.11-050411-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CompositorRunning: None Date: Tue Jan 14 20:17:26 2020 DistUpgraded: Fresh install DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20180608-47+beaver-three-eyed-raven+X92 DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: backport-iwlwifi, 8286, 4.15.0-1042-oem, x86_64: installed backport-iwlwifi, 8286, 4.15.0-1066-oem, x86_64: installed ExtraDebuggingInterest: Yes GpuHangFrequency: Very infrequently GraphicsCard: Intel Corporation Device [8086:9bca] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0962] InstallationDate: Installed on 2020-01-13 (1 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 Lsusb: Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 8087:0029 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 13 7390 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=es_CL.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.11-050411-generic root=UUID=8fd25548-00af-4395-92f0-5d7d27a54deb ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/25/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.4.0 dmi.board.name: 0377MH dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.4.0:bd11/25/2019:svnDellInc.:pnXPS137390:pvr:rvnDellInc.:rn0377MH:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 7390 dmi.product.sku: 0962 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~18.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~18.04.3 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1859730/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1850130] Re: zpools fail to import after reboot on fresh install of eoan
Same problem, but pool did was not attached when system was initialized. Fresh install of 19.10 using Ubuntu installer with ZFS root. Pool exported from another system (also running 19.10, but with a "normal" ext4 boot drive). Attached to new host, imported just fine. Reboot and pool is not imported. Refreshed the zpool cache. Same behavior. Added requirements for mpath per comment #6. Same behavior. As a workaround, tried setting ZPOOL_IMPORT_ALL_VISIBLE='yes' in /etc/defaults/zfs. No change. Even if this had worked it is at best a workaround due to possibly importing unwanted pools. -- 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/1850130 Title: zpools fail to import after reboot on fresh install of eoan Status in zfs-linux package in Ubuntu: Confirmed Bug description: Fresh installation of stock Ubuntu 19.10 Eoan with experimental root on ZFS. System has existing zpools with data. Installation is uneventful. First boot with no problems. Updates applied. No other changes from fresh installation. Reboot. External pool 'tank' imports with no errors. Reboot. External pool has failed to import on boot. In contrast bpool and rpool are ok. Manually re-import 'tank' with no issues. I can see both 'tank' and its path in /dev/disk/by-id/ in /etc/zfs/zpool.cache. Reboot. 'tank' has failed to import on boot. It is also missing from /etc/zfs/zpool.cache. Is it possible that the cache is being re- generated on reboot, and the newly imported pools are getting erased from it? I can re-import the pools again manually with no issues, but they don't persist between re-boots. Installing normally on ext4 this is not an issue and data pools import automatically on boot with no further effort. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1850130/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1860621] Status changed to Confirmed
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/1860621 Title: Acer Predator Helios 300 Touchpad not recognized after kernel upgrade. Status in linux package in Ubuntu: Confirmed Bug description: My touchpad Stopped Working After i upgraded to 20.04 2 days ago. I'm using an external mouse which works. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-9-generic 5.4.0-9.12 ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3 Uname: Linux 5.4.0-9-generic x86_64 ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: hamza 5957 F pulseaudio /dev/snd/controlC1: hamza 5957 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Jan 23 07:29:23 2020 InstallationDate: Installed on 2019-11-24 (59 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0408:a060 Quanta Computer, Inc. HD Webcam Bus 001 Device 002: ID 04ca:3016 Lite-On Technology Corp. Bus 001 Device 004: ID 12cf:0390 DEXIN Predator Gaming Mouse PMW 730 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Acer Predator G3-571 ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-9-generic root=UUID=e4f2e8e9-32cf-43bb-b96b-226e6b0c8767 ro recovery nomodeset RelatedPackageVersions: linux-restricted-modules-5.4.0-9-generic N/A linux-backports-modules-5.4.0-9-generic N/A linux-firmware 1.184 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/27/2017 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.14 dmi.board.asset.tag: Type2 - Board Serial Number dmi.board.name: Sienta_KLS dmi.board.vendor: KBL dmi.board.version: V1.14 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.14 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.14:bd12/27/2017:svnAcer:pnPredatorG3-571:pvrV1.14:rvnKBL:rnSienta_KLS:rvrV1.14:cvnAcer:ct10:cvrV1.14: dmi.product.family: Predator Helios 300 dmi.product.name: Predator G3-571 dmi.product.sku: dmi.product.version: V1.14 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860621/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1860621] [NEW] Acer Predator Helios 300 Touchpad not recognized after kernel upgrade.
Public bug reported: My touchpad Stopped Working After i upgraded to 20.04 2 days ago. I'm using an external mouse which works. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-9-generic 5.4.0-9.12 ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3 Uname: Linux 5.4.0-9-generic x86_64 ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: hamza 5957 F pulseaudio /dev/snd/controlC1: hamza 5957 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Jan 23 07:29:23 2020 InstallationDate: Installed on 2019-11-24 (59 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0408:a060 Quanta Computer, Inc. HD Webcam Bus 001 Device 002: ID 04ca:3016 Lite-On Technology Corp. Bus 001 Device 004: ID 12cf:0390 DEXIN Predator Gaming Mouse PMW 730 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Acer Predator G3-571 ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-9-generic root=UUID=e4f2e8e9-32cf-43bb-b96b-226e6b0c8767 ro recovery nomodeset RelatedPackageVersions: linux-restricted-modules-5.4.0-9-generic N/A linux-backports-modules-5.4.0-9-generic N/A linux-firmware 1.184 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/27/2017 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.14 dmi.board.asset.tag: Type2 - Board Serial Number dmi.board.name: Sienta_KLS dmi.board.vendor: KBL dmi.board.version: V1.14 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.14 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.14:bd12/27/2017:svnAcer:pnPredatorG3-571:pvrV1.14:rvnKBL:rnSienta_KLS:rvrV1.14:cvnAcer:ct10:cvrV1.14: dmi.product.family: Predator Helios 300 dmi.product.name: Predator G3-571 dmi.product.sku: dmi.product.version: V1.14 dmi.sys.vendor: Acer ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ** Attachment added: "All files Attached" https://bugs.launchpad.net/bugs/1860621/+attachment/5322247/+files/About.zip -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1860621 Title: Acer Predator Helios 300 Touchpad not recognized after kernel upgrade. Status in linux package in Ubuntu: New Bug description: My touchpad Stopped Working After i upgraded to 20.04 2 days ago. I'm using an external mouse which works. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-9-generic 5.4.0-9.12 ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3 Uname: Linux 5.4.0-9-generic x86_64 ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: hamza 5957 F pulseaudio /dev/snd/controlC1: hamza 5957 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Jan 23 07:29:23 2020 InstallationDate: Installed on 2019-11-24 (59 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0408:a060 Quanta Computer, Inc. HD Webcam Bus 001 Device 002: ID 04ca:3016 Lite-On Technology Corp. Bus 001 Device 004: ID 12cf:0390 DEXIN Predator Gaming Mouse PMW 730 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Acer Predator G3-571 ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-9-generic root=UUID=e4f2e8e9-32cf-43bb-b96b-226e6b0c8767 ro recovery nomodeset RelatedPackageVersions: linux-restricted-modules-5.4.0-9-generic N/A linux-backports-modules-5.4.0-9-generic N/A linux-firmware 1.184 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/27/2017 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.14 dmi.board.asset.tag: Type2 - Board Serial Number dmi.board.name: Sienta_KLS dmi.board.vendor: KBL dmi.board.version: V1.14 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.14 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.14:bd12/27/2017:svnAcer:pnPredatorG3-571:pvrV1.14:rvnKBL:rnSienta_KLS:rvrV1.14:cvnAcer:ct10:cvrV1.14: dmi.product.family: Predator Helios 300 dmi.product.name: Predator G3-571 dmi.product.sku: dmi.product.version: V1.14 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860621/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe :
[Kernel-packages] [Bug 1859730] Status changed to Confirmed
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/1859730 Title: [comet lake] Gnome freezes, icons missing, graphics corruption Status in linux package in Ubuntu: Confirmed Status in mesa package in Ubuntu: New Status in mutter package in Ubuntu: New Bug description: ack please.. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 Uname: Linux 5.4.11-050411-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CompositorRunning: None Date: Tue Jan 14 20:17:26 2020 DistUpgraded: Fresh install DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20180608-47+beaver-three-eyed-raven+X92 DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: backport-iwlwifi, 8286, 4.15.0-1042-oem, x86_64: installed backport-iwlwifi, 8286, 4.15.0-1066-oem, x86_64: installed ExtraDebuggingInterest: Yes GpuHangFrequency: Very infrequently GraphicsCard: Intel Corporation Device [8086:9bca] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0962] InstallationDate: Installed on 2020-01-13 (1 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 Lsusb: Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 8087:0029 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 13 7390 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=es_CL.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.11-050411-generic root=UUID=8fd25548-00af-4395-92f0-5d7d27a54deb ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/25/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.4.0 dmi.board.name: 0377MH dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.4.0:bd11/25/2019:svnDellInc.:pnXPS137390:pvr:rvnDellInc.:rn0377MH:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 7390 dmi.product.sku: 0962 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~18.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~18.04.3 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1859730/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1860483] Re: [nouveau] screen background overlaid with scan type artifact in red
Thanks. This is starting to sound like general problems with the nouveau kernel driver, or maybe GPU memory corruption, since multiple desktop environments are broken. Next please try the latest kernel packages from https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.5-rc7/ ** No longer affects: mutter (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1860483 Title: [nouveau] screen background overlaid with scan type artifact in red Status in linux package in Ubuntu: Incomplete Status in mesa package in Ubuntu: Incomplete Bug description: My desktop has both it's usual items in place; toolbar on left and desktop icons distributed around the screen. Then there's what appears to be a bunch of scan line, raster line artifacts, in red, laid over my normal background, which is a star field photo on what is ordinarily a black field. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-74.84-generic 4.15.18 Uname: Linux 4.15.0-74-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Jan 21 13:04:20 2020 DistUpgraded: 2018-10-03 14:38:19,863 DEBUG icon theme changed, re-reading DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation G72 [GeForce 7300 LE] [10de:01d1] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell G72 [GeForce 7300 LE] [1028:0405] InstallationDate: Installed on 2016-08-19 (1249 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: Dell Inc. Inspiron 531 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-74-generic root=UUID=08d8f7c1-e351-4abe-8ebe-443d6a751497 ro plymouth:debug=1 quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to bionic on 2018-10-03 (474 days ago) dmi.bios.date: 11/09/2007 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.7 dmi.board.name: 0RY206 dmi.board.vendor: Dell Inc. dmi.board.version: ��� dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnDellInc.:bvr1.0.7:bd11/09/2007:svnDellInc.:pnInspiron531:pvr00:rvnDellInc.:rn0RY206:rvr:cvnDellInc.:ct3:cvrChassisVersion: dmi.product.name: Inspiron 531 dmi.product.version: 00 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.1-1ubuntu1~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Wed Oct 3 10:41:28 2018 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputDell Dell USB Keyboard KEYBOARD, id 8 inputLogitech USB Trackball MOUSE, id 9 xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-0ubuntu0.8 xserver.video_driver: nouveau To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860483/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1860204] Re: GNOME3 notification background layer paints over notification text if mouse is moved in notification area
Thanks. It looks like broken damage tracking, maybe relating to a software cursor? Though I'm not sure why you would have a software cursor when the graphics driver is working properly. ** Tags added: nvidia ** Summary changed: - GNOME3 notification background layer paints over notification text if mouse is moved in notification area + [nvidia] GNOME3 notification background layer paints over notification text if mouse is moved in notification area ** Also affects: mutter (Ubuntu) Importance: Undecided Status: New ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => New ** Also affects: nvidia-graphics-drivers-435 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-435 in Ubuntu. https://bugs.launchpad.net/bugs/1860204 Title: [nvidia] GNOME3 notification background layer paints over notification text if mouse is moved in notification area Status in gnome-shell package in Ubuntu: New Status in mutter package in Ubuntu: New Status in nvidia-graphics-drivers-435 package in Ubuntu: New Bug description: Hello, I do not know if it is a problem of the current proprietary driver or xorg or GNOME. I tried my best to include all the info you might need. Problem: When I receive a notification in the notification centre of GNOME, it shows up in the notification bubble. If the text in the notification bubble is longer than the amount of text can be shown at once, the it needs to be opened. If I click on the bubble, it opens, but if I move my mouse pointer inside the said notification the light greyish background color of the notification area paints over the text rendering it to be unreadable. If I wait some seconds then this 'layer' disappears partly or completely. Since my VGA works fine under heavy load (GPU intensive applications and games) I guess it is a software related bug --- Release: 19.10 xorg: Installed: 1:7.7+19ubuntu12 Candidate: 1:7.7+19ubuntu12 NVIDIA Driver Version: 435.21 VGA: GTX 960 4GB ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13 Uname: Linux 5.3.0-26-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..07.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:07: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: Sat Jan 18 11:21:51 2020 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-26-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GM206 [GeForce GTX 960] [10de:1401] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd GM206 [GeForce GTX 960] [1458:36c2] InstallationDate: Installed on 2020-01-17 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Gigabyte Technology Co., Ltd. X570 AORUS ELITE ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-26-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/06/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F11 dmi.board.asset.tag: Default string dmi.board.name: X570 AORUS ELITE dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF11:bd12/06/2019:svnGigabyteTechnologyCo.,Ltd.:pnX570AORUSELITE:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnX570AORUSELITE:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: X570 AORUS ELITE dmi.product.sku: Default string dmi.product.version: -CF dmi.sys.vendor: Gigabyte Technology Co., Ltd. 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 N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core
[Kernel-packages] [Bug 1858625] Re: trusty/linux: 3.13.0-176.227 -proposed tracker
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
packages:
main: linux
meta: linux-meta
signed: linux-signed
phase: Packaging
phase-changed: Wednesday, 22. January 2020 18:25 UTC
reason:
prepare-package: Ongoing -- {} package not yet fully built
- promote-to-proposed: Pending -- builds not complete in ppa
main:building,signed:queued
+ promote-to-proposed: Ongoing -- builds not complete in ppa main:building
trackers:
precise/linux-lts-trusty: bug 1858624
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/1858625
Title:
trusty/linux: 3.13.0-176.227 -proposed tracker
Status in Kernel SRU Workflow:
In Progress
Status in Kernel SRU Workflow automated-testing series:
Invalid
Status in Kernel SRU Workflow certification-testing series:
Invalid
Status in Kernel SRU Workflow prepare-package series:
Fix Committed
Status in Kernel SRU Workflow prepare-package-meta series:
Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
Fix Released
Status in Kernel SRU Workflow promote-signing-to-proposed series:
New
Status in Kernel SRU Workflow promote-to-proposed series:
New
Status in Kernel SRU Workflow promote-to-security series:
Invalid
Status in Kernel SRU Workflow promote-to-updates series:
New
Status in Kernel SRU Workflow regression-testing series:
New
Status in Kernel SRU Workflow security-signoff series:
Invalid
Status in Kernel SRU Workflow verification-testing series:
New
Status in linux package in Ubuntu:
Invalid
Status in linux source package in Trusty:
Confirmed
Bug description:
This bug will contain status and test results related to a kernel
source (or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
packages:
main: linux
meta: linux-meta
signed: linux-signed
phase: Packaging
phase-changed: Wednesday, 22. January 2020 18:25 UTC
reason:
prepare-package: Ongoing -- {} package not yet fully built
promote-to-proposed: Ongoing -- builds not complete in ppa main:building
trackers:
precise/linux-lts-trusty: bug 1858624
variant: debs
To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1858625/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1859730] Re: [comet lake] Gnome freezes, icons missing, graphics corruption
** Changed in: mesa (Ubuntu) Status: Incomplete => New ** Changed in: linux (Ubuntu) Status: Incomplete => New ** Also affects: mutter (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/1859730 Title: [comet lake] Gnome freezes, icons missing, graphics corruption Status in linux package in Ubuntu: New Status in mesa package in Ubuntu: New Status in mutter package in Ubuntu: New Bug description: ack please.. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 Uname: Linux 5.4.11-050411-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CompositorRunning: None Date: Tue Jan 14 20:17:26 2020 DistUpgraded: Fresh install DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20180608-47+beaver-three-eyed-raven+X92 DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: backport-iwlwifi, 8286, 4.15.0-1042-oem, x86_64: installed backport-iwlwifi, 8286, 4.15.0-1066-oem, x86_64: installed ExtraDebuggingInterest: Yes GpuHangFrequency: Very infrequently GraphicsCard: Intel Corporation Device [8086:9bca] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0962] InstallationDate: Installed on 2020-01-13 (1 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 Lsusb: Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 8087:0029 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 13 7390 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=es_CL.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.11-050411-generic root=UUID=8fd25548-00af-4395-92f0-5d7d27a54deb ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/25/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.4.0 dmi.board.name: 0377MH dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.4.0:bd11/25/2019:svnDellInc.:pnXPS137390:pvr:rvnDellInc.:rn0377MH:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 7390 dmi.product.sku: 0962 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~18.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~18.04.3 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1859730/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1858625] Re: trusty/linux: 3.13.0-176.227 -proposed tracker
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
packages:
main: linux
meta: linux-meta
signed: linux-signed
phase: Packaging
phase-changed: Wednesday, 22. January 2020 18:25 UTC
reason:
prepare-package: Ongoing -- {} package not yet fully built
- promote-to-proposed: Ongoing -- builds not complete in ppa
main:building,signed:depwait
+ promote-to-proposed: Pending -- builds not complete in ppa
main:building,signed:queued
trackers:
precise/linux-lts-trusty: bug 1858624
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/1858625
Title:
trusty/linux: 3.13.0-176.227 -proposed tracker
Status in Kernel SRU Workflow:
In Progress
Status in Kernel SRU Workflow automated-testing series:
Invalid
Status in Kernel SRU Workflow certification-testing series:
Invalid
Status in Kernel SRU Workflow prepare-package series:
Fix Committed
Status in Kernel SRU Workflow prepare-package-meta series:
Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
Fix Released
Status in Kernel SRU Workflow promote-signing-to-proposed series:
New
Status in Kernel SRU Workflow promote-to-proposed series:
New
Status in Kernel SRU Workflow promote-to-security series:
Invalid
Status in Kernel SRU Workflow promote-to-updates series:
New
Status in Kernel SRU Workflow regression-testing series:
New
Status in Kernel SRU Workflow security-signoff series:
Invalid
Status in Kernel SRU Workflow verification-testing series:
New
Status in linux package in Ubuntu:
Invalid
Status in linux source package in Trusty:
Confirmed
Bug description:
This bug will contain status and test results related to a kernel
source (or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
packages:
main: linux
meta: linux-meta
signed: linux-signed
phase: Packaging
phase-changed: Wednesday, 22. January 2020 18:25 UTC
reason:
prepare-package: Ongoing -- {} package not yet fully built
promote-to-proposed: Pending -- builds not complete in ppa
main:building,signed:queued
trackers:
precise/linux-lts-trusty: bug 1858624
variant: debs
To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1858625/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-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
I also see no change with BIOS 1.10.0 on Eoan (though with kernel 5.3 due to an unrelated issue; I ran 5.4 and 5.5 before with the 1.7.1 BIOS and had the problem with all three kernels). I also noticed that though I have the problem just for ca 13 secs most of the time, occasionally it never seems to start working (I waited more than a minute). However, a few times recently I sent the laptop to sleep with the power button while the problem was occurring. The power button works even when the keyboard does not, and on wake-up the problem was gone. It is possible that I happened to press the button exactly when the keyboard would have worked anyway, but as the procedure helped every time this seems unlikely. Can anyone confirm? -- You 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 1858531] Re: disco/linux-aws: 5.0.0-1024.27 -proposed tracker
** 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: '1859724' packages: main: linux-aws meta: linux-meta-aws phase: Testing phase-changed: Monday, 13. January 2020 13: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 trackers: bionic/linux-aws-5.0: bug 1858530 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/1858531 Title: disco/linux-aws: 5.0.0-1024.27 -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-aws package in Ubuntu: Invalid Status in linux-aws source package in Disco: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: '1859724' packages: main: linux-aws meta: linux-meta-aws phase: Testing phase-changed: Monday, 13. January 2020 13: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-aws-5.0: bug 1858530 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1858531/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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
** Tags added: sru-20200106
--
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 1858531] Re: disco/linux-aws: 5.0.0-1024.27 -proposed tracker
** 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/1858531 Title: disco/linux-aws: 5.0.0-1024.27 -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-aws package in Ubuntu: Invalid Status in linux-aws source package in Disco: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: '1859724' packages: main: linux-aws meta: linux-meta-aws phase: Testing phase-changed: Monday, 13. January 2020 13: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-aws-5.0: bug 1858530 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1858531/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1858625] Re: trusty/linux: 3.13.0-176.227 -proposed tracker
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
packages:
main: linux
meta: linux-meta
signed: linux-signed
phase: Packaging
phase-changed: Wednesday, 22. January 2020 18:25 UTC
reason:
prepare-package: Ongoing -- {} package not yet fully built
- promote-to-proposed: Ongoing -- builds not complete in ppa
main:building,meta:building,signed:depwait
+ promote-to-proposed: Ongoing -- builds not complete in ppa
main:building,signed:depwait
trackers:
precise/linux-lts-trusty: bug 1858624
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/1858625
Title:
trusty/linux: 3.13.0-176.227 -proposed tracker
Status in Kernel SRU Workflow:
In Progress
Status in Kernel SRU Workflow automated-testing series:
Invalid
Status in Kernel SRU Workflow certification-testing series:
Invalid
Status in Kernel SRU Workflow prepare-package series:
Fix Committed
Status in Kernel SRU Workflow prepare-package-meta series:
Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
Fix Released
Status in Kernel SRU Workflow promote-signing-to-proposed series:
New
Status in Kernel SRU Workflow promote-to-proposed series:
New
Status in Kernel SRU Workflow promote-to-security series:
Invalid
Status in Kernel SRU Workflow promote-to-updates series:
New
Status in Kernel SRU Workflow regression-testing series:
New
Status in Kernel SRU Workflow security-signoff series:
Invalid
Status in Kernel SRU Workflow verification-testing series:
New
Status in linux package in Ubuntu:
Invalid
Status in linux source package in Trusty:
Confirmed
Bug description:
This bug will contain status and test results related to a kernel
source (or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
packages:
main: linux
meta: linux-meta
signed: linux-signed
phase: Packaging
phase-changed: Wednesday, 22. January 2020 18:25 UTC
reason:
prepare-package: Ongoing -- {} package not yet fully built
promote-to-proposed: Ongoing -- builds not complete in ppa
main:building,signed:depwait
trackers:
precise/linux-lts-trusty: bug 1858624
variant: debs
To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1858625/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1858625] Re: trusty/linux: 3.13.0-176.227 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package
Status: In Progress => Fix Committed
** Changed in: kernel-sru-workflow/prepare-package-meta
Status: In Progress => Fix Committed
** Changed in: kernel-sru-workflow/prepare-package-meta
Status: Fix Committed => Fix Released
** Changed in: kernel-sru-workflow/prepare-package-signed
Status: In Progress => Fix Committed
** Changed in: kernel-sru-workflow/prepare-package-signed
Status: Fix Committed => 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 --
packages:
main: linux
meta: linux-meta
signed: linux-signed
phase: Packaging
phase-changed: Wednesday, 22. January 2020 18:25 UTC
reason:
- prepare-package: Pending -- package not yet uploaded
- prepare-package-meta: Pending -- package not yet uploaded
- prepare-package-signed: Pending -- package not yet uploaded
+ prepare-package: Ongoing -- {} package not yet fully built
+ promote-to-proposed: Ongoing -- builds not complete in ppa
main:building,meta:building,signed:depwait
trackers:
precise/linux-lts-trusty: bug 1858624
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/1858625
Title:
trusty/linux: 3.13.0-176.227 -proposed tracker
Status in Kernel SRU Workflow:
In Progress
Status in Kernel SRU Workflow automated-testing series:
Invalid
Status in Kernel SRU Workflow certification-testing series:
Invalid
Status in Kernel SRU Workflow prepare-package series:
Fix Committed
Status in Kernel SRU Workflow prepare-package-meta series:
Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
Fix Released
Status in Kernel SRU Workflow promote-signing-to-proposed series:
New
Status in Kernel SRU Workflow promote-to-proposed series:
New
Status in Kernel SRU Workflow promote-to-security series:
Invalid
Status in Kernel SRU Workflow promote-to-updates series:
New
Status in Kernel SRU Workflow regression-testing series:
New
Status in Kernel SRU Workflow security-signoff series:
Invalid
Status in Kernel SRU Workflow verification-testing series:
New
Status in linux package in Ubuntu:
Invalid
Status in linux source package in Trusty:
Confirmed
Bug description:
This bug will contain status and test results related to a kernel
source (or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
packages:
main: linux
meta: linux-meta
signed: linux-signed
phase: Packaging
phase-changed: Wednesday, 22. January 2020 18:25 UTC
reason:
prepare-package: Ongoing -- {} package not yet fully built
promote-to-proposed: Ongoing -- builds not complete in ppa
main:building,meta:building,signed:depwait
trackers:
precise/linux-lts-trusty: bug 1858624
variant: debs
To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1858625/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1858456] Re: ThinkPad T450 stutters without intel_idle.max_cstate=2
I have upgraded to focal, am now running 5.4.0-9-generic and no longer see the issue -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1858456 Title: ThinkPad T450 stutters without intel_idle.max_cstate=2 Status in linux package in Ubuntu: Confirmed Bug description: I noticed my 19.10 laptop was stuttering - YouTube videos freezing. Did further investigations and the entire desktop freezes, not just the video rendering. https://www.youtube.com/watch?v=869e9YwW0vw Some investigation led me to https://bugzilla.kernel.org/show_bug.cgi?id=109051 and https://askubuntu.com/questions/803640/system-freezes-completely-with- intel-bay-trail I set intel_idle.max_cstate=2 in my grub config and now the issue never happens, but I have (anecdotally) seen worse battery life as a result. Can this be fixed in such a way that I don't have to suffer poor battery performance. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-24-generic 5.3.0-24.26 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Jan 6 16:26:20 2020 HibernationDevice: RESUME=UUID=60f73ebd-ac30-42de-968a-76a4f3332440 InstallationDate: Installed on 2018-02-04 (700 days ago) InstallationMedia: neon userlts "Xenial" - Build amd64 LIVE Binary 20180202-11:07 MachineType: LENOVO 20BV001BUK ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic root=UUID=36ab10c5-4404-47e2-89ec-6639af6cc629 ro quiet splash noibrs noibpb nopti nospectre_v2 nospectre_v1 l1tf=off nospec_store_bypass_disable no_stf_barrier mds=off tsx=on tsx_async_abort=off mitigations=off intel_idle.max_cstate=2 vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.3.0-24-generic N/A linux-backports-modules-5.3.0-24-generic N/A linux-firmware1.183.3 SourcePackage: linux UpgradeStatus: Upgraded to eoan on 2019-09-19 (109 days ago) dmi.bios.date: 08/14/2019 dmi.bios.vendor: LENOVO dmi.bios.version: JBET73WW (1.37 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BV001BUK dmi.board.vendor: LENOVO dmi.board.version: 0B98417 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrJBET73WW(1.37):bd08/14/2019:svnLENOVO:pn20BV001BUK:pvrThinkPadT450:rvnLENOVO:rn20BV001BUK:rvr0B98417WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T450 dmi.product.name: 20BV001BUK dmi.product.sku: LENOVO_MT_20BV_BU_Think_FM_ThinkPad T450 dmi.product.version: ThinkPad T450 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1858456/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1857616] Re: Cannot collect dump due to "Can't get a valid pmd_pte" error
I tested kdump functionality using makedumpfile and kdump version
'1:1.6.5-1ubuntu1~18.04.4' from -proposed on kernel 5.3.0-24 kernel and
it works.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to makedumpfile in Ubuntu.
https://bugs.launchpad.net/bugs/1857616
Title:
Cannot collect dump due to "Can't get a valid pmd_pte" error
Status in makedumpfile package in Ubuntu:
Fix Released
Status in makedumpfile source package in Xenial:
Opinion
Status in makedumpfile source package in Bionic:
Fix Committed
Status in makedumpfile source package in Disco:
Invalid
Status in makedumpfile source package in Eoan:
Fix Committed
Status in makedumpfile source package in Focal:
Fix Released
Bug description:
[Impact]
* Currently makedumpfile has 2 flaws due to: (a) out of
synchronization with kernel code and, (b) kaslr handling. The first is
related to a definition of a memory flag bit, whereas the second is
about kaslr offset calculation - both cause similar failures when
collecting the vmcore in kdump environment:
Excluding unnecessary pages : [ 46.3 %] / __vtop4_x86_64[ 39.341233]: Can't
get a valid pmd_pte.
readmem: Can't convert a virtual address(e05cb400) to physical
address.
readmem: type_addr: 0, addr:e05cb400, size:32768
__exclude_unnecessary_pages: Can't read the buffer of struct page.
create_2nd_bitmap: Can't exclude unnecessary pages.
* The report is mainly related to the first issue, which started to
happen after the merge of kernel commit 326e1b8f83a4 ("mm/sparsemem:
introduce a SECTION_IS_EARLY flag"), introduced in kernel 5.3. After
this commit, a memory flag was changed and induced the error in dump
collection. The fix is available in makedumpfile, as commit 7bdb468c2c
("Increase SECTION_MAP_LAST_BIT to 4"). This is hereby SRUed to Bionic
(due to HWE kernel 5.3), Eoan and Focal.
* The other issue is fixed in both Eoan and Focal, on makedumpfile
1.6.6-based version. It is related with the kaslr offset: if the
offset is small enough, we may return 0 wrongly in
get_kaslr_offset_x86_64(), causing the vmcore collection to fail or
even worse, to erase unintended data from the memory dump. This is
fixed by makedumpfile commit 3222d4ad04 ("x86_64: fix
get_kaslr_offset_x86_64() to return kaslr_offset correctly"), which
isn't present in versions before 1.6.6. We hereby SRU this fix for
Bionic.
* Notice this modification is being worked concurrently with other
kdump-tools' changes in LP #1828596.
[Test Case]
1) Deploy an Eoan VM e.g. with uvt-kvm;
2) Set-up console output in the guest;
3) Install the kdump-tools package;
4) Configure and collect a dump (with sysrq to panic the system) - the error
aforementioned is observed given Eoan kernel is 5.3-based.
[Regression Potential]
* The modifications hereby proposed are minimal and scope-constrained
to makedumpfile in x86_64; both are merged in makedumpfile upstream,
one of them being already released in E/F. An unlikely regression
would potentially fails vmcore collection in kdump environment.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1857616/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-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
I am still experiencing the issue after updating the BIOS firmware to version 1.10.0, on Ubuntu 19.10 (kernel 5.3.0-26). Firmware info and download page: https://www.dell.com/support/Home/us/en/frdhs1/Drivers/DriversDetails?driverId=0KJ0 -- You 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 1727358] Re: cloud-init is slow to complete init on minimized images
Eric, this bug is about the linux-kvm kernel _in Ubuntu_. If you're
seeing a cloud-init issue on Centos, then please file a separate bug.
Thanks!
--
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/1727358
Title:
cloud-init is slow to complete init on minimized images
Status in cloud-init:
Won't Fix
Status in cloud-init package in Ubuntu:
Won't Fix
Status in linux-kvm package in Ubuntu:
Confirmed
Status in python3.6 package in Ubuntu:
Triaged
Bug description:
http://paste.ubuntu.com/25816789/ for the full logs.
cloud-init is very slow to complete its initialization steps.
Specifically, the 'init' takes over 150 seconds.
Cloud-init v. 17.1 running 'init-local' at Wed, 25 Oct 2017 13:22:07 +.
Up 2.39 seconds.
2017-10-25 13:22:07,157 - util.py[WARNING]: did not find either path
/sys/class/dmi/id or dmidecode command
Cloud-init v. 17.1 running 'init' at Wed, 25 Oct 2017 13:22:16 +. Up
11.37 seconds.
ci-info: Net device
info+
ci-info:
++---+-+---+---+---+
ci-info: | Device | Up | Address | Mask | Scope |
Hw-Address|
ci-info:
++---+-+---+---+---+
ci-info: | ens3: | True | 192.168.100.161 | 255.255.255.0 | . |
52:54:00:bb:ad:fb |
ci-info: | ens3: | True |.| . | d |
52:54:00:bb:ad:fb |
ci-info: | lo: | True |127.0.0.1| 255.0.0.0 | . |
. |
ci-info: | lo: | True |.| . | d |
. |
ci-info: | sit0: | False |.| . | . |
. |
ci-info:
++---+-+---+---+---+
ci-info: Route IPv4
info
ci-info:
+---+---+---+-+---+---+
ci-info: | Route | Destination |Gateway| Genmask |
Interface | Flags |
ci-info:
+---+---+---+-+---+---+
ci-info: | 0 |0.0.0.0| 192.168.100.1 | 0.0.0.0 |ens3
| UG |
ci-info: | 1 | 192.168.100.0 |0.0.0.0| 255.255.255.0 |ens3
| U |
ci-info: | 2 | 192.168.100.1 |0.0.0.0| 255.255.255.255 |ens3
| UH |
ci-info:
+---+---+---+-+---+---+
2017-10-25 13:24:38,187 - util.py[WARNING]: Failed to resize filesystem
(cmd=('resize2fs', '/dev/root'))
2017-10-25 13:24:38,193 - util.py[WARNING]: Running module resizefs () failed
Generating public/private rsa key pair.
Your identification has been saved in /etc/ssh/ssh_host_rsa_key.
Your public key has been saved in /etc/ssh/ssh_host_rsa_key.pub.
The key fingerprint is:
SHA256:LKNlCqqOgPB8KBKGfPhFO5Rs6fDMnAvVet/W9i4vLxY root@cloudimg
The key's randomart image is:
+---[RSA 2048]+
| |
|. + |
| . O . |
|o . % +. |
|++.o %=.S|
|+=ooo=+o. . .E |
|* +.+. . o o. |
|=. . . .=. |
|+. . B= |
+[SHA256]-+
Generating public/private dsa key pair.
Your identification has been saved in /etc/ssh/ssh_host_dsa_key.
Your public key has been saved in /etc/ssh/ssh_host_dsa_key.pub.
The key fingerprint is:
SHA256:dNWNyBHqTUCl820/vL0dEhOVDFYJzqr1WeuqV1PAmjk root@cloudimg
The key's randomart image is:
+---[DSA 1024]+
| .oo=X==o|
| =* *+.|
|. = .B . |
| . o =E.. .|
|S .oo+o..|
| o ..*+.|
| . +.=o|
| .o *|
| .o..++|
+[SHA256]-+
Generating public/private ecdsa key pair.
Your identification has been saved in /etc/ssh/ssh_host_ecdsa_key.
Your public key has been saved in /etc/ssh/ssh_host_ecdsa_key.pub.
The key fingerprint is:
SHA256:N3RTlPa7KU5ryq6kJAO8Tiq90ub4P1DGSofn6jFkM3k root@cloudimg
The key's randomart image is:
+---[ECDSA 256]---+
| .o. |
| .o |
| o . o. . |
| +.*. . . .|
| .*XE S o .|
| oo++. . . |
| oo= o . . . o|
|o.Oo. + o . .o.o |
|oB=+.. . .o++o. |
+[SHA256]-+
Generating public/private ed25519 key pair.
Your identification has been saved in /etc/ssh/ssh_host_ed25519_key.
Your public key has been saved in /etc/ssh/ssh_host_ed25519_key.pub.
The key fingerprint is:
SHA256:B6B/1SyUB/TFPfmU1ADIotnD+wjISO5L2JZkWe2lDUA root@cloudimg
The key's randomart image is:
+--[ED25519 256]--+
| .E . o++.o+++|
| + ...++...++|
|o o=o.o.+ .o|
| .o oo=+o ..|
| o+o .+ So. |
|
[Kernel-packages] [Bug 1850130] Re: zpools fail to import after reboot on fresh install of eoan
I think there are multiple issues here. If it's just multipath, that
issue should be resolved by adding After=multipathd.service to zfs-
import-{cache,scan}.service.
For other issues, I wonder if this is cache file related. I'd suggest
checking that the cache file exists (I expect it would), and then
looking at the cache file (e.g. strings /etc/zfs/zpool.cache | less). I
suspect the issue is that the cache file has only the rpool. I'm not
entirely sure why that is happening.
--
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/1850130
Title:
zpools fail to import after reboot on fresh install of eoan
Status in zfs-linux package in Ubuntu:
Confirmed
Bug description:
Fresh installation of stock Ubuntu 19.10 Eoan with experimental root on ZFS.
System has existing zpools with data.
Installation is uneventful. First boot with no problems. Updates
applied. No other changes from fresh installation. Reboot.
External pool 'tank' imports with no errors. Reboot.
External pool has failed to import on boot. In contrast bpool and
rpool are ok. Manually re-import 'tank' with no issues. I can see both
'tank' and its path in /dev/disk/by-id/ in /etc/zfs/zpool.cache.
Reboot.
'tank' has failed to import on boot. It is also missing from
/etc/zfs/zpool.cache. Is it possible that the cache is being re-
generated on reboot, and the newly imported pools are getting erased
from it? I can re-import the pools again manually with no issues, but
they don't persist between re-boots.
Installing normally on ext4 this is not an issue and data pools import
automatically on boot with no further effort.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1850130/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1727358] Re: cloud-init is slow to complete init on minimized images
Ok, I got a question for all the interested folks out there;
What is we were to have a test case that run init-local and fails if
random gets imported?
I'm looking at how this could be done, but that test could link to this bug and
have people realise that they need to be careful about the random import.
Is it a good idea or a bad idea? I honestly cannot tell and I have the
tendency to think it's a good idea...
--
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/1727358
Title:
cloud-init is slow to complete init on minimized images
Status in cloud-init:
Won't Fix
Status in cloud-init package in Ubuntu:
Won't Fix
Status in linux-kvm package in Ubuntu:
Confirmed
Status in python3.6 package in Ubuntu:
Triaged
Bug description:
http://paste.ubuntu.com/25816789/ for the full logs.
cloud-init is very slow to complete its initialization steps.
Specifically, the 'init' takes over 150 seconds.
Cloud-init v. 17.1 running 'init-local' at Wed, 25 Oct 2017 13:22:07 +.
Up 2.39 seconds.
2017-10-25 13:22:07,157 - util.py[WARNING]: did not find either path
/sys/class/dmi/id or dmidecode command
Cloud-init v. 17.1 running 'init' at Wed, 25 Oct 2017 13:22:16 +. Up
11.37 seconds.
ci-info: Net device
info+
ci-info:
++---+-+---+---+---+
ci-info: | Device | Up | Address | Mask | Scope |
Hw-Address|
ci-info:
++---+-+---+---+---+
ci-info: | ens3: | True | 192.168.100.161 | 255.255.255.0 | . |
52:54:00:bb:ad:fb |
ci-info: | ens3: | True |.| . | d |
52:54:00:bb:ad:fb |
ci-info: | lo: | True |127.0.0.1| 255.0.0.0 | . |
. |
ci-info: | lo: | True |.| . | d |
. |
ci-info: | sit0: | False |.| . | . |
. |
ci-info:
++---+-+---+---+---+
ci-info: Route IPv4
info
ci-info:
+---+---+---+-+---+---+
ci-info: | Route | Destination |Gateway| Genmask |
Interface | Flags |
ci-info:
+---+---+---+-+---+---+
ci-info: | 0 |0.0.0.0| 192.168.100.1 | 0.0.0.0 |ens3
| UG |
ci-info: | 1 | 192.168.100.0 |0.0.0.0| 255.255.255.0 |ens3
| U |
ci-info: | 2 | 192.168.100.1 |0.0.0.0| 255.255.255.255 |ens3
| UH |
ci-info:
+---+---+---+-+---+---+
2017-10-25 13:24:38,187 - util.py[WARNING]: Failed to resize filesystem
(cmd=('resize2fs', '/dev/root'))
2017-10-25 13:24:38,193 - util.py[WARNING]: Running module resizefs () failed
Generating public/private rsa key pair.
Your identification has been saved in /etc/ssh/ssh_host_rsa_key.
Your public key has been saved in /etc/ssh/ssh_host_rsa_key.pub.
The key fingerprint is:
SHA256:LKNlCqqOgPB8KBKGfPhFO5Rs6fDMnAvVet/W9i4vLxY root@cloudimg
The key's randomart image is:
+---[RSA 2048]+
| |
|. + |
| . O . |
|o . % +. |
|++.o %=.S|
|+=ooo=+o. . .E |
|* +.+. . o o. |
|=. . . .=. |
|+. . B= |
+[SHA256]-+
Generating public/private dsa key pair.
Your identification has been saved in /etc/ssh/ssh_host_dsa_key.
Your public key has been saved in /etc/ssh/ssh_host_dsa_key.pub.
The key fingerprint is:
SHA256:dNWNyBHqTUCl820/vL0dEhOVDFYJzqr1WeuqV1PAmjk root@cloudimg
The key's randomart image is:
+---[DSA 1024]+
| .oo=X==o|
| =* *+.|
|. = .B . |
| . o =E.. .|
|S .oo+o..|
| o ..*+.|
| . +.=o|
| .o *|
| .o..++|
+[SHA256]-+
Generating public/private ecdsa key pair.
Your identification has been saved in /etc/ssh/ssh_host_ecdsa_key.
Your public key has been saved in /etc/ssh/ssh_host_ecdsa_key.pub.
The key fingerprint is:
SHA256:N3RTlPa7KU5ryq6kJAO8Tiq90ub4P1DGSofn6jFkM3k root@cloudimg
The key's randomart image is:
+---[ECDSA 256]---+
| .o. |
| .o |
| o . o. . |
| +.*. . . .|
| .*XE S o .|
| oo++. . . |
| oo= o . . . o|
|o.Oo. + o . .o.o |
|oB=+.. . .o++o. |
+[SHA256]-+
Generating public/private ed25519 key pair.
Your identification has been saved in /etc/ssh/ssh_host_ed25519_key.
Your public key has been saved in
[Kernel-packages] [Bug 1860602] Re: Bionic update: upstream stable patchset 2020-01-22
** Description changed: - - SRU Justification - - Impact: -The upstream process for stable tree updates is quite similar -in scope to the Ubuntu SRU process, e.g., each patch has to -demonstrably fix a bug, and each patch is vetted by upstream -by originating either directly from a mainline/stable Linux tree or -a minimally backported form of that patch. The following upstream -stable patches should be included in the Ubuntu kernel: - -upstream stable patchset 2020-01-22 -from git://git.kernel.org/ + SRU Justification + + Impact: + The upstream process for stable tree updates is quite similar + in scope to the Ubuntu SRU process, e.g., each patch has to + demonstrably fix a bug, and each patch is vetted by upstream + by originating either directly from a mainline/stable Linux tree or + a minimally backported form of that patch. The following upstream + stable patches should be included in the Ubuntu kernel: + + upstream stable patchset 2020-01-22 + + Ported from the following upstream stable releases: + v4.14.163, v4.19.94 + v4.14.162, v4.19.93 + + from git://git.kernel.org/ + + scsi: lpfc: Fix discovery failures when target device connectivity bounces + scsi: mpt3sas: Fix clear pending bit in ioctl status + scsi: lpfc: Fix locking on mailbox command completion + Input: atmel_mxt_ts - disable IRQ across suspend + iommu/tegra-smmu: Fix page tables in > 4 GiB memory + scsi: target: compare full CHAP_A Algorithm strings + scsi: lpfc: Fix SLI3 hba in loop mode not discovering devices + scsi: csiostor: Don't enable IRQs too early + powerpc/pseries: Mark accumulate_stolen_time() as notrace + powerpc/pseries: Don't fail hash page table insert for bolted mapping + powerpc/tools: Don't quote $objdump in scripts + dma-debug: add a schedule point in debug_dma_dump_mappings() + clocksource/drivers/asm9260: Add a check for of_clk_get + powerpc/security/book3s64: Report L1TF status in sysfs + powerpc/book3s64/hash: Add cond_resched to avoid soft lockup warning + ext4: update direct I/O read lock pattern for IOCB_NOWAIT + jbd2: Fix statistics for the number of logged blocks + scsi: tracing: Fix handling of TRANSFER LENGTH == 0 for READ(6) and WRITE(6) + scsi: lpfc: Fix duplicate unreg_rpi error in port offline flow + f2fs: fix to update dir's i_pino during cross_rename + clk: qcom: Allow constant ratio freq tables for rcg + irqchip/irq-bcm7038-l1: Enable parent IRQ if necessary + irqchip: ingenic: Error out if IRQ domain creation failed + fs/quota: handle overflows of sysctl fs.quota.* and report as unsigned long + scsi: lpfc: fix: Coverity: lpfc_cmpl_els_rsp(): Null pointer dereferences + scsi: ufs: fix potential bug which ends in system hang + powerpc/pseries/cmm: Implement release() function for sysfs device + powerpc/security: Fix wrong message when RFI Flush is disable + scsi: atari_scsi: sun3_scsi: Set sg_tablesize to 1 instead of SG_NONE + clk: pxa: fix one of the pxa RTC clocks + bcache: at least try to shrink 1 node in bch_mca_scan() + HID: logitech-hidpp: Silence intermittent get_battery_capacity errors + libnvdimm/btt: fix variable 'rc' set but not used + HID: Improve Windows Precision Touchpad detection. + scsi: pm80xx: Fix for SATA device discovery + scsi: ufs: Fix error handing during hibern8 enter + scsi: scsi_debug: num_tgts must be >= 0 + scsi: NCR5380: Add disconnect_mask module parameter + scsi: iscsi: Don't send data to unbound connection + scsi: target: iscsi: Wait for all commands to finish before freeing a session + gpio: mpc8xxx: Don't overwrite default irq_set_type callback + apparmor: fix unsigned len comparison with less than zero + scripts/kallsyms: fix definitely-lost memory leak + cdrom: respect device capabilities during opening action + perf script: Fix brstackinsn for AUXTRACE + perf regs: Make perf_reg_name() return "unknown" instead of NULL + s390/zcrypt: handle new reply code FILTERED_BY_HYPERVISOR + libfdt: define INT32_MAX and UINT32_MAX in libfdt_env.h + s390/cpum_sf: Check for SDBT and SDB consistency + ocfs2: fix passing zero to 'PTR_ERR' warning + kernel: sysctl: make drop_caches write-only + userfaultfd: require CAP_SYS_PTRACE for UFFD_FEATURE_EVENT_FORK + x86/mce: Fix possibly incorrect severity calculation on AMD + net, sysctl: Fix compiler warning when only cBPF is present + netfilter: nf_queue: enqueue skbs with NULL dst + ALSA: hda - Downgrade error message for single-cmd fallback + bonding: fix active-backup transition after link failure + perf strbuf: Remove redundant va_end() in strbuf_addv() + Make filldir[64]() verify the directory entry filename is valid + filldir[64]: remove WARN_ON_ONCE() for bad directory entries + netfilter: ebtables: compat: reject all padding in matches/watchers + 6pack,mkiss: fix possible deadlock + netfilter: bridge: make sure to pull arp
[Kernel-packages] [Bug 1860602] [NEW] Bionic update: upstream stable patchset 2020-01-22
Public bug reported: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: upstream stable patchset 2020-01-22 Ported from the following upstream stable releases: v4.14.163, v4.19.94 v4.14.162, v4.19.93 from git://git.kernel.org/ scsi: lpfc: Fix discovery failures when target device connectivity bounces scsi: mpt3sas: Fix clear pending bit in ioctl status scsi: lpfc: Fix locking on mailbox command completion Input: atmel_mxt_ts - disable IRQ across suspend iommu/tegra-smmu: Fix page tables in > 4 GiB memory scsi: target: compare full CHAP_A Algorithm strings scsi: lpfc: Fix SLI3 hba in loop mode not discovering devices scsi: csiostor: Don't enable IRQs too early powerpc/pseries: Mark accumulate_stolen_time() as notrace powerpc/pseries: Don't fail hash page table insert for bolted mapping powerpc/tools: Don't quote $objdump in scripts dma-debug: add a schedule point in debug_dma_dump_mappings() clocksource/drivers/asm9260: Add a check for of_clk_get powerpc/security/book3s64: Report L1TF status in sysfs powerpc/book3s64/hash: Add cond_resched to avoid soft lockup warning ext4: update direct I/O read lock pattern for IOCB_NOWAIT jbd2: Fix statistics for the number of logged blocks scsi: tracing: Fix handling of TRANSFER LENGTH == 0 for READ(6) and WRITE(6) scsi: lpfc: Fix duplicate unreg_rpi error in port offline flow f2fs: fix to update dir's i_pino during cross_rename clk: qcom: Allow constant ratio freq tables for rcg irqchip/irq-bcm7038-l1: Enable parent IRQ if necessary irqchip: ingenic: Error out if IRQ domain creation failed fs/quota: handle overflows of sysctl fs.quota.* and report as unsigned long scsi: lpfc: fix: Coverity: lpfc_cmpl_els_rsp(): Null pointer dereferences scsi: ufs: fix potential bug which ends in system hang powerpc/pseries/cmm: Implement release() function for sysfs device powerpc/security: Fix wrong message when RFI Flush is disable scsi: atari_scsi: sun3_scsi: Set sg_tablesize to 1 instead of SG_NONE clk: pxa: fix one of the pxa RTC clocks bcache: at least try to shrink 1 node in bch_mca_scan() HID: logitech-hidpp: Silence intermittent get_battery_capacity errors libnvdimm/btt: fix variable 'rc' set but not used HID: Improve Windows Precision Touchpad detection. scsi: pm80xx: Fix for SATA device discovery scsi: ufs: Fix error handing during hibern8 enter scsi: scsi_debug: num_tgts must be >= 0 scsi: NCR5380: Add disconnect_mask module parameter scsi: iscsi: Don't send data to unbound connection scsi: target: iscsi: Wait for all commands to finish before freeing a session gpio: mpc8xxx: Don't overwrite default irq_set_type callback apparmor: fix unsigned len comparison with less than zero scripts/kallsyms: fix definitely-lost memory leak cdrom: respect device capabilities during opening action perf script: Fix brstackinsn for AUXTRACE perf regs: Make perf_reg_name() return "unknown" instead of NULL s390/zcrypt: handle new reply code FILTERED_BY_HYPERVISOR libfdt: define INT32_MAX and UINT32_MAX in libfdt_env.h s390/cpum_sf: Check for SDBT and SDB consistency ocfs2: fix passing zero to 'PTR_ERR' warning kernel: sysctl: make drop_caches write-only userfaultfd: require CAP_SYS_PTRACE for UFFD_FEATURE_EVENT_FORK x86/mce: Fix possibly incorrect severity calculation on AMD net, sysctl: Fix compiler warning when only cBPF is present netfilter: nf_queue: enqueue skbs with NULL dst ALSA: hda - Downgrade error message for single-cmd fallback bonding: fix active-backup transition after link failure perf strbuf: Remove redundant va_end() in strbuf_addv() Make filldir[64]() verify the directory entry filename is valid filldir[64]: remove WARN_ON_ONCE() for bad directory entries netfilter: ebtables: compat: reject all padding in matches/watchers 6pack,mkiss: fix possible deadlock netfilter: bridge: make sure to pull arp header in br_nf_forward_arp() inetpeer: fix data-race in inet_putpeer / inet_putpeer net: add a READ_ONCE() in skb_peek_tail() net: icmp: fix data-race in cmp_global_allow() hrtimer: Annotate lockless access to timer->state spi: fsl: don't map irq during probe tty/serial: atmel: fix out of range clock divider handling pinctrl: baytrail: Really serialize all register accesses net: ena: fix napi handler misbehavior when the napi budget is zero net/mlxfw: Fix out-of-memory error in mfa2 flash burning ptp: fix the race between the release of ptp_clock and cdev udp: fix integer overflow while computing available space in sk_rcvbuf vhost/vsock: accept only packets with the right dst_cid net: add bool confirm_neigh
[Kernel-packages] [Bug 1860603] [NEW] [linux-azure] VMs crashing due to 503 SMB errors
Public bug reported:
Several Azure VMs on AKS and are experiencing some random node restarts.
The issues was narrowed down to a NULL pointer dereference in
smb2_push_mandatory_locks().
The following commit fixes this issue:
6f582b273ec2 ("CIFS: Fix NULL-pointer dereference in smb2_push_mandatory_locks")
This commit landed in mainline as of v5.5-rc1. The commit has also been
applied to linux-azure-bionic in Ubuntu-azure-5.0.0-1029.31 via stable
updates.
However, this commit has not been applied to linux-azure-xenial, but it
is needed there. Please apply the commit to xenial.
** 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/1860603
Title:
[linux-azure] VMs crashing due to 503 SMB errors
Status in linux-azure package in Ubuntu:
New
Bug description:
Several Azure VMs on AKS and are experiencing some random node
restarts.
The issues was narrowed down to a NULL pointer dereference in
smb2_push_mandatory_locks().
The following commit fixes this issue:
6f582b273ec2 ("CIFS: Fix NULL-pointer dereference in
smb2_push_mandatory_locks")
This commit landed in mainline as of v5.5-rc1. The commit has also
been applied to linux-azure-bionic in Ubuntu-azure-5.0.0-1029.31 via
stable updates.
However, this commit has not been applied to linux-azure-xenial, but
it is needed there. Please apply the commit to xenial.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1860603/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1851416] Re: Prime Profiles page could be better
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: nvidia-settings (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-settings in Ubuntu. https://bugs.launchpad.net/bugs/1851416 Title: Prime Profiles page could be better Status in nvidia-settings package in Ubuntu: Confirmed Bug description: There are 4 possibly problem points, placement, names, tooltips, help. The 1st 3 are somewhat linked. The new profile, NVIDIA On-Demand is currently placed between the 2 previous & historical ones of NVIDIA.. & Intel.. The placement and name could lead one to believe that it's an app on demand or as needed similar to how optimus works in windows. This is clearly not the case & if picked produces a degraded experience for most users.. It should be the 3rd listed profile and if possible named more towards it's actual use case. There previously were 2 tooltips on hover, currently there still are just 2, the one designed for Intel now exposes only when hovered over NVIDIA On-Demand, hovering over Intel produces nothing NVIDIA On-Demand should get it's own tooltip. The Help button popup shows no info on what NVIDIA On-Demand is about or for, considering the vast majority of users should not use that profile it should be described, ect. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: nvidia-settings 435.21-0ubuntu2 ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1 Uname: Linux 5.3.0-18-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu9 Architecture: amd64 CurrentDesktop: Unity:Unity7:ubuntu Date: Tue Nov 5 12:18:49 2019 InstallationDate: Installed on 2019-10-29 (6 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20191029.2) SourcePackage: nvidia-settings UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-settings/+bug/1851416/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1844245] Re: Integrate Intel SGX driver into linux-azure
** Tags removed: verification-needed-bionic verification-needed-disco verification-needed-xenial ** Tags added: verification-done-bionic verification-done-disco verification-done-xenial ** Tags removed: verification-needed-eoan ** Tags added: verification-done-eoan -- 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/1844245 Title: Integrate Intel SGX driver into linux-azure Status in linux package in Ubuntu: Incomplete Status in linux-azure package in Ubuntu: In Progress Status in linux source package in Xenial: Fix Committed Status in linux-azure source package in Xenial: Fix Committed Status in linux source package in Bionic: Fix Committed Status in linux-azure source package in Bionic: Invalid Status in linux source package in Disco: Fix Committed Status in linux-azure source package in Disco: Fix Committed Status in linux source package in Eoan: Fix Committed Status in linux-azure source package in Eoan: Fix Committed Bug description: Intel is still trying to upstream the SGX driver, but in the meantime it would be desirable to have it available on the linux-azure kernel. The following version relies only on Kbuild: https://github.com/haimc-intel/SGXDataCenterAttestationPrimitives inker-ph1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1844245/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1858798] Re: tools/perf fails to build after Xenial update to 4.4.208 upstream stable release
I think this can be marked as verificaiton-done since we know the build
is now fine.
** Tags removed: verification-needed-xenial
** Tags added: verification-done-xenial
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1858798
Title:
tools/perf fails to build after Xenial update to 4.4.208 upstream
stable release
Status in linux package in Ubuntu:
Invalid
Status in linux source package in Xenial:
Fix Committed
Bug description:
[Impact]
xenial/linux after the update to 4.4.208 upstream stable fails to build
tools/perf on environments that don't have libunwind installed.
https://launchpad.net/~canonical-kernel-
team/+archive/ubuntu/ppa/+build/18530346/+files/buildlog_ubuntu-
xenial-powerpc.linux_4.4.0-172.201_BUILDING.txt.gz
[...]
builtin-report.c: In function ‘report__setup_sample_type’:
builtin-report.c:289:6: error: ‘dwarf_callchain_users’ undeclared (first use
in this function)
if (dwarf_callchain_users) {
^
[...]
This is caused by the following commit from linux-4.4.y:
commit faece3af80729763bb28449fa803d12c962571bd
Author: Jin Yao
Date: Fri Oct 11 10:21:22 2019 +0800
perf report: Add warning when libunwind not compiled in
[ Upstream commit 800d3f561659b5436f8c57e7c26dd1f6928b5615 ]
[Fix]
Revert the mentioned commit. The variable 'dwarf_callchain_users' was
introduced by eabad8c6856f "perf unwind: Do not look just at the global
callchain_param.record_mode" which as of now hasn't been backported to stable
linux-4.4.y.
[Test]
Build the kernel on PPA for powerpc, ppc64el and s390x.
[Regression Potential]
Null. This commit is supposed to only add a warning and is breaking the build
for some architectures, so reverting it will not cause any regression for the
users.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1858798/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1858625] Re: trusty/linux: 3.13.0-176.227 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-security Status: New => Invalid ** Changed in: kernel-sru-workflow/security-signoff Status: New => Invalid ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- packages: main: linux meta: linux-meta signed: linux-signed - phase: Ready for Packaging - phase-changed: Tuesday, 07. January 2020 10:16 UTC + phase: Packaging + phase-changed: Wednesday, 22. January 2020 18:25 UTC reason: - prepare-package: Pending -- version not specified + prepare-package: Pending -- package not yet uploaded + prepare-package-meta: Pending -- package not yet uploaded + prepare-package-signed: Pending -- package not yet uploaded trackers: precise/linux-lts-trusty: bug 1858624 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/1858625 Title: trusty/linux: 3.13.0-176.227 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow prepare-package-signed series: In Progress Status in Kernel SRU Workflow promote-signing-to-proposed series: New Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Trusty: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- packages: main: linux meta: linux-meta signed: linux-signed phase: Packaging phase-changed: Wednesday, 22. January 2020 18:25 UTC reason: prepare-package: Pending -- package not yet uploaded prepare-package-meta: Pending -- package not yet uploaded prepare-package-signed: Pending -- package not yet uploaded trackers: precise/linux-lts-trusty: bug 1858624 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1858625/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1858625] Re: trusty/linux: 3.13.0-176.227 -proposed tracker
** Summary changed: - trusty/linux: -proposed tracker + trusty/linux: 3.13.0-176.227 -proposed tracker ** Changed in: kernel-sru-workflow/prepare-package Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/prepare-package Assignee: Canonical Kernel Team (canonical-kernel-team) => Connor Kuehl (connork) ** Changed in: kernel-sru-workflow/prepare-package-meta Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: Canonical Kernel Team (canonical-kernel-team) => Connor Kuehl (connork) ** Changed in: kernel-sru-workflow/prepare-package-signed Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-signed Assignee: Canonical Kernel Team (canonical-kernel-team) => Connor Kuehl (connork) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1858625 Title: trusty/linux: 3.13.0-176.227 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow prepare-package-signed series: In Progress Status in Kernel SRU Workflow promote-signing-to-proposed series: New Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Trusty: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- packages: main: linux meta: linux-meta signed: linux-signed phase: Packaging phase-changed: Wednesday, 22. January 2020 18:25 UTC reason: prepare-package: Pending -- package not yet uploaded prepare-package-meta: Pending -- package not yet uploaded prepare-package-signed: Pending -- package not yet uploaded trackers: precise/linux-lts-trusty: bug 1858624 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1858625/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1858533] Re: bionic/linux-azure: 5.0.0-1029.31~18.04.1 -proposed tracker
** 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: 1858534 packages: lrm: linux-restricted-modules-azure main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Testing phase-changed: Thursday, 16. January 2020 11:06 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 stakeholder-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-azure/azure-kernel: bug 1858532 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/1858533 Title: bionic/linux-azure: 5.0.0-1029.31~18.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-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 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 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: 1858534 packages: lrm: linux-restricted-modules-azure main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Testing phase-changed: Thursday, 16. January 2020 11:06 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: regression-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/azure-kernel: bug 1858532 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1858533/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1858536] Re: bionic/linux-gcp: 5.0.0-1029.30~18.04.1 -proposed tracker
** 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: 1858539 packages: lrm: linux-restricted-modules-gcp main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp phase: Testing phase-changed: Monday, 13. January 2020 16:38 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 1858535 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/1858536 Title: bionic/linux-gcp: 5.0.0-1029.30~18.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-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: 1858539 packages: lrm: linux-restricted-modules-gcp main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp phase: Testing phase-changed: Monday, 13. January 2020 16:38 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/gcp-kernel: bug 1858535 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1858536/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1850130] Re: zpools fail to import after reboot on fresh install of eoan
And I'm on focal now. -- 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/1850130 Title: zpools fail to import after reboot on fresh install of eoan Status in zfs-linux package in Ubuntu: Confirmed Bug description: Fresh installation of stock Ubuntu 19.10 Eoan with experimental root on ZFS. System has existing zpools with data. Installation is uneventful. First boot with no problems. Updates applied. No other changes from fresh installation. Reboot. External pool 'tank' imports with no errors. Reboot. External pool has failed to import on boot. In contrast bpool and rpool are ok. Manually re-import 'tank' with no issues. I can see both 'tank' and its path in /dev/disk/by-id/ in /etc/zfs/zpool.cache. Reboot. 'tank' has failed to import on boot. It is also missing from /etc/zfs/zpool.cache. Is it possible that the cache is being re- generated on reboot, and the newly imported pools are getting erased from it? I can re-import the pools again manually with no issues, but they don't persist between re-boots. Installing normally on ext4 this is not an issue and data pools import automatically on boot with no further effort. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1850130/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1850130] Re: zpools fail to import after reboot on fresh install of eoan
I have a local data mirror zpool, and need to import it manually like others. The system was installed with eoan and zfs on root, the data mirror was added afterwards. -- 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/1850130 Title: zpools fail to import after reboot on fresh install of eoan Status in zfs-linux package in Ubuntu: Confirmed Bug description: Fresh installation of stock Ubuntu 19.10 Eoan with experimental root on ZFS. System has existing zpools with data. Installation is uneventful. First boot with no problems. Updates applied. No other changes from fresh installation. Reboot. External pool 'tank' imports with no errors. Reboot. External pool has failed to import on boot. In contrast bpool and rpool are ok. Manually re-import 'tank' with no issues. I can see both 'tank' and its path in /dev/disk/by-id/ in /etc/zfs/zpool.cache. Reboot. 'tank' has failed to import on boot. It is also missing from /etc/zfs/zpool.cache. Is it possible that the cache is being re- generated on reboot, and the newly imported pools are getting erased from it? I can re-import the pools again manually with no issues, but they don't persist between re-boots. Installing normally on ext4 this is not an issue and data pools import automatically on boot with no further effort. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1850130/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1860524] Re: Unable to install linux-oem-5.4 from the proposed pocket
As a temporary workaround, I have to change linux-oem-5.4 to linux- oem-20.04 in kmsgq-jenkins and craft a test request with package changed to linux-oem-20.04 as well to get them tested. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1860524 Title: Unable to install linux-oem-5.4 from the proposed pocket Status in linux package in Ubuntu: Incomplete Bug description: With proposed enabled, I can't install linux-oem-5.4 meta package to get the 5.4 OEM kernel. $ sudo apt update Hit:1 http://archive.ubuntu.com/ubuntu focal InRelease Hit:2 http://archive.ubuntu.com/ubuntu focal-updates InRelease Hit:3 http://archive.ubuntu.com/ubuntu focal-security InRelease Hit:4 http://archive.ubuntu.com/ubuntu focal-backports InRelease Hit:5 http://archive.ubuntu.com/ubuntu focal-proposed InRelease Reading package lists... Done Building dependency tree Reading state information... Done 56 packages can be upgraded. Run 'apt list --upgradable' to see them. $ apt-cache search linux-oem-5.4 linux-oem-5.4-headers-5.4.0-1002 - Header files related to Linux kernel version 5.4.0 linux-oem-5.4-tools-5.4.0-1002 - Linux kernel version specific tools for version 5.4.0-1002 linux-oem-5.4-tools-common - Linux kernel version specific tools for version 5.4.0 linux-oem-5.4-tools-host - Linux kernel VM host tools It looks like this package does not exist, however a double tab after the "sudo apt install linux-oem" command shows it's there $ sudo apt install linux-oem linux-oem linux-oem-5.4-headers-5.4.0-1002 linux-oem-5.4-tools-host linux-oem-tools-host linux-oem-20.04 linux-oem-5.4-tools-5.4.0-1002 linux-oem-osp1 linux-oem-5.4 linux-oem-5.4-tools-common linux-oem-osp1-tools-host To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860524/+subscriptions -- Mailing list: https://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 1860483] Re: [nouveau] screen background overlaid with scan type artifact in red
I tried "Ubuntu on Wayland". Crash. Logged in. Screen loaded improperly and keyboard and mouse froze; handlers blocked and who knows what else. The screen didn't have the red artifact though; it had a cluster of diagonal black and white scan lines covering about the middle third of the screen, an incomplete population of the left hand tool bar icons I use and none of the desktop icons. The top tool bar seemed complete, but was non-functional. Tried "Unity" while I was at it, and that was a complete flop post-log-in. Blank screen, except for an oversized audio slider icon at the top right and the cursor arrow, and the cursor was frozen; once again, no handlers. On 1/22/20 8:40 AM, Paul Collinsworth wrote: > I encountered an issue after advising you that 18.04.3 works. Perhaps > it sheds some light on the problem. > > It occurred to me that perhaps there is a graphics issue and that part > of what I was seeing is contamination of the background image I was > using. So I tried to open "Settings" in order to revert to the default > image. Didn't work; that is, "Settings" doesn't work. No response. I > can click on "Settings" on either toolbar or try to access it through > "Show Applications" and no response. > > What's more, after getting no response there, other stuff is locked > out and doesn't respond. I have to reboot to get functionality back. > In getting to reboot, the shutdown process does report that anything > I've tried to open or start, after trying to reach "Settings", isn't > responding, and then it hangs. If I click on "Power down" again at > that point, it doesn't, it just puts up an image and stalls (the image > it displays is the background image I've been using, without the > toolbars and the contaminant artifact!). At that point, I've just hit > the power switch. > > I've not tried "Ubuntu on Wayland" or the test kernel package. I'll > see what happens there. I can boot into the prior Linux generic via > grub; haven't tried to pull up any apps there, but the image issue was > still there. > > > > On 1/22/20 12:43 AM, Daniel van Vugt wrote: >> OK, thanks. Assuming the bug isn't just hiding and wouldn't reappear >> later in 18.04.3 if used long enough, then this implies a fix exists >> somewhere in the HWE packages (which are the difference between 18.04 >> fully updated and 18.04.3 fully updated). >> >> The only two sets of HWE packages I can think of that affect graphics >> are Xorg and the kernel. >> >> Firstly Xorg: Does the bug occur if you log into "Ubuntu on Wayland" >> instead? >> >> Secondly the kernel: Does the bug occur if you install the latest test >> kernel packages from here?https://kernel.ubuntu.com/~kernel- >> ppa/mainline/v5.5-rc7/ Remember to run 'uname -a' to check which kernel >> is active. >> > -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1860483 Title: [nouveau] screen background overlaid with scan type artifact in red Status in linux package in Ubuntu: Incomplete Status in mesa package in Ubuntu: Incomplete Status in mutter package in Ubuntu: Incomplete Bug description: My desktop has both it's usual items in place; toolbar on left and desktop icons distributed around the screen. Then there's what appears to be a bunch of scan line, raster line artifacts, in red, laid over my normal background, which is a star field photo on what is ordinarily a black field. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-74.84-generic 4.15.18 Uname: Linux 4.15.0-74-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Jan 21 13:04:20 2020 DistUpgraded: 2018-10-03 14:38:19,863 DEBUG icon theme changed, re-reading DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation G72 [GeForce 7300 LE] [10de:01d1] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell G72 [GeForce 7300 LE] [1028:0405] InstallationDate: Installed on 2016-08-19 (1249 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: Dell Inc. Inspiron 531 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-74-generic root=UUID=08d8f7c1-e351-4abe-8ebe-443d6a751497 ro plymouth:debug=1 quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to bionic on 2018-10-03 (474 days ago) dmi.bios.date: 11/09/2007 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.7 dmi.board.name: 0RY206 dmi.board.vendor: Dell Inc. dmi.board.version: ��� dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.chassis.version:
[Kernel-packages] [Bug 1850130] Re: zpools fail to import after reboot on fresh install of eoan
@gustypants: Sorry, the other one is scan, not pool. Are you using a multipath setup? Does the pool import fine if you do it manually once booted? -- 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/1850130 Title: zpools fail to import after reboot on fresh install of eoan Status in zfs-linux package in Ubuntu: Confirmed Bug description: Fresh installation of stock Ubuntu 19.10 Eoan with experimental root on ZFS. System has existing zpools with data. Installation is uneventful. First boot with no problems. Updates applied. No other changes from fresh installation. Reboot. External pool 'tank' imports with no errors. Reboot. External pool has failed to import on boot. In contrast bpool and rpool are ok. Manually re-import 'tank' with no issues. I can see both 'tank' and its path in /dev/disk/by-id/ in /etc/zfs/zpool.cache. Reboot. 'tank' has failed to import on boot. It is also missing from /etc/zfs/zpool.cache. Is it possible that the cache is being re- generated on reboot, and the newly imported pools are getting erased from it? I can re-import the pools again manually with no issues, but they don't persist between re-boots. Installing normally on ext4 this is not an issue and data pools import automatically on boot with no further effort. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1850130/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1859795] Re: bionic/linux-aws: 4.15.0-1058.60 -proposed tracker
** 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: '1860123' packages: lrm: linux-restricted-modules-aws main: linux-aws meta: linux-meta-aws phase: Testing phase-changed: Thursday, 16. January 2020 10:17 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 1859801 bionic/linux-aws/aws-kernel: bug 1859794 xenial/linux-aws-hwe: bug 1859802 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/1859795 Title: bionic/linux-aws: 4.15.0-1058.60 -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: '1860123' packages: lrm: linux-restricted-modules-aws main: linux-aws meta: linux-meta-aws phase: Testing phase-changed: Thursday, 16. January 2020 10:17 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 1859801 bionic/linux-aws/aws-kernel: bug 1859794 xenial/linux-aws-hwe: bug 1859802 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1859795/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1854550] Re: [scsi-1130]scsi: scsi_transport_sas: Fix memory leak when removing devices
** Changed in: kunpeng920/ubuntu-18.04-hwe Status: In Progress => Fix Committed ** Changed in: kunpeng920/ubuntu-20.04 Status: In Progress => Fix Committed ** Changed in: kunpeng920 Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1854550 Title: [scsi-1130]scsi: scsi_transport_sas: Fix memory leak when removing devices Status in kunpeng920: Fix Committed Status in kunpeng920 ubuntu-18.04 series: Invalid Status in kunpeng920 ubuntu-18.04-hwe series: Fix Committed 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: Fix Committed Status in kunpeng920 upstream-kernel series: Fix Committed Status in linux package in Ubuntu: Fix Committed Bug description: [Impact] kmemleak detects potential leaks and this is the fix [Test Case] Not known case, regression test on system with SAS host is needed. [Fix] 82ea3e0e12 scsi: scsi_transport_sas: Fix memory leak when removing devices [Regression Risk] Patch is simple and reviewed on upstream. Since modification is for scsi subsystem not on a single driver, applying on focal gives us enough time for test. "[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:
[Kernel-packages] [Bug 1860574] Re: [UBUNTU 20.04] zkey: Fix display of clear key size for XTS keys
** Also affects: ubuntu-z-systems Importance: Undecided Status: New ** Package changed: linux (Ubuntu) => s390-tools (Ubuntu) ** Changed in: ubuntu-z-systems Importance: Undecided => High ** Changed in: ubuntu-z-systems Status: New => Triaged ** Changed in: ubuntu-z-systems Assignee: (unassigned) => Canonical Foundations Team (canonical-foundations) ** Also affects: s390-tools (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: s390-tools (Ubuntu Focal) Importance: Undecided Assignee: Skipper Bug Screeners (skipper-screen-team) Status: New ** Also affects: s390-tools (Ubuntu Eoan) 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/1860574 Title: [UBUNTU 20.04] zkey: Fix display of clear key size for XTS keys Status in Ubuntu on IBM z Systems: Triaged Status in s390-tools package in Ubuntu: New Status in s390-tools source package in Bionic: New Status in s390-tools source package in Eoan: New Status in s390-tools source package in Focal: New Bug description: Description: zkey: Fix display of clear key size for XTS keys Symptom: The 'zkey list' command shows bogus values for the keys 'Clear key size' for XTS keys of type CCA-AESDATA or CCA-AESCIPHER. Problem: XTS keys consist of 2 keys concatenated to each other. To calculate the clear key size, the clear key size of both keys must be added. The code does not address the second key correctly, and thus reads the clear key size of the second key from an invalid memory location. This results in bogus values reported as clear key size. This bug has been introduced with feature "Cipher key support" with commit 298fab68fee8 "zkey: Preparations for introducing a new key type". Solution: Correct the addressing of the second key. Reproduction: Generate an XTS key of type CCA-AESDATA or CCA-AESCIPHER and then run 'zkey list'. Upstream commit: https://github.com/ibm-s390-tools/s390-tools/commit/e7f446432b92b293e758099842843cfb1f18fa97 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1860574/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1859700] Re: bionic/linux-raspi2: 4.15.0-1054.58 -proposed tracker
** 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: '1860123' packages: main: linux-raspi2 meta: linux-meta-raspi2 phase: Testing phase-changed: Thursday, 16. January 2020 00:31 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-raspi2/pi-kernel: bug 1859699 variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi2 in Ubuntu. https://bugs.launchpad.net/bugs/1859700 Title: bionic/linux-raspi2: 4.15.0-1054.58 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Fix Released Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux-raspi2 package in Ubuntu: Invalid Status in linux-raspi2 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: '1860123' packages: main: linux-raspi2 meta: linux-meta-raspi2 phase: Testing phase-changed: Thursday, 16. January 2020 00:31 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-raspi2/pi-kernel: bug 1859699 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1859700/+subscriptions -- Mailing list: https://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 1860483] Re: [nouveau] screen background overlaid with scan type artifact in red
I encountered an issue after advising you that 18.04.3 works. Perhaps it sheds some light on the problem. It occurred to me that perhaps there is a graphics issue and that part of what I was seeing is contamination of the background image I was using. So I tried to open "Settings" in order to revert to the default image. Didn't work; that is, "Settings" doesn't work. No response. I can click on "Settings" on either toolbar or try to access it through "Show Applications" and no response. What's more, after getting no response there, other stuff is locked out and doesn't respond. I have to reboot to get functionality back. In getting to reboot, the shutdown process does report that anything I've tried to open or start, after trying to reach "Settings", isn't responding, and then it hangs. If I click on "Power down" again at that point, it doesn't, it just puts up an image and stalls (the image it displays is the background image I've been using, without the toolbars and the contaminant artifact!). At that point, I've just hit the power switch. I've not tried "Ubuntu on Wayland" or the test kernel package. I'll see what happens there. I can boot into the prior Linux generic via grub; haven't tried to pull up any apps there, but the image issue was still there. On 1/22/20 12:43 AM, Daniel van Vugt wrote: > OK, thanks. Assuming the bug isn't just hiding and wouldn't reappear > later in 18.04.3 if used long enough, then this implies a fix exists > somewhere in the HWE packages (which are the difference between 18.04 > fully updated and 18.04.3 fully updated). > > The only two sets of HWE packages I can think of that affect graphics > are Xorg and the kernel. > > Firstly Xorg: Does the bug occur if you log into "Ubuntu on Wayland" > instead? > > Secondly the kernel: Does the bug occur if you install the latest test > kernel packages from here? https://kernel.ubuntu.com/~kernel- > ppa/mainline/v5.5-rc7/ Remember to run 'uname -a' to check which kernel > is active. > -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1860483 Title: [nouveau] screen background overlaid with scan type artifact in red Status in linux package in Ubuntu: Incomplete Status in mesa package in Ubuntu: Incomplete Status in mutter package in Ubuntu: Incomplete Bug description: My desktop has both it's usual items in place; toolbar on left and desktop icons distributed around the screen. Then there's what appears to be a bunch of scan line, raster line artifacts, in red, laid over my normal background, which is a star field photo on what is ordinarily a black field. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-74.84-generic 4.15.18 Uname: Linux 4.15.0-74-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Jan 21 13:04:20 2020 DistUpgraded: 2018-10-03 14:38:19,863 DEBUG icon theme changed, re-reading DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation G72 [GeForce 7300 LE] [10de:01d1] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell G72 [GeForce 7300 LE] [1028:0405] InstallationDate: Installed on 2016-08-19 (1249 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: Dell Inc. Inspiron 531 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-74-generic root=UUID=08d8f7c1-e351-4abe-8ebe-443d6a751497 ro plymouth:debug=1 quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to bionic on 2018-10-03 (474 days ago) dmi.bios.date: 11/09/2007 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.7 dmi.board.name: 0RY206 dmi.board.vendor: Dell Inc. dmi.board.version: ��� dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnDellInc.:bvr1.0.7:bd11/09/2007:svnDellInc.:pnInspiron531:pvr00:rvnDellInc.:rn0RY206:rvr:cvnDellInc.:ct3:cvrChassisVersion: dmi.product.name: Inspiron 531 dmi.product.version: 00 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.1-1ubuntu1~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1
[Kernel-packages] [Bug 1859839] Re: the sound is distorted when playing via nvidia hdmi
With Kernel 5.4.0-12-generic (from repository) the problem seems to be solved. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1859839 Title: the sound is distorted when playing via nvidia hdmi Status in linux package in Ubuntu: Incomplete Bug description: When playing back the sound via nv hdmi, the sound is distorted on Ubuntu 20.04 LTS with Kernel 5.4.0-9 No problem if i login with kernel 5.3.0-24-generic Ubuntu 20.04 LTS nvidia 440.44 alsa 1.0.25+dfsg-0ubuntu5 pulseaudio 1:13.0-3ubuntu1 kernel 5.4.0-9.12 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: marco 1792 F pulseaudio /dev/snd/controlC1: marco 1792 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-01-15 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200106) IwConfig: lono wireless extensions. enp34s0 no wireless extensions. MachineType: Micro-Star International Co., Ltd MS-7C02 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-9-generic root=UUID=30c539b6-2e84-470d-bac2-486e25129f20 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3 RelatedPackageVersions: linux-restricted-modules-5.4.0-9-generic N/A linux-backports-modules-5.4.0-9-generic N/A linux-firmware 1.184 RfKill: Tags: focal Uname: Linux 5.4.0-9-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: 11/07/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3.50 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B450 TOMAHAWK MAX (MS-7C02) dmi.board.vendor: Micro-Star International Co., Ltd dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3.50:bd11/07/2019:svnMicro-StarInternationalCo.,Ltd:pnMS-7C02:pvr1.0:rvnMicro-StarInternationalCo.,Ltd:rnB450TOMAHAWKMAX(MS-7C02):rvr1.0:cvnMicro-StarInternationalCo.,Ltd:ct3:cvr1.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7C02 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1859839/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1860574] [NEW] [UBUNTU 20.04] zkey: Fix display of clear key size for XTS keys
Public bug reported: Description: zkey: Fix display of clear key size for XTS keys Symptom: The 'zkey list' command shows bogus values for the keys 'Clear key size' for XTS keys of type CCA-AESDATA or CCA-AESCIPHER. Problem: XTS keys consist of 2 keys concatenated to each other. To calculate the clear key size, the clear key size of both keys must be added. The code does not address the second key correctly, and thus reads the clear key size of the second key from an invalid memory location. This results in bogus values reported as clear key size. This bug has been introduced with feature "Cipher key support" with commit 298fab68fee8 "zkey: Preparations for introducing a new key type". Solution: Correct the addressing of the second key. Reproduction: Generate an XTS key of type CCA-AESDATA or CCA-AESCIPHER and then run 'zkey list'. Upstream commit: https://github.com/ibm-s390-tools/s390-tools/commit/e7f446432b92b293e758099842843cfb1f18fa97 ** Affects: linux (Ubuntu) Importance: Undecided Assignee: Skipper Bug Screeners (skipper-screen-team) Status: New ** Tags: architecture-s39064 bugnameltc-183404 severity-high targetmilestone-inin2004 ** Tags added: architecture-s39064 bugnameltc-183404 severity-high targetmilestone-inin2004 ** Changed in: ubuntu Assignee: (unassigned) => Skipper Bug Screeners (skipper-screen-team) ** Package changed: ubuntu => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1860574 Title: [UBUNTU 20.04] zkey: Fix display of clear key size for XTS keys Status in linux package in Ubuntu: New Bug description: Description: zkey: Fix display of clear key size for XTS keys Symptom: The 'zkey list' command shows bogus values for the keys 'Clear key size' for XTS keys of type CCA-AESDATA or CCA-AESCIPHER. Problem: XTS keys consist of 2 keys concatenated to each other. To calculate the clear key size, the clear key size of both keys must be added. The code does not address the second key correctly, and thus reads the clear key size of the second key from an invalid memory location. This results in bogus values reported as clear key size. This bug has been introduced with feature "Cipher key support" with commit 298fab68fee8 "zkey: Preparations for introducing a new key type". Solution: Correct the addressing of the second key. Reproduction: Generate an XTS key of type CCA-AESDATA or CCA-AESCIPHER and then run 'zkey list'. Upstream commit: https://github.com/ibm-s390-tools/s390-tools/commit/e7f446432b92b293e758099842843cfb1f18fa97 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860574/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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
On bios 1.10.0 that was released yesterday with kernel 5.4(fedora) I no longer have this issue. The keyboard and mouse work on boot for me. -- You 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 1860574] [NEW] [UBUNTU 20.04] zkey: Fix display of clear key size for XTS keys
You have been subscribed to a public bug: Description: zkey: Fix display of clear key size for XTS keys Symptom: The 'zkey list' command shows bogus values for the keys 'Clear key size' for XTS keys of type CCA-AESDATA or CCA-AESCIPHER. Problem: XTS keys consist of 2 keys concatenated to each other. To calculate the clear key size, the clear key size of both keys must be added. The code does not address the second key correctly, and thus reads the clear key size of the second key from an invalid memory location. This results in bogus values reported as clear key size. This bug has been introduced with feature "Cipher key support" with commit 298fab68fee8 "zkey: Preparations for introducing a new key type". Solution: Correct the addressing of the second key. Reproduction: Generate an XTS key of type CCA-AESDATA or CCA-AESCIPHER and then run 'zkey list'. Upstream commit: https://github.com/ibm-s390-tools/s390-tools/commit/e7f446432b92b293e758099842843cfb1f18fa97 ** Affects: linux (Ubuntu) Importance: Undecided Assignee: Skipper Bug Screeners (skipper-screen-team) Status: New ** Tags: architecture-s39064 bugnameltc-183404 severity-high targetmilestone-inin2004 -- [UBUNTU 20.04] zkey: Fix display of clear key size for XTS keys https://bugs.launchpad.net/bugs/1860574 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1509717] Re: Wily LVM-RAID1 – md: personality for level 1 is not loaded
** Description changed: - After upgrading to Wily, raid1 LVs don't activate during the initrd - phase. Since the root LV is also RAID1-mirrored, the system doesn't - boot. + [Impact] + system does not boot after converting lvm volume to raid1 w/o having mdadm installed. + + [Test case] + + 1. Install server with subiquity to VM + 2. Add second disk to it + 3. Run pvcreate /dev/vdb + 4. Run vgextend ubuntu-vg /dev/vdb + 5. Run lvconvert -m1 --type raid1 ubuntu-vg/lv + + Reboot and check that it still boots. + + [Regression potential] + Not really anything, we just add the raid1 module to initramfs, so it might be loaded during boot, and raid1 logical volumes might appear earlier. + + [Original bug report] + After upgrading to Wily, raid1 LVs don't activate during the initrd phase. Since the root LV is also RAID1-mirrored, the system doesn't boot. I get the following message each time LVM tries to activate a raid1 LV: md: personality for level 1 is not loaded! Everything was fine with Vivid. I had to downgrade to Vivid kernel (3.19.0-30) to get my system to a usable state. I pretty much hope it to be a temporary workaround and I'll get the new 4.2.0 kernel work with Wily in days. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1509717 Title: Wily LVM-RAID1 – md: personality for level 1 is not loaded Status in linux package in Ubuntu: Invalid Status in lvm2 package in Ubuntu: Fix Released Status in linux source package in Bionic: Invalid Status in lvm2 source package in Bionic: New Status in linux source package in Cosmic: Invalid Status in lvm2 source package in Cosmic: Won't Fix Status in linux source package in Disco: Invalid Status in lvm2 source package in Disco: Won't Fix Status in linux source package in Eoan: Invalid Status in lvm2 source package in Eoan: Triaged Status in lvm2 package in Debian: Incomplete Bug description: [Impact] system does not boot after converting lvm volume to raid1 w/o having mdadm installed. [Test case] 1. Install server with subiquity to VM 2. Add second disk to it 3. Run pvcreate /dev/vdb 4. Run vgextend ubuntu-vg /dev/vdb 5. Run lvconvert -m1 --type raid1 ubuntu-vg/lv Reboot and check that it still boots. [Regression potential] Not really anything, we just add the raid1 module to initramfs, so it might be loaded during boot, and raid1 logical volumes might appear earlier. [Original bug report] After upgrading to Wily, raid1 LVs don't activate during the initrd phase. Since the root LV is also RAID1-mirrored, the system doesn't boot. I get the following message each time LVM tries to activate a raid1 LV: md: personality for level 1 is not loaded! Everything was fine with Vivid. I had to downgrade to Vivid kernel (3.19.0-30) to get my system to a usable state. I pretty much hope it to be a temporary workaround and I'll get the new 4.2.0 kernel work with Wily in days. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1509717/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1860559] Re: [18.04.4] System fails to reboot after installation
Diff of the manifest between last known good image and first broken image. noticeable packages are gcc-8 and upgrade of linux 5.0 to linux 5.3 ** Patch added: "bionic-desktop-amd64.manifest.20191210-12.diff" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860559/+attachment/5322192/+files/bionic-desktop-amd64.manifest.20191210-12.diff -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1860559 Title: [18.04.4] System fails to reboot after installation Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: New Bug description: bionic desktop 20190122 Since bionic 20191211 the system doesn't reboot after installation. After pressing enter to reboot, the system hangs. There is this message printed in a loop on the console: [sdb] tag#0 access beyond end of device 20191211 includes a new kernel and a new gcc ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubiquity (not installed) ProcVersionSignature: Ubuntu 5.3.0-28.30~18.04.1-generic 5.3.13 Uname: Linux 5.3.0-28-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.10 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Jan 22 15:17:58 2020 InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper initrd=/casper/initrd quiet splash --- maybe-ubiquity InstallationDate: Installed on 2020-01-22 (0 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Beta amd64 (20200122) SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860559/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1860231] Re: 5.4.0-11 crash on cryptsetup open
** Changed in: linux (Ubuntu) Status: Incomplete => Triaged ** Changed in: linux (Ubuntu) Importance: Undecided => High ** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Eoan) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Disco) 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/1860231 Title: 5.4.0-11 crash on cryptsetup open Status in linux package in Ubuntu: Triaged Status in linux source package in Xenial: New Status in linux source package in Bionic: New Status in linux source package in Disco: New Status in linux source package in Eoan: New Bug description: [Impact] An attempt to run cryptsetup open on a newly created LUKS partition on Ubuntu Core 20 causes a kernel crash. This happens in 100% of the attempts on the snapd Core 20 installation test, but on an image created to reproduce this bug it happens only when certain parameters are passed to cryptsetup. Both images are built similarly so the reason for this discrepancy is unknown. The kernel was installed from pc-kernel_374.snap. [Test Case] $ dir=$(mktemp -d /tmp/lp1860231.X) $ dmsetup create lp1860231 --notable $ mount -t ext4 \ "/dev/dm-$(dmsetup info -c -o minor --noheadings lp1860231)" "$dir" Now check the logs for a backtrace. [Regression Potential] The currently proposed fix introduces no chance of stability regressions. There is a chance of a very small performance regression since an additional pointer comparison is performed on each block layer request but this is unlikely to be noticeable. [Original Report] Linux version 5.4.0-11-generic (buildd@lgw01-amd64-021) (gcc version 9.2.1 20200104 (Ubuntu 9.2.1-22ubuntu2)) #14-Ubuntu SMP Thu Jan 9 16:14:26 UTC 2020 Version signature: Ubuntu 5.4.0-11.14-generic 5.4.8 How to reproduce the crash in 3 "easy" steps: 1. Build a Core 20 image using the attached model file: 1.1. Install the ubuntu-image from latest/edge $ sudo snap install --channel latest/edge ubuntu-image 1.2. Build the image $ sudo ubuntu-image --image-size=4G ubuntu-core-20-amd64.model 2. Boot the image in kvm 2.1. Install ovmf version 0~20190606.20d2e5a1-2ubuntu1 or newer (the stock ovmf from bionic may not work) 2.2. Boot the image $ sudo kvm -snapshot -m 2048 -smp 4 \ -netdev user,id=mynet0,hostfwd=tcp::8022-:22,hostfwd=tcp::8090-:80 \ -device virtio-net-pci,netdev=mynet0 \ -drive file=pc.img,if=virtio \ -bios /usr/share/OVMF/OVMF_CODE.ms.fd 2.3. In the grub menu, edit the default option to include parameter "systemd.debug-shell=1" in the kernel command line 2.4. Boot the kernel 3. Crash the kernel 3.1. When the system boots to the "Press enter to configure" message, press ALT-F9 to enter the debug shell. 3.2. The system should have two partitions in /dev/vda. Create a third one with fdisk. 3.3. Create a LUKS encrypted partition: # echo 123|cryptsetup luksFormat -q --type luks2 --key-file - --pbkdf argon2i --iter-time 1 /dev/vda3 (the system will complain about a missing locking directory, just ignore it.) 3.4. Open the encrypted device: # echo 123|cryptsetup open --key-file - /dev/vda name The Core 20 images contain the following udev rule which causes the new block device to be mounted automatically. This mount is what triggers the BUG: ACTION=="add", SUBSYSTEM=="block", KERNEL!="loop*", KERNEL!="ram*" \ RUN+="/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/%k" 3.5. Read the crash message The attached screenshots show these steps being executed. A few notes: - The backtrace seems very similar to the one reported in bug #1835279, however that problem was possibly caused by a race between partition creation and LUKS formatting. This time it doesn't seem to be the case, delays between commands don't help us here. - In the test case above using large values of KDF iter-time may prevent the crash. I successfully opened the device in kernel 5.4.0-9 with --iter-time larger than 100, but 5.4.0-11 seems to require values closer to 1000. Regardless of the --iter-time value used, the crash always happen when running the test in a spread-driven automated environment (same kernel with image built in the same way, some other variable seems to be disturbing the system). - All necessary modules are loaded before the LUKS partition creation (i.e. it doesn't seem to be caused by a race between dm-crypt loading and cryptsetup
[Kernel-packages] [Bug 1860231] Re: 5.4.0-11 crash on cryptsetup open
** Description changed: - An attempt to run cryptsetup open on a newly created LUKS partition on - Ubuntu Core 20 causes a kernel crash. This happens in 100% of the - attempts on the snapd Core 20 installation test, but on an image created - to reproduce this bug it happens only when certain parameters are passed - to cryptsetup. Both images are built similarly so the reason for this - discrepancy is unknown. The kernel was installed from pc- - kernel_374.snap. + [Impact] + An attempt to run cryptsetup open on a newly created LUKS partition on Ubuntu Core 20 causes a kernel crash. This happens in 100% of the attempts on the snapd Core 20 installation test, but on an image created to reproduce this bug it happens only when certain parameters are passed to cryptsetup. Both images are built similarly so the reason for this discrepancy is unknown. The kernel was installed from pc-kernel_374.snap. - Linux version 5.4.0-11-generic (buildd@lgw01-amd64-021) (gcc version - 9.2.1 20200104 (Ubuntu 9.2.1-22ubuntu2)) #14-Ubuntu SMP Thu Jan 9 - 16:14:26 UTC 2020 + [Test Case] + + $ dir=$(mktemp -d /tmp/lp1860231.X) + $ dmsetup create lp1860231 --notable + $ mount -t ext4 \ + "/dev/dm-$(dmsetup info -c -o minor --noheadings lp1860231)" "$dir" + + Now check the logs for a backtrace. + + [Regression Potential] + + The currently proposed fix introduces no chance of stability + regressions. There is a chance of a very small performance regression + since an additional pointer comparison is performed on each block layer + request but this is unlikely to be noticeable. + + [Original Report] + + + Linux version 5.4.0-11-generic (buildd@lgw01-amd64-021) (gcc version 9.2.1 20200104 (Ubuntu 9.2.1-22ubuntu2)) #14-Ubuntu SMP Thu Jan 9 16:14:26 UTC 2020 Version signature: Ubuntu 5.4.0-11.14-generic 5.4.8 How to reproduce the crash in 3 "easy" steps: 1. Build a Core 20 image using the attached model file: 1.1. Install the ubuntu-image from latest/edge $ sudo snap install --channel latest/edge ubuntu-image 1.2. Build the image $ sudo ubuntu-image --image-size=4G ubuntu-core-20-amd64.model 2. Boot the image in kvm 2.1. Install ovmf version 0~20190606.20d2e5a1-2ubuntu1 or newer (the stock ovmf from bionic may not work) 2.2. Boot the image $ sudo kvm -snapshot -m 2048 -smp 4 \ -netdev user,id=mynet0,hostfwd=tcp::8022-:22,hostfwd=tcp::8090-:80 \ -device virtio-net-pci,netdev=mynet0 \ -drive file=pc.img,if=virtio \ -bios /usr/share/OVMF/OVMF_CODE.ms.fd 2.3. In the grub menu, edit the default option to include parameter "systemd.debug-shell=1" in the kernel command line 2.4. Boot the kernel 3. Crash the kernel 3.1. When the system boots to the "Press enter to configure" message, press ALT-F9 to enter the debug shell. 3.2. The system should have two partitions in /dev/vda. Create a third one with fdisk. 3.3. Create a LUKS encrypted partition: # echo 123|cryptsetup luksFormat -q --type luks2 --key-file - --pbkdf argon2i --iter-time 1 /dev/vda3 (the system will complain about a missing locking directory, just ignore it.) 3.4. Open the encrypted device: # echo 123|cryptsetup open --key-file - /dev/vda name - The Core 20 images contain the following udev rule which causes - the new block device to be mounted automatically. This mount is - what triggers the BUG: - ACTION=="add", SUBSYSTEM=="block", KERNEL!="loop*", KERNEL!="ram*" \ - RUN+="/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/%k" + The Core 20 images contain the following udev rule which causes + the new block device to be mounted automatically. This mount is + what triggers the BUG: + ACTION=="add", SUBSYSTEM=="block", KERNEL!="loop*", KERNEL!="ram*" \ + RUN+="/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/%k" 3.5. Read the crash message The attached screenshots show these steps being executed. A few notes: - The backtrace seems very similar to the one reported in bug #1835279, however that problem was possibly caused by a race between partition creation and LUKS formatting. This time it doesn't seem to be the case, delays between commands don't help us here. - In the test case above using large values of KDF iter-time may prevent the crash. I successfully opened the device in kernel 5.4.0-9 with --iter-time larger than 100, but 5.4.0-11 seems to require values closer to 1000. Regardless of the --iter-time value used, the crash always happen when running the test in a spread-driven automated environment (same kernel with image built in the same way, some other variable seems to be disturbing the system). - All necessary modules are loaded before the LUKS partition creation (i.e. it doesn't seem
[Kernel-packages] [Bug 1851162] Re: nvidia-drivers-390 fail to build with kernel 5.3
All good here too with 390.116-0ubuntu0.18.04.3 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1851162 Title: nvidia-drivers-390 fail to build with kernel 5.3 Status in linux package in Ubuntu: Confirmed Status in linux-hwe package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-390 package in Ubuntu: Confirmed Status in linux source package in Bionic: Confirmed Status in linux-hwe source package in Bionic: Confirmed Status in nvidia-graphics-drivers-390 source package in Bionic: Fix Committed Bug description: nvidia-graphics-drivers-390 fails to build against linux 5.3. SRU Request: [Test Case] 1) Enable the -proposed repository, and install the new 390 NVIDIA driver (nvidia-graphics-drivers-390_390.116-0ubuntu0.18.04.2). 2) Check that the kernel module can be built against the new kernel. 3) Restart your computer, and see if everything works correctly when accessing the desktop. [Regression Potential] Low. The update only fixes build issues with Linux versions 5.3. __ With linux-image-5.0.0-23 I had no problems. Following an update linux-image-5.3.0-19 was installed, the DKMS build failed, and the system became unusable. Removing 5.3.0 brings the system back. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: nvidia-driver-390 390.116-0ubuntu0.18.04.1 ProcVersionSignature: Ubuntu 5.0.0-23.24~18.04.1-generic 5.0.15 Uname: Linux 5.0.0-23-generic x86_64 NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.8 Architecture: amd64 CurrentDesktop: MATE Date: Sun Nov 3 19:55:57 2019 InstallationDate: Installed on 2019-06-09 (147 days ago) InstallationMedia: Ubuntu-MATE 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) SourcePackage: nvidia-graphics-drivers-390 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1851162/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1851162] Re: nvidia-drivers-390 fail to build with kernel 5.3
** Tags removed: verification-needed verification-needed-bionic ** Tags added: verification-done verification-done-bionic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1851162 Title: nvidia-drivers-390 fail to build with kernel 5.3 Status in linux package in Ubuntu: Confirmed Status in linux-hwe package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-390 package in Ubuntu: Confirmed Status in linux source package in Bionic: Confirmed Status in linux-hwe source package in Bionic: Confirmed Status in nvidia-graphics-drivers-390 source package in Bionic: Fix Committed Bug description: nvidia-graphics-drivers-390 fails to build against linux 5.3. SRU Request: [Test Case] 1) Enable the -proposed repository, and install the new 390 NVIDIA driver (nvidia-graphics-drivers-390_390.116-0ubuntu0.18.04.2). 2) Check that the kernel module can be built against the new kernel. 3) Restart your computer, and see if everything works correctly when accessing the desktop. [Regression Potential] Low. The update only fixes build issues with Linux versions 5.3. __ With linux-image-5.0.0-23 I had no problems. Following an update linux-image-5.3.0-19 was installed, the DKMS build failed, and the system became unusable. Removing 5.3.0 brings the system back. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: nvidia-driver-390 390.116-0ubuntu0.18.04.1 ProcVersionSignature: Ubuntu 5.0.0-23.24~18.04.1-generic 5.0.15 Uname: Linux 5.0.0-23-generic x86_64 NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.8 Architecture: amd64 CurrentDesktop: MATE Date: Sun Nov 3 19:55:57 2019 InstallationDate: Installed on 2019-06-09 (147 days ago) InstallationMedia: Ubuntu-MATE 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) SourcePackage: nvidia-graphics-drivers-390 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1851162/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1860559] Re: [18.04.4] System fails to reboot after installation
** Package changed: ubiquity (Ubuntu) => linux (Ubuntu) ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Bionic) Importance: Undecided => Critical ** Changed in: linux (Ubuntu) Status: New => Fix Released ** Changed in: linux (Ubuntu Bionic) Milestone: None => ubuntu-18.04.4 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1860559 Title: [18.04.4] System fails to reboot after installation Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: New Bug description: bionic desktop 20190122 Since bionic 20191211 the system doesn't reboot after installation. After pressing enter to reboot, the system hangs. There is this message printed in a loop on the console: [sdb] tag#0 access beyond end of device 20191211 includes a new kernel and a new gcc ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubiquity (not installed) ProcVersionSignature: Ubuntu 5.3.0-28.30~18.04.1-generic 5.3.13 Uname: Linux 5.3.0-28-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.10 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Jan 22 15:17:58 2020 InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper initrd=/casper/initrd quiet splash --- maybe-ubiquity InstallationDate: Installed on 2020-01-22 (0 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Beta amd64 (20200122) SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860559/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1860523] Re: [UBUNTU] Fix the misleading error message: Configuring the VNIC characteristics failed
** Summary changed: - [UBUNTU-18.04] Fix for "Configuring the VNIC characteristics failed" + [UBUNTU] Fix the misleading error message: Configuring the VNIC characteristics failed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1860523 Title: [UBUNTU] Fix the misleading error message: Configuring the VNIC characteristics failed Status in Ubuntu on IBM z Systems: New Status in linux package in Ubuntu: New Status in linux source package in Bionic: New Status in linux source package in Eoan: New Status in linux source package in Focal: New Bug description: The patch titled s390/qeth: fix false reporting of VNIC CHAR config failure has been added to the 4.19-stable tree which can be found at: http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary The filename of the patch is: s390-qeth-fix-false-reporting-of-vnic- char-config-failure.patch and it can be found in the queue-4.19 subdirectory. Same for the the 5.4-stable tree which can be found at: http://www.kernel.org/git/?p=linux/kernel/git/stable/stable- queue.git;a=summary The filename of the patch is: s390-qeth-fix-vnicc_is_in_use-if- rx_bcast-not-set.patch and it can be found in the queue-5.4 subdirectory. s390/qeth: fix false reporting of VNIC CHAR config failure commit 68c57bfd52836e31bff33e5e1fc64029749d2c35 upstream. Request: Please provide that fix also for Ubuntu 18.04 . Many thanks in advance To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1860523/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1860559] [NEW] [18.04.4] System fails to reboot after installation
You have been subscribed to a public bug: bionic desktop 20190122 Since bionic 20191211 the system doesn't reboot after installation. After pressing enter to reboot, the system hangs. There is this message printed in a loop on the console: [sdb] tag#0 access beyond end of device 20191211 includes a new kernel and a new gcc ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubiquity (not installed) ProcVersionSignature: Ubuntu 5.3.0-28.30~18.04.1-generic 5.3.13 Uname: Linux 5.3.0-28-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.10 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Jan 22 15:17:58 2020 InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper initrd=/casper/initrd quiet splash --- maybe-ubiquity InstallationDate: Installed on 2020-01-22 (0 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Beta amd64 (20200122) SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux (Ubuntu) Importance: Critical Status: New ** Tags: amd64 apport-bug bionic rls-bb-incoming ubiquity-18.04.14.13 -- [18.04.4] System fails to reboot after installation https://bugs.launchpad.net/bugs/1860559 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1859702] Re: bionic/linux-oem: 4.15.0-1067.77 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: '1860123' packages: lrm: linux-restricted-modules-oem main: linux-oem meta: linux-meta-oem signed: linux-signed-oem phase: Testing phase-changed: Tuesday, 21. January 2020 16:47 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - certification-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem in Ubuntu. https://bugs.launchpad.net/bugs/1859702 Title: bionic/linux-oem: 4.15.0-1067.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: 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-oem package in Ubuntu: Invalid Status in linux-oem source package in Bionic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: '1860123' packages: lrm: linux-restricted-modules-oem main: linux-oem meta: linux-meta-oem signed: linux-signed-oem phase: Testing phase-changed: Tuesday, 21. January 2020 16:47 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1859702/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1860123] Re: bionic/linux: 4.15.0-76.86 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true bugs-spammed: true packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Testing phase-changed: Monday, 20. January 2020 14:12 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Ongoing -- testing in progress - security-signoff: Pending -- waiting for signoff + security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-aws: bug 1859795 bionic/linux-oem: bug 1859702 bionic/linux-raspi2: bug 1859700 bionic/linux-snapdragon: bug 1859793 bionic/linux/pc-kernel: bug 1860120 bionic/linux/pc-lowlatency-kernel: bug 1860121 xenial/linux-azure: bug 1859798 xenial/linux-hwe: bug 1860122 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/1860123 Title: bionic/linux: 4.15.0-76.86 -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: Monday, 20. January 2020 14:12 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 1859795 bionic/linux-oem: bug 1859702 bionic/linux-raspi2: bug 1859700 bionic/linux-snapdragon: bug 1859793 bionic/linux/pc-kernel: bug 1860120 bionic/linux/pc-lowlatency-kernel: bug 1860121 xenial/linux-azure: bug 1859798 xenial/linux-hwe: bug 1860122 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1860123/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1860119] Re: eoan/linux: 5.3.0-29.31 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true bugs-spammed: true packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Testing phase-changed: Monday, 20. January 2020 14:11 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Ongoing -- testing in progress - security-signoff: Pending -- waiting for signoff + security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-hwe: bug 1859693 eoan/linux-raspi2: bug 1859692 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/1860119 Title: eoan/linux: 5.3.0-29.31 -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 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 bugs-spammed: true packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Testing phase-changed: Monday, 20. January 2020 14: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: bionic/linux-hwe: bug 1859693 eoan/linux-raspi2: bug 1859692 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1860119/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1859702] Re: bionic/linux-oem: 4.15.0-1067.77 -proposed tracker
Kernel deb testing completes, no regressions found. Ready for Updates. Results here: https://trello.com/c/DRAFW8jz/282-oem-linux- image-4150-1067-oem-4150-106777 ** Changed in: kernel-sru-workflow/certification-testing Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem in Ubuntu. https://bugs.launchpad.net/bugs/1859702 Title: bionic/linux-oem: 4.15.0-1067.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: 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-oem package in Ubuntu: Invalid Status in linux-oem source package in Bionic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: '1860123' packages: lrm: linux-restricted-modules-oem main: linux-oem meta: linux-meta-oem signed: linux-signed-oem phase: Testing phase-changed: Tuesday, 21. January 2020 16:47 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1859702/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1860535] Re: [UBUNTU] - Disable Thin Provisioning to prevent data loss
After the work on LP 1830731 got completed, problems occurred prior to the release of Eoan / kernel 5.3 and it got partially reverted based on LP 1846219: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1846219 Is the revert in LP 1846219 already sufficient to complete this ticket for Eoan? (I assume yes) Or do all the patches from LP 1830731 need to be reverted? ** Changed in: ubuntu-z-systems 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/1860535 Title: [UBUNTU] - Disable Thin Provisioning to prevent data loss Status in Ubuntu on IBM z Systems: Incomplete Status in linux package in Ubuntu: New Status in linux source package in Eoan: New Bug description: Discription will provided soon.. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1860535/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1859730] Re: [comet lake] Gnome freezes, icons missing, graphics corruption
Dear, I have the same mistakes again with Wayland and especially with the updates. I did everything you suggested, I no longer have outdated library problems but the bugs remain the same: c -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1859730 Title: [comet lake] Gnome freezes, icons missing, graphics corruption Status in linux package in Ubuntu: Incomplete Status in mesa package in Ubuntu: Incomplete Bug description: ack please.. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 Uname: Linux 5.4.11-050411-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CompositorRunning: None Date: Tue Jan 14 20:17:26 2020 DistUpgraded: Fresh install DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20180608-47+beaver-three-eyed-raven+X92 DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: backport-iwlwifi, 8286, 4.15.0-1042-oem, x86_64: installed backport-iwlwifi, 8286, 4.15.0-1066-oem, x86_64: installed ExtraDebuggingInterest: Yes GpuHangFrequency: Very infrequently GraphicsCard: Intel Corporation Device [8086:9bca] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0962] InstallationDate: Installed on 2020-01-13 (1 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 Lsusb: Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 8087:0029 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 13 7390 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=es_CL.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.11-050411-generic root=UUID=8fd25548-00af-4395-92f0-5d7d27a54deb ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/25/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.4.0 dmi.board.name: 0377MH dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.4.0:bd11/25/2019:svnDellInc.:pnXPS137390:pvr:rvnDellInc.:rn0377MH:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 7390 dmi.product.sku: 0962 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~18.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~18.04.3 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1859730/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1851162] Re: nvidia-drivers-390 fail to build with kernel 5.3
Problem fixed for me with 390.116-0ubuntu0.18.04.3 from bionic-proposed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1851162 Title: nvidia-drivers-390 fail to build with kernel 5.3 Status in linux package in Ubuntu: Confirmed Status in linux-hwe package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-390 package in Ubuntu: Confirmed Status in linux source package in Bionic: Confirmed Status in linux-hwe source package in Bionic: Confirmed Status in nvidia-graphics-drivers-390 source package in Bionic: Fix Committed Bug description: nvidia-graphics-drivers-390 fails to build against linux 5.3. SRU Request: [Test Case] 1) Enable the -proposed repository, and install the new 390 NVIDIA driver (nvidia-graphics-drivers-390_390.116-0ubuntu0.18.04.2). 2) Check that the kernel module can be built against the new kernel. 3) Restart your computer, and see if everything works correctly when accessing the desktop. [Regression Potential] Low. The update only fixes build issues with Linux versions 5.3. __ With linux-image-5.0.0-23 I had no problems. Following an update linux-image-5.3.0-19 was installed, the DKMS build failed, and the system became unusable. Removing 5.3.0 brings the system back. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: nvidia-driver-390 390.116-0ubuntu0.18.04.1 ProcVersionSignature: Ubuntu 5.0.0-23.24~18.04.1-generic 5.0.15 Uname: Linux 5.0.0-23-generic x86_64 NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.8 Architecture: amd64 CurrentDesktop: MATE Date: Sun Nov 3 19:55:57 2019 InstallationDate: Installed on 2019-06-09 (147 days ago) InstallationMedia: Ubuntu-MATE 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) SourcePackage: nvidia-graphics-drivers-390 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1851162/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1859702] Re: bionic/linux-oem: 4.15.0-1067.77 -proposed tracker
** 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: '1860123' packages: lrm: linux-restricted-modules-oem main: linux-oem meta: linux-meta-oem signed: linux-signed-oem phase: Testing phase-changed: Tuesday, 21. January 2020 16:47 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - automated-testing: Ongoing -- testing in progress certification-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem in Ubuntu. https://bugs.launchpad.net/bugs/1859702 Title: bionic/linux-oem: 4.15.0-1067.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-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-oem package in Ubuntu: Invalid Status in linux-oem source package in Bionic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: '1860123' packages: lrm: linux-restricted-modules-oem main: linux-oem meta: linux-meta-oem signed: linux-signed-oem phase: Testing phase-changed: Tuesday, 21. January 2020 16:47 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: certification-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1859702/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1860552] [NEW] Xiaomi RedmiBook 14" Ryzen Edition broken WiFi
Public bug reported: Running Linux RedmiBook 5.3.0-26-generic #28-Ubuntu SMP Wed Dec 18 05:37:46 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux lspci reports the device 01:00.0 Network controller: Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter (rev 32) dmesg shows following messages when modprobe ath10_pci [ 35.405479] ath10k_pci :01:00.0: pci irq msi oper_irq_mode 2 irq_mode 0 reset_mode 0 [ 35.677189] ath10k_pci :01:00.0: qca6174 hw3.2 target 0x0503 chip_id 0x00340aff sub 11ad:0847 [ 35.677191] ath10k_pci :01:00.0: kconfig debug 0 debugfs 1 tracing 1 dfs 0 testmode 0 [ 35.677655] ath10k_pci :01:00.0: firmware ver WLAN.RM.4.4.1-00140-QCARMSWPZ-1 api 6 features wowlan,ignore-otp,mfp crc32 29eb8ca1 [ 35.741238] ath10k_pci :01:00.0: failed to fetch board data for bus=pci,vendor=168c,device=003e,subsystem-vendor=11ad,subsystem-device=0847 from ath10k/QCA6174/hw3.0/board-2.bin [ 35.741396] ath10k_pci :01:00.0: board_file api 1 bmi_id N/A crc32 ed5f849a [ 35.813765] ath10k_pci :01:00.0: unsupported HTC service id: 1536 [ 36.237594] ath10k_pci :01:00.0: htt version request timed out [ 36.237601] ath10k_pci :01:00.0: failed to setup htt: -110 [ 36.317707] ath10k_pci :01:00.0: could not init core (-110) [ 36.317770] ath10k_pci :01:00.0: could not probe fw (-110) as a result no wifi no networks visible and no connection possible ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-firmware 1.183.3 ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13 Uname: Linux 5.3.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 Date: Wed Jan 22 16:26:03 2020 Dependencies: InstallationDate: Installed on 2020-01-20 (1 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) PackageArchitecture: all SourcePackage: linux-firmware UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-firmware (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1860552 Title: Xiaomi RedmiBook 14" Ryzen Edition broken WiFi Status in linux-firmware package in Ubuntu: New Bug description: Running Linux RedmiBook 5.3.0-26-generic #28-Ubuntu SMP Wed Dec 18 05:37:46 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux lspci reports the device 01:00.0 Network controller: Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter (rev 32) dmesg shows following messages when modprobe ath10_pci [ 35.405479] ath10k_pci :01:00.0: pci irq msi oper_irq_mode 2 irq_mode 0 reset_mode 0 [ 35.677189] ath10k_pci :01:00.0: qca6174 hw3.2 target 0x0503 chip_id 0x00340aff sub 11ad:0847 [ 35.677191] ath10k_pci :01:00.0: kconfig debug 0 debugfs 1 tracing 1 dfs 0 testmode 0 [ 35.677655] ath10k_pci :01:00.0: firmware ver WLAN.RM.4.4.1-00140-QCARMSWPZ-1 api 6 features wowlan,ignore-otp,mfp crc32 29eb8ca1 [ 35.741238] ath10k_pci :01:00.0: failed to fetch board data for bus=pci,vendor=168c,device=003e,subsystem-vendor=11ad,subsystem-device=0847 from ath10k/QCA6174/hw3.0/board-2.bin [ 35.741396] ath10k_pci :01:00.0: board_file api 1 bmi_id N/A crc32 ed5f849a [ 35.813765] ath10k_pci :01:00.0: unsupported HTC service id: 1536 [ 36.237594] ath10k_pci :01:00.0: htt version request timed out [ 36.237601] ath10k_pci :01:00.0: failed to setup htt: -110 [ 36.317707] ath10k_pci :01:00.0: could not init core (-110) [ 36.317770] ath10k_pci :01:00.0: could not probe fw (-110) as a result no wifi no networks visible and no connection possible ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-firmware 1.183.3 ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13 Uname: Linux 5.3.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 Date: Wed Jan 22 16:26:03 2020 Dependencies: InstallationDate: Installed on 2020-01-20 (1 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) PackageArchitecture: all SourcePackage: linux-firmware UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1860552/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1860535] Comment bridged from LTC Bugzilla
--- Comment From heinz-werner_se...@de.ibm.com 2020-01-22 08:25 EDT--- IBM has discovered a problem with a new feature within Ubuntu 19.10 with following feature request which might result in data loss., https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1830731 For 19.10 we will not provide a fix for it, but a patch for disabling this feature. For 20.04 a fix will be made available via backport from kernel 5.6 where the patch is targeted for. Info will follow -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1860535 Title: [UBUNTU] - Disable Thin Provisioning to prevent data loss Status in Ubuntu on IBM z Systems: New Status in linux package in Ubuntu: New Status in linux source package in Eoan: New Bug description: Discription will provided soon.. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1860535/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1860123] Re: bionic/linux: 4.15.0-76.86 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true bugs-spammed: true packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Testing phase-changed: Monday, 20. January 2020 14:12 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - automated-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-aws: bug 1859795 bionic/linux-oem: bug 1859702 bionic/linux-raspi2: bug 1859700 bionic/linux-snapdragon: bug 1859793 bionic/linux/pc-kernel: bug 1860120 bionic/linux/pc-lowlatency-kernel: bug 1860121 xenial/linux-azure: bug 1859798 xenial/linux-hwe: bug 1860122 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/1860123 Title: bionic/linux: 4.15.0-76.86 -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: Monday, 20. January 2020 14:12 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-aws: bug 1859795 bionic/linux-oem: bug 1859702 bionic/linux-raspi2: bug 1859700 bionic/linux-snapdragon: bug 1859793 bionic/linux/pc-kernel: bug 1860120 bionic/linux/pc-lowlatency-kernel: bug 1860121 xenial/linux-azure: bug 1859798 xenial/linux-hwe: bug 1860122 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1860123/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1860123] Re: bionic/linux: 4.15.0-76.86 -proposed tracker
At the moment we can't fix/hint that the network-manager MISS in our ADT testing. The problem is that a new version of network-manager was published to updates and later reverted. That caused our automation to still expect tests with that version. I'm flipping the ADT task manually because of that. ** Changed in: kernel-sru-workflow/automated-testing Status: In Progress => Fix Committed ** Changed in: kernel-sru-workflow/automated-testing Status: Fix Committed => 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/1860123 Title: bionic/linux: 4.15.0-76.86 -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: Monday, 20. January 2020 14:12 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-aws: bug 1859795 bionic/linux-oem: bug 1859702 bionic/linux-raspi2: bug 1859700 bionic/linux-snapdragon: bug 1859793 bionic/linux/pc-kernel: bug 1860120 bionic/linux/pc-lowlatency-kernel: bug 1860121 xenial/linux-azure: bug 1859798 xenial/linux-hwe: bug 1860122 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1860123/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1859096] Re: No sound or Crazy sound on Display port since kernel change to 5.4 (but 5.3.0-24 works)
Please see bisect.log in attachment. Fauty patch seems to be : # bad: [5398e94fb753d022301825ebfa5f7cf8a660d8eb] ALSA: hda - Add DP-MST support for NVIDIA codecs ** Attachment added: "bisect.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1859096/+attachment/5322151/+files/bisect.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1859096 Title: No sound or Crazy sound on Display port since kernel change to 5.4 (but 5.3.0-24 works) Status in linux package in Ubuntu: Incomplete Bug description: I use Nvidia driver 440. The sound became crazy on DisplayPort. Volume is not adjustable. I have either full volume or nothing. sound is crazy on my GTX1650 video card. If I use Nouveau driver I have no sound on my Display port. If I boot with 5.3.0-24 kernel sound is OK with Nivdia driver. But no sound with nouveau driver. Same things append on Focal and on Ubuntu 19.10. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3 Uname: Linux 5.4.0-9-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] est un dossier: '/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 440.44 Sun Dec 8 03:38:56 UTC 2019 GCC version: gcc version 9.2.1 20191130 (Ubuntu 9.2.1-21ubuntu1) ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: MATE Date: Fri Jan 10 00:26:20 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 440.44, 5.4.0-9-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation TU117 [GeForce GTX 1650] [10de:1f82] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd TU117 [GeForce GTX 1650] [1458:3fcb] InstallationDate: Installed on 2020-01-05 (4 days ago) InstallationMedia: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Alpha amd64 (20200104) MachineType: Micro-Star International Co., Ltd. MS-7B51 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-9-generic root=UUID=0b5d6829-5bb4-40e3-9fee-0fdec99e5f5a ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/21/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.50 dmi.board.asset.tag: Default string dmi.board.name: MPG Z390 GAMING PLUS (MS-7B51) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.50:bd02/21/2019:svnMicro-StarInternationalCo.,Ltd.:pnMS-7B51:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMPGZ390GAMINGPLUS(MS-7B51):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0: dmi.product.family: Default string dmi.product.name: MS-7B51 dmi.product.sku: Default string dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.100-4 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.4-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.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.1.0-1 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/1859096/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1860519] Re: Out of memory running crashkernel in ubuntu18.04.1. (Regression/qla2xxx/ubuntu18.04.1/BostonLC)(Documentation?)
I just added the requested section to the wiki:
https://wiki.ubuntu.com/ppc64el/Recommendations#Configuring_Dump_Capturing_Support_.28KDump.2FFADump.29
and closing this bug.
** No longer affects: linux (Ubuntu)
** Changed in: ubuntu-power-systems
Status: New => Fix Released
** Changed in: ubuntu-power-systems
Importance: Undecided => Medium
** Changed in: ubuntu-power-systems
Assignee: Canonical Kernel Team (canonical-kernel-team) => Ubuntu on IBM
Power Systems Bug Triage (ubuntu-power-triage)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1860519
Title:
Out of memory running crashkernel in ubuntu18.04.1.
(Regression/qla2xxx/ubuntu18.04.1/BostonLC)(Documentation?)
Status in The Ubuntu-power-systems project:
Fix Released
Bug description:
== Comment: #0 - Naresh Bannoth - 2018-06-06 01:49:02 ==
---Problem Description---
getting the following kernel panic message while trying to dump the crash
over local directory of ubuntu18.04.1.
"Kernel panic - not syncing: Out of memory and no killable
processes..."
This is a Regression BUG, as it worked fine in Ubuntu18.04 for local
dump.
configuration details are as follows,
root@ltciofvtr-bostonlc1:~# free -g
totalusedfree shared buff/cache
available
Mem:123 20 97 0 5
101
Swap: 1 0 1
root@ltciofvtr-bostonlc1:~# df -h
Filesystem Size Used Avail Use% Mounted on
udev 59G 0 59G 0% /dev
tmpfs13G 21M 13G 1% /run
/dev/sde2 5.5T 98G 5.1T 2% /
tmpfs62G 0 62G 0% /dev/shm
tmpfs 5.0M 0 5.0M 0% /run/lock
tmpfs62G 0 62G 0% /sys/fs/cgroup
tmpfs13G 0 13G 0% /run/user/0
tmpfs 128K 0 128K 0% /var/lib/lxd/shmounts
tmpfs 128K 0 128K 0% /var/lib/lxd/devlxd
root@ltciofvtr-bostonlc1:~#
root@ltciofvtr-bostonlc1:~# service kdump-tools restart
root@ltciofvtr-bostonlc1:~# service kdump-tools status
? kdump-tools.service - Kernel crash dump capture service
Loaded: loaded (/lib/systemd/system/kdump-tools.service; enabled; vendor
preset: enabled)
Active: active (exited) since Tue 2018-06-05 06:51:45 EDT; 6s ago
Process: 18478 ExecStop=/etc/init.d/kdump-tools stop (code=exited,
status=0/SUCCESS)
Process: 18519 ExecStart=/etc/init.d/kdump-tools start (code=exited,
status=0/SUCCESS)
Main PID: 18519 (code=exited, status=0/SUCCESS)
Jun 05 06:51:44 ltciofvtr-bostonlc1 systemd[1]: Starting Kernel crash dump
capture service...
Jun 05 06:51:44 ltciofvtr-bostonlc1 kdump-tools[18519]: Starting kdump-tools:
* Creating symlink /var/lib/kdump/vmlinuz
Jun 05 06:51:44 ltciofvtr-bostonlc1 kdump-tools[18519]: * Creating symlink
/var/lib/kdump/initrd.img
Jun 05 06:51:44 ltciofvtr-bostonlc1 kdump-tools[18519]: Modified
cmdline:root=UUID=6e1afd6a-a199-4bc5-a324-b65d5607d03b ro quiet splash
nr_cpus=1 systemd.unit=kdump-tools.service irqpoll noirqdistrib nousb
Jun 05 06:51:45 ltciofvtr-bostonlc1 kdump-tools[18519]: * loaded kdump kernel
Jun 05 06:51:45 ltciofvtr-bostonlc1 systemd[1]: Started Kernel crash dump
capture service.
root@ltciofvtr-bostonlc1:~#
root@ltciofvtr-bostonlc1:~#
root@ltciofvtr-bostonlc1:~#
root@ltciofvtr-bostonlc1:~#
root@ltciofvtr-bostonlc1:~# cat /proc/cmdline
root=UUID=6e1afd6a-a199-4bc5-a324-b65d5607d03b ro quiet splash
crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M@128M
root@ltciofvtr-bostonlc1:~#
root@ltciofvtr-bostonlc1:~# kdump-config show
DUMP_MODE:kdump
USE_KDUMP:1
KDUMP_SYSCTL: kernel.panic_on_oops=1
KDUMP_COREDIR:/var/crash
crashkernel addr:
/var/lib/kdump/vmlinuz: symbolic link to /boot/vmlinux-4.15.0-23-generic
kdump initrd:
/var/lib/kdump/initrd.img: symbolic link to
/var/lib/kdump/initrd.img-4.15.0-23-generic
current state:ready to kdump
kexec command:
/sbin/kexec -p
--command-line="root=UUID=6e1afd6a-a199-4bc5-a324-b65d5607d03b ro quiet splash
nr_cpus=1 systemd.unit=kdump-tools.service irqpoll noirqdistrib nousb"
--initrd=/var/lib/kdump/initrd.img /var/lib/kdump/vmlinuz
root@ltciofvtr-bostonlc1:~#
root@ltciofvtr-bostonlc1:~# cat /sys/kernel/kexec_crash_loaded
1
root@ltciofvtr-bostonlc1:~#
root@ltciofvtr-bostonlc1:~# cat /etc/default/kdump-tools | grep -i crash
KDUMP_COREDIR="/var/crash"
KDUMP_COREDIR="/var/crash"
# the crash dump. The syntax must be {HOSTNAME}:{MOUNTPOINT}
# (e.g. remote:/var/crash)
root@ltciofvtr-bostonlc1:~#
root@ltciofvtr-bostonlc1:~#
== Snippet of Error logs,
[ OK ] Reached target System Time Synchronized.
[ 32.167186] Out of memory:
[Kernel-packages] [Bug 1860119] Re: eoan/linux: 5.3.0-29.31 -proposed tracker
** 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 bugs-spammed: true packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Testing phase-changed: Monday, 20. January 2020 14:11 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - automated-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-hwe: bug 1859693 eoan/linux-raspi2: bug 1859692 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/1860119 Title: eoan/linux: 5.3.0-29.31 -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 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 bugs-spammed: true packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Testing phase-changed: Monday, 20. January 2020 14:11 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-hwe: bug 1859693 eoan/linux-raspi2: bug 1859692 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1860119/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1860519] Re: Out of memory running crashkernel in ubuntu18.04.1. (Regression/qla2xxx/ubuntu18.04.1/BostonLC)(Documentation?)
This is not a bug about the Ubuntu desktop guide. Please stop using
ubuntu-docs for bugs like this.
** No longer affects: ubuntu-docs (Ubuntu)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1860519
Title:
Out of memory running crashkernel in ubuntu18.04.1.
(Regression/qla2xxx/ubuntu18.04.1/BostonLC)(Documentation?)
Status in The Ubuntu-power-systems project:
New
Status in linux package in Ubuntu:
New
Bug description:
== Comment: #0 - Naresh Bannoth - 2018-06-06 01:49:02 ==
---Problem Description---
getting the following kernel panic message while trying to dump the crash
over local directory of ubuntu18.04.1.
"Kernel panic - not syncing: Out of memory and no killable
processes..."
This is a Regression BUG, as it worked fine in Ubuntu18.04 for local
dump.
configuration details are as follows,
root@ltciofvtr-bostonlc1:~# free -g
totalusedfree shared buff/cache
available
Mem:123 20 97 0 5
101
Swap: 1 0 1
root@ltciofvtr-bostonlc1:~# df -h
Filesystem Size Used Avail Use% Mounted on
udev 59G 0 59G 0% /dev
tmpfs13G 21M 13G 1% /run
/dev/sde2 5.5T 98G 5.1T 2% /
tmpfs62G 0 62G 0% /dev/shm
tmpfs 5.0M 0 5.0M 0% /run/lock
tmpfs62G 0 62G 0% /sys/fs/cgroup
tmpfs13G 0 13G 0% /run/user/0
tmpfs 128K 0 128K 0% /var/lib/lxd/shmounts
tmpfs 128K 0 128K 0% /var/lib/lxd/devlxd
root@ltciofvtr-bostonlc1:~#
root@ltciofvtr-bostonlc1:~# service kdump-tools restart
root@ltciofvtr-bostonlc1:~# service kdump-tools status
? kdump-tools.service - Kernel crash dump capture service
Loaded: loaded (/lib/systemd/system/kdump-tools.service; enabled; vendor
preset: enabled)
Active: active (exited) since Tue 2018-06-05 06:51:45 EDT; 6s ago
Process: 18478 ExecStop=/etc/init.d/kdump-tools stop (code=exited,
status=0/SUCCESS)
Process: 18519 ExecStart=/etc/init.d/kdump-tools start (code=exited,
status=0/SUCCESS)
Main PID: 18519 (code=exited, status=0/SUCCESS)
Jun 05 06:51:44 ltciofvtr-bostonlc1 systemd[1]: Starting Kernel crash dump
capture service...
Jun 05 06:51:44 ltciofvtr-bostonlc1 kdump-tools[18519]: Starting kdump-tools:
* Creating symlink /var/lib/kdump/vmlinuz
Jun 05 06:51:44 ltciofvtr-bostonlc1 kdump-tools[18519]: * Creating symlink
/var/lib/kdump/initrd.img
Jun 05 06:51:44 ltciofvtr-bostonlc1 kdump-tools[18519]: Modified
cmdline:root=UUID=6e1afd6a-a199-4bc5-a324-b65d5607d03b ro quiet splash
nr_cpus=1 systemd.unit=kdump-tools.service irqpoll noirqdistrib nousb
Jun 05 06:51:45 ltciofvtr-bostonlc1 kdump-tools[18519]: * loaded kdump kernel
Jun 05 06:51:45 ltciofvtr-bostonlc1 systemd[1]: Started Kernel crash dump
capture service.
root@ltciofvtr-bostonlc1:~#
root@ltciofvtr-bostonlc1:~#
root@ltciofvtr-bostonlc1:~#
root@ltciofvtr-bostonlc1:~#
root@ltciofvtr-bostonlc1:~# cat /proc/cmdline
root=UUID=6e1afd6a-a199-4bc5-a324-b65d5607d03b ro quiet splash
crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M@128M
root@ltciofvtr-bostonlc1:~#
root@ltciofvtr-bostonlc1:~# kdump-config show
DUMP_MODE:kdump
USE_KDUMP:1
KDUMP_SYSCTL: kernel.panic_on_oops=1
KDUMP_COREDIR:/var/crash
crashkernel addr:
/var/lib/kdump/vmlinuz: symbolic link to /boot/vmlinux-4.15.0-23-generic
kdump initrd:
/var/lib/kdump/initrd.img: symbolic link to
/var/lib/kdump/initrd.img-4.15.0-23-generic
current state:ready to kdump
kexec command:
/sbin/kexec -p
--command-line="root=UUID=6e1afd6a-a199-4bc5-a324-b65d5607d03b ro quiet splash
nr_cpus=1 systemd.unit=kdump-tools.service irqpoll noirqdistrib nousb"
--initrd=/var/lib/kdump/initrd.img /var/lib/kdump/vmlinuz
root@ltciofvtr-bostonlc1:~#
root@ltciofvtr-bostonlc1:~# cat /sys/kernel/kexec_crash_loaded
1
root@ltciofvtr-bostonlc1:~#
root@ltciofvtr-bostonlc1:~# cat /etc/default/kdump-tools | grep -i crash
KDUMP_COREDIR="/var/crash"
KDUMP_COREDIR="/var/crash"
# the crash dump. The syntax must be {HOSTNAME}:{MOUNTPOINT}
# (e.g. remote:/var/crash)
root@ltciofvtr-bostonlc1:~#
root@ltciofvtr-bostonlc1:~#
== Snippet of Error logs,
[ OK ] Reached target System Time Synchronized.
[ 32.167186] Out of memory: Kill process 2958 (systemd-udevd) score 1 or
sacrifice child
[ 32.167270] Killed process 2958 (systemd-udevd) total-vm:23616kB,
anon-rss:0kB, file-rss:1856kB, shmem-rss:0kB
[ 32.180509] Out of memory: Kill process 432 (systemd-network) score 1 or
sacrifice child
[ 32.180565] Killed process 432 (systemd-network) total-vm:19520kB,
[Kernel-packages] [Bug 1851162] Re: nvidia-drivers-390 fail to build with kernel 5.3
Adding the patch from https://gist.github.com/wheresvic/1e526c3cd937414661ce6be7c5e4667d worked. I managed to build and install the driver. Patch https://gist.github.com/wheresvic/a118420b9592088ea23c7414e7f2d676 resulted in failed build. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1851162 Title: nvidia-drivers-390 fail to build with kernel 5.3 Status in linux package in Ubuntu: Confirmed Status in linux-hwe package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-390 package in Ubuntu: Confirmed Status in linux source package in Bionic: Confirmed Status in linux-hwe source package in Bionic: Confirmed Status in nvidia-graphics-drivers-390 source package in Bionic: Fix Committed Bug description: nvidia-graphics-drivers-390 fails to build against linux 5.3. SRU Request: [Test Case] 1) Enable the -proposed repository, and install the new 390 NVIDIA driver (nvidia-graphics-drivers-390_390.116-0ubuntu0.18.04.2). 2) Check that the kernel module can be built against the new kernel. 3) Restart your computer, and see if everything works correctly when accessing the desktop. [Regression Potential] Low. The update only fixes build issues with Linux versions 5.3. __ With linux-image-5.0.0-23 I had no problems. Following an update linux-image-5.3.0-19 was installed, the DKMS build failed, and the system became unusable. Removing 5.3.0 brings the system back. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: nvidia-driver-390 390.116-0ubuntu0.18.04.1 ProcVersionSignature: Ubuntu 5.0.0-23.24~18.04.1-generic 5.0.15 Uname: Linux 5.0.0-23-generic x86_64 NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.8 Architecture: amd64 CurrentDesktop: MATE Date: Sun Nov 3 19:55:57 2019 InstallationDate: Installed on 2019-06-09 (147 days ago) InstallationMedia: Ubuntu-MATE 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) SourcePackage: nvidia-graphics-drivers-390 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1851162/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1860535] Re: [UBUNTU] - Disable Thin Provisioning to prevent data loss
** Also affects: linux (Ubuntu Eoan) 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/1860535 Title: [UBUNTU] - Disable Thin Provisioning to prevent data loss Status in Ubuntu on IBM z Systems: New Status in linux package in Ubuntu: New Status in linux source package in Eoan: New Bug description: Discription will provided soon.. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1860535/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1860231] Re: 5.4.0-11 crash on cryptsetup open
With additional data it is basically a bug in either the mount syscall, the generic_make_request_checks, or dm.c. Basically device-mapper is set up in two stages, the initial device creation and the table load. Somehwere around v4.1 things were changed to defer setting the make- request function of the device (queue) to when the mapping table gets loaded. One can create such a intermediate setup using "dmsetup create -n ". Then a "mount /dev/dm-?" triggers the bug. Since generic_make_request_checks has a check for device->queue == NULL but not for device->queue->make_request_fn == NULL. Interestingly neither blkid nor dd would trigger this. Likely because they first check the size which is still 0 at that time. Only mount seems to go off and try to read superblock info regardless. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1860231 Title: 5.4.0-11 crash on cryptsetup open Status in linux package in Ubuntu: Incomplete Bug description: An attempt to run cryptsetup open on a newly created LUKS partition on Ubuntu Core 20 causes a kernel crash. This happens in 100% of the attempts on the snapd Core 20 installation test, but on an image created to reproduce this bug it happens only when certain parameters are passed to cryptsetup. Both images are built similarly so the reason for this discrepancy is unknown. The kernel was installed from pc-kernel_374.snap. Linux version 5.4.0-11-generic (buildd@lgw01-amd64-021) (gcc version 9.2.1 20200104 (Ubuntu 9.2.1-22ubuntu2)) #14-Ubuntu SMP Thu Jan 9 16:14:26 UTC 2020 Version signature: Ubuntu 5.4.0-11.14-generic 5.4.8 How to reproduce the crash in 3 "easy" steps: 1. Build a Core 20 image using the attached model file: 1.1. Install the ubuntu-image from latest/edge $ sudo snap install --channel latest/edge ubuntu-image 1.2. Build the image $ sudo ubuntu-image --image-size=4G ubuntu-core-20-amd64.model 2. Boot the image in kvm 2.1. Install ovmf version 0~20190606.20d2e5a1-2ubuntu1 or newer (the stock ovmf from bionic may not work) 2.2. Boot the image $ sudo kvm -snapshot -m 2048 -smp 4 \ -netdev user,id=mynet0,hostfwd=tcp::8022-:22,hostfwd=tcp::8090-:80 \ -device virtio-net-pci,netdev=mynet0 \ -drive file=pc.img,if=virtio \ -bios /usr/share/OVMF/OVMF_CODE.ms.fd 2.3. In the grub menu, edit the default option to include parameter "systemd.debug-shell=1" in the kernel command line 2.4. Boot the kernel 3. Crash the kernel 3.1. When the system boots to the "Press enter to configure" message, press ALT-F9 to enter the debug shell. 3.2. The system should have two partitions in /dev/vda. Create a third one with fdisk. 3.3. Create a LUKS encrypted partition: # echo 123|cryptsetup luksFormat -q --type luks2 --key-file - --pbkdf argon2i --iter-time 1 /dev/vda3 (the system will complain about a missing locking directory, just ignore it.) 3.4. Open the encrypted device: # echo 123|cryptsetup open --key-file - /dev/vda name The Core 20 images contain the following udev rule which causes the new block device to be mounted automatically. This mount is what triggers the BUG: ACTION=="add", SUBSYSTEM=="block", KERNEL!="loop*", KERNEL!="ram*" \ RUN+="/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/%k" 3.5. Read the crash message The attached screenshots show these steps being executed. A few notes: - The backtrace seems very similar to the one reported in bug #1835279, however that problem was possibly caused by a race between partition creation and LUKS formatting. This time it doesn't seem to be the case, delays between commands don't help us here. - In the test case above using large values of KDF iter-time may prevent the crash. I successfully opened the device in kernel 5.4.0-9 with --iter-time larger than 100, but 5.4.0-11 seems to require values closer to 1000. Regardless of the --iter-time value used, the crash always happen when running the test in a spread-driven automated environment (same kernel with image built in the same way, some other variable seems to be disturbing the system). - All necessary modules are loaded before the LUKS partition creation (i.e. it doesn't seem to be caused by a race between dm-crypt loading and cryptsetup luksFormat for example). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860231/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1859793] Re: bionic/linux-snapdragon: 4.15.0-1071.78 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: '1860123' packages: main: linux-snapdragon meta: linux-meta-snapdragon phase: Testing phase-changed: Friday, 17. January 2020 10:36 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - certification-testing: Ongoing -- testing in progress + certification-testing: Stalled -- testing FAILED security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-snapdragon/dragonboard-kernel: bug 1859791 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/1859793 Title: bionic/linux-snapdragon: 4.15.0-1071.78 -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: Incomplete Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow 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: '1860123' packages: main: linux-snapdragon meta: linux-meta-snapdragon phase: Testing phase-changed: Friday, 17. January 2020 10:36 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: certification-testing: Stalled -- testing FAILED security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-snapdragon/dragonboard-kernel: bug 1859791 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1859793/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1860531] Re: IPL on z15 always performed regardless of the secure-boot related settings
Changing affected package (from kernel to) s390-tools, according to comment #2 and the mentioned patch there. ** Package changed: linux (Ubuntu) => s390-tools (Ubuntu) ** Changed in: ubuntu-z-systems Status: New => Triaged ** Changed in: ubuntu-z-systems Assignee: (unassigned) => Canonical Foundations Team (canonical-foundations) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1860531 Title: IPL on z15 always performed regardless of the secure-boot related settings Status in Ubuntu on IBM z Systems: Triaged Status in s390-tools package in Ubuntu: New Bug description: Description will follow To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1860531/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1859793] Re: bionic/linux-snapdragon: 4.15.0-1071.78 -proposed tracker
Setting 'certification-testing' to 'Incomplete' per Gavin's report. ** Changed in: kernel-sru-workflow/certification-testing Status: In Progress => Incomplete -- 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/1859793 Title: bionic/linux-snapdragon: 4.15.0-1071.78 -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: Incomplete Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow 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: '1860123' packages: main: linux-snapdragon meta: linux-meta-snapdragon phase: Testing phase-changed: Friday, 17. January 2020 10:36 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: certification-testing: Stalled -- testing FAILED security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-snapdragon/dragonboard-kernel: bug 1859791 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1859793/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1859718] Re: xenial/linux: 4.4.0-173.203 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true bugs-spammed: true packages: main: linux meta: linux-meta signed: linux-signed phase: Testing phase-changed: Thursday, 16. January 2020 04:02 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: + trusty/linux-aws: bug 1858591 trusty/linux-lts-xenial: bug 1859717 xenial/linux-fips: bug 1858589 xenial/linux-kvm: bug 1858584 xenial/linux-raspi2: bug 1858586 xenial/linux-snapdragon: bug 1858588 xenial/linux/caracalla-kernel: bug 1859714 xenial/linux/pc-kernel: bug 1859715 xenial/linux/stlouis-kernel: bug 1859716 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/1859718 Title: xenial/linux: 4.4.0-173.203 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Fix Released Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: 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 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 bugs-spammed: true packages: main: linux meta: linux-meta signed: linux-signed phase: Testing phase-changed: Thursday, 16. January 2020 04:02 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: trusty/linux-aws: bug 1858591 trusty/linux-lts-xenial: bug 1859717 xenial/linux-fips: bug 1858589 xenial/linux-kvm: bug 1858584 xenial/linux-raspi2: bug 1858586 xenial/linux-snapdragon: bug 1858588 xenial/linux/caracalla-kernel: bug 1859714 xenial/linux/pc-kernel: bug 1859715 xenial/linux/stlouis-kernel: bug 1859716 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1859718/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1860527] Re: sysfs files under /sys/devices/system/cpu/cpufreq/ disappear after upgrading kernel
** Also affects: linux-snapdragon (Ubuntu Bionic) Importance: Undecided Status: New -- 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/1860527 Title: sysfs files under /sys/devices/system/cpu/cpufreq/ disappear after upgrading kernel Status in linux-snapdragon package in Ubuntu: New Status in linux-snapdragon source package in Bionic: New Bug description: sysfs files under /sys/devices/system/cpu/cpufreq/ disappear after upgrading kernel. Kernel: Linux dragon410c 4.15.0-1071-snapdragon #78-Ubuntu SMP Thu Jan 16 22:30:28 UTC 2020 aarch64 aarch64 aarch64 GNU/Linux Steps: 1. Flash following image and boot the DUT https://people.canonical.com/~ppisati/ubuntu_embedded/ubuntu-embedded-18.04-dragon410c.img.xz 2. Enable proposed repository 3. Upgrade kernel to 4.15.0-1071 4. Reboot 5. Check file in /sys/devices/system/cpu/cpufreq/ Expected result: Files are still there after upgrading kernel. Actual result: Files under /sys/devices/system/cpu/cpufreq/ disappear after upgrading kernel. Hardware infomation: Dragonboard 410c ip address: 10.101.51.17 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-snapdragon/+bug/1860527/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1860535] Re: [UBUNTU] - Disable Thin Provisioning to prevent data loss
** Changed in: ubuntu-z-systems Importance: Undecided => High -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1860535 Title: [UBUNTU] - Disable Thin Provisioning to prevent data loss Status in Ubuntu on IBM z Systems: New Status in linux package in Ubuntu: New Bug description: Discription will provided soon.. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1860535/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1860535] Re: [UBUNTU] - Disable Thin Provisioning to prevent data loss
** Also affects: ubuntu-z-systems 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/1860535 Title: [UBUNTU] - Disable Thin Provisioning to prevent data loss Status in Ubuntu on IBM z Systems: New Status in linux package in Ubuntu: New Bug description: Discription will provided soon.. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1860535/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1850130] Re: zpools fail to import after reboot on fresh install of eoan
Tried adding "After=multipathd.service" to zfs-import-cache.service. Do not have a zfs-import-pool.service file. Still no mount after reboot. -- 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/1850130 Title: zpools fail to import after reboot on fresh install of eoan Status in zfs-linux package in Ubuntu: Confirmed Bug description: Fresh installation of stock Ubuntu 19.10 Eoan with experimental root on ZFS. System has existing zpools with data. Installation is uneventful. First boot with no problems. Updates applied. No other changes from fresh installation. Reboot. External pool 'tank' imports with no errors. Reboot. External pool has failed to import on boot. In contrast bpool and rpool are ok. Manually re-import 'tank' with no issues. I can see both 'tank' and its path in /dev/disk/by-id/ in /etc/zfs/zpool.cache. Reboot. 'tank' has failed to import on boot. It is also missing from /etc/zfs/zpool.cache. Is it possible that the cache is being re- generated on reboot, and the newly imported pools are getting erased from it? I can re-import the pools again manually with no issues, but they don't persist between re-boots. Installing normally on ext4 this is not an issue and data pools import automatically on boot with no further effort. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1850130/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1851162] Re: nvidia-drivers-390 fail to build with kernel 5.3
Hello Ken, or anyone else affected, Accepted nvidia-graphics-drivers-390 into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source /nvidia-graphics-drivers-390/390.116-0ubuntu0.18.04.3 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Tags removed: verification-failed-bionic ** Tags added: verification-needed-bionic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1851162 Title: nvidia-drivers-390 fail to build with kernel 5.3 Status in linux package in Ubuntu: Confirmed Status in linux-hwe package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-390 package in Ubuntu: Confirmed Status in linux source package in Bionic: Confirmed Status in linux-hwe source package in Bionic: Confirmed Status in nvidia-graphics-drivers-390 source package in Bionic: Fix Committed Bug description: nvidia-graphics-drivers-390 fails to build against linux 5.3. SRU Request: [Test Case] 1) Enable the -proposed repository, and install the new 390 NVIDIA driver (nvidia-graphics-drivers-390_390.116-0ubuntu0.18.04.2). 2) Check that the kernel module can be built against the new kernel. 3) Restart your computer, and see if everything works correctly when accessing the desktop. [Regression Potential] Low. The update only fixes build issues with Linux versions 5.3. __ With linux-image-5.0.0-23 I had no problems. Following an update linux-image-5.3.0-19 was installed, the DKMS build failed, and the system became unusable. Removing 5.3.0 brings the system back. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: nvidia-driver-390 390.116-0ubuntu0.18.04.1 ProcVersionSignature: Ubuntu 5.0.0-23.24~18.04.1-generic 5.0.15 Uname: Linux 5.0.0-23-generic x86_64 NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.8 Architecture: amd64 CurrentDesktop: MATE Date: Sun Nov 3 19:55:57 2019 InstallationDate: Installed on 2019-06-09 (147 days ago) InstallationMedia: Ubuntu-MATE 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) SourcePackage: nvidia-graphics-drivers-390 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1851162/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1859799] Re: xenial/linux-deeplens: 4.15.0-1015.15 -proposed tracker
** Changed in: kernel-sru-workflow/verification-testing Status: Confirmed => In Progress ** 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: '1860122' packages: main: linux-deeplens meta: linux-meta-deeplens - phase: Ready for Testing - phase-changed: Tuesday, 21. January 2020 15:37 UTC + phase: Testing + phase-changed: Wednesday, 22. January 2020 10:42 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: verification-testing: Ongoing -- testing in progress variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1859799 Title: xenial/linux-deeplens: 4.15.0-1015.15 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow certification-testing series: Fix Released Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Invalid Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: '1860122' packages: main: linux-deeplens meta: linux-meta-deeplens phase: Testing phase-changed: Wednesday, 22. January 2020 10:42 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: verification-testing: Ongoing -- testing in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1859799/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1860531] Comment bridged from LTC Bugzilla
--- Comment From heinz-werner_se...@de.ibm.com 2020-01-22 05:29 EDT--- addl. description: "Operating system messages" output Test on a z15 LPAR: Checking the combinations of the /etc/zipl.conf "secure" keyword and the HMC "Enable Secure Boot for Linux" option on the HMC SCSI load panel. Result: the system always performs a successful IPL regardless of the settings of the zipl.conf "secure" keyword and and the HMC "Enable Secure Boot for Linux" option. Problem: No IPL should be performed for the combination of "secure=0" in /etc/zipl.conf and the selection of "Enable Secure Boot for Linux" option in the HMC SCSI load panel. Scenario root@t35lp36:~# cat /etc/os-release NAME="Ubuntu" VERSION="20.04 LTS (Focal Fossa)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu Focal Fossa (development branch)" VERSION_ID="20.04" HOME_URL="https://www.ubuntu.com/; SUPPORT_URL="https://help.ubuntu.com/; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy; VERSION_CODENAME=focal UBUNTU_CODENAME=focal root@t35lp36:~# uname -a Linux t35lp36 5.4.0-9-generic #12-Ubuntu SMP Mon Dec 16 22:31:38 UTC 2019 s390x s390x s390x GNU/Linux Setting secure=0 in /etc/zipl.conf root@t35lp36:~# cat /etc/zipl.conf [defaultboot] defaultmenu = menu secure=0 :menu target = /boot 1 = ubuntu 2 = old default = 1 prompt = 1 timeout = 10 [ubuntu] target = /boot image = /boot/vmlinuz ramdisk = /boot/initrd.img parameters = root=UUID=dc6b7633-49f0-4095-8c35-678cbc212ca5 crashkernel=196M [old] target = /boot image = /boot/vmlinuz.old ramdisk = /boot/initrd.img.old parameters = root=UUID=dc6b7633-49f0-4095-8c35-678cbc212ca5 crashkernel=196M optional = 1 root@t35lp36:~# zipl -V Using config file '/etc/zipl.conf' Run /lib/s390-tools/zipl_helper.device-mapper /boot Target device information Device..: fd:00 *) Partition...: fd:01 Device name.: dm-0 Device driver name..: device-mapper Type: disk partition Disk layout.: SCSI disk layout *) Geometry - start: 2048 *) File system block size..: 4096 Physical block size.: 512 *) Device size in physical blocks..: 37746688 *) Data provided by script. Building bootmap in '/boot' Building menu 'menu' Adding #1: IPL section 'ubuntu' (default) initial ramdisk...: /boot/initrd.img signature for.: /lib/s390-tools/stage3.bin kernel image..: /boot/vmlinuz signature for.: /boot/vmlinuz kernel parmline...: 'root=UUID=dc6b7633-49f0-4095-8c35-678cbc212ca5 crashkernel=196M' component address: heap area...: 0x2000-0x5fff stack area..: 0xf000-0x internal loader.: 0xa000-0xdfff parameters..: 0x9000-0x91ff kernel image: 0x0001-0x007d7fff parmline: 0x007d9000-0x007d91ff initial ramdisk.: 0x007e-0x01a73bff Adding #2: IPL section 'old' initial ramdisk...: /boot/initrd.img.old signature for.: /lib/s390-tools/stage3.bin kernel image..: /boot/vmlinuz.old signature for.: /boot/vmlinuz.old kernel parmline...: 'root=UUID=dc6b7633-49f0-4095-8c35-678cbc212ca5 crashkernel=196M' component address: heap area...: 0x2000-0x5fff stack area..: 0xf000-0x internal loader.: 0xa000-0xdfff parameters..: 0x9000-0x91ff kernel image: 0x0001-0x007d7fff parmline: 0x007d9000-0x007d91ff initial ramdisk.: 0x007e-0x01a73bff Preparing boot device: dm-0. Detected SCSI PCBIOS disk layout. Writing SCSI master boot record. Syncing disks... Done. root@t35lp36:~# Then the system was shut down and a new IPL was triggered from the HMC SCSI load panel. The system IPL'd successfully. Excerpt from the "Operating System Messages" output: Preparing system. Starting system. System version 8. Watchdog enabled. Running 'ZBootLoader' version '1.0.0' level 'D41C.D41C_0013'. ZBootLoader 2.0.0. OK Success [0.317598] Linux version 5.4.0-9-generic (buildd@bos02-s390x-011) (gcc versi on 9.2.1 20191130 (Ubuntu 9.2.1-21ubuntu1)) #12-Ubuntu SMP Mon Dec 16 22:31:38 U TC 2019 (Ubuntu 5.4.0-9.12-generic 5.4.3) [0.317600] setup.6bac7a: Linux is running natively in 64-bit mode [0.317601] setup.433296: Linux is running with Secure-IPL enabled [0.317602] setup.6482e5: The IPL report contains the following components: [0.317603] setup.4da44b: 2000 - 6000 (not signed) [0.317605] setup.4da44b: f000 - 0001 (not signed) [0.317606] setup.4da44b: a000 - e000 (signed, verified) [0.317607] setup.4da44b: 9000 - 9200 (not signed) [0.317608] setup.4da44b: 0001 - 007d8000 (signed, verified) [0.317609] setup.4da44b: 007d9000 - 007d9200 (not signed) [0.317610] setup.4da44b: 007e -
