[Kernel-packages] [Bug 1892288] Re: Comet Lake PCH-H RAID not support on Ubuntu20.04
In BIOS, Change to RAID/Intel RST and create a volume.
Boot with 5.6.0.1028, the raid device can be found in /dev
#sudo fdisk -l
/dev/mapper/lsw_gdejahcjf_Volume1p1 2048 2000420863 2000418816 953.9G 83 Linu
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.6 in Ubuntu.
https://bugs.launchpad.net/bugs/1892288
Title:
Comet Lake PCH-H RAID not support on Ubuntu20.04
Status in HWE Next:
New
Status in OEM Priority Project:
New
Status in linux package in Ubuntu:
Invalid
Status in linux-oem-5.6 package in Ubuntu:
Invalid
Status in linux source package in Focal:
In Progress
Status in linux-oem-5.6 source package in Focal:
In Progress
Bug description:
[Impact]
Add Intel Comet Lake PCH-H PCI ID to the list of supported controllers.
[Fix]
Add Intel Comet Lake PCH-H PCI ID to the list of supported controllers.
[test]
[Regression Potential]
Low. Just add a PCI id for the sata/ahci raid.
== Original ==
As Ubuntu 20.04 AHCI driver doesn’t include comet lake PCH-H RAID support
{ PCI_VDEVICE(INTEL, 0x06d6), board_ahci }, /* Comet Lake PCH-H RAID */
If Thinkstation P340 configured as RAID mode, It can not find any RAID volume
disk.
please update such support. Thanks.
Regards,
Jiqi.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1892288/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1896565] [NEW] Kexec doesn't properly reintialize GPU on Dell XPS13 9343
Public bug reported: I've symlinked /lib/systemd/system/reboot.target to /lib/systemd/system/kexec.target and everything works fine except my framebuffer screen which on very initial screen with full disk encryption password starts to floating horizontally. I'm able to use it, after blindly typing password everything works fine, but I'm worried that something not initialized at this stage may break hardware, and it just doesn't look good. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: kexec-tools 1:2.0.16-1ubuntu1.1 ProcVersionSignature: Ubuntu 4.15.0-118.119-generic 4.15.18 Uname: Linux 4.15.0-118-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7.17 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Sep 22 06:30:13 2020 InstallationDate: Installed on 2015-05-08 (1963 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/bash SourcePackage: kexec-tools UpgradeStatus: Upgraded to bionic on 2018-08-26 (757 days ago) ** Affects: kexec-tools (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic third-party-packages -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to kexec-tools in Ubuntu. https://bugs.launchpad.net/bugs/1896565 Title: Kexec doesn't properly reintialize GPU on Dell XPS13 9343 Status in kexec-tools package in Ubuntu: New Bug description: I've symlinked /lib/systemd/system/reboot.target to /lib/systemd/system/kexec.target and everything works fine except my framebuffer screen which on very initial screen with full disk encryption password starts to floating horizontally. I'm able to use it, after blindly typing password everything works fine, but I'm worried that something not initialized at this stage may break hardware, and it just doesn't look good. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: kexec-tools 1:2.0.16-1ubuntu1.1 ProcVersionSignature: Ubuntu 4.15.0-118.119-generic 4.15.18 Uname: Linux 4.15.0-118-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7.17 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Sep 22 06:30:13 2020 InstallationDate: Installed on 2015-05-08 (1963 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/bash SourcePackage: kexec-tools UpgradeStatus: Upgraded to bionic on 2018-08-26 (757 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kexec-tools/+bug/1896565/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1125452] Re: [Lenovo T530]: Volume Mute key LED is not responding correctly
This is working fine in Ubuntu 20.10
** Changed in: linux (Ubuntu)
Status: Incomplete => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1125452
Title:
[Lenovo T530]: Volume Mute key LED is not responding correctly
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Precise:
Confirmed
Status in linux source package in Quantal:
Won't Fix
Status in linux source package in Raring:
Won't Fix
Bug description:
Problem description:
When attempting a hardware mute the volume mute action is applied
correctly and the volume applet correctly displays that the audio
output is muted. However, the mute key's LED backlight's
responsiveness is flaky at best. Pressing the mute key repeatedly may
or may not result in an mute key LED change. This can quickly get out
of sync where it's possible for the mute key LED to be lit yet the
volume is not actually muted.
Again mute action does actually respond correctly via keypress:
Simple mixer control 'Master',0
Capabilities: pvolume pvolume-joined pswitch pswitch-joined penum
Playback channels: Mono
Limits: Playback 0 - 87
Mono: Playback 63 [72%] [-18.00dB] [on]
Simple mixer control 'Master',0
Capabilities: pvolume pvolume-joined pswitch pswitch-joined penum
Playback channels: Mono
Limits: Playback 0 - 87
Mono: Playback 63 [72%] [-18.00dB] [off]
Software mute does not change status of LED.
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: linux-image-3.2.0-37-generic 3.2.0-37.58
ProcVersionSignature: Ubuntu 3.2.0-37.58-generic 3.2.35
Uname: Linux 3.2.0-37-generic x86_64
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
ApportVersion: 2.0.1-0ubuntu17.1
Architecture: amd64
ArecordDevices:
List of CAPTURE Hardware Devices
card 0: PCH [HDA Intel PCH], device 0: ALC269VC Analog [ALC269VC Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: ubuntu 1621 F pulseaudio
Card0.Amixer.info:
Card hw:0 'PCH'/'HDA Intel PCH at 0xf253 irq 46'
Mixer name : 'Intel PantherPoint HDMI'
Components : 'HDA:10ec0269,17aa21f6,00100203
HDA:80862806,80860101,0010'
Controls : 41
Simple ctrls : 15
Card29.Amixer.info:
Card hw:29 'ThinkPadEC'/'ThinkPad Console Audio Control at EC reg 0x30, fw
unknown'
Mixer name : 'ThinkPad EC (unknown)'
Components : ''
Controls : 1
Simple ctrls : 1
Card29.Amixer.values:
Simple mixer control 'Console',0
Capabilities: pswitch pswitch-joined penum
Playback channels: Mono
Mono: Playback [on]
Date: Thu Feb 14 13:33:49 2013
HibernationDevice: RESUME=UUID=33af243d-8694-4458-a1eb-5c94d7303d8e
InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64
(20120823.1)
MachineType: LENOVO 235923U
MarkForUpload: True
ProcEnviron:
TERM=xterm
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-37-generic
root=UUID=212db818-8dcd-4bbd-94a9-0a9ca8d086a3 ro quiet splash initcall_debug
vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-3.2.0-37-generic N/A
linux-backports-modules-3.2.0-37-generic N/A
linux-firmware1.79.1
SourcePackage: linux
StagingDrivers: mei
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/29/2012
dmi.bios.vendor: LENOVO
dmi.bios.version: G4ET37WW (1.12 )
dmi.board.asset.tag: Not Available
dmi.board.name: 235923U
dmi.board.vendor: LENOVO
dmi.board.version: Not Available
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias:
dmi:bvnLENOVO:bvrG4ET37WW(1.12):bd05/29/2012:svnLENOVO:pn235923U:pvrThinkPadT530:rvnLENOVO:rn235923U:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 235923U
dmi.product.version: ThinkPad T530
dmi.sys.vendor: LENOVO
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1125452/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1892288] Re: Comet Lake PCH-H RAID not support on Ubuntu20.04
** Changed in: linux-oem-5.6 (Ubuntu Focal)
Status: Fix Committed => In Progress
** Changed in: linux (Ubuntu Focal)
Status: Fix Committed => In Progress
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.6 in Ubuntu.
https://bugs.launchpad.net/bugs/1892288
Title:
Comet Lake PCH-H RAID not support on Ubuntu20.04
Status in HWE Next:
New
Status in OEM Priority Project:
New
Status in linux package in Ubuntu:
Invalid
Status in linux-oem-5.6 package in Ubuntu:
Invalid
Status in linux source package in Focal:
In Progress
Status in linux-oem-5.6 source package in Focal:
In Progress
Bug description:
[Impact]
Add Intel Comet Lake PCH-H PCI ID to the list of supported controllers.
[Fix]
Add Intel Comet Lake PCH-H PCI ID to the list of supported controllers.
[test]
[Regression Potential]
Low. Just add a PCI id for the sata/ahci raid.
== Original ==
As Ubuntu 20.04 AHCI driver doesn’t include comet lake PCH-H RAID support
{ PCI_VDEVICE(INTEL, 0x06d6), board_ahci }, /* Comet Lake PCH-H RAID */
If Thinkstation P340 configured as RAID mode, It can not find any RAID volume
disk.
please update such support. Thanks.
Regards,
Jiqi.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1892288/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1894591] Re: clock: overriding the clocksource should select the requested clocksource
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- xenial' to 'verification-done-xenial'. If the problem still exists, change the tag 'verification-needed-xenial' to 'verification-failed- xenial'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-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/1894591 Title: clock: overriding the clocksource should select the requested clocksource Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Committed Bug description: BugLink: https://bugs.launchpad.net/bugs/1894591 [Impact] The default clocksource for a KVM VM is kvm-clock, and I happen to need tsc. $ cat /sys/devices/system/clocksource/clocksource0/current_clocksource kvm-clock If I edit /etc/default/grub and append "clocksource=tsc" to GRUB_CMDLINE_LINUX_DEFAULT and reboot, I find the clocksource is still kvm-clock. $ cat /sys/devices/system/clocksource/clocksource0/current_clocksource kvm-clock I can work around this by telling the kernel that the tsc clocksource is reliable, before the watchdog has a chance to see for itself that it is reliable: GRUB_CMDLINE_LINUX_DEFAULT="clocksource=tsc tsc=reliable" $ cat /sys/devices/system/clocksource/clocksource0/current_clocksource tsc If I override the clocksource, the kernel should respect my wishes and I should receive the requested clocksource. [Fix] The fix landed in Linux 4.9 in the below commit: commit 36374583f9084cdab4b5dcf5521a3ce55bebb9fa Author: Kyle Walker Date: Sat Aug 6 12:07:30 2016 -0400 Subject: clocksource: Defer override invalidation unless clock is unstable Link: https://github.com/torvalds/linux/commit/36374583f9084cdab4b5dcf5521a3ce55bebb9fa The commit ensures the override doesn't get cleared before the watchdog has had an opportunity to check if the clocksource is stable or not. However, if the clocksource is known to be unstable at this point in time, it will clear the override and return to the default. This is a clean cherry-pick to the Xenial 4.4 kernel. [Testcase] Start up a KVM VM, possibly enable invtsc on the QEMU command line. The default clocksource will be kvm-clock: $ cat /sys/devices/system/clocksource/clocksource0/current_clocksource kvm-clock If you set the kernel command line to: GRUB_CMDLINE_LINUX_DEFAULT="clocksource=tsc" If you reboot, you will see the incorrect option of kvm-clock: $ cat /sys/devices/system/clocksource/clocksource0/current_clocksource kvm-clock There is a test kernel available in the below ppa, with the commit applied: https://launchpad.net/~mruffell/+archive/ubuntu/sf291501-test If you install the test kernel, and leave the kernel command line as: GRUB_CMDLINE_LINUX_DEFAULT="clocksource=tsc" You will get the requested clocksource: $ cat /sys/devices/system/clocksource/clocksource0/current_clocksource tsc You will also get the following in dmesg: $ dmesg | grep defer [1.002599] clocksource: Override clocksource tsc is not currently HRT compatible - deferring [Regression Potential] This commit changes how the kernel treats clocksource overrides. If any users have an override set, but the kernel is clearing the override and returning to the default, when they install a patched kernel, they will change over to their requested override, which may come as a surprise. If there is a regression, it will only affect systems who have clocksource overrides in place, and in the worst case, will revert the system to its default clocksource if the selected clocksource override is found to be unstable. The commit is well tested, and should not cause any regressions. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1894591/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1892546] Re: Novalink (mkvterm command failure)
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- xenial' to 'verification-done-xenial'. If the problem still exists, change the tag 'verification-needed-xenial' to 'verification-failed- xenial'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-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/1892546 Title: Novalink (mkvterm command failure) Status in The Ubuntu-power-systems project: Fix Committed Status in linux package in Ubuntu: In Progress Status in linux source package in Xenial: Fix Committed Status in linux source package in Bionic: Fix Committed Status in linux source package in Focal: Fix Committed Status in linux source package in Groovy: In Progress Bug description: SRU Justification: [Impact] * drmgr command is failing while trying to open console for IBMi on PowerVM LPAR [Fix] * 63ffcbdad738 "tty: hvcs: Don't NULL tty->driver_data until hvcs_cleanup()" [Test Case] * Create a VM from PowerVC on a Novalink managed host. * Unmanage and manage the VM, this problem gets reproduced. * grep the logs for "drmgr" [Regression Potential] The regression can be considered as very low, since: * limited to the IBM Hypervisor Virtual Console Server. * patched kernel where shared and successfully tested by IBM. * the worse case, if the cleanup is broken a new opened connection might break. [Other] * The patch got upstream accepted. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1892546/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1889446] Re: DELL LATITUDE 5491 touchscreen doesn't work
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- xenial' to 'verification-done-xenial'. If the problem still exists, change the tag 'verification-needed-xenial' to 'verification-failed- xenial'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-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/1889446 Title: DELL LATITUDE 5491 touchscreen doesn't work Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Fix Committed Status in linux source package in Bionic: Fix Committed Status in linux source package in Focal: Fix Committed Bug description: I will really appreciate any help like said in summary my touchscreen doesnt work on my dell lattitude 5491 with a I5-8400H cpu. Any idea ? ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-42-generic 5.4.0-42.46 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ying 1977 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Jul 29 18:45:20 2020 InstallationDate: Installed on 2020-07-29 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Dell Inc. Latitude 5491 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-42-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-42-generic N/A linux-backports-modules-5.4.0-42-generic N/A linux-firmware1.187.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/25/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.12.0 dmi.board.name: 0VK7YF dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.12.0:bd02/25/2020:svnDellInc.:pnLatitude5491:pvr:rvnDellInc.:rn0VK7YF:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Latitude dmi.product.name: Latitude 5491 dmi.product.sku: 0818 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1889446/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1895603] Re: alsa/hdmi: the hdmi audio stops working from Ubuntu-4.4.0-155.182
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- xenial' to 'verification-done-xenial'. If the problem still exists, change the tag 'verification-needed-xenial' to 'verification-failed- xenial'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-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/1895603 Title: alsa/hdmi: the hdmi audio stops working from Ubuntu-4.4.0-155.182 Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux source package in Xenial: Fix Committed Bug description: [Impact] We had a Dell machine, this machine was enabled with ubuntu 4.4 kernel before, but recently the hdmi audio on this machine stopped working with the latest ubuntu 4.4. kernel. The system can't detect its plugging and can't output sound to it anymore. [Fix] This is because we backported a patch from stable updates, and that patch is for v5.2 kernel, if we backported it to 4.4 kernel, we need to do some change, and also we need to backport one more patch from stabe kernel. [Test Case] Connect a monitor to the machine and boot up, after booting up, we could see the hdmi audio is found, and play sound to the hdmi audio, we could hear the sound from monitor. [Regression Risk] It is possible to make the hdmi audio fail to work after applying this patchset, like the hdmi audio can't be detected after plugging a hdmi monitor. But this possibility is very low, we tested the patchset on many dell and lenovo machines, all worked well. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1895603/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1888354] Re: Kernel oops on 5.3.0.62 (Ubuntu Linux 19.10)
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1888354 Title: Kernel oops on 5.3.0.62 (Ubuntu Linux 19.10) Status in linux package in Ubuntu: Expired Bug description: This is the third kernel oops (VM freeze) in two days after updating linux-generic to 5.3.0.62 Output from syslog: Jul 20 15:11:13 santiago kernel: [ 7727.794172] BUG: kernel NULL pointer dereference, address: 0010 Jul 20 15:11:13 santiago kernel: [ 7727.794180] #PF: supervisor read access in kernel mode Jul 20 15:11:13 santiago kernel: [ 7727.794182] #PF: error_code(0x) - not-present page Jul 20 15:11:13 santiago kernel: [ 7727.794183] PGD 0 P4D 0 Jul 20 15:11:13 santiago kernel: [ 7727.794186] Oops: [#1] SMP PTI Jul 20 15:11:13 santiago kernel: [ 7727.794188] CPU: 1 PID: 1176 Comm: nfsd Not tainted 5.3.0-62-generic #56-Ubuntu Jul 20 15:11:13 santiago kernel: [ 7727.794189] Hardware name: VMware, Inc. VMware Virtual Platform/440BX Desktop Reference Platform, BIOS 6.00 12/12/2018 Jul 20 15:11:13 santiago kernel: [ 7727.794196] RIP: 0010:__cgroup_bpf_run_filter_skb+0x25e/0x3c0 Jul 20 15:11:13 santiago kernel: [ 7727.794198] Code: 40 89 45 cc 48 8b 45 a0 48 c7 00 00 00 00 00 48 c7 40 08 00 00 00 00 c7 40 10 00 00 00 00 e9 cf fe ff ff 48 8b 86 38 06 00 00 <4c> 8b 78 10 4c 8d 60 10 4d 85 ff 0f 84 3a 01 00 00 49 8d 46 30 31 Jul 20 15:11:13 santiago kernel: [ 7727.794199] RSP: 0018:b95e415b38f0 EFLAGS: 00010246 Jul 20 15:11:13 santiago kernel: [ 7727.794201] RAX: RBX: RCX: 0034 Jul 20 15:11:13 santiago kernel: [ 7727.794202] RDX: RSI: 92e190424000 RDI: 92e1b96a4ec0 Jul 20 15:11:13 santiago kernel: [ 7727.794203] RBP: b95e415b3978 R08: 92e10f0fef00 R09: Jul 20 15:11:13 santiago kernel: [ 7727.794204] R10: 92e1657aab30 R11: 0003 R12: 92e1b96a4ec0 Jul 20 15:11:13 santiago kernel: [ 7727.794205] R13: 0001 R14: 92e1a8d7c6e0 R15: a23e1280 Jul 20 15:11:13 santiago kernel: [ 7727.794206] FS: () GS:92e1bfc8() knlGS: Jul 20 15:11:13 santiago kernel: [ 7727.794208] CS: 0010 DS: ES: CR0: 80050033 Jul 20 15:11:13 santiago kernel: [ 7727.794209] CR2: 0010 CR3: 00022ce8a006 CR4: 000606e0 Jul 20 15:11:13 santiago kernel: [ 7727.794256] Call Trace: Jul 20 15:11:13 santiago kernel: [ 7727.794269] ? nf_confirm+0xd6/0x100 [nf_conntrack] Jul 20 15:11:13 santiago kernel: [ 7727.794272] ip_finish_output+0x76/0xb0 Jul 20 15:11:13 santiago kernel: [ 7727.794274] ip_output+0x75/0xf0 Jul 20 15:11:13 santiago kernel: [ 7727.794276] ? __ip_finish_output+0x1e0/0x1e0 Jul 20 15:11:13 santiago kernel: [ 7727.794278] ip_local_out+0x3d/0x50 Jul 20 15:11:13 santiago kernel: [ 7727.794279] __ip_queue_xmit+0x17a/0x450 Jul 20 15:11:13 santiago kernel: [ 7727.794281] ? __switch_to_asm+0x34/0x70 Jul 20 15:11:13 santiago kernel: [ 7727.794283] ? __switch_to_asm+0x40/0x70 Jul 20 15:11:13 santiago kernel: [ 7727.794284] ? __switch_to_asm+0x34/0x70 Jul 20 15:11:13 santiago kernel: [ 7727.794287] ip_queue_xmit+0x10/0x20 Jul 20 15:11:13 santiago kernel: [ 7727.794288] __tcp_transmit_skb+0x555/0xb10 Jul 20 15:11:13 santiago kernel: [ 7727.794290] tcp_write_xmit+0x3bc/0xb90 Jul 20 15:11:13 santiago kernel: [ 7727.794292] ? __alloc_skb+0x98/0x1d0 Jul 20 15:11:13 santiago kernel: [ 7727.794294] __tcp_push_pending_frames+0x37/0x100 Jul 20 15:11:13 santiago kernel: [ 7727.794296] tcp_push+0xfd/0x100 Jul 20 15:11:13 santiago kernel: [ 7727.794298] do_tcp_sendpages+0x5d8/0x620 Jul 20 15:11:13 santiago kernel: [ 7727.794300] tcp_sendpage_locked+0x43/0x60 Jul 20 15:11:13 santiago kernel: [ 7727.794302] tcp_sendpage+0x3c/0x60 Jul 20 15:11:13 santiago kernel: [ 7727.794304] inet_sendpage+0x59/0xa0 Jul 20 15:11:13 santiago kernel: [ 7727.794305] kernel_sendpage+0x1e/0x30 Jul 20 15:11:13 santiago kernel: [ 7727.794321] svc_send_common+0x66/0x160 [sunrpc] Jul 20 15:11:13 santiago kernel: [ 7727.794332] svc_sendto+0xf3/0x200 [sunrpc] Jul 20 15:11:13 santiago kernel: [ 7727.794352] ? nfsd4_encode_operation+0x152/0x1b0 [nfsd] Jul 20 15:11:13 santiago kernel: [ 7727.794360] ? nfsd4_proc_compound+0x241/0x740 [nfsd] Jul 20 15:11:13 santiago kernel: [ 7727.794368] ? nfsd4_decode_compound.constprop.0+0x3b0/0x460 [nfsd] Jul 20 15:11:13 santiago kernel: [ 7727.794370] ? refcount_dec_and_lock+0x12/0x60 Jul 20 15:11:13 santiago kernel: [ 7727.794374] ? module_put+0x13/0x20 Jul 20 15:11:13 santiago kernel: [ 7727.794385] svc_tcp_sendto+0x3a/0x50 [sunrpc]
[Kernel-packages] [Bug 1838151] Re: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support.
Ubuntu 20.04 user, can confirm this bug. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1838151 Title: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support. Status in PulseAudio: New Status in bluez package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in pulseaudio package in Ubuntu: In Progress Status in Arch Linux: New Bug description: Bluetooth HSP/HFP audio quality is poor on Ubuntu comparative to all other major platforms (Windows, MacOS, ChromeOS, Android, iOS). Modern Bluetooth headsets (such as the Bose QC series headphones, many others) are capable of using HFP 1.6 with mSBC 16kHz audio encoding. As it currently stands, Ubuntu defaults to only supporting HSP headsets using 8kHz CVSD, and is incapable of supporting HFP 1.6 at this time. The ChromiumOS team recently tackled this issue - https://bugs.chromium.org/p/chromium/issues/detail?id=843048 Their efforts may assist in bringing this to Ubuntu, however it appears that there are quite a lot of differences considering they have developed their own audio server solution etc. The Bluetooth Telephony Working Group published the HFP 1.6 spec in May 2011 - https://www.bluetooth.org/docman/handlers/downloaddoc.ashx?doc_id=238193 Patches have been proposed in the past for this issue to the kernel and PulseAudio: PulseAudio: https://patchwork.freedesktop.org/patch/245272/ Kernel: https://www.spinics.net/lists/linux-bluetooth/msg76982.html It appears that the Chromium OS team applied the same kernel patch: https://chromium.googlesource.com/chromiumos/third_party/kernel/+/77dd0cb94c1713a8a12f6e392955dfa64c430e54 ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: pulseaudio 1:12.2-2ubuntu3 ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8 Uname: Linux 5.0.0-20-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jnappi 2777 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Jul 27 11:08:29 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2017-11-04 (629 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: Upgraded to disco on 2019-07-18 (9 days ago) dmi.bios.date: 06/07/2016 dmi.bios.vendor: LENOVO dmi.bios.version: R07ET67W (2.07 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FW000TUS dmi.board.vendor: LENOVO dmi.board.version: SDK0J40705 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR07ET67W(2.07):bd06/07/2016:svnLENOVO:pn20FW000TUS:pvrThinkPadT460p:rvnLENOVO:rn20FW000TUS:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T460p dmi.product.name: 20FW000TUS dmi.product.sku: LENOVO_MT_20FW_BU_Think_FM_ThinkPad T460p dmi.product.version: ThinkPad T460p dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1838151/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1837348] Re: test_vxlan_under_vrf.sh in net from ubuntu_kernel_selftests failed with D-KVM / E-KVM
Failed with gkeop-5.4 as well. ** Tags added: sru-20200831 -- 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/1837348 Title: test_vxlan_under_vrf.sh in net from ubuntu_kernel_selftests failed with D-KVM / E-KVM Status in ubuntu-kernel-tests: New Status in linux-kvm package in Ubuntu: New Status in linux-kvm source package in Disco: Won't Fix Status in linux-kvm source package in Eoan: Won't Fix Bug description: Issue found on a AMD64 KVM node with Disco KVM kernel. selftests: net: test_vxlan_under_vrf.sh Error: Unknown device type. Cannot remove namespace file "/var/run/netns/hv-2": No such file or directory Cannot remove namespace file "/var/run/netns/vm-1": No such file or directory Cannot remove namespace file "/var/run/netns/vm-2": No such file or directory not ok 1..24 selftests: net: test_vxlan_under_vrf.sh [FAIL] ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-1010-kvm 5.0.0-1010.11 ProcVersionSignature: User Name 5.0.0-1010.11-kvm 5.0.8 Uname: Linux 5.0.0-1010-kvm x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 Date: Mon Jul 22 05:04:42 2019 SourcePackage: linux-kvm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1837348/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1812622] Re: fib related test in net from ubuntu_kernel_selftests failed with Operation not supported / Error: Unknown device type.
fib_tests.sh / fib-onlink-tests.sh failed with Error: Unknown device type. on gkeop-5.4 ** Tags added: sru-20200831 -- 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/1812622 Title: fib related test in net from ubuntu_kernel_selftests failed with Operation not supported / Error: Unknown device type. Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Status in linux-aws package in Ubuntu: New Status in linux-kvm package in Ubuntu: New Status in linux source package in Cosmic: Incomplete Status in linux-kvm source package in Cosmic: New Status in linux source package in Eoan: Won't Fix Status in linux-aws source package in Eoan: Won't Fix Status in linux-kvm source package in Eoan: Won't Fix Bug description: These tests: * fib_tests.sh * fib-onlink-tests.sh * fib_rule_tests.sh All failed on Cosmic KVM kernel with RTNETLINK answers: Operation not supported: selftests: net: fib_tests.sh Single path route test RTNETLINK answers: Operation not supported not ok 1..11 selftests: net: fib_tests.sh [FAIL] selftests: net: fib-onlink-tests.sh Configuring interfaces RTNETLINK answers: Operation not supported not ok 1..12 selftests: net: fib-onlink-tests.sh [FAIL] selftests: net: fib_rule_tests.sh RTNETLINK answers: Operation not supported not ok 1..16 selftests: net: fib_rule_tests.sh [FAIL] (works on generic Cosmic kernel) ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-1006-kvm 4.18.0-1006.6 ProcVersionSignature: User Name 4.18.0-1006.6-kvm 4.18.17 Uname: Linux 4.18.0-1006-kvm x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 Date: Mon Jan 21 08:00:22 2019 SourcePackage: linux-kvm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1812622/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1862559] Re: ubuntu 19.10: unresponsive/freezes on ThunderX2 if system is idle for ~22min
I asked our desktop team about this, and Iain Lane mentioned that Ubuntu overrides the GNOME default of auto-suspending, but that override only takes effect if you have the ubuntu-settings package installed. I tested this out on a Saber system, and I can confirm that it does seem to only happen when gdm is installed/running and ubuntu-settings is *not* installed. And that explains why I was unable to reproduce in Comment #5. There I had installed ubuntu-desktop which would bring in ubuntu- settings. It also explains why the CUDA-11 dependency chain *did* cause the problem on the x86 server in Comment #8. In that case, gdm3 is getting installed as a Recommends somewhere in the dependency chain - but it does not pull in gnome-settings. I'll therefore go ahead and close the 'linux' task as Invalid - this isn't a kernel bug. I'll mark the gdm3 bug as "Won't Fix" because, in theory, we could change the defaults inside of gdm3 itself - but we instead recommend users install ubuntu-settings to override the defaults. ** Changed in: linux (Ubuntu) Status: Incomplete => Invalid ** Changed in: gdm3 (Ubuntu) Status: Incomplete => Won't Fix -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1862559 Title: ubuntu 19.10: unresponsive/freezes on ThunderX2 if system is idle for ~22min Status in gdm3 package in Ubuntu: Won't Fix Status in linux package in Ubuntu: Invalid Bug description: UBUNTU 19.10 installed on ThunderX2 saber ARM64 machine. If the system left idle for ~22min it becomes unresponsive. The system will not take any inputs like from UART, ping ..etc. The system will completely freeze and we need to hard reset the system. It could be possible the system goes to hibernate state and could not able to come out of the state. Dmesg log when system halts/no response on Saber boards (TX2) Ubuntu 19.10 ubuntu ttyAMA0 ubuntu login: ubuntu Password: Last login: Wed Jan 29 20:08:22 PST 2020 on ttyAMA0 Welcome to Ubuntu 19.10 (GNU/Linux 5.3.0-26-generic aarch64) * Documentation: https://help.ubuntu.com * Management: https://landscape.canonical.com * Support:https://ubuntu.com/advantage ubuntu@ubuntu:~$ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 19.10 Release: 19.10 Codename: eoan [ +0.732512] audit: type=1400 audit(1580358920.412:2): apparmor="STATUS" operation="profile_load" profile="unconfined" name="lsb_release" pid=3087 comm="apparmor_parser" [ +0.64] audit: type=1400 audit(1580358920.412:3): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/sbin/ippusbxd" pid=3091 comm="apparmor_parser" [ +0.000168] audit: type=1400 audit(1580358920.412:4): apparmor="STATUS" operation="profile_load" profile="unconfined" name="nvidia_modprobe" pid=3086 comm="apparmor_parser" [ +0.05] audit: type=1400 audit(1580358920.412:5): apparmor="STATUS" operation="profile_load" profile="unconfined" name="nvidia_modprobe//kmod" pid=3086 comm="apparmor_parser" [ +0.000546] audit: type=1400 audit(1580358920.412:6): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/bin/man" pid=3085 comm="apparmor_parser" [ +0.06] audit: type=1400 audit(1580358920.412:7): apparmor="STATUS" operation="profile_load" profile="unconfined" name="man_filter" pid=3085 comm="apparmor_parser" [ +0.05] audit: type=1400 audit(1580358920.412:8): apparmor="STATUS" operation="profile_load" profile="unconfined" name="man_groff" pid=3085 comm="apparmor_parser" [ +0.000854] audit: type=1400 audit(1580358920.412:9): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/sbin/tcpdump" pid=3089 comm="apparmor_parser" [ +0.002667] audit: type=1400 audit(1580358920.416:10): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/sbin/dhclient" pid=3093 comm="apparmor_parser" [ +0.04] audit: type=1400 audit(1580358920.416:11): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=3093 comm="apparmor_parser" [ +1.382579] igb :92:00.1 enp146s0f1: igb: enp146s0f1 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX [ +0.000299] IPv6: ADDRCONF(NETDEV_CHANGE): enp146s0f1: link becomes ready [ +3.131173] mpt3sas_cm0: port enable: SUCCESS [Jan29 20:36] random: crng init done [ +0.04] random: 7 urandom warning(s) missed due to ratelimiting *[Jan29 20:37] rfkill: input handler disabled* *[Jan29 20:57] PM: suspend entry (deep)* To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1862559/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More
[Kernel-packages] [Bug 1894017] Re: Keyboard not working
Same here. Same computer as original bug report (Hewlett-Packard HP Pavilion 11 x360 PC) But different distro release (Xubuntu 20.04) Laptop keyboard and trackpad totally nonfunctional on any kernel higher than 5.4.0.42. Starting with 5.4.0-45 and all further kernels to today (2020-09-22) the problem persists. External (USB) mice and keyboards work fine. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1894017 Title: Keyboard not working Status in linux package in Ubuntu: Confirmed Bug description: The laptop keyboard doesn't work at login or in the de. If I ctrl+alt+F3 from an external usb keyboard to a terminal the laptop keyboard works. An external usb keyboard works everywhere. The laptop's keyboard does work everywhere with the previous kernel 5.4.0.42. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-45-lowlatency 5.4.0-45.49 ProcVersionSignature: Ubuntu 5.4.0-45.49-lowlatency 5.4.55 Uname: Linux 5.4.0-45-lowlatency x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Thu Sep 3 03:09:49 2020 InstallationDate: Installed on 2019-08-07 (392 days ago) InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: Hewlett-Packard HP Pavilion 11 x360 PC ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-45-lowlatency root=UUID=6035c42c-766d-44fd-b45c-6cdf9c74e0b5 ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-5.4.0-45-lowlatency N/A linux-backports-modules-5.4.0-45-lowlatency N/A linux-firmware 1.187.3 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-04-06 (149 days ago) dmi.bios.date: 03/13/2018 dmi.bios.vendor: Insyde dmi.bios.version: F.30 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 2209 dmi.board.vendor: Hewlett-Packard dmi.board.version: 57.57 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.30:bd03/13/2018:svnHewlett-Packard:pnHPPavilion11x360PC:pvr097710405F00010420180:rvnHewlett-Packard:rn2209:rvr57.57:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV X=MIN dmi.product.name: HP Pavilion 11 x360 PC dmi.product.sku: M0B61EA#ACQ dmi.product.version: 097710405F00010420180 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1894017/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1894605] Re: gtp: unable to associate contextes to interfaces
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
bionic' to 'verification-done-bionic'. If the problem still exists,
change the tag 'verification-needed-bionic' to 'verification-failed-
bionic'.
If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!
** Tags added: verification-needed-bionic
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1894605
Title:
gtp: unable to associate contextes to interfaces
Status in linux package in Ubuntu:
Fix Committed
Status in linux source package in Bionic:
Fix Committed
Status in linux source package in Focal:
Fix Committed
Status in linux source package in Groovy:
Fix Committed
Bug description:
[Impact]
When a user dump pdp contextes, it cannot associate them with existing
gtp interfaces. Thus, the dump is unusable.
This problem has been fixed in the upstream commit b274e47d9e3f ("gtp: add
GTPA_LINK info to msg sent to userspace"):
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=b274e47d9e3f
[Test Case]
Create several gtp interfaces and setup PDP contextes on them. Perform
a dump with the genl command GTP_CMD_GETPDP.
[Regression Potential]
The patch affects only the gtp driver and is quite trivial. Thus, the
potential regressions are limited to this area and low.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1894605/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1889446] Re: DELL LATITUDE 5491 touchscreen doesn't work
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed- bionic'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-bionic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1889446 Title: DELL LATITUDE 5491 touchscreen doesn't work Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Fix Committed Status in linux source package in Bionic: Fix Committed Status in linux source package in Focal: Fix Committed Bug description: I will really appreciate any help like said in summary my touchscreen doesnt work on my dell lattitude 5491 with a I5-8400H cpu. Any idea ? ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-42-generic 5.4.0-42.46 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ying 1977 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Jul 29 18:45:20 2020 InstallationDate: Installed on 2020-07-29 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Dell Inc. Latitude 5491 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-42-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-42-generic N/A linux-backports-modules-5.4.0-42-generic N/A linux-firmware1.187.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/25/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.12.0 dmi.board.name: 0VK7YF dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.12.0:bd02/25/2020:svnDellInc.:pnLatitude5491:pvr:rvnDellInc.:rn0VK7YF:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Latitude dmi.product.name: Latitude 5491 dmi.product.sku: 0818 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1889446/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1895803] Re: uvcvideo: add mapping for HEVC payloads
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed- bionic'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-bionic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1895803 Title: uvcvideo: add mapping for HEVC payloads Status in HWE Next: Confirmed Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: Fix Committed Status in linux source package in Focal: Confirmed Status in linux source package in Groovy: Confirmed Bug description: == Impact == Add mapping for HEVC so that uvcvideo can support the format. == Fixes == The commit "media: uvcvideo: Add mapping for HEVC payloads", which is already in the maintainer tree: https://patchwork.kernel.org/patch/11577395/ https://git.linuxtv.org/media_tree.git/commit/?id=40b222b56ea81aa636a4aa7a84939786369e726b For 4.15 we also need the "media: videodev2.h: Add v4l2 definition for HEVC" from mainline. == Regression Potential == Low since the patch only introduces a new format. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1895803/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1895258] Re: rtnetlink.sh in net from ubuntu_kernel_selftests is returning 1 for a skipped test
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
bionic' to 'verification-done-bionic'. If the problem still exists,
change the tag 'verification-needed-bionic' to 'verification-failed-
bionic'.
If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!
** Tags added: verification-needed-bionic
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1895258
Title:
rtnetlink.sh in net from ubuntu_kernel_selftests is returning 1 for a
skipped test
Status in ubuntu-kernel-tests:
In Progress
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Bionic:
Fix Committed
Bug description:
== SRU Justification ==
The rtnetlink.sh in kselftest/net from 4.15 kernel will fail with:
selftests: rtnetlink.sh
PASS: policy routing
PASS: route get
PASS: preferred_lft addresses have expired
PASS: tc htb hierarchy
PASS: gre tunnel endpoint
PASS: bridge setup
PASS: ipv6 addrlabel
PASS: set ifalias e1dfde61-e5a7-415f-8bd9-924e9796038f for test-dummy0
PASS: vrf
PASS: vxlan
SKIP: fou: iproute2 too old
SKIP: macsec: iproute2 too old
not ok 1..10 selftests: rtnetlink.sh [FAIL]
The return value for this script is 1.
Look into the code, it's the kci_test_encap_fou() test that causes
this issue:
ip fou help 2>&1 |grep -q 'Usage: ip fou'
if [ $? -ne 0 ];then
echo "SKIP: fou: iproute2 too old"
return 1
fi
It should at least return ksft_skip=4 (or 0 with older release that
does not support this skip code in kselftest framework)
== Fix ==
* 57aefc7c226d ("selftests: net: return Kselftest Skip code for
skipped tests")
This patch needs to be backported into Bionic, as some newer tests
does not exist in Bionic.
== Test ==
Tested directly on the affected kernel, the test will be marked as:
not ok 1..10 selftests: rtnetlink.sh [SKIP]
== Regression Potential ==
Low, changes limited to test scripts. And the kselftest framework in
Bionic can handle this ksft_skip=4 return code properly, tests won't
be marked as failed because of this.
Although IMO in this case the test should be marked as PASS instead of
SKIP in the end, as not all tests were skipped, but that's something
we could fix with upstream in the future.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1895258/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1891454] Re: [UBUNTU 20.04] kernel: s390/cpum_cf, perf: changeDFLT_CCERROR counter name
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
bionic' to 'verification-done-bionic'. If the problem still exists,
change the tag 'verification-needed-bionic' to 'verification-failed-
bionic'.
If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!
** Tags added: verification-needed-bionic
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1891454
Title:
[UBUNTU 20.04] kernel: s390/cpum_cf,perf: changeDFLT_CCERROR counter
name
Status in Ubuntu on IBM z Systems:
Fix Committed
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Bionic:
Fix Committed
Status in linux source package in Focal:
Fix Released
Status in linux source package in Groovy:
Fix Released
Bug description:
SRU Justification:
==
[Impact]
* Change the counter name DLFT_CCERROR to DLFT_CCFINISH on IBM z15 to
avoid confusion.
* This counter counts completed DEFLATE instructions with exit code 0,
1 or 2.
* And since exit code 0 means success and exit code 1 or 2 indicate
errors the name can be ambiguous.
[Fix]
* Rename s390 z15 counter named DFLT_CCERROR to DFLT_CCFINISH.
* Backport Focal: https://launchpadlibrarian.net/493272507/0001-s390
-cpum_cf-perf-change-DFLT_CCERROR-counter-name.patch
* Backport Bionic:
https://launchpadlibrarian.net/493439681/u18-0001-s390-cpum_cf-Add-
new-extended-counters-for-IBM-z15.patch
[Test Case]
* Enable hardware counters in the activation profile of a z15 LPAR.
* Just check the countername in sysfs with: ls
/sys/devices/cpum_cf/events/{DFLT_CCERROR,DFLT_CCFINISH}
[Regression Potential]
* The regression potential can be considered as low, since:
* Counters like these are usually not activated by default and need to
be explicitly enabled.
* No code functionality is changed with that patch, only a renaming is
done at 3 places in one code file
arch/s390/kernel/perf_cpum_cf_events.c as well as in /tools/perf/pmu-
events/arch/s390/cf_z15/extended.json.
* The fix got already upstream accepted in 5.8-rc7, hence it got
upstream reviewed,
* and the modifications are limited to s390x, are only relevant for
the z15 / LinuxONE III hw generation that are relatively new.
* Issue with the renaming I can think of are that people don't know
about the new name and may look for the old one and don't find it
anymore,
* and with that also if the old counter name is used in scripts or
applications, these may fails due to an unknown counter name.
[Other Info]
* The backports are based on commit
3d3af181d370069861a3be94608464e2ff3682e2 ("s390/cpum_cf,perf: change
DFLT_CCERROR counter name") that is upstream accepted since v5.8-rc7.
* Hence this SRU is not requested for groovy, since it's already in groovys
kernel 5.8 in proposed, but only requested for focal and bionic.
__
Description: kernel: s390/cpum_cf,perf: change DFLT_CCERROR counter name
Symptom: Counter name CCERROR is misleading.
Problem: Change the counter name DLFT_CCERROR to DLFT_CCFINISH on
IBM z15. This counter counts completed DEFLATE instructions
with exit code 0, 1 or 2. Since exit code 0 means success
and exit code 1 or 2 indicate errors, change the counter
name to avoid confusion. This counter is incremented each
time the DEFLATE instruction completed regardless if an
error was detected or not.
Solution: Rename s390 z15 counter named DFLT_CCERROR to DFLT_CCFINISH
Reproduction: Command # ls /sys/devices/cpum_cf/events/DFLT_CCERROR
currently succeeds. After this patch has been applied the
command does not work anymore. The file does not exist
anymore. Use command
# ls /sys/devices/cpum_cf/events/DFLT_CCFINISH
instead.
Upstream-ID: 5ce1a24dd98c00a57a8fa13660648abf7e08e3ef
Component: kernel 5.8
Will be integrated into 20.10 by kernel 5.8 integration.
Backport available for 20.04.
To be checked for 18.04 and 16.04, update will be provided
Here is the backported patch.
The upstream commit id is 3d3af181d370069861a3be94608464e2ff3682e2
("s390/cpum_cf,perf: change DFLT_CCERROR counter name")
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1891454/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to :
[Kernel-packages] [Bug 1892546] Re: Novalink (mkvterm command failure)
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed- bionic'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-bionic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1892546 Title: Novalink (mkvterm command failure) Status in The Ubuntu-power-systems project: Fix Committed Status in linux package in Ubuntu: In Progress Status in linux source package in Xenial: Fix Committed Status in linux source package in Bionic: Fix Committed Status in linux source package in Focal: Fix Committed Status in linux source package in Groovy: In Progress Bug description: SRU Justification: [Impact] * drmgr command is failing while trying to open console for IBMi on PowerVM LPAR [Fix] * 63ffcbdad738 "tty: hvcs: Don't NULL tty->driver_data until hvcs_cleanup()" [Test Case] * Create a VM from PowerVC on a Novalink managed host. * Unmanage and manage the VM, this problem gets reproduced. * grep the logs for "drmgr" [Regression Potential] The regression can be considered as very low, since: * limited to the IBM Hypervisor Virtual Console Server. * patched kernel where shared and successfully tested by IBM. * the worse case, if the cleanup is broken a new opened connection might break. [Other] * The patch got upstream accepted. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1892546/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1896482] Re: acpi event detection crashes
The warning messages occurred between "ACPI: EC: interrupt blocked" and "ACPI: EC: interrupt unblocked". Let's try to apply all (17) mainline patches to ACPI EC to Ubuntu-5.4.0-47.51. If this solves the problems we can then bi-select to identify which patches are the solution and then backport to 5.4 kernel. The test kernel is available @ https://people.canonical.com/~alexhung/LP1896482/ and the applied patches are listed in ec_patches.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/1896482 Title: acpi event detection crashes Status in linux package in Ubuntu: Confirmed Bug description: Right after booting, acpi lid open/close is detected as it should be by the kernel, but some time later it crashes, so I have to manually suspend the system. The traceback is here: Sep 20 11:35:33 laxmi kernel: [232492.303557] [ cut here ] Sep 20 11:35:33 laxmi kernel: [232492.303564] WARNING: CPU: 0 PID: 8302 at kernel/workqueue.c:1416 __queue_work+0x337/0x3f0 Sep 20 11:35:33 laxmi kernel: [232492.303565] Modules linked in: ccm rfcomm cmac algif_hash algif_skcipher af_alg bnep nls_iso8859_1 snd_soc_skl_hda_dsp snd_hda_codec_hdmi snd_soc_hdac_hdmi snd_hda_codec_realtek snd_soc_dmic snd_hda_codec_generic snd_sof_pci mei_hdcp x86_pkg_temp_thermal intel_powerclamp intel_rapl_msr coretemp snd_sof_intel_hda_common snd_soc_hdac_hda snd_sof_intel_hda kvm_intel snd_sof_intel_byt snd_sof_intel_ipc kvm snd_sof snd_sof_xtensa_dsp snd_hda_ext_core snd_soc_acpi_intel_match snd_soc_acpi snd_soc_core snd_compress ac97_bus snd_pcm_dmaengine joydev crct10dif_pclmul ghash_clmulni_intel snd_hda_intel aesni_intel snd_intel_dspcfg crypto_simd iwlmvm cryptd snd_hda_codec glue_helper rapl mac80211 snd_hda_core snd_seq_midi snd_hwdep snd_seq_midi_event libarc4 intel_cstate uvcvideo snd_rawmidi i915 snd_pcm videobuf2_vmalloc input_leds thinkpad_acpi btusb videobuf2_memops serio_raw btrtl videobuf2_v4l2 snd_seq btbcm btintel nvram videobuf2_common iwlwifi processor_thermal_device bluetooth videodev Sep 20 11:35:33 laxmi kernel: [232492.303600] drm_kms_helper mc wmi_bmof i2c_algo_bit intel_rapl_common fb_sys_fops ucsi_acpi intel_wmi_thunderbolt ecdh_generic ledtrig_audio typec_ucsi mei_me syscopyarea hid_multitouch snd_seq_device sysfillrect cfg80211 ecc sysimgblt mei intel_soc_dts_iosf typec snd_timer snd soundcore int3403_thermal int340x_thermal_zone acpi_pad intel_hid int3400_thermal acpi_thermal_rel sparse_keymap mac_hid sch_fq_codel parport_pc ppdev lp parport drm ip_tables x_tables autofs4 hid_generic crc32_pclmul nvme psmouse e1000e i2c_i801 thunderbolt intel_lpss_pci intel_lpss nvme_core idma64 virt_dma i2c_hid hid wmi video pinctrl_cannonlake pinctrl_intel Sep 20 11:35:33 laxmi kernel: [232492.303628] CPU: 0 PID: 8302 Comm: kworker/0:0 Not tainted 5.4.0-47-generic #51-Ubuntu Sep 20 11:35:33 laxmi kernel: [232492.303629] Hardware name: LENOVO 20U9001NUS/20U9001NUS, BIOS N2WET19W (1.09 ) 07/01/2020 Sep 20 11:35:33 laxmi kernel: [232492.303632] Workqueue: kec_query acpi_ec_event_processor Sep 20 11:35:33 laxmi kernel: [232492.303635] RIP: 0010:__queue_work+0x337/0x3f0 Sep 20 11:35:33 laxmi kernel: [232492.303637] Code: ff 49 8b 9d a0 00 00 00 e9 aa fd ff ff 65 8b 05 e7 59 15 6d a9 00 01 1f 00 75 0f 65 48 8b 3c 25 c0 6b 01 00 f6 47 24 20 75 25 <0f> 0b 48 83 c4 18 5b 41 5c 41 5d 41 5e 41 5f 5d c3 0f 0b e9 fd fd Sep 20 11:35:33 laxmi kernel: [232492.303638] RSP: 0018:b16bc0ebb8f8 EFLAGS: 00010087 Sep 20 11:35:33 laxmi kernel: [232492.303640] RAX: 9a2477432600 RBX: 0002 RCX: 0004 Sep 20 11:35:33 laxmi kernel: [232492.303641] RDX: 9a2475af4a90 RSI: 9a2475b03200 RDI: 9a2430215f00 Sep 20 11:35:33 laxmi kernel: [232492.303642] RBP: b16bc0ebb938 R08: R09: 0007 Sep 20 11:35:33 laxmi kernel: [232492.303643] R10: 9a24755ad678 R11: R12: 9a2475af4a00 Sep 20 11:35:33 laxmi kernel: [232492.303643] R13: 9a2475b03200 R14: 2000 R15: 9a2475af4a90 Sep 20 11:35:33 laxmi kernel: [232492.303645] FS: () GS:9a247740() knlGS: Sep 20 11:35:33 laxmi kernel: [232492.303646] CS: 0010 DS: ES: CR0: 80050033 Sep 20 11:35:33 laxmi kernel: [232492.303647] CR2: 00c42098b000 CR3: 00018520a003 CR4: 003606f0 Sep 20 11:35:33 laxmi kernel: [232492.303648] Call Trace: Sep 20 11:35:33 laxmi kernel: [232492.303654] ? acpi_os_release_lock+0xe/0x10 Sep 20 11:35:33 laxmi kernel: [232492.303657] queue_work_on+0x3b/0x50 Sep 20 11:35:33 laxmi kernel: [232492.303659] advance_transaction+0x2b9/0x620 Sep 20 11:35:33 laxmi kernel: [232492.303661] acpi_ec_transaction+0x16c/0x3c0 Sep 20 11:35:33 laxmi kernel: [232492.303663]
[Kernel-packages] [Bug 1892860] Re: af_alg07 in crypto / cve-2019-8912 in cve from ubuntu_ltp failed on B-arm64
UCT mentions commits 9060cb719e61b685ec0102574e10337fa5f445ea (specific
to AF_ALG) and ff7b11aa481f682e0e9711abfeb7d03f5cd612bf (all sockets).
The other commit we should care about is
6d8c50dcb029872b298eea68cc6209c866fd3e14 ("socket: close race condition
between sock_close() and sockfs_setattr()").
If you have that one, you should expect ENOENT (which is what the test
case expects), but only if sock_close wins the race. If it doesn't, you
might still succeed at sockfs_setattr, and then we get this test
failure.
Cascardo.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1892860
Title:
af_alg07 in crypto / cve-2019-8912 in cve from ubuntu_ltp failed on
B-arm64
Status in ubuntu-kernel-tests:
New
Status in linux package in Ubuntu:
Incomplete
Bug description:
Issue found on 4.15.0-114.115-generic with ARM64 node appleton-kernel
and wright-kernel.
Looks like this is a new test case added 13 days ago:
https://github.com/linux-test-project/ltp/commit/fdff6139e43aa9b19f27907f6d7f2cb4765632a1#diff-8a83d6b2c6c7d74e750e3af47e3f4a79
The test will fail with:
startup='Fri Aug 14 10:13:27 2020'
tst_test.c:1247: INFO: Timeout per run is 0h 05m 00s
tst_taint.c:88: CONF: Ignoring already set kernel warning taint
../../../include/tst_fuzzy_sync.h:507: INFO: Minimum sampling period ended
../../../include/tst_fuzzy_sync.h:331: INFO: loop = 1024, delay_bias = 0
../../../include/tst_fuzzy_sync.h:320: INFO: start_a - start_b: { avg =
-2259470ns, avg_dev = 13695382ns, dev_ratio = 6.06 }
../../../include/tst_fuzzy_sync.h:320: INFO: end_a - start_a : { avg =
13968ns, avg_dev = 4310ns, dev_ratio = 0.31 }
../../../include/tst_fuzzy_sync.h:320: INFO: end_b - start_b : { avg =
15975ns, avg_dev = 50ns, dev_ratio = 0.00 }
../../../include/tst_fuzzy_sync.h:320: INFO: end_a - end_b : { avg =
-2261477ns, avg_dev = 13699742ns, dev_ratio = 6.06 }
../../../include/tst_fuzzy_sync.h:320: INFO: spins : { avg = 3575095 ,
avg_dev = 4553 , dev_ratio = 0.00 }
../../../include/tst_fuzzy_sync.h:637: INFO: Exceeded execution time,
requesting exit
af_alg07.c:97: FAIL: fchownat() failed to fail, kernel may be vulnerable
HINT: You _MAY_ be missing kernel fixes, see:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=9060cb719e61
HINT: You _MAY_ be vulnerable to CVE(s), see:
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-8912
Summary:
passed 0
failed 1
skipped 1
warnings 0
tag=af_alg07 stime=159747 dur=150 exit=exited stat=33 core=no cu=15051
cs=0
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1892860/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1886769] Re: [ 0.000000] Initramfs unpacking failed: Decoding failed
** Tags added: focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1886769 Title: [ 0.00] Initramfs unpacking failed: Decoding failed Status in linux package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1. Download MATE Groovy daily (sha256sum = 7d2fdad36b8fcf0409aa0a484755e5fc5ef3798fd256eeebbde905a71ad474b7 ) 2. Insert ISO into VirtualBox with EFI enabled 3. Boot VM Expected results: * VM boots normally Actual results: * VM hangs during early boot with message [ 0.00] Initramfs unpacking failed: Decoding failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1886769/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1895563] Re: Kernel Oops: Rsyncing to bcache device w/o backing cache kernel panic
Cannot upload crash dumps due to timeout presumably due to size (1.6Gb). Here're links instead: 1. http://temp.karakhorum.com/dl/crash_202009120944.tar.bz2 2. http://temp.karakhorum.com/dl/crash_202009121459.tar.bz2 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1895563 Title: Kernel Oops: Rsyncing to bcache device w/o backing cache kernel panic Status in linux package in Ubuntu: Confirmed Bug description: Platform details: 1) version.log attached 2) lspci-vnvn.log attached 3) lsb_release -rd Description:Ubuntu 18.04.5 LTS Release:18.04 4) apt-cache policy bcache-tools bcache-tools: Installed: 1.0.8-2ubuntu0.18.04.1 Candidate: 1.0.8-2ubuntu0.18.04.1 Version table: *** 1.0.8-2ubuntu0.18.04.1 500 500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 1.0.8-2build1 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages 5) uname -a: Linux timber4 4.15.0-117-generic #118-Ubuntu SMP Fri Sep 4 20:02:41 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux Short problem description: Rsyncing from a 1.4TB home dir to a an new filesystem on a bcache device without an attached cache eventually results in kernel panic. What I expected to happen: no kernel panic. Long problem description: 1) Devices / Filesystems: bfd01: 8*4TB configured as RAID6 using md LVM2 volume group. bfd02: 8*4TB configured as RAID6 using Dell PERC H810 LVM2 volume group. The tree contains 1069685 files / dirs. 2) Steps to reproduce: # Make the device, format and mount it make-bcache -B /dev/vg-bfd02/delme01_bc mkfs.xfs -f -L delme01bc /dev/bcache0 mount /dev/bcache0 /dev/bfd02/delme01bc # Rsync flags="-a --delete" ; info_cmd="--info=progress2" ; excludes=""; src=/mnt/bfd01/delme01 ; tgt=/mnt/bfd02/delme01bc/ ; time rsync $flags $info_cmd $excludes $src/ $tgt/ ... # eventually kernel panic Using incremental rsync it will kernel panic after reading about 21GB. # If instead I use non-incremental rsync it will kernel panic after reading about 1.2-1.3TB. flags="--no-inc-recursive -ax -HAXS --delete" ; info_cmd="--info=progress2" ; excludes=""; ... # eventually kernel panic Additional detail: 1) I was *not* able to reproduce if bfd01/delm01bc was a target and bfd02 was the source e.g. # Rsync flags="-a --delete" ; info_cmd="--info=progress2" ; excludes=""; src=/mnt/bfd02/delme01 ; tgt=/mnt/bfd01/delme01bc/ ; time rsync $flags $info_cmd $excludes $src/ $tgt/ ... # rsync completes successfully 2) I was *not* able to reproduce if I attached and then detached a cache set: ceho 'd3b93488-714e-4efa-af94-cd80fd2db11f' > /sys/block/bcache0/bcache/attach echo 1 > /sys/block/bcache0/bcache/detach ... time rsync $flags $info_cmd $excludes $src/ $tgt/ ... # rsync completes successfully I have 11 compressed kernel crash dumps. I will upload 3 after filing this. Let me know if you want the other 8. ProblemType: KernelCrash DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-117-generic 4.15.0-117.118 ProcVersionSignature: Ubuntu 4.15.0-117.118-generic 4.15.18 Uname: Linux 4.15.0-117-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Sep 13 12:53 seq crw-rw 1 root audio 116, 33 Sep 13 12:53 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.17 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Sat Sep 12 09:51:37 2020 HibernationDevice: RESUME=none IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: Dell Inc. PowerEdge R620 PciMultimedia: ProcFB: 0 mgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-117-generic root=UUID=de68d15b-3948-4666-9bc5-5cbecc83971c ro maybe-ubiquity crashkernel=512M-:512M RelatedPackageVersions: linux-restricted-modules-4.15.0-117-generic N/A linux-backports-modules-4.15.0-117-generic N/A linux-firmware 1.173.19 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/06/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.9.0 dmi.board.name: 0KCKR5 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.9.0:bd12/06/2019:svnDellInc.:pnPowerEdgeR620:pvr:rvnDellInc.:rn0KCKR5:rvrA00:cvnDellInc.:ct23:cvr: dmi.product.name: PowerEdge R620 dmi.sys.vendor: Dell Inc. ---
[Kernel-packages] [Bug 1887674] Re: Introduce the new NVIDIA 450-server and the 450 UDA series
** Changed in: nvidia-graphics-drivers-450-server (Ubuntu) Status: In Progress => Fix Released ** Changed in: nvidia-graphics-drivers-450 (Ubuntu) Status: In Progress => Fix Released ** Changed in: linux-restricted-modules (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-restricted-modules in Ubuntu. https://bugs.launchpad.net/bugs/1887674 Title: Introduce the new NVIDIA 450-server and the 450 UDA series Status in OEM Priority Project: New Status in linux package in Ubuntu: Triaged Status in linux-restricted-modules package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-450 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-450-server package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-restricted-modules source package in Bionic: Fix Released Status in nvidia-graphics-drivers-450 source package in Bionic: Fix Released Status in nvidia-graphics-drivers-450-server source package in Bionic: Fix Released Status in linux source package in Focal: Fix Released Status in linux-restricted-modules source package in Focal: Fix Released Status in nvidia-graphics-drivers-450 source package in Focal: Fix Released Status in nvidia-graphics-drivers-450-server source package in Focal: Fix Released Bug description: [Impact] These releases provide both bug fixes and new features, and we would like to make sure all of our users have access to these improvements. See the changelog entry below for a full list of changes and bugs. [Test Case] The following development and SRU process was followed: https://wiki.ubuntu.com/NVidiaUpdates Certification test suite must pass on a range of hardware: https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu The QA team that executed the tests will be in charge of attaching the artifacts and console output of the appropriate run to the bug. nVidia maintainers team members will not mark ‘verification-done’ until this has happened. [Regression Potential] In order to mitigate the regression potential, the results of the aforementioned system level tests are attached to this bug. [Discussion] To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1887674/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1891336] Re: gkrellm2-cpufreq depends on libcpupower-dev produced by Debian kernel
It appears to fail only for ppc64el. The proper solution sounds to be complicated; would it be suitable as a temporary workaround to drop that arch from the cpufreqd package (and leave this bug open until the underlying issue is resolved)? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1891336 Title: gkrellm2-cpufreq depends on libcpupower-dev produced by Debian kernel Status in cpufreqd package in Ubuntu: New Status in gkrellm2-cpufreq package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Bug description: I don't know how important that is as gkrellm2-cpufreq itself is scheduled for removal. But I wanted to make sure that it is known that the Debian kernel produces "libcpupower-dev" which isn't available in Ubuntu and thereby blocking various things in proposed. root@d10-sid:~# apt-cache show libcpupower-dev Package: libcpupower-dev Source: linux Version: 5.7.10-1 Installed-Size: 169 Maintainer: Debian Kernel Team Architecture: amd64 Replaces: libcpufreq-dev Provides: libcpufreq-dev Depends: libcpupower1 (= 5.7.10-1) Conflicts: libcpufreq-dev Description-en: CPU frequency and voltage scaling tools for Linux (development files) libcpupower is a library for inspecting and controlling cpufreq and cpuidle tunables. . This package is needed to compile programs against libcpupower. gkrellm2-cpufreq will most likely be removed from goovy as it makes no sense without that build-dep. Never the less the kernel Team could evaluate if providing "libcpupower-dev" makes sense for Ubuntu. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cpufreqd/+bug/1891336/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1892860] Re: af_alg07 in crypto / cve-2019-8912 in cve from ubuntu_ltp failed on B-arm64
It seems that you *can* chown a socket, so this call just works fine. No
races with close needed. So, it seems to be a bogus assumption on the
part of the test.
Cascardo.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1892860
Title:
af_alg07 in crypto / cve-2019-8912 in cve from ubuntu_ltp failed on
B-arm64
Status in ubuntu-kernel-tests:
New
Status in linux package in Ubuntu:
Incomplete
Bug description:
Issue found on 4.15.0-114.115-generic with ARM64 node appleton-kernel
and wright-kernel.
Looks like this is a new test case added 13 days ago:
https://github.com/linux-test-project/ltp/commit/fdff6139e43aa9b19f27907f6d7f2cb4765632a1#diff-8a83d6b2c6c7d74e750e3af47e3f4a79
The test will fail with:
startup='Fri Aug 14 10:13:27 2020'
tst_test.c:1247: INFO: Timeout per run is 0h 05m 00s
tst_taint.c:88: CONF: Ignoring already set kernel warning taint
../../../include/tst_fuzzy_sync.h:507: INFO: Minimum sampling period ended
../../../include/tst_fuzzy_sync.h:331: INFO: loop = 1024, delay_bias = 0
../../../include/tst_fuzzy_sync.h:320: INFO: start_a - start_b: { avg =
-2259470ns, avg_dev = 13695382ns, dev_ratio = 6.06 }
../../../include/tst_fuzzy_sync.h:320: INFO: end_a - start_a : { avg =
13968ns, avg_dev = 4310ns, dev_ratio = 0.31 }
../../../include/tst_fuzzy_sync.h:320: INFO: end_b - start_b : { avg =
15975ns, avg_dev = 50ns, dev_ratio = 0.00 }
../../../include/tst_fuzzy_sync.h:320: INFO: end_a - end_b : { avg =
-2261477ns, avg_dev = 13699742ns, dev_ratio = 6.06 }
../../../include/tst_fuzzy_sync.h:320: INFO: spins : { avg = 3575095 ,
avg_dev = 4553 , dev_ratio = 0.00 }
../../../include/tst_fuzzy_sync.h:637: INFO: Exceeded execution time,
requesting exit
af_alg07.c:97: FAIL: fchownat() failed to fail, kernel may be vulnerable
HINT: You _MAY_ be missing kernel fixes, see:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=9060cb719e61
HINT: You _MAY_ be vulnerable to CVE(s), see:
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-8912
Summary:
passed 0
failed 1
skipped 1
warnings 0
tag=af_alg07 stime=159747 dur=150 exit=exited stat=33 core=no cu=15051
cs=0
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1892860/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1895458] Re: Computer freezes on kernel 5, works on kernel 4
1. kernel 5.4.0-48 -"quiet" -"splash" +"dis_ucode_ldr" cat /proc/cpuinfo > cpuinfo-5.4.0-48.txt dpkg -s intel-microcode | grep Version > intel-microcode-5.4.0-48.txt 2. kernel 4.15.0-112 -"quiet" -"splash" -"dis_ucode_ldr" cat /proc/cpuinfo > cpuinfo-4.15.0-112.txt dpkg -s intel-microcode | grep Version > intel-microcode-4.15.0-112.txt I noticed something disturbing: The printout to the screen from kernel 4 is kind of neat and left aligned. While the printout from kernel 5 is all over the screen (sloppy and not aligned - like someone missed many '\n'). This may seem unimportant, but is demonstrates the same trend I see in everything :) For example an old refrigerator works for 20 years, while the new and shiny one breaks within (not even) 5 years. ** Attachment added: "cmds.tar.gz" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1895458/+attachment/5413031/+files/cmds.tar.gz -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1895458 Title: Computer freezes on kernel 5, works on kernel 4 Status in linux package in Ubuntu: Confirmed Bug description: The computer works with kernel Ubuntu 4.15.0-112.113-generic 4.15.18. If I update to linux-image-5.4.0-47-generic 5.4.0-47.51 - it freezes. I tried the procedure "https://wiki.ubuntu.com/DebuggingKernelBoot; it freezes after Ctrl+x To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1895458/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1895563] Re: Kernel Oops: Rsyncing to bcache device w/o backing cache kernel panic
I'll test the 5.8 kernel this weekend. I'll upload a couple of tarballs next. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1895563 Title: Kernel Oops: Rsyncing to bcache device w/o backing cache kernel panic Status in linux package in Ubuntu: Confirmed Bug description: Platform details: 1) version.log attached 2) lspci-vnvn.log attached 3) lsb_release -rd Description:Ubuntu 18.04.5 LTS Release:18.04 4) apt-cache policy bcache-tools bcache-tools: Installed: 1.0.8-2ubuntu0.18.04.1 Candidate: 1.0.8-2ubuntu0.18.04.1 Version table: *** 1.0.8-2ubuntu0.18.04.1 500 500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 1.0.8-2build1 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages 5) uname -a: Linux timber4 4.15.0-117-generic #118-Ubuntu SMP Fri Sep 4 20:02:41 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux Short problem description: Rsyncing from a 1.4TB home dir to a an new filesystem on a bcache device without an attached cache eventually results in kernel panic. What I expected to happen: no kernel panic. Long problem description: 1) Devices / Filesystems: bfd01: 8*4TB configured as RAID6 using md LVM2 volume group. bfd02: 8*4TB configured as RAID6 using Dell PERC H810 LVM2 volume group. The tree contains 1069685 files / dirs. 2) Steps to reproduce: # Make the device, format and mount it make-bcache -B /dev/vg-bfd02/delme01_bc mkfs.xfs -f -L delme01bc /dev/bcache0 mount /dev/bcache0 /dev/bfd02/delme01bc # Rsync flags="-a --delete" ; info_cmd="--info=progress2" ; excludes=""; src=/mnt/bfd01/delme01 ; tgt=/mnt/bfd02/delme01bc/ ; time rsync $flags $info_cmd $excludes $src/ $tgt/ ... # eventually kernel panic Using incremental rsync it will kernel panic after reading about 21GB. # If instead I use non-incremental rsync it will kernel panic after reading about 1.2-1.3TB. flags="--no-inc-recursive -ax -HAXS --delete" ; info_cmd="--info=progress2" ; excludes=""; ... # eventually kernel panic Additional detail: 1) I was *not* able to reproduce if bfd01/delm01bc was a target and bfd02 was the source e.g. # Rsync flags="-a --delete" ; info_cmd="--info=progress2" ; excludes=""; src=/mnt/bfd02/delme01 ; tgt=/mnt/bfd01/delme01bc/ ; time rsync $flags $info_cmd $excludes $src/ $tgt/ ... # rsync completes successfully 2) I was *not* able to reproduce if I attached and then detached a cache set: ceho 'd3b93488-714e-4efa-af94-cd80fd2db11f' > /sys/block/bcache0/bcache/attach echo 1 > /sys/block/bcache0/bcache/detach ... time rsync $flags $info_cmd $excludes $src/ $tgt/ ... # rsync completes successfully I have 11 compressed kernel crash dumps. I will upload 3 after filing this. Let me know if you want the other 8. ProblemType: KernelCrash DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-117-generic 4.15.0-117.118 ProcVersionSignature: Ubuntu 4.15.0-117.118-generic 4.15.18 Uname: Linux 4.15.0-117-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Sep 13 12:53 seq crw-rw 1 root audio 116, 33 Sep 13 12:53 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.17 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Sat Sep 12 09:51:37 2020 HibernationDevice: RESUME=none IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: Dell Inc. PowerEdge R620 PciMultimedia: ProcFB: 0 mgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-117-generic root=UUID=de68d15b-3948-4666-9bc5-5cbecc83971c ro maybe-ubiquity crashkernel=512M-:512M RelatedPackageVersions: linux-restricted-modules-4.15.0-117-generic N/A linux-backports-modules-4.15.0-117-generic N/A linux-firmware 1.173.19 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/06/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.9.0 dmi.board.name: 0KCKR5 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.9.0:bd12/06/2019:svnDellInc.:pnPowerEdgeR620:pvr:rvnDellInc.:rn0KCKR5:rvrA00:cvnDellInc.:ct23:cvr: dmi.product.name: PowerEdge R620 dmi.sys.vendor: Dell Inc. --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Sep 13 12:53 seq crw-rw 1 root audio 116, 33 Sep 13
[Kernel-packages] [Bug 1895526] Re: ocfs2 file system no longer write - "disk full" despite lots of free space
Hi ~richard-from-davel and ~marco-zannoni, Could you please test kernel 5.4.0-48, just released to focal-updates a few hours ago and confirm it that helps? It has fixes for two of the four patches introduced between 5.4.0-42 and 5.4.0-45/-47 (reported to be good/bad versions.) Thanks, Mauricio Details: --- Per comment #12, good/bad version is 5.4.0-42/-47 Per comment #9, bad version is early 5.4.0-45. $ git log Ubuntu-5.4.0-42.46..Ubuntu-5.4.0-47.51 --format='commit %s%n%b' -- fs/ocfs2/ | grep ^commit commit ocfs2: fix panic on nfs server over ocfs2 commit e5a15e17a78d58f933d17cafedfcf7486a29f5b4 upstream. commit ocfs2: fix value of OCFS2_INVALID_SLOT commit 9277f8334ffc719fe922d776444d6e4e884dbf30 upstream. commit ocfs2: load global_inode_alloc commit 7569d3c754e452769a5747eeeba488179e38a5da upstream. commit ocfs2: avoid inode removal while nfsd is accessing it commit 4cd9973f9ff69e37dd0ba2bd6e6423f8179c329a upstream. Which is the same between 5.4.0-42 to 5.4.0-45. Looking at the upstream linux git tree, two of the four commits mentioned have Fixes: tag (ie, had issues fixed.) $ git-grep-commit e5a15e17a78d58f933d17cafedfcf7486a29f5b4 $ git-grep-commit 9277f8334ffc719fe922d776444d6e4e884dbf30 38d51b2dd171 ocfs2: change slot number type s16 to u16 $ git-grep-commit 7569d3c754e452769a5747eeeba488179e38a5da $ git-grep-commit 4cd9973f9ff69e37dd0ba2bd6e6423f8179c329a 57c720d4144a ocfs2: fix unbalanced locking And looking back into Focal's git tree, fortunately those 2 patches are already included in 5.4.0-48: $ git log --oneline Ubuntu-5.4.0-47.51..origin/master-next -- fs/ocfs2/ 44c9715a99ad ocfs2: change slot number type s16 to u16 5fcff07bd0be ocfs2: fix unbalanced locking $ git describe --contains 44c9715a99ad 5fcff07bd0be Ubuntu-5.4.0-48.52~125 Ubuntu-5.4.0-48.52~238 Hopefully both are sufficient to fix these issues, let's see. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1895526 Title: ocfs2 file system no longer write - "disk full" despite lots of free space Status in linux package in Ubuntu: Incomplete Status in ocfs2-tools package in Ubuntu: Confirmed Bug description: Fairly new server on Ubuntu 20.04.1 LTS, 5.4.0-47-generic kernel, DRBD device across 2 sites with one server in each site, ocfs2 filesystem on DRBD device, shared to local network using Samba (and also Samba-AD-DC for network). All packages from "normal" Ubuntu repositories. ocfs2-tools is Installed: 1.8.6-2ubuntu1. The filesystem is around 3.3 TB. Stored data amounted to 24% of this filesystem. Recent updates applied and server restarted Wed 9th Sept after which staff started reporting inability to save to server shares. Checked Samba settings as Windows error messages were at first showing permission issues, but following various checks no wrong Samba settings were found so restarted their server after which the errors were "no space left on disk". Checked on the server terminal and couldn't even "touch" an empty file but got "no space left on disk". Found an article describing limitations caused by ocfs2 cluster size, so copied all data out to a backup machine, recreated the ocfs2 file system using mkfs.ocfs2 -C 64K /dev/drbd0 but again the "no disk space" error keeps happening despite this now being an empty file system. Perhaps it wasn't a cluster size problem in the first instance. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ocfs2-tools 1.8.6-2ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-47.51-generic 5.4.55 Uname: Linux 5.4.0-47-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: pass Date: Mon Sep 14 12:23:35 2020 InstallationDate: Installed on 2020-05-06 (130 days ago) InstallationMedia: Ubuntu-Server 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ocfs2-tools UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1895526/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1895458] Re: Computer freezes on kernel 5, works on kernel 4
Interesting. For that you can add 'dis_ucode_ldr' in GRUB_CMDLINE_LINUX_DEFAULT in /etc/default/grub. Then run 'sudo update-grub', and confirm the change with 'grep dis_ucode_ldr /boot/grub/grub.cfg'. You should see non-recovery lines w/ that option as well. Could you please upload /proc/cpuinfo with the 4.15 kernel (without that option), and 5.4 kernel (with that option, of course)? For example, $ cat /proc/cpuinfo > cpuinfo-4.15 # similarly for 5.4 when booted. Also, please provide the output of: $ dpkg -s intel-microcode | grep Version Thanks, Mauricio -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1895458 Title: Computer freezes on kernel 5, works on kernel 4 Status in linux package in Ubuntu: Confirmed Bug description: The computer works with kernel Ubuntu 4.15.0-112.113-generic 4.15.18. If I update to linux-image-5.4.0-47-generic 5.4.0-47.51 - it freezes. I tried the procedure "https://wiki.ubuntu.com/DebuggingKernelBoot; it freezes after Ctrl+x To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1895458/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1894780] Re: Oops and hang when starting LVM snapshots on 5.4.0-47
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- focal' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1894780 Title: Oops and hang when starting LVM snapshots on 5.4.0-47 Status in linux package in Ubuntu: Confirmed Status in linux source package in Focal: Fix Committed Bug description: [Impact] kmemcaches will fail to be created after they have just been removed but not completely ripped out. This will cause some drivers (like lvm snapshots) to properly work and cause kernel traces to go on the logs. [Test case] See comment #9. [Regression potential] The fix reverts a commit, so we go back to a state of a previously released kernel, where a leak was possible. The regression here, though, is better than the impact that will also lead to a different leak and prevent users from correctly using LVM snapshots. = One of my bionic servers with HWE 5.4.0 hangs on boot (apparently while starting LVM snapshots) after upgrading from Linux 5.4.0-42 to 5.4.0-47, with the following trace: [ 29.126292] kobject_add_internal failed for :a-152 with -EEXIST, don't try to register things with the same name in the same directory. [ 29.138854] BUG: kernel NULL pointer dereference, address: 0020 [ 29.145977] #PF: supervisor read access in kernel mode [ 29.145979] #PF: error_code(0x) - not-present page [ 29.145981] PGD 0 P4D 0 [ 29.158800] Oops: [#1] SMP NOPTI [ 29.162468] CPU: 6 PID: 2532 Comm: lvm Not tainted 5.4.0-46-generic #50~18.04.1-Ubuntu [ 29.170378] Hardware name: Supermicro AS -2023US-TR4/H11DSU-iN, BIOS 1.3 07/15/2019 [ 29.178038] RIP: 0010:free_percpu+0x120/0x1f0 [ 29.183786] Code: 43 64 48 01 d0 49 39 c4 0f 83 71 ff ff ff 65 8b 05 a5 4e bc 58 48 8b 15 0e 4e 20 01 48 98 48 8b 3c c2 4c 01 e7 e8 f0 97 02 00 <48> 8b 58 20 48 8b 53 38 e9 48 ff ff ff f3 c3 48 8b 43 38 48 89 45 [ 29.202530] RSP: 0018:a2f69c3d38e8 EFLAGS: 00010046 [ 29.209204] RAX: RBX: 92202ff397c0 RCX: a880a000 [ 29.216336] RDX: cf35c0f24f2cc3c0 RSI: 43817c451b92afcb RDI: [ 29.223469] RBP: a2f69c3d3918 R08: R09: a74a5300 [ 29.230609] R10: a2f69c3d3820 R11: R12: cf35c0f24f14c3c0 [ 29.237745] R13: cf362fb2a054c3c0 R14: 0287 R15: 0008 [ 29.244878] FS: 7f93a04b0900() GS:913faed8() knlGS: [ 29.252961] CS: 0010 DS: ES: CR0: 80050033 [ 29.258707] CR2: 0020 CR3: 003fa9d9 CR4: 003406e0 [ 29.265883] Call Trace: [ 29.268346] __kmem_cache_release+0x1a/0x30 [ 29.273913] __kmem_cache_create+0x4f9/0x550 [ 29.278192] ? __kmalloc_node+0x1eb/0x320 [ 29.282205] ? kvmalloc_node+0x31/0x80 [ 29.285962] create_cache+0x120/0x1f0 [ 29.291003] kmem_cache_create_usercopy+0x17d/0x270 [ 29.295882] kmem_cache_create+0x16/0x20 [ 29.300152] dm_bufio_client_create+0x1af/0x3f0 [dm_bufio] [ 29.305644] ? snapshot_map+0x5e0/0x5e0 [dm_snapshot] [ 29.310693] persistent_read_metadata+0x1ed/0x500 [dm_snapshot] [ 29.316627] ? _cond_resched+0x19/0x40 [ 29.320384] snapshot_ctr+0x79e/0x910 [dm_snapshot] [ 29.325276] dm_table_add_target+0x18d/0x370 [ 29.329552] table_load+0x12a/0x370 [ 29.333045] ctl_ioctl+0x1e2/0x590 [ 29.336450] ? retrieve_status+0x1c0/0x1c0 [ 29.340551] dm_ctl_ioctl+0xe/0x20 [ 29.343958] do_vfs_ioctl+0xa9/0x640 [ 29.347547] ? ksys_semctl.constprop.19+0xf7/0x190 [ 29.352337] ksys_ioctl+0x75/0x80 [ 29.355663] __x64_sys_ioctl+0x1a/0x20 [ 29.359421] do_syscall_64+0x57/0x190 [ 29.363094] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [ 29.368144] RIP: 0033:0x7f939f0286d7 [ 29.371732] Code: b3 66 90 48 8b 05 b1 47 2d 00 64 c7 00 26 00 00 00 48 c7 c0 ff ff ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 b8 10 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d 81 47 2d 00 f7 d8 64 89 01 48 [ 29.390478] RSP: 002b:7ffe918df168 EFLAGS: 0202 ORIG_RAX: 0010
[Kernel-packages] [Bug 1889446] Re: DELL LATITUDE 5491 touchscreen doesn't work
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- focal' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1889446 Title: DELL LATITUDE 5491 touchscreen doesn't work Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Fix Committed Status in linux source package in Bionic: Fix Committed Status in linux source package in Focal: Fix Committed Bug description: I will really appreciate any help like said in summary my touchscreen doesnt work on my dell lattitude 5491 with a I5-8400H cpu. Any idea ? ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-42-generic 5.4.0-42.46 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ying 1977 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Jul 29 18:45:20 2020 InstallationDate: Installed on 2020-07-29 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Dell Inc. Latitude 5491 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-42-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-42-generic N/A linux-backports-modules-5.4.0-42-generic N/A linux-firmware1.187.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/25/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.12.0 dmi.board.name: 0VK7YF dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.12.0:bd02/25/2020:svnDellInc.:pnLatitude5491:pvr:rvnDellInc.:rn0VK7YF:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Latitude dmi.product.name: Latitude 5491 dmi.product.sku: 0818 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1889446/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1892546] Re: Novalink (mkvterm command failure)
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- focal' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1892546 Title: Novalink (mkvterm command failure) Status in The Ubuntu-power-systems project: Fix Committed Status in linux package in Ubuntu: In Progress Status in linux source package in Xenial: Fix Committed Status in linux source package in Bionic: Fix Committed Status in linux source package in Focal: Fix Committed Status in linux source package in Groovy: In Progress Bug description: SRU Justification: [Impact] * drmgr command is failing while trying to open console for IBMi on PowerVM LPAR [Fix] * 63ffcbdad738 "tty: hvcs: Don't NULL tty->driver_data until hvcs_cleanup()" [Test Case] * Create a VM from PowerVC on a Novalink managed host. * Unmanage and manage the VM, this problem gets reproduced. * grep the logs for "drmgr" [Regression Potential] The regression can be considered as very low, since: * limited to the IBM Hypervisor Virtual Console Server. * patched kernel where shared and successfully tested by IBM. * the worse case, if the cleanup is broken a new opened connection might break. [Other] * The patch got upstream accepted. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1892546/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1875199] Re: [NUC8CCHK][HDA-Intel - HDA Intel PCH, playback] No sound at all
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- focal' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1875199 Title: [NUC8CCHK][HDA-Intel - HDA Intel PCH, playback] No sound at all Status in linux package in Ubuntu: Incomplete Status in linux source package in Focal: Fix Committed Bug description: No sound output. Only a 'Dummy' audio output device is listed in the Gnome Sound application. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rboerner 1205 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Apr 26 12:12:49 2020 InstallationDate: Installed on 2020-04-25 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rboerner 1205 F pulseaudio Symptom_PulsePlaybackTest: PulseAudio playback test failed Symptom_Type: No sound at all Title: [HDA-Intel - HDA Intel PCH, playback] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/25/2020 dmi.bios.vendor: Intel Corp. dmi.bios.version: CHAPLCEL.0048.2020.0225.1640 dmi.board.name: NUC8CCHB dmi.board.vendor: Intel Corporation dmi.board.version: K44767-502 dmi.chassis.type: 35 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnIntelCorp.:bvrCHAPLCEL.0048.2020.0225.1640:bd02/25/2020:svnIntel(R)ClientSystems:pnNUC8CCHK:pvrK44798-502:rvnIntelCorporation:rnNUC8CCHB:rvrK44767-502:cvnIntelCorporation:ct35:cvr2.0: dmi.product.family: CH dmi.product.name: NUC8CCHK dmi.product.sku: BKNUC8CCHKR dmi.product.version: K44798-502 dmi.sys.vendor: Intel(R) Client Systems --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rboerner 1215 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-04-25 (6 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Intel(R) Client Systems NUC8CCHK Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-28-generic root=UUID=afbb0f64-e729-46a8-82e4-a060e9e729c4 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 RelatedPackageVersions: linux-restricted-modules-5.4.0-28-generic N/A linux-backports-modules-5.4.0-28-generic N/A linux-firmware1.187 Tags: focal Uname: Linux 5.4.0-28-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: 02/25/2020 dmi.bios.vendor: Intel Corp. dmi.bios.version: CHAPLCEL.0048.2020.0225.1640 dmi.board.name: NUC8CCHB dmi.board.vendor: Intel Corporation dmi.board.version: K44767-502 dmi.chassis.type: 35 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnIntelCorp.:bvrCHAPLCEL.0048.2020.0225.1640:bd02/25/2020:svnIntel(R)ClientSystems:pnNUC8CCHK:pvrK44798-502:rvnIntelCorporation:rnNUC8CCHB:rvrK44767-502:cvnIntelCorporation:ct35:cvr2.0: dmi.product.family: CH dmi.product.name: NUC8CCHK dmi.product.sku: BKNUC8CCHKR dmi.product.version: K44798-502 dmi.sys.vendor: Intel(R) Client Systems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1875199/+subscriptions --
[Kernel-packages] [Bug 1893778] Re: [UBUNTU 20.04] zPCI device hot-plug during boot may result in unusable device
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- focal' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1893778 Title: [UBUNTU 20.04] zPCI device hot-plug during boot may result in unusable device Status in Ubuntu on IBM z Systems: Fix Committed Status in linux package in Ubuntu: Fix Released Status in linux source package in Focal: Fix Committed Status in linux source package in Groovy: Fix Released Bug description: SRU Justification: == [Impact] * If a PCI device (incl. virtio-pci) is hot-plugged during boot-up on s390x, it can be detected as an entry in CLP List PCI functions and via the hot-plug event. * (This is basically equivalent to boot time probing on other architectures.) * In such a case the hot-plug event will be stale, but Linux still tries to add and enable the device which leads to: * a) a duplicate entry in zPCI internal device list * b) an attempt to enable the device with a stale function handle * In case b) the device will be placed in error state which makes it unusable. [Fix] * b76fee1bc56c31a9d2a49592810eba30cc06d61a b76fee1bc56c "s390/pci: ignore stale configuration request event" [Test Case] * Setup an Ubuntu Server 20.04 (focal) Linux operating system on an IBM Z or LinuxONE III LPAR. * It's now easiest to test on KVM using virtio-pci (on s390x). * Start a test virtual machine: sudo virsh start * Attach and hotplug a virtio-pci device: sudo virsh attach-device hotplug_pci_block.xml * Where hotplug_pci_block.xml looks like: [Regression Potential] * The regression risk is moderate, since the modification is very limited and therefore manageable (additional if statement - two lines of code) and easily testable on KVM using virtio-pci. * The changes are in the zPCI event code, so in worst-case it can happen that the event handling get harmed which may break zPCI entirely, affecting all PCI devices incl. virtio-pci (on s390x). * A bug in PCI 'availability' handling also just lead to wrong states of PCI devices which make them unavailable, hence unusable. * Notice that zPCI is the s390x-specific PCI implementation, modifications here do not affect any other architecture. * And zPCI devices are less wide-spread compared to ccw devices on s390x. * On top a test kernel was build and made available for further testing atesting can be easily done with virtio-pci on KVM. [Other] * The fix/patch got upstream accepted with kernel v5.9-rc2. * But it landed already in groovy's proposed kernel 5.8 (Ubuntu-5.8.0-18.19), due to 'Groovy update: v5.8.4 upstream stable release' that is handled in LP 1893048. * Hence this fix/patch need to be applied to focal only. __ When a PCI device (including virtio-pci for which this is easiest to test) is hot-plugged while Linux is still booting, it can be detected as an entry in CLP List PCI Functions (basically equivalent to boot time probing on other architectures) and with the hot-plug event. In this case the hot-plug event will be stale but Linux still tried to add and enable the device leading a) to a duplicate entry in zPCI internal device list b) an attempt to enable the device witha stale function handle Part b) would lead to the device being place in the error state and make it unusable. This can most easily be reproduced using KVM and doing # sudo virsh start myguest && sudo virsh attach-device myguest hotplug_pci_block.xml Where hotplug_pci_block.xml looks like the following: The problem is fixed with the 3-line upstream commit b76fee1bc56c31a9d2a49592810eba30cc06d61a s390/pci: ignore stale configuration request event I also confirmed that as of the focal tag Ubuntu-5.4.0-46.50 this cherry-picks cleanly. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1893778/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help :
[Kernel-packages] [Bug 1887490] Re: Add/Backport EPYC-v3 and EPYC-Rome CPU model
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- focal' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1887490 Title: Add/Backport EPYC-v3 and EPYC-Rome CPU model Status in libvirt package in Ubuntu: Incomplete Status in linux package in Ubuntu: Invalid Status in qemu package in Ubuntu: Fix Released Status in libvirt source package in Focal: Incomplete Status in linux source package in Focal: Fix Committed Status in qemu source package in Focal: Incomplete Bug description: Qemu in focal has already support for most (except amd-stibp) flags of this model. Please backport the following patches: https://github.com/qemu/qemu/commit/a16e8dbc043720abcb37fc7dca313e720b4e0f0c https://github.com/qemu/qemu/commit/143c30d4d346831a09e59e9af45afdca0331e819 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1887490/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1895718] Re: Fix non-working NVMe after S3
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- focal' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.6 in Ubuntu. https://bugs.launchpad.net/bugs/1895718 Title: Fix non-working NVMe after S3 Status in HWE Next: New Status in linux package in Ubuntu: Confirmed Status in linux-oem-5.6 package in Ubuntu: Invalid Status in linux source package in Focal: Fix Committed Status in linux-oem-5.6 source package in Focal: Confirmed Status in linux source package in Groovy: Confirmed Status in linux-oem-5.6 source package in Groovy: Won't Fix Bug description: [Impact] KIOXIA NVMe has a 10% chance to stop working after S3. [Fix] Enable ACS quirk on Intel CML root port. [Test] With the patch applied, KIOXIA NVMe always works after S3. [Regression Potential] ACS works at hardware level, so I can't really assess the risk of regression. Since Intel confirmed CML also needs ACS quirk, we can only trust them. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1895718/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1893956] Re: Intel x710 LOMs do not work on Focal
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- focal' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1893956 Title: Intel x710 LOMs do not work on Focal Status in linux package in Ubuntu: Invalid Status in linux source package in Focal: Fix Committed Bug description: [IMPACT] The Intel x710-TM4 is one of the latest 10GbE controllers from intel using the i40e driver. This particular 4 port comes in a 2x2 arrangement: 2x SFP+ and 2x RJ-45. This card is enabled in 5.4 via the inbox version of the i40e driver, and hwinfo does show both sides of the card but the kernel only sees the two SFP+ ports and cannot address or use the two copper ports. These devices have up to 4 ports, but only two seem to work and this has been seen on at least two different systems using LOMs based on this. This is currently blocking certification for one of our hardware partners. [FIX] This list of Patches enables the latest X710 controller fully: * 3df5b9a6a9ec i40e: enable X710 support * d80a476f4a12 i40e: Fix LED blinking flow for X710T*L devices These are all clean cherry picks from 5.5 into 5.4 My tree with these can be found here: https://code.launchpad.net/~bladernr/ubuntu/+source/linux/+git/focal/+ref/1893956-update-i40e-intel-lom [TESTCASE] i40e should load successfully, all ports on Carlsville x710 LOM should be visible, configurable, and can pass traffic at full speed. Test kernels have been verified by the vendor reporting the issue that all network ports on the LOM are accessible and pass traffic at expected speeds. [REGRESSION RISK] Possible problem could be if the LED patch causes LEDs to not function correctly (or not at all) but the risk for this is pretty low. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1893956/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1896519] 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/1896519 Title: kworker consumes 80% of CPU Status in linux package in Ubuntu: Confirmed Bug description: Like yesterday I have noticed my CPU on Leonovo Thinkpad T590 laptop has starting to be consumed by kworker for 80% of 2-CPU 4-core processor. I also see fan works like crazy and "ejects" hot air non stop. This has never happened in my 6 months of having this new laptop. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-47-generic 5.4.0-47.51 ProcVersionSignature: Ubuntu 5.4.0-47.51-generic 5.4.55 Uname: Linux 5.4.0-47-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip Date: Mon Sep 21 19:29:32 2020 InstallationDate: Installed on 2019-10-23 (334 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) MachineType: LENOVO 20N4S06V00 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-47-generic root=UUID=5ae35a7d-8195-4867-8bb5-49ab3106da83 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-47-generic N/A linux-backports-modules-5.4.0-47-generic N/A linux-firmware1.187.3 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-08-14 (38 days ago) dmi.bios.date: 08/12/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N2IET91W (1.69 ) dmi.board.asset.tag: Not Available dmi.board.name: 20N4S06V00 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2IET91W(1.69):bd08/12/2020:svnLENOVO:pn20N4S06V00:pvrThinkPadT590:rvnLENOVO:rn20N4S06V00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T590 dmi.product.name: 20N4S06V00 dmi.product.sku: LENOVO_MT_20N4_BU_Think_FM_ThinkPad T590 dmi.product.version: ThinkPad T590 dmi.sys.vendor: LENOVO modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2020-04-29T17:08:03.553351 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1896519/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1896521] Status changed to Confirmed
This change was made by a bot.
** Changed in: linux (Ubuntu)
Status: New => Confirmed
** Tags added: yakkety
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1896521
Title:
Mounting a logical volume on a Drobo 5D will hang
Status in linux package in Ubuntu:
Confirmed
Bug description:
Given these logical volumes on a Drobo 5D mounting will result in a
hang:
root@atx1:/var/log# lvs vg-drobo
LV VG Attr LSizePool Origin Data% Meta% Move Log
Cpy%Sync Convert
encrypted vg-drobo -wi-a- 1000.00g
persistent vg-drobo -wi-a- 600.00g
timber vg-drobo -wi-ao1.50t
timber2vg-drobo -wi-ao1.00t
root@atx1:/var/log# mount /dev/vg-drobo/timber /mnt/drobo-timber/
# hangs
I expect the mount to succeed without hanging.
This bug is not present in 16.04 / 16.04.1 (latest is
linux-4.4.0-189-generic).
Release bisection revealed it showed up in u16.04.2:
linux-4.8.0-36-generic from LiveCD.
I found it when finally upgrading a 16.04 host which was using 4.4
kernel to 18.04 which uses 4.15 (LTS) / 5.4 (HWE) kernels.
After further commit bisection I found the commit which introduced
this behavior is: https://git.launchpad.net/~ubuntu-
kernel/ubuntu/+source/linux/+git/bionic/commit/?id=5b91dfe187bbe3a8116432016375f39fff91a237
$ git show 5b91dfe187bb
Mon Apr 18 13:09:10 2016 +0300 5b91dfe187bb usb: storage: scsiglue: limit
USB3 devices to 2048 sectors [Felipe Balbi]
diff --git a/drivers/usb/storage/scsiglue.c b/drivers/usb/storage/scsiglue.c
index 9da1fb3d0ff4..88920142e375 100644
--- a/drivers/usb/storage/scsiglue.c
+++ b/drivers/usb/storage/scsiglue.c
@@ -133,6 +133,11 @@ static int slave_configure(struct scsi_device *sdev)
* let the queue segment size sort out the real limit.
*/
blk_queue_max_hw_sectors(sdev->request_queue, 0x7F);
+ } else if (us->pusb_dev->speed >= USB_SPEED_SUPER) {
+ /* USB3 devices will be limited to 2048 sectors. This gives us
+* better throughput on most devices.
+*/
+ blk_queue_max_hw_sectors(sdev->request_queue, 2048);
}
/* Some USB host controllers can't do DMA; they have to use PIO.
I built kernels with this change commented out and confirmed I can
successfully mount the LV from the Drobo using 4.8 and 4.15 kernels.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-117-generic 4.15.0-117.118
ProcVersionSignature: Ubuntu 4.15.0-117.118-generic 4.15.18
Uname: Linux 4.15.0-117-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.17
Architecture: amd64
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq',
'/dev/snd/timer'] failed with exit code 1:
CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211
not found.
Date: Mon Sep 21 12:37:39 2020
HibernationDevice:
#RESUME=UUID=64794be3-24a0-49f9-9239-371624a3d193
RESUME=none
InstallationDate: Installed on 2020-09-20 (0 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
IwConfig:
enp0s31f6 no wireless extensions.
lono wireless extensions.
MachineType: System manufacturer System Product Name
ProcFB: 0 VESA VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-117-generic
root=/dev/mapper/vg--ssd2tb-u18040 ro
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
linux-restricted-modules-4.15.0-117-generic N/A
linux-backports-modules-4.15.0-117-generic N/A
linux-firmware 1.173.19
RfKill:
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/15/2018
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 3802
dmi.board.asset.tag: Default string
dmi.board.name: MAXIMUS VIII RANGER
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvr3802:bd03/15/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnMAXIMUSVIIIRANGER:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer
To manage
[Kernel-packages] [Bug 1895458] Re: Computer freezes on kernel 5, works on kernel 4
Good catch Mauricio! 1. "nomodeset" did not help. 2. "dis_ucode_ldr" succeed. The logs after the successful boot are attached. What can I do to make the boot use "dis_ucode_ldr" by default? ** Attachment added: "var_log3.tar.gz" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1895458/+attachment/5413022/+files/var_log3.tar.gz -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1895458 Title: Computer freezes on kernel 5, works on kernel 4 Status in linux package in Ubuntu: Confirmed Bug description: The computer works with kernel Ubuntu 4.15.0-112.113-generic 4.15.18. If I update to linux-image-5.4.0-47-generic 5.4.0-47.51 - it freezes. I tried the procedure "https://wiki.ubuntu.com/DebuggingKernelBoot; it freezes after Ctrl+x To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1895458/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1896521] [NEW] Mounting a logical volume on a Drobo 5D will hang
Public bug reported:
Given these logical volumes on a Drobo 5D mounting will result in a
hang:
root@atx1:/var/log# lvs vg-drobo
LV VG Attr LSizePool Origin Data% Meta% Move Log
Cpy%Sync Convert
encrypted vg-drobo -wi-a- 1000.00g
persistent vg-drobo -wi-a- 600.00g
timber vg-drobo -wi-ao1.50t
timber2vg-drobo -wi-ao1.00t
root@atx1:/var/log# mount /dev/vg-drobo/timber /mnt/drobo-timber/
# hangs
I expect the mount to succeed without hanging.
This bug is not present in 16.04 / 16.04.1 (latest is
linux-4.4.0-189-generic).
Release bisection revealed it showed up in u16.04.2:
linux-4.8.0-36-generic from LiveCD.
I found it when finally upgrading a 16.04 host which was using 4.4
kernel to 18.04 which uses 4.15 (LTS) / 5.4 (HWE) kernels.
After further commit bisection I found the commit which introduced this
behavior is: https://git.launchpad.net/~ubuntu-
kernel/ubuntu/+source/linux/+git/bionic/commit/?id=5b91dfe187bbe3a8116432016375f39fff91a237
$ git show 5b91dfe187bb
Mon Apr 18 13:09:10 2016 +0300 5b91dfe187bb usb: storage: scsiglue: limit USB3
devices to 2048 sectors [Felipe Balbi]
diff --git a/drivers/usb/storage/scsiglue.c b/drivers/usb/storage/scsiglue.c
index 9da1fb3d0ff4..88920142e375 100644
--- a/drivers/usb/storage/scsiglue.c
+++ b/drivers/usb/storage/scsiglue.c
@@ -133,6 +133,11 @@ static int slave_configure(struct scsi_device *sdev)
* let the queue segment size sort out the real limit.
*/
blk_queue_max_hw_sectors(sdev->request_queue, 0x7F);
+ } else if (us->pusb_dev->speed >= USB_SPEED_SUPER) {
+ /* USB3 devices will be limited to 2048 sectors. This gives us
+* better throughput on most devices.
+*/
+ blk_queue_max_hw_sectors(sdev->request_queue, 2048);
}
/* Some USB host controllers can't do DMA; they have to use PIO.
I built kernels with this change commented out and confirmed I can
successfully mount the LV from the Drobo using 4.8 and 4.15 kernels.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-117-generic 4.15.0-117.118
ProcVersionSignature: Ubuntu 4.15.0-117.118-generic 4.15.18
Uname: Linux 4.15.0-117-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.17
Architecture: amd64
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq',
'/dev/snd/timer'] failed with exit code 1:
CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not
found.
Date: Mon Sep 21 12:37:39 2020
HibernationDevice:
#RESUME=UUID=64794be3-24a0-49f9-9239-371624a3d193
RESUME=none
InstallationDate: Installed on 2020-09-20 (0 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
IwConfig:
enp0s31f6 no wireless extensions.
lono wireless extensions.
MachineType: System manufacturer System Product Name
ProcFB: 0 VESA VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-117-generic
root=/dev/mapper/vg--ssd2tb-u18040 ro
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
linux-restricted-modules-4.15.0-117-generic N/A
linux-backports-modules-4.15.0-117-generic N/A
linux-firmware 1.173.19
RfKill:
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/15/2018
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 3802
dmi.board.asset.tag: Default string
dmi.board.name: MAXIMUS VIII RANGER
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvr3802:bd03/15/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnMAXIMUSVIIIRANGER:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug bionic
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1896521
Title:
Mounting a logical volume on a Drobo 5D will hang
Status in linux package in Ubuntu:
New
Bug description:
Given these logical volumes on a Drobo 5D mounting will result in a
hang:
root@atx1:/var/log# lvs vg-drobo
LV VG Attr LSizePool Origin Data%
[Kernel-packages] [Bug 1896521] Re: Mounting a logical volume on a Drobo 5D will hang
** Attachment added: "syslog entries showing several "blocked for more than 120
seconds" errors"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1896521/+attachment/5413021/+files/syslog
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1896521
Title:
Mounting a logical volume on a Drobo 5D will hang
Status in linux package in Ubuntu:
New
Bug description:
Given these logical volumes on a Drobo 5D mounting will result in a
hang:
root@atx1:/var/log# lvs vg-drobo
LV VG Attr LSizePool Origin Data% Meta% Move Log
Cpy%Sync Convert
encrypted vg-drobo -wi-a- 1000.00g
persistent vg-drobo -wi-a- 600.00g
timber vg-drobo -wi-ao1.50t
timber2vg-drobo -wi-ao1.00t
root@atx1:/var/log# mount /dev/vg-drobo/timber /mnt/drobo-timber/
# hangs
I expect the mount to succeed without hanging.
This bug is not present in 16.04 / 16.04.1 (latest is
linux-4.4.0-189-generic).
Release bisection revealed it showed up in u16.04.2:
linux-4.8.0-36-generic from LiveCD.
I found it when finally upgrading a 16.04 host which was using 4.4
kernel to 18.04 which uses 4.15 (LTS) / 5.4 (HWE) kernels.
After further commit bisection I found the commit which introduced
this behavior is: https://git.launchpad.net/~ubuntu-
kernel/ubuntu/+source/linux/+git/bionic/commit/?id=5b91dfe187bbe3a8116432016375f39fff91a237
$ git show 5b91dfe187bb
Mon Apr 18 13:09:10 2016 +0300 5b91dfe187bb usb: storage: scsiglue: limit
USB3 devices to 2048 sectors [Felipe Balbi]
diff --git a/drivers/usb/storage/scsiglue.c b/drivers/usb/storage/scsiglue.c
index 9da1fb3d0ff4..88920142e375 100644
--- a/drivers/usb/storage/scsiglue.c
+++ b/drivers/usb/storage/scsiglue.c
@@ -133,6 +133,11 @@ static int slave_configure(struct scsi_device *sdev)
* let the queue segment size sort out the real limit.
*/
blk_queue_max_hw_sectors(sdev->request_queue, 0x7F);
+ } else if (us->pusb_dev->speed >= USB_SPEED_SUPER) {
+ /* USB3 devices will be limited to 2048 sectors. This gives us
+* better throughput on most devices.
+*/
+ blk_queue_max_hw_sectors(sdev->request_queue, 2048);
}
/* Some USB host controllers can't do DMA; they have to use PIO.
I built kernels with this change commented out and confirmed I can
successfully mount the LV from the Drobo using 4.8 and 4.15 kernels.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-117-generic 4.15.0-117.118
ProcVersionSignature: Ubuntu 4.15.0-117.118-generic 4.15.18
Uname: Linux 4.15.0-117-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.17
Architecture: amd64
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq',
'/dev/snd/timer'] failed with exit code 1:
CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211
not found.
Date: Mon Sep 21 12:37:39 2020
HibernationDevice:
#RESUME=UUID=64794be3-24a0-49f9-9239-371624a3d193
RESUME=none
InstallationDate: Installed on 2020-09-20 (0 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
IwConfig:
enp0s31f6 no wireless extensions.
lono wireless extensions.
MachineType: System manufacturer System Product Name
ProcFB: 0 VESA VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-117-generic
root=/dev/mapper/vg--ssd2tb-u18040 ro
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
linux-restricted-modules-4.15.0-117-generic N/A
linux-backports-modules-4.15.0-117-generic N/A
linux-firmware 1.173.19
RfKill:
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/15/2018
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 3802
dmi.board.asset.tag: Default string
dmi.board.name: MAXIMUS VIII RANGER
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvr3802:bd03/15/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnMAXIMUSVIIIRANGER:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: System Product Name
[Kernel-packages] [Bug 1896008] Re: linux-libc-dev in proposed cause seccomp_bpf from seccomp in ubuntu_kernel_selftests to fail on F-oem-5.6
So, the test is running with the newer definition as it is picked up from linux-libc-dev. But the kernel (linux-oem-5.6, in this case) doesn't know about it. So it fails. However, any binaries out there would be using the old definition, which the linux-oem-5.6 should accept just fine. I guess we will be stuck with this double definition forever as "we don't break userspace ABI *ever*" *coff*. IMHO, it's just fine leaving this for next cycle. But pick it up, cause we will start seeing binaries out there using the new definition. Cascardo. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.6 in Ubuntu. https://bugs.launchpad.net/bugs/1896008 Title: linux-libc-dev in proposed cause seccomp_bpf from seccomp in ubuntu_kernel_selftests to fail on F-oem-5.6 Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Confirmed Status in linux-oem-5.6 package in Ubuntu: New Bug description: Issue found on node glameow with 5.6.0-1028.28 # [ RUN ] global.user_notification_kill_in_middle # [ FAIL ] global.user_notification_kill_in_middle 74 / 75 tests passed. Since this might be the first time we're testing Focal OEM kernel with this dedicated node glameow, further investigation is needed. --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Sep 18 06:34 seq crw-rw 1 root audio 116, 33 Sep 18 06:34 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: HP ProLiant DL360 Gen9 Package: linux (not installed) PciMultimedia: ProcFB: 0 mgag200drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.6.0-1028-oem root=UUID=6422cfdd-2a69-4c0b-9784-6809a77ab980 ro console=ttyS0,96008n1 ProcVersionSignature: User Name 5.6.0-1028.28-oem 5.6.19 RelatedPackageVersions: linux-restricted-modules-5.6.0-1028-oem N/A linux-backports-modules-5.6.0-1028-oem N/A linux-firmware 1.187.3 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal uec-images Uname: Linux 5.6.0-1028-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip floppy lxd netdev plugdev sudo video _MarkForUpload: True dmi.bios.date: 04/25/2017 dmi.bios.vendor: HP dmi.bios.version: P89 dmi.board.name: ProLiant DL360 Gen9 dmi.board.vendor: HP dmi.chassis.type: 23 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrP89:bd04/25/2017:svnHP:pnProLiantDL360Gen9:pvr:rvnHP:rnProLiantDL360Gen9:rvr:cvnHP:ct23:cvr: dmi.product.family: ProLiant dmi.product.name: ProLiant DL360 Gen9 dmi.product.sku: 780020-S01 dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1896008/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1896519] [NEW] kworker consumes 80% of CPU
Public bug reported: Like yesterday I have noticed my CPU on Leonovo Thinkpad T590 laptop has starting to be consumed by kworker for 80% of 2-CPU 4-core processor. I also see fan works like crazy and "ejects" hot air non stop. This has never happened in my 6 months of having this new laptop. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-47-generic 5.4.0-47.51 ProcVersionSignature: Ubuntu 5.4.0-47.51-generic 5.4.55 Uname: Linux 5.4.0-47-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip Date: Mon Sep 21 19:29:32 2020 InstallationDate: Installed on 2019-10-23 (334 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) MachineType: LENOVO 20N4S06V00 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-47-generic root=UUID=5ae35a7d-8195-4867-8bb5-49ab3106da83 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-47-generic N/A linux-backports-modules-5.4.0-47-generic N/A linux-firmware1.187.3 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-08-14 (38 days ago) dmi.bios.date: 08/12/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N2IET91W (1.69 ) dmi.board.asset.tag: Not Available dmi.board.name: 20N4S06V00 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2IET91W(1.69):bd08/12/2020:svnLENOVO:pn20N4S06V00:pvrThinkPadT590:rvnLENOVO:rn20N4S06V00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T590 dmi.product.name: 20N4S06V00 dmi.product.sku: LENOVO_MT_20N4_BU_Think_FM_ThinkPad T590 dmi.product.version: ThinkPad T590 dmi.sys.vendor: LENOVO modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2020-04-29T17:08:03.553351 ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1896519 Title: kworker consumes 80% of CPU Status in linux package in Ubuntu: New Bug description: Like yesterday I have noticed my CPU on Leonovo Thinkpad T590 laptop has starting to be consumed by kworker for 80% of 2-CPU 4-core processor. I also see fan works like crazy and "ejects" hot air non stop. This has never happened in my 6 months of having this new laptop. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-47-generic 5.4.0-47.51 ProcVersionSignature: Ubuntu 5.4.0-47.51-generic 5.4.55 Uname: Linux 5.4.0-47-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip Date: Mon Sep 21 19:29:32 2020 InstallationDate: Installed on 2019-10-23 (334 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) MachineType: LENOVO 20N4S06V00 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-47-generic root=UUID=5ae35a7d-8195-4867-8bb5-49ab3106da83 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-47-generic N/A linux-backports-modules-5.4.0-47-generic N/A linux-firmware1.187.3 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-08-14 (38 days ago) dmi.bios.date: 08/12/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N2IET91W (1.69 ) dmi.board.asset.tag: Not Available dmi.board.name: 20N4S06V00 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2IET91W(1.69):bd08/12/2020:svnLENOVO:pn20N4S06V00:pvrThinkPadT590:rvnLENOVO:rn20N4S06V00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T590 dmi.product.name: 20N4S06V00 dmi.product.sku: LENOVO_MT_20N4_BU_Think_FM_ThinkPad T590 dmi.product.version: ThinkPad T590 dmi.sys.vendor: LENOVO modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2020-04-29T17:08:03.553351 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1896519/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1895458] Re: Computer freezes on kernel 5, works on kernel 4
Ok, so nothing yet on the screen seems to suggest either a graphics-related issue or a different, early problem. The successful test to boot into recovery mode provides a very good lead; thanks for coming up with that. These are the 3 kernel options added by the recovery mode, per the kern.log file you attached: 'recovery nomodeset dis_ucode_ldr' - nomodeset is graphics related, and - dis_ucode_ldr is processor microcode related, which runs very early. which supports that theory. So please try booting with either one of them, (please remove quiet and splash, no more earlyprintk nor ignore_loglevel.) I imagine that nomodeset is more likely to do the trick. If dis_ucode_ldr does it, there's something worse in it. If you need _both_, I'd be surprised, as they're not related. Thanks! Mauricio -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1895458 Title: Computer freezes on kernel 5, works on kernel 4 Status in linux package in Ubuntu: Confirmed Bug description: The computer works with kernel Ubuntu 4.15.0-112.113-generic 4.15.18. If I update to linux-image-5.4.0-47-generic 5.4.0-47.51 - it freezes. I tried the procedure "https://wiki.ubuntu.com/DebuggingKernelBoot; it freezes after Ctrl+x To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1895458/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1895458] Re: Computer freezes on kernel 5, works on kernel 4
Removing 'quiet splash' and adding 'earlyprintk=vga ignore_loglevel' changed nothing - no more info on the screen. Than I rebooted kernel 5.4.0-48 in recovery mode (Your system is currently running without video hardware acceleration) and I am attaching the var_log2.tar.gz ** Attachment added: "var_log2.tar.gz" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1895458/+attachment/5412983/+files/var_log2.tar.gz -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1895458 Title: Computer freezes on kernel 5, works on kernel 4 Status in linux package in Ubuntu: Confirmed Bug description: The computer works with kernel Ubuntu 4.15.0-112.113-generic 4.15.18. If I update to linux-image-5.4.0-47-generic 5.4.0-47.51 - it freezes. I tried the procedure "https://wiki.ubuntu.com/DebuggingKernelBoot; it freezes after Ctrl+x To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1895458/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1896350] Re: nbd locks system?
(The zero size problem mentioned above also occurs occasionally on ubuntu 18.04, and the workaround is to add a sleep in the user script after modprobe nbd, so that's really a separate problem.) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1896350 Title: nbd locks system? Status in linux package in Ubuntu: Confirmed Bug description: I'm trying to use nbd on ubuntu 20.04 like so: qemu-img create -f qcow2 foo.img 500M sudo modprobe nbd sudo qemu-nbd --disconnect /dev/nbd15 || true sudo qemu-nbd --connect=/dev/nbd15 --cache=writeback --format=qcow2 foo.img sudo mkfs.ext4 -L root -O "^64bit" -E nodiscard /dev/nbd15 sudo qemu-nbd --disconnect /dev/nbd15 It seems to work on some systems, but even on those systems, strange things show up in syslog, e.g. Sep 19 15:46:02 thinky kernel: [27042.757768] block nbd15: Possible stuck request dd2d7f93: control (read@135168,126976B). Runtime 450 seconds Sep 19 15:46:26 thinky kernel: [27067.333867] INFO: task systemd-udevd:17364 blocked for more than 241 seconds. and in kern.log, e.g. ... Sep 19 16:17:27 thinky kernel: [ 71.676026] Buffer I/O error on dev nbd15, logical block 7, async page read Sep 19 16:17:27 thinky kernel: [ 71.676049] blk_update_request: I/O error, dev nbd15, sector 0 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0 Sep 19 16:17:27 thinky kernel: [ 71.676051] Buffer I/O error on dev nbd15, logical block 0, async page read Sep 19 16:17:27 thinky kernel: [ 71.676061] blk_update_request: I/O error, dev nbd15, sector 1 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0 Sep 19 16:17:27 thinky kernel: [ 71.676063] Buffer I/O error on dev nbd15, logical block 1, async page read Sep 19 16:17:27 thinky kernel: [ 71.676147] ldm_validate_partition_table(): Disk read failed. Sep 19 16:17:27 thinky kernel: [ 71.676324] Dev nbd15: unable to read RDB block 0 Sep 19 16:17:27 thinky kernel: [ 71.676473] nbd15: unable to read partition table Sep 19 16:17:27 thinky kernel: [ 71.678340] nbd15: detected capacity change from 0 to 524288000 Sep 19 16:17:27 thinky kernel: [ 71.678536] ldm_validate_partition_table(): Disk read failed. Sep 19 16:17:27 thinky kernel: [ 71.678719] Dev nbd15: unable to read RDB block 0 Sep 19 16:17:27 thinky kernel: [ 71.678947] nbd15: unable to read partition table Sep 19 16:17:27 thinky kernel: [ 71.679985] ldm_validate_partition_table(): Disk read failed. Sep 19 16:17:27 thinky kernel: [ 71.680172] Dev nbd15: unable to read RDB block 0 Sep 19 16:17:27 thinky kernel: [ 71.680366] nbd15: unable to read partition table Sep 19 16:17:27 thinky kernel: [ 71.680647] block nbd15: Attempted send on invalid socket and the system seems to hang on reboot. Also, on another system (an up to date mac, running ubuntu 20.04 in virtualbox), the mkfs.ext4 fails, complaining the device is zero size. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-47-generic 5.4.0-47.51 ProcVersionSignature: Ubuntu 5.4.0-47.51-generic 5.4.55 Uname: Linux 5.4.0-47-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: dank 2948 F pulseaudio /dev/snd/controlC2: dank 2948 F pulseaudio /dev/snd/controlC0: dank 2948 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Sep 19 16:28:43 2020 HibernationDevice: RESUME=UUID=7aecd5d3-2f5b-4c07-8867-801e63868a0f InstallationDate: Installed on 2017-04-29 (1239 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: LENOVO ThinkServer TS140 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-47-generic root=UUID=ff9a24e4-277d-4baf-819b-826a33d5bb5e ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-47-generic N/A linux-backports-modules-5.4.0-47-generic N/A linux-firmware1.187.2 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-05-01 (141 days ago) dmi.bios.date: 09/19/2014 dmi.bios.vendor: LENOVO dmi.bios.version: FBKT99AUS dmi.board.name: ThinkServer TS140 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.type: 7 dmi.chassis.vendor: LENOVO dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnLENOVO:bvrFBKT99AUS:bd09/19/2014:svnLENOVO:pnThinkServerTS140:pvr70A4000HUX:rvnLENOVO:rnThinkServerTS140:rvrNotDefined:cvnLENOVO:ct7:cvrToBeFilledByO.E.M.: dmi.product.family: To be
[Kernel-packages] [Bug 1895458] Re: Computer freezes on kernel 5, works on kernel 4
Thanks. Ok, so there's nothing printed to console after grub loads the kernel and initramfs. The parameters in your grub config look good (kernel+initramfs+cmdline w/ root= and ro.) Could you please try without 'quiet splash' again, but add the options: 'earlyprintk=vga ignore_loglevel' ? That might print some early initialization messages. Thanks, Mauricio -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1895458 Title: Computer freezes on kernel 5, works on kernel 4 Status in linux package in Ubuntu: Confirmed Bug description: The computer works with kernel Ubuntu 4.15.0-112.113-generic 4.15.18. If I update to linux-image-5.4.0-47-generic 5.4.0-47.51 - it freezes. I tried the procedure "https://wiki.ubuntu.com/DebuggingKernelBoot; it freezes after Ctrl+x To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1895458/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1896504] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:
apport-collect 1896504
and then change the status of the bug to 'Confirmed'.
If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a comment stating that fact and change
the bug status to 'Confirmed'.
This change has been made by an automated script, maintained by the
Ubuntu Kernel Team.
** Changed in: linux (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1896504
Title:
tc/ebpf: unable to use BPF_FUNC_skb_change_head
Status in linux package in Ubuntu:
Incomplete
Bug description:
[Impact]
tc ebpf program that uses BPF_FUNC_skb_change_head are rejected.
This helper exists since linux v4.10, but it cannot be used until the the
upstream commit 6f3f65d80dac ("net: bpf: Allow TC programs to call
BPF_FUNC_skb_change_head"):
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=6f3f65d80dac
[Test Case]
Create a, ebpf program that uses this helper and load it with tc.
[Regression Potential]
The patch is trivial, the potential regressions are low.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1896504/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1896348] Re: wifi not working due to bcmwl-kernel-source
>From Apttermlog: Setting up bcmwl-kernel-source (6.30.223.271+bdcom-0ubuntu6) ... Loading new bcmwl-6.30.223.271+bdcom DKMS files... Building for 5.4.0-47-generic 5.8.0-18-generic Building for architecture x86_64 Building initial module for 5.4.0-47-generic ERROR (dkms apport): kernel package linux-headers-5.4.0-47-generic is not supported Error! Application of patch 0028-add-support-for-linux-5.6.patch failed. Check /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/ for more information. dpkg: error processing package bcmwl-kernel-source (--configure): installed bcmwl-kernel-source package post-installation script subprocess returned error exit status 6 ** Package changed: ubuntu-release-upgrader (Ubuntu) => bcmwl (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bcmwl in Ubuntu. https://bugs.launchpad.net/bugs/1896348 Title: wifi not working due to bcmwl-kernel-source Status in bcmwl package in Ubuntu: New Bug description: wifi not working installed bcmwl-kernel-source package post-installation script subprocess returned error exit status 6 Errors were encountered while processing: bcmwl-kernel-source E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: ubuntu-release-upgrader-core 1:20.10.11 ProcVersionSignature: Ubuntu 5.8.0-18.19-generic 5.8.4 Uname: Linux 5.8.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu45 Architecture: amd64 CasperMD5CheckResult: skip CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Sat Sep 19 18:07:20 2020 InstallationDate: Installed on 2020-09-18 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: Upgraded to groovy on 2020-09-19 (0 days ago) VarLogDistupgradeXorgFixuplog: INFO:root:/usr/bin/do-release-upgrade running INFO:root:No xorg.conf, exiting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1896348/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1896504] [NEW] tc/ebpf: unable to use BPF_FUNC_skb_change_head
Public bug reported:
[Impact]
tc ebpf program that uses BPF_FUNC_skb_change_head are rejected.
This helper exists since linux v4.10, but it cannot be used until the the
upstream commit 6f3f65d80dac ("net: bpf: Allow TC programs to call
BPF_FUNC_skb_change_head"):
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=6f3f65d80dac
[Test Case]
Create a, ebpf program that uses this helper and load it with tc.
[Regression Potential]
The patch is trivial, the potential regressions are low.
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Description changed:
-
[Impact]
tc ebpf program that uses BPF_FUNC_skb_change_head are rejected.
- This helper exists since linux v4.10, but it cannot be used until the the
upstream commit f65d80dac ("net: bpf: Allow TC programs to call
BPF_FUNC_skb_change_head"):
+ This helper exists since linux v4.10, but it cannot be used until the the
upstream commit 6f3f65d80dac ("net: bpf: Allow TC programs to call
BPF_FUNC_skb_change_head"):
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=6f3f65d80dac
[Test Case]
Create a, ebpf program that uses this helper and load it with tc.
[Regression Potential]
The patch is trivial, the potential regressions are low.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1896504
Title:
tc/ebpf: unable to use BPF_FUNC_skb_change_head
Status in linux package in Ubuntu:
New
Bug description:
[Impact]
tc ebpf program that uses BPF_FUNC_skb_change_head are rejected.
This helper exists since linux v4.10, but it cannot be used until the the
upstream commit 6f3f65d80dac ("net: bpf: Allow TC programs to call
BPF_FUNC_skb_change_head"):
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=6f3f65d80dac
[Test Case]
Create a, ebpf program that uses this helper and load it with tc.
[Regression Potential]
The patch is trivial, the potential regressions are low.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1896504/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1896348] [NEW] wifi not working due to bcmwl-kernel-source
You have been subscribed to a public bug: wifi not working installed bcmwl-kernel-source package post-installation script subprocess returned error exit status 6 Errors were encountered while processing: bcmwl-kernel-source E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: ubuntu-release-upgrader-core 1:20.10.11 ProcVersionSignature: Ubuntu 5.8.0-18.19-generic 5.8.4 Uname: Linux 5.8.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu45 Architecture: amd64 CasperMD5CheckResult: skip CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Sat Sep 19 18:07:20 2020 InstallationDate: Installed on 2020-09-18 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: Upgraded to groovy on 2020-09-19 (0 days ago) VarLogDistupgradeXorgFixuplog: INFO:root:/usr/bin/do-release-upgrade running INFO:root:No xorg.conf, exiting ** Affects: bcmwl (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug dist-upgrade groovy -- wifi not working due to bcmwl-kernel-source https://bugs.launchpad.net/bugs/1896348 You received this bug notification because you are a member of Kernel Packages, which is subscribed to bcmwl 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 1895458] Re: Computer freezes on kernel 5, works on kernel 4
Please find attached a snapshot of the boot screen (var_log.tar.gz::var_log/1.jpg) and the screen after Ctrl+x (var_log.tar.gz::var_log/2.jpg) - it simply freezes and displays nothing more. What I did: 1. booted kernel 5.4.0-48 without "quiet" & "splash" - 1.jpg 2. Ctrl+x - the computer totally froze (as I said before) - 2.jpg 3. Than I re-booted with kernel 4.5.0-112, logged in and took all /var/log/* files from today Thank you for your support! ** Attachment added: "var_log.tar.gz" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1895458/+attachment/5412981/+files/var_log.tar.gz -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1895458 Title: Computer freezes on kernel 5, works on kernel 4 Status in linux package in Ubuntu: Confirmed Bug description: The computer works with kernel Ubuntu 4.15.0-112.113-generic 4.15.18. If I update to linux-image-5.4.0-47-generic 5.4.0-47.51 - it freezes. I tried the procedure "https://wiki.ubuntu.com/DebuggingKernelBoot; it freezes after Ctrl+x To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1895458/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1896419] Re: Comet Lake CPUID family:model:stepping 0x6:a5:2 (6:165:2) is not included
I've uploaded the update for Groovy to debian, it will get sync'd into Ubuntu in the next 24 hours. I've uploaded the fix for Focal to Ubuntu for SRU. ** Changed in: thermald (Ubuntu Focal) Assignee: (unassigned) => Colin Ian King (colin-king) ** Changed in: thermald (Ubuntu Focal) Status: New => In Progress ** Changed in: thermald (Ubuntu Focal) Status: In Progress => Fix Committed ** Changed in: thermald (Ubuntu Groovy) Status: In Progress => Fix Committed ** Changed in: thermald (Ubuntu Focal) Importance: Undecided => High ** Changed in: thermald (Ubuntu Groovy) Importance: Undecided => High ** Changed in: thermald (Ubuntu Groovy) Assignee: Kai-Chuan Hsieh (kchsieh) => Colin Ian King (colin-king) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to thermald in Ubuntu. https://bugs.launchpad.net/bugs/1896419 Title: Comet Lake CPUID family:model:stepping 0x6:a5:2 (6:165:2) is not included Status in OEM Priority Project: In Progress Status in thermald package in Ubuntu: Fix Committed Status in thermald source package in Focal: Fix Committed Status in thermald source package in Groovy: Fix Committed Bug description: [Impact] * The CPUID is not included, which cause the thermald starts failed. Sep 15 17:07:00 ubuntu thermald[1089]: [WARN]Unsupported cpu model, use thermal-conf.xml file or run with --ignore-cpuid-check Sep 15 17:07:00 ubuntu thermald[1089]: [ERR]THD engine start failed Sep 15 17:07:00 ubuntu systemd[1]: thermald.service: Succeeded. * A upstream commit added missing CPUID https://github.com/intel/thermal_daemon/commit/7f2003ee911dd1c97ff74d2b84c62e10950bc9e0 [Test Case] On an affected system (Comet Lake): * $ systemctl is-active thermald active [Regression Potential] * Only new id added, no process or logic adjustment, so no regression risk. [Other Info] * The upstream bug: https://github.com/intel/thermal_daemon/issues/275 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1896419/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1896419] Re: Comet Lake CPUID family:model:stepping 0x6:a5:2 (6:165:2) is not included
I'm the maintainer for thermald, I'll upload the fix to groovy and SRU this for focal today. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to thermald in Ubuntu. https://bugs.launchpad.net/bugs/1896419 Title: Comet Lake CPUID family:model:stepping 0x6:a5:2 (6:165:2) is not included Status in OEM Priority Project: In Progress Status in thermald package in Ubuntu: In Progress Status in thermald source package in Focal: New Status in thermald source package in Groovy: In Progress Bug description: [Impact] * The CPUID is not included, which cause the thermald starts failed. Sep 15 17:07:00 ubuntu thermald[1089]: [WARN]Unsupported cpu model, use thermal-conf.xml file or run with --ignore-cpuid-check Sep 15 17:07:00 ubuntu thermald[1089]: [ERR]THD engine start failed Sep 15 17:07:00 ubuntu systemd[1]: thermald.service: Succeeded. * A upstream commit added missing CPUID https://github.com/intel/thermal_daemon/commit/7f2003ee911dd1c97ff74d2b84c62e10950bc9e0 [Test Case] On an affected system (Comet Lake): * $ systemctl is-active thermald active [Regression Potential] * Only new id added, no process or logic adjustment, so no regression risk. [Other Info] * The upstream bug: https://github.com/intel/thermal_daemon/issues/275 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1896419/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1896419] Re: Comet Lake CPUID family:model:stepping 0x6:a5:2 (6:165:2) is not included
** Also affects: thermald (Ubuntu Groovy) Importance: Undecided Assignee: Kai-Chuan Hsieh (kchsieh) Status: In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to thermald in Ubuntu. https://bugs.launchpad.net/bugs/1896419 Title: Comet Lake CPUID family:model:stepping 0x6:a5:2 (6:165:2) is not included Status in OEM Priority Project: In Progress Status in thermald package in Ubuntu: In Progress Status in thermald source package in Focal: New Status in thermald source package in Groovy: In Progress Bug description: [Impact] * The CPUID is not included, which cause the thermald starts failed. Sep 15 17:07:00 ubuntu thermald[1089]: [WARN]Unsupported cpu model, use thermal-conf.xml file or run with --ignore-cpuid-check Sep 15 17:07:00 ubuntu thermald[1089]: [ERR]THD engine start failed Sep 15 17:07:00 ubuntu systemd[1]: thermald.service: Succeeded. * A upstream commit added missing CPUID https://github.com/intel/thermal_daemon/commit/7f2003ee911dd1c97ff74d2b84c62e10950bc9e0 [Test Case] On an affected system (Comet Lake): * $ systemctl is-active thermald active [Regression Potential] * Only new id added, no process or logic adjustment, so no regression risk. [Other Info] * The upstream bug: https://github.com/intel/thermal_daemon/issues/275 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1896419/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1847105] Re: very slow disk creation, snapshotting
Now that we got the change we sort of wanted from the beginning I have created a test build of virt-manager with the change applied. I need to debug if that now really enters the right code paths for non fallocate. -- 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/1847105 Title: very slow disk creation, snapshotting Status in virt-manager: Fix Released Status in Native ZFS for Linux: New Status in libvirt package in Ubuntu: Triaged Status in virt-manager package in Ubuntu: Triaged Status in zfs-linux package in Ubuntu: New Status in libvirt source package in Bionic: Invalid Status in virt-manager source package in Bionic: Invalid Status in zfs-linux source package in Bionic: Won't Fix Status in libvirt source package in Disco: Won't Fix Status in virt-manager source package in Disco: Won't Fix Status in zfs-linux source package in Disco: Won't Fix Status in libvirt source package in Focal: Triaged Status in libvirt source package in Groovy: Triaged Bug description: This is a regression in eoan for me. I use virt-manager to create vms, and I noticed that creating one now takes more than a minute. Looking at the process listing while the backing disk is being created, I see this qemu-img command line: 15658 ?Ssl0:00 /usr/sbin/libvirtd 23726 ?Sl 0:04 \_ /usr/bin/qemu-img create -f qcow2 -o preallocation=falloc,compat=1.1,lazy_refcounts /var/lib/libvirt/images/live-server.qcow2 41943040K If I run qemu-img with that preallocation parameter set, even on bionic, then it also takes a very long time. On eoan, for comparison: andreas@nsn7:~$ time qemu-img create -f qcow2 no-prealloc-image.qcow2 40G Formatting 'no-prealloc-image.qcow2', fmt=qcow2 size=42949672960 cluster_size=65536 lazy_refcounts=off refcount_bits=16 real 0m0,016s user 0m0,010s sys 0m0,006s andreas@nsn7:~$ qemu-img info no-prealloc-image.qcow2 image: no-prealloc-image.qcow2 file format: qcow2 virtual size: 40G (42949672960 bytes) disk size: 17K cluster_size: 65536 Format specific information: compat: 1.1 lazy refcounts: false refcount bits: 16 corrupt: false andreas@nsn7:~$ du -hs no-prealloc-image.qcow2 17K no-prealloc-image.qcow2 andreas@nsn7:~$ and now with preallocation=falloc: andreas@nsn7:~$ time qemu-img create -f qcow2 -o preallocation=falloc with-prealloc-image.qcow2 40G Formatting 'with-prealloc-image.qcow2', fmt=qcow2 size=42949672960 cluster_size=65536 preallocation=falloc lazy_refcounts=off refcount_bits=16 real 1m43,196s user 0m3,564s sys 1m26,720s andreas@nsn7:~$ qemu-img info with-prealloc-image.qcow2 image: with-prealloc-image.qcow2 file format: qcow2 virtual size: 40G (42949672960 bytes) disk size: 2.7M cluster_size: 65536 Format specific information: compat: 1.1 lazy refcounts: false refcount bits: 16 corrupt: false andreas@nsn7:~$ du -hs with-prealloc-image.qcow2 2,8M with-prealloc-image.qcow2 andreas@nsn7:~$ ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: libvirt-daemon 5.4.0-0ubuntu5 ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0 Uname: Linux 5.3.0-13-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 Date: Mon Oct 7 11:36:03 2019 InstallationDate: Installed on 2019-10-07 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Beta amd64 (20191006) SourcePackage: libvirt UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.libvirt.nwfilter.allow-arp.xml: [inaccessible: [Errno 13] Permission denied: '/etc/libvirt/nwfilter/allow-arp.xml'] modified.conffile..etc.libvirt.nwfilter.allow-dhcp-server.xml: [inaccessible: [Errno 13] Permission denied: '/etc/libvirt/nwfilter/allow-dhcp-server.xml'] modified.conffile..etc.libvirt.nwfilter.allow-dhcp.xml: [inaccessible: [Errno 13] Permission denied: '/etc/libvirt/nwfilter/allow-dhcp.xml'] modified.conffile..etc.libvirt.nwfilter.allow-incoming-ipv4.xml: [inaccessible: [Errno 13] Permission denied: '/etc/libvirt/nwfilter/allow-incoming-ipv4.xml'] modified.conffile..etc.libvirt.nwfilter.allow-ipv4.xml: [inaccessible: [Errno 13] Permission denied: '/etc/libvirt/nwfilter/allow-ipv4.xml'] modified.conffile..etc.libvirt.nwfilter.clean-traffic-gateway.xml: [inaccessible: [Errno 13] Permission denied: '/etc/libvirt/nwfilter/clean-traffic-gateway.xml'] modified.conffile..etc.libvirt.nwfilter.clean-traffic.xml: [inaccessible: [Errno 13] Permission denied: '/etc/libvirt/nwfilter/clean-traffic.xml'] modified.conffile..etc.libvirt.nwfilter.no-arp-ip-spoofing.xml: [inaccessible: [Errno 13] Permission denied: '/etc/libvirt/nwfilter/no-arp-ip-spoofing.xml']
[Kernel-packages] [Bug 1847105] Re: very slow disk creation, snapshotting
It works (as expected): before: 4 0 17337 263 20 0 163108 4240 - Sl ? 0:47 \_ /usr/bin/qemu-img create -f qcow2 -o preallocation=falloc,compat=1.1,lazy_refcounts /var/lib/libvirt/images/ubuntu20.04.qcow2 26214400K Now: 4 0 43901 263 20 0 163108 5436 - Sl ? 0:00 \_ /usr/bin/qemu-img create -f qcow2 -o preallocation=metadata,compat=1.1,lazy_refcounts /var/lib/libvirt/images/ubuntu20.04.qcow2 26214400K Even without the change to libvirt it works (as that is a valid fix, but for a different use case). And it is going much faster is on e.g. the ZFS based setup that was mentioned. -- 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/1847105 Title: very slow disk creation, snapshotting Status in virt-manager: Fix Released Status in Native ZFS for Linux: New Status in libvirt package in Ubuntu: Triaged Status in virt-manager package in Ubuntu: Triaged Status in zfs-linux package in Ubuntu: New Status in libvirt source package in Bionic: Invalid Status in virt-manager source package in Bionic: Invalid Status in zfs-linux source package in Bionic: Won't Fix Status in libvirt source package in Disco: Won't Fix Status in virt-manager source package in Disco: Won't Fix Status in zfs-linux source package in Disco: Won't Fix Status in libvirt source package in Focal: Triaged Status in libvirt source package in Groovy: Triaged Bug description: This is a regression in eoan for me. I use virt-manager to create vms, and I noticed that creating one now takes more than a minute. Looking at the process listing while the backing disk is being created, I see this qemu-img command line: 15658 ?Ssl0:00 /usr/sbin/libvirtd 23726 ?Sl 0:04 \_ /usr/bin/qemu-img create -f qcow2 -o preallocation=falloc,compat=1.1,lazy_refcounts /var/lib/libvirt/images/live-server.qcow2 41943040K If I run qemu-img with that preallocation parameter set, even on bionic, then it also takes a very long time. On eoan, for comparison: andreas@nsn7:~$ time qemu-img create -f qcow2 no-prealloc-image.qcow2 40G Formatting 'no-prealloc-image.qcow2', fmt=qcow2 size=42949672960 cluster_size=65536 lazy_refcounts=off refcount_bits=16 real 0m0,016s user 0m0,010s sys 0m0,006s andreas@nsn7:~$ qemu-img info no-prealloc-image.qcow2 image: no-prealloc-image.qcow2 file format: qcow2 virtual size: 40G (42949672960 bytes) disk size: 17K cluster_size: 65536 Format specific information: compat: 1.1 lazy refcounts: false refcount bits: 16 corrupt: false andreas@nsn7:~$ du -hs no-prealloc-image.qcow2 17K no-prealloc-image.qcow2 andreas@nsn7:~$ and now with preallocation=falloc: andreas@nsn7:~$ time qemu-img create -f qcow2 -o preallocation=falloc with-prealloc-image.qcow2 40G Formatting 'with-prealloc-image.qcow2', fmt=qcow2 size=42949672960 cluster_size=65536 preallocation=falloc lazy_refcounts=off refcount_bits=16 real 1m43,196s user 0m3,564s sys 1m26,720s andreas@nsn7:~$ qemu-img info with-prealloc-image.qcow2 image: with-prealloc-image.qcow2 file format: qcow2 virtual size: 40G (42949672960 bytes) disk size: 2.7M cluster_size: 65536 Format specific information: compat: 1.1 lazy refcounts: false refcount bits: 16 corrupt: false andreas@nsn7:~$ du -hs with-prealloc-image.qcow2 2,8M with-prealloc-image.qcow2 andreas@nsn7:~$ ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: libvirt-daemon 5.4.0-0ubuntu5 ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0 Uname: Linux 5.3.0-13-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 Date: Mon Oct 7 11:36:03 2019 InstallationDate: Installed on 2019-10-07 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Beta amd64 (20191006) SourcePackage: libvirt UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.libvirt.nwfilter.allow-arp.xml: [inaccessible: [Errno 13] Permission denied: '/etc/libvirt/nwfilter/allow-arp.xml'] modified.conffile..etc.libvirt.nwfilter.allow-dhcp-server.xml: [inaccessible: [Errno 13] Permission denied: '/etc/libvirt/nwfilter/allow-dhcp-server.xml'] modified.conffile..etc.libvirt.nwfilter.allow-dhcp.xml: [inaccessible: [Errno 13] Permission denied: '/etc/libvirt/nwfilter/allow-dhcp.xml'] modified.conffile..etc.libvirt.nwfilter.allow-incoming-ipv4.xml: [inaccessible: [Errno 13] Permission denied: '/etc/libvirt/nwfilter/allow-incoming-ipv4.xml'] modified.conffile..etc.libvirt.nwfilter.allow-ipv4.xml: [inaccessible: [Errno 13] Permission denied: '/etc/libvirt/nwfilter/allow-ipv4.xml'] modified.conffile..etc.libvirt.nwfilter.clean-traffic-gateway.xml: [inaccessible: [Errno
[Kernel-packages] [Bug 1896216] Re: [Ubuntu 20.10] zPCI DMA tables and bitmap leak on hard unplug (PCI Event 0x0304)
Patch request submitted for focal: https://lists.ubuntu.com/archives/kernel-team/2020-September/thread.html#113609 changing status to 'In Progress' for focal. ** Changed in: linux (Ubuntu Focal) Status: New => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1896216 Title: [Ubuntu 20.10] zPCI DMA tables and bitmap leak on hard unplug (PCI Event 0x0304) Status in Ubuntu on IBM z Systems: In Progress Status in linux package in Ubuntu: In Progress Status in linux source package in Focal: In Progress Status in linux source package in Groovy: In Progress Bug description: SRU Justification: == [Impact] * Since zpci_dma_exit_device() is never called on a zPCI device there is a potential leaking in DMA tables and bitmaps. * This is because commit "s390/pci: adapt events for zbus" removed the zpci_disable_device() call for a zPCI event with PEC 0x0304 (means on hot unplug). * It is only not called on hot unplug with event type PEC 0x0304 - this is the one where Linux is informed the device is gone instead of being asked to deconfigure it. * It should also always leak them with that event type on an enabled device. [Fix] * afdf9550e54627fcf4dd609bdc1153059378cdf5 afdf9550e546 "s390/pci: fix leak of DMA tables on hard unplug" [Test Case] * Have an IBM Z LPAR, that has PCIe devices (like RoCE adapters) assigned and Ubuntu Server 20.04 installed. * Disable and re-enable one (or more) of the assigned PCIe cards (using hotplug) - on LPAR this can be triggered using the 'Reassign I/O Path' function at the HMC/SE. * Monitor DMA tables and bitmaps for any kind of leaking. * Since these tables are vmalloc-ed memory, it's sufficient to monitor via /proc/meminfo and see that reassigning back and forth of a device will have the memory usage grow continuously. * The test and verification needs to be conducted by IBM. [Regression Potential] * There regression risk can be considered as moderate, because: * only a call of zpci_disable_device(zdev) got reintroduced (and some comment lines). * Since __zpci_event_availability gets modified, the zPCI event handling could be scrud up, * which could cause issues regarding the availability of zPCI devices * and in worst case make zPCI devices unusable. * But only one switch case of the function is modified and all cases break, so only PEC 0x0304 should be affected. * And the code changes themselves are minimal, and the zPCI code is limited to the s390x architecture. * On top test kernels were built and shared for further testing. [Other] * Since this commit needs to land in groovy too, but groovy is still in development (hence the SRU process does not apply for groovy yet), I've sent a separate Patch request for groovy. __ Commit "s390/pci: adapt events for zbus" removed the zpci_disable_device() call for a zPCI event with PEC 0x0304 (hot unplug) because the device is already deconfigured by the platform. This however skips the Linux side of the disable in particular it leads to leaking the DMA tables and bitmaps because zpci_dma_exit_device() is never called on the device. This has been fixed in the following commit (currently in linux-next) afdf9550e54627fcf4dd609bdc1153059378cdf5 s390/pci: fix leak of DMA tables on hard unplug The commit re-introduces the zpci_disable_device() call as it was before the zbus introduction, for good measure I also added a comment to zpci_disable_device() to call out the fact that it may be called with the device disabled already. As the commit was introduced with the multi-function support this of course should go into both 20.10 and 20.04. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1896216/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1895458] Re: Computer freezes on kernel 5, works on kernel 4
Hi Petar, Thanks for the bug report. Unfortunately there's little details about the error. Could you please post a picture of your compute screen once the 5.4 kernel fails to boot? (after you removed the 'quiet' and 'splash' options in the grub editor, and pressed ctrl-x to boot.) Mainly looking for error messages, a initramfs prompt, or something like a stack trace. Thanks, Mauricio -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1895458 Title: Computer freezes on kernel 5, works on kernel 4 Status in linux package in Ubuntu: Confirmed Bug description: The computer works with kernel Ubuntu 4.15.0-112.113-generic 4.15.18. If I update to linux-image-5.4.0-47-generic 5.4.0-47.51 - it freezes. I tried the procedure "https://wiki.ubuntu.com/DebuggingKernelBoot; it freezes after Ctrl+x To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1895458/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1885031] Re: supervisor write access in kernel mode
Hey Martin. The issues reported on comment 1 and commment 24 have different stack trace signatures, and do not seem to be the same issue at all. I'll thus mark this bug as Invalid as apparently you couldn't reproduce the original issue anymore. If the new issue is still present with the latest 5.4 kernel in -updates, please feel free to report a new bug. Thank you! ... comment 1: Jun 24 18:56:43 MartoBeast kernel: BUG: kernel NULL pointer dereference, address: Jun 24 18:56:43 MartoBeast kernel: #PF: supervisor write access in kernel mode Jun 24 18:56:43 MartoBeast kernel: #PF: error_code(0x0002) - not-present page Jun 24 18:56:43 MartoBeast kernel: PGD 0 P4D 0 Jun 24 18:56:43 MartoBeast kernel: Oops: 0002 [#1] SMP NOPTI Jun 24 18:56:43 MartoBeast kernel: CPU: 4 PID: 114660 Comm: sshd Tainted: P OE 5.4.0-37-generic #41-Ubuntu Jun 24 18:56:43 MartoBeast kernel: Hardware name: Gigabyte Technology Co., Ltd. X570 AORUS ELITE/X570 AORUS ELITE, BIOS F11 12/06/2019 Jun 24 18:56:43 MartoBeast kernel: RIP: 0010:__rb_erase_color+0x1aa/0x280 ... Jun 24 18:56:43 MartoBeast kernel: Call Trace: Jun 24 18:56:43 MartoBeast kernel: vma_interval_tree_remove+0x1a0/0x2b0 Jun 24 18:56:43 MartoBeast kernel: __remove_shared_vm_struct+0x32/0x40 Jun 24 18:56:43 MartoBeast kernel: unlink_file_vma+0x41/0x60 Jun 24 18:56:43 MartoBeast kernel: free_pgtables+0x9b/0xf0 Jun 24 18:56:43 MartoBeast kernel: exit_mmap+0xc7/0x1b0 Jun 24 18:56:43 MartoBeast kernel: mmput+0x5d/0x130 Jun 24 18:56:43 MartoBeast kernel: do_exit+0x2fd/0xac0 Jun 24 18:56:43 MartoBeast kernel: ? kill_something_info+0x145/0x170 Jun 24 18:56:43 MartoBeast kernel: do_group_exit+0x47/0xb0 Jun 24 18:56:43 MartoBeast kernel: __x64_sys_exit_group+0x18/0x20 Jun 24 18:56:43 MartoBeast kernel: do_syscall_64+0x57/0x190 Jun 24 18:56:43 MartoBeast kernel: entry_SYSCALL_64_after_hwframe+0x44/0xa9 Jun 24 18:56:43 MartoBeast kernel: RIP: 0033:0x7f52319de136 comment 24: Aug 21 00:04:56 MartoBeast kernel: BUG: unable to handle page fault for address: 00090b64 Aug 21 00:04:56 MartoBeast kernel: #PF: supervisor write access in kernel mode Aug 21 00:04:56 MartoBeast kernel: #PF: error_code(0x0002) - not-present page Aug 21 00:04:56 MartoBeast kernel: PGD 0 P4D 0 Aug 21 00:04:56 MartoBeast kernel: Oops: 0002 [#3] SMP NOPTI Aug 21 00:04:56 MartoBeast kernel: CPU: 3 PID: 4610 Comm: threaded-ml Tainted: P DOE 5.4.0-44-generic #48-Ubuntu Aug 21 00:04:56 MartoBeast kernel: Hardware name: Gigabyte Technology Co., Ltd. X570 AORUS ELITE/X570 AORUS ELITE, BIOS F20b 07/02/2020 Aug 21 00:04:56 MartoBeast kernel: RIP: 0010:_raw_spin_lock_irqsave+0x23/0x40 ... Aug 21 00:04:56 MartoBeast kernel: Call Trace: Aug 21 00:04:56 MartoBeast kernel: try_to_wake_up+0x4e/0x6a0 Aug 21 00:04:56 MartoBeast kernel: ? poll_select_finish+0x210/0x210 Aug 21 00:04:56 MartoBeast kernel: ? ttwu_do_wakeup+0x10d/0x150 Aug 21 00:04:56 MartoBeast kernel: default_wake_function+0x12/0x20 Aug 21 00:04:56 MartoBeast kernel: pollwake+0x72/0x90 Aug 21 00:04:56 MartoBeast kernel: ? wake_up_q+0x70/0x70 Aug 21 00:04:56 MartoBeast kernel: __wake_up_common+0x7e/0x140 Aug 21 00:04:56 MartoBeast kernel: __wake_up_locked_key+0x1b/0x20 Aug 21 00:04:56 MartoBeast kernel: eventfd_write+0xd3/0x230 Aug 21 00:04:56 MartoBeast kernel: ? wake_up_q+0x70/0x70 Aug 21 00:04:56 MartoBeast kernel: __vfs_write+0x1b/0x40 Aug 21 00:04:56 MartoBeast kernel: vfs_write+0xb9/0x1a0 Aug 21 00:04:56 MartoBeast kernel: ksys_write+0x67/0xe0 Aug 21 00:04:56 MartoBeast kernel: __x64_sys_write+0x1a/0x20 Aug 21 00:04:56 MartoBeast kernel: do_syscall_64+0x57/0x190 Aug 21 00:04:56 MartoBeast kernel: entry_SYSCALL_64_after_hwframe+0x44/0xa9 Aug 21 00:04:56 MartoBeast kernel: RIP: 0033:0x7fd41a6412cf ** Changed in: linux (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1885031 Title: supervisor write access in kernel mode Status in linux package in Ubuntu: Invalid Bug description: machine froze. Only mouse could be moved. BUG: kernel NULL pointer dereference, address: Jun 24 18:56:43 MartoBeast kernel: #PF: supervisor write access in kernel mode Jun 24 18:56:43 MartoBeast kernel: #PF: error_code(0x0002) - not-present page Ubuntu 20.04 Linux MartoBeast 5.4.0-37-generic #41-Ubuntu SMP Wed Jun 3 18:57:02 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: martin 2649 F pulseaudio /dev/snd/controlC0: martin 2649 F pulseaudio /dev/snd/controlC2: martin 2649 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-12-08 (199
[Kernel-packages] [Bug 1896419] Re: Comet Lake CPUID family:model:stepping 0x6:a5:2 (6:165:2) is not included
Debian bug created. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=970686 ** Bug watch added: Debian Bug tracker #970686 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=970686 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to thermald in Ubuntu. https://bugs.launchpad.net/bugs/1896419 Title: Comet Lake CPUID family:model:stepping 0x6:a5:2 (6:165:2) is not included Status in OEM Priority Project: In Progress Status in thermald package in Ubuntu: In Progress Status in thermald source package in Focal: New Bug description: [Impact] * The CPUID is not included, which cause the thermald starts failed. Sep 15 17:07:00 ubuntu thermald[1089]: [WARN]Unsupported cpu model, use thermal-conf.xml file or run with --ignore-cpuid-check Sep 15 17:07:00 ubuntu thermald[1089]: [ERR]THD engine start failed Sep 15 17:07:00 ubuntu systemd[1]: thermald.service: Succeeded. * A upstream commit added missing CPUID https://github.com/intel/thermal_daemon/commit/7f2003ee911dd1c97ff74d2b84c62e10950bc9e0 [Test Case] On an affected system (Comet Lake): * $ systemctl is-active thermald active [Regression Potential] * Only new id added, no process or logic adjustment, so no regression risk. [Other Info] * The upstream bug: https://github.com/intel/thermal_daemon/issues/275 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1896419/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1891151] Re: md: improve IO accounting
FYI, the patch on the mailing list is here: https://lists.ubuntu.com/archives/kernel-team/2020-September/113590.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1891151 Title: md: improve IO accounting Status in linux package in Ubuntu: Confirmed Status in linux source package in Focal: Confirmed Status in linux source package in Groovy: Confirmed Bug description: [IMPACT] Currently reported IO stats may be incorrect or missing. This adds correct statistics about in-flight IOs and IO processing time, interpreted e.g. in iostat as await, svctm, aqu-sz and %util. [FIX] Commit: 41d2d848 md: improve io stats accounting This isn't a clean cherry pick to either 5.8 or 5.4, so some backport work is necessary. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1891151/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1847105] Re: very slow disk creation, snapshotting
** Changed in: virt-manager Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1847105 Title: very slow disk creation, snapshotting Status in virt-manager: Fix Released Status in Native ZFS for Linux: New Status in libvirt package in Ubuntu: Triaged Status in virt-manager package in Ubuntu: Triaged Status in zfs-linux package in Ubuntu: New Status in libvirt source package in Bionic: Invalid Status in virt-manager source package in Bionic: Invalid Status in zfs-linux source package in Bionic: Won't Fix Status in libvirt source package in Disco: Won't Fix Status in virt-manager source package in Disco: Won't Fix Status in zfs-linux source package in Disco: Won't Fix Status in libvirt source package in Focal: Triaged Status in libvirt source package in Groovy: Triaged Bug description: This is a regression in eoan for me. I use virt-manager to create vms, and I noticed that creating one now takes more than a minute. Looking at the process listing while the backing disk is being created, I see this qemu-img command line: 15658 ?Ssl0:00 /usr/sbin/libvirtd 23726 ?Sl 0:04 \_ /usr/bin/qemu-img create -f qcow2 -o preallocation=falloc,compat=1.1,lazy_refcounts /var/lib/libvirt/images/live-server.qcow2 41943040K If I run qemu-img with that preallocation parameter set, even on bionic, then it also takes a very long time. On eoan, for comparison: andreas@nsn7:~$ time qemu-img create -f qcow2 no-prealloc-image.qcow2 40G Formatting 'no-prealloc-image.qcow2', fmt=qcow2 size=42949672960 cluster_size=65536 lazy_refcounts=off refcount_bits=16 real 0m0,016s user 0m0,010s sys 0m0,006s andreas@nsn7:~$ qemu-img info no-prealloc-image.qcow2 image: no-prealloc-image.qcow2 file format: qcow2 virtual size: 40G (42949672960 bytes) disk size: 17K cluster_size: 65536 Format specific information: compat: 1.1 lazy refcounts: false refcount bits: 16 corrupt: false andreas@nsn7:~$ du -hs no-prealloc-image.qcow2 17K no-prealloc-image.qcow2 andreas@nsn7:~$ and now with preallocation=falloc: andreas@nsn7:~$ time qemu-img create -f qcow2 -o preallocation=falloc with-prealloc-image.qcow2 40G Formatting 'with-prealloc-image.qcow2', fmt=qcow2 size=42949672960 cluster_size=65536 preallocation=falloc lazy_refcounts=off refcount_bits=16 real 1m43,196s user 0m3,564s sys 1m26,720s andreas@nsn7:~$ qemu-img info with-prealloc-image.qcow2 image: with-prealloc-image.qcow2 file format: qcow2 virtual size: 40G (42949672960 bytes) disk size: 2.7M cluster_size: 65536 Format specific information: compat: 1.1 lazy refcounts: false refcount bits: 16 corrupt: false andreas@nsn7:~$ du -hs with-prealloc-image.qcow2 2,8M with-prealloc-image.qcow2 andreas@nsn7:~$ ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: libvirt-daemon 5.4.0-0ubuntu5 ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0 Uname: Linux 5.3.0-13-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 Date: Mon Oct 7 11:36:03 2019 InstallationDate: Installed on 2019-10-07 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Beta amd64 (20191006) SourcePackage: libvirt UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.libvirt.nwfilter.allow-arp.xml: [inaccessible: [Errno 13] Permission denied: '/etc/libvirt/nwfilter/allow-arp.xml'] modified.conffile..etc.libvirt.nwfilter.allow-dhcp-server.xml: [inaccessible: [Errno 13] Permission denied: '/etc/libvirt/nwfilter/allow-dhcp-server.xml'] modified.conffile..etc.libvirt.nwfilter.allow-dhcp.xml: [inaccessible: [Errno 13] Permission denied: '/etc/libvirt/nwfilter/allow-dhcp.xml'] modified.conffile..etc.libvirt.nwfilter.allow-incoming-ipv4.xml: [inaccessible: [Errno 13] Permission denied: '/etc/libvirt/nwfilter/allow-incoming-ipv4.xml'] modified.conffile..etc.libvirt.nwfilter.allow-ipv4.xml: [inaccessible: [Errno 13] Permission denied: '/etc/libvirt/nwfilter/allow-ipv4.xml'] modified.conffile..etc.libvirt.nwfilter.clean-traffic-gateway.xml: [inaccessible: [Errno 13] Permission denied: '/etc/libvirt/nwfilter/clean-traffic-gateway.xml'] modified.conffile..etc.libvirt.nwfilter.clean-traffic.xml: [inaccessible: [Errno 13] Permission denied: '/etc/libvirt/nwfilter/clean-traffic.xml'] modified.conffile..etc.libvirt.nwfilter.no-arp-ip-spoofing.xml: [inaccessible: [Errno 13] Permission denied: '/etc/libvirt/nwfilter/no-arp-ip-spoofing.xml'] modified.conffile..etc.libvirt.nwfilter.no-arp-mac-spoofing.xml: [inaccessible: [Errno 13] Permission denied: '/etc/libvirt/nwfilter/no-arp-mac-spoofing.xml']
[Kernel-packages] [Bug 1847105]
Okay now that I actually look into this and wrap my head around it, virt-manager should change. See this previously mentioned change: https://github.com/virt-manager/virt-manager/commit/15a6a7e2105440df528f75c4df4d2471df28bd1e The idea behind virt-manager's default was if user selected 'raw' for disk images, assume the user wants to maximize performance, so fully allocate the disk. qcow2 didn't support anything except sparse, so the sparse=True vs sparse=False made no difference. So we always set sparse=False Then qcow2 grows non-sparse support, and virt-manager is suddenly defaulting to it. That's a pretty big semantic change. Even if falloc is fast enough in most cases, it is still claiming all the storage up front. Which is not the historically intended behavior. So I pushed a change to virt-manager to default to only use non-sparse for raw format by default. That should side step this issue I'll be pushing a new release with the fix sometime this coming week commit ba08f84b3408744e9aa9763d100e8aa217c1f5ff Author: Cole Robinson Date: Sat Sep 19 18:06:45 2020 -0400 addstorage: Return to using qcow2 sparse by default -- 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/1847105 Title: very slow disk creation, snapshotting Status in virt-manager: Fix Released Status in Native ZFS for Linux: New Status in libvirt package in Ubuntu: Triaged Status in virt-manager package in Ubuntu: Triaged Status in zfs-linux package in Ubuntu: New Status in libvirt source package in Bionic: Invalid Status in virt-manager source package in Bionic: Invalid Status in zfs-linux source package in Bionic: Won't Fix Status in libvirt source package in Disco: Won't Fix Status in virt-manager source package in Disco: Won't Fix Status in zfs-linux source package in Disco: Won't Fix Status in libvirt source package in Focal: Triaged Status in libvirt source package in Groovy: Triaged Bug description: This is a regression in eoan for me. I use virt-manager to create vms, and I noticed that creating one now takes more than a minute. Looking at the process listing while the backing disk is being created, I see this qemu-img command line: 15658 ?Ssl0:00 /usr/sbin/libvirtd 23726 ?Sl 0:04 \_ /usr/bin/qemu-img create -f qcow2 -o preallocation=falloc,compat=1.1,lazy_refcounts /var/lib/libvirt/images/live-server.qcow2 41943040K If I run qemu-img with that preallocation parameter set, even on bionic, then it also takes a very long time. On eoan, for comparison: andreas@nsn7:~$ time qemu-img create -f qcow2 no-prealloc-image.qcow2 40G Formatting 'no-prealloc-image.qcow2', fmt=qcow2 size=42949672960 cluster_size=65536 lazy_refcounts=off refcount_bits=16 real 0m0,016s user 0m0,010s sys 0m0,006s andreas@nsn7:~$ qemu-img info no-prealloc-image.qcow2 image: no-prealloc-image.qcow2 file format: qcow2 virtual size: 40G (42949672960 bytes) disk size: 17K cluster_size: 65536 Format specific information: compat: 1.1 lazy refcounts: false refcount bits: 16 corrupt: false andreas@nsn7:~$ du -hs no-prealloc-image.qcow2 17K no-prealloc-image.qcow2 andreas@nsn7:~$ and now with preallocation=falloc: andreas@nsn7:~$ time qemu-img create -f qcow2 -o preallocation=falloc with-prealloc-image.qcow2 40G Formatting 'with-prealloc-image.qcow2', fmt=qcow2 size=42949672960 cluster_size=65536 preallocation=falloc lazy_refcounts=off refcount_bits=16 real 1m43,196s user 0m3,564s sys 1m26,720s andreas@nsn7:~$ qemu-img info with-prealloc-image.qcow2 image: with-prealloc-image.qcow2 file format: qcow2 virtual size: 40G (42949672960 bytes) disk size: 2.7M cluster_size: 65536 Format specific information: compat: 1.1 lazy refcounts: false refcount bits: 16 corrupt: false andreas@nsn7:~$ du -hs with-prealloc-image.qcow2 2,8M with-prealloc-image.qcow2 andreas@nsn7:~$ ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: libvirt-daemon 5.4.0-0ubuntu5 ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0 Uname: Linux 5.3.0-13-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 Date: Mon Oct 7 11:36:03 2019 InstallationDate: Installed on 2019-10-07 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Beta amd64 (20191006) SourcePackage: libvirt UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.libvirt.nwfilter.allow-arp.xml: [inaccessible: [Errno 13] Permission denied: '/etc/libvirt/nwfilter/allow-arp.xml'] modified.conffile..etc.libvirt.nwfilter.allow-dhcp-server.xml: [inaccessible: [Errno 13] Permission denied: '/etc/libvirt/nwfilter/allow-dhcp-server.xml']
[Kernel-packages] [Bug 1868551] Re: Intel GPU Hangs : random screen freezing w/ Ubuntu 20.04 (Linux 5.4) i915_active_acquire
Recently installed a brand new copy of Linux Mint 20 Cinnamon and suffered frequent freezes. The workaround suggested in comment #45 fixed these for me. My current kernel is 5.4.0-47-generic, and I'm using a Intel© Core™ i5-6500T CPU (2.50GHz × 4) with Intel Corporation HD Graphics 530. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1868551 Title: Intel GPU Hangs : random screen freezing w/ Ubuntu 20.04 (Linux 5.4) i915_active_acquire Status in linux package in Ubuntu: Fix Released Status in linux source package in Focal: Fix Released Bug description: SRU Justification: [Impact] Users are experiencing a frequent NULL pointer dereference crash in i915_active_acquire when using kms, which is used by default. [Fix] The fix is a cherry pick from upstream which was supposed to be backported to 5.4 by upstream, but was neglected. The fix has a subsequent Fixes patch to resolve some uninitialized pointer usage. [Test] Verified by multiple bug reporters. [Regression Potential] Medium. Although there are a lot of lines added, they're mostly boilerplate, and this patch is confirmed by multiple users to fix a crash. --- uname -a Linux xps 5.4.0-14-generic #17-Ubuntu SMP Thu Feb 6 22:47:59 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu Focal Fossa (development branch) Release: 20.04 Codename: focal [ 2556.956079] BUG: kernel NULL pointer dereference, address: 0040 [ 2556.956084] #PF: supervisor read access in kernel mode [ 2556.956084] #PF: error_code(0x) - not-present page [ 2556.956085] PGD 0 P4D 0 [ 2556.956088] Oops: [#1] SMP NOPTI [ 2556.956090] CPU: 2 PID: 1685 Comm: xfwm4 Not tainted 5.4.0-14-generic #17-Ubuntu [ 2556.956092] Hardware name: Dell Inc. XPS 13 7390/0G2D0W, BIOS 1.2.0 10/03/2019 [ 2556.956161] RIP: 0010:i915_active_acquire+0xe/0x80 [i915] [ 2556.956163] Code: 00 48 c7 c6 11 4d 6b c0 e8 af a1 d6 c7 5d c3 66 66 2e 0f 1f 84 00 00 00 00 00 66 90 0f 1f 44 00 00 55 48 89 e5 41 55 41 54 53 <8b> 47 38 48 89 fb 85 c0 74 17 8d 50 01 f0 0f b1 53 38 75 f2 45 31 [ 2556.956164] RSP: 0018:ac17c13279c8 EFLAGS: 00010286 [ 2556.956165] RAX: RBX: 983831d3e480 RCX: [ 2556.956166] RDX: 983783475200 RSI: 983831d3e480 RDI: 0008 [ 2556.956167] RBP: ac17c13279e0 R08: R09: 98382d6b6520 [ 2556.956168] R10: 6cc0 R11: 983838b4db00 R12: 983783475200 [ 2556.956169] R13: 0008 R14: 983783475200 R15: 98382d6b6400 [ 2556.956170] FS: 7f9031c28f00() GS:98383e50() knlGS: [ 2556.956171] CS: 0010 DS: ES: CR0: 80050033 [ 2556.956172] CR2: 0040 CR3: 00046eac6001 CR4: 003606e0 [ 2556.956173] Call Trace: [ 2556.956199] i915_active_ref+0x24/0x200 [i915] [ 2556.956223] i915_vma_move_to_active+0x74/0xf0 [i915] [ 2556.956245] eb_submit+0xff/0x440 [i915] [ 2556.956267] i915_gem_do_execbuffer+0x88e/0xc20 [i915] [ 2556.956271] ? sock_def_readable+0x40/0x70 [ 2556.956274] ? __kmalloc_node+0x205/0x320 [ 2556.956294] i915_gem_execbuffer2_ioctl+0x2c3/0x3d0 [i915] [ 2556.956314] ? i915_gem_execbuffer_ioctl+0x2d0/0x2d0 [i915] [ 2556.956330] drm_ioctl_kernel+0xae/0xf0 [drm] [ 2556.956338] drm_ioctl+0x234/0x3d0 [drm] [ 2556.956358] ? i915_gem_execbuffer_ioctl+0x2d0/0x2d0 [i915] [ 2556.956361] ? vfs_writev+0xc3/0xf0 [ 2556.956363] do_vfs_ioctl+0x407/0x670 [ 2556.956365] ? fput+0x13/0x15 [ 2556.956367] ? __sys_recvmsg+0x88/0xa0 [ 2556.956369] ksys_ioctl+0x67/0x90 [ 2556.956371] __x64_sys_ioctl+0x1a/0x20 [ 2556.956373] do_syscall_64+0x57/0x190 [ 2556.956376] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [ 2556.956377] RIP: 0033:0x7f9032b3f68b [ 2556.956379] Code: 0f 1e fa 48 8b 05 05 28 0d 00 64 c7 00 26 00 00 00 48 c7 c0 ff ff ff ff c3 66 0f 1f 44 00 00 f3 0f 1e fa b8 10 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d d5 27 0d 00 f7 d8 64 89 01 48 [ 2556.956380] RSP: 002b:7ffee39a0078 EFLAGS: 0246 ORIG_RAX: 0010 [ 2556.956381] RAX: ffda RBX: 55a8abeb6e48 RCX: 7f9032b3f68b [ 2556.956382] RDX: 7ffee39a0090 RSI: 40406469 RDI: 000d [ 2556.956382] RBP: 7ffee39a0120 R08: 0001 R09: [ 2556.956383] R10: 7ffee39a0140 R11: 0246 R12: 7f9022a4f460 [ 2556.956384] R13: R14: 7ffee39a0090 R15: 000d [ 2556.956385] Modules linked in: ccm rfcomm xt_CHECKSUM xt_MASQUERADE xt_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp ip6table_mangle ip6table_nat typec_displayport iptable_mangle iptable_nat nf_nat nf_conntrack
[Kernel-packages] [Bug 1895563] Re: Kernel Oops: Rsyncing to bcache device w/o backing cache kernel panic
Oops, please remove the --dry-run from apt 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/1895563 Title: Kernel Oops: Rsyncing to bcache device w/o backing cache kernel panic Status in linux package in Ubuntu: Confirmed Bug description: Platform details: 1) version.log attached 2) lspci-vnvn.log attached 3) lsb_release -rd Description:Ubuntu 18.04.5 LTS Release:18.04 4) apt-cache policy bcache-tools bcache-tools: Installed: 1.0.8-2ubuntu0.18.04.1 Candidate: 1.0.8-2ubuntu0.18.04.1 Version table: *** 1.0.8-2ubuntu0.18.04.1 500 500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 1.0.8-2build1 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages 5) uname -a: Linux timber4 4.15.0-117-generic #118-Ubuntu SMP Fri Sep 4 20:02:41 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux Short problem description: Rsyncing from a 1.4TB home dir to a an new filesystem on a bcache device without an attached cache eventually results in kernel panic. What I expected to happen: no kernel panic. Long problem description: 1) Devices / Filesystems: bfd01: 8*4TB configured as RAID6 using md LVM2 volume group. bfd02: 8*4TB configured as RAID6 using Dell PERC H810 LVM2 volume group. The tree contains 1069685 files / dirs. 2) Steps to reproduce: # Make the device, format and mount it make-bcache -B /dev/vg-bfd02/delme01_bc mkfs.xfs -f -L delme01bc /dev/bcache0 mount /dev/bcache0 /dev/bfd02/delme01bc # Rsync flags="-a --delete" ; info_cmd="--info=progress2" ; excludes=""; src=/mnt/bfd01/delme01 ; tgt=/mnt/bfd02/delme01bc/ ; time rsync $flags $info_cmd $excludes $src/ $tgt/ ... # eventually kernel panic Using incremental rsync it will kernel panic after reading about 21GB. # If instead I use non-incremental rsync it will kernel panic after reading about 1.2-1.3TB. flags="--no-inc-recursive -ax -HAXS --delete" ; info_cmd="--info=progress2" ; excludes=""; ... # eventually kernel panic Additional detail: 1) I was *not* able to reproduce if bfd01/delm01bc was a target and bfd02 was the source e.g. # Rsync flags="-a --delete" ; info_cmd="--info=progress2" ; excludes=""; src=/mnt/bfd02/delme01 ; tgt=/mnt/bfd01/delme01bc/ ; time rsync $flags $info_cmd $excludes $src/ $tgt/ ... # rsync completes successfully 2) I was *not* able to reproduce if I attached and then detached a cache set: ceho 'd3b93488-714e-4efa-af94-cd80fd2db11f' > /sys/block/bcache0/bcache/attach echo 1 > /sys/block/bcache0/bcache/detach ... time rsync $flags $info_cmd $excludes $src/ $tgt/ ... # rsync completes successfully I have 11 compressed kernel crash dumps. I will upload 3 after filing this. Let me know if you want the other 8. ProblemType: KernelCrash DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-117-generic 4.15.0-117.118 ProcVersionSignature: Ubuntu 4.15.0-117.118-generic 4.15.18 Uname: Linux 4.15.0-117-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Sep 13 12:53 seq crw-rw 1 root audio 116, 33 Sep 13 12:53 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.17 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Sat Sep 12 09:51:37 2020 HibernationDevice: RESUME=none IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: Dell Inc. PowerEdge R620 PciMultimedia: ProcFB: 0 mgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-117-generic root=UUID=de68d15b-3948-4666-9bc5-5cbecc83971c ro maybe-ubiquity crashkernel=512M-:512M RelatedPackageVersions: linux-restricted-modules-4.15.0-117-generic N/A linux-backports-modules-4.15.0-117-generic N/A linux-firmware 1.173.19 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/06/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.9.0 dmi.board.name: 0KCKR5 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.9.0:bd12/06/2019:svnDellInc.:pnPowerEdgeR620:pvr:rvnDellInc.:rn0KCKR5:rvrA00:cvnDellInc.:ct23:cvr: dmi.product.name: PowerEdge R620 dmi.sys.vendor: Dell Inc. --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Sep 13 12:53 seq crw-rw 1 root audio 116, 33 Sep 13 12:53 timer AplayDevices:
[Kernel-packages] [Bug 1891437] Comment bridged from LTC Bugzilla
--- Comment From heinz-werner_se...@de.ibm.com 2020-09-21 09:07 EDT--- IBM bugzilla status->closed, Fix Released for focal and groovy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1891437 Title: [UBUNTU 20.04] zPCI: Enabling of a reserved PCI function regression introduced by multi-function support Status in Ubuntu on IBM z Systems: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Focal: Fix Released Status in linux source package in Groovy: Fix Released Bug description: SRU Justification: == [Impact] * If a NVMe drive is assigned/hotplugged to a Linux on s390x LPAR, a bug in lib/list_debug.c is hit and the device is not accessible. * The reason is a missing /dev/ file -- lspci does not report it either. [Fix] * 3047766bc6ec9c6bc9ece85b45a41ff401e8d988 3047766bc6ec "s390/pci: fix enabling a reserved PCI function" [Test Case] * Assign a NMVe drive to your LPAR (using the HMC) * Unassign the NVMe drive from your LPAR * Reassign it to your LPAR again * Look at dmesg for 'kernel BUG at lib/list_debug.c' [Regression Potential] * There is some regression risk with having code changes in the zPCI sub-system. * zPCI is the PCI implementation on s390x, modifications here do not affect any other architecture. * It could be that PCI events do not work anymore and NVMe devices don't IPL (boot) on s390x anymore. * However, the code changes below to a single file: arch/s390/pci/pci_event.c * and IPL from NVMe is brand new in Ubuntu for s390x, * and zPCI devices are less wide-spread compared to ccw devices on s390x. * On top a test kernel was build and made available for further testing. [Other] * Since the fix/patch got upstream accepted with kernel v5.8-rc5, it's already in the groovy proposed kernel 5.8, hence this SRU is for focal only. __ When a NVMe drive is assigned/hotplugged to a Linux LPAR then a bug is hit in lib/list_debug.c. And the device is not accessible, there is no /dev/ file and lspci does not report it also. [ 1681.564462] list_add double add: new=eed0f808, prev=eed0f808, next=4070a300. [ 1681.564489] [ cut here ] [ 1681.564490] kernel BUG at lib/list_debug.c:31! [ 1681.564504] monitor event: 0040 ilc:2 [#1] SMP [ 1681.564507] Modules linked in: ip6t_REJECT nf_reject_ipv6 ip6t_rpfilter ipt_REJECT nf_reject_ipv4 xt_conntrack ebtable_nat ebtable_broute ip6table_nat ip6table_mangle ip6table_raw ip6table_security iptable_nat nf_nat iptable_mangle iptable_raw iptable_security nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 libcrc32c ip_set nfnetlink ebtable_filter ebtables ip6table_filter ip6_tables iptable_filter s390_trng ghash_s390 prng aes_s390 des_s390 libdes sha512_s390 vfio_ccw sha1_s390 vfio_mdev mdev chsc_sch vfio_iommu_type1 eadm_sch vfio ip_tables dm_service_time nvme crc32_vx_s390 sha256_s390 sha_common nvme_core qeth_l2 zfcp qeth scsi_transport_fc qdio ccwgroup dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua pkey zcrypt [ 1681.564534] CPU: 6 PID: 139 Comm: kmcheck Not tainted 5.8.0-rc1+ #2 [ 1681.564535] Hardware name: IBM 8561 T01 701 (LPAR) [ 1681.564536] Krnl PSW : 0704c0018000 3ffcadb8 (__list_add_valid+0x70/0xa8) [ 1681.564544]R:0 T:1 IO:1 EX:1 Key:0 M:1 W:0 P:0 AS:3 CC:0 PM:0 RI:0 EA:3 [ 1681.564545] Krnl GPRS: 0040 0027 0058 0007 [ 1681.564546]3ffcadb4 03e0051a7ce0 [ 1681.564547]4070a300 eed0f808 eed0f808 4070a300 [ 1681.564548]f56a2000 40c2c788 3ffcadb4 03e0051a7bc8 [ 1681.564583] Krnl Code: 3ffcada8: c02000302b09larl %r2,405d03ba 3ffcadae: c0e5ffdd30b1brasl %r14,3fb70f10 #3ffcadb4: af00mc 0,0 >3ffcadb8: b9040054lgr %r5,%r4 3ffcadbc: c02000302aadlarl %r2,405d0316 3ffcadc2: b9040041lgr %r4,%r1 3ffcadc6: c0e5ffdd30a5brasl %r14,3fb70f10 3ffcadcc: af00mc 0,0 [ 1681.564592] Call Trace: [ 1681.564594] [<3ffcadb8>] __list_add_valid+0x70/0xa8 [ 1681.564596] ([<3ffcadb4>] __list_add_valid+0x6c/0xa8) [ 1681.564599] [<3faf2920>] zpci_create_device+0x60/0x1b0 [ 1681.564601] [<3faf704a>] zpci_event_availability+0x282/0x2f0 [ 1681.564605]
[Kernel-packages] [Bug 1895563] Re: Kernel Oops: Rsyncing to bcache device w/o backing cache kernel panic
Hey Brendan,
Thanks for reporting this bug.
It looks like the crashdump files didn't come through?
Could you please try to reproduce with the 5.8 kernel from Groovy on
your Bionic install?
These are the steps to install it.
Please remove the .list file as soon as you install the packages, to avoid
other packages from Groovy to be installed unintendly.
$ echo 'deb http://archive.ubuntu.com/ubuntu groovy main restricted' | sudo tee
/etc/apt/sources.list.d/groovy.list
deb http://archive.ubuntu.com/ubuntu groovy main restricted
$ sudo apt update
$ sudo apt install --dry-run
linux-{image,modules-extra,headers}-5.8.0-18-generic
$ sudo rm /etc/apt/sources.list.d/groovy.list
Once you're done with testing, you can remove the installed packages
with:
$ sudo apt purge linux-{image,modules,modules-
extra,headers}-5.8.0-18-generic
Please note there's an additional linux-modules package in this list (which is
a pulled as a dependency in the install command.)
You can also specify other packages if any are also pulled during the install
step, but testing it here it doesn't look like any other packages are pulled in.
Thanks,
Mauricio
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1895563
Title:
Kernel Oops: Rsyncing to bcache device w/o backing cache kernel panic
Status in linux package in Ubuntu:
Confirmed
Bug description:
Platform details:
1) version.log attached
2) lspci-vnvn.log attached
3) lsb_release -rd
Description:Ubuntu 18.04.5 LTS
Release:18.04
4) apt-cache policy bcache-tools
bcache-tools:
Installed: 1.0.8-2ubuntu0.18.04.1
Candidate: 1.0.8-2ubuntu0.18.04.1
Version table:
*** 1.0.8-2ubuntu0.18.04.1 500
500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64
Packages
100 /var/lib/dpkg/status
1.0.8-2build1 500
500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages
5) uname -a:
Linux timber4 4.15.0-117-generic #118-Ubuntu SMP Fri Sep 4 20:02:41 UTC 2020
x86_64 x86_64 x86_64 GNU/Linux
Short problem description:
Rsyncing from a 1.4TB home dir to a an new filesystem on a bcache
device without an attached cache eventually results in kernel panic.
What I expected to happen: no kernel panic.
Long problem description:
1) Devices / Filesystems:
bfd01: 8*4TB configured as RAID6 using md LVM2 volume group.
bfd02: 8*4TB configured as RAID6 using Dell PERC H810 LVM2 volume group.
The tree contains 1069685 files / dirs.
2) Steps to reproduce:
# Make the device, format and mount it
make-bcache -B /dev/vg-bfd02/delme01_bc
mkfs.xfs -f -L delme01bc /dev/bcache0
mount /dev/bcache0 /dev/bfd02/delme01bc
# Rsync
flags="-a --delete" ; info_cmd="--info=progress2" ; excludes="";
src=/mnt/bfd01/delme01 ; tgt=/mnt/bfd02/delme01bc/ ;
time rsync $flags $info_cmd $excludes $src/ $tgt/
...
# eventually kernel panic
Using incremental rsync it will kernel panic after reading about 21GB.
# If instead I use non-incremental rsync it will kernel panic after
reading about 1.2-1.3TB.
flags="--no-inc-recursive -ax -HAXS --delete" ; info_cmd="--info=progress2" ;
excludes="";
...
# eventually kernel panic
Additional detail:
1) I was *not* able to reproduce if bfd01/delm01bc was a target and
bfd02 was the source e.g.
# Rsync
flags="-a --delete" ; info_cmd="--info=progress2" ; excludes="";
src=/mnt/bfd02/delme01 ; tgt=/mnt/bfd01/delme01bc/ ;
time rsync $flags $info_cmd $excludes $src/ $tgt/
...
# rsync completes successfully
2) I was *not* able to reproduce if I attached and then detached a cache set:
ceho 'd3b93488-714e-4efa-af94-cd80fd2db11f' > /sys/block/bcache0/bcache/attach
echo 1 > /sys/block/bcache0/bcache/detach
...
time rsync $flags $info_cmd $excludes $src/ $tgt/
...
# rsync completes successfully
I have 11 compressed kernel crash dumps. I will upload 3 after filing this.
Let me know if you want the other 8.
ProblemType: KernelCrash
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-117-generic 4.15.0-117.118
ProcVersionSignature: Ubuntu 4.15.0-117.118-generic 4.15.18
Uname: Linux 4.15.0-117-generic x86_64
AlsaDevices:
total 0
crw-rw 1 root audio 116, 1 Sep 13 12:53 seq
crw-rw 1 root audio 116, 33 Sep 13 12:53 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
ApportVersion: 2.20.9-0ubuntu7.17
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord':
'arecord'
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq',
'/dev/snd/timer'] failed with exit code 1:
Date: Sat Sep 12 09:51:37 2020
HibernationDevice: RESUME=none
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
MachineType: Dell Inc. PowerEdge R620
PciMultimedia:
ProcFB: 0
[Kernel-packages] [Bug 1896482] 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/1896482 Title: acpi event detection crashes Status in linux package in Ubuntu: Confirmed Bug description: Right after booting, acpi lid open/close is detected as it should be by the kernel, but some time later it crashes, so I have to manually suspend the system. The traceback is here: Sep 20 11:35:33 laxmi kernel: [232492.303557] [ cut here ] Sep 20 11:35:33 laxmi kernel: [232492.303564] WARNING: CPU: 0 PID: 8302 at kernel/workqueue.c:1416 __queue_work+0x337/0x3f0 Sep 20 11:35:33 laxmi kernel: [232492.303565] Modules linked in: ccm rfcomm cmac algif_hash algif_skcipher af_alg bnep nls_iso8859_1 snd_soc_skl_hda_dsp snd_hda_codec_hdmi snd_soc_hdac_hdmi snd_hda_codec_realtek snd_soc_dmic snd_hda_codec_generic snd_sof_pci mei_hdcp x86_pkg_temp_thermal intel_powerclamp intel_rapl_msr coretemp snd_sof_intel_hda_common snd_soc_hdac_hda snd_sof_intel_hda kvm_intel snd_sof_intel_byt snd_sof_intel_ipc kvm snd_sof snd_sof_xtensa_dsp snd_hda_ext_core snd_soc_acpi_intel_match snd_soc_acpi snd_soc_core snd_compress ac97_bus snd_pcm_dmaengine joydev crct10dif_pclmul ghash_clmulni_intel snd_hda_intel aesni_intel snd_intel_dspcfg crypto_simd iwlmvm cryptd snd_hda_codec glue_helper rapl mac80211 snd_hda_core snd_seq_midi snd_hwdep snd_seq_midi_event libarc4 intel_cstate uvcvideo snd_rawmidi i915 snd_pcm videobuf2_vmalloc input_leds thinkpad_acpi btusb videobuf2_memops serio_raw btrtl videobuf2_v4l2 snd_seq btbcm btintel nvram videobuf2_common iwlwifi processor_thermal_device bluetooth videodev Sep 20 11:35:33 laxmi kernel: [232492.303600] drm_kms_helper mc wmi_bmof i2c_algo_bit intel_rapl_common fb_sys_fops ucsi_acpi intel_wmi_thunderbolt ecdh_generic ledtrig_audio typec_ucsi mei_me syscopyarea hid_multitouch snd_seq_device sysfillrect cfg80211 ecc sysimgblt mei intel_soc_dts_iosf typec snd_timer snd soundcore int3403_thermal int340x_thermal_zone acpi_pad intel_hid int3400_thermal acpi_thermal_rel sparse_keymap mac_hid sch_fq_codel parport_pc ppdev lp parport drm ip_tables x_tables autofs4 hid_generic crc32_pclmul nvme psmouse e1000e i2c_i801 thunderbolt intel_lpss_pci intel_lpss nvme_core idma64 virt_dma i2c_hid hid wmi video pinctrl_cannonlake pinctrl_intel Sep 20 11:35:33 laxmi kernel: [232492.303628] CPU: 0 PID: 8302 Comm: kworker/0:0 Not tainted 5.4.0-47-generic #51-Ubuntu Sep 20 11:35:33 laxmi kernel: [232492.303629] Hardware name: LENOVO 20U9001NUS/20U9001NUS, BIOS N2WET19W (1.09 ) 07/01/2020 Sep 20 11:35:33 laxmi kernel: [232492.303632] Workqueue: kec_query acpi_ec_event_processor Sep 20 11:35:33 laxmi kernel: [232492.303635] RIP: 0010:__queue_work+0x337/0x3f0 Sep 20 11:35:33 laxmi kernel: [232492.303637] Code: ff 49 8b 9d a0 00 00 00 e9 aa fd ff ff 65 8b 05 e7 59 15 6d a9 00 01 1f 00 75 0f 65 48 8b 3c 25 c0 6b 01 00 f6 47 24 20 75 25 <0f> 0b 48 83 c4 18 5b 41 5c 41 5d 41 5e 41 5f 5d c3 0f 0b e9 fd fd Sep 20 11:35:33 laxmi kernel: [232492.303638] RSP: 0018:b16bc0ebb8f8 EFLAGS: 00010087 Sep 20 11:35:33 laxmi kernel: [232492.303640] RAX: 9a2477432600 RBX: 0002 RCX: 0004 Sep 20 11:35:33 laxmi kernel: [232492.303641] RDX: 9a2475af4a90 RSI: 9a2475b03200 RDI: 9a2430215f00 Sep 20 11:35:33 laxmi kernel: [232492.303642] RBP: b16bc0ebb938 R08: R09: 0007 Sep 20 11:35:33 laxmi kernel: [232492.303643] R10: 9a24755ad678 R11: R12: 9a2475af4a00 Sep 20 11:35:33 laxmi kernel: [232492.303643] R13: 9a2475b03200 R14: 2000 R15: 9a2475af4a90 Sep 20 11:35:33 laxmi kernel: [232492.303645] FS: () GS:9a247740() knlGS: Sep 20 11:35:33 laxmi kernel: [232492.303646] CS: 0010 DS: ES: CR0: 80050033 Sep 20 11:35:33 laxmi kernel: [232492.303647] CR2: 00c42098b000 CR3: 00018520a003 CR4: 003606f0 Sep 20 11:35:33 laxmi kernel: [232492.303648] Call Trace: Sep 20 11:35:33 laxmi kernel: [232492.303654] ? acpi_os_release_lock+0xe/0x10 Sep 20 11:35:33 laxmi kernel: [232492.303657] queue_work_on+0x3b/0x50 Sep 20 11:35:33 laxmi kernel: [232492.303659] advance_transaction+0x2b9/0x620 Sep 20 11:35:33 laxmi kernel: [232492.303661] acpi_ec_transaction+0x16c/0x3c0 Sep 20 11:35:33 laxmi kernel: [232492.303663] acpi_ec_space_handler+0xd4/0x280 Sep 20 11:35:33 laxmi kernel: [232492.303666] acpi_ev_address_space_dispatch+0x2f7/0x39f Sep 20 11:35:33 laxmi kernel: [232492.303668] ? ec_transaction+0x70/0x70 Sep 20 11:35:33 laxmi kernel: [232492.303670] acpi_ex_access_region+0x454/0x4ed Sep 20 11:35:33 laxmi kernel: [232492.303672] acpi_ex_field_datum_io+0x18a/0x42d Sep 20
[Kernel-packages] [Bug 1896482] [NEW] acpi event detection crashes
Public bug reported: Right after booting, acpi lid open/close is detected as it should be by the kernel, but some time later it crashes, so I have to manually suspend the system. The traceback is here: Sep 20 11:35:33 laxmi kernel: [232492.303557] [ cut here ] Sep 20 11:35:33 laxmi kernel: [232492.303564] WARNING: CPU: 0 PID: 8302 at kernel/workqueue.c:1416 __queue_work+0x337/0x3f0 Sep 20 11:35:33 laxmi kernel: [232492.303565] Modules linked in: ccm rfcomm cmac algif_hash algif_skcipher af_alg bnep nls_iso8859_1 snd_soc_skl_hda_dsp snd_hda_codec_hdmi snd_soc_hdac_hdmi snd_hda_codec_realtek snd_soc_dmic snd_hda_codec_generic snd_sof_pci mei_hdcp x86_pkg_temp_thermal intel_powerclamp intel_rapl_msr coretemp snd_sof_intel_hda_common snd_soc_hdac_hda snd_sof_intel_hda kvm_intel snd_sof_intel_byt snd_sof_intel_ipc kvm snd_sof snd_sof_xtensa_dsp snd_hda_ext_core snd_soc_acpi_intel_match snd_soc_acpi snd_soc_core snd_compress ac97_bus snd_pcm_dmaengine joydev crct10dif_pclmul ghash_clmulni_intel snd_hda_intel aesni_intel snd_intel_dspcfg crypto_simd iwlmvm cryptd snd_hda_codec glue_helper rapl mac80211 snd_hda_core snd_seq_midi snd_hwdep snd_seq_midi_event libarc4 intel_cstate uvcvideo snd_rawmidi i915 snd_pcm videobuf2_vmalloc input_leds thinkpad_acpi btusb videobuf2_memops serio_raw btrtl videobuf2_v4l2 snd_seq btbcm btintel nvram videobuf2_common iwlwifi processor_thermal_device bluetooth videodev Sep 20 11:35:33 laxmi kernel: [232492.303600] drm_kms_helper mc wmi_bmof i2c_algo_bit intel_rapl_common fb_sys_fops ucsi_acpi intel_wmi_thunderbolt ecdh_generic ledtrig_audio typec_ucsi mei_me syscopyarea hid_multitouch snd_seq_device sysfillrect cfg80211 ecc sysimgblt mei intel_soc_dts_iosf typec snd_timer snd soundcore int3403_thermal int340x_thermal_zone acpi_pad intel_hid int3400_thermal acpi_thermal_rel sparse_keymap mac_hid sch_fq_codel parport_pc ppdev lp parport drm ip_tables x_tables autofs4 hid_generic crc32_pclmul nvme psmouse e1000e i2c_i801 thunderbolt intel_lpss_pci intel_lpss nvme_core idma64 virt_dma i2c_hid hid wmi video pinctrl_cannonlake pinctrl_intel Sep 20 11:35:33 laxmi kernel: [232492.303628] CPU: 0 PID: 8302 Comm: kworker/0:0 Not tainted 5.4.0-47-generic #51-Ubuntu Sep 20 11:35:33 laxmi kernel: [232492.303629] Hardware name: LENOVO 20U9001NUS/20U9001NUS, BIOS N2WET19W (1.09 ) 07/01/2020 Sep 20 11:35:33 laxmi kernel: [232492.303632] Workqueue: kec_query acpi_ec_event_processor Sep 20 11:35:33 laxmi kernel: [232492.303635] RIP: 0010:__queue_work+0x337/0x3f0 Sep 20 11:35:33 laxmi kernel: [232492.303637] Code: ff 49 8b 9d a0 00 00 00 e9 aa fd ff ff 65 8b 05 e7 59 15 6d a9 00 01 1f 00 75 0f 65 48 8b 3c 25 c0 6b 01 00 f6 47 24 20 75 25 <0f> 0b 48 83 c4 18 5b 41 5c 41 5d 41 5e 41 5f 5d c3 0f 0b e9 fd fd Sep 20 11:35:33 laxmi kernel: [232492.303638] RSP: 0018:b16bc0ebb8f8 EFLAGS: 00010087 Sep 20 11:35:33 laxmi kernel: [232492.303640] RAX: 9a2477432600 RBX: 0002 RCX: 0004 Sep 20 11:35:33 laxmi kernel: [232492.303641] RDX: 9a2475af4a90 RSI: 9a2475b03200 RDI: 9a2430215f00 Sep 20 11:35:33 laxmi kernel: [232492.303642] RBP: b16bc0ebb938 R08: R09: 0007 Sep 20 11:35:33 laxmi kernel: [232492.303643] R10: 9a24755ad678 R11: R12: 9a2475af4a00 Sep 20 11:35:33 laxmi kernel: [232492.303643] R13: 9a2475b03200 R14: 2000 R15: 9a2475af4a90 Sep 20 11:35:33 laxmi kernel: [232492.303645] FS: () GS:9a247740() knlGS: Sep 20 11:35:33 laxmi kernel: [232492.303646] CS: 0010 DS: ES: CR0: 80050033 Sep 20 11:35:33 laxmi kernel: [232492.303647] CR2: 00c42098b000 CR3: 00018520a003 CR4: 003606f0 Sep 20 11:35:33 laxmi kernel: [232492.303648] Call Trace: Sep 20 11:35:33 laxmi kernel: [232492.303654] ? acpi_os_release_lock+0xe/0x10 Sep 20 11:35:33 laxmi kernel: [232492.303657] queue_work_on+0x3b/0x50 Sep 20 11:35:33 laxmi kernel: [232492.303659] advance_transaction+0x2b9/0x620 Sep 20 11:35:33 laxmi kernel: [232492.303661] acpi_ec_transaction+0x16c/0x3c0 Sep 20 11:35:33 laxmi kernel: [232492.303663] acpi_ec_space_handler+0xd4/0x280 Sep 20 11:35:33 laxmi kernel: [232492.303666] acpi_ev_address_space_dispatch+0x2f7/0x39f Sep 20 11:35:33 laxmi kernel: [232492.303668] ? ec_transaction+0x70/0x70 Sep 20 11:35:33 laxmi kernel: [232492.303670] acpi_ex_access_region+0x454/0x4ed Sep 20 11:35:33 laxmi kernel: [232492.303672] acpi_ex_field_datum_io+0x18a/0x42d Sep 20 11:35:33 laxmi kernel: [232492.303673] acpi_ex_extract_from_field+0x172/0x320 Sep 20 11:35:33 laxmi kernel: [232492.303675] acpi_ex_read_data_from_field+0x30f/0x361 Sep 20 11:35:33 laxmi kernel: [232492.303677] acpi_ex_resolve_node_to_value+0x3a7/0x4dd Sep 20 11:35:33 laxmi kernel: [232492.303679] acpi_ex_resolve_to_value+0x3c3/0x472 Sep 20 11:35:33 laxmi kernel: [232492.303681]
[Kernel-packages] [Bug 1887674] Re: Introduce the new NVIDIA 450-server and the 450 UDA series
This bug was fixed in the package nvidia-graphics-drivers-450-server - 450.51.06-0ubuntu0.18.04.2 --- nvidia-graphics-drivers-450-server (450.51.06-0ubuntu0.18.04.2) bionic; urgency=medium * debian/dkms_nvidia/patches/buildfix_kernel_5.8.patch: - Fix build failure (LP: #1887674). nvidia-graphics-drivers-450-server (450.51.06-0ubuntu0.18.04.1) bionic; urgency=medium * Initial release (LP: #1887674). -- Alberto Milone Fri, 28 Aug 2020 16:02:02 +0200 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-restricted-modules in Ubuntu. https://bugs.launchpad.net/bugs/1887674 Title: Introduce the new NVIDIA 450-server and the 450 UDA series Status in OEM Priority Project: New Status in linux package in Ubuntu: Triaged Status in linux-restricted-modules package in Ubuntu: Triaged Status in nvidia-graphics-drivers-450 package in Ubuntu: In Progress Status in nvidia-graphics-drivers-450-server package in Ubuntu: In Progress Status in linux source package in Bionic: Fix Released Status in linux-restricted-modules source package in Bionic: Fix Released Status in nvidia-graphics-drivers-450 source package in Bionic: Fix Released Status in nvidia-graphics-drivers-450-server source package in Bionic: Fix Released Status in linux source package in Focal: Fix Released Status in linux-restricted-modules source package in Focal: Fix Released Status in nvidia-graphics-drivers-450 source package in Focal: Fix Released Status in nvidia-graphics-drivers-450-server source package in Focal: Fix Released Bug description: [Impact] These releases provide both bug fixes and new features, and we would like to make sure all of our users have access to these improvements. See the changelog entry below for a full list of changes and bugs. [Test Case] The following development and SRU process was followed: https://wiki.ubuntu.com/NVidiaUpdates Certification test suite must pass on a range of hardware: https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu The QA team that executed the tests will be in charge of attaching the artifacts and console output of the appropriate run to the bug. nVidia maintainers team members will not mark ‘verification-done’ until this has happened. [Regression Potential] In order to mitigate the regression potential, the results of the aforementioned system level tests are attached to this bug. [Discussion] To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1887674/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1887674] Re: Introduce the new NVIDIA 450-server and the 450 UDA series
This bug was fixed in the package nvidia-graphics-drivers-450-server - 450.51.06-0ubuntu0.20.04.2 --- nvidia-graphics-drivers-450-server (450.51.06-0ubuntu0.20.04.2) focal; urgency=medium * debian/dkms_nvidia/patches/buildfix_kernel_5.8.patch: - Fix build failure (LP: #1887674). nvidia-graphics-drivers-450-server (450.51.06-0ubuntu0.20.04.1) focal; urgency=medium * Initial release (LP: #1887674). -- Alberto Milone Fri, 28 Aug 2020 15:59:50 +0200 ** Changed in: nvidia-graphics-drivers-450 (Ubuntu Bionic) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-restricted-modules in Ubuntu. https://bugs.launchpad.net/bugs/1887674 Title: Introduce the new NVIDIA 450-server and the 450 UDA series Status in OEM Priority Project: New Status in linux package in Ubuntu: Triaged Status in linux-restricted-modules package in Ubuntu: Triaged Status in nvidia-graphics-drivers-450 package in Ubuntu: In Progress Status in nvidia-graphics-drivers-450-server package in Ubuntu: In Progress Status in linux source package in Bionic: Fix Released Status in linux-restricted-modules source package in Bionic: Fix Released Status in nvidia-graphics-drivers-450 source package in Bionic: Fix Released Status in nvidia-graphics-drivers-450-server source package in Bionic: Fix Released Status in linux source package in Focal: Fix Released Status in linux-restricted-modules source package in Focal: Fix Released Status in nvidia-graphics-drivers-450 source package in Focal: Fix Released Status in nvidia-graphics-drivers-450-server source package in Focal: Fix Released Bug description: [Impact] These releases provide both bug fixes and new features, and we would like to make sure all of our users have access to these improvements. See the changelog entry below for a full list of changes and bugs. [Test Case] The following development and SRU process was followed: https://wiki.ubuntu.com/NVidiaUpdates Certification test suite must pass on a range of hardware: https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu The QA team that executed the tests will be in charge of attaching the artifacts and console output of the appropriate run to the bug. nVidia maintainers team members will not mark ‘verification-done’ until this has happened. [Regression Potential] In order to mitigate the regression potential, the results of the aforementioned system level tests are attached to this bug. [Discussion] To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1887674/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1887674] Re: Introduce the new NVIDIA 450-server and the 450 UDA series
This bug was fixed in the package nvidia-graphics-drivers-450 - 450.66-0ubuntu0.20.04.1 --- nvidia-graphics-drivers-450 (450.66-0ubuntu0.20.04.1) focal; urgency=medium * Initial release (LP: #1887674). -- Alberto Milone Tue, 14 Jul 2020 10:12:39 +0200 ** Changed in: nvidia-graphics-drivers-450 (Ubuntu Focal) Status: In Progress => Fix Released ** Changed in: nvidia-graphics-drivers-450-server (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-restricted-modules in Ubuntu. https://bugs.launchpad.net/bugs/1887674 Title: Introduce the new NVIDIA 450-server and the 450 UDA series Status in OEM Priority Project: New Status in linux package in Ubuntu: Triaged Status in linux-restricted-modules package in Ubuntu: Triaged Status in nvidia-graphics-drivers-450 package in Ubuntu: In Progress Status in nvidia-graphics-drivers-450-server package in Ubuntu: In Progress Status in linux source package in Bionic: Fix Released Status in linux-restricted-modules source package in Bionic: Fix Released Status in nvidia-graphics-drivers-450 source package in Bionic: Fix Released Status in nvidia-graphics-drivers-450-server source package in Bionic: Fix Released Status in linux source package in Focal: Fix Released Status in linux-restricted-modules source package in Focal: Fix Released Status in nvidia-graphics-drivers-450 source package in Focal: Fix Released Status in nvidia-graphics-drivers-450-server source package in Focal: Fix Released Bug description: [Impact] These releases provide both bug fixes and new features, and we would like to make sure all of our users have access to these improvements. See the changelog entry below for a full list of changes and bugs. [Test Case] The following development and SRU process was followed: https://wiki.ubuntu.com/NVidiaUpdates Certification test suite must pass on a range of hardware: https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu The QA team that executed the tests will be in charge of attaching the artifacts and console output of the appropriate run to the bug. nVidia maintainers team members will not mark ‘verification-done’ until this has happened. [Regression Potential] In order to mitigate the regression potential, the results of the aforementioned system level tests are attached to this bug. [Discussion] To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1887674/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1891222] Re: Only notify Hyper-V for die events that are oops
This bug was fixed in the package linux-azure - 5.4.0-1026.26 --- linux-azure (5.4.0-1026.26) focal; urgency=medium * focal/linux-azure: 5.4.0-1026.26 -proposed tracker (LP: #1894641) * Mellanox Check For Write Combining Support (LP: #1874503) - IB/mlx5: Align usage of QP1 create flags with rest of mlx5 defines - IB/mlx5: Test write combining support * Enable Invariant TSC Support (LP: #1875467) - x86/hyperv: Allow guests to enable InvariantTSC - clocksource/drivers/hyper-v: Set TSC clocksource as default w/ InvariantTSC * Only notify Hyper-V for die events that are oops (LP: #1891222) - Drivers: hv: vmbus: Only notify Hyper-V for die events that are oops * speed for CX4 VF showing as unknown in ethtool output (LP: #1876770) - net/mlx5: Expose link speed directly - net/mlx5: Expose port speed when possible - net/mlx5: Tidy up and fix reverse christmas ordring [ Ubuntu: 5.4.0-48.52 ] * focal/linux: 5.4.0-48.52 -proposed tracker (LP: #1894654) * mm/slub kernel oops on focal kernel 5.4.0-45 (LP: #1895109) - SAUCE: Revert "mm/slub: fix a memory leak in sysfs_slab_add()" * Packaging resync (LP: #1786013) - update dkms package versions - update dkms package versions * Introduce the new NVIDIA 450-server and the 450 UDA series (LP: #1887674) - [packaging] add signed modules for nvidia 450 and 450-server * [UBUNTU 20.04] zPCI attach/detach issues with PF/VF linking support (LP: #1892849) - s390/pci: fix zpci_bus_link_virtfn() - s390/pci: re-introduce zpci_remove_device() - s390/pci: fix PF/VF linking on hot plug * [UBUNTU 20.04] kernel: s390/cpum_cf,perf: changeDFLT_CCERROR counter name (LP: #1891454) - s390/cpum_cf, perf: change DFLT_CCERROR counter name * [UBUNTU 20.04] zPCI: Enabling of a reserved PCI function regression introduced by multi-function support (LP: #1891437) - s390/pci: fix enabling a reserved PCI function * CVE-2020-12888 - vfio/type1: Support faulting PFNMAP vmas - vfio-pci: Fault mmaps to enable vma tracking - vfio-pci: Invalidate mmaps and block MMIO access on disabled memory * [Hyper-V] VSS and File Copy daemons intermittently fails to start (LP: #1891224) - [Packaging] Bind hv_vss_daemon startup to hv_vss device - [Packaging] bind hv_fcopy_daemon startup to hv_fcopy device * alsa/hdmi: support nvidia mst hdmi/dp audio (LP: #1867704) - ALSA: hda - Rename snd_hda_pin_sense to snd_hda_jack_pin_sense - ALSA: hda - Add DP-MST jack support - ALSA: hda - Add DP-MST support for non-acomp codecs - ALSA: hda - Add DP-MST support for NVIDIA codecs - ALSA: hda: hdmi - fix regression in connect list handling - ALSA: hda: hdmi - fix kernel oops caused by invalid PCM idx - ALSA: hda: hdmi - preserve non-MST PCM routing for Intel platforms - ALSA: hda: hdmi - Keep old slot assignment behavior for Intel platforms - ALSA: hda - Fix DP-MST support for NVIDIA codecs * Focal update: v5.4.60 upstream stable release (LP: #1892899) - smb3: warn on confusing error scenario with sec=krb5 - genirq/affinity: Make affinity setting if activated opt-in - genirq/PM: Always unlock IRQ descriptor in rearm_wake_irq() - PCI: hotplug: ACPI: Fix context refcounting in acpiphp_grab_context() - PCI: Add device even if driver attach failed - PCI: qcom: Define some PARF params needed for ipq8064 SoC - PCI: qcom: Add support for tx term offset for rev 2.1.0 - btrfs: allow use of global block reserve for balance item deletion - btrfs: free anon block device right after subvolume deletion - btrfs: don't allocate anonymous block device for user invisible roots - btrfs: ref-verify: fix memory leak in add_block_entry - btrfs: stop incremening log_batch for the log root tree when syncing log - btrfs: remove no longer needed use of log_writers for the log root tree - btrfs: don't traverse into the seed devices in show_devname - btrfs: open device without device_list_mutex - btrfs: move the chunk_mutex in btrfs_read_chunk_tree - btrfs: relocation: review the call sites which can be interrupted by signal - btrfs: add missing check for nocow and compression inode flags - btrfs: avoid possible signal interruption of btrfs_drop_snapshot() on relocation tree - btrfs: sysfs: use NOFS for device creation - btrfs: don't WARN if we abort a transaction with EROFS - btrfs: fix race between page release and a fast fsync - btrfs: fix messages after changing compression level by remount - btrfs: only search for left_info if there is no right_info in try_merge_free_space - btrfs: inode: fix NULL pointer dereference if inode doesn't need compression - btrfs: fix memory leaks after failure to lookup checksums during inode logging - btrfs: make sure SB_I_VERSION doesn't get unset by remount - btrfs: fix return value mixup in
[Kernel-packages] [Bug 1891224] Re: [Hyper-V] VSS and File Copy daemons intermittently fails to start
This bug was fixed in the package linux - 4.4.0-190.220 --- linux (4.4.0-190.220) xenial; urgency=medium * xenial/linux: 4.4.0-190.220 -proposed tracker (LP: #1893431) * Packaging resync (LP: #1786013) - [Packaging] update helper scripts * [Hyper-V] VSS and File Copy daemons intermittently fails to start (LP: #1891224) - [Packaging] Bind hv_vss_daemon startup to hv_vss device - [Packaging] bind hv_fcopy_daemon startup to hv_fcopy device * CVE-2019-20811 - net-sysfs: call dev_hold if kobject_init_and_add success * CVE-2020-0067 - f2fs: fix to avoid memory leakage in f2fs_listxattr * CVE-2019-9453 - f2fs: fix to avoid accessing xattr across the boundary * Xenial update: 4.4.233 upstream stable release (LP: #1892822) - media: rc: prevent memory leak in cx23888_ir_probe - ath9k_htc: release allocated buffer if timed out - ath9k: release allocated buffer if timed out - nfs: Move call to security_inode_listsecurity into nfs_listxattr - PCI/ASPM: Disable ASPM on ASMedia ASM1083/1085 PCIe-to-PCI bridge - drm/amdgpu: Prevent kernel-infoleak in amdgpu_info_ioctl() - drm: hold gem reference until object is no longer accessed - f2fs: check memory boundary by insane namelen - f2fs: check if file namelen exceeds max value - ARM: 8986/1: hw_breakpoint: Don't invoke overflow handler on uaccess watchpoints - fbdev: Detect integer underflow at "struct fbcon_ops"->clear_margins. - rds: Prevent kernel-infoleak in rds_notify_queue_get() - net/x25: Fix x25_neigh refcnt leak when x25 disconnect - net/x25: Fix null-ptr-deref in x25_disconnect - sh: Fix validation of system call number - net: lan78xx: add missing endpoint sanity check - net: lan78xx: fix transfer-buffer memory leak - mlxsw: core: Increase scope of RCU read-side critical section - mac80211: mesh: Free ie data when leaving mesh - nfc: s3fwrn5: add missing release on skb in s3fwrn5_recv_frame - net: ethernet: ravb: exit if re-initialization fails in tx timeout - Revert "i2c: cadence: Fix the hold bit setting" - xen-netfront: fix potential deadlock in xennet_remove() - x86/i8259: Use printk_deferred() to prevent deadlock - random32: update the net random state on interrupt and activity - ARM: percpu.h: fix build error - random: fix circular include dependency on arm64 after addition of percpu.h - random32: remove net_rand_state from the latent entropy gcc plugin - random32: move the pseudo-random 32-bit definitions to prandom.h - ext4: fix direct I/O read error - USB: serial: qcserial: add EM7305 QDL product ID - ALSA: seq: oss: Serialize ioctls - Bluetooth: Fix slab-out-of-bounds read in hci_extended_inquiry_result_evt() - Bluetooth: Prevent out-of-bounds read in hci_inquiry_result_evt() - Bluetooth: Prevent out-of-bounds read in hci_inquiry_result_with_rssi_evt() - vgacon: Fix for missing check in scrollback handling - mtd: properly check all write ioctls for permissions - net/9p: validate fds in p9_fd_open - drm/nouveau/fbcon: fix module unload when fbcon init has failed for some reason - cfg80211: check vendor command doit pointer before use - igb: reinit_locked() should be called with rtnl_lock - atm: fix atm_dev refcnt leaks in atmtcp_remove_persistent - tools lib traceevent: Fix memory leak in process_dynamic_array_len - binder: Prevent context manager from incrementing ref 0 - ipv4: Silence suspicious RCU usage warning - ipv6: fix memory leaks on IPV6_ADDRFORM path - Revert "vxlan: fix tos value before xmit" - net: lan78xx: replace bogus endpoint lookup - usb: hso: check for return value in hso_serial_common_create() - vxlan: Ensure FDB dump is performed under RCU - Smack: fix use-after-free in smk_write_relabel_self() - tracepoint: Mark __tracepoint_string's __used - udp: drop corrupt packets earlier to avoid data corruption - gpio: fix oops resulting from calling of_get_named_gpio(NULL, ...) - EDAC: Fix reference count leaks - m68k: mac: Don't send IOP message until channel is idle - m68k: mac: Fix IOP status/control register writes - ARM: at91: pm: add missing put_device() call in at91_pm_sram_init() - ARM: socfpga: PM: add missing put_device() call in socfpga_setup_ocram_self_refresh() - drm/tilcdc: fix leak & null ref in panel_connector_get_modes - Bluetooth: add a mutex lock to avoid UAF in do_enale_set - fs/btrfs: Add cond_resched() for try_release_extent_mapping() stalls - drm/radeon: Fix reference count leaks caused by pm_runtime_get_sync - video: fbdev: neofb: fix memory leak in neo_scan_monitor() - drm/nouveau: fix multiple instances of reference count leaks - drm/debugfs: fix plain echo to connector "force" attribute - mm/mmap.c: Add cond_resched() for exit_mmap() CPU stalls - brcmfmac: To fix Bss
[Kernel-packages] [Bug 1875467] Re: Enable Invariant TSC Support
This bug was fixed in the package linux-azure - 5.4.0-1026.26 --- linux-azure (5.4.0-1026.26) focal; urgency=medium * focal/linux-azure: 5.4.0-1026.26 -proposed tracker (LP: #1894641) * Mellanox Check For Write Combining Support (LP: #1874503) - IB/mlx5: Align usage of QP1 create flags with rest of mlx5 defines - IB/mlx5: Test write combining support * Enable Invariant TSC Support (LP: #1875467) - x86/hyperv: Allow guests to enable InvariantTSC - clocksource/drivers/hyper-v: Set TSC clocksource as default w/ InvariantTSC * Only notify Hyper-V for die events that are oops (LP: #1891222) - Drivers: hv: vmbus: Only notify Hyper-V for die events that are oops * speed for CX4 VF showing as unknown in ethtool output (LP: #1876770) - net/mlx5: Expose link speed directly - net/mlx5: Expose port speed when possible - net/mlx5: Tidy up and fix reverse christmas ordring [ Ubuntu: 5.4.0-48.52 ] * focal/linux: 5.4.0-48.52 -proposed tracker (LP: #1894654) * mm/slub kernel oops on focal kernel 5.4.0-45 (LP: #1895109) - SAUCE: Revert "mm/slub: fix a memory leak in sysfs_slab_add()" * Packaging resync (LP: #1786013) - update dkms package versions - update dkms package versions * Introduce the new NVIDIA 450-server and the 450 UDA series (LP: #1887674) - [packaging] add signed modules for nvidia 450 and 450-server * [UBUNTU 20.04] zPCI attach/detach issues with PF/VF linking support (LP: #1892849) - s390/pci: fix zpci_bus_link_virtfn() - s390/pci: re-introduce zpci_remove_device() - s390/pci: fix PF/VF linking on hot plug * [UBUNTU 20.04] kernel: s390/cpum_cf,perf: changeDFLT_CCERROR counter name (LP: #1891454) - s390/cpum_cf, perf: change DFLT_CCERROR counter name * [UBUNTU 20.04] zPCI: Enabling of a reserved PCI function regression introduced by multi-function support (LP: #1891437) - s390/pci: fix enabling a reserved PCI function * CVE-2020-12888 - vfio/type1: Support faulting PFNMAP vmas - vfio-pci: Fault mmaps to enable vma tracking - vfio-pci: Invalidate mmaps and block MMIO access on disabled memory * [Hyper-V] VSS and File Copy daemons intermittently fails to start (LP: #1891224) - [Packaging] Bind hv_vss_daemon startup to hv_vss device - [Packaging] bind hv_fcopy_daemon startup to hv_fcopy device * alsa/hdmi: support nvidia mst hdmi/dp audio (LP: #1867704) - ALSA: hda - Rename snd_hda_pin_sense to snd_hda_jack_pin_sense - ALSA: hda - Add DP-MST jack support - ALSA: hda - Add DP-MST support for non-acomp codecs - ALSA: hda - Add DP-MST support for NVIDIA codecs - ALSA: hda: hdmi - fix regression in connect list handling - ALSA: hda: hdmi - fix kernel oops caused by invalid PCM idx - ALSA: hda: hdmi - preserve non-MST PCM routing for Intel platforms - ALSA: hda: hdmi - Keep old slot assignment behavior for Intel platforms - ALSA: hda - Fix DP-MST support for NVIDIA codecs * Focal update: v5.4.60 upstream stable release (LP: #1892899) - smb3: warn on confusing error scenario with sec=krb5 - genirq/affinity: Make affinity setting if activated opt-in - genirq/PM: Always unlock IRQ descriptor in rearm_wake_irq() - PCI: hotplug: ACPI: Fix context refcounting in acpiphp_grab_context() - PCI: Add device even if driver attach failed - PCI: qcom: Define some PARF params needed for ipq8064 SoC - PCI: qcom: Add support for tx term offset for rev 2.1.0 - btrfs: allow use of global block reserve for balance item deletion - btrfs: free anon block device right after subvolume deletion - btrfs: don't allocate anonymous block device for user invisible roots - btrfs: ref-verify: fix memory leak in add_block_entry - btrfs: stop incremening log_batch for the log root tree when syncing log - btrfs: remove no longer needed use of log_writers for the log root tree - btrfs: don't traverse into the seed devices in show_devname - btrfs: open device without device_list_mutex - btrfs: move the chunk_mutex in btrfs_read_chunk_tree - btrfs: relocation: review the call sites which can be interrupted by signal - btrfs: add missing check for nocow and compression inode flags - btrfs: avoid possible signal interruption of btrfs_drop_snapshot() on relocation tree - btrfs: sysfs: use NOFS for device creation - btrfs: don't WARN if we abort a transaction with EROFS - btrfs: fix race between page release and a fast fsync - btrfs: fix messages after changing compression level by remount - btrfs: only search for left_info if there is no right_info in try_merge_free_space - btrfs: inode: fix NULL pointer dereference if inode doesn't need compression - btrfs: fix memory leaks after failure to lookup checksums during inode logging - btrfs: make sure SB_I_VERSION doesn't get unset by remount - btrfs: fix return value mixup in
[Kernel-packages] [Bug 1874503] Re: Mellanox Check For Write Combining Support
This bug was fixed in the package linux-azure - 5.4.0-1026.26 --- linux-azure (5.4.0-1026.26) focal; urgency=medium * focal/linux-azure: 5.4.0-1026.26 -proposed tracker (LP: #1894641) * Mellanox Check For Write Combining Support (LP: #1874503) - IB/mlx5: Align usage of QP1 create flags with rest of mlx5 defines - IB/mlx5: Test write combining support * Enable Invariant TSC Support (LP: #1875467) - x86/hyperv: Allow guests to enable InvariantTSC - clocksource/drivers/hyper-v: Set TSC clocksource as default w/ InvariantTSC * Only notify Hyper-V for die events that are oops (LP: #1891222) - Drivers: hv: vmbus: Only notify Hyper-V for die events that are oops * speed for CX4 VF showing as unknown in ethtool output (LP: #1876770) - net/mlx5: Expose link speed directly - net/mlx5: Expose port speed when possible - net/mlx5: Tidy up and fix reverse christmas ordring [ Ubuntu: 5.4.0-48.52 ] * focal/linux: 5.4.0-48.52 -proposed tracker (LP: #1894654) * mm/slub kernel oops on focal kernel 5.4.0-45 (LP: #1895109) - SAUCE: Revert "mm/slub: fix a memory leak in sysfs_slab_add()" * Packaging resync (LP: #1786013) - update dkms package versions - update dkms package versions * Introduce the new NVIDIA 450-server and the 450 UDA series (LP: #1887674) - [packaging] add signed modules for nvidia 450 and 450-server * [UBUNTU 20.04] zPCI attach/detach issues with PF/VF linking support (LP: #1892849) - s390/pci: fix zpci_bus_link_virtfn() - s390/pci: re-introduce zpci_remove_device() - s390/pci: fix PF/VF linking on hot plug * [UBUNTU 20.04] kernel: s390/cpum_cf,perf: changeDFLT_CCERROR counter name (LP: #1891454) - s390/cpum_cf, perf: change DFLT_CCERROR counter name * [UBUNTU 20.04] zPCI: Enabling of a reserved PCI function regression introduced by multi-function support (LP: #1891437) - s390/pci: fix enabling a reserved PCI function * CVE-2020-12888 - vfio/type1: Support faulting PFNMAP vmas - vfio-pci: Fault mmaps to enable vma tracking - vfio-pci: Invalidate mmaps and block MMIO access on disabled memory * [Hyper-V] VSS and File Copy daemons intermittently fails to start (LP: #1891224) - [Packaging] Bind hv_vss_daemon startup to hv_vss device - [Packaging] bind hv_fcopy_daemon startup to hv_fcopy device * alsa/hdmi: support nvidia mst hdmi/dp audio (LP: #1867704) - ALSA: hda - Rename snd_hda_pin_sense to snd_hda_jack_pin_sense - ALSA: hda - Add DP-MST jack support - ALSA: hda - Add DP-MST support for non-acomp codecs - ALSA: hda - Add DP-MST support for NVIDIA codecs - ALSA: hda: hdmi - fix regression in connect list handling - ALSA: hda: hdmi - fix kernel oops caused by invalid PCM idx - ALSA: hda: hdmi - preserve non-MST PCM routing for Intel platforms - ALSA: hda: hdmi - Keep old slot assignment behavior for Intel platforms - ALSA: hda - Fix DP-MST support for NVIDIA codecs * Focal update: v5.4.60 upstream stable release (LP: #1892899) - smb3: warn on confusing error scenario with sec=krb5 - genirq/affinity: Make affinity setting if activated opt-in - genirq/PM: Always unlock IRQ descriptor in rearm_wake_irq() - PCI: hotplug: ACPI: Fix context refcounting in acpiphp_grab_context() - PCI: Add device even if driver attach failed - PCI: qcom: Define some PARF params needed for ipq8064 SoC - PCI: qcom: Add support for tx term offset for rev 2.1.0 - btrfs: allow use of global block reserve for balance item deletion - btrfs: free anon block device right after subvolume deletion - btrfs: don't allocate anonymous block device for user invisible roots - btrfs: ref-verify: fix memory leak in add_block_entry - btrfs: stop incremening log_batch for the log root tree when syncing log - btrfs: remove no longer needed use of log_writers for the log root tree - btrfs: don't traverse into the seed devices in show_devname - btrfs: open device without device_list_mutex - btrfs: move the chunk_mutex in btrfs_read_chunk_tree - btrfs: relocation: review the call sites which can be interrupted by signal - btrfs: add missing check for nocow and compression inode flags - btrfs: avoid possible signal interruption of btrfs_drop_snapshot() on relocation tree - btrfs: sysfs: use NOFS for device creation - btrfs: don't WARN if we abort a transaction with EROFS - btrfs: fix race between page release and a fast fsync - btrfs: fix messages after changing compression level by remount - btrfs: only search for left_info if there is no right_info in try_merge_free_space - btrfs: inode: fix NULL pointer dereference if inode doesn't need compression - btrfs: fix memory leaks after failure to lookup checksums during inode logging - btrfs: make sure SB_I_VERSION doesn't get unset by remount - btrfs: fix return value mixup in
[Kernel-packages] [Bug 1876770] Re: speed for CX4 VF showing as unknown in ethtool output
This bug was fixed in the package linux-azure - 5.4.0-1026.26 --- linux-azure (5.4.0-1026.26) focal; urgency=medium * focal/linux-azure: 5.4.0-1026.26 -proposed tracker (LP: #1894641) * Mellanox Check For Write Combining Support (LP: #1874503) - IB/mlx5: Align usage of QP1 create flags with rest of mlx5 defines - IB/mlx5: Test write combining support * Enable Invariant TSC Support (LP: #1875467) - x86/hyperv: Allow guests to enable InvariantTSC - clocksource/drivers/hyper-v: Set TSC clocksource as default w/ InvariantTSC * Only notify Hyper-V for die events that are oops (LP: #1891222) - Drivers: hv: vmbus: Only notify Hyper-V for die events that are oops * speed for CX4 VF showing as unknown in ethtool output (LP: #1876770) - net/mlx5: Expose link speed directly - net/mlx5: Expose port speed when possible - net/mlx5: Tidy up and fix reverse christmas ordring [ Ubuntu: 5.4.0-48.52 ] * focal/linux: 5.4.0-48.52 -proposed tracker (LP: #1894654) * mm/slub kernel oops on focal kernel 5.4.0-45 (LP: #1895109) - SAUCE: Revert "mm/slub: fix a memory leak in sysfs_slab_add()" * Packaging resync (LP: #1786013) - update dkms package versions - update dkms package versions * Introduce the new NVIDIA 450-server and the 450 UDA series (LP: #1887674) - [packaging] add signed modules for nvidia 450 and 450-server * [UBUNTU 20.04] zPCI attach/detach issues with PF/VF linking support (LP: #1892849) - s390/pci: fix zpci_bus_link_virtfn() - s390/pci: re-introduce zpci_remove_device() - s390/pci: fix PF/VF linking on hot plug * [UBUNTU 20.04] kernel: s390/cpum_cf,perf: changeDFLT_CCERROR counter name (LP: #1891454) - s390/cpum_cf, perf: change DFLT_CCERROR counter name * [UBUNTU 20.04] zPCI: Enabling of a reserved PCI function regression introduced by multi-function support (LP: #1891437) - s390/pci: fix enabling a reserved PCI function * CVE-2020-12888 - vfio/type1: Support faulting PFNMAP vmas - vfio-pci: Fault mmaps to enable vma tracking - vfio-pci: Invalidate mmaps and block MMIO access on disabled memory * [Hyper-V] VSS and File Copy daemons intermittently fails to start (LP: #1891224) - [Packaging] Bind hv_vss_daemon startup to hv_vss device - [Packaging] bind hv_fcopy_daemon startup to hv_fcopy device * alsa/hdmi: support nvidia mst hdmi/dp audio (LP: #1867704) - ALSA: hda - Rename snd_hda_pin_sense to snd_hda_jack_pin_sense - ALSA: hda - Add DP-MST jack support - ALSA: hda - Add DP-MST support for non-acomp codecs - ALSA: hda - Add DP-MST support for NVIDIA codecs - ALSA: hda: hdmi - fix regression in connect list handling - ALSA: hda: hdmi - fix kernel oops caused by invalid PCM idx - ALSA: hda: hdmi - preserve non-MST PCM routing for Intel platforms - ALSA: hda: hdmi - Keep old slot assignment behavior for Intel platforms - ALSA: hda - Fix DP-MST support for NVIDIA codecs * Focal update: v5.4.60 upstream stable release (LP: #1892899) - smb3: warn on confusing error scenario with sec=krb5 - genirq/affinity: Make affinity setting if activated opt-in - genirq/PM: Always unlock IRQ descriptor in rearm_wake_irq() - PCI: hotplug: ACPI: Fix context refcounting in acpiphp_grab_context() - PCI: Add device even if driver attach failed - PCI: qcom: Define some PARF params needed for ipq8064 SoC - PCI: qcom: Add support for tx term offset for rev 2.1.0 - btrfs: allow use of global block reserve for balance item deletion - btrfs: free anon block device right after subvolume deletion - btrfs: don't allocate anonymous block device for user invisible roots - btrfs: ref-verify: fix memory leak in add_block_entry - btrfs: stop incremening log_batch for the log root tree when syncing log - btrfs: remove no longer needed use of log_writers for the log root tree - btrfs: don't traverse into the seed devices in show_devname - btrfs: open device without device_list_mutex - btrfs: move the chunk_mutex in btrfs_read_chunk_tree - btrfs: relocation: review the call sites which can be interrupted by signal - btrfs: add missing check for nocow and compression inode flags - btrfs: avoid possible signal interruption of btrfs_drop_snapshot() on relocation tree - btrfs: sysfs: use NOFS for device creation - btrfs: don't WARN if we abort a transaction with EROFS - btrfs: fix race between page release and a fast fsync - btrfs: fix messages after changing compression level by remount - btrfs: only search for left_info if there is no right_info in try_merge_free_space - btrfs: inode: fix NULL pointer dereference if inode doesn't need compression - btrfs: fix memory leaks after failure to lookup checksums during inode logging - btrfs: make sure SB_I_VERSION doesn't get unset by remount - btrfs: fix return value mixup in
[Kernel-packages] [Bug 1887674] Re: Introduce the new NVIDIA 450-server and the 450 UDA series
This bug was fixed in the package nvidia-graphics-drivers-450 - 450.66-0ubuntu0.18.04.1 --- nvidia-graphics-drivers-450 (450.66-0ubuntu0.18.04.1) bionic; urgency=medium * Initial release (LP: #1887674). -- Alberto Milone Tue, 14 Jul 2020 10:12:39 +0200 ** Changed in: nvidia-graphics-drivers-450-server (Ubuntu Bionic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-restricted-modules in Ubuntu. https://bugs.launchpad.net/bugs/1887674 Title: Introduce the new NVIDIA 450-server and the 450 UDA series Status in OEM Priority Project: New Status in linux package in Ubuntu: Triaged Status in linux-restricted-modules package in Ubuntu: Triaged Status in nvidia-graphics-drivers-450 package in Ubuntu: In Progress Status in nvidia-graphics-drivers-450-server package in Ubuntu: In Progress Status in linux source package in Bionic: Fix Released Status in linux-restricted-modules source package in Bionic: Fix Released Status in nvidia-graphics-drivers-450 source package in Bionic: Fix Released Status in nvidia-graphics-drivers-450-server source package in Bionic: Fix Released Status in linux source package in Focal: Fix Released Status in linux-restricted-modules source package in Focal: Fix Released Status in nvidia-graphics-drivers-450 source package in Focal: Fix Released Status in nvidia-graphics-drivers-450-server source package in Focal: Fix Released Bug description: [Impact] These releases provide both bug fixes and new features, and we would like to make sure all of our users have access to these improvements. See the changelog entry below for a full list of changes and bugs. [Test Case] The following development and SRU process was followed: https://wiki.ubuntu.com/NVidiaUpdates Certification test suite must pass on a range of hardware: https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu The QA team that executed the tests will be in charge of attaching the artifacts and console output of the appropriate run to the bug. nVidia maintainers team members will not mark ‘verification-done’ until this has happened. [Regression Potential] In order to mitigate the regression potential, the results of the aforementioned system level tests are attached to this bug. [Discussion] To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1887674/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1892822] Re: Xenial update: 4.4.233 upstream stable release
This bug was fixed in the package linux - 4.4.0-190.220 --- linux (4.4.0-190.220) xenial; urgency=medium * xenial/linux: 4.4.0-190.220 -proposed tracker (LP: #1893431) * Packaging resync (LP: #1786013) - [Packaging] update helper scripts * [Hyper-V] VSS and File Copy daemons intermittently fails to start (LP: #1891224) - [Packaging] Bind hv_vss_daemon startup to hv_vss device - [Packaging] bind hv_fcopy_daemon startup to hv_fcopy device * CVE-2019-20811 - net-sysfs: call dev_hold if kobject_init_and_add success * CVE-2020-0067 - f2fs: fix to avoid memory leakage in f2fs_listxattr * CVE-2019-9453 - f2fs: fix to avoid accessing xattr across the boundary * Xenial update: 4.4.233 upstream stable release (LP: #1892822) - media: rc: prevent memory leak in cx23888_ir_probe - ath9k_htc: release allocated buffer if timed out - ath9k: release allocated buffer if timed out - nfs: Move call to security_inode_listsecurity into nfs_listxattr - PCI/ASPM: Disable ASPM on ASMedia ASM1083/1085 PCIe-to-PCI bridge - drm/amdgpu: Prevent kernel-infoleak in amdgpu_info_ioctl() - drm: hold gem reference until object is no longer accessed - f2fs: check memory boundary by insane namelen - f2fs: check if file namelen exceeds max value - ARM: 8986/1: hw_breakpoint: Don't invoke overflow handler on uaccess watchpoints - fbdev: Detect integer underflow at "struct fbcon_ops"->clear_margins. - rds: Prevent kernel-infoleak in rds_notify_queue_get() - net/x25: Fix x25_neigh refcnt leak when x25 disconnect - net/x25: Fix null-ptr-deref in x25_disconnect - sh: Fix validation of system call number - net: lan78xx: add missing endpoint sanity check - net: lan78xx: fix transfer-buffer memory leak - mlxsw: core: Increase scope of RCU read-side critical section - mac80211: mesh: Free ie data when leaving mesh - nfc: s3fwrn5: add missing release on skb in s3fwrn5_recv_frame - net: ethernet: ravb: exit if re-initialization fails in tx timeout - Revert "i2c: cadence: Fix the hold bit setting" - xen-netfront: fix potential deadlock in xennet_remove() - x86/i8259: Use printk_deferred() to prevent deadlock - random32: update the net random state on interrupt and activity - ARM: percpu.h: fix build error - random: fix circular include dependency on arm64 after addition of percpu.h - random32: remove net_rand_state from the latent entropy gcc plugin - random32: move the pseudo-random 32-bit definitions to prandom.h - ext4: fix direct I/O read error - USB: serial: qcserial: add EM7305 QDL product ID - ALSA: seq: oss: Serialize ioctls - Bluetooth: Fix slab-out-of-bounds read in hci_extended_inquiry_result_evt() - Bluetooth: Prevent out-of-bounds read in hci_inquiry_result_evt() - Bluetooth: Prevent out-of-bounds read in hci_inquiry_result_with_rssi_evt() - vgacon: Fix for missing check in scrollback handling - mtd: properly check all write ioctls for permissions - net/9p: validate fds in p9_fd_open - drm/nouveau/fbcon: fix module unload when fbcon init has failed for some reason - cfg80211: check vendor command doit pointer before use - igb: reinit_locked() should be called with rtnl_lock - atm: fix atm_dev refcnt leaks in atmtcp_remove_persistent - tools lib traceevent: Fix memory leak in process_dynamic_array_len - binder: Prevent context manager from incrementing ref 0 - ipv4: Silence suspicious RCU usage warning - ipv6: fix memory leaks on IPV6_ADDRFORM path - Revert "vxlan: fix tos value before xmit" - net: lan78xx: replace bogus endpoint lookup - usb: hso: check for return value in hso_serial_common_create() - vxlan: Ensure FDB dump is performed under RCU - Smack: fix use-after-free in smk_write_relabel_self() - tracepoint: Mark __tracepoint_string's __used - udp: drop corrupt packets earlier to avoid data corruption - gpio: fix oops resulting from calling of_get_named_gpio(NULL, ...) - EDAC: Fix reference count leaks - m68k: mac: Don't send IOP message until channel is idle - m68k: mac: Fix IOP status/control register writes - ARM: at91: pm: add missing put_device() call in at91_pm_sram_init() - ARM: socfpga: PM: add missing put_device() call in socfpga_setup_ocram_self_refresh() - drm/tilcdc: fix leak & null ref in panel_connector_get_modes - Bluetooth: add a mutex lock to avoid UAF in do_enale_set - fs/btrfs: Add cond_resched() for try_release_extent_mapping() stalls - drm/radeon: Fix reference count leaks caused by pm_runtime_get_sync - video: fbdev: neofb: fix memory leak in neo_scan_monitor() - drm/nouveau: fix multiple instances of reference count leaks - drm/debugfs: fix plain echo to connector "force" attribute - mm/mmap.c: Add cond_resched() for exit_mmap() CPU stalls - brcmfmac: To fix Bss
[Kernel-packages] [Bug 1887674] Update Released
The verification of the Stable Release Update for nvidia-graphics- drivers-450 has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-restricted-modules in Ubuntu. https://bugs.launchpad.net/bugs/1887674 Title: Introduce the new NVIDIA 450-server and the 450 UDA series Status in OEM Priority Project: New Status in linux package in Ubuntu: Triaged Status in linux-restricted-modules package in Ubuntu: Triaged Status in nvidia-graphics-drivers-450 package in Ubuntu: In Progress Status in nvidia-graphics-drivers-450-server package in Ubuntu: In Progress Status in linux source package in Bionic: Fix Released Status in linux-restricted-modules source package in Bionic: Fix Released Status in nvidia-graphics-drivers-450 source package in Bionic: Fix Released Status in nvidia-graphics-drivers-450-server source package in Bionic: Fix Released Status in linux source package in Focal: Fix Released Status in linux-restricted-modules source package in Focal: Fix Released Status in nvidia-graphics-drivers-450 source package in Focal: Fix Released Status in nvidia-graphics-drivers-450-server source package in Focal: Fix Released Bug description: [Impact] These releases provide both bug fixes and new features, and we would like to make sure all of our users have access to these improvements. See the changelog entry below for a full list of changes and bugs. [Test Case] The following development and SRU process was followed: https://wiki.ubuntu.com/NVidiaUpdates Certification test suite must pass on a range of hardware: https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu The QA team that executed the tests will be in charge of attaching the artifacts and console output of the appropriate run to the bug. nVidia maintainers team members will not mark ‘verification-done’ until this has happened. [Regression Potential] In order to mitigate the regression potential, the results of the aforementioned system level tests are attached to this bug. [Discussion] To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1887674/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1896419] Re: Comet Lake CPUID family:model:stepping 0x6:a5:2 (6:165:2) is not included
@sil2100 I'll create MP to Debian. I'll notify you once my MP is ready. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to thermald in Ubuntu. https://bugs.launchpad.net/bugs/1896419 Title: Comet Lake CPUID family:model:stepping 0x6:a5:2 (6:165:2) is not included Status in OEM Priority Project: In Progress Status in thermald package in Ubuntu: In Progress Status in thermald source package in Focal: New Bug description: [Impact] * The CPUID is not included, which cause the thermald starts failed. Sep 15 17:07:00 ubuntu thermald[1089]: [WARN]Unsupported cpu model, use thermal-conf.xml file or run with --ignore-cpuid-check Sep 15 17:07:00 ubuntu thermald[1089]: [ERR]THD engine start failed Sep 15 17:07:00 ubuntu systemd[1]: thermald.service: Succeeded. * A upstream commit added missing CPUID https://github.com/intel/thermal_daemon/commit/7f2003ee911dd1c97ff74d2b84c62e10950bc9e0 [Test Case] On an affected system (Comet Lake): * $ systemctl is-active thermald active [Regression Potential] * Only new id added, no process or logic adjustment, so no regression risk. [Other Info] * The upstream bug: https://github.com/intel/thermal_daemon/issues/275 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1896419/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1877878] Re: package linux-firmware 1.183.5 failed to install/upgrade: unable to create '/lib/firmware/brcm/BCM-0bb4-0306.hcd.dpkg-new' (while processing './lib/firmware/brcm/BC
Thanks @mkaya387 that worked prefectly for me. I understand that chattr is the command in the GNU operating system (with Linux kernel) that allows a user to set certain attributes of a file. But can you elaborate on your solution of this issue? -- 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/1877878 Title: package linux-firmware 1.183.5 failed to install/upgrade: unable to create '/lib/firmware/brcm/BCM-0bb4-0306.hcd.dpkg-new' (while processing './lib/firmware/brcm/BCM-0bb4-0306.hcd'): Operation not permitted Status in linux-firmware package in Ubuntu: Confirmed Bug description: since my Bluetooth card was not working so I had to download the .hcd file for my specific card and make the directory lib/firmware/brcm mutable and copy the file then make it unmutable "sudo chattr +i /lib/firmware/brcm" during my update to ubuntu 20 I faced this issue so now ill try removing this file and updating the packages again ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-firmware 1.183.5 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia wl ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip Date: Sun May 10 23:40:47 2020 Dependencies: DuplicateSignature: package:linux-firmware:1.183.5 Unpacking linux-firmware (1.187) over (1.183.5) ... dpkg: error processing archive /tmp/apt-dpkg-install-Y0df9D/409-linux-firmware_1.187_all.deb (--unpack): unable to create '/lib/firmware/brcm/BCM-0bb4-0306.hcd.dpkg-new' (while processing './lib/firmware/brcm/BCM-0bb4-0306.hcd'): Operation not permitted ErrorMessage: unable to create '/lib/firmware/brcm/BCM-0bb4-0306.hcd.dpkg-new' (while processing './lib/firmware/brcm/BCM-0bb4-0306.hcd'): Operation not permitted InstallationDate: Installed on 2020-02-08 (92 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) PackageArchitecture: all Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18rc1, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2 SourcePackage: linux-firmware Title: package linux-firmware 1.183.5 failed to install/upgrade: unable to create '/lib/firmware/brcm/BCM-0bb4-0306.hcd.dpkg-new' (while processing './lib/firmware/brcm/BCM-0bb4-0306.hcd'): Operation not permitted UpgradeStatus: Upgraded to focal on 2020-05-10 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1877878/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1891437] Re: [UBUNTU 20.04] zPCI: Enabling of a reserved PCI function regression introduced by multi-function support
I just verified if the patch/commit also landed in groovy and it did. Hence updating the groovy entry to Fix Released and with that the entire case. ** Changed in: linux (Ubuntu Groovy) Status: Fix Committed => Fix Released ** Changed in: ubuntu-z-systems 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/1891437 Title: [UBUNTU 20.04] zPCI: Enabling of a reserved PCI function regression introduced by multi-function support Status in Ubuntu on IBM z Systems: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Focal: Fix Released Status in linux source package in Groovy: Fix Released Bug description: SRU Justification: == [Impact] * If a NVMe drive is assigned/hotplugged to a Linux on s390x LPAR, a bug in lib/list_debug.c is hit and the device is not accessible. * The reason is a missing /dev/ file -- lspci does not report it either. [Fix] * 3047766bc6ec9c6bc9ece85b45a41ff401e8d988 3047766bc6ec "s390/pci: fix enabling a reserved PCI function" [Test Case] * Assign a NMVe drive to your LPAR (using the HMC) * Unassign the NVMe drive from your LPAR * Reassign it to your LPAR again * Look at dmesg for 'kernel BUG at lib/list_debug.c' [Regression Potential] * There is some regression risk with having code changes in the zPCI sub-system. * zPCI is the PCI implementation on s390x, modifications here do not affect any other architecture. * It could be that PCI events do not work anymore and NVMe devices don't IPL (boot) on s390x anymore. * However, the code changes below to a single file: arch/s390/pci/pci_event.c * and IPL from NVMe is brand new in Ubuntu for s390x, * and zPCI devices are less wide-spread compared to ccw devices on s390x. * On top a test kernel was build and made available for further testing. [Other] * Since the fix/patch got upstream accepted with kernel v5.8-rc5, it's already in the groovy proposed kernel 5.8, hence this SRU is for focal only. __ When a NVMe drive is assigned/hotplugged to a Linux LPAR then a bug is hit in lib/list_debug.c. And the device is not accessible, there is no /dev/ file and lspci does not report it also. [ 1681.564462] list_add double add: new=eed0f808, prev=eed0f808, next=4070a300. [ 1681.564489] [ cut here ] [ 1681.564490] kernel BUG at lib/list_debug.c:31! [ 1681.564504] monitor event: 0040 ilc:2 [#1] SMP [ 1681.564507] Modules linked in: ip6t_REJECT nf_reject_ipv6 ip6t_rpfilter ipt_REJECT nf_reject_ipv4 xt_conntrack ebtable_nat ebtable_broute ip6table_nat ip6table_mangle ip6table_raw ip6table_security iptable_nat nf_nat iptable_mangle iptable_raw iptable_security nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 libcrc32c ip_set nfnetlink ebtable_filter ebtables ip6table_filter ip6_tables iptable_filter s390_trng ghash_s390 prng aes_s390 des_s390 libdes sha512_s390 vfio_ccw sha1_s390 vfio_mdev mdev chsc_sch vfio_iommu_type1 eadm_sch vfio ip_tables dm_service_time nvme crc32_vx_s390 sha256_s390 sha_common nvme_core qeth_l2 zfcp qeth scsi_transport_fc qdio ccwgroup dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua pkey zcrypt [ 1681.564534] CPU: 6 PID: 139 Comm: kmcheck Not tainted 5.8.0-rc1+ #2 [ 1681.564535] Hardware name: IBM 8561 T01 701 (LPAR) [ 1681.564536] Krnl PSW : 0704c0018000 3ffcadb8 (__list_add_valid+0x70/0xa8) [ 1681.564544]R:0 T:1 IO:1 EX:1 Key:0 M:1 W:0 P:0 AS:3 CC:0 PM:0 RI:0 EA:3 [ 1681.564545] Krnl GPRS: 0040 0027 0058 0007 [ 1681.564546]3ffcadb4 03e0051a7ce0 [ 1681.564547]4070a300 eed0f808 eed0f808 4070a300 [ 1681.564548]f56a2000 40c2c788 3ffcadb4 03e0051a7bc8 [ 1681.564583] Krnl Code: 3ffcada8: c02000302b09larl %r2,405d03ba 3ffcadae: c0e5ffdd30b1brasl %r14,3fb70f10 #3ffcadb4: af00mc 0,0 >3ffcadb8: b9040054lgr %r5,%r4 3ffcadbc: c02000302aadlarl %r2,405d0316 3ffcadc2: b9040041lgr %r4,%r1 3ffcadc6: c0e5ffdd30a5brasl %r14,3fb70f10 3ffcadcc: af00mc 0,0 [ 1681.564592] Call Trace: [ 1681.564594] [<3ffcadb8>] __list_add_valid+0x70/0xa8 [ 1681.564596] ([<3ffcadb4>] __list_add_valid+0x6c/0xa8) [
[Kernel-packages] [Bug 1891454] Re: [UBUNTU 20.04] kernel: s390/cpum_cf, perf: changeDFLT_CCERROR counter name
** Changed in: linux (Ubuntu Groovy)
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/1891454
Title:
[UBUNTU 20.04] kernel: s390/cpum_cf,perf: changeDFLT_CCERROR counter
name
Status in Ubuntu on IBM z Systems:
Fix Committed
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Bionic:
Fix Committed
Status in linux source package in Focal:
Fix Released
Status in linux source package in Groovy:
Fix Released
Bug description:
SRU Justification:
==
[Impact]
* Change the counter name DLFT_CCERROR to DLFT_CCFINISH on IBM z15 to
avoid confusion.
* This counter counts completed DEFLATE instructions with exit code 0,
1 or 2.
* And since exit code 0 means success and exit code 1 or 2 indicate
errors the name can be ambiguous.
[Fix]
* Rename s390 z15 counter named DFLT_CCERROR to DFLT_CCFINISH.
* Backport Focal: https://launchpadlibrarian.net/493272507/0001-s390
-cpum_cf-perf-change-DFLT_CCERROR-counter-name.patch
* Backport Bionic:
https://launchpadlibrarian.net/493439681/u18-0001-s390-cpum_cf-Add-
new-extended-counters-for-IBM-z15.patch
[Test Case]
* Enable hardware counters in the activation profile of a z15 LPAR.
* Just check the countername in sysfs with: ls
/sys/devices/cpum_cf/events/{DFLT_CCERROR,DFLT_CCFINISH}
[Regression Potential]
* The regression potential can be considered as low, since:
* Counters like these are usually not activated by default and need to
be explicitly enabled.
* No code functionality is changed with that patch, only a renaming is
done at 3 places in one code file
arch/s390/kernel/perf_cpum_cf_events.c as well as in /tools/perf/pmu-
events/arch/s390/cf_z15/extended.json.
* The fix got already upstream accepted in 5.8-rc7, hence it got
upstream reviewed,
* and the modifications are limited to s390x, are only relevant for
the z15 / LinuxONE III hw generation that are relatively new.
* Issue with the renaming I can think of are that people don't know
about the new name and may look for the old one and don't find it
anymore,
* and with that also if the old counter name is used in scripts or
applications, these may fails due to an unknown counter name.
[Other Info]
* The backports are based on commit
3d3af181d370069861a3be94608464e2ff3682e2 ("s390/cpum_cf,perf: change
DFLT_CCERROR counter name") that is upstream accepted since v5.8-rc7.
* Hence this SRU is not requested for groovy, since it's already in groovys
kernel 5.8 in proposed, but only requested for focal and bionic.
__
Description: kernel: s390/cpum_cf,perf: change DFLT_CCERROR counter name
Symptom: Counter name CCERROR is misleading.
Problem: Change the counter name DLFT_CCERROR to DLFT_CCFINISH on
IBM z15. This counter counts completed DEFLATE instructions
with exit code 0, 1 or 2. Since exit code 0 means success
and exit code 1 or 2 indicate errors, change the counter
name to avoid confusion. This counter is incremented each
time the DEFLATE instruction completed regardless if an
error was detected or not.
Solution: Rename s390 z15 counter named DFLT_CCERROR to DFLT_CCFINISH
Reproduction: Command # ls /sys/devices/cpum_cf/events/DFLT_CCERROR
currently succeeds. After this patch has been applied the
command does not work anymore. The file does not exist
anymore. Use command
# ls /sys/devices/cpum_cf/events/DFLT_CCFINISH
instead.
Upstream-ID: 5ce1a24dd98c00a57a8fa13660648abf7e08e3ef
Component: kernel 5.8
Will be integrated into 20.10 by kernel 5.8 integration.
Backport available for 20.04.
To be checked for 18.04 and 16.04, update will be provided
Here is the backported patch.
The upstream commit id is 3d3af181d370069861a3be94608464e2ff3682e2
("s390/cpum_cf,perf: change DFLT_CCERROR counter name")
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1891454/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1892849] Re: [UBUNTU 20.04] zPCI attach/detach issues with PF/VF linking support
I just verified if the patches/commits are in groovy master-next and they are.
Hence updating the groovy entry to Fix Released as well - and with that the
entire case.
** Changed in: linux (Ubuntu Groovy)
Status: In Progress => Fix Released
** Changed in: ubuntu-z-systems
Status: In Progress => Fix Released
** Changed in: linux (Ubuntu Groovy)
Assignee: Frank Heimes (fheimes) => (unassigned)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1892849
Title:
[UBUNTU 20.04] zPCI attach/detach issues with PF/VF linking support
Status in Ubuntu on IBM z Systems:
Fix Released
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Focal:
Fix Released
Status in linux source package in Groovy:
Fix Released
Bug description:
SRU Justification:
==
[Impact]
* There is a zPCI attach/detach issue in combination with PF/VF
linking support.
* On IBM Z with zPCI, VFs can be enabled/disabled individually with
/sys/bus/pci/slots//power.
* If this was done with a VF that is linked to a parent PF, the PF symlink
would become stale while the VF is disabled and
when turned back to the VF, it would not be properly linked back to the PF.
* The PF link is removed together with the whole VF directory.
* Hence for example qemu cannot be used since it relies on such links.
* Additionally there is a missing pci_dev_put() when searching for the
parent PF. This potentially results in a reference count of the parent
PFs that is becoming too high.
[Fix]
* 3cddb79afc60bcdb5fd9dd7a1c64a8d03bdd460f 3cddb79afc60 "s390/pci: fix
zpci_bus_link_virtfn()"
* 2f0230b2f2d5fd287a85583eefb5aed35b6fe510 2f0230b2f2d5 "390/pci: re-
introduce zpci_remove_device()"
* b97bf44f99155e57088e16974afb1f2d7b5287aa b97bf44f9915 "s390/pci: fix
PF/VF linking on hot plug"
[Test Case]
* Assign a zPCI device, that is capable of handling PFs/VFs (like a
RoCE adapter / Connect-X5) to a z15 or LinuxONE III LPAR (usually
using the HMC).
* Enable/disable a VF with /sys/bus/pci/slots//power
* Try to pass it through to qemu.
* The test needs to be done at IBM due to the special hardware
requirements.
[Regression Potential]
* A larger subset of the zPCI files in arch/s390/pci is touched
(pci_bus.{h,c}, pci_bus.c, pci.c, s390_pci_hpc.c and pci_event.c),
hence there is a certain risk for regressions.
* zPCI is the s390x-specific PCI implementation and (aot) less wide
spread compared to the traditional CCW hardware on s390x - no code is
touched outside of arch/s390/.
* The modifications are mainly in the IOV and hotplug area of zPCI.
* So SR-IOV, like RoCE adapters, may be harmed by bugs or issues with
hot-plugging PCI hardware on s390x.
* But on the other hand side that is the area where these patches fix
existing problems.
* In worst case PCI events can be impacted as well, that may harm
control and communication
* or changes in base pci_bus/pci code may even break zPCI entirely.
* Right now regular RoCE adapters (like Connect-X5) are currently not
handled as real SR-IOV VFs in zPCI, but are treated as normal PCI
devices.
* Hence these zPCI SR-IOV setup changes currently apply to PFs with
SR-IOV capability only, and those are currently not yet available to
customers outside IBM.
* The modifications were tested at IBM in house and a patched Ubuntu
kernel was created and shared for further testing and got successfully
verified (LP 1892849, comment #3).
[Other]
* This SRU depends on the SRU submitted for LP 1891437, which got
already ACKed. So LP 1891437 is a prerequisite and needs to be applied
before this one!
* The patches of the depending SRU and the ones here were successfully
tested based on a patched Ubuntu test kernel (LP 1892849, comment #3).
* Since the above three patches got upstream accepted with 5.9-rc2, this SRU
request is for Focal and Groovy.
__
Problem description:
When a NVMe drive is assigned/hotplugged to a Linux LPAR then
a bug is hit in lib/list_debug.c. And the device is not accessible, there is
no /dev/ file
and lspci does not report it also.
[ 1681.564462] list_add double add: new=eed0f808,
prev=eed0f808, next=4070a300.
[ 1681.564489] [ cut here ]
[ 1681.564490] kernel BUG at lib/list_debug.c:31!
[ 1681.564504] monitor event: 0040 ilc:2 [#1] SMP
[ 1681.564507] Modules linked in: ip6t_REJECT nf_reject_ipv6 ip6t_rpfilter
ipt_REJECT nf_reject_ipv4 xt_conntrack ebtable_nat ebtable_broute ip6table_nat
ip6table_mangle ip6table_raw ip6table_security iptable_nat nf_nat
iptable_mangle iptable_raw iptable_security nf_conntrack nf_defrag_ipv6
nf_defrag_ipv4 libcrc32c ip_set nfnetlink ebtable_filter ebtables
ip6table_filter ip6_tables iptable_filter
[Kernel-packages] [Bug 1867704] Re: alsa/hdmi: support nvidia mst hdmi/dp audio
** Changed in: hwe-next Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem in Ubuntu. https://bugs.launchpad.net/bugs/1867704 Title: alsa/hdmi: support nvidia mst hdmi/dp audio Status in HWE Next: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux-oem package in Ubuntu: Fix Released Status in linux source package in Bionic: Won't Fix Status in linux-oem source package in Bionic: Fix Released Status in linux source package in Focal: Fix Released Bug description: This is the justification for focal: This patchset will introduce a big change on hda_jack and hda_hdmi, So I sent the patcheset to oem-b 4 months ago. After 4 months of running oem-b kernel, there is no any regression reported on this patchset, now I am backporting the patchset to our focal kernel since our oem project is waiting for the patchset to be landed to ubuntu 5.4 kernel ASAP. This patchset are already merged to mainline kernel 5.5-rc and 5.6-rc, so there is no need to send the patchset to oem-5.6 or groovy kernel. [Impact] On some LENOVO I+N machines, when setting the graphic mode to discrete, The dp/hdmi audio on the Docking Gen2 can't work with this machine + LENOVO Docking Gen2, users can't find the hdmi audio entry in the gnome-sound-setting. [Fix] Nvidia developer submit the mst audio support to 5.5-rcN and 5.6-RC1, those patches could fix this issue. [Test Case] set the machien to discrete, plug the dock gen2 to it, then boot, after booting, plug hdmi or dp to dock gen2, the hdmi or dp audio works. test other machines without Nvidia graphic or without gen2, their hdmi/dp audio still work, and check other output/input devices like headphone, microphone, they all worked as well as before. [Regression Risk] one regression possibility is the audio jacks (including analogue and hdmi) can't work anymore, that means after users plug a headphone, headset, hdmi monitor or microphone to the audio jacks or hdmi connectors, the audio driver can't detect the plugging event. But regression's possibility is very low: - this patchset was already applied to oem-b kernel for 4 months, and oem projects didn't report any regression on the patchset - I tested the testing focal kernel with this patchset on many machines, includes a dell hda audio machine, a dell dmic machine, a Lenovo I+N hda audio machine, a lenovo I+N dmic machine, a lenovo I hda audio machine, a lenovo amd hda audio machine. The audio on them all worked as well as before. This is the justification for oem-b Drop the B, so far only need to merge this patchset to OEM-B first, After the patchset is widely verified with oem-b kernel, I send the patchset to B and F then. This patchset will add support of mst audio for nvidia hdmi/dp, this patchset changes lots of common code on hda_jack and hdmi codec, so it is not easy to say it is 100% safe for other machines, but our oem project needs this patchset to be backported to ubuntu kernel, because the tight sechdule of oem project, we backport this patchset to B and OEM-B first, if the hdmi audio works well for a period of time after this patchset is merged, I will backport this patchset to focal, maybe eoan as well. [Impact] On some LENOVO I+N machines, when setting the graphic mode to discrete, The dp/hdmi audio on the Docking Gen2 can't work with this machine + LENOVO Docking Gen2 [Fix] Nvidia developer submit the mst audio support to 5.5-rcN and 5.6-RC1, those patches could fix this issue. [Test Case] set the machien to discrete, plug the dock gen2 to it, then boot, after booting, plug hdmi or dp to dock gen2, the hdmi or dp audio works. test other machines without Nvidia graphic or without gen2, their hdmi/dp audio still work. [Regression Risk] Low, those patches come from mainline kernel, I have tested those patches on the machiens with or without nvidia hdmi, and on the machines with or without docks, all worked well as before. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1867704/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1891585] Re: alsa/sof: support 1 and 3 dmics
** Changed in: linux-oem-5.6 (Ubuntu) Status: Triaged => Fix Released ** Changed in: hwe-next Status: Triaged => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1891585 Title: alsa/sof: support 1 and 3 dmics Status in HWE Next: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux-firmware package in Ubuntu: Fix Released Status in linux-oem-5.6 package in Ubuntu: Fix Released Status in linux source package in Focal: Fix Released Status in linux-firmware source package in Focal: Fix Released Status in linux-oem-5.6 source package in Focal: Fix Released Status in linux source package in Groovy: Fix Released Status in linux-firmware source package in Groovy: Fix Released Bug description: This is for linux-firmware: [Impact] On a Dell tigerlake laptop, the sof driver fails to detect the dmic, it alwasys report 0 dmics on the machine. So users doesn't have internal mic to use. [Fix] Intel provides 2 new topology files to us, they could support 1 dmic and 3 dmics. [Test Case] Boot the kernel with this patch, and put sof-hda-generic-1ch.tplg in the linux-firmware, the sof driver could detect the dmic and users have a workable internal mic after booting up. [Regression Risk] This is adding 2 new topology files, not changing anything on current sof-firmware, so the regression posibility is very low. This is for linux kernel: [Impact] On a Dell tigerlake laptop, the sof driver fails to detect the dmic, it alwasys report 0 dmics on the machine. So users doesn't have internal mic to use. [Fix] Intel write a patch to fix this issue, if NHLT table returns 1 or 3 dmics, the sof driver will not fail like before, it can support 1 or 3 dmics after applying this patch. [Test Case] Boot the kernel with this patch, and put sof-hda-generic-1ch.tplg in the linux-firmware, the sof driver could detect the dmic and users have a workable internal mic after booting up. [Regression Risk] This patch adds new support for 1 and 3 dmics, it doesn't change anything on existing functions, so the regression posibility is very low. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1891585/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1876770] Re: speed for CX4 VF showing as unknown in ethtool output
This bug was fixed in the package linux-azure - 4.15.0-1096.106~16.04.1
---
linux-azure (4.15.0-1096.106~16.04.1) xenial; urgency=medium
* xenial/linux-azure: 4.15.0-1096.106~16.04.1 -proposed tracker (LP:
#1894681)
[ Ubuntu: 4.15.0-1096.106 ]
* bionic/linux-azure-4.15: 4.15.0-1096.106 -proposed tracker (LP: #1894683)
* Mellanox Check For Write Combining Support (LP: #1874503)
- RDMA/rxe: Close a race after ib_register_device
- IB/mlx5: Align usage of QP1 create flags with rest of mlx5 defines
- IB/mlx5: Test write combining support
* Enable Invariant TSC Support (LP: #1875467)
- x86/hyperv: Allow guests to enable InvariantTSC
- x86/hyperv: Set TSC clocksource as default w/ InvariantTSC
* Only notify Hyper-V for die events that are oops (LP: #1891222)
- Drivers: hv: vmbus: Only notify Hyper-V for die events that are oops
* speed for CX4 VF showing as unknown in ethtool output (LP: #1876770)
- net/mlx5: Expose link speed directly
- net/mlx5: Expose port speed when possible
- net/mlx5: Tidy up and fix reverse christmas ordring
* bionic/linux: 4.15.0-118.119 -proposed tracker (LP: #1894697)
* Packaging resync (LP: #1786013)
- update dkms package versions
* Introduce the new NVIDIA 450-server and the 450 UDA series (LP: #1887674)
- [packaging] add signed modules for nvidia 450 and 450-server
* cgroup refcount is bogus when cgroup_sk_alloc is disabled (LP: #1886860)
- cgroup: add missing skcd->no_refcnt check in cgroup_sk_clone()
* CVE-2020-12888
- vfio/type1: Support faulting PFNMAP vmas
- vfio-pci: Fault mmaps to enable vma tracking
- vfio-pci: Invalidate mmaps and block MMIO access on disabled memory
* [Hyper-V] VSS and File Copy daemons intermittently fails to start
(LP: #1891224)
- [Packaging] Bind hv_vss_daemon startup to hv_vss device
- [Packaging] bind hv_fcopy_daemon startup to hv_fcopy device
* KVM: Fix zero_page reference counter overflow when using KSM on KVM compute
host (LP: #1837810)
- KVM: fix overflow of zero page refcount with ksm running
* Fix false-negative return value for rtnetlink.sh in kselftests/net
(LP: #1890136)
- selftests: rtnetlink: correct the final return value for the test
- selftests: rtnetlink: make kci_test_encap() return sub-test result
* Bionic update: upstream stable patchset 2020-08-18 (LP: #1892091)
- USB: serial: qcserial: add EM7305 QDL product ID
- USB: iowarrior: fix up report size handling for some devices
- usb: xhci: define IDs for various ASMedia host controllers
- usb: xhci: Fix ASMedia ASM1142 DMA addressing
- Revert "ALSA: hda: call runtime_allow() for all hda controllers"
- ALSA: seq: oss: Serialize ioctls
- staging: android: ashmem: Fix lockdep warning for write operation
- Bluetooth: Fix slab-out-of-bounds read in
hci_extended_inquiry_result_evt()
- Bluetooth: Prevent out-of-bounds read in hci_inquiry_result_evt()
- Bluetooth: Prevent out-of-bounds read in
hci_inquiry_result_with_rssi_evt()
- omapfb: dss: Fix max fclk divider for omap36xx
- binder: Prevent context manager from incrementing ref 0
- vgacon: Fix for missing check in scrollback handling
- mtd: properly check all write ioctls for permissions
- leds: wm831x-status: fix use-after-free on unbind
- leds: da903x: fix use-after-free on unbind
- leds: lm3533: fix use-after-free on unbind
- leds: 88pm860x: fix use-after-free on unbind
- net/9p: validate fds in p9_fd_open
- drm/nouveau/fbcon: fix module unload when fbcon init has failed for some
reason
- drm/nouveau/fbcon: zero-initialise the mode_cmd2 structure
- i2c: slave: improve sanity check when registering
- i2c: slave: add sanity check when unregistering
- usb: hso: check for return value in hso_serial_common_create()
- firmware: Fix a reference count leak.
- cfg80211: check vendor command doit pointer before use
- igb: reinit_locked() should be called with rtnl_lock
- atm: fix atm_dev refcnt leaks in atmtcp_remove_persistent
- tools lib traceevent: Fix memory leak in process_dynamic_array_len
- Drivers: hv: vmbus: Ignore CHANNELMSG_TL_CONNECT_RESULT(23)
- xattr: break delegations in {set,remove}xattr
- ipv4: Silence suspicious RCU usage warning
- ipv6: fix memory leaks on IPV6_ADDRFORM path
- net: ethernet: mtk_eth_soc: fix MTU warnings
- vxlan: Ensure FDB dump is performed under RCU
- net: lan78xx: replace bogus endpoint lookup
- hv_netvsc: do not use VF device if link is down
- net: gre: recompute gre csum for sctp over gre tunnels
- openvswitch: Prevent kernel-infoleak in ovs_ct_put_key()
- Revert "vxlan: fix tos value before xmit"
- selftests/net: relax cpu affinity requirement in msg_zerocopy test
- rxrpc: Fix race between recvmsg and sendmsg on immediate call failure
- i40e: add num_vectors checker in iwarp handler
-
[Kernel-packages] [Bug 1875467] Re: Enable Invariant TSC Support
This bug was fixed in the package linux-azure - 4.15.0-1096.106~16.04.1
---
linux-azure (4.15.0-1096.106~16.04.1) xenial; urgency=medium
* xenial/linux-azure: 4.15.0-1096.106~16.04.1 -proposed tracker (LP:
#1894681)
[ Ubuntu: 4.15.0-1096.106 ]
* bionic/linux-azure-4.15: 4.15.0-1096.106 -proposed tracker (LP: #1894683)
* Mellanox Check For Write Combining Support (LP: #1874503)
- RDMA/rxe: Close a race after ib_register_device
- IB/mlx5: Align usage of QP1 create flags with rest of mlx5 defines
- IB/mlx5: Test write combining support
* Enable Invariant TSC Support (LP: #1875467)
- x86/hyperv: Allow guests to enable InvariantTSC
- x86/hyperv: Set TSC clocksource as default w/ InvariantTSC
* Only notify Hyper-V for die events that are oops (LP: #1891222)
- Drivers: hv: vmbus: Only notify Hyper-V for die events that are oops
* speed for CX4 VF showing as unknown in ethtool output (LP: #1876770)
- net/mlx5: Expose link speed directly
- net/mlx5: Expose port speed when possible
- net/mlx5: Tidy up and fix reverse christmas ordring
* bionic/linux: 4.15.0-118.119 -proposed tracker (LP: #1894697)
* Packaging resync (LP: #1786013)
- update dkms package versions
* Introduce the new NVIDIA 450-server and the 450 UDA series (LP: #1887674)
- [packaging] add signed modules for nvidia 450 and 450-server
* cgroup refcount is bogus when cgroup_sk_alloc is disabled (LP: #1886860)
- cgroup: add missing skcd->no_refcnt check in cgroup_sk_clone()
* CVE-2020-12888
- vfio/type1: Support faulting PFNMAP vmas
- vfio-pci: Fault mmaps to enable vma tracking
- vfio-pci: Invalidate mmaps and block MMIO access on disabled memory
* [Hyper-V] VSS and File Copy daemons intermittently fails to start
(LP: #1891224)
- [Packaging] Bind hv_vss_daemon startup to hv_vss device
- [Packaging] bind hv_fcopy_daemon startup to hv_fcopy device
* KVM: Fix zero_page reference counter overflow when using KSM on KVM compute
host (LP: #1837810)
- KVM: fix overflow of zero page refcount with ksm running
* Fix false-negative return value for rtnetlink.sh in kselftests/net
(LP: #1890136)
- selftests: rtnetlink: correct the final return value for the test
- selftests: rtnetlink: make kci_test_encap() return sub-test result
* Bionic update: upstream stable patchset 2020-08-18 (LP: #1892091)
- USB: serial: qcserial: add EM7305 QDL product ID
- USB: iowarrior: fix up report size handling for some devices
- usb: xhci: define IDs for various ASMedia host controllers
- usb: xhci: Fix ASMedia ASM1142 DMA addressing
- Revert "ALSA: hda: call runtime_allow() for all hda controllers"
- ALSA: seq: oss: Serialize ioctls
- staging: android: ashmem: Fix lockdep warning for write operation
- Bluetooth: Fix slab-out-of-bounds read in
hci_extended_inquiry_result_evt()
- Bluetooth: Prevent out-of-bounds read in hci_inquiry_result_evt()
- Bluetooth: Prevent out-of-bounds read in
hci_inquiry_result_with_rssi_evt()
- omapfb: dss: Fix max fclk divider for omap36xx
- binder: Prevent context manager from incrementing ref 0
- vgacon: Fix for missing check in scrollback handling
- mtd: properly check all write ioctls for permissions
- leds: wm831x-status: fix use-after-free on unbind
- leds: da903x: fix use-after-free on unbind
- leds: lm3533: fix use-after-free on unbind
- leds: 88pm860x: fix use-after-free on unbind
- net/9p: validate fds in p9_fd_open
- drm/nouveau/fbcon: fix module unload when fbcon init has failed for some
reason
- drm/nouveau/fbcon: zero-initialise the mode_cmd2 structure
- i2c: slave: improve sanity check when registering
- i2c: slave: add sanity check when unregistering
- usb: hso: check for return value in hso_serial_common_create()
- firmware: Fix a reference count leak.
- cfg80211: check vendor command doit pointer before use
- igb: reinit_locked() should be called with rtnl_lock
- atm: fix atm_dev refcnt leaks in atmtcp_remove_persistent
- tools lib traceevent: Fix memory leak in process_dynamic_array_len
- Drivers: hv: vmbus: Ignore CHANNELMSG_TL_CONNECT_RESULT(23)
- xattr: break delegations in {set,remove}xattr
- ipv4: Silence suspicious RCU usage warning
- ipv6: fix memory leaks on IPV6_ADDRFORM path
- net: ethernet: mtk_eth_soc: fix MTU warnings
- vxlan: Ensure FDB dump is performed under RCU
- net: lan78xx: replace bogus endpoint lookup
- hv_netvsc: do not use VF device if link is down
- net: gre: recompute gre csum for sctp over gre tunnels
- openvswitch: Prevent kernel-infoleak in ovs_ct_put_key()
- Revert "vxlan: fix tos value before xmit"
- selftests/net: relax cpu affinity requirement in msg_zerocopy test
- rxrpc: Fix race between recvmsg and sendmsg on immediate call failure
- i40e: add num_vectors checker in iwarp handler
-
[Kernel-packages] [Bug 1861554] Re: Radeon mobility HD3450 (RV620) heavy screen flickering after trying to upgrade kernel 4.15.0-54
I see there are problems with this patch. Any chance to solve this bug? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1861554 Title: Radeon mobility HD3450 (RV620) heavy screen flickering after trying to upgrade kernel 4.15.0-54 Status in linux package in Ubuntu: Confirmed Bug description: laptop Asus x50sl with graphic card AMD rv620 / Mobility Radeon HD3450. Distro: Linux Mint 19.2 Tina base: Ubuntu 18.04 bionic. This happen trying any distro. I tried Ubuntu, Manjaro, Debian, Deepin, MX and so on. I'm stuck with Kernel 4.15.0-54 and 5.0.0-20 (and the contemporary 5.3 kernel). I cannot upgrade to newer kernels. Seems that the fixes for bug #1791312 broke my kind of card. here is a video: https://youtu.be/9Rez7s0V6iA here is another user with same problem: https://forums.linuxmint.com/viewtopic.php?p=1702005#p1702005 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861554/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1891222] Re: Only notify Hyper-V for die events that are oops
This bug was fixed in the package linux-azure - 4.15.0-1096.106~16.04.1
---
linux-azure (4.15.0-1096.106~16.04.1) xenial; urgency=medium
* xenial/linux-azure: 4.15.0-1096.106~16.04.1 -proposed tracker (LP:
#1894681)
[ Ubuntu: 4.15.0-1096.106 ]
* bionic/linux-azure-4.15: 4.15.0-1096.106 -proposed tracker (LP: #1894683)
* Mellanox Check For Write Combining Support (LP: #1874503)
- RDMA/rxe: Close a race after ib_register_device
- IB/mlx5: Align usage of QP1 create flags with rest of mlx5 defines
- IB/mlx5: Test write combining support
* Enable Invariant TSC Support (LP: #1875467)
- x86/hyperv: Allow guests to enable InvariantTSC
- x86/hyperv: Set TSC clocksource as default w/ InvariantTSC
* Only notify Hyper-V for die events that are oops (LP: #1891222)
- Drivers: hv: vmbus: Only notify Hyper-V for die events that are oops
* speed for CX4 VF showing as unknown in ethtool output (LP: #1876770)
- net/mlx5: Expose link speed directly
- net/mlx5: Expose port speed when possible
- net/mlx5: Tidy up and fix reverse christmas ordring
* bionic/linux: 4.15.0-118.119 -proposed tracker (LP: #1894697)
* Packaging resync (LP: #1786013)
- update dkms package versions
* Introduce the new NVIDIA 450-server and the 450 UDA series (LP: #1887674)
- [packaging] add signed modules for nvidia 450 and 450-server
* cgroup refcount is bogus when cgroup_sk_alloc is disabled (LP: #1886860)
- cgroup: add missing skcd->no_refcnt check in cgroup_sk_clone()
* CVE-2020-12888
- vfio/type1: Support faulting PFNMAP vmas
- vfio-pci: Fault mmaps to enable vma tracking
- vfio-pci: Invalidate mmaps and block MMIO access on disabled memory
* [Hyper-V] VSS and File Copy daemons intermittently fails to start
(LP: #1891224)
- [Packaging] Bind hv_vss_daemon startup to hv_vss device
- [Packaging] bind hv_fcopy_daemon startup to hv_fcopy device
* KVM: Fix zero_page reference counter overflow when using KSM on KVM compute
host (LP: #1837810)
- KVM: fix overflow of zero page refcount with ksm running
* Fix false-negative return value for rtnetlink.sh in kselftests/net
(LP: #1890136)
- selftests: rtnetlink: correct the final return value for the test
- selftests: rtnetlink: make kci_test_encap() return sub-test result
* Bionic update: upstream stable patchset 2020-08-18 (LP: #1892091)
- USB: serial: qcserial: add EM7305 QDL product ID
- USB: iowarrior: fix up report size handling for some devices
- usb: xhci: define IDs for various ASMedia host controllers
- usb: xhci: Fix ASMedia ASM1142 DMA addressing
- Revert "ALSA: hda: call runtime_allow() for all hda controllers"
- ALSA: seq: oss: Serialize ioctls
- staging: android: ashmem: Fix lockdep warning for write operation
- Bluetooth: Fix slab-out-of-bounds read in
hci_extended_inquiry_result_evt()
- Bluetooth: Prevent out-of-bounds read in hci_inquiry_result_evt()
- Bluetooth: Prevent out-of-bounds read in
hci_inquiry_result_with_rssi_evt()
- omapfb: dss: Fix max fclk divider for omap36xx
- binder: Prevent context manager from incrementing ref 0
- vgacon: Fix for missing check in scrollback handling
- mtd: properly check all write ioctls for permissions
- leds: wm831x-status: fix use-after-free on unbind
- leds: da903x: fix use-after-free on unbind
- leds: lm3533: fix use-after-free on unbind
- leds: 88pm860x: fix use-after-free on unbind
- net/9p: validate fds in p9_fd_open
- drm/nouveau/fbcon: fix module unload when fbcon init has failed for some
reason
- drm/nouveau/fbcon: zero-initialise the mode_cmd2 structure
- i2c: slave: improve sanity check when registering
- i2c: slave: add sanity check when unregistering
- usb: hso: check for return value in hso_serial_common_create()
- firmware: Fix a reference count leak.
- cfg80211: check vendor command doit pointer before use
- igb: reinit_locked() should be called with rtnl_lock
- atm: fix atm_dev refcnt leaks in atmtcp_remove_persistent
- tools lib traceevent: Fix memory leak in process_dynamic_array_len
- Drivers: hv: vmbus: Ignore CHANNELMSG_TL_CONNECT_RESULT(23)
- xattr: break delegations in {set,remove}xattr
- ipv4: Silence suspicious RCU usage warning
- ipv6: fix memory leaks on IPV6_ADDRFORM path
- net: ethernet: mtk_eth_soc: fix MTU warnings
- vxlan: Ensure FDB dump is performed under RCU
- net: lan78xx: replace bogus endpoint lookup
- hv_netvsc: do not use VF device if link is down
- net: gre: recompute gre csum for sctp over gre tunnels
- openvswitch: Prevent kernel-infoleak in ovs_ct_put_key()
- Revert "vxlan: fix tos value before xmit"
- selftests/net: relax cpu affinity requirement in msg_zerocopy test
- rxrpc: Fix race between recvmsg and sendmsg on immediate call failure
- i40e: add num_vectors checker in iwarp handler
-
[Kernel-packages] [Bug 1890136] Re: Fix false-negative return value for rtnetlink.sh in kselftests/net
This bug was fixed in the package linux - 5.4.0-48.52 --- linux (5.4.0-48.52) focal; urgency=medium * focal/linux: 5.4.0-48.52 -proposed tracker (LP: #1894654) * mm/slub kernel oops on focal kernel 5.4.0-45 (LP: #1895109) - SAUCE: Revert "mm/slub: fix a memory leak in sysfs_slab_add()" * Packaging resync (LP: #1786013) - update dkms package versions - update dkms package versions * Introduce the new NVIDIA 450-server and the 450 UDA series (LP: #1887674) - [packaging] add signed modules for nvidia 450 and 450-server * [UBUNTU 20.04] zPCI attach/detach issues with PF/VF linking support (LP: #1892849) - s390/pci: fix zpci_bus_link_virtfn() - s390/pci: re-introduce zpci_remove_device() - s390/pci: fix PF/VF linking on hot plug * [UBUNTU 20.04] kernel: s390/cpum_cf,perf: changeDFLT_CCERROR counter name (LP: #1891454) - s390/cpum_cf, perf: change DFLT_CCERROR counter name * [UBUNTU 20.04] zPCI: Enabling of a reserved PCI function regression introduced by multi-function support (LP: #1891437) - s390/pci: fix enabling a reserved PCI function * CVE-2020-12888 - vfio/type1: Support faulting PFNMAP vmas - vfio-pci: Fault mmaps to enable vma tracking - vfio-pci: Invalidate mmaps and block MMIO access on disabled memory * [Hyper-V] VSS and File Copy daemons intermittently fails to start (LP: #1891224) - [Packaging] Bind hv_vss_daemon startup to hv_vss device - [Packaging] bind hv_fcopy_daemon startup to hv_fcopy device * alsa/hdmi: support nvidia mst hdmi/dp audio (LP: #1867704) - ALSA: hda - Rename snd_hda_pin_sense to snd_hda_jack_pin_sense - ALSA: hda - Add DP-MST jack support - ALSA: hda - Add DP-MST support for non-acomp codecs - ALSA: hda - Add DP-MST support for NVIDIA codecs - ALSA: hda: hdmi - fix regression in connect list handling - ALSA: hda: hdmi - fix kernel oops caused by invalid PCM idx - ALSA: hda: hdmi - preserve non-MST PCM routing for Intel platforms - ALSA: hda: hdmi - Keep old slot assignment behavior for Intel platforms - ALSA: hda - Fix DP-MST support for NVIDIA codecs * Focal update: v5.4.60 upstream stable release (LP: #1892899) - smb3: warn on confusing error scenario with sec=krb5 - genirq/affinity: Make affinity setting if activated opt-in - genirq/PM: Always unlock IRQ descriptor in rearm_wake_irq() - PCI: hotplug: ACPI: Fix context refcounting in acpiphp_grab_context() - PCI: Add device even if driver attach failed - PCI: qcom: Define some PARF params needed for ipq8064 SoC - PCI: qcom: Add support for tx term offset for rev 2.1.0 - btrfs: allow use of global block reserve for balance item deletion - btrfs: free anon block device right after subvolume deletion - btrfs: don't allocate anonymous block device for user invisible roots - btrfs: ref-verify: fix memory leak in add_block_entry - btrfs: stop incremening log_batch for the log root tree when syncing log - btrfs: remove no longer needed use of log_writers for the log root tree - btrfs: don't traverse into the seed devices in show_devname - btrfs: open device without device_list_mutex - btrfs: move the chunk_mutex in btrfs_read_chunk_tree - btrfs: relocation: review the call sites which can be interrupted by signal - btrfs: add missing check for nocow and compression inode flags - btrfs: avoid possible signal interruption of btrfs_drop_snapshot() on relocation tree - btrfs: sysfs: use NOFS for device creation - btrfs: don't WARN if we abort a transaction with EROFS - btrfs: fix race between page release and a fast fsync - btrfs: fix messages after changing compression level by remount - btrfs: only search for left_info if there is no right_info in try_merge_free_space - btrfs: inode: fix NULL pointer dereference if inode doesn't need compression - btrfs: fix memory leaks after failure to lookup checksums during inode logging - btrfs: make sure SB_I_VERSION doesn't get unset by remount - btrfs: fix return value mixup in btrfs_get_extent - arm64: perf: Correct the event index in sysfs - dt-bindings: iio: io-channel-mux: Fix compatible string in example code - iio: dac: ad5592r: fix unbalanced mutex unlocks in ad5592r_read_raw() - xtensa: add missing exclusive access state management - xtensa: fix xtensa_pmu_setup prototype - cifs: Fix leak when handling lease break for cached root fid - powerpc/ptdump: Fix build failure in hashpagetable.c - powerpc: Allow 4224 bytes of stack expansion for the signal frame - powerpc: Fix circular dependency between percpu.h and mmu.h - pinctrl: ingenic: Enhance support for IRQ_TYPE_EDGE_BOTH - media: vsp1: dl: Fix NULL pointer dereference on unbind - net: ethernet: stmmac: Disable hardware multicast filter - net: stmmac: dwmac1000: provide multicast filter fallback
[Kernel-packages] [Bug 1874503] Re: Mellanox Check For Write Combining Support
This bug was fixed in the package linux-azure - 4.15.0-1096.106~16.04.1
---
linux-azure (4.15.0-1096.106~16.04.1) xenial; urgency=medium
* xenial/linux-azure: 4.15.0-1096.106~16.04.1 -proposed tracker (LP:
#1894681)
[ Ubuntu: 4.15.0-1096.106 ]
* bionic/linux-azure-4.15: 4.15.0-1096.106 -proposed tracker (LP: #1894683)
* Mellanox Check For Write Combining Support (LP: #1874503)
- RDMA/rxe: Close a race after ib_register_device
- IB/mlx5: Align usage of QP1 create flags with rest of mlx5 defines
- IB/mlx5: Test write combining support
* Enable Invariant TSC Support (LP: #1875467)
- x86/hyperv: Allow guests to enable InvariantTSC
- x86/hyperv: Set TSC clocksource as default w/ InvariantTSC
* Only notify Hyper-V for die events that are oops (LP: #1891222)
- Drivers: hv: vmbus: Only notify Hyper-V for die events that are oops
* speed for CX4 VF showing as unknown in ethtool output (LP: #1876770)
- net/mlx5: Expose link speed directly
- net/mlx5: Expose port speed when possible
- net/mlx5: Tidy up and fix reverse christmas ordring
* bionic/linux: 4.15.0-118.119 -proposed tracker (LP: #1894697)
* Packaging resync (LP: #1786013)
- update dkms package versions
* Introduce the new NVIDIA 450-server and the 450 UDA series (LP: #1887674)
- [packaging] add signed modules for nvidia 450 and 450-server
* cgroup refcount is bogus when cgroup_sk_alloc is disabled (LP: #1886860)
- cgroup: add missing skcd->no_refcnt check in cgroup_sk_clone()
* CVE-2020-12888
- vfio/type1: Support faulting PFNMAP vmas
- vfio-pci: Fault mmaps to enable vma tracking
- vfio-pci: Invalidate mmaps and block MMIO access on disabled memory
* [Hyper-V] VSS and File Copy daemons intermittently fails to start
(LP: #1891224)
- [Packaging] Bind hv_vss_daemon startup to hv_vss device
- [Packaging] bind hv_fcopy_daemon startup to hv_fcopy device
* KVM: Fix zero_page reference counter overflow when using KSM on KVM compute
host (LP: #1837810)
- KVM: fix overflow of zero page refcount with ksm running
* Fix false-negative return value for rtnetlink.sh in kselftests/net
(LP: #1890136)
- selftests: rtnetlink: correct the final return value for the test
- selftests: rtnetlink: make kci_test_encap() return sub-test result
* Bionic update: upstream stable patchset 2020-08-18 (LP: #1892091)
- USB: serial: qcserial: add EM7305 QDL product ID
- USB: iowarrior: fix up report size handling for some devices
- usb: xhci: define IDs for various ASMedia host controllers
- usb: xhci: Fix ASMedia ASM1142 DMA addressing
- Revert "ALSA: hda: call runtime_allow() for all hda controllers"
- ALSA: seq: oss: Serialize ioctls
- staging: android: ashmem: Fix lockdep warning for write operation
- Bluetooth: Fix slab-out-of-bounds read in
hci_extended_inquiry_result_evt()
- Bluetooth: Prevent out-of-bounds read in hci_inquiry_result_evt()
- Bluetooth: Prevent out-of-bounds read in
hci_inquiry_result_with_rssi_evt()
- omapfb: dss: Fix max fclk divider for omap36xx
- binder: Prevent context manager from incrementing ref 0
- vgacon: Fix for missing check in scrollback handling
- mtd: properly check all write ioctls for permissions
- leds: wm831x-status: fix use-after-free on unbind
- leds: da903x: fix use-after-free on unbind
- leds: lm3533: fix use-after-free on unbind
- leds: 88pm860x: fix use-after-free on unbind
- net/9p: validate fds in p9_fd_open
- drm/nouveau/fbcon: fix module unload when fbcon init has failed for some
reason
- drm/nouveau/fbcon: zero-initialise the mode_cmd2 structure
- i2c: slave: improve sanity check when registering
- i2c: slave: add sanity check when unregistering
- usb: hso: check for return value in hso_serial_common_create()
- firmware: Fix a reference count leak.
- cfg80211: check vendor command doit pointer before use
- igb: reinit_locked() should be called with rtnl_lock
- atm: fix atm_dev refcnt leaks in atmtcp_remove_persistent
- tools lib traceevent: Fix memory leak in process_dynamic_array_len
- Drivers: hv: vmbus: Ignore CHANNELMSG_TL_CONNECT_RESULT(23)
- xattr: break delegations in {set,remove}xattr
- ipv4: Silence suspicious RCU usage warning
- ipv6: fix memory leaks on IPV6_ADDRFORM path
- net: ethernet: mtk_eth_soc: fix MTU warnings
- vxlan: Ensure FDB dump is performed under RCU
- net: lan78xx: replace bogus endpoint lookup
- hv_netvsc: do not use VF device if link is down
- net: gre: recompute gre csum for sctp over gre tunnels
- openvswitch: Prevent kernel-infoleak in ovs_ct_put_key()
- Revert "vxlan: fix tos value before xmit"
- selftests/net: relax cpu affinity requirement in msg_zerocopy test
- rxrpc: Fix race between recvmsg and sendmsg on immediate call failure
- i40e: add num_vectors checker in iwarp handler
-
[Kernel-packages] [Bug 1896419] Re: Comet Lake CPUID family:model:stepping 0x6:a5:2 (6:165:2) is not included
The debdiff looks sane, the package seems to be good for SRU upload under the HWE criteria. One question though: this change seems to be missing from groovy. We could, of course, just upload the same change on top of groovy's 2.3-2, but I would prefer not to introduce an Ubuntu delta if not needed. Currently in groovy the package is in sync with Debian - did anyone try getting this change accepted in Debian then and only then later synced to Ubuntu? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to thermald in Ubuntu. https://bugs.launchpad.net/bugs/1896419 Title: Comet Lake CPUID family:model:stepping 0x6:a5:2 (6:165:2) is not included Status in OEM Priority Project: In Progress Status in thermald package in Ubuntu: In Progress Status in thermald source package in Focal: New Bug description: [Impact] * The CPUID is not included, which cause the thermald starts failed. Sep 15 17:07:00 ubuntu thermald[1089]: [WARN]Unsupported cpu model, use thermal-conf.xml file or run with --ignore-cpuid-check Sep 15 17:07:00 ubuntu thermald[1089]: [ERR]THD engine start failed Sep 15 17:07:00 ubuntu systemd[1]: thermald.service: Succeeded. * A upstream commit added missing CPUID https://github.com/intel/thermal_daemon/commit/7f2003ee911dd1c97ff74d2b84c62e10950bc9e0 [Test Case] On an affected system (Comet Lake): * $ systemctl is-active thermald active [Regression Potential] * Only new id added, no process or logic adjustment, so no regression risk. [Other Info] * The upstream bug: https://github.com/intel/thermal_daemon/issues/275 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1896419/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1890136] Re: Fix false-negative return value for rtnetlink.sh in kselftests/net
This bug was fixed in the package linux-hwe - 4.15.0-118.119~16.04.1
---
linux-hwe (4.15.0-118.119~16.04.1) xenial; urgency=medium
* xenial/linux-hwe: 4.15.0-118.119~16.04.1 -proposed tracker (LP:
#1894696)
[ Ubuntu: 4.15.0-118.119 ]
* bionic/linux: 4.15.0-118.119 -proposed tracker (LP: #1894697)
* Packaging resync (LP: #1786013)
- update dkms package versions
* Introduce the new NVIDIA 450-server and the 450 UDA series (LP: #1887674)
- [packaging] add signed modules for nvidia 450 and 450-server
* cgroup refcount is bogus when cgroup_sk_alloc is disabled (LP: #1886860)
- cgroup: add missing skcd->no_refcnt check in cgroup_sk_clone()
* CVE-2020-12888
- vfio/type1: Support faulting PFNMAP vmas
- vfio-pci: Fault mmaps to enable vma tracking
- vfio-pci: Invalidate mmaps and block MMIO access on disabled memory
* [Hyper-V] VSS and File Copy daemons intermittently fails to start
(LP: #1891224)
- [Packaging] Bind hv_vss_daemon startup to hv_vss device
- [Packaging] bind hv_fcopy_daemon startup to hv_fcopy device
* KVM: Fix zero_page reference counter overflow when using KSM on KVM compute
host (LP: #1837810)
- KVM: fix overflow of zero page refcount with ksm running
* Fix false-negative return value for rtnetlink.sh in kselftests/net
(LP: #1890136)
- selftests: rtnetlink: correct the final return value for the test
- selftests: rtnetlink: make kci_test_encap() return sub-test result
* Bionic update: upstream stable patchset 2020-08-18 (LP: #1892091)
- USB: serial: qcserial: add EM7305 QDL product ID
- USB: iowarrior: fix up report size handling for some devices
- usb: xhci: define IDs for various ASMedia host controllers
- usb: xhci: Fix ASMedia ASM1142 DMA addressing
- Revert "ALSA: hda: call runtime_allow() for all hda controllers"
- ALSA: seq: oss: Serialize ioctls
- staging: android: ashmem: Fix lockdep warning for write operation
- Bluetooth: Fix slab-out-of-bounds read in
hci_extended_inquiry_result_evt()
- Bluetooth: Prevent out-of-bounds read in hci_inquiry_result_evt()
- Bluetooth: Prevent out-of-bounds read in
hci_inquiry_result_with_rssi_evt()
- omapfb: dss: Fix max fclk divider for omap36xx
- binder: Prevent context manager from incrementing ref 0
- vgacon: Fix for missing check in scrollback handling
- mtd: properly check all write ioctls for permissions
- leds: wm831x-status: fix use-after-free on unbind
- leds: da903x: fix use-after-free on unbind
- leds: lm3533: fix use-after-free on unbind
- leds: 88pm860x: fix use-after-free on unbind
- net/9p: validate fds in p9_fd_open
- drm/nouveau/fbcon: fix module unload when fbcon init has failed for some
reason
- drm/nouveau/fbcon: zero-initialise the mode_cmd2 structure
- i2c: slave: improve sanity check when registering
- i2c: slave: add sanity check when unregistering
- usb: hso: check for return value in hso_serial_common_create()
- firmware: Fix a reference count leak.
- cfg80211: check vendor command doit pointer before use
- igb: reinit_locked() should be called with rtnl_lock
- atm: fix atm_dev refcnt leaks in atmtcp_remove_persistent
- tools lib traceevent: Fix memory leak in process_dynamic_array_len
- Drivers: hv: vmbus: Ignore CHANNELMSG_TL_CONNECT_RESULT(23)
- xattr: break delegations in {set,remove}xattr
- ipv4: Silence suspicious RCU usage warning
- ipv6: fix memory leaks on IPV6_ADDRFORM path
- net: ethernet: mtk_eth_soc: fix MTU warnings
- vxlan: Ensure FDB dump is performed under RCU
- net: lan78xx: replace bogus endpoint lookup
- hv_netvsc: do not use VF device if link is down
- net: gre: recompute gre csum for sctp over gre tunnels
- openvswitch: Prevent kernel-infoleak in ovs_ct_put_key()
- Revert "vxlan: fix tos value before xmit"
- selftests/net: relax cpu affinity requirement in msg_zerocopy test
- rxrpc: Fix race between recvmsg and sendmsg on immediate call failure
- i40e: add num_vectors checker in iwarp handler
- i40e: Wrong truncation from u16 to u8
- i40e: Memory leak in i40e_config_iwarp_qvlist
- Smack: fix use-after-free in smk_write_relabel_self()
* Bionic update: upstream stable patchset 2020-08-11 (LP: #1891228)
- AX.25: Fix out-of-bounds read in ax25_connect()
- AX.25: Prevent out-of-bounds read in ax25_sendmsg()
- dev: Defer free of skbs in flush_backlog
- drivers/net/wan/x25_asy: Fix to make it work
- net-sysfs: add a newline when printing 'tx_timeout' by sysfs
- net: udp: Fix wrong clean up for IS_UDPLITE macro
- rxrpc: Fix sendmsg() returning EPIPE due to recvmsg() returning ENODATA
- AX.25: Prevent integer overflows in connect and sendmsg
- ip6_gre: fix null-ptr-deref in ip6gre_init_net()
- rtnetlink: Fix memory(net_device) leak when ->newlink fails
- tcp: allow at most one TLP probe
[Kernel-packages] [Bug 1886277] Re: Regression on NFS: unable to handle page fault in mempool_alloc_slab
This bug was fixed in the package linux - 5.4.0-48.52 --- linux (5.4.0-48.52) focal; urgency=medium * focal/linux: 5.4.0-48.52 -proposed tracker (LP: #1894654) * mm/slub kernel oops on focal kernel 5.4.0-45 (LP: #1895109) - SAUCE: Revert "mm/slub: fix a memory leak in sysfs_slab_add()" * Packaging resync (LP: #1786013) - update dkms package versions - update dkms package versions * Introduce the new NVIDIA 450-server and the 450 UDA series (LP: #1887674) - [packaging] add signed modules for nvidia 450 and 450-server * [UBUNTU 20.04] zPCI attach/detach issues with PF/VF linking support (LP: #1892849) - s390/pci: fix zpci_bus_link_virtfn() - s390/pci: re-introduce zpci_remove_device() - s390/pci: fix PF/VF linking on hot plug * [UBUNTU 20.04] kernel: s390/cpum_cf,perf: changeDFLT_CCERROR counter name (LP: #1891454) - s390/cpum_cf, perf: change DFLT_CCERROR counter name * [UBUNTU 20.04] zPCI: Enabling of a reserved PCI function regression introduced by multi-function support (LP: #1891437) - s390/pci: fix enabling a reserved PCI function * CVE-2020-12888 - vfio/type1: Support faulting PFNMAP vmas - vfio-pci: Fault mmaps to enable vma tracking - vfio-pci: Invalidate mmaps and block MMIO access on disabled memory * [Hyper-V] VSS and File Copy daemons intermittently fails to start (LP: #1891224) - [Packaging] Bind hv_vss_daemon startup to hv_vss device - [Packaging] bind hv_fcopy_daemon startup to hv_fcopy device * alsa/hdmi: support nvidia mst hdmi/dp audio (LP: #1867704) - ALSA: hda - Rename snd_hda_pin_sense to snd_hda_jack_pin_sense - ALSA: hda - Add DP-MST jack support - ALSA: hda - Add DP-MST support for non-acomp codecs - ALSA: hda - Add DP-MST support for NVIDIA codecs - ALSA: hda: hdmi - fix regression in connect list handling - ALSA: hda: hdmi - fix kernel oops caused by invalid PCM idx - ALSA: hda: hdmi - preserve non-MST PCM routing for Intel platforms - ALSA: hda: hdmi - Keep old slot assignment behavior for Intel platforms - ALSA: hda - Fix DP-MST support for NVIDIA codecs * Focal update: v5.4.60 upstream stable release (LP: #1892899) - smb3: warn on confusing error scenario with sec=krb5 - genirq/affinity: Make affinity setting if activated opt-in - genirq/PM: Always unlock IRQ descriptor in rearm_wake_irq() - PCI: hotplug: ACPI: Fix context refcounting in acpiphp_grab_context() - PCI: Add device even if driver attach failed - PCI: qcom: Define some PARF params needed for ipq8064 SoC - PCI: qcom: Add support for tx term offset for rev 2.1.0 - btrfs: allow use of global block reserve for balance item deletion - btrfs: free anon block device right after subvolume deletion - btrfs: don't allocate anonymous block device for user invisible roots - btrfs: ref-verify: fix memory leak in add_block_entry - btrfs: stop incremening log_batch for the log root tree when syncing log - btrfs: remove no longer needed use of log_writers for the log root tree - btrfs: don't traverse into the seed devices in show_devname - btrfs: open device without device_list_mutex - btrfs: move the chunk_mutex in btrfs_read_chunk_tree - btrfs: relocation: review the call sites which can be interrupted by signal - btrfs: add missing check for nocow and compression inode flags - btrfs: avoid possible signal interruption of btrfs_drop_snapshot() on relocation tree - btrfs: sysfs: use NOFS for device creation - btrfs: don't WARN if we abort a transaction with EROFS - btrfs: fix race between page release and a fast fsync - btrfs: fix messages after changing compression level by remount - btrfs: only search for left_info if there is no right_info in try_merge_free_space - btrfs: inode: fix NULL pointer dereference if inode doesn't need compression - btrfs: fix memory leaks after failure to lookup checksums during inode logging - btrfs: make sure SB_I_VERSION doesn't get unset by remount - btrfs: fix return value mixup in btrfs_get_extent - arm64: perf: Correct the event index in sysfs - dt-bindings: iio: io-channel-mux: Fix compatible string in example code - iio: dac: ad5592r: fix unbalanced mutex unlocks in ad5592r_read_raw() - xtensa: add missing exclusive access state management - xtensa: fix xtensa_pmu_setup prototype - cifs: Fix leak when handling lease break for cached root fid - powerpc/ptdump: Fix build failure in hashpagetable.c - powerpc: Allow 4224 bytes of stack expansion for the signal frame - powerpc: Fix circular dependency between percpu.h and mmu.h - pinctrl: ingenic: Enhance support for IRQ_TYPE_EDGE_BOTH - media: vsp1: dl: Fix NULL pointer dereference on unbind - net: ethernet: stmmac: Disable hardware multicast filter - net: stmmac: dwmac1000: provide multicast filter fallback
