[Kernel-packages] [Bug 1948807] Re: Boot time from snap in 20/stable increases boot time on 3.5 seconds
This bug was fixed in the package linux-raspi-5.4 - 5.4.0-1052.58~18.04.1 --- linux-raspi-5.4 (5.4.0-1052.58~18.04.1) bionic; urgency=medium * bionic/linux-raspi-5.4: 5.4.0-1052.58~18.04.1 -proposed tracker (LP: #1959810) * Boot time from snap in 20/stable increases boot time on 3.5 seconds (LP: #1948807) - [Config] raspi-bionic: Set BLK_DEV_LOOP_MIN_COUNT=8 [ Ubuntu: 5.4.0-1052.58 ] * focal/linux-raspi: 5.4.0-1052.58 -proposed tracker (LP: #1959811) * Boot time from snap in 20/stable increases boot time on 3.5 seconds (LP: #1948807) - [Config] raspi: Set BLK_DEV_LOOP_MIN_COUNT=8 * Missing overlays/README (LP: #1954757) - SAUCE: Install overlays/README * focal/linux: 5.4.0-99.112 -proposed tracker (LP: #1959817) * linux-image-5.4.0-97.110 freezes by accessing cifs shares (LP: #1959665) - Revert "cifs: To match file servers, make sure the server hostname matches" - Revert "cifs: set a minimum of 120s for next dns resolution" - Revert "cifs: use the expiry output of dns_query to schedule next resolution" * icmp_redirect from selftests fails on F/kvm (unary operator expected) (LP: #1938964) - selftests: icmp_redirect: pass xfail=0 to log_test() * Focal: CIFS stable updates (LP: #1954926) - cifs: use the expiry output of dns_query to schedule next resolution - cifs: set a minimum of 120s for next dns resolution - cifs: To match file servers, make sure the server hostname matches * seccomp_bpf in seccomp from ubuntu_kernel_selftests failed to build on B-5.4 (LP: #1896420) - SAUCE: selftests/seccomp: fix "storage size of 'md' isn't known" build issue - SAUCE: selftests/seccomp: Fix s390x regs not defined issue * system crash when removing ipmi_msghandler module (LP: #1950666) - ipmi: Move remove_work to dedicated workqueue - ipmi: msghandler: Make symbol 'remove_work_wq' static * zcrypt DD: Toleration for new IBM Z Crypto Hardware - (Backport to Ubuntu 20.04) (LP: #1954680) - s390/AP: support new dynamic AP bus size limit * [UBUNTU 20.04] KVM hardware diagnose data improvements for guest kernel - kernel part (LP: #1953334) - s390/setup: diag 318: refactor struct - s390/kvm: diagnose 0x318 sync and reset - KVM: s390: remove diag318 reset code - KVM: s390: add debug statement for diag 318 CPNC data * Updates to ib_peer_memory requested by Nvidia (LP: #1947206) - SAUCE: RDMA/core: Updated ib_peer_memory * Include Infiniband Peer Memory interface (LP: #1923104) - IB: Allow calls to ib_umem_get from kernel ULPs - SAUCE: RDMA/core: Introduce peer memory interface * Focal update: v5.4.162 upstream stable release (LP: #1954834) - arm64: zynqmp: Do not duplicate flash partition label property - arm64: zynqmp: Fix serial compatible string - ARM: dts: NSP: Fix mpcore, mmc node names - scsi: lpfc: Fix list_add() corruption in lpfc_drain_txq() - arm64: dts: hisilicon: fix arm,sp805 compatible string - RDMA/bnxt_re: Check if the vlan is valid before reporting - usb: musb: tusb6010: check return value after calling platform_get_resource() - usb: typec: tipd: Remove WARN_ON in tps6598x_block_read - arm64: dts: qcom: msm8998: Fix CPU/L2 idle state latency and residency - arm64: dts: freescale: fix arm,sp805 compatible string - ASoC: SOF: Intel: hda-dai: fix potential locking issue - clk: imx: imx6ul: Move csi_sel mux to correct base register - ASoC: nau8824: Add DMI quirk mechanism for active-high jack-detect - scsi: advansys: Fix kernel pointer leak - firmware_loader: fix pre-allocated buf built-in firmware use - ARM: dts: omap: fix gpmc,mux-add-data type - usb: host: ohci-tmio: check return value after calling platform_get_resource() - ARM: dts: ls1021a: move thermal-zones node out of soc/ - ARM: dts: ls1021a-tsn: use generic "jedec,spi-nor" compatible for flash - ALSA: ISA: not for M68K - tty: tty_buffer: Fix the softlockup issue in flush_to_ldisc - MIPS: sni: Fix the build - scsi: target: Fix ordered tag handling - scsi: target: Fix alua_tg_pt_gps_count tracking - iio: imu: st_lsm6dsx: Avoid potential array overflow in st_lsm6dsx_set_odr() - powerpc/5200: dts: fix memory node unit name - ALSA: gus: fix null pointer dereference on pointer block - powerpc/dcr: Use cmplwi instead of 3-argument cmpli - sh: check return code of request_irq - maple: fix wrong return value of maple_bus_init(). - f2fs: fix up f2fs_lookup tracepoints - sh: fix kconfig unmet dependency warning for FRAME_POINTER - sh: math-emu: drop unused functions - sh: define __BIG_ENDIAN for math-emu - clk: ingenic: Fix bugs with divided dividers - clk/ast2600: Fix soc revision for AHB - clk: qcom: gcc-msm8996: Drop (again) gcc_aggre1_pnoc_ahb_clk - mips: BCM63XX: ensure that CPU_SUPPORTS_32BIT_KERNEL is set - sched/core: Mitig
[Kernel-packages] [Bug 1947311] Re: Unexpected partition growth on first boot on impish for raspberry pi
I tried this again on the latest Raspberry Pi daily for Jammy, downloaded from here today (20210216): https://cdimage.ubuntu.com/ubuntu-server/daily-preinstalled/current/jammy-preinstalled-server-arm64+raspi.img.xz The issue persists. Can anyone suggest how I can get this assigned to the right project? I'm trying ubuntu-image as a target, as I think that's how the raspberry pi images are generated? Sorry if it's the wrong package. ** Also affects: ubuntu-image (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi in Ubuntu. https://bugs.launchpad.net/bugs/1947311 Title: Unexpected partition growth on first boot on impish for raspberry pi Status in cloud-init package in Ubuntu: Incomplete Status in linux-raspi package in Ubuntu: Invalid Status in ubuntu-image package in Ubuntu: New Bug description: Hi, On Raspberry Pi since Impish, the partition always grows even if I set the following in user-data of cloud-init. growpart: mode: off devices: ['/'] I have tested this on 21.04, and it works, but is broken on 21.10. (partition always grows) I've also tested this in KVM on amd64, and it works (partition does NOT grow). This is a problem for me because I am using runcmd in cloud init to migrate my drive to LVM/LUKS, and the partitioning step fails because the drive is already full. Cheers, Noah To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1947311/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1960865] Re: System freeze when plugging USB-C monitor into a hybrid Intel/Nvidia laptop: [drm:__nv_drm_gem_nvkms_memory_prime_get_sg_table [nvidia_drm]] *ERROR* [nvidia-drm] [G
This sounds like a simple bug in nvidia-drm-470 or kernel 5.13. Both have been upgraded in Ubuntu 22.04 already so there's a chance this issue is already fixed. Still, please follow the instruction in comment #7 because I would like to understand more about the system. ** Changed in: mutter (Ubuntu) Status: Confirmed => Opinion -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-470 in Ubuntu. https://bugs.launchpad.net/bugs/1960865 Title: System freeze when plugging USB-C monitor into a hybrid Intel/Nvidia laptop: [drm:__nv_drm_gem_nvkms_memory_prime_get_sg_table [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x0100] Failed to get memory pages for NvKmsKapiMemory Status in Mutter: Unknown Status in linux package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Opinion Status in nvidia-graphics-drivers-470 package in Ubuntu: Confirmed Bug description: I recently upgraded my NVidia drivers on my ThinkPad P1 Gen 3. If I start Ubuntu on Wayland session and plug in my USB-C monitor the system reliably completely freeze. The freeze is also reproducible if the screen is plugged in during startup and trying to login into a Wayland session. Only Wayland session experiences a crash. The crash happens ONLY if the USB-C monitor is plugged in. USB-C monitor is also a USB3 hub. Hardware seems to work fine, as Windows shows no issues with the setup. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: xorg 1:7.7+22ubuntu2 ProcVersionSignature: Ubuntu 5.13.0-30.33-generic 5.13.19 Uname: Linux 5.13.0-30-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 470.103.01 Thu Jan 6 12:10:04 UTC 2022 GCC version: gcc version 11.2.0 (Ubuntu 11.2.0-7ubuntu2) ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Feb 14 16:39:34 2022 DistUpgraded: 2021-10-14 18:36:11,564 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: impish DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GpuHangFrequency: Continuously GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Within the last few days GraphicsCard: Intel Corporation CometLake-H GT2 [UHD Graphics] [8086:9bc4] (rev 05) (prog-if 00 [VGA controller]) Subsystem: Lenovo CometLake-H GT2 [UHD Graphics] [17aa:22c1] NVIDIA Corporation TU117GLM [Quadro T1000 Mobile] [10de:1fb9] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Lenovo TU117GLM [Quadro T1000 Mobile] [17aa:22c1] InstallationDate: Installed on 2020-10-05 (497 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: LENOVO 20THCT01WW ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-30-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: Upgraded to impish on 2021-10-14 (122 days ago) dmi.bios.date: 12/27/2021 dmi.bios.release: 1.21 dmi.bios.vendor: LENOVO dmi.bios.version: N2VET36W (1.21 ) dmi.board.asset.tag: Not Available dmi.board.name: 20THCT01WW dmi.board.vendor: LENOVO dmi.board.version: 0B98417 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.10 dmi.modalias: dmi:bvnLENOVO:bvrN2VET36W(1.21):bd12/27/2021:br1.21:efr1.10:svnLENOVO:pn20THCT01WW:pvrThinkPadP1Gen3:rvnLENOVO:rn20THCT01WW:rvr0B98417WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20TH_BU_Think_FM_ThinkPadP1Gen3: dmi.product.family: ThinkPad P1 Gen 3 dmi.product.name: 20THCT01WW dmi.product.sku: LENOVO_MT_20TH_BU_Think_FM_ThinkPad P1 Gen 3 dmi.product.version: ThinkPad P1 Gen 3 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-8ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1 version.libgl1-mesa-glx: libgl1-mesa-glx 21.2.6-0ubuntu0.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1.1 version.xserver-xo
[Kernel-packages] [Bug 1937295] Re: PCI: vmd: Do not disable MSI-X remapping if interrupt remapping is enabled by IOMMU
** Changed in: linux (Ubuntu Bionic)
Status: Incomplete => Invalid
** Changed in: linux (Ubuntu Focal)
Status: Incomplete => In Progress
** Changed in: linux (Ubuntu Impish)
Status: Incomplete => In Progress
** Changed in: linux (Ubuntu Jammy)
Status: Incomplete => In Progress
** Changed in: linux (Ubuntu Focal)
Assignee: (unassigned) => Jeff Lane (bladernr)
** Changed in: linux (Ubuntu Impish)
Assignee: (unassigned) => Jeff Lane (bladernr)
** Changed in: linux (Ubuntu Jammy)
Assignee: (unassigned) => Jeff Lane (bladernr)
** Changed in: linux (Ubuntu Jammy)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu Impish)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu Focal)
Importance: Undecided => Medium
** Description changed:
+ [Impact]
+
+ A hardware partner discovered they were unable to install Ubuntu on some
+ servers using VROC setups. They point to this issue involving DMAR that
+ is blocking discovery of the VROC RAID devices:
+
+
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=2565e5b69c44b4e42469afea3cc5a97e74d1ed45
+
+ `git bisect` points to this offending commit ee81ee84f873 ("PCI:
+ vmd: Disable MSI-X remapping when possible"), which disables VMD MSI
+ remapping. The IOMMU hardware blocks the compatibility format
+ interrupt request because Interrupt Remapping Enable Status (IRES) and
+ Extended Interrupt Mode Enable (EIME) are enabled. Please refer to
+ section "5.1.4 Interrupt-Remapping Hardware Operation" in Intel VT-d
+ spec.
+
+ To fix the issue, VMD driver still enables the interrupt remapping
+ irrespective of VMD_FEAT_CAN_BYPASS_MSI_REMAP if the IOMMU subsystem
+ enables the interrupt remapping.
+
+ [Fix]
+
+ 2565e5b69c44 PCI: vmd: Do not disable MSI-X remapping if interrupt
+ remapping is enabled by IOMMU
+
+ [Test Plan]
+
+ 1. Boot into VRoC controller in uEFI Setup and create a raid10 disk.
+ 2. Install affected Ubuntu release on the RAID10.
+ 3. The system hangs at "Partitions formatting 33%".
+
+ [Where problems could occur]
+
+ The fix itself is a very small change to drivers/pci/controller/vmd.c
+ and problems should not occur, the patch has been tested and accepted
+ upstream as of 5.16.
+
+ That said, I doubt this will fix 18.04.6 as it would require a respin to
+ get the patched kernel onto the ISO. 20.04 should pick it up in ISO in
+ 20.04.5, so there could still be the initial issue since those ISOs
+ would be lacking the patched kernel.
+
+ [Other Info]
+
+ As noted, this would need to not only land in the kernel but land in the
+ kernel in the ISO to resolve the issue in the installation process.
+ I'll bring this back as far as Focal with the expectation that while
+ 20.04.4 is too late, it will be present using the GA kernel in 20.04.5
+ later on.
+
+
+ *
+
+
+ Original Bug Summary:
+
A hardware partner has been testing 18.04 subiquity images on their
servers with VROC enabled and configured in a RAID 10 setup.
-
In their own words:
Steps to reproduce:
- 1. Boot into VRoC controller in uEFI Setup and create a raid10 disk.
+ 1. Boot into VRoC controller in uEFI Setup and create a raid10 disk.
- 2. Install Ubuntu 18.04.5 on the RAID10.
+ 2. Install Ubuntu 18.04.5 on the RAID10.
- 3. The system hangs at "Partitions formatting 33%".
-
+ 3. The system hangs at "Partitions formatting 33%".
After looking at the launchpad
(https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1896578/), the fix
was included in the updated kernel.
-[Quotes from the launchpad]
+ [Quotes from the launchpad]
- The released kernels are:
+ The released kernels are:
- Hirsute: 5.11.0-22-generic
- Groovy: 5.8.0-59-generic
- Focal: 5.4.0-77-generic
- Bionic: 4.15.0-147-generic
+ Hirsute: 5.11.0-22-generic
+ Groovy: 5.8.0-59-generic
+ Focal: 5.4.0-77-generic
+ Bionic: 4.15.0-147-generic
-
-
- I've asked them to also confirm this on 20.04.2, and check that 20.04.3
dailies fix the issue.
+ I've asked them to also confirm this on 20.04.2, and check that 20.04.3
+ dailies fix the issue.
It is at least a very reasonable hypothesis that this will also break on
all current ISO installs as none of them are respun once released to
include updated SRUs in the installation media. This currently affects
20.04.2 but that will be resolved shortly when 20.04.3 releases as the
GA and HWE kernels in that image should have the SRU that fixes this
issue. However, 18.04 has no further releases, and even the 18.04.5
daily-live and daily images on cdimages.ubuntu.com are not built after
18.04.5 was released.
** Description changed:
[Impact]
A hardware partner discovered they were unabl
[Kernel-packages] [Bug 1937295] Re: Installation hangs on VROC systems during Bionic installsPCI: vmd: Do not disable MSI-X remapping if interrupt remapping is enabled by IOMMU
** Summary changed: - Installation hangs on VROC systems during Bionic installs + Installation hangs on VROC systems during Bionic installsPCI: vmd: Do not disable MSI-X remapping if interrupt remapping is enabled by IOMMU ** Summary changed: - Installation hangs on VROC systems during Bionic installsPCI: vmd: Do not disable MSI-X remapping if interrupt remapping is enabled by IOMMU + PCI: vmd: Do not disable MSI-X remapping if interrupt remapping is enabled by IOMMU -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1937295 Title: PCI: vmd: Do not disable MSI-X remapping if interrupt remapping is enabled by IOMMU Status in subiquity: Incomplete Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: Incomplete Status in linux source package in Focal: Incomplete Status in linux source package in Impish: Incomplete Status in linux source package in Jammy: Incomplete Bug description: A hardware partner has been testing 18.04 subiquity images on their servers with VROC enabled and configured in a RAID 10 setup. In their own words: Steps to reproduce: 1. Boot into VRoC controller in uEFI Setup and create a raid10 disk. 2. Install Ubuntu 18.04.5 on the RAID10. 3. The system hangs at "Partitions formatting 33%". After looking at the launchpad (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1896578/), the fix was included in the updated kernel. [Quotes from the launchpad] The released kernels are: Hirsute: 5.11.0-22-generic Groovy: 5.8.0-59-generic Focal: 5.4.0-77-generic Bionic: 4.15.0-147-generic I've asked them to also confirm this on 20.04.2, and check that 20.04.3 dailies fix the issue. It is at least a very reasonable hypothesis that this will also break on all current ISO installs as none of them are respun once released to include updated SRUs in the installation media. This currently affects 20.04.2 but that will be resolved shortly when 20.04.3 releases as the GA and HWE kernels in that image should have the SRU that fixes this issue. However, 18.04 has no further releases, and even the 18.04.5 daily-live and daily images on cdimages.ubuntu.com are not built after 18.04.5 was released. To manage notifications about this bug go to: https://bugs.launchpad.net/subiquity/+bug/1937295/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1960865] Re: System freeze when plugging USB-C monitor into a hybrid Intel/Nvidia laptop: [drm:__nv_drm_gem_nvkms_memory_prime_get_sg_table [nvidia_drm]] *ERROR* [nvidia-drm] [G
The strange thing to me is that Nvidia shouldn't be involved here. A USB-C port is likely to be wired to the Intel chips only. As a DisplayPort the USB-C is wired to the Intel GPU. And gnome-shell by default will use the integrated Intel GPU only for the desktop. Please reproduce the freeze again, then reboot and run: journalctl -b-1 > prevboot.txt and attach the resulting text file here. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-470 in Ubuntu. https://bugs.launchpad.net/bugs/1960865 Title: System freeze when plugging USB-C monitor into a hybrid Intel/Nvidia laptop: [drm:__nv_drm_gem_nvkms_memory_prime_get_sg_table [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x0100] Failed to get memory pages for NvKmsKapiMemory Status in Mutter: Unknown Status in linux package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-470 package in Ubuntu: Confirmed Bug description: I recently upgraded my NVidia drivers on my ThinkPad P1 Gen 3. If I start Ubuntu on Wayland session and plug in my USB-C monitor the system reliably completely freeze. The freeze is also reproducible if the screen is plugged in during startup and trying to login into a Wayland session. Only Wayland session experiences a crash. The crash happens ONLY if the USB-C monitor is plugged in. USB-C monitor is also a USB3 hub. Hardware seems to work fine, as Windows shows no issues with the setup. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: xorg 1:7.7+22ubuntu2 ProcVersionSignature: Ubuntu 5.13.0-30.33-generic 5.13.19 Uname: Linux 5.13.0-30-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 470.103.01 Thu Jan 6 12:10:04 UTC 2022 GCC version: gcc version 11.2.0 (Ubuntu 11.2.0-7ubuntu2) ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Feb 14 16:39:34 2022 DistUpgraded: 2021-10-14 18:36:11,564 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: impish DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GpuHangFrequency: Continuously GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Within the last few days GraphicsCard: Intel Corporation CometLake-H GT2 [UHD Graphics] [8086:9bc4] (rev 05) (prog-if 00 [VGA controller]) Subsystem: Lenovo CometLake-H GT2 [UHD Graphics] [17aa:22c1] NVIDIA Corporation TU117GLM [Quadro T1000 Mobile] [10de:1fb9] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Lenovo TU117GLM [Quadro T1000 Mobile] [17aa:22c1] InstallationDate: Installed on 2020-10-05 (497 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: LENOVO 20THCT01WW ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-30-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: Upgraded to impish on 2021-10-14 (122 days ago) dmi.bios.date: 12/27/2021 dmi.bios.release: 1.21 dmi.bios.vendor: LENOVO dmi.bios.version: N2VET36W (1.21 ) dmi.board.asset.tag: Not Available dmi.board.name: 20THCT01WW dmi.board.vendor: LENOVO dmi.board.version: 0B98417 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.10 dmi.modalias: dmi:bvnLENOVO:bvrN2VET36W(1.21):bd12/27/2021:br1.21:efr1.10:svnLENOVO:pn20THCT01WW:pvrThinkPadP1Gen3:rvnLENOVO:rn20THCT01WW:rvr0B98417WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20TH_BU_Think_FM_ThinkPadP1Gen3: dmi.product.family: ThinkPad P1 Gen 3 dmi.product.name: 20THCT01WW dmi.product.sku: LENOVO_MT_20TH_BU_Think_FM_ThinkPad P1 Gen 3 dmi.product.version: ThinkPad P1 Gen 3 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-8ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1 version.libgl1-mesa-glx: libgl1-mesa-glx 21.2.6-0ubuntu0.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core:
[Kernel-packages] [Bug 1952403] Re: Laptop discharged while in sleep breaks Realtek 8822CE wireless card and USB type C on Asus TUF FA506IV
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]
** Changed in: linux (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1952403
Title:
Laptop discharged while in sleep breaks Realtek 8822CE wireless card
and USB type C on Asus TUF FA506IV
Status in linux package in Ubuntu:
Expired
Bug description:
I own an Asus TUF A15 FA506IV laptop with Ubuntu 21.10. After putting
it to sleep it discharged. Turning it back on the Wireless cards
doesn't work.
This is what I found in the logs that could help:
Nov 24 15:25:56 Zveri2 krunner[16146]: [11/24/21, 15:25:56:311] info: Store:
POWER_RESUMED
Nov 24 15:25:56 Zveri2 krunner[16146]: [11/24/21, 15:25:56:312] info: Store:
SET_SUSPEND_STATUS true
Nov 24 15:25:56 Zveri2 krunner[16146]: [11/24/21, 15:25:56:313] info:
[DESKTOP-SIDE-EFFECT] Update from desktop for keys ["app"]
Nov 24 15:25:56 Zveri2 kernel: [21587.358139] rtw_8822ce :03:00.0: start
vif 80:30:49:cc:98:0f on port 0
Nov 24 15:25:56 Zveri2 charon: 01[KNL] interface wlp3s0 activated
Nov 24 15:25:56 Zveri2 NetworkManager[1059]: [1637760356.4839]
manager: NetworkManager state is now CONNECTED_LOCAL
Nov 24 15:25:56 Zveri2 krunner[16146]: [11/24/21, 15:25:56:489] info:
NetworkStatus: Network check failed {
Nov 24 15:25:56 Zveri2 krunner[16146]: "error": "Failed to fetch"
Nov 24 15:25:56 Zveri2 krunner[16146]: }
Nov 24 15:25:56 Zveri2 krunner[16146]: [11/24/21, 15:25:56:490] info: Network
status check {
Nov 24 15:25:56 Zveri2 krunner[16146]: "elapsed_time_ms": 999784,
Nov 24 15:25:56 Zveri2 krunner[16146]: "navigator_online": false,
Nov 24 15:25:56 Zveri2 krunner[16146]: "api_test": "offline"
Nov 24 15:25:56 Zveri2 krunner[16146]: }
After this I am getting the following trace:
Nov 24 15:26:05 Zveri2 kernel: [21596.291200] rtw_8822ce :03:00.0: timed
out to flush pci tx ring[0]
Nov 24 15:26:05 Zveri2 kernel: [21596.291287] rtw_8822ce :03:00.0: timed
out to flush pci tx ring[1]
Nov 24 15:26:05 Zveri2 kernel: [21596.291365] rtw_8822ce :03:00.0: timed
out to flush pci tx ring[2]
Nov 24 15:26:05 Zveri2 kernel: [21596.291484] rtw_8822ce :03:00.0: timed
out to flush pci tx ring[3]
Nov 24 15:26:05 Zveri2 kernel: [21596.291570] rtw_8822ce :03:00.0: timed
out to flush pci tx ring[5]
Nov 24 15:26:05 Zveri2 kernel: [21596.291651] rtw_8822ce :03:00.0: timed
out to flush pci tx ring[6]
Nov 24 15:26:06 Zveri2 krunner[16146]: [11/24/21, 15:26:06:125] info:
[NETWORK-CONNECTIVITY] Failed to establish a connection after 10 attempt(s).
Nov 24 15:26:07 Zveri2 kernel: [21598.291806] rtw_8822ce :03:00.0: failed
to poll offset=0x5 mask=0x2 value=0x0
Nov 24 15:26:07 Zveri2 kernel: [21598.292047] [ cut here
]
Nov 24 15:26:07 Zveri2 kernel: [21598.292049] failed to read DBI register,
addr=0x0719
Nov 24 15:26:07 Zveri2 kernel: [21598.292082] WARNING: CPU: 2 PID: 17826 at
drivers/net/wireless/realtek/rtw88/pci.c:1310 rtw_dbi_read8.constprop.0+0x
aa/0xc0 [rtw88_pci]
Nov 24 15:26:07 Zveri2 kernel: [21598.292096] Modules linked in:
nf_conntrack_netlink xt_addrtype br_netfilter vboxnetadp(OE) vboxnetflt(OE)
xfrm_user
xfrm_algo vboxdrv(OE) rfcomm xt_CHECKSUM xt_MASQUERADE xt_conntrack
ipt_REJECT nf_reject_ipv4 xt_tcpudp nft_compat nft_chain_nat nf_nat nf_conntrack
nf_defrag_ipv6 nf_defrag_ipv4 nft_counter nf_tables nfnetlink bridge stp llc
cmac algif_hash algif_skcipher overlay af_alg bnep binfmt_misc zfs(PO) zu
nicode(PO) zzstd(O) zlua(O) zavl(PO) icp(PO) zcommon(PO) znvpair(PO) spl(O)
intel_rapl_msr intel_rapl_common joydev snd_hda_codec_realtek snd_hda_code
c_generic ledtrig_audio snd_hda_codec_hdmi snd_hda_intel edac_mce_amd
snd_intel_dspcfg snd_intel_sdw_acpi uvcvideo snd_hda_codec rtw88_8822ce rtw88_88
22c videobuf2_vmalloc snd_hda_core kvm_amd snd_hwdep rtw88_pci btusb
videobuf2_memops snd_pcm btrtl rtw88_core videobuf2_v4l2 btbcm videobuf2_common
k
vm btintel snd_seq_midi bluetooth videodev snd_seq_midi_event ecdh_generic
nls_iso8859_1 mc mac80211 rapl ecc snd_rawmidi input_leds
Nov 24 15:26:07 Zveri2 kernel: [21598.292174] serio_raw efi_pstore wmi_bmof
hid_multitouch snd_seq k10temp snd_seq_device cfg80211 snd_timer ucsi_ccg
snd snd_rn_pci_acp3x libarc4 ccp snd_pci_acp3x soundcore ucsi_acpi
typec_ucsi typec asus_wireless mac_hid nvidia_uvm(POE) sch_fq_codel msr
parport_pc ppdev lp parport ip_tables x_tables autofs4 btrfs blake2b_generic
xor zstd_compress raid6_pq libcrc32c dm_crypt hid_logitech_hidpp
hid_logitech_dj nvidia_drm(POE) nvidia_modeset(POE) usbhid nvidia(POE)
hid_generic amdgpu mfd_aaeon asus_wmi sparse_keymap iommu_v2 gpu_sched
i2c_algo_bit drm_ttm_helper ttm drm_kms_helper crct10dif_pclmul crc32_pclmul
syscopyarea ghash_clmulni_intel sysfillrect sysimgblt fb_sy
[Kernel-packages] [Bug 1960083] Re: dirname applet missing from initramfs
Downloaded the iso today doesn't mean the iso was built today, or if it contains this update. jammy installer iso are attempted to be built daily, but are only published once they pass automated smoke testing and validation. The last image that passed that was built on 2nd of February. And builds since then have been failing validation are probably toast. You can try a /pending/ image to see if this bug is fixed, but please be aware it has been failing automated testing thus it may have other issues. -- 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/1960083 Title: dirname applet missing from initramfs Status in busybox package in Ubuntu: Fix Released Status in zfs-linux package in Ubuntu: Confirmed Bug description: The initramfs is currently being built without the dirname applet. This is causing issues with zfs encrypted devices, as cryptsetup is attempting to use dirname to determine the location of the system key. This results in the following error: /init: line 971: dirname: not found followed by a prompt that is missing the zpool name. For example "Please unlock disk keystore-" rather than "Please unlock disk keystore-rpool". After entering the password, the user is dropped to an initramfs shell. It appears that this was caused by a change in cryptsetup to suddenly need dirname to function properly. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/busybox/+bug/1960083/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1957026] Re: AMD Yellow Carp DMCUB fw update for s0i3 B0 fixes
Verified linux-oem-5.14/focal-proposed version 5.14.0-1023 ** Changed in: linux-oem-5.14 (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-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1957026 Title: AMD Yellow Carp DMCUB fw update for s0i3 B0 fixes Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-firmware package in Ubuntu: Fix Released Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-firmware source package in Focal: Fix Released Status in linux-oem-5.14 source package in Focal: Fix Committed Status in linux source package in Jammy: In Progress Status in linux-firmware source package in Jammy: Fix Released Status in linux-oem-5.14 source package in Jammy: Invalid Bug description: [SRU Justification] [Impact] On AMD Yellow Carp B0 platforms, S0i3 is still not working. [Fix] This denpends on a few fixes for kernel driver that are all either in v5.17-rc1 or in stable linux-5.1x.y, along with an already upstreamed dmcub firmware. [Test Case] On AMD RMT CRB board, 1. apply both kernel and firmware fixes 2. module blacklist amd_sfh as it's still under development, 3. trigger system suspend. Use power button to wake up the device. 4. check /sys/kernel/debug/amd_pmc/s0ix_stats, the values shall be non-zero On without any of above, the board may not cut device power during suspend, and/or fail to resume and leaving a blank screen, and/or s0ix stats remain all zeros. [Where problems could occur] On AMD RMT CRB board, Sensor Fusion Hub (amd_sfh) still doesn't support S0ix and has to be disabled. For the kernel side, the driver fixes addressed a few procedure errors that should be unlikely to introduce regressions; for the firmware side, also tested loading new firmware on unpatched kernels and there is no difference found yet. [Other Info] For kernel driver fixes, patches for both oem-5.14 and jammy are necessary; for firmware, that has been available in jammy branch but not yet released, so only Focal will be nominated. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1957026/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1958850] Re: USB port lost function after unplugging usb drive
** Changed in: oem-priority Importance: Undecided => Critical -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1958850 Title: USB port lost function after unplugging usb drive Status in HWE Next: New Status in OEM Priority Project: New Status in linux package in Ubuntu: In Progress Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: New Status in linux-oem-5.14 source package in Focal: Fix Committed Status in linux source package in Jammy: In Progress Status in linux-oem-5.14 source package in Jammy: Invalid Bug description: [Impact] Test the proposed 5.14 oem kernel, and get a failure symptom. Unplug a usb drive from WD19TB docking and a BUG reported in kernel, then the other embedded usb port can't detect usb drive anymore after a while. kernel: usb 5-2.3.3: USB disconnect, device number 5 kernel: BUG: kernel NULL pointer dereference, address: 0030 kernel: #PF: supervisor read access in kernel mode kernel: #PF: error_code(0x) - not-present page kernel: PGD 0 P4D 0 kernel: Oops: [#1] SMP NOPTI [Fix] 2a19b28f7929) blk-mq: cancel blk-mq dispatch work... is the first regression and it lands mainline since v5.16-rc2. After applied https://lore.kernel.org/all/20210816134624.ga24...@lst.de/#r, issue is gone. the patches has beend landed since v5.15-rc1. [Test Case] 1. plug usb driver on the machine. 2. unplug usb driver. 3. check the dmesg if the oops would be shown [Where problems could occur] Medium ~~~ Test the proposed 5.14 oem kernel, and get a failure symptom. Unplug a usb drive from WD19TB docking and a BUG reported in kernel, then the other embedded usb port can't detect usb drive anymore after a while. kernel: usb 5-2.3.3: USB disconnect, device number 5 kernel: BUG: kernel NULL pointer dereference, address: 0030 kernel: #PF: supervisor read access in kernel mode kernel: #PF: error_code(0x) - not-present page kernel: PGD 0 P4D 0 kernel: Oops: [#1] SMP NOPTI --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: u 2205 F pulseaudio /dev/snd/controlC0: u 2205 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 21.10 InstallationDate: Installed on 2021-04-29 (270 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: Dell Inc. Precision 5750 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.14.0-1021-oem root=UUID=834a3a4a-65e5-44ed-8f1a-4bdd2df3cce2 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.14.0-1021.23-oem 5.14.21 RelatedPackageVersions: linux-restricted-modules-5.14.0-1021-oem N/A linux-backports-modules-5.14.0-1021-oem N/A linux-firmware 1.201.3 Tags: impish Uname: Linux 5.14.0-1021-oem x86_64 UpgradeStatus: Upgraded to impish on 2022-01-06 (18 days ago) UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/18/2021 dmi.bios.release: 1.11 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.11.1 dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.11.1:bd11/18/2021:br1.11:svnDellInc.:pnPrecision5750:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:sku0990: dmi.product.family: Precision dmi.product.name: Precision 5750 dmi.product.sku: 0990 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1958850/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1960865] Re: System freeze when plugging USB-C monitor into a hybrid Intel/Nvidia laptop: [drm:__nv_drm_gem_nvkms_memory_prime_get_sg_table [nvidia_drm]] *ERROR* [nvidia-drm] [G
** Also affects: nvidia-graphics-drivers-470 (Ubuntu) Importance: Undecided Status: New ** Changed in: nvidia-graphics-drivers-470 (Ubuntu) Importance: Undecided => High ** Changed in: nvidia-graphics-drivers-470 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-470 in Ubuntu. https://bugs.launchpad.net/bugs/1960865 Title: System freeze when plugging USB-C monitor into a hybrid Intel/Nvidia laptop: [drm:__nv_drm_gem_nvkms_memory_prime_get_sg_table [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x0100] Failed to get memory pages for NvKmsKapiMemory Status in Mutter: Unknown Status in linux package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-470 package in Ubuntu: Confirmed Bug description: I recently upgraded my NVidia drivers on my ThinkPad P1 Gen 3. If I start Ubuntu on Wayland session and plug in my USB-C monitor the system reliably completely freeze. The freeze is also reproducible if the screen is plugged in during startup and trying to login into a Wayland session. Only Wayland session experiences a crash. The crash happens ONLY if the USB-C monitor is plugged in. USB-C monitor is also a USB3 hub. Hardware seems to work fine, as Windows shows no issues with the setup. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: xorg 1:7.7+22ubuntu2 ProcVersionSignature: Ubuntu 5.13.0-30.33-generic 5.13.19 Uname: Linux 5.13.0-30-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 470.103.01 Thu Jan 6 12:10:04 UTC 2022 GCC version: gcc version 11.2.0 (Ubuntu 11.2.0-7ubuntu2) ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Feb 14 16:39:34 2022 DistUpgraded: 2021-10-14 18:36:11,564 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: impish DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GpuHangFrequency: Continuously GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Within the last few days GraphicsCard: Intel Corporation CometLake-H GT2 [UHD Graphics] [8086:9bc4] (rev 05) (prog-if 00 [VGA controller]) Subsystem: Lenovo CometLake-H GT2 [UHD Graphics] [17aa:22c1] NVIDIA Corporation TU117GLM [Quadro T1000 Mobile] [10de:1fb9] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Lenovo TU117GLM [Quadro T1000 Mobile] [17aa:22c1] InstallationDate: Installed on 2020-10-05 (497 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: LENOVO 20THCT01WW ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-30-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: Upgraded to impish on 2021-10-14 (122 days ago) dmi.bios.date: 12/27/2021 dmi.bios.release: 1.21 dmi.bios.vendor: LENOVO dmi.bios.version: N2VET36W (1.21 ) dmi.board.asset.tag: Not Available dmi.board.name: 20THCT01WW dmi.board.vendor: LENOVO dmi.board.version: 0B98417 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.10 dmi.modalias: dmi:bvnLENOVO:bvrN2VET36W(1.21):bd12/27/2021:br1.21:efr1.10:svnLENOVO:pn20THCT01WW:pvrThinkPadP1Gen3:rvnLENOVO:rn20THCT01WW:rvr0B98417WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20TH_BU_Think_FM_ThinkPadP1Gen3: dmi.product.family: ThinkPad P1 Gen 3 dmi.product.name: 20THCT01WW dmi.product.sku: LENOVO_MT_20TH_BU_Think_FM_ThinkPad P1 Gen 3 dmi.product.version: ThinkPad P1 Gen 3 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-8ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1 version.libgl1-mesa-glx: libgl1-mesa-glx 21.2.6-0ubuntu0.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-v
[Kernel-packages] [Bug 1960865] Re: System freeze when plugging USB-C monitor into a hybrid Intel/Nvidia laptop: [drm:__nv_drm_gem_nvkms_memory_prime_get_sg_table [nvidia_drm]] *ERROR* [nvidia-drm] [G
** Changed in: mutter (Ubuntu) Status: New => Confirmed ** Changed in: mutter (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1960865 Title: System freeze when plugging USB-C monitor into a hybrid Intel/Nvidia laptop: [drm:__nv_drm_gem_nvkms_memory_prime_get_sg_table [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x0100] Failed to get memory pages for NvKmsKapiMemory Status in Mutter: Unknown Status in linux package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-470 package in Ubuntu: Confirmed Bug description: I recently upgraded my NVidia drivers on my ThinkPad P1 Gen 3. If I start Ubuntu on Wayland session and plug in my USB-C monitor the system reliably completely freeze. The freeze is also reproducible if the screen is plugged in during startup and trying to login into a Wayland session. Only Wayland session experiences a crash. The crash happens ONLY if the USB-C monitor is plugged in. USB-C monitor is also a USB3 hub. Hardware seems to work fine, as Windows shows no issues with the setup. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: xorg 1:7.7+22ubuntu2 ProcVersionSignature: Ubuntu 5.13.0-30.33-generic 5.13.19 Uname: Linux 5.13.0-30-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 470.103.01 Thu Jan 6 12:10:04 UTC 2022 GCC version: gcc version 11.2.0 (Ubuntu 11.2.0-7ubuntu2) ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Feb 14 16:39:34 2022 DistUpgraded: 2021-10-14 18:36:11,564 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: impish DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GpuHangFrequency: Continuously GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Within the last few days GraphicsCard: Intel Corporation CometLake-H GT2 [UHD Graphics] [8086:9bc4] (rev 05) (prog-if 00 [VGA controller]) Subsystem: Lenovo CometLake-H GT2 [UHD Graphics] [17aa:22c1] NVIDIA Corporation TU117GLM [Quadro T1000 Mobile] [10de:1fb9] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Lenovo TU117GLM [Quadro T1000 Mobile] [17aa:22c1] InstallationDate: Installed on 2020-10-05 (497 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: LENOVO 20THCT01WW ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-30-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: Upgraded to impish on 2021-10-14 (122 days ago) dmi.bios.date: 12/27/2021 dmi.bios.release: 1.21 dmi.bios.vendor: LENOVO dmi.bios.version: N2VET36W (1.21 ) dmi.board.asset.tag: Not Available dmi.board.name: 20THCT01WW dmi.board.vendor: LENOVO dmi.board.version: 0B98417 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.10 dmi.modalias: dmi:bvnLENOVO:bvrN2VET36W(1.21):bd12/27/2021:br1.21:efr1.10:svnLENOVO:pn20THCT01WW:pvrThinkPadP1Gen3:rvnLENOVO:rn20THCT01WW:rvr0B98417WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20TH_BU_Think_FM_ThinkPadP1Gen3: dmi.product.family: ThinkPad P1 Gen 3 dmi.product.name: 20THCT01WW dmi.product.sku: LENOVO_MT_20TH_BU_Think_FM_ThinkPad P1 Gen 3 dmi.product.version: ThinkPad P1 Gen 3 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-8ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1 version.libgl1-mesa-glx: libgl1-mesa-glx 21.2.6-0ubuntu0.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu2 version.xserver-x
[Kernel-packages] [Bug 1960865] 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/1960865 Title: System freeze when plugging USB-C monitor into a hybrid Intel/Nvidia laptop: [drm:__nv_drm_gem_nvkms_memory_prime_get_sg_table [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x0100] Failed to get memory pages for NvKmsKapiMemory Status in Mutter: Unknown Status in linux package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: I recently upgraded my NVidia drivers on my ThinkPad P1 Gen 3. If I start Ubuntu on Wayland session and plug in my USB-C monitor the system reliably completely freeze. The freeze is also reproducible if the screen is plugged in during startup and trying to login into a Wayland session. Only Wayland session experiences a crash. The crash happens ONLY if the USB-C monitor is plugged in. USB-C monitor is also a USB3 hub. Hardware seems to work fine, as Windows shows no issues with the setup. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: xorg 1:7.7+22ubuntu2 ProcVersionSignature: Ubuntu 5.13.0-30.33-generic 5.13.19 Uname: Linux 5.13.0-30-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 470.103.01 Thu Jan 6 12:10:04 UTC 2022 GCC version: gcc version 11.2.0 (Ubuntu 11.2.0-7ubuntu2) ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Feb 14 16:39:34 2022 DistUpgraded: 2021-10-14 18:36:11,564 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: impish DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GpuHangFrequency: Continuously GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Within the last few days GraphicsCard: Intel Corporation CometLake-H GT2 [UHD Graphics] [8086:9bc4] (rev 05) (prog-if 00 [VGA controller]) Subsystem: Lenovo CometLake-H GT2 [UHD Graphics] [17aa:22c1] NVIDIA Corporation TU117GLM [Quadro T1000 Mobile] [10de:1fb9] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Lenovo TU117GLM [Quadro T1000 Mobile] [17aa:22c1] InstallationDate: Installed on 2020-10-05 (497 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: LENOVO 20THCT01WW ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-30-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: Upgraded to impish on 2021-10-14 (122 days ago) dmi.bios.date: 12/27/2021 dmi.bios.release: 1.21 dmi.bios.vendor: LENOVO dmi.bios.version: N2VET36W (1.21 ) dmi.board.asset.tag: Not Available dmi.board.name: 20THCT01WW dmi.board.vendor: LENOVO dmi.board.version: 0B98417 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.10 dmi.modalias: dmi:bvnLENOVO:bvrN2VET36W(1.21):bd12/27/2021:br1.21:efr1.10:svnLENOVO:pn20THCT01WW:pvrThinkPadP1Gen3:rvnLENOVO:rn20THCT01WW:rvr0B98417WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20TH_BU_Think_FM_ThinkPadP1Gen3: dmi.product.family: ThinkPad P1 Gen 3 dmi.product.name: 20THCT01WW dmi.product.sku: LENOVO_MT_20TH_BU_Think_FM_ThinkPad P1 Gen 3 dmi.product.version: ThinkPad P1 Gen 3 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-8ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1 version.libgl1-mesa-glx: libgl1-mesa-glx 21.2.6-0ubuntu0.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1build1 To manage notifications about this bug
[Kernel-packages] [Bug 1960865] Re: System freeze when plugging USB-C monitor into a hybrid Intel/Nvidia laptop: [drm:__nv_drm_gem_nvkms_memory_prime_get_sg_table [nvidia_drm]] *ERROR* [nvidia-drm] [G
Also tracking in https://gitlab.gnome.org/GNOME/mutter/-/issues/1891 ** Also affects: mutter (Ubuntu) Importance: Undecided Status: New ** Also affects: mutter via https://gitlab.gnome.org/GNOME/mutter/-/issues/1891 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/1960865 Title: System freeze when plugging USB-C monitor into a hybrid Intel/Nvidia laptop: [drm:__nv_drm_gem_nvkms_memory_prime_get_sg_table [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x0100] Failed to get memory pages for NvKmsKapiMemory Status in Mutter: Unknown Status in linux package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: I recently upgraded my NVidia drivers on my ThinkPad P1 Gen 3. If I start Ubuntu on Wayland session and plug in my USB-C monitor the system reliably completely freeze. The freeze is also reproducible if the screen is plugged in during startup and trying to login into a Wayland session. Only Wayland session experiences a crash. The crash happens ONLY if the USB-C monitor is plugged in. USB-C monitor is also a USB3 hub. Hardware seems to work fine, as Windows shows no issues with the setup. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: xorg 1:7.7+22ubuntu2 ProcVersionSignature: Ubuntu 5.13.0-30.33-generic 5.13.19 Uname: Linux 5.13.0-30-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 470.103.01 Thu Jan 6 12:10:04 UTC 2022 GCC version: gcc version 11.2.0 (Ubuntu 11.2.0-7ubuntu2) ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Feb 14 16:39:34 2022 DistUpgraded: 2021-10-14 18:36:11,564 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: impish DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GpuHangFrequency: Continuously GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Within the last few days GraphicsCard: Intel Corporation CometLake-H GT2 [UHD Graphics] [8086:9bc4] (rev 05) (prog-if 00 [VGA controller]) Subsystem: Lenovo CometLake-H GT2 [UHD Graphics] [17aa:22c1] NVIDIA Corporation TU117GLM [Quadro T1000 Mobile] [10de:1fb9] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Lenovo TU117GLM [Quadro T1000 Mobile] [17aa:22c1] InstallationDate: Installed on 2020-10-05 (497 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: LENOVO 20THCT01WW ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-30-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: Upgraded to impish on 2021-10-14 (122 days ago) dmi.bios.date: 12/27/2021 dmi.bios.release: 1.21 dmi.bios.vendor: LENOVO dmi.bios.version: N2VET36W (1.21 ) dmi.board.asset.tag: Not Available dmi.board.name: 20THCT01WW dmi.board.vendor: LENOVO dmi.board.version: 0B98417 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.10 dmi.modalias: dmi:bvnLENOVO:bvrN2VET36W(1.21):bd12/27/2021:br1.21:efr1.10:svnLENOVO:pn20THCT01WW:pvrThinkPadP1Gen3:rvnLENOVO:rn20THCT01WW:rvr0B98417WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20TH_BU_Think_FM_ThinkPadP1Gen3: dmi.product.family: ThinkPad P1 Gen 3 dmi.product.name: 20THCT01WW dmi.product.sku: LENOVO_MT_20TH_BU_Think_FM_ThinkPad P1 Gen 3 dmi.product.version: ThinkPad P1 Gen 3 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-8ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1 version.libgl1-mesa-glx: libgl1-mesa-glx 21.2.6-0ubuntu0.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build1 version.xserver-xorg-video-int
[Kernel-packages] [Bug 1960865] Re: System freeze
It looks like the main issue just before the zeros is a kernel crash: Feb 14 16:32:46 alex-power kernel: [ 67.119401] [drm:__nv_drm_gem_nvkms_memory_prime_get_sg_table [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x0100] Failed to get memory pages for NvKmsKapiMemory 0x76ba531b Feb 14 16:32:46 alex-power kernel: [ 67.119416] BUG: kernel NULL pointer dereference, address: 000c Feb 14 16:32:46 alex-power kernel: [ 67.119418] #PF: supervisor read access in kernel mode Feb 14 16:32:46 alex-power kernel: [ 67.119419] #PF: error_code(0x) - not-present page Feb 14 16:32:46 alex-power kernel: [ 67.119420] PGD 0 P4D 0 Feb 14 16:32:46 alex-power kernel: [ 67.119422] Oops: [#1] SMP NOPTI Feb 14 16:32:46 alex-power kernel: [ 67.119424] CPU: 3 PID: 4291 Comm: gnome-shell Tainted: P OE 5.13.0-30-generic #33-Ubuntu Feb 14 16:32:46 alex-power kernel: [ 67.119427] Hardware name: LENOVO 20THCT01WW/20THCT01WW, BIOS N2VET36W (1.21 ) 12/27/2021 Feb 14 16:32:46 alex-power kernel: [ 67.119428] RIP: 0010:drm_gem_map_dma_buf+0x43/0xb0 [drm] Feb 14 16:32:46 alex-power kernel: [ 67.119455] Code: 00 00 83 fe 03 74 6f 48 8b 87 40 01 00 00 48 8b 40 38 48 85 c0 74 72 41 89 f5 ff d0 0f 1f 00 49 89 c4 48 3d 00 f0 ff ff 77 21 <8b> 50 0c 48 8b 7b 08 41 b8 20 00 00 00 44 89 e9 48 8b 30 e8 55 ca Feb 14 16:32:46 alex-power kernel: [ 67.119457] RSP: 0018:b921c72838d8 EFLAGS: 00010207 Feb 14 16:32:46 alex-power kernel: [ 67.119458] RAX: RBX: 9799510f37e0 RCX: Feb 14 16:32:46 alex-power kernel: [ 67.119460] RDX: RSI: 979c0bfa09c0 RDI: 979c0bfa09c0 Feb 14 16:32:46 alex-power kernel: [ 67.119461] RBP: b921c72838f0 R08: R09: b921c7283610 Feb 14 16:32:46 alex-power kernel: [ 67.119462] R10: b921c7283608 R11: 92355428 R12: Feb 14 16:32:46 alex-power kernel: [ 67.119463] R13: R14: dfd20881 R15: 0800 Feb 14 16:32:46 alex-power kernel: [ 67.119464] FS: 7fe6b9d9bd80() GS:979c0bf8() knlGS: Feb 14 16:32:46 alex-power kernel: [ 67.119466] CS: 0010 DS: ES: CR0: 80050033 Feb 14 16:32:46 alex-power kernel: [ 67.119467] CR2: 000c CR3: 00011cbae002 CR4: 007706e0 Feb 14 16:32:46 alex-power kernel: [ 67.119468] PKRU: 5554 Feb 14 16:32:46 alex-power kernel: [ 67.119469] Call Trace: Feb 14 16:32:46 alex-power kernel: [ 67.119470] Feb 14 16:32:46 alex-power kernel: [ 67.119473] dma_buf_map_attachment+0x8c/0x100 Feb 14 16:32:46 alex-power kernel: [ 67.119477] i915_gem_object_get_pages_dmabuf+0x1c/0x70 [i915] Feb 14 16:32:46 alex-power kernel: [ 67.119535] __i915_gem_object_get_pages+0x4d/0x80 [i915] As a workaround please try logging into a Xorg session. It's the one called 'Ubuntu on Xorg' or if that's not listed then just 'Ubuntu' on the login screen. ** Tags added: hybrid multigpu ** Tags added: nvidia ** Tags added: wayland wayland-session ** Summary changed: - System freeze + System freeze when plugging USB-C monitor into a hybrid Intel/Nvidia laptop ** Summary changed: - System freeze when plugging USB-C monitor into a hybrid Intel/Nvidia laptop + System freeze when plugging USB-C monitor into a hybrid Intel/Nvidia laptop: [drm:__nv_drm_gem_nvkms_memory_prime_get_sg_table [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x0100] Failed to get memory pages for NvKmsKapiMemory ** Package changed: ubuntu => linux (Ubuntu) ** Changed in: linux (Ubuntu) Importance: Undecided => High ** Changed in: linux (Ubuntu) Status: Incomplete => New ** Bug watch added: gitlab.gnome.org/GNOME/mutter/-/issues #1891 https://gitlab.gnome.org/GNOME/mutter/-/issues/1891 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1960865 Title: System freeze when plugging USB-C monitor into a hybrid Intel/Nvidia laptop: [drm:__nv_drm_gem_nvkms_memory_prime_get_sg_table [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x0100] Failed to get memory pages for NvKmsKapiMemory Status in Mutter: Unknown Status in linux package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: I recently upgraded my NVidia drivers on my ThinkPad P1 Gen 3. If I start Ubuntu on Wayland session and plug in my USB-C monitor the system reliably completely freeze. The freeze is also reproducible if the screen is plugged in during startup and trying to login into a Wayland session. Only Wayland session experiences a crash. The crash happens ONLY if the USB-C monitor is plugged in. USB-C monitor is also a USB3 hub. Hardware seems to work fine, as Windows shows no issues with the setup. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: xorg 1:7.7+22ubuntu2
[Kernel-packages] [Bug 1960865] [NEW] System freeze when plugging USB-C monitor into a hybrid Intel/Nvidia laptop: [drm:__nv_drm_gem_nvkms_memory_prime_get_sg_table [nvidia_drm]] *ERROR* [nvidia-drm]
You have been subscribed to a public bug: I recently upgraded my NVidia drivers on my ThinkPad P1 Gen 3. If I start Ubuntu on Wayland session and plug in my USB-C monitor the system reliably completely freeze. The freeze is also reproducible if the screen is plugged in during startup and trying to login into a Wayland session. Only Wayland session experiences a crash. The crash happens ONLY if the USB-C monitor is plugged in. USB-C monitor is also a USB3 hub. Hardware seems to work fine, as Windows shows no issues with the setup. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: xorg 1:7.7+22ubuntu2 ProcVersionSignature: Ubuntu 5.13.0-30.33-generic 5.13.19 Uname: Linux 5.13.0-30-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 470.103.01 Thu Jan 6 12:10:04 UTC 2022 GCC version: gcc version 11.2.0 (Ubuntu 11.2.0-7ubuntu2) ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Feb 14 16:39:34 2022 DistUpgraded: 2021-10-14 18:36:11,564 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: impish DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GpuHangFrequency: Continuously GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Within the last few days GraphicsCard: Intel Corporation CometLake-H GT2 [UHD Graphics] [8086:9bc4] (rev 05) (prog-if 00 [VGA controller]) Subsystem: Lenovo CometLake-H GT2 [UHD Graphics] [17aa:22c1] NVIDIA Corporation TU117GLM [Quadro T1000 Mobile] [10de:1fb9] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Lenovo TU117GLM [Quadro T1000 Mobile] [17aa:22c1] InstallationDate: Installed on 2020-10-05 (497 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: LENOVO 20THCT01WW ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-30-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: Upgraded to impish on 2021-10-14 (122 days ago) dmi.bios.date: 12/27/2021 dmi.bios.release: 1.21 dmi.bios.vendor: LENOVO dmi.bios.version: N2VET36W (1.21 ) dmi.board.asset.tag: Not Available dmi.board.name: 20THCT01WW dmi.board.vendor: LENOVO dmi.board.version: 0B98417 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.10 dmi.modalias: dmi:bvnLENOVO:bvrN2VET36W(1.21):bd12/27/2021:br1.21:efr1.10:svnLENOVO:pn20THCT01WW:pvrThinkPadP1Gen3:rvnLENOVO:rn20THCT01WW:rvr0B98417WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20TH_BU_Think_FM_ThinkPadP1Gen3: dmi.product.family: ThinkPad P1 Gen 3 dmi.product.name: 20THCT01WW dmi.product.sku: LENOVO_MT_20TH_BU_Think_FM_ThinkPad P1 Gen 3 dmi.product.version: ThinkPad P1 Gen 3 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-8ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1 version.libgl1-mesa-glx: libgl1-mesa-glx 21.2.6-0ubuntu0.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1build1 ** Affects: linux (Ubuntu) Importance: High Status: New ** Tags: amd64 apport-bug freeze hybrid impish multigpu nvidia third-party-packages ubuntu wayland wayland-session -- System freeze when plugging USB-C monitor into a hybrid Intel/Nvidia laptop: [drm:__nv_drm_gem_nvkms_memory_prime_get_sg_table [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x0100] Failed to get memory pages for NvKmsKapiMemory https://bugs.launchpad.net/bugs/1960865 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 1937295] 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 1937295 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete ** Changed in: linux (Ubuntu Bionic) Status: New => Incomplete ** Changed in: linux (Ubuntu Focal) Status: New => Incomplete ** Changed in: linux (Ubuntu Impish) 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/1937295 Title: Installation hangs on VROC systems during Bionic installs Status in subiquity: Incomplete Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: Incomplete Status in linux source package in Focal: Incomplete Status in linux source package in Impish: Incomplete Status in linux source package in Jammy: Incomplete Bug description: A hardware partner has been testing 18.04 subiquity images on their servers with VROC enabled and configured in a RAID 10 setup. In their own words: Steps to reproduce: 1. Boot into VRoC controller in uEFI Setup and create a raid10 disk. 2. Install Ubuntu 18.04.5 on the RAID10. 3. The system hangs at "Partitions formatting 33%". After looking at the launchpad (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1896578/), the fix was included in the updated kernel. [Quotes from the launchpad] The released kernels are: Hirsute: 5.11.0-22-generic Groovy: 5.8.0-59-generic Focal: 5.4.0-77-generic Bionic: 4.15.0-147-generic I've asked them to also confirm this on 20.04.2, and check that 20.04.3 dailies fix the issue. It is at least a very reasonable hypothesis that this will also break on all current ISO installs as none of them are respun once released to include updated SRUs in the installation media. This currently affects 20.04.2 but that will be resolved shortly when 20.04.3 releases as the GA and HWE kernels in that image should have the SRU that fixes this issue. However, 18.04 has no further releases, and even the 18.04.5 daily-live and daily images on cdimages.ubuntu.com are not built after 18.04.5 was released. To manage notifications about this bug go to: https://bugs.launchpad.net/subiquity/+bug/1937295/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1937295] Re: Installation hangs on VROC systems during Bionic installs
** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Impish) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1937295 Title: Installation hangs on VROC systems during Bionic installs Status in subiquity: Incomplete Status in linux package in Ubuntu: New Status in linux source package in Bionic: New Status in linux source package in Focal: New Status in linux source package in Impish: New Status in linux source package in Jammy: New Bug description: A hardware partner has been testing 18.04 subiquity images on their servers with VROC enabled and configured in a RAID 10 setup. In their own words: Steps to reproduce: 1. Boot into VRoC controller in uEFI Setup and create a raid10 disk. 2. Install Ubuntu 18.04.5 on the RAID10. 3. The system hangs at "Partitions formatting 33%". After looking at the launchpad (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1896578/), the fix was included in the updated kernel. [Quotes from the launchpad] The released kernels are: Hirsute: 5.11.0-22-generic Groovy: 5.8.0-59-generic Focal: 5.4.0-77-generic Bionic: 4.15.0-147-generic I've asked them to also confirm this on 20.04.2, and check that 20.04.3 dailies fix the issue. It is at least a very reasonable hypothesis that this will also break on all current ISO installs as none of them are respun once released to include updated SRUs in the installation media. This currently affects 20.04.2 but that will be resolved shortly when 20.04.3 releases as the GA and HWE kernels in that image should have the SRU that fixes this issue. However, 18.04 has no further releases, and even the 18.04.5 daily-live and daily images on cdimages.ubuntu.com are not built after 18.04.5 was released. To manage notifications about this bug go to: https://bugs.launchpad.net/subiquity/+bug/1937295/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1950306] Re: Ubuntu server 21.10 and 22.04 installation crash with VROC raid10
Apologies, I duped the wrong bug... reopening this one. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1950306 Title: Ubuntu server 21.10 and 22.04 installation crash with VROC raid10 Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: Incomplete Status in linux source package in Focal: Incomplete Status in linux source package in Impish: Incomplete Status in linux source package in Jammy: Incomplete Bug description: Try to install ubuntu server 21.10 and 22.04 with VROC raid disk, the raid disk can be identified and created partition normally, but it crash when finish the configuration setup. Ubuntu server 18.04.6 cannot reproduce the issue, no matter DI- installer or live installer. ubuntu desktop 18.04.6 only display the nvme disk, not VROC disk, when it is on insalling. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1950306/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1960392] Re: Ubuntu server 22.04 installation crash with intel VROC sata raid
*** This bug is a duplicate of bug 1960926 *** https://bugs.launchpad.net/bugs/1960926 This is a duplicate of the linked bug that was filed by the upstream. ** This bug has been marked a duplicate of bug 1960926 [VROC] Installation on RAID volume fails - ubuntu 22.04 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1960392 Title: Ubuntu server 22.04 installation crash with intel VROC sata raid Status in subiquity: New Status in linux package in Ubuntu: Invalid Bug description: Reproduce steps: 1.Setup raid 0 with 2 sata disks and intel VROC SATA controller. 2.Install Ubuntu server 22.04 with the latest image. 3.It crash with error "devices or container for raid must be specified" To manage notifications about this bug go to: https://bugs.launchpad.net/subiquity/+bug/1960392/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1950306] Re: Ubuntu server 21.10 and 22.04 installation crash with VROC raid10
Pretty sure this is a duplicate of the bug filed by the upstream vendor linked. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1950306 Title: Ubuntu server 21.10 and 22.04 installation crash with VROC raid10 Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: Incomplete Status in linux source package in Focal: Incomplete Status in linux source package in Impish: Incomplete Status in linux source package in Jammy: Incomplete Bug description: Try to install ubuntu server 21.10 and 22.04 with VROC raid disk, the raid disk can be identified and created partition normally, but it crash when finish the configuration setup. Ubuntu server 18.04.6 cannot reproduce the issue, no matter DI- installer or live installer. ubuntu desktop 18.04.6 only display the nvme disk, not VROC disk, when it is on insalling. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1950306/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1960083] Re: dirname applet missing from initramfs
I just downloaded the iso today, then I redid an installation But it's still the version minus one I don't know how to update the ISO I just downloaded before installing it -- 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/1960083 Title: dirname applet missing from initramfs Status in busybox package in Ubuntu: Fix Released Status in zfs-linux package in Ubuntu: Confirmed Bug description: The initramfs is currently being built without the dirname applet. This is causing issues with zfs encrypted devices, as cryptsetup is attempting to use dirname to determine the location of the system key. This results in the following error: /init: line 971: dirname: not found followed by a prompt that is missing the zpool name. For example "Please unlock disk keystore-" rather than "Please unlock disk keystore-rpool". After entering the password, the user is dropped to an initramfs shell. It appears that this was caused by a change in cryptsetup to suddenly need dirname to function properly. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/busybox/+bug/1960083/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1950062] Re: Unable to access CPU i2c interfaces with AMD "Cezanne" CPU's
Didn't expect to see this fixed that soon. Amazing to see that, very happy AMD getting onboard. Vicamo can confirm it works on Focal Fossa with AMD 5700G. No more i2c errors and OpenRGB program just works now. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1950062 Title: Unable to access CPU i2c interfaces with AMD "Cezanne" CPU's Status in amd: New Status in linux package in Ubuntu: Confirmed Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-oem-5.14 source package in Focal: New Status in linux source package in Jammy: Confirmed Status in linux-oem-5.14 source package in Jammy: Invalid Status in Arch Linux: New Bug description: OpenRGB uses the CPU SMBus/i2c interfaces to talk to the motherboard RGB controller and the DRAM RGB controllers and after updating my system to a 5700G from a 2400G I see error messages in dmesg for each read and write attempt to the interfaces. If I swap the CPU back on the same install I am able to see and control the RGB interfaces. Another user on the OpenRGB discord with a 5600G is also seeing the same issues. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: linux-image-5.13.0-20-generic 5.13.0-20.20 ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14 Uname: Linux 5.13.0-20-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: user 1654 F pulseaudio /dev/snd/pcmC1D0p: user 1654 F...m pulseaudio /dev/snd/controlC0: user 1654 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Nov 6 16:36:17 2021 InstallationDate: Installed on 2021-09-18 (49 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcEnviron: TERM=xterm-256color PATH=(custom, no username) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-20-generic root=UUID=dc2e65cb-a2e0-408c-a64b-bb0ccc6fdef0 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.13.0-20-generic N/A linux-backports-modules-5.13.0-20-generic N/A linux-firmware 1.201.1 SourcePackage: linux UpgradeStatus: Upgraded to impish on 2021-10-17 (20 days ago) dmi.bios.date: 08/11/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P4.60 dmi.board.name: B450 Gaming-ITX/ac dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP4.60:bd08/11/2021:br5.17:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.:rvnASRock:rnB450Gaming-ITX/ac:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/amd/+bug/1950062/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1950062] Re: Unable to access CPU i2c interfaces with AMD "Cezanne" CPU's
Do you have a PPA for impish? > E: The repository 'http://ppa.launchpad.net/vicamo/ppa-1950062/ubuntu impish Release' does not have a Release file. >From memory, I could not boot the OS with Focal and needed to use hirsute after I upgraded the CPU. I will try the latest Jammy live CD shortly. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1950062 Title: Unable to access CPU i2c interfaces with AMD "Cezanne" CPU's Status in amd: New Status in linux package in Ubuntu: Confirmed Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-oem-5.14 source package in Focal: New Status in linux source package in Jammy: Confirmed Status in linux-oem-5.14 source package in Jammy: Invalid Status in Arch Linux: New Bug description: OpenRGB uses the CPU SMBus/i2c interfaces to talk to the motherboard RGB controller and the DRAM RGB controllers and after updating my system to a 5700G from a 2400G I see error messages in dmesg for each read and write attempt to the interfaces. If I swap the CPU back on the same install I am able to see and control the RGB interfaces. Another user on the OpenRGB discord with a 5600G is also seeing the same issues. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: linux-image-5.13.0-20-generic 5.13.0-20.20 ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14 Uname: Linux 5.13.0-20-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: user 1654 F pulseaudio /dev/snd/pcmC1D0p: user 1654 F...m pulseaudio /dev/snd/controlC0: user 1654 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Nov 6 16:36:17 2021 InstallationDate: Installed on 2021-09-18 (49 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcEnviron: TERM=xterm-256color PATH=(custom, no username) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-20-generic root=UUID=dc2e65cb-a2e0-408c-a64b-bb0ccc6fdef0 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.13.0-20-generic N/A linux-backports-modules-5.13.0-20-generic N/A linux-firmware 1.201.1 SourcePackage: linux UpgradeStatus: Upgraded to impish on 2021-10-17 (20 days ago) dmi.bios.date: 08/11/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P4.60 dmi.board.name: B450 Gaming-ITX/ac dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP4.60:bd08/11/2021:br5.17:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.:rvnASRock:rnB450Gaming-ITX/ac:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/amd/+bug/1950062/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1950062] Re: Unable to access CPU i2c interfaces with AMD "Cezanne" CPU's
Jammy appears to have failed to build. Trying it on oem-5.14 on a machine with the failing symptom it seems to fail on the machine I tested unfortunately. When loading the i2c-piix4 module I see the following: [ 97.103748] ACPI Warning: SystemIO range 0x0B00-0x0B08 conflicts with OpRegion 0x0B00-0x0B06 (\_SB.PCI0.SMBS.SMBO) (20210604/utaddress-204) [ 97.103760] ACPI: OSL: Resource conflict; ACPI support missing from driver? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1950062 Title: Unable to access CPU i2c interfaces with AMD "Cezanne" CPU's Status in amd: New Status in linux package in Ubuntu: Confirmed Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-oem-5.14 source package in Focal: New Status in linux source package in Jammy: Confirmed Status in linux-oem-5.14 source package in Jammy: Invalid Status in Arch Linux: New Bug description: OpenRGB uses the CPU SMBus/i2c interfaces to talk to the motherboard RGB controller and the DRAM RGB controllers and after updating my system to a 5700G from a 2400G I see error messages in dmesg for each read and write attempt to the interfaces. If I swap the CPU back on the same install I am able to see and control the RGB interfaces. Another user on the OpenRGB discord with a 5600G is also seeing the same issues. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: linux-image-5.13.0-20-generic 5.13.0-20.20 ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14 Uname: Linux 5.13.0-20-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: user 1654 F pulseaudio /dev/snd/pcmC1D0p: user 1654 F...m pulseaudio /dev/snd/controlC0: user 1654 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Nov 6 16:36:17 2021 InstallationDate: Installed on 2021-09-18 (49 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcEnviron: TERM=xterm-256color PATH=(custom, no username) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-20-generic root=UUID=dc2e65cb-a2e0-408c-a64b-bb0ccc6fdef0 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.13.0-20-generic N/A linux-backports-modules-5.13.0-20-generic N/A linux-firmware 1.201.1 SourcePackage: linux UpgradeStatus: Upgraded to impish on 2021-10-17 (20 days ago) dmi.bios.date: 08/11/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P4.60 dmi.board.name: B450 Gaming-ITX/ac dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP4.60:bd08/11/2021:br5.17:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.:rvnASRock:rnB450Gaming-ITX/ac:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/amd/+bug/1950062/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1948807] Re: Boot time from snap in 20/stable increases boot time on 3.5 seconds
This bug was fixed in the package linux-raspi - 5.4.0-1052.58 --- linux-raspi (5.4.0-1052.58) focal; urgency=medium * focal/linux-raspi: 5.4.0-1052.58 -proposed tracker (LP: #1959811) * Boot time from snap in 20/stable increases boot time on 3.5 seconds (LP: #1948807) - [Config] raspi: Set BLK_DEV_LOOP_MIN_COUNT=8 * Missing overlays/README (LP: #1954757) - SAUCE: Install overlays/README [ Ubuntu: 5.4.0-99.112 ] * focal/linux: 5.4.0-99.112 -proposed tracker (LP: #1959817) * linux-image-5.4.0-97.110 freezes by accessing cifs shares (LP: #1959665) - Revert "cifs: To match file servers, make sure the server hostname matches" - Revert "cifs: set a minimum of 120s for next dns resolution" - Revert "cifs: use the expiry output of dns_query to schedule next resolution" [ Ubuntu: 5.4.0-97.110 ] * icmp_redirect from selftests fails on F/kvm (unary operator expected) (LP: #1938964) - selftests: icmp_redirect: pass xfail=0 to log_test() * Focal: CIFS stable updates (LP: #1954926) - cifs: use the expiry output of dns_query to schedule next resolution - cifs: set a minimum of 120s for next dns resolution - cifs: To match file servers, make sure the server hostname matches * seccomp_bpf in seccomp from ubuntu_kernel_selftests failed to build on B-5.4 (LP: #1896420) - SAUCE: selftests/seccomp: fix "storage size of 'md' isn't known" build issue - SAUCE: selftests/seccomp: Fix s390x regs not defined issue * system crash when removing ipmi_msghandler module (LP: #1950666) - ipmi: Move remove_work to dedicated workqueue - ipmi: msghandler: Make symbol 'remove_work_wq' static * zcrypt DD: Toleration for new IBM Z Crypto Hardware - (Backport to Ubuntu 20.04) (LP: #1954680) - s390/AP: support new dynamic AP bus size limit * [UBUNTU 20.04] KVM hardware diagnose data improvements for guest kernel - kernel part (LP: #1953334) - s390/setup: diag 318: refactor struct - s390/kvm: diagnose 0x318 sync and reset - KVM: s390: remove diag318 reset code - KVM: s390: add debug statement for diag 318 CPNC data * Updates to ib_peer_memory requested by Nvidia (LP: #1947206) - SAUCE: RDMA/core: Updated ib_peer_memory * Include Infiniband Peer Memory interface (LP: #1923104) - IB: Allow calls to ib_umem_get from kernel ULPs - SAUCE: RDMA/core: Introduce peer memory interface * Focal update: v5.4.162 upstream stable release (LP: #1954834) - arm64: zynqmp: Do not duplicate flash partition label property - arm64: zynqmp: Fix serial compatible string - ARM: dts: NSP: Fix mpcore, mmc node names - scsi: lpfc: Fix list_add() corruption in lpfc_drain_txq() - arm64: dts: hisilicon: fix arm,sp805 compatible string - RDMA/bnxt_re: Check if the vlan is valid before reporting - usb: musb: tusb6010: check return value after calling platform_get_resource() - usb: typec: tipd: Remove WARN_ON in tps6598x_block_read - arm64: dts: qcom: msm8998: Fix CPU/L2 idle state latency and residency - arm64: dts: freescale: fix arm,sp805 compatible string - ASoC: SOF: Intel: hda-dai: fix potential locking issue - clk: imx: imx6ul: Move csi_sel mux to correct base register - ASoC: nau8824: Add DMI quirk mechanism for active-high jack-detect - scsi: advansys: Fix kernel pointer leak - firmware_loader: fix pre-allocated buf built-in firmware use - ARM: dts: omap: fix gpmc,mux-add-data type - usb: host: ohci-tmio: check return value after calling platform_get_resource() - ARM: dts: ls1021a: move thermal-zones node out of soc/ - ARM: dts: ls1021a-tsn: use generic "jedec,spi-nor" compatible for flash - ALSA: ISA: not for M68K - tty: tty_buffer: Fix the softlockup issue in flush_to_ldisc - MIPS: sni: Fix the build - scsi: target: Fix ordered tag handling - scsi: target: Fix alua_tg_pt_gps_count tracking - iio: imu: st_lsm6dsx: Avoid potential array overflow in st_lsm6dsx_set_odr() - powerpc/5200: dts: fix memory node unit name - ALSA: gus: fix null pointer dereference on pointer block - powerpc/dcr: Use cmplwi instead of 3-argument cmpli - sh: check return code of request_irq - maple: fix wrong return value of maple_bus_init(). - f2fs: fix up f2fs_lookup tracepoints - sh: fix kconfig unmet dependency warning for FRAME_POINTER - sh: math-emu: drop unused functions - sh: define __BIG_ENDIAN for math-emu - clk: ingenic: Fix bugs with divided dividers - clk/ast2600: Fix soc revision for AHB - clk: qcom: gcc-msm8996: Drop (again) gcc_aggre1_pnoc_ahb_clk - mips: BCM63XX: ensure that CPU_SUPPORTS_32BIT_KERNEL is set - sched/core: Mitigate race cpus_share_cache()/update_top_cache_domain() - tracing: Save normal string variables - tracing/histogram: Do not copy the fixed-size char array field over the field size - RDMA/netlink: Add __maybe_unused
[Kernel-packages] [Bug 1954757] Re: Missing overlays/README
This bug was fixed in the package linux-raspi - 5.4.0-1052.58 --- linux-raspi (5.4.0-1052.58) focal; urgency=medium * focal/linux-raspi: 5.4.0-1052.58 -proposed tracker (LP: #1959811) * Boot time from snap in 20/stable increases boot time on 3.5 seconds (LP: #1948807) - [Config] raspi: Set BLK_DEV_LOOP_MIN_COUNT=8 * Missing overlays/README (LP: #1954757) - SAUCE: Install overlays/README [ Ubuntu: 5.4.0-99.112 ] * focal/linux: 5.4.0-99.112 -proposed tracker (LP: #1959817) * linux-image-5.4.0-97.110 freezes by accessing cifs shares (LP: #1959665) - Revert "cifs: To match file servers, make sure the server hostname matches" - Revert "cifs: set a minimum of 120s for next dns resolution" - Revert "cifs: use the expiry output of dns_query to schedule next resolution" [ Ubuntu: 5.4.0-97.110 ] * icmp_redirect from selftests fails on F/kvm (unary operator expected) (LP: #1938964) - selftests: icmp_redirect: pass xfail=0 to log_test() * Focal: CIFS stable updates (LP: #1954926) - cifs: use the expiry output of dns_query to schedule next resolution - cifs: set a minimum of 120s for next dns resolution - cifs: To match file servers, make sure the server hostname matches * seccomp_bpf in seccomp from ubuntu_kernel_selftests failed to build on B-5.4 (LP: #1896420) - SAUCE: selftests/seccomp: fix "storage size of 'md' isn't known" build issue - SAUCE: selftests/seccomp: Fix s390x regs not defined issue * system crash when removing ipmi_msghandler module (LP: #1950666) - ipmi: Move remove_work to dedicated workqueue - ipmi: msghandler: Make symbol 'remove_work_wq' static * zcrypt DD: Toleration for new IBM Z Crypto Hardware - (Backport to Ubuntu 20.04) (LP: #1954680) - s390/AP: support new dynamic AP bus size limit * [UBUNTU 20.04] KVM hardware diagnose data improvements for guest kernel - kernel part (LP: #1953334) - s390/setup: diag 318: refactor struct - s390/kvm: diagnose 0x318 sync and reset - KVM: s390: remove diag318 reset code - KVM: s390: add debug statement for diag 318 CPNC data * Updates to ib_peer_memory requested by Nvidia (LP: #1947206) - SAUCE: RDMA/core: Updated ib_peer_memory * Include Infiniband Peer Memory interface (LP: #1923104) - IB: Allow calls to ib_umem_get from kernel ULPs - SAUCE: RDMA/core: Introduce peer memory interface * Focal update: v5.4.162 upstream stable release (LP: #1954834) - arm64: zynqmp: Do not duplicate flash partition label property - arm64: zynqmp: Fix serial compatible string - ARM: dts: NSP: Fix mpcore, mmc node names - scsi: lpfc: Fix list_add() corruption in lpfc_drain_txq() - arm64: dts: hisilicon: fix arm,sp805 compatible string - RDMA/bnxt_re: Check if the vlan is valid before reporting - usb: musb: tusb6010: check return value after calling platform_get_resource() - usb: typec: tipd: Remove WARN_ON in tps6598x_block_read - arm64: dts: qcom: msm8998: Fix CPU/L2 idle state latency and residency - arm64: dts: freescale: fix arm,sp805 compatible string - ASoC: SOF: Intel: hda-dai: fix potential locking issue - clk: imx: imx6ul: Move csi_sel mux to correct base register - ASoC: nau8824: Add DMI quirk mechanism for active-high jack-detect - scsi: advansys: Fix kernel pointer leak - firmware_loader: fix pre-allocated buf built-in firmware use - ARM: dts: omap: fix gpmc,mux-add-data type - usb: host: ohci-tmio: check return value after calling platform_get_resource() - ARM: dts: ls1021a: move thermal-zones node out of soc/ - ARM: dts: ls1021a-tsn: use generic "jedec,spi-nor" compatible for flash - ALSA: ISA: not for M68K - tty: tty_buffer: Fix the softlockup issue in flush_to_ldisc - MIPS: sni: Fix the build - scsi: target: Fix ordered tag handling - scsi: target: Fix alua_tg_pt_gps_count tracking - iio: imu: st_lsm6dsx: Avoid potential array overflow in st_lsm6dsx_set_odr() - powerpc/5200: dts: fix memory node unit name - ALSA: gus: fix null pointer dereference on pointer block - powerpc/dcr: Use cmplwi instead of 3-argument cmpli - sh: check return code of request_irq - maple: fix wrong return value of maple_bus_init(). - f2fs: fix up f2fs_lookup tracepoints - sh: fix kconfig unmet dependency warning for FRAME_POINTER - sh: math-emu: drop unused functions - sh: define __BIG_ENDIAN for math-emu - clk: ingenic: Fix bugs with divided dividers - clk/ast2600: Fix soc revision for AHB - clk: qcom: gcc-msm8996: Drop (again) gcc_aggre1_pnoc_ahb_clk - mips: BCM63XX: ensure that CPU_SUPPORTS_32BIT_KERNEL is set - sched/core: Mitigate race cpus_share_cache()/update_top_cache_domain() - tracing: Save normal string variables - tracing/histogram: Do not copy the fixed-size char array field over the field size - RDMA/netlink: Add __maybe_unused
[Kernel-packages] [Bug 1960871] Re: linux-modules-extra-* fails to install due to dependency on unsigned package
Fixed sent to ML and has been applied https://lists.ubuntu.com/archives/kernel-team/2022-February/128100.html ** Changed in: linux-aws (Ubuntu) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1960871 Title: linux-modules-extra-* fails to install due to dependency on unsigned package Status in linux-aws package in Ubuntu: Fix Committed Bug description: Several SRU tests are failing the test setup due to failure to install the modules-extra package: * Command: yes "" | DEBIAN_FRONTEND=noninteractive apt-get install --yes --force-yes automake bison build-essential byacc flex git keyutils libacl1-dev libaio- dev libcap-dev libmm-dev libnuma-dev libsctp-dev libselinux1-dev libssl- dev libtirpc-dev pkg-config quota xfslibs-dev xfsprogs gcc linux-modules- extra-4.15.0-1120-aws Exit status: 100 Duration: 0.908210039139 stdout: Reading package lists... Building dependency tree... Reading state information... xfsprogs is already the newest version (4.9.0+nmu1ubuntu2). xfsprogs set to manually installed. git is already the newest version (1:2.17.1-1ubuntu0.9). git set to manually installed. Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: linux-modules-extra-4.15.0-1120-aws : Depends: linux-image-unsigned-4.15.0-1120-aws but it is not going to be installed stderr: W: --force-yes is deprecated, use one of the options starting with --allow instead. E: Unable to correct problems, you have held broken packages. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1960871/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1960324] Re: [VROC] Kernel does not contain fixes for iostat for md devices
Hi @ktanska- Here is a test build of the hwe-5.13 kernel with the requested series applied: https://kernel.ubuntu.com/~kamal/lp1960324/ Please verify that it works as expected and report your results here. Following that, our intention is to pull the series into our Impish 5.13 baseline kernel from which hwe-5.13 is derived. Thanks! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1960324 Title: [VROC] Kernel does not contain fixes for iostat for md devices Status in linux package in Ubuntu: Invalid Status in linux-hwe-5.13 package in Ubuntu: In Progress Status in linux source package in Focal: Invalid Status in linux-hwe-5.13 source package in Focal: In Progress Status in linux source package in Impish: In Progress Status in linux-hwe-5.13 source package in Impish: Invalid Bug description: Hello, I noticed that kernel which was used in ubuntu 22.04 (hwe-5.13) does not contain fixes for IO statistics for md devices. IO statistics for md devices were added to kernel 5.10 (https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=41d2d848e5c09209bdb57ff9c0ca34075e22783d) but then bug for double fault was reported and this patch was reverted by Guoqing Jiang (https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=ad3fc798800fb7ca04c1dfc439dba946818048d8). Guoqing Jiang added series of patches which fixes problem and adds IO stats for md devices on top on the revert patch: - first commit from series: 10764815ff4728d2c57da677cd5d3dd6f446cf5f (https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=10764815ff4728d2c57da677cd5d3dd6f446cf5f) - last one: de3ea66e9d23a34eef5e17f960d6473f78a1c54b (https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=de3ea66e9d23a34eef5e17f960d6473f78a1c54b) I checked that kernel used in ubuntu 22.04 contains only patch with revert - iostat does not report for md devices (https://kernel.ubuntu.com/git/ubuntu/ubuntu-focal.git/log/?h=hwe-5.13&qt=author&q=Guoqing+Jiang) Please consider adding series of patches described above. Regards, Kinga Tanska To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1960324/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1960083] Re: dirname applet missing from initramfs
Fix was released in busybox 1:1.30.1-7ubuntu3 and requires initramfs rebuild your screenshot clearly shows version number 1:1.30.1-7ubuntu2 -- 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/1960083 Title: dirname applet missing from initramfs Status in busybox package in Ubuntu: Fix Released Status in zfs-linux package in Ubuntu: Confirmed Bug description: The initramfs is currently being built without the dirname applet. This is causing issues with zfs encrypted devices, as cryptsetup is attempting to use dirname to determine the location of the system key. This results in the following error: /init: line 971: dirname: not found followed by a prompt that is missing the zpool name. For example "Please unlock disk keystore-" rather than "Please unlock disk keystore-rpool". After entering the password, the user is dropped to an initramfs shell. It appears that this was caused by a change in cryptsetup to suddenly need dirname to function properly. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/busybox/+bug/1960083/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1960083] Re: dirname applet missing from initramfs
Hello Are you sure? https://zupimages.net/viewer.php?id=22/07/fxcb.jpg -- 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/1960083 Title: dirname applet missing from initramfs Status in busybox package in Ubuntu: Fix Released Status in zfs-linux package in Ubuntu: Confirmed Bug description: The initramfs is currently being built without the dirname applet. This is causing issues with zfs encrypted devices, as cryptsetup is attempting to use dirname to determine the location of the system key. This results in the following error: /init: line 971: dirname: not found followed by a prompt that is missing the zpool name. For example "Please unlock disk keystore-" rather than "Please unlock disk keystore-rpool". After entering the password, the user is dropped to an initramfs shell. It appears that this was caused by a change in cryptsetup to suddenly need dirname to function properly. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/busybox/+bug/1960083/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1960324] Re: [VROC] Kernel does not contain fixes for iostat for md devices
** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Impish) Importance: Undecided Status: New ** Also affects: linux-hwe-5.13 (Ubuntu Impish) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Impish) Status: New => In Progress ** Changed in: linux (Ubuntu Impish) Importance: Undecided => Medium ** Changed in: linux (Ubuntu) Status: New => Invalid ** Changed in: linux (Ubuntu Impish) Assignee: (unassigned) => Kamal Mostafa (kamalmostafa) ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux-hwe-5.13 (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Focal) Status: New => Invalid ** Changed in: linux-hwe-5.13 (Ubuntu Impish) Status: New => Invalid ** Changed in: linux-hwe-5.13 (Ubuntu Focal) Status: New => In Progress ** Changed in: linux-hwe-5.13 (Ubuntu Focal) Importance: Undecided => Medium ** Changed in: linux-hwe-5.13 (Ubuntu Focal) Assignee: (unassigned) => Kamal Mostafa (kamalmostafa) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1960324 Title: [VROC] Kernel does not contain fixes for iostat for md devices Status in linux package in Ubuntu: Invalid Status in linux-hwe-5.13 package in Ubuntu: In Progress Status in linux source package in Focal: Invalid Status in linux-hwe-5.13 source package in Focal: In Progress Status in linux source package in Impish: In Progress Status in linux-hwe-5.13 source package in Impish: Invalid Bug description: Hello, I noticed that kernel which was used in ubuntu 22.04 (hwe-5.13) does not contain fixes for IO statistics for md devices. IO statistics for md devices were added to kernel 5.10 (https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=41d2d848e5c09209bdb57ff9c0ca34075e22783d) but then bug for double fault was reported and this patch was reverted by Guoqing Jiang (https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=ad3fc798800fb7ca04c1dfc439dba946818048d8). Guoqing Jiang added series of patches which fixes problem and adds IO stats for md devices on top on the revert patch: - first commit from series: 10764815ff4728d2c57da677cd5d3dd6f446cf5f (https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=10764815ff4728d2c57da677cd5d3dd6f446cf5f) - last one: de3ea66e9d23a34eef5e17f960d6473f78a1c54b (https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=de3ea66e9d23a34eef5e17f960d6473f78a1c54b) I checked that kernel used in ubuntu 22.04 contains only patch with revert - iostat does not report for md devices (https://kernel.ubuntu.com/git/ubuntu/ubuntu-focal.git/log/?h=hwe-5.13&qt=author&q=Guoqing+Jiang) Please consider adding series of patches described above. Regards, Kinga Tanska To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1960324/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1960324] Re: [VROC] Kernel does not contain fixes for iostat for md devices
** Changed in: linux-hwe-5.13 (Ubuntu) Status: New => In Progress ** Changed in: linux-hwe-5.13 (Ubuntu) Importance: Undecided => Medium -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1960324 Title: [VROC] Kernel does not contain fixes for iostat for md devices Status in linux package in Ubuntu: New Status in linux-hwe-5.13 package in Ubuntu: In Progress Bug description: Hello, I noticed that kernel which was used in ubuntu 22.04 (hwe-5.13) does not contain fixes for IO statistics for md devices. IO statistics for md devices were added to kernel 5.10 (https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=41d2d848e5c09209bdb57ff9c0ca34075e22783d) but then bug for double fault was reported and this patch was reverted by Guoqing Jiang (https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=ad3fc798800fb7ca04c1dfc439dba946818048d8). Guoqing Jiang added series of patches which fixes problem and adds IO stats for md devices on top on the revert patch: - first commit from series: 10764815ff4728d2c57da677cd5d3dd6f446cf5f (https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=10764815ff4728d2c57da677cd5d3dd6f446cf5f) - last one: de3ea66e9d23a34eef5e17f960d6473f78a1c54b (https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=de3ea66e9d23a34eef5e17f960d6473f78a1c54b) I checked that kernel used in ubuntu 22.04 contains only patch with revert - iostat does not report for md devices (https://kernel.ubuntu.com/git/ubuntu/ubuntu-focal.git/log/?h=hwe-5.13&qt=author&q=Guoqing+Jiang) Please consider adding series of patches described above. Regards, Kinga Tanska To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1960324/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1960324] Re: [VROC] Kernel does not contain fixes for iostat for md devices
** Changed in: linux-hwe-5.13 (Ubuntu) Assignee: (unassigned) => Kamal Mostafa (kamalmostafa) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1960324 Title: [VROC] Kernel does not contain fixes for iostat for md devices Status in linux-hwe-5.13 package in Ubuntu: New Bug description: Hello, I noticed that kernel which was used in ubuntu 22.04 (hwe-5.13) does not contain fixes for IO statistics for md devices. IO statistics for md devices were added to kernel 5.10 (https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=41d2d848e5c09209bdb57ff9c0ca34075e22783d) but then bug for double fault was reported and this patch was reverted by Guoqing Jiang (https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=ad3fc798800fb7ca04c1dfc439dba946818048d8). Guoqing Jiang added series of patches which fixes problem and adds IO stats for md devices on top on the revert patch: - first commit from series: 10764815ff4728d2c57da677cd5d3dd6f446cf5f (https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=10764815ff4728d2c57da677cd5d3dd6f446cf5f) - last one: de3ea66e9d23a34eef5e17f960d6473f78a1c54b (https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=de3ea66e9d23a34eef5e17f960d6473f78a1c54b) I checked that kernel used in ubuntu 22.04 contains only patch with revert - iostat does not report for md devices (https://kernel.ubuntu.com/git/ubuntu/ubuntu-focal.git/log/?h=hwe-5.13&qt=author&q=Guoqing+Jiang) Please consider adding series of patches described above. Regards, Kinga Tanska To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.13/+bug/1960324/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1960936] 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/1960936 Title: Laptop stalls, kernel log flooded with "Allocating resources" Status in linux package in Ubuntu: Confirmed Bug description: Hi, I have experiencing this for a while now (1 year+), with the laptop (Thinkpad T430s) stalling at times, and often for a long period (hours). Even under very low load. In fact, the issue seems to affect input devices (mouse and keyboard, both external and built-in devices), as the screens continue to operate normally and receiving notifications from applications, such as Slack. The /var/log/kern.log gets flooded with messages like: Feb 15 13:40:12 fernando-ThinkPad-T430s kernel: [ 516.556167] pci_bus :04: Allocating resources Feb 15 13:40:13 fernando-ThinkPad-T430s kernel: [ 518.031745] pci_bus :02: Allocating resources Feb 15 13:40:13 fernando-ThinkPad-T430s kernel: [ 518.031756] pci_bus :03: Allocating resources Feb 15 13:40:13 fernando-ThinkPad-T430s kernel: [ 518.031814] pci_bus :04: Allocating resources Feb 15 13:40:14 fernando-ThinkPad-T430s kernel: [ 518.771217] pci_bus :02: Allocating resources Feb 15 13:40:14 fernando-ThinkPad-T430s kernel: [ 518.771230] pci_bus :03: Allocating resources Feb 15 13:40:14 fernando-ThinkPad-T430s kernel: [ 518.771291] pci_bus :04: Allocating resources Feb 15 13:40:14 fernando-ThinkPad-T430s kernel: [ 519.510986] pci_bus :02: Allocating resources Feb 15 13:40:14 fernando-ThinkPad-T430s kernel: [ 519.510999] pci_bus :03: Allocating resources Feb 15 13:40:14 fernando-ThinkPad-T430s kernel: [ 519.511058] pci_bus :04: Allocating resources Feb 15 13:40:16 fernando-ThinkPad-T430s kernel: [ 520.986362] pci_bus :02: Allocating resources Feb 15 13:40:16 fernando-ThinkPad-T430s kernel: [ 520.986374] pci_bus :03: Allocating resources Feb 15 13:40:16 fernando-ThinkPad-T430s kernel: [ 520.986435] pci_bus :04: Allocating resources Feb 15 13:40:17 fernando-ThinkPad-T430s kernel: [ 521.722015] pci_bus :02: Allocating resources Feb 15 13:40:17 fernando-ThinkPad-T430s kernel: [ 521.722026] pci_bus :03: Allocating resources Feb 15 13:40:17 fernando-ThinkPad-T430s kernel: [ 521.722068] pci_bus :04: Allocating resources Feb 15 13:40:17 fernando-ThinkPad-T430s kernel: [ 522.457759] pci_bus :02: Allocating resources Feb 15 13:40:17 fernando-ThinkPad-T430s kernel: [ 522.457771] pci_bus :03: Allocating resources Feb 15 13:40:17 fernando-ThinkPad-T430s kernel: [ 522.457807] pci_bus :04: Allocating resources Feb 15 13:40:19 fernando-ThinkPad-T430s kernel: [ 523.933552] pci_bus :02: Allocating resources Feb 15 13:40:19 fernando-ThinkPad-T430s kernel: [ 523.933572] pci_bus :03: Allocating resources Feb 15 13:40:19 fernando-ThinkPad-T430s kernel: [ 523.933638] pci_bus :04: Allocating resources Would the problem be linked to a driver that controls a pci device? A malfunctioning hardware part? Sometimes the issue is not noticed for days. I should also note the disc is encrypted and even if I restart the computer, when Ubuntu starts loading and the prompt to enter the password to access the disk, the issue is already manifesting itself: I type the password and sometimes the key that is pressed is not sent, sometimes it is send twice. Any other information I can provide, please let me know. Thanks! ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-99-generic 5.4.0-99.112 ProcVersionSignature: Ubuntu 5.4.0-99.112-generic 5.4.162 Uname: Linux 5.4.0-99-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: fernando 2655 F pulseaudio CasperMD5CheckResult: skip Date: Tue Feb 15 13:45:42 2022 InstallationDate: Installed on 2019-10-28 (841 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) MachineType: LENOVO 23539KU ProcEnviron: LANGUAGE=pt_BR:pt:en TERM=xterm-256color PATH=(custom, no user) LANG=pt_BR.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-99-generic root=/dev/mapper/ubuntu--vg-root 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-99-generic N/A linux-backports-modules-5.4.0-99-generic N/A linux-firmware1.187.25 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-07-12 (583 days ago) dmi.bios.date: 11/12/2012 dmi.bios.vendor: LENO
[Kernel-packages] [Bug 1960936] [NEW] Laptop stalls, kernel log flooded with "Allocating resources"
Public bug reported: Hi, I have experiencing this for a while now (1 year+), with the laptop (Thinkpad T430s) stalling at times, and often for a long period (hours). Even under very low load. In fact, the issue seems to affect input devices (mouse and keyboard, both external and built-in devices), as the screens continue to operate normally and receiving notifications from applications, such as Slack. The /var/log/kern.log gets flooded with messages like: Feb 15 13:40:12 fernando-ThinkPad-T430s kernel: [ 516.556167] pci_bus :04: Allocating resources Feb 15 13:40:13 fernando-ThinkPad-T430s kernel: [ 518.031745] pci_bus :02: Allocating resources Feb 15 13:40:13 fernando-ThinkPad-T430s kernel: [ 518.031756] pci_bus :03: Allocating resources Feb 15 13:40:13 fernando-ThinkPad-T430s kernel: [ 518.031814] pci_bus :04: Allocating resources Feb 15 13:40:14 fernando-ThinkPad-T430s kernel: [ 518.771217] pci_bus :02: Allocating resources Feb 15 13:40:14 fernando-ThinkPad-T430s kernel: [ 518.771230] pci_bus :03: Allocating resources Feb 15 13:40:14 fernando-ThinkPad-T430s kernel: [ 518.771291] pci_bus :04: Allocating resources Feb 15 13:40:14 fernando-ThinkPad-T430s kernel: [ 519.510986] pci_bus :02: Allocating resources Feb 15 13:40:14 fernando-ThinkPad-T430s kernel: [ 519.510999] pci_bus :03: Allocating resources Feb 15 13:40:14 fernando-ThinkPad-T430s kernel: [ 519.511058] pci_bus :04: Allocating resources Feb 15 13:40:16 fernando-ThinkPad-T430s kernel: [ 520.986362] pci_bus :02: Allocating resources Feb 15 13:40:16 fernando-ThinkPad-T430s kernel: [ 520.986374] pci_bus :03: Allocating resources Feb 15 13:40:16 fernando-ThinkPad-T430s kernel: [ 520.986435] pci_bus :04: Allocating resources Feb 15 13:40:17 fernando-ThinkPad-T430s kernel: [ 521.722015] pci_bus :02: Allocating resources Feb 15 13:40:17 fernando-ThinkPad-T430s kernel: [ 521.722026] pci_bus :03: Allocating resources Feb 15 13:40:17 fernando-ThinkPad-T430s kernel: [ 521.722068] pci_bus :04: Allocating resources Feb 15 13:40:17 fernando-ThinkPad-T430s kernel: [ 522.457759] pci_bus :02: Allocating resources Feb 15 13:40:17 fernando-ThinkPad-T430s kernel: [ 522.457771] pci_bus :03: Allocating resources Feb 15 13:40:17 fernando-ThinkPad-T430s kernel: [ 522.457807] pci_bus :04: Allocating resources Feb 15 13:40:19 fernando-ThinkPad-T430s kernel: [ 523.933552] pci_bus :02: Allocating resources Feb 15 13:40:19 fernando-ThinkPad-T430s kernel: [ 523.933572] pci_bus :03: Allocating resources Feb 15 13:40:19 fernando-ThinkPad-T430s kernel: [ 523.933638] pci_bus :04: Allocating resources Would the problem be linked to a driver that controls a pci device? A malfunctioning hardware part? Sometimes the issue is not noticed for days. I should also note the disc is encrypted and even if I restart the computer, when Ubuntu starts loading and the prompt to enter the password to access the disk, the issue is already manifesting itself: I type the password and sometimes the key that is pressed is not sent, sometimes it is send twice. Any other information I can provide, please let me know. Thanks! ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-99-generic 5.4.0-99.112 ProcVersionSignature: Ubuntu 5.4.0-99.112-generic 5.4.162 Uname: Linux 5.4.0-99-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: fernando 2655 F pulseaudio CasperMD5CheckResult: skip Date: Tue Feb 15 13:45:42 2022 InstallationDate: Installed on 2019-10-28 (841 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) MachineType: LENOVO 23539KU ProcEnviron: LANGUAGE=pt_BR:pt:en TERM=xterm-256color PATH=(custom, no user) LANG=pt_BR.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-99-generic root=/dev/mapper/ubuntu--vg-root 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-99-generic N/A linux-backports-modules-5.4.0-99-generic N/A linux-firmware1.187.25 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-07-12 (583 days ago) dmi.bios.date: 11/12/2012 dmi.bios.vendor: LENOVO dmi.bios.version: G7ET63WW (2.05 ) dmi.board.asset.tag: Not Available dmi.board.name: 23539KU dmi.board.vendor: LENOVO dmi.board.version: Win8 Pro DPK TPG dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG7ET63WW(2.05):bd11/12/2012:svnLENOVO:pn23539KU:pvrThinkPadT430s:rvnLENOVO:rn23539KU:rvrWin8ProDPKTPG:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T430s dmi.product.name: 2353
[Kernel-packages] [Bug 1957790] Re: NVIDIA CVE-2022-{21813|21814}
It appears that this change might have introduced a regression.
Please have a look at bug 1960499 and bug 1960621.
+--[ https://askubuntu.com/questions/1392037/ ]
|
| From Ubuntu package list for nvidia-driver-*, any
| nvidia driver in the major versions on the left will
| be effectively upgraded to the major version on the
| right:
|
| 495, 510 -> 510
| 460, 465, 470 -> 470
| 455 -> 460
|
| This breaks compatibility if something relies on 495
| but is not compatible with 510. An example is A100
| GPUs on GCP, which can take 495 but not 510.
|
+--
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-restricted-modules in Ubuntu.
https://bugs.launchpad.net/bugs/1957790
Title:
NVIDIA CVE-2022-{21813|21814}
Status in fabric-manager-450 package in Ubuntu:
New
Status in fabric-manager-470 package in Ubuntu:
New
Status in libnvidia-nscq-450 package in Ubuntu:
New
Status in libnvidia-nscq-470 package in Ubuntu:
New
Status in linux-restricted-modules package in Ubuntu:
New
Status in nvidia-graphics-drivers-450-server package in Ubuntu:
New
Status in nvidia-graphics-drivers-470 package in Ubuntu:
New
Status in nvidia-graphics-drivers-470-server package in Ubuntu:
New
Status in nvidia-graphics-drivers-495 package in Ubuntu:
New
Status in fabric-manager-450 source package in Bionic:
Fix Released
Status in fabric-manager-470 source package in Bionic:
Fix Released
Status in libnvidia-nscq-450 source package in Bionic:
Fix Released
Status in libnvidia-nscq-470 source package in Bionic:
Fix Released
Status in linux-restricted-modules source package in Bionic:
New
Status in nvidia-graphics-drivers-450-server source package in Bionic:
Fix Released
Status in nvidia-graphics-drivers-470 source package in Bionic:
Fix Released
Status in nvidia-graphics-drivers-470-server source package in Bionic:
Fix Released
Status in nvidia-graphics-drivers-495 source package in Bionic:
New
Status in fabric-manager-450 source package in Focal:
Fix Released
Status in fabric-manager-470 source package in Focal:
Fix Released
Status in libnvidia-nscq-450 source package in Focal:
Fix Released
Status in libnvidia-nscq-470 source package in Focal:
Fix Released
Status in linux-restricted-modules source package in Focal:
New
Status in nvidia-graphics-drivers-450-server source package in Focal:
Fix Released
Status in nvidia-graphics-drivers-470 source package in Focal:
Fix Released
Status in nvidia-graphics-drivers-470-server source package in Focal:
Fix Released
Status in nvidia-graphics-drivers-495 source package in Focal:
New
Status in fabric-manager-450 source package in Impish:
Fix Released
Status in fabric-manager-470 source package in Impish:
Fix Released
Status in libnvidia-nscq-450 source package in Impish:
Fix Released
Status in libnvidia-nscq-470 source package in Impish:
Fix Released
Status in linux-restricted-modules source package in Impish:
New
Status in nvidia-graphics-drivers-450-server source package in Impish:
Fix Released
Status in nvidia-graphics-drivers-470 source package in Impish:
Fix Released
Status in nvidia-graphics-drivers-470-server source package in Impish:
Fix Released
Status in nvidia-graphics-drivers-495 source package in Impish:
New
Bug description:
As per the subject, the update includes fixes for the following CVEs:
CVE-2022-21813
CVE-2022-21814
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fabric-manager-450/+bug/1957790/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1960933] [NEW] rtw89_pci constantly drops connection with old firmware
Public bug reported: This was on a new Lenovo P14s Gen2 AMD. I'm using Ubuntu 21.10 (impish) The current linux-firmware package (1.201.4+1.201.3) ships with realtek rtw89_pci firmware (/lib/firmware/rtw89/rtw8852a_fw.bin) version v0.13.8.0. My wifi chip wasn't able to keep a connection for more than a minute when connected to a Rodgers "Advanced Wi-Fi Modem". I searched around tried disabling the power_save and stuff. But that had little to no effect. I was about to open an issue on the upstream project and did a last ditch attempt to see if there were any firmware updates... I found linux-firmware.git and it had two newer versions! - v0.13.30.0 (was submitted in May 2021, but it took until october 2021 to show up) https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/rtw89/rtw8852a_fw.bin?id=ec17b637b7ab928ca7ebc0389e0e3921f1cc7d17 - v0.13.33.0 (was submitted in November 2021 and got merged in December 2021): https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/rtw89/rtw8852a_fw.bin?id=4a7e1f5cabaebe5c044b94b91149f35471d1e983 I've downloaded and installed the latest "v0.13.33.0" on a whim and rebooted. And what a pleasant surprise: Instantly, my wifi connection lasted until the rest of the day. Could you please consider updating this realtek firmware in the next release? Thanks! ** Affects: linux-firmware (Ubuntu) Importance: Undecided Status: New ** Tags: rtw89 -- 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/1960933 Title: rtw89_pci constantly drops connection with old firmware Status in linux-firmware package in Ubuntu: New Bug description: This was on a new Lenovo P14s Gen2 AMD. I'm using Ubuntu 21.10 (impish) The current linux-firmware package (1.201.4+1.201.3) ships with realtek rtw89_pci firmware (/lib/firmware/rtw89/rtw8852a_fw.bin) version v0.13.8.0. My wifi chip wasn't able to keep a connection for more than a minute when connected to a Rodgers "Advanced Wi-Fi Modem". I searched around tried disabling the power_save and stuff. But that had little to no effect. I was about to open an issue on the upstream project and did a last ditch attempt to see if there were any firmware updates... I found linux-firmware.git and it had two newer versions! - v0.13.30.0 (was submitted in May 2021, but it took until october 2021 to show up) https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/rtw89/rtw8852a_fw.bin?id=ec17b637b7ab928ca7ebc0389e0e3921f1cc7d17 - v0.13.33.0 (was submitted in November 2021 and got merged in December 2021): https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/rtw89/rtw8852a_fw.bin?id=4a7e1f5cabaebe5c044b94b91149f35471d1e983 I've downloaded and installed the latest "v0.13.33.0" on a whim and rebooted. And what a pleasant surprise: Instantly, my wifi connection lasted until the rest of the day. Could you please consider updating this realtek firmware in the next release? Thanks! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1960933/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1960808] Re: Suspend does not work, trying twice crashes GUI. Hibernation crashes GUI when having have opened a non default firefox profile
** Description changed: When trying to suspend my Laptop (clicking suspend in the drop down menu) the screen goes black and all lights go out, but then everything springs back to life and the computer shows me the login screen again. When clicking suspend (in the drop down menu) again the GUI crashes(Only if I haven't logged back in). When restarting the GUI is back. The same problem occurs if the computer hibernates. But this only occurs when having opened a profile that is not the default one in Firefox. Hibernating without having done anything works just fine. (I am up to date with every package 14.2.2022) I am using the Xorg driver. 1) $lsb_release -rd Description: Ubuntu 20.04.3 LTS Release: 20.04 2) $apt-cache policy gnome-power-manager gnome-power-manager: Installed: 3.32.0-2 Candidate: 3.32.0-2 Version table: *** 3.32.0-2 500 500 http://de.archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status $apt-cache policy pm-utils pm-utils: Installed: (none) Candidate: 1.4.1-19 Version table: 1.4.1-19 500 500 http://de.archive.ubuntu.com/ubuntu focal/universe amd64 Packages 500 http://de.archive.ubuntu.com/ubuntu focal/universe i386 Packages ^ Is pm-utils the issue ? It is not. I installed the Package with Synaptic Package manager but there is no change 3) I expected my computer to hibernate/Suspend. 4) It did not. + I am unable to attach the log files as apport-collect requires confirmation in a browser. I do not have access to a browser in a crashed GUI. If you have a way around this please don't hesitate to tell me. I am happy to help. ** 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/1960808 Title: Suspend does not work, trying twice crashes GUI. Hibernation crashes GUI when having have opened a non default firefox profile Status in linux package in Ubuntu: Confirmed Bug description: When trying to suspend my Laptop (clicking suspend in the drop down menu) the screen goes black and all lights go out, but then everything springs back to life and the computer shows me the login screen again. When clicking suspend (in the drop down menu) again the GUI crashes(Only if I haven't logged back in). When restarting the GUI is back. The same problem occurs if the computer hibernates. But this only occurs when having opened a profile that is not the default one in Firefox. Hibernating without having done anything works just fine. (I am up to date with every package 14.2.2022) I am using the Xorg driver. 1) $lsb_release -rd Description: Ubuntu 20.04.3 LTS Release: 20.04 2) $apt-cache policy gnome-power-manager gnome-power-manager: Installed: 3.32.0-2 Candidate: 3.32.0-2 Version table: *** 3.32.0-2 500 500 http://de.archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status $apt-cache policy pm-utils pm-utils: Installed: (none) Candidate: 1.4.1-19 Version table: 1.4.1-19 500 500 http://de.archive.ubuntu.com/ubuntu focal/universe amd64 Packages 500 http://de.archive.ubuntu.com/ubuntu focal/universe i386 Packages ^ Is pm-utils the issue ? It is not. I installed the Package with Synaptic Package manager but there is no change 3) I expected my computer to hibernate/Suspend. 4) It did not. I am unable to attach the log files as apport-collect requires confirmation in a browser. I do not have access to a browser in a crashed GUI. If you have a way around this please don't hesitate to tell me. I am happy to help. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1960808/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1960826] Re: NFSv4 performance problem with newer kernels
OK, to set a random nfs4_unique_id you can just cat/echo a string like this: cat /proc/sys/kernel/random/uuid |tr -d '\n' > /sys/module/nfs/parameters/nfs4_unique_id so long as you do this before your first NFS mount, which in my case is not a problem. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1960826 Title: NFSv4 performance problem with newer kernels Status in linux package in Ubuntu: Confirmed Bug description: I am seeing an issue with NFSv4 performance on Ubuntu 20.04.3 LTS on both clients and server (tested kernels 5.4 to 5.16), where the server is connected by 10Gbit Ethernet and with multiple clients connected by 1Gbit. I am reading a large file from an NFS mount via "dd" sending output to /dev/null with bs=4096. Using default sysctl and mount options I am seeing speeds maxing out below 1Gbit/sec. If I force NFSv3 I see speeds close to 10Gbit/sec with sufficient clients connected. I also see no issue with Ubuntu 16.04 (when used for both server and clients) in conjunction with NFSv4. I have attached the output from two iftop's which shows the status when using NFSv4 and when using NFSv3, in the NFSv4 you can clearly see one client reading at max speed and all the others apparently throttling back to practically nothing. I have additionally tested a range of mount options, which made no difference, BBR congestion control which made no difference and the following kernel settings which also made no difference: net.core.netdev_max_backlog=25 net.core.rmem_max=4194304 net.core.wmem_max=4194304 net.core.rmem_default=4194304 net.core.wmem_default=4194304 net.core.optmem_max=4194304 net.ipv4.tcp_rmem=4096 87380 4194304 net.ipv4.tcp_wmem=4096 65536 4194304 net.ipv4.tcp_mem=786432 1048576 26777216 net.ipv4.udp_mem=1529892 2039859 3059784 net.ipv4.udp_rmem_min=16384 net.ipv4.udp_wmem_min=16384 The problem is seen on dissimilar hardware, ie this problem exists when testing with an HP DL380 G10 with Mellanox 10Gbit Ethernet connected to Cisco switch, and also on a Dell R430 with Broadcom 10Gbit Ethernet connected to a Netgear switch (just to name two of several configurations that have been tested). The clients vary in each test case also, but are desktop PCs and laptops. --- ProblemType: Bug AlsaDevices: total 0 crw-rw+ 1 root audio 116, 1 Feb 15 10:23 seq crw-rw+ 1 root audio 116, 33 Feb 15 10:23 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: pass DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2022-02-14 (0 days ago) InstallationMedia: Ubuntu-Server 20.04.2 LTS "Focal Fossa" - Release amd64 (20210201.2) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: Dell Inc. PowerEdge R430 Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 mgag200drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-28-generic root=UUID=d227a745-134e-4633-9c26-bcc062655f95 ro ProcVersionSignature: Ubuntu 5.13.0-28.31~20.04.1-generic 5.13.19 RelatedPackageVersions: linux-restricted-modules-5.13.0-28-generic N/A linux-backports-modules-5.13.0-28-generic N/A linux-firmware 1.187.26 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal uec-images Uname: Linux 5.13.0-28-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 06/07/2021 dmi.bios.release: 2.13 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.13.0 dmi.board.name: 0CN7X8 dmi.board.vendor: Dell Inc. dmi.board.version: A04 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.13.0:bd06/07/2021:br2.13:svnDellInc.:pnPowerEdgeR430:pvr:rvnDellInc.:rn0CN7X8:rvrA04:cvnDellInc.:ct23:cvr:skuSKU=NotProvided;ModelName=PowerEdgeR430: dmi.product.name: PowerEdge R430 dmi.product.sku: SKU=NotProvided;ModelName=PowerEdge R430 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1960826/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1960324] Re: Kernel does not contain fixes for iostat for md devices
** Tags added: vroc ** Summary changed: - Kernel does not contain fixes for iostat for md devices + [VROC] Kernel does not contain fixes for iostat for md devices -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1960324 Title: [VROC] Kernel does not contain fixes for iostat for md devices Status in linux-hwe-5.13 package in Ubuntu: New Bug description: Hello, I noticed that kernel which was used in ubuntu 22.04 (hwe-5.13) does not contain fixes for IO statistics for md devices. IO statistics for md devices were added to kernel 5.10 (https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=41d2d848e5c09209bdb57ff9c0ca34075e22783d) but then bug for double fault was reported and this patch was reverted by Guoqing Jiang (https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=ad3fc798800fb7ca04c1dfc439dba946818048d8). Guoqing Jiang added series of patches which fixes problem and adds IO stats for md devices on top on the revert patch: - first commit from series: 10764815ff4728d2c57da677cd5d3dd6f446cf5f (https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=10764815ff4728d2c57da677cd5d3dd6f446cf5f) - last one: de3ea66e9d23a34eef5e17f960d6473f78a1c54b (https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=de3ea66e9d23a34eef5e17f960d6473f78a1c54b) I checked that kernel used in ubuntu 22.04 contains only patch with revert - iostat does not report for md devices (https://kernel.ubuntu.com/git/ubuntu/ubuntu-focal.git/log/?h=hwe-5.13&qt=author&q=Guoqing+Jiang) Please consider adding series of patches described above. Regards, Kinga Tanska To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.13/+bug/1960324/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1960826] Re: NFSv4 performance problem with newer kernels
I have found the root cause, in my test environment the clients are all clones with unique machine-id but the same hostname. The issue is resolve by either changing the hostname of each client, or by setting a unique value here: echo options nfs nfs4_unique_id=[string] > /etc/modprobe.d/nfsclient.conf In my production environment the clients all share the same NFS root, and I'm not sure how to set a random value in nfsclient.conf (I tried nfs4_unique_id=`cat /proc/sys/kernel/random/uuid` but this doesn't work). Currently I can work around by setting a random hostname. If anyone can suggest how to do this via nfsclient.conf instead that might be neater. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1960826 Title: NFSv4 performance problem with newer kernels Status in linux package in Ubuntu: Confirmed Bug description: I am seeing an issue with NFSv4 performance on Ubuntu 20.04.3 LTS on both clients and server (tested kernels 5.4 to 5.16), where the server is connected by 10Gbit Ethernet and with multiple clients connected by 1Gbit. I am reading a large file from an NFS mount via "dd" sending output to /dev/null with bs=4096. Using default sysctl and mount options I am seeing speeds maxing out below 1Gbit/sec. If I force NFSv3 I see speeds close to 10Gbit/sec with sufficient clients connected. I also see no issue with Ubuntu 16.04 (when used for both server and clients) in conjunction with NFSv4. I have attached the output from two iftop's which shows the status when using NFSv4 and when using NFSv3, in the NFSv4 you can clearly see one client reading at max speed and all the others apparently throttling back to practically nothing. I have additionally tested a range of mount options, which made no difference, BBR congestion control which made no difference and the following kernel settings which also made no difference: net.core.netdev_max_backlog=25 net.core.rmem_max=4194304 net.core.wmem_max=4194304 net.core.rmem_default=4194304 net.core.wmem_default=4194304 net.core.optmem_max=4194304 net.ipv4.tcp_rmem=4096 87380 4194304 net.ipv4.tcp_wmem=4096 65536 4194304 net.ipv4.tcp_mem=786432 1048576 26777216 net.ipv4.udp_mem=1529892 2039859 3059784 net.ipv4.udp_rmem_min=16384 net.ipv4.udp_wmem_min=16384 The problem is seen on dissimilar hardware, ie this problem exists when testing with an HP DL380 G10 with Mellanox 10Gbit Ethernet connected to Cisco switch, and also on a Dell R430 with Broadcom 10Gbit Ethernet connected to a Netgear switch (just to name two of several configurations that have been tested). The clients vary in each test case also, but are desktop PCs and laptops. --- ProblemType: Bug AlsaDevices: total 0 crw-rw+ 1 root audio 116, 1 Feb 15 10:23 seq crw-rw+ 1 root audio 116, 33 Feb 15 10:23 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: pass DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2022-02-14 (0 days ago) InstallationMedia: Ubuntu-Server 20.04.2 LTS "Focal Fossa" - Release amd64 (20210201.2) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: Dell Inc. PowerEdge R430 Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 mgag200drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-28-generic root=UUID=d227a745-134e-4633-9c26-bcc062655f95 ro ProcVersionSignature: Ubuntu 5.13.0-28.31~20.04.1-generic 5.13.19 RelatedPackageVersions: linux-restricted-modules-5.13.0-28-generic N/A linux-backports-modules-5.13.0-28-generic N/A linux-firmware 1.187.26 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal uec-images Uname: Linux 5.13.0-28-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 06/07/2021 dmi.bios.release: 2.13 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.13.0 dmi.board.name: 0CN7X8 dmi.board.vendor: Dell Inc. dmi.board.version: A04 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.13.0:bd06/07/2021:br2.13:svnDellInc.:pnPowerEdgeR430:pvr:rvnDellInc.:rn0CN7X8:rvrA04:cvnDellInc.:ct23:cvr:skuSKU=NotProvided;ModelName=PowerEdgeR430: dmi.product.name: PowerEdge R430 dmi.product.sku: SKU=NotProvided;ModelName=PowerEdge R430 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/
[Kernel-packages] [Bug 1960926] [NEW] Installation on RAID volume fails - ubuntu 22.04
Public bug reported:
Installation on RAID volume created in uefi fails with error
"ValueError: devices or container for raid must be specified". Syslog
contains error log with curtin:
Jan 20 08:58:16 ubuntu-server subiquity_log.4517[4968]: start:
cmd-install/stage-partitioning/builtin/cmd-block-meta: configuring raid:
raid-md127
Jan 20 08:58:16 ubuntu-server subiquity_log.4517[4968]: An error occured
handling 'raid-md127': ValueError - devices or container for raid must be
specified
Jan 20 08:58:16 ubuntu-server subiquity_log.4517[4968]: finish:
cmd-install/stage-partitioning/builtin/cmd-block-meta: FAIL: configuring raid:
raid-md127
Jan 20 08:58:16 ubuntu-server subiquity_log.4517[4968]: TIMED BLOCK_META: 0.647
Jan 20 08:58:16 ubuntu-server subiquity_log.4517[4968]: finish:
cmd-install/stage-partitioning/builtin/cmd-block-meta: FAIL: curtin command
block-meta
Jan 20 08:58:16 ubuntu-server subiquity_log.4517[4968]: Traceback (most recent
call last):
Jan 20 08:58:16 ubuntu-server subiquity_log.4517[4968]: File
"/snap/subiquity/2974/lib/python3.8/site-packages/curtin/commands/main.py",
line 202, in main
Jan 20 08:58:16 ubuntu-server subiquity_log.4517[4968]: ret =
args.func(args)
Jan 20 08:58:16 ubuntu-server subiquity_log.4517[4968]: File
"/snap/subiquity/2974/lib/python3.8/site-packages/curtin/log.py", line 97, in
wrapper
Jan 20 08:58:16 ubuntu-server subiquity_log.4517[4968]: return
log_time("TIMED %s: " % msg, func, *args, **kwargs)
Jan 20 08:58:16 ubuntu-server subiquity_log.4517[4968]: File
"/snap/subiquity/2974/lib/python3.8/site-packages/curtin/log.py", line 79, in
log_time
Jan 20 08:58:16 ubuntu-server subiquity_log.4517[4968]: return func(*args,
**kwargs)
Jan 20 08:58:16 ubuntu-server subiquity_log.4517[4968]: File
"/snap/subiquity/2974/lib/python3.8/site-packages/curtin/commands/block_meta.py",
line 117, in block_meta
Jan 20 08:58:16 ubuntu-server subiquity_log.4517[4968]: return
meta_custom(args)
Jan 20 08:58:16 ubuntu-server subiquity_log.4517[4968]: File
"/snap/subiquity/2974/lib/python3.8/site-packages/curtin/commands/block_meta.py",
line 2024, in meta_custom
Jan 20 08:58:16 ubuntu-server subiquity_log.4517[4968]: handler(command,
storage_config_dict)
Jan 20 08:58:16 ubuntu-server subiquity_log.4517[4968]: File
"/snap/subiquity/2974/lib/python3.8/site-packages/curtin/commands/block_meta.py",
line 1586, in raid_handler
Jan 20 08:58:16 ubuntu-server subiquity_log.4517[4968]: raise
ValueError("devices or container for raid must be specified")
Jan 20 08:58:16 ubuntu-server subiquity_log.4517[4968]: ValueError: devices or
container for raid must be specified
Jan 20 08:58:16 ubuntu-server subiquity_log.4517[4968]: devices or container
for raid must be specified
Jan 20 08:58:16 ubuntu-server subiquity_log.4517[4968]: builtin command failed
Jan 20 08:58:16 ubuntu-server subiquity_log.4517[4968]: finish:
cmd-install/stage-partitioning/builtin: FAIL: running 'curtin block-meta simple'
Jan 20 08:58:16 ubuntu-server curtin_event.4517.3[4968]: finish:
cmd-install/stage-partitioning/builtin: FAIL: running 'curtin block-meta simple'
Jan 20 08:58:16 ubuntu-server subiquity_log.4517[4968]: builtin took 1.288
seconds
Jan 20 08:58:16 ubuntu-server subiquity_log.4517[4968]: stage_partitioning took
1.289 seconds
Jan 20 08:58:16 ubuntu-server subiquity_log.4517[4968]: finish:
cmd-install/stage-partitioning: FAIL: configuring storage
Jan 20 08:58:16 ubuntu-server curtin_event.4517.3[4968]: finish:
cmd-install/stage-partitioning: FAIL: configuring storage
Jan 20 08:58:16 ubuntu-server subiquity_log.4517[4968]: curtin: Installation
failed with exception: Unexpected error while running command.
Jan 20 08:58:16 ubuntu-server subiquity_log.4517[4968]: Command: ['curtin',
'block-meta', 'simple']
Jan 20 08:58:16 ubuntu-server subiquity_log.4517[4968]: Exit code: 3
** Affects: curtin (Ubuntu)
Importance: Undecided
Status: New
** Tags: vroc
** Description changed:
Installation on RAID volume created in uefi fails with error
"ValueError: devices or container for raid must be specified". Syslog
contains error log with curtin:
+ Jan 20 08:58:16 ubuntu-server subiquity_log.4517[4968]: start:
cmd-install/stage-partitioning/builtin/cmd-block-meta: configuring raid:
raid-md127
+ Jan 20 08:58:16 ubuntu-server subiquity_log.4517[4968]: An error occured
handling 'raid-md127': ValueError - devices or container for raid must be
specified
+ Jan 20 08:58:16 ubuntu-server subiquity_log.4517[4968]: finish:
cmd-install/stage-partitioning/builtin/cmd-block-meta: FAIL: configuring raid:
raid-md127
+ Jan 20 08:58:16 ubuntu-server subiquity_log.4517[4968]: TIMED BLOCK_META:
0.647
Jan 20 08:58:16 ubuntu-server subiquity_log.4517[4968]: finish:
cmd-install/stage-partitioning/builtin/cmd-block-meta: FAIL: curtin command
block-meta
Jan 20 08:58:16 ubuntu-server subiquity_log.4517[4968]: Traceback (most
recent call last):
Jan 20 08:5
[Kernel-packages] [Bug 1911917] Re: Kernel general protection fault when using NFQUEUE iptables target
I could not reproduce the issue with the following newer kernels on Bionic: - linux-image-5.4.0-99-generic - linux-image-5.4.0-80-generic - linux-image-5.4.0-70-generic Kernel linux-image-5.4.0-65-generic still crashing, so this issue has been fixed between 5.4.0-65 and 5.4.0-70. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1911917 Title: Kernel general protection fault when using NFQUEUE iptables target Status in linux package in Ubuntu: Incomplete Bug description: When a packet is forwarded through an Ubuntu Focal host with kernel version 5.4.0-62-generic and NFQUEUE target is used in mangle PREROUTING and POSTROUTING, the kernel crashes. Current Focal linux- generic-hwe-20.04 kernel (5.8.0.38.43) is not affected. How to reproduce: - Set up Focal host with a packet forwarding scenario (at least two interface: client subnet -> server subnet). sudo sysctl net.ipv4.ip_forward=1 sudo apt-get install build-essential python-dev libnetfilter-queue-dev git clone https://github.com/kti/python-netfilterqueue.git cd python-netfilterqueue sudo python setup.py install cd examples sudo iptables-restore < iptables.conf.nfq # From the comment attachment sudo ./print_and_accept.py - Run packet through the host. Stack trace: [ 856.055991] general protection fault: [#1] SMP PTI [ 856.151292] CPU: 0 PID: 722 Comm: nfq-cpp Kdump: loaded Tainted: G W 5.4.0-62-generic #70-Ubuntu [ 856.152503] Hardware name: innotek GmbH VirtualBox/VirtualBox, BIOS VirtualBox 12/01/2006 [ 856.153448] RIP: 0010:validate_xmit_skb_list+0x34/0x70 [ 856.154058] Code: 57 41 56 41 55 41 54 53 48 85 ff 74 45 49 89 ff 49 89 f4 49 89 d5 45 31 f6 eb 0c 48 89 03 48 8b 58 08 4d 85 ff 74 2e 4c 89 ff <4d> 8b 3f 4c 89 ea 4c 89 e6 48 c7 07 00 00 00 00 48 89 7f 08 e8 73 [ 856.156228] RSP: 0018:a061404776d8 EFLAGS: 00010286 [ 856.156868] RAX: 8d1c2fa6d900 RBX: 8d1c2fa6d900 RCX: 9f32fd20 [ 856.157715] RDX: a0614047771b RSI: 00800013ca29 RDI: dead0100 [ 856.361073] RBP: a06140477700 R08: 8d1c2fd6a8ac R09: 0001 [ 856.543925] R10: 8d1c30373870 R11: a061404779f8 R12: 8d1c29afb000 [ 856.544761] R13: a0614047771b R14: 8d1c2fa6d900 R15: dead0100 [ 856.545586] FS: 7fd887366740() GS:8d1c3fc0() knlGS: [ 856.546514] CS: 0010 DS: ES: CR0: 80050033 [ 856.547206] CR2: 7ffcbb2be8d8 CR3: 6cace001 CR4: 000606f0 [ 856.548029] Call Trace: [ 856.548349] sch_direct_xmit+0x150/0x340 [ 856.548824] __dev_queue_xmit+0x57b/0x8e0 [ 856.549353] dev_queue_xmit+0x10/0x20 [ 856.549841] neigh_resolve_output+0x110/0x1c0 [ 856.550426] ip_finish_output2+0x19b/0x590 [ 856.550990] ? nf_ct_del_from_dying_or_unconfirmed_list+0x34/0x70 [nf_conntrack] [ 856.551929] __ip_finish_output+0xbf/0x1e0 [ 856.552464] ip_finish_output+0x2d/0xb0 [ 856.552972] nf_reinject+0x12e/0x200 [ 856.553452] nfqnl_reinject+0x52/0x60 [nfnetlink_queue] [ 856.554110] nfqnl_recv_verdict+0x289/0x4b0 [nfnetlink_queue] [ 856.554826] ? __nla_validate_parse+0x116/0x140 [ 856.555409] nfnetlink_rcv_msg+0x172/0x2a0 [nfnetlink] [ 856.556062] ? __switch_to_asm+0x40/0x70 [ 856.556579] ? __switch_to_asm+0x34/0x70 [ 856.681025] ? __switch_to_asm+0x40/0x70 [ 856.811662] ? __switch_to_asm+0x34/0x70 [ 856.812216] ? __switch_to_asm+0x40/0x70 [ 856.812770] ? __switch_to_asm+0x34/0x70 [ 856.813324] ? __switch_to_asm+0x40/0x70 [ 856.813879] ? __switch_to_asm+0x34/0x70 [ 856.814434] ? __switch_to_asm+0x40/0x70 [ 856.815009] ? __switch_to_asm+0x34/0x70 [ 856.815567] ? nfnetlink_net_exit_batch+0x70/0x70 [nfnetlink] [ 856.816327] netlink_rcv_skb+0x50/0x120 [ 856.816859] nfnetlink_rcv+0x6c/0x14b [nfnetlink] [ 856.817463] netlink_unicast+0x187/0x220 [ 856.817982] netlink_sendmsg+0x222/0x3e0 [ 856.818502] sock_sendmsg+0x65/0x70 [ 856.818973] sys_sendmsg+0x212/0x280 [ 856.819491] ___sys_sendmsg+0x88/0xd0 [ 856.820020] ? sock_recvmsg+0x70/0x80 [ 856.831151] ? __sys_recvfrom+0x19e/0x1d0 [ 856.831715] __sys_sendmsg+0x5c/0xa0 [ 856.832197] __x64_sys_sendmsg+0x1f/0x30 [ 856.832716] do_syscall_64+0x57/0x190 [ 856.833207] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [ 856.833848] RIP: 0033:0x7fd8875e7747 [ 856.834331] Code: 64 89 02 48 c7 c0 ff ff ff ff eb bb 0f 1f 80 00 00 00 00 f3 0f 1e fa 64 8b 04 25 18 00 00 00 85 c0 75 10 b8 2e 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 51 c3 48 83 ec 28 89 54 24 1c 48 89 74 24 10 [ 856.836582] RSP: 002b:7ffcbb2be708 EFLAGS: 0246 ORIG_RAX: 002e [ 856.837563] RAX: ffda RBX: 7ffcbb2be7b0 RCX: 7fd8875e7747 [ 856.838452] RDX: RS
[Kernel-packages] [Bug 1944080] Re: [fan-network] Race-condition between "apt update" and dhcp request causes cloud-init error
** Changed in: juju Milestone: 2.9.25 => 2.9.26 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to ubuntu-fan in Ubuntu. https://bugs.launchpad.net/bugs/1944080 Title: [fan-network] Race-condition between "apt update" and dhcp request causes cloud-init error Status in OpenStack RabbitMQ Server Charm: Invalid Status in juju: Triaged Status in ubuntu-fan package in Ubuntu: New Bug description: Hi, Using manual provider on top of VMWare. Juju: 2.9.14 VM: Focal Containers: Bionic I've noticed that, in a given Focal host, 2x Bionic containers may have different behavior: one successfully completes cloud-init whereas the other fails. The failed container errors at "apt update" in cloud- init with: Err:1 http://archive.ubuntu.com/ubuntu bionic InRelease Something wicked happened resolving 'PROXY_IP:' (-9 - Address family for hostname not supported) (Likely this is the line where it breaks: https://github.com/Debian/apt/blob/766b24b7f7484751950c76bc66d3d6cdeaf949a5/methods/connect.cc#L436) Failed container, full cloud-init-output.log: https://pastebin.canonical.com/p/hKNw49mvJP/ Successful container, full cloud-init-output.log: https://pastebin.canonical.com/p/P6MZdQPrWd/ Host syslog: https://pastebin.canonical.com/p/jjMmWRFd9y/ I can see that, on the host, dnsmasq served the FAN IP to the broken container after the "apt-update" was called. - FAILED CONTAINER -: Sep 19 13:02:14 lma-stack-2 dnsmasq-dhcp[1243]: DHCPOFFER(fan-252) 252.252.15.198 00:16:3e:da:dd:c4 apt-update on cloud-init was ran: Cloud-init v. 21.2-3-g899bfaa9-0ubuntu2~18.04.1 running 'modules:config' at Sun, 19 Sep 2021 13:02:13 +. Up 3.90 seconds. - SUCCESSFUL CONTAINER -: Sep 19 13:09:40 lma-stack-2 dnsmasq-dhcp[1243]: DHCPOFFER(fan-252) 252.252.15.253 00:16:3e:d7:6b:ef apt-update on cloud-init was ran: Cloud-init v. 21.2-3-g899bfaa9-0ubuntu2~18.04.1 running 'modules:config' at Sun, 19 Sep 2021 13:10:10 +. Up 35.99 seconds. In the case of the Failed Container, the DHCPOFFER arrived 1s after the "apt update" was requested, whereas the Successful Container logged a DHCPOFFER 30s before the "apt update". To manage notifications about this bug go to: https://bugs.launchpad.net/charm-rabbitmq-server/+bug/1944080/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1960182] s390/cpumf: Support for CPU Measurement Facility CSVN 7 for Ubuntu 20
--- Comment on attachment From tmri...@de.ibm.com 2022-02-15 07:48 EDT--- Reworked patch for ubuntu 20.04 branch master-next ** Attachment added: "s390/cpumf: Support for CPU Measurement Facility CSVN 7 for Ubuntu 20" https://bugs.launchpad.net/bugs/1960182/+attachment/5561026/+files/0001-s390-cpumf-Support-for-CPU-Measurement-Facility-CSVN.patch -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1960182 Title: [UBUNTU 20.04] kernel: Add support for CPU-MF counter second version 7 Status in linux package in Ubuntu: New Bug description: Fix CPU-MF error on new IBM Z Hardware by adding support for CPU-MF counter second version 7 Error Symptom: Daemon cpacfstatsd fails on start up of the system with this error message cpacfstatsd: Event DEA_FUNCTIONS for pmu cpum_cf not found (2:No such file or directory) Problem: When the CPU Measurement facility device driver is initialized during kernel boot, it reads out the CPU Measurement facility counter hardware first and second version numbers. Depending on these numbers the device driver exports attributes in the sysfs directory /sys/devices/cpum_cf/events. When the CPM-MF second version number is not known, no attributes of the crypto counter set are exported. However the cpacfstatsd program scans the sysfs directory /sys/devices/cpum_cf/events for attribute files of the crypto counter set, for example attribute file DEA_FUNCTIONS and others. Solution: Add support for the new CPU-MF Measurement counter facility second version number 7. This number then exports the crypto counter set in directory directory /sys/devices/cpum_cf/events. Also add support for limited samples. These hardware samples contain all zeroes and are of no value when using the CPU Measurement Facility sampling hardware. Drop these samples when the limited sampled bit is set in the sample descriptor. Reproduction: Run command ls -l /sys/devices/cpum_cf/events | fgrep DEA DEA_BLOCKED_CYCLES DEA_BLOCKED_FUNCTIONS DEA_CYCLES DEA_FUNCTIONS When there is no output at all the attributes files for the crypto counter set have not been exported. If above output is visible, the described problem does not show up. Upstream-ID: a87b0fd4f9003f8521226e226cf92b18147b3519 745f5d20e7936931f924410f32d8b0e599b5990e Problem-ID:196017 Preventive:yes Reported: Christian Rund SupportTicket: - Reference: - Date: 2022-01-20 Author:Thomas Richter Component: kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1960182/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1960182] s390/cpumf: Support for CPU Measurement Sampling Facility LS bit
--- Comment on attachment From tmri...@de.ibm.com 2022-02-15 07:49 EDT--- This is the upstream patch which applies with 3 lines off message ** Attachment added: "s390/cpumf: Support for CPU Measurement Sampling Facility LS bit" https://bugs.launchpad.net/bugs/1960182/+attachment/5561027/+files/0001-s390-cpumf-Support-for-CPU-Measurement-Sampling-Faci.patch -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1960182 Title: [UBUNTU 20.04] kernel: Add support for CPU-MF counter second version 7 Status in linux package in Ubuntu: New Bug description: Fix CPU-MF error on new IBM Z Hardware by adding support for CPU-MF counter second version 7 Error Symptom: Daemon cpacfstatsd fails on start up of the system with this error message cpacfstatsd: Event DEA_FUNCTIONS for pmu cpum_cf not found (2:No such file or directory) Problem: When the CPU Measurement facility device driver is initialized during kernel boot, it reads out the CPU Measurement facility counter hardware first and second version numbers. Depending on these numbers the device driver exports attributes in the sysfs directory /sys/devices/cpum_cf/events. When the CPM-MF second version number is not known, no attributes of the crypto counter set are exported. However the cpacfstatsd program scans the sysfs directory /sys/devices/cpum_cf/events for attribute files of the crypto counter set, for example attribute file DEA_FUNCTIONS and others. Solution: Add support for the new CPU-MF Measurement counter facility second version number 7. This number then exports the crypto counter set in directory directory /sys/devices/cpum_cf/events. Also add support for limited samples. These hardware samples contain all zeroes and are of no value when using the CPU Measurement Facility sampling hardware. Drop these samples when the limited sampled bit is set in the sample descriptor. Reproduction: Run command ls -l /sys/devices/cpum_cf/events | fgrep DEA DEA_BLOCKED_CYCLES DEA_BLOCKED_FUNCTIONS DEA_CYCLES DEA_FUNCTIONS When there is no output at all the attributes files for the crypto counter set have not been exported. If above output is visible, the described problem does not show up. Upstream-ID: a87b0fd4f9003f8521226e226cf92b18147b3519 745f5d20e7936931f924410f32d8b0e599b5990e Problem-ID:196017 Preventive:yes Reported: Christian Rund SupportTicket: - Reference: - Date: 2022-01-20 Author:Thomas Richter Component: kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1960182/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1960820] Re: linux-azure: Missing ext4 commits
** Changed in: linux-azure (Ubuntu Focal) Status: In Progress => Fix Committed ** Changed in: linux-azure (Ubuntu Impish) Status: In Progress => Fix Committed -- 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/1960820 Title: linux-azure: Missing ext4 commits Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure source package in Focal: Fix Committed Status in linux-azure source package in Impish: Fix Committed Status in linux-azure source package in Jammy: Fix Released Bug description: SRU Justification [Impact] Microsoft has a test that checks for missing file system commits; It has detected that these commits are not present in Azure tuned kernels: 0f2f87d51aebcf71a709b52f661d681594c7dffa ext4: prevent partial update of the extent blocks 9c6e071913792d80894cd0be98cc3c4b770e26d3 ext4: check for inconsistent extents between index and leaf block 8dd27fecede55e8a4e67eef2878040ecad0f0d33 ext4: check for out-of-order index extents in ext4_valid_extent_entries() [Test Case] Microsoft tested [Where things could go wrong] Ext4 file systems could have problems. [Other Info] SF: #00324445 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1960820/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1960182] Comment bridged from LTC Bugzilla
--- Comment From tmri...@de.ibm.com 2022-02-15 07:46 EDT--- I have downloaded the master-next branch from ubuntu version 20. I used this repository: Fetch URL: https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/focal The patches needed to support the new machine are already upstream since 5.17.0rc1: 1. Patch a87b0fd4f9003f8521226e226cf92b18147b3519 Adds support for the CPU Measurement Counter Facility second version number 7. 2. Patch 745f5d20e7936931f924410f32d8b0e599b5990e s390/cpumf: Support for CPU Measurement Sampling Facility LS bit The first upstream patch (commit a87b0fd4f900) does not apply and I had to rework it. I have attached the reworked version and now it applies and compiles. The second upstream patch (commit 745f5d20e7936) applies clean (with 3 lines off). I also have attached the second patch for completeness. I consider this item complete. Please let me know if you have any questions. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1960182 Title: [UBUNTU 20.04] kernel: Add support for CPU-MF counter second version 7 Status in linux package in Ubuntu: New Bug description: Fix CPU-MF error on new IBM Z Hardware by adding support for CPU-MF counter second version 7 Error Symptom: Daemon cpacfstatsd fails on start up of the system with this error message cpacfstatsd: Event DEA_FUNCTIONS for pmu cpum_cf not found (2:No such file or directory) Problem: When the CPU Measurement facility device driver is initialized during kernel boot, it reads out the CPU Measurement facility counter hardware first and second version numbers. Depending on these numbers the device driver exports attributes in the sysfs directory /sys/devices/cpum_cf/events. When the CPM-MF second version number is not known, no attributes of the crypto counter set are exported. However the cpacfstatsd program scans the sysfs directory /sys/devices/cpum_cf/events for attribute files of the crypto counter set, for example attribute file DEA_FUNCTIONS and others. Solution: Add support for the new CPU-MF Measurement counter facility second version number 7. This number then exports the crypto counter set in directory directory /sys/devices/cpum_cf/events. Also add support for limited samples. These hardware samples contain all zeroes and are of no value when using the CPU Measurement Facility sampling hardware. Drop these samples when the limited sampled bit is set in the sample descriptor. Reproduction: Run command ls -l /sys/devices/cpum_cf/events | fgrep DEA DEA_BLOCKED_CYCLES DEA_BLOCKED_FUNCTIONS DEA_CYCLES DEA_FUNCTIONS When there is no output at all the attributes files for the crypto counter set have not been exported. If above output is visible, the described problem does not show up. Upstream-ID: a87b0fd4f9003f8521226e226cf92b18147b3519 745f5d20e7936931f924410f32d8b0e599b5990e Problem-ID:196017 Preventive:yes Reported: Christian Rund SupportTicket: - Reference: - Date: 2022-01-20 Author:Thomas Richter Component: kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1960182/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1960361] Re: hwmon: k10temp updates for AMD Genoa in 22.04
** Changed in: linux (Ubuntu Jammy) 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/1960361 Title: hwmon: k10temp updates for AMD Genoa in 22.04 Status in linux package in Ubuntu: Fix Committed Status in linux source package in Jammy: Fix Committed Bug description: Patch pull request to include additional support for AMD Genoa in 22.04 f707bcb5d1cb 5.17 hwmon: (k10temp) Remove unused definitions 3cf90efa1367 5.17 hwmon: (k10temp) Add support for AMD Family 19h Models 10h-1Fh and A0h-AFh 8bb050cd5cf4 5.17 hwmon: (k10temp) Support up to 12 CCDs on AMD Family of processors To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1960361/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1960362] Re: EDAC update for AMD Genoa support in 22.04
** Changed in: linux (Ubuntu Jammy) 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/1960362 Title: EDAC update for AMD Genoa support in 22.04 Status in linux package in Ubuntu: Fix Committed Status in linux source package in Jammy: Fix Committed Bug description: EDAC updates for AMD Genoa support for 22.04 as requested by AMD f957112423905.17EDAC: Add RDDR5 and LRDDR5 memory types e2be5955a8865.17EDAC/amd64: Add support for AMD Family 19h Models 10h-1Fh and A0h-AFh To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1960362/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1951135] Re: hirsute:linux-aws ubuntu_ltp Failed test cases : read_all_proc
Also found on impish/linux 5.13.0-28.31 running generic-64k on a arm64 box. ** Tags added: 5.13 impish sru-20220131 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1951135 Title: hirsute:linux-aws ubuntu_ltp Failed test cases : read_all_proc Status in ubuntu-kernel-tests: New Status in linux-aws package in Ubuntu: Confirmed Bug description: Failed test cases : read_all_proc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1951135/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1960839] Re: Missing firmware /lib/firmware/intel/ice/ddp/ice.pkg for ice driver
** No longer affects: linux-firmware (Ubuntu Focal)
** No longer affects: linux-firmware (Ubuntu Impish)
** No longer affects: linux-firmware (Ubuntu Jammy)
** Tags added: kern-2460
--
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/1960839
Title:
Missing firmware /lib/firmware/intel/ice/ddp/ice.pkg for ice driver
Status in linux-firmware package in Ubuntu:
Invalid
Status in linux-firmware source package in Bionic:
Fix Committed
Bug description:
[Impact]
* Missing firmware for Intel ICE driver on Bionic,
which is supported by the HWE kernel from Focal.
[Fix]
* commit 9ae61e7d8658 ("ice: Add package file for Intel E800 series driver")
brings the Bionic package in line with Focal (ice-1.3.4.0.pkg,LICENSE.ice)
[Test Case]
* Without firmware:
ice :98:00.0: firmware 5.4.5 api 1.7.6 nvm 2.40 0x8000706a 0.0.0
build 0x391f7640
ice :98:00.0: Direct firmware load for intel/ice/ddp/ice.pkg failed
with error -2
ice :98:00.0: The DDP package file was not found or could not be
read. Entering Safe Mode
ice :98:00.0: Package download failed. Advanced features disabled -
Device now in Safe Mode
* With firmware:
ice :98:00.0: firmware 5.4.5 api 1.7.6 nvm 2.40 0x8000706a 0.0.0
build 0x391f7640
ice :98:00.0: The DDP package was successfully loaded: ICE OS Default
Package version 1.3.4.0
ice :98:00.0: DCB is enabled in the hardware, max number of TCs
supported on this port are 8
ice :98:00.0: FW LLDP is disabled, DCBx/LLDP in SW mode.
[Where problems could occur]
* Systems with devices managed by the ice driver on Bionic HWE kernel
from Focal.
* The firmware enables advanced features, increasing driver exposure
and device activity.
* This has been available on Focal, which helps with some chance of issues
being hit and
reported previously (e.g. bug 1939855, searched for 'kernel ice driver' on
bugs.lp.net).
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1960839/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1957026] Re: AMD Yellow Carp DMCUB fw update for s0i3 B0 fixes
Released with linux-firmware 20220124.git0c6a7b3b-0ubuntu1 in Jammy. ** Changed in: linux-firmware (Ubuntu Jammy) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1957026 Title: AMD Yellow Carp DMCUB fw update for s0i3 B0 fixes Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-firmware package in Ubuntu: Fix Released Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-firmware source package in Focal: Fix Released Status in linux-oem-5.14 source package in Focal: In Progress Status in linux source package in Jammy: In Progress Status in linux-firmware source package in Jammy: Fix Released Status in linux-oem-5.14 source package in Jammy: Invalid Bug description: [SRU Justification] [Impact] On AMD Yellow Carp B0 platforms, S0i3 is still not working. [Fix] This denpends on a few fixes for kernel driver that are all either in v5.17-rc1 or in stable linux-5.1x.y, along with an already upstreamed dmcub firmware. [Test Case] On AMD RMT CRB board, 1. apply both kernel and firmware fixes 2. module blacklist amd_sfh as it's still under development, 3. trigger system suspend. Use power button to wake up the device. 4. check /sys/kernel/debug/amd_pmc/s0ix_stats, the values shall be non-zero On without any of above, the board may not cut device power during suspend, and/or fail to resume and leaving a blank screen, and/or s0ix stats remain all zeros. [Where problems could occur] On AMD RMT CRB board, Sensor Fusion Hub (amd_sfh) still doesn't support S0ix and has to be disabled. For the kernel side, the driver fixes addressed a few procedure errors that should be unlikely to introduce regressions; for the firmware side, also tested loading new firmware on unpatched kernels and there is no difference found yet. [Other Info] For kernel driver fixes, patches for both oem-5.14 and jammy are necessary; for firmware, that has been available in jammy branch but not yet released, so only Focal will be nominated. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1957026/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1956518] Re: linux-firmware 1.187.24 may crash USB ports
Can you please install the latest linux-firwmare 1.187.26 and let us know if you're still experiencing the problems? ** Also affects: linux-firmware (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: linux-firmware (Ubuntu Focal) Status: New => Incomplete ** Changed in: linux-firmware (Ubuntu) Status: Confirmed => Invalid -- 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/1956518 Title: linux-firmware 1.187.24 may crash USB ports Status in linux-firmware package in Ubuntu: Invalid Status in linux-firmware source package in Focal: Incomplete Bug description: Description: Ubuntu 20.04.3 LTS Release: 20.04 5.4.0-92-generic linux-firmware: Instalados: 1.187.24 Candidato: 1.187.24 Tabla de versión: *** 1.187.24 500 500 http://es.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 500 http://es.archive.ubuntu.com/ubuntu focal-updates/main i386 Packages 100 /var/lib/dpkg/status 1.187 500 500 http://es.archive.ubuntu.com/ubuntu focal/main amd64 Packages 500 http://es.archive.ubuntu.com/ubuntu focal/main i386 Packages linux-firmware 1.187.24 upgrade disabled all mainboard USB ports. USB keyboard and mouse stopped working on the next reboot after upgrade. I disconnected an USB bluetooth key from a back USB port, rebooted, and everything restored to normality. My personal conclusion: there is a bug in the bluetooth firmware update that may cause a general USB crash when an USB bluetooth key is connected. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: alvaro 2225 F pulseaudio /dev/snd/controlC0: alvaro 2225 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Dependencies: DistroRelease: Ubuntu 20.04 HibernationDevice: RESUME=UUID=fd59aa5f-2c5c-44c8-9fd3-36c7b5ec516a InstallationDate: Installed on 2014-10-25 (2634 days ago) InstallationMedia: Ubuntu 12.04.2 LTS "Precise Pangolin" - Release amd64 (20130213) IwConfig: lono wireless extensions. enp7s0no wireless extensions. MachineType: Gigabyte Technology Co., Ltd. B365M H NonfreeKernelModules: nvidia_modeset nvidia Package: linux-firmware 1.187.24 PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/bin/bash ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-92-generic root=UUID=ff070320-7281-484d-a5d3-4a42ed9ed075 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-92.103-generic 5.4.157 RelatedPackageVersions: linux-restricted-modules-5.4.0-92-generic N/A linux-backports-modules-5.4.0-92-generic N/A linux-firmware1.187.24 RfKill: 2: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: focal Uname: Linux 5.4.0-92-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-04-27 (623 days ago) UserGroups: adm boinc cdrom dip lpadmin netdev plugdev render sambashare sudo video _MarkForUpload: True dmi.bios.date: 08/18/2020 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F4b dmi.board.asset.tag: Default string dmi.board.name: B365M H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF4b:bd08/18/2020:svnGigabyteTechnologyCo.,Ltd.:pnB365MH:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB365MH:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: B365M H dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1956518/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1959529] Re: Hipersocket page allocation failure on Ubuntu 20.04 based SSC environments
** 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/1959529 Title: Hipersocket page allocation failure on Ubuntu 20.04 based SSC environments Status in Ubuntu on IBM z Systems: Fix Committed Status in linux package in Ubuntu: Fix Released Status in linux source package in Focal: Fix Committed Bug description: == Comment: #0 - D. Gary Chapman - 2022-01-26 12:43:25 == ---Problem Description--- IBM IDAA customer exposes hipersocket page allocation failure on Ubuntu 20.04 based SSC Contact Information = Gary Chapman (ch...@us.ibm.com) ---uname output--- 5.4.0-73-generic #82-Ubuntu Machine Type = IBM Z in IDAA SSC-mode lpar ---Debugger--- A debugger is not configured -- IBM SSC LEVEL: 4.1.5 IBM IDAA LEVEL: 7.5.6 On a client system we are observing this: Jan 19 16:25:57 data5 kernel: kworker/u760:28: page allocation failure: order:0, mode:0xa20(GFP_ATOMIC), nodemask=(null),cpuset=/,mems_allowed=0 Jan 19 16:25:57 data5 kernel: CPU: 20 PID: 4137988 Comm: kworker/u760:28 Kdump: loaded Tainted: G OE 5.4.0-73-generic #82-Ubuntu Jan 19 16:25:57 data5 kernel: Hardware name: IBM 8561 T01 727 (LPAR) Jan 19 16:25:57 data5 kernel: Workqueue: kcryptd/253:11 kcryptd_crypt [dm_crypt] Jan 19 16:25:57 data5 kernel: Call Trace: Jan 19 16:25:57 data5 kernel: ([<006b6d63e092>] show_stack+0x7a/0xc0) Jan 19 16:25:57 data5 kernel: [<006b6d64588a>] dump_stack+0x8a/0xb8 Jan 19 16:25:57 data5 kernel: [<006b6cfd8262>] warn_alloc+0xe2/0x160 IBM LTC Networking team has identified the upstream commit 714c9108851743bb718fbc1bfb81290f12a53854 as the root cause. This patch shows up in the Ubuntu kernel source tree: https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/commit/?id=714c9108851743bb718fbc1bfb81290f12a53854 but has not been ported to Ubuntu 20.04 / kernel 5.4 IDAA on SSC requests backport to focal. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1959529/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1960826] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1960826/+attachment/5561022/+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/1960826 Title: NFSv4 performance problem with newer kernels Status in linux package in Ubuntu: Confirmed Bug description: I am seeing an issue with NFSv4 performance on Ubuntu 20.04.3 LTS on both clients and server (tested kernels 5.4 to 5.16), where the server is connected by 10Gbit Ethernet and with multiple clients connected by 1Gbit. I am reading a large file from an NFS mount via "dd" sending output to /dev/null with bs=4096. Using default sysctl and mount options I am seeing speeds maxing out below 1Gbit/sec. If I force NFSv3 I see speeds close to 10Gbit/sec with sufficient clients connected. I also see no issue with Ubuntu 16.04 (when used for both server and clients) in conjunction with NFSv4. I have attached the output from two iftop's which shows the status when using NFSv4 and when using NFSv3, in the NFSv4 you can clearly see one client reading at max speed and all the others apparently throttling back to practically nothing. I have additionally tested a range of mount options, which made no difference, BBR congestion control which made no difference and the following kernel settings which also made no difference: net.core.netdev_max_backlog=25 net.core.rmem_max=4194304 net.core.wmem_max=4194304 net.core.rmem_default=4194304 net.core.wmem_default=4194304 net.core.optmem_max=4194304 net.ipv4.tcp_rmem=4096 87380 4194304 net.ipv4.tcp_wmem=4096 65536 4194304 net.ipv4.tcp_mem=786432 1048576 26777216 net.ipv4.udp_mem=1529892 2039859 3059784 net.ipv4.udp_rmem_min=16384 net.ipv4.udp_wmem_min=16384 The problem is seen on dissimilar hardware, ie this problem exists when testing with an HP DL380 G10 with Mellanox 10Gbit Ethernet connected to Cisco switch, and also on a Dell R430 with Broadcom 10Gbit Ethernet connected to a Netgear switch (just to name two of several configurations that have been tested). The clients vary in each test case also, but are desktop PCs and laptops. --- ProblemType: Bug AlsaDevices: total 0 crw-rw+ 1 root audio 116, 1 Feb 15 10:23 seq crw-rw+ 1 root audio 116, 33 Feb 15 10:23 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: pass DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2022-02-14 (0 days ago) InstallationMedia: Ubuntu-Server 20.04.2 LTS "Focal Fossa" - Release amd64 (20210201.2) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: Dell Inc. PowerEdge R430 Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 mgag200drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-28-generic root=UUID=d227a745-134e-4633-9c26-bcc062655f95 ro ProcVersionSignature: Ubuntu 5.13.0-28.31~20.04.1-generic 5.13.19 RelatedPackageVersions: linux-restricted-modules-5.13.0-28-generic N/A linux-backports-modules-5.13.0-28-generic N/A linux-firmware 1.187.26 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal uec-images Uname: Linux 5.13.0-28-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 06/07/2021 dmi.bios.release: 2.13 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.13.0 dmi.board.name: 0CN7X8 dmi.board.vendor: Dell Inc. dmi.board.version: A04 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.13.0:bd06/07/2021:br2.13:svnDellInc.:pnPowerEdgeR430:pvr:rvnDellInc.:rn0CN7X8:rvrA04:cvnDellInc.:ct23:cvr:skuSKU=NotProvided;ModelName=PowerEdgeR430: dmi.product.name: PowerEdge R430 dmi.product.sku: SKU=NotProvided;ModelName=PowerEdge R430 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1960826/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1960826] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1960826/+attachment/5561019/+files/ProcCpuinfo.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/1960826 Title: NFSv4 performance problem with newer kernels Status in linux package in Ubuntu: Confirmed Bug description: I am seeing an issue with NFSv4 performance on Ubuntu 20.04.3 LTS on both clients and server (tested kernels 5.4 to 5.16), where the server is connected by 10Gbit Ethernet and with multiple clients connected by 1Gbit. I am reading a large file from an NFS mount via "dd" sending output to /dev/null with bs=4096. Using default sysctl and mount options I am seeing speeds maxing out below 1Gbit/sec. If I force NFSv3 I see speeds close to 10Gbit/sec with sufficient clients connected. I also see no issue with Ubuntu 16.04 (when used for both server and clients) in conjunction with NFSv4. I have attached the output from two iftop's which shows the status when using NFSv4 and when using NFSv3, in the NFSv4 you can clearly see one client reading at max speed and all the others apparently throttling back to practically nothing. I have additionally tested a range of mount options, which made no difference, BBR congestion control which made no difference and the following kernel settings which also made no difference: net.core.netdev_max_backlog=25 net.core.rmem_max=4194304 net.core.wmem_max=4194304 net.core.rmem_default=4194304 net.core.wmem_default=4194304 net.core.optmem_max=4194304 net.ipv4.tcp_rmem=4096 87380 4194304 net.ipv4.tcp_wmem=4096 65536 4194304 net.ipv4.tcp_mem=786432 1048576 26777216 net.ipv4.udp_mem=1529892 2039859 3059784 net.ipv4.udp_rmem_min=16384 net.ipv4.udp_wmem_min=16384 The problem is seen on dissimilar hardware, ie this problem exists when testing with an HP DL380 G10 with Mellanox 10Gbit Ethernet connected to Cisco switch, and also on a Dell R430 with Broadcom 10Gbit Ethernet connected to a Netgear switch (just to name two of several configurations that have been tested). The clients vary in each test case also, but are desktop PCs and laptops. --- ProblemType: Bug AlsaDevices: total 0 crw-rw+ 1 root audio 116, 1 Feb 15 10:23 seq crw-rw+ 1 root audio 116, 33 Feb 15 10:23 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: pass DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2022-02-14 (0 days ago) InstallationMedia: Ubuntu-Server 20.04.2 LTS "Focal Fossa" - Release amd64 (20210201.2) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: Dell Inc. PowerEdge R430 Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 mgag200drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-28-generic root=UUID=d227a745-134e-4633-9c26-bcc062655f95 ro ProcVersionSignature: Ubuntu 5.13.0-28.31~20.04.1-generic 5.13.19 RelatedPackageVersions: linux-restricted-modules-5.13.0-28-generic N/A linux-backports-modules-5.13.0-28-generic N/A linux-firmware 1.187.26 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal uec-images Uname: Linux 5.13.0-28-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 06/07/2021 dmi.bios.release: 2.13 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.13.0 dmi.board.name: 0CN7X8 dmi.board.vendor: Dell Inc. dmi.board.version: A04 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.13.0:bd06/07/2021:br2.13:svnDellInc.:pnPowerEdgeR430:pvr:rvnDellInc.:rn0CN7X8:rvrA04:cvnDellInc.:ct23:cvr:skuSKU=NotProvided;ModelName=PowerEdgeR430: dmi.product.name: PowerEdge R430 dmi.product.sku: SKU=NotProvided;ModelName=PowerEdge R430 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1960826/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1960826] Lsusb-v.txt
apport information ** Attachment added: "Lsusb-v.txt" https://bugs.launchpad.net/bugs/1960826/+attachment/5561018/+files/Lsusb-v.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/1960826 Title: NFSv4 performance problem with newer kernels Status in linux package in Ubuntu: Confirmed Bug description: I am seeing an issue with NFSv4 performance on Ubuntu 20.04.3 LTS on both clients and server (tested kernels 5.4 to 5.16), where the server is connected by 10Gbit Ethernet and with multiple clients connected by 1Gbit. I am reading a large file from an NFS mount via "dd" sending output to /dev/null with bs=4096. Using default sysctl and mount options I am seeing speeds maxing out below 1Gbit/sec. If I force NFSv3 I see speeds close to 10Gbit/sec with sufficient clients connected. I also see no issue with Ubuntu 16.04 (when used for both server and clients) in conjunction with NFSv4. I have attached the output from two iftop's which shows the status when using NFSv4 and when using NFSv3, in the NFSv4 you can clearly see one client reading at max speed and all the others apparently throttling back to practically nothing. I have additionally tested a range of mount options, which made no difference, BBR congestion control which made no difference and the following kernel settings which also made no difference: net.core.netdev_max_backlog=25 net.core.rmem_max=4194304 net.core.wmem_max=4194304 net.core.rmem_default=4194304 net.core.wmem_default=4194304 net.core.optmem_max=4194304 net.ipv4.tcp_rmem=4096 87380 4194304 net.ipv4.tcp_wmem=4096 65536 4194304 net.ipv4.tcp_mem=786432 1048576 26777216 net.ipv4.udp_mem=1529892 2039859 3059784 net.ipv4.udp_rmem_min=16384 net.ipv4.udp_wmem_min=16384 The problem is seen on dissimilar hardware, ie this problem exists when testing with an HP DL380 G10 with Mellanox 10Gbit Ethernet connected to Cisco switch, and also on a Dell R430 with Broadcom 10Gbit Ethernet connected to a Netgear switch (just to name two of several configurations that have been tested). The clients vary in each test case also, but are desktop PCs and laptops. --- ProblemType: Bug AlsaDevices: total 0 crw-rw+ 1 root audio 116, 1 Feb 15 10:23 seq crw-rw+ 1 root audio 116, 33 Feb 15 10:23 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: pass DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2022-02-14 (0 days ago) InstallationMedia: Ubuntu-Server 20.04.2 LTS "Focal Fossa" - Release amd64 (20210201.2) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: Dell Inc. PowerEdge R430 Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 mgag200drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-28-generic root=UUID=d227a745-134e-4633-9c26-bcc062655f95 ro ProcVersionSignature: Ubuntu 5.13.0-28.31~20.04.1-generic 5.13.19 RelatedPackageVersions: linux-restricted-modules-5.13.0-28-generic N/A linux-backports-modules-5.13.0-28-generic N/A linux-firmware 1.187.26 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal uec-images Uname: Linux 5.13.0-28-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 06/07/2021 dmi.bios.release: 2.13 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.13.0 dmi.board.name: 0CN7X8 dmi.board.vendor: Dell Inc. dmi.board.version: A04 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.13.0:bd06/07/2021:br2.13:svnDellInc.:pnPowerEdgeR430:pvr:rvnDellInc.:rn0CN7X8:rvrA04:cvnDellInc.:ct23:cvr:skuSKU=NotProvided;ModelName=PowerEdgeR430: dmi.product.name: PowerEdge R430 dmi.product.sku: SKU=NotProvided;ModelName=PowerEdge R430 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1960826/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1960826] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1960826/+attachment/5561020/+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/1960826 Title: NFSv4 performance problem with newer kernels Status in linux package in Ubuntu: Confirmed Bug description: I am seeing an issue with NFSv4 performance on Ubuntu 20.04.3 LTS on both clients and server (tested kernels 5.4 to 5.16), where the server is connected by 10Gbit Ethernet and with multiple clients connected by 1Gbit. I am reading a large file from an NFS mount via "dd" sending output to /dev/null with bs=4096. Using default sysctl and mount options I am seeing speeds maxing out below 1Gbit/sec. If I force NFSv3 I see speeds close to 10Gbit/sec with sufficient clients connected. I also see no issue with Ubuntu 16.04 (when used for both server and clients) in conjunction with NFSv4. I have attached the output from two iftop's which shows the status when using NFSv4 and when using NFSv3, in the NFSv4 you can clearly see one client reading at max speed and all the others apparently throttling back to practically nothing. I have additionally tested a range of mount options, which made no difference, BBR congestion control which made no difference and the following kernel settings which also made no difference: net.core.netdev_max_backlog=25 net.core.rmem_max=4194304 net.core.wmem_max=4194304 net.core.rmem_default=4194304 net.core.wmem_default=4194304 net.core.optmem_max=4194304 net.ipv4.tcp_rmem=4096 87380 4194304 net.ipv4.tcp_wmem=4096 65536 4194304 net.ipv4.tcp_mem=786432 1048576 26777216 net.ipv4.udp_mem=1529892 2039859 3059784 net.ipv4.udp_rmem_min=16384 net.ipv4.udp_wmem_min=16384 The problem is seen on dissimilar hardware, ie this problem exists when testing with an HP DL380 G10 with Mellanox 10Gbit Ethernet connected to Cisco switch, and also on a Dell R430 with Broadcom 10Gbit Ethernet connected to a Netgear switch (just to name two of several configurations that have been tested). The clients vary in each test case also, but are desktop PCs and laptops. --- ProblemType: Bug AlsaDevices: total 0 crw-rw+ 1 root audio 116, 1 Feb 15 10:23 seq crw-rw+ 1 root audio 116, 33 Feb 15 10:23 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: pass DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2022-02-14 (0 days ago) InstallationMedia: Ubuntu-Server 20.04.2 LTS "Focal Fossa" - Release amd64 (20210201.2) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: Dell Inc. PowerEdge R430 Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 mgag200drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-28-generic root=UUID=d227a745-134e-4633-9c26-bcc062655f95 ro ProcVersionSignature: Ubuntu 5.13.0-28.31~20.04.1-generic 5.13.19 RelatedPackageVersions: linux-restricted-modules-5.13.0-28-generic N/A linux-backports-modules-5.13.0-28-generic N/A linux-firmware 1.187.26 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal uec-images Uname: Linux 5.13.0-28-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 06/07/2021 dmi.bios.release: 2.13 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.13.0 dmi.board.name: 0CN7X8 dmi.board.vendor: Dell Inc. dmi.board.version: A04 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.13.0:bd06/07/2021:br2.13:svnDellInc.:pnPowerEdgeR430:pvr:rvnDellInc.:rn0CN7X8:rvrA04:cvnDellInc.:ct23:cvr:skuSKU=NotProvided;ModelName=PowerEdgeR430: dmi.product.name: PowerEdge R430 dmi.product.sku: SKU=NotProvided;ModelName=PowerEdge R430 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1960826/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1960826] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1960826/+attachment/5561024/+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/1960826 Title: NFSv4 performance problem with newer kernels Status in linux package in Ubuntu: Confirmed Bug description: I am seeing an issue with NFSv4 performance on Ubuntu 20.04.3 LTS on both clients and server (tested kernels 5.4 to 5.16), where the server is connected by 10Gbit Ethernet and with multiple clients connected by 1Gbit. I am reading a large file from an NFS mount via "dd" sending output to /dev/null with bs=4096. Using default sysctl and mount options I am seeing speeds maxing out below 1Gbit/sec. If I force NFSv3 I see speeds close to 10Gbit/sec with sufficient clients connected. I also see no issue with Ubuntu 16.04 (when used for both server and clients) in conjunction with NFSv4. I have attached the output from two iftop's which shows the status when using NFSv4 and when using NFSv3, in the NFSv4 you can clearly see one client reading at max speed and all the others apparently throttling back to practically nothing. I have additionally tested a range of mount options, which made no difference, BBR congestion control which made no difference and the following kernel settings which also made no difference: net.core.netdev_max_backlog=25 net.core.rmem_max=4194304 net.core.wmem_max=4194304 net.core.rmem_default=4194304 net.core.wmem_default=4194304 net.core.optmem_max=4194304 net.ipv4.tcp_rmem=4096 87380 4194304 net.ipv4.tcp_wmem=4096 65536 4194304 net.ipv4.tcp_mem=786432 1048576 26777216 net.ipv4.udp_mem=1529892 2039859 3059784 net.ipv4.udp_rmem_min=16384 net.ipv4.udp_wmem_min=16384 The problem is seen on dissimilar hardware, ie this problem exists when testing with an HP DL380 G10 with Mellanox 10Gbit Ethernet connected to Cisco switch, and also on a Dell R430 with Broadcom 10Gbit Ethernet connected to a Netgear switch (just to name two of several configurations that have been tested). The clients vary in each test case also, but are desktop PCs and laptops. --- ProblemType: Bug AlsaDevices: total 0 crw-rw+ 1 root audio 116, 1 Feb 15 10:23 seq crw-rw+ 1 root audio 116, 33 Feb 15 10:23 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: pass DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2022-02-14 (0 days ago) InstallationMedia: Ubuntu-Server 20.04.2 LTS "Focal Fossa" - Release amd64 (20210201.2) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: Dell Inc. PowerEdge R430 Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 mgag200drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-28-generic root=UUID=d227a745-134e-4633-9c26-bcc062655f95 ro ProcVersionSignature: Ubuntu 5.13.0-28.31~20.04.1-generic 5.13.19 RelatedPackageVersions: linux-restricted-modules-5.13.0-28-generic N/A linux-backports-modules-5.13.0-28-generic N/A linux-firmware 1.187.26 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal uec-images Uname: Linux 5.13.0-28-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 06/07/2021 dmi.bios.release: 2.13 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.13.0 dmi.board.name: 0CN7X8 dmi.board.vendor: Dell Inc. dmi.board.version: A04 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.13.0:bd06/07/2021:br2.13:svnDellInc.:pnPowerEdgeR430:pvr:rvnDellInc.:rn0CN7X8:rvrA04:cvnDellInc.:ct23:cvr:skuSKU=NotProvided;ModelName=PowerEdgeR430: dmi.product.name: PowerEdge R430 dmi.product.sku: SKU=NotProvided;ModelName=PowerEdge R430 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1960826/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1960826] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1960826/+attachment/5561023/+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/1960826 Title: NFSv4 performance problem with newer kernels Status in linux package in Ubuntu: Confirmed Bug description: I am seeing an issue with NFSv4 performance on Ubuntu 20.04.3 LTS on both clients and server (tested kernels 5.4 to 5.16), where the server is connected by 10Gbit Ethernet and with multiple clients connected by 1Gbit. I am reading a large file from an NFS mount via "dd" sending output to /dev/null with bs=4096. Using default sysctl and mount options I am seeing speeds maxing out below 1Gbit/sec. If I force NFSv3 I see speeds close to 10Gbit/sec with sufficient clients connected. I also see no issue with Ubuntu 16.04 (when used for both server and clients) in conjunction with NFSv4. I have attached the output from two iftop's which shows the status when using NFSv4 and when using NFSv3, in the NFSv4 you can clearly see one client reading at max speed and all the others apparently throttling back to practically nothing. I have additionally tested a range of mount options, which made no difference, BBR congestion control which made no difference and the following kernel settings which also made no difference: net.core.netdev_max_backlog=25 net.core.rmem_max=4194304 net.core.wmem_max=4194304 net.core.rmem_default=4194304 net.core.wmem_default=4194304 net.core.optmem_max=4194304 net.ipv4.tcp_rmem=4096 87380 4194304 net.ipv4.tcp_wmem=4096 65536 4194304 net.ipv4.tcp_mem=786432 1048576 26777216 net.ipv4.udp_mem=1529892 2039859 3059784 net.ipv4.udp_rmem_min=16384 net.ipv4.udp_wmem_min=16384 The problem is seen on dissimilar hardware, ie this problem exists when testing with an HP DL380 G10 with Mellanox 10Gbit Ethernet connected to Cisco switch, and also on a Dell R430 with Broadcom 10Gbit Ethernet connected to a Netgear switch (just to name two of several configurations that have been tested). The clients vary in each test case also, but are desktop PCs and laptops. --- ProblemType: Bug AlsaDevices: total 0 crw-rw+ 1 root audio 116, 1 Feb 15 10:23 seq crw-rw+ 1 root audio 116, 33 Feb 15 10:23 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: pass DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2022-02-14 (0 days ago) InstallationMedia: Ubuntu-Server 20.04.2 LTS "Focal Fossa" - Release amd64 (20210201.2) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: Dell Inc. PowerEdge R430 Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 mgag200drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-28-generic root=UUID=d227a745-134e-4633-9c26-bcc062655f95 ro ProcVersionSignature: Ubuntu 5.13.0-28.31~20.04.1-generic 5.13.19 RelatedPackageVersions: linux-restricted-modules-5.13.0-28-generic N/A linux-backports-modules-5.13.0-28-generic N/A linux-firmware 1.187.26 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal uec-images Uname: Linux 5.13.0-28-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 06/07/2021 dmi.bios.release: 2.13 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.13.0 dmi.board.name: 0CN7X8 dmi.board.vendor: Dell Inc. dmi.board.version: A04 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.13.0:bd06/07/2021:br2.13:svnDellInc.:pnPowerEdgeR430:pvr:rvnDellInc.:rn0CN7X8:rvrA04:cvnDellInc.:ct23:cvr:skuSKU=NotProvided;ModelName=PowerEdgeR430: dmi.product.name: PowerEdge R430 dmi.product.sku: SKU=NotProvided;ModelName=PowerEdge R430 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1960826/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1960826] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1960826/+attachment/5561021/+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/1960826 Title: NFSv4 performance problem with newer kernels Status in linux package in Ubuntu: Confirmed Bug description: I am seeing an issue with NFSv4 performance on Ubuntu 20.04.3 LTS on both clients and server (tested kernels 5.4 to 5.16), where the server is connected by 10Gbit Ethernet and with multiple clients connected by 1Gbit. I am reading a large file from an NFS mount via "dd" sending output to /dev/null with bs=4096. Using default sysctl and mount options I am seeing speeds maxing out below 1Gbit/sec. If I force NFSv3 I see speeds close to 10Gbit/sec with sufficient clients connected. I also see no issue with Ubuntu 16.04 (when used for both server and clients) in conjunction with NFSv4. I have attached the output from two iftop's which shows the status when using NFSv4 and when using NFSv3, in the NFSv4 you can clearly see one client reading at max speed and all the others apparently throttling back to practically nothing. I have additionally tested a range of mount options, which made no difference, BBR congestion control which made no difference and the following kernel settings which also made no difference: net.core.netdev_max_backlog=25 net.core.rmem_max=4194304 net.core.wmem_max=4194304 net.core.rmem_default=4194304 net.core.wmem_default=4194304 net.core.optmem_max=4194304 net.ipv4.tcp_rmem=4096 87380 4194304 net.ipv4.tcp_wmem=4096 65536 4194304 net.ipv4.tcp_mem=786432 1048576 26777216 net.ipv4.udp_mem=1529892 2039859 3059784 net.ipv4.udp_rmem_min=16384 net.ipv4.udp_wmem_min=16384 The problem is seen on dissimilar hardware, ie this problem exists when testing with an HP DL380 G10 with Mellanox 10Gbit Ethernet connected to Cisco switch, and also on a Dell R430 with Broadcom 10Gbit Ethernet connected to a Netgear switch (just to name two of several configurations that have been tested). The clients vary in each test case also, but are desktop PCs and laptops. --- ProblemType: Bug AlsaDevices: total 0 crw-rw+ 1 root audio 116, 1 Feb 15 10:23 seq crw-rw+ 1 root audio 116, 33 Feb 15 10:23 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: pass DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2022-02-14 (0 days ago) InstallationMedia: Ubuntu-Server 20.04.2 LTS "Focal Fossa" - Release amd64 (20210201.2) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: Dell Inc. PowerEdge R430 Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 mgag200drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-28-generic root=UUID=d227a745-134e-4633-9c26-bcc062655f95 ro ProcVersionSignature: Ubuntu 5.13.0-28.31~20.04.1-generic 5.13.19 RelatedPackageVersions: linux-restricted-modules-5.13.0-28-generic N/A linux-backports-modules-5.13.0-28-generic N/A linux-firmware 1.187.26 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal uec-images Uname: Linux 5.13.0-28-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 06/07/2021 dmi.bios.release: 2.13 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.13.0 dmi.board.name: 0CN7X8 dmi.board.vendor: Dell Inc. dmi.board.version: A04 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.13.0:bd06/07/2021:br2.13:svnDellInc.:pnPowerEdgeR430:pvr:rvnDellInc.:rn0CN7X8:rvrA04:cvnDellInc.:ct23:cvr:skuSKU=NotProvided;ModelName=PowerEdgeR430: dmi.product.name: PowerEdge R430 dmi.product.sku: SKU=NotProvided;ModelName=PowerEdge R430 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1960826/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1960826] acpidump.txt
apport information ** Attachment added: "acpidump.txt" https://bugs.launchpad.net/bugs/1960826/+attachment/5561025/+files/acpidump.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/1960826 Title: NFSv4 performance problem with newer kernels Status in linux package in Ubuntu: Confirmed Bug description: I am seeing an issue with NFSv4 performance on Ubuntu 20.04.3 LTS on both clients and server (tested kernels 5.4 to 5.16), where the server is connected by 10Gbit Ethernet and with multiple clients connected by 1Gbit. I am reading a large file from an NFS mount via "dd" sending output to /dev/null with bs=4096. Using default sysctl and mount options I am seeing speeds maxing out below 1Gbit/sec. If I force NFSv3 I see speeds close to 10Gbit/sec with sufficient clients connected. I also see no issue with Ubuntu 16.04 (when used for both server and clients) in conjunction with NFSv4. I have attached the output from two iftop's which shows the status when using NFSv4 and when using NFSv3, in the NFSv4 you can clearly see one client reading at max speed and all the others apparently throttling back to practically nothing. I have additionally tested a range of mount options, which made no difference, BBR congestion control which made no difference and the following kernel settings which also made no difference: net.core.netdev_max_backlog=25 net.core.rmem_max=4194304 net.core.wmem_max=4194304 net.core.rmem_default=4194304 net.core.wmem_default=4194304 net.core.optmem_max=4194304 net.ipv4.tcp_rmem=4096 87380 4194304 net.ipv4.tcp_wmem=4096 65536 4194304 net.ipv4.tcp_mem=786432 1048576 26777216 net.ipv4.udp_mem=1529892 2039859 3059784 net.ipv4.udp_rmem_min=16384 net.ipv4.udp_wmem_min=16384 The problem is seen on dissimilar hardware, ie this problem exists when testing with an HP DL380 G10 with Mellanox 10Gbit Ethernet connected to Cisco switch, and also on a Dell R430 with Broadcom 10Gbit Ethernet connected to a Netgear switch (just to name two of several configurations that have been tested). The clients vary in each test case also, but are desktop PCs and laptops. --- ProblemType: Bug AlsaDevices: total 0 crw-rw+ 1 root audio 116, 1 Feb 15 10:23 seq crw-rw+ 1 root audio 116, 33 Feb 15 10:23 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: pass DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2022-02-14 (0 days ago) InstallationMedia: Ubuntu-Server 20.04.2 LTS "Focal Fossa" - Release amd64 (20210201.2) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: Dell Inc. PowerEdge R430 Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 mgag200drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-28-generic root=UUID=d227a745-134e-4633-9c26-bcc062655f95 ro ProcVersionSignature: Ubuntu 5.13.0-28.31~20.04.1-generic 5.13.19 RelatedPackageVersions: linux-restricted-modules-5.13.0-28-generic N/A linux-backports-modules-5.13.0-28-generic N/A linux-firmware 1.187.26 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal uec-images Uname: Linux 5.13.0-28-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 06/07/2021 dmi.bios.release: 2.13 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.13.0 dmi.board.name: 0CN7X8 dmi.board.vendor: Dell Inc. dmi.board.version: A04 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.13.0:bd06/07/2021:br2.13:svnDellInc.:pnPowerEdgeR430:pvr:rvnDellInc.:rn0CN7X8:rvrA04:cvnDellInc.:ct23:cvr:skuSKU=NotProvided;ModelName=PowerEdgeR430: dmi.product.name: PowerEdge R430 dmi.product.sku: SKU=NotProvided;ModelName=PowerEdge R430 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1960826/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1960826] Lspci-vt.txt
apport information ** Attachment added: "Lspci-vt.txt" https://bugs.launchpad.net/bugs/1960826/+attachment/5561015/+files/Lspci-vt.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/1960826 Title: NFSv4 performance problem with newer kernels Status in linux package in Ubuntu: Confirmed Bug description: I am seeing an issue with NFSv4 performance on Ubuntu 20.04.3 LTS on both clients and server (tested kernels 5.4 to 5.16), where the server is connected by 10Gbit Ethernet and with multiple clients connected by 1Gbit. I am reading a large file from an NFS mount via "dd" sending output to /dev/null with bs=4096. Using default sysctl and mount options I am seeing speeds maxing out below 1Gbit/sec. If I force NFSv3 I see speeds close to 10Gbit/sec with sufficient clients connected. I also see no issue with Ubuntu 16.04 (when used for both server and clients) in conjunction with NFSv4. I have attached the output from two iftop's which shows the status when using NFSv4 and when using NFSv3, in the NFSv4 you can clearly see one client reading at max speed and all the others apparently throttling back to practically nothing. I have additionally tested a range of mount options, which made no difference, BBR congestion control which made no difference and the following kernel settings which also made no difference: net.core.netdev_max_backlog=25 net.core.rmem_max=4194304 net.core.wmem_max=4194304 net.core.rmem_default=4194304 net.core.wmem_default=4194304 net.core.optmem_max=4194304 net.ipv4.tcp_rmem=4096 87380 4194304 net.ipv4.tcp_wmem=4096 65536 4194304 net.ipv4.tcp_mem=786432 1048576 26777216 net.ipv4.udp_mem=1529892 2039859 3059784 net.ipv4.udp_rmem_min=16384 net.ipv4.udp_wmem_min=16384 The problem is seen on dissimilar hardware, ie this problem exists when testing with an HP DL380 G10 with Mellanox 10Gbit Ethernet connected to Cisco switch, and also on a Dell R430 with Broadcom 10Gbit Ethernet connected to a Netgear switch (just to name two of several configurations that have been tested). The clients vary in each test case also, but are desktop PCs and laptops. --- ProblemType: Bug AlsaDevices: total 0 crw-rw+ 1 root audio 116, 1 Feb 15 10:23 seq crw-rw+ 1 root audio 116, 33 Feb 15 10:23 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: pass DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2022-02-14 (0 days ago) InstallationMedia: Ubuntu-Server 20.04.2 LTS "Focal Fossa" - Release amd64 (20210201.2) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: Dell Inc. PowerEdge R430 Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 mgag200drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-28-generic root=UUID=d227a745-134e-4633-9c26-bcc062655f95 ro ProcVersionSignature: Ubuntu 5.13.0-28.31~20.04.1-generic 5.13.19 RelatedPackageVersions: linux-restricted-modules-5.13.0-28-generic N/A linux-backports-modules-5.13.0-28-generic N/A linux-firmware 1.187.26 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal uec-images Uname: Linux 5.13.0-28-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 06/07/2021 dmi.bios.release: 2.13 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.13.0 dmi.board.name: 0CN7X8 dmi.board.vendor: Dell Inc. dmi.board.version: A04 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.13.0:bd06/07/2021:br2.13:svnDellInc.:pnPowerEdgeR430:pvr:rvnDellInc.:rn0CN7X8:rvrA04:cvnDellInc.:ct23:cvr:skuSKU=NotProvided;ModelName=PowerEdgeR430: dmi.product.name: PowerEdge R430 dmi.product.sku: SKU=NotProvided;ModelName=PowerEdge R430 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1960826/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1960826] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1960826/+attachment/5561016/+files/Lsusb.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/1960826 Title: NFSv4 performance problem with newer kernels Status in linux package in Ubuntu: Confirmed Bug description: I am seeing an issue with NFSv4 performance on Ubuntu 20.04.3 LTS on both clients and server (tested kernels 5.4 to 5.16), where the server is connected by 10Gbit Ethernet and with multiple clients connected by 1Gbit. I am reading a large file from an NFS mount via "dd" sending output to /dev/null with bs=4096. Using default sysctl and mount options I am seeing speeds maxing out below 1Gbit/sec. If I force NFSv3 I see speeds close to 10Gbit/sec with sufficient clients connected. I also see no issue with Ubuntu 16.04 (when used for both server and clients) in conjunction with NFSv4. I have attached the output from two iftop's which shows the status when using NFSv4 and when using NFSv3, in the NFSv4 you can clearly see one client reading at max speed and all the others apparently throttling back to practically nothing. I have additionally tested a range of mount options, which made no difference, BBR congestion control which made no difference and the following kernel settings which also made no difference: net.core.netdev_max_backlog=25 net.core.rmem_max=4194304 net.core.wmem_max=4194304 net.core.rmem_default=4194304 net.core.wmem_default=4194304 net.core.optmem_max=4194304 net.ipv4.tcp_rmem=4096 87380 4194304 net.ipv4.tcp_wmem=4096 65536 4194304 net.ipv4.tcp_mem=786432 1048576 26777216 net.ipv4.udp_mem=1529892 2039859 3059784 net.ipv4.udp_rmem_min=16384 net.ipv4.udp_wmem_min=16384 The problem is seen on dissimilar hardware, ie this problem exists when testing with an HP DL380 G10 with Mellanox 10Gbit Ethernet connected to Cisco switch, and also on a Dell R430 with Broadcom 10Gbit Ethernet connected to a Netgear switch (just to name two of several configurations that have been tested). The clients vary in each test case also, but are desktop PCs and laptops. --- ProblemType: Bug AlsaDevices: total 0 crw-rw+ 1 root audio 116, 1 Feb 15 10:23 seq crw-rw+ 1 root audio 116, 33 Feb 15 10:23 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: pass DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2022-02-14 (0 days ago) InstallationMedia: Ubuntu-Server 20.04.2 LTS "Focal Fossa" - Release amd64 (20210201.2) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: Dell Inc. PowerEdge R430 Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 mgag200drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-28-generic root=UUID=d227a745-134e-4633-9c26-bcc062655f95 ro ProcVersionSignature: Ubuntu 5.13.0-28.31~20.04.1-generic 5.13.19 RelatedPackageVersions: linux-restricted-modules-5.13.0-28-generic N/A linux-backports-modules-5.13.0-28-generic N/A linux-firmware 1.187.26 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal uec-images Uname: Linux 5.13.0-28-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 06/07/2021 dmi.bios.release: 2.13 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.13.0 dmi.board.name: 0CN7X8 dmi.board.vendor: Dell Inc. dmi.board.version: A04 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.13.0:bd06/07/2021:br2.13:svnDellInc.:pnPowerEdgeR430:pvr:rvnDellInc.:rn0CN7X8:rvrA04:cvnDellInc.:ct23:cvr:skuSKU=NotProvided;ModelName=PowerEdgeR430: dmi.product.name: PowerEdge R430 dmi.product.sku: SKU=NotProvided;ModelName=PowerEdge R430 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1960826/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1960826] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1960826/+attachment/5561014/+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/1960826 Title: NFSv4 performance problem with newer kernels Status in linux package in Ubuntu: Confirmed Bug description: I am seeing an issue with NFSv4 performance on Ubuntu 20.04.3 LTS on both clients and server (tested kernels 5.4 to 5.16), where the server is connected by 10Gbit Ethernet and with multiple clients connected by 1Gbit. I am reading a large file from an NFS mount via "dd" sending output to /dev/null with bs=4096. Using default sysctl and mount options I am seeing speeds maxing out below 1Gbit/sec. If I force NFSv3 I see speeds close to 10Gbit/sec with sufficient clients connected. I also see no issue with Ubuntu 16.04 (when used for both server and clients) in conjunction with NFSv4. I have attached the output from two iftop's which shows the status when using NFSv4 and when using NFSv3, in the NFSv4 you can clearly see one client reading at max speed and all the others apparently throttling back to practically nothing. I have additionally tested a range of mount options, which made no difference, BBR congestion control which made no difference and the following kernel settings which also made no difference: net.core.netdev_max_backlog=25 net.core.rmem_max=4194304 net.core.wmem_max=4194304 net.core.rmem_default=4194304 net.core.wmem_default=4194304 net.core.optmem_max=4194304 net.ipv4.tcp_rmem=4096 87380 4194304 net.ipv4.tcp_wmem=4096 65536 4194304 net.ipv4.tcp_mem=786432 1048576 26777216 net.ipv4.udp_mem=1529892 2039859 3059784 net.ipv4.udp_rmem_min=16384 net.ipv4.udp_wmem_min=16384 The problem is seen on dissimilar hardware, ie this problem exists when testing with an HP DL380 G10 with Mellanox 10Gbit Ethernet connected to Cisco switch, and also on a Dell R430 with Broadcom 10Gbit Ethernet connected to a Netgear switch (just to name two of several configurations that have been tested). The clients vary in each test case also, but are desktop PCs and laptops. --- ProblemType: Bug AlsaDevices: total 0 crw-rw+ 1 root audio 116, 1 Feb 15 10:23 seq crw-rw+ 1 root audio 116, 33 Feb 15 10:23 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: pass DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2022-02-14 (0 days ago) InstallationMedia: Ubuntu-Server 20.04.2 LTS "Focal Fossa" - Release amd64 (20210201.2) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: Dell Inc. PowerEdge R430 Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 mgag200drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-28-generic root=UUID=d227a745-134e-4633-9c26-bcc062655f95 ro ProcVersionSignature: Ubuntu 5.13.0-28.31~20.04.1-generic 5.13.19 RelatedPackageVersions: linux-restricted-modules-5.13.0-28-generic N/A linux-backports-modules-5.13.0-28-generic N/A linux-firmware 1.187.26 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal uec-images Uname: Linux 5.13.0-28-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 06/07/2021 dmi.bios.release: 2.13 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.13.0 dmi.board.name: 0CN7X8 dmi.board.vendor: Dell Inc. dmi.board.version: A04 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.13.0:bd06/07/2021:br2.13:svnDellInc.:pnPowerEdgeR430:pvr:rvnDellInc.:rn0CN7X8:rvrA04:cvnDellInc.:ct23:cvr:skuSKU=NotProvided;ModelName=PowerEdgeR430: dmi.product.name: PowerEdge R430 dmi.product.sku: SKU=NotProvided;ModelName=PowerEdge R430 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1960826/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1960826] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1960826/+attachment/5561013/+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/1960826 Title: NFSv4 performance problem with newer kernels Status in linux package in Ubuntu: Confirmed Bug description: I am seeing an issue with NFSv4 performance on Ubuntu 20.04.3 LTS on both clients and server (tested kernels 5.4 to 5.16), where the server is connected by 10Gbit Ethernet and with multiple clients connected by 1Gbit. I am reading a large file from an NFS mount via "dd" sending output to /dev/null with bs=4096. Using default sysctl and mount options I am seeing speeds maxing out below 1Gbit/sec. If I force NFSv3 I see speeds close to 10Gbit/sec with sufficient clients connected. I also see no issue with Ubuntu 16.04 (when used for both server and clients) in conjunction with NFSv4. I have attached the output from two iftop's which shows the status when using NFSv4 and when using NFSv3, in the NFSv4 you can clearly see one client reading at max speed and all the others apparently throttling back to practically nothing. I have additionally tested a range of mount options, which made no difference, BBR congestion control which made no difference and the following kernel settings which also made no difference: net.core.netdev_max_backlog=25 net.core.rmem_max=4194304 net.core.wmem_max=4194304 net.core.rmem_default=4194304 net.core.wmem_default=4194304 net.core.optmem_max=4194304 net.ipv4.tcp_rmem=4096 87380 4194304 net.ipv4.tcp_wmem=4096 65536 4194304 net.ipv4.tcp_mem=786432 1048576 26777216 net.ipv4.udp_mem=1529892 2039859 3059784 net.ipv4.udp_rmem_min=16384 net.ipv4.udp_wmem_min=16384 The problem is seen on dissimilar hardware, ie this problem exists when testing with an HP DL380 G10 with Mellanox 10Gbit Ethernet connected to Cisco switch, and also on a Dell R430 with Broadcom 10Gbit Ethernet connected to a Netgear switch (just to name two of several configurations that have been tested). The clients vary in each test case also, but are desktop PCs and laptops. --- ProblemType: Bug AlsaDevices: total 0 crw-rw+ 1 root audio 116, 1 Feb 15 10:23 seq crw-rw+ 1 root audio 116, 33 Feb 15 10:23 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: pass DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2022-02-14 (0 days ago) InstallationMedia: Ubuntu-Server 20.04.2 LTS "Focal Fossa" - Release amd64 (20210201.2) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: Dell Inc. PowerEdge R430 Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 mgag200drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-28-generic root=UUID=d227a745-134e-4633-9c26-bcc062655f95 ro ProcVersionSignature: Ubuntu 5.13.0-28.31~20.04.1-generic 5.13.19 RelatedPackageVersions: linux-restricted-modules-5.13.0-28-generic N/A linux-backports-modules-5.13.0-28-generic N/A linux-firmware 1.187.26 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal uec-images Uname: Linux 5.13.0-28-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 06/07/2021 dmi.bios.release: 2.13 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.13.0 dmi.board.name: 0CN7X8 dmi.board.vendor: Dell Inc. dmi.board.version: A04 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.13.0:bd06/07/2021:br2.13:svnDellInc.:pnPowerEdgeR430:pvr:rvnDellInc.:rn0CN7X8:rvrA04:cvnDellInc.:ct23:cvr:skuSKU=NotProvided;ModelName=PowerEdgeR430: dmi.product.name: PowerEdge R430 dmi.product.sku: SKU=NotProvided;ModelName=PowerEdge R430 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1960826/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1960826] Lsusb-t.txt
apport information ** Attachment added: "Lsusb-t.txt" https://bugs.launchpad.net/bugs/1960826/+attachment/5561017/+files/Lsusb-t.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/1960826 Title: NFSv4 performance problem with newer kernels Status in linux package in Ubuntu: Confirmed Bug description: I am seeing an issue with NFSv4 performance on Ubuntu 20.04.3 LTS on both clients and server (tested kernels 5.4 to 5.16), where the server is connected by 10Gbit Ethernet and with multiple clients connected by 1Gbit. I am reading a large file from an NFS mount via "dd" sending output to /dev/null with bs=4096. Using default sysctl and mount options I am seeing speeds maxing out below 1Gbit/sec. If I force NFSv3 I see speeds close to 10Gbit/sec with sufficient clients connected. I also see no issue with Ubuntu 16.04 (when used for both server and clients) in conjunction with NFSv4. I have attached the output from two iftop's which shows the status when using NFSv4 and when using NFSv3, in the NFSv4 you can clearly see one client reading at max speed and all the others apparently throttling back to practically nothing. I have additionally tested a range of mount options, which made no difference, BBR congestion control which made no difference and the following kernel settings which also made no difference: net.core.netdev_max_backlog=25 net.core.rmem_max=4194304 net.core.wmem_max=4194304 net.core.rmem_default=4194304 net.core.wmem_default=4194304 net.core.optmem_max=4194304 net.ipv4.tcp_rmem=4096 87380 4194304 net.ipv4.tcp_wmem=4096 65536 4194304 net.ipv4.tcp_mem=786432 1048576 26777216 net.ipv4.udp_mem=1529892 2039859 3059784 net.ipv4.udp_rmem_min=16384 net.ipv4.udp_wmem_min=16384 The problem is seen on dissimilar hardware, ie this problem exists when testing with an HP DL380 G10 with Mellanox 10Gbit Ethernet connected to Cisco switch, and also on a Dell R430 with Broadcom 10Gbit Ethernet connected to a Netgear switch (just to name two of several configurations that have been tested). The clients vary in each test case also, but are desktop PCs and laptops. --- ProblemType: Bug AlsaDevices: total 0 crw-rw+ 1 root audio 116, 1 Feb 15 10:23 seq crw-rw+ 1 root audio 116, 33 Feb 15 10:23 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: pass DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2022-02-14 (0 days ago) InstallationMedia: Ubuntu-Server 20.04.2 LTS "Focal Fossa" - Release amd64 (20210201.2) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: Dell Inc. PowerEdge R430 Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 mgag200drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-28-generic root=UUID=d227a745-134e-4633-9c26-bcc062655f95 ro ProcVersionSignature: Ubuntu 5.13.0-28.31~20.04.1-generic 5.13.19 RelatedPackageVersions: linux-restricted-modules-5.13.0-28-generic N/A linux-backports-modules-5.13.0-28-generic N/A linux-firmware 1.187.26 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal uec-images Uname: Linux 5.13.0-28-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 06/07/2021 dmi.bios.release: 2.13 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.13.0 dmi.board.name: 0CN7X8 dmi.board.vendor: Dell Inc. dmi.board.version: A04 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.13.0:bd06/07/2021:br2.13:svnDellInc.:pnPowerEdgeR430:pvr:rvnDellInc.:rn0CN7X8:rvrA04:cvnDellInc.:ct23:cvr:skuSKU=NotProvided;ModelName=PowerEdgeR430: dmi.product.name: PowerEdge R430 dmi.product.sku: SKU=NotProvided;ModelName=PowerEdge R430 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1960826/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1960826] Re: NFSv4 performance problem with newer kernels
apport information ** Tags added: apport-collected focal uec-images ** Description changed: I am seeing an issue with NFSv4 performance on Ubuntu 20.04.3 LTS on both clients and server (tested kernels 5.4 to 5.16), where the server is connected by 10Gbit Ethernet and with multiple clients connected by 1Gbit. I am reading a large file from an NFS mount via "dd" sending output to /dev/null with bs=4096. Using default sysctl and mount options I am seeing speeds maxing out below 1Gbit/sec. If I force NFSv3 I see speeds close to 10Gbit/sec with sufficient clients connected. I also see no issue with Ubuntu 16.04 (when used for both server and clients) in conjunction with NFSv4. I have attached the output from two iftop's which shows the status when using NFSv4 and when using NFSv3, in the NFSv4 you can clearly see one client reading at max speed and all the others apparently throttling back to practically nothing. I have additionally tested a range of mount options, which made no difference, BBR congestion control which made no difference and the following kernel settings which also made no difference: net.core.netdev_max_backlog=25 net.core.rmem_max=4194304 net.core.wmem_max=4194304 net.core.rmem_default=4194304 net.core.wmem_default=4194304 net.core.optmem_max=4194304 net.ipv4.tcp_rmem=4096 87380 4194304 net.ipv4.tcp_wmem=4096 65536 4194304 net.ipv4.tcp_mem=786432 1048576 26777216 net.ipv4.udp_mem=1529892 2039859 3059784 net.ipv4.udp_rmem_min=16384 net.ipv4.udp_wmem_min=16384 - The problem is seen on dissimilar hardware, ie this problem exists when - testing with an HP DL380 G10 with Mellanox 10Gbit Ethernet connected to - Cisco switch, and also on a Dell R430 with Broadcom 10Gbit Ethernet - connected to a Netgear switch (just to name two of several - configurations that have been tested). The clients vary in each test - case also, but are desktop PCs and laptops. + The problem is seen on dissimilar hardware, ie this problem exists when testing with an HP DL380 G10 with Mellanox 10Gbit Ethernet connected to Cisco switch, and also on a Dell R430 with Broadcom 10Gbit Ethernet connected to a Netgear switch (just to name two of several configurations that have been tested). The clients vary in each test case also, but are desktop PCs and laptops. + --- + ProblemType: Bug + AlsaDevices: + total 0 + crw-rw+ 1 root audio 116, 1 Feb 15 10:23 seq + crw-rw+ 1 root audio 116, 33 Feb 15 10:23 timer + AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' + ApportVersion: 2.20.11-0ubuntu27.21 + Architecture: amd64 + ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' + AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: + CasperMD5CheckResult: pass + DistroRelease: Ubuntu 20.04 + InstallationDate: Installed on 2022-02-14 (0 days ago) + InstallationMedia: Ubuntu-Server 20.04.2 LTS "Focal Fossa" - Release amd64 (20210201.2) + IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' + MachineType: Dell Inc. PowerEdge R430 + Package: linux (not installed) + PciMultimedia: + + ProcEnviron: + TERM=xterm + PATH=(custom, no user) + LANG=en_US.UTF-8 + SHELL=/bin/bash + ProcFB: 0 mgag200drmfb + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-28-generic root=UUID=d227a745-134e-4633-9c26-bcc062655f95 ro + ProcVersionSignature: Ubuntu 5.13.0-28.31~20.04.1-generic 5.13.19 + RelatedPackageVersions: + linux-restricted-modules-5.13.0-28-generic N/A + linux-backports-modules-5.13.0-28-generic N/A + linux-firmware 1.187.26 + RfKill: Error: [Errno 2] No such file or directory: 'rfkill' + Tags: focal uec-images + Uname: Linux 5.13.0-28-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: N/A + _MarkForUpload: True + dmi.bios.date: 06/07/2021 + dmi.bios.release: 2.13 + dmi.bios.vendor: Dell Inc. + dmi.bios.version: 2.13.0 + dmi.board.name: 0CN7X8 + dmi.board.vendor: Dell Inc. + dmi.board.version: A04 + dmi.chassis.type: 23 + dmi.chassis.vendor: Dell Inc. + dmi.modalias: dmi:bvnDellInc.:bvr2.13.0:bd06/07/2021:br2.13:svnDellInc.:pnPowerEdgeR430:pvr:rvnDellInc.:rn0CN7X8:rvrA04:cvnDellInc.:ct23:cvr:skuSKU=NotProvided;ModelName=PowerEdgeR430: + dmi.product.name: PowerEdge R430 + dmi.product.sku: SKU=NotProvided;ModelName=PowerEdge R430 + dmi.sys.vendor: Dell Inc. ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1960826/+attachment/5561012/+files/CRDA.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/1960826 Title: NFSv4 performance problem with newer kernels Status in linux package in Ubuntu: Confirmed Bug description: I am seeing an issue with NFSv4 performance on Ubuntu 20.04.3 LTS on both clients and server (tested kernels 5.4 to 5.16), where the server is conne
[Kernel-packages] [Bug 1928393] Re: linux-firmware 1.197 causes kernel to report error "amdgpu: [gfxhub0] retry page fault"
Hirsute is EOL so closing this bug. Please open a new one if the problem still persists with one of the supported series. ** Changed in: linux-firmware (Ubuntu Hirsute) Status: Incomplete => Won't Fix -- 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/1928393 Title: linux-firmware 1.197 causes kernel to report error "amdgpu: [gfxhub0] retry page fault" Status in amd: New Status in linux-firmware package in Ubuntu: Invalid Status in mesa package in Ubuntu: Invalid Status in linux-firmware source package in Hirsute: Won't Fix Bug description: After upgrading linux-firmware from 1.190.5 to 1.197 (as part of the upgrade from Ubuntu 20.10 to 21.04), I started experiencing frequent and severe GPU instability. When this happens, I see this error in dmesg: [20061.061069] amdgpu :03:00.0: amdgpu: [gfxhub0] retry page fault (src_id:0 ring:0 vmid:1 pasid:32769, for process Xorg pid 1141 thread Xorg:cs0 pid 1236) [20061.061103] amdgpu :03:00.0: amdgpu: in page starting at address 0x80401000 from client 27 [20061.061135] amdgpu :03:00.0: amdgpu: VM_L2_PROTECTION_FAULT_STATUS:0x00101031 [20061.061147] amdgpu :03:00.0: amdgpu: Faulty UTCL2 client ID: TCP (0x8) [20061.061157] amdgpu :03:00.0: amdgpu: MORE_FAULTS: 0x1 [20061.061167] amdgpu :03:00.0: amdgpu: WALKER_ERROR: 0x0 [20061.061174] amdgpu :03:00.0: amdgpu: PERMISSION_FAULTS: 0x3 [20061.061183] amdgpu :03:00.0: amdgpu: MAPPING_ERROR: 0x0 [20061.061189] amdgpu :03:00.0: amdgpu: RW: 0x0 I'll attach a couple of full dmesgs that I collected. Many of the times when this happens, the screen and keyboard freeze irreversibly (I tried waiting for more than 30 minutes, but it doesn't help). I can still log in via ssh though. When there's no freeze, I can continue using the computer normally, but the laptop fans keep running are always running and the battery depletes fast. There's probably something on a permanent loop either in the kernel or in the GPU. This bug happens several times a day, rendering the machine so unstable as to be almost unusable. It is a severe regression and I'm aghast that it passed AMD's Quality Assurance. After downgrading back to linux-firmware 1.190.5, the machine is back to the previous, mostly-reliable state. Which is to say, this bug is gone, I'm just left with the other amdgpu suspend bug I've learned to live with since I bought this computer. Please revert the amdgpu firmware in this package as soon as possible. This is unbearable. Relevant information: Ubuntu version: 21.04 Linux kernel: 5.11.0-17-generic x86_64 CPU model: AMD Ryzen 7 3700U with Radeon Vega Mobile Gfx GPU: 03:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Picasso (rev c1) Laptop model: Lenovo Ideapad S145 To manage notifications about this bug go to: https://bugs.launchpad.net/amd/+bug/1928393/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1909499] Re: iwlwifi 0000:03:00.0: No beacon heard and the time event is over already...
No response and seems to be resolved at least for some users. Please open a new bug if the problem still persists. ** Changed in: linux-firmware (Ubuntu) Status: Confirmed => Invalid -- 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/1909499 Title: iwlwifi :03:00.0: No beacon heard and the time event is over already... Status in linux-firmware package in Ubuntu: Invalid Bug description: I see this error frequently inside logs: iwlwifi :03:00.0: No beacon heard and the time event is over already... Also, the internet doesn't seem stable, from time to time it disconnects and reconnects on its own, and other times it disconnects and wants me to enter the key again to connect. However, if i hit the X button to close the password modal and try to connect again from the networks list, it does connect without the need to enter the password. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-firmware 1.187.6 ProcVersionSignature: Ubuntu 5.4.0-58.64-lowlatency 5.4.73 Uname: Linux 5.4.0-58-lowlatency x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lyubo 14448 F pulseaudio /dev/snd/pcmC0D0p: lyubo 14448 F...m pulseaudio CasperMD5CheckResult: skip Date: Mon Dec 28 21:50:51 2020 Dependencies: InstallationDate: Installed on 2020-12-27 (0 days ago) InstallationMedia: Kubuntu 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 004: ID 04f2:b5f7 Chicony Electronics Co., Ltd HD WebCam Bus 001 Device 003: ID 8087:0aa7 Intel Corp. Bus 001 Device 002: ID 275d:0ba6 USB OPTICAL MOUSE Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Acer Aspire A515-51G PackageArchitecture: all ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-58-lowlatency root=/dev/mapper/vgkubuntu-root ro quiet splash lockdown=confidentiality 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-58-lowlatency N/A linux-backports-modules-5.4.0-58-lowlatency N/A linux-firmware 1.187.6 SourcePackage: linux-firmware UpgradeStatus: No upgrade log present (probably fresh install) 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1909499/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1908800] Re: Wireless card crashes daily on my XPS 13 9380
** Also affects: linux-firmware (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: linux-firmware (Ubuntu) Status: New => Incomplete -- 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/1908800 Title: Wireless card crashes daily on my XPS 13 9380 Status in linux-firmware package in Ubuntu: Incomplete Status in linux-firmware source package in Focal: New Bug description: Hello all, Daily, or multiple times per day, the wireless card on my XPS 13 9380 crashes, forcing me to shutdown my computer and then boot it back up. I am on Ubuntu 20.04, and here is the results from dmesg -T right after such a crash happens: [Sat Dec 19 15:08:59 2020] ath10k_pci :02:00.0: firmware crashed! (guid 170ee3ba-1809-4276-9b34-9d4e37da0937) [Sat Dec 19 15:08:59 2020] ath10k_pci :02:00.0: qca6174 hw3.2 target 0x0503 chip_id 0x00340aff sub 1a56:143a [Sat Dec 19 15:08:59 2020] ath10k_pci :02:00.0: kconfig debug 0 debugfs 1 tracing 1 dfs 0 testmode 0 [Sat Dec 19 15:08:59 2020] ath10k_pci :02:00.0: firmware ver WLAN.RM.4.4.1-00140-QCARMSWPZ-1 api 6 features wowlan,ignore-otp,mfp crc32 29eb8ca1 [Sat Dec 19 15:08:59 2020] ath10k_pci :02:00.0: board_file api 2 bmi_id N/A crc32 4ac0889b [Sat Dec 19 15:08:59 2020] ath10k_pci :02:00.0: htt-ver 3.60 wmi-op 4 htt-op 3 cal otp max-sta 32 raw 0 hwcrypto 1 [Sat Dec 19 15:08:59 2020] ath10k_pci :02:00.0: failed to get memcpy hi address for firmware address 4: -16 [Sat Dec 19 15:08:59 2020] ath10k_pci :02:00.0: failed to read firmware dump area: -16 [Sat Dec 19 15:08:59 2020] ath10k_pci :02:00.0: Copy Engine register dump: [Sat Dec 19 15:08:59 2020] ath10k_pci :02:00.0: [00]: 0x00034400 11 11 3 3 [Sat Dec 19 15:08:59 2020] ath10k_pci :02:00.0: [01]: 0x00034800 23 23 164 165 [Sat Dec 19 15:08:59 2020] ath10k_pci :02:00.0: [02]: 0x00034c00 31 30 93 94 [Sat Dec 19 15:08:59 2020] ath10k_pci :02:00.0: [03]: 0x00035000 20 20 22 20 [Sat Dec 19 15:08:59 2020] ath10k_pci :02:00.0: [04]: 0x00035400 4711 4707 114 50 [Sat Dec 19 15:08:59 2020] ath10k_pci :02:00.0: [05]: 0x00035800 0 0 64 0 [Sat Dec 19 15:08:59 2020] ath10k_pci :02:00.0: [06]: 0x00035c00 7 7 12 12 [Sat Dec 19 15:08:59 2020] ath10k_pci :02:00.0: [07]: 0x00036000 1 0 1 0 [Sat Dec 19 15:08:59 2020] ath10k_pci :02:00.0: failed to read hi_board_data address: -28 [Sat Dec 19 15:08:59 2020] ieee80211 phy0: Hardware restart was requested [Sat Dec 19 15:08:59 2020] ath10k_pci :02:00.0: unsupported HTC service id: 1536 [Sat Dec 19 15:08:59 2020] ath10k_pci :02:00.0: device successfully recovered lsb_release -rd Description: Ubuntu 20.04.1 LTS Release: 20.04 apt-cache policy linux-firmware linux-firmware: Installed: 1.187.6 Candidate: 1.187.6 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-firmware 1.187.6 ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73 Uname: Linux 5.4.0-58-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bsbrom 3384 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Dec 19 15:21:02 2020 Dependencies: InstallationDate: Installed on 2020-09-05 (105 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Dell Inc. XPS 13 9380 PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/usr/bin/fish ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_wxgq6h@/vmlinuz-5.4.0-58-generic root=ZFS=rpool/ROOT/ubuntu_wxgq6h ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-5.4.0-58-generic N/A linux-backports-modules-5.4.0-58-generic N/A linux-firmware1.187.6 SourcePackage: linux-firmware UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/06/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.11.0 dmi.board.name: 0KTW76 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.11.0:bd07/06/2020:svnDellInc.:pnXPS139380:pvr:rvnDellInc.:rn0KTW76:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9380 dmi.product.sku: 08AF dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1908800/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages
[Kernel-packages] [Bug 1909836] Re: iwlwifi crashes when getting image from IPWebcam
No response, so closing. Please open a new bug if the problems still persists. ** Changed in: linux-firmware (Ubuntu) Status: New => Invalid -- 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/1909836 Title: iwlwifi crashes when getting image from IPWebcam Status in linux-firmware package in Ubuntu: Invalid Bug description: I am getting "Microcode SW error detected. Restarting 0x8200." dmesg after making http/https request to a particular web server. I have Lenovo Yoga 370, Ubuntu 16.04.7 LTS, after fresh apt-get update and upgrade. I normally (heavily) use wifi for all the possible things. One single particular Android app which allows to use cell phone cameras as webcams via http or https causes iwlwifi to crash. Fully reproducible. To reproduce: 1. Download to your android cell phone: https://play.google.com/store/apps/details?id=com.pas.webcam&hl=en&gl=US 2. Connect both the computer and the cell phone to the same wifi. 3. Get the auto-focussed image from the cell phone by requesting: http://192.168.0.103:8080/photoaf.jpg (replace the IP with the IP of your cell phone) 4. (You *will* get the image correctly downloaded.) 5. Observe "No networks available notification", see dmesg (attached). Following this tip: https://forums.linuxmint.com/viewtopic.php?p=1641176&sid=a97b63d2196745139e281ff7a3b40dc2#p1641176 I saw that 16.04 only had 3 versions: ls /lib/firmware/ | grep 9260 iwlwifi-9260-th-b0-jf-b0-33.ucode iwlwifi-9260-th-b0-jf-b0-34.ucode iwlwifi-9260-th-b0-jf-b0-38.ucode So I tried manually downloading the driver and adding it there: sudo mv iwlwifi-9260-th-b0-jf-b0-46.ucode /lib/firmware/ I do not know if it got activated at all. In any case, the crash persists even after the restart. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1909836/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1960826] Re: NFSv4 performance problem with newer kernels
apport-collect 1960826 just writings out "." endlessly. The documentation says that apport-bug collects the same info so I have manually created a file locally which I have attached here. HTH, if something else is required please let me know. ** Attachment added: "1960826.apport" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1960826/+attachment/5561011/+files/1960826.apport ** 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/1960826 Title: NFSv4 performance problem with newer kernels Status in linux package in Ubuntu: Confirmed Bug description: I am seeing an issue with NFSv4 performance on Ubuntu 20.04.3 LTS on both clients and server (tested kernels 5.4 to 5.16), where the server is connected by 10Gbit Ethernet and with multiple clients connected by 1Gbit. I am reading a large file from an NFS mount via "dd" sending output to /dev/null with bs=4096. Using default sysctl and mount options I am seeing speeds maxing out below 1Gbit/sec. If I force NFSv3 I see speeds close to 10Gbit/sec with sufficient clients connected. I also see no issue with Ubuntu 16.04 (when used for both server and clients) in conjunction with NFSv4. I have attached the output from two iftop's which shows the status when using NFSv4 and when using NFSv3, in the NFSv4 you can clearly see one client reading at max speed and all the others apparently throttling back to practically nothing. I have additionally tested a range of mount options, which made no difference, BBR congestion control which made no difference and the following kernel settings which also made no difference: net.core.netdev_max_backlog=25 net.core.rmem_max=4194304 net.core.wmem_max=4194304 net.core.rmem_default=4194304 net.core.wmem_default=4194304 net.core.optmem_max=4194304 net.ipv4.tcp_rmem=4096 87380 4194304 net.ipv4.tcp_wmem=4096 65536 4194304 net.ipv4.tcp_mem=786432 1048576 26777216 net.ipv4.udp_mem=1529892 2039859 3059784 net.ipv4.udp_rmem_min=16384 net.ipv4.udp_wmem_min=16384 The problem is seen on dissimilar hardware, ie this problem exists when testing with an HP DL380 G10 with Mellanox 10Gbit Ethernet connected to Cisco switch, and also on a Dell R430 with Broadcom 10Gbit Ethernet connected to a Netgear switch (just to name two of several configurations that have been tested). The clients vary in each test case also, but are desktop PCs and laptops. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1960826/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1908800] Re: Wireless card crashes daily on my XPS 13 9380
@benuski, Can you confirm that this is still an issue with an up-to-date Focal 20.04 system? @craigwharding, 21.04 is EOL. Is this still an issue with Impish 21.10? -- 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/1908800 Title: Wireless card crashes daily on my XPS 13 9380 Status in linux-firmware package in Ubuntu: Incomplete Status in linux-firmware source package in Focal: New Bug description: Hello all, Daily, or multiple times per day, the wireless card on my XPS 13 9380 crashes, forcing me to shutdown my computer and then boot it back up. I am on Ubuntu 20.04, and here is the results from dmesg -T right after such a crash happens: [Sat Dec 19 15:08:59 2020] ath10k_pci :02:00.0: firmware crashed! (guid 170ee3ba-1809-4276-9b34-9d4e37da0937) [Sat Dec 19 15:08:59 2020] ath10k_pci :02:00.0: qca6174 hw3.2 target 0x0503 chip_id 0x00340aff sub 1a56:143a [Sat Dec 19 15:08:59 2020] ath10k_pci :02:00.0: kconfig debug 0 debugfs 1 tracing 1 dfs 0 testmode 0 [Sat Dec 19 15:08:59 2020] ath10k_pci :02:00.0: firmware ver WLAN.RM.4.4.1-00140-QCARMSWPZ-1 api 6 features wowlan,ignore-otp,mfp crc32 29eb8ca1 [Sat Dec 19 15:08:59 2020] ath10k_pci :02:00.0: board_file api 2 bmi_id N/A crc32 4ac0889b [Sat Dec 19 15:08:59 2020] ath10k_pci :02:00.0: htt-ver 3.60 wmi-op 4 htt-op 3 cal otp max-sta 32 raw 0 hwcrypto 1 [Sat Dec 19 15:08:59 2020] ath10k_pci :02:00.0: failed to get memcpy hi address for firmware address 4: -16 [Sat Dec 19 15:08:59 2020] ath10k_pci :02:00.0: failed to read firmware dump area: -16 [Sat Dec 19 15:08:59 2020] ath10k_pci :02:00.0: Copy Engine register dump: [Sat Dec 19 15:08:59 2020] ath10k_pci :02:00.0: [00]: 0x00034400 11 11 3 3 [Sat Dec 19 15:08:59 2020] ath10k_pci :02:00.0: [01]: 0x00034800 23 23 164 165 [Sat Dec 19 15:08:59 2020] ath10k_pci :02:00.0: [02]: 0x00034c00 31 30 93 94 [Sat Dec 19 15:08:59 2020] ath10k_pci :02:00.0: [03]: 0x00035000 20 20 22 20 [Sat Dec 19 15:08:59 2020] ath10k_pci :02:00.0: [04]: 0x00035400 4711 4707 114 50 [Sat Dec 19 15:08:59 2020] ath10k_pci :02:00.0: [05]: 0x00035800 0 0 64 0 [Sat Dec 19 15:08:59 2020] ath10k_pci :02:00.0: [06]: 0x00035c00 7 7 12 12 [Sat Dec 19 15:08:59 2020] ath10k_pci :02:00.0: [07]: 0x00036000 1 0 1 0 [Sat Dec 19 15:08:59 2020] ath10k_pci :02:00.0: failed to read hi_board_data address: -28 [Sat Dec 19 15:08:59 2020] ieee80211 phy0: Hardware restart was requested [Sat Dec 19 15:08:59 2020] ath10k_pci :02:00.0: unsupported HTC service id: 1536 [Sat Dec 19 15:08:59 2020] ath10k_pci :02:00.0: device successfully recovered lsb_release -rd Description: Ubuntu 20.04.1 LTS Release: 20.04 apt-cache policy linux-firmware linux-firmware: Installed: 1.187.6 Candidate: 1.187.6 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-firmware 1.187.6 ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73 Uname: Linux 5.4.0-58-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bsbrom 3384 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Dec 19 15:21:02 2020 Dependencies: InstallationDate: Installed on 2020-09-05 (105 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Dell Inc. XPS 13 9380 PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/usr/bin/fish ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_wxgq6h@/vmlinuz-5.4.0-58-generic root=ZFS=rpool/ROOT/ubuntu_wxgq6h ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-5.4.0-58-generic N/A linux-backports-modules-5.4.0-58-generic N/A linux-firmware1.187.6 SourcePackage: linux-firmware UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/06/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.11.0 dmi.board.name: 0KTW76 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.11.0:bd07/06/2020:svnDellInc.:pnXPS139380:pvr:rvnDellInc.:rn0KTW76:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9380 dmi.product.sku: 08AF dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1908800/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packag
[Kernel-packages] [Bug 1959529] Re: Hipersocket page allocation failure on Ubuntu 20.04 based SSC environments
** Changed in: linux (Ubuntu Focal) Status: In Progress => Fix Committed ** Changed in: linux (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1959529 Title: Hipersocket page allocation failure on Ubuntu 20.04 based SSC environments Status in Ubuntu on IBM z Systems: In Progress Status in linux package in Ubuntu: Fix Released Status in linux source package in Focal: Fix Committed Bug description: == Comment: #0 - D. Gary Chapman - 2022-01-26 12:43:25 == ---Problem Description--- IBM IDAA customer exposes hipersocket page allocation failure on Ubuntu 20.04 based SSC Contact Information = Gary Chapman (ch...@us.ibm.com) ---uname output--- 5.4.0-73-generic #82-Ubuntu Machine Type = IBM Z in IDAA SSC-mode lpar ---Debugger--- A debugger is not configured -- IBM SSC LEVEL: 4.1.5 IBM IDAA LEVEL: 7.5.6 On a client system we are observing this: Jan 19 16:25:57 data5 kernel: kworker/u760:28: page allocation failure: order:0, mode:0xa20(GFP_ATOMIC), nodemask=(null),cpuset=/,mems_allowed=0 Jan 19 16:25:57 data5 kernel: CPU: 20 PID: 4137988 Comm: kworker/u760:28 Kdump: loaded Tainted: G OE 5.4.0-73-generic #82-Ubuntu Jan 19 16:25:57 data5 kernel: Hardware name: IBM 8561 T01 727 (LPAR) Jan 19 16:25:57 data5 kernel: Workqueue: kcryptd/253:11 kcryptd_crypt [dm_crypt] Jan 19 16:25:57 data5 kernel: Call Trace: Jan 19 16:25:57 data5 kernel: ([<006b6d63e092>] show_stack+0x7a/0xc0) Jan 19 16:25:57 data5 kernel: [<006b6d64588a>] dump_stack+0x8a/0xb8 Jan 19 16:25:57 data5 kernel: [<006b6cfd8262>] warn_alloc+0xe2/0x160 IBM LTC Networking team has identified the upstream commit 714c9108851743bb718fbc1bfb81290f12a53854 as the root cause. This patch shows up in the Ubuntu kernel source tree: https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/commit/?id=714c9108851743bb718fbc1bfb81290f12a53854 but has not been ported to Ubuntu 20.04 / kernel 5.4 IDAA on SSC requests backport to focal. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1959529/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1922350] Re: missing firmware reported when updating initramfs
Closing this as won't fix. We can revisit and open new bugs if specific firmware blobs are needed and can be tested by the reporter. As discussed on the mailing list [1], we're not blindly adding firmwares that initramfs-tools complains are missing. [1] https://lists.ubuntu.com/archives/kernel-team/2021-April/119192.html ** Changed in: linux-firmware (Ubuntu Bionic) Status: In Progress => Won't Fix ** Changed in: linux-firmware (Ubuntu Focal) Status: In Progress => Won't Fix ** Changed in: linux-firmware (Ubuntu) Status: In Progress => Invalid -- 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/1922350 Title: missing firmware reported when updating initramfs Status in HWE Next: New Status in linux-firmware package in Ubuntu: Invalid Status in linux-firmware source package in Bionic: Won't Fix Status in linux-firmware source package in Focal: Won't Fix Status in linux-firmware source package in Groovy: Won't Fix Status in linux-firmware source package in Hirsute: Won't Fix Bug description: [SRU Justification] [Impact] Some kernel firmwares might be landed after linux-firmware forked for each series, or for LTS series, kernels of new versions may claim additional ones that were not previously available. This leaves devices fail to function correctly while they ought to. With a checking script that enumerates all the blobs available in upstream repo and in the Ubuntu fork of a given series, e.g. hirsute, iterate through all the installed kernel modules of a given version to check if claimed firmware blobs are available in Ubuntu's fork. Following kernel version/series have been checked: * 5.11.0-14-generic/hirsute * 5.8.0-48-generic/groovy * 5.4.0-70-generic/focal * 5.6.0-1052-oem/focal * 5.8.0-48-generic/focal * 5.10.0-1019-oem/focal * 4.15.0-140-generic/bionic * 4.18.0-25-generic/bionic * 5.0.0-65-generic/bionic * 5.4.0-70-generic/bionic And it gives following files were missing in at least one of above cases: * amdgpu/arcturus_asd.bin * amdgpu/arcturus_gpu_info.bin * amdgpu/arcturus_mec.bin * amdgpu/arcturus_mec2.bin * amdgpu/arcturus_rlc.bin * amdgpu/arcturus_sdma.bin * amdgpu/arcturus_smc.bin * amdgpu/arcturus_sos.bin * amdgpu/arcturus_ta.bin * amdgpu/arcturus_vcn.bin * amdgpu/navi12_asd.bin * amdgpu/navi12_ce.bin * amdgpu/navi12_dmcu.bin * amdgpu/navi12_gpu_info.bin * amdgpu/navi12_me.bin * amdgpu/navi12_mec.bin * amdgpu/navi12_mec2.bin * amdgpu/navi12_pfp.bin * amdgpu/navi12_rlc.bin * amdgpu/navi12_sdma.bin * amdgpu/navi12_sdma1.bin * amdgpu/navi12_smc.bin * amdgpu/navi12_sos.bin * amdgpu/navi12_ta.bin * amdgpu/navi12_vcn.bin * amdgpu/navy_flounder_ce.bin * amdgpu/navy_flounder_dmcub.bin * amdgpu/navy_flounder_me.bin * amdgpu/navy_flounder_mec.bin * amdgpu/navy_flounder_mec2.bin * amdgpu/navy_flounder_pfp.bin * amdgpu/navy_flounder_rlc.bin * amdgpu/navy_flounder_sdma.bin * amdgpu/navy_flounder_smc.bin * amdgpu/navy_flounder_sos.bin * amdgpu/navy_flounder_ta.bin * amdgpu/navy_flounder_vcn.bin * amdgpu/oland_uvd.bin * amdgpu/pitcairn_uvd.bin * amdgpu/renoir_asd.bin * amdgpu/renoir_ce.bin * amdgpu/renoir_gpu_info.bin * amdgpu/renoir_me.bin * amdgpu/renoir_mec.bin * amdgpu/renoir_mec2.bin * amdgpu/renoir_pfp.bin * amdgpu/renoir_rlc.bin * amdgpu/renoir_sdma.bin * amdgpu/renoir_ta.bin * amdgpu/renoir_vcn.bin * amdgpu/sienna_cichlid_ce.bin * amdgpu/sienna_cichlid_dmcub.bin * amdgpu/sienna_cichlid_me.bin * amdgpu/sienna_cichlid_mec.bin * amdgpu/sienna_cichlid_mec2.bin * amdgpu/sienna_cichlid_pfp.bin * amdgpu/sienna_cichlid_rlc.bin * amdgpu/sienna_cichlid_sdma.bin * amdgpu/sienna_cichlid_smc.bin * amdgpu/sienna_cichlid_sos.bin * amdgpu/sienna_cichlid_ta.bin * amdgpu/sienna_cichlid_vcn.bin * amdgpu/tahiti_uvd.bin * amdgpu/vega20_ta.bin * amdgpu/verde_uvd.bin * atmel/wilc1000_wifi_firmware-1.bin * cmmb_vega_12mhz.inp * cmmb_venice_12mhz.inp * dvb_nova_12mhz.inp * dvb_nova_12mhz_b0.inp * i915/bxt_guc_33.0.0.bin * i915/glk_guc_33.0.0.bin * i915/icl_guc_33.0.0.bin * i915/kbl_guc_33.0.0.bin * i915/skl_guc_33.0.0.bin * i915/tgl_dmc_ver2_04.bin * i915/tgl_huc_7.5.0.bin * isdbt_nova_12mhz.inp * isdbt_nova_12mhz_b0.inp * isdbt_rio.inp * iwlwifi-Qu-b0-hr-b0-59.ucode * iwlwifi-Qu-b0-jf-b0-50.ucode * iwlwifi-Qu-b0-jf-b0-59.ucode * iwlwifi-Qu-c0-hr-b0-50.ucode * iwlwifi-Qu-c0-hr-b0-59.ucode * iwlwifi-QuZ-a0-hr-b0-50.ucode * iwlwifi-QuZ-a0-hr-b0-59.ucode * iwlwifi-QuZ-a0-jf-b0-50.ucode * iwlwifi-QuZ-a0-jf-b0-59.ucode * iwlwifi-cc-a0-50.ucode * i
[Kernel-packages] [Bug 1960681] Re: Bionic update: upstream stable patchset 2022-02-11
** 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/1960681
Title:
Bionic update: upstream stable patchset 2022-02-11
Status in linux package in Ubuntu:
Invalid
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 2022-02-11
Ported from the following upstream stable releases:
v4.14.263, v4.19.226
from git://git.kernel.org/
Bluetooth: bfusb: fix division by zero in send path
USB: core: Fix bug in resuming hub's handling of wakeup requests
USB: Fix "slab-out-of-bounds Write" bug in usb_hcd_poll_rh_status
mfd: intel-lpss: Fix too early PM enablement in the ACPI ->probe()
can: gs_usb: fix use of uninitialized variable, detach device on reception of
invalid USB data
can: gs_usb: gs_can_start_xmit(): zero-initialize hf->{flags,reserved}
random: fix data race on crng_node_pool
random: fix data race on crng init time
staging: wlan-ng: Avoid bitwise vs logical OR warning in
hfa384x_usb_throttlefn()
drm/i915: Avoid bitwise vs logical OR warning in snb_wm_latency_quirk()
orangefs: Fix the size of a memory allocation in orangefs_bufmap_alloc()
media: uvcvideo: fix division by zero at stream start
rtlwifi: rtl8192cu: Fix WARNING when calling local_irq_restore() with
interrupts enabled
Bluetooth: schedule SCO timeouts with delayed_work
Bluetooth: fix init and cleanup of sco_conn.timeout_work
HID: uhid: Fix worker destroying device without any protection
HID: wacom: Ignore the confidence flag when a touch is removed
HID: wacom: Avoid using stale array indicies to read contact count
nfc: llcp: fix NULL error pointer dereference on sendmsg() after failed bind()
rtc: cmos: take rtc_lock while reading from CMOS
media: flexcop-usb: fix control-message timeouts
media: mceusb: fix control-message timeouts
media: em28xx: fix control-message timeouts
media: cpia2: fix control-message timeouts
media: s2255: fix control-message timeouts
media: dib0700: fix undefined behavior in tuner shutdown
media: redrat3: fix control-message timeouts
media: pvrusb2: fix control-message timeouts
media: stk1160: fix control-message timeouts
can: softing_cs: softingcs_probe(): fix memleak on registration failure
shmem: fix a race between shmem_unused_huge_shrink and shmem_evict_inode
PCI: Add function 1 DMA alias quirk for Marvell 88SE9125 SATA controller
Bluetooth: cmtp: fix possible panic when cmtp_init_sockets() fails
clk: bcm-2835: Pick the closest clock rate
clk: bcm-2835: Remove rounding up the dividers
wcn36xx: Indicate beacon not connection loss on MISSED_BEACON_IND
media: em28xx: fix memory leak in em28xx_init_dev
Bluetooth: stop proccessing malicious adv data
media: dmxdev: fix UAF when dvb_register_device() fails
crypto: qce - fix uaf on qce_ahash_register_one
tty: serial: atmel: Check return code of dmaengine_submit()
tty: serial: atmel: Call dma_async_issue_pending()
media: mtk-vcodec: call v4l2_m2m_ctx_release first when file is released
netfilter: bridge: add support for pppoe filtering
arm64: dts: qcom: msm8916: fix MMC controller aliases
drm/amdgpu: Fix a NULL pointer dereference in
amdgpu_connector_lcd_native_mode()
drm/radeon/radeon_kms: Fix a NULL pointer dereference in
radeon_driver_open_kms()
serial: amba-pl011: do not request memory region twice
floppy: Fix hang in watchdog when disk is ejected
media: dib8000: Fix a memleak in dib8000_init()
media: saa7146: mxb: Fix a NULL pointer dereference in mxb_attach()
media: si2157: Fix "warm" tuner state detection
sched/rt: Try to restart rt period timer when rt runtime exceeded
media: dw2102: Fix use after free
media: msi001: fix possible null-ptr-deref in msi001_probe()
usb: ftdi-elan: fix memory leak on device disconnect
x86/mce/inject: Avoid out-of-bounds write when setting flags
pcmcia: rsrc_nonstatic: Fix a NULL pointer dereference in
__nonstatic_find_io_region()
pcmcia: rsrc_nonstatic: Fix a NULL pointer dereference in
nonstatic_find_mem_region()
ppp: ensure minimum packet size in ppp_write()
fsl/fman: Check for null pointer after calling devm_ioremap
spi: spi-meson-spifc: Add missing pm_runtime_disable() in meson_spifc_probe
tpm: add request_locality before write TPM_INT_ENABLE
can: softing:
[Kernel-packages] [Bug 1958467] Re: focal linux-firmware package omits amdgpu/navi12 firmware
** Description changed: + [Impact] + The 20.04 LTS linux-firmware package list was cut before the amdgpu/navi12* firmware files were upstreamed to the Linux kernel repository, which is unfortunate because this hardware is older than some other included firmware (navi14*), and the firmware is required for using the AMDGPU kernel module on AWS EC2 cloud instances with AMD GPUs. The files are included in 21.04 and 21.10, but to date they have not been included in the LTS hardware-enablement releases for 20.04. It would be helpful to include the navi12 firmware files for the next LTS+HWE release, since 22.04 isn't due out for a while. Without this firmware it is difficult to get AWS EC2 G4ad instances working with Ubuntu, as customers need to manually download and install the firmware from a reputable source and put it into the appropriate directory, which is not the experience they expect on hardware that is over a year old with the most recent HWE release. + + [Test Case] + + See above. + + [Fix] + + Backport amdgpu/nav12* from linux-firmware Jammy. + + [Where Problems Could Occur] + + Graphics problems, kernel crashes on machines with AMD GPU. + + [Notes] + + This is required for the HWE kernel so not fixing Impish. ** Also affects: linux-firmware (Ubuntu Impish) Importance: Undecided Status: New ** Also affects: linux-firmware (Ubuntu Jammy) Importance: Undecided Status: Invalid ** Changed in: linux-firmware (Ubuntu Impish) Status: New => Won't Fix ** Description changed: [Impact] The 20.04 LTS linux-firmware package list was cut before the amdgpu/navi12* firmware files were upstreamed to the Linux kernel repository, which is unfortunate because this hardware is older than some other included firmware (navi14*), and the firmware is required for using the AMDGPU kernel module on AWS EC2 cloud instances with AMD GPUs. The files are included in 21.04 and 21.10, but to date they have not been included in the LTS hardware-enablement releases for 20.04. It would be helpful to include the navi12 firmware files for the next LTS+HWE release, since 22.04 isn't due out for a while. Without this firmware it is difficult to get AWS EC2 G4ad instances working with Ubuntu, as customers need to manually download and install the firmware from a reputable source and put it into the appropriate directory, which is not the experience they expect on hardware that is over a year old with the most recent HWE release. [Test Case] See above. [Fix] Backport amdgpu/nav12* from linux-firmware Jammy. [Where Problems Could Occur] Graphics problems, kernel crashes on machines with AMD GPU. [Notes] - This is required for the HWE kernel so not fixing Impish. + This is required for the HWE kernel so not updating linux-firmware in + Impish. -- 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/1958467 Title: focal linux-firmware package omits amdgpu/navi12 firmware Status in linux-firmware package in Ubuntu: Invalid Status in linux-firmware source package in Focal: Triaged Status in linux-firmware source package in Impish: Won't Fix Status in linux-firmware source package in Jammy: Invalid Bug description: [Impact] The 20.04 LTS linux-firmware package list was cut before the amdgpu/navi12* firmware files were upstreamed to the Linux kernel repository, which is unfortunate because this hardware is older than some other included firmware (navi14*), and the firmware is required for using the AMDGPU kernel module on AWS EC2 cloud instances with AMD GPUs. The files are included in 21.04 and 21.10, but to date they have not been included in the LTS hardware-enablement releases for 20.04. It would be helpful to include the navi12 firmware files for the next LTS+HWE release, since 22.04 isn't due out for a while. Without this firmware it is difficult to get AWS EC2 G4ad instances working with Ubuntu, as customers need to manually download and install the firmware from a reputable source and put it into the appropriate directory, which is not the experience they expect on hardware that is over a year old with the most recent HWE release. [Test Case] See above. [Fix] Backport amdgpu/nav12* from linux-firmware Jammy. [Where Problems Could Occur] Graphics problems, kernel crashes on machines with AMD GPU. [Notes] This is required for the HWE kernel so not updating linux-firmware in Impish. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1958467/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/L
[Kernel-packages] [Bug 1960861] Re: Impish update: upstream stable patchset 2022-02-14
** Changed in: linux (Ubuntu Impish) 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/1960861 Title: Impish update: upstream stable patchset 2022-02-14 Status in linux package in Ubuntu: Invalid Status in linux source package in Impish: 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 2022-02-14 Ported from the following upstream stable releases: v5.10.93, v5.15.16 from git://git.kernel.org/ devtmpfs regression fix: reconfigure on each mount orangefs: Fix the size of a memory allocation in orangefs_bufmap_alloc() remoteproc: qcom: pil_info: Don't memcpy_toio more than is provided perf: Protect perf_guest_cbs with RCU KVM: x86: Register Processor Trace interrupt hook iff PT enabled in guest KVM: s390: Clarify SIGP orders versus STOP/RESTART 9p: only copy valid iattrs in 9P2000.L setattr implementation video: vga16fb: Only probe for EGA and VGA 16 color graphic cards media: uvcvideo: fix division by zero at stream start rtlwifi: rtl8192cu: Fix WARNING when calling local_irq_restore() with interrupts enabled firmware: qemu_fw_cfg: fix sysfs information leak firmware: qemu_fw_cfg: fix NULL-pointer deref on duplicate entries firmware: qemu_fw_cfg: fix kobject leak in probe error path KVM: x86: remove PMU FIXED_CTR3 from msrs_to_save_all ALSA: hda/realtek: Add speaker fixup for some Yoga 15ITL5 devices ALSA: hda/realtek - Fix silent output on Gigabyte X570 Aorus Master after reboot from Windows ALSA: hda: ALC287: Add Lenovo IdeaPad Slim 9i 14ITL5 speaker quirk ALSA: hda/realtek: Add quirk for Legion Y9000X 2020 ALSA: hda/realtek: Re-order quirk entries for Lenovo powerpc/pseries: Get entry and uaccess flush required bits from H_GET_CPU_CHARACTERISTICS mtd: fixup CFI on ixp4xx KVM: x86: don't print when fail to read/write pv eoi memory remoteproc: qcom: pas: Add missing power-domain "mxc" for CDSP perf annotate: Avoid TUI crash when navigating in the annotation of recursive functions ALSA: hda/realtek: Use ALC285_FIXUP_HP_GPIO_LED on another HP laptop ALSA: hda/tegra: Fix Tegra194 HDA reset failure UBUNTU: upstream stable to v5.10.93, v5.15.16 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1960861/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1827982] Re: hyperv_stimer in ubuntu_kvm_unit_tests failed on B-KVM / B-Oracle-5.3 / B-Oracle-5.4
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux-kvm (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oracle in Ubuntu. https://bugs.launchpad.net/bugs/1827982 Title: hyperv_stimer in ubuntu_kvm_unit_tests failed on B-KVM / B-Oracle-5.3 / B-Oracle-5.4 Status in ubuntu-kernel-tests: New Status in linux-kvm package in Ubuntu: Confirmed Status in linux-oracle package in Ubuntu: Confirmed Bug description: Test timeouted. # TESTNAME=hyperv_stimer TIMEOUT=90s ACCEL= ./x86/run x86/hyperv_stimer.flat -smp 2 -cpu kvm64,hv_vpindex,hv_time,hv_synic,hv_stimer -device hyperv-testdev timeout -k 1s --foreground 90s /usr/bin/qemu-system-x86_64 -nodefaults -device pc-testdev -device isa-debug-exit,iobase=0xf4,iosize=0x4 -vnc none -serial stdio -device pci-testdev -machine accel=kvm -kernel x86/hyperv_stimer.flat -smp 2 -cpu kvm64,hv_vpindex,hv_time,hv_synic,hv_stimer -device hyperv-testdev # -initrd /tmp/tmp.ouYfwUEdq5 qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.01H:EDX.vme [bit 1] qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.01H:EDX.vme [bit 1] enabling apic enabling apic paging enabled cr0 = 80010011 cr3 = 459000 cr4 = 20 enabling apic cpus = 2 qemu-system-x86_64: terminating on signal 15 from pid 2224 (timeout) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-1032-kvm 4.15.0-1032.32 ProcVersionSignature: User Name 4.15.0-1032.32-kvm 4.15.18 Uname: Linux 4.15.0-1032-kvm x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 Date: Tue May 7 03:39:16 2019 SourcePackage: linux-kvm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1827982/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1827980] Re: hyperv_synic in ubuntu_kvm_unit_tests failed on B-KVM / B-Oracle-5.3
Timeout on d2022.02.03/jammy/linux-realtime/5.15.0-1005.5 (rumford.amd64) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oracle in Ubuntu. https://bugs.launchpad.net/bugs/1827980 Title: hyperv_synic in ubuntu_kvm_unit_tests failed on B-KVM / B-Oracle-5.3 Status in ubuntu-kernel-tests: New Status in linux-kvm package in Ubuntu: Confirmed Status in linux-oracle package in Ubuntu: Confirmed Bug description: Test timeout. # TESTNAME=hyperv_synic TIMEOUT=90s ACCEL= ./x86/run x86/hyperv_synic.flat -smp 2 -cpu kvm64,hv_vpindex,hv_synic -device hyperv-testdev timeout -k 1s --foreground 90s /usr/bin/qemu-system-x86_64 -nodefaults -device pc-testdev -device isa-debug-exit,iobase=0xf4,iosize=0x4 -vnc none -serial stdio -device pci-testdev -machine accel=kvm -kernel x86/hyperv_synic.flat -smp 2 -cpu kvm64,hv_vpindex,hv_synic -device hyperv-testdev # -initrd /tmp/tmp.LeYhxJZmHV qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.01H:EDX.vme [bit 1] qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.01H:EDX.vme [bit 1] enabling apic enabling apic paging enabled cr0 = 80010011 cr3 = 459000 cr4 = 20 enabling apic ncpus = 2 prepare qemu-system-x86_64: terminating on signal 15 from pid 1658 (timeout) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-1032-kvm 4.15.0-1032.32 ProcVersionSignature: User Name 4.15.0-1032.32-kvm 4.15.18 Uname: Linux 4.15.0-1032-kvm x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 Date: Tue May 7 03:36:32 2019 SourcePackage: linux-kvm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1827980/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1827982] Re: hyperv_stimer in ubuntu_kvm_unit_tests failed on B-KVM / B-Oracle-5.3 / B-Oracle-5.4
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux-oracle (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oracle in Ubuntu. https://bugs.launchpad.net/bugs/1827982 Title: hyperv_stimer in ubuntu_kvm_unit_tests failed on B-KVM / B-Oracle-5.3 / B-Oracle-5.4 Status in ubuntu-kernel-tests: New Status in linux-kvm package in Ubuntu: Confirmed Status in linux-oracle package in Ubuntu: Confirmed Bug description: Test timeouted. # TESTNAME=hyperv_stimer TIMEOUT=90s ACCEL= ./x86/run x86/hyperv_stimer.flat -smp 2 -cpu kvm64,hv_vpindex,hv_time,hv_synic,hv_stimer -device hyperv-testdev timeout -k 1s --foreground 90s /usr/bin/qemu-system-x86_64 -nodefaults -device pc-testdev -device isa-debug-exit,iobase=0xf4,iosize=0x4 -vnc none -serial stdio -device pci-testdev -machine accel=kvm -kernel x86/hyperv_stimer.flat -smp 2 -cpu kvm64,hv_vpindex,hv_time,hv_synic,hv_stimer -device hyperv-testdev # -initrd /tmp/tmp.ouYfwUEdq5 qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.01H:EDX.vme [bit 1] qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.01H:EDX.vme [bit 1] enabling apic enabling apic paging enabled cr0 = 80010011 cr3 = 459000 cr4 = 20 enabling apic cpus = 2 qemu-system-x86_64: terminating on signal 15 from pid 2224 (timeout) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-1032-kvm 4.15.0-1032.32 ProcVersionSignature: User Name 4.15.0-1032.32-kvm 4.15.18 Uname: Linux 4.15.0-1032-kvm x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 Date: Tue May 7 03:39:16 2019 SourcePackage: linux-kvm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1827982/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1827982] Re: hyperv_stimer in ubuntu_kvm_unit_tests failed on B-KVM / B-Oracle-5.3 / B-Oracle-5.4
Timeout on d2022.02.03/jammy/linux-realtime/5.15.0-1005.5 (rumford.amd64) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oracle in Ubuntu. https://bugs.launchpad.net/bugs/1827982 Title: hyperv_stimer in ubuntu_kvm_unit_tests failed on B-KVM / B-Oracle-5.3 / B-Oracle-5.4 Status in ubuntu-kernel-tests: New Status in linux-kvm package in Ubuntu: Confirmed Status in linux-oracle package in Ubuntu: Confirmed Bug description: Test timeouted. # TESTNAME=hyperv_stimer TIMEOUT=90s ACCEL= ./x86/run x86/hyperv_stimer.flat -smp 2 -cpu kvm64,hv_vpindex,hv_time,hv_synic,hv_stimer -device hyperv-testdev timeout -k 1s --foreground 90s /usr/bin/qemu-system-x86_64 -nodefaults -device pc-testdev -device isa-debug-exit,iobase=0xf4,iosize=0x4 -vnc none -serial stdio -device pci-testdev -machine accel=kvm -kernel x86/hyperv_stimer.flat -smp 2 -cpu kvm64,hv_vpindex,hv_time,hv_synic,hv_stimer -device hyperv-testdev # -initrd /tmp/tmp.ouYfwUEdq5 qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.01H:EDX.vme [bit 1] qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.01H:EDX.vme [bit 1] enabling apic enabling apic paging enabled cr0 = 80010011 cr3 = 459000 cr4 = 20 enabling apic cpus = 2 qemu-system-x86_64: terminating on signal 15 from pid 2224 (timeout) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-1032-kvm 4.15.0-1032.32 ProcVersionSignature: User Name 4.15.0-1032.32-kvm 4.15.18 Uname: Linux 4.15.0-1032-kvm x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 Date: Tue May 7 03:39:16 2019 SourcePackage: linux-kvm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1827982/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1953587] Re: Fix sanity checker and cleanup metadata
** Changed in: linux-firmware (Ubuntu Bionic) Status: New => 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/1953587 Title: Fix sanity checker and cleanup metadata Status in linux-firmware package in Ubuntu: New Status in linux-firmware source package in Bionic: Fix Committed Status in linux-firmware source package in Focal: Fix Released Status in linux-firmware source package in Hirsute: Fix Released Status in linux-firmware source package in Impish: Fix Released Bug description: The repo contains a checker script check_whence.py that checks WHENCE data against present firmware files and flags missing files and missing WHENCE entries. It currently doesn't parse the downstream WHENCE.ubuntu file. Fix that and cleanup any errors flagged by the checker. [ Impact ] None. These are packaging changes that are not visible to the end user. [ Where Problems Could Occur ] None. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1953587/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1960839] Re: Missing firmware /lib/firmware/intel/ice/ddp/ice.pkg for ice driver
** Changed in: linux-firmware (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-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/1960839
Title:
Missing firmware /lib/firmware/intel/ice/ddp/ice.pkg for ice driver
Status in linux-firmware package in Ubuntu:
Invalid
Status in linux-firmware source package in Bionic:
Fix Committed
Status in linux-firmware source package in Focal:
Invalid
Status in linux-firmware source package in Impish:
Invalid
Status in linux-firmware source package in Jammy:
Invalid
Bug description:
[Impact]
* Missing firmware for Intel ICE driver on Bionic,
which is supported by the HWE kernel from Focal.
[Fix]
* commit 9ae61e7d8658 ("ice: Add package file for Intel E800 series driver")
brings the Bionic package in line with Focal (ice-1.3.4.0.pkg,LICENSE.ice)
[Test Case]
* Without firmware:
ice :98:00.0: firmware 5.4.5 api 1.7.6 nvm 2.40 0x8000706a 0.0.0
build 0x391f7640
ice :98:00.0: Direct firmware load for intel/ice/ddp/ice.pkg failed
with error -2
ice :98:00.0: The DDP package file was not found or could not be
read. Entering Safe Mode
ice :98:00.0: Package download failed. Advanced features disabled -
Device now in Safe Mode
* With firmware:
ice :98:00.0: firmware 5.4.5 api 1.7.6 nvm 2.40 0x8000706a 0.0.0
build 0x391f7640
ice :98:00.0: The DDP package was successfully loaded: ICE OS Default
Package version 1.3.4.0
ice :98:00.0: DCB is enabled in the hardware, max number of TCs
supported on this port are 8
ice :98:00.0: FW LLDP is disabled, DCBx/LLDP in SW mode.
[Where problems could occur]
* Systems with devices managed by the ice driver on Bionic HWE kernel
from Focal.
* The firmware enables advanced features, increasing driver exposure
and device activity.
* This has been available on Focal, which helps with some chance of issues
being hit and
reported previously (e.g. bug 1939855, searched for 'kernel ice driver' on
bugs.lp.net).
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1960839/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1959424] Re: ubuntu_kernel_selftests / ftrace:ftracetest hangs on arm64 on Jammy realtime
Also: d2022.02.03/jammy/linux-realtime/5.15.0-1005.5 on dazzle.arm64 and helo-kernel.arm64 ** Tags added: arm64 ubuntu-kernel-selftests -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1959424 Title: ubuntu_kernel_selftests / ftrace:ftracetest hangs on arm64 on Jammy realtime Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Bug description: d2021.10.26/jammy/linux-realtime/5.15.0-1004.4, only on node appleton-kernel.arm64, hangs (timeouts) on ubuntu_kernel_selftests / ftrace:ftracetest test: 01:28:34 DEBUG| [stdout] # === Ftrace unit tests === 01:28:34 DEBUG| [stdout] # [1] Basic trace file check[PASS] 01:28:38 DEBUG| [stdout] # [2] Basic test for tracers[PASS] 01:28:38 DEBUG| [stdout] # [3] Basic trace clock test[PASS] 01:28:38 DEBUG| [stdout] # [4] Basic event tracing check[PASS] 01:28:39 DEBUG| [stdout] # [5] Change the ringbuffer size[PASS] 01:28:39 DEBUG| [stdout] # [6] Snapshot and tracing setting[PASS] 01:28:40 DEBUG| [stdout] # [7] trace_pipe and trace_marker[PASS] 01:28:40 DEBUG| [stdout] # [8] Test ftrace direct functions against tracers [UNRESOLVED] 01:28:40 DEBUG| [stdout] # [9] Test ftrace direct functions against kprobes [UNRESOLVED] 01:28:40 DEBUG| [stdout] # [10] Generic dynamic event - add/remove eprobe events[PASS] 01:28:41 DEBUG| [stdout] # [11] Generic dynamic event - add/remove kprobe events[PASS] 01:28:41 DEBUG| [stdout] # [12] Generic dynamic event - add/remove synthetic events[PASS] 01:28:41 DEBUG| [stdout] # [13] Generic dynamic event - selective clear (compatibility)[PASS] 01:28:41 DEBUG| [stdout] # [14] Generic dynamic event - generic clear event [PASS] 01:28:42 DEBUG| [stdout] # [15] Generic dynamic event - check if duplicate events are caught[PASS] 01:58:36 INFO | Timer expired (1800 sec.), nuking pid 161336 The issue was not reproduced on mcdivitt36 (HP ProLiant m400 server cartridge with AppliedMicro X-Gene 64-bit ARM). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1959424/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1960361] Re: hwmon: k10temp updates for AMD Genoa in 22.04
** Also affects: linux (Ubuntu Jammy) Importance: Medium Assignee: Jeff Lane (bladernr) Status: 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/1960361 Title: hwmon: k10temp updates for AMD Genoa in 22.04 Status in linux package in Ubuntu: In Progress Status in linux source package in Jammy: In Progress Bug description: Patch pull request to include additional support for AMD Genoa in 22.04 f707bcb5d1cb 5.17 hwmon: (k10temp) Remove unused definitions 3cf90efa1367 5.17 hwmon: (k10temp) Add support for AMD Family 19h Models 10h-1Fh and A0h-AFh 8bb050cd5cf4 5.17 hwmon: (k10temp) Support up to 12 CCDs on AMD Family of processors To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1960361/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1960362] Re: EDAC update for AMD Genoa support in 22.04
** Also affects: linux (Ubuntu Jammy) Importance: Medium Assignee: Jeff Lane (bladernr) Status: 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/1960362 Title: EDAC update for AMD Genoa support in 22.04 Status in linux package in Ubuntu: In Progress Status in linux source package in Jammy: In Progress Bug description: EDAC updates for AMD Genoa support for 22.04 as requested by AMD f957112423905.17EDAC: Add RDDR5 and LRDDR5 memory types e2be5955a8865.17EDAC/amd64: Add support for AMD Family 19h Models 10h-1Fh and A0h-AFh To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1960362/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1960771] Re: Use EC GPE for s2idle wakeup on AMD platforms
** Tags added: originate-from-1952215 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1960771 Title: Use EC GPE for s2idle wakeup on AMD platforms Status in HWE Next: New Status in linux package in Ubuntu: Confirmed Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Won't Fix Status in linux-oem-5.14 source package in Focal: Fix Committed Status in linux source package in Jammy: Confirmed Status in linux-oem-5.14 source package in Jammy: Invalid Bug description: [Impact] Opening lid doesn't wakeup some AMD platforms from s2idle. [Fix] Use EC GPE for lid events to wakeup the laptops. [Test] Close and only the lid. The affected laptop now can be woken up by lid. [Where problems could occur] The original issue was later fixed by "pinctrl: amd: Fix wakeups when IRQ is shared with SCI". However, EC GPE is prone to cause spurious wakeup, so we still need to keep an eye on the regression reports. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1960771/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1953587] Re: Fix sanity checker and cleanup metadata
** Also affects: linux-firmware (Ubuntu Bionic) Importance: Undecided Status: New -- 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/1953587 Title: Fix sanity checker and cleanup metadata Status in linux-firmware package in Ubuntu: New Status in linux-firmware source package in Bionic: New Status in linux-firmware source package in Focal: Fix Released Status in linux-firmware source package in Hirsute: Fix Released Status in linux-firmware source package in Impish: Fix Released Bug description: The repo contains a checker script check_whence.py that checks WHENCE data against present firmware files and flags missing files and missing WHENCE entries. It currently doesn't parse the downstream WHENCE.ubuntu file. Fix that and cleanup any errors flagged by the checker. [ Impact ] None. These are packaging changes that are not visible to the end user. [ Where Problems Could Occur ] None. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1953587/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1960895] Re: apt ubuntu-driver-460 Point to 470.103.01-0ubuntu0.18.04.1
** Package changed: ubuntu => nvidia-graphics-drivers-460-server (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-460-server in Ubuntu. https://bugs.launchpad.net/bugs/1960895 Title: apt ubuntu-driver-460 Point to 470.103.01-0ubuntu0.18.04.1 Status in nvidia-graphics-drivers-460-server package in Ubuntu: New Bug description: libnvidia-cfg1-460/bionic-updates,bionic-security 470.103.01-0ubuntu0.18.04.1 amd64 [upgradable from: 460.106.00-0ubuntu1] libnvidia-common-460/bionic-updates,bionic-security 470.103.01-0ubuntu0.18.04.1 all [upgradable from: 460.106.00-0ubuntu1] libnvidia-compute-460/bionic-updates,bionic-security 470.103.01-0ubuntu0.18.04.1 amd64 [upgradable from: 460.106.00-0ubuntu1] libnvidia-decode-460/bionic-updates,bionic-security 470.103.01-0ubuntu0.18.04.1 amd64 [upgradable from: 460.106.00-0ubuntu1] libnvidia-encode-460/bionic-updates,bionic-security 470.103.01-0ubuntu0.18.04.1 amd64 [upgradable from: 460.106.00-0ubuntu1] libnvidia-extra-460/bionic-updates,bionic-security 470.103.01-0ubuntu0.18.04.1 amd64 [upgradable from: 460.106.00-0ubuntu1] libnvidia-fbc1-460/bionic-updates,bionic-security 470.103.01-0ubuntu0.18.04.1 amd64 [upgradable from: 460.106.00-0ubuntu1] libnvidia-gl-460/bionic-updates,bionic-security 470.103.01-0ubuntu0.18.04.1 amd64 [upgradable from: 460.106.00-0ubuntu1] libnvidia-ifr1-460/bionic-updates,bionic-security 470.103.01-0ubuntu0.18.04.1 amd64 [upgradable from: 460.106.00-0ubuntu1] mesa-vdpau-drivers/bionic-updates 20.0.8-0ubuntu1~18.04.1 amd64 [upgradable from: 18.0.0~rc5-1ubuntu1] nvidia-compute-utils-460/bionic-updates,bionic-security 470.103.01-0ubuntu0.18.04.1 amd64 [upgradable from: 460.106.00-0ubuntu1] nvidia-dkms-460/bionic-updates,bionic-security 470.103.01-0ubuntu0.18.04.1 amd64 [upgradable from: 460.106.00-0ubuntu1] nvidia-driver-460/bionic-updates,bionic-security 470.103.01-0ubuntu0.18.04.1 amd64 [upgradable from: 460.106.00-0ubuntu1] nvidia-kernel-common-460/bionic-updates,bionic-security 470.103.01-0ubuntu0.18.04.1 amd64 [upgradable from: 460.106.00-0ubuntu1] nvidia-kernel-source-460/bionic-updates,bionic-security 470.103.01-0ubuntu0.18.04.1 amd64 [upgradable from: 460.106.00-0ubuntu1] nvidia-prime/bionic-updates 0.8.16~0.18.04.1 all [upgradable from: 0.8.8] nvidia-utils-460/bionic-updates,bionic-security 470.103.01-0ubuntu0.18.04.1 amd64 [upgradable from: 460.106.00-0ubuntu1] ubuntu-mono/bionic-updates 16.10+18.04.20181005-0ubuntu1 all [upgradable from: 16.10+18.04.20180421.1-0ubuntu1] x11-common/bionic-updates 1:7.7+19ubuntu7.1 all [upgradable from: 1:7.7+19ubuntu7] x11-xkb-utils/bionic-updates 7.7+3ubuntu0.18.04.1 amd64 [upgradable from: 7.7+3] xserver-common/bionic-updates,bionic-security 2:1.19.6-1ubuntu4.10 all [upgradable from: 2:1.19.6-1ubuntu4] xserver-xorg-core/bionic-updates,bionic-security 2:1.19.6-1ubuntu4.10 amd64 [upgradable from: 2:1.19.6-1ubuntu4] xserver-xorg-video-nvidia-460/bionic-updates,bionic-security 470.103.01-0ubuntu0.18.04.1 amd64 [upgradable from: 460.106.00-0ubuntu1] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-460-server/+bug/1960895/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1960895] [NEW] apt ubuntu-driver-460 Point to 470.103.01-0ubuntu0.18.04.1
You have been subscribed to a public bug: libnvidia-cfg1-460/bionic-updates,bionic-security 470.103.01-0ubuntu0.18.04.1 amd64 [upgradable from: 460.106.00-0ubuntu1] libnvidia-common-460/bionic-updates,bionic-security 470.103.01-0ubuntu0.18.04.1 all [upgradable from: 460.106.00-0ubuntu1] libnvidia-compute-460/bionic-updates,bionic-security 470.103.01-0ubuntu0.18.04.1 amd64 [upgradable from: 460.106.00-0ubuntu1] libnvidia-decode-460/bionic-updates,bionic-security 470.103.01-0ubuntu0.18.04.1 amd64 [upgradable from: 460.106.00-0ubuntu1] libnvidia-encode-460/bionic-updates,bionic-security 470.103.01-0ubuntu0.18.04.1 amd64 [upgradable from: 460.106.00-0ubuntu1] libnvidia-extra-460/bionic-updates,bionic-security 470.103.01-0ubuntu0.18.04.1 amd64 [upgradable from: 460.106.00-0ubuntu1] libnvidia-fbc1-460/bionic-updates,bionic-security 470.103.01-0ubuntu0.18.04.1 amd64 [upgradable from: 460.106.00-0ubuntu1] libnvidia-gl-460/bionic-updates,bionic-security 470.103.01-0ubuntu0.18.04.1 amd64 [upgradable from: 460.106.00-0ubuntu1] libnvidia-ifr1-460/bionic-updates,bionic-security 470.103.01-0ubuntu0.18.04.1 amd64 [upgradable from: 460.106.00-0ubuntu1] mesa-vdpau-drivers/bionic-updates 20.0.8-0ubuntu1~18.04.1 amd64 [upgradable from: 18.0.0~rc5-1ubuntu1] nvidia-compute-utils-460/bionic-updates,bionic-security 470.103.01-0ubuntu0.18.04.1 amd64 [upgradable from: 460.106.00-0ubuntu1] nvidia-dkms-460/bionic-updates,bionic-security 470.103.01-0ubuntu0.18.04.1 amd64 [upgradable from: 460.106.00-0ubuntu1] nvidia-driver-460/bionic-updates,bionic-security 470.103.01-0ubuntu0.18.04.1 amd64 [upgradable from: 460.106.00-0ubuntu1] nvidia-kernel-common-460/bionic-updates,bionic-security 470.103.01-0ubuntu0.18.04.1 amd64 [upgradable from: 460.106.00-0ubuntu1] nvidia-kernel-source-460/bionic-updates,bionic-security 470.103.01-0ubuntu0.18.04.1 amd64 [upgradable from: 460.106.00-0ubuntu1] nvidia-prime/bionic-updates 0.8.16~0.18.04.1 all [upgradable from: 0.8.8] nvidia-utils-460/bionic-updates,bionic-security 470.103.01-0ubuntu0.18.04.1 amd64 [upgradable from: 460.106.00-0ubuntu1] ubuntu-mono/bionic-updates 16.10+18.04.20181005-0ubuntu1 all [upgradable from: 16.10+18.04.20180421.1-0ubuntu1] x11-common/bionic-updates 1:7.7+19ubuntu7.1 all [upgradable from: 1:7.7+19ubuntu7] x11-xkb-utils/bionic-updates 7.7+3ubuntu0.18.04.1 amd64 [upgradable from: 7.7+3] xserver-common/bionic-updates,bionic-security 2:1.19.6-1ubuntu4.10 all [upgradable from: 2:1.19.6-1ubuntu4] xserver-xorg-core/bionic-updates,bionic-security 2:1.19.6-1ubuntu4.10 amd64 [upgradable from: 2:1.19.6-1ubuntu4] xserver-xorg-video-nvidia-460/bionic-updates,bionic-security 470.103.01-0ubuntu0.18.04.1 amd64 [upgradable from: 460.106.00-0ubuntu1] ** Affects: nvidia-graphics-drivers-460-server (Ubuntu) Importance: Undecided Status: New ** Tags: bot-comment -- apt ubuntu-driver-460 Point to 470.103.01-0ubuntu0.18.04.1 https://bugs.launchpad.net/bugs/1960895 You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-460-server 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 1960841] Re: Make linux-tools-common Provide linux-cpupower
** Also affects: opa-ff (Ubuntu) Importance: Undecided Status: New ** Changed in: opa-ff (Ubuntu) Status: New => Incomplete ** Changed in: opa-ff (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/1960841 Title: Make linux-tools-common Provide linux-cpupower Status in linux package in Ubuntu: Confirmed Status in opa-ff package in Ubuntu: Confirmed Bug description: In Debian, the tools cpupower, turbostat and x86_energy_perf_policy are packaged in linux-cpupower. In turn, some packages that use those CLI tools depend on this package. Currently on Debian sid, we have ❯ reverse-depends linux-cpupower Reverse-Recommends * tuned Reverse-Depends * opa-basic-tools [amd64 Having linux-tools-common Providing linux-cpupower would allow us to keep the aforementioned packages in sync with Debian without introducing a delta. While this is related to https://bugs.launchpad.net/ubuntu/+source/opa-ff/+bug/1215411 it is *not* the same issue, as we're not dealing with the libraries but with the CLI tools. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1960841/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
