[Kernel-packages] [Bug 1904884] Re: s390: dbginfo.sh triggers kernel panic, reading from /sys/kernel/mm/page_idle/bitmap
** Changed in: ubuntu-z-systems Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1904884 Title: s390: dbginfo.sh triggers kernel panic, reading from /sys/kernel/mm/page_idle/bitmap Status in Ubuntu on IBM z Systems: Fix Committed Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Committed Status in linux source package in Focal: Fix Committed Status in linux source package in Groovy: Fix Released Status in linux source package in Hirsute: Fix Released Bug description: SRU Justification: == [Impact] * While executing dbginfo.sh (a script to collect runtime, configuration, and trace information on s390x) the systems hangs. * This is because 'idle page tracking' users can pass random pfn, that might be mapped to an offline page - and attempts to access offline pages lead to the hang. * It needs to be avoided that such pages are accessed. * The upstream commit modifies 'page_idle_get_page()' to use 'pfn_to_online_page()' instead of a 'pfn_valid()' and 'pfn_to_page()' combination, so that the pfn mapped to an offline page is skipped. [Fix] * 92fb1db26eef "mm/page_idle.c: skip offline pages" [Test Case] * IBM Z or LinuxONE hardware with Ubuntu Server 18.04 (GA kernel, 4.15) installed. * Execute a test application that tries to access offline pages. * Or execute dbginfo.sh with having some offline (idle) pages in the system. [Regression Potential] * There is a certain regression risk, especially for bionic, since the structure in the kernel 4.15 is a bit different compared to kernel 5.4 (and newer). * However, for newer kernels the modification is pretty save, since it's upstream accepted since kernel 5.8 and with that already inluded in hirsute and groovy. * And the patch is fine (and cherry picks cleanly) for focal as well. * For bionic there is a slightly conflicting context, since the struct 'zone' was replaced by 'pg_data_t *pgdat' (by another commit: 92fb1db26eef), but that change (or any change to the struct zone) would not be necessary to fix the uninitialized struct page access. * Hence the upstream commit/patch needs to be adjusted/backported to bionic 4.15, largely by replacing line 'pg_data_t *pgdat;' with 'struct zone *zone;' (or actually leaving this line). * But this needs to be carefully considered, since the handling of idle pages could be harmful, in the end it could make things even worse, means break even more. [Other] * The patch got upstream accepted with kernel v5.8, hence it's already is in groovy and hirsute. * The upstream commit cherry picks cleanly to focal, but for bionic a backport is needed. * Hence this kernel SRU request is for focal (cherry-pick) and bionic (backport). __ System hangs on dbginfo.sh script execution. Solution: Commit 92fb1db26eef ("mm/page_idle.c: skip offline pages") Included upstream since kernel v5.8, so it is already included in Ubuntu 20.10, but not in 20.04 and earlier. Commit 92fb1db26eef ("mm/page_idle.c: skip offline pages") applies cleanly on ubuntu-focal, but not on ubuntu-bionic. Adjustment / backport for bionic should be trivial, but it is not IBM code and therefore the backport will be requested here by Canonical. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1904884/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1906095] [NEW] Fails to boot
Public bug reported: 1) Ubuntu 20.10 2) kernel 5.8.0-29-generic 3) To boot 4) Instead the boot screen only shows up on one monitor and freezes ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-5.8.0-29-generic 5.8.0-29.31 ProcVersionSignature: Ubuntu 5.8.0-29.31-generic 5.8.14 Uname: Linux 5.8.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.2 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Sat Nov 28 00:21:51 2020 InstallationDate: Installed on 2020-11-19 (8 days ago) InstallationMedia: Kubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: System manufacturer System Product Name ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-29-generic root=UUID=b19340a3-b1fa-4e95-88ea-3b3d2ff8e4f6 ro recovery nomodeset dis_ucode_ldr RelatedPackageVersions: linux-restricted-modules-5.8.0-29-generic N/A linux-backports-modules-5.8.0-29-generic N/A linux-firmware1.190.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/04/2020 dmi.bios.release: 5.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3201 dmi.board.asset.tag: Default string dmi.board.name: ROG STRIX X299-E GAMING 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.:bvr3201:bd09/04/2020:br5.13:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGSTRIXX299-EGAMING:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: ASUS_MB_KBLX dmi.product.version: System Version dmi.sys.vendor: System manufacturer ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug groovy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1906095 Title: Fails to boot Status in linux package in Ubuntu: New Bug description: 1) Ubuntu 20.10 2) kernel 5.8.0-29-generic 3) To boot 4) Instead the boot screen only shows up on one monitor and freezes ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-5.8.0-29-generic 5.8.0-29.31 ProcVersionSignature: Ubuntu 5.8.0-29.31-generic 5.8.14 Uname: Linux 5.8.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.2 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Sat Nov 28 00:21:51 2020 InstallationDate: Installed on 2020-11-19 (8 days ago) InstallationMedia: Kubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: System manufacturer System Product Name ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-29-generic root=UUID=b19340a3-b1fa-4e95-88ea-3b3d2ff8e4f6 ro recovery nomodeset dis_ucode_ldr RelatedPackageVersions: linux-restricted-modules-5.8.0-29-generic N/A linux-backports-modules-5.8.0-29-generic N/A linux-firmware1.190.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/04/2020 dmi.bios.release: 5.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3201 dmi.board.asset.tag: Default string dmi.board.name: ROG STRIX X299-E GAMING 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.:bvr3201:bd09/04/2020:br5.13:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGSTRIXX299-EGAMING:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: ASUS_MB_KBLX dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1906095/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1906088] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1906088 Title: Touchpad is not detected and not responsive Status in linux package in Ubuntu: Confirmed Bug description: 1. See attachment 2. Vendor is Microsoft ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-54-generic 5.4.0-54.60 ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65 Uname: Linux 5.4.0-54-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: niteshb1201 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Nov 28 11:00:25 2020 InstallationDate: Installed on 2020-11-28 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 046d:c52f Logitech, Inc. Unifying Receiver Bus 001 Device 002: ID 174f:1176 Syntek Integrated Camera Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 81WD ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-54-generic root=UUID=c57708b6-f80b-474d-92fa-b586f01e6b4c ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-54-generic N/A linux-backports-modules-5.4.0-54-generic N/A linux-firmware1.187.4 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/10/2020 dmi.bios.vendor: LENOVO dmi.bios.version: EMCN40WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0Q55724 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: IdeaPad 3 14IIL05 dmi.modalias: dmi:bvnLENOVO:bvrEMCN40WW:bd08/10/2020:svnLENOVO:pn81WD:pvrIdeaPad314IIL05:rvnLENOVO:rnLNVNB161216:rvrSDK0Q55724WIN:cvnLENOVO:ct10:cvrIdeaPad314IIL05: dmi.product.family: IdeaPad 3 14IIL05 dmi.product.name: 81WD dmi.product.sku: LENOVO_MT_81WD_BU_idea_FM_IdeaPad 3 14IIL05 dmi.product.version: IdeaPad 3 14IIL05 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1906088/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1906088] [NEW] Touchpad is not detected and not responsive
Public bug reported: 1. See attachment 2. Vendor is Microsoft ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-54-generic 5.4.0-54.60 ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65 Uname: Linux 5.4.0-54-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: niteshb1201 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Nov 28 11:00:25 2020 InstallationDate: Installed on 2020-11-28 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 046d:c52f Logitech, Inc. Unifying Receiver Bus 001 Device 002: ID 174f:1176 Syntek Integrated Camera Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 81WD ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-54-generic root=UUID=c57708b6-f80b-474d-92fa-b586f01e6b4c ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-54-generic N/A linux-backports-modules-5.4.0-54-generic N/A linux-firmware1.187.4 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/10/2020 dmi.bios.vendor: LENOVO dmi.bios.version: EMCN40WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0Q55724 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: IdeaPad 3 14IIL05 dmi.modalias: dmi:bvnLENOVO:bvrEMCN40WW:bd08/10/2020:svnLENOVO:pn81WD:pvrIdeaPad314IIL05:rvnLENOVO:rnLNVNB161216:rvrSDK0Q55724WIN:cvnLENOVO:ct10:cvrIdeaPad314IIL05: dmi.product.family: IdeaPad 3 14IIL05 dmi.product.name: 81WD dmi.product.sku: LENOVO_MT_81WD_BU_idea_FM_IdeaPad 3 14IIL05 dmi.product.version: IdeaPad 3 14IIL05 dmi.sys.vendor: LENOVO ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ** Attachment added: "devices" https://bugs.launchpad.net/bugs/1906088/+attachment/5438939/+files/devices -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1906088 Title: Touchpad is not detected and not responsive Status in linux package in Ubuntu: New Bug description: 1. See attachment 2. Vendor is Microsoft ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-54-generic 5.4.0-54.60 ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65 Uname: Linux 5.4.0-54-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: niteshb1201 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Nov 28 11:00:25 2020 InstallationDate: Installed on 2020-11-28 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 046d:c52f Logitech, Inc. Unifying Receiver Bus 001 Device 002: ID 174f:1176 Syntek Integrated Camera Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 81WD ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-54-generic root=UUID=c57708b6-f80b-474d-92fa-b586f01e6b4c ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-54-generic N/A linux-backports-modules-5.4.0-54-generic N/A linux-firmware1.187.4 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/10/2020 dmi.bios.vendor: LENOVO dmi.bios.version: EMCN40WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0Q55724 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: IdeaPad 3 14IIL05 dmi.modalias: dmi:bvnLENOVO:bvrEMCN40WW:bd08/10/2020:svnLENOVO:pn81WD:pvrIdeaPad314IIL05:rvnLENOVO:rnLNVNB161216:rvrSDK0Q55724WIN:cvnLENOVO:ct10:cvrIdeaPad314IIL05: dmi.product.family: IdeaPad 3 14IIL05 dmi.product.name: 81WD dmi.product.sku: LENOVO_MT_81WD_BU_idea_FM_IdeaPad 3 14IIL05 dmi.product.version: IdeaPad 3 14IIL05 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1906088/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help :
[Kernel-packages] [Bug 1893538] Re: No bluetooth on Dell XPS 7390 with AX200 after upgrade to 20.04
This is being fixed in 1905214. I've tested the focal-proposed package already and it appears to work fine. -- 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/1893538 Title: No bluetooth on Dell XPS 7390 with AX200 after upgrade to 20.04 Status in linux-firmware package in Ubuntu: Confirmed Bug description: Hi, my Dell XPS 7390 worked just fine with Ubuntu 19.10, but after clean-install upgrading to 20.04 I don't have working bluetooth any more. The machine has an Intel AX200 installed. I'm not sure what details are helpful to provide, so here are some random things, happy to provide more if people can provide hints... # uname -a Linux marvin 5.4.0-42-generic #46-Ubuntu SMP Fri Jul 10 00:24:02 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux # lspci 00:00.0 Host bridge: Intel Corporation Device 9b61 (rev 0c) 00:02.0 VGA compatible controller: Intel Corporation UHD Graphics (rev 02) 00:04.0 Signal processing controller: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Thermal Subsystem (rev 0c) 00:08.0 System peripheral: Intel Corporation Xeon E3-1200 v5/v6 / E3-1500 v5 / 6th/7th/8th Gen Core Processor Gaussian Mixture Model 00:12.0 Signal processing controller: Intel Corporation Comet Lake Thermal Subsytem 00:14.0 USB controller: Intel Corporation Device 02ed 00:14.2 RAM memory: Intel Corporation Device 02ef 00:15.0 Serial bus controller [0c80]: Intel Corporation Serial IO I2C Host Controller 00:15.1 Serial bus controller [0c80]: Intel Corporation Comet Lake Serial IO I2C Host Controller 00:16.0 Communication controller: Intel Corporation Comet Lake Management Engine Interface 00:1c.0 PCI bridge: Intel Corporation Device 02bc (rev f0) 00:1c.6 PCI bridge: Intel Corporation Device 02be (rev f0) 00:1d.0 PCI bridge: Intel Corporation Device 02b0 (rev f0) 00:1d.4 PCI bridge: Intel Corporation Device 02b4 (rev f0) 00:1f.0 ISA bridge: Intel Corporation Device 0284 00:1f.3 Audio device: Intel Corporation Device 02c8 00:1f.4 SMBus: Intel Corporation Device 02a3 00:1f.5 Serial bus controller [0c80]: Intel Corporation Comet Lake SPI (flash) Controller 01:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS525A PCI Express Card Reader (rev 01) 02:00.0 Network controller: Intel Corporation Wi-Fi 6 AX200 (rev 1a) 03:00.0 PCI bridge: Intel Corporation JHL6540 Thunderbolt 3 Bridge (C step) [Alpine Ridge 4C 2016] (rev 02) 04:00.0 PCI bridge: Intel Corporation JHL6540 Thunderbolt 3 Bridge (C step) [Alpine Ridge 4C 2016] (rev 02) 04:01.0 PCI bridge: Intel Corporation JHL6540 Thunderbolt 3 Bridge (C step) [Alpine Ridge 4C 2016] (rev 02) 04:02.0 PCI bridge: Intel Corporation JHL6540 Thunderbolt 3 Bridge (C step) [Alpine Ridge 4C 2016] (rev 02) 04:04.0 PCI bridge: Intel Corporation JHL6540 Thunderbolt 3 Bridge (C step) [Alpine Ridge 4C 2016] (rev 02) 05:00.0 System peripheral: Intel Corporation JHL6540 Thunderbolt 3 NHI (C step) [Alpine Ridge 4C 2016] (rev 02) 3b:00.0 USB controller: Intel Corporation JHL6540 Thunderbolt 3 USB Controller (C step) [Alpine Ridge 4C 2016] (rev 02) 71:00.0 Non-Volatile memory controller: Micron Technology Inc Device 5410 (rev 01) # dmesg | grep iwl [8.578338] iwlwifi :02:00.0: enabling device ( -> 0002) [8.594306] iwlwifi :02:00.0: Direct firmware load for iwlwifi-cc-a0-50.ucode failed with error -2 [8.594320] iwlwifi :02:00.0: Direct firmware load for iwlwifi-cc-a0-49.ucode failed with error -2 [8.597017] iwlwifi :02:00.0: TLV_FW_FSEQ_VERSION: FSEQ Version: 43.2.23.17 [8.597019] iwlwifi :02:00.0: Found debug destination: EXTERNAL_DRAM [8.597020] iwlwifi :02:00.0: Found debug configuration: 0 [8.597192] iwlwifi :02:00.0: loaded firmware version 48.4fa0041f.0 op_mode iwlmvm [8.650489] iwlwifi :02:00.0: Detected Killer(R) Wi-Fi 6 AX1650w 160MHz Wireless Network Adapter (200D2W), REV=0x340 [8.663161] iwlwifi :02:00.0: Applying debug destination EXTERNAL_DRAM [8.663495] iwlwifi :02:00.0: Allocated 0x0040 bytes for firmware monitor. [8.829671] iwlwifi :02:00.0: base HW address: 04:ed:33:c0:85:78 [8.846912] iwlwifi :02:00.0 wlp2s0: renamed from wlan0 [9.459653] iwlwifi :02:00.0: Applying debug destination EXTERNAL_DRAM [9.626499] iwlwifi :02:00.0: FW already configured (0) - re-configuring To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1893538/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1903969] Re: failed to boot to GUI: i915 0000:00:02.0: [drm] *ERROR* Link Training Unsuccessful
Kernel in proposed solved the problem, system can now boot correctly with monitor connected on WD19 docking, with docking connected on system TBT port. Done 10 cold boot and 10 warm boot cycles, all pass. -- 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/1903969 Title: failed to boot to GUI: i915 :00:02.0: [drm] *ERROR* Link Training Unsuccessful Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux-oem-5.6 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-oem-5.10 source package in Focal: Fix Committed Status in linux-oem-5.6 source package in Focal: New Status in linux source package in Groovy: Won't Fix Status in linux-oem-5.10 source package in Groovy: Invalid Status in linux-oem-5.6 source package in Groovy: Invalid Status in linux source package in Hirsute: In Progress Status in linux-oem-5.10 source package in Hirsute: Invalid Status in linux-oem-5.6 source package in Hirsute: Invalid Bug description: [SRU Justification] [Impact] On platforms supported DP tunneling over USB 3.2 or so, a Retimer is required on the host side to cover insertion loss. On such platforms the rtimer firmware maybe configured to use LTTPR (Link Training Tunable PHY Repeater) non-transparent mode only, which is only supported in drm-tip currently. Without LTTPR support, link training may fail with following error messages depending on the data path configuration: i915 :00:02.0: [drm] *ERROR* Link Training Unsuccessful i915 :00:02.0: [drm] *ERROR* CPU pipe A FIFO underrun [Fix] Patchset https://www.spinics.net/lists/intel-gfx/msg248700.html ("drm/i915: Add support for LTTPR non-transparent link training mode") is required to fix this issue. It has been landed to drm-tip and will only be merged to mainline in v5.11. Patchset https://patchwork.freedesktop.org/series/76993/ ("Plumb crtc state to link training code") is included for link training functions prototype changes. [Test Case] On Dell OptiPlex and WD19 docking station, use following steps to verify: 1. disconnect WD19 from OptiPlex, disconnect OptiPlex's power 2. attach OptiPlex's power cord 3. attach WD19's power cord 4. attach DP to WD19 5. attach WD19 to OptiPlex 6. boot up and check if boot to GUI directly 7. `dmesg` and check if aforementioned DRM link training error appears [Where problems could occur] The second patchset pulled for dependency doesn't have too much effective changes but refactoring some translation functions, so very unlikely to have regressions. For the major part, LTTPR support, when LTTPR is either not detected or not supported, it will fall back to use transparent mode as it was. Otherwise, DP Standard recommends to use LTTPR non-transparent mode for link training, so this should be the right way to have best hardware support. == original bug description == [Summary] When the monitor ONLY is connected to the WD19 (DP port) and WD19 is connected to the type c port than boot the machine, the monitor shows no video output after loaded i915. [Reproduce Steps] 1. connect power cable of WD19 2. connect DP cable from monitor to WD19 3. connect power cable to target system. 4. connect type c cable from WD19 to target system 5. boot up [Results] Expected: video output as there is only one monitor connected. Actual: No video output. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.6.0-1033-oem 5.6.0-1033.35 ProcVersionSignature: Ubuntu 5.6.0-1033.35-oem 5.6.19 Uname: Linux 5.6.0-1033-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.11 Architecture: amd64 CasperMD5CheckResult: skip Date: Thu Nov 12 05:11:11 2020 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-metapod+X40 InstallationDate: Installed on 2020-11-03 (9 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 SourcePackage: linux-signed-oem-5.6 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1903969/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1906067] Re: Boot from ISO - exFAT support missing
** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1906067 Title: Boot from ISO - exFAT support missing Status in linux package in Ubuntu: Confirmed Bug description: Please add support for booting the ISO image via grub2 (loopback) in initrd. For larger images and a USB sticks, FAT32 is no longer sufficient. Most popular distributions already have support for exFAT in initrd (they can find and mount ISO on this filesystem). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1906067/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1905214] Re: linux-firmware: intel AX200 (8087:0029) and AX201(8087:0026) bluetooth firmware update
Verified on Groovy, same steps and same hardware environment as #4, it worked well. -- 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/1905214 Title: linux-firmware: intel AX200 (8087:0029) and AX201(8087:0026) bluetooth firmware update 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 Groovy: Fix Committed Status in linux-firmware source package in Hirsute: Fix Released Bug description: For H, it already has all patches, this SRU is not needed for H For G, only needs the 0005-xxx.patch and 0010-xxx.patch For F, needs all patches. [Impact] We found 2 issues: Bluetooth headset can't work in hsp/hfp mode, Both AX200 and AX201 have this issue (#1871794) Bluetooth will stop working randomly on the machines with AX200 (OEM bug). [Fix] Update the firmware to the latest version, the above 2 issues could be fixed. [Test] connect a bluetooth headset, after connecting, it is in A2DP mode by default, change it to hsp/hfp mode from gnome-sound-setting, play sound and record sound from headset, all work well. Keep the machine powered on and let it be idle for 1 day, check the bluetooth headset, still could work. [Regression Potential] I could make the Bluetooth function stop working on the machines with AX200 or AX201 module, like can't scan the BT devices, can't connect the BT devices or the BT devices can't work normally. But this possibility is very low, we have tested the SRU on a couple of lenovo machines, all worked well. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1905214/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1905214] Re: linux-firmware: intel AX200 (8087:0029) and AX201(8087:0026) bluetooth firmware update
Reply #10 and #11: I found only power-off/power-on is not enough to make the kernel reload the BT firmware on some desktop machines or AIO machines, need to power off, wait for a couple of minutes, power on. For laptop machines, looks like power-off/power-on could make the kernel reload the BT firmware. -- 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/1905214 Title: linux-firmware: intel AX200 (8087:0029) and AX201(8087:0026) bluetooth firmware update 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 Groovy: Fix Committed Status in linux-firmware source package in Hirsute: Fix Released Bug description: For H, it already has all patches, this SRU is not needed for H For G, only needs the 0005-xxx.patch and 0010-xxx.patch For F, needs all patches. [Impact] We found 2 issues: Bluetooth headset can't work in hsp/hfp mode, Both AX200 and AX201 have this issue (#1871794) Bluetooth will stop working randomly on the machines with AX200 (OEM bug). [Fix] Update the firmware to the latest version, the above 2 issues could be fixed. [Test] connect a bluetooth headset, after connecting, it is in A2DP mode by default, change it to hsp/hfp mode from gnome-sound-setting, play sound and record sound from headset, all work well. Keep the machine powered on and let it be idle for 1 day, check the bluetooth headset, still could work. [Regression Potential] I could make the Bluetooth function stop working on the machines with AX200 or AX201 module, like can't scan the BT devices, can't connect the BT devices or the BT devices can't work normally. But this possibility is very low, we have tested the SRU on a couple of lenovo machines, all worked well. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1905214/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1906067] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1906067 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1906067 Title: Boot from ISO - exFAT support missing Status in linux package in Ubuntu: Incomplete Bug description: Please add support for booting the ISO image via grub2 (loopback) in initrd. For larger images and a USB sticks, FAT32 is no longer sufficient. Most popular distributions already have support for exFAT in initrd (they can find and mount ISO on this filesystem). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1906067/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1906067] Re: Boot from ISO - exFAT support missing
Exfat support is not a question of ubuntu-cdimage, but of the kernel. ** Project changed: ubuntu-cdimage => 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/1906067 Title: Boot from ISO - exFAT support missing Status in linux package in Ubuntu: New Bug description: Please add support for booting the ISO image via grub2 (loopback) in initrd. For larger images and a USB sticks, FAT32 is no longer sufficient. Most popular distributions already have support for exFAT in initrd (they can find and mount ISO on this filesystem). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1906067/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1906067] [NEW] Boot from ISO - exFAT support missing
You have been subscribed to a public bug: Please add support for booting the ISO image via grub2 (loopback) in initrd. For larger images and a USB sticks, FAT32 is no longer sufficient. Most popular distributions already have support for exFAT in initrd (they can find and mount ISO on this filesystem). ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- Boot from ISO - exFAT support missing https://bugs.launchpad.net/bugs/1906067 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 1900362] Re: Kernel turns off USB-devices
I started noticing this today after a reboot (kernel 5.8.0-25 hirsute/dev repos). Both my keyboard and mouse have begun autosuspending after only a few seconds on non-use. Echoing 'on' to the appropriate /sys/bus/usb/devices/usb#/#-#/power/control path gets them working again. This is a desktop with no laptop tools / power management packages installed. Looks like udev is being too optimistic about what it should shut down. Bus 007 Device 002: ID 0416:a0f8 Winbond Electronics Corp. WHIFTEC Mechanical Gaming Keyboard 汇富特游戏机械键盘 Bus 001 Device 011: ID 1b1c:1b31 Corsair Corsair Vengeance M90 Mouse -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1900362 Title: Kernel turns off USB-devices Status in linux package in Ubuntu: Confirmed Bug description: Kernel turns off USB-devices. A mouse connected to an usb-port works until some time. Then this device is turned off and never turned on again. I tried to turn off power saving for such devices, but without success. This started with kernels 5.4.0-49-generic and later. I do not see this with kernel 5.4.0-48-generic. This bug renders all usb-ports used unusable. You can unplug the device (a mouse or keyboard) to an unused usb-port. But this will be switched off then soon too. At some point in future you are out of working ports, because all of them are switched off and never on again. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-52-generic 5.4.0-52.57 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tps6019 F pulseaudio CasperMD5CheckResult: skip Date: Mon Oct 19 00:49:09 2020 HibernationDevice: RESUME=/dev/vg/swap_1 InstallationDate: Installed on 2011-10-19 (3287 days ago) InstallationMedia: Xubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) MachineType: Acer TravelMate P643-M ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-52-generic root=/dev/mapper/vg-root ro elevator=deadline splash acpi=force reboot=bios ipv6.disable=1 crashkernel=384M-2G:128M,2G-:256M 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.4.0-52-generic N/A linux-backports-modules-5.4.0-52-generic N/A linux-firmware1.187.3 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2019-04-27 (540 days ago) dmi.bios.date: 10/21/2013 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: V2.15 dmi.board.asset.tag: No Asset Tag dmi.board.name: TravelMate P643-M dmi.board.vendor: Acer dmi.board.version: V2.15 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Acer dmi.chassis.version: V2.15 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvrV2.15:bd10/21/2013:svnAcer:pnTravelMateP643-M:pvrV2.15:rvnAcer:rnTravelMateP643-M:rvrV2.15:cvnAcer:ct9:cvrV2.15: dmi.product.family: TravelMate P643-M dmi.product.name: TravelMate P643-M dmi.product.sku: TravelMate P643-M_0681_2.15 dmi.product.version: V2.15 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1900362/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1904904] Re: Xenial update: v4.4.243 upstream stable release
** Changed in: linux (Ubuntu Xenial) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1904904 Title: Xenial update: v4.4.243 upstream stable release Status in linux package in Ubuntu: Confirmed Status in linux source package in Xenial: Fix Committed 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: v4.4.243 upstream stable release from git://git.kernel.org/ Note: This patch set is empty for xenial because v4.4.243 contained only one patch: ed3691aa7e4a powercap: restrict energy meter to root access The contents of which are already present here via: 7a1c0417c5111 powercap: make attributes only readable by root ^^^ (note also that this should have been "UBUNTU: SAUCE:") Linux 4.4.243 UBUNTU: upstream stable to v4.4.243 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1904904/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1903750] Re: Xenial update: v4.4.242 upstream stable release
** Changed in: linux (Ubuntu Xenial) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1903750 Title: Xenial update: v4.4.242 upstream stable release Status in linux package in Ubuntu: Confirmed Status in linux source package in Xenial: Fix Committed 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: v4.4.242 upstream stable release from git://git.kernel.org/ SUNRPC: ECONNREFUSED should cause a rebind. scripts/setlocalversion: make git describe output more reliable ravb: Fix bit fields checking in ravb_hwtstamp_get() tipc: fix memory leak caused by tipc_buf_append() mtd: lpddr: Fix bad logic in print_drs_error ata: sata_rcar: Fix DMA boundary mask fscrypt: return -EXDEV for incompatible rename or link into encrypted dir f2fs crypto: avoid unneeded memory allocation in ->readdir powerpc/powernv/smp: Fix spurious DBG() warning sparc64: remove mm_cpumask clearing to fix kthread_use_mm race f2fs: fix to check segment boundary during SIT page readahead um: change sigio_spinlock to a mutex xfs: fix realtime bitmap/summary file truncation when growing rt volume video: fbdev: pvr2fb: initialize variables ath10k: fix VHT NSS calculation when STBC is enabled mmc: via-sdmmc: Fix data race bug printk: reduce LOG_BUF_SHIFT range for H8300 kgdb: Make "kgdbcon" work properly with "kgdb_earlycon" USB: adutux: fix debugging drivers/net/wan/hdlc_fr: Correctly handle special skb->protocol values power: supply: test_power: add missing newlines when printing parameters by sysfs md/bitmap: md_bitmap_get_counter returns wrong blocks clk: ti: clockdomain: fix static checker warning net: 9p: initialize sun_server.sun_path to have addr's value only when addr is valid drivers: watchdog: rdc321x_wdt: Fix race condition bugs ext4: Detect already used quota file early gfs2: add validation checks for size of superblock memory: emif: Remove bogus debugfs error handling ARM: dts: s5pv210: move PMU node out of clock controller ARM: dts: s5pv210: remove dedicated 'audio-subsystem' node md/raid5: fix oops during stripe resizing leds: bcm6328, bcm6358: use devres LED registering function NFS: fix nfs_path in case of a rename retry ACPI / extlog: Check for RDMSR failure ACPI: video: use ACPI backlight for HP 635 Notebook acpi-cpufreq: Honor _PSD table setting on new AMD CPUs w1: mxc_w1: Fix timeout resolution problem leading to bus error scsi: mptfusion: Fix null pointer dereferences in mptscsih_remove() btrfs: reschedule if necessary when logging directory items vt: keyboard, simplify vt_kdgkbsent vt: keyboard, extend func_buf_lock to readers dmaengine: dma-jz4780: Fix race in jz4780_dma_tx_status iio:gyro:itg3200: Fix timestamp alignment and prevent data leak. powerpc/powernv/elog: Fix race while processing OPAL error log event. ubifs: dent: Fix some potential memory leaks while iterating entries ubi: check kthread_should_stop() after the setting of task state ia64: fix build error with !COREDUMP ceph: promote to unsigned long long before shifting libceph: clear con->out_msg on Policy::stateful_server faults 9P: Cast to loff_t before multiplying ring-buffer: Return 0 on success from ring_buffer_resize() vringh: fix __vringh_iov() when riov and wiov are different tty: make FONTX ioctl use the tty pointer they were actually passed arm64: berlin: Select DW_APB_TIMER_OF cachefiles: Handle readpage error correctly hil/parisc: Disable HIL driver when it gets stuck ARM: samsung: fix PM debug build with DEBUG_LL but !MMU ARM: s3c24xx: fix missing system reset device property: Keep secondary firmware node secondary by type device property: Don't clear secondary pointer for shared primary firmware node staging: comedi: cb_pcidas: Allow 2-channel commands for AO subdevice Revert "Revert "XEN uses irqdesc::irq_data_common::handler_data to store a per interrupt XEN data pointer which contains XEN specific information."" xen/events: don't use chip_data for legacy IRQs tipc: fix use-after-free in tipc_bcast_get_mode gianfar: Replace skb_realloc_headroom with skb_cow_head for PTP gianfar: Account for Tx PTP timestamp in the skb headroom Fonts: Replace discarded const qualifier ALSA: usb-audio: Add implicit feedback quirk for Qu-16 ftrace: Fix recursion check for NMI test ftrace: Handle tracing when switching between
[Kernel-packages] [Bug 1904914] Re: Xenial update: v4.4.244 upstream stable release
** Changed in: linux (Ubuntu Xenial) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1904914 Title: Xenial update: v4.4.244 upstream stable release Status in linux package in Ubuntu: Confirmed Status in linux source package in Xenial: Fix Committed 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: v4.4.244 upstream stable release from git://git.kernel.org/ ring-buffer: Fix recursion protection transitions between interrupt context gfs2: Wake up when sd_glock_disposal becomes zero mm: mempolicy: fix potential pte_unmap_unlock pte error time: Prevent undefined behaviour in timespec64_to_ns() btrfs: reschedule when cloning lots of extents net: xfrm: fix a race condition during allocing spi perf tools: Add missing swap for ino_generation ALSA: hda: prevent undefined shift in snd_hdac_ext_bus_get_link() can: dev: can_get_echo_skb(): prevent call to kfree_skb() in hard IRQ context can: dev: __can_get_echo_skb(): fix real payload length return value for RTR frames can: can_create_echo_skb(): fix echo skb generation: always use skb_clone() can: peak_usb: add range checking in decode operations can: peak_usb: peak_usb_get_ts_time(): fix timestamp wrapping Btrfs: fix missing error return if writeback for extent buffer never started i40e: Wrong truncation from u16 to u8 i40e: Fix of memory leak and integer truncation in i40e_virtchnl.c ath9k_htc: Use appropriate rs_datalen type usb: gadget: goku_udc: fix potential crashes in probe gfs2: Free rd_bits later in gfs2_clear_rgrpd to fix use-after-free gfs2: check for live vs. read-only file system in gfs2_fitrim drm/amdgpu: perform srbm soft reset always on SDMA resume mac80211: fix use of skb payload instead of header cfg80211: regulatory: Fix inconsistent format argument iommu/amd: Increase interrupt remapping table limit to 512 entries xfs: fix a missing unlock on error in xfs_fs_map_blocks of/address: Fix of_node memory leak in of_dma_is_coherent cosa: Add missing kfree in error path of cosa_write perf: Fix get_recursion_context() ext4: correctly report "not supported" for {usr,grp}jquota when !CONFIG_QUOTA ext4: unlock xattr_sem properly in ext4_inline_data_truncate() usb: cdc-acm: Add DISABLE_ECHO for Renesas USB Download mode mei: protect mei_cl_mtu from null dereference ocfs2: initialize ip_next_orphan don't dump the threads that had been already exiting when zapped. drm/gma500: Fix out-of-bounds access to struct drm_device.vblank[] pinctrl: amd: use higher precision for 512 RtcClk pinctrl: amd: fix incorrect way to disable debounce filter swiotlb: fix "x86: Don't panic if can not alloc buffer for swiotlb" IPv6: Set SIT tunnel hard_header_len to zero net/af_iucv: fix null pointer dereference on shutdown net/x25: Fix null-ptr-deref in x25_connect net: Update window_clamp if SOCK_RCVBUF is set random32: make prandom_u32() output unpredictable x86/speculation: Allow IBPB to be conditionally enabled on CPUs with always-on STIBP xen/events: avoid removing an event channel while handling it xen/events: add a proper barrier to 2-level uevent unmasking xen/events: fix race in evtchn_fifo_unmask() xen/events: add a new "late EOI" evtchn framework xen/blkback: use lateeoi irq binding xen/netback: use lateeoi irq binding xen/scsiback: use lateeoi irq binding xen/pciback: use lateeoi irq binding xen/events: switch user event channels to lateeoi model xen/events: use a common cpu hotplug hook for event channels xen/events: defer eoi in case of excessive number of events xen/events: block rogue events for some time Revert "kernel/reboot.c: convert simple_strtoul to kstrtoint" reboot: fix overflow parsing reboot cpu number ext4: fix leaking sysfs kobject after failed mount Convert trailing spaces and periods in path components Linux 4.4.244 UBUNTU: upstream stable to v4.4.244 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1904914/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1898786] Re: bcache: Issues with large IO wait in bch_mca_scan() when shrinker is enabled
Hi Benjamin, No worries about being busy. Now, the kernel is scheduled to be released early next week, around the 30th of November. I think at this stage it is best to wait it out and install the kernel once it reaches -updates. That way you will have a fixed kernel that is supported by livepatch, and you don't have to justify a reboot twice. I did some regression testing in my comments above, and everything looks okay. These patches also worked great in your test kernel. We have done the best can to verify the kernel in the time given, so don't worry about testing at this stage. I'll let you know once the kernel has reached -updates, likely Monday or Tuesday next week. 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/1898786 Title: bcache: Issues with large IO wait in bch_mca_scan() when shrinker is enabled Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Committed Status in linux source package in Focal: Fix Committed Bug description: BugLink: https://bugs.launchpad.net/bugs/1898786 [Impact] Systems that utilise bcache can experience extremely high IO wait times when under constant IO pressure. The IO wait times seem to stay at a consistent 1 second, and never drop as long as the bcache shrinker is enabled. If you disable the shrinker, then IO wait drops significantly to normal levels. We did some perf analysis, and it seems we spend a huge amount of time in bch_mca_scan(), likely waiting for the mutex ">bucket_lock". Looking at the recent commits in Bionic, we found the following commit merged in upstream 5.1-rc1 and backported to 4.15.0-87-generic through upstream stable: commit 9fcc34b1a6dd4b8e5337e2b6ef45e428897eca6b Author: Coly Li Date: Wed Nov 13 16:03:24 2019 +0800 Subject: bcache: at least try to shrink 1 node in bch_mca_scan() Link: https://github.com/torvalds/linux/commit/9fcc34b1a6dd4b8e5337e2b6ef45e428897eca6b It mentions in the description that: > If sc->nr_to_scan is smaller than c->btree_pages, after the above > calculation, variable 'nr' will be 0 and nothing will be shrunk. It is > frequeently observed that only 1 or 2 is set to sc->nr_to_scan and make > nr to be zero. Then bch_mca_scan() will do nothing more then acquiring > and releasing mutex c->bucket_lock. This seems to be what is going on here, but the above commit only addresses when nr is 0. From what I can see, the problems we are experiencing are when nr is 1 or 2, and again, we just waste time in bch_mca_scan() waiting on c->bucket_lock, only to release c->bucket_lock since the shrinker loop never executes since there is no work to do. [Fix] The following commits fix the problem, and all landed in 5.6-rc1: commit 125d98edd11464c8e0ec9eaaba7d682d0f832686 Author: Coly Li Date: Fri Jan 24 01:01:40 2020 +0800 Subject: bcache: remove member accessed from struct btree Link: https://github.com/torvalds/linux/commit/125d98edd11464c8e0ec9eaaba7d682d0f832686 commit d5c9c470b01177e4d90cdbf178b8c7f37f5b8795 Author: Coly Li Date: Fri Jan 24 01:01:41 2020 +0800 Subject: bcache: reap c->btree_cache_freeable from the tail in bch_mca_scan() Link: https://github.com/torvalds/linux/commit/d5c9c470b01177e4d90cdbf178b8c7f37f5b8795 commit e3de04469a49ee09c89e80bf821508df458ccee6 Author: Coly Li Date: Fri Jan 24 01:01:42 2020 +0800 Subject: bcache: reap from tail of c->btree_cache in bch_mca_scan() Link: https://github.com/torvalds/linux/commit/e3de04469a49ee09c89e80bf821508df458ccee6 The first commit is a dependency of the other two. The first commit removes a "recently accessed" marker, used to indicate if a particular cache has been used recently, and if it has been, not consider it for cache eviction. The commit mentions that under heavy IO, all caches will end up being recently accessed, and nothing will ever be shrunk. The second commit changes a previous design decision of skipping the first 3 caches to shrink, since it is a common case to call bch_mca_scan() with nr being 1, or 2, just like 0 was common in the very first commit I mentioned. This time, if we land on 1 or 2, the loop exits and nothing happens, and we waste time waiting on locks, just like the very first commit I mentioned. The fix is to try shrink caches from the tail of the list, and not the beginning. The third commit fixes a minor issue where we don't want to re-arrange the linked list c->btree_cache, which is what the second commit ended up doing, and instead, just shrink the cache at the end of the linked list, and not change the order. One minor backport / context adjustment was required in the first commit for Bionic, and the rest are all clean cherry picks to Bionic and Focal. [Testcase] This is kind of hard to test,
[Kernel-packages] [Bug 1853277] Re: Lenovo ThinkBook 14-IML Touchpad not showing up in /proc/bus/input/devices
Verification for Focal is needed on this bug. Would someone who has tested the fix with focal please complete that? Thank you! This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- focal' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! -- 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/1853277 Title: Lenovo ThinkBook 14-IML Touchpad not showing up in /proc/bus/input/devices Status in linux package in Ubuntu: Triaged 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: Fix Released Status in linux source package in Groovy: Triaged Status in linux-oem-5.6 source package in Groovy: Invalid Bug description: == SRU Justification == [Impact] Touchpad on sereval Lenovo ThinkBook doesn't work. [Fix] Maintain method calling ordering by calling _REG before issuing _STA, as ACPI spec suggested, for I2C ACPI devices. [Test] Positive feedback from several users. [Regression Potential] If there are some systems that rely on the wrong calling ordering then there's a regression risk. However it's rather unlikely. == Original Bug Report == This is happening on a ThinkBook 14 IML 20RV. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-18-generic 5.3.0-18.19+1 ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1 Uname: Linux 5.3.0-18-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1848 F pulseaudio CasperVersion: 1.427 CurrentDesktop: ubuntu:GNOME Date: Wed Nov 20 11:10:52 2019 LiveMediaBuild: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: LENOVO 20RV ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/username.seed quiet splash --- RelatedPackageVersions: linux-restricted-modules-5.3.0-18-generic N/A linux-backports-modules-5.3.0-18-generic N/A linux-firmware1.183 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/10/2019 dmi.bios.vendor: LENOVO dmi.bios.version: CJCN21WW dmi.board.name: LVA/LVAB dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.modalias: dmi:bvnLENOVO:bvrCJCN21WW:bd10/10/2019:svnLENOVO:pn20RV:pvrLenovoThinkBook14-IML:rvnLENOVO:rnLVA/LVAB:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvr: dmi.product.family: ThinkBook 14-IML dmi.product.name: 20RV dmi.product.sku: LENOVO_MT_20RV_BU_idea_FM_ThinkBook 14-IML dmi.product.version: Lenovo ThinkBook 14-IML dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1853277/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1897963] Re: Cherry Pick needed for Critical upstream patch for Kernel null pointer dereference - usb-c altmode
Hi @Igor, may you please complete the verification? Thank you! This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-focal' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1897963 Title: Cherry Pick needed for Critical upstream patch for Kernel null pointer dereference - usb-c altmode Status in linux package in Ubuntu: Confirmed Status in linux source package in Focal: Fix Committed Bug description: Basically a null pointer dereference was happening while using a lenovo usb-c dock. The issue has been addressed upstream with commit: https://github.com/torvalds/linux/commit/386e15a650447f53de3d2d8819ce9393f31650a4 Apparently the dock kept sending altmode information repeatedly, and the kernel did not expect this to happen, a check was added to make sure it only observes the amount of altmodes limited by the standard. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-5.4.0-48-generic 5.4.0-48.52~18.04.1 ProcVersionSignature: Ubuntu 5.4.0-48.52~18.04.1-generic 5.4.60 Uname: Linux 5.4.0-48-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.17 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Sep 30 15:40:24 2020 InstallationDate: Installed on 2020-09-30 (0 days ago) InstallationMedia: Ubuntu 18.04.5 LTS "Bionic Beaver" - Release amd64 (20200806.1) SourcePackage: linux-signed-hwe-5.4 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1897963/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1896642] Re: Request for CIFS patches to be available in 5.4 kernel
Hi @Marcelo - may you please complete the verification? 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/1896642 Title: Request for CIFS patches to be available in 5.4 kernel Status in linux package in Ubuntu: In Progress Status in linux-azure package in Ubuntu: In Progress Status in linux source package in Focal: Fix Committed Status in linux-azure source package in Focal: Invalid Bug description: [Impact] Microsoft's CIFS product team requested to ensure below patches are available in 5.4 kernel https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/fs/cifs?id=df58fae72428be113f041fe55c9605a9088bfb14 https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/fs/cifs?id=0e6705182d4e1b77248a93470d6d7b3013d59b30 https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/fs/cifs?id=cf5371ae460eb8e484e4884747af270c86c3c469 https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/fs/cifs?id=43f8a6a74ee2442b9410ed297f5d4c77e7cb5ace I notice couple commits are already picked up in 5.4 kernel. Just sharing the CIFS patch commit requests came in. [Test Case] Since those are small improvements a basic smoke test can be used to avoid regressions: 1. Install cifs-utils and dbench: $ sudo apt-get install cifs-utils dbench 2. Mount a CIFS share using: $ sudo mount -t cifs -o username=REMOTEUSER \\remoteip\path\to\shared\folder /mnt 3. Run dbench and check for regressions: $ cd /mnt; dbench 20 -t 120 -D . [Regression potential] The regression potential is restricted to the ability of mounting and accessing CIFS volumes. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1896642/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1900855] Re: linux-aws: fold test_bpf SAUCE to linux/master
Hi @Paolo - may you please complete the verification on this? Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1900855 Title: linux-aws: fold test_bpf SAUCE to linux/master Status in linux package in Ubuntu: Triaged Status in linux source package in Groovy: Fix Committed Bug description: [Impact] Groovy/linux-aws is carrying this patch: 0deca25e3bb1 UBUNTU: SAUCE: selftests: net: don't fail test_bpf when module is not present since the fix is not aws specific, (and other kernels might benefit from it), fold it in generic and make it disappear from aws after next rebase. [Fix] Cherry-pick the above SAUCE patch [Regression potential] It's a seltest fix. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1900855/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1905333] Re: Bionic update: upstream stable patchset 2020-11-23
** Changed in: linux (Ubuntu Bionic) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1905333 Title: Bionic update: upstream stable patchset 2020-11-23 Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: Fix Committed Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: upstream stable patchset 2020-11-23 Ported from the following upstream stable releases: v4.14.205, v4.19.156 from git://git.kernel.org/ drm/i915: Break up error capture compression loops with cond_resched() tipc: fix use-after-free in tipc_bcast_get_mode gianfar: Replace skb_realloc_headroom with skb_cow_head for PTP gianfar: Account for Tx PTP timestamp in the skb headroom net: usb: qmi_wwan: add Telit LE910Cx 0x1230 composition sctp: Fix COMM_LOST/CANT_STR_ASSOC err reporting on big-endian platforms sfp: Fix error handing in sfp_probe() Blktrace: bail out early if block debugfs is not configured blktrace: fix debugfs use after free i40e: Fix of memory leak and integer truncation in i40e_virtchnl.c Fonts: Replace discarded const qualifier ALSA: usb-audio: Add implicit feedback quirk for Qu-16 lib/crc32test: remove extra local_irq_disable/enable kthread_worker: prevent queuing delayed work from timer_fn when it is being canceled mm: always have io_remap_pfn_range() set pgprot_decrypted() gfs2: Wake up when sd_glock_disposal becomes zero ftrace: Fix recursion check for NMI test ftrace: Handle tracing when switching between context tracing: Fix out of bounds write in get_trace_buf futex: Handle transient "ownerless" rtmutex state correctly ARM: dts: sun4i-a10: fix cpu_alert temperature x86/kexec: Use up-to-dated screen_info copy to fill boot params of: Fix reserved-memory overlap detection blk-cgroup: Fix memleak on error path blk-cgroup: Pre-allocate tree node on blkg_conf_prep scsi: core: Don't start concurrent async scan on same host vsock: use ns_capable_noaudit() on socket create drm/vc4: drv: Add error handding for bind ACPI: NFIT: Fix comparison to '-ENXIO' vt: Disable KD_FONT_OP_COPY fork: fix copy_process(CLONE_PARENT) race with the exiting ->real_parent serial: 8250_mtk: Fix uart_get_baud_rate warning serial: txx9: add missing platform_driver_unregister() on error in serial_txx9_init USB: serial: cyberjack: fix write-URB completion race USB: serial: option: add Quectel EC200T module support USB: serial: option: add LE910Cx compositions 0x1203, 0x1230, 0x1231 USB: serial: option: add Telit FN980 composition 0x1055 USB: Add NO_LPM quirk for Kingston flash drive usb: mtu3: fix panic in mtu3_gadget_stop() ARC: stack unwinding: avoid indefinite looping Revert "ARC: entry: fix potential EFA clobber when TIF_SYSCALL_TRACE" PM: runtime: Resume the device earlier in __device_release_driver() btrfs: extent_io: add proper error handling to lock_extent_buffer_for_io() Btrfs: fix unwritten extent buffers and hangs on future writeback attempts btrfs: tree-checker: fix the error message for transid error mm: mempolicy: fix potential pte_unmap_unlock pte error tools: perf: Fix build error in v4.19.y net: dsa: read mac address from DT for slave device arm64: dts: marvell: espressobin: Add ethernet switch aliases UBUNTU: upstream stable to v4.14.205, v4.19.156 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1905333/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1904791] Re: Bionic update: upstream stable patchset 2020-11-18
** Changed in: linux (Ubuntu Bionic) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1904791 Title: Bionic update: upstream stable patchset 2020-11-18 Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: Fix Committed Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: upstream stable patchset 2020-11-18 Ported from the following upstream stable releases: v4.14.204, v4.19.155 from git://git.kernel.org/ scripts/setlocalversion: make git describe output more reliable arm64: link with -z norelro regardless of CONFIG_RELOCATABLE gtp: fix an use-before-init in gtp_newlink() ravb: Fix bit fields checking in ravb_hwtstamp_get() tipc: fix memory leak caused by tipc_buf_append() arch/x86/amd/ibs: Fix re-arming IBS Fetch x86/xen: disable Firmware First mode for correctable memory errors fuse: fix page dereference after free p54: avoid accessing the data mapped to streaming DMA mtd: lpddr: Fix bad logic in print_drs_error ata: sata_rcar: Fix DMA boundary mask fscrypt: return -EXDEV for incompatible rename or link into encrypted dir x86/unwind/orc: Fix inactive tasks with stack pointer in %sp on GCC 10 compiled kernels mlxsw: core: Fix use-after-free in mlxsw_emad_trans_finish() futex: Fix incorrect should_fail_futex() handling powerpc/powernv/smp: Fix spurious DBG() warning powerpc: select ARCH_WANT_IRQS_OFF_ACTIVATE_MM sparc64: remove mm_cpumask clearing to fix kthread_use_mm race f2fs: add trace exit in exception path f2fs: fix to check segment boundary during SIT page readahead um: change sigio_spinlock to a mutex ARM: 8997/2: hw_breakpoint: Handle inexact watchpoint addresses xfs: fix realtime bitmap/summary file truncation when growing rt volume video: fbdev: pvr2fb: initialize variables ath10k: start recovery process when payload length exceeds max htc length for sdio ath10k: fix VHT NSS calculation when STBC is enabled drm/brige/megachips: Add checking if ge_b850v3_lvds_init() is working correctly media: videodev2.h: RGB BT2020 and HSV are always full range media: platform: Improve queue set up flow for bug fixing usb: typec: tcpm: During PR_SWAP, source caps should be sent only after tSwapSourceStart media: tw5864: check status of tw5864_frameinterval_get mmc: via-sdmmc: Fix data race bug drm/bridge/synopsys: dsi: add support for non-continuous HS clock printk: reduce LOG_BUF_SHIFT range for H8300 kgdb: Make "kgdbcon" work properly with "kgdb_earlycon" cpufreq: sti-cpufreq: add stih418 support USB: adutux: fix debugging uio: free uio id after uio file node is freed arm64/mm: return cpu_all_mask when node is NUMA_NO_NODE ACPI: Add out of bounds and numa_off protections to pxm_to_node() drivers/net/wan/hdlc_fr: Correctly handle special skb->protocol values bus/fsl_mc: Do not rely on caller to provide non NULL mc_io power: supply: test_power: add missing newlines when printing parameters by sysfs md/bitmap: md_bitmap_get_counter returns wrong blocks bnxt_en: Log unknown link speed appropriately. clk: ti: clockdomain: fix static checker warning net: 9p: initialize sun_server.sun_path to have addr's value only when addr is valid drivers: watchdog: rdc321x_wdt: Fix race condition bugs ext4: Detect already used quota file early gfs2: add validation checks for size of superblock arm64: dts: renesas: ulcb: add full-pwr-cycle-in-suspend into eMMC nodes memory: emif: Remove bogus debugfs error handling ARM: dts: s5pv210: remove DMA controller bus node name to fix dtschema warnings ARM: dts: s5pv210: move PMU node out of clock controller ARM: dts: s5pv210: remove dedicated 'audio-subsystem' node nbd: make the config put is called before the notifying the waiter sgl_alloc_order: fix memory leak nvme-rdma: fix crash when connect rejected md/raid5: fix oops during stripe resizing perf/x86/amd/ibs: Don't include randomized bits in get_ibs_op_count() perf/x86/amd/ibs: Fix raw sample data accumulation leds: bcm6328, bcm6358: use devres LED registering function fs: Don't invalidate page buffers in block_write_full_page() NFS: fix nfs_path in case of a rename retry ACPI / extlog: Check for RDMSR failure ACPI: video: use ACPI backlight for HP 635 Notebook ACPI: debug: don't allow debugging when ACPI is disabled
[Kernel-packages] [Bug 1904613] Re: Bionic update: upstream stable patchset 2020-11-17
** Changed in: linux (Ubuntu Bionic) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1904613 Title: Bionic update: upstream stable patchset 2020-11-17 Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: Fix Committed Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: upstream stable patchset 2020-11-17 Ported from the following upstream stable releases: v4.19.154 from git://git.kernel.org/ RDMA/cma: Remove dead code for kernel rdmacm multicast RDMA/hns: Fix missing sq_sig_type when querying QP rpmsg: smd: Fix a kobj leak in in qcom_smd_parse_edge() pwm: img: Fix null pointer access in probe watchdog: Fix memleak in watchdog_cdev_register watchdog: Use put_device on error SUNRPC: fix copying of multiple pages in gss_read_proxy_verf() netfilter: conntrack: connection timeout after re-register netfilter: nf_fwd_netdev: clear timestamp in forwarding path ARM: dts: imx6sl: fix rng node ARM: dts: sun8i: r40: bananapi-m2-ultra: Fix dcdc1 regulator memory: omap-gpmc: Fix build error without CONFIG_OF arm64: dts: qcom: pm8916: Remove invalid reg size from wcd_codec ip_gre: set dev->hard_header_len and dev->needed_headroom properly usb: dwc3: simple: add support for Hikey 970 UBUNTU: upstream stable to v4.19.154 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1904613/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1904884] Re: s390: dbginfo.sh triggers kernel panic, reading from /sys/kernel/mm/page_idle/bitmap
** Changed in: linux (Ubuntu Bionic) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1904884 Title: s390: dbginfo.sh triggers kernel panic, reading from /sys/kernel/mm/page_idle/bitmap Status in Ubuntu on IBM z Systems: In Progress Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Committed Status in linux source package in Focal: Fix Committed Status in linux source package in Groovy: Fix Released Status in linux source package in Hirsute: Fix Released Bug description: SRU Justification: == [Impact] * While executing dbginfo.sh (a script to collect runtime, configuration, and trace information on s390x) the systems hangs. * This is because 'idle page tracking' users can pass random pfn, that might be mapped to an offline page - and attempts to access offline pages lead to the hang. * It needs to be avoided that such pages are accessed. * The upstream commit modifies 'page_idle_get_page()' to use 'pfn_to_online_page()' instead of a 'pfn_valid()' and 'pfn_to_page()' combination, so that the pfn mapped to an offline page is skipped. [Fix] * 92fb1db26eef "mm/page_idle.c: skip offline pages" [Test Case] * IBM Z or LinuxONE hardware with Ubuntu Server 18.04 (GA kernel, 4.15) installed. * Execute a test application that tries to access offline pages. * Or execute dbginfo.sh with having some offline (idle) pages in the system. [Regression Potential] * There is a certain regression risk, especially for bionic, since the structure in the kernel 4.15 is a bit different compared to kernel 5.4 (and newer). * However, for newer kernels the modification is pretty save, since it's upstream accepted since kernel 5.8 and with that already inluded in hirsute and groovy. * And the patch is fine (and cherry picks cleanly) for focal as well. * For bionic there is a slightly conflicting context, since the struct 'zone' was replaced by 'pg_data_t *pgdat' (by another commit: 92fb1db26eef), but that change (or any change to the struct zone) would not be necessary to fix the uninitialized struct page access. * Hence the upstream commit/patch needs to be adjusted/backported to bionic 4.15, largely by replacing line 'pg_data_t *pgdat;' with 'struct zone *zone;' (or actually leaving this line). * But this needs to be carefully considered, since the handling of idle pages could be harmful, in the end it could make things even worse, means break even more. [Other] * The patch got upstream accepted with kernel v5.8, hence it's already is in groovy and hirsute. * The upstream commit cherry picks cleanly to focal, but for bionic a backport is needed. * Hence this kernel SRU request is for focal (cherry-pick) and bionic (backport). __ System hangs on dbginfo.sh script execution. Solution: Commit 92fb1db26eef ("mm/page_idle.c: skip offline pages") Included upstream since kernel v5.8, so it is already included in Ubuntu 20.10, but not in 20.04 and earlier. Commit 92fb1db26eef ("mm/page_idle.c: skip offline pages") applies cleanly on ubuntu-focal, but not on ubuntu-bionic. Adjustment / backport for bionic should be trivial, but it is not IBM code and therefore the backport will be requested here by Canonical. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1904884/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1906072] [NEW] Out-of-tree modules no longer build since 596b0474d3d9 in 5.10-rc1
Public bug reported: Hi, See these for reference: - https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=975571 - https://lore.kernel.org/lkml/cah2r5msnpjeabv2er7anqrsde-9vyrznsdif0+odojayl_a...@mail.gmail.com/ (and the other messages in the thread - https://github.com/openSUSE/kernel-source/commit/fe37c160c33dc09edff1781810aa098a2c316e20 Building nvidia under 5.10-rc1 or later fails, because of commit https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=596b0474d3d9b1242eab713f84d8873f9887d980 ** Affects: linux Importance: Unknown Status: Unknown ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Bug watch added: Debian Bug tracker #975571 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=975571 ** Also affects: linux via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=975571 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1906072 Title: Out-of-tree modules no longer build since 596b0474d3d9 in 5.10-rc1 Status in Linux: Unknown Status in linux package in Ubuntu: New Bug description: Hi, See these for reference: - https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=975571 - https://lore.kernel.org/lkml/cah2r5msnpjeabv2er7anqrsde-9vyrznsdif0+odojayl_a...@mail.gmail.com/ (and the other messages in the thread - https://github.com/openSUSE/kernel-source/commit/fe37c160c33dc09edff1781810aa098a2c316e20 Building nvidia under 5.10-rc1 or later fails, because of commit https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=596b0474d3d9b1242eab713f84d8873f9887d980 To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1906072/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1903768] Re: Bionic update: upstream stable patchset 2020-11-10
** Changed in: linux (Ubuntu Bionic) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1903768 Title: Bionic update: upstream stable patchset 2020-11-10 Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: Fix Committed Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: upstream stable patchset 2020-11-10 Ported from the following upstream stable releases: v4.14.202, v4.19.152, v4.14.203, v4.19.153 from git://git.kernel.org/ Bluetooth: fix kernel oops in store_pending_adv_report Bluetooth: Consolidate encryption handling in hci_encrypt_cfm Bluetooth: Fix update of connection state in `hci_encrypt_cfm` Bluetooth: Disconnect if E0 is used for Level 4 media: usbtv: Fix refcounting mixup USB: serial: option: add Cellient MPL200 card USB: serial: option: Add Telit FT980-KS composition staging: comedi: check validity of wMaxPacketSize of usb endpoints found USB: serial: pl2303: add device-id for HP GC device USB: serial: ftdi_sio: add support for FreeCalypso JTAG+UART adapters reiserfs: Initialize inode keys properly reiserfs: Fix oops during mount drivers/net/ethernet/marvell/mvmdio.c: Fix non OF case crypto: bcm - Verify GCM/CCM key length in setkey crypto: qat - check cipher length for aead AES-CBC-HMAC-SHA ARM: 8858/1: vdso: use $(LD) instead of $(CC) to link VDSO ARM: 8939/1: kbuild: use correct nm executable ARM: 8867/1: vdso: pass --be8 to linker if necessary UBUNTU: upstream stable to v4.14.202, v4.19.152 ibmveth: Switch order of ibmveth_helper calls. ibmveth: Identify ingress large send packets. ipv4: Restore flowi4_oif update before call to xfrm_lookup_route mlx4: handle non-napi callers to napi_poll net: usb: qmi_wwan: add Cellient MPL200 card tipc: fix the skb_unshare() in tipc_buf_append() net/ipv4: always honour route mtu during forwarding r8169: fix data corruption issue on RTL8402 binder: fix UAF when releasing todo list ALSA: bebob: potential info leak in hwdep_read() net: hdlc: In hdlc_rcv, check to make sure dev is an HDLC device net: hdlc_raw_eth: Clear the IFF_TX_SKB_SHARING flag after calling ether_setup nfc: Ensure presence of NFC_ATTR_FIRMWARE_NAME attribute in nfc_genl_fw_download() tcp: fix to update snd_wl1 in bulk receiver fast path icmp: randomize the global rate limiter cifs: remove bogus debug code cifs: Return the error from crypt_message when enc/dec key not found. KVM: x86/mmu: Commit zap of remaining invalid pages when recovering lpages KVM: SVM: Initialize prev_ga_tag before use ima: Don't ignore errors from crypto_shash_update() crypto: algif_aead - Do not set MAY_BACKLOG on the async path EDAC/i5100: Fix error handling order in i5100_init_one() x86/fpu: Allow multiple bits in clearcpuid= parameter drivers/perf: xgene_pmu: Fix uninitialized resource struct crypto: algif_skcipher - EBUSY on aio should be an error crypto: mediatek - Fix wrong return value in mtk_desc_ring_alloc() crypto: ixp4xx - Fix the size used in a 'dma_free_coherent()' call media: tuner-simple: fix regression in simple_set_radio_freq media: Revert "media: exynos4-is: Add missed check for pinctrl_lookup_state()" media: m5mols: Check function pointer in m5mols_sensor_power media: uvcvideo: Set media controller entity functions media: omap3isp: Fix memleak in isp_probe crypto: omap-sham - fix digcnt register handling with export/import cypto: mediatek - fix leaks in mtk_desc_ring_alloc media: mx2_emmaprp: Fix memleak in emmaprp_probe media: tc358743: initialize variable media: platform: fcp: Fix a reference count leak. media: s5p-mfc: Fix a reference count leak media: ti-vpe: Fix a missing check and reference count leak regulator: resolve supply after creating regulator ath10k: provide survey info as accumulated data Bluetooth: hci_uart: Cancel init work before unregistering ath6kl: prevent potential array overflow in ath6kl_add_new_sta() ath9k: Fix potential out of bounds in ath9k_htc_txcompletion_cb() wcn36xx: Fix reported 802.11n rx_highest rate wcn3660/wcn3680 ASoC: qcom: lpass-platform: fix memory leak ASoC: qcom: lpass-cpu: fix concurrency issue brcmfmac: check ndev pointer mwifiex: Do not use GFP_KERNEL in atomic context drm/gma500: fix error check scsi: qla4xxx:
[Kernel-packages] [Bug 1901755] Re: "btrfs subvolume list" sporadically segfaults with linux-image-5.4.0-52-generic
I'm still getting this error on Ubuntu 18.04 with kernel 5.4.0-54.60. Installed Mainline Kernel 5.9.10 as a workaround... -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1901755 Title: "btrfs subvolume list" sporadically segfaults with linux- image-5.4.0-52-generic Status in linux package in Ubuntu: Fix Committed Bug description: On a BTRFS volume with a lot of subvolumes, I get sporadic segfaults on "btrfs subvolume list", about 1/3 of the time. This is on Ubuntu 20.04. linux-image-5.4.0-48-generic does not experience those segfaults. On #btrfs on freenode, it was pointed out that 5.4.0-52.57 seems to have a regression but not the fix for it committed. To quote from the IRC message: > 5.4.0-52.57 has a regression (a48b73eca4ce btrfs: fix potential deadlock in the search ioctl) and not the fix (1c78544eaa46 btrfs: fix wrong address when faulting in pages in the search ioctl) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1901755/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1905993] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1905993/+attachment/5438833/+files/ProcModules.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1905993 Title: Actual kernel don't want to make more than 64 cpus available Status in linux package in Ubuntu: Incomplete Bug description: This is kinda complicated but i try my best to explain it as much as i can. First of all i found out that in bionic beaver cloud image i was able to have 248 cpus without any issues. Then i've taken a look into focal, but there i was only able to get up up to 64 cpus. Then i've tryed to figure out what was wrong. Debian, wasnt able to handle this with a 4.19 kernel. Bionic beaver had 4.18 so i tried to upgrade to a 4.19 with success but only with 64 cpus. So i think the problem maybe exist since 4.19. My setup. Openstack Hypervisor with ubuntu 18.04 KVM/Qemu with a vm clean bionic works fine, till i upgrade to a kernel > 4.18. Every 5.* version seems to be affected as well. Debian buster has this issue and fedora (Both in latest versions with kernel above 4.18) Already started debugging with TJ- at irc. Paste links with debugging informations /sys/devices/system/cpu/cpu*/topology/ http://paste.ubuntu.com/p/5txHGPHpBT/ and virsh dumpxml of the VM https://pastebin.ubuntu.com/p/sPWHVMn5FX/ CPU on the Hypervisor (works fine): https://pastebin.ubuntu.com/p/KRNMSThT92/ Hope this helps to dig down the bug. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.20 Architecture: amd64 DistroRelease: Ubuntu 18.04 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash Tags: bionic uec-images Uname: Linux 4.19.160-0419160-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip floppy lxd netdev plugdev sudo video _MarkForUpload: True --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Nov 27 21:50 seq crw-rw 1 root audio 116, 33 Nov 27 21:50 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.20 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A DistroRelease: Ubuntu 18.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: OpenStack Foundation OpenStack Nova Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-63-generic root=UUID=17d2bcf1-3687-426a-8219-978743746d51 ro console=tty1 console=ttyS0 ProcVersionSignature: Ubuntu 5.0.0-63.69-generic 5.0.21 RelatedPackageVersions: linux-restricted-modules-5.0.0-63-generic N/A linux-backports-modules-5.0.0-63-generic N/A linux-firmwareN/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic uec-images Uname: Linux 5.0.0-63-generic x86_64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip floppy lxd netdev plugdev sudo video _MarkForUpload: False dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.10.2-1ubuntu1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-4.0 dmi.modalias: dmi:bvnSeaBIOS:bvr1.10.2-1ubuntu1:bd04/01/2014:svnOpenStackFoundation:pnOpenStackNova:pvr20.1.1:cvnQEMU:ct1:cvrpc-i440fx-4.0: dmi.product.family: Virtual Machine dmi.product.name: OpenStack Nova dmi.product.version: 20.1.1 dmi.sys.vendor: OpenStack Foundation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1905993/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1905993] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1905993/+attachment/5438829/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1905993 Title: Actual kernel don't want to make more than 64 cpus available Status in linux package in Ubuntu: Incomplete Bug description: This is kinda complicated but i try my best to explain it as much as i can. First of all i found out that in bionic beaver cloud image i was able to have 248 cpus without any issues. Then i've taken a look into focal, but there i was only able to get up up to 64 cpus. Then i've tryed to figure out what was wrong. Debian, wasnt able to handle this with a 4.19 kernel. Bionic beaver had 4.18 so i tried to upgrade to a 4.19 with success but only with 64 cpus. So i think the problem maybe exist since 4.19. My setup. Openstack Hypervisor with ubuntu 18.04 KVM/Qemu with a vm clean bionic works fine, till i upgrade to a kernel > 4.18. Every 5.* version seems to be affected as well. Debian buster has this issue and fedora (Both in latest versions with kernel above 4.18) Already started debugging with TJ- at irc. Paste links with debugging informations /sys/devices/system/cpu/cpu*/topology/ http://paste.ubuntu.com/p/5txHGPHpBT/ and virsh dumpxml of the VM https://pastebin.ubuntu.com/p/sPWHVMn5FX/ CPU on the Hypervisor (works fine): https://pastebin.ubuntu.com/p/KRNMSThT92/ Hope this helps to dig down the bug. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.20 Architecture: amd64 DistroRelease: Ubuntu 18.04 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash Tags: bionic uec-images Uname: Linux 4.19.160-0419160-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip floppy lxd netdev plugdev sudo video _MarkForUpload: True --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Nov 27 21:50 seq crw-rw 1 root audio 116, 33 Nov 27 21:50 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.20 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A DistroRelease: Ubuntu 18.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: OpenStack Foundation OpenStack Nova Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-63-generic root=UUID=17d2bcf1-3687-426a-8219-978743746d51 ro console=tty1 console=ttyS0 ProcVersionSignature: Ubuntu 5.0.0-63.69-generic 5.0.21 RelatedPackageVersions: linux-restricted-modules-5.0.0-63-generic N/A linux-backports-modules-5.0.0-63-generic N/A linux-firmwareN/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic uec-images Uname: Linux 5.0.0-63-generic x86_64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip floppy lxd netdev plugdev sudo video _MarkForUpload: False dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.10.2-1ubuntu1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-4.0 dmi.modalias: dmi:bvnSeaBIOS:bvr1.10.2-1ubuntu1:bd04/01/2014:svnOpenStackFoundation:pnOpenStackNova:pvr20.1.1:cvnQEMU:ct1:cvrpc-i440fx-4.0: dmi.product.family: Virtual Machine dmi.product.name: OpenStack Nova dmi.product.version: 20.1.1 dmi.sys.vendor: OpenStack Foundation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1905993/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1905993] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1905993/+attachment/5438835/+files/WifiSyslog.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/1905993 Title: Actual kernel don't want to make more than 64 cpus available Status in linux package in Ubuntu: Incomplete Bug description: This is kinda complicated but i try my best to explain it as much as i can. First of all i found out that in bionic beaver cloud image i was able to have 248 cpus without any issues. Then i've taken a look into focal, but there i was only able to get up up to 64 cpus. Then i've tryed to figure out what was wrong. Debian, wasnt able to handle this with a 4.19 kernel. Bionic beaver had 4.18 so i tried to upgrade to a 4.19 with success but only with 64 cpus. So i think the problem maybe exist since 4.19. My setup. Openstack Hypervisor with ubuntu 18.04 KVM/Qemu with a vm clean bionic works fine, till i upgrade to a kernel > 4.18. Every 5.* version seems to be affected as well. Debian buster has this issue and fedora (Both in latest versions with kernel above 4.18) Already started debugging with TJ- at irc. Paste links with debugging informations /sys/devices/system/cpu/cpu*/topology/ http://paste.ubuntu.com/p/5txHGPHpBT/ and virsh dumpxml of the VM https://pastebin.ubuntu.com/p/sPWHVMn5FX/ CPU on the Hypervisor (works fine): https://pastebin.ubuntu.com/p/KRNMSThT92/ Hope this helps to dig down the bug. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.20 Architecture: amd64 DistroRelease: Ubuntu 18.04 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash Tags: bionic uec-images Uname: Linux 4.19.160-0419160-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip floppy lxd netdev plugdev sudo video _MarkForUpload: True --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Nov 27 21:50 seq crw-rw 1 root audio 116, 33 Nov 27 21:50 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.20 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A DistroRelease: Ubuntu 18.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: OpenStack Foundation OpenStack Nova Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-63-generic root=UUID=17d2bcf1-3687-426a-8219-978743746d51 ro console=tty1 console=ttyS0 ProcVersionSignature: Ubuntu 5.0.0-63.69-generic 5.0.21 RelatedPackageVersions: linux-restricted-modules-5.0.0-63-generic N/A linux-backports-modules-5.0.0-63-generic N/A linux-firmwareN/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic uec-images Uname: Linux 5.0.0-63-generic x86_64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip floppy lxd netdev plugdev sudo video _MarkForUpload: False dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.10.2-1ubuntu1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-4.0 dmi.modalias: dmi:bvnSeaBIOS:bvr1.10.2-1ubuntu1:bd04/01/2014:svnOpenStackFoundation:pnOpenStackNova:pvr20.1.1:cvnQEMU:ct1:cvrpc-i440fx-4.0: dmi.product.family: Virtual Machine dmi.product.name: OpenStack Nova dmi.product.version: 20.1.1 dmi.sys.vendor: OpenStack Foundation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1905993/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1905993] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1905993/+attachment/5438830/+files/Lspci.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1905993 Title: Actual kernel don't want to make more than 64 cpus available Status in linux package in Ubuntu: Incomplete Bug description: This is kinda complicated but i try my best to explain it as much as i can. First of all i found out that in bionic beaver cloud image i was able to have 248 cpus without any issues. Then i've taken a look into focal, but there i was only able to get up up to 64 cpus. Then i've tryed to figure out what was wrong. Debian, wasnt able to handle this with a 4.19 kernel. Bionic beaver had 4.18 so i tried to upgrade to a 4.19 with success but only with 64 cpus. So i think the problem maybe exist since 4.19. My setup. Openstack Hypervisor with ubuntu 18.04 KVM/Qemu with a vm clean bionic works fine, till i upgrade to a kernel > 4.18. Every 5.* version seems to be affected as well. Debian buster has this issue and fedora (Both in latest versions with kernel above 4.18) Already started debugging with TJ- at irc. Paste links with debugging informations /sys/devices/system/cpu/cpu*/topology/ http://paste.ubuntu.com/p/5txHGPHpBT/ and virsh dumpxml of the VM https://pastebin.ubuntu.com/p/sPWHVMn5FX/ CPU on the Hypervisor (works fine): https://pastebin.ubuntu.com/p/KRNMSThT92/ Hope this helps to dig down the bug. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.20 Architecture: amd64 DistroRelease: Ubuntu 18.04 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash Tags: bionic uec-images Uname: Linux 4.19.160-0419160-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip floppy lxd netdev plugdev sudo video _MarkForUpload: True --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Nov 27 21:50 seq crw-rw 1 root audio 116, 33 Nov 27 21:50 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.20 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A DistroRelease: Ubuntu 18.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: OpenStack Foundation OpenStack Nova Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-63-generic root=UUID=17d2bcf1-3687-426a-8219-978743746d51 ro console=tty1 console=ttyS0 ProcVersionSignature: Ubuntu 5.0.0-63.69-generic 5.0.21 RelatedPackageVersions: linux-restricted-modules-5.0.0-63-generic N/A linux-backports-modules-5.0.0-63-generic N/A linux-firmwareN/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic uec-images Uname: Linux 5.0.0-63-generic x86_64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip floppy lxd netdev plugdev sudo video _MarkForUpload: False dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.10.2-1ubuntu1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-4.0 dmi.modalias: dmi:bvnSeaBIOS:bvr1.10.2-1ubuntu1:bd04/01/2014:svnOpenStackFoundation:pnOpenStackNova:pvr20.1.1:cvnQEMU:ct1:cvrpc-i440fx-4.0: dmi.product.family: Virtual Machine dmi.product.name: OpenStack Nova dmi.product.version: 20.1.1 dmi.sys.vendor: OpenStack Foundation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1905993/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1905993] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1905993/+attachment/5438834/+files/UdevDb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1905993 Title: Actual kernel don't want to make more than 64 cpus available Status in linux package in Ubuntu: Incomplete Bug description: This is kinda complicated but i try my best to explain it as much as i can. First of all i found out that in bionic beaver cloud image i was able to have 248 cpus without any issues. Then i've taken a look into focal, but there i was only able to get up up to 64 cpus. Then i've tryed to figure out what was wrong. Debian, wasnt able to handle this with a 4.19 kernel. Bionic beaver had 4.18 so i tried to upgrade to a 4.19 with success but only with 64 cpus. So i think the problem maybe exist since 4.19. My setup. Openstack Hypervisor with ubuntu 18.04 KVM/Qemu with a vm clean bionic works fine, till i upgrade to a kernel > 4.18. Every 5.* version seems to be affected as well. Debian buster has this issue and fedora (Both in latest versions with kernel above 4.18) Already started debugging with TJ- at irc. Paste links with debugging informations /sys/devices/system/cpu/cpu*/topology/ http://paste.ubuntu.com/p/5txHGPHpBT/ and virsh dumpxml of the VM https://pastebin.ubuntu.com/p/sPWHVMn5FX/ CPU on the Hypervisor (works fine): https://pastebin.ubuntu.com/p/KRNMSThT92/ Hope this helps to dig down the bug. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.20 Architecture: amd64 DistroRelease: Ubuntu 18.04 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash Tags: bionic uec-images Uname: Linux 4.19.160-0419160-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip floppy lxd netdev plugdev sudo video _MarkForUpload: True --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Nov 27 21:50 seq crw-rw 1 root audio 116, 33 Nov 27 21:50 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.20 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A DistroRelease: Ubuntu 18.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: OpenStack Foundation OpenStack Nova Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-63-generic root=UUID=17d2bcf1-3687-426a-8219-978743746d51 ro console=tty1 console=ttyS0 ProcVersionSignature: Ubuntu 5.0.0-63.69-generic 5.0.21 RelatedPackageVersions: linux-restricted-modules-5.0.0-63-generic N/A linux-backports-modules-5.0.0-63-generic N/A linux-firmwareN/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic uec-images Uname: Linux 5.0.0-63-generic x86_64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip floppy lxd netdev plugdev sudo video _MarkForUpload: False dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.10.2-1ubuntu1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-4.0 dmi.modalias: dmi:bvnSeaBIOS:bvr1.10.2-1ubuntu1:bd04/01/2014:svnOpenStackFoundation:pnOpenStackNova:pvr20.1.1:cvnQEMU:ct1:cvrpc-i440fx-4.0: dmi.product.family: Virtual Machine dmi.product.name: OpenStack Nova dmi.product.version: 20.1.1 dmi.sys.vendor: OpenStack Foundation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1905993/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1905993] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1905993/+attachment/5438831/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1905993 Title: Actual kernel don't want to make more than 64 cpus available Status in linux package in Ubuntu: Incomplete Bug description: This is kinda complicated but i try my best to explain it as much as i can. First of all i found out that in bionic beaver cloud image i was able to have 248 cpus without any issues. Then i've taken a look into focal, but there i was only able to get up up to 64 cpus. Then i've tryed to figure out what was wrong. Debian, wasnt able to handle this with a 4.19 kernel. Bionic beaver had 4.18 so i tried to upgrade to a 4.19 with success but only with 64 cpus. So i think the problem maybe exist since 4.19. My setup. Openstack Hypervisor with ubuntu 18.04 KVM/Qemu with a vm clean bionic works fine, till i upgrade to a kernel > 4.18. Every 5.* version seems to be affected as well. Debian buster has this issue and fedora (Both in latest versions with kernel above 4.18) Already started debugging with TJ- at irc. Paste links with debugging informations /sys/devices/system/cpu/cpu*/topology/ http://paste.ubuntu.com/p/5txHGPHpBT/ and virsh dumpxml of the VM https://pastebin.ubuntu.com/p/sPWHVMn5FX/ CPU on the Hypervisor (works fine): https://pastebin.ubuntu.com/p/KRNMSThT92/ Hope this helps to dig down the bug. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.20 Architecture: amd64 DistroRelease: Ubuntu 18.04 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash Tags: bionic uec-images Uname: Linux 4.19.160-0419160-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip floppy lxd netdev plugdev sudo video _MarkForUpload: True --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Nov 27 21:50 seq crw-rw 1 root audio 116, 33 Nov 27 21:50 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.20 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A DistroRelease: Ubuntu 18.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: OpenStack Foundation OpenStack Nova Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-63-generic root=UUID=17d2bcf1-3687-426a-8219-978743746d51 ro console=tty1 console=ttyS0 ProcVersionSignature: Ubuntu 5.0.0-63.69-generic 5.0.21 RelatedPackageVersions: linux-restricted-modules-5.0.0-63-generic N/A linux-backports-modules-5.0.0-63-generic N/A linux-firmwareN/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic uec-images Uname: Linux 5.0.0-63-generic x86_64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip floppy lxd netdev plugdev sudo video _MarkForUpload: False dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.10.2-1ubuntu1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-4.0 dmi.modalias: dmi:bvnSeaBIOS:bvr1.10.2-1ubuntu1:bd04/01/2014:svnOpenStackFoundation:pnOpenStackNova:pvr20.1.1:cvnQEMU:ct1:cvrpc-i440fx-4.0: dmi.product.family: Virtual Machine dmi.product.name: OpenStack Nova dmi.product.version: 20.1.1 dmi.sys.vendor: OpenStack Foundation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1905993/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1905993] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1905993/+attachment/5438832/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1905993 Title: Actual kernel don't want to make more than 64 cpus available Status in linux package in Ubuntu: Incomplete Bug description: This is kinda complicated but i try my best to explain it as much as i can. First of all i found out that in bionic beaver cloud image i was able to have 248 cpus without any issues. Then i've taken a look into focal, but there i was only able to get up up to 64 cpus. Then i've tryed to figure out what was wrong. Debian, wasnt able to handle this with a 4.19 kernel. Bionic beaver had 4.18 so i tried to upgrade to a 4.19 with success but only with 64 cpus. So i think the problem maybe exist since 4.19. My setup. Openstack Hypervisor with ubuntu 18.04 KVM/Qemu with a vm clean bionic works fine, till i upgrade to a kernel > 4.18. Every 5.* version seems to be affected as well. Debian buster has this issue and fedora (Both in latest versions with kernel above 4.18) Already started debugging with TJ- at irc. Paste links with debugging informations /sys/devices/system/cpu/cpu*/topology/ http://paste.ubuntu.com/p/5txHGPHpBT/ and virsh dumpxml of the VM https://pastebin.ubuntu.com/p/sPWHVMn5FX/ CPU on the Hypervisor (works fine): https://pastebin.ubuntu.com/p/KRNMSThT92/ Hope this helps to dig down the bug. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.20 Architecture: amd64 DistroRelease: Ubuntu 18.04 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash Tags: bionic uec-images Uname: Linux 4.19.160-0419160-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip floppy lxd netdev plugdev sudo video _MarkForUpload: True --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Nov 27 21:50 seq crw-rw 1 root audio 116, 33 Nov 27 21:50 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.20 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A DistroRelease: Ubuntu 18.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: OpenStack Foundation OpenStack Nova Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-63-generic root=UUID=17d2bcf1-3687-426a-8219-978743746d51 ro console=tty1 console=ttyS0 ProcVersionSignature: Ubuntu 5.0.0-63.69-generic 5.0.21 RelatedPackageVersions: linux-restricted-modules-5.0.0-63-generic N/A linux-backports-modules-5.0.0-63-generic N/A linux-firmwareN/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic uec-images Uname: Linux 5.0.0-63-generic x86_64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip floppy lxd netdev plugdev sudo video _MarkForUpload: False dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.10.2-1ubuntu1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-4.0 dmi.modalias: dmi:bvnSeaBIOS:bvr1.10.2-1ubuntu1:bd04/01/2014:svnOpenStackFoundation:pnOpenStackNova:pvr20.1.1:cvnQEMU:ct1:cvrpc-i440fx-4.0: dmi.product.family: Virtual Machine dmi.product.name: OpenStack Nova dmi.product.version: 20.1.1 dmi.sys.vendor: OpenStack Foundation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1905993/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1905993] Re: Actual kernel don't want to make more than 64 cpus available
apport information ** Tags added: apport-collected bionic uec-images ** Description changed: This is kinda complicated but i try my best to explain it as much as i can. First of all i found out that in bionic beaver cloud image i was able to have 248 cpus without any issues. Then i've taken a look into focal, but there i was only able to get up up to 64 cpus. Then i've tryed to figure out what was wrong. Debian, wasnt able to handle this with a 4.19 kernel. Bionic beaver had 4.18 so i tried to upgrade to a 4.19 with success but only with 64 cpus. So i think the problem maybe exist since 4.19. My setup. Openstack Hypervisor with ubuntu 18.04 KVM/Qemu with a vm clean bionic works fine, till i upgrade to a kernel > 4.18. Every 5.* version seems to be affected as well. Debian buster has this issue and fedora (Both in latest versions with kernel above 4.18) Already started debugging with TJ- at irc. Paste links with debugging informations /sys/devices/system/cpu/cpu*/topology/ http://paste.ubuntu.com/p/5txHGPHpBT/ and virsh dumpxml of the VM https://pastebin.ubuntu.com/p/sPWHVMn5FX/ CPU on the Hypervisor (works fine): https://pastebin.ubuntu.com/p/KRNMSThT92/ Hope this helps to dig down the bug. + --- + ProblemType: Bug + ApportVersion: 2.20.9-0ubuntu7.20 + Architecture: amd64 + DistroRelease: Ubuntu 18.04 + Package: linux (not installed) + ProcEnviron: + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=C.UTF-8 + SHELL=/bin/bash + Tags: bionic uec-images + Uname: Linux 4.19.160-0419160-generic x86_64 + UnreportableReason: The running kernel is not an Ubuntu kernel + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm audio cdrom dialout dip floppy lxd netdev plugdev sudo video + _MarkForUpload: True ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1905993/+attachment/5438828/+files/ProcCpuinfoMinimal.txt ** Description changed: This is kinda complicated but i try my best to explain it as much as i can. First of all i found out that in bionic beaver cloud image i was able to have 248 cpus without any issues. Then i've taken a look into focal, but there i was only able to get up up to 64 cpus. Then i've tryed to figure out what was wrong. Debian, wasnt able to handle this with a 4.19 kernel. Bionic beaver had 4.18 so i tried to upgrade to a 4.19 with success but only with 64 cpus. So i think the problem maybe exist since 4.19. My setup. Openstack Hypervisor with ubuntu 18.04 KVM/Qemu with a vm clean bionic works fine, till i upgrade to a kernel > 4.18. Every 5.* version seems to be affected as well. Debian buster has this issue and fedora (Both in latest versions with kernel above 4.18) Already started debugging with TJ- at irc. Paste links with debugging informations /sys/devices/system/cpu/cpu*/topology/ http://paste.ubuntu.com/p/5txHGPHpBT/ and virsh dumpxml of the VM https://pastebin.ubuntu.com/p/sPWHVMn5FX/ CPU on the Hypervisor (works fine): https://pastebin.ubuntu.com/p/KRNMSThT92/ Hope this helps to dig down the bug. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.20 Architecture: amd64 DistroRelease: Ubuntu 18.04 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash Tags: bionic uec-images Uname: Linux 4.19.160-0419160-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip floppy lxd netdev plugdev sudo video _MarkForUpload: True + --- + ProblemType: Bug + AlsaDevices: + total 0 + crw-rw 1 root audio 116, 1 Nov 27 21:50 seq + crw-rw 1 root audio 116, 33 Nov 27 21:50 timer + AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' + ApportVersion: 2.20.9-0ubuntu7.20 + Architecture: amd64 + ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' + AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: + CRDA: N/A + DistroRelease: Ubuntu 18.04 + IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' + Lsusb: + Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd + Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub + MachineType: OpenStack Foundation OpenStack Nova + Package: linux (not installed) + PciMultimedia: + + ProcEnviron: + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=C.UTF-8 + SHELL=/bin/bash + ProcFB: + + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-63-generic root=UUID=17d2bcf1-3687-426a-8219-978743746d51 ro console=tty1 console=ttyS0 + ProcVersionSignature: Ubuntu 5.0.0-63.69-generic 5.0.21 +
[Kernel-packages] [Bug 1902588] Re: zfs mount -a: double free / memory corruption / segfault when mountpoint of dataset is not empty
debdiff for hirsute in attach. ** Patch added: "hirsute-zfs-fix-double-free-with-zfs-mount.debdiff" https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1902588/+attachment/5438827/+files/hirsute-zfs-fix-double-free-with-zfs-mount.debdiff -- 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/1902588 Title: zfs mount -a: double free / memory corruption / segfault when mountpoint of dataset is not empty Status in zfs-linux package in Ubuntu: New Status in zfs-linux source package in Xenial: New Status in zfs-linux source package in Bionic: New Status in zfs-linux source package in Focal: New Status in zfs-linux source package in Groovy: New Status in zfs-linux source package in Hirsute: New Bug description: == SRU Justification Focal == zfs mount -a when run on a nonempty mountpoint causes a double free, memory corruption, and a segfault. == Impact == Double free and memory corruption in ZFS when run as root and attempting to mount all. While running this I observed other ZFS volumes randomly unmounting, and mount points owner being spuriously zeroed (set to root). == Fix == https://github.com/openzfs/zfs/commit/d1b84da8c1a69c084f04b504beefe804591bca07 == Test == Steps are laid out in the ZFS issue: https://github.com/openzfs/zfs/issues/9560 == Regression Potential == Limited to the behavior of zfs mount when a previous attempt to mount has failed, or is still in progress. Changes the behavior in that case to failure, instead of double-free. Example case of running into this bug, with dmesg: https://pastebin.com/YRXW8WgM $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 20.04.1 LTS Release: 20.04 Codename: focal $ apt-cache policy zfsutils-linux zfsutils-linux: Installed: 0.8.3-1ubuntu12.4 Candidate: 0.8.3-1ubuntu12.4 Version table: *** 0.8.3-1ubuntu12.4 500 500 http://us.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 100 /var/lib/dpkg/status 0.8.3-1ubuntu12 500 500 http://us.archive.ubuntu.com/ubuntu focal/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1902588/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1902588] Re: zfs mount -a: double free / memory corruption / segfault when mountpoint of dataset is not empty
** Tags added: patch -- 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/1902588 Title: zfs mount -a: double free / memory corruption / segfault when mountpoint of dataset is not empty Status in zfs-linux package in Ubuntu: New Status in zfs-linux source package in Xenial: New Status in zfs-linux source package in Bionic: New Status in zfs-linux source package in Focal: New Status in zfs-linux source package in Groovy: New Status in zfs-linux source package in Hirsute: New Bug description: == SRU Justification Focal == zfs mount -a when run on a nonempty mountpoint causes a double free, memory corruption, and a segfault. == Impact == Double free and memory corruption in ZFS when run as root and attempting to mount all. While running this I observed other ZFS volumes randomly unmounting, and mount points owner being spuriously zeroed (set to root). == Fix == https://github.com/openzfs/zfs/commit/d1b84da8c1a69c084f04b504beefe804591bca07 == Test == Steps are laid out in the ZFS issue: https://github.com/openzfs/zfs/issues/9560 == Regression Potential == Limited to the behavior of zfs mount when a previous attempt to mount has failed, or is still in progress. Changes the behavior in that case to failure, instead of double-free. Example case of running into this bug, with dmesg: https://pastebin.com/YRXW8WgM $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 20.04.1 LTS Release: 20.04 Codename: focal $ apt-cache policy zfsutils-linux zfsutils-linux: Installed: 0.8.3-1ubuntu12.4 Candidate: 0.8.3-1ubuntu12.4 Version table: *** 0.8.3-1ubuntu12.4 500 500 http://us.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 100 /var/lib/dpkg/status 0.8.3-1ubuntu12 500 500 http://us.archive.ubuntu.com/ubuntu focal/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1902588/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1545320] Re: Dell XPS13 with i915 hangs with only mouse cursor and SSH working
No longer an issue on Ubuntu kernel 4.15.0-124-generic ** Changed in: linux (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1545320 Title: Dell XPS13 with i915 hangs with only mouse cursor and SSH working Status in Linux: Fix Released Status in linux package in Ubuntu: Fix Released Bug description: [42662.007846] [drm:check_crtc_state] [CRTC:21] [42662.007851] [drm:check_crtc_state] [CRTC:25] [42662.007852] [drm:check_crtc_state] [CRTC:29] [42662.007853] [drm:check_shared_dpll_state] WRPLL 1 [42662.007854] [drm:check_shared_dpll_state] WRPLL 2 [42662.074691] [ cut here ] [42662.074711] WARNING: CPU: 0 PID: 0 at /build/linux-NgsOGa/linux-4.2.0/drivers/gpu/drm/i915/intel_display.c:11102 intel_check_page_flip+0xfc/0x110 [i915]() [42662.074712] Kicking stuck page flip: queued at 1340036, now 1340040 [42662.074713] Modules linked in: cdc_acm hid_logitech_hidpp hid_logitech_dj hid_generic vmnet(OE) parport_pc vmw_vsock_vmci_transport vsock vmw_vmci vmmon(OE) rfcomm bnep pci_stub vboxpci(OE) vboxnetadp($ [42662.074740] snd_pcm rtsx_pci_ms snd_seq memstick snd_seq_device snd_timer snd shpchp soundcore mei_me lpc_ich mei soc_button_array int3403_thermal i2c_designware_platform int3402_thermal dw_dmac dw_dm$ [42662.074766] CPU: 0 PID: 0 Comm: swapper/0 Tainted: P OE 4.2.0-27-generic #32-Ubuntu [42662.074767] Hardware name: Dell Inc. XPS 13 9343/09K8G1, BIOS A05 07/14/2015 [42662.074768] 6e5309da9f364044 88021f403d48 817eae99 [42662.074770] 88021f403da0 88021f403d88 8107b9c6 [42662.074772] 88021f403db8 880210c5d800 8802113cf000 880210c5d9a8 [42662.074773] Call Trace: [42662.074774][] dump_stack+0x45/0x57 [42662.074780] [] warn_slowpath_common+0x86/0xc0 [42662.074782] [] warn_slowpath_fmt+0x55/0x70 [42662.074793] [] intel_check_page_flip+0xfc/0x110 [i915] [42662.074802] [] gen8_irq_handler+0x325/0x590 [i915] [42662.074804] [] handle_irq_event_percpu+0x74/0x180 [42662.074806] [] handle_irq_event+0x49/0x70 [42662.074808] [] handle_edge_irq+0x81/0x150 [42662.074810] [] handle_irq+0x25/0x40 [42662.074812] [] do_IRQ+0x4f/0xe0 [42662.074813] [] common_interrupt+0x6b/0x6b [42662.074814][] ? enqueue_hrtimer+0x44/0x80 [42662.074818] [] ? cpuidle_enter_state+0x130/0x270 [42662.074819] [] ? cpuidle_enter_state+0x10b/0x270 [42662.074821] [] cpuidle_enter+0x17/0x20 [42662.074822] [] call_cpuidle+0x32/0x60 [42662.074823] [] ? cpuidle_select+0x13/0x20 [42662.074825] [] cpu_startup_entry+0x268/0x320 ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: xserver-xorg-video-intel 2:2.99.917+git20150808-0ubuntu4 ProcVersionSignature: Ubuntu 4.2.0-27.32-generic 4.2.8-ckt1 Uname: Linux 4.2.0-27-generic x86_64 NonfreeKernelModules: wl .tmp.unity.support.test.0: ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Sat Feb 13 20:13:24 2016 DistUpgraded: 2015-11-15 21:52:38,727 DEBUG enabling apt cron job DistroCodename: wily DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.248+bdcom, 4.2.0-25-generic, x86_64: installed bcmwl, 6.30.223.248+bdcom, 4.2.0-27-generic, x86_64: installed vboxhost, 5.0.10, 4.2.0-25-generic, x86_64: installed vboxhost, 5.0.10, 4.2.0-27-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation Broadwell-U Integrated Graphics [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0665] InstallationDate: Installed on 2015-05-08 (281 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) MachineType: Dell Inc. XPS 13 9343 PlymouthDebug: Error: [Errno 13] Brak dostępu: '/var/log/plymouth-debug.log' ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.2.0-27-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro plymouth:debug splash quiet drm.debug=0xe crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M vt.handoff=7 SourcePackage: xserver-xorg-video-intel UdevLog: Error: [Errno 2] Nie ma takiego pliku ani katalogu: '/var/log/udev' UpgradeStatus: Upgraded to wily on 2015-11-15 (89 days ago) dmi.bios.date: 07/14/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A05 dmi.board.name: 09K8G1 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias:
[Kernel-packages] [Bug 1902588] Re: zfs mount -a: double free / memory corruption / segfault when mountpoint of dataset is not empty
debdiff for groovy in attach (all zfs autotests completed correctly). ** Patch added: "groovy-zfs-fix-double-free-with-zfs-mount.debdiff" https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1902588/+attachment/5438809/+files/groovy-zfs-fix-double-free-with-zfs-mount.debdiff -- 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/1902588 Title: zfs mount -a: double free / memory corruption / segfault when mountpoint of dataset is not empty Status in zfs-linux package in Ubuntu: New Status in zfs-linux source package in Xenial: New Status in zfs-linux source package in Bionic: New Status in zfs-linux source package in Focal: New Status in zfs-linux source package in Groovy: New Status in zfs-linux source package in Hirsute: New Bug description: == SRU Justification Focal == zfs mount -a when run on a nonempty mountpoint causes a double free, memory corruption, and a segfault. == Impact == Double free and memory corruption in ZFS when run as root and attempting to mount all. While running this I observed other ZFS volumes randomly unmounting, and mount points owner being spuriously zeroed (set to root). == Fix == https://github.com/openzfs/zfs/commit/d1b84da8c1a69c084f04b504beefe804591bca07 == Test == Steps are laid out in the ZFS issue: https://github.com/openzfs/zfs/issues/9560 == Regression Potential == Limited to the behavior of zfs mount when a previous attempt to mount has failed, or is still in progress. Changes the behavior in that case to failure, instead of double-free. Example case of running into this bug, with dmesg: https://pastebin.com/YRXW8WgM $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 20.04.1 LTS Release: 20.04 Codename: focal $ apt-cache policy zfsutils-linux zfsutils-linux: Installed: 0.8.3-1ubuntu12.4 Candidate: 0.8.3-1ubuntu12.4 Version table: *** 0.8.3-1ubuntu12.4 500 500 http://us.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 100 /var/lib/dpkg/status 0.8.3-1ubuntu12 500 500 http://us.archive.ubuntu.com/ubuntu focal/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1902588/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1905167] Re: htop shows 100% usage of systemd-udevd, constant spamming of nvidia in journalctl
** Summary changed: - htop shows 100% usage of systemd-udevd + htop shows 100% usage of systemd-udevd, constant spamming of nvidia in journalctl -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-455 in Ubuntu. https://bugs.launchpad.net/bugs/1905167 Title: htop shows 100% usage of systemd-udevd, constant spamming of nvidia in journalctl Status in nvidia-graphics-drivers-455 package in Ubuntu: New Status in systemd package in Ubuntu: Invalid Bug description: I'm attaching a perf profile. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: systemd 245.4-4ubuntu3.3 ProcVersionSignature: Ubuntu 5.4.0-54.60-lowlatency 5.4.65 Uname: Linux 5.4.0-54-lowlatency x86_64 ApportVersion: 2.20.11-0ubuntu27.12 Architecture: amd64 CasperMD5CheckResult: skip Date: Sun Nov 22 13:57:47 2020 InstallationDate: Installed on 2020-02-08 (287 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Acer Aspire A515-51G ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-54-lowlatency root=/dev/mapper/vgubuntu-root ro quiet splash resume=UUID=f0e63db4-d3af-4977-a82a-5a46a3c677ae lockdown=confidentiality intel_iommu=on iommu=pt vfio-pci.ids=10de:1d10 vt.handoff=7 SourcePackage: systemd SystemdDelta: [EXTENDED] /usr/lib/systemd/system/dnscrypt-proxy.service → /etc/systemd/system/dnscrypt-proxy.service.d/override.conf [EXTENDED] /usr/lib/systemd/system/rc-local.service → /usr/lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /usr/lib/systemd/system/user@.service → /usr/lib/systemd/system/user@.service.d/timeout.conf 3 overridden configuration files found. UpgradeStatus: Upgraded to focal on 2020-10-23 (29 days ago) dmi.bios.date: 01/03/2019 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V2.02 dmi.board.asset.tag: Type2 - Board Serial Number dmi.board.name: Charmander_KL dmi.board.vendor: KBL dmi.board.version: V2.02 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V2.02 dmi.modalias: dmi:bvnInsydeCorp.:bvrV2.02:bd01/03/2019:svnAcer:pnAspireA515-51G:pvrV2.02:rvnKBL:rnCharmander_KL:rvrV2.02:cvnAcer:ct10:cvrV2.02: dmi.product.family: Aspire 5 dmi.product.name: Aspire A515-51G dmi.product.sku: dmi.product.version: V2.02 dmi.sys.vendor: Acer mtime.conffile..etc.apport.crashdb.conf: 2020-05-15T09:41:35.683742 mtime.conffile..etc.systemd.sleep.conf: 2020-09-26T18:33:31.018002 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-455/+bug/1905167/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1905993] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1905993 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1905993 Title: Actual kernel don't want to make more than 64 cpus available Status in linux package in Ubuntu: Incomplete Bug description: This is kinda complicated but i try my best to explain it as much as i can. First of all i found out that in bionic beaver cloud image i was able to have 248 cpus without any issues. Then i've taken a look into focal, but there i was only able to get up up to 64 cpus. Then i've tryed to figure out what was wrong. Debian, wasnt able to handle this with a 4.19 kernel. Bionic beaver had 4.18 so i tried to upgrade to a 4.19 with success but only with 64 cpus. So i think the problem maybe exist since 4.19. My setup. Openstack Hypervisor with ubuntu 18.04 KVM/Qemu with a vm clean bionic works fine, till i upgrade to a kernel > 4.18. Every 5.* version seems to be affected as well. Debian buster has this issue and fedora (Both in latest versions with kernel above 4.18) Already started debugging with TJ- at irc. Paste links with debugging informations /sys/devices/system/cpu/cpu*/topology/ http://paste.ubuntu.com/p/5txHGPHpBT/ and virsh dumpxml of the VM https://pastebin.ubuntu.com/p/sPWHVMn5FX/ CPU on the Hypervisor (works fine): https://pastebin.ubuntu.com/p/KRNMSThT92/ Hope this helps to dig down the bug. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1905993/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1905994] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1905994 Title: failure to set dtr/rts on USB VCP causes kernel page fault Status in linux package in Ubuntu: Confirmed Bug description: attempting to reproduce bug https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1905782 on ubuntu 20.04.1 LTS yields a kernel OOOPS / page fault in the USB cdc_acm driver. will upload OOOPs shortly. steps to reproduce: 1. boot ubuntu 20.04.1 LTS (In this case from live CD) 2. plug in a USB device with a virtual com port 3. configure the TTY assigned (/dev/ttyACM0) setting dtr/rts (for example with minicom) 4. device does not support setting dtr/rts expected result: error message actual result: error message plus page fault in kernel space plus system becoming unstable will upload and attach dmesg log as soon as I managed to log the oops ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-42-generic 5.4.0-42.46 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 4492 F pulseaudio CasperMD5CheckMismatches: ./casper/filesystem.squashfs CasperMD5CheckResult: skip CasperVersion: 1.445.1 CurrentDesktop: ubuntu:GNOME Date: Fri Nov 27 17:37:22 2020 LiveMediaBuild: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: FUJITSU LIFEBOOK E736 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=/casper/vmlinuz file=/cdrom/preseed/username.seed maybe-ubiquity quiet splash --- RelatedPackageVersions: linux-restricted-modules-5.4.0-42-generic N/A linux-backports-modules-5.4.0-42-generic N/A linux-firmware1.187.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/20/2016 dmi.bios.vendor: FUJITSU // Insyde Software Corp. dmi.bios.version: Version 1.22 dmi.board.name: FJNB293 dmi.board.vendor: FUJITSU dmi.board.version: M4 dmi.chassis.type: 10 dmi.chassis.vendor: FUJITSU dmi.chassis.version: LIFEBOOK E736 dmi.modalias: dmi:bvnFUJITSU//InsydeSoftwareCorp.:bvrVersion1.22:bd12/20/2016:svnFUJITSU:pnLIFEBOOKE736:pvr10601115935:rvnFUJITSU:rnFJNB293:rvrM4:cvnFUJITSU:ct10:cvrLIFEBOOKE736: dmi.product.family: LIFEBOOK-FTS dmi.product.name: LIFEBOOK E736 dmi.product.version: 10601115935 dmi.sys.vendor: FUJITSU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1905994/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1905782] Re: kernel freeze on USB disconnect after failure to set rts/dts on USB VCP device
on Obuntu 20 LTS the same bug also exists, but with slightly different symptoms, see bug https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1905994 #1905994 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1905782 Title: kernel freeze on USB disconnect after failure to set rts/dts on USB VCP device Status in linux package in Ubuntu: Confirmed Bug description: When plugging in a USB device on Ubuntu 18.04 that offers a virtual modem/com port (typically /dev/ttyACM0) then the "modemmanager" service will try to configure this modem/serial port automatically without user interaction, setting dtr/rts parameters. However sometimes USB modem devices are used as a generic serial interface to hardware internals, without an actual serial line connected. Setting dtr/rts makes no sense in this context, and this feature might be unsupported. This, however, triggers a faulty code path in the linux kernel that on device disconnect causes a kworker process to freeze - blocking the CPU core it is running on indefinitely. This in turn has catastrophic effects on system stability. Some IO calls, that run on other cores, will work without problem, while those scheduled on the same core will never execute. Although no "OOPS" or "PANIC" is generated, the situation is dire, as the system typically can not be shutdown or rebooted, and during tests I ended up with file system corruption in a few cases that could not be fixed by a simple journal recovery To trigger this bug, several side-conditions need to be met: 1. A USB device needs to be plugged in that provides a virtual com port 2. The device must not support setting of DTR/RTS parameters 3. A program must try to set these via ioctls 4. The device must then be disconnected --> Kernel freeze On Ubuntu "3." is always guaranteed, if modemmanager is installed and the service is running Please contact me if you need additional information about how to reproduce this. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-124-generic 4.15.0-124.127 ProcVersionSignature: Ubuntu 4.15.0-124.127-generic 4.15.18 Uname: Linux 4.15.0-124-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.20 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: raven 2039 F pulseaudio CurrentDesktop: XFCE Date: Thu Nov 26 20:30:58 2020 EcryptfsInUse: Yes HibernationDevice: #RESUME=UUID=de4646dc-eb1a-4530-b6bc-df659b641728 RESUME=none InstallationDate: Installed on 2017-04-28 (1308 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) MachineType: FUJITSU LIFEBOOK E736 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-124-generic root=/dev/mapper/ubuntu--vg-root ro "acpi_osi=!Windows 2012" RelatedPackageVersions: linux-restricted-modules-4.15.0-124-generic N/A linux-backports-modules-4.15.0-124-generic N/A linux-firmware 1.173.19 SourcePackage: linux UpgradeStatus: Upgraded to bionic on 2019-06-28 (517 days ago) dmi.bios.date: 12/20/2016 dmi.bios.vendor: FUJITSU // Insyde Software Corp. dmi.bios.version: Version 1.22 dmi.board.name: FJNB293 dmi.board.vendor: FUJITSU dmi.board.version: M4 dmi.chassis.type: 10 dmi.chassis.vendor: FUJITSU dmi.chassis.version: LIFEBOOK E736 dmi.modalias: dmi:bvnFUJITSU//InsydeSoftwareCorp.:bvrVersion1.22:bd12/20/2016:svnFUJITSU:pnLIFEBOOKE736:pvr10601115935:rvnFUJITSU:rnFJNB293:rvrM4:cvnFUJITSU:ct10:cvrLIFEBOOKE736: dmi.product.family: LIFEBOOK-FTS dmi.product.name: LIFEBOOK E736 dmi.product.version: 10601115935 dmi.sys.vendor: FUJITSU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1905782/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1905994] Re: failure to set dtr/rts on USB VCP causes kernel page fault
note, as visible in the dmesg log, IO attempts with another unrelated USB device (the USB stick ubuntu had previously booted from) failed, causing IO errors, as the entire USB subsystem was down. this is also why I had to submit this bug with "ubuntu-bug" prior to actually causing the bug and upload the dmesg.log later, since ubuntu- bug would no longer be able to work after the OOPS happened. like with Ubuntu 18 this bug has the potential to cause data loss, make the system unstable, and a hard reboot is required to recover -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1905994 Title: failure to set dtr/rts on USB VCP causes kernel page fault Status in linux package in Ubuntu: Confirmed Bug description: attempting to reproduce bug https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1905782 on ubuntu 20.04.1 LTS yields a kernel OOOPS / page fault in the USB cdc_acm driver. will upload OOOPs shortly. steps to reproduce: 1. boot ubuntu 20.04.1 LTS (In this case from live CD) 2. plug in a USB device with a virtual com port 3. configure the TTY assigned (/dev/ttyACM0) setting dtr/rts (for example with minicom) 4. device does not support setting dtr/rts expected result: error message actual result: error message plus page fault in kernel space plus system becoming unstable will upload and attach dmesg log as soon as I managed to log the oops ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-42-generic 5.4.0-42.46 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 4492 F pulseaudio CasperMD5CheckMismatches: ./casper/filesystem.squashfs CasperMD5CheckResult: skip CasperVersion: 1.445.1 CurrentDesktop: ubuntu:GNOME Date: Fri Nov 27 17:37:22 2020 LiveMediaBuild: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: FUJITSU LIFEBOOK E736 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=/casper/vmlinuz file=/cdrom/preseed/username.seed maybe-ubiquity quiet splash --- RelatedPackageVersions: linux-restricted-modules-5.4.0-42-generic N/A linux-backports-modules-5.4.0-42-generic N/A linux-firmware1.187.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/20/2016 dmi.bios.vendor: FUJITSU // Insyde Software Corp. dmi.bios.version: Version 1.22 dmi.board.name: FJNB293 dmi.board.vendor: FUJITSU dmi.board.version: M4 dmi.chassis.type: 10 dmi.chassis.vendor: FUJITSU dmi.chassis.version: LIFEBOOK E736 dmi.modalias: dmi:bvnFUJITSU//InsydeSoftwareCorp.:bvrVersion1.22:bd12/20/2016:svnFUJITSU:pnLIFEBOOKE736:pvr10601115935:rvnFUJITSU:rnFJNB293:rvrM4:cvnFUJITSU:ct10:cvrLIFEBOOKE736: dmi.product.family: LIFEBOOK-FTS dmi.product.name: LIFEBOOK E736 dmi.product.version: 10601115935 dmi.sys.vendor: FUJITSU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1905994/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1905994] Re: failure to set dtr/rts on USB VCP causes kernel page fault
adding dmesg log of the OOOPS note that the behavior differs from bug #1905782 on Ubuntu 18. On Ubuntu 18 no OOPS is triggered, instead the driver enters an endless loop when the USB device gets disconnected later On Ubuntu 20 a kernel OOPS is generated and takes the whole USB stack with it. past that point no more USB events are generated and the system doesn't even notice USB devices getting plugged in or plugged out. note that to trigger the OOOPS I had to repeat the procedure to reproduce twice - connect, try to set dtr/rts, disconnect, connect again, once more try to set dtr/rts --> OOOPS on Ubuntu18 the modemmanager service automatically tried to set dtr/rts on the device. On Ubuntu 20 I had to do this by hand by opening the tty device with: minicom -o -D /dev/ttyACM0 ** Attachment added: "dmesg2.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1905994/+attachment/5438802/+files/dmesg2.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1905994 Title: failure to set dtr/rts on USB VCP causes kernel page fault Status in linux package in Ubuntu: Confirmed Bug description: attempting to reproduce bug https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1905782 on ubuntu 20.04.1 LTS yields a kernel OOOPS / page fault in the USB cdc_acm driver. will upload OOOPs shortly. steps to reproduce: 1. boot ubuntu 20.04.1 LTS (In this case from live CD) 2. plug in a USB device with a virtual com port 3. configure the TTY assigned (/dev/ttyACM0) setting dtr/rts (for example with minicom) 4. device does not support setting dtr/rts expected result: error message actual result: error message plus page fault in kernel space plus system becoming unstable will upload and attach dmesg log as soon as I managed to log the oops ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-42-generic 5.4.0-42.46 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 4492 F pulseaudio CasperMD5CheckMismatches: ./casper/filesystem.squashfs CasperMD5CheckResult: skip CasperVersion: 1.445.1 CurrentDesktop: ubuntu:GNOME Date: Fri Nov 27 17:37:22 2020 LiveMediaBuild: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: FUJITSU LIFEBOOK E736 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=/casper/vmlinuz file=/cdrom/preseed/username.seed maybe-ubiquity quiet splash --- RelatedPackageVersions: linux-restricted-modules-5.4.0-42-generic N/A linux-backports-modules-5.4.0-42-generic N/A linux-firmware1.187.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/20/2016 dmi.bios.vendor: FUJITSU // Insyde Software Corp. dmi.bios.version: Version 1.22 dmi.board.name: FJNB293 dmi.board.vendor: FUJITSU dmi.board.version: M4 dmi.chassis.type: 10 dmi.chassis.vendor: FUJITSU dmi.chassis.version: LIFEBOOK E736 dmi.modalias: dmi:bvnFUJITSU//InsydeSoftwareCorp.:bvrVersion1.22:bd12/20/2016:svnFUJITSU:pnLIFEBOOKE736:pvr10601115935:rvnFUJITSU:rnFJNB293:rvrM4:cvnFUJITSU:ct10:cvrLIFEBOOKE736: dmi.product.family: LIFEBOOK-FTS dmi.product.name: LIFEBOOK E736 dmi.product.version: 10601115935 dmi.sys.vendor: FUJITSU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1905994/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1902588] Re: zfs mount -a: double free / memory corruption / segfault when mountpoint of dataset is not empty
debdiff for focal reported in attach (built and tested). ** Patch added: "focal-zfs-fix-double-free-with-zfs-mount.debdiff" https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1902588/+attachment/5438801/+files/focal-zfs-fix-double-free-with-zfs-mount.debdiff -- 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/1902588 Title: zfs mount -a: double free / memory corruption / segfault when mountpoint of dataset is not empty Status in zfs-linux package in Ubuntu: New Status in zfs-linux source package in Xenial: New Status in zfs-linux source package in Bionic: New Status in zfs-linux source package in Focal: New Status in zfs-linux source package in Groovy: New Status in zfs-linux source package in Hirsute: New Bug description: == SRU Justification Focal == zfs mount -a when run on a nonempty mountpoint causes a double free, memory corruption, and a segfault. == Impact == Double free and memory corruption in ZFS when run as root and attempting to mount all. While running this I observed other ZFS volumes randomly unmounting, and mount points owner being spuriously zeroed (set to root). == Fix == https://github.com/openzfs/zfs/commit/d1b84da8c1a69c084f04b504beefe804591bca07 == Test == Steps are laid out in the ZFS issue: https://github.com/openzfs/zfs/issues/9560 == Regression Potential == Limited to the behavior of zfs mount when a previous attempt to mount has failed, or is still in progress. Changes the behavior in that case to failure, instead of double-free. Example case of running into this bug, with dmesg: https://pastebin.com/YRXW8WgM $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 20.04.1 LTS Release: 20.04 Codename: focal $ apt-cache policy zfsutils-linux zfsutils-linux: Installed: 0.8.3-1ubuntu12.4 Candidate: 0.8.3-1ubuntu12.4 Version table: *** 0.8.3-1ubuntu12.4 500 500 http://us.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 100 /var/lib/dpkg/status 0.8.3-1ubuntu12 500 500 http://us.archive.ubuntu.com/ubuntu focal/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1902588/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1905994] [NEW] failure to set dtr/rts on USB VCP causes kernel page fault
Public bug reported: attempting to reproduce bug https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1905782 on ubuntu 20.04.1 LTS yields a kernel OOOPS / page fault in the USB cdc_acm driver. will upload OOOPs shortly. steps to reproduce: 1. boot ubuntu 20.04.1 LTS (In this case from live CD) 2. plug in a USB device with a virtual com port 3. configure the TTY assigned (/dev/ttyACM0) setting dtr/rts (for example with minicom) 4. device does not support setting dtr/rts expected result: error message actual result: error message plus page fault in kernel space plus system becoming unstable will upload and attach dmesg log as soon as I managed to log the oops ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-42-generic 5.4.0-42.46 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 4492 F pulseaudio CasperMD5CheckMismatches: ./casper/filesystem.squashfs CasperMD5CheckResult: skip CasperVersion: 1.445.1 CurrentDesktop: ubuntu:GNOME Date: Fri Nov 27 17:37:22 2020 LiveMediaBuild: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: FUJITSU LIFEBOOK E736 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=/casper/vmlinuz file=/cdrom/preseed/username.seed maybe-ubiquity quiet splash --- RelatedPackageVersions: linux-restricted-modules-5.4.0-42-generic N/A linux-backports-modules-5.4.0-42-generic N/A linux-firmware1.187.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/20/2016 dmi.bios.vendor: FUJITSU // Insyde Software Corp. dmi.bios.version: Version 1.22 dmi.board.name: FJNB293 dmi.board.vendor: FUJITSU dmi.board.version: M4 dmi.chassis.type: 10 dmi.chassis.vendor: FUJITSU dmi.chassis.version: LIFEBOOK E736 dmi.modalias: dmi:bvnFUJITSU//InsydeSoftwareCorp.:bvrVersion1.22:bd12/20/2016:svnFUJITSU:pnLIFEBOOKE736:pvr10601115935:rvnFUJITSU:rnFJNB293:rvrM4:cvnFUJITSU:ct10:cvrLIFEBOOKE736: dmi.product.family: LIFEBOOK-FTS dmi.product.name: LIFEBOOK E736 dmi.product.version: 10601115935 dmi.sys.vendor: FUJITSU ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1905994 Title: failure to set dtr/rts on USB VCP causes kernel page fault Status in linux package in Ubuntu: New Bug description: attempting to reproduce bug https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1905782 on ubuntu 20.04.1 LTS yields a kernel OOOPS / page fault in the USB cdc_acm driver. will upload OOOPs shortly. steps to reproduce: 1. boot ubuntu 20.04.1 LTS (In this case from live CD) 2. plug in a USB device with a virtual com port 3. configure the TTY assigned (/dev/ttyACM0) setting dtr/rts (for example with minicom) 4. device does not support setting dtr/rts expected result: error message actual result: error message plus page fault in kernel space plus system becoming unstable will upload and attach dmesg log as soon as I managed to log the oops ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-42-generic 5.4.0-42.46 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 4492 F pulseaudio CasperMD5CheckMismatches: ./casper/filesystem.squashfs CasperMD5CheckResult: skip CasperVersion: 1.445.1 CurrentDesktop: ubuntu:GNOME Date: Fri Nov 27 17:37:22 2020 LiveMediaBuild: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: FUJITSU LIFEBOOK E736 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=/casper/vmlinuz file=/cdrom/preseed/username.seed maybe-ubiquity quiet splash --- RelatedPackageVersions: linux-restricted-modules-5.4.0-42-generic N/A linux-backports-modules-5.4.0-42-generic N/A linux-firmware1.187.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/20/2016 dmi.bios.vendor: FUJITSU // Insyde Software Corp. dmi.bios.version: Version 1.22 dmi.board.name: FJNB293 dmi.board.vendor: FUJITSU dmi.board.version: M4 dmi.chassis.type: 10 dmi.chassis.vendor: FUJITSU
[Kernel-packages] [Bug 1905993] Re: Actual kernel don't want to make more than 64 cpus available
** Project changed: launchpad => 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/1905993 Title: Actual kernel don't want to make more than 64 cpus available Status in linux package in Ubuntu: New Bug description: This is kinda complicated but i try my best to explain it as much as i can. First of all i found out that in bionic beaver cloud image i was able to have 248 cpus without any issues. Then i've taken a look into focal, but there i was only able to get up up to 64 cpus. Then i've tryed to figure out what was wrong. Debian, wasnt able to handle this with a 4.19 kernel. Bionic beaver had 4.18 so i tried to upgrade to a 4.19 with success but only with 64 cpus. So i think the problem maybe exist since 4.19. My setup. Openstack Hypervisor with ubuntu 18.04 KVM/Qemu with a vm clean bionic works fine, till i upgrade to a kernel > 4.18. Every 5.* version seems to be affected as well. Debian buster has this issue and fedora (Both in latest versions with kernel above 4.18) Already started debugging with TJ- at irc. Paste links with debugging informations /sys/devices/system/cpu/cpu*/topology/ http://paste.ubuntu.com/p/5txHGPHpBT/ and virsh dumpxml of the VM https://pastebin.ubuntu.com/p/sPWHVMn5FX/ CPU on the Hypervisor (works fine): https://pastebin.ubuntu.com/p/KRNMSThT92/ Hope this helps to dig down the bug. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1905993/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1905993] [NEW] Actual kernel don't want to make more than 64 cpus available
You have been subscribed to a public bug: This is kinda complicated but i try my best to explain it as much as i can. First of all i found out that in bionic beaver cloud image i was able to have 248 cpus without any issues. Then i've taken a look into focal, but there i was only able to get up up to 64 cpus. Then i've tryed to figure out what was wrong. Debian, wasnt able to handle this with a 4.19 kernel. Bionic beaver had 4.18 so i tried to upgrade to a 4.19 with success but only with 64 cpus. So i think the problem maybe exist since 4.19. My setup. Openstack Hypervisor with ubuntu 18.04 KVM/Qemu with a vm clean bionic works fine, till i upgrade to a kernel > 4.18. Every 5.* version seems to be affected as well. Debian buster has this issue and fedora (Both in latest versions with kernel above 4.18) Already started debugging with TJ- at irc. Paste links with debugging informations /sys/devices/system/cpu/cpu*/topology/ http://paste.ubuntu.com/p/5txHGPHpBT/ and virsh dumpxml of the VM https://pastebin.ubuntu.com/p/sPWHVMn5FX/ CPU on the Hypervisor (works fine): https://pastebin.ubuntu.com/p/KRNMSThT92/ Hope this helps to dig down the bug. ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- Actual kernel don't want to make more than 64 cpus available https://bugs.launchpad.net/bugs/1905993 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 1904589] Re: zfs PANIC: accessing past end of object in 0.8.3-1ubuntu12.4
** Description changed: + [Impact] + + zfs_write() doesn't properly account partial copies done by + copy_from_user(), causing accesses past the end of objects and + triggering kernel panics. + + [Test case] + + The problem seems to be workload specific, there is not a specific test + case to reproduce the problem, but the bug seems to be pretty well + identified by the upstream commit reported below. + + [Fix] + + Apply upstream commit c9e3efdb3a6111b9795becc6594b3c52ba004522 + ("Bugfix/fix uio partial copies"). + + [Regression potential] + + Upstream commit that is basically fixing potential out-of-bounds + accesses by properly checking partial copies done by copy_from_user() + and preventing kernel panics. Regression potential is minimal: it seems + unlikely to break other things if this change is applied. + + [Original bug report] + Using latest zfs 0.8.3-1ubuntu12.4 on latest Ubuntu 20.04.1, I observe a rare zfs panics that seem to be workload-specific which render a server mostly unresponsive besides ssh still working. Attempting to reboot the server in this state makes the shutdown hang forever. You may want to consider backporting the fix released in zfs 0.8.4 into 20.04: https://github.com/openzfs/zfs/pull/10148 Log sample of panic: ``` Nov 17 16:06:15 hostname kernel: [3385134.716024] PANIC: zfs: accessing past end of object c1c/2db52f (size=17408 access=7492+16428) Nov 17 16:06:15 hostname kernel: [3385134.716072] Showing stack for process 3166846 Nov 17 16:06:15 hostname kernel: [3385134.716074] CPU: 25 PID: 3166846 Comm: node Tainted: P O 5.4.0-48-generic #52-Ubuntu Nov 17 16:06:15 hostname kernel: [3385134.716075] Hardware name: Nov 17 16:06:15 hostname kernel: [3385134.716076] Call Trace: Nov 17 16:06:15 hostname kernel: [3385134.716085] dump_stack+0x6d/0x9a Nov 17 16:06:15 hostname kernel: [3385134.716097] spl_dumpstack+0x29/0x2b [spl] Nov 17 16:06:15 hostname kernel: [3385134.716102] vcmn_err.cold+0x60/0x99 [spl] Nov 17 16:06:15 hostname kernel: [3385134.716106] ? _cond_resched+0x19/0x30 Nov 17 16:06:15 hostname kernel: [3385134.716108] ? __kmalloc_node+0x20e/0x330 Nov 17 16:06:15 hostname kernel: [3385134.716113] ? spl_kmem_alloc_impl+0xa8/0x100 [spl] Nov 17 16:06:15 hostname kernel: [3385134.716190] ? __list_add+0x17/0x40 [zfs] Nov 17 16:06:15 hostname kernel: [3385134.716235] zfs_panic_recover+0x6f/0x90 [zfs] Nov 17 16:06:15 hostname kernel: [3385134.716272] ? dsl_dir_tempreserve_impl.isra.0.constprop.0+0xed/0x330 [zfs] Nov 17 16:06:15 hostname kernel: [3385134.716305] dmu_buf_hold_array_by_dnode+0x3a0/0x490 [zfs] Nov 17 16:06:15 hostname kernel: [3385134.716338] dmu_write_uio_dnode+0x4c/0x140 [zfs] Nov 17 16:06:15 hostname kernel: [3385134.716370] dmu_write_uio_dbuf+0x4f/0x70 [zfs] Nov 17 16:06:15 hostname kernel: [3385134.716416] zfs_write+0xa1f/0xd40 [zfs] Nov 17 16:06:15 hostname kernel: [3385134.716419] ? d_absolute_path+0x74/0xb0 Nov 17 16:06:15 hostname kernel: [3385134.716421] ? __switch_to_asm+0x34/0x70 Nov 17 16:06:15 hostname kernel: [3385134.716423] ? __switch_to_asm+0x40/0x70 Nov 17 16:06:15 hostname kernel: [3385134.716424] ? __switch_to_asm+0x40/0x70 Nov 17 16:06:15 hostname kernel: [3385134.716425] ? __switch_to_asm+0x34/0x70 Nov 17 16:06:15 hostname kernel: [3385134.716427] ? __switch_to_asm+0x34/0x70 Nov 17 16:06:15 hostname kernel: [3385134.716474] zpl_write_common_iovec+0xad/0x120 [zfs] Nov 17 16:06:15 hostname kernel: [3385134.716567] zpl_iter_write+0x56/0x90 [zfs] Nov 17 16:06:15 hostname kernel: [3385134.716570] do_iter_write+0x84/0x1a0 Nov 17 16:06:15 hostname kernel: [3385134.716574] ? futex_wake+0x8b/0x180 Nov 17 16:06:15 hostname kernel: [3385134.716577] do_writev+0x71/0x120 Nov 17 16:06:15 hostname kernel: [3385134.716581] do_syscall_64+0x57/0x190 Nov 17 16:06:15 hostname kernel: [3385134.716584] RIP: 0033:0x7fa366eee0cd Nov 17 16:06:15 hostname kernel: [3385134.716587] RSP: 002b:7fa35e7fbde0 EFLAGS: 0293 ORIG_RAX: 0014 Nov 17 16:06:15 hostname kernel: [3385134.716590] RDX: 000c RSI: 0651c7b0 RDI: 001d ``` -- 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/1904589 Title: zfs PANIC: accessing past end of object in 0.8.3-1ubuntu12.4 Status in zfs-linux package in Ubuntu: Fix Released Status in zfs-linux source package in Focal: In Progress Status in zfs-linux source package in Groovy: Fix Released Status in zfs-linux source package in Hirsute: Fix Released Bug description: [Impact] zfs_write() doesn't properly account partial copies done by copy_from_user(), causing accesses past the end of objects and triggering kernel panics. [Test case] The problem seems to be workload specific, there is not a specific test case
[Kernel-packages] [Bug 1902588] Re: zfs mount -a: double free / memory corruption / segfault when mountpoint of dataset is not empty
** Also affects: zfs-linux (Ubuntu Groovy) Importance: Undecided Status: New ** Also affects: zfs-linux (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: zfs-linux (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: zfs-linux (Ubuntu Hirsute) Importance: Undecided Status: New ** Also affects: zfs-linux (Ubuntu Focal) Importance: Undecided Status: New -- 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/1902588 Title: zfs mount -a: double free / memory corruption / segfault when mountpoint of dataset is not empty Status in zfs-linux package in Ubuntu: New Status in zfs-linux source package in Xenial: New Status in zfs-linux source package in Bionic: New Status in zfs-linux source package in Focal: New Status in zfs-linux source package in Groovy: New Status in zfs-linux source package in Hirsute: New Bug description: == SRU Justification Focal == zfs mount -a when run on a nonempty mountpoint causes a double free, memory corruption, and a segfault. == Impact == Double free and memory corruption in ZFS when run as root and attempting to mount all. While running this I observed other ZFS volumes randomly unmounting, and mount points owner being spuriously zeroed (set to root). == Fix == https://github.com/openzfs/zfs/commit/d1b84da8c1a69c084f04b504beefe804591bca07 == Test == Steps are laid out in the ZFS issue: https://github.com/openzfs/zfs/issues/9560 == Regression Potential == Limited to the behavior of zfs mount when a previous attempt to mount has failed, or is still in progress. Changes the behavior in that case to failure, instead of double-free. Example case of running into this bug, with dmesg: https://pastebin.com/YRXW8WgM $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 20.04.1 LTS Release: 20.04 Codename: focal $ apt-cache policy zfsutils-linux zfsutils-linux: Installed: 0.8.3-1ubuntu12.4 Candidate: 0.8.3-1ubuntu12.4 Version table: *** 0.8.3-1ubuntu12.4 500 500 http://us.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 100 /var/lib/dpkg/status 0.8.3-1ubuntu12 500 500 http://us.archive.ubuntu.com/ubuntu focal/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1902588/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1903969] Re: failed to boot to GUI: i915 0000:00:02.0: [drm] *ERROR* Link Training Unsuccessful
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- focal' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.6 in Ubuntu. https://bugs.launchpad.net/bugs/1903969 Title: failed to boot to GUI: i915 :00:02.0: [drm] *ERROR* Link Training Unsuccessful Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux-oem-5.6 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-oem-5.10 source package in Focal: Fix Committed Status in linux-oem-5.6 source package in Focal: New Status in linux source package in Groovy: Won't Fix Status in linux-oem-5.10 source package in Groovy: Invalid Status in linux-oem-5.6 source package in Groovy: Invalid Status in linux source package in Hirsute: In Progress Status in linux-oem-5.10 source package in Hirsute: Invalid Status in linux-oem-5.6 source package in Hirsute: Invalid Bug description: [SRU Justification] [Impact] On platforms supported DP tunneling over USB 3.2 or so, a Retimer is required on the host side to cover insertion loss. On such platforms the rtimer firmware maybe configured to use LTTPR (Link Training Tunable PHY Repeater) non-transparent mode only, which is only supported in drm-tip currently. Without LTTPR support, link training may fail with following error messages depending on the data path configuration: i915 :00:02.0: [drm] *ERROR* Link Training Unsuccessful i915 :00:02.0: [drm] *ERROR* CPU pipe A FIFO underrun [Fix] Patchset https://www.spinics.net/lists/intel-gfx/msg248700.html ("drm/i915: Add support for LTTPR non-transparent link training mode") is required to fix this issue. It has been landed to drm-tip and will only be merged to mainline in v5.11. Patchset https://patchwork.freedesktop.org/series/76993/ ("Plumb crtc state to link training code") is included for link training functions prototype changes. [Test Case] On Dell OptiPlex and WD19 docking station, use following steps to verify: 1. disconnect WD19 from OptiPlex, disconnect OptiPlex's power 2. attach OptiPlex's power cord 3. attach WD19's power cord 4. attach DP to WD19 5. attach WD19 to OptiPlex 6. boot up and check if boot to GUI directly 7. `dmesg` and check if aforementioned DRM link training error appears [Where problems could occur] The second patchset pulled for dependency doesn't have too much effective changes but refactoring some translation functions, so very unlikely to have regressions. For the major part, LTTPR support, when LTTPR is either not detected or not supported, it will fall back to use transparent mode as it was. Otherwise, DP Standard recommends to use LTTPR non-transparent mode for link training, so this should be the right way to have best hardware support. == original bug description == [Summary] When the monitor ONLY is connected to the WD19 (DP port) and WD19 is connected to the type c port than boot the machine, the monitor shows no video output after loaded i915. [Reproduce Steps] 1. connect power cable of WD19 2. connect DP cable from monitor to WD19 3. connect power cable to target system. 4. connect type c cable from WD19 to target system 5. boot up [Results] Expected: video output as there is only one monitor connected. Actual: No video output. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.6.0-1033-oem 5.6.0-1033.35 ProcVersionSignature: Ubuntu 5.6.0-1033.35-oem 5.6.19 Uname: Linux 5.6.0-1033-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.11 Architecture: amd64 CasperMD5CheckResult: skip Date: Thu Nov 12 05:11:11 2020 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-metapod+X40 InstallationDate: Installed on 2020-11-03 (9 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 SourcePackage: linux-signed-oem-5.6 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to:
[Kernel-packages] [Bug 1905975] Re: kernel: Enable CONFIG_BPF_LSM on Ubuntu
(This is a feature request, so no log needed.) ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed ** Also affects: linux (Ubuntu Hirsute) Importance: Undecided Status: Confirmed ** Also affects: linux (Ubuntu Groovy) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Groovy) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1905975 Title: kernel: Enable CONFIG_BPF_LSM on Ubuntu Status in linux package in Ubuntu: Confirmed Status in linux source package in Groovy: Confirmed Status in linux source package in Hirsute: Confirmed Bug description: == Impact == Enabling CONFIG_BPF_LSM in the KConfig of Ubuntu Kernels, allowing users to use BPF LSM programs. == Background == The BPF LSM was merged into the Linux kernel 5.7 https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=641cd7b06c911c5935c34f24850ea18690649917 https://outflux.net/blog/archives/2020/09/21/security-things-in- linux-v5-7 It allows users to implement MAC and Audit Policies using BPF programs. As a follow-up from the interest generated by the LSM on BPF/Linux conferences and on request from users, we’d like to request the enabling of CONFIG_BPF_LSM on Ubuntu starting with H. The LSM won't be added to the list of active LSMs by default (in CONFIG_LSM or lsm= on the boot parameters) yet, as it adds an indirect function call overhead by registering an empty LSM hook for all hooks. However enabling it in the kernel config will support users who wish to use BPF LSM programs without needing to replace their kernel image. The LSM can be made "active" by default when our work on getting rid of this overhead is merged in the kernel: https://lore.kernel.org/bpf/20200820164753.3256899-1-jackm...@chromium.org == Regression Potential == None. The LSM is not active by default, so it does not have any performance or functional regression. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1905975/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1904589] Re: zfs PANIC: accessing past end of object in 0.8.3-1ubuntu12.4
I've uploaded the fixed package, it will be available in the -proposed pocket for SRU testing at some point in the near future. -- 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/1904589 Title: zfs PANIC: accessing past end of object in 0.8.3-1ubuntu12.4 Status in zfs-linux package in Ubuntu: Fix Released Status in zfs-linux source package in Focal: In Progress Status in zfs-linux source package in Groovy: Fix Released Status in zfs-linux source package in Hirsute: Fix Released Bug description: Using latest zfs 0.8.3-1ubuntu12.4 on latest Ubuntu 20.04.1, I observe a rare zfs panics that seem to be workload-specific which render a server mostly unresponsive besides ssh still working. Attempting to reboot the server in this state makes the shutdown hang forever. You may want to consider backporting the fix released in zfs 0.8.4 into 20.04: https://github.com/openzfs/zfs/pull/10148 Log sample of panic: ``` Nov 17 16:06:15 hostname kernel: [3385134.716024] PANIC: zfs: accessing past end of object c1c/2db52f (size=17408 access=7492+16428) Nov 17 16:06:15 hostname kernel: [3385134.716072] Showing stack for process 3166846 Nov 17 16:06:15 hostname kernel: [3385134.716074] CPU: 25 PID: 3166846 Comm: node Tainted: P O 5.4.0-48-generic #52-Ubuntu Nov 17 16:06:15 hostname kernel: [3385134.716075] Hardware name: Nov 17 16:06:15 hostname kernel: [3385134.716076] Call Trace: Nov 17 16:06:15 hostname kernel: [3385134.716085] dump_stack+0x6d/0x9a Nov 17 16:06:15 hostname kernel: [3385134.716097] spl_dumpstack+0x29/0x2b [spl] Nov 17 16:06:15 hostname kernel: [3385134.716102] vcmn_err.cold+0x60/0x99 [spl] Nov 17 16:06:15 hostname kernel: [3385134.716106] ? _cond_resched+0x19/0x30 Nov 17 16:06:15 hostname kernel: [3385134.716108] ? __kmalloc_node+0x20e/0x330 Nov 17 16:06:15 hostname kernel: [3385134.716113] ? spl_kmem_alloc_impl+0xa8/0x100 [spl] Nov 17 16:06:15 hostname kernel: [3385134.716190] ? __list_add+0x17/0x40 [zfs] Nov 17 16:06:15 hostname kernel: [3385134.716235] zfs_panic_recover+0x6f/0x90 [zfs] Nov 17 16:06:15 hostname kernel: [3385134.716272] ? dsl_dir_tempreserve_impl.isra.0.constprop.0+0xed/0x330 [zfs] Nov 17 16:06:15 hostname kernel: [3385134.716305] dmu_buf_hold_array_by_dnode+0x3a0/0x490 [zfs] Nov 17 16:06:15 hostname kernel: [3385134.716338] dmu_write_uio_dnode+0x4c/0x140 [zfs] Nov 17 16:06:15 hostname kernel: [3385134.716370] dmu_write_uio_dbuf+0x4f/0x70 [zfs] Nov 17 16:06:15 hostname kernel: [3385134.716416] zfs_write+0xa1f/0xd40 [zfs] Nov 17 16:06:15 hostname kernel: [3385134.716419] ? d_absolute_path+0x74/0xb0 Nov 17 16:06:15 hostname kernel: [3385134.716421] ? __switch_to_asm+0x34/0x70 Nov 17 16:06:15 hostname kernel: [3385134.716423] ? __switch_to_asm+0x40/0x70 Nov 17 16:06:15 hostname kernel: [3385134.716424] ? __switch_to_asm+0x40/0x70 Nov 17 16:06:15 hostname kernel: [3385134.716425] ? __switch_to_asm+0x34/0x70 Nov 17 16:06:15 hostname kernel: [3385134.716427] ? __switch_to_asm+0x34/0x70 Nov 17 16:06:15 hostname kernel: [3385134.716474] zpl_write_common_iovec+0xad/0x120 [zfs] Nov 17 16:06:15 hostname kernel: [3385134.716567] zpl_iter_write+0x56/0x90 [zfs] Nov 17 16:06:15 hostname kernel: [3385134.716570] do_iter_write+0x84/0x1a0 Nov 17 16:06:15 hostname kernel: [3385134.716574] ? futex_wake+0x8b/0x180 Nov 17 16:06:15 hostname kernel: [3385134.716577] do_writev+0x71/0x120 Nov 17 16:06:15 hostname kernel: [3385134.716581] do_syscall_64+0x57/0x190 Nov 17 16:06:15 hostname kernel: [3385134.716584] RIP: 0033:0x7fa366eee0cd Nov 17 16:06:15 hostname kernel: [3385134.716587] RSP: 002b:7fa35e7fbde0 EFLAGS: 0293 ORIG_RAX: 0014 Nov 17 16:06:15 hostname kernel: [3385134.716590] RDX: 000c RSI: 0651c7b0 RDI: 001d ``` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1904589/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1905336] Re: sha1_ce and sha2_ce modules no longer load on arm64
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- xenial' to 'verification-done-xenial'. If the problem still exists, change the tag 'verification-needed-xenial' to 'verification-failed- xenial'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-xenial -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1905336 Title: sha1_ce and sha2_ce modules no longer load on arm64 Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Fix Committed Bug description: [Impact] The sha{1,2}_ce modules no longer load on arm64, preventing the use of the hardware accelerated ARMv8 crypto extensions for SHA1, SHA-224/SHA-256. [Test Case] sudo modprobe sha1_ce Currently fails: [ 33.838295] module sha1_ce: unsupported RELA relocation: 275 [Fix] For now I suggest reverting the commit that introduced the regression: 2675530a1d16 crypto: arm64/sha - avoid non-standard inline asm tricks [Where problems could occur] The purpose of this commit appears to be better compatibility with Clang, so regressions are likely to be with any developers using Clang with our kernel source. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1905336/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1905475] Re: Fails to build on powerpc
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- xenial' to 'verification-done-xenial'. If the problem still exists, change the tag 'verification-needed-xenial' to 'verification-failed- xenial'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-xenial -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1905475 Title: Fails to build on powerpc Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Fix Committed Bug description: [Impact] powerpc flavor powerpc64-emb fails to build with kernel 4.4.0-196. [Test case] Build the kernel with all powerpc flavors. [Potential regression] The kernel might still not boot. Userspace data might be corrupted when kernel writes to it. Kernel might not read userspace data correctly and on-disk data would get corrupted. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1905475/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1905984] Re: Hard lockup with "watchdog: BUG: soft lockup - CPU#10 stuck for 22s! [Xorg:13615]" in the journal
Looking through the journal further, I do see non-NVidia call traces such as: Nov 27 09:43:52 surprise kernel: INFO: task qemu-system-x86:16736 blocked for more than 120 seconds. Nov 27 09:43:52 surprise kernel: Tainted: P OEL 5.8.0-29-generic #31-Ubuntu Nov 27 09:43:52 surprise kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. Nov 27 09:43:52 surprise kernel: qemu-system-x86 D0 16736 1 0x0320 Nov 27 09:43:52 surprise kernel: Call Trace: Nov 27 09:43:52 surprise kernel: __schedule+0x212/0x5d0 Nov 27 09:43:52 surprise kernel: ? usleep_range+0x90/0x90 Nov 27 09:43:52 surprise kernel: schedule+0x55/0xc0 Nov 27 09:43:52 surprise kernel: schedule_timeout+0x10f/0x160 Nov 27 09:43:52 surprise kernel: ? do_sync_core+0x1d/0x20 Nov 27 09:43:52 surprise kernel: __wait_for_common+0xa8/0x150 Nov 27 09:43:52 surprise kernel: wait_for_completion+0x24/0x30 Nov 27 09:43:52 surprise kernel: __wait_rcu_gp+0x11b/0x120 Nov 27 09:43:52 surprise kernel: synchronize_rcu+0x67/0x70 Nov 27 09:43:52 surprise kernel: ? __call_rcu+0x250/0x250 Nov 27 09:43:52 surprise kernel: ? __bpf_trace_rcu_utilization+0x10/0x10 Nov 27 09:43:52 surprise kernel: account_event+0x1e8/0x1f0 Nov 27 09:43:52 surprise kernel: perf_event_alloc+0x77e/0x920 Nov 27 09:43:52 surprise kernel: ? kvm_perf_overflow+0x40/0x40 [kvm] Nov 27 09:43:52 surprise kernel: perf_event_create_kernel_counter.part.0+0x21/0x160 Nov 27 09:43:52 surprise kernel: perf_event_create_kernel_counter+0xf/0x20 Nov 27 09:43:52 surprise kernel: pmc_reprogram_counter+0x105/0x190 [kvm] Nov 27 09:43:52 surprise kernel: reprogram_gp_counter+0x194/0x210 [kvm] Nov 27 09:43:52 surprise kernel: amd_pmu_set_msr+0x17d/0x190 [kvm_amd] Nov 27 09:43:52 surprise kernel: kvm_pmu_set_msr+0x4e/0x60 [kvm] Nov 27 09:43:52 surprise kernel: kvm_set_msr_common+0x4cc/0xf00 [kvm] Nov 27 09:43:52 surprise kernel: svm_set_msr+0x39d/0x6e0 [kvm_amd] Nov 27 09:43:52 surprise kernel: __kvm_set_msr+0x8a/0x150 [kvm] Nov 27 09:43:52 surprise kernel: kvm_emulate_wrmsr+0x3c/0x120 [kvm] Nov 27 09:43:52 surprise kernel: handle_exit+0x39a/0x420 [kvm_amd] Nov 27 09:43:52 surprise kernel: ? kvm_set_cr8+0x22/0x40 [kvm] Nov 27 09:43:52 surprise kernel: vcpu_enter_guest+0x862/0xd90 [kvm] Nov 27 09:43:52 surprise kernel: ? kvm_apic_has_interrupt+0x41/0x80 [kvm] Nov 27 09:43:52 surprise kernel: ? kvm_cpu_has_interrupt+0x7a/0x90 [kvm] Nov 27 09:43:52 surprise kernel: ? kvm_vcpu_has_events+0x134/0x190 [kvm] Nov 27 09:43:52 surprise kernel: vcpu_run+0x76/0x240 [kvm] Nov 27 09:43:52 surprise kernel: kvm_arch_vcpu_ioctl_run+0x9f/0x2b0 [kvm] Nov 27 09:43:52 surprise kernel: kvm_vcpu_ioctl+0x247/0x600 [kvm] Nov 27 09:43:52 surprise kernel: ksys_ioctl+0x8e/0xc0 Nov 27 09:43:52 surprise kernel: __x64_sys_ioctl+0x1a/0x20 Nov 27 09:43:52 surprise kernel: do_syscall_64+0x49/0xc0 Nov 27 09:43:52 surprise kernel: entry_SYSCALL_64_after_hwframe+0x44/0xa9 Nov 27 09:43:52 surprise kernel: RIP: 0033:0x7fc2853b16d7 Nov 27 09:43:52 surprise kernel: Code: Bad RIP value. Nov 27 09:43:52 surprise kernel: RSP: 002b:7fc276220068 EFLAGS: 0246 ORIG_RAX: 0010 Nov 27 09:43:52 surprise kernel: RAX: ffda RBX: ae80 RCX: 7fc2853b16d7 Nov 27 09:43:52 surprise kernel: RDX: RSI: ae80 RDI: 0023 Nov 27 09:43:52 surprise kernel: RBP: R08: 564557831eb0 R09: ffe1 Nov 27 09:43:52 surprise kernel: R10: 0001 R11: 0246 R12: 564557ba8ad0 Nov 27 09:43:52 surprise kernel: R13: 564556b5c040 R14: 7fc28901 R15: -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-450 in Ubuntu. https://bugs.launchpad.net/bugs/1905984 Title: Hard lockup with "watchdog: BUG: soft lockup - CPU#10 stuck for 22s! [Xorg:13615]" in the journal Status in nvidia-graphics-drivers-450 package in Ubuntu: New Bug description: The system was restored from hibernation this morning, but the issue did not exhibit for ~30 minutes after "boot". I have also seen hard locks without hibernation (but they have never produced any journal output, so may be a different issue). Examining `journalctl -k`, I see something like the below repeated every few seconds. I've attached `journalctl -k`s output (truncated from unhibernate this morning). Nov 27 09:42:09 surprise kernel: watchdog: BUG: soft lockup - CPU#10 stuck for 22s! [Xorg:13615] Nov 27 09:42:09 surprise kernel: Modules linked in: hid_logitech unix_diag vhost_net tap vhost_vsock vmw_vsock_virtio_transport_common vhost vsock vhost_iotlb binfmt_misc veth nft_masq zfs(PO) zunicode(PO) zavl(PO) icp(PO) zcommon(PO) znvpair(PO) spl(O) zlua(PO) xt_CHECKSUM xt_MASQUERADE xt_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp nft_compat nft_counter nft_chain_nat nf_nat nf_conntrack
[Kernel-packages] [Bug 1905984] [NEW] Hard lockup with "watchdog: BUG: soft lockup - CPU#10 stuck for 22s! [Xorg:13615]" in the journal
Public bug reported: The system was restored from hibernation this morning, but the issue did not exhibit for ~30 minutes after "boot". I have also seen hard locks without hibernation (but they have never produced any journal output, so may be a different issue). Examining `journalctl -k`, I see something like the below repeated every few seconds. I've attached `journalctl -k`s output (truncated from unhibernate this morning). Nov 27 09:42:09 surprise kernel: watchdog: BUG: soft lockup - CPU#10 stuck for 22s! [Xorg:13615] Nov 27 09:42:09 surprise kernel: Modules linked in: hid_logitech unix_diag vhost_net tap vhost_vsock vmw_vsock_virtio_transport_common vhost vsock vhost_iotlb binfmt_misc veth nft_masq zfs(PO) zunicode(PO) zavl(PO) icp(PO) zcommon(PO) znvpair(PO) spl(O) zlua(PO) xt_CHECKSUM xt_MASQUERADE xt_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp nft_compat nft_counter nft_chain_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 nf_tables nfnetlink bridge stp llc aufs rdma_ucm ib_uverbs rdma_cm iw_cm ib_cm ib_core overlay nls_iso8859_1 snd_hda_codec_realtek snd_hda_codec_generic ledtrig_audio snd_hda_codec_hdmi snd_hda_intel snd_intel_dspcfg snd_usb_audio snd_hda_codec uvcvideo snd_hda_core snd_usbmidi_lib videobuf2_vmalloc videobuf2_memops snd_hwdep videobuf2_v4l2 snd_seq_midi videobuf2_common snd_seq_midi_event snd_rawmidi edac_mce_amd videodev snd_pcm kvm_amd snd_seq mc input_leds kvm snd_seq_device joydev snd_timer ucsi_ccg typec_ucsi snd typec soundcore ccp rapl wmi_bmof k10temp efi_pstore mac_hid nvidia_uvm(OE) Nov 27 09:42:09 surprise kernel: sch_fq_codel parport_pc ppdev lp parport ip_tables x_tables autofs4 btrfs blake2b_generic xor raid6_pq libcrc32c dm_crypt hid_logitech_hidpp hid_microsoft hid_logitech_dj ff_memless hid_generic usbhid hid nvidia_drm(POE) nvidia_modeset(POE) nvidia(POE) crct10dif_pclmul crc32_pclmul ghash_clmulni_intel drm_kms_helper aesni_intel syscopyarea sysfillrect sysimgblt fb_sys_fops crypto_simd cec cryptd glue_helper rc_core drm i2c_piix4 i2c_nvidia_gpu nvme r8169 ahci xhci_pci nvme_core realtek xhci_pci_renesas libahci wmi gpio_amdpt gpio_generic Nov 27 09:42:09 surprise kernel: CPU: 10 PID: 13615 Comm: Xorg Tainted: P OE 5.8.0-29-generic #31-Ubuntu Nov 27 09:42:09 surprise kernel: Hardware name: Gigabyte Technology Co., Ltd. B450M DS3H/B450M DS3H-CF, BIOS F4 01/25/2019 Nov 27 09:42:09 surprise kernel: RIP: 0010:_nv001550kms+0x16/0x70 [nvidia_modeset] Nov 27 09:42:09 surprise kernel: Code: 53 28 e9 0e fe ff ff 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 00 41 54 55 49 89 fc 53 48 8d 5f 38 48 89 f5 48 89 df e8 9a 48 00 00 <84> c0 75 46 49 8b 54 24 40 48 39 d3 48 8b 42 18 74 17 48 39 c5 75 Nov 27 09:42:09 surprise kernel: RSP: 0018:b479cf577910 EFLAGS: 0287 Nov 27 09:42:09 surprise kernel: RAX: c1a15800 RBX: 9c30b2233640 RCX: 001f1623 Nov 27 09:42:09 surprise kernel: RDX: 9c2fd6186ac8 RSI: 9c2d33ef4008 RDI: 9c30b2233640 Nov 27 09:42:09 surprise kernel: RBP: 9c2d33ef4008 R08: b479cf577830 R09: 0001 Nov 27 09:42:09 surprise kernel: R10: 9c2cd20fbbc0 R11: 001a R12: 9c30b2233608 Nov 27 09:42:09 surprise kernel: R13: R14: 9c2d33ef4008 R15: 0002 Nov 27 09:42:09 surprise kernel: FS: 7f82d95e4a40() GS:9c30cf08() knlGS: Nov 27 09:42:09 surprise kernel: CS: 0010 DS: ES: CR0: 80050033 Nov 27 09:42:09 surprise kernel: CR2: 55683e860ff8 CR3: 00037893c000 CR4: 003406e0 Nov 27 09:42:09 surprise kernel: Call Trace: Nov 27 09:42:09 surprise kernel: ? _nv001123kms+0xb2/0x400 [nvidia_modeset] Nov 27 09:42:09 surprise kernel: ? _nv000732kms+0x1e/0x80 [nvidia_modeset] Nov 27 09:42:09 surprise kernel: ? _nv002395kms+0x112/0x130 [nvidia_modeset] Nov 27 09:42:09 surprise kernel: ? _nv000515kms+0xd1/0xe1 [nvidia_modeset] Nov 27 09:42:09 surprise kernel: ? _nv19kms+0x230/0x6fc [nvidia_modeset] Nov 27 09:42:09 surprise kernel: ? kfree+0xb8/0x220 Nov 27 09:42:09 surprise kernel: ? os_free_mem+0x22/0x30 [nvidia] Nov 27 09:42:09 surprise kernel: ? _nv008503rm+0xbe/0x100 [nvidia] Nov 27 09:42:09 surprise kernel: ? _nv035038rm+0x2a/0x60 [nvidia] Nov 27 09:42:09 surprise kernel: ? _nv030385rm+0x23/0x40 [nvidia] Nov 27 09:42:09 surprise kernel: ? _nv033621rm+0x58/0xf0 [nvidia] Nov 27 09:42:09 surprise kernel: ? _nv008135rm+0x33c/0x3f0 [nvidia] Nov 27 09:42:09 surprise kernel: ? os_acquire_spinlock+0x12/0x30 [nvidia] Nov 27 09:42:09 surprise kernel: ? os_release_spinlock+0x1a/0x20 [nvidia] Nov 27 09:42:09 surprise kernel: ? _nv037019rm+0xa1/0x190 [nvidia] Nov 27 09:42:09 surprise kernel: ? nvidia_modeset_rm_ops_free_stack+0x1d/0x20 [nvidia] Nov 27 09:42:09 surprise kernel: ? _nv002759kms+0x12a0/0x1470 [nvidia_modeset] Nov 27 09:42:09 surprise kernel: ? mpol_rebind_preferred+0x1c0/0x1c0 Nov 27 09:42:09 surprise kernel: ? _nv000531kms+0x50/0x50
[Kernel-packages] [Bug 1905975] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1905975 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1905975 Title: kernel: Enable CONFIG_BPF_LSM on Ubuntu Status in linux package in Ubuntu: Incomplete Bug description: == Impact == Enabling CONFIG_BPF_LSM in the KConfig of Ubuntu Kernels, allowing users to use BPF LSM programs. == Background == The BPF LSM was merged into the Linux kernel 5.7 https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=641cd7b06c911c5935c34f24850ea18690649917 https://outflux.net/blog/archives/2020/09/21/security-things-in- linux-v5-7 It allows users to implement MAC and Audit Policies using BPF programs. As a follow-up from the interest generated by the LSM on BPF/Linux conferences and on request from users, we’d like to request the enabling of CONFIG_BPF_LSM on Ubuntu starting with H. The LSM won't be added to the list of active LSMs by default (in CONFIG_LSM or lsm= on the boot parameters) yet, as it adds an indirect function call overhead by registering an empty LSM hook for all hooks. However enabling it in the kernel config will support users who wish to use BPF LSM programs without needing to replace their kernel image. The LSM can be made "active" by default when our work on getting rid of this overhead is merged in the kernel: https://lore.kernel.org/bpf/20200820164753.3256899-1-jackm...@chromium.org == Regression Potential == None. The LSM is not active by default, so it does not have any performance or functional regression. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1905975/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1905978] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1905978 Title: not recognizing touchpad Status in linux package in Ubuntu: Confirmed Bug description: kernel doesn't recognize touchpad. touchpad stopped working about 1 month. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-53-generic 5.4.0-53.59 ProcVersionSignature: Ubuntu 5.4.0-53.59-generic 5.4.65 Uname: Linux 5.4.0-53-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lightlessness 5648 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: MATE Date: Fri Nov 27 09:46:09 2020 MachineType: LENOVO 80SV ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-53-generic root=UUID=5aed6b68-e7aa-4c24-8b7b-0a9fa03f9a0f ro splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-53-generic N/A linux-backports-modules-5.4.0-53-generic N/A linux-firmware1.187.4 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/17/2018 dmi.bios.vendor: LENOVO dmi.bios.version: 3JCN31WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: Torronto 5C1 dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 510-15IKB dmi.modalias: dmi:bvnLENOVO:bvr3JCN31WW:bd07/17/2018:svnLENOVO:pn80SV:pvrLenovoideapad510-15IKB:rvnLENOVO:rnTorronto5C1:rvrNODPK:cvnLENOVO:ct10:cvrLenovoideapad510-15IKB: dmi.product.family: IDEAPAD dmi.product.name: 80SV dmi.product.sku: LENOVO_MT_80SV_BU_idea_FM_ dmi.product.version: Lenovo ideapad 510-15IKB dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1905978/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1873439] Re: Logitech BRIO webcam fails with "xhci_hcd 0000:02:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 2 comp_code 13"
This bug seems to be related to the ASMedia USB3.1 host controller. I'm also experiencing this issue when my webcam is connected to my ASM1142 host controller. (Also under Windows it works quite flaky btw.) When connected to my Intel USB3.0 host controller, I have no issues. @John: if you have external USB ports which are connected to your AMD USB3.0 host controller you can use these as a workaround. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1873439 Title: Logitech BRIO webcam fails with "xhci_hcd :02:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 2 comp_code 13" Status in linux package in Ubuntu: Confirmed Bug description: [ 450.844431] xhci_hcd :02:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 2 comp_code 13 [ 450.844439] xhci_hcd :02:00.0: Looking for event-dma fd473230 trb-start fd473210 trb-end fd473210 seg-start fd473000 seg-end fd473ff0 The above occurs while trying to use Cheese to access the Logitech BRIO webcam (USB device 046d:085e). Ultimately the webcam doesn't work with Cheese. When it produces any image at all, it is full of vertical bars and is in greyscale. Meanwhile dmesg shows hundreds of the above kernel messages. After getting out of Cheese, I unplugged and replugged the webcam. This produced: Apr 17 03:58:30 shh kernel: [ 1218.202407] usb 2-8: reset SuperSpeed Gen 1 USB device number 2 using xhci_hcd Apr 17 03:58:35 shh kernel: [ 1223.341073] usb 2-8: device descriptor read/8, error -110 then a new series when plugged in: Apr 17 03:59:13 shh kernel: [ 1261.369494] usb 2-8: new SuperSpeed Gen 1 USB device number 4 using xhci_hcd Apr 17 03:59:18 shh kernel: [ 1266.604852] usb 2-8: device descriptor read/8, error -110 which repeated a few times, interspersed with: Apr 17 03:59:34 shh kernel: [ 1282.848732] usb usb2-port8: attempt power cycle Apr 17 03:59:35 shh kernel: [ 1283.361363] usb 2-8: new SuperSpeed Gen 1 USB device number 6 using xhci_hcd Apr 17 03:59:40 shh kernel: [ 1288.621098] usb 2-8: device descriptor read/8, error -110 Apr 17 03:59:40 shh kernel: [ 1288.728918] usb 2-8: new SuperSpeed Gen 1 USB device number 6 using xhci_hcd Apr 17 03:59:46 shh kernel: [ 1293.996668] usb 2-8: device descriptor read/8, error -110 and ultimately: Apr 17 03:59:56 shh kernel: [ 1304.864636] usb usb2-port8: unable to enumerate USB device This dustup with the webcam also seems to screw up the USB interface to a nearby disk drive on a completely different USB port on the motherboard. The problem persists until the kernel is rebooted. Power cycling the webcam (it has no battery, so pulling the USB cord, waiting ten seconds, and replugging it suffices) does not fix the "error -110" issue, so the webcam can never be accessed again until the kernel is rebooted. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-24-generic 5.4.0-24.28 ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30 Uname: Linux 5.4.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-id', '/dev/snd/controlC2', '/dev/snd/pcmC2D0c', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/by-path', '/dev/snd/controlC1', '/dev/snd/hwC1D1', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D4c', '/dev/snd/pcmC1D4p', '/dev/snd/pcmC1D2c', '/dev/snd/pcmC1D1p', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Apr 17 03:54:10 2020 InstallationDate: Installed on 2020-04-17 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) IwConfig: enp5s0no wireless extensions. enp6s0no wireless extensions. lono wireless extensions. MachineType: Gigabyte Technology Co., Ltd. AX370-Gaming 5 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 nouveaudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-24-generic root=UUID=35b84e12-683c-43ea-9b3f-64fae90e1984 ro quiet splash 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.4.0-24-generic N/A linux-backports-modules-5.4.0-24-generic N/A linux-firmware1.187 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/16/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F25 dmi.board.asset.tag: Default
[Kernel-packages] [Bug 1905978] [NEW] not recognizing touchpad
Public bug reported: kernel doesn't recognize touchpad. touchpad stopped working about 1 month. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-53-generic 5.4.0-53.59 ProcVersionSignature: Ubuntu 5.4.0-53.59-generic 5.4.65 Uname: Linux 5.4.0-53-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lightlessness 5648 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: MATE Date: Fri Nov 27 09:46:09 2020 MachineType: LENOVO 80SV ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-53-generic root=UUID=5aed6b68-e7aa-4c24-8b7b-0a9fa03f9a0f ro splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-53-generic N/A linux-backports-modules-5.4.0-53-generic N/A linux-firmware1.187.4 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/17/2018 dmi.bios.vendor: LENOVO dmi.bios.version: 3JCN31WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: Torronto 5C1 dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 510-15IKB dmi.modalias: dmi:bvnLENOVO:bvr3JCN31WW:bd07/17/2018:svnLENOVO:pn80SV:pvrLenovoideapad510-15IKB:rvnLENOVO:rnTorronto5C1:rvrNODPK:cvnLENOVO:ct10:cvrLenovoideapad510-15IKB: dmi.product.family: IDEAPAD dmi.product.name: 80SV dmi.product.sku: LENOVO_MT_80SV_BU_idea_FM_ dmi.product.version: Lenovo ideapad 510-15IKB dmi.sys.vendor: LENOVO ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1905978 Title: not recognizing touchpad Status in linux package in Ubuntu: New Bug description: kernel doesn't recognize touchpad. touchpad stopped working about 1 month. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-53-generic 5.4.0-53.59 ProcVersionSignature: Ubuntu 5.4.0-53.59-generic 5.4.65 Uname: Linux 5.4.0-53-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lightlessness 5648 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: MATE Date: Fri Nov 27 09:46:09 2020 MachineType: LENOVO 80SV ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-53-generic root=UUID=5aed6b68-e7aa-4c24-8b7b-0a9fa03f9a0f ro splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-53-generic N/A linux-backports-modules-5.4.0-53-generic N/A linux-firmware1.187.4 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/17/2018 dmi.bios.vendor: LENOVO dmi.bios.version: 3JCN31WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: Torronto 5C1 dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 510-15IKB dmi.modalias: dmi:bvnLENOVO:bvr3JCN31WW:bd07/17/2018:svnLENOVO:pn80SV:pvrLenovoideapad510-15IKB:rvnLENOVO:rnTorronto5C1:rvrNODPK:cvnLENOVO:ct10:cvrLenovoideapad510-15IKB: dmi.product.family: IDEAPAD dmi.product.name: 80SV dmi.product.sku: LENOVO_MT_80SV_BU_idea_FM_ dmi.product.version: Lenovo ideapad 510-15IKB dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1905978/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1880426] Re: Intel Wireless-AC 8260 [8086:24f3] Subsystem [8086:1010] - iwlwifi Microcode SW error detected
I do not get any of these Microcode SW error detected errors with backport-iwlwifi-dkms and the wifi is stable. That being said, I did not encounter any more wifi breakdowns recently. Since they were sporadic to begin with, I cannot say for certain when they stopped happening, but with the current kernel (4.15.0-124-generic) my network connection is pretty stable - even though I still kept getting these "Microcode SW error" messages consistently every once in a while. With the backport iwlwifi driver there is no such Microcode SW error messages. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1880426 Title: Intel Wireless-AC 8260 [8086:24f3] Subsystem [8086:1010] - iwlwifi Microcode SW error detected Status in linux package in Ubuntu: Incomplete Bug description: Ever since the previous to last apt-get upgrade, my wifi has become very unstable. After a few minutes to every few hours, the WIFI connection becomes completely unresponsive with any further packets timing out, and any attempt to (re-)connect to any AP being impossible. Wifi can only be recovered by turning wifi completely off in the menu and back on, or by a system reboot. System cold reboot after upgrade did not help. As far as I can recall the bug first appeared with linux-modules-extra-4.15.0-99-generic, but was not present prior to that. The bug is currently present on the system after apt upgrade to linux- modules-extra-4.15.0-101-generic. dmesg|grep iwlwifi: [ 14.623738] iwlwifi :02:00.0: loaded firmware version 34.0.1 op_mode iwlmvm [ 14.662856] iwlwifi :02:00.0: Detected Intel(R) Dual Band Wireless AC 8260, REV=0x208 [ 14.754145] iwlwifi :02:00.0: base HW address: 28:16:ad:9b:7e:27 [ 14.937064] iwlwifi :02:00.0 wlp2s0: renamed from wlan0 [18635.796270] iwlwifi :02:00.0: Microcode SW error detected. Restarting 0x200. [18635.796433] iwlwifi :02:00.0: Start IWL Error Log Dump: [18635.796444] iwlwifi :02:00.0: Status: 0x0100, count: 6 [18635.796452] iwlwifi :02:00.0: Loaded firmware version: 34.0.1 [18635.796462] iwlwifi :02:00.0: 0x0071 | ADVANCED_SYSASSERT [18635.796470] iwlwifi :02:00.0: 0x0230 | trm_hw_status0 [18635.796478] iwlwifi :02:00.0: 0x | trm_hw_status1 [18635.796486] iwlwifi :02:00.0: 0x0002395C | branchlink2 [18635.796493] iwlwifi :02:00.0: 0x0003867A | interruptlink1 [18635.796500] iwlwifi :02:00.0: 0x0003867A | interruptlink2 [18635.796507] iwlwifi :02:00.0: 0x | data1 [18635.796515] iwlwifi :02:00.0: 0x1000 | data2 [18635.796522] iwlwifi :02:00.0: 0x0783 | data3 [18635.796530] iwlwifi :02:00.0: 0x73C18DA9 | beacon time [18635.796537] iwlwifi :02:00.0: 0x4816439E | tsf low [18635.796545] iwlwifi :02:00.0: 0x014C | tsf hi [18635.796552] iwlwifi :02:00.0: 0x | time gp1 [18635.796559] iwlwifi :02:00.0: 0x55BF8308 | time gp2 [18635.796567] iwlwifi :02:00.0: 0x0001 | uCode revision type [18635.796574] iwlwifi :02:00.0: 0x0022 | uCode version major [18635.796582] iwlwifi :02:00.0: 0x | uCode version minor [18635.796589] iwlwifi :02:00.0: 0x0201 | hw version [18635.796596] iwlwifi :02:00.0: 0x00C89008 | board version [18635.796604] iwlwifi :02:00.0: 0x001C | hcmd [18635.796611] iwlwifi :02:00.0: 0x24022000 | isr0 [18635.796618] iwlwifi :02:00.0: 0x0180 | isr1 [18635.796625] iwlwifi :02:00.0: 0x08001802 | isr2 [18635.796632] iwlwifi :02:00.0: 0x004178C1 | isr3 [18635.796640] iwlwifi :02:00.0: 0x0001 | isr4 [18635.796647] iwlwifi :02:00.0: 0x005F019C | last cmd Id [18635.796654] iwlwifi :02:00.0: 0x | wait_event [18635.796662] iwlwifi :02:00.0: 0x0080 | l2p_control [18635.796669] iwlwifi :02:00.0: 0x00010030 | l2p_duration [18635.796676] iwlwifi :02:00.0: 0x003F | l2p_mhvalid [18635.796683] iwlwifi :02:00.0: 0x00CE | l2p_addr_match [18635.796691] iwlwifi :02:00.0: 0x000D | lmpm_pmg_sel [18635.796698] iwlwifi :02:00.0: 0x30101341 | timestamp [18635.796706] iwlwifi :02:00.0: 0x00340818 | flow_handler [18635.796901] iwlwifi :02:00.0: Start IWL Error Log Dump: [18635.796909] iwlwifi :02:00.0: Status: 0x0100, count: 7 [18635.796917] iwlwifi :02:00.0: 0x00100116 | ADVANCED_SYSASSERT [18635.796924] iwlwifi :02:00.0: 0x | umac branchlink1 [18635.796932] iwlwifi :02:00.0: 0xC0086A78 | umac branchlink2 [18635.796940] iwlwifi :02:00.0: 0xC0083C90 | umac interruptlink1 [18635.796947] iwlwifi :02:00.0: 0x | umac interruptlink2 [18635.796954] iwlwifi :02:00.0: 0xDEADBEEF | umac data1 [18635.796961] iwlwifi :02:00.0: 0xDEADBEEF | umac data2
[Kernel-packages] [Bug 1902895] Re: WiFi loses connection on an irregular basis probably due to buffer overflow
Looks like with ath10k_pci FW ver. WLAN.RM.4.4.1-00157-QCARMSWPZ-1 the issue is gone or at least delayed that much, that it makes it irreproducible for me. The faulty one wasWLAN.RM.4.4.1-00140-QCARMSWPZ-1. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1902895 Title: WiFi loses connection on an irregular basis probably due to buffer overflow Status in linux package in Ubuntu: Incomplete Bug description: Dell XPS13, Ubuntu 20.10, kernel 5.8. I cannot pinpoint the exact scenario, but it happens most often when trying to build Xorg-master from source via their build.sh script. Setup: WiFi connected, xorg is built in terminal window. Speculatively I would say it say realted to trasferring large number of small files, but I don't have any hard evidence to prove that. To depict it better: A Main terminal (and let it run): $ ./util/modular/build.sh --clone $HOME/build B Second terminal (and let it run): $ ping www.onet.pl #any host should do, just using popular news site as an example C Third terminal (optionally) # dmesg -w At some point of build.sh cloning, the other terminal (B) starts to display this: 64 bytes from sg1.any.onet.pl (213.180.141.140): icmp_seq=151 ttl=58 time=20.2 ms #that's ok ping: sendmsg: No buffer space available ping: sendmsg: No buffer space available ping: sendmsg: No buffer space available It usually happens when A is in the middle of git clone, which just hangs there. Nothing displayed by dmesg. All other network activity stalls (but not fails). Waiting ca. 5 minutes does not help. WiFi icon indicates everything's fine. Restarting WiFi (either using the icon or with rfkill, ifconfig should probably work too) restores connectivity, but breaks all the stalled activity, e.g. scripts, git etc. Increasing /proc/sys/net/core/wmem_max delays the problem and allows one or two clones to complete in the given example. I have observed that on 18.04, 20.04 and 20.10, with the default kernels i.e. 5.4 and 5.8. Scenario in each case is exactly the same. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-5.8.0-25-generic 5.8.0-25.26 ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14 Uname: Linux 5.8.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dladmin1368 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Nov 4 15:51:00 2020 InstallationDate: Installed on 2020-10-26 (9 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0c45:670c Microdia Integrated Webcam HD Bus 001 Device 003: ID 04f3:2234 Elan Microelectronics Corp. Touchscreen Bus 001 Device 002: ID 0cf3:e300 Qualcomm Atheros Communications QCA61x4 Bluetooth 4.0 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 13 9360 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-25-generic root=UUID=746d5f05-e21a-42c5-9191-a65c526a3305 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.8.0-25-generic N/A linux-backports-modules-5.8.0-25-generic N/A linux-firmware1.190 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/14/2019 dmi.bios.release: 2.13 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.13.0 dmi.board.name: 0839Y6 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.13.0:bd11/14/2019:br2.13:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn0839Y6:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9360 dmi.product.sku: 075B dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1902895/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1901392] Re: updated system after long time and it failed installing libnvidia-common-450
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: nvidia-graphics-drivers-450 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-450 in Ubuntu. https://bugs.launchpad.net/bugs/1901392 Title: updated system after long time and it failed installing libnvidia- common-450 Status in nvidia-graphics-drivers-450 package in Ubuntu: Confirmed Bug description: For about 2 months or more I was not using the laptop, so the updates were neither being installed for that time. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: libnvidia-common-450 450.66-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 Uname: Linux 5.4.0-48-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.10 Architecture: amd64 CasperMD5CheckResult: skip Date: Sun Oct 25 10:51:41 2020 Dependencies: DuplicateSignature: package:libnvidia-common-450:450.66-0ubuntu0.20.04.1 Unpacking libnvidia-common-450 (450.80.02-0ubuntu0.20.04.2) over (450.66-0ubuntu0.20.04.1) ... dpkg: error processing archive /tmp/apt-dpkg-install-dY2p3p/44-libnvidia-common-450_450.80.02-0ubuntu0.20.04.2_all.deb (--unpack): trying to overwrite '/usr/share/nvidia/nvidia-application-profiles-450.80.02-key-documentation', which is also in package libnvidia-common-450-server 450.80.02-0ubuntu0.20.04.3 ErrorMessage: trying to overwrite '/usr/share/nvidia/nvidia-application-profiles-450.80.02-key-documentation', which is also in package libnvidia-common-450-server 450.80.02-0ubuntu0.20.04.3 InstallationDate: Installed on 2020-01-29 (269 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) PackageArchitecture: all 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: nvidia-graphics-drivers-450 Title: package libnvidia-common-450 450.66-0ubuntu0.20.04.1 failed to install/upgrade: trying to overwrite '/usr/share/nvidia/nvidia-application-profiles-450.80.02-key-documentation', which is also in package libnvidia-common-450-server 450.80.02-0ubuntu0.20.04.3 UpgradeStatus: Upgraded to focal on 2020-05-10 (167 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-450/+bug/1901392/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1905975] [NEW] kernel: Enable CONFIG_BPF_LSM on Ubuntu
Public bug reported: == Impact == Enabling CONFIG_BPF_LSM in the KConfig of Ubuntu Kernels, allowing users to use BPF LSM programs. == Background == The BPF LSM was merged into the Linux kernel 5.7 https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=641cd7b06c911c5935c34f24850ea18690649917 https://outflux.net/blog/archives/2020/09/21/security-things-in- linux-v5-7 It allows users to implement MAC and Audit Policies using BPF programs. As a follow-up from the interest generated by the LSM on BPF/Linux conferences and on request from users, we’d like to request the enabling of CONFIG_BPF_LSM on Ubuntu starting with H. The LSM won't be added to the list of active LSMs by default (in CONFIG_LSM or lsm= on the boot parameters) yet, as it adds an indirect function call overhead by registering an empty LSM hook for all hooks. However enabling it in the kernel config will support users who wish to use BPF LSM programs without needing to replace their kernel image. The LSM can be made "active" by default when our work on getting rid of this overhead is merged in the kernel: https://lore.kernel.org/bpf/20200820164753.3256899-1-jackm...@chromium.org == Regression Potential == None. The LSM is not active by default, so it does not have any performance or functional regression. ** 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/1905975 Title: kernel: Enable CONFIG_BPF_LSM on Ubuntu Status in linux package in Ubuntu: New Bug description: == Impact == Enabling CONFIG_BPF_LSM in the KConfig of Ubuntu Kernels, allowing users to use BPF LSM programs. == Background == The BPF LSM was merged into the Linux kernel 5.7 https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=641cd7b06c911c5935c34f24850ea18690649917 https://outflux.net/blog/archives/2020/09/21/security-things-in- linux-v5-7 It allows users to implement MAC and Audit Policies using BPF programs. As a follow-up from the interest generated by the LSM on BPF/Linux conferences and on request from users, we’d like to request the enabling of CONFIG_BPF_LSM on Ubuntu starting with H. The LSM won't be added to the list of active LSMs by default (in CONFIG_LSM or lsm= on the boot parameters) yet, as it adds an indirect function call overhead by registering an empty LSM hook for all hooks. However enabling it in the kernel config will support users who wish to use BPF LSM programs without needing to replace their kernel image. The LSM can be made "active" by default when our work on getting rid of this overhead is merged in the kernel: https://lore.kernel.org/bpf/20200820164753.3256899-1-jackm...@chromium.org == Regression Potential == None. The LSM is not active by default, so it does not have any performance or functional regression. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1905975/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1900809] Re: [SRU]sof-firmware: update the sof-firmware from version v1.4.2 to stable-v1.6
Hello Hui, or anyone else affected, Accepted linux-firmware into groovy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/linux- firmware/1.190.2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- groovy to verification-done-groovy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-groovy. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: linux-firmware (Ubuntu Groovy) Status: Triaged => Fix Committed -- 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/1900809 Title: [SRU]sof-firmware: update the sof-firmware from version v1.4.2 to stable-v1.6 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 Groovy: Fix Committed Status in linux-firmware source package in Hirsute: Fix Released Bug description: BugLink: https://bugs.launchpad.net/bugs/1900809 [Impact] Intel released the sof-firmware v1.6, and in our oem projects, the Dell TGL machines and the machines with soundwire audio need the new firmware, otherwise they will fail to load the firmware or the audio can't work well. [Fix] replace the old sof-firmware-v1.4.2 with sof-firmware-v1.6 [Test] Tested on the Dell cml/tgl soundwire machines, all audio functions worked well, and those audio functions didn't work with old firmware. Tested on Lenovo dimc machines, all audio functions worked as well as before. [Regression Potential] Intel tested the new firmware with the 5.8 and 5.9 kernel, but we need the new firmware to work with 5.4 and 5.6 kernel as well, so there is some possibility that the 5.4/5.6 kernel can't work well with the new sof-firmware. I have tested the new firmware with 5.4/5.6 kernel on some Lenovo machines, so far no issues were found. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1900809/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1905214] Re: linux-firmware: intel AX200 (8087:0029) and AX201(8087:0026) bluetooth firmware update
Hello Hui, or anyone else affected, Accepted linux-firmware into groovy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/linux- firmware/1.190.2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- groovy to verification-done-groovy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-groovy. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: linux-firmware (Ubuntu Groovy) Status: In Progress => Fix Committed -- 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/1905214 Title: linux-firmware: intel AX200 (8087:0029) and AX201(8087:0026) bluetooth firmware update 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 Groovy: Fix Committed Status in linux-firmware source package in Hirsute: Fix Released Bug description: For H, it already has all patches, this SRU is not needed for H For G, only needs the 0005-xxx.patch and 0010-xxx.patch For F, needs all patches. [Impact] We found 2 issues: Bluetooth headset can't work in hsp/hfp mode, Both AX200 and AX201 have this issue (#1871794) Bluetooth will stop working randomly on the machines with AX200 (OEM bug). [Fix] Update the firmware to the latest version, the above 2 issues could be fixed. [Test] connect a bluetooth headset, after connecting, it is in A2DP mode by default, change it to hsp/hfp mode from gnome-sound-setting, play sound and record sound from headset, all work well. Keep the machine powered on and let it be idle for 1 day, check the bluetooth headset, still could work. [Regression Potential] I could make the Bluetooth function stop working on the machines with AX200 or AX201 module, like can't scan the BT devices, can't connect the BT devices or the BT devices can't work normally. But this possibility is very low, we have tested the SRU on a couple of lenovo machines, all worked well. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1905214/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1904595] Re: Fix no headset sound after S3 on Intel HDA
** Changed in: linux (Ubuntu Groovy) Status: Confirmed => Fix Committed -- 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/1904595 Title: Fix no headset sound after S3 on Intel HDA Status in HWE Next: New 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: Won't Fix Status in linux-oem-5.6 source package in Focal: Confirmed Status in linux source package in Groovy: Fix Committed Status in linux-oem-5.6 source package in Groovy: Invalid Bug description: [Impact] After system S3, hotplugging headset cannot produce any sound despite of being auto-selected as audio output. [Fix] Avoid using pm_runtime_force_{suspend,resume} helpers to ensure codec suspend/resume flow, and also ensure HDA driver and PCI set correct wakeup settings. [Test case] Plug headset, unplug headset, switch audio ouput from speakers to HDMI to let Intel HDA auto suspend. Suspend/resume the system, plug the headset again, hear no sound. With the patch series applied, the issue is gone. [Where problems could occur] If there is bad firmware/hardware that makes codec have system-wide wakeup capability, direct-complete flow may trigger unwanted system wakeup or even break system suspend. The series was tested on both AMD and Intel platforms, with Realtek and Connexant codecs respectively. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1904595/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1904221] Re: Ask 8821C Bluetooth controller to drop old firmware
** Changed in: linux (Ubuntu Groovy) Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1904221 Title: Ask 8821C Bluetooth controller to drop old firmware Status in linux package in Ubuntu: Confirmed Status in linux-oem-5.6 package in Ubuntu: Invalid Status in linux source package in Focal: Fix Committed Status in linux-oem-5.6 source package in Focal: Confirmed Status in linux source package in Groovy: Fix Committed Status in linux-oem-5.6 source package in Groovy: Invalid Bug description: [Impact] Some platforms may keep USB power in S3/S4/S5, so Realtek 8821C retains its firmware even with a cold boot. [Fix] Use vendor command to drop firmware if the version is old. [Test case] Use dmesg to check if new firmware is loaded. With the patch applied, we can find new firmware is loaded. [Where problems could occur] There's a 200ms delay which can slow down when BT controller is opened by userspace first time. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1904221/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1904225] Re: Use ACPI S5 for reboot
** Changed in: linux (Ubuntu Groovy) Status: Confirmed => Fix Committed -- 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/1904225 Title: Use ACPI S5 for reboot Status in HWE Next: New Status in OEM Priority Project: New Status in linux package in Ubuntu: Confirmed Status in linux-oem-5.6 package in Ubuntu: Invalid Status in linux source package in Focal: Fix Committed Status in linux-oem-5.6 source package in Focal: Confirmed Status in linux source package in Groovy: Fix Committed Status in linux-oem-5.6 source package in Groovy: Invalid Bug description: [Impact] On some HP laptops, BIOS hotkeys don't work right after reboot, becuase OS doesn't call _PTS to indicate ACPI it's rebooting. [Fix] Follow Windows and use S5 for reboot. [Test case] Reboot and see if hotkeys like F10/F11 can trigger BIOS functions. Hotkeys work great with the patch applied. [Where problems could occur] If there are platforms don't expect S5 for reboot then there could be unexpected result. However Windows uses S5 so that's rather unlikely. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1904225/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1896091] Re: [i915] Noise-like lines of graphics corruption when moving windows in Xorg sessions
** Changed in: linux (Ubuntu Groovy) Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1896091 Title: [i915] Noise-like lines of graphics corruption when moving windows in Xorg sessions Status in linux package in Ubuntu: Triaged Status in linux source package in Groovy: Fix Committed Bug description: == SRU Justification == [Impact] Noise-like lines of graphics corruption when moving windows in Xorg sessions. [Fix] Revert "UBUNTU: SAUCE: drm/i915: Synchronize active and retire callbacks". [Test] Daniel van Vugt confirmed reverting the commit fixes the issue. I can also reproduce the issue on one of my system, I can confirm it fixes the issue too. [Where problems could occur] Race condition the commit solves may appear again. The commit was reverted and replaced by an upstream fix, which is already included in 5.8. So it should be rather safe here. == Original Bug Report == I left my desktop (T480s thinkpad docked to ThinkVision P24h-10) unattended for a while, and then got the error message and now have funny lines on activity, e.g. red lines flashing on top of gnome-shell bar when switching windows, or white blocks/lines around typing text. This is the second or third time it happened, reboot fixes it until the error pops up again. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-5.8.0-19-generic 5.8.0-19.20 ProcVersionSignature: Ubuntu 5.8.0-19.20-generic 5.8.8 Uname: Linux 5.8.0-19-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu45 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: jak5052 F pulseaudio /dev/snd/controlC1: jak5052 F pulseaudio /dev/snd/pcmC1D0p: jak5052 F...m pulseaudio /dev/snd/controlC0: jak5052 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: GNOME CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read kernel buffer failed: Operation not permitted Date: Thu Sep 17 19:14:11 2020 HibernationDevice: RESUME=none InstallationDate: Installed on 2018-03-14 (917 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180313) MachineType: LENOVO 20L8S02D00 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-19-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.8.0-19-generic N/A linux-backports-modules-5.8.0-19-generic N/A linux-firmware1.190 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/04/2020 dmi.bios.release: 1.42 dmi.bios.vendor: LENOVO dmi.bios.version: N22ET65W (1.42 ) dmi.board.asset.tag: Not Available dmi.board.name: 20L8S02D00 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.20 dmi.modalias: dmi:bvnLENOVO:bvrN22ET65W(1.42):bd06/04/2020:br1.42:efr1.20:svnLENOVO:pn20L8S02D00:pvrThinkPadT480s:rvnLENOVO:rn20L8S02D00:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T480s dmi.product.name: 20L8S02D00 dmi.product.sku: LENOVO_MT_20L8_BU_Think_FM_ThinkPad T480s dmi.product.version: ThinkPad T480s dmi.sys.vendor: LENOVO --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu45 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: jak5052 F pulseaudio /dev/snd/controlC1: jak5052 F pulseaudio /dev/snd/pcmC1D0p: jak5052 F...m pulseaudio /dev/snd/controlC0: jak5052 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: GNOME CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read kernel buffer failed: Operation not permitted DistroRelease: Ubuntu 20.10 HibernationDevice: RESUME=none InstallationDate: Installed on 2018-03-14 (917 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180313) MachineType: LENOVO 20L8S02D00 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-19-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-19.20-generic 5.8.8 RelatedPackageVersions: linux-restricted-modules-5.8.0-19-generic N/A linux-backports-modules-5.8.0-19-generic N/A linux-firmware1.190 Tags: groovy Uname: Linux 5.8.0-19-generic x86_64 UpgradeStatus: No upgrade log present
[Kernel-packages] [Bug 1904521] Re: Intel Tiger Lake IDs supplement
** Changed in: linux (Ubuntu Groovy) Status: In Progress => Fix Committed -- 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/1904521 Title: Intel Tiger Lake IDs supplement Status in HWE Next: New Status in linux package in Ubuntu: Invalid Status in linux-oem-5.6 package in Ubuntu: Invalid Status in linux-oem-5.6 source package in Focal: In Progress Status in linux source package in Groovy: Fix Committed Bug description: [Impact] Intel Tiger Lake-H platform requires new pin settings and IDs to enable. [Fix] Intel provides us a list of TGL-H commits from 5.8 and 5.9, we need all of the commits to enable TGL-H platforms completely. [Test] Verified those commits on Intel TGL-H SDP [Regression potential] Low, all of those commits are adding new IDs for TGL-H platform. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1904521/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1904941] Re: Groovy update: v5.8.18 upstream stable release
** Changed in: linux (Ubuntu Groovy) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1904941 Title: Groovy update: v5.8.18 upstream stable release Status in linux package in Ubuntu: Confirmed Status in linux source package in Groovy: Fix Committed 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.8.18 upstream stable release from git://git.kernel.org/ netfilter: nftables_offload: KASAN slab-out-of-bounds Read in nft_flow_rule_create io_uring: don't run task work on an exiting task io_uring: allow timeout/poll/files killing to take task into account io_uring: move dropping of files into separate helper io_uring: stash ctx task reference for SQPOLL io_uring: unconditionally grab req->task io_uring: return cancelation status from poll/timeout/files handlers io_uring: enable task/files specific overflow flushing io_uring: don't rely on weak ->files references io_uring: reference ->nsproxy for file table commands io_wq: Make io_wqe::lock a raw_spinlock_t io-wq: fix use-after-free in io_wq_worker_running io_uring: no need to call xa_destroy() on empty xarray io_uring: Fix use of XArray in __io_uring_files_cancel io_uring: Fix XArray usage in io_uring_add_task_file io_uring: Convert advanced XArray uses to the normal API scripts/setlocalversion: make git describe output more reliable efi/arm64: libstub: Deal gracefully with EFI_RNG_PROTOCOL failure fs/kernel_read_file: Remove FIRMWARE_EFI_EMBEDDED enum arm64: Run ARCH_WORKAROUND_1 enabling code on all CPUs arm64: Run ARCH_WORKAROUND_2 enabling code on all CPUs arm64: link with -z norelro regardless of CONFIG_RELOCATABLE x86/PCI: Fix intel_mid_pci.c build error when ACPI is not enabled x86, powerpc: Rename memcpy_mcsafe() to copy_mc_to_{user, kernel}() UBUNTU: [Config] update config for ARCH_HAS_COPY_MC x86/copy_mc: Introduce copy_mc_enhanced_fast_string() bnxt_en: Check abort error state in bnxt_open_nic(). bnxt_en: Fix regression in workqueue cleanup logic in bnxt_remove_one(). bnxt_en: Invoke cancel_delayed_work_sync() for PFs also. bnxt_en: Re-write PCI BARs after PCI fatal error. bnxt_en: Send HWRM_FUNC_RESET fw command unconditionally. chelsio/chtls: fix deadlock issue chelsio/chtls: fix memory leaks in CPL handlers chelsio/chtls: fix tls record info to user cxgb4: set up filter action after rewrites gtp: fix an use-before-init in gtp_newlink() ibmveth: Fix use of ibmveth in a bridge. ibmvnic: fix ibmvnic_set_mac mlxsw: core: Fix memory leak on module removal netem: fix zero division in tabledist net: hns3: Clear the CMDQ registers before unmapping BAR region net: ipa: command payloads already mapped net/sched: act_mpls: Add softdep on mpls_gso.ko r8169: fix issue with forced threading in combination with shared interrupts ravb: Fix bit fields checking in ravb_hwtstamp_get() tcp: Prevent low rmem stalls with SO_RCVLOWAT. tipc: fix memory leak caused by tipc_buf_append() net: protect tcf_block_unbind with block lock erofs: avoid duplicated permission check for "trusted." xattrs arch/x86/amd/ibs: Fix re-arming IBS Fetch x86/traps: Fix #DE Oops message regression x86/xen: disable Firmware First mode for correctable memory errors PCI: aardvark: Fix initialization with old Marvell's Arm Trusted Firmware ata: ahci: mvebu: Make SATA PHY optional for Armada 3720 fuse: fix page dereference after free bpf: Fix comment for helper bpf_current_task_under_cgroup() evm: Check size of security.evm before using it p54: avoid accessing the data mapped to streaming DMA cxl: Rework error message for incompatible slots RDMA/addr: Fix race with netevent_callback()/rdma_addr_cancel() mtd: lpddr: Fix bad logic in print_drs_error drm/i915/gem: Serialise debugfs i915_gem_objects with ctx->mutex serial: qcom_geni_serial: To correct QUP Version detection logic serial: pl011: Fix lockdep splat when handling magic-sysrq interrupt PM: runtime: Fix timer_expires data type on 32-bit arches ata: sata_rcar: Fix DMA boundary mask xen/gntdev.c: Mark pages as dirty openrisc: Fix issue with get_user for 64-bit values misc: rtsx: do not setting OC_POWER_DOWN reg in rtsx_pci_init_ocp() phy: marvell: comphy: Convert internal SMCC firmware return codes to errno Linux 5.8.18 UBUNTU: upstream stable to v5.8.18 To manage notifications about this bug go to:
[Kernel-packages] [Bug 1898786] Re: bcache: Issues with large IO wait in bch_mca_scan() when shrinker is enabled
Hello Matthew, sorry for the lack of response. I'll check with Launchpad people if we can justify a reboot of the server soon and will keep you posted ! Regards, -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1898786 Title: bcache: Issues with large IO wait in bch_mca_scan() when shrinker is enabled Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Committed Status in linux source package in Focal: Fix Committed Bug description: BugLink: https://bugs.launchpad.net/bugs/1898786 [Impact] Systems that utilise bcache can experience extremely high IO wait times when under constant IO pressure. The IO wait times seem to stay at a consistent 1 second, and never drop as long as the bcache shrinker is enabled. If you disable the shrinker, then IO wait drops significantly to normal levels. We did some perf analysis, and it seems we spend a huge amount of time in bch_mca_scan(), likely waiting for the mutex ">bucket_lock". Looking at the recent commits in Bionic, we found the following commit merged in upstream 5.1-rc1 and backported to 4.15.0-87-generic through upstream stable: commit 9fcc34b1a6dd4b8e5337e2b6ef45e428897eca6b Author: Coly Li Date: Wed Nov 13 16:03:24 2019 +0800 Subject: bcache: at least try to shrink 1 node in bch_mca_scan() Link: https://github.com/torvalds/linux/commit/9fcc34b1a6dd4b8e5337e2b6ef45e428897eca6b It mentions in the description that: > If sc->nr_to_scan is smaller than c->btree_pages, after the above > calculation, variable 'nr' will be 0 and nothing will be shrunk. It is > frequeently observed that only 1 or 2 is set to sc->nr_to_scan and make > nr to be zero. Then bch_mca_scan() will do nothing more then acquiring > and releasing mutex c->bucket_lock. This seems to be what is going on here, but the above commit only addresses when nr is 0. From what I can see, the problems we are experiencing are when nr is 1 or 2, and again, we just waste time in bch_mca_scan() waiting on c->bucket_lock, only to release c->bucket_lock since the shrinker loop never executes since there is no work to do. [Fix] The following commits fix the problem, and all landed in 5.6-rc1: commit 125d98edd11464c8e0ec9eaaba7d682d0f832686 Author: Coly Li Date: Fri Jan 24 01:01:40 2020 +0800 Subject: bcache: remove member accessed from struct btree Link: https://github.com/torvalds/linux/commit/125d98edd11464c8e0ec9eaaba7d682d0f832686 commit d5c9c470b01177e4d90cdbf178b8c7f37f5b8795 Author: Coly Li Date: Fri Jan 24 01:01:41 2020 +0800 Subject: bcache: reap c->btree_cache_freeable from the tail in bch_mca_scan() Link: https://github.com/torvalds/linux/commit/d5c9c470b01177e4d90cdbf178b8c7f37f5b8795 commit e3de04469a49ee09c89e80bf821508df458ccee6 Author: Coly Li Date: Fri Jan 24 01:01:42 2020 +0800 Subject: bcache: reap from tail of c->btree_cache in bch_mca_scan() Link: https://github.com/torvalds/linux/commit/e3de04469a49ee09c89e80bf821508df458ccee6 The first commit is a dependency of the other two. The first commit removes a "recently accessed" marker, used to indicate if a particular cache has been used recently, and if it has been, not consider it for cache eviction. The commit mentions that under heavy IO, all caches will end up being recently accessed, and nothing will ever be shrunk. The second commit changes a previous design decision of skipping the first 3 caches to shrink, since it is a common case to call bch_mca_scan() with nr being 1, or 2, just like 0 was common in the very first commit I mentioned. This time, if we land on 1 or 2, the loop exits and nothing happens, and we waste time waiting on locks, just like the very first commit I mentioned. The fix is to try shrink caches from the tail of the list, and not the beginning. The third commit fixes a minor issue where we don't want to re-arrange the linked list c->btree_cache, which is what the second commit ended up doing, and instead, just shrink the cache at the end of the linked list, and not change the order. One minor backport / context adjustment was required in the first commit for Bionic, and the rest are all clean cherry picks to Bionic and Focal. [Testcase] This is kind of hard to test, since the problem shows up in production environments that are under constant IO pressure, with many different items entering and leaving the cache. The Launchpad git server is currently suffering this issue, and has been sitting at a constant IO wait of 1 second / slightly over 1 second which was causing slow response times, which was leading to build failures when git clones ended up timing out. We installed a test kernel, which is available in the following PPA:
[Kernel-packages] [Bug 1903682] Re: NULL pointer dereference when configuring multi-function with devfn != 0 before devfn == 0
** Changed in: ubuntu-z-systems Status: Triaged => 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/1903682 Title: NULL pointer dereference when configuring multi-function with devfn != 0 before devfn == 0 Status in Ubuntu on IBM z Systems: In Progress Status in linux package in Ubuntu: Triaged Status in linux source package in Focal: Fix Committed Status in linux source package in Groovy: Triaged Status in linux source package in Hirsute: Triaged Bug description: SRU Justification: == [Impact] * While handling multifunction devices in zPCI the UID of the PCI function with function number 0 (that always exists according to the PCI spec) is taken as domain number. * Therefore if hot plugging functions with a function number larger than 0 are used before function 0, these need to be held in standby before creating the domain and bus. * This has been tested during development of this feature using a patched QEMU and in DPM, but unfortunately never in classic/traditional HMC mode. * On a classic/traditional mode machine with a multi-function device, and hot plug ("Reassign I/O Path") of the FID of the second port of the LPAR, any additional hotplug (and even just deconfiguring a PCI device) will hang - and hotplug now makes the entire Linux instance unresponsive. * The reason for this is a NULL pointer dereference - inc case configuring multi-function with devfn != 0 before devfn == 0. * This issue was introduced with the topology-aware PCI enumeration code. [Fix] * 0b2ca2c7d0c9e2731d01b6c862375d44a7e13923 0b2ca2c7d0c9 "s390/pci: fix hot-plug of PCI function missing bus" [Test Case] * IBM Z or LinuxONE hardware, equipped with hot-pluggable, multi- functional PCIe cards (like for example RoCE Express 2 adapters) in classic/traditional mode. * An Ubuntu OS running in LPAR, that comes with a kernel that includes the topology-aware PCI enumeration code (like for example 20.04.1 w/o further updates or 20.10 GA kernel). * Now on a system that is in classic/traditional mode, hot plug ("Reassign I/O Path") a multi-function device, but using the FID of the second port. [Regression Potential] * There is at least some regression risk, but I consider it as low, because: * Even is the modification is a single if statement (that spans two lines) in 'zpci_event_availability' it could harm the zPCI event management even more, in worst case it could break hot plug not only for systems in classic/traditional mode, but also in DPM mode (and making the system hang) or for all ports. * In such a case no enabling / disabling of devices would be possible. * But the fix is very simple and straight-forward, it checks zdev->zbus->bus for being NULL and in such a case break the function - means breaking instead of calling the PCI common code pci_scan_single_device() with the NULL pointer. * PCIe devices are usually more optional devices on s390x (compared to CCW and OSA devices for network) and this affects the zPCI subsystem only, which is unique to s390x. [Other] * The patch got upstream accepted with kernel v5.10-rc3, hence it will land sooner or later in Hirsute. * The patch has also been tagged for the upstream stable v5.8 series, hence will land in Groovy (based on kernel teams regular 'Groovy update: v5.8.x upstream stable release' LP bug). * Hence requesting this Kernel SRU for Focal only, since Ubuntu releases older than Focal do not have the topology-aware zPCI enumeration code. __ Background: When handling multifunction devices in zPCI we take the UID of the PCI function with function number 0 (that always exists according to the PCI spec) as domain number. Therefore when hot plugging functions with function number larger than 0 before function 0, we need to hold these in standby before creating the domain and bus. This has been tested during feature development using a patched QEMU and with DPM but never in Classic Mode. Reproduction: This issue was introduced with the Topology aware PCI Enumeration code so test with a Linux supporting that feature. E.g. Upstream, Devel Driver etc. On a Classic Mode machine with a multi-function device, hot plug ("Reassign I/O Path") only the FID of the second port to the LPAR. Symptom: After this any additional hotplug and even just deconfiguring a PCI device will hang. A hotplug makes the entire Linux instance unresponsive. Analysis: The problem occurs in Classic Mode but not with previous testing as the LPAR hypervisor does hot plug/Reassign I/O Path as a two step process: 1. zPCI event with PEC 0x0302 to plug the zPCI function in Standby 2. zPCI event with PEC 0x0301 to configure the zPCI function For the
[Kernel-packages] [Bug 1903682] Re: NULL pointer dereference when configuring multi-function with devfn != 0 before devfn == 0
** Changed in: linux (Ubuntu Focal) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Focal) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1903682 Title: NULL pointer dereference when configuring multi-function with devfn != 0 before devfn == 0 Status in Ubuntu on IBM z Systems: Triaged Status in linux package in Ubuntu: Triaged Status in linux source package in Focal: Fix Committed Status in linux source package in Groovy: Triaged Status in linux source package in Hirsute: Triaged Bug description: SRU Justification: == [Impact] * While handling multifunction devices in zPCI the UID of the PCI function with function number 0 (that always exists according to the PCI spec) is taken as domain number. * Therefore if hot plugging functions with a function number larger than 0 are used before function 0, these need to be held in standby before creating the domain and bus. * This has been tested during development of this feature using a patched QEMU and in DPM, but unfortunately never in classic/traditional HMC mode. * On a classic/traditional mode machine with a multi-function device, and hot plug ("Reassign I/O Path") of the FID of the second port of the LPAR, any additional hotplug (and even just deconfiguring a PCI device) will hang - and hotplug now makes the entire Linux instance unresponsive. * The reason for this is a NULL pointer dereference - inc case configuring multi-function with devfn != 0 before devfn == 0. * This issue was introduced with the topology-aware PCI enumeration code. [Fix] * 0b2ca2c7d0c9e2731d01b6c862375d44a7e13923 0b2ca2c7d0c9 "s390/pci: fix hot-plug of PCI function missing bus" [Test Case] * IBM Z or LinuxONE hardware, equipped with hot-pluggable, multi- functional PCIe cards (like for example RoCE Express 2 adapters) in classic/traditional mode. * An Ubuntu OS running in LPAR, that comes with a kernel that includes the topology-aware PCI enumeration code (like for example 20.04.1 w/o further updates or 20.10 GA kernel). * Now on a system that is in classic/traditional mode, hot plug ("Reassign I/O Path") a multi-function device, but using the FID of the second port. [Regression Potential] * There is at least some regression risk, but I consider it as low, because: * Even is the modification is a single if statement (that spans two lines) in 'zpci_event_availability' it could harm the zPCI event management even more, in worst case it could break hot plug not only for systems in classic/traditional mode, but also in DPM mode (and making the system hang) or for all ports. * In such a case no enabling / disabling of devices would be possible. * But the fix is very simple and straight-forward, it checks zdev->zbus->bus for being NULL and in such a case break the function - means breaking instead of calling the PCI common code pci_scan_single_device() with the NULL pointer. * PCIe devices are usually more optional devices on s390x (compared to CCW and OSA devices for network) and this affects the zPCI subsystem only, which is unique to s390x. [Other] * The patch got upstream accepted with kernel v5.10-rc3, hence it will land sooner or later in Hirsute. * The patch has also been tagged for the upstream stable v5.8 series, hence will land in Groovy (based on kernel teams regular 'Groovy update: v5.8.x upstream stable release' LP bug). * Hence requesting this Kernel SRU for Focal only, since Ubuntu releases older than Focal do not have the topology-aware zPCI enumeration code. __ Background: When handling multifunction devices in zPCI we take the UID of the PCI function with function number 0 (that always exists according to the PCI spec) as domain number. Therefore when hot plugging functions with function number larger than 0 before function 0, we need to hold these in standby before creating the domain and bus. This has been tested during feature development using a patched QEMU and with DPM but never in Classic Mode. Reproduction: This issue was introduced with the Topology aware PCI Enumeration code so test with a Linux supporting that feature. E.g. Upstream, Devel Driver etc. On a Classic Mode machine with a multi-function device, hot plug ("Reassign I/O Path") only the FID of the second port to the LPAR. Symptom: After this any additional hotplug and even just deconfiguring a PCI device will hang. A hotplug makes the entire Linux instance unresponsive. Analysis: The problem occurs in Classic Mode but not with previous testing as the LPAR hypervisor does hot plug/Reassign I/O Path as a two step process: 1. zPCI event with PEC 0x0302 to plug the zPCI function in Standby
[Kernel-packages] [Bug 1904445] Re: Focal update: v5.4.74 upstream stable release
** Changed in: linux (Ubuntu Focal) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Focal) Status: In Progress => Fix Committed ** 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/1904445 Title: Focal update: v5.4.74 upstream stable release Status in linux package in Ubuntu: Invalid Status in linux source package in Focal: Fix Committed 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.74 upstream stable release from git://git.kernel.org/ netfilter: nftables_offload: KASAN slab-out-of-bounds Read in nft_flow_rule_create socket: don't clear SOCK_TSTAMP_NEW when SO_TIMESTAMPNS is disabled objtool: Support Clang non-section symbols in ORC generation scripts/setlocalversion: make git describe output more reliable arm64: Run ARCH_WORKAROUND_1 enabling code on all CPUs arm64: Run ARCH_WORKAROUND_2 enabling code on all CPUs arm64: link with -z norelro regardless of CONFIG_RELOCATABLE x86/PCI: Fix intel_mid_pci.c build error when ACPI is not enabled bnxt_en: Check abort error state in bnxt_open_nic(). bnxt_en: Send HWRM_FUNC_RESET fw command unconditionally. chelsio/chtls: fix deadlock issue chelsio/chtls: fix memory leaks in CPL handlers chelsio/chtls: fix tls record info to user cxgb4: set up filter action after rewrites gtp: fix an use-before-init in gtp_newlink() ibmvnic: fix ibmvnic_set_mac mlxsw: core: Fix memory leak on module removal netem: fix zero division in tabledist net/sched: act_mpls: Add softdep on mpls_gso.ko r8169: fix issue with forced threading in combination with shared interrupts ravb: Fix bit fields checking in ravb_hwtstamp_get() tcp: Prevent low rmem stalls with SO_RCVLOWAT. tipc: fix memory leak caused by tipc_buf_append() net: hns3: Clear the CMDQ registers before unmapping BAR region bnxt_en: Re-write PCI BARs after PCI fatal error. bnxt_en: Fix regression in workqueue cleanup logic in bnxt_remove_one(). bnxt_en: Invoke cancel_delayed_work_sync() for PFs also. erofs: avoid duplicated permission check for "trusted." xattrs arch/x86/amd/ibs: Fix re-arming IBS Fetch x86/xen: disable Firmware First mode for correctable memory errors ata: ahci: mvebu: Make SATA PHY optional for Armada 3720 fuse: fix page dereference after free bpf: Fix comment for helper bpf_current_task_under_cgroup() evm: Check size of security.evm before using it p54: avoid accessing the data mapped to streaming DMA cxl: Rework error message for incompatible slots RDMA/addr: Fix race with netevent_callback()/rdma_addr_cancel() mtd: lpddr: Fix bad logic in print_drs_error serial: qcom_geni_serial: To correct QUP Version detection logic serial: pl011: Fix lockdep splat when handling magic-sysrq interrupt PM: runtime: Fix timer_expires data type on 32-bit arches ata: sata_rcar: Fix DMA boundary mask xen/gntdev.c: Mark pages as dirty crypto: x86/crc32c - fix building with clang ias openrisc: Fix issue with get_user for 64-bit values misc: rtsx: do not setting OC_POWER_DOWN reg in rtsx_pci_init_ocp() phy: marvell: comphy: Convert internal SMCC firmware return codes to errno Linux 5.4.74 UBUNTU: upstream stable to v5.4.74 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1904445/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1904450] Re: Focal update: v5.4.75 upstream stable release
** Changed in: linux (Ubuntu Focal) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Focal) Status: In Progress => Fix Committed ** 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/1904450 Title: Focal update: v5.4.75 upstream stable release Status in linux package in Ubuntu: Invalid Status in linux source package in Focal: Fix Committed 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.75 upstream stable release from git://git.kernel.org/ xen/events: avoid removing an event channel while handling it xen/events: add a proper barrier to 2-level uevent unmasking xen/events: fix race in evtchn_fifo_unmask() xen/events: add a new "late EOI" evtchn framework xen/blkback: use lateeoi irq binding xen/netback: use lateeoi irq binding xen/scsiback: use lateeoi irq binding xen/pvcallsback: use lateeoi irq binding xen/pciback: use lateeoi irq binding xen/events: switch user event channels to lateeoi model xen/events: use a common cpu hotplug hook for event channels xen/events: defer eoi in case of excessive number of events xen/events: block rogue events for some time firmware: arm_scmi: Fix ARCH_COLD_RESET firmware: arm_scmi: Add missing Rx size re-initialisation x86/unwind/orc: Fix inactive tasks with stack pointer in %sp on GCC 10 compiled kernels mlxsw: core: Fix use-after-free in mlxsw_emad_trans_finish() RDMA/qedr: Fix memory leak in iWARP CM ata: sata_nv: Fix retrieving of active qcs futex: Fix incorrect should_fail_futex() handling powerpc/powernv/smp: Fix spurious DBG() warning UBUNTU: [Config] update config for ARCH_WANT_IRQS_OFF_ACTIVATE_MM mm: fix exec activate_mm vs TLB shootdown and lazy tlb switching race powerpc: select ARCH_WANT_IRQS_OFF_ACTIVATE_MM sparc64: remove mm_cpumask clearing to fix kthread_use_mm race f2fs: add trace exit in exception path f2fs: fix uninit-value in f2fs_lookup f2fs: fix to check segment boundary during SIT page readahead s390/startup: avoid save_area_sync overflow um: change sigio_spinlock to a mutex f2fs: handle errors of f2fs_get_meta_page_nofail ARM: 8997/2: hw_breakpoint: Handle inexact watchpoint addresses NFS4: Fix oops when copy_file_range is attempted with NFS4.0 source power: supply: bq27xxx: report "not charging" on all types xfs: fix realtime bitmap/summary file truncation when growing rt volume video: fbdev: pvr2fb: initialize variables ath10k: start recovery process when payload length exceeds max htc length for sdio ath10k: fix VHT NSS calculation when STBC is enabled drm/brige/megachips: Add checking if ge_b850v3_lvds_init() is working correctly selftests/x86/fsgsbase: Reap a forgotten child media: videodev2.h: RGB BT2020 and HSV are always full range media: platform: Improve queue set up flow for bug fixing usb: typec: tcpm: During PR_SWAP, source caps should be sent only after tSwapSourceStart media: tw5864: check status of tw5864_frameinterval_get media: imx274: fix frame interval handling mmc: via-sdmmc: Fix data race bug drm/bridge/synopsys: dsi: add support for non-continuous HS clock arm64: topology: Stop using MPIDR for topology information printk: reduce LOG_BUF_SHIFT range for H8300 ia64: kprobes: Use generic kretprobe trampoline handler kgdb: Make "kgdbcon" work properly with "kgdb_earlycon" bpf: Permit map_ptr arithmetic with opcode add and offset 0 media: uvcvideo: Fix dereference of out-of-bound list iterator selftests/bpf: Define string const as global for test_sysctl_prog.c samples/bpf: Fix possible deadlock in xdpsock riscv: Define AT_VECTOR_SIZE_ARCH for ARCH_DLINFO cpufreq: sti-cpufreq: add stih418 support USB: adutux: fix debugging uio: free uio id after uio file node is freed usb: xhci: omit duplicate actions when suspending a runtime suspended host. SUNRPC: Mitigate cond_resched() in xprt_transmit() arm64/mm: return cpu_all_mask when node is NUMA_NO_NODE can: flexcan: disable clocks during stop mode xfs: don't free rt blocks when we're doing a REMAP bunmapi call ACPI: Add out of bounds and numa_off protections to pxm_to_node() brcmfmac: Fix warning message after dongle setup failed drivers/net/wan/hdlc_fr: Correctly handle special skb->protocol values bus/fsl_mc: Do not rely on caller to provide non NULL mc_io ACPI: HMAT: Fix handling of changes from
[Kernel-packages] [Bug 1385113] Re: hid-generic 0005:099A:0500.0001: unknown main item tag 0x0
Same with Ubuntu 20.10 with Nintendo Switch Controller [13057.760448] hid-generic 0005:057E:2009.0003: input,hidraw0: BLUETOOTH HID v0.01 Gamepad [Pro Controller] on 5c:e0:c5:b9:18:14 [13349.524358] intel_powerclamp: Start idle injection to reduce power [13350.532202] intel_powerclamp: Stop forced idle injection [13472.477911] intel_powerclamp: Start idle injection to reduce power [13474.497237] intel_powerclamp: Stop forced idle injection [13484.578532] intel_powerclamp: Start idle injection to reduce power [13485.588576] intel_powerclamp: Stop forced idle injection [13596.460316] intel_powerclamp: Start idle injection to reduce power [13597.469583] intel_powerclamp: Stop forced idle injection [13713.020296] hid-generic 0005:057E:2009.0004: unknown main item tag 0x0 [13713.020428] input: Pro Controller as /devices/pci:00/:00:1d.0/usb1/1-1/1-1.3/1-1.3:1.0/bluetooth/hci0/hci0:256/0005:057E:2009.0004/input/input22 [13713.024183] hid-generic 0005:057E:2009.0004: input,hidraw0: BLUETOOTH HID v0.01 Gamepad [Pro Controller] on 5c:e0:c5:b9:18:14 [13721.432677] intel_powerclamp: Start idle injection to reduce power [13722.443189] intel_powerclamp: Stop forced idle injection [13820.720765] hid-generic 0005:057E:2009.0005: unknown main item tag 0x0 [13820.720890] input: Pro Controller as /devices/pci:00/:00:1d.0/usb1/1-1/1-1.3/1-1.3:1.0/bluetooth/hci0/hci0:256/0005:057E:2009.0005/input/input23 [13820.721751] hid-generic 0005:057E:2009.0005: input,hidraw0: BLUETOOTH HID v0.01 Gamepad [Pro Controller] on 5c:e0:c5:b9:18:14 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1385113 Title: hid-generic 0005:099A:0500.0001: unknown main item tag 0x0 Status in Linux: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: Message with Mouse Bluetooth [ 32.960478] hid-generic 0005:099A:0500.0001: unknown main item tag 0x0 ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: linux-image-3.16.0-23-generic 3.16.0-23.31 ProcVersionSignature: Ubuntu 3.16.0-23.31-generic 3.16.4 Uname: Linux 3.16.0-23-generic x86_64 ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: caravena 3344 F pulseaudio CurrentDesktop: GNOME Date: Fri Oct 24 05:22:54 2014 HibernationDevice: RESUME=UUID=360bd2d2-4f44-4311-86d6-4781ac81ee87 InstallationDate: Installed on 2014-09-25 (29 days ago) InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Alpha amd64 (20140923) MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-3.16.0-23-generic root=UUID=0fb75fae-baa3-428b-ace4-498e69ff7fb6 ro rootflags=subvol=@ quiet splash nomdmonddf nomdmonisw nomdmonddf nomdmonisw vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.16.0-23-generic N/A linux-backports-modules-3.16.0-23-generic N/A linux-firmware 1.138 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/15/2013 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: P14AAJ dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: SAMSUNG_NP1234567890 dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: FAB1 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvrP14AAJ:bd04/15/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1: dmi.product.name: 530U3C/530U4C dmi.product.version: 0.1 dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1385113/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1904225] Re: Use ACPI S5 for reboot
** Changed in: linux (Ubuntu Focal) Status: Confirmed => Fix Committed -- 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/1904225 Title: Use ACPI S5 for reboot Status in HWE Next: New Status in OEM Priority Project: New Status in linux package in Ubuntu: Confirmed Status in linux-oem-5.6 package in Ubuntu: Invalid Status in linux source package in Focal: Fix Committed Status in linux-oem-5.6 source package in Focal: Confirmed Status in linux source package in Groovy: Confirmed Status in linux-oem-5.6 source package in Groovy: Invalid Bug description: [Impact] On some HP laptops, BIOS hotkeys don't work right after reboot, becuase OS doesn't call _PTS to indicate ACPI it's rebooting. [Fix] Follow Windows and use S5 for reboot. [Test case] Reboot and see if hotkeys like F10/F11 can trigger BIOS functions. Hotkeys work great with the patch applied. [Where problems could occur] If there are platforms don't expect S5 for reboot then there could be unexpected result. However Windows uses S5 so that's rather unlikely. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1904225/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1904884] Re: s390: dbginfo.sh triggers kernel panic, reading from /sys/kernel/mm/page_idle/bitmap
** Changed in: linux (Ubuntu Focal) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Focal) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1904884 Title: s390: dbginfo.sh triggers kernel panic, reading from /sys/kernel/mm/page_idle/bitmap Status in Ubuntu on IBM z Systems: In Progress Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: In Progress Status in linux source package in Focal: Fix Committed Status in linux source package in Groovy: Fix Released Status in linux source package in Hirsute: Fix Released Bug description: SRU Justification: == [Impact] * While executing dbginfo.sh (a script to collect runtime, configuration, and trace information on s390x) the systems hangs. * This is because 'idle page tracking' users can pass random pfn, that might be mapped to an offline page - and attempts to access offline pages lead to the hang. * It needs to be avoided that such pages are accessed. * The upstream commit modifies 'page_idle_get_page()' to use 'pfn_to_online_page()' instead of a 'pfn_valid()' and 'pfn_to_page()' combination, so that the pfn mapped to an offline page is skipped. [Fix] * 92fb1db26eef "mm/page_idle.c: skip offline pages" [Test Case] * IBM Z or LinuxONE hardware with Ubuntu Server 18.04 (GA kernel, 4.15) installed. * Execute a test application that tries to access offline pages. * Or execute dbginfo.sh with having some offline (idle) pages in the system. [Regression Potential] * There is a certain regression risk, especially for bionic, since the structure in the kernel 4.15 is a bit different compared to kernel 5.4 (and newer). * However, for newer kernels the modification is pretty save, since it's upstream accepted since kernel 5.8 and with that already inluded in hirsute and groovy. * And the patch is fine (and cherry picks cleanly) for focal as well. * For bionic there is a slightly conflicting context, since the struct 'zone' was replaced by 'pg_data_t *pgdat' (by another commit: 92fb1db26eef), but that change (or any change to the struct zone) would not be necessary to fix the uninitialized struct page access. * Hence the upstream commit/patch needs to be adjusted/backported to bionic 4.15, largely by replacing line 'pg_data_t *pgdat;' with 'struct zone *zone;' (or actually leaving this line). * But this needs to be carefully considered, since the handling of idle pages could be harmful, in the end it could make things even worse, means break even more. [Other] * The patch got upstream accepted with kernel v5.8, hence it's already is in groovy and hirsute. * The upstream commit cherry picks cleanly to focal, but for bionic a backport is needed. * Hence this kernel SRU request is for focal (cherry-pick) and bionic (backport). __ System hangs on dbginfo.sh script execution. Solution: Commit 92fb1db26eef ("mm/page_idle.c: skip offline pages") Included upstream since kernel v5.8, so it is already included in Ubuntu 20.10, but not in 20.04 and earlier. Commit 92fb1db26eef ("mm/page_idle.c: skip offline pages") applies cleanly on ubuntu-focal, but not on ubuntu-bionic. Adjustment / backport for bionic should be trivial, but it is not IBM code and therefore the backport will be requested here by Canonical. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1904884/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1894667] Re: [HP 635] Radeon 6310 brightness control does not work
Via "Focal update: v5.4.75 upstream stable release" for 20.04 ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Focal) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Focal) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1894667 Title: [HP 635] Radeon 6310 brightness control does not work Status in linux package in Ubuntu: Confirmed Status in linux source package in Focal: Fix Committed Bug description: Brightness setting does not work on versions 16.04.7 and 20.04.1 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3.1 ProcVersionSignature: Ubuntu 4.15.0-112.113~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-112-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.24 Architecture: amd64 CasperVersion: 1.376.2 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Mon Sep 7 12:10:27 2020 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Wrestler [Radeon HD 6310] [1002:9802] (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Wrestler [Radeon HD 6310] [103c:3577] LiveMediaBuild: Ubuntu 16.04.7 LTS "Xenial Xerus" - Release amd64 (20200806) MachineType: Hewlett-Packard HP 635 Notebook PC ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=tr_TR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: file=/cdrom/preseed/username.seed boot=casper initrd=/casper/initrd quiet splash --- debian-installer/language=tr keyboard-configuration/layoutcode?=tr SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/18/2011 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: F.48 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 3577 dmi.board.vendor: Hewlett-Packard dmi.board.version: 24.4A dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnHewlett-Packard:bvrF.48:bd12/18/2011:svnHewlett-Packard:pnHP635NotebookPC:pvr058A10004C1000260:rvnHewlett-Packard:rn3577:rvr24.4A:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5336AN G=N L=SMB B=HP S=635 dmi.product.name: HP 635 Notebook PC dmi.product.version: 058A10004C1000260 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.91-2~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Mon Sep 7 14:57:25 2020 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.6-1ubuntu4.1~16.04.2 xserver.video_driver: radeon --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: xubuntu1827 F pulseaudio /dev/snd/controlC0: xubuntu1827 F pulseaudio CasperMD5CheckMismatches: ./pool/main/g/glibc/libc-dev-bin_2.31-0ubuntu9_amd64.deb CasperMD5CheckResult: skip CasperVersion: 1.445.1 CurrentDesktop: XFCE DistroRelease: Ubuntu 20.04 LiveMediaBuild: Xubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Hewlett-Packard HP 635 Notebook PC NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=tr_TR.UTF-8 SHELL=/bin/bash ProcFB: 0 radeondrmfb ProcKernelCmdLine: file=/cdrom/preseed/username.seed initrd=/casper/initrd quiet splash --- debian-installer/language=tr keyboard-configuration/layoutcode?=tr ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 RelatedPackageVersions: linux-restricted-modules-5.4.0-42-generic N/A linux-backports-modules-5.4.0-42-generic N/A linux-firmware1.187.2 Tags: focal Uname: Linux 5.4.0-42-generic
[Kernel-packages] [Bug 1904221] Re: Ask 8821C Bluetooth controller to drop old firmware
** Changed in: linux (Ubuntu Focal) Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1904221 Title: Ask 8821C Bluetooth controller to drop old firmware Status in linux package in Ubuntu: Confirmed Status in linux-oem-5.6 package in Ubuntu: Invalid Status in linux source package in Focal: Fix Committed Status in linux-oem-5.6 source package in Focal: Confirmed Status in linux source package in Groovy: Confirmed Status in linux-oem-5.6 source package in Groovy: Invalid Bug description: [Impact] Some platforms may keep USB power in S3/S4/S5, so Realtek 8821C retains its firmware even with a cold boot. [Fix] Use vendor command to drop firmware if the version is old. [Test case] Use dmesg to check if new firmware is loaded. With the patch applied, we can find new firmware is loaded. [Where problems could occur] There's a 200ms delay which can slow down when BT controller is opened by userspace first time. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1904221/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1894329] Re: ZFS revert from grub menu not working.
** Description changed: + [Impact] + + * Users can’t revert to previous snapshots when enabling the hw enablement stack kernel on focal or using any more recent version. + * The option is available on grub and will let you with a broken system, partially cloned. + + [Test Case] + + * Boot on a system, using ZFS and ZSys. + * In grub, select "History" entry + * Select one of the "Revert" option: the system should boot after being reverted with an older version. + + + [Where problems could occur] + * The code is in the initramfs, where the generated id suffix for all our ZFS datasets was empty due to new coreutils/kernels. + * We replace dd with another way (more robust and simple) for generating this ID. + + + - + @coreutils maintainers, any idea why dd is being flagged as having an executable stack? When I try to revert to a previous state from the grub menu, the boot fails. The system drops me to a repair modus. zfs-mount-generator fails with the message: couldn't ensure boot: Mounted clone bootFS dataset created by initramfs doesn't have a valid _suffix (at least .*_): \"rpool/ROOT/ubuntu_\"". After a reboot I have an extra clone called "rpool/ROOT/ubuntu_", indeed without a suffix. After a little investigation I found the problem in /usr/share/initramfs-tools/scripts/zfs at the end in function uid() { dd if=/dev/urandom of=/dev/stdout bs=1 count=100 2>/dev/null | tr -dc 'a-z0-9' | cut -c-6 }, the dd command fails during boot with the message "process 'dd' started with executable stack. After this an empty uid is returned which explains the dataset without a proper suffix. Replacing the function with: uid() { grep -a -m10 -E "\*" /dev/urandom 2>/dev/null | tr -dc 'a-z0-9' | cut -c-6 } fixes the problem. Ubuntu version is: Description:Ubuntu Groovy Gorilla (development branch) Release:20.10 zfs-initramfs version is: 0.8.4-1ubuntu11 With regards, Usarin Heininga ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: zfs-initramfs 0.8.4-1ubuntu11 ProcVersionSignature: Ubuntu 5.8.0-18.19-generic 5.8.4 Uname: Linux 5.8.0-18-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu45 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Fri Sep 4 20:23:44 2020 InstallationDate: Installed on 2020-09-02 (2 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200831) ProcEnviron: LANGUAGE= PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=nl_NL.UTF-8 SHELL=/bin/bash SourcePackage: zfs-linux UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1894329 Title: ZFS revert from grub menu not working. Status in coreutils package in Ubuntu: Incomplete Status in zfs-linux package in Ubuntu: Fix Released Status in coreutils source package in Focal: Incomplete Status in zfs-linux source package in Focal: Triaged Status in coreutils source package in Groovy: Incomplete Status in zfs-linux source package in Groovy: Triaged Bug description: [Impact] * Users can’t revert to previous snapshots when enabling the hw enablement stack kernel on focal or using any more recent version. * The option is available on grub and will let you with a broken system, partially cloned. [Test Case] * Boot on a system, using ZFS and ZSys. * In grub, select "History" entry * Select one of the "Revert" option: the system should boot after being reverted with an older version. [Where problems could occur] * The code is in the initramfs, where the generated id suffix for all our ZFS datasets was empty due to new coreutils/kernels. * We replace dd with another way (more robust and simple) for generating this ID. - @coreutils maintainers, any idea why dd is being flagged as having an executable stack? When I try to revert to a previous state from the grub menu, the boot fails. The system drops me to a repair modus. zfs-mount-generator fails with the message: couldn't ensure boot: Mounted clone bootFS dataset created by initramfs doesn't have a valid _suffix (at least .*_): \"rpool/ROOT/ubuntu_\"". After a reboot I have an extra clone called "rpool/ROOT/ubuntu_", indeed without a suffix. After a little investigation I found the problem in /usr/share/initramfs-tools/scripts/zfs at the end in function uid() { dd if=/dev/urandom of=/dev/stdout bs=1 count=100 2>/dev/null | tr -dc 'a-z0-9' | cut -c-6 }, the dd command fails during boot with the message "process 'dd' started with executable stack. After this an empty uid is returned which explains the
[Kernel-packages] [Bug 1903397] Re: Groovy 5.8 kernel hangs on boot on CPUs with eLLC
In case -proposed in Focal's HWE needs also verification: could someone with a 5675C or 5775C test 5.8.0-31.33~20.04.1 with the corresponding patch as well? I've unfortunately no access to my Broadwell machine for the next 5-7 days. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1903397 Title: Groovy 5.8 kernel hangs on boot on CPUs with eLLC Status in linux package in Ubuntu: Confirmed Status in linux-hwe-5.8 package in Ubuntu: Confirmed Status in linux-hwe-5.8 source package in Focal: In Progress Status in linux source package in Groovy: Fix Committed Bug description: 5.8 kernel hangs on boot on my PC with Intel Core i7-5775C. Bug is already fixed upstream: https://gitlab.freedesktop.org/drm/intel/-/issues/2381 https://bugzilla.kernel.org/show_bug.cgi?id=208737 https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?h=v5.10-rc1=1664ffee760a5d98952318fdd9b198fae396d660 Please backport the fix. Thanks! [Impact] * Bug causes boot failure on common hardware. [Test Case] * Test kernel validated by submitter (see Comment #6). [Regression Potential] * Low: Simple cherry-pick from upstream. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1903397/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1903397] Re: Groovy 5.8 kernel hangs on boot on CPUs with eLLC
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux-hwe-5.8 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1903397 Title: Groovy 5.8 kernel hangs on boot on CPUs with eLLC Status in linux package in Ubuntu: Confirmed Status in linux-hwe-5.8 package in Ubuntu: Confirmed Status in linux-hwe-5.8 source package in Focal: In Progress Status in linux source package in Groovy: Fix Committed Bug description: 5.8 kernel hangs on boot on my PC with Intel Core i7-5775C. Bug is already fixed upstream: https://gitlab.freedesktop.org/drm/intel/-/issues/2381 https://bugzilla.kernel.org/show_bug.cgi?id=208737 https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?h=v5.10-rc1=1664ffee760a5d98952318fdd9b198fae396d660 Please backport the fix. Thanks! [Impact] * Bug causes boot failure on common hardware. [Test Case] * Test kernel validated by submitter (see Comment #6). [Regression Potential] * Low: Simple cherry-pick from upstream. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1903397/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1904589] Re: zfs PANIC: accessing past end of object in 0.8.3-1ubuntu12.4
Upstream fix that has been backported is attached ** Patch added: "upstream patch" https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1904589/+attachment/5438715/+files/0001-Bugfix-fix-uio-partial-copies.patch -- 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/1904589 Title: zfs PANIC: accessing past end of object in 0.8.3-1ubuntu12.4 Status in zfs-linux package in Ubuntu: Fix Released Status in zfs-linux source package in Focal: In Progress Status in zfs-linux source package in Groovy: Fix Released Status in zfs-linux source package in Hirsute: Fix Released Bug description: Using latest zfs 0.8.3-1ubuntu12.4 on latest Ubuntu 20.04.1, I observe a rare zfs panics that seem to be workload-specific which render a server mostly unresponsive besides ssh still working. Attempting to reboot the server in this state makes the shutdown hang forever. You may want to consider backporting the fix released in zfs 0.8.4 into 20.04: https://github.com/openzfs/zfs/pull/10148 Log sample of panic: ``` Nov 17 16:06:15 hostname kernel: [3385134.716024] PANIC: zfs: accessing past end of object c1c/2db52f (size=17408 access=7492+16428) Nov 17 16:06:15 hostname kernel: [3385134.716072] Showing stack for process 3166846 Nov 17 16:06:15 hostname kernel: [3385134.716074] CPU: 25 PID: 3166846 Comm: node Tainted: P O 5.4.0-48-generic #52-Ubuntu Nov 17 16:06:15 hostname kernel: [3385134.716075] Hardware name: Nov 17 16:06:15 hostname kernel: [3385134.716076] Call Trace: Nov 17 16:06:15 hostname kernel: [3385134.716085] dump_stack+0x6d/0x9a Nov 17 16:06:15 hostname kernel: [3385134.716097] spl_dumpstack+0x29/0x2b [spl] Nov 17 16:06:15 hostname kernel: [3385134.716102] vcmn_err.cold+0x60/0x99 [spl] Nov 17 16:06:15 hostname kernel: [3385134.716106] ? _cond_resched+0x19/0x30 Nov 17 16:06:15 hostname kernel: [3385134.716108] ? __kmalloc_node+0x20e/0x330 Nov 17 16:06:15 hostname kernel: [3385134.716113] ? spl_kmem_alloc_impl+0xa8/0x100 [spl] Nov 17 16:06:15 hostname kernel: [3385134.716190] ? __list_add+0x17/0x40 [zfs] Nov 17 16:06:15 hostname kernel: [3385134.716235] zfs_panic_recover+0x6f/0x90 [zfs] Nov 17 16:06:15 hostname kernel: [3385134.716272] ? dsl_dir_tempreserve_impl.isra.0.constprop.0+0xed/0x330 [zfs] Nov 17 16:06:15 hostname kernel: [3385134.716305] dmu_buf_hold_array_by_dnode+0x3a0/0x490 [zfs] Nov 17 16:06:15 hostname kernel: [3385134.716338] dmu_write_uio_dnode+0x4c/0x140 [zfs] Nov 17 16:06:15 hostname kernel: [3385134.716370] dmu_write_uio_dbuf+0x4f/0x70 [zfs] Nov 17 16:06:15 hostname kernel: [3385134.716416] zfs_write+0xa1f/0xd40 [zfs] Nov 17 16:06:15 hostname kernel: [3385134.716419] ? d_absolute_path+0x74/0xb0 Nov 17 16:06:15 hostname kernel: [3385134.716421] ? __switch_to_asm+0x34/0x70 Nov 17 16:06:15 hostname kernel: [3385134.716423] ? __switch_to_asm+0x40/0x70 Nov 17 16:06:15 hostname kernel: [3385134.716424] ? __switch_to_asm+0x40/0x70 Nov 17 16:06:15 hostname kernel: [3385134.716425] ? __switch_to_asm+0x34/0x70 Nov 17 16:06:15 hostname kernel: [3385134.716427] ? __switch_to_asm+0x34/0x70 Nov 17 16:06:15 hostname kernel: [3385134.716474] zpl_write_common_iovec+0xad/0x120 [zfs] Nov 17 16:06:15 hostname kernel: [3385134.716567] zpl_iter_write+0x56/0x90 [zfs] Nov 17 16:06:15 hostname kernel: [3385134.716570] do_iter_write+0x84/0x1a0 Nov 17 16:06:15 hostname kernel: [3385134.716574] ? futex_wake+0x8b/0x180 Nov 17 16:06:15 hostname kernel: [3385134.716577] do_writev+0x71/0x120 Nov 17 16:06:15 hostname kernel: [3385134.716581] do_syscall_64+0x57/0x190 Nov 17 16:06:15 hostname kernel: [3385134.716584] RIP: 0033:0x7fa366eee0cd Nov 17 16:06:15 hostname kernel: [3385134.716587] RSP: 002b:7fa35e7fbde0 EFLAGS: 0293 ORIG_RAX: 0014 Nov 17 16:06:15 hostname kernel: [3385134.716590] RDX: 000c RSI: 0651c7b0 RDI: 001d ``` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1904589/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1903596] Re: stack trace in kernel
** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Hirsute) Importance: Undecided Status: Confirmed ** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Groovy) Importance: Undecided Status: New ** Description changed: - This appears to be a problem in the ath10k module. I am not sure what it - is exactly. + == SRU Justification == + Whenever a buggy NAPI driver returns more than its budget, it will + trigger a stack trace warning with: + WARN_ON_ONCE(work > weight); + + The warning message looks like this : + WARNING: CPU: 2 PID: 0 at /build/linux-hwe-ymdo11/linux-hwe-4.15.0/net/core/dev.c:5672 net_rx_action+0x276/0x3b0 + + This is not very useful for debugging purpose, since it does not tell + you what's going on there. + + == Fix == + * 427d5838e996 ("net: napi: remove useless stack trace") + + This patch will emit a message giving the function name, and a + descriptive message like: + NAPI poll function ath10k_pci_napi_poll+0x0/0x120 [ath10k_pci] returned 0, exceeding its budget of 64. + + This patch is a clean-cherry for all the releases except Xenial. + For Xenial it will need to be applied with -C1 + + == Test == + Test kernels can be found here: + https://people.canonical.com/~phlin/kernel/lp-1903596-napi-warnon/ + + Please note that even though I tried to reproduce this on a XPS 13 + 9360 mentioned in this bug report that shipped with Atheros QCA6174 + [168c:003e] wireless card, but I can't trigger this warning message. + The bug opener is also unable to test this due to some other reasons. + + Howeve I did tried to trigger this warning forcibly by putting it + outside the if statement with the test kernels in the following link + to make sure it won't cause some other problem. + + https://people.canonical.com/~phlin/kernel/lp-1903596-napi-warnon/force- + to-warn/ + + == Where problems could occur == + For this bug itself, this patch does not really solve the problem + but it will provide more debug information for developers in the + future (and since this is just a warning message, it should be fine). + We can expect to see more a detailed report against ath10k driver + in the future on launchpad. + + + == Original Bug Report == + This appears to be a problem in the ath10k module. I am not sure what it is exactly. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.15.0-122-generic 4.15.0-122.124~16.04.1 ProcVersionSignature: Ubuntu 4.15.0-122.124~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-122-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.26 Architecture: amd64 CurrentDesktop: Unity Date: Mon Nov 9 13:35:54 2020 DistributionChannelDescriptor: - # This is a distribution channel descriptor - # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor - canonical-oem-somerville-xenial-amd64-20160624-2 + # This is a distribution channel descriptor + # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor + canonical-oem-somerville-xenial-amd64-20160624-2 InstallationDate: Installed on 2020-11-09 (0 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 SourcePackage: linux-signed-hwe UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1903596 Title: stack trace in kernel Status in linux package in Ubuntu: Confirmed Status in linux source package in Xenial: New Status in linux source package in Bionic: New Status in linux source package in Focal: New Status in linux source package in Groovy: New Status in linux source package in Hirsute: Confirmed Bug description: == SRU Justification == Whenever a buggy NAPI driver returns more than its budget, it will trigger a stack trace warning with: WARN_ON_ONCE(work > weight); The warning message looks like this : WARNING: CPU: 2 PID: 0 at /build/linux-hwe-ymdo11/linux-hwe-4.15.0/net/core/dev.c:5672 net_rx_action+0x276/0x3b0 This is not very useful for debugging purpose, since it does not tell you what's going on there. == Fix == * 427d5838e996 ("net: napi: remove useless stack trace") This patch will emit a message giving the function name, and a descriptive message like: NAPI poll function ath10k_pci_napi_poll+0x0/0x120 [ath10k_pci] returned 0, exceeding its budget of 64. This patch is a clean-cherry for all the releases except Xenial. For Xenial it will need to be applied with -C1 == Test == Test kernels can be found here: https://people.canonical.com/~phlin/kernel/lp-1903596-napi-warnon/ Please note that even though I tried to reproduce this on a XPS 13 9360 mentioned in this bug report that shipped with
[Kernel-packages] [Bug 1905214] Re: linux-firmware: intel AX200 (8087:0029) and AX201(8087:0026) bluetooth firmware update
@bmerchant8-0 That fixed it! -- 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/1905214 Title: linux-firmware: intel AX200 (8087:0029) and AX201(8087:0026) bluetooth firmware update 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 Groovy: In Progress Status in linux-firmware source package in Hirsute: Fix Released Bug description: For H, it already has all patches, this SRU is not needed for H For G, only needs the 0005-xxx.patch and 0010-xxx.patch For F, needs all patches. [Impact] We found 2 issues: Bluetooth headset can't work in hsp/hfp mode, Both AX200 and AX201 have this issue (#1871794) Bluetooth will stop working randomly on the machines with AX200 (OEM bug). [Fix] Update the firmware to the latest version, the above 2 issues could be fixed. [Test] connect a bluetooth headset, after connecting, it is in A2DP mode by default, change it to hsp/hfp mode from gnome-sound-setting, play sound and record sound from headset, all work well. Keep the machine powered on and let it be idle for 1 day, check the bluetooth headset, still could work. [Regression Potential] I could make the Bluetooth function stop working on the machines with AX200 or AX201 module, like can't scan the BT devices, can't connect the BT devices or the BT devices can't work normally. But this possibility is very low, we have tested the SRU on a couple of lenovo machines, all worked well. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1905214/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1885087] Please test proposed package
Hello hugh, or anyone else affected, Accepted nvidia-graphics-drivers-455 into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source /nvidia-graphics-drivers-455/455.45.01-0ubuntu0.18.04.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-450 in Ubuntu. https://bugs.launchpad.net/bugs/1885087 Title: Can't keep brightness value after reboot/poweroff in some nvidia gfx Status in OEM Priority Project: Confirmed Status in OEM Priority Project focal series: New Status in nvidia-graphics-drivers-450 package in Ubuntu: In Progress Status in nvidia-graphics-drivers-455 package in Ubuntu: Fix Committed Status in nvidia-graphics-drivers-450 source package in Bionic: New Status in nvidia-graphics-drivers-455 source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-450 source package in Focal: In Progress Status in nvidia-graphics-drivers-455 source package in Focal: Fix Committed Status in nvidia-graphics-drivers-450 source package in Groovy: New Status in nvidia-graphics-drivers-455 source package in Groovy: Fix Committed Bug description: systemd-backlight saves the brightness value right before shutdown.target, however it doesn't work because the nvidia_0 backlight sysfs disappears after GFX device is closed by Xorg, long before shutdown.target. [Impact] System can not keep the brightness value, after reboot/poweroff the brightness will still be highest. [Fix] Suggested by Nvidia, we need to run nvidia-persistenced.service before systemd-backlight@backlight:nvidia_0.service [Test Case] Adjust the brightness value, reboot, the value must keep persistence during boots. [Regression Risk] Low, this fix is just adjust the systemd order more earier. https://github.com/hugh712/nvidia-graphics-drivers To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1885087/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1885087] Re: Can't keep brightness value after reboot/poweroff in some nvidia gfx
Hello hugh, or anyone else affected, Accepted nvidia-graphics-drivers-455 into groovy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source /nvidia-graphics-drivers-455/455.45.01-0ubuntu0.20.10.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- groovy to verification-done-groovy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-groovy. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Tags added: verification-needed verification-needed-groovy ** Also affects: nvidia-graphics-drivers-455 (Ubuntu) Importance: Undecided Status: New ** Also affects: nvidia-graphics-drivers-450 (Ubuntu Groovy) Importance: Undecided Status: New ** Also affects: nvidia-graphics-drivers-455 (Ubuntu Groovy) Importance: Undecided Status: New ** Changed in: nvidia-graphics-drivers-455 (Ubuntu) Status: New => Fix Committed ** Changed in: nvidia-graphics-drivers-455 (Ubuntu Groovy) Status: New => Fix Committed ** Changed in: nvidia-graphics-drivers-455 (Ubuntu Focal) Status: New => Fix Committed ** Tags added: verification-needed-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-450 in Ubuntu. https://bugs.launchpad.net/bugs/1885087 Title: Can't keep brightness value after reboot/poweroff in some nvidia gfx Status in OEM Priority Project: Confirmed Status in OEM Priority Project focal series: New Status in nvidia-graphics-drivers-450 package in Ubuntu: In Progress Status in nvidia-graphics-drivers-455 package in Ubuntu: Fix Committed Status in nvidia-graphics-drivers-450 source package in Bionic: New Status in nvidia-graphics-drivers-455 source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-450 source package in Focal: In Progress Status in nvidia-graphics-drivers-455 source package in Focal: Fix Committed Status in nvidia-graphics-drivers-450 source package in Groovy: New Status in nvidia-graphics-drivers-455 source package in Groovy: Fix Committed Bug description: systemd-backlight saves the brightness value right before shutdown.target, however it doesn't work because the nvidia_0 backlight sysfs disappears after GFX device is closed by Xorg, long before shutdown.target. [Impact] System can not keep the brightness value, after reboot/poweroff the brightness will still be highest. [Fix] Suggested by Nvidia, we need to run nvidia-persistenced.service before systemd-backlight@backlight:nvidia_0.service [Test Case] Adjust the brightness value, reboot, the value must keep persistence during boots. [Regression Risk] Low, this fix is just adjust the systemd order more earier. https://github.com/hugh712/nvidia-graphics-drivers To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1885087/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1885087] Please test proposed package
Hello hugh, or anyone else affected, Accepted nvidia-graphics-drivers-455 into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source /nvidia-graphics-drivers-455/455.45.01-0ubuntu0.20.04.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Also affects: nvidia-graphics-drivers-450 (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: nvidia-graphics-drivers-455 (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: nvidia-graphics-drivers-455 (Ubuntu Bionic) Status: New => Fix Committed ** Tags added: verification-needed-bionic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-450 in Ubuntu. https://bugs.launchpad.net/bugs/1885087 Title: Can't keep brightness value after reboot/poweroff in some nvidia gfx Status in OEM Priority Project: Confirmed Status in OEM Priority Project focal series: New Status in nvidia-graphics-drivers-450 package in Ubuntu: In Progress Status in nvidia-graphics-drivers-455 package in Ubuntu: Fix Committed Status in nvidia-graphics-drivers-450 source package in Bionic: New Status in nvidia-graphics-drivers-455 source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-450 source package in Focal: In Progress Status in nvidia-graphics-drivers-455 source package in Focal: Fix Committed Status in nvidia-graphics-drivers-450 source package in Groovy: New Status in nvidia-graphics-drivers-455 source package in Groovy: Fix Committed Bug description: systemd-backlight saves the brightness value right before shutdown.target, however it doesn't work because the nvidia_0 backlight sysfs disappears after GFX device is closed by Xorg, long before shutdown.target. [Impact] System can not keep the brightness value, after reboot/poweroff the brightness will still be highest. [Fix] Suggested by Nvidia, we need to run nvidia-persistenced.service before systemd-backlight@backlight:nvidia_0.service [Test Case] Adjust the brightness value, reboot, the value must keep persistence during boots. [Regression Risk] Low, this fix is just adjust the systemd order more earier. https://github.com/hugh712/nvidia-graphics-drivers To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1885087/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1904863] Please test proposed package
Hello Alberto, or anyone else affected, Accepted nvidia-graphics-drivers-455 into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source /nvidia-graphics-drivers-455/455.45.01-0ubuntu0.18.04.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-455 in Ubuntu. https://bugs.launchpad.net/bugs/1904863 Title: Update the NVIDIA 455 driver Status in nvidia-graphics-drivers-455 package in Ubuntu: In Progress Status in nvidia-graphics-drivers-455 source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-455 source package in Focal: Fix Committed Status in nvidia-graphics-drivers-455 source package in Groovy: Fix Committed Bug description: [Impact] These releases provide both bug fixes and new features, and we would like to make sure all of our users have access to these improvements. See the changelog entry below for a full list of changes and bugs. [Test Case] The following development and SRU process was followed: https://wiki.ubuntu.com/NVidiaUpdates Certification test suite must pass on a range of hardware: https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu The QA team that executed the tests will be in charge of attaching the artifacts and console output of the appropriate run to the bug. nVidia maintainers team members will not mark ‘verification-done’ until this has happened. [Regression Potential] In order to mitigate the regression potential, the results of the aforementioned system level tests are attached to this bug. [Discussion] [Changelogs] * New upstream release: - Fixed a bug in a Vulkan blending optimization that could produce incorrect results. Some of the Vulkan titles affected by this bug were: Life is Strange 2 Shadow of the Tomb Raider - Fixed an issue that caused Vulkan swapchain creation to fail for full-screen windows when a G-SYNC monitor is connected. [ Kai-Heng Feng ] * debian/71-nvidia.rules: - Add rules to enable runtimepm by default. [ Alberto Milone ] * debian/add-ids-to-json-db, debian/additional_runtimepm_ids, debian/rules: - Make it possible to add new IDs to mark support for runtimepm. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-455/+bug/1904863/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1904863] Please test proposed package
Hello Alberto, or anyone else affected, Accepted nvidia-graphics-drivers-455 into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source /nvidia-graphics-drivers-455/455.45.01-0ubuntu0.20.04.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: nvidia-graphics-drivers-455 (Ubuntu Bionic) Status: In Progress => Fix Committed ** Tags added: verification-needed-bionic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-455 in Ubuntu. https://bugs.launchpad.net/bugs/1904863 Title: Update the NVIDIA 455 driver Status in nvidia-graphics-drivers-455 package in Ubuntu: In Progress Status in nvidia-graphics-drivers-455 source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-455 source package in Focal: Fix Committed Status in nvidia-graphics-drivers-455 source package in Groovy: Fix Committed Bug description: [Impact] These releases provide both bug fixes and new features, and we would like to make sure all of our users have access to these improvements. See the changelog entry below for a full list of changes and bugs. [Test Case] The following development and SRU process was followed: https://wiki.ubuntu.com/NVidiaUpdates Certification test suite must pass on a range of hardware: https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu The QA team that executed the tests will be in charge of attaching the artifacts and console output of the appropriate run to the bug. nVidia maintainers team members will not mark ‘verification-done’ until this has happened. [Regression Potential] In order to mitigate the regression potential, the results of the aforementioned system level tests are attached to this bug. [Discussion] [Changelogs] * New upstream release: - Fixed a bug in a Vulkan blending optimization that could produce incorrect results. Some of the Vulkan titles affected by this bug were: Life is Strange 2 Shadow of the Tomb Raider - Fixed an issue that caused Vulkan swapchain creation to fail for full-screen windows when a G-SYNC monitor is connected. [ Kai-Heng Feng ] * debian/71-nvidia.rules: - Add rules to enable runtimepm by default. [ Alberto Milone ] * debian/add-ids-to-json-db, debian/additional_runtimepm_ids, debian/rules: - Make it possible to add new IDs to mark support for runtimepm. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-455/+bug/1904863/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1904863] Re: Update the NVIDIA 455 driver
Hello Alberto, or anyone else affected, Accepted nvidia-graphics-drivers-455 into groovy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source /nvidia-graphics-drivers-455/455.45.01-0ubuntu0.20.10.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- groovy to verification-done-groovy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-groovy. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: nvidia-graphics-drivers-455 (Ubuntu Groovy) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-groovy ** Changed in: nvidia-graphics-drivers-455 (Ubuntu Focal) Status: In Progress => Fix Committed ** Tags added: verification-needed-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-455 in Ubuntu. https://bugs.launchpad.net/bugs/1904863 Title: Update the NVIDIA 455 driver Status in nvidia-graphics-drivers-455 package in Ubuntu: In Progress Status in nvidia-graphics-drivers-455 source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-455 source package in Focal: Fix Committed Status in nvidia-graphics-drivers-455 source package in Groovy: Fix Committed Bug description: [Impact] These releases provide both bug fixes and new features, and we would like to make sure all of our users have access to these improvements. See the changelog entry below for a full list of changes and bugs. [Test Case] The following development and SRU process was followed: https://wiki.ubuntu.com/NVidiaUpdates Certification test suite must pass on a range of hardware: https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu The QA team that executed the tests will be in charge of attaching the artifacts and console output of the appropriate run to the bug. nVidia maintainers team members will not mark ‘verification-done’ until this has happened. [Regression Potential] In order to mitigate the regression potential, the results of the aforementioned system level tests are attached to this bug. [Discussion] [Changelogs] * New upstream release: - Fixed a bug in a Vulkan blending optimization that could produce incorrect results. Some of the Vulkan titles affected by this bug were: Life is Strange 2 Shadow of the Tomb Raider - Fixed an issue that caused Vulkan swapchain creation to fail for full-screen windows when a G-SYNC monitor is connected. [ Kai-Heng Feng ] * debian/71-nvidia.rules: - Add rules to enable runtimepm by default. [ Alberto Milone ] * debian/add-ids-to-json-db, debian/additional_runtimepm_ids, debian/rules: - Make it possible to add new IDs to mark support for runtimepm. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-455/+bug/1904863/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1854001] Re: pmtu net kernel selftests are skipped on bionic linux-hwe-edge 5.3
We don have this net/pmtu test in bionic 4.15 and this has already landed on 5.4, therefore I will close this bug. ** Changed in: ubuntu-kernel-tests Status: New => Fix Released ** Changed in: iproute2 (Ubuntu Bionic) Status: New => Invalid ** Package changed: linux-hwe-edge (Ubuntu) => linux (Ubuntu) ** Changed in: linux (Ubuntu) Status: In Progress => Fix Released ** Changed in: linux (Ubuntu Bionic) Status: In Progress => Won't Fix -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to iproute2 in Ubuntu. Matching subscriptions: iproute2 https://bugs.launchpad.net/bugs/1854001 Title: pmtu net kernel selftests are skipped on bionic linux-hwe-edge 5.3 Status in ubuntu-kernel-tests: Fix Released Status in iproute2 package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in iproute2 source package in Bionic: Invalid Status in linux source package in Bionic: Won't Fix Bug description: [Impact] selftests will incorrectly indicate a failure, taking the time of developers to verify a false positive, and preventing us from finding real bugs in the corresponding code. [Test case] Run the script directly and verify there are no failures. sudo ./tools/testing/selftests/net/pmtu.sh [Regression potential] No kernel code was changed, only the test. The fix could cause false positives to happen with newer versions of iproute2, but those were tested as well. 11:52:44 DEBUG| [stdout] # selftests: net: pmtu.sh 11:52:44 DEBUG| [stdout] # TEST: ipv4: PMTU exceptions [ OK ] 11:52:44 DEBUG| [stdout] # TEST: ipv6: PMTU exceptions [ OK ] 11:52:44 DEBUG| [stdout] # vxlan4 not supported 11:52:44 DEBUG| [stdout] # TEST: IPv4 over vxlan4: PMTU exceptions [SKIP] 11:52:44 DEBUG| [stdout] # vxlan4 not supported 11:52:44 DEBUG| [stdout] # TEST: IPv6 over vxlan4: PMTU exceptions [SKIP] 11:52:46 DEBUG| [stdout] # TEST: IPv4 over vxlan6: PMTU exceptions [ OK ] 11:52:47 DEBUG| [stdout] # TEST: IPv6 over vxlan6: PMTU exceptions [ OK ] 11:52:47 DEBUG| [stdout] # geneve4 not supported 11:52:47 DEBUG| [stdout] # TEST: IPv4 over geneve4: PMTU exceptions [SKIP] 11:52:47 DEBUG| [stdout] # geneve4 not supported 11:52:47 DEBUG| [stdout] # TEST: IPv6 over geneve4: PMTU exceptions [SKIP] 11:52:48 DEBUG| [stdout] # TEST: IPv4 over geneve6: PMTU exceptions [ OK ] 11:52:49 DEBUG| [stdout] # TEST: IPv6 over geneve6: PMTU exceptions [ OK ] 11:52:51 DEBUG| [stdout] # TEST: IPv4 over fou4: PMTU exceptions [ OK ] 11:52:52 DEBUG| [stdout] # TEST: IPv6 over fou4: PMTU exceptions [ OK ] 11:52:53 DEBUG| [stdout] # TEST: IPv4 over fou6: PMTU exceptions [ OK ] 11:52:54 DEBUG| [stdout] # TEST: IPv6 over fou6: PMTU exceptions [ OK ] 11:52:55 DEBUG| [stdout] # TEST: IPv4 over gue4: PMTU exceptions [ OK ] 11:52:57 DEBUG| [stdout] # TEST: IPv6 over gue4: PMTU exceptions [ OK ] 11:52:58 DEBUG| [stdout] # TEST: IPv4 over gue6: PMTU exceptions [ OK ] 11:52:59 DEBUG| [stdout] # TEST: IPv6 over gue6: PMTU exceptions [ OK ] 11:53:00 DEBUG| [stdout] # TEST: vti6: PMTU exceptions [ OK ] 11:53:03 DEBUG| [stdout] # TEST: vti4: PMTU exceptions [ OK ] 11:53:03 DEBUG| [stdout] # TEST: vti4: default MTU assignment [ OK ] 11:53:03 DEBUG| [stdout] # TEST: vti6: default MTU assignment [ OK ] 11:53:03 DEBUG| [stdout] # TEST: vti4: MTU setting on link creation [ OK ] 11:53:04 DEBUG| [stdout] # TEST: vti6: MTU setting on link creation [ OK ] 11:53:04 DEBUG| [stdout] # TEST: vti6: MTU changes on link changes [ OK ] 11:53:04 DEBUG| [stdout] # vxlan4 not supported 11:53:04 DEBUG| [stdout] # TEST: ipv4: cleanup of cached exceptions [SKIP] Upgrading iproute2 to 5.2 fixes this. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1854001/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1905951] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1905951 Title: Touchpad not working on ACER SWIFT 3 Status in linux package in Ubuntu: Confirmed Bug description: I have just installed Ubuntu 20.04 on my new ACER SWIFT3 and the touchpad is not even recognized by the system. It did not work even during the instalation of ubuntu either. List of devices attached. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-54-generic 5.4.0-54.60 ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65 Uname: Linux 5.4.0-54-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.13 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Nov 27 11:56:48 2020 InstallationDate: Installed on 2020-11-27 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Acer Swift SF313-53 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=cs_CZ.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-54-generic root=UUID=371bc628-e284-48e1-b91b-fbdd04f2875e ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-54-generic N/A linux-backports-modules-5.4.0-54-generic N/A linux-firmware1.187.4 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/17/2020 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.03 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Skol_TL dmi.board.vendor: TGL dmi.board.version: V1.03 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.03:bd09/17/2020:svnAcer:pnSwiftSF313-53:pvrV1.03:rvnTGL:rnSkol_TL:rvrV1.03:cvnAcer:ct10:cvrChassisVersion: dmi.product.family: Swift 3 dmi.product.name: Swift SF313-53 dmi.product.sku: dmi.product.version: V1.03 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1905951/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1880645] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1880645 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-oem-5.6 in Ubuntu. https://bugs.launchpad.net/bugs/1880645 Title: icmp_redirect.sh in net from ubuntu_kernel_selftests failed on F-OEM-5.6 / G-AWS Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Status in linux-signed-oem-5.6 package in Ubuntu: New Status in linux source package in Focal: Invalid Status in linux-signed-oem-5.6 source package in Focal: Confirmed Status in linux source package in Groovy: Confirmed Status in linux-signed-oem-5.6 source package in Groovy: Invalid Bug description: Issue found on Focal 5.6.0-1011.11-oem ubuntu@rizzo:~/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net$ sudo ./icmp_redirect.sh ### Legacy routing ### TEST: IPv4: redirect exception [ OK ] TEST: IPv6: redirect exception [ OK ] TEST: IPv4: redirect exception plus mtu [ OK ] TEST: IPv6: redirect exception plus mtu [ OK ] TEST: IPv4: routing reset [ OK ] TEST: IPv6: routing reset [ OK ] TEST: IPv4: mtu exception [ OK ] TEST: IPv6: mtu exception [ OK ] TEST: IPv4: mtu exception plus redirect [ OK ] TEST: IPv6: mtu exception plus redirect [FAIL] ### Legacy routing with VRF ### TEST: IPv4: redirect exception [ OK ] TEST: IPv6: redirect exception [ OK ] TEST: IPv4: redirect exception plus mtu [ OK ] TEST: IPv6: redirect exception plus mtu [ OK ] TEST: IPv4: routing reset [ OK ] TEST: IPv6: routing reset [ OK ] TEST: IPv4: mtu exception [ OK ] TEST: IPv6: mtu exception [ OK ] TEST: IPv4: mtu exception plus redirect [ OK ] TEST: IPv6: mtu exception plus redirect [FAIL] ### Routing with nexthop objects ### TEST: IPv4: redirect exception [ OK ] TEST: IPv6: redirect exception [ OK ] TEST: IPv4: redirect exception plus mtu [ OK ] TEST: IPv6: redirect exception plus mtu [ OK ] TEST: IPv4: routing reset [ OK ] TEST: IPv6: routing reset [ OK ] TEST: IPv4: mtu exception [ OK ] TEST: IPv6: mtu exception [ OK ] TEST: IPv4: mtu exception plus redirect [ OK ] TEST: IPv6: mtu exception plus redirect [FAIL] ### Routing with nexthop objects and VRF ### TEST: IPv4: redirect exception [ OK ] TEST: IPv6: redirect exception [ OK ] TEST: IPv4: redirect exception plus mtu [ OK ] TEST: IPv6: redirect exception plus mtu [ OK ] TEST: IPv4: routing reset [ OK ] TEST: IPv6: routing reset [ OK ] TEST: IPv4: mtu exception