[Kernel-packages] [Bug 1930188] Re: Acer Aspire 5 sound driver issues
Glad to know it won't take too long to be available in ubuntu. This is a very popular budget laptop so many ubuntu users will be happy when the sound driver issues are fixed and everything works smoothly. Will wait patiently for a notification from this thread that the fixes are now available officially in ubuntu also really appreciate this being fixed so quickly that I expected. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1930188 Title: Acer Aspire 5 sound driver issues Status in linux package in Ubuntu: New Bug description: Hello, There seems to be lots of issues in sound driver for Acer Aspire A515-56-57XR with ALC255. I will list all of them below and what I have tried so far. 1. Headphones appears always plugged in even if they are physically not 2. When actually plugging in headset/earphones it does not auto switch from speakers/internal mic to headphones/headset microphone automatically and vice versa, have to manually switch everytime. 3. External headset/earphones microphone won't work at all After, logs of trial and error I have found a temporary fix. This seems to use legacy intel drivers which solves all 3 issues mentioned above but the internal/dmic mic is completely gone (which seems intentional when using this). Both depreciated dmic_detect and dsp_driver works, I have been using dsp_driver for now as I need external microphone at any cost. End of /etc/modprobe.d/alsa-base.conf # Headset mic fix options snd-hda-intel dmic_detect=0 / options snd-intel-dspcfg dsp_driver=1 options snd-hda-intel model=alc255-acer In another thread similar to this I got some support and at least fixed the external microphone without using the alsa-base.conf change in custom modified kernel. I will attach it here. Now, hoping to fix other issues as well slowly like making headphones unplugged when physically removing as well as auto switching like the legacy driver one. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1930188/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1929657] Re: [Ubuntu 20.4.2] vLan not getting static IP assigned (on s390x)
Oh, I simply meant using the 'ip' command, like (in my example): $ ip a | grep enP1 6: enP1p0s0: mtu 1500 qdisc mq state UP group default qlen 1000 $ sudo ip link add link enP1p0s0 name enP1p0s0.1234 type vlan id 1234 $ sudo ip addr add 192.168.1.201/24 dev enP1p0s0 $ sudo ip addr add 192.168.1.202/24 dev enP1p0s0.1234 $ sudo ip link set dev enP1p0s0 up $ sudo ip link set dev enP1p0s0.1234 up $ ip a -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1929657 Title: [Ubuntu 20.4.2] vLan not getting static IP assigned (on s390x) Status in Ubuntu on IBM z Systems: Incomplete Status in linux package in Ubuntu: New Status in netplan.io package in Ubuntu: New Bug description: ---Problem Description--- Doing vLAN configuration one of the vLANs is not getting static IP assigned when the rest are workin without problems Contact Information = Mario Alvarado/mario.alberto.gali...@ibm.com ---uname output--- Linux ilabg13.tuc.stglabs.ibm.com 5.4.0-73-generic #82-Ubuntu SMP Wed Apr 14 17:29:32 UTC 2021 s390x s390x s390x GNU/Linux Machine Type = z15 ---Debugger--- A debugger is not configured ---Steps to Reproduce--- 1)Configure the netplan file as follow: root@ilabg13:~# cat /etc/netplan/01-iscsi-config.yaml # This is the network config written by 'subiquity' network: ethernets: encdb0: addresses: - 11.111.114.213/22 macaddress: 02:76:54:00:00:03 encdc0: addresses: - 11.111.112.213/22 macaddress: 02:76:54:00:00:04 enP50s3832 : addresses: - 11.111.112.214/22 enP53p0s0: addresses: - 11.111.112.215/22 vlans: encdb0.160: id: 160 link: encdb0 mtu: 9000 addresses: - 192.168.160.53/24 encdc0.150: id: 150 link: encdc0 mtu: 9000 addresses: - 192.168.150.53/24 enP50s3832.170: id: 170 link: enP50s3832 mtu: 9000 addresses: - 192.168.170.53/24 enP53p0s0.171: id: 171 link: enP53p0s0 mtu: 9000 addresses: - 192.168.171.53/24 version: 2 2)run net plan apply: root@ilabg13:~# netplan --debug apply ** (generate:59965): DEBUG: 14:55:15.046: Processing input file /etc/netplan/00-installer-config.yaml.. ** (generate:59965): DEBUG: 14:55:15.046: starting new processing pass ** (generate:59965): DEBUG: 14:55:15.046: Processing input file /etc/netplan/01-iscsi-config.yaml.. ** (generate:59965): DEBUG: 14:55:15.046: starting new processing pass ** (generate:59965): DEBUG: 14:55:15.046: We have some netdefs, pass them through a final round of validation ** (generate:59965): DEBUG: 14:55:15.046: encdc0: setting default backend to 1 ** (generate:59965): DEBUG: 14:55:15.046: Configuration is valid ** (generate:59965): DEBUG: 14:55:15.046: encdb0: setting default backend to 1 ** (generate:59965): DEBUG: 14:55:15.046: Configuration is valid ** (generate:59965): DEBUG: 14:55:15.046: ence0f: setting default backend to 1 ** (generate:59965): DEBUG: 14:55:15.046: Configuration is valid ** (generate:59965): DEBUG: 14:55:15.046: encdb0.160: setting default backend to 1 ** (generate:59965): DEBUG: 14:55:15.046: Configuration is valid ** (generate:59965): DEBUG: 14:55:15.046: enP50s3832: setting default backend to 1 ** (generate:59965): DEBUG: 14:55:15.046: Configuration is valid ** (generate:59965): DEBUG: 14:55:15.046: enP53p0s0.171: setting default backend to 1 ** (generate:59965): DEBUG: 14:55:15.046: Configuration is valid ** (generate:59965): DEBUG: 14:55:15.046: enP50s3832.170: setting default backend to 1 ** (generate:59965): DEBUG: 14:55:15.046: Configuration is valid ** (generate:59965): DEBUG: 14:55:15.046: enP53p0s0: setting default backend to 1 ** (generate:59965): DEBUG: 14:55:15.046: Configuration is valid ** (generate:59965): DEBUG: 14:55:15.046: encdc0.150: setting default backend to 1 ** (generate:59965): DEBUG: 14:55:15.046: Configuration is valid ** (generate:59965): DEBUG: 14:55:15.047: Generating output files.. ** (generate:59965): DEBUG: 14:55:15.047: openvswitch: definition ence0f is not for us (backend 1) ** (generate:59965): DEBUG: 14:55:15.047: NetworkManager: definition ence0f is not for us (backend 1) ** (generate:59965): DEBUG: 14:55:15.047: openvswitch: definition encdb0 is not for us (backend 1) ** (generate:59965): DEBUG: 14:55:15.047: NetworkManager: definition encdb0 is not for us (backend 1) ** (generate:59965): DEBUG: 14:55:15.047: openvswitch: definition encdc0 is not for us (backend 1) ** (generate:59965): DEBUG: 14:55:15.047: NetworkManager: definition encdc0 is not for us (backend 1)
[Kernel-packages] [Bug 1930976] Re: 5.8.0-55 kernel issue with RTX 3080 on Nvidia drivers
** Tags added: nvidia ** Package changed: xorg (Ubuntu) => linux-hwe-5.8 (Ubuntu) ** Tags added: regression-update -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-460 in Ubuntu. https://bugs.launchpad.net/bugs/1930976 Title: 5.8.0-55 kernel issue with RTX 3080 on Nvidia drivers Status in linux-hwe-5.8 package in Ubuntu: New Status in nvidia-graphics-drivers-460 package in Ubuntu: New Bug description: Kernel: 5.8.0-55 The last kernel destroyed my Ubuntu 20.04.02 installation, something went wrong with some kernel packages. It seems like Ubuntu is unable to find my video card correctly and the device drivers from Nvidia don't seem to work anymore. I had to do a clean installation, but even that doesn't solve the problem. I think this is a serious issue that needs to be looked into. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.8.0-55.62~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-55-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CompositorRunning: None Date: Sat Jun 5 16:50:38 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu GraphicsCard: NVIDIA Corporation Device [10de:2206] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd Device [1458:403f] InstallationDate: Installed on 2021-06-05 (0 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: Gigabyte Technology Co., Ltd. X570 AORUS MASTER ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=nl_NL.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-55-generic root=UUID=4984fe2f-d45f-4734-884c-2426bcf10ca4 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/23/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: F33j dmi.board.asset.tag: Default string dmi.board.name: X570 AORUS MASTER dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF33j:bd04/23/2021:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnX570AORUSMASTER:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnX570AORUSMASTER:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: X570 MB dmi.product.name: X570 AORUS MASTER dmi.product.sku: Default string dmi.product.version: -CF dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.8/+bug/1930976/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1926236] Re: Fix The sound has noise while audio volume is maximum
** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- 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/1926236 Title: Fix The sound has noise while audio volume is maximum Status in HWE Next: New Status in linux-firmware package in Ubuntu: Fix Released Status in linux-firmware source package in Focal: Fix Committed Bug description: [Impact] The sound has noise while turning the audio volume to maximum [Fix] For VEGA & Polaris, need two patches(landed on mainline kernel) to fix and a modprobe 1.(50ceb1fe7a) drm/amd/pm: bug fix for pcie dpm, has landed on oem kernel. 2.(9d03730ecb) drm/amd/pm: workaround for audio noise issue, has landed on oem kernel 3. #modprobe amdgpu ppfeaturemask=0xfff7bffb. For Navi_1x, need smc firmware to fix. 1. (4fe6e53b96 linux-firmware) amdgpu: update navi10 SMC firmware 1. (8ab7abaf63 linux-firmware) amdgpu: update navi14 SMC firmware [Test] Verified on RKL platform A. with wx3200(Polaris series) and the following configuration 1. With these two patch, 1.1. (50ceb1fe7a) drm/amd/pm: bug fix for pcie dpm, has landed on oem kernel. 1.2. (9d03730ecb) drm/amd/pm: workaround for audio noise issue, has landed on oem kernel 2. doesn't append ppfeaturemask=0xfff7bffb Can't observe issue. B. With wx5500(Navi series) and update the related firmware, Can't observe issue [Where problems could occur] Because disabling DPM, the power consumption would be slightly higher. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1926236/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1930903] Re: Frequent kernel oops related to nvidia / nv_drm_master_set
** Tags added: nvidia ** Package changed: xorg (Ubuntu) => nvidia-graphics-drivers-460 (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-460 in Ubuntu. https://bugs.launchpad.net/bugs/1930903 Title: Frequent kernel oops related to nvidia / nv_drm_master_set Status in nvidia-graphics-drivers-460 package in Ubuntu: New Bug description: After upgrading yesterday from ubuntu 20 to 21.04 my machine now exhibits frequent involuntary restarts, related to a kernel oops of the form Jun 3 10:48:32 zotac kernel: [ 20.464926] RIP: 0010:nv_drm_master_set+0x27/0x30 [nvidia_drm] [...] Jun 3 10:48:32 zotac kernel: [ 20.464958] Call Trace: Jun 3 10:48:32 zotac kernel: [ 20.464964] drm_new_set_master+0x7e/0x100 [drm] Jun 3 10:48:32 zotac kernel: [ 20.464994] drm_master_open+0x6e/0xa0 [drm] Jun 3 10:48:32 zotac kernel: [ 20.465017] drm_open+0xf8/0x250 [drm] Jun 3 10:48:32 zotac kernel: [ 20.465044] drm_stub_open+0xba/0x140 [drm] Jun 3 10:48:32 zotac kernel: [ 20.465070] chrdev_open+0xf7/0x220 Jun 3 10:48:32 zotac kernel: [ 20.465075] ? cdev_device_add+0x90/0x90 Jun 3 10:48:32 zotac kernel: [ 20.465078] do_dentry_open+0x156/0x370 Jun 3 10:48:32 zotac kernel: [ 20.465081] vfs_open+0x2d/0x30 Jun 3 10:48:32 zotac kernel: [ 20.465084] do_open+0x1c3/0x340 Jun 3 10:48:32 zotac kernel: [ 20.465087] path_openat+0x10a/0x1d0 Jun 3 10:48:32 zotac kernel: [ 20.465090] do_filp_open+0x8c/0x130 Jun 3 10:48:32 zotac kernel: [ 20.465093] ? __check_object_size+0x1c/0x20 Jun 3 10:48:32 zotac kernel: [ 20.465096] do_sys_openat2+0x9b/0x150 Jun 3 10:48:32 zotac kernel: [ 20.465099] __x64_sys_openat+0x56/0x90 Jun 3 10:48:32 zotac kernel: [ 20.465102] do_syscall_64+0x38/0x90 Jun 3 10:48:32 zotac kernel: [ 20.465105] entry_SYSCALL_64_after_hwframe+0x44/0xa9 Jun 3 10:48:32 zotac kernel: [ 20.465108] RIP: 0033:0x7fe6ea270954 ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: xorg 1:7.7+22ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-18.19-generic 5.11.17 Uname: Linux 5.11.0-18-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..0a.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 460.80 Fri May 7 06:55:54 UTC 2021 GCC version: gcc version 10.3.0 (Ubuntu 10.3.0-1ubuntu1) ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: unknown Date: Fri Jun 4 17:00:45 2021 DistUpgraded: Fresh install DistroCodename: hirsute DistroVariant: ubuntu DkmsStatus: nvidia, 460.80, 5.11.0-18-generic, x86_64: installed nvidia, 460.80, 5.8.0-53-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation GP106 [GeForce GTX 1060 3GB] [10de:1c02] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ZOTAC International (MCO) Ltd. GP106 [GeForce GTX 1060 3GB] [19da:2438] InstallationDate: Installed on 2020-05-09 (391 days ago) InstallationMedia: Xubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: NA ZBOX-ER51070 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-18-generic root=UUID=4e73512b-1846-4fe4-87d1-079bbaae2a1a ro quiet splash crashkernel=512M-:192M vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/25/2019 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5.12 dmi.board.asset.tag: Default string dmi.board.name: ZBOX-ER51070 dmi.board.vendor: NA dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr5.12:bd04/25/2019:br5.12:svnNA:pnZBOX-ER51070:pvrDefaultstring:rvnNA:rnZBOX-ER51070:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: ZBOX-ER51070 dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: NA version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.104-1build1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.1-2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati:
[Kernel-packages] [Bug 1930925] Re: Ubuntu 20.04 doesn't work with Logitech, Inc. Unifying Receiver over a KVM
** Summary changed: - Ubuntu 20.04 doesn't work with moidern KVMs + Ubuntu 20.04 doesn't work with Logitech, Inc. Unifying Receiver over a KVM ** Package changed: xorg (Ubuntu) => linux (Ubuntu) ** Tags added: kvm ** Summary changed: - Ubuntu 20.04 doesn't work with Logitech, Inc. Unifying Receiver over a KVM + Ubuntu 20.04 doesn't work with Logitech, Inc. Unifying Receiver over a KVM switch -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1930925 Title: Ubuntu 20.04 doesn't work with Logitech, Inc. Unifying Receiver over a KVM switch Status in linux package in Ubuntu: New Bug description: I have recently acquired a acquired a desktop running ubuntu 20.04. I have several computers and switch between them using this KVM https://www.amazon.co.uk/gp/product/B077SV9MMQ/ref=ppx_yo_dt_b_search_asin_title?ie=UTF8=1 The other machines are either running windows or ubuntu 18.04 or earlier. They are all fine, but the with 20.04 machine neither the keyboard nor the mouse works. On the 18.04 machine I can see lsusb Bus 002 Device 002: ID 8087:8000 Intel Corp. Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 8087:8008 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 005: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub and it is the Logitech, Inc. Unifying Receiver which appears when the USB from the KVM is connected. On the 20.04 machine only this appears lsusb Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0b05:19af ASUSTek Computer, Inc. AURA LED Controller Bus 001 Device 002: ID 05e3:0610 Genesys Logic, Inc. 4-port hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub I have tested installation discs from 19.04 onwards. The failure first appears in 19.10 and is still present in 21.04 I can observe a similar problem with a dual boot laptop running windows 10 and 20.04. With windows 10 I can use it with the KVM for screen and keyboard/mouse, but with ubuntu 20.04 the keyboard and mouse do not work. This issue has also been observed here https://unix.stackexchange.com/questions/646515/using-logitech-mouse- keyboard-on-tesmart-kvm-switch-with-ubuntu-20-04 and I have observed it using a Lindy 2 port HDMI/USB KVM (but I'm unsure of the model). I had to report this originally against xorg as this bug reporting system seems not to allow reporting of bugs against unknown packages. I also had to report it through the ubuntu-bug executable as I've been unable to find a way in launchpad of reporting a bug (as opposed to getting a guided tour about reporting bugs). I am happy to supply more info and test fixes if I am asked but as with this type of bug where something fails to happen rather than something wrong happens I don't know what to look at. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.8.0-53.60~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-53-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None Date: Fri Jun 4 20:21:15 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DpkgLog: ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:4c8a] (rev 04) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:8694] InstallationDate: Installed on 2021-05-14 (21 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0b05:19af ASUSTek Computer, Inc. AURA LED Controller Bus 001 Device 002: ID 05e3:0610 Genesys Logic, Inc. 4-port hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/8p, 1M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/16p, 480M |__ Port 11: Dev 2, If 0, Class=Hub, Driver=hub/4p, 480M |__ Port 13: Dev 3, If 0, Class=Vendor Specific Class, Driver=, 12M |__ Port 13: Dev 3, If 2, Class=Human Interface Device, Driver=usbhid, 12M MachineType: ASUS System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-53-generic root=UUID=0c391c11-c570-4e04-a351-4fd128a75369 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/27/2021 dmi.bios.release: 8.20 dmi.bios.vendor: American Megatrends Inc.
[Kernel-packages] [Bug 1927925] Re: Massive network problems with I219-V on Thinkpad T14 Gen2 (e1000e)
Just booted the kernel from #64 without the parameter - downloads suffer from slow speeds, ethtool reports rx_errors and rx_crc_errors again. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1927925 Title: Massive network problems with I219-V on Thinkpad T14 Gen2 (e1000e) Status in OEM Priority Project: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: I recently got a Thinkpad T14 Gen2 with a I219-V network adapter (8086:15fc). I get very slow connection speeds and even total loss of connectivity without seeing much in the logs (like dmesg etc.). ethtool reports CRC errors and paket loss. Besides Ubuntu 21.04/kernel 5.11 I tried to install Ubuntu 20.04 (kernel seems to old) and i tried the e1000e driver directly from upstream (3.8.7) with no success. A strange behaviour I observed: if connectivity is lost (notebook is not reachable via ping from another host), if I do something like "ping 8.8.8.8" on the notebook itself, it becomes reachable from the other host again. Downloads in general are very slow if they work at all. WLAN (AX210) seems to work fine, wired network using a USB-network adapter works fine, too. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ros3285 F pulseaudio CasperMD5CheckResult: pass DistroRelease: Ubuntu 21.04 HibernationDevice: RESUME=none InstallationDate: Installed on 2021-05-07 (2 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: LENOVO 20W0004MGE NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_n51dtp@/vmlinuz-5.11.0-16-generic root=ZFS=rpool/ROOT/ubuntu_n51dtp ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.11.0-16-generic N/A linux-backports-modules-5.11.0-16-generic N/A linux-firmware 1.197 Tags: hirsute Uname: Linux 5.11.0-16-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 03/10/2021 dmi.bios.release: 1.10 dmi.bios.vendor: LENOVO dmi.bios.version: N34ET21W (1.10 ) dmi.board.asset.tag: Not Available dmi.board.name: 20W0004MGE 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.ec.firmware.release: 1.8 dmi.modalias: dmi:bvnLENOVO:bvrN34ET21W(1.10):bd03/10/2021:br1.10:efr1.8:svnLENOVO:pn20W0004MGE:pvrThinkPadT14Gen2i:rvnLENOVO:rn20W0004MGE:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T14 Gen 2i dmi.product.name: 20W0004MGE dmi.product.sku: LENOVO_MT_20W0_BU_Think_FM_ThinkPad T14 Gen 2i dmi.product.version: ThinkPad T14 Gen 2i dmi.sys.vendor: LENOVO --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ros1673 F pulseaudio /dev/snd/controlC1: ros1673 F pulseaudio CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-05-31 (0 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: LENOVO 20W0004MGE Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.10.0-1026-oem root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.10.0-1026.27-oem 5.10.31 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.10.0-1026-oem N/A linux-backports-modules-5.10.0-1026-oem N/A linux-firmware 1.187.12 Tags: focal Uname: Linux 5.10.0-1026-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 03/10/2021 dmi.bios.release: 1.10 dmi.bios.vendor: LENOVO dmi.bios.version: N34ET21W (1.10 ) dmi.board.asset.tag: Not Available dmi.board.name: 20W0004MGE 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.ec.firmware.release: 1.8 dmi.modalias:
[Kernel-packages] [Bug 1930925] [NEW] Ubuntu 20.04 doesn't work with Logitech, Inc. Unifying Receiver over a KVM
You have been subscribed to a public bug: I have recently acquired a acquired a desktop running ubuntu 20.04. I have several computers and switch between them using this KVM https://www.amazon.co.uk/gp/product/B077SV9MMQ/ref=ppx_yo_dt_b_search_asin_title?ie=UTF8=1 The other machines are either running windows or ubuntu 18.04 or earlier. They are all fine, but the with 20.04 machine neither the keyboard nor the mouse works. On the 18.04 machine I can see lsusb Bus 002 Device 002: ID 8087:8000 Intel Corp. Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 8087:8008 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 005: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub and it is the Logitech, Inc. Unifying Receiver which appears when the USB from the KVM is connected. On the 20.04 machine only this appears lsusb Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0b05:19af ASUSTek Computer, Inc. AURA LED Controller Bus 001 Device 002: ID 05e3:0610 Genesys Logic, Inc. 4-port hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub I have tested installation discs from 19.04 onwards. The failure first appears in 19.10 and is still present in 21.04 I can observe a similar problem with a dual boot laptop running windows 10 and 20.04. With windows 10 I can use it with the KVM for screen and keyboard/mouse, but with ubuntu 20.04 the keyboard and mouse do not work. This issue has also been observed here https://unix.stackexchange.com/questions/646515/using-logitech-mouse- keyboard-on-tesmart-kvm-switch-with-ubuntu-20-04 and I have observed it using a Lindy 2 port HDMI/USB KVM (but I'm unsure of the model). I had to report this originally against xorg as this bug reporting system seems not to allow reporting of bugs against unknown packages. I also had to report it through the ubuntu-bug executable as I've been unable to find a way in launchpad of reporting a bug (as opposed to getting a guided tour about reporting bugs). I am happy to supply more info and test fixes if I am asked but as with this type of bug where something fails to happen rather than something wrong happens I don't know what to look at. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.8.0-53.60~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-53-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None Date: Fri Jun 4 20:21:15 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DpkgLog: ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:4c8a] (rev 04) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:8694] InstallationDate: Installed on 2021-05-14 (21 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0b05:19af ASUSTek Computer, Inc. AURA LED Controller Bus 001 Device 002: ID 05e3:0610 Genesys Logic, Inc. 4-port hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/8p, 1M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/16p, 480M |__ Port 11: Dev 2, If 0, Class=Hub, Driver=hub/4p, 480M |__ Port 13: Dev 3, If 0, Class=Vendor Specific Class, Driver=, 12M |__ Port 13: Dev 3, If 2, Class=Human Interface Device, Driver=usbhid, 12M MachineType: ASUS System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-53-generic root=UUID=0c391c11-c570-4e04-a351-4fd128a75369 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/27/2021 dmi.bios.release: 8.20 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0820 dmi.board.asset.tag: Default string dmi.board.name: PRIME H570M-PLUS 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.:bvr0820:bd04/27/2021:br8.20:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEH570M-PLUS:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: ASUS version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1 version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1
[Kernel-packages] [Bug 1930903] [NEW] Frequent kernel oops related to nvidia / nv_drm_master_set
You have been subscribed to a public bug: After upgrading yesterday from ubuntu 20 to 21.04 my machine now exhibits frequent involuntary restarts, related to a kernel oops of the form Jun 3 10:48:32 zotac kernel: [ 20.464926] RIP: 0010:nv_drm_master_set+0x27/0x30 [nvidia_drm] [...] Jun 3 10:48:32 zotac kernel: [ 20.464958] Call Trace: Jun 3 10:48:32 zotac kernel: [ 20.464964] drm_new_set_master+0x7e/0x100 [drm] Jun 3 10:48:32 zotac kernel: [ 20.464994] drm_master_open+0x6e/0xa0 [drm] Jun 3 10:48:32 zotac kernel: [ 20.465017] drm_open+0xf8/0x250 [drm] Jun 3 10:48:32 zotac kernel: [ 20.465044] drm_stub_open+0xba/0x140 [drm] Jun 3 10:48:32 zotac kernel: [ 20.465070] chrdev_open+0xf7/0x220 Jun 3 10:48:32 zotac kernel: [ 20.465075] ? cdev_device_add+0x90/0x90 Jun 3 10:48:32 zotac kernel: [ 20.465078] do_dentry_open+0x156/0x370 Jun 3 10:48:32 zotac kernel: [ 20.465081] vfs_open+0x2d/0x30 Jun 3 10:48:32 zotac kernel: [ 20.465084] do_open+0x1c3/0x340 Jun 3 10:48:32 zotac kernel: [ 20.465087] path_openat+0x10a/0x1d0 Jun 3 10:48:32 zotac kernel: [ 20.465090] do_filp_open+0x8c/0x130 Jun 3 10:48:32 zotac kernel: [ 20.465093] ? __check_object_size+0x1c/0x20 Jun 3 10:48:32 zotac kernel: [ 20.465096] do_sys_openat2+0x9b/0x150 Jun 3 10:48:32 zotac kernel: [ 20.465099] __x64_sys_openat+0x56/0x90 Jun 3 10:48:32 zotac kernel: [ 20.465102] do_syscall_64+0x38/0x90 Jun 3 10:48:32 zotac kernel: [ 20.465105] entry_SYSCALL_64_after_hwframe+0x44/0xa9 Jun 3 10:48:32 zotac kernel: [ 20.465108] RIP: 0033:0x7fe6ea270954 ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: xorg 1:7.7+22ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-18.19-generic 5.11.17 Uname: Linux 5.11.0-18-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..0a.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 460.80 Fri May 7 06:55:54 UTC 2021 GCC version: gcc version 10.3.0 (Ubuntu 10.3.0-1ubuntu1) ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: unknown Date: Fri Jun 4 17:00:45 2021 DistUpgraded: Fresh install DistroCodename: hirsute DistroVariant: ubuntu DkmsStatus: nvidia, 460.80, 5.11.0-18-generic, x86_64: installed nvidia, 460.80, 5.8.0-53-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation GP106 [GeForce GTX 1060 3GB] [10de:1c02] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ZOTAC International (MCO) Ltd. GP106 [GeForce GTX 1060 3GB] [19da:2438] InstallationDate: Installed on 2020-05-09 (391 days ago) InstallationMedia: Xubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: NA ZBOX-ER51070 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-18-generic root=UUID=4e73512b-1846-4fe4-87d1-079bbaae2a1a ro quiet splash crashkernel=512M-:192M vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/25/2019 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5.12 dmi.board.asset.tag: Default string dmi.board.name: ZBOX-ER51070 dmi.board.vendor: NA dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr5.12:bd04/25/2019:br5.12:svnNA:pnZBOX-ER51070:pvrDefaultstring:rvnNA:rnZBOX-ER51070:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: ZBOX-ER51070 dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: NA version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.104-1build1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.1-2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1 ** Affects: nvidia-graphics-drivers-460 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug hirsute nvidia ubuntu -- Frequent kernel oops related to nvidia / nv_drm_master_set https://bugs.launchpad.net/bugs/1930903 You received this bug notification because you are a member of Kernel Packages, which is subscribed to
[Kernel-packages] [Bug 1907262] Re: raid10: discard leads to corrupted file system
Hi Thimo, The kernel team have built all of the kernels for this SRU cycle, and have placed them into -proposed for verification. We now need to do some thorough testing and make sure that Raid10 arrays function with good performance, ensure data integrity and make sure we won't be introducing any regressions when these kernels are released in two weeks time. I would really appreciate it if you could help test and verify these kernels function as intended. Instructions to Install: 1) cat << EOF | sudo tee /etc/apt/sources.list.d/ubuntu-$(lsb_release -cs)-proposed.list # Enable Ubuntu proposed archive deb http://archive.ubuntu.com/ubuntu/ $(lsb_release -cs)-proposed main universe EOF 2) sudo apt update For 21.04 / Hirsute: 3) sudo apt install linux-image-5.11.0-20-generic linux-modules-5.11.0-20-generic \ linux-modules-extra-5.11.0-20-generic linux-headers-5.11.0-20-generic For 20.10 / Groovy: 3) sudo apt install linux-image-5.8.0-56-generic linux-modules-5.8.0-56-generic \ linux-modules-extra-5.8.0-56-generic linux-headers-5.8.0-56-generic For 20.04 / Focal: 3) sudo apt install linux-image-5.4.0-75-generic linux-modules-5.4.0-75-generic \ linux-modules-extra-5.4.0-75-generic linux-headers-5.4.0-75-generic For 18.04 / Bionic: For the 5.4 Bionic HWE Kernel: 3) sudo apt install linux-image-5.4.0-75-generic linux-modules-5.4.0-75-generic \ linux-modules-extra-5.4.0-75-generic linux-headers-5.4.0-75-generic For the 4.15 Bionic GA Kernel: 3) sudo apt install linux-image-4.15.0-145-generic linux-modules-4.15.0-145-generic \ linux-modules-extra-4.15.0-145-generic linux-headers-4.15.0-145-generic 4) sudo reboot 5) uname -rv You may need to modify your grub configuration to boot the correct kernel. If you need help, read these instructions: https://paste.ubuntu.com/p/XrTzWPPnWJ/ I am running the -proposed kernel on my cloud instance with my /home directory on a Raid10 array made up of 4x NVMe devices, and things are looking okay. I will be performing my detailed regression testing against these kernels tomorrow, and I will write back with the results then. Please help test these kernels in -proposed, and let me know how they go. Thanks, Matthew -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1907262 Title: raid10: discard leads to corrupted file system Status in linux package in Ubuntu: Fix Released Status in linux source package in Trusty: Invalid Status in linux source package in Xenial: Invalid Status in linux source package in Bionic: Fix Released Status in linux source package in Focal: Fix Released Status in linux source package in Groovy: Fix Released Bug description: Seems to be closely related to https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1896578 After updating the Ubuntu 18.04 kernel from 4.15.0-124 to 4.15.0-126 the fstrim command triggered by fstrim.timer causes a severe number of mismatches between two RAID10 component devices. This bug affects several machines in our company with different HW configurations (All using ECC RAM). Both, NVMe and SATA SSDs are affected. How to reproduce: - Create a RAID10 LVM and filesystem on two SSDs mdadm -C -v -l10 -n2 -N "lv-raid" -R /dev/md0 /dev/nvme0n1p2 /dev/nvme1n1p2 pvcreate -ff -y /dev/md0 vgcreate -f -y VolGroup /dev/md0 lvcreate -n root-L 100G -ay -y VolGroup mkfs.ext4 /dev/VolGroup/root mount /dev/VolGroup/root /mnt - Write some data, sync and delete it dd if=/dev/zero of=/mnt/data.raw bs=4K count=1M sync rm /mnt/data.raw - Check the RAID device echo check >/sys/block/md0/md/sync_action - After finishing (see /proc/mdstat), check the mismatch_cnt (should be 0): cat /sys/block/md0/md/mismatch_cnt - Trigger the bug fstrim /mnt - Re-Check the RAID device echo check >/sys/block/md0/md/sync_action - After finishing (see /proc/mdstat), check the mismatch_cnt (probably in the range of N*1): cat /sys/block/md0/md/mismatch_cnt After investigating this issue on several machines it *seems* that the first drive does the trim correctly while the second one goes wild. At least the number and severity of errors found by a USB stick live session fsck.ext4 suggests this. To perform the single drive evaluation the RAID10 was started using a single drive at once: mdadm --assemble /dev/md127 /dev/nvme0n1p2 mdadm --run /dev/md127 fsck.ext4 -n -f /dev/VolGroup/root vgchange -a n /dev/VolGroup mdadm --stop /dev/md127 mdadm --assemble /dev/md127 /dev/nvme1n1p2 mdadm --run /dev/md127 fsck.ext4 -n -f /dev/VolGroup/root When starting these fscks without -n, on the first device it seems the directory structure is OK while on the second device there is only the lost+found folder left. Side-note: Another machine using HWE
[Kernel-packages] [Bug 1896578] Re: raid10: Block discard is very slow, causing severe delays for mkfs and fstrim operations
Hi Evan, The kernel team have built all of the kernels for this SRU cycle, and have placed them into -proposed for verification. We now need to do some thorough testing and make sure that Raid10 arrays function with good performance, ensure data integrity and make sure we won't be introducing any regressions when these kernels are released in two weeks time. I would really appreciate it if you could help test and verify these kernels function as intended. Instructions to Install: 1) cat << EOF | sudo tee /etc/apt/sources.list.d/ubuntu-$(lsb_release -cs)-proposed.list # Enable Ubuntu proposed archive deb http://archive.ubuntu.com/ubuntu/ $(lsb_release -cs)-proposed main universe EOF 2) sudo apt update For 21.04 / Hirsute: 3) sudo apt install linux-image-5.11.0-20-generic linux-modules-5.11.0-20-generic \ linux-modules-extra-5.11.0-20-generic linux-headers-5.11.0-20-generic For 20.10 / Groovy: 3) sudo apt install linux-image-5.8.0-56-generic linux-modules-5.8.0-56-generic \ linux-modules-extra-5.8.0-56-generic linux-headers-5.8.0-56-generic For 20.04 / Focal: 3) sudo apt install linux-image-5.4.0-75-generic linux-modules-5.4.0-75-generic \ linux-modules-extra-5.4.0-75-generic linux-headers-5.4.0-75-generic For 18.04 / Bionic: For the 5.4 Bionic HWE Kernel: 3) sudo apt install linux-image-5.4.0-75-generic linux-modules-5.4.0-75-generic \ linux-modules-extra-5.4.0-75-generic linux-headers-5.4.0-75-generic For the 4.15 Bionic GA Kernel: 3) sudo apt install linux-image-4.15.0-145-generic linux-modules-4.15.0-145-generic \ linux-modules-extra-4.15.0-145-generic linux-headers-4.15.0-145-generic 4) sudo reboot 5) uname -rv You may need to modify your grub configuration to boot the correct kernel. If you need help, read these instructions: https://paste.ubuntu.com/p/XrTzWPPnWJ/ I am running the -proposed kernel on my cloud instance with my /home directory on a Raid10 array made up of 4x NVMe devices, and things are looking okay. I will be performing my detailed regression testing against these kernels tomorrow, and I will write back with the results then. Please help test these kernels in -proposed, and let me know how they go. Thanks, Matthew -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1896578 Title: raid10: Block discard is very slow, causing severe delays for mkfs and fstrim operations Status in linux package in Ubuntu: In Progress 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 Status in linux source package in Hirsute: Fix Committed Bug description: BugLink: https://bugs.launchpad.net/bugs/1896578 [Impact] Block discard is very slow on Raid10, which causes common use cases which invoke block discard, such as mkfs and fstrim operations, to take a very long time. For example, on a i3.8xlarge instance on AWS, which has 4x 1.9TB NVMe devices which support block discard, a mkfs.xfs operation on Raid 10 takes between 8 to 11 minutes, where the same mkfs.xfs operation on Raid 0, takes 4 seconds. The bigger the devices, the longer it takes. The cause is that Raid10 currently uses a 512k chunk size, and uses this for the discard_max_bytes value. If we need to discard 1.9TB, the kernel splits the request into millions of 512k bio requests, even if the underlying device supports larger requests. For example, the NVMe devices on i3.8xlarge support 2.2TB of discard at once: $ cat /sys/block/nvme0n1/queue/discard_max_bytes 2199023255040 $ cat /sys/block/nvme0n1/queue/discard_max_hw_bytes 2199023255040 Where the Raid10 md device only supports 512k: $ cat /sys/block/md0/queue/discard_max_bytes 524288 $ cat /sys/block/md0/queue/discard_max_hw_bytes 524288 If we perform a mkfs.xfs operation on the /dev/md array, it takes over 11 minutes and if we examine the stack, it is stuck in blkdev_issue_discard() $ sudo cat /proc/1626/stack [<0>] wait_barrier+0x14c/0x230 [raid10] [<0>] regular_request_wait+0x39/0x150 [raid10] [<0>] raid10_write_request+0x11e/0x850 [raid10] [<0>] raid10_make_request+0xd7/0x150 [raid10] [<0>] md_handle_request+0x123/0x1a0 [<0>] md_submit_bio+0xda/0x120 [<0>] __submit_bio_noacct+0xde/0x320 [<0>] submit_bio_noacct+0x4d/0x90 [<0>] submit_bio+0x4f/0x1b0 [<0>] __blkdev_issue_discard+0x154/0x290 [<0>] blkdev_issue_discard+0x5d/0xc0 [<0>] blk_ioctl_discard+0xc4/0x110 [<0>] blkdev_common_ioctl+0x56c/0x840 [<0>] blkdev_ioctl+0xeb/0x270 [<0>] block_ioctl+0x3d/0x50 [<0>] __x64_sys_ioctl+0x91/0xc0 [<0>] do_syscall_64+0x38/0x90 [<0>] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [Fix] Xiao Ni has developed a patchset which resolves the block discard performance problems. These commits have now landed in 5.13-rc1. commit
[Kernel-packages] [Bug 1930868] Re: Package firmware-sof-signed (not installed) failed to install/upgrade: trying to overwrite '/lib/firmware/intel/sof/sof-apl.ri', which is also in package linux-firm
The current firmware-sof version 1.6.1-2 can't replace the sof-firmware in our linux-firmware package. At least an important firmware file is missing in the firmware-sof. I have wrote an email to debian maintainer, he told me he is planning a higher version (1.7), once the 1.7 is ready, we could remove the sof- firmware in the linux-firmware and use the firmware-sof package. Below is the reply from the maintainer: Hi Hui, I hadn't realised that's how it worked So I had prepared a 1.7 version a month ago: https://salsa.debian.org/mpearson/firmware-sof/-/commit/fdce28e87c495ab69c1cdfaaff19bc7aff70af5f But I wasn't able to get this uploaded as there was a freeze on so the debian maintainer who has been helping me wouldn't take it. I'll see if that's possible now (and likely have to update to the latest...) Mark -- 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/1930868 Title: Package firmware-sof-signed (not installed) failed to install/upgrade: trying to overwrite '/lib/firmware/intel/sof/sof-apl.ri', which is also in package linux-firmware 1.197 Status in firmware-sof package in Ubuntu: New Status in linux-firmware package in Ubuntu: New Bug description: (Reading database ... 220533 files and directories currently installed.) Preparing to unpack .../firmware-sof-signed_1.6.1-2_all.deb ... Unpacking firmware-sof-signed (1.6.1-2) ... dpkg: error processing archive /var/cache/apt/archives/firmware-sof-signed_1.6.1-2_all.deb (--unpack): trying to overwrite '/lib/firmware/intel/sof/sof-apl.ri', which is also in package linux-firmware 1.197 Errors were encountered while processing: /var/cache/apt/archives/firmware-sof-signed_1.6.1-2_all.deb Is there a work around? ProblemType: Package DistroRelease: Ubuntu 21.04 Package: firmware-sof-signed (not installed) ProcVersionSignature: Ubuntu 5.11.0-18.19-generic 5.11.17 Uname: Linux 5.11.0-18-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu65.1 AptOrdering: firmware-sof-signed:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: pass Date: Fri Jun 4 17:22:54 2021 DpkgTerminalLog: Preparing to unpack .../firmware-sof-signed_1.6.1-2_all.deb ... Unpacking firmware-sof-signed (1.6.1-2) ... dpkg: error processing archive /var/cache/apt/archives/firmware-sof-signed_1.6.1-2_all.deb (--unpack): trying to overwrite '/lib/firmware/intel/sof/sof-apl.ri', which is also in package linux-firmware 1.197 DuplicateSignature: package:firmware-sof-signed:(not installed) Unpacking firmware-sof-signed (1.6.1-2) ... dpkg: error processing archive /var/cache/apt/archives/firmware-sof-signed_1.6.1-2_all.deb (--unpack): trying to overwrite '/lib/firmware/intel/sof/sof-apl.ri', which is also in package linux-firmware 1.197 ErrorMessage: trying to overwrite '/lib/firmware/intel/sof/sof-apl.ri', which is also in package linux-firmware 1.197 InstallationDate: Installed on 2021-06-02 (2 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) Python3Details: /usr/bin/python3.9, Python 3.9.5, python3-minimal, 3.9.4-1 PythonDetails: N/A RelatedPackageVersions: dpkg 1.20.9ubuntu1 apt 2.2.3 SourcePackage: firmware-sof Title: package firmware-sof-signed (not installed) failed to install/upgrade: trying to overwrite '/lib/firmware/intel/sof/sof-apl.ri', which is also in package linux-firmware 1.197 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firmware-sof/+bug/1930868/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1930188] Re: Acer Aspire 5 sound driver issues
The kernel patch: https://mailman.alsa-project.org/pipermail/alsa-devel/2021-June/185823.html The PA MR: https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/577 Once they are accepted by upstream, will backport them to ubuntu. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1930188 Title: Acer Aspire 5 sound driver issues Status in linux package in Ubuntu: New Bug description: Hello, There seems to be lots of issues in sound driver for Acer Aspire A515-56-57XR with ALC255. I will list all of them below and what I have tried so far. 1. Headphones appears always plugged in even if they are physically not 2. When actually plugging in headset/earphones it does not auto switch from speakers/internal mic to headphones/headset microphone automatically and vice versa, have to manually switch everytime. 3. External headset/earphones microphone won't work at all After, logs of trial and error I have found a temporary fix. This seems to use legacy intel drivers which solves all 3 issues mentioned above but the internal/dmic mic is completely gone (which seems intentional when using this). Both depreciated dmic_detect and dsp_driver works, I have been using dsp_driver for now as I need external microphone at any cost. End of /etc/modprobe.d/alsa-base.conf # Headset mic fix options snd-hda-intel dmic_detect=0 / options snd-intel-dspcfg dsp_driver=1 options snd-hda-intel model=alc255-acer In another thread similar to this I got some support and at least fixed the external microphone without using the alsa-base.conf change in custom modified kernel. I will attach it here. Now, hoping to fix other issues as well slowly like making headphones unplugged when physically removing as well as auto switching like the legacy driver one. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1930188/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1905157] Re: package zfsutils-linux 0.8.3-1ubuntu12.4 failed to install/upgrade: installed zfsutils-linux package post-installation script subprocess returned error exit status
[Expired for zfs-linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: zfs-linux (Ubuntu) Status: Incomplete => Expired -- 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/1905157 Title: package zfsutils-linux 0.8.3-1ubuntu12.4 failed to install/upgrade: installed zfsutils-linux package post-installation script subprocess returned error exit status 1 Status in zfs-linux package in Ubuntu: Expired Bug description: When I try to update zfsutils-linux, the upgrade process tries to mount all zfs file systems but since my root / is on zfs it fails with: nov 22 08:21:28 Home systemd[1]: Starting Mount ZFS filesystems... nov 22 08:21:28 Home zfs[286979]: cannot mount '/': directory is not empty nov 22 08:21:28 Home systemd[1]: zfs-mount.service: Main process exited, code=exited, status=1/FAILURE nov 22 08:21:28 Home systemd[1]: zfs-mount.service: Failed with result 'exit-code'. nov 22 08:21:28 Home systemd[1]: Failed to start Mount ZFS filesystems. As a consequence, the upgrade process fails. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: zfsutils-linux 0.8.3-1ubuntu12.4 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.12 AptOrdering: linux-headers-5.4.0-52-generic:amd64: Remove linux-headers-5.4.0-52:amd64: Remove NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: skip Date: Sun Nov 22 06:41:54 2020 ErrorMessage: installed zfsutils-linux package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2020-07-08 (136 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.1 SourcePackage: zfs-linux Title: package zfsutils-linux 0.8.3-1ubuntu12.4 failed to install/upgrade: installed zfsutils-linux package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.default.zfs: 2020-08-05T10:29:12.101838 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1905157/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta-raspi-5.4/5.4.0.1037.39)
All autopkgtests for the newly accepted linux-meta-raspi-5.4 (5.4.0.1037.39) for bionic have finished running. The following regressions have been reported in tests triggered by the package: fwts/unknown (arm64) systemd/237-3ubuntu10.47 (arm64) lxc/3.0.3-0ubuntu1~18.04.1 (arm64) dpdk/unknown (arm64) zfs-linux/0.7.5-1ubuntu16.11 (arm64) adv-17v35x/unknown (arm64) bbswitch/0.8-4ubuntu1 (arm64) glibc/unknown (arm64) xtables-addons/unknown (arm64) linux-raspi-5.4/unknown (arm64) acpi-call/1.1.0-4 (arm64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/bionic/update_excuses.html#linux-meta-raspi-5.4 [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1786013 Title: Packaging resync Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-edge package in Ubuntu: Confirmed Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Invalid Status in linux-azure-edge source package in Precise: Invalid Status in linux source package in Trusty: Fix Released Status in linux-azure source package in Trusty: Fix Released Status in linux-azure-edge source package in Trusty: Invalid Status in linux source package in Xenial: Fix Released Status in linux-azure source package in Xenial: Fix Released Status in linux-azure-edge source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-azure source package in Bionic: Fix Released Status in linux-azure-edge source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux-azure source package in Cosmic: Fix Released Status in linux-azure-edge source package in Cosmic: Confirmed Status in linux source package in Disco: Fix Released Status in linux-azure source package in Disco: Fix Released Status in linux-azure-edge source package in Disco: Won't Fix Bug description: Ongoing packing resyncs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1890772] Re: No signal on 4K 60Hz DisplayPort monitor by default, until "max bpc" is lowered to 8
This should also fix the problem for some people in Wayland sessions: https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1834 It is in mutter release 40.1 and future release 3.38.5. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1890772 Title: No signal on 4K 60Hz DisplayPort monitor by default, until "max bpc" is lowered to 8 Status in gnome-control-center: Unknown Status in HWE Next: New Status in Linux: Unknown Status in Mutter: Unknown Status in OEM Priority Project: New Status in X.Org X server: Unknown Status in linux package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Won't Fix Status in xorg-server package in Ubuntu: Invalid Bug description: The bug is originated from, https://bugs.launchpad.net/somerville/+bug/1887915/ https://bugs.launchpad.net/somerville/+bug/1886778 It has some problem when user connect to external 4K monitor with refresh rate 60. The problem can be solved by lower the bpc, or lower the refresh rate. `xrandr --output DP-3 --set "max bpc" 8` Would like to open this bug to open discussion for enhancing user experience. existed upstream bug: - https://gitlab.freedesktop.org/drm/intel/-/issues/1890 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME DistUpgraded: Fresh install DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-focal-amd64-20200502-85+fossa-samwell-tgl+X42 DistroCodename: focal DistroRelease: Ubuntu 20.04 DistroVariant: ubuntu DkmsStatus: nvidia, 440.100, 5.6.0-1021-oem, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:09fc] Subsystem: Dell GP107M [GeForce MX350] [1028:09fc] InstallationDate: Installed on 2020-08-07 (0 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 Package: xorg 1:7.7+19ubuntu14 [origin: unknown] PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.6.0-1021-oem root=UUID=41be2253-410a-4ef7-a096-4193a58efdbd ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.6.0-1021.21-oem 5.6.19 Tags: third-party-packages focal ubuntu Uname: Linux 5.6.0-1021-oem x86_64 UnreportableReason: This is not an official Ubuntu package. Please remove any third party package and try again. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1890772/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1836858] Re: Display flickers (monitor loses signal briefly) during "flickerfree" boot, while showing the BIOS logo on a black background
Yeah the problem seems to be getting worse in recent Ubuntu releases and is more obvious on more laptops. That's good for testing at least. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1836858 Title: Display flickers (monitor loses signal briefly) during "flickerfree" boot, while showing the BIOS logo on a black background Status in Plymouth: Unknown Status in linux package in Ubuntu: Confirmed Status in plymouth package in Ubuntu: Confirmed Bug description: I am trying flickerfree boot in 19.10 [1], but find it actually flickers part way through: 1. BIOS logo on a black background. 2. Display mode resets, no image on a black background briefly. 3. BIOS logo on a black background. The flicker occurs seemingly during kernel startup since my peripherals are lit up before the problem occurs. Suspecting this might be related to FB handover: [2.751028] fb0: switching to inteldrmfb from EFI VGA I tried disabling that with a big hammer: i915.modeset=0 so it stays in efifb, and that works -- no more flickering, providing I don't let i915 take over the framebuffer. [1] https://discourse.ubuntu.com/t/testing-flickerfree-boot/11854 ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.2.0-8-generic 5.2.0-8.9 ProcVersionSignature: Ubuntu 5.2.0-8.9-generic 5.2.0 Uname: Linux 5.2.0-8-generic x86_64 ApportVersion: 2.20.11-0ubuntu5 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Wed Jul 17 16:34:36 2019 InstallationDate: Installed on 2019-05-02 (76 days ago) InstallationMedia: Ubuntu 19.10 "Eoan EANIMAL" - Alpha amd64 (20190501) MachineType: LENOVO 10M7CTO1WW ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.2.0-8-generic root=UUID=9bfb5f01-bdd4-4854-bfce-1c28e2f2f3bc ro quiet splash i915.fastboot=1 vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.2.0-8-generic N/A linux-backports-modules-5.2.0-8-generic N/A linux-firmware 1.180 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/06/2018 dmi.bios.vendor: LENOVO dmi.bios.version: M16KT47A dmi.board.name: 3102 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN 3259627060530 dmi.chassis.type: 3 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrM16KT47A:bd02/06/2018:svnLENOVO:pn10M7CTO1WW:pvrThinkCentreM710s:rvnLENOVO:rn3102:rvrSDK0J40709WIN3259627060530:cvnLENOVO:ct3:cvrNone: dmi.product.family: ThinkCentre M710s dmi.product.name: 10M7CTO1WW dmi.product.sku: LENOVO_MT_10M7_BU_Think_FM_ThinkCentre M710s dmi.product.version: ThinkCentre M710s dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/plymouth/+bug/1836858/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1883840] Re: Double free in DCCP module causing kernel panic
Hello Hadar, I'm sorry for the trouble.
These have been fixed:
https://ubuntu.com/security/notices/USN-4577-1
https://ubuntu.com/security/notices/USN-4576-1
https://ubuntu.com/security/notices/USN-4578-1
https://ubuntu.com/security/notices/USN-4579-1
https://ubuntu.com/security/notices/USN-4580-1
This page is regenerated by a cronjob, it should be fixed eventually:
https://ubuntu.com/security/CVE-2020-16119
Thanks
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1883840
Title:
Double free in DCCP module causing kernel panic
Status in linux package in Ubuntu:
Fix Released
Bug description:
The problem is when the sock object gets cloned via
dccp_create_openreq_child(),
it gives all its attributes to the child sock object, and no reference counter
is taken for the object dccps_hc_tx_ccid.
If one of the sock objects (the parent or the cahild) is closes or
disconnected,
it frees the target objects dccps_hc_tx_ccid and provides us a dagling
pointer in the other sock object.
This causes an exploitable double free for an object contains function
pointers.
We can free dccps_hc_tx_ccid by calling connect(AF_UNSPEC),then spray the
heap with other allocations,
then call close() we'll potentially have a RIP control.
This chunk of code is the responsible of freeing dccps_hc_tx_ccid, if called
again it will call
ccid_hc_tx_exit() from a freed object
void ccid_hc_tx_delete(struct ccid *ccid, struct sock *sk)
{
if (ccid != NULL) {
if (ccid->ccid_ops->ccid_hc_tx_exit != NULL)
ccid->ccid_ops->ccid_hc_tx_exit(sk); // <-- Calling a function
pointer
kmem_cache_free(ccid->ccid_ops->ccid_hc_tx_slab, ccid);
}
}
disassembly :
(gdb) disas ccid_hc_tx_delete
Dump of assembler code for function ccid_hc_tx_delete:
0x81a7a3a0 <+0>: test rdi,rdi
0x81a7a3a3 <+3>: je 0x81a7a3cd
0x81a7a3a5 <+5>: push rbx
0x81a7a3a6 <+6>: movrbx,rdi
0x81a7a3a9 <+9>: movrdi,rsi
0x81a7a3ac <+12>:movrax,QWORD PTR [rbx]
0x81a7a3af <+15>:movrdx,QWORD PTR [rax+0x80]<—
rax points to a freed object
0x81a7a3b6 <+22>:test rdx,rdx
0x81a7a3b9 <+25>:je 0x81a7a3c0
0x81a7a3bb <+27>:call rdx // <-- arbitrary call
0x81a7a3bd <+29>:movrax,QWORD PTR [rbx]
0x81a7a3c0 <+32>:movrsi,rbx
0x81a7a3c3 <+35>:movrdi,QWORD PTR [rax+0x18]
0x81a7a3c7 <+39>:poprbx
0x81a7a3c8 <+40>:jmp0x811fb980
0x81a7a3cd <+45>:repz ret
End of assembler dump.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1883840/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1930422] Re: thermald_1.9.1-1ubuntu0.4_amd64 breaks system
I wish fan control worked. I release v2.4.6 with the changes. This is in master branch with tag v2.4.6. There are three commits on top of v2.4.5 to address this issue. Please try. -- 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/1930422 Title: thermald_1.9.1-1ubuntu0.4_amd64 breaks system Status in thermald package in Ubuntu: New Bug description: cpu runs at 100c fan at 3000rpm when in heavy use previous version was ok re: https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/1913186 lshw -short is: H/W path Device Class Description == system XPS 8940 (09C5) /0 bus0KV3RP /0/0memory 64KiB BIOS /0/9memory 16GiB System Memory /0/9/0 memory 8GiB DIMM DDR4 Synchronous 32 /0/9/1 memory 8GiB DIMM DDR4 Synchronous 32 /0/9/2 memory Project-Id-Version: lshwRepor /0/9/3 memory Project-Id-Version: lshwRepor /0/35 memory 512KiB L1 cache /0/36 memory 2MiB L2 cache /0/37 memory 16MiB L3 cache /0/38 processor Intel(R) Core(TM) i7-10700 CP /0/100 bridge Intel Corporation /0/100/1bridge Xeon E3-1200 v5/E3-1500 v5/6t /0/100/1/0 displayTU106 [GeForce RTX 2060 Rev. /0/100/1/0.1multimedia TU106 High Definition Audio C /0/100/1/0.2busTU106 USB 3.1 Host Controller /0/100/1/0.2/0 usb3 busxHCI Host Controller /0/100/1/0.2/1 usb4 busxHCI Host Controller /0/100/1/0.3busTU106 USB Type-C UCSI Control /0/100/2displayIntel Corporation /0/100/4genericXeon E3-1200 v5/E3-1500 v5/6t /0/100/8genericXeon E3-1200 v5/v6 / E3-1500 /0/100/12 genericComet Lake PCH Thermal Contro /0/100/14 busComet Lake USB 3.1 xHCI Host /0/100/14/0usb1 busxHCI Host Controller /0/100/14/0/4 enx0c5b8f279a64 communication HUAWEI_MOBILE /0/100/14/0/5 input Dell MS116 USB Optical Mouse /0/100/14/0/6 input Dell KB216 Wired Keyboard /0/100/14/0/b genericUSB2.0-CRW /0/100/14/0/c genericUB91C /0/100/14/0/e communication Bluetooth wireless interface /0/100/14/1usb2 busxHCI Host Controller /0/100/14.2 memory RAM memory /0/100/14.3wlo1 networkWi-Fi 6 AX201 /0/100/15 busComet Lake PCH Serial IO I2C /0/100/16 communication Comet Lake HECI Controller /0/100/17 storageIntel Corporation /0/100/1b bridge Comet Lake PCI Express Root P /0/100/1b/0 storageSamsung Electronics Co Ltd /0/100/1b/0/0 /dev/nvme0 storagePM991 NVMe Samsung 512GB /0/100/1b/0/0/1/dev/nvme0n1 disk 512GB NVMe namespace /0/100/1b/0/0/1/1 volume 149MiB Windows FAT volume /0/100/1b/0/0/1/2 /dev/nvme0n1p2 volume 127MiB reserved partition /0/100/1b/0/0/1/3 /dev/nvme0n1p3 volume 214GiB Windows NTFS volume /0/100/1b/0/0/1/4 /dev/nvme0n1p4 volume 989MiB Windows NTFS volume /0/100/1b/0/0/1/5 /dev/nvme0n1p5 volume 16GiB Windows NTFS volume /0/100/1b/0/0/1/6 /dev/nvme0n1p6 volume 1417MiB Windows NTFS volume /0/100/1b/0/0/1/7 /dev/nvme0n1p7 volume 243GiB EXT4 volume /0/100/1c bridge Intel Corporation /0/100/1c/0enp3s0 networkRealtek Semiconductor Co., Lt /0/100/1f bridge Intel Corporation /0/100/1f.3 multimedia Comet Lake PCH cAVS /0/100/1f.4 busComet Lake PCH SMBus Controll /0/100/1f.5 busComet Lake PCH SPI Controller /0/1
[Kernel-packages] [Bug 1928950] Re: ThinkPad X250 boot failure with kernel 5.4.0-73-generic (Linux Mint 19.3)
Still boot failure with kernel 5.4.0.75-generic. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1928950 Title: ThinkPad X250 boot failure with kernel 5.4.0-73-generic (Linux Mint 19.3) Status in linux package in Ubuntu: Incomplete Bug description: Bug/Regression introduced between 5.4.0-73 and 5.4.0-72 (-72 and all previous kernels installed by Mint 19.3 had no problems). Happens whether docked or undocked. Might relate to Bug #1928530. System tells to do a journalctl -xb, but I couldn't spot if there's something relevant. I'll collect the logs twice to help find the difference (one from -73 panic shell and one from -72 normally booted). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1928950/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
Re: [Kernel-packages] [Bug 1930422] Re: thermald_1.9.1-1ubuntu0.4_amd64 breaks system
yes desktop/tower pc with ubuntu 20.04 lts desktop cooling_device0-4 (out of 21) type = fan all five cur_state were set at 0 changed them to various values between 0-1 made no difference to fans On 07/06/2021 20:36, Srinivas Pandruvada wrote: > Thanks for the comment. > I would like to know something more about this system? > - Is this a desktop? > - Do you see any entry where /sys/class/thermal/cooling_device*/type = fan? > If you see can you control fan speed via > /sys/class/thermal/cooling_device*/cur_state > > I will cleanup the change and upload one final version before I merge > and release. > -- 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/1930422 Title: thermald_1.9.1-1ubuntu0.4_amd64 breaks system Status in thermald package in Ubuntu: New Bug description: cpu runs at 100c fan at 3000rpm when in heavy use previous version was ok re: https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/1913186 lshw -short is: H/W path Device Class Description == system XPS 8940 (09C5) /0 bus0KV3RP /0/0memory 64KiB BIOS /0/9memory 16GiB System Memory /0/9/0 memory 8GiB DIMM DDR4 Synchronous 32 /0/9/1 memory 8GiB DIMM DDR4 Synchronous 32 /0/9/2 memory Project-Id-Version: lshwRepor /0/9/3 memory Project-Id-Version: lshwRepor /0/35 memory 512KiB L1 cache /0/36 memory 2MiB L2 cache /0/37 memory 16MiB L3 cache /0/38 processor Intel(R) Core(TM) i7-10700 CP /0/100 bridge Intel Corporation /0/100/1bridge Xeon E3-1200 v5/E3-1500 v5/6t /0/100/1/0 displayTU106 [GeForce RTX 2060 Rev. /0/100/1/0.1multimedia TU106 High Definition Audio C /0/100/1/0.2busTU106 USB 3.1 Host Controller /0/100/1/0.2/0 usb3 busxHCI Host Controller /0/100/1/0.2/1 usb4 busxHCI Host Controller /0/100/1/0.3busTU106 USB Type-C UCSI Control /0/100/2displayIntel Corporation /0/100/4genericXeon E3-1200 v5/E3-1500 v5/6t /0/100/8genericXeon E3-1200 v5/v6 / E3-1500 /0/100/12 genericComet Lake PCH Thermal Contro /0/100/14 busComet Lake USB 3.1 xHCI Host /0/100/14/0usb1 busxHCI Host Controller /0/100/14/0/4 enx0c5b8f279a64 communication HUAWEI_MOBILE /0/100/14/0/5 input Dell MS116 USB Optical Mouse /0/100/14/0/6 input Dell KB216 Wired Keyboard /0/100/14/0/b genericUSB2.0-CRW /0/100/14/0/c genericUB91C /0/100/14/0/e communication Bluetooth wireless interface /0/100/14/1usb2 busxHCI Host Controller /0/100/14.2 memory RAM memory /0/100/14.3wlo1 networkWi-Fi 6 AX201 /0/100/15 busComet Lake PCH Serial IO I2C /0/100/16 communication Comet Lake HECI Controller /0/100/17 storageIntel Corporation /0/100/1b bridge Comet Lake PCI Express Root P /0/100/1b/0 storageSamsung Electronics Co Ltd /0/100/1b/0/0 /dev/nvme0 storagePM991 NVMe Samsung 512GB /0/100/1b/0/0/1/dev/nvme0n1 disk 512GB NVMe namespace /0/100/1b/0/0/1/1 volume 149MiB Windows FAT volume /0/100/1b/0/0/1/2 /dev/nvme0n1p2 volume 127MiB reserved partition /0/100/1b/0/0/1/3 /dev/nvme0n1p3 volume 214GiB Windows NTFS volume /0/100/1b/0/0/1/4 /dev/nvme0n1p4 volume 989MiB Windows NTFS volume /0/100/1b/0/0/1/5 /dev/nvme0n1p5 volume 16GiB Windows NTFS volume /0/100/1b/0/0/1/6 /dev/nvme0n1p6 volume 1417MiB Windows NTFS volume /0/100/1b/0/0/1/7 /dev/nvme0n1p7 volume 243GiB EXT4 volume /0/100/1c bridge
[Kernel-packages] [Bug 1931166] Re: Focal update: v5.4.124 upstream stable release
** Description changed: + SRU Justification - SRU Justification + Impact: + The upstream process for stable tree updates is quite similar + in scope to the Ubuntu SRU process, e.g., each patch has to + demonstrably fix a bug, and each patch is vetted by upstream + by originating either directly from a mainline/stable Linux tree or + a minimally backported form of that patch. The following upstream + stable patches should be included in the Ubuntu kernel: - Impact: -The upstream process for stable tree updates is quite similar -in scope to the Ubuntu SRU process, e.g., each patch has to -demonstrably fix a bug, and each patch is vetted by upstream -by originating either directly from a mainline/stable Linux tree or -a minimally backported form of that patch. The following upstream -stable patches should be included in the Ubuntu kernel: + v5.4.124 upstream stable release + from git://git.kernel.org/ -v5.4.124 upstream stable release -from git://git.kernel.org/ + ALSA: hda/realtek: Headphone volume is controlled by Front mixer + ALSA: usb-audio: scarlett2: Fix device hang with ehci-pci + ALSA: usb-audio: scarlett2: Improve driver startup messages + cifs: set server->cipher_type to AES-128-CCM for SMB3.0 + NFSv4: Fix a NULL pointer dereference in pnfs_mark_matching_lsegs_return() + iommu/vt-d: Fix sysfs leak in alloc_iommu() + perf intel-pt: Fix sample instruction bytes + perf intel-pt: Fix transaction abort handling + perf scripts python: exported-sql-viewer.py: Fix copy to clipboard from Top Calls by elapsed Time report + perf scripts python: exported-sql-viewer.py: Fix Array TypeError + perf scripts python: exported-sql-viewer.py: Fix warning display + proc: Check /proc/$pid/attr/ writes against file opener + net: hso: fix control-request directions + ath10k: Validate first subframe of A-MSDU before processing the list + dm snapshot: properly fix a crash when an origin has no snapshots + drm/amdgpu/vcn1: add cancel_delayed_work_sync before power gate + drm/amdgpu/vcn2.0: add cancel_delayed_work_sync before power gate + drm/amdgpu/vcn2.5: add cancel_delayed_work_sync before power gate + selftests/gpio: Use TEST_GEN_PROGS_EXTENDED + selftests/gpio: Move include of lib.mk up + selftests/gpio: Fix build when source tree is read only + kgdb: fix gcc-11 warnings harder + Documentation: seccomp: Fix user notification documentation + serial: core: fix suspicious security_locked_down() call + misc/uss720: fix memory leak in uss720_probe + thunderbolt: dma_port: Fix NVM read buffer bounds and offset issue + mei: request autosuspend after sending rx flow control + staging: iio: cdc: ad7746: avoid overwrite of num_channels + iio: gyro: fxas21002c: balance runtime power in error path + iio: adc: ad7768-1: Fix too small buffer passed to iio_push_to_buffers_with_timestamp() + iio: adc: ad7124: Fix missbalanced regulator enable / disable on error. + iio: adc: ad7124: Fix potential overflow due to non sequential channel numbers + iio: adc: ad7793: Add missing error code in ad7793_setup() + serial: 8250_pci: Add support for new HPE serial device + serial: 8250_pci: handle FL_NOIRQ board flag + USB: trancevibrator: fix control-request direction + USB: usbfs: Don't WARN about excessively large memory allocations + serial: tegra: Fix a mask operation that is always true + serial: sh-sci: Fix off-by-one error in FIFO threshold register setting + serial: rp2: use 'request_firmware' instead of 'request_firmware_nowait' + USB: serial: ti_usb_3410_5052: add startech.com device id + USB: serial: option: add Telit LE910-S1 compositions 0x7010, 0x7011 + USB: serial: ftdi_sio: add IDs for IDS GmbH Products + USB: serial: pl2303: add device id for ADLINK ND-6530 GC + thermal/drivers/intel: Initialize RW trip to THERMAL_TEMP_INVALID + usb: dwc3: gadget: Properly track pending and queued SG + usb: gadget: udc: renesas_usb3: Fix a race in usb3_start_pipen() + net: usb: fix memory leak in smsc75xx_bind + spi: spi-geni-qcom: Fix use-after-free on unbind + Bluetooth: cmtp: fix file refcount when cmtp_attach_device fails + fs/nfs: Use fatal_signal_pending instead of signal_pending + NFS: fix an incorrect limit in filelayout_decode_layout() + NFS: Fix an Oopsable condition in __nfs_pageio_add_request() + NFS: Don't corrupt the value of pg_bytes_written in nfs_do_recoalesce() + NFSv4: Fix v4.0/v4.1 SEEK_DATA return -ENOTSUPP when set NFS_V4_2 config + drm/meson: fix shutdown crash when component not probed + net/mlx5e: Fix multipath lag activation + net/mlx5e: Fix nullptr in add_vlan_push_action() + net/mlx4: Fix EEPROM dump support + Revert "net:tipc: Fix a double free in tipc_sk_mcast_rcv" + tipc: wait and exit until all work queues are done + tipc: skb_linearize the head skb when reassembling msgs + spi: spi-fsl-dspi: Fix a resource leak in an error handling path + net: dsa: mt7530: fix VLAN traffic
[Kernel-packages] [Bug 1931166] [NEW] Focal update: v5.4.124 upstream stable release
Public bug reported: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v5.4.124 upstream stable release from git://git.kernel.org/ ** Affects: linux (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux (Ubuntu Focal) Importance: Medium Assignee: Kamal Mostafa (kamalmostafa) Status: In Progress ** Tags: kernel-stable-tracking-bug ** Changed in: linux (Ubuntu) Status: New => Confirmed ** Tags added: kernel-stable-tracking-bug ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Focal) Status: New => In Progress ** Changed in: linux (Ubuntu Focal) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Focal) Assignee: (unassigned) => Kamal Mostafa (kamalmostafa) ** Changed in: linux (Ubuntu) Status: Confirmed => 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/1931166 Title: Focal update: v5.4.124 upstream stable release Status in linux package in Ubuntu: Invalid Status in linux source package in Focal: In Progress Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v5.4.124 upstream stable release from git://git.kernel.org/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1931166/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1929657] Comment bridged from LTC Bugzilla
--- Comment From mario.alberto.gali...@ibm.com 2021-06-07 16:13 EDT--- Just executed netplan try and netplan apply and take snapshot of journalctl. It is attached now! - The configuration has not being touched for long time - Correct is the only one presenting this problem - Correct all of the host has RoCe v2.X installed Could you explain what do you mean with setup the vLan using the IP commands? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1929657 Title: [Ubuntu 20.4.2] vLan not getting static IP assigned (on s390x) Status in Ubuntu on IBM z Systems: Incomplete Status in linux package in Ubuntu: New Status in netplan.io package in Ubuntu: New Bug description: ---Problem Description--- Doing vLAN configuration one of the vLANs is not getting static IP assigned when the rest are workin without problems Contact Information = Mario Alvarado/mario.alberto.gali...@ibm.com ---uname output--- Linux ilabg13.tuc.stglabs.ibm.com 5.4.0-73-generic #82-Ubuntu SMP Wed Apr 14 17:29:32 UTC 2021 s390x s390x s390x GNU/Linux Machine Type = z15 ---Debugger--- A debugger is not configured ---Steps to Reproduce--- 1)Configure the netplan file as follow: root@ilabg13:~# cat /etc/netplan/01-iscsi-config.yaml # This is the network config written by 'subiquity' network: ethernets: encdb0: addresses: - 11.111.114.213/22 macaddress: 02:76:54:00:00:03 encdc0: addresses: - 11.111.112.213/22 macaddress: 02:76:54:00:00:04 enP50s3832 : addresses: - 11.111.112.214/22 enP53p0s0: addresses: - 11.111.112.215/22 vlans: encdb0.160: id: 160 link: encdb0 mtu: 9000 addresses: - 192.168.160.53/24 encdc0.150: id: 150 link: encdc0 mtu: 9000 addresses: - 192.168.150.53/24 enP50s3832.170: id: 170 link: enP50s3832 mtu: 9000 addresses: - 192.168.170.53/24 enP53p0s0.171: id: 171 link: enP53p0s0 mtu: 9000 addresses: - 192.168.171.53/24 version: 2 2)run net plan apply: root@ilabg13:~# netplan --debug apply ** (generate:59965): DEBUG: 14:55:15.046: Processing input file /etc/netplan/00-installer-config.yaml.. ** (generate:59965): DEBUG: 14:55:15.046: starting new processing pass ** (generate:59965): DEBUG: 14:55:15.046: Processing input file /etc/netplan/01-iscsi-config.yaml.. ** (generate:59965): DEBUG: 14:55:15.046: starting new processing pass ** (generate:59965): DEBUG: 14:55:15.046: We have some netdefs, pass them through a final round of validation ** (generate:59965): DEBUG: 14:55:15.046: encdc0: setting default backend to 1 ** (generate:59965): DEBUG: 14:55:15.046: Configuration is valid ** (generate:59965): DEBUG: 14:55:15.046: encdb0: setting default backend to 1 ** (generate:59965): DEBUG: 14:55:15.046: Configuration is valid ** (generate:59965): DEBUG: 14:55:15.046: ence0f: setting default backend to 1 ** (generate:59965): DEBUG: 14:55:15.046: Configuration is valid ** (generate:59965): DEBUG: 14:55:15.046: encdb0.160: setting default backend to 1 ** (generate:59965): DEBUG: 14:55:15.046: Configuration is valid ** (generate:59965): DEBUG: 14:55:15.046: enP50s3832: setting default backend to 1 ** (generate:59965): DEBUG: 14:55:15.046: Configuration is valid ** (generate:59965): DEBUG: 14:55:15.046: enP53p0s0.171: setting default backend to 1 ** (generate:59965): DEBUG: 14:55:15.046: Configuration is valid ** (generate:59965): DEBUG: 14:55:15.046: enP50s3832.170: setting default backend to 1 ** (generate:59965): DEBUG: 14:55:15.046: Configuration is valid ** (generate:59965): DEBUG: 14:55:15.046: enP53p0s0: setting default backend to 1 ** (generate:59965): DEBUG: 14:55:15.046: Configuration is valid ** (generate:59965): DEBUG: 14:55:15.046: encdc0.150: setting default backend to 1 ** (generate:59965): DEBUG: 14:55:15.046: Configuration is valid ** (generate:59965): DEBUG: 14:55:15.047: Generating output files.. ** (generate:59965): DEBUG: 14:55:15.047: openvswitch: definition ence0f is not for us (backend 1) ** (generate:59965): DEBUG: 14:55:15.047: NetworkManager: definition ence0f is not for us (backend 1) ** (generate:59965): DEBUG: 14:55:15.047: openvswitch: definition encdb0 is not for us (backend 1) ** (generate:59965): DEBUG: 14:55:15.047: NetworkManager: definition encdb0 is not for us (backend 1) ** (generate:59965): DEBUG: 14:55:15.047: openvswitch: definition encdc0 is not for us (backend 1) ** (generate:59965): DEBUG: 14:55:15.047: NetworkManager: definition encdc0 is not for us (backend
[Kernel-packages] [Bug 1929657] joutnalctl
--- Comment (attachment only) From mario.alberto.gali...@ibm.com 2021-06-07 16:08 EDT--- ** Attachment added: "joutnalctl" https://bugs.launchpad.net/bugs/1929657/+attachment/5502963/+files/dump-of-journalctl.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1929657 Title: [Ubuntu 20.4.2] vLan not getting static IP assigned (on s390x) Status in Ubuntu on IBM z Systems: Incomplete Status in linux package in Ubuntu: New Status in netplan.io package in Ubuntu: New Bug description: ---Problem Description--- Doing vLAN configuration one of the vLANs is not getting static IP assigned when the rest are workin without problems Contact Information = Mario Alvarado/mario.alberto.gali...@ibm.com ---uname output--- Linux ilabg13.tuc.stglabs.ibm.com 5.4.0-73-generic #82-Ubuntu SMP Wed Apr 14 17:29:32 UTC 2021 s390x s390x s390x GNU/Linux Machine Type = z15 ---Debugger--- A debugger is not configured ---Steps to Reproduce--- 1)Configure the netplan file as follow: root@ilabg13:~# cat /etc/netplan/01-iscsi-config.yaml # This is the network config written by 'subiquity' network: ethernets: encdb0: addresses: - 11.111.114.213/22 macaddress: 02:76:54:00:00:03 encdc0: addresses: - 11.111.112.213/22 macaddress: 02:76:54:00:00:04 enP50s3832 : addresses: - 11.111.112.214/22 enP53p0s0: addresses: - 11.111.112.215/22 vlans: encdb0.160: id: 160 link: encdb0 mtu: 9000 addresses: - 192.168.160.53/24 encdc0.150: id: 150 link: encdc0 mtu: 9000 addresses: - 192.168.150.53/24 enP50s3832.170: id: 170 link: enP50s3832 mtu: 9000 addresses: - 192.168.170.53/24 enP53p0s0.171: id: 171 link: enP53p0s0 mtu: 9000 addresses: - 192.168.171.53/24 version: 2 2)run net plan apply: root@ilabg13:~# netplan --debug apply ** (generate:59965): DEBUG: 14:55:15.046: Processing input file /etc/netplan/00-installer-config.yaml.. ** (generate:59965): DEBUG: 14:55:15.046: starting new processing pass ** (generate:59965): DEBUG: 14:55:15.046: Processing input file /etc/netplan/01-iscsi-config.yaml.. ** (generate:59965): DEBUG: 14:55:15.046: starting new processing pass ** (generate:59965): DEBUG: 14:55:15.046: We have some netdefs, pass them through a final round of validation ** (generate:59965): DEBUG: 14:55:15.046: encdc0: setting default backend to 1 ** (generate:59965): DEBUG: 14:55:15.046: Configuration is valid ** (generate:59965): DEBUG: 14:55:15.046: encdb0: setting default backend to 1 ** (generate:59965): DEBUG: 14:55:15.046: Configuration is valid ** (generate:59965): DEBUG: 14:55:15.046: ence0f: setting default backend to 1 ** (generate:59965): DEBUG: 14:55:15.046: Configuration is valid ** (generate:59965): DEBUG: 14:55:15.046: encdb0.160: setting default backend to 1 ** (generate:59965): DEBUG: 14:55:15.046: Configuration is valid ** (generate:59965): DEBUG: 14:55:15.046: enP50s3832: setting default backend to 1 ** (generate:59965): DEBUG: 14:55:15.046: Configuration is valid ** (generate:59965): DEBUG: 14:55:15.046: enP53p0s0.171: setting default backend to 1 ** (generate:59965): DEBUG: 14:55:15.046: Configuration is valid ** (generate:59965): DEBUG: 14:55:15.046: enP50s3832.170: setting default backend to 1 ** (generate:59965): DEBUG: 14:55:15.046: Configuration is valid ** (generate:59965): DEBUG: 14:55:15.046: enP53p0s0: setting default backend to 1 ** (generate:59965): DEBUG: 14:55:15.046: Configuration is valid ** (generate:59965): DEBUG: 14:55:15.046: encdc0.150: setting default backend to 1 ** (generate:59965): DEBUG: 14:55:15.046: Configuration is valid ** (generate:59965): DEBUG: 14:55:15.047: Generating output files.. ** (generate:59965): DEBUG: 14:55:15.047: openvswitch: definition ence0f is not for us (backend 1) ** (generate:59965): DEBUG: 14:55:15.047: NetworkManager: definition ence0f is not for us (backend 1) ** (generate:59965): DEBUG: 14:55:15.047: openvswitch: definition encdb0 is not for us (backend 1) ** (generate:59965): DEBUG: 14:55:15.047: NetworkManager: definition encdb0 is not for us (backend 1) ** (generate:59965): DEBUG: 14:55:15.047: openvswitch: definition encdc0 is not for us (backend 1) ** (generate:59965): DEBUG: 14:55:15.047: NetworkManager: definition encdc0 is not for us (backend 1) ** (generate:59965): DEBUG: 14:55:15.047: openvswitch: definition enP50s3832 is not for us (backend 1) ** (generate:59965): DEBUG: 14:55:15.047: NetworkManager: definition
[Kernel-packages] [Bug 1930422] Re: thermald_1.9.1-1ubuntu0.4_amd64 breaks system
Thanks for the comment. I would like to know something more about this system? - Is this a desktop? - Do you see any entry where /sys/class/thermal/cooling_device*/type = fan? If you see can you control fan speed via /sys/class/thermal/cooling_device*/cur_state I will cleanup the change and upload one final version before I merge and release. -- 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/1930422 Title: thermald_1.9.1-1ubuntu0.4_amd64 breaks system Status in thermald package in Ubuntu: New Bug description: cpu runs at 100c fan at 3000rpm when in heavy use previous version was ok re: https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/1913186 lshw -short is: H/W path Device Class Description == system XPS 8940 (09C5) /0 bus0KV3RP /0/0memory 64KiB BIOS /0/9memory 16GiB System Memory /0/9/0 memory 8GiB DIMM DDR4 Synchronous 32 /0/9/1 memory 8GiB DIMM DDR4 Synchronous 32 /0/9/2 memory Project-Id-Version: lshwRepor /0/9/3 memory Project-Id-Version: lshwRepor /0/35 memory 512KiB L1 cache /0/36 memory 2MiB L2 cache /0/37 memory 16MiB L3 cache /0/38 processor Intel(R) Core(TM) i7-10700 CP /0/100 bridge Intel Corporation /0/100/1bridge Xeon E3-1200 v5/E3-1500 v5/6t /0/100/1/0 displayTU106 [GeForce RTX 2060 Rev. /0/100/1/0.1multimedia TU106 High Definition Audio C /0/100/1/0.2busTU106 USB 3.1 Host Controller /0/100/1/0.2/0 usb3 busxHCI Host Controller /0/100/1/0.2/1 usb4 busxHCI Host Controller /0/100/1/0.3busTU106 USB Type-C UCSI Control /0/100/2displayIntel Corporation /0/100/4genericXeon E3-1200 v5/E3-1500 v5/6t /0/100/8genericXeon E3-1200 v5/v6 / E3-1500 /0/100/12 genericComet Lake PCH Thermal Contro /0/100/14 busComet Lake USB 3.1 xHCI Host /0/100/14/0usb1 busxHCI Host Controller /0/100/14/0/4 enx0c5b8f279a64 communication HUAWEI_MOBILE /0/100/14/0/5 input Dell MS116 USB Optical Mouse /0/100/14/0/6 input Dell KB216 Wired Keyboard /0/100/14/0/b genericUSB2.0-CRW /0/100/14/0/c genericUB91C /0/100/14/0/e communication Bluetooth wireless interface /0/100/14/1usb2 busxHCI Host Controller /0/100/14.2 memory RAM memory /0/100/14.3wlo1 networkWi-Fi 6 AX201 /0/100/15 busComet Lake PCH Serial IO I2C /0/100/16 communication Comet Lake HECI Controller /0/100/17 storageIntel Corporation /0/100/1b bridge Comet Lake PCI Express Root P /0/100/1b/0 storageSamsung Electronics Co Ltd /0/100/1b/0/0 /dev/nvme0 storagePM991 NVMe Samsung 512GB /0/100/1b/0/0/1/dev/nvme0n1 disk 512GB NVMe namespace /0/100/1b/0/0/1/1 volume 149MiB Windows FAT volume /0/100/1b/0/0/1/2 /dev/nvme0n1p2 volume 127MiB reserved partition /0/100/1b/0/0/1/3 /dev/nvme0n1p3 volume 214GiB Windows NTFS volume /0/100/1b/0/0/1/4 /dev/nvme0n1p4 volume 989MiB Windows NTFS volume /0/100/1b/0/0/1/5 /dev/nvme0n1p5 volume 16GiB Windows NTFS volume /0/100/1b/0/0/1/6 /dev/nvme0n1p6 volume 1417MiB Windows NTFS volume /0/100/1b/0/0/1/7 /dev/nvme0n1p7 volume 243GiB EXT4 volume /0/100/1c bridge Intel Corporation /0/100/1c/0enp3s0 networkRealtek Semiconductor Co., Lt /0/100/1f bridge Intel Corporation /0/100/1f.3 multimedia Comet Lake PCH cAVS /0/100/1f.4
[Kernel-packages] [Bug 1929657] Re: [Ubuntu 20.4.2] vLan not getting static IP assigned (on s390x)
Hi Mario, so did I got it right that this is the only one out of multiple systems with a similar config that has this problem - on a ROcE interface with vlan? Did you modified expanded the device config of that system over time (with more OSA or more RoCE devices) or was it untouched after initial installation? (Well, I think at least regular updates were done ...) Are all these systems with RoCE v2.x devices? What happens if you try to set the IP via the ip command? Well, I just configured all RoCE devices that I have on this LPAR for vlan usage and assigned IP addresses to the base and vlan interface with the help of the ip command, which worked: ip a | grep "192.168.1.20" inet 192.168.1.201/24 scope global enP1p0s0 inet 192.168.1.203/24 scope global enP1p0s0d1 inet 192.168.1.205/24 scope global enP2p0s0 inet 192.168.1.207/24 scope global enP2p0s0d1 inet 192.168.1.202/24 scope global enP1p0s0.1234 inet 192.168.1.204/24 scope global enP1p0s0d1.1234 inet 192.168.1.206/24 scope global enP2p0s0.1234 inet 192.168.1.208/24 scope global enP2p0s0d1.1234 Next: transfer this config to the netplan yaml ... -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1929657 Title: [Ubuntu 20.4.2] vLan not getting static IP assigned (on s390x) Status in Ubuntu on IBM z Systems: Incomplete Status in linux package in Ubuntu: New Status in netplan.io package in Ubuntu: New Bug description: ---Problem Description--- Doing vLAN configuration one of the vLANs is not getting static IP assigned when the rest are workin without problems Contact Information = Mario Alvarado/mario.alberto.gali...@ibm.com ---uname output--- Linux ilabg13.tuc.stglabs.ibm.com 5.4.0-73-generic #82-Ubuntu SMP Wed Apr 14 17:29:32 UTC 2021 s390x s390x s390x GNU/Linux Machine Type = z15 ---Debugger--- A debugger is not configured ---Steps to Reproduce--- 1)Configure the netplan file as follow: root@ilabg13:~# cat /etc/netplan/01-iscsi-config.yaml # This is the network config written by 'subiquity' network: ethernets: encdb0: addresses: - 11.111.114.213/22 macaddress: 02:76:54:00:00:03 encdc0: addresses: - 11.111.112.213/22 macaddress: 02:76:54:00:00:04 enP50s3832 : addresses: - 11.111.112.214/22 enP53p0s0: addresses: - 11.111.112.215/22 vlans: encdb0.160: id: 160 link: encdb0 mtu: 9000 addresses: - 192.168.160.53/24 encdc0.150: id: 150 link: encdc0 mtu: 9000 addresses: - 192.168.150.53/24 enP50s3832.170: id: 170 link: enP50s3832 mtu: 9000 addresses: - 192.168.170.53/24 enP53p0s0.171: id: 171 link: enP53p0s0 mtu: 9000 addresses: - 192.168.171.53/24 version: 2 2)run net plan apply: root@ilabg13:~# netplan --debug apply ** (generate:59965): DEBUG: 14:55:15.046: Processing input file /etc/netplan/00-installer-config.yaml.. ** (generate:59965): DEBUG: 14:55:15.046: starting new processing pass ** (generate:59965): DEBUG: 14:55:15.046: Processing input file /etc/netplan/01-iscsi-config.yaml.. ** (generate:59965): DEBUG: 14:55:15.046: starting new processing pass ** (generate:59965): DEBUG: 14:55:15.046: We have some netdefs, pass them through a final round of validation ** (generate:59965): DEBUG: 14:55:15.046: encdc0: setting default backend to 1 ** (generate:59965): DEBUG: 14:55:15.046: Configuration is valid ** (generate:59965): DEBUG: 14:55:15.046: encdb0: setting default backend to 1 ** (generate:59965): DEBUG: 14:55:15.046: Configuration is valid ** (generate:59965): DEBUG: 14:55:15.046: ence0f: setting default backend to 1 ** (generate:59965): DEBUG: 14:55:15.046: Configuration is valid ** (generate:59965): DEBUG: 14:55:15.046: encdb0.160: setting default backend to 1 ** (generate:59965): DEBUG: 14:55:15.046: Configuration is valid ** (generate:59965): DEBUG: 14:55:15.046: enP50s3832: setting default backend to 1 ** (generate:59965): DEBUG: 14:55:15.046: Configuration is valid ** (generate:59965): DEBUG: 14:55:15.046: enP53p0s0.171: setting default backend to 1 ** (generate:59965): DEBUG: 14:55:15.046: Configuration is valid ** (generate:59965): DEBUG: 14:55:15.046: enP50s3832.170: setting default backend to 1 ** (generate:59965): DEBUG: 14:55:15.046: Configuration is valid ** (generate:59965): DEBUG: 14:55:15.046: enP53p0s0: setting default backend to 1 ** (generate:59965): DEBUG: 14:55:15.046: Configuration is valid ** (generate:59965): DEBUG: 14:55:15.046: encdc0.150: setting default backend to 1 ** (generate:59965):
[Kernel-packages] [Bug 1929657] Comment bridged from LTC Bugzilla
--- Comment From mario.alberto.gali...@ibm.com 2021-06-07 14:49 EDT--- Compressed and attached system.journal. Frank, I have other systems with similar configurations but not exactly the same. It is another ubuntu host but Native linux installed in its own Lpar, and have some other hosts in a zVM bug with different OS. All of them with 2 OSA adapters and 2 RoCE. This is the first time that this issue is seen we have being using this host for at least 6 moths without doing OS reinstallation or changing the adapters and was working correctly. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1929657 Title: [Ubuntu 20.4.2] vLan not getting static IP assigned (on s390x) Status in Ubuntu on IBM z Systems: Incomplete Status in linux package in Ubuntu: New Status in netplan.io package in Ubuntu: New Bug description: ---Problem Description--- Doing vLAN configuration one of the vLANs is not getting static IP assigned when the rest are workin without problems Contact Information = Mario Alvarado/mario.alberto.gali...@ibm.com ---uname output--- Linux ilabg13.tuc.stglabs.ibm.com 5.4.0-73-generic #82-Ubuntu SMP Wed Apr 14 17:29:32 UTC 2021 s390x s390x s390x GNU/Linux Machine Type = z15 ---Debugger--- A debugger is not configured ---Steps to Reproduce--- 1)Configure the netplan file as follow: root@ilabg13:~# cat /etc/netplan/01-iscsi-config.yaml # This is the network config written by 'subiquity' network: ethernets: encdb0: addresses: - 11.111.114.213/22 macaddress: 02:76:54:00:00:03 encdc0: addresses: - 11.111.112.213/22 macaddress: 02:76:54:00:00:04 enP50s3832 : addresses: - 11.111.112.214/22 enP53p0s0: addresses: - 11.111.112.215/22 vlans: encdb0.160: id: 160 link: encdb0 mtu: 9000 addresses: - 192.168.160.53/24 encdc0.150: id: 150 link: encdc0 mtu: 9000 addresses: - 192.168.150.53/24 enP50s3832.170: id: 170 link: enP50s3832 mtu: 9000 addresses: - 192.168.170.53/24 enP53p0s0.171: id: 171 link: enP53p0s0 mtu: 9000 addresses: - 192.168.171.53/24 version: 2 2)run net plan apply: root@ilabg13:~# netplan --debug apply ** (generate:59965): DEBUG: 14:55:15.046: Processing input file /etc/netplan/00-installer-config.yaml.. ** (generate:59965): DEBUG: 14:55:15.046: starting new processing pass ** (generate:59965): DEBUG: 14:55:15.046: Processing input file /etc/netplan/01-iscsi-config.yaml.. ** (generate:59965): DEBUG: 14:55:15.046: starting new processing pass ** (generate:59965): DEBUG: 14:55:15.046: We have some netdefs, pass them through a final round of validation ** (generate:59965): DEBUG: 14:55:15.046: encdc0: setting default backend to 1 ** (generate:59965): DEBUG: 14:55:15.046: Configuration is valid ** (generate:59965): DEBUG: 14:55:15.046: encdb0: setting default backend to 1 ** (generate:59965): DEBUG: 14:55:15.046: Configuration is valid ** (generate:59965): DEBUG: 14:55:15.046: ence0f: setting default backend to 1 ** (generate:59965): DEBUG: 14:55:15.046: Configuration is valid ** (generate:59965): DEBUG: 14:55:15.046: encdb0.160: setting default backend to 1 ** (generate:59965): DEBUG: 14:55:15.046: Configuration is valid ** (generate:59965): DEBUG: 14:55:15.046: enP50s3832: setting default backend to 1 ** (generate:59965): DEBUG: 14:55:15.046: Configuration is valid ** (generate:59965): DEBUG: 14:55:15.046: enP53p0s0.171: setting default backend to 1 ** (generate:59965): DEBUG: 14:55:15.046: Configuration is valid ** (generate:59965): DEBUG: 14:55:15.046: enP50s3832.170: setting default backend to 1 ** (generate:59965): DEBUG: 14:55:15.046: Configuration is valid ** (generate:59965): DEBUG: 14:55:15.046: enP53p0s0: setting default backend to 1 ** (generate:59965): DEBUG: 14:55:15.046: Configuration is valid ** (generate:59965): DEBUG: 14:55:15.046: encdc0.150: setting default backend to 1 ** (generate:59965): DEBUG: 14:55:15.046: Configuration is valid ** (generate:59965): DEBUG: 14:55:15.047: Generating output files.. ** (generate:59965): DEBUG: 14:55:15.047: openvswitch: definition ence0f is not for us (backend 1) ** (generate:59965): DEBUG: 14:55:15.047: NetworkManager: definition ence0f is not for us (backend 1) ** (generate:59965): DEBUG: 14:55:15.047: openvswitch: definition encdb0 is not for us (backend 1) ** (generate:59965): DEBUG: 14:55:15.047: NetworkManager: definition encdb0 is not for us (backend 1) ** (generate:59965): DEBUG: 14:55:15.047: openvswitch:
[Kernel-packages] [Bug 1931160] [NEW] Focal update: v5.4.123 upstream stable release
Public bug reported: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v5.4.123 upstream stable release from git://git.kernel.org/ usb: dwc3: gadget: Enable suspend events perf unwind: Fix separate debug info files when using elfutils' libdw's unwinder perf unwind: Set userdata for all __report_module() paths NFC: nci: fix memory leak in nci_allocate_device Linux 5.4.123 UBUNTU: upstream stable to v5.4.123 ** Affects: linux (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux (Ubuntu Focal) Importance: Medium Assignee: Kamal Mostafa (kamalmostafa) Status: In Progress ** Tags: kernel-stable-tracking-bug ** Changed in: linux (Ubuntu) Status: New => Confirmed ** Tags added: kernel-stable-tracking-bug ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Focal) Status: New => In Progress ** Changed in: linux (Ubuntu Focal) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Focal) Assignee: (unassigned) => Kamal Mostafa (kamalmostafa) ** Changed in: linux (Ubuntu) Status: Confirmed => Invalid ** Description changed: + SRU Justification - SRU Justification + Impact: + The upstream process for stable tree updates is quite similar + in scope to the Ubuntu SRU process, e.g., each patch has to + demonstrably fix a bug, and each patch is vetted by upstream + by originating either directly from a mainline/stable Linux tree or + a minimally backported form of that patch. The following upstream + stable patches should be included in the Ubuntu kernel: - Impact: -The upstream process for stable tree updates is quite similar -in scope to the Ubuntu SRU process, e.g., each patch has to -demonstrably fix a bug, and each patch is vetted by upstream -by originating either directly from a mainline/stable Linux tree or -a minimally backported form of that patch. The following upstream -stable patches should be included in the Ubuntu kernel: + v5.4.123 upstream stable release + from git://git.kernel.org/ -v5.4.123 upstream stable release -from git://git.kernel.org/ + usb: dwc3: gadget: Enable suspend events + perf unwind: Fix separate debug info files when using elfutils' libdw's unwinder + perf unwind: Set userdata for all __report_module() paths + NFC: nci: fix memory leak in nci_allocate_device + Linux 5.4.123 + UBUNTU: upstream stable to v5.4.123 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1931160 Title: Focal update: v5.4.123 upstream stable release Status in linux package in Ubuntu: Invalid Status in linux source package in Focal: In Progress Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v5.4.123 upstream stable release from git://git.kernel.org/ usb: dwc3: gadget: Enable suspend events perf unwind: Fix separate debug info files when using elfutils' libdw's unwinder perf unwind: Set userdata for all __report_module() paths NFC: nci: fix memory leak in nci_allocate_device Linux 5.4.123 UBUNTU: upstream stable to v5.4.123 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1931160/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1929657] system.journal
--- Comment (attachment only) From mario.alberto.gali...@ibm.com 2021-06-07 14:39 EDT--- ** Attachment added: "system.journal" https://bugs.launchpad.net/bugs/1929657/+attachment/5502962/+files/system.journal.zip -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1929657 Title: [Ubuntu 20.4.2] vLan not getting static IP assigned (on s390x) Status in Ubuntu on IBM z Systems: Incomplete Status in linux package in Ubuntu: New Status in netplan.io package in Ubuntu: New Bug description: ---Problem Description--- Doing vLAN configuration one of the vLANs is not getting static IP assigned when the rest are workin without problems Contact Information = Mario Alvarado/mario.alberto.gali...@ibm.com ---uname output--- Linux ilabg13.tuc.stglabs.ibm.com 5.4.0-73-generic #82-Ubuntu SMP Wed Apr 14 17:29:32 UTC 2021 s390x s390x s390x GNU/Linux Machine Type = z15 ---Debugger--- A debugger is not configured ---Steps to Reproduce--- 1)Configure the netplan file as follow: root@ilabg13:~# cat /etc/netplan/01-iscsi-config.yaml # This is the network config written by 'subiquity' network: ethernets: encdb0: addresses: - 11.111.114.213/22 macaddress: 02:76:54:00:00:03 encdc0: addresses: - 11.111.112.213/22 macaddress: 02:76:54:00:00:04 enP50s3832 : addresses: - 11.111.112.214/22 enP53p0s0: addresses: - 11.111.112.215/22 vlans: encdb0.160: id: 160 link: encdb0 mtu: 9000 addresses: - 192.168.160.53/24 encdc0.150: id: 150 link: encdc0 mtu: 9000 addresses: - 192.168.150.53/24 enP50s3832.170: id: 170 link: enP50s3832 mtu: 9000 addresses: - 192.168.170.53/24 enP53p0s0.171: id: 171 link: enP53p0s0 mtu: 9000 addresses: - 192.168.171.53/24 version: 2 2)run net plan apply: root@ilabg13:~# netplan --debug apply ** (generate:59965): DEBUG: 14:55:15.046: Processing input file /etc/netplan/00-installer-config.yaml.. ** (generate:59965): DEBUG: 14:55:15.046: starting new processing pass ** (generate:59965): DEBUG: 14:55:15.046: Processing input file /etc/netplan/01-iscsi-config.yaml.. ** (generate:59965): DEBUG: 14:55:15.046: starting new processing pass ** (generate:59965): DEBUG: 14:55:15.046: We have some netdefs, pass them through a final round of validation ** (generate:59965): DEBUG: 14:55:15.046: encdc0: setting default backend to 1 ** (generate:59965): DEBUG: 14:55:15.046: Configuration is valid ** (generate:59965): DEBUG: 14:55:15.046: encdb0: setting default backend to 1 ** (generate:59965): DEBUG: 14:55:15.046: Configuration is valid ** (generate:59965): DEBUG: 14:55:15.046: ence0f: setting default backend to 1 ** (generate:59965): DEBUG: 14:55:15.046: Configuration is valid ** (generate:59965): DEBUG: 14:55:15.046: encdb0.160: setting default backend to 1 ** (generate:59965): DEBUG: 14:55:15.046: Configuration is valid ** (generate:59965): DEBUG: 14:55:15.046: enP50s3832: setting default backend to 1 ** (generate:59965): DEBUG: 14:55:15.046: Configuration is valid ** (generate:59965): DEBUG: 14:55:15.046: enP53p0s0.171: setting default backend to 1 ** (generate:59965): DEBUG: 14:55:15.046: Configuration is valid ** (generate:59965): DEBUG: 14:55:15.046: enP50s3832.170: setting default backend to 1 ** (generate:59965): DEBUG: 14:55:15.046: Configuration is valid ** (generate:59965): DEBUG: 14:55:15.046: enP53p0s0: setting default backend to 1 ** (generate:59965): DEBUG: 14:55:15.046: Configuration is valid ** (generate:59965): DEBUG: 14:55:15.046: encdc0.150: setting default backend to 1 ** (generate:59965): DEBUG: 14:55:15.046: Configuration is valid ** (generate:59965): DEBUG: 14:55:15.047: Generating output files.. ** (generate:59965): DEBUG: 14:55:15.047: openvswitch: definition ence0f is not for us (backend 1) ** (generate:59965): DEBUG: 14:55:15.047: NetworkManager: definition ence0f is not for us (backend 1) ** (generate:59965): DEBUG: 14:55:15.047: openvswitch: definition encdb0 is not for us (backend 1) ** (generate:59965): DEBUG: 14:55:15.047: NetworkManager: definition encdb0 is not for us (backend 1) ** (generate:59965): DEBUG: 14:55:15.047: openvswitch: definition encdc0 is not for us (backend 1) ** (generate:59965): DEBUG: 14:55:15.047: NetworkManager: definition encdc0 is not for us (backend 1) ** (generate:59965): DEBUG: 14:55:15.047: openvswitch: definition enP50s3832 is not for us (backend 1) ** (generate:59965): DEBUG: 14:55:15.047: NetworkManager: definition
[Kernel-packages] [Bug 1931159] Re: Focal update: v5.4.122 upstream stable release
** Description changed: + SRU Justification - SRU Justification + Impact: + The upstream process for stable tree updates is quite similar + in scope to the Ubuntu SRU process, e.g., each patch has to + demonstrably fix a bug, and each patch is vetted by upstream + by originating either directly from a mainline/stable Linux tree or + a minimally backported form of that patch. The following upstream + stable patches should be included in the Ubuntu kernel: - Impact: -The upstream process for stable tree updates is quite similar -in scope to the Ubuntu SRU process, e.g., each patch has to -demonstrably fix a bug, and each patch is vetted by upstream -by originating either directly from a mainline/stable Linux tree or -a minimally backported form of that patch. The following upstream -stable patches should be included in the Ubuntu kernel: + v5.4.122 upstream stable release + from git://git.kernel.org/ -v5.4.122 upstream stable release -from git://git.kernel.org/ + firmware: arm_scpi: Prevent the ternary sign expansion bug + openrisc: Fix a memory leak + RDMA/siw: Properly check send and receive CQ pointers + RDMA/siw: Release xarray entry + RDMA/rxe: Clear all QP fields if creation failed + scsi: ufs: core: Increase the usable queue depth + scsi: qla2xxx: Fix error return code in qla82xx_write_flash_dword() + RDMA/mlx5: Recover from fatal event in dual port mode + RDMA/core: Don't access cm_id after its destruction + platform/mellanox: mlxbf-tmfifo: Fix a memory barrier issue + platform/x86: dell-smbios-wmi: Fix oops on rmmod dell_smbios + RDMA/uverbs: Fix a NULL vs IS_ERR() bug + ptrace: make ptrace() fail if the tracee changed its pid unexpectedly + nvmet: seset ns->file when open fails + locking/mutex: clear MUTEX_FLAGS if wait_list is empty due to signal + btrfs: avoid RCU stalls while running delayed iputs + cifs: fix memory leak in smb2_copychunk_range + ALSA: dice: fix stream format for TC Electronic Konnekt Live at high sampling transfer frequency + ALSA: intel8x0: Don't update period unless prepared + ALSA: line6: Fix racy initialization of LINE6 MIDI + ALSA: dice: fix stream format at middle sampling rate for Alesis iO 26 + ALSA: firewire-lib: fix calculation for size of IR context payload + ALSA: usb-audio: Validate MS endpoint descriptors + ALSA: bebob/oxfw: fix Kconfig entry for Mackie d.2 Pro + ALSA: hda: fixup headset for ASUS GU502 laptop + Revert "ALSA: sb8: add a check for request_region" + ALSA: firewire-lib: fix check for the size of isochronous packet payload + ALSA: hda/realtek: reset eapd coeff to default value for alc287 + ALSA: hda/realtek: Add some CLOVE SSIDs of ALC293 + ALSA: hda/realtek: Fix silent headphone output on ASUS UX430UA + ALSA: hda/realtek: Add fixup for HP OMEN laptop + ALSA: hda/realtek: Add fixup for HP Spectre x360 15-df0xxx + uio_hv_generic: Fix a memory leak in error handling paths + Revert "rapidio: fix a NULL pointer dereference when create_workqueue() fails" + rapidio: handle create_workqueue() failure + Revert "serial: mvebu-uart: Fix to avoid a potential NULL pointer dereference" + drm/amdgpu: disable 3DCGCG on picasso/raven1 to avoid compute hang + drm/amdgpu: update gc golden setting for Navi12 + drm/amdgpu: update sdma golden setting for Navi12 + mmc: sdhci-pci-gli: increase 1.8V regulator wait + xen-pciback: reconfigure also from backend watch handler + dm snapshot: fix crash with transient storage and zero chunk size + Revert "video: hgafb: fix potential NULL pointer dereference" + Revert "net: stmicro: fix a missing check of clk_prepare" + Revert "leds: lp5523: fix a missing check of return value of lp55xx_read" + Revert "hwmon: (lm80) fix a missing check of bus read in lm80 probe" + Revert "video: imsttfb: fix potential NULL pointer dereferences" + Revert "ecryptfs: replace BUG_ON with error handling code" + Revert "scsi: ufs: fix a missing check of devm_reset_control_get" + Revert "gdrom: fix a memory leak bug" + cdrom: gdrom: deallocate struct gdrom_unit fields in remove_gdrom + cdrom: gdrom: initialize global variable at init time + Revert "media: rcar_drif: fix a memory disclosure" + Revert "rtlwifi: fix a potential NULL pointer dereference" + Revert "qlcnic: Avoid potential NULL pointer dereference" + Revert "niu: fix missing checks of niu_pci_eeprom_read" + ethernet: sun: niu: fix missing checks of niu_pci_eeprom_read() + net: stmicro: handle clk_prepare() failure during init + scsi: ufs: handle cleanup correctly on devm_reset_control_get error + net: rtlwifi: properly check for alloc_workqueue() failure + ics932s401: fix broken handling of errors when word reading fails + leds: lp5523: check return value of lp5xx_read and jump to cleanup code + qlcnic: Add null check after calling netdev_alloc_skb + video: hgafb: fix potential NULL pointer dereference + vgacon: Record video mode changes with VT_RESIZEX +
[Kernel-packages] [Bug 1931159] [NEW] Focal update: v5.4.122 upstream stable release
Public bug reported: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v5.4.122 upstream stable release from git://git.kernel.org/ firmware: arm_scpi: Prevent the ternary sign expansion bug openrisc: Fix a memory leak RDMA/siw: Properly check send and receive CQ pointers RDMA/siw: Release xarray entry RDMA/rxe: Clear all QP fields if creation failed scsi: ufs: core: Increase the usable queue depth scsi: qla2xxx: Fix error return code in qla82xx_write_flash_dword() RDMA/mlx5: Recover from fatal event in dual port mode RDMA/core: Don't access cm_id after its destruction platform/mellanox: mlxbf-tmfifo: Fix a memory barrier issue platform/x86: dell-smbios-wmi: Fix oops on rmmod dell_smbios RDMA/uverbs: Fix a NULL vs IS_ERR() bug ptrace: make ptrace() fail if the tracee changed its pid unexpectedly nvmet: seset ns->file when open fails locking/mutex: clear MUTEX_FLAGS if wait_list is empty due to signal btrfs: avoid RCU stalls while running delayed iputs cifs: fix memory leak in smb2_copychunk_range ALSA: dice: fix stream format for TC Electronic Konnekt Live at high sampling transfer frequency ALSA: intel8x0: Don't update period unless prepared ALSA: line6: Fix racy initialization of LINE6 MIDI ALSA: dice: fix stream format at middle sampling rate for Alesis iO 26 ALSA: firewire-lib: fix calculation for size of IR context payload ALSA: usb-audio: Validate MS endpoint descriptors ALSA: bebob/oxfw: fix Kconfig entry for Mackie d.2 Pro ALSA: hda: fixup headset for ASUS GU502 laptop Revert "ALSA: sb8: add a check for request_region" ALSA: firewire-lib: fix check for the size of isochronous packet payload ALSA: hda/realtek: reset eapd coeff to default value for alc287 ALSA: hda/realtek: Add some CLOVE SSIDs of ALC293 ALSA: hda/realtek: Fix silent headphone output on ASUS UX430UA ALSA: hda/realtek: Add fixup for HP OMEN laptop ALSA: hda/realtek: Add fixup for HP Spectre x360 15-df0xxx uio_hv_generic: Fix a memory leak in error handling paths Revert "rapidio: fix a NULL pointer dereference when create_workqueue() fails" rapidio: handle create_workqueue() failure Revert "serial: mvebu-uart: Fix to avoid a potential NULL pointer dereference" drm/amdgpu: disable 3DCGCG on picasso/raven1 to avoid compute hang drm/amdgpu: update gc golden setting for Navi12 drm/amdgpu: update sdma golden setting for Navi12 mmc: sdhci-pci-gli: increase 1.8V regulator wait xen-pciback: reconfigure also from backend watch handler dm snapshot: fix crash with transient storage and zero chunk size Revert "video: hgafb: fix potential NULL pointer dereference" Revert "net: stmicro: fix a missing check of clk_prepare" Revert "leds: lp5523: fix a missing check of return value of lp55xx_read" Revert "hwmon: (lm80) fix a missing check of bus read in lm80 probe" Revert "video: imsttfb: fix potential NULL pointer dereferences" Revert "ecryptfs: replace BUG_ON with error handling code" Revert "scsi: ufs: fix a missing check of devm_reset_control_get" Revert "gdrom: fix a memory leak bug" cdrom: gdrom: deallocate struct gdrom_unit fields in remove_gdrom cdrom: gdrom: initialize global variable at init time Revert "media: rcar_drif: fix a memory disclosure" Revert "rtlwifi: fix a potential NULL pointer dereference" Revert "qlcnic: Avoid potential NULL pointer dereference" Revert "niu: fix missing checks of niu_pci_eeprom_read" ethernet: sun: niu: fix missing checks of niu_pci_eeprom_read() net: stmicro: handle clk_prepare() failure during init scsi: ufs: handle cleanup correctly on devm_reset_control_get error net: rtlwifi: properly check for alloc_workqueue() failure ics932s401: fix broken handling of errors when word reading fails leds: lp5523: check return value of lp5xx_read and jump to cleanup code qlcnic: Add null check after calling netdev_alloc_skb video: hgafb: fix potential NULL pointer dereference vgacon: Record video mode changes with VT_RESIZEX vt: Fix character height handling with VT_RESIZEX tty: vt: always invoke vc->vc_sw->con_resize callback nvme-multipath: fix double initialization of ANA state ext4: fix error handling in ext4_end_enable_verity() Bluetooth: L2CAP: Fix handling LE modes by L2CAP_OPTIONS nvmet: use new ana_log_size instead the old one video: hgafb: correctly handle card detect failure during probe Bluetooth: SMP: Fail if remote and local public keys are identical Linux 5.4.122 UBUNTU: upstream stable to v5.4.122 ** Affects: linux (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux (Ubuntu Focal) Importance: Medium Assignee: Kamal Mostafa (kamalmostafa) Status: In
[Kernel-packages] [Bug 1930733] Re: Kernel oops with the 460.80 and 465.27 drivers when using DP, but not with HDMI
The nvidia-driver-460-server packages in the Ubuntu repositries are on 460.73.01 I installed those, and disconnected my monitor from HDMI and connected with DisplayPort instead. This seems to work without problems. What is the purpose of the server packages? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-460 in Ubuntu. https://bugs.launchpad.net/bugs/1930733 Title: Kernel oops with the 460.80 and 465.27 drivers when using DP, but not with HDMI Status in nvidia-graphics-drivers-460 package in Ubuntu: Triaged Status in nvidia-graphics-drivers-465 package in Ubuntu: Triaged Bug description: I get a kernel oops with the 460.80 and 465.27 drivers on Hirsute Jun 03 16:26:57 willow kernel: Oops: [#1] SMP PTI Jun 03 16:26:57 willow kernel: CPU: 7 PID: 2004 Comm: Xorg Tainted: P OE 5.11.0-18-generic #19-Ubuntu Jun 03 16:26:57 willow kernel: Hardware name: System manufacturer System Product Name/PRIME H270M-PLUS, BIOS 1605 12/13/2019 Jun 03 16:26:57 willow kernel: RIP: 0010:_nv015534rm+0x1b6/0x330 [nvidia] Jun 03 16:26:57 willow kernel: Code: 8b 87 68 05 00 00 ba 01 00 00 00 be 02 00 00 00 e8 bf eb 55 c8 41 83 c5 01 41 83 fd 1f 0f 84 0b 01 00 00 48 8b 45 10 44 89 ee <48> 8b b8 70 01 00 00 48 8b 87 d8 04 00 00 e8> Jun 03 16:26:57 willow kernel: RSP: :af4201893958 EFLAGS: 00010297 Jun 03 16:26:57 willow kernel: RAX: RBX: 0400 RCX: 0003 Jun 03 16:26:57 willow kernel: RDX: 0004 RSI: 0003 RDI: Jun 03 16:26:57 willow kernel: RBP: 8e318220add0 R08: 0001 R09: 8e318220acb8 Jun 03 16:26:57 willow kernel: R10: 8e3182204008 R11: 1010 R12: 0400 Jun 03 16:26:57 willow kernel: R13: 0003 R14: 8e3186ca8010 R15: 0800 Jun 03 16:26:57 willow kernel: FS: 7f5807f38a40() GS:8e3466dc() knlGS: Jun 03 16:26:57 willow kernel: CS: 0010 DS: ES: CR0: 80050033 Jun 03 16:26:57 willow kernel: CR2: 0170 CR3: 000140710005 CR4: 003706e0 Jun 03 16:26:57 willow kernel: DR0: DR1: DR2: Jun 03 16:26:57 willow kernel: DR3: DR6: fffe0ff0 DR7: 0400 Jun 03 16:26:57 willow kernel: Call Trace: Jun 03 16:26:57 willow kernel: ? _nv015556rm+0x7fd/0x1020 [nvidia] Jun 03 16:26:57 willow kernel: ? _nv027155rm+0x22c/0x4f0 [nvidia] Jun 03 16:26:57 willow kernel: ? _nv017787rm+0x303/0x5e0 [nvidia] Jun 03 16:26:57 willow kernel: ? _nv017789rm+0xe1/0x220 [nvidia] Jun 03 16:26:57 willow kernel: ? _nv022829rm+0xed/0x220 [nvidia] Jun 03 16:26:57 willow kernel: ? _nv023065rm+0x30/0x60 [nvidia] Jun 03 16:26:57 willow kernel: ? _nv000704rm+0x16da/0x22b0 [nvidia] Jun 03 16:26:57 willow kernel: ? rm_init_adapter+0xc5/0xe0 [nvidia] Jun 03 16:26:57 willow kernel: ? nv_open_device+0x122/0x8e0 [nvidia] Jun 03 16:26:57 willow kernel: ? nvidia_open+0x2b7/0x560 [nvidia] Jun 03 16:26:57 willow kernel: ? nvidia_frontend_open+0x58/0xa0 [nvidia] Jun 03 16:26:57 willow kernel: ? chrdev_open+0xf7/0x220 Jun 03 16:26:57 willow kernel: ? cdev_device_add+0x90/0x90 Jun 03 16:26:57 willow kernel: ? do_dentry_open+0x156/0x370 Jun 03 16:26:57 willow kernel: ? vfs_open+0x2d/0x30 Jun 03 16:26:57 willow kernel: ? do_open+0x1c3/0x340 Jun 03 16:26:57 willow kernel: ? path_openat+0x10a/0x1d0 Jun 03 16:26:57 willow kernel: ? do_filp_open+0x8c/0x130 Jun 03 16:26:57 willow kernel: ? __check_object_size+0x1c/0x20 Jun 03 16:26:57 willow kernel: ? do_sys_openat2+0x9b/0x150 Jun 03 16:26:57 willow kernel: ? __x64_sys_openat+0x56/0x90 Jun 03 16:26:57 willow kernel: ? do_syscall_64+0x38/0x90 Jun 03 16:26:57 willow kernel: ? entry_SYSCALL_64_after_hwframe+0x44/0xa9 Jun 03 16:26:57 willow kernel: Modules linked in: snd_seq_dummy snd_hrtimer vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) binfmt_misc zfs(PO) zunicode(PO) zzstd(O) zlua(O) zavl(PO) icp(PO) zcommon(PO) znvpair(PO) > Jun 03 16:26:57 willow kernel: sunrpc ip_tables x_tables autofs4 btrfs blake2b_generic xor raid6_pq libcrc32c hid_generic usbhid hid crct10dif_pclmul crc32_pclmul ghash_clmulni_intel aesni_intel crypto_simd c> Jun 03 16:26:57 willow kernel: CR2: 0170 Jun 03 16:26:57 willow kernel: ---[ end trace 0013b6989b267f32 ]--- Jun 03 16:26:57 willow kernel: RIP: 0010:_nv015534rm+0x1b6/0x330 [nvidia] Jun 03 16:26:57 willow kernel: Code: 8b 87 68 05 00 00 ba 01 00 00 00 be 02 00 00 00 e8 bf eb 55 c8 41 83 c5 01 41 83 fd 1f 0f 84 0b 01 00 00 48 8b 45 10 44 89 ee <48> 8b b8 70 01 00 00 48 8b 87 d8 04 00 00 e8> Jun 03 16:26:57 willow kernel: RSP: :af4201893958 EFLAGS: 00010297 Jun 03 16:26:57 willow kernel: RAX: RBX: 0400 RCX:
[Kernel-packages] [Bug 1931158] Re: Focal update: v5.4.121 upstream stable release
** Description changed:
+ SRU Justification
- SRU Justification
+ Impact:
+ The upstream process for stable tree updates is quite similar
+ in scope to the Ubuntu SRU process, e.g., each patch has to
+ demonstrably fix a bug, and each patch is vetted by upstream
+ by originating either directly from a mainline/stable Linux tree or
+ a minimally backported form of that patch. The following upstream
+ stable patches should be included in the Ubuntu kernel:
- Impact:
-The upstream process for stable tree updates is quite similar
-in scope to the Ubuntu SRU process, e.g., each patch has to
-demonstrably fix a bug, and each patch is vetted by upstream
-by originating either directly from a mainline/stable Linux tree or
-a minimally backported form of that patch. The following upstream
-stable patches should be included in the Ubuntu kernel:
+ v5.4.121 upstream stable release
+ from git://git.kernel.org/
-v5.4.121 upstream stable release
-from git://git.kernel.org/
+ x86/msr: Fix wr/rdmsr_safe_regs_on_cpu() prototypes
+ kgdb: fix gcc-11 warning on indentation
+ usb: sl811-hcd: improve misleading indentation
+ cxgb4: Fix the -Wmisleading-indentation warning
+ isdn: capi: fix mismatched prototypes
+ pinctrl: ingenic: Improve unreachable code generation
+ xsk: Simplify detection of empty and full rings
+ virtio_net: Do not pull payload in skb->head
+ PCI: thunder: Fix compile testing
+ dmaengine: dw-edma: Fix crash on loading/unloading driver
+ ARM: 9066/1: ftrace: pause/unpause function graph tracer in cpu_suspend()
+ ACPI / hotplug / PCI: Fix reference count leak in enable_slot()
+ Input: elants_i2c - do not bind to i2c-hid compatible ACPI instantiated
devices
+ Input: silead - add workaround for x86 BIOS-es which bring the chip up in a
stuck state
+ um: Mark all kernel symbols as local
+ um: Disable CONFIG_GCOV with MODULES
+ ARM: 9075/1: kernel: Fix interrupted SMC calls
+ scripts/recordmcount.pl: Fix RISC-V regex for clang
+ riscv: Workaround mcount name prior to clang-13
+ scsi: lpfc: Fix illegal memory access on Abort IOCBs
+ ceph: fix fscache invalidation
+ scsi: target: tcmu: Return from tcmu_handle_completions() if cmd_id not found
+ bridge: Fix possible races between assigning rx_handler_data and setting
IFF_BRIDGE_PORT bit
+ drm/amd/display: Fix two cursor duplication when using overlay
+ gpiolib: acpi: Add quirk to ignore EC wakeups on Dell Venue 10 Pro 5055
+ ALSA: hda: generic: change the DAC ctl name for LO+SPK or LO+HP
+ block: reexpand iov_iter after read/write
+ lib: stackdepot: turn depot_lock spinlock to raw_spinlock
+ net: stmmac: Do not enable RX FIFO overflow interrupts
+ ip6_gre: proper dev_{hold|put} in ndo_[un]init methods
+ sit: proper dev_{hold|put} in ndo_[un]init methods
+ ip6_tunnel: sit: proper dev_{hold|put} in ndo_[un]init methods
+ ipv6: remove extra dev_hold() for fallback tunnels
+ KVM: arm64: Initialize VCPU mdcr_el2 before loading it
+ tweewide: Fix most Shebang lines
+ scripts: switch explicitly to Python 3
+ Linux 5.4.121
+ UBUNTU: upstream stable to v5.4.121
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1931158
Title:
Focal update: v5.4.121 upstream stable release
Status in linux package in Ubuntu:
Invalid
Status in linux source package in Focal:
In Progress
Bug description:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either directly from a mainline/stable Linux tree or
a minimally backported form of that patch. The following upstream
stable patches should be included in the Ubuntu kernel:
v5.4.121 upstream stable release
from git://git.kernel.org/
x86/msr: Fix wr/rdmsr_safe_regs_on_cpu() prototypes
kgdb: fix gcc-11 warning on indentation
usb: sl811-hcd: improve misleading indentation
cxgb4: Fix the -Wmisleading-indentation warning
isdn: capi: fix mismatched prototypes
pinctrl: ingenic: Improve unreachable code generation
xsk: Simplify detection of empty and full rings
virtio_net: Do not pull payload in skb->head
PCI: thunder: Fix compile testing
dmaengine: dw-edma: Fix crash on loading/unloading driver
ARM: 9066/1: ftrace: pause/unpause function graph tracer in cpu_suspend()
ACPI / hotplug / PCI: Fix reference count leak in enable_slot()
Input: elants_i2c - do not bind to i2c-hid compatible ACPI instantiated
devices
Input: silead - add workaround for x86 BIOS-es which bring the chip up in a
stuck state
um: Mark all kernel symbols as local
um: Disable CONFIG_GCOV with MODULES
ARM: 9075/1: kernel: Fix interrupted SMC
[Kernel-packages] [Bug 1931158] [NEW] Focal update: v5.4.121 upstream stable release
Public bug reported: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v5.4.121 upstream stable release from git://git.kernel.org/ ** Affects: linux (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux (Ubuntu Focal) Importance: Medium Assignee: Kamal Mostafa (kamalmostafa) Status: In Progress ** Tags: kernel-stable-tracking-bug ** Changed in: linux (Ubuntu) Status: New => Confirmed ** Tags added: kernel-stable-tracking-bug ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Focal) Status: New => In Progress ** Changed in: linux (Ubuntu Focal) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Focal) Assignee: (unassigned) => Kamal Mostafa (kamalmostafa) ** Changed in: linux (Ubuntu) Status: Confirmed => 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/1931158 Title: Focal update: v5.4.121 upstream stable release Status in linux package in Ubuntu: Invalid Status in linux source package in Focal: In Progress Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v5.4.121 upstream stable release from git://git.kernel.org/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1931158/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1810183] Re: numpad on touchpad doesn't work in ASUS Zenbook 14
asus M433IA doesn`t work backlight OS: Parrot OS 4.11 x86_64 Host: VivoBook_ASUSLaptop X421IA_M433IA 1.0 Kernel: 5.10.0-6parrot1-amd64 sudo i2cdetect -l: ``` i2c-3 smbus SMBus PIIX4 adapter port 1 at 0b20 SMBus adapter i2c-1 smbus SMBus PIIX4 adapter port 0 at 0b00 SMBus adapter i2c-6 i2c AMDGPU DM aux hw bus 0 I2C adapter i2c-4 i2c AMDGPU DM i2c hw bus 0 I2C adapter i2c-2 smbus SMBus PIIX4 adapter port 2 at 0b00 SMBus adapter i2c-0 i2c Synopsys DesignWare I2C adapter I2C adapter i2c-5 i2c AMDGPU DM i2c hw bus 1 I2C adapter ``` -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1810183 Title: numpad on touchpad doesn't work in ASUS Zenbook 14 Status in Linux: New Status in linux package in Ubuntu: Confirmed Bug description: I have Asus Zenbook 14 UX433FA which I have installed Ubuntu 18.10 alongside windows 10. The numeric keypads are within the touchpad and are supposed to be turned on by a button on the touchpad. This works well in Windows but doesn't work in Ubuntu. I have tried to search for any related problems/solutions online but I haven't been able to. I will appreciate any suggestion or help. Thanks, --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.10 InstallationDate: Installed on 2018-12-30 (4 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) Package: linux (not installed) Tags: cosmic Uname: Linux 4.19.11-041911-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.10 InstallationDate: Installed on 2018-12-30 (4 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) Package: linux (not installed) Tags: cosmic Uname: Linux 4.18.10-041810-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1810183/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1931106] Re: bnxt_en NIC driver crashes IO_PAGE_FAULT
Did that, and after ~1 hour after I put them back in production 4 out of 5 servers I've upgraded to v5.13-rc5 crashed and the last after one more hour. For comaparison, with the old kernel version it occured ~2/3 times a week. New syslog: https://pastebin.com/GWqtVaA3 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1931106 Title: bnxt_en NIC driver crashes IO_PAGE_FAULT Status in linux package in Ubuntu: Incomplete Bug description: Hi all, We received a bunch of new servers with a Supermicro H12SSL-NT mainboard that has an embedded Broadcom BCM57416 NIC. On all those servers we observe crashes of the NIC driver (bnxt_en) from time to time. We're not able to manually reproduce this issue, it just occurs at some point. Also our monitoring does not show any irregularities(high traffic flow or sth. like this). Syslog: https://pastebin.com/yDAyjHvF All servers are running with up-to-date packages: $ lsb_release -rd Description: Ubuntu 20.04.2 LTS Release: 20.04 $ uname -r 5.4.0-73-generic It also happens on older kernel versions (tested 5.4.0-66) as well as the HWE kernel (tested 5.8.0-55). Thanks in advance. ~ Roman To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1931106/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1929455] Re: Hirsute update: v5.11.21 upstream stable release
** Also affects: linux-gcp (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Impish) Importance: Undecided Status: Invalid ** Also affects: linux-gcp (Ubuntu Impish) Importance: Undecided Status: New ** Also affects: linux-oracle (Ubuntu Impish) Importance: Undecided Status: New ** Changed in: linux-gcp (Ubuntu Impish) Status: New => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1929455 Title: Hirsute update: v5.11.21 upstream stable release Status in linux package in Ubuntu: Invalid Status in linux-gcp package in Ubuntu: In Progress Status in linux-oracle package in Ubuntu: New Status in linux source package in Hirsute: Fix Committed Status in linux-gcp source package in Hirsute: New Status in linux-oracle source package in Hirsute: New Status in linux source package in Impish: Invalid Status in linux-gcp source package in Impish: In Progress Status in linux-oracle source package in Impish: New Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v5.11.21 upstream stable release from git://git.kernel.org/ Bluetooth: verify AMP hci_chan before amp_destroy bluetooth: eliminate the potential race condition when removing the HCI controller net/nfc: fix use-after-free llcp_sock_bind/connect Revert "USB: cdc-acm: fix rounding error in TIOCSSERIAL" usb: roles: Call try_module_get() from usb_role_switch_find_by_fwnode() tty: moxa: fix TIOCSSERIAL jiffies conversions tty: amiserial: fix TIOCSSERIAL permission check USB: serial: usb_wwan: fix TIOCSSERIAL jiffies conversions staging: greybus: uart: fix TIOCSSERIAL jiffies conversions USB: serial: ti_usb_3410_5052: fix TIOCSSERIAL permission check staging: fwserial: fix TIOCSSERIAL jiffies conversions tty: moxa: fix TIOCSSERIAL permission check staging: fwserial: fix TIOCSSERIAL permission check drm: bridge: fix LONTIUM use of mipi_dsi_() functions usb: typec: tcpm: Address incorrect values of tcpm psy for fixed supply usb: typec: tcpm: Address incorrect values of tcpm psy for pps supply usb: typec: tcpm: update power supply once partner accepts usb: xhci-mtk: remove or operator for setting schedule parameters usb: xhci-mtk: improve bandwidth scheduling with TT ASoC: samsung: tm2_wm5110: check of of_parse return value ASoC: Intel: kbl_da7219_max98927: Fix kabylake_ssp_fixup function ASoC: tlv320aic32x4: Register clocks before registering component ASoC: tlv320aic32x4: Increase maximum register in regmap MIPS: pci-mt7620: fix PLL lock check MIPS: pci-rt2880: fix slot 0 configuration FDDI: defxx: Bail out gracefully with unassigned PCI resource for CSR PCI: Allow VPD access for QLogic ISP2722 KVM: x86: Defer the MMU unload to the normal path on an global INVPCID PCI: keystone: Let AM65 use the pci_ops defined in pcie-designware-host.c PM / devfreq: Unlock mutex and free devfreq struct in error path soc/tegra: regulators: Fix locking up when voltage-spread is out of range iio: inv_mpu6050: Fully validate gyro and accel scale writes iio: sx9310: Fix write_.._debounce() iio:accel:adis16201: Fix wrong axis assignment that prevents loading iio:adc:ad7476: Fix remove handling iio: sx9310: Fix access to variable DT array sc16is7xx: Defer probe if device read fails phy: cadence: Sierra: Fix PHY power_on sequence misc: lis3lv02d: Fix false-positive WARN on various HP models phy: ti: j721e-wiz: Invoke wiz_init() before of_platform_device_create() misc: vmw_vmci: explicitly initialize vmci_notify_bm_set_msg struct misc: vmw_vmci: explicitly initialize vmci_datagram payload selinux: add proper NULL termination to the secclass_map permissions x86, sched: Treat Intel SNC topology as default, COD as exception async_xor: increase src_offs when dropping destination page md/bitmap: wait for external bitmap writes to complete during tear down md-cluster: fix use-after-free issue when removing rdev md: split mddev_find md: factor out a mddev_find_locked helper from mddev_find md: md_open returns -EBUSY when entering racing area md: Fix missing unused status line of /proc/mdstat MIPS: generic: Update node names to avoid unit addresses mt76: mt7615: use ieee80211_free_txskb() in mt7615_tx_token_put() ipw2x00: potential buffer overflow in libipw_wx_set_encodeext() cfg80211: scan: drop entry from hidden_list on overflow
[Kernel-packages] [Bug 1929657] Comment bridged from LTC Bugzilla
--- Comment From mario.alberto.gali...@ibm.com 2021-06-07 13:56 EDT--- Could you provide a place to upload the system.journal file? it pass the limit of 51200 KB -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1929657 Title: [Ubuntu 20.4.2] vLan not getting static IP assigned (on s390x) Status in Ubuntu on IBM z Systems: Incomplete Status in linux package in Ubuntu: New Status in netplan.io package in Ubuntu: New Bug description: ---Problem Description--- Doing vLAN configuration one of the vLANs is not getting static IP assigned when the rest are workin without problems Contact Information = Mario Alvarado/mario.alberto.gali...@ibm.com ---uname output--- Linux ilabg13.tuc.stglabs.ibm.com 5.4.0-73-generic #82-Ubuntu SMP Wed Apr 14 17:29:32 UTC 2021 s390x s390x s390x GNU/Linux Machine Type = z15 ---Debugger--- A debugger is not configured ---Steps to Reproduce--- 1)Configure the netplan file as follow: root@ilabg13:~# cat /etc/netplan/01-iscsi-config.yaml # This is the network config written by 'subiquity' network: ethernets: encdb0: addresses: - 11.111.114.213/22 macaddress: 02:76:54:00:00:03 encdc0: addresses: - 11.111.112.213/22 macaddress: 02:76:54:00:00:04 enP50s3832 : addresses: - 11.111.112.214/22 enP53p0s0: addresses: - 11.111.112.215/22 vlans: encdb0.160: id: 160 link: encdb0 mtu: 9000 addresses: - 192.168.160.53/24 encdc0.150: id: 150 link: encdc0 mtu: 9000 addresses: - 192.168.150.53/24 enP50s3832.170: id: 170 link: enP50s3832 mtu: 9000 addresses: - 192.168.170.53/24 enP53p0s0.171: id: 171 link: enP53p0s0 mtu: 9000 addresses: - 192.168.171.53/24 version: 2 2)run net plan apply: root@ilabg13:~# netplan --debug apply ** (generate:59965): DEBUG: 14:55:15.046: Processing input file /etc/netplan/00-installer-config.yaml.. ** (generate:59965): DEBUG: 14:55:15.046: starting new processing pass ** (generate:59965): DEBUG: 14:55:15.046: Processing input file /etc/netplan/01-iscsi-config.yaml.. ** (generate:59965): DEBUG: 14:55:15.046: starting new processing pass ** (generate:59965): DEBUG: 14:55:15.046: We have some netdefs, pass them through a final round of validation ** (generate:59965): DEBUG: 14:55:15.046: encdc0: setting default backend to 1 ** (generate:59965): DEBUG: 14:55:15.046: Configuration is valid ** (generate:59965): DEBUG: 14:55:15.046: encdb0: setting default backend to 1 ** (generate:59965): DEBUG: 14:55:15.046: Configuration is valid ** (generate:59965): DEBUG: 14:55:15.046: ence0f: setting default backend to 1 ** (generate:59965): DEBUG: 14:55:15.046: Configuration is valid ** (generate:59965): DEBUG: 14:55:15.046: encdb0.160: setting default backend to 1 ** (generate:59965): DEBUG: 14:55:15.046: Configuration is valid ** (generate:59965): DEBUG: 14:55:15.046: enP50s3832: setting default backend to 1 ** (generate:59965): DEBUG: 14:55:15.046: Configuration is valid ** (generate:59965): DEBUG: 14:55:15.046: enP53p0s0.171: setting default backend to 1 ** (generate:59965): DEBUG: 14:55:15.046: Configuration is valid ** (generate:59965): DEBUG: 14:55:15.046: enP50s3832.170: setting default backend to 1 ** (generate:59965): DEBUG: 14:55:15.046: Configuration is valid ** (generate:59965): DEBUG: 14:55:15.046: enP53p0s0: setting default backend to 1 ** (generate:59965): DEBUG: 14:55:15.046: Configuration is valid ** (generate:59965): DEBUG: 14:55:15.046: encdc0.150: setting default backend to 1 ** (generate:59965): DEBUG: 14:55:15.046: Configuration is valid ** (generate:59965): DEBUG: 14:55:15.047: Generating output files.. ** (generate:59965): DEBUG: 14:55:15.047: openvswitch: definition ence0f is not for us (backend 1) ** (generate:59965): DEBUG: 14:55:15.047: NetworkManager: definition ence0f is not for us (backend 1) ** (generate:59965): DEBUG: 14:55:15.047: openvswitch: definition encdb0 is not for us (backend 1) ** (generate:59965): DEBUG: 14:55:15.047: NetworkManager: definition encdb0 is not for us (backend 1) ** (generate:59965): DEBUG: 14:55:15.047: openvswitch: definition encdc0 is not for us (backend 1) ** (generate:59965): DEBUG: 14:55:15.047: NetworkManager: definition encdc0 is not for us (backend 1) ** (generate:59965): DEBUG: 14:55:15.047: openvswitch: definition enP50s3832 is not for us (backend 1) ** (generate:59965): DEBUG: 14:55:15.047: NetworkManager: definition enP50s3832 is not for us (backend 1) **
[Kernel-packages] [Bug 1929657] Re: [Ubuntu 20.4.2] vLan not getting static IP assigned (on s390x)
I was now able to work on trying to recreate this situation - even if I will not be able to recreate it exactly due to different CEC and peripherals. On a clean 20.04.2 install (incl. latest updates) with 4 OSA based qeth devices, I have the first qeth device with only one IP address assigned to the vlan interface - that is what I wanted, since that is the default (and I want to make sure to always be able to reach the system). Then I added 4 additional qeth devices and assigned IP addresses to the base-, as well as to their vlan-interface, both - everything is fine so far and all 8 (well, in total 9) addresses got statically assigned. I'll now try to add RoCE interfaces on top of this, but I only have RoCE 1 aka Mellanox Connect-X 3. Btw. have you been able to gather the journal logs, so that you can share them with us, too? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1929657 Title: [Ubuntu 20.4.2] vLan not getting static IP assigned (on s390x) Status in Ubuntu on IBM z Systems: Incomplete Status in linux package in Ubuntu: New Status in netplan.io package in Ubuntu: New Bug description: ---Problem Description--- Doing vLAN configuration one of the vLANs is not getting static IP assigned when the rest are workin without problems Contact Information = Mario Alvarado/mario.alberto.gali...@ibm.com ---uname output--- Linux ilabg13.tuc.stglabs.ibm.com 5.4.0-73-generic #82-Ubuntu SMP Wed Apr 14 17:29:32 UTC 2021 s390x s390x s390x GNU/Linux Machine Type = z15 ---Debugger--- A debugger is not configured ---Steps to Reproduce--- 1)Configure the netplan file as follow: root@ilabg13:~# cat /etc/netplan/01-iscsi-config.yaml # This is the network config written by 'subiquity' network: ethernets: encdb0: addresses: - 11.111.114.213/22 macaddress: 02:76:54:00:00:03 encdc0: addresses: - 11.111.112.213/22 macaddress: 02:76:54:00:00:04 enP50s3832 : addresses: - 11.111.112.214/22 enP53p0s0: addresses: - 11.111.112.215/22 vlans: encdb0.160: id: 160 link: encdb0 mtu: 9000 addresses: - 192.168.160.53/24 encdc0.150: id: 150 link: encdc0 mtu: 9000 addresses: - 192.168.150.53/24 enP50s3832.170: id: 170 link: enP50s3832 mtu: 9000 addresses: - 192.168.170.53/24 enP53p0s0.171: id: 171 link: enP53p0s0 mtu: 9000 addresses: - 192.168.171.53/24 version: 2 2)run net plan apply: root@ilabg13:~# netplan --debug apply ** (generate:59965): DEBUG: 14:55:15.046: Processing input file /etc/netplan/00-installer-config.yaml.. ** (generate:59965): DEBUG: 14:55:15.046: starting new processing pass ** (generate:59965): DEBUG: 14:55:15.046: Processing input file /etc/netplan/01-iscsi-config.yaml.. ** (generate:59965): DEBUG: 14:55:15.046: starting new processing pass ** (generate:59965): DEBUG: 14:55:15.046: We have some netdefs, pass them through a final round of validation ** (generate:59965): DEBUG: 14:55:15.046: encdc0: setting default backend to 1 ** (generate:59965): DEBUG: 14:55:15.046: Configuration is valid ** (generate:59965): DEBUG: 14:55:15.046: encdb0: setting default backend to 1 ** (generate:59965): DEBUG: 14:55:15.046: Configuration is valid ** (generate:59965): DEBUG: 14:55:15.046: ence0f: setting default backend to 1 ** (generate:59965): DEBUG: 14:55:15.046: Configuration is valid ** (generate:59965): DEBUG: 14:55:15.046: encdb0.160: setting default backend to 1 ** (generate:59965): DEBUG: 14:55:15.046: Configuration is valid ** (generate:59965): DEBUG: 14:55:15.046: enP50s3832: setting default backend to 1 ** (generate:59965): DEBUG: 14:55:15.046: Configuration is valid ** (generate:59965): DEBUG: 14:55:15.046: enP53p0s0.171: setting default backend to 1 ** (generate:59965): DEBUG: 14:55:15.046: Configuration is valid ** (generate:59965): DEBUG: 14:55:15.046: enP50s3832.170: setting default backend to 1 ** (generate:59965): DEBUG: 14:55:15.046: Configuration is valid ** (generate:59965): DEBUG: 14:55:15.046: enP53p0s0: setting default backend to 1 ** (generate:59965): DEBUG: 14:55:15.046: Configuration is valid ** (generate:59965): DEBUG: 14:55:15.046: encdc0.150: setting default backend to 1 ** (generate:59965): DEBUG: 14:55:15.046: Configuration is valid ** (generate:59965): DEBUG: 14:55:15.047: Generating output files.. ** (generate:59965): DEBUG: 14:55:15.047: openvswitch: definition ence0f is not for us (backend 1) ** (generate:59965): DEBUG: 14:55:15.047: NetworkManager: definition ence0f is not for
[Kernel-packages] [Bug 1903426] Re: package firmware-b43-installer 1:019-6 failed to install/upgrade: installed firmware-b43-installer package post-installation script subprocess returned error exit s
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: b43-fwcutter (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to b43-fwcutter in Ubuntu. https://bugs.launchpad.net/bugs/1903426 Title: package firmware-b43-installer 1:019-6 failed to install/upgrade: installed firmware-b43-installer package post-installation script subprocess returned error exit status 1 Status in b43-fwcutter package in Ubuntu: Confirmed Bug description: Upgrading system from Ubuntu MATE 20.04 to Ubuntu MATE 20.10 via Alt+F2 and then update-manager -c Updates begins but error shows with Could not install 'firmware-b43-installer' (Screenshot attached) Upgrade completes but shows error message "Upgrade could not be installed, system may be unusable" System shows that the firmware is installed: firmware-b43-installer/groovy,groovy,now 1:019-6 all [installed] firmware installer for the b43 driver ProblemType: Package DistroRelease: Ubuntu 20.10 Package: firmware-b43-installer 1:019-6 ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14 Uname: Linux 5.8.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip Date: Sat Nov 7 17:22:21 2020 ErrorMessage: installed firmware-b43-installer package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2019-04-25 (562 days ago) InstallationMedia: Ubuntu-MATE 19.04 "Disco Dingo" - Release amd64 (20190416) PackageArchitecture: all Python3Details: /usr/bin/python3.8, Python 3.8.6, python3-minimal, 3.8.6-0ubuntu1 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.20.5ubuntu2 apt 2.1.10 SourcePackage: b43-fwcutter Title: package firmware-b43-installer 1:019-6 failed to install/upgrade: installed firmware-b43-installer package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to groovy on 2020-11-08 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/b43-fwcutter/+bug/1903426/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1928788] Re: linux-azure: Add Mana network driver
** Also affects: linux-azure-5.8 (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-azure-5.8 (Ubuntu Focal) Status: New => In Progress ** Changed in: linux-azure-5.8 (Ubuntu Groovy) Status: New => Invalid ** Changed in: linux-azure-5.8 (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1928788 Title: linux-azure: Add Mana network driver Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-5.8 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-azure source package in Focal: Fix Committed Status in linux-azure-5.8 source package in Focal: In Progress Status in linux source package in Groovy: Invalid Status in linux-azure source package in Groovy: Fix Committed Status in linux-azure-5.8 source package in Groovy: Invalid Bug description: SRU Justification [Impact] Microsoft has requested the addition of the "mana" driver from Linux v5.11 https://canonical.my.salesforce.com/5004K05pZQCQA2 [Fix] This patch set consists of 5 patches that are now in mainline. The patches add the VF driver for Microsoft Azure Network Adapter (MANA), and also changes the hv_netvsc driver's netvsc/VF binding logic to check both the MAC address and the serial number (this is required by the MANA VF driver). Microsoft would like to request the following 5 patches in all supported releases: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=64ff412ad41fe3a5bf759ff4844dc1382176485c https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net- next.git/commit/?id=ca9c54d2d6a5ab2430c4eda364c77125d62e5e0f https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net- next.git/commit/?id=55cdc26a91ac270887583945aef2bd460a2805f7 https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net- next.git/commit/?id=45b102dd81491e30ac7596b5515856141f99319f https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net- next.git/commit/?id=d90a94680bc0a8069d93282bc5f2966d00b9c4a4 [Test Plan] 2021-05-17 15:25 UTC- -We tested the two versions of mana.ko: root@decui-u2004-vf:~# uname -a Linux decui-u2004-vf 5.4.0-1048-azure #50~sf00310147.1-Ubuntu SMP Tue May 11 02:06:24 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux root@decui-u2004-vf:~# modinfo mana | grep filename filename: /lib/modules/5.4.0-1048-azure/kernel/drivers/net/ethernet/microsoft/mana/mana.ko root@decui-u2004-vf:~# uname -a Linux decui-u2004-vf 5.8.0-1032-azure #34~SF00310147.1-Ubuntu SMP Tue May 11 02:01:58 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux root@decui-u2004-vf:~# modinfo mana | grep filename filename: /lib/modules/5.8.0-1032-azure/kernel/drivers/net/ethernet/microsoft/mana/mana.ko Everything worked as expected in our testing: 1. The MANA driver loads and unloads multiple times without any issue. 2. iperf TX/RX tests run without any issue, and the performance numbers are on par with what we get with the latest mainline kernel: the TX number is pretty good; the RX number is sometimes not great but this is a known issue with the latest mainline kernel as well. 3. "ethtool -S" and "ethtool -L" work as expected. 4. When iperf TX/RX tests are running, changing the number of the MANA NIC TX/RX queues and unloading/reloading the MANA driver work without any issue. [Where problems could occur] The driver may have bug(s) that cause a kernel crash. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1928788/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1927925] Re: Massive network problems with I219-V on Thinkpad T14 Gen2 (e1000e)
Thanks for the testing. Please give this kernel a try without any parameter: https://people.canonical.com/~khfeng/lp1927925-qos/ -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1927925 Title: Massive network problems with I219-V on Thinkpad T14 Gen2 (e1000e) Status in OEM Priority Project: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: I recently got a Thinkpad T14 Gen2 with a I219-V network adapter (8086:15fc). I get very slow connection speeds and even total loss of connectivity without seeing much in the logs (like dmesg etc.). ethtool reports CRC errors and paket loss. Besides Ubuntu 21.04/kernel 5.11 I tried to install Ubuntu 20.04 (kernel seems to old) and i tried the e1000e driver directly from upstream (3.8.7) with no success. A strange behaviour I observed: if connectivity is lost (notebook is not reachable via ping from another host), if I do something like "ping 8.8.8.8" on the notebook itself, it becomes reachable from the other host again. Downloads in general are very slow if they work at all. WLAN (AX210) seems to work fine, wired network using a USB-network adapter works fine, too. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ros3285 F pulseaudio CasperMD5CheckResult: pass DistroRelease: Ubuntu 21.04 HibernationDevice: RESUME=none InstallationDate: Installed on 2021-05-07 (2 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: LENOVO 20W0004MGE NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_n51dtp@/vmlinuz-5.11.0-16-generic root=ZFS=rpool/ROOT/ubuntu_n51dtp ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.11.0-16-generic N/A linux-backports-modules-5.11.0-16-generic N/A linux-firmware 1.197 Tags: hirsute Uname: Linux 5.11.0-16-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 03/10/2021 dmi.bios.release: 1.10 dmi.bios.vendor: LENOVO dmi.bios.version: N34ET21W (1.10 ) dmi.board.asset.tag: Not Available dmi.board.name: 20W0004MGE 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.ec.firmware.release: 1.8 dmi.modalias: dmi:bvnLENOVO:bvrN34ET21W(1.10):bd03/10/2021:br1.10:efr1.8:svnLENOVO:pn20W0004MGE:pvrThinkPadT14Gen2i:rvnLENOVO:rn20W0004MGE:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T14 Gen 2i dmi.product.name: 20W0004MGE dmi.product.sku: LENOVO_MT_20W0_BU_Think_FM_ThinkPad T14 Gen 2i dmi.product.version: ThinkPad T14 Gen 2i dmi.sys.vendor: LENOVO --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ros1673 F pulseaudio /dev/snd/controlC1: ros1673 F pulseaudio CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-05-31 (0 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: LENOVO 20W0004MGE Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.10.0-1026-oem root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.10.0-1026.27-oem 5.10.31 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.10.0-1026-oem N/A linux-backports-modules-5.10.0-1026-oem N/A linux-firmware 1.187.12 Tags: focal Uname: Linux 5.10.0-1026-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 03/10/2021 dmi.bios.release: 1.10 dmi.bios.vendor: LENOVO dmi.bios.version: N34ET21W (1.10 ) dmi.board.asset.tag: Not Available dmi.board.name: 20W0004MGE 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.ec.firmware.release: 1.8 dmi.modalias:
[Kernel-packages] [Bug 1931147] [NEW] Fix non-working GPU on Some HP desktops
Public bug reported: [Impact] Integrated GPU on AMD based HP desktop doesn't work. [Fix] Coalesce host bridge contiguous apertures so the resources requested by child devices can be met. [Test] Boot affected systems. No picture from the iGPU. With the patch applied, iGPU can work normally. [Where problems could occur] Assume there are device A and device B and they request overlapped resource region, the original logic may not be able to allocate enough resource for A so device B claimed the resource in the end. Once the fix is applied, the region may be big enough for device A, hence device B won't be able to get the resource it needs. Hopefully we don't have such broken systems. ** Affects: hwe-next Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: Critical Status: Confirmed ** Affects: linux-oem-5.10 (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux (Ubuntu Focal) Importance: Undecided Status: Won't Fix ** Affects: linux-oem-5.10 (Ubuntu Focal) Importance: Critical Status: Confirmed ** Affects: linux (Ubuntu Hirsute) Importance: Critical Status: Confirmed ** Affects: linux-oem-5.10 (Ubuntu Hirsute) Importance: Undecided Status: Invalid ** Tags: oem-priority originate-from-1914373 stella ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Hirsute) Importance: Undecided Status: New ** Also affects: linux-oem-5.10 (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-oem-5.10 (Ubuntu) Status: New => Invalid ** Changed in: linux-oem-5.10 (Ubuntu Focal) Status: New => Confirmed ** Changed in: linux-oem-5.10 (Ubuntu Hirsute) Status: New => Invalid ** Changed in: linux (Ubuntu Focal) Status: New => Won't Fix ** Changed in: linux (Ubuntu) Status: New => Confirmed ** Changed in: linux (Ubuntu Hirsute) Status: New => Confirmed ** Changed in: linux (Ubuntu) Importance: Undecided => Critical ** Changed in: linux (Ubuntu Hirsute) Importance: Undecided => Critical ** Changed in: linux-oem-5.10 (Ubuntu Focal) Importance: Undecided => Critical ** Tags added: oem-priority originate-from-1914373 stella -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1931147 Title: Fix non-working GPU on Some HP desktops Status in HWE Next: New Status in linux package in Ubuntu: Confirmed Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux source package in Focal: Won't Fix Status in linux-oem-5.10 source package in Focal: Confirmed Status in linux source package in Hirsute: Confirmed Status in linux-oem-5.10 source package in Hirsute: Invalid Bug description: [Impact] Integrated GPU on AMD based HP desktop doesn't work. [Fix] Coalesce host bridge contiguous apertures so the resources requested by child devices can be met. [Test] Boot affected systems. No picture from the iGPU. With the patch applied, iGPU can work normally. [Where problems could occur] Assume there are device A and device B and they request overlapped resource region, the original logic may not be able to allocate enough resource for A so device B claimed the resource in the end. Once the fix is applied, the region may be big enough for device A, hence device B won't be able to get the resource it needs. Hopefully we don't have such broken systems. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1931147/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1931129] Re: v5.13 net bpf selftests fail with older clang toolchains
** Tags added: patch -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1931129 Title: v5.13 net bpf selftests fail with older clang toolchains Status in linux package in Ubuntu: New Bug description: selftests/bpf: add ifdefs in tests for required Clang versions This codifies the clang version requirements from README.rst in the code, such that only expected working test cases are compiled for the expected clang version combinations. This insures that most tests are still executed, even when one doesn't have access to the latest clang toolchain. Also see internal v5.13 test results. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1931129/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1931001] Re: kernel: watchdog: BUG: soft lockup - CPU#3 stuck for 22s!
Hello Cascardo. Here you will find dmesg.tgz with: dmesg/dmesg-2021-05-07-08-22.txt dmesg/dmesg-normal.txt dmesg/dmesg-unresponsive.txt dmesg/dmesg-2021-05-20.txt dmesg-normal.txt is a full dmesg when the computer works fine. dmesg-unresponsive.txt is a full dmesg in which the computer boots and very soon becomes unresponsive to trackpad and even you can type faster than computers manages to process. Usually this happens on the first boot after a full day with the laptop shut down. dmesg-2021-05-07-08-22.txt and dmesg-2021-05-20.txt are full dmesg in which you can see the message CPU# stuck for 22s! When this happens nothing works well. I even deployed a small script to reboot the laptop when this happens. We are an school with hundreds of desktops and laptops with ubuntu 20.04 without problems. But we have received a big number of this lenovo laptops that does't work well with ubuntu 20.04 or 21.04. I don't know if it may help you but with Fedora 34 the laptop works fine. Thank you for your attention. ** Attachment added: "dmesg.tgz" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1931001/+attachment/5502949/+files/dmesg.tgz -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1931001 Title: kernel: watchdog: BUG: soft lockup - CPU#3 stuck for 22s! Status in linux package in Ubuntu: New Bug description: Ubuntu 20.04 LTS and Ubuntu 21.04 occasionally boots with very bad performance and very unresponsive to user input on Lenovo laptop Lenovo 300e 2nd Gen 81M9 (LENOVO_MT_81M9_BU_idea_FM_300e 2nd G). When this happens you can read this kind of messages on journal: --- root@alumne-1-58:~# journalctl | grep "BUG: soft" may 20 21:44:35 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [swapper/3:0] may 20 21:44:35 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [swapper/3:0] may 22 09:33:34 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [swapper/0:0] may 24 16:45:14 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#1 stuck for 23s! [prometheus-node:4220] may 24 16:45:14 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#0 stuck for 23s! [swapper/0:0] jun 03 00:01:09 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [swapper/0:0] jun 03 00:01:09 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#0 stuck for 23s! [swapper/0:0] jun 03 00:01:09 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#1 stuck for 22s! [swapper/1:0] jun 03 00:01:09 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [swapper/0:0] jun 03 00:02:15 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#0 stuck for 21s! [swapper/0:0] jun 05 08:22:58 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [irq/138-iwlwifi:1044] jun 05 08:25:06 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#2 stuck for 22s! [swapper/2:0] jun 05 08:25:06 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [irq/138-iwlwifi:1044] jun 05 08:26:42 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#1 stuck for 23s! [lxd:3975] jun 05 08:26:42 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#2 stuck for 23s! [swapper/2:0] jun 05 08:26:42 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#3 stuck for 23s! [irq/138-iwlwifi:1044] jun 05 08:27:38 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#3 stuck for 23s! [irq/138-iwlwifi:1044] jun 05 08:28:34 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [irq/138-iwlwifi:1044] jun 05 08:29:46 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [irq/138-iwlwifi:1044] root@alumne-1-58:~# --- Usually if you reboot everything works fine but it's very annoying when happens. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1931001/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1924207] Re: [SRU][F:OEM-5.10/G/H] add realtek 8852 bluetooth support
This bug was fixed in the package linux - 5.11.0-18.19+21.10.1 --- linux (5.11.0-18.19+21.10.1) impish; urgency=medium * impish/linux: 5.11.0-18.19+21.10.1 -proposed tracker (LP: #1927560) * Packaging resync (LP: #1786013) - [Packaging] update update.conf - update dkms package versions [ Ubuntu: 5.11.0-18.19 ] * hirsute/linux: 5.11.0-18.19 -proposed tracker (LP: #1927578) * Packaging resync (LP: #1786013) - update dkms package versions * Introduce the 465 driver series, fabric-manager, and libnvidia-nscq (LP: #1925522) - debian/dkms-versions -- add NVIDIA 465 and migrate 450 to 460 * linux-image-5.0.0-35-generic breaks checkpointing of container (LP: #1857257) - SAUCE: overlayfs: fix incorrect mnt_id of files opened from map_files * Hirsute update: v5.11.17 upstream stable release (LP: #1927535) - vhost-vdpa: protect concurrent access to vhost device iotlb - Revert "UBUNTU: SAUCE: ovl: Restore vm_file value when lower fs mmap fails" - ovl: fix reference counting in ovl_mmap error path - coda: fix reference counting in coda_file_mmap error path - amd/display: allow non-linear multi-planar formats - drm/amdgpu: reserve fence slot to update page table - drm/amdgpu: fix GCR_GENERAL_CNTL offset for dimgrey_cavefish - gpio: omap: Save and restore sysconfig - KEYS: trusted: Fix TPM reservation for seal/unseal - vdpa/mlx5: Set err = -ENOMEM in case dma_map_sg_attrs fails - pinctrl: lewisburg: Update number of pins in community - block: return -EBUSY when there are open partitions in blkdev_reread_part - pinctrl: core: Show pin numbers for the controllers with base = 0 - arm64: dts: allwinner: Revert SD card CD GPIO for Pine64-LTS - bpf: Allow variable-offset stack access - bpf: Refactor and streamline bounds check into helper - bpf: Tighten speculative pointer arithmetic mask - perf/x86/intel/uncore: Remove uncore extra PCI dev HSWEP_PCI_PCU_3 - perf/x86/kvm: Fix Broadwell Xeon stepping in isolation_ucodes[] - perf auxtrace: Fix potential NULL pointer dereference - perf map: Fix error return code in maps__clone() - HID: google: add don USB id - HID: asus: Add support for 2021 ASUS N-Key keyboard - HID: alps: fix error return code in alps_input_configured() - HID cp2112: fix support for multiple gpiochips - HID: wacom: Assign boolean values to a bool variable - soc: qcom: geni: shield geni_icc_get() for ACPI boot - dmaengine: xilinx: dpdma: Fix descriptor issuing on video group - dmaengine: xilinx: dpdma: Fix race condition in done IRQ - ARM: dts: Fix swapped mmc order for omap3 - m68k: fix flatmem memory model setup - net: geneve: check skb is large enough for IPv4/IPv6 header - dmaengine: tegra20: Fix runtime PM imbalance on error - s390/entry: save the caller of psw_idle - arm64: kprobes: Restore local irqflag if kprobes is cancelled - xen-netback: Check for hotplug-status existence before watching - cavium/liquidio: Fix duplicate argument - csky: change a Kconfig symbol name to fix e1000 build error - ia64: fix discontig.c section mismatches - ia64: tools: remove duplicate definition of ia64_mf() on ia64 - x86/crash: Fix crash_setup_memmap_entries() out-of-bounds access - net: hso: fix NULL-deref on disconnect regression - USB: CDC-ACM: fix poison/unpoison imbalance - Linux 5.11.17 * locking/qrwlock: Fix ordering in queued_write_lock_slowpath() (LP: #1926184) - locking/qrwlock: Fix ordering in queued_write_lock_slowpath() * Fix kernel panic at boot on dual GFX systems (LP: #1926792) - drm/amdgpu: Register VGA clients after init can no longer fail * Gigabyte R120-T33 (ARM ThunderX SoC) fails to boot in ACPI mode (LP: #1925075) - ACPI: GTDT: Don't corrupt interrupt mappings on watchdow probe failure * CirrusLogic: Cracking noises appears in built-in speaker when output volume is set >80% (LP: #1924997) - ALSA: hda/cirrus: Use CS8409 filter to fix abnormal sounds on Bullseye * CirrusLogic: The default input volume is "0%" (LP: #1923557) - ALSA: hda/cirrus: Set Initial DMIC volume for Bullseye to -26 dB * Fix no picture from HDMI when it's plugged after boot (LP: #1924238) - drm/i915/display: Handle lane polarity for DDI port * Make AMD gpus choose YCbCr420 encoding automatically when required for 4k 60Hz output (LP: #1922754) - drm/amd/display: Try YCbCr420 color when YCbCr444 fails * Hirsute update: v5.11.16 upstream stable release (LP: #1926999) - AMD_SFH: Removed unused activecontrolstatus member from the amd_mp2_dev struct - AMD_SFH: Add sensor_mask module parameter - AMD_SFH: Add DMI quirk table for BIOS-es which don't set the activestatus bits - mtd: rawnand: mtk: Fix WAITRDY break condition and timeout - Input: nspire-keypad - enable interrupts only when opened - gpio: sysfs: Obey
[Kernel-packages] [Bug 1926993] Re: Hirsute update: v5.11.15 upstream stable release
This bug was fixed in the package linux - 5.11.0-18.19+21.10.1 --- linux (5.11.0-18.19+21.10.1) impish; urgency=medium * impish/linux: 5.11.0-18.19+21.10.1 -proposed tracker (LP: #1927560) * Packaging resync (LP: #1786013) - [Packaging] update update.conf - update dkms package versions [ Ubuntu: 5.11.0-18.19 ] * hirsute/linux: 5.11.0-18.19 -proposed tracker (LP: #1927578) * Packaging resync (LP: #1786013) - update dkms package versions * Introduce the 465 driver series, fabric-manager, and libnvidia-nscq (LP: #1925522) - debian/dkms-versions -- add NVIDIA 465 and migrate 450 to 460 * linux-image-5.0.0-35-generic breaks checkpointing of container (LP: #1857257) - SAUCE: overlayfs: fix incorrect mnt_id of files opened from map_files * Hirsute update: v5.11.17 upstream stable release (LP: #1927535) - vhost-vdpa: protect concurrent access to vhost device iotlb - Revert "UBUNTU: SAUCE: ovl: Restore vm_file value when lower fs mmap fails" - ovl: fix reference counting in ovl_mmap error path - coda: fix reference counting in coda_file_mmap error path - amd/display: allow non-linear multi-planar formats - drm/amdgpu: reserve fence slot to update page table - drm/amdgpu: fix GCR_GENERAL_CNTL offset for dimgrey_cavefish - gpio: omap: Save and restore sysconfig - KEYS: trusted: Fix TPM reservation for seal/unseal - vdpa/mlx5: Set err = -ENOMEM in case dma_map_sg_attrs fails - pinctrl: lewisburg: Update number of pins in community - block: return -EBUSY when there are open partitions in blkdev_reread_part - pinctrl: core: Show pin numbers for the controllers with base = 0 - arm64: dts: allwinner: Revert SD card CD GPIO for Pine64-LTS - bpf: Allow variable-offset stack access - bpf: Refactor and streamline bounds check into helper - bpf: Tighten speculative pointer arithmetic mask - perf/x86/intel/uncore: Remove uncore extra PCI dev HSWEP_PCI_PCU_3 - perf/x86/kvm: Fix Broadwell Xeon stepping in isolation_ucodes[] - perf auxtrace: Fix potential NULL pointer dereference - perf map: Fix error return code in maps__clone() - HID: google: add don USB id - HID: asus: Add support for 2021 ASUS N-Key keyboard - HID: alps: fix error return code in alps_input_configured() - HID cp2112: fix support for multiple gpiochips - HID: wacom: Assign boolean values to a bool variable - soc: qcom: geni: shield geni_icc_get() for ACPI boot - dmaengine: xilinx: dpdma: Fix descriptor issuing on video group - dmaengine: xilinx: dpdma: Fix race condition in done IRQ - ARM: dts: Fix swapped mmc order for omap3 - m68k: fix flatmem memory model setup - net: geneve: check skb is large enough for IPv4/IPv6 header - dmaengine: tegra20: Fix runtime PM imbalance on error - s390/entry: save the caller of psw_idle - arm64: kprobes: Restore local irqflag if kprobes is cancelled - xen-netback: Check for hotplug-status existence before watching - cavium/liquidio: Fix duplicate argument - csky: change a Kconfig symbol name to fix e1000 build error - ia64: fix discontig.c section mismatches - ia64: tools: remove duplicate definition of ia64_mf() on ia64 - x86/crash: Fix crash_setup_memmap_entries() out-of-bounds access - net: hso: fix NULL-deref on disconnect regression - USB: CDC-ACM: fix poison/unpoison imbalance - Linux 5.11.17 * locking/qrwlock: Fix ordering in queued_write_lock_slowpath() (LP: #1926184) - locking/qrwlock: Fix ordering in queued_write_lock_slowpath() * Fix kernel panic at boot on dual GFX systems (LP: #1926792) - drm/amdgpu: Register VGA clients after init can no longer fail * Gigabyte R120-T33 (ARM ThunderX SoC) fails to boot in ACPI mode (LP: #1925075) - ACPI: GTDT: Don't corrupt interrupt mappings on watchdow probe failure * CirrusLogic: Cracking noises appears in built-in speaker when output volume is set >80% (LP: #1924997) - ALSA: hda/cirrus: Use CS8409 filter to fix abnormal sounds on Bullseye * CirrusLogic: The default input volume is "0%" (LP: #1923557) - ALSA: hda/cirrus: Set Initial DMIC volume for Bullseye to -26 dB * Fix no picture from HDMI when it's plugged after boot (LP: #1924238) - drm/i915/display: Handle lane polarity for DDI port * Make AMD gpus choose YCbCr420 encoding automatically when required for 4k 60Hz output (LP: #1922754) - drm/amd/display: Try YCbCr420 color when YCbCr444 fails * Hirsute update: v5.11.16 upstream stable release (LP: #1926999) - AMD_SFH: Removed unused activecontrolstatus member from the amd_mp2_dev struct - AMD_SFH: Add sensor_mask module parameter - AMD_SFH: Add DMI quirk table for BIOS-es which don't set the activestatus bits - mtd: rawnand: mtk: Fix WAITRDY break condition and timeout - Input: nspire-keypad - enable interrupts only when opened - gpio: sysfs: Obey
[Kernel-packages] [Bug 1926792] Re: Fix kernel panic at boot on dual GFX systems
This bug was fixed in the package linux - 5.11.0-18.19+21.10.1 --- linux (5.11.0-18.19+21.10.1) impish; urgency=medium * impish/linux: 5.11.0-18.19+21.10.1 -proposed tracker (LP: #1927560) * Packaging resync (LP: #1786013) - [Packaging] update update.conf - update dkms package versions [ Ubuntu: 5.11.0-18.19 ] * hirsute/linux: 5.11.0-18.19 -proposed tracker (LP: #1927578) * Packaging resync (LP: #1786013) - update dkms package versions * Introduce the 465 driver series, fabric-manager, and libnvidia-nscq (LP: #1925522) - debian/dkms-versions -- add NVIDIA 465 and migrate 450 to 460 * linux-image-5.0.0-35-generic breaks checkpointing of container (LP: #1857257) - SAUCE: overlayfs: fix incorrect mnt_id of files opened from map_files * Hirsute update: v5.11.17 upstream stable release (LP: #1927535) - vhost-vdpa: protect concurrent access to vhost device iotlb - Revert "UBUNTU: SAUCE: ovl: Restore vm_file value when lower fs mmap fails" - ovl: fix reference counting in ovl_mmap error path - coda: fix reference counting in coda_file_mmap error path - amd/display: allow non-linear multi-planar formats - drm/amdgpu: reserve fence slot to update page table - drm/amdgpu: fix GCR_GENERAL_CNTL offset for dimgrey_cavefish - gpio: omap: Save and restore sysconfig - KEYS: trusted: Fix TPM reservation for seal/unseal - vdpa/mlx5: Set err = -ENOMEM in case dma_map_sg_attrs fails - pinctrl: lewisburg: Update number of pins in community - block: return -EBUSY when there are open partitions in blkdev_reread_part - pinctrl: core: Show pin numbers for the controllers with base = 0 - arm64: dts: allwinner: Revert SD card CD GPIO for Pine64-LTS - bpf: Allow variable-offset stack access - bpf: Refactor and streamline bounds check into helper - bpf: Tighten speculative pointer arithmetic mask - perf/x86/intel/uncore: Remove uncore extra PCI dev HSWEP_PCI_PCU_3 - perf/x86/kvm: Fix Broadwell Xeon stepping in isolation_ucodes[] - perf auxtrace: Fix potential NULL pointer dereference - perf map: Fix error return code in maps__clone() - HID: google: add don USB id - HID: asus: Add support for 2021 ASUS N-Key keyboard - HID: alps: fix error return code in alps_input_configured() - HID cp2112: fix support for multiple gpiochips - HID: wacom: Assign boolean values to a bool variable - soc: qcom: geni: shield geni_icc_get() for ACPI boot - dmaengine: xilinx: dpdma: Fix descriptor issuing on video group - dmaengine: xilinx: dpdma: Fix race condition in done IRQ - ARM: dts: Fix swapped mmc order for omap3 - m68k: fix flatmem memory model setup - net: geneve: check skb is large enough for IPv4/IPv6 header - dmaengine: tegra20: Fix runtime PM imbalance on error - s390/entry: save the caller of psw_idle - arm64: kprobes: Restore local irqflag if kprobes is cancelled - xen-netback: Check for hotplug-status existence before watching - cavium/liquidio: Fix duplicate argument - csky: change a Kconfig symbol name to fix e1000 build error - ia64: fix discontig.c section mismatches - ia64: tools: remove duplicate definition of ia64_mf() on ia64 - x86/crash: Fix crash_setup_memmap_entries() out-of-bounds access - net: hso: fix NULL-deref on disconnect regression - USB: CDC-ACM: fix poison/unpoison imbalance - Linux 5.11.17 * locking/qrwlock: Fix ordering in queued_write_lock_slowpath() (LP: #1926184) - locking/qrwlock: Fix ordering in queued_write_lock_slowpath() * Fix kernel panic at boot on dual GFX systems (LP: #1926792) - drm/amdgpu: Register VGA clients after init can no longer fail * Gigabyte R120-T33 (ARM ThunderX SoC) fails to boot in ACPI mode (LP: #1925075) - ACPI: GTDT: Don't corrupt interrupt mappings on watchdow probe failure * CirrusLogic: Cracking noises appears in built-in speaker when output volume is set >80% (LP: #1924997) - ALSA: hda/cirrus: Use CS8409 filter to fix abnormal sounds on Bullseye * CirrusLogic: The default input volume is "0%" (LP: #1923557) - ALSA: hda/cirrus: Set Initial DMIC volume for Bullseye to -26 dB * Fix no picture from HDMI when it's plugged after boot (LP: #1924238) - drm/i915/display: Handle lane polarity for DDI port * Make AMD gpus choose YCbCr420 encoding automatically when required for 4k 60Hz output (LP: #1922754) - drm/amd/display: Try YCbCr420 color when YCbCr444 fails * Hirsute update: v5.11.16 upstream stable release (LP: #1926999) - AMD_SFH: Removed unused activecontrolstatus member from the amd_mp2_dev struct - AMD_SFH: Add sensor_mask module parameter - AMD_SFH: Add DMI quirk table for BIOS-es which don't set the activestatus bits - mtd: rawnand: mtk: Fix WAITRDY break condition and timeout - Input: nspire-keypad - enable interrupts only when opened - gpio: sysfs: Obey
[Kernel-packages] [Bug 1927050] Re: Enable BLK_DEV_NVME =y to support "shielded VM minimal images"
This bug was fixed in the package linux-gcp - 5.11.0-1008.8+21.10.1 --- linux-gcp (5.11.0-1008.8+21.10.1) impish; urgency=medium * impish/linux-gcp: 5.11.0-1008.8+21.10.1 -proposed tracker (LP: #1927565) * Packaging resync (LP: #1786013) - [Packaging] update update.conf - update dkms package versions -- Paolo Pisati Thu, 20 May 2021 13:01:39 +0200 ** Changed in: linux-gcp (Ubuntu) Status: Invalid => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1927050 Title: Enable BLK_DEV_NVME =y to support "shielded VM minimal images" Status in linux-gcp package in Ubuntu: Fix Released Status in linux-gcp-4.15 package in Ubuntu: Invalid Status in linux-gcp source package in Bionic: Invalid Status in linux-gcp-4.15 source package in Bionic: Fix Released Status in linux-gcp source package in Focal: Fix Released Status in linux-gcp-4.15 source package in Focal: Invalid Status in linux-gcp source package in Groovy: Fix Released Status in linux-gcp-4.15 source package in Groovy: Invalid Status in linux-gcp source package in Hirsute: Fix Released Status in linux-gcp-4.15 source package in Hirsute: Invalid Bug description: This is requested by CPC -- see the title. [Impact] nvme.ko exists outside the kernel currently [Fix] Enable BLK_DEV_NVME=y [Test] Tested by CPC crew / Google: > The test images have passed testing and we would like this enabled so we > can have minimal images boot with NVME boot disk and so we can enable > GCE confidential VMs with minimal images. [Regression Potential] Not aware of any. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-gcp/+bug/1927050/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1923415] Re: Hirsute update: v5.11.13 upstream stable release
This bug was fixed in the package linux - 5.11.0-18.19+21.10.1 --- linux (5.11.0-18.19+21.10.1) impish; urgency=medium * impish/linux: 5.11.0-18.19+21.10.1 -proposed tracker (LP: #1927560) * Packaging resync (LP: #1786013) - [Packaging] update update.conf - update dkms package versions [ Ubuntu: 5.11.0-18.19 ] * hirsute/linux: 5.11.0-18.19 -proposed tracker (LP: #1927578) * Packaging resync (LP: #1786013) - update dkms package versions * Introduce the 465 driver series, fabric-manager, and libnvidia-nscq (LP: #1925522) - debian/dkms-versions -- add NVIDIA 465 and migrate 450 to 460 * linux-image-5.0.0-35-generic breaks checkpointing of container (LP: #1857257) - SAUCE: overlayfs: fix incorrect mnt_id of files opened from map_files * Hirsute update: v5.11.17 upstream stable release (LP: #1927535) - vhost-vdpa: protect concurrent access to vhost device iotlb - Revert "UBUNTU: SAUCE: ovl: Restore vm_file value when lower fs mmap fails" - ovl: fix reference counting in ovl_mmap error path - coda: fix reference counting in coda_file_mmap error path - amd/display: allow non-linear multi-planar formats - drm/amdgpu: reserve fence slot to update page table - drm/amdgpu: fix GCR_GENERAL_CNTL offset for dimgrey_cavefish - gpio: omap: Save and restore sysconfig - KEYS: trusted: Fix TPM reservation for seal/unseal - vdpa/mlx5: Set err = -ENOMEM in case dma_map_sg_attrs fails - pinctrl: lewisburg: Update number of pins in community - block: return -EBUSY when there are open partitions in blkdev_reread_part - pinctrl: core: Show pin numbers for the controllers with base = 0 - arm64: dts: allwinner: Revert SD card CD GPIO for Pine64-LTS - bpf: Allow variable-offset stack access - bpf: Refactor and streamline bounds check into helper - bpf: Tighten speculative pointer arithmetic mask - perf/x86/intel/uncore: Remove uncore extra PCI dev HSWEP_PCI_PCU_3 - perf/x86/kvm: Fix Broadwell Xeon stepping in isolation_ucodes[] - perf auxtrace: Fix potential NULL pointer dereference - perf map: Fix error return code in maps__clone() - HID: google: add don USB id - HID: asus: Add support for 2021 ASUS N-Key keyboard - HID: alps: fix error return code in alps_input_configured() - HID cp2112: fix support for multiple gpiochips - HID: wacom: Assign boolean values to a bool variable - soc: qcom: geni: shield geni_icc_get() for ACPI boot - dmaengine: xilinx: dpdma: Fix descriptor issuing on video group - dmaengine: xilinx: dpdma: Fix race condition in done IRQ - ARM: dts: Fix swapped mmc order for omap3 - m68k: fix flatmem memory model setup - net: geneve: check skb is large enough for IPv4/IPv6 header - dmaengine: tegra20: Fix runtime PM imbalance on error - s390/entry: save the caller of psw_idle - arm64: kprobes: Restore local irqflag if kprobes is cancelled - xen-netback: Check for hotplug-status existence before watching - cavium/liquidio: Fix duplicate argument - csky: change a Kconfig symbol name to fix e1000 build error - ia64: fix discontig.c section mismatches - ia64: tools: remove duplicate definition of ia64_mf() on ia64 - x86/crash: Fix crash_setup_memmap_entries() out-of-bounds access - net: hso: fix NULL-deref on disconnect regression - USB: CDC-ACM: fix poison/unpoison imbalance - Linux 5.11.17 * locking/qrwlock: Fix ordering in queued_write_lock_slowpath() (LP: #1926184) - locking/qrwlock: Fix ordering in queued_write_lock_slowpath() * Fix kernel panic at boot on dual GFX systems (LP: #1926792) - drm/amdgpu: Register VGA clients after init can no longer fail * Gigabyte R120-T33 (ARM ThunderX SoC) fails to boot in ACPI mode (LP: #1925075) - ACPI: GTDT: Don't corrupt interrupt mappings on watchdow probe failure * CirrusLogic: Cracking noises appears in built-in speaker when output volume is set >80% (LP: #1924997) - ALSA: hda/cirrus: Use CS8409 filter to fix abnormal sounds on Bullseye * CirrusLogic: The default input volume is "0%" (LP: #1923557) - ALSA: hda/cirrus: Set Initial DMIC volume for Bullseye to -26 dB * Fix no picture from HDMI when it's plugged after boot (LP: #1924238) - drm/i915/display: Handle lane polarity for DDI port * Make AMD gpus choose YCbCr420 encoding automatically when required for 4k 60Hz output (LP: #1922754) - drm/amd/display: Try YCbCr420 color when YCbCr444 fails * Hirsute update: v5.11.16 upstream stable release (LP: #1926999) - AMD_SFH: Removed unused activecontrolstatus member from the amd_mp2_dev struct - AMD_SFH: Add sensor_mask module parameter - AMD_SFH: Add DMI quirk table for BIOS-es which don't set the activestatus bits - mtd: rawnand: mtk: Fix WAITRDY break condition and timeout - Input: nspire-keypad - enable interrupts only when opened - gpio: sysfs: Obey
[Kernel-packages] [Bug 1925386] Re: Upgrade from 460.32.03-0ubuntu2 to 460.73.01-0ubuntu1 fails
This bug was fixed in the package nvidia-graphics-drivers-460 - 460.80-0ubuntu3 --- nvidia-graphics-drivers-460 (460.80-0ubuntu3) impish; urgency=medium * debian/dkms_nvidia/patches/buildfix_kernel_5.13.patch, debian/templates/dkms_nvidia.conf.in: - Add support for Linux 5.13. -- Alberto Milone Wed, 26 May 2021 17:37:16 +0200 ** Changed in: nvidia-graphics-drivers-460 (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-460 in Ubuntu. https://bugs.launchpad.net/bugs/1925386 Title: Upgrade from 460.32.03-0ubuntu2 to 460.73.01-0ubuntu1 fails Status in nvidia-graphics-drivers-460 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-460-server package in Ubuntu: Triaged Status in nvidia-graphics-drivers-460 source package in Bionic: Fix Released Status in nvidia-graphics-drivers-460 source package in Focal: Fix Released Status in nvidia-graphics-drivers-460 source package in Groovy: Fix Released Status in nvidia-graphics-drivers-460 source package in Hirsute: Fix Released Bug description: ubuntu@dgx-1-exotic-skunk-201710-25896:~$ sudo apt install nvidia-dkms-460-server nvidia-utils-460-server Reading package lists... Done Building dependency tree... Done Reading state information... Done The following additional packages will be installed: nvidia-kernel-common-460-server Suggested packages: nvidia-driver-460-server The following packages will be upgraded: nvidia-dkms-460-server nvidia-kernel-common-460-server nvidia-utils-460-server 3 upgraded, 0 newly installed, 0 to remove and 37 not upgraded. Need to get 424 kB of archives. After this operation, 0 B of additional disk space will be used. Do you want to continue? [Y/n] Get:1 http://archive.ubuntu.com/ubuntu hirsute-proposed/restricted amd64 nvidia-dkms-460-server amd64 460.73.01-0ubuntu1 [42.8 kB] Get:2 http://archive.ubuntu.com/ubuntu hirsute-proposed/restricted amd64 nvidia-kernel-common-460-server amd64 460.73.01-0ubuntu1 [18.4 kB] Get:3 http://archive.ubuntu.com/ubuntu hirsute-proposed/restricted amd64 nvidia-utils-460-server amd64 460.73.01-0ubuntu1 [363 kB] Fetched 424 kB in 2s (220 kB/s) (Reading database ... 87065 files and directories currently installed.) Preparing to unpack .../nvidia-dkms-460-server_460.73.01-0ubuntu1_amd64.deb ... Removing all DKMS Modules Done. Unpacking nvidia-dkms-460-server (460.73.01-0ubuntu1) over (460.32.03-0ubuntu2) ... Preparing to unpack .../nvidia-kernel-common-460-server_460.73.01-0ubuntu1_amd64 .deb ... Unpacking nvidia-kernel-common-460-server (460.73.01-0ubuntu1) over (460.32.03-0 ubuntu2) ... Preparing to unpack .../nvidia-utils-460-server_460.73.01-0ubuntu1_amd64.deb ... Unpacking nvidia-utils-460-server (460.73.01-0ubuntu1) over (460.32.03-0ubuntu2) ... Setting up nvidia-kernel-common-460-server (460.73.01-0ubuntu1) ... update-initramfs: deferring update (trigger activated) Setting up nvidia-utils-460-server (460.73.01-0ubuntu1) ... Setting up nvidia-dkms-460-server (460.73.01-0ubuntu1) ... update-initramfs: deferring update (trigger activated) Loading new nvidia-srv-460.73.01 DKMS files... Building for 5.11.0-16-generic Building for architecture x86_64 Building initial module for 5.11.0-16-generic Error! Application of patch disable_fstack-clash-protection_fcf-protection.patch failed. Check /var/lib/dkms/nvidia-srv/460.73.01/build/ for more information. dpkg: error processing package nvidia-dkms-460-server (--configure): installed nvidia-dkms-460-server package post-installation script subprocess re turned error exit status 6 Processing triggers for man-db (2.9.4-2) ... Processing triggers for initramfs-tools (0.139ubuntu3) ... update-initramfs: Generating /boot/initrd.img-5.11.0-16-generic W: Possible missing firmware /lib/firmware/ast_dp501_fw.bin for module ast Errors were encountered while processing: nvidia-dkms-460-server needrestart is being skipped since dpkg has failed E: Sub-process /usr/bin/dpkg returned an error code (1) ubuntu@dgx-1-exotic-skunk-201710-25896:~$ ls /var/lib/dkms/nvidia-srv/460.73.01/build/ dkms.conf patches ubuntu@dgx-1-exotic-skunk-201710-25896:~$ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-460/+bug/1925386/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1912499] Re: Reset upload number to 1 for derivative ABI bumps
This bug was fixed in the package linux-meta - 5.11.0.18.19+21.10.1 --- linux-meta (5.11.0.18.19+21.10.1) impish; urgency=medium * Bump ABI 5.11.0-18.19+21.10 * Reset upload number to 1 for derivative ABI bumps (LP: #1912499) - [Packaging] update-version -- Reset upload number on abi bump * Packaging resync (LP: #1786013) - [Packaging] resync debian/dkms-versions from main package -- Seth Forshee Thu, 13 May 2021 16:08:47 -0500 ** Changed in: linux-meta (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta in Ubuntu. https://bugs.launchpad.net/bugs/1912499 Title: Reset upload number to 1 for derivative ABI bumps Status in linux-meta package in Ubuntu: Fix Released Bug description: [Impact] For derivative kernels we reset the upload number to 1 when bumping the ABI. For the meta packages we just continue to increment the upload number. This at best looks odd and at worst may result in some confusion. Update the scripting in linux-meta to likewise reset the upload number whenever its derivative kernel has done an ABI bump. [Test Case] When preparing a derivative meta package, note that an ABI bump results in the upload number being reset to 1, while subsequent uploads using the same ABI result in incrementing the upload number. [Where problems could occur] This change affects only preparation of derivative meta packages. Bugs could result in having an unexpected upload number in the package version, but any such mistakes should be caught when reviewing package changes prior to upload. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/1912499/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1905466] Re: drm/i915: Drop force_probe requirement for Rocket Lake
This bug was fixed in the package linux - 5.11.0-18.19+21.10.1 --- linux (5.11.0-18.19+21.10.1) impish; urgency=medium * impish/linux: 5.11.0-18.19+21.10.1 -proposed tracker (LP: #1927560) * Packaging resync (LP: #1786013) - [Packaging] update update.conf - update dkms package versions [ Ubuntu: 5.11.0-18.19 ] * hirsute/linux: 5.11.0-18.19 -proposed tracker (LP: #1927578) * Packaging resync (LP: #1786013) - update dkms package versions * Introduce the 465 driver series, fabric-manager, and libnvidia-nscq (LP: #1925522) - debian/dkms-versions -- add NVIDIA 465 and migrate 450 to 460 * linux-image-5.0.0-35-generic breaks checkpointing of container (LP: #1857257) - SAUCE: overlayfs: fix incorrect mnt_id of files opened from map_files * Hirsute update: v5.11.17 upstream stable release (LP: #1927535) - vhost-vdpa: protect concurrent access to vhost device iotlb - Revert "UBUNTU: SAUCE: ovl: Restore vm_file value when lower fs mmap fails" - ovl: fix reference counting in ovl_mmap error path - coda: fix reference counting in coda_file_mmap error path - amd/display: allow non-linear multi-planar formats - drm/amdgpu: reserve fence slot to update page table - drm/amdgpu: fix GCR_GENERAL_CNTL offset for dimgrey_cavefish - gpio: omap: Save and restore sysconfig - KEYS: trusted: Fix TPM reservation for seal/unseal - vdpa/mlx5: Set err = -ENOMEM in case dma_map_sg_attrs fails - pinctrl: lewisburg: Update number of pins in community - block: return -EBUSY when there are open partitions in blkdev_reread_part - pinctrl: core: Show pin numbers for the controllers with base = 0 - arm64: dts: allwinner: Revert SD card CD GPIO for Pine64-LTS - bpf: Allow variable-offset stack access - bpf: Refactor and streamline bounds check into helper - bpf: Tighten speculative pointer arithmetic mask - perf/x86/intel/uncore: Remove uncore extra PCI dev HSWEP_PCI_PCU_3 - perf/x86/kvm: Fix Broadwell Xeon stepping in isolation_ucodes[] - perf auxtrace: Fix potential NULL pointer dereference - perf map: Fix error return code in maps__clone() - HID: google: add don USB id - HID: asus: Add support for 2021 ASUS N-Key keyboard - HID: alps: fix error return code in alps_input_configured() - HID cp2112: fix support for multiple gpiochips - HID: wacom: Assign boolean values to a bool variable - soc: qcom: geni: shield geni_icc_get() for ACPI boot - dmaengine: xilinx: dpdma: Fix descriptor issuing on video group - dmaengine: xilinx: dpdma: Fix race condition in done IRQ - ARM: dts: Fix swapped mmc order for omap3 - m68k: fix flatmem memory model setup - net: geneve: check skb is large enough for IPv4/IPv6 header - dmaengine: tegra20: Fix runtime PM imbalance on error - s390/entry: save the caller of psw_idle - arm64: kprobes: Restore local irqflag if kprobes is cancelled - xen-netback: Check for hotplug-status existence before watching - cavium/liquidio: Fix duplicate argument - csky: change a Kconfig symbol name to fix e1000 build error - ia64: fix discontig.c section mismatches - ia64: tools: remove duplicate definition of ia64_mf() on ia64 - x86/crash: Fix crash_setup_memmap_entries() out-of-bounds access - net: hso: fix NULL-deref on disconnect regression - USB: CDC-ACM: fix poison/unpoison imbalance - Linux 5.11.17 * locking/qrwlock: Fix ordering in queued_write_lock_slowpath() (LP: #1926184) - locking/qrwlock: Fix ordering in queued_write_lock_slowpath() * Fix kernel panic at boot on dual GFX systems (LP: #1926792) - drm/amdgpu: Register VGA clients after init can no longer fail * Gigabyte R120-T33 (ARM ThunderX SoC) fails to boot in ACPI mode (LP: #1925075) - ACPI: GTDT: Don't corrupt interrupt mappings on watchdow probe failure * CirrusLogic: Cracking noises appears in built-in speaker when output volume is set >80% (LP: #1924997) - ALSA: hda/cirrus: Use CS8409 filter to fix abnormal sounds on Bullseye * CirrusLogic: The default input volume is "0%" (LP: #1923557) - ALSA: hda/cirrus: Set Initial DMIC volume for Bullseye to -26 dB * Fix no picture from HDMI when it's plugged after boot (LP: #1924238) - drm/i915/display: Handle lane polarity for DDI port * Make AMD gpus choose YCbCr420 encoding automatically when required for 4k 60Hz output (LP: #1922754) - drm/amd/display: Try YCbCr420 color when YCbCr444 fails * Hirsute update: v5.11.16 upstream stable release (LP: #1926999) - AMD_SFH: Removed unused activecontrolstatus member from the amd_mp2_dev struct - AMD_SFH: Add sensor_mask module parameter - AMD_SFH: Add DMI quirk table for BIOS-es which don't set the activestatus bits - mtd: rawnand: mtk: Fix WAITRDY break condition and timeout - Input: nspire-keypad - enable interrupts only when opened - gpio: sysfs: Obey
[Kernel-packages] [Bug 1927535] Re: Hirsute update: v5.11.17 upstream stable release
This bug was fixed in the package linux - 5.11.0-18.19+21.10.1 --- linux (5.11.0-18.19+21.10.1) impish; urgency=medium * impish/linux: 5.11.0-18.19+21.10.1 -proposed tracker (LP: #1927560) * Packaging resync (LP: #1786013) - [Packaging] update update.conf - update dkms package versions [ Ubuntu: 5.11.0-18.19 ] * hirsute/linux: 5.11.0-18.19 -proposed tracker (LP: #1927578) * Packaging resync (LP: #1786013) - update dkms package versions * Introduce the 465 driver series, fabric-manager, and libnvidia-nscq (LP: #1925522) - debian/dkms-versions -- add NVIDIA 465 and migrate 450 to 460 * linux-image-5.0.0-35-generic breaks checkpointing of container (LP: #1857257) - SAUCE: overlayfs: fix incorrect mnt_id of files opened from map_files * Hirsute update: v5.11.17 upstream stable release (LP: #1927535) - vhost-vdpa: protect concurrent access to vhost device iotlb - Revert "UBUNTU: SAUCE: ovl: Restore vm_file value when lower fs mmap fails" - ovl: fix reference counting in ovl_mmap error path - coda: fix reference counting in coda_file_mmap error path - amd/display: allow non-linear multi-planar formats - drm/amdgpu: reserve fence slot to update page table - drm/amdgpu: fix GCR_GENERAL_CNTL offset for dimgrey_cavefish - gpio: omap: Save and restore sysconfig - KEYS: trusted: Fix TPM reservation for seal/unseal - vdpa/mlx5: Set err = -ENOMEM in case dma_map_sg_attrs fails - pinctrl: lewisburg: Update number of pins in community - block: return -EBUSY when there are open partitions in blkdev_reread_part - pinctrl: core: Show pin numbers for the controllers with base = 0 - arm64: dts: allwinner: Revert SD card CD GPIO for Pine64-LTS - bpf: Allow variable-offset stack access - bpf: Refactor and streamline bounds check into helper - bpf: Tighten speculative pointer arithmetic mask - perf/x86/intel/uncore: Remove uncore extra PCI dev HSWEP_PCI_PCU_3 - perf/x86/kvm: Fix Broadwell Xeon stepping in isolation_ucodes[] - perf auxtrace: Fix potential NULL pointer dereference - perf map: Fix error return code in maps__clone() - HID: google: add don USB id - HID: asus: Add support for 2021 ASUS N-Key keyboard - HID: alps: fix error return code in alps_input_configured() - HID cp2112: fix support for multiple gpiochips - HID: wacom: Assign boolean values to a bool variable - soc: qcom: geni: shield geni_icc_get() for ACPI boot - dmaengine: xilinx: dpdma: Fix descriptor issuing on video group - dmaengine: xilinx: dpdma: Fix race condition in done IRQ - ARM: dts: Fix swapped mmc order for omap3 - m68k: fix flatmem memory model setup - net: geneve: check skb is large enough for IPv4/IPv6 header - dmaengine: tegra20: Fix runtime PM imbalance on error - s390/entry: save the caller of psw_idle - arm64: kprobes: Restore local irqflag if kprobes is cancelled - xen-netback: Check for hotplug-status existence before watching - cavium/liquidio: Fix duplicate argument - csky: change a Kconfig symbol name to fix e1000 build error - ia64: fix discontig.c section mismatches - ia64: tools: remove duplicate definition of ia64_mf() on ia64 - x86/crash: Fix crash_setup_memmap_entries() out-of-bounds access - net: hso: fix NULL-deref on disconnect regression - USB: CDC-ACM: fix poison/unpoison imbalance - Linux 5.11.17 * locking/qrwlock: Fix ordering in queued_write_lock_slowpath() (LP: #1926184) - locking/qrwlock: Fix ordering in queued_write_lock_slowpath() * Fix kernel panic at boot on dual GFX systems (LP: #1926792) - drm/amdgpu: Register VGA clients after init can no longer fail * Gigabyte R120-T33 (ARM ThunderX SoC) fails to boot in ACPI mode (LP: #1925075) - ACPI: GTDT: Don't corrupt interrupt mappings on watchdow probe failure * CirrusLogic: Cracking noises appears in built-in speaker when output volume is set >80% (LP: #1924997) - ALSA: hda/cirrus: Use CS8409 filter to fix abnormal sounds on Bullseye * CirrusLogic: The default input volume is "0%" (LP: #1923557) - ALSA: hda/cirrus: Set Initial DMIC volume for Bullseye to -26 dB * Fix no picture from HDMI when it's plugged after boot (LP: #1924238) - drm/i915/display: Handle lane polarity for DDI port * Make AMD gpus choose YCbCr420 encoding automatically when required for 4k 60Hz output (LP: #1922754) - drm/amd/display: Try YCbCr420 color when YCbCr444 fails * Hirsute update: v5.11.16 upstream stable release (LP: #1926999) - AMD_SFH: Removed unused activecontrolstatus member from the amd_mp2_dev struct - AMD_SFH: Add sensor_mask module parameter - AMD_SFH: Add DMI quirk table for BIOS-es which don't set the activestatus bits - mtd: rawnand: mtk: Fix WAITRDY break condition and timeout - Input: nspire-keypad - enable interrupts only when opened - gpio: sysfs: Obey
[Kernel-packages] [Bug 1926999] Re: Hirsute update: v5.11.16 upstream stable release
This bug was fixed in the package linux - 5.11.0-18.19+21.10.1 --- linux (5.11.0-18.19+21.10.1) impish; urgency=medium * impish/linux: 5.11.0-18.19+21.10.1 -proposed tracker (LP: #1927560) * Packaging resync (LP: #1786013) - [Packaging] update update.conf - update dkms package versions [ Ubuntu: 5.11.0-18.19 ] * hirsute/linux: 5.11.0-18.19 -proposed tracker (LP: #1927578) * Packaging resync (LP: #1786013) - update dkms package versions * Introduce the 465 driver series, fabric-manager, and libnvidia-nscq (LP: #1925522) - debian/dkms-versions -- add NVIDIA 465 and migrate 450 to 460 * linux-image-5.0.0-35-generic breaks checkpointing of container (LP: #1857257) - SAUCE: overlayfs: fix incorrect mnt_id of files opened from map_files * Hirsute update: v5.11.17 upstream stable release (LP: #1927535) - vhost-vdpa: protect concurrent access to vhost device iotlb - Revert "UBUNTU: SAUCE: ovl: Restore vm_file value when lower fs mmap fails" - ovl: fix reference counting in ovl_mmap error path - coda: fix reference counting in coda_file_mmap error path - amd/display: allow non-linear multi-planar formats - drm/amdgpu: reserve fence slot to update page table - drm/amdgpu: fix GCR_GENERAL_CNTL offset for dimgrey_cavefish - gpio: omap: Save and restore sysconfig - KEYS: trusted: Fix TPM reservation for seal/unseal - vdpa/mlx5: Set err = -ENOMEM in case dma_map_sg_attrs fails - pinctrl: lewisburg: Update number of pins in community - block: return -EBUSY when there are open partitions in blkdev_reread_part - pinctrl: core: Show pin numbers for the controllers with base = 0 - arm64: dts: allwinner: Revert SD card CD GPIO for Pine64-LTS - bpf: Allow variable-offset stack access - bpf: Refactor and streamline bounds check into helper - bpf: Tighten speculative pointer arithmetic mask - perf/x86/intel/uncore: Remove uncore extra PCI dev HSWEP_PCI_PCU_3 - perf/x86/kvm: Fix Broadwell Xeon stepping in isolation_ucodes[] - perf auxtrace: Fix potential NULL pointer dereference - perf map: Fix error return code in maps__clone() - HID: google: add don USB id - HID: asus: Add support for 2021 ASUS N-Key keyboard - HID: alps: fix error return code in alps_input_configured() - HID cp2112: fix support for multiple gpiochips - HID: wacom: Assign boolean values to a bool variable - soc: qcom: geni: shield geni_icc_get() for ACPI boot - dmaengine: xilinx: dpdma: Fix descriptor issuing on video group - dmaengine: xilinx: dpdma: Fix race condition in done IRQ - ARM: dts: Fix swapped mmc order for omap3 - m68k: fix flatmem memory model setup - net: geneve: check skb is large enough for IPv4/IPv6 header - dmaengine: tegra20: Fix runtime PM imbalance on error - s390/entry: save the caller of psw_idle - arm64: kprobes: Restore local irqflag if kprobes is cancelled - xen-netback: Check for hotplug-status existence before watching - cavium/liquidio: Fix duplicate argument - csky: change a Kconfig symbol name to fix e1000 build error - ia64: fix discontig.c section mismatches - ia64: tools: remove duplicate definition of ia64_mf() on ia64 - x86/crash: Fix crash_setup_memmap_entries() out-of-bounds access - net: hso: fix NULL-deref on disconnect regression - USB: CDC-ACM: fix poison/unpoison imbalance - Linux 5.11.17 * locking/qrwlock: Fix ordering in queued_write_lock_slowpath() (LP: #1926184) - locking/qrwlock: Fix ordering in queued_write_lock_slowpath() * Fix kernel panic at boot on dual GFX systems (LP: #1926792) - drm/amdgpu: Register VGA clients after init can no longer fail * Gigabyte R120-T33 (ARM ThunderX SoC) fails to boot in ACPI mode (LP: #1925075) - ACPI: GTDT: Don't corrupt interrupt mappings on watchdow probe failure * CirrusLogic: Cracking noises appears in built-in speaker when output volume is set >80% (LP: #1924997) - ALSA: hda/cirrus: Use CS8409 filter to fix abnormal sounds on Bullseye * CirrusLogic: The default input volume is "0%" (LP: #1923557) - ALSA: hda/cirrus: Set Initial DMIC volume for Bullseye to -26 dB * Fix no picture from HDMI when it's plugged after boot (LP: #1924238) - drm/i915/display: Handle lane polarity for DDI port * Make AMD gpus choose YCbCr420 encoding automatically when required for 4k 60Hz output (LP: #1922754) - drm/amd/display: Try YCbCr420 color when YCbCr444 fails * Hirsute update: v5.11.16 upstream stable release (LP: #1926999) - AMD_SFH: Removed unused activecontrolstatus member from the amd_mp2_dev struct - AMD_SFH: Add sensor_mask module parameter - AMD_SFH: Add DMI quirk table for BIOS-es which don't set the activestatus bits - mtd: rawnand: mtk: Fix WAITRDY break condition and timeout - Input: nspire-keypad - enable interrupts only when opened - gpio: sysfs: Obey
[Kernel-packages] [Bug 1924238] Re: Fix no picture from HDMI when it's plugged after boot
This bug was fixed in the package linux - 5.11.0-18.19+21.10.1 --- linux (5.11.0-18.19+21.10.1) impish; urgency=medium * impish/linux: 5.11.0-18.19+21.10.1 -proposed tracker (LP: #1927560) * Packaging resync (LP: #1786013) - [Packaging] update update.conf - update dkms package versions [ Ubuntu: 5.11.0-18.19 ] * hirsute/linux: 5.11.0-18.19 -proposed tracker (LP: #1927578) * Packaging resync (LP: #1786013) - update dkms package versions * Introduce the 465 driver series, fabric-manager, and libnvidia-nscq (LP: #1925522) - debian/dkms-versions -- add NVIDIA 465 and migrate 450 to 460 * linux-image-5.0.0-35-generic breaks checkpointing of container (LP: #1857257) - SAUCE: overlayfs: fix incorrect mnt_id of files opened from map_files * Hirsute update: v5.11.17 upstream stable release (LP: #1927535) - vhost-vdpa: protect concurrent access to vhost device iotlb - Revert "UBUNTU: SAUCE: ovl: Restore vm_file value when lower fs mmap fails" - ovl: fix reference counting in ovl_mmap error path - coda: fix reference counting in coda_file_mmap error path - amd/display: allow non-linear multi-planar formats - drm/amdgpu: reserve fence slot to update page table - drm/amdgpu: fix GCR_GENERAL_CNTL offset for dimgrey_cavefish - gpio: omap: Save and restore sysconfig - KEYS: trusted: Fix TPM reservation for seal/unseal - vdpa/mlx5: Set err = -ENOMEM in case dma_map_sg_attrs fails - pinctrl: lewisburg: Update number of pins in community - block: return -EBUSY when there are open partitions in blkdev_reread_part - pinctrl: core: Show pin numbers for the controllers with base = 0 - arm64: dts: allwinner: Revert SD card CD GPIO for Pine64-LTS - bpf: Allow variable-offset stack access - bpf: Refactor and streamline bounds check into helper - bpf: Tighten speculative pointer arithmetic mask - perf/x86/intel/uncore: Remove uncore extra PCI dev HSWEP_PCI_PCU_3 - perf/x86/kvm: Fix Broadwell Xeon stepping in isolation_ucodes[] - perf auxtrace: Fix potential NULL pointer dereference - perf map: Fix error return code in maps__clone() - HID: google: add don USB id - HID: asus: Add support for 2021 ASUS N-Key keyboard - HID: alps: fix error return code in alps_input_configured() - HID cp2112: fix support for multiple gpiochips - HID: wacom: Assign boolean values to a bool variable - soc: qcom: geni: shield geni_icc_get() for ACPI boot - dmaengine: xilinx: dpdma: Fix descriptor issuing on video group - dmaengine: xilinx: dpdma: Fix race condition in done IRQ - ARM: dts: Fix swapped mmc order for omap3 - m68k: fix flatmem memory model setup - net: geneve: check skb is large enough for IPv4/IPv6 header - dmaengine: tegra20: Fix runtime PM imbalance on error - s390/entry: save the caller of psw_idle - arm64: kprobes: Restore local irqflag if kprobes is cancelled - xen-netback: Check for hotplug-status existence before watching - cavium/liquidio: Fix duplicate argument - csky: change a Kconfig symbol name to fix e1000 build error - ia64: fix discontig.c section mismatches - ia64: tools: remove duplicate definition of ia64_mf() on ia64 - x86/crash: Fix crash_setup_memmap_entries() out-of-bounds access - net: hso: fix NULL-deref on disconnect regression - USB: CDC-ACM: fix poison/unpoison imbalance - Linux 5.11.17 * locking/qrwlock: Fix ordering in queued_write_lock_slowpath() (LP: #1926184) - locking/qrwlock: Fix ordering in queued_write_lock_slowpath() * Fix kernel panic at boot on dual GFX systems (LP: #1926792) - drm/amdgpu: Register VGA clients after init can no longer fail * Gigabyte R120-T33 (ARM ThunderX SoC) fails to boot in ACPI mode (LP: #1925075) - ACPI: GTDT: Don't corrupt interrupt mappings on watchdow probe failure * CirrusLogic: Cracking noises appears in built-in speaker when output volume is set >80% (LP: #1924997) - ALSA: hda/cirrus: Use CS8409 filter to fix abnormal sounds on Bullseye * CirrusLogic: The default input volume is "0%" (LP: #1923557) - ALSA: hda/cirrus: Set Initial DMIC volume for Bullseye to -26 dB * Fix no picture from HDMI when it's plugged after boot (LP: #1924238) - drm/i915/display: Handle lane polarity for DDI port * Make AMD gpus choose YCbCr420 encoding automatically when required for 4k 60Hz output (LP: #1922754) - drm/amd/display: Try YCbCr420 color when YCbCr444 fails * Hirsute update: v5.11.16 upstream stable release (LP: #1926999) - AMD_SFH: Removed unused activecontrolstatus member from the amd_mp2_dev struct - AMD_SFH: Add sensor_mask module parameter - AMD_SFH: Add DMI quirk table for BIOS-es which don't set the activestatus bits - mtd: rawnand: mtk: Fix WAITRDY break condition and timeout - Input: nspire-keypad - enable interrupts only when opened - gpio: sysfs: Obey
[Kernel-packages] [Bug 1925075] Re: Gigabyte R120-T33 (ARM ThunderX SoC) fails to boot in ACPI mode
This bug was fixed in the package linux - 5.11.0-18.19+21.10.1 --- linux (5.11.0-18.19+21.10.1) impish; urgency=medium * impish/linux: 5.11.0-18.19+21.10.1 -proposed tracker (LP: #1927560) * Packaging resync (LP: #1786013) - [Packaging] update update.conf - update dkms package versions [ Ubuntu: 5.11.0-18.19 ] * hirsute/linux: 5.11.0-18.19 -proposed tracker (LP: #1927578) * Packaging resync (LP: #1786013) - update dkms package versions * Introduce the 465 driver series, fabric-manager, and libnvidia-nscq (LP: #1925522) - debian/dkms-versions -- add NVIDIA 465 and migrate 450 to 460 * linux-image-5.0.0-35-generic breaks checkpointing of container (LP: #1857257) - SAUCE: overlayfs: fix incorrect mnt_id of files opened from map_files * Hirsute update: v5.11.17 upstream stable release (LP: #1927535) - vhost-vdpa: protect concurrent access to vhost device iotlb - Revert "UBUNTU: SAUCE: ovl: Restore vm_file value when lower fs mmap fails" - ovl: fix reference counting in ovl_mmap error path - coda: fix reference counting in coda_file_mmap error path - amd/display: allow non-linear multi-planar formats - drm/amdgpu: reserve fence slot to update page table - drm/amdgpu: fix GCR_GENERAL_CNTL offset for dimgrey_cavefish - gpio: omap: Save and restore sysconfig - KEYS: trusted: Fix TPM reservation for seal/unseal - vdpa/mlx5: Set err = -ENOMEM in case dma_map_sg_attrs fails - pinctrl: lewisburg: Update number of pins in community - block: return -EBUSY when there are open partitions in blkdev_reread_part - pinctrl: core: Show pin numbers for the controllers with base = 0 - arm64: dts: allwinner: Revert SD card CD GPIO for Pine64-LTS - bpf: Allow variable-offset stack access - bpf: Refactor and streamline bounds check into helper - bpf: Tighten speculative pointer arithmetic mask - perf/x86/intel/uncore: Remove uncore extra PCI dev HSWEP_PCI_PCU_3 - perf/x86/kvm: Fix Broadwell Xeon stepping in isolation_ucodes[] - perf auxtrace: Fix potential NULL pointer dereference - perf map: Fix error return code in maps__clone() - HID: google: add don USB id - HID: asus: Add support for 2021 ASUS N-Key keyboard - HID: alps: fix error return code in alps_input_configured() - HID cp2112: fix support for multiple gpiochips - HID: wacom: Assign boolean values to a bool variable - soc: qcom: geni: shield geni_icc_get() for ACPI boot - dmaengine: xilinx: dpdma: Fix descriptor issuing on video group - dmaengine: xilinx: dpdma: Fix race condition in done IRQ - ARM: dts: Fix swapped mmc order for omap3 - m68k: fix flatmem memory model setup - net: geneve: check skb is large enough for IPv4/IPv6 header - dmaengine: tegra20: Fix runtime PM imbalance on error - s390/entry: save the caller of psw_idle - arm64: kprobes: Restore local irqflag if kprobes is cancelled - xen-netback: Check for hotplug-status existence before watching - cavium/liquidio: Fix duplicate argument - csky: change a Kconfig symbol name to fix e1000 build error - ia64: fix discontig.c section mismatches - ia64: tools: remove duplicate definition of ia64_mf() on ia64 - x86/crash: Fix crash_setup_memmap_entries() out-of-bounds access - net: hso: fix NULL-deref on disconnect regression - USB: CDC-ACM: fix poison/unpoison imbalance - Linux 5.11.17 * locking/qrwlock: Fix ordering in queued_write_lock_slowpath() (LP: #1926184) - locking/qrwlock: Fix ordering in queued_write_lock_slowpath() * Fix kernel panic at boot on dual GFX systems (LP: #1926792) - drm/amdgpu: Register VGA clients after init can no longer fail * Gigabyte R120-T33 (ARM ThunderX SoC) fails to boot in ACPI mode (LP: #1925075) - ACPI: GTDT: Don't corrupt interrupt mappings on watchdow probe failure * CirrusLogic: Cracking noises appears in built-in speaker when output volume is set >80% (LP: #1924997) - ALSA: hda/cirrus: Use CS8409 filter to fix abnormal sounds on Bullseye * CirrusLogic: The default input volume is "0%" (LP: #1923557) - ALSA: hda/cirrus: Set Initial DMIC volume for Bullseye to -26 dB * Fix no picture from HDMI when it's plugged after boot (LP: #1924238) - drm/i915/display: Handle lane polarity for DDI port * Make AMD gpus choose YCbCr420 encoding automatically when required for 4k 60Hz output (LP: #1922754) - drm/amd/display: Try YCbCr420 color when YCbCr444 fails * Hirsute update: v5.11.16 upstream stable release (LP: #1926999) - AMD_SFH: Removed unused activecontrolstatus member from the amd_mp2_dev struct - AMD_SFH: Add sensor_mask module parameter - AMD_SFH: Add DMI quirk table for BIOS-es which don't set the activestatus bits - mtd: rawnand: mtk: Fix WAITRDY break condition and timeout - Input: nspire-keypad - enable interrupts only when opened - gpio: sysfs: Obey
[Kernel-packages] [Bug 1925522] Re: Introduce the 465 driver series, fabric-manager, and libnvidia-nscq
This bug was fixed in the package nvidia-graphics-drivers-450-server - 450.119.04-0ubuntu3 --- nvidia-graphics-drivers-450-server (450.119.04-0ubuntu3) impish; urgency=medium * debian/dkms_nvidia/patches/buildfix_kernel_5.13.patch, debian/templates/dkms_nvidia.conf.in: - Add support for Linux 5.13. -- Alberto Milone Thu, 27 May 2021 12:42:41 +0200 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-460 in Ubuntu. https://bugs.launchpad.net/bugs/1925522 Title: Introduce the 465 driver series, fabric-manager, and libnvidia-nscq Status in fabric-manager-450 package in Ubuntu: Fix Released Status in fabric-manager-460 package in Ubuntu: Fix Released Status in libnvidia-nscq-450 package in Ubuntu: Fix Released Status in libnvidia-nscq-460 package in Ubuntu: Fix Released Status in linux-restricted-modules package in Ubuntu: In Progress Status in nvidia-graphics-drivers-450-server package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-460 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-465 package in Ubuntu: Fix Released Status in nvidia-settings package in Ubuntu: In Progress Status in fabric-manager-450 source package in Bionic: Fix Released Status in fabric-manager-460 source package in Bionic: Fix Released Status in libnvidia-nscq-450 source package in Bionic: Fix Released Status in libnvidia-nscq-460 source package in Bionic: Fix Released Status in linux-restricted-modules source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-450-server source package in Bionic: Fix Released Status in nvidia-graphics-drivers-460 source package in Bionic: Fix Released Status in nvidia-graphics-drivers-465 source package in Bionic: Fix Released Status in nvidia-settings source package in Bionic: Fix Committed Status in fabric-manager-450 source package in Focal: Fix Released Status in fabric-manager-460 source package in Focal: Fix Released Status in libnvidia-nscq-450 source package in Focal: Fix Released Status in libnvidia-nscq-460 source package in Focal: Fix Released Status in linux-restricted-modules source package in Focal: Fix Committed Status in nvidia-graphics-drivers-450-server source package in Focal: Fix Released Status in nvidia-graphics-drivers-460 source package in Focal: Fix Released Status in nvidia-graphics-drivers-465 source package in Focal: Fix Released Status in nvidia-settings source package in Focal: Fix Committed Status in fabric-manager-450 source package in Groovy: Fix Committed Status in fabric-manager-460 source package in Groovy: Fix Committed Status in libnvidia-nscq-450 source package in Groovy: Fix Committed Status in libnvidia-nscq-460 source package in Groovy: Fix Committed Status in linux-restricted-modules source package in Groovy: Fix Committed Status in nvidia-graphics-drivers-450-server source package in Groovy: Fix Released Status in nvidia-graphics-drivers-460 source package in Groovy: Fix Released Status in nvidia-graphics-drivers-465 source package in Groovy: Fix Released Status in nvidia-settings source package in Groovy: Fix Committed Status in fabric-manager-450 source package in Hirsute: Fix Released Status in fabric-manager-460 source package in Hirsute: Fix Released Status in libnvidia-nscq-450 source package in Hirsute: Fix Released Status in libnvidia-nscq-460 source package in Hirsute: Fix Released Status in linux-restricted-modules source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-450-server source package in Hirsute: Fix Released Status in nvidia-graphics-drivers-460 source package in Hirsute: Fix Released Status in nvidia-graphics-drivers-465 source package in Hirsute: Fix Released Status in nvidia-settings source package in Hirsute: Fix Committed Bug description: Introduce the new NVIDIA 465 driver series, fabric-manager and libnvidia-nscq. Also migrate the UDA 450 series to the 460 series. [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] [Changelog] == 450-server == *
[Kernel-packages] [Bug 1926368] Re: Hirsute update: v5.11.14 upstream stable release
This bug was fixed in the package linux - 5.11.0-18.19+21.10.1 --- linux (5.11.0-18.19+21.10.1) impish; urgency=medium * impish/linux: 5.11.0-18.19+21.10.1 -proposed tracker (LP: #1927560) * Packaging resync (LP: #1786013) - [Packaging] update update.conf - update dkms package versions [ Ubuntu: 5.11.0-18.19 ] * hirsute/linux: 5.11.0-18.19 -proposed tracker (LP: #1927578) * Packaging resync (LP: #1786013) - update dkms package versions * Introduce the 465 driver series, fabric-manager, and libnvidia-nscq (LP: #1925522) - debian/dkms-versions -- add NVIDIA 465 and migrate 450 to 460 * linux-image-5.0.0-35-generic breaks checkpointing of container (LP: #1857257) - SAUCE: overlayfs: fix incorrect mnt_id of files opened from map_files * Hirsute update: v5.11.17 upstream stable release (LP: #1927535) - vhost-vdpa: protect concurrent access to vhost device iotlb - Revert "UBUNTU: SAUCE: ovl: Restore vm_file value when lower fs mmap fails" - ovl: fix reference counting in ovl_mmap error path - coda: fix reference counting in coda_file_mmap error path - amd/display: allow non-linear multi-planar formats - drm/amdgpu: reserve fence slot to update page table - drm/amdgpu: fix GCR_GENERAL_CNTL offset for dimgrey_cavefish - gpio: omap: Save and restore sysconfig - KEYS: trusted: Fix TPM reservation for seal/unseal - vdpa/mlx5: Set err = -ENOMEM in case dma_map_sg_attrs fails - pinctrl: lewisburg: Update number of pins in community - block: return -EBUSY when there are open partitions in blkdev_reread_part - pinctrl: core: Show pin numbers for the controllers with base = 0 - arm64: dts: allwinner: Revert SD card CD GPIO for Pine64-LTS - bpf: Allow variable-offset stack access - bpf: Refactor and streamline bounds check into helper - bpf: Tighten speculative pointer arithmetic mask - perf/x86/intel/uncore: Remove uncore extra PCI dev HSWEP_PCI_PCU_3 - perf/x86/kvm: Fix Broadwell Xeon stepping in isolation_ucodes[] - perf auxtrace: Fix potential NULL pointer dereference - perf map: Fix error return code in maps__clone() - HID: google: add don USB id - HID: asus: Add support for 2021 ASUS N-Key keyboard - HID: alps: fix error return code in alps_input_configured() - HID cp2112: fix support for multiple gpiochips - HID: wacom: Assign boolean values to a bool variable - soc: qcom: geni: shield geni_icc_get() for ACPI boot - dmaengine: xilinx: dpdma: Fix descriptor issuing on video group - dmaengine: xilinx: dpdma: Fix race condition in done IRQ - ARM: dts: Fix swapped mmc order for omap3 - m68k: fix flatmem memory model setup - net: geneve: check skb is large enough for IPv4/IPv6 header - dmaengine: tegra20: Fix runtime PM imbalance on error - s390/entry: save the caller of psw_idle - arm64: kprobes: Restore local irqflag if kprobes is cancelled - xen-netback: Check for hotplug-status existence before watching - cavium/liquidio: Fix duplicate argument - csky: change a Kconfig symbol name to fix e1000 build error - ia64: fix discontig.c section mismatches - ia64: tools: remove duplicate definition of ia64_mf() on ia64 - x86/crash: Fix crash_setup_memmap_entries() out-of-bounds access - net: hso: fix NULL-deref on disconnect regression - USB: CDC-ACM: fix poison/unpoison imbalance - Linux 5.11.17 * locking/qrwlock: Fix ordering in queued_write_lock_slowpath() (LP: #1926184) - locking/qrwlock: Fix ordering in queued_write_lock_slowpath() * Fix kernel panic at boot on dual GFX systems (LP: #1926792) - drm/amdgpu: Register VGA clients after init can no longer fail * Gigabyte R120-T33 (ARM ThunderX SoC) fails to boot in ACPI mode (LP: #1925075) - ACPI: GTDT: Don't corrupt interrupt mappings on watchdow probe failure * CirrusLogic: Cracking noises appears in built-in speaker when output volume is set >80% (LP: #1924997) - ALSA: hda/cirrus: Use CS8409 filter to fix abnormal sounds on Bullseye * CirrusLogic: The default input volume is "0%" (LP: #1923557) - ALSA: hda/cirrus: Set Initial DMIC volume for Bullseye to -26 dB * Fix no picture from HDMI when it's plugged after boot (LP: #1924238) - drm/i915/display: Handle lane polarity for DDI port * Make AMD gpus choose YCbCr420 encoding automatically when required for 4k 60Hz output (LP: #1922754) - drm/amd/display: Try YCbCr420 color when YCbCr444 fails * Hirsute update: v5.11.16 upstream stable release (LP: #1926999) - AMD_SFH: Removed unused activecontrolstatus member from the amd_mp2_dev struct - AMD_SFH: Add sensor_mask module parameter - AMD_SFH: Add DMI quirk table for BIOS-es which don't set the activestatus bits - mtd: rawnand: mtk: Fix WAITRDY break condition and timeout - Input: nspire-keypad - enable interrupts only when opened - gpio: sysfs: Obey
[Kernel-packages] [Bug 1926184] Re: locking/qrwlock: Fix ordering in queued_write_lock_slowpath()
This bug was fixed in the package linux - 5.11.0-18.19+21.10.1 --- linux (5.11.0-18.19+21.10.1) impish; urgency=medium * impish/linux: 5.11.0-18.19+21.10.1 -proposed tracker (LP: #1927560) * Packaging resync (LP: #1786013) - [Packaging] update update.conf - update dkms package versions [ Ubuntu: 5.11.0-18.19 ] * hirsute/linux: 5.11.0-18.19 -proposed tracker (LP: #1927578) * Packaging resync (LP: #1786013) - update dkms package versions * Introduce the 465 driver series, fabric-manager, and libnvidia-nscq (LP: #1925522) - debian/dkms-versions -- add NVIDIA 465 and migrate 450 to 460 * linux-image-5.0.0-35-generic breaks checkpointing of container (LP: #1857257) - SAUCE: overlayfs: fix incorrect mnt_id of files opened from map_files * Hirsute update: v5.11.17 upstream stable release (LP: #1927535) - vhost-vdpa: protect concurrent access to vhost device iotlb - Revert "UBUNTU: SAUCE: ovl: Restore vm_file value when lower fs mmap fails" - ovl: fix reference counting in ovl_mmap error path - coda: fix reference counting in coda_file_mmap error path - amd/display: allow non-linear multi-planar formats - drm/amdgpu: reserve fence slot to update page table - drm/amdgpu: fix GCR_GENERAL_CNTL offset for dimgrey_cavefish - gpio: omap: Save and restore sysconfig - KEYS: trusted: Fix TPM reservation for seal/unseal - vdpa/mlx5: Set err = -ENOMEM in case dma_map_sg_attrs fails - pinctrl: lewisburg: Update number of pins in community - block: return -EBUSY when there are open partitions in blkdev_reread_part - pinctrl: core: Show pin numbers for the controllers with base = 0 - arm64: dts: allwinner: Revert SD card CD GPIO for Pine64-LTS - bpf: Allow variable-offset stack access - bpf: Refactor and streamline bounds check into helper - bpf: Tighten speculative pointer arithmetic mask - perf/x86/intel/uncore: Remove uncore extra PCI dev HSWEP_PCI_PCU_3 - perf/x86/kvm: Fix Broadwell Xeon stepping in isolation_ucodes[] - perf auxtrace: Fix potential NULL pointer dereference - perf map: Fix error return code in maps__clone() - HID: google: add don USB id - HID: asus: Add support for 2021 ASUS N-Key keyboard - HID: alps: fix error return code in alps_input_configured() - HID cp2112: fix support for multiple gpiochips - HID: wacom: Assign boolean values to a bool variable - soc: qcom: geni: shield geni_icc_get() for ACPI boot - dmaengine: xilinx: dpdma: Fix descriptor issuing on video group - dmaengine: xilinx: dpdma: Fix race condition in done IRQ - ARM: dts: Fix swapped mmc order for omap3 - m68k: fix flatmem memory model setup - net: geneve: check skb is large enough for IPv4/IPv6 header - dmaengine: tegra20: Fix runtime PM imbalance on error - s390/entry: save the caller of psw_idle - arm64: kprobes: Restore local irqflag if kprobes is cancelled - xen-netback: Check for hotplug-status existence before watching - cavium/liquidio: Fix duplicate argument - csky: change a Kconfig symbol name to fix e1000 build error - ia64: fix discontig.c section mismatches - ia64: tools: remove duplicate definition of ia64_mf() on ia64 - x86/crash: Fix crash_setup_memmap_entries() out-of-bounds access - net: hso: fix NULL-deref on disconnect regression - USB: CDC-ACM: fix poison/unpoison imbalance - Linux 5.11.17 * locking/qrwlock: Fix ordering in queued_write_lock_slowpath() (LP: #1926184) - locking/qrwlock: Fix ordering in queued_write_lock_slowpath() * Fix kernel panic at boot on dual GFX systems (LP: #1926792) - drm/amdgpu: Register VGA clients after init can no longer fail * Gigabyte R120-T33 (ARM ThunderX SoC) fails to boot in ACPI mode (LP: #1925075) - ACPI: GTDT: Don't corrupt interrupt mappings on watchdow probe failure * CirrusLogic: Cracking noises appears in built-in speaker when output volume is set >80% (LP: #1924997) - ALSA: hda/cirrus: Use CS8409 filter to fix abnormal sounds on Bullseye * CirrusLogic: The default input volume is "0%" (LP: #1923557) - ALSA: hda/cirrus: Set Initial DMIC volume for Bullseye to -26 dB * Fix no picture from HDMI when it's plugged after boot (LP: #1924238) - drm/i915/display: Handle lane polarity for DDI port * Make AMD gpus choose YCbCr420 encoding automatically when required for 4k 60Hz output (LP: #1922754) - drm/amd/display: Try YCbCr420 color when YCbCr444 fails * Hirsute update: v5.11.16 upstream stable release (LP: #1926999) - AMD_SFH: Removed unused activecontrolstatus member from the amd_mp2_dev struct - AMD_SFH: Add sensor_mask module parameter - AMD_SFH: Add DMI quirk table for BIOS-es which don't set the activestatus bits - mtd: rawnand: mtk: Fix WAITRDY break condition and timeout - Input: nspire-keypad - enable interrupts only when opened - gpio: sysfs: Obey
[Kernel-packages] [Bug 1926184] Re: locking/qrwlock: Fix ordering in queued_write_lock_slowpath()
This bug was fixed in the package linux-aws - 5.11.0-1008.8+21.10.1
---
linux-aws (5.11.0-1008.8+21.10.1) impish; urgency=medium
* impish/linux-aws: 5.11.0-1008.8+21.10.1 -proposed tracker (LP:
#1927561)
* Packaging resync (LP: #1786013)
- [Packaging] update update.conf
-- Tim Gardner Thu, 20 May 2021 13:54:07
-0600
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-aws in Ubuntu.
https://bugs.launchpad.net/bugs/1926184
Title:
locking/qrwlock: Fix ordering in queued_write_lock_slowpath()
Status in linux package in Ubuntu:
Fix Released
Status in linux-aws package in Ubuntu:
Fix Released
Status in linux source package in Bionic:
Fix Released
Status in linux-aws source package in Bionic:
Fix Released
Status in linux source package in Focal:
Fix Released
Status in linux-aws source package in Focal:
Fix Released
Status in linux source package in Groovy:
Fix Released
Status in linux-aws source package in Groovy:
Fix Released
Status in linux source package in Hirsute:
Fix Released
Status in linux-aws source package in Hirsute:
Fix Released
Bug description:
[Impact]
* Out of order reads can fetch a NULL pointer causing a kernel crash. Affects
kernels from v4.15 to v5.11.
[Fix]
* commit 84a24bf8c52e ("locking/qrwlock: Fix ordering in
queued_write_lock_slowpath()")
* For Bionic, we also require an additional patch: commit fcfdfe30e324
("locking/barriers: Introduce smp_cond_load_relaxed() and
atomic_cond_read_relaxed()")
[Where problems could occur]
* This is quite a subtle bug. It is more prevalent on arm64. Regression
possibility seems quite low. The worst impact could be a minor performance
degradation.
* Kernels 4.15 / 5.4 / 5.8 / 5.11 were successfully built and booted
with this patch. Also, by using ftrace we could see that the changed
function was executed with success multiple times.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1926184/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1925539] Re: ftrace synthetic_events selftests failure in 5.11
This bug was fixed in the package linux - 5.11.0-18.19+21.10.1 --- linux (5.11.0-18.19+21.10.1) impish; urgency=medium * impish/linux: 5.11.0-18.19+21.10.1 -proposed tracker (LP: #1927560) * Packaging resync (LP: #1786013) - [Packaging] update update.conf - update dkms package versions [ Ubuntu: 5.11.0-18.19 ] * hirsute/linux: 5.11.0-18.19 -proposed tracker (LP: #1927578) * Packaging resync (LP: #1786013) - update dkms package versions * Introduce the 465 driver series, fabric-manager, and libnvidia-nscq (LP: #1925522) - debian/dkms-versions -- add NVIDIA 465 and migrate 450 to 460 * linux-image-5.0.0-35-generic breaks checkpointing of container (LP: #1857257) - SAUCE: overlayfs: fix incorrect mnt_id of files opened from map_files * Hirsute update: v5.11.17 upstream stable release (LP: #1927535) - vhost-vdpa: protect concurrent access to vhost device iotlb - Revert "UBUNTU: SAUCE: ovl: Restore vm_file value when lower fs mmap fails" - ovl: fix reference counting in ovl_mmap error path - coda: fix reference counting in coda_file_mmap error path - amd/display: allow non-linear multi-planar formats - drm/amdgpu: reserve fence slot to update page table - drm/amdgpu: fix GCR_GENERAL_CNTL offset for dimgrey_cavefish - gpio: omap: Save and restore sysconfig - KEYS: trusted: Fix TPM reservation for seal/unseal - vdpa/mlx5: Set err = -ENOMEM in case dma_map_sg_attrs fails - pinctrl: lewisburg: Update number of pins in community - block: return -EBUSY when there are open partitions in blkdev_reread_part - pinctrl: core: Show pin numbers for the controllers with base = 0 - arm64: dts: allwinner: Revert SD card CD GPIO for Pine64-LTS - bpf: Allow variable-offset stack access - bpf: Refactor and streamline bounds check into helper - bpf: Tighten speculative pointer arithmetic mask - perf/x86/intel/uncore: Remove uncore extra PCI dev HSWEP_PCI_PCU_3 - perf/x86/kvm: Fix Broadwell Xeon stepping in isolation_ucodes[] - perf auxtrace: Fix potential NULL pointer dereference - perf map: Fix error return code in maps__clone() - HID: google: add don USB id - HID: asus: Add support for 2021 ASUS N-Key keyboard - HID: alps: fix error return code in alps_input_configured() - HID cp2112: fix support for multiple gpiochips - HID: wacom: Assign boolean values to a bool variable - soc: qcom: geni: shield geni_icc_get() for ACPI boot - dmaengine: xilinx: dpdma: Fix descriptor issuing on video group - dmaengine: xilinx: dpdma: Fix race condition in done IRQ - ARM: dts: Fix swapped mmc order for omap3 - m68k: fix flatmem memory model setup - net: geneve: check skb is large enough for IPv4/IPv6 header - dmaengine: tegra20: Fix runtime PM imbalance on error - s390/entry: save the caller of psw_idle - arm64: kprobes: Restore local irqflag if kprobes is cancelled - xen-netback: Check for hotplug-status existence before watching - cavium/liquidio: Fix duplicate argument - csky: change a Kconfig symbol name to fix e1000 build error - ia64: fix discontig.c section mismatches - ia64: tools: remove duplicate definition of ia64_mf() on ia64 - x86/crash: Fix crash_setup_memmap_entries() out-of-bounds access - net: hso: fix NULL-deref on disconnect regression - USB: CDC-ACM: fix poison/unpoison imbalance - Linux 5.11.17 * locking/qrwlock: Fix ordering in queued_write_lock_slowpath() (LP: #1926184) - locking/qrwlock: Fix ordering in queued_write_lock_slowpath() * Fix kernel panic at boot on dual GFX systems (LP: #1926792) - drm/amdgpu: Register VGA clients after init can no longer fail * Gigabyte R120-T33 (ARM ThunderX SoC) fails to boot in ACPI mode (LP: #1925075) - ACPI: GTDT: Don't corrupt interrupt mappings on watchdow probe failure * CirrusLogic: Cracking noises appears in built-in speaker when output volume is set >80% (LP: #1924997) - ALSA: hda/cirrus: Use CS8409 filter to fix abnormal sounds on Bullseye * CirrusLogic: The default input volume is "0%" (LP: #1923557) - ALSA: hda/cirrus: Set Initial DMIC volume for Bullseye to -26 dB * Fix no picture from HDMI when it's plugged after boot (LP: #1924238) - drm/i915/display: Handle lane polarity for DDI port * Make AMD gpus choose YCbCr420 encoding automatically when required for 4k 60Hz output (LP: #1922754) - drm/amd/display: Try YCbCr420 color when YCbCr444 fails * Hirsute update: v5.11.16 upstream stable release (LP: #1926999) - AMD_SFH: Removed unused activecontrolstatus member from the amd_mp2_dev struct - AMD_SFH: Add sensor_mask module parameter - AMD_SFH: Add DMI quirk table for BIOS-es which don't set the activestatus bits - mtd: rawnand: mtk: Fix WAITRDY break condition and timeout - Input: nspire-keypad - enable interrupts only when opened - gpio: sysfs: Obey
[Kernel-packages] [Bug 1922754] Re: Make AMD gpus choose YCbCr420 encoding automatically when required for 4k 60Hz output
This bug was fixed in the package linux - 5.11.0-18.19+21.10.1 --- linux (5.11.0-18.19+21.10.1) impish; urgency=medium * impish/linux: 5.11.0-18.19+21.10.1 -proposed tracker (LP: #1927560) * Packaging resync (LP: #1786013) - [Packaging] update update.conf - update dkms package versions [ Ubuntu: 5.11.0-18.19 ] * hirsute/linux: 5.11.0-18.19 -proposed tracker (LP: #1927578) * Packaging resync (LP: #1786013) - update dkms package versions * Introduce the 465 driver series, fabric-manager, and libnvidia-nscq (LP: #1925522) - debian/dkms-versions -- add NVIDIA 465 and migrate 450 to 460 * linux-image-5.0.0-35-generic breaks checkpointing of container (LP: #1857257) - SAUCE: overlayfs: fix incorrect mnt_id of files opened from map_files * Hirsute update: v5.11.17 upstream stable release (LP: #1927535) - vhost-vdpa: protect concurrent access to vhost device iotlb - Revert "UBUNTU: SAUCE: ovl: Restore vm_file value when lower fs mmap fails" - ovl: fix reference counting in ovl_mmap error path - coda: fix reference counting in coda_file_mmap error path - amd/display: allow non-linear multi-planar formats - drm/amdgpu: reserve fence slot to update page table - drm/amdgpu: fix GCR_GENERAL_CNTL offset for dimgrey_cavefish - gpio: omap: Save and restore sysconfig - KEYS: trusted: Fix TPM reservation for seal/unseal - vdpa/mlx5: Set err = -ENOMEM in case dma_map_sg_attrs fails - pinctrl: lewisburg: Update number of pins in community - block: return -EBUSY when there are open partitions in blkdev_reread_part - pinctrl: core: Show pin numbers for the controllers with base = 0 - arm64: dts: allwinner: Revert SD card CD GPIO for Pine64-LTS - bpf: Allow variable-offset stack access - bpf: Refactor and streamline bounds check into helper - bpf: Tighten speculative pointer arithmetic mask - perf/x86/intel/uncore: Remove uncore extra PCI dev HSWEP_PCI_PCU_3 - perf/x86/kvm: Fix Broadwell Xeon stepping in isolation_ucodes[] - perf auxtrace: Fix potential NULL pointer dereference - perf map: Fix error return code in maps__clone() - HID: google: add don USB id - HID: asus: Add support for 2021 ASUS N-Key keyboard - HID: alps: fix error return code in alps_input_configured() - HID cp2112: fix support for multiple gpiochips - HID: wacom: Assign boolean values to a bool variable - soc: qcom: geni: shield geni_icc_get() for ACPI boot - dmaengine: xilinx: dpdma: Fix descriptor issuing on video group - dmaengine: xilinx: dpdma: Fix race condition in done IRQ - ARM: dts: Fix swapped mmc order for omap3 - m68k: fix flatmem memory model setup - net: geneve: check skb is large enough for IPv4/IPv6 header - dmaengine: tegra20: Fix runtime PM imbalance on error - s390/entry: save the caller of psw_idle - arm64: kprobes: Restore local irqflag if kprobes is cancelled - xen-netback: Check for hotplug-status existence before watching - cavium/liquidio: Fix duplicate argument - csky: change a Kconfig symbol name to fix e1000 build error - ia64: fix discontig.c section mismatches - ia64: tools: remove duplicate definition of ia64_mf() on ia64 - x86/crash: Fix crash_setup_memmap_entries() out-of-bounds access - net: hso: fix NULL-deref on disconnect regression - USB: CDC-ACM: fix poison/unpoison imbalance - Linux 5.11.17 * locking/qrwlock: Fix ordering in queued_write_lock_slowpath() (LP: #1926184) - locking/qrwlock: Fix ordering in queued_write_lock_slowpath() * Fix kernel panic at boot on dual GFX systems (LP: #1926792) - drm/amdgpu: Register VGA clients after init can no longer fail * Gigabyte R120-T33 (ARM ThunderX SoC) fails to boot in ACPI mode (LP: #1925075) - ACPI: GTDT: Don't corrupt interrupt mappings on watchdow probe failure * CirrusLogic: Cracking noises appears in built-in speaker when output volume is set >80% (LP: #1924997) - ALSA: hda/cirrus: Use CS8409 filter to fix abnormal sounds on Bullseye * CirrusLogic: The default input volume is "0%" (LP: #1923557) - ALSA: hda/cirrus: Set Initial DMIC volume for Bullseye to -26 dB * Fix no picture from HDMI when it's plugged after boot (LP: #1924238) - drm/i915/display: Handle lane polarity for DDI port * Make AMD gpus choose YCbCr420 encoding automatically when required for 4k 60Hz output (LP: #1922754) - drm/amd/display: Try YCbCr420 color when YCbCr444 fails * Hirsute update: v5.11.16 upstream stable release (LP: #1926999) - AMD_SFH: Removed unused activecontrolstatus member from the amd_mp2_dev struct - AMD_SFH: Add sensor_mask module parameter - AMD_SFH: Add DMI quirk table for BIOS-es which don't set the activestatus bits - mtd: rawnand: mtk: Fix WAITRDY break condition and timeout - Input: nspire-keypad - enable interrupts only when opened - gpio: sysfs: Obey
[Kernel-packages] [Bug 1925522] Re: Introduce the 465 driver series, fabric-manager, and libnvidia-nscq
This bug was fixed in the package nvidia-graphics-drivers-460 - 460.80-0ubuntu3 --- nvidia-graphics-drivers-460 (460.80-0ubuntu3) impish; urgency=medium * debian/dkms_nvidia/patches/buildfix_kernel_5.13.patch, debian/templates/dkms_nvidia.conf.in: - Add support for Linux 5.13. -- Alberto Milone Wed, 26 May 2021 17:37:16 +0200 ** Changed in: nvidia-graphics-drivers-460 (Ubuntu) Status: In Progress => Fix Released ** Changed in: nvidia-graphics-drivers-450-server (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-460 in Ubuntu. https://bugs.launchpad.net/bugs/1925522 Title: Introduce the 465 driver series, fabric-manager, and libnvidia-nscq Status in fabric-manager-450 package in Ubuntu: Fix Released Status in fabric-manager-460 package in Ubuntu: Fix Released Status in libnvidia-nscq-450 package in Ubuntu: Fix Released Status in libnvidia-nscq-460 package in Ubuntu: Fix Released Status in linux-restricted-modules package in Ubuntu: In Progress Status in nvidia-graphics-drivers-450-server package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-460 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-465 package in Ubuntu: Fix Released Status in nvidia-settings package in Ubuntu: In Progress Status in fabric-manager-450 source package in Bionic: Fix Released Status in fabric-manager-460 source package in Bionic: Fix Released Status in libnvidia-nscq-450 source package in Bionic: Fix Released Status in libnvidia-nscq-460 source package in Bionic: Fix Released Status in linux-restricted-modules source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-450-server source package in Bionic: Fix Released Status in nvidia-graphics-drivers-460 source package in Bionic: Fix Released Status in nvidia-graphics-drivers-465 source package in Bionic: Fix Released Status in nvidia-settings source package in Bionic: Fix Committed Status in fabric-manager-450 source package in Focal: Fix Released Status in fabric-manager-460 source package in Focal: Fix Released Status in libnvidia-nscq-450 source package in Focal: Fix Released Status in libnvidia-nscq-460 source package in Focal: Fix Released Status in linux-restricted-modules source package in Focal: Fix Committed Status in nvidia-graphics-drivers-450-server source package in Focal: Fix Released Status in nvidia-graphics-drivers-460 source package in Focal: Fix Released Status in nvidia-graphics-drivers-465 source package in Focal: Fix Released Status in nvidia-settings source package in Focal: Fix Committed Status in fabric-manager-450 source package in Groovy: Fix Committed Status in fabric-manager-460 source package in Groovy: Fix Committed Status in libnvidia-nscq-450 source package in Groovy: Fix Committed Status in libnvidia-nscq-460 source package in Groovy: Fix Committed Status in linux-restricted-modules source package in Groovy: Fix Committed Status in nvidia-graphics-drivers-450-server source package in Groovy: Fix Released Status in nvidia-graphics-drivers-460 source package in Groovy: Fix Released Status in nvidia-graphics-drivers-465 source package in Groovy: Fix Released Status in nvidia-settings source package in Groovy: Fix Committed Status in fabric-manager-450 source package in Hirsute: Fix Released Status in fabric-manager-460 source package in Hirsute: Fix Released Status in libnvidia-nscq-450 source package in Hirsute: Fix Released Status in libnvidia-nscq-460 source package in Hirsute: Fix Released Status in linux-restricted-modules source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-450-server source package in Hirsute: Fix Released Status in nvidia-graphics-drivers-460 source package in Hirsute: Fix Released Status in nvidia-graphics-drivers-465 source package in Hirsute: Fix Released Status in nvidia-settings source package in Hirsute: Fix Committed Bug description: Introduce the new NVIDIA 465 driver series, fabric-manager and libnvidia-nscq. Also migrate the UDA 450 series to the 460 series. [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
[Kernel-packages] [Bug 1928808] Re: Requiring extra device ID for nvidia-driver-460
*** This bug is a duplicate of bug 1925522 *** https://bugs.launchpad.net/bugs/1925522 This bug was fixed in the package nvidia-graphics-drivers-460 - 460.80-0ubuntu3 --- nvidia-graphics-drivers-460 (460.80-0ubuntu3) impish; urgency=medium * debian/dkms_nvidia/patches/buildfix_kernel_5.13.patch, debian/templates/dkms_nvidia.conf.in: - Add support for Linux 5.13. -- Alberto Milone Wed, 26 May 2021 17:37:16 +0200 ** Changed in: nvidia-graphics-drivers-460 (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-460 in Ubuntu. https://bugs.launchpad.net/bugs/1928808 Title: Requiring extra device ID for nvidia-driver-460 Status in nvidia-graphics-drivers-460 package in Ubuntu: Fix Released Bug description: There are some new nvidia graphics could be supported by nvidia-driver-460. Here are the list: 1fb1 (Nvidia T600) 2231 (Nvidia RTX A5000) 24b7 (Nvidia RTX A4000 mobile) 24b8 (Nvidia RTX A3000 mobile) 25b8 (Nvidia RTX A2000 mobile) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-460/+bug/1928808/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1925241] Re: Disable CONFIG_DELL_SMBIOS_SMM, CONFIG_DELL_UART_BACKLIGHT, CONFIG_I2C_AMD_MP2
This bug was fixed in the package linux-gcp - 5.11.0-1008.8+21.10.1 --- linux-gcp (5.11.0-1008.8+21.10.1) impish; urgency=medium * impish/linux-gcp: 5.11.0-1008.8+21.10.1 -proposed tracker (LP: #1927565) * Packaging resync (LP: #1786013) - [Packaging] update update.conf - update dkms package versions -- Paolo Pisati Thu, 20 May 2021 13:01:39 +0200 ** Changed in: linux-gcp (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1925241 Title: Disable CONFIG_DELL_SMBIOS_SMM, CONFIG_DELL_UART_BACKLIGHT, CONFIG_I2C_AMD_MP2 Status in linux package in Ubuntu: Invalid Status in linux-gcp package in Ubuntu: Fix Released Status in linux-gcp-5.8 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-gcp source package in Focal: Invalid Status in linux-gcp-5.8 source package in Focal: In Progress Status in linux source package in Groovy: Invalid Status in linux-gcp source package in Groovy: Fix Released Status in linux-gcp-5.8 source package in Groovy: Invalid Status in linux source package in Hirsute: Invalid Status in linux-gcp source package in Hirsute: Fix Released Status in linux-gcp-5.8 source package in Hirsute: Invalid Bug description: SRU Justification: Enforcement annotations indicate that these config options should never have been set. [Impact] Disable these options for hardware that does not exist in the Google cloud fabric. There should be no impact to existing users. [Fix] CONFIG_DELL_SMBIOS_SMM=n CONFIG_DELL_UART_BACKLIGHT=n CONFIG_I2C_AMD_MP2=n [Test Plan] Boot a GCP instance and ensure there are no new kernel log errors. [Where problems could occur] Regression potential should be low since this HW does not exists in a GCP guest instance. [Other Info] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1925241/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1923557] Re: CirrusLogic: The default input volume is "0%" on Dell Bullseye
This bug was fixed in the package linux - 5.11.0-18.19+21.10.1 --- linux (5.11.0-18.19+21.10.1) impish; urgency=medium * impish/linux: 5.11.0-18.19+21.10.1 -proposed tracker (LP: #1927560) * Packaging resync (LP: #1786013) - [Packaging] update update.conf - update dkms package versions [ Ubuntu: 5.11.0-18.19 ] * hirsute/linux: 5.11.0-18.19 -proposed tracker (LP: #1927578) * Packaging resync (LP: #1786013) - update dkms package versions * Introduce the 465 driver series, fabric-manager, and libnvidia-nscq (LP: #1925522) - debian/dkms-versions -- add NVIDIA 465 and migrate 450 to 460 * linux-image-5.0.0-35-generic breaks checkpointing of container (LP: #1857257) - SAUCE: overlayfs: fix incorrect mnt_id of files opened from map_files * Hirsute update: v5.11.17 upstream stable release (LP: #1927535) - vhost-vdpa: protect concurrent access to vhost device iotlb - Revert "UBUNTU: SAUCE: ovl: Restore vm_file value when lower fs mmap fails" - ovl: fix reference counting in ovl_mmap error path - coda: fix reference counting in coda_file_mmap error path - amd/display: allow non-linear multi-planar formats - drm/amdgpu: reserve fence slot to update page table - drm/amdgpu: fix GCR_GENERAL_CNTL offset for dimgrey_cavefish - gpio: omap: Save and restore sysconfig - KEYS: trusted: Fix TPM reservation for seal/unseal - vdpa/mlx5: Set err = -ENOMEM in case dma_map_sg_attrs fails - pinctrl: lewisburg: Update number of pins in community - block: return -EBUSY when there are open partitions in blkdev_reread_part - pinctrl: core: Show pin numbers for the controllers with base = 0 - arm64: dts: allwinner: Revert SD card CD GPIO for Pine64-LTS - bpf: Allow variable-offset stack access - bpf: Refactor and streamline bounds check into helper - bpf: Tighten speculative pointer arithmetic mask - perf/x86/intel/uncore: Remove uncore extra PCI dev HSWEP_PCI_PCU_3 - perf/x86/kvm: Fix Broadwell Xeon stepping in isolation_ucodes[] - perf auxtrace: Fix potential NULL pointer dereference - perf map: Fix error return code in maps__clone() - HID: google: add don USB id - HID: asus: Add support for 2021 ASUS N-Key keyboard - HID: alps: fix error return code in alps_input_configured() - HID cp2112: fix support for multiple gpiochips - HID: wacom: Assign boolean values to a bool variable - soc: qcom: geni: shield geni_icc_get() for ACPI boot - dmaengine: xilinx: dpdma: Fix descriptor issuing on video group - dmaengine: xilinx: dpdma: Fix race condition in done IRQ - ARM: dts: Fix swapped mmc order for omap3 - m68k: fix flatmem memory model setup - net: geneve: check skb is large enough for IPv4/IPv6 header - dmaengine: tegra20: Fix runtime PM imbalance on error - s390/entry: save the caller of psw_idle - arm64: kprobes: Restore local irqflag if kprobes is cancelled - xen-netback: Check for hotplug-status existence before watching - cavium/liquidio: Fix duplicate argument - csky: change a Kconfig symbol name to fix e1000 build error - ia64: fix discontig.c section mismatches - ia64: tools: remove duplicate definition of ia64_mf() on ia64 - x86/crash: Fix crash_setup_memmap_entries() out-of-bounds access - net: hso: fix NULL-deref on disconnect regression - USB: CDC-ACM: fix poison/unpoison imbalance - Linux 5.11.17 * locking/qrwlock: Fix ordering in queued_write_lock_slowpath() (LP: #1926184) - locking/qrwlock: Fix ordering in queued_write_lock_slowpath() * Fix kernel panic at boot on dual GFX systems (LP: #1926792) - drm/amdgpu: Register VGA clients after init can no longer fail * Gigabyte R120-T33 (ARM ThunderX SoC) fails to boot in ACPI mode (LP: #1925075) - ACPI: GTDT: Don't corrupt interrupt mappings on watchdow probe failure * CirrusLogic: Cracking noises appears in built-in speaker when output volume is set >80% (LP: #1924997) - ALSA: hda/cirrus: Use CS8409 filter to fix abnormal sounds on Bullseye * CirrusLogic: The default input volume is "0%" (LP: #1923557) - ALSA: hda/cirrus: Set Initial DMIC volume for Bullseye to -26 dB * Fix no picture from HDMI when it's plugged after boot (LP: #1924238) - drm/i915/display: Handle lane polarity for DDI port * Make AMD gpus choose YCbCr420 encoding automatically when required for 4k 60Hz output (LP: #1922754) - drm/amd/display: Try YCbCr420 color when YCbCr444 fails * Hirsute update: v5.11.16 upstream stable release (LP: #1926999) - AMD_SFH: Removed unused activecontrolstatus member from the amd_mp2_dev struct - AMD_SFH: Add sensor_mask module parameter - AMD_SFH: Add DMI quirk table for BIOS-es which don't set the activestatus bits - mtd: rawnand: mtk: Fix WAITRDY break condition and timeout - Input: nspire-keypad - enable interrupts only when opened - gpio: sysfs: Obey
[Kernel-packages] [Bug 1925415] Re: Enable mute/micmute LEDs and limit mic boost on EliteBook 845 G8
This bug was fixed in the package linux - 5.11.0-18.19+21.10.1 --- linux (5.11.0-18.19+21.10.1) impish; urgency=medium * impish/linux: 5.11.0-18.19+21.10.1 -proposed tracker (LP: #1927560) * Packaging resync (LP: #1786013) - [Packaging] update update.conf - update dkms package versions [ Ubuntu: 5.11.0-18.19 ] * hirsute/linux: 5.11.0-18.19 -proposed tracker (LP: #1927578) * Packaging resync (LP: #1786013) - update dkms package versions * Introduce the 465 driver series, fabric-manager, and libnvidia-nscq (LP: #1925522) - debian/dkms-versions -- add NVIDIA 465 and migrate 450 to 460 * linux-image-5.0.0-35-generic breaks checkpointing of container (LP: #1857257) - SAUCE: overlayfs: fix incorrect mnt_id of files opened from map_files * Hirsute update: v5.11.17 upstream stable release (LP: #1927535) - vhost-vdpa: protect concurrent access to vhost device iotlb - Revert "UBUNTU: SAUCE: ovl: Restore vm_file value when lower fs mmap fails" - ovl: fix reference counting in ovl_mmap error path - coda: fix reference counting in coda_file_mmap error path - amd/display: allow non-linear multi-planar formats - drm/amdgpu: reserve fence slot to update page table - drm/amdgpu: fix GCR_GENERAL_CNTL offset for dimgrey_cavefish - gpio: omap: Save and restore sysconfig - KEYS: trusted: Fix TPM reservation for seal/unseal - vdpa/mlx5: Set err = -ENOMEM in case dma_map_sg_attrs fails - pinctrl: lewisburg: Update number of pins in community - block: return -EBUSY when there are open partitions in blkdev_reread_part - pinctrl: core: Show pin numbers for the controllers with base = 0 - arm64: dts: allwinner: Revert SD card CD GPIO for Pine64-LTS - bpf: Allow variable-offset stack access - bpf: Refactor and streamline bounds check into helper - bpf: Tighten speculative pointer arithmetic mask - perf/x86/intel/uncore: Remove uncore extra PCI dev HSWEP_PCI_PCU_3 - perf/x86/kvm: Fix Broadwell Xeon stepping in isolation_ucodes[] - perf auxtrace: Fix potential NULL pointer dereference - perf map: Fix error return code in maps__clone() - HID: google: add don USB id - HID: asus: Add support for 2021 ASUS N-Key keyboard - HID: alps: fix error return code in alps_input_configured() - HID cp2112: fix support for multiple gpiochips - HID: wacom: Assign boolean values to a bool variable - soc: qcom: geni: shield geni_icc_get() for ACPI boot - dmaengine: xilinx: dpdma: Fix descriptor issuing on video group - dmaengine: xilinx: dpdma: Fix race condition in done IRQ - ARM: dts: Fix swapped mmc order for omap3 - m68k: fix flatmem memory model setup - net: geneve: check skb is large enough for IPv4/IPv6 header - dmaengine: tegra20: Fix runtime PM imbalance on error - s390/entry: save the caller of psw_idle - arm64: kprobes: Restore local irqflag if kprobes is cancelled - xen-netback: Check for hotplug-status existence before watching - cavium/liquidio: Fix duplicate argument - csky: change a Kconfig symbol name to fix e1000 build error - ia64: fix discontig.c section mismatches - ia64: tools: remove duplicate definition of ia64_mf() on ia64 - x86/crash: Fix crash_setup_memmap_entries() out-of-bounds access - net: hso: fix NULL-deref on disconnect regression - USB: CDC-ACM: fix poison/unpoison imbalance - Linux 5.11.17 * locking/qrwlock: Fix ordering in queued_write_lock_slowpath() (LP: #1926184) - locking/qrwlock: Fix ordering in queued_write_lock_slowpath() * Fix kernel panic at boot on dual GFX systems (LP: #1926792) - drm/amdgpu: Register VGA clients after init can no longer fail * Gigabyte R120-T33 (ARM ThunderX SoC) fails to boot in ACPI mode (LP: #1925075) - ACPI: GTDT: Don't corrupt interrupt mappings on watchdow probe failure * CirrusLogic: Cracking noises appears in built-in speaker when output volume is set >80% (LP: #1924997) - ALSA: hda/cirrus: Use CS8409 filter to fix abnormal sounds on Bullseye * CirrusLogic: The default input volume is "0%" (LP: #1923557) - ALSA: hda/cirrus: Set Initial DMIC volume for Bullseye to -26 dB * Fix no picture from HDMI when it's plugged after boot (LP: #1924238) - drm/i915/display: Handle lane polarity for DDI port * Make AMD gpus choose YCbCr420 encoding automatically when required for 4k 60Hz output (LP: #1922754) - drm/amd/display: Try YCbCr420 color when YCbCr444 fails * Hirsute update: v5.11.16 upstream stable release (LP: #1926999) - AMD_SFH: Removed unused activecontrolstatus member from the amd_mp2_dev struct - AMD_SFH: Add sensor_mask module parameter - AMD_SFH: Add DMI quirk table for BIOS-es which don't set the activestatus bits - mtd: rawnand: mtk: Fix WAITRDY break condition and timeout - Input: nspire-keypad - enable interrupts only when opened - gpio: sysfs: Obey
[Kernel-packages] [Bug 1926236] Re: Fix The sound has noise while audio volume is maximum
How did the packages get tested? What package versions have been verified? Please follow the SRU guidelines before switching the tags to verification-done*. Switching back to unverified. ** Tags removed: verification-done-focal ** Tags added: verification-needed-focal -- 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/1926236 Title: Fix The sound has noise while audio volume is maximum Status in HWE Next: New Status in linux-firmware package in Ubuntu: Fix Released Status in linux-firmware source package in Focal: Fix Committed Bug description: [Impact] The sound has noise while turning the audio volume to maximum [Fix] For VEGA & Polaris, need two patches(landed on mainline kernel) to fix and a modprobe 1.(50ceb1fe7a) drm/amd/pm: bug fix for pcie dpm, has landed on oem kernel. 2.(9d03730ecb) drm/amd/pm: workaround for audio noise issue, has landed on oem kernel 3. #modprobe amdgpu ppfeaturemask=0xfff7bffb. For Navi_1x, need smc firmware to fix. 1. (4fe6e53b96 linux-firmware) amdgpu: update navi10 SMC firmware 1. (8ab7abaf63 linux-firmware) amdgpu: update navi14 SMC firmware [Test] Verified on RKL platform A. with wx3200(Polaris series) and the following configuration 1. With these two patch, 1.1. (50ceb1fe7a) drm/amd/pm: bug fix for pcie dpm, has landed on oem kernel. 1.2. (9d03730ecb) drm/amd/pm: workaround for audio noise issue, has landed on oem kernel 2. doesn't append ppfeaturemask=0xfff7bffb Can't observe issue. B. With wx5500(Navi series) and update the related firmware, Can't observe issue [Where problems could occur] Because disabling DPM, the power consumption would be slightly higher. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1926236/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1924997] Re: CirrusLogic: Cracking noises appears in built-in speaker when output volume is set >80%
This bug was fixed in the package linux - 5.11.0-18.19+21.10.1 --- linux (5.11.0-18.19+21.10.1) impish; urgency=medium * impish/linux: 5.11.0-18.19+21.10.1 -proposed tracker (LP: #1927560) * Packaging resync (LP: #1786013) - [Packaging] update update.conf - update dkms package versions [ Ubuntu: 5.11.0-18.19 ] * hirsute/linux: 5.11.0-18.19 -proposed tracker (LP: #1927578) * Packaging resync (LP: #1786013) - update dkms package versions * Introduce the 465 driver series, fabric-manager, and libnvidia-nscq (LP: #1925522) - debian/dkms-versions -- add NVIDIA 465 and migrate 450 to 460 * linux-image-5.0.0-35-generic breaks checkpointing of container (LP: #1857257) - SAUCE: overlayfs: fix incorrect mnt_id of files opened from map_files * Hirsute update: v5.11.17 upstream stable release (LP: #1927535) - vhost-vdpa: protect concurrent access to vhost device iotlb - Revert "UBUNTU: SAUCE: ovl: Restore vm_file value when lower fs mmap fails" - ovl: fix reference counting in ovl_mmap error path - coda: fix reference counting in coda_file_mmap error path - amd/display: allow non-linear multi-planar formats - drm/amdgpu: reserve fence slot to update page table - drm/amdgpu: fix GCR_GENERAL_CNTL offset for dimgrey_cavefish - gpio: omap: Save and restore sysconfig - KEYS: trusted: Fix TPM reservation for seal/unseal - vdpa/mlx5: Set err = -ENOMEM in case dma_map_sg_attrs fails - pinctrl: lewisburg: Update number of pins in community - block: return -EBUSY when there are open partitions in blkdev_reread_part - pinctrl: core: Show pin numbers for the controllers with base = 0 - arm64: dts: allwinner: Revert SD card CD GPIO for Pine64-LTS - bpf: Allow variable-offset stack access - bpf: Refactor and streamline bounds check into helper - bpf: Tighten speculative pointer arithmetic mask - perf/x86/intel/uncore: Remove uncore extra PCI dev HSWEP_PCI_PCU_3 - perf/x86/kvm: Fix Broadwell Xeon stepping in isolation_ucodes[] - perf auxtrace: Fix potential NULL pointer dereference - perf map: Fix error return code in maps__clone() - HID: google: add don USB id - HID: asus: Add support for 2021 ASUS N-Key keyboard - HID: alps: fix error return code in alps_input_configured() - HID cp2112: fix support for multiple gpiochips - HID: wacom: Assign boolean values to a bool variable - soc: qcom: geni: shield geni_icc_get() for ACPI boot - dmaengine: xilinx: dpdma: Fix descriptor issuing on video group - dmaengine: xilinx: dpdma: Fix race condition in done IRQ - ARM: dts: Fix swapped mmc order for omap3 - m68k: fix flatmem memory model setup - net: geneve: check skb is large enough for IPv4/IPv6 header - dmaengine: tegra20: Fix runtime PM imbalance on error - s390/entry: save the caller of psw_idle - arm64: kprobes: Restore local irqflag if kprobes is cancelled - xen-netback: Check for hotplug-status existence before watching - cavium/liquidio: Fix duplicate argument - csky: change a Kconfig symbol name to fix e1000 build error - ia64: fix discontig.c section mismatches - ia64: tools: remove duplicate definition of ia64_mf() on ia64 - x86/crash: Fix crash_setup_memmap_entries() out-of-bounds access - net: hso: fix NULL-deref on disconnect regression - USB: CDC-ACM: fix poison/unpoison imbalance - Linux 5.11.17 * locking/qrwlock: Fix ordering in queued_write_lock_slowpath() (LP: #1926184) - locking/qrwlock: Fix ordering in queued_write_lock_slowpath() * Fix kernel panic at boot on dual GFX systems (LP: #1926792) - drm/amdgpu: Register VGA clients after init can no longer fail * Gigabyte R120-T33 (ARM ThunderX SoC) fails to boot in ACPI mode (LP: #1925075) - ACPI: GTDT: Don't corrupt interrupt mappings on watchdow probe failure * CirrusLogic: Cracking noises appears in built-in speaker when output volume is set >80% (LP: #1924997) - ALSA: hda/cirrus: Use CS8409 filter to fix abnormal sounds on Bullseye * CirrusLogic: The default input volume is "0%" (LP: #1923557) - ALSA: hda/cirrus: Set Initial DMIC volume for Bullseye to -26 dB * Fix no picture from HDMI when it's plugged after boot (LP: #1924238) - drm/i915/display: Handle lane polarity for DDI port * Make AMD gpus choose YCbCr420 encoding automatically when required for 4k 60Hz output (LP: #1922754) - drm/amd/display: Try YCbCr420 color when YCbCr444 fails * Hirsute update: v5.11.16 upstream stable release (LP: #1926999) - AMD_SFH: Removed unused activecontrolstatus member from the amd_mp2_dev struct - AMD_SFH: Add sensor_mask module parameter - AMD_SFH: Add DMI quirk table for BIOS-es which don't set the activestatus bits - mtd: rawnand: mtk: Fix WAITRDY break condition and timeout - Input: nspire-keypad - enable interrupts only when opened - gpio: sysfs: Obey
[Kernel-packages] [Bug 1927518] Re: Fix kdump failures
This bug was fixed in the package linux-azure - 5.11.0-1006.6+21.10.1 --- linux-azure (5.11.0-1006.6+21.10.1) impish; urgency=medium * impish/linux-azure: 5.11.0-1006.6+21.10.1 -proposed tracker (LP: #1927563) * Packaging resync (LP: #1786013) - [Packaging] update update.conf - update dkms package versions -- Paolo Pisati Wed, 19 May 2021 12:51:59 +0200 ** Changed in: linux-azure (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1927518 Title: Fix kdump failures Status in linux package in Ubuntu: Incomplete Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-4.15 package in Ubuntu: New Status in linux source package in Bionic: Fix Committed Status in linux-azure source package in Bionic: Invalid Status in linux-azure-4.15 source package in Bionic: Fix Released Status in linux source package in Focal: Fix Committed Status in linux-azure source package in Focal: Fix Released Status in linux-azure-4.15 source package in Focal: Invalid Status in linux source package in Groovy: Fix Committed Status in linux-azure source package in Groovy: Fix Released Status in linux-azure-4.15 source package in Groovy: Invalid Status in linux source package in Hirsute: Fix Committed Status in linux-azure source package in Hirsute: Fix Released Status in linux-azure-4.15 source package in Hirsute: Invalid Bug description: SRU Justification [Impact] Microsoft relayed a customer report of failures when trying to take a kdump. These 3 patches fix the issue: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/video/fbdev/hyperv_fb.c?id=aa5b7d11c7cb87c266d705b237368985e7171958 https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/hv/channel_mgmt.c?id=77db0ec8b7764cb9b09b78066ebfd47b2c0c1909 https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/hv/channel_mgmt.c?id=8c2d5e0640e53c14b6240e9bf1e32a2226e6e6ca Patch #1 solves a problem where the “Unable to send packet via vmbus” message is output continuously. But with that problem fixed, the second problem can occur where the kdump kernel panics due to receiving an unexpected VMbus UNLOAD complete message. Patch #2 prevents the UNLOAD complete message from ever occurring in the kdump kernel. But if the UNLOAD complete message does occur at some unexpected time, Patch #3 prevents it from causing a panic. These patches seem worthy of application to all affected master kernels. [Test Plan] Cause a guest kernel to crash and successfully acquire a kdump. [Where problems could occur] The extended Hyper-V wait while flushing could cause side effects. [Other Info] SF: #00310145 https://canonical.lightning.force.com/lightning/r/Case/5004K05pZNNQA2/view To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1927518/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1930923] Re: Miscelaneou kernel freeze after connecting USB-C dock
Please test latest drm-tip kernel: https://kernel.ubuntu.com/~kernel-ppa/mainline/drm-tip/current/ Headers are not needed. ** 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/1930923 Title: Miscelaneou kernel freeze after connecting USB-C dock Status in linux package in Ubuntu: Incomplete Bug description: If the notebook (DELL 5590) is connected to USB-C dock I-Tec Metal Nano https://i-tec.pro/en/produkt/c31nanodocklanpd-2/ occasionally (in few hours) the kernel locks itself and hard reset have to be done. There are then usually errors in "journalctl" (after some occurences, nothing is logged, but it is probably due to incompleteness of the writed logs). During each freeze more errors are logged and the error differ, so I append complete logged errors from two cases (I can post more "cases", if it will help). Both memcheck and smart says no error, and without the dock the notebook works fine. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: linux-image-5.11.0-18-generic 5.11.0-18.19 ProcVersionSignature: Ubuntu 5.11.0-18.19-generic 5.11.17 Uname: Linux 5.11.0-18-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: logik 2404 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: X-Cinnamon Date: Fri Jun 4 21:01:08 2021 HibernationDevice: RESUME=UUID=5f7825a4-cd50-4645-9ff6-32de3bdf9b1f InstallationDate: Installed on 2017-01-06 (1610 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: Dell Inc. Latitude 5590 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-18-generic root=UUID=be75c71c-97f3-406f-9310-e1bf1252c62a ro quiet splash resume=uuid=5f7825a4-cd50-4645-9ff6-32de3bdf9b1f usbcore.autosuspend=-1 vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.11.0-18-generic N/A linux-backports-modules-5.11.0-18-generic N/A linux-firmware 1.197 SourcePackage: linux UpgradeStatus: Upgraded to hirsute on 2021-06-01 (2 days ago) WifiSyslog: dmi.bios.date: 03/05/2021 dmi.bios.release: 1.16 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.16.3 dmi.board.name: 02N9PD dmi.board.vendor: Dell Inc. dmi.board.version: A05 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.16.3:bd03/05/2021:br1.16:svnDellInc.:pnLatitude5590:pvr:rvnDellInc.:rn02N9PD:rvrA05:cvnDellInc.:ct10:cvr: dmi.product.family: Latitude dmi.product.name: Latitude 5590 dmi.product.sku: 0817 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1930923/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1931106] Re: bnxt_en NIC driver crashes IO_PAGE_FAULT
Please test latest mainline kernel: https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.13-rc5/amd64/ Headers are not needed. ** 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/1931106 Title: bnxt_en NIC driver crashes IO_PAGE_FAULT Status in linux package in Ubuntu: Incomplete Bug description: Hi all, We received a bunch of new servers with a Supermicro H12SSL-NT mainboard that has an embedded Broadcom BCM57416 NIC. On all those servers we observe crashes of the NIC driver (bnxt_en) from time to time. We're not able to manually reproduce this issue, it just occurs at some point. Also our monitoring does not show any irregularities(high traffic flow or sth. like this). Syslog: https://pastebin.com/yDAyjHvF All servers are running with up-to-date packages: $ lsb_release -rd Description: Ubuntu 20.04.2 LTS Release: 20.04 $ uname -r 5.4.0-73-generic It also happens on older kernel versions (tested 5.4.0-66) as well as the HWE kernel (tested 5.8.0-55). Thanks in advance. ~ Roman To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1931106/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1929147] Re: fix system hang with 5.10 kernel + RX540 on RKL platform
How did the packages get tested? What package versions have been verified? Please follow the SRU guidelines before switching the tags to verification-done*. Switching back to unverified. ** Tags removed: verification-done-focal verification-done-hirsute ** Tags added: verification-needed-focal verification-needed-hirsute -- 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/1929147 Title: fix system hang with 5.10 kernel + RX540 on RKL platform Status in HWE Next: New Status in linux-firmware package in Ubuntu: Fix Released Status in linux-firmware source package in Focal: Fix Committed Status in linux-firmware source package in Hirsute: Fix Committed Bug description: [Impact] On RKL platform with AMD RX540, system would hang during boot-up. [Fix] AMD introduce a brand new firmware, polaris 12 MC firmware. This fix the issue and the system wouldn't hang during boot-up with AMD RX540. [Test] Verified on RKL platform and AMD RX540 System would boot-up and login to desktop successfully. [Where problems could occur] This's a brand new firmware to support Polaris-series, it may introduce new issues. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1929147/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1931129] Re: v5.13 net bpf selftests fail with older clang toolchains
** Patch added: "0001-selftests-bpf-add-ifdefs-in-tests-for-required-Clang.patch" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1931129/+attachment/5502940/+files/0001-selftests-bpf-add-ifdefs-in-tests-for-required-Clang.patch -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1931129 Title: v5.13 net bpf selftests fail with older clang toolchains Status in linux package in Ubuntu: New Bug description: selftests/bpf: add ifdefs in tests for required Clang versions This codifies the clang version requirements from README.rst in the code, such that only expected working test cases are compiled for the expected clang version combinations. This insures that most tests are still executed, even when one doesn't have access to the latest clang toolchain. Also see internal v5.13 test results. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1931129/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1931129] [NEW] v5.13 net bpf selftests fail with older clang toolchains
Public bug reported: selftests/bpf: add ifdefs in tests for required Clang versions This codifies the clang version requirements from README.rst in the code, such that only expected working test cases are compiled for the expected clang version combinations. This insures that most tests are still executed, even when one doesn't have access to the latest clang toolchain. Also see internal v5.13 test results. ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1931129 Title: v5.13 net bpf selftests fail with older clang toolchains Status in linux package in Ubuntu: New Bug description: selftests/bpf: add ifdefs in tests for required Clang versions This codifies the clang version requirements from README.rst in the code, such that only expected working test cases are compiled for the expected clang version combinations. This insures that most tests are still executed, even when one doesn't have access to the latest clang toolchain. Also see internal v5.13 test results. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1931129/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1930188] Re: Acer Aspire 5 sound driver issues
I just tested with the latest custom kernel shared here and with this updated pulseaudio package and can confirm speakers and headphones have separate volume now. Thanks a lot again, I guess all of the major 3 initially mentioned and 1 extra issues are solved now and hope the 3 ucm realted very minor issues will be refined in future. So, now only thing remaining is to get these fixes in official ubuntu kernel and pulseaudio package I guess, also I am not sure if it's safe to keep using the custom kernel/pulseaudio driver or wait till it arrives officially and meanwhile keep using temp fix for now. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1930188 Title: Acer Aspire 5 sound driver issues Status in linux package in Ubuntu: New Bug description: Hello, There seems to be lots of issues in sound driver for Acer Aspire A515-56-57XR with ALC255. I will list all of them below and what I have tried so far. 1. Headphones appears always plugged in even if they are physically not 2. When actually plugging in headset/earphones it does not auto switch from speakers/internal mic to headphones/headset microphone automatically and vice versa, have to manually switch everytime. 3. External headset/earphones microphone won't work at all After, logs of trial and error I have found a temporary fix. This seems to use legacy intel drivers which solves all 3 issues mentioned above but the internal/dmic mic is completely gone (which seems intentional when using this). Both depreciated dmic_detect and dsp_driver works, I have been using dsp_driver for now as I need external microphone at any cost. End of /etc/modprobe.d/alsa-base.conf # Headset mic fix options snd-hda-intel dmic_detect=0 / options snd-intel-dspcfg dsp_driver=1 options snd-hda-intel model=alc255-acer In another thread similar to this I got some support and at least fixed the external microphone without using the alsa-base.conf change in custom modified kernel. I will attach it here. Now, hoping to fix other issues as well slowly like making headphones unplugged when physically removing as well as auto switching like the legacy driver one. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1930188/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1931131] [NEW] Update the 465 and the 460 NVIDIA driver series
Public bug reported: Update the 465 and the 460 NVIDIA driver series [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] [Changelog] ** Affects: nvidia-settings (Ubuntu) Importance: Medium Assignee: Alberto Milone (albertomilone) Status: Triaged ** Description changed: Update the 465 and the 460 NVIDIA driver series + + [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] + + [Changelog] -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-settings in Ubuntu. https://bugs.launchpad.net/bugs/1931131 Title: Update the 465 and the 460 NVIDIA driver series Status in nvidia-settings package in Ubuntu: Triaged Bug description: Update the 465 and the 460 NVIDIA driver series [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] [Changelog] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-settings/+bug/1931131/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1930733] Re: Kernel oops with the 460.80 and 465.27 drivers when using DP, but not with HDMI
Works with DVI-D, but not if DP is connected to a device. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-460 in Ubuntu. https://bugs.launchpad.net/bugs/1930733 Title: Kernel oops with the 460.80 and 465.27 drivers when using DP, but not with HDMI Status in nvidia-graphics-drivers-460 package in Ubuntu: Triaged Status in nvidia-graphics-drivers-465 package in Ubuntu: Triaged Bug description: I get a kernel oops with the 460.80 and 465.27 drivers on Hirsute Jun 03 16:26:57 willow kernel: Oops: [#1] SMP PTI Jun 03 16:26:57 willow kernel: CPU: 7 PID: 2004 Comm: Xorg Tainted: P OE 5.11.0-18-generic #19-Ubuntu Jun 03 16:26:57 willow kernel: Hardware name: System manufacturer System Product Name/PRIME H270M-PLUS, BIOS 1605 12/13/2019 Jun 03 16:26:57 willow kernel: RIP: 0010:_nv015534rm+0x1b6/0x330 [nvidia] Jun 03 16:26:57 willow kernel: Code: 8b 87 68 05 00 00 ba 01 00 00 00 be 02 00 00 00 e8 bf eb 55 c8 41 83 c5 01 41 83 fd 1f 0f 84 0b 01 00 00 48 8b 45 10 44 89 ee <48> 8b b8 70 01 00 00 48 8b 87 d8 04 00 00 e8> Jun 03 16:26:57 willow kernel: RSP: :af4201893958 EFLAGS: 00010297 Jun 03 16:26:57 willow kernel: RAX: RBX: 0400 RCX: 0003 Jun 03 16:26:57 willow kernel: RDX: 0004 RSI: 0003 RDI: Jun 03 16:26:57 willow kernel: RBP: 8e318220add0 R08: 0001 R09: 8e318220acb8 Jun 03 16:26:57 willow kernel: R10: 8e3182204008 R11: 1010 R12: 0400 Jun 03 16:26:57 willow kernel: R13: 0003 R14: 8e3186ca8010 R15: 0800 Jun 03 16:26:57 willow kernel: FS: 7f5807f38a40() GS:8e3466dc() knlGS: Jun 03 16:26:57 willow kernel: CS: 0010 DS: ES: CR0: 80050033 Jun 03 16:26:57 willow kernel: CR2: 0170 CR3: 000140710005 CR4: 003706e0 Jun 03 16:26:57 willow kernel: DR0: DR1: DR2: Jun 03 16:26:57 willow kernel: DR3: DR6: fffe0ff0 DR7: 0400 Jun 03 16:26:57 willow kernel: Call Trace: Jun 03 16:26:57 willow kernel: ? _nv015556rm+0x7fd/0x1020 [nvidia] Jun 03 16:26:57 willow kernel: ? _nv027155rm+0x22c/0x4f0 [nvidia] Jun 03 16:26:57 willow kernel: ? _nv017787rm+0x303/0x5e0 [nvidia] Jun 03 16:26:57 willow kernel: ? _nv017789rm+0xe1/0x220 [nvidia] Jun 03 16:26:57 willow kernel: ? _nv022829rm+0xed/0x220 [nvidia] Jun 03 16:26:57 willow kernel: ? _nv023065rm+0x30/0x60 [nvidia] Jun 03 16:26:57 willow kernel: ? _nv000704rm+0x16da/0x22b0 [nvidia] Jun 03 16:26:57 willow kernel: ? rm_init_adapter+0xc5/0xe0 [nvidia] Jun 03 16:26:57 willow kernel: ? nv_open_device+0x122/0x8e0 [nvidia] Jun 03 16:26:57 willow kernel: ? nvidia_open+0x2b7/0x560 [nvidia] Jun 03 16:26:57 willow kernel: ? nvidia_frontend_open+0x58/0xa0 [nvidia] Jun 03 16:26:57 willow kernel: ? chrdev_open+0xf7/0x220 Jun 03 16:26:57 willow kernel: ? cdev_device_add+0x90/0x90 Jun 03 16:26:57 willow kernel: ? do_dentry_open+0x156/0x370 Jun 03 16:26:57 willow kernel: ? vfs_open+0x2d/0x30 Jun 03 16:26:57 willow kernel: ? do_open+0x1c3/0x340 Jun 03 16:26:57 willow kernel: ? path_openat+0x10a/0x1d0 Jun 03 16:26:57 willow kernel: ? do_filp_open+0x8c/0x130 Jun 03 16:26:57 willow kernel: ? __check_object_size+0x1c/0x20 Jun 03 16:26:57 willow kernel: ? do_sys_openat2+0x9b/0x150 Jun 03 16:26:57 willow kernel: ? __x64_sys_openat+0x56/0x90 Jun 03 16:26:57 willow kernel: ? do_syscall_64+0x38/0x90 Jun 03 16:26:57 willow kernel: ? entry_SYSCALL_64_after_hwframe+0x44/0xa9 Jun 03 16:26:57 willow kernel: Modules linked in: snd_seq_dummy snd_hrtimer vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) binfmt_misc zfs(PO) zunicode(PO) zzstd(O) zlua(O) zavl(PO) icp(PO) zcommon(PO) znvpair(PO) > Jun 03 16:26:57 willow kernel: sunrpc ip_tables x_tables autofs4 btrfs blake2b_generic xor raid6_pq libcrc32c hid_generic usbhid hid crct10dif_pclmul crc32_pclmul ghash_clmulni_intel aesni_intel crypto_simd c> Jun 03 16:26:57 willow kernel: CR2: 0170 Jun 03 16:26:57 willow kernel: ---[ end trace 0013b6989b267f32 ]--- Jun 03 16:26:57 willow kernel: RIP: 0010:_nv015534rm+0x1b6/0x330 [nvidia] Jun 03 16:26:57 willow kernel: Code: 8b 87 68 05 00 00 ba 01 00 00 00 be 02 00 00 00 e8 bf eb 55 c8 41 83 c5 01 41 83 fd 1f 0f 84 0b 01 00 00 48 8b 45 10 44 89 ee <48> 8b b8 70 01 00 00 48 8b 87 d8 04 00 00 e8> Jun 03 16:26:57 willow kernel: RSP: :af4201893958 EFLAGS: 00010297 Jun 03 16:26:57 willow kernel: RAX: RBX: 0400 RCX: 0003 Jun 03 16:26:57 willow kernel: RDX: 0004 RSI: 0003 RDI: Jun 03 16:26:57 willow kernel: RBP: 8e318220add0 R08: 0001 R09:
[Kernel-packages] [Bug 1930923] Re: Miscelaneou kernel freeze after connecting USB-C dock
Disabling CPU C-states in bios seems to solve this issue (however, this solution has an impact on the battery life). -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1930923 Title: Miscelaneou kernel freeze after connecting USB-C dock Status in linux package in Ubuntu: New Bug description: If the notebook (DELL 5590) is connected to USB-C dock I-Tec Metal Nano https://i-tec.pro/en/produkt/c31nanodocklanpd-2/ occasionally (in few hours) the kernel locks itself and hard reset have to be done. There are then usually errors in "journalctl" (after some occurences, nothing is logged, but it is probably due to incompleteness of the writed logs). During each freeze more errors are logged and the error differ, so I append complete logged errors from two cases (I can post more "cases", if it will help). Both memcheck and smart says no error, and without the dock the notebook works fine. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: linux-image-5.11.0-18-generic 5.11.0-18.19 ProcVersionSignature: Ubuntu 5.11.0-18.19-generic 5.11.17 Uname: Linux 5.11.0-18-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: logik 2404 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: X-Cinnamon Date: Fri Jun 4 21:01:08 2021 HibernationDevice: RESUME=UUID=5f7825a4-cd50-4645-9ff6-32de3bdf9b1f InstallationDate: Installed on 2017-01-06 (1610 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: Dell Inc. Latitude 5590 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-18-generic root=UUID=be75c71c-97f3-406f-9310-e1bf1252c62a ro quiet splash resume=uuid=5f7825a4-cd50-4645-9ff6-32de3bdf9b1f usbcore.autosuspend=-1 vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.11.0-18-generic N/A linux-backports-modules-5.11.0-18-generic N/A linux-firmware 1.197 SourcePackage: linux UpgradeStatus: Upgraded to hirsute on 2021-06-01 (2 days ago) WifiSyslog: dmi.bios.date: 03/05/2021 dmi.bios.release: 1.16 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.16.3 dmi.board.name: 02N9PD dmi.board.vendor: Dell Inc. dmi.board.version: A05 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.16.3:bd03/05/2021:br1.16:svnDellInc.:pnLatitude5590:pvr:rvnDellInc.:rn02N9PD:rvrA05:cvnDellInc.:ct10:cvr: dmi.product.family: Latitude dmi.product.name: Latitude 5590 dmi.product.sku: 0817 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1930923/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1930921] Re: Apache 2.4.41 corrupts files from samba share
Thank you for taking the time to report this bug and helping to make Ubuntu better. I'll leave any security assessment and security-based prioritisation for the security team. >From a non-security perspective, I think this is of low priority since it only affects an unusual end-user configuration that is likely to affect only a very small minority of users. Feel free to continue to use this bug to track the problem, but I do not expect anyone else to spend time looking into this soon. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1930921 Title: Apache 2.4.41 corrupts files from samba share Status in apache2 package in Ubuntu: New Status in linux package in Ubuntu: New Status in samba package in Ubuntu: New Bug description: Wenn I serve a samba share with apache 2.4.41 on Ubuntu 20.04 then some files have a corrupt header during transmission. It seems that the first few bytes of the headers are truncated and sometimes other bytes of the download are not belonging to the file. A workaround I found that works is to set "EnableMMAP Off" in the apache config. See other bug reports like this: https://serverfault.com/questions/1044724/apache2-sends-corrupt-responses-when-using-a-cifs-share https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=900821 This is most probably not a bug in Ubuntu itself but I am reporting it here since I assume that a data corruption bug is seen as critical. I am also marking it as a security vulnerability since it seems that wrong parts of memory get exposed during file download. I don't know how random the exposed memory is and if it potentially could expose e.g. secrets. Please feel free to remove the security vulnerability flag if your assessment leads to a different conclusion. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1930921/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1215411] Re: libcpupower.so is not installed from linux-tools
Yeah Dmitry, thanks for reminding everyone about it. But TBH I have not had the feeling that the feeling that the kernel team (which needs to do it) had started working/thinking on this case. @Kernel Team - ping is this on your radar at all or did it fall through the cracks? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1215411 Title: libcpupower.so is not installed from linux-tools Status in cpufreqd package in Ubuntu: Confirmed Status in gkrellm2-cpufreq package in Ubuntu: Confirmed Status in linux package in Ubuntu: In Progress Bug description: The patch for bug 1158668 installs cpupower_$(abi_version) command- line tool as well as libcpupower.so.$(abi_version). This isn't particularly suitable for projects that previously used libcpufreq and intend to migrate to libcpupower, because the libcpupower.so symlink is no longer installed. The command-line tools can also have symlinks (e.g. cpupower -> cpupower_$(abi_version)). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cpufreqd/+bug/1215411/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
Re: [Kernel-packages] [Bug 1930422] Re: thermald_1.9.1-1ubuntu0.4_amd64 breaks system
longer run. thanks for your help. without people like you we'd all be using Windows! On 07/06/2021 03:23, Srinivas Pandruvada wrote: > Please try this version > https://github.com/intel/thermal_daemon/tree/ubuntu-bug-1930422 > > checkout branch ubuntu-bug-1930422. > Then repeat comments at #11 > ** Attachment added: "branch-journalctl.txt" https://bugs.launchpad.net/bugs/1930422/+attachment/5502932/+files/branch-journalctl.txt -- 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/1930422 Title: thermald_1.9.1-1ubuntu0.4_amd64 breaks system Status in thermald package in Ubuntu: New Bug description: cpu runs at 100c fan at 3000rpm when in heavy use previous version was ok re: https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/1913186 lshw -short is: H/W path Device Class Description == system XPS 8940 (09C5) /0 bus0KV3RP /0/0memory 64KiB BIOS /0/9memory 16GiB System Memory /0/9/0 memory 8GiB DIMM DDR4 Synchronous 32 /0/9/1 memory 8GiB DIMM DDR4 Synchronous 32 /0/9/2 memory Project-Id-Version: lshwRepor /0/9/3 memory Project-Id-Version: lshwRepor /0/35 memory 512KiB L1 cache /0/36 memory 2MiB L2 cache /0/37 memory 16MiB L3 cache /0/38 processor Intel(R) Core(TM) i7-10700 CP /0/100 bridge Intel Corporation /0/100/1bridge Xeon E3-1200 v5/E3-1500 v5/6t /0/100/1/0 displayTU106 [GeForce RTX 2060 Rev. /0/100/1/0.1multimedia TU106 High Definition Audio C /0/100/1/0.2busTU106 USB 3.1 Host Controller /0/100/1/0.2/0 usb3 busxHCI Host Controller /0/100/1/0.2/1 usb4 busxHCI Host Controller /0/100/1/0.3busTU106 USB Type-C UCSI Control /0/100/2displayIntel Corporation /0/100/4genericXeon E3-1200 v5/E3-1500 v5/6t /0/100/8genericXeon E3-1200 v5/v6 / E3-1500 /0/100/12 genericComet Lake PCH Thermal Contro /0/100/14 busComet Lake USB 3.1 xHCI Host /0/100/14/0usb1 busxHCI Host Controller /0/100/14/0/4 enx0c5b8f279a64 communication HUAWEI_MOBILE /0/100/14/0/5 input Dell MS116 USB Optical Mouse /0/100/14/0/6 input Dell KB216 Wired Keyboard /0/100/14/0/b genericUSB2.0-CRW /0/100/14/0/c genericUB91C /0/100/14/0/e communication Bluetooth wireless interface /0/100/14/1usb2 busxHCI Host Controller /0/100/14.2 memory RAM memory /0/100/14.3wlo1 networkWi-Fi 6 AX201 /0/100/15 busComet Lake PCH Serial IO I2C /0/100/16 communication Comet Lake HECI Controller /0/100/17 storageIntel Corporation /0/100/1b bridge Comet Lake PCI Express Root P /0/100/1b/0 storageSamsung Electronics Co Ltd /0/100/1b/0/0 /dev/nvme0 storagePM991 NVMe Samsung 512GB /0/100/1b/0/0/1/dev/nvme0n1 disk 512GB NVMe namespace /0/100/1b/0/0/1/1 volume 149MiB Windows FAT volume /0/100/1b/0/0/1/2 /dev/nvme0n1p2 volume 127MiB reserved partition /0/100/1b/0/0/1/3 /dev/nvme0n1p3 volume 214GiB Windows NTFS volume /0/100/1b/0/0/1/4 /dev/nvme0n1p4 volume 989MiB Windows NTFS volume /0/100/1b/0/0/1/5 /dev/nvme0n1p5 volume 16GiB Windows NTFS volume /0/100/1b/0/0/1/6 /dev/nvme0n1p6 volume 1417MiB Windows NTFS volume /0/100/1b/0/0/1/7 /dev/nvme0n1p7 volume 243GiB EXT4 volume /0/100/1c bridge Intel Corporation /0/100/1c/0enp3s0 networkRealtek Semiconductor Co., Lt /0/100/1f bridge Intel Corporation
[Kernel-packages] [Bug 1931001] Re: kernel: watchdog: BUG: soft lockup - CPU#3 stuck for 22s!
Hi, vcarceler. Can you give complete dmesg from when this happens? Thanks for you report. 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/1931001 Title: kernel: watchdog: BUG: soft lockup - CPU#3 stuck for 22s! Status in linux package in Ubuntu: New Bug description: Ubuntu 20.04 LTS and Ubuntu 21.04 occasionally boots with very bad performance and very unresponsive to user input on Lenovo laptop Lenovo 300e 2nd Gen 81M9 (LENOVO_MT_81M9_BU_idea_FM_300e 2nd G). When this happens you can read this kind of messages on journal: --- root@alumne-1-58:~# journalctl | grep "BUG: soft" may 20 21:44:35 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [swapper/3:0] may 20 21:44:35 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [swapper/3:0] may 22 09:33:34 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [swapper/0:0] may 24 16:45:14 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#1 stuck for 23s! [prometheus-node:4220] may 24 16:45:14 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#0 stuck for 23s! [swapper/0:0] jun 03 00:01:09 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [swapper/0:0] jun 03 00:01:09 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#0 stuck for 23s! [swapper/0:0] jun 03 00:01:09 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#1 stuck for 22s! [swapper/1:0] jun 03 00:01:09 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [swapper/0:0] jun 03 00:02:15 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#0 stuck for 21s! [swapper/0:0] jun 05 08:22:58 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [irq/138-iwlwifi:1044] jun 05 08:25:06 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#2 stuck for 22s! [swapper/2:0] jun 05 08:25:06 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [irq/138-iwlwifi:1044] jun 05 08:26:42 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#1 stuck for 23s! [lxd:3975] jun 05 08:26:42 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#2 stuck for 23s! [swapper/2:0] jun 05 08:26:42 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#3 stuck for 23s! [irq/138-iwlwifi:1044] jun 05 08:27:38 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#3 stuck for 23s! [irq/138-iwlwifi:1044] jun 05 08:28:34 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [irq/138-iwlwifi:1044] jun 05 08:29:46 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [irq/138-iwlwifi:1044] root@alumne-1-58:~# --- Usually if you reboot everything works fine but it's very annoying when happens. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1931001/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1931105] Re: Sleep issue on ubuntu 21.04, CPU AMD 5700u
** Tags added: hirsute ** Package changed: ubuntu => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1931105 Title: Sleep issue on ubuntu 21.04, CPU AMD 5700u Status in linux package in Ubuntu: New Bug description: System Info Dell Inspiron 5515 Operating System: Kubuntu 21.04 Kernel Version: 5.12.9-051209-generic OS Type: 64-bit Processors: 16 × AMD Ryzen 7 5700U with Radeon Graphics Memory: 15,1 GiB of RAM Graphics Processor: AMD RENOIR If I suspend my pc, the screen, fans and keyboard backlight turn off. However if I try to wake up from suspension the screen stays black, while the keyboard backlight starts blinking. The only way to unlock it is to click the power button, and the pc will automatically restart (thus losing the data of the active session). Initially I had the 5.11 kernel, then to see if the problem was solved I tried to install the 5.12 kernel and the 5.12.9 kernel, but there were no improvements. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1931105/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1931106] Re: bnxt_en NIC driver crashes IO_PAGE_FAULT
** Attachment added: "apport.linux-image-5.8.0-55-generic.cime34c6.apport" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1931106/+attachment/5502930/+files/apport.linux-image-5.8.0-55-generic.cime34c6.apport -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1931106 Title: bnxt_en NIC driver crashes IO_PAGE_FAULT Status in linux package in Ubuntu: New Bug description: Hi all, We received a bunch of new servers with a Supermicro H12SSL-NT mainboard that has an embedded Broadcom BCM57416 NIC. On all those servers we observe crashes of the NIC driver (bnxt_en) from time to time. We're not able to manually reproduce this issue, it just occurs at some point. Also our monitoring does not show any irregularities(high traffic flow or sth. like this). Syslog: https://pastebin.com/yDAyjHvF All servers are running with up-to-date packages: $ lsb_release -rd Description: Ubuntu 20.04.2 LTS Release: 20.04 $ uname -r 5.4.0-73-generic It also happens on older kernel versions (tested 5.4.0-66) as well as the HWE kernel (tested 5.8.0-55). Thanks in advance. ~ Roman To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1931106/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1931106] [NEW] bnxt_en NIC driver crashes IO_PAGE_FAULT
Public bug reported: Hi all, We received a bunch of new servers with a Supermicro H12SSL-NT mainboard that has an embedded Broadcom BCM57416 NIC. On all those servers we observe crashes of the NIC driver (bnxt_en) from time to time. We're not able to manually reproduce this issue, it just occurs at some point. Also our monitoring does not show any irregularities(high traffic flow or sth. like this). Syslog: https://pastebin.com/yDAyjHvF All servers are running with up-to-date packages: $ lsb_release -rd Description: Ubuntu 20.04.2 LTS Release: 20.04 $ uname -r 5.4.0-73-generic It also happens on older kernel versions (tested 5.4.0-66) as well as the HWE kernel (tested 5.8.0-55). Thanks in advance. ~ Roman ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1931106 Title: bnxt_en NIC driver crashes IO_PAGE_FAULT Status in linux package in Ubuntu: New Bug description: Hi all, We received a bunch of new servers with a Supermicro H12SSL-NT mainboard that has an embedded Broadcom BCM57416 NIC. On all those servers we observe crashes of the NIC driver (bnxt_en) from time to time. We're not able to manually reproduce this issue, it just occurs at some point. Also our monitoring does not show any irregularities(high traffic flow or sth. like this). Syslog: https://pastebin.com/yDAyjHvF All servers are running with up-to-date packages: $ lsb_release -rd Description: Ubuntu 20.04.2 LTS Release: 20.04 $ uname -r 5.4.0-73-generic It also happens on older kernel versions (tested 5.4.0-66) as well as the HWE kernel (tested 5.8.0-55). Thanks in advance. ~ Roman To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1931106/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1931105] [NEW] Sleep issue on ubuntu 21.04, CPU AMD 5700u
You have been subscribed to a public bug: System Info Dell Inspiron 5515 Operating System: Kubuntu 21.04 Kernel Version: 5.12.9-051209-generic OS Type: 64-bit Processors: 16 × AMD Ryzen 7 5700U with Radeon Graphics Memory: 15,1 GiB of RAM Graphics Processor: AMD RENOIR If I suspend my pc, the screen, fans and keyboard backlight turn off. However if I try to wake up from suspension the screen stays black, while the keyboard backlight starts blinking. The only way to unlock it is to click the power button, and the pc will automatically restart (thus losing the data of the active session). Initially I had the 5.11 kernel, then to see if the problem was solved I tried to install the 5.12 kernel and the 5.12.9 kernel, but there were no improvements. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: hirsute -- Sleep issue on ubuntu 21.04, CPU AMD 5700u https://bugs.launchpad.net/bugs/1931105 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1926030] Re: IR Remote Keys Repeat Many Times Starting with Kernel 5.8.0-49
** No longer affects: focal (Ubuntu)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1926030
Title:
IR Remote Keys Repeat Many Times Starting with Kernel 5.8.0-49
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Groovy:
Fix Committed
Bug description:
[Impact]
Patch:
* media: rc: fix timeout handling after switch to microsecond durations
* media: rc: ite-cir: fix min_timeout calculation
Were applied to Groovy with our stable update process (bug 1918516)
User reported that IR Remote key press will be repeated for multiple times
with these patches applied.
Commit 528222d853f92 ("media: rc: harmonize infrared durations to
microseconds") that needs to be fixed by these two does not exist in
5.8 kernel. The patch author Matthias Reichl also state these are for
5.10 and onward.
[Fix]
Revert these two patches for groovy.
[Test]
Test kernels for G-5.8 / F-5.8 can be found here:
https://people.canonical.com/~phlin/kernel/lp-1926030-revert-for-ir/
User Ted L confirmed that F-5.8 test kernel can fix the problem.
[Where problems could occur]
The chance to cause regression can be considered as low since the original
patch that need to be fix by these two patches does not exist in 5.8 at all.
[Original Bug Report]
I use an IR remote with the ir-keytable package. Everything was working fine
until kernel 5.8.0-49 was automatically installed by Software Updater on Ubuntu
20.04.2. When any key is pressed on the remote, the key is repeated about 500
times. The kernel is now 5.8.0-50, and the problem persists.
Other users on the MythTV mailing list are reporting the issue, and it
appears that the problem is related to changes in the following files:
drivers/media/rc/ir-mce_kbd-decoder.c
drivers/media/rc/rc-main.c b/drivers/media/rc/rc-main.c
drivers/media/rc/serial_ir.c
It has been reported that reverting the ir-mce_kbd-decoder.c and rc-
main.c files to the older versions fixes the problem.
/proc/version_signature > version.log:
Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18
lspci -vnvn:
00:00.0 Host bridge [0600]: Intel Corporation Xeon E3-1200 v6/7th Gen Core
Processor Host Bridge/DRAM Registers [8086:590f] (rev 06)
Subsystem: ASUSTeK Computer Inc. Xeon E3-1200 v6/7th Gen Core Processor Host
Bridge/DRAM Registers [1043:8694]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR-
Kernel driver in use: skl_uncore
ir-keytable -V:
IR keytable control version 1.18.0
lsb_release -rd:
Description: Ubuntu 20.04.2 LTS
Release: 20.04
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.16
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: ted1020 F pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 20.04
InstallationDate: Installed on 2020-09-19 (217 days ago)
InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
IwConfig:
lono wireless extensions.
enp3s0no wireless extensions.
enp0s31f6 no wireless extensions.
MachineType: System manufacturer System Product Name
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.8.0-50-generic
root=UUID=529cae8e-19cd-4732-80d5-b3dca123afc6 ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18
RelatedPackageVersions:
linux-restricted-modules-5.8.0-50-generic N/A
linux-backports-modules-5.8.0-50-generic N/A
linux-firmware1.187.11
RfKill:
Tags: focal
Uname: Linux 5.8.0-50-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin lxd mythtv plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 07/05/2017
dmi.bios.release: 5.12
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 3405
dmi.board.asset.tag: Default string
dmi.board.name: H110T
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev X.0x
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvr3405:bd07/05/2017:br5.12:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH110T:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: System Product Name
dmi.product.sku: SKU
dmi.product.version: System Version
[Kernel-packages] [Bug 1930733] Re: Kernel oops with the 460.80 and 465.27 drivers when using DP, but not with HDMI
** Changed in: nvidia-graphics-drivers-460 (Ubuntu) Status: Confirmed => Triaged ** Changed in: nvidia-graphics-drivers-465 (Ubuntu) Status: Confirmed => Triaged ** Changed in: nvidia-graphics-drivers-460 (Ubuntu) Importance: Undecided => High ** Changed in: nvidia-graphics-drivers-465 (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-460 in Ubuntu. https://bugs.launchpad.net/bugs/1930733 Title: Kernel oops with the 460.80 and 465.27 drivers when using DP, but not with HDMI Status in nvidia-graphics-drivers-460 package in Ubuntu: Triaged Status in nvidia-graphics-drivers-465 package in Ubuntu: Triaged Bug description: I get a kernel oops with the 460.80 and 465.27 drivers on Hirsute Jun 03 16:26:57 willow kernel: Oops: [#1] SMP PTI Jun 03 16:26:57 willow kernel: CPU: 7 PID: 2004 Comm: Xorg Tainted: P OE 5.11.0-18-generic #19-Ubuntu Jun 03 16:26:57 willow kernel: Hardware name: System manufacturer System Product Name/PRIME H270M-PLUS, BIOS 1605 12/13/2019 Jun 03 16:26:57 willow kernel: RIP: 0010:_nv015534rm+0x1b6/0x330 [nvidia] Jun 03 16:26:57 willow kernel: Code: 8b 87 68 05 00 00 ba 01 00 00 00 be 02 00 00 00 e8 bf eb 55 c8 41 83 c5 01 41 83 fd 1f 0f 84 0b 01 00 00 48 8b 45 10 44 89 ee <48> 8b b8 70 01 00 00 48 8b 87 d8 04 00 00 e8> Jun 03 16:26:57 willow kernel: RSP: :af4201893958 EFLAGS: 00010297 Jun 03 16:26:57 willow kernel: RAX: RBX: 0400 RCX: 0003 Jun 03 16:26:57 willow kernel: RDX: 0004 RSI: 0003 RDI: Jun 03 16:26:57 willow kernel: RBP: 8e318220add0 R08: 0001 R09: 8e318220acb8 Jun 03 16:26:57 willow kernel: R10: 8e3182204008 R11: 1010 R12: 0400 Jun 03 16:26:57 willow kernel: R13: 0003 R14: 8e3186ca8010 R15: 0800 Jun 03 16:26:57 willow kernel: FS: 7f5807f38a40() GS:8e3466dc() knlGS: Jun 03 16:26:57 willow kernel: CS: 0010 DS: ES: CR0: 80050033 Jun 03 16:26:57 willow kernel: CR2: 0170 CR3: 000140710005 CR4: 003706e0 Jun 03 16:26:57 willow kernel: DR0: DR1: DR2: Jun 03 16:26:57 willow kernel: DR3: DR6: fffe0ff0 DR7: 0400 Jun 03 16:26:57 willow kernel: Call Trace: Jun 03 16:26:57 willow kernel: ? _nv015556rm+0x7fd/0x1020 [nvidia] Jun 03 16:26:57 willow kernel: ? _nv027155rm+0x22c/0x4f0 [nvidia] Jun 03 16:26:57 willow kernel: ? _nv017787rm+0x303/0x5e0 [nvidia] Jun 03 16:26:57 willow kernel: ? _nv017789rm+0xe1/0x220 [nvidia] Jun 03 16:26:57 willow kernel: ? _nv022829rm+0xed/0x220 [nvidia] Jun 03 16:26:57 willow kernel: ? _nv023065rm+0x30/0x60 [nvidia] Jun 03 16:26:57 willow kernel: ? _nv000704rm+0x16da/0x22b0 [nvidia] Jun 03 16:26:57 willow kernel: ? rm_init_adapter+0xc5/0xe0 [nvidia] Jun 03 16:26:57 willow kernel: ? nv_open_device+0x122/0x8e0 [nvidia] Jun 03 16:26:57 willow kernel: ? nvidia_open+0x2b7/0x560 [nvidia] Jun 03 16:26:57 willow kernel: ? nvidia_frontend_open+0x58/0xa0 [nvidia] Jun 03 16:26:57 willow kernel: ? chrdev_open+0xf7/0x220 Jun 03 16:26:57 willow kernel: ? cdev_device_add+0x90/0x90 Jun 03 16:26:57 willow kernel: ? do_dentry_open+0x156/0x370 Jun 03 16:26:57 willow kernel: ? vfs_open+0x2d/0x30 Jun 03 16:26:57 willow kernel: ? do_open+0x1c3/0x340 Jun 03 16:26:57 willow kernel: ? path_openat+0x10a/0x1d0 Jun 03 16:26:57 willow kernel: ? do_filp_open+0x8c/0x130 Jun 03 16:26:57 willow kernel: ? __check_object_size+0x1c/0x20 Jun 03 16:26:57 willow kernel: ? do_sys_openat2+0x9b/0x150 Jun 03 16:26:57 willow kernel: ? __x64_sys_openat+0x56/0x90 Jun 03 16:26:57 willow kernel: ? do_syscall_64+0x38/0x90 Jun 03 16:26:57 willow kernel: ? entry_SYSCALL_64_after_hwframe+0x44/0xa9 Jun 03 16:26:57 willow kernel: Modules linked in: snd_seq_dummy snd_hrtimer vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) binfmt_misc zfs(PO) zunicode(PO) zzstd(O) zlua(O) zavl(PO) icp(PO) zcommon(PO) znvpair(PO) > Jun 03 16:26:57 willow kernel: sunrpc ip_tables x_tables autofs4 btrfs blake2b_generic xor raid6_pq libcrc32c hid_generic usbhid hid crct10dif_pclmul crc32_pclmul ghash_clmulni_intel aesni_intel crypto_simd c> Jun 03 16:26:57 willow kernel: CR2: 0170 Jun 03 16:26:57 willow kernel: ---[ end trace 0013b6989b267f32 ]--- Jun 03 16:26:57 willow kernel: RIP: 0010:_nv015534rm+0x1b6/0x330 [nvidia] Jun 03 16:26:57 willow kernel: Code: 8b 87 68 05 00 00 ba 01 00 00 00 be 02 00 00 00 e8 bf eb 55 c8 41 83 c5 01 41 83 fd 1f 0f 84 0b 01 00 00 48 8b 45 10 44 89 ee <48> 8b b8 70 01 00 00 48 8b 87 d8 04 00 00 e8> Jun 03 16:26:57 willow kernel: RSP: :af4201893958 EFLAGS: 00010297
Re: [Kernel-packages] [Bug 1930422] Re: thermald_1.9.1-1ubuntu0.4_amd64 breaks system
wow it's running like a fridge! cheers. On 07/06/2021 03:23, Srinivas Pandruvada wrote: > Please try this version > https://github.com/intel/thermal_daemon/tree/ubuntu-bug-1930422 > > checkout branch ubuntu-bug-1930422. > Then repeat comments at #11 > ** Attachment added: "branch-output.txt" https://bugs.launchpad.net/bugs/1930422/+attachment/5502925/+files/branch-output.txt ** Attachment added: "Screenshot from 2021-06-07 11-40-29.png" https://bugs.launchpad.net/bugs/1930422/+attachment/5502926/+files/Screenshot%20from%202021-06-07%2011-40-29.png -- 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/1930422 Title: thermald_1.9.1-1ubuntu0.4_amd64 breaks system Status in thermald package in Ubuntu: New Bug description: cpu runs at 100c fan at 3000rpm when in heavy use previous version was ok re: https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/1913186 lshw -short is: H/W path Device Class Description == system XPS 8940 (09C5) /0 bus0KV3RP /0/0memory 64KiB BIOS /0/9memory 16GiB System Memory /0/9/0 memory 8GiB DIMM DDR4 Synchronous 32 /0/9/1 memory 8GiB DIMM DDR4 Synchronous 32 /0/9/2 memory Project-Id-Version: lshwRepor /0/9/3 memory Project-Id-Version: lshwRepor /0/35 memory 512KiB L1 cache /0/36 memory 2MiB L2 cache /0/37 memory 16MiB L3 cache /0/38 processor Intel(R) Core(TM) i7-10700 CP /0/100 bridge Intel Corporation /0/100/1bridge Xeon E3-1200 v5/E3-1500 v5/6t /0/100/1/0 displayTU106 [GeForce RTX 2060 Rev. /0/100/1/0.1multimedia TU106 High Definition Audio C /0/100/1/0.2busTU106 USB 3.1 Host Controller /0/100/1/0.2/0 usb3 busxHCI Host Controller /0/100/1/0.2/1 usb4 busxHCI Host Controller /0/100/1/0.3busTU106 USB Type-C UCSI Control /0/100/2displayIntel Corporation /0/100/4genericXeon E3-1200 v5/E3-1500 v5/6t /0/100/8genericXeon E3-1200 v5/v6 / E3-1500 /0/100/12 genericComet Lake PCH Thermal Contro /0/100/14 busComet Lake USB 3.1 xHCI Host /0/100/14/0usb1 busxHCI Host Controller /0/100/14/0/4 enx0c5b8f279a64 communication HUAWEI_MOBILE /0/100/14/0/5 input Dell MS116 USB Optical Mouse /0/100/14/0/6 input Dell KB216 Wired Keyboard /0/100/14/0/b genericUSB2.0-CRW /0/100/14/0/c genericUB91C /0/100/14/0/e communication Bluetooth wireless interface /0/100/14/1usb2 busxHCI Host Controller /0/100/14.2 memory RAM memory /0/100/14.3wlo1 networkWi-Fi 6 AX201 /0/100/15 busComet Lake PCH Serial IO I2C /0/100/16 communication Comet Lake HECI Controller /0/100/17 storageIntel Corporation /0/100/1b bridge Comet Lake PCI Express Root P /0/100/1b/0 storageSamsung Electronics Co Ltd /0/100/1b/0/0 /dev/nvme0 storagePM991 NVMe Samsung 512GB /0/100/1b/0/0/1/dev/nvme0n1 disk 512GB NVMe namespace /0/100/1b/0/0/1/1 volume 149MiB Windows FAT volume /0/100/1b/0/0/1/2 /dev/nvme0n1p2 volume 127MiB reserved partition /0/100/1b/0/0/1/3 /dev/nvme0n1p3 volume 214GiB Windows NTFS volume /0/100/1b/0/0/1/4 /dev/nvme0n1p4 volume 989MiB Windows NTFS volume /0/100/1b/0/0/1/5 /dev/nvme0n1p5 volume 16GiB Windows NTFS volume /0/100/1b/0/0/1/6 /dev/nvme0n1p6 volume 1417MiB Windows NTFS volume /0/100/1b/0/0/1/7 /dev/nvme0n1p7 volume 243GiB EXT4 volume /0/100/1c bridge Intel Corporation /0/100/1c/0enp3s0
[Kernel-packages] [Bug 1839912] Re: test_map in ubuntu_bpf failed with "Allowed update sockmap '0:3' not in ESTABLISHED"
** Description changed: + [Impact] + test_maps bpf selftests is failing on bionic. + + [Regression potential] + Kernel is not changed, but test may give a false pass with this change. + + [Test case] + The fixed test has been run on the kernel in -proposed, and passes. + After building it, just run ./test_maps from tools/testing/selftests/bpf/. + + -- + This is at lease a test case regression with the proposed kernel: selftests: test_maps Allowed update sockmap '0:3' not in ESTABLISHED not ok 1..3 selftests: test_maps [FAIL] But with older kernel: selftests: test_maps test_maps: OK ok 1..3 selftests: test_maps [PASS] ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-58-generic 4.15.0-58.64 ProcVersionSignature: User Name 4.15.0-58.64-generic 4.15.18 Uname: Linux 4.15.0-58-generic x86_64 AlsaDevices: - total 0 - crw-rw 1 root audio 116, 1 Aug 13 03:42 seq - crw-rw 1 root audio 116, 33 Aug 13 03:42 timer + total 0 + crw-rw 1 root audio 116, 1 Aug 13 03:42 seq + crw-rw 1 root audio 116, 33 Aug 13 03:42 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Tue Aug 13 03:52:52 2019 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: Intel Corporation S1200RP PciMultimedia: - + ProcFB: 0 mgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-58-generic root=UUID=b0d2ae4e-12dd-423e-acea-272ee8b2a893 ro RelatedPackageVersions: - linux-restricted-modules-4.15.0-58-generic N/A - linux-backports-modules-4.15.0-58-generic N/A - linux-firmware 1.173.10 + linux-restricted-modules-4.15.0-58-generic N/A + linux-backports-modules-4.15.0-58-generic N/A + linux-firmware 1.173.10 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/01/2015 dmi.bios.vendor: Intel Corp. dmi.bios.version: S1200RP.86B.03.02.0003.070120151022 dmi.board.asset.tag: dmi.board.name: S1200RP dmi.board.vendor: Intel Corporation dmi.board.version: G62254-407 dmi.chassis.asset.tag: dmi.chassis.type: 17 dmi.chassis.vendor: .. dmi.chassis.version: .. dmi.modalias: dmi:bvnIntelCorp.:bvrS1200RP.86B.03.02.0003.070120151022:bd07/01/2015:svnIntelCorporation:pnS1200RP:pvr:rvnIntelCorporation:rnS1200RP:rvrG62254-407:cvn..:ct17:cvr..: dmi.product.family: To be filled by O.E.M. dmi.product.name: S1200RP dmi.product.version: dmi.sys.vendor: Intel Corporation -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1839912 Title: test_map in ubuntu_bpf failed with "Allowed update sockmap '0:3' not in ESTABLISHED" Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: In Progress Bug description: [Impact] test_maps bpf selftests is failing on bionic.
[Kernel-packages] [Bug 1929527] Re: Mark kprobe_args_user.tc in kselftest/ftrace as unsupported
Works as expected in 5.4.0-75.84-generic on Focal s390x
# [41] Kprobe event user-memory access [UNSUPPORTED]
** Tags removed: verification-needed-focal
** Tags added: verification-done-focal
** Tags added: 5.4 focal ubuntu-kernel-selftests
--
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/1929527
Title:
Mark kprobe_args_user.tc in kselftest/ftrace as unsupported
Status in ubuntu-kernel-tests:
In Progress
Status in linux package in Ubuntu:
Fix Released
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:
In Progress
Bug description:
[Impact]
This kprobe_args_user.tc test will be marked as "unresolved" and once causing
failures in ftrace of our ubuntu_kernel_selftests (lp:1869227)
Our workaround is to blacklist this test in autotest-client-tests [1]
Note that with patch b730d668138cb3 ("ftrace/selftest: make unresolved
cases cause failure if --fail-unresolved set") available, an
unresolved case will not be treated as a failure unless we requested
so.
[1] https://kernel.ubuntu.com/git/ubuntu/autotest-client-
tests.git/commit/ubuntu_kernel_selftests/ubuntu_kernel_selftests.py?id=a381d47a9004388730e825cd20566ef102a29399
[Fix]
* 1e11b7dbef17bb selftests/ftrace: Return unsupported for the unconfigured
features
With this patch it will be marked as unsupported, easier to understand
than unresolved.
This patch can be found in Groovy and newer releases, and this test
does not exist in Bionic and older releases.
[Test]
Tested on s390x / PowerPC, this will be marked as unsupported:
$ sudo ./ftracetest test.d/kprobe/kprobe_args_user.tc
=== Ftrace unit tests ===
[1] Kprobe event user-memory access [UNSUPPORTED]
# of passed: 0
# of failed: 0
# of unresolved: 0
# of untested: 0
# of unsupported: 1
# of xfailed: 0
# of undefined(test bug): 0
$ echo $?
0
[Where problems could occur]
Changes limited to testing tool, should not impact real kernel functionality.
With this patch and local workaround in autotest-client-tests removed we might
see failures in s390x / PowerPC in the future.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1929527/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1929646] Re: [SRU][OEM-5.10/H] Fix typec output on AMD Cezanne GPU
Verified on oem-5.10-1030, external monitor works fine after suspend. ** Tags removed: verification-needed-focal ** Tags added: verification-done-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/1929646 Title: [SRU][OEM-5.10/H] Fix typec output on AMD Cezanne GPU Status in HWE Next: New Status in linux package in Ubuntu: New Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux-oem-5.10 source package in Focal: Fix Committed Status in linux source package in Hirsute: Fix Committed Bug description: SRU justification: [Impact] Display can't work when replug in after suspend on AMD Cezanne platform. [Fix] Enable display power gating, display of typec will work as expected. [Test] Verified on hardware, suspend then replug the cable of typec, repeat for 10 times, all good. [Where problems could occur] The AMD typec output may not output. Unstable kernel already got it, only for OEM-5.10/H. Minor changes during backport. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1929646/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1925209] Re: No iwilwifi driver in Linux 5.4.0-1034-raspi
This bug was fixed in the package linux-raspi - 5.8.0-1026.29 --- linux-raspi (5.8.0-1026.29) groovy; urgency=medium * groovy/linux-raspi: 5.8.0-1026.29 -proposed tracker (LP: #1930377) [ Ubuntu: 5.8.0-55.62 ] * groovy/linux: 5.8.0-55.62 -proposed tracker (LP: #1930379) * [Potential Regression] Unable to create KVM with uvtool on Groovy ARM64 (LP: #1929925) - SAUCE: KVM: arm64: Assign kvm_ipa_limit linux-raspi (5.8.0-1025.28) groovy; urgency=medium * groovy/linux-raspi: 5.8.0-1025.28 -proposed tracker (LP: #1927588) * Groovy update: upstream stable patchset 2021-04-27 (LP: #1926360) - [Config] raspi: Remove CONFIG_VFIO debian.raspi overrides and follow master * Groovy update: upstream stable patchset 2021-04-20 (LP: #1925259) - [Config] raspi: updateconfigs for PCIE_BW - [Packaging] raspi: update modules for rc-cec * Raspberry Pi kernel config doesn't match generic for NFT, breaks LXD (LP: #1927108) - [Config] raspi: SET NFT_FIB_INET=m * Support Auvidea B101 (TC358743) (LP: #1926755) - [Config] raspi: Set VIDEO_TC358743=m * No iwilwifi driver in Linux 5.4.0-1034-raspi (LP: #1925209) - [Config] raspi: Set IWLWIFI=m [ Ubuntu: 5.8.0-54.61 ] * groovy/linux: 5.8.0-54.61 -proposed tracker (LP: #1927592) * Introduce the 465 driver series, fabric-manager, and libnvidia-nscq (LP: #1925522) - debian/dkms-versions -- add NVIDIA 465 and migrate 450 to 460 * linux-image-5.0.0-35-generic breaks checkpointing of container (LP: #1857257) - SAUCE: overlayfs: fix incorrect mnt_id of files opened from map_files * netfilter: x_tables: fix compat match/target pad out-of-bound write (LP: #1927682) - netfilter: x_tables: fix compat match/target pad out-of-bound write * Groovy update: upstream stable patchset 2021-05-04 (LP: #1927150) - mt76: fix tx skb error handling in mt76_dma_tx_queue_skb - net: fec: ptp: avoid register access when ipg clock is disabled - powerpc/4xx: Fix build errors from mfdcr() - atm: eni: dont release is never initialized - atm: lanai: dont run lanai_dev_close if not open - Revert "r8152: adjust the settings about MAC clock speed down for RTL8153" - ALSA: hda: ignore invalid NHLT table - ixgbe: Fix memleak in ixgbe_configure_clsu32 - scsi: ufs: ufs-qcom: Disable interrupt in reset path - blk-cgroup: Fix the recursive blkg rwstat - net: tehuti: fix error return code in bdx_probe() - net: intel: iavf: fix error return code of iavf_init_get_resources() - sun/niu: fix wrong RXMAC_BC_FRM_CNT_COUNT count - cifs: ask for more credit on async read/write code paths - gfs2: fix use-after-free in trans_drain - cpufreq: blacklist Arm Vexpress platforms in cpufreq-dt-platdev - gpiolib: acpi: Add missing IRQF_ONESHOT - nfs: fix PNFS_FLEXFILE_LAYOUT Kconfig default - NFS: Correct size calculation for create reply length - net: hisilicon: hns: fix error return code of hns_nic_clear_all_rx_fetch() - net: wan: fix error return code of uhdlc_init() - net: davicom: Use platform_get_irq_optional() - net: enetc: set MAC RX FIFO to recommended value - atm: uPD98402: fix incorrect allocation - atm: idt77252: fix null-ptr-dereference - cifs: change noisy error message to FYI - irqchip/ingenic: Add support for the JZ4760 - kbuild: add image_name to no-sync-config-targets - kbuild: dummy-tools: fix inverted tests for gcc - umem: fix error return code in mm_pci_probe() - sparc64: Fix opcode filtering in handling of no fault loads - habanalabs: Call put_pid() when releasing control device - staging: rtl8192e: fix kconfig dependency on CRYPTO - u64_stats,lockdep: Fix u64_stats_init() vs lockdep - regulator: qcom-rpmh: Correct the pmic5_hfsmps515 buck - block: Fix REQ_OP_ZONE_RESET_ALL handling - drm/amd/display: Revert dram_clock_change_latency for DCN2.1 - drm/amdgpu: fb BO should be ttm_bo_type_device - drm/radeon: fix AGP dependency - nvme: add NVME_REQ_CANCELLED flag in nvme_cancel_request() - nvme-fc: set NVME_REQ_CANCELLED in nvme_fc_terminate_exchange() - nvme-fc: return NVME_SC_HOST_ABORTED_CMD when a command has been aborted - nvme-rdma: Fix a use after free in nvmet_rdma_write_data_done - nvme-pci: add the DISABLE_WRITE_ZEROES quirk for a Samsung PM1725a - nfs: we don't support removing system.nfs4_acl - block: Suppress uevent for hidden device when removed - ia64: fix ia64_syscall_get_set_arguments() for break-based syscalls - ia64: fix ptrace(PTRACE_SYSCALL_INFO_EXIT) sign - netsec: restore phy power state after controller reset - platform/x86: intel-vbtn: Stop reporting SW_DOCK events - psample: Fix user API breakage - z3fold: prevent reclaim/free race for headless pages - squashfs: fix inode lookup sanity checks - squashfs: fix xattr id and id lookup sanity checks - hugetlb_cgroup: fix
[Kernel-packages] [Bug 1926755] Re: Support Auvidea B101 (TC358743)
This bug was fixed in the package linux-raspi - 5.8.0-1026.29 --- linux-raspi (5.8.0-1026.29) groovy; urgency=medium * groovy/linux-raspi: 5.8.0-1026.29 -proposed tracker (LP: #1930377) [ Ubuntu: 5.8.0-55.62 ] * groovy/linux: 5.8.0-55.62 -proposed tracker (LP: #1930379) * [Potential Regression] Unable to create KVM with uvtool on Groovy ARM64 (LP: #1929925) - SAUCE: KVM: arm64: Assign kvm_ipa_limit linux-raspi (5.8.0-1025.28) groovy; urgency=medium * groovy/linux-raspi: 5.8.0-1025.28 -proposed tracker (LP: #1927588) * Groovy update: upstream stable patchset 2021-04-27 (LP: #1926360) - [Config] raspi: Remove CONFIG_VFIO debian.raspi overrides and follow master * Groovy update: upstream stable patchset 2021-04-20 (LP: #1925259) - [Config] raspi: updateconfigs for PCIE_BW - [Packaging] raspi: update modules for rc-cec * Raspberry Pi kernel config doesn't match generic for NFT, breaks LXD (LP: #1927108) - [Config] raspi: SET NFT_FIB_INET=m * Support Auvidea B101 (TC358743) (LP: #1926755) - [Config] raspi: Set VIDEO_TC358743=m * No iwilwifi driver in Linux 5.4.0-1034-raspi (LP: #1925209) - [Config] raspi: Set IWLWIFI=m [ Ubuntu: 5.8.0-54.61 ] * groovy/linux: 5.8.0-54.61 -proposed tracker (LP: #1927592) * Introduce the 465 driver series, fabric-manager, and libnvidia-nscq (LP: #1925522) - debian/dkms-versions -- add NVIDIA 465 and migrate 450 to 460 * linux-image-5.0.0-35-generic breaks checkpointing of container (LP: #1857257) - SAUCE: overlayfs: fix incorrect mnt_id of files opened from map_files * netfilter: x_tables: fix compat match/target pad out-of-bound write (LP: #1927682) - netfilter: x_tables: fix compat match/target pad out-of-bound write * Groovy update: upstream stable patchset 2021-05-04 (LP: #1927150) - mt76: fix tx skb error handling in mt76_dma_tx_queue_skb - net: fec: ptp: avoid register access when ipg clock is disabled - powerpc/4xx: Fix build errors from mfdcr() - atm: eni: dont release is never initialized - atm: lanai: dont run lanai_dev_close if not open - Revert "r8152: adjust the settings about MAC clock speed down for RTL8153" - ALSA: hda: ignore invalid NHLT table - ixgbe: Fix memleak in ixgbe_configure_clsu32 - scsi: ufs: ufs-qcom: Disable interrupt in reset path - blk-cgroup: Fix the recursive blkg rwstat - net: tehuti: fix error return code in bdx_probe() - net: intel: iavf: fix error return code of iavf_init_get_resources() - sun/niu: fix wrong RXMAC_BC_FRM_CNT_COUNT count - cifs: ask for more credit on async read/write code paths - gfs2: fix use-after-free in trans_drain - cpufreq: blacklist Arm Vexpress platforms in cpufreq-dt-platdev - gpiolib: acpi: Add missing IRQF_ONESHOT - nfs: fix PNFS_FLEXFILE_LAYOUT Kconfig default - NFS: Correct size calculation for create reply length - net: hisilicon: hns: fix error return code of hns_nic_clear_all_rx_fetch() - net: wan: fix error return code of uhdlc_init() - net: davicom: Use platform_get_irq_optional() - net: enetc: set MAC RX FIFO to recommended value - atm: uPD98402: fix incorrect allocation - atm: idt77252: fix null-ptr-dereference - cifs: change noisy error message to FYI - irqchip/ingenic: Add support for the JZ4760 - kbuild: add image_name to no-sync-config-targets - kbuild: dummy-tools: fix inverted tests for gcc - umem: fix error return code in mm_pci_probe() - sparc64: Fix opcode filtering in handling of no fault loads - habanalabs: Call put_pid() when releasing control device - staging: rtl8192e: fix kconfig dependency on CRYPTO - u64_stats,lockdep: Fix u64_stats_init() vs lockdep - regulator: qcom-rpmh: Correct the pmic5_hfsmps515 buck - block: Fix REQ_OP_ZONE_RESET_ALL handling - drm/amd/display: Revert dram_clock_change_latency for DCN2.1 - drm/amdgpu: fb BO should be ttm_bo_type_device - drm/radeon: fix AGP dependency - nvme: add NVME_REQ_CANCELLED flag in nvme_cancel_request() - nvme-fc: set NVME_REQ_CANCELLED in nvme_fc_terminate_exchange() - nvme-fc: return NVME_SC_HOST_ABORTED_CMD when a command has been aborted - nvme-rdma: Fix a use after free in nvmet_rdma_write_data_done - nvme-pci: add the DISABLE_WRITE_ZEROES quirk for a Samsung PM1725a - nfs: we don't support removing system.nfs4_acl - block: Suppress uevent for hidden device when removed - ia64: fix ia64_syscall_get_set_arguments() for break-based syscalls - ia64: fix ptrace(PTRACE_SYSCALL_INFO_EXIT) sign - netsec: restore phy power state after controller reset - platform/x86: intel-vbtn: Stop reporting SW_DOCK events - psample: Fix user API breakage - z3fold: prevent reclaim/free race for headless pages - squashfs: fix inode lookup sanity checks - squashfs: fix xattr id and id lookup sanity checks - hugetlb_cgroup: fix
[Kernel-packages] [Bug 1927108] Re: Raspberry Pi kernel config doesn't match generic for NFT, breaks LXD
This bug was fixed in the package linux-raspi - 5.8.0-1026.29 --- linux-raspi (5.8.0-1026.29) groovy; urgency=medium * groovy/linux-raspi: 5.8.0-1026.29 -proposed tracker (LP: #1930377) [ Ubuntu: 5.8.0-55.62 ] * groovy/linux: 5.8.0-55.62 -proposed tracker (LP: #1930379) * [Potential Regression] Unable to create KVM with uvtool on Groovy ARM64 (LP: #1929925) - SAUCE: KVM: arm64: Assign kvm_ipa_limit linux-raspi (5.8.0-1025.28) groovy; urgency=medium * groovy/linux-raspi: 5.8.0-1025.28 -proposed tracker (LP: #1927588) * Groovy update: upstream stable patchset 2021-04-27 (LP: #1926360) - [Config] raspi: Remove CONFIG_VFIO debian.raspi overrides and follow master * Groovy update: upstream stable patchset 2021-04-20 (LP: #1925259) - [Config] raspi: updateconfigs for PCIE_BW - [Packaging] raspi: update modules for rc-cec * Raspberry Pi kernel config doesn't match generic for NFT, breaks LXD (LP: #1927108) - [Config] raspi: SET NFT_FIB_INET=m * Support Auvidea B101 (TC358743) (LP: #1926755) - [Config] raspi: Set VIDEO_TC358743=m * No iwilwifi driver in Linux 5.4.0-1034-raspi (LP: #1925209) - [Config] raspi: Set IWLWIFI=m [ Ubuntu: 5.8.0-54.61 ] * groovy/linux: 5.8.0-54.61 -proposed tracker (LP: #1927592) * Introduce the 465 driver series, fabric-manager, and libnvidia-nscq (LP: #1925522) - debian/dkms-versions -- add NVIDIA 465 and migrate 450 to 460 * linux-image-5.0.0-35-generic breaks checkpointing of container (LP: #1857257) - SAUCE: overlayfs: fix incorrect mnt_id of files opened from map_files * netfilter: x_tables: fix compat match/target pad out-of-bound write (LP: #1927682) - netfilter: x_tables: fix compat match/target pad out-of-bound write * Groovy update: upstream stable patchset 2021-05-04 (LP: #1927150) - mt76: fix tx skb error handling in mt76_dma_tx_queue_skb - net: fec: ptp: avoid register access when ipg clock is disabled - powerpc/4xx: Fix build errors from mfdcr() - atm: eni: dont release is never initialized - atm: lanai: dont run lanai_dev_close if not open - Revert "r8152: adjust the settings about MAC clock speed down for RTL8153" - ALSA: hda: ignore invalid NHLT table - ixgbe: Fix memleak in ixgbe_configure_clsu32 - scsi: ufs: ufs-qcom: Disable interrupt in reset path - blk-cgroup: Fix the recursive blkg rwstat - net: tehuti: fix error return code in bdx_probe() - net: intel: iavf: fix error return code of iavf_init_get_resources() - sun/niu: fix wrong RXMAC_BC_FRM_CNT_COUNT count - cifs: ask for more credit on async read/write code paths - gfs2: fix use-after-free in trans_drain - cpufreq: blacklist Arm Vexpress platforms in cpufreq-dt-platdev - gpiolib: acpi: Add missing IRQF_ONESHOT - nfs: fix PNFS_FLEXFILE_LAYOUT Kconfig default - NFS: Correct size calculation for create reply length - net: hisilicon: hns: fix error return code of hns_nic_clear_all_rx_fetch() - net: wan: fix error return code of uhdlc_init() - net: davicom: Use platform_get_irq_optional() - net: enetc: set MAC RX FIFO to recommended value - atm: uPD98402: fix incorrect allocation - atm: idt77252: fix null-ptr-dereference - cifs: change noisy error message to FYI - irqchip/ingenic: Add support for the JZ4760 - kbuild: add image_name to no-sync-config-targets - kbuild: dummy-tools: fix inverted tests for gcc - umem: fix error return code in mm_pci_probe() - sparc64: Fix opcode filtering in handling of no fault loads - habanalabs: Call put_pid() when releasing control device - staging: rtl8192e: fix kconfig dependency on CRYPTO - u64_stats,lockdep: Fix u64_stats_init() vs lockdep - regulator: qcom-rpmh: Correct the pmic5_hfsmps515 buck - block: Fix REQ_OP_ZONE_RESET_ALL handling - drm/amd/display: Revert dram_clock_change_latency for DCN2.1 - drm/amdgpu: fb BO should be ttm_bo_type_device - drm/radeon: fix AGP dependency - nvme: add NVME_REQ_CANCELLED flag in nvme_cancel_request() - nvme-fc: set NVME_REQ_CANCELLED in nvme_fc_terminate_exchange() - nvme-fc: return NVME_SC_HOST_ABORTED_CMD when a command has been aborted - nvme-rdma: Fix a use after free in nvmet_rdma_write_data_done - nvme-pci: add the DISABLE_WRITE_ZEROES quirk for a Samsung PM1725a - nfs: we don't support removing system.nfs4_acl - block: Suppress uevent for hidden device when removed - ia64: fix ia64_syscall_get_set_arguments() for break-based syscalls - ia64: fix ptrace(PTRACE_SYSCALL_INFO_EXIT) sign - netsec: restore phy power state after controller reset - platform/x86: intel-vbtn: Stop reporting SW_DOCK events - psample: Fix user API breakage - z3fold: prevent reclaim/free race for headless pages - squashfs: fix inode lookup sanity checks - squashfs: fix xattr id and id lookup sanity checks - hugetlb_cgroup: fix
[Kernel-packages] [Bug 1930188] Re: Acer Aspire 5 sound driver issues
Please install the testing pulseaudio, reboot and redo the test.This pulseaudio is for fixing the issue of "speaker and headphone share the same volume". https://launchpad.net/~hui.wang/+archive/ubuntu/pa-testing -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1930188 Title: Acer Aspire 5 sound driver issues Status in linux package in Ubuntu: New Bug description: Hello, There seems to be lots of issues in sound driver for Acer Aspire A515-56-57XR with ALC255. I will list all of them below and what I have tried so far. 1. Headphones appears always plugged in even if they are physically not 2. When actually plugging in headset/earphones it does not auto switch from speakers/internal mic to headphones/headset microphone automatically and vice versa, have to manually switch everytime. 3. External headset/earphones microphone won't work at all After, logs of trial and error I have found a temporary fix. This seems to use legacy intel drivers which solves all 3 issues mentioned above but the internal/dmic mic is completely gone (which seems intentional when using this). Both depreciated dmic_detect and dsp_driver works, I have been using dsp_driver for now as I need external microphone at any cost. End of /etc/modprobe.d/alsa-base.conf # Headset mic fix options snd-hda-intel dmic_detect=0 / options snd-intel-dspcfg dsp_driver=1 options snd-hda-intel model=alc255-acer In another thread similar to this I got some support and at least fixed the external microphone without using the alsa-base.conf change in custom modified kernel. I will attach it here. Now, hoping to fix other issues as well slowly like making headphones unplugged when physically removing as well as auto switching like the legacy driver one. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1930188/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1839912] Re: test_map in ubuntu_bpf failed with "Allowed update sockmap '0:3' not in ESTABLISHED"
** Changed in: linux (Ubuntu Bionic) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Bionic) 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/1839912 Title: test_map in ubuntu_bpf failed with "Allowed update sockmap '0:3' not in ESTABLISHED" Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: In Progress Bug description: This is at lease a test case regression with the proposed kernel: selftests: test_maps Allowed update sockmap '0:3' not in ESTABLISHED not ok 1..3 selftests: test_maps [FAIL] But with older kernel: selftests: test_maps test_maps: OK ok 1..3 selftests: test_maps [PASS] ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-58-generic 4.15.0-58.64 ProcVersionSignature: User Name 4.15.0-58.64-generic 4.15.18 Uname: Linux 4.15.0-58-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Aug 13 03:42 seq crw-rw 1 root audio 116, 33 Aug 13 03:42 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Tue Aug 13 03:52:52 2019 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: Intel Corporation S1200RP PciMultimedia: ProcFB: 0 mgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-58-generic root=UUID=b0d2ae4e-12dd-423e-acea-272ee8b2a893 ro RelatedPackageVersions: linux-restricted-modules-4.15.0-58-generic N/A linux-backports-modules-4.15.0-58-generic N/A linux-firmware 1.173.10 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/01/2015 dmi.bios.vendor: Intel Corp. dmi.bios.version: S1200RP.86B.03.02.0003.070120151022 dmi.board.asset.tag: dmi.board.name: S1200RP dmi.board.vendor: Intel Corporation dmi.board.version: G62254-407 dmi.chassis.asset.tag: dmi.chassis.type: 17 dmi.chassis.vendor: .. dmi.chassis.version: .. dmi.modalias: dmi:bvnIntelCorp.:bvrS1200RP.86B.03.02.0003.070120151022:bd07/01/2015:svnIntelCorporation:pnS1200RP:pvr:rvnIntelCorporation:rnS1200RP:rvrG62254-407:cvn..:ct17:cvr..: dmi.product.family: To be filled by O.E.M. dmi.product.name: S1200RP dmi.product.version: dmi.sys.vendor: Intel Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1839912/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
